bug: 553745 title: plymouthd crashed with SIGSEGV in ply_event_loop_process_pending_events() date-reported: Fri, 02 Apr 2010 02:20:10 -0000 date-updated: Sat, 30 Nov 2013 04:01:06 -0000 reporter: j0sh (zerounix) duplicate-of: duplicates: 553812 553867 553908 553991 554130 554218 554220 554395 554430 554519 554525 554568 554629 554793 554802 554851 554893 554914 554942 554955 555050 555207 555231 555331 555379 555402 555517 555572 555712 556030 556160 556177 556250 556266 556307 556366 556423 556542 556588 556701 556706 556720 556840 556873 556949 556981 557008 557086 557219 557221 557267 557339 557366 557377 557733 557768 558645 559207 559877 638423 639648 640359 640853 649603 710899 710974 713574 718230 721059 722126 723801 725253 730424 732468 737056 739255 752215 849414 850951 850952 851082 851468 851591 852253 852327 852527 853059 853097 854173 854291 854499 854742 854966 855502 855822 856168 856445 857544 857898 858233 858317 858638 858743 858932 859332 861037 861824 861940 862071 862095 862371 862414 862421 862472 862805 863417 863431 863712 864289 864385 864393 864895 865736 867478 867817 868008 868231 869090 869232 869985 870113 870243 870399 870613 870820 871117 871181 871331 871591 871660 871868 897001 897306 897420 898886 901106 903372 903704 904389 904509 904865 905116 906156 906412 909530 909727 910548 910632 912887 914929 915821 916068 916363 918160 918407 918700 919633 919894 920396 920778 920904 921262 922313 923054 924334 926410 928944 929477 929721 930592 930666 931285 931478 931623 932650 932679 933651 935888 936406 936833 936949 937095 937926 938522 938664 940303 940778 940866 940998 941767 943814 944167 944194 944243 944419 944777 945464 946105 946205 946906 946952 946975 948431 948654 949915 950511 950721 950839 951349 952060 952160 952611 952651 953624 954073 954209 954266 955606 955651 955891 956126 956467 956529 956998 957766 958538 959059 959328 959528 960826 960924 961134 961167 961604 961607 962663 962787 962877 962922 963765 963910 964159 964326 964366 964715 964834 965354 965639 965745 965781 965924 966500 966589 966626 966877 966923 967270 967993 968441 968991 attachments: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/553745/+attachment/1265092/+files/BootDmesg.txt text/plain; charset="utf-8" https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/553745/+attachment/1265094/+files/CurrentDmesg.txt text/plain; charset="utf-8" https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/553745/+attachment/1265095/+files/Dependencies.txt text/plain; charset="utf-8" https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/553745/+attachment/1265096/+files/Disassembly.txt text/plain; charset="utf-8" https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/553745/+attachment/1265097/+files/Lspci.txt text/plain; charset="utf-8" https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/553745/+attachment/1265098/+files/Lsusb.txt text/plain; charset="utf-8" https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/553745/+attachment/1265099/+files/ProcCpuinfo.txt text/plain; charset="utf-8" https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/553745/+attachment/1265100/+files/ProcInterrupts.txt text/plain; charset="utf-8" https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/553745/+attachment/1265101/+files/ProcMaps.txt text/plain; charset="utf-8" https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/553745/+attachment/1265102/+files/ProcModules.txt text/plain; charset="utf-8" https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/553745/+attachment/1265103/+files/ProcStatus.txt text/plain; charset="utf-8" https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/553745/+attachment/1265104/+files/Registers.txt text/plain; charset="utf-8" https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/553745/+attachment/1265105/+files/Stacktrace.txt text/plain; charset="utf-8" https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/553745/+attachment/1265106/+files/ThreadStacktrace.txt text/plain; charset="utf-8" https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/553745/+attachment/1265107/+files/UdevDb.txt text/plain; charset="utf-8" https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/553745/+attachment/1265108/+files/UdevLog.txt text/plain; charset="utf-8" https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/553745/+attachment/1272169/+files/Stacktrace.txt text/plain https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/553745/+attachment/1272170/+files/ThreadStacktrace.txt text/plain https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/553745/+attachment/1311825/+files/xorg.conf text/plain https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/553745/+attachment/1323418/+files/Xorg.0.log text/plain https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/553745/+attachment/1401949/+files/BootDmesg.txt text/plain https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/553745/+attachment/1401950/+files/CurrentDmesg.txt text/plain https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/553745/+attachment/1401951/+files/Dependencies.txt text/plain https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/553745/+attachment/1401952/+files/Lspci.txt text/plain https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/553745/+attachment/1401953/+files/Lsusb.txt text/plain https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/553745/+attachment/1401954/+files/ProcCpuinfo.txt text/plain https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/553745/+attachment/1401955/+files/ProcInterrupts.txt text/plain https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/553745/+attachment/1401956/+files/ProcModules.txt text/plain https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/553745/+attachment/1401957/+files/UdevDb.txt text/plain https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/553745/+attachment/1401958/+files/UdevLog.txt text/plain https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/553745/+attachment/1766850/+files/syslog text/plain https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/553745/+attachment/2380871/+files/_sbin_plymouthd.0.crash text/plain https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/553745/+attachment/2395909/+files/BootDmesg.txt text/plain https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/553745/+attachment/2395910/+files/CurrentDmesg.txt text/plain https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/553745/+attachment/2395911/+files/Dependencies.txt text/plain https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/553745/+attachment/2395912/+files/EtcDefaultGrub.txt text/plain https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/553745/+attachment/2395913/+files/Lspci.txt text/plain https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/553745/+attachment/2395914/+files/Lsusb.txt text/plain https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/553745/+attachment/2395915/+files/ProcCpuinfo.txt text/plain https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/553745/+attachment/2395916/+files/ProcInterrupts.txt text/plain https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/553745/+attachment/2395922/+files/ProcModules.txt text/plain https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/553745/+attachment/2395923/+files/UdevDb.txt text/plain https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/553745/+attachment/2395924/+files/UdevLog.txt text/plain https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/553745/+attachment/2437867/+files/plymouth-debug.log text/plain https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/553745/+attachment/2597194/+files/plymouth-debug.log text/plain patches: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/553745/+attachment/1369678/+files/45.diff text/plain tags: apport-collected apport-crash bugpattern-written i386 iso-testing lucid patch-forwarded-upstream precise raring rls-mgr-p-tracking rls-p-tracking subscribers: j0sh (zerounix) Apport retracing service (apport) Crash bug triagers for Ubuntu packages (ubuntu-crashes-universe) Mathieu Marquer (slasher-fun) Martin Pitt (pitti) Ddiods (ddiods) mikbini (mikbini) Ken Richards (kenrichards) Son (son.caokim) luca (l-savio) Martin Karpinski (mkarpinski) pascalc (pascal-chevrel) Paul Turner (paulj-turner1) Francis De Brabandere (francisdb) Bordi (borderlinedancer) Homer Smith (homermsmith) Javier (javiersmail) Chaostya (chaostya) LumpyCustard (orangelumpycustard) Krishna (kpulusu) Ernst (ernst-blaauw) Gilles (gilles-civario) jack bakunin (jackbakunin) Ubuntu Review Team (ubuntu-reviewers) Neil Perry (nperry) Nicolò Chieffo (yelo3) Vincent Ladeuil (vila) RussianNeuroMancer (russianneuromancer) smoosh (lolomcdoo) Andrea Caminiti (nrayever) Jaime Rave (jaimerave) Gary M (garym) Nicolas DERIVE (kalon33) Leo Arias (elopio) Wira (wms7939) Martin Wildam (mwildam) Dave Chiluk (chiluk) Eugene Savelov (savelov) Jason Airlie (jairlie) Dmitry Shachnev (mitya57) Trebacz (david-trebacz) Bruce Pieterse (octoquad) Monkey (monkey-libre) Ragmaanir (ragmaanir) Ludovic (draco91) dino99 (9d9) Willem Vanhulle (wlvh42) Frank Schreuder (frankschreuder-443) Eduard Hasenleithner (eduard-hasenleithner) Tim Kornhammar (tim-kornhammar) Jared (jared-vanvolkenburg) Yeri (yeri-riveyplus) stop (whoopwhoop) johnlon (jakewc2) K790 (sonyk790) Pit(er) Ralon (pitralon) Santtu Salonen (shortboard74) martyfelker (martyfelker-gmail) Jaakan Shorter (jaakanshorter) Erick John Cuevas (stjohnmedrano) Antec (info-janmob) Mark Wallace (shorty9039) iGadget (igadget) Ewano (i-launchpad-ewano-net) Brian Mastenbrook (bmastenbrook) Ernesto Celis (celisdelafuente) Philip Stark (hellerbarde) Guillaume Romagny (golfromeo.ovh) Tormod Volden (tormodvolden) Christian Diefenbach (christiand59) Rafael Peñates (androxvanxo) Jason Kern (jaskerx) Christopher Forster (christopherforster) Colin Mills (cm006a5077) Mo Z (zmau1962) task: plymouth status: Fix Released date-created: Sat, 10 Apr 2010 07:14:35 -0000 date-triaged: Fri, 27 Apr 2012 13:30:30 -0000 date-inprogress: Fri, 27 Apr 2012 13:30:30 -0000 date-closed: Fri, 27 Apr 2012 13:30:30 -0000 date-fix-committed: Fri, 27 Apr 2012 13:30:30 -0000 date-fix-released: Fri, 27 Apr 2012 13:30:30 -0000 reporter: Dmitriy (dimkapodol) watch: https://bugs.freedesktop.org/show_bug.cgi?id=28548 importance: Medium assignee: milestone: task: plymouth (Ubuntu) status: Fix Released date-created: Fri, 02 Apr 2010 02:20:10 -0000 date-left-new: Tue, 06 Apr 2010 06:10:06 -0000 date-confirmed: Sat, 10 Mar 2012 06:28:42 -0000 date-triaged: Fri, 13 Apr 2012 15:34:02 -0000 date-assigned: Wed, 20 Apr 2011 16:45:59 -0000 date-inprogress: Fri, 13 Apr 2012 15:34:02 -0000 date-closed: Fri, 13 Apr 2012 15:34:02 -0000 date-fix-committed: Fri, 13 Apr 2012 15:34:02 -0000 date-fix-released: Fri, 13 Apr 2012 15:34:02 -0000 date-left-closed: Wed, 14 Sep 2011 13:27:57 -0000 reporter: j0sh (zerounix) importance: High component: main assignee: James Hunt (jamesodhunt) milestone: ubuntu-12.04 task: plymouth (Ubuntu Natty) status: Fix Released date-created: Tue, 19 Oct 2010 14:44:44 -0000 date-left-new: Tue, 06 Apr 2010 06:10:06 -0000 date-confirmed: Tue, 13 Apr 2010 23:09:22 -0000 date-triaged: Tue, 13 Apr 2010 23:09:22 -0000 date-assigned: Wed, 20 Apr 2011 16:45:59 -0000 date-inprogress: Thu, 24 Mar 2011 14:20:33 -0000 date-closed: Thu, 24 Mar 2011 14:20:33 -0000 date-fix-committed: Thu, 24 Mar 2011 14:20:33 -0000 date-fix-released: Thu, 24 Mar 2011 14:20:33 -0000 reporter: Kate Stewart (kate.stewart) importance: High assignee: Canonical Foundations Team (canonical-foundations) milestone: task: plymouth (Ubuntu Precise) status: Fix Released date-created: Fri, 30 Sep 2011 19:11:23 -0000 date-left-new: Fri, 30 Sep 2011 19:11:50 -0000 date-confirmed: Sat, 10 Mar 2012 06:28:42 -0000 date-triaged: Fri, 13 Apr 2012 15:34:02 -0000 date-assigned: Fri, 30 Sep 2011 19:12:17 -0000 date-inprogress: Fri, 13 Apr 2012 15:34:02 -0000 date-closed: Fri, 13 Apr 2012 15:34:02 -0000 date-fix-committed: Fri, 13 Apr 2012 15:34:02 -0000 date-fix-released: Fri, 13 Apr 2012 15:34:02 -0000 reporter: Kate Stewart (kate.stewart) importance: High component: main assignee: James Hunt (jamesodhunt) milestone: ubuntu-12.04 Content-Type: multipart/mixed; boundary="===============4591571337669137179==" MIME-Version: 1.0 --===============4591571337669137179== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Binary package hint: plymouth just upgraded to lucid, first reboot tried to start accounts ProblemType: Crash DistroRelease: Ubuntu 10.04 Package: plymouth 0.8.1-4 ProcVersionSignature: Ubuntu 2.6.32-19.28-generic 2.6.32.10+drm33.1 Uname: Linux 2.6.32-19-generic i686 NonfreeKernelModules: wl Architecture: i386 Date: Thu Apr 1 22:14:11 2010 DefaultPlymouth: /lib/plymouth/themes/kubuntu-logo/kubuntu-logo.plymouth ExecutablePath: /sbin/plymouthd MachineType: Dell Inc. Inspiron 1545 ProcCmdLine: root=3DUUID=3D73530dc8-e3cc-4147-b801-4725b2f88141 ro quiet sp= lash vga=3D792 ProcCmdline: /sbin/plymouthd --mode=3Dboot --attach-to-session ProcEnviron: PATH=3D(custom, no user) ProcFB: 0 inteldrmfb SegvAnalysis: Segfault happened at: 0xfb5fe1 = : test %eax,0x4(%esi) PC (0x00fb5fe1) ok source "%eax" ok destination "0x4(%esi)" (0x00000004) not located in a known VMA region (ne= eded writable region)! SegvReason: writing NULL VMA Signal: 11 SourcePackage: plymouth StacktraceTop: ply_event_loop_process_pending_events () ply_event_loop_run () from /lib/libply.so.2 ?? () __libc_start_main () from /lib/tls/i686/cmov/libc.so.6 ?? () TextPlymouth: /lib/plymouth/themes/ubuntu-text/ubuntu-text.plymouth Title: plymouthd crashed with SIGSEGV in ply_event_loop_process_pending_eve= nts() UserGroups: =20 dmi.bios.date: 07/17/2009 dmi.bios.vendor: Dell Inc. dmi.bios.version: A10 dmi.board.name: 0G848F dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA10:bd07/17/2009:svnDellInc.:pnInspiron154= 5:pvr:rvnDellInc.:rn0G848F:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Inspiron 1545 dmi.sys.vendor: Dell Inc. --===============4591571337669137179== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: j0sh (zerounix) Date: Fri, 02 Apr 2010 02:20:10 -0000 Message-Id: <20100402022011.9520.42145.malone@gandwana.canonical.com> --===============4591571337669137179== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Apport retracing service (apport) Date: Sat, 03 Apr 2010 22:19:27 -0000 Message-Id: <20100403221927.22052.89285.malone@soybean.canonical.com> StacktraceTop: ply_event_loop_process_pending_events ( ply_event_loop_run (loop=3D0x90280a8) at ply-event-loop.c:1312 main (argc=3D3, argv=3D0xbfeba124) at main.c:1916 --===============4591571337669137179== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Apport retracing service (apport) Date: Sat, 03 Apr 2010 22:19:29 -0000 Message-Id: <20100403221929.22052.74621.malone@soybean.canonical.com> --===============4591571337669137179== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Apport retracing service (apport) Date: Sat, 03 Apr 2010 22:19:32 -0000 Message-Id: <20100403221932.22652.65449.malone@potassium.ubuntu.com> --===============4591571337669137179== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: xteejx (xteejx) Date: Wed, 07 Apr 2010 17:55:46 -0000 Message-Id: <20100407175546.15753.65417.malone@wampee.canonical.com> This seemed to happen randomly for me, but didn't appear to affect system stability. --===============4591571337669137179== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: swests (simon-thewests) Date: Wed, 07 Apr 2010 19:23:53 -0000 Message-Id: <20100407192354.32093.41058.malone@soybean.canonical.com> I only seem to get this when I use the new nouveau driver. If I use the Nvidia (Current version) driver I don't seem to get the problem. --===============4591571337669137179== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: NeilGreenwood (neil-greenwood) Date: Wed, 07 Apr 2010 19:56:43 -0000 Message-Id: <20100407195643.15753.53647.malone@wampee.canonical.com> I don't have a Nvidia graphics card in the laptop where I saw this crash. lspci shows: Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics = Controller [8086:27a2] --===============4591571337669137179== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Martin Pitt (pitti) Date: Wed, 07 Apr 2010 20:15:56 -0000 Message-Id: <20100407201556.GA2044@piware.de> For the record, I get this crash on a Dell Mini 10, with Intel 945. --===============4591571337669137179== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: xteejx (xteejx) Date: Wed, 07 Apr 2010 20:30:35 -0000 Message-Id: <20100407203035.1180.32851.malone@palladium.canonical.com> Compaq Presario CQ50 laptop Geforce 8200M here. --===============4591571337669137179== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: xteejx (xteejx) Date: Wed, 07 Apr 2010 20:33:24 -0000 Message-Id: <20100407203324.1180.50952.malone@palladium.canonical.com> Using (current) nvidia driver as well, missed that out. Doesn't look like a graphics driver issue. --===============4591571337669137179== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Mark Cariaga (mzc) Date: Wed, 07 Apr 2010 23:45:55 -0000 Message-Id: <1270683955.1832.1.camel@mark-netbook2> @Martin Pitt: I have an AOD250 and HP mini 110-1116NR, both exhibit the bug.=20 On Wed, 2010-04-07 at 20:15 +0000, Martin Pitt wrote: > For the record, I get this crash on a Dell Mini 10, with Intel 945. > --===============4591571337669137179== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Mark Cariaga (mzc) Date: Wed, 07 Apr 2010 23:46:51 -0000 Message-Id: <1270684011.1832.2.camel@mark-netbook2> @Martin Pitt: I have an AOD250 and a HP mini 110-1116NR both exhibit the same bug On Wed, 2010-04-07 at 20:15 +0000, Martin Pitt wrote: > For the record, I get this crash on a Dell Mini 10, with Intel 945. > --===============4591571337669137179== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Martin Spacek (mspacek) Date: Thu, 08 Apr 2010 00:29:33 -0000 Message-Id: <20100408002933.9079.76684.malone@gandwana.canonical.com> I got this on my Thinkpad W510, quite randomly soon after bootup. It's only happened once so far. I'm running the latest 64 bit lucid, with the latest nvidia binary drivers. --===============4591571337669137179== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Ruben Verweij (ruben-verweij) Date: Thu, 08 Apr 2010 06:57:34 -0000 Message-Id: <20100408065734.9079.86388.malone@gandwana.canonical.com> Also see this with dual monitors using nouveau on a nVidia Corporation NV44A [GeForce 6200] (rev a1). --===============4591571337669137179== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Alessandro Losavio (alo21) Date: Thu, 08 Apr 2010 12:08:47 -0000 Message-Id: <20100408120847.15797.40570.malone@wampee.canonical.com> when i want to update my system there was this bug --===============4591571337669137179== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Yann (lostec) Date: Thu, 08 Apr 2010 14:03:23 -0000 Message-Id: <20100408140323.5035.62991.malone@potassium.ubuntu.com> I had this bug, running pae kernel in a VirtualBox VM: Disk check was running and freezed at this moment... syslog output around crash: **** Apr 8 16:15:53 yann-laptop NetworkManager: Activation (eth0) Stage= 5 of 5 (IP Configure Commit) scheduled... Apr 8 16:15:53 yann-laptop NetworkManager: Activation (eth0) Stage= 4 of 5 (IP4 Configure Get) complete. Apr 8 16:15:53 yann-laptop NetworkManager: Activation (eth0) Stage= 5 of 5 (IP Configure Commit) started... Apr 8 16:15:53 yann-laptop avahi-daemon[547]: Joining mDNS multicast group= on interface eth0.IPv4 with address 10.0.2.15. Apr 8 16:15:53 yann-laptop avahi-daemon[547]: New relevant interface eth0.= IPv4 for mDNS. Apr 8 16:15:53 yann-laptop avahi-daemon[547]: Registering new address reco= rd for 10.0.2.15 on eth0.IPv4. Apr 8 16:15:53 yann-laptop dhclient: bound to 10.0.2.15 -- renewal in 3310= 2 seconds. Apr 8 16:15:53 yann-laptop kernel: [ 44.457002] vboxguest: exports dupli= cate symbol RTMemExecFree (owned by vboxdrv) Apr 8 16:15:54 yann-laptop NetworkManager: (eth0): device state ch= ange: 7 -> 8 (reason 0) Apr 8 16:15:54 yann-laptop NetworkManager: Policy set 'Auto eth0' = (eth0) as default for routing and DNS. Apr 8 16:15:54 yann-laptop NetworkManager: Activation (eth0) succe= ssful, device activated. Apr 8 16:15:54 yann-laptop NetworkManager: Activation (eth0) Stage= 5 of 5 (IP Configure Commit) complete. Apr 8 14:15:57 yann-laptop ntpdate[901]: step time server 91.189.94.4 offs= et -7198.369434 sec Apr 8 14:16:01 yann-laptop kernel: [ 51.051506] eth0: no IPv6 routers pr= esent Apr 8 14:17:01 yann-laptop CRON[952]: (root) CMD ( cd / && run-parts --r= eport /etc/cron.hourly) Apr 8 17:44:21 yann-laptop kernel: imklog 4.2.0, log source =3D /proc/kmsg= started. Apr 8 17:44:21 yann-laptop rsyslogd: [origin software=3D"rsyslogd" swVersi= on=3D"4.2.0" x-pid=3D"514" x-info=3D"http://www.rsyslog.com"] (re)start Apr 8 17:44:21 yann-laptop rsyslogd: rsyslogd's groupid changed to 103 Apr 8 17:44:21 yann-laptop rsyslogd: rsyslogd's userid changed to 101 Apr 8 17:44:21 yann-laptop rsyslogd-2039: Could no open output file '/dev/= xconsole' [try http://www.rsyslog.com/e/2039 ] Apr 8 17:44:21 yann-laptop kernel: [ 0.000000] Initializing cgroup subs= ys cpuset Apr 8 17:44:21 yann-laptop kernel: [ 0.000000] Initializing cgroup subs= ys cpu Apr 8 17:44:21 yann-laptop kernel: [ 0.000000] Linux version 2.6.32-19-= generic-pae (buildd@palmer) (gcc version 4.4.3 (Ubuntu 4.4.3-4ubuntu5) ) #2= 8-Ubu ntu SMP Wed Mar 31 18:57:46 UTC 2010 (Ubuntu 2.6.32-19.28-generic-pae 2.6.3= 2.10+drm33.1) (...) Apr 8 17:44:23 yann-laptop cron[710]: (CRON) STARTUP (fork ok) Apr 8 17:44:23 yann-laptop anacron[706]: Will run job `cron.daily' in 5 mi= n. Apr 8 17:44:23 yann-laptop anacron[706]: Jobs will be executed sequentially Apr 8 17:44:24 yann-laptop acpid: 39 rules loaded Apr 8 17:44:24 yann-laptop acpid: waiting for events: event logging is off Apr 8 17:44:24 yann-laptop cron[710]: (CRON) INFO (Running @reboot jobs) Apr 8 17:44:25 yann-laptop kernel: [ 30.573175] vboxdrv: Trying to deact= ivate the NMI watchdog permanently... Apr 8 17:44:25 yann-laptop kernel: [ 30.573206] vboxdrv: Successfully do= ne. Apr 8 17:44:25 yann-laptop kernel: [ 30.573209] vboxdrv: Found 2 process= or cores. Apr 8 17:44:25 yann-laptop kernel: [ 30.573558] vboxdrv: fAsync=3D1 offM= in=3D0x63e518 offMax=3D0x63e518 Apr 8 17:44:25 yann-laptop kernel: [ 30.573686] vboxdrv: TSC mode is 'as= ynchronous', kernel timer mode is 'normal'. Apr 8 17:44:25 yann-laptop kernel: [ 30.573689] vboxdrv: Successfully lo= aded version 3.1.4_OSE (interface 0x00100001). Apr 8 17:44:25 yann-laptop kernel: [ 30.651166] vboxguest: exports dupli= cate symbol RTMemExecFree (owned by vboxdrv) Apr 8 15:44:28 yann-laptop ntpdate[792]: step time server 91.189.94.4 offs= et -7197.713072 sec Apr 8 15:44:28 yann-laptop acpid: client connected from 812[0:0] Apr 8 15:44:28 yann-laptop acpid: 1 client rule loaded Apr 8 15:44:28 yann-laptop kernel: [ 31.715398] vboxguest: exports dupli= cate symbol RTMemExecFree (owned by vboxdrv) Apr 8 15:44:31 yann-laptop kernel: [ 34.778781] Linux agpgart interface = v0.103 Apr 8 15:44:32 yann-laptop kernel: [ 34.824938] [drm] Initialized drm 1.= 1.0 20060810 Apr 8 15:44:32 yann-laptop kernel: [ 34.827167] alloc irq_desc for 18 = on node -1 Apr 8 15:44:32 yann-laptop kernel: [ 34.827171] alloc kstat_irqs on no= de -1 Apr 8 15:44:32 yann-laptop kernel: [ 34.827224] pci 0000:00:02.0: PCI IN= T A -> GSI 18 (level, low) -> IRQ 18 Apr 8 15:44:32 yann-laptop kernel: [ 34.827266] pci 0000:00:02.0: settin= g latency timer to 64 Apr 8 15:44:32 yann-laptop kernel: [ 34.827638] [drm] Initialized vboxvi= deo 1.0.0 20090303 for 0000:00:02.0 on minor 0 Apr 8 15:44:34 yann-laptop gdm-session-worker[990]: WARNING: Unable to loa= d file '/etc/gdm/custom.conf': Aucun fichier ou dossier de ce type Apr 8 15:44:34 yann-laptop rtkit-daemon[998]: Sucessfully called chroot. Apr 8 15:44:34 yann-laptop rtkit-daemon[998]: Sucessfully dropped privileg= es. Apr 8 15:44:34 yann-laptop rtkit-daemon[998]: Sucessfully limited resource= s. Apr 8 15:44:34 yann-laptop rtkit-daemon[998]: Running. Apr 8 15:44:34 yann-laptop rtkit-daemon[998]: Watchdog thread running. Apr 8 15:44:34 yann-laptop rtkit-daemon[998]: Canary thread running. Apr 8 15:44:34 yann-laptop kernel: [ 37.685118] eth0: no IPv6 routers pr= esent Apr 8 15:44:35 yann-laptop polkitd[1002]: started daemon version 0.96 usin= g authority implementation `local' version `0.96' Apr 8 15:44:35 yann-laptop rtkit-daemon[998]: Sucessfully made thread 995 = of process 995 (n/a) owned by '114' high priority at nice level -11. Apr 8 15:44:35 yann-laptop rtkit-daemon[998]: Supervising 1 threads of 1 p= rocesses of 1 users. Apr 8 15:44:35 yann-laptop pulseaudio[995]: alsa-util.c: Disabling timer-b= ased scheduling because running inside a VM. **** It seems at least there is a big mess with ntp: we go from 16h15 to 14h15... and reboot at 17h44, but real local time was 15h44, corrected only at reboot (this one was allright). --===============4591571337669137179== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Guy Taylor (thebiggerguy) Date: Thu, 08 Apr 2010 23:04:05 -0000 Message-Id: <20100408230405.15841.20003.malone@wampee.canonical.com> Running under VMware Workstation 6.5.3 build-185404c with VMware tools inst= alled I get the same error. Here is my log Apr 8 22:50:50 Guy-dev tpvmlpd[2038]: device type not supported Apr 8 22:50:50 Guy-dev init: plymouth-stop pre-start process (2115) termin= ated with status 1 Apr 8 22:50:53 Guy-dev kernel: [ 15.648161] eth0: no IPv6 routers present /proc/version: Linux version 2.6.32-19-generic-pae (buildd@palmer) (gcc version 4.4.3 (Ubuntu 4.4.3-4ubuntu5) ) #28-Ubuntu SMP Wed Mar 31 18:57:46 UTC 2010 --===============4591571337669137179== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Mark Cariaga (mzc) Date: Thu, 08 Apr 2010 23:56:15 -0000 Message-Id: <20100408235615.5071.76258.malone@potassium.ubuntu.com> The bug is still present on Beta2! --===============4591571337669137179== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Simon (simon-west-family) Date: Fri, 09 Apr 2010 07:05:46 -0000 Message-Id: <20100409070546.1180.75514.malone@palladium.canonical.com> Acer 5810T was running disk check an d froze at 75%, no disk activity. Reboot brought it back to life. --===============4591571337669137179== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: timuckun (timuckun) Date: Fri, 09 Apr 2010 08:14:35 -0000 Message-Id: <20100409081435.1144.18712.malone@palladium.canonical.com> Asus k42Jr. ATI mobility Radeon 5470 --===============4591571337669137179== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Riccardo Padovani (rpadovani) Date: Fri, 09 Apr 2010 13:56:35 -0000 Message-Id: <20100409135635.1144.6816.malone@palladium.canonical.com> Dell inspirion 6000 , Ati Mobility Radeon X300 --===============4591571337669137179== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: justy55555 (justy55555) Date: Fri, 09 Apr 2010 15:37:25 -0000 Message-Id: <20100409153725.1144.51176.malone@palladium.canonical.com> Acer Aspire One AOD250, Intel GMA 950 --===============4591571337669137179== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Kai Vogel (kai-vogel) Date: Fri, 09 Apr 2010 17:18:03 -0000 Message-Id: <20100409171803.1144.69250.malone@palladium.canonical.com> GeForce 7300 GS with NVidia's "Current" Driver No more crashes afte I've reseted all profiles in "ccsm" and activated the basic profile in "simple-ccsm". Notice: I've also reinstalled virtualbox-ose, but I'm not sure if this causes the crashes... Hope this helps... --===============4591571337669137179== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: HugoHirsch (ubuntubugs-aiki-it) Date: Fri, 09 Apr 2010 21:06:08 -0000 Message-Id: <20100409210608.7543.74867.malone@wampee.canonical.com> +1 Lenovo S10e 00:02.1 Display controller: Intel Corporation Mobile 945GM/GMS/GME, 943/940= GML Express Integrated Graphics Controller (rev 03) --===============4591571337669137179== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Sonsum (scottonsum) Date: Sat, 10 Apr 2010 02:05:02 -0000 Message-Id: <20100410020502.32129.41020.malone@soybean.canonical.com> Samsung N120. Pretty sure its an Intel GMA 950 --===============4591571337669137179== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: cyberb764 (rmills764) Date: Sat, 10 Apr 2010 04:06:09 -0000 Message-Id: <20100410040609.32093.64419.malone@soybean.canonical.com> Doesn't anyone know why ub untuone cannot be manually configured to work? It works fine on my other computer, even after upgrading it. --===============4591571337669137179== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: cyberb764 (rmills764) Date: Sat, 10 Apr 2010 04:07:12 -0000 Message-Id: <20100410040712.1180.48902.malone@palladium.canonical.com> still not able to change a configuration that does'nt exist in the folder it is suppose to be. --===============4591571337669137179== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: cyberb764 (rmills764) Date: Sat, 10 Apr 2010 04:07:44 -0000 Message-Id: <20100410040744.5071.85759.malone@potassium.ubuntu.com> I am alm ost going to give up on it. --===============4591571337669137179== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Adrian Wilkins (adrian-wilkins) Date: Sat, 10 Apr 2010 10:16:51 -0000 Message-Id: <20100410101651.1180.91397.malone@palladium.canonical.com> This occurred for me during a disk check (at 73% if that has any relevance...). --===============4591571337669137179== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: michael barany (michael-barany) Date: Sat, 10 Apr 2010 10:31:16 -0000 Message-Id: <20100410103116.9079.93615.malone@gandwana.canonical.com> Asus EEE 1000, Intel video card; I've had Plymouth hang on disk checks at 70% and 73% (never visibly complete one successfully), and the disk check screen has been the only time I've seen the start-up splash screen for more than a moment (though usually doesn't appear at all). Once everything's booted, though, seems fine. Might also be relevant that the SSD memory in the computer is split into two drives, which I've set respectively to root and /home. --===============4591571337669137179== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Son (son.caokim) Date: Sat, 10 Apr 2010 11:32:09 -0000 Message-Id: <20100410113209.7543.44090.malone@wampee.canonical.com> acer asprire one - AOA110 --===============4591571337669137179== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: xteejx (xteejx) Date: Sat, 10 Apr 2010 12:13:50 -0000 Message-Id: <20100410121350.1144.65008.malone@palladium.canonical.com> cyberb764, this bug report has absolutely nothing to do with Ubuntu One. If you are having problems with it, ask in #ubuntu on irc.freenode.net for support questions, or if it is a bug, file one with ubuntu-bug. --===============4591571337669137179== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Laurie (welcome) Date: Sat, 10 Apr 2010 18:50:36 -0000 Message-Id: <20100410185036.32093.84254.malone@soybean.canonical.com> Problem occurred when sending an e-mail using claws-mail. It did not stop the e-mail being sent or have any obvious harmful effects. --===============4591571337669137179== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Noel Arzola (noel.arzola) Date: Sat, 10 Apr 2010 19:35:59 -0000 Message-Id: <20100410193559.32129.396.malone@soybean.canonical.com> dell dimension 2350 lucid beta 2 this was at random --===============4591571337669137179== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Noel Arzola (noel.arzola) Date: Sat, 10 Apr 2010 19:52:19 -0000 Message-Id: <20100410195219.5071.11481.malone@potassium.ubuntu.com> Occured right on boot just now, after a reboot. Not seeing anything other than it reporting the crash. Desktop and everything appears to load without issue. Crash icon shows up. --===============4591571337669137179== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Polemaker1 (polemaker1) Date: Sat, 10 Apr 2010 22:03:38 -0000 Message-Id: <20100410220338.9079.9311.malone@gandwana.canonical.com> Same problem with an Acer Aspire One AOA150 --===============4591571337669137179== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Martin Karpinski (mkarpinski) Date: Sun, 11 Apr 2010 02:21:07 -0000 Message-Id: <20100411022107.7693.86654.malone@wampee.canonical.com> I had this happen in Lucid beta 2 amd64 (virtualised) when I opened up the language support menu. --===============4591571337669137179== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: hatzigia (hatzigia) Date: Sun, 11 Apr 2010 05:39:01 -0000 Message-Id: <20100411053901.32093.64465.malone@soybean.canonical.com> Same problem trying to install support for greek language after I opened up the language support menu --===============4591571337669137179== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: =?utf-8?q?Andr=C3=A9_Lucas_=28andre=2Elucas=29?= Date: Sun, 11 Apr 2010 12:20:33 -0000 Message-Id: <20100411122033.7624.62255.malone@wampee.canonical.com> Got this on my HP Mini 210. I have a blank screen as the system boots, with a flashing text-mode cursor, and I get the crash report on logging in. --===============4591571337669137179== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: =?utf-8?q?Odin_H=C3=B8rthe_Omdal_=28velmont=29?= Date: Sun, 11 Apr 2010 12:27:08 -0000 Message-Id: <20100411122708.5071.11705.malone@potassium.ubuntu.com> There is just so much crashing with Lucid Lynx :-((((((( I get a crash every 1-2 hours. The intel 845-issue. The boot took LONG time today, so I thought it'd hang and shut it of. Turns out (I think) that it was doing ureadahead-logging or something. After that the display didn't work, so I had to SSH in and run dpkg --configure -a to fix it. (also did dpkg-reconfigure linux-image-generic plymouth ureadahead, and deleted all the ureadahead-files). --===============4591571337669137179== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: axelsvag (darinsson) Date: Sun, 11 Apr 2010 13:54:38 -0000 Message-Id: <20100411135438.1144.26473.malone@palladium.canonical.com> Did not notice anything besides the crashreport --===============4591571337669137179== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: PatrickSCarrroll (patrickscarroll-hotmail) Date: Sun, 11 Apr 2010 17:38:00 -0000 Message-Id: <20100411173800.1180.2008.malone@palladium.canonical.com> Intel 950 graphics, EEE PC 1000h. I see a lot of Intels being mentioned here. Just did an update, rebooted, then eventually got this crash error. System appears to be working fine. Didn't get the splash during bootup. --===============4591571337669137179== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: thecityofgold (simon-haighmail) Date: Mon, 12 Apr 2010 06:20:05 -0000 Message-Id: <20100412062005.1180.44282.malone@palladium.canonical.com> eee900 intel 915 integrated graphics and i have never seen plymouth on boot. using lucid since beta1 with regular updates. usual behaviour is blank screen then normal boot. occasional broken pipes message then normal boot. very occasional hang. even more occasionally it submits this bug report. this particular bug report today was the first boot after a series of updates including kernel. --===============4591571337669137179== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Ralemy (reza.alemy) Date: Mon, 12 Apr 2010 19:10:05 -0000 Message-Id: <20100412191005.7693.62054.malone@wampee.canonical.com> Same here, NVidia Geforce 9300M, Intel HD Audio ICH9 8280II, Lucid Beta 2 Desktop 64bit. --===============4591571337669137179== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Mark Cariaga (mzc) Date: Mon, 12 Apr 2010 19:23:17 -0000 Message-Id: <-7208521697178543707@unknownmsgid> @rex: have you noticed the "could not write bytes: broken pipe" at boot? On Apr 12, 2010, at 12:10 PM, ralemi wrote: > Same here, NVidia Geforce 9300M, Intel HD Audio ICH9 8280II, Lucid > Beta > 2 Desktop 64bit. > > -- > plymouthd crashed with SIGSEGV in > ply_event_loop_process_pending_events() > https://bugs.launchpad.net/bugs/553745 > You received this bug notification because you are a direct subscriber > of a duplicate bug. > > Status in The Plymouth splash screen: New > Status in =E2=80=9Cplymouth=E2=80=9D package in Ubuntu: Confirmed > Status in =E2=80=9Cplymouth=E2=80=9D source package in Lucid: Confirmed > > Bug description: > Binary package hint: plymouth > > just upgraded to lucid, first reboot tried to start accounts > > ProblemType: Crash > DistroRelease: Ubuntu 10.04 > Package: plymouth 0.8.1-4 > ProcVersionSignature: Ubuntu 2.6.32-19.28-generic 2.6.32.10+drm33.1 > Uname: Linux 2.6.32-19-generic i686 > NonfreeKernelModules: wl > Architecture: i386 > Date: Thu Apr 1 22:14:11 2010 > DefaultPlymouth: /lib/plymouth/themes/kubuntu-logo/kubuntu- > logo.plymouth > ExecutablePath: /sbin/plymouthd > MachineType: Dell Inc. Inspiron 1545 > ProcCmdLine: root=3DUUID=3D73530dc8-e3cc-4147-b801-4725b2f88141 ro quiet > splash vga=3D792 > ProcCmdline: /sbin/plymouthd --mode=3Dboot --attach-to-session > ProcEnviron: PATH=3D(custom, no user) > ProcFB: 0 inteldrmfb > SegvAnalysis: > Segfault happened at: 0xfb5fe1 +513>: test %eax,0x4(%esi) > PC (0x00fb5fe1) ok > source "%eax" ok > destination "0x4(%esi)" (0x00000004) not located in a known VMA > region (needed writable region)! > SegvReason: writing NULL VMA > Signal: 11 > SourcePackage: plymouth > StacktraceTop: > ply_event_loop_process_pending_events () > ply_event_loop_run () from /lib/libply.so.2 > ?? () > __libc_start_main () from /lib/tls/i686/cmov/libc.so.6 > ?? () > TextPlymouth: /lib/plymouth/themes/ubuntu-text/ubuntu-text.plymouth > Title: plymouthd crashed with SIGSEGV in > ply_event_loop_process_pending_events() > UserGroups: > > dmi.bios.date: 07/17/2009 > dmi.bios.vendor: Dell Inc. > dmi.bios.version: A10 > dmi.board.name: 0G848F > dmi.board.vendor: Dell Inc. > dmi.chassis.type: 8 > dmi.chassis.vendor: Dell Inc. > dmi.modalias: > dmi:bvnDellInc. > :bvrA10: > bd07/ > 17/ > 2009: > svnDellInc. > :pnInspiron1545:pvr:rvnDellInc.:rn0G848F:rvr:cvnDellInc.:ct8:cvr: > dmi.product.name: Inspiron 1545 > dmi.sys.vendor: Dell Inc. > > To unsubscribe from this bug, go to: > https://bugs.launchpad.net/plymouth/+bug/553745/+subscribe --===============4591571337669137179== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Gav Mack (gavinmac) Date: Mon, 12 Apr 2010 19:36:58 -0000 Message-Id: <20100412193658.9079.1255.malone@gandwana.canonical.com> Same issue with an AAO1 ZG5 with Intel 945 graphics. --===============4591571337669137179== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: bofphile (bofphile) Date: Tue, 13 Apr 2010 00:32:43 -0000 Message-Id: <20100413003243.7693.2237.malone@wampee.canonical.com> Same issue as everyone else on my Thinkpad T500, using the integrated graphic card (Intel 4500MHD). I'm running the latest beta 2 of Lucid with all the updates. --===============4591571337669137179== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: travy4911 (travy4911) Date: Tue, 13 Apr 2010 01:52:11 -0000 Message-Id: <20100413015211.24665.9939.malone@soybean.canonical.com> Acer Aspire One 150. Happened right after reboot. --===============4591571337669137179== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: axion (bugzilla-axion) Date: Tue, 13 Apr 2010 05:13:11 -0000 Message-Id: <20100413051311.1144.12246.malone@palladium.canonical.com> If this is the bug that made my system kill off the X-Server, then go to a black screen and reset the video card, making the display go to sleep mode, I can only say I still had control over the system using ssh. So I safely did a remote shutdown. Before I shutdown I checked all log but could find nothing of significant value. The only thing I do know is that the bug only occurs if I do not throttle the processor down using the userspace CPU Frequency Monitor. For that to work I need to manually add p4_clockmod. I was wondering why this p4_clockmod is not loaded automatically, or added to: /etc/modules. But I think it might be because of the recently removed working conservative and ondemand cpu-gov modules. Btw, since everyone is naming their graphics card here is my (probably useless) lspci info. laptop:~$ lspci 00:00.0 Host bridge: Intel Corporation 82852/82855 GM/GME/PM/GMV Processor = to I/O Controller (rev 02) 00:00.1 System peripheral: Intel Corporation 82852/82855 GM/GME/PM/GMV Proc= essor to I/O Controller (rev 02) 00:00.3 System peripheral: Intel Corporation 82852/82855 GM/GME/PM/GMV Proc= essor to I/O Controller (rev 02) 00:02.0 VGA compatible controller: Intel Corporation 82852/855GM Integrated= Graphics Device (rev 02) 00:02.1 Display controller: Intel Corporation 82852/855GM Integrated Graphi= cs Device (rev 02) 00:1d.0 USB Controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4= -M) USB UHCI Controller #1 (rev 03) 00:1d.1 USB Controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4= -M) USB UHCI Controller #2 (rev 03) 00:1d.2 USB Controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4= -M) USB UHCI Controller #3 (rev 03) 00:1d.7 USB Controller: Intel Corporation 82801DB/DBM (ICH4/ICH4-M) USB2 EH= CI Controller (rev 03) 00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev 83) 00:1f.0 ISA bridge: Intel Corporation 82801DBM (ICH4-M) LPC Interface Bridg= e (rev 03) 00:1f.1 IDE interface: Intel Corporation 82801DBM (ICH4-M) IDE Controller (= rev 03) 00:1f.3 SMBus: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) SMBus= Controller (rev 03) 00:1f.5 Multimedia audio controller: Intel Corporation 82801DB/DBL/DBM (ICH= 4/ICH4-L/ICH4-M) AC'97 Audio Controller (rev 03) 00:1f.6 Modem: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) AC'97= Modem Controller (rev 03) 02:00.0 FireWire (IEEE 1394): VIA Technologies, Inc. VT6306/7/8 [Fire II(M)= ] IEEE 1394 OHCI Controller (rev 80) 02:01.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C= /8139C+ (rev 10) 02:02.0 Ethernet controller: Atheros Communications Inc. Atheros AR5001X+ W= ireless Network Adapter (rev 01) 02:04.0 CardBus bridge: ENE Technology Inc CB1410 Cardbus Controller (rev 0= 1) 03:00.0 Multimedia controller: Philips Semiconductors SAA7131/SAA7133/SAA71= 35 Video Broadcast Decoder (rev f0) laptop:/proc$ cat cpuinfo=20 processor : 0 vendor_id : GenuineIntel cpu family : 15 model : 2 model name : Intel(R) Pentium(R) 4 CPU 2.80GHz stepping : 7 cpu MHz : 1749.956 cache size : 512 KB fdiv_bug : no hlt_bug : no f00f_bug : no coma_bug : no fpu : yes fpu_exception : yes cpuid level : 2 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 mtrr pge mca cmov pat pse36 clf= lush dts acpi mmx fxsr sse sse2 ss ht tm pbe up pebs bts cid xtpr bogomips : 5594.96 clflush size : 64 cache_alignment : 128 address sizes : 36 bits physical, 32 bits virtual power management: --===============4591571337669137179== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: MarkieB (ubunt-u-markbenjamin) Date: Tue, 13 Apr 2010 05:44:13 -0000 Message-Id: <20100413054413.18553.9345.malone@potassium.ubuntu.com> For me it happened after adjusting the grub display resolution to a higher-resolution than the default 640 480 vga setting, in fact it was 1280 1024 32 [found as supported in vbeinfo], set in /etc/default/grub as GRUB_GFX_MODE, GRUB_GFXPAYLOAD_LINUX=3Dkeep; the higher resolution worked as far as the ubuntu splash screen, then at xserver startup it looked as though possibly the 32-bit depth is too funky :-) attached xorg.conf as you see I've set 1 high-res setting, not supported in vbeinfo though --===============4591571337669137179== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Simon (simon-west-family) Date: Tue, 13 Apr 2010 06:17:58 -0000 Message-Id: <20100413061758.7693.4497.malone@wampee.canonical.com> Linux-image 2.6.32-20.30 seems to have fixed this for me this morning. Single reboot after update and back to working kernel. only slight issue was Ubuntu logo on splash screen just before login had ugly green artefacts around it for a few seconds (2 or 3) before clearing to the beautiful new logo. I've seen posts saying "never seen Plymouth splash"... does anyone know what _should_ appear as "splash" after grub text menu? I assumed blank screen immediately after then Ubuntu "I'm starting up - purple and dots" screen is expected sequence. Am I missing anything? My install is a Hoary / Karmic / Lucid upgrade so may have some cruft from it's history --===============4591571337669137179== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: madmax1735 (rebel1735) Date: Tue, 13 Apr 2010 15:42:38 -0000 Message-Id: <20100413154238.18723.19148.malone@palladium.canonical.com> bug still exists in Lucid Lynx beta 2 with kernel 2.6.32-20.30 crash is reported right after the system login but does not seem to affect the system stability. --===============4591571337669137179== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Scott James Remnant (Canonical) (canonical-scott) Date: Wed, 14 Apr 2010 01:16:24 -0000 Message-Id: <20100414011624.12992.41775.malone@soybean.canonical.com> Steve, since you already pulled this patch in the 0.8.2 merge - could you build the package and pop it in a PPA for the reporters to test? --===============4591571337669137179== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Steve Langasek (vorlon) Date: Wed, 14 Apr 2010 08:08:47 -0000 Message-Id: <20100414080847.18127.51463.malone@wampee.canonical.com> Done. Could those experiencing this issue please run 'sudo add-apt- repository ppa:vorlon/ppa' and install the new version of plymouth from there, and let us know if this fixes the problem or causes any new ones? --===============4591571337669137179== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Martin Pitt (pitti) Date: Wed, 14 Apr 2010 11:37:16 -0000 Message-Id: <20100414113716.GC9636@piware.de> Steve Langasek [2010-04-14 8:08 -0000]: > Done. Could those experiencing this issue please run 'sudo add-apt- > repository ppa:vorlon/ppa' and install the new version of plymouth from > there, and let us know if this fixes the problem or causes any new ones? I tested 0.8.2-0ubuntu1~ppa2, and still get exactly the same crash. Please note that I do not press any keys during startup (since the changelog links this bug with a "keyboard handling" fix) I did three boots, and it looked differently each time: 1) No plymouth at all, text mode all the way through X (this was without ureadahead pack, so the boot took a little longer) 2) Text mode most of the time, plymouth splash appears for a second, X. (I think this categorizes as "work fine") 3) Text mode most of the time, then a black screen without the cursor for a second, and then back to text mode (and finally X, with starting into a white screen). This was probably plymouthd starting up, crashing, and writing an apport report. I do not get a crash report every time, I suppose plymouth and apport start around the same time and it's a race. But I still get it very frequently. Thanks, Martin --=20 Martin Pitt | http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org) --===============4591571337669137179== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Tommy Prevatt (tommyprevatt) Date: Wed, 14 Apr 2010 13:58:48 -0000 Message-Id: <20100414135848.23545.65460.malone@potassium.ubuntu.com> This is all I've seen of the mysterious Plymouth: http://j.imagehost.org/0799/Screenshot_5.png --===============4591571337669137179== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Lucas (totus-tuus) Date: Wed, 14 Apr 2010 15:01:21 -0000 Message-Id: <20100414150121.18127.18292.malone@wampee.canonical.com> The system (input, mainly) just freezes out of nowhere, apparently at random with no specific cause. Only keyboard and touchpad stop working, but system itself seems to be normal, some animated stuff (dropbox tray icon, for instance) keeps working. When I press the power button, the Shutdown dialog shows up asking if I want to shut down, suspend, log out, etc, but of course, I can't do anything besides waiting for automatic shutdown. The same problem has also happened on Windows XP (I have dual boot), so it might be a hardware thing. I use a Asus EeePC 1008HA, Intel Atom. The disk check freeze has also occurred a few times, and none has completed in full, stopping around 91%. --===============4591571337669137179== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Cor Driehuis (cor3huis) Date: Wed, 14 Apr 2010 15:12:09 -0000 Message-Id: <20100414151209.24517.59528.malone@gandwana.canonical.com> Just FYI: Happend to me, I'm running the latest 64 bit lucid Beta2 kernel Linux 2.6.32-21-generic #31~raofnvaccel201004131332 SMP Tue Apr 13 13:06:14 UTC 2010 x86_64 GNU/Linux, Nvidia restricted 195.36.15 on Macbook Pro 5,2. --===============4591571337669137179== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: RonzO (ronz0o) Date: Wed, 14 Apr 2010 17:56:26 -0000 Message-Id: <20100414175626.18723.16617.malone@palladium.canonical.com> My lspci output 00:00.0 Host bridge: Intel Corporation 82845G/GL[Brookdale-G]/GE/PE DRAM Co= ntroller/Host-Hub Interface (rev 01) 00:02.0 VGA compatible controller: Intel Corporation 82845G/GL[Brookdale-G]= /GE Chipset Integrated Graphics Device (rev 01) 00:1d.0 USB Controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4= -M) USB UHCI Controller #1 (rev 01) 00:1d.1 USB Controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4= -M) USB UHCI Controller #2 (rev 01) 00:1d.2 USB Controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4= -M) USB UHCI Controller #3 (rev 01) 00:1d.7 USB Controller: Intel Corporation 82801DB/DBM (ICH4/ICH4-M) USB2 EH= CI Controller (rev 01) 00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev 81) 00:1f.0 ISA bridge: Intel Corporation 82801DB/DBL (ICH4/ICH4-L) LPC Interfa= ce Bridge (rev 01) 00:1f.1 IDE interface: Intel Corporation 82801DB (ICH4) IDE Controller (rev= 01) 00:1f.3 SMBus: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) SMBus= Controller (rev 01) 00:1f.5 Multimedia audio controller: Intel Corporation 82801DB/DBL/DBM (ICH= 4/ICH4-L/ICH4-M) AC'97 Audio Controller (rev 01) 01:0c.0 Ethernet controller: Intel Corporation 82540EM Gigabit Ethernet Con= troller (rev 02) It seems to think my desktop is a laptop for some reason. Dell Optiplex GX260 --===============4591571337669137179== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Chris B (billington-chris) Date: Thu, 15 Apr 2010 08:59:56 -0000 Message-Id: <20100415085956.24561.31149.malone@gandwana.canonical.com> Steve Langasek [2010-04-14 8:08 -0000]: > Done. Could those experiencing this issue please run 'sudo add-apt- > repository ppa:vorlon/ppa' and install the new version of plymouth from > there, and let us know if this fixes the problem or causes any new ones? After update to 0.8.2-0ubuntu1~ppa2 the crash report after boot no longer o= ccurs. However, no splash animation is visible during boot- text mode blank screen= , then kms text mode screen with a few console messages, then GDM login scr= een. Animated splash appears only during shutdown/reboot, and during regular dis= k checks, which appear to terminate at 73%. Intel Atom netbook, =20 00:00.0 Host bridge: Intel Corporation Mobile 945GME Express Memory Control= ler Hub (rev 03) 00:02.0 VGA compatible controller: Intel Corporation Mobile 945GME Express = Integrated Graphics Controller (rev 03) 00:02.1 Display controller: Intel Corporation Mobile 945GM/GMS/GME, 943/940= GML Express Integrated Graphics Controller (rev 03) 00:1b.0 Audio device: Intel Corporation N10/ICH 7 Family High Definition Au= dio Controller (rev 02) 00:1c.0 PCI bridge: Intel Corporation N10/ICH 7 Family PCI Express Port 1 (= rev 02) 00:1c.1 PCI bridge: Intel Corporation N10/ICH 7 Family PCI Express Port 2 (= rev 02) 00:1d.0 USB Controller: Intel Corporation N10/ICH7 Family USB UHCI Controll= er #1 (rev 02) 00:1d.1 USB Controller: Intel Corporation N10/ICH 7 Family USB UHCI Control= ler #2 (rev 02) 00:1d.2 USB Controller: Intel Corporation N10/ICH 7 Family USB UHCI Control= ler #3 (rev 02) 00:1d.3 USB Controller: Intel Corporation N10/ICH 7 Family USB UHCI Control= ler #4 (rev 02) 00:1d.7 USB Controller: Intel Corporation N10/ICH 7 Family USB2 EHCI Contro= ller (rev 02) 00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev e2) 00:1f.0 ISA bridge: Intel Corporation 82801GBM (ICH7-M) LPC Interface Bridg= e (rev 02) 00:1f.1 IDE interface: Intel Corporation 82801G (ICH7 Family) IDE Controlle= r (rev 02) 00:1f.2 IDE interface: Intel Corporation 82801GBM/GHM (ICH7 Family) SATA ID= E Controller (rev 02) 00:1f.3 SMBus: Intel Corporation N10/ICH 7 Family SMBus Controller (rev 02) 03:00.0 Network controller: Intel Corporation Wireless WiFi Link 5100 --===============4591571337669137179== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: bornagainpenguin (bornagainpenguin) Date: Thu, 15 Apr 2010 20:04:28 -0000 Message-Id: <20100415200428.18723.26021.malone@palladium.canonical.com> Wheee! THIS bug again. It's starting to look as if I'm going to have no choice but to revert to either Hardy or find myself a new distro if this is how broken Beta 2 of Lucid is at this late date. Notice I say Hardy and not Karmic, because there is something in Karmic making my eeepc run hot all the time. What is it the guy from array.org was able to do that the Cannonical developers seem incapable of figuring out? And before anyone trots out that tired "esoteric and non-standard hardware" excuse, please consider the rapid growth of the netbook category in the past year or two and try to realize this excuse no longer flies, no matter how much trust you shove into it. --bornagainpenguin --===============4591571337669137179== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Sepero (cowpie2000) Date: Thu, 15 Apr 2010 22:05:57 -0000 Message-Id: <20100415220557.32082.49662.malone@soybean.canonical.com> HP Compaq Presario CQ60-215DX Lucid Lynx 10.04 --===============4591571337669137179== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: W. Scott Lockwood III (wsl3) Date: Thu, 15 Apr 2010 22:11:27 -0000 Message-Id: <20100415221127.24517.60283.malone@gandwana.canonical.com> Xorg.0.log for analysis --===============4591571337669137179== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Steve Langasek (vorlon) Date: Thu, 15 Apr 2010 22:31:55 -0000 Message-Id: <20100415223155.18723.92731.malone@palladium.canonical.com> This has nothing to do with X, and is not hardware-dependent. Please don't send us X logfiles or follow up to tell us your hardware. --===============4591571337669137179== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Qays Poonawala (qayshp) Date: Fri, 16 Apr 2010 01:50:38 -0000 Message-Id: <20100416015038.30443.45251.malone@gandwana.canonical.com> at boot in UNR 10.04 beta2 --===============4591571337669137179== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Tolsimir Wolf (tolsimirwolf) Date: Fri, 16 Apr 2010 16:53:10 -0000 Message-Id: <20100416165310.32126.28313.malone@soybean.canonical.com> I ran the command given to add the new plymouth to my repository but I have= n't installed it. I'm a bit afraid to do so after reading other peoples exp= eriences with it. It doesn't really cause any problems, only that I get the crash report ever= y so often. I can then just tell it to close and continue on with my life -= no problem. I'd just kind of like to see the problem fixed even as minuscu= le as it seems now. Here's what I get when I run lspci 00:00.0 Host bridge: Intel Corporation Mobile 915GM/PM/GMS/910GML Express P= rocessor to DRAM Controller (rev 03) 00:02.0 VGA compatible controller: Intel Corporation Mobile 915GM/GMS/910GM= L Express Graphics Controller (rev 03) 00:02.1 Display controller: Intel Corporation Mobile 915GM/GMS/910GML Expre= ss Graphics Controller (rev 03) 00:1d.0 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Famil= y) USB UHCI #1 (rev 03) 00:1d.1 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Famil= y) USB UHCI #2 (rev 03) 00:1d.2 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Famil= y) USB UHCI #3 (rev 03) 00:1d.3 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Famil= y) USB UHCI #4 (rev 03) 00:1d.7 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Famil= y) USB2 EHCI Controller (rev 03) 00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev d3) 00:1e.2 Multimedia audio controller: Intel Corporation 82801FB/FBM/FR/FW/FR= W (ICH6 Family) AC'97 Audio Controller (rev 03) 00:1e.3 Modem: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) AC'97 = Modem Controller (rev 03) 00:1f.0 ISA bridge: Intel Corporation 82801FBM (ICH6M) LPC Interface Bridge= (rev 03) 00:1f.1 IDE interface: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family= ) IDE Controller (rev 03) 00:1f.3 SMBus: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) SMBus = Controller (rev 03) 02:01.0 CardBus bridge: Texas Instruments PCI1510 PC card Cardbus Controller 02:03.0 Network controller: Broadcom Corporation BCM4318 [AirForce One 54g]= 802.11g Wireless LAN Controller (rev 02) 02:08.0 Ethernet controller: Intel Corporation 82562ET/EZ/GT/GZ - PRO/100 V= E (LOM) Ethernet Controller Mobile (rev 03) Hope that adding these specs to the list could help with coming up with a more sure solution. --===============4591571337669137179== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Jordan Bradley (jordan-w-bradley) Date: Fri, 16 Apr 2010 18:53:08 -0000 Message-Id: <20100416185308.23509.12545.malone@potassium.ubuntu.com> This is the first time Plymouth crashed for me. Something else has been crashing during boot up. --===============4591571337669137179== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Gonzalo Bulnes Guilpain (gonzalo-bulnes) Date: Fri, 16 Apr 2010 21:26:31 -0000 Message-Id: <20100416212631.32170.57028.malone@soybean.canonical.com> Hi people, this bug affects me on a MSI PR210 with an ATI video controller: $ lspci | grep VGA 01:05.0 VGA compatible controller: ATI Technologies Inc RS690M [Radeon X120= 0 Series] It doesn't occur every time I boot, but when it occurs it is just after the boot. Regards --===============4591571337669137179== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Dexter (dexter-greycells) Date: Sat, 17 Apr 2010 02:39:45 -0000 Message-Id: <20100417023945.24517.22544.malone@gandwana.canonical.com> Affects me on my Sony Vaio, Intel 945 Integrated graphics. The error just comes up all of a sudden... --===============4591571337669137179== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: burlingk (burlingk) Date: Sun, 18 Apr 2010 09:05:20 -0000 Message-Id: <20100418090520.24517.5627.malone@gandwana.canonical.com> I got this on a Toshiba Satalite with ATI graphics and AMD64, and it was not the first reboot after an upgrade. --===============4591571337669137179== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: jpedros2@xtec.cat (jpedros2-xtec) Date: Sun, 18 Apr 2010 10:35:32 -0000 Message-Id: <20100418103532.32082.84286.malone@soybean.canonical.com> Affects me on a HP Pavilion dev6000, AMD 64, graphics with: nvidia 8400 --===============4591571337669137179== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Alice (pisufnita) Date: Sun, 18 Apr 2010 23:40:34 -0000 Message-Id: <20100418234034.17662.81940.malone@wampee.canonical.com> nec computers Intel P4 2.40, 2gb ram, VGA compatible controller: Intel Corporation 82865G Integrated Graphics Controller Fresh install lucid beta 2 (from usb thumb). Errors at each boot. This error came in the first restart after installing non free video codecs (universe). No other ppa but the official. Seems nobody reported it after installing codecs... --===============4591571337669137179== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Alice (pisufnita) Date: Sun, 18 Apr 2010 23:47:53 -0000 Message-Id: <20100418234753.17662.51996.malone@wampee.canonical.com> ok. wasn't net computers. this board is asrock p4i65gv.=20 I restart and error still there. Plus my screensaver is having a huge lag. = Before saying the system is old, let you know this wasn't happening in Karm= ic. --===============4591571337669137179== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Alan Lord (theopensourcerer) Date: Mon, 19 Apr 2010 13:00:13 -0000 Message-Id: <20100419130013.18020.11558.malone@wampee.canonical.com> Fresh install of the daily Lucid build (today 19/04/2010). Intel Atom 330 Mobo # lspci 00:00.0 Host bridge: Intel Corporation 82945G/GZ/P/PL Memory Controller Hub= (rev 02) 00:02.0 VGA compatible controller: Intel Corporation 82945G/GZ Integrated G= raphics Controller (rev 02) 00:1b.0 Audio device: Intel Corporation N10/ICH 7 Family High Definition Au= dio Controller (rev 01) 00:1c.0 PCI bridge: Intel Corporation N10/ICH 7 Family PCI Express Port 1 (= rev 01) 00:1c.1 PCI bridge: Intel Corporation N10/ICH 7 Family PCI Express Port 2 (= rev 01) 00:1d.0 USB Controller: Intel Corporation N10/ICH7 Family USB UHCI Controll= er #1 (rev 01) 00:1d.1 USB Controller: Intel Corporation N10/ICH 7 Family USB UHCI Control= ler #2 (rev 01) 00:1d.2 USB Controller: Intel Corporation N10/ICH 7 Family USB UHCI Control= ler #3 (rev 01) 00:1d.3 USB Controller: Intel Corporation N10/ICH 7 Family USB UHCI Control= ler #4 (rev 01) 00:1d.7 USB Controller: Intel Corporation N10/ICH 7 Family USB2 EHCI Contro= ller (rev 01) 00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev e1) 00:1f.0 ISA bridge: Intel Corporation 82801GB/GR (ICH7 Family) LPC Interfac= e Bridge (rev 01) 00:1f.1 IDE interface: Intel Corporation 82801G (ICH7 Family) IDE Controlle= r (rev 01) 00:1f.2 IDE interface: Intel Corporation N10/ICH7 Family SATA IDE Controlle= r (rev 01) 00:1f.3 SMBus: Intel Corporation N10/ICH 7 Family SMBus Controller (rev 01) 02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8101E/RTL81= 02E PCI Express Fast Ethernet controller (rev 01) Have experienced complete lock-ups (no mouse, no ALT+CTL+Fn) not sure if related to this or not. --===============4591571337669137179== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Colin Watson (cjwatson) Date: Mon, 26 Apr 2010 16:53:06 -0000 Message-Id: <20100426165308.17248.27423.malone@soybean.canonical.com> Pushing to lucid-updates per Steve, although of course we still want to try to fix this ASAP. --===============4591571337669137179== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Tero Mononen (tmo-iki) Date: Mon, 03 May 2010 10:25:27 -0000 Message-Id: <20100503102527.20610.27495.malone@soybean.canonical.com> Folks, I'm back on this old issue again. FSCK with progress indicator (-C switch) produces a very large number of progress messages, which all are read, and forwarded to plymouth on function fsck_reader(), file mountall.c. Plymouthd can't keep up with hundreds of thousands, perhaps millions, of messages, especially if it needs to display them. Please limit the number of messages sent (for example check whether last progress percentage was the same as the one to be sent). [this is actually for #559761] Also there is something hairy in the libply/ply-event-loop.c, as indicated on the attached stack traces. Function ply_event_loop_handle_timeouts() tried dereference a null pointer 'watch'. Possible workaround is to check whether 'watch' is NULL, and in that case simply remove it from the list. Additionally, I propose removal of the O(N^2) behaviour causing assertion from the end of function ply_list_unlink_node(), file ply- list.c. BR -- tmo --===============4591571337669137179== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Tero Mononen (tmo-iki) Date: Mon, 03 May 2010 11:20:28 -0000 Message-Id: <20100503112029.19525.31916.malone@wampee.canonical.com> Attached patches containing workarounds / proposed fixes for mountall.c an= d libply. These fix the issue for me, at least. BR -- Tmo --===============4591571337669137179== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Martin Erik Werner (arand) Date: Tue, 04 May 2010 02:34:38 -0000 Message-Id: <20100504023439.19763.61255.malone@potassium.ubuntu.com> Above patch fixes Bug #571707 for me. --===============4591571337669137179== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Martin Erik Werner (arand) Date: Tue, 04 May 2010 13:32:22 -0000 Message-Id: <20100504133223.18035.39740.malone@gandwana.canonical.com> I have applied Tero Mononen's patch and uploaded corresponding packages to my "unstable" PPA: https://edge.launchpad.net/~arand/+archive/unstable for ease of testing (i386 seems to take a while to build, amd64 done already). Two bugs with high prio and a lot of affects, I'd claim this fix to be of some importance, the sooner the SRU process starts the better, methinks... --===============4591571337669137179== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: =?utf-8?b?SHJvdGvDsyBHw6Fib3IgKHJvdGktYWwp?= Date: Wed, 05 May 2010 18:53:37 -0000 Message-Id: <20100505185337.21203.67604.malone@wampee.canonical.com> @Tero Mononen thank you! you satisfied my wife :-) --===============4591571337669137179== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Tero Mononen (tmo-iki) Date: Wed, 05 May 2010 20:36:30 -0000 Message-Id: <20100505203630.21146.87468.malone@wampee.canonical.com> Arand, Thank's for taking care of the patch. I'm amazed that there are so few reports on this issue, as *everyone* updating or installing 10.04 will be affected by the issue when fsck is eventually run ... once a month with journalling FS. My guess is, that unless released soon, the number of affected users will rocket up. Luckily folks are pretty lazy on reporting issues :( BR. -- Tmo --===============4591571337669137179== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Martin Erik Werner (arand) Date: Thu, 06 May 2010 22:02:42 -0000 Message-Id: <20100506220242.22668.15300.malone@potassium.ubuntu.com> Fyi, this just posted on the other Bug #571707 concerning the patch, by Kees Cook: "The intent of the mountall patch is correct -- no reason to flood plymouth with updates, however, the "lastprogress" tracking needs to be attached to the mount structure, rather than the callback, since the callback can be used for multiple mounts." ref. https://bugs.edge.launchpad.net/ubuntu/+source/mountall/+bug/571707/comment= s/74 ...Times like these one wish that there was some way to link bugs without marking them as dupes --===============4591571337669137179== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Martin Erik Werner (arand) Date: Sun, 16 May 2010 14:03:18 -0000 Message-Id: <20100516140318.15331.38775.malone@potassium.ubuntu.com> Is this issue addressed with the latest mountall 2.15 in lucid, or does the plymouth part of the patch also play into this bug? --===============4591571337669137179== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Gilles (gilles-civario) Date: Mon, 17 May 2010 05:09:52 -0000 Message-Id: <20100517050952.31359.53044.malone@wampee.canonical.com> Hi, I used to have apport popping out almost once every two boots of my laptop= , leading me to this very bug report. Since I installed the mountall patch corresponding to bug 571707, it has ne= ver appended again. FMPOV, the present bug is fixed. Thanks for the great job. Gilles --===============4591571337669137179== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Anders Kaseorg (andersk) Date: Mon, 17 May 2010 08:22:45 -0000 Message-Id: <20100517082245.31307.42184.malone@wampee.canonical.com> The plymouth patches should still be applied (hopefully upstream); they=E2=80=99re all good changes. Whether they should be applied as a Luci= d SRU is up to the SRU team. It=E2=80=99s possible that the reduction in events = from mountall has made this bug unlikely enough that an SRU is no longer as critical; I=E2=80=99m not sure. (I never saw the crash myself, I can just = see that the bug is real from looking at the code.) If you are still seeing this crash after upgrading to mountall 2.15, please let us know. --===============4591571337669137179== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Gilles (gilles-civario) Date: Fri, 21 May 2010 05:00:35 -0000 Message-Id: <20100521050035.32211.10821.malone@wampee.canonical.com> Hi, Finally, for the first time since I installed the patch for bug 571707, ply= mouthd crashed. For the record, I have to remind that: 1/ before installing that patch, plymouthd used to crash about once every = two boot of my laptop 2/ I boot my laptop at least once a day, some time up to 5 times per day (= due to bug 510803 preventing me from suspending it to ram) 3/ to be able to collect useful informations about previous bug, I had ena= bled apport long time ago, and never disabled it since then. In the present= case, that is only because apport pops-up that I know that plymouthd crash= ed. From the very first time this bug showed-up, it has never been for me a= real pain. I don't know how critical it is but the only symptom it has dis= played for me has been (excepted apport of course) about 10s more to boot t= han usual Anyway, in any case, I would happily test your plymouthd patch if I could h= ave the slightest idea on how to do so. I can even uninstall the patch for = bug 571707 beforehand to increase the interest of the test if you see it us= eful (and if you tell ma how to do so). Cheers. Gilles --===============4591571337669137179== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Martin Erik Werner (arand) Date: Sat, 22 May 2010 03:22:50 -0000 Message-Id: <20100522032250.31626.76809.malone@gandwana.canonical.com> @Gilles: The plymouth patch by Tero is still available from my "Unstable" PPA I have no idea if downgrading the mountall package and running only on the = plymouth patch would be of any use, but I can tell you how to do it: 1. add my ppa https://edge.launchpad.net/~arand/+archive/unstable 2. Run an upgrade which should (in normal casees) pull in [libplymouth2 ply= mouth plymouth-label plymouth-theme-ubuntu-logo plymouth-theme-ubuntu-text = plymouth-x11] all of version [0.8.2-2ubuntu3~ppa1] (Maybe) 3. Downgrade mountall to 2.14 temporarily: [sudo aptitude install mountall= =3D2.14] (if you have enabled proposed, the update will automatically be su= ggested again) --===============4591571337669137179== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Gilles (gilles-civario) Date: Mon, 24 May 2010 08:31:01 -0000 Message-Id: <20100524083101.7423.56262.malone@gandwana.canonical.com> Architecture: i386 DefaultPlymouth: /lib/plymouth/themes/ubuntu-logo/ubuntu-logo.plymouth DistroRelease: Ubuntu 10.04 InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5) MachineType: eMachines eMachines E510 Package: plymouth 0.8.2-2ubuntu3~ppa1 PackageArchitecture: i386 ProcCmdLine: BOOT_IMAGE=3D/boot/vmlinuz-2.6.32-22-generic root=3DUUID=3D29b= f3f7c-0d46-4d91-96ad-111f143c4911 ro quiet splash ProcEnviron: PATH=3D(custom, no user) LANG=3Den_IE.utf8 SHELL=3D/bin/bash ProcFB: 0 inteldrmfb ProcVersionSignature: Ubuntu 2.6.32-22.33-generic 2.6.32.11+drm33.2 Tags: lucid lucid TextPlymouth: /lib/plymouth/themes/ubuntu-text/ubuntu-text.plymouth Uname: Linux 2.6.32-22-generic i686 UnreportableReason: This is not a genuine Ubuntu package UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare dmi.bios.date: 11/10/2008 dmi.bios.vendor: EMACHINES dmi.bios.version: V1.45 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Rhine dmi.board.vendor: EMACHINES dmi.board.version: V1.45 dmi.chassis.type: 1 dmi.chassis.vendor: EMACHINES dmi.chassis.version: V1.45 dmi.modalias: dmi:bvnEMACHINES:bvrV1.45:bd11/10/2008:svneMachines:pneMachin= esE510:pvrV1.45:rvnEMACHINES:rnRhine:rvrV1.45:cvnEMACHINES:ct1:cvrV1.45: dmi.product.name: eMachines E510 dmi.product.version: V1.45 dmi.sys.vendor: eMachines --===============4591571337669137179== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Gilles (gilles-civario) Date: Mon, 24 May 2010 08:31:09 -0000 Message-Id: <20100524083109.26872.43876.malone@soybean.canonical.com> apport information --===============4591571337669137179== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Gilles (gilles-civario) Date: Mon, 24 May 2010 08:31:13 -0000 Message-Id: <20100524083114.26872.40627.malone@soybean.canonical.com> apport information --===============4591571337669137179== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Gilles (gilles-civario) Date: Mon, 24 May 2010 08:31:17 -0000 Message-Id: <20100524083117.12551.78630.malone@potassium.ubuntu.com> apport information --===============4591571337669137179== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Gilles (gilles-civario) Date: Mon, 24 May 2010 08:31:20 -0000 Message-Id: <20100524083120.12551.37270.malone@potassium.ubuntu.com> apport information --===============4591571337669137179== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Gilles (gilles-civario) Date: Mon, 24 May 2010 08:31:25 -0000 Message-Id: <20100524083125.12551.14989.malone@potassium.ubuntu.com> apport information --===============4591571337669137179== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Gilles (gilles-civario) Date: Mon, 24 May 2010 08:31:31 -0000 Message-Id: <20100524083131.12551.51426.malone@potassium.ubuntu.com> apport information --===============4591571337669137179== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Gilles (gilles-civario) Date: Mon, 24 May 2010 08:31:35 -0000 Message-Id: <20100524083135.26872.43672.malone@soybean.canonical.com> apport information --===============4591571337669137179== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Gilles (gilles-civario) Date: Mon, 24 May 2010 08:31:37 -0000 Message-Id: <20100524083137.12551.22665.malone@potassium.ubuntu.com> apport information --===============4591571337669137179== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Gilles (gilles-civario) Date: Mon, 24 May 2010 08:31:42 -0000 Message-Id: <20100524083142.7423.28744.malone@gandwana.canonical.com> apport information --===============4591571337669137179== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Gilles (gilles-civario) Date: Mon, 24 May 2010 08:31:46 -0000 Message-Id: <20100524083146.26872.61977.malone@soybean.canonical.com> apport information --===============4591571337669137179== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Gilles (gilles-civario) Date: Mon, 24 May 2010 08:51:11 -0000 Message-Id: <20100524085111.32211.39489.malone@wampee.canonical.com> Hello, As you can guess fro the apport-collect above, I made a few tests over the = week-end, that have not all been successful... Here are a few details: 1/ I've downgraded mountall from 2.15 to 2.14 for experimenting if I was b= ack in my plymouth crass-prone environment: and first reboot that didn't im= plied a looong fsck (the one that fastfoward until 70% of the disk, and the= n takes ages to finish) generated a plymouthd SEGV. 2/ then I installed arand's ppa plymouthd packages as described in above c= omment #87 : after something like 10 reboots, id didn't experiment any prob= lem 3/ then I reinstalled mountall 2.15 and I rebooted =3D> fine. I though let= 's reboot one last time before reporting that everything is fine and that t= he patch fixed everything.... Bad idea! 4/ I rebooted (2nd time after mountall 2.15 reinstall) and then the hell b= egan: during the booting phase, I usually have for 2 to 3 second a blinking= cursor of large VGA type, that disappear and is replaced by a small graphi= c-like one, and then I've got X11 starting and the login screen. This time,= instead of this, 3 lines appeared on the large non-graphic console, then t= he graphic one started with the small cursor locate line 4 instead of line = one as usual, then the screen went black and the laptop freezed. The only way I managed to get it back was trough the On/Off button. I tried 3 more times to resart it, and 3 times it freezed the same, but wit= hout the 3 lines in non-graphic console this time. Finally, in the 4th attempt, I did a failsafe reboot and managed to get it = back. I then reboot once more normally, and it worked. That's the time I did the apport-collect action. I'm not sure to know where the culprit is but first of all I will remove the testing plymouthd packages.... Is there anything I can do more to be of help? Gilles --===============4591571337669137179== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Gilles (gilles-civario) Date: Thu, 27 May 2010 08:09:05 -0000 Message-Id: <20100527080905.15345.51555.malone@gandwana.canonical.com> Hi, does the above comment: Changed in plymouth (Ubuntu): status: Triaged =E2=86=92 Fix Committed=20 means that the proposed patch located in https://edge.launchpad.net/~arand/= +archive/unstable has been committed to the sources? If so, this is very bad news as using it totally crashed my machine, to the= point I feared not being able to recover it without using the liveCD... Ho= nestly, the non patched version crashed all the same, but at least it does = it transparently for the user (for me at least). Now, I may have missed something, but I don't think so. Gilles --===============4591571337669137179== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Draycen DeCator (ddecator) Date: Thu, 27 May 2010 13:49:16 -0000 Message-Id: <20100527134917.14256.90967.malone@gandwana.canonical.com> Please do not change the Status of a bug without providing a reason for doing so. Thanks! --===============4591571337669137179== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: JoseLuisTriana (theunfor) Date: Wed, 02 Jun 2010 16:18:41 -0000 Message-Id: <20100602161841.14807.79583.malone@wampee.canonical.com> I was trying to run "Star Wars Episode I The phantom Menace" with the patch in wine without virtual desktop when this crash happened, I have an NVidia GeForce 7200 GS, my CPU is an Intel Celeron with 1995 Mhz of Frequency, the version of Wine in which I was running the game is 1.1.42. --===============4591571337669137179== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Tux Rev (tuxrev) Date: Sun, 13 Jun 2010 16:04:00 -0000 Message-Id: <20100613160400.5676.34006.malone@wampee.canonical.com> It occurred as I logged in. I'm not sure what impact this has on my system. Intel Pentium Dual-Core Processor 2G RAM Ubuntu 10.04 Gnome 2.30.0 Kernel Linux 2.6.32-22-generic --===============4591571337669137179== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Neil Perry (nperry) Date: Tue, 15 Jun 2010 02:52:00 -0000 Message-Id: <20100914053756.757.15152.launchpad@loganberry.canonical.com> Created an attachment (id=3D36279) patch Inital bug report https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/553745 just upgraded to lucid, first reboot tried to start accounts ProblemType: Crash DistroRelease: Ubuntu 10.04 Package: plymouth 0.8.1-4 ProcVersionSignature: Ubuntu 2.6.32-19.28-generic 2.6.32.10+drm33.1 Uname: Linux 2.6.32-19-generic i686 NonfreeKernelModules: wl Architecture: i386 Date: Thu Apr 1 22:14:11 2010 DefaultPlymouth: /lib/plymouth/themes/kubuntu-logo/kubuntu-logo.plymouth ExecutablePath: /sbin/plymouthd MachineType: Dell Inc. Inspiron 1545 ProcCmdLine: root=3DUUID=3D73530dc8-e3cc-4147-b801-4725b2f88141 ro quiet sp= lash vga=3D792 ProcCmdline: /sbin/plymouthd --mode=3Dboot --attach-to-session ProcEnviron: PATH=3D(custom, no user) ProcFB: 0 inteldrmfb SegvAnalysis: Segfault happened at: 0xfb5fe1 = : test %eax,0x4(%esi) PC (0x00fb5fe1) ok source "%eax" ok destination "0x4(%esi)" (0x00000004) not located in a known VMA region (ne= eded writable region)! SegvReason: writing NULL VMA Signal: 11 SourcePackage: plymouth StacktraceTop: ply_event_loop_process_pending_events () ply_event_loop_run () from /lib/libply.so.2 ?? () __libc_start_main () from /lib/tls/i686/cmov/libc.so.6 ?? () TextPlymouth: /lib/plymouth/themes/ubuntu-text/ubuntu-text.plymouth Title: plymouthd crashed with SIGSEGV in ply_event_loop_process_pending_eve= nts() UserGroups: dmi.bios.date: 07/17/2009 dmi.bios.vendor: Dell Inc. dmi.bios.version: A10 dmi.board.name: 0G848F dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA10:bd07/17/2009:svnDellInc.:pnInspiron154= 5:pvr:rvnDellInc.:rn0G848F:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Inspiron 1545 dmi.sys.vendor: Dell Inc. StacktraceTop: ply_event_loop_process_pending_events ( ply_event_loop_run (loop=3D0x90280a8) at ply-event-loop.c:1312 main (argc=3D3, argv=3D0xbfeba124) at main.c:1916 --===============4591571337669137179== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Ray Strode (halfline) Date: Tue, 15 Jun 2010 07:31:26 -0000 Message-Id: <20100914053756.757.14904.launchpad@loganberry.canonical.com> Review of attachment 36279: ::: mountall-2.14/src/mountall.c @@ +2742,2 @@ nih_assert_not_reached (); } This stuff seems to be unrelated to plymouth ::: plymouth-0.8.2/src/libply/ply-event-loop.c @@ +1193,3 @@ =20 + if (watch =3D=3D NULL) + { This shouldn't even happen. If this is happening there must be a bug some where else in the code. @@ +1248,3 @@ + number_of_received_events =3D epoll_wait (loop->epoll_fd, + events, PLY_EVENT_LOOP_NUM_EVENT_HANDLERS, + timeout); Ah, this is a nice catch! Hard to believe this bug went unnoticed for so long. Unfortunately, it just means plymouth was processing less events per iteration than its configured upper limit (8 instead of 64). I don't think this is related to your crash. I've committed this part though: http://cgit.freedesktop.org/plymouth/commit/?id=3D26bc6f87c0507d0b457b23548= 094c475e00e75c9 ::: plymouth-0.8.2/src/libply/ply-list.c @@ +225,2 @@ list->number_of_nodes--; + // assert (ply_list_find_node (list, node->data) !=3D node); again, if this is failing there is a bug somewhere else in the code. --===============4591571337669137179== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Neil Perry (nperry) Date: Tue, 15 Jun 2010 09:54:26 -0000 Message-Id: <20100615095426.12976.15858.malone@soybean.canonical.com> Patch applied fine for me, forwarded upstream. Work on behalf of Ubuntu Reviews. --===============4591571337669137179== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: dORSY (dorsyka) Date: Sat, 24 Jul 2010 21:34:07 -0000 Message-Id: <20100724213407.6500.78056.malone@wampee.canonical.com> Still afffecting me. And it is random. 00:06.0 IDE interface: nVidia Corporation MCP78S [GeForce 8200] IDE (rev a1) 00:07.0 Audio device: nVidia Corporation MCP72XE/MCP72P/MCP78U/MCP78S High = Definition Audio (rev a1) 00:08.0 PCI bridge: nVidia Corporation MCP78S [GeForce 8200] PCI Bridge (re= v a1) ... 02:00.0 VGA compatible controller: nVidia Corporation G92 [GeForce 8800 GT]= (rev a2) Linux amd64 2.6.35-10-generic #15-Ubuntu SMP Thu Jul 22 11:10:38 UTC 2010 x= 86_64 GNU/Linux I found nothing relevant in logs, just this: Jul 24 23:19:35 amd64 init: plymouth main process (385) killed by SEGV signal --===============4591571337669137179== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: richard (richard-e-morton) Date: Tue, 27 Jul 2010 18:41:30 -0000 Message-Id: <20100727184130.27224.28466.malone@wampee.canonical.com> Also affects Maverick Alpha 2 --===============4591571337669137179== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Christopher Patrick (cpatrick08) Date: Wed, 04 Aug 2010 12:37:31 -0000 Message-Id: <20100804123731.19526.36488.malone@soybean.canonical.com> also affects maverick alpha 3 --===============4591571337669137179== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Saul (creative-balm) Date: Wed, 11 Aug 2010 15:41:18 -0000 Message-Id: <20100811154118.22698.36649.malone@palladium.canonical.com> Has happened twice while removing nvidia driver in failsafex - using Maverick 3 after recent X11 update. However nvidia driver is safely removed and reboot gives working desktop. --===============4591571337669137179== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Tom Pringle (thomas-b-pringle) Date: Tue, 17 Aug 2010 09:27:58 -0000 Message-Id: <20100817092758.12955.54275.malone@wampee.canonical.com> just saw this on 'apt-get upgraded' Maverick running on Thinkpad Edge (AMD cpu/gpu) --===============4591571337669137179== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Nicolas DERIVE (kalon33) Date: Mon, 30 Aug 2010 22:19:29 -0000 Message-Id: <20100830221929.30879.34020.malone@soybean.canonical.com> @lool: why for maverick-updates when maverick is not yet released (more than 1 month remaining) ? --===============4591571337669137179== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: bartdx (bart-bdx) Date: Tue, 31 Aug 2010 05:19:33 -0000 Message-Id: <20100831051934.11153.16670.malone@soybean.canonical.com> have not seen this problem for some time, now on august 31 2010 it popped up again, after i downloaded and installed newest kernel on Maverick 10.10 --===============4591571337669137179== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: =?utf-8?q?Lo=C3=AFc_Minier_=28lool=29?= Date: Tue, 31 Aug 2010 11:02:43 -0000 Message-Id: <20100831110243.32222.14660.malone@soybean.canonical.com> maverick-updates was a mistake of mine; not sure how I picked that one, I wanted to fix the lucid-updates milestone; thanks for the heads up --===============4591571337669137179== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Blaster (holst-niels) Date: Fri, 03 Sep 2010 11:17:32 -0000 Message-Id: <20100903111732.20364.41397.malone@potassium.ubuntu.com> @ #111: I'm in the same situation. --===============4591571337669137179== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: PatrickSCarrroll (patrickscarroll-hotmail) Date: Mon, 06 Sep 2010 11:52:21 -0000 Message-Id: <20100906115221.7265.33817.malone@wampee.canonical.com> Is this one of those bugs that goes on for years, un-addressed? --===============4591571337669137179== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: PatrickSCarrroll (patrickscarroll-hotmail) Date: Mon, 06 Sep 2010 11:53:00 -0000 Message-Id: <20100906115300.31210.27689.malone@soybean.canonical.com> Also, I'm NOT using Nvidia. --===============4591571337669137179== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Scott James Remnant (Canonical) (canonical-scott) Date: Mon, 13 Sep 2010 16:21:05 -0000 Message-Id: <20100913162106.8815.44840.malone@potassium.ubuntu.com> While I appreciate that it's always frustrating to be affected by a bug that seems like it's going "un-addressed for years", I'm not aware of any new information on this bug? Previous attempts at fixing it haven't helped or have made things worse - and without a new line of investigation, we're pretty stumped on what causes it or how to fix it. --===============4591571337669137179== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Kenny Strawn (realkstrawn93) Date: Wed, 15 Sep 2010 14:36:42 -0000 Message-Id: <20100915143644.30816.45757.malone@palladium.canonical.com> I also experienced this bug on an Acer Aspire One AOA110-1545, but it too didn't affect system stability, just the splash screen. --===============4591571337669137179== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: ec (ecroes) Date: Sun, 19 Sep 2010 01:38:34 -0000 Message-Id: <20100919013834.27205.68477.malone@wampee.canonical.com> LinuxUbuntu maverick (development branch) \n \l 2.6.35-22-generic #32-Ubuntu SMP Wed Sep 15 23:18:18 UTC 2010 x86_64 GNU/Li= nux compaq 6910p notebook Plymouth: Ge=C3=AFnstalleerd: 0.8.2-2ubuntu4 Kandidaat: 0.8.2-2ubuntu4 Versietabel: *** 0.8.2-2ubuntu4 0 500 http://nl.archive.ubuntu.com/ubuntu/ maverick/main amd64 Packag= es 100 /var/lib/dpkg/status the crash happened right after coming out hibernation mode --===============4591571337669137179== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: maik stolle (ms090780) Date: Sat, 25 Sep 2010 13:31:17 -0000 Message-Id: <20100925133117.31065.53265.malone@gandwana.canonical.com> the crash happened right after coming out sleep mode, and start updating my= system. ubuntu maverik 10.10 x64 2.6.35-22-generic regards maik --===============4591571337669137179== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Andrew Cartine (cartine) Date: Tue, 28 Sep 2010 00:55:05 -0000 Message-Id: <20100928005505.724.94629.malone@soybean.canonical.com> my laptop battery died, so i guess it went into hibernate(?). i hit the power button and it booted back into it's pre-hibernation state. i did an apt-get update and upgrade, rebooted when it was finished. upon logging in, nothing seemed wrong, but i got the "crash" icon on the upper right panel, complaining about Plymouth and leading me here. Maverick 10.10 beta Asus K52J laptop Intel(R) Core(TM) i5 CPU M 430 @ 2.27GHz ATI HD5470 Linux 2.6.35-22-generic #33-Ubuntu SMP Sun Sep 19 20:32:27 UTC 2010 x86_64= GNU/Linux Package: plymouth =20 State: installed Automatically installed: no Version: 0.8.2-2ubuntu5 I also thought this might be interesting: p libplymouth-dev - graphical boot animation and logger -= deve i libplymouth2 - graphical boot animation and logger -= shar p lubuntu-plymouth-theme - plymouth theme for Lubuntu = =20 i plymouth - graphical boot animation and logger -= main i A plymouth-label - graphical boot animation and logger -= labe v plymouth-theme - = =20 p plymouth-theme-fade-in - graphical boot animation and logger -= fade p plymouth-theme-glow - graphical boot animation and logger -= glow p plymouth-theme-kubuntu-logo - graphical boot animation and logger -= kubu p plymouth-theme-kubuntu-text - graphical boot animation and logger -= kubu p plymouth-theme-lubuntu-logo - plymouth theme for Lubuntu = =20 p plymouth-theme-sabily - plymouth theme for Sabily = =20 p plymouth-theme-script - graphical boot animation and logger -= scri p plymouth-theme-solar - graphical boot animation and logger -= sola p plymouth-theme-spinfinity - graphical boot animation and logger -= spin p plymouth-theme-text - graphical boot animation and logger -= text i A plymouth-theme-ubuntu-logo - graphical boot animation and logger -= ubun i A plymouth-theme-ubuntu-text - graphical boot animation and logger -= ubun p plymouth-theme-ubuntustudio - Ubuntu Studio Plymouth theme = =20 c plymouth-theme-xubuntu-logo - graphical boot animation and logger -= xubu i plymouth-x11 - graphical boot animation and logger -= X11=20 p xubuntu-plymouth-theme - Plymouth theme for Xubuntu =20 notice the configs for xubuntu are still there. dunno if that would cause a problem or not. please let me know any other information i could provide that would be helpful. --===============4591571337669137179== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: tamalet (tamalet) Date: Tue, 28 Sep 2010 11:45:50 -0000 Message-Id: <20100928114550.30986.62817.malone@gandwana.canonical.com> I also started seeing an apport crash leading to this bug after today's update of Maverick. $lspci Intel Corporation Mobile 945GM/PM/GMS, 943/940GML and 945GT Express Memory = Controller Hub (rev 03) --===============4591571337669137179== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Illogic_Gate (illogicgate) Date: Fri, 01 Oct 2010 20:44:38 -0000 Message-Id: <20101001204438.19399.23648.malone@soybean.canonical.com> Yeah, same problem here, it popped up after rebooting from a kernel panic caused by another problem. IBM Thinkpad T42 (model 2373) with the M7 Radeon 7500 Mobility. --===============4591571337669137179== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: gerstrong (gerstrong) Date: Sun, 03 Oct 2010 08:14:09 -0000 Message-Id: <20101003081409.2161.1663.malone@wampee.canonical.com> Ubuntu 10.10 RC. System does not freeze or anything but it reports that error --===============4591571337669137179== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Bruce Pieterse (octoquad) Date: Wed, 15 Dec 2010 15:30:26 -0000 Message-Id: <20101215153026.5740.41560.malone@soybean.canonical.com> I'm not sure if I can reproduce this error, but I did the following that caused it to crash: - Logged in - Launched HeidiSQL (WINE) - I had no network connection, so I clicked on network manager (16:49:26) a= nd selected my default connection while HeidiSQL was loading. - Application crashed after being connected to the network See attachment for a copy of my syslog. Interesting items are at 16:47:37, 16:47:39, 16:48:19-16:48:24, 16:49:28. --===============4591571337669137179== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Jorge Marcano (jorgitomarcano) Date: Fri, 04 Mar 2011 11:23:31 -0000 Message-Id: <20110304112333.1823.22550.malone@palladium.canonical.com> It occurred as I logged in --===============4591571337669137179== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Mark Cariaga (mzc) Date: Sun, 20 Mar 2011 06:02:21 -0000 Message-Id: <20110320060221.24025.13718.malone@wampee.canonical.com> crashed after plugging a camera via usb --===============4591571337669137179== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Launchpad Janitor (janitor) Date: Thu, 24 Mar 2011 14:20:12 -0000 Message-Id: <20110324142035.21360.7532.malone@cocoplum.canonical.com> This bug was fixed in the package plymouth - 0.8.2-2ubuntu20 --------------- plymouth (0.8.2-2ubuntu20) natty; urgency=3Dlow * Backport from upstream: - [event-loop] Add reference count to event sources (with any luck, this will fix LP: #553745). - [event-loop] Handle more than 8 events at once (LP: #518926). - [terminal] Force enter to output newline. - [terminal] Add OPOST to tty attributes (LP: #546251). - [terminal] Don't set ISTRIP in terminal attributes. -- Colin Watson Thu, 24 Mar 2011 14:17:20 +0000 --===============4591571337669137179== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Greg A (etulfetulf) Date: Mon, 04 Apr 2011 19:36:36 -0000 Message-Id: <20110404193637.15956.78169.malone@soybean.canonical.com> I just got redirected to this bug (by Apport) despite having 0.8.2-2ubuntu21 installed. --===============4591571337669137179== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Colin Watson (cjwatson) Date: Tue, 05 Apr 2011 08:42:16 -0000 Message-Id: <20110405084216.GD9163@riva.ucam.org> On Mon, Apr 04, 2011 at 07:36:36PM -0000, Greg Auger wrote: > I just got redirected to this bug (by Apport) despite having > 0.8.2-2ubuntu21 installed. Could you file a new bug using Apport and post the bug number, please? I want to analyse the stack trace separately, even if Apport thinks that it looks like this one. (This is the kind of bug that I expect could be caused in a few different ways; it wouldn't surprise me if I'd plugged some of the holes but missed others.) --===============4591571337669137179== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: =?utf-8?b?0KHQvNC40YDQvdC+0LIg0JDQu9C10LrRgdCw0L3QtNGAINCS0LDQu9C10YDQuNGP0L3QvtCy0LjRhyAoc21pcm5vdjA5YWwp?= Date: Tue, 05 Apr 2011 12:46:01 -0000 Message-Id: Really the first message of the bug was generated automatically. If you explained exactly what to do I would like to help you. 2011/4/5 Colin Watson > On Mon, Apr 04, 2011 at 07:36:36PM -0000, Greg Auger wrote: > > I just got redirected to this bug (by Apport) despite having > > 0.8.2-2ubuntu21 installed. > > Could you file a new bug using Apport and post the bug number, please? > I want to analyse the stack trace separately, even if Apport thinks that > it looks like this one. > > (This is the kind of bug that I expect could be caused in a few > different ways; it wouldn't surprise me if I'd plugged some of the holes > but missed others.) > > -- > You received this bug notification because you are a direct subscriber > of a duplicate bug (739255). > https://bugs.launchpad.net/bugs/553745 > > Title: > plymouthd crashed with SIGSEGV in > ply_event_loop_process_pending_events() > > Status in The Plymouth splash screen: > Confirmed > Status in =E2=80=9Cplymouth=E2=80=9D package in Ubuntu: > Fix Released > Status in =E2=80=9Cplymouth=E2=80=9D source package in Lucid: > Triaged > Status in =E2=80=9Cplymouth=E2=80=9D source package in Maverick: > Triaged > Status in =E2=80=9Cplymouth=E2=80=9D source package in Natty: > Fix Released > > Bug description: > Binary package hint: plymouth > > just upgraded to lucid, first reboot tried to start accounts > > ProblemType: Crash > DistroRelease: Ubuntu 10.04 > Package: plymouth 0.8.1-4 > ProcVersionSignature: Ubuntu 2.6.32-19.28-generic 2.6.32.10+drm33.1 > Uname: Linux 2.6.32-19-generic i686 > NonfreeKernelModules: wl > Architecture: i386 > Date: Thu Apr 1 22:14:11 2010 > DefaultPlymouth: /lib/plymouth/themes/kubuntu-logo/kubuntu-logo.plymouth > ExecutablePath: /sbin/plymouthd > MachineType: Dell Inc. Inspiron 1545 > ProcCmdLine: root=3DUUID=3D73530dc8-e3cc-4147-b801-4725b2f88141 ro quiet > splash vga=3D792 > ProcCmdline: /sbin/plymouthd --mode=3Dboot --attach-to-session > ProcEnviron: PATH=3D(custom, no user) > ProcFB: 0 inteldrmfb > SegvAnalysis: > Segfault happened at: 0xfb5fe1 > : test %eax,0x4(%esi) > PC (0x00fb5fe1) ok > source "%eax" ok > destination "0x4(%esi)" (0x00000004) not located in a known VMA region > (needed writable region)! > SegvReason: writing NULL VMA > Signal: 11 > SourcePackage: plymouth > StacktraceTop: > ply_event_loop_process_pending_events () > ply_event_loop_run () from /lib/libply.so.2 > ?? () > __libc_start_main () from /lib/tls/i686/cmov/libc.so.6 > ?? () > TextPlymouth: /lib/plymouth/themes/ubuntu-text/ubuntu-text.plymouth > Title: plymouthd crashed with SIGSEGV in > ply_event_loop_process_pending_events() > UserGroups: > > dmi.bios.date: 07/17/2009 > dmi.bios.vendor: Dell Inc. > dmi.bios.version: A10 > dmi.board.name: 0G848F > dmi.board.vendor: Dell Inc. > dmi.chassis.type: 8 > dmi.chassis.vendor: Dell Inc. > dmi.modalias: > dmi:bvnDellInc.:bvrA10:bd07/17/2009:svnDellInc.:pnInspiron1545:pvr:rvnDel= lInc.:rn0G848F:rvr:cvnDellInc.:ct8:cvr: > dmi.product.name: Inspiron 1545 > dmi.sys.vendor: Dell Inc. > > To unsubscribe from this bug, go to: > https://bugs.launchpad.net/plymouth/+bug/553745/+subscribe > --===============4591571337669137179== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Rick Flynn (flynn1959) Date: Tue, 05 Apr 2011 14:07:04 -0000 Message-Id: Hi, Were I only skilled enough to do so!! I'm OK at reporting problems, but not much beyond that. Is there another way I could help? Thanks, Rick :-) On Tue, Apr 5, 2011 at 4:42 AM, Colin Watson wrote: > On Mon, Apr 04, 2011 at 07:36:36PM -0000, Greg Auger wrote: > > I just got redirected to this bug (by Apport) despite having > > 0.8.2-2ubuntu21 installed. > > Could you file a new bug using Apport and post the bug number, please? > I want to analyse the stack trace separately, even if Apport thinks that > it looks like this one. > > (This is the kind of bug that I expect could be caused in a few > different ways; it wouldn't surprise me if I'd plugged some of the holes > but missed others.) > > -- > You received this bug notification because you are a direct subscriber > of a duplicate bug (710974). > https://bugs.launchpad.net/bugs/553745 > > Title: > plymouthd crashed with SIGSEGV in > ply_event_loop_process_pending_events() > > Status in The Plymouth splash screen: > Confirmed > Status in =E2=80=9Cplymouth=E2=80=9D package in Ubuntu: > Fix Released > Status in =E2=80=9Cplymouth=E2=80=9D source package in Lucid: > Triaged > Status in =E2=80=9Cplymouth=E2=80=9D source package in Maverick: > Triaged > Status in =E2=80=9Cplymouth=E2=80=9D source package in Natty: > Fix Released > > Bug description: > Binary package hint: plymouth > > just upgraded to lucid, first reboot tried to start accounts > > ProblemType: Crash > DistroRelease: Ubuntu 10.04 > Package: plymouth 0.8.1-4 > ProcVersionSignature: Ubuntu 2.6.32-19.28-generic 2.6.32.10+drm33.1 > Uname: Linux 2.6.32-19-generic i686 > NonfreeKernelModules: wl > Architecture: i386 > Date: Thu Apr 1 22:14:11 2010 > DefaultPlymouth: /lib/plymouth/themes/kubuntu-logo/kubuntu-logo.plymouth > ExecutablePath: /sbin/plymouthd > MachineType: Dell Inc. Inspiron 1545 > ProcCmdLine: root=3DUUID=3D73530dc8-e3cc-4147-b801-4725b2f88141 ro quiet > splash vga=3D792 > ProcCmdline: /sbin/plymouthd --mode=3Dboot --attach-to-session > ProcEnviron: PATH=3D(custom, no user) > ProcFB: 0 inteldrmfb > SegvAnalysis: > Segfault happened at: 0xfb5fe1 > : test %eax,0x4(%esi) > PC (0x00fb5fe1) ok > source "%eax" ok > destination "0x4(%esi)" (0x00000004) not located in a known VMA region > (needed writable region)! > SegvReason: writing NULL VMA > Signal: 11 > SourcePackage: plymouth > StacktraceTop: > ply_event_loop_process_pending_events () > ply_event_loop_run () from /lib/libply.so.2 > ?? () > __libc_start_main () from /lib/tls/i686/cmov/libc.so.6 > ?? () > TextPlymouth: /lib/plymouth/themes/ubuntu-text/ubuntu-text.plymouth > Title: plymouthd crashed with SIGSEGV in > ply_event_loop_process_pending_events() > UserGroups: > > dmi.bios.date: 07/17/2009 > dmi.bios.vendor: Dell Inc. > dmi.bios.version: A10 > dmi.board.name: 0G848F > dmi.board.vendor: Dell Inc. > dmi.chassis.type: 8 > dmi.chassis.vendor: Dell Inc. > dmi.modalias: > dmi:bvnDellInc.:bvrA10:bd07/17/2009:svnDellInc.:pnInspiron1545:pvr:rvnDel= lInc.:rn0G848F:rvr:cvnDellInc.:ct8:cvr: > dmi.product.name: Inspiron 1545 > dmi.sys.vendor: Dell Inc. > > To unsubscribe from this bug, go to: > https://bugs.launchpad.net/plymouth/+bug/553745/+subscribe > --===============4591571337669137179== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: David Racine (bass-dr) Date: Mon, 18 Apr 2011 15:24:43 -0000 Message-Id: <20110418152443.22732.73392.malone@wampee.canonical.com> Problem occured here on 0.8.2ubuntu22 (Ubuntu 11.04 beta). --===============4591571337669137179== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Observer (dbvweb) Date: Mon, 18 Apr 2011 21:13:49 -0000 Message-Id: <20110418211349.5267.85417.malone@chaenomeles.canonical.com> Bug occurs for me in a fresh install of natty (beta1) in an Asus 1015B (AMD= Brazos platform, c-50 + AMD 6250HD-CPU). It also occurs for me in an upgrade install of natty (beta1) in a Packard B= ell (Intel Celeron M, ATI Xpress 200m). --===============4591571337669137179== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Carlo Marcelo Arenas Belon (carenas) Date: Tue, 19 Apr 2011 18:21:47 -0000 Message-Id: <20110419182147.4272.68865.malone@chaenomeles.canonical.com> similar failures with versions of plymouth after the one this bug refers as released are being tracked by BUG752215 --===============4591571337669137179== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Sebastian (sebastianhaselbeck) Date: Sat, 23 Apr 2011 15:35:31 -0000 Message-Id: <20110423153531.29165.82568.malone@wampee.canonical.com> fix released? I am still getting this --===============4591571337669137179== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Colin Watson (cjwatson) Date: Sat, 23 Apr 2011 16:14:07 -0000 Message-Id: <20110423161407.GI9163@riva.ucam.org> Probably best to file a new bug if you're still seeing this - I suspect there were several possible causes, and repeatedly reopening/reclosing a single bug isn't a very good way to untangle that kind of thing. --===============4591571337669137179== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Paul Crawford (psc-sat) Date: Tue, 28 Jun 2011 08:09:57 -0000 Message-Id: <20110628080957.27178.69621.malone@chaenomeles.canonical.com> "Probably best to file a new bug if you're still seeing this" Yes, I am still seeing this but how do I file a new bug report? On detecting the crash apport simply directs me to this page where I am told it has been fixed! Obviously not! --===============4591571337669137179== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Paul Crawford (psc-sat) Date: Tue, 28 Jun 2011 08:13:31 -0000 Message-Id: <20110628081331.28870.9154.malone@gac.canonical.com> Just to add I am on 10.04 LTS with the 'proposed' updates. I assume that you will be fixing the LTS release? --===============4591571337669137179== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: =?utf-8?q?J=C4=81nis_Kangarooo_=28kangarooo=29?= Date: Tue, 28 Jun 2011 13:56:29 -0000 Message-Id: <20110628135629.20233.62836.malone@soybean.canonical.com> This made VLC not opening. 10.04.2 LTS and 2 days ago latests updates. Right now theres no new updates. Laptop eMachines e525 1. Startet downloading video 2. While download in middle opened unfinished file in VLC 3. VLC didnt open and this bug came. 4. reporting told that this is my bug so here im comenting that i had this = with VLC. 5. 2nd time opening- VLC opened and im watching unfinished file --===============4591571337669137179== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: =?utf-8?q?J=C4=81nis_Kangarooo_=28kangarooo=29?= Date: Thu, 30 Jun 2011 17:43:58 -0000 Message-Id: <20110630174359.23958.29995.malone@wampee.canonical.com> I thing im also now after update i did 5 days ago im getting this all the time on start. On clean 10.04.2 i didnt got this --===============4591571337669137179== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: =?utf-8?q?J=C4=81nis_Kangarooo_=28kangarooo=29?= Date: Sat, 02 Jul 2011 13:55:30 -0000 Message-Id: <20110702135530.25242.10494.malone@gac.canonical.com> I tryd now also hibernation and this bug doesnt come up. So it comes only on new start. --===============4591571337669137179== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: =?utf-8?b?VHVvbWFzIEzDpGh0ZWVubcOka2kgKGxhaHRpcyk=?= Date: Sun, 03 Jul 2011 08:57:16 -0000 Message-Id: <20110703085716.24082.1354.malone@wampee.canonical.com> This seemed to happen a start. --===============4591571337669137179== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: =?utf-8?q?J=C4=81nis_Kangarooo_=28kangarooo=29?= Date: Thu, 28 Jul 2011 21:19:07 -0000 Message-Id: <20110728211907.12632.28736.malone@chaenomeles.canonical.com> i updated yesterday and now started and didnt get error --===============4591571337669137179== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: =?utf-8?q?J=C4=81nis_Kangarooo_=28kangarooo=29?= Date: Sun, 31 Jul 2011 18:14:50 -0000 Message-Id: <20110731181450.10626.58913.malone@wampee.canonical.com> hmm on next start i did get it again. so once i didnt get this error as in previous comment i wrote --===============4591571337669137179== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Jason Warner (jasoncwarner) Date: Sat, 10 Sep 2011 08:31:16 -0000 Message-Id: <20110910083116.6929.64049.malone@gac.canonical.com> I got this in Oneiric. However, have not been able to reproduce. Log is attached. --===============4591571337669137179== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Jason Warner (jasoncwarner) Date: Sat, 10 Sep 2011 08:32:47 -0000 Message-Id: <20110910083247.7333.79084.malone@gac.canonical.com> This time with log... --===============4591571337669137179== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Jared (jared-vanvolkenburg) Date: Sun, 11 Sep 2011 00:58:31 -0000 Message-Id: <20110911005831.3412.29260.malone@wampee.canonical.com> I received this error on Oneiric 11.10 beta 1 after rebooting. I logged in, and received a message saying that there was a system problem, but with no error message. I selected to report it, and a few seconds later the plymouthd crash error came up which I selected to report as well. I had upgraded from 11.04 to 11.10 beta 1. --===============4591571337669137179== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: dino99 (9d9) Date: Tue, 13 Sep 2011 07:49:57 -0000 Message-Id: <20110913074957.32608.11933.malone@soybean.canonical.com> Had an Oneiric i386 b1 crash at cold boot time, and apport (wrongly) redirect to this bug report, even if it had never been opened for Oneiric and been fixed for Natty and plymouthd(ubuntu) !!! and apport- collect is not more clever sadly: it propose (force) to use ubuntu-bug, which redirect here ( hey Apport devs team, you still have some works to do ) --===============4591571337669137179== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: dino99 (9d9) Date: Tue, 13 Sep 2011 07:53:03 -0000 Message-Id: <20110913075303.21042.37.malone@wampee.canonical.com> ApportVersion: 1.22.1-0ubuntu2 Architecture: i386 DefaultPlymouth: /lib/plymouth/themes/ubuntu-logo/ubuntu-logo.plymouth DistroRelease: Ubuntu 11.10 MachineType: ASUSTEK COMPUTER INC P5W DH Deluxe NonfreeKernelModules: nvidia Package: plymouth 0.8.2-2ubuntu25 PackageArchitecture: i386 ProcCmdLine: BOOT_IMAGE=3D/boot/vmlinuz-3.0.0-11-generic-pae root=3DUUID=3D= 9e61e83e-bca9-43cf-aa90-5a68892213fa ro vga=3D791 splash quiet crashkernel= =3D384M-2G:64M,2G-:128M acpi_osi=3DLinux ProcEnviron: PATH=3D(custom, no user) LANG=3Dfr_FR.UTF-8 SHELL=3D/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=3D/boot/vmlinuz-3.0.0-11-generic-pae root=3DU= UID=3D9e61e83e-bca9-43cf-aa90-5a68892213fa ro vga=3D791 splash quiet crashk= ernel=3D384M-2G:64M,2G-:128M acpi_osi=3DLinux ProcVersionSignature: Ubuntu 3.0.0-11.17-generic-pae 3.0.4 Tags: oneiric oneiric TextPlymouth: /lib/plymouth/themes/ubuntu-text/ubuntu-text.plymouth Uname: Linux 3.0.0-11-generic-pae i686 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm admin audio avahi avahi-autoipd boinc cdrom couchdb crontab= daemon debian-tor dialout disk fuse haldaemon klog kmem libuuid lpadmin ma= il messagebus mlocate mysql mythtv netdev ntp operator plugdev polkituser p= ulse root sambashare saned shadow ssh ssl-cert sudo syslog tty users utmp v= ideo voice www-data dmi.bios.date: 10/22/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3001 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5W DH Deluxe dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3001:bd10/22/2009:svnASUSTEK= COMPUTERINC:pnP5WDHDeluxe:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5WDHDe= luxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: P5W DH Deluxe dmi.product.version: System Version dmi.sys.vendor: ASUSTEK COMPUTER INC --===============4591571337669137179== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: dino99 (9d9) Date: Tue, 13 Sep 2011 07:53:08 -0000 Message-Id: <20110913075309.4814.1127.malone@chaenomeles.canonical.com> apport information --===============4591571337669137179== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: dino99 (9d9) Date: Tue, 13 Sep 2011 07:53:13 -0000 Message-Id: <20110913075313.7074.26495.malone@gac.canonical.com> apport information --===============4591571337669137179== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: dino99 (9d9) Date: Tue, 13 Sep 2011 07:53:17 -0000 Message-Id: <20110913075317.31374.29656.malone@soybean.canonical.com> apport information --===============4591571337669137179== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: dino99 (9d9) Date: Tue, 13 Sep 2011 07:53:22 -0000 Message-Id: <20110913075322.5224.44693.malone@chaenomeles.canonical.com> apport information --===============4591571337669137179== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: dino99 (9d9) Date: Tue, 13 Sep 2011 07:53:27 -0000 Message-Id: <20110913075327.7074.3454.malone@gac.canonical.com> apport information --===============4591571337669137179== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: dino99 (9d9) Date: Tue, 13 Sep 2011 07:53:31 -0000 Message-Id: <20110913075331.20936.12357.malone@wampee.canonical.com> apport information --===============4591571337669137179== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: dino99 (9d9) Date: Tue, 13 Sep 2011 07:53:36 -0000 Message-Id: <20110913075336.31077.25129.malone@soybean.canonical.com> apport information --===============4591571337669137179== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: dino99 (9d9) Date: Tue, 13 Sep 2011 07:53:42 -0000 Message-Id: <20110913075342.21967.89310.malone@wampee.canonical.com> apport information --===============4591571337669137179== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: dino99 (9d9) Date: Tue, 13 Sep 2011 07:53:47 -0000 Message-Id: <20110913075347.21246.48956.malone@wampee.canonical.com> apport information --===============4591571337669137179== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: dino99 (9d9) Date: Tue, 13 Sep 2011 07:53:52 -0000 Message-Id: <20110913075352.6052.80730.malone@gac.canonical.com> apport information --===============4591571337669137179== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: dino99 (9d9) Date: Tue, 13 Sep 2011 07:53:56 -0000 Message-Id: <20110913075356.6158.66459.malone@chaenomeles.canonical.com> apport information --===============4591571337669137179== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: dino99 (9d9) Date: Tue, 20 Sep 2011 12:04:53 -0000 Message-Id: <20110920120453.22433.61768.malone@soybean.canonical.com> seems to be fixed now on Oneiric i386 b1, does not get that crash since a few days now --===============4591571337669137179== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Brian Murray (brian-murray) Date: Tue, 20 Sep 2011 16:43:00 -0000 Message-Id: <20110920164302.21628.28331.malone@soybean.canonical.com> Recent versions of this crash are still appearing in bug 849414 and its duplicates. --===============4591571337669137179== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Steve Langasek (vorlon) Date: Tue, 20 Sep 2011 22:47:13 -0000 Message-Id: <20110920224715.29633.95073.malone@wampee.canonical.com> These crash reports are caused by a bug in plymouth, the boot-time splash screen. Sometimes the errors are not reported for quite a while after the crash actually happens. If someone here is able to reproduce this bug reliably, please do the follo= wing: - edit /etc/default/grub so that GRUB_CMDLINE_LINUX_DEFAULT is set to "qui= et splash plymouth:debug" - run sudo update-grub - reboot, and when you receive the prompt asking whether to report a crash= about plymouthd, say "yes" - attach /var/log/plymouth-debug.log to the new bug report --===============4591571337669137179== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Bruce Pieterse (octoquad) Date: Wed, 21 Sep 2011 20:52:01 -0000 Message-Id: <20110921205202.12117.5.malone@gac.canonical.com> --===============4591571337669137179== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Bruce Pieterse (octoquad) Date: Wed, 21 Sep 2011 20:53:11 -0000 Message-Id: <20110921205311.12954.32739.malone@gac.canonical.com> Steve, I did not get the error message again, however after enabling debugging for plymouth I noticed a few files missing like x11.so on line 100, double slashes in path names and plymouthd.conf not existing. See attached file. --===============4591571337669137179== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Steve Langasek (vorlon) Date: Wed, 21 Sep 2011 21:45:06 -0000 Message-Id: <20110921214506.GB15472@virgil.dodds.net> Hi Bruce, On Wed, Sep 21, 2011 at 08:53:11PM -0000, Bruce Pieterse wrote: > I did not get the error message again, however after enabling debugging > for plymouth I noticed a few files missing like x11.so on line 100, > double slashes in path names and plymouthd.conf not existing. These are all expected behavior and not related to this bug. I need a plymouth debug log that corresponds to an actual crash in order to make progress here. --=20 Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developer http://www.debian.org/ slangasek@ubuntu.com vorlon@debian.org --===============4591571337669137179== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Bruce Pieterse (octoquad) Date: Wed, 21 Sep 2011 21:55:33 -0000 Message-Id: <20110921215533.12335.90521.malone@gac.canonical.com> Ok, Well, I'll leave plymouth debugging on just in case the error does crop up again. I'm currently using 11.10 Beta 1. --===============4591571337669137179== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Jared (jared-vanvolkenburg) Date: Fri, 23 Sep 2011 13:26:12 -0000 Message-Id: <20110923132612.27477.25873.malone@soybean.canonical.com> I just received this crash after a reboot. I am using 11.10 beta 2 about 30 seconds after logging into unity. --===============4591571337669137179== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Jared (jared-vanvolkenburg) Date: Fri, 23 Sep 2011 13:28:38 -0000 Message-Id: <20110923132838.9607.84929.malone@gac.canonical.com> Sorry for the mis-edit of my comment should read: I just received this crash after a reboot about 30 seconds after logging in= to unity. I am using 11.10 beta 2 . I have not had coffee yet this morning. --===============4591571337669137179== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Adam-cowan (adam-cowan) Date: Tue, 04 Oct 2011 18:02:03 -0000 Message-Id: <20111004180203.26780.63536.malone@chaenomeles.canonical.com> This bug is also affecting me on 11.10 beta 2 with all the current updates. --===============4591571337669137179== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Steve Langasek (vorlon) Date: Tue, 04 Oct 2011 18:42:37 -0000 Message-Id: <20111004184237.28969.79613.malone@soybean.canonical.com> This bug (and other similar crasher bugs like it) is known to affect a large number of users, but inconveniently the developers are not able to reproduce the bug - which means we can't fix it. If this crash happens consistently for you, please add the option 'plymouth:debug=3Dfile:/var/log/plymouth-debug.log' to your boot settings, and the next time you see this crash, please report it as a new bug with apport and attach the /var/log/plymouth-debug.log file to the report. --===============4591571337669137179== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: James Hunt (jamesodhunt) Date: Wed, 12 Oct 2011 15:26:56 -0000 Message-Id: <20111012152657.29800.93214.malone@soybean.canonical.com> If anyone is getting this issue, please help us by obtaining the plymouth debug log. Note that most updates on this issue are now being added to bug 849414. --===============4591571337669137179== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: =?utf-8?q?J=C4=81nis_Kangarooo_=28kangarooo=29?= Date: Tue, 15 Nov 2011 01:49:56 -0000 Message-Id: <20111115014957.2688.80118.malone@gac.canonical.com> Heres with splash plymouth:debug and without crash. cant get crash anymore with this line added but got this= file. --===============4591571337669137179== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: iGadget (igadget) Date: Thu, 01 Mar 2012 19:23:49 -0000 Message-Id: <20120301192349.20106.37540.malone@chaenomeles.canonical.com> Just got this after booting a freshly installed and updated 12.04 alpha 2. Amazing it seems to be present for so many releases but still remains unfixed. If it happens again I'll dive deeper into all the comments above. --===============4591571337669137179== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: =?utf-8?q?J=C4=81nis_Kangarooo_=28kangarooo=29?= Date: Tue, 06 Mar 2012 04:43:59 -0000 Message-Id: <20120306044359.2328.61189.malone@chaenomeles.canonical.com> Where actually is the problem? Its that this problem comes up. Nothing crashes actually but it just comes = up. Make this bug disable to show up: 1.) Add this bug ignorance 2.) Remove plymouth --===============4591571337669137179== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Ewano (i-launchpad-ewano-net) Date: Tue, 13 Mar 2012 02:17:28 -0000 Message-Id: <20120313021729.22417.60015.malone@gac.canonical.com> FWIW: HP ze2000 laptop: Fresh install of 12.04 beta using the mini.iso - non PAE. Installed fine, then installed LXDE. Upon login to LXDE I get this error. I can gather logs and sys info if required. --===============4591571337669137179== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: jerrylamos (jerrylamos) Date: Tue, 13 Mar 2012 19:24:06 -0000 Message-Id: <20120313192406.22621.8364.malone@gac.canonical.com> Booted up, idle, and this crash occurred. Jerry --===============4591571337669137179== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Ernesto Celis (celisdelafuente) Date: Mon, 26 Mar 2012 22:20:15 -0000 Message-Id: <20120326222015.19824.33933.malone@wampee.canonical.com> Same problem as others, after fresh boot and loging into my user account, the crash dialog pops up. HP Pavillion dv4 64bit Ubuntu 12.04 amd64 beta up to date March 25 2012. I can give you any other information that can help to solve this, its not a big issue but anoying. --===============4591571337669137179== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Martin Wildam (mwildam) Date: Tue, 27 Mar 2012 07:30:46 -0000 Message-Id: Through different versions of Ubuntu I see SIGSEGV related errors coming and going. And I have the impression, they always start if I begin to install different desktop environments on the same machine to make every user choose his prefered one. Mostly I see them on my testing machines where I install basically all available Desktop environments. Not sure if that idea helps. --=20 Martin Wildam http://martin.wildam.org/ --===============4591571337669137179== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: James Hunt (jamesodhunt) Date: Fri, 30 Mar 2012 16:17:41 -0000 Message-Id: <20120330161741.27754.46062.malone@gac.canonical.com> At long last, I can now recreate this problem at will. Although I haven't debugged the actual cause yet (and hence don't yet have a fix), it is triggered when the following occur "very close together": plymouth show-splash plymouth quit Note that the problem can occur on boot (where plymouthd is run with '-- mode=3Dboot') and shutdown (where plymouthd is run with '-- mode=3Dshutdown'). For those interested, to recreate the problem: # in 1 window... $ sudo apt-get install plymouth-x11 $ ./test_plymouth.sh -s /sbin/plymouthd # in another window $ ./force_crash.sh After a few seconds, a crash will occur. test_plymouth.sh and force_crash.sh are available here: http://people.canonical.com/~jhunt/plymouth/ What I can see currently is that objects are being corrupted and a repeating pattern appears to be timeout/pending calls. Further investigation is required, but atleast once we have a fix available, we now have a way to test it. --===============4591571337669137179== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: James Hunt (jamesodhunt) Date: Fri, 30 Mar 2012 16:27:47 -0000 Message-Id: <20120330162747.26714.91335.malone@gac.canonical.com> One other point to note - this problem only seems to occur if using the "script" splash plugin (which Ubuntu uses). --===============4591571337669137179== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: devtry (devtry) Date: Fri, 06 Apr 2012 16:18:28 -0000 Message-Id: <20120406161828.2027.82563.malone@chaenomeles.canonical.com> I'm using an up to date Ubuntu 12.04. Ubuntu automatically raised a bug report with the same title ("plymouthd crashed with SIGSEGV in ply_event_loop_process_pending_events()") while I was going to print a pdf file to pdf. Hope this helps! --===============4591571337669137179== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Francesco Muriana (f-muriana) Date: Thu, 12 Apr 2012 07:19:03 -0000 Message-Id: <20120412071903.8504.79110.malone@chaenomeles.canonical.com> This happened to me today on startup, ubuntu 12.04 x86 --===============4591571337669137179== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Launchpad Janitor (janitor) Date: Fri, 13 Apr 2012 15:33:59 -0000 Message-Id: <20120413153406.10804.2278.malone@cocoplum.canonical.com> This bug was fixed in the package plymouth - 0.8.2-2ubuntu30 --------------- plymouth (0.8.2-2ubuntu30) precise; urgency=3Dlow [ Philip Mu=C5=A1kovac ] * debian/patches/kubuntu-text.patch: Change kubuntu-text theme to new grey (LP: #979824) [ James Hunt ] * Temporary work-around that minimizes chance of referencing invalid sources (LP: #553745). -- James Hunt Fri, 13 Apr 2012 15:11:36 +0100 --===============4591571337669137179== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Adolfo Jayme Barrientos (fitojb) Date: Fri, 13 Apr 2012 17:53:45 -0000 Message-Id: <20120413175345.4267.4316.malone@gac.canonical.com> Maverick has reached end of life, so invalidating --===============4591571337669137179== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: James Hunt (jamesodhunt) Date: Tue, 17 Apr 2012 09:38:51 -0000 Message-Id: <20120418124653.18419.34254.launchpad@loganberry.canonical.com> I think I've worked out what is going on here (and which caused me to raise the erroneous bug 42285): In ply_event_loop_process_pending_events(), ply_event_loop_handle_timeouts() is being called *after* epoll_wait(), but ply_event_loop_handle_timeouts() may free event sources. I can reliabily force plymouthd to SIGSEGV (in various parts of the code) by running the following: plymouth show-splash plymouth quit I'm seeing epoll_wait() return with a single valid fd event. ply_event_loop_handle_timeouts() then runs, and calls main.c:on_boot_splash_idle(). This causes the event source object referred to in the epoll_wait() event set to be freed and its reference count set to zero. After ply_event_loop_handle_timeouts() finishes, the now invalid source object pointed to by the epoll event data is referenced (it now has a reference_count of 1), and the invalid event is now processed with varying SIGSEGV scenarios ensuing. Currently ply_event_loop_process_pending_events() can be summarized as: 1. get events. 2. handle timeouts. 3. reference event sources. 4. process events. 5. unreference event sources. The attached patch changes this slightly to be effectively: 1. get events. 2. reference event sources. 3. handle timeouts. 4. process events. 5. unreference event sources. --===============4591571337669137179== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: James Hunt (jamesodhunt) Date: Tue, 17 Apr 2012 09:39:58 -0000 Message-Id: <20120418124654.18419.30972.launchpad@loganberry.canonical.com> Created attachment 60179 reference event sources before calling timeout handler to ensure events sta= y valid for loop iteration. If ply_event_loop_handle_timeouts() is called before the events returned by epoll_wait() are referenced, a timeout handler can free an event source leading to undefined behaviour (and frequently SIGSEGV crashes) once ply_event_loop_handle_timeouts() has finished since ply_event_loop_process_pending_events() continues to try and process the now invalid event sources. Thanks to cjwatson for a simpler solution to my original fix. Save errno values to ensure logic is robust in case handler makes system call. --===============4591571337669137179== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: James Hunt (jamesodhunt) Date: Wed, 18 Apr 2012 14:40:54 -0000 Message-Id: <20120418144054.8760.54299.malone@soybean.canonical.com> We now belive we understand the whole problem. A patch has been submitted upstream - see https://bugs.freedesktop.org/show_bug.cgi?id=3D28548 --===============4591571337669137179== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: James Hunt (jamesodhunt) Date: Wed, 25 Apr 2012 07:45:41 -0000 Message-Id: <20120425074541.22448.66333.malone@soybean.canonical.com> The full fix has now been accepted and committed upstream. --===============4591571337669137179== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Rstrode (rstrode) Date: Tue, 24 Apr 2012 14:36:07 -0000 Message-Id: <20120427133041.5067.21975.launchpad@loganberry.canonical.com> Hi, (In reply to comment #2) > I think I've worked out what is going on here (and which caused me to > raise the erroneous bug 42285): great! > In ply_event_loop_process_pending_events(), > ply_event_loop_handle_timeouts() is being called *after* epoll_wait(), > but ply_event_loop_handle_timeouts() may free event sources. ah ha. So to be a little more specific, a timeout callback may call ply_ev= ent_loop_stop_watching_fd and if that fd became ready at the same time as t= he callback then crash would result. =20 > I can reliabily force plymouthd to SIGSEGV (in various parts of the > code) by running the following: >=20 > plymouth show-splash > plymouth quit In this case plymouth quit queues a callback to get called after the animat= ion gets to an idle state, on_boot_splash_idle calls functions that ultimat= ely stops watching the terminal fd. if that callback happens in the same i= teration of the loop that the terminal fd becomes ready, then boom. Makes s= ense. Thanks for figuring this out. --===============4591571337669137179== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Rstrode (rstrode) Date: Tue, 24 Apr 2012 14:50:18 -0000 Message-Id: <20120427133041.5067.61003.launchpad@loganberry.canonical.com> Comment on attachment 60179 reference event sources before calling timeout handler to ensure events sta= y valid for loop iteration. Review of attachment 60179: ----------------------------------------------------------------- ::: src/libply/ply-event-loop.c @@ +1296,5 @@ > + { > + ply_event_source_t *source; > + source =3D (ply_event_source_t *) (events[i].data.ptr); > + > + ply_event_source_take_reference (source); we can't just take the reference inside the loop, since the loop may get called repeatedly because of EINTR. We could explicitly check for EINTR and not take the reference in that case, I guess. We do need to ensure events don't get dispatched after they are no longer being watched, but I think we should still be okay. The source is going to stick around, now, but the destination will still get free'd at stop_watching_fd time, so the source will in effect be orphaned and harmless. --===============4591571337669137179== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Rstrode (rstrode) Date: Tue, 24 Apr 2012 15:11:13 -0000 Message-Id: <20120427133041.5067.63853.launchpad@loganberry.canonical.com> Alright, pushed with minor changes: http://cgit.freedesktop.org/plymouth/commit/?id=3D16c7b306b34839d95a05f246f= 2184a7aab03b180 Thanks for tracking this down! --===============4591571337669137179== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Matthew (justapawn) Date: Thu, 07 Mar 2013 20:34:44 -0000 Message-Id: <20130307203444.31447.72721.malone@chaenomeles.canonical.com> I'm experiencing this bug using 12.10 Quantal Quetzal. When I try to do "also affects project" it will let me add "quantal-backpor= ts" but not "Quantal", and that doesn't seem right. (Is it?) So I don't know what to do. Thanks for your help. --===============4591571337669137179== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Glenn J. Schworak (glenn-schworak) Date: Fri, 17 May 2013 12:49:36 -0000 Message-Id: <20130517124936.15553.25618.malone@chaenomeles.canonical.com> I am experiencing this problem using 13.04. --===============4591571337669137179== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Mo Z (zmau1962) Date: Sun, 21 Jul 2013 19:04:32 -0000 Message-Id: <20130721190432.20778.7017.malone@gac.canonical.com> Funny Story : I had this bug infinite number of times. I was not able to work at all. The system would get to log-in window and crash after a few seconds. Once I was able to work a whole minuet before restart..... In the following link I saw a comment which told me that this is a consequence of a race between two drivers https://bugs.freedesktop.org/show_bug.cgi?id=3D48894 So, I pulled out the Ethernet cable, and the problem disappeared. After the system is UP, I can re-connect the Ethernet, and there is no problem..... More information : I am working with Ubuntu 12.04 on an Ivy Bridge machine.... --===============4591571337669137179==--