After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 476552 - crash in Deskbar: try to run scim
crash in Deskbar: try to run scim
Status: RESOLVED DUPLICATE of bug 452746
Product: deskbar-applet
Classification: Deprecated
Component: general
unspecified
Other All
: High critical
: ---
Assigned To: Deskbar Applet Maintainer(s)
Deskbar Applet Maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2007-09-13 13:35 UTC by lixi915
Modified: 2007-09-17 15:16 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20



Description lixi915 2007-09-13 13:35:06 UTC
What were you doing when the application crashed?
try to run scim


Distribution: Ubuntu 7.10 (gutsy)
Gnome Release: 2.19.92 2007-09-04 (Ubuntu)
BugBuddy Version: 2.18.1

System: Linux 2.6.22-8-generic #1 SMP Thu Jul 12 15:59:45 GMT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 0 vsize: 0 resident: 0 share: 0 rss: 0 rss_rlim: 0
CPU usage: start_time: 0 rtime: 0 utime: 0 stime: 0 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 0



----------- .xsession-errors ---------------------
Creating backend ...
Loading socket FrontEnd module ...
Starting SCIM as daemon ...
Launching a SCIM process with x11...
Loading socket Config module ...
Creating backend ...
Loading x11 FrontEnd module ...
GTK Panel of SCIM 1.4.7
Starting SCIM ...
checking for valid crashreport now
checking for valid crashreport now
checking for valid crashreport now
(gnome-panel:8394): Gtk-WARNING **: gtk_widget_size_allocate(): attempt to allocate widget with width -8 and height 24
--------------------------------------------------
ImportError: could not import gnomecanvas
Comment 1 palfrey 2007-09-17 15:16:46 UTC
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.


*** This bug has been marked as a duplicate of 452746 ***