Bug 89900 - unclear how to run with --verbose by default
Summary: unclear how to run with --verbose by default
Status: RESOLVED FIXED
Alias: None
Product: PackageKit
Classification: Unclassified
Component: General (show other bugs)
Version: unspecified
Hardware: Other All
: medium normal
Assignee: Richard Hughes
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-04-04 07:54 UTC by Kamil Páral
Modified: 2015-04-07 11:02 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments

Description Kamil Páral 2015-04-04 07:54:12 UTC
I have set myself a noble goal of making sure that packagekit works well for end users. In order to make finding and debugging packagekit issues easier, I want to run packagekitd with --verbose option by default. However, I fail to find out how to do that.

When I look into /etc/PackageKit/PackageKit.conf, there's no option for increased verbosity.

In the Reporting Bugs and FAQ sections on the web, there's no info either:
http://www.freedesktop.org/software/PackageKit/pk-bugs.html
http://www.freedesktop.org/software/PackageKit/pk-faq.html

If I override the existing systemd unit file in /etc and add --verbose as a default argument, packagekit doesn't start at all (I have no idea why):

$ sudo systemctl stop packagekit.service
$ sudo cp /usr/lib/systemd/system/packagekit.service /etc/systemd/system
$ sudo vim /etc/systemd/system/packagekit.service  # add --verbose
$ sudo systemctl daemon-reload 
$ systemctl cat packagekit.service 
# /etc/systemd/system/packagekit.service
[Unit]
Description=PackageKit Daemon

[Service]
Type=dbus
BusName=org.freedesktop.PackageKit
User=root
ExecStart=/usr/libexec/packagekitd --verbose
$ pgrep -fl packagekit
$ sudo systemctl start packagekit.service
Job for packagekit.service failed. See "systemctl status packagekit.service" and "journalctl -xe" for details.
$ systemctl status packagekit.service 
● packagekit.service - PackageKit Daemon
   Loaded: loaded (/etc/systemd/system/packagekit.service; static)
   Active: failed (Result: timeout) since Sat 2015-04-04 09:41:27 CEST; 2min 8s ago
  Process: 28148 ExecStart=/usr/libexec/packagekitd --verbose (code=killed, signal=TERM)
 Main PID: 28148 (code=killed, signal=TERM)

Apr 04 09:39:57 medusa packagekitd[28148]: 09:39:57        PackageKit        Verbose debugging enabled (on console 0)
Apr 04 09:39:57 medusa PackageKit[28148]: daemon start
Apr 04 09:41:27 medusa systemd[1]: packagekit.service start operation timed out. Terminating.
Apr 04 09:41:27 medusa systemd[1]: Failed to start PackageKit Daemon.
Apr 04 09:41:27 medusa systemd[1]: Unit packagekit.service entered failed state.
Apr 04 09:41:27 medusa systemd[1]: packagekit.service failed.


If I don't include --verbose on the ExecStart line, everything works correctly.

Is this a bug or intention? Can you help me run with --verbose by default?
Comment 1 Kamil Páral 2015-04-04 07:56:23 UTC
PackageKit-1.0.4-1.fc21.x86_64
Comment 2 Richard Hughes 2015-04-07 11:02:31 UTC
commit c86e358d934c2ce89ece86440d435d2fedcc122e
Author: Richard Hughes <richard@hughsie.com>
Date:   Tue Apr 7 11:35:52 2015 +0100

    Don't recursive lock the debug mutex when using --verbose without a tty
    
    Resolves: https://bugs.freedesktop.org/show_bug.cgi?id=89900


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.