[Bug 184711] Re: network-admin error: The interface does not exist
Variant here: Running Hardy. I needed to change from 100MBps to 1000MBps. Shutdown, replaced the Intel Pro/100 NIC (removed it) for a Pro/1000, fixed the DHCP so the machine kept the same IP. At reboot, the machine had detected the new NIC and assigned it to eth1. The network worked. But the "Configure" button in Networks Tools behaved as reported here. Incidentally, /etc/network/interfaces was still referencing eth0. Changing it to eth1 didn't make anything better (even after a reboot) - at least anything obvious. I manually put eth0 back in interfaces, shutdown, removed the Pro/1000 for the original e100b NIC, fixed the DHCP server accordingly: The machine went back to using eth0. But the problem persisted (same "The interface does not exist" message. So it looks like I'm just in the same situation as anyone else here. I might just have got there using a slightly different path. -- network-admin error: The interface does not exist https://bugs.launchpad.net/bugs/184711 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 184711] Re: network-admin error: The interface does not exist
I see the same here.
I would add that system > administration > network works.
The only thing that doesn't work (at least here) is gnome-nettool, either
command line or as in
system > administration > network tools > {Select interface} > {Configure
button>}
It then yelds the infamous "The interface does not exist".
As a side note, I think there is something strange in the interface handling
logic when one changes the NIC, anyway. This might or might not be related to
the bug we're talking about, but the contents of /etc/network/interfaces
after a NIC change doesn't seem to be what it should be, and it takes a few
reboots (with the machine coming up with no interface at all) and manual fixing
of the /etc/network/interfaces fix before things get back to normal, and
stable. When the machine comes up with no interface at all, I see that
something has removed all but the loopback device from /etc/network/interfaces.
I'm trying to understand what goes on there.
Might also be related to what udev does: I've noticed that if I manually load
my enet driver at early boot (i.e. while still in initramfs), it appears as
eth0. While when the machine is done booting, i.e. after the root partition has
been mounted, it appears as eth1.
What I'm seeing when performing a NIC replacement might also happen when using
two alternative ways to access the network, like a wired connection and a WiFi
one used alternatively.
--
network-admin error: The interface does not exist
https://bugs.launchpad.net/bugs/184711
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 230011] Re: [HARDY] Firefox print failure, default papersize erroneously Letter in German install
Same here with 3.0.1: Installé : 3.0.1+build1+nobinonly-0ubuntu0.8.04.3 Candidat : 3.0.1+build1+nobinonly-0ubuntu0.8.04.3 Table de version : *** 3.0.1+build1+nobinonly-0ubuntu0.8.04.3 0 500 http://archive.ubuntu.com hardy-updates/main Packages 500 http://archive.ubuntu.com hardy-security/main Packages 100 /var/lib/dpkg/status 3.0~b5+nobinonly-0ubuntu3 0 500 http://archive.ubuntu.com hardy/main Packages -- [HARDY] Firefox print failure, default papersize erroneously Letter in German install https://bugs.launchpad.net/bugs/230011 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 227326] Re: [upstream] [hardy] openoffice switches keyboard layout
This problem is more of a nuisance than it seems at first. "Use case" and consequence analysis: After OpenOffice Writer has one auto-corrected once a case of cAPS LOCK, it sticks to reverting the state of the Caps Locks key. This auto- correcting behavior doesn't spontaneously disappears after the user has pressed the Caps Lock key, presumably indicating that the user is back in charge of the Caps Lock key. It seems that the only way to reverse the behavior is actually to recreate the problem (e.g. to type another instance of an inverted caps word at the beginning of a paragraph and have it "autocorrected" the other (right) way). But there is worse: The Caps Lock inversion applies to the whole desktop, even if your Keyboard Preferance / Layout option "Separate layout for each window" is set. So if you had a terminal window opened on the desktop and start typing in it, it will start generating and echoing UPPERCASE commands there too, the behavior of your Caps Lock key / LED being inverted. And the cherry on the cake: This behavior persists even after the user has exited from OpenOffice Writer. That results is an interesting (?) puzzle for the user and/or the support person having to deal with questions like "Why does Ubuntu manage my Caps Lock key the wrong way?" (and "It worked before, how (or why) did I get there?"). (Been there: I just spent a few hours to figuring out that one for my wife!) -- [upstream] [hardy] openoffice switches keyboard layout https://bugs.launchpad.net/bugs/227326 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 184817] Re: unable to lock screen with ctrl - alt - L if numlock is on
Hi, I see just ran the same problem after upgrading from GG to HH (Actual 8.04 release): Ctrl-Alt-L stopped working. It is config'd as a keyboard shortcut for Lock Screen but doesn't work. I tried defining it again, but it didn't work better any after that. I'm using an an original MS Natural Keyboard, AZERTY (French/France) keymap. xev: KeyPress event, serial 27, synthetic NO, window 0x761, root 0x61, subw 0x0, time 8735982, (-454,-162), root:(1851,322), state 0x0, keycode 64 (keysym 0xffe9, Alt_L), same_screen YES, XLookupString gives 0 bytes: XmbLookupString gives 0 bytes: XFilterEvent returns: False KeyPress event, serial 30, synthetic NO, window 0x761, root 0x61, subw 0x0, time 8736106, (-454,-162), root:(1851,322), state 0x8, keycode 37 (keysym 0xffe3, Control_L), same_screen YES, XLookupString gives 0 bytes: XmbLookupString gives 0 bytes: XFilterEvent returns: False FocusOut event, serial 30, synthetic NO, window 0x761, mode NotifyGrab, detail NotifyAncestor FocusIn event, serial 30, synthetic NO, window 0x761, mode NotifyUngrab, detail NotifyAncestor KeymapNotify event, serial 30, synthetic NO, window 0x0, keys: 4294967213 0 0 0 32 64 0 0 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 KeyRelease event, serial 30, synthetic NO, window 0x761, root 0x61, subw 0x0, time 8736916, (-454,-162), root:(1851,322), state 0xc, keycode 46 (keysym 0x6c, l), same_screen YES, XLookupString gives 1 bytes: (0c) " " XFilterEvent returns: False KeyRelease event, serial 30, synthetic NO, window 0x761, root 0x61, subw 0x0, time 8737109, (-454,-162), root:(1851,322), state 0xc, keycode 64 (keysym 0xffe9, Alt_L), same_screen YES, XLookupString gives 0 bytes: XFilterEvent returns: False KeyRelease event, serial 30, synthetic NO, window 0x761, root 0x61, subw 0x0, time 8737159, (-454,-162), root:(1851,322), state 0x4, keycode 37 (keysym 0xffe3, Control_L), same_screen YES, XLookupString gives 0 bytes: XFilterEvent returns: False FocusOut event, serial 30, synthetic NO, window 0x761, mode NotifyNormal, detail NotifyNonlinear -- unable to lock screen with ctrl - alt - L if numlock is on https://bugs.launchpad.net/bugs/184817 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 108883] [apport] displayconfig-restore.py crashed with SIGSEGV
Public bug reported: Binary package hint: kde-guidance Crashed happened without any intervention during the automatic reboot after upgrading (using upgrade manager) to Feisty Fawn (release). ProblemType: Crash Architecture: i386 Date: Sun Apr 22 13:11:57 2007 DistroRelease: Ubuntu 7.04 ExecutablePath: /usr/share/python-support/kde-guidance/displayconfig-restore.py InterpreterPath: /usr/bin/python2.5 Package: kde-guidance 0.8.0-0ubuntu5 PackageArchitecture: i386 ProcCmdline: /usr/bin/python /usr/bin/displayconfig-restore ProcCwd: /home/philippe ProcEnviron: SHELL=/bin/bash PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/bin/X11:/usr/games LANG=en_US.UTF-8 Signal: 11 SourcePackage: kde-guidance StacktraceTop: ?? () from /usr/lib/libXrandr.so.2 ?? () ?? () ?? () ?? () from /usr/lib/libX11.so.6 Uname: Linux PhilKUbuntu 2.6.20-15-generic #2 SMP Sun Apr 15 07:36:31 UTC 2007 i686 GNU/Linux UserGroups: adm admin audio cdrom dialout dip floppy lpadmin plugdev scanner video ** Affects: kde-guidance (Ubuntu) Importance: Undecided Status: Unconfirmed -- [apport] displayconfig-restore.py crashed with SIGSEGV https://bugs.launchpad.net/bugs/108883 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
[Bug 108883] Re: [apport] displayconfig-restore.py crashed with SIGSEGV
** Attachment added: "CoreDump.gz" http://librarian.launchpad.net/7385861/CoreDump.gz ** Attachment added: "Dependencies.txt" http://librarian.launchpad.net/7385862/Dependencies.txt ** Attachment added: "Disassembly.txt" http://librarian.launchpad.net/7385863/Disassembly.txt ** Attachment added: "ProcMaps.txt" http://librarian.launchpad.net/7385864/ProcMaps.txt ** Attachment added: "ProcStatus.txt" http://librarian.launchpad.net/7385865/ProcStatus.txt ** Attachment added: "Registers.txt" http://librarian.launchpad.net/7385866/Registers.txt ** Attachment added: "Stacktrace.txt" http://librarian.launchpad.net/7385867/Stacktrace.txt ** Attachment added: "ThreadStacktrace.txt" http://librarian.launchpad.net/7385868/ThreadStacktrace.txt -- [apport] displayconfig-restore.py crashed with SIGSEGV https://bugs.launchpad.net/bugs/108883 You received this bug notification because you are a member of Kubuntu Team, which is a bug contact for kde-guidance in ubuntu. -- kubuntu-bugs mailing list [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 91545] Re: MASTER [apport] displayconfig-restore.py crashed with SIGSEGV in XRRGetScreenInfo()
I reported a similar error, that was marked as a duplicate of this one. But I didn't mention in my original report that I was running a dual screen configuration. Mine uses a dual-head Matrox G400 PCI board. -- MASTER [apport] displayconfig-restore.py crashed with SIGSEGV in XRRGetScreenInfo() https://bugs.launchpad.net/bugs/91545 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
[Bug 68968] Re: Randomly garbled display, secondary screen, dual-head
** Changed in: xorg (Ubuntu) Status: Unconfirmed => Confirmed -- Randomly garbled display, secondary screen, dual-head https://bugs.launchpad.net/bugs/68968 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 68968] Randomly garbled display, secondary screen, dual-head
Public bug reported: Dual-head display (Matrox G450, Xinerama, 1280x1024 on each screen). The problem appeared immediately after migrating from drapper 6.06 to edgy 6.10 When moving a window fast enough on the secondary screen, the "trailing" effect behind the window is not erased from the desktop and leaves random patterns behind (on the desktop background). When moving the window very slowly, the problem does not happen. Displaying then closing any window on the garbled desktop repaints the desktop background. A much less frequent form of the problem is that once in a while, a graphical object is painted garbled in an application window (for instance, the Google logo in Firefox). In this case, the garbled spot is exactly the rectangle that should have contained the graphical object. ** Affects: Ubuntu Importance: Undecided Status: Unconfirmed -- Randomly garbled display, secondary screen, dual-head https://launchpad.net/bugs/68968 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 68968] Re: Randomly garbled display, secondary screen, dual-head
** Description changed: Dual-head display (Matrox G450, Xinerama, 1280x1024 on each screen). The problem appeared immediately after migrating from drapper 6.06 to edgy 6.10 - When moving a window the window fast enough on the secondary screen, the "trailing" effect behind the window is not erased from the desktop and leaves random patterns behind (on the desktop background). When moving the window very slowly, the problem does not happen. + When moving a window fast enough on the secondary screen, the "trailing" effect behind the window is not erased from the desktop and leaves random patterns behind (on the desktop background). When moving the window very slowly, the problem does not happen. Displaying then closing any window on the garbled desktop repaints the desktop background. A much less frequent form of the problem is that once in a while, a graphical object is painted garbled in an application window (for instance, the Google logo in Firefox). In this case, the garbled spot is exactly the rectangle that should have contained the graphical object. ** Description changed: Dual-head display (Matrox G450, Xinerama, 1280x1024 on each screen). The problem appeared immediately after migrating from drapper 6.06 to edgy 6.10 When moving a window fast enough on the secondary screen, the "trailing" effect behind the window is not erased from the desktop and leaves random patterns behind (on the desktop background). When moving the window very slowly, the problem does not happen. - Displaying then closing any window on the garbled desktop repaints the desktop background. + Displaying then closing any window, or moving a window very slowly on the garbled desktop properly repaints the desktop background. + When moving a window over another window, the underneath window always repaints properly. + This never happens on the primary screen. A much less frequent form of the problem is that once in a while, a graphical object is painted garbled in an application window (for instance, the Google logo in Firefox). In this case, the garbled spot is exactly the rectangle that should have contained the graphical object. ** Description changed: Dual-head display (Matrox G450, Xinerama, 1280x1024 on each screen). The problem appeared immediately after migrating from drapper 6.06 to edgy 6.10 When moving a window fast enough on the secondary screen, the "trailing" effect behind the window is not erased from the desktop and leaves random patterns behind (on the desktop background). When moving the window very slowly, the problem does not happen. Displaying then closing any window, or moving a window very slowly on the garbled desktop properly repaints the desktop background. - When moving a window over another window, the underneath window always repaints properly. + When moving a window over another window, the underneath window always repaints properly (i.e. doesn't endup garbled). This never happens on the primary screen. A much less frequent form of the problem is that once in a while, a graphical object is painted garbled in an application window (for instance, the Google logo in Firefox). In this case, the garbled spot is exactly the rectangle that should have contained the graphical object. -- Randomly garbled display, secondary screen, dual-head https://launchpad.net/bugs/68968 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 68968] Re: Randomly garbled display, secondary screen, dual-head
Problem has simply disappeared today, I can't reproduce it - even after trying hard. I have no idea why it went away (nor what created in the first place, apart from the upgrade to edgy, since it appeared at this time). Before I reported it, I had made sure it wasn't a one-shot glitch I could fix: I checked a bunch of various issues including xorg.log (there was no error nor anything unusual there), rebooted the machine a couple of times just to make sure this wasn't a temp upgrade glitch, etc. I'm just puzzled. As far as I'm concerned, Bug #68968 can be considered closed. I apologize for the trouble :-( /Ph. -- Randomly garbled display, secondary screen, dual-head https://launchpad.net/bugs/68968 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 68968] Re: Randomly garbled display, secondary screen, dual-head
Scoop: The problem came back as initially described (sigh). The current status is that on some boots, the problem randomly shows up (and sticks), and on some others, it doesn't. This is happening on a vanilla 6.06 upgraded to 6.10, with very little customization or added software at this point. -- Randomly garbled display, secondary screen, dual-head https://launchpad.net/bugs/68968 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 68968] Re: Randomly garbled display, secondary screen, dual-head
Confirmed: The problem might or might not show up on a given session after a reboot. Whenever it reproduces, I will see how it resists / recurs when login off / login back and Ctrl-Alt-Bksp ing. -- Randomly garbled display, secondary screen, dual-head https://launchpad.net/bugs/68968 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 68968] Re: Randomly garbled display, secondary screen, dual-head
> It may be helpful to attach your /etc/X11/xorg.conf > and /var/log/Xorg.0.log, to assist in troubleshooting. > Also the output of lshw and/or lspci if you have it could > be helpful. Thanks for your suggestions. Will do next time the problem re-appears. I will also compare the log on a boot that results in the problem with the log on a boot that doesn't reproduce it, just in case. I saw the problem again a few days ago: That time, in addition to what's described above, the bottom 1/5 of the secondary screen was constantly flickering erroneous pixels. Everything came back to normal after restarting X thru a Ctrl-Alt-Bksp sequence. > I wonder if it could be differences or incompatibilities > between the two monitors I don't think so, the two monitors are exactly identical, same brand (Hyundai), same model, bought at the same time, same Xorg parms. I would rather suspect the fact that the Matrox G400 hardware and/or driver doesn't handle the primary and secondary screen exactly the same way. -- Randomly garbled display, secondary screen, dual-head https://launchpad.net/bugs/68968 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 68968] Re: Randomly garbled display, secondary screen, dual-head
Bryce, There we are. The attached files contains the xorg.conf, a log after a "good" xorg session, and a log after a "bad" one. Thanks for your assistance! ** Attachment added: "xorg conf file." http://librarian.launchpad.net/5724744/XConfFiles.tar.gz -- Randomly garbled display, secondary screen, dual-head https://launchpad.net/bugs/68968 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 68968] Re: Randomly garbled display, secondary screen, dual-head
** Changed in: xserver-xorg-video-mga (Ubuntu) Status: Incomplete => Fix Released -- Randomly garbled display, secondary screen, dual-head https://bugs.launchpad.net/bugs/68968 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 419143] Re: Printing from evince (and perhaps other GTK apps) to PostScript printers is broken
Not fully fixed for me either, after all. Printing a PDF from the document viewer to an HP LJ4 Plus, I get a failure on the first page: ERROR: invalidfont OFFENDING COMMAND: definefont STACK /Font -dictionary- /LiberationSerif_00 -- Printing from evince (and perhaps other GTK apps) to PostScript printers is broken https://bugs.launchpad.net/bugs/419143 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 479296] Re: Karmic: frequent freezes
Another one found in this morning logs: Nov 19 09:06:49 Philinux pulseaudio[1851]: ratelimit.c: 3 events suppressed Nov 19 09:07:15 Philinux kernel: [ 147.347561] __ratelimit: 3 callbacks suppressed Nov 19 09:07:15 Philinux kernel: [ 147.347575] deskbar-applet[2141]: segfault at 4fc00c ip 08094a8e sp bfab3cd0 error 6 in python2.6[8048000+1d3000] Nov 19 09:07:57 Philinux kernel: [ 189.158323] apport-checkrep[2957]: segfault at 6d016c ip 08106ad8 sp bf9ea720 error 4 in python2.6[8048000+1d3000] Nov 19 09:07:57 Philinux kernel: [ 189.508341] apport-checkrep[2958]: segfault at 7b5d1c ip 0810602a sp bf9b19d0 error 4 in python2.6[8048000+1d3000] -- Karmic: frequent freezes https://bugs.launchpad.net/bugs/479296 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 479296] Re: Karmic: frequent freezes
Hi Lelamal, It's not clear from your message what got you to suspect Compiz, but just as a test, I disabled it: On the next reboot, I got the following in the log: Nov 21 14:37:20 Philinux pulseaudio[1857]: ratelimit.c: 2 events suppressed Nov 21 14:37:27 Philinux pulseaudio[1857]: ratelimit.c: 4 events suppressed Nov 21 14:37:35 Philinux kernel: [ 93.228051] Clocksource tsc unstable (delta = -249963054 ns) Nov 21 14:37:51 Philinux kernel: [ 109.760217] __ratelimit: 3 callbacks suppressed Nov 21 14:37:51 Philinux kernel: [ 109.760230] deskbar-applet[2181]: segfault at 34 ip 0034 sp bfa7432c error 4 in libc-2.10.1.so[11+13e000] I haven't got a freeze yet, but still having various apps segfaulting here and there makes me think that it will sure happen in the coming hours. Here, the segfaults are often enough happening in the same second as a "__ratelimit: X callbacks suppressed", BTW. Is there a way to prevent pulseaudio for loading at all in the machine (without disabling anything else than the sound subsystem)? A manual killing of pulsaudio happens too late, since pulseaudio is already loaded then, and I see the suspicious "ratelimit.c" messages at several places during the boot. Trying this could at least give an indication of whether pulseaudio is really the main suspect here: If the problem still exists after pulseaudio has been fully removed, drivers and all, it will clearly indicate that the problem comes from something else... -- Karmic: frequent freezes https://bugs.launchpad.net/bugs/479296 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 479296] Re: Karmic: frequent freezes
Triggered a reboot: Nov 22 11:34:38 Philinux kernel: [ 106.085237] __ratelimit: 3 callbacks suppressed Nov 22 11:34:38 Philinux kernel: [ 106.085250] python[1917]: segfault at 900c0c ip 0808e110 sp bf8c0530 error 4 in python2.6[8048000+1d3000] Nov 22 11:38:10 Philinux kernel: imklog 4.2.0, log source = /var/run/rsyslog/kmsg started. Triggered a reboot: Nov 22 11:39:35 Philinux kernel: [ 113.942371] __ratelimit: 3 callbacks suppressed Nov 22 11:39:35 Philinux kernel: [ 113.942385] deskbar-applet[2308]: segfault at c35d5f9e ip 00d1ade7 sp bfafe724 error 5 in libc-2.10.1.so[c14000+13e000] Nov 22 11:40:03 Philinux kernel: [ 142.089533] BUG: Bad page map in process apport-checkrep pte:00c92025 pmd:32b91067 Nov 22 11:40:03 Philinux kernel: [ 142.089549] page:c104b240 flags:0004 count:0 mapcount:-1 mapping:(null) index:0 Nov 22 11:40:03 Philinux kernel: [ 142.089559] addr:002e vm_flags:0875 anon_vma:(null) mapping:f6db833c index:df Nov 22 11:40:03 Philinux kernel: [ 142.089574] vma->vm_ops->fault: filemap_fault+0x0/0x340 Nov 22 11:40:03 Philinux kernel: [ 142.089582] vma->vm_file->f_op->mmap: generic_file_mmap+0x0/0x50 Nov 22 11:40:03 Philinux kernel: [ 142.089591] Pid: 2988, comm: apport-checkrep Tainted: P 2.6.31-15-generic #50-Ubuntu Nov 22 11:40:03 Philinux kernel: [ 142.089598] Call Trace: Nov 22 11:40:03 Philinux kernel: [ 142.089613] [] print_bad_pte+0x139/0x1f0 Nov 22 11:40:03 Philinux kernel: [ 142.089622] [] zap_pte_range+0x3d7/0x3e0 Nov 22 11:40:03 Philinux kernel: [ 142.089631] [] unmap_vmas+0x186/0x350 Nov 22 11:40:03 Philinux kernel: [ 142.089640] [] exit_mmap+0xa0/0x160 Nov 22 11:40:03 Philinux kernel: [ 142.089651] [] mmput+0x2e/0xa0 Nov 22 11:40:03 Philinux kernel: [ 142.089659] [] exit_mm+0xe2/0x120 Nov 22 11:40:03 Philinux kernel: [ 142.089667] [] do_exit+0xfc/0x2e0 Nov 22 11:40:03 Philinux kernel: [ 142.089676] [] ? dequeue_signal+0x2d/0x170 Nov 22 11:40:03 Philinux kernel: [ 142.089685] [] ? sched_clock_cpu+0xeb/0x1a0 Nov 22 11:40:03 Philinux kernel: [ 142.089693] [] do_group_exit+0x3a/0xb0 Nov 22 11:40:03 Philinux kernel: [ 142.089702] [] get_signal_to_deliver+0x18f/0x300 Nov 22 11:40:03 Philinux kernel: [ 142.089712] [] ? scsi_finish_command+0x98/0x100 Nov 22 11:40:03 Philinux kernel: [ 142.089721] [] do_signal+0x6b/0x160 Nov 22 11:40:03 Philinux kernel: [ 142.089730] [] ? send_signal+0x38/0x70 Nov 22 11:40:03 Philinux kernel: [ 142.089738] [] ? force_sig_info+0x77/0xc0 Nov 22 11:40:03 Philinux kernel: [ 142.089747] [] ? force_sig+0xf/0x20 Nov 22 11:40:03 Philinux kernel: [ 142.089756] [] ? do_trap+0xb9/0xc0 Nov 22 11:40:03 Philinux kernel: [ 142.089764] [] do_notify_resume+0x4d/0x60 Nov 22 11:40:03 Philinux kernel: [ 142.089772] [] work_notifysig+0x13/0x1b Nov 22 11:41:52 Philinux kernel: imklog 4.2.0, log source = /var/run/rsyslog/kmsg started. Triggered a reboot: Nov 22 11:42:28 Philinux pulseaudio[1842]: ratelimit.c: 1 events suppressed Nov 22 11:42:34 Philinux pulseaudio[1842]: ratelimit.c: 2 events suppressed Nov 22 11:42:57 Philinux kernel: [ 93.236038] Clocksource tsc unstable (delta = -165929002 ns) Nov 22 11:45:22 Philinux kernel: [ 238.053692] __ratelimit: 3 callbacks suppressed Nov 22 11:45:22 Philinux kernel: [ 238.053705] update-python-m[2997]: segfault at 97ba81c ip 0808e8db sp bfad1100 error 4 in python2.6[8048000+1d3000] In all three cases, the crash followed immediately a __ratelimit: 3 callbacks suppressed message. Even when the machine does not hard crash / freeze, I can see at least one desktop application crash (usually a segfault) for each reboot, during the time the desktop initializes. The crashing application varies from time to time. I have also seen several cases of a full freeze (or even a direct reboot) during the loading firefox. And one time, I had a full freeze (keyboard and soft power button dead) when the machine speakers produced a loud, random "static noise": A noise similar to that of a radio tuned to no station on a short AM waveband. It looks more and more to me that the problem is related to pulseaudio, but the next step would be to see if the problem still occurs with pulseaudio out of the way. Could anyone tell me how to prevent pulseaudio and all of its drivers to load at all at boot time? -- Karmic: frequent freezes https://bugs.launchpad.net/bugs/479296 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 479296] Re: Karmic: frequent freezes
Peter, Thanks for the link. I'm going to try this and see is that makes a change. I'm not just looking for a quick way to get rid of the problem on the one machine I have that exhibits the problem. Even if this makes the problem go away, I'm ready to come back to the problem configuration if I can help in pinpointing it. Since I have a machine that does exhibit the problem, is there anything special I can do to help? About "> PulseAudio doesn't have any sound drivers." What if I replace "drivers" in my previous message by "kernel module"? -- Karmic: frequent freezes https://bugs.launchpad.net/bugs/479296 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 479296] Re: Karmic: frequent freezes
Daniel, I applied the method indicated at the link you sent. Copied / pasted / executed: touch ~/.pulse_a11y_nostart echo autospawn = no|tee -a ~/.pulse/client.conf killall pulseaudio and rebooted the machine. That didn't prevent pulseaudio from starting, though, as my log still contains: Nov 22 16:44:53 Philinux kernel: [ 28.182386] __ratelimit: 3 callbacks suppressed (...) Nov 22 16:45:05 Philinux pulseaudio[1697]: ratelimit.c: 1 events suppressed Nov 22 16:45:58 Philinux kernel: [ 93.244043] Clocksource tsc unstable (delta = -216722338 ns) What gives?... > PulseAudio is entirely userspace. Are you referring to > the ALSA kernel modules (sound drivers)? Well, the reason I'm asking is that I repeatedly see various processes segfaulting within a dozen microseconds after a __ratelimit: X callbacks suppressed messages, I inferred that some pulseaudio kernel module was involved: How could the pulseaudio usermode process interfere with a whole set of other user processes otherwise? Or send the whole OS to a freeze? Example follows: Nov 21 14:09:42 Philinux pulseaudio[1842]: ratelimit.c: 2 events suppressed Nov 21 14:10:05 Philinux kernel: [ 94.732041] Clocksource tsc unstable (delta = -223109891 ns) Nov 21 14:10:38 Philinux kernel: [ 127.890435] __ratelimit: 3 callbacks suppressed Nov 21 14:10:38 Philinux kernel: [ 127.890447] apt-check[2885] general protection ip:805b17c sp:bf88202c error:0 in python2.6[8048000+1d3000] Nov 21 14:11:35 Philinux kernel: [ 184.778508] update-manager[2935] general protection ip:809494a sp:bfae3134 error:0 in python2.6[8048000+1d3000] Finally, my apologies for answering to you as "Peter" in my previous message. We have a Peter Chen in our team, and it looks like I blew a couple of synapses while typing the previous message! -- Karmic: frequent freezes https://bugs.launchpad.net/bugs/479296 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 479296] Re: Karmic: frequent freezes
That's a good question. I see the pulseaudio messages in the log (the one below is from the latest / current boot), but I see no pulseaudio process in ps when I'm using the machine. So it seems pulseaudio was active in the machine at boot, 14 seconds after the very first boot-time log message was written, but isn't when I look at it. The only mention of pulse I find in ps are in ssh-agent, gpg-agent and dbus-launch: All three have been launched with a cmd containing a pulse related option: --exit-with-session /usr/bin/pulse-session gnome-session -- Karmic: frequent freezes https://bugs.launchpad.net/bugs/479296 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 479296] Re: Karmic: frequent freezes
> Once you've logged in as your user, you can probably > verify with "pgrep pulseaudio" that it is not running as your user. Sure, but what I wanted was to prevent pulseaudio from starting at all in the machine. Not even once. I first created file /var/lib/pulseaudio/pulse_a11y_nostart: Better than the $HOME/.pulse_a11y_nostart because it prevents logging whatever $HOME resolves to. But that wasn't enough. It seems that pulseaudio was still called, presumably from the login screen (when it rolled the Ubuntu drum). I ended up using the brute force approach and renaming the the pulseaudio binary to pulseaudio.off. That worked. I'll be back here within at most 72 hours, to report either yet another freeze or random segfault (and pulseaudio presumably innocent) or no problem (and pulseaudio still under suspicion). -- Karmic: frequent freezes https://bugs.launchpad.net/bugs/479296 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 479296] Re: Karmic: frequent freezes
pulseaudio not guilty, at least not in my case. I'm still experiencing random freezes... -- Karmic: frequent freezes https://bugs.launchpad.net/bugs/479296 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 479296] Re: Karmic: frequent freezes
At least one of the problems I had was a failing RAM stick. I could isolate this 100% by swapping it with a perfectly identical machine running Windows (it immediately started to BSoD all around the place). I have replaced the RAM and reenabled pulseaudio. -- Karmic: frequent freezes https://bugs.launchpad.net/bugs/479296 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 328575] Re: [gnome-terminal SRU] Cannot start gnome-terminal (or x-terminal-emulator) because of gconf error
Update manager downloaded and installed the fix this morning. Everything works fine now. Lotsa thanks! -- [gnome-terminal SRU] Cannot start gnome-terminal (or x-terminal-emulator) because of gconf error https://bugs.launchpad.net/bugs/328575 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 479296] Re: Karmic: frequent freezes
Hmmm, here I have an "NVidia nForce3 with AD1981B sound card" that takes snd-intel8x0m. Aka ac97. According to the alsa docs, this is the right driver for that one. I still the pulseaudio messages in the log, but nothing segfault anymore, and the freezes are gone. Not sure what I can improve there. Anyhow, the machine works much better with 512 MiB of healthy RAM than with 1280 MiB including a bad stick! -- Karmic: frequent freezes https://bugs.launchpad.net/bugs/479296 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 197762] Re: file transfers on USB disk are very slow
Same problem here copying 100MB from the disk to an USB key using Nautilus (drag n drop from Nautilus to Nautilus). During the copy, the gnome desktop is mostly frozen, the copy progress bar only appears after after *minutes* and once appeared, is hardly refreshed at all before the end of the copy. During that time, the desktop is totally unresponsive. Karmic 2.6.31-15 and 16. OTOH, reading from the key writing to the disk is perfectly normal, both in term of speed and behavior of the progress bar, desktopn etc. All cache effect has being eliminated (the data copied was not already in the cache). I never saw anything comparable under Jaunty same hardware (key included). -- file transfers on USB disk are very slow https://bugs.launchpad.net/bugs/197762 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 197762] Re: file transfers on USB disk are very slow
2.6.31-16-generic #53-Ubuntu x86_64 fixed my problem too. -- file transfers on USB disk are very slow https://bugs.launchpad.net/bugs/197762 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 417757] Re: [karmic regression] all network apps / browsers suffer from multi-second delays by default due to IPv6 DNS lookups
That might do it on the (very) long term, and if this is what the problem is, it has to be done anyway. But I don't see how that would solve the problem at hand *NOW*. I'm experiencing the problem and I'm connected behind a recent Linksys BEFVP41 VPN router, downstream my DSL box, that I use to isolate / protect me from the network. Linksys is Cisco, btw, the king of the routing world. And the box is new, bought in 2009. Latest firmware, april 2009. http://www.linksysbycisco.com/US/en/support/BEFVP41/download And I do have the problem. There are myriads of people and small and large businesses in the same situation. Expecting that all those are going to rush buying a new router (and for many, finding someone to config it for them) because Linux misbehaves (even if it "rightly" misbehaves) seems a wild goose chase to me. Many would rather conclude that Windows is still the king of the hill after all and change the piece of software that reveals the problem for the one that doesn't. -- [karmic regression] all network apps / browsers suffer from multi-second delays by default due to IPv6 DNS lookups https://bugs.launchpad.net/bugs/417757 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 419143] Re: Printing from evince (and perhaps other GTK apps) to PostScript printers is broken
After this morning batch of patches (including various cups ones), I still have a Postcript crash too on my LaserJet 4 Si (using the recommended driver HP LaserJet 4 Plus v2013.111 Postscript). The printer diagnoses this: Error: Undefined OFFENDING COMMAND: 0a STACK: -mark- false -- Printing from evince (and perhaps other GTK apps) to PostScript printers is broken https://bugs.launchpad.net/bugs/419143 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 459547] Re: Screen resolution not correct
Same problem here, nomodeset xdriver=intel solved it too (thanks Paul). Machine is an HP Compaq DC7700 desktop with an Intel 945Q, and problem occurred at the first reboot immediately after today's Jaunty to Koala (online) upgrade. -- Screen resolution not correct https://bugs.launchpad.net/bugs/459547 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 479296] Re: Karmic: frequent freezes
Similar freezes here since I upgraded to Karmic. I never had such a problem with Jaunty (or any previous version). The typical freeze is a severe one (everything really dead, keyboard LEDs don't toggle, soft power off does nothing, forced power off needed). The last items present in the log is always something like this: Nov 18 07:49:18 Philinux pulseaudio[1854]: ratelimit.c: 5 events suppressed and the next message is when I realized the machine was dead and rebooted it: Nov 18 08:38:19 Philinux kernel: imklog 4.2.0, log source = /var/run/rsyslog/kmsg started. Nov 18 10:29:49 Philinux pulseaudio[1825]: ratelimit.c: 229 events suppressed Nov 18 10:56:55 Philinux kernel: imklog 4.2.0, log source = /var/run/rsyslog/kmsg started. Nov 18 11:09:39 Philinux pulseaudio[1853]: ratelimit.c: 1 events suppressed Nov 18 12:40:22 Philinux kernel: imklog 4.2.0, log source = /var/run/rsyslog/kmsg started. When those freezes happened, no sound application such as Rythmbox or other was active. Sound is only used by the default system sounds (like on error, etc.). So far, the freezes didn't happen when I was actively working on the machine (keyboard / mouse), so I suspected a relation with the power management. The machine is configured to never sleep when inactive, "Spin down hard disks" is not checked, but the display is config'd to turn off after 5 minutes. Finally, looking at past logs, the machine doesn't always freeze after a "pulseaudio[1854]: ratelimit.c: 5 events suppressed" message, but most often, the next consecutive lines in the log indicate some severe problem: Either a reboot or some segfault (usually nautilus, sometimes a deskbar applet). The segfault or reboot might happen immediately (same second) or several minutes after the "event suppressed" message, though. Quite often, the "events suppressed" message is followed by a "Clocksource tsc unstable": Nov 18 08:39:17 Philinux pulseaudio[1825]: ratelimit.c: 5 events suppressed Nov 18 08:39:25 Philinux kernel: [ 92.232052] Clocksource tsc unstable (delta = -109978147 ns) I'm not sure this makes sense or is any useful, just trying to identify patterns... -- Karmic: frequent freezes https://bugs.launchpad.net/bugs/479296 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 479296] Re: Karmic: frequent freezes
Follow up to my own #24: I installed linux-backports-modules-alsa-karmic-generic but it didn't prevent my station to freeze again (same messages in the log). :( -- Karmic: frequent freezes https://bugs.launchpad.net/bugs/479296 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 555122] Re: Cannot adjust brightness in Lucid Lynx
Silvan's solution (#20) worked perfectly for me (I have exactly the same hardware configuration he has, but I'm running 32-bit Lucid). Thanks Silvan! -- Cannot adjust brightness in Lucid Lynx https://bugs.launchpad.net/bugs/555122 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 555122] Re: Cannot adjust brightness in Lucid Lynx
@C Charles #47: > Silvan's solution works only for radeon driver Huh? AFAIKT, the hp 8530w we both have is an Intel / nvidia machine (Quadro FX 770M)... -- Cannot adjust brightness in Lucid Lynx https://bugs.launchpad.net/bugs/555122 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 459647] Re: Cannot change mouse cursor theme when compiz is enabled
The fix worked quite well for me, except for the move cursor as previously reported. OTOH, for me, the resizing cursors are now what they should be. About the move cursor: The "old" one still shows up when dragging a window around the desktop, but the right one is in use when moving a file inside Nautilus, for instance. -- Cannot change mouse cursor theme when compiz is enabled https://bugs.launchpad.net/bugs/459647 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 417757] Re: [karmic regression] all network apps / browsers suffer from multi-second delays by default due to IPv6 DNS lookups
@Bernhard #134 wrote "Pessimistic estimates say that the problem we suspect (a DNS proxy that cannot handle queries) affects about 0.5% of the global userbase. @Bernhard #134 wrote 50% of those can easily be fixed with a firmware upgrade of their router, which is usually a very good idea anyway." Do you have any verifiable and opposable reference on those figures? Where is the study that produced those "pessimistic estimates" (...) "0.5%" (...) "50% of those"(...) ? What was the methodology used to produced those figures? What was the sample? How was it picked worldwide? -- [karmic regression] all network apps / browsers suffer from multi-second delays by default due to IPv6 DNS lookups https://bugs.launchpad.net/bugs/417757 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 313713] Re: HP LaserJet 4 Plus sometimes fails to print with "v2013.111 Postscript" driver
Since I upgraded to Karmic (release), neither the HP LaserJet 4 Plus v2013.111 Postscript [en] (recommended) nor the HP LaserJet 4 Plus Foomatic/Postscript [en] work for me. Printing a vanilla .odt document (not even anything fancy) from Ooo 3.1, I get: Using HP LaserJet 4 Plus v2013.111 Postscript [en] (recommended), I get nothing but: ERROR: invalid font OFFENDING COMMAND: definefont STACK: /Font -dictionary- /OpenSymbol__0 Using HP LaserJet 4 Plus Foomatic/Postscript [en], I get the first page, then instead of the second page: ERROR: invalidaccess OFFENDING COMMAND: writestring STACK: (PAGE: ) -filestream- 1 true Same problem exporting to PDF then printing from the PDF viewer. Sending the .pdf to a windows machine and printing the PDF from there does work, so the .pdf is valid. I finally worked around the problem by switching to the HP LaserJet4 Plus hpljs pcl3, 3.9.8 [en] -- HP LaserJet 4 Plus sometimes fails to print with "v2013.111 Postscript" driver https://bugs.launchpad.net/bugs/313713 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 419143] Re: Printing from evince (and perhaps other GTK apps) to PostScript printers is broken
Janne, Your workaround 2 (packages) worked just fine for me too. I was experiencing the problem on both an HP 4250 and an HP LJ4 Plus rather than a 4100, btw. Thanks alot! -- Printing from evince (and perhaps other GTK apps) to PostScript printers is broken https://bugs.launchpad.net/bugs/419143 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 417757] Re: [karmic regression] all network apps / browsers suffer from multi-second delays by default due to IPv6 DNS lookups
After applying the updates and removing the workarounds I had used before, the problem seems to be gone on my machines. Thanks, folks! -- [karmic regression] all network apps / browsers suffer from multi-second delays by default due to IPv6 DNS lookups https://bugs.launchpad.net/bugs/417757 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 459547] Re: Screen resolution not correct
Looks like this bug has been fixed at some point: I upgraded Grub to Grub 2 (Karmic), and Grub 2 didn't propagate the nomodeset xdriver=intel parms that were on the Grub 1 line. But nevertheless, the video restarted just fine. So for me, this has been corrected by some patch that appeared between Nov 16th 2009 and now. Thanks to the maintainers! -- Screen resolution not correct https://bugs.launchpad.net/bugs/459547 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 1584557] Re: Seagate external drive causes SCSI bus resets when UAS enabled
FWIW, I changed my notebook and reinstalled 18.04.2 64-bit on the new machine. I then plugged my 4 external disks (see comment #6) to the new machine. And much to my dismay, when plugged into USB 3.x ports, the disks didn't mount... It did on USB 2.0 ports, though. Looking at sysdev reminded me of this problem I had experienced in 2016 on the same devices, and the same fix worked just as well: - Creating a "blacklist-uas-on-quirks.conf" in /etc/modprobe.d and - Adding the line options usb-storage quirks=059f:105e:u,059f:107e:u in the file to blacklist uas for the two listed devices and use usb-storage instead. That fixed it for me. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1584557 Title: Seagate external drive causes SCSI bus resets when UAS enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1584557/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1584557] Re: Seagate external drive causes SCSI bus resets when UAS enabled
Kai-Heng Feng, I wouldn't mind if I knew how to do it... :) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1584557 Title: Seagate external drive causes SCSI bus resets when UAS enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1584557/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1776030] Re: Backup fails with "an unknown error"
Michael (#7): 18.04.2 x64: I uninstalled deja-dup and duplicity then did what you suggested (snap install etc.). It mostly solved the problem I had (#6). Thanks! Still, the backup ended with the following error message: Backup Finished Could not back up the following files. Please make sure you are able to open them. /home/philippe/.cache/deconf /home/philippe/.dbus Anything I could do to fix those? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1776030 Title: Backup fails with "an unknown error" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1776030/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1776030] Re: Backup fails with "an unknown error"
#9: > Are those files you need backed up? Otherwise, you can put them in the > "folders to be ignored" list. Problem is, I'd rather not put them in the "ignored" list *if* they actually should be backed up and something else should be done instead (like changing permissions). All I can tell I didn't have this error when running off previous Ubuntu versions. But I couldn't tell whether deja-dup successfully saved them or automatically skipped them back then. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1776030 Title: Backup fails with "an unknown error" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1776030/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1776030] Re: Backup fails with "an unknown error"
I see something that looks *exactly* identical to the problem sambo63
has (#6):
Same uname -a,
same everything except for:
deja-dup --version
deja-dup 37.0
I get:
Backup Failed
Failed with an unknown error.
Traceback (innermost last):
File "/usr/bin/duplicity", line 1555, in
with_tempdir(main)
File "/usr/bin/duplicity", line 1541, in with_tempdir
fn()
File "/usr/bin/duplicity", line 1393, in main
do_backup(action)
File "/usr/bin/duplicity", line 1511, in do_backup
full_backup(col_stats)
File "/usr/bin/duplicity", line 572, in full_backup
globals.backend)
File "/usr/bin/duplicity", line 454, in write_multivol
(tdp, dest_filename, vol_num)))
File "/usr/lib/python2.7/dist-packages/duplicity/asyncscheduler.py", line
146, in schedule_task
return self.__run_synchronously(fn, params)
File "/usr/lib/python2.7/dist-packages/duplicity/asyncscheduler.py", line
172, in __run_synchronously
ret = fn(*params)
File "/usr/bin/duplicity", line 453, in
vol_num: put(tdp, dest_filename, vol_num),
File "/usr/bin/duplicity", line 342, in put
backend.put(tdp, dest_filename)
File "/usr/lib/python2.7/dist-packages/duplicity/backend.py", line 395, in
inner_retry
% (n, e.__class__.__name__, util.uexc(e)))
File "/usr/lib/python2.7/dist-packages/duplicity/util.py", line 79, in uexc
return ufn(unicode(e).encode('utf-8'))
UnicodeDecodeError: 'ascii' codec can't decode byte 0xe2 in position 37:
ordinal not in range(128)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1776030
Title:
Backup fails with "an unknown error"
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1776030/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1690836] Re: libnl-genl-3.0 memory leak
Joshua, Since this is apparently fixed in Debian 8.0, couldn't it have been fixed already upstream? In which case, the problem would rather be updating the Ubuntu LTS version (or backporting the fix)? On Wed, May 17, 2017 at 11:56 PM, Joshua Powers wrote: > I believe this is the upstream project: > https://github.com/tgraf/libnl > > ** Tags added: bitesize needs-upstream-report > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1690836 > > Title: > libnl-genl-3.0 memory leak > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/libnl3/+bug/ > 1690836/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1690836 Title: libnl-genl-3.0 memory leak To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libnl3/+bug/1690836/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1292398] Re: Second screen position isn't saved from one session to another
@davias (#108): This works for me too! Thanks a lot! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1292398 Title: Second screen position isn't saved from one session to another To manage notifications about this bug go to: https://bugs.launchpad.net/elementaryos/+bug/1292398/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1292398] Re: Second screen position isn't saved from one session to another
Same problem here after upgrading three days ago from Ubuntu 14.04.4 (that worked) to 16.04.1 (that's broken as explained below). Desktop Environment: GNOME-Flashback:Unity (gnome-flashback-metacity) Dual screen, notebook + external VGA monitor. NVidia Quadro FX 770M, 3.3.0 NVIDIA 340.96 I set the primary monitor to the notebook screen using nvidia-settings, and the setting stuck across logout: I see the gnome panel properly moving to the notebook screen when the Gnome GUI comes up after logout and reboot. OTOH, my notebook is positioned to the right of my VGA monitor, and that's where the problem starts. The system insists on placing the notebook built-in screen to the left of the monitor. If I set the primary monitor (notebook built-in screen) to the right of the VGA screen using nvidia-settings, I get what I want for the current session. But this setting is lost after the next session logout (or reboot for that matter). If alternately, I set the primary monitor (notebook built-in screen) to the right of the VGA screen using "System Settings / Displays", I get what I want for the session, but this setting is also lost after the next logout (reboot). The trick suggesting at #39 doesn't work for me (to start with, I have no etc/gnome-setting-daemon/xrandr on my system) To add insult to injury, the upgrade also brought me a similar problem with the alsamixer settings: They are set to some default muted values that makes the machine totally silent at each session start, and whatever way I set them, they are reset to the same muted default values upon the next logout / login. Not sure whether I also owe this to gnome-shell, but that's what I suspect. I use "sudo alsactl" to manually handle the problem and reload the proper alsamixer value, but I hate it. I have so far not found any simple, reliable fix or workaround for either problem. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1292398 Title: Second screen position isn't saved from one session to another To manage notifications about this bug go to: https://bugs.launchpad.net/elementaryos/+bug/1292398/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1584557] Re: Seagate external drive causes SCSI bus resets when UAS enabled
Same problem here using 16.04 / kernel 4.4.0-42-generic (i686) and external drive LaCie d2 Quadra, USB ID 059f:105e I get random hangs under heavy traffic, during rsync from one external USB drive to another. rsync just hangs during a transfer. Sometimes it recovers after a number of seconds, sometimes it never does and hangs there, possibly for hours. dmesg contains then contains repeated error recovery sequences such as: [ 2350.056247] usb 1-4.4: cmd cmplt err -2 [ 2350.128049] usb 1-4.4: reset high-speed USB device number 12 using ehci-pci [ 2350.333548] scsi host8: uas_eh_bus_reset_handler success [ 2381.032039] sd 8:0:0:0: [sdc] tag#1 uas_eh_abort_handler 0 uas-tag 2 inflight: CMD [ 2381.032045] sd 8:0:0:0: [sdc] tag#1 CDB: Read(10) 28 00 95 5a 11 00 00 00 08 00 [ 2381.032049] sd 8:0:0:0: [sdc] tag#0 uas_eh_abort_handler 0 uas-tag 1 inflight: CMD [ 2381.032052] sd 8:0:0:0: [sdc] tag#0 CDB: Read(10) 28 00 00 00 00 00 00 00 20 00 [ 2381.032079] scsi host8: uas_eh_bus_reset_handler start Disabling uas worked the problem around. I still see some: usb 1-4.4: reset high-speed USB device number 14 using ehci-pci in dmesg but the disk recovers after the reset. Additionally, disabling uas allows me to see the external disk SMART data (including using Disks), something I couldn't do before and was sorely missing in these circumstances! The bottom line is that it seems under certain circumstances, uas is not able to recover from errors. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1584557 Title: Seagate external drive causes SCSI bus resets when UAS enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1584557/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 692324] [NEW] boot freeze during pcmcia_socket : cs: IO port probe
Public bug reported: Since I upgraded to 10.10, my nx9105 freeze at boot about 3 times out of 4. The freeze happens early enough that nothing is recorded in any log. using ignore_loglevel, it appeared that it was related to pcmcia / cardbus / yenta_socket.ko, and that the log lines preceding the freeze were most of the time looking like those: Dec 19 09:26:09 Philinux kernel: [ 39.528596] yenta_cardbus :02:04.1: ISA IRQ mask 0x0c30, PCI irq 18 Dec 19 09:26:09 Philinux kernel: [ 39.528602] yenta_cardbus :02:04.1: Socket status: 3006 Dec 19 09:26:09 Philinux kernel: [ 39.528608] pci_bus :02: Raising subordinate bus# of parent bus (#02) from #06 to #0a Dec 19 09:26:09 Philinux kernel: [ 39.528624] yenta_cardbus :02:04.1: pcmcia: parent PCI bridge window: [io 0x3000-0x7fff] Dec 19 09:26:09 Philinux kernel: [ 39.528629] pcmcia_socket pcmcia_socket1: cs: IO port probe 0x3000-0x7fff: excluding 0x3000-0x30ff 0x3400-0x34ff 0x3800-0x38ff 0x3c00-0x3cff 0x7000-0x70ff 0x7400-0x743f with the freeze occuring on the last line above. After many searches and attempts, it appeared that I could totally suppress the problem by blacklisting yenta_socket.ko. ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: linux-image-generic 2.6.35.24.28 Regression: Yes Reproducible: Yes ProcVersionSignature: Ubuntu 2.6.35-24.42-generic 2.6.35.8 Uname: Linux 2.6.35-24-generic i686 NonfreeKernelModules: nvidia AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23. Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: philippe 1580 F pulseaudio /dev/snd/pcmC0D0p: philippe 1580 F...m pulseaudio CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'nForce3'/'NVidia nForce3 with AD1981B at irq 21' Mixer name : 'Analog Devices AD1981B' Components : 'AC97a:41445374' Controls : 33 Simple ctrls : 22 Date: Sun Dec 19 20:54:52 2010 HibernationDevice: RESUME=UUID=56372925-af65-4c29-997c-6fb390a77b82 IwConfig: lono wireless extensions. eth0 no wireless extensions. Lsusb: Bus 003 Device 002: ID 046d:c018 Logitech, Inc. Optical Wheel Mouse Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Hewlett-Packard hp compaq nx9105 (DU426ET#ABF) PccardctlIdent: Socket 0: no product info available Socket 1: no product info available PccardctlStatus: Socket 0: no card Socket 1: no card ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-24-generic root=UUID=cc373c0c-6ca1-4e73-b743-08081d90c21b ro ignore_loglevel acpi=apci_pm nvidia.nomodeset ProcEnviron: SHELL=/bin/bash LANG=en_US.utf8 RelatedPackageVersions: linux-firmware 1.38.2 RfKill: SourcePackage: linux WpaSupplicantLog: dmi.bios.date: 04/28/2005 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.35 dmi.board.name: 08A0 dmi.board.vendor: Compal dmi.board.version: 32.42 dmi.chassis.type: 10 dmi.chassis.vendor: Compal dmi.modalias: dmi:bvnHewlett-Packard:bvrF.35:bd04/28/2005:svnHewlett-Packard:pnhpcompaqnx9105(DU426ET#ABF):pvrF.35:rvnCompal:rn08A0:rvr32.42:cvnCompal:ct10:cvr: dmi.product.name: hp compaq nx9105 (DU426ET#ABF) dmi.product.version: F.35 dmi.sys.vendor: Hewlett-Packard ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 kernel-uncat maverick needs-upstream-testing regression-release -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/692324 Title: boot freeze during pcmcia_socket : cs: IO port probe -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 692324] Re: boot freeze during pcmcia_socket : cs: IO port probe
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/692324 Title: boot freeze during pcmcia_socket : cs: IO port probe -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 681819] Re: libcrc32c.ko does not declare dependancy on crc32c.ko
Tim, Acutally, once I figured out what was going wrong, I did work around the problem for myself: I just created a hook script in /etc/initramfs-tools with a manual_add_modules crc32c in it, and ran an update-initramfs -u and that was it. It didn't even require a kernel build. But the reason I'm reporting it is because googling around, it seems that since that crc32 thing has been spilt in its two libcrc32c and crc32c parts, quite a few people are regularly bitten by this problem when trying to remote boot iSCSI, NFS or whatever other technique, and waste a few hours or more trying to figure out what's going wrong (been there, done that ;-) ). So it's a nuisance, and it looks to me that it should be addressed. I did noticed that libcrc32c dynamically loads a registered "crc32c" module, and that this is the reason why libcrc32c doesn't declare a dependency on crc32c, but I still think that the fact that this mechanism breaks depmod and whatever relies on it (like initramfs) is a problem. Today, libcrc32c seems to pull a single module, crc32c. But even if tomorrow, it might pull any one of several, then the whole set of modules should be considered and made available when libcrc32c is required... instead of none as of today. This could of course be solved in initramfs-tools by some hard coded exception handling of libcrc32c (in a similar way that an initramfs-tools function currently excludes arcnet, token ring, bnx2 and a few others), but there might be a better, smarter, more generic solution. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/681819 Title: libcrc32c.ko does not declare dependancy on crc32c.ko -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 681819] Re: libcrc32c.ko does not declare dependancy on crc32c.ko
Looks very good to me! Thanks, Tim! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/681819 Title: libcrc32c.ko does not declare dependancy on crc32c.ko -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 681819] [NEW] libcrc32c.ko does not declare dependancy on crc32c.ko
Public bug reported: As a result, depmod doesn't report the dependancy in modules.dep, and initramfs doesn't pull crc32c.ko when a module declares libcrc32c.ko as a dependency. I ran into this when I noticed I couldn't remote boot a machine that uses the bnx2x.ko 10Gb BroadCom Enet adapter. bnx2x.ko depends on libcrc32c.ko another module, and all were properly present in initramfs. But the NIC driver didn't load. When attempting to manually insmod the module from the BusyBox, I realized libcrc32c was not loading, and insmod'ing libcrc32c from a fully booted machine, I realized it actually loaded crc32c.ko -- that didn't exist in the initramfs image. Running modinfo on libcrc32c.ko shows no dependancy. Consistently, modules.dep doesn't report any dependancy for libcrc32c.ko This results in all kind of nasty irritating problems when libcrc32c.ko is needed in initramfs (including a number reported in launchpad), like when people try to use btrfs as their root and end up being unable to boot. This problem has existed for a while, and has most likely been introduced with this patch: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=69c35efcf1576ab5f00cba83e8ca740923afb6c9 ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: linux-image-2.6.35-23-generic 2.6.35-23.40 [modified: lib/modules/2.6.35-23-generic/kernel/drivers/net/bnx2.ko lib/modules/2.6.35-23-generic/kernel/drivers/net/cnic.ko] Regression: No Reproducible: Yes ProcVersionSignature: Ubuntu 2.6.35-23.40-generic 2.6.35.7 Uname: Linux 2.6.35-23-generic i686 AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access /dev/snd/: No such file or directory AplayDevices: aplay: device_list:235: no soundcards found... Architecture: i386 ArecordDevices: arecord: device_list:235: no soundcards found... Date: Fri Nov 26 15:48:34 2010 InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007) MachineType: HP ProLiant DL380 G6 PciMultimedia: ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-23-generic root=UUID=727daec2-c6f1-43da-a59b-0831b8769949 ro debug ignore_loglevel radeon.nomodeset kgdb=ttyS0,115200 kgdboc=ttyS0,115200 ProcEnviron: SHELL=/bin/bash LANG=en_US.utf8 SourcePackage: linux dmi.bios.date: 10/14/2010 dmi.bios.vendor: HP dmi.bios.version: P62 dmi.chassis.type: 23 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrP62:bd10/14/2010:svnHP:pnProLiantDL380G6:pvr:cvnHP:ct23:cvr: dmi.product.name: ProLiant DL380 G6 dmi.sys.vendor: HP ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 kernel-uncat maverick needs-upstream-testing -- libcrc32c.ko does not declare dependancy on crc32c.ko https://bugs.launchpad.net/bugs/681819 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 681819] Re: libcrc32c.ko does not declare dependancy on crc32c.ko
-- libcrc32c.ko does not declare dependancy on crc32c.ko https://bugs.launchpad.net/bugs/681819 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 1431654] Re: lightdm (1.2.3-0ubuntu2.6) 100%/high cpu usage
Same here, 32_bit: 3.2.0-79-generic #115-Ubuntu SMP Thu Mar 12 14:21:14 UTC 2015 i686 i686 i386 GNU/Linux -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1431654 Title: lightdm (1.2.3-0ubuntu2.6) 100%/high cpu usage To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1431654/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1431654] Re: lightdm (1.2.3-0ubuntu2.6) 100%/high cpu usage
Confirmation for the 32-bit version as well: 1.2.3-0ubuntu2.7 fixed it. Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1431654 Title: lightdm (1.2.3-0ubuntu2.6) 100%/high cpu usage To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1431654/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 994790] Re: [Dell XT3] Firewire does not work
I see a similar problem with 12.04 on an HP EliteBook 8530w: Kernel Linux 3.5.0-45-generic Release 12.04 (precise) 32-bit On Firewire insertion, nothing happens and the disk does not start. If I then plug the disk using USB 2, the disk starts and works. If I then unplug the USB cable, then plug the Firewire cable again, this time, the disk starts, gets properly automounted, and works perfectly until shutdown. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/994790 Title: [Dell XT3] Firewire does not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/994790/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 979839] Re: No X with nvidia-current 270.41.06-0ubuntu1.1
The cause of the problem seems to be that when Natty updates the kernel, for some reason, it does install linux-headers-2.6.38-xx linux-headers-2.6.38-xx-generic but does NOT install linux-headers-2.6.38-xx-generic-pae. As a result, it can't rebuild the nvidia-current drivers for the new pae kernel. And the next boot results in no X.org... Manually installing linux-headers-2.6.38-xx-generic-pae then removing and installing again nvidia-current properly rebuilds the nvidia driver. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/979839 Title: No X with nvidia-current 270.41.06-0ubuntu1.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/979839/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 696841] Re: vlc stops playing audio after pause/resume or seek
FWIW: 14.04.3 x32, vlc 2.2.1: Using "Reset Preferences" in VLC recreates the problem. This would indicate that the default config exhibits it. And indeed, I initially hit the problem for the very first time after upgrading my machine from Ubuntu 12.04.x LTS to 14.04.3 LTS. The fix suggested above (output module -> ALSA, Device -> PulseAudio Sound Server) still works. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/696841 Title: vlc stops playing audio after pause/resume or seek To manage notifications about this bug go to: https://bugs.launchpad.net/vlc/+bug/696841/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1172500] Re: MP4Client: Modules not found
Get same behavior on 14.04, 0.5.0+svn4288 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1172500 Title: MP4Client: Modules not found To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gpac/+bug/1172500/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1366221] Re: gnome-calculator does not show application menu anywhere
Same problem here, running 14.04 with flashback-metacity. When needed, as a workaround, I'm changing gnome-calculator config using dconf as indicated below, but I certainly would not consider this convenient. $ dconf write /org/gnome/calculator/button-mode "'basic'"; gnome-calculator $ dconf write /org/gnome/calculator/button-mode "'advanced'"; gnome-calculator $ dconf write /org/gnome/calculator/button-mode "'programming'"; gnome-calculator $ dconf write /org/gnome/calculator/button-mode "'financial'"; gnome-calculator -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1366221 Title: gnome-calculator does not show application menu anywhere To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calculator/+bug/1366221/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 996480] Re: gnome-session-fallback most keyboard shortcuts not working as in GNOME 2.32
I see navigating text boxes broken too ( http://library.gnome.org/users /gnome-access-guide/2.32/keynav-28.html.en ) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/996480 Title: gnome-session-fallback most keyboard shortcuts not working as in GNOME 2.32 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/996480/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 770380] Re: power meter panel icon shows duplicated information
I have a variant here: HP Elitebook 8530, two batteries (primary + travel). When on the AC adapter, I get "Laptop battery waiting to charge" on both (always, even when 100% full). Behavior when running on batteries seems to be normal so far. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/770380 Title: power meter panel icon shows duplicated information -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 589140] Re: [i855gm] VGA out flickering after upgrade to lucid (regression)
I see exactly the same thing as Daniel Kulesz mentions at #5. The problem occurs at 1024x768, 60hz and 70hz, and goes away at 75hz (Thanks for finding and reporting this, Daniel!) Since I originally thought this was related to Bug #541511 - MASTER: [i855] GPU lockup (apport-crash) I have tried all the workarounds known from man as mentionned at https://wiki.ubuntu.com/X/Bugs/Lucidi8xxFreezes I could get rid of the boot freeze, but not of the (very intense) flickering, until I ran into Daniel's finding. For certain patterns of display activity, the screen was flickering so strongly that it was mostly unreadable. I'm running 00:02.0 VGA compatible controller [0300]: Intel Corporation 82845G/GL[Brookdale-G]/GE Chipset Integrated Graphics Device [8086:2562] (rev 01) on a Intel motherboard (Pentium M Intel reference motherboard). Screen used is a Hyunday L72S -- [i855gm] VGA out flickering after upgrade to lucid (regression) https://bugs.launchpad.net/bugs/589140 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 589140] Re: [i855gm] VGA out flickering after upgrade to lucid (regression)
Sorry, wrong i885 controller above at #15. Should have been: 00:02.0 VGA compatible controller [0300]: Intel Corporation 82852/855GM Integrated Graphics Device [8086:3582] (rev 02) -- [i855gm] VGA out flickering after upgrade to lucid (regression) https://bugs.launchpad.net/bugs/589140 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 1918948] Re: Issue in Extended Disk Data retrieval (biosdisk: int 13h/service 48h)
Hi Guilherme, My machine is a 10-years old (but i7, quite powerful) HP Elitebook 8560w. Old BIOS, not maintained anymore, that has an experimental / early UEFI that I'd rather not use. The SSD is a 8TB ATA Samsung SSD 870 device. No RAID involved, just a plain 8TB disk. "--disk-module=ahci" get it to work because the Grub ahci native driver support 64-bit LBA adressing, while GRUB by default uses the BIOS LBA, that is 32-bit. Since the partition table is GPT, GRUB has access to all information about the disk size and partition addresses in 64-bit values. It does not have to rely on a legacy DOS partition C/H/S info. I assume GRUB uses BIOS by default to bet maximum compatibility with the real BIOS, and this is fine until your boot files land above the 4TiB limit... which is what happened to me a while after I upgraded my 4TB Crucial disk to an 8TB Samsung one. At that point, Grub failed with a message stating that an "attempt to read outside of hd0" message. The message is actually not accurate, since the boot files are indeed inside the partition. It's just that the BIOS driver is not able to reach them. This problem should happen more and more now that the price of 8TB disks is going down - and people start upgrading. And this is not really Ubuntu not setting the default, as far as I understand it, it's a pure all-GRUB (thus GNU / FSF) problem: The official GRUB documentation mentions that GRUB defaults to BIOS drivers. It would be nice if GRUB were upgraded to default to native drivers when it detects the boot partition crosses the 4TiB limit... Best! On Thu, Jun 2, 2022 at 11:40 PM Guilherme G. Piccoli < 1918...@bugs.launchpad.net> wrote: > @Filofel, thanks for your report! Very interesting. Is your machine a > Dell, running with HW RAID? > > My experience so far with GRUB and this LP bug is that there are two > things here: > > (a) Seems commit [0] might be missing in old Ubuntu releases (IIRC > Xenial, but *maybe* Bionic). This might cause issues with some disks 2T+ > ... > > (b) [And this is the main issue reported in this LP] Dell HW RAID > *legacy BIOS* driver has a bug and fails to inform properly some data to > Grub. In other words: imagine 5x1T disks composing a HW RAID of 5T. Grub > asks BIOS data (through nativedisk likely) and the legacy BIOS driver > from Dell returns data from disk 01 only - 1T of size. So, if GRUB > itself (some module, for example) or the kernel/initrd are present in > sectors *after* disk 01 size, it fails to load. > > For more reference on that, please check the following thread: > https://lists.gnu.org/archive/html/grub-devel/2021-03/msg00380.html > [According Dell, this is "expected" and UEFI is required!] > > > So, your case seems a little bit different. Maybe wirth to clarify the > exact model of your 4T disk, the version of Firmware (and of course the > machine model) and maybe collect some GRUB logs. > Interesting that you mentioned running with "--disk-module=ahci" make it > works - I wonder why this isn't set by defualt on Ubuntu, likely there is a > reason and I'm not aware. > > Cheers! > > > [0] https://git.savannah.gnu.org/cgit/grub.git/commit/?id=d1130afa5f > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1918948 > > Title: > Issue in Extended Disk Data retrieval (biosdisk: int 13h/service 48h) > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1918948/+subscriptions > > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1918948 Title: Issue in Extended Disk Data retrieval (biosdisk: int 13h/service 48h) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1918948/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1284196] Re: Install to 3TB disk fails with "attempt to read or write outside of disk" error on reboot
I ran into the same bug too, booting 20.04.4 from a 4TiB partition partition on a 4TiB disk. I have grub installed in a bios-grub partition, sectors 34-2047. The problem seems to be that by default, Grub uses BIOS drivers to load files from the target partition. When using native grub drivers (ahci in my case), everything works. I solved the problem by re-running a grub-install with parameter --disk-module=ahci The problem with that approach is that any further grub-install without those parms (like an Ubuntu software update might decide to do) will zap the native driver from the Grub partition, and break the boot again. grub-install should never generate a broken boot when it can avoid it: Ideally, when grub detects that at least one of its target partitions crosses the 2TiB boundary, it should give a warning and do a grub-install with the --disk-module=MODULE parameter. 4TB SSD disk prices dropping fast (below 350€ these days). This problem might increasingly show up... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1284196 Title: Install to 3TB disk fails with "attempt to read or write outside of disk" error on reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1284196/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1918948] Re: Issue in Extended Disk Data retrieval (biosdisk: int 13h/service 48h)
I ran into the same bug too, booting 20.04.4 from a 4TiB partition partition on a 4TiB disk. No RAID or LVM, plain 4TB ext4 partition. I have grub installed in a bios-grub partition, sectors 34-2047. The problem seems to be that by default, Grub uses BIOS drivers to load files from the target partition. This is tersely documented in the Grub 2.06 documentation, in the "nativedisk" command paragraph. When using native grub drivers (ahci in my case), everything works. Ditto after running the nativedisk command from the Grub rescue console. I solved the problem by re-running a grub-install with parameter --disk-module=ahci The problem with that approach is that any further grub-install without those parms (like an Ubuntu software update might decide to do) will zap the native driver from the Grub partition, and break the boot again. grub-install should never generate a broken boot when it can avoid it: Ideally, when grub detects that at least one of its target partitions crosses the 2TiB boundary, it should give a warning and do a grub-install with the --disk-module=MODULE parameter. 4TB SSD disk prices dropping fast (below 350€ these days). This problem might increasingly show up... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1918948 Title: Issue in Extended Disk Data retrieval (biosdisk: int 13h/service 48h) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1918948/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1918948] Re: Issue in Extended Disk Data retrieval (biosdisk: int 13h/service 48h)
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1918948 Title: Issue in Extended Disk Data retrieval (biosdisk: int 13h/service 48h) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1918948/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970236] [NEW] Grub2 bios-install defaults to BIOS disk drivers
Public bug reported: Description:Ubuntu 20.04.4 LTS Release:20.04 grub-pc 2.04-1ubuntu26.15 Booting Ubuntu 20.04.4 from a 4TiB partition partition on a 4TiB GPT disk. I have grub bootblocks installed in a bios-grub partition, sectors 34-2047, bios-grub flag. The Ubuntu bootable partition is a plain 4TB ext4. Suddenly, after a routine automatic Ubuntu kernel update, the boot started to break with message: "error: attempt to read or write outside of disk (hd0)." Boot-Repair didn't find nor fix anything. fscheck found nothing bad. After a painful search, I realized that part of the new kernel file had been allocated by the filesystem above the 2TiB limit... Some more investigation in the Grub documentation suggested that by default, Grub uses BIOS drivers to load files from the target partition. This is tersely documented in the Grub 2.06 documentation, in the "nativedisk" command paragraph. And the BIOS drivers are limited to 32-bit sector addresses, i.e. 2TiB. The native Grub drivers don't have this limitation (empirical find, when they are used, the same kernel file loads - and using them fixes the problem for good). So when using native grub drivers (ahci in my case), everything works. Native drivers can be activated from Grub Rescue using nativedisk But a better and longer-lasting solution is to insert them into the bootblocks by running grub-install with a parameter such as --disk-module=ahci (could be ahci, ehci, ATA, ohci or uhci according to harware). So I solved the problem by re-running a grub-install on that disk with parameter --disk-module=ahci The problem with that approach is that any further grub-install without those parms (like an Ubuntu software update or upgrade might decide to do?) will zap the native driver from the Grub partition, and break the boot again. grub-install (and/or update-grub) should never generate a potential broken boot when it can avoid it: Couldn't it (shouldn't it) detect when one of the boot partitions in the boot menu crosses the 2TiB mark, give a warning, and generate a grub-install with the appropriate --disk-module=MODULE parameter? 4TB SSD disk prices dropping fast (below 350€ these days). This problem might increasingly show up... ** Affects: grub2 (Ubuntu) Importance: Undecided Status: New ** Tags: grub grub-pc ** Description changed: Description: Ubuntu 20.04.4 LTS Release: 20.04 + grub-pc 2.04-1ubuntu26.15 + Booting Ubuntu 20.04.4 from a 4TiB partition partition on a 4TiB GPT disk. I have grub bootblocks installed in a bios-grub partition, sectors 34-2047, bios-grub flag. The Ubuntu bootable partition is a plain 4TB ext4. Suddenly, after a routine automatic Ubuntu kernel update, the boot started to break with message: "error: attempt to read or write outside of disk (hd0)." Boot-Repair didn't find nor fix anything. After a painful search, I realized that part of the new kernel file had been allocated by the filesystem above the 2TiB limit... Some more investigation in the Grub documentation suggested that by default, Grub uses BIOS drivers to load files from the target partition. This is tersely documented in the Grub 2.06 documentation, in the "nativedisk" command paragraph. And the BIOS drivers are limited to 32-bit sector addresses, i.e. 2TiB. The native Grub drivers don't have this limitation (empirical find, when they are used, the same kernel file loads!) So when using native grub drivers (ahci in my case), everything works. - Native drivers can be activated from Grub Rescue using - nativedisk + Native drivers can be activated from Grub Rescue using + nativedisk But a better a longer-lasting solution is to insert them into the bootblocks by running grub-install with a parameter such as --disk-module=ahci (could be ehci, ATA, ohci or uhci according to harware). So I solved the problem by re-running a grub-install on that disk with parameter --disk-module=ahci The problem with that approach is that any further grub-install without those parms (like an Ubuntu software update or upgrade might decide to do?) will zap the native driver from the Grub partition, and break the boot again. grub-install (and/or update-grub) should never generate a potential broken boot when it can avoid it: Couldn't it (shouldn't it) detect when one of the boot partitions in the boot menu crosses the 2TiB mark, give a warning, and generate a grub-install with the appropriate --disk-module=MODULE parameter? 4TB SSD disk prices dropping fast (below 350€ these days). This problem might increasingly show up... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970236 Title: Grub2 bios-install defaults to BIOS disk drivers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1970236/+subscripti
[Bug 1970236] Re: Grub2 bios-install defaults to BIOS disk drivers
Added grub-pc package version ** Description changed: Description: Ubuntu 20.04.4 LTS Release: 20.04 grub-pc 2.04-1ubuntu26.15 - Booting Ubuntu 20.04.4 from a 4TiB partition partition on a 4TiB GPT disk. I have grub bootblocks installed in a bios-grub partition, sectors 34-2047, bios-grub flag. The Ubuntu bootable partition is a plain 4TB ext4. Suddenly, after a routine automatic Ubuntu kernel update, the boot started to break with message: "error: attempt to read or write outside of disk (hd0)." Boot-Repair didn't find nor fix anything. + fscheck found nothing bad. After a painful search, I realized that part of the new kernel file had been allocated by the filesystem above the 2TiB limit... Some more investigation in the Grub documentation suggested that by default, Grub uses BIOS drivers to load files from the target partition. This is tersely documented in the Grub 2.06 documentation, in the "nativedisk" command paragraph. And the BIOS drivers are limited to 32-bit sector addresses, i.e. 2TiB. The native Grub drivers don't have this limitation (empirical find, when they are used, the same kernel file loads!) So when using native grub drivers (ahci in my case), everything works. Native drivers can be activated from Grub Rescue using nativedisk But a better a longer-lasting solution is to insert them into the bootblocks by running grub-install with a parameter such as --disk-module=ahci (could be ehci, ATA, ohci or uhci according to harware). So I solved the problem by re-running a grub-install on that disk with parameter --disk-module=ahci The problem with that approach is that any further grub-install without those parms (like an Ubuntu software update or upgrade might decide to do?) will zap the native driver from the Grub partition, and break the boot again. grub-install (and/or update-grub) should never generate a potential broken boot when it can avoid it: Couldn't it (shouldn't it) detect when one of the boot partitions in the boot menu crosses the 2TiB mark, give a warning, and generate a grub-install with the appropriate --disk-module=MODULE parameter? 4TB SSD disk prices dropping fast (below 350€ these days). This problem might increasingly show up... ** Description changed: Description: Ubuntu 20.04.4 LTS Release: 20.04 grub-pc 2.04-1ubuntu26.15 Booting Ubuntu 20.04.4 from a 4TiB partition partition on a 4TiB GPT disk. I have grub bootblocks installed in a bios-grub partition, sectors 34-2047, bios-grub flag. The Ubuntu bootable partition is a plain 4TB ext4. Suddenly, after a routine automatic Ubuntu kernel update, the boot started to break with message: "error: attempt to read or write outside of disk (hd0)." Boot-Repair didn't find nor fix anything. fscheck found nothing bad. After a painful search, I realized that part of the new kernel file had been allocated by the filesystem above the 2TiB limit... Some more investigation in the Grub documentation suggested that by default, Grub uses BIOS drivers to load files from the target partition. This is tersely documented in the Grub 2.06 documentation, in the "nativedisk" command paragraph. And the BIOS drivers are limited to 32-bit sector addresses, i.e. 2TiB. - The native Grub drivers don't have this limitation (empirical find, when they are used, the same kernel file loads!) + The native Grub drivers don't have this limitation (empirical find, when they are used, the same kernel file loads - and using them fixes the problem for good). So when using native grub drivers (ahci in my case), everything works. Native drivers can be activated from Grub Rescue using nativedisk But a better a longer-lasting solution is to insert them into the bootblocks by running grub-install with a parameter such as --disk-module=ahci (could be ehci, ATA, ohci or uhci according to harware). So I solved the problem by re-running a grub-install on that disk with parameter --disk-module=ahci The problem with that approach is that any further grub-install without those parms (like an Ubuntu software update or upgrade might decide to do?) will zap the native driver from the Grub partition, and break the boot again. grub-install (and/or update-grub) should never generate a potential broken boot when it can avoid it: Couldn't it (shouldn't it) detect when one of the boot partitions in the boot menu crosses the 2TiB mark, give a warning, and generate a grub-install with the appropriate --disk-module=MODULE parameter? 4TB SSD disk prices dropping fast (below 350€ these days). This problem might increasingly show up... ** Description changed: Description: Ubuntu 20.04.4 LTS Release: 20.04 grub-pc 2.04-1ubuntu26.15 Booting Ubuntu 20.04.4 from a 4TiB partition partition on a 4TiB GPT disk. I have grub bootblocks installed in a bios-grub partition, sectors
[Bug 1970236] Re: Grub2 bios-install defaults to BIOS disk drivers
** Description changed: Description: Ubuntu 20.04.4 LTS Release: 20.04 grub-pc 2.04-1ubuntu26.15 Booting Ubuntu 20.04.4 from a 4TiB partition partition on a 4TiB GPT disk. I have grub bootblocks installed in a bios-grub partition, sectors 34-2047, bios-grub flag. The Ubuntu bootable partition is a plain 4TB ext4. Suddenly, after a routine automatic Ubuntu kernel update, the boot started to break with message: "error: attempt to read or write outside of disk (hd0)." Boot-Repair didn't find nor fix anything. fscheck found nothing bad. After a painful search, I realized that part of the new kernel file had been allocated by the filesystem above the 2TiB limit... - Some more investigation in the Grub documentation suggested that by default, Grub uses BIOS drivers to load files from the target partition. This is tersely documented in the Grub 2.06 documentation, in the "nativedisk" command paragraph. + Some more investigation suggested that by default, Grub uses BIOS drivers to load files from the target partition. This is tersely documented in the Grub 2.06 documentation, in the "nativedisk" command paragraph. And the BIOS drivers are limited to 32-bit sector addresses, i.e. 2TiB. The native Grub drivers don't have this limitation (empirical find, when they are used, the same kernel file loads - and using them fixes the problem for good). So when using native grub drivers (ahci in my case), everything works. Native drivers can be activated from Grub Rescue using nativedisk But a better and longer-lasting solution is to insert them into the bootblocks by running grub-install with a parameter such as - --disk-module=ahci - (could be ahci, ehci, ATA, ohci or uhci according to harware). + --disk-module=ahci + (could be ahci, ehci, ATA, ohci or uhci according to harware): + grub-install --disk-module=ahci /dev/sdaX - So I solved the problem by re-running a grub-install on that disk with parameter - --disk-module=ahci - The problem with that approach is that any further grub-install without those parms (like an Ubuntu software update or upgrade might decide to do?) will zap the native driver from the Grub partition, and break the boot again. + The problem with that approach is that any further grub-install without + those parms (like an Ubuntu software update or upgrade might decide to + do?) will zap the native driver from the Grub partition, and break the + boot again. grub-install (and/or update-grub) should never generate a potential broken boot when it can avoid it: Couldn't it (shouldn't it) detect when one of the boot partitions in the boot menu crosses the 2TiB mark, give a warning, and generate a grub-install with the appropriate --disk-module=MODULE parameter? 4TB SSD disk prices dropping fast (below 350€ these days). This problem might increasingly show up... ** Description changed: Description: Ubuntu 20.04.4 LTS Release: 20.04 grub-pc 2.04-1ubuntu26.15 Booting Ubuntu 20.04.4 from a 4TiB partition partition on a 4TiB GPT disk. - I have grub bootblocks installed in a bios-grub partition, sectors 34-2047, bios-grub flag. - The Ubuntu bootable partition is a plain 4TB ext4. + I have grub bootblocks installed in a bios-grub partition, sectors 34-2047, bios-grub flag set. + The Ubuntu bootable partition is a plain 4TB ext4 filling up the rest of the disk. Suddenly, after a routine automatic Ubuntu kernel update, the boot started to break with message: "error: attempt to read or write outside of disk (hd0)." Boot-Repair didn't find nor fix anything. fscheck found nothing bad. + Using Grub rescue showed this happened when loading the new kernel. + Previous linux images were still booting. After a painful search, I realized that part of the new kernel file had been allocated by the filesystem above the 2TiB limit... - Some more investigation suggested that by default, Grub uses BIOS drivers to load files from the target partition. This is tersely documented in the Grub 2.06 documentation, in the "nativedisk" command paragraph. + Some more investigation suggested that by default, Grub uses BIOS drivers to load files from the target partition. This is tersely documented in the Grub 2.06 documentation, in the "nativedisk" command paragraph. And the BIOS drivers are limited to 32-bit sector addresses, i.e. 2TiB. The native Grub drivers don't have this limitation (empirical find, when they are used, the same kernel file loads - and using them fixes the problem for good). So when using native grub drivers (ahci in my case), everything works. Native drivers can be activated from Grub Rescue using nativedisk But a better and longer-lasting solution is to insert them into the bootblocks by running grub-install with a parameter such as - --disk-module=ahci - (could be ahci, ehci, ATA, ohci or uhci according to harware): - grub-install --disk-module=ahci /d
[Bug 1970236] Re: Grub2 bios-install defaults to BIOS disk drivers, breaks boot
** Summary changed: - Grub2 bios-install defaults to BIOS disk drivers + Grub2 bios-install defaults to BIOS disk drivers, breaks boot ** Summary changed: - Grub2 bios-install defaults to BIOS disk drivers, breaks boot + Grub2 bios-install defaults to BIOS disk drivers, may break large disk boot -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970236 Title: Grub2 bios-install defaults to BIOS disk drivers, may break large disk boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1970236/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970236] Re: Grub2 bios-install defaults to BIOS disk drivers, may break large disk boot
Hi mkukri, I'm using an HP Elitebook 8760W, released in 2011. It's great fast, powerful, two internal SATA slots, very large RAM, and carbon footprint largely amortized by now. And it's i7 is still largely fast and powerful enough for most usages, and I don't see the need for buying a new machine, and I would instantly recommend a similar refurbished machine over brand new cheap ones. Heck, it was a Rolls Royce in 2011! But its UEFI BIOS is a prototype (it warns / displays so and can't be fixed), not reliable, and hackable by rootkits and other malwares. OTOH, it works and boots fine with Grub native drivers, and I haven't had any problem since I figured the default 32-bit BIOS drivers out (april 2022), fixed the problem and posted this message. The Grub config wasn't altered through OS and/or Grub updates / upgrades, not even upgrading from 20.04 to 22.04, so I guess I'm safe enough. Too bad that Grub doesn't autodetect and autofix the BIOS-Grub / BIOS driver on disks > 2TiB though, since that's a guaranteed failure. While using native drivers is only a hazard - and not even one as far as I'm concerned! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970236 Title: Grub2 bios-install defaults to BIOS disk drivers, may break large disk boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1970236/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970236] Re: Grub2 bios-install defaults to BIOS disk drivers, may break large disk boot
Hi Ben, the answer to your question (and the solution to our common problem) is located in the Bug Description for this very bug, that I updated with all the gory details (up this message) and globally there: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1970236 that says: "But a better and longer-lasting solution is to insert the native driver into the bootblocks by running grub-install with a parameter such as --disk-module=ahci " The good news is that the solution I suggested back then resisted so far all updates, and it even resisted and upgrade from 20.04 to 22.04. And I'm still running my good'ole Elitebook 8760w while writing this! ;-) " -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970236 Title: Grub2 bios-install defaults to BIOS disk drivers, may break large disk boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1970236/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
