[Bug 2064977] [NEW] new gnome-terminal instances launched from nautilus fail to receive automatic focus
Public bug reported: When a first gnome-terminal instance is launched from nautilus (context menu item "Open in Terminal"), it automatically receives focus for keyboard input. When additional instances are launched in the same way, the mechanism breaks down and focus remains with nautilus. If the user immediately starts typing, their input ends up being processed by the nautilus search bar instead of the terminal. Correcting this course of action requires unnecessary clicks or keyboard strokes. That is potentially confusing and certainly annoying. I remember being affected by the same bug in the early days of either Ubuntu 23.04 or 23.10. I have found a bug report related to gentoo that mentions something very much like what I am describing here: https://forums.gentoo.org/viewtopic-p-8790088.html?sid=fe9cfd6188d38eb5e550e3e45fffe19f;. It seems to suggest that the bug affects only wayland but I use X11. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: mutter (not installed) ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue May 7 03:06:57 2024 InstallationDate: Installed on 2022-03-27 (771 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326) SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: mutter (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble ** Description changed: When a first gnome-terminal instance is launched from nautilus (context menu item "Open in Terminal"), it automatically receives focus. When additional instances are launched in the same way, the mechanism breaks down and focus remains with nautilus. If the user immediately starts typing, their input ends up being processed by the nautilus search bar instead of the terminal. Correcting this course of action requires unnecessary clicks or keyboard strokes. That is potentially confusing and certainly annoying. I remember being affected by the same bug in the early days of either Ubuntu 23.04 or 23.10. I have found a bug report on the gentoo forums that looks very much like what I am describing here: https://forums.gentoo.org/viewtopic-p-8790088.html?sid=fe9cfd6188d38eb5e550e3e45fffe19f;> - g ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: mutter (not installed) ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue May 7 03:06:57 2024 InstallationDate: Installed on 2022-03-27 (771 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326) SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) ** Description changed: When a first gnome-terminal instance is launched from nautilus (context menu item "Open in Terminal"), it automatically receives focus. When additional instances are launched in the same way, the mechanism breaks down and focus remains with nautilus. If the user immediately starts typing, their input ends up being processed by the nautilus search bar instead of the terminal. Correcting this course of action requires unnecessary clicks or keyboard strokes. That is potentially confusing and certainly annoying. I remember being affected by the same bug in the early days of either Ubuntu 23.04 or 23.10. I have found a bug report on the gentoo forums - that looks very much like what I am describing here: https://forums.gentoo.org/viewtopic-p-8790088.html?sid=fe9cfd6188d38eb5e550e3e45fffe19f;> - g + that looks very much like what I am describing here: + https://forums.gentoo.org/viewtopic-p-8790088.html?sid=fe9cfd6188d38eb5e550e3e45fffe19f; ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: mutter (not installed) ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue May 7 03:06:57 2024 InstallationDate: Installed on 2022-03-27 (771 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326) SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) ** Description changed: When a first gnome-terminal instance is launched from nautilus (context - menu item "Open in Terminal"), it automatically receives focus. + menu item "Open in Terminal"), it automatically receives focus for + keyboard input. When additional instances are launched in the same way, the
[Bug 2063397] Re: extracting rar archives sometime incomplete
I have tried to create an archive of my own to reproduce the problem. I
think I have succeeded.
Check the included archive, which contains:
- 10 folders containing 10 (empty) text files
- a zip archive containing a single file filled with some data gleaned from
/dev/random
observation:
- trying to inspect the contents with file-roller causes file-roller to crash
- extracting the file extracts only the contents of the zip archive (compare:
extraction from the CLI with rar e)
more observations:
- I had to compress from the command line (with the rar utility) as nautilus
consistently crashes if I try to compress through the context menu ("compress")
- the issue appears to match this report on reddit:
https://www.reddit.com/r/gnome/comments/1btxk69/nautilus_crashing_when_selecting_multiple_files/
** Attachment added: "archive.rar"
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2063397/+attachment/5770668/+files/archive.rar
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/2063397
Title:
extracting rar archives sometime incomplete
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2063397/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2063397] Re: extracting rar archives sometime incomplete
Sadly, no. The archives in question are copyrighted so I doubt it would be a good idea to post them here in the open. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/2063397 Title: extracting rar archives sometime incomplete To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2063397/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2063397] [NEW] nautilus extract option causes date loss from rar archives
Public bug reported:
Extraction of rar files (v5) from the context menu ("Extract")
occasionally results in one or more subfolders silently being skipped.
This behavior is not systematic. Some rar archives extract properly,
other ones do not.
There is not any warning or error message when the problem manifests,
which make it likely that the problem goes overlooked. I have
effectively sustained data loss until I discovered that one of my
extracted folders was much smaller than it should have been.
I have unrar (non-free) and 7z installed.
Applications like file-roller and arqiver appear to function properly.
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: nautilus 1:46.0-0ubuntu2
ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1
Uname: Linux 6.8.0-31-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.28.1-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Thu Apr 25 05:26:17 2024
InstallationDate: Installed on 2022-03-27 (759 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326)
SourcePackage: nautilus
UpgradeStatus: No upgrade log present (probably fresh install)
usr_lib_nautilus:
eiciel0.10.0-1build2
file-roller 44.1-1
nautilus-extension-gnome-terminal 3.52.0-1ubuntu2
python3-nautilus 4.0-1build4
** Affects: nautilus (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug noble third-party-packages
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/2063397
Title:
nautilus extract option causes date loss from rar archives
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2063397/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2060575] Re: gnome-keyring fails to automatically unlock login keyring after recent updates in noble
I believe that the evolution mail program and google accounts are to blame. The problem went away for me after I deleted my keyring and switched from evolution to thunderbird. Trying to (re-)add a mail account to evolution immediately brings the problem is back. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/2060575 Title: gnome-keyring fails to automatically unlock login keyring after recent updates in noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/2060575/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2042705] Re: screen blank randomly fails and system crashes when X is restarted
It sounds like this bug is (at least partly) related to https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2040453 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2042705 Title: screen blank randomly fails and system crashes when X is restarted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2042705/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2042705] [NEW] screen blank randomly fails and system crashes when X is restarted
Public bug reported: My screen randomly stops blanking, ignoring the interval I set under Settings > Power > Power Saving Options > Screen blank (8 minutes). This behaviour behaviour has so far manifested only after I resumed the system from suspend but that connection is not consistent - more often than not, the system resumes without any noticeable impact on screen blanking. However, when screen blanking does break, it appears to go hand in hand with an unstable gnome session. That is, when I try to restart my gnome session (I am using X), it results in a desktop crash and I am forced to log out. (on a side note: I noticed the other day that gnome also broke when I logged out of my second desktop account to return to my main account; the screen went black and I had to reboot). The crash does not appear to generate a log but journald has recorded the following at/around the time that restarting gnome-shell ended in a crash (the messages are reproduced here in reverse order): nov 04 02:41:46 Dapple gsd-media-keys[3125]: g_dbus_proxy_call_internal: assertion 'G_IS_DBUS_PROXY (proxy)' failed nov 04 02:41:45 Dapple systemd[2589]: org.gnome.Shell-disable-extensions.service - Disable GNOME Shell extensions after failure was skipped because of an unmet condition check (ConditionPathExists=/run/user/1002/gnome-shell-disa> nov 04 02:41:45 Dapple systemd[2589]: Reached target gnome-session-failed.target - GNOME Session Failed. nov 04 02:41:45 Dapple systemd[2589]: Started gnome-session-failed.service - GNOME Session Failed lockdown screen (user). nov 04 02:41:45 Dapple systemd[2589]: org.gnome.Shell@x11.service: Triggering OnFailure= dependencies. nov 04 02:41:45 Dapple systemd[2589]: Failed to start org.gnome.Shell@x11.service - GNOME Shell on X11. nov 04 02:41:45 Dapple systemd[2589]: org.gnome.Shell@x11.service: Failed with result 'protocol'. nov 04 02:41:45 Dapple systemd[2589]: org.gnome.Shell@x11.service: Start request repeated too quickly. nov 04 02:41:45 Dapple systemd[2589]: Stopped org.gnome.Shell@x11.service - GNOME Shell on X11. nov 04 02:41:45 Dapple systemd[2589]: org.gnome.Shell@x11.service: Scheduled restart job, restart counter is at 4. nov 04 02:41:45 Dapple systemd[2589]: Failed to start org.gnome.Shell@x11.service - GNOME Shell on X11. nov 04 02:41:45 Dapple systemd[2589]: org.gnome.Shell@x11.service: Failed with result 'protocol'. nov 04 02:41:45 Dapple gnome-shell[73870]: Window manager error: Another compositing manager is already running on screen 0 on display “:1”. nov 04 02:41:45 Dapple gsd-media-keys[3125]: Failed to grab accelerators: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: Object does not exist at path “/org/gnome/Shell” nov 04 02:41:44 Dapple gsd-media-keys[3125]: Failed to grab accelerators: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: Object does not exist at path “/org/gnome/Shell” nov 04 02:41:44 Dapple xdg-desktop-por[3867]: Failed to get application states: GDBus.Error:org.freedesktop.portal.Error.Failed: Could not get window list nov 04 02:41:44 Dapple /usr/libexec/gdm-x-session[2762]: (--) NVIDIA(GPU-0): nov 04 02:41:44 Dapple /usr/libexec/gdm-x-session[2762]: (--) NVIDIA(GPU-0): DFP-4: 330.0 MHz maximum pixel clock nov 04 02:41:44 Dapple /usr/libexec/gdm-x-session[2762]: (--) NVIDIA(GPU-0): DFP-4: Internal TMDS nov 04 02:41:44 Dapple /usr/libexec/gdm-x-session[2762]: (--) NVIDIA(GPU-0): DFP-4: disconnected nov 04 02:41:44 Dapple /usr/libexec/gdm-x-session[2762]: (--) NVIDIA(GPU-0): nov 04 02:41:44 Dapple /usr/libexec/gdm-x-session[2762]: (--) NVIDIA(GPU-0): DFP-3: 165.0 MHz maximum pixel clock nov 04 02:41:44 Dapple /usr/libexec/gdm-x-session[2762]: (--) NVIDIA(GPU-0): DFP-3: Internal TMDS nov 04 02:41:44 Dapple /usr/libexec/gdm-x-session[2762]: (--) NVIDIA(GPU-0): DFP-3: disconnected nov 04 02:41:44 Dapple /usr/libexec/gdm-x-session[2762]: (--) NVIDIA(GPU-0): nov 04 02:41:44 Dapple /usr/libexec/gdm-x-session[2762]: (--) NVIDIA(GPU-0): DFP-2: 960.0 MHz maximum pixel clock nov 04 02:41:44 Dapple /usr/libexec/gdm-x-session[2762]: (--) NVIDIA(GPU-0): DFP-2: Internal DisplayPort nov 04 02:41:44 Dapple /usr/libexec/gdm-x-session[2762]: (--) NVIDIA(GPU-0): DFP-2: disconnected nov 04 02:41:44 Dapple /usr/libexec/gdm-x-session[2762]: (--) NVIDIA(GPU-0): nov 04 02:41:44 Dapple /usr/libexec/gdm-x-session[2762]: (--) NVIDIA(GPU-0): BenQ EW3270U (DFP-1): 600.0 MHz maximum pixel clock nov 04 02:41:44 Dapple /usr/libexec/gdm-x-session[2762]: (--) NVIDIA(GPU-0): BenQ EW3270U (DFP-1): Internal TMDS nov 04 02:41:44 Dapple /usr/libexec/gdm-x-session[2762]: (--) NVIDIA(GPU-0): BenQ EW3270U (DFP-1): connected nov 04 02:41:44 Dapple /usr/libexec/gdm-x-session[2762]: (--) NVIDIA(GPU-0): nov 04 02:41:44 Dapple /usr/libexec/gdm-x-session[2762]: (--) NVIDIA(GPU-0): Samsung SyncMaster (DFP-0): 330.0 MHz maximum pixel clock nov 04 02:41:44 Dapple /usr/libexec/gdm-x-session[2762]: (--) NVIDIA(GPU-0): Samsung SyncMaster (DFP-0): Internal TMDS
[Bug 2017716] Re: Folders and files frequently need to be clicked twice
The issue seems to be related. The video shows a feature I had not noticed yet but that is certainly there: the problem does not manifest if I take the "precaution" of first moving the mouse outside nautilus before I click on a different folder. What I mean is: 1. open nautilus 2. click on a folder to open it 3. move back (I am using the side button on my mouse to do so) 4. move the cursor outside nautilus (no clicking required here) 5. return to the window and click on a different folder; it instantly opens Without step 4, step 5 is unpredictable - sometimes the folder opens at once, sometimes nothing happens and the folder needs to be clicked again at least once. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/2017716 Title: Folders and files frequently need to be clicked twice To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2017716/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2017716] [NEW] Folders and files frequently need to be clicked twice
Public bug reported: Nautilus randomly drops about half of my mouse clicks. Clicked folders or files will sometimes open at once, yet the next time(s) fail to respond until clicked a second time. I am seeing this both on X11 and on wayland. Single or double click policy does not make any difference. I have experimented with different mouse speeds but have not seen any noticeable difference. This behaviour is, in fact, something that I already noticed when I was trying out Ubuntu 22.10. It was enough to send me back to 22.04. I was really hoping that the issue would be solved by now, but clearly it is not. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: nautilus 1:44.0-1ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Apr 26 02:25:07 2023 InstallationDate: Installed on 2022-10-29 (178 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) SourcePackage: nautilus UpgradeStatus: Upgraded to lunar on 2023-04-12 (13 days ago) usr_lib_nautilus: file-roller 43.0-1 nautilus-extension-gnome-terminal 3.48.0-1ubuntu1 python3-nautilus 4.0-1build1 ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lunar -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/2017716 Title: Folders and files frequently need to be clicked twice To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2017716/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2006059] Re: systemd refuses to start secondary Xorg logins [org.gnome.Shell@x11.service: Skipped due to 'exec-condition'.]
I have installed the package from proposed, rebooted and now the login process is finally working as it should. Well done! -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/2006059 Title: systemd refuses to start secondary Xorg logins [org.gnome.Shell@x11.service: Skipped due to 'exec-condition'.] To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/2006059/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2016428] Re: nautilus crashes when entering a query into the search box
Update: It seems to be fixed by a tracker3 reset --filesystem. I'll see how it goes... -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/2016428 Title: nautilus crashes when entering a query into the search box To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2016428/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2016428] Re: nautilus crashes when entering a query into the search box
Update: the bug is NOT restricted to X11. Wayland is affected, too, although not as badly: it does not crash immediately and it happens only when searching directories containing many files (many = tens of thousands) and mostly when doing a remote search (over NFS). The error message is different, too: "Segmentation fault (core dumped)". -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/2016428 Title: nautilus crashes when entering a query into the search box To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2016428/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2016428] [NEW] nautilus crashes when entering a query into the search box
Public bug reported: As soon as I start typing in its search box, nautilus freezes for a second and then goes on to crash. When that happens, the terminal reports a "Bus Error". This happens systematically when the directory contains many files. It also appears to be restricted to X11. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: nautilus 1:44.0-1ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: GNOME Date: Sun Apr 16 21:39:52 2023 InstallationDate: Installed on 2022-10-29 (169 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) SourcePackage: nautilus UpgradeStatus: Upgraded to lunar on 2023-04-12 (4 days ago) usr_lib_nautilus: eiciel0.10.0-1 file-roller 43.0-1 nautilus-extension-gnome-terminal 3.48.0-1ubuntu1 python3-nautilus 4.0-1build1 ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lunar wayland-session -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/2016428 Title: nautilus crashes when entering a query into the search box To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2016428/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2006059] Re: systemd refuses to start secondary Xorg logins [org.gnome.Shell@x11.service: Skipped due to 'exec-condition'.]
I commented out the suggested line but the only effect is that switching accounts is now completely impossible. More specifically, it prevents me from getting past the login screen: 1. I select "switch user" from my running user session 2. I am sent to the login screen 3. I select a different user and submit the password 4. the screen goes black for a second 5 and I find myself back at step 2 6. All I can do at this stage is log in again as my initial user After enabling debugging in /etc/gdm3/custom.conf, /var/crash has received a pulseaudio related crash message. I see the owner is my initial user so I am not sure it has anything to do with my other user accounts. Should I append the crash file here as an attachment? -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/2006059 Title: systemd refuses to start secondary Xorg logins [org.gnome.Shell@x11.service: Skipped due to 'exec-condition'.] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/2006059/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2016182] [NEW] terminal opened started from nautilus does not get focus
Public bug reported:
Terminals launched from the nautilus context menu ("Open in Terminal") do not
automatically receive focus.If one starts typing, the input goes to nautilus
instead of the terminal and the terminal needs to be selected manually to get
focus.
Steps:
1. right-click in nautilus
2. select "Open in Terminal"
3. A terminal pops up but the prompt is inactive
I gave up on 22.10 because it had the same issue. I thought the issue
would be solved by now but clearly it still exists. Maybe the behaviour
is intended but that feels go against basic UX...
ProblemType: Bug
DistroRelease: Ubuntu 23.04
Package: nautilus 1:44.0-1ubuntu2
ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
Uname: Linux 6.2.0-20-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.26.0-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: GNOME
Date: Thu Apr 13 21:34:46 2023
InstallationDate: Installed on 2022-10-29 (166 days ago)
InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
SourcePackage: nautilus
UpgradeStatus: Upgraded to lunar on 2023-04-12 (1 days ago)
usr_lib_nautilus:
eiciel0.10.0-1
file-roller 43.0-1
nautilus-extension-gnome-terminal 3.48.0-1ubuntu1
python3-nautilus 4.0-1build1
** Affects: nautilus (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug lunar
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/2016182
Title:
terminal opened started from nautilus does not get focus
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2016182/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2006059] Re: gdm requires a second login to start xorg session instead of wayland
** Description changed: I have three accounts and I need all three to run on xorg instead of wayland. - For some reason, two of them consistently start wayland even when I - select plain gnome from the gdm menu. To get xorg, I need to log out and - log in a second time. + For some reason, when switching accounts, two of them consistently start + wayland even when I select plain gnome from the gdm menu. To get xorg, I + need to log out and log in a second time. A solution that is supposed to work consists in customizing /etc/gdm3/custom.conf (see https://docs.fedoraproject.org/en-US/quick- docs/configuring-xorg-as-default-gnome-session/). This solution does not work. I have also experimented with the following options: DefaultSession=gnome-xorg.desktop and PreferredDisplayServer=xorg Neither appears to set xorg as the default... I have found the following bug reported upstream against gdm: https://gitlab.gnome.org/GNOME/gdm/-/issues/733. It looks like this was fixed a year ago but my system is still affected. - - Note that I am using the gnome-session package. I doubt whether it makes any difference but I am adding it for the sake of completeness. + Note that I am using the gnome-session package. I doubt whether it makes + any difference but I am adding it for the sake of completeness. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gdm3 42.0-1ubuntu7 ProcVersionSignature: Ubuntu 6.0.0-1010.10-oem 6.0.9 Uname: Linux 6.0.0-1010-oem x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: GNOME Date: Sun Feb 5 19:44:53 2023 InstallationDate: Installed on 2022-03-27 (315 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.gdm3.custom.conf: 2023-01-30T07:57:48.574915 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/2006059 Title: gdm requires a second login to start xorg session instead of wayland To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/2006059/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2006059] Re: gdm requires a second login to start xorg session instead of wayland
There are not any gdm crash reports in /var/crash. Neither do I find anything gdm related at https://errors.ubuntu.com/. In my journalctl log, I do find this: feb 07 02:29:00 Dapple systemd[53605]: Stopped GNOME Shell on X11. feb 07 02:29:00 Dapple systemd[53605]: Starting GNOME Shell on X11... feb 07 02:29:00 Dapple systemd[53605]: org.gnome.Shell@x11.service: Skipped due to 'exec-condition'. feb 07 02:29:00 Dapple systemd[53605]: Condition check resulted in GNOME Shell on X11 being skipped. That sequence is repeated three times and then X11 appears to be replaced with wayland: feb 07 02:29:00 Dapple gnome-shell[53866]: Running GNOME Shell (using mutter 42.5) as a Wayland display server [...] feb 07 02:29:01 Dapple gnome-shell[53866]: Enabling experimental feature 'x11-randr-fractional-scaling' feb 07 02:29:01 Dapple gnome-shell[53866]: Enabling experimental feature 'scale-monitor-framebuffer' feb 07 02:29:01 Dapple gnome-shell[53866]: Created gbm renderer for '/dev/dri/card0' feb 07 02:29:01 Dapple dbus-daemon[53634]: [session uid=1001 pid=53634] Successfully activated service 'org.gtk.vfs.Metadata' feb 07 02:29:01 Dapple systemd[53605]: Started Virtual filesystem metadata service. feb 07 02:29:01 Dapple gnome-shell[53866]: Disabling DMA buffer screen sharing (implicit modifiers not supported) feb 07 02:29:01 Dapple gnome-shell[53866]: Using public X11 display :2, (using :3 for managed services) feb 07 02:29:01 Dapple gnome-shell[53866]: Using Wayland display name 'wayland-0' [...] feb 07 02:29:12 Dapple systemd[53605]: Started GNOME Shell on Wayland. feb 07 02:29:12 Dapple systemd[53605]: Reached target GNOME Session is initialized. feb 07 02:29:12 Dapple systemd[53605]: GNOME session X11 services is inactive. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/2006059 Title: gdm requires a second login to start xorg session instead of wayland To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/2006059/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2006059] [NEW] gdm requires a second login to start xorg session instead of wayland
Public bug reported: I have three accounts and I need all three to run on xorg instead of wayland. For some reason, two of them consistently start wayland even when I select plain gnome from the gdm menu. To get xorg, I need to log out and log in a second time. A solution that is supposed to work consists in customizing /etc/gdm3/custom.conf (see https://docs.fedoraproject.org/en-US/quick- docs/configuring-xorg-as-default-gnome-session/). This solution does not work. I have also experimented with the following options: DefaultSession=gnome-xorg.desktop and PreferredDisplayServer=xorg Neither appears to set xorg as the default... I have found the following bug reported upstream against gdm: https://gitlab.gnome.org/GNOME/gdm/-/issues/733. It looks like this was fixed a year ago but my system is still affected. Note that I am using the gnome-session package. I doubt whether it makes any difference but I am adding it for the sake of completeness. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gdm3 42.0-1ubuntu7 ProcVersionSignature: Ubuntu 6.0.0-1010.10-oem 6.0.9 Uname: Linux 6.0.0-1010-oem x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: GNOME Date: Sun Feb 5 19:44:53 2023 InstallationDate: Installed on 2022-03-27 (315 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.gdm3.custom.conf: 2023-01-30T07:57:48.574915 ** Affects: gdm3 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy ** Description changed: I have three accounts and I need all three to run on xorg instead of wayland. For some reason, two of them consistently start wayland even when I select plain gnome from the gdm menu. To get xorg, I need to log out and log in a second time. A solution that is supposed to work consists in customizing /etc/gdm3/custom.conf (see https://docs.fedoraproject.org/en-US/quick- docs/configuring-xorg-as-default-gnome-session/). This solution does not work. - I have also experimented with the following options: + I have also experimented with the following options: DefaultSession=gnome-xorg.desktop and PreferredDisplayServer=xorg Neither appears to set xorg as the default... I have found the following bug reported upstream against gdm: - https://gitlab.gnome.org/GNOME/gdm/-/issues/733. + https://gitlab.gnome.org/GNOME/gdm/-/issues/733. It looks like this was fixed a year ago but my system is still affected. + + Note that I am using the gnome-session package. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gdm3 42.0-1ubuntu7 ProcVersionSignature: Ubuntu 6.0.0-1010.10-oem 6.0.9 Uname: Linux 6.0.0-1010-oem x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: GNOME Date: Sun Feb 5 19:44:53 2023 InstallationDate: Installed on 2022-03-27 (315 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.gdm3.custom.conf: 2023-01-30T07:57:48.574915 ** Description changed: I have three accounts and I need all three to run on xorg instead of wayland. For some reason, two of them consistently start wayland even when I select plain gnome from the gdm menu. To get xorg, I need to log out and log in a second time. A solution that is supposed to work consists in customizing /etc/gdm3/custom.conf (see https://docs.fedoraproject.org/en-US/quick- docs/configuring-xorg-as-default-gnome-session/). This solution does not work. I have also experimented with the following options: DefaultSession=gnome-xorg.desktop and PreferredDisplayServer=xorg Neither appears to set xorg as the default... I have found the following bug reported upstream against gdm: https://gitlab.gnome.org/GNOME/gdm/-/issues/733. It looks like this was fixed a year ago but my system is still affected. - Note that I am using the gnome-session package. + + Note that I am using the gnome-session package. I doubt whether it makes any difference but I am adding it for the sake of completeness. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gdm3 42.0-1ubuntu7 ProcVersionSignature: Ubuntu 6.0.0-1010.10-oem 6.0.9 Uname: Linux 6.0.0-1010-oem x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: GNOME Date: Sun Feb 5 19:44:53 2023 InstallationDate: Installed on 2022-03-27 (315 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326) SourcePackage: gdm3
[Bug 1998296] Re: evolution fails to connect to gmail account ("failed to obtain an access token: timeout was reached")
Yes, that seems to fix it. Thank you.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to evolution in Ubuntu.
https://bugs.launchpad.net/bugs/1998296
Title:
evolution fails to connect to gmail account ("failed to obtain an
access token: timeout was reached")
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1998296/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1998296] Re: evolution fails to connect to gmail account ("failed to obtain an access token: timeout was reached")
Probably caused by a GO A bug as described at
https://gitlab.gnome.org/GNOME/evolution/-/issues/2149.
** Bug watch added: gitlab.gnome.org/GNOME/evolution/-/issues #2149
https://gitlab.gnome.org/GNOME/evolution/-/issues/2149
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to evolution in Ubuntu.
https://bugs.launchpad.net/bugs/1998296
Title:
evolution fails to connect to gmail account ("failed to obtain an
access token: timeout was reached")
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1998296/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1998296] [NEW] evolution fails to connect to gmail account ("failed to obtain an access token: timeout was reached")
Public bug reported:
Whenever I start evolution, it displays a red alert bar stating "Failed
to connect "user.n...@gamil.com", reporting as a reason: "Failed to
obtain an access token for "user.n...@gmail.com": Timeout was reached".
The message is cleared when I click the "Reconnect" button displayd on
the bar. My gmail account then works as expected but only as long as
evolution remains opened The next time it is started - even immediately
after closing it - the alert is back.
This is not new. I faced the same issue on the previous LTS version of
Ubuntu once it had been out for just over a year A little research at
the time showed that the default version of evolution was outdated an
needed an upgrade I ended up replacing evolution with thunderbird but
that did not properly integrate with my google calendar, I eventually
saw myself forced to upgrade the whole system to the (then) current non-
LTS release.
I have just installed the flatpak version of the package as it appears
to be a newer version (3.46 over 3.44). I though that might work but it
does not. It auto-detects my gmail account only to display a message
that echoing the one I was already getting: "Failed to open folder. The
reported error was "Failed to authenticate. Timeout was reached."" Mail
is not loading at all.
Evolution is a key part of the gnome desktop so I feel that upgrading
evolution should really be part of regular upgrades.
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: evolution 3.44.4-0ubuntu1
ProcVersionSignature: Ubuntu 5.17.0-1021.22-oem 5.17.15
Uname: Linux 5.17.0-1021-oem x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu82.2
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: GNOME
Date: Wed Nov 30 06:07:02 2022
InstallationDate: Installed on 2022-03-27 (247 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326)
SourcePackage: evolution
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: evolution (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug jammy
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to evolution in Ubuntu.
https://bugs.launchpad.net/bugs/1998296
Title:
evolution fails to connect to gmail account ("failed to obtain an
access token: timeout was reached")
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1998296/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1969896] Re: Evince Document Viewer(42.0) does not remember last page in 22.04
But the flatpak version typically fails to generate thumbnails. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1969896 Title: Evince Document Viewer(42.0) does not remember last page in 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1969896/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1969896] Re: Evince Document Viewer(42.0) does not remember last page in 22.04
I am seeing the same issues. They have to do with apparmor. Preferences do stick when the evince profile is disabled (sudo apparmor_parser -R /etc/apparmor.d/usr.bin.evince). -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1969896 Title: Evince Document Viewer(42.0) does not remember last page in 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1969896/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1969266] Re: application windows frozen after screen blanking
The bug appears to be a theming issue. I have not seen it since I replaced the third party theme I was using with the default. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1969266 Title: application windows frozen after screen blanking To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1969266/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1969266] Re: application windows frozen after screen blanking
** Description changed: - Every time I want to use my computer after the screen has blanked, I - find that the open applications are frozen. + When I want to use my computer after the screen has blanked, I often + (about half of the time) find that the open applications are frozen. I can bring them back to life by restarting X or by cycling through the windows (ALT + TAB). Not a major bug certainly annoying as it is happening time and again. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Apr 16 09:53:51 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-03-27 (19 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326) RelatedPackageVersions: mutter-common 42.0-3ubuntu2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1969266 Title: application windows frozen after screen blanking To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1969266/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1969266] [NEW] application windows frozen after screen blanking
Public bug reported: Every time I want to use my computer after the screen has blanked, I find that the open applications are frozen. I can bring them back to life by restarting X or by cycling through the windows (ALT + TAB). Not a major bug certainly annoying as it is happening time and again. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Apr 16 09:53:51 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-03-27 (19 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326) RelatedPackageVersions: mutter-common 42.0-3ubuntu2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1969266 Title: application windows frozen after screen blanking To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1969266/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1967885] Re: blanking locks screen although screen lock is disabled
Running gsettings with sudo seems to nail it: sudo gsettings set org.gnome.desktop.lockdown disable-lock-screen 'true' But this disables screen locking for every user. That is irrelevant to me but some may care. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1967885 Title: blanking locks screen although screen lock is disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1967885/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1967885] Re: blanking locks screen although screen lock is disabled
-- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1967885 Title: blanking locks screen although screen lock is disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1967885/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1967885] Re: blanking locks screen although screen lock is disabled
Possibly related to bug #1968208, which I reported today: frozen gnome- shell after logging in/unlocking. This new bug would indicate that gnome-shell indeed randomly crashes. The behaviour is inconsistent, though. Sometimes it does not crash at all, at other times it does but it does not always cause the desktop to freeze. I can add a photo, as your requested, but I wonder whether that would add anything. The lock screen is simply the log-in screen that traditionally comes up when the system is booted. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1967885 Title: blanking locks screen although screen lock is disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1967885/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1967885] [NEW] blanking locks screen although screen lock is disabled
Public bug reported: I disabled screen lock from Settings > Privacy > Screen. Even so, I am forced to log in any time my screen has blanked. When I inspect dconf-editor (org.gnome.desktop.lockdown), I see that locking is indeed active. This looks like a discrepancy between the settings mechanism and dconf. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gdm3 42.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Apr 5 16:06:06 2022 InstallationDate: Installed on 2022-03-27 (8 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gdm3 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1967885 Title: blanking locks screen although screen lock is disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1967885/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1955697] [NEW] file-roller fails to extract zip|rar|tar to symlinked directories
Public bug reported: File-roller fails to extract rar, zip, xz and tar archives when 1) the output folder is or is below a symbolic link and 2) extraction is run from the context menu (Extract Here) The typical error message is: "There was an error while extracting ". The file is not a directory." Extraction does work when I 1) navigate to the actual location of the output folder or move the archive(s) to a location that is not a symbolic link or 2) open the archive and run "Extract to" from its menu (which is quite cumbersome when there are dozens of archives to process...). I am dual booting 20.04 and 21.10 with a single home directory (which is where the problematic symlink is located). The issue I am reporting occurs only when I am using 21.10. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: file-roller 3.40.0-2 ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19 Uname: Linux 5.13.0-22-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Dec 24 07:29:37 2021 InstallationDate: Installed on 2021-10-12 (73 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Beta amd64 (20210922) SourcePackage: file-roller UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: file-roller (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish third-party-packages ** Description changed: - File-roller fails to extract rar, zip, xz and tar archives when - 1) the output folder is or is below a symbolic link + File-roller fails to extract rar, zip, xz and tar archives when + 1) the output folder is or is below a symbolic link and 2) extraction is run from the context menu (Extract Here) - The typical error message is: + The typical error message is: "There was an error while extracting ". The file is not a directory." Extraction does work when I - 1) navigate to the actual location of the output folder + 1) navigate to the actual location of the output folder or move the archive(s) to a location that is not a symbolic link or 2) open the archive and run "Extract to" from its menu (that may be fine for a single archive but it is frustrating when there are dozens of archives to process...). I am dual booting 20.04 and 21.10 with a single home directory (which is where the problematic symlink is located). The issue I am reporting occurs only when I am using 21.10. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: file-roller 3.40.0-2 ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19 Uname: Linux 5.13.0-22-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Dec 24 07:29:37 2021 InstallationDate: Installed on 2021-10-12 (73 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Beta amd64 (20210922) SourcePackage: file-roller UpgradeStatus: No upgrade log present (probably fresh install) ** Description changed: File-roller fails to extract rar, zip, xz and tar archives when 1) the output folder is or is below a symbolic link and 2) extraction is run from the context menu (Extract Here) The typical error message is: "There was an error while extracting ". The file is not a directory." Extraction does work when I 1) navigate to the actual location of the output folder or move the archive(s) to a location that is not a symbolic link or - 2) open the archive and run "Extract to" from its menu (that may be fine for a single archive but it is frustrating when there are dozens of archives to process...). + 2) open the archive and run "Extract to" from its menu (which is quite cumbersome when there are dozens of archives to process...). I am dual booting 20.04 and 21.10 with a single home directory (which is where the problematic symlink is located). The issue I am reporting occurs only when I am using 21.10. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: file-roller 3.40.0-2 ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19 Uname: Linux 5.13.0-22-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Dec 24 07:29:37 2021 InstallationDate: Installed on 2021-10-12 (73 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Beta amd64 (20210922) SourcePackage: file-roller UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to file-roller in Ubuntu. https://bugs.launchpad.net/bugs/1955697 Title: file-roller fails to extract zip|rar|tar to symlinked directories To manage notifications about this
[Bug 1954586] Re: login screen freezes when switching users
Using method 2, I have found one (recent) link that refers to an issue affecting gdm3: https://errors.ubuntu.com/oops/10ce3186-5b3e-11ec-88a3-fa163e983629 I hope that this sort of link is what you were asking for; I do not seem to have permission to access its contents so I cannot tell. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1954586 Title: login screen freezes when switching users To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1954586/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1954586] [NEW] login screen freezes when switching users
Public bug reported: Switching users causes the login screen to lock up and the mouse and keyboard to become unresponsive. The order is this: 1) I select "switch user..." from the top bar 2) the login screen pops up and displays the list of users 2) I select my user 4) I enter the password 5) the screen turns black for 2-3 seconds (this is much longer than usual) 6) the login screen pops up again, this time with the text "password" in the input box; the gear in the bottom right corner to select the type of session is missing; the mouse and keyboard are unresponsive 7) I need to reboot I have tried disabling Wayland (uncommented WaylandEnable=false in /etc/gdm3/custom.conf) but that does not make any difference. I do not know whether this may be related, but I have had to disabled the nvidia systemd services because my system failed to suspend until I did (nvidia driver 470). ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: gdm3 41~rc-0ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19 Uname: Linux 5.13.0-22-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Dec 12 12:11:57 2021 InstallationDate: Installed on 2021-10-12 (61 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Beta amd64 (20210922) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gdm3 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish third-party-packages ** Description changed: - Switching users cause the login screen to lock up and the mouse and + Switching users causes the login screen to lock up and the mouse and keyboard to become unresponsive. The order is this: - 1) I select "switch user..." from the top bar + 1) I select "switch user..." from the top bar 2) gdm3 pops up and displays the list of users 2) I select my user - 4) I enter the password - 5) the screen turns black for 2-3 seconds (this is much longer than usual) + 4) I enter the password + 5) the screen turns black for 2-3 seconds (this is much longer than usual) 6) the login screen pops up again, this time with the text "password" in the password input box; at this stage, the mouse and keyboard have become unresponsive 7) I need to reboot I have tried disabling Wayland (uncommented WaylandEnable=false in /etc/gdm3/custom.conf) but that does not make any difference. I do not know whether this may be related, but I have had to disabled the nvidia systemd services because my system failed to suspend until I did (nvidia driver 470). ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: gdm3 41~rc-0ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19 Uname: Linux 5.13.0-22-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Dec 12 12:11:57 2021 InstallationDate: Installed on 2021-10-12 (61 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Beta amd64 (20210922) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) ** Description changed: Switching users causes the login screen to lock up and the mouse and keyboard to become unresponsive. The order is this: 1) I select "switch user..." from the top bar - 2) gdm3 pops up and displays the list of users + 2) the login screen pops up and displays the list of users 2) I select my user 4) I enter the password 5) the screen turns black for 2-3 seconds (this is much longer than usual) - 6) the login screen pops up again, this time with the text "password" in the password input box; at this stage, the mouse and keyboard have become unresponsive + 6) the login screen pops up again, this time with the text "password" in the input box; the gear in the bottom right corner to select the type of session is missing; the mouse and keyboard are unresponsive 7) I need to reboot I have tried disabling Wayland (uncommented WaylandEnable=false in /etc/gdm3/custom.conf) but that does not make any difference. I do not know whether this may be related, but I have had to disabled the nvidia systemd services because my system failed to suspend until I did (nvidia driver 470). ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: gdm3 41~rc-0ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19 Uname: Linux 5.13.0-22-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Dec 12 12:11:57 2021 InstallationDate: Installed on 2021-10-12 (61 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Beta amd64 (20210922) SourcePackage: gdm3 UpgradeStatus: No upgrade log
[Bug 1881458] Re: Playback aborts when a download is started, printing "server does not support seeking"
Well... I just find that mp3 streams work just as fine. Most likely a kernel thing, then. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/1881458 Title: Playback aborts when a download is started, printing "server does not support seeking" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1881458/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1881458] Re: Playback aborts when a download is started, printing "server does not support seeking"
I think this ticket can be closed, at least for now. Since I replaced all my mp3 format streams with aac streams, I have not experienced as much as a stutter. Then again, for all I know, the actual reason may be a recent be a kernel update... Anyway, thanks for your assistance! -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/1881458 Title: Playback aborts when a download is started, printing "server does not support seeking" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1881458/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1881458] Re: Playback aborts when a download is started, printing "server does not support seeking"
The URI you put up plays fine. Unfortunately, I ran into the same issue when I started a different stream. There were a few short skips at first but the player came back. Then it suddenly gave up completely with the error message mentioned in my opening post. I am including the log file. The issue appears to show up in lines 8492-8493. The lines further down show a recurring pattern so I assume that the player is stuck in a loop that prevents it from resuming. ** Attachment added: "rhythmbox.log" https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1881458/+attachment/5385346/+files/rhythmbox.log -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/1881458 Title: Playback aborts when a download is started, printing "server does not support seeking" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1881458/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1881458] [NEW] Playback aborts when a download is started, printing "server does not support seeking"
Public bug reported: Whenever heavy traffic starts on my network, Rhythmbox will abruptly stop playing audio streams. The traffic in question may be local data transfer or (mostly large) downloads. The same happens to local audio streams managed by pulseaudio. A data transfer starts and the stream very much immediately cuts out. Typically, rhythmbox will pops up a dialog saying "server does not support seeking". I can usually resume playback but during longer data transfers/downloads, it will frequently cut out again. I have tried replacing the onboard audio chip with a discrete ASUS DX card. This does not make any difference. What does work is manually restricting download speeds using a download manager. However,, not all network traffic is controlled by such a manager. Something trivial - say, installing a firefox or a gnome-shell plug-in - has been enough for an audio stream to die instantly. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: rhythmbox 3.4.4-1ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun May 31 05:06:56 2020 ExecutablePath: /usr/bin/rhythmbox InstallationDate: Installed on 2020-04-05 (55 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) SourcePackage: rhythmbox UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: rhythmbox (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal third-party-packages ** Description changed: Whenever heavy traffic starts on my network, Rhythmbox will abruptly stop playing audio streams. The traffic in question may be local data transfer or (mostly large) downloads. The same happens to local audio streams managed by pulseaudio. A data transfer starts and the stream very much immediately cuts out. Typically, rhythmbox will pops up a dialog saying "server does not support seeking". I can usually resume playback but during longer data transfers/downloads, it will frequently cut out again. I have tried replacing the onboard audio chip with a discrete ASUS DX card. This does not make any difference. What does work is manually restricting download speeds using a download manager. However,, not all network traffic is controlled by such a - manager. Something trivial like installing a firefox or a gnome-shell - plug-in can be enough to interrupt playback. + manager. Something trivial - say, installing a firefox or a gnome-shell + plug-in - has been enough for an audio stream to die instantly. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: rhythmbox 3.4.4-1ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun May 31 05:06:56 2020 ExecutablePath: /usr/bin/rhythmbox InstallationDate: Installed on 2020-04-05 (55 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) SourcePackage: rhythmbox UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/1881458 Title: Playback aborts when a download is started, printing "server does not support seeking" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1881458/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
