Ok; I never used gdb before, just visual debuggers.
I'm not sure this is not a blind alley. The "gtk_container_add warning" is not
reproducible and has IMHO nothing to do with this bug(s) (just IMHO).
As far as I understood, "b g_log" sets a breakpoint at the g_log() function,
right?
Just too understand right; I first have to set "b g_log", and then "run" the
program, right, and "c" means "continue".
I tried everything here, including deleteing the printer, and watching it
respawn. Only logs I got was:
Thread 1 "gnome-control-c" hit Breakpoint 1, g_log
(log_domain=log_domain@entry=0x5555556b6a97 "printers-cc-panel",
log_level=log_level@entry=G_LOG_LEVEL_DEBUG,
format=format@entry=0x5555556b8428 "Could not check 'Clean' maintenance
command: %s") at ../../../../glib/gmessages.c:1428
1428 in ../../../../glib/gmessages.c
Which seems completely unrelated to me.
BTW: system-config-printer does NOT show the "driverless" printer at
all.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1813825
Title:
"driverless" printer workflow has bad usability/ is partly broken
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1813825/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
