[Bug 95857] Re: [feisty] kernel boot delayed 60 secs on floppy error
There seems to be no way to avoid the problem by changing a BIOS setting on my Dell Latitude C400. BIOS setup utility already claims that there is no floppy drive installed. Probably, BIOS provides a kind of placeholder device for future attachment of the floppy drive. There exists a workaround for this problem (tested on kubuntu-7.04-alternate-i386): modprobe -r floppy rm /lib/modules/`uname -r`/kernel/drivers/block/floppy.ko This removes the floppy module from memory and then from ramdisk to prevent reloading it. -- [feisty] kernel boot delayed 60 secs on floppy error https://bugs.launchpad.net/bugs/95857 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 341202] Re: Firefox crashes on sqlite3 memcpy segfault
I have encountered this bug on Ubuntu 9.04: firefox-3.0.13+nobinonly- 0ubuntu0.9.04.1, sqlite-3.6.10-1ubuntu0.2. with libsqlite-dbg package installed, backtrace of the coredump gives the following: (gdb) bt #0 0xb7fb5430 in __kernel_vsyscall () #1 0xb7f984b0 in raise () from /lib/tls/i686/cmov/libpthread.so.0 #2 0xb71b4145 in ?? () from /usr/lib/xulrunner-1.9.0.13/libxul.so #3 #4 0xb7d788aa in memcpy () from /lib/tls/i686/cmov/libc.so.6 #5 0xb6fd3cbd in fillInCell (pPage=, pCell=0xa7cbf88 "", pKey=0x0, nKey=611190, pData=0x0, nData=0, nZero=0, pnSize=0xb23f65d0) at /usr/include/bits/string3.h:52 #6 0xb6fd5e0e in balance_nonroot (pCur=0x9c19294) at sqlite3.c:41705 #7 0xb6fd4640 in balance (pCur=0x9c19294, isInsert=244) at sqlite3.c:42013 #8 0xb6fdd26a in sqlite3BtreeInsert (pCur=0x9c19294, pKey=0xa37ad80, nKey=10, pData=0xb7014e74, nData=0, nZero=0, appendBias=0) at sqlite3.c:42177 #9 0xb6fe9c19 in sqlite3VdbeExec (p=0x9dd41a8) at sqlite3.c:52819 #10 0xb6ff03b0 in sqlite3_step (pStmt=0x9dd41a8) at sqlite3.c:47849 #11 0xb7857610 in ?? () from /usr/lib/xulrunner-1.9.0.13/libxul.so #12 0xb7856f19 in ?? () from /usr/lib/xulrunner-1.9.0.13/libxul.so #13 0xb775916c in ?? () from /usr/lib/xulrunner-1.9.0.13/libxul.so #14 0xb776057d in ?? () from /usr/lib/xulrunner-1.9.0.13/libxul.so #15 0xb7761a2e in ?? () from /usr/lib/xulrunner-1.9.0.13/libxul.so #16 0xb7761b4e in ?? () from /usr/lib/xulrunner-1.9.0.13/libxul.so #17 0xb7974af1 in NS_InvokeByIndex_P () from /usr/lib/xulrunner-1.9.0.13/libxul.so #18 0xb796ce6d in ?? () from /usr/lib/xulrunner-1.9.0.13/libxul.so #19 0xb7968c50 in ?? () from /usr/lib/xulrunner-1.9.0.13/libxul.so #20 0xb79394dc in ?? () from /usr/lib/xulrunner-1.9.0.13/libxul.so #21 0xb79693b7 in ?? () from /usr/lib/xulrunner-1.9.0.13/libxul.so #22 0xb7c4b151 in ?? () from /usr/lib/libnspr4.so #23 0xb7f904ff in start_thread () from /lib/tls/i686/cmov/libpthread.so.0 #24 0xb7de349e in clone () from /lib/tls/i686/cmov/libc.so.6 Every time firefox crashed, the backtrace was identical. Reinstalling firefox, xulrunner and sqlite, rebuilding sqlite from sources (dpkg- buildpackage) didn't help. Since having downloaded, built and installed the newest sqlite release (3.6.17), the bug does not happen anymore. I recommend to upgrade the official Ubuntu packages, because it seems that sqlite team fixed a lot of strange bugs, especially related to operation with corrupted databases. -- Firefox crashes on sqlite3 memcpy segfault https://bugs.launchpad.net/bugs/341202 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 1320485] Re: about:startpage is http://start.ubuntu.com/13.10/Google/ on Ubuntu 14.04
Hello Stéphane, Chris, Martin, I just downloaded and installed xul-ext- ubufox_2.9-0ubuntu0.14.04.1_all.deb and I confirm that it fixes the issue. The about:startpage site is now correctly fetched from http://start.ubuntu.com/14.04/Google/?sourceid=hp Best regards, Michał -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1320485 Title: about:startpage is http://start.ubuntu.com/13.10/Google/ on Ubuntu 14.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubufox/+bug/1320485/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 878612] Re: Linker fails when compiling fuse files with "undefined reference to `fuse_main_real'
I corrected the Makefile by reordering LDFLAGS similarly to how Flávio Martins (xhaker) suggested, fixed installation of fioc.h header which was needed to build all the examples (including cusexmp, fioc, fioclient, fsel, fselclient) and uploaded the package to my PPA (at the time of writing, pending to be built): https://launchpad.net/~maw/+archive/fixes -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/878612 Title: Linker fails when compiling fuse files with "undefined reference to `fuse_main_real' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fuse/+bug/878612/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 740785] Re: Caught signal 11 (Segmentation fault). Server aborting
My 64-bit Maverick runs without a crash for 9 days now on 270.41.06 nVidia binary drivers. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/740785 Title: Caught signal 11 (Segmentation fault). Server aborting -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 778490] Re: Random logout after upgrading to Natty Narwhal 11.04
William and Daniel, thanks for noticing the (partial?) relationship with other bugs. That's how I found this one. badhorse, ZaHACKieL and Daniel -- you mention using nVidia cards. I run a 64-bit Maverick with nVidia card as well. In my case, the bug seems to disappear after upgrading nVidia binary drivers to 270.41.06 using ppa:ubuntu-x-swat/x-updates. Can you provide your Xorg.log after a crash (/var/log/Xorg.0.log.old copied after logging in again), so that there can be more certainty that you have the same bug as I did? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/778490 Title: Random logout after upgrading to Natty Narwhal 11.04 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 740785] Re: Caught signal 11 (Segmentation fault). Server aborting
I was getting the same error as Ian, JPM ( #775705) and qwazi on my 64-bit Maverick with nVidia binary drivers (260.19.06). No compiz here, but extensively using VMware Player with 3D acceleration. According to a hint by Paul de Vries (http://vimeo.com/groups/cinelerra/forumthread:236340), I have updated the nVidia drivers. I took 270.41.06 from ppa:ubuntu-x-swat/x-updates. I will report whether it stopped crashing. ** Attachment added: "Xorg.crash.log" https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/740785/+attachment/2124313/+files/Xorg.crash.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/740785 Title: Caught signal 11 (Segmentation fault). Server aborting -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 740785] Re: Caught signal 11 (Segmentation fault). Server aborting
Unfortunately, my Xorg on the new nVidia drivers crashed, but this time on another account with compiz enabled and during non-3D work (just a terminal and a browser, no VMware). The backtrace was this time quite different. ** Attachment added: "Xorg.crash3.log" https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/740785/+attachment/2124357/+files/Xorg.crash3.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/740785 Title: Caught signal 11 (Segmentation fault). Server aborting -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 740785] Re: Caught signal 11 (Segmentation fault). Server aborting
** Attachment removed: "Xorg.crash3.log" https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/740785/+attachment/2124357/+files/Xorg.crash3.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/740785 Title: Caught signal 11 (Segmentation fault). Server aborting -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 740785] Re: Caught signal 11 (Segmentation fault). Server aborting
Please ignore my comment #14 for now, as this seems to be a completely different bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/740785 Title: Caught signal 11 (Segmentation fault). Server aborting -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
