August 2014 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 786679] New: usability issues with man
by bugzilla_noreply＠novell.com 16 Feb '17

16 Feb '17

https://bugzilla.novell.com/show_bug.cgi?id=786679 https://bugzilla.novell.com/show_bug.cgi?id=786679#c0 Summary: usability issues with man Classification: openSUSE Product: openSUSE 12.2 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Minor Priority: P5 - None Component: Documentation AssignedTo: ke(a)suse.com ReportedBy: aspiers(a)suse.com QAContact: ke(a)suse.com Found By: Development Blocker: --- This bug has two parts - a minor behavioural issue, and a minor documentation issue. As per FATE #303433, the default behaviour of man when there are multiple sections offering the requested man page was changed in June 2008. The old behaviour can be reverted by setting the MAN_POSIXLY_CORRECT environment variable. Whilst this was an improvement on the prior situation, there seems to be a minor behavioural issue when two versions of the same man page are on the manpath, e.g. $ manpath | tr : '\n' manpath: warning: $MANPATH set, ignoring /etc/manpath.config /home/adam/share/man /home/adam/.rvm/rubies/ruby-1.9.3-p194/share/man /home/adam/.rvm/man /opt/kde3/share/man /usr/local/man /usr/share/man /home/adam/.GIT/3rd-party/rvm/man $ ls -l ~/share/man/man1/git-commit.1 lrwxrwxrwx 1 adam users 46 Sep 26 13:19 /home/adam/share/man/man1/git-commit.1 -> ../../../.STOW/git/share/man/man1/git-commit.1 $ man -aw git-commit /usr/share/man/man1/git-commit.1.gz /home/adam/.STOW/git/share/man/man1/git-commit.1 $ man git-commit Man: find all matching manual pages (set MAN_POSIXLY_CORRECT to avoid this) * git-commit (1) git-commit (1+) Man: What manual page do you want? Man: However, if I enter '1+' and hit Enter, I still get the version from /usr/share. Likewise, $ man 1+ git-commit No manual entry for git-commit in section 1+ Perhaps I am wrong to expect this to work, which brings me onto the documentation issue: it is not clear how this is supposed to work, because while man-db-2.5.1-listall.dif patches src/man.c to introduce MAN_POSIXLY_CORRECT, it does not patch man/man1/man.man1 to correspondingly amend the documentation. So it would also be good if the changed behaviour and MAN_POSIXLY_CORRECT were documented. This would presumably help the patch get accepted upstream too. (Incidentally I notice that 2.5.1 is 4 years behind the current version 2.6.3, so it might be worth refreshing at some point soon.) -- 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

[Bug 854323] New: libpgf OpenMP digikam memory leak when thumbnailing and face recognition - fix available in pgf SVN
by bugzilla_noreply＠novell.com 03 Feb '17

03 Feb '17

https://bugzilla.novell.com/show_bug.cgi?id=854323 https://bugzilla.novell.com/show_bug.cgi?id=854323#c0 Summary: libpgf OpenMP digikam memory leak when thumbnailing and face recognition - fix available in pgf SVN Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: x86-64 OS/Version: openSUSE 13.1 Status: NEW Severity: Normal Priority: P5 - None Component: KDE4 Applications AssignedTo: kde-maintainers(a)suse.de ReportedBy: rickscafe.casablanca(a)gmx.net QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:25.0) Gecko/20100101 Firefox/25.0 The version of libpgf that is shipped with 13.1 produces a massive memory leak with digikam. This happens when initially thumbnailing a larger picture collection or when trying face recognition on a collection. In both cases digikam will eat up all RAM plus swap. At least part of the problem is libpgf and it was fixed in SVN, though has not been released yet. See http://sourceforge.net/p/libpgf/code/HEAD/tree/ *** trunk 2013-11-08 rs [r123] fix memory leak in Encoder w/ OpenMP *** I compiled r123 which identifies as 6.13.45 and it does indeed fix the memory leak with digikam. The fix should be included in a libpgf update to 13.1 RH Bug: https://bugzilla.redhat.com/show_bug.cgi?id=1023241 KDE Bug: https://bugs.kde.org/show_bug.cgi?id=326525 Reproducible: Always Steps to Reproduce: 1. backup digikam collection db and start from scratch 2. initial scan/tumbnailing uses all available RAM 3. face recognition uses all available RAM Actual Results: system runs out of memory or gets very slow due to digikam eating all RAM Expected Results: memory usage should be stable -- 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 3

[Bug 845245] New: chmod and chgrp make unnecessary disc writes
by bugzilla_noreply＠novell.com 23 Jan '17

23 Jan '17

https://bugzilla.novell.com/show_bug.cgi?id=845245 https://bugzilla.novell.com/show_bug.cgi?id=845245#c0 Summary: chmod and chgrp make unnecessary disc writes Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: x86-64 OS/Version: openSUSE 12.3 Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: R.Vickers(a)cs.rhul.ac.uk QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 Using chmod or chgrp alters the last-change time of a file even if no changes are actually made. This may seem like a very minor matter, but if you are dealing with a large number of files (for example with the -R option) then there are a number of bad consequences: (1) system performance is impacted while the command is running (2) incremental backups take longer and consume more space (3) restores after a disc failure take much longer because many large incremental backups have to be processed We use cron jobs to set correct permissions on shared directories, because it is not fair on users to expect them to manage this themselves. On one file system we find a third of the files are backed up every night because of this, and it extended the recovery time after a disc failure by many hours. Reproducible: Always Steps to Reproduce: $ touch test $ chmod 700 test $ stat test $ chmod 700 test $ stat test Actual Results: The Change time is updated after every chmod. Expected Results: The Change time should only be updated if the mode was changed. -- 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 3

[Bug 851394] New: nouveau failed to idle channel 0xcccc0001
by bugzilla_noreply＠novell.com 09 Jan '17

09 Jan '17

https://bugzilla.novell.com/show_bug.cgi?id=851394 https://bugzilla.novell.com/show_bug.cgi?id=851394#c0 Summary: nouveau failed to idle channel 0xcccc0001 Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers(a)forge.provo.novell.com ReportedBy: abergmann(a)suse.com QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- I just can into a problem with a GeForce 7300 LE VGA controller. Under X the system is unstable and is crashing. [ 865.851006] nouveau E[Xorg[3304]] failed to idle channel 0xcccc0001 [Xorg[3304]] [ 880.852005] nouveau E[Xorg[3304]] failed to idle channel 0xcccc0001 [Xorg[3304]] [ 895.852004] nouveau E[Xorg[3304]] failed to idle channel 0xcccc0001 [Xorg[3304]] I found the following bug describing this problem: https://bugs.launchpad.net/ubuntu/+source/linux-lts-quantal/+bug/1097178 -- 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 16

[Bug 883192] New: ElanTech Touchpad not working
by bugzilla_noreply＠novell.com 09 Jan '17

09 Jan '17

https://bugzilla.novell.com/show_bug.cgi?id=883192 https://bugzilla.novell.com/show_bug.cgi?id=883192#c0 Summary: ElanTech Touchpad not working Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: x86-64 OS/Version: openSUSE 13.1 Status: NEW Severity: Major Priority: P5 - None Component: Usability AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: sverre.moe(a)gmail.com QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created an attachment (id=595041) --> (http://bugzilla.novell.com/attachment.cgi?id=595041) Various touchpad information User-Agent: Opera/9.80 (X11; Linux x86_64) Presto/2.12.388 Version/12.16 The ElanTech Touchpad on my Fujitsu Celsius H730 does not work. Every time I touch the Touchpad the following output in /var/log/messages 2014-06-18T13:36:38.590522+02:00 machine kernel: [16561.131699] psmouse serio4: Touchpad at isa0060/serio4/input0 lost sync at byte 6 2014-06-18T13:36:38.599954+02:00 machine kernel: [16561.140887] psmouse serio4: Touchpad at isa0060/serio4/input0 lost sync at byte 6 2014-06-18T13:36:38.608547+02:00 machine kernel: [16561.149751] psmouse serio4: Touchpad at isa0060/serio4/input0 lost sync at byte 6 2014-06-18T13:36:38.617273+02:00 machine kernel: [16561.158496] psmouse serio4: Touchpad at isa0060/serio4/input0 lost sync at byte 6 2014-06-18T13:36:38.626209+02:00 machine kernel: [16561.167412] psmouse serio4: Touchpad at isa0060/serio4/input0 lost sync at byte 6 2014-06-18T13:36:38.626223+02:00 machine kernel: [16561.167416] psmouse serio4: issuing reconnect request Clicking on the right and left Touchpad buttons: 2014-06-18T13:37:39.027531+02:00 machine kernel: [16621.617646] psmouse serio4: Touchpad at isa0060/serio4/input0 lost sync at byte 6 2014-06-18T13:37:39.155018+02:00 machine kernel: [16621.745236] psmouse serio4: Touchpad at isa0060/serio4/input0 lost sync at byte 6 Clicking on the middle Touchpad button: 2014-06-18T13:39:44.049662+02:00 machine kernel: [16746.740984] psmouse serio4: Touchpad at isa0060/serio4/input0 - driver resynced. 2014-06-18T13:39:44.277859+02:00 machine kernel: [16746.969352] psmouse serio4: Touchpad at isa0060/serio4/input0 lost sync at byte 6 Attached text document with various output from /proc/bus/input/devices, xinput, dmesg and /var/log/Xorg.0.log I have tried the kernel-desktop-3.11.10-11 that comes with OpenSUSE 13.1 I have tried the latest stable kernel-desktop-3.15.0-1 I have tried the latest stable kernel-vanilla-3.15.0-1 This problem persists in all these kernel versions. Tried with both KDE 4.13.2 and LXQt. I tried to start the laptop with the OpenSUSE install ISO booted from USB. Touchpad not working there either. Have verified that the Touchpad is working in Windows. So it is not a hardware problem. Reproducible: Always Steps to Reproduce: 1. Touch Touchpad 2. 3. Actual Results: Mouse pointer standing still Expected Results: Move mouse pointer -- 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 14

[Bug 680125] New: dlclose() can not unload all dynamic libraries
by bugzilla_noreply＠novell.com 02 Jan '17

02 Jan '17

https://bugzilla.novell.com/show_bug.cgi?id=680125 https://bugzilla.novell.com/show_bug.cgi?id=680125#c0 Summary: dlclose() can not unload all dynamic libraries Classification: openSUSE Product: openSUSE 11.4 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: Development AssignedTo: pth(a)novell.com ReportedBy: gotterdammerung(a)web.de QAContact: qa(a)suse.de Found By: --- Blocker: --- Created an attachment (id=419657) --> (http://bugzilla.novell.com/attachment.cgi?id=419657) test program which opens a dl from cmdline, closes it and checks if it is still open User-Agent: Mozilla/5.0 (X11; U; Linux i686; de-DE; rv:1.9.2.15) Gecko/20110310 Gentoo Firefox/3.6.15 A call to dlclose() does not unload some dynamic libraries, even if the reference count drops to zero and no other loaded libraries use symbols in it. See attached test programm. Some libraries like 'pthread' exhibit this behaviour and it propagates up the dependency chain. This breaks programs which rely on reloading of affected dynamic libraries. Reproducible: Always Steps to Reproduce: 1. compile test program with 'g++ test.cpp -otest -ldl' 2. run 'for file in /usr/lib64/lib*.so; do ./test $file; done | grep failed' Actual Results: see attachment #2 Expected Results: /usr/lib64/librt.so failed. (at least that is what happens on my gentoo machine) AFAIK, x86_64 and x86 are both affected. Related: [[bugzilla:645652]] -- 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 622977] New: pstoedit crashes when called from inkscape
by bugzilla_noreply＠novell.com 01 Jan '17

01 Jan '17

http://bugzilla.novell.com/show_bug.cgi?id=622977 http://bugzilla.novell.com/show_bug.cgi?id=622977#c0 Summary: pstoedit crashes when called from inkscape Classification: openSUSE Product: openSUSE 11.3 Version: Final Platform: All OS/Version: openSUSE 11.3 Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: gerlach(a)mbi-berlin.de QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.6) Gecko/20100626 SUSE/3.6.6-1.1 Firefox/3.6.6 pstoedit crashes when converting pdf to svg (used by inkscape textext) Reproducible: Always Steps to Reproduce: 1. pstoedit -f plot-svg file.pdf file.svg -dt -ssp -psarg -r9600x9600 (command used by inkscape) Actual Results: pstoedit: version 3.50 / DLL interface 108 (build Jul 5 2010 - release build - g++ 4.5.0 20100604 [gcc-4_5-branch revision 160292]) : Copyright (C) 1993 - 2009 Wolfgang Glunz Inconsistency detected by ld.so: dl-close.c: 731: _dl_close: Assertion `map->l_init_called' failed! -- 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 22

[Bug 584970] New: Yast gives error -4017 when trying to partition using LVM
by bugzilla_noreply＠novell.com 22 Dec '16

22 Dec '16

http://bugzilla.novell.com/show_bug.cgi?id=584970 http://bugzilla.novell.com/show_bug.cgi?id=584970#c0 Summary: Yast gives error -4017 when trying to partition using LVM Classification: openSUSE Product: openSUSE 11.2 Version: Final Platform: HP OS/Version: openSUSE 11.2 Status: NEW Severity: Major Priority: P5 - None Component: Installation AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: p.c.manning(a)swansea.ac.uk QAContact: jsrain(a)novell.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/532.5 (KHTML, like Gecko) Chrome/4.0.249.89 Safari/532.5 Hardware: HP ML115 with E200 SmartArray card. 4 250GB drives built as raid 5. Use OpenSUSE DVD installer, select LVM partitioning scheme, installation dies when preparing disks with error -4017 Reproducible: Always Steps to Reproduce: 1.Use OpenSUSE 11.2 DVD 64bit to Install OS 2.Get to partitioning scheme - select LVM 3.Continue through installation, installation dies at preparing disks stage Actual Results: Retried this with text mode installer which enabled me to switch to a working shell console, I could see that the installer had created a boot partition, an LVM partition and an LVM group. But had failed to create any logical volumes Expected Results: A properly partitioned disk! http://forums.opensuse.org/install-boot-login/433990-yast-partitioning-erro… Workround was to partition manually via a shell console. -- 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 833235] New: security:OpenVAS:UNSTABLE:v6: Bug
by bugzilla_noreply＠novell.com 19 Dec '16

19 Dec '16

https://bugzilla.novell.com/show_bug.cgi?id=833235 https://bugzilla.novell.com/show_bug.cgi?id=833235#c0 Summary: security:OpenVAS:UNSTABLE:v6: Bug Classification: openSUSE Product: openSUSE.org Version: unspecified Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: 3rd party software AssignedTo: johann.luce(a)wanadoo.fr ReportedBy: chrisfischer81(a)gmx.de QAContact: opensuse-communityscreening(a)forge.provo.novell.com Found By: --- Blocker: --- Hi, the current OpenVAS v6 packages on OBS for Debian 7 (i don't know the status of other packages) are missing some files for running the openvas-certdata-sync script: /usr/sbin/openvas-certdata-sync: 185: /usr/sbin/openvas-certdata-sync: cannot open /usr/share/openvas/cert/cert_db_init.sql: No such file Error: no such table: dfn_cert_advs Error: no such table: meta Error: Inconsistent data. Resetting CERT database. [i] Updating /var/lib/openvas/cert-data/dfn-cert-2008.xml warning: failed to load external entity "/usr/share/openvas/cert/dfn_cert_update.xsl" Because of this the openvas-manager failed to start: /etc/init.d/openvas-manager start Starting OpenVAS Manager: ERROR. because of this log entry: md main:WARNING:2013-08-03 13h21.04 utc:7559: sql_x: sqlite3_prepare faile d: no such table: main.meta -- 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 888446] New: dead_caron + u should produce uring for czech locale xim
by bugzilla_noreply＠novell.com 18 Dec '16

18 Dec '16

https://bugzilla.novell.com/show_bug.cgi?id=888446 https://bugzilla.novell.com/show_bug.cgi?id=888446#c0 Summary: dead_caron + u should produce uring for czech locale xim Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: i686 OS/Version: openSUSE 13.1 Status: NEW Severity: Normal Priority: P5 - None Component: X.Org AssignedTo: bnc-team-xorg-bugs(a)forge.provo.novell.com ReportedBy: vlmarek(a)volny.cz QAContact: xorg-maintainer-bugs(a)forge.provo.novell.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:30.0) Gecko/20100101 Firefox/30.0 My .profile contains: export GTK_IM_MODULE=xim export QT_IM_MODULE=xim export LC_ALL=cs_CZ.UTF-8 Now if I press dead_caron + u, I get ǔ, but I should get ů. The same for capital letters - I get Ǔ but I should get Ů. The workaround I use is to set ~/.XCompose to include "%S/en_US.UTF-8/Compose" <dead_caron> <u> : "ů" U016F # LATIN SMALL LETTER U WITH RING ABOVE <dead_caron> <U> : "Ů" U016E # LATIN CAPITAL LETTER U WITH RING ABOVE This is already defined in /usr/share/X11/locale/iso8859-2/Compose , but one would have to use iso8859-2 instead of UTF-8: <dead_caron> <U> : "\331" Uring <dead_caron> <u> : "\371" uring (of course the binary value for Uring is different in iso8859-2 and UTF-8, so it can't be fixed by straight copy/paste) I don't understand the xkb too well, but I guess that there should be new directory and file /usr/share/X11/locale/cs_CZ.UTF-8/Compose which would contain something similar to what I have in ~/.XCompose Please note that it does not seem to be logical to use dead_caron for ring above u, but since we don't use ring above any other letter, and ǔ does not exist in czech, it's very convenient to have it print ů. This way it works on czech keyboards since ever. It's interesting that I have hard time finding evidence that it should be set this way. For example https://ufal.mff.cuni.cz/pdt/Support/czech-info.html The ring accent can occur only above an "u" where, in contrary, no caron can occur. That is why many keyboards use the sequence "dead caron" - "u"/"U" to enter an "u" with ring above. However, other keyboards (including Microsoft Windows, I guess) alocate a "dead ring" key elsewhere, often to shifted semicolon, replacing the U.S. key for tilde. https://lists.debian.org/debian-gtk-gnome/2003/11/msg00235.html Thank you __ Vlad Reproducible: Always Steps to Reproduce: 1. Enable XIM input method by putting this into your .profile: export GTK_IM_MODULE=xim export QT_IM_MODULE=xim export LC_ALL=cs_CZ.UTF-8 2. restart X so that the options take effect 2.5 start xterm 3. set czech keyboard map setxkbmap "us,cz(qwerty)" -option grp:shifts_toggle -option ctrl:swapcaps 4. switch into czech map by pressing both shifts together 5. Press dead_caron (shift + key "=" which should normally produce character "+") 6. Press letter "u" 7. ǔ appears, but I should see ů Actual Results: ǔ appears Expected Results: I should see ů -- 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