[Touch-packages] [Bug 1476702] Re: Xorg crash when using Spotify client

2015-12-03 Thread Christopher M. Penalver
Paul Smith, this bug report is being closed due to your last comment
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1476702/comments/5
regarding this being fixed with a BIOS update. For future reference you
can manage the status of your own bugs by clicking on the current status
in the yellow line and then choosing a new status in the revealed drop
down box. You can learn more about bug statuses at
https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time
to report this bug and helping to make Ubuntu better. Please submit any
future bugs you may find.

** Changed in: xorg (Ubuntu)
   Importance: Low => Undecided

** Changed in: xorg (Ubuntu)
   Status: Expired => Invalid

-- 
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:
  Invalid

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  0x7f3db4d3b8dd in poll () at ../sysdeps/unix/syscall-template.S:81
  #1  0x7f3db5271ebc 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  0x7f3db5271ebc in g_main_context_iterate 
(context=context@entry=0x1363e20, block=block@entry=1, 
dispatch=dispatch@entry=1, self=) at 
/build/buildd/glib2.0-2.44.1/./glib/gmain.c:3803
  #3  0x7f3db5271fcc 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  0x7f3db5272009 in glib_worker_main (data=) at 
/build/buildd/glib2.0-2.44.1/./glib/gmain.c:5618
  #5  0x7f3db5298955 in g_thread_proxy (data=0x1364000) at 
/build/buildd/glib2.0-2.44.1/./glib/gthread.c:764
  #6  0x7f3db50116aa in start_thread (arg=0x7f3da0ebd700) at 
pthread_create.c:333
  #7  0x7f3db4d46eed in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

  Thread 1 (Thread 0x7f3db81a4a40 (LWP 16538)):
  #0  0x7f3db5278d00 in g_logv (log_domain=0x7f3db6bfc260 "mutter", 
log_level=G_LOG_LEVEL_ERROR, format=, 
args=args@entry=0x7ffd6e47ad40) at 
/build/buildd/glib2.0-2.44.1/./glib/gmessages.c:1046
  #1  0x7f3db5278f3f 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  0x7f3db6b71a7e in meta_clutter_init () at backends/meta-backend.c:469
  #3  0x7f3db6ba1072 in meta_init () at core/main.c:358
  #4  0x00401ddb 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 

[Touch-packages] [Bug 1476702] Re: Xorg crash when using Spotify client

2015-12-02 Thread Paul Smith
Updating the BIOS seems to have fixed it: no crashes since then.  Thanks
for the support!

-- 
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:
  Expired

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  0x7f3db4d3b8dd in poll () at ../sysdeps/unix/syscall-template.S:81
  #1  0x7f3db5271ebc 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  0x7f3db5271ebc in g_main_context_iterate 
(context=context@entry=0x1363e20, block=block@entry=1, 
dispatch=dispatch@entry=1, self=) at 
/build/buildd/glib2.0-2.44.1/./glib/gmain.c:3803
  #3  0x7f3db5271fcc 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  0x7f3db5272009 in glib_worker_main (data=) at 
/build/buildd/glib2.0-2.44.1/./glib/gmain.c:5618
  #5  0x7f3db5298955 in g_thread_proxy (data=0x1364000) at 
/build/buildd/glib2.0-2.44.1/./glib/gthread.c:764
  #6  0x7f3db50116aa in start_thread (arg=0x7f3da0ebd700) at 
pthread_create.c:333
  #7  0x7f3db4d46eed in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

  Thread 1 (Thread 0x7f3db81a4a40 (LWP 16538)):
  #0  0x7f3db5278d00 in g_logv (log_domain=0x7f3db6bfc260 "mutter", 
log_level=G_LOG_LEVEL_ERROR, format=, 
args=args@entry=0x7ffd6e47ad40) at 
/build/buildd/glib2.0-2.44.1/./glib/gmessages.c:1046
  #1  0x7f3db5278f3f 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  0x7f3db6b71a7e in meta_clutter_init () at backends/meta-backend.c:469
  #3  0x7f3db6ba1072 in meta_init () at core/main.c:358
  #4  0x00401ddb 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: 

[Touch-packages] [Bug 1476702] Re: Xorg crash when using Spotify client

2015-11-20 Thread Launchpad Bug Tracker
[Expired for xorg (Ubuntu) because there has been no activity for 60
days.]

** Changed in: xorg (Ubuntu)
   Status: Incomplete => Expired

-- 
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:
  Expired

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  0x7f3db4d3b8dd in poll () at ../sysdeps/unix/syscall-template.S:81
  #1  0x7f3db5271ebc 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  0x7f3db5271ebc in g_main_context_iterate 
(context=context@entry=0x1363e20, block=block@entry=1, 
dispatch=dispatch@entry=1, self=) at 
/build/buildd/glib2.0-2.44.1/./glib/gmain.c:3803
  #3  0x7f3db5271fcc 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  0x7f3db5272009 in glib_worker_main (data=) at 
/build/buildd/glib2.0-2.44.1/./glib/gmain.c:5618
  #5  0x7f3db5298955 in g_thread_proxy (data=0x1364000) at 
/build/buildd/glib2.0-2.44.1/./glib/gthread.c:764
  #6  0x7f3db50116aa in start_thread (arg=0x7f3da0ebd700) at 
pthread_create.c:333
  #7  0x7f3db4d46eed in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

  Thread 1 (Thread 0x7f3db81a4a40 (LWP 16538)):
  #0  0x7f3db5278d00 in g_logv (log_domain=0x7f3db6bfc260 "mutter", 
log_level=G_LOG_LEVEL_ERROR, format=, 
args=args@entry=0x7ffd6e47ad40) at 
/build/buildd/glib2.0-2.44.1/./glib/gmessages.c:1046
  #1  0x7f3db5278f3f 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  0x7f3db6b71a7e in meta_clutter_init () at backends/meta-backend.c:469
  #3  0x7f3db6ba1072 in meta_init () at core/main.c:358
  #4  0x00401ddb 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 

[Touch-packages] [Bug 1476702] Re: Xorg crash when using Spotify client

2015-09-21 Thread Paul Smith
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  0x7f3db4d3b8dd in poll () at ../sysdeps/unix/syscall-template.S:81
  #1  0x7f3db5271ebc 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  0x7f3db5271ebc in g_main_context_iterate 
(context=context@entry=0x1363e20, block=block@entry=1, 
dispatch=dispatch@entry=1, self=) at 
/build/buildd/glib2.0-2.44.1/./glib/gmain.c:3803
  #3  0x7f3db5271fcc 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  0x7f3db5272009 in glib_worker_main (data=) at 
/build/buildd/glib2.0-2.44.1/./glib/gmain.c:5618
  #5  0x7f3db5298955 in g_thread_proxy (data=0x1364000) at 
/build/buildd/glib2.0-2.44.1/./glib/gthread.c:764
  #6  0x7f3db50116aa in start_thread (arg=0x7f3da0ebd700) at 
pthread_create.c:333
  #7  0x7f3db4d46eed in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

  Thread 1 (Thread 0x7f3db81a4a40 (LWP 16538)):
  #0  0x7f3db5278d00 in g_logv (log_domain=0x7f3db6bfc260 "mutter", 
log_level=G_LOG_LEVEL_ERROR, format=, 
args=args@entry=0x7ffd6e47ad40) at 
/build/buildd/glib2.0-2.44.1/./glib/gmessages.c:1046
  #1  0x7f3db5278f3f 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  0x7f3db6b71a7e in meta_clutter_init () at backends/meta-backend.c:469
  #3  0x7f3db6ba1072 in meta_init () at core/main.c:358
  #4  0x00401ddb 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 

[Touch-packages] [Bug 1476702] Re: Xorg crash when using Spotify client

2015-09-20 Thread Christopher M. Penalver
Paul Smith, thank you for reporting this and helping make Ubuntu better.
As per https://www.asus.com/Tower-PCs/CM6870/HelpDesk_Download/ an
update to your computer's buggy and outdated BIOS is available (0708).
If you update to this following
https://help.ubuntu.com/community/BIOSUpdate does it change anything?

If it doesn't, could you please both specify what happened, and provide the 
output of the following terminal command:
sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date

For more on BIOS updates and linux, please see
https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette
.

Please note your current BIOS is already in the Bug Description, so
posting this on the old BIOS would not be helpful. As well, you don't
have to create a new bug report.

Once the BIOS is updated, and the information above is provided, then
please mark this report Status New.

Thank you for your understanding.

** Changed in: xorg (Ubuntu)
   Importance: Undecided => Low

** Changed in: xorg (Ubuntu)
   Status: New => Incomplete

-- 
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  0x7f3db4d3b8dd in poll () at ../sysdeps/unix/syscall-template.S:81
  #1  0x7f3db5271ebc 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  0x7f3db5271ebc in g_main_context_iterate 
(context=context@entry=0x1363e20, block=block@entry=1, 
dispatch=dispatch@entry=1, self=) at 
/build/buildd/glib2.0-2.44.1/./glib/gmain.c:3803
  #3  0x7f3db5271fcc 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  0x7f3db5272009 in glib_worker_main (data=) at 
/build/buildd/glib2.0-2.44.1/./glib/gmain.c:5618
  #5  0x7f3db5298955 in g_thread_proxy (data=0x1364000) at 
/build/buildd/glib2.0-2.44.1/./glib/gthread.c:764
  #6  0x7f3db50116aa in start_thread (arg=0x7f3da0ebd700) at 
pthread_create.c:333
  #7  0x7f3db4d46eed in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

  Thread 1 (Thread 0x7f3db81a4a40 (LWP 16538)):
  #0  0x7f3db5278d00 in g_logv (log_domain=0x7f3db6bfc260 "mutter", 
log_level=G_LOG_LEVEL_ERROR, format=, 
args=args@entry=0x7ffd6e47ad40) at 
/build/buildd/glib2.0-2.44.1/./glib/gmessages.c:1046
  #1  0x7f3db5278f3f 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  0x7f3db6b71a7e in meta_clutter_init () at backends/meta-backend.c:469
  #3  0x7f3db6ba1072 in meta_init () at core/main.c:358
  #4  0x00401ddb 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) 

[Touch-packages] [Bug 1476702] Re: Xorg crash when using Spotify client

2015-09-20 Thread Christopher M. Penalver
** Tags added: bios-outdated-0706

** Tags removed: bios-outdated-0706
** Tags added: bios-outdated-0708

-- 
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  0x7f3db4d3b8dd in poll () at ../sysdeps/unix/syscall-template.S:81
  #1  0x7f3db5271ebc 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  0x7f3db5271ebc in g_main_context_iterate 
(context=context@entry=0x1363e20, block=block@entry=1, 
dispatch=dispatch@entry=1, self=) at 
/build/buildd/glib2.0-2.44.1/./glib/gmain.c:3803
  #3  0x7f3db5271fcc 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  0x7f3db5272009 in glib_worker_main (data=) at 
/build/buildd/glib2.0-2.44.1/./glib/gmain.c:5618
  #5  0x7f3db5298955 in g_thread_proxy (data=0x1364000) at 
/build/buildd/glib2.0-2.44.1/./glib/gthread.c:764
  #6  0x7f3db50116aa in start_thread (arg=0x7f3da0ebd700) at 
pthread_create.c:333
  #7  0x7f3db4d46eed in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

  Thread 1 (Thread 0x7f3db81a4a40 (LWP 16538)):
  #0  0x7f3db5278d00 in g_logv (log_domain=0x7f3db6bfc260 "mutter", 
log_level=G_LOG_LEVEL_ERROR, format=, 
args=args@entry=0x7ffd6e47ad40) at 
/build/buildd/glib2.0-2.44.1/./glib/gmessages.c:1046
  #1  0x7f3db5278f3f 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  0x7f3db6b71a7e in meta_clutter_init () at backends/meta-backend.c:469
  #3  0x7f3db6ba1072 in meta_init () at core/main.c:358
  #4  0x00401ddb 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