[raring] Enters infinite loop if gwibber service cannot be started
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gwibber (Ubuntu) |
Won't Fix
|
Undecided
|
Unassigned |
Bug Description
Gwibber now suffers from bug 1112106 and unity-gwibber-
unity-gwibber-
(process:6753): libunity-CRITICAL **: unity_filter_
(process:6753): libunity-CRITICAL **: unity_filter_
** (process:6753): CRITICAL **: file /home/ken/
** (process:6753): CRITICAL **: file /home/ken/
...
And it takes 99% of the CPU while printing this over and over:
(process:6753): unity-gwibber-
(process:6753): dee-CRITICAL **: dee_analyzer_
(process:6753): dee-CRITICAL **: dee_model_is_last: assertion `DEE_IS_MODEL (self)' failed
(process:6753): dee-CRITICAL **: dee_model_
(process:6753): dee-CRITICAL **: dee_model_is_last: assertion `DEE_IS_MODEL (self)' failed
ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: unity-lens-gwibber 3.6.0-0ubuntu2
ProcVersionSign
Uname: Linux 3.8.0-3-generic x86_64
ApportVersion: 2.8-0ubuntu4
Architecture: amd64
Date: Fri Feb 1 15:12:08 2013
InstallationDate: Installed on 2013-01-04 (28 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130104)
MarkForUpload: True
SourcePackage: gwibber
UpgradeStatus: No upgrade log present (probably fresh install)
Changed in gwibber (Ubuntu): | |
status: | Confirmed → Won't Fix |
Status changed to 'Confirmed' because the bug affects multiple users.