January 2015 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 902771] New: No network with wireless card and wicked service
by bugzilla_noreply＠novell.com 02 Jan '15

02 Jan '15

http://bugzilla.suse.com/show_bug.cgi?id=902771 Bug ID: 902771 Summary: No network with wireless card and wicked service Classification: openSUSE Product: openSUSE Factory Version: 13.2 Beta 1 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Network Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: pilotgi(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- After bug #893678 was marked as a duplicate of #895447 I am creating a new bug as I am still unable to get a network connection with my wireless card and wicked. I followed the instructions from the last comment of bug #893678 to shut down NetworkManager and verify that wicked is the only service running. Here is the output of 'systemctl status network.service wickedd.service wpa_supplicant.service NetworkManager.service' wicked.service - wicked managed network interfaces Loaded: loaded (/usr/lib/systemd/system/wicked.service; enabled) Active: active (exited) since Mon 2014-10-27 12:41:05 CDT; 4min 44s ago Process: 917 ExecStart=/usr/sbin/wicked --systemd ifup all (code=exited, status=0/SUCCESS) Main PID: 917 (code=exited, status=0/SUCCESS) CGroup: /system.slice/wicked.service Oct 27 12:41:05 linux-0a83 wicked[917]: device enp9s0 failed: operation timed out Oct 27 12:41:05 linux-0a83 wicked[917]: device wlp5s5 failed: operation timed out Oct 27 12:41:05 linux-0a83 wicked[917]: lo up Oct 27 12:41:05 linux-0a83 wicked[917]: enp9s0 setup-in-progress Oct 27 12:41:05 linux-0a83 wicked[917]: wlp5s5 setup-in-progress wickedd.service - wicked network management service daemon Loaded: loaded (/usr/lib/systemd/system/wickedd.service; enabled) Active: active (running) since Mon 2014-10-27 12:40:35 CDT; 5min ago Main PID: 903 (wickedd) CGroup: /system.slice/wickedd.service └─903 /usr/sbin/wickedd --systemd --foreground Oct 27 12:40:35 linux-0a83 wickedd[903]: unable to translate eap protocol AKA Oct 27 12:40:35 linux-0a83 wickedd[903]: unable to translate eap protocol AKA' Oct 27 12:40:35 linux-0a83 wickedd[903]: unable to translate eap protocol FAST Oct 27 12:40:36 linux-0a83 wickedd[903]: lo: address 127.0.0.1 covered by a static lease Oct 27 12:40:37 linux-0a83 wickedd[903]: lo: address ::1 covered by a static lease wpa_supplicant.service - WPA Supplicant daemon Loaded: loaded (/usr/lib/systemd/system/wpa_supplicant.service; enabled) Active: active (running) since Mon 2014-10-27 12:40:33 CDT; 5min ago Main PID: 815 (wpa_supplicant) CGroup: /system.slice/wpa_supplicant.service └─815 /usr/sbin/wpa_supplicant -c /etc/wpa_supplicant/wpa_supplicant.conf -u -f /var/log/wpa_sup... Oct 27 12:40:35 linux-0a83 wpa_supplicant[815]: ioctl[SIOCSIWENCODEEXT]: Invalid argument Oct 27 12:40:35 linux-0a83 wpa_supplicant[815]: ioctl[SIOCSIWENCODEEXT]: Invalid argument NetworkManager.service - Network Manager Loaded: loaded (/usr/lib/systemd/system/NetworkManager.service; disabled) Active: inactive (dead) And here is the result of the same command with ethernet connected: wicked.service - wicked managed network interfaces Loaded: loaded (/usr/lib/systemd/system/wicked.service; enabled) Active: active (exited) since Mon 2014-10-27 13:10:09 CDT; 8min ago Process: 4483 ExecStop=/usr/sbin/wicked --systemd ifdown all (code=exited, status=0/SUCCESS) Process: 2630 ExecReload=/usr/sbin/wicked --systemd ifreload all (code=exited, status=0/SUCCESS) Process: 4490 ExecStart=/usr/sbin/wicked --systemd ifup all (code=exited, status=0/SUCCESS) Main PID: 4490 (code=exited, status=0/SUCCESS) CGroup: /system.slice/wicked.service Oct 27 13:10:09 linux-0a83 wicked[4490]: device wlp5s5 failed: operation timed out Oct 27 13:10:09 linux-0a83 wicked[4490]: lo up Oct 27 13:10:09 linux-0a83 wicked[4490]: enp9s0 up Oct 27 13:10:09 linux-0a83 wicked[4490]: wlp5s5 setup-in-progress wickedd.service - wicked network management service daemon Loaded: loaded (/usr/lib/systemd/system/wickedd.service; enabled) Active: active (running) since Mon 2014-10-27 12:40:35 CDT; 37min ago Main PID: 903 (wickedd) CGroup: /system.slice/wickedd.service └─903 /usr/sbin/wickedd --systemd --foreground Oct 27 13:04:39 linux-0a83 wickedd[903]: lo: address ::1 covered by a static lease Oct 27 13:06:26 linux-0a83 wickedd[903]: lo: address 127.0.0.1 covered by a static lease Oct 27 13:06:26 linux-0a83 wickedd[903]: lo: address ::1 covered by a static lease Oct 27 13:08:19 linux-0a83 wickedd[903]: lo: address 127.0.0.1 covered by a static lease Oct 27 13:08:19 linux-0a83 wickedd[903]: lo: address ::1 covered by a static lease Oct 27 13:08:53 linux-0a83 wickedd[903]: lo: address 127.0.0.1 covered by a static lease Oct 27 13:08:53 linux-0a83 wickedd[903]: lo: address ::1 covered by a static lease Oct 27 13:09:39 linux-0a83 wickedd[903]: lo: address 127.0.0.1 covered by a static lease Oct 27 13:09:39 linux-0a83 wickedd[903]: lo: address ::1 covered by a static lease Oct 27 13:09:41 linux-0a83 wickedd[903]: enp9s0: Notified neighbours about IP address 192.xxx.x.xx wpa_supplicant.service - WPA Supplicant daemon Loaded: loaded (/usr/lib/systemd/system/wpa_supplicant.service; enabled) Active: active (running) since Mon 2014-10-27 12:40:33 CDT; 37min ago Main PID: 815 (wpa_supplicant) CGroup: /system.slice/wpa_supplicant.service └─815 /usr/sbin/wpa_supplicant -c /etc/wpa_supplicant/wpa_supplicant.conf -u -f /var/log/wpa_sup... Oct 27 12:40:35 linux-0a83 wpa_supplicant[815]: ioctl[SIOCSIWENCODEEXT]: Invalid argument Oct 27 12:40:35 linux-0a83 wpa_supplicant[815]: ioctl[SIOCSIWENCODEEXT]: Invalid argument NetworkManager.service - Network Manager Loaded: loaded (/usr/lib/systemd/system/NetworkManager.service; disabled) Active: inactive (dead) And the result of 'ps axwww | grep -E "dhc|NetworkManager" | grep -v grep' 900 ? SLs 0:00 /usr/lib/wicked/bin/wickedd-dhcp4 --systemd --foreground 901 ? SLs 0:00 /usr/lib/wicked/bin/wickedd-dhcp6 --systemd --foreground enp9s0 is set to 'Connect automatically on cable connection'. If I unplug the cable and reboot, I have to restart the network 3-4 times after conncecting the cable before I get a connection -- You are receiving this mail because: You are on the CC list for the bug.

1 17

[Bug 807781] New: Yast2: empty window under 12.2 KDE4.10 or XFCE 4.10 in NX or Xvnc session
by bugzilla_noreply＠novell.com 02 Jan '15

02 Jan '15

https://bugzilla.novell.com/show_bug.cgi?id=807781 https://bugzilla.novell.com/show_bug.cgi?id=807781#c0 Summary: Yast2: empty window under 12.2 KDE4.10 or XFCE 4.10 in NX or Xvnc session Classification: openSUSE Product: openSUSE 12.2 Version: Final Platform: x86-64 OS/Version: openSUSE 12.2 Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: manfred.kreisl(a)nexgo.de QAContact: jsrain(a)suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux i686; rv:13.0) Gecko/20100101 Firefox/13.0 If I start Yast2 in a remote NX or Xvnc session, Yast2 comes up but shows an empty window. Starting Yast2 from a console, I can see following messages kmxbmc:~ # yast2 X Error: BadAccess (attempt to access private resource denied) 10 Extension: 129 (MIT-SHM) Minor opcode: 1 (X_ShmAttach) Resource id: 0x1a00002 X Error: BadShmSeg (invalid shared segment parameter) 128 Extension: 129 (MIT-SHM) Minor opcode: 5 (X_ShmCreatePixmap) Resource id: 0x1a0000e X Error: BadDrawable (invalid Pixmap or Window parameter) 9 Major opcode: 62 (X_CopyArea) Resource id: 0x1a0000f X Error: BadPixmap (invalid Pixmap parameter) 4 Major opcode: 54 (X_FreePixmap) Resource id: 0x1a0000f X Error: BadShmSeg (invalid shared segment parameter) 128 Extension: 129 (MIT-SHM) Minor opcode: 2 (X_ShmDetach) Resource id: 0x1a0000e Looking deeper to the problem, I found that the issue is in the package libqt4-x11-4.8.4, current package from the KDE 4.10 repository (libqt4-x11-4.8.4-298.1 and at least one earlier version) is broken, libqt4-x11-4.8.4-283.1 from the KDE Factory repo is still ok. Reproducible: Always Steps to Reproduce: 1. Installing KDE4 from the KDE4.10 repo 2. Start a NX remote session 3. Start Yast2 -- 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 19

[Bug 792309] systemd: Apache2 fails to start (timeout) at boot when mod_ssl enabled
by bugzilla_noreply＠novell.com 02 Jan '15

02 Jan '15

http://bugzilla.suse.com/show_bug.cgi?id=792309 Kristyna Streitova <kstreitova(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution|--- |FIXED --- Comment #12 from Kristyna Streitova <kstreitova(a)suse.com> --- As the update was successfully released, I'm closing this bug as resolved. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 911558] New: HP Smart Array Controler Driver Generation 9 not recognized
by bugzilla_noreply＠novell.com 02 Jan '15

02 Jan '15

http://bugzilla.opensuse.org/show_bug.cgi?id=911558 Bug ID: 911558 Summary: HP Smart Array Controler Driver Generation 9 not recognized Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-maintainers(a)forge.provo.novell.com Reporter: jm(a)pks.mpg.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:33.0) Gecko/20100101 Firefox/33.0 Build Identifier: Neither in 13.1 nor in 13.2 are the latest drivers for the HP SmartArray Controler installed, therefor the current controlers are not recognized by the system. Reproducible: Always Actual Results: The Smart Array Controler is not recognized Expected Results: The Smart Array Controler should be recognized The latest drivers are availabe at: http://sourceforge.net/projects/cciss/files/hpsa-3.0-tarballs The only problem is, that you need to compile them again after every single kernel update. Instead of the old HP-Software "hpacucli", you now need the new management software by HP, which is called "hpssacli" -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 911505] YaST partitioner is mounting a NTFS drive with a dmask=022 it should be dmask=002 making the drive read only
by bugzilla_noreply＠novell.com 02 Jan '15

02 Jan '15

http://bugzilla.suse.com/show_bug.cgi?id=911505 Arvin Schnell <aschnell(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P4 - Low --- Comment #3 from Arvin Schnell <aschnell(a)suse.com> --- Needs more research, likely a fate request. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 903963] encrypted /home not mounted
by bugzilla_noreply＠novell.com 02 Jan '15

02 Jan '15

http://bugzilla.suse.com/show_bug.cgi?id=903963 --- Comment #15 from Thomas Blume <thomas.blume(a)suse.com> --- (In reply to Marc Schütz from comment #14) > (In reply to Daniel Zeleny from comment #13) > > Is it already in stable 13.2? I have same problems and it is quite annoying > > that KDM is started before /home is mounted. > > @Thomas Blume: I'm also interested in this. Will there be an update, or do > we have to wait for openSUSE 13.3? The fix is available in systemd-210-905 from the Base System repository at: http://download.opensuse.org/repositories/Base:/System/openSUSE_13.2/ I'm not sure when it will be available in the update repositories. Maybe someone from OpenSUSE maintenance can comment? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 911523] YaST2->Security->Boot->Interpretation of Ctrl-Alt-Del is ineffective
by bugzilla_noreply＠novell.com 02 Jan '15

02 Jan '15

http://bugzilla.suse.com/show_bug.cgi?id=911523 Lukas Ocilka <locilka(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|yast2-maintainers(a)suse.de |jsuchome(a)suse.com --- Comment #1 from Lukas Ocilka <locilka(a)suse.com> --- The ctrl+alt+del behavior has been implemented by this commit: https://github.com/yast/yast-security/commit/2cdc2950147c57d3ce59fc8698a019… -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 911505] YaST partitioner is mounting a NTFS drive with a dmask=022 it should be dmask=002 making the drive read only
by bugzilla_noreply＠novell.com 02 Jan '15

02 Jan '15

http://bugzilla.suse.com/show_bug.cgi?id=911505 Lukas Ocilka <locilka(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|yast2-maintainers(a)suse.de |aschnell(a)suse.com --- Comment #2 from Lukas Ocilka <locilka(a)suse.com> --- fmask=133,dmask=022 are there because of bug #300694 See https://github.com/yast/yast-storage/commit/5395df060223b83703e643ab90288c1… -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 911401] Wrong yast language when multiple languages specified in LANGUAGE env variable
by bugzilla_noreply＠novell.com 02 Jan '15

02 Jan '15

http://bugzilla.suse.com/show_bug.cgi?id=911401 Lukas Ocilka <locilka(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |locilka(a)suse.com Assignee|yast2-maintainers(a)suse.de |mvidner(a)suse.com --- Comment #1 from Lukas Ocilka <locilka(a)suse.com> --- Martin, please, have a look. Is this supported? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 911375] LDAP installing buggy, not work, no manual, no howto
by bugzilla_noreply＠novell.com 02 Jan '15

02 Jan '15

http://bugzilla.suse.com/show_bug.cgi?id=911375 Lukas Ocilka <locilka(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(Fiona777(a)seznam.c | |z) --- Comment #1 from Lukas Ocilka <locilka(a)suse.com> --- Please attach all Yast logs. More about Yast logs can be found here: https://en.opensuse.org/openSUSE:Report_a_YaST_bug Thanks! -- You are receiving this mail because: You are on the CC list for the bug.

1 0