openSUSE Factory April 2017

factory@lists.opensuse.org

160 participants
118 discussions

[opensuse-factory] IBus daemon not running after the system wakes up from Suspend mode in Plasma desktop
by René Krell 30 Apr '17

30 Apr '17

Hi all, In Plasma/KDE, I have had repeatedly the problem, that no keyboard input has been possible in a open yakuake terminal after the laptop lid has been close (Suspend mode) and reopened. I figured out that this can be recovered by starting the IBus daemon from start menu, which opens first a dialog window "The IBus daemon is not running. Do you wish to start it?". After confirming the keyboard input is possible again. What is the default behavior, is it intended to automatically start the IBus daemon with logging in? I had to hide its icon in the sys tray, otherwise I got two language icons for switching the keyboard layout, one from IBus daemon and one from KDE. What is the desired behavior here, is IBus daemon necessary to come up with the system and why are there two icons? Is this a Plasma problem or just a misconfiguration? René -- 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] kmail duplicates and crash problem
by Constant Brouerius van Nidek 30 Apr '17

30 Apr '17

Got the impression that the problems with dups and crashes were solved. As I had a perfect working Kmail for more than a month after I got the hint that removing the automatic filter use from the filter configuration and doing the filtering of emails manual only, I thought it was time to sniff out if the problems are gone. Within half an hour I had four duplicates and a crash as usual. Was I wrong that the problem was solved or did I miss some instruction during the updates of the past. For now it is back to manual filtering of my pop email accounts. -- opensuse:tumbleweed:20170424 Qt: 5.7.1 KDE Frameworks: 5.32.0 kf5-config: 1.0 KDE Plasma: 5.9.4 plasmashell 5.9.4 Kernel: 4.10.10-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

6 6

[opensuse-factory] New Tumbleweed snapshot 20170425 released!
by Dominique Leuenberger 29 Apr '17

29 Apr '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 (17.0.3 -> 17.0.4) autoyast2 (3.2.13 -> 3.2.14) bc (1.06.95 -> 1.07.1) binutils device-mapper (1.02.137 -> 1.02.139) dracut elfutils gawk glibc glibc libarchive (3.2.2 -> 3.3.1) libserf libzypp (16.6.1 -> 16.8.0) llvm4 lockdev lvm2 (2.02.168 -> 2.02.170) lzo (2.09 -> 2.10) open-iscsi opie perl-XML-Simple (2.22 -> 2.24) perl-libwww-perl (6.25 -> 6.26) rubygem-cfa_grub2 (0.6.1 -> 0.6.2) samba (4.6.2 -> 4.6.2+git.19.c267455e57b) sysconfig (0.84.0 -> 0.84.1) systemd util-linux (2.29.1 -> 2.29.2) util-linux-systemd (2.29.1 -> 2.29.2) vim (8.0.324 -> 8.0.566) yast2 (3.2.27 -> 3.2.28) yast2-bootloader (3.2.18 -> 3.2.19) yast2-update (3.2.0 -> 3.2.2) zypper (1.13.22 -> 1.13.24) === Details === ==== Mesa ==== Version update (17.0.3 -> 17.0.4) Subpackages: Mesa-dri-devel Mesa-dri-nouveau Mesa-libEGL-devel Mesa-libEGL1 Mesa-libGL-devel Mesa-libGL1 Mesa-libglapi0 Mesa-libglapi0-32bit Mesa-libva libOSMesa8 libOSMesa8-32bit libgbm1 libvdpau_nouveau libvdpau_r300 libvdpau_r600 libvdpau_radeonsi libvulkan_intel libvulkan_radeon libwayland-egl1 libxatracker2 - let Mesa require Mesa-libEGL1 for a libglvnd build; xf86-video-amdgpu driver needs it for 2D support via glamor (boo#1034832) - Add u_add_llvm_codegen_dependencies.patch to link to libLLVMCodegen to fix cyclic linking problems. bsc#981975 - Enable OpenCL for aarch64, ppc64 and ppc64le now, too. %arm is still left out, waiting for llvm4 to build. - update to 17.0.4 * fdo#100391 - SachaWillems deferredmultisampling asserts * fdo#100452 - push_constants host memory leak when resetting command buffer * fdo#100582 - piglit.spec.arb_stencil_texturing.glblitframebuffer corrupts state.gl_texture* assertions * radeonsi: add new polaris10 pci ids * fixes for anv, radv, i965 and nouveau drivers ==== autoyast2 ==== Version update (3.2.13 -> 3.2.14) Subpackages: autoyast2-installation - Moved configuration management before software selection in order to select packages which are needed for CM. (FATE#319830) - 3.2.14 ==== bc ==== Version update (1.06.95 -> 1.07.1) - Update to version 1.07.1: * Fixed ibase extension causing problems for read() * Fixed parallel make problem. * Fixed dc "Q" comanmd bug. - Changes for version 1.07: * Added void functions. * fixes bug in load_code introduced by mathlib string storage in 1.06. * fix to get long options working. * signal code clean-up. * fixed a bug in the AVL tree routines. * fixed math library to work properly when called with ibase not 10. * fixed a symbol table bug when using more than 32 names. * removed a double free. * Added base 17 to 36 for ibase. * Fixed some memory leaks. * Various small tweaks and doc bug fixes. - Drop no longer needed patches: * bc-1.06.95-memleak.patch * bc-1.06.95-matlib.patch * bc-1.06.95-sigintmasking.patch - Refresh bc-1.06-dc_ibase.patch - Add gpg signature ==== binutils ==== Subpackages: binutils-devel - Add riscv64 target, tested with gcc7 and downstream newlib 2.4.0 * Prepare riscv32 target (gh#riscv/riscv-newlib#8) - Update binutils-2.28-branch.diff. - Make compressed debug section handling explicit, disable for old products and enable for gas on all architectures otherwise. - Add binutils-bso21333.diff. [boo#1029995] - Remove empty rpath component removal optimization from binutils-skip-rpaths.patch to workaround CMake rpath handling. [boo#1025282] ==== device-mapper ==== Version update (1.02.137 -> 1.02.139) Subpackages: libdevmapper-event1_03 libdevmapper1_03 libdevmapper1_03-32bit - Update to 2.02.170: * Few smal fixes around; obsoleted 169 release that was removed from mirrors - Refresh patch: * display-dm-name-for-lv-name.diff - Update device mapper version to 1.02.138, see WHATS_NEW_DM for detailed changelogs * Drop obsolete lvmchange files accordingly - Refresh libdm-iface-not-output-error-message-inside-retry-loop.patch - Refresh make-mirror-legs-on-different-tag-pvs.patch - device-mapper-dmsetup-export.patch - Version update to 2.02.169 release, see WHATS_NEW and WHATS_NEW_DM files for detailed changelogs - Split configure options to have one per line - Pass over with spec-cleaner - Enable internal cache - Enable lvmpolld - Add 'lvm2-lockd' subpackage, fate#323203 to lvm2-clvm to not pull corosync and other deps to the core lvm2 package ==== dracut ==== - Ensure hisi_sas_v2_hw gets included (bsc#1034597) * adds 0515-90kernel-modules-also-add-block-device-driver-revers.patch - Fix mdraid regression (bsc#1028542) * adds 0513-Fix-regression-caused-by-6f9bf2b8ac436259bdccb110545.patch - man: make the -k option clear using mkinitrd (bsc#1012656) * adds 0514-man-make-the-k-option-clear-using-mkinitrd.patch - Fix typo in installkernel script (bsc#1032576) - Drop binutils dependency in favor of elfutils * add 0512-Make-binutils-optional-when-elfutils-are-available.patch ==== elfutils ==== Subpackages: libasm1 libdw1 libelf1 libelf1-32bit - Add missing ldconfig calls for libasm1 - make tests pass when user does not want debuginfo (boo#1031556) ==== gawk ==== - Added an explicit rpmlint rule to keep one file (gawkapi.h) from requiring a separate package. [+gawk.rpmlintrc] ==== glibc ==== Subpackages: glibc-32bit glibc-locale-32bit - i686-memchr-sse.patch: Fix i686 memchr overflow calculation (bsc#1031021, BZ #21182) - sunrpc-use-after-free.patch: Avoid use-after-free read access in clntudp_call (BZ #21115) - Build testsuite with gdb and python-pexpect to enable more tests ==== glibc ==== Subpackages: glibc-devel glibc-extra glibc-info glibc-locale nscd - i686-memchr-sse.patch: Fix i686 memchr overflow calculation (bsc#1031021, BZ #21182) - sunrpc-use-after-free.patch: Avoid use-after-free read access in clntudp_call (BZ #21115) - Build testsuite with gdb and python-pexpect to enable more tests ==== libarchive ==== Version update (3.2.2 -> 3.3.1) Subpackages: bsdtar libarchive-devel libarchive13 - update to version 3.3.1 * Security & Feature release Details are not documented from upstream yet fix-extract-over-links.patch and libarchive-openssl.patch obsoleted ==== libserf ==== Subpackages: libserf-1-1 libserf-devel - do not check with time-dependent failures bsc#1035395 bsc#1031549 ==== libzypp ==== Version update (16.6.1 -> 16.8.0) - Add API to control resolver job to update all packages (FATE#320653) - Remove legacy vendor equivalence between 'suse' and 'opensuse' (bsc#1030686) - version 16.8.0 (0) - RepoInfo: Allow temporary repos to control their metadata directories (bsc#1032632) - Arch: add armv5tl - version 16.7.0 (0) ==== llvm4 ==== - readd arm_suse_support.diff which was accidentally removed in the 4.0.0 update ==== lockdev ==== Subpackages: liblockdev1 liblockdev1-32bit - add bcond lockdev_debug to be able to build a package with debugging output ==== lvm2 ==== Version update (2.02.168 -> 2.02.170) Subpackages: liblvm2app2_2 liblvm2cmd2_02 - Update to 2.02.170: * Few smal fixes around; obsoleted 169 release that was removed from mirrors - Refresh patch: * display-dm-name-for-lv-name.diff - Update device mapper version to 1.02.138, see WHATS_NEW_DM for detailed changelogs * Drop obsolete lvmchange files accordingly - Refresh libdm-iface-not-output-error-message-inside-retry-loop.patch - Refresh make-mirror-legs-on-different-tag-pvs.patch - device-mapper-dmsetup-export.patch - Version update to 2.02.169 release, see WHATS_NEW and WHATS_NEW_DM files for detailed changelogs - Split configure options to have one per line - Pass over with spec-cleaner - Enable internal cache - Enable lvmpolld - Add 'lvm2-lockd' subpackage, fate#323203 to lvm2-clvm to not pull corosync and other deps to the core lvm2 package ==== lzo ==== Version update (2.09 -> 2.10) Subpackages: liblzo2-2 lzo-devel - Update to 2.10 * Improve CMake build support. * Add support for pkg-config. * Do not redefine "snprintf" so that the examples build with MSVC 2015. * Assorted cleanups. ==== open-iscsi ==== Subpackages: iscsiuio - Fixed coredump when printing session information (bsc#1035236), backporting commit c8e6198dca71 from upstream open-iscsi ==== opie ==== Subpackages: opie-32bit - opie-fix-indendation.patch: fixed a wrong ; that broke a while() loop - opie-2.4-decl.diff: added missing stdlib.h, ctype.h, time.h includes everywhere (bsc#1031339) ==== perl-XML-Simple ==== Version update (2.22 -> 2.24) - updated to 2.24 see /usr/share/doc/packages/perl-XML-Simple/Changes 2.24 2017-04-17 16:12:00+12:00 Pacific/Auckland - fix typo in last commit with mistakenly removed some underscores - don't initialise $XML::Simple::PREFERRED_PARSER to undef as a caller may have already set it before loading XML::Simple and if not, it would have defaulted to undef anyway (RT#118205 from Slaven Rezi?) 2.23 2017-04-17 15:49:14+12:00 Pacific/Auckland - another fix to the logic for detecting circular references (RT#114120 from Matthias Pitzl, also report from Erland Sommarskog) ==== perl-libwww-perl ==== Version update (6.25 -> 6.26) - updated to 6.26 see /usr/share/doc/packages/perl-libwww-perl/Changes 6.26 2017-04-12 - Perltidy all apps in the bin/ directory - Make all apps in bin/ use strict and warnings (RT #92633) - Fix bug tracker URL in metadata ==== rubygem-cfa_grub2 ==== Version update (0.6.1 -> 0.6.2) - fix parsing grub.cfg with multi-level of submenus (bsc#1009025) - 0.6.2 ==== samba ==== Version update (4.6.2 -> 4.6.2+git.19.c267455e57b) Subpackages: libdcerpc-binding0 libdcerpc-binding0-32bit libdcerpc0 libdcerpc0-32bit libndr-krb5pac0 libndr-krb5pac0-32bit libndr-nbt0 libndr-nbt0-32bit libndr-standard0 libndr-standard0-32bit libndr0 libndr0-32bit libnetapi0 libnetapi0-32bit libsamba-credentials0 libsamba-credentials0-32bit libsamba-errors0 libsamba-errors0-32bit libsamba-hostconfig0 libsamba-hostconfig0-32bit libsamba-passdb0 libsamba-passdb0-32bit libsamba-util0 libsamba-util0-32bit libsamdb0 libsamdb0-32bit libsmbclient-devel libsmbclient0 libsmbconf0 libsmbconf0-32bit libsmbldap0 libsmbldap0-32bit libtevent-util0 libtevent-util0-32bit libwbclient0 libwbclient0-32bit samba-client samba-client-32bit samba-doc samba-libs samba-libs-32bit samba-winbind samba-winbind-32bit - Generate source tarball directly from Git using OBS tar_scm + use version string derived from parent Git tag and commit hash - remove obsolete vendor-files/tools/package-data version ID + explicitly generate ctdb manpages, needed without "make dist" ==== sysconfig ==== Version update (0.84.0 -> 0.84.1) Subpackages: sysconfig-netconfig - version 0.84.1 - netconfig: cleanup tmp files (boo#1010760) When /var/run/ntp/servers-netconfig has been modified externaly, don't try to backup or keep tmp files to show what we would do. - netconfig: improve input check for duplicate keys (bsc#1009801) ==== systemd ==== Subpackages: libsystemd0 libsystemd0-32bit libudev-devel libudev1 libudev1-32bit systemd-32bit systemd-bash-completion systemd-logger systemd-sysvinit udev - Import commit f0325620d23a247682c629d28883a364e4a7a8c4 327814841 core: when a unit's SourcePath points to API VFS pretend we are never out-of-date (#5487) f4b9fb58e units: move Before deps for quota services to remote-fs.target (#5627) (bsc#1028263) 44b9d27f8 udev: net_id - support predictable ifnames on vio buses (#5675) (bnc#1029183) 64f4761c9 units: apply plymouth warning fix to in rescue mode as well (#5615) 77607b887 units: do not throw a warning in emergency mode if plymouth is not installed (#5528) (bsc#1025398) 336d6016c core: downgrade "Time has been changed" to debug (#4906) (bsc#1028610) - Consider chroot updates in fix-machines-subvol-for-rollbacks.sh (bsc#1030290) ==== util-linux ==== Version update (2.29.1 -> 2.29.2) Subpackages: libblkid-devel libblkid1 libblkid1-32bit libfdisk1 libmount1 libmount1-32bit libsmartcols1 libuuid-devel libuuid1 libuuid1-32bit - Prefer sysfs exported SMBIOS3 tables in lscu (bsc#1033718) + arm64-lscpu-use-sysfs-for-table-access-if-available.patch - To cover release numbers of both SLE12 SP3 and Leap 42.3, relax release based conflict with bash-completion from 13.1 to 10. - fix util-linux-losetup-Add-support-for-setting-logical-blocksize.patch - -logical-blocksize was behaving like --nooverlap - Conflict with old systemd-presets-branding to ensure correct preset migration (boo#1029775, bsc#1012850). - Drop "codepage" fstab migration needed for SuSE Linux < 9.1 (bsc#51950 (suse#36950)). - Keep dependency on insserv and fillup for compatibilitiy reasons in Leap 42.3. Too many poorly written packages depend on it. (Marked as "sysv compatibility hack".) - Update to version 2.29.2: * su(1) security issue CVE-2017-2616 (bsc#1023041) * minor bugfixes and enhancements ==== util-linux-systemd ==== Version update (2.29.1 -> 2.29.2) - Prefer sysfs exported SMBIOS3 tables in lscu (bsc#1033718) + arm64-lscpu-use-sysfs-for-table-access-if-available.patch - To cover release numbers of both SLE12 SP3 and Leap 42.3, relax release based conflict with bash-completion from 13.1 to 10. - fix util-linux-losetup-Add-support-for-setting-logical-blocksize.patch - -logical-blocksize was behaving like --nooverlap - Conflict with old systemd-presets-branding to ensure correct preset migration (boo#1029775, bsc#1012850). - Drop "codepage" fstab migration needed for SuSE Linux < 9.1 (bsc#51950 (suse#36950)). - Keep dependency on insserv and fillup for compatibilitiy reasons in Leap 42.3. Too many poorly written packages depend on it. (Marked as "sysv compatibility hack".) - Update to version 2.29.2: * su(1) security issue CVE-2017-2616 (bsc#1023041) * minor bugfixes and enhancements ==== vim ==== Version update (8.0.324 -> 8.0.566) Subpackages: gvim vim-data - Updated to revision 566, fixes the following problems * :windo allows for ! but it's not supported. * Undefined behavior when using backslash after empty line. * Not enough test coverage for syntax commands. * Crash when getting the window position in tmux. * Cannot detect Bazel BUILD files on some systems. * Using freed memory in :caddbuf after clearing quickfix list. * Setting nocompatible for the tiny version moves the cursor. - Refresh and re-add vim-8.0-ttytype-test.patch - Updated to revision 559, fixes the following problems * Test_edit causes older xfce4-terminal to close. (Dominique Pelle) * Cppcheck warnings. * Edit test may fail on some systems. * Swap file exists briefly when opening the command window. * Extra line break in verbosefile when using ":echomsg". (Ingo Karkat) * Saving the redo buffer only works one time, resulting in the "." command not working well for a function call inside another function call. * No test for the 8g8 command. * Some etags format tags file use 0x01, breaking the parsing. * The typeahead buffer is reallocated too often. * Toupper and tolower don't work properly for Turkish when 'casemap' is empty. (Bjorn Linse) * Toupper/tolower test with Turkish locale fails on Mac. * Toupper and tolower don't work properly for Turkish when 'casemap' contains "keepascii". (Bjorn Linse) * Toupper/tolower test fails on OSX without Darwin. * Getting the window position fails if both the GUI and term code is built in. * GTK: using static gravities is not useful. * The :ownsyntax command is not tested. * Setting ttytype to xxx does not always fail as expected. - Remove vim-8.0-ttytype-test.patch, fixed upstream. - Update the update-alternatives code - Updated to revision 542, fixes the following problems * ml_get errors in silent Ex mode. (Dominique Pelle) * A large count on a normal command causes trouble. (Dominique Pelle) * There is no way to remove quickfix lists (for testing). * Storing a zero byte from a multi-byte character causes fold text to show up wrong. * Character classes are not well tested. They can differ between platforms. * Using a function pointer instead of the actual function, which we know. * GtkForm handling is outdated. * MS-Windows: when 'clipboard' is "unnamed" yyp does not work in a :global command. * dv} deletes part of a multi-byte character. (Urtica Dioica) * Folds are messed up when 'encodin' is "utf-8". * Coverity complains about possible negative value. * RISC OS support was removed long ago, but one file is still included. * When 'wildmenu' is set and 'wildmode' has "longest" then the first file name is highlighted, even though the text shows the longest match. * Line in test commented out. * Buffer overflow when 'columns' is very big. (Nikolai Pavlov) * Test with long directory name fails on non-unix systems. * Test with long directory name fails on Mac. * Abbreviation doesn't work after backspacing newline. (Hkonrk) * Defaults.vim does not work well with tiny features. (crd477) * Memory leak when exiting from within a user function. * Quickfix window not updated when freeing quickfix stack. * Illegal memory access with :z and large count. * No test for falling back to default term value. * Startup test fails on Mac. * Building unit tests fails. * Compiler warning on MS-Windows. * getpos() can return a negative line number. (haya14busa) - Update spec.skeleton with spec-cleaner - Updated to revision 514, fixes the following problems * Insufficient testing for statusline. * 'makeencoding' missing from the options window. * Git and hg see new files after running tests. (Manuel Ortega) * Options test does not always test everything. * Options test fails or hangs on MS-Windows. * 'cinoptions' cannot set indent for extern block. * "make shadow" creates an invalid link. * Quite a few beeps when running tests. * Clang version not correctly detected. * Some functions are not tested. * Running the options test sometimes resizes the terminal. * The packadd test does not create the symlink correctly and does not test the right thing. * The fnamemodify test changes 'shell' in a way later tests may not be able to use system(). * Using ":%argdel" while the argument list is already empty gives an error. (Pavol Juhas) * Not enough test coverage in Insert mode. * Dead code in #ifdef. * Patch shell command uses double quotes around the argument, which allows for $HOME to be expanded. (Etienne) * Terminal width is set to 80 in test3. * Diffpatch fails when the file name has a quote. * Getpgid is not supported on all systems. * The ";" command does not work after characters with a lower byte that is NUL. * Getting font name does not work on X11. * Some macros are in lower case, which can be confusing. * Part of fold patch accidentally included. * v:progpath is not reliably set. * Some macros are in lower case. * Some macros are in lower case. * Adding fold marker creates new comment. * Compiler warnings for comparing unsigned char with 256 always being true. (Manuel Ortega) * The mode test may hang in Test_mode(). (Michael Soyka) * Typo in MinGW test makefile. * Using :move messes up manual folds. * Potential crash if adding list or dict to dict fails. * Old fix for :move messing up folding no longer needed, now that we have a proper solution. * Can't build on HPUX. * Test 45 hangs on MS-Windows. * If an MS-Windows tests succeeds at first and then fails in a way it does not produce a test.out file it looks like the test succeeded. * Resetting 'compatible' in defaults.vim has unexpected side effects. (David Fishburn) * Can't find executable name on Solaris and FreeBSD. * Off-by-one error in using :move with folding. * There are still a few macros that should be all-caps. * Using g< after :for does not show the right output. (Marcin Szamotulski) * After aborting an Ex command g< does not work. (Marcin Szamotulski) * Compiler warnings on MS-Windows. * Not enough testing for help commands. * Exit callback test sometimes fails. * When a test fails and test.log is created, Test_edit_CTRL_I matches it instead of test1.in. * No test covering arg_all(). * The client-server feature is not tested. * Not enough testing for the client-server feature. * Missing change to main.c. * The client-server test may hang when failing. * Tests use assert_true(0) and assert_false(1) to report errors. * remote_peek() is not tested. * The remote_peek() test fails on MS-Windows. * Unnecessary if statement. * The setbufvar() function may mess up the window layout. (Kay Z.) * Illegal memory access when using :all. (Dominique Pelle) * Using :lhelpgrep with an argument that should fail does not produce an error if the previous :helpgrep worked. * Not all windows commands are tested. * Crash and endless loop when closing windows in a SessionLoadPost autocommand. * The autocmd test hangs on MS-Windows. * Running tests leaves an "xxx" file behind. * Clipboard and "* register is not tested. * Splitting a 'winfixwidth' window vertically makes it one column smaller. (Dominique Pelle) * The quotestar test fails when a required feature is missing. * A failing client-server request can make Vim hang. * Crash with cd command with very long argument. * Build failure with older compiler on MS-Windows. * The quotestar test uses a timer instead of a timeout, thus it cannot be rerun like a flaky test. * Insufficient testing for folding. * Arabic support is not fully tested. * Two autocmd tests are skipped on MS-Windows. * taglist() does not prioritize tags for a buffer. * Quotestar test is still a bit flaky. * On MS-Windows ":!start" does not work as expected. * Coverity complains about possible NULL pointer. * Endless loop in updating folds with 32 bit ints. * Looking up an Ex command is a bit slow. * Failed window split for :stag not handled. (Coverity CID 99204) * Can't build with ANSI C. * Client-server tests fail when $DISPLAY is not set. * Coveralls no longer shows per-file coverage. * No link to codecov.io results. * Typo in link to codecov.io results. * Menuage for skipping client-server tests is unclear. * Check for available characters takes too long. * Getting name of cleared highlight group is wrong. (Matt Wozniski) * Script for creating cmdidxs can be improved. - Disable term=xxx test, does not work with any vim version * vim-8.0-ttytype-test.patch - Update apparmor.vim (taken from AppArmor 2.11) * add support for the "kcm" and "qipcrtr" network keywords * update change_profile rule highlighting - Build default vim without X11 support, use update-alternatives to prefer gvim if installed for X11 support. - Updated to revision 425, fixes the following problems * Packadd test does not clean up symlink. * Packadd test uses wrong directory name. * The E11 error message in the command line window is not translated. * The "zero count" error doesn't have a number. (Hirohito Higashi) * Xfontset and guifontwide are not tested. * Illegal memory access after "vapo". (Dominique Pelle) * Restoring help snapshot accesses freed memory. (Dominique Pelle) * GUI test fails on some systems. * Illegal memory access when 'complete' ends in a backslash. * Can't access b:changedtick from a dict reference. * Functions test fails. * Flags of :substitute not sufficiently tested. * Invalid memory access in :recover command. * :recover test fails on MS-Windows. * Illegal memory access with vi' * Not checking return valud of dict_add(). (Coverity) * When using complete() and typing a character undo is saved after the character was inserted. (Shougo) * Double free when compiled with EXITFREE and setting 'ttytype'. * b:changedtick can be unlocked, even though it has no effect. * Unlet command leaks memory. (Nikolai Pavlov) * islocked('d.changedtick') does not work. * Vim relies on limits.h to be included indirectly, but on Solaris 9 it may not be. (Ben Fritz) * When using CTRL-X CTRL-U inside a comment, the use of the comment leader may not work. (Klement) * When building with a shadow directory on macOS lacks the +clipboard feature. * Redrawing errors with GTK 3. * Not enough test coverage for Perl. * No test for concatenating an empty string that results from out of bounds indexing. * The condition for when a typval needs to be cleared is too complicated. * If [RO] in the status line is translated to a longer string, it is trunctted to 4 bytes. * Test to check that setting termcap key fails sometimes. * Using uninitialized memory when 'isfname' is empty. * Leaking memory when setting 'ttytype'. * Crash when setting 'guicursor' to weird value. * Invalid memory access in C-indent code. * 'number' and 'relativenumber' are not properly tested. * Sometimes VimL is used, which is confusing. * GUI initialisation is not sufficiently tested. * Tests fail on MS-Windows. * Travis is too slow to keep up with patches. * ]s does not move cursor with two spell errors in one line. * Might free a dict item that wasn't allocated. * Build fails with tiny features. * If configure defines _LARGE_FILES some include files are included before it is defined. * Not all options are tested with a range of values. * The 'balloondelay', 'ballooneval' and 'balloonexpr' options are not defined without the +balloon_eval feature. Testing that an option value fails does not work for unsupported options. * Invalid memory access when setting wildchar empty. * Leaking memory when setting v:completed_item. * More options are not always defined. * Build fails without +folding. * Invalid memory access when using :sc in Ex mode. (Dominique Pelle) * The "+ register is not tested. * Size computations in spell file reading are not exactly right. * Possible overflow when reading corrupted undo file. CVE-2017-6349 bsc#1027057 * Another possible overflow when reading corrupted undo file. CVE-2017-6350 bsc#1027053 * CTRL-Z and mouse click use CTRL-O unnecessary. * With 'linebreak' set and 'breakat' includes ">" a double-wide character results in "<<" displayed. * Diff mode is not sufficiently tested. * Warning in tiny build for unused variable. (Tony Mechelynck) * Misplaced #ifdef. (Christ van Willigen) * Timer test failed for no apparent reason. * No tests for arabic. * Tiny build has a problem with generating the options test. * compiler warnings * filtering lines through "cat", without changing the line count, changes manual folds. * Test for arabic does not check what is displayed. * When the window scrolls horizontally when the popup menu is displayed part of it may not be cleared. (Neovim issue #6184) * Arabic support is verbose and not well tested. * GUI test fails with Athena and Motif. * When the same tag appears more than once, the order is unpredictable. (Charles Campbell) * Tabs are not aligned when scrolling horizontally and a Tab doesn't fit. (Axel Bender) * Testing the + register fails with Motif. * 'balloonexpr' only works synchronously. * Cannot build with the viminfo feature but without the eval feature. * Illegal memory access with "t". * Crash when using balloon_show() when not supported. (Hirohito Higashi) * Some tests have a one second delay. * Test fails with missing balloon feature. * :map completion does not have <special>. (Dominique Pelle) * GUI tests may fail. * Not enough testing for quickfix. * v:progpath may become invalid after ":cd". * The arabic shaping code is verbose. * Filtering folds with marker method not tested. * Updating folds does not work properly when inserting a file and a few other situations. * set_progpath is defined but not always used * Newer gettext/iconv library has extra dll file. * We can't change the case in menu entries, it breaks translations. * Menu test fails on MS-Windows. * Menu test fails on MS-Windows using gvim. * Balloon eval is not tested. * Balloon test fails on MS-Windows. * Setting v:progpath is not quite right. * Test for the clipboard fails sometimes. * ASAN logs are disabled and don't cause a failure. * Test for v:progpath fails on MS-Windows. * When running :make the output may be in the system encoding, different from 'encoding'. * Diff mode is displayed wrong when adding a line at the end of a buffer. * Python test fails with Python 3.6. * The effect of adding "#" to 'cinoptions' is not always removed. * Compiler warnings on MS-Windows. (Ajit Thakkar) * Build errors when building without folding. - Drop test87-python36.patch, fixed upstream. ==== yast2 ==== Version update (3.2.27 -> 3.2.28) - Fixed parsing whitespace lines in /etc/fstab (bsc#1030425) - 3.2.28 ==== yast2-bootloader ==== Version update (3.2.18 -> 3.2.19) - Add possibility to use trusted boot for EFI (FATE#315831) - 3.2.19 ==== yast2-update ==== Version update (3.2.0 -> 3.2.2) - Fixed parsing whitespace lines in the original /etc/fstab (bsc#1030425) - 3.2.2 - Allow YaST modules to add packages during upgrade (bsc#1009834) - 3.2.1 ==== zypper ==== Version update (1.13.22 -> 1.13.24) Subpackages: zypper-aptitude zypper-log - patch: add --with-update to install also plain package updates. This is basically the same as running 'zypper update' afterwards. (FATE#320653) - BuildRequires: libzypp-devel >= 16.8.0 - Fix TODOs in zypper manpage (bsc#1032259) - Remove legacy vendor equivalence between 'suse' and 'opensuse' (bsc#1030686) - version 1.13.24 - Fix crash when exiting after pressing CTRL-C quickly twice or more (bsc#1032279) - Use private temporary repos for --plus-repo (bsc#1032632,bsc#1017267) - Use private temporary repos to collect rpms passed on the command line (bsc#1032632) - Allow --plus-content to temporarily enable repos by alias/number - refresh: recognize --plus-content repos (FATE#319486) - BuildRequires: libzypp-devel >= 16.7.0 - version 1.13.23 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

4 4

[opensuse-factory] Submissions to openSUSE:Backports project
by İsmail Dönmez 28 Apr '17

28 Apr '17

Hi all, I wanted to clear up some confusion around the Backports project on OBS. As you know Backports (also know as PackageHub by its consumer name, https://packagehub.suse.com/) provides packages for Enterprise users that does not exist on on the SUSE Linux Enterprise releases. First of all, thank you for submitting to Backports, we appreciate it! But please consider two things: 1. Please submit to the lowest compatible release. If your software builds/runs perfectly on SLE12 please submit to openSUSE:Backports:SLE-12 . If you need features from SP2 it's perfectly fine to submit to openSUSE:Backports:SLE-12-SP2, but unless you need updated libs etc. try to target the minimum release. 2. Please never submit to :Update project as these only exist for internal purposes and not published. If you want to know more about the Backports project, please see https://en.opensuse.org/Portal:Backports https://en.opensuse.org/openSUSE:Backports_Package_Submission_Process Thank you! İsmail DÖNMEZ -- SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg)

1 0

[opensuse-factory] New Tumbleweed snapshot 20170426 released!
by Dominique Leuenberger 28 Apr '17

28 Apr '17

1 0

[opensuse-factory] Re: [opensuse-packaging] Proposal: Update rpm configuration to fix issues and rationalize configuration
by Ludwig Nussel 27 Apr '17

27 Apr '17

Michael Matz schrieb: > On Wed, 26 Apr 2017, Ludwig Nussel wrote: > >>> belongs where, header files to /usr/include, libraries to /usr/lib and >>> executables called only internally by other tools into /usr/libexec, or >>> /usr/libexec/$toolname (modules would belong into this category) and >>> other files associated with a tool into /usr/share. >>> >>> From there it follows fairly easily that /usr/lib should be empty on a >>> pure lib64 system. Also /usr/lib should be able to be mounted noexec, and >> >> So where would you move /usr/lib/perl5 then? I has it's own architecture >> specific subdirectories. And where to put plugins in general? They ought >> to be in subdirectories of lib to not interfere with the dynamic linker. > > As I said, modules (i.e. DSOs that are used with dlopen, not loaded by > ld.so) would be placed into (subdirs of) libexec (conceptually (to me) > they are more similar to helper executables than shared libraries; they > just happen to be implemented via shared library mechanisms) Shared libraries need to have matching architecures though. Ie 32bit and 64bit libs need different plugins (like e.g. pam modules). So putting them in libexec wouldn't work. >>> [...] >> Packages that put helper binaries in lib64 are doing it wrong unless the >> binary has an ABI incompatible with a 32bit library that calls it. > > Huh? No, whatever the bitness of executable-a (and hence libs used by > it), that doesn't at all have to influence the bitness of exe-b > execve(2)'ed by it. So, it's _always_ wrong to put executables into lib64 In theory a binary could speak a protocol with it's calling library that differs depending on architecture (like eg. writing structs in shared memory). In such a case it would have to go to lib64. > /usr/lib/perl5 is one of the big blobs with its own way of doing things. > Many (but not all) of the files therein are not arch dependend or binary, > and hence would actually have a better place under /usr/share. The binary > files that are there are not shared libraries for the dynamic loader but > dlopen modules, so that would speak for libexec. Splitting the content of > perl stuff between /usr/share and /usr/libexec might be seen as to large a > hassle (though with the appropriate setting of $PERL5LIB might be > invisible in practice), or going against perls idea that there should be > "the" main directory for putting stuff in (though even that would be wrong > to claim, perl is happy when confired with additional search dirs). > > So, considering this I'd answer you with "/usr/libexec/perl5", or "split > into /usr/libexec/perl5 and /usr/share/perl5". Sounds like libexec would lead to even more hairsplitting about where files should be placed for little if any at all practical benefit. > (and I agree with that if libexec isn't used). Nevertheless it happens, > and I claim it happens because if a tool has shared libs and helper exes > the packager is confused what to place where and just chooses lib64 for > everything, and I further claim that with libexec with the appropriate > role (or better with lib/lib64 having very strict roles) there would be > less confusion. (The rule then would be very easy: every shared lib > that's directly shown in output of ldd is put into lib{,64}, and > _everything else_ is not put there). > >> On a system without libexec, /usr/lib/%name is the right choice rather >> than %_libdir/%name. > > Yes, agreed as per above. I just randomly looked at gawk for other > reasons, et voila, it already gets that part wrong. It wrongly uses --libexecdir=%{_libdir}. Doesn't matter how we define %_libexecdir then :-) cu Ludwig -- (o_ Ludwig Nussel //\ V_/_ http://www.suse.com/ SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) -- 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] Is lsyncd still having an active maintainer?
by Dominique Leuenberger / DimStar 27 Apr '17

27 Apr '17

Hi everybody, Since the upgrade of rpm to version 4.13, lsyncd has been failing in openSUSE:Factory. A submit request by me, created on March 15 2017 remained without comment or other actions (by neither the pkg nor any of the prj maintainers). The fix is really trivial - but if even such things are not moving forward I can't but wonder if this package can actually be considered maintained? If not, I will initiate a delete request of this package to have it dropped from openSUSE:Factory. Cheers, Dominique

1 0

[opensuse-factory] High CPU use in Plasma 5
by Constant Brouerius van Nidek 27 Apr '17

27 Apr '17

Most of the time I use LXQt as my desktop due to a better readability. Sometimes I also use Plasma 5. Just found out that the CPU usage in Plasma is way to high (70%) in comparison with a similar usage of programs in LXQT (10 to 20%). In Plasma the culprits seem to be according to KSysGuard : X with 29 to 28 %, Kwin_x11 15 to 20%, Chromium 15 to 20% and QtWebEngineProssesor with 5% With the same programs loaded under LXQT none of above programs have exceptional CPU usage. The highest user Chromium does not come over the 4% CPU usage. What is going wrong in Plasma? How can I let it behave better? -- opensuse:tumbleweed:20170424 Qt: 5.7.1 KDE Frameworks: 5.32.0 kf5-config: 1.0 KDE Plasma: 5.9.4 plasmashell 5.9.4 Kernel: 4.10.10-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

3 2

[opensuse-factory] openSUSE Leap's Next rpm macro values
by Greg Freemyer 27 Apr '17

27 Apr '17

On Tue, Apr 25, 2017 at 5:54 PM, Simon Lees <sflees(a)suse.de> wrote: > > On 04/25/2017 11:57 PM, Rüdiger Meier wrote: >> >> >> On 04/25/2017 04:11 PM, Simon Lees wrote: >>> >>> >>> On 04/25/2017 11:30 PM, Simon Lees wrote: >>>> >>>> >>>> On 04/25/2017 10:44 PM, Rüdiger Meier wrote: >>>>> >>>>> >>>>> On 04/25/2017 03:05 PM, Greg Freemyer wrote: >>>>>> On Tue, Apr 25, 2017 at 8:53 AM, Stefan Seyfried >>>>>> <stefan.seyfried(a)googlemail.com> wrote: >>>>>>> On 25.04.2017 14:26, Christian Boltz wrote: >>>>>>>> So even without the 42.x -> 15.x leap (pun intended), it seems >>>>>>>> version >>>>>>>> numbers are already confusing ;-) I know switching to 15.x adds >>>>>>>> slightly more confusion now, but on the long term it's much >>>>>>>> better to >>>>>>>> have SLE, Leap and suse_version in sync than always having to do >>>>>>>> the "+ >>>>>>>> 30" math for the Leap version. >>>>>>> >>>>>>> As I already mentioned, we could just go for 150, 151, 152, 160... >>>>>>> >>>>>>> This would still be tied to SLES in an obvious way, and not backwards >>>>>>> from 42.x >>>>>>> >>>>>>> Best of both worlds. >>>>>> >>>>>> At a minimum that should be done in /etc/issue. >>>>>> >>>>>> And maybe %leap_version 1500000, 1510000, 1520000, 1600000, ... in rpm >>>>>> macros. >>>>> >>>>> I still don't get why do we need to be tied to SLES version numbers at >>>>> all. What is the technical reason behind this? It is pure unimportant >>>>> cosmetics. >> >>>> Well the two distro's share a significant number of source packages that >>>> are the same so being able to refer to them in the same way in places >>>> makes a reasonable amount of sense. >> >> That's true and it's *nice* to know, not more. There is no technical >> reason why /etc/os-release should have the same VERSION_ID on LEAP and >> SLE. >> >>> The following shows us that around 1890 of the 9296 packages in Leap >>> 42.2 come directly from the SLE equivalent, most of these packages are >>> core parts of the distro, think systemd, dbus, gtk, qt etc. So from a >>> technical perspective being able to version them the same certainly has >>> advantages. >> >>> simon@tek-top ~ ➤  osc -A https://api.opensuse.org cat >>> openSUSE:Leap:42.2:Update 00Meta lookup.yml | wc -l >>> 9296 >>> simon@tek-top ~ ➤  osc -A https://api.opensuse.org cat >>> openSUSE:Leap:42.2:Update 00Meta lookup.yml | grep "SLE-12" | wc -l >>> 1890 >> >> And...? You mean you could have done this task easier on Leap 15 as >> it's planned? >> >> No, Obviously you've found out this although 42.2 is different from >> the SLE version. You did not even used "SP2", probably you could have >> also grepped without "12". > > No, I'm not referring to this specific task, but i'm showing 1890 places > where there is a technical reason to use the same version between the > two as we share the code between the two. I'm just talking rpm macros exclusively below, so nothing visible to the public or 99% of users: I don't think any of the negative comments I've heard are complaining about %suse_version being 1500 for the next major Leap release (after 42.3). I'm going to treat that as a given and I think that is all the board has spoken to so far. But we have %suse_version, %sle_version, %leap_version, and %is_opensuse. In Leap 42.2 they are: suse_version = 1315 sle_version = 120200 leap_version = 420200 is_opensuse = 1 In Leap Next, if I understand correctly, we may kill off leap_version and only have: suse_version = 1500 sle_version = 150000 is_opensuse = 1 Is it really all that painful to also have: leap_version = 450000 or leap_version = 1500000 (note the extra zero) And if having both sle_version and leap_version different really is that painful, why not make both 1500000 sle_version = 1500000 (with the extra zero) leap_version = 1500000 (with the extra zero) There are no existing spec files that are testing for %sle_version == 150000, so just add a zero and the spec files get to as simple as possible from day 1 of SLE 15 development. (which I assume is very soon). Greg -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

3 8

[opensuse-factory] Re: [opensuse-packaging] Proposal: Update rpm configuration to fix issues and rationalize configuration
by Jan Engelhardt 26 Apr '17

26 Apr '17

On Wednesday 2017-04-26 17:57, Michael Matz wrote: >> > From there it follows fairly easily that /usr/lib should be empty on a >> > pure lib64 system. Also /usr/lib should be able to be mounted noexec, and >> >> So where would you move /usr/lib/perl5 then? I has it's own architecture >> specific subdirectories. And where to put plugins in general? They ought >> to be in subdirectories of lib to not interfere with the dynamic linker. > >As I said, modules (i.e. DSOs that are used with dlopen, not loaded by >ld.so) would be placed into (subdirs of) libexec (conceptually (to me) >they are more similar to helper executables than shared libraries; they >just happen to be implemented via shared library mechanisms) > >/usr/lib/perl5 is one of the big blobs with its own way of doing things. >Many (but not all) of the files therein are not arch dependend or binary, >and hence would actually have a better place under /usr/share. The binary >files that are there are not shared libraries for the dynamic loader but >dlopen modules, so that would speak for libexec. It's not that easy. perl also exists as a dynamic loader library (libperl.so) that could exist in multiple bitnesses, which means all the Perl modules (well,mthe XS things) cannot be libexec aka single bitness. Same for Python.. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

1 0

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

openSUSE Factory April 2017