November 2013 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 436378] testutf8 sometimes hangs hard in X terminals
by bugzilla_noreply＠novell.com 06 Nov '13

06 Nov '13

https://bugzilla.novell.com/show_bug.cgi?id=436378 https://bugzilla.novell.com/show_bug.cgi?id=436378#c20 Stanislav Brabec <sbrabec(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |FIXED --- Comment #20 from Stanislav Brabec <sbrabec(a)suse.com> 2013-11-06 19:35:10 CET --- testutf8 no longer exists in its original form. The code that triggered or caused the hang is dropped. The dummy script does not do any more any UTF-8 detection. It is just an obsolete piece of code. Opening bug 849258 for finishing the testutf8 removal. If there is still a need for the UTF-8 detection, the old code can be reused in another way and only in place where it makes sense (e. g. shell opened by one of remote access daemons), and this bug can then be re-checked. Dummy testutf8 script: #!/bin/sh # testutf8 will be soon removed completely, it's kept only not to break # /etc/profile currently if tty -s; then exit 2 else exit 0 fi It means, that it only returns: 2 if standard input is a terminal 0 if standard input is not a terminal or if a write error occurs -- 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 848654] New: Grub failure after zypper dup rc1->rc2
by bugzilla_noreply＠novell.com 06 Nov '13

06 Nov '13

https://bugzilla.novell.com/show_bug.cgi?id=848654 https://bugzilla.novell.com/show_bug.cgi?id=848654#c0 Summary: Grub failure after zypper dup rc1->rc2 Classification: openSUSE Product: openSUSE 13.1 Version: RC 2 Platform: Other OS/Version: Other Status: NEW Severity: Critical Priority: P5 - None Component: Bootloader AssignedTo: jsrain(a)suse.com ReportedBy: kkaempf(a)suse.com QAContact: jsrain(a)suse.com Found By: Development Blocker: --- This system gets updated via "zypper dup" since years. 12.3->13.1b1 was okayish, 13.1b1->13.1rc1 good, but after 13.1rc1->13.1rc2 grub fails to boot. Grub only shows "GRUB " in the upper left corner. -- 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 7

[Bug 712508] New: rpmbuild of mysql-community-server-5.1.53-4.7.1 fails
by bugzilla_noreply＠novell.com 06 Nov '13

06 Nov '13

https://bugzilla.novell.com/show_bug.cgi?id=712508 https://bugzilla.novell.com/show_bug.cgi?id=712508#c0 Summary: rpmbuild of mysql-community-server-5.1.53-4.7.1 fails Classification: openSUSE Product: openSUSE 11.4 Version: Final Platform: x86-64 OS/Version: openSUSE 11.4 Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: leroy.nick(a)gmail.com QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/15.0.846.0 Safari/535.1 SUSE/15.0.846.0 It looks as though most of the build succeeds, but it then fails in the verification stages (see below). I've tried building 5.5.14-1.1 (from the 'openSUSE BuildService - Database' repo), with similar results. I've also tried this build on several different openSUSE 11.4 machines, with similar results. Finally, I've tried building mysql-community-server-5.1.46-2.18 on an openSUSE 11.3 machine -- this succeeds. I haven't tried building this source package on an 11.4 machine (yet). Please let me know what further information I can provide. Thanks -Nick Reproducible: Always Steps to Reproduce: 1.zypper si mysql-community-server 2.rpmbuild -bb mysql-community-server.spec Actual Results: ... INFO: relinking /usr/sbin/rcmysql -> /etc/init.d/mysql (was ./../etc/init.d/mysql) Processing files: mysql-community-server-5.1.53-4.7.1.x86_64 error: File not found by glob: /usr/src/packages/BUILDROOT/mysql-community-server-5.1.53-4.7.1.x86_64/etc/mysql/* RPM build errors: File not found by glob: /usr/src/packages/BUILDROOT/mysql-community-server-5.1.53-4.7.1.x86_64/etc/mysql/* -- 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

[Bug 710794] New: mysql-community-server: Wrong Default-Start in init script
by bugzilla_noreply＠novell.com 06 Nov '13

06 Nov '13

https://bugzilla.novell.com/show_bug.cgi?id=710794 https://bugzilla.novell.com/show_bug.cgi?id=710794#c0 Summary: mysql-community-server: Wrong Default-Start in init script Classification: openSUSE Product: openSUSE 11.4 Version: Final Platform: All OS/Version: openSUSE 11.4 Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: lauffer(a)ph-freiburg.de QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:5.0) Gecko/20100101 Firefox/5.0 In the init script of the mysql-community-server-5.1.53-4.7.1.x86_64 (openSUSE-11.4 final) we have in /etc/init.d/mysql line 19: # Default-Start: 2 3 5 Right is not trying to start in runlevel 2. The factory build of the mysql-community-server is already fixed. This is just a reminder to merge this fix in a further 11.4 update package. Reproducible: Always Steps to Reproduce: 1. insserv /etc/init.d/mysql if mysql-community-server is installed ends in a insserv warning that there is no network in runlevel 2... -- 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

[Bug 787076] New: SLE11: llvm.src.rpm is missing
by bugzilla_noreply＠novell.com 06 Nov '13

06 Nov '13

https://bugzilla.novell.com/show_bug.cgi?id=787076 https://bugzilla.novell.com/show_bug.cgi?id=787076#c0 Summary: SLE11: llvm.src.rpm is missing Classification: openSUSE Product: openSUSE Factory Version: 12.3 Milestone 0 Platform: x86-64 OS/Version: Linux Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: jengelh(a)inai.de QAContact: qa-bugs(a)suse.de CC: jw(a)suse.com, sndirsch(a)suse.com Found By: Beta-Customer Blocker: --- The SLES 11 SP 2 SDK 2 DVD contains Mesa-7.11.2-0.5.31.src.rpm with Mesa.spec, which references BuildRequires: llvm-devel, but there is no llvm*.src.rpm to be found at all on the DVDs. -- 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 352419] strace shows wrong system call
by bugzilla_noreply＠novell.com 06 Nov '13

06 Nov '13

https://bugzilla.novell.com/show_bug.cgi?id=352419 https://bugzilla.novell.com/show_bug.cgi?id=352419#c10 Stanislav Brabec <sbrabec(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO InfoProvider| |opensuse.org(a)contacts.eelis | |.net --- Comment #10 from Stanislav Brabec <sbrabec(a)suse.com> 2013-11-06 18:16:35 CET --- Retesting with openSUSE 13.1 strace-4.8, I don't see the Input/output error above. Upstream fixed it differently than the Debian patch, and the output does not contain fork(), but I guess it is an acceptable fix. What do you think about it? .. write(1, "--------------------\n", 21-------------------- ) = 21 open(NULL, O_RDONLY|O_ASYNC|O_DIRECT|O_LARGEFILE|O_NOFOLLOW|O_NOATIME|O_CLOEXEC|0xdb200000Process 12765 attached ) = 12765 [pid 12765] getpid( <unfinished ...> [pid 12764] getpid( <unfinished ...> [pid 12765] <... getpid resumed> ) = 12765 [pid 12764] <... getpid resumed> ) = 12764 [pid 12765] write(1, "[i am 12765]\n", 13[i am 12765] <unfinished ...> [pid 12764] write(1, "[i am 12764]\n", 13 <unfinished ...> [i am 12764] [pid 12765] <... write resumed> ) = 13 [pid 12764] <... write resumed> ) = 13 [pid 12765] exit_group(13) = ? [pid 12764] exit_group(13) = ? [pid 12765] +++ exited with 13 +++ +++ exited with 13 +++ -- 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 849188] New: RN -> Docs: Initializing Graphics with KMS (Kernel Mode Setting)
by bugzilla_noreply＠novell.com 06 Nov '13

06 Nov '13

https://bugzilla.novell.com/show_bug.cgi?id=849188 https://bugzilla.novell.com/show_bug.cgi?id=849188#c0 Summary: RN -> Docs: Initializing Graphics with KMS (Kernel Mode Setting) Classification: openSUSE Product: openSUSE Factory Version: 13.1 Beta 1 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Documentation AssignedTo: fs(a)suse.com ReportedBy: ke(a)suse.com QAContact: ke(a)suse.com CC: sndirsch(a)suse.com, suse-beta(a)cboltz.de Found By: Documentation Blocker: --- Since 11.4 (?) we have the following info in the release notes (time to add this to the official docs now--13.2 and later). Frank, please reassign as appropriate:   <sect2 id="sec.114.kms"> <title>Initializing Graphics with KMS (Kernel Mode Setting)</title>  <para> With openSUSE 11.3 we switched to KMS (Kernel Mode Setting) for Intel, ATI and NVIDIA graphics, which now is our default. If you encounter problems with the KMS driver support (intel, radeon, nouveau), disable KMS by adding <literal>nomodeset</literal> to the kernel boot command line. To set this permanently using Grub 2, the default boot loader, add it to the <literal>GRUB_CMDLINE_LINUX_DEFAULT</literal> kernel default load options line in your <filename>/etc/default/grub</filename> text file as root and running the terminal command </para> <screen>sudo /usr/sbin/grub2-mkconfig --output=/boot/grub2/grub.cfg</screen> <para> for the changes to take effect. Else, for Grub Legacy, add it to the kernel command line in <filename>/boot/grub/menu.lst</filename>, also done as root. This option makes sure the appropriate kernel module (intel, radeon, nouveau) is loaded with <literal>modeset=0</literal> in <filename>initrd</filename>, i.e. KMS is disabled. </para> <para> In the rare cases when loading the DRM module from <filename>initrd</filename> is a general problem and unrelated to KMS, it is even possible to disable loading of the DRM module in <filename>initrd</filename> completely. For this set the <literal>NO_KMS_IN_INITRD</literal> sysconfig variable to <literal>yes</literal> via YaST, which then recreates <filename>initrd</filename> afterwards. Reboot your machine.</para> <para> On Intel without KMS the Xserver falls back to the <literal>fbdev</literal> driver (the <literal>intel</literal> driver only supports KMS); alternatively, for legacy GPUs from Intel the "intellegacy" driver (<systemitem>xorg-x11-driver-video-intel-legacy</systemitem> package) is available, which still supports UMS (User Mode Setting). To use it, edit <filename>/etc/X11/xorg.conf.d/50-device.conf</filename> and change the driver entry to <literal>intellegacy</literal>.</para> <para> On ATI for current GPUs it falls back to <literal>radeonhd</literal>. On NVIDIA without KMS the <literal>nv</literal> driver is used (the <literal>nouveau</literal> driver supports only KMS). Note, newer ATI and NVIDIA GPUs are falling back to <literal>fbdev</literal>, if you specify the <literal>nomodeset</literal> kernel boot parameter.</para> </sect2> ======================================================================= I'll remove it from the Factory release notes soon. -- 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 809816] New: Some meniu categories not translated
by bugzilla_noreply＠novell.com 06 Nov '13

06 Nov '13

https://bugzilla.novell.com/show_bug.cgi?id=809816 https://bugzilla.novell.com/show_bug.cgi?id=809816#c0 Summary: Some meniu categories not translated Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: Other OS/Version: SUSE Other Status: NEW Severity: Normal Priority: P5 - None Component: Translations AssignedTo: ke(a)suse.com ReportedBy: embar(a)super.lt QAContact: ke(a)suse.com Found By: --- Blocker: --- Created an attachment (id=530047) --> (http://bugzilla.novell.com/attachment.cgi?id=530047) Not translated some categories of programs User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:19.0) Gecko/20100101 Firefox/19.0 I upgraded system from openSUSE 12.2 to 12.3 I see, that some menu categories are not translated in Lithuanian, but can not found any related empty string to these words. For exmaple, not translated: Science, Education, Mathematics, Teaching Reproducible: Always Steps to Reproduce: 1. in openSUSE 12.3 change locale to Lithuanian 2. Press SuSE button at corn (to open meniu) Actual Results: Some categories of programs are not translated Expected Results: All categories translated -- 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 5

[Bug 848778] New: yast2 --install: Add context menu entry to remove orphaned packages
by bugzilla_noreply＠novell.com 06 Nov '13

06 Nov '13

https://bugzilla.novell.com/show_bug.cgi?id=848778 https://bugzilla.novell.com/show_bug.cgi?id=848778#c0 Summary: yast2 --install: Add context menu entry to remove orphaned packages Classification: openSUSE Product: openSUSE 13.1 Version: RC 2 Platform: Other OS/Version: Other Status: NEW Severity: Enhancement Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: johannesobermayr(a)gmx.de QAContact: jsrain(a)suse.com Found By: --- Blocker: --- Created an attachment (id=565959) --> (http://bugzilla.novell.com/attachment.cgi?id=565959) screenshot User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.21 (KHTML, like Gecko) rekonq/2.3.2 Safari/537.21 All packages in attached screenshot should be selected for removal via a context menu entry (All in This list -> Remove orphaned) 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 2

[Bug 848706] New: YaST Sound Configuration volume gui too large
by bugzilla_noreply＠novell.com 06 Nov '13

06 Nov '13

https://bugzilla.novell.com/show_bug.cgi?id=848706 https://bugzilla.novell.com/show_bug.cgi?id=848706#c0 Summary: YaST Sound Configuration volume gui too large Classification: openSUSE Product: openSUSE 13.1 Version: RC 2 Platform: PC OS/Version: Other Status: NEW Severity: Minor Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: kalenic(a)gmail.com QAContact: jsrain(a)suse.com Found By: --- Blocker: --- Created an attachment (id=565912) --> (http://bugzilla.novell.com/attachment.cgi?id=565912) Minimal width and height are 1405x443 User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/30.0.1599.114 Safari/537.36 When opening Volume GUI in sound configuration window doesn't scale good. Vertical scaling is ok, but horizontal is too big for some screens. I have 1280x1024 resolution and it cant fit. The main problem is that the buttons are located too far out to be seen. Minimal width and height are 1405x443 pixels Reproducible: Always Steps to Reproduce: 1.Open Yast 2.Open Sound Configuration 3.Open Volume in "Other" menu Expected Results: Volume window should scale horizontally to fit reasonable pixel width and show buttons This happens on default GNOME installation, with default theme and DPI -- 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