[Dx-packages] [Bug 1613909] [NEW] /usr/lib/arm-linux-gnueabihf/indicator-bluetooth/indicator-bluetooth-service:5:g_settings_set_property:object_set_property:g_object_new_internal:g_object_new_valist:g
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding indicator-bluetooth. This problem was most recently seen with version 0.0.6+16.04.20160526-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/78bcd419fdd02dc9be375b0983d3ed7c8a60399a contains more details. ** Affects: indicator-bluetooth (Ubuntu) Importance: Undecided Status: New ** Tags: xenial -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-bluetooth in Ubuntu. https://bugs.launchpad.net/bugs/1613909 Title: /usr/lib/arm-linux-gnueabihf/indicator-bluetooth/indicator-bluetooth- service:5:g_settings_set_property:object_set_property:g_object_new_internal:g_object_new_valist:g_object_new Status in indicator-bluetooth package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding indicator-bluetooth. This problem was most recently seen with version 0.0.6+16.04.20160526-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/78bcd419fdd02dc9be375b0983d3ed7c8a60399a contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-bluetooth/+bug/1613909/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1613906] [NEW] /usr/lib/arm-linux-gnueabihf/indicator-power/indicator-power-service:5:g_settings_set_property:object_set_property:g_object_new_internal:g_object_new_valist:g_object_
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding indicator-power. This problem was most recently seen with version 12.10.6+16.04.20160708-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/979610fc87fd996e3a9c32a8ce1f9d29b3206f27 contains more details. ** Affects: indicator-power (Ubuntu) Importance: Undecided Status: New ** Tags: xenial -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-power in Ubuntu. https://bugs.launchpad.net/bugs/1613906 Title: /usr/lib/arm-linux-gnueabihf/indicator-power/indicator-power- service:5:g_settings_set_property:object_set_property:g_object_new_internal:g_object_new_valist:g_object_new Status in indicator-power package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding indicator-power. This problem was most recently seen with version 12.10.6+16.04.20160708-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/979610fc87fd996e3a9c32a8ce1f9d29b3206f27 contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1613906/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 501864] Re: Regression: fast user switch can no longer be fast because it locks screen every time.
# Current status: regression bug still observed Bug still present on Xubuntu 16.04 running XFCE (and without a doubt with Unity, too, since logic is in lightdm which is common). # Good discussion at the time of bug report Robert Pollak reported it very well: it's a regression. ## Some workarounds no longer applicable with lightdm Hugo Buddel @v-launchpad-hugo-doemaarwat-nl wrote: > FWIW, if you disable locking the screen entirely for the accounts, then it will not lock the screen when switching users anymore. This workaround no longer works under the new lightdm logic: lightdm always switch to a lightdm greeter even if the session is not locked. Robert Pollak (robert-pollak) wrote: > I am still on Karmic and my workaround so far was to train my family to use Ctrl-Alt-Fx for switching if possible. This also helped with Karmic's missing fast-user-switch. This workaround combined with completely disabling locking might still works under the new lightdm logic. Then users then have to guess and try which session is on which VT. Klaus Reichl (klaus-reichl) made a very good case: > A use case for family sharing computers is also: > - If I wanna lock, I do > - If I switch to another user for whatever purpose, > I don't want to lock automatically, > since I'm switching back in most of the cases soon > > So what would be needed here is another option beside "disable_lock_screen", > named something like "disable_lock_screen_on_user_switch" and this should > really be changeable efficiently in the user switching menu. Hugo Buddel @v-launchpad-hugo-doemaarwat-nl confirmed with: * concrete examples * good analysis of what is related and what is not, showing that current logic is flawed # What now? ## Need remains In the meantime, some tech layers have changed (specifically, lightdm replaced many other components) but the users' needs remain. And human users that share a computer (e.g. at home) want fast switching that is fast. ## Solution Bringing back a per-user option that says "Lock screen on switching users" would be very nice. ## Proof-of-concept implementation I opened https://askubuntu.com/questions/811953/switching-between-two- opened-x-sessions-without-reauthenticating with a proof-of-concept implementation for lightdm. Currently it just allows any user to fast switch to any user that has a session already opened (actually, it unlocks it, this can be improved). This is overkill, but at least it provides the benefit and users wishing security can use a third party screen locker (e.g. xscreensaver) to get it back. I'm open to discussing alternate solutions, like having groups of mutually trusted users as sketched on https://askubuntu.com/questions/811953/switching-between-two-opened-x -sessions-without-reauthenticating . Thank you for your attention. -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-session in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/501864 Title: Regression: fast user switch can no longer be fast because it locks screen every time. Status in Session Menu: Triaged Status in indicator-session package in Ubuntu: Triaged Bug description: In the preferences of Jaunty's fast-user-switch-applet it was possible to uncheck "Lock screen after switching users". This is missing now. To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-session/+bug/501864/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 501864] Re: Regression: fast user switch can no longer be fast because it locks screen every time.
** Summary changed: - Switch Users without locking screen + Regression: fast user switch can no longer be fast because it locks screen every time. -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-session in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/501864 Title: Regression: fast user switch can no longer be fast because it locks screen every time. Status in Session Menu: Triaged Status in indicator-session package in Ubuntu: Triaged Bug description: In the preferences of Jaunty's fast-user-switch-applet it was possible to uncheck "Lock screen after switching users". This is missing now. To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-session/+bug/501864/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1612767] Re: Drop appmenu-qt5 from default installations
Thanks a lot for that work! No objections, commit away but don't upload yet since we still struggle with the proposed migration... -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-appmenu in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1612767 Title: Drop appmenu-qt5 from default installations Status in indicator-appmenu package in Ubuntu: New Status in qtbase-opensource-src package in Ubuntu: New Bug description: Currently we are using appmenu-qt5 as our platform theme on desktop, however it has many disadvantages, which make me want to get rid of it: 1) Its design is a hack: instead of the using normal QPA API for getting the menu, it retrieves the menu bar using QWidget::findChild, and then casts the pointer to QMenu*. The normal methods (which are getting called by Qt) remain empty stubs. 2) It is preventing applications from using GTK+ theme integration, such as dialogs (I reported this as bug 1378935, but there is no easy way to fix that). 3) It is not working with Qt Quick applications (because it expects a QtWidgets window; see also bug 1323853). The standard implementation will work with i.e. Qt Quick Controls 2 using apps (implemented in https://codereview.qt-project.org/142733). 4) Finally, it is mostly unmaintained: most patches since 2014 are authored by me, however I see no point continuing to develop that code. Recently, Shawn Rutledge and I have written a native implementation of what appmenu-qt5 provides (global menu and system tray), which is part of Qt. That code uses the normal API, is well maintained, and works better than appmenu-qt5 (or at least not worse). So I propose to drop appmenu-qt5 from default Ubuntu installations, and maybe later from archive too. Unfortunately we use Qt 5.6, and some of the needed patches are only in Qt 5.7, so I would like to backport them to our packaging: https://code.qt.io/cgit/qt/qtbase.git/commit/?id=f199bb9133fe0446 (will be in 5.6.2 / 5.7.0) https://code.qt.io/cgit/qt/qtbase.git/commit/?id=488cf78e44947eff (will be in 5.7.0) https://code.qt.io/cgit/qt/qtbase.git/commit/?id=b6a824d0a3b4fabd (will be in 5.7.0) https://code.qt.io/cgit/qt/qtbase.git/commit/?id=e4d79e1fdeb6b26b (will be in 5.7.0) Timo: if you have no objections, I will commit those patches to the packaging Git. After we do that, I will remove the appmenu-qt5 recommendation from indicator-appmenu (that is the only package referring to it). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-appmenu/+bug/1612767/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1613591] [NEW] Theme parsing error
Public bug reported: Logged on yakkety, gnome-shell session: org.freedesktop.Notifications[2307]: (notify-osd:2584): Gtk-WARNING **: Theme parsing error: gtk-widgets.css:23:18: not a number org.freedesktop.Notifications[2307]: (notify-osd:2584): Gtk-WARNING **: Theme parsing error: gtk-widgets.css:23:18: Expected a string. org.freedesktop.Notifications[2307]: (notify-osd:2584): Gtk-WARNING **: Theme parsing error: gtk-widgets.css:815:10: not a number org.freedesktop.Notifications[2307]: (notify-osd:2584): Gtk-WARNING **: Theme parsing error: gtk-widgets.css:815:24: Using Pango syntax for the font: style property is depreca org.freedesktop.Notifications[2307]: (notify-osd:2584): Gtk-WARNING **: Theme parsing error: gtk-widgets.css:1966:14: not a number org.freedesktop.Notifications[2307]: (notify-osd:2584): Gtk-WARNING **: Theme parsing error: gtk-widgets.css:1966:14: Expected a string. org.freedesktop.Notifications[2307]: (notify-osd:2584): Gtk-WARNING **: Theme parsing error: nautilus.css:50:71: Using one color stop with linear-gradient() is deprecated. org.freedesktop.Notifications[2307]: (notify-osd:2584): Gtk-WARNING **: Theme parsing error: nautilus.css:51:71: Using one color stop with linear-gradient() is deprecated. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: notify-osd 0.9.35+16.04.20160415-0ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-0.1-generic 4.8.0-rc1 Uname: Linux 4.8.0-0-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Aug 16 09:51:44 2016 DesktopSession: 'ubuntu' GtkTheme: 'Adwaita' IconTheme: 'Adwaita' Lsusb: Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 046d:c062 Logitech, Inc. M-UAS144 [LS1 Laser Mouse] Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: ASUSTEK COMPUTER INC P5W DH Deluxe ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-0-generic root=UUID=7c755ed6-51cc-4b75-88ac-9c75acf82749 ro RelatedPackageVersions: xserver-xorg 1:7.7+13ubuntu3 libgl1-mesa-glx 12.0.1-3ubuntu3 libdrm2 2.4.70-1 xserver-xorg-video-intel N/A xserver-xorg-video-ati N/A SourcePackage: notify-osd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/22/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3002 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5W DH Deluxe dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3002:bd07/22/2010:svnASUSTEKCOMPUTERINC:pnP5WDHDeluxe:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5WDHDeluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: P5W DH Deluxe dmi.product.version: System Version dmi.sys.vendor: ASUSTEK COMPUTER INC ** Affects: notify-osd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages yakkety -- You received this bug notification because you are a member of DX Packages, which is subscribed to notify-osd in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1613591 Title: Theme parsing error Status in notify-osd package in Ubuntu: New Bug description: Logged on yakkety, gnome-shell session: org.freedesktop.Notifications[2307]: (notify-osd:2584): Gtk-WARNING **: Theme parsing error: gtk-widgets.css:23:18: not a number org.freedesktop.Notifications[2307]: (notify-osd:2584): Gtk-WARNING **: Theme parsing error: gtk-widgets.css:23:18: Expected a string. org.freedesktop.Notifications[2307]: (notify-osd:2584): Gtk-WARNING **: Theme parsing error: gtk-widgets.css:815:10: not a number org.freedesktop.Notifications[2307]: (notify-osd:2584): Gtk-WARNING **: Theme parsing error: gtk-widgets.css:815:24: Using Pango syntax for the font: style property is depreca org.freedesktop.Notifications[2307]: (notify-osd:2584): Gtk-WARNING **: Theme parsing error: gtk-widgets.css:1966:14: not a number org.freedesktop.Notifications[2307]: (notify-osd:2584): Gtk-WARNING **: Theme parsing error: gtk-widgets.css:1966:14: Expected a string. org.freedesktop.Notifications[2307]: (notify-osd:2584): Gtk-WARNING **: Theme parsing error: nautilus.css:50:71: Using one color stop with linear-gradient() is deprecated. org.freedesktop.Notifications[2307]: (notify-osd:2584): Gtk-WARNING **: Theme parsing error: nautilus.css:51:71: Using one color stop with linear-gradient() is deprecated. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: notify-osd 0.9.35+16.04.20160415-0ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-0.1-generic 4.8.0-rc1 Uname: Linux 4.8.0-0-generic x86_64
