March 2013 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 774406] New: rpmlint complains about correct license spelling
by bugzilla_noreply＠novell.com 14 Mar '13

14 Mar '13

https://bugzilla.novell.com/show_bug.cgi?id=774406 https://bugzilla.novell.com/show_bug.cgi?id=774406#c0 Summary: rpmlint complains about correct license spelling Classification: Internal Novell Products Product: openSUSE Build Service Version: master Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: General AssignedTo: coolo(a)suse.com ReportedBy: jw(a)suse.com QAContact: adrian(a)suse.com CC: froh(a)suse.com Found By: --- Blocker: --- With home:jnweiger:LinuxCNC/cgal I get the following bogus warning when the build is finished: libcgal8.src: W: invalid-license QPL-1.0; LGPL-2.1; LGPL-2.1+ The specified license string is not recognized. Please refer to http://license.opensuse.org/ for the list of known licences and their exact spelling. The three names are correct, according to the table linked at the top of http://license.opensuse.org/ I assume, that the complaint is about the 'semicolon'. Neither the table nor the website has any information what operator should be used for aggregate. Please let me know, and I will update license.opensuse.org with a list of acceptable operators. I was not aware that this warning is important, but today sr#129834 was declined because of this warning. -- 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 808557] New: Automatic screen lock after a period of inactivity - unlocks with password
by bugzilla_noreply＠novell.com 14 Mar '13

14 Mar '13

https://bugzilla.novell.com/show_bug.cgi?id=808557 https://bugzilla.novell.com/show_bug.cgi?id=808557#c0 Summary: Automatic screen lock after a period of inactivity - unlocks with password Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: i686 OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: michalng(a)gmail.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 openSUSE 12.3 KDE4 desktop will provides a screen lock function after a certain period of no activity (e.g. user is away from computer). Wwhen user is back (e.g. after 30 minutes), the screen shows the "screen-lock" gui. However, the user just needs to touch any key or touchpad (without entering the password) and the "screen-lock" will be disable. To confirm that the "screen-lock" function is working properly, "screen-lock" is manually activate using ctrl-alt-l (KDE4). "screen-lock" requires password before allowing access. Reproducible: Always Steps to Reproduce: 1. Login into desktop 2. Leave the destop alone for an external period (e.g. 15 minutes) 3. "screen-lock" automatically activated 4. Touch any keys or touchpad and allowed access. Actual Results: "screen-lock" allows access without entering password Expected Results: "screen-lock" allows access only after entering password -- 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 807667] New: Package version currently in Factory is very outdated
by bugzilla_noreply＠novell.com 14 Mar '13

14 Mar '13

https://bugzilla.novell.com/show_bug.cgi?id=807667 https://bugzilla.novell.com/show_bug.cgi?id=807667#c0 Summary: Package version currently in Factory is very outdated Classification: openSUSE Product: openSUSE.org Version: unspecified Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Software Portal AssignedTo: benji(a)opensuse.org ReportedBy: EagleScreen(a)gmail.com QAContact: opensuse-communityscreening(a)forge.provo.novell.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Ubuntu; Linux i686; rv:19.0) Gecko/20100101 Firefox/19.0 Hello, from this Portal Factory site: http://en.opensuse.org/Portal:Factory We can access to a page that shows the package versions currently in Factory. This is the page: http://en.opensuse.org/openSUSE:Factory_versions As you can easily see, the package versions showed there are not the current versions in Factory, the page is very very outdated. Some script which used to do the work for auto-updating the page in the past, might be failing now. Reproducible: Always Steps to Reproduce: 1. Visit http://en.opensuse.org/openSUSE:Factory_versions 2. Pay attention at the package versions there. 3. Check it against current Factory versions and you will see that versions are very outdated. Actual Results: Package versions are very outdated. Expected Results: Package versions should be automatically updated regularly as it used to happen some time ago. -- 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 807609] New: CD-ROM Access Library "libcdio.so.13" missing when installing libxine2-codecs 1.2.2-80.3
by bugzilla_noreply＠novell.com 14 Mar '13

14 Mar '13

https://bugzilla.novell.com/show_bug.cgi?id=807609 https://bugzilla.novell.com/show_bug.cgi?id=807609#c0 Summary: CD-ROM Access Library "libcdio.so.13" missing when installing libxine2-codecs 1.2.2-80.3 Classification: openSUSE Product: openSUSE 12.3 Version: RC 2 Platform: x86-64 OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: rb03884(a)gmail.com QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created an attachment (id=528273) --> (http://bugzilla.novell.com/attachment.cgi?id=528273) conflict message User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:19.0) Gecko/20100101 Firefox/19.0 Installing libxine2-codecs from Pckman Factory on openSUSE 12.3 RC2 When selecting libxine2-codecs for installation a message prompts the user for libcdio.so.13 or libcdio13. However openSUSE 12.2 RC2 only provides libcdio.so.14 or libcdio14. Reproducible: Always Steps to Reproduce: 1. Start Yast Software Management 2. Select libxine2-codecs 3. Prompted by nothing provides libcdio.so.13()(64bit) needed by libxine2-codecs-1.2.2-80.3.x86_64 Actual Results: nothing provides libcdio.so.13()needed by libxine2-codecs 1.2.2-80.3.x86_64 Expected Results: Use libcdio.so.14 for libxine2-codecs for installation -- 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 766408] New: Drop RUN+="socket:..." from multipath.rule
by bugzilla_noreply＠novell.com 14 Mar '13

14 Mar '13

https://bugzilla.novell.com/show_bug.cgi?id=766408 https://bugzilla.novell.com/show_bug.cgi?id=766408#c0 Summary: Drop RUN+="socket:..." from multipath.rule Classification: openSUSE Product: openSUSE 12.2 Version: Beta 1 Platform: All OS/Version: openSUSE 12.2 Status: NEW Severity: Major Priority: P5 - None Component: Hotplug AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: rmilasan(a)suse.com QAContact: qa-bugs(a)suse.de Found By: L3 Blocker: --- Created an attachment (id=494321) --> (http://bugzilla.novell.com/attachment.cgi?id=494321) 0001-multipath.rules.patch We need to drop the RUN+="socket:..." from the multipath rule as is been dropped by udev. In the attachment is a "possible" version of the fix for this issue. -- 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 794496] New: Attached USB HID device is created with unsufficient permissions
by bugzilla_noreply＠novell.com 14 Mar '13

14 Mar '13

https://bugzilla.novell.com/show_bug.cgi?id=794496 https://bugzilla.novell.com/show_bug.cgi?id=794496#c0 Summary: Attached USB HID device is created with unsufficient permissions Classification: openSUSE Product: openSUSE 12.2 Version: Final Platform: x86-64 OS/Version: openSUSE 12.2 Status: NEW Severity: Normal Priority: P5 - None Component: Hotplug AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: cyberbeat(a)gmx.de QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.13 (KHTML, like Gecko) Chrome/24.0.1290.0 Safari/537.13 SUSE/24.0.1290.0 When I attach the usb hid device "ID 2133:0001" (a digital sign-pad) it is created with permissions "crw-rw-r-- 1 root root 189, 693 14. Dez 10:24 /dev/bus/usb/006/054" I have to chmod o+w /dev/bus/usb/006/054 to use it as a user. 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 12

[Bug 787664] New: systemd: stuck login prompt
by bugzilla_noreply＠novell.com 14 Mar '13

14 Mar '13

https://bugzilla.novell.com/show_bug.cgi?id=787664 https://bugzilla.novell.com/show_bug.cgi?id=787664#c0 Summary: systemd: stuck login prompt Classification: openSUSE Product: openSUSE Factory Version: 12.3 Milestone 0 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: fcrozat(a)suse.com ReportedBy: jslaby(a)suse.com QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- Every time I boot my system, for the first time, the login password prompt is stuck on the serial console. I am able to enter login, it is printed twice, but password query does not respond to my typing (enter does nothing). It's like: linux-u8yo login: root root Password: <stuck> Then it writes "login: timed out after 60 seconds" and I'm able to log in normally. The cure is also to press enter with blanc name to start a new login prompt. It looks like getty is started twice on ttyS0? # cat /proc/cmdline BOOT_IMAGE=/boot/vmlinuz-3.6.5-1-desktop root=UUID=2a083c62-4eca-44f4-b3f9-61cc420b9887 video=1024x768 console=tty0 console=ttyS0,115200 splash=silent quiet showopts # ll /etc/systemd/system/getty.target.wants/ total 0 lrwxrwxrwx 1 root root 34 Aug 24 21:48 getty(a)tty1.service -> /lib/systemd/system/getty@.service lrwxrwxrwx 1 root root 41 Sep 12 20:53 serial-getty(a)ttyS0.service -> /lib/systemd/system/serial-getty@.service -- 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 13

[Bug 809308] New: osc: emits a "bad request" message
by bugzilla_noreply＠novell.com 14 Mar '13

14 Mar '13

https://bugzilla.novell.com/show_bug.cgi?id=809308 https://bugzilla.novell.com/show_bug.cgi?id=809308#c0 Summary: osc: emits a "bad request" message Classification: openSUSE Product: openSUSE 12.2 Version: Final Platform: All OS/Version: Linux Status: NEW Severity: Normal Priority: P5 - None Component: Development AssignedTo: adrian(a)suse.com ReportedBy: jengelh(a)inai.de QAContact: qa-bugs(a)suse.de Found By: Beta-Customer Blocker: --- The obs server has returned an unexpected 400 error, while still completing the request. 09:28 ares07:~ > osc request accept 159278 --message="reviewed ok." Result of change request state: <?xml version="1.0"?> <status code="ok"> <summary>Ok</summary> <details></details> </status> This package instance is defined as devel are in openSUSE:Factory Forward this submit to it? ([y]/n) license update: LGPL-3.0+ and GPL-2.0+ examples are under GPL-2.0Ã+ (forwarded request 159278 from babelworx) Server returned an error: HTTP Error 400: Bad Request Failed parsing the request xml 09:28 ares07:~ > osc request accept 159278 --message="reviewed ok." *** The state of the request (#159278) is already 'accepted'. Change state anyway? [y/n] *** ^Cinterrupted! 09:28 ares07:~ > rpm -q osc osc-0.139.1-1.9.1.noarch -- 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 808607] New: XV does not build anymore due licence digger detecting invalid-license
by bugzilla_noreply＠novell.com 14 Mar '13

14 Mar '13

https://bugzilla.novell.com/show_bug.cgi?id=808607 https://bugzilla.novell.com/show_bug.cgi?id=808607#c0 Summary: XV does not build anymore due licence digger detecting invalid-license Classification: openSUSE Product: openSUSE Factory Version: 13.1 Milestone 0 Platform: All OS/Version: SUSE Other Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: dmueller(a)suse.com ReportedBy: werner(a)suse.com QAContact: qa-bugs(a)suse.de CC: cfarrell(a)suse.com Found By: Development Blocker: --- Current build of XV part of projects multimedia:apps and openSUSE:Factory:NonFree does not build due [ 156s] xv.x86_64: E: invalid-license (Badness: 100000) Beerware, Cardware, Shareware [ 156s] xv.x86_64: E: invalid-license (Badness: 100000) not restricted [ 156s] xv.src: E: invalid-license (Badness: 100000) Beerware, Cardware, Shareware [ 156s] xv.src: E: invalid-license (Badness: 100000) not restricted [ 156s] The specified license string is not recognized. Please refer to [ 156s] http://license.opensuse.org/ for the list of known licences and their exact [ 156s] spelling. it should ber noted that XV is already part of openSUSE:Factory:NonFree. Therefore I'd like to know why this had happen? -- 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 808108] New: Enable Secure Boot is not enabled by default when in secure boot mode
by bugzilla_noreply＠novell.com 14 Mar '13

14 Mar '13

https://bugzilla.novell.com/show_bug.cgi?id=808108 https://bugzilla.novell.com/show_bug.cgi?id=808108#c0 Summary: Enable Secure Boot is not enabled by default when in secure boot mode Classification: openSUSE Product: openSUSE 12.3 Version: RC 2 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Release Notes AssignedTo: ke(a)suse.com ReportedBy: lnussel(a)suse.com QAContact: coolo(a)suse.com CC: aplanas(a)novell.com Found By: --- Blocker: --- +++ This bug was initially created as a clone of Bug #807839 +++ This only affects machines in UEFI mode with secure boot enabled. YaST does not automatically detect if the machine has secure boot enabled and will therefore install an unsigned bootloader by default which will not be accepted by the firmware. To have a signed bootloader installed the option "Enable Secure" boot has to be manually checked. -- 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