Yes, that got rid of the messages.
Thanks,
Frank M. Ramaekers Jr.
-Original Message-
From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of
Jan Stodola
Sent: Thursday, March 03, 2016 12:46 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: ClefOS 7.1.1503 install "KDE&qu
You can check /etc/sysconfig/initial-setup and set
RUN_INITIAL_SETUP=NO
Initial setup is failing to start when you log in, this should disable
it from running.
On 03/03/2016 07:19 PM, Frank M. Ramaekers wrote:
Okay, got through an install of ClefOS 7.1.1503, but I keep getting
email like:
Okay, got through an install of ClefOS 7.1.1503, but I keep getting
email like:
>From u...@localhost.torchmarkcorp.com Thu Mar 3 10:18:55 2016
Return-Path:
X-Original-To: root@localhost
Delivered-To: r...@localhost.domain.com
Date: Thu, 03 Mar 2016 10:18:55 -0600
From: u...@localhost.do
is not that
verbose, so it might hide the low level but important details.
Dan
> [root@fedora ~]# dnf groupinstall "KDE Plasma Workspaces"
> Last metadata expiration check performed 0:06:36 ago on Wed Jan 20
> 07:09:52
> 2016.
> Error: nothing provid
I was wrong apparently the groupinstall never did work..@#!#%
I guess I just have to wait for the package fix..
[root@fedora ~]# dnf groupinstall "KDE Plasma Workspaces"
Last metadata expiration check performed 0:06:36 ago on Wed Jan 20 07:09:52
2016.
Error: nothing provides plasmash
>>> On 1/8/2016 at 09:11 AM, Tom Huegel wrote:
> Here is what that shows..
> [root@fedora ~]# ps ax | grep dm
>74 ?S< 0:00 [dm_bufio_cache]
> 820 ?S< 0:00 [kdmflush]
> 831 ?S< 0:00 [kdmflush]
> 862 ?S< 0:00 [xfs-buf/dm-0]
> 863 ?
Here is what that shows..
[root@fedora ~]# ps ax | grep dm
74 ?S< 0:00 [dm_bufio_cache]
820 ?S< 0:00 [kdmflush]
831 ?S< 0:00 [kdmflush]
862 ?S< 0:00 [xfs-buf/dm-0]
863 ?S< 0:00 [xfs-data/dm-0]
864 ?S< 0:00 [xfs-con
>>> On 1/7/2016 at 03:52 PM, Tom Huegel wrote:
> When I try STARTX I get:
> [root@fedora /]# startx
> xauth: file /root/.serverauth.2220 does not exist
> xinit: unable to run server "/usr/bin/X": No such file or directory
> Use the -- option, or make sure that /usr/bin is in your path and
> that
/]#
On Thu, Jan 7, 2016 at 12:14 PM, Tom Huegel wrote:
> I don't know .. I get really confused easily.
>
> On Thu, Jan 7, 2016 at 11:52 AM, Mark Post wrote:
>
>> >>> On 1/7/2016 at 02:44 PM, Tom Huegel wrote:
>> > It appears the packaging problem has be
On Thu, 7 Jan 2016 11:44:10 -0800
Tom Huegel wrote:
> It appears the packaging problem has been resolved.
> I ran dnf groupinstall "KDE Plasma Workspaces" and it installed.
thanks for the update, I'm glad it worked this time :-)
> But when I VNC to FEDORA F23 all I ge
>>> On 1/7/2016 at 02:44 PM, Tom Huegel wrote:
> It appears the packaging problem has been resolved.
> I ran dnf groupinstall "KDE Plasma Workspaces" and it installed.
>
> But when I VNC to FEDORA F23 all I get is a blank blue screen (It looks a
> lot like t
you can try also
dnf groups install "KDE Plasma Workspaces"
On 12/08/2015 11:32 PM, Dan Horák wrote:
On Tue, 8 Dec 2015 14:04:15 -0800
Tom Huegel wrote:
When I try to do this:
[root@fedora ~]# dnf groupinstall "KDE Plasma Workspaces"
I get this:
Last metadata expirati
On Tue, 8 Dec 2015 14:04:15 -0800
Tom Huegel wrote:
> When I try to do this:
> [root@fedora ~]# dnf groupinstall "KDE Plasma Workspaces"
>
> I get this:
> Last metadata expiration check performed 2:55:39 ago on Tue Dec 8
> 14:04:18
> 2015.
> Error: nothing pro
When I try to do this:
[root@fedora ~]# dnf groupinstall "KDE Plasma Workspaces"
I get this:
Last metadata expiration check performed 2:55:39 ago on Tue Dec 8 14:04:18
2015.
Error: nothing provides plasmashell >= 5.4 needed by
plasma-workspace-5.4.2-4.fc23.s390.
nothing provid
A co-worker found this Redbook about tuning SLES. While the focus is on
xSeries hardware, a lot of the concepts are platform agnostic.
http://www.redbooks.ibm.com/redpapers/pdfs/redp3862.pdf
I found the section on using KDE SysGuard to be pretty neat. By
installing the stand alone package
-- :1
This starts a 2nd kde desktop on the intel. Go to it : ctl-alt-f8
ssh -X to the mainframe and startkde on the mainframe
It now all works fine. All my mainframe stuff is now on the 2nd desktop.
(I do had to kill the 2nd "kicker" prior to the ssh, but I think this is a
kicker bu
rame Linux KDE desktop within Xnest.
-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of
Ifurung, [EMAIL PROTECTED]
Sent: Friday, February 18, 2005 1:47 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: KDE
OK, here's the process that I've tried:
1) Using
> What I'd really want to do is run the mainframe kde client on
> a separate
> window.
You're confusing client, server and window manager. In X terms, the X
*server* runs on the machine with the keyboard and mouse, as does the
window manager. Clients run *anywhere* and poin
> 5) run "kde". Corrupts the window and kills kicker but continues to run
> somewhat.
The desktop opens up a bunch of windows and you create a mess of
various windows on your workstation managed by two different window
managers. You probably should not run a desktop but stick to
OK, here's the process that I've tried:
1) Using desktop intel linux, boots up and login in kde environment.
2) start a "konsole" shell
3) ssh -X mainframeLinux
4) while login to mainframeLinux, I can run things like, xeyes, xclock,
yast2, konqueror successfully with no proble
If you make sure that you forward X11 traffic through ssh, then there
will be a DISPLAY variable set to a local socket the the
authentication is taken care of as well. That's probably simpler than
fiddle with xhost stuff.
Rob
--
Rob van der Heij rvdheij @ gmail.com
--
Simplest is:
1) set up remote login using SSH keys instead of userid/pw (see
ssh-keygen and ssh man page) on mainframe linux.
2) on Intel: ssh [EMAIL PROTECTED] command
your $DISPLAY var and shell environment are carried over to the
mainframe Linux if set on Intel, and the client pops up just l
I have a SUSE9 on an intel desktop. With this desktop running as X-server,
what is the correct procedure to run a KDE client of the mainframe SLES9 .
When I run KDE on top of the desktop KDE, the windows goes crazy and kills
the kicker. What I like to do is run the mainframe KDE client on an
t;
If it is installed, then do this:
1. "ldd -v /opt/kde/bin/kreadconfig"
2. Send me the output off-list
Mark Post
--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] wit
Hmm. That sounds like one of the tagfiles might be messed up. If it is not
installed:
1. Post that to the list
2. Do an "installpkg /path/to/package/elflibs-9.1.0-s390-1.tgz"
If it is installed, then do this:
1. "ldd -v /opt/kde/bin/kreadconfig"
2. Send me the output
I installed the package and it looks like it's working. But like I said, I did a full
install and I checked the "a" directory and that package is there.
Onward and forward.
l
>>> [EMAIL PROTECTED] 09/15/04 11:09AM >>>
It looks like you didn't install the elflibs-9.1.0-s390-1 package. That's
On Wed, 2004-09-15 at 09:41, Richard Pinion wrote:
> I'm getting the following when attempting to use kde.
>
> [EMAIL PROTECTED]:~# cat .xsession-errors
> stderr is not a tty - where are you?
> startkde: Starting up...
> kreadconfig: /usr/lib/./libgcc_s.so.1: version `GCC_3
I'll check on that, but I did choose the "full install" with no prompting.
--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.ma
er 15, 2004 10:41 AM
To: [EMAIL PROTECTED]
Subject: Slack390 9.1 kde
I'm getting the following when attempting to use kde.
[EMAIL PROTECTED]:~# cat .xsession-errors
stderr is not a tty - where are you?
startkde: Starting up...
kreadconfig: /usr/lib/./libgcc_s.so.1: version `GCC_3.3' n
I'm getting the following when attempting to use kde.
[EMAIL PROTECTED]:~# cat .xsession-errors
stderr is not a tty - where are you?
startkde: Starting up...
kreadconfig: /usr/lib/./libgcc_s.so.1: version `GCC_3.3' not found (required by
/usr/lib/./libstdc++.so.5)
ksplash: /usr/lib/./l
New kdelibs and kdebase packages are available for Slack/390 9.1, and
-current to fix security issues.
More details about this issues may be found in the Common Vulnerabilities
and Exposures (CVE) database:
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CAN-2004-0689
http://cve.mitre.org/cgi-b
I didn't think it was Yast, either. What I ended up doing was ctrl-alt-2 to
get out of the kde desktop to a Plain ol' tty and take care of it that way,
ctrl-alt-7 to get back to KDE. I knew it was a problem in Konsole, but
you'd think they'd at LEAST default to VT100 emulati
> I find that when using telnet to access my s/390 linux machine from a
> Konsole shell window under KDE 3.0, into yast 1.07.1 PF keys don't
> translate properly. When adding a user, for instance, I
> cannot actually enter 'PF-4' to add them. It acts like an escape
y not YaST-specific.
Mark Post
-Original Message-
From: James Melin [mailto:[EMAIL PROTECTED]]
Sent: Thursday, October 03, 2002 11:49 AM
To: [EMAIL PROTECTED]
Subject: Interesting issue with Konsole from KDE 3.0 telnetting into
SUSE 7.0 distro using yast 1.07.1
I find that when using telnet
|
| cc:
|
| Subject: Interesting issue with Konsole from KDE 3.0 telnetting into SUSE
7.0 distro usi
I find that when using telnet to access my s/390 linux machine from a
Konsole shell window under KDE 3.0, into yast 1.07.1 PF keys don't
translate properly. When adding a user, for instance, I cannot actually
enter 'PF-4' to add them. It acts like an escape or something. The resu
d x11 applications and desktop environment as Kde and Gnome.
=
After installation i've also checked with "rpm -qa" command if packages
=
was installed and everithings seems to be fine, but I'm not able to =
launch both environment kde & Gnome: infact searching in to director
: Kde & Gnome on RedHat 7.2 s390
arch
Sent by: Linux
on 390 Port
<[EMAIL PROTECTED]
ARIST.EDU>
21.06.02 12:04
Please respond
to Li
Hello,
I've just installed Linux RedHat 7.2 on VM image. During installation i've selected
x11 applications and desktop environment as Kde and Gnome. After installation i've
also checked with "rpm -qa" command if packages was installed and everithings seems to
be
t;kdm", DEFAULT_WM="kde"
4. Check, if in your rc{your_run_level_}.d present link to xdm script.
Lionel Dyck
cc:
Sent by: Linux Subject: xdm and kde on sles
on 390 Port
Following chapter 12 in the SLES System and Reference manual isn't
helping much. I've got a few questions:
1. there is no step in this chapter on how to get xdm to start at boot
time
2. there is no doc on how to configure it to use kdm/kde
when I connect I get a screen with XDMCP
using sles how does one setup xdm/kde? the process is different from suse
7.0.
I've got it connecting but get a screen that has the word list and options
to cancel, accept, or ping - with only cancel appearing to work.
Bradley,
What was that process?
Mark Post
-Original Message-
From: Bradley Snyder [mailto:[EMAIL PROTECTED]]
Sent: Monday, January 28, 2002 11:11 AM
To: [EMAIL PROTECTED]
Subject: Getting KDE to work with SuSE 2.4 Kernel
> I am running into problems getting my KDE desktop to o
> I am running into problems getting my KDE desktop to open with the SuSE
2.4
> kernel I just installed. I used the same process as for the 2.2 kernel
but
> I am getting no connections. Are there any known issues with the new
> kernel that I don't know about?
Thanks
44 matches
Mail list logo
