June 2013 - openSUSE Users - openSUSE Mailing Lists

[opensuse] systemd fails to start famd
by Carlos E. R. 16 Jun '13

16 Jun '13

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Look: Telcontar:~ # date;systemctl status fam.service Sun Jun 16 14:41:51 CEST 2013 fam.service - LSB: file access monitoring Loaded: loaded (/etc/init.d/fam) Active: failed (Result: exit-code) since Sun, 2013-06-16 14:41:44 CEST; 7s ago Process: 8738 ExecStart=/etc/init.d/fam start (code=exited, status=7) CGroup: name=systemd:/system/fam.service Jun 16 14:41:44 Telcontar.valinor systemd[1]: Starting LSB: file access monitoring... Jun 16 14:41:44 Telcontar.valinor fam[8738]: Starting File Access Monitoring Daemon..failed Jun 16 14:41:44 Telcontar.valinor systemd[1]: Failed to start LSB: file access monitoring. Jun 16 14:41:44 Telcontar.valinor systemd[1]: Unit fam.service entered failed state Telcontar:~ # journalctl -n Jun 16 14:43:23 Telcontar.valinor famd[8826]: can't register with portmapper. Please start a portmapper (for example rpcbind), then try again to start famd. Jun 16 14:43:23 Telcontar.valinor fam[8818]: Starting File Access Monitoring Daemon..failed Jun 16 14:43:23 Telcontar.valinor systemd[1]: fam.service: control process exited, code=exited status=7 Jun 16 14:43:23 Telcontar.valinor systemd[1]: Failed to start LSB: file access monitoring. Jun 16 14:43:23 Telcontar.valinor systemd[1]: Unit fam.service entered failed state lines 1-11/11 (END) Why does it want portmapper? Is it not needed for NFS? Ie, network filesystems? Surely, NFS is also failing. Telcontar:~ # date;systemctl status nfsserver.service Sun Jun 16 14:44:55 CEST 2013 nfsserver.service - LSB: Start the kernel based NFS daemon Loaded: loaded (/etc/init.d/nfsserver) Active: failed (Result: exit-code) since Sun, 2013-06-16 13:57:46 CEST; 47min ago CGroup: name=systemd:/system/nfsserver.service └ 3152 /usr/sbin/rpc.idmapd Jun 16 13:57:46 Telcontar.valinor systemd[1]: Starting LSB: Start the kernel based NFS daemon... Jun 16 13:57:46 Telcontar.valinor startproc[4700]: startproc: exit status of parent of /usr/sbin/rpc.mountd: 1 Jun 16 13:57:46 Telcontar.valinor nfsserver[4661]: Starting kernel based NFS server: idmapd mountd..failed Jun 16 13:57:46 Telcontar.valinor systemd[1]: Failed to start LSB: Start the kernel based NFS daemon. Jun 16 13:57:46 Telcontar.valinor systemd[1]: Unit nfsserver.service entered failed state Telcontar:~ # Telcontar:~ # date;systemctl status rpcbind.service Sun Jun 16 14:46:12 CEST 2013 rpcbind.service - RPC Bind Loaded: loaded (/usr/lib/systemd/system/rpcbind.service; disabled) Active: inactive (dead) CGroup: name=systemd:/system/rpcbind.service Telcontar:~ # Starting and or enabling them: Telcontar:~ # date;systemctl enable rpcbind.service Sun Jun 16 14:46:34 CEST 2013 ln -s '/usr/lib/systemd/system/rpcbind.service' '/etc/systemd/system/multi-user.target.wants/rpcbind.service' ln -s '/usr/lib/systemd/system/rpcbind.socket' '/etc/systemd/system/sockets.target.wants/rpcbind.socket' Telcontar:~ # date;systemctl start rpcbind.service Sun Jun 16 14:46:40 CEST 2013 Telcontar:~ # date;systemctl status rpcbind.service Sun Jun 16 14:46:43 CEST 2013 rpcbind.service - RPC Bind Loaded: loaded (/usr/lib/systemd/system/rpcbind.service; enabled) Active: active (running) since Sun, 2013-06-16 14:46:40 CEST; 2s ago Main PID: 8968 (rpcbind) CGroup: name=systemd:/system/rpcbind.service └ 8968 /sbin/rpcbind -w -f Jun 16 14:46:40 Telcontar.valinor systemd[1]: Started RPC Bind. Telcontar:~ # Telcontar:~ # date;systemctl restart nfsserver.service Sun Jun 16 14:47:30 CEST 2013 Telcontar:~ # date;systemctl status nfsserver.service Sun Jun 16 14:47:36 CEST 2013 nfsserver.service - LSB: Start the kernel based NFS daemon Loaded: loaded (/etc/init.d/nfsserver) Active: active (running) since Sun, 2013-06-16 14:47:30 CEST; 5s ago Process: 8995 ExecStart=/etc/init.d/nfsserver start (code=exited, status=0/SUCCESS) CGroup: name=systemd:/system/nfsserver.service ├ 3152 /usr/sbin/rpc.idmapd ├ 9016 /usr/sbin/rpc.mountd └ 9019 /usr/sbin/rpc.statd --no-notify Jun 16 14:47:30 Telcontar.valinor systemd[1]: Starting LSB: Start the kernel based NFS daemon... Jun 16 14:47:30 Telcontar.valinor rpc.mountd[9016]: Version 1.2.7 starting Jun 16 14:47:30 Telcontar.valinor rpc.statd[9019]: Version 1.2.7 starting Jun 16 14:47:30 Telcontar.valinor rpc.statd[9019]: Flags: TI-RPC Jun 16 14:47:30 Telcontar.valinor nfsserver[8995]: Starting kernel based NFS server: idmapd mountd statd nfsd sm-notify..done Jun 16 14:47:30 Telcontar.valinor systemd[1]: Started LSB: Start the kernel based NFS daemon. Telcontar:~ # Telcontar:~ # date;systemctl status fam.service Sun Jun 16 14:48:05 CEST 2013 fam.service - LSB: file access monitoring Loaded: loaded (/etc/init.d/fam) Active: failed (Result: exit-code) since Sun, 2013-06-16 14:43:23 CEST; 4min 41s ago CGroup: name=systemd:/system/fam.service Jun 16 14:43:23 Telcontar.valinor systemd[1]: Starting LSB: file access monitoring... Jun 16 14:43:23 Telcontar.valinor fam[8818]: Starting File Access Monitoring Daemon..failed Jun 16 14:43:23 Telcontar.valinor systemd[1]: Failed to start LSB: file access monitoring. Jun 16 14:43:23 Telcontar.valinor systemd[1]: Unit fam.service entered failed state Telcontar:~ # date;systemctl restart fam.service Sun Jun 16 14:48:11 CEST 2013 Telcontar:~ # date;systemctl status fam.service Sun Jun 16 14:48:13 CEST 2013 fam.service - LSB: file access monitoring Loaded: loaded (/etc/init.d/fam) Active: active (running) since Sun, 2013-06-16 14:48:11 CEST; 2s ago Process: 9059 ExecStart=/etc/init.d/fam start (code=exited, status=0/SUCCESS) CGroup: name=systemd:/system/fam.service └ 9067 /usr/sbin/famd -t 4 -T 0 Jun 16 14:48:11 Telcontar.valinor systemd[1]: Starting LSB: file access monitoring... Jun 16 14:48:11 Telcontar.valinor fam[9059]: Starting File Access Monitoring Daemon..done Jun 16 14:48:11 Telcontar.valinor systemd[1]: Started LSB: file access monitoring. Telcontar:~ # - -- Cheers Carlos E. R. (from 12.3 x86_64 "Dartmouth" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) iEYEARECAAYFAlG9tX0ACgkQtTMYHG2NR9XPZQCfQaiWRG3b1B0rRSYhAWYtwR/x ASAAn0pC2GzVY6TpRsLyiWM59pc1igYO =xSsO -----END PGP SIGNATURE-----

4 7

[opensuse] systemd restart
by Moby 16 Jun '13

16 Jun '13

How does one restart systemd without rebooting the OS? I have some OSS machines that use Samba for AD integration. Whenever Samba is updated, libwinbind* all get updated. Prior to OSS 12.3, I could just restart services that used files that had been updated and everything was good. Now, however, systemd appears to use libwinbind* and I have no idea how to get systemd to use the new libwind. I cannot figure out how to restart systemd without a system reboot. Any help is appreciated. -- --Moby They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety. -- Benjamin Franklin -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

3 7

[opensuse] Systemd fails to start my spamd
by Carlos E. R. 16 Jun '13

16 Jun '13

Hi, look at this: > Telcontar:~ # date;systemctl restart spamd.service > Sat Jun 15 22:58:36 CEST 2013 > Job for spamd.service failed. See 'systemctl status spamd.service' and 'journalctl -n' for details. > Telcontar:~ # date;systemctl status spamd.service > Sat Jun 15 22:58:40 CEST 2013 > spamd.service - Daemonized version of spamassassin > Loaded: loaded (/usr/lib/systemd/system/spamd.service; enabled) > Active: failed (Result: exit-code) since Sat, 2013-06-15 22:58:36 CEST; 3s ago > Process: 31577 ExecStart=/usr/sbin/spamd $SPAMD_ARGS -r /var/run/spamd.pid (code=exited, status=64) > Process: 31573 ExecStartPre=/bin/echo Starting spamd: (code=exited, status=0/SUCCESS) > CGroup: name=systemd:/system/spamd.service > > Jun 15 22:58:36 Telcontar.valinor spamd[31577]: --ssl-version sslversion Specify SSL protocol version to use > Jun 15 22:58:36 Telcontar.valinor spamd[31577]: --server-key keyfile Specify an SSL keyfile > Jun 15 22:58:36 Telcontar.valinor spamd[31577]: --server-cert certfile Specify an SSL certificate > Jun 15 22:58:36 Telcontar.valinor spamd[31577]: --socketpath=path Listen on given UNIX domain socket > Jun 15 22:58:36 Telcontar.valinor spamd[31577]: --socketowner=name Set UNIX domain socket file's owner > Jun 15 22:58:36 Telcontar.valinor spamd[31577]: --socketgroup=name Set UNIX domain socket file's group > Jun 15 22:58:36 Telcontar.valinor spamd[31577]: --socketmode=mode Set UNIX domain socket file's mode > Jun 15 22:58:36 Telcontar.valinor spamd[31577]: -V, --version Print version and exit > Jun 15 22:58:36 Telcontar.valinor systemd[1]: Failed to start Daemonized version of spamassassin. > Jun 15 22:58:36 Telcontar.valinor systemd[1]: Unit spamd.service entered failed state > Telcontar:~ # Is systemd calling "/usr/sbin/spamd $SPAMD_ARGS -r /var/run/spamd.pid" without expanding "$SPAMD_ARGS"? > Telcontar:~ # cat /usr/lib/systemd/system/spamd.service > # This file is part of package amavisd. > # > # Copyright (c) 2011 SuSE LINUX Products GmbH, Germany. > # Author: Werner Fink > # Please send feedback to http://www.suse.de/feedback > # > # Description: > # > # Used to start the spamd the daemonized version of spamassassin > # spamassassin adds a header line that shows if the mail has been > # determined spam or not. This way, you can decide what to do with the > # mail within the scope of your own filtering rules in your MUA (Mail > # User Agent, your mail program) or your LDA (Local Delivery Agent). > # > > [Unit] > Description=Daemonized version of spamassassin > Requires=remote-fs.target syslog.target > After=remote-fs.target syslog.target > Before=mail-transfer-agent.target > Conflicts= > > [Service] > Type=forking > PIDFile=/var/run/spamd.pid > ExecStartPre=-/bin/echo 'Starting spamd:' > EnvironmentFile=-/etc/sysconfig/spamd > ExecStart=/usr/sbin/spamd $SPAMD_ARGS -r /var/run/spamd.pid > > [Install] > WantedBy=multi-user.target > Telcontar:~ # I edit the line, replacing the contents: #ExecStart=/usr/sbin/spamd $SPAMD_ARGS -r /var/run/spamd.pid ExecStart=/usr/sbin/spamd -d -c --max-children=6 -r /var/run/spamd.pid Then restart the service: > Telcontar:~ # date;systemctl restart spamd.service > Sat Jun 15 23:05:52 CEST 2013 > Warning: Unit file of spamd.service changed on disk, 'systemctl --system daemon-reload' recommended. > Job for spamd.service failed. See 'systemctl status spamd.service' and 'journalctl -n' for details. > Telcontar:~ # systemctl --system daemon-reload > Telcontar:~ # date;systemctl restart spamd.service > Sat Jun 15 23:06:09 CEST 2013 > Telcontar:~ # date;systemctl status spamd.service > Sat Jun 15 23:07:19 CEST 2013 > spamd.service - Daemonized version of spamassassin > Loaded: loaded (/usr/lib/systemd/system/spamd.service; enabled) > Active: active (running) since Sat, 2013-06-15 23:06:11 CEST; 1min 8s ago > Process: 31800 ExecStart=/usr/sbin/spamd -d -c --max-children=6 -r /var/run/spamd.pid (code=exited, status=0/SUCCESS) > Process: 31796 ExecStartPre=/bin/echo Starting spamd: (code=exited, status=0/SUCCESS) > Main PID: 31802 (/usr/sbin/spamd) > CGroup: name=systemd:/system/spamd.service > ├ 31802 /usr/sbin/spamd -d -c --max-children=6 -r /var/run/spamd.pid > ├ 31805 spamd child > └ 31806 spamd child > > Jun 15 23:06:11 Telcontar.valinor spamd[31802]: rules: meta test FROM_12LTRDOM has dependency 'ALL_TRUSTED' with a zero score > Jun 15 23:06:11 Telcontar.valinor spamd[31802]: rules: meta test HDRS_LCASE has dependency 'ALL_TRUSTED' with a zero score > Jun 15 23:06:11 Telcontar.valinor spamd[31802]: rules: meta test TBIRD_SPOOF has dependency 'ALL_TRUSTED' with a zero score > Jun 15 23:06:11 Telcontar.valinor spamd[31802]: spamd: server started on port 783/tcp (running version 3.3.2) > Jun 15 23:06:11 Telcontar.valinor spamd[31802]: spamd: server pid: 31802 > Jun 15 23:06:11 Telcontar.valinor spamd[31802]: spamd: server successfully spawned child process, pid 31805 > Jun 15 23:06:11 Telcontar.valinor systemd[1]: Started Daemonized version of spamassassin. > Jun 15 23:06:11 Telcontar.valinor spamd[31802]: spamd: server successfully spawned child process, pid 31806 > Jun 15 23:06:11 Telcontar.valinor spamd[31802]: prefork: child states: IS > Jun 15 23:06:11 Telcontar.valinor spamd[31802]: prefork: child states: II > Telcontar:~ # > > Telcontar:~ # ps afxu | grep spamd > root 31872 0.0 0.0 7048 860 pts/21 S+ 23:09 0:00 | | \_ grep --color=auto spamd > root 31802 0.6 0.7 144792 59876 ? Ss 23:06 0:01 /usr/sbin/spamd -d -c --max-children=6 -r /var/run/spamd.pid > root 31805 0.0 0.7 144792 57492 ? S 23:06 0:00 \_ spamd child > root 31806 0.0 0.7 144792 57476 ? S 23:06 0:00 \_ spamd child > Telcontar:~ # So indeed, the variable was not expanded, because me editing it works. Why? Bug? Surprising, after several months of release... -- Cheers / Saludos, Carlos E. R. (from 12.3 x86_64 "Dartmouth" at Telcontar)

5 5

[opensuse] Configuring Gnus for opensuseforums via nntp
by toganm＠opensuse.org 15 Jun '13

15 Jun '13

Hi, I seem to be not able to get Gnus work with opensuseforums. According to the FAQ of the forums there are servers A and B nntp.netiq.com and nntp.suse.com I have the following in my gnus.el as the gnus-selec-method is already defined for gmane.org (add-to list 'gnus-secondary-select-methods '(nntp "nntp.suse.com")) All I am getting is the following Opening nntp server on nntp.suse.com...failed: Error when connecting: 200 Welcome to forums.novell.com! (Typhoon v2.1.2.394) Error when connecting: 200 Welcome to forums.novell.com! (Typhoon v2.1.2.394) Unable to contact server nntp.suse.com: Error when connecting: 200 Welcome to forums.novell.com! (Typhoon v2.1.2.394) Connecting to nntp.netiq.com... Opening nntp server on nntp.netiq.com...failed: Error when connecting: 200 Welcome to forums.novell.com! (Typhoon v2.1.2.394) Error when connecting: 200 Welcome to forums.novell.com! (Typhoon v2.1.2.394) Unable to contact server nntp.netiq.com: Error when connecting: 200 Welcome to forums.novell.com! (Typhoon v2.1.2.394) What I am missing -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

4 9

[opensuse] looking for pgAdmin 1.16.xx
by Andreas 15 Jun '13

15 Jun '13

Hi even though openSUSE 12.3 provides PostgreSQL 9.2.4 in it's repository, it only offers pgAdmin 1.14.x which complains to be outdated for PG 9.2.x. Even the packet search on the web page doesn't cough up pgAdmin 1.16.x. which isn't actually brand new. Where could I look? regards Andreas -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

2 1

[opensuse] Do I have a rpm database corruption (OpenSUSE 12.3) (noobish)
by h 15 Jun '13

15 Jun '13

Hi, I have a fully patched [1] installation of OpenSuse 12.3. It was a clean install on a reformatted partition. For some time now (sorry, I have no record of when it started, or what happened to cause it), when doing "zypper up" I get messages such as: ************************************************************************ Installation of libqmmp0-plugin-mplayer-debuginfo-0.7.1-45.3 failed: (with --nodeps --force) Error: Subprocess failed. Error: RPM failed: error: db4 error(-30986) from dbcursor->c_get: DB_PAGE_NOTFOUND: Requested page not found error: error(-30986) getting "Development/Debug" records from Group index error: libqmmp0-plugin-mplayer-debuginfo-0.7.1-45.3.x86_64: install failed error: libqmmp0-plugin-mplayer-debuginfo-0.7.1-45.2.x86_64: erase skipped error: libqmmp0-plugin-mplayer-debuginfo-0.7.1-45.1.x86_64: erase skipped error: libqmmp0-plugin-mplayer-debuginfo-0.7.0-44.2.x86_64: erase skipped error: libqmmp0-plugin-mplayer-debuginfo-0.7.0-44.1.x86_64: erase skipped error: libqmmp0-plugin-mplayer-debuginfo-0.7.0-41.1.x86_64: erase skipped error: libqmmp0-plugin-mplayer-debuginfo-0.7.0-40.4.x86_64: erase skipped error: libqmmp0-plugin-mplayer-debuginfo-0.7.0-40.3.x86_64: erase skipped Abort, retry, ignore? [a/r/i] (a): ************************************************************************ I ignore and continue and eventually the command finishes. The failures only appear to occur with debuginfo packages. The rest of the updates appear to install and run correctly. I am guessing that part of my rpm database has become corrupt. Can I reconstruct the database, or a part of it? (I have had a look at the rpm documentation, but it is beyond my understanding, so a link to a basic / tutorial example, or some **simple to follow** instructions would be greatly appreciated!! With thanks, H -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

6 7

[opensuse] How to stop KDE complaining about an unknown device?
by Andreas 15 Jun '13

15 Jun '13

Everytime I log in KDE pops up a message that it doesn't know what to do with the sound card. It asks if it should ignore this device and there is a checkbox that says "don't ask this question again". Even when I check this checkbox the message still comes up at login. As I don't need sound on this system I would rather disable this particular message completely. How can I stop KDE complaining about an unknown device? regards Andreas -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 0

[opensuse] systemd hides important information for diagnosis of rsyslog.
by Carlos E. R. 15 Jun '13

15 Jun '13

I have an rsyslog with a configuration error. However: Telcontar:~ # systemctl restart rsyslog Telcontar:~ # It claims success, but it is not true, it fails seconds later: > Telcontar:~ # systemctl status rsyslog > rsyslog.service - System Logging Service > Loaded: loaded (/usr/lib/systemd/system/rsyslog.service; enabled) > Active: failed (Result: start-limit) since Thu, 2013-06-13 23:48:23 CEST; 4s ago > Process: 13783 ExecReload=/bin/kill -HUP $MAINPID (code=exited, status=0/SUCCESS) > Process: 16495 ExecStart=/usr/sbin/rsyslogd -n $RSYSLOGD_PARAMS (code=exited, status=1/FAILURE) > Process: 16491 ExecStartPre=/usr/sbin/rsyslog-service-prepare (code=exited, status=0/SUCCESS) > CGroup: name=systemd:/system/rsyslog.service > > Jun 13 23:48:23 Telcontar.valinor systemd[1]: Failed to start System Logging Service. > Jun 13 23:48:23 Telcontar.valinor systemd[1]: Failed to start System Logging Service. > Jun 13 23:48:23 Telcontar.valinor systemd[1]: Failed to start System Logging Service. > Jun 13 23:48:23 Telcontar.valinor systemd[1]: Failed to start System Logging Service. > Jun 13 23:48:23 Telcontar.valinor systemd[1]: Failed to start System Logging Service. > Jun 13 23:48:23 Telcontar.valinor systemd[1]: Failed to start System Logging Service. > Jun 13 23:48:23 Telcontar.valinor systemd[1]: Failed to start System Logging Service. > Jun 13 23:48:23 Telcontar.valinor systemd[1]: Failed to start System Logging Service. > Jun 13 23:48:23 Telcontar.valinor systemd[1]: Failed to start System Logging Service. > Jun 13 23:48:23 Telcontar.valinor systemd[1]: Failed to start System Logging Service. > Telcontar:~ # journalctl -n says nothing different. Calling rsyslog says something else that is not in systemd log: > Telcontar:~ # rsyslogd > rsyslogd: run failed with error -2207 (see rsyslog.h or try http://www.rsyslog.com/e/2207 to learn what that number means) > Telcontar:~ # Looking at the service call I see it uses the parameter "-n". ExecStart=/usr/sbin/rsyslogd -n $RSYSLOGD_PARAMS If I do, then I get this: which tells me the exact and useful error: > Telcontar:~ # /usr/sbin/rsyslogd -n > rsyslogd: error during parsing file /etc/rsyslog.conf, on or before line 262: syntax error on token 'isequal' [try http://www.rsyslog.com/e/2207 ] > rsyslogd: CONFIG ERROR: could not interpret master config file '/etc/rsyslog.conf'. [try http://www.rsyslog.com/e/2207 ] > rsyslogd: run failed with error -2207 (see rsyslog.h or try http://www.rsyslog.com/e/2207 to learn what that number means) > Telcontar:~ # Why is not systemd logging this output? It has its own log system, it does not depend on syslog working... -- Cheers / Saludos, Carlos E. R. (from 12.3 x86_64 "Dartmouth" at Telcontar)

5 22

[opensuse] Re: [opensuse-factory] Re: Question about findutils-locate
by James Knott 15 Jun '13

15 Jun '13

Linda Walsh wrote: >> Ie, if I'm plain user john:users, I should have permissions to use >> locate on my "/home/john" directory, but not those of /root, and maybe >> yes, maybe not, those of "/home/ian", depending on group permissions. > --- > I would say it should let you see the same files you can see > with 'ls'. > > If I am not root, and ls /root, I can see nothing. > > OTOH, Just because I can't write to files in /usr/bin or whatever, > doesn't > mean I wouldn't want them to show up in a locate. Even if the files > are unreadable -- if they are in a directory that is readable, > then their names should appear on locate. IIRC, locate simply searches a file created by updatedb. Since updatedb runs as root, it should contain all files. Since locate can be run by anyone, anyone can see all the files. To do anything else would require updatedb to save the permissions and locate to honour them. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

3 2

[opensuse] Systemd kills text terminals
by Carlos E. R. 15 Jun '13

15 Jun '13

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 [CTRL][Alt][F1] does not work. chvt 1 - hangs. It was working an hour ago. Removing plymouth-branding-openSUSE and plymouth-scripts, tabooing them. - -- Cheers / Saludos, Carlos E. R. (from 12.3 x86_64 "Dartmouth" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlG1GwsACgkQIvFNjefEBxqTgACguLG0ep2YJOkwa2W8UmcvzZs8 qAAAniKgqsPAqUsGcmajiWszjlnrlQKD =5iUl -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

7 29