Kubuntu 9.10, when booting after the logo disappears there is only black screen

[ppietryga]

After applying upgrades on Wednesday (11.11) my system doesn't start up.
Well to be honest the system starts but everything I get is blinking cursor. After switching the VTs i can see what is displayed on one of them, but what is the most strange is that I can only see the screen on vt7, to describe it better I see what is displayed on on a VT I selected before selecting VT7.
For example: I switch to vt1 (Alt+F1) and see black screen with blinking cursor, then I switch to vt7 (Alt+F7) and I can see what was on the vt1.

When I switch to 1st console I can log into system (typing by blind), then I can see what was the result viewing it on the 7th console.

This way I managed to uninstall latest 2.6.31 kernels (which in some way happened to cause these problems, one of the upgrades was linux-image-2.6.31-15-generic).
Additionally touchpad (it's a laptop, Dell Inspiron 1525) doesn't work.

The system was upgraded from 9.04 to 9.10 about a month ago that's why I had still 2.6.28 kernel and can now write this message, but the system is very unresponding, load average is 1.4 1.4 1.5 with only firefox (2 tabs, no flash) and kontact open. I don't use compiz, so this is not a reason for sluggishness.
I have a C2D processor with 4GB or RAM, no resource demanding services are running. I usually solve most of my issues myself, but this time I can't see anything in logfiles.

This bug is similar to #480707, but I have Intel graphics card and to be honest I don't think it is a bug in kernel, but although to 2.6.28 version solved the black screen issue.

If You need more information, let me know and I'll be more then happy to help.

[ppietryga (ppietryga)]

Managed to solve this, by removing kdm and installing older version.

[ppietryga (ppietryga)]

As described in this http://ubuntuforums.org/showthread.php?t=1325199 forum thread (last Edit) I managed to solve this. The problem was with kdm (v. 4.3.2_ubuntu7.1) package from karmic-proposed repository.
Regards
ppietryga

[Jonathan Thomas (echidnaman)]

The ubuntu7.1 update didn't affect kdm at all, so I highly doubt that it was the cause.
As long as it's solved now then we really can't know what was causing it in the first place, so I am closing this bug. Thanks for the report.

[ppietryga (ppietryga)]

Below I attach an aptitude log of changes I made that fixed my issue (I have Polish locale set up, so the translation is my and some entries may not look like on Your computer).

As You can see I removed kdm (7.1) which uninstalled also kubuntu-desktop.

After removing proposed-updates I cleaned apt cache (not sure if it's needed), aptitude updated and then installed kubuntu-desktop, which installed also kdm (as dependency) and reverted some packages from version 7.1 to 7.

=== START ===
Aptitude 0.4.11.11: log report
Sun, Nov 15 2009 20:18:36 +0100

IMPORTANT: this log only lists intended actions; actions which fail due to
dpkg problems may not be completed.

Will install 0 packages, and remove 2 packages.
4358kB of disk space will be freed
===============================================================================
[REMOVE, DEPENDENCIES] kubuntu-desktop
[REMOVE] kdm
===============================================================================

Log complete.
Aptitude 0.4.11.11: log report
Sun, Nov 15 2009 20:25:43 +0100

IMPORTANT: this log only lists intended actions; actions which fail due to
dpkg problems may not be completed.

Will install 8 packages, and remove 0 packages.
4358kB of disk space will be used
===============================================================================
[REVERT] kdebase-workspace 4:4.3.2-0ubuntu7.1 -> 4:4.3.2-0ubuntu7
[REVERT] kdebase-workspace-bin 4:4.3.2-0ubuntu7.1 -> 4:4.3.2-0ubuntu7
[REVERT] kdebase-workspace-data 4:4.3.2-0ubuntu7.1 -> 4:4.3.2-0ubuntu7
[REVERT] kdebase-workspace-kgreet-plugins 4:4.3.2-0ubuntu7.1 -> 4:4.3.2-0ubuntu7
[REVERT] plasma-dataengines-workspace 4:4.3.2-0ubuntu7.1 -> 4:4.3.2-0ubuntu7
[REVERT] plasma-widgets-workspace 4:4.3.2-0ubuntu7.1 -> 4:4.3.2-0ubuntu7
[INSTALL] kdm
[INSTALL] kubuntu-desktop
===============================================================================

Log complete.
=== END ===

And the upgrade from 11.11 upgraded also kdm, below is a line from aptitude log file (again my translation):
[UPGRADED] kdm 4:4.3.2-0ubuntu7 -> 4:4.3.2-0ubuntu7.1

Maybe by saying that ubuntu7.1 update didn't affect kdm You mean nothing changed in kdm, but something was/is broken around there (maybe kdebase-workspace), because gdm worked (I could even log into KDE).

[ppietryga (ppietryga)]

Ho do I reopen this bug? After upgrades from 18th November the same thin happens.

I really don't care if this is a bug in kdm, something is wrong here since after changing the default display manager from kdm to gdm (dpkg-reconfigure kdm) system works and now it is not so unresponding.

I Posted this bug, a week ago and NO ONE has even got the effort to ask me any additional questions. I was even ready to revert to the upgrades and run whatever command to give You the output.

This bug was not an instability issue (as is the proposed repository described) it is CRITICAL!

Below is the aptitude log of the upgrades:

Aptitude 0.4.11.11: dziennik operacji
Wed, Nov 18 2009 13:54:04 +0100

IMPORTANT: this log only lists intended actions; actions which fail due to
dpkg problems may not be completed.

Will install 12 packages, and remove 0 packages.
28.7kB of disk space will be used
===============================================================================
[UPGRDAED] apparmor 2.3.1+1403-0ubuntu27.1 -> 2.3.1+1403-0ubuntu27.2
[UPGRDAED] apparmor-utils 2.3.1+1403-0ubuntu27.1 -> 2.3.1+1403-0ubuntu27.2
[UPGRDAED] kdebase-workspace 4:4.3.2-0ubuntu7 -> 4:4.3.2-0ubuntu7.1
[UPGRDAED] kdebase-workspace-bin 4:4.3.2-0ubuntu7 -> 4:4.3.2-0ubuntu7.1
[UPGRDAED] kdebase-workspace-data 4:4.3.2-0ubuntu7 -> 4:4.3.2-0ubuntu7.1
[UPGRDAED] kdebase-workspace-kgreet-plugins 4:4.3.2-0ubuntu7 -> 4:4.3.2-0ubuntu7.1
[UPGRDAED] kdm 4:4.3.2-0ubuntu7 -> 4:4.3.2-0ubuntu7.1
[UPGRDAED] libapparmor-perl 2.3.1+1403-0ubuntu27.1 -> 2.3.1+1403-0ubuntu27.2
[UPGRDAED] libapparmor1 2.3.1+1403-0ubuntu27.1 -> 2.3.1+1403-0ubuntu27.2
[UPGRDAED] plasma-dataengines-workspace 4:4.3.2-0ubuntu7 -> 4:4.3.2-0ubuntu7.1
[UPGRDAED] plasma-widgets-workspace 4:4.3.2-0ubuntu7 -> 4:4.3.2-0ubuntu7.1
[UPGRDAED] virtualbox-3.0 3.0.10-54097_Ubuntu_karmic -> 3.0.12-54655_Ubuntu_karmic
===============================================================================

Log complete.

[ppietryga (ppietryga)]

I changed the status to new, because I don't know how to reopen a bug report.

[ppietryga (ppietryga)]

This bug was NOT solved. I maganged to override the way to log into system, but the bug is still there.
Do You read what I write here? I WANT to use kdm (because my main working environment id KDE and using gdm my wife can't shutdown the system from K-menu).
I repeat the bug was not solved, I had to revert the upgrades from ubuntu7.1 to ubuntu7, but because You moved the updates from proposed (not fixing the error, not even searching for it) now it is a current version and it broke my system.

In my bug report I wrote it is in kdm because changing to gdm fixed my main issue, but I don't know where it sits.Why are You ignoring my attempts? Is it my bad English (it's not my mothertongue)?

YOU keep on saying: If You want to help, report bugs. I did it and You just ignore me.
I wrote it before: What information do You want from me and I will provide it.

[ppietryga (ppietryga)]

Jonathan, I'll keep assigning this bug to You, until YOU take the steps to solve this problem.

I am don't have knowledge as to who should this be assigned, but You replied to my first bugreport, so I suppose You who is who here.

Unassigning from this bug won't help, UNTIL YOU TAKE SOME STEPS TO FIX THIS. Mybe point to someone who should take care of it or has more knowledge to solve this. I'm willing to help. But YOU (all) have to tell me how.

Regards
Paweł

[Terence Simpson (tsimpson)]

Being abusive is not the way to get the issue resolved

[ppietryga (ppietryga)]

THEN WHAT IS THE WAY TO GET THE ISSUE RESOLVED!?

[ppietryga (ppietryga)]

THEN WHAT IS THE WAY TO GET THE ISSUE RESOLVED?!

[Jonathan Thomas (echidnaman)]

You will probably just have to find someone to help you. To be honest I am getting pretty sick of this bullshit. We are not your paid servants. If you would like free tech support you could try your luck getting help in the #kubuntu support IRC channel. That failing, you could consider buying a support plan from Canonical and get professional tech support. But do not harass bug triagers. We are all doing this on our own, volunteer time. Horrendously impolite and demanding reports such as what this report has devolved to will be closed as unmanageable. Good day.

[ppietryga (ppietryga)]

Is this a bug tracker or just a tool to change the status from net to invalid?

This BUG is still happening, so how can You be so IGNORANT.

I was always very fond of how linux community works, but looking at how YOU "SOLVE" issue I must say You're just a buch of ignorants.

I wasn't demanding until You started acting strange, this is Your quotation:

The ubuntu7.1 update didn't affect kdm at all, so I highly doubt that it was the cause.
As long as it's solved now then we really can't know what was causing it in the first place, so I am closing this bug. Thanks for the report.

How can You say it was solved (Yes I marked it that, but it wasn't solved in 7.1 version), since You saw what I need to do to fix my problem.

Good day and hope You're still so fond of yourselves like You are- VOLOUNTEERS!!.

[ppietryga (ppietryga)]

Assigned to You so I can keep my impolite and demanding badge :/

[Dylan McCall (dylanmccall)]

This is a bug against kdm, right?

Why is it marked as affecting the kdebase-workspace package?

[Terence Simpson (tsimpson)]

Because kdebase-workspace is the source package of kdm

[hawk (rudidu)]

ppietryga stop being such a rude, obnoxious and downright ungrateful pig.

We are all volunteers, seriously grow up man.

[ppietryga (ppietryga)]

It's my last post here, as I can see this is not going to resolving the issue.

I was a happy Linux user for over 10 years and had a good time with ubuntu/kubuntu. My issues I always solved using forums, mailing-lists, wikis, bug trackers. I did alot to advocate FOR ubuntu because of it's community, stability, quality and support. I even made appear in one of my college's computer laboratory on all computers. I'm more an administrator than developer and after few years without problems I decided to help at least by reporting bugs and enabled ubuntu-proposed repo. It all worked great until 11.11.2009 when the upgrade broke everything.
I filed a bug report (whaever the quality of it, I'm quite sure it was of poor quality) and awaited some questions that will help YOU (bug triagers) get some more info about it and in the end fix the issue. Maybe the bug was not in the code of kdm, but in the package itself (although the upgrade went flawless).
Jonathan wrote that You are not my paid servants but bug triagers, so why don't You triage the bug? It was CRITICAL (no matter what You say about it), because it prevented using the system by me. I worked around this problem by switching to gdm (and reverting from 7.1 to 7), but that didn't solve the issue with kdm (v7.1 or whatever this bug was in). After a week the proposed update was moved to update and my system automatically changed to broken version. I could of course install old version of it, but that STILL DIDN'T solve the problem. I switched the status of bug from invalid back to new and assigned Jonathan (he was the only one who responded to my first report), but he and no one else made any attempt to fix this problem (didn't contact me about more information, didn't delegate it to someone else) just unassigned from it without any comment.
Yeah! and the problem is fixed (if I can't see it, it doesn't exist).
I wrote some rude words about this situation and assigned it again to Jonathan, then Terence wrote a very interesting comment that abusing is not a way to get the issue resolved, but if that's not the way, then WHAT IS THE WAY?
I wrote some rude, obnoxious and ungrateful words about how self loving not seeing further then the tip of Your nose "bug triagers" You are (and I am still as sure about that as then).
During this discussion I get a feeling no one reads what I write about the issue, so @hawk grow up yourself, if working for free means to You that You can ignore whatever You want based on i.e. the result of dice throw.
Now it's time to test some other distros where the community is not so focused on how great they are and try to be as helpful as thay can.
So long, have a good self focused day.