June 2014 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 882154] New: root should not be required for unmounting
by bugzilla_noreply＠novell.com 11 Jun '14

11 Jun '14

https://bugzilla.novell.com/show_bug.cgi?id=882154 https://bugzilla.novell.com/show_bug.cgi?id=882154#c0 Summary: root should not be required for unmounting Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: illumilore(a)gmail.com QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:26.0) Gecko/20100101 Firefox/26.0 when unmounting a usb drive, I am always asked for root password. Considering I didn't need one to mount it in the first place, it shouldn't be required. 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 2

[Bug 881825] New: username is reported to contain forbidden characters although it does not
by bugzilla_noreply＠novell.com 11 Jun '14

11 Jun '14

https://bugzilla.novell.com/show_bug.cgi?id=881825 https://bugzilla.novell.com/show_bug.cgi?id=881825#c0 Summary: username is reported to contain forbidden characters although it does not Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: Other OS/Version: openSUSE 13.1 Status: NEW Severity: Minor Priority: P5 - None Component: Installation AssignedTo: yast2-maintainers(a)suse.de ReportedBy: tobiasmue(a)gnome.org QAContact: jsrain(a)suse.com Found By: --- Blocker: --- Created an attachment (id=593839) --> (http://bugzilla.novell.com/attachment.cgi?id=593839) screenshot showing the username popup while a valid username is entered User-Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:29.0) Gecko/20100101 Firefox/29.0 I tried to install OpenSuSE and got the the username screen. I entered my username "muelli" and clicked the "next" button. A popup would show up, complaining about the username. See the attached screenshot. My gut feeling is that I accidentally hit the Enter key while typing in the username and that the popup was raised asynchronously so that it didn't know that the username I entered by the time the popup appeared was correct. Maybe the popup could just before it's being raised, check whether the contents of the username field has been changed and then re-check whether it is valid. 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 6

[Bug 352419] strace shows wrong system call
by bugzilla_noreply＠novell.com 10 Jun '14

10 Jun '14

https://bugzilla.novell.com/show_bug.cgi?id=352419 https://bugzilla.novell.com/show_bug.cgi?id=352419#c12 --- Comment #12 from Eelis - <opensuse.org(a)contacts.eelis.net> 2014-06-10 21:13:25 UTC --- Wait, in what sense was the bug fixed upstream? The bug is "strace shows wrong system call", and in the output in your last comment, fork() is still reported as a wonky open(). :) -- 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 0

[Bug 352419] strace shows wrong system call
by bugzilla_noreply＠novell.com 10 Jun '14

10 Jun '14

https://bugzilla.novell.com/show_bug.cgi?id=352419 https://bugzilla.novell.com/show_bug.cgi?id=352419#c11 Stanislav Brabec <sbrabec(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |RESOLVED InfoProvider|opensuse.org(a)contacts.eelis | |.net | Resolution| |FIXED --- Comment #11 from Stanislav Brabec <sbrabec(a)suse.com> 2014-06-10 22:19:58 CEST --- As there is no response to NEEDINFO and the reported bug was fixed by the upstream, closing the bug. -- 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 0

[Bug 881184] New: owncloud-client package doesnt work
by bugzilla_noreply＠novell.com 10 Jun '14

10 Jun '14

https://bugzilla.novell.com/show_bug.cgi?id=881184 https://bugzilla.novell.com/show_bug.cgi?id=881184#c0 Summary: owncloud-client package doesnt work Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: i586 OS/Version: openSUSE 13.1 Status: NEW Severity: Normal Priority: P5 - None Component: Network AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: defuzo(a)gmail.com QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux i686; rv:29.0) Gecko/20100101 Firefox/29.0 The owncloud-client thingy doesnt work. Neather from its giu or from terminal, "owncloudcmd" returns: .. 06-03 20:07:32:183 Database Drivers could not be loaded. 06-03 20:07:32:183 Database Drivers could not be loaded. 06-03 20:07:32:183 No database Transaction to commit 06-03 20:07:32:183 No way to create a sync journal! .. Reproducible: Always Steps to Reproduce: 1. type $owncloundcmd /path/to/local/folder owncloud://id:pass@server/remote.php/webdav/path/to/remote/server 2. hit return 3. - and oh, it doesnt need tobe connected, some local error. Actual Results: mentioned "Database Drivers could not be loaded.".. Expected Results: It is supposse to sync local folder, with the owncloud folder. Google suggested it may depend on locales, dono.. (use "en_US" allover). Building it from source, is another hairy history, next thing to test.. But there also exist a package called "owncloud-client-debuginfo" no clew what it does. Also "libowncloudsync0-debuginfo"? -dont wanto install? -- 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 882078] New: man-pages-zh_CN should not include apropos.1 nor man.1 nor whatis.1
by bugzilla_noreply＠novell.com 10 Jun '14

10 Jun '14

https://bugzilla.novell.com/show_bug.cgi?id=882078 https://bugzilla.novell.com/show_bug.cgi?id=882078#c0 Summary: man-pages-zh_CN should not include apropos.1 nor man.1 nor whatis.1 Classification: openSUSE Product: openSUSE Factory Version: 13.2 Milestone 0 Platform: All OS/Version: openSUSE 13.2 Status: NEW Severity: Major Priority: P5 - None Component: Documentation AssignedTo: alexepico(a)gmail.com ReportedBy: werner(a)suse.com QAContact: ke(a)suse.com CC: coolo(a)suse.com Found By: Development Blocker: --- >From last submit I've seen: Descr: - Update to version 2.6.6 - rebase following patches: * man- db-2.6.3.dif * man-db-2.6.3-security4.dif * man- db-2.6.3-firefox.dif * man-db-2.6.3-zio.dif - enable checks (forwarded request 229380 from rudi_m) Comment: Shouldn't we integrate the chinese ones as subpackage so we can easier remove the outdated ones? found conflict of man-2.6.6-107.1.x86_64 with man-pages-zh_CN-1.5-92.5.noarch: - /usr/share/man/zh_CN/man1/apropos.1.gz - /usr/share/man/zh_CN/man1/man.1.gz - /usr/share/man/zh_CN/man1/whatis.1.gz please remove those manual pages from man-pages-zh_CN as the manual pages for the man package do describe the the man-db features. -- 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 0

[Bug 850463] New: Using yast network module changes postfix configuration files
by bugzilla_noreply＠novell.com 10 Jun '14

10 Jun '14

https://bugzilla.novell.com/show_bug.cgi?id=850463 https://bugzilla.novell.com/show_bug.cgi?id=850463#c0 Summary: Using yast network module changes postfix configuration files Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: x86-64 OS/Version: openSUSE 12.3 Status: NEW Severity: Major Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: f.malfatto(a)fmal.com QAContact: jsrain(a)suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/30.0.1599.101 Safari/537.36 I have a manual postfix configuration with complex main.cf. I never used /etc/sysconfig/postfix if not during insatllation to activate postfix at boot. After several months of normal work, I entered yast network to do a minor change (added a secondary dns server). This action reverted my main.cf and master.cf to default values contained in sysconfig, also if both were manually modified. So my mail serve blocked refusing to relay for my domains. I restored *.cf from a backup, saved into .bak file, and replyed the process with yast: again they were changed to defaults, bloking postfix operations. Tested on a complely different host, running with standard postfix configuration, again yast changes *.cf, loosing personal selections if different from sysconfig ones. Reproducible: Always Steps to Reproduce: 1.Modify main.cf with some value different from sysconfig/postfix defaults and save it also as a backup 2.Run Yast network to change a dns server or an ip address 3.check your new main.cf against the backupped one Actual Results: Postfix is restarted without your values Expected Results: Yast network should not change a manually edited postfix configuration file -- 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 790871] New: /etc/postfix/system scripts are not instance sensitive
by bugzilla_noreply＠novell.com 10 Jun '14

10 Jun '14

https://bugzilla.novell.com/show_bug.cgi?id=790871 https://bugzilla.novell.com/show_bug.cgi?id=790871#c0 Summary: /etc/postfix/system scripts are not instance sensitive Classification: openSUSE Product: openSUSE 12.2 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: per(a)computer.org QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux i686 on x86_64; rv:11.0) Gecko/20100101 Firefox/11.0 The extra scripts now supplied in /etc/postfix/system all assume the default postfix instance. Anyone trying to run multiple postfix instances will run into problems with these. 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 2

[Bug 855688] New: possible systemd bug: postfix & cifs dependency confiict
by bugzilla_noreply＠novell.com 10 Jun '14

10 Jun '14

https://bugzilla.novell.com/show_bug.cgi?id=855688 https://bugzilla.novell.com/show_bug.cgi?id=855688#c0 Summary: possible systemd bug: postfix & cifs dependency confiict Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: i586 OS/Version: openSUSE 12.3 Status: NEW Severity: Major Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: clkennedy(a)netpipe.com QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux i686; rv:23.0) Gecko/20100101 Firefox/23.0 I'm experiencing what I suspect is a systemd bug. I have two machines A & B in my test environment -- both running suse 12.3, Computer B, once in production will be a Windows box. On B I have an smb share called testshare that mounts on A quite happily. Life is good till B is shut off. If I reboot A while B is off line, obviously the share won't mount but, in addition, postfix won't start. Note: the hostname of computer A is util-x Here is the fstab of A: /dev/sda1 swap swap defaults 0 0 /dev/md0 / ext3 acl,user_xattr 1 1 proc /proc proc defaults 0 0 sysfs /sys sysfs noauto 0 0 debugfs /sys/kernel/debug debugfs noauto 0 0 usbfs /proc/bus/usb usbfs noauto 0 0 devpts /dev/pts devpts mode=0620,gid=5 0 0 //b/testshare /media/test cifs guest,uid=1000,gid=100 0 0 As I said above A is happy when B is alive. When B is down and I reboot A, postfix doesn't start: systemctl status postfix.service postfix.service - Postfix Mail Transport Agent Loaded: loaded (/usr/lib/systemd/system/postfix.service; enabled) Active: inactive (dead) CGroup: name=systemd:/system/postfix.service Dec 16 05:44:33 util-x.pdc systemd[1]: Dependency failed for Postfix Mail Transport Agent. If I try to start postfix from the command line: systemctl start postfix.service A dependency job for postfix.service failed. See 'journalctl -n' for details. Viewing the journal: postfix start attempt at boot time Dec 16 05:44:33 util-x.pdc systemd[1]: Mounting /media/test... Dec 16 05:44:33 util-x.pdc mount[2196]: Unable to find suitable address. Dec 16 05:44:33 util-x.pdc kernel: CIFS VFS: Error connecting to socket. Aborting operation Dec 16 05:44:33 util-x.pdc systemd[1]: media-test.mount mount process exited, code=exited status=32 Dec 16 05:44:33 util-x.pdc kernel: CIFS VFS: cifs_mount failed w/return code = -111 Dec 16 05:44:33 util-x.pdc systemd[1]: Failed to mount /media/test. Dec 16 05:44:33 util-x.pdc systemd[1]: Dependency failed for Remote File Systems. Dec 16 05:44:33 util-x.pdc systemd[1]: Dependency failed for Postfix Mail Transport Agent. Dec 16 05:44:33 util-x.pdc systemd[1]: Job postfix.service/start failed with result 'dependency'. Dec 16 05:44:33 util-x.pdc systemd[1]: Job remote-fs.target/start failed with result 'dependency'. Dec 16 05:44:33 util-x.pdc systemd[1]: Unit media-test.mount entered failed state postfix start attempt from the command line Dec 16 05:44:55 util-x.pdc systemd[1]: Mounting /media/test... Dec 16 05:44:55 util-x.pdc mount[2204]: Unable to find suitable address. Dec 16 05:44:55 util-x.pdc systemd[1]: media-test.mount mount process exited, code=exited status=32 Dec 16 05:44:55 util-x.pdc kernel: CIFS VFS: Error connecting to socket. Aborting operation Dec 16 05:44:55 util-x.pdc kernel: CIFS VFS: cifs_mount failed w/return code = -111 Dec 16 05:44:55 util-x.pdc systemd[1]: Failed to mount /media/test. Dec 16 05:44:55 util-x.pdc systemd[1]: Dependency failed for Remote File Systems. Dec 16 05:44:55 util-x.pdc systemd[1]: Dependency failed for Postfix Mail Transport Agent. Dec 16 05:44:55 util-x.pdc systemd[1]: Job postfix.service/start failed with result 'dependency'. Dec 16 05:44:55 util-x.pdc systemd[1]: Job remote-fs.target/start failed with result 'dependency'. Dec 16 05:44:55 util-x.pdc systemd[1]: Unit media-test.mount entered failed state Reproducible: Always Steps to Reproduce: 1. Disconnect Server B above. 2. Reboot A (util-x) above 3. postfix fails to start Actual Results: see writeup above Expected Results: see writeup above This seems as though it's possibly related to bug report 838750 from last September. I have provided more details. -- 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 801760] New: yast configurations for postfix are not applied to /etc/postfix configuration files
by bugzilla_noreply＠novell.com 10 Jun '14

10 Jun '14

https://bugzilla.novell.com/show_bug.cgi?id=801760 https://bugzilla.novell.com/show_bug.cgi?id=801760#c0 Summary: yast configurations for postfix are not applied to /etc/postfix configuration files Classification: openSUSE Product: openSUSE 12.2 Version: Final Platform: x86-64 OS/Version: openSUSE 12.2 Status: NEW Severity: Major Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: tibirna(a)kde.org QAContact: jsrain(a)suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.22 (KHTML, like Gecko) Chrome/25.0.1362.0 Safari/537.22 SUSE/25.0.1362.0 I traditionally set "relayhost=my.local.network" and "nullclient=yes" in YaST>System>/etc/sysconfig>Network>Mail>Postfix and apply them. I can then go in /etc/sysconfig/postfix and inspect the file visually, and see that my configurations are well recorded. But then looking into /etc/postfix/main.cf and /etc/postfix/master.cf, I see "relayhost=" and I see that "smtp" and "local" services are *not* commented out. This is dangerous, as it then silently fails to route local e-mail as purposedly configuref. Reproducible: Always Steps to Reproduce: 1. change a config in YaST>System>/etc/sysconfig>Network>Mail>Postfix 2. apply it 3. check that the modif is saved in /etc/sysconfig/postfix 4. check that the appropriate modifs *are not* done in /etc/postfix/* Actual Results: The /etc/postfix/* files are not modified Expected Results: Configuration modifications should be applied. -- 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