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 458903 - crash in Deskbar: USB 接続でメモリーカードよりコピーしたとき ...
crash in Deskbar: USB 接続でメモリーカードよりコピーしたとき ...
Status: RESOLVED DUPLICATE of bug 403752
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-07-21 07:16 UTC by kwjwq974
Modified: 2007-07-22 09:47 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description kwjwq974 2007-07-21 07:16:15 UTC 
What were you doing when the application crashed?
USB 接続でメモリーカードよりコピーしたとき
またカードリーダーは USB に差し込んだ時しか認識されない
常時接続では認識されない


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.3 2007-07-02 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.22.1-27.fc7 #1 SMP Tue Jul 17 17:13:26 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

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 ---------------------
Watching directory /home/iyharuna/Pictures/未タイトルのフォルダ/61202eneA-2 (total watches = 351)
Watching directory /home/iyharuna/Pictures/未タイトルのフォルダ/A4size (total watches = 352)
Watching directory /home/iyharuna/Pictures/未タイトルのフォルダ/61203sm-1 (total watches = 353)
Watching directory /home/iyharuna/Pictures/未タイトルのフォルダ/oupenmae/新しいフォルダ (2) (total watches = 354)
Watching directory /home/iyharuna/Pictures/未タイトルのフォルダ/oupenmae/新しいフォルダ (4) (total watches = 355)
Watching directory /home/iyharuna/Pictures/未タイトルのフォルダ/oupenmae/新しいフォルダ (3) (total watches = 356)
Watching directory /home/iyharuna/Pictures/未タイトルのフォルダ/oupenmae/新しいフォルダ (total watches = 357)
Watching directory /home/iyharuna/Pictures/未タイトルのフォルダ/sonota/新しいフォルダ (total watches = 358)
Watching directory /home/iyharuna/Pictures/未タイトルのフォルダ/back4/新しいフォルダ (total watches = 359)
Watching directory /home/iyharuna/Pictures/未タイトルのフォルダ/backu6/新しいフォルダ (2) (total watches = 360)
Watching directory /home/iyharuna/Pictures/未タイトルのフォルダ/backu6/新しいフォルダ (total watches = 361)
starting indexing...
indexing #1 - /home/iyharuna
flushing all words
Finished indexing. Waiting for new events...
--------------------------------------------------
Traceback (most recent call last):

+ Trace 149525

  • File "/usr/lib/python2.5/site-packages/deskbar/ModuleLoader.py", line 149 in load_all 
    self.load (f)
  • File "/usr/lib/python2.5/site-packages/deskbar/ModuleLoader.py", line 131 in load 
    mod_instance = getattr (mod, handler) ()
  • File "/usr/lib/deskbar-applet/handlers/tracker-handler.py", line 201 in __init__ 
    self.tracker = bus.get_object('org.freedesktop.Tracker','/org/freedesktop/tracker')
  • File "/usr/lib/python2.5/site-packages/dbus/bus.py", line 226 in get_object 
    follow_name_owner_changes=follow_name_owner_changes)
  • File "/usr/lib/python2.5/site-packages/dbus/proxies.py", line 236 in __init__ 
    self._named_service = conn.activate_name_owner(bus_name)
  • File "/usr/lib/python2.5/site-packages/dbus/bus.py", line 165 in activate_name_owner 
    self.start_service_by_name(bus_name)
  • File "/usr/lib/python2.5/site-packages/dbus/bus.py", line 261 in start_service_by_name 
    'su', (bus_name, flags)))
  • File "/usr/lib/python2.5/site-packages/dbus/connection.py", line 598 in call_blocking 
    message, timeout)
DBusException: org.freedesktop.DBus.Error.Spawn.ChildExited: Process /usr/bin/trackerd exited with status 0 






Comment 1


palfrey





          2007-07-22 09:47:42 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 403752 ***