Opened 15 years ago
Closed 15 years ago
#532 closed defect (worksforme)
VMware client Xorg unable to log in
Reported by: | wildintellect | Owned by: | |
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | OSGeoLive | Keywords: | desktop 3.0 VMWare |
Cc: |
Description
On VMWare Server 2.x It does appear that using any kernel newer than the base kernel (might be related xorg package) on Xubuntu 9.10 causes an odd glitch where the login page comes up but X restarts after login and tosses you back out to the login page.
Sometimes going into xterm session and running
sudo dpkg-reconfigure xserver-xorg
then exiting to restart X resolves the issue for a single login. Reading online hardcoding resolutions might also solve the issue with an xorg.conf file.(Note Xubuntu by default no longer has a xorg.conf file so you have to create it.)
This issue does not effect VirtualBox, might effect VMware player and is unlikely to effect the live DVD/USB.
Should we temporarily disable the sudo apt-get dist-upgrade to exlude kernel updates? I also think we should modify the ubuntu config to only notify users about updates every 3-7 days. So that a normal person using it in a workshop will never see the update prompt.
Change History (3)
follow-up: 2 comment:1 by , 15 years ago
comment:2 by , 15 years ago
Replying to hamish:
Replying to wildintellect:
Should we temporarily disable the sudo apt-get dist-upgrade to exlude kernel updates?
"dist-upgrade" should never be there in the first place.
see the email list about this one...
To be hard nosed about it, if VMware can't handle a security fix in the kernel they should release an update.
It actually seems to be a play between the 2, VMware is now letting VMs resize without the need for VMware tools to be installed. Because of this xorg seems to fail at guessing what size it can be, but the stock Xubuntu 9.10 works fine. The error only creeps in after and upgrade.
Ubuntu should not change the main kernel version in a security update, just the bit after the first "-". fwiw (I don't know if this is true for ubuntu) debian bumps the package name if the ABI will be broken by the security update:
kernel-image-2.4.27-2-686 kernel-image-2.4.27-3-686
That's just it we aren't limiting it to security updates it going: 2.6.31 2.6.36
I also think we should modify the ubuntu config to only notify users about updates every 3-7 days. So that a normal person using it in a workshop will never see the update prompt.
updates are useless for live-DVD users, mostly useless for live-USB stick users (they fill up the modifications space very quickly), but very important for folks who have installed from the DVD/USB.
So do we disable the APT preference for reminders, seems like that might mess with VM users?
comment:3 by , 15 years ago
Resolution: | → worksforme |
---|---|
Status: | new → closed |
Seems to be working again as of 3.0 rc4, no idea why.
Replying to wildintellect:
"dist-upgrade" should never be there in the first place.
To be hard nosed about it, if VMware can't handle a security fix in the kernel they should release an update.
Ubuntu should not change the main kernel version in a security update, just the bit after the first "-". fwiw (I don't know if this is true for ubuntu) debian bumps the package name if the ABI will be broken by the security update:
kernel-image-2.4.27-2-686 kernel-image-2.4.27-3-686
updates are useless for live-DVD users, mostly useless for live-USB stick users (they fill up the modifications space very quickly), but very important for folks who have installed from the DVD/USB.
I don't think it matters what you put it for live-DVD users if the clock will be reset every time they boot -- does the clock restart when you first boot? In that case they won't see a message unless they leave the computer booted from the DVD for a week. Or does it run like a Sunday cron job? shrug. The VM could easily be left open for a week though.
shrug, Hamish