Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem.
We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures. At a minimum, we need: 1. The specific steps or actions you took that caused you to encounter the problem. 2. The behavior you expected. 3. The behavior you actually encountered (in as much detail as possible). Please also ensure that you include the release and flavour of Ubuntu that you are using. Thank you! Please note: Your linked bug report says you fixed it with "I was able to recover from the desaster by hitting ctrl+alt+F3, logging in via the virtual console, and running: sudo dpkg-reconfigure kdm3" however no such package exists (https://packages.ubuntu.com/search?suite=all&searchon=names&keywords=kdm3) let alone other vague details you couldn't remember. It's very possible you meant `gdm3`, however that should be stated/corrected. -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to meta-kde in Ubuntu. https://bugs.launchpad.net/bugs/1888859 Title: installing kde-standard bricks computer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/meta-kde/+bug/1888859/+subscriptions -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
