January 2014 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 646093] New: Ghostscript 9.00 fails when building lilypond documentation
by bugzilla_noreply＠novell.com 16 Jan '14

16 Jan '14

https://bugzilla.novell.com/show_bug.cgi?id=646093 https://bugzilla.novell.com/show_bug.cgi?id=646093#c0 Summary: Ghostscript 9.00 fails when building lilypond documentation Classification: openSUSE Product: openSUSE 11.4 Version: Factory Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Printing AssignedTo: jsmeix(a)novell.com ReportedBy: davejplater(a)gmail.com QAContact: jsmeix(a)novell.com CC: werner(a)novell.com Found By: --- Blocker: --- Created an attachment (id=394667) --> (http://bugzilla.novell.com/attachment.cgi?id=394667) File to reproduce the bug gs fails when converting ps to pdf :- gs -dEPSCrop -dGraphicsAlphaBits=4 -dTextAlphaBits=4 -dNOPAUSE -sDEVICE=png16m -sOutputFile="./d6/lily-50e2bfee.png" -r202 "./d6/lily-50e2bfee.eps" -c quit GPL Ghostscript 9.00 (2010-09-14) Copyright (C) 2010 Artifex Software, Inc. All rights reserved. This software comes with NO WARRANTY: see the file COPYING for details. Can't handle format 12 Error: /typecheck in --@0x7f798cd8f830-- Operand stack: 1.951 0.0 0.0 uni306B 1.951 0.0 0.0 uni306F 1.951 0.0 0.0 uni308D 1.951 77.7211 -24.8756 --dict:15/17(ro)(L)-- uni3044 uni3044 --nostringval-- Execution stack: %interp_exit .runexec2 --nostringval-- --nostringval-- --nostringval-- 2 %stopped_push --nostringval-- --nostringval-- --nostringval-- false 1 %stopped_push 1910 1 3 %oparray_pop 1909 1 3 %oparray_pop --nostringval-- 1893 1 3 %oparray_pop 1787 1 3 %oparray_pop --nostringval-- %errorexec_pop .runexec2 --nostringval-- --nostringval-- --nostringval-- 2 %stopped_push --nostringval-- 3 --nostringval-- %repeat_continue --nostringval-- %finish_show --nostringval-- --nostringval-- 6 3 15 --nostringval-- (gs_show_enum) %op_show_continue Dictionary stack: --dict:1177/3371(ro)(G)-- --dict:0/20(G)-- --dict:121/200(L)-- Current allocation mode is local Last OS error: 2 Current file position is 18922 GPL Ghostscript 9.00: Unrecoverable error, exit code 1 For complete build logs with three "Can't handle format 12" failures only the last one faults :- https://build.opensuse.org/stage/package/show?package=lilypond&project=open… I'll attach the offending file to enable reproduction -- 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 17

[Bug 568280] New: ghostscript segfaults building lilypond-2.12.3
by bugzilla_noreply＠novell.com 16 Jan '14

16 Jan '14

http://bugzilla.novell.com/show_bug.cgi?id=568280 http://bugzilla.novell.com/show_bug.cgi?id=568280#c0 Summary: ghostscript segfaults building lilypond-2.12.3 Classification: openSUSE Product: openSUSE 11.3 Version: Factory Platform: x86-64 OS/Version: SuSE Other Status: NEW Severity: Normal Priority: P5 - None Component: Printing AssignedTo: jsmeix(a)novell.com ReportedBy: janneke(a)gnu.org QAContact: jsmeix(a)novell.com Found By: --- Blocker: --- Created an attachment (id=334964) --> (http://bugzilla.novell.com/attachment.cgi?id=334964) lily-65a7b1b1-1.eps modified to read emmentaler-20.otf from cwd User-Agent: Mozilla/5.0 (X11; U; Linux i686; nl; rv:1.9.1.6) Gecko/20091215 Ubuntu/9.10 (karmic) Firefox/3.5.6 Trying to bump lilypond to 2.12.3, I find that the documentation does (still, see #502647) not build in current factory, due to ghostscript segfaulting. There's a new upstream release of ghostscript available: 8.70 that successfully builds the lilypond documentation, you may want to update. I'm attaching the input file: lily-65a7b1b1-1.eps Reproducible: Always Steps to Reproduce: This is the command that fails Run LANG= gs -dNOSAFER -dEPSCrop -dCompatibilityLevel=1.4 -dNOPAUSE -dBATCH -r1200 -sDEVICE=pdfwrite -sOutputFile="lily-65a7b1b1-1.pdf" -c .setpdfwrite -f "bug.eps" Actual Results: Segmentation fault Expected Results: Clean exit producing lily-65a7b1b1-1.pdf peder:/usr/src/packages/BUILD/lilypond-2.12.3> rpm -qi ghostscript-library Name : ghostscript-library Relocations: (not relocatable) Version : 8.64 Vendor: openSUSE Release : 9.3 Build Date: ma 04 jan 2010 05:06:04 UTC Install Date: ma 04 jan 2010 19:58:14 UTC Build Host: build35 Group : System/Libraries Source RPM: ghostscript-library-8.64-9.3.src.rpm -- 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 30

[Bug 466437] lilypond: new upstream release: 2.12 with spec fixes for documentation
by bugzilla_noreply＠novell.com 16 Jan '14

16 Jan '14

https://bugzilla.novell.com/show_bug.cgi?id=466437 https://bugzilla.novell.com/show_bug.cgi?id=466437#c4 --- Comment #4 from Swamp Workflow Management <swamp(a)suse.de> 2014-01-16 10:04:45 UTC --- openSUSE-RU-2014:0079-1: An update that has 5 recommended fixes can now be installed. Category: recommended (moderate) Bug References: 466437,568280,646093,733730,851999 CVE References: Sources used: openSUSE 13.1 (src): lilypond-2.18.0-2.4.1, lilypond-doc-2.18.0-2.4.1 -- 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 0

[Bug 857708] New: Calibre in openSUSE 13.1 refuses to use Kobo with latest fimware version
by bugzilla_noreply＠novell.com 16 Jan '14

16 Jan '14

https://bugzilla.novell.com/show_bug.cgi?id=857708 https://bugzilla.novell.com/show_bug.cgi?id=857708#c0 Summary: Calibre in openSUSE 13.1 refuses to use Kobo with latest fimware version Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: x86-64 OS/Version: openSUSE 13.1 Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: iacobcatalin(a)gmail.com QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:26.0) Gecko/20100101 Firefox/26.0 When using a Kobo that has been updated to the latest firmware version, Calibre complains with: Your Kobo is running an updated firmware/database version. As calibre does not know about this updated firmware, database editing is disabled, to prevent corruption. You can still send books to your Kobo with calibre, but deleting books and managing collections is disabled. If you are willing to experiment and know how to reset your Kobo to Factory defaults, you can override this check by right clicking the device icon in calibre and selecting "Configure this device" and then the "Attempt to support newer firmware" option. Doing so may require you to perform a factory reset of' your Kobo. Upstream commits show that no code changes are needed to support the newer versions besides version bumps: https://github.com/kovidgoyal/calibre/commit/a4c35af27d7d6a8b7d11c596133809… https://github.com/kovidgoyal/calibre/commit/c6fda62cc774e2148d1669a69af931… https://github.com/kovidgoyal/calibre/commit/7f4cce12f4f5547765ae12ecbf4cc4… https://github.com/kovidgoyal/calibre/commit/eabb3078e83957c845f07c35611cfc… Factory isn't affected since it has the upstream commits to bump the version. Reproducible: Always -- 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 858827] New: X.Org X Server 1.15.0 does not work with latest nvidia proprietary driver 331.38
by bugzilla_noreply＠novell.com 16 Jan '14

16 Jan '14

https://bugzilla.novell.com/show_bug.cgi?id=858827 https://bugzilla.novell.com/show_bug.cgi?id=858827#c0 Summary: X.Org X Server 1.15.0 does not work with latest nvidia proprietary driver 331.38 Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: x86-64 OS/Version: openSUSE 13.1 Status: NEW Severity: Normal Priority: P5 - None Component: X.Org AssignedTo: bnc-team-xorg-bugs(a)forge.provo.novell.com ReportedBy: rainer.klier(a)gmx.at QAContact: xorg-maintainer-bugs(a)forge.provo.novell.com Found By: --- Blocker: --- Created an attachment (id=574428) --> (http://bugzilla.novell.com/attachment.cgi?id=574428) log file of X start User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:26.0) Gecko/20100101 Firefox/26.0 X crashes with a segfault when starting. Reproducible: Always Steps to Reproduce: 1. install latest X.Org X Server 1.15.0 from the Xorg repo for openSUSE 13.1 2. install latest nvidia proprietary driver 331.38 from http://www.nvidia.com/Download/driverResults.aspx/72250/en-us 3. start x after installing the driver Actual Results: Xorg crashes with a Segmentation fault Expected Results: X should start, as it did with last X.Org X Server 1.14 although on page https://devtalk.nvidia.com/default/topic/672875/unix-graphics-announcements… is stated at the last in the feature list "Added support for X.org xserver ABI 15 (xorg-server 1.15)" IT IS NOT WORKING! at least not under openSUSE 13.1 x86_64 with latest Xorg server 1.15.0. although the new driver compiles without any problems, it crashes when starting X with a Segmentation fault. as you can see in the devtalk-forum-thread, in the meantime other users with other linux distros report, that it is working on their machines. therefor i think, it has to do something with the xorg 1.15 packages from opensuse, because xorg 1.14 does work. -- 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 8

[Bug 856905] New: package xorg-x11-server does not provide COPYING
by bugzilla_noreply＠novell.com 16 Jan '14

16 Jan '14

https://bugzilla.novell.com/show_bug.cgi?id=856905 https://bugzilla.novell.com/show_bug.cgi?id=856905#c0 Summary: package xorg-x11-server does not provide COPYING Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: i686 OS/Version: openSUSE 13.1 Status: NEW Severity: Major Priority: P5 - None Component: Documentation AssignedTo: ke(a)suse.com ReportedBy: giecrilj(a)stegny.2a.pl QAContact: ke(a)suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux i686; rv:26.0) Gecko/20100101 Firefox/26.0 SeaMonkey/2.23 The package xorg-x11-server is licensed under the terms of GNU Public License. The license requires that the text of the license should be bundled with binary packages. Currently the package violates this requirement, thereby invalidating the license, and therefore exposes the customers to legal risk. Reproducible: Always Steps to Reproduce: 1. { rpm -qi xorg-x11-server; } 2. { rpm -qd xorg-x11-server | grep -F COPYING; } 3. Actual Results: 1. License : GPL-2.0+ and MIT Expected Results: 2. /usr/share/doc/packages/xorg-x11-server/COPYING -- 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 5

[Bug 858948] New: cannot disable systemd debugging without "quiet" option
by bugzilla_noreply＠novell.com 16 Jan '14

16 Jan '14

https://bugzilla.novell.com/show_bug.cgi?id=858948 https://bugzilla.novell.com/show_bug.cgi?id=858948#c0 Summary: cannot disable systemd debugging without "quiet" option Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: andi-nbz(a)firstfloor.org QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux i686 on x86_64; rv:26.0) Gecko/20100101 Firefox/26.0 I need to disable the "quiet" kernel option for kernel debugging purposes. This enables systemd debugging messages in the log which spam my log and I don't need them. I changed /etc/systemd/system.conf to [Manager] LogLevel=info But the messages still appear. So it appears the quiet check overrides the set log level, which seems like a bug. This is a regression against older SuSE releases, where this worked (or rather quiet didn't imply systemd debugging) 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 2

[Bug 786109] New: undefined symbol: _XGetRequest - symbol lookup error: /usr/lib/libXcomposite in /usr/lib/NX/nxagent
by bugzilla_noreply＠novell.com 16 Jan '14

16 Jan '14

https://bugzilla.novell.com/show_bug.cgi?id=786109 https://bugzilla.novell.com/show_bug.cgi?id=786109#c0 Summary: undefined symbol: _XGetRequest - symbol lookup error: /usr/lib/libXcomposite in /usr/lib/NX/nxagent Classification: openSUSE Product: openSUSE 12.2 Version: Final Platform: i686 OS/Version: openSUSE 12.2 Status: NEW Severity: Normal Priority: P5 - None Component: X.Org AssignedTo: bnc-team-xorg-bugs(a)forge.provo.novell.com ReportedBy: ah(a)zunit.com QAContact: xorg-maintainer-bugs(a)forge.provo.novell.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:16.0) Gecko/20100101 Firefox/16.0 it seems that there may be build error similar to: http://forums.gentoo.org/viewtopic-t-929508-start-0.html and https://bugzilla.redhat.com/show_bug.cgi?id=782251 It happens both on 32bit and 64bit versions of opensuse 12.2 when trying to use freenx Is it worthwhile and safe enough to try to add experimental repository? http://download.opensuse.org/repositories/X11:/XOrg/openSUSE_12.2/ -------------- freenx startup error log: Session: Starting session at 'Sun Oct 21 23:34:50 2012'. Info: Proxy running in server mode with pid '18232'. Info: Waiting for connection from '127.0.0.1' on port '5000'. Info: Accepted connection from '127.0.0.1'. Warning: Connected to remote version 3.5.0 with local version 3.4.0. Warning: Consider checking NoMachine NX - Desktop Virtualization and Remote Access Management Software for updates. Info: Connection with remote proxy completed. Info: Using ADSL link parameters 512/24/1/0. Info: Using agent parameters 5000/10/50/0/0. Info: Using cache parameters 4/4096KB/131072KB/131072KB. Info: Using pack method 'adaptive-7' with session 'unix-kde'. Info: Using ZLIB data compression 1/1/32. Info: Using ZLIB stream compression 4/4. Info: No suitable cache file found. Info: Listening to X11 connections on display ':1000'. Info: Established X client connection. Info: Using shared memory parameters 1/1/1/4096K. Info: Using alpha channel in render extension. Info: Not using local device configuration changes. /usr/lib/NX/nxagent: symbol lookup error: /usr/lib/libXcomposite.so.1: undefined symbol: _XGetRequest NX> 1006 Session status: closed Reproducible: Always Steps to Reproduce: 1. install freenx 2. trying to connect via nxclient 3. check startup logs Actual Results: remote session fails to start Expected Results: graphical remote access to our server -- 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 15

[Bug 851020] New: autofs(nfs) and wifi(NM) are brought down/up in the wrong order for suspend/hibernate
by bugzilla_noreply＠novell.com 15 Jan '14

15 Jan '14

https://bugzilla.novell.com/show_bug.cgi?id=851020 https://bugzilla.novell.com/show_bug.cgi?id=851020#c0 Summary: autofs(nfs) and wifi(NM) are brought down/up in the wrong order for suspend/hibernate 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: hp(a)lisa-gmbh.de 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 Hi, when suspending/hibernating my wife's notebook with 13.1 GM, autofs is shut down after wifi, which is a pitty, since she has some autofs mounts running. Net result: it takes several minutes to suspend, as it will wait for nfs timeouts. Consequently on resume, autofs cannot start correctly, since wifi is missing. Some progress is noticable in this area, since older releases failed to start autofs at all. Wifi device is configured in NetworkManager as system connection and starting at boot. Reproducible: Always Steps to Reproduce: 1. Enable /net in /etc/auto.master 2. Create a system NM wifi connection, started on boot 3. suspend Actual Results: Long delay, before it finally suspends correctly. Expected Results: Immediate suspend (well, after autofs unmount at least) -- 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 3

[Bug 803653] New: hostnamed/hostnamectl is just broken
by bugzilla_noreply＠novell.com 15 Jan '14

15 Jan '14

https://bugzilla.novell.com/show_bug.cgi?id=803653 https://bugzilla.novell.com/show_bug.cgi?id=803653#c0 Summary: hostnamed/hostnamectl is just broken Classification: openSUSE Product: openSUSE 12.3 Version: RC 1 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: mike.catanzaro(a)gmail.com QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:18.0) Gecko/20100101 Firefox/18.0 hostnamed/hostnamectl is just broken. By default... michael@linux-h2qj:~> hostnamectl Static hostname: n/a Transient hostname: linux-h2qj.site Pretty hostname: n/a <snip> That's not my transient hostname, which is completely different. That's my static hostname. It's supposed to be stored in /etc/hostname according to the manpage and upstream, but it's actually in /etc/HOSTNAME as that's where it's always been for openSUSE. michael@linux-h2qj:~> hostnamectl set-hostname 'Victory Road' michael@linux-h2qj:~> hostnamectl Static hostname: victory-road Pretty hostname: Victory Road <snip> Now that made /etc/hostname: michael@linux-h2qj:~> cat /etc/hostname victory-road michael@linux-h2qj:~> cat /etc/machine-info PRETTY_HOSTNAME=Victory Road michael@linux-h2qj:~> cat /etc/HOSTNAME linux-h2qj.site YaST of course only knows about /etc/HOSTNAME. So I think hostnamed is not really accomplishing anything? Maybe it should be patched to use /etc/HOSTNAME instead for now? And something is really odd about the transient hostname. I'm not sure what it's doing there, but mine is absolutely completely different from what is displayed.... (Maybe we don't need to build hostnamed/hostnamectl at all for 12.3 -- does anything hard depend on them?) Reproducible: Always Also we're missing a soft dependency on nss-myhostname, so if hostnamed DID work it would make the new hostname unresolvable. That's merged into systemd 197 upstream, but since we're on systemd 195 we just get a little complaint in the journal that we're doing it wrong: Warning: nss-myhostname is not installed. Changing the local hostname might make it unresolvable. Please install nss-myhostname! -- 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 8