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 548423 - crash in Deskbar: Tripple clicked the sear...
crash in Deskbar: Tripple clicked the sear...
Status: RESOLVED DUPLICATE of bug 548422
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: 2008-08-19 12:03 UTC by marques
Modified: 2008-08-19 12:09 UTC
See Also:
GNOME target: ---
GNOME version: 2.23/2.24



Description marques 2008-08-19 12:03:48 UTC
What were you doing when the application crashed?
Tripple clicked the search text while Google Code Search and twitter results were displayed.  Also briefly hovered over the right triangle / more button just prior to tripple clicking the search text.

The text was "what is this? some kind of joke?" .. I was testing the deskbar responses after enabling those two extensions and installing python-simplejson.


Distribution: Ubuntu 8.10 (intrepid)
Gnome Release: 2.23.90 2008-08-18 (Ubuntu)
BugBuddy Version: 2.23.90

System: Linux 2.6.26-5-generic #1 SMP Sun Aug 3 01:25:54 UTC 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10499906
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 (605876 sec old) ---------------------
** (gnome-session:7919): DEBUG: Starting app: /org/gnome/SessionManager/App9
** (gnome-session:7919): DEBUG: GsmAutostartApp: starting gnome-at-session.desktop: command=gnome-at-visual -s startup-id=106d9507c2a7c32748121854138223404900000079190007
** (gnome-session:7919): DEBUG: GsmAutostartApp: started pid:8273
** (gnome-session:7919): DEBUG: Starting app: /org/gnome/SessionManager/App30
** (gnome-session:7919): DEBUG: GsmAutostartApp: starting beagled.desktop: command=beagled startup-id=106d9507c2a7c32748121854138224290600000079190026
** (gnome-session:7919): WARNING **: Could not launch application 'beagled.desktop': Unable to start application: Failed to execute child process "beagled" (No such file or directory)
** (gnome-session:7919): DEBUG: Starting app: /org/gnome/SessionManager/App31
(gnome-session:7919): GLib-WARNING **: GError set over the top of a previous GError or uninitialized memory.
This indicates a bug in someone's code. You must ensure an error is NULL before it's set.
The overwriting error message was: Key file contains key 'Terminal' which has value that cannot be interpreted.
(gnome-login-sound:8254): EggSMClient-WARNING **: Failed to connect to the session manager: IO error occured opening connection
--------------------------------------------------
Traceback (most recent call last):
  • File "/usr/lib/python2.5/site-packages/deskbar/ui/cuemiac/CuemiacTreeView.py", line 260 in __on_query_tooltip
    markup = action.get_tooltip (qstring)
  • File "/usr/lib/deskbar-applet/modules-2.20-compatible/twitter.py", line 154 in get_tooltip
    return _("Update your %s account with the message:\n\n\t<i>%s</i>") % (self._service_name, self._msg)
AttributeError: TwitterUpdateAction instance has no attribute '_service_name'

Comment 1 marques 2008-08-19 12:05:14 UTC
Sorry for the dupe - the gnome bug submitter allowed me to press submit twice.

*** This bug has been marked as a duplicate of 548422 ***
Comment 2 marques 2008-08-19 12:09:20 UTC
I had to cancel out of BugBuddy 3 more times after submitting this second bug.  I don't think the app died five times at once so this is a little odd.  The trackeback in this report matches the original, so I presume the other 3 (all deskbar related) were also clones.

Maybe something about this should be filed against BugBuddy.