December 2015 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 909567] New: scangearmp2 produces segfault in libpthread-2.18.so
by bugzilla_noreply＠novell.com 05 Apr '19

05 Apr '19

http://bugzilla.opensuse.org/show_bug.cgi?id=909567 Bug ID: 909567 Summary: scangearmp2 produces segfault in libpthread-2.18.so Classification: openSUSE Product: openSUSE 13.1 Version: Final Hardware: x86-64 OS: openSUSE 13.1 Status: NEW Severity: Normal Priority: P5 - None Component: Commercial Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: martin.gu(a)intergga.ch QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux i686; rv:34.0) Gecko/20100101 Firefox/34.0 Build Identifier: The application scangearmp2 is downloaded from http://de.canon.ch/Support/Consumer_Products/products/Fax__Multifunctionals… Installation with YaST or install.sh does not produce any error. But a start results in a memory access error. dmesg shows scangearmp2[9080]: segfault at 30 ip 00007fa0cf0f1294 sp 00007ffff2277a20 error 4 in libpthread-2.18.so[7fa0cf0e7000+18000] This error occurres with or withour a Canon Pixma MG7550 attached / switched on. Reproducible: Always Steps to Reproduce: 1.install scangearmp2 2.run scangearmp2 3. Actual Results: Application crashes with error message "Speicherzugriffsfehler" (memory access error) Expected Results: The application should be up and running, allowing to scan images I reported the error to Canon but I was informed that this is an error of the distribution (in libpthread-2.18.so) and that I should get help there. Unfortunately SANE does not yet support the Canon pixma MG7550 -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 955986] New: Caff unusable
by bugzilla_noreply＠novell.com 01 Apr '19

01 Apr '19

http://bugzilla.suse.com/show_bug.cgi?id=955986 Bug ID: 955986 Summary: Caff unusable Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.1 Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: security-team(a)suse.de Reporter: holgi(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- It is impossible to use caff since it reports syntac error no matter which options or flags you are using: holgi@opti:~> rpm -q signing-party signing-party-2.1-4.2.noarch holgi@opti:~> caff --version syntax error at /usr/bin/caff line 776, near "$handles{" Global symbol "@infhs" requires explicit package name at /usr/bin/caff line 778. Global symbol "@outfhs" requires explicit package name at /usr/bin/caff line 779. Global symbol "%opts" requires explicit package name at /usr/bin/caff line 781. Global symbol "%opts" requires explicit package name at /usr/bin/caff line 783. Global symbol "%opts" requires explicit package name at /usr/bin/caff line 784. Global symbol "%opts" requires explicit package name at /usr/bin/caff line 786. Global symbol "%opts" requires explicit package name at /usr/bin/caff line 786. Global symbol "%opts" requires explicit package name at /usr/bin/caff line 786. Global symbol "$handles" requires explicit package name at /usr/bin/caff line 788. Global symbol "@infhs" requires explicit package name at /usr/bin/caff line 788. Global symbol "@outfhs" requires explicit package name at /usr/bin/caff line 788. Global symbol "$handles" requires explicit package name at /usr/bin/caff line 789. Global symbol "@infhs" requires explicit package name at /usr/bin/caff line 789. Global symbol "$handles" requires explicit package name at /usr/bin/caff line 790. Global symbol "@outfhs" requires explicit package name at /usr/bin/caff line 790. Global symbol "%opts" requires explicit package name at /usr/bin/caff line 793. Global symbol "%opts" requires explicit package name at /usr/bin/caff line 793. Global symbol "@outfhs" requires explicit package name at /usr/bin/caff line 793. Global symbol "%opts" requires explicit package name at /usr/bin/caff line 794. Global symbol "@outfhs" requires explicit package name at /usr/bin/caff line 794. Global symbol "%opts" requires explicit package name at /usr/bin/caff line 799. Global symbol "%opts" requires explicit package name at /usr/bin/caff line 799. Global symbol "@outfhs" requires explicit package name at /usr/bin/caff line 799. Global symbol "%fh" requires explicit package name at /usr/bin/caff line 811. Global symbol "%fh" requires explicit package name at /usr/bin/caff line 812. Global symbol "%fh" requires explicit package name at /usr/bin/caff line 817. Global symbol "%opts" requires explicit package name at /usr/bin/caff line 818. Global symbol "%opts" requires explicit package name at /usr/bin/caff line 819. Global symbol "%opts" requires explicit package name at /usr/bin/caff line 820. Global symbol "%opts" requires explicit package name at /usr/bin/caff line 820. Global symbol "%opts" requires explicit package name at /usr/bin/caff line 823. Global symbol "%opts" requires explicit package name at /usr/bin/caff line 826. Global symbol "%fh" requires explicit package name at /usr/bin/caff line 831. syntax error at /usr/bin/caff line 844, near "}" /usr/bin/caff has too many errors. -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 918402] New: gpg2: signing-party does not work
by bugzilla_noreply＠novell.com 01 Apr '19

01 Apr '19

http://bugzilla.suse.com/show_bug.cgi?id=918402 Bug ID: 918402 Summary: gpg2: signing-party does not work Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: vcizek(a)suse.com Reporter: meissner(a)suse.com QA Contact: qa-bugs(a)suse.de CC: astieger(a)suse.com Found By: --- Blocker: --- signing-party does not work with gpg on 13.2. gpg: Fatal: '/suse/meissner/.caff/gnupghome/trustdb.gpg' kann nicht geöffnet werden: Datei oder Verzeichnis nicht gefunden Not all keys could be imported from your normal GnuPGHOME. Andreas debugged this: Bug in gpg2. http://bugs.g10code.com/gnupg/issue1622 http://git.gnupg.org/cgi-bin/gitweb.cgi?p=gnupg.git;a=commitdiff;h=07006c99… https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=751266 -- You are receiving this mail because: You are on the CC list for the bug.

1 11

[Bug 914537] New: after resume wicked seems to work but connection to the internet is absent
by bugzilla_noreply＠novell.com 27 Mar '19

27 Mar '19

http://bugzilla.opensuse.org/show_bug.cgi?id=914537 Bug ID: 914537 Summary: after resume wicked seems to work but connection to the internet is absent Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: 64bit OS: openSUSE 13.2 Status: NEW Severity: Critical Priority: P5 - None Component: KDE4 Applications Assignee: kde-maintainers(a)suse.de Reporter: pier_andreit(a)yahoo.it QA Contact: qa-bugs(a)suse.de CC: bwiedemann(a)suse.com, dimstar(a)opensuse.org, jnelson-suse(a)jamponi.net, kstreitova(a)suse.com, suse(a)bugs.jan.ritzerfeld.org, systemd-maintainers(a)suse.de Depends on: 899800 Found By: --- Blocker: --- +++ This bug was initially created as a clone of Bug #899800 +++ on my PC=Dell latitude E6510, RAM=8Gb, GPU=GT218 NVS 3100M, CPU=i7 Q 720 @ 1.60GHz, OS=opensuse 13.2 KDE= 4.14.3 after resume from suspend to RAM the network seems to works, networkmanager shows wired connection 1 connected, but thunderbird, firefox, chrome, chromium do not connect to internet, close them before suspend doesn't solve, restart them doesn't solve, logout and login again doesn't solve, reboot solve.... I suspect it happens when I change network from the suspend and the resume, for example if I suspend and resume using the same network at my home it works, if I change network, for example I suspend at my home and resume at work it doesn't works. a discussion here https://forums.opensuse.org/showthread.php/504498-wired-network-problem-on-… -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 899800] New: after suspend, sometimes networkmanager doesn't wake up
by bugzilla_noreply＠novell.com 27 Mar '19

27 Mar '19

http://bugzilla.opensuse.org/show_bug.cgi?id=899800 Bug ID: 899800 Summary: after suspend, sometimes networkmanager doesn't wake up Classification: openSUSE Product: openSUSE Factory Version: 201409* Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: jnelson-suse(a)jamponi.net QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Since upgrading to Factory from 13.1, I'm *deeply* impressed at the awesomeness I find. Pretty much everything works as well as, or better than, before. One thing doesn't: networkmanager sometimes needs to be kicked after restart. Not every time, but only some times. -- You are receiving this mail because: You are on the CC list for the bug.

1 11

[Bug 957198] New: btrfs subvolume delete does not work
by bugzilla_noreply＠novell.com 26 Mar '19

26 Mar '19

http://bugzilla.opensuse.org/show_bug.cgi?id=957198 Bug ID: 957198 Summary: btrfs subvolume delete does not work Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.1 Hardware: x86-64 OS: Other Status: NEW Severity: Minor Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: jmader2(a)gmu.edu QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- # btrfs subvolume show opt /opt Name: opt UUID: d031edb9-47b3-f34d-8402-7b574bdac5bd Parent UUID: - Received UUID: - Creation time: 2015-11-30 12:02:19 -0500 Subvolume ID: 261 Generation: 32 Gen at creation: 15 Parent ID: 257 Top level ID: 257 Flags: - Snapshot(s): # btrfs subvolume delete opt Delete subvolume (no-commit): '//opt' ERROR: cannot delete '//opt' - Invalid argument -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 939067] New: On OBS, %goinstall does something weired with find
by bugzilla_noreply＠novell.com 25 Mar '19

25 Mar '19

http://bugzilla.suse.com/show_bug.cgi?id=939067 Bug ID: 939067 Summary: On OBS, %goinstall does something weired with find Classification: openSUSE Product: openSUSE Factory Version: 201505* Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: wagner-thomas(a)gmx.at QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I followed https://en.opensuse.org/openSUSE:Packaging_Go#The_easy_and_the_stupid_way to create a spec file build a go package with OBS. However, %goinstall calls "find" wrongly and "find" aborts. The short log: + cd /home/abuild/rpmbuild/BUILD/go/src [ 67s] + find . -name rclone.go rclone_test.go redirect_stderr.go redirect_stderr_unix.go redirect_stderr_windows.go -exec install -Dm644 '{}' '/home/abuild/rpmbuild/BUILDROOT/go-rclone-1.17-3.1.x86_64/usr/share/go/contrib/src/pkg/{}' ';' [ 67s] find: paths must precede expression: rclone_test.go [ 67s] Usage: find [-H] [-L] [-P] [-Olevel] [-D help|tree|search|stat|rates|opt|exec] [path...] [expression] The long log: https://build.opensuse.org/package/live_build_log/home:Aikhjarto/rclone/ope… -- You are receiving this mail because: You are on the CC list for the bug.

1 8

[Bug 903889] New: incorrect routing with bridge interface
by bugzilla_noreply＠novell.com 11 Mar '19

11 Mar '19

http://bugzilla.opensuse.org/show_bug.cgi?id=903889 Bug ID: 903889 Summary: incorrect routing with bridge interface Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: PC OS: openSUSE 13.2 Status: NEW Severity: Normal Priority: P5 - None Component: Installation Assignee: yast2-maintainers(a)suse.de Reporter: comes(a)naic.edu QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- I have done a fresh installation of 13.2. I use static network parameters (no dhcp) and I selected the KVM Host Server pattern. This makes the installer to automatically select the network configuration: bridged configuration using wicked (which by the way I cannot override anymore during the setup after the first reboot because the "improved" installer decided I don't need to). The problem with this configuration (bridged network and no dhcp) is that the gateway get associated with the ethernet device and not the bridge device. It exists the file /etc/sysconfig/network/ifroute-eth0 which contains default <gateway ip> - eth0 but that's wrong. I can use yast to correct the routing and after that the routing configuration file is: /etc/sysconfig/network/ifroute-br0 containing: default <gateway ip> - br0 If during the installation I select dhcp the bridge has the proper routing. -- You are receiving this mail because: You are on the CC list for the bug.

1 9

[Bug 925873] New: resume fails after hibernate from Cinnamon, succeeds after hibernate from command line
by bugzilla_noreply＠novell.com 11 Mar '19

11 Mar '19

http://bugzilla.suse.com/show_bug.cgi?id=925873 Bug ID: 925873 Summary: resume fails after hibernate from Cinnamon, succeeds after hibernate from command line Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: schuetzm(a)gmx.net QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 629922 --> http://bugzilla.suse.com/attachment.cgi?id=629922&action=edit screenshot After installing systemd 210-25.16.1 via update, resume after hibernate from the Cinnamon shutdown dialog hangs, while everything works flawlessly when I use "echo -n disk > /sys/power/state". (Previously I had used systemd 210-879.1 from tsaupe repo IIRC, because of another bug which has since been resolved.) In my setup, I have encrypted /home and swap partitions. It correctly asks me for the password (in Plymouth), but then everything stops; there's only the Plymouth splash screen, which doesn't react to <Esc>, <Ctrl+Fn> or <Ctrl+Alt+Del>. I managed to circumvent the splash screen by pressing escape early; see the attached screen shot. The last thing printed is "Starting dracut pre-mount hook...", after that, even the cursor disappears. -- You are receiving this mail because: You are on the CC list for the bug.

1 78

[Bug 900099] New: smartmontools: generate_smartd_opts refers to init script
by bugzilla_noreply＠novell.com 08 Mar '19

08 Mar '19

http://bugzilla.suse.com/show_bug.cgi?id=900099 Bug ID: 900099 Summary: smartmontools: generate_smartd_opts refers to init script Classification: openSUSE Product: openSUSE Factory Version: 201410* Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: sbrabec(a)suse.com Reporter: lnussel(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- - /usr/lib/smartmontools/generate_smartd_opts refers to an init script that no longer exists - /usr/lib/smartmontools/generate_smartd_opts is never called AFAICS unless one uses YaST to edit /etc/sysconfig/smartmontools. Maybe the service file should call it before launching smartd? - /var/lib/smartmontools/smartd_opts should probably be moved to /run - rcsmartd symlink is missing -- You are receiving this mail because: You are on the CC list for the bug.

1 19