December 2013 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 850341] New: python3-pip crashes because of urllib problem
by bugzilla_noreply＠novell.com 16 Dec '13

16 Dec '13

https://bugzilla.novell.com/show_bug.cgi?id=850341 https://bugzilla.novell.com/show_bug.cgi?id=850341#c0 Summary: python3-pip crashes because of urllib problem Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: x86-64 OS/Version: openSUSE 13.1 Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: spiollinux(a)alice-dsl.net QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:25.0) Gecko/20100101 Firefox/25.0 pip seems to have a problem with urllib. It gives the following traceback: Traceback (most recent call last): File "/usr/bin/pip", line 9, in <module> load_entry_point('pip==1.4', 'console_scripts', 'pip-3.3')() File "/usr/lib/python3.3/site-packages/pkg_resources.py", line 378, in load_entry_point return get_distribution(dist).load_entry_point(group, name) File "/usr/lib/python3.3/site-packages/pkg_resources.py", line 2566, in load_entry_point return ep.load() File "/usr/lib/python3.3/site-packages/pkg_resources.py", line 2260, in load entry = __import__(self.module_name, globals(),globals(), ['__name__']) File "/usr/lib/python3.3/site-packages/pip/__init__.py", line 11, in <module> from pip.vcs import git, mercurial, subversion, bazaar # noqa File "/usr/lib/python3.3/site-packages/pip/vcs/mercurial.py", line 9, in <module> from pip.download import path_to_url2 File "/usr/lib/python3.3/site-packages/pip/download.py", line 147, in <module> class VerifiedHTTPSHandler(urllib.request.HTTPSHandler): AttributeError: 'module' object has no attribute 'request' Reproducible: Always Steps to Reproduce: 1. install python3-pip 2. launch pip with ´pip´ or ´pip-3.3´ 3. enjoy traceback Actual Results: pip crashes, the traceback given above appears. Expected Results: pip should work and display a help I'm using a fully-updated openSUSE 13.1 RC2 with python 3.3.2-5.1.3 and python3-pip 1.4-3.1.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 853545] New: gi.pygtkcompat should be replaced with pygtkcompat
by bugzilla_noreply＠novell.com 16 Dec '13

16 Dec '13

https://bugzilla.novell.com/show_bug.cgi?id=853545 https://bugzilla.novell.com/show_bug.cgi?id=853545#c0 Summary: gi.pygtkcompat should be replaced with pygtkcompat Classification: openSUSE Product: openSUSE.org Version: unspecified Platform: All OS/Version: openSUSE 13.1 Status: NEW Severity: Normal 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: --- See this upstream issue: http://twistedmatrix.com/trac/ticket/6280 The gi.pygtkcompat module import has been deprecated in recent pygobject and should be replaced with plain import of pygtkcompat. Unfortunately, this recent pygobject combined with twisted's use of gi.pygtkcompat results in a crash. I'm not sure if the crash is caused by twisted, or pygobject, but appears to be memory corruption, so likely the latter. However, dealing with this deprecation warning does fix the crash problem as well. And unluckily we are using "recent pygobject"... So please apply this patch: http://twistedmatrix.com/trac/attachment/ticket/6280/lp1102685.diff to our python-Twisted in devel:languages:python, openSUSE:Factory and create an update stack for openSUSE 13.1 Thanks! 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 4

[Bug 846550] New: YaST2 Network - deleting alias not reflected
by bugzilla_noreply＠novell.com 16 Dec '13

16 Dec '13

https://bugzilla.novell.com/show_bug.cgi?id=846550 https://bugzilla.novell.com/show_bug.cgi?id=846550#c0 Summary: YaST2 Network - deleting alias not reflected Classification: openSUSE Product: openSUSE 13.1 Version: RC 1 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: mfilka(a)suse.com ReportedBy: mfilka(a)suse.com QAContact: jsrain(a)suse.com CC: aburgemeister(a)gmail.com, norbert.jurkeit(a)web.de, rh(a)eng-int.co.uk Depends on: 845534 Found By: Customer Blocker: --- +++ This bug was initially created as a clone of Bug #845534 +++ I am using IPv4 addresses. I had one existing,which I edited (changed label and address) and added another. Left YaST then confirmed changes with 'ip addr', and conncring from another host. I restarted YaST and "deleted" the additional addresses. Exited YaST, and 'ip addr' shows the additional addresses still present. In order to remove the unwanted addresses I used: # vi /etc/sysconfig/network/ifcfg-enp4s0 to delete the entries (enp4s0 is the target ethernet device) then: # systemctl restart network.service # ip addr -- 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 855521] New: Can not login to news.opensuse.org
by bugzilla_noreply＠novell.com 16 Dec '13

16 Dec '13

https://bugzilla.novell.com/show_bug.cgi?id=855521 https://bugzilla.novell.com/show_bug.cgi?id=855521#c0 Summary: Can not login to news.opensuse.org Classification: openSUSE Product: openSUSE.org Version: unspecified Platform: Other OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: Infrastructure AssignedTo: mrueckert(a)suse.com ReportedBy: egdfree(a)opensuse.org QAContact: lrupp(a)suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux i686; rv:25.0) Gecko/20100101 Firefox/25.0 Other resources authorization is successful (forums, bugzilla, wiki). Trying to clean the cookies did not help. Reproducible: Always Steps to Reproduce: 1. goto news.opensuse.org 2. click login in top 3. you do not have access Actual Results: You do not have access to the administration page. Error: Unauthorized Account User: MyLogin Email: MyLogin(a)email.org -- 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 855601] New: gnome desktop stops responding when screensaver is active
by bugzilla_noreply＠novell.com 16 Dec '13

16 Dec '13

https://bugzilla.novell.com/show_bug.cgi?id=855601 https://bugzilla.novell.com/show_bug.cgi?id=855601#c0 Summary: gnome desktop stops responding when screensaver is active Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: x86-64 OS/Version: Linux Status: NEW Severity: Major Priority: P5 - None Component: GNOME AssignedTo: bnc-team-gnome(a)forge.provo.novell.com ReportedBy: ohering(a)suse.com QAContact: qa-bugs(a)suse.de Found By: Outsourced Testing Blocker: --- Created an attachment (id=571917) --> (http://bugzilla.novell.com/attachment.cgi?id=571917) Xorg.0.log fresh 13.1 x86_64 with gnome desktop sometimes it happens that when the screensaver is active and I press space or any key to get the desktop back the whole session just stops responding. all whats displayed is the to-be-moved-up thing with time and date. the menu in the uppper right corner does not respond either. today I figured that switching to console 1 and back to 7 causes a blank screen with just the mouse pointer. so it appears that something is stuck. there are no errors logged in these files: /home/olaf/.xsession-errors-:0 /var/log/Xorg.0.log /var/log/messages I will attach the Xorg.0.log -- 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 852165] New: Firewall Setting during installation
by bugzilla_noreply＠novell.com 16 Dec '13

16 Dec '13

https://bugzilla.novell.com/show_bug.cgi?id=852165 https://bugzilla.novell.com/show_bug.cgi?id=852165#c0 Summary: Firewall Setting during installation Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: x86-64 OS/Version: openSUSE 13.1 Status: NEW Severity: Normal Priority: P5 - None Component: Installation AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: holgi(a)suse.com QAContact: jsrain(a)suse.com Found By: Component Test Blocker: --- In openSUSE 13.1 you get two times asked about your firewall setting. First option in the "Installation overview" (step 1 of installation) where you can enable/disable the firewall and open/close port for SSH. Second option is in step 2 (after reboot). I now recognized that the firewall is still enabled at the second option even I disabled firewall at the first option already. I think this is not as it should be and as it was with later openSUSE versions. Disabling firewall in "Installation overview" should result in a disabled pre-selection in stage 2. -- 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 855404] New: Nvidia driver shows only a white screen
by bugzilla_noreply＠novell.com 16 Dec '13

16 Dec '13

https://bugzilla.novell.com/show_bug.cgi?id=855404 https://bugzilla.novell.com/show_bug.cgi?id=855404#c0 Summary: Nvidia driver shows only a white screen Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: x86-64 OS/Version: openSUSE 13.1 Status: NEW Severity: Major Priority: P5 - None Component: X11 3rd Party Driver AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: rsalevsky(a)suse.com QAContact: sndirsch(a)suse.com CC: sndirsch(a)suse.com Found By: Development Blocker: --- After installing the nvidia driver on openSuse 13.1 the screen shows only a white screen. The xsession-errors log prints that the user has no access to /dev/nvidia0. A simple workaround is to add the user to the video group. -- 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 855511] New: on boot, screen brightness goes to 0 after splash screen
by bugzilla_noreply＠novell.com 16 Dec '13

16 Dec '13

https://bugzilla.novell.com/show_bug.cgi?id=855511 https://bugzilla.novell.com/show_bug.cgi?id=855511#c0 Summary: on boot, screen brightness goes to 0 after splash screen Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: x86-64 OS/Version: openSUSE 13.1 Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: ondra(a)cifka.com 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.63 Safari/537.36 On Lenovo IdeaPad G500, when starting the system, the animated splash screen (chameleon turning green) is shown; at some point during this animation, the screen backlight gets a bit dim and after a second or so, it goes out altogether. Then I have to turn the backlight up using the keyboard button so that I can see the login screen. I'm using GNOME, but don't know if this is GNOME related. Reproducible: Always Steps to Reproduce: 1. Boot the system and wait -- 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 827289] New: UEFI system 1st reboot during installation always goes to Windows8 and not to grub2
by bugzilla_noreply＠novell.com 16 Dec '13

16 Dec '13

https://bugzilla.novell.com/show_bug.cgi?id=827289 https://bugzilla.novell.com/show_bug.cgi?id=827289#c0 Summary: UEFI system 1st reboot during installation always goes to Windows8 and not to grub2 Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: x86-64 OS/Version: openSUSE 12.3 Status: NEW Severity: Enhancement Priority: P5 - None Component: Installation AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: lee_matheson(a)hotmail.com QAContact: jsrain(a)suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:21.0) Gecko/20100101 Firefox/21.0 During installation from an openSUSE-12.3 DVD install .iso (using a USB-3.0 memory stick in a USB-3.0 port) on a Toshiba Satellite Z930 (which had a UEFI enabled firmware) the 1st reboot of the SSD drive during installation always goes to Windows8 and not to grub2. This was true for both secure boot enabled and for secure boot disabled in the UEFI firmware. During install secure boot was selected and grub2-efi was also selected. In the end, the solution that worked was to boot to an openSUSE liveDVD and copy the contents of the EFI/opensuse to the EFI/boot and also to rename the 'shim.efi' to 'bootx64.efi' (replacing the existing bootx64.efi). After that, when rebooting to the SSD drive the installation then continued successfully. The PC has been running openSUSE-12.3 well since with secure boot enabled or disabled. Speculation: This is possibly due to a Toshiba quirk in their UEFI implementation (Toshiba firmware v.6.70) on this Toshiba Satellite Z930 ultrabook. Possibly consider an openSUSE enhancement with an option of a more user friendly way to do this bootx64.efi replacement with shim.efi (assuming that this is the appropriate work around and that no better method available). Reproducible: Always Steps to Reproduce: 1. Do a fresh install of openSUSE-12.3 with secure boot enabled (or disabled) on a Toshiba Satellite Z930 2. Proceed with 1st reboot after software install complete (but before installation configuration is complete). 3. Actual Results: After os s/w install during 1st reboot only Windows8 will boot. Expected Results: Installation via grub2 should continue and windows8 should NOT continue booting regardless. Obtained help on openSUSE forums to find the functional work around: https://forums.opensuse.org/english/get-technical-help-here/install-boot-lo… (problem starting at post#78). That's a long thread so I don't expect bug report users to read the thread ! In windows8 I tried (with admin permissions) sending the command: bcdedit /set {bootmgr} path \EFI\opensuse\shim.efi while that reported successful, the Toshiba still rebooted to Windows8 The Windows8 command: efibootmgr -v yielded: linux:/home/linux # efibootmgr -v BootCurrent: 0004 Timeout: 1 seconds BootOrder: 0006,0005,0003,0000,0004,0002,0001 Boot0000* HDD/SSD ACPI(a0341d0,0)PCI(1f,2)ATAPI(0,0,0) Boot0001* LAN2 ACPI(a0341d0,0)PCI(19,0)MAC(e8e0b773c368,0)IPv4(0.0.0.0:0<->0.0.0.0:0,0, 0 Boot0002* LAN1 ACPI(a0341d0,0)PCI(19,0)MAC(e8e0b773c368,0)030d3c000000000000000000000000000000000000000000000000000000000000000000000000000000004000000000000000000000000000000000 Boot0003* Windows Boot Manager HD(2,e1800,82000,34e17e3e-31c6-11e2-a4d9-e8e0b773c368)File(\EFI\Microsoft\Boot\bootmgfw.efi)WINDOWS.........x...B.C.D.O.B.J.E.C.T.=.{.9.d.e.a.8.6.2.c.-.5.c.d.d.-.4.e.7.0.-.a.c.c.1.-.f.3.2.b.3.4.4.d.4.7.9.5.}...9................ Boot0004* USB Memory ACPI(a0341d0,0)PCI(1d,0)USB(0,0) Boot0005* opensuse HD(2,e1800,82000,34e17e3e-31c6-11e2-a4d9-e8e0b773c368)File(\EFI\opensuse\grubx64.efi) Boot0006* opensuse-secureboot HD(2,e1800,82000,34e17e3e-31c6-11e2-a4d9-e8e0b773c368)File(\EFI\opensuse\shim.efi) which suggested all was well, but the Toshiba still would boot only to MS-Windows8. On the replacement of bootx64.efi with shim.efi appeared to work. I note everytime grub2 configuration is updated, I need to recopy 'shim.efi' over 'bootx64.efi' to have the grub2 update applied. -- 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 855467] New: Network sometimes shut down while bootign
by bugzilla_noreply＠novell.com 16 Dec '13

16 Dec '13

https://bugzilla.novell.com/show_bug.cgi?id=855467 https://bugzilla.novell.com/show_bug.cgi?id=855467#c0 Summary: Network sometimes shut down while bootign Classification: openSUSE Product: openSUSE Factory Version: 13.2 Milestone 0 Platform: Other OS/Version: openSUSE 13.2 Status: NEW Severity: Major Priority: P5 - None Component: Network AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: suse-beta(a)cboltz.de QAContact: qa-bugs(a)suse.de Found By: Beta-Customer Blocker: --- Created an attachment (id=571782) --> (http://bugzilla.novell.com/attachment.cgi?id=571782) /v/l/boot.log Factory, last updated 2013-11-29 Sometimes, my network interfaces are down after boot (only "lo" is up). After digging in the log, it looks like the network is started correctly, but then shut down again some seconds later. To be exact (timestamps removed for readability, everything happens within the one second): avahi-autoipd(wlan0)[3317]: Got SIGTERM, quitting. dhcpcd[4930]: wlan0: sending signal 15 to pid 3470 dhcpcd[3470]: wlan0: received SIGTERM, stopping dhcpcd[3470]: wlan0: removing default route via 192.168.1.1 metric 0 dhcpcd[3470]: wlan0: removing IP address 192.168.1.100/24 avahi-daemon[1747]: Withdrawing address record for 192.168.1.100 on wlan0. This happens only sometimes, I'd guess at every 10th boot. I'll attach journalctl -b output (hint: grep for "eth0" or "wlan0") and boot.log - please tell me if you need more/other logs to debug this problem. The workaround is: systemctl restart network(a)wlan0.service systemctl restart network(a)eth0.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 3