Has anyone tried speak about this with upstream? Did not check Eugene's patch, but my idea is simple. Just add extra command line option to allow disable acceleration check. If it is set, than check should not be made. For example --disable-acceleration-check. Than sessions who need it could add that in .desktop file: gnome-session --session=gnome-flashback --disable-acceleration-check
-- You received this bug notification because you are a member of Tieto, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1251281 Title: gnome-flashback (metacity) fails to start without hardware acceleration, cloud/remote environments (Forwarded-X/XRDP/VNC/NX/X2GO/Chromoting) Status in “gnome-session” package in Ubuntu: In Progress Bug description: When trying to launch gnome-flashback (metacity) session from XRDP/VNC/NX/X2GO/Chromoting it fails with diagnostics in log: >gnome-session-is-accelerated: No composite extension. >gnome-session-check-accelerated: Helper exited with code 256 >gnome-session-is-accelerated: No composite extension. >gnome-session-check-accelerated: Helper exited with code 256 >** (process:11622): WARNING **: software acceleration check failed: Child process exited with code 1 When starting manually gnome-panel, metacity, nautilus and other components from .xsession - it works normally. Looks like - unnecessary check performed (and failed). This breaks gnome-flashback, breaking upgrade path from previous LTS and removing most sane option for cloud environments! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1251281/+subscriptions -- Mailing list: https://launchpad.net/~tieto Post to : [email protected] Unsubscribe : https://launchpad.net/~tieto More help : https://help.launchpad.net/ListHelp
