On Sun, Sep 23, 2018 at 11:51:29AM -0400, Gene Heskett wrote:
> gene@rock64:~$ sudo netstat -anp|grep 6000
> [sudo] password for gene:
> gene@rock64:~$ sudo netstat -anp|grep 6000
> gene@rock64:~$
>
> Nothing returned, did it twice while logged into the rock64 as
> UID=1000=gene
>
> What is thi
Hi there
On 23/09/2018 20:07, Grzesiek Sójka wrote:
On 9/23/18 2:36 PM, Rob van der Putten wrote:
On 23/09/2018 13:48, Grzegorz Sójka wrote:
I need to allow remote applications to connect to xorg. Since I log
in using lxdm i have tcp_listen=1 in /etc/lxdm/lxdm.conf. Thus Xorg
is running w
On 9/23/18 2:36 PM, Rob van der Putten wrote:
Hi there
On 23/09/2018 13:48, Grzegorz Sójka wrote:
I need to allow remote applications to connect to xorg. Since I log in
using lxdm i have tcp_listen=1 in /etc/lxdm/lxdm.conf. Thus Xorg is
running without -nolisten tcp flag. Unfortunately:
$
On 9/23/18 4:00 PM, Gene Heskett wrote:
> On Sunday 23 September 2018 06:30:01 Étienne Mollier wrote:
> > Maybe try:
> >
> > xhost +LOCAL:
> > DISPLAY=localhost:0.0 xterm
>
> On which machine? The target of the ssh login, or this one
> with the comfy office chair to sit it?
That is not cle
On Sunday 23 September 2018 10:36:01 Rob van der Putten wrote:
Humm, my puzzle for X11Forwarding has even more pieces.
copy/pasted from the konsole logged into the rock64, running stretch
gene@rock64:~$ sudo netstat -anp|grep 6000
[sudo] password for gene:
gene@rock64:~$ sudo netstat -anp|grep 6
On Sunday 23 September 2018 09:20:34 Étienne Mollier wrote:
> On 9/23/18 5:06 PM, Grzesiek Sójka wrote:
> > $ xhost +LOCAL: ; DISPLAY=localhost:0.0 xterm
> > non-network local connections being added to access control list
> > xterm: Xt error: Can't open display: localhost:0.0
>
> Whoops, however
Hi there
On 23/09/2018 13:48, Grzegorz Sójka wrote:
I need to allow remote applications to connect to xorg. Since I log in
using lxdm i have tcp_listen=1 in /etc/lxdm/lxdm.conf. Thus Xorg is
running without -nolisten tcp flag. Unfortunately:
$ xhost +localhost; DISPLAY=localhost:0.0 xterm
l
On Sunday 23 September 2018 06:30:01 Étienne Mollier wrote:
> On 9/23/18 1:48 PM, Grzegorz Sójka wrote:
> > Hi there,
> >
> > I need to allow remote applications to connect to xorg. Since I log
> > in using lxdm i have tcp_listen=1 in /etc/lxdm/lxdm.conf. Thus Xorg
> > is running without -nolisten
On 9/23/18 5:14 PM, Grzesiek Sójka wrote:
> On 9/23/18 1:06 PM, Étienne Mollier wrote:
> > ssh -YC user@remotehost
>
> I do not need encryption since all machines are in the same
> network segment. So I prefer not to use ssh.
In that case, perhaps you should simply test with remote
clients; I
On 9/23/18 5:06 PM, Grzesiek Sójka wrote:
> $ xhost +LOCAL: ; DISPLAY=localhost:0.0 xterm
> non-network local connections being added to access control list
> xterm: Xt error: Can't open display: localhost:0.0
Whoops, however the DISPLAY=localhost:0.0 was a typo of mine.
DISPLAY=:0.0 should have b
On 9/23/18 1:06 PM, Étienne Mollier wrote:
On 9/23/18 2:59 PM, The Wanderer wrote:
On 2018-09-23 at 10:24, Grzesiek Sójka wrote:
On 9/23/18 10:30 AM, Étienne Mollier wrote:
Maybe try:
xhost +LOCAL:
DISPLAY=localhost:0.0 xterm
It does not work:
# xhost +LOCAL; DISPLAY=localh
Étienne Mollier (2018-09-23):
> or removing “-nolisten” to Xorg parameters:
Finally somebody in this thread who payed attention in the last fifteen
years...
Regards,
--
Nicolas George
signature.asc
Description: Digital signature
On 9/23/18 2:59 PM, The Wanderer wrote:
> On 2018-09-23 at 10:24, Grzesiek Sójka wrote:
> > On 9/23/18 10:30 AM, Étienne Mollier wrote:
> > > Maybe try:
> > >
> > > xhost +LOCAL:
> > > DISPLAY=localhost:0.0 xterm
> >
> > It does not work:
> >
> > # xhost +LOCAL; DISPLAY=localhost:0.0 xterm
> >
On 9/23/18 12:59 PM, The Wanderer wrote:
On 2018-09-23 at 10:24, Grzesiek Sójka wrote:
On 9/23/18 10:30 AM, Étienne Mollier wrote:
On 9/23/18 1:48 PM, Grzegorz Sójka wrote:
Hi there,
I need to allow remote applications to connect to xorg. Since I
log in using lxdm i have tcp_listen=1 in /e
On 2018-09-23 at 10:24, Grzesiek Sójka wrote:
> On 9/23/18 10:30 AM, Étienne Mollier wrote:
>
>> On 9/23/18 1:48 PM, Grzegorz Sójka wrote:
>>
>>> Hi there,
>>>
>>> I need to allow remote applications to connect to xorg. Since I
>>> log in using lxdm i have tcp_listen=1 in /etc/lxdm/lxdm.conf.
>>>
On 9/23/18 12:27 PM, Anders Andersson wrote:
On Sun, Sep 23, 2018 at 4:24 PM, Grzesiek Sójka wrote:
On 9/23/18 10:30 AM, Étienne Mollier wrote:
On 9/23/18 1:48 PM, Grzegorz Sójka wrote:
Hi there,
I need to allow remote applications to connect to xorg. Since I log in
using lxdm i have tcp_l
On Sun, Sep 23, 2018 at 4:24 PM, Grzesiek Sójka wrote:
> On 9/23/18 10:30 AM, Étienne Mollier wrote:
>>
>> On 9/23/18 1:48 PM, Grzegorz Sójka wrote:
>>>
>>> Hi there,
>>>
>>> I need to allow remote applications to connect to xorg. Since I log in
>>> using lxdm i have tcp_listen=1 in /etc/lxdm/lxdm
On 9/23/18 10:30 AM, Étienne Mollier wrote:
On 9/23/18 1:48 PM, Grzegorz Sójka wrote:
Hi there,
I need to allow remote applications to connect to xorg. Since I log in using
lxdm i have tcp_listen=1 in /etc/lxdm/lxdm.conf. Thus Xorg is running without
-nolisten tcp flag. Unfortunately:
$ xhos
On 9/23/18 1:48 PM, Grzegorz Sójka wrote:
> Hi there,
>
> I need to allow remote applications to connect to xorg. Since I log in using
> lxdm i have tcp_listen=1 in /etc/lxdm/lxdm.conf. Thus Xorg is running without
> -nolisten tcp flag. Unfortunately:
>
> $ xhost +localhost; DISPLAY=localhost:0
Hi there,
I need to allow remote applications to connect to xorg. Since I log in
using lxdm i have tcp_listen=1 in /etc/lxdm/lxdm.conf. Thus Xorg is
running without -nolisten tcp flag. Unfortunately:
$ xhost +localhost; DISPLAY=localhost:0.0 xterm
localhost being added to access control list
Good time of the day, Camaleón.
Thank You for Your time and answer!
You wrote:
> I suggested because you seemed to have many X related packages
> udpated and it could be that Xorg needed to be power-cycled.
And that's why I did it. :o)
> > But I have already solved the problem for me - removin
On Wed, 29 Aug 2012 01:37:17 +0700, Sthu Deus wrote:
>> This can sound a bit odd but have you tried with a system restart?
>
> It happened right after restart! :o)
Ouch!
I suggested because you seemed to have many X related packages udpated
and it could be that Xorg needed to be power-cycled.
Good time of the day, Camaleón.
Thank You for Your time and answer, again.
You wrote:
> This can sound a bit odd but have you tried with a system restart?
It happened right after restart! :o)
But I have already solved the problem for me - removing all seemed
Gconf-related config. garbage accum
-init-tools:amd64 8-2 -> 9-1
>
> I can not run several X app.s from sux-ed user:
>
> $ chromium
> No protocol specified
> (chromium:N): Gtk-WARNING **: cannot open display: :0
(...)
This can sound a bit odd but have you tried with a system restart?
Greetings,
--
specified
(chromium:N): Gtk-WARNING **: cannot open display: :0
$ liferea
(liferea:N): GConf-WARNING **: Client failed to connect to the D-BUS
daemon: /usr/bin/dbus-launch terminated abnormally with the following
error: No protocol specified Autolaunch error: X11 initialization
failed.
GConf Error:
On Sat, May 30, 2009 at 5:28 PM, Lorenzo wrote:
> Well, googling "no protocol specified cannot open display" gave me a hint:
> are you trying to run gedit with root privilege, as in "sudo gedit
> /etc/apt/sources.list" (or /boot/grub/menu.lst or whatever)?
> If th
Aniruddha ha scritto:
Hi,
After an certain amount of time applications no longer open on my
Gnome desktop, When I try to run a program from an already opened
terminal I get the following output:
$ gedit
No protocol specified
cannot open display:
When I log out and in the problem is solved
Hi,
After an certain amount of time applications no longer open on my
Gnome desktop, When I try to run a program from an already opened
terminal I get the following output:
$ gedit
No protocol specified
cannot open display:
When I log out and in the problem is solved. Is this a know bug in
On Sat, Aug 23, 2008 at 08:12:11PM +0200, Aniruddha wrote:
> On Fri, 2008-08-22 at 11:17 -0700, Bob McGowan wrote:
> > I'd guess "libgnomebreakpad.so" is not accessible from within the
> > schroot environment.
> >
> > And without it, GTK and nero can't do anything affecting the display.
> >
> >
On Fri, 2008-08-22 at 11:17 -0700, Bob McGowan wrote:
> I'd guess "libgnomebreakpad.so" is not accessible from within the
> schroot environment.
>
> And without it, GTK and nero can't do anything affecting the display.
>
> *However*, this is all guesswork, my knowledge of schroot (or chroot,
>
access control list
$ schroot -p nero
I: [sid-1516ecae-815d-4eb3-ab8c-c7a94befa26f chroot] Running command:
“nero”
Gtk-Message: Failed to load module "gnomebreakpad":
libgnomebreakpad.so: cannot open shared object file: No such file or
directory
(nero:23894): Gtk-WARNING **: cannot op
onnections being added to access control list
$ schroot -p nero
> I: [sid-1516ecae-815d-4eb3-ab8c-c7a94befa26f chroot] Running command:
> “nero”
> Gtk-Message: Failed to load module "gnomebreakpad":
> libgnomebreakpad.so: cannot open shared object file: No such file or
> di
command: “nero”
(nero:456): Gtk-WARNING **: cannot open display: :0.0
I have set up a succesfull schroot before, the only difference now is
that I use sudo.
"DISPLAY=:0" doesn't work either:
(sid32)[EMAIL PROTECTED]:/# export DISPLAY=:0
(sid32)[EMAIL PROTECTED]:/# nero
(nero:423
nd: “nero”
>
> (nero:456): Gtk-WARNING **: cannot open display: :0.0
I have set up a succesfull schroot before, the only difference now is
that I use sudo.
"DISPLAY=:0" doesn't work either:
> (sid32)[EMAIL PROTECTED]:/# export DISPLAY=:0
> (sid32)[EMAIL PROTECTED]:/
Am 2006-03-29 12:03:26, schrieb Niels Larsen:
> I am using debian sarge.
>
> When I try to run: "sudo synaptic" I get the below warning.
synaptic with sudo?
I do not use synaptic, but does it not work like aptitude?
I mean, you run it as $USER and if it comes to the installation
of the package(
I am using debian sarge.
When I try to run: "sudo synaptic" I get the below warning.
(synaptic:4338): Gtk-WARNING **: cannot open display:
I have to my ~/.bash_profile file added following, according to advice from
some mailing list, but it does not help:
if [[ -z $DISPLA
Niels Larsen wrote:
> I am using debian sarge.
>
> When I try to run: "sudo synaptic" I get the below warning.
>
> (synaptic:4338): Gtk-WARNING **: cannot open display:
>
> I have to my ~/.bash_profile file added following, according to advice from
> some
The problem you have is with sudo, not with your shell. What happens is that
in the configuration file (/etc/sudoers) the env_reset option is set, which
causes most of the environment variables to be deleted. This option comes
enabled by default because of some conflictive variables:
http://lists.g
Luis R Finotti wrote:
> Hi,
>
> On Wed, 29 Mar 2006, Niels Larsen wrote:
>
>> I am using debian sarge.
>>
>> When I try to run: "sudo synaptic" I get the below warning.
>>
>> (synaptic:4338): Gtk-WARNING **: cannot open display:
>>
>>
Hi,
On Wed, 29 Mar 2006, Niels Larsen wrote:
I am using debian sarge.
When I try to run: "sudo synaptic" I get the below warning.
(synaptic:4338): Gtk-WARNING **: cannot open display:
I have to my ~/.bash_profile file added following, according to advice from
some mailing list, b
I am using debian sarge.
When I try to run: "sudo synaptic" I get the below warning.
(synaptic:4338): Gtk-WARNING **: cannot open display:
I have to my ~/.bash_profile file added following, according to advice from
some mailing list, but it does not help:
if [[ -z $DISPLA
On Mon, 8 Nov 2004 03:58:12 -0800 (PST), belahcene abdelkader
<[EMAIL PROTECTED]> wrote:
>
> hi,
> in some distro ( like unbutu : debian-like), when I
> use the su - from the normal user to run an
> administartor command , I get cannot open display: 0.0
> I give the acces
hi,
in some distro ( like unbutu : debian-like), when I
use the su - from the normal user to run an
administartor command , I get cannot open display: 0.0
I give the access with xhost +,( in the normal user )
but the problem remains
this is an example:
as a normal login user:
[EMAIL
It seems to me that your are missing the gnome-common libs. there are
few gnome packages you MUST have if you wish to run gtk apps. i *think*
if you apt-get install gnome-common your probs will go away, but i havnt
thought about this in a very long time.
cheers
-howell
ZekeVarg wrote:
I'm runn
Gimp, gtkam. KDE's qt programs works just fine, and no the gtk
programs dont start at all.
Zeke
On Tue, 2003-08-05 at 18:20, Howell Evans wrote:
> what program is giving you that error? Does the program run at all?
>
> cheers
> -Howell
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with
> Yeah... shutdown X and then restart it. If that doesn't work...
That helpt, thanks. I'm new to debian, used to run RedHat.
Zeke
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
On Tue, 2003-08-05 at 13:57, ZekeVarg wrote:
> Hi!
>
> Have just installed debian and run a dist-upgrade to sid. Now when I try
> to open a gtk based program I get this error message:
>
> Gtk-WARNING **: cannot open display:
>
> Any idee's on what's th
On Tue, 2003-08-05 at 10:57, ZekeVarg wrote:
> Hi!
>
> Have just installed debian and run a dist-upgrade to sid. Now when I try
> to open a gtk based program I get this error message:
>
> Gtk-WARNING **: cannot open display:
>
> Any idee's on what's the pr
what program is giving you that error? Does the program run at all?
cheers
-Howell
ZekeVarg wrote:
Hi!
Have just installed debian and run a dist-upgrade to sid. Now when I try
to open a gtk based program I get this error message:
Gtk-WARNING **: cannot open display:
Any idee's on what&
I'm running X as a user. QT programs works just fine.
Zeke
> IIRC, the display is not set by default for root. If you are
> trying to do this as root you need to set the display manually,
> or better yet, start X as a regular user, not root, and then
> only use root when you absolutely have to.
Hi!
Have just installed debian and run a dist-upgrade to sid. Now when I try
to open a gtk based program I get this error message:
Gtk-WARNING **: cannot open display:
Any idee's on what's the problem and how to fix it?
Zeke
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sun, Jul 20, 2003 at 11:17:09AM +0100, David selby wrote:
> Gtk-WARNING **: cannot open display:
> I know cron works AOK on non x programs
Cron only works with non-interactive programs.
- --
.''`. Paul Johnson &
Sebastian Kapfer wrote:
On Sun, 20 Jul 2003 13:30:10 +0200, David selby wrote:
PS works with mozilla
mozilla --display=:0
Mozilla is GDK/GTK-based. Those apps use the GNU-style long options with
two leading dashes.
* * * * * dillo --display=:0
works for me. (What about DISPLAY=:0 dillo?)
On Sun, 20 Jul 2003 13:30:10 +0200, David selby wrote:
> PS works with mozilla
> mozilla --display=:0
Mozilla is GDK/GTK-based. Those apps use the GNU-style long options with
two leading dashes.
* * * * * dillo --display=:0
works for me. (What about DISPLAY=:0 dillo?)
--
Best Regards, | H
IL PROTECTED]
Subject: Cron <[EMAIL PROTECTED]> /usr/X11R6/bin/dillo
X-Cron-Env:
X-Cron-Env:
X-Cron-Env:
X-Cron-Env:
Message-Id: <[EMAIL PROTECTED]>
Sender: CronDaemon <[EMAIL PROTECTED]>
Date: Sun, 20 Jul 2003 11:10:01 +0100
Setting locale to C
Gtk-WARNING **: cannot open displa
IL PROTECTED]
Subject: Cron <[EMAIL PROTECTED]> /usr/X11R6/bin/dillo
X-Cron-Env:
X-Cron-Env:
X-Cron-Env:
X-Cron-Env:
Message-Id: <[EMAIL PROTECTED]>
Sender: CronDaemon <[EMAIL PROTECTED]>
Date: Sun, 20 Jul 2003 11:10:01 +0100
Setting locale to C
Gtk-WARNING **: cannot open displa
[EMAIL PROTECTED] (Cron Daemon)
> To: [EMAIL PROTECTED]
> Subject: Cron <[EMAIL PROTECTED]> /usr/X11R6/bin/dillo
> X-Cron-Env:
> X-Cron-Env:
> X-Cron-Env:
> X-Cron-Env:
> Message-Id: <[EMAIL PROTECTED]>
> Sender: CronDaemon <[EMAIL PROTECTED]>
> Da
-Cron-Env:
X-Cron-Env:
X-Cron-Env:
X-Cron-Env:
Message-Id: <[EMAIL PROTECTED]>
Sender: CronDaemon <[EMAIL PROTECTED]>
Date: Sun, 20 Jul 2003 11:10:01 +0100
Setting locale to C
Gtk-WARNING **: cannot open display:
OK so i know its something to do with $DISPLAY, I tried setting
DISPLA
Jan Ulrich Hasecke said:
> Hi!
>
> I fear this is a faq.
>
> It is said that ssh tunnels the x-connection and that all you have
> to do is:
>
> To login with
> % ssh -X -l username host
try using -v for verbose. it will tell you if X forwarding
was accepted by the remote host or not. it can also t
% ssh -X -l username host
> % password
> and type
> % xterm
>
> Nothing about removing -nolisten tcp in xserverrc and so on.
>
> But when I do it, I get the error
>
> cannot open display
>
> I have the default settings in the ssh-configs on woody.
--
It's better to reign in hell,
than to serve in heaven...
Jan Ulrich Hasecke <[EMAIL PROTECTED]> writes:
> I fear this is a faq.
Umpf! Sorry. Its vica versa. I can shh -X from a potato-box to a
woody-box but not from the woody-box to the potato-box.
Sorry for that
juh
--
Auf die FDP ist Verlass
http://www.sudelbuch.de/2000/2214.html
Hi!
I fear this is a faq.
It is said that ssh tunnels the x-connection and that all you have to
do is:
To login with
% ssh -X -l username host
% password
and type
% xterm
Nothing about removing -nolisten tcp in xserverrc and so on.
But when I do it, I get the error
cannot open display
I
>
> 1. Don't use "su -", try "su". Your environment variables stay
> the same. Unfortunately this can be a problem because normal
> users don't have /sbin and /usr/sbin in their PATH.
thats what I get for thinking today...of course just "su"..stupido
..thanks for reminding me ..yikes
cu
l
Martin Maciaszek <[EMAIL PROTECTED]> writes:
> 1. Don't use "su -", try "su". Your environment variables stay
> the same. Unfortunately this can be a problem because normal
> users don't have /sbin and /usr/sbin in their PATH.
Easily remedied by adding them to the path yourself. There's plenty
o
On Thu, Jun 21, 2001 at 10:34:35AM -0700, G.LeeJohnson wrote:
> Upon su -'ing from console to say use gedit it says cannot open display
> (for root)..reg user is finehow do i fix this.
>
So don't do that! Executing "su -" deletes als environment
variables (
"Hall Stevenson" wrote:
> There's a "secure" way to accomplish this, but I don't
> remember it.
Pointer to docs:
$ dpkg -S /usr/share/doc/HOWTO/en-txt/mini/Remote-X-Apps.txt.gz
doc-linux-text: /usr/share/doc/HOWTO/en-txt/mini/Remote-X-Apps.txt.gz
On Thu, Jun 21, 2001 at 03:45:38PM -0400, Hall Stevenson wrote:
> > On Thu, 21 Jun 2001, G.LeeJohnson wrote:
>
> > You can narrow it down by specifying the allowed hosts:
> > xhost + allows every host
> > xhost +foo allows computer 'foo' to connect
> > xhost - allows only the owner of the display
> On Thu, 21 Jun 2001, G.LeeJohnson wrote:
> You can narrow it down by specifying the allowed hosts:
> xhost + allows every host
> xhost +foo allows computer 'foo' to connect
> xhost - allows only the owner of the display
>
> I do not know how to specify a user. You could try
> 'xhost localhost' f
On Thu, 21 Jun 2001, G.LeeJohnson wrote:
> Hall Stevenson wrote:
>
> > > > Upon su -'ing from console to say use gedit it says
> > > > cannot open display (for root)..reg user is finehow
> > > > do i fix this.
> > > >
>
Hall Stevenson wrote:
> > > Upon su -'ing from console to say use gedit it says
> > > cannot open display (for root)..reg user is finehow
> > > do i fix this.
> > >
> > I think you need to allow other 'hosts' to connect to your
&g
> > Upon su -'ing from console to say use gedit it says
> > cannot open display (for root)..reg user is finehow
> > do i fix this.
> >
> I think you need to allow other 'hosts' to connect to your
> display. You can turn this on with: xho
Hi,
> Upon su -'ing from console to say use gedit it says cannot open display
> (for root)..reg user is finehow do i fix this.
>
I think you need to allow other 'hosts' to connect to your display. You
can turn this on with:
xhosts +
as a regular user. This will
Upon su -'ing from console to say use gedit it says cannot open display
(for root)..reg user is finehow do i fix this.
Thanks
lee
-===
d the Tree falls off...'
> -Original Message-
> From: Thomas Wegner [mailto:[EMAIL PROTECTED]
> Sent: 11 April 2001 20:03
> To: MaRCeL FiGUeRoLa EsTRaDa
> Cc: Debian User List
> Subject: RE: Err: Cannot open display
>
>
> Hi Marcel!
>
> O
figured properly. When I try to go to the X-Windows the
> following
> error message appears:
>
> Gtk-WARNING ** : cannot open display
>
> I have an AGP Graphics Card : Nvidia Geforce2 MX 32 Mby RAM.
>
> How can I configure Debian to make the graphics work properly?
When y
Hi there!
I'm new to debian and I've just installed Debian Linux 2.2 r2 "Potato".
During installation Anxious couldn't find a suitable grafic card and so it's
not yet configured properly. When I try to go to the X-Windows the following
error message appears:
Gtk-WA
On Oct 24 14:28, kmself@ix.netcom.com wrote:
> Are you specifying a display for the X client? Following works:
>
> [EMAIL PROTECTED]:karsten]$ batch
> warning: commands will be executed using /bin/sh
> at> export DISPLAY=:1
> at> xlogo &
> at>
> job 66 at 2000-10-24 14:2
am on my local X from crontab but
> > > in my
> > > mail report from the cron it says:
> > >
> > > Gtk-WARNING **: cannot open display:
> > >
> > > And the program won't come up. My display is :0 and yes, X is running.
> > >
>
On Oct 24 11:09, kmself@ix.netcom.com wrote:
> on Tue, Oct 24, 2000 at 03:39:53AM +0200, John Ericson ([EMAIL PROTECTED])
> wrote:
> > I'm trying to launch a local Gnome program on my local X from crontab but
> > in my
> > mail report from the cron it says:
> &g
on Tue, Oct 24, 2000 at 03:39:53AM +0200, John Ericson ([EMAIL PROTECTED])
wrote:
> I'm trying to launch a local Gnome program on my local X from crontab but in
> my
> mail report from the cron it says:
>
> Gtk-WARNING **: cannot open display:
>
> And the program wo
I'm trying to launch a local Gnome program on my local X from crontab but in my
mail report from the cron it says:
Gtk-WARNING **: cannot open display:
And the program won't come up. My display is :0 and yes, X is running.
Can anyone give me a hint here?
--
* John Ericson [EMAIL
WT> Quoting [EMAIL PROTECTED]([EMAIL PROTECTED]):
>>
>> As to the Viewer/Grpahics thing. Viewer to me is for pdf readers
>> and the like. I expect a graphics app to be in graphics.
>>
>>
>> Feel free to bring this up on policy.
I would appreciate, if the maintainers of graphic viewers could
Subject: Re: gqview error: ** WARNING **: cannot open display:
Date: Thu, May 27, 1999 at 12:02:36PM -0400
In reply to:[EMAIL PROTECTED]
Quoting [EMAIL PROTECTED]([EMAIL PROTECTED]):
> >
> > After answering Dan's question, I installed gqview to check it out.
&g
Subject: gqview error: ** WARNING **: cannot open display:
Date: Thu, May 27, 1999 at 01:52:52AM -0700
In reply to:Dan Smith
Quoting Dan Smith([EMAIL PROTECTED]):
> NOTICE: I am not subscribed to the list, so please
> send replies to ME, [EMAIL PROTECTED]
> Than
Subject: gqview error: ** WARNING **: cannot open display:
Date: Thu, May 27, 1999 at 01:52:52AM -0700
In reply to:Dan Smith
Quoting Dan Smith([EMAIL PROTECTED]):
> NOTICE: I am not subscribed to the list, so please
> send replies to ME, [EMAIL PROTECTED]
> Than
mands:
> gqview
> gqview
> gqview -h
> gqview --help
> All resulted in this error:
>
> ** WARNING **: cannot open display:
>
> Is there some conf file I need to configure? And if
> so, where? The docs offered no help.
gqview must be run from X by the user running X (like a
>> "DS" == Dan Smith <[EMAIL PROTECTED]> writes:
DS> All resulted in this error: ** WARNING **: cannot
DS> open display:
You try to start it as root, but you use X as another user? Only the
user opening the X display may use it by default.
Try running gqview as this user. If you want to be ab
resulted in this error:
** WARNING **: cannot open display:
Is there some conf file I need to configure? And if
so, where? The docs offered no help.
_
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
88 matches
Mail list logo
