Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • linuxmce linuxmce
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 255
    • Issues 255
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • linuxmcelinuxmce
  • linuxmcelinuxmce
  • Issues
  • #1518
Closed
Open
Issue created Jul 20, 2012 by ArmorGnome@ArmorGnome

HybridCore graffically crippled on a failed MD load

1004, updated last July 19th.

A diskless MD hung and crashed on its first load for me (same junk box I shouldn't be wasting time with.) That failure seemed to have dumped devices and child devices onto my hybrid core. I had 2 orbiters, 2 flickr screens, etc. etc. It kicked my resolution down to 500x404. It was more than a resolution change though, I was also locked into onscreen orbiter's windows and could not recover. PadOrbiter failed to bring me out of suspense as it typically can by playing media on my stuck UI.

I was able to eventually alt+ctrl+f2 out and deleted the Generic PC as MD from devices. I did a full reboot and came back to the same graffic errors. After that I did a restore from clone and could not repeat the bug.

Assignee
Assign to
Time tracking