Remove xserver-xgl, this did the trick for me.
--
gnome-settings-daemon crashes at login
https://bugs.launchpad.net/bugs/61381
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
holy thank you Peter,
Perfectly corrected my stupid laptop,,, :D
--
gnome-settings-daemon crashes at login
https://bugs.launchpad.net/bugs/61381
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
desktop-bug
Some step by step guide:
1) Network issue:
Try to ping localhost:
# ping localhost
If you can't have a response, so check network issues as described
above.
2) Sound issue
Go to sound preferences and uncheck ESD support, as described above.
Following these steps i was able to solve the problem
the bug is fixed in gutsy now
** Changed in: control-center (Ubuntu)
Importance: Undecided => Medium
Status: Needs Info => Fix Released
--
gnome-settings-daemon crashes at login
https://bugs.launchpad.net/bugs/61381
You received this bug notification because you are a member of Ubuntu
I've opened http://bugzilla.gnome.org/show_bug.cgi?id=439208 about the
error=0x0 bug
--
gnome-settings-daemon crashes at login
https://bugs.launchpad.net/bugs/61381
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs maili
Follow up...
Turned off Software Sound Mixing seemed to work at first. (No longer hung for
several minutes starting Gnome, no more error message)
Other strange things started happening though.. Clicking the shutdown button on
the panel caused it to freeze. Had to kill gnome panel.
Eventually I k
Same problem here on up to date Feisty.
Uncommenting the following had no effect for me.
auto lo
iface lo inet loopback
However, unchecking 'Enable Software Sound Mixing (ESD)' on the Sounds tab of
Sound Preferences seems to have solved the problem.
Gnome now starts quickly with no errors.
--
Ha! I found a solution in the ubuntuusers.de wiki:
in "/etc/hosts" append the line:
"""
127.0.0.1 localhost
"""
change to:
"""
127.0.0.1 localhost unix
"""
After restarting network, freeNX works fine ;)
--
gnome-settings-daemon crashes at login
https://bugs.launchpad.net/bugs/61381
You received
Possibly I have the same problem. I had freshly installed system. After
freeNX installation I get the error. I used the packages from
nomachines.com:
- NX Client for Linux
- NX Node for Linux
- NX Free Edition for Linux
I login via freeNX:
"""
Beim Starten des GNOME-Einstellungsdienstes ist ein
I had the same prooblem with the grey rectangle in the upper left corner
:-(
followed the solution in post 82: https://launchpad.net/ubuntu/+source
/control-center/+bug/61381/comments/82 and everything works again.
Greetz and THX,
S.
--
gnome-settings-daemon crashes at login
https://bugs.launc
Ah, the session dbus daemon wasn't running. From a shell, `dbus_launch`
went a long way toward fixing it.
--
gnome-settings-daemon crashes at login
https://bugs.launchpad.net/bugs/61381
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
-
FWIW, I had the same problem on Fedora Core 5 after an attempt to use a GUI
tool to change my hostname failed.
My /etc/hosts file was screwed up and it took several minutes for a terminal to
be displayed so I could fix it.
--
gnome-settings-daemon crashes at login
https://bugs.launchpad.net/bu
I *did* have problems, and my lo0 has been always working.
jaime
El lun, 16-04-2007 a las 15:10 +, Daniel Holbach escribió:
> Does anybody still have problems once 'lo' is working again?
>
--
Jaime Alemany
Lunático Astronomía S. L.
www.lunatico.es
TFN: +34 91 859 5567
FAX: +34 91 790 3589
I have no problems now that 'lo' is working
--
gnome-settings-daemon crashes at login
https://bugs.launchpad.net/bugs/61381
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
htt
Does anybody still have problems once 'lo' is working again?
--
gnome-settings-daemon crashes at login
https://bugs.launchpad.net/bugs/61381
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
desktop-bugs@lis
Here's the real culprit.
*ping localhost
This command wasn't working. Seems when I upgraded to Feisty and when I
was setting a static IP, I commented EVERYTHING in
/etc/network/interfaces. This is not good as the 'lo' or loopback
device is needed. I uncommented auto lo and the iface line for
me again. I just tried to install kubuntu, and it's more or less the
same scenario. The dialog doesn't appear this time, but there are also
stripes on the screen and it loads very very slow, and the mouse barely
moves.
--
gnome-settings-daemon crashes at login
https://bugs.launchpad.net/bugs/6138
I got the same error. I'm new to ubuntu.
My steps:
I downloaded ubuntu 6.10-desktop-i386
Inserted cdrom clicked "start or install ubuntu"
then the Ubutu-load-screen came up, normal so far
but then there a lightbrown background with blue small stripes came up over my
screen, after two minutes a di
Glad you got it working. Now we know the problem isn't just with the
live CD which is what I thought from my experience.
--
gnome-settings-daemon crashes at login
https://launchpad.net/bugs/61381
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listin
i actually installed from alternate cd bob
however i added interfaces and hosts lines like Peter Dinges said except not
the ipv6 lines like other people said and it works ok now
--
gnome-settings-daemon crashes at login
https://launchpad.net/bugs/61381
--
desktop-bugs mailing list
desktop-bugs
If you are using the Live CD kingcobra, try downloading and burning to
CD the alternate install .iso at
http://ubuntu-releases.cs.umn.edu/edgy/ubuntu-6.10-alternate-i386.iso
I was having exactly the problem you are describing, when I used the
alternate iso the installation went without a hitch.
B
I am using ubuntu edgy
gnome freezes after login every bootup for ages.
I get a brown screen for a few seconds, then a brown screen with a white
rectangle on the top-left corner for up to 2 minutes, and finally the following
error message (where the white rectangle was):
There was an error start
I was able to install with no problem with the alternative iso found at
http://ubuntu-releases.cs.umn.edu/edgy/ubuntu-6.10-alternate-i386.iso
--
gnome-settings-daemon crashes at login
https://launchpad.net/bugs/61381
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubun
I should note that the second box was running Debian Sarge successfully
on the same network before I wiped it clean with killdisk and attempting
to install Ubuntu.
--
gnome-settings-daemon crashes at login
https://launchpad.net/bugs/61381
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.c
I tried installing on a different box to eliminate possible hardware
causes. Same result even in safe mode.
--
gnome-settings-daemon crashes at login
https://launchpad.net/bugs/61381
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bu
More details ;-)
>From the Themes browser -> Details, i've found that only the windows
border themes (i.e., metacity) is responsive. Controls and icons are
stuck on the 'gnome default'.
P.S., I forgot to mention my attachment of the g-c-d crash:
http://librarian.launchpad.net/6897581/gnome-settin
I've tested a few of the above suggestions, i.e. disabling ESP, changing
Theme, and loggin in from a different account. That doesn't work. I'll
try a new account as well.
--
gnome-settings-daemon crashes at login
https://launchpad.net/bugs/61381
--
desktop-bugs mailing list
desktop-bugs@lists.u
I believe I have a similar problem to what is described here (though not all
symptoms appear identical).
When loggin in on my Gnome session, the only thing I get is a black screen and
a (functional) mouse cursor. 'ps' in a terminal shows that only
x-window-manager, ssh-agend, dbus-lauch & -daemo
I'm getting the same error message at the same time as described. Stops
at a tan background with bars at top and bottom with no icons on the
desktop. This is a clean install from an ISO on CD downloaded and
burned today for network install. My Internet connection is through a
LAN cable modem. S
Running the 6.10 release as a live CD I encountered exactly the same
problem/error message as is described in the initial posting to this
thread. I
* switched to a tty with ctl-alt-f1,
* ran sudo vi /etc/hosts,
* commented out the ::1 line in the ipv6 section,
* ran sudo gnome-session-manager
ok I will
--
gnome-settings-daemon crashes at login
https://launchpad.net/bugs/61381
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Sergey, that looks like a different problem, could you open a new bug?
--
gnome-settings-daemon crashes at login
https://launchpad.net/bugs/61381
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
In my case the problem was related to the ldap nss authentication. dbus-
daemon is running as messagebus user while libnss-ldap.conf is not
readable by anyone except root (600) - so dbus-daemon could not
authenticate. Changing permissions to 644 fixed the connection problem.
--
gnome-settings-dae
Same story here - g-s-d cannot start.
** (gnome-settings-daemon:7517): WARNING **: Unable to connect to dbus:
Failed to connect to socket /tmp/dbus-5kcxZTRe53: Connection refused
I am running feisty (on ppc).
--
gnome-settings-daemon crashes at login
https://launchpad.net/bugs/61381
--
deskto
I can confirm the problem being reported for VNC. The solution is this:
In your ~/.vnc/xstartup file put the following:
#!/bin/sh
vncconfig -iconic &
eval `dbus-launch --sh-syntax --exit-with-session`
gnome-session &
Then chmod 744 xstartup, and your problem should be fixed. Again, this
only
Here's a surefire way to reproduce this bug every time:
1. Install Edgy.
2. Install TightVNCServer
3. Start a VNC server session and connect to your Edgy box from another
machine using a VNC client. (I've been using realVNC's client)
You'll see the error upon connecting with VNC. The UI wil
One word to my previous comment ^^. My edgy was updated from dapper.
--
gnome-settings-daemon crashes at login
https://launchpad.net/bugs/61381
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
In my case it seems to be a network settings problem.
in my /etc/network/interfaces the lo device is configured as:
auto lo
after system startup the lo device is not alive. Starting gnome gives the well
known white box in the left bottom corner.
After
sudo ifconfig lo up
in
My problem was gnome-settings-daemon crashes at NXSERVER login, it is very
similar/linked to generic gnome-settings-daemon crashes at login.
Seems that several replies have been provided, read carefully all the
thread.
The hosts removal of ipv6 lines solution does not work for me and several
othe
I am not sure we are talking about the same bug in this thread anymore.
The problems described at the top of the thread all were solved by
editing /etc/hosts I think.
--
gnome-settings-daemon crashes at login
https://launchpad.net/bugs/61381
--
desktop-bugs mailing list
desktop-bugs@lists.ubunt
Hi all,
Disabling the ESD in Sound Preferences fixes NXSERVER logon problem
(white or grey square and long wait) for me too.
I also noticed that the ESD must be disabled in all user profiles you
use to connect using NXSERVER.
Cheers and thanks for your help.
Emmanuel
--
gnome-settings-daemon
Hi Sebastian,
I had the problem after a fresh install of Ubuntu 6.10 - Edgy Eft. I
also installed Cygwin/X on a windows machine, and, connecting via XDMCP
"XWin -fullscreen -query 192.168...", after successfully viewing the
login screen, keyed user and pass, and then, the long wait, the white
zone
With regard to the windows firewall having to be disabled, i have found that if
you add port exceptions for the following ports under the windows firewall
exceptions tab it will also work just as well as disabling the firewall... The
ports you need to open are: UDP 177, TCP 6000, TCP 16001
I was
It seems like to be something related with desktop themes.
I had same problem. But if I create a new desktop account and login, no
errors are shown.
I switch to the error account and changed theme to ubuntu default theme.
Now all works perfectly.
I was working around sounds too.
--
gnome-setti
Could anybody describe how to configure things to trigger that bug?
--
gnome-settings-daemon crashes at login
https://launchpad.net/bugs/61381
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Had the same problem just now after chmod ing my home dir, would take
5min or so to log in, before giving me the error above.
Going into preferences>sound>sounds and disabling ESD solved it.
--
gnome-settings-daemon crashes at login
https://launchpad.net/bugs/61381
--
desktop-bugs mailing list
Magically, turning off ESD has also worked for me... after changing my
windows client machine, I was back at the problem even with no firewall.
Quite an elusive bug!
Thanks,
jaime
El mar, 20-02-2007 a las 08:21 +, sleuth escribió:
> After spending all day fighting nomachines windows client,
summary:
similar problem here. cannot start GNOME or Beryl sessions on the machines,
splash screen hangs on Metacity.
Failsafe GNOME will boot, but kicks the above warning:
first error:
"Unable to determine the address of the message bus (try 'man dbus-launch' and
'man dbus-daemon' for help)"
After spending all day fighting nomachines windows client, freenx
server, nomachines nxserver, on opensuse 10.2 with gnome. I found that
turning off ESD in the gnome control center sound screen solved the
error described above. I had tried commenting the hosts file for IP6 and
it didn't work. Addit
Quote François2 I discovered by accident that the problem was ESD.
So if you go in the sound preferences and disable ESD, it may work
again
This did it for me, instantly the login was oké.
Thanks!!!
--
gnome-settings-daemon crashes at login
https://launchpad.net/bugs/61381
--
desktop-b
This is too weird! As per my prior message I followed up by adjusting:
/etc/hosts and /etc/network/interfaces and removing ::1 ip6-localhost
ip6-loopback -- actually I didn't adjust the later file since the lo loopback
reference was already there.
The result when I restarted the session was no
This error message just started for me yesterday, and as far as I'm aware I
only did two things:
1) I tried installing enlightenment -- but because it didn't work properly I
"completely" uninstalled it using Synaptic Package Manager.
2) in the same session I changed the theme of Gnome
After reb
that bug has many comment and is very confusing now, could anybody
describe some steps to trigger the problem?
--
gnome-settings-daemon crashes at login
https://launchpad.net/bugs/61381
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-
nt: Wednesday, January 17, 2007 12:23 PM
Subject: [Bug 61381] Re: gnome-settings-daemon crashes at login
This problem seems to be tied indeed to some value problems in /etc/hosts
and /etc/network/interfaces.
I removed ::1 ip6-localhost ip6-loopback from /etc/hosts and added the lo
loopback ref
This problem seems to be tied indeed to some value problems in /etc/hosts and
/etc/network/interfaces.
I removed ::1 ip6-localhost ip6-loopback from /etc/hosts and added the lo
loopback reference in /etc/network/interfaces.
I will test things separately to point out which one does what.
--
gno
More info: I've updated the Fedora box to FC 6 and now it gives me the
well-known error message about the GNOME Settings Daemon failing to
start. The desktop environment does come up about a minute later
however.
--
gnome-settings-daemon crashes at login
https://launchpad.net/bugs/61381
--
desk
I have the same symptoms when using Xming to set up an XDMCP connection
to my Ubuntu laptop on a local network. If I start up a VMWare Player
with a LiveCD version of Ubuntu I can start a new login, press F10 and
then log in to the laptop. Logging in to a Fedora station is no problem
with Xming as
I could not remotely log into X on Ubuntu with Cygwin until I shut down
the Windows XP firewall. I have not changed /etc/hosts in any way.
Suse works fine with the firewall in its normal state so it is clearly a
difference in the way Ubuntu sets up X that is causing the remote login
problem. I sus
This problem occurred for me because network-manager added a duplicate
"auto eth0" to the bottom of my /etc/network/interfaces file. After I
rebooted fine, I re-added the line and was able to get the error to
return...although it still seems a little slow... Maybe that's something
else.
--
gnome-
I had the same problem, mainly when using Nxserver to connect to my
computer remotely, and also from the second login on the computer
without a reboot.
I had an error in my /etc/hosts file, I fixed it, but I was still having
the problem. I discovered by accident that the problem was ESD. So if
you
Nope, Sebastien, I tried both of them separately and none is enough,
only the combination of the two things made it work.
I can post some more information but I found nothing not published here
before.
Cheers,
jaime
El vie, 08-12-2006 a las 10:16 +, Sebastien Bacher escribió:
> Does doing o
Does doing one of those only fix the problem? That's not likely to be a
combinaison of IPV6 and firewall, probably only one of them. That bug
starts to be confusing too, lot of comment from different people, I
would not be surprised if the current comments are not the same problem
than the crasher
I can confirm Jaime Alemany's solution to the problem. Disabling the
Windows firewall and commenting all IPv6 hosts from /etc/hosts did the
trick.
--
gnome-settings-daemon crashes at login
https://launchpad.net/bugs/61381
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists
Hi all,
I had one of the problems mentioned here (slow remote login via XDMCP
with X/Cygwin, white rectangle in the upper left of the screen, the
warning message
"There was an error starting the GNOME Settings Daemon.
Some things, such as themes, sounds, or background settings may not work
corr
I started a (lonely) thread at ubuntuforums:
http://ubuntuforums.org/showthread.php?t=290822
that details my problem.
One apparently unusual feature of my problem is that I see no errors anywhere
and am unable to post a backtrace.
I've had this happen on 5 successive rebuilds over the last few wee
Again, thank you Peter. I removed a line (::1 ip6-localhost
ip6-loopback) from my /etc/hosts file. Everything seems a ok now!
--
gnome-settings-daemon crashes at login
https://launchpad.net/bugs/61381
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/
Yes, that's it!
auto lo was missing from my /etc/network/interfaces
No it works fine.
Thnx, Peter
--
gnome-settings-daemon crashes at login
https://launchpad.net/bugs/61381
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Markus, I don't think your bug is a duplicate of this.
--
gnome-settings-daemon crashes at login
https://launchpad.net/bugs/61381
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Playing with /etc/hosts and /etc/network/interfaces didn't help me.
--
gnome-settings-daemon crashes at login
https://launchpad.net/bugs/61381
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Thank you Peter! Now everything runs normally on my computer. For some
reason the line "auto lo" was missing in my /etc/network/interfaces.
--
gnome-settings-daemon crashes at login
https://launchpad.net/bugs/61381
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.
gnome-settings-daemon starts if I set permissions on /etc/libnss-
ldap.conf to 644. It was, and should be, 600 becuase it contains
credentials. The lookups is done through nscd. But nscd randomly quits,
see bug #57214 and remote bug http://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=344563 .
This a
I also have this problem. I reported it as bug #70046, which is a duplicate I
guess.
Anyway here's a backtrace from bug-buddy.
** Attachment added: "Debug backtrace from bug-buddy"
http://librarian.launchpad.net/5067490/gnome-settings-daemon-bugreport.txt
--
gnome-settings-daemon crashes at
Inspired by kaptengu and Yerakon's comments, I started with a clean
/etc/hosts file (as there was an error message that the local host could
not be resolved). I also made sure that the loopback network interface
is loaded, as it was omitted in /etc/networking/interfaces. That did the
trick for me;
I don't understand.
What did you do to your /etc/network/interfaces?
Can you paste it here?
--
gnome-settings-daemon crashes at login
https://launchpad.net/bugs/61381
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Network? SSID? ok! I think that is not a bug...
Have You destroyed (manomitted) /etc/network/interfaces? :-)
I have replaced my /etc/network/interfaces and the "bug" it is resolved!
Sorry for my poor english... Regards.
--
gnome-settings-daemon crashes at login
https://launchpad.net/bugs/61381
Maybe I should add that my AP:s SSID is something else. I correct the
SSID after starting gnome. This makes the startup-time faster for me.
Maybe I should just change to WEP.
--
gnome-settings-daemon crashes at login
https://launchpad.net/bugs/61381
--
desktop-bugs mailing list
desktop-bugs@lis
I found out it has something to do with wpa_supplicant. When I am
outside my home WiFi-network, Gnome starts normally. I tried to change
my SSID in /etc/wpa_supplicant.conf to "blablabla", and then it also
worked fine.
--
gnome-settings-daemon crashes at login
https://launchpad.net/bugs/61381
--
Confirmed - I have this problem too.
--
gnome-settings-daemon crashes at login
https://launchpad.net/bugs/61381
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
I have the same problem. It takes 5 minutes to login. During login I see
a white box in the top left corner, after awhile it displays the error
message:
"There was an error starting the GNOME Settings Daemon.
Some things, such as themes, sounds, or background settings may not work
correctly.
The
I can confirm this bug too - I've just done a fresh install of Edgy from
CD (tried it twice) and I get it every time. However, here's the twist
for me:
I ONLY get it when I connect to my box through VNC. (I'm using TightVNC
- not sure if that matters) If I simply login at the console, there's
n
I was able to get this bug again on an other machine.
On my laptop I have a fresh install of Xubuntu.
I installed Ubuntu with sudo aptitude install ubuntu-desktop.
During the install several dependency problems arouse.
I continued with the installation, logged out of Xubuntu and tried to login to
I confirm this bug, on a fresh install of Edgy. Same symptoms, can't
find any solution.
--
gnome-settings-daemon crashes at login
https://launchpad.net/bugs/61381
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
I found a workaround, learned from my windows experience: I reinstalled
edgy and it works :-/
I know that's not a scientific way to resolve this bug, and I would have
liked to know what happened on the first install. I just used the same
procedure for both!
The only thing I can add: this is not a
In my case (Edgy RC1 Live-CD) there's no crash, only a message box.
Everything seems to work normally.
** Attachment added: "Screenshot Settings Daemon error"
http://librarian.launchpad.net/4930721/Screenshot-gnome-session.png
--
gnome-settings-daemon crashes at login
https://launchpad.net/bu
does running gnome-settings-daemon by hand after the startup works fine?
does running gnome-session from a debug session displays anything useful
on the command line?
--
gnome-settings-daemon crashes at login
https://launchpad.net/bugs/61381
--
desktop-bugs mailing list
desktop-bugs@lists.ubunt
>does running gnome-settings-daemon by hand after the startup works
fine?
yes. Following lines are written in the console:
Rrdb: "*Label.background" on line 243 overrides entry on line 170
xrdb: "*Text.background" on line 249 overrides entry on line 211
xrdb: "*Label.foreground" on line 255 ove
Sorry, I forgot the errors lines written by the last "gnome-settings-
daemon" command:
(gnome-settings-daemon:5108): GSwitchIt-WARNING **: Unable to connect to
dbus: Unable to determine the address of the message bus (try 'man dbus-
launch' and 'man dbus-daemon' for help)
** (gnome-settings-daem
I have this bug too. The behaviour is like markba's one. So I don't know
where I can find logs about the error reported in the message box. Can
experienced users guide me to find more informations?
scole evoked dbus: I found the error message (Did not receive a
reply...) in a dbus source code file
I was getting this previously too.
I had an idea that is had something to do with dbus.
--
gnome-settings-daemon crashes at login
https://launchpad.net/bugs/61381
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Maybe I'm stating the obvious, but this problem does not show when I
start a KDE session.
--
gnome-settings-daemon crashes at login
https://launchpad.net/bugs/61381
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
This is happening to me *every time* I try to login using XDMCP (from
Cygwin), up to the latest updates on my Edgy box as of this moment.
Edgy was dist-upgraded from Dapper 3 weeks ago. Before the upgrade,
everything worked.
Just to be clear: I can login, but the symptoms after that are much like
I logged in with a new user.
Still it took an awful lot of time.
Then this message appeared:
here was an error starting the GNOME Settings Daemon.
Some things, such as themes, sounds, or background settings may not work
correctly.
The last error message was:
Did not receive a reply. Possible ca
Bug-buddy did not give me a report when I logged in this time.
However, festival crashed and there was no window manager this time...
I'll try again if I can find some usefull information.
--
gnome-settings-daemon crashes at login
https://launchpad.net/bugs/61381
--
desktop-bugs mailing list
de
No, what you attached before with the title "gnome-settings-daemon bug
report", get the same while gnome-control-center-dbg is installed (it's
used automatically)
--
gnome-settings-daemon crashes at login
https://launchpad.net/bugs/61381
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.co
Is this what you are looking for?
Or how do I use gnome-control-center-dbg?
** Attachment added: "gdb output"
http://librarian.launchpad.net/4441483/gdb
--
gnome-settings-daemon crashes at login
https://launchpad.net/bugs/61381
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
http
Thanks for your bug. Could you get a backtrace with gnome-control-
center-dbg installed?
** Changed in: daemon (Ubuntu)
Sourcepackagename: daemon => control-center
Assignee: (unassigned) => Ubuntu Desktop Bugs
Status: Unconfirmed => Needs Info
--
gnome-settings-daemon crashes at logi
96 matches
Mail list logo
