Home Wiki > SDB:Zypper troubleshooting
Sign up | Login

Revision as of 11:09, 1 December 2014 by Belphegor belbel (Talk | contribs)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

SDB:Zypper troubleshooting

tagline: From openSUSE

Zypper troubleshooting tips.

Verbose output

There is a global --verbose option that can be used multiple times to increase verbosity (2 levels currently) of zypper's output to find out what is going on. For example, use zypper -vv up.


Since version 0.8.0, the zypper log is by default at /var/log/zypper.log. The location of the log file can be changed using ZYPP_LOGFILE environment variable, e.g.

$ ZYPP_LOGFILE=zypper-refresh-updates.log zypper refresh updates

To enable excessive debug log, add ZYPP_FULLLOG=1 variable to the call.

To debug solver, set ZYPP_LIBSAT_FULLLOG=1.

Solver test case

Since version 0.8.7, zypper is able to generate a solver test case to help debugging problems related to package dependencies and libzypp's dependency resolver. To generate a test case, add the --debug-solver command option to commands like install, remove, update, dist-upgrade, verify, or source-install. For example:

$ zypper install --debug-solver MozillaFirefox

The test case files will be written into /var/log/zypper.solverTestCase directory. You can pack and compress and attach them to a bug report then.

Reporting a bug

When filing bugs, please use component libzypp and attach the log and zypper output. If you can easily reproduce the bug, there is no need to attach the whole log from previous runs. When reproducing the bug, prepend ZYPP_LOGFILE=logfile_name to the zypper command you are about to execute, and attach the file you specified, e.g.:

$ ZYPP_LOGFILE=zypper.log zypper -vv install MozillaFirefox

Ignore still running zypper

During development of applications, it can be useful to ignore a lock for zypper (don't try this on production machines!):

$ zypper ...