[Desktop-packages] [Bug 1844158] [NEW] FTBFS using vala-0.46.1
Public bug reported: Trying to build on/for fedora 31+ fails with the following errors: make[2]: Entering directory '/builddir/build/BUILD/libunity-7.1.4/src' /usr/bin/valac -C -H unity.h -d . --gir=Unity-7.0.gir --library unity --internal-vapi=unity-internal.vapi --internal-header=unity-internal.h --target-glib=2.32 --thread --use-header --vapidir ../vapi --vapidir ../protocol --vapidir . --pkg unity-protocol --pkg config --pkg unity-trace --pkg glib-2.0 --pkg gmodule-2.0 --pkg gobject-2.0 --pkg gio-2.0 --pkg gio-unix-2.0 --pkg dee-1.0 --pkg Dbusmenu-0.4 unity-appinfo-manager.vala unity-icon.vala unity-inspector.vala unity-io.vala unity-launcher.vala unity-category.vala unity-filters.vala unity-preferences-manager.vala unity-merge-strategy.vala unity-models.vala unity-search.vala unity-synchronizer.vala unity-previews.vala unity-result-activation.vala unity-scope-interface.vala unity-scope-dbus-connector.vala unity-scope-dbus-impl.vala unity-scope-channel.vala unity-deprecated-scope.vala unity-deprecated-scope-impl.vala unity-aggregator-scope.vala unity-aggregator-scope-private.vala unity-master-scope.vala unity-simple-scope.vala unity-scope-loader.vala unity-scope-tracker.vala unity-sound-menu.vala unity-sound-menu-mpris.vala unity-utils.vala Command-line option `--thread` is deprecated and will be ignored Compilation failed: 2 error(s), 0 warning(s) BUILDSTDERR: unity-deprecated-scope.vala:64.3-64.28: error: Creation method of abstract class cannot be public. BUILDSTDERR: public DeprecatedScopeBase (string dbus_path_, string id_) BUILDSTDERR: ^^ BUILDSTDERR: unity-aggregator-scope.vala:54.3-54.24: error: Creation method of abstract class cannot be public. BUILDSTDERR: public AggregatorScope (string dbus_path_, string id_, MergeMode merge_mode = AggregatorScope.MergeMode.OWNER_SCOPE, bool proxy_filter_hints = false) BUILDSTDERR: ^^ BUILDSTDERR: make[2]: *** [Makefile:1389: libunity_la_vala.stamp] Error 1 ** Affects: libunity (Ubuntu) Importance: Undecided Status: New ** Affects: libunity (Fedora) Importance: Unknown Status: Unknown ** Bug watch added: Red Hat Bugzilla #1736053 https://bugzilla.redhat.com/show_bug.cgi?id=1736053 ** Also affects: libunity via https://bugzilla.redhat.com/show_bug.cgi?id=1736053 Importance: Unknown Status: Unknown ** Also affects: libunity (Fedora) via https://bugzilla.redhat.com/show_bug.cgi?id=1736053 Importance: Unknown Status: Unknown ** No longer affects: libunity -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libunity in Ubuntu. Matching subscriptions: dp-libunity https://bugs.launchpad.net/bugs/1844158 Title: FTBFS using vala-0.46.1 Status in libunity package in Ubuntu: New Status in libunity package in Fedora: Unknown Bug description: Trying to build on/for fedora 31+ fails with the following errors: make[2]: Entering directory '/builddir/build/BUILD/libunity-7.1.4/src' /usr/bin/valac -C -H unity.h -d . --gir=Unity-7.0.gir --library unity --internal-vapi=unity-internal.vapi --internal-header=unity-internal.h --target-glib=2.32 --thread --use-header --vapidir ../vapi --vapidir ../protocol --vapidir . --pkg unity-protocol --pkg config --pkg unity-trace --pkg glib-2.0 --pkg gmodule-2.0 --pkg gobject-2.0 --pkg gio-2.0 --pkg gio-unix-2.0 --pkg dee-1.0 --pkg Dbusmenu-0.4 unity-appinfo-manager.vala unity-icon.vala unity-inspector.vala unity-io.vala unity-launcher.vala unity-category.vala unity-filters.vala unity-preferences-manager.vala unity-merge-strategy.vala unity-models.vala unity-search.vala unity-synchronizer.vala unity-previews.vala unity-result-activation.vala unity-scope-interface.vala unity-scope-dbus-connector.vala unity-scope-dbus-impl.vala unity-scope-channel.vala unity-deprecated-scope.vala unity-deprecated-scope-impl.vala unity-aggregator-scope.vala unity-aggregator-scope-private.vala unity-master-scope.vala unity-simple-scope.vala unity-scope-loader.vala unity-scope-tracker.vala unity-sound-menu.vala unity-sound-menu-mpris.vala unity-utils.vala Command-line option `--thread` is deprecated and will be ignored Compilation failed: 2 error(s), 0 warning(s) BUILDSTDERR: unity-deprecated-scope.vala:64.3-64.28: error: Creation method of abstract class cannot be public. BUILDSTDERR: public DeprecatedScopeBase (string dbus_path_, string id_) BUILDSTDERR: ^^ BUILDSTDERR: unity-aggregator-scope.vala:54.3-54.24: error: Creation method of abstract class cannot be public. BUILDSTDERR: public AggregatorScope (string dbus_path_, string id_, MergeMode merge_mode = AggregatorScope.MergeMode.OWNER_SCOPE, bool proxy_filter_hints = false) BUILDSTDERR: ^^ BUILDSTDERR: make[2]: *** [Makefile:1389: libunity_la_vala.stamp] Error 1 To manage notifications about this bug go to:
[Desktop-packages] [Bug 310351]
That said, I'll have to review what gnome (still) supports. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-utils in Ubuntu. https://bugs.launchpad.net/bugs/310351 Title: Kubuntu screensaver xdg-screensaver broken Status in Xdg-utils: Unknown Status in xdg-utils package in Ubuntu: Confirmed Status in xdg-utils package in Debian: Confirmed Bug description: Binary package hint: kscreensaver xdg-screensaver returns "bad call" for all values tested. Looking at the script, I'd guess it is because it detects the KDE desktop and tries to use dcop when KDE4 has moved to dbus, but that's just a guess. For example: $ xdg-screensaver activate call failed lsb_release -rd -> Ubuntu 8.10 Flavor is kbuntu To manage notifications about this bug go to: https://bugs.launchpad.net/xdg-utils/+bug/310351/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 310351]
I think I agree with Michael, would you mind rebasing your patch against latest xdg-screensaver.in ? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-utils in Ubuntu. https://bugs.launchpad.net/bugs/310351 Title: Kubuntu screensaver xdg-screensaver broken Status in Xdg-utils: Unknown Status in xdg-utils package in Ubuntu: Confirmed Status in xdg-utils package in Debian: Confirmed Bug description: Binary package hint: kscreensaver xdg-screensaver returns "bad call" for all values tested. Looking at the script, I'd guess it is because it detects the KDE desktop and tries to use dcop when KDE4 has moved to dbus, but that's just a guess. For example: $ xdg-screensaver activate call failed lsb_release -rd -> Ubuntu 8.10 Flavor is kbuntu To manage notifications about this bug go to: https://bugs.launchpad.net/xdg-utils/+bug/310351/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 310351]
In short, maybe we can use SimulateUserActivity where it is available, and do something else where it isn't -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-utils in Ubuntu. https://bugs.launchpad.net/bugs/310351 Title: Kubuntu screensaver xdg-screensaver broken Status in Xdg-utils: Unknown Status in xdg-utils package in Ubuntu: Confirmed Status in xdg-utils package in Debian: Confirmed Bug description: Binary package hint: kscreensaver xdg-screensaver returns "bad call" for all values tested. Looking at the script, I'd guess it is because it detects the KDE desktop and tries to use dcop when KDE4 has moved to dbus, but that's just a guess. For example: $ xdg-screensaver activate call failed lsb_release -rd -> Ubuntu 8.10 Flavor is kbuntu To manage notifications about this bug go to: https://bugs.launchpad.net/xdg-utils/+bug/310351/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 310351]
I'll have to think about this more, not keen on adding any perl dependencies. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-utils in Ubuntu. https://bugs.launchpad.net/bugs/310351 Title: Kubuntu screensaver xdg-screensaver broken Status in Xdg-utils: Unknown Status in xdg-utils package in Ubuntu: Confirmed Status in xdg-utils package in Debian: Confirmed Bug description: Binary package hint: kscreensaver xdg-screensaver returns "bad call" for all values tested. Looking at the script, I'd guess it is because it detects the KDE desktop and tries to use dcop when KDE4 has moved to dbus, but that's just a guess. For example: $ xdg-screensaver activate call failed lsb_release -rd -> Ubuntu 8.10 Flavor is kbuntu To manage notifications about this bug go to: https://bugs.launchpad.net/xdg-utils/+bug/310351/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1024482] Re: Mouse cursor theme does not change from default after login
** Bug watch added: Red Hat Bugzilla #989152 https://bugzilla.redhat.com/show_bug.cgi?id=989152 ** Also affects: unity-greeter via https://bugzilla.redhat.com/show_bug.cgi?id=989152 Importance: Unknown Status: Unknown ** Project changed: unity-greeter = lightdm -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-greeter in Ubuntu. https://bugs.launchpad.net/bugs/1024482 Title: Mouse cursor theme does not change from default after login Status in Light Display Manager: Unknown Status in LightDM GTK+ Greeter: Confirmed Status in “unity-greeter” package in Ubuntu: Confirmed Status in “lightdm” package in Debian: Confirmed Status in “lightdm-gtk-greeter” package in Debian: Confirmed Bug description: When using LightDM to login to a GNOME Shell session, the mouse cursor's appearance does not change from what it is in the lightdm login screen (black pointer from default X theme). Any custom mouse cursor theme actually does apply within any open application windows, but hovering the cursor over the window title bar, the root window, or the Shell interface changes it back to the default black pointer, leading to an inconsistent appearance. To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1024482/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
