GLib-CRITICAL **: g_variant_new_string: assertion `string != NULL' failed
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
policykit-gnome (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
Startup is very slow and xsession errors give the following message:
openConnection: connect: Bestand of map bestaat niet
cannot connect to brltty at :0
xfce4-settings-
(polkit-
(polkit-
** Message: applet now removed from the notification area
** Message: applet now embedded in the notification area
** Message: applet now removed from the notification area
** Message: using fallback from indicator to GtkStatusIcon
** Message: applet now embedded in the notification area
WARNING: gnome-keyring:: couldn't connect to: /tmp/keyring-
Object::connect: No such slot TimetrackerWidg
Connecting to deprecated signal QDBusConnection
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
kbuildsycoca4 running...
kbuildsycoca4(1846) KBuildSycoca:
kbuildsycoca4(1846) KBuildSycoca:
kbuildsycoca4(1846) kdemain: Emitting notifyDatabaseC
Object::connect: No such slot ktimetrackerpar
QSystemTrayIcon
Object::connect: No such signal TrayIcon:
Object::connect: (sender name: 'Ktimetracker Tray')
ktimetracker(
debconf: DbDriver "passwords" warning: could not open /var/cache/
debconf: DbDriver "passwords" warning: could not open /var/cache/
debconf: DbDriver "passwords" warning: could not open /var/cache/
Object::connect: No such slot TimetrackerWidg
Object::connect: No such slot ktimetrackerpar
QSystemTrayIcon
Object::connect: No such signal TrayIcon:
Object::connect: (sender name: 'Ktimetracker Tray')
Is this a known issue?
Changed in policykit-gnome (Ubuntu): | |
status: | Incomplete → Confirmed |
Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https:/ /wiki.ubuntu. com/Bugs/ FindRightPackag e. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.
To change the source package that this bug is filed about visit https:/ /bugs.launchpad .net/ubuntu/ +bug/1048138/ +editstatus and add the package name in the text box next to the word Package.
[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]