openSUSE Bugs July 2020

bugs@lists.opensuse.org

1 participants
3607 discussions

[Bug 1003872] dracut creates faulty default cmdline argument
by bugzilla_noreply＠suse.com 01 Jul '20

01 Jul '20

https://bugzilla.suse.com/show_bug.cgi?id=1003872 https://bugzilla.suse.com/show_bug.cgi?id=1003872#c27 --- Comment #27 from Thomas Blume <thomas.blume(a)suse.com> --- I've created testpackages with a proposed patch at: https://build.opensuse.org/package/binaries/home:tsaupe:branches:openSUSE:L… Anyone who could give it a try? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1173550] zypper dumps core on specific subcommands lu, lp, pch
by bugzilla_noreply＠suse.com 01 Jul '20

01 Jul '20

https://bugzilla.suse.com/show_bug.cgi?id=1173550 Marcus Meissner <meissner(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |meissner(a)suse.com -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1173194] After several last updates laptops on I945 did not show graphics (nomodeset did not help anymore)
by bugzilla_noreply＠suse.com 01 Jul '20

01 Jul '20

https://bugzilla.suse.com/show_bug.cgi?id=1173194 https://bugzilla.suse.com/show_bug.cgi?id=1173194#c10 --- Comment #10 from Igor Kuznetsov <virex(a)mail.ru> --- Created attachment 839250 --> https://bugzilla.suse.com/attachment.cgi?id=839250&action=edit Xorg.0.log Updated, but problem only progressed. Now where is no sddm on a screen, only like a mouse cursor. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1172992] Chromium: Closing tab after using Picture-in-Picture crashes chromium
by bugzilla_noreply＠suse.com 01 Jul '20

01 Jul '20

https://bugzilla.suse.com/show_bug.cgi?id=1172992 Alynx Zhou <alynx.zhou(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |alynx.zhou(a)suse.com Assignee|screening-team-bugs(a)suse.de |tchvatal(a)suse.com -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1084631] GCC 8: nasm build fails
by bugzilla_noreply＠suse.com 01 Jul '20

01 Jul '20

https://bugzilla.suse.com/show_bug.cgi?id=1084631 https://bugzilla.suse.com/show_bug.cgi?id=1084631#c4 jun wang <junguo.wang(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |junguo.wang(a)suse.com --- Comment #4 from jun wang <junguo.wang(a)suse.com> --- I am testing nasm update, and when checking the url https://build.suse.de/build/SUSE:Maintenance:15602/SUSE_SLE-15_Update/x86_6…, I get many these output: [ 95s] cd test && perl -I./perllib -I. performtest.pl --nasm=../nasm *.asm [ 95s] Can't compare at _file_/bin file stdout [ 95s] Can't compare at _version/version file stdout [ 95s] Can't compare at a32offs/unoptimized file a32offs.bin [ 95s] Can't compare at a32offs/optimized file a32offs.bin is this OK? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1161036] New: pk-offline-update reports success despite failed update
by bugzilla_noreply＠novell.com 01 Jul '20

01 Jul '20

http://bugzilla.suse.com/show_bug.cgi?id=1161036 Bug ID: 1161036 Summary: pk-offline-update reports success despite failed update Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: GNOME Assignee: gnome-bugs(a)suse.de Reporter: martin.wilck(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- End user experience: - Klick "restart and update" in GNOME Software - Confirm restart - System boots - After a few minutes, system boots again - Logging in and restarting GNOME softwrare, the same list of updates is displayed again, with the same "Restart and Update" button - This can be repeated journalctl -b -1 shows this: > Jan 16 08:37:49 apollon pk-offline-update[1406]: status wait > Jan 16 08:37:49 apollon pk-offline-update[1406]: status setup > Jan 16 08:37:52 apollon pk-offline-update[1406]: status finished > Jan 16 08:37:52 apollon PackageKit[1449]: update-packages transaction /1_ebebddca from uid 0 finished with failed after 2901ms > Jan 16 08:37:52 apollon pk-offline-update[1406]: writing failed results > Jan 16 08:37:52 apollon pk-offline-update[1406]: failed to update system: There is no update candidate for post-build-checks-84.88+git> > Jan 16 08:37:52 apollon systemd[1]: systemd-rfkill.service: Succeeded. > Jan 16 08:38:02 apollon pk-offline-update[1406]: rebooting > Jan 16 08:38:02 apollon pk-offline-update[1406]: sent mode to plymouth 'shutdown' > Jan 16 08:38:02 apollon pk-offline-update[1406]: sent msg to plymouth 'Rebooting after installing updates…' > Jan 16 08:38:02 apollon systemd[1]: packagekit-offline-update.service: Succeeded. > Jan 16 08:38:02 apollon systemd[1]: Stopped Update the operating system whilst offline. So, pk-offline-update returns Success status even though it failed to do the update. The actual update problem was due to a version "correction" in post-build-checks that would cause the package to be downgraded: > ---------------------------------------------------------------------------- > r95 | dimstar_suse | 2020-01-10 16:47:24 | 7568a213422b18c1c6714e41fb98c0b2 | 84.87+git20200110.2d02f07 | rq762807 > > - Update to version 84.87+git20200110.2d02f07: > * Tweaks to make rpm-ndb build > * Detect name of coreutils package and don't remove it > - restore correct version installed version: 84.88+git20190716.5a0e034-1.1 candidate version: 84.87+git20200110.2d02f07-1.1 I have set "solver.dupAllowDowngrade = true" in zypp.conf. If I run "zypper dup -D -y --details, I get this: > ... > The following package is going to be downgraded: > post-build-checks > 84.88+git20190716.5a0e034-1.1 -> 84.87+git20200110.2d02f07-1.1 > noarch > openSUSE-Tumbleweed-Oss > openSUSE > ... > 544 packages to upgrade, 1 to downgrade, 10 new, 3 to remove, 1 to change arch. > Overall download size: 0 B. Already cached: 913.1 MiB. After the operation, additional 281.8 MiB will be used. > > Note: System reboot required. > Continue? [y/n/v/...? shows all options] (y): y > > Checking for file conflicts: [...........done] So, zypper handles this situation just fine, and finds no other conflicts. Arguably the PackageKit zypp plugin should be able to deal with this rather trivial conflict automatically. But that's not my main point: The real problem is that the error didn't propagate to GNOME software, which thus offers the same update again and again, providing no clue to the end user that something went wrong, let alone what it was. -- You are receiving this mail because: You are on the CC list for the bug.

2 4

[Bug 1173550] New: zypper dumps core on specific subcommands lu, lp, pch
by bugzilla_noreply＠suse.com 01 Jul '20

01 Jul '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1173550 Bug ID: 1173550 Summary: zypper dumps core on specific subcommands lu, lp, pch Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.1 Hardware: x86-64 OS: SUSE Other Status: NEW Severity: Normal Priority: P5 - None Component: libzypp Assignee: zypp-maintainers(a)suse.de Reporter: dcfleck(a)protonmail.ch QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- System: Lenovo ThinkPad Edge E531, OpenSUSE Leap 15.1 upgraded from 42.3. Problem: zypper dumps core when using any of the subcommands: lu, lp, pch. Error message is identical for each of the 3 cases: # zypper -vv lu Verbosity: 3 Initializing Target Checking whether to refresh metadata for Non-OSS Repository Checking whether to refresh metadata for Main Repository Checking whether to refresh metadata for Main Update Repository Checking whether to refresh metadata for Update Repository (Non-Oss) Loading repository data... Reading installed packages... Force resolution: No /usr/include/c++/7/bits/stl_vector.h:797: std::vector<_Tp, _Alloc>::reference std::vector<_Tp, _Alloc>::operator[](std::vector<_Tp, _Alloc>::size_type) [with _Tp = std::__cxx11::basic_string<char>; _Alloc = std::allocator<std::__cxx11::basic_string<char> >; std::vector<_Tp, _Alloc>::reference = std::__cxx11::basic_string<char>&; std::vector<_Tp, _Alloc>::size_type = long unsigned int]: Assertion '__builtin_expect(__n < this->size(), true)' failed. Aborted (core dumped) # zypper -V zypper 1.14.37 # tail /var/log/zypper.log 2020-06-30 18:47:00 <1> moira2.sourballs.org(18053) [libsolv++] PoolImpl.cc(logSat):123 done solving. 2020-06-30 18:47:00 <1> moira2.sourballs.org(18053) [libsolv++] PoolImpl.cc(logSat):123 2020-06-30 18:47:00 <1> moira2.sourballs.org(18053) [libsolv++] PoolImpl.cc(logSat):123 solver took 580 ms 2020-06-30 18:47:00 <1> moira2.sourballs.org(18053) [libsolv++] PoolImpl.cc(logSat):123 final solver statistics: 0 problems, 0 learned rules, 0 unsolvable 2020-06-30 18:47:00 <1> moira2.sourballs.org(18053) [libsolv++] PoolImpl.cc(logSat):123 solver_solve took 796 ms 2020-06-30 18:47:00 <1> moira2.sourballs.org(18053) [zypp::solver] SATResolver.cc(establish):222 Establish DONE 2020-06-30 18:47:00 <1> moira2.sourballs.org(18053) [zypp] TargetImpl.cc(updateFileContent):786 updating '/var/lib/zypp/LastDistributionFlavor' content. 2020-06-30 18:47:00 <1> moira2.sourballs.org(18053) [zypp] TargetImpl.cc(load):1177 Target loaded: 3376 resolvables 2020-06-30 18:47:00 <1> moira2.sourballs.org(18053) [zypper] repos.cc(load_resolvables):1759 Done loading resolvables 2020-06-30 18:47:00 <1> moira2.sourballs.org(18053) [zypper] basecommand.cc(defaultSystemSetup):199 -------------- Calling SAT Solver to establish the PPP status ------------------- [end of file] Not sure what other information would be helpful. I assume the problem is something in the machine's environment interacting badly with zypper, but I don't know what zypper is looking for at this point in the code that would cause this error. Because it is machine-specific, I don't really know what would need to be done to a machine to reproduce the error (I have a second identical laptop that does not have the problem). -- You are receiving this mail because: You are on the CC list for the bug.

1 0

Jump to page:

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

openSUSE Bugs July 2020