[opensuse-factory] New Tumbleweed snapshot 20180818 released!
Please note that this mail was generated by a script.
The described changes are computed based on the x86_64 DVD.
The full online repo contains too many changes to be listed here.
Please check the known defects of this snapshot before upgrading:
https://openqa.opensuse.org/tests/overview?distri=opensuse&groupid=1&version=Tumbleweed&build=20180818
Please do not reply to this email to report issues, rather file a bug
on bugzilla.opensuse.org. For more information on filing bugs please
see https://en.opensuse.org/openSUSE:Submitting_bug_reports
Packages changed:
MozillaFirefox (61.0.1 -> 61.0.2)
PackageKit
drbd (9.0.14+git.62f906cf -> 9.0.15+git.c46d2790)
drbd-utils (9.4.0 -> 9.5.0)
ffmpeg-4 (4.0.1 -> 4.0.2)
firewalld (0.6.0 -> 0.6.1)
gtk2
gtk3
hyper-v
installation-images-Kubic
iso-codes (3.77 -> 3.79)
iw (4.9 -> 4.14)
kactivitymanagerd
kernel-source (4.17.14 -> 4.18.0)
kfilemetadata5
libdlm
libgsf (1.14.43 -> 1.14.44)
libmatroska
libsoup (2.62.2 -> 2.62.3)
mariadb-connector-c (3.0.5 -> 3.0.6)
nfs-utils
python-matplotlib (2.2.2 -> 2.2.3)
python-pycurl
python-six
quota
rpm
rubygem-mini_mime (1.0.0 -> 1.0.1)
strace (4.23 -> 4.24)
systemd
tracker
utf8proc (2.1.0 -> 2.2.0)
vim (8.1.0235 -> 8.1.0258)
xf86-video-v4l (0.2.0 -> 0.3.0)
xfce4-panel-plugin-mount (1.1.2 -> 1.1.3)
xfce4-panel-plugin-whiskermenu (2.2.0 -> 2.2.1)
xfce4-screenshooter (1.9.2 -> 1.9.3)
xfwm4 (4.12.4 -> 4.12.5)
yast2-http-server (4.1.0 -> 4.1.1)
yast2-instserver (4.0.3 -> 4.0.4)
=== Details ===
==== MozillaFirefox ====
Version update (61.0.1 -> 61.0.2)
Subpackages: MozillaFirefox-translations-common
- update to Firefox 61.0.2
* Improved website rendering with the Retained Display List feature
enabled (bmo#1474402)
* Fixed broken DevTools panels with certain extensions installed
(bmo#1474379)
* Fixed a crash for users with some accessibility tools enabled
(bmo#1474007)
==== PackageKit ====
Subpackages: PackageKit-backend-zypp PackageKit-gstreamer-plugin PackageKit-gtk3-module PackageKit-lang libpackagekit-glib2-18 typelib-1_0-PackageKitGlib-1_0
- Add PackageKit.tmpfiles: Use tmpfile.d to make sure PackageKit
doesn't package files in /var (bsc#1098042).
==== drbd ====
Version update (9.0.14+git.62f906cf -> 9.0.15+git.c46d2790)
Subpackages: drbd-kmp-default
- Update to 9.0.15-1
* fix tracking of changes (on a secondary) against the lost disk of a
primary and also fix re-attaching in case the disk is replaced
* fix live migrate of VMs on DRBD when migrated to/from diskless nodes
* fix an IO deadlock in DRBD when the activity log on a secondary runs
full
* fix hanging demote after IO error followed by attaching the disk
again and the corresponding resync
* fix DRBD dopping connection after an IO error on the secondary node
* improve details when online changing devices from diskless to with
disk and vice versa. (Including peers freeing bitmap slots)
* new module parameter to disable support for older protocol versions
* improve details when online changing devices from diskless to with disk
* remove no longer relevant compat tests
* expose openers via debugfs
* optimize IO submit code path
* compat for v4.18 kernel
==== drbd-utils ====
Version update (9.4.0 -> 9.5.0)
- Update to 9.5.0
* drbdmon: allow to start in problems view (--problems)
* drbdadm,v9: fix always failing stacked handlers from kernel
* drbdadm,v9: adjust now hands over the information that a
diskfull->diskless change was intentional.
* drbdadm,v9: adjust verifies now IPs
- Remove patch: fix_call_khelper_with_stack.patch in 60ec9fa68
==== ffmpeg-4 ====
Version update (4.0.1 -> 4.0.2)
Subpackages: libavcodec58 libavdevice58 libavfilter7 libavformat58 libavresample4 libavutil56 libpostproc55 libswresample3 libswscale5
- Update to version 4.0.2:
* Various bugfixes and a revert.
- bsc#1092241 Enable webvtt encoders and decoders.
- Build codec2 encoder and decoder, add libcodec2 to
enable_decoders and enable_encoders.
- Enable mpeg 1 and 2 encoders.
- Add conditional pkgconfig(aom) BuildRequires and pass
- -enable-libaom to configure as well as add libaom and libaom_av1
to enable_decoders and enable_encoders: Build AOMedia Video 1
(AV1) support.
- bsc#1103064 attempt to allow migration from the unprefixed devel
packages cleanly
==== firewalld ====
Version update (0.6.0 -> 0.6.1)
Subpackages: firewall-macros firewalld-lang python3-firewall
- Restore nftables as default backend (bsc#1102761). nftables and
iptables can co-exist but the 'nat' table had a bug which was fixed
in kernel-4.18.
- Update to 0.6.1. Some of the changes are:
* Correct source/destination in rich rule masquerade
* Only modify ifcfg files for permanent configuration changes
* Fix a backtrace when calling common_reverse_rule()
* man firewalld.conf: Show nftables is the default FirewallBackend
* firewall-config: fix some untranslated strings that caused a UI
bug causing rich rules to not be modify-able (bsc#1096542)
* fw_direct: avoid log for untracked passthrough queries
* fixed many issues if iptables is actually iptables-nft
* Use preferred location for AppData files
* ipXtables: fix ICMP block inversion with set-log-denied
* fixes ICMP block inversion with set-log-denied with
IndividualCalls=yes
* nftables: fix set-log-denied if target is not ACCEPT
* fw_direct: strip _direct chain suffix if using nftables
* NetworkManager integration bugfixes.
==== gtk2 ====
Subpackages: gtk2-data gtk2-immodule-amharic gtk2-immodule-inuktitut gtk2-immodule-thai gtk2-immodule-vietnamese gtk2-immodule-xim gtk2-lang gtk2-tools gtk2-tools-32bit libgtk-2_0-0 libgtk-2_0-0-32bit
- Fix package name to be uniform immodules -> immodule bsc#1104264
==== gtk3 ====
Subpackages: gtk3-data gtk3-immodule-amharic gtk3-immodule-inuktitut gtk3-immodule-thai gtk3-immodule-vietnamese gtk3-immodule-xim gtk3-lang gtk3-tools libgtk-3-0 typelib-1_0-Gtk-3_0
- Fix package name to be uniform immodules -> immodule bsc#1104264
==== hyper-v ====
- hyper-v.tools.hv.hv_vss_daemon.c: Include
On Tue, 2018-08-21 at 15:00 +0200, Dominique Leuenberger wrote:
kernel-source (4.17.14 -> 4.18.0)
Hi all, I would like to inform you about an issue uncovered in kernel 4.18, coming from the L1TF mitigation patch set. The PAE kernel (i586), when running on intal x86_64 hardware with an address size of > 42 phusical bits can show issue while enabling swap space, in the form of: Truncating oversized swap area, only using 0k out of 2047996k (to be found in dmesg) The options you have in this case are: * Accept to run without swap for the time being * Keep on using a 4.17.x kernel * If it's a VM you run a 32bit guest in on a 64bit host, you might tune the address size of the machine The kernel team has already submitted a fixed kernel into Tumbleweed, which is currently being staged and is hopefully reaching Tumbleweed soon. Cheers, Dominique
* Dominique Leuenberger / DimStar
On Tue, 2018-08-21 at 15:00 +0200, Dominique Leuenberger wrote:
kernel-source (4.17.14 -> 4.18.0)
and the nvidia driver, NVIDIA-Linux-x86_64-390.67.run, will not install w/o adding "--no-drm" to install params. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Registered Linux User #207535 @ http://linuxcounter.net Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Patrick Shanahan wrote:
* Dominique Leuenberger / DimStar
[08-21-18 09:39]: On Tue, 2018-08-21 at 15:00 +0200, Dominique Leuenberger wrote:
kernel-source (4.17.14 -> 4.18.0)
and the nvidia driver, NVIDIA-Linux-x86_64-390.67.run, will not install w/o adding "--no-drm" to install params.
Maybe update? I'm running bumblebee, that one uses 390.77. Compiled fine against 4.18.0, and also loads&runs w/o problems (optirun) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
* Peter Suetterlin
Patrick Shanahan wrote:
* Dominique Leuenberger / DimStar
[08-21-18 09:39]: On Tue, 2018-08-21 at 15:00 +0200, Dominique Leuenberger wrote:
kernel-source (4.17.14 -> 4.18.0)
and the nvidia driver, NVIDIA-Linux-x86_64-390.67.run, will not install w/o adding "--no-drm" to install params.
Maybe update? I'm running bumblebee, that one uses 390.77. Compiled fine against 4.18.0, and also loads&runs w/o problems (optirun)
tks, hadn't noticed that being available. >390.xx doesn't support my ancient gs400 series card :(. will adivse result next opportunity. tks -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Registered Linux User #207535 @ http://linuxcounter.net Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
* Patrick Shanahan
* Peter Suetterlin
[08-21-18 10:22]: Patrick Shanahan wrote:
* Dominique Leuenberger / DimStar
[08-21-18 09:39]: On Tue, 2018-08-21 at 15:00 +0200, Dominique Leuenberger wrote:
kernel-source (4.17.14 -> 4.18.0)
and the nvidia driver, NVIDIA-Linux-x86_64-390.67.run, will not install w/o adding "--no-drm" to install params.
Maybe update? I'm running bumblebee, that one uses 390.77. Compiled fine against 4.18.0, and also loads&runs w/o problems (optirun)
tks, hadn't noticed that being available. >390.xx doesn't support my ancient gs400 series card :(.
will adivse result next opportunity. tks
more info and have not yet tried 390.77, inxi -Gxx reports (partial): OpenGL: renderer: GeForce GTS 450/PCIe/SSE2 v: 4.6.0 NVIDIA 390.67 direct render: Yes so perhaps the error msg is itself in err... -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Registered Linux User #207535 @ http://linuxcounter.net Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
* Patrick Shanahan
* Patrick Shanahan
[08-21-18 13:24]: * Peter Suetterlin
[08-21-18 10:22]: Patrick Shanahan wrote:
* Dominique Leuenberger / DimStar
[08-21-18 09:39]: On Tue, 2018-08-21 at 15:00 +0200, Dominique Leuenberger wrote:
kernel-source (4.17.14 -> 4.18.0)
and the nvidia driver, NVIDIA-Linux-x86_64-390.67.run, will not install w/o adding "--no-drm" to install params.
Maybe update? I'm running bumblebee, that one uses 390.77. Compiled fine against 4.18.0, and also loads&runs w/o problems (optirun)
tks, hadn't noticed that being available. >390.xx doesn't support my ancient gs400 series card :(.
will adivse result next opportunity. tks
more info and have not yet tried 390.77,
inxi -Gxx reports (partial): OpenGL: renderer: GeForce GTS 450/PCIe/SSE2 v: 4.6.0 NVIDIA 390.67 direct render: Yes
so perhaps the error msg is itself in err...
390.77 does indeed build w/o requiring "--no-drm". although, building with "--no-drm" and heavy use of gpu developing photographs showed little noticable performance difference, if any. am running another test atm to confirm above. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Registered Linux User #207535 @ http://linuxcounter.net Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
* Patrick Shanahan
* Patrick Shanahan
[08-23-18 08:25]: * Patrick Shanahan
[08-21-18 13:24]: * Peter Suetterlin
[08-21-18 10:22]: Patrick Shanahan wrote:
* Dominique Leuenberger / DimStar
[08-21-18 09:39]: On Tue, 2018-08-21 at 15:00 +0200, Dominique Leuenberger wrote: > kernel-source (4.17.14 -> 4.18.0)
and the nvidia driver, NVIDIA-Linux-x86_64-390.67.run, will not install w/o adding "--no-drm" to install params.
Maybe update? I'm running bumblebee, that one uses 390.77. Compiled fine against 4.18.0, and also loads&runs w/o problems (optirun)
tks, hadn't noticed that being available. >390.xx doesn't support my ancient gs400 series card :(.
will adivse result next opportunity. tks
more info and have not yet tried 390.77,
inxi -Gxx reports (partial): OpenGL: renderer: GeForce GTS 450/PCIe/SSE2 v: 4.6.0 NVIDIA 390.67 direct render: Yes
so perhaps the error msg is itself in err...
390.77 does indeed build w/o requiring "--no-drm". although, building with "--no-drm" and heavy use of gpu developing photographs showed little noticable performance difference, if any.
am running another test atm to confirm above.
the test I ran more or less confirms that "--no-drm" makes no or negligible performance hit. ??? -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Registered Linux User #207535 @ http://linuxcounter.net Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Tuesday, 21 August 2018 14:00:03 BST Dominique Leuenberger wrote:
Packages changed: MozillaFirefox (61.0.1 -> 61.0.2) Hi
Since this snapshot update my screen display is occasionally pushed to the left by about 10% and the only way to recover is to reboot. It usually happens once i log out of a session and return to the login screen but today it happened on boot up. Anyone else experiencing this? regards Ian -- opensuse:tumbleweed:20180818 Qt: 5.11.1 KDE Frameworks: 5.48.0 - KDE Plasma: 5.13.4 - kwin 5.13.4 kdm-4.11.22-15.3.x86_64 kmail2 5.8.3 - akonadiserver 5.8.3 - Kernel: 4.18.0-1-default - xf86-video-nouveau: 1.0.15 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Ianseeks composed on 2018-08-23 07:59 (UTC+0100):
Since this snapshot update my screen display is occasionally pushed to the left by about 10% and the only way to recover is to reboot. It usually happens once i log out of a session and return to the login screen but today it happened on boot up...xf86-video-nouveau: 1.0.15
Does it still happen if you 'zypper rm xf86-video-nouveau'? Exactly which gfxchip do you have ('inxi -Gxx')? -- "Wisdom is supreme; therefore get wisdom. Whatever else you get, get wisdom." Proverbs 4:7 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Thursday, 23 August 2018 08:16:05 BST Felix Miata wrote:
Ianseeks composed on 2018-08-23 07:59 (UTC+0100):
Since this snapshot update my screen display is occasionally pushed to the left by about 10% and the only way to recover is to reboot. It usually happens once i log out of a session and return to the login screen but today it happened on boot up...xf86-video-nouveau: 1.0.15
Does it still happen if you 'zypper rm xf86-video-nouveau'?
I've not tried that, i'll give it a go after i've sent this email
Exactly which gfxchip do you have ('inxi -Gxx')?
Its an old one GT218 [GEforce 210] Thanks -- opensuse:tumbleweed:20180818 Qt: 5.11.1 KDE Frameworks: 5.48.0 - KDE Plasma: 5.13.4 - kwin 5.13.4 kmail2 5.8.3 - akonadiserver 5.8.3 - Kernel: 4.18.0-1-default - xf86-video-nouveau: 1.0.15 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Ianseeks composed on 2018-08-23 09:37 (UTC+0100):
Felix Miata wrote:
Ianseeks composed on 2018-08-23 07:59 (UTC+0100):
Since this snapshot update my screen display is occasionally pushed to the left by about 10% and the only way to recover is to reboot. It usually happens once i log out of a session and return to the login screen but today it happened on boot up...xf86-video-nouveau: 1.0.15
Does it still happen if you 'zypper rm xf86-video-nouveau'?
I've not tried that, i'll give it a go after i've sent this email
Mine's been like that many moons.
Exactly which gfxchip do you have ('inxi -Gxx')?
Its an old one GT218 [GEforce 210]
$ inxi -Gxx Graphics: Card-1: NVIDIA GT218 [GeForce 210] driver: nouveau v: kernel bus ID: 01:00.0 chip ID: 10de:0a65 Display: server: X.Org 1.20.1 driver: modesetting unloaded: fbdev,vesa alternate: nouveau,nv,nvidia resolution: 1920x1200~60Hz OpenGL: renderer: NVA8 v: 3.3 Mesa 18.1.6 compat-v: 3.1 direct render: Yes Which cable type do you use to connect it to your display? I use HDMI ATM. It seems rather slow, but without apparent errors other than no sound. TW just updated Xorg server from 1.20.0 to 1.20.1. Maybe go ahead with another dup & see if it still happens. Here I have yet to see it, but this is just a test box, so doesn't spend much time up. Also I have explicitly disabled compositing, and run only KDE3 on it. -- "Wisdom is supreme; therefore get wisdom. Whatever else you get, get wisdom." Proverbs 4:7 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Thursday, 23 August 2018 13:35:55 BST Felix Miata wrote:
Ianseeks composed on 2018-08-23 09:37 (UTC+0100):
Felix Miata wrote:
Ianseeks composed on 2018-08-23 07:59 (UTC+0100):
Since this snapshot update my screen display is occasionally pushed to the left by about 10% and the only way to recover is to reboot. It usually happens once i log out of a session and return to the login screen but today it happened on boot up...xf86-video-nouveau: 1.0.15
Does it still happen if you 'zypper rm xf86-video-nouveau'?
I've not tried that, i'll give it a go after i've sent this email
Mine's been like that many moons. removing that meant i ended up at the cli with no GUI so i reinstalled it
Exactly which gfxchip do you have ('inxi -Gxx')? inxi -Gxx Graphics: Card-1: NVIDIA GT218 [GeForce 210] driver: nouveau v: kernel bus ID: 01:00.0 chip ID: 10de:0a65 Display: server: X.Org 1.20.0 driver: nouveau compositor: kwin x11 resolution: 1680x1050~60Hz OpenGL: renderer: llvmpipe (LLVM 6.0 128 bits) v: 3.3 Mesa 18.1.5 compat-v: 3.1 direct render: Yes Its an old one GT218 [GEforce 210]
$ inxi -Gxx Graphics: Card-1: NVIDIA GT218 [GeForce 210] driver: nouveau v: kernel bus ID: 01:00.0 chip ID: 10de:0a65 Display: server: X.Org 1.20.1 driver: modesetting unloaded: fbdev,vesa alternate: nouveau,nv,nvidia resolution: 1920x1200~60Hz OpenGL: renderer: NVA8 v: 3.3 Mesa 18.1.6 compat-v: 3.1 direct render: Yes
Which cable type do you use to connect it to your display? I use HDMI ATM. It seems rather slow, but without apparent errors other than no sound. Just a standard cable as per what came with the monitor - its been working fine for years, its just after this snapshot. I tried changing to SDDM to see if that worked okay but that was painful, kdeinit5 crashed on login and systemd plus kdeinit5 were grabbing tons of CPU making any work impossible - back to kdm now.
TW just updated Xorg server from 1.20.0 to 1.20.1. Maybe go ahead with another dup & see if it still happens. Here I have yet to see it, but this is just a test box, so doesn't spend much time up. Also I have explicitly disabled compositing, and run only KDE3 on it.
Yes, just seen that, i'll update and see if that makes a difference. Thanks for the help. -- opensuse:tumbleweed:20180818 Qt: 5.11.1 KDE Frameworks: 5.48.0 - KDE Plasma: 5.13.4 - kwin 5.13.4 kmail2 5.8.3 - akonadiserver 5.8.3 - Kernel: 4.18.0-1-default - xf86-video-nouveau: 1.0.15 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Ianseeks composed on 2018-08-23 14:58 (UTC+0100):
Felix Miata wrote:
Ianseeks composed on 2018-08-23 09:37 (UTC+0100):
Felix Miata wrote:
Ianseeks composed on 2018-08-23 07:59 (UTC+0100):
Since this snapshot update my screen display is occasionally pushed to the left by about 10% and the only way to recover is to reboot. It usually happens once i log out of a session and return to the login screen but today it happened on boot up...xf86-video-nouveau: 1.0.15
Does it still happen if you 'zypper rm xf86-video-nouveau'?
I've not tried that, i'll give it a go after i've sent this email
Mine's been like that many moons.
removing that meant i ended up at the cli with no GUI so i reinstalled it
No greeter for me either, but startx worked. It turns out that kdm3 needed a package(s) that wasn't installed, either Mesa-dri-nouveau and/or libvdpau_nouveau. I installed both, solving the failure, so like all my other PCs with nvidia gfx, xf86-video-nouveau is not installed and still Xorg works as expected. -- "Wisdom is supreme; therefore get wisdom. Whatever else you get, get wisdom." Proverbs 4:7 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Friday, 24 August 2018 06:43:08 BST Felix Miata wrote:
Ianseeks composed on 2018-08-23 14:58 (UTC+0100):
Felix Miata wrote:
Ianseeks composed on 2018-08-23 09:37 (UTC+0100):
Felix Miata wrote:
Ianseeks composed on 2018-08-23 07:59 (UTC+0100):
Since this snapshot update my screen display is occasionally pushed to the left by about 10% and the only way to recover is to reboot. It usually happens once i log out of a session and return to the login screen but today it happened on boot up...xf86-video-nouveau: 1.0.15
Does it still happen if you 'zypper rm xf86-video-nouveau'?
I've not tried that, i'll give it a go after i've sent this email
Mine's been like that many moons.
removing that meant i ended up at the cli with no GUI so i reinstalled it
No greeter for me either, but startx worked. It turns out that kdm3 needed a package(s) that wasn't installed, either Mesa-dri-nouveau and/or libvdpau_nouveau. I installed both, solving the failure, so like all my other PCs with nvidia gfx, xf86-video-nouveau is not installed and still Xorg works as expected.
Ok, i'll try that for a while as the latest snapshot did not fix the issue. Thanks -- opensuse:tumbleweed:20180820 Qt: 5.11.1 KDE Frameworks: 5.48.0 - KDE Plasma: 5.13.4 - kwin 5.13.4 kmail2 5.8.3 - akonadiserver 5.8.3 - Kernel: 4.18.0-1-default - xf86-video-nouveau: 1.0.15 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Friday, 24 August 2018 06:43:08 BST Felix Miata wrote:
Ianseeks composed on 2018-08-23 14:58 (UTC+0100):
Felix Miata wrote:
Ianseeks composed on 2018-08-23 09:37 (UTC+0100):
Felix Miata wrote: snip No greeter for me either, but startx worked. It turns out that kdm3 needed a package(s) that wasn't installed, either Mesa-dri-nouveau and/or libvdpau_nouveau. I installed both, solving the failure, so like all my other PCs with nvidia gfx, xf86-video-nouveau is not installed and still Xorg works as expected.
I seem to have "solved" the problem. If i use systemsettings5 and reduce the resolution and apply it and then put it back to the original one, it seems to have stopped the shifting to the left but its caused another minor issue that i'll need do a separate email for. thanks for the advice. -- opensuse:tumbleweed:20180820 Qt: 5.11.1 KDE Frameworks: 5.48.0 - KDE Plasma: 5.13.4 - kwin 5.13.4 kmail2 5.8.3 - akonadiserver 5.8.3 - Kernel: 4.18.0-1-default - xf86-video-nouveau: 1.0.15 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Since this update gimp is no longer working for me! With my previous version (TW 20180812) it still runs, when I start it now from a console it just hangs there until I press CTRL-C, then it repots a segfault: woodstock:~% gimp ^CSegmentation fault (core dumped) This was gimp-2.10.4. meanwhile I am at 20180820 with gimp-2.10.6 I use gimp from repo home:/mrbadguy:/gimp-unstable Anyone else running 2.10 successfully on current TW? from which repo? -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 08/28/2018 09:53 AM, Peter Suetterlin wrote:
Since this update gimp is no longer working for me!
With my previous version (TW 20180812) it still runs, when I start it now from a console it just hangs there until I press CTRL-C, then it repots a segfault:
woodstock:~% gimp ^CSegmentation fault (core dumped)
This was gimp-2.10.4. meanwhile I am at 20180820 with gimp-2.10.6
I use gimp from repo home:/mrbadguy:/gimp-unstable
Anyone else running 2.10 successfully on current TW? from which repo?
I am running it on the current TW release (updated this morning). It is version 2.10.4 from the openSUSE-Tumbleweed-OSS repo. You might try forcing the repo change from the YaST GUI. Larry -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Peter Suetterlin wrote:
Since this update gimp is no longer working for me!
With my previous version (TW 20180812) it still runs, when I start it now from a console it just hangs there until I press CTRL-C, then it repots a segfault:
woodstock:~% gimp ^CSegmentation fault (core dumped)
This was gimp-2.10.4. meanwhile I am at 20180820 with gimp-2.10.6
I use gimp from repo home:/mrbadguy:/gimp-unstable
Anyone else running 2.10 successfully on current TW? from which repo?
Looking around (I had used that repo for more than a year w/o issues) I realized the official TW also has gimp 2.10 now (though 'only' 2.10.4). So I switched to that one instead. The symptom is still the same though: hangs until ^C, then segfault. Additional info: Skylake laptop with HD530 graphics (in case it's related). At least a simple 'gimp -h' works. Other option: Python. I had two times when, after starting, the splash screen actually showed up, and then, when querying plugins, stopped at python-eval.py Maybe someone has other suggestions what to look for? -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
So some more updates. I'm on the official TW version now (2.10.4), on TW 20180820 Others are running this without problems, both on nvidia and intel graphics. I can strace the execution. Last thing to happen is that it does several clone calls, and the last line then is futex(0x7f9c377b39d0, FUTEX_WAIT, 6842, NULL Where it will indefinitely hang. The respective clone call is clone(child_stack=0x7f9c377b28f0, flags=CLONE_VM|CLONE_FS|CLONE_FILES|CLONE_SIGHAND|CLONE_THREAD|CLONE_SYSVSEM|CLONE_SETTLS|CLONE_PARENT_SETTID|CLONE_CHILD_CLEARTID, parent_tidptr=0x7f9c377b39d0, tls=0x7f9c377b3700, child_tidptr=0x7f9c377b39d0) = 6842 I have no idea what that means though :( I tried running in gdb (also without knowing what I am doing...) [New Thread 0x7fffe90d4700 (LWP 8868)] [New Thread 0x7fffe88d3700 (LWP 8869)] [New Thread 0x7fffe7abd700 (LWP 8870)] [New Thread 0x7fffe72bc700 (LWP 8871)] [New Thread 0x7fffe6abb700 (LWP 8872)] [New Thread 0x7fffe57c7700 (LWP 8873)] [New Thread 0x7fffe4fc6700 (LWP 8874)] [Thread 0x7fffe7abd700 (LWP 8870) exited] [Thread 0x7fffe88d3700 (LWP 8869) exited] [Thread 0x7fffe90d4700 (LWP 8868) exited] Then hangs. Anyone know how to get more info from it in that state? Have to quite for today :( -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Am 28.08.2018 um 16:53 schrieb Peter Suetterlin:
Since this update gimp is no longer working for me!
With my previous version (TW 20180812) it still runs, when I start it now from a console it just hangs there until I press CTRL-C, then it repots a segfault:
woodstock:~% gimp ^CSegmentation fault (core dumped)
This was gimp-2.10.4. meanwhile I am at 20180820 with gimp-2.10.6
I use gimp from repo home:/mrbadguy:/gimp-unstable
Anyone else running 2.10 successfully on current TW? from which repo?
Hi, the version from the standard repos works for me on current TW ("20180827"): rpm -qa | grep gimp libgimp-2_0-0-2.10.4-1.2.x86_64 gimp-lang-2.10.4-1.2.noarch gimp-help-2.8.2-1.2.noarch gimp-2.10.4-1.2.x86_64 libgimpui-2_0-0-2.10.4-1.2.x86_64 gimp-plugins-python-2.10.4-1.2.x86_64 gimp-help-de-2.8.2-1.2.noarch gimp-plugin-aa-2.10.4-1.2.x86_64 Hendrik -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Hendrik Woltersdorf wrote:
the version from the standard repos works for me on current TW ("20180827"):
Indeed, seems 0827 is out now (though not yet announced). I had updated before, so I'm still on 0820. The gimp stuff is unchanged though, and I have the same now (downgraded) What graphics HW are you on? -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Am 28.08.2018 um 17:53 schrieb Peter Suetterlin:
Hendrik Woltersdorf wrote:
the version from the standard repos works for me on current TW ("20180827"):
Indeed, seems 0827 is out now (though not yet announced). I had updated before, so I'm still on 0820. The gimp stuff is unchanged though, and I have the same now (downgraded)
What graphics HW are you on?
intel processor graphics ("i915") Hendrik -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Dienstag, 28. August 2018 16:53:09 CEST Peter Suetterlin wrote:
Since this update gimp is no longer working for me!
With my previous version (TW 20180812) it still runs, when I start it now from a console it just hangs there until I press CTRL-C, then it repots a segfault:
woodstock:~% gimp ^CSegmentation fault (core dumped)
Try to generate a backtrace, either: sudo coredumpctl gdb gimp (gdb) thread apply all bt (gdb) quit or: gdb --args gimp (gdb) ... Regards, Stefan-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Thanks for the guides :) Brüns, Stefan wrote:
On Dienstag, 28. August 2018 16:53:09 CEST Peter Suetterlin wrote:
Since this update gimp is no longer working for me!
With my previous version (TW 20180812) it still runs, when I start it now from a console it just hangs there until I press CTRL-C, then it repots a segfault:
woodstock:~% gimp ^CSegmentation fault (core dumped)
Try to generate a backtrace, either:
sudo coredumpctl gdb gimp
Didn't have coredumpctl installed. After I did, it returned woodstock:~ # coredumpctl gdb gimp No match found.
(gdb) thread apply all bt (gdb) quit
So I did 'gdb gimp', then typed 'run' at the prompt, and when it hang pressed CRL-C to get back to gdb promt, and there typed the mentioned command http://paste.opensuse.org/92100830 I see all the cloned threads refer to openblas, and checking I noticed that the installed version here is from the Science repo, which recently did an update 0.2.20 -> 0.3.2. Is it safe to assume that this might be the problem? I'll try to downgrade to the TW version and see if that helps... -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Peter Suetterlin wrote:
I see all the cloned threads refer to openblas, and checking I noticed that the installed version here is from the Science repo, which recently did an update 0.2.20 -> 0.3.2. Is it safe to assume that this might be the problem? I'll try to downgrade to the TW version and see if that helps...
Indeed, that was the problem. Downgraded to the TW version (0.2.20), and gimp runs again. Sorry for the noise, and thanks for your support :D -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
participants (9)
-
Brüns, Stefan
-
Dominique Leuenberger
-
Dominique Leuenberger / DimStar
-
Felix Miata
-
Hendrik Woltersdorf
-
Ianseeks
-
Larry Finger
-
Patrick Shanahan
-
Peter Suetterlin