Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

On the latest Nightly, Save to Pocket won't let me log in

  • 4 பதிலளிப்புகள்
  • 1 இந்த பிரச்சனை உள்ளது
  • 7 views
  • Last reply by Bryan Moore

When I click the Save to Pocket icon in the address bar, I'm greeted with a dialog stating I'm not signed in and asking if I'd like to create and account or log in to one I already have. I log in appropriately and a tab open into my Pocket; however, the icon still thinks I'm not logged in and the process simply repeats. I've done this with the Google, Firefox, and email/username sign in choices. What gives?

My system: System: Host: zenbook Kernel: 4.17.3-81.current x86_64 bits: 64 Desktop: Budgie 10.4-85-g36667bcb

          Distro: Solus 3.9999 

Machine: Type: Laptop System: ASUSTeK product: UX330UAR v: 1.0 serial: <filter>

          Mobo: ASUSTeK model: UX330UAR v: 1.0 serial: <filter> UEFI: American Megatrends v: UX330UAR.300 
          date: 08/03/2017 

Battery: ID-1: BAT0 charge: 42.1 Wh condition: 50.3/57.1 Wh (88%) CPU: Topology: Quad Core model: Intel Core i5-8250U bits: 64 type: MT MCP L2 cache: 6144 KiB

          Speed: 900 MHz min/max: 400/3400 MHz Core speeds (MHz): 1: 900 2: 900 3: 900 4: 900 5: 900 6: 900 
          7: 900 8: 900 

Graphics: Card-1: Intel UHD Graphics 620 driver: i915 v: kernel

          Display: x11 server: X.Org 1.19.6 driver: modesetting unloaded: fbdev,intel,vesa 
          resolution: 1920x1080~60Hz 
          OpenGL: renderer: Mesa DRI Intel UHD Graphics 620 (Kabylake GT2) v: 4.5 Mesa 18.1.3 

Audio: Card-1: Intel Sunrise Point-LP HD Audio driver: snd_hda_intel

          Sound Server: ALSA v: k4.17.3-81.current 

Network: Card-1: Intel Wireless 8260 driver: iwlwifi

          IF: wlp2s0 state: up mac: <filter> 

Drives: HDD Total Size: 354.16 GiB used: 18.21 GiB (5.1%)

          ID-1: /dev/sda vendor: Micron model: 1100 MTFDDAV256TBN size: 238.47 GiB 
          ID-2: /dev/sdb type: USB vendor: SanDisk model: Ultra Fit size: 115.69 GiB 

Partition: ID-1: / size: 229.59 GiB used: 18.21 GiB (7.9%) fs: ext4 dev: /dev/dm-1 Sensors: Missing: Required tool sensors not installed. Check --recommends Info: Processes: 256 Uptime: 45m Memory: 7.74 GiB used: 2.25 GiB (29.1%) Shell: bash inxi: 3.0.10

When I click the Save to Pocket icon in the address bar, I'm greeted with a dialog stating I'm not signed in and asking if I'd like to create and account or log in to one I already have. I log in appropriately and a tab open into my Pocket; however, the icon still thinks I'm not logged in and the process simply repeats. I've done this with the Google, Firefox, and email/username sign in choices. What gives? My system: System: Host: zenbook Kernel: 4.17.3-81.current x86_64 bits: 64 Desktop: Budgie 10.4-85-g36667bcb Distro: Solus 3.9999 Machine: Type: Laptop System: ASUSTeK product: UX330UAR v: 1.0 serial: <filter> Mobo: ASUSTeK model: UX330UAR v: 1.0 serial: <filter> UEFI: American Megatrends v: UX330UAR.300 date: 08/03/2017 Battery: ID-1: BAT0 charge: 42.1 Wh condition: 50.3/57.1 Wh (88%) CPU: Topology: Quad Core model: Intel Core i5-8250U bits: 64 type: MT MCP L2 cache: 6144 KiB Speed: 900 MHz min/max: 400/3400 MHz Core speeds (MHz): 1: 900 2: 900 3: 900 4: 900 5: 900 6: 900 7: 900 8: 900 Graphics: Card-1: Intel UHD Graphics 620 driver: i915 v: kernel Display: x11 server: X.Org 1.19.6 driver: modesetting unloaded: fbdev,intel,vesa resolution: 1920x1080~60Hz OpenGL: renderer: Mesa DRI Intel UHD Graphics 620 (Kabylake GT2) v: 4.5 Mesa 18.1.3 Audio: Card-1: Intel Sunrise Point-LP HD Audio driver: snd_hda_intel Sound Server: ALSA v: k4.17.3-81.current Network: Card-1: Intel Wireless 8260 driver: iwlwifi IF: wlp2s0 state: up mac: <filter> Drives: HDD Total Size: 354.16 GiB used: 18.21 GiB (5.1%) ID-1: /dev/sda vendor: Micron model: 1100 MTFDDAV256TBN size: 238.47 GiB ID-2: /dev/sdb type: USB vendor: SanDisk model: Ultra Fit size: 115.69 GiB Partition: ID-1: / size: 229.59 GiB used: 18.21 GiB (7.9%) fs: ext4 dev: /dev/dm-1 Sensors: Missing: Required tool sensors not installed. Check --recommends Info: Processes: 256 Uptime: 45m Memory: 7.74 GiB used: 2.25 GiB (29.1%) Shell: bash inxi: 3.0.10

All Replies (4)

Please note that Firefox Nightly is for evaluation purposes only. This version represents Firefox in the earliest stage of development and it contains many bugs. We highly recommend not to run Firefox Nightly edition as your regular internet browser.

If you still want to experiment with Firefox before it reaches the release stage, I would recommend the Firefox Beta version instead because it's far more stable and a lot of the bugs have been worked out.

I would recommend trying to run Firefox in Safe Mode to see if the issue is still there. If it is, you may have found a bug with Firefox Nightly and you can report it on Bugzilla.

Thanks for the reply, Wesley. If I'm posting a possible bug while using Nightly, shouldn't one assume I'm aware it's pre-release and buggy? I'm truly not trying to sound snarky; it's a frustration of mine when a dev/alpha user posts in a forum looking to see if anyone else is suffering a problem to be greeted with "alphas are always buggy." <sarcasm>O, rly?</sarcasm>

I've seen there is, indeed, a bug already open about this; so, I've added my two cents.

Thanks, again, for the reply and reminding me about relaunching with add-ons disabled... that's something I always forget to do. ::bashful::

HI, you are in the wrong place for posting bugs. Volunteer Support can do nothing with them. Also this is not run as a regular forum. When you post you are serviced by Volunteers or sometimes several to trouble shoot the issue and to get it back working properly. The public is not invited to be posting in your question for help.

If you have a bug, file a bug report. https://bugzilla.mozilla.org/ Bug Writing Guidelines : https://developer.mozilla.org/en-US/docs/Mozilla/QA/Bug_writing_guidelines

Pkshadow: again, I was seeking out if my issue is isolated *before* submitting a bug; I now understanding the Mozilla process is slightly different than other fora...