qtile: Widget `Notify` throws error in logs every time it's used (even if it works fine).

The issue:

Every time I feed my Notify widget with something (using, for example, notify-send), it throws the following into the log file:

Traceback (most recent call last):    
  File "/usr/lib/python3.11/asyncio/events.py", line 80, in _run    
    self._context.run(self._callback, *self._args)    
  File "/usr/lib/python3.11/site-packages/libqtile/core/manager.py", line 909, in f    
    func(*args)    
  File "/usr/lib/python3.11/site-packages/libqtile/widget/notify.py", line 132, in real_update    
    self.set_notif_text(notif)    
  File "/usr/lib/python3.11/site-packages/libqtile/widget/notify.py", line 104, in set_notif_text    
    self.text = pangocffi.markup_escape_text(notif.summary)    
    ^^^^^^^^^    
  File "/usr/lib/python3.11/site-packages/libqtile/widget/base.py", line 490, in text    
    self.layout.text = self.formatted_text    
    ^^^^^^^^^^^^^^^^    
  File "/usr/lib/python3.11/site-packages/libqtile/drawer.py", line 73, in text    
    self.layout.set_attributes(attrlist)    
  File "/usr/lib/python3.11/site-packages/libqtile/pangocffi.py", line 118, in set_attributes    
    pango.pango_layout_set_attributes(self._pointer, attrs)    
TypeError: initializer for ctype 'PangoLayout *' must be a cdata pointer, not NoneType

This error is repeated 16 times (always).

I’ve tried it on a default settings for the widget, so I don’t think my configuration is relevant here.

~ ❯ qtile --version                                                                                                                                                                                                                                                                                                                                                26s
0.22.2.dev127+gffbf518e

Required:

  • I have searched past issues to see if this bug has already been reported.

About this issue

  • Original URL
  • State: closed
  • Created a year ago
  • Comments: 20 (20 by maintainers)

Commits related to this issue

Most upvoted comments

After updating to 0.22.2.dev150+ge293f26c the problem is gone for me.