openSUSE Bugs May 2020

bugs@lists.opensuse.org

2 participants
3538 discussions

[Bug 987114] New: Bluetooth headset connected but not showing under 'Sound Settings'
by bugzilla_noreply＠novell.com 16 Nov '22

16 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=987114 Bug ID: 987114 Summary: Bluetooth headset connected but not showing under 'Sound Settings' Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Major Priority: P5 - None Component: GNOME Assignee: bnc-team-gnome(a)forge.provo.novell.com Reporter: damien.lloyd21(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:47.0) Gecko/20100101 Firefox/47.0 Build Identifier: On openSUSE Tumbleweed, my bluetooth headset pairs and connects successfully through GNOME's bluetooth interface, but after going to the 'Sound Settings' my bluetooth headset doesn't show up, even though it is paired up. Because I can't see my bluetooth headset under 'Sound Settings' it's not possible to re-route sound through it, which means I can't use my bluetooth headset. Reproducible: Always Steps to Reproduce: 1. Make bluetooth headset discoverable; 2. Open up GNOME's bluetooth interface and select bluetooth headset; 3. Connect to bluetooth headset; 4. Once paired, access 'Sound Settings': bluetooth headset doesn't show up. Actual Results: The bluetooth headset doesn't show up under 'Sound Settings' even though it is connected and paired. Expected Results: The bluetooth headset should appear under 'Sound Settings' so that sound can be re-routed through it. My headset is a UE MEGABOOM and it worked under Ubuntu 14.04/16.04 extremely well. It doesn't work under openSUSE Tumbleweed. -- You are receiving this mail because: You are on the CC list for the bug.

2 13

[Bug 1110245] New: Connection to online repositories should be HTTPS
by bugzilla_noreply＠novell.com 15 Nov '22

15 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1110245 Bug ID: 1110245 Summary: Connection to online repositories should be HTTPS Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.3 Hardware: All OS: All Status: NEW Severity: Enhancement Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: digitalmon(a)rambler.ru QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- Although the online repository servers support HTTPS connection, downloading of packets still occurs via the HTTP protocol. This compromises the security of users. If their connection to the Internet is intercepted, if they work through any proxy server, the attackers can modify the packages on the fly during the download. To install malware and spyware into target system. At the moment, you can only manually change the URLs of the repositories to https so that the packets are downloaded over a secure channel. I want that by default in the operating system the connection to the online-repositories, the downloading of packets, should be with HTTPS connection. This will make users' safety a step higher. I'm sure there will be less glitches, bugs in user systems. But Https is not a panacea. She is also vulnerable to the attack of MITM. The private surveilance service known to me, generates its own RSA-keys to encrypt the HTTPS, brute-force for them a digital signature so that the browser of user does not suspect forgery. The attacker's computer connects to the remote server by https, downloads packages, replaces executable files, infects them with a virus, and the user gives https traffic with his encryption key and a digital signature. But such an attack is not for everyone. To make it more difficult, you need to use long encryption keys and digital signatures on the repository servers. RSA4096 at least. I know that even LTE-connection to the Internet can be intercepted with using of special technical means and OpenLTE, so I do not trust to LTE. LTE-connection can work without encryption, and 3G connection seems to be always encrypted. A wired connection to the Internet, to intercept - generally easy. As PPPoe, as DHCP (DHCP is without authorization and verification of provider access point). The 3G modem with a good antenna has the same speed as the LTE. -- You are receiving this mail because: You are on the CC list for the bug.

2 4

[Bug 1170409] New: update-test-trivial: TW test maintenance updates do not work
by bugzilla_noreply＠novell.com 14 Nov '22

14 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1170409 Bug ID: 1170409 Summary: update-test-trivial: TW test maintenance updates do not work Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Maintenance Assignee: screening-team-bugs(a)suse.de Reporter: Andreas.Stieger(a)gmx.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- The test maintenance update is broken in openSUSE:Factory:Update. Installing update-test-trivial from the TW OSS repository does make the zypper maintenance update available/needed, despite it being in the repository. This indicates that the maintenance update stack is not being tested in Tumbleweed. Same for (at least) update-test-security. Install the non-updated package: $ zypper in --from tw-oss update-test-trivial $ zypper search -s -t package update-test-trivial.x86_64 S | Name | Type | Version | Arch | Repository ---+---------------------+---------+---------+--------+----------- v | update-test-trivial | package | 5-5.1 | x86_64 | tw-update i+ | update-test-trivial | package | 5-4.11 | x86_64 | tw-oss v | update-test-trivial | package | 5-4.1 | x86_64 | tw-update Update is not available: $ zypper lp No updates found. But a newer packages is available: $ zypper lu S | Repository | Name | Current Version | Available Version | Arch --+------------+---------------------+-----------------+-------------------+------- v | tw-update | update-test-trivial | 5-4.11 | 5-5.1 | x86_64 The patch seems to refer a previous package $ zypper info -t patch update-test-trivial Information for patch update-test-trivial: ------------------------------------------ Repository : tw-update Name : update-test-trivial Version : 1 Arch : noarch Vendor : BenniBrunner Status : applied Category : recommended Severity : low Created On : Thu Mar 1 11:28:21 2018 Interactive : --- Summary : Test-update for openSUSE Tumbleweed Description : This is a trivial test-update for openSUSE Tumbleweed. Provides : patch:update-test-trivial = 1 Conflicts : [4] update-test-trivial.src < 5-4.1 update-test-trivial.noarch < 5-4.1 update-test-trivial.x86_64 < 5-4.1 update-test-trivial.i586 < 5-4.1 -- You are receiving this mail because: You are on the CC list for the bug.

2 7

[Bug 1129466] New: fwupd cannot update BIOS with UEFI Secure Boot enabled because of missing fwupdx64.efi.signed
by bugzilla_noreply＠novell.com 10 Nov '22

10 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1129466 Bug ID: 1129466 Summary: fwupd cannot update BIOS with UEFI Secure Boot enabled because of missing fwupdx64.efi.signed Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: pujos.michael(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- fwdupd 1.2.3-2.1 cannot update the BIOS on my laptop because of this error: $fwupdmgr get-devices ... 20MBCTO1WW System Firmware DeviceId: 65b6a9dc7b7df18bdff003584b51bf21373e3aa6 Guid: 1e1fe415-74e8-49e1-9508-106b3d13d50d Guid: 230c8b18-8d9b-53ec-838b-6cfc0383493a Guid: 171800c9-1a51-5fd9-a32b-7b3999cb1c4e Plugin: uefi Flags: internal|require-ac|supported|registered|needs-reboot Version: 0.1.18 VersionLowest: 0.1.0 Icon: computer Created: 2019-03-15 UpdateError: /usr/lib/fwupd/efi/fwupdx64.efi.signed cannot be found Apparently, if Secure Boot is enabled (my case and I believe TW default on UEFI installs), it looks for /usr/lib/fwupd/efi/fwupdx64.efi.signed. This file is missing but it turns out that /usr/lib/fwupd/efi/fwupdx64.efi is present AND signed: $pesign -S -i /usr/lib/fwupd/efi/fwupdx64.efi --------------------------------------------- certificate address is 0x7f0e55679f78 Content was not encrypted. Content is detached; signature cannot be verified. The signer's common name is openSUSE Secure Boot Signkey The signer's email address is build(a)opensuse.org Signing time: Tue Mar 05, 2019 There were certs or crls included. --------------------------------------------- So the fix is simply so make a symlink and restart fwupd so it sees the change: $ln -s /usr/lib/fwupd/fwupdx64.efi /usr/lib/fwupd/fwupdx64.efi.signed $systemctl restart fwupd Then the error goes away in 'fwupdmgr get-devices' and you can supposedly update with 'fwupdmgr update' (didn't try it at updating the BIOS is rather scary and I do not absolutely need this update currently). So I think the package should be updated to make the symlink (or rename the file if keeping fwupdx64.efi is unecessary). -- You are receiving this mail because: You are on the CC list for the bug.

2 19

[Bug 1161823] New: Adding compress=zstd in fstab option in YaST2 on / partition result in "compression type 0x3 not supported"
by bugzilla_noreply＠novell.com 10 Nov '22

10 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1161823 Bug ID: 1161823 Summary: Adding compress=zstd in fstab option in YaST2 on / partition result in "compression type 0x3 not supported" Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: andythe_great(a)pm.me QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- Created attachment 828281 --> http://bugzilla.opensuse.org/attachment.cgi?id=828281&action=edit Step 1 of installation When installing OpenSUSE TW, by adding compress=zstd in fstab arbitrary option value will result in broken grub "compression type 0x3 not supported" even it grub already support zstd compression on btrfs. Or maybe I did something wrong. Installation process photos were attached. -- You are receiving this mail because: You are on the CC list for the bug.

2 37

[Bug 1098360] New: aide --init gives the error DBG: md_enable: algorithm 7 not available
by bugzilla_noreply＠novell.com 09 Nov '22

09 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1098360 Bug ID: 1098360 Summary: aide --init gives the error DBG: md_enable: algorithm 7 not available Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 Hardware: 64bit OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: chevy.stroker(a)yahoo.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- virt:~ # aide --init DBG: md_enable: algorithm 7 not available gcry_md_enable 7 failedAIDE initialized database at /var/lib/aide/aide.db.new Number of entries: 218651virt:~ # -- You are receiving this mail because: You are on the CC list for the bug.

2 7

[Bug 1028824] New: aide looking for a removed algorithm
by bugzilla_noreply＠novell.com 09 Nov '22

09 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1028824 Bug ID: 1028824 Summary: aide looking for a removed algorithm Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Minor Priority: P5 - None Component: Upgrade Problems Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: tschaefer(a)t-online.de QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- After starting: aide -i comes the following notice: DBG: md_enable: algorithm 7 not available -- You are receiving this mail because: You are on the CC list for the bug.

2 3

[Bug 1139017] New: aide gcry_md_enable 7 failure
by bugzilla_noreply＠novell.com 09 Nov '22

09 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1139017 Bug ID: 1139017 Summary: aide gcry_md_enable 7 failure Classification: openSUSE Product: openSUSE Backports Version: SLE-15-SP1 Hardware: x86-64 OS: SLES 15 Status: NEW Severity: Normal Priority: P5 - None Component: Packages Assignee: packagehub-bugs(a)suse.com Reporter: woe.2018(a)wizonet.ch QA Contact: packagehub-bugs(a)suse.com Found By: --- Blocker: --- This error occurs in openSuSE Leap 15 and openSuSE Leap 15.1 (which is not available ub in OS: and Version: selector above). The output of aide shows no longer the differ files - only the summary is available: aide_2019-06-23 gcry_md_enable 7 failedAIDE found differences between database and filesystem!! Summary: Total number of entries: 103548 Added entries: 18 Removed entries: 0 Changed entries: 17 Therefore it is no longer possible to identify the files that has changed. I think the error is based on this message: In output: gcry_md_enable 7 failed When started: DBG: md_enable: algorithm 7 not available -- You are receiving this mail because: You are on the CC list for the bug.

2 3

[Bug 1094780] New: Laptop with Intel+Nvidia hybrid graphics won't suspend after hibernation
by bugzilla_noreply＠novell.com 09 Nov '22

09 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1094780 Bug ID: 1094780 Summary: Laptop with Intel+Nvidia hybrid graphics won't suspend after hibernation Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-maintainers(a)forge.provo.novell.com Reporter: srid(a)rkmail.ru QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 771476 --> http://bugzilla.opensuse.org/attachment.cgi?id=771476&action=edit Log of kernel-vanilla + drm.debug=0x0e A laptop with hybrid graphics won't suspend after it was hibernated and restored. It may not happen on the fist time, but the main idea is that laptop stops suspending to ram at some point if it was hibernated at least one time. Also, it won't shut down gracefully, there are some error messages about nouveau errors and stalled CPU cores. I'm using kernel-vanilla, as kernel-default still has bug 1094751, but if you apply fix proposed in that report, kernel-default behaves identically to kernel-vanilla. -- You are receiving this mail because: You are on the CC list for the bug.

2 1

[Bug 1087375] New: openSUSE:Tools/osc: Bug -- Package internal error
by bugzilla_noreply＠novell.com 05 Nov '22

05 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1087375 Bug ID: 1087375 Summary: openSUSE:Tools/osc: Bug -- Package internal error Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: 3rd party software Assignee: ro(a)suse.com Reporter: luc14n0(a)linuxmail.org QA Contact: opensuse-communityscreening(a)forge.provo.novell.com Found By: --- Blocker: --- Created attachment 765332 --> http://bugzilla.opensuse.org/attachment.cgi?id=765332&action=edit The working directory compressed in a *.tar.xz file. After running checking in with `osc` I got this error: server does not accept filelist: <directory><entry hash="sha256:db932ad3676e6610047c61561b773da361df1b8e3f412aecc6cc0b7e7aa0428a" md5="5ef267ff27c590ec5d8975a8ee489767" name="baselibs.conf" /><entry hash="sha256:b98a9ea2ed5ea0a62d908182974e8a049fe7a890aad525b44a28bb5e44ca0d4c" md5="6b8f9f2beff3954b29085e7060b2f1e1" name="glibmm-2.57.1.tar.xz" /><entry hash="sha256:d97ebf807e146fcf3a6ae223fb495b0878d7f578a1edde2f3ddb04712993251b" md5="60130102823c2c4007295ce1b9e00fb5" name="glibmm2.changes" /><entry hash="sha256:11665c9da3c95c2ae9b2bb5d804ba9775387ef9d9c48f1a66b8f8b060b05ee07" md5="6a6c21ed626b67736b313ee88d02c455" name="glibmm2.spec" /></directory> missing: <directory error="missing" name="glibmm2"> <entry hash="sha256:d97ebf807e146fcf3a6ae223fb495b0878d7f578a1edde2f3ddb04712993251b" md5="60130102823c2c4007295ce1b9e00fb5" name="glibmm2.changes" /> </directory> Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/osc/babysitter.py", line 61, in run return prg.main(argv) File "/usr/lib/python2.7/site-packages/osc/cmdln.py", line 344, in main return self.cmd(args) File "/usr/lib/python2.7/site-packages/osc/cmdln.py", line 367, in cmd retval = self.onecmd(argv) File "/usr/lib/python2.7/site-packages/osc/cmdln.py", line 501, in onecmd return self._dispatch_cmd(handler, argv) File "/usr/lib/python2.7/site-packages/osc/cmdln.py", line 1232, in _dispatch_cmd return handler(argv[0], opts, *args) File "/usr/lib/python2.7/site-packages/osc/commandline.py", line 4612, in do_commit self._commit(subcmd, opts, args) File "/usr/lib/python2.7/site-packages/osc/commandline.py", line 4715, in _commit prj.commit(packages, msg=msg, files=prj_files, skip_local_service_run=skip_local_service_run, verbose=opts.verbose, can_branch=can_branch, force=opts.force) File "/usr/lib/python2.7/site-packages/osc/core.py", line 989, in commit self.commitExtPackage(pac, msg, todo, verbose=verbose, skip_local_service_run=skip_local_service_run) File "/usr/lib/python2.7/site-packages/osc/core.py", line 1079, in commitExtPackage p.commit(msg=msg, verbose=verbose, skip_local_service_run=skip_local_service_run) File "/usr/lib/python2.7/site-packages/osc/core.py", line 1540, in commit % (ET.tostring(filelist, encoding=ET_ENCODING), ET.tostring(sfilelist, encoding=ET_ENCODING))) PackageInternalError It's the second time I got this error in this last week. -- You are receiving this mail because: You are on the CC list for the bug.

2 2

← Newer
1
...
9
10
11
12
13
14
15
...
354
Older →

Jump to page:

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

openSUSE Bugs May 2020