desktop loads incredibly slow after todays upgrade and wireless doesn' t come up automatically

[Casual Jim]

I also get a bug report offered for openoffice

System: Linux 2.6.20-11-generic #2 SMP Thu Mar 15 03:43:56 UTC 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 70200000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Human
Icon Theme: nuoveXT-1.6

Memory status: size: 3956736 vsize: 3956736 resident: 552960 share: 458752 rss: 552960 rss_rlim: 18446744073709551615
CPU usage: start_time: 1174097015 rtime: 0 utime: 0 stime: 0 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/libexec/evolution-data-server-1.10'

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
(no debugging symbols found)
0x00002b4cb023db8a in wait4 () from /lib/libc.so.6
#0 0x00002b4cb023db8a in wait4 () from /lib/libc.so.6
#1 0x0000000000407ef1 in ?? ()
#2 0x000000000040816d in ?? ()
#3 0x0000000000404116 in ?? ()
#4 0x000000000040331e in ?? ()
#5 0x00000000004042c9 in ?? ()
#6 0x0000000000409a76 in ?? ()
#7 0x00002b4cb01c58e4 in __libc_start_main () from /lib/libc.so.6
#8 0x0000000000402149 in ?? ()
#9 0x00007ffffab1c638 in ?? ()
#10 0x0000000000000000 in ?? ()
The program is running. Quit anyway (and detach it)? (y or n) [answered Y; input not from terminal]

----------- .xsession-errors ---------------------
(evolution-alarm-notify:5945): libecal-WARNING **: e-cal.c:1128: Could not activate calendar factory (OAFIID:GNOME_Evolution_Exchange_Connector_CalFactory:1.2)
Async... 0x6de4e0
alarm-notify.c:220 (load_calendars) - Loading Calendar exchange://ivan;auth=Basic@FIJI/;personal/Tasks
alarm-notify.c:220 (load_calendars) - Loading Calendar file:///home/ivan/.evolution/memos/local/system
alarm-notify.c:456 (alarm_notify_add_calendar) file:///home/ivan/.evolution/memos/local/system - Calendar Open Async... 0x6ddd00
alarm-notify.c:274 (alarm_notify_finalize) - Finalize
 alarm-notify.c:259 (dequeue_client) - Removing client 0x68c300
 alarm-queue.c:2167 (alarm_queue_remove_client) - Posting a task
alarm-notify.c:259 (dequeue_client) - Removing client 0x6d0a60
 alarm-queue.c:2167 (alarm_queue_remove_client) - Posting a task
alarm-notify.c:259 (dequeue_client) - Removing client 0x6de4e0
 alarm-queue.c:2167 (alarm_queue_remove_client) - Posting a task
alarm-notify.c:259 (dequeue_client) - Removing client 0x6ddd00
 alarm-queue.c:2167 (alarm_queue_remove_client) - Posting a task
alarm-queue.c:1946 (alarm_queue_done)
--------------------------------------------------

ProblemType: Bug
Architecture: amd64
Date: Sat Mar 17 16:12:40 2007
DistroRelease: Ubuntu 7.04
Uname: Linux cuba 2.6.20-11-generic #2 SMP Thu Mar 15 03:43:56 UTC 2007 x86_64 GNU/Linux

[Sebastien Bacher (seb128)]

Thanks for taking the time to report this bug. Unfortunately we can't fix it, because your description didn't include enough information. You may find it helpful to read "How to report bugs effectively" <http://www.chiark.greenend.org.uk/~sgtatham/bugs.html>. We'd be grateful if you would then provide a more complete description of the problem.

 We have instructions on debugging some types of problems. <http://wiki.ubuntu.com/DebuggingProcedures> Thanks!

[Casual Jim (ivan-flanders)]

I figured out what seems to cause the problem and I can reproduce it.
It has to do with the new network-manager and/or restricted-manager
The delay is caused because my wireless needs to connect first to the access point, but before it does that it first needs to work out that there is an access point, wpa, etc.

I'm using a Dell M90 x64 dual core laptop with an NVidia card and ipw3945ABG wireless drivers

To reproduce the delay (and it is really a delay 1-4 min depending from boot to boot)
boot a laptop without being connected to a wired network
login .. start waiting

[Alexander Butenko (avb)]

Same here.

Quick fix is to associate 127.0.0.1 with a hostname in /etc/hosts before network-manager start.
/etc/dbus-1/event.d/25NetworkManager:

d_start() {
   if [ ! -d $PIDDIR ]; then
      mkdir -p $PIDDIR
      chown $USER:$USER $PIDDIR
   fi

   # lets create temporary hosts for faster gnome startup
   echo "127.0.0.1 localhost localhost.localdomain `hostname`" > /etc/hosts

   start-stop-daemon --start --quiet --pidfile $PIDFILE \
      --user $USER --exec $DAEMON -- $DAEMON_OPTS --pid-file $PIDFILE

}

[Gareth Fitzworthington (mapping-gp-deactivatedaccount)]

The slow login/desktop bug appears to have been around for a while. The bug is reported in edgy & feisty and they are mostly unconfirmed and mostly of undecided importance. Although I'm very happy with feisty, I am finding this bug a bit bothersome so I thought I'd do some research through the bug archives.

I think this bug has been reported numerous times. The bug list that follows, I think are reports of effectively the same bug.

Bug #78263 - claims workaround (feisty)
Bug #78493 (edgy)
Bug #79466 (edgy)
Bug #80827 - claims workaround (edgy)
Bug #92997 - claims workaround (feisty)
Bug #94048 (feisty)
Bug #110616 (feisty?)
Bug #110775 (feisty)
Bug #110187 - reports slow desktop as a side effect of other network config issues. (feisty)
---------------
Bug #95264 - Maybe related (not clear) (feisty)
Bug #93447 - Maybe related (not clear) (edgy)
---------------
It seems most discussions are blaming this bug on one or more of:
Network-manager
avahi
hosts file
resolve file
static IP addresses
no network connection.

I can't vouch for the claimed workarounds - but I intend on investigating them further.

The person who solves this one will likely 'kill a number of bugs with one stone'.

I hope I'm not being too forward by presenting such a list but I am rather keen to see this bug solved. I hope this list helps to unify further discussion & prompts some further thought on the matter.

(note: I have posted it to all above bug reports so that all are in the loop)

[Gareth Fitzworthington (mapping-gp-deactivatedaccount)]

Add Bug #79661 (edgy) to above list.

[Kazakx (gevezex)]

Hi guys i have the same problem. I have a dell inspiron 6000 with an intel pro 2200 wireless card.
The problem started after I changed the domain for localhost.localdomain. Changing back to localhost.localdomain did not solve the problem. It looks like the system is searching for something and after a timeout (4 minutes) its resumes his things. The funny thing is that I cannot see any cpu load :( via ctrl-alt-F1 console access.

1 of 4-5 boots inititiates this problem. Then i do a hard reset and it will solve.
Also a logout an login again initiates the problem.
Very frustrating.

Who can fix this???