To reiterate, this only happens with Gnome regardless of login manager. I have KDE & XFCE installed as well which work just fine from either gdm or kdm. It happens on two desktops for me, but not my laptop anymore after a reinstall of Feisty. I've tried to isolate what triggers this to no avail. I know what doesn't trigger it.
It's not:
*related to nvidia card or binary drivers as I've seen this on an Intel i810 and an ATI Radeon 7500 Mobility using the ati driver
*related to user preferences, as I've created a new user and wiped my ~/.* and the problem still exists
It must be package related somewhere since when I reinstalled the Feisty Beta on my desktop, the problem was gone. I tried to be conservative about installing packages to isolate what caused the issue, but it just came back all of a sudden and I'm not sure what brought it.
For the record, I have a desktop that only has gnome and xfce which the problem appears on. I have another desktop with KDE, Xfce, and Gnome on, but the problem occurred when it was only Gnome.
alarm-queue.c:497 (load_alarms)
alarm-notify.c:393 (cal_opened_cb) file:///home/burner/.evolution/tasks/local/system - Calendar Status 0
alarm-queue.c:2057 (alarm_queue_add_client) - Posting a task
alarm-notify.c:393 (cal_opened_cb) file:///home/burner/.evolution/memos/local/system - Calendar Status 0
alarm-queue.c:2057 (alarm_queue_add_client) - Posting a task
alarm-queue.c:526 (load_alarms) - Setting Call backs
alarm-notify.c:349 (alarm_msg_received) - 0x80da798: Received at thread b45f3b90
alarm-queue.c:2008 (alarm_queue_add_async) - 0x80d7790
alarm-queue.c:560 (load_alarms_for_today) - From Wed Apr 11 07:58:26 2007
to Wed Apr 11 07:58:26 2007
alarm-queue.c:497 (load_alarms)
alarm-notify.c:337 (alarm_msgport_replied) - 0x80e18d0: Replied to GUI thread
alarm-queue.c:526 (load_alarms) - Setting Call backs
alarm-notify.c:337 (alarm_msgport_replied) - 0x80da798: Replied to GUI thread
alarm-notify.c:349 (alarm_msg_received) - 0x80e77e0: Received at thread b45f3b90
alarm-queue.c:2008 (alarm_queue_add_async) - 0x80dbb10
alarm-queue.c:560 (load_alarms_for_today) - From Wed Apr 11 07:58:26 2007
to Wed Apr 11 07:58:26 2007
alarm-queue.c:497 (load_alarms)
alarm-queue.c:526 (load_alarms) - Setting Call backs
alarm-notify.c:337 (alarm_msgport_replied) - 0x80e77e0: Replied to GUI thread
alarm-notify.c:393 (cal_opened_cb) contacts:/// - Calendar Status 0
alarm-queue.c:2057 (alarm_queue_add_client) - Posting a task
alarm-notify.c:349 (alarm_msg_received) - 0x80d8098: Received at thread b45f3b90
alarm-queue.c:2008 (alarm_queue_add_async) - 0x80d0300
alarm-queue.c:560 (load_alarms_for_today) - From Wed Apr 11 07:58:26 2007
to Wed Apr 11 07:58:26 2007
/var/log/messages:
---------------------------------------------------------------------------------
this file is waaaaaaaaaaay too long to post and I don't see anything interesting
/var/log/syslog:
---------------------------------------------------------------------------------
Apr 11 07:40:38 ymir syslogd 1.4.1#20ubuntu4: restart.
Apr 11 07:40:38 ymir anacron[11338]: Job `cron.daily' terminated
Apr 11 07:40:38 ymir anacron[11338]: Normal exit (1 job run)
Apr 11 07:54:20 ymir gconfd (burner-8766): Exiting
Apr 11 07:54:21 ymir gconfd (burner-12117): starting (version 2.18.0.1), pid 12117 user 'burner'
Apr 11 07:54:21 ymir gconfd (burner-12117): Resolved address "xml:readonly:/etc/gconf/gconf.xml.mandatory" to a read-only configuration source at position 0
Apr 11 07:54:21 ymir gconfd (burner-12117): Resolved address "xml:readwrite:/home/burner/.gconf" to a writable configuration source at position 1
Apr 11 07:54:21 ymir gconfd (burner-12117): Resolved address "xml:readonly:/etc/gconf/gconf.xml.defaults" to a read-only configuration source at position 2
Apr 11 07:54:21 ymir gconfd (burner-12117): Resolved address "xml:readonly:/var/lib/gconf/debian.defaults" to a read-only configuration source at position 3
Apr 11 07:54:21 ymir gconfd (burner-12117): Resolved address "xml:readonly:/var/lib/gconf/defaults" to a read-only configuration source at position 4
Apr 11 07:58:18 ymir gconfd (burner-12117): Resolved address "xml:readwrite:/home/burner/.gconf" to a writable configuration source at position 0
Apr 11 07:58:21 ymir NetworkManager: <information>^IUpdating allowed wireless network lists.
Apr 11 07:58:21 ymir NetworkManager: <WARNING>^I nm_dbus_get_networks_cb (): error received: org.freedesktop.NetworkManagerInfo.NoNetworks - There are no wireless networks stored..
Apr 11 08:09:01 ymir /USR/SBIN/CRON[12606]: (root) CMD ( [ -d /var/lib/php5 ] && find /var/lib/php5/ -type f -cmin +$(/usr/lib/php5/maxlifetime) -print0 | xargs -r -0 rm)
Apr 11 08:17:01 ymir /USR/SBIN/CRON[12813]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
PLEASE HELP! I have found no workaround to this other than reinstalling and hoping it doesn't come back. If you need more info, ask. If we can fix this before Feisty Final, it would be ideal!
I have this same bug. Screenshot: http:// picasaweb. google. com/xburnerx/ UbuntuLinuxScre enshots/ photo#505183924 0363084114
To reiterate, this only happens with Gnome regardless of login manager. I have KDE & XFCE installed as well which work just fine from either gdm or kdm. It happens on two desktops for me, but not my laptop anymore after a reinstall of Feisty. I've tried to isolate what triggers this to no avail. I know what doesn't trigger it.
It's not:
*related to nvidia card or binary drivers as I've seen this on an Intel i810 and an ATI Radeon 7500 Mobility using the ati driver
*related to user preferences, as I've created a new user and wiped my ~/.* and the problem still exists
It must be package related somewhere since when I reinstalled the Feisty Beta on my desktop, the problem was gone. I tried to be conservative about installing packages to isolate what caused the issue, but it just came back all of a sudden and I'm not sure what brought it.
For the record, I have a desktop that only has gnome and xfce which the problem appears on. I have another desktop with KDE, Xfce, and Gnome on, but the problem occurred when it was only Gnome.
Related bugs: /bugs.launchpad .net/ubuntu/ +bug/89022 /bugs.launchpad .net/ubuntu/ +source/ gtk-qt- engine/ +bug/83152 /bugs.launchpad .net/ubuntu/ +source/ gtk-qt- engine/ +bug/66124 /bugs.launchpad .net/ubuntu/ +source/ control- center/ +bug/61381 /bugs.launchpad .net/ubuntu/ +source/ control- center/ +bug/84876
*https:/
*https:/
*https:/
*https:/
*https:/
~/.xsession-errors: ------- ------- ------- ------- ------- ------- ------- ------- ------- ------- ---- PreSession/ Default: Registering your session with wtmp and utmp PreSession/ Default: running: /usr/X11R6/ bin/sessreg -a -w /var/log/wtmp -u /var/run/utmp -x "/var/lib/ gdm/:0. Xservers" -h "" -l ":0" "burner" MANAGER= local/ymir: /tmp/.ICE- unix/12130 1001/socket
-------
/etc/gdm/
/etc/gdm/
/etc/gdm/Xsession: Beginning session setup...
SESSION_
esd: Esound sound daemon already running or stale UNIX socket
/tmp/.esd-
This socket already exists indicating esd is already running.
Exiting...
(gnome- session: 12130): GLib-GObject- CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed open-terminal extension alarm-notify- Message: Setting timeout for 57697 1176357600 1176299903 alarm-notify- Message: Thu Apr 12 00:00:00 2007
Window manager warning: "" found in configuration database is not a valid value for keybinding "toggle_shaded"
Initializing nautilus-
Initializing gnome-mount extension
seahorse nautilus module initialized
evolution-
evolution-
evolution- alarm-notify- Message: Wed Apr 11 07:58:23 2007
(evolution- alarm-notify: 12247): libecal-WARNING **: e-cal.c:318: Unexpected response channel_ setup) - Channel Setup midnight_ refresh) - Refresh at Thu Apr 12 00:00:00 2007
alarm-notify.c:368 (alarm_notify_new) - Alarm Notify New
alarm-notify.c:304 (alarm_
alarm-notify.c:243 (alarm_notify_init) - Initing Alarm Notify
alarm-queue.c:1875 (alarm_queue_init)
alarm-queue.c:218 (queue_
alarm-notify.c:220 (load_calendars) - Loading Calendar file:// /home/burner/ .evolution/ calendar/ local/system notify_ add_calendar) file:// /home/burner/ .evolution/ calendar/ local/system - Calendar Open Async... 0x80d02c0 notify_ add_calendar) contacts:/// - Calendar Open Async... 0x80d0300 //dburanen; <email address hidden> /;personal/ Calendar notify_ add_calendar) exchange: //dburanen; <email address hidden> /;personal/ Calendar - Calendar Open Async... 0x80d5b10 alarm-notify: 12247): libecal-WARNING **: e-cal.c:318: Unexpected response /home/burner/ .evolution/ tasks/local/ system notify_ add_calendar) file:// /home/burner/ .evolution/ tasks/local/ system - Calendar Open Async... 0x80d7790 //dburanen; <email address hidden> /;personal/ Tasks notify_ add_calendar) exchange: //dburanen; <email address hidden> /;personal/ Tasks - Calendar Open Async... 0x80d9eb0 /home/burner/ .evolution/ memos/local/ system notify_ add_calendar) file:// /home/burner/ .evolution/ memos/local/ system - Calendar Open Async... 0x80dbb10 /home/burner/ .evolution/ calendar/ local/system - Calendar Status 0 queue_add_ client) - Posting a task //dburanen; <email address hidden> /;personal/ Calendar - Calendar Status 3 //dburanen; <email address hidden> /;personal/ Tasks - Calendar Status 3 msg_received) - 0x80e18d0: Received at thread b45f3b90 queue_add_ async) - 0x80d02c0 for_today) - From Wed Apr 11 07:58:26 2007
alarm-notify.c:456 (alarm_
alarm-notify.c:220 (load_calendars) - Loading Calendar contacts:///
alarm-notify.c:456 (alarm_
alarm-notify.c:220 (load_calendars) - Loading Calendar exchange:
alarm-notify.c:456 (alarm_
alarm-notify.c:220 (load_calenda
(evolution-
rs) - Loading Calendar file://
alarm-notify.c:456 (alarm_
alarm-notify.c:220 (load_calendars) - Loading Calendar exchange:
alarm-notify.c:456 (alarm_
alarm-notify.c:220 (load_calendars) - Loading Calendar file://
alarm-notify.c:456 (alarm_
alarm-notify.c:393 (cal_opened_cb) file://
alarm-queue.c:2057 (alarm_
alarm-notify.c:393 (cal_opened_cb) exchange:
alarm-notify.c:393 (cal_opened_cb) exchange:
alarm-notify.c:349 (alarm_
alarm-queue.c:2008 (alarm_
alarm-queue.c:560 (load_alarms_
to Wed Apr 11 07:58:26 2007
alarm-queue.c:497 (load_alarms) /home/burner/ .evolution/ tasks/local/ system - Calendar Status 0 queue_add_ client) - Posting a task /home/burner/ .evolution/ memos/local/ system - Calendar Status 0 queue_add_ client) - Posting a task msg_received) - 0x80da798: Received at thread b45f3b90 queue_add_ async) - 0x80d7790 for_today) - From Wed Apr 11 07:58:26 2007
alarm-notify.c:393 (cal_opened_cb) file://
alarm-queue.c:2057 (alarm_
alarm-notify.c:393 (cal_opened_cb) file://
alarm-queue.c:2057 (alarm_
alarm-queue.c:526 (load_alarms) - Setting Call backs
alarm-notify.c:349 (alarm_
alarm-queue.c:2008 (alarm_
alarm-queue.c:560 (load_alarms_
to Wed Apr 11 07:58:26 2007
alarm-queue.c:497 (load_alarms) msgport_ replied) - 0x80e18d0: Replied to GUI thread msgport_ replied) - 0x80da798: Replied to GUI thread msg_received) - 0x80e77e0: Received at thread b45f3b90 queue_add_ async) - 0x80dbb10 for_today) - From Wed Apr 11 07:58:26 2007
alarm-notify.c:337 (alarm_
alarm-queue.c:526 (load_alarms) - Setting Call backs
alarm-notify.c:337 (alarm_
alarm-notify.c:349 (alarm_
alarm-queue.c:2008 (alarm_
alarm-queue.c:560 (load_alarms_
to Wed Apr 11 07:58:26 2007
alarm-queue.c:497 (load_alarms) msgport_ replied) - 0x80e77e0: Replied to GUI thread queue_add_ client) - Posting a task msg_received) - 0x80d8098: Received at thread b45f3b90 queue_add_ async) - 0x80d0300 for_today) - From Wed Apr 11 07:58:26 2007
alarm-queue.c:526 (load_alarms) - Setting Call backs
alarm-notify.c:337 (alarm_
alarm-notify.c:393 (cal_opened_cb) contacts:/// - Calendar Status 0
alarm-queue.c:2057 (alarm_
alarm-notify.c:349 (alarm_
alarm-queue.c:2008 (alarm_
alarm-queue.c:560 (load_alarms_
to Wed Apr 11 07:58:26 2007
/var/log/messages: ------- ------- ------- ------- ------- ------- ------- ------- ------- ------- ----
-------
this file is waaaaaaaaaaay too long to post and I don't see anything interesting
/var/log/syslog: ------- ------- ------- ------- ------- ------- ------- ------- ------- ------- ---- /etc/gconf/ gconf.xml. mandatory" to a read-only configuration source at position 0 /home/burner/ .gconf" to a writable configuration source at position 1 /etc/gconf/ gconf.xml. defaults" to a read-only configuration source at position 2 /var/lib/ gconf/debian. defaults" to a read-only configuration source at position 3 /var/lib/ gconf/defaults" to a read-only configuration source at position 4 /home/burner/ .gconf" to a writable configuration source at position 0 ^IUpdating allowed wireless network lists. get_networks_ cb (): error received: org.freedesktop .NetworkManager Info.NoNetworks - There are no wireless networks stored.. CRON[12606] : (root) CMD ( [ -d /var/lib/php5 ] && find /var/lib/php5/ -type f -cmin +$(/usr/ lib/php5/ maxlifetime) -print0 | xargs -r -0 rm) CRON[12813] : (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
-------
Apr 11 07:40:38 ymir syslogd 1.4.1#20ubuntu4: restart.
Apr 11 07:40:38 ymir anacron[11338]: Job `cron.daily' terminated
Apr 11 07:40:38 ymir anacron[11338]: Normal exit (1 job run)
Apr 11 07:54:20 ymir gconfd (burner-8766): Exiting
Apr 11 07:54:21 ymir gconfd (burner-12117): starting (version 2.18.0.1), pid 12117 user 'burner'
Apr 11 07:54:21 ymir gconfd (burner-12117): Resolved address "xml:readonly:
Apr 11 07:54:21 ymir gconfd (burner-12117): Resolved address "xml:readwrite:
Apr 11 07:54:21 ymir gconfd (burner-12117): Resolved address "xml:readonly:
Apr 11 07:54:21 ymir gconfd (burner-12117): Resolved address "xml:readonly:
Apr 11 07:54:21 ymir gconfd (burner-12117): Resolved address "xml:readonly:
Apr 11 07:58:18 ymir gconfd (burner-12117): Resolved address "xml:readwrite:
Apr 11 07:58:21 ymir NetworkManager: <information>
Apr 11 07:58:21 ymir NetworkManager: <WARNING>^I nm_dbus_
Apr 11 08:09:01 ymir /USR/SBIN/
Apr 11 08:17:01 ymir /USR/SBIN/
PLEASE HELP! I have found no workaround to this other than reinstalling and hoping it doesn't come back. If you need more info, ask. If we can fix this before Feisty Final, it would be ideal!