January 2017 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1017734] ModemManager: Missing mbim-proxy
by bugzilla_noreply＠novell.com 02 Jan '17

02 Jan '17

http://bugzilla.suse.com/show_bug.cgi?id=1017734 http://bugzilla.suse.com/show_bug.cgi?id=1017734#c1 --- Comment #1 from Bernhard Wiedemann <bwiedemann(a)suse.com> --- This is an autogenerated message for OBS integration: This bug (1017734) was mentioned in https://build.opensuse.org/request/show/448484 13.2+42.1+42.2 / ModemManager -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1002563] python-sphinxcontrib-docbookrestapi is not installable
by bugzilla_noreply＠novell.com 02 Jan '17

02 Jan '17

http://bugzilla.suse.com/show_bug.cgi?id=1002563 http://bugzilla.suse.com/show_bug.cgi?id=1002563#c2 Dirk Mueller <dmueller(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #2 from Dirk Mueller <dmueller(a)suse.com> --- filed a drop request. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1017682] VUL-0: CVE-2016-10091: UnRTF: stack-based buffer overflows in cmd_* functions
by bugzilla_noreply＠novell.com 02 Jan '17

02 Jan '17

http://bugzilla.suse.com/show_bug.cgi?id=1017682 Andreas Stieger <astieger(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|opensuse-communityscreening |opensuse-kde-bugs@opensuse. |(a)forge.provo.novell.com |org -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1017682] VUL-0: CVE-2016-10091: UnRTF: stack-based buffer overflows in cmd_* functions
by bugzilla_noreply＠novell.com 02 Jan '17

02 Jan '17

http://bugzilla.suse.com/show_bug.cgi?id=1017682 http://bugzilla.suse.com/show_bug.cgi?id=1017682#c3 Ilya Chernykh <anixx(a)opensuse.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|anixx(a)opensuse.org |opensuse-communityscreening | |(a)forge.provo.novell.com --- Comment #3 from Ilya Chernykh <anixx(a)opensuse.org> --- Why this bug is assigned to me? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1015705] php7: php-config --php-binary gives wrong/missing binary
by bugzilla_noreply＠novell.com 02 Jan '17

02 Jan '17

http://bugzilla.suse.com/show_bug.cgi?id=1015705 http://bugzilla.suse.com/show_bug.cgi?id=1015705#c2 Petr Gajdos <pgajdos(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |INVALID --- Comment #2 from Petr Gajdos <pgajdos(a)suse.com> --- Closing as invalid.(In reply to Paolo Panto from comment #1) > I think, this could be closed. Closing as invalid. > on the other side: php-config --php-binary > the wording is a little bit misleading, cause /usr/bin/php from > php7 package is also a php binary... > > and "man php-config" says: > > --php-binary Full path to php CLI or CGI binary Feel free to report upstream. Thanks -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1014358] Hibernate fails with "ACPI: Hardware changed while hibernated, success doubtful"
by bugzilla_noreply＠novell.com 02 Jan '17

02 Jan '17

http://bugzilla.suse.com/show_bug.cgi?id=1014358 http://bugzilla.suse.com/show_bug.cgi?id=1014358#c1 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |digulla(a)hepe.com, | |tiwai(a)suse.com Flags| |needinfo?(digulla(a)hepe.com) --- Comment #1 from Takashi Iwai <tiwai(a)suse.com> --- It's mostly harmless, and we can't debug anything as long as it's related with Nvidia stuff, unfortunately. As a workaround, you can pass acpi_sleep=s4_nohwsig boot option. Give it a try. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1016607] i915 blinks; regression?
by bugzilla_noreply＠novell.com 02 Jan '17

02 Jan '17

http://bugzilla.suse.com/show_bug.cgi?id=1016607 http://bugzilla.suse.com/show_bug.cgi?id=1016607#c2 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ingham(a)i-pi.com, | |tiwai(a)suse.com Flags| |needinfo?(ingham(a)i-pi.com) --- Comment #2 from Takashi Iwai <tiwai(a)suse.com> --- Please give the hardware details, as this kind of issue is very specific to a hardware model. At least, hwinfo output would be helpful. Also, TW already moved to 4.9. Does the problem still persist? If yes, please report to upstream bugzilla (bugzilla.freedesktop.org) the component DRI/Intel. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1016223] Intel 7260 wifi card disconnect
by bugzilla_noreply＠novell.com 02 Jan '17

02 Jan '17

http://bugzilla.suse.com/show_bug.cgi?id=1016223 http://bugzilla.suse.com/show_bug.cgi?id=1016223#c3 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fabio74.lima(a)gmail.com, | |tiwai(a)suse.com Flags| |needinfo?(fabio74.lima@gmai | |l.com) --- Comment #3 from Takashi Iwai <tiwai(a)suse.com> --- Could you give the more hardware detail? At least, hwinfo output would be helpful. The symptom sounds like some issue in the power management. But it's not sure what's wrong, as Intel 7260 seems working fine on other machines, AFAIK. If you see any relevant error or warning in the kernel messages when the problem happens, please give the dmesg output, too. Or any other information showing the problem would help for further analysis. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1017175] With Kernel 4.4: crash of sddm and it seems of the X server (repeatable)
by bugzilla_noreply＠novell.com 02 Jan '17

02 Jan '17

http://bugzilla.suse.com/show_bug.cgi?id=1017175 http://bugzilla.suse.com/show_bug.cgi?id=1017175#c3 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(tiwai(a)suse.com) | --- Comment #3 from Takashi Iwai <tiwai(a)suse.com> --- Yes, we need every piece of information as much as possible, not as your words :) Please give the kernel messages, preferably before and after the sddm crash appears. Also, give X logs, too. But... (In reply to Stakanov Schufter from comment #2) > Created attachment 708133 [details] > hwinfo of X201 > > I have still AFAIK the xorg errors of the user in question. > > Problem is as follows: as 42.2 was incompatible with kmail/kontakt4 and I > did not find currently the kontact/kmail5 version convenient to work with I > did drop back to 42.1. > That said: I want to get this error fixed because I was using before with > 42.1 and the kernel from 42.2 (without any problem). Then under 4.1 suddenly > I had the very same problem (that did lead me first to use the stable kernel > and then, to shift to 42.2. This makes me wonder whether it's rather a user-space issue (either sddm or X). It might be dependent on the kernel, but it doesn't mean that the culprit is the kernel, instead, it might be just triggering a bug in user-space. But without logs, it's nothing but a guess. Please provide more logs and infos. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1017726] New: [doc]
by bugzilla_noreply＠novell.com 02 Jan '17

02 Jan '17

http://bugzilla.opensuse.org/show_bug.cgi?id=1017726 Bug ID: 1017726 Summary: [doc] Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.2 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Documentation Assignee: fs(a)suse.com Reporter: richard.bos(a)xs4all.nl QA Contact: fs(a)suse.com Found By: --- Blocker: --- 12.2.3 Scripts in <code class="filename">/etc/grub.d</code> https://doc.opensuse.org/documentation/leap/reference/html/book.opensuse.re… Information about 40_custom and 90_persistent are not fully clear. 1) How are 40_custom and 90_persistent related to each other? Why does one prefer over the other? 40_custom seems more flexible than 90_persistent. 2) In case of 90_persistent information seems to be missing. The lines to be stored in the /boot/grub2/grub.cfg must be between the lines: ### BEGIN /etc/grub.d/90_persistent ### <data to be put here> ### END /etc/grub.d/90_persistent ### It would be good to mention this requirement here. However, in the beginning of grub.cfg the following warning is stated: # head /boot/grub2/grub.cfg # # DO NOT EDIT THIS FILE # # It is automatically generated by grub2-mkconfig using templates # from /etc/grub.d and settings from /etc/default/grub As such, I would be good to mention that for 90_persistent this warning must be neglected. Perhaps in more general (refer to my remark 1) above ), it's probably better, easier to use 40_custom instead of 90_persistent. Is there a good reason for 90_persistent? If so, have it mentioned in the 90_persistent explanation please. -- You are receiving this mail because: You are on the CC list for the bug.

1 2