> I would be happy to provide a backtrace, but I just don't know how
> to do it with gnome-settings-daemon: how/when should I launch it?
I don't think it's required to provide a backtrace any more. The bug
has been merged with #706330 which already has a backtrace.
For future bug reports: http://
Hi guys,
I would be happy to provide a backtrace, but I just don't know how to do it
with gnome-settings-daemon: how/when should I launch it?
It seems to be launched when gdm starts...
(and yes: I am a noob: I never did a backtrace before :-))
Regards,
Sam
reassign 709946 gtk3-engines-unico
forcemerge 706330 706330
thanks
Am 04.06.2013 02:21, schrieb Marco:
>> You are using the unico GTK engine which doesn't work with gtk 3.8 [1].
>>
>> Please use the Adwaita theme until unico is fixed.
>
> Thanks. That workaround helped. Seems like this bug is the
> You are using the unico GTK engine which doesn't work with gtk 3.8 [1].
>
> Please use the Adwaita theme until unico is fixed.
Thanks. That workaround helped. Seems like this bug is then a
duplicate of #706330.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subj
Am 04.06.2013 00:56, schrieb Marco:
> I deactivated the option “Disable touchpad while typing” as
> mentioned in bug #697427 but it still crashes. These are my
> settings:
>
> $ gsettings list-recursively org.gnome.settings-daemon.peripherals.touchpad
> org.gnome.settings-daemon.peripherals.touchp
I deactivated the option “Disable touchpad while typing” as
mentioned in bug #697427 but it still crashes. These are my
settings:
$ gsettings list-recursively org.gnome.settings-daemon.peripherals.touchpad
org.gnome.settings-daemon.peripherals.touchpad disable-while-typing false
org.gnome.settings
Well, after hours of testing, this bug is related to
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=697427
Setting "Disable touchpad while typing" breaks the desktop on next session
startIt is 100% reproductible
Any help will be appreciated...
Regards,
Sam
Package: gnome-settings-daemon
Version: 3.4.2+git20121218.7c1322-3
Followup-For: Bug #709946
I think I am affected by the same bug.
It is very serious because gnome is unusable as it won't start (after the oops
dialog the session is automatically closed)
The bug seems to be reproductible as soon
Package: gnome-settings-daemon
Version: 3.4.2+git20121218.7c1322-3
Severity: important
Dear Maintainer,
* What led up to the situation?
After a system update logging into the GUI from gdm starts the
window manager and some other services, then displays the “Oh no!
Something has gone wrong” sc
9 matches
Mail list logo
