[Bug 1292041] Re: Lockscreen doesn't turn off the screen

2019-05-13 Thread Stephane Lapie
I have also been hit by this bug. Extremely irritating.

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-screensaver in Ubuntu.
https://bugs.launchpad.net/bugs/1292041

Title:
  Lockscreen doesn't turn off the screen

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1292041/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1507764] Re: metacity crashed with signal 5 in _XEventsQueued() ; forcing gnome session to logout

2018-09-17 Thread Stephane Lapie
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 received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to metacity in Ubuntu.
https://bugs.launchpad.net/bugs/1507764

Title:
  metacity crashed with signal 5 in _XEventsQueued() ; forcing gnome
  session to logout

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/1507764/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 771272] Re: gnome-keyring doesn't support ecdsa or ed25519 keys

2017-06-25 Thread Stephane Lapie
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
Desktop Bugs, which is subscribed to gnome-keyring in Ubuntu.
https://bugs.launchpad.net/bugs/771272

Title:
  gnome-keyring doesn't support ecdsa or ed25519 keys

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-keyring/+bug/771272/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs


[Bug 1637855] [NEW] Composite characters or Japanese input gets sometimes sent to the wrong terminal window

2016-10-30 Thread Stephane Lapie
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 input),
and only these characters will be redirected to another terminal window.

This means that for two terminals, typing in terminal 1 : "Verbe être" results 
in this :
Terminal 1 : "Verbe tre"
Terminal 2 : "ê"

When this happens, the following workarounds work to put things in order :
- close the affected terminal window
- spawn a new one and close it

I am not sure whether this is an IBus problem, or a Gnome Terminal
problem at its core.

ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: gnome-terminal 3.16.2-1ubuntu4
ProcVersionSignature: Ubuntu 4.2.0-35.40-generic 4.2.8-ckt5
Uname: Linux 4.2.0-35-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.19.1-0ubuntu5
Architecture: amd64
CurrentDesktop: GNOME-Flashback:Unity
Date: Mon Oct 31 01:51:06 2016
InstallationDate: Installed on 2010-01-30 (2465 days ago)
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027.1)
SourcePackage: gnome-terminal
UpgradeStatus: Upgraded to wily on 2016-04-16 (197 days ago)

** Affects: gnome-terminal (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug third-party-packages wily

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu.
https://bugs.launchpad.net/bugs/1637855

Title:
  Composite characters or Japanese input gets sometimes sent to the
  wrong terminal window

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1637855/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1637822] [NEW] autosave freezes editor and loses keystrokes

2016-10-30 Thread Stephane Lapie
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 that interval, here is an example of what ends up being 
processed :
abcdefghpqrstuvwxyz

As is obvious, keystrokes for "ijklmno" are lost.
This happens every time.

I am not sure if this is specific to gedit, or to the input framework I
am using (IBus, and at times Anthy for Japanese input)

This is quite annoying as it forces me to re-read absolutely everything
I typed to make sure gedit did not miss anything.

ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: gedit 3.10.4-0ubuntu13
ProcVersionSignature: Ubuntu 4.2.0-35.40-generic 4.2.8-ckt5
Uname: Linux 4.2.0-35-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.19.1-0ubuntu5
Architecture: amd64
CurrentDesktop: GNOME-Flashback:Unity
Date: Sun Oct 30 20:37:04 2016
InstallationDate: Installed on 2010-01-30 (2464 days ago)
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027.1)
SourcePackage: gedit
UpgradeStatus: Upgraded to wily on 2016-04-16 (196 days ago)

** Affects: gedit (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug third-party-packages wily

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gedit in Ubuntu.
https://bugs.launchpad.net/bugs/1637822

Title:
  autosave freezes editor and loses keystrokes

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1637822/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs


[Bug 1507764] Re: metacity crashed with signal 5 in _XEventsQueued() ; forcing gnome session to logout

2016-05-04 Thread Stephane Lapie
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 because you are a member of Ubuntu
Desktop Bugs, which is subscribed to metacity in Ubuntu.
https://bugs.launchpad.net/bugs/1507764

Title:
  metacity crashed with signal 5 in _XEventsQueued() ; forcing gnome
  session to logout

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/1507764/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs


[Bug 1507764] Re: metacity crashed with signal 5 in _XEventsQueued() ; forcing gnome session to logout

2016-02-11 Thread Stephane Lapie
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 
instant before redraw happens.
This might indicate that the core problem with metacity crashing in the first 
place is linked to Xorg or the nvidia driver ?
- Also, with previous versions of Ubuntu, I did have metacity crash on me at 
times, but the session would keep on running, so I could relaunch metacity from 
an open terminal (or via console using : DISPLAY=:0.0 metacity ) ; The crash 
itself is not a problem, gnome-sessions's extremely poor handling of it is.

The easiest way for me to produce this crash is to edit text in gedit,
open a PDF in evince, and spend my time alt tabbing between them (which
happens quite a lot as I am doing translation work). At one point, I'll
start seeing redrawing artifacts (to explain : even though I switched
applications, the display still shows a black surface, or the
application which was on top of gedit at that time, and I have to
interact with the application for redraw to occur.

When I see this symptom, I know that within the next 50~100 window
switchings, I will crash.

The crash can even be triggered by clicking the window tab on the
application bar.

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to metacity in Ubuntu.
https://bugs.launchpad.net/bugs/1507764

Title:
  metacity crashed with signal 5 in _XEventsQueued() ; forcing gnome
  session to logout

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/1507764/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs


[Bug 1507764] Re: metacity crashed with signal 5 in _XEventsQueued() ; forcing gnome session to logout

2016-01-04 Thread Stephane Lapie
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 ; which I thought might take a toll on graphics
function).

As for the steps, I am sorry I can't provide any better information :
the only thing I can say is, it looks like something is accumulating
like a leak. At one point I will start seeing artifacts when switching
windows, seeing window redraw problems, and ultimately the last straw
will make stuff blow up. Thanks for the packages, I will try that right
away.

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to metacity in Ubuntu.
https://bugs.launchpad.net/bugs/1507764

Title:
  metacity crashed with signal 5 in _XEventsQueued() ; forcing gnome
  session to logout

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/1507764/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs


[Bug 1507764] Re: metacity crashed with signal 5 in _XEventsQueued() ; forcing gnome session to logout

2016-01-04 Thread Stephane Lapie
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 'alt-tab-thumbnails'

As for configuration, it seems I am still relying on CCSM (CompizConfig 
Settings Manager), which offers :
- Application Switcher
- Static Application Switcher (the one I use, which pops up with only icons)

Also, I don't think this is related but it feels like at times the
application switch is not instant (meaning, I need to wait a little bit
to be sure that it did switch, otherwise the keys I hit right after
Alt+Tab get processed by the previous application, which is kind of
annoying)

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to metacity in Ubuntu.
https://bugs.launchpad.net/bugs/1507764

Title:
  metacity crashed with signal 5 in _XEventsQueued() ; forcing gnome
  session to logout

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/1507764/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs


[Bug 1507764] Re: metacity crashed with signal 5 in _XEventsQueued() ; forcing gnome session to logout

2015-12-30 Thread Stephane Lapie
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 gnome-session[28277]: The error was 'BadRegion (invalid 
Region parameter)'.
Dec 30 23:49:59 archer gnome-session[28277]: (Details: serial 1686054464 
error_code 140 request_code 138 (XFIXES) minor_code 12)
Dec 30 23:49:59 archer gnome-session[28277]: (Note to programmers: normally, X 
errors are reported asynchronously;
Dec 30 23:49:59 archer gnome-session[28277]: that is, you will receive the 
error a while after causing it.
Dec 30 23:49:59 archer gnome-session[28277]: To debug your program, run it with 
the GDK_SYNCHRONIZE environment
Dec 30 23:49:59 archer gnome-session[28277]: variable to change this behavior. 
You can then get a meaningful
Dec 30 23:49:59 archer gnome-session[28277]: backtrace from your debugger if 
you break on the gdk_x_error() function.)

which led once apport was done writing the crash report :
Dec 30 23:54:51 archer gnome-session[28277]: gnome-session[28277]: WARNING: 
Application 'metacity.desktop' killed by signal 5
Dec 30 23:54:51 archer gnome-session[28277]: WARNING: Application 
'metacity.desktop' killed by signal 5
Dec 30 23:54:51 archer gnome-session[28277]: gnome-session[28277]: WARNING: App 
'metacity.desktop' respawning too quickly
Dec 30 23:54:51 archer gnome-session[28277]: WARNING: App 'metacity.desktop' 
respawning too quickly
Dec 30 23:54:51 archer gnome-session[28277]: Unrecoverable failure in required 
component metacity.desktop
Dec 30 23:54:51 archer gnome-session[28277]: gnome-session[28277]: CRITICAL: We 
failed, but the fail whale is dead. Sorry
Dec 30 23:54:51 archer gnome-session[28277]: CRITICAL: We failed, but the fail 
whale is dead. Sorry

>From what I tried, it seems like trying to run "metacity --replace"
before apport finishes killing the old instance does not work : once it
freezes and apport is writing its stuff, the whole session will go down.

Seriously, this regression is infuriating and makes Ubuntu barely usable for me.
I nearly stopped using Alt+Tab out of fear of losing work when switching 
between gedit and evince.

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to metacity in Ubuntu.
https://bugs.launchpad.net/bugs/1507764

Title:
  metacity crashed with signal 5 in _XEventsQueued() ; forcing gnome
  session to logout

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/1507764/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs


[Bug 1528896] [NEW] metacity crashed with signal 5 in _XEventsQueued() ; forcing gnome session to logout (#1507764 duplicate)

2015-12-23 Thread Stephane Lapie
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: Ubuntu 15.04
Package: metacity 1:3.14.3-1ubuntu7
ProcVersionSignature: Ubuntu 3.19.0-42.48-generic 3.19.8-ckt10
Uname: Linux 3.19.0-42-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.17.2-0ubuntu1.8
Architecture: amd64
CrashCounter: 1
CurrentDesktop: GNOME-Flashback:Unity
Date: Thu Dec 24 01:49:05 2015
ExecutablePath: /usr/bin/metacity
InstallationDate: Installed on 2010-01-30 (2153 days ago)
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027.1)
ProcCmdline: metacity
ProcEnviron:
 LANGUAGE=en_US:en
 PATH=(custom, user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/zsh
Signal: 5
SourcePackage: metacity
StacktraceTop:
 ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
 ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
 _XEventsQueued () from /usr/lib/x86_64-linux-gnu/libX11.so.6
 _XGetRequest () from /usr/lib/x86_64-linux-gnu/libX11.so.6
 XFixesCopyRegion () from /usr/lib/x86_64-linux-gnu/libXfixes.so.3
Title: metacity crashed with signal 5 in _XEventsQueued()
UpgradeStatus: Upgraded to vivid on 2015-09-05 (109 days ago)
UserGroups: adm admin audio cdrom dialout libvirtd lpadmin plugdev pulse 
pulse-access sambashare vboxusers video

** Affects: metacity (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-crash need-amd64-retrace third-party-packages vivid

** Information type changed from Private to Public

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to metacity in Ubuntu.
https://bugs.launchpad.net/bugs/1528896

Title:
  metacity crashed with signal 5 in _XEventsQueued() ; forcing gnome
  session to logout (#1507764 duplicate)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/1528896/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs


[Bug 1507764] Re: metacity crashed with signal 5 in _XEventsQueued() ; forcing gnome session to logout

2015-12-19 Thread Stephane Lapie
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 remain, and application windows redraw gets flaky.

Also, this looks strangely alike to :
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1455916

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to metacity in Ubuntu.
https://bugs.launchpad.net/bugs/1507764

Title:
  metacity crashed with signal 5 in _XEventsQueued() ; forcing gnome
  session to logout

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/1507764/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs


[Bug 1507764] Re: metacity crashed with signal 5 in _XEventsQueued() ; forcing gnome session to logout

2015-10-20 Thread Stephane Lapie
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 this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to metacity in Ubuntu.
https://bugs.launchpad.net/bugs/1507764

Title:
  metacity crashed with signal 5 in _XEventsQueued() ; forcing gnome
  session to logout

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/1507764/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs


[Bug 1507764] Re: metacity crashed with signal 5 in _XEventsQueued() ; forcing gnome session to logout

2015-10-20 Thread Stephane Lapie
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. (Especially mplayer/evince probably take a lot of
memory).

When metacity crashes, everything freezes while apport runs and writes its 
files, during which only the audio players and non graphical stuff keep running 
(if I am lucky I can SSH and force gedit to save my work), and once apport 
finishes, in a split second, every window just loses its decorations, and I am 
forced back to the login screen. Logs indeed indicate this :
/var/log/syslog.1:Oct 20 05:22:14 archer gnome-session[29421]: WARNING: App 
'metacity.desktop' respawning too quickly
/var/log/syslog.1:Oct 20 05:22:14 archer gnome-session[29421]: 
gnome-session[29421]: WARNING: App 'metacity.desktop' respawning too quickly

But I can't confirm with the bare eye that it tries to reload anything,
or what the respawn threshold is.

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to metacity in Ubuntu.
https://bugs.launchpad.net/bugs/1507764

Title:
  metacity crashed with signal 5 in _XEventsQueued() ; forcing gnome
  session to logout

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/1507764/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs


[Bug 1507764] Re: metacity crashed with signal 5 in _XEventsQueued() ; forcing gnome session to logout

2015-10-19 Thread Stephane Lapie
** Information type changed from Private to Public

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to metacity in Ubuntu.
https://bugs.launchpad.net/bugs/1507764

Title:
  metacity crashed with signal 5 in _XEventsQueued() ; forcing gnome
  session to logout

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/1507764/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs