I don't know the protocol for filing bugs against a proxy-maintained package. Please correct the assignee/CC list if I messed that up. gnome-session 3.8 no longer supports RequiredProviders, see https://bugzilla.gnome.org/show_bug.cgi?id=691663. Non-GNOME sessions are expected to use RequiredComponents instead. This means the awesome-gnome.session no longer starts awesome, just gnome-settings-daemon. This makes it considerably less awesome. Moving awesome-gnome (and notification-daemon, if still considered necessary) to RequiredComponents should make gnome 3.8 awesome again.
Created attachment 354546 [details, diff] awesome-gnome.session.patch
(In reply to Alexander Tsoy from comment #1) > Created attachment 354546 [details, diff] [details, diff] > awesome-gnome.session.patch Will this patch work with old gnomes too?
(In reply to Maxim Koltsov from comment #2) > Will this patch work with old gnomes too? Hard to say. I tested it only with gnome-3.8.
I'd be surprised if this didn't work on older gnomes. RequiredComponents was already used to start gnome-settings-daemon (and you'd probably notice if that wasn't running). Unless older gnomes don't support starting more than one thing that way this should be fine.
We should test this patch against at least gnome 2.32 before applying, I'd say.
(In reply to Nikolaj Sjujskij from comment #5) > We should test this patch against at least gnome 2.32 before applying, I'd > say. You could apply the patch in a revbump that would be stabilized with Gnome 3.8
(In reply to Pacho Ramos from comment #6) > (In reply to Nikolaj Sjujskij from comment #5) > > We should test this patch against at least gnome 2.32 before applying, I'd > > say. > > You could apply the patch in a revbump that would be stabilized with Gnome > 3.8 True enough. Maxim, could you do that pretty please? I'd keep two copies of awesome-gnome.session in ./files/. Then we could ask AT with Gnome 2 to try it out.
Patch commited to tree in awesome-3.5.2-r1
