Problems with x.org after update.

Do you still have this problem? The nVidia problem should be fixed, not sure about the layout problem though.

More information about keyboard layout problem: Bug #149759 and Bug #149829

The reporter of Bug #149787 suggests that there is something wrong with the restricted drivers in the Norwegian repository.

How can it be that there is an update which breaks xorg-settings of all users?

My nVidia dirver is still disabled and not installed which it was before!

My Xfce4-Terminal has some weird transparenz that I cannot even see any output.

This is why this system is not for the masses: you need to know where to fix thins and not "Just Works"! Didn't we have the same problem 1 year ago with Draper to Edgy?

P.S.: While complaining I know that this Gutsy is still Beta... But take care for the real Gutsy release. I wish the developers very possible success of this world to get a polished release!

The update didn't really screw anything up - it just left out the restricted modules (which are needed if you are using accelerated graphics). The modules were released about a day later, so it was just a matter of choosing your updates wisely.

Well, at least it's true that it was quickly fixed. It did cause other problems too, however, but that is to be expected with pre-release software.

> The update didn't really screw anything up - it just left out the restricted modules (which are needed if you are using accelerated graphics).
No screw up. But for one day it wasn't possible to have my local keyboard settings nor to get a correct display.

> The modules were released about a day later, so it was just a matter of choosing your updates wisely.
I think when the update-notifier pops up in the notification area one just can install the updates. Or do I have to check somewhere whether I still need to waint some days to update in order to keep the system consistent?

Yes, it's Beta. But for getting to mass market ready one has to consider these things.

Thanks for your efforts.

Beta versions and pre-releases aren't meant for the masses though. This must not happen after release. Perhaps there should be two update release cycles; one early for advanced and experienced users, and one for "normal" users. That way, such update bugs could be trapped before it does any harm.

I see two different solutions to help in these situations:

1- A community-based feedback. For example, after updating your system, you could push a button indicating whether or not this update was harmless (or solved a bug you had or crashed your system or whatever). For each update there would be a color or a value indicating how "safe" is the update.

2- More obvious changelog or warnings (maybe with a dialog warning the user or a color code, but set by developers, not the user community?). For "normal" user (like me), it is clearly not obvious why I should not select a particular update and every update looks similar to me: just a name in the update list.

I would tend to go with the second solution, because the first one seems overkill: most updates should be harmless at the beta and after release stages.

Just my two cents...

I disagree. The updates that are made available to the users should be safe. You can't assume that it isn't. However, if the main update was delayed only a few hours, then alot of users would be able to update and report any bugs.

A big problem with the Gutsy repos has been that sometimes (read often) the local mirrors (like the swedish one) are "off sync". Sometimes for days it seems. Chaning to the main repo solved this issue for me.

Do you still have these problems in Gutsy Final?

No problems, x-org is ok.

ons, 24.10.2007 kl. 22.37 +0000, skrev Nanley Chery:
> Do you still have these problems in Gutsy Final?
>
> ** Changed in: xorg (Ubuntu)
> Sourcepackagename: None => xorg
>

No, I don't have this problem anymore after installing the restricted drivers.

Please don't mark it just as solved.
Ubuntu should learn from the issue above that the release process needs to be improved.

Also, bulled-proof X should be improved: when there is no restriced modules available but set in the settings because it was available before then do something to let the user with a working system and same keyboard settings etc.

1 more problem here is that the user has to edit xorg manually to add/change the keyboard layout.

No, everything is in sync now

@Tim
This was an update problem that happened during gutsy beta/alpha testing, I'm pretty sure this problem won't be repeated in an official release where all updates are tested before devs release it to the public.