alarm-clock-applet crashes when disabling automatic start at login

Bug #704659 reported by Kamal Mostafa
This bug affects 1 person
Affects Status Importance Assigned to Milestone
alarm-clock-applet (Ubuntu)

Bug Description

Binary package hint: alarm-clock-applet

Description: Ubuntu 10.10
Release: 10.10


alarm-clock-applet crashes (SIGSEGV) when I try to un-check the "Start automatically at login" box in its Preferences panel. Since alarm-clock-applet does start automatically at login, this makes it impossible to prevent it from starting!

The crash occurs only when the directory $HOME/.config/autostart does not exist. alarm-clock-applet fails to try to create it, and then crashes when mishandling a subsequent file copy into that directory.

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: alarm-clock-applet 0.3.1-1
ProcVersionSignature: Ubuntu 2.6.35-24.42-generic
Uname: Linux 2.6.35-24-generic x86_64
NonfreeKernelModules: nvidia
Architecture: amd64
Date: Tue Jan 18 13:57:04 2011
Disassembly: => 0x0: Cannot access memory at address 0x0
ExecutablePath: /usr/bin/alarm-clock-applet
ProcCmdline: alarm-clock-applet
 PATH=(custom, user)
 Segfault happened at: 0x0: Cannot access memory at address 0x0
 PC (0x00000000) not located in a known VMA region (needed executable region)!
SegvReason: executing NULL VMA
Signal: 11
SourcePackage: alarm-clock-applet
 ?? ()
 pango_attribute_copy () from /usr/lib/
 pango_attr_list_copy () from /usr/lib/
 get_layout (celltext=0x220a2b0, widget=0x22902e0, will_render=<value optimized out>, flags=0) at /build/buildd/gtk+2.0-2.22.0/gtk/gtkcellrenderertext.c:1378
 get_size (cell=0x220a2b0, widget=0x22902e0, cell_area=<value optimized out>, layout=0x0, x_offset=0x0, y_offset=0x0, width=0x7fffb6cd3f80, height=0x0) at /build/buildd/gtk+2.0-2.22.0/gtk/gtkcellrenderertext.c:1540
Title: alarm-clock-applet crashed with SIGSEGV in pango_attribute_copy()
UserGroups: adm admin audio cdrom dialout libvirtd lpadmin ntp plugdev sambashare

Revision history for this message
Kamal Mostafa (kamalmostafa) wrote :
Changed in alarm-clock-applet (Ubuntu):
assignee: nobody → Kamal Mostafa (kamalmostafa)
status: New → In Progress
Revision history for this message
Kamal Mostafa (kamalmostafa) wrote :

Attached branch fixes the problem. I will upstream after acceptance.

Changed in alarm-clock-applet (Ubuntu):
assignee: Kamal Mostafa (kamalmostafa) → Ubuntu Sponsors Team (ubuntu-sponsors)
importance: Undecided → Low
milestone: none → natty-alpha-2
status: In Progress → New
Changed in alarm-clock-applet (Ubuntu):
assignee: Ubuntu Sponsors Team (ubuntu-sponsors) → nobody
status: New → Triaged
Revision history for this message
Chow Loong Jin (hyperair) wrote :

Thanks Kamal, for the fix. I'll poke upstream about this patch, and get it into Debian as well.

Revision history for this message
Johannes H. Jensen (joh) wrote :

Hi, I believe this has been fixed in trunk already, but no release has yet been made which incorporates this fix. Could you please try the trunk version and see if you still are able to reproduce the problem?



Revision history for this message
Kamal Mostafa (kamalmostafa) wrote :

See my comment and proposed fix branch in bug 610632; The problems still occur in trunk rev 194.

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.