[Ubuntu-x-swat] [Bug 1526155] Re: nvidia-* kernel module failed to build [cc: error: unrecognized command line option ‘-fstack-protector-strong’]
** Also affects: nvidia-graphics-drivers-375 (Ubuntu) Importance: Undecided Status: New ** Changed in: nvidia-graphics-drivers-375 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers-304-updates in Ubuntu. https://bugs.launchpad.net/bugs/1526155 Title: nvidia-* kernel module failed to build [cc: error: unrecognized command line option ‘-fstack-protector-strong’] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304-updates/+bug/1526155/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1639180] Re: no login possible after update to nvidia 304.132
Did anyone try 304.135-0ubuntu0.16.04.1 on 16.04.2? I would not want to mess up my system if it doesn't work. Any success? Thanks. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers-304 in Ubuntu. https://bugs.launchpad.net/bugs/1639180 Title: no login possible after update to nvidia 304.132 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1639180/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1593549] Re: cannot install libvdpau1 as ffmpeg need
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: libvdpau (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to libvdpau in Ubuntu. https://bugs.launchpad.net/bugs/1593549 Title: cannot install libvdpau1 as ffmpeg need To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ffmpeg/+bug/1593549/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1672033] Re: Xorg does not detect displays in rootless mode on nvidia proprietary drivers (GNOME)
** Attachment added: "xorg_after_lightdm.txt" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1672033/+attachment/4841880/+files/xorg_after_lightdm.txt -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1672033 Title: Xorg does not detect displays in rootless mode on nvidia proprietary drivers (GNOME) To manage notifications about this bug go to: https://bugs.launchpad.net/nvidia-drivers-ubuntu/+bug/1672033/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1672033] Re: Xorg does not detect displays in rootless mode on nvidia proprietary drivers (GNOME)
** Attachment added: "xorg_faileed_monitor_detect.txt" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1672033/+attachment/4841879/+files/xorg_faileed_monitor_detect.txt -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1672033 Title: Xorg does not detect displays in rootless mode on nvidia proprietary drivers (GNOME) To manage notifications about this bug go to: https://bugs.launchpad.net/nvidia-drivers-ubuntu/+bug/1672033/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1672033] Re: Xorg does not detect displays in rootless mode on nvidia proprietary drivers (GNOME)
Here you go: ** Attachment added: "logind.txt" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1672033/+attachment/4841878/+files/logind.txt -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1672033 Title: Xorg does not detect displays in rootless mode on nvidia proprietary drivers (GNOME) To manage notifications about this bug go to: https://bugs.launchpad.net/nvidia-drivers-ubuntu/+bug/1672033/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1300215] Re: Failed to open VDPAU backend libvdpau_i965.so: cannot open shared object file: No such file or directory
Closing VLC bug as already explained in previous comment. ** Changed in: vlc (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to libvdpau in Ubuntu. https://bugs.launchpad.net/bugs/1300215 Title: Failed to open VDPAU backend libvdpau_i965.so: cannot open shared object file: No such file or directory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvdpau/+bug/1300215/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1553441] Re: [Asus K55DR] When VGA plugged into laptop, only one monitor working at a time
** Tags removed: kernel-bug-exists-upstream-4.11-rc1 ** Tags added: kernel-bug-exists-upstream-4.11-rc3 -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/1553441 Title: [Asus K55DR] When VGA plugged into laptop, only one monitor working at a time To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1553441/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1674704] [NEW] blank screen after software update
Public bug reported: I ran "sudo apt-get upgrade" and after rebooting I started to have problems with the display. Now it's black even from the boot options screen (I mean before GRUB menu). I left the system go up end after connecting via ssh I could see the following in dmesg: [ 796.633789] [drm:radeon_cs_ioctl] *ERROR* Failed to schedule IB ! [ 797.133525] [drm:radeon_ib_schedule] *ERROR* radeon: couldn't schedule IB(8). [ 797.133531] [drm:radeon_cs_ioctl] *ERROR* Failed to schedule IB ! [ 797.633326] [drm:radeon_ib_schedule] *ERROR* radeon: couldn't schedule IB(9). [ 797.61] [drm:radeon_cs_ioctl] *ERROR* Failed to schedule IB ! [ 798.133117] [drm:radeon_ib_schedule] *ERROR* radeon: couldn't schedule IB(10). [ 798.133122] [drm:radeon_cs_ioctl] *ERROR* Failed to schedule IB ! [ 798.632897] [drm:radeon_ib_schedule] *ERROR* radeon: couldn't schedule IB(11). [ 798.632903] [drm:radeon_cs_ioctl] *ERROR* Failed to schedule IB ! [ 799.132682] [drm:radeon_ib_schedule] *ERROR* radeon: couldn't schedule IB(12). [ 799.132687] [drm:radeon_cs_ioctl] *ERROR* Failed to schedule IB ! [ 799.632462] [drm:radeon_ib_schedule] *ERROR* radeon: couldn't schedule IB(13). [ 799.632467] [drm:radeon_cs_ioctl] *ERROR* Failed to schedule IB ! [ 800.132257] [drm:radeon_ib_schedule] *ERROR* radeon: couldn't schedule IB(14). [ 800.132263] [drm:radeon_cs_ioctl] *ERROR* Failed to schedule IB ! [ 800.632060] [drm:radeon_ib_schedule] *ERROR* radeon: couldn't schedule IB(15). [ 800.632065] [drm:radeon_cs_ioctl] *ERROR* Failed to schedule IB ! [ 801.131826] [drm:radeon_ib_schedule] *ERROR* radeon: couldn't schedule IB(0). [ 801.131832] [drm:radeon_cs_ioctl] *ERROR* Failed to schedule IB ! [ 801.631619] [drm:radeon_ib_schedule] *ERROR* radeon: couldn't schedule IB(1). [ 801.631624] [drm:radeon_cs_ioctl] *ERROR* Failed to schedule IB ! [ 802.131420] [drm:radeon_ib_schedule] *ERROR* radeon: couldn't schedule IB(2). [ 802.131426] [drm:radeon_cs_ioctl] *ERROR* Failed to schedule IB ! [ 802.631209] [drm:radeon_ib_schedule] *ERROR* radeon: couldn't schedule IB(3). $ uname -a Linux ajax 3.2.0-124-generic #167-Ubuntu SMP Fri Mar 3 15:25:36 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux Any suggestion? Thanks in advance, Giuseppe ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: xorg 1:7.6+12ubuntu2 ProcVersionSignature: Ubuntu 3.2.0-124.167-generic 3.2.79 Uname: Linux 3.2.0-124-generic x86_64 ApportVersion: 2.0.1-0ubuntu17.15 Architecture: amd64 Date: Tue Mar 21 15:25:55 2017 InstallationMedia: Kubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120423) MarkForUpload: True SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug precise -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1674704 Title: blank screen after software update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1674704/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1636564] Re: Segfault from libX11.so.6.3.0
Although the referenced bug regards Nvidia, some comments mention similar problems with Radeon (and I'm not using Nvidia drivers either - I have integrated Intel graphics). My main point was that the syslog lists other errors before the segfault, so this can be a result rather than the cause. I could not find a syslog in your report. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to libx11 in Ubuntu. https://bugs.launchpad.net/bugs/1636564 Title: Segfault from libX11.so.6.3.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libx11/+bug/1636564/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1674674] Re: Xorg crashed with SIGABRT in OsAbort()
*** This bug is a duplicate of bug 1543192 *** https://bugs.launchpad.net/bugs/1543192 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1543192, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1674674/+attachment/4841572/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1674674/+attachment/4841575/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1674674/+attachment/4841585/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1674674/+attachment/4841587/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1674674/+attachment/4841588/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1674674/+attachment/4841589/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1674674/+attachment/4841590/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1543192 Xorg crashed with SIGABRT in OsAbort() ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers in Ubuntu. https://bugs.launchpad.net/bugs/1674674 Title: Xorg crashed with SIGABRT in OsAbort() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/1674674/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1673850] Re: Problem with video after suspend
you're using amdgpu-pro, we can't support that ** Changed in: xorg (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1673850 Title: Problem with video after suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1673850/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1673286] Re: /usr/bin/mate-volume-control-applet:11:malloc_consolidate:_int_malloc:__GI___libc_malloc:read_packet:_xcb_in_read
** Package changed: mate-media (Ubuntu) => libxcb (Ubuntu) -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to libxcb in Ubuntu. https://bugs.launchpad.net/bugs/1673286 Title: /usr/bin/mate-volume-control- applet:11:malloc_consolidate:_int_malloc:__GI___libc_malloc:read_packet:_xcb_in_read To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxcb/+bug/1673286/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1673286] [NEW] /usr/bin/mate-volume-control-applet:11:malloc_consolidate:_int_malloc:__GI___libc_malloc:read_packet:_xcb_in_read
You have been subscribed to a public bug: The Ubuntu Error Tracker has been receiving reports about a problem regarding mate-media. This problem was most recently seen with package version 1.12.1-1, the problem page at https://errors.ubuntu.com/problem/31206cc9f08f903a2d53a96328a56c00a5561c3a contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. ** Affects: libxcb (Ubuntu) Importance: Undecided Status: New ** Tags: xenial -- /usr/bin/mate-volume-control-applet:11:malloc_consolidate:_int_malloc:__GI___libc_malloc:read_packet:_xcb_in_read https://bugs.launchpad.net/bugs/1673286 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to libxcb in Ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1639517] Re: [HP Pavilion Notebook - 17-g164ng] black screen when booting
Upstream kernel test - kernel 4.11-rc3 Installation without errors. booting (no workaround) > 3 min no local login remote login (ssh) dmesg: some errors backlight: as formerly described -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1639517 Title: [HP Pavilion Notebook - 17-g164ng] black screen when booting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1639517/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1639517] Re: [HP Pavilion Notebook - 17-g164ng] black screen when booting
** Tags removed: kernel-bug-exists-upstream-4.11-rc2 ** Tags added: kernel-bug-exists-upstream-4.11-rc3 -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1639517 Title: [HP Pavilion Notebook - 17-g164ng] black screen when booting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1639517/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1672033] Re: Xorg does not detect displays in rootless mode on nvidia proprietary drivers (GNOME)
Igor, can you post full logs from Xorg, and also any systemd-logind logs from journalctl. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1672033 Title: Xorg does not detect displays in rootless mode on nvidia proprietary drivers (GNOME) To manage notifications about this bug go to: https://bugs.launchpad.net/nvidia-drivers-ubuntu/+bug/1672033/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1672033] Re: Xorg does not detect displays in rootless mode on nvidia proprietary drivers (GNOME)
(before your workaround) -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1672033 Title: Xorg does not detect displays in rootless mode on nvidia proprietary drivers (GNOME) To manage notifications about this bug go to: https://bugs.launchpad.net/nvidia-drivers-ubuntu/+bug/1672033/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
Re: [Ubuntu-x-swat] [Bug 1636564] Re: Segfault from libX11.so.6.3.0
I don't think I'm using the Nvidia drivers on the machine I reported this
from. That would mean they could not be the route cause.
On Mon, 20 Mar 2017, 17:51 Jan Lachnitt, <1636...@bugs.launchpad.net>
wrote:
> Another report and some thoughts below
>
> HW: Asus Vivobook (touchscreen, Intel graphics), external monitor attached.
> OS: Linux Mint 18 Cinnamon x64.
> State before crash: Running X session using both displays ("big desktop"),
> several applications, Vivaldi browser active.
> My aim: Lock the computer.
> Course of action, the USUAL part: Pressed Ctrl+Alt+L, not locked - Vivaldi
> displayed its menu (to be displayed upon pressing Alt), tapped the
> touchscreen to get rid of the menu and thus actually lock the computer.
> Course of action, the UNUSUAL part: Black screen for a few seconds, then
> login screen, old X session gone.
>
> syslog:
> Mar 20 14:43:20 VivoBook org.a11y.atspi.Registry[1729]: XIO: fatal IO
> error 11 (Resource temporarily unavailable) on X server ":0"
> Mar 20 14:43:20 VivoBook org.a11y.atspi.Registry[1729]: after 2925
> requests (2925 known processed) with 0 events remaining.
> Mar 20 14:43:20 VivoBook cinnamon-session[1640]: Gdk-WARNING:
> t+4492,79569s: cinnamon-session: Fatal IO error 11 (Prostředek je dočasně
> nepřístupný) on X server :0.
> Mar 20 14:43:20 VivoBook org.gtk.vfs.Daemon[1711]: A connection to the bus
> can't be made
> Mar 20 14:43:20 VivoBook org.gtk.vfs.Daemon[1711]: A connection to the bus
> can't be made
> Mar 20 14:43:20 VivoBook mdm[1212]: WARNING: mdm_slave_xioerror_handler:
> Kritická chyba X - Restartování :0
> Mar 20 14:43:20 VivoBook kernel: [ 4538.677519] vivaldi-bin[4100]:
> segfault at 968 ip 7f61ac384643 sp 7ffc09f25b50 error 4 in
> libX11.so.6.3.0[7f61ac35c000+135000]
> Mar 20 14:43:20 VivoBook ag[4118]: mdm-superpost Starting...
> Mar 20 14:43:20 VivoBook ag[4122]: mdm-superpost Finished
> Mar 20 14:43:20 VivoBook console-kit-daemon[1566]: (process:4128):
> GLib-CRITICAL **: g_slice_set_config: assertion 'sys_page_size == 0' failed
> Mar 20 14:43:21 VivoBook acpid: client 1219[0:0] has disconnected
> Mar 20 14:43:21 VivoBook acpid: client connected from 4131[0:0]
> Mar 20 14:43:21 VivoBook acpid: 1 client rule loaded
> Mar 20 14:43:22 VivoBook ag[4139]: mdm-superinit Starting...
> Mar 20 14:43:22 VivoBook ag[4140]: mdm-superinit Finished
>
> Xorg.0.log covers the new session, Xorg.0.log.old has no record of the
> event.
>
> The segfault really seems to affect multiple users, especially with
> Chromium-based browsers, e.g.:
> https://bbs.archlinux.org/viewtopic.php?id=131328 - from 2011 already
> https://bbs.archlinux.org/viewtopic.php?id=221888 - solution?
>
> I don't know if syslog preserves the order of events (within a second),
> but if yes, then the segfault is just a consequence of another problem,
> e.g.:
>
> https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/999191
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1636564
>
> Title:
> Segfault from libX11.so.6.3.0
>
> Status in libx11 package in Ubuntu:
> Confirmed
>
> Bug description:
> Something went wrong with my Ubuntu 16.04 LTS desktop today. When I
> got back to the system Mattermost and a Chrome were indicating that
> the network was not working. I started to look about and it seemed
> that my main ethernet network connection had lost its IPv4 address
> somehow. ifconfig and the GUI network manager confirmed this.
>
> To try and resolve this I physically removed the connector and the
> plugged it back in. Shortly after I did this my GUI seemed to die out
> and I ended up back at the login screen.
>
> Once everything had calmed down I logged back in. After some digging
> about in the logs I noticed the following in /var/log/kern.log
>
> Oct 25 13:01:09 thorne-ul-dt kernel: [694321.877561] Mattermost[744]:
> segfault at 968 ip 7f8a9e257643 sp 7ffe72a3b510 error 4 in
> libX11.so.6.3.0[7f8a9e22f000+135000]
> Oct 25 13:01:09 thorne-ul-dt kernel: [694322.029362] chrome[745]:
> segfault at 968 ip 7fd4b5c73643 sp 7fff94f78d90 error 4 in
> libX11.so.6.3.0[7fd4b5c4b000+135000]
>
> That seemed to be the correct time for the problem I noticed. What
> exactly caused it I am not sure.
>
> ProblemType: Bug
> DistroRelease: Ubuntu 16.04
> Package: libx11-6 2:1.6.3-1ubuntu2
> ProcVersionSignature: Ubuntu 4.4.0-42.62-generic 4.4.21
> Uname: Linux 4.4.0-42-generic x86_64
> .tmp.unity_support_test.0:
>
> ApportVersion: 2.20.1-0ubuntu2.1
> Architecture: amd64
> CompizPlugins: No value set for
> `/apps/compiz-1/general/screen0/options/active_plugins'
> CompositorRunning: compiz
> CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
> CompositorUnredirectFSW: true
> CurrentDesktop: Unity
> Date: Tue Oct 25 17:07:28 2016
> DistUpgraded: Fresh install
> DistroCodename: xenial
> DistroVariant:
