Package: mirage
Version: 0.9.5.1-3
Severity: grave
Dear maintainer,
after the last update, mirage crashes immediately on startup:
$ mirage
/usr/lib/python2.7/dist-packages/mirage.py:608: Warning: The property
GtkWindow:allow-shrink is deprecated and shouldn't be used anymore. It will be
Okay, this seems to be a bug in Python?
There is also a very similar issue with reportbug at
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=758619 but that
doesn’t have an immediate solution either.
(Backtrace from gdb below)
Best,
Claudius
$ gdb --args python /usr/bin/mirage
GNU gdb
Hi,
following your hints, I just completely removed
/usr/share/pixmaps/hicolor/ - the window that the
application doesn't responds appears now in a
correct way and I'm able to just click abort
or kill.
Just one question, how can a broken image index crash Metacity or
at least making it nearly
Sven Arvidsson [EMAIL PROTECTED] wrote:
On Thu, 2007-08-30 at 12:20 +0200, Claudius Hubig wrote:
following your hints, I just completely removed
/usr/share/pixmaps/hicolor/ - the window that the
application doesn't responds appears now in a
correct way and I'm able to just click abort
or kill
Hi,
I just tested this problem with a completely new user and the error
still occurs. In the meanwhile, I changed the
script /etc/acpi/powerbtn.sh to killall metacity and metacity-dialog
processes. Thus, I can just press the power-button to solve the
problem, although this is - of course - not a
Morning,
Robert Freund [EMAIL PROTECTED] wrote:
Claudius 'x2017' Hubig wrote:
it happens regulary and reproducible while my system
passes 18h memtest86+-testing
How exactly is the 18h memory test related to this? How can you run
metacity while running memtest86+? Memtest86+ is some kind of
Hi,
manphiz [EMAIL PROTECTED] wrote:
Some search work at http://bugzilla.gnome.org shows no similar
report, and as it is unreproducible anywhere, there's no reason for
the upstream or Debian maintainer to address such bug, which doesn't
prevent the possibility for the bug's silent disappearance
Hi,
I now tested it with Kernel 2.6.21, but hat the same result as
before: Keyboard and mouse input is blocked, killing Metacity helps.
Then, I removed libc6-i686, but that didn't solve the problem neither.
Additionally, the problem with aptitude doesn't occur here, it works
just fine.
Hi,
manphiz [EMAIL PROTECTED] wrote:
Thanks to curiosity, I updated my metacity from 1:2.14.5-4(testing)
to current unstable 1:2.18.5-1, and when encountering Force Quit
situation, everything works fine at my place: no lockup, no
non-responding, everything is fine.
Well, this bug doesn't
Hi,
I did as you told me and have now two new backtraces saved in the
files created by gdb's logging capacity. I hope they're better, but
I'm only a user, not a programmer and have not a single idea what
they mean - sorry.
You asked for a way to reproduce it: Well, I wrote it
in my first mail:
Hi,
Josselin Mouette [EMAIL PROTECTED] wrote:
Thanks for your input. Unfortunately I'm still not able to reproduce the
bug.
It would be very nice if either of you could install libgtk2.0-0-dbg,
rebuild the package with debugging symbols and obtain, when the lockup
occurs, a backtrace of both
Josselin Mouette [EMAIL PROTECTED] wrote:
Le dimanche 03 juin 2007 à 20:24 +0200, Claudius 'x2017' Hubig a écrit :
To reproduce it, do the following:
* Crash an application to make it not answering; I use claws-mail and remove
the
network-connection while it is fetching mails, but it's
12 matches
Mail list logo
