openSUSE Users March 2015

users@lists.opensuse.org

95 participants
145 discussions

Web Site Standards
by Bryan Tyson 25 Sep '21

25 Sep '21

On Wednesday 03 July 2002 03:38, Michael wrote: > I tried to visit this site. > http://www.bet365.com > The result upset me so much i sent them this. I sent the letter below, and I encourage everyone on the list to send a similar letter. ----------------------------------------- Subject: Create a Real Web Site Please From: Bryan S. Tyson <bryantyson(a)earthlink.net> To: webmaster(a)bet365.com When attempting to view your site using Konqueror 2.2.1 and Mozilla 0.9.4, both Linux web browsers, I was curtly informed that my browser is "incompatible." Your site, sir, is what is "incompatible." Stick with established standards and real html, not Microsoft proprietary "features." *************************************************** Powered by SuSE Linux 7.3 Professional KDE 2.2.1 KMail 1.3.1 This is a Microsoft-free computer Bryan S. Tyson bryantyson(a)earthlink.net ***************************************************

10 9

Mount Windows NT(NTFS) drive as drive Z: for all users
by Keith Jacobs 25 Sep '21

25 Sep '21

We have an winNT server and need to auto mount a shared folder as if it were a windose mapped drive Z: on SuSE8 Could someone please explain how to do this and how to make sure it is set-up for every user everytime the system is booted. Thanks Regards Keith Jacobs New to Linux

3 2

[opensuse] oS 13.1 : "gnome keyring socket is not owned with the same credentials as the user"
by ellanios82 11 Aug '19

11 Aug '19

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

2 1

Adding fonts?
by Tracer Bullet 22 Aug '16

22 Aug '16

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

3 2

[opensuse] Does 13.2+ work with shorewall properly yet? Read about wicked/systemd woes
by cagsm 06 Jun '16

06 Jun '16

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

8 20

[opensuse] I can not filter out some systemd messages in syslog
by Carlos E. R. 17 May '16

17 May '16

-----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

2 2

[opensuse] Namebench
by Steven Hess 25 Dec '15

25 Dec '15

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

4 5

[opensuse] Where can I get genIS_PLAINcache
by Chuck Payne 09 Nov '15

09 Nov '15

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

4 4

[opensuse] Strange messages in log, when cron jobs run, about "Failed to open private bus connection"
by Carlos E. R. 06 Apr '15

06 Apr '15

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hi, Since recently, I think, I get these messages on the warn log when a cron job runs, on two computers at least: <3.4> 2015-03-31 02:34:01 minas-tirith systemd 4025 - - Failed to open private bus connection: Failed to connect to socket /run/user/9/dbus/user_bus_socket: No such file or directory <3.4> 2015-03-31 02:38:01 minas-tirith systemd 4096 - - Failed to open private bus connection: Failed to connect to socket /run/user/9/dbus/user_bus_socket: No such file or directory <3.4> 2015-03-31 02:44:01 minas-tirith systemd 4195 - - Failed to open private bus connection: Failed to connect to socket /run/user/9/dbus/user_bus_socket: No such file or directory <3.4> 2015-03-31 02:45:01 minas-tirith systemd 4229 - - Failed to open private bus connection: Failed to connect to socket /run/user/0/dbus/user_bus_socket: No such file or directory <3.4> 2015-03-31 02:48:01 minas-tirith systemd 4508 - - Failed to open private bus connection: Failed to connect to socket /run/user/9/dbus/user_bus_socket: No such file or directory <3.4> 2015-03-31 02:54:01 minas-tirith systemd 4627 - - Failed to open private bus connection: Failed to connect to socket /run/user/9/dbus/user_bus_socket: No such file or directory <3.4> 2015-03-31 02:58:01 minas-tirith systemd 4873 - - Failed to open private bus connection: Failed to connect to socket /run/user/9/dbus/user_bus_socket: No such file or directory <3.4> 2015-03-31 03:00:01 minas-tirith systemd 4955 - - Failed to open private bus connection: Failed to connect to socket /run/user/0/dbus/user_bus_socket: No such file or directory User 0 is root, and 9 is news. Those directories do not exist, obviously. Should they? (they are not logged-in). And those messages are spamming the warning log. Anything that goes to the warning log is supposedly VERY important. It the message is trivial, it is a bug to create them on warning level, IMO. - -- Cheers Carlos E. R. (from 13.1 x86_64 "Bottle" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iF4EAREIAAYFAlUZ9MoACgkQja8UbcUWM1yziAD+Pc2t90zgZWvI8j9EB68yWFFY QHJeqvwnAUciZiXnZl0A+wUgb+TUJhDGQ2jFINuvXg75u21IZsJ0IY33JOHUqMSL =0Zh3 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

3 6

[opensuse] 13.1 Bash HISTCONTROL=erasedups -- not working? confirm?
by David C. Rankin 06 Apr '15

06 Apr '15

All, A value of HISTCONTROL=erasedups causes all previous lines matching the current line to be removed from the history list before that line is saved. (man bash) This isn't working on 13.1 for me. Can anyone else confirm that duplicates are NOT removed in 13.1 when this value is set? Searching, it looks like other distros have patched bash to insure this works when multiple terminals are open. (e.g.: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/189881) If this is confirmed, could something similar be done here? The reason, after moving my history file from 11.4 to 13.1 and running for close to a year, I have close to 14,000 duplicate lines -- despite having 'erasedups' set: current lines: 20000 - uniq lines: 6099 = 13901 duplicates To fix the problem temporarily, I wrote the current file out, then sorted uniquely, then deleted the current history, read the sorted unique file in as current, and wrote the current back to HISTFILE: $ history -w | sort | uniq > uniqfile $ history -c $ history -r uniqfile $ history -w $ rm uniqfile That seems to have fixed the issue in the current session, and ~/.bash_history is current correct, but when closing the remaining sessions, I suspect the duplicates will once again be written to ~/.bash_history, even though 'erasedups' is set. If someone can confirm 13.1 is ignoring 'erasedups', I'll file the bug. -- 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

4 16

Jump to page:

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

2000

1999

1998

1997

1996

1995

1994

1993

1992

openSUSE Users March 2015