[Bug 242312] Re: HARDY: Genome panel takes more than 10 min to load or do not load at all

2008-06-23 Thread dnielben
Yes, I had some smb server bookmarks in Nautilus. After removing them
the panel started working normally.

This is a duplicate bug report, you can close it.

Thanks

** Summary changed:

- HARDY: Genome panel takes more than 10 min to load or do not load at all
+ HARDY: Gnome panel takes more than 10 min to load or do not load at all

-- 
HARDY: Gnome panel takes more than 10 min to load or do not load at all
https://bugs.launchpad.net/bugs/242312
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 242312] Re: HARDY: Genome panel takes more than 10 min to load or do not load at all

2008-06-23 Thread dnielben

** Attachment added: "backtrace of gnome-panel"
   http://launchpadlibrarian.net/15532803/gdb-gnome-panel.txt

-- 
HARDY: Genome panel takes more than 10 min to load or do not load at all
https://bugs.launchpad.net/bugs/242312
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 242312] [NEW] HARDY: Genome panel takes more than 10 min to load or do not load at all

2008-06-23 Thread dnielben
Public bug reported:

Binary package hint: gnome-panel

It takes more than 10 min. to load gnome panel. and takes all my cpu
Nautilus works and I can start programs with no problems.

My system:

Dell D410 (laptop)
1Gb Ram
 >uname -a
Linux dnielben-laptop 2.6.24-19-386 #1 Wed Jun 18 14:09:56 UTC 2008 i686 
GNU/Linux

The problem start happening on Saturday 21 June 2008. As I update my
system in a daily basis, I assume this problem was introduced in the
last update, Friday 20 June 2008.

What I have tried until now with no success:

- Stop the trash applet
- stop gvfsd-trash
- Reset configuration settings of gnome
- Stop nautilus
- Stop nm-applet

I am attaching a backtrace of a session where the panel did not load at
all. I did suspend the execution of the panel manually.

** Affects: gnome-panel (Ubuntu)
 Importance: Undecided
 Status: New

-- 
HARDY: Genome panel takes more than 10 min to load or do not load at all
https://bugs.launchpad.net/bugs/242312
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 115616] Re: Device-mapper errors: dm-linear, lookup failed

2007-10-24 Thread dnielben
I had the same error when upgrading to gusty. My laptop had a feisty
version upgraded from drapper. I am going to remove evms to confirm the
workarround.

To upgrade I use the command "update-manager -d -c", this because when
opening the upgrade manager it did not detected the availability of the
new version.

My previous version of the kernel allows me to use my computer

uname -a
Linux dnielben-laptop 2.6.20-16-386 #2 Sun Sep 23 19:47:10 UTC 2007 i686 
GNU/Linux

I am posting just to confirm that this is a real problem and upgrade-
manager is not removing evms.

-- 
Device-mapper errors: dm-linear, lookup failed
https://bugs.launchpad.net/bugs/115616
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 9718] Re: [network-admin] GNOME network tool slow after applying changes

2007-09-24 Thread dnielben
I confirm this bug in Feisty. The bug still open and it should be
changed to critical (this bug (with others) is really killing my ubuntu-
laptop experience)

How to reproduce it:

1. Open the network-admin tool.

2. Set the wired interface (eth0) to dhcp.

3. Apply the changes or deactivate and activate the interface.

4. Wait for the "changing interface configuration" window to close

5. Run ifconfig in a terminal window. You don't have an ip configured.

6. After several minutes, more than 5, you will get finally an ip.

Work around:

You can force the interface to get an ip address using the command:

sudo dhclient eth0

It will get an ip address immediately

It seems that network-admin does not force the interface to negotiate an
ip address immediately after interface activation.

uname -a: Linux dnielben-laptop 2.6.20-16-386 #2 Fri Aug 31 00:51:58 UTC
2007 i686 GNU/Linux

>From syslog, reproducing the bug and the workaround:

Sep 24 18:43:54 dnielben-laptop dhclient: There is already a pid file 
/var/run/dhclient.eth0.pid with pid 28023
Sep 24 18:43:54 dnielben-laptop dhclient: killed old client process, removed 
PID file
Sep 24 18:43:54 dnielben-laptop dhclient: Internet Systems Consortium DHCP 
Client V3.0.4
Sep 24 18:43:54 dnielben-laptop dhclient: Copyright 2004-2006 Internet Systems 
Consortium.
Sep 24 18:43:54 dnielben-laptop dhclient: All rights reserved.
Sep 24 18:43:54 dnielben-laptop dhclient: For info, please visit 
http://www.isc.org/sw/dhcp/
Sep 24 18:43:54 dnielben-laptop dhclient: 
Sep 24 18:43:54 dnielben-laptop dhclient: Listening on 
LPF/eth0/00:14:22:fd:ae:82
Sep 24 18:43:54 dnielben-laptop dhclient: Sending on   
LPF/eth0/00:14:22:fd:ae:82
Sep 24 18:43:54 dnielben-laptop dhclient: Sending on   Socket/fallback
Sep 24 18:43:54 dnielben-laptop dhclient: DHCPRELEASE on eth0 to 193.104.32.84 
port 67
Sep 24 18:43:54 dnielben-laptop avahi-autoipd(eth0)[28256]: Found user 
'avahi-autoipd' (UID 110) and group 'avahi-autoipd' (GID 116).
Sep 24 18:43:54 dnielben-laptop avahi-autoipd(eth0)[28256]: Successfully called 
chroot().
Sep 24 18:43:54 dnielben-laptop avahi-autoipd(eth0)[28256]: Successfully 
dropped root privileges.
Sep 24 18:43:54 dnielben-laptop avahi-autoipd(eth0)[28256]: fopen() failed: 
Permission denied
Sep 24 18:43:54 dnielben-laptop avahi-autoipd(eth0)[28256]: Starting with 
address 169.254.8.146
Sep 24 18:44:00 dnielben-laptop avahi-autoipd(eth0)[28256]: Callout BIND, 
address 169.254.8.146 on interface eth0
Sep 24 18:44:04 dnielben-laptop avahi-autoipd(eth0)[28256]: Successfully 
claimed IP address 169.254.8.146
Sep 24 18:44:04 dnielben-laptop avahi-autoipd(eth0)[28256]: fopen() failed: 
Permission denied
Sep 24 18:44:04 dnielben-laptop kernel: [215828.96] bridge-eth0: disabling 
the bridge
Sep 24 18:44:04 dnielben-laptop avahi-autoipd(eth0)[28256]: SIOCSIFFLAGS 
failed: Permission denied
Sep 24 18:44:04 dnielben-laptop avahi-autoipd(eth0)[28256]: Callout STOP, 
address 169.254.8.146 on interface eth0
Sep 24 18:44:04 dnielben-laptop avahi-autoipd(eth0)[28257]: client: RTNETLINK 
answers: No such process
Sep 24 18:44:04 dnielben-laptop dhclient: receive_packet failed on eth0: 
Network is down
Sep 24 18:44:04 dnielben-laptop kernel: [215828.972000] bridge-eth0: down
Sep 24 18:44:05 dnielben-laptop kernel: [215830.596000] bridge-eth0: enabling 
the bridge
Sep 24 18:44:05 dnielben-laptop kernel: [215830.596000] bridge-eth0: up
Sep 24 18:44:05 dnielben-laptop kernel: [215830.596000] ADDRCONF(NETDEV_UP): 
eth0: link is not ready
Sep 24 18:44:05 dnielben-laptop dhclient: There is already a pid file 
/var/run/dhclient.eth0.pid with pid 134993416
Sep 24 18:44:05 dnielben-laptop dhclient: Internet Systems Consortium DHCP 
Client V3.0.4
Sep 24 18:44:05 dnielben-laptop dhclient: Copyright 2004-2006 Internet Systems 
Consortium.
Sep 24 18:44:05 dnielben-laptop dhclient: All rights reserved.
Sep 24 18:44:05 dnielben-laptop dhclient: For info, please visit 
http://www.isc.org/sw/dhcp/
Sep 24 18:44:05 dnielben-laptop dhclient: 
Sep 24 18:44:06 dnielben-laptop NetworkManager: ^IGoing to sleep. 
Sep 24 18:44:06 dnielben-laptop NetworkManager: ^IWaking up from 
sleep. 
Sep 24 18:44:06 dnielben-laptop NetworkManager: ^IDeactivating 
device eth1. 
Sep 24 18:44:06 dnielben-laptop NetworkManager: ^Ieth1: Device is 
fully-supported using driver 'ipw2200'. 
Sep 24 18:44:06 dnielben-laptop NetworkManager: 
^Inm_device_init(): waiting for device's worker thread to start 
Sep 24 18:44:06 dnielben-laptop NetworkManager: 
^Inm_device_init(): device's worker thread started, continuing. 
Sep 24 18:44:06 dnielben-laptop NetworkManager: ^INow managing 
wireless (802.11) device 'eth1'. 
Sep 24 18:44:06 dnielben-laptop NetworkManager: ^IDeactivating 
device eth1. 
Sep 24 18:44:06 dnielben-laptop dhclient: Listening on 
LPF/eth0/00:14:22:fd:ae:82
Sep 24 18:44:06 dnielben-laptop dhclient: Sending on   
LPF/eth0/00:14:22:fd:ae:82
Sep 24 18