Telegram-desktop via x2go won't start
up vote
0
down vote
favorite
Telegram-desktop via x2go won't start.
Host machine:
$ uname -r
4.17.14-arch1-1-ARCH
$ pacman -Qs openssh
local/openssh 7.7p1-2
$ pacman -Qs x2goserver
local/x2goserver 4.1.0.2-1
$ pacman -Qs telegram-desktop
local/telegram-desktop 1.3.10-2
Client machine:
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 18.04.1 LTS
Release: 18.04
Codename: bionic
$ x2goclient --version
x2go-INFO-1> "Starting X2Go Client 4.1.1.1..."
Telegram-desktop works just fine on the host (arch linux). However it won't start through x2goclient with session type XFCE.
$ telegram-desktop
QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-russ'
QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-russ'
QApplication: invalid style override passed, ignoring it.
Gdk-Message: 10:56:30.756: telegram-desktop: Fatal IO error 2 (No such file or directory) on X server :132.0.
I tried different ways to start it.
$ XDG_RUNTIME_DIR=/run/user/1000/ telegram-desktop
QApplication: invalid style override passed, ignoring it.
Gdk-Message: 10:58:01.143: telegram-desktop: Fatal IO error 2 (No such file or directory) on X server :132.0.
$ XDG_RUNTIME_DIR=/run/user/1000/ telegram-desktop -style Fusion
Gdk-Message: 10:58:37.227: telegram-desktop: Fatal IO error 2 (No such file or directory) on X server :132.0.
Also tried to change the icon theme on the host machine, but no luck. Other apps works ok through x2go. Would be grateful for any help.
x2go
add a comment |
up vote
0
down vote
favorite
Telegram-desktop via x2go won't start.
Host machine:
$ uname -r
4.17.14-arch1-1-ARCH
$ pacman -Qs openssh
local/openssh 7.7p1-2
$ pacman -Qs x2goserver
local/x2goserver 4.1.0.2-1
$ pacman -Qs telegram-desktop
local/telegram-desktop 1.3.10-2
Client machine:
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 18.04.1 LTS
Release: 18.04
Codename: bionic
$ x2goclient --version
x2go-INFO-1> "Starting X2Go Client 4.1.1.1..."
Telegram-desktop works just fine on the host (arch linux). However it won't start through x2goclient with session type XFCE.
$ telegram-desktop
QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-russ'
QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-russ'
QApplication: invalid style override passed, ignoring it.
Gdk-Message: 10:56:30.756: telegram-desktop: Fatal IO error 2 (No such file or directory) on X server :132.0.
I tried different ways to start it.
$ XDG_RUNTIME_DIR=/run/user/1000/ telegram-desktop
QApplication: invalid style override passed, ignoring it.
Gdk-Message: 10:58:01.143: telegram-desktop: Fatal IO error 2 (No such file or directory) on X server :132.0.
$ XDG_RUNTIME_DIR=/run/user/1000/ telegram-desktop -style Fusion
Gdk-Message: 10:58:37.227: telegram-desktop: Fatal IO error 2 (No such file or directory) on X server :132.0.
Also tried to change the icon theme on the host machine, but no luck. Other apps works ok through x2go. Would be grateful for any help.
x2go
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
Telegram-desktop via x2go won't start.
Host machine:
$ uname -r
4.17.14-arch1-1-ARCH
$ pacman -Qs openssh
local/openssh 7.7p1-2
$ pacman -Qs x2goserver
local/x2goserver 4.1.0.2-1
$ pacman -Qs telegram-desktop
local/telegram-desktop 1.3.10-2
Client machine:
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 18.04.1 LTS
Release: 18.04
Codename: bionic
$ x2goclient --version
x2go-INFO-1> "Starting X2Go Client 4.1.1.1..."
Telegram-desktop works just fine on the host (arch linux). However it won't start through x2goclient with session type XFCE.
$ telegram-desktop
QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-russ'
QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-russ'
QApplication: invalid style override passed, ignoring it.
Gdk-Message: 10:56:30.756: telegram-desktop: Fatal IO error 2 (No such file or directory) on X server :132.0.
I tried different ways to start it.
$ XDG_RUNTIME_DIR=/run/user/1000/ telegram-desktop
QApplication: invalid style override passed, ignoring it.
Gdk-Message: 10:58:01.143: telegram-desktop: Fatal IO error 2 (No such file or directory) on X server :132.0.
$ XDG_RUNTIME_DIR=/run/user/1000/ telegram-desktop -style Fusion
Gdk-Message: 10:58:37.227: telegram-desktop: Fatal IO error 2 (No such file or directory) on X server :132.0.
Also tried to change the icon theme on the host machine, but no luck. Other apps works ok through x2go. Would be grateful for any help.
x2go
Telegram-desktop via x2go won't start.
Host machine:
$ uname -r
4.17.14-arch1-1-ARCH
$ pacman -Qs openssh
local/openssh 7.7p1-2
$ pacman -Qs x2goserver
local/x2goserver 4.1.0.2-1
$ pacman -Qs telegram-desktop
local/telegram-desktop 1.3.10-2
Client machine:
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 18.04.1 LTS
Release: 18.04
Codename: bionic
$ x2goclient --version
x2go-INFO-1> "Starting X2Go Client 4.1.1.1..."
Telegram-desktop works just fine on the host (arch linux). However it won't start through x2goclient with session type XFCE.
$ telegram-desktop
QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-russ'
QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-russ'
QApplication: invalid style override passed, ignoring it.
Gdk-Message: 10:56:30.756: telegram-desktop: Fatal IO error 2 (No such file or directory) on X server :132.0.
I tried different ways to start it.
$ XDG_RUNTIME_DIR=/run/user/1000/ telegram-desktop
QApplication: invalid style override passed, ignoring it.
Gdk-Message: 10:58:01.143: telegram-desktop: Fatal IO error 2 (No such file or directory) on X server :132.0.
$ XDG_RUNTIME_DIR=/run/user/1000/ telegram-desktop -style Fusion
Gdk-Message: 10:58:37.227: telegram-desktop: Fatal IO error 2 (No such file or directory) on X server :132.0.
Also tried to change the icon theme on the host machine, but no luck. Other apps works ok through x2go. Would be grateful for any help.
x2go
x2go
edited Aug 12 at 8:23
Thomas
3,67161225
3,67161225
asked Aug 12 at 8:08
Russel FP
11
11
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
up vote
0
down vote
this worked for me:
X2GO_NXAGENT_DEFAULT_OPTIONS+=" -extension BIG-REQUESTS"
comment out this line in /etc/x2go/nx_agent.options
There's a warning w/r to crashing when the option is enabled, so I'll have to keep an eye on that; Telegram works again nicely via x2go now, though.
All the best, uwe
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
this worked for me:
X2GO_NXAGENT_DEFAULT_OPTIONS+=" -extension BIG-REQUESTS"
comment out this line in /etc/x2go/nx_agent.options
There's a warning w/r to crashing when the option is enabled, so I'll have to keep an eye on that; Telegram works again nicely via x2go now, though.
All the best, uwe
add a comment |
up vote
0
down vote
this worked for me:
X2GO_NXAGENT_DEFAULT_OPTIONS+=" -extension BIG-REQUESTS"
comment out this line in /etc/x2go/nx_agent.options
There's a warning w/r to crashing when the option is enabled, so I'll have to keep an eye on that; Telegram works again nicely via x2go now, though.
All the best, uwe
add a comment |
up vote
0
down vote
up vote
0
down vote
this worked for me:
X2GO_NXAGENT_DEFAULT_OPTIONS+=" -extension BIG-REQUESTS"
comment out this line in /etc/x2go/nx_agent.options
There's a warning w/r to crashing when the option is enabled, so I'll have to keep an eye on that; Telegram works again nicely via x2go now, though.
All the best, uwe
this worked for me:
X2GO_NXAGENT_DEFAULT_OPTIONS+=" -extension BIG-REQUESTS"
comment out this line in /etc/x2go/nx_agent.options
There's a warning w/r to crashing when the option is enabled, so I'll have to keep an eye on that; Telegram works again nicely via x2go now, though.
All the best, uwe
answered Nov 28 at 13:10
hoover
1
1
add a comment |
add a comment |
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f462094%2ftelegram-desktop-via-x2go-wont-start%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown