aasen, thanks for the tip. unfortunately, changing owner did not fix my
problem.
i am trying to connect to a public wifi access point. i can connect
using my other laptop running vista. i used to be able to connect with
my laptop (asus eeepc, running ubuntu 8.10) until a few days ago when it
aasen, i am a newbie. could you please tell me the commands i need to
use to change the owner? much appreciated.
tinkerer
--
Gnome settings manager error to start desktop
https://bugs.launchpad.net/bugs/84876
You received this bug notification because you are a member of Ubuntu
Bugs, which is
okidoke, can do. from the command line (assuming you are in your home
directory), do:
sudo chown -R your_username_here .dbus
--
Gnome settings manager error to start desktop
https://bugs.launchpad.net/bugs/84876
You received this bug notification because you are a member of Ubuntu
Bugs, which
I got the same error message because ~/.dbus/ and its contents were for
some reason owned by root. Changing the owner resolved the problem.
--
Gnome settings manager error to start desktop
https://bugs.launchpad.net/bugs/84876
You received this bug notification because you are a member of Ubuntu
I have this (or something simila) on intrepid when trying to start nautilus
remotely via ssh with X-forwarding.
Don't know if it is a seperate bug (as it is on ibex) but anyhow I _have_
localhost set in my host file correctly.
--
Gnome settings manager error to start desktop
If anyone still interested: I got this error recently (15 min ago), and
by now have managed to resolve it.
The problem was in my /etc/hosts file - it was missing 127.0.0.1
localhost line. It was removed by Network Settings applet when I
tried to add an alias 127.0.0.1 testhost for my apache
Don't know, nadavkav:
I've not used Ubuntu for awhile.
Regards,
Robert
On Mon, Jun 23, 2008 at 9:52 AM, nadavkav [EMAIL PROTECTED] wrote:
i have reported similar bug:
https://bugs.launchpad.net/ubuntu/+source/gnome-system-tools/+bug/233980
please see if it is duplicate or not ?
--
Gnome
i have reported similar bug:
https://bugs.launchpad.net/ubuntu/+source/gnome-system-tools/+bug/233980
please see if it is duplicate or not ?
--
Gnome settings manager error to start desktop
https://bugs.launchpad.net/bugs/84876
You received this bug notification because you are a member of
the bug has a collection of different issues, the message just state
that it doesn't start as expected, everybody having the issue on hardy
should open new bugs so we triage those properly and figure what the
issue are there
** Changed in: control-center (Ubuntu)
Status: Confirmed =
Allright, I have this very same problem on three different machines.
Lots of people have it.
It's not a showstopper, but it's a scary thing to have in a stable release for
this many months.
Let's raise the priority, let's look into this.
Looks like a synchronization problem to me. Did anyone
On Sat, Apr 12, 2008 at 5:03 AM, Andrea Ratto [EMAIL PROTECTED]
wrote:
Looks like a synchronization problem to me. Did anyone have this on a
single core machine?
Yeah.
Also found a dupe:
https://bugs.launchpad.net/ubuntu/+bug/155164
Thanks, I marked it as such.
** Attachment added:
I'had the same problem (I think) 2 time for 5 Gnome doesn't start
properly. It's totaly random. We talk about this problem in a thread at
the francophone ubuntu forum. http://forum.ubuntu-
fr.org/viewtopic.php?id=172109
The message :
Il y a eu une erreur lors du démarrage du démon des
Got the same problem on two computers...
* Laptop ACER Aspire 3104 (lspcis attached)
* A desktop computer (homemade)
This problem seems to occurs randomly.
Restarting X corrects the problem.
Nothing new about this bug ?
TGZ file with (lspcis, dmesg, lsusb, uname, lsb_release...).
Best
Also, see bug #140469.
--
Gnome settings manager error to start desktop
https://bugs.launchpad.net/bugs/84876
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
I guess my solution is similar to j. Tole,
In my case, I had this error because my firewall guarddog doesn't keep its
settings at boot, and was filtering that.
You can verify it with iptables -L. To reload the rules at startup, I had to
add in /etc/rc.d/rc.local:
if [ -x /etc/rc.firewall ];
I was having this same problem as well on a friends computer I was
setting up with ubuntu Feisty on x86_64. This had happened over to
installs and usually after I had just installed a pile of software so I
did not know what was causing the problem however I was getting the
Original qoute that
Same problem here, Ubu Feisty.
/etc/network/interfaces
auto lo
iface lo inet loopback
auto eth0
iface eth0 inet dhcp
auto eth1
iface eth1 inet dhcp
---
[EMAIL PROTECTED]:~$ lsusb
Bus 005 Device 001: ID :
Bus 004 Device 001: ID :
Bus 003 Device 001: ID :
Bus 002
Same problem here, Ubu Feisty.
/etc/network/interfaces
auto lo
iface lo inet loopback
auto eth0
iface eth0 inet dhcp
auto eth1
iface eth1 inet dhcp
---
[EMAIL PROTECTED]:~$ lsusb
Bus 005 Device 001: ID :
Bus 004 Device 001: ID :
Bus 003 Device 001: ID :
Bus 002
I seem to be having a similar problem on an updated install of Feisty,
except that my GNOME is never slow to load---it loads with about the
same speed as in Edgy.
Here is what happens. If I login normally after booting, all is fine.
But say I boot up the computer and leave gdm running for a
I'm having the same problem on a fresh install of Feisty.When I tried sudo
ifup lo (like Shum), it reported that interface lo already configured. Pinging
my localhost did not return any errors either. I have attached the requested
information. Ignore the Microcode errors in dmesg, as I
hi everybody. I report the same behaviour with my laptop and desktop
computers with Ubuntu 6.10, with and without internet conection. I
haven't try derek's solution yet but I'll report about it.
** Attachment added: outputs
http://librarian.launchpad.net/7373139/outputs
--
Gnome settings
you need to have a working loopack, that's not a GNOME bug
--
Gnome settings manager error to start desktop
https://bugs.launchpad.net/bugs/84876
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
[EMAIL
I can confirm that this bug occurs for me as well, except I do get my
theme and background etc. I still have the long load time for gnome, and
the same gnome-settings message. I haven't tried disabling by touchpad,
however.
Attached is the output of the commands requested above.
** Attachment
bug has been confirmed
** Changed in: control-center (Ubuntu)
Status: Unconfirmed = Confirmed
--
Gnome settings manager error to start desktop
https://bugs.launchpad.net/bugs/84876
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for
Oh, oops. Forgot to run sudo ifup lo. Once that's done, my session is
back to normal. Possibly gnome-settings-daemon seems to use it for
communication; thus, a possible solution is to let NetworkManager manage
lo.
Just my $0.02
--
Gnome settings manager error to start desktop
Also, trimming my /etc/network/interfaces to
auto lo
iface lo inet loopback
does not make a difference.
--
Gnome settings manager error to start desktop
https://bugs.launchpad.net/bugs/84876
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for
Greetings, Derek:
I haven't upgraded to Feisty yet; and my ping localhost works. My
loopback device is fine. Yet, my system still hangs when I try to
access the GNOME Menu on occasion.
Thanks; and regards,
Robert
On 4/11/07, DerekBuranen [EMAIL PROTECTED] wrote:
Here's the real culprit.
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
not marking confirmed, there is not enough information and there is no
other user who confirmed having the bug
** Changed in: control-center (Ubuntu)
Importance: Undecided = Low
Assignee: (unassigned) = Ubuntu Desktop Bugs
Status: Confirmed = Unconfirmed
--
Gnome settings manager
Sorry for tooking so long, but I didn`t have time to boot here, and I
was using Feisty Fawn in another partition, which by the way is working
great.
** Attachment added: All info is in the attachment, files are ordered by name
exactly as the commands asked
** Changed in: Ubuntu
Sourcepackagename: None = control-center
Assignee: Brian Murray = (unassigned)
Status: Needs Info = Confirmed
--
Gnome settings manager error to start desktop
https://launchpad.net/bugs/84876
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Thanks for your bug report. Could you please add the output of 'lspci
-vv', 'lspci -vvn', 'lsusb' and 'dmesg' to your bug report as
attachments? Thanks in advance.
** Changed in: Ubuntu
Assignee: (unassigned) = Brian Murray
Status: Unconfirmed = Needs Info
--
Gnome settings manager
32 matches
Mail list logo
