October 2015 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 947628] qtcurve-5 package is missing the qtcurve window decoration in Leap 42.1 Beta 1
by bugzilla_noreply＠novell.com 02 Oct '15

02 Oct '15

http://bugzilla.suse.com/show_bug.cgi?id=947628 http://bugzilla.suse.com/show_bug.cgi?id=947628#c1 --- Comment #1 from Stephan Kulow <coolo(a)suse.com> --- and how is that basesystem? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 948227] Upcoming DST change for Turkey
by bugzilla_noreply＠novell.com 02 Oct '15

02 Oct '15

http://bugzilla.novell.com/show_bug.cgi?id=948227 http://bugzilla.novell.com/show_bug.cgi?id=948227#c2 --- Comment #2 from Bernhard Wiedemann <bwiedemann(a)suse.com> --- This is an autogenerated message for OBS integration: This bug (948227) was mentioned in https://build.opensuse.org/request/show/335666 13.2+13.1 / timezone -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 947704] "Calling the YaST module `inst_proposal has failed"
by bugzilla_noreply＠novell.com 02 Oct '15

02 Oct '15

http://bugzilla.suse.com/show_bug.cgi?id=947704 http://bugzilla.suse.com/show_bug.cgi?id=947704#c12 --- Comment #12 from Stefan Seyfried <seife(a)novell.slipkontur.de> --- changing my pxelinux.cfg stanza to LABEL InstallLEAP MENU LABEL Install LEAP Beta KERNEL /memdisk APPEND initrd=/LEAP/leap.iso harddisk=1 INCLUDE pxelinux.cfg/default.iso makes memdisk 0x81 and the built-in disk 0x80. With this, I get a installation proposal without yast crashing. I have not yet proceeded with the installation (because the system is already zypper dup'ed to Leap), but this really looks like the root of the problem: only BIOS drive 0x81 available but no 0x80. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 947704] "Calling the YaST module `inst_proposal has failed"
by bugzilla_noreply＠novell.com 02 Oct '15

02 Oct '15

http://bugzilla.suse.com/show_bug.cgi?id=947704 http://bugzilla.suse.com/show_bug.cgi?id=947704#c11 Stefan Seyfried <seife(a)novell.slipkontur.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(seife(a)novell.slip | |kontur.de) | --- Comment #11 from Stefan Seyfried <seife(a)novell.slipkontur.de> --- Created attachment 649867 --> http://bugzilla.suse.com/attachment.cgi?id=649867&action=edit foo.log as requested in comment#9 Hello Steffen, foo.log is attached. One thing I remembered when looking at the hwinfo --disk output and /sys/firmware/edd/* is: I started this installation by pxelinux-booting the image like this: server:/srv/tftpboot/x86_64 # cat pxelinux.cfg/default LABEL InstallLEAP MENU LABEL Install LEAP Beta KERNEL /memdisk APPEND initrd=/LEAP/leap.iso INCLUDE pxelinux.cfg/default.iso ----- default.iso is the syslinux.cfg from the 13.2 iso, slightly massaged to allow pxe-installation of 13.2 So maybe using memdisk masks BIOS device 0x80? And my setup would be unbootable after installation anyway? But then Yast should tell me to go away and not crash :-) -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 924488] fstab entry prevents booting no emergency shell
by bugzilla_noreply＠novell.com 02 Oct '15

02 Oct '15

http://bugzilla.opensuse.org/show_bug.cgi?id=924488 http://bugzilla.opensuse.org/show_bug.cgi?id=924488#c15 Felix Miata <mrmazda(a)earthlink.net> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |arvidjaar(a)gmail.com --- Comment #15 from Felix Miata <mrmazda(a)earthlink.net> --- On i586 host kt400, upgrading to BaseSystemLegacy's systemd-210 and its deps solves the defective emergency shell problem, but introduces a new one described in http://lists.opensuse.org/opensuse-factory/2015-09/msg00671.html that I've yet to search for in Bugzilla, and for which a fix or workaround exists in /usr/lib/systemd/system/network@.service thus: --- .network@.service.01 2014-04-10 03:46:57.000000000 -0400 +++ .network@.service.03 2015-09-27 21:40:40.000000000 -0400 @@ -4,7 +4,7 @@ PartOf=network.service BindsTo=sys-subsystem-net-devices-%i.device IgnoreOnIsolate=yes -Before=network-online.target +Before=network.target [Service] Type=forking -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 939462] ibus-table input methods not working
by bugzilla_noreply＠novell.com 02 Oct '15

02 Oct '15

http://bugzilla.novell.com/show_bug.cgi?id=939462 http://bugzilla.novell.com/show_bug.cgi?id=939462#c3 --- Comment #3 from Marguerite Su <i(a)marguerite.su> --- @hillwoodroc uninstall ibus-table-zhuyin and test again. your debug output indicates there's problem with ibus-table-zhuyin. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 939594] X11 fails to start after second boot
by bugzilla_noreply＠novell.com 02 Oct '15

02 Oct '15

http://bugzilla.opensuse.org/show_bug.cgi?id=939594 http://bugzilla.opensuse.org/show_bug.cgi?id=939594#c25 --- Comment #25 from Anwesh Reddy <anwesh(a)gmx.com> --- (In reply to Dr. Werner Fink from comment #23) > (In reply to Dominique Leuenberger from comment #22) > > The code in agetty is strait forward: > > struct termios lock; > #ifdef TIOCGLCKTRMIOS > int i = (plymouth_command("--ping") == 0) ? 30 : 0; > > while (i-- > 0) { > /* > * Even with TTYReset=no it seems with systemd or plymouth > * the termios flags become changed from under the first > * agetty on a serial system console as the flags are locked. > */ > memset(&lock, 0, sizeof(struct termios)); > if (ioctl(STDIN_FILENO, TIOCGLCKTRMIOS, &lock) < 0) > break; > if (!lock.c_iflag && !lock.c_oflag && !lock.c_cflag && > !lock.c_lflag) > break; > debug("termios locked\n"); > if (i == 15 && plymouth_command("quit") != 0) > break; > sleep(1); > } > memset(&lock, 0, sizeof(struct termios)); > ioctl(STDIN_FILENO, TIOCSLCKTRMIOS, &lock); > #endif its it gdm 3.18.0.411 build ? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 947747] npm: openssl fips failed
by bugzilla_noreply＠novell.com 01 Oct '15

01 Oct '15

http://bugzilla.opensuse.org/show_bug.cgi?id=947747 http://bugzilla.opensuse.org/show_bug.cgi?id=947747#c14 --- Comment #14 from Andrei Dziahel <develop7(a)develop7.info> --- Upstream reported issue has been fixed, so here is it in obs — https://build.opensuse.org/package/rdiff/home:develop7:branches:devel:langu… -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 948368] poor peformance as compared to other modern distros
by bugzilla_noreply＠novell.com 01 Oct '15

01 Oct '15

http://bugzilla.suse.com/show_bug.cgi?id=948368 http://bugzilla.suse.com/show_bug.cgi?id=948368#c3 Richard Brown <rbrown(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED CC| |rbrown(a)suse.com Resolution|INVALID |--- Flags| |needinfo?(jeffm(a)suse.com) --- Comment #3 from Richard Brown <rbrown(a)suse.com> --- Jeff, quoting from the listed article: > - openSUSE 42.1 Leap beta with Linux 4.1, KDE Frameworks 5, Mesa 10.6.6, and GCC 4.8.5. OpenSUSE is using XFS in the home directory (where tests are run from) while the root file-system is Btrfs. Based on my understanding from this article, and experience with PTS myself, I believe that in the documented case, Phoronix has actually followed our recommendations and run the sensitive workloads against XFS Can you please double check and confirm? If we have an issue with XFS on Leap I'd rather we be absolutely sure at this point -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 947747] npm: openssl fips failed
by bugzilla_noreply＠novell.com 01 Oct '15

01 Oct '15

http://bugzilla.opensuse.org/show_bug.cgi?id=947747 http://bugzilla.opensuse.org/show_bug.cgi?id=947747#c13 --- Comment #13 from Andrei Dziahel <develop7(a)develop7.info> --- By "best way available" I mean I've honestly tried other approaches to fix it (played with configure script keys around, default 'openssl_fips' variable values) but had no success. -- You are receiving this mail because: You are on the CC list for the bug.

1 0