November 2011 - openSUSE Factory - openSUSE Mailing Lists

[opensuse-factory] Problem with md Raids in RC2
by Andreas Hoffmann 08 Nov '11

08 Nov '11

Hi All, since ive performed zypper dup to upgrade to rc2, ive larger problems with my md raids (level1). The system is not comming up after a clean or unclean system shutdown. It boots into maintenance mode and complains bad superblocks on device /dev/mdx and waits for the root password to login. If I wait for a while in this state and then press reset on the machine after the hdd leds stopped blinking he system resets and boots ok. Raids are in sync and clean and working after that. This happens with all boot options (failsafe and desktop). If I give rootpassword and login and try an fsck the md device it complains about the missing superblock. Pressing reset in this position also will result in a booting system afterwards. The system is then running fine and normal until the next shutdown. In the next reboot it goes to repairmode and asks for root password. Just wait about 5-6 seconds press reset after leds stopped flashing and it will boot again. This can be played over and over again, its always the same. Does anybody have experienced the same and maybe an idea what might be wrong? Greetings Andreas -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

2 2

[opensuse-factory] No splash screen for 1920x1200
by Ilya Chernykh 08 Nov '11

08 Nov '11

Hi! There is no splash screen with progress bar for 1920x1200 resolution which causes text-mode boot up when the framebuffer comsole resolution is set to 1920x1200. I wonder if it has been addressed in Factory. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

1 0

[opensuse-factory] Apparmor problems with kdm3
by Ilya Chernykh 08 Nov '11

08 Nov '11

Hi! After recent update to 11.4 kdm3 (KDE3's display manager) does not start with normal boot, leaving me with console screen. Only sequence of init 3 init 5 from root account helps. On the other hand, gdm works well. I also receive the following in dmesg when using kdm3: [ 53.186180] type=1400 audit(1320709759.623:2): apparmor="DENIED" operation="c hange_hat" info="unconfined" error=-1 pid=2875 comm="login" [ 53.186193] type=1400 audit(1320709759.623:3): apparmor="DENIED" operation="c hange_hat" info="unconfined" error=-1 pid=2875 comm="login" [ 76.645315] type=1400 audit(1320709783.082:4): apparmor="DENIED" operation="c hange_hat" info="unconfined" error=-1 pid=3050 comm="kdm" [ 76.645328] type=1400 audit(1320709783.082:5): apparmor="DENIED" operation="c hange_hat" info="unconfined" error=-1 pid=3050 comm="kdm" [ 165.897837] type=1400 audit(1320709872.333:6): apparmor="DENIED" operation="c hange_hat" info="unconfined" error=-1 pid=3962 comm="kdm" [ 165.897849] type=1400 audit(1320709872.333:7): apparmor="DENIED" operation="c hange_hat" info="unconfined" error=-1 pid=3962 comm="kdm" which is why I suspect apparmor even though it is switched off in Yast2 (switching it on does not help). -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

2 2

[opensuse-factory] 12.1 RC 2 will not install on Acer aspire 7720 (AMD)
by Giel Peters 08 Nov '11

08 Nov '11

Hi, Downloaded 64bit iso, checked it, burned it, checked it again and tried to install 12.1. Everything looks fine but after a few seconds intallation stops with a nice splashscreen. Trying alt-F2 for the console it shows "Starting udev..." and that's it. Tried it tree times, waited for 5 minutes if something happens and gave up... regards, Giel Peters -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

3 2

[opensuse-factory] gdm launch failure
by Dimstar / Dominique Leuenberger 08 Nov '11

08 Nov '11

Hi all, I just dup'ed my machine today as well and ran into an issue I believe a bunch of users ran into already. GDM fails to show the greeter with the all famous 'oh no! something has gone wrong' error message. I could track it down to /dev/nvidiactl: the gdm greeter seems not to have sufficient permissions to access this device, causing the error. /dev/nvidiactl is created as crw-rw---- root:video; which obviously is not matching the gdm user's permission. As a quick workaround I just added user 'gdm' to the group 'video', which helped over the problem, but I'm wondering why this would have started to happen now? Dominique PS: No, no bugreport created yet. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

10 16

[opensuse-factory] openSUSE-release Package on Factory still Has RC1
by Andi Sugandi 08 Nov '11

08 Nov '11

Hi, As on my $Subject, is it known issue? Does it mean I'm still using openSUSE 12.1 RC1 or it is only the packaging problem? $ cat /etc/SuSE-release openSUSE 12.1 RC 1 (x86_64) VERSION = 12.1 CODENAME = Asparagus $ rpm -qf /etc/SuSE-release openSUSE-release-12.1-1.29.x86_64 $ zypper info openSUSE-release Loading repository data... Reading installed packages... Information for package openSUSE-release: Repository: f-oss Name: openSUSE-release Version: 12.1-1.29 Arch: x86_64 Vendor: openSUSE Installed: Yes Status: up-to-date Installed Size: 140.0 KiB Summary: openSUSE 12.1 Description: openSUSE is a distribution by the openSUSE.org project. $ zypper lr f-oss Alias : f-oss Name : f-oss URI : http://download.opensuse.org/factory/repo/oss/ Enabled : Yes Priority : 99 Auto-refresh: On Keep Packages : On Type : yast2 GPG Check : On GPG Key URI : Path Prefix : / Parent Service: MD Cache Path : /var/cache/zypp/raw/f-oss Thanks in advance. Best regards, -- Andi Sugandi. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

5 7

[opensuse-factory] RC2 LiveCD KDE test complete: findings.
by Roger Luedecke 07 Nov '11

07 Nov '11

Progress bar missing on bootsplash. Kde desktop took very long time to show sound in tray and the clock was the wrong size for about two minutes. No startup sound. "System Policy prevents modification of personal network settings", but connects anyway. After Wi-Fi connected, desktop becomes unresponsive briefly. Firefox asks for user profile. Oxygen looks good on Firefox. No sound from Firefox, though sound works in Kaffeine and Amarok. Desktop Walnut, is unmovable (lag problem). Nepomuk not running error. Activity Manager icon looks out of place. Walnut corrected, problem due to slow initial desktop. Applications launch very slowly. New Oxygen skin and icons look very good. YaST assumes correct oxygen and colors. Software Management assumes different skin and green buttons. All YaST modules do this, though the control panel appears correctly. Recommend using that color scheme as default. Kmail imap performance seems good. Desktop slow in general... seems odd. Clementine missing. Apper runs. Was not able to check cd_emu due to desktop slowdown. I was taking notes as I went, so forgive the messiness. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

2 2

[opensuse-factory] RC1 -> RC2 failed because of systemd
by Greg Freemyer 07 Nov '11

07 Nov '11

All, Before we go Gold, can the zypper dup process be updated to warn users of the possibility of needing to add init=/sbin/sysvinit to menu.lst before allowing them to proceed? I'm just talking about a simple test message that pops up somehow. I know the zypper package itself is not the way to do this because users will still be running zypper from 11.4 most likely. Is their a text file, or license file trick we could play to force a warning to the user? If not, is there a way to rush out a 11.4 update to zypper that would have it check the update repo and if its 12.1, give a warning? == my story I have a desktop machine that I upgraded a week or two ago from Tumbleweed to RC1. That went reasonably smooth. I "think" I was running systemd after that upgrade. I did NOT have a init= statement in /boot/grub/menu.lst, and I think the RC1 default was systemd. I just upgraded to RC2 via zypper up. (Note the repo was already set and I had already re-enabled a number of devel repos, so I didn't feel the need to use zypper dup.) Anyway, after the upgrade I rebooted immediately and ended up in Emergency Mode. Fortunately I knew to add init=/sbin/sysvinit. I know that will be in the release notes, but that just doesn't seem like enough of a safeguard. I don't think many of the "zypper dup" upgraders will read the release notes. Greg -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

2 4

Re: [opensuse-factory] GMP build issue (make check) for armv7l
by Joop Boonen 07 Nov '11

07 Nov '11

On Sun, November 6, 2011 8:14 pm, Cristian RodrÃguez wrote: > On 06/11/11 06:11, Joop Boonen wrote: >> Hi All, >> >> I'm busy checking out why make test fails for gmp. > > There are a large number of bugs in qemu arm so you have to exclude the test suite for now. I forgot to mention in the email that I'm building on the pandaboard, osc build is working on the Pandaboad. :) I at first also thought it might be qemu related. > -- > To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org > > -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

1 0

[opensuse-factory] Fwd: [Bug 719076] No backlight at boot with 11.4 and 12.1m5 on laptop with Mobile Intel GM45 Express Chipset
by Roger Luedecke 07 Nov '11

07 Nov '11

Ok. There is progress on this... can we get it rolling now? Can we fix this behavior? A lesser man would have bumped openSUSE.

2 1