November 2016 - openSUSE Factory - openSUSE Mailing Lists

[opensuse-factory] Leap 42.2 - plasmashell freezing
by mh＠mike.franken.de 04 Dec '16

04 Dec '16

Hi *, on one of my machines (Lenovo T420 notebook) I have a problem with plasmashell freezing often when a notification is shown. The notification frame shows up, but no content and then the complete desktop freezes. Killing and restarting plasmashell cures the problem for a short time - til one of the the next notifications wants to display something. It doesn't happen for all notifications, though. Using tools like notify-send the problem can not be reproduced, but notifications stemming from plasma-nm and plasma-workspace itself (like the one for a removed plasmoid) always lead to the freeze. The system originally was openSuSE Leap 42.2, but because of the problem I upgraded step by step to - the latest kernel from the kernel stable repo, - the latest X server plus everyting from the X11:Xorg repo - and the latest plasma workspace including everything from the KDE:Framework5 repo. The problem remained unchanged, though. A few more facts: - The X server is xf86-video-intel. - Switching off the compositor doesn't help either. - Everything worked with Leap 42.1 - No according entry in the journal or .xsession-errors* can be found. - And a curiosity: After removing .config/plasmarc and restarting plasmashell the problem vanishes for a few hours or even a day, before it comes back. - Logging off or restarting the machine doesn't help in case the problems exists at that time. In found a few bug reports for plasma freezes, but none of them seems to fit exactly. Is this a known problem? Can I debug it and if so, how? TIA. Bye. Michael. -- Michael Hirmke -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

9 16

[opensuse-factory] Tumbleweed does not halt
by Michael Ströder 02 Dec '16

02 Dec '16

HI! On one laptop (of half a dozen) I've configured with Tumbleweed the system is hanging during shutdown, some process is massively accessing the hard-disk. Any hint where to search for this issue? Ciao, Michael.

4 11

[opensuse-factory] TW: systemd v228.16, dbus access problems
by mab 02 Dec '16

02 Dec '16

Hello, My system works fine with systemd-228-15.2. After upgrading to 228-16 (with systemd-sysvinit udev) the journal contains entries like: cron[16200]: pam_systemd(crond:session): Failed to connect to system bus: No such file or directory dbus[1257]: [system] Failed to activate service 'org.freedesktop.systemd1': timed out sddm-helper[16255]: pam_systemd(sddm:session): Failed to connect to system bus: No such file or directory A reboot results in several failed services (avahi, bluetooth, ModemManager, login-systemd, NetworkManager) , as far as I can see due to dbus access failure. Other programs, e.g. gpg (failed IPC call), are affected, too. systemd-logind[1254]: Failed to connect to system bus: No such file or directory dbus[1257]: [system] Failed to activate service 'org.freedesktop.PolicyKit1': timed outdbus[1257]: [system] Failed to activate service 'org.freedesktop.systemd1': timed out dbus[1257]: [system] Failed to activate service 'org.freedesktop.hostname1': timed out dbus[1257]: [system] Failed to activate service 'org.freedesktop.nm_dispatcher': timed out How to analyze that? Greetings mab KDE-Plasma-Version: 5.8.4 KDE-Frameworks-Version: 5.28.0 Qt-Version: 5.7.0 Kernel-Version: 4.8.10-1-default -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

1 1

[opensuse-factory] [RFH] Anyone wiling to give systemd v232 a try ?
by Franck Bui 30 Nov '16

30 Nov '16

Hey, Newest version of systemd v232 has been integrated and is mostly ready to land in Factory. It can be found here: https://build.opensuse.org/package/show/home:fbui:systemd:next:openSUSE-Fac… We already gave it some testing internally and it also ran over the weekend on my own laptop (which is still alive): so far, so good :) However my setup is quite boring without any fancy configs (LVM, DM, encryption, ...). So in case some of you want to give it a shot, you're more than welcome. However please note that it's still "experimental" material (or rather call it a release candidate, which is probably a more appropriate wording) so make sure to test it on a testing/spare system only... A couple things that might be worth to be noted: - Make sure to use the latest version of dracut first. It should include the following change: * Tue Nov 08 2016 daniel(a)molkentin.de - systemd-initrd: Add initrd-root-device.target. Cherry-pick to get systemd v230 into factory (bsc1009089) * add 0451-systemd-initrd-add-initrd-root-device.target.patch - For those who rely on wicked: systemd is now making sure that local users are logged out before the network is shut down when the system goes down (commit 8c856804780681e). The consequence of this is that user can log in only after the network.target is activated. But for some reasons, wicked takes a while to do so (~15 secs), so you'll see a long delay before being able to log in. For now I don't know why wicked takes so long time, maybe that was already reported or discussed in the past... - The service that flushes the journal during boot looks to be stucked when the debug logs are enabled. I'll try to debug this but that shouldn't affect you for regular boot. - Here I could have noted a faster boot: 2 secs less spents in userspace :) Thanks ! -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

17 36

[opensuse-factory] too much failures during reboot
by Constant Brouerius van Nidek 30 Nov '16

30 Nov '16

My system does not work as expected. Have looked into hardware problems and memory, but did not find anything up to now Did a new install and although in the begin it worked quit well I had some system freezes. Started to look into journalctl and found quit a lot failed results. e.g. failed to start Flush Journal to Persistent Storage. No idea what that means but it does not sound good. Failed to start login service and cups scheduler where some others. I have copied some pieces of the end of the journalctl. What is wrong with computer or its software. Why a whole bunch of failures and where to start working on the system. ----------------------------------- Nov 25 12:22:16 linux-c8ur kernel: XFS (sda5): Starting recovery (logdev: internal) Nov 25 12:22:16 linux-c8ur kernel: XFS (sda5): Metadata corruption detected at __write_verify+0xd0/0xe0 [xfs], xfs_dir3_leaf1 block 0xea5a00 Nov 25 12:22:16 linux-c8ur kernel: XFS (sda5): Unmount and run xfs_repair Nov 25 12:22:16 linux-c8ur kernel: XFS (sda5): First 64 bytes of corrupted metadata buffer: Nov 25 12:22:16 linux-c8ur kernel: ffff96e8ff161000: 00 00 00 00 00 00 00 00 3d f1 00 00 df bc 03 ec ........=....... Nov 25 12:22:17 linux-c8ur kernel: ffff96e8ff161010: 00 00 00 00 00 ea 5a 00 00 00 07 9c 00 00 20 c5 ......Z....... . Nov 25 12:22:17 linux-c8ur kernel: ffff96e8ff161020: 57 d3 e4 b0 b3 94 44 28 92 6c d5 8d 3c 0f cb 6a W.....D(.l..<..j Nov 25 12:22:17 linux-c8ur kernel: ffff96e8ff161030: 00 00 00 00 01 00 00 60 00 96 00 05 00 00 00 00 .......`........ Nov 25 12:22:17 linux-c8ur kernel: XFS (sda5): xfs_do_force_shutdown(0x8) called from line 1322 of file ../fs/xfs/xfs_buf.c. Return address = 0xffffffffc0832d55 Nov 25 12:22:17 linux-c8ur kernel: XFS (sda5): Corruption of in-memory data detected. Shutting down filesystem Nov 25 12:22:17 linux-c8ur kernel: XFS (sda5): Please umount the filesystem and rectify the problem(s) Nov 25 12:22:18 linux-c8ur kernel: XFS (sda5): log mount/recovery failed: error -117 Nov 25 12:22:18 linux-c8ur kernel: XFS (sda5): log mount failed Nov 28 06:30:30 linux-c8ur mtp-probe[7085]: bus: 2, device: 104 was not an MTP device Nov 28 06:30:31 linux-c8ur systemd-logind[7079]: Failed to enable subscription: Connection timed out Nov 28 06:30:31 linux-c8ur dbus[1026]: [system] Failed to activate service 'org.freedesktop.systemd1': timed out Nov 28 06:30:31 linux-c8ur systemd-logind[7079]: Failed to fully start up daemon: Connection timed out Nov 28 06:30:31 linux-c8ur systemd[1]: systemd-logind.service: Main process exited, code=exited, status=1/FAILURE Nov 28 06:30:31 linux-c8ur systemd[1]: Failed to start Login Service. -- Subject: Unit systemd-logind.service has failed -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit systemd-logind.service has failed. -- -- The result is failed. Nov 28 06:30:31 linux-c8ur systemd[1]: systemd-logind.service: Unit entered failed state. Nov 28 06:30:31 linux-c8ur systemd[1]: systemd-logind.service: Failed with result 'exit-code'. Nov 28 06:30:31 linux-c8ur systemd[1]: systemd-logind.service: Service has no hold-off time, scheduling restart. Nov 28 06:30:31 linux-c8ur systemd[1]: Stopped Login Service. -- Subject: Unit systemd-logind.service has finished shutting down -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit systemd-logind.service has finished shutting down. Nov 28 06:30:31 linux-c8ur systemd[1]: Starting Login Service... -- Subject: Unit systemd-logind.service has begun start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit systemd-logind.service has begun starting up. Nov 28 06:30:56 linux-c8ur systemd-logind[7090]: Failed to enable subscription: Connection timed out Nov 28 06:30:56 linux-c8ur systemd-logind[7090]: Failed to fully start up daemon: Connection timed out Nov 28 06:30:56 linux-c8ur systemd[1]: systemd-logind.service: Main process exited, code=exited, status=1/FAILURE Nov 28 06:30:56 linux-c8ur systemd[1]: Failed to start Login Service. -- Subject: Unit systemd-logind.service has failed -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit systemd-logind.service has failed. -- -- The result is failed. Nov 28 06:30:56 linux-c8ur systemd[1]: systemd-logind.service: Unit entered failed state. Nov 28 06:30:56 linux-c8ur systemd[1]: systemd-logind.service: Failed with result 'exit-code'. Nov 28 06:30:56 linux-c8ur systemd[1]: systemd-logind.service: Service has no hold-off time, scheduling restart. Failed to get journal fields: Bad message -- opensuse:tumbleweed:20161123 Qt: 5.7.0 KDE Frameworks: 5.28.0 kf5-config: 1.0 KDE Plasma: 5.8.3 Kernel: 4.8.9-1-default Linux User 183145 working on a Pentium IV . -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

4 3

[opensuse-factory] zypper dup from 42.1 to 42.2 pulls Mesa on headless VM
by Thomas Wagner 30 Nov '16

30 Nov '16

Hi, I have a headless virtual machine (just apache running and i connect via ssh) with Leap 42.1. Thus no Mesa or X installed. This maschine I wanted to upgrade to Leap 42.2. So, I replaced the 42.1 repos with the repos for 42.2. However, a "zypper dup --no-recommends" tries to pull Mesa with quite some other graphic related libX* and libdrm* packages. I dug around a bit and IMHO python-gobject has now a dependency on all the graphic stuff. On the other hand snapper-zypp-plugin needs python-gobject. At the opensuse mailinglist I was told two things. Firstly, maybe a change in libcairo might be the reason for an indirect requirement on Mesa. Secondly, the people on opensuse-factory might be able to help. Now my question: How to upgrade from 42.1 to 42.2 without installing Mesa but keep snapper? Best regards Thomas -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

2 3

[opensuse-factory] New Tumbleweed snapshot 20161128 released!
by Dominique Leuenberger 30 Nov '16

30 Nov '16

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: bash dleyna-server file (5.28 -> 5.29) krb5 krusader lftp (4.7.3 -> 4.7.4) mlterm (3.7.0 -> 3.7.2) mutt sddm (0.13.0 -> 0.14.0) timezone (2016i -> 2016j) timezone-java (2016i -> 2016j) wine (1.9.23 -> 1.9.24) ypserv === Details === ==== bash ==== Subpackages: bash-doc libreadline7 readline-devel readline-doc - Add upstream patch bash44-001 Bash-4.4 changed the way the history list is initially allocated to reduce the number of reallocations and copies. Users who set HISTSIZE to a very large number to essentially unlimit the size of the history list will get memory allocation errors - Add upstream patch bash44-002 Bash-4.4 warns when discarding NUL bytes in command substitution output instead of silently dropping them. This patch changes the warnings from one per NUL byte encountered to one warning per command substitution. - Drop no-null-warning.patch as bash44-002 is official replacement - Add upstream patch bash44-003 Specially-crafted input, in this case an incomplete pathname expansion bracket expression containing an invalid collating symbol, can cause the shell to crash. - Add upstream patch bash44-004 There is a race condition that can result in bash referencing freed memory when freeing data associated with the last process substitution. - Add upstream patch bash44-005 Under certain circumstances, a simple command is optimized to eliminate a fork, resulting in an EXIT trap not being executed. (boo#1008459) - Add upstream patch readline70-001 Readline-7.0 changed the way the history list is initially allocated to reduce the number of reallocations and copies. Users who set the readline history-size variable to a very large number to essentially unlimit the size of the history list will get memory allocation errors ==== dleyna-server ==== - Add dleyna-server-includes.patch: include the right headers to be able to compile against up-to-date gupnp stack (gh#01org/dleyna-server#159). ==== file ==== Version update (5.28 -> 5.29) Subpackages: file-devel file-magic libmagic1 libmagic1-32bit - Update to file version 5.29 * der getlength overflow (Jonas Wagner) * multiple magic file load failure (Christoph Biedl) * CDF parsing improvements (Guy Helmer) * Add support for signed indirect offsets * cat /dev/null | file - should print empty (Christoph Biedl) * Bump string size from 64 to 96. * PR/556: Fix separators on annotations. - Remove patch file-5.28-compress.patch now upstream - Rename patch file-5.28.dif which becomes now file-5.29.dif ==== krb5 ==== Subpackages: krb5-32bit krb5-client krb5-devel - add pam configuration file required for ksu just use a copy of "su" one from Tumbleweed ==== krusader ==== Subpackages: kio_iso - Add Remove-non-archive-mimetypes-from-krarc-archive-mime-type-list.patch to fix dolphin opening e.g. LibreOffice files as archives (boo#1011320, kde#371765) ==== lftp ==== Version update (4.7.3 -> 4.7.4) - lftp 4.7.4: * mirror: new option --directory (-F) for source directories glob pattern. * mirror: fixed coredump with --depth-first + --recursion=newer. * mirror: create inaccessible directories anyway. * pget, torrent: avoid long delays in posix_fallocate(3) call. * new setting dns:name for host aliases. * ftp: allow SSL after certain types of ftp proxy. * http: fixed interpretation of links without a protocol. * cls: fixed glob metacharacter unquoting. * sftp: fixed mirroring of files with a leading tilde. * fixed transfer logging. ==== mlterm ==== Version update (3.7.0 -> 3.7.2) - updated to 3.7.2 * Add mlterm-con which is a console version of mlterm (like GNU Screen) and which works on various terminal emulators. (see doc/en/README.console) * Add "console_encoding" / --ckm option which specifies a character encoding of the console where mlterm-con works. * Add "default_cell_size" / --csz option for mlterm-con. * Add "console_sixel_colors" / --csc option for mlterm-con. * Add "primary_da" / --da1 and "secondary_da" / --da2 options. * Support DECRQSS partially. * Support wheel mouse on MacOSX/Cocoa. (Thanks to @nyarla) (Merge a patch at http://the.nyarla.net/entry/2016/06/03/195013) * Bug fixes: Fix misalignment of the position of characters in drawing them with the use of complementary loaded fonts on cairo. - removed mlterm-noreturn.patch (upstreamed) ==== mutt ==== - Add patch mutt-1.6.2-gpgme_set_sender.patch that is avoid name space clash with gpgme_set_sender() from gpgme - Rename patch mutt-1.5.23-cariage-return.path to mutt-1.5.23-carriage-return.path - Extend patch mutt-1.5.23-carriage-return.path Be sure that also signed messages from Android can be verified by gpgme interface of mutt ==== sddm ==== Version update (0.13.0 -> 0.14.0) Subpackages: sddm-branding-openSUSE - Fix %post and %postun of branding subpackages - Add various bugfixes from develop branch: * 0001-Fix-display-of-user-avatars.-684.patch * 0002-Add-a-config-option-to-enable-high-DPI-scaling-701.patch * 0003-elarun-Update-date-and-time.patch * 0004-Support-Non-Latin-characters-in-theme-settings-708.patch * 0005-Cleanup-dangling-pointer-in-SocketServer-725.patch - Sync with KDE:Frameworks5:LTS, sort sddm.changes - Remove 0001-Fall-back-to-regular-login-when-autologin-fails.patch ==== timezone ==== Version update (2016i -> 2016j) - timezone update 2016j [bsc#1011797]: * Saratov, Russia switches from +03 to +04 on 2016-12-04 at 02:00. (new zone Europe/Saratov split from Europe/Volgograd) * 1994-1999 corrections for Kazakhstan, with new zone Asia/Atyrau * Asia/Gaza and Asia/Hebron now use "EEST", not "EET", to denote summer time before 1948. The old use of "EET" was a typo. ==== timezone-java ==== Version update (2016i -> 2016j) - timezone update 2016j [bsc#1011797]: * Saratov, Russia switches from +03 to +04 on 2016-12-04 at 02:00. (new zone Europe/Saratov split from Europe/Volgograd) * 1994-1999 corrections for Kazakhstan, with new zone Asia/Atyrau * Asia/Gaza and Asia/Hebron now use "EEST", not "EET", to denote summer time before 1948. The old use of "EET" was a typo. ==== wine ==== Version update (1.9.23 -> 1.9.24) Subpackages: wine-32bit - Updated to 1.9.24 development snapshot - Support for unordered access views in Direct3D. - Many fixes in the regression tests. - Some more improvements in HID support. - Various bug fixes. - updated winetricks - downgrade requires of cabextract and unzip to recommends, so we can use 32bit wine during build on reduced 32bit package sets. ==== ypserv ==== - add 0001-use-_PATH_VARRUN-from-paths.h.patch [bnc#1011483] -- 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] calibre does no longer work on tumbleweed
by Kyek, Andreas, Vodafone DE 29 Nov '16

29 Nov '16

Hi, since a few days calibre does no longer work here on my Tumblewee machine. Starting as user gives: t510w:~> calibre python2: siplib.c:12299: sipEnumType_alloc: Zusicherung »sipTypeIsEnum(currentType)« nicht erfüllt. Abgebrochen (Speicherabzug geschrieben) while starting as root gives some more information: t510w:~ # calibre Traceback (most recent call last): File "/usr/bin/calibre", line 20, in <module> sys.exit(calibre()) File "/usr/lib64/calibre/calibre/gui_launch.py", line 69, in calibre main(args) File "/usr/lib64/calibre/calibre/gui2/main.py", line 533, in main app, opts, args = init_qt(args) File "/usr/lib64/calibre/calibre/gui2/main.py", line 104, in init_qt app = Application(args, override_program_name=override) File "/usr/lib64/calibre/calibre/gui2/__init__.py", line 962, in __init__ self.load_calibre_style() File "/usr/lib64/calibre/calibre/gui2/__init__.py", line 1074, in load_calibre_style self.pi.load_style(icon_map) TypeError: a dict value has type 'unicode' but 'QString' is expected Since I'm not a python expert I've no idea what needs to be checked. System is a Lenovo t510 laptop with tumbleweed, packman, x2go and Bumblebee repo enabled. All updates done. Calibre 2.71.0-1.1 is installed in 64bit version from standard repo. Any ideas? Andreas -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

4 7

[opensuse-factory] docker cannot be installed
by Kyek, Andreas, Vodafone DE 29 Nov '16

29 Nov '16

Hi @all, is there a known problem with docker now on tumbleweed? :~ # zypper in docker Loading repository data... Reading installed packages... Resolving package dependencies... Problem: nothing provides containerd = 0.2.4+git0366d7e needed by docker-1.12.3-1.2.X86_64 Solution 1: do not install docker-1.12.3-1.2.X86_64 Solution 2: break docker-1.12.3-1.2.X86_64 by ignoring some of its depencies Choose from above solutions by number or cancel [1/2/c] (c): "zypper se -s containerd" shows a version 0.2.4+gitr565_0366d7e-1.1 So is it just a naming problem in versioning? Or is something missing? (I already had docker installed a while ago and installation was fine) (all version are from standard repo!) Andreas -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

4 3

[opensuse-factory] TW: the command "mount"
by ellanios82 29 Nov '16

29 Nov '16

TW : under kernel-default-4.8.10-1.1.x86_64 command "mount" sometimes fails [without leaving dmesg trace] ........ regards -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

4 6