August 2014 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 884843] New: libimobiledevice does not support iOS 7 devices
by bugzilla_noreply＠novell.com 02 Aug '14

02 Aug '14

https://bugzilla.novell.com/show_bug.cgi?id=884843 https://bugzilla.novell.com/show_bug.cgi?id=884843#c0 Summary: libimobiledevice does not support iOS 7 devices Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: iPhone OS/Version: Apple iOS 7.x Status: NEW Severity: Normal Priority: P5 - None Component: Network 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/35.0.1916.153 Safari/537.36 libimobiledevice 1.1.5 in 13.1 and Factory does not support iOS 7 devices. There will be an endless connect, authenticate, disconnect loop. See: http://forums.opensuse.org/showthread.php/495540-Internet-through-iphone-us… An update to 1.1.6 should help. Reproducible: Always Steps to Reproduce: 1. Connect an iOS 7 device via USB 2. Tell the iOS 7 device to trust your computer Actual Results: The iOS 7 device disconnects after a few seconds Expected Results: The iOS 7 device stays connected until I pull the USB cord -- 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 883994] New: WARNING loop after inserting USB device - BOGUS urb flags.
by bugzilla_noreply＠novell.com 02 Aug '14

02 Aug '14

https://bugzilla.novell.com/show_bug.cgi?id=883994 https://bugzilla.novell.com/show_bug.cgi?id=883994#c0 Summary: WARNING loop after inserting USB device - BOGUS urb flags. 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: support(a)microtechniques.com QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created an attachment (id=595673) --> (http://bugzilla.novell.com/attachment.cgi?id=595673) kernel log User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20140610 Firefox/24.0 PaleMoon/24.6.2 The system went into an error loop repeatedly logging call trace information after I inserted a USB storage device. I have used the same device with previous kernels without any issues. WARNING: CPU: 1 PID: 2528 at /home/abuild/rpmbuild/BUILD/kernel-default-3.15.0/linux-3.15/drivers/usb/core/urb.c:476 usb_submit_urb.part.6+0x1d7/0x5b0 [usbcore]() usb 1-7: BOGUS urb flags, 1 --> 0 There were over 7,000,000 lines of messages before the system rebooted. log file attached 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 8

[Bug 890087] New: devel:languages:python3/python3-pycurl: import exceptions/mimetools in __init__.py
by bugzilla_noreply＠novell.com 02 Aug '14

02 Aug '14

https://bugzilla.novell.com/show_bug.cgi?id=890087 https://bugzilla.novell.com/show_bug.cgi?id=890087#c0 Summary: devel:languages:python3/python3-pycurl: import exceptions/mimetools in __init__.py Classification: openSUSE Product: openSUSE.org Version: unspecified Platform: All OS/Version: openSUSE 13.1 Status: NEW Severity: Critical Priority: P5 - None Component: 3rd party software AssignedTo: speilicke(a)suse.com ReportedBy: i(a)marguerite.su QAContact: opensuse-communityscreening(a)forge.provo.novell.com Found By: Community User Blocker: --- exceptions module has changed into a built-in module in Python3, But we still have it in __init__.py. So it builds successfully but users can't use it, will output: import curl File "/usr/lib64/python3.3/site-packages/curl/__init__.py", line 9, in <module> import os, sys, urllib.request, urllib.parse, urllib.error, exceptions, mimetools, pycurl ImportError: No module named 'exceptions' The same problem also applies to "mimetools" module. So a maintenance update to openSUSE 12.3 and openSUSE 13.1 is required to make python3-pycurl usable. Marguerite -- 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 855548] New: gfxboot Should bring back the penguins that appear in GRUB
by bugzilla_noreply＠novell.com 01 Aug '14

01 Aug '14

https://bugzilla.novell.com/show_bug.cgi?id=855548 https://bugzilla.novell.com/show_bug.cgi?id=855548#c0 Summary: gfxboot Should bring back the penguins that appear in GRUB Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: All OS/Version: openSUSE 13.2 Status: NEW Severity: Enhancement Priority: P5 - None Component: Bootloader AssignedTo: jsrain(a)suse.com ReportedBy: alanbortu(a)gmail.com QAContact: jsrain(a)suse.com Found By: --- Blocker: --- Created an attachment (id=571861) --> (http://bugzilla.novell.com/attachment.cgi?id=571861) Screenshot of the penguins during boot User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:15.0) Gecko/20120427 Firefox/15.0a1 After reading the thread on the opensuse help forums, I thought it would be a nice idea to propose bringing the penguins back. What I mean by this is that sometimes, in grub on special dates the boot loader graphics will change at a random boot to one that features a bunch of penguins wearing some Christmas hats and doing general penguin things. However, in grub2 this does not happen and it's always using the same (boring) graphic when it boots up. I know it might seem silly and worthless but I just thought it would be a nice thing to propose just for the sake of fun. Reproducible: Always Steps to Reproduce: 1. Power on system 2. Wait for grub2 to display its boot options 3. Display the penguin graphic instead of the default graphic The thread that started this: https://forums.opensuse.org/english/get-technical-help-here/install-boot-lo… The openFATE request page: https://features.opensuse.org/316767 If you still dont know what I am talking about please see the attached picture -- 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 881283] New: XEN Network totally killed from outside
by bugzilla_noreply＠novell.com 01 Aug '14

01 Aug '14

https://bugzilla.novell.com/show_bug.cgi?id=881283 https://bugzilla.novell.com/show_bug.cgi?id=881283#c0 Summary: XEN Network totally killed from outside Classification: openSUSE Product: openSUSE 12.2 Version: Final Platform: x86-64 OS/Version: openSUSE 12.2 Status: NEW Severity: Critical Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers(a)forge.provo.novell.com ReportedBy: rde3(a)ipw.net QAContact: qa-bugs(a)suse.de Found By: Community User Blocker: --- June 2014 On a HP DL385 G1 it happend, that the server did an Watchdog reboot, but complete Network was totally missed. Running yast and changing the servers name or any other less important varaible (to accept a change and write it back), saving the network - the network IP and XEN bridge was back and I could reboot the server again and get it running - up to the next chinese attack. RDE Networks Wiesbaden Germany Gert Redlich -- 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 878667] New: Screen rotation not working with Intel driver
by bugzilla_noreply＠novell.com 01 Aug '14

01 Aug '14

https://bugzilla.novell.com/show_bug.cgi?id=878667 https://bugzilla.novell.com/show_bug.cgi?id=878667#c0 Summary: Screen rotation not working with Intel driver Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: X.Org AssignedTo: bnc-team-xorg-bugs(a)forge.provo.novell.com ReportedBy: rschweikert(a)suse.com QAContact: xorg-maintainer-bugs(a)forge.provo.novell.com Found By: --- Blocker: --- I have a 3 monitor setup: 2 Dell: SR2320L (1920x1080) 1 Viewsonic: VA2226W (1680x1050) The 2 Dell monitors are connected to a Zotac GeForce GT630 based card and the Viewsonic monitor is connected to the DVI connector on the mother board driven by the Intel i7-4770. Rotation of the display connected to the mother board fails (Monitor 3, Viewsonic). I have the monitor rotated to get more vertical screen real estate, but the display is not playing along. When using: xrandr --output HDMI2 --right-of DVI-I-1 --rotate right Terminals on my other screens disappear and the display on the 3rd monitor is not affected, i.e. everything is still sideways. Using: xrandr --output HDMI2 --right-of DVI-I-1 --rotate left The background on the 3rd monitor is messed up and things are still sideways. And I get the following error: X Error of failed request: BadValue (integer parameter out of range for operation) Major opcode of failed request: 140 (RANDR) Minor opcode of failed request: 7 (RRSetScreenSize) Value in failed request: 0x0 Serial number of failed request: 61 Current serial number in output stream: 62 The display operates properly when using xrandr --output HDMI2 --right-of DVI-I-1 --rotate normal but then everything is displayed sideways as the monitor is set up on end. This makes it very difficult to work with ;) Thus this appears to be a bug in the Intel graphics driver. For the GeForce based card I am using nouveau diver and the i915 driver is loaded for the Intel integrated graphics: drm 313440 6 i915,nouveau,ttm,drm_kms_helper video 19507 3 asus_wmi,i915,nouveau All monitors are connected via DVI cable (the Zotac card provides 2 outputs), although the connection to the mother board is identified by "xrandr -q" as HDMI2. -- 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 17

[Bug 803590] New: Start remote desktop does not work (KDM)
by bugzilla_noreply＠novell.com 01 Aug '14

01 Aug '14

https://bugzilla.novell.com/show_bug.cgi?id=803590 https://bugzilla.novell.com/show_bug.cgi?id=803590#c0 Summary: Start remote desktop does not work (KDM) Classification: openSUSE Product: openSUSE Factory Version: 12.3 Beta 1 Platform: x86-64 OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: X.Org AssignedTo: bnc-team-xorg-bugs(a)forge.provo.novell.com ReportedBy: antcregoz(a)telefonica.net QAContact: xorg-maintainer-bugs(a)forge.provo.novell.com Found By: --- Blocker: --- Created an attachment (id=524536) --> (http://bugzilla.novell.com/attachment.cgi?id=524536) xdmcp menu User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:18.0) Gecko/20100101 Firefox/18.0 Start a remote desktop with XDMCP (Alt+R) does not work, can not enter the IP address of the destination host. Reproducible: Always Steps to Reproduce: 1.Power ON PC , Start PC ("no automatic login") 2.Alt+R (remote Desktop) 3.Write destination host IP 4.It does not work, you can not write anything Actual Results: It does not work, you can not write anything -- 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 797522] New: Jreen 1.1.0 has a bug that breaks proper XMPP auth in Tomahawk
by bugzilla_noreply＠novell.com 01 Aug '14

01 Aug '14

https://bugzilla.novell.com/show_bug.cgi?id=797522 https://bugzilla.novell.com/show_bug.cgi?id=797522#c0 Summary: Jreen 1.1.0 has a bug that breaks proper XMPP auth in Tomahawk Classification: openSUSE Product: openSUSE 12.2 Version: Final Platform: Other OS/Version: openSUSE 12.2 Status: NEW Severity: Normal Priority: P5 - None Component: KDE4 Workspace AssignedTo: kde-maintainers(a)suse.de ReportedBy: dev(a)dominik-schmidt.de QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/17.0 Firefox/17.0 With Jreen 1.1.0 you need to restart Tomahawk after granting XMPP auth and you can get the auth popup several times. There is a new bugfix release 1.1.1 which fixes this issue. Reproducible: Always Steps to Reproduce: 1.Add a contact to your XMPP roster in Tomahawk Actual Results: Once the contact authorizes you, you get a popup asking for your permission to be added to his roster, then another one and another one and... A connection between two peers is only established after restarting. Expected Results: Tomahawk usually auto-acks the request of someone who has just been added to your own roster and allows users to immediately connect afterwards. -- 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 783725] New: Keyboard arrow keys don't work in kickoff menu
by bugzilla_noreply＠novell.com 01 Aug '14

01 Aug '14

https://bugzilla.novell.com/show_bug.cgi?id=783725 https://bugzilla.novell.com/show_bug.cgi?id=783725#c0 Summary: Keyboard arrow keys don't work in kickoff menu Classification: openSUSE Product: openSUSE 12.2 Version: Final Platform: x86-64 OS/Version: openSUSE 12.2 Status: NEW Severity: Minor Priority: P5 - None Component: KDE4 Workspace AssignedTo: kde-maintainers(a)suse.de ReportedBy: gav616(a)gmail.com QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:15.0) Gecko/20100101 Firefox/15.0.1 The keyboard arrow keys don't work in the kickoff menu after using it to search for an application. Reproducible: Always Steps to Reproduce: 1. Press ALt-F1 2. Type 'firefox' 3. Press the down arrow on keyboard Actual Results: The menu selector doesn't decent through the application list in one motion. This can be achieved however, but you have to press 'Esc' then use the arrow keys. Expected Results: Being able to use the keyboard exclusively to select and run application from the kickoff menu as fast as possible. -- 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 776522] New: remote login chooser crashes
by bugzilla_noreply＠novell.com 01 Aug '14

01 Aug '14

https://bugzilla.novell.com/show_bug.cgi?id=776522 https://bugzilla.novell.com/show_bug.cgi?id=776522#c0 Summary: remote login chooser crashes Classification: openSUSE Product: openSUSE 12.2 Version: RC 2 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE4 Workspace AssignedTo: kde-maintainers(a)suse.de ReportedBy: volker3204(a)paradise.net.nz QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/534.34 (KHTML, like Gecko) konqueror/4.7.2 Safari/534.34 Using kdm as login manager (or whatever is default when installing a KDE system). Getting a remote login via XDMCP crashes the chooser/greeter etc and doesn't do anything useful. Reproducible: Always Steps to Reproduce: 1. Start a new loginsesion (leave -> switch user -> new sesion). 2. Select Remote login. 3. Any input (mouse or keyboard) crashes the chooser, back to being able to select "remote login". Actual Results: The chooser/greeter crashes. Expected Results: See KDE 3. When selecting "remote login", a list of hosts shows up for XDMCP logins. Selecting one host opens a login screen on that host. I doubt it has ever worked on KDE 4. Unfortunately that reduces usability of openSUSE (or should that be KDE?) for multiple workstations and terminals on the LAN to low values. The problems seems to be well known: https://bugs.kde.org/show_bug.cgi?id=281862 https://bugzilla.novell.com/show_bug.cgi?id=715265 https://bugs.kde.org/show_bug.cgi?id=283919 https://bugs.launchpad.net/ubuntu/+source/kde-workspace/+bug/872761 Nothing is fixed in 12.1, and it doesn't work any better/different in 12.2.RC2. I am so far not aware of any functional workaround. Tested with 12.2RC2 in virtualbox. -- 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