Hello List
am using Xfce : - in /var/log/warn : i see warning
" The gnome keyring socket is not owned with the same credentials as
the user login: /run/user/1000/keyring-4i77r7/control
2013-11-27T13:27:17.434100+02:00 su: gkr-pam: couldn't unlock the login
keyring "
...............
- any ideas how to fix ?
thanks
--
To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse+owner(a)opensuse.org
Hi all,
Reading some mails on the GIMP mail list, I ran across the procedure
to install some more fonts for not only Gimp, but the system and
StarOffice to use also. Well, I installed the fonts, went to the
shell and issued the command xset fp+ <font directory> and then the
rehash command and all fonts are there! Ok, that went well, but each
time I restart the system, I have to do it all over again? Is there
a way to make it permanent and read the new fonts like it does the
ones the system installs or is that a no-no?
end of line
Tracer
Shell commands:
xset fp+ <new font directory>
xset fp rehash
--
---KMail 1.2--- SuSE Linux v7.2---
Registered Linux User #225206
/tracerb(a)sprintmail.com/ *Magic Page Products*
*Team Amiga* http://home.sprintmail.com/~tracerb
Good day, I am trying to find out of shorewall is supposed to work
with 13.2 properly, as I read about systemd stuff being in the midst
of creation and wicked and sort of that things that make it
problematic to run something different from susefirewall2.
Thanks for helping.
--
To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse+owner(a)opensuse.org
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
I have this in "/etc/rsyslog.conf":
if ($programname == 'named' or $syslogtag == '[named]:') \
then -/var/log/named
& stop
...
if ($msg contains 'Started Session' and $msg contains 'of user') \
then -/var/log/systemdpurged
& stop
#
# the rest in one file
#
*.*;mail.none;news.none -/var/log/messages
I get the expected entries in "/var/log/systemdpurged":
<3.6> 2014-03-01 16:30:01 Telcontar systemd 1 - - Started Session 93 of user cer.
<3.6> 2014-03-01 16:33:01 Telcontar systemd 1 - - Started Session 94 of user news.
But I'm also getting them in "/var/log/messages":
<3.6> 2014-03-01 16:30:01 Telcontar systemd 1 - - Starting Session 93 of user cer.
<3.6> 2014-03-01 16:33:01 Telcontar systemd 1 - - Starting Session 94 of user news.
And they should not be there.
So the "stop" line for those systemd entries is not acting. However, it
works for other sections, like the "named" section shown above, and others
I do not show for clarity.
Are systemd entries special?
- --
Cheers
Carlos E. R.
(from 13.1 x86_64 "Bottle" at Telcontar)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)
iEYEARECAAYFAlMSADcACgkQtTMYHG2NR9WCgwCdEgnb+Apy47tcjI31Dv5brA9X
+TMAoIt87JaGgMoP5Zf11OZM0XevIjif
=uI81
-----END PGP SIGNATURE-----
--
To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse+owner(a)opensuse.org
There was a previews thread where namebench was mentioned. I thought
it was the optimizing resolv.conf thread.
Anyway this is a different issue. Id like to run it.
The ones I located in OBS were not functional here.
What could I do to try another source?
Thanks
Steven
--
____________
Apply appropriate technology. Use what works without prejudice.
Steven L Hess ARS KC6KGE DM05gd22
Owner Flex-1500 and Flex-3000, FT-857D, FT-817ND, FT-450
openSUSE Linux 12.3 KDE
Known as FlameBait and The Sock Puppet of Doom.
--
To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse+owner(a)opensuse.org
Hi,
I am trying to set up a simple repo, I read on the opensuse site about
a binary called genIS_PLAINcache, because I can't see to find it or
the package yast2-packmanager either. Can someone help. I am setting
this repo up for SLE9, I have tried to use createrepo but I keeping
getting errors.
--
----------------------------------------
When a place gets crowded enough to require ID's, social collapse is
not far away. It is time to go elsewhere. The best thing about space
travel is that it made it possible to go elsewhere.
-- Robert Heinlein
--
To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse+help(a)opensuse.org
Hello,
Wonder if others using a Sandy-bridge Intel video card (i915) is having
same Plymouth boot splash dark screen with the three ??? question marks
dots.
I tried all the possible solutions found by Googling but the issue
continues.
The problem has raised recently, I suspect caused by some package updates.
Regards,
--
There is no such thing as a problem without a gift for you in its hands.
--
To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse+owner(a)opensuse.org
I am using the version of gftp that is a component of 3.2. When try to
access the opensuse source at:
http://download.opensuse.org
/source/distribution/13.2/repo/oss/suse/src
I receive a directory listing, with some file lengths listed as zero.
When I try to download the files using HTTP I get:
HTTP/1.1 302 Found
Date: Wed, 18 Feb 2015 23:21:32 GMT
Server: Apache/2.2.12 (Linux/SUSE)
X-Prefix: 71.228.144.0/20
X-AS: 33653
X-MirrorBrain-Mirror: suse.mobile-central.org
X-MirrorBrain-Realm: country
Location:
http://suse.mobile-central.org/source/distribution/13.2/repo/oss/suse/src/z…
Content-Type: text/html; charset=iso-8859-1
Disconnecting from site download.opensuse.org
Error: Remote site download.opensuse.org disconnected. Max retries
reached...giving up
I have not done this in awhile, and it used to be from ftp sites. Can
you help me with what I am doing wrong? Is it because the file content
is not text? I know I can download files using a browser. I thought
this would be similar. How does one set up gftp to access these sites?
Thanks, and sorry if a dumb question.
Don
--
To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse+owner(a)opensuse.org
All,
I have not yet investigated the tor network, but as "ransomeware" has become
more prolific, with the bad-guys demanding payment via anonymous tor sites and
bitcoin, it is probably time to understand WTF it is. (a colleague running M$
was hit today) Are there different tor browsers available, or is torproject
basically it.
Also, if anyone has a favorite link explaining the nuts and bolts of the tor
quagmire, I welcome that as well. At first blush, it looks like tor navigation
is basically what internet nav was prior to http (circa 1988). Just looking for
a reference. Will start with wikipedia and go from there.
Castration is too good for these ransomeware weasels.
--
David C. Rankin, J.D.,P.E.
--
To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse+owner(a)opensuse.org
On 19/02/15 16:56, Joe Zappa wrote:
> Peter wrote:
>> Bonjour.
>>
>> This is now driving me mad. Just over a year ago (I had to go hunt
>> down the thread, here:
>> http://lists.opensuse.org/opensuse/2014-01/msg00988.html) the issue
>> was once again raised of why temp files were not being cleaned at boot
>> (on openSUSE 13.1) if one tried to set the system to do so.
>>
>> It was established that the cron job configurable from YaST's
>> sysconfig editor was no longer functional since supposedly being
>> replaced by the all-round saviour and
>> tuck-your-sheets-in-would-you-like-a-cup-of-hot-cocoa-with-that
>> princess that is systemd. Except that the replacement doesn't work. At
>> least not on any of my 13.1 installations, whereupon both /tmp and
>> /var/tmp become laden with relics that outright refuse to ever part my
>> system, gradually filling my root partition until there is no more
>> room for maneouvre. Currently my /tmp is sitting at 5GB. Looking at
>> files in there, many are up to a year old. It seems to just accumulate
>> stuff like an eccentric lonely old man with an attic. This was a fresh
>> 13.1 installation made about a year ago. The root partition (ext4) is
>> 17GB, about half of which was filled after installation. Now there's
>> little left.
>>
>> It was also established that SuSE likes to do its SuSEy thing and go
>> its own way, against systemd defaults, in preserving temp files across
>> reboots, since some SuSErs want their systems configured that way and
>> consider /tmp to be a persistent directory.
>>
>
> I've just given up
>
> Now, when I reboot my machines, I log into root and run a shellscript
> that I call "start"
> which I wrote to do any and all initializations which I USED to put in
> in /etc/init.d/local.initializations and then link to from rc{2,3,5}.d
> directories
> as S99local.initalizations.
>
> But since systemd completely and utterly fucking ignores /etc/init.d/*,
> that's out the window.
>
So is /tmp filling interminably for all users of 13.1 who haven't
otherwise fiddled with something to prevent this, or who don't have /tmp
stored in RAM? I don't understand if this is a universal issue/bug or
it's only affecting certain users, such as those not using btrfs for
example. Google searches aren't throwing up much in the way of openSUSE,
only similar issues affecting various other distros.
I don't know what more I can do to empty my /tmp and /var/tmp aside from
simply rm -rf /tmp. I'm reluctant to do that as a last resort because I
had problems long ago on this same system after emptying temp, although
admittedly I stupidly did that whilst running as user with x.
Doing some more plugging I found that
systemctl -l status systemd-tmpfiles-clean.service
was throwing up a failed message concerning gvfs. Thinking this might be
preventing the service from running, I found a thread on the Arch bug
tracker (https://bugs.archlinux.org/task/32715) which suggests a
workaround for this being to create a file, /etc/tmpfiles.d/gvfs.conf
containing, essentially:
x /run/user/*
to stop systemd going near /run/user at all. Well that changed nothing
on my system. I've tried manually running
systemd-tmpfiles --clean --remove
but again, though it doesn't return an error, nothing is cleaned up or
removed. I also notice when running
systemctl -l status systemd-tmpfiles-clean.service
the lines:
Loaded: loaded
(/usr/lib/systemd/system/systemd-tmpfiles-clean.service; static)
Active: inactive (dead)
It seems to always be inactive. Meanwhile, running
systemctl -l status systemd-tmpfiles-setup.service
I get this:
systemd-tmpfiles-setup.service - Recreate Volatile Files and Directories
Loaded: loaded
(/usr/lib/systemd/system/systemd-tmpfiles-setup.service; static)
Active: active (exited) since Sat 2015-02-21 20:17:27 CET; 2min 4s ago
Docs: man:tmpfiles.d(5)
man:systemd-tmpfiles(8)
Process: 356 ExecStart=/usr/bin/systemd-tmpfiles --create --remove
--exclude-prefix=/dev (code=exited, status=0/SUCCESS)
Main PID: 356 (code=exited, status=0/SUCCESS)
And I've no idea how to go about setting /tmp to store files for 30 days
and /var/tmp for 90 like in the good old days, because there's clearly
not much point even tinkering with that idea until I can get the service
to run at all. The documentation (man page) for systemd-tmpfiles is
awful and tells me nothing useful.
I still have 2.5GB to fill on my root partition. I'll keep waiting.
Before long I'll have to do something.
Peter
--
To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse+owner(a)opensuse.org