[Bug 2054761] Re: Dist upgrades from Jammy to Noble crash [Oh no! Something has gone wrong.]
The autopkgtest regressions were all resolved with retries. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2054761 Title: Dist upgrades from Jammy to Noble crash [Oh no! Something has gone wrong.] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2054761/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2054761] Re: Dist upgrades from Jammy to Noble crash [Oh no! Something has gone wrong.]
I have verified the fix using systemd 255.4-1ubuntu8.1 from noble- proposed. On a Jammy Desktop system, I simply ran an upgrade: nr@clean-jammy-amd64:~$ wget http://archive.ubuntu.com/ubuntu/dists/noble-proposed/main/dist-upgrader-all/24.04.18/noble.tar.gz --2024-05-22 11:45:16-- http://archive.ubuntu.com/ubuntu/dists/noble-proposed/main/dist-upgrader-all/24.04.18/noble.tar.gz Resolving archive.ubuntu.com (archive.ubuntu.com)... 91.189.91.82, 185.125.190.36, 91.189.91.83, ... Connecting to archive.ubuntu.com (archive.ubuntu.com)|91.189.91.82|:80... connected. HTTP request sent, awaiting response... 200 OK Length: 1274850 (1.2M) [application/x-gzip] Saving to: \u2018noble.tar.gz\u2019 noble.tar.gz100%[===>] 1.21M --.-KB/sin 0.1s 2024-05-22 11:45:16 (9.20 MB/s) - \u2018noble.tar.gz\u2019 saved [1274850/1274850] nr@clean-jammy-amd64:~$ tar xf noble.tar.gz nr@clean-jammy-amd64:~$ sudo -E ./noble --frontend DistUpgradeViewNonInteractive [ ... ] The upgrade proceeded without issue. Namely, my session was not killed during the upgrade. nr@clean-jammy-amd64:~$ apt policy systemd systemd: Installed: 255.4-1ubuntu8.1 Candidate: 255.4-1ubuntu8.1 Version table: *** 255.4-1ubuntu8.1 500 500 http://archive.ubuntu.com/ubuntu noble-proposed/main amd64 Packages 100 /var/lib/dpkg/status 255.4-1ubuntu8 500 500 http://archive.ubuntu.com/ubuntu noble/main amd64 Packages ** Tags removed: verification-needed-noble ** Tags added: verification-done-noble -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2054761 Title: Dist upgrades from Jammy to Noble crash [Oh no! Something has gone wrong.] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2054761/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2054761] Re: Dist upgrades from Jammy to Noble crash [Oh no! Something has gone wrong.]
This is not a problem for oracular, because no supported upgrade paths to oracular would have an old enough systemd to hit this. ** Also affects: mutter (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: gnome-shell (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Noble) Importance: Undecided Status: New ** Changed in: systemd (Ubuntu Noble) Status: New => In Progress ** Changed in: systemd (Ubuntu Noble) Importance: Undecided => High ** Changed in: systemd (Ubuntu Noble) Assignee: (unassigned) => Nick Rosbrook (enr0n) ** Changed in: systemd (Ubuntu) Status: Triaged => Invalid -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2054761 Title: Dist upgrades from Jammy to Noble crash [Oh no! Something has gone wrong.] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2054761/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2054761] Re: Dist upgrades from Jammy to Noble crash [Oh no! Something has gone wrong.]
** Description changed: + [Impact] + During upgrades from Jammy to Noble, systemd.postinst trys to reexec all running user managers. It does so using a feature that was not added until v250, and attempting this against a v249 daemon results in it being killed instead, which brings down all user sessions. + + Hence, during the upgrades, the user session is killed, and the system + is left in a bad state. + + [Test Plan] + + Run an upgrade from Jammy to Noble on Ubuntu desktop. The upgrade should + proceed normally (or at least not have the entire session killed by + systemd.postinst). + + [Where problems could occur] + + The fix is to add a version guard against this logic in + systemd.postinst. If the version string was wrong or typo'd, the fix + would not work as expected. + + [Original Description] + Feb 21 21:39:12 autopkgtest gnome-shell[17945]: Settings schema 'org.gnome.mutter.wayland' does not contain a key named 'xwayland-allow-byte-swapped-clients' Feb 21 21:39:12 autopkgtest gnome-session-binary[17908]: WARNING: Application 'org.gnome.Shell.desktop' killed by signal 5 Feb 21 21:39:12 autopkgtest gnome-shell[17959]: Settings schema 'org.gnome.mutter.wayland' does not contain a key named 'xwayland-allow-byte-swapped-clients' Feb 21 21:39:12 autopkgtest gnome-session-binary[17908]: WARNING: Application 'org.gnome.Shell.desktop' killed by signal 5 https://errors.ubuntu.com/problem/bf714caff944bed915a3c4321664107c65547d1f https://errors.ubuntu.com/problem/db8f7e3dfc79e658b9b2aa8c596b014ce4b9f217 https://errors.ubuntu.com/oops/af2e99fc-d101-11ee-8a58-fa163ec8ca8c -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2054761 Title: Dist upgrades from Jammy to Noble crash [Oh no! Something has gone wrong.] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2054761/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2054761] Re: gnome-shell crashed with signal 5: Settings schema 'org.gnome.mutter.wayland' does not contain a key named 'xwayland-allow-byte-swapped-clients'
I believe I figured out what is happening here. In systemd v250, systemd user managers began interpreting the signal RTMIN+25 as a command to daemon-reexec. This was done so that: systemctl kill --kill-whom='main' --signal='SIGRTMIN+25' 'user@*.service' could be used as a way to reexec all user instances at once. So, systemd.postinst now contains such a line so that user managers are also reexec'd during package upgrades. However, since Jammy is running systemd v249, the running user manager at the time of the upgrade does not have this reexec logic, and appears to behave as if it were killed normally. So, the fix should be to not attempt to restart all the user managers if the old version is too old. ** Changed in: systemd (Ubuntu) Importance: Undecided => High ** Changed in: systemd (Ubuntu) Assignee: (unassigned) => Nick Rosbrook (enr0n) ** Changed in: systemd (Ubuntu) Status: New => Triaged ** Tags added: systemd-sru-next -- 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/2054761 Title: gnome-shell crashed with signal 5: Settings schema 'org.gnome.mutter.wayland' does not contain a key named 'xwayland- allow-byte-swapped-clients' To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2054761/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2055012] Re: When I upgraded from 22.04 to 24.04, DNS resolution went wrong.
*** This bug is a duplicate of bug 2054761 *** https://bugs.launchpad.net/bugs/2054761 Adding my journal from the crash. ** Attachment added: "journal.txt" https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2055012/+attachment/5769751/+files/journal.txt -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/2055012 Title: When I upgraded from 22.04 to 24.04, DNS resolution went wrong. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2055012/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2055012] Re: When I upgraded from 22.04 to 24.04, DNS resolution went wrong.
*** This bug is a duplicate of bug 2054761 *** https://bugs.launchpad.net/bugs/2054761 The problem is that gnome-shell crashes during the upgrade, so packages including systemd-resolved never finish getting installed. Marking as a duplicate of bug 2054761. ** This bug has been marked a duplicate of bug 2054761 gnome-shell crashed with signal 5: Settings schema 'org.gnome.mutter.wayland' does not contain a key named 'xwayland-allow-byte-swapped-clients' -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/2055012 Title: When I upgraded from 22.04 to 24.04, DNS resolution went wrong. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2055012/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2055012] Re: When I upgraded from 22.04 to 24.04, DNS resolution went wrong.
** Changed in: ubuntu-release-upgrader (Ubuntu) Importance: Undecided => Critical -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/2055012 Title: When I upgraded from 22.04 to 24.04, DNS resolution went wrong. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2055012/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2055012] Re: When I upgraded from 22.04 to 24.04, DNS resolution went wrong.
I attempted an upgrade from a clean Jammy install to Noble so that I could gather upgrade logs. I have attached them here. ** Attachment added: "dist-upgrade.tar.gz" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2055012/+attachment/5769726/+files/dist-upgrade.tar.gz ** Also affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/2055012 Title: When I upgraded from 22.04 to 24.04, DNS resolution went wrong. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2055012/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2061696] Re: Trying to setup a google account in settings
** Package changed: ubuntu-release-upgrader (Ubuntu) => gnome-control- center (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/2061696 Title: Trying to setup a google account in settings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2061696/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1162475] Re: [hostnamed] Changing hostname doesn't update /etc/hosts
** Changed in: systemd (Ubuntu) Status: Triaged => Won't Fix -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1162475 Title: [hostnamed] Changing hostname doesn't update /etc/hosts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1162475/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1911137] Re: alt-tab not working after left mouse click
I do see this behavior on Focal still, but I don't think systemd is the correct package. ** Package changed: systemd (Ubuntu) => gnome-shell (Ubuntu) -- 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/1911137 Title: alt-tab not working after left mouse click To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1911137/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1965219] Re: gnome lock screen does not permit reentering password
** Changed in: systemd (Ubuntu) Importance: Undecided => Low -- 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/1965219 Title: gnome lock screen does not permit reentering password To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1965219/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1882034] Re: cannot start X session with NIS account
Marking invalid for systemd due to age, and it being unclear whether this is in fact a systemd bug. ** Changed in: systemd (Ubuntu) Status: Incomplete => Invalid -- 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/1882034 Title: cannot start X session with NIS account To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1882034/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 192330] Re: [wish] extract multipart files zip archive
** Changed in: unzip (Ubuntu) Importance: Undecided => Wishlist -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. https://bugs.launchpad.net/bugs/192330 Title: [wish] extract multipart files zip archive To manage notifications about this bug go to: https://bugs.launchpad.net/file-roller/+bug/192330/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1995199] Re: Renaming home folders corrupts side panel behavior
Thank you for the description. I use Wayland, tried to rename "Downloads". By the way, when renaming "Downloads" at side panel to longer string then side panel extends appropriately. But panel's width can not be changed and folder names do not wrap, it looks too wide. ** Attachment added: "Screenshot from 2022-11-04 15-42-44.png" https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1995199/+attachment/5629159/+files/Screenshot%20from%202022-11-04%2015-42-44.png -- 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/1995199 Title: Renaming home folders corrupts side panel behavior To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1995199/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1995199] [NEW] Renaming home folders corrupts side panel behavior
Public bug reported: Hi! Renamed home folder is not synchronized with side panel. So, side panel's link does not work after renaming home folders. Expected, opening renamed folder from side panel. Due to lack of customization of side panel, links can not be changed to the new renamed location. It is not only my opinion that the side panel must have more customization features, including resizing and disabling it. Ubuntu 22.10 5.19.0-23-generic nautilus-data/kinetic,kinetic,now 1:43.0-1ubuntu1 all [installed,automatic] nautilus-extension-gnome-terminal/kinetic,now 3.46.2-1ubuntu1 amd64 [installed,automatic] nautilus/kinetic,now 1:43.0-1ubuntu1 amd64 [installed,automatic] ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Screenshot from 2022-10-30 10-18-07.png" https://bugs.launchpad.net/bugs/1995199/+attachment/5627830/+files/Screenshot%20from%202022-10-30%2010-18-07.png -- 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/1995199 Title: Renaming home folders corrupts side panel behavior To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1995199/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1988488] Re: Screen freeze at the moment of login
** This bug is no longer a duplicate of bug 1988473 [SRU] VirtualBox 6.1.34 guests crash with kernel 5.15.0-47 ** Package changed: systemd (Ubuntu) => gdm3 (Ubuntu) ** Changed in: gdm3 (Ubuntu) Status: Confirmed => New -- 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/1988488 Title: Screen freeze at the moment of login To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1988488/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1986850] Re: Manual proxy is partially cleared on 20.04 => 22.04 upgrade
I don't believe this is related to any ubuntu-release-upgrader logic. I will re-assign the bug to gnome-control-center since it sounds like that's where you're configuring your proxy. ** Package changed: ubuntu-release-upgrader (Ubuntu) => gnome-control- center (Ubuntu) ** Changed in: ubuntu-release-upgrader Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1986850 Title: Manual proxy is partially cleared on 20.04 => 22.04 upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-upgrader/+bug/1986850/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1987225] Re: I open tweaks, set my icons to Breathe. Then I go to settings for something and my icons are rest to default icons
** Package changed: ubuntu-release-upgrader (Ubuntu) => gnome-control- center (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1987225 Title: I open tweaks, set my icons to Breathe. Then I go to settings for something and my icons are rest to default icons To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1987225/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1986510] Re: No settings options for "Dock" under setting>>appearance
** Package changed: ubuntu-release-upgrader (Ubuntu) => gnome-control- center (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1986510 Title: No settings options for "Dock" under setting>>appearance To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1986510/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1983456] Re: Context menu options are shown under dock panel and can not be chosen on Ubuntu 22.04
** Description changed: 1. Ubuntu 22.04.1 LTS 2. Installed packeges: ... gnome-shell-common/jammy-updates,jammy-updates,now 42.2-0ubuntu0.2 all [installed,automatic] gnome-shell-extension-appindicator/jammy,jammy,now 42-2~fakesync1 all [installed,automatic] gnome-shell-extension-desktop-icons-ng/jammy-updates,jammy-updates,now 43-2ubuntu1 all [installed,automatic] gnome-shell-extension-ubuntu-dock/jammy-updates,jammy-updates,now 72~ubuntu5.22.04.1 all [installed,automatic] gnome-shell/jammy-updates,now 42.2-0ubuntu0.2 amd64 [installed,automatic] 3. Expected to choose "Property" option in right-click context menu of a folder in file manager. 4. In some position of file manager's window near middle to bottom of the screen, the context menu was shown under dock panel without possibility to choose options, the dock hides menu. - - *On Ubuntu 20.04 the menu is shown upon the dock panel, so all options - can be chosen. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1983456 Title: Context menu options are shown under dock panel and can not be chosen on Ubuntu 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1983456/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1983456] Re: Context menu options are shown under dock panel and can not be chosen on Ubuntu 22.04
Thank you for quick response. * My dock set to auto-hide. * I am using Wayland. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1983456 Title: Context menu options are shown under dock panel and can not be chosen on Ubuntu 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1983456/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1983456] [NEW] Context menu options are shown under dock panel and can not be chosen on Ubuntu 22.04
Public bug reported: 1. Ubuntu 22.04.1 LTS 2. Installed packeges: ... gnome-shell-common/jammy-updates,jammy-updates,now 42.2-0ubuntu0.2 all [installed,automatic] gnome-shell-extension-appindicator/jammy,jammy,now 42-2~fakesync1 all [installed,automatic] gnome-shell-extension-desktop-icons-ng/jammy-updates,jammy-updates,now 43-2ubuntu1 all [installed,automatic] gnome-shell-extension-ubuntu-dock/jammy-updates,jammy-updates,now 72~ubuntu5.22.04.1 all [installed,automatic] gnome-shell/jammy-updates,now 42.2-0ubuntu0.2 amd64 [installed,automatic] 3. Expected to choose "Property" option in right-click context menu of a folder in file manager. 4. In some position of file manager's window near middle to bottom of the screen, the context menu was shown under dock panel without possibility to choose options, the dock hides menu. *On Ubuntu 20.04 the menu is shown upon the dock panel, so all options can be chosen. ** Affects: gnome-shell-extension-ubuntu-dock (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Screenshot from 2022-08-03 11-35-43.png" https://bugs.launchpad.net/bugs/1983456/+attachment/5606646/+files/Screenshot%20from%202022-08-03%2011-35-43.png -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1983456 Title: Context menu options are shown under dock panel and can not be chosen on Ubuntu 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1983456/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1972812] Re: The operating system does not ask for a password after unlocking the screen.
Hi, I didn't see the same problem as mine at https://errors.ubuntu.com/user/79a8c2c9b8e3ae7f68e16547e26ac4ad39c73d24cdc52a0d0f6a76e10652499f128832ff3f331727c271478d5d0afcf33c4c29e15f55387b5ac7045106358e3c I attach the result the command journalctl -b0 > journal.txt ** Attachment added: "journal.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1972812/+attachment/5589544/+files/journal.txt -- 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/1972812 Title: The operating system does not ask for a password after unlocking the screen. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1972812/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1972812] Re: The operating system does not ask for a password after unlocking the screen.
Hi, @Daniel van Vugt (vanvugt), I give you a report. I have been rebooted my laptop and repeated the problem again, but I didn't find a file *.crash in /var/crash directory. Apparently, the problem is not crash (it's my opinion), because Operation System does't show error messages on my screen, so I can't use ubuntu-bug command -- 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/1972812 Title: The operating system does not ask for a password after unlocking the screen. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1972812/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1972812] Re: The operating system does not ask for a password after unlocking the screen.
Hello. I don't have installed extensions. i added a screenshot. ** Attachment added: "gnome-shell.png" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1972812/+attachment/5588740/+files/gnome-shell.png -- 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/1972812 Title: The operating system does not ask for a password after unlocking the screen. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1972812/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1968144] Re: Appearance options not available in settings after upgrading from Ubuntu 21.10 to Ubuntu 22.04
** Package changed: ubuntu-release-upgrader (Ubuntu) => gnome-control- center (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1968144 Title: Appearance options not available in settings after upgrading from Ubuntu 21.10 to Ubuntu 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1968144/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1885953] Re: color-cc-panel calls gcm-calibrate which was removed from package
Still an issue in 21.10. And probably a duplicate of https://bugs.launchpad.net/ubuntu/+source/gnome-color- manager/+bug/862992 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1885953 Title: color-cc-panel calls gcm-calibrate which was removed from package To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1885953/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1966317] Re: gvfsd-fuse crashed with SIGABRT in __pthread_setname_np()
*** This bug is a duplicate of bug 1962036 *** https://bugs.launchpad.net/bugs/1962036 ** This bug has been marked a duplicate of bug 1962036 dbus was stopped during today's jammy update, breaking desktop -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1966317 Title: gvfsd-fuse crashed with SIGABRT in __pthread_setname_np() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1966317/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1871538] Re: dbus timeout-ed during an upgrade, taking services down including gdm
** Tags removed: verification-needed verification-needed-focal verification-needed-impish ** Tags added: verification-done verification-done-focal verification-done-impish -- 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/1871538 Title: dbus timeout-ed during an upgrade, taking services down including gdm To manage notifications about this bug go to: https://bugs.launchpad.net/dbus/+bug/1871538/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1871538] Re: dbus timeout-ed during an upgrade, taking services down including gdm
The autopkgtest regressions blocking systemd 248.3-1ubuntu8.5 in impish- proposed have been resolved. The regressions were caused either by (1) network/infrastructure issues and succeeded on retry, or by (2) unrelated snapd regressions. The systemd 248.3-1ubuntu8.5 upload added an autopkgtest change for systemd to ignore failed snap mount units which are caused by unrelated snapd issues. -- 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/1871538 Title: dbus timeout-ed during an upgrade, taking services down including gdm To manage notifications about this bug go to: https://bugs.launchpad.net/dbus/+bug/1871538/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1871538] Re: dbus timeout-ed during an upgrade, taking services down including gdm
The autopkgtest regressions blocking systemd 245.4-4ubuntu3.16 in focal- proposed have been resolved. The regressions appear to have been related to recent autopkgtest infrastructure issues, and retrying the tests resolved the issues. -- 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/1871538 Title: dbus timeout-ed during an upgrade, taking services down including gdm To manage notifications about this bug go to: https://bugs.launchpad.net/dbus/+bug/1871538/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1966317] Re: gvfsd-fuse crashed with SIGABRT in __pthread_setname_np()
I think this is causing bug 1965652. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1966317 Title: gvfsd-fuse crashed with SIGABRT in __pthread_setname_np() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1966317/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1966317] [NEW] gvfsd-fuse crashed with SIGABRT in __pthread_setname_np()
Public bug reported: I encountered this crash during a dist-upgrade from impish to jammy, i.e. running `do-release-upgrade --devel-release`. My desktop session crashed, and my VM can no longer boot the desktop (but I can ssh still). ProblemType: Crash DistroRelease: Ubuntu 21.10 Package: gvfs-fuse 1.47.91-1ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-28.31-generic 5.13.19 Uname: Linux 5.13.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckMismatches: ./boot/grub/grub.cfg CasperMD5CheckResult: fail Date: Thu Mar 24 12:10:04 2022 ExecutablePath: /usr/libexec/gvfsd-fuse ExecutableTimestamp: 1615801987 InstallationDate: Installed on 2022-02-02 (49 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) ProcCmdline: /usr/libexec/gvfsd-fuse /run/user/1000/gvfs -f -o big_writes ProcCwd: /home/nr ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= Signal: 6 SourcePackage: gvfs StacktraceTop: __pthread_setname_np (th=1251, name=0x6 ) at ./nptl/pthread_setname.c:32 ?? () Title: gvfsd-fuse crashed with SIGABRT in __pthread_setname_np() UpgradeStatus: Upgraded to impish on 2022-03-24 (0 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: ** Affects: gvfs (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash impish need-amd64-retrace third-party-packages ** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1966317 Title: gvfsd-fuse crashed with SIGABRT in __pthread_setname_np() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1966317/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1960857] Re: gdm3 self-enables during upgrade
Oh also maybe this would be handy, I use etckeeper(8) with unattended- upgrades(8) so I can show you that the change happened when gdm went from 3.36.3-0ubuntu0.20.04.3 -> 3.36.3-0ubuntu0.20.04.4: root@romane:~# etckeeper vcs log fea52b81f4bbc9c171206a56a4d53087bf82b82d~..fea52b81f4bbc9c171206a56a4d53087bf82b82d commit fea52b81f4bbc9c171206a56a4d53087bf82b82d Author: root Date: Thu Feb 10 06:25:28 2022 -0500 committing changes in /etc made by "/usr/bin/python3 /usr/bin/unattended-upgrade" Package changes: +aptdaemon-data 1.1.1+bzr982-0ubuntu32.3 all -avahi-daemon 0.7-4ubuntu7 amd64 +avahi-daemon 0.7-4ubuntu7.1 amd64 +avahi-utils 0.7-4ubuntu7.1 amd64 -bluez 5.53-0ubuntu3.1 amd64 +bluez 5.53-0ubuntu3.5 amd64 +cheese-common 3.34.0-1ubuntu1 all +colord-data 1.4.4-2 all +dconf-cli 0.36.0-1 amd64 -evolution-data-server 3.36.4-0ubuntu1 amd64 +evolution-data-server 3.36.5-0ubuntu1 amd64 +evolution-data-server-common 3.36.5-0ubuntu1 all -fprintd 1.90.1-1ubuntu1 amd64 +fprintd 1.90.9-1~ubuntu20.04.1 amd64 +gcr 3.36.0-2build1 amd64 -gdm3 3.36.3-0ubuntu0.20.04.3 amd64 +gdm3 3.36.3-0ubuntu0.20.04.4 amd64 +gir1.2-accountsservice-1.0 0.6.55-0ubuntu12~20.04.5 amd64 +gir1.2-atk-1.0 2.35.1-1ubuntu2 amd64 +gir1.2-atspi-2.0 2.36.0-2 amd64 +gir1.2-freedesktop 1.64.1-1~ubuntu20.04.1 amd64 +gir1.2-gck-1 3.36.0-2build1 amd64 +gir1.2-gcr-3 3.36.0-2build1 amd64 +gir1.2-gdesktopenums-3.0 3.36.0-1ubuntu1 amd64 +gir1.2-gdkpixbuf-2.0 2.40.0+dfsg-3ubuntu0.2 amd64 +gir1.2-gdm-1.0 3.36.3-0ubuntu0.20.04.4 amd64 +gir1.2-geoclue-2.0 2.5.6-0ubuntu1 amd64 +gir1.2-gnomebluetooth-1.0 3.34.3-0ubuntu1 amd64 +gir1.2-gnomedesktop-3.0 3.36.8-0ubuntu1 amd64 +gir1.2-graphene-1.0 1.10.0-1build2 amd64 +gir1.2-gtk-3.0 3.24.20-0ubuntu1 amd64 +gir1.2-gweather-3.0 3.36.1-1~ubuntu20.04.1 amd64 +gir1.2-ibus-1.0 1.5.22-2ubuntu2.1 amd64 +gir1.2-json-1.0 1.4.4-2ubuntu2 amd64 +gir1.2-mutter-6 3.36.9-0ubuntu0.20.04.2 amd64 +gir1.2-nm-1.0 1.22.10-1ubuntu2.3 amd64 +gir1.2-nma-1.0 1.8.24-1ubuntu3 amd64 +gir1.2-notify-0.7 0.7.9-1ubuntu2 amd64 +gir1.2-packagekitglib-1.0 1.1.13-2ubuntu1.1 amd64 +gir1.2-pango-1.0 1.44.7-2ubuntu4 amd64 +gir1.2-polkit-1.0 0.105-26ubuntu1.2 amd64 +gir1.2-rsvg-2.0 2.48.9-1ubuntu0.20.04.1 amd64 +gir1.2-secret-1 0.20.4-0ubuntu1 amd64 +gir1.2-soup-2.4 2.70.0-1 amd64 +gir1.2-upowerglib-1.0 0.99.11-1build2 amd64 +gir1.2-vte-2.91 0.60.3-0ubuntu1~20.04 amd64 +gjs 1.64.5-0ubuntu0.20.04.01 amd64 +gkbd-capplet 3.26.1-1 amd64 -gnome-control-center-data 1:3.36.5-0ubuntu1 all +gnome-control-center 1:3.36.5-0ubuntu3 amd64 +gnome-control-center-data 1:3.36.5-0ubuntu3 all +gnome-control-center-faces 1:3.36.5-0ubuntu3 all +gnome-desktop3-data 3.36.8-0ubuntu1 all +gnome-keyring-pkcs11 3.36.0-1ubuntu1 amd64 +gnome-online-accounts 3.36.1-0ubuntu1 amd64 +gnome-session-bin 3.36.0-2ubuntu1 amd64 -gnome-settings-daemon 3.36.1-0ubuntu1 amd64 -gnome-shell 3.36.7-0ubuntu0.20.04.1 amd64 +gnome-settings-daemon 3.36.1-0ubuntu1.1 amd64 +gnome-settings-daemon-common 3.36.1-0ubuntu1.1 all +gnome-shell 3.36.9-0ubuntu0.20.04.2 amd64 +gnome-shell-common 3.36.9-0ubuntu0.20.04.2 all +gnome-startup-applications 3.36.0-2ubuntu1 amd64 +gnome-user-docs 3.36.2+git20200704-0ubuntu0.1 all +gstreamer1.0-clutter-3.0 3.0.27-1 amd64 +gstreamer1.0-plugins-base 1.16.2-4ubuntu0.1 amd64 +gstreamer1.0-plugins-good 1.16.2-1ubuntu2.1 amd64 +gstreamer1.0-x 1.16.2-4ubuntu0.1 amd64 +ibus-data 1.5.22-2ubuntu2.1 all +ibus-gtk 1.5.22-2ubuntu2.1 amd64 +ibus-gtk3 1.5.22-2ubuntu2.1 amd64 +language-selector-gnome 0.204.2 all +libaa1 1.4p5-46 amd64 +libappindicator3-1 12.10.1+20.04.20200408.1-0ubuntu1 amd64 +libappstream4 0.12.10-2 amd64 +libasyncns0 0.8-6 amd64 +libavahi-core7 0.7-4ubuntu7.1 amd64 +libavahi-glib1 0.7-4ubuntu7.1 amd64 +libavc1394-0 0.5.4-5 amd64 +libbluetooth3 5.53-0ubuntu3.5 amd64 +libcaca0 0.99.beta19-2.1ubuntu1.20.04.2 amd64 +libcamel-1.2-62 3.36.5-0ubuntu1 amd64 +libcanberra-gtk3-0 0.30-7ubuntu1 amd64 +libcanberra-gtk3-module 0.30-7ubuntu1 amd64 +libcanberra-pulse 0.30-7ubuntu1 amd64 +libcdparanoia0 3.10.2+debian-13 amd64 +libcheese-gtk25 3.34.0-1ubuntu1 amd64 +libcheese8 3.34.0-1ubuntu1 amd64 +libclutter-1.0-0 1.26.4+dfsg-1 amd64 +libclutter-1.0-common 1.26.4+dfsg-1 all +libclutter-gst-3.0-0 3.0.27-1 amd64 +libclutter-gtk-1.0-0 1.8.4-4 amd64 +libcogl-common 1.22.6-1 all +libcogl-pango20 1.22.6-1 amd64 +libcogl-path20 1.22.6-1 amd64 +libcogl20 1.22.6-1 amd64 +libcolord-gtk1 0.2.0-0ubuntu1 amd64 +libcolorhug2 1.4.4-2 amd64 +libdaemon0 0.14-7 amd64 +libdbusmenu-glib4 16.04.1+18.10.20180917-0ubuntu6 amd64 +libdbusmenu-gtk3-4 16.04.1+18.10.20180917-0ubuntu6 amd64 +libdv4
[Bug 1960857] [NEW] gdm3 self-enables during upgrade
Public bug reported: I've been running Ubuntu 20.04 LTS on some servers for a while. This week, they started going non-responsive. Plugging in monitors and keyboards to them, I found they had gone to sleep, and waking them up showed the purple gdm login screen. Before, they've always just had my good friend getty showing a black and white "login: " prompt. Watching their behaviour for about an hour, I found the suspends were happening at 20 minute intervals, which is gdm's default sleep timer, so I'm reasonably confident my downtime problem was because gdm had self- activated unexpectedly. I checked my logs and found that unattended-upgrades had installed a new version overnight. I'd never noticed I even had gdm3 installed because it was never active before, and I'm still working out why that is, and I've disabled and purged it, but regardless I am surprised that the upgrade self-activated it like that without my consent. I would like to ask that gdm3's configure script takes account of the current `service enable`/`service disable`/`systemctl enable`/`systemctl disable` state, if it's not already doing that. Or, just don't touch `service` at all during an upgrade. During an install is fine, but please not during an upgrade. Here's version details from the two servers I've seen this on so far: root@romane:~# lsb_release -rd Description:Ubuntu 20.04.3 LTS Release:20.04 root@romane:~# apt-cache policy gdm3 gdm3: Installed: (none) Candidate: 3.36.3-0ubuntu0.20.04.4 Version table: 3.36.3-0ubuntu0.20.04.4 500 500 http://ca.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 3.36.3-0ubuntu0.20.04.2 500 500 http://ca.archive.ubuntu.com/ubuntu focal-security/main amd64 Packages 3.34.1-1ubuntu1 500 500 http://ca.archive.ubuntu.com/ubuntu focal/main amd64 Packages root@rosenberg:~# lsb_release -rd Description:Ubuntu 20.04.3 LTS Release:20.04 root@rosenberg:~# apt-cache policy gdm3 gdm3: Installed: 3.36.3-0ubuntu0.20.04.4 Candidate: 3.36.3-0ubuntu0.20.04.4 Version table: *** 3.36.3-0ubuntu0.20.04.4 500 500 http://ca.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.36.3-0ubuntu0.20.04.2 500 500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages 3.34.1-1ubuntu1 500 500 http://ca.archive.ubuntu.com/ubuntu focal/main amd64 Packages Here's the relevant upgrade logs from the two: root@romane:~# grep 2022-02-10 /var/log/dpkg.log | grep gdm3 2022-02-10 06:22:56 install gdm3:amd64 3.36.3-0ubuntu0.20.04.3 3.36.3-0ubuntu0.20.04.4 2022-02-10 06:22:56 status half-installed gdm3:amd64 3.36.3-0ubuntu0.20.04.3 2022-02-10 06:22:56 status unpacked gdm3:amd64 3.36.3-0ubuntu0.20.04.4 2022-02-10 06:25:01 configure gdm3:amd64 3.36.3-0ubuntu0.20.04.4 2022-02-10 06:25:01 status unpacked gdm3:amd64 3.36.3-0ubuntu0.20.04.4 2022-02-10 06:25:01 status half-configured gdm3:amd64 3.36.3-0ubuntu0.20.04.4 2022-02-10 06:25:02 status installed gdm3:amd64 3.36.3-0ubuntu0.20.04.4 root@rosenberg:~# grep 2022-02-13 /var/log/dpkg.log | grep gdm3 2022-02-13 06:08:05 install gdm3:amd64 3.36.3-0ubuntu0.20.04.4 2022-02-13 06:08:05 status half-installed gdm3:amd64 3.36.3-0ubuntu0.20.04.4 2022-02-13 06:08:06 status unpacked gdm3:amd64 3.36.3-0ubuntu0.20.04.4 2022-02-13 06:11:52 configure gdm3:amd64 3.36.3-0ubuntu0.20.04.4 2022-02-13 06:11:52 status unpacked gdm3:amd64 3.36.3-0ubuntu0.20.04.4 2022-02-13 06:11:52 status half-configured gdm3:amd64 3.36.3-0ubuntu0.20.04.4 2022-02-13 06:11:53 status installed gdm3:amd64 3.36.3-0ubuntu0.20.04.4 ** Affects: gdm3 (Ubuntu) Importance: Undecided Status: New -- 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/1960857 Title: gdm3 self-enables during upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1960857/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1957718] [NEW] package libnautilus-extension1a:amd64 1:40.2-1ubuntu1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configurati
Public bug reported: Not sure what the issue is. A message pops up and says there is an issue. ProblemType: Package DistroRelease: Ubuntu 21.10 Package: libnautilus-extension1a:amd64 1:40.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19 Uname: Linux 5.13.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 AptOrdering: ghostscript-x:amd64: Install ghostscript:amd64: Install libgs9:amd64: Install libgs9-common:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: pass Date: Wed Jan 12 19:29:51 2022 DpkgHistoryLog: Start-Date: 2022-01-12 19:29:40 Commandline: /usr/bin/unattended-upgrade Upgrade: ghostscript-x:amd64 (9.54.0~dfsg1-0ubuntu2, 9.54.0~dfsg1-0ubuntu2.1), libgs9-common:amd64 (9.54.0~dfsg1-0ubuntu2, 9.54.0~dfsg1-0ubuntu2.1), ghostscript:amd64 (9.54.0~dfsg1-0ubuntu2, 9.54.0~dfsg1-0ubuntu2.1), libgs9:amd64 (9.54.0~dfsg1-0ubuntu2, 9.54.0~dfsg1-0ubuntu2.1) DuplicateSignature: package:libnautilus-extension1a:amd64:1:40.2-1ubuntu1 Setting up libgs9:amd64 (9.54.0~dfsg1-0ubuntu2.1) ... dpkg: error processing package libuno-sal3 (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration GsettingsChanges: InstallationDate: Installed on 2021-04-28 (260 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) Python3Details: /usr/bin/python3.9, Python 3.9.7, python3-minimal, 3.9.4-1build1 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.20.9ubuntu2 apt 2.3.9 SourcePackage: nautilus Title: package libnautilus-extension1a:amd64 1:40.2-1ubuntu1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: Upgraded to impish on 2021-10-14 (90 days ago) usr_lib_nautilus: evince40.4-2 file-roller 3.40.0-2 nautilus-extension-gnome-terminal 3.38.1-1ubuntu2 nautilus-share0.7.3-2ubuntu4 ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package impish need-duplicate-check -- 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/1957718 Title: package libnautilus-extension1a:amd64 1:40.2-1ubuntu1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1957718/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1933748] Re: Gnome wifi menu items jumping up and down make clicking risky
Jumping does not occur most of the time that I boot or awaken it, so I'll accept your prioritization, since my idea for a patch may be more complicated to implement than I suppose. So, I won't download a new Ubuntu now. The apport-collect command is too risky to run (see https://bugs.launchpad.net/ubuntu/+source/update- manager/+bug/1933747/comments/2) and it does not provide relevant terminal output I could copy and paste into here. If there's something you'd like to know about my platform or something like that, let me know and I can try to check and report back. -- 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/1933748 Title: Gnome wifi menu items jumping up and down make clicking risky To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1933748/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1933748] Re: Gnome menu items jumping up and down make clicking risky
I thought I did, but I guess the entry didn't save, and somehow my copy of the entry has the wrong entry anyway. The opening post has it correctly and with the full string. ** Package changed: ubuntu => gnome-shell (Ubuntu) -- 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/1933748 Title: Gnome menu items jumping up and down make clicking risky To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1933748/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1917806] Re: [amdgpu] Freezes after submitting the login password
** Attachment added: "prevboot log" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1917806/+attachment/5473726/+files/prevboot.txt -- 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/1917806 Title: [amdgpu] Freezes after submitting the login password To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1917806/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1873093] Re: Gnome-terminal tab bar steals keyboard focus
Oops, yes it does. To reproduce in 20.04: * open multiple tabs. * click on an inactive tab, to activate it. do not move the mouse at all once clicked. * wait a couple of seconds. * move the mouse slightly within the new active tab title, and stop. * wait a couple more seconds. * when the tab tooltip pops up, the focus is stolen from the active terminal frame. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1873093 Title: Gnome-terminal tab bar steals keyboard focus To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1873093/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1873093] Re: Gnome-terminal tab bar steals keyboard focus
Doesn't seem to be happening with 20.04, for now at least. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1873093 Title: Gnome-terminal tab bar steals keyboard focus To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1873093/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1887504] [NEW] On first launch system sounds shown at 0% volume but really are not
Public bug reported: Fresh installation + updates of 20.04. The system sounds (e.g. plugging in charger) volume is shown to be at 0% volume but they are still playing. This is worked around by dragging the slider up then back to 0. I would have expected it to be at around 20% volume based on the loudness of the sounds. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.3-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Jul 14 19:29:18 2020 InstallationDate: Installed on 2020-07-13 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: LANGUAGE=en_AU:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal wayland-session ** Attachment added: "The system volume slider in its default position" https://bugs.launchpad.net/bugs/1887504/+attachment/5392546/+files/Screenshot%20from%202020-07-14%2019-35-08.png -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1887504 Title: On first launch system sounds shown at 0% volume but really are not To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1887504/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1764096] Re: Brasero can't burn DVD because of permissions issue
Thanks! > sudo chmod +s $(which wodim) Worked for me, too! -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to brasero in Ubuntu. https://bugs.launchpad.net/bugs/1764096 Title: Brasero can't burn DVD because of permissions issue To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/brasero/+bug/1764096/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 1873093] Re: Gnome-terminal tab bar steals keyboard focus
On 12/05/20 2:51 am, Sebastien Bacher wrote: > Thank you for the bug report, could you try to screencast the issue, it > could be cleared than a text description there. Reading the summary it > sounds like it could maybe be a touchpad generating click event when not > wanted? No touchpad, not a laptop. Will be upgrading to 20.04 in next day or two; will check whether it is still present after that. Cheers, Nick -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1873093 Title: Gnome-terminal tab bar steals keyboard focus To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1873093/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1873093] Re: Gnome-terminal tab bar steals keyboard focus
As upstream bug is now closed & it seems likely not an upstream bug... it's back. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1873093 Title: Gnome-terminal tab bar steals keyboard focus To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1873093/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1874583] [NEW] Setting fractional scaling beyond 125% causes segfault
Public bug reported: Setting fractional scaling between 125% and 175% yields improper behavior. When set to 125%, display will be scaled to 200%. Attempting to use either 150% or 175% scaling causes gnome-control-center to segfault. Selecting 200% scaling exhibits proper behavior. Steps to reproduce the issue: 1. Enable the Fractional Scaling toggle under Displays in gnome-control-center. 2a. Select 125% beside Scale, and press "Apply" at the top right. Display should scale to 200% and the selected scale should also change to 200%. 2b. Select either 150% or 175% beside Scale and press "Apply" at the top right. Monitor may possibly turn off for a few seconds, and gnome-control-center will have segfaulted with scaling remaining at 100% when it turns back on. Release: Ubuntu 20.04 LTS Package version: 1:3.36.1-1ubuntu5 Expected behavior: Display scaling set properly to fractional values Exhibited behavior: Improper scaling with scale set to 125% and segmentation faults with 150% and 175% scale ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.1-1ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Apr 23 21:17:22 2020 InstallationDate: Installed on 2020-04-23 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1874583 Title: Setting fractional scaling beyond 125% causes segfault To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1874583/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1873093] Re: Gnome-terminal tab bar steals keyboard focus
See upstream bug report for more details. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1873093 Title: Gnome-terminal tab bar steals keyboard focus To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1873093/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1873093] [NEW] Gnome-terminal tab bar steals keyboard focus
Public bug reported: I'm not sure when it started, but using the version of Gnome-Terminal in latest ubuntu (GT 3.34.2), I regularly find the tab bar stealing keyboard focus. This is dangerous. The problem is usually that I click on a tab, leave the mouse there, and start typing. The tab bar then steals the first character typed. Sometimes I click in the terminal window, and then move the mouse out of the way (to the tab bar). Sometimes it happens later, when the mouse drifts onto a tab (maybe I knock it slightly while typing). There are many cases in which the unexpected loss of a character typed could lead to significant damage. For example, rm *~ losing the tilde. Or sudo rm -rf /mnt/1/* losing the 1. I have preferred click to focus (as opposed to focus-follows-mouse) in X for nearly 30 years. Gnome-Terminal should not pervert this preference. Reported upstream - https://gitlab.gnome.org/GNOME/gnome- terminal/-/issues/245 Not clear that this is 100% a bug with gnome-terminal, or whether it is an interaction between it and another part of the XWayland/gnome/gnome- shell setup. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-terminal 3.34.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-46.38-generic 5.3.18 Uname: Linux 5.3.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.8 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Apr 16 10:16:15 2020 InstallationDate: Installed on 2020-03-15 (31 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: gnome-terminal UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-terminal (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan wayland-session -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1873093 Title: Gnome-terminal tab bar steals keyboard focus To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1873093/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1827428] Re: Mouse cursor left frozen copy of itself
Also FWIW it also happens with amdgpu so I think it's probably mutter and not nvidia -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1827428 Title: Mouse cursor left frozen copy of itself To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1827428/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1827428] Re: Mouse cursor left frozen copy of itself
Been experiencing this on multiple distributions but haven't been able to find an upstream bug report -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1827428 Title: Mouse cursor left frozen copy of itself To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1827428/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1844641] [NEW] Login screen not keyboard accessible after using NoMachine
Public bug reported: As far as I can tell this is related to having used the system via the NoMachine remote desktop server. - Be at the login screen - Connect remotely to system from another computer and start a new Virtual desktop - Sign out of virtual desktop - Return to system and try to log in using only the keyboard - The current user is not selected and no combination of keyboard keys (tab etc.) are able to focus it. Only the mouse can select the user to show the password field. I'm using a NoMachine Workstation subscription but I think the free package would be similarly affected. Description:Ubuntu 19.04 Release:19.04 Package: nomachine-workstation Version: 6.6.8-8 Status: install ok installed Priority: optional Section: net Maintainer: NoMachine S.a.r.l. Installed-Size: 258 MB Conflicts: nxmanager, nxwebplayer, nxserver, nxnode, nxclient, nomachine-enterprise-client Replaces: nxmanager, nxwebplayer, nxserver, nxnode, nxclient, nomachine Download-Size: unknown APT-Manual-Installed: yes APT-Sources: /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gdm3 3.32.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-29.31-generic 5.0.21 Uname: Linux 5.0.0-29-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Sep 19 10:15:08 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2018-08-23 (391 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/usr/local/bin/bash SourcePackage: gdm3 UpgradeStatus: Upgraded to disco on 2019-05-08 (133 days ago) ** Affects: gdm3 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco -- 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/1844641 Title: Login screen not keyboard accessible after using NoMachine To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1844641/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1811707] Re: gnome-calculator snap does not respect shell theme
I am also seeing this using X.org, not Wayland. Theme is set to Communitheme in gsettings. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-calculator in Ubuntu. https://bugs.launchpad.net/bugs/1811707 Title: gnome-calculator snap does not respect shell theme To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calculator/+bug/1811707/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1800043] Re: nautilus cannot write on nfs file share
** Changed in: nautilus (Ubuntu) Status: Invalid => Incomplete -- 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/1800043 Title: nautilus cannot write on nfs file share To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1800043/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1800043] Re: nautilus cannot write on nfs file share
I exported a nfs share (rw,sync,no_subtree_check) on Ubuntu 18.04.1 LTS, used nfs-kernel-server: 1:1.3.4-2.1ubuntu5 and nfs-common: 1:1.3.4-2.1ubuntu5 nautilus: 1:3.26.4-0~ubuntu18.04.2 and could not reproduce the problem. Ensure the system is properly patched. ** Changed in: nautilus (Ubuntu) Status: Incomplete => Invalid -- 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/1800043 Title: nautilus cannot write on nfs file share To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1800043/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1800043] Re: nautilus cannot write on nfs file share
** Changed in: nautilus (Ubuntu) Status: New => Incomplete -- 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/1800043 Title: nautilus cannot write on nfs file share To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1800043/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1800043] Re: nautilus cannot write on nfs file share
I exported a nfs share (rw,sync,no_subtree_check) on Ubuntu 18.04.1 LTS Release: 18.04 nautilus: 1:3.26.4-0~ubuntu18.04.2 and could not reproduce the problem. Nautilus works OK. -- 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/1800043 Title: nautilus cannot write on nfs file share To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1800043/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1810234] Re: Nautilus (list view) - selection is done by a whole line instead of by a file name which causing problem to get the right mouse click menu of the current folder
** Summary changed: - Nautilus (list view) - selection is done by a whole line instead of a file name which causing problem to get the right mouse click menu of the current folder + Nautilus (list view) - selection is done by a whole line instead of by a file name which causing problem to get the right mouse click menu of the current folder -- 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/1810234 Title: Nautilus (list view) - selection is done by a whole line instead of by a file name which causing problem to get the right mouse click menu of the current folder To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1810234/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1810234] Re: Nautilus (list view) - selection is done by a whole line instead of a file name which causing problem to get the right mouse click menu of the current folder
** Summary changed: - Nautilus (list view) - it is not always possible to get the right mouse click menu of the current folder + Nautilus (list view) - selection is done by a whole line instead of a file name which causing problem to get the right mouse click menu of the current folder -- 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/1810234 Title: Nautilus (list view) - selection is done by a whole line instead of by a file name which causing problem to get the right mouse click menu of the current folder To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1810234/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1810234] Re: Nautilus (list view) - it is not always possible to get the right mouse click menu of the current folder
** Summary changed: - In the nautilus list view is not always possible to get the right mouse click menu of the current folder + Nautilus (list view) - it is not always possible to get the right mouse click menu of the current folder -- 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/1810234 Title: Nautilus (list view) - it is not always possible to get the right mouse click menu of the current folder To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1810234/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1810234] Re: In the nautilus list view is not always possible to get the right mouse click menu of the current folder
** Summary changed: - Not always possible in the nautilus list view to get the right mouse click menu of the current folder + In the nautilus list view is not always possible to get the right mouse click menu of the current folder -- 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/1810234 Title: In the nautilus list view is not always possible to get the right mouse click menu of the current folder To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1810234/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1810234] [NEW] Not always possible in the nautilus list view to get the right mouse click menu of the current folder
Public bug reported: Description:Ubuntu 18.04.1 LTS Release:18.04 $ apt-cache policy nautilus nautilus: Installed: 1:3.26.4-0~ubuntu18.04.2 Candidate: 1:3.26.4-0~ubuntu18.04.2 Version table: *** 1:3.26.4-0~ubuntu18.04.2 500 500 http://au.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:3.26.3-0ubuntu4 500 500 http://au.archive.ubuntu.com/ubuntu bionic/main amd64 Packages If a folder is opened in the GNOME/nautilus list view it is not always possible to get the right mouse click menu of the current folder because nautilus selects a whole line instead of a file name and produced right click menu belongs to a file in the list, not to the current folder. If the current folder list is short enough then one can right click on the empty space below the last line and that way can get the right click menu of the current folder. This problem is caused by nautilus selecting a whole line in the list view instead of a file name in the list. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nautilus 1:3.26.4-0~ubuntu18.04.2 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Jan 2 14:04:58 2019 InstallationDate: Installed on 2018-12-29 (3 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcEnviron: LANGUAGE=en_AU:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- 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/1810234 Title: Not always possible in the nautilus list view to get the right mouse click menu of the current folder To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1810234/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1809117] Re: Screen corruption on "Lock Screen" or "Switch User" command
Re-enabled GSConnect and it seems fine now. Very strange. Anyway I think this can be closed. Apologies for the noise. -- 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/1809117 Title: Screen corruption on "Lock Screen" or "Switch User" command To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1809117/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1809117] Re: Screen corruption on "Lock Screen" or "Switch User" command
Disabled the GSConnect extension and all seems fine now. I'll head over and raise the bug there. -- 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/1809117 Title: Screen corruption on "Lock Screen" or "Switch User" command To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1809117/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1809117] Re: Screen corruption on "Lock Screen" or "Switch User" command
Further to comment 5, I've had a further look in the live environment
and it appears the screen isn't locked out when I switch user - so I can
use Ctrl-Alt-F{1..8} to switch between things. This suggests to me that
the screen-locking code path isn't getting tested when I try this from
the Live USB.
--
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/1809117
Title:
Screen corruption on "Lock Screen" or "Switch User" command
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1809117/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1809117] Re: Screen corruption on "Lock Screen" or "Switch User" command
Not a problem on live USB stick I installed from. I booted the live medium for Cosmic, set a password for the live user, created 'anotheruser' from the Settings panel, logged out and back in as the live session user. Clicked the User Menu -> Live Session User -> Switch User, and I was taken straight to the GDM login screen, where I could switch user to anotheruser. And I was able to switch back and forth between the live user and anotheruser without any issues. An oddity is in the live session the 'Lock screen' icon isn't offered even though the accounts are password-protected - only Switch User is present - which makes me wonder if I'm activating the same code path this way. -- 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/1809117 Title: Screen corruption on "Lock Screen" or "Switch User" command To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1809117/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1809117] Re: Screen corruption on "Lock Screen" or "Switch User" command
Despite my not selecting the option when I raised this, I do think this is a security issue because it can reveal on-screen data in a mode where it's expected it's all locked away. However I can't find an option to add the security flag to this bug report after the fact. -- 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/1809117 Title: Screen corruption on "Lock Screen" or "Switch User" command To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1809117/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1809117] Re: Screen corruption on "Lock Screen" or "Switch User" command
** Attachment added: "lspci -k -nn" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1809117/+attachment/5223520/+files/lspci-k-nn.txt -- 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/1809117 Title: Screen corruption on "Lock Screen" or "Switch User" command To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1809117/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1809117] Re: Screen corruption on "Lock Screen" or "Switch User" command
The VGA bit of lspci -k -nn 00:02.0 VGA compatible controller [0300]: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [1043:8534] Kernel driver in use: i915 Kernel modules: i915 -- 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/1809117 Title: Screen corruption on "Lock Screen" or "Switch User" command To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1809117/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1809117] [NEW] Screen corruption on "Lock Screen" or "Switch User" command
Public bug reported: Click the user menu (top right) and choose either the Lock icon or $username -> Switch User. I expected to be sent to a lock screen (possibly via a blanked screen or a screensaver - I don't know what normal behaviour is for Ubuntu 19.04). What happened was most of the Gnome shell was left up on screen, including all my apps that were running, along with the user menu with greyed-out Lock button. If I click the menu again, I get the cut-down version I would expect from GDM with only the option to alter volume and network connections. If I click the top bar again, I get a sort of shimmering version of the cut-down user menu superimposed on the original full version of the user menu that never went away. The favourites icon on the left dock are also clickable and hoverable, but they don't actually do anything and any tooltips are left imprinted on the screen. I can unlock the screen again by manually pressing Ctrl-Alt-F1 to return me to the original GDM login screen, clicking my user picture and entering my password. I have an unlisted youtube video of most of this behaviour, except there's no recording of me switching to VT1 to unlock again (the recorded screen goes blank for that part). https://www.youtube.com/watch?v=JjocsxBLUpE My assignment of 'gnome-shell' is a guess. As far as I know it could be related to gdm3, the X intel driver, X itself or even the kernel, or some nasty interaction between those. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gnome-shell 3.30.1-2ubuntu1.18.10.1 ProcVersionSignature: Ubuntu 4.18.0-12.13-generic 4.18.17 Uname: Linux 4.18.0-12-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Dec 19 13:27:31 2018 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'enabled-extensions' b"['gsconn...@andyholmes.github.io']" b'org.gnome.shell' b'command-history' redacted by apport b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2018-12-19 (0 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic -- 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/1809117 Title: Screen corruption on "Lock Screen" or "Switch User" command To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1809117/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1292398] Re: Second screen position isn't saved from one session to another
@Alberts this is still an issue in Xubuntu 18.04 :( I have been battling with in xubuntu 16.04 and thought it would have been resolved by now...no love for xubuntu :( root issue: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1283615 A Work around solution: http://bernaerts.dyndns.org/linux/74-ubuntu/309-ubuntu-dual-display-monitor-position-lost#h1-setup-a-clean-configuration -- 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/1292398 Title: Second screen position isn't saved from one session to another To manage notifications about this bug go to: https://bugs.launchpad.net/elementaryos/+bug/1292398/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1697229] Re: GNOME extensions deactivated after lock unlock
I've experienced possibly this bug intermittently since moving to Manjaro Gnome with Gnome 3.30.2. In my case it's not all the extensions that are reset, but two that I've set different to default: Places status indicator and Topicons plus. Furthermore, rebooting usually puts it right; it's the locking and unlocking that deactivates those extensions on my system. -- 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/1697229 Title: GNOME extensions deactivated after lock unlock To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-session/+bug/1697229/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1791555] [NEW] Gnome-software segmentation faults on open
Public bug reported: Gnome-software, "Software" in Unity, recently began crashing upon opening. I have attached the terminal output below. ** Affects: gnome-software (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Terminal output for `$ gnome-software --verbose`" https://bugs.launchpad.net/bugs/1791555/+attachment/5186923/+files/terminalout.txt -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1791555 Title: Gnome-software segmentation faults on open To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1791555/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1672297] Re: gnome-shell uses lots of memory, and grows over time
For us end-users, does "Fix Released" just mean released to a nightly/unstable/private package repo? Because https://packages.ubuntu.com/bionic/gjs still lists the version at 1.52.1, that means this still unreleased in stable? What's the status to look out for when an `apt-get upgrade` will fix the issue? -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gjs in Ubuntu. https://bugs.launchpad.net/bugs/1672297 Title: gnome-shell uses lots of memory, and grows over time To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1672297/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1748871] Re: GDM horizontal scanline corruption with an ultra wide monitor
I can also verify this issue. A few things to further note (just in case there may be other involved components): 1) This issue also affects Ubuntu 17.10 out of the box, as well as Fedora 27. 2) The issue is not just with the login screen; this "vertical asynchronization" is also present during bootup, as well as during the desktop session if logged in. (It is even present during boot with Ubuntu 16.04, which I clean-installed when I encountered this issue initially with 17.10 after purchasing my ultrawide monitor) 3) The issue is not present if I am able to change the resolution to 1920x1080 (of course, this negates the benefit of the ultrawide monitor) 4) If it weren't for it also being present during the bootup sequence, I would say that it seems to be constrained to Wayland; if Wayland is disabled, the issue is not present at the login screen nor during the desktop session. I understand this makes pinning the culprit down more difficult; if it weren't for everything working fine in X.org, I would point the finger at the AMDGPU driver. If it weren't for the issue being present during the bootup sequence, I would point the finger at Wayland. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1748871 Title: GDM horizontal scanline corruption with an ultra wide monitor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1748871/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1748147] [NEW] Upgrading systemd sets incorrect permissions on /var/log/
Public bug reported: Upgrading or reinstalling the systemd package when using rsyslogd results in bad permissions (0755 instead of 0775) being set on /var/log/. As a consequence of this, rsyslogd can no longer create new files within this directory, resulting in lost log messages. The default configuration of rsyslogd provided by Ubuntu runs the daemon as syslog:syslog and sets ownership of /var/log to syslog:adm with mode 0775. Systemd's default tmpfiles configuration sets /var/log to 0755 in /usr/lib/tmpfiles.d/var.conf, however this is overridden in /usr/lib/tmpfiles.d/00rsyslog.conf which is provided by package rsyslog. It looks as though an upgrade of the systemd package fails to take /usr/lib/tmpfiles.d/00rsyslog.conf into account, as demonstrated below. This results in /var/log receiving mode 0755 instead of the expected 0775: nick @ log2.be1.ams1:~ $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 16.04.3 LTS Release:16.04 Codename: xenial nick @ log2.be1.ams1:~ $ apt policy systemd systemd: Installed: 229-4ubuntu21.1 Candidate: 229-4ubuntu21.1 Version table: *** 229-4ubuntu21.1 500 500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages 100 /var/lib/dpkg/status 229-4ubuntu4 500 500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages nick @ log2.be1.ams1:~ $ apt policy rsyslog rsyslog: Installed: 8.16.0-1ubuntu3 Candidate: 8.16.0-1ubuntu3 Version table: *** 8.16.0-1ubuntu3 500 500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status nick @ log2.be1.ams1:~ $ grep -F /var/log /usr/lib/tmpfiles.d/var.conf d /var/log 0755 - - - f /var/log/wtmp 0664 root utmp - f /var/log/btmp 0600 root utmp - nick @ log2.be1.ams1:~ $ cat /usr/lib/tmpfiles.d/00rsyslog.conf # Override systemd's default tmpfiles.d/var.conf to make /var/log writable by # the syslog group, so that rsyslog can run as user. # See tmpfiles.d(5) for details. # Type PathMode UID GID Age Argument d /var/log 0775 root syslog - nick @ log2.be1.ams1:~ $ ls -ld /var/log drwxrwxr-x 8 root syslog 4096 Feb 7 13:45 /var/log nick @ log2.be1.ams1:~ $ sudo apt install --reinstall systemd Reading package lists... Done Building dependency tree Reading state information... Done 0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 7 not upgraded. Need to get 3,634 kB of archives. After this operation, 0 B of additional disk space will be used. Get:1 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 systemd amd64 229-4ubuntu21.1 [3,634 kB] Fetched 3,634 kB in 0s (24.3 MB/s) (Reading database ... 86614 files and directories currently installed.) Preparing to unpack .../systemd_229-4ubuntu21.1_amd64.deb ... Unpacking systemd (229-4ubuntu21.1) over (229-4ubuntu21.1) ... Processing triggers for dbus (1.10.6-1ubuntu3.3) ... Processing triggers for ureadahead (0.100.0-19) ... Processing triggers for man-db (2.7.5-1) ... Setting up systemd (229-4ubuntu21.1) ... addgroup: The group `systemd-journal' already exists as a system group. Exiting. nick @ log2.be1.ams1:~ $ ls -ld /var/log drwxr-xr-x 8 root syslog 4096 Feb 7 13:45 /var/log ** Affects: systemd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1748147 Title: Upgrading systemd sets incorrect permissions on /var/log/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1748147/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1208993] Re: Ubuntu slows down and hangs while copying file from/to USB
False alarm! The problem just happened again. Froze while downloading the google chrome installer. It does seem like the vm.dirty modifications definitely helped. But it could have been coincidence. At least it didn't freeze during the updater and ruin my filesystem this time. -- 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/1208993 Title: Ubuntu slows down and hangs while copying file from/to USB To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1208993/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1208993] Re: Ubuntu slows down and hangs while copying file from/to USB
Same issue here on a new 16.04 install on a new HP laptop. SSD. It was crashing randomly during the install, then when I got it installed it crashed every time I tried to run the updater. Setting the vm.dirty_ratio and vm.dirty_background_ratio to 10 and 5 worked for me as well so far. I did notice one interesting thing, which I feel might help diagnose what's going on behind the scenes. When I was having the problem, the CPU temp would get pretty high (up to 70 C) and the fan on the laptop was running very loudly. These symptoms happened every time. The mouse became slower, and slower, and unresponsive. Ctrl-Alt-F1 and other keyboard shortcuts were unresponsive as well. After changing those vm values, I was able to go through the updater with no issue. And my CPU temp was about 10 C lower, hovering around 60 during the updater. The cooling fan did not go on high either. So somehow the higher vm.dirty values are creating a situation where the CPU is working much harder than it needs to for the job it's trying to do. I don't know nearly enough about the inner workings of linux to know what this means, but my instincts tell me it might be an important clue for anyone trying to fix this bug. Hopefully it helps. -- 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/1208993 Title: Ubuntu slows down and hangs while copying file from/to USB To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1208993/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1714596] Re: PDF images are blank
This bug makes the PDF viewer all but useless in artful. Can we hope to see a bug fix before release? -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to poppler in Ubuntu. https://bugs.launchpad.net/bugs/1714596 Title: PDF images are blank To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1714596/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1722005] Re: Image-heavy PDF no longer displays
Interestingly the .djvu file of the same images from the torrent works smoothly and without incident. the PDF claims to be a PDF/A of some variety, so I'd have assumed it was less complicated a dataset than most! -- 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/1722005 Title: Image-heavy PDF no longer displays To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1722005/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1722005] [NEW] Image-heavy PDF no longer displays
Public bug reported: The PDF from https://archive.org/details/kamikiukulelemet00newy displayed fine under zesty, but under artful it shows up as lots of blank white pages. This is the same under other PDF viewers, so I suspect the real bug is in one of the shared libraries used by all of them. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: evince 3.26.0-1 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Oct 7 20:53:07 2017 InstallationDate: Installed on 2014-05-29 (1227 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) SourcePackage: evince UpgradeStatus: Upgraded to artful on 2017-10-07 (0 days ago) ** Affects: evince (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful wayland-session -- 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/1722005 Title: Image-heavy PDF no longer displays To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1722005/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1641442] [NEW] Import with reneg-sec larger than 65535 fails
Public bug reported: Attempting to import a .ovpn config file with a reneg-sec option larger than 65535 through the gnome network manager causes the following error message: The file 'config.ovpn' could not be read or does not contain recognized VPN connection information Error: configuration error: invalid 1th argument to 'reneg-sec' where number expected (line 54). ** Affects: network-manager-openvpn (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to network-manager-openvpn in Ubuntu. https://bugs.launchpad.net/bugs/1641442 Title: Import with reneg-sec larger than 65535 fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1641442/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1437411] Re: Keyboard layout indicator shows wrong layout
This bug still exists in Ubuntu 15.10 with gnome-settings-daemon version 3.16.3-0ubuntu1. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1437411 Title: Keyboard layout indicator shows wrong layout To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1437411/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1409032] Re: gvfsd-smb: very high CPU utilisation
Can anyone briefly state what gvfsd-smb-browse does? I know samba is used to connect to Windows networks. Perhaps clarity on this would help people decide weather to keep, remove, or find a work-around to it. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1409032 Title: gvfsd-smb: very high CPU utilisation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1409032/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1409032] Re: gvfsd-smb: very high CPU utilisation
I used the terminal to back up the gvfsd-smb-browse, then removed it. I think I do not use this file for anything. It looks like the system is still running fine as far as I can see. The CPU has a normal load after boot up... -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1409032 Title: gvfsd-smb: very high CPU utilisation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1409032/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1573206] Re: GNOME Software does not install third-party .deb packages
*** This bug is a duplicate of bug 1573408 *** https://bugs.launchpad.net/bugs/1573408 Loving 16.04 except for the downloads. hoping it gets fixed soon. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1573206 Title: GNOME Software does not install third-party .deb packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-gnome/+bug/1573206/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1557797] Re: Big bug : CPU 100% load with gvfsd-smb-browse on Ubuntu Mate 16.04
I would stop the smb-browse manually, but later another process would start up again. I could not see it in the system monitor under processes, and the smb-browse was still stopped. It did the same thing: by taking %100 of one core. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1557797 Title: Big bug : CPU 100% load with gvfsd-smb-browse on Ubuntu Mate 16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1557797/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1557797] Re: Big bug : CPU 100% load with gvfsd-smb-browse on Ubuntu Mate 16.04
I was also affected by this bug. It is after start up, then appears to either time out or simply stops. I was told by another user that it stopped occurring after some time. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1557797 Title: Big bug : CPU 100% load with gvfsd-smb-browse on Ubuntu Mate 16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1557797/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1574880] [NEW] Xubuntu needs a lot of time to shutdown
Public bug reported: Xubuntu needs a lot of time to shutdown. In Xubuntu 15.04 it needed only a few seconds and now a minute. I'm using a Lenovo X220. Description:Ubuntu 16.04 LTS Release:16.04 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: systemd-sysv 229-4ubuntu4 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: XFCE Date: Tue Apr 26 00:31:34 2016 InstallationDate: Installed on 2016-04-24 (1 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial ** Description changed: Xubuntu needs a lot of time to shutdown. In Xubuntu 15.04 it needed only a few seconds and now a minute. + + I'm using a Lenovo X220. Description: Ubuntu 16.04 LTS Release: 16.04 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: systemd-sysv 229-4ubuntu4 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: XFCE Date: Tue Apr 26 00:31:34 2016 InstallationDate: Installed on 2016-04-24 (1 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: systemd 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 systemd in Ubuntu. https://bugs.launchpad.net/bugs/1574880 Title: Xubuntu needs a lot of time to shutdown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1574880/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1556429] Re: Cannot add partition to a formatted USB memory
I encounter the same error when formatting a drive and adding a partition, using the default options. Occasionally the program will simply crash without displaying an error message. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-disk-utility in Ubuntu. https://bugs.launchpad.net/bugs/1556429 Title: Cannot add partition to a formatted USB memory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/1556429/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1495851] [NEW] Can't seem to make USB microphone the preferred input
Public bug reported: My laptop has a built-in audio port that accepts a three-channel ⅛” plug for a stereo+microphone headset. Unfortunately due to the nature of the beast, there is rather a lot of cross-talk, and the electronics in the laptop are not the best. Also the DSP inside the laptop is surrounded by sources of magnetic interference such as the fans, power supply, WiFi antenna, etc. When I plug in my nice USB microphone, I always have to go into the sound settings tool and hunt over to the input tab and select it from the listing in order to get audio through it. It's lucky that I know how to do this, as some folks would simply plug it in, test it, and decide that it doesn't work! While I would argue that USB audio devices should be preferred over built-in laptop chips, I am most frustrated by the lack of ability for me to even say "From now on prefer this specific audio device for input, whenever it is present". I want to make my USB microphone Just Work without all the clicking about! ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: gnome-control-center (not installed) ProcVersionSignature: Ubuntu 3.19.0-28.30-generic 3.19.8-ckt5 Uname: Linux 3.19.0-28-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.4 Architecture: amd64 CurrentDesktop: Unity Date: Tue Sep 15 09:09:22 2015 InstallationDate: Installed on 2014-05-29 (473 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to vivid on 2015-05-05 (132 days ago) ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug vivid -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1495851 Title: Can't seem to make USB microphone the preferred input To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1495851/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1495851] Re: Can't seem to make USB microphone the preferred input
The command-line way to do this seems to be: $ pacmd load-module module-switch-on-connect Which works fine. I am willing to be convinced that this is a bad default for some reason (and I'm going to file that as a separate bug) but at least the control centre should give me a checkbox to flip this on! -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1495851 Title: Can't seem to make USB microphone the preferred input To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1495851/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1100415] Re: git commit fails if gedit is already opened
This is not a bug but a wrong configuration issue. Most editors (including gedit, subl, atom ) should be configured with -w (--wait) parameter. From gedit -h: -w, --waitOpen files and block process until files are closed So the configuration command should be like this: git config --global core.editor gedit -w -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1100415 Title: git commit fails if gedit is already opened To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1100415/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1284308] Re: Can't copy files from a bluetooth device: Another operation in progress
** Tags added: vivid -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1284308 Title: Can't copy files from a bluetooth device: Another operation in progress To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/1284308/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1284308] Re: Can't copy files from a bluetooth device: Another operation in progress
Using Xubuntu 15.04: hci0: Type: BR/EDR Bus: USB BD Address: E4:D5:3D:CB:D3:1D ACL MTU: 1021:8 SCO MTU: 64:1 UP RUNNING PSCAN RX bytes:273872 acl:1239 sco:0 events:586 errors:0 TX bytes:39316 acl:1037 sco:0 commands:41 errors:0 btusb 32768 0 bluetooth 491520 22 bnep,btusb,rfcomm Bus 001 Device 006: ID 0a5c:217f Broadcom Corp. BCM2045B (BDC-2.1) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1284308 Title: Can't copy files from a bluetooth device: Another operation in progress To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/1284308/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1251281] Re: gnome-session-flashback/Unity fails to start without hardware acceleration in cloud/remote environments (Forwarded-X/XRDP/VNC/NX/X2GO/Chromoting)
** Bug watch added: Debian Bug tracker #776746 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=776746 ** Also affects: gnome-session (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=776746 Importance: Unknown Status: Unknown -- 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/1251281 Title: gnome-session-flashback/Unity fails to start without hardware acceleration in cloud/remote environments (Forwarded-X/XRDP/VNC/NX/X2GO/Chromoting) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-session/+bug/1251281/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1352977] Re: Creating a prompt session for an app without a surface does not show the prompt
** Changed in: qtmir Status: In Progress = Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to location-service in Ubuntu. https://bugs.launchpad.net/bugs/1352977 Title: Creating a prompt session for an app without a surface does not show the prompt To manage notifications about this bug go to: https://bugs.launchpad.net/osmtouch/+bug/1352977/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1283682] Re: GdkPixbuf-WARNING **: Cannot open pixbuf loader module file '/usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders.cache':
*** This bug is a duplicate of bug 619003 *** https://bugs.launchpad.net/bugs/619003 ** This bug has been marked a duplicate of bug 619003 GdkPixbuf-WARNING **: Cannot open pixbuf loader module file '/usr/lib/gdk-pixbuf-2.0/2.10.0/loaders.cache' -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-icon-theme in Ubuntu. https://bugs.launchpad.net/bugs/1283682 Title: GdkPixbuf-WARNING **: Cannot open pixbuf loader module file '/usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders.cache': To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-icon-theme/+bug/1283682/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 146206] Re: files are copied to a local directory before being extracted
I wrote about this 4 years ago. http://linuxtechie.wordpress.com/2010/01/05/file-roller-is-terribly- inefficient/ You hit the exact same points I did. I no longer use Gnome anymore but it's sad to see this stupidity still hasn't been fixed. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. https://bugs.launchpad.net/bugs/146206 Title: files are copied to a local directory before being extracted To manage notifications about this bug go to: https://bugs.launchpad.net/file-roller/+bug/146206/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
