I'm also using gnome-panel and I am seeing the same behavior.
This is pretty annoying as once you accidentally press shut down in the menu
there is practically no easy way to undo this and whatever you press or even
when xkill-ing the window your computer will shut down.
This can cause
Public bug reported:
Xorg unexpectedly crashed bringing down down metacity and gnome-flashback too.
This is the relevant section from the system logs:
May 17 15:09:05 ultra-d gnome-session[1514]: Window manager warning: Log level
6: The program 'metacity' received an X Window System error.
May
Unfortunately the directory is empty.
I see that it does not turn out from my comment that this crash has only
happened to me once.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
Christopher, sorry for the very late answer.
Yes I'm using GNOME Flashback with Metacity.
I have been using this combination of desktop and WM since Ubuntu 15.04 came
out (April).
So it would be hard to say if using Compiz makes any change.
I was watching a movie in VLC then I switched VLC from
Public bug reported:
Xorg unexpectedly crahed with Segmentation fault during normal daily work using
gnome-shell.
Logs should contain all the necessary details.
ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: xorg 1:7.7+7ubuntu4
ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3
Public bug reported:
I was about to click on a button in Chromium when Xorg unexpectedly crashed.
This bug just happened and I doubt that it is reproducible.
This might be a kernel and not an xorg error, please re-categorize if needed.
Relevant section from the Xorg files:
[ 6812.749] (EE)
There is now a different Xorg trace that came along with the exactly same
kernel trace:
[194186.689] (EE) Backtrace:
[194186.692] (EE) 0: /usr/bin/X (xorg_backtrace+0x4e) [0x556be545768e]
[194186.692] (EE) 1: /usr/bin/X (0x556be52a3000+0x1b89f9) [0x556be545b9f9]
[194186.692] (EE) 2:
Christopher M. Penalver, what I wanted to point out in my last comment is that
since I reported this bug I changed to gnome-shell and even updated to 15.10 so
I will not be able to help further debugging this issue and of course as this
is about metacity and I don't use it any more I have not
Christopher M. Penalver, as I switched to gnome-shell meanwhile and I
had several Xorg crashes since then (see my bug reports) I'm not sure if
this happened to me again since then. Sorry for that.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
Christopher M. Penalver, it does not turn out for me form the linked
documentation what I could do here to capture the crash.
Please give me some more details.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
Christopher, I'm unfortunately not able to test the unstable image as this is
my work computer and I need to have a stable release running on it.
The other problem is that I can't reproduce the bug as it just happened, so
installing the daily image and running it for whatever time without this
Hi. Forgot to mention in the original report, but there was no crash
file for xorg in /var/crash after the crash.
--
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/1516699
Title:
Upstream bug: https://bugzilla.gnome.org/show_bug.cgi?id=767667
** Bug watch added: GNOME Bug Tracker #767667
https://bugzilla.gnome.org/show_bug.cgi?id=767667
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
Will do that in the next days.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1575354
Title:
Connecting to VPN times out after 25 seconds if login credentials not
Upgrading to BIOS 1.13.3 on Latitude 3520 seems to have solved the issue.
Thanks for the help.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1944409
Title:
Systemd uses
I experience the same issue on a Dell Latitude 3520.
It is Manjaro and systemd version is 249 but the issue/solution is exactly the
same.
Did you find any permanent solution to the problem?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
The difference between your and my setup is that I do not use a docking station.
Maybe worth a try if this also happens without it.
Upstream bug has been reported here:
https://github.com/systemd/systemd/issues/21751
Also, I have a BIOS update that just came out so will install it right now and
17 matches
Mail list logo
