July 2013 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 829428] New: keyboard reset after suspend to ram
by bugzilla_noreply＠novell.com 15 Jul '13

15 Jul '13

https://bugzilla.novell.com/show_bug.cgi?id=829428 https://bugzilla.novell.com/show_bug.cgi?id=829428#c0 Summary: keyboard reset after suspend to ram Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: x86-64 OS/Version: openSUSE 12.3 Status: NEW Severity: Normal Priority: P5 - None Component: X.Org AssignedTo: bnc-team-xorg-bugs(a)forge.provo.novell.com ReportedBy: pmlists(a)free.fr QAContact: xorg-maintainer-bugs(a)forge.provo.novell.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:22.0) Gecko/20100101 Firefox/22.0 Hi, I use a custom .Xmodmap and "xset r rate 250 50" settings. But after a supsend to ram "s2ram", often these settings are lost and I have to type "xset r rate 250 50;xmodmap .Xmodmap" to get them back. There was no such problem with earlier opensuse versions. TIA for any help, Peter Reproducible: Sometimes Steps to Reproduce: 1. run X11 (I use fvwm and xscreensaver) 2. when idle for a long time, run s2ram (done with crond) 3. get back and wake up the system: often, the custom xmodmap settings are lost Actual Results: the personal xmodmap and xset settings are often lost after a s2ram Expected Results: the personal xmodmap and xset settings should never be lost after a s2ram -- 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 829367] New: devel:languages:python/python-qt4: Bug
by bugzilla_noreply＠novell.com 15 Jul '13

15 Jul '13

https://bugzilla.novell.com/show_bug.cgi?id=829367 https://bugzilla.novell.com/show_bug.cgi?id=829367#c0 Summary: devel:languages:python/python-qt4: Bug Classification: openSUSE Product: openSUSE.org Version: unspecified Platform: Other URL: https://build.opensuse.org/package/show/devel:language s:python/python-qt4?expand=1 OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: OBS Request AssignedTo: speilicke(a)suse.com ReportedBy: termim(a)gmail.com QAContact: adrian(a)suse.com Found By: Community User Blocker: Yes Web UI can't expand source list claiming that there is a conflict in python3-qt4.spec which is missing in the link ... see https://build.opensuse.org/package/show/devel:languages:python/python-qt4?e… -- 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 816739] New: Problems with 4096 byte sector size
by bugzilla_noreply＠novell.com 15 Jul '13

15 Jul '13

https://bugzilla.novell.com/show_bug.cgi?id=816739 https://bugzilla.novell.com/show_bug.cgi?id=816739#c0 Summary: Problems with 4096 byte sector size Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: All OS/Version: openSUSE 12.3 Status: NEW Severity: Minor Priority: P5 - None Component: Bootloader AssignedTo: jsrain(a)suse.com ReportedBy: f+novell(a)congenio.de QAContact: jsrain(a)suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:20.0) Gecko/20100101 Firefox/20.0 When I did an upgrade from openSUSE 12.2 to 12.3, I stumbled over these error messages: Installing: grub2-branding-openSUSE-12.3-6.11.3 ................................[done] Additional rpm output: Generating grub.cfg ... Found theme: /boot/grub2/themes/openSUSE/theme.txt Found linux image: /boot/vmlinuz-3.7.10-1.1-default Found initrd image: /boot/initrd-3.7.10-1.1-default Found linux image: /boot/vmlinuz-3.4.33-2.24-default Found initrd image: /boot/initrd-3.4.33-2.24-default ERROR: unsupported sector size 4096 on /dev/sdd. ERROR: unsupported sector size 4096 on /dev/sdd. ERROR: unsupported sector size 4096 on /dev/sdd. done These errors are in the postinstall-script from a call to /usr/sbin/grub2-mkconfig -o /boot/grub2/grub.cfg, which calls /etc/grub.d/30_os-prober in turn. Somewhere in there, the 4096 byte sector size seems to be a problem. The system boots, so this seems to be only a cosmetic problem. Reproducible: Always Steps to Reproduce: 1. Call '/usr/sbin/grub2-mkconfig -o /boot/grub2/grub.cfg' 2. 3. Actual Results: ERROR: unsupported sector size 4096 on /dev/sdd. Expected Results: no errors -- 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 818441] New: GRUB Menu: zypper up often wipes out custom grub.cfg changes, created by modifications to theme.txt
by bugzilla_noreply＠novell.com 15 Jul '13

15 Jul '13

https://bugzilla.novell.com/show_bug.cgi?id=818441 https://bugzilla.novell.com/show_bug.cgi?id=818441#c0 Summary: GRUB Menu: zypper up often wipes out custom grub.cfg changes, created by modifications to theme.txt Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: x86-64 OS/Version: openSUSE 12.3 Status: NEW Severity: Normal Priority: P5 - None Component: Bootloader AssignedTo: jsrain(a)suse.com ReportedBy: tonysu(a)su-networking.com QAContact: jsrain(a)suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:20.0) Gecko/20100101 Firefox/20.0 whenever "zypper up" updates the components used to re-build grub.cfg, previous customizations are wiped out. Workaround: Script the changes so that they can be re-applied easily Reproducible: Always Steps to Reproduce: Although various changes can be made various ways, perhaps the easiest way is to use the script and replacement grub menu theme background I posted with this bug https://bugzilla.novell.com/show_bug.cgi?id=817866 1. Extract the package and run the script following the instructions in the script's first few lines, this will a. Modify the grub menu item width, font size, and progress bar b. Point to a different background image 2. Sometime, usually not longer than a week for me, a "zypper up" seems to re-apply the original theme.txt configuration (don't know where it's coming from) Actual Results: After theme.txt has been replace with the original from I don't know where, the original default configuration is used to re-build grub.cfg Expected Results: I don't know what in a "zypper up" might be re-applying a default theme.txt configuration, but ti's wiping out the changes entered into theme.txt IIRC it should also be possible to point to a different configuration file than theme.txt, so a possible workaround might be to implement that way instead of editing theme.txt but would have to be tested. Regardless, AFAIK, editing theme.txt directly is supposed to be a recognized and recommended way to alter the appearance of the GRUB2 menu. Possible solution? For each and every component used to re-build grub.cfg, IMO should remain untouched unless a re-install is requested. This is assuming there is even a good reason to re-build grub.cfg (I haven't looked closely at why "zypper up" might be doing this). Recommending "Normal" importance because this could be a significant problem for someone who simply edits theme.txt and does not use a script like what I provided for simple and quick re-implementation. -- 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 824859] New: 12.3 restore won't open a file creating using 12.2 dump and bzlib compression
by bugzilla_noreply＠novell.com 15 Jul '13

15 Jul '13

https://bugzilla.novell.com/show_bug.cgi?id=824859 https://bugzilla.novell.com/show_bug.cgi?id=824859#c0 Summary: 12.3 restore won't open a file creating using 12.2 dump and bzlib compression Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: x86-64 OS/Version: openSUSE 12.3 Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: mfrost(a)rooville.com QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/27.0.1453.110 Safari/537.36 Before doing a full reinstall of the OS to migrate from opensuse 12.2 to 12.3, I used 'dump' under 12.2 on my filesystems to locally attached drive. An example command I used was dump 0 -j 9 -f root.dump.bz / When I remounted the drive after the 12.3 install (and after installing the 12.3 dump package), I ran restore -if root.dump.bz and was presented with restore: This restore version doesn't support bzlib decompression This is with dump-0.4b43-12.1.1.x86_64. The man page provided with this package still mentions that the -j option is supported for 'dump' so I'd assume that it works for 'restore' as well. Or it should. I grabbed the 12.2 package from a repository (dump-0.4b43-9.1.2.x86_64.rpm) and pulled it apart with rpm2cpio. When I tried the restore using the 12.2 restore command, it worked like a champ. Just a guess, but I'm wondering if perhaps there was some build problem with the 12.3 dump where it maybe couldn't find the bzlib library or other devel files and therefore didn't include support for it when it should have? In general, I wouldn't think one would want to be removing functionality from functions as critical as those doing backup and restore. I see that the 12.2 version of restore is linked against libbz2.so.1 (via ldd) whereas the 12.3 version is not. I also confirmed that while the -j option is mentioned in the 12.3 dump man page, if you try to use -j with the 12.3 dump command it tells you the argument is not supported. Reproducible: Always Steps to Reproduce: 1. See comments in Details. 2. 3. Actual Results: See comments in Details. Expected Results: Read my 12.2-generated dump file. -- 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 827459] New: perl-Bootloader: chokes on non-existence of /proc/misc
by bugzilla_noreply＠novell.com 15 Jul '13

15 Jul '13

https://bugzilla.novell.com/show_bug.cgi?id=827459 https://bugzilla.novell.com/show_bug.cgi?id=827459#c0 Summary: perl-Bootloader: chokes on non-existence of /proc/misc Classification: openSUSE Product: openSUSE Factory Version: 13.1 Milestone 1 Platform: x86-64 OS/Version: Linux Status: NEW Severity: Minor 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 Found By: Beta-Customer Blocker: --- Created an attachment (id=546240) --> (http://bugzilla.novell.com/attachment.cgi?id=546240) screenshot Installation of factory du jour reported an error. -- 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 828833] New: Apparmor has been Stripped from an Enormous Amount of Functionality
by bugzilla_noreply＠novell.com 15 Jul '13

15 Jul '13

https://bugzilla.novell.com/show_bug.cgi?id=828833 https://bugzilla.novell.com/show_bug.cgi?id=828833#c0 Summary: Apparmor has been Stripped from an Enormous Amount of Functionality Classification: openSUSE Product: openSUSE 12.2 Version: Final Platform: x86-64 OS/Version: openSUSE 12.2 Status: NEW Severity: Major Priority: P5 - None Component: AppArmor AssignedTo: suse-beta(a)cboltz.de ReportedBy: secure(a)aphofis.com QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:21.0) Gecko/20100101 Firefox/21.0 Apparmor no longer has provision to set notifications. Apparmor no longer has any provisions to generate reports. Apparmor has had all its language and help support stripped to a single line of help text. Without the help legends its impossible to understand If I set any profile to complain I cant call for its log via the traditional report writer that’s been left out. The notification ability and options have been stripped. Why leave functionality to create a profile when there's no report writer to know what its doing With all profiles set to enforce there is no report writter or 'readme' type application to know if apparmor is doing anything at all? Reproducible: Always Steps to Reproduce: 1.Yast>System and Security>Apparmor 2. 3. Actual Results: It cannot be confirmed that in its current state it does anything at all Expected Results: Put back the code, well most of it that did work the best in say v11.3??? I may be an old software analyst and DBA, but the fundamental of removing code outright that did work, even partially, as fundamentally wrong WHY strip the code, even the bits that did work? We use to AppArmor as a Marketing and Advertisement about our positive product? -- 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 827509] New: openSUSE:12.3/pcmanfm: Bug
by bugzilla_noreply＠novell.com 14 Jul '13

14 Jul '13

https://bugzilla.novell.com/show_bug.cgi?id=827509 https://bugzilla.novell.com/show_bug.cgi?id=827509#c0 Summary: openSUSE:12.3/pcmanfm: Bug Classification: openSUSE Product: openSUSE.org Version: unspecified Platform: x86-64 OS/Version: openSUSE 12.3 Status: NEW Severity: Minor Priority: P5 - None Component: 3rd party software AssignedTo: andrea(a)opensuse.org ReportedBy: jcsl(a)eresmas.com QAContact: opensuse-communityscreening(a)forge.provo.novell.com Found By: --- Blocker: --- Hi. Tabs does not show current location but "..." always. Bug have been reported and there are patches available as you can see in http://sourceforge.net/tracker/?func=detail&aid=3607427&group_id=156956&ati… Using the Factory repository does not solve the problem. Greetings. -- 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 820984] New: No translation by copy progress
by bugzilla_noreply＠novell.com 14 Jul '13

14 Jul '13

https://bugzilla.novell.com/show_bug.cgi?id=820984 https://bugzilla.novell.com/show_bug.cgi?id=820984#c0 Summary: No translation by copy progress Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: x86-64 OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE4 Workspace AssignedTo: kde-maintainers(a)suse.de ReportedBy: asv(a)lumo.de QAContact: qa-bugs(a)suse.de Found By: --- Blocker: No Created an attachment (id=540409) --> (http://bugzilla.novell.com/attachment.cgi?id=540409) Problems are marked with red Some words are not translated in Russian: - files - dirs (s. attachment) -- 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 820983] New: No translation on unlock screen
by bugzilla_noreply＠novell.com 14 Jul '13

14 Jul '13

https://bugzilla.novell.com/show_bug.cgi?id=820983 https://bugzilla.novell.com/show_bug.cgi?id=820983#c0 Summary: No translation on unlock screen Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: x86-64 OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: KDE4 Workspace AssignedTo: kde-maintainers(a)suse.de ReportedBy: asv(a)lumo.de QAContact: qa-bugs(a)suse.de Found By: --- Blocker: No Created an attachment (id=540407) --> (http://bugzilla.novell.com/attachment.cgi?id=540407) Problems are marked with red Translations for buttons are not available (tested in German and Russian versions): - Switch users - Unlock -- 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