Granite.Services.Logger is broken

Bug #826119 reported by Avi Romanoff
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Granite
Invalid
Undecided
Unassigned

Bug Description

No errors, but it seems to just not print anything (i.e they don't show up in terminal) when I try and log things either using the GLib functions or Logger.notification(). The only exception to this are fatal/critical errors which seem to display perfectly fine.

Revision history for this message
Jaap Broekhuizen (jaapz-b) wrote :

Did you do Logger.DisplayLevel = LogLevel.NOTIFY? Could you provide a simple test case?

Also i think Granite.Services.Logger in this state is nog very logical, or maybe there is something wrong with Granite.Application... I dont have much time at the moment, but i will look further into it tomorrow...

Revision history for this message
Avi Romanoff (aroman) wrote :

Yeah, that was part of the problem. I just generally didn't understand how the logging system worked. (Documentation would be nice, but is very offtopic to this bug). I resolved this a while ago :)

Changed in granite:
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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