March 2013 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 808487] New: Yast Partitioner does not detect encrypted LVM as encrypted
by bugzilla_noreply＠novell.com 26 Mar '13

26 Mar '13

https://bugzilla.novell.com/show_bug.cgi?id=808487 https://bugzilla.novell.com/show_bug.cgi?id=808487#c0 Summary: Yast Partitioner does not detect encrypted LVM as encrypted Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: x86-64 OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: londycircle(a)gmail.com QAContact: jsrain(a)suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.22 (KHTML, like Gecko) Chrome/25.0.1364.160 Safari/537.22 I originally created my encrypted LVM with the 12.1 installer. When I installed 12.2 I imported the partition setup and it worked fine. I installed 12.3 rc2 yesterday and I again imported the partition and the installation went smoothly. When it boots up, I enter my passphrase like I normally do and it boots up fine. When I open up Yast Partitioner, my LVM does not have the encrypted label. On the Installation Summary page, it says "Set up encrypted dm device on /dev/sda3" in red letters. 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 10

[Bug 808020] New: Installer writes LUKS header onto existing filesystems while creating filesystem layout, before starting install
by bugzilla_noreply＠novell.com 26 Mar '13

26 Mar '13

https://bugzilla.novell.com/show_bug.cgi?id=808020 https://bugzilla.novell.com/show_bug.cgi?id=808020#c0 Summary: Installer writes LUKS header onto existing filesystems while creating filesystem layout, before starting install Classification: openSUSE Product: openSUSE 12.3 Version: RC 2 Platform: Other OS/Version: Other Status: NEW Severity: Critical Priority: P5 - None Component: Installation AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: wstephenson(a)suse.com QAContact: jsrain(a)suse.com Found By: Development Blocker: --- Will Stephenson <wstephenson(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flag| |SHIP_STOPPER?(coolo(a)suse.co | |m) I just wrecked an installed system with the installer, without starting an installation. Background: I have a production installation on sda1-4 (GPT/UEFI/no Secure Boot). I wanted to put an encrypted LVM installation on existing test partitions sda5 and 6. I booted the Build110 DVD installer from USB stick and got as far as the partitioner, clicked LVM, Encrypted VG, was prompted for a password and got a proposal that IIRC put a VG across sda3,4,5,6. At this point I decided to try something else* and aborted the installer using the Abort button, was dumped back to linuxrc and rebooted. I got a grub2 rescue prompt, sda3 and sda4 are now crypto_LUKS partitions requiring the password to activate - I haven't tried mounting them yet. -- 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 9

[Bug 811715] New: bugzilla.novell.com: Can't select openSUSE 12.3 as "Operating System"
by bugzilla_noreply＠novell.com 26 Mar '13

26 Mar '13

https://bugzilla.novell.com/show_bug.cgi?id=811715 https://bugzilla.novell.com/show_bug.cgi?id=811715#c0 Summary: bugzilla.novell.com: Can't select openSUSE 12.3 as "Operating System" Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: All OS/Version: SUSE Other Status: NEW Severity: Minor Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: colAflash(a)gmx.net QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:19.0) Gecko/20100101 Firefox/19.0 On https://bugzilla.novell.com "openSUSE 12.3" is not listed at "Operating System" when creating a new bug. When changing an existing bug, the corresponding field is called "Platform". Don't be confused. "openSUSE 12.3" can be selected as "Product" but not as "Operating System". And because "SUSE 6.3" to "openSUSE 12.2" are listed at "Operating System" I think "openSUSE 12.3" should be there too. 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 0

[Bug 810969] New: Automounting with xfce4 and thunar doesn't work
by bugzilla_noreply＠novell.com 26 Mar '13

26 Mar '13

https://bugzilla.novell.com/show_bug.cgi?id=810969 https://bugzilla.novell.com/show_bug.cgi?id=810969#c0 Summary: Automounting with xfce4 and thunar doesn't work Classification: openSUSE Product: openSUSE 12.2 Version: Final Platform: i586 OS/Version: openSUSE 12.2 Status: NEW Severity: Major Priority: P5 - None Component: Xfce AssignedTo: bnc-team-xfce(a)forge.provo.novell.com ReportedBy: Franz.Reinhardt(a)wenglor.com QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:19.0) Gecko/20100101 Firefox/19.0 I start with kdm and switch to the xfce4 environment. Is configure Thunar to handle automounting inside the GUI. If then plugin a USB drive, nothing happens. In Kde it works! Reproducible: Always Steps to Reproduce: 1. Plugin in a USB device 2. Plugout 3. Plugin Actual Results: cat ~/.xsession-errors contains: thunar-volman: Unsupported USB device type. thunar-volman: Unsupported USB device type. thunar-volman: Unknown block device type. thunar-volman: Could not detect the volume corresponding to the device. No automounting done at all, no device visible in thunar Expected Results: It should 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 811541] New: openSUSE 12.3: Eclipse crashes when workspace was selected
by bugzilla_noreply＠novell.com 26 Mar '13

26 Mar '13

https://bugzilla.novell.com/show_bug.cgi?id=811541 https://bugzilla.novell.com/show_bug.cgi?id=811541#c0 Summary: openSUSE 12.3: Eclipse crashes when workspace was selected Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: 64bit OS/Version: openSUSE 12.2 Status: NEW Severity: Critical Priority: P5 - None Component: Development AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: andi(a)xenoage.com QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created an attachment (id=531638) --> (http://bugzilla.novell.com/attachment.cgi?id=531638) JVM crash log User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:19.0) Gecko/20100101 Firefox/19.0 This in on openSUSE 12.3, but it was not registered in bugzilla yet, please move this bug when possible! -- Eclipse, both Indigo and Juno, crash on both OpenJDK and SunJDK, when selecting a workspace. The first selected workspace works, but as soon as another workspace is selected, the JVM crashes. # # A fatal error has been detected by the Java Runtime Environment: # # SIGSEGV (0xb) at pc=0x00007f4dc7776ba0, pid=3669, tid=139972257920768 # # JRE version: 7.0 # Java VM: Java HotSpot(TM) 64-Bit Server VM (19.0-b05 mixed mode linux-amd64 compressed oops) # Problematic frame: # C [libgobject-2.0.so.0+0x19ba0] g_object_get_qdata+0x20 # # An error report file with more information is saved as: # /home/andi/hs_err_pid3669.log # # If you would like to submit a bug report, please visit: # http://java.sun.com/webapps/bugreport/crash.jsp # Reproducible: Always Steps to Reproduce: 1. Start eclipse 2. Select a workspace and quit 3. Start eclipse again, but select a different workspace. 4. JVM/Eclipse crash immediately. -- 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 698030] New: ypbind: Fails to recognize connectivity with NetworkManager
by bugzilla_noreply＠novell.com 26 Mar '13

26 Mar '13

https://bugzilla.novell.com/show_bug.cgi?id=698030 https://bugzilla.novell.com/show_bug.cgi?id=698030#c0 Summary: ypbind: Fails to recognize connectivity with NetworkManager Classification: openSUSE Product: openSUSE 12.1 Version: Factory Platform: All OS/Version: SuSE Other Status: NEW Severity: Major Priority: P5 - None Component: Basesystem AssignedTo: jeffm(a)novell.com ReportedBy: jeffm(a)novell.com QAContact: qa(a)suse.de Found By: Development Blocker: --- # ypbind -debug 27165: parsing config file 27165: Trying entry: domain lan.jeffreymahoney.com server 192.168.1.13 27165: parsed domain 'lan.jeffreymahoney.com' server '192.168.1.13' 27165: add_server() domain: lan.jeffreymahoney.com, host: 192.168.1.13, slot: 0 27165: [Welcome to ypbind-mt, version 1.32] 27165: ping interval is 20 seconds 27167: NetworkManager is running. 27167: No network is available. Waiting... 27167: interface: org.freedesktop.DBus, object path: /org/freedesktop/DBus, method: NameAcquired ^C27166: Signal (2) for quitting program arrived. This is due to NetworkManager offering more than just NM_STATE_CONNECTED. It now offers NM_STATE_CONNECTED_{LOCAL,SITE,GLOBAL} using different state numbers than it did previously. I have a patch I'll attach. -- 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 810823] New: SLES 11 SP3 Beta_2 OS does not see the iscsi LUN for installation during iSCSI Boot Installation.
by bugzilla_noreply＠novell.com 26 Mar '13

26 Mar '13

https://bugzilla.novell.com/show_bug.cgi?id=810823 https://bugzilla.novell.com/show_bug.cgi?id=810823#c0 Summary: SLES 11 SP3 Beta_2 OS does not see the iscsi LUN for installation during iSCSI Boot Installation. Classification: openSUSE Product: openSUSE 11.4 Version: RC 2 Platform: x86-64 OS/Version: SLES 11 Status: NEW Severity: Major Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: sony.john-n(a)emulex.com QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created an attachment (id=531002) --> (http://bugzilla.novell.com/attachment.cgi?id=531002) snapshot of error message during installation User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:19.0) Gecko/20100101 Firefox/19.0 The test done was installing SLES 11 SP3 Beta 2 on a remote LUN, and test failed with "No Hard Disk found for installation". >From the shell when the command "iscsiadm -m fw" is run, the boot target details are shown fine. When the command "iscsiadm -m fw -l" is run, error message "/usr/sbin/rcopen-iscsi: No such file or directory" and "could not connect to iscsid" gets displayed. If we start the open-iscsi service and then issue the command "iscsiadm -m fw -l", login to target happens fine. After the login happened fine, the LUN is also shown up fine for installation. Reproducible: Always Steps to Reproduce: 1. Configure boot target on BE3 adapter using iSCSI Select Utility 2. Continue with the installation. 3. Actual Results: The LUN is not shown up for installation. Expected Results: The LUN should have shown for installation. -- 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 9

[Bug 450196] ext3 - recovering journal on / on first boot on new kernel/fresh system updates
by bugzilla_noreply＠novell.com 25 Mar '13

25 Mar '13

https://bugzilla.novell.com/show_bug.cgi?id=450196 https://bugzilla.novell.com/show_bug.cgi?id=450196#c133 Christian Boltz <suse-beta(a)cboltz.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |REOPENED InfoProvider|suse-beta(a)cboltz.de | --- Comment #133 from Christian Boltz <suse-beta(a)cboltz.de> 2013-03-25 22:52:27 CET --- (In reply to comment #131) > Removing all instances I can do, but if it means sifting through > https://build.opensuse.org/request/show/149258 to locate selected instances > that need removal it isn't going to happen. My /etc/init.d/ntp (Factory, slightly newer than 12.3) doesn't contain --noadjfile, so I'd say you can remove --noadjfile everywhere. (As usual, a backup can't hurt ;-) About the OBS user interface: ENOTMYBUG, but I'm sure the OBS team is open for suggestions how to make it better ;-) In other words, open a bug against the buildservice or discuss it on the opensuse-buildservice ML. -- 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 787688] New: Evolution fails marks messages as unread
by bugzilla_noreply＠novell.com 25 Mar '13

25 Mar '13

https://bugzilla.novell.com/show_bug.cgi?id=787688 https://bugzilla.novell.com/show_bug.cgi?id=787688#c0 Summary: Evolution fails marks messages as unread Classification: openSUSE Product: openSUSE 12.2 Version: Final Platform: All OS/Version: openSUSE 12.2 Status: NEW Severity: Normal Priority: P5 - None Component: Evolution AssignedTo: bnc-team-evolution(a)forge.provo.novell.com ReportedBy: mike.catanzaro(a)gmail.com QAContact: lakhil(a)novell.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Ubuntu; Linux i686; rv:16.0) Gecko/20100101 Firefox/16.0 Evolution marks Gmail messages as read while I read them, but the next time I open Evolution, or if I check my mail online, they are marked as unread. This will be fixed in Evolution 3.6.2; perhaps it can be backported? https://bugzilla.gnome.org/show_bug.cgi?id=685034#c7 There's also a couple of workarounds discussed in that topic. Reproducible: Sometimes -- 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 11

[Bug 803126] New: Problem with installation from KDE Live using mount by label
by bugzilla_noreply＠novell.com 25 Mar '13

25 Mar '13

https://bugzilla.novell.com/show_bug.cgi?id=803126 https://bugzilla.novell.com/show_bug.cgi?id=803126#c0 Summary: Problem with installation from KDE Live using mount by label Classification: openSUSE Product: openSUSE 12.3 Version: RC 1 Platform: x86-64 OS/Version: SUSE Other Status: NEW Severity: Normal Priority: P5 - None Component: Installation AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: f.de.kruijf(a)gmail.com QAContact: jsrain(a)suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:18.0) Gecko/20100101 Firefox/18.0 I use in setting up the partitions when installing using KDE Live CD the mount by label. In that case the system halts during the boot after the installation. It asks for the root password and suggests the use of journalctl -b to look for an error message. This reveals a timeout in mounting the last partitions to be mounted in /etc/fstab after that it suggests to continue with systemctl default or systemctl default. Both commands result in the same situation, however a "mount /<folder with the problematic partition>" and systemctl default makes the system to continue and results in the login screen. Reproducible: Always Steps to Reproduce: 1. Install a system from the KDE Live CD 2. Choose in the partition setup to mount the partitions by label also giving labels on the partitions. 3. The first boot stops and asks for the root password 4. Provide the password and look for the partition with trouble using "journalctl -b" 5. mount that partition with "mount /<mount_point>" 6. Continue with "systemctl default" Actual Results: Without step 5 above, you can't get on with the installation Expected Results: The first boot should continue without any problem. On another system I have 6 more partitions that I want to mount by label. I need to give the command "mount -all" before the system continues. Even the swap partition did not get mounted. -- 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