October 2012 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 784286] New: [PATCH] Ignore stale exit events if they come in <1s after startup
by bugzilla_noreply＠novell.com 09 Oct '12

09 Oct '12

https://bugzilla.novell.com/show_bug.cgi?id=784286 https://bugzilla.novell.com/show_bug.cgi?id=784286#c0 Summary: [PATCH] Ignore stale exit events if they come in <1s after startup Classification: Internal Novell Products Product: openSUSE Build Service Version: 2.0 Platform: Other OS/Version: Other Status: NEW Severity: Minor Priority: P5 - None Component: backend AssignedTo: mls(a)suse.com ReportedBy: wm161(a)wm161.net QAContact: adrian(a)suse.com Found By: --- Blocker: --- Created an attachment (id=508780) --> (http://bugzilla.novell.com/attachment.cgi?id=508780) patch to bs_sched User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.1 (KHTML, like Gecko) Chrome/21.0.1180.89 Safari/537.1 Running this command: obs_admin --shutdown-scheduler i586 while the scheduler is not running will cause the scheduler to exit as soon as it starts up. The attached patch fixes this by ignoring any exit events that come in less than one second after startup. Reproducible: Always Steps to Reproduce: 1. Run obs_admin --shutdown-scheduler i586 to kill the i586 scheduler. 2. Run obs_admin --shutdown-scheduler i586 again after it has exited 3. Restart bs_sched Actual Results: bs_sched exits immediately after starting up Expected Results: bs_sched should ignore the stale event and continue starting up. -- 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 267903] KDM kcm module conflicts with /etc/sysconfig/displaymanager settings
by bugzilla_noreply＠novell.com 09 Oct '12

09 Oct '12

https://bugzilla.novell.com/show_bug.cgi?id=267903 https://bugzilla.novell.com/show_bug.cgi?id=267903#c52 --- Comment #52 from T. van Beelen <teuniz(a)gmail.com> 2012-10-09 18:03:08 UTC --- Out of curiosity, what is the reason that this bug hasn't been solved in five years? Not important enough? Lack of programmers? Gnome environment has priority? Because KDE isn't used in the enterprise edition? Other reasons? -- 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 267903] KDM kcm module conflicts with /etc/sysconfig/displaymanager settings
by bugzilla_noreply＠novell.com 09 Oct '12

09 Oct '12

https://bugzilla.novell.com/show_bug.cgi?id=267903 https://bugzilla.novell.com/show_bug.cgi?id=267903#c51 Christian Trippe <ctrippe(a)opensuse.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |Rudolf.Goeldner(a)email.de --- Comment #51 from Christian Trippe <ctrippe(a)opensuse.org> 2012-10-09 17:51:06 UTC --- *** Bug 784265 has been marked as a duplicate of this bug. *** http://bugzilla.novell.com/show_bug.cgi?id=784265 -- 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 784265] New: Login Screen cannot be changed by "Configure Desktorp"
by bugzilla_noreply＠novell.com 09 Oct '12

09 Oct '12

https://bugzilla.novell.com/show_bug.cgi?id=784265 https://bugzilla.novell.com/show_bug.cgi?id=784265#c0 Summary: Login Screen cannot be changed by "Configure Desktorp" Classification: openSUSE Product: openSUSE 12.2 Version: Final Platform: x86-64 OS/Version: openSUSE 12.2 Status: NEW Severity: Normal Priority: P5 - None Component: KDE4 Applications AssignedTo: kde-maintainers(a)suse.de ReportedBy: Rudolf.Goeldner(a)email.de QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:15.0) Gecko/20100101 Firefox/15.0.1 If you change the settings for the Login Screen by "configure Desktop" of KDE the changes are not proceeded. 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 1

[Bug 778926] New: Keyboard/mouse does not work if connected through USB hub/KVM switch
by bugzilla_noreply＠novell.com 09 Oct '12

09 Oct '12

https://bugzilla.novell.com/show_bug.cgi?id=778926 https://bugzilla.novell.com/show_bug.cgi?id=778926#c0 Summary: Keyboard/mouse does not work if connected through USB hub/KVM switch Classification: openSUSE Product: openSUSE 12.2 Version: Final Platform: x86-64 OS/Version: openSUSE 12.2 Status: NEW Severity: Normal Priority: P5 - None Component: GNOME AssignedTo: bnc-team-gnome(a)forge.provo.novell.com ReportedBy: rgoldwyn(a)suse.com QAContact: qa-bugs(a)suse.de Found By: L3 Blocker: --- I have a KVM switch connected to a laptop which doubles up as a USB hub to connect USB peripherals. Connecting an external keyboard and mouse to the KVM/hub does not work in GNOME (or X). If I use the the Virtual Terminal (Ctrl+Alt+F2) and use the external keyboard or mouse (gpm), it works fine. Also, I noticed that if I insert a USB drive in the hub, it asks for authentication to mount. However, if the drive is connected directly to the laptop or docking station, it does not ask for authentication. Let me know if you need any more information, such as X logs. This setup used to work with opensuse 12.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 6

[Bug 783585] New: systemd: Error messages not written to the journal.
by bugzilla_noreply＠novell.com 09 Oct '12

09 Oct '12

https://bugzilla.novell.com/show_bug.cgi?id=783585 https://bugzilla.novell.com/show_bug.cgi?id=783585#c0 Summary: systemd: Error messages not written to the journal. Classification: openSUSE Product: openSUSE 12.2 Version: Final Platform: x86-64 OS/Version: openSUSE 12.2 Status: NEW Severity: Major Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: erwinlam(a)dds.nl QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:15.0) Gecko/20100101 Firefox/15.0.1 When I shutdown my computer, occasionally, I see a message like "unable to handle kernel paging request ...." followed by a lot of register(?) information. The entire message passes by too quickly to capture manually. In those days, when I still used sysvinit, these messages were always written to the syslog so I could have a look at them later and report a bug. However, nowadays I am using systemd and these messages are not registered anywhere. It seems systemd does not capture them. Reproducible: Always Steps to Reproduce: Don't know. It occasionally happens. -- 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 776582] Confirm licensing of smolt
by bugzilla_noreply＠novell.com 09 Oct '12

09 Oct '12

https://bugzilla.novell.com/show_bug.cgi?id=776582 https://bugzilla.novell.com/show_bug.cgi?id=776582#c8 --- Comment #8 from Ciaran Farrell <cfarrell(a)suse.com> 2012-10-09 15:17:33 UTC --- (In reply to comment #7) > concerning specifically that bug I close it as WONTFIX > Ciaran, you could then send a sr delete for factory already so we already clean > up the situation for 12.3 sr#137625 -- 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 776582] Confirm licensing of smolt
by bugzilla_noreply＠novell.com 09 Oct '12

09 Oct '12

https://bugzilla.novell.com/show_bug.cgi?id=776582 https://bugzilla.novell.com/show_bug.cgi?id=776582#c7 --- Comment #7 from Bruno Friedmann <bruno(a)ioda-net.ch> 2012-10-09 15:11:11 UTC --- Thanks Andreas, I was already considering it like a dead horse once I've digging what commit come in. okay what's important for us 2012-10 - Implement eol/dummy server/redirects 2012-11-07 - Switch smolt server to placeholder/eol 2013-11-01 - take down dummy/eol server So then as what they said we should a) communicate about that retirement b) organize a way to deactivate the cron job by an update at least c) once that update is pushed outside, osc sr delete :-) Concerning census, it look like not a well performing project (last commit and initial one 6 months ago, by one person ) and I don't see a strong highlight on using python3 only ... :-) concerning specifically that bug I close it as WONTFIX Ciaran, you could then send a sr delete for factory already so we already clean up the situation for 12.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 0

[Bug 779087] New: after 12.1->12.2 upgrade, system with ROOT on LVM-on-RAID fails to boot; loops VG not found/partial mode
by bugzilla_noreply＠novell.com 09 Oct '12

09 Oct '12

https://bugzilla.novell.com/show_bug.cgi?id=779087 https://bugzilla.novell.com/show_bug.cgi?id=779087#c0 Summary: after 12.1->12.2 upgrade, system with ROOT on LVM-on-RAID fails to boot; loops VG not found/partial mode Classification: openSUSE Product: openSUSE 12.2 Version: Final Platform: All OS/Version: openSUSE 12.2 Status: NEW Severity: Critical 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:15.0) Gecko/20100101 Firefox/15.0 My a number opensuse 12.1 boxes that have: /boot on RAID-1 /root on LVM on RAID-10 They've been configured and running that way, without issue, for a long time. I'm working on 12.1->12.2 upgrades. The upgrades were performed by (1) adding the full isntall DVD as a priority 98 (1 above default 99) source (2) zypper dup (3) remove/disable the DVD source (4) zypper dup All boxes that have NO raid involvement have upgraded without incident; boot is fine. On all boxes that have a RAID array +LVMs, post 12.1->12.2 upgrade fail to find their respective VolumeGroups. They boot, 'thru' grub, but only get so far as the boot console endlessly looping the following message: "Volume Group "VG_XX" not found. Partial Mode. Incomplete logical volumes will not be processed" I've verified that it's not a problem with the array -- it assembles fine if I boot from a non-systemd-init rescue disk, e.g. SystemRescueCD. I've been asked (by AJaeger @ #opensuse-factory) to file this bug, and attache a photo of the boot screen and to "use the rescue system to show the setup". I've attached the photo here, but boot from the Opensuse 122 full-install diskis'sresuce system fails. It just hangs at the 'green screen + chameleon'. Attempting to booting from a sysvinit fallback init via the grub prompt to switch the init system , specifying "init=/sbin/init.sysv.fallback" on kernel grub line, unfortunately does NOT fix the problem; same error -- not finding the VG. Again, boot from 'systemrescueCD' does find the array. This is true on 3 different upgraded machines I've just checked. Chatting in #lvm, the following was offered: <kabi_> Aresby: I guess you will need to ask package maintainer for your distro for help [07:19] <Aresby> kabi_: So nothing @lvm that's fundamentally at-odds with systemd? [07:20] <kabi_> Aresby: since systemd is quite invasive in the system boot process and it's highly quite a bit distro specific [07:21] <kabi_> Aresby: Well there are some on going steps being made in Fedora Rawhide towards better intergration of systemd and lvm and in general Fedora should mostly always work [07:21] <kabi_> Aresby: but I've no idea how the Opensuse is resolving related problems (and there are some...) [07:22] <wN> Aresby: i was giogn to say that if it was a non-root volume you could try adding _netdev to the mount options to delay the startup [07:23] <Aresby> wN to grub kernel line? [07:23] <wN> to fstab [07:23] <Aresby> ah, hence the non-root reqt. [07:23] <wN> partially activation usually only happens when some PVs are missing, but others are not. [07:24] <wN> (in the vg) [07:24] <wN> it looks like you're already going into partial mode, which means that parts of the LV could be missing [07:25] <Aresby> wN Not clear how that might be the case. It's one PV & one VG across a 4-disk RAID-10 array. [07:25] <wN> that is odd. [07:25] <kabi_> do problem is that you need to ensure all volumes are ready and available [07:25] <wN> perhaps there is another scenario that invokes partial activation. [07:26] <kabi_> and in Fedora for a long time there was udevadm settle used for this [07:26] <Aresby> wN: & if it were 'missing' for some persistent/physical reason, I'd expect it to be also the case when booted from other media [07:26] <Aresby> kabi_: specifically for the systemd case? [07:27] <kabi_> Aresby: yes - which slows down to booting process - since udev cannot wait only for particalar discs [07:28] <kabi_> Aresby: now ongoing modificaition are trying to bring-in auto-activation in the right time - but that's still under developement and just somehow explored/tested in Rawhide 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 40

[Bug 784206] New: Memtest86+ is broken on all of the openSUSE 12.2 installation images
by bugzilla_noreply＠novell.com 09 Oct '12

09 Oct '12

https://bugzilla.novell.com/show_bug.cgi?id=784206 https://bugzilla.novell.com/show_bug.cgi?id=784206#c0 Summary: Memtest86+ is broken on all of the openSUSE 12.2 installation images Classification: openSUSE Product: openSUSE 12.2 Version: Final Platform: All OS/Version: openSUSE 12.2 Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: avallach2000(a)gmail.com QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created an attachment (id=508684) --> (http://bugzilla.novell.com/attachment.cgi?id=508684) Running test on Fujitsu D2831-S PC with DDR2 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:15.0) Gecko/20100101 Firefox/15.0.1 It seems that corrupted memtest86+ binary was used when creating the installation ISO images. Here's the comparison: Memtest86+ 4.20 from any of openSUSE 12.2 installation images (/boot/i386/loader/memtest) > size: 176760 > mtime: Aug 24 2012 00:00 > md5: 8b140fbf85f256973bdea1c5c5e620c5 Memtest86+ 4.20 (unpacked from http://www.memtest.org/download/4.20/memtest86+-4.20.bin.gz) > size: 164504 > mtime: Jan 25 2011 > md5: 72789a40fa4737d6c4b8f81e56bbb450 Memtest86+ 4.20 from Arch Linux 2011.08 net-install (/arch/boot/memtest) > size: 164504 > mtime: Aug 19 2011 > md5: 72789a40fa4737d6c4b8f81e56bbb450 Reproducible: Always Steps to Reproduce: 1. Select "Memory test" from openSUSE 12.2 installation image grub menu. 2. Wait until 40-50% of the pass will be completed. 3. Memtest86+ will give an error. -- 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