Gwibber

Window gets white after some time

Bug #398416 reported by uvok
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Gwibber
Fix Released
Undecided
Alexander Sack
gwibber (Ubuntu)
Fix Released
Medium
Alexander Sack

Bug Description

I run gwibber on LXDE with awesome as WM.

After some time, the window gets totally white and such unusable. (see screenshot).

When I used openbox as WM, there were no such problems.
(So is it the fault of awesome?)

Are there other users who had problems with running gwibber on awesome?

Related branches

lp:~asac/gwibber/lp398416
gwibber-committers: Pending requested
Diff: None lines
Revision history for this message
uvok (uvok-deactivatedaccount) wrote :
Revision history for this message
uvok (uvok-deactivatedaccount) wrote :

Got the traceback:

Traceback (most recent call last):
  File "/usr/lib/python2.6/site-packages/gwibber/client.py", line 1123, in update_view_contents
    if tab.show_notifications: self.show_notification_bubbles(view.message_store)
  File "/usr/lib/python2.6/site-packages/gwibber/client.py", line 1070, in show_notification_bubbles
    n = gintegration.notify(message.sender, body, image, ["reply", "Reply"], expire_timeout)
  File "/usr/lib/python2.6/site-packages/gwibber/gintegration.py", line 36, in notify
    if "actions" in caps:
TypeError: argument of type 'NoneType' is not iterable

Revision history for this message
Alexander Sack (asac) wrote :

please try the branch i attached:

1. stop gwibber
2. cd /tmp/
3. bzr branch lp:~asac/gwibber/lp398416 gwibber
4. ./bin/gwibber

see if you can still reproduce it.

Changed in gwibber:
assignee: nobody → Alexander Sack (asac)
status: New → Triaged
Revision history for this message
Alexander Sack (asac) wrote :

also, are you using notify-osd or the gnome notification-daemon? when this happen, maybe the notify-osd has crashed or something?

Revision history for this message
uvok (uvok-deactivatedaccount) wrote :

I use no notification daemon.

The attached branch works for me, thanks !

Revision history for this message
Alexander Sack (asac) wrote :

> I use no notification daemon.

Curious, is that because LXDE doesn't use any by default?

Revision history for this message
Alexander Sack (asac) wrote :

fixed in rev 348

Changed in gwibber (Ubuntu):
assignee: nobody → Alexander Sack (asac)
importance: Undecided → Medium
status: New → Fix Committed
Changed in gwibber:
status: Triaged → Fix Released
Revision history for this message
uvok (uvok-deactivatedaccount) wrote :

Don't know, but when I type $ ps aux | grep notif , there is no process...
(but I can send notifications with notify-send...)

Revision history for this message
Miciah Dashiel Butler Masters (miciah) wrote :

I confirm the issue with Gwibber running with the Awesome window manager. I also confirm that the patch resolves the issue. Thank you!

BTW, FYI, BBQ, Awesome itself handles notifications: the C code allows the Lua code to interface with D-BUS, and notifications are handled by the Naughty library (cf. /usr/share/awesome/lib/naughty.lua). No notification daemon is required with Awesome.

Alexander Sack (asac)
Changed in gwibber (Ubuntu):
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.