[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1957711 Title: Switching users causes system crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1957711/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1954939 Title: Cannot open additional instances of the same file with the same name inside a zip archive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/1954939/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1954939 Title: Cannot open additional instances of the same file with the same name inside a zip archive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/1954939/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940534] [NEW] Notifications, Panel, Icons are all biased towards left monitor.
Public bug reported: As explained on this thread with the Xubuntu twitter manager: https://twitter.com/ZanaGB/status/1427328542786920454 The panel, icons, and notifications all defy the primary monitor setting, and instead get biased towards the left. Monitor orientation is irrelevant to the issue. Both monitors are 1440 pixels in height when they're both placed in landscape. On first boot after install ( cannot test on live environment. Propietary NVidia drivers are needed as Noveau produces no output. ) the panel, icons, and notifications will be correctly shown on the right monitor. Opening the display preferences pane and doing ANY change to the layout will make everything migrate to the left monitor. Setting the primary monitor toggle on the display does nothing. Changing the orientation of the left display to portrait or landscape does nothing. Everything stays on the left monitor. Changing the secondary monitor to be on the right, regardless of orientation, fixes the issue. Whichever monitor is on the left, is the monitor where everything will be Manually setting the output property inside panel preferences will forcefully change the panel. Everything else will still not follow. https://youtu.be/ZJIL87Jmr9Y From the aforementioned thread. A video demonstrating the issue. The bug may be related to bug #1596751, on which, despite the user's first port mentions "rightmost". The rest of the posts and the attached evidence shows that the panels stay to the "leftmost" monitor. This in turn may be a descendant of Bug #8328 on the old XFCE bug tracker, and https://forum.xfce.org/viewtopic.php?id=6440 this 2011 entry on the official XFCE forums detailing the same exact issue. As a result of the Xubuntu's twitter and I's back and forth and the delays implied in that. I have since installed a different distribution to suit my needs. Installing to a ejectable drive multiple times resulted on the installer crashing halfway through the process. So i can't boot from any secondary media to further testing. I will happily provide additional testing if there's a way to get the latest nvidia-driver metapackage ( and corresponding kernel modules ) working directly into the live installer. ** Affects: xubuntu-meta (Ubuntu) Importance: Undecided Status: New ** Tags: monitor primary xfce -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940534 Title: Notifications, Panel, Icons are all biased towards left monitor. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xubuntu-meta/+bug/1940534/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1889250] Re: Unable to calculate the upgrade to 20.04 due to nodejs from nodesource
@eyallior not exactly the same, I don't get; ... INFO failed to remove python-minimal ... INFO failed to remove libpython-stdlib my case seems worst that your! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1889250 Title: Unable to calculate the upgrade to 20.04 due to nodejs from nodesource To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1889250/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1889250] Re: Unable to calculate the upgrade to 20.04 due to nodejs from nodesource
@Daniel, after cleanning a LOT (removing everything from /etc/apt/source.list.d/ and expurging /etc/apt/source.list this is what i get... Any idea? (I'm afraid I must remove python-minimal... and so remove mate*!) ** Attachment added: "do-release-upgrade.log.tgz" https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1889250/+attachment/5429613/+files/do-release-upgrade.log.tgz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1889250 Title: Unable to calculate the upgrade to 20.04 due to nodejs from nodesource To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1889250/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1889250] Re: Unable to calculate the upgrade to 20.04 due to nodejs from nodesource
@Daniel, Here it is. Thank you! ** Attachment added: "apt.log.tgz" https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1889250/+attachment/5429607/+files/apt.log.tgz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1889250 Title: Unable to calculate the upgrade to 20.04 due to nodejs from nodesource To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1889250/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1889250] Re: Unable to calculate the upgrade to 20.04 due to nodejs from nodesource
Hello Daniel, I ran ppa-purge on them. Do you have an idea how to detect the packages causing the trouble? Thank you! Guillaume -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1889250 Title: Unable to calculate the upgrade to 20.04 due to nodejs from nodesource To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1889250/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1889250] Re: Unable to calculate the upgrade to 20.04 due to nodejs from nodesource
I disabled all my PPA's... I still cannot do-release-upgrade grep Broken /var/log/dist-upgrade/apt.log |wc 1405 17699 153251 Does it mean i have to remove all "Broken" 1405 packages ?! Thank you for your help! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1889250 Title: Unable to calculate the upgrade to 20.04 due to nodejs from nodesource To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1889250/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1889250] Re: Unable to calculate the upgrade to 20.04 due to nodejs from nodesource
Hi Brian, I did remove nodejs and related packages and I tried again. The result is the same. I'll open a new bug report. Where did you check to say nodejs was responsible? Thanks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1889250 Title: Unable to calculate the upgrade to 20.04 due to nodejs from nodesource To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1889250/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1898358] Re: do-release-upgrade to focal failed due to non standard (undetectable) packages on the system !
*** This bug is a duplicate of bug 1889250 *** https://bugs.launchpad.net/bugs/1889250 Hi Brian, I did remove nodejs and related packages and I tried again. The result is the same. I'll open a new bug report. Where did you check to say nodejs was responsible? Thanks. Guillaume Le 05/10/2020 à 23:50, Brian Murray a écrit : > *** This bug is a duplicate of bug 1889250 *** > https://bugs.launchpad.net/bugs/1889250 > > Reviewing the files from your upgrade attempt you have installed nodejs > from a location other than the offical Ubuntu archive. This version of > nodejs is greater than the one in the official archive and is keeping > some python packages installed which then prevents the upgrade from > being calculated. Please remove nodejs along with any other packages > from that archive and disable the archive. After that you can try > upgrading again and if it still fails open a new bug report. Thanks and > good luck! > > ** Changed in: ubuntu-release-upgrader (Ubuntu) >Status: Confirmed => Invalid > > ** Tags added: nodesource-nodejs > > ** This bug has been marked a duplicate of bug 1889250 >Unable to calculate the upgrade to 20.04 due to nodejs from nodesource > -- Guillaume Ballet https://keys.openpgp.org que...@laposte.net 36DAA9ACBCECCBBF15F7A53AF4F5B83C70C3788C -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1898358 Title: do-release-upgrade to focal failed due to non standard (undetectable) packages on the system ! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1898358/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1898358] Re: do-release-upgrade to focal failed due to non standard (undetectable) packages on the system !
The system is ; >$ lsb_release -a LSB Version: core-9.20170808ubuntu1-noarch:printing-9.20170808ubuntu1-noarch:security-9.20170808ubuntu1-noarch Distributor ID: Ubuntu Description:Ubuntu 18.04.5 LTS Release:18.04 Codename: bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1898358 Title: do-release-upgrade to focal failed due to non standard (undetectable) packages on the system ! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1898358/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1898358] [NEW] do-release-upgrade to focal failed due to non standard (undetectable) packages on the system !
Public bug reported: do-release-upgrade to focal failed because non standard (and non detectable) packages on the system. > sudo apt-mark unhold ... sudo ppa-purge ... sudo apt updated sudo apt upgrade sudo do-release-upgrade ... Vérification du gestionnaire de paquets Lecture des listes de paquets… Terminé Construction de l'arbre des dépendances Lecture des informations d'état… Terminé Calcul des modifications en cours Calcul des modifications en cours Impossible d'évaluer la mise à niveau Un problème insoluble est survenu lors du calcul de la mise à niveau. Cela a probablement été causé par : * des paquets logiciels non officiels qui ne proviennent pas d’Ubuntu. Veuillez utiliser la commande « ppa-purge » du paquet « ppa-purge » afin de supprimer les paquets d’un dépôt PPA Launchpad, puis essayez de relancer la mise à niveau. Si rien de tout cela ne s'applique, signalez ce bogue à l'aide de la commande « ubuntu-bug ubuntu-release-upgrader-core » dans un terminal. Si vous souhaitez analyser le problème par vous-même, les fichiers journaux contenus dans le répertoire « /var/log/dist-upgrade » contiennent les informations sur la mise à niveau. Plus précisément, veuillez consulter les journaux « main.log » et « apt.log ». Restauration du système dans son état d'origine Annulation Lecture des listes de paquets… Terminé Construction de l'arbre des dépendances Lecture des informations d'état… Terminé === Command detached from window (Sat Oct 3 14:40:18 2020) === === Command terminated with exit status 1 (Sat Oct 3 14:40:28 2020) === Nothing wrong on cat /var/log/dist-upgrade/apt.log cryptic error on /var/log/dist-upgrade/main.log ... 2020-10-03 14:40:15,979 ERROR Dist-upgrade failed: 'E:Erreur, pkgProblem::Resolve a généré des ruptures, ce qui a pu être causé par les paquets devant être gardés en l'état.' ... ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-release-upgrader-core 1:18.04.38 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: vtsspp sep5 socperf3 pax nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.17 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: MATE Date: Sat Oct 3 14:47:18 2020 InstallationDate: Installed on 2017-03-07 (1305 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader UpgradeStatus: Upgraded to bionic on 2020-10-03 (0 days ago) ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic dist-upgrade -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1898358 Title: do-release-upgrade to focal failed due to non standard (undetectable) packages on the system ! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1898358/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1085706 Title: pam_ecryptfs: seteuid error To manage notifications about this bug go to: https://bugs.launchpad.net/ecryptfs/+bug/1085706/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1628439] Re: login loop on lightdm-greeter
Not a bug. corrupted xinputrc -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1628439 Title: login loop on lightdm-greeter To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1628439/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1628439 Title: login loop on lightdm-greeter To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1628439/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1079552 Title: Unexpectedly asks for authentication halfway through file restore process To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1079552/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1628439 Title: login loop on lightdm-greeter To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1628439/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1628439 Title: login loop on lightdm-greeter To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1628439/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1628439 Title: login loop on lightdm-greeter To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1628439/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 806761] Re: Feature Request: Upstart scripts for nslcd
Our nslcd (0.8.4) keeps crashing on Ubuntu 12.04, like so: [2221821.130260] nslcd[17641]: segfault at 0 ip 004159c8 sp 7f11fd78b6a0 error 4 in nslcd[40+21000] [4448958.894131] nslcd[31759]: segfault at 0 ip 004159c8 sp 7fa87d3826a0 error 4 in nslcd[40+21000] and then it does not restart. Would having a /etc/init/nslcd.conf (with an appropriate respawn) fix this issue, or is there a way to fix it within the old 'service' framework? Any help would be appreciated - whenever it crashes (which happens every few weeks) some user with a local account has to log on and restart it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/806761 Title: Feature Request: Upstart scripts for nslcd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nss-pam-ldapd/+bug/806761/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1096286]
bug 348023 has some pointers to that. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1096286 Title: Firefox Search Engine is Broken To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1096286/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 994749] Re: checkfs run on already mounted filesystem, preventing boot
Ok, I purged ureadahead, the problem persists. Attached is an updated bootchart, which also shows a process called 'mountall' running before 30checkfs.sh ** Attachment added: "bootchart that runs mountall before 30checkfs.sh" https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/994749/+attachment/3132696/+files/theta-precise-20120505-2.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/994749 Title: checkfs run on already mounted filesystem, preventing boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/994749/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 994749] Re: checkfs run on already mounted filesystem, preventing boot
I'm not sure why you flagged this as 'util-linux" I think the culprit may be ureadahead Please see the attached bootchart. ureadahead calls mountall before 30checkfs.sh runs. Why? ** Attachment added: "theta-precise-20120505-1.png" https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/994749/+attachment/3132695/+files/theta-precise-20120505-1.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/994749 Title: checkfs run on already mounted filesystem, preventing boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/994749/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 994749] Re: checkfs run on already mounted filesystem, preventing boot
I did some further sleuthing. Here's the excerpt from dmesg where sda4/sda2 are mounted: [ 13.278025] nvidia :01:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16 [ 13.278033] nvidia :01:00.0: setting latency timer to 64 [ 13.278036] vgaarb: device changed decodes: PCI::01:00.0,olddecodes=io+mem,decodes=none:owns=io+mem [ 13.278145] NVRM: loading NVIDIA UNIX x86_64 Kernel Module 295.40 Thu Apr 5 21:37:00 PDT 2012 [ 13.487250] EXT4-fs (sda1): re-mounted. Opts: errors=remount-ro [ 13.973519] EXT4-fs (sda2): mounted filesystem with ordered data mode. Opts: (null) [ 14.168728] EXT4-fs (sda4): mounted filesystem with ordered data mode. Opts: (null) [ 14.315352] EXT4-fs (sdb3): warning: checktime reached, running e2fsck is recommended [ 14.321058] EXT4-fs (sdb3): mounted filesystem with ordered data mode. Opts: (null) [ 14.344202] init: failsafe main process (1163) killed by TERM signal [ 14.401456] Bluetooth: Core ver 2.16 Note the 'failsafe main process killed by TERM signal'... Could it be that you're mounting the sda2/sda4 partitions just temporarily, but then fail to unmount them? On a related note, I need to update the bug report. On 10.04, before upgrading to 12.04, I was able to Ctrl-Alt-F7 to reach the maintenance shell and kill it. But sshd didn't start. On 12.04, I'm no longer able to Ctrl-Alt out of plymouth (no getty has been started), but at least sshd has now started, allowing my to log on remotely and kill the maintenance shell. Am I right that the 'failsafe main process ... killed by TERM signal' may be the culprit? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/994749 Title: checkfs run on already mounted filesystem, preventing boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/994749/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 994749] [NEW] checkfs run on already mounted filesystem, preventing boot
Public bug reported: I had Ubuntu 10.04 LTS installed, now upgraded to 12.04 Precise. When the system enters run state 'S', it attempts to fsck two mounted file systems. This causes it to drop into a maintenance shell, preventing other system services (sshd, etc. etc. ) from starting until the maintenance is entered. However, it does progress to running gdm and gives a prompt to login (X is running on tty1 then). Ctrl-Alt-F7 leads to the maintenance shell, exiting it makes the boot complete. /var/log/checkfs is -- Log of fsck -C -R -A -a Fri May 4 15:40:13 2012 fsck from util-linux 2.19.1 /dev/sda2 is mounted. e2fsck: Cannot continue, aborting. /dev/sda4 is mounted. e2fsck: Cannot continue, aborting. fsck died with exit status 8 Fri May 4 15:40:13 2012 My /etc/fstab: proc/proc procnodev,noexec,nosuid 0 0 /dev/sda1 / ext4errors=remount-ro 0 1 /dev/sda2 /home ext4defaults0 2 UUID=02e8ad70-9e55-41e3-85be-42d7edf07c5e /optext4defaults 0 2 /dev/sda3 noneswapsw 0 0 /dev/sdb3 /media/gbackext4rw 0 0 (The device with UUID=02e... is /dev/sda4). My question: how in the world can it happen that your checkfs.sh runs 'fsck -C -R -A -a' *apparently after* you've mounted all configured filesystems read-write? This would fail deterministically, as it does for me. Clearly, something must be wrong with my installation, but what? I did not make any changes to /etc/rc*/* Any insights/hints for what I could try? As is, I can't reboot the machine remotely because it never gets to starting the network/sshd, which is highly annoying. I need to physically exit the maintenance shell. ** Affects: ubuntu Importance: Undecided Status: New ** Tags: boot checkfs failure maintenance shell -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/994749 Title: checkfs run on already mounted filesystem, preventing boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/994749/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 748550] Re: Dash Icons are too large
*** This bug is a duplicate of bug 735509 *** https://bugs.launchpad.net/bugs/735509 I don't agree that this problem is a duplicate of #73509. I'm using Ubuntu 11.10 and have resorted to the "classic" gnome desktop to avoid this probem in the unity desktop. The problem here is that the application icons are so large that only 8 (eight) will fit on my 10" netbook screen (in two rows of 4). With over a hundred applications, this means a lot of scrolling to find what I want. By comparison, my 3.5" smartphone screen shows 20 icons on one screen. Icons and text should be independent. In fact the whole point of icons (my opinion) is to not need text. I would request that the icon size be a user option with a wide range of size values, and the descriptive text only be shown as a mouse-over, to help when learning to recognise the icons. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/748550 Title: Dash Icons are too large To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/748550/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 793226] Re: package linux-image-2.6.32-31-generic 2.6.32-31.61 failed to install/upgrade: grub-probe fails for NFS root filesystem
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/793226 Title: package linux-image-2.6.32-31-generic 2.6.32-31.61 failed to install/upgrade: grub-probe fails for NFS root filesystem -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 793226] [NEW] package linux-image-2.6.32-31-generic 2.6.32-31.61 failed to install/upgrade: grub-probe fails for NFS root filesystem
Public bug reported: Binary package hint: grub2 Please don't bail if / is not a mounted hard drive. Just ignore the failure. (I'm running a diskless Ubuntu install. Upgrading Setting up linux-image-2.6.32-31-generic (2.6.32-31.61) ... Running depmod. update-initramfs: Generating /boot/initrd.img-2.6.32-31-generic Running postinst hook script /usr/sbin/update-grub. /usr/sbin/grub-probe: error: cannot find a device for / (is /dev mounted?). Perhaps the postinst hook script could test for this condition or simply proceed. Just update the initramfs and vmlinuz files - I'll copy them over to where my tftp server keeps them. Thanks. ProblemType: Package DistroRelease: Ubuntu 10.04 Package: linux-image-2.6.32-31-generic 2.6.32-31.61 ProcVersionSignature: Ubuntu 2.6.32-30.59-generic 2.6.32.29+drm33.13 Uname: Linux 2.6.32-30-generic i686 NonfreeKernelModules: nvidia AptOrdering: linux-image-2.6.32-31-generic: Configure linux-image-2.6.32-32-generic: Configure linux-image-generic: Configure linux-generic: Configure Architecture: i386 Date: Sun Jun 5 14:42:53 2011 ErrorMessage: subprocess installed post-installation script returned error exit status 1 SourcePackage: grub2 Title: package linux-image-2.6.32-31-generic 2.6.32-31.61 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 ** Affects: grub2 (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 lucid ubuntu-une -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/793226 Title: package linux-image-2.6.32-31-generic 2.6.32-31.61 failed to install/upgrade: grub-probe fails for NFS root filesystem -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
RE: [Bug 627191] Re: no cursor when coming out of sleep
no i can't see the cursor at all > Date: Tue, 31 Aug 2010 03:17:58 + > From: a...@alexandos.org > To: gsavag...@hotmail.com > Subject: [Bug 627191] Re: no cursor when coming out of sleep > > Thank you for taking the time to report this bug and helping to make > Ubuntu better. Unfortunately, we cannot work on this bug because your > description didn't include enough information. What exactly happens when > you pull the laptop out of sleep? Is it a screen something like this: > http://toastytech.com/guis/ubuntu10lock.png ? > > ** Changed in: ubuntu >Status: New => Incomplete > > -- > no cursor when coming out of sleep > https://bugs.launchpad.net/bugs/627191 > You received this bug notification because you are a direct subscriber > of the bug. > > Status in Ubuntu: Incomplete > > Bug description: > when i pull my laptop out of sleep i can't see the cursor > > To unsubscribe from this bug, go to: > https://bugs.launchpad.net/ubuntu/+bug/627191/+subscribe -- no cursor when coming out of sleep https://bugs.launchpad.net/bugs/627191 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 627191] [NEW] no cursor when coming out of sleep
Public bug reported: when i pull my laptop out of sleep i can't see the cursor ** Affects: ubuntu Importance: Undecided Status: New -- no cursor when coming out of sleep https://bugs.launchpad.net/bugs/627191 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 239351] Re: missing alsa installation file during apt-get dist-upgrade crashes whole upgrade...
I would like to close the thread - because I redid the system. Thanks. On Fri, Oct 31, 2008 at 4:08 AM, IanW <[EMAIL PROTECTED]> wrote: > Thank you for taking the time to report this bug and helping to make > Ubuntu better. You reported this bug a while ago and there hasn't been > any activity in it recently. We were wondering is this still an issue > for you? Can you try with latest Ubuntu release? Thanks in advance. > > ** Changed in: ubuntu > Status: New => Incomplete > > -- > missing alsa installation file during apt-get dist-upgrade crashes whole > upgrade... > https://bugs.launchpad.net/bugs/239351 > You received this bug notification because you are a direct subscriber > of the bug. > > Status in Ubuntu: Incomplete > > Bug description: > Failed to fetch > http://archive.ubuntu.com/ubuntu/pool/main/e/esound/libesd-alsa0_0.2.38-0ubuntu9_i386.deb > Error reading from server - read (104 Connection reset by peer) [IP: > 91.189.88.31 80] > > After letting apt-get dist-upgrade run the entire afternoon and night, and > waking up to realise just this had made it fail is kind of frustrating. > Tried to ping the IP address given, but not available. Port 80 also not. > -- missing alsa installation file during apt-get dist-upgrade crashes whole upgrade... https://bugs.launchpad.net/bugs/239351 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 239351] Re: missing alsa installation file during apt-get dist-upgrade crashes whole upgrade...
Oh, but it does work as a link... I can manage to download it from firefox say. -- missing alsa installation file during apt-get dist-upgrade crashes whole upgrade... https://bugs.launchpad.net/bugs/239351 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 239351] [NEW] missing alsa installation file during apt-get dist-upgrade crashes whole upgrade...
Public bug reported: Failed to fetch http://archive.ubuntu.com/ubuntu/pool/main/e/esound /libesd-alsa0_0.2.38-0ubuntu9_i386.deb Error reading from server - read (104 Connection reset by peer) [IP: 91.189.88.31 80] After letting apt-get dist-upgrade run the entire afternoon and night, and waking up to realise just this had made it fail is kind of frustrating. Tried to ping the IP address given, but not available. Port 80 also not. ** Affects: ubuntu Importance: Undecided Status: New -- missing alsa installation file during apt-get dist-upgrade crashes whole upgrade... https://bugs.launchpad.net/bugs/239351 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 123574] Re: Upgrade strongswan to latest version
** Also affects: strongswan (Baltix) Importance: Undecided Status: New -- Upgrade strongswan to latest version https://bugs.launchpad.net/bugs/123574 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
