November 2012 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 615361] New: Qt Creator doesnt handle threads with gdb
by bugzilla_noreply＠novell.com 15 Apr '16

15 Apr '16

http://bugzilla.novell.com/show_bug.cgi?id=615361 http://bugzilla.novell.com/show_bug.cgi?id=615361#c0 Summary: Qt Creator doesnt handle threads with gdb Classification: openSUSE Product: openSUSE 11.3 Version: Factory Platform: x86-64 OS/Version: openSUSE 11.3 Status: NEW Severity: Major Priority: P5 - None Component: Development AssignedTo: pth(a)novell.com ReportedBy: highwaystar.ru(a)gmail.com QAContact: qa(a)suse.de Found By: --- Blocker: --- Created an attachment (id=369956) --> (http://bugzilla.novell.com/attachment.cgi?id=369956) Screenshot of Qt Creator from factory works wrong with gdb and cant display threads User-Agent: Mozilla/5.0 (X11; U; Linux; ru-RU) AppleWebKit/532.4 (KHTML, like Gecko) Arora/0.10.2 Safari/532.4 Current version of Qt Creator from factory cant handle threads in debugged applications Reproducible: Always Steps to Reproduce: 1. Install current factory of m7,rc1 2. Install Qt Creator and gdb 3. Try to debug an program 4. Pause debugged program and look to threads windows Actual Results: Threads not displayed, navigation by threads not avaliable Expected Results: Threads should be displayed in Threads window Problem caused by Qt Creator. It cant parse SUSE gdb version, that reports now as "GNU gdb (GDB) SUSE (7.1-2.4)". gdb rebuilded without additional suffix works well with qt creator. There are bug for Qt Creator upstream http://bugreports.qt.nokia.com/browse/QTCREATORBUG-1490?page=com.atlassian.… and commit fixing that problem: http://qt.gitorious.org/qt-creator/qt-creator/commit/5afeaa7 this should parse SUSE gdb well -- 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 4

[Bug 615223] New: ImageMagick cannot compress grayscale TIFF images with JPEG
by bugzilla_noreply＠novell.com 15 Apr '16

15 Apr '16

http://bugzilla.novell.com/show_bug.cgi?id=615223 http://bugzilla.novell.com/show_bug.cgi?id=615223#c0 Summary: ImageMagick cannot compress grayscale TIFF images with JPEG Classification: openSUSE Product: openSUSE 11.3 Version: Factory Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: suse(a)bugs.jan.ritzerfeld.net QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Opera/9.80 (X11; Linux x86_64; U; de) Presto/2.5.29 Version/10.60 ImageMagick-6.6.1-0 cannot compress grayscale TIFF images with JPEG. This seems to be fixed since ImageMagick-6.6.1-5: http://www.imagemagick.org/discourse-server/viewtopic.php?f=3&t=16064#p58060 Reproducible: Always Steps to Reproduce: 1. 2. 3. -- 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 28

[Bug 615073] New: Differing fuzz handling between rpmbuild and quilt
by bugzilla_noreply＠novell.com 15 Apr '16

15 Apr '16

http://bugzilla.novell.com/show_bug.cgi?id=615073 http://bugzilla.novell.com/show_bug.cgi?id=615073#c0 Summary: Differing fuzz handling between rpmbuild and quilt Classification: openSUSE Product: openSUSE 11.3 Version: Factory Platform: Other OS/Version: Other Status: NEW Severity: Enhancement Priority: P5 - None Component: Development AssignedTo: jdelvare(a)novell.com ReportedBy: pth(a)novell.com QAContact: qa(a)suse.de CC: mrueckert(a)novell.com Found By: Development Blocker: --- patch fuzz configuration for rpmbuild happens via _default_patch_fuzz which is normally set in /usr/lib/rpm/macros whereas for quilt you set it in your ~/.quiltrc. Now the patch in factory defaults to fuzz=0 so you have to change it to the old default of 2 for packages from older distributions in order to be able to set them up with quilt. It's cumbersome that you have to edit two places to achieve this, one of them being /usr/lib/rpm/macros which is only writable by root. I'd propose to have an extra configuration var for quiltrc which passes --fuzz=<value> to patch *and* sets _default_patch_fuzz to the same value in the configuration it passes to rpmbuild. -- 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 11

[Bug 615044] New: gdm greeter doesn't work without local users (e.g. NIS)
by bugzilla_noreply＠novell.com 15 Apr '16

15 Apr '16

http://bugzilla.novell.com/show_bug.cgi?id=615044 http://bugzilla.novell.com/show_bug.cgi?id=615044#c0 Summary: gdm greeter doesn't work without local users (e.g. NIS) Classification: openSUSE Product: openSUSE 11.3 Version: Factory Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: GNOME AssignedTo: vuntz(a)novell.com ReportedBy: lnussel(a)novell.com QAContact: qa(a)suse.de Found By: --- Blocker: --- my system is configured for NIS so doesn't have any local users besides root. The gdm greeter in this case only shows a lone 'login' button and the waiting curser but is empty otherwise. Ie there is no way to enter a user name. Pressing the login button leads to X restart. Simply adding one local user makes the button to manually enter a user name show up. FWIW I used the minimal X selection+gdm for installation so no full gnome session available, only the pkgs that got installed via deps. -- 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 11

[Bug 614779] New: Adding a printer requires the root password 7 times
by bugzilla_noreply＠novell.com 15 Apr '16

15 Apr '16

http://bugzilla.novell.com/show_bug.cgi?id=614779 http://bugzilla.novell.com/show_bug.cgi?id=614779#c0 Summary: Adding a printer requires the root password 7 times Classification: openSUSE Product: openSUSE 11.3 Version: Factory Platform: Other OS/Version: Other Status: NEW Severity: Critical Priority: P5 - None Component: GNOME AssignedTo: bnc-team-gnome(a)forge.provo.novell.com ReportedBy: stshaw(a)novell.com QAContact: qa(a)suse.de Found By: --- Blocker: --- This is absurd at the very least. Having to put my password in 2 times just to bring up the print adding tool from control center is dumb, but to put my password in 5 times to finish the printer add is just plain absurd! -- 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 21

[Bug 614774] New: Adding a printer crashes when it tries to find drivers
by bugzilla_noreply＠novell.com 15 Apr '16

15 Apr '16

http://bugzilla.novell.com/show_bug.cgi?id=614774 http://bugzilla.novell.com/show_bug.cgi?id=614774#c0 Summary: Adding a printer crashes when it tries to find drivers Classification: openSUSE Product: openSUSE 11.3 Version: Factory Platform: Other OS/Version: Other Status: NEW Severity: Critical Priority: P5 - None Component: GNOME AssignedTo: bnc-team-gnome(a)forge.provo.novell.com ReportedBy: stshaw(a)novell.com QAContact: qa(a)suse.de Found By: --- Blocker: --- Created an attachment (id=369575) --> (http://bugzilla.novell.com/attachment.cgi?id=369575) Screenshot of crash When adding a network printer and it goes to find a driver it crashes when trying to talk to packagekit. 1. Control Center 2. Printing 3. Add 4. Expand Network Printer 5. Click on Find Network Printer 6. Select one of the printers that appears 7. Click Forward 8. Experience a gpk-dbus-service crash :) -- 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 3

[Bug 614748] New: new default wallpaper not shown
by bugzilla_noreply＠novell.com 15 Apr '16

15 Apr '16

http://bugzilla.novell.com/show_bug.cgi?id=614748 http://bugzilla.novell.com/show_bug.cgi?id=614748#c0 Summary: new default wallpaper not shown Classification: openSUSE Product: openSUSE 11.3 Version: Factory Platform: Other OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: KDE4 Workspace AssignedTo: kde-maintainers(a)suse.de ReportedBy: wstephenson(a)novell.com QAContact: qa(a)suse.de Found By: Development Blocker: --- Due to a change in the caching logic, the new wallpaper in 11.3 is not detected if the user did not change from the default 11.2 wallpaper. -- 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 2

[Bug 614670] New: XFS crash with stack corruption, with bugfix by XFS devs
by bugzilla_noreply＠novell.com 15 Apr '16

15 Apr '16

http://bugzilla.novell.com/show_bug.cgi?id=614670 http://bugzilla.novell.com/show_bug.cgi?id=614670#c0 Summary: XFS crash with stack corruption, with bugfix by XFS devs Classification: openSUSE Product: openSUSE 11.2 Version: Final Platform: x86-64 OS/Version: openSUSE 11.2 Status: NEW Severity: Normal Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers(a)forge.provo.novell.com ReportedBy: novell-web(a)zmi.at QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; de; rv:1.9.2.3) Gecko/20100401 SUSE/3.6.3-1.2 Firefox/3.6.3 I've suffered twice now from an XFS bug with the default openSUSE 11.2 kernel version 2.6.31.12-0.2-xen (VM running on XenServer). The kernel crashed. Christoph Hellwig (XFS dev) wrote back today (2010-Jun-16 11:41): ************** Try backporting commit 070ecdca54dde9577d2697088e74e45568f48efb "xfs: skip writeback from reclaim context", that should get rid of places calling into ->writepage with already deep stack usage. ************** As this is a Novell/openSUSE kernel, could you please provide the fix? Reproducible: Sometimes Steps to Reproduce: 1. have XFS filesystem 2. Once I did: I just rsynced from another server to this one, the filesystem is nearly full, I was in the process of vgextend (done), lvextend (done) and just wanted to call xfs_growfs but before I could press enter the system was gone. It's a VM within XenServer, if that matters. 3. Today it crashed while running rsync from a PC to that server, while in the process of syncing the file list. Actual Results: kernel crash Expected Results: should not crash :-) -- 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 6

[Bug 614316] New: amavisd-new: amavisd-new/README.SuSE does not match /etc/amavisd.conf
by bugzilla_noreply＠novell.com 15 Apr '16

15 Apr '16

http://bugzilla.novell.com/show_bug.cgi?id=614316 http://bugzilla.novell.com/show_bug.cgi?id=614316#c0 Summary: amavisd-new: amavisd-new/README.SuSE does not match /etc/amavisd.conf Classification: openSUSE Product: openSUSE 11.3 Version: Factory Platform: Other OS/Version: openSUSE 11.3 Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: bjoern(a)cs.tu-berlin.de QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux i686; de-AT; rv:1.8.1.23) Gecko/20090912 SUSE/1.1.18-2.1 SeaMonkey/1.1.18 Mnenhy/0.7.6.666 The are some hints for using Amavisd-new together with Sendmail (Milter) in /usr/share/doc/packages/amavisd-new/README.SuSE: [...] NOTE: If you DO NOT HAVE any VIRUS scanner installed, amavisd-new will not work per default! If you ONLY want spamfiltering WITHOUT any virusscanning, search for "@bypass_virus_checks_acl" in /etc/amavisd.conf and remove the comment sign. [...] But there is no match for "@bypass_virus_checks_acl" in /etc/amavisd.conf. [...] - if you want to use sendmail instead of postfix, set AMAVIS_SENDMAIL_MILTER="yes" in /etc/sysconfig/amavis and restart amavisd using rcamavis restart. Additionally you have to edit /etc/amavisd.conf and remove the comment sign of the following two lines: $forward_method = undef; $notify_method = 'pipe:flags=q argv=/usr/sbin/sendmail -Ac -i -odd -f ${sender} -- ${recipient}'; just search for "MILTER", and you will find them. [...] But there are no such lines in /etc/amavisd.conf. If I search for "MILTER", I only get some lower-case matches: [...] $unix_socketname = "$MYHOME/amavisd.sock"; # amavisd-release or amavis-milter # option(s) -p overrides $inet_socket_port and $unix_socketname [...] # Use with amavis-release over a socket or with Petr Rehor's amavis-milter.c # (with amavis-milter.c from this package or old amavis.c client use 'AM.CL'): $policy_bank{'AM.PDP-SOCK'} = { protocol => 'AM.PDP', auth_required_release => 0, # do not require secret_id for amavisd-release }; [...] # $notify_method = 'smtp:[127.0.0.1]:10025'; # $forward_method = 'smtp:[127.0.0.1]:10025'; # set to undef with milter! [...] # # NOTE: If using amavis-milter, change length to: # # length("$TEMPBASE/amavis-milter-xxxxxxxxxxxxxx/parts/pxxx"). [...] In /usr/share/doc/packages/amavisd-new-docs/amavisd.conf-sample there are matches for "MILTER". But uncommenting and inserting the lines # SENDMAIL MILTER, using amavis-milter.c helper program: #$forward_method = undef; # no explicit forwarding, sendmail does it by itself # milter; option -odd is needed to avoid deadlocks #$notify_method = 'pipe:flags=q argv=/usr/sbin/sendmail -Ac -i -odd -f ${sender} -- ${recipient}'; # just a thought: can we use use -Am instead of -odd ? does not seem to configure a working Amavis/Sendmail system. The documentation file /usr/share/doc/packages/amavisd-new/README.SuSE should be checked. May be also /etc/amavisd.conf should be checked. The problem was tested with the following package versions from openSUSE 11.3: amavisd-new-2.6.4-3.4.i586 amavisd-new-docs-2.6.4-3.4.i586 The same problem can be found in openSUSE 11.2 and in SLES-11. Reproducible: Always -- 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 4

[Bug 614208] New: Choppy effects with fglrx workaround enabled
by bugzilla_noreply＠novell.com 15 Apr '16

15 Apr '16

http://bugzilla.novell.com/show_bug.cgi?id=614208 http://bugzilla.novell.com/show_bug.cgi?id=614208#c0 Summary: Choppy effects with fglrx workaround enabled Classification: openSUSE Product: openSUSE 11.3 Version: Factory Platform: x86-64 OS/Version: openSUSE 11.3 Status: NEW Severity: Normal Priority: P5 - None Component: Compiz AssignedTo: bnc-team-compiz(a)forge.provo.novell.com ReportedBy: badshah400(a)gmail.com QAContact: ories(a)novell.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-GB; rv:1.9.1.9) Gecko/20100317 SUSE/3.5.9-0.1.1 Firefox/3.5.9 With the factory builds of compiz, the workaround "Fix screen updates in XGl with fglrx" has been enabled as a response to bug 597596. However it makes the effects decidedly slow and choppy on my system [Intel 945G]. The lazy desktop effect (problem with the screen not being updated/refreshed when desktop effect is enabled) which I too experienced throughout testing phases is now solved because of new Xorg/compiz packages even without enabling this workaround. It would be nice if this workaround can be disabled by default, as disabling it now causes no observable problems. Enabling it, on the other hand, causes choppy choppy effects. Reproducible: Always Steps to Reproduce: 1. 2. 3. -- 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 3