| |
| |
| |
|
Page: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
Comments:
<0> moka_: out of luck this time. next time look into screen or nohup beforehand
<1> tybalt, no. a process is running with PID 1023 but i want to make it run in the foreground.
<2> moka_: i was hoping for some clarification
<3> did you send it to the background
<1> whitecap, yeah i think so too.
<1> tybalt, no i mistakenly stopped gdm and there you go! :(
<3> Viking667, what are you talking about?
<3> moka_, reboot the system
<1> tybalt, **** that
<1> tybalt, there's should be another way.
<2> there's ?
<4> moka_: try this: kill -CONT 1023
<3> ctrl+alt+[F1-F7]
<1> Viking667, i don't want to kill the process.
<3> if you have command line access, start gdm again
<5> tybalt: Just STFU. No advice is better than bad advice.
<3> Nobody was talking to you, ThomasM
<1> NetBandit, have all these conversations made the situation clear to you ?
<4> moka_: I'm actually serious. It won't STOP the process, it'll CONTinue the process.
<2> yeah i understand what you want, i just dont know how :(
<1> Viking667, nope.
<4> moka_: read "man 7 signal" and "man kill" for more explanations
<1> Viking667, already did. before issuing the command.
<2> moka_: i've been in the same situation as well, but never had a solution
<4> Didn't continue it?
<1> Viking667, nope.
<1> NetBandit, i think whitecap did say abt this earlier. moka_: out of luck this time. next time look into screen or nohup beforehand
<4> Right. What distribution are you on? Mandriva? Fedora? Debian?
<1> Viking667, debian.
<4> hm.
<4> Do you have a current X session you need to get back to, or can you lose it safely?
<6> moka_: restart it -- gdm-restart gdm-safe-restart
<0> you can restart X with no problem, can't get thet program back afaik
<4> insmod: thank you. I wondered if there was any way.
<1> whitecap, yeah. screen offers solution but i didn't look into that earlier.
<6> Viking667: :)
<4> ... and given you can...hang on.
<4> I've just thought of something.
<4> Can you start a VNC server pointing at that X session? (x0rfbserver is an example)
<4> Because if you can you may have a chance if you have a second machine with a vnc client.
<1> Viking667, are you talking to me ?
<4> yeah.
<5> Hah. Good idea, Viking667.
<1> Viking667, i only have 1 machine.
<4> uhmmm., vino is another example of a VNC server
<4> But they all depend upon having a second machine.
<1> Viking667, just start the server and client in the same machine
<4> Darn.
<1> Viking667, don't you think ?
<4> Then you'll lose the programs in that X session once you restart it. Unless it's shifted TTYs on you.
<4> moka_: can't do, unless you start up a second X server; :1
<1> Viking667, bummer...... :/
<4> Is it the gdm you want to get back to, or the X session that gdm started?
<5> What'd you lose that was so important?
<1> Viking667, yeah I'll restart gdm.
<4> moka_: there's no reason why you can't start a second X session... in your .xinitrc put "xterm " and start up "startx -- :1"
<0> start the leeching over
<4> moka_: if you restart gdm, then you'll lose what you were running.
<1> Viking667, true. i think i'll have to shut xchat and start irssi with screens. thanks. be back
<6> Viking667: no need to put "xterm " in .xinitrc -- "startx -- :1" should work fine
<1> Viking667, exactly the last time.
<4> insmod: I'm giving him a xterm so he can start other programs, dear dude.
<1> Viking667, if i shut gdm, it's hard to get that program on.
<4> ... moka_??
<4> err, WHAT program?
<4> Remember I came into this from halfway.
<1> Viking667, err.. process.
<1> Viking667, :)
<6> Viking667: no need it loads with startx i think
<1> Viking667, be back.. thanks so far. :)
<6> Viking667: X starts xterm
<0> depends on the distro
<4> insmod: no it doesn't. Not unless someone puts that into a xsession somewhere.
<6> Viking667: default xsession has it
<4> in fact, startx doesn't even start a window manager unless it's in a xsession or xinitrc somewhere.
<4> insmod: default for what distro?
<6> Viking667: most i try -- on deb it works -- cat /etc/skel/.xsession | grep xterm
<4> ahhh. I'll go take a look at that.
<4> doesn't exist here.
<6> Viking667: hmm -- what if you startx -- :1 do you get any term?
<4> I've got a customised .xinitrc and .Xsession so it'll pick up on at least ONE of those.
<4> I'd have to create a new user to test that.
<6> Viking667: everytime i load it works
<6> Viking667: no customised configs -- just the wm
<0> Viking667: that's debian based and by default it would start tvm with about three xterms oddly shaped and a oclock
<4> hm. I don't get that - I get "perhaps you do not have console ownership"... which would be about right.
<4> ... given that I logged on using root.
<4> Ah huh. I'll try logging on as user, see what that does.
<0> Viking667: check /etc/securetty or somesuch ?
<0> nah, you couldn't log in then
<6> Viking667: startx -- :1 -- or have the wm in the rc file - or in xfce startxfce -- :1 etc
<4> crikey. Damn default is set to kde...blech
<4> I created user, logged in, typed "startx -- :1" and it gives me startkde.
<6> Viking667: startkde -- :1
<4> lol. Funny that.
<6> Viking667: mandrivia for ya -- mandrake 6 was ok
<4> hmmm. I haven't done this for years. Previously to about 2004, I used a manual script I'd written, called "MyX", which was a text frontend for a WM, when it was run, it prompted user for couple of things, then executed X with those same things.
<4> Became a bit useless once I started using gdm.
<6> Viking667: the wifes computer uses gdm -- i don't
<6> Viking667: did it work
<4> Well, yeah. Didn't do just the xterm though. AS I said, the default here is to start KDE. yeesh.
<6> Viking667: lol never used kde but the wife does
<4> I find that it's nice once it gets its legs under it. And 3.5.x is better performing than 3.4.x, though I've already found one bug with the kde-mixer
<6> Viking667: it got better when they redid it with QT
<4> i.e. the mixer itself works fine, but when I ***ign the media keys to raise/lower volume, that only changes the "Master-Mono" volume, not the "Master" volume.
<4> insmod: hrm? They DID?
<4> When wasn't it done with qt?
<6> Viking667: 10 years ago
<6> around then
<4> yup. That'd be a while ago. I was barely playing with Gnome-0.3 at that stage.
<6> Viking667: never got gnome to load -- always crashes -- but the apps rock
<6> Viking667: even they know that that is why they use other front ends meta etc
<4> yeah. Running with enlightenment and the panel at the moment, seeing as gnome-session+metacity doesn't like me much...
<6> Viking667: see -- enlightenment rocks -- as does xfce -- before 4 -- blackbox -- and mindow maker
<6> window maker that is
<4> I haven't yet pinned down what it is about metacity that I don't like, or that doesn't work.
<6> Viking667: CDE rocks as well
<4> Metacity works, don't get me wrong (or did, before I upgraded to 2007.0)
<4> insmod: actually, I don't like CDE much. I've used it, and just ... don't like it.
<6> Viking667: as i said evertime i load a box i check it -- doen't work -- so i don't use it
<6> Viking667: that's why i love the old xfce
<4> insmod: define "doesn't work" for you...?
<6> Viking667: and will xfce change there mane with xorg hmmmmm
<6> Viking667: click app crash -- please report this ...
<4> err, WHAT app?
<6> Viking667: lol no idea last time i tried it was ......... 3 4 yrs ago
<7> hi Viking667, sorry was busy drinking coffee ;)
<4> you're not being terrifically detailed. And don't say "any app", that doesn't wash.
<4> insmod: then you can't have loaded a machine for a while... given the 3 - 4 years gap.
<6> Viking667: just my experience
<6> Viking667: never got it to go so i never use it
<4> And both KDE and Gnome have changed heaps since 4 years ago...
<6> Viking667: ya the wife loves kde
<6> Viking667: artsd another story :)
<4> I like it too, but it ****s more memory, and takes longer to get started.
<4> dunno about artsd. Just Works(TM) for me.
<6> Viking667: not for non kde apps though
<6> Viking667: even when i use k3b in xfce or enightenment etc i have to killall -9 artsd after lol
<6> jerks lol
<6> Viking667: microsoft in drag
<8> hello all.
<8> This is the KDE session I started...
<4> I don't think I have THAT problem with artsd. It shuts up when KDE does.
<8> so no, I'm not disappointed (this time) with KDE.
<8> heh. Guess that's the signal for me to leave.
<6> Viking667: not if you are in it -- unless the time out is lower -- who knows lol
<6> Viking667: tha'ts kde for ya
Return to
#linux
or
Go to some related
logs:
back to the base london
15young teens
#linux
bridge 2 ethernet cards
#london
hidebehind dewez
mastermind scanf c++
´farmbot readme
#MissKitten
michelle19
|
|