December 2014 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 902697] New: Cannot start software witin YAST e.g Network Settings or Software Repositories
by bugzilla_noreply＠novell.com 20 Jan '17

20 Jan '17

http://bugzilla.opensuse.org/show_bug.cgi?id=902697 Bug ID: 902697 Summary: Cannot start software witin YAST e.g Network Settings or Software Repositories Classification: openSUSE Product: openSUSE Factory Version: 201408* Hardware: i586 OS: openSUSE 13.2 Status: NEW Severity: Major Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: f.leerink(a)xs4all.nl QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- Created attachment 611307 --> http://bugzilla.opensuse.org/attachment.cgi?id=611307&action=edit yast2 error message from Konsole After the Yast CONTROL Center software started successfully and I click e.g Network Settings you can see by the rotating stick that that program is started but that is all that happened. If I try to start ,as root, yast2 from the konsole I get the following error message: inux-vbye:/home/frans # yast2 static QPlatformTheme* QKdeTheme::createKdeTheme(): Unable to determine KDEHOME Run command: /sbin/yast2 add-on & [BUG] Segmentation fault at 0x000378 ruby 2.1.2p95 (2014-05-08 revision 45877) [i586-linux-gnu] [NOTE] You may have encountered a bug in the Ruby interpreter or extension libraries. Bug reports are welcome. For details: http://www.ruby-lang.org/bugreport.html /sbin/yast2: line 440: 2669 Aborted $ybindir/y2base $module "$@" "$SELECTED_GUI" $Y2_GEOMETRY $Y2UI_ARGS See attatchment for more details I have installed this system yesterday and have applied all available updates. -- You are receiving this mail because: You are on the CC list for the bug.

1 7

[Bug 904484] New: Nouveau x.org stays dark after resume from suspended state
by bugzilla_noreply＠novell.com 20 Jan '17

20 Jan '17

http://bugzilla.opensuse.org/show_bug.cgi?id=904484 Bug ID: 904484 Summary: Nouveau x.org stays dark after resume from suspended state Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: x86-64 OS: openSUSE 13.2 Status: NEW Severity: Normal Priority: P5 - None Component: X.Org Assignee: bnc-team-xorg-bugs(a)forge.provo.novell.com Reporter: lmuelle(a)suse.com QA Contact: xorg-maintainer-bugs(a)forge.provo.novell.com Found By: Development Blocker: No Suspend and resume worked for this system with openSUSE 13.1, kernel-default-3.11.10-21.1, with the Nouveau x.org driver. After a fresh install suspend works and resume is possible too. Afterwards I'm able to login over the network with ssh for example. Unfortunately the display stays black. Compared with bug#904483 (s2ram case) it doesn't help to go back to an openSUSE 13.1 kernel. -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 904825] New: Nouveau - MMIO write/read faul
by bugzilla_noreply＠novell.com 20 Jan '17

20 Jan '17

http://bugzilla.opensuse.org/show_bug.cgi?id=904825 Bug ID: 904825 Summary: Nouveau - MMIO write/read faul Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: X.Org Assignee: bnc-team-xorg-bugs(a)forge.provo.novell.com Reporter: renda.krell(a)gmail.com QA Contact: xorg-maintainer-bugs(a)forge.provo.novell.com Found By: --- Blocker: --- After dist upgrading from 13.1 / Tumbleweed to OpenSUSE 13.2 the nouveau driver has some trouble with the original kernel 3.16.6: [ 6.281241] nouveau E[ PBUS][0000:01:00.0] MMIO write of 0x00000001 FAULT at 0x4188ac [ TIMEOUT ] [ 6.281517] nouveau E[ PBUS][0000:01:00.0] MMIO write of 0xbad0011f FAULT at 0x000260 [ TIMEOUT ] [ 6.289592] nouveau E[ PBUS][0000:01:00.0] MMIO read of 0x00000000 FAULT at 0x000260 [ TIMEOUT ] [ 6.292231] nouveau E[ PBUS][0000:01:00.0] MMIO read of 0x00000000 FAULT at 0x000260 [ TIMEOUT ] Hardware: HP ZBook NVIDIA Corporation GK208GLM [Quadro K610M] >From what I remember this problem did not happen using the last Tumbleweed kernel 3.17.2 before. -- You are receiving this mail because: You are on the CC list for the bug.

1 7

[Bug 905565] New: AMD/Intel hybrid graphic won`t work with free/open driver
by bugzilla_noreply＠novell.com 20 Jan '17

20 Jan '17

http://bugzilla.opensuse.org/show_bug.cgi?id=905565 Bug ID: 905565 Summary: AMD/Intel hybrid graphic won`t work with free/open driver Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: HP OS: openSUSE 13.2 Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: lathanderjk(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/38.0.2125.122 Safari/537.36 Build Identifier: HP zbook 14, openSUSE 13.2 x86_64, xrandr --listproviders detect 3 GPU ( twice AMD with same ID) command DRI_PRIME=1 glxinfo | grep "OpenGL renderer" output OpenGL renderer string: Mesa DRI Intel(R) Haswell Mobile instead of Gallium 0.4 on AMD OLAND I try command xrandr --setprovideroffloadsink radeon Intel or xrandr --setprovideroffloadsink ID(radeon) ID(intel) but doesn`t work. Reproducible: Always -- You are receiving this mail because: You are on the CC list for the bug.

1 8

[Bug 905904] New: fresh install of openSUSE 13.2 KDE
by bugzilla_noreply＠novell.com 20 Jan '17

20 Jan '17

http://bugzilla.opensuse.org/show_bug.cgi?id=905904 Bug ID: 905904 Summary: fresh install of openSUSE 13.2 KDE Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: x86-64 OS: openSUSE 13.2 Status: NEW Severity: Critical Priority: P5 - None Component: X.Org Assignee: bnc-team-xorg-bugs(a)forge.provo.novell.com Reporter: juergenlange60(a)gmail.com QA Contact: xorg-maintainer-bugs(a)forge.provo.novell.com Found By: --- Blocker: --- After a new install of openSUSE 13.2 - KDE, my desktop was completely broken (windows were not rendered properly, menus would only partially display on mouse over). My graphics card is a GeForce 7600 GT. I somehow managed to turn off desktop effects (like groping in the dark) and the problem was gone. Conclusion: desktop effects should be turned off by default together with the nouveau driver. Addition (not critical): Later I installed the nvidia driver via zypper and the problem also didn't appear. However, with desktop effects turned on in "Configure Desktop", these don't work. When e.g. changing the animation speed, an error message appears "24 desktop effects could not be loaded"; details: "desktop effect system is not running". -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 910671] New: X does not handle additional DVI
by bugzilla_noreply＠novell.com 20 Jan '17

20 Jan '17

http://bugzilla.opensuse.org/show_bug.cgi?id=910671 Bug ID: 910671 Summary: X does not handle additional DVI Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: X.Org Assignee: bnc-team-xorg-bugs(a)forge.provo.novell.com Reporter: kinfoo.dev(a)gmail.com QA Contact: xorg-maintainer-bugs(a)forge.provo.novell.com Found By: --- Blocker: --- Created attachment 617856 --> http://bugzilla.opensuse.org/attachment.cgi?id=617856&action=edit X.org log Hi, I just updated my laptop, everything runs smooth. Except that when I plug an additional DVI both screens display black. I soon as I unplug additional DVI display, all windows are back. Back, but frozen, I can see and move mouse cursor. Unfortunately it is impossible to get focus for any of windows. Keyboard reacts to input like CTRL-ALT-F1. /etc/X11/xorg.conf does not exist. -- You are receiving this mail because: You are on the CC list for the bug.

1 7

[Bug 905444] New: Pidgin Attempt to unlock mutex that was not locked pidgin/skype4pidgin
by bugzilla_noreply＠novell.com 18 Jan '17

18 Jan '17

http://bugzilla.opensuse.org/show_bug.cgi?id=905444 Bug ID: 905444 Summary: Pidgin Attempt to unlock mutex that was not locked pidgin/skype4pidgin Classification: openSUSE Product: openSUSE Factory Version: NO 13.2 BUGS!! Hardware: Other OS: openSUSE 13.2 Status: NEW Severity: Major Priority: P5 - None Component: GNOME Assignee: bnc-team-gnome(a)forge.provo.novell.com Reporter: spamcenter(a)hotmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Adding skype4pidgin lets skype crash patch exists: https://code.google.com/p/skype4pidgin/issues/detail?id=239 Could some fix that, please -- You are receiving this mail because: You are on the CC list for the bug.

1 7

[Bug 900092] New: PackageKit/zypp has trouble with multiple versions in a repo (libzypp can handle it)
by bugzilla_noreply＠novell.com 18 Jan '17

18 Jan '17

http://bugzilla.opensuse.org/show_bug.cgi?id=900092 Bug ID: 900092 Summary: PackageKit/zypp has trouble with multiple versions in a repo (libzypp can handle it) Classification: openSUSE Product: openSUSE Factory Version: 201410* Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: GNOME Assignee: bnc-team-gnome(a)forge.provo.novell.com Reporter: dimstar(a)opensuse.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- The VideoLAN repository (and likely also packman) certainly have a strange setup for that, nevertheless it's existing in the real world. there is a package * vlc-2.1.5-2.1 (whith subpackages built, I only focus on one of them:) * libvlc5-2.1.5-2-1 (version 100% in sync to vlc) and there is * vlc-beta-3.0.0-2.1 * libvlc5-3.0.0-2.1 (it is supposed to be ABI compatible, but we prefer not to gamble) vlc has a Requires: libvlc5 = %{version-%{release} and so does vlc-beta vlc and vlc beta have a Conflicts: against each other. while the user has vlc-2.1.5-1.1 installed, a zypper up happily upgrades vlc inside the 'stable branch', and keeps libvlc5 in line to what it should be if the user has vlc-beta installe, the same works using zypper Using PackageKit though (pkcon for one): if the user has vlc installed, pkcon update fails with Fatal error: vlc-noX-2.1.5-111.1.x86_64 requires libvlc5 = 2.1.5-111.1, but this requirement cannot be provided which is quite annoying: if the user happens to have this constellation (and probably others!) then pkcon update simply aborts -- You are receiving this mail because: You are on the CC list for the bug.

1 16

[Bug 899510] New: Fix support using multiple base URLs for a reop
by bugzilla_noreply＠novell.com 16 Jan '17

16 Jan '17

http://bugzilla.suse.com/show_bug.cgi?id=899510 Bug ID: 899510 Summary: Fix support using multiple base URLs for a reop Classification: openSUSE Product: openSUSE Factory Version: 201409* Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: libzypp Assignee: zypp-maintainers(a)forge.provo.novell.com Reporter: ma(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- [http://lists.opensuse.org/zypp-devel/2014-10/msg00000.html] - Support defining multiple base URLs directly within a .reop file. - This is currently possible by using a 'mirrorlist=' instead of 'baseurl', but unfortunately using a local file as mirrorlist is broken (code strips 'path' component from URL which is illegal for 'file:' schema) - Fix zypper to non-interactively switch baseurls upon error. -- You are receiving this mail because: You are on the CC list for the bug.

1 16

[Bug 906005] New: Forward Email Template Error
by bugzilla_noreply＠novell.com 14 Jan '17

14 Jan '17

http://bugzilla.opensuse.org/show_bug.cgi?id=906005 Bug ID: 906005 Summary: Forward Email Template Error Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: All OS: openSUSE 13.2 Status: NEW Severity: Normal Priority: P5 - None Component: KDE4 Applications Assignee: kde-maintainers(a)suse.de Reporter: guoyunhebrave(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- This is the default head of forward mail in KMail: -------------------------------------------------- Subject: XXXXX Date: Tuesday 18 November 2014 From: 10:24:08 To: A <someonea(a)example.com> To: B <someoneb(a)example.com> ---------------------------------------------------- I checked the template of forward email, the head part is: ------------------------------------------------------- Subject: %OFULLSUBJECT Date: %ODATE From: %OTIMELONG To: %OFROMADDR %OADDRESSEESADDR ------------------------------------------------------- I think this is a template error. -- You are receiving this mail because: You are on the CC list for the bug.

1 2