orageclock crashed with SIGSEGV in strchr()

Bug #508039 reported by xFilx
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Orage
Invalid
Unknown
orage (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: orage

xubuntu 10.04

ProblemType: Crash
Architecture: i386
Date: Fri Jan 15 21:07:25 2010
DistroRelease: Ubuntu 10.04
ExecutablePath: /usr/lib/orage/xfce4/panel-plugins/orageclock
InstallationMedia: Xubuntu 9.10 "Karmic Koala" - Release i386 (20091028.3)
NonfreeKernelModules: nvidia
Package: orage 4.6.1-1ubuntu1
ProcCmdline: /usr/lib/orage/xfce4/panel-plugins/orageclock socket_id 18874420 name orageclock id 12592573450 display_name Часы\ с\ датой size 24 screen_position 11
ProcEnviron:
 LANG=ru_RU.utf8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-10.14-generic
SegvAnalysis:
 Segfault happened at: 0x45afc0 <strchr+32>: add %al,0x111840f(%ecx,%ecx,8)
 PC (0x0045afc0) ok
 source "%al" ok
 destination "0x111840f(%ecx,%ecx,8)" (0x0111840f) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: orage
StacktraceTop:
 strchr () from /lib/tls/i686/cmov/libc.so.6
 ?? () from /usr/lib/libgtk-x11-2.0.so.0
 ?? () from /usr/lib/libgtk-x11-2.0.so.0
 ?? () from /usr/lib/libgtk-x11-2.0.so.0
 gtk_widget_size_request () from /usr/lib/libgtk-x11-2.0.so.0
Tags: lucid
Title: orageclock crashed with SIGSEGV in strchr()
Uname: Linux 2.6.32-10-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare vboxusers

Revision history for this message
xFilx (sia6911) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 strchr () at ../sysdeps/i386/strchr.S:69
 ?? () from /usr/lib/libgtk-x11-2.0.so.0
 do_size_request (widget=0x97a2000)
 _gtk_size_group_compute_requisition (widget=0x97a2000,
 IA__gtk_widget_size_request (widget=0x97a2000,

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in orage (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
visibility: private → public
Revision history for this message
Charlie Kravetz (cjkgeek) wrote :

Thank you for your bug report. This bug has been reported to the developers of the software.

Changed in orage (Ubuntu):
status: New → Triaged
Revision history for this message
Charlie Kravetz (cjkgeek) wrote :

Comments from the developer, please respond at the Xfce bugzilla if possible. If you do not have an account and do not wish to open one, please comment here and add the attachment. I will forward them to the developer:

<email address hidden> editbugs 2010-02-02 07:44:31 UTC

I do not see any lines from orageclock source in the backtrace.
It actually crashes in the
XFCE_PANEL_PLUGIN_REGISTER_EXTERNAL(oc_construct);
which is part of panel.

Can you reproduce this or explain what you did to get it crash?

I can only push it to xfce panel team with the available data, but I doubt they
can also find the problem if we have no description of what happened?

Based on the .xsession errors it looks like the whole panel crashed? Or at
least
several plugins?

Does not look a orageclock bug

Revision history for this message
Charlie Kravetz (cjkgeek) wrote :

We'd like to figure out what's causing this bug for you, but we haven't heard back from you in a while. Could you please provide the requested information? The upstream developers have closed the Xfce bug due to no response. Thanks!

Changed in orage (Ubuntu):
status: Triaged → Incomplete
Revision history for this message
Charlie Kravetz (cjkgeek) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in orage (Ubuntu):
status: Incomplete → Invalid
Changed in orage:
status: Unknown → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.