[Desktop-packages] [Bug 1232454] Re: "Computer will suspend very soon because of inactivity." dialog when resuming from suspend
NotifyOSD has a fallback to alertbox function and maybe this is being called in stead of a normal notification. More info here: https://wiki.ubuntu.com/NotifyOSD#Fallback_alert_boxes The first lines read: "For cases where applications have expected the notification system to allow interactivity without checking whether it actually does, and cases where applications have expected the notification system to display a notification indefinitely, Notify OSD should show an alert box as a fallback." -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1232454 Title: "Computer will suspend very soon because of inactivity." dialog when resuming from suspend Status in Gnome Settings Daemon: Unknown Status in “gnome-settings-daemon” package in Ubuntu: Confirmed Bug description: After upgrading to 13.10 today, every time I unlock my computer after leaving it for a long time I get this prompt: -- Power Automatic suspend Computer will suspend very soon because of inactivity. -- However, the computer doesn't actually suspend. And even if I do this manually (which works) and then resume, the prompt is still there (and in that case, not true at all). This is ugly and seems broken! As suggested by the upstream Gnome bug report, this is an issue pertaining to Ubuntu's lack of systemd integration. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: ubuntu-desktop 1.304 ProcVersionSignature: Ubuntu 3.11.0-8.15-generic 3.11.1 Uname: Linux 3.11.0-8-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.12.5-0ubuntu1 Architecture: i386 Date: Sat Sep 28 15:32:42 2013 InstallationDate: Installed on 2012-08-03 (420 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 (20120423) MarkForUpload: True SourcePackage: ubuntu-meta UpgradeStatus: Upgraded to saucy on 2013-09-28 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/1232454/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1276572] [NEW] gnome control center crashes after switching between lock/display and security/privacy thru breadcrumb
Public bug reported: 1) Using ubuntu 13.10 64-bit 2) gnome-control-center: Installed: 1:3.6.3-0ubuntu45.2 Candidate: 1:3.6.3-0ubuntu45.2 Version table: *** 1:3.6.3-0ubuntu45.2 0 500 http://nl.archive.ubuntu.com/ubuntu/ saucy-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:3.6.3-0ubuntu44 0 500 http://nl.archive.ubuntu.com/ubuntu/ saucy/main amd64 Packages 3) expected behaviour: The control center doesn't crash 4) observed behaviour: The control center crashes/just closes. Steps to reproduce: 1. Open control center (doesn't matter how) 2. Go to Display & Lock 3. Turn the option to lock your screen to off 4. Go back to all settings by clicking on the breadcrumb 'All Settings' 5. Open Security & Privacy Terminal give these errors: ** (gnome-control-center:6324): CRITICAL **: gee_abstract_map_set: assertion 'self != NULL' failed ** (gnome-control-center:6324): CRITICAL **: gee_abstract_map_set: assertion 'self != NULL' failed ** (gnome-control-center:6324): CRITICAL **: gee_abstract_map_set: assertion 'self != NULL' failed ** (gnome-control-center:6324): CRITICAL **: gee_abstract_map_set: assertion 'self != NULL' failed ** (gnome-control-center:6324): CRITICAL **: gee_abstract_map_set: assertion 'self != NULL' failed ** (gnome-control-center:6324): CRITICAL **: gee_abstract_map_set: assertion 'self != NULL' failed ** (gnome-control-center:6324): CRITICAL **: gee_abstract_map_set: assertion 'self != NULL' failed ** (gnome-control-center:6324): CRITICAL **: gee_abstract_map_set: assertion 'self != NULL' failed 6. In the security tab change tik the box marked 'returning from blank screen' 7. Go back to all settings by clicking on the breadcrumb 'All Settings' Terminal give error: (gnome-control-center:2894): GLib-GObject-CRITICAL **: g_object_unref: assertion 'G_IS_OBJECT (object)' failed (gnome-control-center:2894): GLib-GObject-WARNING **: invalid unclassed pointer in cast to 'WhoopsieDaisyPreferences' (gnome-control-center:2894): Gtk-CRITICAL **: gtk_builder_get_object: assertion 'GTK_IS_BUILDER (builder)' failed (gnome-control-center:2894): Gtk-CRITICAL **: gtk_builder_get_object: assertion 'GTK_IS_BUILDER (builder)' failed (gnome-control-center:2894): Gtk-CRITICAL **: gtk_toggle_button_set_active: assertion 'GTK_IS_TOGGLE_BUTTON (toggle_button)' failed (gnome-control-center:2894): Gtk-CRITICAL **: gtk_toggle_button_set_active: assertion 'GTK_IS_TOGGLE_BUTTON (toggle_button)' failed 8. Go to Display & Lock 9. Turn the option to lock your screen back off 10. click on breadcrumb 'all settings' 11. Control Center disapears /crashes (if not directly repeat steps 5 - 10) Terminal gives errors: ** (gnome-control-center:2894): CRITICAL **: gee_abstract_map_set: assertion 'self != NULL' failed ** (gnome-control-center:2894): CRITICAL **: gee_abstract_map_set: assertion 'self != NULL' failed ** (gnome-control-center:2894): CRITICAL **: gee_abstract_map_set: assertion 'self != NULL' failed ** (gnome-control-center:2894): CRITICAL **: gee_abstract_map_set: assertion 'self != NULL' failed ** (gnome-control-center:2894): CRITICAL **: gee_abstract_map_set: assertion 'self != NULL' failed ** (gnome-control-center:2894): CRITICAL **: gee_abstract_map_set: assertion 'self != NULL' failed ** (gnome-control-center:2894): CRITICAL **: gee_abstract_map_set: assertion 'self != NULL' failed ** (gnome-control-center:2894): CRITICAL **: gee_abstract_map_set: assertion 'self != NULL' failed (gnome-control-center:2894): Gtk-CRITICAL **: gtk_tree_model_get_iter_first: assertion 'GTK_IS_TREE_MODEL (tree_model)' failed (gnome-control-center:2894): Gtk-CRITICAL **: gtk_tree_model_get: assertion 'GTK_IS_TREE_MODEL (tree_model)' failed (gnome-control-center:2894): Gtk-CRITICAL **: gtk_tree_model_iter_next: assertion 'GTK_IS_TREE_MODEL (tree_model)' failed (gnome-control-center:2894): GLib-GObject-WARNING **: invalid cast from 'GtkButtonBox' to 'WhoopsieDaisyPreferences' Segmentation fault (core dumped) ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gnome-control-center 1:3.6.3-0ubuntu45.2 ProcVersionSignature: Ubuntu 3.11.0-15.25-generic 3.11.10 Uname: Linux 3.11.0-15-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 Date: Wed Feb 5 13:17:40 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-01-30 (5 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MarkForUpload: True SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_gnome-control-center: activity-log-manager 0.9.7-0ubuntu4 deja-dup 27.3.1-0ubuntu1 gnome-control-center-datetime 13.10.0+13.10.20131023.2-0ubuntu1 gnome-control-center-signon 0.1.7~+13.10.20130724.1-0ubuntu1 gnome-control-center-unity1.3+13.10.20131004-0ubuntu1 ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug saucy
