Bug 351368 – crash on Datum und Uhrzeit

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 351368 - crash on Datum und Uhrzeit


Summary:	crash on Datum und Uhrzeit


Status:	RESOLVED INCOMPLETE

Product:	gnome-system-tools
Classification:	Deprecated
Component:	time-admin
Version:	2.15.x
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	Carlos Garnacho
QA Contact:	Carlos Garnacho

URL:
Whiteboard:

Duplicates:	353934 354081 354747 354748 355089 355101 355108 355668 355843 374557 392019 (view as bug list)
Depends on:
Blocks:

Reported:	2006-08-14 21:32 UTC by fspmc
Modified:	2007-01-02 21:47 UTC

See Also:
GNOME target:	---
GNOME version:	2.15/2.16

Description fspmc 2006-08-14 21:32:28 UTC

What were you doing when the application crashed?
I was changing the date within the gnome timeconfig tool.


Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.15.91 2006-08-08 (Ubuntu)
BugBuddy Version: 2.15.90

Memory status: size: 140156928 vsize: 140156928 resident: 17670144 share: 10596352 rss: 17670144 rss_rlim: -1
CPU usage: start_time: 1155591031 rtime: 138 utime: 129 stime: 9 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/bin/time-admin'

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 47614595529504 (LWP 4981)]
0x00002b4e220edd85 in waitpid () from /lib/libpthread.so.0

+ Trace 70452

Thread 1 (Thread 47614595529504 (LWP 4981))

#0 waitpid
from /lib/libpthread.so.0
#1 gnome_gtk_module_info_get
from /usr/lib/libgnomeui-2.so.0
#2 <signal handler called>
#3 dbus_error_has_name
from /usr/lib/libdbus-1.so.2
#4 dbus_error_has_name
from /usr/lib/libdbus-1.so.2
#5 ??
#6 ??
#7 g_source_get_current_time
from /usr/lib/libglib-2.0.so.0
#8 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#9 g_main_context_check
from /usr/lib/libglib-2.0.so.0
#10 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#11 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#12 ??
#13 __libc_start_main
from /lib/libc.so.6
#14 ??
#15 ??
#16 ??
#0 waitpid
from /lib/libpthread.so.0

Comment 1 Sergej Kotliar 2006-09-02 14:35:21 UTC

*** Bug 353934 has been marked as a duplicate of this bug. ***

Comment 2 Sergej Kotliar 2006-09-02 14:35:40 UTC

Thanks for the bug report. Unfortunately, that stack trace is not very useful in determining the cause of the crash. Can you get us one with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so.

Comment 3 Christian Kirbach 2006-09-03 11:13:04 UTC

*** Bug 354081 has been marked as a duplicate of this bug. ***

Comment 4 holland.v 2006-09-03 17:06:18 UTC

Unfortunately, shortly after that error, I downloaded a fresh copy of the Edgy Eft Live DVD and then proceeded with a text base installation that worked without incident.

Therefore I can't provide any additional information.  I really wasn't looking for a resolution as the error wasn't fatal, I was just following the on-screen instructions that ended up creating this report.

Thanks!

Van Holland

Comment 5 Karsten Bräckelmann 2006-09-07 10:30:28 UTC

*** Bug 354748 has been marked as a duplicate of this bug. ***

Comment 6 Karsten Bräckelmann 2006-09-07 10:30:30 UTC

*** Bug 354747 has been marked as a duplicate of this bug. ***

Comment 7 Sergej Kotliar 2006-09-09 11:11:01 UTC

*** Bug 355089 has been marked as a duplicate of this bug. ***

Comment 8 Sergej Kotliar 2006-09-09 13:32:06 UTC

*** Bug 355101 has been marked as a duplicate of this bug. ***

Comment 9 Sergej Kotliar 2006-09-09 13:32:12 UTC

*** Bug 355108 has been marked as a duplicate of this bug. ***

Comment 10 Karsten Bräckelmann 2006-09-12 23:16:01 UTC

*** Bug 355668 has been marked as a duplicate of this bug. ***

Comment 11 Karsten Bräckelmann 2006-09-13 19:46:25 UTC

*** Bug 355843 has been marked as a duplicate of this bug. ***

Comment 12 André Klapper 2006-10-24 12:23:25 UTC

Closing this bug report as no further information has been provided. Anybody please feel free to reopen this bug if you can provide the information asked for and if he/she can still reproduce this issue (no duplicates for more than a month now).
Thanks!

Comment 13 André Klapper 2006-11-13 11:02:19 UTC

*** Bug 374557 has been marked as a duplicate of this bug. ***

Comment 14 Jonathon Jongsma 2007-01-02 21:47:11 UTC

*** Bug 392019 has been marked as a duplicate of this bug. ***