November 2013 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 843718] kiwi: missing patch: use kpartx sync mode to make sure devices are created
by bugzilla_noreply＠novell.com 05 Nov '13

05 Nov '13

https://bugzilla.novell.com/show_bug.cgi?id=843718 https://bugzilla.novell.com/show_bug.cgi?id=843718#c12 Michael Schröder <mls(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|adrian(a)suse.com | AssignedTo|mls(a)suse.com |ms(a)suse.com --- Comment #12 from Michael Schröder <mls(a)suse.com> 2013-11-05 16:33:36 UTC --- The log indicates that udevd is running. (It's automatically started when the udev package is installed). So it doesn't seem to be a bug in the build script. I have no clue why the device does not show up, please ask a udev expert. -- 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 809737] New: mount -oloop,sizelimit=nnnnnn ignores the sizelimit
by bugzilla_noreply＠novell.com 05 Nov '13

05 Nov '13

https://bugzilla.novell.com/show_bug.cgi?id=809737 https://bugzilla.novell.com/show_bug.cgi?id=809737#c0 Summary: mount -oloop,sizelimit=nnnnnn ignores the sizelimit Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: puzel(a)suse.com ReportedBy: jeffm(a)suse.com QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- I recently tried to mount an hfsplus file system from an image file with a partition table by using the loop offset and sizelimit options to specify the location of the file system. hfsplus stores some metadata at a set offset from the end of the partition, so it's sensitive to the device size reported by the kernel. It worked with this: # losetup -r -o 32k --sizelimit=102400000 <loopdev> <imagefile> # mount -r -t hfsplus <loopdev> <mountpoint> But failed with this: # mount -r -oloop,offset=32k,sizelimit=102400000 <imagefile> <mountpoint> # losetup -a /dev/loop0: [0089]:2 (<imagefile>), offset 32768, sizelimit 102400000 /dev/loop1: [0089]:2 (<imagefile>), offset 32768, sizelimit 102400000 /proc/partitions shows the correct number of blocks to match the sizelimit. But if I set a breakpoint in mount before the mount syscall, I could see: # blockdev --getsize64 /dev/loop[01] 102400000 102432768 Patch to follow. -- 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 12

[Bug 812511] New: tk menu go beyond screen edges
by bugzilla_noreply＠novell.com 05 Nov '13

05 Nov '13

https://bugzilla.novell.com/show_bug.cgi?id=812511 https://bugzilla.novell.com/show_bug.cgi?id=812511#c0 Summary: tk menu go beyond screen edges Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: i686 OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: X11 Applications AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: alien.www(a)gmx.com QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux i686; rv:19.0) Gecko/20100101 Firefox/19.0 in 12.3 my tkabber's context menu started to ignore screen edges, if invoked near. that's probably same bug: http://sourceforge.net/tracker/?func=detail&aid=3562426&group_id=12997&atid… Reproducible: Always Steps to Reproduce: 1. execute 'wish /usr/lib/tcl/tk8.5/demos/widget' 2. choose "Menus and cascades (sub-menus)" 3. place the box near screen edge and invoke some menus Actual Results: menu goes out of screen Expected Results: menu should remain within the screen -- 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 847790] New: Fails to boot after installation, kernel panic?
by bugzilla_noreply＠novell.com 05 Nov '13

05 Nov '13

https://bugzilla.novell.com/show_bug.cgi?id=847790 https://bugzilla.novell.com/show_bug.cgi?id=847790#c0 Summary: Fails to boot after installation, kernel panic? Classification: openSUSE Product: openSUSE 13.1 Version: RC 1 Platform: x86-64 OS/Version: SUSE Other Status: NEW Severity: Critical Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: hkaustin(a)luukku.com QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created an attachment (id=565117) --> (http://bugzilla.novell.com/attachment.cgi?id=565117) image of screen after failure User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 Installed openSUSE 13.1 RC1 on my other partition. Installation went fine but it hangs at middle of boot. Looks like kernel panic. Tried both ext4 and btfrs file systems, but they both fail to boot. Reproducible: Always Steps to Reproduce: 1. 2. 3. Actual Results: Computer freezes on middle of boot. Image of screen in attachment. boot.log file: http://pastebin.com/BWadaECS /u/58427341/opensuse_13-1-1.jpg Image of another installation attempt: https://dl.dropboxusercontent.com Live KDE -version. Verified md5 sums. Tried to install from usb-stick and dvd. I didn't install bootloader because I had grub2 already installed on my other partition. Boot succeeds on virtual machine. 12.3 installs and boots flawlessly. My hardware CPU: Dual core Intel Pentium CPU E6300 (-MCP-) Mobo: Intel D946GZIS version: AAD66165-302 Graphics: Advanced Micro Devices [AMD] nee ATI RV710 [Radeon HD 4550] Drives: SAMSUNG_HD502HI Network: Card: Intel PRO/100 VE Network Connection Audio: Intel NM10/ICH7 Family High Definition Audio Controller -- 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 8

[Bug 848564] New: openSUSE 13.1 RC2 Repositories are missing after update from RC1
by bugzilla_noreply＠novell.com 05 Nov '13

05 Nov '13

https://bugzilla.novell.com/show_bug.cgi?id=848564 https://bugzilla.novell.com/show_bug.cgi?id=848564#c0 Summary: openSUSE 13.1 RC2 Repositories are missing after update from RC1 Classification: openSUSE Product: openSUSE 13.1 Version: RC 2 Platform: x86-64 OS/Version: SUSE Other Status: NEW Severity: Major Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: thomas.e.schreiner(a)t-online.de QAContact: jsrain(a)suse.com Found By: --- Blocker: --- Created an attachment (id=565788) --> (http://bugzilla.novell.com/attachment.cgi?id=565788) screenshot of yast window "configured software repositories" User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 I've updated my OS 13.1 RC1 to RC2 and wanted to make the Update-Test. Test failed because there where no repositories, as you can see in the screen shot. Reproducible: Always Steps to Reproduce: 1.dd if=openSUSE-13.1-DVD-Build0084-x86_64.iso of=/dev/sdb bs=1M (sdb=USB stick) 2.boot from USB stick and make a update installation 3.start yast2 online_update Actual Results: the only software repositories available is the USB device. Expected Results: I got an error message -- 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 10

[Bug 809553] New: Service boot.localnet requires non-existent boot.rootfsck
by bugzilla_noreply＠novell.com 05 Nov '13

05 Nov '13

https://bugzilla.novell.com/show_bug.cgi?id=809553 https://bugzilla.novell.com/show_bug.cgi?id=809553#c0 Summary: Service boot.localnet requires non-existent boot.rootfsck Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: anixx(a)opensuse.org QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:19.0) Gecko/20100101 Firefox/19.0 Service boot.localnet, provided by aaa_base requires boot.rootfsck to start but the letter was dropped from 12.3 which leads to impossibility to start boot.localnet. 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 9

[Bug 846831] New: The openSUSE 13.1 RC1 install medium is not able to load the kernel when booted via UEFI
by bugzilla_noreply＠novell.com 05 Nov '13

05 Nov '13

https://bugzilla.novell.com/show_bug.cgi?id=846831 https://bugzilla.novell.com/show_bug.cgi?id=846831#c0 Summary: The openSUSE 13.1 RC1 install medium is not able to load the kernel when booted via UEFI Classification: openSUSE Product: openSUSE 13.1 Version: RC 1 Platform: x86-64 OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Bootloader AssignedTo: jsrain(a)suse.com ReportedBy: rguenther(a)suse.com QAContact: jsrain(a)suse.com Found By: Development Blocker: --- When not using the legacy boot option to boot the RC1 install DVD medium then, while grub starts just fine, the install system does not boot because grub cannot load the kernel. On the grub command-line the kernel file is clearly visible in the path it tries to load, so this seems to be a bug in grub? The system is an Intel DHSK3 software development platform (Haswell) with up-to-date firmware. -- 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 24

[Bug 747939] New: Documentation for AD doesn't say "do not use .local".
by bugzilla_noreply＠novell.com 05 Nov '13

05 Nov '13

https://bugzilla.novell.com/show_bug.cgi?id=747939 https://bugzilla.novell.com/show_bug.cgi?id=747939#c0 Summary: Documentation for AD doesn't say "do not use .local". Classification: openSUSE Product: openSUSE 12.1 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Documentation AssignedTo: ke(a)suse.com ReportedBy: carlos.e.r(a)opensuse.org QAContact: ke(a)suse.com Found By: --- Blocker: --- Chapter 5. Active Directory Support of openSUSE Security Guide doesn't say that joining the domain will not work if the domain is something.local because it collides with zeroconf. https://bugs.launchpad.net/ubuntu/+source/likewise-open/+bug/205236 Also, YaST could detect this situation and advise the 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 6

[Bug 848553] New: chromium crashes in icu_49::RegexMatcher::reset
by bugzilla_noreply＠novell.com 05 Nov '13

05 Nov '13

https://bugzilla.novell.com/show_bug.cgi?id=848553 https://bugzilla.novell.com/show_bug.cgi?id=848553#c0 Summary: chromium crashes in icu_49::RegexMatcher::reset Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: Other OS/Version: openSUSE 12.3 Status: NEW Severity: Critical Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: suse(a)bugs.jan.ritzerfeld.org QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/31.0.1650.26 Safari/537.36 SUSE/31.0.1650.26 network:chromium crashes in icu_49::RegexMatcher::reset when entering its settings because of an old bug in libicu49 shipped with oS 12.2 and 12.3: https://code.google.com/p/chromium/issues/detail?id=122499 http://bugs.icu-project.org/trac/ticket/9283 Updating icu to 49.1.2 fixes this. 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 6

[Bug 846218] New: Displaylink device not available for xrandr 1.4
by bugzilla_noreply＠novell.com 05 Nov '13

05 Nov '13

https://bugzilla.novell.com/show_bug.cgi?id=846218 https://bugzilla.novell.com/show_bug.cgi?id=846218#c0 Summary: Displaylink device not available for xrandr 1.4 Classification: openSUSE Product: openSUSE Factory Version: 13.1 Beta 1 Platform: x86-64 OS/Version: SUSE Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: oneukum(a)suse.com QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- By default the udlfb driver binds to the device. That's wrong. udl should be used, because udlfb doesn't implemt the modesetting ioctls. udlfb must be blacklisted. -- 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