[Desktop-packages] [Bug 1957711] [NEW] Switching users causes system crash
Public bug reported: Ubuntu 21.10 gdm3: Installed: 41~rc-0ubuntu2 Candidate: 41~rc-0ubuntu2 Version table: *** 41~rc-0ubuntu2 500 500 http://us.archive.ubuntu.com/ubuntu impish/main amd64 Packages 100 /var/lib/dpkg/status Steps to reproduce: 1. Log in as any user 2. In the top right of the screen, click the power icon (⏻) 3. Select [Power Off/Log Out] 4. Select [Switch User] 5. Select any user that is NOT the user which is still currently logged in 6. Operating system is now frozen, mouse and keyboard don't respond, and user is never logged in. 7. Pressing [CTRL] + [ALT] + [DEL] appears to cause the system to crash Apport.log: https://pastebin.com/srFwgfAh ** Affects: gdm3 (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Crash log" https://bugs.launchpad.net/bugs/1957711/+attachment/5553637/+files/gdm3.0.crash ** Package changed: apport (Ubuntu) => gdm3 (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1957711 Title: Switching users causes system crash Status in gdm3 package in Ubuntu: New Bug description: Ubuntu 21.10 gdm3: Installed: 41~rc-0ubuntu2 Candidate: 41~rc-0ubuntu2 Version table: *** 41~rc-0ubuntu2 500 500 http://us.archive.ubuntu.com/ubuntu impish/main amd64 Packages 100 /var/lib/dpkg/status Steps to reproduce: 1. Log in as any user 2. In the top right of the screen, click the power icon (⏻) 3. Select [Power Off/Log Out] 4. Select [Switch User] 5. Select any user that is NOT the user which is still currently logged in 6. Operating system is now frozen, mouse and keyboard don't respond, and user is never logged in. 7. Pressing [CTRL] + [ALT] + [DEL] appears to cause the system to crash Apport.log: https://pastebin.com/srFwgfAh To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1957711/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1954939] Re: Cannot open additional instances of the same file with the same name inside a zip archive
I cannot report it upstream, their signup system does not accept any of my email addresses. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to file-roller in Ubuntu. https://bugs.launchpad.net/bugs/1954939 Title: Cannot open additional instances of the same file with the same name inside a zip archive Status in file-roller package in Ubuntu: New Bug description: This issue is very simple. A zip file can legally contain multiple entries with the same name in the same path. If you attempt to open a file that has the same name and path as another, you can only open one of them, and cannot open the other. An example zip file has been provided which contains two `fabric.mod.json` files. If either one of them is double clicked within file roller, it will only open one of them, and never the other. example.zip | | fabric.mod.json (2.1kb) | fabric.mod.json (484 bytes) For me, the 484 byte file is always opened, even if you double click the 2.1kb file. Ubuntu 21.10 file-roller 3.40.0-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/1954939/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1954939] [NEW] Cannot open additional instances of the same file with the same name inside a zip archive
Public bug reported: This issue is very simple. A zip file can legally contain multiple entries with the same name in the same path. If you attempt to open a file that has the same name and path as another, you can only open one of them, and cannot open the other. An example zip file has been provided which contains two `fabric.mod.json` files. If either one of them is double clicked within file roller, it will only open one of them, and never the other. example.zip | | fabric.mod.json (2.1kb) | fabric.mod.json (484 bytes) For me, the 484 byte file is always opened, even if you double click the 2.1kb file. Ubuntu 21.10 file-roller 3.40.0-2 ** Affects: file-roller (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Example zip file which can be used to demonstrate the issue" https://bugs.launchpad.net/bugs/1954939/+attachment/5547843/+files/example.zip ** Summary changed: - Cannot open additional instances of the same file with the same name inside a zip + Cannot open additional instances of the same file with the same name inside a zip archive -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to file-roller in Ubuntu. https://bugs.launchpad.net/bugs/1954939 Title: Cannot open additional instances of the same file with the same name inside a zip archive Status in file-roller package in Ubuntu: New Bug description: This issue is very simple. A zip file can legally contain multiple entries with the same name in the same path. If you attempt to open a file that has the same name and path as another, you can only open one of them, and cannot open the other. An example zip file has been provided which contains two `fabric.mod.json` files. If either one of them is double clicked within file roller, it will only open one of them, and never the other. example.zip | | fabric.mod.json (2.1kb) | fabric.mod.json (484 bytes) For me, the 484 byte file is always opened, even if you double click the 2.1kb file. Ubuntu 21.10 file-roller 3.40.0-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/1954939/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1085706] Re: pam_ecryptfs: seteuid error
xscreenserver on Ubuntu 16.10 affected nov. 16 14:10:13 clevo.gigi.edu xscreensaver[24025]: pam_ecryptfs: seteuid error -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/1085706 Title: pam_ecryptfs: seteuid error Status in eCryptfs: Confirmed Status in GNOME Screensaver: New Status in ecryptfs-utils package in Ubuntu: Triaged Status in gnome-screensaver package in Ubuntu: Triaged Status in kscreenlocker package in Ubuntu: Confirmed Status in plasma-workspace package in Ubuntu: Confirmed Status in gnome-screensaver package in Debian: New Bug description: I get this error message in the syslog when I authenticate succesfully in the screensaver. --- ApportVersion: 2.6.1-0ubuntu6 Architecture: amd64 DistroRelease: Ubuntu 12.10 EcryptfsInUse: Yes GnomeSessionIdleInhibited: No GnomeSessionInhibitors: None GsettingsGnomeSession: org.gnome.desktop.session idle-delay uint32 600 org.gnome.desktop.session session-name 'ubuntu' InstallationDate: Installed on 2012-06-13 (172 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) MarkForUpload: True Package: gnome-screensaver 3.6.0-0ubuntu2 PackageArchitecture: amd64 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 3.5.0-19.30-generic 3.5.7 Tags: quantal running-unity Uname: Linux 3.5.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ecryptfs/+bug/1085706/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1628439] Re: login loop on lightdm-greeter
Not a bug. corrupted xinputrc -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1628439 Title: login loop on lightdm-greeter Status in gvfs package in Ubuntu: Invalid Bug description: After an upgrade of the system not possible anymore to login using lightdm-greeter. Tried dpkg-reconfigure on all major DM package - no success Looking for errors in PAM - no authentication errors Looking for errors in syslog ; org.gtk.vfs.Daemon[7528]: A connection to the bus can't be made seems same problem that Bug #1571206 reported by dino99 on 2016-04-16 but with different symptoms. Workaround ; put the system boot into text mode then "startx" works everytime (and doesn't trigger gvfs error) ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gvfs 1.28.2-1ubuntu1~16.04.1 ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19 Uname: Linux 4.4.0-38-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: MATE Date: Wed Sep 28 11:28:04 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2016-06-01 (118 days ago) InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: gvfs UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1628439/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1628439] Re: login loop on lightdm-greeter
I realized that .xinputrc was corrupted due to the fact that im-config was using an non official md5sum build! For that reason, the bus couldn't sucessfully complete its initialization and gvfs couldn't launch itself. With the use the official md5sum (from coreutils), the .xinputrc was corrected and I could launch the graphical environment automaticaly again without issue (sudo systemctl set-default graphical.target --force) The gvfs error was gone away from syslog. Guillaume -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1628439 Title: login loop on lightdm-greeter Status in gvfs package in Ubuntu: Confirmed Bug description: After an upgrade of the system not possible anymore to login using lightdm-greeter. Tried dpkg-reconfigure on all major DM package - no success Looking for errors in PAM - no authentication errors Looking for errors in syslog ; org.gtk.vfs.Daemon[7528]: A connection to the bus can't be made seems same problem that Bug #1571206 reported by dino99 on 2016-04-16 but with different symptoms. Workaround ; put the system boot into text mode then "startx" works everytime (and doesn't trigger gvfs error) ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gvfs 1.28.2-1ubuntu1~16.04.1 ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19 Uname: Linux 4.4.0-38-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: MATE Date: Wed Sep 28 11:28:04 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2016-06-01 (118 days ago) InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: gvfs UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1628439/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1079552] Re: Unexpectedly asks for authentication halfway through file restore process
This is still a problem in ubuntu 16.04 Xenial. In my situation, I have a number of missing files to restore, let's say six. I run "restore missing files" from the Files right-click option, then for every missing file, I have to type in my user password for authentication. This means that I have to do this six times during the restore process. The message is - "Authentication is needed to run ‘/bin/sh’ as the super user An application is attempting to perform an action that requires privileges. Authentication is required to perform this action." Perhaps there might be a way to allow "/bin/sh" to run without needing authentication? (I configured Backups to restore without a password) The best workaround I can come up with so far is to run deja-dup with sudo at the command line - $ sudo deja-dup --restore-missing file:/// This way I only have to enter my user password once, and right at the beginning. No authentication was needed to run the backup - it's confusing to need it for the restore. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to deja-dup in Ubuntu. https://bugs.launchpad.net/bugs/1079552 Title: Unexpectedly asks for authentication halfway through file restore process Status in deja-dup package in Ubuntu: Confirmed Bug description: While restoring files, after the (very long) "Preparing" step, Deja Dup seems to execute "pkexec /bin/sh …" in order to run some script as root. This is problematic for a few reasons: 1. It happens in the middle of the restore process. At best, the prompt for authentication will appear while the user is doing something else, causing confusion. At worst, the prompt will appear while the user is away from the computer expecting Deja Dup to be restoring his files. 2. When restoring a number of files (deja-dup --restore-missing) the prompt for authentication happens for each file that has been selected. Combined with #1, this means the user must babysit Deja Dup. 3. Deja Dup is running some code with full root permissions, without telling the user what that code does. This shouldn't be necessary. This authentication should be somehow replaced with a gentler, less privileged PolicyKit request, and Deja Dup should ask for authentication either as soon as possible or as late as possible so the need does not arise (repeatedly) while the application is restoring files in the background. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1079552/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1628439] Re: login loop on lightdm-greeter
** Attachment added: "auth" https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1628439/+attachment/4750063/+files/fuck7 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1628439 Title: login loop on lightdm-greeter Status in gvfs package in Ubuntu: New Bug description: After an upgrade of the system not possible anymore to login using lightdm-greeter. Tried dpkg-reconfigure on all major DM package - no success Looking for errors in PAM - no authentication errors Looking for errors in syslog ; org.gtk.vfs.Daemon[7528]: A connection to the bus can't be made seems same problem that Bug #1571206 reported by dino99 on 2016-04-16 but with different symptoms. Workaround ; put the system boot into text mode then "startx" works everytime (and doesn't trigger gvfs error) ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gvfs 1.28.2-1ubuntu1~16.04.1 ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19 Uname: Linux 4.4.0-38-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: MATE Date: Wed Sep 28 11:28:04 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2016-06-01 (118 days ago) InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: gvfs UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1628439/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1628439] Re: login loop on lightdm-greeter
** Attachment added: "syslog" https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1628439/+attachment/4750062/+files/fuck6 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1628439 Title: login loop on lightdm-greeter Status in gvfs package in Ubuntu: New Bug description: After an upgrade of the system not possible anymore to login using lightdm-greeter. Tried dpkg-reconfigure on all major DM package - no success Looking for errors in PAM - no authentication errors Looking for errors in syslog ; org.gtk.vfs.Daemon[7528]: A connection to the bus can't be made seems same problem that Bug #1571206 reported by dino99 on 2016-04-16 but with different symptoms. Workaround ; put the system boot into text mode then "startx" works everytime (and doesn't trigger gvfs error) ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gvfs 1.28.2-1ubuntu1~16.04.1 ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19 Uname: Linux 4.4.0-38-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: MATE Date: Wed Sep 28 11:28:04 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2016-06-01 (118 days ago) InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: gvfs UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1628439/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1628439] [NEW] login loop on lightdm-greeter
Public bug reported: After an upgrade of the system not possible anymore to login using lightdm-greeter. Tried dpkg-reconfigure on all major DM package - no success Looking for errors in PAM - no authentication errors Looking for errors in syslog ; org.gtk.vfs.Daemon[7528]: A connection to the bus can't be made seems same problem that Bug #1571206 reported by dino99 on 2016-04-16 but with different symptoms. Workaround ; put the system boot into text mode then "startx" works everytime (and doesn't trigger gvfs error) ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gvfs 1.28.2-1ubuntu1~16.04.1 ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19 Uname: Linux 4.4.0-38-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: MATE Date: Wed Sep 28 11:28:04 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2016-06-01 (118 days ago) InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: gvfs UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gvfs (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial ** Attachment added: "This file describe the upgrade of the system - before apply it works, after it fails" https://bugs.launchpad.net/bugs/1628439/+attachment/4750058/+files/fuck4 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1628439 Title: login loop on lightdm-greeter Status in gvfs package in Ubuntu: New Bug description: After an upgrade of the system not possible anymore to login using lightdm-greeter. Tried dpkg-reconfigure on all major DM package - no success Looking for errors in PAM - no authentication errors Looking for errors in syslog ; org.gtk.vfs.Daemon[7528]: A connection to the bus can't be made seems same problem that Bug #1571206 reported by dino99 on 2016-04-16 but with different symptoms. Workaround ; put the system boot into text mode then "startx" works everytime (and doesn't trigger gvfs error) ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gvfs 1.28.2-1ubuntu1~16.04.1 ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19 Uname: Linux 4.4.0-38-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: MATE Date: Wed Sep 28 11:28:04 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2016-06-01 (118 days ago) InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: gvfs UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1628439/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1096286]
bug 348023 has some pointers to that. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1096286 Title: Firefox Search Engine is Broken Status in The Mozilla Firefox Browser: In Progress Status in “firefox” package in Ubuntu: Triaged Bug description: Firefox (package: firefox 17.0.1+build1-0ubuntu0.12.10.1) has several search engines pre-installed. One is labelled Chambers (UK). This search link is broken: When, for example, putting in the search term Test, then Firefox goes to the following URL www.chambersharrap.co.uk/chambers/chref/chref.py/main?query=Testtitle=21stsourceid =Mozilla-search This results in the display of an error page (HTTP Error 404 - File or directory not found). This error has been persistent for the past four weeks, suggesting a fundamentally broken search link. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1096286/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
