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 509002 - crash in Deskbar: lancer firefox session t...
crash in Deskbar: lancer firefox session t...
Status: RESOLVED DUPLICATE of bug 475351
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-01-12 18:37 UTC by dont
Modified: 2008-01-13 11:36 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20


Description dont 2008-01-12 18:37:17 UTC 
What were you doing when the application crashed?
lancer firefox
session tout juste démarrée (ubuntu)


Distribution: Ubuntu 7.10 (gutsy)
Gnome Release: 2.20.1 2007-10-19 (Ubuntu)
BugBuddy Version: 2.18.1

System: Linux 2.6.22-14-generic #1 SMP Tue Dec 18 08:02:57 UTC 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Glossy P
Icon Theme: Mac4Lin_Icons_v0.4

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 (136 sec old) ---------------------
Impossible d'ouvrir le fichier de bureau /home/rudewolf/Bureau/Metacity.desktop pour le lanceur du tableau de bord: Aucun fichier ou répertoire de ce type
Impossible d'ouvrir le fichier de bureau /home/rudewolf/Bureau/skype.desktop pour le lanceur du tableau de bord: Aucun fichier ou répertoire de ce type
Impossible d'ouvrir le fichier de bureau /home/rudewolf/Bureau/freeciv.desktop pour le lanceur du tableau de bord: Aucun fichier ou répertoire de ce type
Impossible d'ouvrir le fichier de bureau /home/rudewolf/Bureau/wesnoth.desktop pour le lanceur du tableau de bord: Aucun fichier ou répertoire de ce type
Impossible d'ouvrir le fichier de bureau /home/rudewolf/Bureau/vegastrike.desktop pour le lanceur du tableau de bord: Aucun fichier ou répertoire de ce type
Impossible d'ouvrir le fichier de bureau /home/rudewolf/Bureau/supertux.desktop pour le lanceur du tableau de bord: Aucun fichier ou répertoire de ce type
(gnome-panel:30939): Gtk-WARNING **: gtk_widget_size_allocate(): attempt to allocate widget with width -4 and height 32
kdecore (KAction): WARNING: KAction::insertKAccel( kaccel = 0x825a228 ): KAccel object already contains an action name "play_pause"
QLayout "unnamed" added to QVBox "unnamed", which already has a layout
kdecore (KAction): WARNING: KAction::insertKAccel( kaccel = 0x825a228 ): KAccel object already contains an action name "play_pause"
QLayout: Adding KToolBar/mainToolBar (child of QVBox/unnamed) to layout for PlaylistWindow/PlaylistWindow
QObject::connect: Incompatible sender/receiver arguments
	StarManager::ratingsColorsChanged() --> ContextBrowser::ratingOrScoreOrLabelsChanged(const QString&)
STARTUP
--------------------------------------------------
Traceback (most recent call last):

+ Trace 185077

  • File "/usr/lib/python2.5/site-packages/deskbar/gtkexcepthook.py", line 67 in run 
    run_old(*args, **kwargs)
  • File "/usr/lib/python2.5/threading.py", line 440 in run 
    self.__target(*self.__args, **self.__kwargs)
  • File "/usr/lib/python2.5/site-packages/deskbar/core/ThreadPool.py", line 67 in _worker 
    function(*args, **kwargs)
  • File "/usr/lib/deskbar-applet/modules-2.20-compatible/history.py", line 52 in query 
    if text.startswith(query):
AttributeError: 'NoneType' object has no attribute 'startswith' 






Comment 1


Sebastian Pölsterl





          2008-01-13 11:36:16 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 475351 ***