System freeze Locks Up & Cannot Alt+F1 to terminal

Bug #1284648 reported by Sepero
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
alarm-clock (Ubuntu)
New
Undecided
Unassigned

Bug Description

Other possibly essential info-
Device make/model: Asus / N53SM
GPU Make/Model: Nvidia / GeForce GT 630M
GPU Driver: Using Bumblebee drivers
Desktop: Openbox + Lxpanel

Crash info:
Screen goes entirely black. Mouse pointer continues to be displayed on screen, but unresponsive. Nothing happens when pressing any Alt+FX combination. System appears frozen locked, and unresponsive to any input. I'm forced to use Alt + SysReq keys to reboot system.

Action at time of crash:
Adjusting or editing settings in alarmclock program.

More details:
I've noticed this bug occur on about 5 occasions within the past couple weeks while I've started making more use of alarm-clock. The bug only occurs while I'm actively using my laptop. During the last crash, I only had 1 scheduled alarm. I use a 24hr clock for all time keeping. I have not yet discovered how to reproduce the bug purposefully. Attached is partial syslog for 2014 Feb 25. The only alarmclock configuration files with information in them are: global.conf and alarms.conf

global.conf:

[WindowGeometry]
WindowPositionX=32
WindowPositionY=0
WindowSizeX=770
WindowSizeY=400

[Global]
TimeType=24
ShowMenuBar=true
StartMinimized=false

alarms.conf:

[alarm_675100830]
DateTime=2014-2-22T6:0:0
Title=Wakeup
ScheduleWeekdays=T:T:T:T:T:T:T
ScheduleMonths=F:T:F:F:F:F:F:F:F:F:F:F
ScheduleDateInclude=
ScheduleDateExclude=
AlarmType=Schedule
SoundEnabled=true
CustomSoundEnabled=false
CustomSoundFile=[DEFAULT]
ConstantSoundEnabled=true
ConstantSoundValue=5
FadeSoundEnabled=false
FadeSoundValue=5
RepeatSoundEnabled=false
RepeatSoundValue=5
PassivePopupEnabled=false
PassivePopupType=0
PassivePopupTimeout=30
PassivePopupTitle=Popup
PassivePopupText=Short popup
DialogWindowEnabled=false
DialogTextColor=#000000000000
DialogBackgroundColor=#ffffffffffff
DialogTextSize=1
DialogTitle=Dialog window
DialogMessage=This is a small message
SnoozeEnabled=false
SnoozeTime=5
RunCommand=false
RunCommandContent=
RunInTerminal=true
ActionEnabled=false
ActionFirstSelected=true

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: alarm-clock 1.2.5-1.2
ProcVersionSignature: Ubuntu 3.2.0-25.40-generic 3.2.18
Uname: Linux 3.2.0-25-generic x86_64
ApportVersion: 2.0.1-0ubuntu15.1
Architecture: amd64
Date: Tue Feb 25 04:52:18 2014
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425)
MarkForUpload: True
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: alarm-clock
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Sepero (cowpie2000) wrote :
description: updated
Revision history for this message
Sepero (cowpie2000) wrote :

Update to this bug. Now I think the bug may be the fault of a library, or something else. After uninstalling the package alarm-clock, and had the same bug occur again yesterday.

Revision history for this message
Sepero (cowpie2000) wrote :

Update 2, after reviewing the syslog again, I think the problem may be the fault of running out of Ram memory. There are oom (out of memory) notices in the syslog.

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.