[Touch-packages] [Bug 1987920] Re: indicator-datetime fails to build with default gcc (gcc-12)
It is released now, but we are looking into fixing build with gcc 12. And we are also looking into if we can port to ayatana this cycle. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-datetime in Ubuntu. https://bugs.launchpad.net/bugs/1987920 Title: indicator-datetime fails to build with default gcc (gcc-12) Status in indicator-datetime package in Ubuntu: Confirmed Status in indicator-datetime source package in Kinetic: Confirmed Bug description: indicator-datetime fails to build from source in Kinetic with the default compiler, gcc/g++-12 To allow the package to build so that we can complete the evolution- data-server 3.45 transition, I switched the package to build with gcc/g++-11. I suggest switching to the Ayatana Indicators (ayatana-indicator- datetime) which are maintained and are able to build successfully with the default compiler. See https://launchpad.net/bugs/1983374 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1987920/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1959343] Re: deprecation of the Canonical partner archive
@vorlon I have now approved Ubuntu-core-dev again which expires on 2023-01-25. You can see it here. https://launchpad.net/~unity7maintainers/+members But I am not sure which file is to modify here It is based on ubuntu- seed which is used by germinate. you can check https://git.launchpad.net/ubuntu-unity-meta/tree/update.cfg. There are lots of deprecated packages in desktop-amd64 and desktop-recommends- amd64. iIt hasn't been updated for long due to lack of sponsoring. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/1959343 Title: deprecation of the Canonical partner archive Status in subiquity: Invalid Status in app-install-data-partner package in Ubuntu: Fix Released Status in cloud-init package in Ubuntu: In Progress Status in curtin package in Ubuntu: Invalid Status in livecd-rootfs package in Ubuntu: Fix Released Status in python-apt package in Ubuntu: Fix Released Status in ubiquity package in Ubuntu: In Progress Status in ubuntu-release-upgrader package in Ubuntu: Fix Released Status in ubuntu-unity-meta package in Ubuntu: New Bug description: The Canonical partner archive is no longer being used for publishing new packages, and is empty from Ubuntu 20.10 on. We should stop including it in the default sources.list, and clean up references to it in our codebase. To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1959343/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1921781] Re: Build-depends on qt5-default which is obsolete and dropped in hirsute
@Gunnar, regarding indicator-sound, My merge requests is here https://code.launchpad.net/~khurshid-alam/indicator-sound/fix-build- impish/+merge/409379 & build-recipe (https://code.launchpad.net/~khurshid-alam/+recipe/indicator-sound- ftbfs-hirsuit), I have disabled the failing tests for now as most are related to phone or works on phone environment. I have no way to debug that. As per my testing this doesn't hamper functionality on desktop, indicator-sound works as expected but perhaps more testing requires on different hardware. These tests can be enabled for desktop later if someone able to fix those...may be ask 3v1n0 ? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to signon-ui in Ubuntu. https://bugs.launchpad.net/bugs/1921781 Title: Build-depends on qt5-default which is obsolete and dropped in hirsute Status in indicator-sound package in Ubuntu: Confirmed Status in libqofono package in Ubuntu: Fix Released Status in poppler-qml-plugin package in Ubuntu: Fix Released Status in qtpowerd package in Ubuntu: Fix Released Status in qtubuntu-cameraplugin-fake package in Ubuntu: Fix Released Status in signon-keyring-extension package in Ubuntu: Fix Released Status in signon-plugin-sasl package in Ubuntu: Fix Released Status in signon-ui package in Ubuntu: Fix Released Status in unity-api package in Ubuntu: Fix Released Status in unity-control-center package in Ubuntu: Invalid Bug description: These packages build-depend on the qt5-default package, which has been dropped upstream in Debian and will not be available in the hirsute release. These packages should either be updated to not require this build- dependency, or be removed from hirsute. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1921781/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1921781] Re: Build-depends on qt5-default which is obsolete and dropped in hirsute
** Changed in: unity-control-center (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to signon-ui in Ubuntu. https://bugs.launchpad.net/bugs/1921781 Title: Build-depends on qt5-default which is obsolete and dropped in hirsute Status in indicator-sound package in Ubuntu: Confirmed Status in libqofono package in Ubuntu: Fix Released Status in poppler-qml-plugin package in Ubuntu: Fix Released Status in qtpowerd package in Ubuntu: Fix Released Status in qtubuntu-cameraplugin-fake package in Ubuntu: Fix Released Status in signon-keyring-extension package in Ubuntu: Fix Released Status in signon-plugin-sasl package in Ubuntu: Fix Released Status in signon-ui package in Ubuntu: Fix Released Status in unity-api package in Ubuntu: Fix Released Status in unity-control-center package in Ubuntu: Invalid Bug description: These packages build-depend on the qt5-default package, which has been dropped upstream in Debian and will not be available in the hirsute release. These packages should either be updated to not require this build- dependency, or be removed from hirsute. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1921781/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1921781] Re: Build-depends on qt5-default which is obsolete and dropped in hirsute
@Gunnar: Th tests are failing...but we can disable the tests for nowthey are mostly phone related anyway...A few vala related fix may be needed. We can ask @ricotz. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to signon-ui in Ubuntu. https://bugs.launchpad.net/bugs/1921781 Title: Build-depends on qt5-default which is obsolete and dropped in hirsute Status in indicator-sound package in Ubuntu: Confirmed Status in libqofono package in Ubuntu: Fix Released Status in poppler-qml-plugin package in Ubuntu: Fix Released Status in qtpowerd package in Ubuntu: Fix Released Status in qtubuntu-cameraplugin-fake package in Ubuntu: Fix Released Status in signon-keyring-extension package in Ubuntu: Fix Released Status in signon-plugin-sasl package in Ubuntu: Fix Released Status in signon-ui package in Ubuntu: Fix Released Status in unity-api package in Ubuntu: Fix Released Status in unity-control-center package in Ubuntu: Confirmed Bug description: These packages build-depend on the qt5-default package, which has been dropped upstream in Debian and will not be available in the hirsute release. These packages should either be updated to not require this build- dependency, or be removed from hirsute. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1921781/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1921781] Re: Build-depends on qt5-default which is obsolete and dropped in hirsute
Unity-control-center is the integral part of Unity, so it can't be removed. I can simply remove indicator-sound from dependency of indicator-sond. But I will ask ~mitya57 if the build dependency can be fixed. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to signon-ui in Ubuntu. https://bugs.launchpad.net/bugs/1921781 Title: Build-depends on qt5-default which is obsolete and dropped in hirsute Status in indicator-sound package in Ubuntu: Confirmed Status in libqofono package in Ubuntu: Fix Released Status in poppler-qml-plugin package in Ubuntu: Fix Released Status in qtpowerd package in Ubuntu: Fix Released Status in qtubuntu-cameraplugin-fake package in Ubuntu: Fix Released Status in signon-keyring-extension package in Ubuntu: Fix Released Status in signon-plugin-sasl package in Ubuntu: Fix Released Status in signon-ui package in Ubuntu: Fix Released Status in unity-api package in Ubuntu: Fix Released Status in unity-control-center package in Ubuntu: Confirmed Bug description: These packages build-depend on the qt5-default package, which has been dropped upstream in Debian and will not be available in the hirsute release. These packages should either be updated to not require this build- dependency, or be removed from hirsute. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1921781/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1931901] Re: Revert background key patch removal breaks dependent packages
Unity-settings-daemon is still using that draw-background key. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gsettings-desktop-schemas in Ubuntu. https://bugs.launchpad.net/bugs/1931901 Title: Revert background key patch removal breaks dependent packages Status in gnome-desktop3 package in Ubuntu: Fix Released Status in gsettings-desktop-schemas package in Ubuntu: Invalid Bug description: in the package gnome-desktop3 there is a custom ubuntu patch that tries to write to the draw-background key that has now been removed in gsettings-desktop-schemas 40.0-1ubuntu1 All packages that depend on the gnome-desktop3 library now crash such as budgie-desktop Suggestion - either re-add the patch again ... or revert the gnome- desktop3 custom patch. The latter option changes the symbols so probably I'm guessing a so- name version bump is needed and any dependent packages need a rebuild? I'll try to locally rebuild gnome-desktop3 without the custom ubuntu patch to see what happens with budgie-desktop ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: gsettings-desktop-schemas 40.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-20.21+21.10.1-generic 5.11.21 Uname: Linux 5.11.0-20-generic x86_64 ApportVersion: 2.20.11-0ubuntu67 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: Budgie:GNOME Date: Mon Jun 14 20:52:16 2021 InstallationDate: Installed on 2021-06-14 (0 days ago) InstallationMedia: Ubuntu-Budgie 21.10 "Impish Indri" - Alpha amd64 (20210614) PackageArchitecture: all SourcePackage: gsettings-desktop-schemas UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-desktop3/+bug/1931901/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1921781] Re: Build-depends on qt5-default which is obsolete and dropped in hirsute
What is alternet meta package which pulls default version of qt hirsute? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to poppler-qml-plugin in Ubuntu. https://bugs.launchpad.net/bugs/1921781 Title: Build-depends on qt5-default which is obsolete and dropped in hirsute Status in indicator-sound package in Ubuntu: New Status in libqofono package in Ubuntu: New Status in poppler-qml-plugin package in Ubuntu: New Status in qtpowerd package in Ubuntu: New Status in qtubuntu-cameraplugin-fake package in Ubuntu: New Status in signon-keyring-extension package in Ubuntu: New Status in signon-plugin-sasl package in Ubuntu: New Status in signon-ui package in Ubuntu: New Status in unity-api package in Ubuntu: Fix Released Bug description: These packages build-depend on the qt5-default package, which has been dropped upstream in Debian and will not be available in the hirsute release. These packages should either be updated to not require this build- dependency, or be removed from hirsute. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1921781/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1869501] Re: Bluetooth status in the Unity menu bar does not always match status in system settings
That's indicator-bluetooth. So not a u-c-c bug. Also the issue could be with gnome-bluetooth since it works fine on my machine. Your error shows "Failed to set mode: Blocked through rfkill (0x12) "...so the hardware is blocking it. Try running "sudo rfkill unblock all" but you may have to re-run it after each boot. ** Also affects: bluez (Ubuntu) Importance: Undecided Status: New ** Changed in: unity-control-center (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1869501 Title: Bluetooth status in the Unity menu bar does not always match status in system settings Status in bluez package in Ubuntu: New Status in unity-control-center package in Ubuntu: Invalid Bug description: When no Bluetooth device is connected and I turn off Bluetooth with the switch in the menu of the notification icon, the Bluetooth status in System Settings app is still "on" however Bluetooth seems to be off. Also, when Bluetooth is turned on, the status of a paired device may show "connection on" in the notification icon menu when it is actually not connected, as System Settings do show correctly. In this case I have to switch off and on again if I want to activate the connection. Also, I can not switch the connection to a paired device on or off with the System Settings app. The switches are grey and I can not click them, however they do always show the correct status. Using: Ubuntu 19.10 with Unity desktop on Asus x571 laptop Info: unity: 7.5.0+19.10.20190924-0ubuntu1 unity-control-center: 15.04.0+19.10.20190921-0ubuntu1 service bluetooth status ● bluetooth.service - Bluetooth service Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset: enabled) Active: active (running) since Sat 2020-03-28 11:26:18 CET; 5h 42min ago Docs: man:bluetoothd(8) Main PID: 1035 (bluetoothd) Status: "Running" Tasks: 1 (limit: 4915) Memory: 3.5M CGroup: /system.slice/bluetooth.service └─1035 /usr/lib/bluetooth/bluetoothd Mär 28 14:17:39 Abook bluetoothd[1035]: /org/bluez/hci0/dev_00_22_37_55_9E_7D/fd0: fd(22) ready Mär 28 16:46:32 Abook bluetoothd[1035]: Failed to set mode: Blocked through rfkill (0x12) Mär 28 16:49:02 Abook bluetoothd[1035]: /org/bluez/hci0/dev_00_22_37_55_9E_7D/fd1: fd(22) ready Mär 28 16:49:22 Abook bluetoothd[1035]: Failed to set mode: Blocked through rfkill (0x12) Mär 28 16:50:05 Abook bluetoothd[1035]: Control: Refusing unexpected connect Mär 28 16:50:08 Abook bluetoothd[1035]: /org/bluez/hci0/dev_00_22_37_55_9E_7D/fd2: fd(22) ready Mär 28 16:53:38 Abook bluetoothd[1035]: Failed to set mode: Blocked through rfkill (0x12) Mär 28 16:58:41 Abook bluetoothd[1035]: Failed to set mode: Blocked through rfkill (0x12) Mär 28 16:59:23 Abook bluetoothd[1035]: Control: Refusing unexpected connect Mär 28 16:59:25 Abook bluetoothd[1035]: /org/bluez/hci0/dev_00_22_37_55_9E_7D/fd3: fd(22) ready Bluetooth device: T: Bus=01 Lev=01 Prnt=01 Port=13 Cnt=02 Dev#= 6 Spd=12 MxCh= 0 D: Ver= 2.01 Cls=e0(wlcon) Sub=01 Prot=01 MxPS=64 #Cfgs= 1 P: Vendor=8087 ProdID=0029 Rev=00.01 C: #Ifs= 2 Cfg#= 1 Atr=e0 MxPwr=100mA I: If#=0x0 Alt= 0 #EPs= 3 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb I: If#=0x1 Alt= 0 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: unity-control-center 15.04.0+19.10.20190921-0ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18 Uname: Linux 5.3.0-42-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.7 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu Date: Sat Mar 28 16:53:08 2020 EcryptfsInUse: Yes InstallationDate: Installed on 2020-01-20 (68 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: unity-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1869501/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1868732] Re: Single Sign-on dialogue has no [OK] button
Hittin Enter, or TAB+Enter should work. It isn't u-c-c bug. The issue is in gnome-online-accounts. For unity, you can run with GTK_CSD=1 unity-control-center ** Also affects: gnome-online-accounts (Ubuntu) Importance: Undecided Status: New ** Changed in: unity-control-center (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1868732 Title: Single Sign-on dialogue has no [OK] button Status in gnome-online-accounts package in Ubuntu: New Status in unity-control-center package in Ubuntu: Invalid Bug description: 1. Software updater says "You can use Livepatch to keep your computer up to date" 2. I click on the Livepatch button 3. Which says I have to log in to my Ubuntu One account 4. Up pops a dialogue box, which allows me to fill in my email and password 5. And no OK button. Hitting [return] doesn't help either. (See image) I can't log in to get Livepatch! ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: unity-control-center 15.04.0+18.04.20180216-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-91.92-generic 4.15.18 Uname: Linux 4.15.0-91-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.12 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu Date: Tue Mar 24 15:09:09 2020 ExecutablePath: /usr/bin/unity-control-center InstallationDate: Installed on 2015-04-27 (1793 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) SourcePackage: unity-control-center UpgradeStatus: Upgraded to bionic on 2020-03-12 (11 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1868732/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1866180] [NEW] Re-Upload in to Focal
Public bug reported: Hud was removed in LP: #1850748 due to python dependency. The merge request attached fixes that issue. ** Affects: hud (Ubuntu) Importance: Undecided Status: New ** Tags: focal ** Branch linked: lp:~khurshid-alam/hud/reupload-to-focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to hud in Ubuntu. https://bugs.launchpad.net/bugs/1866180 Title: Re-Upload in to Focal Status in hud package in Ubuntu: New Bug description: Hud was removed in LP: #1850748 due to python dependency. The merge request attached fixes that issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hud/+bug/1866180/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1860994] Re: Indicator menu is too wide
Which theme are you using ? Looks like mate which doesn't have calendar widget styles for indicator-datetime. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-datetime in Ubuntu. https://bugs.launchpad.net/bugs/1860994 Title: Indicator menu is too wide Status in indicator-datetime package in Ubuntu: New Bug description: The indicator's context menu does not appear to have a maximal width. This leads to an unattractive appearance when the show-events key in the com.canonical.indicator.datetime schema is true (default value) and there is an event with quite long name. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1860994/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1842324] Re: Port schemas from gnome-settings-daemon-common to com.canonical.unity.settings-daemon
** Changed in: unity-control-center (Ubuntu) Status: Fix Released => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1842324 Title: Port schemas from gnome-settings-daemon-common to com.canonical.unity .settings-daemon Status in indicator-session package in Ubuntu: Fix Released Status in ubuntu-settings package in Ubuntu: Fix Released Status in unity package in Ubuntu: Fix Released Status in unity-control-center package in Ubuntu: In Progress Status in unity-greeter package in Ubuntu: Fix Released Status in unity-settings-daemon package in Ubuntu: Fix Released Bug description: Unity-settings-daemon still depends on gnome-settings-daemon schemas. It is undesired as it requires to modify code in all unity related components when upstream drops some gsettings schemas. gnome-settings-daemon > 3.33 drops/modify media-keys schemas in an undesired way that it can't easily be reverted. Keyboard & mouse schemas are modified and unity-settings-daemon is crashing. So it's better unity uses it's own schema as suggested by Laney. We will of- course keep using settings migration (org.gnome.settings-daemon-> org.gnome.desktop) wherever possible. https://gitlab.gnome.org/GNOME/gnome-settings- daemon/commit/6dff93a0dfa80db3f481eed5d6ed689bf469aa1b https://gitlab.gnome.org/GNOME/gnome-settings- daemon/commit/44f53c64c5a2514d2c022bcb1596a9e46f1df51c https://gitlab.gnome.org/GNOME/gnome-settings- daemon/commit/121a6f89917898b8d05db2e1933dd0ad59c26768 Since this is a huge task it can be achieved gradually. 1) Ubuntu 19.10 - Port media keys to use com.canonical.unity.settings-daemon - u-s-d will still use org.gnome.settings-daemon name in dbus - u-s-d will still respects activation toggle in org.gnome.settings- daemon - everything else remains the same 2) Ubuntu 20.04 - Port rest of plugins to use com.canonical.unity.settings-daemon - u-s-d will still use org.gnome.settings-daemon name in dbus - Activation toggle key will now use com.canonical.unity.settings- daemon - Everything else will remain the same To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-session/+bug/1842324/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1842324] Re: Port schemas from gnome-settings-daemon-common to com.canonical.unity.settings-daemon
** Changed in: unity-control-center (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1842324 Title: Port schemas from gnome-settings-daemon-common to com.canonical.unity .settings-daemon Status in indicator-session package in Ubuntu: Fix Released Status in ubuntu-settings package in Ubuntu: Fix Released Status in unity package in Ubuntu: Fix Released Status in unity-control-center package in Ubuntu: Fix Released Status in unity-greeter package in Ubuntu: Fix Released Status in unity-settings-daemon package in Ubuntu: Fix Released Bug description: Unity-settings-daemon still depends on gnome-settings-daemon schemas. It is undesired as it requires to modify code in all unity related components when upstream drops some gsettings schemas. gnome-settings-daemon > 3.33 drops/modify media-keys schemas in an undesired way that it can't easily be reverted. Keyboard & mouse schemas are modified and unity-settings-daemon is crashing. So it's better unity uses it's own schema as suggested by Laney. We will of- course keep using settings migration (org.gnome.settings-daemon-> org.gnome.desktop) wherever possible. https://gitlab.gnome.org/GNOME/gnome-settings- daemon/commit/6dff93a0dfa80db3f481eed5d6ed689bf469aa1b https://gitlab.gnome.org/GNOME/gnome-settings- daemon/commit/44f53c64c5a2514d2c022bcb1596a9e46f1df51c https://gitlab.gnome.org/GNOME/gnome-settings- daemon/commit/121a6f89917898b8d05db2e1933dd0ad59c26768 Since this is a huge task it can be achieved gradually. 1) Ubuntu 19.10 - Port media keys to use com.canonical.unity.settings-daemon - u-s-d will still use org.gnome.settings-daemon name in dbus - u-s-d will still respects activation toggle in org.gnome.settings- daemon - everything else remains the same 2) Ubuntu 20.04 - Port rest of plugins to use com.canonical.unity.settings-daemon - u-s-d will still use org.gnome.settings-daemon name in dbus - Activation toggle key will now use com.canonical.unity.settings- daemon - Everything else will remain the same To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-session/+bug/1842324/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1842324] Re: Port schemas from gnome-settings-daemon-common to com.canonical.unity.settings-daemon
** Changed in: indicator-session (Ubuntu) Assignee: (unassigned) => Khurshid Alam (khurshid-alam) ** Also affects: ubuntu-settings (Ubuntu) Importance: Undecided Status: New ** Changed in: ubuntu-settings (Ubuntu) Assignee: (unassigned) => Khurshid Alam (khurshid-alam) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1842324 Title: Port schemas from gnome-settings-daemon-common to com.canonical.unity .settings-daemon Status in indicator-session package in Ubuntu: New Status in ubuntu-settings package in Ubuntu: New Status in unity package in Ubuntu: Confirmed Status in unity-control-center package in Ubuntu: Confirmed Status in unity-greeter package in Ubuntu: Confirmed Status in unity-settings-daemon package in Ubuntu: Confirmed Bug description: Unity-settings-daemon still depends on gnome-settings-daemon schemas. It is undesired as it requires to modify code in all unity related components when upstream drops some gsettings schemas. gnome-settings-daemon > 3.33 drops/modify media-keys schemas in an undesired way that it can't easily be reverted. Keyboard & mouse schemas are modified and unity-settings-daemon is crashing. So it's better unity uses it's own schema as suggested by Laney. We will of- course keep using settings migration (org.gnome.settings-daemon-> org.gnome.desktop) wherever possible. https://gitlab.gnome.org/GNOME/gnome-settings- daemon/commit/6dff93a0dfa80db3f481eed5d6ed689bf469aa1b https://gitlab.gnome.org/GNOME/gnome-settings- daemon/commit/44f53c64c5a2514d2c022bcb1596a9e46f1df51c https://gitlab.gnome.org/GNOME/gnome-settings- daemon/commit/121a6f89917898b8d05db2e1933dd0ad59c26768 Since this is a huge task it can be achieved gradually. 1) Ubuntu 19.10 - Port media keys to use com.canonical.unity.settings-daemon - u-s-d will still use org.gnome.settings-daemon name in dbus - u-s-d will still respects activation toggle in org.gnome.settings- daemon - everything else remains the same 2) Ubuntu 20.04 - Port rest of plugins to use com.canonical.unity.settings-daemon - u-s-d will still use org.gnome.settings-daemon name in dbus - Activation toggle key will now use com.canonical.unity.settings- daemon - Everything else will remain the same To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-session/+bug/1842324/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1831491] [NEW] Do not unset XDG_SEAT & XDG_SESSION_ID in 95dbus_update-activation-env (Unity7)
Public bug reported: Unity still requires it. For example indicator-session depends on those session environments. Without those set it doesn't behave properly. ** Affects: dbus (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: eoan ** Description changed: - Unity still requires it. Fir example indicator-session depends on those + Unity still requires it. For example indicator-session depends on those session environments. Without those set it doesn't behave properly. ** Changed in: dbus (Ubuntu) Status: New => Confirmed ** Summary changed: - Do not unset XDG_SEAT & XDG_SESSION_ID in 95dbus_update-activation-env + Do not unset XDG_SEAT & XDG_SESSION_ID in 95dbus_update-activation-env (Unity7) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus in Ubuntu. https://bugs.launchpad.net/bugs/1831491 Title: Do not unset XDG_SEAT & XDG_SESSION_ID in 95dbus_update-activation-env (Unity7) Status in dbus package in Ubuntu: Confirmed Bug description: Unity still requires it. For example indicator-session depends on those session environments. Without those set it doesn't behave properly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1831491/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1770674] Re: Please drop recommends on geoclue-ubuntu-geoip | geoclue-provider
It is now removed in eoan. ** Changed in: indicator-datetime (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-datetime in Ubuntu. https://bugs.launchpad.net/bugs/1770674 Title: Please drop recommends on geoclue-ubuntu-geoip | geoclue-provider Status in indicator-datetime package in Ubuntu: Fix Committed Bug description: Please drop the recommends on geoclue-ubuntu-geoip | geoclue-provider so that geoclue can be removed. I am not doing this myself since I haven't checked to see what functionality is lost by removing the recommended package. This issue is blocking the removal of libnm-glib4 (from network- manager-applet) from Ubuntu. The library has already been removed from Debian. See also LP: #1389336 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1770674/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1828725] Re: indicator-datetime does not have color squares for different calendars and dates from contacts (birthdays & anniversaries)
By "we" do you mean official ubuntu-mate team ? In that case, contact me on community.ubuntu.com. Indicator-datetime requires lots of changes including the upcoming api break from eds. Someone from community proposed to remove phone realted code and go back to c. Not sure if it is still possible. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-datetime in Ubuntu. https://bugs.launchpad.net/bugs/1828725 Title: indicator-datetime does not have color squares for different calendars and dates from contacts (birthdays & anniversaries) Status in indicator-datetime package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Install Ubuntu with `indicator-datetime` and `evolution` 2. Add event to *Personal* calendar (default color) 3. Add new calendar and name it for example *Work* (red color) 4. Create contact with two dates - birthday and anniversary (it is pink color) Expected results: * `indicator-datetime` show four coloured events as it was in Ubuntu 12.04 LTS (see screenshot - ubuntu-12-04.png) Actual results: * `indicator-datetime` show for event without color squares in the left of them (see screenshot - ubuntu-19-10.png) ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: indicator-datetime 15.10+19.10.20190507-0ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-14.15-generic 5.0.6 Uname: Linux 5.0.0-14-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: MATE Date: Sun May 12 14:54:43 2019 InstallationDate: Installed on 2019-04-28 (13 days ago) InstallationMedia: Ubuntu-MATE 19.10 "Eoan EANIMAL" - Alpha amd64 (20190426) SourcePackage: indicator-datetime UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1828725/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1828725] Re: indicator-datetime does not have color squares for different calendars and dates from contacts (birthdays & anniversaries)
Why this is relevant in 19.10 ? Trusty already had eol. Indicator-datetime was ported from C to C++ (r: 298) to work with unity-8 and that feature gone missing with that. But there is no unity-8 anymore and the code doesn't work. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1828725 Title: indicator-datetime does not have color squares for different calendars and dates from contacts (birthdays & anniversaries) Status in evolution-data-server package in Ubuntu: New Status in indicator-datetime package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Install Ubuntu with `indicator-datetime` and `evolution` 2. Add event to *Personal* calendar (default color) 3. Add new calendar and name it for example *Work* (red color) 4. Create contact with two dates - birthday and anniversary (it is pink color) Expected results: * `indicator-datetime` show four coloured events as it was in Ubuntu 12.04 LTS (see screenshot - ubuntu-12-04.png) Actual results: * `indicator-datetime` show for event without color squares in the left of them (see screenshot - ubuntu-19-10.png) ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: indicator-datetime 15.10+19.10.20190507-0ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-14.15-generic 5.0.6 Uname: Linux 5.0.0-14-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: MATE Date: Sun May 12 14:54:43 2019 InstallationDate: Installed on 2019-04-28 (13 days ago) InstallationMedia: Ubuntu-MATE 19.10 "Eoan EANIMAL" - Alpha amd64 (20190426) SourcePackage: indicator-datetime UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1828725/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1823550] Re: GtkSourceView wrongly has monospaced font in dropdown (context) menu
In lp: #1242984 light theme is already using (see
https://code.launchpad.net/~larsu/ubuntu-themes/gedit-
fixes/+merge/201212)
.context-menu { font: regular medium;}
not sure why it is not working. May be it needs to use font-family. So
changing it in ~/.config/gtk-3.0/gtk.css works for me.
.context-menu {
font-weight: medium;
font-family: regular;
}
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1823550
Title:
GtkSourceView wrongly has monospaced font in dropdown (context) menu
Status in GtkSourceView:
Fix Released
Status in gtk+3.0 package in Ubuntu:
Invalid
Status in gtksourceview3 package in Ubuntu:
Invalid
Status in mate-themes package in Ubuntu:
Confirmed
Status in pluma package in Ubuntu:
Invalid
Status in ubuntu-themes package in Ubuntu:
Confirmed
Bug description:
Steps to reproduce:
1. Have Ubuntu 17.04 or later installed
2. Open any application with GtkSourceView component - such as Pluma, Gedit,
Giggle, Gitg, gnome-builder and maybe others (see complete list with `apt-cache
rdepends libgtksourceview-3.0-1`)
3. Click right mouse button on text zone
Expected result:
* dropdown menu has normal font as all other interface elements
Actual result:
* dropdwon menu wrongly has monospaced font
Notes:
* first seen in 17.04, but persists in 17.10, 18.04 LTS, 18.10, 19.04
releases.
* seems to be caused by GTK3 library
ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: pluma 1.18.1-0ubuntu1
ProcVersionSignature: Ubuntu 4.10.0-42.46-generic 4.10.17
Uname: Linux 4.10.0-42-generic x86_64
ApportVersion: 2.20.4-0ubuntu4.10
Architecture: amd64
CurrentDesktop: MATE
Date: Sun Apr 7 20:13:24 2019
InstallationDate: Installed on 2018-08-07 (243 days ago)
InstallationMedia: Ubuntu-MATE 16.04.3 LTS "Xenial Xerus" - Release amd64
(20170801)
SourcePackage: pluma
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/gtksourceview/+bug/1823550/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1811596] Re: Ubuntu Single Sign-On GUI not showing login button
** Also affects: gnome-online-accounts (Ubuntu) Importance: Undecided Status: New ** Changed in: unity-control-center (Ubuntu) Status: Confirmed => Invalid ** Changed in: gnome-online-accounts (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1811596 Title: Ubuntu Single Sign-On GUI not showing login button Status in gnome-online-accounts package in Ubuntu: Confirmed Status in unity-control-center package in Ubuntu: Invalid Bug description: System Settings->Online Accounts->Ubuntu Single Sign-On I can enter my email address and password abd select "I have an Ubuntu Single Sign-On account". But there is no "Save" or "Login" or any other button. I can only close the window. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1811596/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1823550] Re: GtkSourceView wrongly has monospaced font in dropdown (context) menu
@Norbert No, I actually wanted you to change the font from gedit preference. For example select purisha oblique. Reset geit pref. Install tweak-tool. Try changing monospace font. It will change both context menu and soureview font. But I think you are right by default it is set to monospace font. But you can force it to use other fonts. And yes this can be set in the theme too. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1823550 Title: GtkSourceView wrongly has monospaced font in dropdown (context) menu Status in GtkSourceView: Fix Released Status in gtk+3.0 package in Ubuntu: Invalid Status in gtksourceview3 package in Ubuntu: Invalid Status in mate-themes package in Ubuntu: Confirmed Status in pluma package in Ubuntu: Invalid Status in ubuntu-themes package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Have Ubuntu 17.04 or later installed 2. Open any application with GtkSourceView component - such as Pluma, Gedit, Giggle, Gitg, gnome-builder and maybe others (see complete list with `apt-cache rdepends libgtksourceview-3.0-1`) 3. Click right mouse button on text zone Expected result: * dropdown menu has normal font as all other interface elements Actual result: * dropdwon menu wrongly has monospaced font Notes: * first seen in 17.04, but persists in 17.10, 18.04 LTS, 18.10, 19.04 releases. * seems to be caused by GTK3 library ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: pluma 1.18.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-42.46-generic 4.10.17 Uname: Linux 4.10.0-42-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.10 Architecture: amd64 CurrentDesktop: MATE Date: Sun Apr 7 20:13:24 2019 InstallationDate: Installed on 2018-08-07 (243 days ago) InstallationMedia: Ubuntu-MATE 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) SourcePackage: pluma UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gtksourceview/+bug/1823550/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1823550] Re: GtkSourceView wrongly has monospaced font in dropdown (context) menu
Did you try changing font by de-selecting "use system fixed width font" ? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1823550 Title: GtkSourceView wrongly has monospaced font in dropdown (context) menu Status in GtkSourceView: Fix Released Status in gtk+3.0 package in Ubuntu: Invalid Status in gtksourceview3 package in Ubuntu: Invalid Status in mate-themes package in Ubuntu: New Status in pluma package in Ubuntu: Invalid Status in ubuntu-themes package in Ubuntu: New Bug description: Steps to reproduce: 1. Have Ubuntu 17.04 or later installed 2. Open any application with GtkSourceView component - such as Pluma, Gedit, Giggle, Gitg, gnome-builder and maybe others (see complete list with `apt-cache rdepends libgtksourceview-3.0-1`) 3. Click right mouse button on text zone Expected result: * dropdown menu has normal font as all other interface elements Actual result: * dropdwon menu wrongly has monospaced font Notes: * first seen in 17.04, but persists in 17.10, 18.04 LTS, 18.10, 19.04 releases. * seems to be caused by GTK3 library ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: pluma 1.18.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-42.46-generic 4.10.17 Uname: Linux 4.10.0-42-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.10 Architecture: amd64 CurrentDesktop: MATE Date: Sun Apr 7 20:13:24 2019 InstallationDate: Installed on 2018-08-07 (243 days ago) InstallationMedia: Ubuntu-MATE 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) SourcePackage: pluma UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gtksourceview/+bug/1823550/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1814506] Re: Use nemo-desktop to draw desktop icons under Unity (Disco)
@Amr Ah, No. In users eye nemo won't even exist in Unity. We are only using nemo-desktop which is a separate binary to draw icons under unity, nothing else. It's difficult to remove nautilus completely as it is burried deep. It requires work on unity, unity-lens-files, hud, bamf, zeitgeist and in indicators. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1814506 Title: Use nemo-desktop to draw desktop icons under Unity (Disco) Status in ubuntu-settings package in Ubuntu: New Status in ubuntu-themes package in Ubuntu: Fix Released Status in unity package in Ubuntu: Fix Released Bug description: As nautilus > 3.30 is now uploaded in Ubuntu 19.10, it doesn't have the desktop any more. The alternate options are to use caja-desktop or nemo-desktop keeping nautilus default file manger for now. Since nemo- desktop does not require any extensive patching it is easy to use under unity. Nemo-desktop will only draw the icons, not the background. In absence of nautilus unity-settings-daemon draws the background, so nothing to do in u-s-d. There are few small patches (nemo action files) required from nemo. @fossfreedom (ubuntu-budgie-dev) suggested that it's better that we ship these action files ourselves as recommended by upstream. Budgie is doing the same. https://github.com/UbuntuBudgie/budgie-desktop-environment/tree/master/nemo-actions Since nautilus still be default file-manager we disable auto-mount with nemo and various other cinnamon/nemo option in ubuntu-settings.gsettings-override To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/1814506/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1814506] Re: Use nemo-desktop to draw desktop icons under Unity (Disco)
** Merge proposal linked: https://code.launchpad.net/~khurshid-alam/ubuntu/+source/gnome-session/+git/gnome-session/+merge/363153 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1814506 Title: Use nemo-desktop to draw desktop icons under Unity (Disco) Status in ubuntu-settings package in Ubuntu: New Status in ubuntu-themes package in Ubuntu: Fix Released Status in unity package in Ubuntu: Fix Released Bug description: As nautilus > 3.30 is now uploaded in Ubuntu 19.10, it doesn't have the desktop any more. The alternate options are to use caja-desktop or nemo-desktop keeping nautilus default file manger for now. Since nemo- desktop does not require any extensive patching it is easy to use under unity. Nemo-desktop will only draw the icons, not the background. In absence of nautilus unity-settings-daemon draws the background, so nothing to do in u-s-d. There are few small patches (nemo action files) required from nemo. @fossfreedom (ubuntu-budgie-dev) suggested that it's better that we ship these action files ourselves as recommended by upstream. Budgie is doing the same. https://github.com/UbuntuBudgie/budgie-desktop-environment/tree/master/nemo-actions Since nautilus still be default file-manager we disable auto-mount with nemo and various other cinnamon/nemo option in ubuntu-settings.gsettings-override To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/1814506/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1814506] Re: Use nemo-desktop to draw desktop icons under Unity (Disco)
** Merge proposal unlinked: https://code.launchpad.net/~khurshid-alam/ubuntu/+source/ubuntu-settings/+git/ubuntu-settings/+merge/362989 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1814506 Title: Use nemo-desktop to draw desktop icons under Unity (Disco) Status in ubuntu-settings package in Ubuntu: New Status in ubuntu-themes package in Ubuntu: New Status in unity package in Ubuntu: Fix Released Bug description: As nautilus > 3.30 is now uploaded in Ubuntu 19.10, it doesn't have the desktop any more. The alternate options are to use caja-desktop or nemo-desktop keeping nautilus default file manger for now. Since nemo- desktop does not require any extensive patching it is easy to use under unity. Nemo-desktop will only draw the icons, not the background. In absence of nautilus unity-settings-daemon draws the background, so nothing to do in u-s-d. There are few small patches (nemo action files) required from nemo. @fossfreedom (ubuntu-budgie-dev) suggested that it's better that we ship these action files ourselves as recommended by upstream. Budgie is doing the same. https://github.com/UbuntuBudgie/budgie-desktop-environment/tree/master/nemo-actions Since nautilus still be default file-manager we disable auto-mount with nemo and various other cinnamon/nemo option in ubuntu-settings.gsettings-override To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/1814506/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1815479] Re: Don't use headerbar for gnome-terminal under Unity (Disco)
** Changed in: ubuntu-settings (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1815479 Title: Don't use headerbar for gnome-terminal under Unity (Disco) Status in ubuntu-settings package in Ubuntu: Confirmed Bug description: Terminal now has a headerbar but unity already uses gtk3-nocsd which draws ssd titebar on top of headerbar and this breaks styles for Ambiance/Radiance. Terminal already has a gsettings key for disabling headerbar. Use that instead. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/1815479/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1815479] [NEW] Don't use headerbar for gnome-terminal under Unity (Disco)
Public bug reported: Terminal now has a headerbar but unity already uses gtk3-nocsd which draws ssd titebar on top of headerbar and this breaks styles for Ambiance/Radiance. Terminal already has a gsettings key for disabling headerbar. Use that instead. ** Affects: ubuntu-settings (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1815479 Title: Don't use headerbar for gnome-terminal under Unity (Disco) Status in ubuntu-settings package in Ubuntu: New Bug description: Terminal now has a headerbar but unity already uses gtk3-nocsd which draws ssd titebar on top of headerbar and this breaks styles for Ambiance/Radiance. Terminal already has a gsettings key for disabling headerbar. Use that instead. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/1815479/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1815094] Re: [FTBFS] cast between incompatible function types from ‘bool (*)(nux::TextEntry*)’ to ‘GSourceFunc’ gcc >= 8.1 (Disco)
** Changed in: nux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to nux in Ubuntu. https://bugs.launchpad.net/bugs/1815094 Title: [FTBFS] cast between incompatible function types from ‘bool (*)(nux::TextEntry*)’ to ‘GSourceFunc’ gcc >= 8.1 (Disco) Status in nux package in Ubuntu: Confirmed Bug description: In disco it doesn't compile. I get cast between incompatible function types from ‘bool (*)(nux::TextEntry*)’ to ‘GSourceFunc’ Either we should build it with -Wextra -Wno-cast-function-type in configure.ac or fix pointer to function for g++ > 8.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nux/+bug/1815094/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1815094] [NEW] [FTBFS] cast between incompatible function types from ‘bool (*)(nux::TextEntry*)’ to ‘GSourceFunc’ gcc >= 8.1 (Disco)
Public bug reported: In disco it doesn't compile. I get cast between incompatible function types from ‘bool (*)(nux::TextEntry*)’ to ‘GSourceFunc’ Either we should build it with -Wextra -Wno-cast-function-type in configure.ac or fix pointer to function for g++ > 8.1 ** Affects: nux (Ubuntu) Importance: Undecided Status: New ** Tags: disco -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to nux in Ubuntu. https://bugs.launchpad.net/bugs/1815094 Title: [FTBFS] cast between incompatible function types from ‘bool (*)(nux::TextEntry*)’ to ‘GSourceFunc’ gcc >= 8.1 (Disco) Status in nux package in Ubuntu: New Bug description: In disco it doesn't compile. I get cast between incompatible function types from ‘bool (*)(nux::TextEntry*)’ to ‘GSourceFunc’ Either we should build it with -Wextra -Wno-cast-function-type in configure.ac or fix pointer to function for g++ > 8.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nux/+bug/1815094/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1814933] [NEW] Ambiance/Radiance: path-bar is broken with nautilus > 3.30
Public bug reported: Nautilus 3.30 has new path-bar. And hence it doesn't look good with current design. I had several ideas to solve the problem. Hence opened a discussion thread in community hub to get opinions from developers and users. See: I will open a merge once this gets finalized. ** Affects: ubuntu-themes (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1814933 Title: Ambiance/Radiance: path-bar is broken with nautilus > 3.30 Status in ubuntu-themes package in Ubuntu: New Bug description: Nautilus 3.30 has new path-bar. And hence it doesn't look good with current design. I had several ideas to solve the problem. Hence opened a discussion thread in community hub to get opinions from developers and users. See: I will open a merge once this gets finalized. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1814933/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1814506] Re: Use nemo-desktop to draw desktop icons under Unity (Disco)
** Also affects: ubuntu-settings (Ubuntu) Importance: Undecided Status: New ** Also affects: ubuntu-themes (Ubuntu) Importance: Undecided Status: New ** Branch linked: lp:~khurshid-alam/ubuntu-themes/nemo-desktop -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1814506 Title: Use nemo-desktop to draw desktop icons under Unity (Disco) Status in ubuntu-settings package in Ubuntu: New Status in ubuntu-themes package in Ubuntu: New Status in unity package in Ubuntu: New Bug description: As nautilus > 3.30 is now uploaded in Ubuntu 19.10, it doesn't have the desktop any more. The alternate options are to use caja-desktop or nemo-desktop keeping nautilus default file manger for now. Since nemo- desktop does not require any extensive patching it is easy to use under unity. Nemo-desktop will only draw the icons, not the background. In absence of nautilus unity-settings-daemon draws the background, so nothing to do in u-s-d. There are few small patches (nemo action files) required from nemo. @fossfreedom (ubuntu-budgie-dev) suggested that it's better that we ship these action files ourselves as recommended by upstream. Budgie is doing the same. https://github.com/UbuntuBudgie/budgie-desktop-environment/tree/master/nemo-actions Since nautilus still be default file-manager we disable auto-mount with nemo and various other cinnamon/nemo option in ubuntu-settings.gsettings-override To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/1814506/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1735998] Re: [Needs-Packaging]Decouple unity related settings as unity-settings
** Summary changed: - Decouple unity related settings as unity-settings + [Needs-Packaging]Decouple unity related settings as unity-settings -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1735998 Title: [Needs-Packaging]Decouple unity related settings as unity-settings Status in ubuntu-settings package in Ubuntu: Confirmed Bug description: This is an attempt to resolve "* Shared GSettings keys" issue listed under https://wiki.ubuntu.com/Unity/NotDefaultIssues. Ubuntu so far is providing session related overrides for both ubuntu & unity sessions in a single package, i.e. ubuntu-settings. But now that Unity is not the default desktop it doesn't make any sense to carry unity related overrides in ubuntu-settings. For this purpose I have created a new project: unity-settings (https://code.launchpad.net/~khurshid-alam/unity-settings/trunk) and the binary would be unity-settings in universe. To make this happen in under 18.04 cycle, the work-flow should be: 1) Have unity-settings in the universe 2) Have ubuntu-unity-desktop in the universe 3) Let ubuntu-unity-desktop depends on unity-settings 4) Drop unity related settings in ubuntu-settings (merge request in-progress) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/1735998/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1812904] [NEW] [FTBFS] Doesn't compile with gtk-doc >=1.26 (Disco)
Public bug reported: Gtkdoc-mktmpl was removed from gtk-doc 1.26. Instead use GtkDocConfig.cmake provided by gtk-doc-tools. See: https://github.com/GNOME/gtk- doc/commit/46df4354abed5724697fd5e39630c5bbc6637cc4#diff- 6023128f8e440b483f85968b0db7799e ** Affects: hud (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: disco ** Changed in: hud (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to hud in Ubuntu. https://bugs.launchpad.net/bugs/1812904 Title: [FTBFS] Doesn't compile with gtk-doc >=1.26 (Disco) Status in hud package in Ubuntu: Confirmed Bug description: Gtkdoc-mktmpl was removed from gtk-doc 1.26. Instead use GtkDocConfig.cmake provided by gtk-doc-tools. See: https://github.com/GNOME/gtk- doc/commit/46df4354abed5724697fd5e39630c5bbc6637cc4#diff- 6023128f8e440b483f85968b0db7799e To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hud/+bug/1812904/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1808671] Re: Drop non working scopes
** Package changed: unity (Ubuntu) => libunity (Ubuntu) ** Changed in: libunity (Ubuntu) Status: New => Confirmed ** Branch linked: lp:~khurshid-alam/libunity/remove-deprecated-scopes -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libunity in Ubuntu. https://bugs.launchpad.net/bugs/1808671 Title: Drop non working scopes Status in libunity package in Ubuntu: Confirmed Bug description: Many online scopes and lenses are not working anymore. So drop them from recommends. And tomboy is going to be removed from debian so use gnote instead of tomboy. unity-gnote-scope: https://launchpad.net/unity-scope-gnote To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libunity/+bug/1808671/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1801148] Re: package gir1.2-unity-5.0:amd64 7.1.4+15.10.20151002-0ubuntu2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before
You should try to re-install the package. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libunity in Ubuntu. https://bugs.launchpad.net/bugs/1801148 Title: package gir1.2-unity-5.0:amd64 7.1.4+15.10.20151002-0ubuntu2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in libunity package in Ubuntu: New Bug description: Unable to open skype ProblemType: Package DistroRelease: Ubuntu 16.04 Package: gir1.2-unity-5.0:amd64 7.1.4+15.10.20151002-0ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-94.117-generic 4.4.83 Uname: Linux 4.4.0-94-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 AptOrdering: gir1.2-unity-5.0: Configure upower: Configure NULL: ConfigurePending Architecture: amd64 Date: Thu Nov 1 13:11:35 2018 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2018-10-31 (1 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.29 SourcePackage: libunity Title: package gir1.2-unity-5.0:amd64 7.1.4+15.10.20151002-0ubuntu2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libunity/+bug/1801148/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1805418] [NEW] Update pre-populator patch with correct desktop names
Public bug reported: Use correct desktop names for totem, gedit and gnome-calculator. ** Affects: zeitgeist (Ubuntu) Importance: Undecided Status: Confirmed ** Patch added: "A small patch to fix pre-populator patch" https://bugs.launchpad.net/bugs/1805418/+attachment/5216774/+files/pre_populator-fix.patch ** Changed in: zeitgeist (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to zeitgeist in Ubuntu. https://bugs.launchpad.net/bugs/1805418 Title: Update pre-populator patch with correct desktop names Status in zeitgeist package in Ubuntu: Confirmed Bug description: Use correct desktop names for totem, gedit and gnome-calculator. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zeitgeist/+bug/1805418/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1732612] Re: Alt+Printscreen not working (doesn't generate keypress event)
This will be fixed soon. See https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1188569/comments/18 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1732612 Title: Alt+Printscreen not working (doesn't generate keypress event) Status in systemd package in Ubuntu: Confirmed Status in unity package in Ubuntu: Confirmed Bug description: Since I have upgraded to Ubuntu 17.10 Alt+PrintScreen doesn't work on my computer. I'm using Unity DE, with default settings. The problem is not about taking screnshots. xev recognizes when I press down the alt key, but nothing happens when I press Print Screen with alt being pressed (it does when PrintScreen is pressed by itself) Here is evtest output when I press Alt+Printscreen: # Alt pressed down: Event: time 1510817663.883489, -- SYN_REPORT Event: time 1510817663.923476, type 1 (EV_KEY), code 56 (KEY_LEFTALT), value 2 Event: time 1510817663.923476, -- SYN_REPORT Event: time 1510817663.963479, type 1 (EV_KEY), code 56 (KEY_LEFTALT), value 2 Event: time 1510817663.963479, -- SYN_REPORT Event: time 1510817663.993036, type 4 (EV_MSC), code 4 (MSC_SCAN), value 70046 # Print screen pressed Event: time 1510817663.993036, -- SYN_REPORT Event: time 1510817664.945032, type 1 (EV_KEY), code 56 (KEY_LEFTALT), value 0 # Alt released Event: time 1510817664.945032, -- SYN_REPORT Event: time 1510817664.945086, type 1 (EV_KEY), code 56 (KEY_LEFTALT), value 1 Event: time 1510817664.945086, type 1 (EV_KEY), code 99 (KEY_SYSRQ), value 1 Event: time 1510817664.945086, -- SYN_REPORT Event: time 1510817664.945097, type 1 (EV_KEY), code 99 (KEY_SYSRQ), value 0 Event: time 1510817664.945097, type 1 (EV_KEY), code 56 (KEY_LEFTALT), value 0 Event: time 1510817664.945097, -- SYN_REPORT ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: udev 234-2ubuntu12.1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu CustomUdevRuleFiles: 67-xorg-wizardpen.rules 99-displaylink.rules 60-vboxdrv.rules 70-snap.core.rules 99-anbox.rules Date: Thu Nov 16 08:29:46 2017 InstallationDate: Installed on 2017-03-26 (234 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170321) MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: Upgraded to artful on 2017-10-23 (23 days ago) dmi.bios.date: 10/24/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F1 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z77-HD3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF1:bd10/24/2012:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ77-HD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1732612/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1415840] Re: Chromium People menu does not work with the HUD
Can't reproduce this on Ubuntu 18.04. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to hud in Ubuntu. https://bugs.launchpad.net/bugs/1415840 Title: Chromium People menu does not work with the HUD Status in hud package in Ubuntu: New Bug description: I have two Chromium users. Their names appear on the HUD when I type the first letters, but hitting enter has no effect. The two other commands on the "People" menu (Edit... and Add person...) are also ineffective via the HUD. I have to use the mouse to execute these commands. I have tested many other commands from the other menus (File, Edit, View, History, Tools and Help) and they work. It seems the problem is exclusive to the People menu. This is an Ubuntu 14.10 desktop. It was upgraded from 14.04. The bug also manifests on my Ubuntu 14.10 notebook, which also was upgraded from 14.04. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: chromium-browser 39.0.2171.65-0ubuntu0.14.10.1.1106 ProcVersionSignature: Ubuntu 3.16.0-29.39-generic 3.16.7-ckt2 Uname: Linux 3.16.0-29-generic x86_64 ApportVersion: 2.14.7-0ubuntu8.1 Architecture: amd64 CurrentDesktop: Unity Date: Thu Jan 29 08:02:03 2015 SourcePackage: chromium-browser UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.chromium.browser: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hud/+bug/1415840/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1795635] Re: Drop transitional dummy packages for qtquick2 and qttest
** Branch linked: lp:~khurshid-alam/unity-api/fix-build-cosmic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-api in Ubuntu. https://bugs.launchpad.net/bugs/1795635 Title: Drop transitional dummy packages for qtquick2 and qttest Status in unity-api package in Ubuntu: Triaged Bug description: qtdeclarative5-qtquick2-plugin and qtdeclarative5-test-plugin are just transitional dummy packages. Instead use qml-module-qtquick2 and qml- module-qttest To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-api/+bug/1795635/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1795635] [NEW] Drop transitional dummy packages for qtquick2 and qttest
Public bug reported: qtdeclarative5-qtquick2-plugin and qtdeclarative5-test-plugin are just transitional dummy packages. Instead use qml-module-qtquick2 and qml- module-qttest ** Affects: unity-api (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: cosmic ** Changed in: unity-api (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-api in Ubuntu. https://bugs.launchpad.net/bugs/1795635 Title: Drop transitional dummy packages for qtquick2 and qttest Status in unity-api package in Ubuntu: Confirmed Bug description: qtdeclarative5-qtquick2-plugin and qtdeclarative5-test-plugin are just transitional dummy packages. Instead use qml-module-qtquick2 and qml- module-qttest To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-api/+bug/1795635/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1708375] Re: Add support for purple-telegram (telepathy-haze)
I have updated the patch with required changes. Thanks.
** Patch added: "telepathy-purple.patch"
https://bugs.launchpad.net/ubuntu/+source/telepathy-mission-control-5/+bug/1708375/+attachment/5195357/+files/telepathy-purple.patch
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to telepathy-mission-
control-5 in Ubuntu.
https://bugs.launchpad.net/bugs/1708375
Title:
Add support for purple-telegram (telepathy-haze)
Status in telepathy-mission-control-5 package in Ubuntu:
Confirmed
Bug description:
When using purple telegram through telepathy-haze, it requires
following permissions:
# for purple telegram
/etc/telegram-purple/server.tglpub r,
/usr/lib/purple-2*/ r,
/usr/lib/purple-2/*.somr,
/usr/share/locale/*/LC_MESSAGES/*.mo r,
/usr/share/pixmaps/pidgin/protocols/{16,32,48}/*.png r,
@{HOME}/.purple/telegram-purple/** rw,
@{HOME}/.telegram-purple/** rw,
under /usr/lib/telepathy/telepathy-* section. See issue
https://github.com/majn/telegram-purple/issues/346 for more details.
I have attached the necessary patch
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/telepathy-mission-control-5/+bug/1708375/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1708375] Re: Add support for purple-telegram (telepathy-haze)
Updated the patch as quilt patch
** Patch added: "telepathy-purple.patch"
https://bugs.launchpad.net/ubuntu/+source/telepathy-mission-control-5/+bug/1708375/+attachment/5195339/+files/telepathy-purple.patch
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to telepathy-mission-
control-5 in Ubuntu.
https://bugs.launchpad.net/bugs/1708375
Title:
Add support for purple-telegram (telepathy-haze)
Status in telepathy-mission-control-5 package in Ubuntu:
Confirmed
Bug description:
When using purple telegram through telepathy-haze, it requires
following permissions:
# for purple telegram
/etc/telegram-purple/server.tglpub r,
/usr/lib/purple-2*/ r,
/usr/lib/purple-2/*.somr,
/usr/share/locale/*/LC_MESSAGES/*.mo r,
/usr/share/pixmaps/pidgin/protocols/{16,32,48}/*.png r,
@{HOME}/.purple/telegram-purple/** rw,
@{HOME}/.telegram-purple/** rw,
under /usr/lib/telepathy/telepathy-* section. See issue
https://github.com/majn/telegram-purple/issues/346 for more details.
I have attached the necessary patch
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/telepathy-mission-control-5/+bug/1708375/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1795412] Re: Allow read access to /usr/share/unity/themes/ for telepathy-haze
telepathy-haze-fix.patch ** Patch added: "tellepathy-haze-fix.patch" https://bugs.launchpad.net/ubuntu/+source/telepathy-mission-control-5/+bug/1795412/+attachment/5195338/+files/tellepathy-haze-fix.patch ** Changed in: telepathy-mission-control-5 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to telepathy-mission- control-5 in Ubuntu. https://bugs.launchpad.net/bugs/1795412 Title: Allow read access to /usr/share/unity/themes/ for telepathy-haze Status in telepathy-mission-control-5 package in Ubuntu: Confirmed Bug description: When You open empathy with a active telepathy-haze connection, syslog reports, Oct 1 03:05:57 cosmic-dev kernel: [ 192.196337] audit: type=1400 audit(1538343357.649:34): apparmor="DENIED" operation="open" profile="/usr/lib/telepathy/telepathy-*" name="/usr/share/unity/themes/" pid=1696 comm="telepathy-haze" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 though it is not critical, it doesn't hurt give telepathy-haze read access to that folder. I can't open merge request since I can't find lp:telepathy-mission- control-5, I am attaching a quilt patch here. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/telepathy-mission-control-5/+bug/1795412/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1795412] [NEW] Allow read access to /usr/share/unity/themes/ for telepathy-haze
Public bug reported: When You open empathy with a active telepathy-haze connection, syslog reports, Oct 1 03:05:57 cosmic-dev kernel: [ 192.196337] audit: type=1400 audit(1538343357.649:34): apparmor="DENIED" operation="open" profile="/usr/lib/telepathy/telepathy-*" name="/usr/share/unity/themes/" pid=1696 comm="telepathy-haze" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 though it is not critical, it doesn't hurt give telepathy-haze read access to that folder. I can't open merge request since I can't find lp:telepathy-mission- control-5, I am attaching a quilt patch here. ** Affects: telepathy-mission-control-5 (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: cosmic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to telepathy-mission- control-5 in Ubuntu. https://bugs.launchpad.net/bugs/1795412 Title: Allow read access to /usr/share/unity/themes/ for telepathy-haze Status in telepathy-mission-control-5 package in Ubuntu: Confirmed Bug description: When You open empathy with a active telepathy-haze connection, syslog reports, Oct 1 03:05:57 cosmic-dev kernel: [ 192.196337] audit: type=1400 audit(1538343357.649:34): apparmor="DENIED" operation="open" profile="/usr/lib/telepathy/telepathy-*" name="/usr/share/unity/themes/" pid=1696 comm="telepathy-haze" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 though it is not critical, it doesn't hurt give telepathy-haze read access to that folder. I can't open merge request since I can't find lp:telepathy-mission- control-5, I am attaching a quilt patch here. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/telepathy-mission-control-5/+bug/1795412/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1773045] Re: Radiance/gtk-3.20/gtk-main.css attempts to import nonexistent gnome-builder.css
** Changed in: ubuntu-themes (Ubuntu)
Assignee: (unassigned) => Khurshid Alam (khurshid-alam)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu.
https://bugs.launchpad.net/bugs/1773045
Title:
Radiance/gtk-3.20/gtk-main.css attempts to import nonexistent gnome-
builder.css
Status in Ubuntu theme:
Confirmed
Status in ubuntu-themes package in Ubuntu:
Confirmed
Bug description:
The file /usr/share/themes/Radiance/gtk-3.20/gtk-main.css contains the
line
@import url("apps/gnome-builder.css");
But this file does not exist in this package or any other, as far as I
can tell from apt-file. This triggers an annoying warning when
running various applications (e.g. evince):
(evince:12714): Gtk-WARNING **: 18:41:45.136: Theme parsing error:
gtk-main.css:73:38: Failed to import: Error opening file
/usr/share/themes/Radiance/gtk-3.20/apps/gnome-builder.css: No such
file or directory
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: light-themes 16.10+18.04.20180421.1-0ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
Uname: Linux 4.15.0-22-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
Date: Wed May 23 18:58:41 2018
PackageArchitecture: all
SourcePackage: ubuntu-themes
UpgradeStatus: Upgraded to bionic on 2018-05-23 (1 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-themes/+bug/1773045/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1579580] Re: ureadahead reports relative path errors in journalctl output
ureadahead has been already removed from cosmic. If you don't need it, just remove the package. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ureadahead in Ubuntu. https://bugs.launchpad.net/bugs/1579580 Title: ureadahead reports relative path errors in journalctl output Status in ureadahead package in Ubuntu: Confirmed Bug description: ureadahead reports relative path errors in my journalctl output. This is currently 4368 lines of useless annoyances in my logs. To see if you have this problem, run: journalctl -b | grep ureadahead | grep relative | wc -l Thanks ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ureadahead 0.100.0-19 ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 Date: Sun May 8 15:55:18 2016 InstallationDate: Installed on 2016-04-04 (34 days ago) InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Beta amd64 (20160325) ProcEnviron: TERM=linux PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ureadahead UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ureadahead/+bug/1579580/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1772798] Re: Unity: Force start background plugin
*** This bug is a duplicate of bug 1795145 *** https://bugs.launchpad.net/bugs/1795145 Right. ** This bug has been marked a duplicate of bug 1795145 Turn on background plugin by default (Ubuntu 18.10) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1772798 Title: Unity: Force start background plugin Status in ubuntu-settings package in Ubuntu: Confirmed Bug description: If a user, already running a Gnome session upgrades or install unity by installing unity-session, background plugin doesn't start automatically (with u-s-d). This plugin has been removed from gnome- settings-daemon (Ubuntu carries a patch which only adds back the schema) and since gsd doesn't use it, it gets turned off. The background plugin is necessary to sync background related settings (wallpaper, sound, messages) with unity-greeter. If it doesn't start with u-s-d, changing wallpaper will not change the background of unity-greeter. The change was introduced in https://bazaar.launchpad.net/~unity- settings-daemon-team/unity-settings-daemon/trunk/revision/4179 This can be done in gsettings-override (In unity specific section) [org.gnome.settings-daemon.plugins.background:Unity] active = true Merge should happen against https://code.launchpad.net/~ubuntu- desktop/+junk/ubuntu-settings Since it's a +junk, I can't request merge proposals. I am also attaching the diff here. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/1772798/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1795145] Re: Turn on background plugin by default (Ubuntu 18.10)
** Changed in: ubuntu-settings (Ubuntu) Assignee: (unassigned) => Khurshid Alam (khurshid-alam) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1795145 Title: Turn on background plugin by default (Ubuntu 18.10) Status in ubuntu-settings package in Ubuntu: Confirmed Bug description: In https://git.launchpad.net/~ubuntu-desktop/ubuntu/+source/ubuntu- settings/tree/debian/ubuntu-settings.gsettings-override#n139 we have, [org.gnome.settings-daemon.plugins.background:ubuntu] active = false which disables the plugin. Gnome-settings-daemon doesn't use that key anymore (They are auto started by desktop files), But unity-settings- daemon now requires it to be enabled by default due to recent changes in lightdm and u-s-d Lightdm now use AccountsService extension system for extended greeter information (like wallpaper) used by unity-greeter (https://github.com/CanonicalLtd/lightdm/commit/6015bce25f241e7580c03594d846769f8236232f) And unity-settings-daemon now depends on new AccountsService method of setting background file for unity greeter. (https://bazaar.launchpad.net/~unity-settings-daemon-team/unity- settings-daemon/trunk/revision/4179) How-to-reproduce: -- 1) First disable the background plugin if it is already enabled. gsettings set org.gnome.settings-daemon.plugins.sharing active false 2) Change the wallpaper from unity-control-center. 3) Log out. Unity-greeter should reflect the change of wallpaper. But it doesn't. 4) Re-enable the background plugin. gsettings set org.gnome.settings-daemon.plugins.sharing active true 5) Change the wallpaper again and then log out. Unity-greeter now reflects the change in wallpaper properly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/1795145/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1795145] Re: Turn on background plugin by default (Ubuntu 18.10)
It got disabled in in https://launchpad.net/ubuntu/+source/ubuntu- settings/12.10.7. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1795145 Title: Turn on background plugin by default (Ubuntu 18.10) Status in ubuntu-settings package in Ubuntu: New Bug description: In https://git.launchpad.net/~ubuntu-desktop/ubuntu/+source/ubuntu- settings/tree/debian/ubuntu-settings.gsettings-override#n139 we have, [org.gnome.settings-daemon.plugins.background:ubuntu] active = false which disables the plugin. Gnome-settings-daemon doesn't use that key anymore (They are auto started by desktop files), But unity-settings- daemon now requires it to be enabled by default due to recent changes in lightdm and u-s-d Lightdm now use AccountsService extension system for extended greeter information (like wallpaper) used by unity-greeter (https://github.com/CanonicalLtd/lightdm/commit/6015bce25f241e7580c03594d846769f8236232f) And unity-settings-daemon now depends on new AccountsService method of setting background file for unity greeter. (https://bazaar.launchpad.net/~unity-settings-daemon-team/unity- settings-daemon/trunk/revision/4179) How-to-reproduce: -- 1) First disable the background plugin if it is already enabled. gsettings set org.gnome.settings-daemon.plugins.sharing active false 2) Change the wallpaper from unity-control-center. 3) Log out. Unity-greeter should reflect the change of wallpaper. But it doesn't. 4) Re-enable the background plugin. gsettings set org.gnome.settings-daemon.plugins.sharing active true 5) Change the wallpaper again and then log out. Unity-greeter now reflects the change in wallpaper properly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/1795145/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1783571] Re: Set Yaru as default
Unity Bug (MP attached) bug #1787572 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1783571 Title: Set Yaru as default Status in gnome-session package in Ubuntu: Fix Released Status in gnome-shell package in Ubuntu: Fix Released Status in ubuntu-meta package in Ubuntu: In Progress Status in ubuntu-settings package in Ubuntu: Fix Released Status in ubuntu-sounds package in Ubuntu: Won't Fix Status in ubuntu-themes package in Ubuntu: Won't Fix Status in yaru-theme package in Ubuntu: Fix Released Bug description: Set Yaru as default ubuntu 18.10 theme. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1783571/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1787297] Re: Clock : incorrect date format in FR in Unity panel …bionic.
Since it is happening in other sessions it could be bug in language-pack or some other package. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-datetime in Ubuntu. https://bugs.launchpad.net/bugs/1787297 Title: Clock : incorrect date format in FR in Unity panel …bionic. Status in indicator-datetime package in Ubuntu: Confirmed Status in unity package in Ubuntu: Invalid Bug description: Hi, Here is Ubuntu 18.04 with Unity session ( I know… ) System language and regional settings are set to French. In regional setting the date reads day number month year hour minute… which is correct for French. But the clock in the Unity panel reads day month number year hour minute… which looks more English than French order. Any config file I might edit to make my clock « more French » ? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1787297/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1787572] [NEW] Keep Ambiance as default for Unity
Public bug reported: Yaru has been set as default theme for Ubuntu session. But Yaru doesn't have unity specific styles (yet). See https://github.com/ubuntu/yaru/issues/701 So we keep Ambiance as default only for Unity session. ** Affects: ubuntu-settings (Ubuntu) Importance: Undecided Assignee: Khurshid Alam (khurshid-alam) Status: In Progress ** Tags: cosmic ** Changed in: ubuntu-settings (Ubuntu) Assignee: (unassigned) => Khurshid Alam (khurshid-alam) ** Changed in: ubuntu-settings (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1787572 Title: Keep Ambiance as default for Unity Status in ubuntu-settings package in Ubuntu: In Progress Bug description: Yaru has been set as default theme for Ubuntu session. But Yaru doesn't have unity specific styles (yet). See https://github.com/ubuntu/yaru/issues/701 So we keep Ambiance as default only for Unity session. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/1787572/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1783571] Re: Set Yaru as default
Please keep Ambiance as default for Unity. Yaru doesn't have unity specific styles (yet). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1783571 Title: Set Yaru as default Status in gnome-session package in Ubuntu: In Progress Status in gnome-shell package in Ubuntu: In Progress Status in ubuntu-meta package in Ubuntu: Won't Fix Status in ubuntu-settings package in Ubuntu: In Progress Status in ubuntu-sounds package in Ubuntu: Triaged Status in ubuntu-themes package in Ubuntu: In Progress Status in yaru-theme package in Ubuntu: Fix Released Bug description: Set Yaru as default ubuntu 18.10 theme. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1783571/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1787297] Re: Clock : incorrect date format in FR in Unity panel …bionic.
Ah I forgot, For your own custom time format, you need to first set `time-format` from 'locale-default' to 'custom'. You can customize the format as long as they are understood by strftime. http://manpages.ubuntu.com/strftime -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-datetime in Ubuntu. https://bugs.launchpad.net/bugs/1787297 Title: Clock : incorrect date format in FR in Unity panel …bionic. Status in indicator-datetime package in Ubuntu: New Status in unity package in Ubuntu: Invalid Bug description: Hi, Here is Ubuntu 18.04 with Unity session ( I know… ) System language and regional settings are set to French. In regional setting the date reads day number month year hour minute… which is correct for French. But the clock in the Unity panel reads day month number year hour minute… which looks more English than French order. Any config file I might edit to make my clock « more French » ? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1787297/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1787297] Re: Clock : incorrect date format in FR in Unity panel …bionic.
For me it works though. What is the output of `locale` ? It is possible that indicator-datetime is not building with language packs. Do you have "french" installed? If not you can install it from System language and regional settings. Also check if you have geoclue installed. 1) Install dconf-editor. 2) Go to /com/canonical/indicator/datetime 3) Check timezone name 4) You can change time-format with "custom-time-format" key ** Also affects: indicator-datetime (Ubuntu) Importance: Undecided Status: New ** Changed in: unity (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-datetime in Ubuntu. https://bugs.launchpad.net/bugs/1787297 Title: Clock : incorrect date format in FR in Unity panel …bionic. Status in indicator-datetime package in Ubuntu: New Status in unity package in Ubuntu: Invalid Bug description: Hi, Here is Ubuntu 18.04 with Unity session ( I know… ) System language and regional settings are set to French. In regional setting the date reads day number month year hour minute… which is correct for French. But the clock in the Unity panel reads day month number year hour minute… which looks more English than French order. Any config file I might edit to make my clock « more French » ? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1787297/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1776074] Re: indicator-datetime shouldn't recommend big ubuntu-touch-sounds package (maybe Suggests should be used instead)
No. Touch sound is also used for desktop for ringtones and alarms. Removing touch-sound will end up indicator-datetime spamming syslog specially if it can't detects the type of system (i.e. phone or desktop). Removing touch-sounds requires dropping "phone" support in its code or similar considerable changes. I can make the ringtones configurable through gsettings and make both phone & desktop use it and then perhaps renaming it to "ubuntu-ringtones /unity-ringtones". It's better than the current situation. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-datetime in Ubuntu. https://bugs.launchpad.net/bugs/1776074 Title: indicator-datetime shouldn't recommend big ubuntu-touch-sounds package (maybe Suggests should be used instead) Status in Default settings and artwork for Baltix OS: New Status in indicator-datetime package in Ubuntu: Confirmed Bug description: indicator-datetime package has big ubuntu-touch-sounds package in Recommends field even in latest Ubuntu Bionic release. gnome-panel recommends indicator-applet-complete and indicator-applet- complete recommends indicator-datetime, so big and not useful ubuntu- touch-sounds is installed in all desktop systems, where gnome- flashback (gnome-panel) desktop environment is used. I think ubuntu-touch-sounds should be removed from Recommends field and if there are some cases, where ubuntu-touch-sounds is usefull for indicator-datetime, then Suggests should be used instead. To manage notifications about this bug go to: https://bugs.launchpad.net/baltix-default-settings/+bug/1776074/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1738034] Re: Muted Sound Indicator randomly remains red when no sound is playing
> NOPE, because sometimes it does go back to normal without any action. > Both becoming red and going back to normal are COMPLETELY UTTERLY RANDOM. You keep saying these random behaviors. But I am unable to reproduce any of them on 18.04 & 18.10. Can you explain, how to reproduce in a concise way? And about sound indicator staying red after music stops, as I explained it is intended behavior. Once a explicit user action is requested, the program shouldn't do anything until that specific user action is completed. This is in-line with ux design & concept (I discussed this with previous dev). So I can't change anything in this area. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1738034 Title: Muted Sound Indicator randomly remains red when no sound is playing Status in indicator-sound package in Ubuntu: Confirmed Status in ubuntu-themes package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Mute the main Ubuntu volume 2. Play some short sound Expected behavior: Obviously you won't hear the sound. While the sound plays, the indicator should become red; then, when the sound is done playing and nothing else is playing, either immediately or after a very short period (e.g. a couple of seconds), the indicator should go back to its normal color. Observed behavior: Sometimes it behaves as expected, but sometimes it will remain red forever, until you unmute it. It's utterly random. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: indicator-sound 12.10.2+16.04.20160406-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-101.124-generic 4.4.95 Uname: Linux 4.4.0-101-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2.13 Architecture: amd64 CurrentDesktop: Unity Date: Wed Dec 13 17:09:25 2017 InstallationDate: Installed on 2013-10-11 (1523 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: indicator-sound UpgradeStatus: No upgrade log present (probably fresh install) upstart.indicator-sound.log: (process:2339): indicator-sound-WARNING **: accounts-service-access.vala:218: unable to sync volume 0,608643 to AccountsService: GDBus.Error:org.freedesktop.DBus.Error.InvalidArgs: No such interface 'com.ubuntu.AccountsService.Sound' (process:2339): indicator-sound-WARNING **: accounts-service-access.vala:218: unable to sync volume 0,848633 to AccountsService: GDBus.Error:org.freedesktop.DBus.Error.InvalidArgs: No such interface 'com.ubuntu.AccountsService.Sound' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1738034/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1738034] Re: Muted Sound Indicator randomly remains red when no sound is playing
> The issue is that the icon doesn't go back to normal and REMAINS red when the sound is finished playing. That is expected behavior. It turns red only to notify user that volume is muted. It requires immediate action. Once user unmute the volume it will go back to normal. Music may stop playing due to various other reason like pulseaudio error, so sound indicator couldn't possibly cover all scenarios why music has stopped playing. ** Changed in: ubuntu-themes (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1738034 Title: Muted Sound Indicator randomly remains red when no sound is playing Status in indicator-sound package in Ubuntu: Invalid Status in ubuntu-themes package in Ubuntu: Invalid Bug description: Steps to reproduce: 1. Mute the main Ubuntu volume 2. Play some short sound Expected behavior: Obviously you won't hear the sound. While the sound plays, the indicator should become red; then, when the sound is done playing and nothing else is playing, either immediately or after a very short period (e.g. a couple of seconds), the indicator should go back to its normal color. Observed behavior: Sometimes it behaves as expected, but sometimes it will remain red forever, until you unmute it. It's utterly random. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: indicator-sound 12.10.2+16.04.20160406-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-101.124-generic 4.4.95 Uname: Linux 4.4.0-101-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2.13 Architecture: amd64 CurrentDesktop: Unity Date: Wed Dec 13 17:09:25 2017 InstallationDate: Installed on 2013-10-11 (1523 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: indicator-sound UpgradeStatus: No upgrade log present (probably fresh install) upstart.indicator-sound.log: (process:2339): indicator-sound-WARNING **: accounts-service-access.vala:218: unable to sync volume 0,608643 to AccountsService: GDBus.Error:org.freedesktop.DBus.Error.InvalidArgs: No such interface 'com.ubuntu.AccountsService.Sound' (process:2339): indicator-sound-WARNING **: accounts-service-access.vala:218: unable to sync volume 0,848633 to AccountsService: GDBus.Error:org.freedesktop.DBus.Error.InvalidArgs: No such interface 'com.ubuntu.AccountsService.Sound' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1738034/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1738034] Re: Muted Sound Indicator randomly remains red when no sound is playing
It's most likely the issue with icon-theme issue. For me it turns red or blue depending or icon-theme. See https://i.imgur.com/zWYqIrl.png ** Also affects: ubuntu-themes (Ubuntu) Importance: Undecided Status: New ** Changed in: indicator-sound (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1738034 Title: Muted Sound Indicator randomly remains red when no sound is playing Status in indicator-sound package in Ubuntu: Invalid Status in ubuntu-themes package in Ubuntu: New Bug description: Steps to reproduce: 1. Mute the main Ubuntu volume 2. Play some short sound Expected behavior: Obviously you won't hear the sound. While the sound plays, the indicator should become red; then, when the sound is done playing and nothing else is playing, either immediately or after a very short period (e.g. a couple of seconds), the indicator should go back to its normal color. Observed behavior: Sometimes it behaves as expected, but sometimes it will remain red forever, until you unmute it. It's utterly random. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: indicator-sound 12.10.2+16.04.20160406-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-101.124-generic 4.4.95 Uname: Linux 4.4.0-101-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2.13 Architecture: amd64 CurrentDesktop: Unity Date: Wed Dec 13 17:09:25 2017 InstallationDate: Installed on 2013-10-11 (1523 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: indicator-sound UpgradeStatus: No upgrade log present (probably fresh install) upstart.indicator-sound.log: (process:2339): indicator-sound-WARNING **: accounts-service-access.vala:218: unable to sync volume 0,608643 to AccountsService: GDBus.Error:org.freedesktop.DBus.Error.InvalidArgs: No such interface 'com.ubuntu.AccountsService.Sound' (process:2339): indicator-sound-WARNING **: accounts-service-access.vala:218: unable to sync volume 0,848633 to AccountsService: GDBus.Error:org.freedesktop.DBus.Error.InvalidArgs: No such interface 'com.ubuntu.AccountsService.Sound' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1738034/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1770839] Re: Syncevolution does not run in Ubuntu 18.04
Please ask in ubuntu-devel mailing list to update syncevolution. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to syncevolution in Ubuntu. https://bugs.launchpad.net/bugs/1770839 Title: Syncevolution does not run in Ubuntu 18.04 Status in syncevolution package in Ubuntu: Confirmed Bug description: There is a problem with the package syncevolution (1.5.3-1ubuntu2) in Ubuntu 18.04 : Step to reproduce: >$ sudo apt install syncevolution Lecture des listes de paquets... Fait Construction de l'arbre des dépendances Lecture des informations d'état... Fait Les paquets supplémentaires suivants seront installés : libopenobex2 libpcrecpp0v5 libsmltk0 libsyncevolution0 libsynthesis0v5 syncevolution-common syncevolution-libs syncevolution-libs-gnome Les NOUVEAUX paquets suivants seront installés : libopenobex2 libpcrecpp0v5 libsmltk0 libsyncevolution0 libsynthesis0v5 syncevolution syncevolution-common syncevolution-libs syncevolution-libs-gnome 0 mis à jour, 9 nouvellement installés, 0 à enlever et 0 non mis à jour. Il est nécessaire de prendre 2'230 ko dans les archives. Après cette opération, 10.2 Mo d'espace disque supplémentaires seront utilisés. Souhaitez-vous continuer ? [O/n] O [...] Paramétrage de syncevolution (1.5.3-1ubuntu2) ... [...] > $ syncevolution --version syncevolution: error while loading shared libraries: libgdbussyncevo.so.0: cannot open shared object file: No such file or directory > $ syncevolution --print-peers syncevolution: error while loading shared libraries: libgdbussyncevo.so.0: cannot open shared object file: No such file or directory > $ syncevolution --print-config syncevolution: error while loading shared libraries: libgdbussyncevo.so.0: cannot open shared object file: No such file or directory Please note that this bug semms corrected in a new release of syncevolution : https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=887043 Would it be possible to have the corrected verion in Ubuntu 18.04 ? Thanks in advance for your help To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/syncevolution/+bug/1770839/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1708375] Re: Add support for purple-telegram (telepathy-haze)
** Tags removed: bionic
** Tags added: cosmic
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to telepathy-mission-
control-5 in Ubuntu.
https://bugs.launchpad.net/bugs/1708375
Title:
Add support for purple-telegram (telepathy-haze)
Status in telepathy-mission-control-5 package in Ubuntu:
Confirmed
Bug description:
When using purple telegram through telepathy-haze, it requires
following permissions:
# for purple telegram
/etc/telegram-purple/server.tglpub r,
/usr/lib/purple-2*/ r,
/usr/lib/purple-2/*.somr,
/usr/share/locale/*/LC_MESSAGES/*.mo r,
/usr/share/pixmaps/pidgin/protocols/{16,32,48}/*.png r,
@{HOME}/.purple/telegram-purple/** rw,
@{HOME}/.telegram-purple/** rw,
under /usr/lib/telepathy/telepathy-* section. See issue
https://github.com/majn/telegram-purple/issues/346 for more details.
I have attached the necessary patch
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/telepathy-mission-control-5/+bug/1708375/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1772798] Re: Unity: Force start background plugin
** Description changed: If a user, already running a Gnome session upgrades or install unity by installing unity-session, background plugin doesn't start automatically (with u-s-d). This plugin has been removed from gnome-settings-daemon - and since gsd doesn't use it, it gets turned off. + (Ubuntu carries a patch which only adds back the schema) and since gsd + doesn't use it, it gets turned off. The background plugin is necessary to sync background related settings (wallpaper, sound, messages) with unity-greeter. If it doesn't start with u-s-d, changing wallpaper will not change the background of unity- greeter. The change was introduced in https://bazaar.launchpad.net/~unity- settings-daemon-team/unity-settings-daemon/trunk/revision/4179 This can be done in gsettings-override (In unity specific section) [org.gnome.settings-daemon.plugins.background:Unity] active = true Merge should happen against https://code.launchpad.net/~ubuntu- desktop/+junk/ubuntu-settings Since it's a +junk, I can't request merge proposals. I am also attaching the diff here. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1772798 Title: Unity: Force start background plugin Status in ubuntu-settings package in Ubuntu: Confirmed Bug description: If a user, already running a Gnome session upgrades or install unity by installing unity-session, background plugin doesn't start automatically (with u-s-d). This plugin has been removed from gnome- settings-daemon (Ubuntu carries a patch which only adds back the schema) and since gsd doesn't use it, it gets turned off. The background plugin is necessary to sync background related settings (wallpaper, sound, messages) with unity-greeter. If it doesn't start with u-s-d, changing wallpaper will not change the background of unity-greeter. The change was introduced in https://bazaar.launchpad.net/~unity- settings-daemon-team/unity-settings-daemon/trunk/revision/4179 This can be done in gsettings-override (In unity specific section) [org.gnome.settings-daemon.plugins.background:Unity] active = true Merge should happen against https://code.launchpad.net/~ubuntu- desktop/+junk/ubuntu-settings Since it's a +junk, I can't request merge proposals. I am also attaching the diff here. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/1772798/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1772798] Re: Unity: Force start background plugin
** Description changed: If a user, already running a Gnome session upgrades or install unity by installing unity-session, background plugin doesn't start automatically. This plugin has been removed from gnome-settings-daemon and since gsd doesn't use it, it gets turned off. The background plugin is necessary to sync background related settings (wallpaper, sound, messages) with unity-greeter. If it doesn't start with u-s-d, changing wallpaper will not change the background of unity- greeter. The change was introduced in https://bazaar.launchpad.net/~unity- settings-daemon-team/unity-settings-daemon/trunk/revision/4179 This can be done in gsettings-override (In unity specific section) [org.gnome.settings-daemon.plugins.background:Unity] active = true + + + Merge should happen against https://code.launchpad.net/~ubuntu-desktop/+junk/ubuntu-settings?_ga=2.170229856.1568832379.1526976197-354995031.1498808407 + + Since it's a +junk, I can't request merge proposals. I am also attaching + the diff here. ** Patch added: "force-start-background-plugin.patch" https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/1772798/+attachment/5143167/+files/force-start-background-plugin.patch ** Description changed: If a user, already running a Gnome session upgrades or install unity by installing unity-session, background plugin doesn't start automatically. This plugin has been removed from gnome-settings-daemon and since gsd doesn't use it, it gets turned off. The background plugin is necessary to sync background related settings (wallpaper, sound, messages) with unity-greeter. If it doesn't start with u-s-d, changing wallpaper will not change the background of unity- greeter. The change was introduced in https://bazaar.launchpad.net/~unity- settings-daemon-team/unity-settings-daemon/trunk/revision/4179 This can be done in gsettings-override (In unity specific section) [org.gnome.settings-daemon.plugins.background:Unity] active = true - - Merge should happen against https://code.launchpad.net/~ubuntu-desktop/+junk/ubuntu-settings?_ga=2.170229856.1568832379.1526976197-354995031.1498808407 + Merge should happen against https://code.launchpad.net/~ubuntu- + desktop/+junk/ubuntu-settings Since it's a +junk, I can't request merge proposals. I am also attaching the diff here. ** Description changed: If a user, already running a Gnome session upgrades or install unity by - installing unity-session, background plugin doesn't start automatically. - This plugin has been removed from gnome-settings-daemon and since gsd - doesn't use it, it gets turned off. + installing unity-session, background plugin doesn't start automatically + (with u-s-d). This plugin has been removed from gnome-settings-daemon + and since gsd doesn't use it, it gets turned off. The background plugin is necessary to sync background related settings (wallpaper, sound, messages) with unity-greeter. If it doesn't start with u-s-d, changing wallpaper will not change the background of unity- greeter. The change was introduced in https://bazaar.launchpad.net/~unity- settings-daemon-team/unity-settings-daemon/trunk/revision/4179 This can be done in gsettings-override (In unity specific section) [org.gnome.settings-daemon.plugins.background:Unity] active = true Merge should happen against https://code.launchpad.net/~ubuntu- desktop/+junk/ubuntu-settings Since it's a +junk, I can't request merge proposals. I am also attaching the diff here. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1772798 Title: Unity: Force start background plugin Status in ubuntu-settings package in Ubuntu: Confirmed Bug description: If a user, already running a Gnome session upgrades or install unity by installing unity-session, background plugin doesn't start automatically (with u-s-d). This plugin has been removed from gnome- settings-daemon and since gsd doesn't use it, it gets turned off. The background plugin is necessary to sync background related settings (wallpaper, sound, messages) with unity-greeter. If it doesn't start with u-s-d, changing wallpaper will not change the background of unity-greeter. The change was introduced in https://bazaar.launchpad.net/~unity- settings-daemon-team/unity-settings-daemon/trunk/revision/4179 This can be done in gsettings-override (In unity specific section) [org.gnome.settings-daemon.plugins.background:Unity] active = true Merge should happen against https://code.launchpad.net/~ubuntu- desktop/+junk/ubuntu-settings Since it's a +junk, I can't request merge proposals. I am also attaching the diff here. To manage notifications about this bug go to:
[Touch-packages] [Bug 1772798] Re: Unity: Force start background plugin
** Description changed: If a user, already running a Gnome session upgrades or install unity by installing unity-session, background plugin doesn't start automatically. This plugin has been removed from gnome-settings-daemon and since gsd doesn't use it, it gets turned off. The background plugin is necessary to sync background related settings (wallpaper, sound, messages) with unity-greeter. If it doesn't start with u-s-d, changing wallpaper will not change the background of unity- greeter. The change was introduced in https://bazaar.launchpad.net/~unity- settings-daemon-team/unity-settings-daemon/trunk/revision/4179 + + This can be done in gsettings-override + + [org.gnome.settings-daemon.plugins.background:Unity] + active = true ** Description changed: If a user, already running a Gnome session upgrades or install unity by installing unity-session, background plugin doesn't start automatically. This plugin has been removed from gnome-settings-daemon and since gsd doesn't use it, it gets turned off. The background plugin is necessary to sync background related settings (wallpaper, sound, messages) with unity-greeter. If it doesn't start with u-s-d, changing wallpaper will not change the background of unity- greeter. The change was introduced in https://bazaar.launchpad.net/~unity- settings-daemon-team/unity-settings-daemon/trunk/revision/4179 - This can be done in gsettings-override + This can be done in gsettings-override (In unity specific section) [org.gnome.settings-daemon.plugins.background:Unity] active = true -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1772798 Title: Unity: Force start background plugin Status in ubuntu-settings package in Ubuntu: Confirmed Bug description: If a user, already running a Gnome session upgrades or install unity by installing unity-session, background plugin doesn't start automatically. This plugin has been removed from gnome-settings-daemon and since gsd doesn't use it, it gets turned off. The background plugin is necessary to sync background related settings (wallpaper, sound, messages) with unity-greeter. If it doesn't start with u-s-d, changing wallpaper will not change the background of unity-greeter. The change was introduced in https://bazaar.launchpad.net/~unity- settings-daemon-team/unity-settings-daemon/trunk/revision/4179 This can be done in gsettings-override (In unity specific section) [org.gnome.settings-daemon.plugins.background:Unity] active = true To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/1772798/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1772798] [NEW] Unity: Force start background plugin
Public bug reported: If a user, already running a Gnome session upgrades or install unity by installing unity-session, background plugin doesn't start automatically. This plugin has been removed from gnome-settings-daemon and since gsd doesn't use it, it gets turned off. The background plugin is necessary to sync background related settings (wallpaper, sound, messages) with unity-greeter. If it doesn't start with u-s-d, changing wallpaper will not change the background of unity- greeter. The change was introduced in https://bazaar.launchpad.net/~unity- settings-daemon-team/unity-settings-daemon/trunk/revision/4179 ** Affects: ubuntu-settings (Ubuntu) Importance: Undecided Assignee: Khurshid Alam (khurshid-alam) Status: Confirmed ** Changed in: ubuntu-settings (Ubuntu) Status: New => Confirmed ** Changed in: ubuntu-settings (Ubuntu) Assignee: (unassigned) => Khurshid Alam (khurshid-alam) ** Description changed: If a user, already running a Gnome session upgrades or install unity by installing unity-session, background plugin doesn't start automatically. This plugin has been removed from gnome-settings-daemon and since gsd doesn't use it, it gets turned off. The background plugin is necessary to sync background related settings (wallpaper, sound, messages) with unity-greeter. If it doesn't start with u-s-d, changing wallpaper will not change the background of unity- greeter. + + The change was introduce in https://bazaar.launchpad.net/~unity- + settings-daemon-team/unity-settings-daemon/trunk/revision/4179 ** Description changed: If a user, already running a Gnome session upgrades or install unity by installing unity-session, background plugin doesn't start automatically. This plugin has been removed from gnome-settings-daemon and since gsd doesn't use it, it gets turned off. The background plugin is necessary to sync background related settings (wallpaper, sound, messages) with unity-greeter. If it doesn't start with u-s-d, changing wallpaper will not change the background of unity- greeter. - The change was introduce in https://bazaar.launchpad.net/~unity- + The change was introduced in https://bazaar.launchpad.net/~unity- settings-daemon-team/unity-settings-daemon/trunk/revision/4179 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1772798 Title: Unity: Force start background plugin Status in ubuntu-settings package in Ubuntu: Confirmed Bug description: If a user, already running a Gnome session upgrades or install unity by installing unity-session, background plugin doesn't start automatically. This plugin has been removed from gnome-settings-daemon and since gsd doesn't use it, it gets turned off. The background plugin is necessary to sync background related settings (wallpaper, sound, messages) with unity-greeter. If it doesn't start with u-s-d, changing wallpaper will not change the background of unity-greeter. The change was introduced in https://bazaar.launchpad.net/~unity- settings-daemon-team/unity-settings-daemon/trunk/revision/4179 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/1772798/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1760435] [NEW] Use Ubuntu language packs for various indicators
Public bug reported: The Unity family of packages was previously part of standard Ubuntu. Thus all the translation templates were made available to the translators via Launchpad, and the translations were included in the language packs. Since those packages are no longer part of standard Ubuntu, they have been moved from main to universe. And translations are dropped. At the moment, it is feasible for us to keep using langpacks. That means adding "X-Ubuntu-Use-Langpack: yes" to their debian/control and doing an upload. See: https://community.ubuntu.com/t/translation-of-unity-packages/4919 ** Affects: indicator-datetime (Ubuntu) Importance: Undecided Status: Confirmed ** Affects: indicator-messages (Ubuntu) Importance: Undecided Status: Confirmed ** Affects: indicator-power (Ubuntu) Importance: Undecided Status: Confirmed ** Affects: indicator-session (Ubuntu) Importance: Undecided Status: Confirmed ** Affects: indicator-sound (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: bionic ** Also affects: indicator-power (Ubuntu) Importance: Undecided Status: New ** Also affects: indicator-session (Ubuntu) Importance: Undecided Status: New ** Also affects: indicator-messages (Ubuntu) Importance: Undecided Status: New ** Also affects: indicator-sound (Ubuntu) Importance: Undecided Status: New ** Summary changed: - Use Ubuntu language packs for various unity-components + Use Ubuntu language packs for various indicators ** Changed in: indicator-datetime (Ubuntu) Status: New => Confirmed ** Changed in: indicator-messages (Ubuntu) Status: New => Confirmed ** Changed in: indicator-power (Ubuntu) Status: New => Confirmed ** Changed in: indicator-session (Ubuntu) Status: New => Confirmed ** Changed in: indicator-sound (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-datetime in Ubuntu. https://bugs.launchpad.net/bugs/1760435 Title: Use Ubuntu language packs for various indicators Status in indicator-datetime package in Ubuntu: Confirmed Status in indicator-messages package in Ubuntu: Confirmed Status in indicator-power package in Ubuntu: Confirmed Status in indicator-session package in Ubuntu: Confirmed Status in indicator-sound package in Ubuntu: Confirmed Bug description: The Unity family of packages was previously part of standard Ubuntu. Thus all the translation templates were made available to the translators via Launchpad, and the translations were included in the language packs. Since those packages are no longer part of standard Ubuntu, they have been moved from main to universe. And translations are dropped. At the moment, it is feasible for us to keep using langpacks. That means adding "X-Ubuntu-Use-Langpack: yes" to their debian/control and doing an upload. See: https://community.ubuntu.com/t/translation-of-unity-packages/4919 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1760435/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1708375] Re: Add support for purple-telegram (telepathy-haze)
I have updated the patch. Is there anything else needed for this?
** Tags removed: artful
** Tags added: bionic
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to telepathy-mission-
control-5 in Ubuntu.
https://bugs.launchpad.net/bugs/1708375
Title:
Add support for purple-telegram (telepathy-haze)
Status in telepathy-mission-control-5 package in Ubuntu:
Confirmed
Bug description:
When using purple telegram through telepathy-haze, it requires
following permissions:
# for purple telegram
/etc/telegram-purple/server.tglpub r,
/usr/lib/purple-2*/ r,
/usr/lib/purple-2/*.somr,
/usr/share/locale/*/LC_MESSAGES/*.mo r,
/usr/share/pixmaps/pidgin/protocols/{16,32,48}/*.png r,
@{HOME}/.purple/telegram-purple/** rw,
@{HOME}/.telegram-purple/** rw,
under /usr/lib/telepathy/telepathy-* section. See issue
https://github.com/majn/telegram-purple/issues/346 for more details.
I have attached the necessary patch
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/telepathy-mission-control-5/+bug/1708375/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1735998] Re: Decouple unity related settings as unity-settings
Ok. I don't have any problem having "unity-settings" on universe without removing gsettings from "ubuntu-settings". They won't collide. They both set same settings for unity any way. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1735998 Title: Decouple unity related settings as unity-settings Status in ubuntu-settings package in Ubuntu: Confirmed Bug description: This is an attempt to resolve "* Shared GSettings keys" issue listed under https://wiki.ubuntu.com/Unity/NotDefaultIssues. Ubuntu so far is providing session related overrides for both ubuntu & unity sessions in a single package, i.e. ubuntu-settings. But now that Unity is not the default desktop it doesn't make any sense to carry unity related overrides in ubuntu-settings. For this purpose I have created a new project: unity-settings (https://code.launchpad.net/~khurshid-alam/unity-settings/trunk) and the binary would be unity-settings in universe. To make this happen in under 18.04 cycle, the work-flow should be: 1) Have unity-settings in the universe 2) Have ubuntu-unity-desktop in the universe 3) Let ubuntu-unity-desktop depends on unity-settings 4) Drop unity related settings in ubuntu-settings (merge request in-progress) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/1735998/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1735998] Re: Decouple unity related settings as unity-settings
@Jeremy 1) I only removed unity specific gsettings overrides from ubuntu-settings. Is there any specific reason to carry unity specific gsettings overrides in ubuntu-settings? Unity is not a default desktop anymore nor it is installed in the default live iso. 2) We carry unity specific gsettings overrides in unity-settings and make unity-session depends on unity-settings. That way Ubuntu and Unity remain separate without overlapping. 3) And as you said we also want to decouple unity-session from gnome- session so two pieces code remains separate. It will easier for us to maintain unity if we keep these separated from one another. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1735998 Title: Decouple unity related settings as unity-settings Status in ubuntu-settings package in Ubuntu: Confirmed Bug description: This is an attempt to resolve "* Shared GSettings keys" issue listed under https://wiki.ubuntu.com/Unity/NotDefaultIssues. Ubuntu so far is providing session related overrides for both ubuntu & unity sessions in a single package, i.e. ubuntu-settings. But now that Unity is not the default desktop it doesn't make any sense to carry unity related overrides in ubuntu-settings. For this purpose I have created a new project: unity-settings (https://code.launchpad.net/~khurshid-alam/unity-settings/trunk) and the binary would be unity-settings in universe. To make this happen in under 18.04 cycle, the work-flow should be: 1) Have unity-settings in the universe 2) Have ubuntu-unity-desktop in the universe 3) Let ubuntu-unity-desktop depends on unity-settings 4) Drop unity related settings in ubuntu-settings (merge request in-progress) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/1735998/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1745070] Re: Decorations/headerbars are broken in bionic: double bar in Xorg logins and missing in Wayland logins
Do you have gtk3-nocsd installed? It is supposed to be disabled for Gnome session. But it is not working properly. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1745070 Title: Decorations/headerbars are broken in bionic: double bar in Xorg logins and missing in Wayland logins Status in Ubuntu theme: New Status in gnome-shell package in Ubuntu: New Status in mutter package in Ubuntu: New Status in ubuntu-themes package in Ubuntu: New Bug description: Decorations/headerbars are broken in bionic: double bar in Xorg logins and missing window buttons + rounding in Wayland logins. Screenshots attached. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: light-themes 16.10+18.04.20180122.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13 Uname: Linux 4.13.0-25-generic x86_64 ApportVersion: 2.20.8-0ubuntu6 Architecture: amd64 Date: Wed Jan 24 10:15:01 2018 InstallationDate: Installed on 2017-12-12 (42 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171211) PackageArchitecture: all SourcePackage: ubuntu-themes UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-themes/+bug/1745070/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1433943] Re: Enable carddav OAuth2 scope ( https://www.googleapis.com/auth/carddav ) in Ubuntu Online Account (Vivid)
** Changed in: evolution-data-server (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1433943 Title: Enable carddav OAuth2 scope ( https://www.googleapis.com/auth/carddav ) in Ubuntu Online Account (Vivid) Status in evolution-data-server package in Ubuntu: Invalid Bug description: It seems Ubuntu does not enable CardDav scope (https://www.googleapis.com/auth/carddav) in online account. Ubuntu only enables Google Contacts API (Gdata) https://www.google.com/m8/feeds/ which is NOT same as CardDav. As a result when some application( ex. Syncevolution) tries to access it (through oauth2), it gives “authentication failed error”. For example, running following command: ''' SYNCEVOLUTION_DEBUG=1 syncevolution --print-databases –daemon=no\ loglevel=2 backend=carddav username=uoa:3,google-contacts\ syncURL=https://www.googleapis.com/.well-known/carddav ''' gives following error: “PROPFIND: Neon error code 1: 403 Forbidden, must not retry” NOTE: It is required that that the scope for accessing CardDAV needs to be specified in the sources too. Having it only in the APIs Console is not enough. Otherwise Google rejects access to the CardDAV resources with a 401 "AuthSub challenge". Discussion on Syncevolution Mailing List: https://lists.syncevolution.org/pipermail/syncevolution/2015-March/005119.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1433943/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1732612] Re: Alt+Printscreen not working (doesn't generate keypress event)
Workaround (1): press and hold Print Screen press and hold Alt release Print Screen (and then Alt) This seemed to work for me, but it shouldn’t be necessary. Workaround (2) For Laptops if Printscreen is combined with Sysreq: sudo sysctl -w kernel.sysrq=1 #disables magic sysreq for that session. Press Alt+Printscreen or Alt+Fn+Printscreen (first Alt, then Fn). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1732612 Title: Alt+Printscreen not working (doesn't generate keypress event) Status in systemd package in Ubuntu: Confirmed Status in unity package in Ubuntu: Confirmed Bug description: Since I have upgraded to Ubuntu 17.10 Alt+PrintScreen doesn't work on my computer. I'm using Unity DE, with default settings. The problem is not about taking screnshots. xev recognizes when I press down the alt key, but nothing happens when I press Print Screen with alt being pressed (it does when PrintScreen is pressed by itself) Here is evtest output when I press Alt+Printscreen: # Alt pressed down: Event: time 1510817663.883489, -- SYN_REPORT Event: time 1510817663.923476, type 1 (EV_KEY), code 56 (KEY_LEFTALT), value 2 Event: time 1510817663.923476, -- SYN_REPORT Event: time 1510817663.963479, type 1 (EV_KEY), code 56 (KEY_LEFTALT), value 2 Event: time 1510817663.963479, -- SYN_REPORT Event: time 1510817663.993036, type 4 (EV_MSC), code 4 (MSC_SCAN), value 70046 # Print screen pressed Event: time 1510817663.993036, -- SYN_REPORT Event: time 1510817664.945032, type 1 (EV_KEY), code 56 (KEY_LEFTALT), value 0 # Alt released Event: time 1510817664.945032, -- SYN_REPORT Event: time 1510817664.945086, type 1 (EV_KEY), code 56 (KEY_LEFTALT), value 1 Event: time 1510817664.945086, type 1 (EV_KEY), code 99 (KEY_SYSRQ), value 1 Event: time 1510817664.945086, -- SYN_REPORT Event: time 1510817664.945097, type 1 (EV_KEY), code 99 (KEY_SYSRQ), value 0 Event: time 1510817664.945097, type 1 (EV_KEY), code 56 (KEY_LEFTALT), value 0 Event: time 1510817664.945097, -- SYN_REPORT ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: udev 234-2ubuntu12.1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu CustomUdevRuleFiles: 67-xorg-wizardpen.rules 99-displaylink.rules 60-vboxdrv.rules 70-snap.core.rules 99-anbox.rules Date: Thu Nov 16 08:29:46 2017 InstallationDate: Installed on 2017-03-26 (234 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170321) MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: Upgraded to artful on 2017-10-23 (23 days ago) dmi.bios.date: 10/24/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F1 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z77-HD3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF1:bd10/24/2012:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ77-HD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1732612/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1727390] Re: New bugfix release 17.2.4
mesa 17.2.4-0ubuntu1~16.04.1 in xenial lots of issues with unity and compiz. See this bugs: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1741447 https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1735594 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1727390 Title: New bugfix release 17.2.4 Status in mesa package in Ubuntu: Fix Released Status in mesa source package in Xenial: Fix Released Status in mesa source package in Artful: Fix Committed Bug description: [Impact] A new upstream bugfix release is available. Release note diff compared to 17.2.2: "Mesa 17.2.3 is now available. In this release we have: The Vulkan drivers ANV and RADV have multiple small fixes. The EGL code has improved handling of the new wl_dmabuf codepath. SWR no longer crashes when checking environment variables. Other gallium drivers have also seen updates - freedreno, nouveau and radeonsi. The gallivm module, used by llvmpipe et al. has gained little endian PPC64 fixes. The VA and VDPAU state-trackers have seems improvements handling interlaced videos. We're using python3 compatible constructs which gives us SCons 3.0 support." "Mesa 17.2.4 is now available. In this release we have: In Mesa Core we have included a change to prevent KOTOR from breaking when in combination with the ATI fragment shader extension. Additionally, NIR has also received a correction. Mesa's state tracker has gotten a patch to avoid leaks in certain situations like when resizing a window. Intel drivers have received several fixes. The compiler has gotten a couple, while anv also received one. i965 got a patch to avoid VA- API, Beignet and other contexts in the system to break when in combination with previous versions of Mesa 17.2.x. AMD's compiler has received a couple of fixes while radv has also received another couple, including one to avoid a hang due to an overflow on huge textures. Broadcom's vc4 has corrected a problem when compiling with Android's clang. clover has also seen fixed a problem compiling after a specific clang revision. Vulkan's WSI has gotten plugged a memory leak for X11." [Test case] Test typical use cases on the most common hw/driver combinations: intel/i965 nvidia/nouveau radeon/radeonsi [Regression potential] These releases are tested against compliance, bugfix releases in particular have minimal risk of regressing anything major at least. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1727390/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1618188] Re: systemd journal should be persistent by default: /var/log/journal should be created
What??!!! Persistent logging does lot more that just logging. Do you people even use sata hard disk? There are multiple reports (check archlinux forums) that it is bad for sata. That is why it is set to auto by default. The word "auto" exactly created for that purposewhen there is both benefit ane cost with certain action. We don't want our hard disk to die quickly becquse of we want to see some logs that we don't understand any way, -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1618188 Title: systemd journal should be persistent by default: /var/log/journal should be created Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: Confirmed Status in systemd source package in Zesty: Confirmed Status in systemd source package in Artful: Confirmed Status in systemd source package in Bionic: Fix Released Bug description: After upgrading 14.04 -> 16.04, key services are now running on systemd and using the systemd journal for logging. In 14.04, key system logs like /var/log/messages and /var/log/syslog were persistent, but after the upgrade to 16.04 there has a been a regression of sorts: Logs sent to systemd's journald are now being thrown away during reboots. This behavior is controlled by the `Storage=` option in `/etc/systemd/journald.conf`. The default setting is `Storage=auto` which will persist logs in `/var/log/journal/`, *only if the directory already exists*. But the directory was not created as part of the 14.04 -> 16.04 upgrade, so logging was being lost for a while before I realized what was happening. This issue could be solved by either creating /var/log/journal or changing the default Storage behavior to `Storage=persistent`, which would create the directory if need be. ## Related reference * `systemd` currently compounds the issue by having ["journal --disk-usage" report memory usage as disk usage](https://github.com/systemd/systemd/issues/4059), giving the impression that the disk is being used for logging when it isn't. * [User wonders where to find logs from previous boots, unaware that the logs were thrown away](http://askubuntu.com/questions/765315/how-to-find-previous-boot-log-after-ubuntu-16-04-restarts) ## Recommended fix Restoring persistent logging as the default is recommended. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1618188/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1736994] Re: [needs-packaging] [MOTU] Have ubuntu-unity-desktop meta package in universe
Seed branch is live on https://code.launchpad.net/~unity7maintainers /ubuntu-seeds/ubuntu-unity.bionic ** Description changed: [needs-packaging] ubuntu-unity-desktop ubuntu-unity-desktop is the meta package which installs a fully functional unity desktop. Source: https://code.launchpad.net/~unity7maintainers/ubuntu-unity- meta/+git/ubuntu-unity-meta + Seed: https://code.launchpad.net/~unity7maintainers/ubuntu-seeds/ubuntu- + unity.bionic + License: GNU GPL v2 PPA: ppa:unity7maintainers/unity7-desktop - - Note: Atm, since ubuntu-unity is not an official flavor there is no seed - branch on https://code.launchpad.net/ubuntu-seeds. ** Changed in: ubuntu-meta (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1736994 Title: [needs-packaging] [MOTU] Have ubuntu-unity-desktop meta package in universe Status in ubuntu-meta package in Ubuntu: Confirmed Bug description: [needs-packaging] ubuntu-unity-desktop ubuntu-unity-desktop is the meta package which installs a fully functional unity desktop. Source: https://code.launchpad.net/~unity7maintainers/ubuntu-unity- meta/+git/ubuntu-unity-meta Seed: https://code.launchpad.net/~unity7maintainers/ubuntu-seeds /ubuntu-unity.bionic License: GNU GPL v2 PPA: ppa:unity7maintainers/unity7-desktop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1736994/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1732612] Re: Alt+Printscreen not working (doesn't generate keypress event)
There is also this bug 1683383, not sure if it is related. But lots key shortcuts problems started to arrive after Ubuntu removed 6 year old patch from xorg. For me, Ctrl+Alt+T works fine though. Only Alt++Fn+Print-screen doesn't work. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1732612 Title: Alt+Printscreen not working (doesn't generate keypress event) Status in systemd package in Ubuntu: Confirmed Status in unity package in Ubuntu: Confirmed Bug description: Since I have upgraded to Ubuntu 17.10 Alt+PrintScreen doesn't work on my computer. I'm using Unity DE, with default settings. The problem is not about taking screnshots. xev recognizes when I press down the alt key, but nothing happens when I press Print Screen with alt being pressed (it does when PrintScreen is pressed by itself) Here is evtest output when I press Alt+Printscreen: # Alt pressed down: Event: time 1510817663.883489, -- SYN_REPORT Event: time 1510817663.923476, type 1 (EV_KEY), code 56 (KEY_LEFTALT), value 2 Event: time 1510817663.923476, -- SYN_REPORT Event: time 1510817663.963479, type 1 (EV_KEY), code 56 (KEY_LEFTALT), value 2 Event: time 1510817663.963479, -- SYN_REPORT Event: time 1510817663.993036, type 4 (EV_MSC), code 4 (MSC_SCAN), value 70046 # Print screen pressed Event: time 1510817663.993036, -- SYN_REPORT Event: time 1510817664.945032, type 1 (EV_KEY), code 56 (KEY_LEFTALT), value 0 # Alt released Event: time 1510817664.945032, -- SYN_REPORT Event: time 1510817664.945086, type 1 (EV_KEY), code 56 (KEY_LEFTALT), value 1 Event: time 1510817664.945086, type 1 (EV_KEY), code 99 (KEY_SYSRQ), value 1 Event: time 1510817664.945086, -- SYN_REPORT Event: time 1510817664.945097, type 1 (EV_KEY), code 99 (KEY_SYSRQ), value 0 Event: time 1510817664.945097, type 1 (EV_KEY), code 56 (KEY_LEFTALT), value 0 Event: time 1510817664.945097, -- SYN_REPORT ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: udev 234-2ubuntu12.1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu CustomUdevRuleFiles: 67-xorg-wizardpen.rules 99-displaylink.rules 60-vboxdrv.rules 70-snap.core.rules 99-anbox.rules Date: Thu Nov 16 08:29:46 2017 InstallationDate: Installed on 2017-03-26 (234 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170321) MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: Upgraded to artful on 2017-10-23 (23 days ago) dmi.bios.date: 10/24/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F1 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z77-HD3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF1:bd10/24/2012:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ77-HD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1732612/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1736994] Re: [needs-packaging] [MOTU] Have ubuntu-unity-desktop meta package in universe
** Description changed: [needs-packaging] ubuntu-unity-desktop ubuntu-unity-desktop is the meta package which installs a fully functional unity desktop. Source: https://code.launchpad.net/~unity7maintainers/ubuntu-unity- meta/+git/ubuntu-unity-meta License: GNU GPL v2 PPA: ppa:unity7maintainers/unity7-desktop - Note: Atm, since ubuntu-unity is no an official flavor there is no seed + Note: Atm, since ubuntu-unity is not an official flavor there is no seed branch on https://code.launchpad.net/ubuntu-seeds. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1736994 Title: [needs-packaging] [MOTU] Have ubuntu-unity-desktop meta package in universe Status in ubuntu-meta package in Ubuntu: Incomplete Bug description: [needs-packaging] ubuntu-unity-desktop ubuntu-unity-desktop is the meta package which installs a fully functional unity desktop. Source: https://code.launchpad.net/~unity7maintainers/ubuntu-unity- meta/+git/ubuntu-unity-meta License: GNU GPL v2 PPA: ppa:unity7maintainers/unity7-desktop Note: Atm, since ubuntu-unity is not an official flavor there is no seed branch on https://code.launchpad.net/ubuntu-seeds. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1736994/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1735998] Re: Decouple unity related settings as unity-settings
@Jeremy >Why do you think you need to take those settings out of ubuntu- settings? 1) We can ship all sorts unity specific overrides in unity-settings. It's cleaner that way. 2) We want to ship per-desktop override of ".desktop" (ex: Gnome- software) on "/usr/share/unity/applications". Rather patching each app individually we could do that in unity-settings. That's what ubuntu-mate does in ubuntu-mate-settings. 3) Not every gnome app will work well with unity. If we want to use a alternative we need to override mimeapps list in "/usr/share/applications/unity-mimeapps.list". We can easily do that in unity-settings. 4) The idea is to have a separate ubuntu-unity-amd64.iso. But in the default iso, both autologin and user-session names set to "ubuntu". If we want to change that to "unity", we could do that by shipping a override in "/usr/share/lightdm/lightdm.conf.d/51-autologin.conf". unity-settings seems proper place to do that. Other option is to carry similar settings in lightdm. 5) In future you may want to demote all unity related components/bits to universe. For that you need to decouple unity-session from gnome-session and a separate unity-settings. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1735998 Title: Decouple unity related settings as unity-settings Status in ubuntu-settings package in Ubuntu: Confirmed Bug description: This is an attempt to resolve "* Shared GSettings keys" issue listed under https://wiki.ubuntu.com/Unity/NotDefaultIssues. Ubuntu so far is providing session related overrides for both ubuntu & unity sessions in a single package, i.e. ubuntu-settings. But now that Unity is not the default desktop it doesn't make any sense to carry unity related overrides in ubuntu-settings. For this purpose I have created a new project: unity-settings (https://code.launchpad.net/~khurshid-alam/unity-settings/trunk) and the binary would be unity-settings in universe. To make this happen in under 18.04 cycle, the work-flow should be: 1) Have unity-settings in the universe 2) Have ubuntu-unity-desktop in the universe 3) Let ubuntu-unity-desktop depends on unity-settings 4) Drop unity related settings in ubuntu-settings (merge request in-progress) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/1735998/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1736994] Re: [needs-packaging] [MOTU] Have ubuntu-unity-desktop meta package in universe
Alright I will prepare a seed branch. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1736994 Title: [needs-packaging] [MOTU] Have ubuntu-unity-desktop meta package in universe Status in ubuntu-meta package in Ubuntu: Incomplete Bug description: [needs-packaging] ubuntu-unity-desktop ubuntu-unity-desktop is the meta package which installs a fully functional unity desktop. Source: https://code.launchpad.net/~unity7maintainers/ubuntu-unity- meta/+git/ubuntu-unity-meta License: GNU GPL v2 PPA: ppa:unity7maintainers/unity7-desktop Note: Atm, since ubuntu-unity is no an official flavor there is no seed branch on https://code.launchpad.net/ubuntu-seeds. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1736994/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1736994] Re: [MOTU] Have ubuntu-unity-desktop meta package in universe
** Tags removed: ubuntu-sponsors ** Tags added: needs-packaging ** Description changed: + [needs-packaging] ubuntu-unity-desktop + ubuntu-unity-desktop is the meta package which installs a fully functional unity desktop. Source: https://code.launchpad.net/~unity7maintainers/ubuntu-unity- meta/+git/ubuntu-unity-meta + License: GNU GPL v2 + PPA: ppa:unity7maintainers/unity7-desktop Note: Atm, since ubuntu-unity is no an official flavor there is no seed branch on https://code.launchpad.net/ubuntu-seeds. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1736994 Title: [MOTU] Have ubuntu-unity-desktop meta package in universe Status in ubuntu-meta package in Ubuntu: New Bug description: [needs-packaging] ubuntu-unity-desktop ubuntu-unity-desktop is the meta package which installs a fully functional unity desktop. Source: https://code.launchpad.net/~unity7maintainers/ubuntu-unity- meta/+git/ubuntu-unity-meta License: GNU GPL v2 PPA: ppa:unity7maintainers/unity7-desktop Note: Atm, since ubuntu-unity is no an official flavor there is no seed branch on https://code.launchpad.net/ubuntu-seeds. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1736994/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1735998] Re: Decouple unity related settings as unity-settings
** Description changed: This is an attempt to resolve "* Shared GSettings keys" issue listed under https://wiki.ubuntu.com/Unity/NotDefaultIssues. Ubuntu so far is providing session related overrides for both ubuntu & unity sessions in a single package, i.e. ubuntu-settings. But now that - Unity is no the default desktop it doesn't make any sense to carry unity - related overrides in ubuntu-settings. + Unity is not the default desktop it doesn't make any sense to carry + unity related overrides in ubuntu-settings. For this purpose I have created a new project: unity-settings (https://code.launchpad.net/~khurshid-alam/unity-settings/trunk) and the binary would be unity -settings in universe. To make this happen in under 18.04 cycle, the work-flow should be: 1) Have unity-settings in the universe 2) Have ubuntu-unity-desktop in the universe 3) Let ubuntu-unity-desktop depends on unity-settings 4) Drop unity related settings in ubuntu-settings (merge request in-progress) ** Description changed: This is an attempt to resolve "* Shared GSettings keys" issue listed under https://wiki.ubuntu.com/Unity/NotDefaultIssues. Ubuntu so far is providing session related overrides for both ubuntu & unity sessions in a single package, i.e. ubuntu-settings. But now that Unity is not the default desktop it doesn't make any sense to carry unity related overrides in ubuntu-settings. For this purpose I have created a new project: unity-settings (https://code.launchpad.net/~khurshid-alam/unity-settings/trunk) and the - binary would be unity -settings in universe. + binary would be unity-settings in universe. To make this happen in under 18.04 cycle, the work-flow should be: 1) Have unity-settings in the universe 2) Have ubuntu-unity-desktop in the universe 3) Let ubuntu-unity-desktop depends on unity-settings 4) Drop unity related settings in ubuntu-settings (merge request in-progress) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1735998 Title: Decouple unity related settings as unity-settings Status in ubuntu-settings package in Ubuntu: Confirmed Bug description: This is an attempt to resolve "* Shared GSettings keys" issue listed under https://wiki.ubuntu.com/Unity/NotDefaultIssues. Ubuntu so far is providing session related overrides for both ubuntu & unity sessions in a single package, i.e. ubuntu-settings. But now that Unity is not the default desktop it doesn't make any sense to carry unity related overrides in ubuntu-settings. For this purpose I have created a new project: unity-settings (https://code.launchpad.net/~khurshid-alam/unity-settings/trunk) and the binary would be unity-settings in universe. To make this happen in under 18.04 cycle, the work-flow should be: 1) Have unity-settings in the universe 2) Have ubuntu-unity-desktop in the universe 3) Let ubuntu-unity-desktop depends on unity-settings 4) Drop unity related settings in ubuntu-settings (merge request in-progress) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/1735998/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1736994] [NEW] [MOTU] Have ubuntu-unity-desktop meta package in universe
Public bug reported: ubuntu-unity-desktop is the meta package which installs a fully functional unity desktop. Source: https://code.launchpad.net/~unity7maintainers/ubuntu-unity- meta/+git/ubuntu-unity-meta PPA: ppa:unity7maintainers/unity7-desktop Note: Atm, since ubuntu-unity is no an official flavor there is no seed branch on https://code.launchpad.net/ubuntu-seeds. ** Affects: ubuntu-meta (Ubuntu) Importance: Undecided Status: New ** Tags: bionic needs-packaging ** Tags added: bionic ** Tags added: ubuntu-sponsors -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1736994 Title: [MOTU] Have ubuntu-unity-desktop meta package in universe Status in ubuntu-meta package in Ubuntu: New Bug description: ubuntu-unity-desktop is the meta package which installs a fully functional unity desktop. Source: https://code.launchpad.net/~unity7maintainers/ubuntu-unity- meta/+git/ubuntu-unity-meta PPA: ppa:unity7maintainers/unity7-desktop Note: Atm, since ubuntu-unity is no an official flavor there is no seed branch on https://code.launchpad.net/ubuntu-seeds. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1736994/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1735998] Re: Decouple unity related settings as unity-settings
** Changed in: ubuntu-settings (Ubuntu) Status: New => Confirmed ** Changed in: ubuntu-settings (Ubuntu) Assignee: (unassigned) => Khurshid Alam (khurshid-alam) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1735998 Title: Decouple unity related settings as unity-settings Status in ubuntu-settings package in Ubuntu: Confirmed Bug description: This is an attempt to resolve "* Shared GSettings keys" issue listed under https://wiki.ubuntu.com/Unity/NotDefaultIssues. Ubuntu so far is providing session related overrides for both ubuntu & unity sessions in a single package, i.e. ubuntu-settings. But now that Unity is no the default desktop it doesn't make any sense to carry unity related overrides in ubuntu-settings. For this purpose I have created a new project: unity-settings (https://code.launchpad.net/~khurshid-alam/unity-settings/trunk) and the binary would be unity -settings in universe. To make this happen in under 18.04 cycle, the work-flow should be: 1) Have unity-settings in the universe 2) Have ubuntu-unity-desktop in the universe 3) Let ubuntu-unity-desktop depends on unity-settings 4) Drop unity related settings in ubuntu-settings (merge request in-progress) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/1735998/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1735998] [NEW] Decouple unity related settings as unity-settings
Public bug reported: This is an attempt to resolve "* Shared GSettings keys" issue listed under https://wiki.ubuntu.com/Unity/NotDefaultIssues. Ubuntu so far is providing session related overrides for both ubuntu & unity sessions in a single package, i.e. ubuntu-settings. But now that Unity is no the default desktop it doesn't make any sense to carry unity related overrides in ubuntu-settings. For this purpose I have created a new project: unity-settings (https://code.launchpad.net/~khurshid-alam/unity-settings/trunk) and the binary would be unity -settings in universe. To make this happen in under 18.04 cycle, the work-flow should be: 1) Have unity-settings in the universe 2) Have ubuntu-unity-desktop in the universe 3) Let ubuntu-unity-desktop depends on unity-settings 4) Drop unity related settings in ubuntu-settings (merge request in-progress) ** Affects: ubuntu-settings (Ubuntu) Importance: Undecided Status: New ** Tags: bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1735998 Title: Decouple unity related settings as unity-settings Status in ubuntu-settings package in Ubuntu: New Bug description: This is an attempt to resolve "* Shared GSettings keys" issue listed under https://wiki.ubuntu.com/Unity/NotDefaultIssues. Ubuntu so far is providing session related overrides for both ubuntu & unity sessions in a single package, i.e. ubuntu-settings. But now that Unity is no the default desktop it doesn't make any sense to carry unity related overrides in ubuntu-settings. For this purpose I have created a new project: unity-settings (https://code.launchpad.net/~khurshid-alam/unity-settings/trunk) and the binary would be unity -settings in universe. To make this happen in under 18.04 cycle, the work-flow should be: 1) Have unity-settings in the universe 2) Have ubuntu-unity-desktop in the universe 3) Let ubuntu-unity-desktop depends on unity-settings 4) Drop unity related settings in ubuntu-settings (merge request in-progress) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/1735998/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1722713] Re: Hud spams systeem-log with "No such interface 'com.canonical.dbusmenu' (Artful)
** Summary changed: - Hud spams systeem-log with "No such interface 'com.canonical.dbusmenu' + Hud spams systeem-log with "No such interface 'com.canonical.dbusmenu' (Artful) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to hud in Ubuntu. https://bugs.launchpad.net/bugs/1722713 Title: Hud spams systeem-log with "No such interface 'com.canonical.dbusmenu' (Artful) Status in hud package in Ubuntu: New Bug description: For gtk-header apps, hud spams system-log like: #033[31mvoid DBusMenuImporter::slotGetLayoutFinished(QDBusPendingCallWatcher*)#033[0m: "No such interface 'com.canonical.dbusmenu' on object at path /org/ayatana/bamf/window/62914572" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hud/+bug/1722713/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1722713] [NEW] Hud spams systeem-log with "No such interface 'com.canonical.dbusmenu' (Artful)
Public bug reported: For gtk-header apps, hud spams system-log like: #033[31mvoid DBusMenuImporter::slotGetLayoutFinished(QDBusPendingCallWatcher*)#033[0m: "No such interface 'com.canonical.dbusmenu' on object at path /org/ayatana/bamf/window/62914572" ** Affects: hud (Ubuntu) Importance: Undecided Status: New ** Tags: artful -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to hud in Ubuntu. https://bugs.launchpad.net/bugs/1722713 Title: Hud spams systeem-log with "No such interface 'com.canonical.dbusmenu' (Artful) Status in hud package in Ubuntu: New Bug description: For gtk-header apps, hud spams system-log like: #033[31mvoid DBusMenuImporter::slotGetLayoutFinished(QDBusPendingCallWatcher*)#033[0m: "No such interface 'com.canonical.dbusmenu' on object at path /org/ayatana/bamf/window/62914572" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hud/+bug/1722713/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1708375] Re: Add support for purple-telegram (telepathy-haze)
Patch updated
** Patch added: "telepathy-purple.patch"
https://bugs.launchpad.net/ubuntu/+source/telepathy-mission-control-5/+bug/1708375/+attachment/4955775/+files/telepathy-purple.patch
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to telepathy-mission-
control-5 in Ubuntu.
https://bugs.launchpad.net/bugs/1708375
Title:
Add support for purple-telegram (telepathy-haze)
Status in telepathy-mission-control-5 package in Ubuntu:
Confirmed
Bug description:
When using purple telegram through telepathy-haze, it requires
following permissions:
# for purple telegram
/etc/telegram-purple/server.tglpub r,
/usr/lib/purple-2*/ r,
/usr/lib/purple-2/*.somr,
/usr/share/locale/*/LC_MESSAGES/*.mo r,
/usr/share/pixmaps/pidgin/protocols/{16,32,48}/*.png r,
@{HOME}/.purple/telegram-purple/** rw,
@{HOME}/.telegram-purple/** rw,
under /usr/lib/telepathy/telepathy-* section. See issue
https://github.com/majn/telegram-purple/issues/346 for more details.
I have attached the necessary patch
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/telepathy-mission-control-5/+bug/1708375/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1717239] [NEW] unity-session should depend on notify-osd (Artful)
Public bug reported: >From live iso, if I install unity-session it doesn't install notify-osd by default. This prevents users from viewing critical notification. Please make unity-session depends on notify-osd. Thanks. ** Affects: ubuntu-meta (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: artful unity ** Changed in: ubuntu-meta (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1717239 Title: unity-session should depend on notify-osd (Artful) Status in ubuntu-meta package in Ubuntu: Confirmed Bug description: From live iso, if I install unity-session it doesn't install notify- osd by default. This prevents users from viewing critical notification. Please make unity-session depends on notify-osd. Thanks. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1717239/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1695928] Re: Please remove obsolete UOA packages
@Dimitry I will maintain it in PPA, once this gets fixed. bug #1706682 I asked the debian maintainer to create a transitional package of qtdeclarative5-gsettings1.0 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to account-plugins in Ubuntu. https://bugs.launchpad.net/bugs/1695928 Title: Please remove obsolete UOA packages Status in account-plugins package in Ubuntu: Fix Released Status in gnome-control-center-signon package in Ubuntu: Fix Released Status in mcloud package in Ubuntu: Fix Released Status in online-accounts-api package in Ubuntu: Fix Released Status in storage-framework package in Ubuntu: Fix Released Bug description: Ubuntu Online Accounts is no longer maintained. There is an alternative, GNOME Online Accounts for the GNOME desktop. Also, Unity's Online Accounts settings panel does not currently work without oxide-qt but oxide-qt will be removed from Ubuntu 17.10. Please remove these source packages and their binaries: = Phase 1 --- gnome-control-center-signon account-plugins account-plugin-fitbit bug 1707794 account-polld (pay-service removed) (qtpurchasing-opensource-src removed) storage-provider-webdav bug 1707799 (sync-monitor removed) ubuntuone-credentials bug 1707798 (ubuntu-push removed) unity-china-photo-scope unity-scope-gdrive bug 1707796 By the way, gnome-control-center-signon fails to build with vala 0.36: https://launchpadlibrarian.net/324396241/buildlog_ubuntu-artful-amd64.gnome-control-center-signon_0.1.9+16.10.20160825-0ubuntu1~ubuntu17.10.1_BUILDING.txt.gz Phase 2 --- ubuntu-system-settings-online-accounts online-accounts-api storage-framework keeper #1707801 mcloud (address-book-app removed) address-book-service (dialer-app removed) (messaging-app removed) telephony-service bug 1707802 tone-generator bug 1707802 ubuntu-system-settings buteo-sync-plugins-contacts-google (camera-app removed) indicator-transfer indicator-transfer-buteo libertine (ubuntu-experience-tests removed) unity-scopes-shell bug 1707797 (unity8 removed) Other Notes --- The Shotwell suggests have been dropped in artful-proposed. Shotwell is temporarily stuck in -proposed because of an autopkgtest issue https://bugzilla.gnome.org/781802 Kubuntu still uses signon-ui. See also https://code.launchpad.net/~xnox/ubuntu- seeds/unity8-removals/+merge/323615 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/account-plugins/+bug/1695928/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1695928] Re: Please remove obsolete UOA packages
I believe we talked about keeping account-plugins in the repo for artful cycle, so that apps which uses signon libraries can still use it while porting away to something else. ? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to account-plugins in Ubuntu. https://bugs.launchpad.net/bugs/1695928 Title: Please remove obsolete UOA packages Status in account-plugins package in Ubuntu: Fix Released Status in gnome-control-center-signon package in Ubuntu: Fix Released Status in mcloud package in Ubuntu: Fix Released Status in online-accounts-api package in Ubuntu: Fix Released Status in storage-framework package in Ubuntu: Fix Released Bug description: Ubuntu Online Accounts is no longer maintained. There is an alternative, GNOME Online Accounts for the GNOME desktop. Also, Unity's Online Accounts settings panel does not currently work without oxide-qt but oxide-qt will be removed from Ubuntu 17.10. Please remove these source packages and their binaries: = Phase 1 --- gnome-control-center-signon account-plugins account-plugin-fitbit bug 1707794 account-polld (pay-service removed) (qtpurchasing-opensource-src removed) storage-provider-webdav bug 1707799 (sync-monitor removed) ubuntuone-credentials bug 1707798 (ubuntu-push removed) unity-china-photo-scope unity-scope-gdrive bug 1707796 By the way, gnome-control-center-signon fails to build with vala 0.36: https://launchpadlibrarian.net/324396241/buildlog_ubuntu-artful-amd64.gnome-control-center-signon_0.1.9+16.10.20160825-0ubuntu1~ubuntu17.10.1_BUILDING.txt.gz Phase 2 --- ubuntu-system-settings-online-accounts online-accounts-api storage-framework keeper #1707801 mcloud (address-book-app removed) address-book-service (dialer-app removed) (messaging-app removed) telephony-service bug 1707802 tone-generator bug 1707802 ubuntu-system-settings buteo-sync-plugins-contacts-google (camera-app removed) indicator-transfer indicator-transfer-buteo libertine (ubuntu-experience-tests removed) unity-scopes-shell bug 1707797 (unity8 removed) Other Notes --- The Shotwell suggests have been dropped in artful-proposed. Shotwell is temporarily stuck in -proposed because of an autopkgtest issue https://bugzilla.gnome.org/781802 Kubuntu still uses signon-ui. See also https://code.launchpad.net/~xnox/ubuntu- seeds/unity8-removals/+merge/323615 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/account-plugins/+bug/1695928/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1670269] Re: Add com.ubuntu.usbcreator.format for usb creator action
I believe latest usb-gtk-creator doesn't use this function at all instead open the whole gui with pkexec, and hence not compatible with wayland. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to policykit-desktop- privileges in Ubuntu. https://bugs.launchpad.net/bugs/1670269 Title: Add com.ubuntu.usbcreator.format for usb creator action Status in policykit-desktop-privileges package in Ubuntu: Confirmed Bug description: Usb creator still asks for password when formatting or trying to install boot-loader. If user doesn't respond within a sepecific time, it fails and user has to start the process all over again. Adding "com.ubuntu.usbcreator.format" to Action solves the issue. ### PATCH - --- a/com.ubuntu.desktop.pkla +++ b/com.ubuntu.desktop.pkla @@ -25,7 +25,7 @@ [usb-creator] Identity=unix-group:admin;unix-group:sudo -Action=com.ubuntu.usbcreator.mount;com.ubuntu.usbcreator.image +Action=com.ubuntu.usbcreator.mount;com.ubuntu.usbcreator.image;com.ubuntu.usbcreator.format ResultActive=yes [Printer administration] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/policykit-desktop-privileges/+bug/1670269/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1710926] [NEW] Build failing against qt 5.9 and python 3.6 on artful
Public bug reported: I am getting following error: ubuntu-ui- toolkit-1.3.2190+17.04.20170327ubuntu1/tests/autopilot/ubuntuuitoolkit/_custom_proxy_objects/_qquicklistview.py:179:9: E722 do not use bare except ubuntu-ui-toolkit-1.3.2190+17.04.20170327ubuntu1/tests/autopilot/ubuntuuitoolkit/_custom_proxy_objects/_uclistitem.py:52:9: E722 do not use bare except It seems to be related with latest pycodestyle version 2.3.0 (2017-01-30) which was added the new E722 check: Add E722 warning for bare except clauses ** Affects: ubuntu-ui-toolkit (Ubuntu) Importance: Undecided Status: New ** Tags: artful -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1710926 Title: Build failing against qt 5.9 and python 3.6 on artful Status in ubuntu-ui-toolkit package in Ubuntu: New Bug description: I am getting following error: ubuntu-ui- toolkit-1.3.2190+17.04.20170327ubuntu1/tests/autopilot/ubuntuuitoolkit/_custom_proxy_objects/_qquicklistview.py:179:9: E722 do not use bare except ubuntu-ui-toolkit-1.3.2190+17.04.20170327ubuntu1/tests/autopilot/ubuntuuitoolkit/_custom_proxy_objects/_uclistitem.py:52:9: E722 do not use bare except It seems to be related with latest pycodestyle version 2.3.0 (2017-01-30) which was added the new E722 check: Add E722 warning for bare except clauses To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1710926/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1708375] Re: Add support for purple-telegram (telepathy-haze)
Updated
** Changed in: telepathy-mission-control-5 (Ubuntu)
Status: New => Confirmed
** Patch added: "telepathy-purple.patch"
https://bugs.launchpad.net/ubuntu/+source/telepathy-mission-control-5/+bug/1708375/+attachment/4928529/+files/telepathy-purple.patch
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to telepathy-mission-
control-5 in Ubuntu.
https://bugs.launchpad.net/bugs/1708375
Title:
Add support for purple-telegram (telepathy-haze)
Status in telepathy-mission-control-5 package in Ubuntu:
Confirmed
Bug description:
When using purple telegram through telepathy-haze, it requires
following permissions:
# for purple telegram
/etc/telegram-purple/server.tglpub r,
/usr/lib/purple-2*/ r,
/usr/lib/purple-2/*.somr,
/usr/share/locale/*/LC_MESSAGES/*.mo r,
/usr/share/pixmaps/pidgin/protocols/{16,32,48}/*.png r,
@{HOME}/.purple/telegram-purple/** rw,
@{HOME}/.telegram-purple/** rw,
under /usr/lib/telepathy/telepathy-* section. See issue
https://github.com/majn/telegram-purple/issues/346 for more details.
I have attached the necessary patch
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/telepathy-mission-control-5/+bug/1708375/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1708375] Re: Add support for purple-telegram (telepathy-haze)
> - I don't understand the line `/usr/lib/purple-2*/`.
You are right. Telegram-purple only creates /usr/lib/purple-2/, so
asterix can be removed. In fact I think we don't need
"/usr/lib/purple-2*/ r", as "/usr/lib/purple-2/*.so mr", will do the
job.
> telegram-purple is supposed to detect telepathy, and avoid the path
> `@{HOME}/.purple/telegram-purple/`. Was it really necessary?
It should but it doesn't at the moment.
And yes, it is necessary with 1.3.x. The plugin stores data after
authentication in either @{HOME}/.purple/telegram-purple/ or @{HOME
}/.telegram-purple/ depending on plugin version number. So telepathy-
haze would require read/write access to that folder, otherwise apparmor
give access-denied and users have to re-authenticate each time after
opening the client (empathy).
I will update the patch. Thanks.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to telepathy-mission-
control-5 in Ubuntu.
https://bugs.launchpad.net/bugs/1708375
Title:
Add support for purple-telegram (telepathy-haze)
Status in telepathy-mission-control-5 package in Ubuntu:
New
Bug description:
When using purple telegram through telepathy-haze, it requires
following permissions:
# for purple telegram
/etc/telegram-purple/server.tglpub r,
/usr/lib/purple-2*/ r,
/usr/lib/purple-2/*.somr,
/usr/share/locale/*/LC_MESSAGES/*.mo r,
/usr/share/pixmaps/pidgin/protocols/{16,32,48}/*.png r,
@{HOME}/.purple/telegram-purple/** rw,
@{HOME}/.telegram-purple/** rw,
under /usr/lib/telepathy/telepathy-* section. See issue
https://github.com/majn/telegram-purple/issues/346 for more details.
I have attached the necessary patch
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/telepathy-mission-control-5/+bug/1708375/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1708375] [NEW] Add support for purple-telegram (telepathy-haze)
Public bug reported:
When using purple telegram through telepathy-haze, it requires following
permissions:
# for purple telegram
/etc/telegram-purple/server.tglpub r,
/usr/lib/purple-2*/ r,
/usr/lib/purple-2/*.so mr,
/usr/share/locale/*/LC_MESSAGES/*.mo r,
/usr/share/pixmaps/pidgin/protocols/{16,32,48}/*.png r,
@{HOME}/.purple/telegram-purple/** rw,
@{HOME}/.telegram-purple/** rw,
under /usr/lib/telepathy/telepathy-* section. See issue
https://github.com/majn/telegram-purple/issues/346 for more details.
I have attached the necessary patch
** Affects: telepathy-mission-control-5 (Ubuntu)
Importance: Undecided
Status: New
** Tags: artful patch
** Attachment added: "telepathy-purple.patch"
https://bugs.launchpad.net/bugs/1708375/+attachment/4926407/+files/telepathy-purple.patch
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to telepathy-mission-
control-5 in Ubuntu.
https://bugs.launchpad.net/bugs/1708375
Title:
Add support for purple-telegram (telepathy-haze)
Status in telepathy-mission-control-5 package in Ubuntu:
New
Bug description:
When using purple telegram through telepathy-haze, it requires
following permissions:
# for purple telegram
/etc/telegram-purple/server.tglpub r,
/usr/lib/purple-2*/ r,
/usr/lib/purple-2/*.somr,
/usr/share/locale/*/LC_MESSAGES/*.mo r,
/usr/share/pixmaps/pidgin/protocols/{16,32,48}/*.png r,
@{HOME}/.purple/telegram-purple/** rw,
@{HOME}/.telegram-purple/** rw,
under /usr/lib/telepathy/telepathy-* section. See issue
https://github.com/majn/telegram-purple/issues/346 for more details.
I have attached the necessary patch
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/telepathy-mission-control-5/+bug/1708375/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1688395] Re: Remove Oxide, webbrowser-app and the Unity webapps
Not sure why oxide is being removed. Various qt-apps/oauth2-gui (search in kubuntu's ppa, getdeb) are still using it. Didn't you get any objection from them? If it is compiling just fine with qt-5.9 (it does, I checked), Ubuntu should keep it in universe. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1688395 Title: Remove Oxide, webbrowser-app and the Unity webapps Status in libunity-webapps package in Ubuntu: Triaged Status in oxide-qt package in Ubuntu: Triaged Status in webbrowser-app package in Ubuntu: Triaged Bug description: These projects are discontinued, unsupported and should be removed. I haven't done any analysis of the deps or rdeps to find out if there is more to cull, or if there is some untangling to do. I know of two tasks other than removing packages - Unity ships an Amazon launcher in its preset favourites which launches a binary from unity-webapps-service. That should be removed. We need to keep providing the Amazon launcher by default (in GNOME Shell) - it should be reimplemented and added to Shell by default. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libunity-webapps/+bug/1688395/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1702794] Re: Please add module-switch-on-connect to default.pa
@Daniel It was working with 1:10.0-1ubuntu2. Now most times a2dp profile is unavailable or I can't switch it to it. Anyway I will file a new bug. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1702794 Title: Please add module-switch-on-connect to default.pa Status in pulseaudio package in Ubuntu: Fix Released Bug description: This way once a user pairs & connects a bluetooth speaker device pulseaudio will auto switch to it. As it stands now users have to open sound settings & switch manually. It's bad enough that auto discover & connect don't work, (can be scripted thru bluetoothctl), no sense adding to frustration In the ### Automatically load driver modules for Bluetooth hardware section .ifexists module-switch-on-connect.so load-module module-switch-on-connect .endif ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: pulseaudio 1:8.0-0ubuntu3.3 ProcVersionSignature: Ubuntu 4.8.0-56.61~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-56-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: doug 1843 F pulseaudio /dev/snd/controlC0: doug 1843 F pulseaudio CurrentDesktop: Unity Date: Thu Jul 6 20:02:15 2017 SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/18/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 74CN44WW(V3.05) dmi.board.asset.tag: No Asset Tag dmi.board.name: VIQY0Y1 dmi.board.vendor: LENOVO dmi.board.version: 31900058STD dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo IdeaPad Y510P dmi.modalias: dmi:bvnLENOVO:bvr74CN44WW(V3.05):bd09/18/2013:svnLENOVO:pn20217:pvrLenovoIdeaPadY510P:rvnLENOVO:rnVIQY0Y1:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoIdeaPadY510P: dmi.product.name: 20217 dmi.product.version: Lenovo IdeaPad Y510P dmi.sys.vendor: LENOVO modified.conffile..etc.pulse.default.pa: [modified] mtime.conffile..etc.pulse.default.pa: 2017-07-04T13:42:27.651527 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1702794/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1702794] Re: Please add module-switch-on-connect to default.pa
After this my bluetooth speaker simply refuses to switch to a2dp_sink profile. It always stays at hsp no mater what I do. So far it wasn't enabled exactly for that reason. Read https://bugs.freedesktop.org/show_bug.cgi?id=93898 and https://bugs.freedesktop.org/show_bug.cgi?id=73325#c52 ** Bug watch added: freedesktop.org Bugzilla #93898 https://bugs.freedesktop.org/show_bug.cgi?id=93898 ** Bug watch added: freedesktop.org Bugzilla #73325 https://bugs.freedesktop.org/show_bug.cgi?id=73325 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1702794 Title: Please add module-switch-on-connect to default.pa Status in pulseaudio package in Ubuntu: Fix Released Bug description: This way once a user pairs & connects a bluetooth speaker device pulseaudio will auto switch to it. As it stands now users have to open sound settings & switch manually. It's bad enough that auto discover & connect don't work, (can be scripted thru bluetoothctl), no sense adding to frustration In the ### Automatically load driver modules for Bluetooth hardware section .ifexists module-switch-on-connect.so load-module module-switch-on-connect .endif ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: pulseaudio 1:8.0-0ubuntu3.3 ProcVersionSignature: Ubuntu 4.8.0-56.61~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-56-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: doug 1843 F pulseaudio /dev/snd/controlC0: doug 1843 F pulseaudio CurrentDesktop: Unity Date: Thu Jul 6 20:02:15 2017 SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/18/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 74CN44WW(V3.05) dmi.board.asset.tag: No Asset Tag dmi.board.name: VIQY0Y1 dmi.board.vendor: LENOVO dmi.board.version: 31900058STD dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo IdeaPad Y510P dmi.modalias: dmi:bvnLENOVO:bvr74CN44WW(V3.05):bd09/18/2013:svnLENOVO:pn20217:pvrLenovoIdeaPadY510P:rvnLENOVO:rnVIQY0Y1:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoIdeaPadY510P: dmi.product.name: 20217 dmi.product.version: Lenovo IdeaPad Y510P dmi.sys.vendor: LENOVO modified.conffile..etc.pulse.default.pa: [modified] mtime.conffile..etc.pulse.default.pa: 2017-07-04T13:42:27.651527 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1702794/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1670269] Re: Add com.ubuntu.usbcreator.format for usb creator action
** Tags added: julyshakedown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to policykit-desktop- privileges in Ubuntu. https://bugs.launchpad.net/bugs/1670269 Title: Add com.ubuntu.usbcreator.format for usb creator action Status in policykit-desktop-privileges package in Ubuntu: Confirmed Bug description: Usb creator still asks for password when formatting or trying to install boot-loader. If user doesn't respond within a sepecific time, it fails and user has to start the process all over again. Adding "com.ubuntu.usbcreator.format" to Action solves the issue. ### PATCH - --- a/com.ubuntu.desktop.pkla +++ b/com.ubuntu.desktop.pkla @@ -25,7 +25,7 @@ [usb-creator] Identity=unix-group:admin;unix-group:sudo -Action=com.ubuntu.usbcreator.mount;com.ubuntu.usbcreator.image +Action=com.ubuntu.usbcreator.mount;com.ubuntu.usbcreator.image;com.ubuntu.usbcreator.format ResultActive=yes [Printer administration] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/policykit-desktop-privileges/+bug/1670269/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
