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 489674 - crash in Deskbar: Searching for the term "...
crash in Deskbar: Searching for the term "...
Status: RESOLVED DUPLICATE of bug 472134
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-10-24 05:16 UTC by Dwight Shepherd
Modified: 2007-10-24 10:44 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20


Description Dwight Shepherd 2007-10-24 05:16:08 UTC 
What were you doing when the application crashed?
Searching for the term "brightness". Nothing else really.

The machine just started up. Before searching for the term bright i adjusted the brightness of the backlight when on battery.

That's it. 


Distribution: Ubuntu 7.10 (gutsy)
Gnome Release: 2.20.0 2007-09-17 (Ubuntu)
BugBuddy Version: 2.18.1

System: Linux 2.6.22-14-generic #1 SMP Sun Oct 14 23:05:12 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 (81 sec old) ---------------------
Throttle level is 0
/home/dwight/.gtkrc-2.0:2: error: scanner: unterminated string constant - e.g. `style'
Initializing gnome-mount extension
Warning: Gtk2::Sexy not found ...
CheckGmail uses Gtk2::Sexy for clickable URLs in mail messages
Please download and install from CPAN (http://search.cpan.org) if you want to use this feature ...
/home/dwight/.gtkrc-2.0:2: error: scanner: unterminated string constant - e.g. `style'
/home/dwight/.gtkrc-2.0:2: error: scanner: unterminated string constant - e.g. `style'
/home/dwight/.gtkrc-2.0:2: error: scanner: unterminated string constant - e.g. `style'
/home/dwight/.gtkrc-2.0:2: error: scanner: unterminated string constant - e.g. `style'
/home/dwight/.gtkrc-2.0:2: error: scanner: unterminated string constant - e.g. `style'
/home/dwight/.gtkrc-2.0:2: error: scanner: unterminated string constant - e.g. `style'
/home/dwight/.gtkrc-2.0:2: error: scanner: unterminated string constant - e.g. `style'
--------------------------------------------------
Traceback (most recent call last):

+ Trace 172435

  • File "/usr/lib/python2.5/site-packages/deskbar/gtkexcepthook.py", line 67 in run 
    run_old(*args, **kwargs)
  • File "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/desklicious.py", line 65 in query 
    posts = self._delicious.get_posts_by_tag(tag)
  • File "/usr/lib/deskbar-applet/modules-2.20-compatible/desklicious.py", line 136 in get_posts_by_tag 
    stream = urllib.urlopen(url, proxies=deskbar.core.Utils.get_proxy())
  • File "urllib.py", line 82 in urlopen 
    return opener.open(url)
  • File "urllib.py", line 190 in open 
    return getattr(self, name)(url)
  • File "urllib.py", line 325 in open_http 
    h.endheaders()
  • File "httplib.py", line 856 in endheaders 
    self._send_output()
  • File "httplib.py", line 728 in _send_output 
    self.send(msg)
  • File "httplib.py", line 695 in send 
    self.connect()
  • File "httplib.py", line 663 in connect 
    socket.SOCK_STREAM):
IOError: [Errno socket error] (-2, 'Name or service not known') 






Comment 1


Christoph Wolk





          2007-10-24 10:44:03 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 472134 ***