Update -- possibly resolved by upgrading to kubuntu 22.10.
I installed that and so far ... fingers crossed, no more black screens.
Jon
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1715749
I have the same issue with a fresh install of kubuntu 22.04 LTS on an HP
820 G1. Random screen blackout -- machine can only be revived by a
reboot. The Windows operating system that was replaced by kubuntu worked
flawlessly (except that it was Windows, which is one hell of a flaw).
--
You
OK.. wee problem related to my ignorance in configuring xorg.conf from
scratch: at least under LTSP, xorg.conf is generated on the fly when
the thin client boots up. I have created a custom xorg.conf for the
various parameters outlined in this thread, but this does not include a
ServerLayout
Bartosz,
That works as well.. I have removed the section from xorg.conf, that
disabled DRI, and instead switched off AIGLX and disabled the
compositing extension, as proposed.
Jon
--
[CLE266]Since upgrade from jaunty to karmic, one of two thin clients' login
broken.
I created an xorg.conf file (there is no xorg.conf by default) in
/opt/ltsp/i386/etc/X11/, as suggested above, disabling DRI . This
represents a workaround to the problem, I now managed to log into the
karmic ltsp server and I am accessing launchpad.net from within. The
only disadvantage to
Bartosz, I have already (unfortunately pasted into the comments, instead
of attached), please see thread above. It is Xorg.7.log because it
originates from the ltsp client. I will attach it properly for
reference. Jon
** Attachment added: Xorg.7.log -- from ltsp client, post-login
I'm not sure this is an issue with the openchrome driver. I copied the
openchrome driver from jaunty ltsp to the karmic ltsp, well expecting it
wouldn't work at all, because it was compiled for a different kernel.
But the system boots up and shows the same fault symptoms as with the
current and
.. then again, the terminal that _does_ work, uses the vesa driver!
--
Since upgrade from jaunty to karmic, one of two thin clients' login broken.
https://bugs.launchpad.net/bugs/482875
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in
I have now installed the upstream openchrome driver in the chroot and
updated the image. There is no change in the bahaviour of the affected
thin client.
Jon
--
Since upgrade from jaunty to karmic, one of two thin clients' login broken.
https://bugs.launchpad.net/bugs/482875
You received this
Tormod, do I need to install this updated driver in the ltsp chroot
(client), on the server (host), or both?
Although, I guess it shouldn't do any harm installing them in both, as
the server doesn't have any openchrome hardware.
Jon
--
Since upgrade from jaunty to karmic, one of two thin
Are we sure this is an ATI/radeon issue? The thin client that is
affected for me is a via based mini-itx with integrated on-board
graphics. Problems arise regardless of what I specify as X_SERVER
(nothing, vesa, via or openchrome) in the lts.conf. Also, if I boot
karmic directly on the
OK, sorry, but I may need some help in obtaining the requested logs: on
jaunty I had the thin clients set up to send their logs to the server in
specified client subdirectories, using syslog-ng. Karmic uses rsyslog by
default, and I haven't yet figured out how to open this up for external
logging.
Thanks, I will set something up and obtain the logs. It may take some time,
because I only have intermittent access (I can only boot into the karmic
system when this does not disturb regular operation. I re-instated jaunty on
another partition to maintain regular operation).
Jon
2009/11/17
glxinfo on client hardware when booting from live-CD-usb:
name of display: :0.0
display: :0 screen: 0
direct rendering: Yes
server glx vendor string: SGI
server glx version string: 1.2
server glx extensions:
GLX_ARB_multisample, GLX_EXT_import_context, GLX_EXT_texture_from_pixmap,
dmesg on client hardware when booting from live-CD-usb:
[0.00] Initializing cgroup subsys cpuset
[0.00] Initializing cgroup subsys cpu
[0.00] Linux version 2.6.31-14-generic (bui...@rothera) (gcc version
4.4.1 (Ubuntu 4.4.1-4ubuntu8) ) #48-Ubuntu SMP Fri Oct 16 14:04:26
dmesg from client after ltsp netboot:
[0.00] Initializing cgroup subsys cpuset
[0.00] Initializing cgroup subsys cpu
[0.00] Linux version 2.6.31-14-generic (bui...@rothera) (gcc version
4.4.1 (Ubuntu 4.4.1-4ubuntu8) ) #48-Ubuntu SMP Fri Oct 16 14:04:26 UTC 2009
(Ubuntu
By-the-way: specifying XSERVER as vesa leaves all screens black.
Interestingly, using the specification of XSERVER = openchrome, I had a
very brief glimpse of the user desktop from the server, before I was
thrown back to the login screen. While I cannot sucessfully log into
gnome desktop from
various .xsession-errors from _host_ after attempted logins on ltsp
terminal:
example 1:
/etc/gdm/Xsession: Beginning session setup...
Setting IM through im-switch for locale=en_GB.
Start IM through /etc/X11/xinit/xinput.d/all_ALL linked to
/etc/X11/xinit/xinput.d/default.
glxinfo and glxinfo -i don't work in the xterm ltsp login session. I get
an error:
name of display 192.168.0.110:7.0
X Error of failed request: BadRequest (invalid request code or no such
operation)
Major Opcode of failed request: 138 (DRI2)
Minor Opcode of failed request: 1 (DRI2Connect)
Serial
PS: I get the X Error BadRequest also in an xterm under jaunty, so that
seems to be a sane response:
j...@sun:~$ glxinfo -i
name of display: 192.168.0.110:7.0
X Error of failed request: BadRequest (invalid request code or no such
operation)
Major opcode of failed request: 138 (DRI2)
Minor
20 matches
Mail list logo
