December 2015 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 957668] Yast fails on openSUSE 13.2 / Raspberry Pi (1st gen)
by bugzilla_noreply＠novell.com 03 Dec '15

03 Dec '15

http://bugzilla.suse.com/show_bug.cgi?id=957668 http://bugzilla.suse.com/show_bug.cgi?id=957668#c4 --- Comment #4 from Ancor Gonzalez Sosa <ancor(a)suse.com> --- "ssh access" would be roughly equivalent to "walk by the YaST team office downstair with your Pi" :-) -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 957668] Yast fails on openSUSE 13.2 / Raspberry Pi (1st gen)
by bugzilla_noreply＠novell.com 03 Dec '15

03 Dec '15

http://bugzilla.suse.com/show_bug.cgi?id=957668 http://bugzilla.suse.com/show_bug.cgi?id=957668#c3 --- Comment #3 from Ancor Gonzalez Sosa <ancor(a)suse.com> --- Without logs there is no much we can do. Can you try to get more info using strace or provide ssh access to the machine somehow? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 931309] [Intel IVB] Occasional Xorg segmentation fault in driver
by bugzilla_noreply＠novell.com 03 Dec '15

03 Dec '15

http://bugzilla.suse.com/show_bug.cgi?id=931309 http://bugzilla.suse.com/show_bug.cgi?id=931309#c15 Maxim Marinchenko <mmarinchenko(a)yahoo.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(mmarinchenko@yaho | |o.com) | --- Comment #15 from Maxim Marinchenko <mmarinchenko(a)yahoo.com> --- Egbert, do you mean xf86-video-intel-2.99.917-5.1.x86_64 version? If yes, it works - no crashes. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 957668] Yast fails on openSUSE 13.2 / Raspberry Pi (1st gen)
by bugzilla_noreply＠novell.com 03 Dec '15

03 Dec '15

http://bugzilla.suse.com/show_bug.cgi?id=957668 http://bugzilla.suse.com/show_bug.cgi?id=957668#c1 Ancor Gonzalez Sosa <ancor(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ancor(a)suse.com, | |pgonin(a)suse.com Flags| |needinfo?(pgonin(a)suse.com) --- Comment #1 from Ancor Gonzalez Sosa <ancor(a)suse.com> --- Mmm. It's quite strange. The attached file includes only /var/log/YaST2/y2start.log (which says that YaST was successfully started) but no trace of /var/log/YaST2/y2log. YaST writes to that file very early in the execution process, so it should be there. In y2start.log there is only info about the attempt to run firstboot, not about your second manual attempt. Did you run yast2 as root? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 957056] yast partitioner asks for cryptsetup-mkinitrd which is not provided
by bugzilla_noreply＠novell.com 03 Dec '15

03 Dec '15

http://bugzilla.suse.com/show_bug.cgi?id=957056 http://bugzilla.suse.com/show_bug.cgi?id=957056#c3 Ancor Gonzalez Sosa <ancor(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ancor(a)suse.com Flags| |needinfo?(martin(a)oneiros.de | |) --- Comment #3 from Ancor Gonzalez Sosa <ancor(a)suse.com> --- Ok, so it really fails to create the encrypted partition. Please attach YaST logs https://en.opensuse.org/openSUSE:Report_a_YaST_bug -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 931309] [Intel IVB] Occasional Xorg segmentation fault in driver
by bugzilla_noreply＠novell.com 03 Dec '15

03 Dec '15

http://bugzilla.suse.com/show_bug.cgi?id=931309 http://bugzilla.suse.com/show_bug.cgi?id=931309#c14 Egbert Eich <eich(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(mmarinchenko@yaho | |o.com) --- Comment #14 from Egbert Eich <eich(a)suse.com> --- Maxim, can you test the 2.99.917 driver for me please? You can find it at the same location as the previous test driver. Thanks! -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 755603] The gnome keyring socket is not owned with the same credentials as the user login
by bugzilla_noreply＠novell.com 03 Dec '15

03 Dec '15

http://bugzilla.suse.com/show_bug.cgi?id=755603 Felix Zhang <fezhang(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fezhang(a)suse.com -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 950900] High fan speed and noise on laptop
by bugzilla_noreply＠novell.com 02 Dec '15

02 Dec '15

http://bugzilla.suse.com/show_bug.cgi?id=950900 http://bugzilla.suse.com/show_bug.cgi?id=950900#c13 Terje J. Hanssen <terje(a)nordland-teknikk.no> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(terje@nordland-te | |knikk.no) | --- Comment #13 from Terje J. Hanssen <terje(a)nordland-teknikk.no> --- I haven't loaded the 13.2 kernel over Leap 42.1. But I've found a workaround that works for 42.1 as follows: After the first, power on startup and logon that cause high speed fan, doing a hot reboot from there and logon again, cause the fan to run slow and normal again. Does this indicate something? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 957662] New: Yast & Yast2 both crash after update
by bugzilla_noreply＠novell.com 02 Dec '15

02 Dec '15

http://bugzilla.opensuse.org/show_bug.cgi?id=957662 Bug ID: 957662 Summary: Yast & Yast2 both crash after update Classification: openSUSE Product: openSUSE Tumbleweed Version: 2015* Hardware: x86-64 OS: Other Status: NEW Severity: Major Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: fkereki(a)gmail.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- Since the last "zypper dup" I ran, whenever I try to run "yast" from the console, I get: # yast /usr/lib/YaST2/bin/y2base: symbol lookup error: /usr/lib64/YaST2/plugin/libpy2UI.so.2: undefined symbol: _Z16should_be_loggediRKSs Opening "Yast2" and clicking on "Software Management" produces the same error: # yast2 Run command: /sbin/yast2 sw_single & /usr/lib/YaST2/bin/y2base: symbol lookup error: /usr/lib64/YaST2/plugin/libpy2UI.so.2: undefined symbol: _Z16should_be_loggediRKSs I tried both "zypper update" and "zypper dup" several times, just in case, with no difference. I checked the mentioned library, and I have: lrwxrwxrwx 1 root root 17 Oct 1 01:08 libpy2UI.so.2 -> libpy2UI.so.2.0.0 -rwxr-xr-x 1 root root 650384 Oct 1 01:08 libpy2UI.so.2.0.0 How can I solve this? Thanks a lot! -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 944125] New: Kernel audit cannot be turned off for a desktop application
by bugzilla_noreply＠novell.com 02 Dec '15

02 Dec '15

http://bugzilla.suse.com/show_bug.cgi?id=944125 Bug ID: 944125 Summary: Kernel audit cannot be turned off for a desktop application Classification: openSUSE Product: openSUSE Factory Version: 201505* Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-maintainers(a)forge.provo.novell.com Reporter: hguo(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- The system is running the latest Tumbleweed snapshot. I start a terminal and run: root@g123 /h/howard# auditd -s disable root@g123 /h/howard# auditctl -e 0 enabled 0 flag 1 pid 9409 rate_limit 0 backlog_limit 64 lost 3014 backlog 0 backlog_wait_time 60000 Then start Opera browser (31.0) on KDE desktop. However, kernel audit does not appear disabled for Opera browser, as I observe many audit trails coming with tab open/close operations. Examples: Sep 02 09:40:47 g123 opera[12593]: <audit-1326> auid=1000 uid=1000 gid=100 ses=2 pid=12593 comm="opera" exe="/usr/lib/x86_64-linux-gnu/opera/opera" sig=0 arch=c000003e syscall=2 compat=0 ip=0x7fd10556111f code=0x50000 Sep 02 09:40:47 g123 opera[9956]: <audit-1326> auid=1000 uid=1000 gid=100 ses=2 pid=9956 comm="opera" exe="/usr/lib/x86_64-linux-gnu/opera/opera" sig=0 arch=c000003e syscall=273 compat=0 ip=0x7fd106b56444 code=0x50000 In the meanwhile, auditctl confirms that auditing is disabled. So it appears that kernel audit cannot be turned off for certain desktop applications, or auditctl is giving false reports. -- You are receiving this mail because: You are on the CC list for the bug.

1 9