Page 1 of 2 12 LastLast
Results 1 to 10 of 20

Thread: where is "detailed report" from update errors?

  1. #1
    Join Date
    Dec 2015
    Posts
    47

    Default where is "detailed report" from update errors?

    Hi,


    I often have dependency resolution fails when I update.

    These error messages that pop up are quite brief, but they refer to a "detailed report".
    Where is this detailed report? I just can't find it.

    Searching the forums it seems that a few people wondered where it is.


    Best
    Marc

  2. #2

    Default Re: where is "detailed report" from update errors?

    Quote Originally Posted by mrc View Post
    I often have dependency resolution fails when I update.
    What repos do you use?
    Please post a list:
    Code:
    zypper lr -d
    There shouldn't be dependency problems with the standard ones...

    These error messages that pop up are quite brief, but they refer to a "detailed report".
    Where is this detailed report? I just can't find it.
    Probably in /var/log/pk_backend_zypp.
    But it might be easier to just run "sudo zypper up" in a terminal window and check the output.

  3. #3
    Join Date
    Dec 2015
    Posts
    47

    Default Re: where is "detailed report" from update errors?

    no, it's no standard repo,

    marc@TheD:~> zypper lr -d
    # | Alias | Name | Aktiviert | GPG-Überprüfung | Aktualisieren | Priorität | Typ | URI | Dienst
    ---+-------------------------------------+---------------------------------------------------------+-----------+-----------------+---------------+-----------+--------+---------------------------------------------------------------------------------------------+-------
    1 | download.opensuse.org-non-oss | Haupt-Repository (NON-OSS) | Ja | (r ) Ja | Ja | 99 | yast2 | http://download.opensuse.org/distrib.../repo/non-oss/ |
    2 | download.opensuse.org-non-oss_1 | Aktualisierungs-Repository (Nicht-Open-Source-Software) | Ja | (r ) Ja | Ja | 99 | rpm-md | http://download.opensuse.org/update/leap/42.1/non-oss/ |
    3 | download.opensuse.org-oss | Haupt-Repository (OSS) | Ja | (r ) Ja | Ja | 99 | yast2 | http://download.opensuse.org/distrib...42.1/repo/oss/ |
    4 | download.opensuse.org-oss_1 | Hauptaktualisierungs-Repository | Ja | (r ) Ja | Ja | 99 | rpm-md | http://download.opensuse.org/update/leap/42.1/oss |
    5 | http-download.opensuse.org-29331b2e | home:Sauerland | Ja | (r ) Ja | Ja | 99 | rpm-md | http://download.opensuse.org/reposit...USE_Leap_42.1/ |
    6 | http-download.opensuse.org-53f44a1e | openSUSE:Leap:42.1 | Ja | (r ) Ja | Ja | 99 | yast2 | http://download.opensuse.org/distrib...42.1/repo/oss/ |
    7 | http-download.opensuse.org-6b62d099 | openSUSE:Leap:42.1 | Ja | (r ) Ja | Ja | 99 | yast2 | http://download.opensuse.org/distrib...42.1/repo/oss/ |
    8 | http-download.opensuse.org-90fbc023 | home:beyerle:IAC | Ja | (r ) Ja | Ja | 99 | rpm-md | http://download.opensuse.org/reposit...USE_Leap_42.1/ |
    9 | openSUSE-42.1-0 | openSUSE-42.1-0 | Nein | ---- | Nein | 99 | yast2 | cd:///?devices=/dev/disk/by-id/ata-VBOX_CD-ROM_VB2-01700376 |
    10 | openSUSE_42.1 | openSUSE_42.1 | Ja | (r ) Ja | Ja | 99 | rpm-md | http://download.opensuse.org/reposit...USE_Leap_42.1/ |
    11 | packman.inode.at-suse | Packman Repository | Ja | (r ) Ja | Ja | 99 | rpm-md | http://ftp.gwdg.de/pub/linux/misc/pa...USE_Leap_42.1/ |
    12 | repo-non-oss | openSUSE-Leap-42.1-Non-Oss | Nein | ---- | Ja | 99 | NONE | http://download.opensuse.org/distrib.../repo/non-oss/ |
    13 | repo-oss | openSUSE-Leap-42.1-Oss | Ja | (r ) Ja | Ja | 99 |p://download.opensuse.org/distribution/leap/42.1/repo/oss/ |
    14 | repo-source | openSUSE-Leap-42.1-Source | Ja | (r ) Ja | Ja | 99 |p://download.opensuse.org/source/distribution/leap/42.1/repo/oss/ |
    15 | repo-tuxedo-computers | TUXEDO Computers - openSUSE leap | Ja | (r ) Ja | Ja | 99 |p://rpm.tuxedocomputers.com/opensuse/leap |
    16 | repo-update | openSUSE-Leap-42.1-Update | Ja | (r ) Ja | Ja | 99 |p://download.opensuse.org/update/leap/42.1/oss/ |
    17 | repo-update-non-oss | openSUSE-Leap-42.1-Update-Non-Oss | Ja | (r ) Ja | Ja | 99 |p://download.opensuse.org/update/leap/42.1/non-oss/ |
    I ran zypper up and 3 of 4 errors are gone. (These were ffmpeg updates)

    The last one remaning is:
    openSUSE-2016-37(1) security update

    Nevertheless I would be interested in how to show this "detailed report"

  4. #4
    Join Date
    Aug 2010
    Location
    Chicago suburbs
    Posts
    12,777
    Blog Entries
    3

    Default Re: where is "detailed report" from update errors?

    Quote Originally Posted by mrc View Post
    I often have dependency resolution fails when I update.

    These error messages that pop up are quite brief, but they refer to a "detailed report".
    Where is this detailed report? I just can't find it.
    I've never been able to find that "detailed report". The update applet should tell us where to find it (IMO). So I see this as a flaw in that applet. However, I have not reported as a bug, since I prefer to turn off the update applet and use Yast and zypper, which do give better messages.
    openSUSE Leap 15.1; KDE Plasma 5;
    testing Leap 15.2Alpha

  5. #5

    Default Re: where is "detailed report" from update errors?

    Quote Originally Posted by mrc View Post
    no, it's no standard repo,
    Ok, that's likely the reason for your update problems.
    I don't see anything particularly wrong there, except some duplicates, #1 to #7 in particular.
    You could remove them but they shouldn't cause a problem either.

    But especially in case of updates it might take a while until they propagate to those other repos.

    And some repos *might* be setup to build against openSUSE:Leap:42.1 standard instead of openSUSE:Leap:42.1:Update, which can "break" them if there are updates. That's up to the maintainers of the particular repos though.

    As a side-note: next time please post something like this in [CODE] tags (''#" button in the editor's toolbar) instead of QUOTE's, so that the URLs don't get truncated. Makes it easier for people trying to help you...

    I ran zypper up and 3 of 4 errors are gone. (These were ffmpeg updates)
    Ok, so those were probably just "timing" issues, the update should have worked now with the desktop's updater as well I suppose.

    The last one remaning is:
    openSUSE-2016-37(1) security update
    Hard to say without the explicit error message.
    Can you please post that?

    I'm not (yet) running Leap 42.1 myself and have no idea what the "openSUSE-2016-37(1) security update" is about.

    Nevertheless I would be interested in how to show this "detailed report"
    Well, I already told you all that I know about it.

  6. #6
    Join Date
    Jun 2008
    Location
    Podunk
    Posts
    27,108
    Blog Entries
    15

    Default Re: where is "detailed report" from update errors?

    Hi
    I think they mean packagekit....

    Code:
    pkcon -v get-details openSUSE-2016-37
    
    18:45:28    PackageKit          Verbose debugging enabled (on console 1)
    18:45:28    PackageKit          filter=(null), filters=0
    18:45:28    PackageKit          resolving 1 packages
    18:45:28    PackageKit          role now resolve
    Resolving                     [                         ] (0%)  18:45:29    PackageKit          adding state 0x557e8b8040d0
    18:45:29    PackageKit          role now get-details
                                  [=========================]         
    Getting details               [=========================]         
    Querying                      [                         ] (0%)  18:45:29    PackageKit          notify::connected
    18:45:29    PackageKit          skipping as the same
                                  [=========================]         
    Finished                      [                         ] (0%)  18:45:29    PackageKit          remove state 0x557e8b8040d0
                                  [=========================]         
    Package description
      package:     openSUSE-2016-37-1.noarch
      summary:     
      license:     
      group:       unknown
      description: 
    This update for libebml, libmatroska fixes the following security issues:
    
    Vulnerabilities fixed in libebml:
    
    * Cisco TALOS-CAN-0036: Invalid memory access when reading from a UTF-8 string resulted in a heap information leak (bsc#961031).
    * Cisco TALOS-CAN-0037: Deeply nested elements with infinite size use-after-free and multiple free (bsc#961031).
    * Invalid mempry access resulted in heap information leak
    
    Vulnerabilities fixed in libmatroska:
    * invalid memory access when reading specially crafted data lead to a heap information leak.
    
      size:        0 bytes
      url:
    Maybe it provides other info on error....
    Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
    SUSE SLE, openSUSE Leap/Tumbleweed (x86_64) | GNOME DE
    If you find this post helpful and are logged into the web interface,
    please show your appreciation and click on the star below... Thanks!

  7. #7

    Default Re: where is "detailed report" from update errors?

    The 'detailed report' message is also seen when the kde crash reporter pops up. If I am unable to load the requested debug files the reporter says refer to the 'detailed report'. I've looked at /var/log/pk_backend_zypp and don't find it informative regarding this situation. When the reporter attempts to download debug files it opens a terminal window and writes a few lines to the screen and then closes so fast that terminal window and leaves me 'in the dark' as to what was written to the screen.

    When I get time to play with this again I'm going to set up a camera and try to capture the output. I should not need to do that. Since the purpose of debugging is to find out what is wrong I would think that if there is a problem the terminal window should remain open so the user can see what is wrong and then prompt the user to close it.

    Or a log file should be created when the crash reporter appears.

    jon

  8. #8

    Default AW: where is "detailed report" from update errors?

    Quote Originally Posted by malcolmlewis View Post
    Code:
    Package description
      package:     openSUSE-2016-37-1.noarch
      summary:     
      license:     
      group:       unknown
      description: 
    This update for libebml, libmatroska fixes the following security issues:
    
    Vulnerabilities fixed in libebml:
    
    * Cisco TALOS-CAN-0036: Invalid memory access when reading from a UTF-8 string resulted in a heap information leak (bsc#961031).
    * Cisco TALOS-CAN-0037: Deeply nested elements with infinite size use-after-free and multiple free (bsc#961031).
    * Invalid mempry access resulted in heap information leak
    
    Vulnerabilities fixed in libmatroska:
    * invalid memory access when reading specially crafted data lead to a heap information leak.
    
      size:        0 bytes
      url:
    Maybe it provides other info on error....
    All right, then it's likely this problem:
    http://bugzilla.opensuse.org/show_bug.cgi?id=961994

    An update to fix the dependencies is on the way.

    Quote Originally Posted by 6520302 View Post
    The 'detailed report' message is also seen when the kde crash reporter pops up. If I am unable to load the requested debug files the reporter says refer to the 'detailed report'. I've looked at /var/log/pk_backend_zypp and don't find it informative regarding this situation.
    The KDE bug reporter tool doesn't use PackageKit at all, it uses zypper directly (the KF5 version opens a Konsole for that as you describe).
    So obviously you won't find any info in PackageKit's log.

    I'm not sure at the moment what happens when the debuginfo files are not found, but for this to work you have to enable repo-debug and repo-debug-update in YaST->Software Repositories.
    There was a problem with Leap's debug-update repo though (it contained the wrong files), I'm not sure if this has been fixed already.

    When I get time to play with this again I'm going to set up a camera and try to capture the output. I should not need to do that. Since the purpose of debugging is to find out what is wrong I would think that if there is a problem the terminal window should remain open so the user can see what is wrong and then prompt the user to close it.
    Well, that terminal window is not supposed to let you do some debugging. You have the "Debug with GDB" button for that.
    The terminal window is only used to run zypper to install the debuginfo packages.

    Btw, this is handled by a (distribution specific) shell script: /usr/bin/installdbgsymbols.sh

    Feel free to improve it and submit a better version.

  9. #9
    Join Date
    Dec 2015
    Posts
    47

    Default Re: where is "detailed report" from update errors?

    Quote Originally Posted by wolfi323 View Post
    Hard to say without the explicit error message.
    Can you please post that?
    That's exactly the point.

    A detailed error message would help here. And the applet refers to a detailed report. However, it doesn't provide it.

  10. #10

    Default Re: where is "detailed report" from update errors?

    Quote Originally Posted by mrc View Post
    That's exactly the point.
    No, it's not.
    I asked about zypper's output.

    A detailed error message would help here. And the applet refers to a detailed report. However, it doesn't provide it.
    Yes. But as I wrote already, the only PackageKit log I am aware of is /var/log/pk_backend_zypp, maybe this is what it refers too.
    And that log depends on the PAckageKit backend in use (PackageKit is distribution agnostic and provides backends for the different distributions/package management systems).
    Last edited by wolfi323; 15-Jan-2016 at 13:17.

Page 1 of 2 12 LastLast

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •