Public bug reported:
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)
** Affects: alarm-clock (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug precise
** Attachment added: "syslog.part"
https://bugs.launchpad.net/bugs/1284648/+attachment/3996183/+files/syslog.part
** Description changed:
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.
Relevent info appears to begin at 04:16:39. You will see Alt + SysRq commands
near the end of the log. The only configuration files with information in them
are: global.conf and alarms.conf
-
+ 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
+ PATH=(custom, no user)
+ LANG=en_US.UTF-8
+ SHELL=/bin/bash
SourcePackage: alarm-clock
UpgradeStatus: No upgrade log present (probably fresh install)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1284648
Title:
System freeze Locks Up & Cannot Alt+F1 to terminal
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alarm-clock/+bug/1284648/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
