! Please note that this is a snapshot of our old Bugzilla server, which is read only since May 29, 2020. Please go to gitlab.xfce.org for our new server !
orageclock crashed with SIGSEGV in strchr()
Status:
CLOSED: WORKSFORME
Component:
clock-plugin

Comments

Description charlie-tca 2010-02-01 18:41:02 CET
Created attachment 2819 
Stacktrace.txt

This bug has been reported on Ubuntu Launchpad as:
  https://bugs.launchpad.net/bugs/508039

From the launchpad report:

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
Comment 1 juha editbugs 2010-02-02 07:44:31 CET
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
Comment 2 juha editbugs 2010-02-25 13:43:35 CET
Does not look like Orage issue. Can't fix with the available data.

Bug #6199

Reported by:
charlie-tca
Reported on: 2010-02-01
Last modified on: 2011-01-18

People

CC List:
1 user

Version

Attachments

Stacktrace.txt (3.34 KB, text/plain)
2010-02-01 18:41 CET , charlie-tca
no flags

Additional information