Bug after todays update?

[Fintan]

After updating I rebooted just to get a black screen. Booting in recovery gives me this:

Caught signal 11 (Segmentation fault). Server aborting

Please consult the The X.Org Foundation support
at http://wiki.x.org
for help.
Please also check the log file at "/var/log/Xorg.0.log" for additional information.

ddxSigGiveUp: Closing log

I found this:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=564256

Which suggests this:

Moving config_init() after InitInput() in dix/main.c:main() should fix
that.

can't find dix/main.c:main though. Never heard of it.

Anyone else see this?

[Jonas]

Re: Bug after todays update?

Same here :S got another xorg update but that didn't fix it either. no time atm to look in to it further.

[GreyGeek]

Re: Bug after todays update?

config_init() and InitInput() are two functions that are in the main() function in main.c. All c and c++ programs must have a main.c source file and in that file must be a main() function. This is the "jump off" point for all c or c++ applications.

The video driver source code is NOT on your system, even though the back-trace referees to them. Until the bug is patched upstream and the repaired driver appears in the repository your best action is to revert to your previous video driver.

[Fintan]

Re: Bug after todays update?

Thankx greek that makes sense, sort of

I am using the default driver so I guess I can just hope for a update at some point.

[claydoh]

Re: Bug after todays update?

from the kubuntu-devel list today:

Currently mesa in Lucid is broken and so no packages that build-depend on it
can be built. As a result, Lucid is currently a mix of 4.3.85 (Beta 2) and
4.3.90 (RC 1) packages. Getting mesa fixed will not be just a matter of a few
minutes (hopefully today).

My recommendation is don't update any Lucid systems now. It's unlikely we
will see 4.4 RC1 fully built until at least Sunday and possibly Monday even on
the fast architectures.

[Fintan]

Re: Bug after todays update?

Thank you clay.

That does it.
Patience is still a good virtue

[timek718]

Re: Bug after todays update?

So for those of us who found out the hard way, is it possible to go back to the previous version of Mesa, and if so, how?

tim

[claydoh]

Re: Bug after todays update?

its not just mesa, it is also packages that depend or are built against it, so even if you reverted mesa, you still have a system with packages from 2 different versions of kde.

so either wait, or reinstall from an older daily build iso

caveat emptor, this is par for the course

[caryb]

Re: Bug after todays update?

I guess I don't reboot till there are remedial updates/fixes are applied

Cary

[3vi1]

Re: Bug after todays update?

...All c and c++ programs must have a main.c source file and in that file must be a main() function.

Just to clarify the overgeneralization: The main() function can be in any source file, independent of name, and C/C++ programs don't necessarily have to have a main() function (ex. WinMain is used for Windows C/C++ programs).

[GreyGeek]

Re: Bug after todays update?

...All c and c++ programs must have a main.c source file and in that file must be a main() function.

Just to clarify the overgeneralization: The main() function can be in any source file, independent of name, and C/C++ programs don't necessarily have to have a main() function (ex. WinMain is used for Windows C/C++ programs).

Psst, psst: *whispering softly* - True, but my example is for C++ 101.

[Kubuntiac]

How to know when it's safe to update?

So what would be the fastest way of knowing when it's safe to update again? My concern isn't how long it will take for them to fix it - I know they're going as fast as they can - but that I can get my systems working as fast as possible once the fix is released.

Is there a bug on Launchpad to watch? A specific package in the repo's or the lucid-devel mailing list?

[Rog131]

Re: Bug after todays update?

How to know when it's safe to update?

Short : After the April 29, 2010.

Before that:

...NOT encouraged for anyone needing a stable system or for anyone who is not comfortable running into occasional, even frequent, breakage...

What to look:
> kubuntu-devel -- Kubuntu Developer Discussion
> Kubuntu.org

Now:

...the packages are only half-built...

Status information can be found:
> Lucid-changes -- Lucid Lynx archive upload notification list
>> The Lucid-changes Archives

One of the Lucid (KDE) packages > kdeplasma-addons” 4:4.3.90-0ubuntu1 is telling:

Builds

* lucid sparc Failed to build
* lucid powerpc Failed to build
* lucid ia64 Failed to build
* lucid i386 Dependency wait
* lucid armel Dependency wait
* lucid amd64 Failed to build

=> when it (4:4.3.90-0ubuntu2 or later) changes to the "Successfully built"

[Fintan]

Re: Bug after todays update?

After last nights (my time) small upgrade my lucid is being more or less lucid again and booting normally (except for the two logins).

Of course rog is right:

...NOT encouraged for anyone needing a stable system or for anyone who is not comfortable running into occasional, even frequent, breakage...

This is Alpha after all.

[Jonas]

Re: Bug after todays update?

After last nights (my time) small upgrade my lucid is being more or less lucid again and booting normally (except for the two logins).

Of course rog is right:

...NOT encouraged for anyone needing a stable system or for anyone who is not comfortable running into occasional, even frequent, breakage...

This is Alpha after all.

I can confirm this but got back the issue described by Verndog in another post with the HAL problem and startx. Amarok-common is broke for me, and there are some kernel updates that are kept back. I would assume that it could be abit more stable with the Alpha2 planned at jan. 16th(?)