I also see it on Ubuntu MATE Jammy.
Will the fix come from Xorg,
or should we add LightDM to the affected projects list?
--
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/1922414
Title:
ssh-agent
** No longer affects: ltsp
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xdm in Ubuntu.
https://bugs.launchpad.net/bugs/206924
Title:
Make it possible to create a guest account
To manage notifications about this bug go to:
Hi Timo,
if I remember correctly, there were some schools that were affected by this
issue, but I wasn't able to reproduce it in the office due to lack of similar
hardware.
Unfortunately it's not easy to check which were those schools; but I can keep
an eye on this issue, in case I hear about
Exactly. I did the "verification-done-bionic" step for 18.2.2 in comment
#12 above; and unfortunately I don't have an affected school nearby,
where I could test 18.2.8 in cosmic, and installing cosmic in a remote
school would be hard.
Thanks a lot Timo!
--
You received this bug notification
Just correcting a wrong comment (#2) I made:
> It happens on both 32bit and 64bit installations.
I asked the school that reported the issue on 64bit to check again, and
they said they have a 32bit installation after all.
So the problem has only been reported in 32bit installations; I don't
know
I don't know the software stacks involved:
If I understood it correctly,
mesa 18.3.3 doesn't work with older kernels while 18.0 did work,
and so I'll do a bisection to see which kernel commit fixes the issue,
and then distro kernel maintainers may cherrypick it for older kernels.
If there's no
I tried a small kernel bisection using the ubuntu kernel binaries,
4.19.2-041902=fails,
4.19.3-041903=works
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1815172
Title:
Black screen on skylake
Hello Sergii,
I tried with 4.20.7 and it appears to work fine! Thanks!
Output of the commands:
# uname -a
Linux srv-6gym-chalk 4.20.7-042007-generic #201902061234 SMP Wed Feb 6 17:49:39
UTC 2019 i686 i686 i686 GNU/Linux
# file /usr/bin/glxinfo
/usr/bin/glxinfo: ELF 32-bit LSB shared object,
I just tried with 4.18.0-14-generic, the same issue happens there as
well.
And, another school reported the issue on HD Graphics 630:
root@pc02:~# lspci -nn -k | grep -A 2 VGA 00:02.0 VGA compatible
controller [0300]: Intel Corporation HD Graphics 630 [8086:5912] (rev
04) Subsystem:
I verify that the bionic-proposed package addresses the issue.
Tested in:
# lspci -nn -k | grep -A 2 VGA
00:02.0 VGA compatible controller [0300]: Intel Corporation HD Graphics 630
[8086:5912] (rev 04)
Subsystem: Gigabyte Technology Co., Ltd HD Graphics 630 [1458:d000]
Kernel
Public bug reported:
Several schools reported black screens after normally updating their
Ubuntu boxes from 18.0.5-0ubuntu0~18.04.1 to 18.2.2-0ubuntu1~18.04.1.
Downgrading mesa fixes the problem.
lspci: 00:02.0 VGA compatible controller [0300]: Intel Corporation HD
Graphics 530 [8086:1912] (rev
Hi Gunnar,
the issue was that in some cases, typing the Greek key for accent (tonos, the
key is ";"), and then after releasing it, typing "α", resulted in two separate
characters, i.e.
;+α=´α
instead of the correct
;+α=ά
At first I thought this was because of ibus, because I was seeing the
Hi, LDM will be deprecated in LTSP 6, so I don't think anyone's going to work
on this issue.
So I'm marking it "Won't Fix".
** Changed in: ltsp
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xdm in Ubuntu.
This bug still exists in a supported release, namely 12.04.5, with the
trusty backported xorg stack.
# lspci -nn -k | grep -A 2 VGA
00:01.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc.
[AMD/ATI] Kabini [Radeon HD 8400] [1002:9830]
Subsystem: ASUSTeK Computer Inc.
I've verified that x11-utils 7.6+4ubuntu0.2 works as expected in Ubuntu
12.04.1, please push it to precise-updates.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to x11-utils
Public bug reported:
[Impact]
Xprop added support for UTF8_STRING back in 2009:
http://cgit.freedesktop.org/xorg/app/xprop/commit/?id=eb64005382abf6262c913a46e6186e019a179d59
Unfortunately `xprop -f 8u -set` has been broken until 2012:
Fix released in LTSP 5.4.5.
** Changed in: ltsp
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-nouveau in Ubuntu.
https://bugs.launchpad.net/bugs/1072711
Title:
Fix committed in http://bazaar.launchpad.net/~ltsp-upstream/ltsp/ltsp-
trunk/revision/2447.
** Changed in: ltsp
Status: In Progress = Fix Committed
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-nouveau in Ubuntu.
The committed fix is applied too late, after xorg is loaded. So it's not
working on the first login, but only on subsequent logins.
The `rm -f /usr/lib/i386-linux-gnu/dri/nouveau_vieux_dri.so` command should be
run from some init-ltsp.d script instead.
A workaround that doesn't involve updating
Added LTSP to the affected projects, because it's very common there
(nvidia drivers on the LTSP server, and e.g. intel-based clients), even
though it can't be fixed in that project.
** Also affects: ltsp (Ubuntu)
Importance: Undecided
Status: New
** Changed in: ltsp (Ubuntu)
Importance: Undecided = High
** Changed in: ltsp
Status: New = Fix Committed
** Changed in: ltsp
Assignee: (unassigned) = Alkis Georgopoulos (alkisg)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-nouveau in Ubuntu
Another teacher reports the same problem in these clients:
root@ltsp135:~# lspci -nn -k | grep -A 2 VGA
01:00.0 VGA compatible controller [0300]: NVIDIA Corporation NV18
[GeForce4 MX 4000] [10de:0185] (rev c1)
Subsystem: Micro-Star International Co., Ltd. Device [1462:9363]
Kernel driver in
Some people are reporting that this doesn't happen in a fresh 12.04.1
installation, but it happens after they `apt-get update` their server.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-nouveau in Ubuntu.
In this case, although with Precise not updated for a couple of months,
the problem did NOT happen:
# lspci -nn -k | grep -A 2 VGA
01:00.0 VGA compatible controller [0300]: NVIDIA Corporation NV11 [GeForce2
MX/MX 400] [10de:0110] (rev b2)
Kernel driver in use: nouveau
Kernel
** Also affects: xserver-xorg-video-nouveau (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-nouveau in Ubuntu.
https://bugs.launchpad.net/bugs/1072711
Title:
Attaching Xorg.log where the segfault in nouveau_vieux_dri.so can be
seen.
An easy way to reproduce the problem without LTSP:
(from a client with an nvidia card):
$ ssh -X server
$ LIBGL_ALWAYS_INDIRECT=true firefox
One workaround mentioned in #nouveau:
(08:34:05 πμ) airlied: got all the accel
** No longer affects: ltsp
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bugs.launchpad.net/bugs/541492
Title:
MASTER: [i845] GPU lockup
To manage notifications about this bug go to:
** Also affects: ltsp
Importance: Undecided
Status: New
** No longer affects: ldm (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xdm in Ubuntu.
https://bugs.launchpad.net/bugs/891793
Title:
Login with USB key or smart
** Also affects: ltsp
Importance: Undecided
Status: New
** No longer affects: ldm (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xdm in Ubuntu.
https://bugs.launchpad.net/bugs/206924
Title:
Make it possible to create a
So the best workaround so far for me is to use the
https://launchpad.net/~brian-rogers/+archive/experimental kernel which
gives me KMS, 3D and XV with no problems.
Erm, actually that's true for an older kernel that Brian Rogers had uploaded
there: 2.6.34rc3-51-generic
With the last kernel there
@Brian Rogers: I tried the last kernel from your ppa
(2.6.35rc4-v9patch1.e467e10) on another laptop with 855, and X wouldn't
start unless nomodeset was used.
Could you please reupload 2.6.34rc3-51-generic because that works for
me, but I didn't keep the .deb? Thank you!
The other methods listed
Thank you Brian for all the help.
I tried linux-image-2.6.35-ppa20+v9patch-generic and the cursor was invisible.
I tried linux-image-2.6.35-ppa20+v9+cursorfix-generic and almost everything was
working fine: KMS, 3D, XV...
glxgears even reported 308 fps instead of 260 fps that it showed with the
Googling revealed a thread that looks relevant to me:
http://www.gossamer-threads.com/lists/linux/kernel/1238374
One even mentions the 10 secs interval between each hanging.
Post #15 claims to have a solution.
--
[i855] [karmic] X freezes with intel 855GM videocard
I tested
https://wiki.ubuntu.com/X/Bugs/Lucidi8xxFreezes#GTT%20Incoherency%20Patch on my
laptop with:
00:02.0 VGA compatible controller [0300]: Intel Corporation 82852/855GM
Integrated Graphics Device [8086:3582] (rev 02)
While it allowed the system to boot, and KMS / 3D acceleration were
Thank you for the tip Willem, with that kernel I'm also able to boot with KMS
on and Xv and everything.
I only noticed a small glitch, in Xv sometimes (e.g. in totem, but not with
fullscreen nor in vlc) there's a black overlay over the video. And if I click
on a totem menu, and then I close the
I can also confirm that the ppa kernel works for me in Lucid, while
without it I can't boot my old laptop.
My card is:
00:02.0 VGA compatible controller [0300]: Intel Corporation 82852/855GM
Integrated Graphics Device [8086:3582] (rev 02)
2.6.32-20.30 = Last one that boots, crashes with Xv
I can't boot with any of the recent kernels. I have this card on my laptop:
00:02.0 VGA compatible controller [0300]: Intel Corporation 82852/855GM
Integrated Graphics Device [8086:3582] (rev 02)
I'm using the linux-image-generic kernels:
2.6.32-20.30 = Last one that boots
2.6.32-21.32 = It
Thank you, much appreciated.
--
Wrong keyboard settings when console-settings has multiple layouts
https://bugs.launchpad.net/bugs/460328
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-evdev in ubuntu.
Before Karmic, I didn't have to configure gnome at all (meaning, all the gconf
settings were working fine if they were empty).
Console-setup was configured to [us,gr], and X would pick it up and let me work
with it, and allow me to switch layouts, no matter if I used an xterm, gnome,
or kde
Just wondering, when you're experiencing the problem, what do you get if you
give this?
gconftool-2 -R /desktop/gnome/peripherals/keyboard/kbd
Because I had similar symptoms, but they were caused by gdm..
--
Keyboard indicator shows additional layout null
https://bugs.launchpad.net/bugs/283128
While X freezes I can't switch to vt1, so I'm sending two directories
with the files, one before the freeze, and one after the freeze but also
after the X reset. Both of them are while I'm on gdm.
Also, when switching to vt1 before the freeze, I'm not seeing the
expected console output, but only
*** This bug is a duplicate of bug 516412 ***
https://bugs.launchpad.net/bugs/516412
I'm not sure if my initial problem was a duplicate of #516412, but what I'm
experiencing now, after the reinstallation, surely is.
Removing plymouth solved my problem.
Thanks!
** Package changed:
I don't know if it's due to my lack of observation or due to the fact
that I've reinstalled Lucid, and I'm using i386 instead of amd64 now,
but the symptoms have changed a bit.
Now I get an X crash the first time I press the [Enter] key.
I'm getting that both with the current xserver-xorg-core
** Attachment added: messages
http://launchpadlibrarian.net/38850355/messages
--
2:1.7.3.902-1ubuntu10 crashes for me, up to -ubuntu9 it worked
https://bugs.launchpad.net/bugs/517276
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server
** Attachment added: keyboard
http://launchpadlibrarian.net/38850358/keyboard
--
2:1.7.3.902-1ubuntu10 crashes for me, up to -ubuntu9 it worked
https://bugs.launchpad.net/bugs/517276
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server
I've just seen that this also works for me:
* Booting to gdm
* Resetting X
* Logging on normally
I.e. an X reset, even without pressing the [Enter] key so that it hangs
first, also allows me to work without problems.
--
2:1.7.3.902-1ubuntu10 crashes for me, up to -ubuntu9 it worked
Yes, that Xorg.0.log was just after the X reset while on gdm and before logging
in.
I'm attaching Xorg.0.log.old. I'm still on the same session, I haven't rebooted
since.
Thank you for the ACPI-errors notice. :-)
** Attachment added: Xorg.0.log.old
Public bug reported:
Using Lucid amd64, after today's updates my PC crashes after 1-2 minutes of
usage.
Downgrading xserver-xorg-core and xserver-common to 2:1.7.3.902-1ubuntu9 worked
fine for me.
I also tried with the daily-live 20100203 and I got the same problem.
I tried with the nvidia, nv,
For the LTSP client mirrored screen, see this bug, it's because of the
proprietary drivers on the server:
https://bugs.launchpad.net/ubuntu/+source/ltsp/+bug/441586
--
system GUI turn upside down when visual effects changed from none to normal
https://bugs.launchpad.net/bugs/267269
You received
Verifying this for Lucid Alpha 1.
Please make gdm use a [Default] layout by default, one which simply
doesn't write anything to
/desktop/gnome/peripherals/keyboard/kbd/layouts, as opposed to
using/forcing the [us] layout.
--
Wrong keyboard settings when console-settings has multiple layouts
*** 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
51 matches
Mail list logo
