February 2014 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 663358] New: [zypper] can not install src rpm available on the local disk
by bugzilla_noreply＠novell.com 29 Jan '19

29 Jan '19

https://bugzilla.novell.com/show_bug.cgi?id=663358 https://bugzilla.novell.com/show_bug.cgi?id=663358#c0 Summary: [zypper] can not install src rpm available on the local disk Classification: openSUSE Product: openSUSE 11.4 Version: Factory Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: libzypp AssignedTo: zypp-maintainers(a)forge.provo.novell.com ReportedBy: ma(a)novell.com QAContact: qa(a)suse.de Found By: --- Blocker: --- While zypper in /tmp/my.rpm works by creating a temp. repo containing my.rpm, zypper si /tmp/my.src.rpm does not work. Probably possible to use the same trick here as for ordinary rpms. -- 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 2

[Bug 804607] New: wrong plymouth on multimonitor (and not visible cryptohome passphrase)
by bugzilla_noreply＠novell.com 17 Jan '19

17 Jan '19

https://bugzilla.novell.com/show_bug.cgi?id=804607 https://bugzilla.novell.com/show_bug.cgi?id=804607#c0 Summary: wrong plymouth on multimonitor (and not visible cryptohome passphrase) Classification: openSUSE Product: openSUSE Factory Version: 12.3 Beta 1 Platform: All OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: noga.dany(a)gmail.com QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:18.0) Gecko/20100101 Firefox/18.0 When booting on two monitors, plymouth animation on second monitor is displaced. And therefore is not visible request for passphrase for accessing encrypted disk. On openSUSE 12.2 is ok. Primary monitor 1600 x 900, secondary monitor 1920 x 1080 (bug found in update in RC1, but I can't set it here in bug report options) Reproducible: Always Steps to Reproduce: 1. Start boot with connected second monitor Actual Results: Wrong plymouth animation on second monitor. Is displaced cca about 10% more left and more down. Expected Results: Good position like in openSUSE 12.2 -- 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 5

[Bug 831921] New: unison segfaults when I try to choose a local directory
by bugzilla_noreply＠novell.com 13 Jan '19

13 Jan '19

https://bugzilla.novell.com/show_bug.cgi?id=831921 https://bugzilla.novell.com/show_bug.cgi?id=831921#c0 Summary: unison segfaults when I try to choose a local directory Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: x86-64 OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: ncutler(a)suse.com QAContact: qa-bugs(a)suse.de Found By: IS&T Blocker: --- I have unison version 2.40.102-2.1.2 installed on openSUSE 12.3 (KDE, fully updated). When I run it and try to add a profile via the "Profile Creation" wizard a.k.a. Unison Profile Creation Assistant, it segfaults when I attempt to choose a local directory. The directory chooser window (which I assume is not a part of unison) flashes on the screen for a split-second. /var/log/messages says: pantograf kernel: [ 649.287711] unison[9180]: segfault at 30 ip 00007ffda011c958 sp 00007fff5cce51a0 error 4 in libgtk-x11-2.0.so.0.2400.18[7ffd9ff01000+42c000] and when I run unison in a bash shell, I get the following messages on-screen: (unison:9217): Gtk-CRITICAL **: gtk_tree_model_filter_get_value: assertion `GTK_TREE_MODEL_FILTER (model)->priv->stamp == iter->stamp' failed (unison:9217): GLib-GObject-WARNING **: gtype.c:4204: type id `0' is invalid (unison:9217): GLib-GObject-WARNING **: can't peek value table for type `<invalid>' which is not currently referenced Segmentation fault Thanks. Nathan -- 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 10

[Bug 805767] New: huge plymouth theme in initrd
by bugzilla_noreply＠novell.com 25 Nov '18

25 Nov '18

https://bugzilla.novell.com/show_bug.cgi?id=805767 https://bugzilla.novell.com/show_bug.cgi?id=805767#c0 Summary: huge plymouth theme in initrd Classification: openSUSE Product: openSUSE 12.3 Version: RC 1 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: tittiatcoke(a)gmail.com ReportedBy: lnussel(a)suse.com QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- There are 23MB of pylmouth theme files in the initrd. Maybe there is a way to omit some files to shrink the total size of initrd making boot even faster. -- 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 5

[Bug 629374] New: desktop-data-openSUSE contains some KDE-specific bits
by bugzilla_noreply＠novell.com 25 Nov '18

25 Nov '18

http://bugzilla.novell.com/show_bug.cgi?id=629374 http://bugzilla.novell.com/show_bug.cgi?id=629374#c0 Summary: desktop-data-openSUSE contains some KDE-specific bits Classification: openSUSE Product: openSUSE 11.4 Version: Factory Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE4 Workspace AssignedTo: kde-maintainers(a)suse.de ReportedBy: vuntz(a)novell.com QAContact: qa(a)suse.de Found By: --- Blocker: --- Here are some bits in desktop-data-openSUSE that should probably live in some of the kde branding packages (or in qt): + etc/kde4/: contains kdm/backgroundrc (should live in kdm-branding-openSUSE) + etc/profile.d/desktop-data.* and usr/share/desktop-data: the scripts have a line to set QT_SYSTEM_DIR to /usr/share/desktop-data. This should really live in a qt package. I'm also wondering about everything in etc/xdg/menus/, usr/share/desktop-directories/ and usr/share/icons/: this contains the XDG menu structure, except that GNOME now uses something else since we were not happy with this structure and were unable to make any real progress on changing it. LXDE also doesn't use it. So it's now more or less KDE-specific... Finally, etc/skel/ contains public_html. Is this something you want to keep? I know it annoys me to have this directory created. -- 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 9

[Bug 803057] New: PostgreSQL 9.2.3, 9.1.8, 9.0.12, 8.4.16 and 8.3.23 released
by bugzilla_noreply＠novell.com 23 Oct '18

23 Oct '18

https://bugzilla.novell.com/show_bug.cgi?id=803057 https://bugzilla.novell.com/show_bug.cgi?id=803057#c0 Summary: PostgreSQL 9.2.3, 9.1.8, 9.0.12, 8.4.16 and 8.3.23 released Classification: openSUSE Product: openSUSE 12.2 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Security AssignedTo: security-team(a)suse.de ReportedBy: lijewski.stefan(a)zabka.pl QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:18.0) Gecko/20100101 Firefox/18.0 >From postgresql.org: The PostgreSQL Global Development Group has released a security update to all current versions of the PostgreSQL database system, including versions 9.2.3, 9.1.8, 9.0.12, 8.4.16, and 8.3.23. This update fixes a denial-of-service (DOS) vulnerability. All users should update their PostgreSQL installations as soon as possible. The security issue fixed in this release, CVE-2013-0255, allows a previously authenticated user to crash the server by calling an internal function with invalid arguments. This issue was discovered by independent security researcher Sumit Soni this week and reported via Secunia SVCRP, and we are grateful for their efforts in making PostgreSQL more secure. Today's update also fixes a performance regression which caused a decrease in throughput when using dynamic queries in stored procedures in version 9.2. Applications which use PL/pgSQL's EXECUTE are strongly affected by this regression and should be updated. Additionally, we have fixed intermittent crashes caused by CREATE/DROP INDEX CONCURRENTLY, and multiple minor issues with replication. Reproducible: Always -- 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 6

[Bug 820566] New: wireshark security updates to 1.8.7 and 1.6.15
by bugzilla_noreply＠novell.com 19 Oct '18

19 Oct '18

https://bugzilla.novell.com/show_bug.cgi?id=820566 https://bugzilla.novell.com/show_bug.cgi?id=820566#c0 Summary: wireshark security updates to 1.8.7 and 1.6.15 Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: All OS/Version: openSUSE 12.3 Status: NEW Severity: Normal Priority: P5 - None Component: Security AssignedTo: security-team(a)suse.de ReportedBy: Andreas.Stieger(a)gmx.de QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux i686; rv:20.0) Gecko/20100101 Firefox/20.0 https://www.wireshark.org/docs/relnotes/wireshark-1.8.7.html wnpa-sec-2013-23 CVE-2013-2486 CVE-2013-2487 The RELOAD dissector could go into an infinite loop. wnpa-sec-2013-24 The GTPv2 dissector could crash. wnpa-sec-2013-25 The ASN.1 BER dissector could crash. wnpa-sec-2013-26 The PPP CCP dissector could crash. wnpa-sec-2013-27 The DCP ETSI dissector could crash. wnpa-sec-2013-28 The MPEG DSM-CC dissector could crash. wnpa-sec-2013-29 The Websocket dissector could crash. wnpa-sec-2013-30 The MySQL dissector could go into an infinite loop. wnpa-sec-2013-31 The ETCH dissector could go into a large loop. https://www.wireshark.org/docs/relnotes/wireshark-1.6.15.html 1.6.15 wnpa-sec-2013-25 The ASN.1 BER dissector could crash Reproducible: Always Steps to Reproduce: 1. 2. 3. -- 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 15

[Bug 800701] New: X windows is corrupt after logging in on an AMD A10-5800K APU
by bugzilla_noreply＠novell.com 31 Jul '18

31 Jul '18

https://bugzilla.novell.com/show_bug.cgi?id=800701 https://bugzilla.novell.com/show_bug.cgi?id=800701#c0 Summary: X windows is corrupt after logging in on an AMD A10-5800K APU Classification: openSUSE Product: openSUSE Factory Version: 12.3 Beta 1 Platform: x86-64 OS/Version: Other Status: NEW Severity: Critical Priority: P5 - None Component: Xen AssignedTo: jdouglas(a)suse.com ReportedBy: ajbiii(a)comcast.net QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:7.0.1) Gecko/20100101 Firefox/7.0.1 Installed 12.3. The regular kernel and X windows works fine. Reboot to the xen kernel. The login screen is displayed correctly. After logging in, the display is corrupt. The mouse pointer is ok and I can see that the menu is active by putting the cursor in the lower left corner and clicking but the display is unusable. Just an aside: The xen kernel wouldn't even boot on the APU with 12.1 or 12.2. Reproducible: Always Steps to Reproduce: 1. Install 12.3 on an AMD Trinity APU. 2. Boot regular kernel, log in and verify X is working. 3. Reboot with the xen kernel. 4. Log in and observe the corruption Actual Results: Screen is corrupt Expected Results: Normal X windows operation -- 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 23

[Bug 848914] New: Publish Information around Partitioning Requirements of Boot Requirements with UEFI BIOS
by bugzilla_noreply＠novell.com 19 Jun '18

19 Jun '18

https://bugzilla.novell.com/show_bug.cgi?id=848914 https://bugzilla.novell.com/show_bug.cgi?id=848914#c0 Summary: Publish Information around Partitioning Requirements of Boot Requirements with UEFI BIOS Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: x86-64 OS/Version: openSUSE 12.3 Status: NEW Severity: Enhancement Priority: P5 - None Component: Installation AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: secure(a)aphofis.com QAContact: jsrain(a)suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 If ever we are going to see changed in PC BIOS's it will be in this decade. Current UEFI BIOS's are standard with most all X_64 Motherboards. The UEFI BIOS is a temporary measure to permit backwardly compatible Processors and Motherboards and my enhancement would be to publish partitioning information on screen thats not an option before the partitioning phase of Installation. Current warnings generated by the Partitioner itself do warn of requirements for /boot/uefi with FAT. As there will be many changes to BIOS this decade I think we need a mandatory full screen explanation of partitioning changes that can be written for all coming versions as it will be needed and under that preface every installation from 13.x to anything can all make use of a text screen before the partitioner is displayed on screen as part of every Installation Reproducible: Always Steps to Reproduce: 1. Try to configure a boot partition with an X_64 UEFI BIOS and a warning is generated on the users final acceptance of the chosen partitioning. 2. The warning is too late and there is not sufficient space to provide detailed instructions and the reasoning and its going to get more problematic. Additionally as soon as M.S come out with a new file formation partitioning we will need to spell partitioning out in a clear concise way before the user does anything with the partitioner 3. Expected Results: Its a small and advantages addition to the Install Program to have a text screen available before the partitioning part of our current installation is reached. Currently we only knock back the partitioning with a warning after the partitioner has been used. It needs full explanation before not a single line after. It should be very easy to implement this text screen as the need far outweighs the man hour time factor it would take to implement above. I believe this should be assigned and completed as an urgent undertaking before we ship another version as its benefit now and future is so very important. -- 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 2

[Bug 813340] New: Suspected memory corruption in standard capi20 lib
by bugzilla_noreply＠novell.com 17 Jun '18

17 Jun '18

https://bugzilla.novell.com/show_bug.cgi?id=813340 https://bugzilla.novell.com/show_bug.cgi?id=813340#c0 Summary: Suspected memory corruption in standard capi20 lib Classification: openSUSE Product: openSUSE Factory Version: 13.1 Milestone 0 Platform: x86-64 OS/Version: openSUSE 12.3 Status: NEW Severity: Normal Priority: P5 - None Component: Network AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: jan.fengler(a)adviqo.com QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.31 (KHTML, like Gecko) Chrome/26.0.1410.43 Safari/537.31 The capi20 lib from the i4l-base source-package from http://download.opensuse.org/repositories/home:/kkeil:/ISDN/openSUSE_Factor… (and also Version 3.23-100.1 which is newer) seems to create memory corruption during capi20_put_message sending data_b3_req, because no memory is assigned for the data that is put behind the original message in the function capi_processMessage (capi20.c row 962ff). Unfortunately this seems to be a private function and so i could not easily write a test against the entire lib. Reproducible: Always Steps to Reproduce: I provide an example program that uses a 1:1 copy of the original function. I use capi via JNI from Java and it crashes when freeing memory exactly as the test program does. Actual Results: Memory corruption when freeing the memory used for the data_b3_req-message. Expected Results: No memory corruption, the program should terminate without a problem. The last known working version (from openSuSE 10.3) assigned memory for SND_BUFSIZ bytes and copied the original message to this before copying the data bytes after the message and that worked. I will change the code of the function standardPutMessage to do this to avoid the problem and add a patch to this bug report if it works with the patch. I must admit that i could have overseen something, but unfortunately it seems not so far. -- 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 9