January 2017 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1017755] New: NVidia driver doesn't load on 42.2
by bugzilla_noreply＠novell.com 05 Jan '17

05 Jan '17

http://bugzilla.suse.com/show_bug.cgi?id=1017755 Bug ID: 1017755 Summary: NVidia driver doesn't load on 42.2 Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.2 Hardware: Other OS: Other Status: NEW Severity: Major Priority: P5 - None Component: X11 3rd Party Driver Assignee: sndirsch(a)suse.com Reporter: msvec(a)suse.com QA Contact: sndirsch(a)suse.com CC: lnussel(a)suse.com Found By: --- Blocker: --- I suppose it's this issue: https://devtalk.nvidia.com/default/topic/910803/-304-131-can-t-install-on-k… At least for G02 the behavior is similar IIRC -- You are receiving this mail because: You are on the CC list for the bug.

1 15

[Bug 1017716] New: Yast crashes when trying to read network configuration
by bugzilla_noreply＠novell.com 05 Jan '17

05 Jan '17

http://bugzilla.opensuse.org/show_bug.cgi?id=1017716 Bug ID: 1017716 Summary: Yast crashes when trying to read network configuration Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.2 Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: jweberhofer(a)weberhofer.at QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- Created attachment 708163 --> http://bugzilla.opensuse.org/attachment.cgi?id=708163&action=edit y2logs created after error Internal error. Please report a bug report with logs. Details: undefined local variable or method `value' for #<Yast::Path:0x0000000a21bc18 @components=[]> Caller: /usr/lib64/ruby/vendor_ruby/2.1.0/yast/path.rb:122:in `invalid_buffer?' The system has been updated from openSUSE 12.3 to Leap 42.2 and has two bridges and thress netwrok adapters configured -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 992756] rsyslog when started by rsyslog.socket doesn't listen network
by bugzilla_noreply＠novell.com 05 Jan '17

05 Jan '17

http://bugzilla.novell.com/show_bug.cgi?id=992756 http://bugzilla.novell.com/show_bug.cgi?id=992756#c2 --- Comment #2 from Nirmoy Das <nirmoy.das(a)suse.com> --- Hi Diego I tested the setup as per your description(rsyslog+dhcp-server+bind), I don't see a problem. Are you still facing the problem ? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1018193] v4l-utils is over 4 years old
by bugzilla_noreply＠novell.com 05 Jan '17

05 Jan '17

http://bugzilla.opensuse.org/show_bug.cgi?id=1018193 http://bugzilla.opensuse.org/show_bug.cgi?id=1018193#c2 --- Comment #2 from Bob Goddard <suse-20050616(a)bgcomp.co.uk> --- >> Why has this not been upgraded in so long? > In openSUSE Leap 42.2, this package is inherited from SLE at this time. WHY?????? The vast majority of other software gets updated regardless of version in SLE. In fact, why has SLE not been updated. V12 came out in October 2014, the version of v4l-utils then was standing at 1.6.0. >> The latest version is 1.10.1 from 15/6/16. > available in OBS https://software.opensuse.org/package/v4l-utils NO IT IS NOT, it is STILL 0.8.9. Please tell me how I can progress this. Please tell me how I can get the link to SLE broken, so that this can be updated.. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1011053] Rebooting takes a long time because dmeventd refuses to exit (LVM thin volume)
by bugzilla_noreply＠novell.com 05 Jan '17

05 Jan '17

http://bugzilla.suse.com/show_bug.cgi?id=1011053 http://bugzilla.suse.com/show_bug.cgi?id=1011053#c4 zhen ren <zren(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |IN_PROGRESS --- Comment #4 from zhen ren <zren(a)suse.com> --- Hi, I am new to this issue. I want to confirm one thing meanwhile I am trying to replicate your trouble on my side: > > I think it does mean that snapper + LV thin-provisioned snapshots for ext4 > should be enough to trigger it. Just make sure that dmeventd is running > before you try to reboot or shutdown. You may also note that dmeventd > refuses to exit with SIGTERM. > Does the problem happen every time when you shutdown or reboot? Or only occurred when the system is happening to run "dmeventd" deamon? What we need to known is what the lvm is doing there? We can imagine that snapper (hourly according to you) tell lvm to take snapshot, after that, the cleanup algorithm will also let lvm to cleanup the old snapshot. I don't know how long each of the operations lvm will take, which decides how busy lvm is, and the time window the shutdown meets a working lvm. It is reasonable if shutdown happens during lvm is busy. Anyway, I will look into more when I get time;-) > > Probably not relevant, but note I have an extra volume mounted inside the > /home FS. It's a regular volume, also ext4, not being snapshotted. it's fine;-) Eric -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 897774] btrfsck crashing while checking a corrupted file system
by bugzilla_noreply＠novell.com 05 Jan '17

05 Jan '17

http://bugzilla.opensuse.org/show_bug.cgi?id=897774 http://bugzilla.opensuse.org/show_bug.cgi?id=897774#c12 Johannes Obermayr <johannesobermayr(a)gmx.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(johannesobermayr@ | |gmx.de) | --- Comment #12 from Johannes Obermayr <johannesobermayr(a)gmx.de> --- Created attachment 708707 --> http://bugzilla.opensuse.org/attachment.cgi?id=708707&action=edit Requested btrfs-image # btrfs-image -c 9 /dev/sda2 btrfs-dump parent transid verify failed on 67666722816 wanted 385998 found 386004 Ignoring transid failure -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1018271] yast lan does not support dsa interfaces (switch ports)
by bugzilla_noreply＠novell.com 05 Jan '17

05 Jan '17

http://bugzilla.suse.com/show_bug.cgi?id=1018271 http://bugzilla.suse.com/show_bug.cgi?id=1018271#c4 Michal Filka <mfilka(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |afaerber(a)suse.com, | |mfilka(a)suse.com Flags| |needinfo?(afaerber(a)suse.com | |) --- Comment #4 from Michal Filka <mfilka(a)suse.com> --- yast depends on hwinfo | libhd when fetching list of available hw. According provided hwinfo output it seems that at least something is available. Some interfaces can be excluded from the list for various reasons. I did a quick check and it doesn't seem that any of this reasons is in game for this particular case. So, for further debugging it would be nice to have yast logs. Thanks. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1018259] VUL-0: CVE-2017-5180: firejail: local root exploit
by bugzilla_noreply＠novell.com 05 Jan '17

05 Jan '17

http://bugzilla.suse.com/show_bug.cgi?id=1018259 http://bugzilla.suse.com/show_bug.cgi?id=1018259#c1 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #1 from Takashi Iwai <tiwai(a)suse.com> --- Submitted with the update to 0.9.44.2 and the two fix patches now. Thanks. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 877191] BUG: unable to handle kernel NULL pointer dereference at 0000000000000020
by bugzilla_noreply＠novell.com 05 Jan '17

05 Jan '17

http://bugzilla.opensuse.org/show_bug.cgi?id=877191 http://bugzilla.opensuse.org/show_bug.cgi?id=877191#c3 Libor Pechacek <lpechacek(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|CONFIRMED |RESOLVED CC| |lpechacek(a)suse.com Resolution|--- |WORKSFORME --- Comment #3 from Libor Pechacek <lpechacek(a)suse.com> --- It seems that there were not enough spare brain cycles for the code path analysis. With openSUSE 13.1 out of maintenance I'm closing this bug. Anyway, thanks for the report, Sebastian! -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1012047] start on boot is not ticked in yast-dns-server
by bugzilla_noreply＠novell.com 05 Jan '17

05 Jan '17

http://bugzilla.suse.com/show_bug.cgi?id=1012047 http://bugzilla.suse.com/show_bug.cgi?id=1012047#c4 Franck Bui <fbui(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fbui(a)suse.com Flags| |needinfo?(igonzalezsosa@sus | |e.com) --- Comment #4 from Franck Bui <fbui(a)suse.com> --- (In reply to Imobach Gonzalez Sosa from comment #2) > > Pay attention to this line: "loaded (/etc/init.d/named; bad; vendor preset: > disabled)". So instead of "enabled" or "disabled", we get a "bad". > That's indeed a shortcoming that has been fixed by upstream commit a3c4eb07106b29, which is included in v230+. This means that the pending systemd update (v232) for factory will "fix" the description of the unit state ("bad"). But the change won't fix this particular bug, see below. @Imobach, it seems that yast is parsing the output and of "systemctl status" and expect to either find "enabled" or "disabled". If it's the case, this doesn't sound correct as: 1. there's no guaranty that the output of "systemctl status" will be stable. For example with v232 (which has the "fix") you'll see "generated" (instead of "bad"). 2. systemd provides a real (D-BUS) API to query the state of a unit file. 3. if 2. is not an option you still might rely on "systemctl is-enabled", which seems more appropriate and has at least a well defined behavior. So IMHO, a better fix would be to change yast to do the right thing. WDYT ? -- You are receiving this mail because: You are on the CC list for the bug.

1 0