** Package changed: xorg (Ubuntu) = xserver-xorg-video-openchrome
(Ubuntu)
--
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
Bugs, which is subscribed to
Attach your /var/log/Xorg.0.log file.
If you can from after reproducing this issue.
--
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
Bugs, which is
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
Bugs, which is subscribed to Ubuntu.
--
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
** Changed in: xorg (Ubuntu)
Status: Incomplete = Confirmed
--
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
Bugs, which is subscribed to Ubuntu.
--
(To correct myself, this is using the unichrome 3D driver)
There should be no DRI2 support on these drivers/cards, so I guess a
DRI2 request should fail, unless it is a is-there-DRI2 probe request.
Anyway, glxinfo -i should not fail like that.
Just to make sure this is still an issue in latest
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
In the LTSP chroot. The graphics driver (the X server) is running
entirely on the LTSP client. Only the X clients (applications and window
manager) are running on the LTSP server, and send drawing requests to
the X server (and receive keyboard/mouse events).
--
Since upgrade from jaunty to
Please attach your Xorg.0.log and dmesg output, so we can verify if this
is a duplicate or not.
** This bug is no longer a duplicate of bug 463369
[RN50] glxinfo breaks with XAA (needs EXA)
** Changed in: xserver-xorg-video-ati (Ubuntu)
Status: New = Incomplete
--
Since upgrade from
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.
I am not so familiar with the LTSP setup, but can you log in as a local
user on a text console? Then you can use scp to copy the files to
another computer. Note that the X server does not use rsyslog anyway.
--
Since upgrade from jaunty to karmic, one of two thin clients' login broken.
https://help.ubuntu.com/community/UbuntuLTSP/ClientTroubleshooting
--
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
Bugs, which is subscribed to Ubuntu.
--
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
If you can attach the Xorg.0.log and dmesg output from booting the
Karmic live CD usb stick, it would help also. And try to run glxinfo on
it.
--
Since upgrade from jaunty to karmic, one of two thin clients' login broken.
https://bugs.launchpad.net/bugs/482875
You received this bug notification
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.
Thanks. For the future, please attach the logs instead of pasting them
into the comments.
You are using the -openchrome driver (with the via 3D driver) so it
is certainly not a radeon issue here.
I noticed this in the LTSP X log, but I do not know if it causes any
harm:
[config/dbus] couldn't
Instead of the live CD, you can of course use the xterm which you
mention in comment 15.
--
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
Bugs, which is
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
It appears this is a duplicate of bug: 463369, see:
https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/463369;
Sorry for the unnecessary report/post.
Jon
--
Since upgrade from jaunty to karmic, one of two thin clients' login broken.
https://bugs.launchpad.net/bugs/482875
You received this
*** This bug is a duplicate of bug 463369 ***
https://bugs.launchpad.net/bugs/463369
** This bug has been marked a duplicate of bug 463369
[RN50] glxinfo breaks with XAA (needs EXA)
** Package changed: ltsp (Ubuntu) = xserver-xorg-video-ati (Ubuntu)
--
Since upgrade from jaunty to
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/35702794/Dependencies.txt
** Attachment added: XsessionErrors.txt
http://launchpadlibrarian.net/35702795/XsessionErrors.txt
--
Since upgrade from jaunty to karmic, one of two thin clients' login broken.
28 matches
Mail list logo
