January 2013 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 771811] New: postfix update does not regenerate the maps
by bugzilla_noreply＠novell.com 27 Jul '17

27 Jul '17

https://bugzilla.novell.com/show_bug.cgi?id=771811 https://bugzilla.novell.com/show_bug.cgi?id=771811#c0 Summary: postfix update does not regenerate the maps Classification: openSUSE Product: openSUSE 12.2 Version: Factory Platform: Other OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: Basesystem AssignedTo: varkoly(a)suse.com ReportedBy: meissner(a)suse.com QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- I think the postfix map regeneration is not working. SuSEconfig seems to be gone, so it needs to be done differently on update. Jul 15 02:16:45 beiboot postfix/cleanup[23526]: warning: database /etc/postfix/canonical.db is older than source file /etc/postfix/canonical Jul 15 02:16:45 beiboot postfix/cleanup[23526]: warning: database /etc/postfix/sender_canonical.db is older than source file /etc/postfix/sender_canonical Jul 15 02:16:45 beiboot postfix/cleanup[23526]: warning: database /etc/postfix/virtual.db is older than source file /etc/postfix/virtual -- 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 797277] New: utilities: Bug
by bugzilla_noreply＠novell.com 03 Jul '17

03 Jul '17

https://bugzilla.novell.com/show_bug.cgi?id=797277 https://bugzilla.novell.com/show_bug.cgi?id=797277#c0 Summary: utilities: Bug Classification: openSUSE Product: openSUSE.org Version: unspecified Platform: Other OS/Version: SUSE Other Status: NEW Severity: Normal Priority: P5 - None Component: 3rd party software AssignedTo: pascal.bleser(a)opensuse.org ReportedBy: archie(a)dellroad.org QAContact: opensuse-communityscreening(a)forge.provo.novell.com Found By: --- Blocker: --- I'm trying to figure out the best way to fix package "mtree" build failures due to "unresolvable: nothing provides libopenssl-devel" in non-suse O/S such as CentOS. I think the best way to fix this is to add the following to the utilities project conf: Substitute: libopenssl-devel openssl-devel Can we add this? Thanks, -Archie -- 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 1

[Bug 701066] New: mc is eating all of ram after encfs until oom killer start to hunting
by bugzilla_noreply＠novell.com 22 Jun '17

22 Jun '17

https://bugzilla.novell.com/show_bug.cgi?id=701066 https://bugzilla.novell.com/show_bug.cgi?id=701066#c0 Summary: mc is eating all of ram after encfs until oom killer start to hunting Classification: openSUSE Product: openSUSE 11.4 Version: Final Platform: x86-64 OS/Version: openSUSE 11.4 Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: hnsz2002(a)gmail.com QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:2.0.1) Gecko/20100101 Firefox/4.0.1 After mounting encfs filesystem, if you started mc, its eating any memory, any swap, then oom killer killed the process. [ 7410.101006] Out of memory: Kill process 11459 (mc) score 809 or sacrifice child [ 7410.101006] Killed process 11459 (mc) total-vm:6710300kB, anon-rss:3615048kB, file-rss:264kB Reproducible: Always Steps to Reproduce: 1. Open a shell, mount an encfs filesystem to a mountpoint. (encfs /data/crypt /mnt/1/ for example) 2. cd to mountpont (cd /mnt/1/) 3. run few ls in the directory until you wait to timeout encfs, and automatically umount the filesystem. 4. start an mc in this directory. Actual Results: oom killer kill mc. -- 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 770608] New: 1-click install shows success, but package not installed
by bugzilla_noreply＠novell.com 16 Jun '17

16 Jun '17

https://bugzilla.novell.com/show_bug.cgi?id=770608 https://bugzilla.novell.com/show_bug.cgi?id=770608#c0 Summary: 1-click install shows success, but package not installed Classification: openSUSE Product: openSUSE 12.1 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: embar(a)super.lt QAContact: jsrain(a)suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:13.0) Gecko/20100101 Firefox/13.0 Installing via 1-click shows success, but package is not installed. Maybe this is because fack, that package is locked. YaST should inform about locked package and ask in dialog, not silently don't install. Reproducible: Always Steps to Reproduce: 1. Remove espeak package 2. Reopen YaST package manager 3. mark espeak as taboo 4. Try install espeak via 1-click http://software.opensuse.org/ymp/openSUSE:12.1/standard/espeak.ymp?base=ope… Actual Results: Any questions (only maybe to accept key of repository) Shows success, but package is not installed Expected Results: Should propt to dialog and ask: 1) remove package's lock and install espeak 2) don't install espeak -- 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 8

[Bug 795594] New: gcc47 source package requires unknown glibc-32bit
by bugzilla_noreply＠novell.com 07 Jun '17

07 Jun '17

https://bugzilla.novell.com/show_bug.cgi?id=795594 https://bugzilla.novell.com/show_bug.cgi?id=795594#c0 Summary: gcc47 source package requires unknown glibc-32bit Classification: openSUSE Product: openSUSE 12.2 Version: Final Platform: x86 OS/Version: openSUSE 12.2 Status: NEW Severity: Normal Priority: P5 - None Component: Development AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: Franz.Reinhardt(a)wenglor.com QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20100101 Firefox/17.0 Installing the sourc package requires glibc-32bit, which is not available zypper si gcc47 Reading installed packages... Loading repository data... Resolving package dependencies... Problem: nothing provides glibc-32bit needed by gcc47-4.7.1_20120723-1.1.1.src Solution 1: do not ask to install a solvable providing gcc47.src = 4.7.1_20120723-1.1.1 Solution 2: break gcc47-4.7.1_20120723-1.1.1.src by ignoring some of its dependencies Choose from above solutions by number or cancel [1/2/c] (c): Reproducible: Always Steps to Reproduce: >From the cli call: zypper si gcc47 rpm -bb on the spec works correctly, even when installed with solution 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 789833] New: Pure-ftpd does not allow login when started as service
by bugzilla_noreply＠novell.com 30 May '17

30 May '17

https://bugzilla.novell.com/show_bug.cgi?id=789833 https://bugzilla.novell.com/show_bug.cgi?id=789833#c0 Summary: Pure-ftpd does not allow login when started as service Classification: openSUSE Product: openSUSE 12.2 Version: Final Platform: Other OS/Version: openSUSE 12.2 Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: erwin.vandevelde(a)gmail.com QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:16.0) Gecko/20100101 Firefox/16.0 When pure-ftpd is started as a service, this happens when trying to connect: :~> ftp localhost Trying ::1... Connected to localhost. 220-Welcome to Pure-FTPd. 220-You are user number 1 of 10 allowed. 220-Local time is now 17:08. Server port: 21. 220-This is a private system - No anonymous login 220 You will be disconnected after 15 minutes of inactivity. Name (localhost:evdvelde): 331 User evdvelde OK. Password required Password: 421 Service not available, remote server has closed connection. ftp: Login failed. ftp> quit No errors recorded in the log files. When running on command line, it works fine. Configuration done normally through Yast, this is the command that is recorded in /var/log/messages (same command I use on the command line): /usr/sbin/pure-ftpd --daemonize -A -c10 -B -C3 -d -z -D -E -fftp -H -I15 -lpam -L10000:8 -m4 -s -u40 -x -r -i -k99 -G -Z -Y0 Reproducible: Always Steps to Reproduce: 1. Install pure-ftpd 2. Configure through Yast (I disabled anonymous login) 3. Try connecting when pure-ftpd runs as a service Actual Results: Error: 421 Service not available, remote server has closed connection. Expected Results: Succesful connection pure-ftpd 1.0.36-3.1.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 21

[Bug 695322] New: home:dannori: Bug
by bugzilla_noreply＠novell.com 23 Apr '17

23 Apr '17

https://bugzilla.novell.com/show_bug.cgi?id=695322 https://bugzilla.novell.com/show_bug.cgi?id=695322#c0 Summary: home:dannori: Bug Classification: openSUSE Product: openSUSE.org Version: unspecified Platform: x86-64 OS/Version: openSUSE 11.4 Status: NEW Severity: Normal Priority: P5 - None Component: 3rd party software AssignedTo: dannoritzer(a)web.de ReportedBy: melchiaros(a)aol.com QAContact: opensuse-communityscreening(a)forge.provo.novell.com Found By: Other Blocker: No Hi, I try to install ghdl from your repo. Yast shows me that ghdl-grt needs libada >= 3.1. A look at my system shows that I´ve installed libada46 from devel:/gcc. So all what ghdl need should be there?! Please make a correction when it is necessary. Greetings -- 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 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