December 2015 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 905034] New: scanimage produces wrong colours in scan
by bugzilla_noreply＠novell.com 15 Dec '17

15 Dec '17

http://bugzilla.opensuse.org/show_bug.cgi?id=905034 Bug ID: 905034 Summary: scanimage produces wrong colours in scan Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: per(a)computer.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 613296 --> http://bugzilla.opensuse.org/attachment.cgi?id=613296&action=edit scanimage output, resolution 150 Hardware: lenovo desktop12. Running vanilla openSUSE 13.2 via NFS root. Doing a scan like these: scanimage --mode color --resolution 300 >office12-scan1.pnm scanimage --mode color --resolution 300 >office12-scan2.pnm produces some pretty weird colours, see attached. Omitting the resolution argument or specifying "--resolution 50" both lead to a "Error in `scanimage': double free or corruption (top): ". I have sane-backends-1.0.24-2.1.10.x86_64 installed. -- You are receiving this mail because: You are on the CC list for the bug.

1 41

[Bug 916773] New: unexpected fd0/floppy messages on tty[1-6]
by bugzilla_noreply＠novell.com 15 Dec '17

15 Dec '17

http://bugzilla.opensuse.org/show_bug.cgi?id=916773 Bug ID: 916773 Summary: unexpected fd0/floppy messages on tty[1-6] Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: mrmazda(a)earthlink.net QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 622338 --> http://bugzilla.opensuse.org/attachment.cgi?id=622338&action=edit Tumbleweed y2logs from host gx760 To reproduce: 1-log in on any of tty[1-6] on system with empty floppy drive 2a-fdisk -l; or 2b-hwinfo --[cdrom|disk|ide|partition|redasd|scsi] # pick any one Actual results: 1-expected command output; plus 2-(e.g.) [ 565.922030] blk_update_request: I/O error, dev fd0, sector 0 [ 565.922903] floppy: error -5 while reading block 0 [ 565.949031] blk_update_request: I/O error, dev fd0, sector 0 [ 565.949927] floppy: error -5 while reading block 0 Expected results: 1-expected command output # (only) Notes: 1-Happens with 3.16.7 on 13.2 and 3.18.3 and 3.19.rc7 on Tumbleweed 2-only happens on two (4 installations) of four (8 installations) real hardware multiboot hosts tested (gx760 w/ ICH10D SATA; fi965 w/ ICH8R SATA using mdraid ), not on hosts big41 (NM10/ICH7 SATA) or gx28c (ICH6 SATA) 3-sometimes litter precedes, sometimes follows, sometimes mixed among expected command output, depending on output expected 4-/proc/partitions on 13.2 and TW contain fd0. /proc/partitions on 13.1 using 3.11.10, and Rawhide using 3.19.rc7 do not contain fd0. -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 937811] New: lxmusic doesn't play sample sound file
by bugzilla_noreply＠novell.com 13 Dec '17

13 Dec '17

http://bugzilla.opensuse.org/show_bug.cgi?id=937811 Bug ID: 937811 Summary: lxmusic doesn't play sample sound file Classification: openSUSE Product: openSUSE Factory Version: 201505* Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Sound Assignee: tiwai(a)suse.com Reporter: maikwagner(a)yahoo.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Hello everyone, I know that this is not a support forum but I would like to report that lxmusic doesn't play the sample file on my system. I got some information when running it from console and it says that the output plugin is not loaded. mwagner@linux-kw69:~> lxmusic ** (lxmusic:3958): WARNING **: on_playback_volume_changed: couldn't get volume, output plugin not loaded ** (lxmusic:3958): WARNING **: Server Quit mwagner@linux-kw69:~> /sbin/lspci | grep Audio 00:01.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Wrestler HDMI Audio 00:14.2 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 Azalia (Intel HDA) (rev 40) What kind of further information would you need? It is a custom built PC I built myself. The audio cable had two ends, is this a hardware or software issue? I tried both the front and back green-audio jack. Regards, Maik -- You are receiving this mail because: You are on the CC list for the bug.

1 14

[Bug 958073] New: Libsodium 1.0.0 has a crash bug in it
by bugzilla_noreply＠novell.com 13 Dec '17

13 Dec '17

http://bugzilla.opensuse.org/show_bug.cgi?id=958073 Bug ID: 958073 Summary: Libsodium 1.0.0 has a crash bug in it Classification: openSUSE Product: openSUSE 13.1 Version: Final Hardware: All OS: openSUSE 12.1 Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: security-team(a)suse.de Reporter: alanr(a)unix.sh QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I was discussing this with Lars Mueller <lmuelle(a)suse.com> and he suggested filing this bug report. When encrypting, libsodium 1.0.0 reads two more bytes from the key (or buffer?) than I told it to. Those bytes don't go into the crypto stream and don't affect the results. If that key is exactly at the end of a page, and the next page in your address space isn't there (isn't valid), then you will crash. Otherwise it's completely harmless. I would recommend just upgrading 12.1 to 1.0.1. That will fix it. Or you could figure out where the fix was and bring it forward. I test my code under valgrind, which is where I found this problem. I noticed this problem when porting my code to openSUSE, since I had previously marked 1.0.0 as "too old" a version in my specfile just to avoid this bug. This bug causing a crash is very unlikely, but possible. I found the problem before 1.0.1 had come out, so I had to put in the workaround in my valgrind tests. So, I would only care if one of my customers crashed as a result. Again, it's very unlikely, but possible. There have been no API changes that I've noticed at least up until 1.0.5. I've tested with most of versions along the way. Not extensively, but enough to know that they work fine for me and I haven't had to change my code at all. In fact, I've never had to change my code for libsodium versions. For what it's worth, the libsodium people have a pretty good set of tests. The package I'm using this with is the Assimilation Suite http://AssimilationSystems.com/ - and I'm trying to get it going under openSUSE as per a customer's request. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 906067] New: Totem SEGFAULT with .avi movies
by bugzilla_noreply＠novell.com 12 Dec '17

12 Dec '17

http://bugzilla.opensuse.org/show_bug.cgi?id=906067 Bug ID: 906067 Summary: Totem SEGFAULT with .avi movies Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: x86-64 OS: Other Status: NEW Severity: Major Priority: P5 - None Component: GNOME Assignee: bnc-team-gnome(a)forge.provo.novell.com Reporter: roger.luedecke(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Originally Totem would play .avi withoug video; audio only. I then installed the Fluendo Codec Pack. Now thumbnails display in Totem and Nautilus. Both Nautilus preview and Totem instantly crash when attempting to play video in .avi. When run from CLI Totem reports a SEGFAULT. Likely related bug reports: https://bugzilla.opensuse.org/show_bug.cgi?id=887781 https://bugzilla.opensuse.org/show_bug.cgi?id=848833 -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 904551] New: Totem could not startup
by bugzilla_noreply＠novell.com 12 Dec '17

12 Dec '17

http://bugzilla.opensuse.org/show_bug.cgi?id=904551 Bug ID: 904551 Summary: Totem could not startup Classification: openSUSE Product: openSUSE 13.1 Version: Final Hardware: x86-64 OS: openSUSE 13.1 Status: NEW Severity: Normal Priority: P5 - None Component: GNOME Assignee: bnc-team-gnome(a)forge.provo.novell.com Reporter: whoknows2012(a)myopera.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Totem vserion: 3.10.1 Error message: Some necessary plug-ins are missing. Make sure that the program is correctly installed. Nothing that I found in the Internet is working. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 509945] New: Enforce packaging of static libraries by rpmlint check
by bugzilla_noreply＠novell.com 08 Dec '17

08 Dec '17

http://bugzilla.novell.com/show_bug.cgi?id=509945 Summary: Enforce packaging of static libraries by rpmlint check Classification: openSUSE Product: openSUSE 11.2 Version: Factory Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: dmueller(a)novell.com ReportedBy: prusnak(a)novell.com QAContact: qa(a)suse.de CC: ro(a)novell.com, mrueckert(a)novell.com, crrodriguez(a)novell.com Found By: Development We are trying to adopt the static libraries packaging scheme described on http://en.opensuse.org/Packaging/Guidelines#Packaging_Static_Libraries By adding rpmlint check we will enforce the correct packaging. rpmlint should check whether the package contains *.{a,la} files and perform these steps: a) package contains *.la files, does not contain *.a files -> throw error suggesting the packager to remove *.la files in %install phase b) package contains only *.la and *.a files -> check if the name ends with "-devel-static", throw error otherwise, suggesting the rename c) package contains *.la, *.a files AND *.so files (and probably some includes) -> check if the name ends with "-devel" AND package also provides "-devel-static" symbol, throw error otherwise, suggesting the addition of symbol -> also point out that packager has to be sure that static libraries are absolutely needed in the system. If not the package should be built with --disable-static and *.la files removed in %install phase -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 8

[Bug 884004] New: bzip2 -dcf skips the first block if fed uncompressed data
by bugzilla_noreply＠novell.com 08 Dec '17

08 Dec '17

https://bugzilla.novell.com/show_bug.cgi?id=884004 https://bugzilla.novell.com/show_bug.cgi?id=884004#c0 Summary: bzip2 -dcf skips the first block if fed uncompressed data Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: jnweiger(a)gmail.com QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- $ echo hello world | bzip2 -dcf returns nothing. I'd expect to see 'hello world'. According to the manual, the effects of -f include: "bzip2 normally declines to decompress files which don't have the correct magic header bytes. If forced (-f), however, it will pass such files through unmodified. This is how GNU gzip behaves. strace includes: read(0, "hello world\n", 4096) = 12 read(0, "", 4096) = 0 lseek(0, 0, SEEK_SET) = -1 ESPIPE (Illegal seek) read(0, "", 4096) = 0 close(0) = 0 I assume, the failing lseek() should be acted on. Possibly already an upstream issue? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 7

[Bug 709260] New: package bzip2 missing documentation
by bugzilla_noreply＠novell.com 08 Dec '17

08 Dec '17

https://bugzilla.novell.com/show_bug.cgi?id=709260 https://bugzilla.novell.com/show_bug.cgi?id=709260#c0 Summary: package bzip2 missing documentation Classification: openSUSE Product: openSUSE 11.4 Version: Final Platform: i686 OS/Version: openSUSE 11.4 Status: NEW Severity: Minor Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: giecrilj(a)stegny.2a.pl QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 5.1; Trident/4.0; GTB7.1) The documentation for package bzip2 is not installed. Reproducible: Always Steps to Reproduce: 1. Read /usr/share/doc/packages/bzip2/README. 2. Find the referenced documentation. Actual Results: 1. Complete documentation is available in Postscript form (manual.ps), PDF (manual.pdf) or html (manual.html). A plain-text version of the manual page is available as bzip2.txt. 2. Nope. Expected Results: 2. /usr/share/doc/packages/bzip2/manual.html -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 4

[Bug 955428] New: Installation of xmlcharent-0.3-427.1 shows error
by bugzilla_noreply＠novell.com 08 Dec '17

08 Dec '17

http://bugzilla.opensuse.org/show_bug.cgi?id=955428 Bug ID: 955428 Summary: Installation of xmlcharent-0.3-427.1 shows error 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: freek(a)opensuse.org QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- Installation of xmlcharent-0.3-427.1 shows the following error: Additional rpm output: I/O error : Attempt to load network entity http://www.oasis-open.org/committees/entity/release/1.0/catalog.dtd /etc/xml/catalog:2: warning: failed to load external entity "http://www.oasis-open.org/committees/entity/release/1.0/catalog.dtd" V1.0//EN" "http://www.oasis-open.org/committees/entity/release/1.0/catalog.dtd" ^ sgml-register-catalog: addition of /usr/share/xmlcharent/xmlcharent.sgml in /etc/sgml/catalog -- You are receiving this mail because: You are on the CC list for the bug.

1 3