hi!
Can somebody of the gnome-team comment on the status of this, or at least
know what do you plan to do about it? :)
bugs upstream status are UNCONFIRM
The debug mode for the window could be a workaround in debian, although i
dont know the implications of setting the window to debug mode. Mayb
On Wed, 05 Sep 2012, Michael Biebl wrote:
> A related upstream discussion is at
> https://bugzilla.gnome.org/show_bug.cgi?id=677875
Indeed, exactely my words.
At some point in time I was told that "programs should save the
data when they are torn down" ... well, hopefully G-devs
start to think no
A related upstream discussion is at
https://bugzilla.gnome.org/show_bug.cgi?id=677875
I have to agree that the fail-whale is a rather annoying "feature".
Michael
--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
signature.asc
Descri
Hi!
When I was using gnome3 some months ago this bug annoyed me more than a
couple of times, I was able to work-around it by making the annoying
whale window to be a normal desktop window, so when it pop-ups you can
move it to a corner with the mouse and save your data before logging out.
To mak
One way to workaround this bug is to minimize (default shortcup alt+f9,
or alt+space then click minimize) the "somthing went wrong" window.
Works well here.
--
Bastien
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listma
Setting that key seems to have resolved the issue for me.
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
I started having this problem recently and to lend some credibility to
the PackageKit theory, it started about the same time I installed
PackageKit. I set the key as noted above and have not experienced the
issue as of yet. I set the key last evening though, so probably not
long enough time has p
Package: gnome-session
Followup-For: Bug #656762
Hi,
I just want to say that I'm too experiencing the issue of massive g-s-d
crashes with the "fail-whale" showing up every now and then.
For that crash window: it seems to be just a stupid application, so a ALT-F4
closes it a
On Mi, 25 Jan 2012, Michael Biebl wrote:
> I've been seeing more frequent crashes of g-s-d too in the last couple
Ahh, at least it is getting reproducible ;-)
> of days. The core dump I got also points into the direction of
> PackageKit. Could you disable the updates plugin for now (re-login, to
On 24.01.2012 05:45, Norbert Preining wrote:
> at the same time packagekit was updated from 0.7.1-2 -> 0.7.2-1
> which brought eg
> - glib: Convert libpackagekit-glib2 from dbus-glib to GDBus
I've been seeing more frequent crashes of g-s-d too in the last couple
of days. The core dump I got
On Di, 24 Jan 2012, Michael Biebl wrote:
> Can you also please either try to get a backtrace or a core dump.
> Instructions have been given in the previous emails.
Ok, I have now installed the -4 versions from testing, rebooted,
and still see the effect:
[ 400.36] gnome-settings-[3633]: segfa
Hi Michael,
On Di, 24 Jan 2012, Michael Biebl wrote:
> Btw, I can't really reproduce the issue, that a segfaulting
> gnome-settings-daemon causes the fail-whale to show up, that is the
> session is closed.
It does not happen *always*. I mean, the g-s-d *often crashes, but
only sometimes it is res
On 24.01.2012 03:41, Norbert Preining wrote:
> Triggered by this, gnome-session shows the "Oh something went wrong"
> screen making it impossible to save work, although the session is
> absolutely fine working, just the settings are not applied. I see
> all the work I was doing in the overview of
13 matches
Mail list logo
