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 129053 - Attempting to run Camorama results in crash
Attempting to run Camorama results in crash
Status: RESOLVED INCOMPLETE
Product: camorama
Classification: Deprecated
Component: General
unspecified
Other other
: Normal normal
: ---
Assigned To: greg
greg
: 121612 156286 301766 329410 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2003-12-11 04:05 UTC by bugbuddy.evolution
Modified: 2006-09-28 01:04 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description bugbuddy.evolution 2003-12-11 04:06:01 UTC
Package: camorama
Severity: blocker
Version: 0.16
Synopsis: Attempting to run Camorama results in crash
Bugzilla-Product: camorama
Bugzilla-Component: General
BugBuddy-GnomeVersion: 2.0 (2.2.0.1)

Description:
Description of Problem:

Attempting to run Camorama results in crash

Steps to reproduce the problem:
1. Start Camorama.
2. Crash.
3. 

Actual Results:

Crash.

Expected Results:

Application starts without critial errors.

How often does this happen?

100% of the time.

Additional Information:




Debugging Information:

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

(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...[New Thread 1086250464 (LWP 27500)]
(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
0x4001543e in _dl_sysinfo_int80 () from /lib/ld-linux.so.2

Thread 1 (Thread 1086250464 (LWP 27500))

  • #0 _dl_sysinfo_int80
    from /lib/ld-linux.so.2
  • #1 waitpid
    from /lib/tls/libpthread.so.0
  • #2 libgnomeui_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 strncpy
    from /lib/tls/libc.so.6
  • #5 main
  • #6 __libc_start_main
    from /lib/tls/libc.so.6
  • #0 _dl_sysinfo_int80
    from /lib/ld-linux.so.2




------- Bug moved to this database by unknown@bugzilla.gnome.org 2003-12-10 23:06 -------

The original reporter (bugbuddy.evolution@metamark.com) of this bug does not have an account here.
Reassigning to the exporter, unknown@bugzilla.gnome.org.
Reassigning to the default owner of the component, greg@fixedgear.org.

Comment 1 Elijah Newren 2003-12-11 14:53:33 UTC
Appears to be a unique stack trace according to the simple-dup-finder,
but I don't know if the stack trace is useful.  Reporter: Is there any
chance you could get us a stack trace with debugging symbols?  Some
basic directions on how to do so can be found at
http://bugzilla.gnome.org/getting-traces.cgi.
Comment 2 Samuel Stringham 2005-07-27 08:54:43 UTC
*** Bug 168983 has been marked as a duplicate of this bug. ***
Comment 3 Samuel Stringham 2005-07-27 08:57:45 UTC
*** Bug 301766 has been marked as a duplicate of this bug. ***
Comment 4 Samuel Stringham 2005-07-27 09:02:33 UTC
*** Bug 156286 has been marked as a duplicate of this bug. ***
Comment 5 Samuel Stringham 2005-07-27 09:05:53 UTC
*** Bug 121612 has been marked as a duplicate of this bug. ***
Comment 6 Karsten Bräckelmann 2006-02-04 22:43:30 UTC
*** Bug 329410 has been marked as a duplicate of this bug. ***
Comment 7 Elijah Newren 2006-09-28 01:04:49 UTC
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for.
Thanks!