October 2017 - openSUSE Factory - openSUSE Mailing Lists

[opensuse-factory] Leap 42.3 - python3-pymongo for ARM is broken
by Axel Braun 24 Oct '17

24 Oct '17

Hi, I noticed during an update on a RasPi that no python3-pymongo is available for Leap on ARM (aarch64). On x86 it is working. Latest (singlespec) version in Factory is disabled for ports, in d:l:p it builds. Is there a plan to get it building against Leap 42.3 on ARM? Thanks Axel -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

1 0

Fwd: [opensuse-factory] Bigs problems with Intel gpu driver i915 and kernel 4.12 and 4.13
by Ivan Linty 24 Oct '17

24 Oct '17

Hi. desktop is kde 5.11 and displaymanager is kdm 2017-10-20 23:40 GMT+02:00 Fraser_Bell <Fraser_Bell(a)opensuse.org>: > On 10/20/2017 06:12 AM, Ivan Linty wrote: >> >> Hi >> >> My system after last upgrade to kernel 4.13-4.12 presents sudden >> random crashes ! >> No mouse, no disk activity, no network activity. The system is completly >> stuck! >> The only solution is a hard reboot. >> No errors are recorded in systemd journal. >> The problem appears randomly after a variable time, sometimes 5/10 >> minutes, sometimes a hour, but as You can think, is very boring!!! >> >> I have found in google some threaths about similar problems: >> >> https://bugs.archlinux.org/task/55629 >> >> but for me the solution intel_iommu=igfx_off does not work! >> >> A fix is to disable hardware accelleration with nomodeset, >> >> Another fix is to revert to kernel 4.9 (4.9.54-2-pf). >> >> With kernel 4.9 no more hangs and hardware accelleration works like a >> charm!!! I test with chrome and web google earth!!!! >> >> Can someone of opensuse report this to kernel mainteners or Intel >> driver mainteners ??? >> >> Kind Regards >> > > What desktop are you using? > What Display Manager are you using? > > Did you try switching either? > > -- > -Gerry Makaro > aka Fraser_Bell on the forums, IRC, and mail at openSUSE.org > -- > To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org > To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org > -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

3 3

[opensuse-factory] vlock no longer working after recent snapshots
by Chan Ju Ping 23 Oct '17

23 Oct '17

After switching to tty1, I ran zypper dup in tmux and after detaching the session, ran vlock, which resulted in a repeated scrolling "authentication failure" text, with no ability to input my password. The problem is still persisting after running zypper dup today. Can anyone else confirm?

3 9

[opensuse-factory] openjfx for SUSE
by Bernhard Donaubauer 23 Oct '17

23 Oct '17

Hello, I am a Java programmer and I want to try JFX. But there is no openjfx package for SUSE available, so one have to install Oracle JRE. It would be nice if SUSE could provide such a package. Regards, Bernhard Donaubauer -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

2 1

[opensuse-factory] ignoring comments
by Boris Manojlovic 22 Oct '17

22 Oct '17

can someone explain this behavior to me? am i invisible? https://build.opensuse.org/request/show/535581 https://build.opensuse.org/request/show/528850 -- Invisible man -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

6 11

[opensuse-factory] New Tumbleweed snapshot 20171019 released!
by Dominique Leuenberger 21 Oct '17

21 Oct '17

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&versio… When you reply to report some issues, make sure to change the subject. It is not helpful to keep the release announcement subject in a thread while discussing a specific problem. Packages changed: Mesa libguestfs libstorage (2.26.12 -> 2.26.13) llvm llvm4 notmuch (0.25 -> 0.25.1) xdg-desktop-portal-kde (5.11.0 -> 5.11.1) yast2-ntp-client (3.3.3 -> 4.0.0) yast2-services-manager (3.3.1 -> 4.0.1) yast2-vm (3.2.2 -> 3.2.3) === Details === ==== Mesa ==== Subpackages: Mesa-dri-devel Mesa-libEGL-devel Mesa-libEGL1 Mesa-libGL-devel Mesa-libGL1 Mesa-libglapi0 Mesa-libva libgbm1 libvdpau_r300 libvdpau_r600 libvdpau_radeonsi libvulkan_radeon libwayland-egl1 libxatracker2 - U_configure.ac-rework-llvm-libs-handling-for-3.9.patch * llvm-config 3.9 and higher works properly, use its values instead of guessing. Fixes build against llvm built as single shared library. - svga is x86-only - u_svga-Fix-build-on-ppc64le.patch: Remove - Add build dependency on clang-devel-static. * Required with new llvm4 build mode (bnc#1049703). * Also rename dependency llvm-clang-devel to clang-devel. The llvm-clang-devel is old name kept around for compatibility. ==== libguestfs ==== Subpackages: guestfs-data libguestfs0 python3-libguestfs - Use "OCaml" in RPM group exactly as all other packages do. ==== libstorage ==== Version update (2.26.12 -> 2.26.13) Subpackages: libstorage-ruby libstorage7 - Don't discard the internally stored volume label before it is applied (bsc#1061850) - 2.26.13 ==== llvm ==== - Add clang-devel-static package. * Requires clang4-devel-static that was added to llvm4 package. ==== llvm4 ==== Subpackages: clang4 libLLVM4 libLTO4 libc++-devel libc++1 libc++abi-devel libc++abi1 libclang4 libomp4-devel - llvm-normally-versioned-libllvm.patch * Change libLLVM naming scheme to match our naming guidelines. * The reasons for the original naming scheme are no longer valid, more details in the patch. - Disable all thread related tests in libcxx. Many of them use timeouts to detect failure. They can fail randomly if the machine is under heavy load (happens often in OBS). - Drop llvm4-devel-static. llvm4-devel contains shared library with the same content. - Use LLVM_BUILD_LLVM_DYLIB instead of BUILD_SHARED_LIBS to build single libLLVM library. This is the recommended way. The old way was causing various issues. * llvm-split-static-library-exports-into-their-own-export-file.diff * clang-split-static-library-exports-into-their-own-export-file.diff (bnc#1049703) - Add lld, linker for Clang/LLVM (sr#517692) - Include clang++-MAJOR.MINOR symbolic link (bnc#1012260) - Remove unnecessary dependency on flex and bison. - Make sure all binaries are managed by update-alternatives - Add llvm-add_a_LLVM_USE_LINKER.patch and link using gold to prevent memory exhaustion on some build machines. - Reduce debuginfo on x86 architecture. LLVM libraries are so big that they exhaust all memory on 32 bit machine if linked with full debuginfo. - Speed up build by skipping parts that are not required in stage1. - Build lldb in-tree as one of the llvm tools. ==== notmuch ==== Version update (0.25 -> 0.25.1) - update to 0.25.1 - disable handling x-display in text/enriched messages ==== xdg-desktop-portal-kde ==== Version update (5.11.0 -> 5.11.1) Subpackages: xdg-desktop-portal-kde-lang - Update to 5.11.1 * New bugfix release * For more details please see: * https://www.kde.org/announcements/plasma-5.11.1.php - Changes since 5.11.0: * None ==== yast2-ntp-client ==== Version update (3.3.3 -> 4.0.0) - Avoid Internal Error during AutoYaST cloning when fudge records are present (bsc#1058510) - 4.0.0 ==== yast2-services-manager ==== Version update (3.3.1 -> 4.0.1) - respect target level specified in control file (bsc#1063216) - 4.0.1 - Use fewer calls of systemctl to speed up startup (bsc#1045658) - 4.0.0 ==== yast2-vm ==== Version update (3.2.2 -> 3.2.3) - use new pattern name for SLES (same as TW) - Remove SLED as this is no more needed - BSC#1055459 - 3.2.3 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

1 0

[opensuse-factory] Bigs problems with Intel gpu driver i915 and kernel 4.12 and 4.13
by Ivan Linty 20 Oct '17

20 Oct '17

Hi My system after last upgrade to kernel 4.13-4.12 presents sudden random crashes ! No mouse, no disk activity, no network activity. The system is completly stuck! The only solution is a hard reboot. No errors are recorded in systemd journal. The problem appears randomly after a variable time, sometimes 5/10 minutes, sometimes a hour, but as You can think, is very boring!!! I have found in google some threaths about similar problems: https://bugs.archlinux.org/task/55629 but for me the solution intel_iommu=igfx_off does not work! A fix is to disable hardware accelleration with nomodeset, Another fix is to revert to kernel 4.9 (4.9.54-2-pf). With kernel 4.9 no more hangs and hardware accelleration works like a charm!!! I test with chrome and web google earth!!!! Can someone of opensuse report this to kernel mainteners or Intel driver mainteners ??? Kind Regards -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

2 1

[opensuse-factory] nvidia and kernel 4.13 from obs:/Kernel:/stable/standard
by Werner Flamme 20 Oct '17

20 Oct '17

Hi, I'm wondering why I don't get the combination of kernel 4.13 and the proprietary nVidia driver to work. I also have installed a 4.12 kernel from that obs repo, and the nvidia installer runs nicely and everything works fine. When booting into a kernel 4.13, I only have a flickering startup screen - there is no graphical display, but the system obviously tries to show it, falls back to the command line, tries graphical mode again and so on. The switching is so fast that I can't even use Strg-Alt-F3 to enter a console... Only rebooting into a kernel 4.12 helps. What am I missing? Last thing I did was setting the default runlevel to "multi-user" instead of "graphical". I'll try to get useful messages at least. Currently I can only presume that kernel 4.13 handles the hardware in an way that is incompatible to the way 4.12 does, but I have no clue how to get around this. Next thing is that I'm going to (re-)install the nvidia driver when running a 4.13 in text mode. Anyone here who can help me, please? What should I look for? Werner --

3 4

Fwd: [opensuse-factory] failed to unmount /home, /var/tmp, /tmp at shutdown
by Ivan Linty 20 Oct '17

20 Oct '17

Hi Ian here the log: journalctl --since=13:40:49 Oct 17 13:40:49 linux-q5nf systemd[1]: Stopped target Local File Systems. Oct 17 13:40:49 linux-q5nf systemd[1]: Unmounting /tmp... Oct 17 13:40:49 linux-q5nf systemd[1]: Unmounting /sda2... Oct 17 13:40:49 linux-q5nf systemd[1]: Unmounting /home... Oct 17 13:40:49 linux-q5nf systemd[1]: Unmounting /var/tmp... Oct 17 13:40:49 linux-q5nf systemd[1]: tmp.mount: Mount process exited, code=exited status=32 Oct 17 13:40:49 linux-q5nf systemd[1]: Failed unmounting /tmp. Oct 17 13:40:49 linux-q5nf systemd[1]: sda2.mount: Mount process exited, code=exited status=32 Oct 17 13:40:49 linux-q5nf systemd[1]: Failed unmounting /sda2. Oct 17 13:40:49 linux-q5nf systemd[1]: Stopped File System Check on /dev/disk/by-id/ata-ST500DM002-1SB10A_ZA4315ME-part1. Oct 17 13:40:49 linux-q5nf systemd[1]: home.mount: Mount process exited, code=exited status=32 Oct 17 13:40:49 linux-q5nf systemd[1]: Failed unmounting /home. Oct 17 13:40:49 linux-q5nf systemd[1]: Stopped File System Check on /dev/disk/by-id/ata-ST500DM002-1SB10A_ZA4315ME-part2. Oct 17 13:40:49 linux-q5nf systemd[1]: Removed slice system-systemd\x2dfsck.slice. Oct 17 13:40:49 linux-q5nf systemd[1]: Unmounted /var/tmp. Oct 17 13:40:49 linux-q5nf systemd[1]: Reached target Unmount All Filesystems. ---------------------------------- Here my etc/fstab: /dev/disk/by-id/ata-ST500DM002-1SB10A_ZA4315ME-part3 swap swap defaults 0 0 /dev/disk/by-id/ata-SanDisk_SDSSDRC032G_123360400662-part1 / ext4 acl,user_xattr,noatime,async,commit=100 1 1 /dev/disk/by-id/ata-ST500DM002-1SB10A_ZA4315ME-part2 /home ext4 acl,user_xattr,noatime,async,commit=100 1 2 /dev/disk/by-id/ata-ST500DM002-1SB10A_ZA4315ME-part1 /sda2 ext4 acl,user_xattr,noatime,async,commit=100 1 2 proc /proc proc defaults 0 0 sysfs /sys sysfs noauto 0 0 debugfs /sys/kernel/debug debugfs noauto 0 0 usbfs /proc/bus/usb usbfs noauto 0 0 devpts /dev/pts devpts mode=0620,gid=5 0 0 tmpfs /tmp tmpfs nodev,nosuid,noexec,mode=1777 0 0 tmpfs /var/tmp tmpfs nodev,nosuid,noexec,mode=1777 0 0 ---------------------------------- kernel is: Linux linux-q5nf 4.13.5-1-default #1 SMP PREEMPT Thu Oct 5 18:28:26 UTC 2017 (3fd9659) x86_64 x86_64 x86_64 GNU/Linux ---------------------------------- cat /proc/cmdline: BOOT_IMAGE=/boot/vmlinuz-4.13.5-1-default root=UUID=df066082-7a21-466d-bd6a-8a5c94fd5750 resume=/dev/disk/by-id/ata-ST500DM002-1SB10A_ZA4315ME-part3 plymouth.enable=0 i915.semaphores=1 splash=0 showopts scsi_mod.use_blk_mq=1 elevator=bfq ---------------------------------- the first disk is a SDD 32GB samsung where I have put / the second is a SATA 500GB where are /home /sda2 and swap space ---------------------------------- fdisk /dev/sdb (32 GB SSD): Welcome to fdisk (util-linux 2.30.1). Changes will remain in memory only, until you decide to write them. Be careful before using the write command. Command (m for help): p Disk /dev/sdb: 29.8 GiB, 32017047552 bytes, 62533296 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0x00087009 Device Boot Start End Sectors Size Id Type /dev/sdb1 * 2048 62533295 62531248 29.8G 83 Linux Command (m for help): q ---------------------------------- fdisk /dev/sda (500 GB): Welcome to fdisk (util-linux 2.30.1). Changes will remain in memory only, until you decide to write them. Be careful before using the write command. Command (m for help): p Disk /dev/sda: 465.8 GiB, 500107862016 bytes, 976773168 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disklabel type: dos Disk identifier: 0xbbd05cf6 Device Boot Start End Sectors Size Id Type /dev/sda1 2048 41945087 41943040 20G 83 Linux /dev/sda2 41945088 964691967 922746880 440G 83 Linux /dev/sda3 964691968 976773167 12081200 5.8G 82 Linux swap / Solaris ---------------------------------- /opt /usr/src /var/log /var/spool are links (ln -s) to: ilinty@linux-q5nf:/sda2> ll /opt lrwxrwxrwx 1 root root 9 11 ago 14.37 /opt -> /sda2/opt ilinty@linux-q5nf:/sda2> ll /usr/src lrwxrwxrwx 1 root root 10 16 ott 11.00 /usr/src -> /sda2/src/ ilinty@linux-q5nf:/sda2> ll /var/log lrwxrwxrwx 1 root root 14 16 ott 10.56 /var/log -> /sda2/var/log/ ilinty@linux-q5nf:/sda2> ll /var/spool lrwxrwxrwx 1 root root 16 16 ott 10.56 /var/spool -> /sda2/var/spool/ to save space and writes on the SDD disk ... 2017-10-17 10:48 GMT+02:00 ianseeks <bingmybong(a)btinternet.com>: > On Tuesday, 17 October 2017 08:08:28 BST Ivan Linty wrote: >> Hello >> >> Someone can help me ? >> After the latest updates, I have noticed the following errors at shutdown: >> >> failed to unmount /home >> failed to unmount /var/tmp >> failed to unmount /tmp >> >> etc... >> that change randomly... >> >> >> (my system is opensuse tumbleweed 20171010) >> >> Kind Regards >> > > It might help if you can post more information about the errors i.e. Cut and paste the lines from the journal where you are getting this information from so it includes any error codes etc. > > -- > opensuse:tumbleweed:20171010 > Qt: 5.9.1 > KDE Frameworks: 5.38.0 > KDE Plasma: 5.11.0 > kwin 5.11.0 > kmail2 5.6.1 > akonadiserver 5.6.1 > Kernel: 4.13.5-1-default > Nouveau: 1.0.15_1.2 > > -- > To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org > To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org > -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

2 2

Re: [opensuse-factory] bug 1022830 GTK3 apps not honoring system-wide DPI settings
by Felix Miata 20 Oct '17

20 Oct '17

Felix Miata composed on 2017-09-04 19:48 (UTC-0400): > https://build.opensuse.org/request/show/510082 (declined) > GTK3 apps not honoring system-wide DPI settings nor KDE mouse cursor > https://bugzilla.opensuse.org/show_bug.cgi?id=1022830 > What's going on with this? I don't know how to interpret the many lnussel > entries in the request history. Is someone trying to push Lars' proposed fix > upstream instead of carrying an openSUSE patch? If yes, where is its discussion > to be found? Fixes have been provided in updated rpms for Leap and SLE, but not TW. Is another bug needed for getting this fixed for TW? -- "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(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

17 28