March 2011 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 456622] [AI GNOME]: captain_magnus to build an upstream version of openSUSE/GNOME in SUSE studio
by bugzilla_noreply＠novell.com 09 Mar '11

09 Mar '11

https://bugzilla.novell.com/show_bug.cgi?id=456622 https://bugzilla.novell.com/show_bug.cgi?id=456622#c4 Hendrik Vogelsang <hvogel(a)novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED CC| |hvogel(a)novell.com Resolution| |FIXED --- Comment #4 from Hendrik Vogelsang <hvogel(a)novell.com> 2011-03-09 18:59:51 UTC --- This is fixed with Fred's G3 DVD now i guess... -- 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 677236] Buffer overflow in fsck.vfat
by bugzilla_noreply＠novell.com 09 Mar '11

09 Mar '11

https://bugzilla.novell.com/show_bug.cgi?id=677236 https://bugzilla.novell.com/show_bug.cgi?id=677236#c8 Christian Boltz <suse-beta(a)cboltz.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|suse-beta(a)cboltz.de | --- Comment #8 from Christian Boltz <suse-beta(a)cboltz.de> 2011-03-09 18:54:50 CET --- (sorry for the delay, I was on several carnival parades with a big float the last 4 days...) (In reply to comment #7) > I have submitted dosfstools with proposed patch into Base:System devel > project. Christian, could you please test if it really fixes you problem? The package in Base:System is only built for Factory (and not yet built), therefore I linked it to home:cboltz to get a 11.4 package. Good news: fsck.vfat -f no longer crashes :-) (And if I add -r, it even repairs the filessytem ;-) Please release the fixed package as maintenance update. -- 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 661785] New: tumbleweed 2.6.36.2 ext4 bug scheduling while atomic
by bugzilla_noreply＠novell.com 09 Mar '11

09 Mar '11

https://bugzilla.novell.com/show_bug.cgi?id=661785 https://bugzilla.novell.com/show_bug.cgi?id=661785#c0 Summary: tumbleweed 2.6.36.2 ext4 bug scheduling while atomic Classification: openSUSE Product: openSUSE 11.3 Version: Final Platform: x86-64 OS/Version: openSUSE 11.3 Status: NEW Severity: Normal Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers(a)forge.provo.novell.com ReportedBy: nevion(a)gmail.com QAContact: qa(a)suse.de Found By: --- Blocker: --- Created an attachment (id=406550) --> (http://bugzilla.novell.com/attachment.cgi?id=406550) dmesg of bug when happening User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.13) Gecko/20101203 SUSE/3.6.13-0.2.1 Firefox/3.6.13 Apparently this is due to a regression introduced in 2.6.36 with discard / sb_issue_discard() being a synchronous call and and ext4_free_blocks() being called in an atomic no sleeping allowed context. I use discard on the mounts of the ssd I have and a cron script based trim solution seems unsavory. So what's the fix for 2.6.36 for now, if any, and what about 11.4? 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 7

[Bug 660804] New: kiwi: cannot create EFI/UEFI compatible images
by bugzilla_noreply＠novell.com 09 Mar '11

09 Mar '11

https://bugzilla.novell.com/show_bug.cgi?id=660804 https://bugzilla.novell.com/show_bug.cgi?id=660804#c0 Summary: kiwi: cannot create EFI/UEFI compatible images Classification: openSUSE Product: openSUSE.org Version: unspecified Platform: x86-64 OS/Version: SLES 11 Status: NEW Severity: Enhancement Priority: P5 - None Component: System Imaging AssignedTo: ms(a)novell.com ReportedBy: troy.stepan(a)unisys.com QAContact: adrian(a)novell.com Found By: Third Party Developer/Partner Blocker: --- Kiwi does not support creation of EFI compatible images. We are really excited to be using Kiwi because as of today we use AutoYast to create custom installation DVDs but need Kiwi to be able to create .raw disk image files. EFI compatible means to us: - creates a FAT16 partition as partition 1, configured to mount as /boot/efi - installs EFI compatible boot files in the FAT16 partition - installs and configures ELILO as the boot loader (or an EFI compatible version of grub) - installs an EFI-compatible El Torito boot record on the CD/DVD ISO (if creating this type of Kiwi image) As a bonus, it would be really great you could make images that work on either EFI or BIOS as we can do with AutoYaST and xorriso today. Cheers. -- 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 450256] System freezes during resume from disk
by bugzilla_noreply＠novell.com 09 Mar '11

09 Mar '11

https://bugzilla.novell.com/show_bug.cgi?id=450256 https://bugzilla.novell.com/show_bug.cgi?id=450256#c50 Christian Lepper <christian.lepper(a)gmx.net> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED InfoProvider|christian.lepper(a)gmx.net | --- Comment #50 from Christian Lepper <christian.lepper(a)gmx.net> 2011-03-09 13:57:42 UTC --- I gave a quick shot at this kernel, but it won't even boot. When I chose this kernel in the grub menu, after hitting enter the screen just goes blank - hard lock (even CAPSLOCK is not working anymore). But in trying, I found out that the latest Kernel from updates (2.6.34.7-0.7-desktop) doesn't need anymore the acpi_sleep=s4_nohwsig option but will hibernate just fine. So with regard to 11.3, please consider my remark as solved. -- 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 677884] New: susefirewall does not put eth0 to internal zone by default
by bugzilla_noreply＠novell.com 09 Mar '11

09 Mar '11

https://bugzilla.novell.com/show_bug.cgi?id=677884 https://bugzilla.novell.com/show_bug.cgi?id=677884#c0 Summary: susefirewall does not put eth0 to internal zone by default Classification: openSUSE Product: openSUSE 11.3 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: Security AssignedTo: security-team(a)suse.de ReportedBy: ensonic(a)sonicpulse.de QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux i686; de; rv:1.9.2.13) Gecko/20101203 SUSE/3.6.13-0.2.1 Firefox/3.6.13 I am behint a nat router, my eth0 is using a 192.168.x.x network address. As susefirewall is always enabled by default it should configure eth0 to the internal zone. Otherwise applications in the local network (also behind the nat router) won't work my default (and it is not visible to the user why). Reproducible: Always Steps to Reproduce: 1. use the similar network setup 2. use netcat to simulate e.g. udp trafic between two computer or the same computer Actual Results: when running netcat twice on the same machine, data gets echoed when running netcat on a different machine in the local network it fails Expected Results: also echo the data for machines in the local network, but not applying firewall filtering I classify this as critical as it is big usability issue for not technical minded people. There is no indication except /var/log/firewall that network trafiic is blocked and most people would not even look there as in this case it is totally unexpected. -- 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 425745] encrypted user home can be created when already exist
by bugzilla_noreply＠novell.com 09 Mar '11

09 Mar '11

https://bugzilla.novell.com/show_bug.cgi?id=425745 https://bugzilla.novell.com/show_bug.cgi?id=425745#c13 --- Comment #13 from Jiří Suchomel <jsuchome(a)novell.com> 2011-03-09 13:48:40 UTC --- OK, I finally got to this one. The problem is, that in that described scenario, data from pam_mount.xml are lost so YaST actually does not know which images are present and to which user they belong. And it is also true that during the new installation, img file is not lost, just new (empty) user directory is created. So I think acceptable solution is to fix this situation on next run of yast2-users (after the installation), when you would select 'use crypted directory' for that user and YaST would retake existing img file by selected user. -- 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 465128] Banshee consumes two CPUs out of four
by bugzilla_noreply＠novell.com 09 Mar '11

09 Mar '11

https://bugzilla.novell.com/show_bug.cgi?id=465128 https://bugzilla.novell.com/show_bug.cgi?id=465128#c13 Stefan Behlert <behlert(a)novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution| |FIXED AssignedTo|rf(a)novell.com |gburt(a)novell.com QAContact|rf(a)novell.com |coolo(a)novell.com --- Comment #13 from Stefan Behlert <behlert(a)novell.com> 2011-03-09 13:21:55 UTC --- see comment 8. -- 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 294127] track copy / paste ..
by bugzilla_noreply＠novell.com 09 Mar '11

09 Mar '11

https://bugzilla.novell.com/show_bug.cgi?id=294127 https://bugzilla.novell.com/show_bug.cgi?id=294127#c Stefan Behlert <behlert(a)novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|rf(a)novell.com |gburt(a)novell.com QAContact|rf(a)novell.com |coolo(a)novell.com -- 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 650932] New: perl XML::Parser (and in effect XML::Parser::Expat) does not return UTF-8 strings as expected.
by bugzilla_noreply＠novell.com 09 Mar '11

09 Mar '11

https://bugzilla.novell.com/show_bug.cgi?id=650932 https://bugzilla.novell.com/show_bug.cgi?id=650932#c0 Summary: perl XML::Parser (and in effect XML::Parser::Expat) does not return UTF-8 strings as expected. Classification: openSUSE Product: openSUSE 11.3 Version: Final Platform: x86-64 OS/Version: openSUSE 11.3 Status: NEW Severity: Critical Priority: P5 - None Component: Development AssignedTo: pth(a)novell.com ReportedBy: DOlsson(a)WEB.de QAContact: qa(a)suse.de Found By: --- Blocker: --- Created an attachment (id=398363) --> (http://bugzilla.novell.com/attachment.cgi?id=398363) Small Perl program using XML::Parser to illustrate the problem reported. User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.10) Gecko/20100914 SUSE/3.6.10-30.2 Firefox/3.6.10 When using the Perl module "XML::Parser" to parse a valid UTF-8 XML text containing e.g. German umlauts, these are *not* returned as UTF-8 characters, but as Latin-1 (ISO-8859-1) characters! Reproducible: Always Steps to Reproduce: Write a Perl program using the XML::Parser module -- see attachment for small test program to illustrate problem. Actual Results: The UTF-8 characters "öäüÖÄÜß" are returned as Latin-1 characters "��". Expected Results: Expected to get the actual characters from read input, i.e. "öäüÖÄÜß". Download attachment, make it executable and run it "./xmlParserBug". Requires the "perl-XML-Parser" package to be installed. -- 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