December 2013 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 853797] New: osc vc chown invalid user
by bugzilla_noreply＠novell.com 05 Dec '13

05 Dec '13

https://bugzilla.novell.com/show_bug.cgi?id=853797 https://bugzilla.novell.com/show_bug.cgi?id=853797#c0 Summary: osc vc chown invalid user Classification: Internal Novell Products Product: openSUSE Build Service Version: master Platform: x86-64 OS/Version: openSUSE 12.3 Status: NEW Severity: Normal Priority: P5 - None Component: osc AssignedTo: adrian(a)suse.com ReportedBy: toganm(a)dinamizm.com QAContact: adrian(a)suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:25.0) Gecko/20100101 Firefox/25.0 With the latest osc I am getting this strange error, the commit is writen though osc vc -m"1.4~rc1.18_g6a96a43" chown: invalid user: ‘users:toganm’ toganm is a normal user in this machine so what is the problem. rpm -q osc osc-0.142.2-116.1.noarch rpm -qi osc Name : osc Version : 0.142.2 Release : 116.1 Architecture: noarch Install Date: Wed 04 Dec 2013 11:34:37 AM CET Group : Development/Tools/Other Size : 1689802 License : GPL-2.0+ Signature : DSA/SHA1, Wed 04 Dec 2013 09:29:28 AM CET, Key ID 85753aa5eefefde9 Source RPM : osc-0.142.2-116.1.src.rpm Build Date : Wed 04 Dec 2013 09:29:13 AM CET Build Host : cloud109 Relocations : (not relocatable) Vendor : obs://build.opensuse.org/openSUSE:Tools URL : http://www.gitorious.org/opensuse/osc Summary : openSUSE Build Service Commander Description : Commandline client for the openSUSE Build Service. 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 1

[Bug 754594] New: kmail does ignore the encryption-settings defined in the addressbook of kontakt
by bugzilla_noreply＠novell.com 05 Dec '13

05 Dec '13

https://bugzilla.novell.com/show_bug.cgi?id=754594 https://bugzilla.novell.com/show_bug.cgi?id=754594#c0 Summary: kmail does ignore the encryption-settings defined in the addressbook of kontakt Classification: openSUSE Product: openSUSE 12.1 Version: Final Platform: x86-64 OS/Version: Other Status: NEW Severity: Critical Priority: P5 - None Component: KDE4 Applications AssignedTo: kde-maintainers(a)suse.de ReportedBy: stakanov(a)freenet.de QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:11.0) Gecko/20100101 Firefox/11.0 Programm version: Kmail and Kontact version 4.7.2 default packages openSUSE 12.1, 64 bit, fresh install. Kmail ignores the mandatory encryption setting in Address book but fools the author with executing correctly the signature. If you set: sign always, encrypt always for a contact in the Kontact address book, only the signature settings are taken. Since the program asks for the encryption password, the author does not notice that the email will departure unencrypted but will believe it is correctly signed and encrypted. I think this is severe because this could make people send potentially sensible information and attachments unencrypted over the internet. This bug will affect also mailing-lists Reproducible: Always Steps to Reproduce: 1.create a contact in the address book. Give mandatory signature and encryption as setting for it. Safe. 2. write a mail to this contact. Do not manually select encryption or signature. 3.Signature will be selected and password asked but the mail will be send unencrypted. Actual Results: Sending your correspondence and attachment unencrypted over the internet, thinking that they have been encrypted. Expected Results: Like Kmail of KDE3: encryption password is asked and encryption is taking place according to settings. In case you deselect a mandatory option a warning is displayed that you may be going against site policy and confirmation is asked. (I do not recall, but maybe - correctly - it is even impossible to send unencrypted in KDE3 Kmail when in address book encryption and signature are obligatory. So with other words, no regression compared to the previous function.I sign this bug critical. If someone sends credit card data, or important documents encrypted, this may be a good way of having a oooops big problem, which is equivalent of loss of data (to say the minor). Since this worked before since a long time, this will fool especially but not only long-time users that habitually use encrypted email. -- 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 853580] New: YaST does not create encrypted home folder when creating user
by bugzilla_noreply＠novell.com 05 Dec '13

05 Dec '13

https://bugzilla.novell.com/show_bug.cgi?id=853580 https://bugzilla.novell.com/show_bug.cgi?id=853580#c0 Summary: YaST does not create encrypted home folder when creating user Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: x86-64 OS/Version: openSUSE 13.1 Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: yast2-maintainers(a)suse.de ReportedBy: fredvej(a)yahoo.com QAContact: jsrain(a)suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:25.0) Gecko/20100101 Firefox/25.0 On a fresh installed OpenSUSE 13.1 I want to create a new user with an encrypted home directory. I can't make it work, no matter what I do I just get two unused files in /home and an unencrypted normal home directory for the user. I boot the PC and login as root, start "Control Center" and choose "User and Group Management". In "Users" tab I click Add to create the new user. On the User Data tab I fill in user name and password and then click on the Details tab. Here I mark "Use Encrypted Home Directory" and the Directory Size in MB turns to 100. Now I click OK to exit the setup for the new user. In the main window I click OK again to apply the creating, The "Writing User and Group Configuration" checks the first four lines, but stops on "Write passwords". Error message box "stat: No such file or directory. Failed to open image". I click OK to close the error, and the configuration continues and then exits. In addition to the normal home directory /home/username, in /home appears two files: username.img sized 100 MiB and username.key 288 bytes. So the new user should be created OK, right ? Well, I can login as the new user, but the encryption is not activated, and the username.img is just, 100 MiB NULL bytes and never changes. No /dev/loop is in use, and df shows no sign of a mounted encrypted loop file. So I try again, reboot PC to get a clean slate and login as root and move the two files into hiding and then use YaST to delete the user, including deleting the home directory. Another reboot to make sure the user is gone, and then I bring back the two files to /home, and try to create the user again. This time the error message is "/home/username.img already exists. Use --force to overwrite it." I click OK, and the user is created, but still the encryption is not used. Reproducible: Always Steps to Reproduce: 1.Create new user, mark "Use Encrypted Home Directory" 2.Login as new user Actual Results: In addition to the normal home directory /home/username, in /home appears two files: username.img sized 100 MiB and username.key 288 bytes. I can login as the new user, but the encryption is not activated, and the username.img is just, 100 MiB NULL bytes and never changes. No /dev/loop is in use, and df shows no sign of a mounted encrypted loop file. Expected Results: Login as the user should mount the encrypted loop file and use that for the content of the user's home directory. OpenSUSE 13.1 64 bit, KDE desktop Intel Haswell HD4400 graphics -- 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 809822] New: Beside first virtual console the other from vt2 upto vt6 are missed
by bugzilla_noreply＠novell.com 05 Dec '13

05 Dec '13

https://bugzilla.novell.com/show_bug.cgi?id=809822 https://bugzilla.novell.com/show_bug.cgi?id=809822#c0 Summary: Beside first virtual console the other from vt2 upto vt6 are missed Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: x86-64 OS/Version: SUSE Other Status: NEW Severity: Major Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: werner(a)suse.com QAContact: qa-bugs(a)suse.de CC: fcrozat(a)suse.com Found By: Development Blocker: --- those logins occur at random time later one ... this is annoying during debuging e.g. a bug with kdm. Why does /usr/lib/systemd/system/systemd-logind.service requires nss-user-lookup.target which requires network.target ??? -- 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 853785] New: Icecast won't start because it requires nonexistent syslog.target
by bugzilla_noreply＠novell.com 05 Dec '13

05 Dec '13

https://bugzilla.novell.com/show_bug.cgi?id=853785 https://bugzilla.novell.com/show_bug.cgi?id=853785#c0 Summary: Icecast won't start because it requires nonexistent syslog.target Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: x86-64 OS/Version: openSUSE 13.1 Status: NEW Severity: Normal Priority: P5 - None Component: Network AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: jimc(a)math.ucla.edu QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created an attachment (id=570334) --> (http://bugzilla.novell.com/attachment.cgi?id=570334) Unit file for Icecast modified to get it started. Version: icecast-2.3.3-2.1.2.x86_64 on OpenSuSE-13.1 When you do systemctl start icecast.service, it complains: cannot add dependency job, syslog.target failed to load. The unit file is /usr/lib/systemd/system/icecast.service . OpenSuSE-13.1 does not have syslog.target (unlike 12.2 and 12.3); it has syslog.service which is intended to be socket activated. The fix is to copy the unit file to /etc/systemd/system/icecast.service and change syslog.target to syslog.service. Also the man page for systemd.unit recommends to use Wants rather than Requires unless the requirement is absolute. I've attached a unit file with both these changes. Also the unit file says PIDFile=/var/run/icecast/icecast.pid . My /etc/icecast.xml lacked the (pidfile) element, but I think that may have disappeared while I was trying to debug this problem. In any case, make sure that the (paths) element contains: (pidfile)/var/run/icecast/icecast.pid(/pidfile) (angle brackets changed to parens to protect the guilty.) -- 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 736092] New: Fetchmail does not start
by bugzilla_noreply＠novell.com 05 Dec '13

05 Dec '13

https://bugzilla.novell.com/show_bug.cgi?id=736092 https://bugzilla.novell.com/show_bug.cgi?id=736092#c0 Summary: Fetchmail does not start Classification: openSUSE Product: openSUSE 12.1 Version: Final Platform: x86-64 OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: james.knott(a)rogers.com 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 Fetchmail does not start with either systemd or systemv. With systemv, there is no info in either /var/log/messages or dmesg. With systemd, /var/log/messages contains the following: "Dec 10 17:46:53 linux fetchmail[1666]: Starting fetchmailFile /etc/fetchmailrc must be owned by you. Dec 10 17:46:53 linux startproc: startproc: exit status of parent of /usr/bin/fetchmail: 6 Dec 10 17:46:53 linux fetchmail[1666]: ..failed Dec 10 17:46:53 linux systemd[1]: fetchmail.service: control process exited, code=exited status=7 Dec 10 17:46:53 linux systemd[1]: Unit fetchmail.service entered failed state." However, fetchmailrc is owned by root, as shown: "ls /etc/fetchmailrc -l -rwx------ 1 root root 271 Dec 4 22:02 /etc/fetchmailrc" In previous versions of openSUSE, I have also been able to start fetchmail, as a user, with /etc/init.d/after.local, but that only works with systemv in 12.1. As a result, if I run systemd in 12.1, I have to manually start fetchmail. Reproducible: Always Steps to Reproduce: 1.Enable fetchmail in System Services 2. 3. Actual Results: Fetchmail fails to start on reboot Expected Results: Fetchmail should be running -- 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 853362] New: rpc.gssd segfault during the NFS mount with kerberos ticket NFS client
by bugzilla_noreply＠novell.com 05 Dec '13

05 Dec '13

https://bugzilla.novell.com/show_bug.cgi?id=853362 https://bugzilla.novell.com/show_bug.cgi?id=853362#c0 Summary: rpc.gssd segfault during the NFS mount with kerberos ticket NFS client Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: x86-64 OS/Version: openSUSE 13.1 Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: mcaj(a)suse.com QAContact: qa-bugs(a)suse.de Found By: Field Engineer Blocker: --- HI, We are using the NFS with Kerberos authentication. The ststem has been working for many years. The server is running SLES 11 SP3 and clients are SLES, SLED or OpenSUSE machines. When I updated from OpenSUSE 12.3 to 13.1 I found this bug. Also tested it on the fresh install of OpenSUSE 13.1 with the same results. Step to reproduce: 1. Install OpenSUSE 13.1 and setup there ldap/kerberos autenticication via SSSD -that is working fine there. 2. ask for keytab ticket from the server and save it into /etc/krb5.keytab 3. setup NFS client with support GSS. it might looks like this: grep -v ^# /etc/sysconfig/nfs USE_KERNEL_NFSD_NUMBER="4" MOUNTD_PORT="" NFS_SECURITY_GSS="yes" NFS3_SERVER_SUPPORT="yes" NFS4_SUPPORT="yes" NFS4_SERVER_MINOR_VERSION="0" SM_NOTIFY_OPTIONS="" NFS_START_SERVICES="yes" STATD_OPTIONS="" NFSV4LEASETIME="" RPC_PIPEFS_DIR="" SVCGSSD_OPTIONS="" NFSD_OPTIONS="" GSSD_OPTIONS="" MOUNTD_OPTIONS="" 4. check /etc/krb5.conf and add mount into /etc/fstab default_realm = SUSE.CZ allow_weak_crypto = true clockskew = 300 ticket_lifetime = 7d renew_lifetime = 27d [realms] SUSE.CZ = { kdc = [$ourkerberosserver.suse.cz] default_domain = suse.cz admin_server = [$ourkerberosserver.suse.cz] } [logging] kdc = FILE:/var/log/krb5/krb5kdc.log admin_server = FILE:/var/log/krb5/kadmind.log default = SYSLOG:NOTICE:DAEMON [domain_realm] .site = SUSE.CZ [appdefaults] pam = { ticket_lifetime = 7d renew_lifetime = 28d forwardable = true proxiable = true minimum_uid = 1 external = sshd use_shmem = sshd validate = false clockskew = 300 debug = true keytab = /etc/krb5.keytab } NFS mount from fstab: nfs.suse.cz:/home /home nfs4 sec=krb5i,intr,rw 0 0 the example of /etc/sssd/sssd.conf config_file_version = 2 services = nss,pam domains = default [nss] filter_groups = root filter_users = root [pam] # Section created by YaST [domain/default] ldap_uri = ldap://[$ourldap-server.suse.cz] ldap_search_base = dc=suse,dc=cz ldap_schema = rfc2307bis id_provider = ldap ldap_user_uuid = entryuuid ldap_group_uuid = entryuuid ldap_id_use_start_tls = True enumerate = False cache_credentials = False chpass_provider = krb5 auth_provider = krb5 ldap_tls_cacertdir = /etc/ssl/certs ldap_tls_cacert = /etc/ssl/certs/[$SUSE-R&D-certsfile] krb5_realm = SUSE.CZ krb5_kdcip = [$ourkerberosserver.suse.cz] krb5_validate = False krb5_renewable_lifetime = 27d krb5_lifetime = 7d krb5_keytab = /etc/krb5.keytab krb5_ccachedir = /tmp krb5_ccname_template = FILE:%d/krb5cc_%U_XXXXXX 5. status NFS client: systemctl start nfs and check what happen there: systemctl status nfs nfs.service - LSB: NFS client services Loaded: loaded (/etc/init.d/nfs) Drop-In: /run/systemd/generator/nfs.service.d └─50-insserv.conf-$remote_fs.conf Active: active (running) since Tue 2013-12-03 12:02:45 CET; 2min 17s ago Process: 2061 ExecStart=/etc/init.d/nfs start (code=exited, status=0/SUCCESS) CGroup: /system.slice/nfs.service └─2096 /usr/sbin/rpc.idmapd Dec 03 12:02:30 v-opensusef-nibbler systemd[1]: Starting LSB: NFS client services... Dec 03 12:02:30 v-opensusef-nibbler sm-notify[2085]: Version 1.2.8 starting Dec 03 12:02:30 v-opensusef-nibbler nfs[2061]: Starting NFS client services: sm-notify gssd idmapd..done Dec 03 12:02:30 v-opensusef-nibbler nfs[2061]: Mounting network file systems ..mount.nfs4: mount system call failed Dec 03 12:02:45 v-opensusef-nibbler nfs[2061]: ..done Dec 03 12:02:45 v-opensusef-nibbler systemd[1]: Started LSB: NFS client services. 6. when you try restart NFS the status is even more chatty :systemctl restart nfs;systemctl -l status nfs nfs.service - LSB: NFS client services Loaded: loaded (/etc/init.d/nfs) Drop-In: /run/systemd/generator/nfs.service.d └─50-insserv.conf-$remote_fs.conf Active: active (running) since Tue 2013-12-03 12:05:24 CET; 31s ago Process: 2321 ExecStop=/etc/init.d/nfs stop (code=exited, status=0/SUCCESS) Process: 2346 ExecStart=/etc/init.d/nfs start (code=exited, status=0/SUCCESS) CGroup: /system.slice/nfs.service ├─2365 /usr/sbin/rpc.gssd -D └─2370 /usr/sbin/rpc.idmapd Dec 03 12:05:24 v-opensusef-nibbler sm-notify[2359]: Already notifying clients; Exiting! Dec 03 12:05:24 v-opensusef-nibbler nfs[2346]: Starting NFS client services: sm-notify gssd idmapd..done Dec 03 12:05:24 v-opensusef-nibbler rpc.gssd[2365]: ERROR: GSS-API: error in gss_export_lucid_sec_context(): GSS_S_BAD_MECH (An unsupported mechanism was requested) - Unknown error Dec 03 12:05:24 v-opensusef-nibbler rpc.gssd[2365]: ERROR: failed serializing krb5 context for kernel Dec 03 12:05:24 v-opensusef-nibbler rpc.gssd[2365]: WARNING: Failed to serialize krb5 context for user with uid 0 for server lizard.suse.cz Dec 03 12:05:24 v-opensusef-nibbler rpc.gssd[2365]: ERROR: GSS-API: error in gss_export_lucid_sec_context(): GSS_S_BAD_MECH (An unsupported mechanism was requested) - Unknown error Dec 03 12:05:24 v-opensusef-nibbler rpc.gssd[2365]: ERROR: failed serializing krb5 context for kernel Dec 03 12:05:24 v-opensusef-nibbler rpc.gssd[2365]: WARNING: Failed to serialize krb5 context for user with uid 0 for server lizard.suse.cz Dec 03 12:05:24 v-opensusef-nibbler nfs[2346]: Mounting network file systems ..mount.nfs4: access denied by server while mounting nfs.suse.cz:/home Dec 03 12:05:24 v-opensusef-nibbler nfs[2346]: ..done Dec 03 12:05:24 v-opensusef-nibbler systemd[1]: Started LSB: NFS client services. 7. and see dmesg : [ 20.188572] RPC: Registered named UNIX socket transport module. [ 20.188575] RPC: Registered udp transport module. [ 20.188576] RPC: Registered tcp transport module. [ 20.188576] RPC: Registered tcp NFSv4.1 backchannel transport module. [ 20.190626] FS-Cache: Loaded [ 20.192473] FS-Cache: Netfs 'nfs' registered for caching [ 20.260984] NFS: Registering the id_resolver key type [ 20.260992] Key type id_resolver registered [ 20.260993] Key type id_legacy registered [ 20.268579] rpc.gssd[2091]: segfault at 1 ip 00007f9a4e3cabe5 sp 00007fffad1316e0 error 4 in libgssglue.so.1.0.0[7f9a4e3c7000+9000] [ 20.268713] NFS: nfs4_discover_server_trunking unhandled error -32. Exiting with error EIO [ 35.273089] RPC: AUTH_GSS upcall timed out. Please check user daemon is running. [ 50.318045] RPC: AUTH_GSS upcall timed out. Please check user daemon is running. [ 50.583714] systemd-journald[207]: Received request to flush runtime journal from PID 1 8. I have tried also the manual mount with verbose mode: mount nfs.suse.cz:/home /home -t nfs -o sec=krb5,intr,rw -vv mount.nfs: timeout set for Tue Dec 3 12:51:12 2013 mount.nfs: trying text-based options 'sec=krb5,intr,vers=4,addr=xx.xx.xx.xx,clientaddr=xx.xx.xx.xx' mount.nfs: mount(2): Permission denied mount.nfs: access denied by server while mounting nfs.suse.cz:/home reproducible: on 13.1 All the time. I think the reason why the nfs client with GSS is not working is the segfault of rpc.gssd. The same setting is working on the previews version OpenSUSE 12.3. And also SLED and SLESS machine with 11SP3 version are working fine. The mount without sec=krb5 GSS is working fine. If you need access into our suse.cz network or any other help with debugging, please let me know. Have nice day. Martin Caj. -- 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 853619] New: akonadi's mysql still runnung after logout from KDE
by bugzilla_noreply＠novell.com 05 Dec '13

05 Dec '13

https://bugzilla.novell.com/show_bug.cgi?id=853619 https://bugzilla.novell.com/show_bug.cgi?id=853619#c0 Summary: akonadi's mysql still runnung after logout from KDE Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: x86-64 OS/Version: openSUSE 13.1 Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com 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 mysqld started by akonadi is still running after logout from a KDE session. This prevents accessing akonadi DB files from a different computer because the original mysqld has a lock on the DB files. Setup is, in pseudo: desktop mount /dev/sdX /home laptop mount nfs4 desktop:/home /home I know that using akonadi/mysql via nfs is discouraged because of concurrency issues but it used to work in previous opensuse releases and it should work fine given that the user is not logged in on both the desktop and the laptop. The issue seems related to #852132 , #849870 , #852982 pointing to systemd as the culprit. Reproducible: Sometimes Steps to Reproduce: 1. log into KDE on desktop 2. log out from KDE on desktop 3. export desktop's /home and mount it nfs on laptop:/home Actual Results: akonadi/mysql startup fails on laptop because of mysqld running on desktop is still running and locking DB files Expected Results: mysqld on desktop should terminate at KDE session logout -- 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 819521] New: High CPU Temperature (fresh openSUSE 12.3 install)
by bugzilla_noreply＠novell.com 04 Dec '13

04 Dec '13

https://bugzilla.novell.com/show_bug.cgi?id=819521 https://bugzilla.novell.com/show_bug.cgi?id=819521#c0 Summary: High CPU Temperature (fresh openSUSE 12.3 install) Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: i586 OS/Version: openSUSE 12.3 Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: txm(a)xpdnet.org QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux i686; rv:20.0) Gecko/20100101 Firefox/20.0 My CPU Temperature is 70-75 degrees with no user processes on the background and raises up when running firefox/xchat2/skype or other software. System specs: CPU: AMD V140 RAM: 2GB DDR2 VID: ATI Radeon HD 4200 Series NET: Broadcom Wifi Reproducible: Always Steps to Reproduce: 1. Set CPU freq to 800mhz 2. Disable unused kernel modules 3. Kill unneeded processes like contact manager, apache2 and etc. Actual Results: Nothing happened at CPU temperature remains high. -- 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 725913] New: booting with systemd leads to strange boot output
by bugzilla_noreply＠novell.com 04 Dec '13

04 Dec '13

https://bugzilla.novell.com/show_bug.cgi?id=725913 https://bugzilla.novell.com/show_bug.cgi?id=725913#c0 Summary: booting with systemd leads to strange boot output Classification: openSUSE Product: openSUSE 12.1 Version: RC 1 Platform: x86-64 OS/Version: SuSE Other Status: NEW Severity: Major Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: lmuelle(a)suse.com QAContact: qa(a)suse.de Found By: Development Blocker: --- This is an upgraded system from 11.4 and booting with systemd destroys the messages while booting. Some messages from started daemons are even printed after the first login was very short visible. Switching back to sysvinit by removing the systemd-sysvinit package made all work as expected. -- 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 28