May 2014 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 829430] New: [Crash] Libreoffice 4.0 stable: missing dependency libmysqlclient_r.so for libreoffice-base-drivers-mysql package
by bugzilla_noreply＠novell.com 01 Jul '16

01 Jul '16

https://bugzilla.novell.com/show_bug.cgi?id=829430 https://bugzilla.novell.com/show_bug.cgi?id=829430#c0 Summary: [Crash] Libreoffice 4.0 stable: missing dependency libmysqlclient_r.so for libreoffice-base-drivers-mysql package Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Critical Priority: P5 - None Component: LibreOffice AssignedTo: bnc-team-ooo(a)forge.provo.novell.com ReportedBy: dennisgrunert(a)hotmail.de QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:22.0) Gecko/20100101 Firefox/22.0 System: openSUSE 12.3 Libreoffice 4.0.4 from the repository http://download.opensuse.org/repositories/LibreOffice:/Stable/openSUSE_12.3/ After switching all Libreoffice packages from 3.6 of the standard openSUSE 12.3 repo to the above mentioned Libreoffice:Stable repo, I got the following reproducible crash: Reproducible: Always Steps to Reproduce: 1. Update all Libreoffice packages to 4.0 from http://download.opensuse.org/repositories/LibreOffice:/Stable/openSUSE_12.3/ 2. Also install the libreoffice-base-drivers-mysql package 3. Open any base file with native mysql support (provided by the plugin above). 4. Enter a username and password. Actual Results: Libreoffice crashes with the error terminate called after throwing an instance of 'sql::InvalidArgumentException' what(): Couldn't load library libmysqlclient_r.so: libmysqlclient_r.so: Kann die Shared-Object-Datei nicht öffnen: Datei oder Verzeichnis nicht gefunden on the console. [translation of the last sentence: "Couldn't open the shared object file: file or directory not found"] Expected Results: Should not crash as it was before with Libreoffice 3.6 from http://download.opensuse.org/distribution/12.3/repo/oss/. Installing the packages libmysql55client_r18 and libmyclient_r18 didn't help. Traceback will be provided if it should be necessary and not a simple dependency issue. Thanks in advance for looking into this bug. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 37

[Bug 806250] New: hunspell spitting errors on each startup
by bugzilla_noreply＠novell.com 01 Jul '16

01 Jul '16

https://bugzilla.novell.com/show_bug.cgi?id=806250 https://bugzilla.novell.com/show_bug.cgi?id=806250#c0 Summary: hunspell spitting errors on each startup Classification: openSUSE Product: openSUSE 12.2 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: LibreOffice AssignedTo: pgajdos(a)suse.com ReportedBy: msvec(a)suse.com QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- bash$ hunspell -d cs_CZ /etc/passwd warning: line 274: incompatible stripping characters and condition warning: line 275: incompatible stripping characters and condition warning: line 599: incompatible stripping characters and condition warning: line 901: incompatible stripping characters and condition warning: line 1309: incompatible stripping characters and condition warning: line 1310: incompatible stripping characters and condition warning: line 1311: incompatible stripping characters and condition warning: line 1759: incompatible stripping characters and condition warning: line 1760: incompatible stripping characters and condition warning: line 1761: incompatible stripping characters and condition warning: line 2119: incompatible stripping characters and condition For context see https://bugs.freedesktop.org/show_bug.cgi?id=61501 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 42

[Bug 853944] New: spurious (?) "Started Activate md array even though degraded" msg on boot; checked arrays are not degraded
by bugzilla_noreply＠novell.com 30 Jun '16

30 Jun '16

https://bugzilla.novell.com/show_bug.cgi?id=853944 https://bugzilla.novell.com/show_bug.cgi?id=853944#c0 Summary: spurious (?) "Started Activate md array even though degraded" msg on boot; checked arrays are not degraded Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: x86-64 OS/Version: openSUSE 13.1 Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: ar16(a)imapmail.org QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:25.0) Gecko/20100101 Firefox/25.0 i've a 13.1 server. /boot & / are on RAID. specifically /boot <-- RAID-1 / <-- LVM on RAID-10 on system boot, i see in serial console output ... [ OK ] Started Activate md array even though degraded. Starting Activate md array even though degraded... [ OK ] Started Activate md array even though degraded. ... the boot continue & completes. checking, there's no trace of the 'degraded' array dmesg | egrep -i "degraded|md.:|activate|array" [ 28.199267] md/raid10:md2: active with 4 out of 4 devices [ 28.268913] md2: bitmap initialized from disk: read 30 pages, set 0 of 953867 bits [ 28.324245] md2: detected capacity change from 0 to 2000404086784 [ 28.358596] md2: unknown partition table [ 28.860292] md/raid1:md0: active with 2 out of 2 mirrors [ 29.071396] md0: bitmap initialized from disk: read 2 pages, set 0 of 50176 bits [ 29.126892] md0: detected capacity change from 0 to 205520896 [ 29.185709] md0: unknown partition table journalctl -xb | egrep -i "degraded|md.:|activate|array|raid" (empty) cat /proc/mdstat Personalities : [raid0] [raid1] [raid10] [raid6] [raid5] [raid4] [linear] md0 : active raid1 sda1[0] sdb1[1] 200704 blocks [2/2] [UU] bitmap: 0/25 pages [0KB], 4KB chunk md2 : active raid10 sdc1[0] sde1[4] sdd1[1] sdf1[3] 1953519616 blocks super 1.2 512K chunks 2 far-copies [4/4] [UUUU] bitmap: 0/466 pages [0KB], 2048KB chunk md125 : active raid1 sdb2[2] sda2[0] 243987048 blocks super 1.0 [2/2] [UU] unused devices: <none> mdadm --detail /dev/md0 /dev/md2 /dev/md125 | grep "State :" State : active State : active State : clean Reproducible: Always Steps to Reproduce: 1. 2. 3. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 16

[Bug 839170] New: reboot cannot reboot (failed to talk to init daemon) after update to Factory
by bugzilla_noreply＠novell.com 30 Jun '16

30 Jun '16

https://bugzilla.novell.com/show_bug.cgi?id=839170 https://bugzilla.novell.com/show_bug.cgi?id=839170#c0 Summary: reboot cannot reboot (failed to talk to init daemon) after update to Factory Classification: openSUSE Product: openSUSE Factory Version: 13.1 Milestone 4 Platform: x86-64 OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: dmuhamedagic(a)suse.com QAContact: qa-bugs(a)suse.de Found By: Development Blocker: --- Updated a Xen VM to factory from 12.3. reboot says: yoyo-b:~ # reboot Failed to open /dev/initctl: No such device or address Failed to talk to init daemon. systemd seems to be running. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 14

[Bug 711489] New: Package 'libffi' has no Description: field
by bugzilla_noreply＠novell.com 30 Jun '16

30 Jun '16

https://bugzilla.novell.com/show_bug.cgi?id=711489 https://bugzilla.novell.com/show_bug.cgi?id=711489#c0 Summary: Package 'libffi' has no Description: field Classification: openSUSE Product: openSUSE 11.4 Version: Final Platform: x86-64 OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Development AssignedTo: pth(a)novell.com ReportedBy: koenig(a)linux.de QAContact: qa(a)suse.de Found By: --- Blocker: --- running "pkg-config --libs libffi" fails with error Package 'libffi' has no Description: field $ rpm -qf /usr/lib64/pkgconfig/libffi.pc libffi45-devel-4.5.1_20101208-9.1.x86_64 workaround for now: # echo Description: foo >> /usr/lib64/pkgconfig/libffi.pc -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 9

[Bug 845572] New: Haskell shared libraries wring metadata in rpms (wrong package group)
by bugzilla_noreply＠novell.com 30 Jun '16

30 Jun '16

https://bugzilla.novell.com/show_bug.cgi?id=845572 https://bugzilla.novell.com/show_bug.cgi?id=845572#c0 Summary: Haskell shared libraries wring metadata in rpms (wrong package group) Classification: openSUSE Product: openSUSE 13.1 Version: RC 1 Platform: All OS/Version: SUSE Other Status: NEW Severity: Normal Priority: P5 - None Component: Development AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: peter.trommler(a)ohm-hochschule.de QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 According to http://en.opensuse.org/openSUSE:Package_group_guidelines Haskell libraries needed by applications should be in group System/Libraries not Development/Languages/Other. Likewise devel packages for those Haskell libraries should be in Development/Libraries/Other. Reproducible: Always Steps to Reproduce: 1. read metadata for ghc-base and ghc-base-devel 2. 3. Actual Results: In both cases Group Development/Languages/Other Expected Results: System/Libraries for ghc-base Development/Libraries/Other Thanks to Scott Bahling for pointing this out and for sending a patch for ghc-rpm-macros. The issue currently applies only libraries that come with the Haskell compiler ghc. Scott's patch will also allow us to build Haskell packages on SLE again. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 12

[Bug 726744] New: ghc-libs fails to symlink libHSsyb and libHSold
by bugzilla_noreply＠novell.com 30 Jun '16

30 Jun '16

https://bugzilla.novell.com/show_bug.cgi?id=726744 https://bugzilla.novell.com/show_bug.cgi?id=726744#c0 Summary: ghc-libs fails to symlink libHSsyb and libHSold Classification: openSUSE Product: openSUSE 11.4 Version: Final Platform: x86-64 OS/Version: openSUSE 11.4 Status: NEW Severity: Normal Priority: P5 - None Component: Development AssignedTo: pth(a)suse.com ReportedBy: admin(a)damienradtke.org QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:7.0.1) Gecko/20100101 Firefox/7.0.1 After installing cabal-install (version 0.8.2) and ghc-libs (version 6.12.3) from the openSUSE 11.4 Haskell repo, trying to run cabal results in a missing library error. Two libraries need to be located before cabal works, through either symlinking or editing LD_LIBRARY_PATH. The quickfix is to run this command: $ export LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:/usr/lib64/ghc-6.12.3/syb-0.1.0.2/:/usr/lib64/ghc-6.12.3/old-locale-1.0.0.2/ After these paths are added to the path, cabal works fine. The more permanent fix would be to symlink them to /usr/lib64 in the package's spec file: $ cd /usr/lib64 $ sudo ln -s /usr/lib64/ghc-6.12.3/old-locale-1.0.0.2/libHSold-locale-1.0.0.2-ghc6.12.3.so libHSold.so $ sudo ln -s /usr/lib64/ghc-6.12.3/syb-0.1.0.2/libHSsyb-0.1.0.2-ghc6.12.3.so libHSsyb.so $ sudo /sbin/ldconfig /usr/lib64 After these libraries are symlinked, everything will work fine without having to update LD_LIBRARY_PATH. These are the only libraries required by cabal, but it wouldn't hurt to make sure every library provided by ghc-libs is symlinked properly. Reproducible: Always Steps to Reproduce: 1. Install cabal-install and ghc-libs and try to run cabal 2. 3. Actual Results: libHSold and libHSsyb cannot be found Expected Results: Cabal should run normally -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 11

[Bug 835815] New: Redis init script ignores bind address on stop
by bugzilla_noreply＠novell.com 28 Jun '16

28 Jun '16

https://bugzilla.novell.com/show_bug.cgi?id=835815 https://bugzilla.novell.com/show_bug.cgi?id=835815#c0 Summary: Redis init script ignores bind address on stop Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: x86-64 OS/Version: openSUSE 12.3 Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: thomas(a)cupracer.de QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/27.0.1453.110 Safari/537.36 Redis may be configured to not listen to all network interfaces, but to a single one, like: # If you want you can bind a single interface, if the bind option is not # specified all the interfaces will listen for incoming connections. # bind 10.0.1.107 The problem is that the corresponding init script tries to stop Redis by using "redis-cli" with $PASS and $PORT as parameters. The configured bind address is missing here, so it just tries 127.0.0.1 and fails to connect to Redis. The bind address has to be added here. Something like this has to be added in /etc/init.d/redis: stop() { .. BIND=`grep ^bind $CONFIG | awk '{print $2}'` [ -n "$BIND" ] && CLI="$CLI -h $BIND" .. } Reproducible: Always Steps to Reproduce: 1. Configure Redis as usual. 2. Add "bind <some-non-lo-ip>" to the config file. 3. Start Redis: /etc/init.d/redis start 4. Make sure that Redis is running. 5. Try to stop Redis: /etc/init.d/redis stop Actual Results: The init script fails to Stop Redis as it doesn't know the correct bind address. Expected Results: The init script should stop Redis by connecting to its bind address. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 11

[Bug 673937] New: apache2: provide rpm macros file for 3rd party modules
by bugzilla_noreply＠novell.com 28 Jun '16

28 Jun '16

https://bugzilla.novell.com/show_bug.cgi?id=673937 https://bugzilla.novell.com/show_bug.cgi?id=673937#c0 Summary: apache2: provide rpm macros file for 3rd party modules Classification: openSUSE Product: openSUSE 11.4 Version: Factory Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Apache AssignedTo: bnc-team-apache(a)forge.provo.novell.com ReportedBy: lnussel(a)novell.com QAContact: qa(a)suse.de Found By: --- Blocker: --- 3rd party modules currently have code like this in the .spec file: %define apxs /usr/sbin/apxs2 %define apache_libexecdir %(%{apxs} -q LIBEXECDIR) Stuff like that should be put into a macro file with pre-computed values. e.g. /etc/rpm/macros.apache2 that is provided by apache2-devel. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 4

[Bug 597744] New: alpine: Missing umlaut in date column: our_strftime does not always return utf8-encoded strings
by bugzilla_noreply＠novell.com 28 Jun '16

28 Jun '16

http://bugzilla.novell.com/show_bug.cgi?id=597744 http://bugzilla.novell.com/show_bug.cgi?id=597744#c0 Summary: alpine: Missing umlaut in date column: our_strftime does not always return utf8-encoded strings Classification: openSUSE Product: openSUSE 11.1 Version: Final Platform: x86-64 OS/Version: openSUSE 11.1 Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: kdevel(a)vogtner.de QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Alpine does not correctly encode non-utf-8-data from locale's time and date formatting. Reproducible: Always Steps to Reproduce: 1. open console/xterm with 8-Bit character encoding (i.e. ISO-8859-1) 2. start alpine with LANG=de_DE@euro 3. have an e-mail in your inbox with a date of March. Actual Results: The Date displayed is "M" Expected Results: "Mär" strftime may return non-utf8 data if operated in a non-utf8 environment. In The non-WINDOWS-case no change of encoding to utf8 is performed in our_strftime (pith/string.c) but utf8 is expected from functions calling our_strftime. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 14