August 2014 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 889147] New: git-review -s problem on non-english locale
by bugzilla_noreply＠novell.com 28 Aug '14

28 Aug '14

https://bugzilla.novell.com/show_bug.cgi?id=889147 https://bugzilla.novell.com/show_bug.cgi?id=889147#c0 Summary: git-review -s problem on non-english locale Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: All OS/Version: openSUSE 12.3 Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: bwiedemann(a)suse.com ReportedBy: bwiedemann(a)suse.com QAContact: qa-bugs(a)suse.de CC: maintenance(a)opensuse.org Found By: Development Blocker: --- git-review -s is parsing git output, which fails in non-english locales such as LANG=de_DE.utf8 in a way that is not easy to diagnose. This is fixed in git-review-1.24 as found in the devel:languages:python repo Because this bug can be quite frustrating I'd like to do a maintenance-update for 12.3 and 13.1 and might need some help with the setup, because 12.3 is still using the python-git-review package name -- 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 892123] New: octave requires latex at runtime
by bugzilla_noreply＠novell.com 28 Aug '14

28 Aug '14

https://bugzilla.novell.com/show_bug.cgi?id=892123 https://bugzilla.novell.com/show_bug.cgi?id=892123#c0 Summary: octave requires latex at runtime Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: dmitry(a)roshchin.org QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Firefox/31.0 Octave requires makeinfo for parsing help files. But octave package requires texinfo package instead of makeinfo. Texinfo requires makeinfo, so everything works fine, but texinfo requires not needed latex packages. 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 4

[Bug 893972] New: GNOME applet to unmount disk does not provide unique identifiers for filesystem
by bugzilla_noreply＠novell.com 28 Aug '14

28 Aug '14

https://bugzilla.novell.com/show_bug.cgi?id=893972 https://bugzilla.novell.com/show_bug.cgi?id=893972#c0 Summary: GNOME applet to unmount disk does not provide unique identifiers for filesystem Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: All OS/Version: openSUSE 12.3 Status: NEW Severity: Normal Priority: P5 - None Component: GNOME AssignedTo: bnc-team-gnome(a)forge.provo.novell.com ReportedBy: Ulrich.Windl(a)rz.uni-regensburg.de QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created an attachment (id=604012) --> (http://bugzilla.novell.com/attachment.cgi?id=604012) Screenshot of lower right corner of the screen (GNOME applet) User-Agent: Mozilla/5.0 (X11; Linux i686; rv:31.0) Gecko/20100101 Firefox/31.0 I plugged in two memory sticks to USB, both having the volume label "VOLUME" (Microsoft default). In Linux these filesystems were mounted as /run/media/user/VOLUME (/dev/sdc1) and /run/media/user/VOLUME1 (dev/sdd1) So a unique identifier was assigned (even though it's not the best possible solution: Who remembers what stick was inserted first?) Reproducible: Didn't try Steps to Reproduce: 1. See "Details" 2. Try to unmount a specific device using the GNOME applet (see attachment with screen shot if it's not clear what I'm talking about) Actual Results: The applet displays "VOLUME" twice and it's not obvious who's who (see screen shot). Expected Results: At least the labels displayed in the applet should match those of the mount points. In Windows 7, the applet to remove a disk shows the vendor of the device which is quite helpful is most cases (I'll provide a screen shot with the same devices later). -- 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 886855] New: Dependency on python3-setuptools is missing in python3-pytest
by bugzilla_noreply＠novell.com 28 Aug '14

28 Aug '14

https://bugzilla.novell.com/show_bug.cgi?id=886855 https://bugzilla.novell.com/show_bug.cgi?id=886855#c0 Summary: Dependency on python3-setuptools is missing in python3-pytest Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: All OS/Version: openSUSE 13.1 Status: NEW Severity: Normal Priority: P5 - None Component: Development AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: rolf(a)rotkraut.de QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:30.0) Gecko/20100101 Firefox/30.0 python3-pytest installs the Python script /usr/bin/py.test-3.3. This script imports pkg_resources, a module which is provided by python3-setuptools. But python3-pytest fails to require python3-setuptools. Reproducible: Always Steps to Reproduce: 1. Do not have python3-setuptools installed. 2. Install python3-pytest using zypper, note that python3-setuptools does *not* get installed as a dependency. 3. py.test-3.3 Actual Results: py.test-3.3 throws the Error: Traceback (most recent call last): File "/usr/bin/py.test-3.3", line 5, in <module> from pkg_resources import load_entry_point ImportError: No module named 'pkg_resources' Expected Results: py.test-3.3 should run without error. After installing python3-setuptools, the error is fixed. -- 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 799559] New: unexplainable messages from floppy driver, possibly after suspend to RAM
by bugzilla_noreply＠novell.com 28 Aug '14

28 Aug '14

https://bugzilla.novell.com/show_bug.cgi?id=799559 https://bugzilla.novell.com/show_bug.cgi?id=799559#c0 Summary: unexplainable messages from floppy driver, possibly after suspend to RAM Classification: openSUSE Product: openSUSE 12.2 Version: Final Platform: i686 OS/Version: openSUSE 12.2 Status: NEW Severity: Normal Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers(a)forge.provo.novell.com ReportedBy: Ulrich.Windl(a)rz.uni-regensburg.de QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux i686; rv:18.0) Gecko/20100101 Firefox/18.0 After resume from suspend to RAm I see many kernel messages about the floppy controller flooding the syslog. One of these sequences looks like this: Jan 21 08:14:09 host kernel: [72861.352011] Jan 21 08:14:09 host kernel: [72861.352016] floppy driver state Jan 21 08:14:09 host kernel: [72861.352019] ------------------- Jan 21 08:14:09 host kernel: [72861.352048] now=18140338 last interrupt=4294927471 diff=18180163 last called handler=seek_interrupt Jan 21 08:14:09 host kernel: [72861.352052] timeout_message=redo fd request Jan 21 08:14:09 host kernel: [72861.352054] last output bytes: Jan 21 08:14:09 host kernel: [72861.352057] 13 90 4294927440 Jan 21 08:14:09 host kernel: [72861.352059] 0 90 4294927440 Jan 21 08:14:09 host kernel: [72861.352062] 1a 90 4294927440 Jan 21 08:14:09 host kernel: [72861.352064] 0 90 4294927440 Jan 21 08:14:09 host kernel: [72861.352067] 3 80 4294927440 Jan 21 08:14:09 host kernel: [72861.352069] c1 90 4294927440 Jan 21 08:14:09 host kernel: [72861.352072] 10 90 4294927440 Jan 21 08:14:09 host kernel: [72861.352074] 7 80 4294927440 Jan 21 08:14:09 host kernel: [72861.352076] 0 90 4294927440 Jan 21 08:14:09 host kernel: [72861.352079] 8 81 4294927440 Jan 21 08:14:09 host kernel: [72861.352081] f 80 4294927440 Jan 21 08:14:09 host kernel: [72861.352084] 0 90 4294927440 Jan 21 08:14:09 host kernel: [72861.352086] 1 90 4294927440 Jan 21 08:14:09 host kernel: [72861.352088] 8 81 4294927441 Jan 21 08:14:09 host kernel: [72861.352091] 4 80 4294927470 Jan 21 08:14:09 host kernel: [72861.352093] 0 90 4294927470 Jan 21 08:14:09 host kernel: [72861.352096] f 80 4294927470 Jan 21 08:14:09 host kernel: [72861.352098] 0 90 4294927470 Jan 21 08:14:09 host kernel: [72861.352100] 0 90 4294927470 Jan 21 08:14:09 host kernel: [72861.352103] 8 81 4294927471 Jan 21 08:14:09 host kernel: [72861.352105] last result at 4294927471 Jan 21 08:14:09 host kernel: [72861.352107] last redo_fd_request at 18139586 Jan 21 08:14:09 host kernel: [72861.352111] 20 00 . Jan 21 08:14:09 host kernel: [72861.352121] status=ff Jan 21 08:14:09 host kernel: [72861.352123] fdc_busy=1 Jan 21 08:14:09 host kernel: [72861.352131] do_floppy=reset_interrupt Jan 21 08:14:09 host kernel: [72861.352133] cont=f825a09c Jan 21 08:14:09 host kernel: [72861.352135] current_req=f6a566b8 Jan 21 08:14:09 host kernel: [72861.352138] command_status=-1 Jan 21 08:14:09 host kernel: [72861.352140] Jan 21 08:14:09 host kernel: [72861.352143] floppy0: floppy timeout called Jan 21 08:14:09 host kernel: [72861.352150] end_request: I/O error, dev fd0, sector 0 Jan 21 08:14:09 host kernel: [72861.352157] Buffer I/O error on device fd0, logical block 0 # xzcat /var/log/messages-20130121.xz | grep "floppy driver state" | wc -l 295 Reproducible: Always Steps to Reproduce: 1. On a PC with a floppy drive, suspend to RAM, wait some time, then resume Actual Results: Kernel messages about the floppy controller Expected Results: No kernel messages, unless there is a real problem with the floppy controller. # hwinfo --floppy 02: Floppy 00.0: 10603 Floppy Disk [Created at floppy.120] Unique ID: sPPV.oZ89vuho4Y3 Parent ID: rdCR.3wRL2_g4d2B Hardware Class: floppy Model: "Floppy Disk" Device File: /dev/fd0 Size: 3.5 '' Size: 2880 sectors a 512 bytes Capacity: 0 GB (1474560 bytes) Drive status: no medium Config Status: cfg=yes, avail=yes, need=no, active=unknown Attached to: #1 (Floppy disk controller) On boot the kernel said: Jan 14 08:03:59 host kernel: [ 30.457523] FDC 0 is a post-1991 82077 -- 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 11

[Bug 892303] New: 'yast2 keyboard' doesn't change the X11 keyboard
by bugzilla_noreply＠novell.com 28 Aug '14

28 Aug '14

https://bugzilla.novell.com/show_bug.cgi?id=892303 https://bugzilla.novell.com/show_bug.cgi?id=892303#c0 Summary: 'yast2 keyboard' doesn't change the X11 keyboard Classification: openSUSE Product: openSUSE Factory Version: 201407* Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: yast2-maintainers(a)suse.de ReportedBy: asn(a)cryptomilk.org QAContact: jsrain(a)suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Firefox/31.0 I've installed openSUSE Factory last week. I wondered why the keyboard is changed back after ~1h to English if I choose German as the keyboard layout. Today I found out that the reason is systemd. After running localectl set-x11-keymap de it started to work as expected. Why doesn't the YaST2 keyboard module call localectl? 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 7

[Bug 893270] New: Yast AppApprmor - Removal of Functional Aspect to Create an AppArmor Profile by Self Learning an Application Execution
by bugzilla_noreply＠novell.com 28 Aug '14

28 Aug '14

https://bugzilla.novell.com/show_bug.cgi?id=893270 https://bugzilla.novell.com/show_bug.cgi?id=893270#c0 Summary: Yast AppApprmor - Removal of Functional Aspect to Create an AppArmor Profile by Self Learning an Application Execution Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: x86-64 OS/Version: openSUSE 13.1 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:31.0) Gecko/20100101 Firefox/31.0 The ability for Apparmor to create a profile by self leaning the use of an application has been removed. AppArmor's functional aspects get removed 1 after another. The ability to create an email notification has gone in 12.3 but the creation of a Mail Server to facilitate email notification is Yast works perfectly well. I'm not sure what taught at Uni now but for an application to have its functionality removed rather than corrected or fixed was known as not the way to develop software. If an aspect or API in this case doesn't work we just dont get rid of it or are there other reasons I'm not aware of please. Is AppArmor no longer a Major System Benefit the on the Side of our Boxes of software? Reproducible: Always Steps to Reproduce: 1. 2. 3. Actual Results: Removal of Functionality Expected Results: Correction and Enhancement of functionality -- 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 893901] New: Software 1-click install's Content-Type: is text/x-suse-ymp, but should be application/octet-stream. So some browser (eg. Google Chrome) can not download .ymp files.
by bugzilla_noreply＠novell.com 27 Aug '14

27 Aug '14

https://bugzilla.novell.com/show_bug.cgi?id=893901 https://bugzilla.novell.com/show_bug.cgi?id=893901#c0 Summary: Software 1-click install's Content-Type: is text/x-suse-ymp, but should be application/octet-stream. So some browser (eg. Google Chrome) can not download .ymp files. Classification: openSUSE Product: openSUSE.org Version: unspecified Platform: All OS/Version: SUSE Other Status: NEW Severity: Normal Priority: P5 - None Component: Software Portal AssignedTo: benji(a)opensuse.org ReportedBy: bkbin005(a)rinku.zaq.ne.jp QAContact: opensuse-communityscreening(a)forge.provo.novell.com Found By: --- Blocker: --- Created an attachment (id=603961) --> (http://bugzilla.novell.com/attachment.cgi?id=603961) Analized HTTP packets, please see Content-Type: in response header. User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/37.0.2062.94 Safari/537.36 1-click install's Content-Type: is text/x-suse-ymp, but should be application/octet-stream. So some browser (eg. Google Chrome) can not download .ymp files, but show as XML files. I reported bnc#836059. This issue was fixed in Chromium. But this issue should fix as a Web servers bug. Reproducible: Always Steps to Reproduce: 1. Open software.opensuse.org with Google Chrome. 2. Search "hello". 3. Select "1 click install" Actual Results: The browser shows http://software.opensuse.org/ymp/openSUSE:13.1/standard/hello.ymp as a XML file. Expected Results: The browser should download .ymp as a file. IANA media-types: http://www.iana.org/assignments/media-types/media-types.xhtml#application . Samples about customize Content-Type: http://qiita.com/horimislime/items/325848fcf1e3dc6bd53a https://www.drupal.org/node/2101017 -- 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 891267] New: Setting system keyboard layout in Yast2 but resets to English (US) after reboot
by bugzilla_noreply＠novell.com 27 Aug '14

27 Aug '14

https://bugzilla.novell.com/show_bug.cgi?id=891267 https://bugzilla.novell.com/show_bug.cgi?id=891267#c0 Summary: Setting system keyboard layout in Yast2 but resets to English (US) after reboot Classification: openSUSE Product: openSUSE Factory Version: 201408* Platform: All OS/Version: openSUSE 13.2 Status: NEW Severity: Major Priority: P5 - None Component: YaST2 AssignedTo: yast2-maintainers(a)suse.de ReportedBy: ianrosswilliams(a)gmail.com QAContact: jsrain(a)suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Firefox/31.0 I use and English (UK) keyboard layout. After a fresh update to Suse Factory (2014-08-11) my keyboard layout reverts to English (US). When I press <shift>+<2> I get an @ symbol rather than a ". I open Yast2 and go to System Keyboard Layout. I see that English (UK) is selected but when typing in the Test box I actually get an English (US) keyboard. If I then select any other language, test it out and then select English (UK) again, my keyboard layout is correct. If I then reboot the computer, the layout reverts to English (US) Reproducible: Always Steps to Reproduce: 1. Upgrade to OpenSuse Factory from 13.1 with English (UK) keyboard. 2. Log-in and see English (US) keyboard layout 3. Load Yast2->System Keyboard Layout 4. See that English (UK) is selected. 5. Select English (US) and then English (UK) again. 6. Reboot machine and see that the layout has reverted to English (US) Actual Results: Pressing <shift>+<2> generates @ symbol, or <shift>+<3> gives #, etc. Expected Results: Pressing <shift>+<2> should generate " symbol, or <shift>+<3> gives £, etc. This problem can prevent users from logging into their computers. I am lucky that my password did not have any effected characters in and that I am able to remember how the US keyboard layout differs from the UK. As such I've marked this as "Major". -- 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 892834] New: Ext4 support of RichACL is broken
by bugzilla_noreply＠novell.com 27 Aug '14

27 Aug '14

https://bugzilla.novell.com/show_bug.cgi?id=892834 https://bugzilla.novell.com/show_bug.cgi?id=892834#c0 Summary: Ext4 support of RichACL is broken Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: x86-64 OS/Version: openSUSE 13.1 Status: NEW Severity: Normal Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers(a)forge.provo.novell.com ReportedBy: novell(a)roblucke.com QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created an attachment (id=602982) --> (http://bugzilla.novell.com/attachment.cgi?id=602982) repaired /usr/src/linux/fs/ext4/richacl.c User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Firefox/31.0 I know this is experimental and alpha. I am investigating NFSv4, CIFS, and POSIX ACLs and wanted to test the richacl implementation in OpenSuSE 13.1. The kernel configuration is non-functional, although the code is present. The kernel configuration clause in /usr/src/linux/fs/ext4/Kconfig depends upon a non-existent variable: EXT4_FS_XATTR. Once the dependency clause is removed, the code can be configured properly. Building the code encounters an error with one of the macros in richacl.c handle = ext4_journal_start( inode, EXT4_DATA_TRANS_BLOCKS(inode->i_sb)); ext4_journal)start() requires three parameters. I have approximated a fix with: handle = ext4_journal_start( inode, EXT4_HT_XATTR, (EXT4_DATA_TRANS_BLOCKS(inode->i_sb) + 1)); This may or may not be correct. (-;]> The code now builds. There apparently is a change in the richacl.h definition of the ACE bits, however, so it is necessary to know which version of the richacl-tools is required to match the code in the /usr/src/fs/ext4 directory (without extracting every git commit and comparing). Is there a way to get the appropriate tools? I know where they are at github. It would be really nice to have this working for my study, but I understand "EXPERIMENTAL", and "ALPHA". Reproducible: Always Steps to Reproduce: 1.Try to enable richacls with menuconfig or xconfig 2.Fix configuration in Kconfig 3.Build code and get error 4.Fix code and build kernel 5.Get richacl-tools v1.0 and attempt to manipulate acls in FS mounted with "richacl" option -- 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