August 2015 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 903582] New: net-udev rules no longer applied in 13.2
by bugzilla_noreply＠novell.com 10 Aug '17

10 Aug '17

http://bugzilla.opensuse.org/show_bug.cgi?id=903582 Bug ID: 903582 Summary: net-udev rules no longer applied in 13.2 Classification: openSUSE Product: openSUSE Distribution Version: 13.2 RC 1 Hardware: Other OS: Other Status: NEW Severity: Major Priority: P5 - None Component: AutoYaST Assignee: autoyast-maintainers(a)suse.de Reporter: bos(a)je-eigen-domein.nl QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- We use autoyast templates with a static network configuration like: == <interfaces config:type="list"> <interface> <bootproto>static</bootproto> <device>eth0</device> <ipaddr><?=$ip ?></ipaddr> <netmask><?=$netmask ?></netmask> <startmode>auto</startmode> <usercontrol>no</usercontrol> </interface> </interfaces> <routing> <ip_forward config:type="boolean">false</ip_forward> <routes config:type="list"> <route> <destination>default</destination> <device>-</device> <gateway><?=$gateway ?></gateway> <netmask>-</netmask> </route> </routes> </routing> <net-udev config:type="list"> <rule> <name>eth0</name> <rule>ATTR{address}</rule> <value><?=$mac ?></value> </rule> </net-udev> == Works fine with OpenSuse 13.1 But the net-udev part is broken in OpenSuse 13.2 There is no longer a persistent network rules file generated in /etc/udev/rules.d And after installation OpenSuse creates the network interface eno1 (running DHCP) instead of eth0 (with static configuration) like specified, resulting in a broken network configuration. This is a major issue as it prevents dedicated server providers (which use static network configurations) from performing autoyast installations. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 908387] New: LXDE and Xfce does not logout.
by bugzilla_noreply＠novell.com 10 Aug '17

10 Aug '17

http://bugzilla.opensuse.org/show_bug.cgi?id=908387 Bug ID: 908387 Summary: LXDE and Xfce does not logout. Classification: openSUSE Product: openSUSE Distribution Version: 13.2 RC 1 Hardware: Other OS: openSUSE 13.2 Status: NEW Severity: Normal Priority: P5 - None Component: LXDE Assignee: andrea(a)opensuse.org Reporter: zozonmr(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:33.0) Gecko/20100101 Firefox/33.0 Build Identifier: When treing to logout from session LXDE does not log out. Xfce hangs at logout. Reproducible: Always Steps to Reproduce: 1. Install OpenSuse with LXDE with Nvidia driver 2. Create at least 2 users 3. try to logout and switch user Actual Results: LXDE: does not logout Xfce: hangs at logout screen Expected Results: logging out and being able to switch user -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 938731] New: logout of LXDE does not work
by bugzilla_noreply＠novell.com 10 Aug '17

10 Aug '17

http://bugzilla.opensuse.org/show_bug.cgi?id=938731 Bug ID: 938731 Summary: logout of LXDE does not work Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: x86-64 OS: openSUSE 13.2 Status: NEW Severity: Normal Priority: P5 - None Component: LXDE Assignee: andrea(a)opensuse.org Reporter: balloon(a)shigakeiichi.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- About LXDE desktop installing openSUSE 13.2 from an installer, When I chose "logout" among logout session, it does not work. - I choose the hardware in "x86-64", but this problem occurs in "x86(32bit)". - When we install other desktop environment, it may become normal. - Because the problem was reported in a forum by Japanese users, I performed bug report: http://forum.geeko.jp/index.php?p=/discussion/26/13-2-rc-%E3%81%A7%E3%81%AE… - I reproduce this while photographing a movie (from around 20:50): https://www.youtube.com/watch?v=tjU7pFfcB_w -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 900923] New: Network Manager DHCP
by bugzilla_noreply＠novell.com 10 Aug '17

10 Aug '17

http://bugzilla.opensuse.org/show_bug.cgi?id=900923 Bug ID: 900923 Summary: Network Manager DHCP Classification: openSUSE Product: openSUSE Factory Version: 13.2 Beta 1 Hardware: x86-64 OS: openSUSE 13.2 Status: NEW Severity: Normal Priority: P5 - None Component: Network Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: amish(a)munshi.biz QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I am using the Live GNOME DVD of openSUSE 13.2 RC1 on a 2013 Macbook pro. I connected my Ethernet cable to the laptop, NetworkManager dected the connection but dhcp client did not auto assign me an IP. I manually assigned an IP, configured gateway and nameserver and networking works perfectly fine. DHCP client is not working on Live GNOME DVD. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 902359] New: Add profile-based proxy settings
by bugzilla_noreply＠novell.com 10 Aug '17

10 Aug '17

http://bugzilla.opensuse.org/show_bug.cgi?id=902359 Bug ID: 902359 Summary: Add profile-based proxy settings Classification: openSUSE Product: openSUSE Distribution Version: 13.2 RC 1 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Network Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: villek(a)matrixscience.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I run openSUSE on a work laptop. - The office has an HTTP proxy server, so whenever the laptop is in the office, I plug in an Ethernet cable, run YAST, set system proxy settings to the office proxy server address, log out, log in and start working. - At home, I use wifi and run a proxy server in my router. When I use the laptop at home, NetworkManager automatically finds the correct SSID and joins it, but I still have to run YAST, set the proxy settings to the right address, log out and log in again. - When I'm travelling on business, the laptop of course encounters many wifi networks. If I want to use wifi in a hotel or at a conference centre, NetworkManager joins the network without problem. But I still have to run YAST, clear proxy settings, log out and log in again. I know this is because http_proxy is a system environment variable, and the way X is run means it inherits the environment variables of the underlying shell. But it would be really nice if the system was able to choose a proxy server address based on which network interface or SSID is active, or even just have a list of "proxy profiles" from which I can choose the most appropriate one without having to log out and log in. -- You are receiving this mail because: You are on the CC list for the bug.

1 7

[Bug 903118] New: KDE PackageKit helper tries and fails to find printer drivers with system-config-printer, DBUS error
by bugzilla_noreply＠novell.com 10 Aug '17

10 Aug '17

http://bugzilla.opensuse.org/show_bug.cgi?id=903118 Bug ID: 903118 Summary: KDE PackageKit helper tries and fails to find printer drivers with system-config-printer, DBUS error Classification: openSUSE Product: openSUSE Distribution Version: 13.2 RC 1 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE4 Workspace Assignee: kde-maintainers(a)suse.de Reporter: sb56637(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Hello, This bug is related to #902407. When adding a new printer with system-config-printer inside KDE, this error appears: https://bugzilla.opensuse.org/attachment.cgi?id=611088 The error does not appear outside of KDE. It appears to be a DBUS problem: --------------------------- ERROR:dbus.proxies:Introspect error on :1.68:/org/freedesktop/PackageKit: dbus.exceptions.IntrospectionParserException: Error parsing introspect data: <class 'xml.parsers.expat.ExpatError'>: unbound prefix: line 5, column 4 HTTP Status 403 None --------------------------- -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 902057] New: QT YaST2 black background in overview screen, unusable checkboxes
by bugzilla_noreply＠novell.com 10 Aug '17

10 Aug '17

http://bugzilla.opensuse.org/show_bug.cgi?id=902057 Bug ID: 902057 Summary: QT YaST2 black background in overview screen, unusable checkboxes Classification: openSUSE Product: openSUSE Distribution Version: 13.2 RC 1 Hardware: Other OS: Other Status: NEW Severity: Major Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: sb56637(a)gmail.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- See attachments -- You are receiving this mail because: You are on the CC list for the bug.

1 7

[Bug 899597] New: Samba Server installation window flickers
by bugzilla_noreply＠novell.com 10 Aug '17

10 Aug '17

http://bugzilla.opensuse.org/show_bug.cgi?id=899597 Bug ID: 899597 Summary: Samba Server installation window flickers Classification: openSUSE Product: openSUSE Factory Version: 13.2 Beta 1 Hardware: Other OS: openSUSE 13.2 Status: NEW Severity: Minor Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: kalenic(a)gmail.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- When you click on Samba Server in Yast2 you get a prompt to install additional packages. After those packages are downloaded they are installed one by one. In previous versions of openSUSE that little window which shows installation progress is permanent for all packages and after that closes. The problem is cosmetic but now for every package the window is closed and reopened which causes the background window of Yast to flicker from black & white to regular. This is caused by default KDE desktop effects. The solution would be to make install progres one window for all packages which will not cause the flicker. Evidently this is only reproducible in KDE. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 899415] New: openjkd 1.7 and 18 both installed on 13.2b1
by bugzilla_noreply＠novell.com 10 Aug '17

10 Aug '17

http://bugzilla.opensuse.org/show_bug.cgi?id=899415 Bug ID: 899415 Summary: openjkd 1.7 and 18 both installed on 13.2b1 Classification: openSUSE Product: openSUSE Factory Version: 13.2 Beta 1 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Java Assignee: bnc-team-java(a)forge.provo.novell.com Reporter: martin.schlander(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- On a fresh 13.2b1 live KDE installation (after running 'zypper inr'). The following openjdk packages are installed: cb400f@linux:~> rpm -qa *openjdk* java-1_7_0-openjdk-headless-1.7.0.65-4.4.1.i586 java-1_7_0-openjdk-1.7.0.65-4.4.1.i586 java-1_8_0-openjdk-plugin-1.5-4.1.3.i586 java-1_7_0-openjdk-plugin-1.5-4.1.3.i586 java-1_8_0-openjdk-headless-1.8.0.20-2.2.2.i586 java-1_8_0-openjdk-1.8.0.20-2.2.2.i586 cb400f@linux:~> I assume it's not intended to have both openjdk 1.7 and 1.8 co-installed by default. However I tested the web plugin in Firefox, and it works, and the latest version (1.8) is used. But I guess having both installed is a waste of space, and might cause unneeded security concerns and potentially other problems - and just general confusion. -- You are receiving this mail because: You are on the CC list for the bug.

1 7

[Bug 900429] New: (Visual Bug) GNOME Control Center Has an Empty Row At the Bottom
by bugzilla_noreply＠novell.com 10 Aug '17

10 Aug '17

http://bugzilla.opensuse.org/show_bug.cgi?id=900429 Bug ID: 900429 Summary: (Visual Bug) GNOME Control Center Has an Empty Row At the Bottom Classification: openSUSE Product: openSUSE Factory Version: 13.2 Beta 1 Hardware: Other OS: openSUSE 13.2 Status: NEW Severity: Normal Priority: P5 - None Component: GNOME Assignee: bnc-team-gnome(a)forge.provo.novell.com Reporter: Antoine.Saroufim(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 609441 --> http://bugzilla.opensuse.org/attachment.cgi?id=609441&action=edit GNOME Control Center with an Extra Row At the Bottom GNOME's Control Center has an empty row at the bottom as if it has a third row of icons but it doesn't. It is vertically longer than it should be. -- You are receiving this mail because: You are on the CC list for the bug.

1 3