July 2016 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 978282] New: vlc: SIGFPE, Arithmetic exception
by bugzilla_noreply＠novell.com 31 Jul '19

31 Jul '19

http://bugzilla.opensuse.org/show_bug.cgi?id=978282 Bug ID: 978282 Summary: vlc: SIGFPE, Arithmetic exception Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: dimstar(a)opensuse.org Reporter: mpluskal(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 675400 --> http://bugzilla.opensuse.org/attachment.cgi?id=675400&action=edit full backtrace When using TW+packman repos for tw and I execute following: /usr/bin/vlc -I dummy v4l:// --sout #transcode{vcodec=mp4v}: standard{access=http,mux=ogg,dst=hobo.local:8080} I get Arithmetic exception: (gdb) bt #0 0x00007f382deb578c in transcode_video_encoder_init (p_stream=p_stream@entry=0x7f380c4c9398, id=id@entry=0x7f381c000b20) at transcode/video.c:551 #1 0x00007f382deb60cb in transcode_video_process (p_stream=0x7f380c4c9398, id=id@entry=0x7f381c000b20, in=0x0, out=out@entry=0x7f382c446c90) at transcode/video.c:884 #2 0x00007f382deb167b in Send (p_stream=0x7f380c4c9398, id=0x7f381c000b20, p_buffer=<optimized out>) at transcode/transcode.c:661 #3 0x00007f383c1ec658 in sout_InputSendBuffer (p_input=0x7f381c0009a0, p_buffer=p_buffer@entry=0x7f38180008c0) at stream_output/stream_output.c:233 #4 0x00007f383c1795c4 in DecoderPlaySout (p_sout_block=0x7f38180008c0, p_dec=0x7f380c4d2a58) at input/decoder.c:1501 #5 DecoderProcessSout (p_block=0x0, p_dec=<optimized out>) at input/decoder.c:1556 #6 DecoderProcess (p_block=<optimized out>, p_dec=<optimized out>) at input/decoder.c:1787 #7 DecoderThread (p_data=0x7f380c4d2a58) at input/decoder.c:909 #8 0x00007f383c9ea424 in start_thread (arg=0x7f382c447700) at pthread_create.c:333 #9 0x00007f383c525add in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 990956] New: Missing categories in brp-check-suse (brp-30-desktop)
by bugzilla_noreply＠novell.com 26 Jul '19

26 Jul '19

http://bugzilla.opensuse.org/show_bug.cgi?id=990956 Bug ID: 990956 Summary: Missing categories in brp-check-suse (brp-30-desktop) Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: luizluca(a)tre-sc.jus.br QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Hello, I was writing a RPM file which packs a .desktop file. I used the categogy "Utility;TelephonyTools;" and OBS gave me: 'ERROR: No sufficient Category definition:' I checked the file /usr/lib/rpm/brp-desktop.data/applications.menu and it seems to be outdated when I compare with https://specifications.freedesktop.org/menu-spec/menu-spec-1.0.html or https://cgit.freedesktop.org/xdg/xdg-specs/tree/menu/menu-spec.xml. Even OpenSUSE suggests TelephonyTools category at https://en.opensuse.org/openSUSE:Packaging_desktop_menu_categories So, something is not updated. Either all the checked sources or brp-check-suse. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 954556] New: After upgrading from 13.2 to Leap 42.1, Mercurial chokes on files locally deleted and ignored, but changed on the remote
by bugzilla_noreply＠novell.com 12 Jul '19

12 Jul '19

http://bugzilla.opensuse.org/show_bug.cgi?id=954556 Bug ID: 954556 Summary: After upgrading from 13.2 to Leap 42.1, Mercurial chokes on files locally deleted and ignored, but changed on the remote Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.1 Hardware: x86-64 URL: http://users.skynet.be/antoine.mechelynck/vim/vim-tony mec.bundle.bz2 OS: openSUSE 42.1 Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: antoine.mechelynck(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I'm not sure if this bug is in the correct Component. It concerns a difference between the Mercurial versions for openSUSE 13.2 and openSUSE Leap 42.1. I'll describe below the problems I had (in a Mercurial repository with local changes) after upgrading to Leap 42.1, and how I solved them (probably not ideally), in the hope that something can be found to make life easier to anyone else running into the same (or a sufficiently similar) problem. FWIW I've uploaded at http://users.skynet.be/antoine.mechelynck/vim/vim-tonymec.bundle.bz2 a full bundle of my local Vim repository, including a clone of the Mercurial mirror at https://bitbucket.org/vim-mirror/vim with local changes. The bundle is 8.8 MiB for a repository occupying about 151 MiB so I didn't attach it to this bug. The tip before I upgraded to Leap 42.1 was the merge commit about 30 changesets from the present tip. The earlier changesets (0 to 7225) are probably not as interesting but I didn't know how else to let you look at it from my point of view. It might be possible to inspect the bundle without unpacking it, by declaring it as a "repository" by means of the -R argument to Mercurial. This past weekend I upgraded to Leap 42.1 and a few hours ago "hg in" displayed 27 new changesets. I tried to "fetch" them but instead of saying "remote changed runtime/doc/tags which local deleted" and asking me if I wanted to download the changes or keep deleted, Mercurial errored out with the new changesets applied, the "old" merge still current, no new merge done, and a message saying that it could not proceed because of a locally ignored file changed on the remote (the deleted file in question). I goofed around some, updated (not easily) to 0 and back to tip, including a couple of manual merges for which Mercurial invoked vimdiff as my preferred merge tool, and finally added one monstrous changeset by hg addremove followed by hg commit. Those "added" files are IIUC files ignored by my locally modified .hgignore on the other unnamed branch. After that I could finally merge my local changes with the monstrous changeset I had just added on top of Bram's official tip. After that I notice that "hg diff" on the locally deleted file does not give the same output as it used to before the upgrade to Leap. Previously it showed a diff between the remote version of the file and /dev/null, which was longish and looked messy, but, well, I used to think that was the way of things, at least with that version of Mercurial. Now it just says: diff --git a/runtime/doc/tags b/runtime/doc/tags deleted file mode 100644 which I find much neater even if it is not visually reversible. I am practically certain that what I did was not the "ideal" thing to do, but it is the best I could find to work around this change of behaviour and still get a working directory tree with which I could compile Bram's version with my local changes (which consist of one feature added and one disabled in src/feature.h, plus .hgignore lines for runtime/doc/tags which is regenerated by "make install" anyway, and for some directories and files not present on the remote, e.g. "shadow" directories allowing me to compile a Huge and a Tiny build in parallel from the same source with different config settings passed as environment variables). I hope Mercurial won't choke again the next time new changesets are added at the remote and I try to apply them. -- You are receiving this mail because: You are on the CC list for the bug.

1 11

[Bug 989493] New: mlocate security: normal user must be added to group nobody; wrong man page info about --require-visibility FLAG
by bugzilla_noreply＠novell.com 11 Jul '19

11 Jul '19

http://bugzilla.suse.com/show_bug.cgi?id=989493 Bug ID: 989493 Summary: mlocate security: normal user must be added to group nobody; wrong man page info about --require-visibility FLAG Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.1 Hardware: x86-64 OS: openSUSE 42.1 Status: NEW Severity: Major Priority: P5 - None Component: Security Assignee: security-team(a)suse.de Reporter: studio(a)anchev.net QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- The man page of update db says (excerpt): --------------- -l, --require-visibility FLAG Set the “require file visibility before reporting it” flag in the generated database to FLAG. If FLAG is 0 or no, or if the database file is readable by "others" or it is not owned by nobody, locate(1) outputs the database entries even if the user running locate(1) could not have read the directory necessary to find out the file described by the database entry. If FLAG is 1 or yes (the default), locate(1) checks the permissions of parent directories of each entry before reporting it to the invoking user. To make the file existence truly hidden from other users, the database group is set to nobody and the database permissions prohibit reading the database by users using other means than locate(1), which is set-gid nobody. Note that the visibility flag is checked only if the database is owned by nobody and it is not readable by "others". --------------- I made the following experiment: - Run updatedb as root with no extra options (supposing by default it will use flag 1 as per man page) - Checked the permission of the db file (it was 644) - Run "locate root" as normal user - I can see the contents of /root (which means the man page is wrong and by default flag is 0) - chown nobody: /var/lib/mlocate/mlocate.db - Run "locate root" as normal user - again I can see the contents of /root - chmod 640 /var/lib/mlocate/mlocate.db (as according to the documentation that is required in order the flag 1 to be respected) - same result Then I tried explicitly to run "updatedb -l 1" as root and I see that it recreates the db file but this time the permissions are 640. So even when owned by nobody a normal user cannot use the locate command: > locate root locate: can not open `/var/lib/mlocate/mlocate.db': Permission denied After adding my user to group nobody I was able to run "locate root" without seeing the files in "/root". This whole thing means that: 1. The man page is not correct as the default is FLAG 0 (insecure), not 1 (secure) 2. One is forced to use the first approach (adding each user to group nobody). I don't know what are the security implications of this but it doesn't sound as something normal, right? 3. The script /etc/cron.daily/mlocate.cron needs to be modified somehow in order to use explicitly FLAG 1 (is that possible?) -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 956262] New: cobbler dependencies.
by bugzilla_noreply＠novell.com 11 Jul '19

11 Jul '19

http://bugzilla.suse.com/show_bug.cgi?id=956262 Bug ID: 956262 Summary: cobbler dependencies. Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.1 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Installation Assignee: yast2-maintainers(a)suse.de Reporter: osynge(a)suse.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- The applications: cobbler-2.6.6-3.8.noarch cobbler-web-2.6.6-3.8.noarch Are separately packaged hence "cobbler" should not depend on apache. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 935339] New: gpgme fails to cleanly uninstall: install-info: No such file or directory for /usr/share/info/gpgme.info.gz
by bugzilla_noreply＠novell.com 05 Jul '19

05 Jul '19

http://bugzilla.suse.com/show_bug.cgi?id=935339 Bug ID: 935339 Summary: gpgme fails to cleanly uninstall: install-info: No such file or directory for /usr/share/info/gpgme.info.gz Classification: openSUSE Product: openSUSE Factory Version: 201505* Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: gp(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Uninstalling gpgme, I get the following: 1 package to remove. After the operation, 355.3 KiB will be freed. Continue? [y/n/? shows all options] (y): y (1/1) Removing gpgme-1.5.5-1.1 .........................................................................................................[done] Additional rpm output: install-info: No such file or directory for /usr/share/info/gpgme.info.gz warning: %postun(gpgme-1.5.5-1.1.x86_64) scriptlet failed, exit status 1 # rpm -ql gpgme | grep info /usr/share/info/gpgme.info-1.gz /usr/share/info/gpgme.info-2.gz /usr/share/info/gpgme.info.gz This looks similar to bug #929415 and may have the same fix? -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 925561] New: NetworkManager should provide a way to designate any connection as a mobile data connection
by bugzilla_noreply＠novell.com 03 Jul '19

03 Jul '19

http://bugzilla.opensuse.org/show_bug.cgi?id=925561 Bug ID: 925561 Summary: NetworkManager should provide a way to designate any connection as a mobile data connection Classification: openSUSE Product: openSUSE Factory Version: 201503* Hardware: x86-64 OS: openSUSE 13.2 Status: NEW Severity: Enhancement Priority: P5 - None Component: Network Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: jrhodes(a)redpointsoftware.com.au QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Apper has an option in it's settings regarding when to automatically download and install updates. Under this setting there's an option "unless I am on a mobile data connection", which supposedly ensures that Apper doesn't download software updates while connected to a mobile (or metered) network. Unfortunately there doesn't appear to be any way in NetworkManager to designate a wireless or wired connection as being a mobile connection, i.e. a connection provided by a wireless hotspot or USB tethered phone. I'd really like to set Apper to automatically download and install updates as soon as they are available (I'm running on openSUSE Tumbleweed, which I believe is just Factory now?), but I can't do this because I occasionally have my laptop connected to my 4G hotspot, and I don't want to risk having packages download over 4G. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 914681] New: jing doesn't find Saxon extension
by bugzilla_noreply＠novell.com 01 Jul '19

01 Jul '19

http://bugzilla.suse.com/show_bug.cgi?id=914681 Bug ID: 914681 Summary: jing doesn't find Saxon extension Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: Other OS: Other Status: NEW Severity: Minor Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: thomas.schraitle(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- The jing package is used to validate an XML document with a RNG schema. When installing the jing package and running it without any options, you get: ----------------- $ rpm -q jing jing-20091111-19.1.3.noarch $ jing /usr/bin/build-classpath: error: Could not find saxon Java extension for this JVM /usr/bin/build-classpath: error: Some specified jars were not found Jing version 20091111 usage: java com.thaiopensource.relaxng.util.Driver [-i] [-c] [-s] [-t] [-C catalogFile] [-e encoding] RNGFile XMLFile... RELAX NG is a schema language for XML See http://relaxng.org/ for more information. ----------------- After investigating it, the respective line is this: BASE_JARS="jing xerces-j2 xml-commons-apis saxon xml-commons-resolver" This contains the list of all JAR files which is used by jing. However, "saxon" doesn't exist anymore, it should be "saxon6". The above line should be therefor look like this: BASE_JARS="jing xerces-j2 xml-commons-apis saxon6 xml-commons-resolver" -- You are receiving this mail because: You are on the CC list for the bug.

1 19

[Bug 941235] New: Upgrading to python-virtualenv-12.0.7-2.1 fails: cpio: rename
by bugzilla_noreply＠novell.com 01 Jul '19

01 Jul '19

http://bugzilla.opensuse.org/show_bug.cgi?id=941235 Bug ID: 941235 Summary: Upgrading to python-virtualenv-12.0.7-2.1 fails: cpio: rename Classification: openSUSE Product: openSUSE Factory Version: 201505* Hardware: All OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: robert.munteanu(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- When upgrading to Tumbleweed 20150807 I get the following error: (1/1) Installing: python-virtualenv-12.0.7-2.1 ...............................................................................[error] Installation of python-virtualenv-12.0.7-2.1 failed: Error: Subprocess failed. Error: RPM failed: error: unpacking of archive failed on file /usr/lib/python2.7/site-packages/virtualenv-1 2.0.7-py2.7.egg-info: cpio: rename error: python-virtualenv-12.0.7-2.1.noarch: install failed error: python-virtualenv-12.0.7-1.3.noarch: erase skipped Installed version is $ rpm -q python-virtualenv python-virtualenv-12.0.7-1.3.noarch -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 947161] New: Attempt the goal to have a default setup without any -32bit packages installed
by bugzilla_noreply＠novell.com 24 Jun '19

24 Jun '19

http://bugzilla.opensuse.org/show_bug.cgi?id=947161 Bug ID: 947161 Summary: Attempt the goal to have a default setup without any -32bit packages installed Classification: openSUSE Product: openSUSE Factory Version: 201505* Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: dimstar(a)opensuse.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- A standard x86_64 machine should not have to pull in any -32bit packages. Those are compatibility layers, generally provided for backwards compatibility with binary-only modules. The goal is to eliminate the installation of *-32bit by default (the goal is NOT to eliminate the presence of the *-32bit packages!) This might actually solve issues like ug 799367 as well -- You are receiving this mail because: You are on the CC list for the bug.

1 6