[Bug 1629543] Re: KDE does not start when using lightdm
I ran into the same problem in 20.04 after switching to lightdm and it took me a while to figure out. Just as Simon pointed out: /usr/share/lightdm/lightdm.conf.d/40-kde-plasma-kf5.conf should have: user-session=plasma instead of user-session=kde-plasma-kf5 since there is no kde-plasma-kf5.desktop in /usr/share/xsessions I understand that most people aren't switching the display manager but this is such an easy fix I'd hope that it's done to save a lot of frustration for the few that do. ** Changed in: plasma-workspace (Ubuntu) Status: Expired => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1629543 Title: KDE does not start when using lightdm To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plasma-workspace/+bug/1629543/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901606] Re: security update broke module import in libpam-python, "from httplib2 import Http" fails now
xenial fix verified, thanks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901606 Title: security update broke module import in libpam-python, "from httplib2 import Http" fails now To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pam-python/+bug/1901606/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901606] Re: security update broke module import in libpam-python, "from httplib2 import Http" fails now
note this also happens with the version of httplib2 installed from apt-get install python-httplib2 from the repositories, not just the version from pip I was using. pip2 install httplib2 installs the module into: /usr/local/lib/python2.7 /dist-packages and the python-httplib2 package installs it into: /usr/lib/python2.7 /dist-packages/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901606 Title: security update broke module import in libpam-python, "from httplib2 import Http" fails now To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pam-python/+bug/1901606/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901606] [NEW] security update broke module import in libpam-python, "from httplib2 import Http" fails now
Public bug reported: I glanced at the libpam-python 1.0.4-1.1+deb8u1build0.16.04.1 diff but it wasn't immediately obvious - why does this security update break importing httplib2 ? Other more standard imports like sys, os, datetime, don't seem to be a problem. Does this update change or restrict the python module paths? Here's the error that shows up in /var/log/auth.log Traceback (most recent call last): File "/lib/security/pam_pacauth.py", line 18, in from httplib2 import Http ImportError: No module named httplib2 Here's line 18 from my pam module: from httplib2 import Http To reproduce this ( on 16.04 ) just install httplib2 using: pip2 install httplib2 and then try to use a python pam module with this line in it: from httplib2 import Http With the older 1.0.4-1 version this has worked just fine for the past 4 years. ** Affects: pam-python (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901606 Title: security update broke module import in libpam-python, "from httplib2 import Http" fails now To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pam-python/+bug/1901606/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1783371] Re: ubuntu versions of libreoffice writer render and print some documents improperly, they show up with fewer/missing pages
output of ubuntu-bug attached, but as far as I can tell there is nothing system-specific about this bug, stock Ubuntu 18.04 is affected. ** Attachment added: "sudo ubuntu-bug --save lowriter.bug libreoffice-writer" https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1783371/+attachment/5167228/+files/lowriter.bug -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1783371 Title: ubuntu versions of libreoffice writer render and print some documents improperly, they show up with fewer/missing pages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1783371/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1783371] [NEW] ubuntu versions of libreoffice writer render and print some documents improperly, they show up with fewer/missing pages
Public bug reported: Libreoffice writer as packaged by Ubuntu is rendering and printing some documents incorrectly - differently than the debs from libreoffice and the versions for most other OSes. It is possibly triggered by lots of overlapping images that were pasted into the document. When you open the attached document it should show up as 7 pages. However with 6.0.3.2 ( 1:6.0.3-0ubuntu1 ) in the standard Ubuntu 18.04 repositories it briefly shows 1/7 pages in the lower left as the document loads and then switches to 1/5 pages, and only 5 pages show up and print. The same thing happens with 6.0.5.2 from the libreoffice fresh ppa and 6.0.6 from the prereleases ppa. This has been repeated using a clean 18.04 install, dist-upgraded. Between versions I remove --purge libreoffice* and delete. .config/libreoffice/. I filed this bug at libreoffice: https://bugs.documentfoundation.org/show_bug.cgi?id=118597 but then found out that the problem does not occur using a different OS like windows or redhat or debian or manjaro. ( linux mint shows the same behavior as Ubuntu). If you open that document with the .deb files downloaded directly from the libreoffice site and installed into /opt then the document renders as 7 pages. So it sure seems like this is an Ubuntu-specific bug. As mentioned in the libreoffice bug it is not as simple as a VCL gtk3 vs. gtk2 difference, I don't know what else is different between the ubuntu repository and ppa packages and the debs from libreoffice. The problem was initially discovered under Ubuntu 16.04 using 6.0.5.2 from the fresh ppa , some documents were showing as 7 pages but only 5 pages were printing, but only with certain printer ppds. The fact that the document displays as 7 vs. 5 pages is much easier to see and replicate and is hopefully related to the original printing missing pages problem. ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New ** Attachment added: "document that should be 7 pages but only renders as 5 on Ubuntu 18.04" https://bugs.launchpad.net/bugs/1783371/+attachment/5167227/+files/flowers-7-pages.odt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1783371 Title: ubuntu versions of libreoffice writer render and print some documents improperly, they show up with fewer/missing pages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1783371/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1767784] Re: [regression] output device not recognized anymore since update 1:8.0-0ubuntu3.9
1:8.0-0ubuntu3.10 from proposed fixes the problem ** Tags removed: verification-needed verification-needed-xenial ** Tags added: verification-done verification-done-xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1767784 Title: [regression] output device not recognized anymore since update 1:8.0-0ubuntu3.9 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1767784/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1768411] Re: pulseaudio 8.0-0ubuntu3.9 update broke sound on certain hardware, the dummy output profile is selected by default
I see now there is an option for additional attachments (one per comment) so I'm going to attache the files separately, here is the output of pacmd list sinks ** Attachment added: "pacmd-list.log" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1768411/+attachment/5131793/+files/pacmd-list.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768411 Title: pulseaudio 8.0-0ubuntu3.9 update broke sound on certain hardware, the dummy output profile is selected by default To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1768411/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1768411] Re: pulseaudio 8.0-0ubuntu3.9 update broke sound on certain hardware, the dummy output profile is selected by default
here is the default.pa ** Attachment added: "default.pa" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1768411/+attachment/5131794/+files/default.pa -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768411 Title: pulseaudio 8.0-0ubuntu3.9 update broke sound on certain hardware, the dummy output profile is selected by default To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1768411/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1768411] Re: pulseaudio 8.0-0ubuntu3.9 update broke sound on certain hardware, the dummy output profile is selected by default
here is the text from running: apport-cli -f -p pulseaudio --save bug.apport ** Attachment added: "bug.apport" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1768411/+attachment/5131795/+files/bug.apport -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768411 Title: pulseaudio 8.0-0ubuntu3.9 update broke sound on certain hardware, the dummy output profile is selected by default To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1768411/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1768411] [NEW] pulseaudio 8.0-0ubuntu3.9 update broke sound on certain hardware, the dummy output profile is selected by default
Public bug reported: I help manage a few hundred computers and since the last pulseaudio update a few weeks ago ( xenial-updates ) from pulseaudio_1%3a8.0-0ubuntu3.8_amd64.deb to pulseaudio_1%3a8.0-0ubuntu3.9_amd64.deb ( and libpulse0 ) certain hardware including dell models 755, 390, and 3050 lost sound. They were working fine for years but now the dummy output profile is selected by default. What happened? This can be worked around by explicitly setting: set-card-profile 0 output:analog-stereo set-sink-port 1 analog-output-headphones or by reverting back to pulseaudio_1%3a8.0-0ubuntu3.8_amd64.deb ( along with libpulse0 ) . When I try to use apport it gets to the end and says "apport cannot connect to crash database" but I have included example system details in the attachment after the output of pacmd list sinks and default.pa. ( You can only attach one file ?!?) ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Attachment added: "pacmd list sinks and default.pa and apport bug text contents" https://bugs.launchpad.net/bugs/1768411/+attachment/5131792/+files/pacmd-list-and-default-pa-and-apport-bug.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768411 Title: pulseaudio 8.0-0ubuntu3.9 update broke sound on certain hardware, the dummy output profile is selected by default To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1768411/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1742912] Re: Please confine guest sessions again
I figured out why the simple test didn't work - when I first installed Ubuntu 18.04, gnome-terminal wouldn't accept any keyboard input, I assumed it was just a pre-alpha bug and installed terminator. Installing terminator switched itself to the default including launching with ctrl-alt-t , and terminator does get apparmor restricted.When I paste in "cat /proc/self/attr/current" into a gnome-terminal it shows unconfined. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1742912 Title: Please confine guest sessions again To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1742912/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1742912] Re: Please confine guest sessions again
Please note that the simple test ( cat /proc/self/attr/current ) can be misleading. I tried that in Ubuntu 18.04 ( switched to lightdm ) and got "(enforce)" but some applications like the file manager could browse other user's home directories. Most applications including firefox and libreoffice are restricted. In Xubuntu the file manager is restricted as well as every other application I tried. Is it possible to just eliminate certain applications or prevent launching applications in specific ways to guarantee a restricted guest sessions? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1742912 Title: Please confine guest sessions again To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1742912/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1713751] Re: soft lockup / stall on CPU when shutting down with hwe 4.10 kernel
The problem no longer seems to be occurring anymore even with the 4.10.0-33-generic kernel. Since 2017-09-11 all of the affected machines have been getting automatic package updates and I'm guessing some non- kernel package has changed something that prevents the problem. I would like to know what fixed it and I could start reverting those package updates or start over with an old install, but for now as long as it is fixed it might not be worth investigating further. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1713751 Title: soft lockup / stall on CPU when shutting down with hwe 4.10 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1713751/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1713751] Re: soft lockup / stall on CPU when shutting down with hwe 4.10 kernel
There were no shutdown issues with 4.13.0-16-generic in 20 shutdowns - very promising. I am switching back to 4.10.0-33 now to make sure the problem still occurs and nothing else has changed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1713751 Title: soft lockup / stall on CPU when shutting down with hwe 4.10 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1713751/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1713751] Re: soft lockup / stall on CPU when shutting down with hwe 4.10 kernel
OK, I'm trying out 4.13.0-16-generic ( and extra ) from artful now on an 8 hour shutdown cycle, it may take a few days to know if the problem will occur. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1713751 Title: soft lockup / stall on CPU when shutting down with hwe 4.10 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1713751/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1713751] Re: soft lockup / stall on CPU when shutting down with hwe 4.10 kernel
The problem still occurs without a separate /tmp partition. Still experiencing the failure on Ubuntu linux-image-4.10.0-33-generic while 4.10.0-041000-generic is problem free. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1713751 Title: soft lockup / stall on CPU when shutting down with hwe 4.10 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1713751/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1713751] Re: soft lockup / stall on CPU when shutting down with hwe 4.10 kernel
I switched back to the Ubuntu linux-image-4.10.0-33-generic kernel and about 6 reboots later it happened again, so its definitely specific to the Ubuntu kernel. I was able to catch it right as it happened, the last thing before the NMI watchgdog messages occur is: [ OK ] Reached target Shutdown. The only errors visible on the screen are [FAILED] unmounting /tmp and /var , I always get the failure unmounting /var but not /tmp, maybe that is significant? I had /tmp on a separate partition, I removed its fstab entry so it will be on the / root partition, we'll see if that changes anything. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1713751 Title: soft lockup / stall on CPU when shutting down with hwe 4.10 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1713751/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1713751] Re: soft lockup / stall on CPU when shutting down with hwe 4.10 kernel
I've been running the 4.10.0-041000-generic upstream kernel for a week with 3 reboots a day and not a single problem - so the issue is probably in the Ubuntu kernel. What is the next step I should take to solve this? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1713751 Title: soft lockup / stall on CPU when shutting down with hwe 4.10 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1713751/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1713751] [NEW] soft lockup / stall on CPU when shutting down with hwe 4.10 kernel
Public bug reported: Instead of normal complete shutdowns we're getting soft lockup failures. This started when 16.04 hwe packages switched to the 4.10 kernel about a month ago. I help manage a few hundred machines spanning several different sites and several different hardware models and they're all experiencing this intermittently, approximately 5% get stuck on shutdown each day. Here is an example of what is on the screen after it happens, the machine is unresponsive and requires a hard reset. I can't see anything in syslog or dmesg that differs when this happens, I think all logging has stopped at this point in the shutdown. [54566.220003] ? (t=6450529 jiffies g=141935 c=141934 q=1288) [54592.092003] NMI watchdog: BUG: soft lockup - CPU#1 stuck for 22s! (systemd:1) [54620.092003] NMI watchdog: BUG: soft lockup - CPU#1 stuck for 22s! (systemd:1) [54648.092003] NMI watchdog: BUG: soft lockup - CPU#1 stuck for 22s! (systemd:1) [54676.092003] NMI watchdog: BUG: soft lockup - CPU#1 stuck for 22s! (systemd:1) [54704.092003] NMI watchdog: BUG: soft lockup - CPU#1 stuck for 22s! (systemd:1) [54732.092003] NMI watchdog: BUG: soft lockup - CPU#1 stuck for 22s! (systemd:1) [54746.232003] INFO: rcu_sched self-detected stall on CPU [54746.232003] ?1-...: (6495431 ticks this GP) idle=5c7/141/0 softirq=218389/218389 fqs=3247712 This repeats every ~ 22 seconds, sometimes it is stuck for 23s instead of 22: ... NMI watchdog: BUG: soft lockup - CPU#1 stuck for 23s! Reverting to 4.8.0-58 avoids the problem. I believe the problem has been present with every hwe 4.10 kernel package through the current linux-image-4.10.0-33-generic. This bug was filed with data right after it occurred with linux-image-4.10.0-33-generic. This only happens approximately 5% of the time with no discernible pattern. I am able to reproduce the issue on one particular machine by scheduling shutdowns 3 times per day and waiting up to a few days for the problem to occur. Shutting down and starting up more frequently, like every 5 minutes or even an hour, will not trigger the problem, it seems like the machine needs to be running for a while. It does not seem to depend on any user actions, it happens even if you never login. It has happened on reboots as as opposed to shutdowns as well. I found a few similar bug reports but nothing for these exact symptoms. I have tried blacklisting mei_me with no change in behavior. I'm not sure but the majority of the affected machines are using intel video chips. Next I am going to try a mainline 4.10 kernel. lsb_release -rd Description:Ubuntu 16.04.3 LTS Release:16.04 apt-cache policy linux-image-4.10.0-33-generic linux-image-4.10.0-33-generic: Installed: 4.10.0-33.37~16.04.1 Candidate: 4.10.0-33.37~16.04.1 Version table: *** 4.10.0-33.37~16.04.1 500 500 http://us.archive.ubuntu.com/ubuntu xenial-security/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.10.0-33-generic 4.10.0-33.37~16.04.1 ProcVersionSignature: Ubuntu 4.10.0-33.37~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-33-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CurrentDesktop: XFCE Date: Tue Aug 29 08:57:26 2017 SourcePackage: linux-hwe UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-hwe (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages xenial ** Attachment added: "soft-lockup-3.png" https://bugs.launchpad.net/bugs/1713751/+attachment/4940859/+files/soft-lockup-3.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1713751 Title: soft lockup / stall on CPU when shutting down with hwe 4.10 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1713751/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1598300] Re: CUPS web interface stops responding after a while
Johannes Martin (johannes-martin) wrote: Is CUPS some deprecated setting? Yes - "BrowseLocalProtocols CUPS" was valid in 12.04 ( what I upgraded from ) but not anymore. If you needed to add a BrowseLocalProtocols line as opposed to switching its value, it seems that this auto-shutdown feature is triggering off that option being present and assigned certain values. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1598300 Title: CUPS web interface stops responding after a while To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1598300/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1598300] Re: CUPS web interface stops responding after a while
(iiro) "Did you look the cups log to make sure that it really is the same problem?" Without any fixes I get these messages about 2 minutes after restarting cups and cupsd is no longer running: I [09/Feb/2017:04:08:47 -0600] Printer sharing is off and there are no jobs pending, will restart on demand. I [09/Feb/2017:04:08:47 -0600] Scheduler shutting down normally. After installing the proposed updates or switching to BrowseLocalProtocols dnssd those messages go away and cupsd stays running and client print jobs don't fail with "Connection error: Transport endpoint is not connected." (iiro) "but it's now too late to do anything" Assuming there is absolutely no way to fix bug 1642966, why not switch "-l" to "-f" in /lib/systemd/system/cups.service as an official fix? Is that the only way to completely disable this buggy feature? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1598300 Title: CUPS web interface stops responding after a while To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1598300/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1598300] Re: CUPS web interface stops responding after a while
This is a very serious bug that breaks network printing in certain configurations. To be clear: its not just that cups stops and the web interface is unavailable - it can lead to not being able to print as the print server looks like it is offline to the clients: D [09/Feb/2017:10:07:02 -0600] [Job 12] Connection error: Transport endpoint is not connected E [09/Feb/2017:10:07:02 -0600] [Job 12] The printer is not responding. I was running into this issue on some print servers but not others and in comparing the two cupsd.conf files I found out I can prevent the issue by changing BrowseLocalProtocols CUPS to BrowseLocalProtocols dnssd The real problem here is that a feature like this should have a clear and easy way to turn if off completely. I don't ever want cups on a print server stopping to save an insignificant amount of cpu cycles or memory or electricity! Applying the packages from xenial-proposed does fix it for me, but in my opinion this is a pretty serious issue that needs a quicker fix. I think the best fix at the moment is the suggestion from Andreas Krausz (kukorica) to change " the option "-l" to "-f" in /lib/systemd/system/cups.service." as it seems that is the only way to turn off this "feature". -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1598300 Title: CUPS web interface stops responding after a while To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1598300/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1427800] Re: Edit and Disconnect options greyed out after update
*** This bug is a duplicate of bug 1424119 *** https://bugs.launchpad.net/bugs/1424119 ** This bug has been marked a duplicate of bug 1424119 Edit Connections...now insensitive by default in network manager's menu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1427800 Title: Edit and Disconnect options greyed out after update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1427800/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1424119] Re: Edit Connections...now insensitive by default in network manager's menu
I have the same problem, my initial search found this bug report: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1427800 The easiest temporary fix is to install the old network-manager-gnome 9.4.1-0ubuntu2.3 deb, luckily I don't have my mirrors auto clean. Here is a copy, I just had the i386 version: http://open-sense.com/temp/network-manager-gnome_0.9.4.1-0ubuntu2.3_i386.deb I wish they would keep at least one older version kept in the repository pools, but I googled the exact file name and found these for i386 and amd64. I haven't tried them but they should work: https://launchpad.net/ubuntu/+source/network-manager-applet/0.9.4.1-0ubuntu2.3/+build/4503560/+files/network-manager-gnome_0.9.4.1-0ubuntu2.3_i386.deb http://launchpadlibrarian.net/137742895/network-manager-gnome_0.9.4.1-0ubuntu2.3_amd64.deb -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1424119 Title: Edit Connections...now insensitive by default in network manager's menu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1424119/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1190344] Re: lightdm is leaking FDs -fix
I just want to confirm this bug affects precise and precise-updates which is using lightdm 1.2.3 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1190344 Title: lightdm is leaking FDs -fix To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1190344/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 574899] Re: segmentation fault on shutdown caused by new 2.6.31-21 clockevents.c
Installed the mainline kernel linux- image-2.6.31-02063113-generic_2.6.31-02063113_i386.deb and problem does not occur. -- segmentation fault on shutdown caused by new 2.6.31-21 clockevents.c https://bugs.launchpad.net/bugs/574899 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 574899] Re: segmentation fault on shutdown caused by new 2.6.31-21 clockevents.c
David, as this only happens on some hardware it is unlikely to be testable except by those already experiencing the problem on their machines. I will gladly test but I need answers to the simple questions I posed a month ago in this bug report. -- segmentation fault on shutdown caused by new 2.6.31-21 clockevents.c https://bugs.launchpad.net/bugs/574899 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 574899] Re: segmentation fault on shutdown caused by new 2.6.31-21 clockevents.c
** Changed in: linux (Ubuntu) Status: Incomplete = New -- segmentation fault on shutdown caused by new 2.6.31-21 clockevents.c https://bugs.launchpad.net/bugs/574899 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 574899] Re: segmentation fault on shutdown caused by new 2.6.31-21 clockevents.c
I would like to help solve this but the cut-n-paste response leading to incomplete instructions didn't help, and I don't want this to just sit here until the bug auto expires. Can someone tell me which upstream kernel version I should be testing with to allow additional upstream developers to examine the issue ? -- segmentation fault on shutdown caused by new 2.6.31-21 clockevents.c https://bugs.launchpad.net/bugs/574899 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 574899] Re: segmentation fault on shutdown caused by new 2.6.31-21 clockevents.c
By latest upstream kernel do you mean http://kernel.ubuntu.com/~kernel-ppa/mainline/v2.6.31.13-karmic/ or the 2.6.34-rc version in http://kernel.ubuntu.com/~kernel-ppa/mainline/daily/current/ ? Why is there no 2.6.31.13-karmic image package built in that ppa? I looked at the source and the suspect clockevents.c in 2.6.31.13 is the same as 2.6.31.12 which ubuntu 2.6.31-21 is based on. If you want me to test with 2.6.31.13 I can build that kernel from source and test just to make sure the problem is still there, but I want to make sure that is the latest version you want tested before I go through that procedure. If you want me to try a 2.6.34-rc version, can you tell me why there are different entries in the ppa for karmic vs. lucid? Will the lucid ones not work on karmic? Sorry if that is a stupid question, I don't mess with kernels much anymore. The karmic 2.6.34-rc ppa entires like: http://kernel.ubuntu.com/~kernel-ppa/mainline/v2.6.34-rc3-karmic/ don't have an image built either. -- segmentation fault on shutdown caused by new 2.6.31-21 clockevents.c https://bugs.launchpad.net/bugs/574899 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 574899] [NEW] segmentation fault on shutdown caused by new 2.6.31-21 clockevents.c
Public bug reported: After upgrading to linux-image-2.6.31-21-generic last week (karmic- updates repository enabled), all of our Gateway E4300 machines end with a segmentation fault instead of shutting down properly and completely. Several other models of hardware are unaffected. This is consistently observed across several hundred machines. The 2.6.31-21.59 changelog includes this: * clockevents: Prevent clockevent_devices list corruption on cpu hotplug - LP: #509730 Reverting to linux-image-2.6.31-20-generic prevents the problem, as does booting with nolapic (but you lose SMP, or hyperthreading in the case of the E4300). Also, rebooting does not exhibit the problem, only halt. This appears to be the same or a nearly identical bug reported in the last few months in other distros: http://bugs.gentoo.org/show_bug.cgi?id=312767 http://lists.opensuse.org/opensuse-bugs/2010-02/msg01527.html https://bugzilla.kernel.org/show_bug.cgi?id=15005 https://bugzilla.redhat.com/show_bug.cgi?id=558231 But this is a new regression for Ubuntu. On the screen the message begins (hand transcribed by someone else): * Stopping early crypto disks... ...done. * Will now halt -[ cut here]-- ...kernel BUG at /build/buildd/linux-2.6.31/kernell/time/clockevents.c:262 ...invalid opcode: [#1] SMP and ends with: ... EIP: [c0168c1d] clockevents_notify+0xfd/0x110 SS:ESP ... ... [ end trace 66b1feeaae5006c8 ]--- Segmentation Fault ProblemType: Bug AplayDevices: List of PLAYBACK Hardware Devices card 0: Intel [HDA Intel], device 0: ALC880 Analog [ALC880 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gvuser16332 F pulseaudio CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0x502c irq 16' Mixer name : 'Realtek ALC880' Components : 'HDA:10ec0880,0860,0009' Controls : 20 Simple ctrls : 12 Date: Mon May 3 22:29:13 2010 DistroRelease: Ubuntu 9.10 HibernationDevice: RESUME=UUID=9e4b0515-e360-4a27-9cb5-bedaae20c5c2 InstallationMedia: Ubuntu 9.10 Karmic Koala - Release i386 (20091028.5) IwConfig: lono wireless extensions. eth0 no wireless extensions. MachineType: Gateway E4300 Package: linux-image-2.6.31-21-generic 2.6.31-21.59 ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.31-21-generic root=UUID=d9a85527-f97d-45e4-8d48-290d7bbbfe09 ro noquiet nosplash ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-21.59-generic RelatedPackageVersions: linux-backports-modules-2.6.31-21-generic N/A linux-firmware 1.26 RfKill: SourcePackage: linux Uname: Linux 2.6.31-21-generic i686 dmi.bios.date: 10/31/2005 dmi.bios.vendor: Intel Corp. dmi.bios.version: SE91510J.15A.2609.2005.1031.1237 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: D915GUX dmi.board.vendor: Intel Corporation dmi.board.version: AAC85199-203 dmi.chassis.asset.tag: NONE dmi.chassis.type: 3 dmi.chassis.vendor: Gateway dmi.chassis.version: WTN01A01 dmi.modalias: dmi:bvnIntelCorp.:bvrSE91510J.15A.2609.2005.1031.1237:bd10/31/2005:svnGateway:pnE4300:pvr4000983:rvnIntelCorporation:rnD915GUX:rvrAAC85199-203:cvnGateway:ct3:cvrWTN01A01: dmi.product.name: E4300 dmi.product.version: 4000983 dmi.sys.vendor: Gateway ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 -- segmentation fault on shutdown caused by new 2.6.31-21 clockevents.c https://bugs.launchpad.net/bugs/574899 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 574899] Re: segmentation fault on shutdown caused by new 2.6.31-21 clockevents.c
** Attachment added: AlsaDevices.txt http://launchpadlibrarian.net/47731678/AlsaDevices.txt ** Attachment added: ArecordDevices.txt http://launchpadlibrarian.net/47731679/ArecordDevices.txt ** Attachment added: BootDmesg.txt http://launchpadlibrarian.net/47731680/BootDmesg.txt ** Attachment added: Card0.Amixer.values.txt http://launchpadlibrarian.net/47731681/Card0.Amixer.values.txt ** Attachment added: Card0.Codecs.codec.2.txt http://launchpadlibrarian.net/47731682/Card0.Codecs.codec.2.txt ** Attachment added: CurrentDmesg.txt http://launchpadlibrarian.net/47731683/CurrentDmesg.txt ** Attachment added: Dependencies.txt http://launchpadlibrarian.net/47731684/Dependencies.txt ** Attachment added: Lspci.txt http://launchpadlibrarian.net/47731685/Lspci.txt ** Attachment added: Lsusb.txt http://launchpadlibrarian.net/47731686/Lsusb.txt ** Attachment added: PciMultimedia.txt http://launchpadlibrarian.net/47731687/PciMultimedia.txt ** Attachment added: ProcCpuinfo.txt http://launchpadlibrarian.net/47731688/ProcCpuinfo.txt ** Attachment added: ProcInterrupts.txt http://launchpadlibrarian.net/47731689/ProcInterrupts.txt ** Attachment added: ProcModules.txt http://launchpadlibrarian.net/47731690/ProcModules.txt ** Attachment added: UdevDb.txt http://launchpadlibrarian.net/47731691/UdevDb.txt ** Attachment added: UdevLog.txt http://launchpadlibrarian.net/47731692/UdevLog.txt ** Attachment added: WifiSyslog.txt http://launchpadlibrarian.net/47731693/WifiSyslog.txt -- segmentation fault on shutdown caused by new 2.6.31-21 clockevents.c https://bugs.launchpad.net/bugs/574899 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 44166] Re: No NTP-Sync during bootup if /usr on different filesystem
This is still broken in Ubuntu 9.10. I don't know what the root cause was going back to 6.06 but here is what is going on in 9.10. I can't believe the importance is low, this probably affects every single server installation. I am tempted to file a new bug as this one is so old and it looks like Ubuntu just doesn't care. ntpdate is supposed to be automatically run after a network connection is available, started by the script: /etc/network/if-up.d/ntpdate If /usr/ is on a separate partition from /, as most servers would do, the network can be up before non-root partitions are mounted. To deal with that, there is this section: # This is for the case that /usr will be mounted later. if [ -r /lib/udev/hotplug.functions ]; then . /lib/udev/hotplug.functions wait_for_file /usr/sbin/ntpdate-debian fi however /lib/udev/hotplug.functions does not exist, so it doesn't wait for /usr/ to be mounted, and the time never gets synced because /usr/sbin/ntpdate-debian is on the /usr/ partition which is not mounted yet. hotplug.functions does not exist in any Ubuntu package as far as I can tell, but it is in the udev package of Debian Lenny. I found some other bugs referencing /lib/udev/hotplug.functions so there is probably a bigger problem than just broken ntpdate functionality. In trying to make the boot process a few seconds faster and win over new linux users, Ubuntu has broken all sorts of functionality that the core linux audience depends on. -- No NTP-Sync during bootup if /usr on different filesystem https://bugs.launchpad.net/bugs/44166 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 44166] Re: No NTP-Sync during bootup if /usr on different filesystem
the problem is either in the ntpdate or udev package, how do we get this bug moved to the correct package? -- No NTP-Sync during bootup if /usr on different filesystem https://bugs.launchpad.net/bugs/44166 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 496640] Re: iwlagn WLAN no longer works after upgrade to 2.6.31-17
same problem, with a 5100 card. working under 2.6.31-16: zcat /var/log/dmesg.2.gz | grep iwlag | cut -c 16-999 iwlagn: Intel(R) Wireless WiFi Link AGN driver for Linux, 1.3.27k iwlagn: Copyright(c) 2003-2009 Intel Corporation iwlagn :20:00.0: PCI INT A - GSI 16 (level, low) - IRQ 16 iwlagn :20:00.0: setting latency timer to 64 iwlagn :20:00.0: Detected Intel Wireless WiFi Link 5100AGN REV=0x54 iwlagn :20:00.0: Tunable channels: 13 802.11bg, 24 802.11a channels iwlagn :20:00.0: irq 33 for MSI/MSI-X iwlagn :20:00.0: firmware: requesting iwlwifi-5000-2.ucode iwlagn :20:00.0: loaded firmware version 8.24.2.12 not working under 2.6.31-17: (iwlist scanning works intermittently, but can't acquire dhcp address) zcat /var/log/dmesg.1.gz | grep iwlag | cut -c 16-999 iwlagn: Intel(R) Wireless WiFi Link AGN driver for Linux, 1.3.27ks iwlagn: Copyright(c) 2003-2009 Intel Corporation iwlagn :20:00.0: PCI INT A - GSI 16 (level, low) - IRQ 16 iwlagn :20:00.0: setting latency timer to 64 iwlagn :20:00.0: Detected Intel Wireless WiFi Link 5100AGN REV=0x54 iwlagn :20:00.0: Tunable channels: 13 802.11bg, 24 802.11a channels iwlagn :20:00.0: irq 33 for MSI/MSI-X iwlagn :20:00.0: firmware: requesting lbm-iwlwifi-5000-2.ucode iwlagn :20:00.0: lbm-iwlwifi-5000-2.ucode firmware file req failed: -2 iwlagn :20:00.0: firmware: requesting lbm-iwlwifi-5000-1.ucode iwlagn :20:00.0: Loaded firmware lbm-iwlwifi-5000-1.ucode, which is deprecated. Please use API v2 instead. iwlagn :20:00.0: loaded firmware version 8.24.2.12 -- iwlagn WLAN no longer works after upgrade to 2.6.31-17 https://bugs.launchpad.net/bugs/496640 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 445256] Re: Wrong path to X server in gdm.conf
sed -i 's/X11R6\///' /etc/gdm/gdm.conf -- Wrong path to X server in gdm.conf https://bugs.launchpad.net/bugs/445256 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 459998] Re: davfs kernoops can't mount partition as user
yes, this is a problem. until there is a legitimate fix I'm going to do without the oops tracker: apt-get remove kerneloops-daemon perl -ni -e 'print unless /kernoops/' /etc/passwd I could maybe see this being a bug of kerneloops-daemon since / is not really a home directory in the traditional sense, but on the other hand davfs2 policy is not ideal since there are many unusual but technically possible assignments of home directories. I would rather see davfs2 restrict mounting in a better way, maybe only on directories that the user has write permission on regardless of where it is in the filesystem. -- davfs kernoops can't mount partition as user https://bugs.launchpad.net/bugs/459998 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 441100] Re: within chroot, can fail to reload daemon configuration if not running (detects dbus daemon outside of chroot)
The title of this bug is a little confusing, I am trying to deal with this bug and I almost filed a separate bug with this description: Upgrades of the dbus package fail unless dbus is running This is a problem for a number of reasons: 1. if you are running in a chroot, dbus upgrades fail. I imagine this is a problem in other similar installation or maintenance scenarios, including the uck package (Ubuntu Customization Kit) 2. if somehow dbus got broken and couldn't start, you could never reinstall or upgrade it to fix the problem This can sometimes be worked around by binding /var/run/dbus on the host system, but what is the upgrade doing over the bus that should really be happening to the chroot system? If it is nothing important the package should not die on the error, and if it is important then the package should be updated to store the necessary bus commands and run them the next time the bus is active. This was a somewhat smaller problem in Jaunty and earlier Ubuntu releases that could easily be worked around by explicitly starting dbus in the chroot, but now with recent init script updates it detects the dbus process from the host system and won't start in the chroot. This issue needs to be formally addressed. error log: Setting up dbus (1.2.16-0ubuntu9) ... Installing new version of config file /etc/dbus-1/system.conf ... The system user `messagebus' already exists. Exiting. Failed to open connection to system message bus: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory dpkg: error processing dbus (--configure): -- within chroot, can fail to reload daemon configuration if not running (detects dbus daemon outside of chroot) https://bugs.launchpad.net/bugs/441100 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 195666] Re: Allow pressing escape to see boot messages
So after this fix, how do you make truly verbose startup messages occur without hitting ESC? Maybe this is a different bug, but removing the quiet and splash parameters in karmic doesn't make things as verbose as it should (and used to). Hitting ESC as recently as the 9.10 RC live CD showed verbose information (all stdout/stderr output by init scripts), but now after this fix hitting ESC kills startup processes potentially causing big problems, for example trying to hit ESC I've gotten messages like: mountall: Cancelled General error mounting filesystems Even with the quiet and splash boot parameters removed in karmic, (and even with usplash uninstalled) you only get the basic messages output by commands like log_begin_message and not anything sent to stdout or stderr like you would in jaunty and all previous releases. If they're just going to a different virtual terminal I couldn't find them there either. So how can I see ALL messages from the init scripts now that the ESC key functionality has essentially been taken away? -- Allow pressing escape to see boot messages https://bugs.launchpad.net/bugs/195666 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
