Public bug reported:
Binary package hint: xfce4-systemload-plugin
My xfce4-systemload-plugin stop working after an upgrade about a month
ago. This applet was running fine under 7.10, and seemed to work on
after I upgraded to Hardy 8.04, however, it failed to start and show up
in xfce panels after an upgrade more than a month ago.
Step to reproduce:
1. running xfce desktop
2. kill xfce4-panel process from a term
3. start xfce4-panel from the term
4. right click on the xfce panel, and select "Add New Item", then select
"System Load Monitor"
5. a dashed square quickly flash on xfce panel, and disappear, nothing added to
the panel
6. you can now see the error message from the term (sometimes it crashes not
only the
xfce4-systemload-plugin, but also the xfce4-panel:
The program 'xfce4-systemload-plugin' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadAlloc (insufficient resources for operation)'.
(Details: serial 197 error_code 11 request_code 53 minor_code 0)
(Note to programmers: normally, X errors are reported asynchronously;
that is, you will receive the error a while after causing it.
To debug your program, run it with the --sync command line
option to change this behavior. You can then get a meaningful
backtrace from your debugger if you break on the gdk_x_error() function.)
** Message: System Load Monitor: screen changed: 0
** Message: No valid plug window.
(xfce4-panel:14441): Gtk-CRITICAL **: gtk_socket_get_id: assertion
`GTK_WIDGET_ANCHORED (socket)' failed
** (xfce4-panel:14441): CRITICAL **: An item was unexpectedly removed:
"System Load Monitor".
(xfce4-panel:14441): GLib-GObject-CRITICAL **: g_type_interface_peek:
assertion `instance_class != NULL' failed
[1] Segmentation fault xfce4-panel
I am using xfce4-systemload-plugin version 1:0.4.2-1ubuntu3.
** Affects: xfce4-systemload-plugin (Ubuntu)
Importance: Undecided
Status: New
--
xfce4-systemload-plugin crashed with BadAlloc error
https://bugs.launchpad.net/bugs/218521
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
