May 2014 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 869224] New: yast lan field for network interface name too short
by bugzilla_noreply＠novell.com 05 May '14

05 May '14

https://bugzilla.novell.com/show_bug.cgi?id=869224 https://bugzilla.novell.com/show_bug.cgi?id=869224#c0 Summary: yast lan field for network interface name too short Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: All OS/Version: openSUSE 13.1 Status: NEW Severity: Minor Priority: P5 - None Component: YaST2 AssignedTo: yast2-maintainers(a)suse.de ReportedBy: Ralf.Friedl(a)online.de QAContact: jsrain(a)suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:27.0) Gecko/20100101 Firefox/27.0 systemd changes the standard interface name name from eth0 to something like ens3p0. This in itself is a bad idea, see also #849749. Anyway, it is possible to use "yast lan"->overview->edit->hardware->change to assign a normal interface name. Unfortunately the input field in the text version of yast is only 5 characters long, with the last free for the cursor. So this ens3p0 is displayed as "←3p0▒". Reproducible: Always Steps to Reproduce: 1."yast lan"->overview->edit->hardware->change Actual Results: Interface name not fully visible. Expected Results: Interface name is fully visible. -- 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

[Bug 865207] New: openSUSE-2014-149 - no patch summary/description
by bugzilla_noreply＠novell.com 05 May '14

05 May '14

https://bugzilla.novell.com/show_bug.cgi?id=865207 https://bugzilla.novell.com/show_bug.cgi?id=865207#c0 Summary: openSUSE-2014-149 - no patch summary/description Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: Other OS/Version: openSUSE 13.1 Status: NEW Severity: Major Priority: P5 - None Component: Maintenance AssignedTo: maintenance(a)opensuse.org ReportedBy: suse-beta(a)cboltz.de QAContact: qa-bugs(a)suse.de Found By: Beta-Customer Blocker: --- zypper lp Loading repository data... Reading installed packages... Repository | Name | Version | Category | Status | Summary ---------------------+-------------------+---------+----------+--------+-------- openSUSE-13.1-Update | openSUSE-2014-149 | 1 | security | needed | That's not very helpful :-( (notice the missing summary and description) and reminds me to bug 862080 Maybe it's a good idea to also ask someone from the OBS team how this happened - I'd like to avoid that I have another similar bug next week ;-) -- 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 876245] New: Online Update Configuration fails
by bugzilla_noreply＠novell.com 05 May '14

05 May '14

https://bugzilla.novell.com/show_bug.cgi?id=876245 https://bugzilla.novell.com/show_bug.cgi?id=876245#c0 Summary: Online Update Configuration fails Classification: openSUSE Product: openSUSE Factory Version: 13.2 Milestone 0 Platform: x86-64 OS/Version: openSUSE 13.2 Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: yast2-maintainers(a)suse.de ReportedBy: ingesvensson(a)bredband.net QAContact: jsrain(a)suse.com Found By: --- Blocker: --- Created an attachment (id=588591) --> (http://bugzilla.novell.com/attachment.cgi?id=588591) outcome of y2log User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:27.0) Gecko/20100101 Firefox/27.0 The module closes without doing what it should Reproducible: Always Steps to Reproduce: 1.as su zypper in yast2-online-update-configuration 2.open YaST2 3.Software 4.Online Update Configuration Actual Results: module closes without doing what it should Expected Results: The Online Update Configuration Toll should have shown. -- 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 742774] systemd-cryptsetup ignores option 'noauto' in /etc/crypttab
by bugzilla_noreply＠novell.com 05 May '14

05 May '14

https://bugzilla.novell.com/show_bug.cgi?id=742774 https://bugzilla.novell.com/show_bug.cgi?id=742774#c14 Christian Boltz <suse-beta(a)cboltz.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Component|Basesystem |Basesystem Version|Final |13.2 Milestone 0 InfoProvider|suse-beta(a)cboltz.de | Product|openSUSE 12.2 |openSUSE Factory Target Milestone|Final |--- --- Comment #14 from Christian Boltz <suse-beta(a)cboltz.de> 2014-05-05 13:25:12 CEST --- (In reply to comment #13) > Is this bug still valid for openSUSE versions *after* 12.2 man crypttab in current factory still needs to be fixed/updated (see comment #12) [Product updated from 12.2 to Factory to make this clear] -- 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 860766] New: openSUSE Factory KDE Live x86_64 image unusable
by bugzilla_noreply＠novell.com 05 May '14

05 May '14

https://bugzilla.novell.com/show_bug.cgi?id=860766 https://bugzilla.novell.com/show_bug.cgi?id=860766#c0 Summary: openSUSE Factory KDE Live x86_64 image unusable Classification: openSUSE Product: openSUSE Factory Version: 13.2 Milestone 0 Platform: x86-64 OS/Version: openSUSE 13.2 Status: NEW Severity: Critical Priority: P5 - None Component: Installation AssignedTo: yast2-maintainers(a)suse.de ReportedBy: fbernasek(a)netscape.net QAContact: jsrain(a)suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:26.0) Gecko/20100101 Firefox/26.0 Hi, i have download the openSUSE Factory (13.2) KDE Live x86_64 iso's 801, 802 and 803 than burn or write on CD, DVD and USB stick, no troubles after reboot with this images all have the same problem when i like to test live or like to install he cancels the process with the message can't find run_init or the 803 image with the same message when boot from usb and the message can't mount root file system when boot from CD or DVD for use as live cd or like to install Reproducible: Always Steps to Reproduce: 1. download image (801, 802, 803) 2. write to dvd, cd or usb 3. boot, and can't continue " can't find run_init or can't mount root file system Actual Results: not usable the images Expected Results: normal work with the openSUSE Factory (13.2) KDE Live x86_64 iso -- 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 876243] New: Add sax3 to YaST
by bugzilla_noreply＠novell.com 05 May '14

05 May '14

https://bugzilla.novell.com/show_bug.cgi?id=876243 https://bugzilla.novell.com/show_bug.cgi?id=876243#c0 Summary: Add sax3 to YaST Classification: openSUSE Product: openSUSE Factory Version: 13.2 Milestone 0 Platform: All OS/Version: openSUSE 13.2 Status: NEW Severity: Enhancement Priority: P5 - None Component: YaST2 AssignedTo: yast2-maintainers(a)suse.de ReportedBy: embar(a)super.lt QAContact: jsrain(a)suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:28.0) Gecko/20100101 Firefox/28.0 Why not to add SAX3 utility for X conguration in YaST? 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 1

[Bug 344403] Build Service Emulators Repo - Mupen64 is fork version -Should be different name than official one in home:/wberrier
by bugzilla_noreply＠novell.com 05 May '14

05 May '14

https://bugzilla.novell.com/show_bug.cgi?id=344403 https://bugzilla.novell.com/show_bug.cgi?id=344403#c5 Aeneas Jaißle <aj(a)ajaissle.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED CC| |aj(a)ajaissle.de Resolution| |FIXED --- Comment #5 from Aeneas Jaißle <aj(a)ajaissle.de> 2014-05-05 12:07:23 CEST --- There are neither Mupen64 nor Mupen64-amd64, we have Mupen64Plus for some time now. Marking this as 'Resolved Fixed', as the packages are also called 'mupen64plus' instead of 'mupen64'. -- 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 737553] New: rpc.idmapd not started automatically
by bugzilla_noreply＠novell.com 05 May '14

05 May '14

https://bugzilla.novell.com/show_bug.cgi?id=737553 https://bugzilla.novell.com/show_bug.cgi?id=737553#c0 Summary: rpc.idmapd not started automatically Classification: openSUSE Product: openSUSE 12.1 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: devel(a)fresse.org QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:11.0a1) Gecko/20111118 Firefox/11.0a1 When mounting nfs4 shares the user mapping is supposed to happen through rpc.idmapd. However this service isn't started even though rpc_pipefs has been force-mounted during the boot. Reproducible: Always Steps to Reproduce: 1. Mount rpc_pipefs through an fstab entry rpc_pipefs /var/lib/nfs/rpc_pipefs rpc_pipefs defaults 0 0 2. Put NFS_START_SERVICES="yes" in /etc/sysconfig/nfs Actual Results: rpc.idmapd is not started automatically. Expected Results: rpc.idmapd should have been started according to the documentation in /etc/sysconfig/nfs. Manually starting rpc.idmapd works so it's just systemd failing to start the service. Exactly the same settings worked in opensuse 11.3 and opensuse 11.4. -- 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 778430] New: Merge OBS project science:vlinux with science
by bugzilla_noreply＠novell.com 05 May '14

05 May '14

https://bugzilla.novell.com/show_bug.cgi?id=778430 https://bugzilla.novell.com/show_bug.cgi?id=778430#c0 Summary: Merge OBS project science:vlinux with science Classification: Internal Novell Products Product: openSUSE Build Service Version: 2.0 Platform: Other OS/Version: Other Status: NEW Severity: Enhancement Priority: P5 - None Component: General AssignedTo: adrian(a)suse.com ReportedBy: vimalkumar_v(a)bioinformatics.org QAContact: adrian(a)suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.1 (KHTML, like Gecko) Chrome/21.0.1180.89 Safari/537.1 I maintain packages in the science:vlinux OBS repository. There was a request from a member of the Science team to merge VLinux with the science repository [https://getsatisfaction.com/vlinux/topics/merge_with_opensuse_science] Development on VLinux has stopped due to lack of interest. Merging this repository with science would make additional packages available to general openSUSE users.I suggest this merge be done. 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 4

[Bug 817212] New: xsession-errors end up in /var/log/messages (journal or gdm?)
by bugzilla_noreply＠novell.com 05 May '14

05 May '14

https://bugzilla.novell.com/show_bug.cgi?id=817212 https://bugzilla.novell.com/show_bug.cgi?id=817212#c0 Summary: xsession-errors end up in /var/log/messages (journal or gdm?) Classification: openSUSE Product: openSUSE Factory Version: 13.1 Milestone 0 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: seife(a)novell.slipkontur.de QAContact: qa-bugs(a)suse.de CC: fcrozat(a)suse.com Found By: Third Party Developer/Partner Blocker: --- Since todays Factory update, which contained a systemd update, stuff that formerly went into ~/.xsession-errors (or the new location gdm chose per default) now ends up in a journal. This is not bad. What is bad is, that it ends not only in the user's journal but also in the system journal and thus in /var/log/messages (via forwarding to syslog-ng). I think this is a bit overkill :-) I am not sure where the problem is located: if it is in gdm or in systemd, so I chose "Base System" as category. If it is a gdm problem, feel free to reassing to category GNOME. -- 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