February 2016 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 943757] New: yast storage with ncurses does not due to nokogiri error message
by bugzilla_noreply＠novell.com 04 Oct '18

04 Oct '18

http://bugzilla.suse.com/show_bug.cgi?id=943757 Bug ID: 943757 Summary: yast storage with ncurses does not due to nokogiri error message Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: aschnell(a)suse.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- For various ruby programs I have installed a bunch of gems from different sources (which I have no overview of). Anyway, many ruby programs print an error during startup, this can be show using irb: aschnell@thalassa:~> irb irb(main):001:0> require "dbus" WARNING: Nokogiri was built against LibXML version 2.9.2, but has dynamically loaded 2.9.1 => true Unfortunately for yast ncurses this causes a program termination since stderr is in a bad state (I suppose closed): [Y2Ruby] binary/Y2RubyUtils.cc(y2_require):25 cannot require yast:Bad file descriptor @ io_write - <STDERR> at /usr/lib64/ruby/gems/2.1.0/gems/nokogiri-1.6.6.2/lib/nokogiri/version.rb:94:in `write' The rest of y2log is very misleading, e.g. stating the Storage.rb does not provide the module Storage. But with the Qt frontend YaST does start. The system is openSUSE 13.2 with YaST:Head and various ruby gems. -- You are receiving this mail because: You are on the CC list for the bug.

1 20

[Bug 944302] New: php5 and openhpi fails to build if MD5 and DES support disabled in net-snmp
by bugzilla_noreply＠novell.com 02 Oct '18

02 Oct '18

http://bugzilla.suse.com/show_bug.cgi?id=944302 Bug ID: 944302 Summary: php5 and openhpi fails to build if MD5 and DES support disabled in net-snmp Classification: openSUSE Product: openSUSE Factory Version: 201505* Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: meissner(a)suse.com Reporter: mlin(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- The latest net-snmp SR https://build.opensuse.org/request/show/323040 has disabled md5 and des support, however php5 and openhpi fails to build then. The same issue also effected Leap as https://build.opensuse.org/request/show/325654 which has the similar changes and pending in Leap for same reason. -- You are receiving this mail because: You are on the CC list for the bug.

1 18

[Bug 911587] New: Message at shutdown: "kernel: watchdog watchdog0: watchdog did not stop!"
by bugzilla_noreply＠novell.com 30 Sep '18

30 Sep '18

http://bugzilla.opensuse.org/show_bug.cgi?id=911587 Bug ID: 911587 Summary: Message at shutdown: "kernel: watchdog watchdog0: watchdog did not stop!" Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: x86-64 OS: openSUSE 13.2 Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: Ulrich.Windl(a)rz.uni-regensburg.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Each shutdown seems to hang for a while, then the message "kernel: watchdog watchdog0: watchdog did not stop!" appears. I guess this is not expected. (Next log message is "dmeventd[945]: dmeventd shutting down."; maybe this helps) -- You are receiving this mail because: You are on the CC list for the bug.

1 15

[Bug 961913] New: security/ecryptfs-utils: Bug %post execution of pam-config fails on 64bit because 32bit package is not installed
by bugzilla_noreply＠novell.com 27 Sep '18

27 Sep '18

http://bugzilla.opensuse.org/show_bug.cgi?id=961913 Bug ID: 961913 Summary: security/ecryptfs-utils: Bug %post execution of pam-config fails on 64bit because 32bit package is not installed Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: Other OS: openSUSE 42.1 Status: NEW Severity: Major Priority: P5 - None Component: 3rd party software Assignee: meissner(a)suse.com Reporter: darin(a)darins.net QA Contact: opensuse-communityscreening(a)forge.provo.novell.com Found By: --- Blocker: --- The execution of 'pam-config -a --ecryptfs' in %post fails on 64bit systems when 32bit pam libraries are installed, unless ecryptfs-utils-32bit is installed first. This failure causes the requisite pam configuration for ecryptfs to not be set, rendering it unusable until someone executes 'pam-config -a --ecryptfs'. # 2016-01-14 08:57:15 ecryptfs-utils-103-1.2.x86_64.rpm installed ok # Additional rpm output: # setting /sbin/mount.ecryptfs_private to root:root 4755. (wrong permissions 0755) # ERROR: module /lib/security/pam_ecryptfs.so is not installed. # warning: %post(ecryptfs-utils-103-1.2.x86_64) scriptlet failed, exit status 1 2016-01-14 08:57:15|install|ecryptfs-utils|103-1.2|x86_64|root@alpinist.athenex.com|repo-oss|89a0849166ef2c6382150534cc22166a6a4c6263| 2016-01-14 08:57:15|install|gnome-keyring-32bit|3.16.0-7.1|x86_64||repo-update|be9d8a3fb5b34ab38b848ed17f7b7a6b032cafd81a27b3e5c470d132b858baf5| 2016-01-14 08:57:15|install|libfreebl3-32bit|3.20.2-6.1|x86_64||repo-update|231b3bc9e17a5ce06b89e624340144157ef9f6908c321a7fe1c7e99bd430ba8f| 2016-01-14 08:57:15|install|mozilla-nspr-32bit|4.10.10-4.1|x86_64||repo-update|80d1c4c057c01ee579810038b726c74d85370eff3abe439e228810f27d6e4380| 2016-01-14 08:57:15|install|mozilla-nss-certs-32bit|3.20.2-6.1|x86_64||repo-update|7feacc18276f36d6711102568f0703fb55f0fe05a10f84019dd454d8feb8aa64| 2016-01-14 08:57:15|install|mozilla-nss-32bit|3.20.2-6.1|x86_64||repo-update|5e21bacb982e68e8ad02c1625fc04f272b81a9594dcf024d1e8cfbd53b60c4f4| 2016-01-14 08:57:16|install|libsoftokn3-32bit|3.20.2-6.1|x86_64||repo-update|ac71df84df77c5cd41f4c61dd9cd149fab9163bdd26f900f87b619496ae4c13e| 2016-01-14 08:57:16|install|libpkcs11-helper1-32bit|1.11-2.2|x86_64||repo-oss|77649250d1d56c1431454cfbdfa5463a0ca42ed1| 2016-01-14 08:57:16|install|ecryptfs-utils-32bit|103-1.2|x86_64||repo-oss|99c66f34c97fa274b0fcb044a3bfcd30b227f660| -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 957071] New: Blueberry OFF toggle does not actually turn off bluetooth
by bugzilla_noreply＠novell.com 09 Sep '18

09 Sep '18

http://bugzilla.opensuse.org/show_bug.cgi?id=957071 Bug ID: 957071 Summary: Blueberry OFF toggle does not actually turn off bluetooth Classification: openSUSE Product: openSUSE Tumbleweed Version: 2015* Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: sb56637(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Hello, the current Tumbleweed version of the Blueberry bluetooth management GUI (1.1.0) has a big ON/OFF toggle. However, this toggle does nothing. After toggling it OFF and re-opening Bluberry, it is again shown as ON. I am using the integrated bluetooth device of a Lenovo Thinkpad T530 laptop. -- You are receiving this mail because: You are on the CC list for the bug.

1 38

[Bug 904303] New: gnome-keyring hijacked the GPG socket
by bugzilla_noreply＠novell.com 07 Sep '18

07 Sep '18

http://bugzilla.opensuse.org/show_bug.cgi?id=904303 Bug ID: 904303 Summary: gnome-keyring hijacked the GPG socket Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: All OS: All Status: NEW Severity: Minor Priority: P5 - None Component: Xfce Assignee: gber(a)opensuse.org Reporter: jengelh(a)inai.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- gpg starts throwing new warnings since openSUSE 13.2. $ gpg -ab blah.txt You need a passphrase to unlock the secret key for user: "Jan Engelhardt <jengelh(a)gmx.de>" 4096-bit RSA key, ID 19FC338D, created 2011-05-09 gpg: WARNING: The GNOME keyring manager hijacked the GnuPG agent. gpg: WARNING: GnuPG will not work properly - please configure that tool to not interfere with the GnuPG system! $ env GPG_AGENT_INFO=/run/user/25121/keyring/gpg:0:1 $ lsof|grep keyring/gpg gnome-key 3799 jengelh 11u unix 0x0000000000000000 0t0 32398 /run/user/25121/keyring/gpg ... (started by xfce or so) -- You are receiving this mail because: You are on the CC list for the bug.

1 8

[Bug 941862] New: GNOME Software won't open RPM files
by bugzilla_noreply＠novell.com 03 Sep '18

03 Sep '18

http://bugzilla.opensuse.org/show_bug.cgi?id=941862 Bug ID: 941862 Summary: GNOME Software won't open RPM files Classification: openSUSE Product: openSUSE Distribution Version: 42.1 Milestone 1 Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: GNOME Assignee: bnc-team-gnome(a)forge.provo.novell.com Reporter: castar(a)cipelli.net QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:40.0) Gecko/20100101 Firefox/40.0 Build Identifier: When downloading RPMs from the internet, the option is given to open them with GNOME Software (presumably to install them). However, when doing so, Software opens with an error: "GetDetailsLocal not supported by backend". Reproducible: Always Steps to Reproduce: 1. Download an RPM for openSUSE. 2. Open it using GNOME Software. Actual Results: Gave error "GetDetailsLocal not supported by backend" Expected Results: Given details about the package. This happened on my old laptop and my new computer (HP G56 with AMD V140 and custom-built with AMD A10-7700K respectively). -- You are receiving this mail because: You are on the CC list for the bug.

1 11

[Bug 909418] New: when ejecting DVD using hardware button, system thinks DVD is still mounted
by bugzilla_noreply＠novell.com 27 Aug '18

27 Aug '18

http://bugzilla.opensuse.org/show_bug.cgi?id=909418 Bug ID: 909418 Summary: when ejecting DVD using hardware button, system thinks DVD is still mounted Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: x86-64 OS: openSUSE 13.2 Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: Ulrich.Windl(a)rz.uni-regensburg.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- When I used a mounted DVD (in a BluRay writer) and press eject-button on the drive, the media ejects, and I close the tray. In GNOME (at least) the system still thinks the media is mounted, even if I inserted another DVD into the drive in the meantime. -- You are receiving this mail because: You are on the CC list for the bug.

1 40

[Bug 953723] New: mksquashfs corrupts files
by bugzilla_noreply＠novell.com 08 Aug '18

08 Aug '18

http://bugzilla.opensuse.org/show_bug.cgi?id=953723 Bug ID: 953723 Summary: mksquashfs corrupts files Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: seife(a)novell.slipkontur.de QA Contact: qa-bugs(a)suse.de CC: duwe(a)suse.com, ms(a)suse.com Found By: --- Blocker: --- IMPORTANT: I have seen this both on 13.2 and on a patched SLES12 installation (no wonder, they have the same version of squashfs :-) While working with KIWI (OEM image, deployed either via PXE or as an ISO), I got spurious checksum errors when unpacking the image. A rebuild of the image often fixed the issue. Until yesterday, when there was no possibility to create a working image anymore. I was assuming something changed with my KIWI setup or a bug in kiwi. I investigated the issue and it comes down to the following: vbox-seife:~/oem # cat SLES_12_image1.x86_64-0.3.4.md5 b6a50a9e4a509b40ee192ee977cc5b48 312192 8192 vbox-seife:~/oem # md5sum SLES_12_image1.x86_64-0.3.4.raw b6a50a9e4a509b40ee192ee977cc5b48 SLES_12_image1.x86_64-0.3.4.raw vbox-seife:~/oem # mksquashfs SLES_12_image1.x86_64-0.3.4.raw SLES_12_image1.x86_64-0.3.4.md5 /tmp/SLES_12_image1.x86_64-0.3.4.raw.squashfs -no-progress Parallel mksquashfs: Using 2 processors Creating 4.0 filesystem on /tmp/SLES_12_image1.x86_64-0.3.4.raw.squashfs, block size 131072. Exportable Squashfs 4.0 filesystem, gzip compressed, data block size 131072 compressed data, compressed metadata, compressed fragments, compressed xattrs duplicates are removed Filesystem size 642142.91 Kbytes (627.09 Mbytes) 25.71% of uncompressed filesystem size (2497612.67 Kbytes) Inode table size 42177 bytes (41.19 Kbytes) 53.94% of uncompressed inode table size (78188 bytes) Directory table size 59 bytes (0.06 Kbytes) 64.13% of uncompressed directory table size (92 bytes) Number of duplicate files found 0 Number of inodes 3 Number of files 2 Number of fragments 2 Number of symbolic links 0 Number of device nodes 0 Number of fifo nodes 0 Number of socket nodes 0 Number of directories 1 Number of ids (unique uids + gids) 1 Number of uids 1 root (0) Number of gids 1 root (0) vbox-seife:~/oem # mount -t squashfs /tmp/SLES_12_image1.x86_64-0.3.4.raw.squashfs /mnt/ vbox-seife:~/oem # md5sum /mnt/SLES_12_image1.x86_64-0.3.4.raw 4f2653aea2424557a4341d1416d21389 /mnt/SLES_12_image1.x86_64-0.3.4.raw So the file got altered when packing up with mksquashfs. vbox-seife:~/oem # cmp -l /mnt/SLES_12_image1.x86_64-0.3.4.raw SLES_12_image1.x86_64-0.3.4.raw |head -1 2557459969 0 110 vbox-seife:~/oem # dd if=SLES_12_image1.x86_64-0.3.4.raw skip=$((2557459969/512))|hexdump -C 33+0 records in 33+0 records out 16896 bytes (17 kB) copied, 0.000102726 s, 164 MB/s 00000000 48 61 68 21 49 64 6f 6e 74 4e 65 65 64 45 46 49 |Hah!IdontNeedEFI| 00000010 f1 d9 c8 c6 e2 3f bd 48 89 b6 17 29 bc 94 dd 67 |.....?.H...)...g| 00000020 00 08 00 00 00 00 00 00 03 18 00 00 00 00 00 00 |................| 00000030 00 00 00 00 00 00 00 00 6c 00 65 00 67 00 61 00 |........l.e.g.a.| 00000040 63 00 79 00 00 00 00 00 00 00 00 00 00 00 00 00 |c.y.............| 00000050 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| * 00000080 28 73 2a c1 1f f8 d2 11 ba 4b 00 a0 c9 3e c9 3b |(s*......K...>.;| 00000090 f6 f0 20 26 9a 16 1e 40 a7 03 f1 5a ea c8 80 90 |.. &...@...Z....| 000000a0 00 20 00 00 00 00 00 00 03 60 06 00 00 00 00 00 |. .......`......| 000000b0 00 00 00 00 00 00 00 00 55 00 45 00 46 00 49 00 |........U.E.F.I.| 000000c0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| * 00000100 a2 a0 d0 eb e5 b9 33 44 87 c0 68 b6 b7 26 99 c7 |......3D..h..&..| 00000110 8b 4b b5 64 5c 86 ab 49 87 f5 13 a2 ba 7b 8f 98 |.K.d\..I.....{..| 00000120 00 68 06 00 00 00 00 00 03 c8 0f 00 00 00 00 00 |.h..............| 00000130 00 00 00 00 00 00 00 00 6c 00 78 00 62 00 6f 00 |........l.x.b.o.| 00000140 6f 00 74 00 00 00 00 00 00 00 00 00 00 00 00 00 |o.t.............| 00000150 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| * 00000180 a2 a0 d0 eb e5 b9 33 44 87 c0 68 b6 b7 26 99 c7 |......3D..h..&..| 00000190 b2 0b ef 75 36 86 a4 4f 8a 7c 42 20 08 af 33 28 |...u6..O.|B ..3(| 000001a0 00 d0 0f 00 00 00 00 00 80 37 4c 00 00 00 00 00 |.........7L.....| 000001b0 00 00 00 00 00 00 00 00 6c 00 78 00 6c 00 76 00 |........l.x.l.v.| 000001c0 6d 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |m...............| 000001d0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| * 00004000 45 46 49 20 50 41 52 54 00 00 01 00 5c 00 00 00 |EFI PART....\...| 00004010 82 ba 8f 32 00 00 00 00 ff 37 4c 00 00 00 00 00 |...2.....7L.....| 00004020 01 00 00 00 00 00 00 00 22 00 00 00 00 00 00 00 |........".......| 00004030 de 37 4c 00 00 00 00 00 8e 28 e4 1a a7 84 ae 48 |.7L......(.....H| 00004040 b2 d1 ff 8a 8b 14 2c 11 df 37 4c 00 00 00 00 00 |......,..7L.....| 00004050 80 00 00 00 80 00 00 00 3f cd f4 5d 00 00 00 00 |........?..]....| 00004060 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| * 00004200 vbox-seife:~/oem # dd if=/mnt/SLES_12_image1.x86_64-0.3.4.raw skip=$((2557459969/512))|hexdump -C 33+0 records in 33+0 records out 00000000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| * 00004200 16896 bytes (17 kB) copied, 0.000606308 s, 27.9 MB/s The last ~16.5kB are just zeroes. I then looked at the upstream git and found this: http://sourceforge.net/p/squashfs/code/ci/de03266983ceb62e5365aac84fcd3b2fd… Note that this bug is present in at least 13.2 and SLES12, and looking at the package I have no reason to believe it is not in Factory/Tumbleweed. -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 915996] New: LibreOffice doesn't show internal Help
by bugzilla_noreply＠novell.com 07 Aug '18

07 Aug '18

http://bugzilla.opensuse.org/show_bug.cgi?id=915996 Bug ID: 915996 Summary: LibreOffice doesn't show internal Help Classification: openSUSE Product: openSUSE Factory Version: 201502* Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: LibreOffice Assignee: bnc-team-ooo(a)forge.provo.novell.com Reporter: lazy.kent(a)opensuse.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- LibreOffice v4.4.0.2 doesn't show internal Help. Using locale "ru_RU". Calling Help from the menu "Help" or "F1" key opens a browser with URL https://help.libreoffice.org/scalc/.uno:HelpIndex?Language=ru&System=UNIX&V… (in case of calc) or https://help.libreoffice.org/swriter/.uno:HelpIndex?Language=ru&System=UNIX… (in case of writer). Installed packages: % rpm -qa | grep libreoffice libreoffice-math-4.4.0.2-1.1.x86_64 libreoffice-draw-4.4.0.2-1.1.x86_64 libreoffice-l10n-en-4.4.0.2-1.1.noarch libreoffice-icon-theme-crystal-4.4.0.2-1.1.noarch libreoffice-calc-extensions-4.4.0.2-1.1.x86_64 libreoffice-calc-4.4.0.2-1.1.x86_64 libreoffice-gnome-4.4.0.2-1.1.x86_64 libreoffice-icon-theme-oxygen-4.4.0.2-1.1.noarch libreoffice-writer-4.4.0.2-1.1.x86_64 libreoffice-branding-openSUSE-4.0-5.1.noarch libreoffice-4.4.0.2-1.1.x86_64 libreoffice-impress-4.4.0.2-1.1.x86_64 libreoffice-mailmerge-4.4.0.2-1.1.x86_64 libreoffice-base-4.4.0.2-1.1.x86_64 libreoffice-pyuno-4.4.0.2-1.1.x86_64 libreoffice-templates-ru-3.3-13.1.noarch libreoffice-icon-theme-galaxy-4.4.0.2-1.1.noarch libreoffice-filters-optional-4.4.0.2-1.1.x86_64 libreoffice-writer-extensions-4.4.0.2-1.1.x86_64 libreoffice-l10n-ru-4.4.0.2-1.1.noarch openSUSE Tumbleweed x86_64. And I remember, it was OK in 4.4.0.1. -- You are receiving this mail because: You are on the CC list for the bug.

1 16