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 497761 - crash in Home Folder: right mouseclick on mpg-...
crash in Home Folder: right mouseclick on mpg-...
Status: RESOLVED DUPLICATE of bug 440988
Product: nautilus
Classification: Core
Component: general
unspecified
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-11-17 22:10 UTC by beckes
Modified: 2007-11-18 02:30 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description beckes 2007-11-17 22:10:54 UTC
What were you doing when the application crashed?
right mouseclick on mpg-file


Distribution: Debian lenny/sid
Gnome Release: 2.18.3 2007-07-03 (Debian)
BugBuddy Version: 2.18.1

System: Linux 2.6.22-2-k7 #1 SMP Fri Aug 31 01:02:37 UTC 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Nuovo

Memory status: size: 75284480 vsize: 75284480 resident: 26361856 share: 15331328 rss: 26361856 rss_rlim: 4294967295
CPU usage: start_time: 1195323813 rtime: 3182 utime: 2848 stime: 334 cutime:0 cstime: 3 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/bin/nautilus'

(no debugging symbols found)
Using host libthread_db library "/lib/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb6da08c0 (LWP 4143)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

Thread 1 (Thread 0xb6da08c0 (LWP 4143))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/i686/cmov/libpthread.so.0
  • #2 ??
    from /usr/lib/libgnomeui-2.so.0
  • #3 ??
  • #4 ??
  • #5 ??
  • #0 __kernel_vsyscall


----------- .xsession-errors (10312 sec old) ---------------------
not rec
:images/idle-low-signal-lock.png
|idle-low-signal-lock.png
  ath0: 4109508    4480    0    0    0     0          0         0   747560    4444    0    0    0     0       0          0
:images/idle-low-signal-lock.png
|both-low-signal-lock.png
  ath0: 4109574    4481    0    0    0     0          0         0   747626    4445    0    0    0     0       0          0
not trans
66
m| 117103
not rec
:images/both-low-signal-lock.png
|idle-low-signal-lock.png
  ath0: 4109574    4481    0    
...Too much output, ignoring rest...
--------------------------------------------------
Comment 1 André Klapper 2007-11-18 02:30:02 UTC
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


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