November 2014 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 903514] wrong text in drbd.de.po
by bugzilla_noreply＠novell.com 04 Nov '14

04 Nov '14

http://bugzilla.suse.com/show_bug.cgi?id=903514 --- Comment #3 from nick wang <nwang(a)suse.com> --- In case any misunderstanding, i plan to replace "and" to "with". So the line will be: =============== You can either omit the device name or the string minor with the minor number. If you omit the name, a default of /dev/drbdminor will be used. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 903514] wrong text in drbd.de.po
by bugzilla_noreply＠novell.com 04 Nov '14

04 Nov '14

http://bugzilla.suse.com/show_bug.cgi?id=903514 nick wang <nwang(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |CONFIRMED --- Comment #2 from nick wang <nwang(a)suse.com> --- (In reply to Sarah Kriesch from comment #0) > In the entry 29 of the file drbd.de.po (every translation) you have written > the following wrong text: > > Or either omit the name or minor and the minor number. since i am not a native speaker, note the lines that i plan to change, if anything wrong, please feel free to let me know, thanks in advanced: =============== You can either omit the name or the string minor and the minor number. If you omit the name, a default of /dev/drbdminor will be used. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 903736] disk device name changed after update 13.1->13.2, grub2 can not load initrd, system does not boot
by bugzilla_noreply＠novell.com 04 Nov '14

04 Nov '14

http://bugzilla.opensuse.org/show_bug.cgi?id=903736 Mircea Kitsune <sonichedgehog_hyperblast00(a)yahoo.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |sonichedgehog_hyperblast00@ | |yahoo.com --- Comment #2 from Mircea Kitsune <sonichedgehog_hyperblast00(a)yahoo.com> --- I'm can't confirm 100% that this is what did it for me. But after upgrading from 13.1 to 13.2 via "zypper dup" yesterday, on both my laptop and PC, grub2 was completely broken. It would only show a few lines of text flickering on the screen, then said that I must load a Kernel first. I coult only fix my system by booting into the recovery console from the 13.1 DVD, and making a completely new grub2 install. This is a really severe bug, which others might not know to fix as easily... I hope it will be looked into soon. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 902464] autoyast after reboot does not load network before scripts
by bugzilla_noreply＠novell.com 03 Nov '14

03 Nov '14

http://bugzilla.novell.com/show_bug.cgi?id=902464 --- Comment #7 from Luiz Angelo Daros de Luca <luizluca(a)tre-sc.jus.br> --- yast tried to start wicked as I would expect and it gave me an error (attachment 611139). If it succeeded, everything would work. Shouldn't the error be a bug? Maybe something is missing in systemd deps but I'm no expert to debug it. There is a valid config and network is brough up after yast without intervention. However, I cannot restart wicked(d). Anyway, as you tell me, there is no place in autoyast to run a script in the installed system context with network. It would be the perfect place to join a windows domain :-) I don't see "save the settings of the ask section in a temporary file" as a solution as it would not allow me to check if the operation has succeeded (i.e.: password was right). It would be a blind shot. In the worst case, it is a regression for me as it worked for OS13.1 and before (I guess since 12.1). Can I reopen it? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 903744] New: lightdm does not automatically unlock gnome-keyring via PAM any more
by bugzilla_noreply＠novell.com 03 Nov '14

03 Nov '14

http://bugzilla.opensuse.org/show_bug.cgi?id=903744 Bug ID: 903744 Summary: lightdm does not automatically unlock gnome-keyring via PAM any more Classification: openSUSE Product: openSUSE Factory Version: 201410* Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: X11 Applications Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: gber(a)opensuse.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- >From http://lists.opensuse.org/opensuse-factory/2014-11/msg00049.html: On openSUSE 13.1 I was used to get the Gnome keyring automagically unlocked whenever I log in. This doesn't happen on a new installation of openSUSE Factory. I've tracked it down to the following line in /etc/pam.d/common-session: session optional pam_gnome_keyring.so auto_start only_if=gdm,gdm-password,lxdm,lightdm Everything looks OK, but even with the Gnome runtime support enabled in xfce4, the keyring stays locked. What's surprising is the following output of "systemctl status display-manager.service": Nov 03 18:08:36 saturn display-manager[25273]: /etc/vconsole.conf available Nov 03 18:08:36 saturn display-manager[25273]: KEYMAP: de-latin1-nodeadkeys Nov 03 18:08:36 saturn display-manager[25273]: Command: localectl set-keymap de-latin1-nod...ys Nov 03 18:08:36 saturn lightdm[25310]: pam_unix(lightdm-greeter:session): session opened ...=0) Nov 03 18:08:36 saturn display-manager[25273]: Starting service lightdm..done Nov 03 18:08:52 saturn lightdm[25339]: pam_unix(xdm:session): session opened for user man...=0) Look at the "xdm" in the last line. When I added some debugging code to pam_gnome_keyring.so, I saw that the display's manager name is indeed passed as "xdm" instead of "lightdm", which then resulted to not unlock the keyring because the manager wasn't in the list of supported ones. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 893648] [Factory 20140820] Plymouth not working on live USB
by bugzilla_noreply＠novell.com 03 Nov '14

03 Nov '14

http://bugzilla.opensuse.org/show_bug.cgi?id=893648 --- Comment #9 from S. B. <sb56637(a)gmail.com> --- Today's update fixed Plymouth on bootup. It appears to just be a fade-in backdrop, with no other animation? Would it be possible to add Plymouth during shutdown as well? It currently shows console vomit during shutdown. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 903736] disk device name changed after update 13.1->13.2, grub2 can not load initrd, system does not boot
by bugzilla_noreply＠novell.com 03 Nov '14

03 Nov '14

http://bugzilla.opensuse.org/show_bug.cgi?id=903736 István Kapcsándi <istvan.kapcsandi(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |istvan.kapcsandi(a)gmail.com --- Comment #1 from István Kapcsándi <istvan.kapcsandi(a)gmail.com> --- Same here, only difference that my setup is one boot partition (ext4) and one luks_crypt partition (lvm). I had to change in /etc/cryptab /etc/fstab /etc/default/grub_installdevice the device names from /dev/disk/by-id/ata-KINGSTON_SVP200S3120G_50026B722B00B326-part1 to /dev/disk/by-id/ata-KINGSTON_SVP200S3120G_._50026B722B00B326-part1 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 903544] New: Screen brightness not working on Sony laptop
by bugzilla_noreply＠novell.com 03 Nov '14

03 Nov '14

http://bugzilla.opensuse.org/show_bug.cgi?id=903544 Bug ID: 903544 Summary: Screen brightness not working on Sony laptop Classification: openSUSE Product: openSUSE 13.1 Version: Final Hardware: x86-64 OS: openSUSE 13.1 Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-maintainers(a)forge.provo.novell.com Reporter: adriano.argiolas(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- The keyboard shortcuts Fn-F5 and Fn-F6 don't change the screen brightness. The OSD shows the brightness being altered, but the screen stays at full brightness. Extract of dmesg: [ 9.778444] sony_laptop: Sony Notebook Control Driver v0.6 [ 9.778581] input: Sony Vaio Keys as /devices/LNXSYSTM:00/device:00/PNP0A08:00/device:02/SNY5001:00/input/input4 [ 9.778644] input: Sony Vaio Jogdial as /devices/LNXSYSTM:00/device:00/PNP0A08:00/device:02/SNY5001:00/input/input5 [ 9.819901] sony_laptop: brightness ignored, must be controlled by ACPI video driver Output of spicctrl -a: /dev/sonypi: No such file or directory in /dev/sonypi there is a 0 length file available output of uname -a Linux 3.11.10-21-desktop #1 SMP PREEMPT Mon Jul 21 15:28:46 UTC 2014 (9a9565d) x86_64 x86_64 x86_64 GNU/Linux -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 903276] claws-mail please update to 3.11.0 from GNOME:Apps
by bugzilla_noreply＠novell.com 03 Nov '14

03 Nov '14

http://bugzilla.novell.com/show_bug.cgi?id=903276 Dirk Weber <d_werner(a)gmx.net> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |d_werner(a)gmx.net --- Comment #4 from Dirk Weber <d_werner(a)gmx.net> --- Actually there exists already Claws Mail 3.11.1 which according to the news contains further improvements for STARTTLS. BTW: after switching from SSL to STARTTLS gmx.net is working fine for me also with 3.10.1. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 700416] click in scroll area causes more than one page advance or retard
by bugzilla_noreply＠novell.com 03 Nov '14

03 Nov '14

http://bugzilla.opensuse.org/show_bug.cgi?id=700416 --- Comment #30 from Felix Miata <mrmazda(a)earthlink.net> --- This continues in 13.2 on hosts (at least) m7ncd (Athlon) and gx28b (Hyperthreading 32 bit P4) using PS/2-connected Logitech Trackman Marble. -- You are receiving this mail because: You are on the CC list for the bug.

1 0