October 2013 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 747783] New: systemd: 'service openvpn start' triggers spamming of all terminals
by bugzilla_noreply＠novell.com 11 Apr '17

11 Apr '17

https://bugzilla.novell.com/show_bug.cgi?id=747783 https://bugzilla.novell.com/show_bug.cgi?id=747783#c0 Summary: systemd: 'service openvpn start' triggers spamming of all terminals Classification: openSUSE Product: openSUSE 12.1 Version: Final Platform: x86-64 OS/Version: openSUSE 12.1 Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: gp(a)suse.com QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0) Gecko/20100101 Firefox/10.0 1. become root 2. # service openvpn start 3. Watch as every terminal will be spammed with something like Broadcast message from root(a)trevally.site (Fri, 17 Feb 2012 17:28:14 +0100): Password entry required for 'Enter Auth Username:' (PID 17770). Please enter password with the systemd-tty-ask-password-agent tool! This does not make any sense since I am already in the terminal with the prompt; why bother all other terminals? 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 19

[Bug 755603] New: The gnome keyring socket is not owned with the same credentials as the user login
by bugzilla_noreply＠novell.com 11 Mar '17

11 Mar '17

https://bugzilla.novell.com/show_bug.cgi?id=755603 https://bugzilla.novell.com/show_bug.cgi?id=755603#c0 Summary: The gnome keyring socket is not owned with the same credentials as the user login Classification: openSUSE Product: openSUSE 12.2 Version: Factory Platform: Other OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: GNOME AssignedTo: bnc-team-gnome(a)forge.provo.novell.com ReportedBy: mvyskocil(a)suse.com QAContact: qa-bugs(a)suse.de CC: vuntz(a)suse.com, vcizek(a)suse.com Found By: Development Blocker: --- Created an attachment (id=484752) --> (http://bugzilla.novell.com/attachment.cgi?id=484752) copy the credential checking code from git.gnome.org Running command via sudo fills my log errors as appears in $SUBJECT $ sudo ls Password: xxxx and then log contains following Apr 4 10:20:01 zelva sudo: The gnome keyring socket is not owned with the same credentials as the user login: /run/user/mvyskocil/keyring-5MIqXs/control Apr 4 10:20:01 zelva sudo: gkr-pam: couldn't unlock the login keyring. Apr 4 10:20:01 zelva sudo: mvyskocil : TTY=pts/5 ; PWD=/home/mvyskocil ; USER=root ; COMMAND=/usr/bin/ls Apr 4 10:20:01 zelva systemd[1]: Got D-Bus request: org.freedesktop.DBus.NameOwnerChanged() on /org/freedesktop/DBus However that's not true $ echo $GNOME_KEYRING_CONTROL /run/user/mvyskocil/keyring-5MIqXs $ ls -n $GNOME_KEYRING_CONTROL/* srwxr-xr-x 1 10112 100 0 4. dub 09.33 /run/user/mvyskocil/keyring-5MIqXs/control srwxr-xr-x 1 10112 100 0 4. dub 09.33 /run/user/mvyskocil/keyring-5MIqXs/gpg srwxr-xr-x 1 10112 100 0 4. dub 09.33 /run/user/mvyskocil/keyring-5MIqXs/pkcs11 srwxr-xr-x 1 10112 100 0 4. dub 09.33 /run/user/mvyskocil/keyring-5MIqXs/ssh $ id uid=10112(mvyskocil) gid=100(users) groups=100(users),10(wheel),33(video),41(xok),113(vboxusers),404(lighttpd),1194(vpn) $ id -u 10112 $ id -ru 10112 so the 10112 is my *real* id and keyring sockets are really owned by this id. $ cat /proc/$GNOME_KEYRING_PID/loginuid 10112 and even the process runs with the same uid, so there is really **no** surprise in my configuration. I did a bit more and copy the part of gnome-keyring-daemon, however even getsockopt returns the id 10112, like getuid does. $ ./creds uid=10112, geteuid()=10112 I would say the best way to debug would be patch gnome-keyring-daemon and print the values of uid and getuid on error, but I haven't a time to do that yet. BTW: as google returns most of suse related things for $SUBJ, I suspect some misconfiguration in our pam stack. -- 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 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 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 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 691709] New: synergy makes cursor disapear over GVIM windows
by bugzilla_noreply＠novell.com 12 Dec '16

12 Dec '16

https://bugzilla.novell.com/show_bug.cgi?id=691709 https://bugzilla.novell.com/show_bug.cgi?id=691709#c0 Summary: synergy makes cursor disapear over GVIM windows Classification: openSUSE Product: openSUSE 11.4 Version: Factory Platform: x86-64 OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: X11 Applications AssignedTo: adam(a)mizerski.pl ReportedBy: jmatejek(a)novell.com QAContact: qa(a)suse.de Found By: --- Blocker: --- this happens on the computer where synergy server is running, not sure about client to reproduce: 1. start synergy server 2. open gvim window 3. start typing in gvim window (for non-vi folk, you initiate insert mode by typing "i" or pressing Ins) 4. the mouse cursor disappears 5. stop typing and move your mouse expected behavior: mouse curshor should reappear - this is standard behavior, designed so that the cursor is hidden while typing actual behavior: the mouse cursor never reappears. if you move mouse out of gvim's window, cursor is visible, but it is invisible when positioned over the window sorry if you're not the right assignee, but you are the only active user in the X11:Utilities project and you did the last change to synergy, so... -- 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 714551] New: Vim's ":tag" command should search corresponding header file first.
by bugzilla_noreply＠novell.com 12 Dec '16

12 Dec '16

https://bugzilla.novell.com/show_bug.cgi?id=714551 https://bugzilla.novell.com/show_bug.cgi?id=714551#c0 Summary: Vim's ":tag" command should search corresponding header file first. Classification: openSUSE Product: openSUSE 11.3 Version: Final Platform: x86-64 OS/Version: openSUSE 11.3 Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: nn.dm55(a)gmail.com QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux i686 on x86_64; rv:6.0) Gecko/20100101 Firefox/6.0 In a C++ project with many variables with the same name, searching for the definition of a variable mentioned in a ".cpp" file using Ctrl-] gives me the definition of an unrelated variable with the same name. The ":tag" command should prefer the definition in the corresponding header file to any other definitions to make finding the correct definition easier. Reproducible: Always Steps to Reproduce: 1. Download SuperTuxKart 2. Open src/karts/kart_model.cpp in Vim 3. Type "/::attachModel" and press Enter 4. Type "/else" and press Enter 5. Type "/m_mesh" and press Enter. 6. Hold Ctrl and press ], then release both keys Actual Results: You end up looking at the following line in src/graphics/shadow.hpp instead of src/karts/kart_model.hpp: scene::IMesh *m_mesh; Expected Results: I expected Vim to show me these line from src/karts/kart_model.hpp: scene::IAnimatedMesh *m_mesh; This bug happens even without having a .vimrc file. I am using openSUSE 11.3 64-bit. -- 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