OK I've updated my bios: $ sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date 0708 12/25/2012
I used to get crashes just by semi-vigorous scrolling in the Spotify window but a session of clicking and scrolling so far hasn't reproduced the crash. I'll keep trying for a while. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1476702 Title: Xorg crash when using Spotify client Status in xorg package in Ubuntu: Incomplete Bug description: Ever since I upgraded from Ubuntu GNOME 14.04 to Ubuntu GNOME 15.04, I've had my entire desktop crash relatively quickly when using Spotify, if I mess around with the client much. Just starting the client is no problem, and it plays songs OK, but for a while whenever I clicked one of my playlists it would immediately crash. I stopped using the client for a while, but last week started using again and it was working for these simple cases. Today I started the client, picked a playlist, and grabbed the scrollbar and dragged it all the way to the top; as I was dragging my desktop crashed. In my home directory I see a gnome-shell core: (gdb) thr a a bt Thread 2 (Thread 0x7f3da0ebd700 (LWP 16545)): #0 0x00007f3db4d3b8dd in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0x00007f3db5271ebc in g_main_context_iterate (priority=2147483647, n_fds=1, fds=0x7f3d9c0008e0, timeout=-1, context=0x1363e20) at /build/buildd/glib2.0-2.44.1/./glib/gmain.c:4103 #2 0x00007f3db5271ebc in g_main_context_iterate (context=context@entry=0x1363e20, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>) at /build/buildd/glib2.0-2.44.1/./glib/gmain.c:3803 #3 0x00007f3db5271fcc in g_main_context_iteration (context=0x1363e20, may_block=may_block@entry=1) at /build/buildd/glib2.0-2.44.1/./glib/gmain.c:3869 #4 0x00007f3db5272009 in glib_worker_main (data=<optimized out>) at /build/buildd/glib2.0-2.44.1/./glib/gmain.c:5618 #5 0x00007f3db5298955 in g_thread_proxy (data=0x1364000) at /build/buildd/glib2.0-2.44.1/./glib/gthread.c:764 #6 0x00007f3db50116aa in start_thread (arg=0x7f3da0ebd700) at pthread_create.c:333 #7 0x00007f3db4d46eed in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 1 (Thread 0x7f3db81a4a40 (LWP 16538)): #0 0x00007f3db5278d00 in g_logv (log_domain=0x7f3db6bfc260 "mutter", log_level=G_LOG_LEVEL_ERROR, format=<optimized out>, args=args@entry=0x7ffd6e47ad40) at /build/buildd/glib2.0-2.44.1/./glib/gmessages.c:1046 #1 0x00007f3db5278f3f in g_log (log_domain=log_domain@entry=0x7f3db6bfc260 "mutter", log_level=log_level@entry=G_LOG_LEVEL_ERROR, format=format@entry=0x7f3db6bf4838 "Unable to initialize Clutter.\n") at /build/buildd/glib2.0-2.44.1/./glib/gmessages.c:1079 #2 0x00007f3db6b71a7e in meta_clutter_init () at backends/meta-backend.c:469 #3 0x00007f3db6ba1072 in meta_init () at core/main.c:358 #4 0x0000000000401ddb in main (argc=1, argv=0x7ffd6e47b1b8) at main.c:429 but I think this is just a symptom of the X server crashing; in my X session log file (Xorg.0.log.old probably attached below) I see: [939562.032] (EE) [939562.064] (EE) Backtrace: [939562.212] (EE) 0: /usr/bin/X (xorg_backtrace+0x56) [0x7f5a10ef6556] [939562.212] (EE) 1: /usr/bin/X (0x7f5a10d43000+0x1b7749) [0x7f5a10efa749] [939562.212] (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (0x7f5a0ea09000+0x352f0) [0x7f5a0ea3e2f0] [939562.212] (EE) 3: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7f5a0afe8000+0xfa6c3) [0x7f5a0b0e26c3] [939562.213] (EE) 4: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7f5a0afe8000+0x10cf60) [0x7f5a0b0f4f60] [939562.213] (EE) 5: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7f5a0afe8000+0x10e3ac) [0x7f5a0b0f63ac] [939562.213] (EE) 6: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7f5a0afe8000+0x10f343) [0x7f5a0b0f7343] [939562.213] (EE) 7: /usr/bin/X (DRI2SwapBuffers+0x1d0) [0x7f5a10ec9100] [939562.213] (EE) 8: /usr/bin/X (0x7f5a10d43000+0x187a7c) [0x7f5a10ecaa7c] [939562.213] (EE) 9: /usr/bin/X (0x7f5a10d43000+0x580a7) [0x7f5a10d9b0a7] [939562.213] (EE) 10: /usr/bin/X (0x7f5a10d43000+0x5c29b) [0x7f5a10d9f29b] [939562.213] (EE) 11: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf0) [0x7f5a0ea29a40] [939562.213] (EE) 12: /usr/bin/X (0x7f5a10d43000+0x4662e) [0x7f5a10d8962e] [939562.213] (EE) [939562.215] (EE) Segmentation fault at address 0x7f5a1119b004 [939562.215] (EE) Fatal server error: [939562.215] (EE) Caught signal 11 (Segmentation fault). Server aborting So maybe an issue with the Intel display driver? ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-22.22-generic 3.19.8-ckt1 Uname: Linux 3.19.0-22-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME Date: Tue Jul 21 10:25:08 2015 DistUpgraded: 2015-04-27 12:05:00,462 DEBUG enabling apt cron job DistroCodename: vivid DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [8086:0162] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. P8 series motherboard [1043:84ca] InstallationDate: Installed on 2014-04-28 (449 days ago) InstallationMedia: Ubuntu-GNOME 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) MachineType: ASUSTeK COMPUTER INC. CM6870 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-22-generic root=UUID=6fec1c27-b55b-4e04-97b8-fc3b02c85068 ro quiet splash nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to vivid on 2015-04-27 (84 days ago) dmi.bios.date: 02/24/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0408 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: CM6870 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0408:bd02/24/2012:svnASUSTeKCOMPUTERINC.:pnCM6870:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnCM6870:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: CM6870 dmi.product.version: System Version dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.12.1+15.04.20150410.1-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.60-2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.2-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2build1 xserver.bootTime: Tue Jul 21 10:12:48 2015 xserver.configfile: default xserver.devices: input Power Button KEYBOARD, id 6 input Power Button KEYBOARD, id 7 input Logitech K520 KEYBOARD, id 8 input Logitech M310/M310t MOUSE, id 9 input Eee PC WMI hotkeys KEYBOARD, id 10 xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.17.1-0ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1476702/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
