https://bugs.kde.org/show_bug.cgi?id=489899

--- Comment #7 from quanticcpu2...@gmail.com ---
(In reply to David Jarvie from comment #6)
> To help find the cause for this, can you please do the following:
> 
> 1) Quit KAlarm (use menu option File -> Quit).
> 
> 2) Open a terminal window and run KAlarm from there (type "kalarm" and then
> Enter).
> 
> 3) Open the Edit Alarm dialog for the alarm, and click Try.
> 
> 4) Copy all the terminal output starting from before Try was clicked, and
> attach it here.
> 
> 5) Quit KAlarm, and start it again from the menu to let it run normally
> again.

❯ kalarm
org.kde.pim.kalarm: Kernel alarm timers not available (no CAP_WAKE_ALARM
capability)
Fontconfig error: "/home/dom/.fonts.conf", line 1: XML declaration allowed only
at the start of the document

QPainter::begin: Paint device returned engine == 0, type: 2
QWidget::render: Cannot render with an inactive painter
QPainter::begin: Paint device returned engine == 0, type: 2
QWidget::render: Cannot render with an inactive painter
QPainter::begin: Paint device returned engine == 0, type: 2
QWidget::render: Cannot render with an inactive painter
QPainter::begin: Paint device returned engine == 0, type: 2
QWidget::render: Cannot render with an inactive painter
QPainter::begin: Paint device returned engine == 0, type: 2
QWidget::render: Cannot render with an inactive painter
QPainter::begin: Paint device returned engine == 0, type: 2
QWidget::render: Cannot render with an inactive painter
QPainter::begin: Paint device returned engine == 0, type: 2
QWidget::render: Cannot render with an inactive painter
QPainter::begin: Paint device returned engine == 0, type: 2
QWidget::render: Cannot render with an inactive painter

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to