January 2014 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 815785] New: Magic Sysreq o / poweroff does not work (alt-sysrq-o)
by bugzilla_noreply＠novell.com 16 Jan '14

16 Jan '14

https://bugzilla.novell.com/show_bug.cgi?id=815785 https://bugzilla.novell.com/show_bug.cgi?id=815785#c0 Summary: Magic Sysreq o / poweroff does not work (alt-sysrq-o) Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: x86-64 OS/Version: openSUSE 12.3 Status: NEW Severity: Major Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: dirk(a)goe.net QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:20.0) Gecko/20100101 Firefox/20.0 When trying to simply power-off the machine using the magic sysreq combination (alt-sysrq-o) the machine hangs instead of powering off. For some odd reason the hdd activity led is on, getting off for short and then staying on. The machine does not power off, but hangs and requires to press the power button for a while to actually power off. This was usually working in earlier openSuSE versions ... Other combinations work properly and behave as expected. Reproducible: Always Steps to Reproduce: 1. Try the magic sysrq combination for power off 2. Machine hangs 3. Actual Results: The machine hangs completely, USB is shut down (LEDs on keyboard and in mouse off). Expected Results: The machine should power off immediately without any hassles. -- 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 856806] New: bind 9.4.x : /lib/YaST/SuSEconfig.functions not exist - patch attached
by bugzilla_noreply＠novell.com 16 Jan '14

16 Jan '14

https://bugzilla.novell.com/show_bug.cgi?id=856806 https://bugzilla.novell.com/show_bug.cgi?id=856806#c0 Summary: bind 9.4.x : /lib/YaST/SuSEconfig.functions not exist - patch attached Classification: openSUSE Product: openSUSE Factory Version: 13.2 Milestone 0 Platform: All OS/Version: openSUSE 13.1 Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: info(a)remsnet.de QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:26.0) Gecko/20100101 Firefox/26.0 syslog at my i386 as well on arm6( rasberry ): 2013-12-26T12:51:41.284140+00:00 ad1 named[2776]: + script=/usr/share/bind/createNamedConfInclude 2013-12-26T12:51:41.293620+00:00 ad1 named[2776]: + /usr/share/bind/createNamedConfInclude 2013-12-26T12:51:41.304312+00:00 ad1 named[2776]: tput: No value for $TERM and no -T specified 2013-12-26T12:51:41.314205+00:00 ad1 named[2776]: Error: tput: No value for $TERM and no -T specified 2013-12-26T12:51:41.333740+00:00 ad1 named[2776]: Can not find /lib/YaST/SuSEconfig.functions! 2013-12-26T12:51:41.339555+00:00 ad1 named[2776]: This should not happen. Exiting. # # check for named settings MAYBE .. more changes required that depend on yast ... Reproducible: Always Steps to Reproduce: 1. install bind9.3+ on OpenSUSE 12.3+ 2. rcnamwed start / restart 3. tail -f /var/log/syslog Actual Results: /usr/share/bind/createNamedConfInclude still try use SuSEconfig.functions Expected Results: NO old SuSEconfig.functions usage. Patch : ad1:/etc/init.d # diff -ur /usr/share/bind/createNamedConfInclude.orig /usr/share/bind/createNamedConfInclude --- /usr/share/bind/createNamedConfInclude.orig 2013-12-21 13:43:00.000000000 +0000 +++ /usr/share/bind/createNamedConfInclude 2013-12-26 13:10:07.939496779 +0000 @@ -36,14 +36,7 @@ } # -# load special SuSEconfig functions -# -if [ ! -f "/lib/YaST/SuSEconfig.functions" ]; then - errorMessage 'Can not find /lib/YaST/SuSEconfig.functions!\nThis should not happen. Exiting.' - exit 1 -fi MD5DIR="/var/adm/SuSEconfig/md5" -. /lib/YaST/SuSEconfig.functions -- 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 858082] New: Network(Manager) is not started by default
by bugzilla_noreply＠novell.com 16 Jan '14

16 Jan '14

https://bugzilla.novell.com/show_bug.cgi?id=858082 https://bugzilla.novell.com/show_bug.cgi?id=858082#c0 Summary: Network(Manager) is not started by default Classification: openSUSE Product: openSUSE Factory Version: 13.2 Milestone 0 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Installation AssignedTo: mfilka(a)suse.com ReportedBy: locilka(a)suse.com QAContact: jsrain(a)suse.com Found By: Development Blocker: --- Created an attachment (id=573850) --> (http://bugzilla.novell.com/attachment.cgi?id=573850) Yast logs I've installed new system from New Installer media, build 0015 and NetworkManager is installed but not started by default. In fact Network is not configured to use NM. -- 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 1

[Bug 859024] New: System.Web.Compilation.CompilationException in ASP.NET with CS1576
by bugzilla_noreply＠novell.com 16 Jan '14

16 Jan '14

https://bugzilla.novell.com/show_bug.cgi?id=859024 https://bugzilla.novell.com/show_bug.cgi?id=859024#c0 Summary: System.Web.Compilation.CompilationException in ASP.NET with CS1576 Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: x86-64 OS/Version: openSUSE 13.1 Status: NEW Severity: Major Priority: P5 - None Component: Mono AssignedTo: bnc-team-mono(a)forge.provo.novell.com ReportedBy: andre.raabe(a)gmail.com QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created an attachment (id=574652) --> (http://bugzilla.novell.com/attachment.cgi?id=574652) Screenshot with full exception User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:26.0) Gecko/20100101 Firefox/26.0 During the on-demand compilation of an ASP.NET site I get a System.Web.Compilation.CompilationException with "CS1576: The line number specified for #line directive is missing or invalid". mono --version Mono JIT compiler version 3.0.6 (tarball Sat Sep 28 04:42:52 UTC 2013) Copyright (C) 2002-2012 Novell, Inc, Xamarin Inc and Contributors. www.mono-project.com TLS: __thread SIGSEGV: altstack Notifications: epoll Architecture: amd64 Disabled: none Misc: softdebug LLVM: supported, not enabled. GC: Included Boehm (with typed GC and Parallel Mark) Reproducible: Always Steps to Reproduce: 1. Create empty directory e.g. /tmp/f1 2. Create trival site e.g. default.aspx: -------8<---[default.aspx]---- <html> <body> Hello </body> </html> ------->8---[default.aspx]---- 3. Create trival web.config -------8<---[web.config]---- <?xml version="1.0" encoding="utf-8"?> <configuration> <system.web> <compilation defaultLanguage="c#" debug="true"/> <customErrors mode="Off"/> </system.web> <system.webServer> <defaultDocument> <files> <clear/> <add value="Default.aspx"/> </files> </defaultDocument> </system.webServer> </configuration> ------->8---[web.config]---- 4. Start "xsp2" in directory and visit URL Actual Results: System.Web.Compilation.CompilationException with "CS1576: The line number specified for #line directive is missing or invalid". Find screenshot in attachments. Expected Results: Site says "Hello" Source code for the on-demand created class is available here: https://gist.github.com/anonymous/8453123 This Bug is already open for Mono directly: https://bugzilla.xamarin.com/show_bug.cgi?id=17269 -- 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 481906] createNamedConfInclude reports errors where there aren't any
by bugzilla_noreply＠novell.com 16 Jan '14

16 Jan '14

https://bugzilla.novell.com/show_bug.cgi?id=481906 https://bugzilla.novell.com/show_bug.cgi?id=481906#c4 Reinhard Max <max(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution| |FIXED --- Comment #4 from Reinhard Max <max(a)suse.com> 2014-01-16 13:59:38 CET --- I tried the example from comment 2 and did not get any warnings anymore. -- 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 851524] New: Wrong description for kdenetwork4-filesharing
by bugzilla_noreply＠novell.com 16 Jan '14

16 Jan '14

https://bugzilla.novell.com/show_bug.cgi?id=851524 https://bugzilla.novell.com/show_bug.cgi?id=851524#c0 Summary: Wrong description for kdenetwork4-filesharing Classification: openSUSE Product: openSUSE Factory Version: 13.2 Milestone 0 Platform: Other OS/Version: Other Status: NEW Severity: Minor Priority: P5 - None Component: KDE4 Workspace AssignedTo: kde-maintainers(a)suse.de ReportedBy: aj(a)suse.com QAContact: qa-bugs(a)suse.de Found By: Product Management Blocker: --- rpm -qi kdenetwork4-filesharing shows as description: kdenetwork3-chat kdenetwork3-dialup kdenetwork3-lan kdenetwork3-mail kdenetwork3-news kdenetwork3-query This looks wrong, especially the "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 1

[Bug 846193] New: install onto nfsroot, chown fails
by bugzilla_noreply＠novell.com 16 Jan '14

16 Jan '14

https://bugzilla.novell.com/show_bug.cgi?id=846193 https://bugzilla.novell.com/show_bug.cgi?id=846193#c0 Summary: install onto nfsroot, chown fails Classification: openSUSE Product: openSUSE 13.1 Version: RC 1 Platform: x86-64 OS/Version: Linux Status: NEW Severity: Major Priority: P5 - None Component: Network AssignedTo: nfbrown(a)suse.com ReportedBy: ohering(a)suse.com QAContact: qa-bugs(a)suse.de Found By: Outsourced Testing Blocker: --- while attempting to install 13.1rc1 onto an existing nfsshare (finding a case for bnc#820407), rpm fails to change ownership. host is bax.arch.suse.de, running sles11sp3: /olaf_xenimages *(rw,async,no_root_squash,no_subtree_check,insecure) guest is a hyperv VM with 13.1rc1 inst-sys: bax.arch.suse.de:/olaf_xenimages/nfsroot/hv /mnt nfs4 rw,noatime,vers=4.0,rsize=1048576,wsize=1048576,namlen=255,hard,proto=tcp,port=0,timeo=600,retrans=2,sec=sys,clientaddr=10.121.48.50,local_lock=none,addr=10.121.8.52 0 0 I did not actively select nfs4 in the yast dialog, perhaps thats the underlying issue? Maybe something defaults to nfs4 now. hammer50:~ # ls -la /mnt/ total 20 drwxr-xr-x 10 4294967294 4294967294 4096 Oct 16 11:25 . drwxr-xr-x 24 root root 840 Oct 16 11:19 .. drwxr-xr-x 4 root root 4096 Oct 16 11:23 boot drwxr-xr-x 11 root root 4640 Oct 16 11:23 dev drwxr-xr-x 3 4294967294 4294967294 4096 Oct 16 11:24 etc dr-xr-xr-x 228 root root 0 Oct 16 2013 proc drwxr-xr-x 7 root root 180 Oct 16 11:20 run dr-xr-xr-x 12 root root 0 Oct 16 2013 sys drwxr-xr-x 3 4294967294 4294967294 4096 Oct 16 11:23 usr drwxr-xr-x 6 4294967294 4294967294 4096 Oct 16 11:23 var -rw-r--r-- 1 4294967294 4294967294 0 Oct 16 11:25 xxx hammer50:~ # chown root /mnt/xxx chown: changing ownership of '/mnt/xxx': Invalid argument touch xxx resulted in the entry above. bax has: ==> /var/log/messages <== Oct 16 13:32:15 bax rpc.idmapd[4317]: nss_getpwnam: name '0' does not map into domain 'localdomain' Neil, I'm giving this to you. If yast, or other tools, should be smarter and not default to nfs4, pass it on. -- 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 858053] New: home:sebschub/osmgpsmap: Bug
by bugzilla_noreply＠novell.com 16 Jan '14

16 Jan '14

https://bugzilla.novell.com/show_bug.cgi?id=858053 https://bugzilla.novell.com/show_bug.cgi?id=858053#c0 Summary: home:sebschub/osmgpsmap: Bug Classification: openSUSE Product: openSUSE.org Version: unspecified Platform: x86-64 OS/Version: openSUSE 13.1 Status: NEW Severity: Minor Priority: P5 - None Component: 3rd party software AssignedTo: schubert.seb(a)gmail.com ReportedBy: GeoBaltz(a)gmail.com QAContact: opensuse-communityscreening(a)forge.provo.novell.com Found By: --- Blocker: --- Looking into installing osmgpsmap module (for gramps) but when I list the RPM there are no files except the docs in /usr/share. gwb@gidney:~/Downloads> rpm -qlp osmgpsmap-1.0.1-5.1.x86_64.rpm warning: osmgpsmap-1.0.1-5.1.x86_64.rpm: Header V3 RSA/SHA1 Signature, key ID 73d0372f: NOKEY /usr/share/doc/packages/osm-gps-map /usr/share/doc/packages/osm-gps-map/AUTHORS /usr/share/doc/packages/osm-gps-map/COPYING /usr/share/doc/packages/osm-gps-map/ChangeLog /usr/share/doc/packages/osm-gps-map/NEWS /usr/share/doc/packages/osm-gps-map/README Shouldn't there be more? -- 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 1

[Bug 853908] New: No network after a fresh OpenSuSE 13.1 install
by bugzilla_noreply＠novell.com 16 Jan '14

16 Jan '14

https://bugzilla.novell.com/show_bug.cgi?id=853908 https://bugzilla.novell.com/show_bug.cgi?id=853908#c0 Summary: No network after a fresh OpenSuSE 13.1 install Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: i586 OS/Version: openSUSE 13.1 Status: NEW Severity: Major Priority: P5 - None Component: Network AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: claudio.prono(a)atpss.net QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:6.0) Gecko/20100101 Firefox/6.0 After a problem with an upgrade test, i have decided to do a fresh test install of OpenSuSE 13.1 32bit. After configuring the network (via Yast), and doing a reboot, no network comes up at all (no ip address assigned on interface). (sorry, the date of the logs are wrong, but is only a test machine) My system is a proxmox VM guest, with this settings: linux-4tjt:~ # lspci -v | grep -i eth 00:12.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 20) cat /etc/sysconfig/network/ifcfg-ens18 BOOTPROTO='static' BROADCAST='' ETHTOOL_OPTIONS='' IPADDR='192.168.90.31/24' MTU='' NAME='RTL-8139/8139C/8139C+' NETMASK='' NETWORK='' REMOTE_IPADDR='' STARTMODE='auto' USERCONTROL='no' systemctl status network(a)ens18.service -l network(a)ens18.service - ifup managed network interface ens18 Loaded: loaded (/usr/lib/systemd/system/network@.service; static) Active: inactive (dead) Nov 09 14:37:46 linux-4tjt systemd[1]: Starting ifup managed network interface ens18... Nov 09 14:37:47 linux-4tjt ifup[784]: ens18 device: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 20) Nov 09 14:37:47 linux-4tjt ifup[829]: ens18 device: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 20) Nov 09 14:37:48 linux-4tjt SuSEfirewall2[953]: /run/SuSEfirewall2.booting exists which means system boot in progress, exit. Nov 09 14:37:49 linux-4tjt systemd[1]: Started ifup managed network interface ens18. Nov 09 14:37:53 linux-4tjt systemd[1]: Stopping ifup managed network interface ens18... Nov 09 14:37:53 linux-4tjt ifdown[1369]: ens18 device: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 20) Nov 09 14:37:53 linux-4tjt ifdown[1410]: ens18 device: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 20) Nov 09 14:37:54 linux-4tjt systemd[1]: Stopped ifup managed network interface ens18. journalctl -u network(a)ens18.service -- Logs begin at Sat 2013-11-09 14:37:38 CET, end at Sat 2013-11-09 14:39:11 CET. -- Nov 09 14:37:46 linux-4tjt systemd[1]: Starting ifup managed network interface ens18... Nov 09 14:37:47 linux-4tjt ifup[784]: ens18 device: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 20) Nov 09 14:37:47 linux-4tjt ifup[829]: ens18 device: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 20) Nov 09 14:37:48 linux-4tjt SuSEfirewall2[953]: /run/SuSEfirewall2.booting exists which means system boot in progress, exit. Nov 09 14:37:49 linux-4tjt systemd[1]: Started ifup managed network interface ens18. Nov 09 14:37:53 linux-4tjt systemd[1]: Stopping ifup managed network interface ens18... Nov 09 14:37:53 linux-4tjt ifdown[1369]: ens18 device: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 20) Nov 09 14:37:53 linux-4tjt ifdown[1410]: ens18 device: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 20) Nov 09 14:37:54 linux-4tjt systemd[1]: Stopped ifup managed network interface ens18. linux-4tjt:~ # dmesg | grep ens18 [ 6.564504] systemd-udevd[245]: renamed network interface eth0 to ens18 [ 13.846605] 8139cp 0000:00:12.0 ens18: link up, 100Mbps, full-duplex, lpa 0x05E1 The same configuration, with an OpenSuSE 13.1 64bit is perfectly working. On 32bit no way to make it work. Reproducible: Always Steps to Reproduce: 1.Fresh install of OpenSuSE 13.1 (only text, no windows manager needed) 2.Configuration of the network via Yast 3.reboot 4.after reboot, no network comes up. No errors from the log. Actual Results: No working network on opensuse 13.1 32bit Expected Results: Normal network coming up after configuration and reboot -- 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 20

[Bug 851999] New: LilyPond Is an Outdated Development Version
by bugzilla_noreply＠novell.com 16 Jan '14

16 Jan '14

https://bugzilla.novell.com/show_bug.cgi?id=851999 https://bugzilla.novell.com/show_bug.cgi?id=851999#c0 Summary: LilyPond Is an Outdated Development Version Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: All OS/Version: openSUSE 13.1 Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: crantila(a)fedoraproject.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 The LilyPond version shipping in openSUSE 13.1 is 2.17.26, part of the 2.17.x series of development releases. (As Linux used to do, odd-numbered major releases are for development of the next even-numbered stable release; thus 2.13.x, 2.15.x, 2.17.x, and so on are unstable). While it makes sense to be shipping the 2.17.x series in Factory, we should have been downgraded to 2.16.2---the most recent stable release---when 13.1 branched from Factory. As it is, the should-be-stable package shipped with 13.1 is not only a development version, but an early and out-of-date development version. Thus, I request a downgrade to LilyPond 2.16.2. If that's impractical, please start shipping updated development versions until the 2.18.x series is released, which should be soon (the current 2.17.95 is beta for 2.18.0). (As an aside, I note from bug 733730 and https://build.opensuse.org/package/users/openSUSE:13.1/lilypond that there may be no dedicated maintainer for the "lilypond" package. If that's the case, I may wish to join in). 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 10