October 2021 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1140585] New: cryfs - 0.10.0-1.3 - Illegal instruction on AMD Phenom II X4 965 Processor
by bugzilla_noreply＠novell.com 05 Aug '22

05 Aug '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1140585 Bug ID: 1140585 Summary: cryfs - 0.10.0-1.3 - Illegal instruction on AMD Phenom II X4 965 Processor Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: palica(a)liguros.net QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Trying to use cryfs on an AMD PC: palica@sucellus:~> cryfs .Private/ 9_Private Illegal instruction (core dumped) palica@sucellus:~> sudo cryfs .Private/ 9_Private -o allow_other Illegal instruction palica@sucellus:~> zypper info cryfs Loading repository data... Reading installed packages... Information for package cryfs: ------------------------------ Repository : Main Repository (OSS) (20190704) Name : cryfs Version : 0.10.0-1.3 Arch : x86_64 Vendor : openSUSE Installed Size : 5.5 MiB Installed : Yes Status : up-to-date Source package : cryfs-0.10.0-1.3.src Summary : CryFS encryption Description : CryFS provides a FUSE-based mount that encrypts file contents, file sizes, metadata and directory structure. It uses encrypted same-size blocks to store both the files themselves and the blocks' relations to one another. These blocks are stored as individual files in the base directory, which can then be synchronized to remote storage (using an external tool). palica@sucellus:~> dmesg|tail [ 667.314215] BTRFS info (device dm-0): qgroup scan completed (inconsistency flag cleared) [ 891.504820] traps: cryfs[17825] trap invalid opcode ip:5596343a66df sp:7ffff48b2638 error:0 in cryfs[559634356000+20f000] [ 911.655522] traps: cryfs[18281] trap invalid opcode ip:5568d347c6df sp:7ffec8878018 error:0 in cryfs[5568d342c000+20f000] palica@sucellus:~> lscpu Architecture: x86_64 CPU op-mode(s): 32-bit, 64-bit Byte Order: Little Endian Address sizes: 48 bits physical, 48 bits virtual CPU(s): 4 On-line CPU(s) list: 0-3 Thread(s) per core: 1 Core(s) per socket: 4 Socket(s): 1 NUMA node(s): 1 Vendor ID: AuthenticAMD CPU family: 16 Model: 4 Model name: AMD Phenom(tm) II X4 965 Processor Stepping: 3 CPU MHz: 800.000 CPU max MHz: 3400.0000 CPU min MHz: 800.0000 BogoMIPS: 6830.70 Virtualization: AMD-V L1d cache: 64K L1i cache: 64K L2 cache: 512K L3 cache: 6144K NUMA node0 CPU(s): 0-3 Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm 3dnowext 3dnow constant_tsc rep_good nopl nonstop_tsc cpuid extd_apicid pni monitor cx16 popcnt lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs skinit wdt hw_pstate vmmcall npt lbrv svm_lock nrip_save I am happy to provide any other info needed. Thanks for help. PS: was already not working with 20190606, I thought that upgrading to latest would solve the issue. IMHO missing some cpu instruction set maybe? -- You are receiving this mail because: You are on the CC list for the bug.

2 3

[Bug 1190346] New: Thunderbird cannot connect after re-connecting to network or after resume from suspend
by bugzilla_noreply＠suse.com 05 Aug '22

05 Aug '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1190346 Bug ID: 1190346 Summary: Thunderbird cannot connect after re-connecting to network or after resume from suspend Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.3 Hardware: x86-64 OS: openSUSE Leap 15.3 Status: NEW Severity: Normal Priority: P5 - None Component: X11 Applications Assignee: screening-team-bugs(a)suse.de Reporter: obs(a)akr.yagii.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 852399 --> http://bugzilla.opensuse.org/attachment.cgi?id=852399&action=edit Partial TB log. From 15:25:51 on, the WLAN has been operational Reproduction: 1) Disconnect WLAN with KDE Network Manager 2) Start Thunderbird 3) Wait until it gives the "cannot connect" message 4) Connect WLAN with KDE Network Manager 5) Press "Get Messages" in Thunderbird 6) Expect "cannot connect" message, goto step 5) ad infinitum The issue also occurs after resuming from suspend state, or on a fresh login where Thunderbird is auto-started in the background and KDE is waiting for wallet credentials, before it connects to a WLAN with user specific credentials. Sometimes Firefox exhibits the same problem, however, I did not try to reproduce this, as for me the issue with Thunderbird is far more annoying. The problem existed throughout Leap 15.2, 15.3 on this system. I have attached a TB log, slightly censored for privacy. Workaround: - Restart Thunderbird -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1179539] New: cryfs crashes with "Illegal hardware instruction"
by bugzilla_noreply＠suse.com 04 Aug '22

04 Aug '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1179539 Bug ID: 1179539 Summary: cryfs crashes with "Illegal hardware instruction" Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: trmdi(a)yandex.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Install cryfs from the official repo, when I run it from the terminal, it crashes with the error: Illegal hardware instruction - Upstream bug report: https://github.com/cryfs/cryfs/issues/348 When I try compiling it without some flags set by openSUSE, it runs. - See this diff: https://build.opensuse.org/package/rdiff/home:trmdi/cryfs?opackage=cryfs&op… -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1180132] New: roundcubemail should recommend httpd, not require lighttpd
by bugzilla_noreply＠suse.com 03 Aug '22

03 Aug '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1180132 Bug ID: 1180132 Summary: roundcubemail should recommend httpd, not require lighttpd Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Apache Assignee: bnc-team-apache(a)forge.provo.novell.com Reporter: jimc(a)jfcarter.net QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Versions: roundcubemail-1.4.9-2.1.noarch (updated 2020-12-15, yesterday) lighttpd-1.4.55-4.1.x86_64 apache2-2.4.46-9.1.x86_64 roundcubemail newly requires lighttpd by name. On my webserver, Apache is the HTTP infrastructure that sends out RoundCube. I hit some snarl-ups with both lighttpd and apache2 installed together (my hacks, not your fault). I wanted to just de-install lighttpd, but roundcubemail has a hard requirement for it. So instead I'm fixing the snarl-up and letting lighttpd sit unused, until it's no longer required. Lighttpd is a nice package and I used it on a project where a lightweight webserver was needed, but in this case roundcubemail needs to defer to the sysop's choice of webserver. Could you please refer to "httpd" as the facility needed by roundcubemail rather than picking a specific one of the various available webservers? Both apache2 and lighttpd provide this generic facility, and I assume that nginx does also. Also, it's a little bizarre and inefficient to install roundcubemail on a different host from the webserver and then make it available to the webserver on a SAN-like kludge like NFS, but that kind of baroque storage architecture seems to be the name of the game in the enterprise today. I'd also like you to change "require" to "recommend" to accommodate situations like that. I'm surprised not to see any hits in a bug search for "roundcubemail lighttpd" that I could add a "mee too" comment to. -- You are receiving this mail because: You are on the CC list for the bug.

1 12

[Bug 1187513] New: Spanish keyboard randomly stops working in some applications
by bugzilla_noreply＠suse.com 03 Aug '22

03 Aug '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1187513 Bug ID: 1187513 Summary: Spanish keyboard randomly stops working in some applications Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Major Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: teo8976(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- On Spanish keyboards (among others, I guess), you type accented characters such as "��" or "��" by hitting the key for the accent ("`" or "��" in the examples above) followed by the letter. This normally works in all applications that I've ever tried in OpenSUSE. Starting recently, it sometimes randomly happens that this suddenly stops working in some applications but not others. When this happens, hitting the accent key followed by a letter results in just the plain unaccented letter. For example, "`"+"e" results in "e" instead of "��". Until today (and since it started happening a few days ago), I had only seen this in Kate. It would stop working in Kate while still working in other applications (usually I would try Chrome) and more importantly, it would get fixed by restarting Kate. Today it happened once more but it also started failing in Konsole and Telegram Desktop. This time, restarting any of the affected application would NOT fix that application. And even restarting all the apparently affected applications didn't. Rebooting did. I reported this to KDE because initially I was observing it only in Kate but they told me: """" Looks like the Qt key composition is broken for you. That would explain why this fails for Qt applications (Telegram Desktop is Qt based, too). I would propose to report this upstream to openSUSE. This seems to be no KDE/Kate specific issue. """" https://bugs.kde.org/show_bug.cgi?id=438820 Operating System: openSUSE Tumbleweed 20210612 KDE Plasma Version: 5.22.0 KDE Frameworks Version: 5.82.0 Qt Version: 5.15.2 Kernel Version: 5.12.9-1-default (64-bit) Graphics Platform: X11 Processors: 8 �� Intel�� Core�� i7-1065G7 CPU @ 1.30GHz Memory: 7.3 GiB of RAM Graphics Processor: Mesa DRI Intel�� Iris�� Plus Graphics -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1186870] New: python-rpm-macros different dependency generated python-six
by bugzilla_noreply＠suse.com 02 Aug '22

02 Aug '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1186870 Bug ID: 1186870 Summary: python-rpm-macros different dependency generated python-six Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: rpm(a)fthiessen.de QA Contact: qa-bugs(a)suse.de CC: mcepl(a)suse.com Found By: --- Blocker: --- I am not sure if this is an issue with the python-rpm-macros package or python-six. If you use the dependency generator and your package uses python-six it will generate a dependency like this: > python3.6dist(six) >= 1.10 But this can not be satisfied, as python-six only provides > python36-six = 1.16.0-103.2 -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1191088] New: perl-Bootloader: finish UsrMerge, install to /usr
by bugzilla_noreply＠suse.com 02 Aug '22

02 Aug '22

https://bugzilla.suse.com/show_bug.cgi?id=1191088 Bug ID: 1191088 Summary: perl-Bootloader: finish UsrMerge, install to /usr Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: snwint(a)suse.com Reporter: lnussel(a)suse.com QA Contact: qa-bugs(a)suse.de Blocks: 1191054 Found By: --- Blocker: --- Following up on the discussion on the Factory list https://lists.opensuse.org/archives/list/factory@lists.opensuse.org/message… All packages installing files into /bin, /sbin, /lib and /lib64 should change the location to the counterpart in /usr instead. Please consider doing that for perl-Bootloader. If perl-Bootloader still needs to build for released distros you may keep the legacy locations within a "%if %suse_version < 1550" block of course. If you do that, please do *NOT* install symlinks from/to /usr as it was done with some packages in the past. Move the files in question instead. -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1191074] New: makedev: finish UsrMerge, install to /usr
by bugzilla_noreply＠suse.com 02 Aug '22

02 Aug '22

https://bugzilla.suse.com/show_bug.cgi?id=1191074 Bug ID: 1191074 Summary: makedev: finish UsrMerge, install to /usr Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: puzel(a)suse.com Reporter: lnussel(a)suse.com QA Contact: qa-bugs(a)suse.de Blocks: 1191054 Found By: --- Blocker: --- Following up on the discussion on the Factory list https://lists.opensuse.org/archives/list/factory@lists.opensuse.org/message… All packages installing files into /bin, /sbin, /lib and /lib64 should change the location to the counterpart in /usr instead. Please consider doing that for makedev. If makedev still needs to build for released distros you may keep the legacy locations within a "%if %suse_version < 1550" block of course. If you do that, please do *NOT* install symlinks from/to /usr as it was done with some packages in the past. Move the files in question instead. -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1190649] New: go1.17 release tracking
by bugzilla_noreply＠suse.com 01 Aug '22

01 Aug '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1190649 Bug ID: 1190649 Summary: go1.17 release tracking Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Development Assignee: screening-team-bugs(a)suse.de Reporter: jkowalczyk(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- go1.17 (released 2021-08-16) is a major release of Go. Minor releases of go1.17.x will be provided through August 2022. This issue tracks go1.17.x releases packaged and submitted initially to openSUSE:Factory and can be referenced in submissions to additional repositories. Go Release Cycle https://github.com/golang/go/wiki/Go-Release-Cycle Go Release history https://golang.org/doc/devel/release.html -- You are receiving this mail because: You are on the CC list for the bug.

1 15

[Bug 1191047] New: sssd: use %_pam_moduledir
by bugzilla_noreply＠suse.com 01 Aug '22

01 Aug '22

https://bugzilla.suse.com/show_bug.cgi?id=1191047 Bug ID: 1191047 Summary: sssd: use %_pam_moduledir Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: scabrero(a)suse.com Reporter: lnussel(a)suse.com QA Contact: qa-bugs(a)suse.de Blocks: 1190946 Found By: --- Blocker: --- The pam package offers a number of macros to avoid hardcoding directory names in spec files: https://build.opensuse.org/package/view_file/openSUSE:Factory/pam/macros.pam Please consider using at least the %_pam_moduledir macro in order to have the package follow UsrMerge. -- You are receiving this mail because: You are on the CC list for the bug.

1 1