I have also been hit by this bug. Extremely irritating.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1292041
Title:
Lockscreen doesn't turn off the screen
To manage notifications about this bug
I was just hit again with it today, with metacity 1:3.18.7-0ubuntu0.3 on
16.04.
Here is the crash dump.
** Attachment added: "_usr_bin_metacity.1000.crash"
https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/1507764/+attachment/5189891/+files/_usr_bin_metacity.1000.crash
--
You
Used the workaround in #12, but it is still a major annoyance that
gnome-keyring-daemon does not handle this.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/771272
Title:
gnome-keyring doesn't
Public bug reported:
At times (I have not found the trigger to reproduce it at will), one
terminal window out of many will refuse to receive complex input
sequences (such as the French composite accented character "ê" (which is
typed with "^ + e" on a french keyboard), or IBus/Anthy Japanese
Public bug reported:
I have noticed several issues with keyboard input processing, that can
all seemingly be tied to high CPU usage.
For context, I am using a french keyboard, and also need to type
Japanese, which has me using IBus and Anthy.
I think at some point in Ubuntu, the way input was
Public bug reported:
The very useful autosave feature that runs every five minutes locks up
the editor when it runs, and when it happens, any keystrokes typed
during the interval are lost.
Such that when typing the following (for example) :
abcdefghijklmnopqrstuvwxyz
If autosave runs during
I upgraded to older version 3.18.1-1ubuntu3, and relaunched metacity
using "metacity --replace", and now I have metacity crashes, but they
don't log me out.
Just wondering if the fact I "replaced" metacity while logged in untied
it from gnome-session.
--
You received this bug notification
It's hard to reproduce "at will". I personally run Firefox, Thunderbird,
Chrome, gedit, gjiten, skype, pidgin, Gnome Terminal, and always have
something like 20 windows open at a time on my main workspace.
Of note :
- When alt tabbing between windows, sometimes surfaces flash to black for one
Initially, I thought the crash was linked to what was implementing the
window switching (with the Compiz configuration tool, one can select
several ways to switch windows, including the Static Application
Switcher, which only shows icons of the application instead of the
contents of the window ;
About the packages, I am still using 15.04 Vivid (which means metacity
3.14), and it seems metacity and gtk+-3.0 will require a ton of
dependencies (glib, pango, atk, etc...), so I can't test these right
away.
Here is what I get :
$ gsettings get org.gnome.metacity alt-tab-thumbnails
No such key
I just had again the same crash. :
Dec 30 23:49:59 archer gnome-session[28277]: Window manager warning: Log level
6: The program 'metacity' received an X Window System error.
Dec 30 23:49:59 archer gnome-session[28277]: This probably reflects a bug in
the program.
Dec 30 23:49:59 archer
I just had again the same crash. :
Dec 30 23:49:59 archer gnome-session[28277]: Window manager warning: Log level
6: The program 'metacity' received an X Window System error.
Dec 30 23:49:59 archer gnome-session[28277]: This probably reflects a bug in
the program.
Dec 30 23:49:59 archer
Public bug reported:
This is a duplicate of bug 1507764, but the bug reporting system would
not let me find it for further addition.
I am posting this in hopes that by crossing this trace and the previous
one this might help developers find what is going on.
ProblemType: Crash
DistroRelease:
Maybe a duplicate of
https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/1507764 (or at
least related ?)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1455916
Title:
Xorg unexpectedly crashed
The crash is still happening no matter what I update.
The fact it comes after somewhat intensive use (one week, two weeks of not
rebooting) and when doing Alt+Tab repeatedly in succession hints maybe at
memory leaks? Again, right before the crashes, artifacts of the application
switcher windows
It seems to crash when I switch windows (alt+tab ; even falling back to
the static application switcher does not alleviate the bug).
For reference, I do a lot of translation work, which requires me to have
gedit, mplayer, evince running at the same time and heavily switching
between these.
Sorry, forgot to specify this : the Alt+Tab crash is indeed seemingly random.
At one point after one day or two of running, Alt+Tab will start leaving
refresh artifacts (parts of another window that I was browsing while switching)
and eventually just outright freeze and crash.
--
You received
** Information type changed from Private to Public
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1507764
Title:
metacity crashed with signal 5 in _XEventsQueued() ; forcing gnome
session to
I also have confirmed the bug, it just happened right now, and here is
the crash dump for metacity.
It feels like gnome-session is trying to restart metacity too fast, when
waiting a few seconds before respawning it would avoid this problem...
** Attachment added: "_usr_bin_metacity.1000.crash"
I would like to propose the following patch to handle the options in the
configuration file (just tested it right now, and it does the job)
[vpn]
...
ping=10
ping-restart=60
As one can see, the process spawned has the proper arguments :
$ ps auxw | grep vpn
root 3752 0.0 0.0 28444 2728
Also confirming this problem.
This is really ANNOYING with a full network of Ubuntu machines, there is
no proper way of monitoring the network interface information, screwing
up about every NMS you can find in the book.
Any further input, help, or attention would be much appreciated.
--
Wrong
Also confirming this problem.
This is really ANNOYING with a full network of Ubuntu machines, there is
no proper way of monitoring the network interface information, screwing
up about every NMS you can find in the book.
Any further input, help, or attention would be much appreciated.
--
Wrong
Public bug reported:
Binary package hint: hal
In Jaunty Jackalope, hald crashed at boot time (and other daemons
depending on hald didn't start).
Following the instructions from man hald, running a gdb hald with
options --daemon=no --verbose=yes has hald crash at this point :
04:34:26.151 [I]
Also occurs for me even on Ubuntu Intrepid.
pulseaudio is 0.9.10-2ubuntu9, alsa is 1.0.17.dfsg-2ubuntu1, running on
kernel 2.6.27-7-generic on a x86_64 machine.
It seems to occur when I have a paused amarok, and a paused mplayer and
pops randomly.
I keep a running terminal with the command
24 matches
Mail list logo
