January 2012 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 732041] New: systemd: /etc/sysconfig/kernel: MODULES_LOADED_ON_BOOT="snd-mixer-oss" --> IGNORED
by bugzilla_noreply＠novell.com 04 Jan '12

04 Jan '12

https://bugzilla.novell.com/show_bug.cgi?id=732041 https://bugzilla.novell.com/show_bug.cgi?id=732041#c0 Summary: systemd: /etc/sysconfig/kernel: MODULES_LOADED_ON_BOOT="snd-mixer-oss" --> IGNORED Classification: openSUSE Product: openSUSE 12.1 Version: Final Platform: x86 OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: madworm_de.novell(a)spitzenpfeil.org QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux i686; rv:8.0) Gecko/20100101 Firefox/8.0 I need snd-mixer-oss loaded to make 'tvtime' happy. So I added "snd-mixer-oss" to MODULES_LOAD_ON_BOOT of '/etc/sysconfig/kernel', made sure it is activated (yast runlevel), but using systemd it is not executed at all. Gone back to sysvinit-init and it works. Reproducible: Always Steps to Reproduce: 1. add module to MODULES_LOAD_ON_BOOT 2. reboot 3. Actual Results: module not loaded on boot Expected Results: module loaded on boot -- 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 17

[Bug 732912] New: Bogus systemd log message regarding sendmail
by bugzilla_noreply＠novell.com 04 Jan '12

04 Jan '12

https://bugzilla.novell.com/show_bug.cgi?id=732912 https://bugzilla.novell.com/show_bug.cgi?id=732912#c0 Summary: Bogus systemd log message regarding sendmail Classification: openSUSE Product: openSUSE 12.1 Version: Final Platform: x86-64 OS/Version: SuSE Other Status: NEW Severity: Minor Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: nrickert(a)ameritech.net QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:8.0) Gecko/20100101 Firefox/8.0 (note: the operating system selector for reports needs an entry for 12.1) When looking through /var/log/messages (researching unrelated bug 732910), I noticed some bogus lines relating to "sendmail". Nov 26 23:52:19 nwr2 echo[4075]: Initializing SMTP port (sendmail) .. Nov 26 23:52:19 nwr2 systemd[1]: Failed to read PID file /var/run/sendmail.pid a fter start. The service might be broken. .. Nov 26 23:52:36 nwr2 systemd[1]: Failed to read PID file /var/spool/clientmqueue/sm-client.pid after start. The service might be broken. In fact, sendmail is running fine, and the two "pid" files exist: -rw------- 1 root mail 54 Nov 26 23:52 /var/run/sendmail.pid -rw------- 1 mail mail 53 Nov 26 23:52 /var/spool/clientmqueue/sm-client.pid This might be a timing issue. Perhaps systemd is checking for the existence of the files a few milliseconds too early. It would be better to not have those log messages at all, than to have them when they are wrong. I see those messages on every boot. The system uses AMD Athlon(tm) 64 X2 Dual Core Processor 4000+ in case that is relevant (the dual core might be relevant) 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 31

[Bug 731358] New: pam_systemd errors (Failed to create session) in /var/log/messages
by bugzilla_noreply＠novell.com 04 Jan '12

04 Jan '12

https://bugzilla.novell.com/show_bug.cgi?id=731358 https://bugzilla.novell.com/show_bug.cgi?id=731358#c0 Summary: pam_systemd errors (Failed to create session) in /var/log/messages Classification: openSUSE Product: openSUSE 12.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: jnelson-suse(a)jamponi.net QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:7.0.1) Gecko/20100101 Firefox/7.0.1 After upgrade to 12.1 my /var/log/messages has stuff like this: Nov 17 17:19:05 turnip su: (to nobody) root on none Nov 17 17:19:05 turnip su: pam_systemd(su:session): Failed to create session: Invalid argument Nov 17 17:19:05 turnip su: (to nobody) root on none Nov 17 17:19:05 turnip su: pam_systemd(su:session): Failed to create session: Invalid argument Nov 17 17:19:05 turnip su: (to nobody) root on none Nov 17 17:19:05 turnip su: pam_systemd(su:session): Failed to create session: Invalid argument I think these are ultimately from cron. 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 11

[Bug 722539] New: encrypted /tmp can only be used by root
by bugzilla_noreply＠novell.com 04 Jan '12

04 Jan '12

https://bugzilla.novell.com/show_bug.cgi?id=722539 https://bugzilla.novell.com/show_bug.cgi?id=722539#c0 Summary: encrypted /tmp can only be used by root Classification: openSUSE Product: openSUSE 12.1 Version: Beta 1 Platform: x86-64 OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: dutchkind(a)txoriaskea.org QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:7.0.1) Gecko/20100101 Firefox/7.0.1 After the upgrade from milestone 5 to beta 1 my encrypted /tmp is no longer mounted as 777 owner rights, so normal users can not login anymore because there is no write access to /tmp. Logging in as root and changing the rights to 777 solves the problem until reboot. 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 42

[Bug 561324] New: YaST Coding style not followed by yast2-devtools nor tutorials
by bugzilla_noreply＠novell.com 04 Jan '12

04 Jan '12

http://bugzilla.novell.com/show_bug.cgi?id=561324 http://bugzilla.novell.com/show_bug.cgi?id=561324#c0 Summary: YaST Coding style not followed by yast2-devtools nor tutorials Classification: openSUSE Product: openSUSE 11.2 Version: Final Platform: All OS/Version: All Status: NEW Severity: Minor Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: felix.wolfsteller(a)intevation.de QAContact: jsrain(a)novell.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux i686; de; rv:1.9.0.15) Gecko/2009102815 Iceweasel/3.0.6 (Debian-3.0.6-3) New to YaST (module) development, my natural starting point was one of the "official" tutorials (e.g. http://en.opensuse.org/YaST/Tutorials, but actually the comprehensive http://forgeftp.novell.com/yast/doc/SL11.1/tutorials/) Wanting to confirm to (imho important) style and coding guides, I looked at the well done http://forgeftp.novell.com/yast/doc/SL10.1/codingrules/index.html and was surprised that the tutorial and the yast2-devtool pointed me a "wrong" (regarding coding style) direction. I found the main problem with the devtools to be the skeletons (e.g. http://svn.opensuse.org/svn/yast/trunk/devtools/devtools/skeletons/config/s… ). A quick improvement of the Tutorials would be to mention that there is a style guide that should be read and applied, while apologizing that the tutorial in current state does not reflect that in every case. In an discussion in irc it was mentioned that reworking the tutorial (and i guess the config skeleton) might be a great Junior Job (JJ), as it automatically brings you closer to YCP. Thanks to jreidinger, kobliha and jsuchome from the #yast irc channel. Reproducible: Always Although the links in my post point to specific versions (e.g. openSUSE 11.2, SLE10.x) i found the tutorials of all versions to be affected. I am sorry to be picky. -- 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 731546] New: command-not-found-0.1.0-46.1.2.noarch requires python, but this requirement cannot be provided
by bugzilla_noreply＠novell.com 04 Jan '12

04 Jan '12

https://bugzilla.novell.com/show_bug.cgi?id=731546 https://bugzilla.novell.com/show_bug.cgi?id=731546#c0 Summary: command-not-found-0.1.0-46.1.2.noarch requires python, but this requirement cannot be provided Classification: openSUSE Product: openSUSE 12.1 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Installation AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: per(a)opensuse.org QAContact: jsrain(a)suse.com Found By: --- Blocker: --- Created an attachment (id=463029) --> (http://bugzilla.novell.com/attachment.cgi?id=463029) y2logs as saved by save_y2logs User-Agent: Mozilla/5.0 (X11; Linux i686 on x86_64; rv:7.0.1) Gecko/20100101 Firefox/7.0.1 I'm installing the minimal server pattern. I chose to break some some dependencies and the installation continued. However, subsequently 'cnf' does not work, but python WAS installed (afaict). 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 4

[Bug 736951] New: yast2-novell-client startup gives >> Error while creating client module novell-client
by bugzilla_noreply＠novell.com 04 Jan '12

04 Jan '12

https://bugzilla.novell.com/show_bug.cgi?id=736951 https://bugzilla.novell.com/show_bug.cgi?id=736951#c0 Summary: yast2-novell-client startup gives >> Error while creating client module novell-client 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: jasonsmr(a)hotmail.com QAContact: jsrain(a)suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.16) Gecko/20110701 Iceweasel/3.5.16 (like Firefox/3.5.16) when in the Yast2 Base console with all modules showing, in the Network Services >section I attempt to start the novell-client scriptlet in yast and a popup window comes up telling me that yast2-novell-client module had an error >>Error while creating client module novell-client the module scriptlet closes then. Reproducible: Always Steps to Reproduce: 1.install yast2-novell-client-2.0.1-0.8.x86_64 2.install novell-client-script-3.0.1-1.40.x86_64 3.and yast2-core and latest yast2 modules needed to get yast2 qt or gtk working (whichever you prefer) 4. start yast from terminal by typing su - (don't forget the - dash), then type yast2 and enter. 5. scroll down to the novell-client yast2 module in the Network Services section of yast2 and double or single click enter on it. Actual Results: 6. receive a error in a separate neat pop-up window about:: Error while creating client module novell-client 7. Remember to check in the /var/logs/YaST2/y2log file for clues (if there are lots of errors unrelated to the issue do: echo -n >/var/log/YaST2/y2log and repeat step 5. Expected Results: I expected to receive a working copy of the novell-client module and greeted by a friendly novel scriptlet about how to login to my novell account and server. from remote and or local machine (over network)~ -- 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 739221] New: /etc/pam.d/xdm lacks pam_systemd module
by bugzilla_noreply＠novell.com 03 Jan '12

03 Jan '12

https://bugzilla.novell.com/show_bug.cgi?id=739221 https://bugzilla.novell.com/show_bug.cgi?id=739221#c0 Summary: /etc/pam.d/xdm lacks pam_systemd module Classification: openSUSE Product: openSUSE 12.1 Version: Final Platform: All OS/Version: SuSE Other Status: NEW Severity: Major Priority: P5 - None Component: X.Org AssignedTo: bnc-team-xorg-bugs(a)forge.provo.novell.com ReportedBy: javier(a)conti-menchini.ch QAContact: xorg-maintainer-bugs(a)forge.provo.novell.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:9.0) Gecko/20100101 Firefox/9.0 In /etc/pam.d/xdm (in openSUSE 12.1) the pam_systemd module is missing by default. systemd-uaccess is used to set ACL on device files in some cases (e.g. when a digital camera is plugged in) and it's not able to get information about the user owning the session (i.e. /run/systemd/seats/seat0 is not updated by PAM), as we can see in the following example: $ cat /run/systemd/seats/seat0 # This is private data. Do not parse. IS_VTCONSOLE=1 Putting the pam_systemd module in /etc/pam.d/xdm as follows: $ cat /etc/pam.d/xdm #%PAM-1.0 auth include common-auth account include common-account password include common-password session required pam_loginuid.so session required pam_systemd.so kill-session-processes=1 session include common-session Makes PAM update the /run/systemd/seats/seat0 correctly, as in the following example: $ cat /run/systemd/seats/seat0 # This is private data. Do not parse. IS_VTCONSOLE=1 ACTIVE=521 ACTIVE_UID=1000 SESSIONS=521 UIDS=1000 And some devices that didn't work because of wrong permissions, start to work. Probably, the case where a user boots with old SysV init should be managed too, but currently without that entry users using systemd may experience problems in using some devices. Reproducible: Always Steps to Reproduce: 1. Plug a device such a digital camera 2. Try using it as the user owning the session (not root) Actual Results: There is an error writing to the device Expected Results: The user owning the session should be able to write to the device (if writing is supported) See OP: http://lists.opensuse.org/opensuse/2011-12/msg01512.html -- 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 7

[Bug 645793] New: file descriptor 3 (/dev/blog) leaked on vgchange invocation
by bugzilla_noreply＠novell.com 03 Jan '12

03 Jan '12

https://bugzilla.novell.com/show_bug.cgi?id=645793 https://bugzilla.novell.com/show_bug.cgi?id=645793#c0 Summary: file descriptor 3 (/dev/blog) leaked on vgchange invocation Classification: openSUSE Product: openSUSE 11.4 Version: Factory Platform: All OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: crrodriguez(a)novell.com QAContact: qa(a)suse.de Found By: Community User Blocker: No Created an attachment (id=394465) --> (http://bugzilla.novell.com/attachment.cgi?id=394465) screen shot of the meesage Hi: Looks like some process is either not close()'ing /dev/blog or it isnt opening it with O_CLOEXEC and boot ends with a warning like is shown in the attached screenshot. -- 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 13

[Bug 728846] New: NTP service disrupts work of other services when started in the same time
by bugzilla_noreply＠novell.com 03 Jan '12

03 Jan '12

https://bugzilla.novell.com/show_bug.cgi?id=728846 https://bugzilla.novell.com/show_bug.cgi?id=728846#c0 Summary: NTP service disrupts work of other services when started in the same time Classification: openSUSE Product: openSUSE 11.4 Version: Factory Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: anixx(a)opensuse.org QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; ru; rv:1.9.1.19) Gecko/20110420 SUSE/2.0.14-0.2.1 SeaMonkey/2.0.14 NTP changes system clock to syncronize it with that obtained from NTP server. This change may potentially disrupt work or other services started at the same time and relying on timer. In my case, NTP starts just after KDE3's kdm display manager which disrupts KDM's notmal functioning. If to disable NTP, kdm works well. I suggest NTP to be started after the network services but before other services in the same runlevel to prevent potential conflicts. 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 13