Public bug reported:
I have a setup with two video cards, each running a separate X screen
(DISPLAY=:0.0 and :0.1), using fglrx driver.
For the most part this is working fine, except that I cannot run
Xfce4-terminal on both X screens at once. Several instances can run on
each screen, but as soon as I start one on one screen, all instances on
the other screen terminate with an X error. No other program seems to
exhibit this behavour. It happens whether transparent background is
enabled or not. lxterminal is able to display a transparent background
on both screens simultaneously.
Example session in lxterminal:
$ echo $DISPLAY
:0.0
$ DISPLAY=:0.0 xfce4-terminal &
[1] 5078
# at this point, an xfce4-terminal window is open next to the lxterminal
# window on display :0.0
# it outputs the following message to stderr:
(xfce4-terminal:5078): GLib-WARNING **:
(/build/buildd/glib2.0-2.38.0/./glib/gerror.c:390):g_error_new_valist: runtime
check failed: (domain != 0)
Failed to connect to session manager: Failed to connect to the session manager:
SESSION_MANAGER environment variable not defined
# now I try to start another xfce4-terminal on display :0.1
$ DISPLAY=:0.1 xfce4-terminal &
[2] 5133
$ The program 'xfce4-terminal' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadMatch (invalid parameter attributes)'.
(Details: serial 480 error_code 8 request_code 1 minor_code 0)
(Note to programmers: normally, X errors are reported asynchronously;
that is, you will receive the error a while after causing it.
To debug your program, run it with the --sync command line
option to change this behavior. You can then get a meaningful
backtrace from your debugger if you break on the gdk_x_error() function.)
(xfce4-terminal:5133): GLib-WARNING **:
(/build/buildd/glib2.0-2.38.0/./glib/gerror.c:390):g_error_new_valist: runtime
check failed: (domain != 0)
Failed to connect to session manager: Failed to connect to the session manager:
SESSION_MANAGER environment variable not defined
[1]- Exit 1 DISPLAY=:0.0 xfce4-terminal
# now an Xfce4-terminal window is shown on display :0.1, but the window
I previously opened on :0.0 is gone, as indicated by the X error
message.
The same issue happens if I use `xfce4-terminal --display=:0.0` instead
of setting the DISPLAY variable. Adding --geometry to ensure the window
actually opens within the boundaries of the display doesn't help either.
(Anyway, it was always opening within the display boundaries even
without that option, but just a hunch that might have helped.)
syslog, kern.log and Xorg.0.log don't show anything interesting when
this happens.
I suspect a driver bug that Xfce4-terminal is triggering somehow, but I
don't know how to investigate. (Unfortunately I couldn't get the open-
source drivers to work with this setup at all.)
ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: xfce4-terminal 0.6.2-3ubuntu1
ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
Uname: Linux 3.11.0-12-generic x86_64
NonfreeKernelModules: fglrx
ApportVersion: 2.12.5-0ubuntu2
Architecture: amd64
Date: Tue Oct 22 14:30:16 2013
InstallationDate: Installed on 2013-10-22 (0 days ago)
InstallationMedia: Lubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
MarkForUpload: True
SourcePackage: xfce4-terminal
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: xfce4-terminal (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug saucy
** Description changed:
I have a setup with two video cards, each running a separate X screen
(DISPLAY=:0.0 and :0.1), using fglrx driver.
For the most part this is working fine, except that I cannot run
Xfce4-terminal on both X screens at once. Several instances can run on
each screen, but as soon as I start one on one screen, all instances on
the other screen terminate with an X error. No other program seems to
exhibit this behavour. It happens whether transparent background is
enabled or not. lxterminal is able to display a transparent background
on both screens simultaneously.
Example session in lxterminal:
$ echo $DISPLAY
:0.0
$ DISPLAY=:0.0 xfce4-terminal &
[1] 5078
- # at this point, an xfce4-terminal window is open next to the lxterminal
window on display :0.0
+ # at this point, an xfce4-terminal window is open next to the lxterminal
+ # window on display :0.0
# it outputs the following message to stderr:
(xfce4-terminal:5078): GLib-WARNING **:
(/build/buildd/glib2.0-2.38.0/./glib/gerror.c:390):g_error_new_valist: runtime
check failed: (domain != 0)
Failed to connect to session manager: Failed to connect to the session
manager: SESSION_MANAGER environment variable not defined
# now I try to start another xfce4-terminal on display :0.1
$ DISPLAY=:0.1 xfce4-terminal &
[2] 5133
$ The program 'xfce4-terminal' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadMatch (invalid parameter attributes)'.
- (Details: serial 480 error_code 8 request_code 1 minor_code 0)
- (Note to programmers: normally, X errors are reported asynchronously;
- that is, you will receive the error a while after causing it.
- To debug your program, run it with the --sync command line
- option to change this behavior. You can then get a meaningful
- backtrace from your debugger if you break on the gdk_x_error() function.)
+ (Details: serial 480 error_code 8 request_code 1 minor_code 0)
+ (Note to programmers: normally, X errors are reported asynchronously;
+ that is, you will receive the error a while after causing it.
+ To debug your program, run it with the --sync command line
+ option to change this behavior. You can then get a meaningful
+ backtrace from your debugger if you break on the gdk_x_error() function.)
(xfce4-terminal:5133): GLib-WARNING **:
(/build/buildd/glib2.0-2.38.0/./glib/gerror.c:390):g_error_new_valist: runtime
check failed: (domain != 0)
Failed to connect to session manager: Failed to connect to the session
manager: SESSION_MANAGER environment variable not defined
[1]- Exit 1 DISPLAY=:0.0 xfce4-terminal
# now an Xfce4-terminal window is shown on display :0.1, but the window
I previously opened on :0.0 is gone, as indicated by the X error
message.
The same issue happens if I use `xfce4-terminal --display=:0.0` instead
of setting the DISPLAY variable. Adding --geometry to ensure the window
actually opens within the boundaries of the display doesn't help either.
(Anyway, it was always opening within the display boundaries even
without that option, but just a hunch that might have helped.)
syslog, kern.log and Xorg.0.log don't show anything interesting when
this happens.
I suspect a driver bug that Xfce4-terminal is triggering somehow, but I
don't know how to investigate. (Unfortunately I couldn't get the open-
source drivers to work with this setup at all.)
ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: xfce4-terminal 0.6.2-3ubuntu1
ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
Uname: Linux 3.11.0-12-generic x86_64
NonfreeKernelModules: fglrx
ApportVersion: 2.12.5-0ubuntu2
Architecture: amd64
Date: Tue Oct 22 14:30:16 2013
InstallationDate: Installed on 2013-10-22 (0 days ago)
InstallationMedia: Lubuntu 13.10 "Saucy Salamander" - Release amd64
(20131016.1)
MarkForUpload: True
SourcePackage: xfce4-terminal
UpgradeStatus: No upgrade log present (probably fresh install)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1243354
Title:
Xfce4-terminal cannot run on more than one X screen at a time
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xfce4-terminal/+bug/1243354/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
