[12.3 KDE] Stuck at the Chameleon - no DeskEnv - constant failed restore of HIBERNATE?

Hello,
I’m looking for assistance debugging my OpenSUSE install - I’m not to savvy with the konsole, and currently I can’t consistently get things up.

Some quasi-reinstalls etc are an option but I’d rather not reformat because I’ve implemented tweaks, and the bandwidth from patches. . .
The error started when an (oddly long and laborious?) Apper update was interupted.

Now I’ve got no desktop. Graphically, boot is paused after the Chameleon-in-a-tree animation completes, and before the logon screen or the series-of-icons graphical boot animation.
Set to auto-logon.

I’ve a novice with OpenSUSE, and while strictly an amateur, I’m pretty savvy.

I played around and got it to verbose ~boot with f8, last instruction seems to be… “Started Restore Soundcard State”

wait a second…
is it stuck restoring from hibernate?

OK, how to restore GRUB via console or the installer USB (granted mine is loopy and uses YUMI, YUMI no like suse 12.3 had to kludge.)

or clear the hibernate data from crunchbang or something?

It seems ctrl-alt f_ isn’t bringing up a terminal anymore. * I can get one after f8 during boot if I am quick enough. Tried sudo /sbin/shutdown -r now, command worked, but still no desktop.

I believe I have hibernation data which is attemption to restore a session during which apper was active, but existed before another session in which apper was running updates, an outdate hibernation data.
Perhaps.
I just remembered the hibernation looks different graphically.

what a story mark

On 06/13/2013 07:06 AM, StuckAtChamelon wrote:
> The error started when an (oddly long and laborious?) Apper update was
> interupted. . . pretty savvy.

hmmmm…interrupting an update is not very savvy…because doing so
is absolutely going to leave the system in an unknown and unstable
state…

how the system got screwed into constantly trying to ‘restore’ from a
hibernate rather than a power off boot is far beyond my ability to
solve from afar…

maybe others will have a better idea but i guess the shortest path
and quickest solution is probably to hmmmmmmm hmmmmmmmmmmmmm start
over and next time don’t abort an update…

ok, so “start over” could have a range of meanings from

  1. restore from the most recent full backup taken when all things
    were smiling
  2. through restore from the latest btrfs snapshot
  3. or reinstall saving /home and data
  4. or maybe full format and install followed by rejoining
    saved/restored data
  5. re-tweaking as needed

i don’t know how extensive your backup or what is best for your
situation but … well, read my sig caveat and wait for other opinions…


dd
http://tinyurl.com/DD-Caveat

Are you getting to a terminal log in? Maybe a update will fix stuff that was not completed.

log in as root
then
zypper up

On 2013-06-13 10:00, dd wrote:
> On 06/13/2013 07:06 AM, StuckAtChamelon wrote:

> hmmmm…interrupting an update is not very savvy…because doing so is
> absolutely going to leave the system in an unknown and unstable state…

Right.

>
> how the system got screwed into constantly trying to ‘restore’ from a
> hibernate rather than a power off boot is far beyond my ability to solve
> from afar…

It is easy to bypass, though.

Grub, edit command line, remove the swap entry. Maybe there is even a
toked to add to ignore restore image.

> maybe others will have a better idea but i guess the shortest path and
> quickest solution is probably to hmmmmmmm hmmmmmmmmmmmmm start over and
> next time don’t abort an update…

That’s what I would do. Or attempt a same version offline system upgrade
(boot from dvd, choose upgrade). Of course, almost all patches and
updates are reverted.


Cheers / Saludos,

Carlos E. R.
(from 12.3 x86_64 “Dartmouth” at Telcontar)

I’m sensing some hostility in here. Not sure what’s up with the arrogant comments based on asinine assumptions. Nobody powers down mid-update intentionally or without urgency. Speaking of asinine assumptions, the hibernate theory’s out the window. I managed to restore grub using the installation medium, booting with the standard option/latest version produces the same error. All other default “advanced options” reach login, but immediately halt, just as the GUI begins to show the second icon in the series of 5 (wrench and screwdriver). In the system console?(ctrl-alt-f10) the halt occurs at this message:

 linux-splj NetowrkManager[469]:  [137118 1676.738010] wifi-utils-nl80211.c:669 nl80211_wiphy_info_handler(): Don't know the meaning of NL80211_ATTR_CIPHER_SUITES 0x000fac06. 

I can get a console and now I can log into the IceWM desktop environment, will try some things.

On 2013-06-14 05:56, StuckAtChamelon wrote:
>
> I’m sensing some hostility in here. Not sure what’s up with the arrogant
> comments based on asinine assumptions.

Huh? :open_mouth:


Cheers / Saludos,

Carlos E. R.
(from 12.3 x86_64 “Dartmouth” at Telcontar)