[Touch-packages] [Bug 1794064] Re: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap
** Also affects: evince (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: apparmor (Ubuntu Lunar) Importance: Undecided Status: New ** Changed in: evince (Ubuntu Lunar) Status: New => Confirmed ** Changed in: apparmor (Ubuntu Lunar) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1794064 Title: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap Status in apparmor package in Ubuntu: Confirmed Status in evince package in Ubuntu: Confirmed Status in apparmor source package in Jammy: Confirmed Status in evince source package in Jammy: Confirmed Status in apparmor source package in Lunar: Confirmed Status in evince source package in Lunar: Confirmed Status in evince package in Debian: Confirmed Bug description: [Impact] * Users cannot open a hyperlink in a PDF opened with evince when the default browser is a snap. * The fix creates a snap_browsers abstraction on AppArmor which can be used in a transition for when the browser is executed. The snap_browsers abstraction provides the minimal amount of permissions required to execute a browser provided through snaps. This is a workaround since AppArmor currently does not provide mediation/filtering on enhanced environment variables. [Test Plan] * Make sure the default browser is provided through the snap store. * Open a PDF that contains a hyperlink using evince and click on the URL. * The browser should open the requested URL. [Where problems could occur] * If the browser or snap core update to have new requirements for opening a browser, then the current policy could become obsolete and will need to be updated again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1794064/+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 1794064] Re: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap
** Changed in: evince (Ubuntu) Status: Incomplete => Confirmed ** Changed in: evince (Ubuntu Jammy) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1794064 Title: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap Status in apparmor package in Ubuntu: Confirmed Status in evince package in Ubuntu: Confirmed Status in apparmor source package in Jammy: Confirmed Status in evince source package in Jammy: Confirmed Status in evince package in Debian: Confirmed Bug description: [Impact] * Users cannot open a hyperlink in a PDF opened with evince when the default browser is a snap. * The fix creates a snap_browsers abstraction on AppArmor which can be used in a transition for when the browser is executed. The snap_browsers abstraction provides the minimal amount of permissions required to execute a browser provided through snaps. This is a workaround since AppArmor currently does not provide mediation/filtering on enhanced environment variables. [Test Plan] * Make sure the default browser is provided through the snap store. * Open a PDF that contains a hyperlink using evince and click on the URL. * The browser should open the requested URL. [Where problems could occur] * If the browser or snap core update to have new requirements for opening a browser, then the current policy could become obsolete and will need to be updated again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1794064/+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 1922464] Re: GNOME 40: GTK3 apps crash with: Settings schema 'org.gnome.settings-daemon.plugins.xsettings' does not contain a key named 'antialiasing'
Snaps which use the gnome-38 snapcraft extension wouldn't be affected, but snaps that use gnome-3-34 may. -- 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/1922464 Title: GNOME 40: GTK3 apps crash with: Settings schema 'org.gnome.settings- daemon.plugins.xsettings' does not contain a key named 'antialiasing' Status in gtk+3.0 package in Ubuntu: Fix Released Status in gtk+3.0 source package in Focal: Triaged Bug description: Applications running with GTK < 3.24.26 crash when running under GNOME 40. This was fixed in GTK 3.24.26 by MR https://gitlab.gnome.org/GNOME/gtk/-/merge_requests/3219 Please package either current GTK 3 (3.24.28) or include the given MR in the current build. Thanks! Example crash: ``` Starting program: /home/mjog/Projects/GNOME/geary/+build/test/test-client [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [New Thread 0x7fffeb8a7640 (LWP 58239)] [New Thread 0x7fffeb086640 (LWP 58240)] [New Thread 0x7fffea839640 (LWP 58241)] (test-client:58235): GLib-GIO-ERROR **: 10:42:55.448: Settings schema 'org.gnome.settings-daemon.plugins.xsettings' does not contain a key named 'antialiasing' Thread 1 "test-client" received signal SIGTRAP, Trace/breakpoint trap. 0x774a5ea7 in g_log_structured_array () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 (gdb) bt #0 0x774a5ea7 in g_log_structured_array () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x774a62b9 in g_log_default_handler () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x774a64fe in g_logv () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x774a67b3 in g_log () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7735d9d1 in () at /lib/x86_64-linux-gnu/libgio-2.0.so.0 #5 0x7735e030 in () at /lib/x86_64-linux-gnu/libgio-2.0.so.0 #6 0x773625d1 in g_settings_get_enum () at /lib/x86_64-linux-gnu/libgio-2.0.so.0 #7 0x710d90ea in update_xft_settings (screen=0x55a8d810) at wayland/../../../../../gdk/wayland/gdkscreen-wayland.c:404 #8 0x710d3c7d in init_settings (screen=0x55a8d810) at wayland/../../../../../gdk/wayland/gdkscreen-wayland.c:828 #9 _gdk_wayland_screen_new (display=0x55a8a0e0) at wayland/../../../../../gdk/wayland/gdkscreen-wayland.c:1320 #10 _gdk_wayland_display_open (display_name=) at wayland/../../../../../gdk/wayland/gdkdisplay-wayland.c:617 #11 0x71072635 in gdk_display_manager_open_display (manager=, name=0x0) at ../../../../gdk/gdkdisplaymanager.c:462 #12 0x76d011fb in gtk_init_check (argc=, argv=) at ../../../../gtk/gtkmain.c:1110 #13 gtk_init_check (argc=, argv=) at ../../../../gtk/gtkmain.c:1102 #14 0x76d0122d in gtk_init (argc=, argv=) at ../../../../gtk/gtkmain.c:1167 #15 0x555b4854 in _vala_main (args=0x7fffdda8, args_length1=1) at ../test/test-client.vala:32 #16 0x555b5213 in main (argc=1, argv=0x7fffdda8) at ../test/test-client.vala:9 ``` ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: libgtk-3-0 3.24.25-1ubuntu3 ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7 Uname: Linux 5.11.0-13-generic x86_64 ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Sun Apr 4 11:11:05 2021 InstallationDate: Installed on 2018-08-13 (964 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gtk+3.0 UpgradeStatus: Upgraded to hirsute on 2021-04-03 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1922464/+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 1934199] Re: Switch from Livepatch service to UA client
@robert-ancell: IIRC you had some code for this already? Or am I misremembering it? ** Changed in: software-properties (Ubuntu Focal) Assignee: (unassigned) => Robert Ancell (robert-ancell) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1934199 Title: Switch from Livepatch service to UA client Status in software-properties package in Ubuntu: New Status in software-properties source package in Xenial: New Status in software-properties source package in Bionic: New Status in software-properties source package in Focal: New Status in software-properties source package in Hirsute: New Status in software-properties source package in Impish: Won't Fix Bug description: software-properties currently uses a HTTP over Unix domain socket service from the livepatch snap to get the status and enable/disable it. This service is being deprecated with the 'ua' command line tool now providing this functionality. software-properties also installed the snap to gain access to this service. This is no longer required as the 'ua' tool does this. (*) The Livepatch service is a HTTP over Unix domain service running on livepatchd.sock inside the livepatch snap. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1934199/+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 1933828] Re: NTP servers from DHCP are not propagated to timesyncd
** Summary changed: - NTP servers from DCHP are not propagated to timesyncd + NTP servers from DHCP are not propagated to timesyncd ** Changed in: network-manager (Ubuntu) Assignee: (unassigned) => Heather Ellsworth (hellsworth) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1933828 Title: NTP servers from DHCP are not propagated to timesyncd Status in network-manager package in Ubuntu: New Bug description: Network manager gets NTP servers from DHCP but do not update timesyncd to use it which keeps using ntp.ubuntu.com. This is a problem on private networks which do not have access to public internet. On this type of network the configuration of timesyncd must be updated manually instead of inheriting the conf from the dhcp servers. This can be integrated with a NM dispatcher script such as below: etc/NetworkManager/dispatcher.d/10-update-timesyncd for example: ==8<=8<=8<=8<=8<== #! /usr/bin/bash [ -n "$CONNECTION_UUID" ] || exit INTERFACE=$1 ACTION=$2 case $ACTION in up | dhcp4-change | dhcp6-change) [ -n "$DHCP4_NTP_SERVERS" ] || exit mkdir -p /etc/systemd/timesyncd.conf.d/ cat< /etc/systemd/timesyncd.conf.d/$CONNECTION_UUID.conf [Time] NTP=$DHCP4_NTP_SERVERS RootDistanceMaxSec=15 EOF systemctl restart systemd-timesyncd ;; down) rm -f /etc/systemd/timesyncd.conf.d/$CONNECTION_UUID.conf systemctl restart systemd-timesyncd ;; esac ==8<=8<=8<=8<=8<== ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: network-manager 1.30.0-1ubuntu3 ProcVersionSignature: Ubuntu 5.11.0-18.19+21.10.1-generic 5.11.17 Uname: Linux 5.11.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu67 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Jun 28 14:08:52 2021 InstallationDate: Installed on 2020-05-31 (393 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200527) RebootRequiredPkgs: linux-image-5.11.0-20-generic linux-base SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.30.0 connected started full enabled enabled disabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1933828/+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 1911802] Re: Video glitches playing hardware accelerated video through VAAPI
** Also affects: mesa (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: mesa (Ubuntu Focal) Assignee: (unassigned) => Timo Aaltonen (tjaalton) ** Tags removed: rls-ff-incoming -- 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/1911802 Title: Video glitches playing hardware accelerated video through VAAPI Status in mesa package in Ubuntu: Fix Released Status in mesa source package in Focal: New Bug description: Same issue as the post here describes: https://gitlab.freedesktop.org/mesa/mesa/-/issues/3681 The video is scaled unevenly in the vertical axis, with a black bar appearing in the bottom of the video window for a few frames. It happens seemingly on all videos able to be hardware decoded, upon starting the video and upon seeking. The regression happened somewhere between 20.0.8-0ubuntu1~20.04.1 and 20.2.6-0ubuntu0.20.04.1 but apparently has been fixed in mesa 20.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1911802/+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 1891478] Re: orca ftbfs in focal (amd64 only)
** Also affects: orca (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: at-spi2-atk (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: orca (Ubuntu Focal) Assignee: (unassigned) => Marcus Tomlinson (marcustomlinson) ** Changed in: orca (Ubuntu Focal) Status: New => In Progress ** Changed in: orca (Ubuntu Focal) Importance: Undecided => High ** Changed in: at-spi2-atk (Ubuntu Focal) Status: New => Fix Committed ** Changed in: at-spi2-atk (Ubuntu Focal) Importance: Undecided => High ** Changed in: at-spi2-atk (Ubuntu) Status: Fix Committed => Invalid ** Changed in: orca (Ubuntu) Status: In Progress => Invalid ** Tags removed: rls-ff-incoming -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to at-spi2-atk in Ubuntu. https://bugs.launchpad.net/bugs/1891478 Title: orca ftbfs in focal (amd64 only) Status in at-spi2-atk package in Ubuntu: Invalid Status in orca package in Ubuntu: Invalid Status in at-spi2-atk source package in Focal: Fix Committed Status in orca source package in Focal: In Progress Bug description: seen in a focal test rebuild: https://launchpad.net/ubuntu/+archive/test-rebuild-20200810-focal-updates/+build/19791402 [...] checking for ATSPI2... yes checking for ATKBRIDGE... no configure: error: Package requirements (atk-bridge-2.0 >= 2.26) were not met: Package 'atk', required by 'atk-bridge-2.0', not found To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/at-spi2-atk/+bug/1891478/+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 1865226] Re: gdm-smartcard pam config needs to be updated for Ubuntu and installed
** Also affects: pam (Ubuntu Groovy) Importance: Undecided Status: Invalid ** Also affects: gdm3 (Ubuntu Groovy) Importance: Low Assignee: Marco Trevisan (Treviño) (3v1n0) Status: Confirmed ** Tags removed: rls-gg-incoming -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pam in Ubuntu. https://bugs.launchpad.net/bugs/1865226 Title: gdm-smartcard pam config needs to be updated for Ubuntu and installed Status in gdm: New Status in gdm3 package in Ubuntu: Confirmed Status in pam package in Ubuntu: Invalid Status in gdm3 source package in Groovy: Confirmed Status in pam source package in Groovy: Invalid Bug description: the pam profile for gdm-smartcard is missing. gdm refuses to login with a smartcard. Looking at ubuntu/+source/gdm3, other pam files are pregenerated into debian/ and installed from there; gdm-smartcard is left out. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gdm3 3.28.3-0ubuntu18.04.4 ProcVersionSignature: Ubuntu 5.3.0-24.26~18.04.2-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Feb 28 14:30:30 2020 InstallationDate: Installed on 2016-05-23 (1376 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.gdm3.Xsession: 2018-04-27T11:41:04.766901 To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1865226/+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 1886854] Re: Race in load-module snap policy check in classic confinement
** Changed in: pulseaudio (Ubuntu) Assignee: (unassigned) => James Henstridge (jamesh) -- 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/1886854 Title: Race in load-module snap policy check in classic confinement Status in pulseaudio package in Ubuntu: New Bug description: SUMMARY = When running a snap in classic confinement, that needs access to PA_COMMAND_LOAD_MODULE and PA_COMMAND_UNLOAD_MODULE. These sometimes succeed and sometimes fail with "Access denied". After running "pacmd unload-module module-snap-policy" and unloading the snap policy module, these work reliably. I have verified this in a fresh install of Ubuntu 20.04 in a VM. STEPS TO REPRODUCE = a) Either build a snap with classic confinement that sends these commands on the pulseaudio native protocol socket. (This is how I found the bug) b) Or, what I did here to easier reproduce, abuse the sandbox of a random classic snap: Download the attached bug.tgz with a minimal reproducer. It contains the source code for a program that sends load and unload commands to pulse. Unfortunately `pacmd` has a pid-file check that fails inside the sandbox and doesn't work. The reproducer does essentially the same as "pacmd load/unload-module" though. (a pre-compiled x64 binary is also included in case you don't have a go compiler and dare to run an untrusted binary in a VM) Unpack the tgz, build it, if necessary with "go mod download && go build" Grab a random classic mode snap to use its sandbox as a test bed: $ sudo snap install atom --classic atom 1.48.0 from Snapcrafters installed Open a shell in its sandbox: snap run --shell atom Navigate to the compiled binary and execute it a few times: user@user-Standard-PC-Q35-ICH9-2009:~/bug$ ./bug 2020/07/08 18:46:10 PulseAudio connection created successfully 2020/07/08 18:46:10 Couldn't load module, error message: PulseAudio error: commandLoadModule -> Access denied user@user-Standard-PC-Q35-ICH9-2009:~/bug$ ./bug 2020/07/08 18:46:11 PulseAudio connection created successfully Loaded Module sucessfully at index: 40 user@user-Standard-PC-Q35-ICH9-2009:~/bug$ ./bug 2020/07/08 18:46:12 PulseAudio connection created successfully Loaded Module sucessfully at index: 41 user@user-Standard-PC-Q35-ICH9-2009:~/bug$ ./bug 2020/07/08 18:46:12 PulseAudio connection created successfully 2020/07/08 18:46:12 Couldn't load module, error message: PulseAudio error: commandLoadModule -> Access denied user@user-Standard-PC-Q35-ICH9-2009:~/bug$ ./bug 2020/07/08 18:46:14 PulseAudio connection created successfully 2020/07/08 18:46:14 Couldn't load module, error message: PulseAudio error: commandLoadModule -> Access denied user@user-Standard-PC-Q35-ICH9-2009:~/bug$ ./bug 2020/07/08 18:46:14 PulseAudio connection created successfully 2020/07/08 18:46:14 Couldn't load module, error message: PulseAudio error: commandLoadModule -> Access denied user@user-Standard-PC-Q35-ICH9-2009:~/bug$ ./bug 2020/07/08 18:46:15 PulseAudio connection created successfully 2020/07/08 18:46:15 Couldn't load module, error message: PulseAudio error: commandLoadModule -> Access denied Succeeds and fails apparently at random. Now from a non-sandboxed shell, run pacmd unload-module module-snap-policy to unload the snap-policy module from pulseaudio, now run ./bug a few more times. It now succeeds reliably, every time. Side note, with the real program on my actual machine, the race seems to behave slightly differently. It seems not to work the first time an application is started, but closing it and reopening it seems to make it work pretty reliably afterwards. Restarting "snapd", causes the following run the snap to fail again. EXPECTED BEHAVIOUR == The pulseaudio snap policy module should correctly determine and enforce it's policy. ACTUAL BEHAVIOUR The pulseaudio snap policy module seemingly at random denies access when the snap has the permissions to do an operation. ADDITIONAL INFORMATION == $ lsb_release -rd Description: Ubuntu 20.04 LTS Release: 20.04 $ apt-cache policy pulseaudio pulseaudio: Installed: 1:13.99.1-1ubuntu3.3 Candidate: 1:13.99.1-1ubuntu3.3 Version table: *** 1:13.99.1-1ubuntu3.3 500 500 http://ch.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:13.99.1-1ubuntu3.2 500 500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages 1:13.99.1-1ubuntu3 500 500 http://ch.archive.ubuntu.com/ubuntu focal/main amd64 Packages To manage
[Touch-packages] [Bug 1864307] Re: Many apps have no icon in Software on Focal
** Changed in: snap-store Status: Fix Committed => Fix Released -- 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/1864307 Title: Many apps have no icon in Software on Focal Status in GNOME Software: Unknown Status in snap-store: Fix Released Status in gnome-software package in Ubuntu: Confirmed Status in ubuntu-meta package in Ubuntu: Fix Released Status in gnome-software source package in Focal: Confirmed Status in ubuntu-meta source package in Focal: Fix Committed Bug description: Many applications have no icon displayed in GNOME Software 3.35.91 on latest Ubuntu Focal. See the attached screenshot. [Impact] * Some apt packages do not include an icon in snap-store [Test Case] * Open snap-store, search for GCompris and confirm there is an appropriate icon [Regression Potential] * Very low. Previous Ubuntu releases including apt-config-icons based on the depends in gnome-software. This just adds an apt config that can be used to fetch icons for apt packages via apt. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-software/+bug/1864307/+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 1864307] Re: Many apps have no icon in Software on Focal
** Description changed: Many applications have no icon displayed in GNOME Software 3.35.91 on latest Ubuntu Focal. See the attached screenshot. + + + [Impact] + + * Some apt packages do not include an icon in snap-store + + [Test Case] + + * Open snap-store, search for GCompris and confirm there is an + appropriate icon + + [Regression Potential] + + * Very low. Previous Ubuntu releases including apt-config-icons based + on the depends in gnome-software. This just adds an apt config that can + be used to fetch icons for apt packages via apt. -- 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/1864307 Title: Many apps have no icon in Software on Focal Status in GNOME Software: Unknown Status in snap-store: Fix Committed Status in gnome-software package in Ubuntu: Confirmed Status in ubuntu-meta package in Ubuntu: Confirmed Status in gnome-software source package in Focal: New Status in ubuntu-meta source package in Focal: Confirmed Bug description: Many applications have no icon displayed in GNOME Software 3.35.91 on latest Ubuntu Focal. See the attached screenshot. [Impact] * Some apt packages do not include an icon in snap-store [Test Case] * Open snap-store, search for GCompris and confirm there is an appropriate icon [Regression Potential] * Very low. Previous Ubuntu releases including apt-config-icons based on the depends in gnome-software. This just adds an apt config that can be used to fetch icons for apt packages via apt. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-software/+bug/1864307/+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 1864307] Re: Many apps have no icon in Software on Focal
** Also affects: ubuntu-meta (Ubuntu) Importance: Undecided Status: New ** Also affects: ubuntu-meta (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: gnome-software (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: ubuntu-meta (Ubuntu) Assignee: (unassigned) => Ken VanDine (ken-vandine) ** Changed in: ubuntu-meta (Ubuntu Focal) Assignee: (unassigned) => Ken VanDine (ken-vandine) ** Changed in: ubuntu-meta (Ubuntu) Status: New => Confirmed ** Changed in: ubuntu-meta (Ubuntu Focal) Status: New => Confirmed ** Changed in: ubuntu-meta (Ubuntu Focal) Importance: Undecided => High ** Changed in: ubuntu-meta (Ubuntu) Importance: Undecided => High -- 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/1864307 Title: Many apps have no icon in Software on Focal Status in GNOME Software: Unknown Status in snap-store: Fix Committed Status in gnome-software package in Ubuntu: Confirmed Status in ubuntu-meta package in Ubuntu: Confirmed Status in gnome-software source package in Focal: New Status in ubuntu-meta source package in Focal: Confirmed Bug description: Many applications have no icon displayed in GNOME Software 3.35.91 on latest Ubuntu Focal. See the attached screenshot. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-software/+bug/1864307/+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 1873658] Re: Deb Files are not associated with an application that manages packages
** Description changed: - When you download a DEB file within 20.04 Ubuntu Beta and you double - click it the file is opened by the archive manager. I would expect the - installer to open the file just like in previous versions of Ubuntu. + [Impact] + + * When a deb is downloaded the default handler is not capable of + installing on 20.04. + + [Test Case] + + We should perform this test on Ubuntu 20.04 as well as some flavors to + ensure we do not regress. + + * Download any deb in firefox, double click on the downloaded file +- On Ubuntu this should open "Ubuntu Software" +- On flavors it should open whatever their default app for handling debs is + + [Regression Potential] + + * For Ubuntu, very low, rarely would a user expect to open a deb with + file-roller + + * Other flavors of ubuntu are overriding this default and should not be + affected. We do need to test this on other flavors to ensure their + defaults are still honored. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdebi in Ubuntu. https://bugs.launchpad.net/bugs/1873658 Title: Deb Files are not associated with an application that manages packages Status in desktop-file-utils package in Ubuntu: Confirmed Status in gdebi package in Ubuntu: Invalid Status in desktop-file-utils source package in Focal: Confirmed Status in gdebi source package in Focal: Invalid Bug description: [Impact] * When a deb is downloaded the default handler is not capable of installing on 20.04. [Test Case] We should perform this test on Ubuntu 20.04 as well as some flavors to ensure we do not regress. * Download any deb in firefox, double click on the downloaded file - On Ubuntu this should open "Ubuntu Software" - On flavors it should open whatever their default app for handling debs is [Regression Potential] * For Ubuntu, very low, rarely would a user expect to open a deb with file-roller * Other flavors of ubuntu are overriding this default and should not be affected. We do need to test this on other flavors to ensure their defaults are still honored. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/desktop-file-utils/+bug/1873658/+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 1873658] Re: Deb Files are not opened by the installer 20.04
** Changed in: gdebi (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdebi in Ubuntu. https://bugs.launchpad.net/bugs/1873658 Title: Deb Files are not associated with an application that manages packages Status in desktop-file-utils package in Ubuntu: Confirmed Status in gdebi package in Ubuntu: Invalid Bug description: When you download a DEB file within 20.04 Ubuntu Beta and you double click it the file is opened by the archive manager. I would expect the installer to open the file just like in previous versions of Ubuntu. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/desktop-file-utils/+bug/1873658/+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 1873658] Re: Deb Files are not opened by the installer 20.04
** Changed in: desktop-file-utils (Ubuntu) Assignee: (unassigned) => Ken VanDine (ken-vandine) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdebi in Ubuntu. https://bugs.launchpad.net/bugs/1873658 Title: Deb Files are not opened by the installer 20.04 Status in desktop-file-utils package in Ubuntu: Confirmed Status in gdebi package in Ubuntu: Confirmed Bug description: When you download a DEB file within 20.04 Ubuntu Beta and you double click it the file is opened by the archive manager. I would expect the installer to open the file just like in previous versions of Ubuntu. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/desktop-file-utils/+bug/1873658/+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 1781428] Re: please enable snap mediation support
All the xenial autopkgtests have passed. What do we need to do to get these published again? -- 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/1781428 Title: please enable snap mediation support Status in pulseaudio package in Ubuntu: Fix Released Status in pulseaudio source package in Xenial: Fix Committed Status in pulseaudio source package in Bionic: Fix Committed Bug description: [Impact] Ubuntu 16.10 added rudimentary snap support to disable audio recording if the connecting process was a snap. By Ubuntu 18.04, something changed in the build resulting in 'Enable Snappy support: no' with audio recording no longer being mediated by pulseaudio (access to the pulseaudio socket continued to be mediated by snapd's apparmor policy). This resulted in any application with the pulseaudio interface connected to be able to also record. Ubuntu 16.04 never had mediation patches and always allowed recording when the pulseaudio interface was connected. To correct this situation but not regress existing behavior, Ubuntu 19.04's pulseaudio was updated patch to allow playback to all connected clients (snaps or not), record by classic snaps (see bug 1787324) and record by strict mode snaps if either the pulseaudio or new-in-snapd-2.41 audio-record interfaces were connected. With this change, snapd is in a position to migrate snaps to the new audio- playback and audio-record interfaces and properly mediate audio recording (see https://forum.snapcraft.io/t/upcoming-pulseaudio- interface-deprecation/13418). The patch to pulseaudio consists of adding a module, enabling it in default.pa and then when it is enabled, pulseaudio when faced with a record operation will, when the connecting process is a snap (ie, its security label (ie, apparmor label) starts with 'snap.'), query snapd via its control socket to ask if the snap is classic and if not, whether the pulseaudio or audio-record interfaces are connected. Adjusting pulseaudio in the manner does not require coordination with any release of snapd. It does need a newer version of snapd-glib, which was recently updated to 1.49 in the last SRU. [Test Case] IMPORTANT: if updating pulseaudio while the session is running, either need to reboot for the test or kill pulseaudio so it can restart with the new snap policy For unconfined applications: $ paplay /usr/share/sounds/alsa/Noise.wav && echo "yes" yes $ rm -f /tmp/out.wav ; parecord /tmp/out.wav && echo "yes" # ctrl-c to stop recording ^Cyes $ paplay /tmp/out.wav && echo "yes" yes For confined, non-snap applications: $ sudo apt-get install evince $ aa-exec -p /usr/bin/evince -- paplay /usr/share/sounds/alsa/Noise.wav && echo yes $ rm -f /tmp/out.wav ; aa-exec -p /usr/bin/evince -- parecord /tmp/out.wav && echo "yes" # ctrl-c to stop recording ^Cyes $ aa-exec -p /usr/bin/evince -- paplay /tmp/out.wav && echo "yes" yes For classic snaps: $ sudo snap install test-snapd-classic-confinement --classic $ snap run --shell test-snapd-classic-confinement $ cat /proc/self/attr/current # verify we are classic confined snap.test-snapd-classic-confinement.test-snapd-classic-confinement (complain) $ paplay /usr/share/sounds/alsa/Noise.wav && echo "yes" yes $ rm -f /tmp/out.wav ; parecord /tmp/out.wav && echo "yes" # ctrl-c to stop recording ^Cyes $ paplay /tmp/out.wav && echo "yes" yes $ exit # out of snap run --shell For strict snaps with pulseaudio: $ sudo snap install test-snapd-pulseaudio --edge $ snap connections test-snapd-pulseaudio Interface Plug Slot Notes pulseaudio test-snapd-pulseaudio:pulseaudio :pulseaudio - $ test-snapd-pulseaudio.play --help # ensure SNAP dirs are created ... $ sudo cp /usr/share/sounds/alsa/Noise.wav /var/snap/test-snapd- pulseaudio/common/ $ test-snapd-pulseaudio.play /var/snap/test-snapd-pulseaudio/common/Noise.wav && echo yes xcb_connection_has_error() returned true yes (note, the xcb_connection_has_error() message is due to the x11 interface not being connecting which is unrelated to mediation. x11 is left out to ensure that just audio-playback/audio-record are tested) $ test-snapd-pulseaudio.record /tmp/out.wav && echo yes # should pass ... ^Cyes $ test-snapd-pulseaudio.play /tmp/out.wav && echo yes ... yes For strict snaps with audio-playback/audio-record: $ sudo snap refresh core --candidate # make sure have 2.41. 'install' on 16.04 $ sudo snap install test-snapd-audio-record --edge $ snap connections test-snapd-audio-record # record not connected Interface PlugSlot Notes audio-playback test-snapd-audio-record:audio-playback :audio-playback - audio-record
[Touch-packages] [Bug 1872864] Re: appstream metadata not created
** Changed in: snap-store Status: Triaged => Invalid -- 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/1872864 Title: appstream metadata not created Status in snap-store: Invalid Status in ubuntu-meta package in Ubuntu: Fix Released Bug description: The gnome-software packaged depends on appstream, which was bringing in that binary package in previous releases. With the switch to seeding the snap this is causing a problem with the appstream cache never getting populated. The appstream package includes an apt config that triggered the appstream cache refresh after update. We need to explicitly seed the appstream package in ubuntu-desktop. To manage notifications about this bug go to: https://bugs.launchpad.net/snap-store/+bug/1872864/+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 1872864] Re: appstream metadata not created
** Also affects: ubuntu-meta (Ubuntu) Importance: Undecided Status: New ** Changed in: ubuntu-meta (Ubuntu) Assignee: (unassigned) => Ken VanDine (ken-vandine) ** Changed in: ubuntu-meta (Ubuntu) Importance: Undecided => Critical ** Changed in: ubuntu-meta (Ubuntu) Status: New => Triaged ** Changed in: ubuntu-meta (Ubuntu) Status: Triaged => In Progress -- 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/1872864 Title: appstream metadata not created Status in snap-store: Triaged Status in ubuntu-meta package in Ubuntu: In Progress Bug description: The gnome-software packaged depends on appstream, which was bringing in that binary package in previous releases. With the switch to seeding the snap this is causing a problem with the appstream cache never getting populated. The appstream package includes an apt config that triggered the appstream cache refresh after update. We need to explicitly seed the appstream package in ubuntu-desktop. To manage notifications about this bug go to: https://bugs.launchpad.net/snap-store/+bug/1872864/+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 1866194] Re: After connecting a Bluetooth headset or speaker, it shows up in the sound output options but the sound keeps being emitted from the internal laptop speaker
This might be more of an issue with handing sound devices being added and removed that being bluetooth specific. Last week I experienced the same behavior when plugging in my USB headphones. Removing them and plugging them in again worked though. I haven't been able to reproduce this today though. I'll keep trying and report back. -- 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/1866194 Title: After connecting a Bluetooth headset or speaker, it shows up in the sound output options but the sound keeps being emitted from the internal laptop speaker Status in pulseaudio package in Ubuntu: New Bug description: Ubuntu version: focal dev Kernel version: 5.4.0-14-generic #17-Ubuntu SMP Thu Feb 6 22:47:59 UTC 2020 Device CID: 201704-25503 Steps to reproduce: 1. Go to Bluetooth settings panel 2. Pair a BT device 3. Make sure it's marked as Connected, and go to the Sound settings 4. Make sure it's the one selected as "Output device" 5. Click "Test" -> the test sound outputs from the internal laptop speakers (NOK) 6. Select "Speakers - Built-in Audio" as Output device and click "Test" -> the test sound outputs from the internal laptop speakers (OK) 7. Try to switch back to the BT device and click Test -> same result as in step 5 Tested with 2 different BT devices (one headset and one speaker) Attached are btmon logs captured during the procedure described above, and pactl logs capture after step 7. Up to this morning, it was harder to connect the BT device, but once connected, the sound would output on it as expected. Now, the BT connection seems to work better, but I can't output the sound to the BT device... I tried to reboot the device, and also to suspend/resume, but in each case, the BT device can connect back, but the sound is still output from the internal laptop speakers, even when the BT device is selected in the Sound settings. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pieq 1566 F pulseaudio /dev/snd/pcmC0D0c: pieq 1566 F...m pulseaudio /dev/snd/pcmC0D0p: pieq 1566 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Mar 5 22:15:50 2020 InstallationDate: Installed on 2020-01-17 (48 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200116) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/23/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.14.0 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.14.0:bd04/23/2019:svnDellInc.:pnInspiron7370:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 7370 dmi.product.sku: 07E9 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1866194/+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 1856054] Re: pulseaudio now depends on libsnapd-glib1 which recommends snapd
** Also affects: snapd-glib (Ubuntu) Importance: Undecided Status: New ** Tags added: rls-bb-incoming rls-xx-incoming ** Tags removed: rls-xx-incoming ** Tags added: rls-x-incoming -- 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/1856054 Title: pulseaudio now depends on libsnapd-glib1 which recommends snapd Status in pulseaudio package in Ubuntu: Confirmed Status in snapd-glib package in Ubuntu: New Bug description: The latest update for pulseaudio (1:11.1-1ubuntu7.5) in bionic now has libsnapd-glib1 as a dependency. This is complete and utter nonsense. I do not want cascading dependencies that have no business being installed on the systems I manage. Please rectify this at once. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1856054/+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 1781428] Re: please enable snap mediation support
** Changed in: pulseaudio (Ubuntu Xenial) Assignee: (unassigned) => James Henstridge (jamesh) ** Changed in: pulseaudio (Ubuntu Bionic) Assignee: (unassigned) => James Henstridge (jamesh) ** Changed in: pulseaudio (Ubuntu Xenial) Importance: Undecided => Medium ** Changed in: pulseaudio (Ubuntu Bionic) Importance: Undecided => Medium -- 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/1781428 Title: please enable snap mediation support Status in pulseaudio package in Ubuntu: Fix Released Status in pulseaudio source package in Xenial: Triaged Status in pulseaudio source package in Bionic: Triaged Bug description: [Impact] Ubuntu 16.10 added rudimentary snap support to disable audio recording if the connecting process was a snap. By Ubuntu 18.04, something changed in the build resulting in 'Enable Snappy support: no' with audio recording no longer being mediated by pulseaudio (access to the pulseaudio socket continued to be mediated by snapd's apparmor policy). This resulted in any application with the pulseaudio interface connected to be able to also record. Ubuntu 16.04 never had mediation patches and always allowed recording when the pulseaudio interface was connected. To correct this situation but not regress existing behavior, Ubuntu 19.04's pulseaudio was updated patch to allow playback to all connected clients (snaps or not), record by classic snaps (see bug 1787324) and record by strict mode snaps if either the pulseaudio or new-in-snapd-2.41 audio-record interfaces were connected. With this change, snapd is in a position to migrate snaps to the new audio- playback and audio-record interfaces and properly mediate audio recording (see https://forum.snapcraft.io/t/upcoming-pulseaudio- interface-deprecation/13418). The patch to pulseaudio consists of adding a module, enabling it in default.pa and then when it is enabled, pulseaudio when faced with a record operation will, when the connecting process is a snap (ie, its security label (ie, apparmor label) starts with 'snap.'), query snapd via its control socket to ask if the snap is classic and if not, whether the pulseaudio or audio-record interfaces are connected. Adjusting pulseaudio in the manner does not require coordination with any release of snapd. It does need a newer version of snapd-glib, which was recently updated to 1.49 in the last SRU. [Test Case] IMPORTANT: if updating pulseaudio while the session is running, either need to reboot for the test or kill pulseaudio so it can restart with the new snap policy For unconfined applications: $ paplay /usr/share/sounds/alsa/Noise.wav && echo "yes" yes $ rm -f /tmp/out.wav ; parecord /tmp/out.wav && echo "yes" # ctrl-c to stop recording ^Cyes $ paplay /tmp/out.wav && echo "yes" yes For confined, non-snap applications: $ sudo apt-get install evince $ aa-exec -p /usr/bin/evince -- paplay /usr/share/sounds/alsa/Noise.wav && echo yes $ rm -f /tmp/out.wav ; aa-exec -p /usr/bin/evince -- parecord /tmp/out.wav && echo "yes" # ctrl-c to stop recording ^Cyes $ aa-exec -p /usr/bin/evince -- paplay /tmp/out.wav && echo "yes" yes For classic snaps: $ sudo snap install test-snapd-classic-confinement --classic $ snap run --shell test-snapd-classic-confinement $ cat /proc/self/attr/current # verify we are classic confined snap.test-snapd-classic-confinement.test-snapd-classic-confinement (complain) $ paplay /usr/share/sounds/alsa/Noise.wav && echo "yes" yes $ rm -f /tmp/out.wav ; parecord /tmp/out.wav && echo "yes" # ctrl-c to stop recording ^Cyes $ paplay /tmp/out.wav && echo "yes" yes For strict snaps with pulseaudio: $ sudo snap install --dangerous ./test-snapd-pulseaudio_1_amd64.snap $ snap connections test-snapd-pulseaudio Interface Plug Slot Notes pulseaudio test-snapd-pulseaudio:pulseaudio :pulseaudio - $ test-snapd-pulseaudio.play --help # ensure SNAP dirs are created ... $ sudo cp /usr/share/sounds/alsa/Noise.wav /var/snap/test-snapd- pulseaudio/common/ $ test-snapd-pulseaudio.play /var/snap/test-snapd-pulseaudio/common/Noise.wav && echo yes xcb_connection_has_error() returned true yes (note, the xcb_connection_has_error() message is due to the x11 interface not being connecting which is unrelated to mediation. x11 is left out to ensure that just audio-playback/audio-record are tested) $ test-snapd-pulseaudio.record /tmp/out.wav && echo yes # should pass ... ^Cyes $ test-snapd-pulseaudio.play /tmp/out.wav && echo yes ... yes For strict snaps with audio-playback/audio-record: $ sudo snap refresh core --candidate # make sure have 2.41. 'install' on 16.04 $ sudo snap install --dangerous ./test-snapd-audio-record_1_amd64.snap $
[Touch-packages] [Bug 1727908] Re: Software & Updates application does not permit changes on the "Other Software" tab
** Changed in: software-properties (Ubuntu Bionic) Assignee: (unassigned) => Sebastien Bacher (seb128) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1727908 Title: Software & Updates application does not permit changes on the "Other Software" tab Status in gnome-shell package in Ubuntu: Confirmed Status in software-properties package in Ubuntu: Confirmed Status in gnome-shell source package in Bionic: New Status in software-properties source package in Bionic: New Bug description: On the "Other Software" tab, I am unable to select "Canonical Partners". Similarly, the other checkboxes on the "Other Software" can not be clicked. Clicking on a checkbox has no effect, and a dialog requesting the admin password is not presented. However, activating or deactivating checkboxes on other tabs causes an authorization dialog to be presented to the user. I experience this bug in an an Xorg session. sources.list and sources.list.d have the following permissions: -rw-r--r-- 1 root root 2897 Oct 26 22:35 sources.list drwxr-xr-x 2 root root 4096 Oct 26 21:29 sources.list.d All files in sources.list.d have the following permissions as this example: -rw-r--r-- 1 root root 189 Oct 25 21:50 google-chrome.list $ lsb_release -rd Description: Ubuntu 17.10 Release: 17.10 $ apt-cache policy software-properties-gtk software-properties-gtk: Installed: 0.96.24.17 Candidate: 0.96.24.17 Version table: *** 0.96.24.17 500 500 http://us.archive.ubuntu.com/ubuntu artful/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu artful/main i386 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: software-properties-gtk 0.96.24.17 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: wl nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Oct 26 22:45:09 2017 InstallationDate: Installed on 2017-10-26 (1 days ago) InstallationMedia: Ubuntu 17.10.0 2017.10.25 amd64 "Custom Artful Aardvark" PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: software-properties UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1727908/+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 1841718] Re: [radeon] Rendering of combo boxes and tooltips is broken
** Changed in: xserver-xorg-video-ati (Ubuntu) Assignee: (unassigned) => Timo Aaltonen (tjaalton) ** Changed in: xserver-xorg-video-ati (Ubuntu) Status: New => Triaged ** Also affects: xserver-xorg-video-ati (Ubuntu Eoan) Importance: Undecided Assignee: Timo Aaltonen (tjaalton) Status: Triaged ** Also affects: mutter (Ubuntu Eoan) Importance: Undecided Status: New ** Also affects: gtk+3.0 (Ubuntu Eoan) Importance: Undecided Status: New ** Changed in: xserver-xorg-video-ati (Ubuntu Eoan) Importance: Undecided => Medium ** Tags removed: rls-ee-incoming ** Changed in: mutter (Ubuntu Eoan) Status: New => Invalid ** Changed in: gtk+3.0 (Ubuntu Eoan) Status: New => Invalid -- 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/1841718 Title: [radeon] Rendering of combo boxes and tooltips is broken Status in gtk+3.0 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Triaged Status in mutter package in Ubuntu: Invalid Status in gtk+3.0 source package in Eoan: Invalid Status in mesa source package in Eoan: Triaged Status in mutter source package in Eoan: Invalid Bug description: Combo boxes are broken (cf screenshot) Tested in gnome-control-center and gtk3-demo. Tooltips are also garbage. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.33.91-1ubuntu1 ProcVersionSignature: Ubuntu 5.2.0-13.14-generic 5.2.8 Uname: Linux 5.2.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Aug 28 07:08:33 2019 DisplayManager: gdm3 InstallationDate: Installed on 2014-07-15 (1869 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140520) RelatedPackageVersions: mutter-common 3.33.91-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to eoan on 2018-03-24 (521 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1841718/+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 1841915] Re: black screen, unresponsive, after logout from gnome Wayland session
** Tags removed: rls-ee-incoming -- 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/1841915 Title: black screen, unresponsive, after logout from gnome Wayland session Status in gdm3 package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Bug description: on logout the screen is black, the system is unresponsive and has to be restarted. (Untested by me yet, but I expect ssh-ing in and restarting gdm would work.) I believe this may be already reported upstream here: https://bugzilla.redhat.com/show_bug.cgi?id=1745554 That's why I've reported this against gdm3 even though I honestly don't know if it might be a gnome-shell, gnome-session or mutter based error. (FWIW without the upstream bug to link to I'd maybe suspect gnome-shell first.) NB: This machine's conf has AutomaticLogin enabled, but another machine also on 19.10 does not, and it's showing the same thing. On *this* machine I found that the *first* time I logged out, it was OK, but not the second time. On the other machine, it fails first time too. It's as if the gdm login screen can appear exactly once. That (and being on gnome 3.33) is why I don't think this is a dupe of #1824588. Nothing appears in /var/crash as a result of this. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gdm3 3.33.90-1ubuntu1 ProcVersionSignature: Ubuntu 5.2.0-13.14-generic 5.2.8 Uname: Linux 5.2.0-13-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Aug 29 10:51:22 2019 InstallationDate: Installed on 2018-09-11 (351 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214) SourcePackage: gdm3 UpgradeStatus: Upgraded to eoan on 2019-07-16 (43 days ago) mtime.conffile..etc.gdm3.custom.conf: 2019-07-17T00:07:04.528641 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1841915/+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 1795959] Re: [FFe] Seed xdg-desktop-portal-gtk
Verfied on xenial, worked properly ** Tags removed: verification-needed verification-needed-xenial ** Tags added: verification-done verification-done-xenial -- 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/1795959 Title: [FFe] Seed xdg-desktop-portal-gtk Status in ubuntu-meta package in Ubuntu: Fix Released Status in ubuntu-meta source package in Xenial: Fix Committed Status in ubuntu-meta source package in Bionic: Fix Released Bug description: [Impact] * These packages can improve desktop integration of snap packages. The risk is low as nothing in the default desktop install actually exercises the portals at this time. We need to seed the portals so they are available when snaps are installed that can utilize them. Flatpak packages will also benefit. [Test Case] * This can be tested by using the portal-test snap [Regression potential] * Nothing in the default install utilizes it, so there should be no risk. [Other Info] * Security and MIR reviews have been completed for xdg-desktop-portal-gtk[1] and xdg-desktop-portal[2]. 1. https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal-gtk/+bug/1750069 2. https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal/+bug/1749672 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1795959/+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 1795959] Re: [FFe] Seed xdg-desktop-portal-gtk
** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- 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/1795959 Title: [FFe] Seed xdg-desktop-portal-gtk Status in ubuntu-meta package in Ubuntu: Fix Released Status in ubuntu-meta source package in Xenial: New Status in ubuntu-meta source package in Bionic: Fix Committed Bug description: [Impact] * These packages can improve desktop integration of snap packages. The risk is low as nothing in the default desktop install actually exercises the portals at this time. We need to seed the portals so they are available when snaps are installed that can utilize them. Flatpak packages will also benefit. [Test Case] * This can be tested by using the portal-test snap [Regression potential] * Nothing in the default install utilizes it, so there should be no risk. [Other Info] * Security and MIR reviews have been completed for xdg-desktop-portal-gtk[1] and xdg-desktop-portal[2]. 1. https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal-gtk/+bug/1750069 2. https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal/+bug/1749672 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1795959/+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 1828102] Re: Regression in ModemManager
I've sponsored this for disco -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1828102 Title: Regression in ModemManager Status in modemmanager package in Ubuntu: Fix Released Status in modemmanager source package in Bionic: Fix Released Status in modemmanager source package in Cosmic: Won't Fix Status in modemmanager source package in Disco: In Progress Status in modemmanager source package in Eoan: Fix Released Bug description: [Impact] ModemManager disconnects from CDMA modem after 30 sec failing to check signal status due to incorrect error handling [Test case] connect to a cdma device without an extra AT channel (Eg. Samsung brightside phone) and modemmanager will terminate the connection [Regression potential] The patch is tiny, fixing an obvious overlook, and it only affects CDMA broadband modems, so the risk of a regression is very low. [Original description] ModemManager disconnects after ~30 sec caused by a typo in 1.8 see https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1819615 and https://gitlab.freedesktop.org/mobile-broadband/ModemManager/issues/119 for details needs a SRU for cosmic and dingo patch attached yechiel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1828102/+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 1795959] Re: [FFe] Seed xdg-desktop-portal-gtk
** Description changed: - Security and MIR reviews have been completed for xdg-desktop-portal- - gtk[1] and xdg-desktop-portal[2]. + [Impact] + * These packages can improve desktop integration of snap packages. The risk is low as nothing in the default desktop install actually exercises the portals at this time. We need to seed the portals so they are available when snaps are installed that can utilize them. Flatpak packages will also benefit. - These packages can improve desktop integration of snap packages. The - risk is low as nothing in the default desktop install actually exercises - the portals at this time. We need to seed the portals so they are - available when snaps are installed that can utilize them. Flatpak - packages will also benefit. + [Test Case] + * This can be tested by using the portal-test snap + + [Regression potential] + * Nothing in the default install utilizes it, so there should be no risk. + + [Other Info] + * Security and MIR reviews have been completed for xdg-desktop-portal-gtk[1] and xdg-desktop-portal[2]. 1. https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal-gtk/+bug/1750069 2. https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal/+bug/1749672 ** Also affects: ubuntu-meta (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: ubuntu-meta (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: ubuntu-meta (Ubuntu Xenial) Assignee: (unassigned) => Ken VanDine (ken-vandine) ** Changed in: ubuntu-meta (Ubuntu Bionic) Assignee: (unassigned) => Ken VanDine (ken-vandine) ** Changed in: ubuntu-meta (Ubuntu Xenial) Importance: Undecided => Medium ** Changed in: ubuntu-meta (Ubuntu Bionic) Importance: Undecided => Medium -- 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/1795959 Title: [FFe] Seed xdg-desktop-portal-gtk Status in ubuntu-meta package in Ubuntu: Fix Released Status in ubuntu-meta source package in Xenial: New Status in ubuntu-meta source package in Bionic: New Bug description: [Impact] * These packages can improve desktop integration of snap packages. The risk is low as nothing in the default desktop install actually exercises the portals at this time. We need to seed the portals so they are available when snaps are installed that can utilize them. Flatpak packages will also benefit. [Test Case] * This can be tested by using the portal-test snap [Regression potential] * Nothing in the default install utilizes it, so there should be no risk. [Other Info] * Security and MIR reviews have been completed for xdg-desktop-portal-gtk[1] and xdg-desktop-portal[2]. 1. https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal-gtk/+bug/1750069 2. https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal/+bug/1749672 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1795959/+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 1819615] Re: For additional hardware support, modemmanager needs to be upgraded to 1.10 on Bionic
@roaf: This was driven by an OEM request, so the priority was bionic. We also needed to make sure disco (and later) was covered to ensure we made the next LTS as well. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1819615 Title: For additional hardware support, modemmanager needs to be upgraded to 1.10 on Bionic Status in OEM Priority Project: In Progress Status in libmbim package in Ubuntu: Fix Released Status in libqmi package in Ubuntu: Fix Released Status in modemmanager package in Ubuntu: Fix Released Status in libmbim source package in Bionic: Fix Committed Status in libqmi source package in Bionic: Fix Committed Status in modemmanager source package in Bionic: Fix Committed Status in libmbim source package in Disco: Fix Released Status in libqmi source package in Disco: Fix Released Status in modemmanager source package in Disco: Fix Released Status in libmbim source package in Eoan: Fix Released Status in libqmi source package in Eoan: Fix Released Status in modemmanager source package in Eoan: Fix Released Bug description: [Impact] * The new modemmanager package adds DW5820e and DW5821 support. * This modemmanager version is needed to support new devices. [Test Case] * install modemmanager, libmbim, and libqmi from -proposed * reboot and try WWAN function to see if any regression there. * perform general dogfooding of its reverse dependencies (network- manager, gnome-control-center etc.) [Regression Potential] * The package comes from Disco and should not have regression there. * Every new upstream release can potentially break existing dependencies if any of the required features have been changed/removed, so besides regular testing a general dogfooding session with the new modemmanager is advised. [Original Description] To have Bionic, the current LTS, working with as wide of a range of modems as possible we need to have it upgraded to the current 1.10 versions. Also the underlying libraries need to get upgraded appropriately. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1819615/+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 1814373] Re: storage / luks / dmsetup regressed (or got better) on ppc64le
** Changed in: udisks2 (Ubuntu Bionic) Status: New => Invalid ** Changed in: udisks2 (Ubuntu Disco) Status: New => Invalid ** Changed in: udisks2 (Ubuntu Eoan) Status: New => Invalid -- 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/1814373 Title: storage / luks / dmsetup regressed (or got better) on ppc64le Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: New Status in udisks2 package in Ubuntu: Invalid Status in linux source package in Bionic: New Status in systemd source package in Bionic: New Status in udisks2 source package in Bionic: Invalid Status in linux source package in Disco: New Status in systemd source package in Disco: New Status in udisks2 source package in Disco: Invalid Status in linux source package in Eoan: Confirmed Status in systemd source package in Eoan: New Status in udisks2 source package in Eoan: Invalid Bug description: in disco proposed with new systemd and v4.19 kernel it appears that dmsetup / cryptsetup storage either got better or worse. Devices take very long to activate, and sometimes remain in use during test clean up. This leads to udisks autopkgtest failing on ppc64le and systemd's "storage" autopkgtest is also failing. I've tried to make ppc64le test more resilient, but it's still odd that it became unstable in disco, and used to be rock solid on ppc64le. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1814373/+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 1819615] Re: For additional hardware support, modemmanager needs to be upgraded to 1.10 on Bionic
I've sponsored these packages -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1819615 Title: For additional hardware support, modemmanager needs to be upgraded to 1.10 on Bionic Status in OEM Priority Project: In Progress Status in libmbim package in Ubuntu: Fix Released Status in libqmi package in Ubuntu: Fix Released Status in modemmanager package in Ubuntu: Fix Released Status in libmbim source package in Bionic: In Progress Status in libqmi source package in Bionic: In Progress Status in modemmanager source package in Bionic: In Progress Bug description: [Impact] * The new modemmanager package adds DW5820e and DW5821 support. * This modemmanager version is needed to support new devices. [Test Case] * install modemmanager, libmbim, and libqmi from -proposed * reboot and try WWAN function to see if any regression there. * perform general dogfooding of its reverse dependencies (network- manager, gnome-control-center etc.) [Regression Potential] * The package comes from Disco and should not have regression there. * Every new upstream release can potentially break existing dependencies if any of the required features have been changed/removed, so besides regular testing a general dogfooding session with the new modemmanager is advised. [Original Description] To have Bionic, the current LTS, working with as wide of a range of modems as possible we need to have it upgraded to the current 1.10 versions. Also the underlying libraries need to get upgraded appropriately. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1819615/+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 1819615] Re: For additional hardware support, modemmanager needs to be upgraded to 1.10 on Bionic
The libmbim debdiff doesn't include the latest version that's in bionic (1.14.2-2.1ubuntu1) in the changelog and it also reverts the change in that version. Please ensure the debdiff is against that version. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1819615 Title: For additional hardware support, modemmanager needs to be upgraded to 1.10 on Bionic Status in OEM Priority Project: New Status in libmbim package in Ubuntu: Fix Released Status in libqmi package in Ubuntu: Fix Released Status in modemmanager package in Ubuntu: Fix Released Status in libmbim source package in Bionic: In Progress Status in libqmi source package in Bionic: In Progress Status in modemmanager source package in Bionic: In Progress Bug description: [Impact] * The new modemmanager package adds DW5820e support. * This modemmanager version is needed to support new devices. [Test Case] * install modemmanager, libmbim, and libqmi from -proposed * reboot and try WWAN function to see if any regression there. * perform general dogfooding of its reverse dependencies (network- manager, gnome-control-center etc.) [Regression Potential] * The package comes from Disco and should not have regression there. * Every new upstream release can potentially break existing dependencies if any of the required features have been changed/removed, so besides regular testing a general dogfooding session with the new modemmanager is advised. [Original Description] To have Bionic, the current LTS, working with as wide of a range of modems as possible we need to have it upgraded to the current 1.10 versions. Also the underlying libraries need to get upgraded appropriately. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1819615/+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 1819615] Re: For additional hardware support, modemmanager needs to be upgraded to 1.10 on Bionic
The libqmi debdiff doesn't include the latest version that's in bionic (1.18.0-3ubuntu1) in the changelog and it also reverts the change in that version. Please ensure the debdiff is against that version. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1819615 Title: For additional hardware support, modemmanager needs to be upgraded to 1.10 on Bionic Status in OEM Priority Project: New Status in libmbim package in Ubuntu: Fix Released Status in libqmi package in Ubuntu: Fix Released Status in modemmanager package in Ubuntu: Fix Released Status in libmbim source package in Bionic: In Progress Status in libqmi source package in Bionic: In Progress Status in modemmanager source package in Bionic: In Progress Bug description: [Impact] * The new modemmanager package adds DW5820e support. * This modemmanager version is needed to support new devices. [Test Case] * install modemmanager, libmbim, and libqmi from -proposed * reboot and try WWAN function to see if any regression there. * perform general dogfooding of its reverse dependencies (network- manager, gnome-control-center etc.) [Regression Potential] * The package comes from Disco and should not have regression there. * Every new upstream release can potentially break existing dependencies if any of the required features have been changed/removed, so besides regular testing a general dogfooding session with the new modemmanager is advised. [Original Description] To have Bionic, the current LTS, working with as wide of a range of modems as possible we need to have it upgraded to the current 1.10 versions. Also the underlying libraries need to get upgraded appropriately. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1819615/+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 1778946] Re: No dns resolution after closing a vpn/pptp connection
** Changed in: network-manager (Ubuntu) Assignee: (unassigned) => Till Kamppeter (till-kamppeter) ** Changed in: network-manager (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to resolvconf in Ubuntu. https://bugs.launchpad.net/bugs/1778946 Title: No dns resolution after closing a vpn/pptp connection Status in network-manager package in Ubuntu: Confirmed Status in ppp package in Ubuntu: Confirmed Status in resolvconf package in Ubuntu: Confirmed Bug description: step to reproduce set a VPN connection configured to connect a Microsoft vpn server (pptp) internet acces is ok enable the vpn connection using the applet on the top right corner of the desktop internet still ok ping works disable the vpn connection ping doesn't works with a host but works if i specify an ip address ping: xx.net: Nom ou service inconnu As a workaround, i disable the ethernet link and re-enable it name resolution is now ok ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager 1.10.6-2ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Jun 27 18:09:30 2018 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2014-06-03 (1484 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) IpRoute: default via 192.168.0.254 dev eth0 proto dhcp metric 20100 169.254.0.0/16 dev eth0 scope link metric 1000 192.168.0.0/24 dev eth0 proto kernel scope link src 192.168.0.47 metric 100 IwConfig: lono wireless extensions. eth0 no wireless extensions. NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true RfKill: SourcePackage: network-manager UpgradeStatus: Upgraded to bionic on 2018-05-10 (48 days ago) nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH eth0ethernet connected /org/freedesktop/NetworkManager/Devices/2 Connexion filaire 1 94806bba-1c68-46b6-87f4-a3aff6dd /org/freedesktop/NetworkManager/ActiveConnection/6 lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.6 connected (site only) started limited enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1778946/+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 1803534] Re: Backport uuid based cache file naming scheme
Marked this as invalid for now. The fontconfig improvements in snapd 2.36.2 seem to have fixed the snap startup issues. Without this SRU there are some additional cache files generated, but that should be fine just some extra noise. ** Changed in: fontconfig (Ubuntu Bionic) Status: Fix Committed => Invalid ** Changed in: fontconfig (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fontconfig in Ubuntu. https://bugs.launchpad.net/bugs/1803534 Title: Backport uuid based cache file naming scheme Status in fontconfig package in Ubuntu: Invalid Status in fontconfig source package in Bionic: Invalid Bug description: Fontconfig 2.13.0 changed the cache file naming scheme to be based on the contents of ".uuid" file in the directory rather than a hash of the directory name. On a pure debs system this doesn't really matter since everything is using the same libfontconfig.so. When snaps are involved, it can lead to some apps not seeing the cache files produced by a different fontconfig version. In particular, while libfontconfig 2.13 can reuse 2.12's cache files for read only directories, the reverse is not true. This will be a problem for apps built on top of the "core18" base snap when run on later Ubuntu releases (cosmic, disco, etc). By providing a backport of the UUID cache file feature to bionic for use by snap applications, we'd avoid this. Having it in bionic- updates would be ideal so that snapcraft picks it up automatically. [Impact] * This update changes how fontconfig cache files are named, instead of using md5($dir), it instead uses the contents of a $dir/.uuid file. No changes are made to the format of the cache file contents. * This change is primarily intended for use by snap applications built with core18: as the updated libfontconfig will fall back to the md5 cache file names for read-only directories without a .uuid file, they will be able to reuse cache files from any host system running fontconfig >= 2.11.95 [Test Case] * After installing the update, cache files should be generated in /var/cache/fontconfig/ with names like "07b67f7a-16ea-4440-9b6c- 21fc9153568c-le64.cache-7" (note the extra dashes not present in the MD5 based cache file names). [Regression Potential] * Applications using a non-default libfontconfig could end up not finding the new cache files and regenerating them in ~/.cache/fontconfig. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1803534/+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 1754693] Re: Xwayland/Xorg crashed with SIGSEGV in st_renderbuffer_delete() from _mesa_reference_renderbuffer_() [often when running Skype or Slack snaps]
I can confirm with the PPA enabled I no longer see classic snaps crash when running wayland on cosmic. I tested vscode and slack. -- 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/1754693 Title: Xwayland/Xorg crashed with SIGSEGV in st_renderbuffer_delete() from _mesa_reference_renderbuffer_() [often when running Skype or Slack snaps] Status in mesa package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Incomplete Status in mesa source package in Bionic: Confirmed Status in xorg-server source package in Bionic: Confirmed Status in mesa source package in Cosmic: Confirmed Status in xorg-server source package in Cosmic: Incomplete Status in mesa source package in Disco: Confirmed Status in xorg-server source package in Disco: Incomplete Bug description: https://errors.ubuntu.com/problem/01a80d2110a46f6b6d857ce814079646e695f4ca https://errors.ubuntu.com/problem/a1e7fe67e388164abd73462b322cb79ac2773fae --- Steps to reproduce: Install 'slack' snap: sudo snap install slack --classic Run slack: slack Instacrash. ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: xwayland 2:1.19.6-1ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CompizPlugins: [core,composite,opengl,decor,mousepoll,grid,vpswitch,compiztoolbox,imgpng,gnomecompat,regex,move,place,resize,snap,unitymtgrabhandles,wall,animation,session,expo,workarounds,fade,ezoom,scale,unityshell] CompositorRunning: None CurrentDesktop: GNOME Date: Fri Mar 9 10:31:06 2018 DistUpgraded: 2018-03-06 13:58:47,853 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: bionic DistroVariant: ubuntu EcryptfsInUse: Yes ExecutablePath: /usr/bin/Xwayland ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [1043:8534] MachineType: ASUS All Series ProcCmdline: /usr/bin/Xwayland :0 -rootless -terminate -accessx -core -listen 4 -listen 5 -displayfd 6 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic root=UUID=cd444f9d-672e-4d7b-aea8-657fff0ea1f4 ro quiet splash crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M vt.handoff=1 Signal: 6 SourcePackage: xorg-server StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so Title: Xwayland crashed with SIGABRT UpgradeStatus: Upgraded to bionic on 2018-03-06 (2 days ago) UserGroups: adm admin audio cdrom chroot-admin dialout dip egbuild fax floppy fuse libvirt libvirtd lpadmin lxd plugdev sambashare sudo tape video wireshark dmi.bios.date: 10/27/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2702 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z97-PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2702:bd10/27/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ97-PRO:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.90-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc4-1ubuntu3 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc4-1ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu2 version.xserver-xorg-input-evdev:
[Touch-packages] [Bug 1763520] Re: after upgrade to bionic, printing fails without explanation / logs / debuggability
** Also affects: gtk+3.0 (Ubuntu Cosmic) Importance: Undecided Status: New ** Also affects: cups-filters (Ubuntu Cosmic) Importance: Undecided Status: New ** Also affects: gtk+3.0 (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: cups-filters (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: cups-filters (Ubuntu Bionic) Status: New => Invalid ** Changed in: cups-filters (Ubuntu Cosmic) Status: New => Invalid -- 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/1763520 Title: after upgrade to bionic, printing fails without explanation / logs / debuggability Status in cups-filters package in Ubuntu: Invalid Status in gtk+3.0 package in Ubuntu: Triaged Status in cups-filters source package in Bionic: Invalid Status in gtk+3.0 source package in Bionic: New Status in cups-filters source package in Cosmic: Invalid Status in gtk+3.0 source package in Cosmic: New Bug description: I am unable to print to my network-attached printer after upgrade to bionic. ps shows: lp 26047 0.0 0.0 91668 5756 ?S15:06 0:00 \_ HP-ENVY-4500-new 473 vorlon USCIS Form I-9 1 print-content-optimize=auto print-rendering-intent=auto cupsPrintQuality=4 number-up=1 MediaType=Stationery noCollate print-scaling=auto PageSize=Custom.Letter.SM ColorModel=RGB Duplex=DuplexNoTumble job-uuid=urn:uuid:08c937ec-ccb6-3ff1-6ed4-212128e4257b job-originating-host-name=localhost date-time-at-creation= date-time-at-processing= time-at-creation=1523570792 time-at-processing=1523570792 print-quality=4 lp 26050 0.1 0.0 0 0 ?Z15:06 0:00 | \_ [gs] lp 26048 0.0 0.0 79908 3836 ?S15:06 0:00 \_ HP-ENVY-4500-new 473 vorlon USCIS Form I-9 1 print-content-optimize=auto print-rendering-intent=auto cupsPrintQuality=4 number-up=1 MediaType=Stationery noCollate print-scaling=auto PageSize=Custom.Letter.SM ColorModel=RGB Duplex=DuplexNoTumble job-uuid=urn:uuid:08c937ec-ccb6-3ff1-6ed4-212128e4257b job-originating-host-name=localhost date-time-at-creation= date-time-at-processing= time-at-creation=1523570792 time-at-processing=1523570792 print-quality=4 root 26049 0.0 0.0 84388 6192 ?S15:06 0:00 \_ ipp://HP645106EA160E.local:631/ipp/print 473 vorlon USCIS Form I-9 1 print-content-optimize=auto print-rendering-intent=auto cupsPrintQuality=4 number-up=1 MediaType=Stationery noCollate print-scaling=auto PageSize=Custom.Letter.SM ColorModel=RGB Duplex=DuplexNoTumble job-uuid=urn:uuid:08c937ec-ccb6-3ff1-6ed4-212128e4257b job-originating-host-name=localhost date-time-at-creation= date-time-at-processing= time-at-creation=1523570792 time-at-processing=1523570792 print-quality=4 Note the un-reaped gs process. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: cups 2.2.7-1ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Apr 12 15:07:49 2018 InstallationDate: Installed on 2010-09-24 (2757 days ago) InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 (20100816.1) MachineType: LENOVO 2306CTO Papersize: letter ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-13-generic.efi.signed root=/dev/mapper/hostname-root ro quiet splash vt.handoff=1 SourcePackage: cups UpgradeStatus: Upgraded to bionic on 2018-03-21 (21 days ago) dmi.bios.date: 10/25/2013 dmi.bios.vendor: LENOVO dmi.bios.version: G2ET97WW (2.57 ) dmi.board.asset.tag: Not Available dmi.board.name: 2306CTO dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG2ET97WW(2.57):bd10/25/2013:svnLENOVO:pn2306CTO:pvrThinkPadX230:rvnLENOVO:rn2306CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad X230 dmi.product.name: 2306CTO dmi.product.version: ThinkPad X230 dmi.sys.vendor: LENOVO modified.conffile..etc.cups.cupsd.conf: [inaccessible: [Errno 13] Permission denied: '/etc/cups/cupsd.conf'] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1763520/+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 1803534] Re: Backport uuid based cache file naming scheme
I've uploaded 2.12.6-0ubuntu2.3 making libfontconfig1-dev depend on uuid-dev -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fontconfig in Ubuntu. https://bugs.launchpad.net/bugs/1803534 Title: Backport uuid based cache file naming scheme Status in fontconfig package in Ubuntu: New Status in fontconfig source package in Bionic: Fix Committed Bug description: Fontconfig 2.13.0 changed the cache file naming scheme to be based on the contents of ".uuid" file in the directory rather than a hash of the directory name. On a pure debs system this doesn't really matter since everything is using the same libfontconfig.so. When snaps are involved, it can lead to some apps not seeing the cache files produced by a different fontconfig version. In particular, while libfontconfig 2.13 can reuse 2.12's cache files for read only directories, the reverse is not true. This will be a problem for apps built on top of the "core18" base snap when run on later Ubuntu releases (cosmic, disco, etc). By providing a backport of the UUID cache file feature to bionic for use by snap applications, we'd avoid this. Having it in bionic- updates would be ideal so that snapcraft picks it up automatically. [Impact] * This update changes how fontconfig cache files are named, instead of using md5($dir), it instead uses the contents of a $dir/.uuid file. No changes are made to the format of the cache file contents. * This change is primarily intended for use by snap applications built with core18: as the updated libfontconfig will fall back to the md5 cache file names for read-only directories without a .uuid file, they will be able to reuse cache files from any host system running fontconfig >= 2.11.95 [Test Case] * After installing the update, cache files should be generated in /var/cache/fontconfig/ with names like "07b67f7a-16ea-4440-9b6c- 21fc9153568c-le64.cache-7" (note the extra dashes not present in the MD5 based cache file names). [Regression Potential] * Applications using a non-default libfontconfig could end up not finding the new cache files and regenerating them in ~/.cache/fontconfig. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1803534/+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 1803534] Re: Backport uuid based cache file naming scheme
Sorry about that, I uploaded 2.12.6-0ubuntu2.2 yesterday which fixes this. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fontconfig in Ubuntu. https://bugs.launchpad.net/bugs/1803534 Title: Backport uuid based cache file naming scheme Status in fontconfig package in Ubuntu: New Status in fontconfig source package in Bionic: Fix Committed Bug description: Fontconfig 2.13.0 changed the cache file naming scheme to be based on the contents of ".uuid" file in the directory rather than a hash of the directory name. On a pure debs system this doesn't really matter since everything is using the same libfontconfig.so. When snaps are involved, it can lead to some apps not seeing the cache files produced by a different fontconfig version. In particular, while libfontconfig 2.13 can reuse 2.12's cache files for read only directories, the reverse is not true. This will be a problem for apps built on top of the "core18" base snap when run on later Ubuntu releases (cosmic, disco, etc). By providing a backport of the UUID cache file feature to bionic for use by snap applications, we'd avoid this. Having it in bionic- updates would be ideal so that snapcraft picks it up automatically. [Impact] * This update changes how fontconfig cache files are named, instead of using md5($dir), it instead uses the contents of a $dir/.uuid file. No changes are made to the format of the cache file contents. * This change is primarily intended for use by snap applications built with core18: as the updated libfontconfig will fall back to the md5 cache file names for read-only directories without a .uuid file, they will be able to reuse cache files from any host system running fontconfig >= 2.11.95 [Test Case] * After installing the update, cache files should be generated in /var/cache/fontconfig/ with names like "07b67f7a-16ea-4440-9b6c- 21fc9153568c-le64.cache-7" (note the extra dashes not present in the MD5 based cache file names). [Regression Potential] * Applications using a non-default libfontconfig could end up not finding the new cache files and regenerating them in ~/.cache/fontconfig. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1803534/+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 1552792] Re: gnome software leaves dependencies installed
I've verified this fixes the issue with the following versions: packagekit=1.1.9-1ubuntu2.18.04.4 gnome-software=3.28.1-0ubuntu4.18.04.7 ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to packagekit in Ubuntu. https://bugs.launchpad.net/bugs/1552792 Title: gnome software leaves dependencies installed Status in GNOME Software: Invalid Status in Release Notes for Ubuntu: Fix Released Status in gnome-software package in Ubuntu: Fix Released Status in packagekit package in Ubuntu: Fix Released Status in gnome-software source package in Bionic: Fix Committed Status in packagekit source package in Bionic: Fix Committed Status in gnome-software source package in Cosmic: Fix Released Status in packagekit source package in Cosmic: Fix Released Bug description: [Impact] Installing an application them removing it leaves dependencies behind. [Test Case] 1. Ensure that GNOME Sudoku is not installed: $ sudo apt remove gnome-sudoku libqqwing2v5 2. Check if you have any packages that need autoremoval: $ sudo apt autoremove --no-act 3. Open GNOME Software. 4. Search for and install GNOME Sudoku (make sure to install the .deb, not the snap). 5. Uninstall GNOME Sudoku. 6. Check if you have any packages that need autoremoval: $ sudo apt autoremove --no-act Expected result: The packages in step 6 are the same as in step 2 (which might be none). Observed result: The packages in step 6 includes libqqwing2v5, which is a dependency of gnome-sudoku and not useful without the game installed. [Regression Potential] This requires a fix to PackageKit which used to autoremove all packages (too aggressive), not just the ones related to the current transaction. A bug in the code could cause more packages to be removed than is suitable. GNOME Software previously didn't use this autoremove functionality, so by enabling it we could trigger a problem in either the existing code or the new fix. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-software/+bug/1552792/+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 1742997] Re: Newly installed applications are not showing in "Installed"
** Changed in: gnome-software (Ubuntu Bionic) Assignee: Olivier Tilloy (osomon) => Robert Ancell (robert-ancell) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to packagekit in Ubuntu. https://bugs.launchpad.net/bugs/1742997 Title: Newly installed applications are not showing in "Installed" Status in GNOME Software: Expired Status in gnome-software package in Ubuntu: Fix Released Status in packagekit package in Ubuntu: Invalid Status in gnome-software source package in Bionic: Confirmed Status in packagekit source package in Bionic: Invalid Bug description: If you install any application using GNOME Software (Ubuntu Software), the newly installed application is not displayed on the "Installed" tab. It starts showing after the next system reboot. Steps to Reproduce: 1. Find any application that is not installed and install it. 2. Switch to the "Installed" tab and try to find the newly installed application. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-software/+bug/1742997/+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 1795959] Re: [FFe] Seed xdg-desktop-portal-gtk
** Changed in: ubuntu-meta (Ubuntu) Assignee: (unassigned) => Ken VanDine (ken-vandine) -- 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/1795959 Title: [FFe] Seed xdg-desktop-portal-gtk Status in ubuntu-meta package in Ubuntu: Triaged Bug description: Security and MIR reviews have been completed for xdg-desktop-portal- gtk[1] and xdg-desktop-portal[2]. These packages can improve desktop integration of snap packages. The risk is low as nothing in the default desktop install actually exercises the portals at this time. We need to seed the portals so they are available when snaps are installed that can utilize them. Flatpak packages will also benefit. 1. https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal-gtk/+bug/1750069 2. https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal/+bug/1749672 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1795959/+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 1795959] [NEW] [FFe] Seed xdg-desktop-portal-gtk
Public bug reported: Security and MIR reviews have been completed for xdg-desktop-portal- gtk[1] and xdg-desktop-portal[2]. These packages can improve desktop integration of snap packages. The risk is low as nothing in the default desktop install actually exercises the portals at this time. We need to seed the portals so they are available when snaps are installed that can utilize them. Flatpak packages will also benefit. 1. https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal-gtk/+bug/1750069 2. https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal/+bug/1749672 ** Affects: ubuntu-meta (Ubuntu) Importance: Undecided Status: New ** Package changed: xdg-desktop-portal-gtk (Ubuntu) => ubuntu-meta (Ubuntu) -- 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/1795959 Title: [FFe] Seed xdg-desktop-portal-gtk Status in ubuntu-meta package in Ubuntu: New Bug description: Security and MIR reviews have been completed for xdg-desktop-portal- gtk[1] and xdg-desktop-portal[2]. These packages can improve desktop integration of snap packages. The risk is low as nothing in the default desktop install actually exercises the portals at this time. We need to seed the portals so they are available when snaps are installed that can utilize them. Flatpak packages will also benefit. 1. https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal-gtk/+bug/1750069 2. https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal/+bug/1749672 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1795959/+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 1788220] Re: [snap] Ubuntu 18.04 LTS includes gnome-calculator as a snap
This was caused by a fontconfig cache miss, which was caused by a difference in the fontconfig cache version between what's bundled in the snap vs the host cache on 18.04. This has been fixed with https://github.com/ubuntu/snapcraft-desktop-helpers/pull/144 ** Changed in: gnome-calculator (Ubuntu) Status: New => Fix Released ** Changed in: ubuntu-meta (Ubuntu) Status: New => Invalid -- 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/1788220 Title: [snap] Ubuntu 18.04 LTS includes gnome-calculator as a snap Status in gnome-calculator package in Ubuntu: Fix Released Status in ubuntu-meta package in Ubuntu: Invalid Bug description: Ubuntu 18.04 includes the calculator as a snap. The standard installation of snap, with no custom snap apps installed other than what Ubuntu installs by default, takes a whooping 1.6GB of hard disk. Calc takes forever to start in a modern machine compared to the normal calc installed with APT, creates snap files in the user's home dir (with name $HOME/snap). This is ridiculous. Snap is immature, there's no sysadmin tool support, and it's not ready to make it the default for standard Ubuntu LTS. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calculator/+bug/1788220/+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 1742997] Re: Newly installed applications are not showing in "Installed"
** Changed in: gnome-software (Ubuntu Bionic) Importance: Undecided => Low ** Changed in: gnome-software (Ubuntu Bionic) Assignee: (unassigned) => Olivier Tilloy (osomon) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to packagekit in Ubuntu. https://bugs.launchpad.net/bugs/1742997 Title: Newly installed applications are not showing in "Installed" Status in GNOME Software: Expired Status in gnome-software package in Ubuntu: Fix Released Status in packagekit package in Ubuntu: New Status in gnome-software source package in Bionic: Confirmed Status in packagekit source package in Bionic: New Bug description: If you install any application using GNOME Software (Ubuntu Software), the newly installed application is not displayed on the "Installed" tab. It starts showing after the next system reboot. Steps to Reproduce: 1. Find any application that is not installed and install it. 2. Switch to the "Installed" tab and try to find the newly installed application. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-software/+bug/1742997/+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 1780996] Re: Convert triggers to noawait
** Changed in: libreoffice (Ubuntu Xenial) Assignee: (unassigned) => Olivier Tilloy (osomon) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to shared-mime-info in Ubuntu. https://bugs.launchpad.net/bugs/1780996 Title: Convert triggers to noawait Status in appstream package in Ubuntu: Fix Released Status in bumblebee package in Ubuntu: Fix Released Status in clutter-imcontext package in Ubuntu: Triaged Status in django-countries package in Ubuntu: Fix Released Status in dochelp package in Ubuntu: Fix Released Status in dovecot package in Ubuntu: Fix Released Status in fusiondirectory package in Ubuntu: Fix Released Status in gdk-pixbuf package in Ubuntu: Fix Released Status in glib2.0 package in Ubuntu: Fix Released Status in gosa package in Ubuntu: Won't Fix Status in guile-2.0 package in Ubuntu: Fix Released Status in guile-2.2 package in Ubuntu: Fix Released Status in hicolor-icon-theme package in Ubuntu: Fix Released Status in libomxil-bellagio package in Ubuntu: Triaged Status in libreoffice package in Ubuntu: Fix Released Status in ltsp package in Ubuntu: Fix Released Status in mate-icon-theme package in Ubuntu: Fix Released Status in maxima package in Ubuntu: Fix Released Status in neurodebian package in Ubuntu: Fix Released Status in nevow package in Ubuntu: Fix Released Status in octave package in Ubuntu: Fix Released Status in packagekit package in Ubuntu: Fix Released Status in pike7.8 package in Ubuntu: Fix Released Status in pike8.0 package in Ubuntu: Fix Released Status in postgresql-common package in Ubuntu: Fix Released Status in qgis package in Ubuntu: Fix Released Status in reconf-inetd package in Ubuntu: Won't Fix Status in shared-mime-info package in Ubuntu: Fix Released Status in sphinx package in Ubuntu: Fix Released Status in syslog-ng-incubator package in Ubuntu: Fix Released Status in tex-common package in Ubuntu: Fix Released Status in wokkel package in Ubuntu: Fix Released Status in xpdf package in Ubuntu: Fix Released Status in yorick package in Ubuntu: Fix Released Status in appstream source package in Xenial: Fix Released Status in bumblebee source package in Xenial: Fix Released Status in clutter-imcontext source package in Xenial: Won't Fix Status in django-countries source package in Xenial: Fix Released Status in dochelp source package in Xenial: Fix Released Status in dovecot source package in Xenial: Fix Released Status in fusiondirectory source package in Xenial: Fix Released Status in gdk-pixbuf source package in Xenial: Fix Released Status in glib2.0 source package in Xenial: Fix Released Status in gosa source package in Xenial: Won't Fix Status in guile-2.0 source package in Xenial: Fix Released Status in hicolor-icon-theme source package in Xenial: Fix Released Status in libomxil-bellagio source package in Xenial: Triaged Status in libreoffice source package in Xenial: Triaged Status in ltsp source package in Xenial: Fix Released Status in mate-icon-theme source package in Xenial: Fix Released Status in maxima source package in Xenial: Fix Committed Status in neurodebian source package in Xenial: Fix Released Status in nevow source package in Xenial: Fix Released Status in octave source package in Xenial: Fix Released Status in packagekit source package in Xenial: Fix Released Status in pike7.8 source package in Xenial: Fix Released Status in pike8.0 source package in Xenial: Fix Released Status in postgresql-common source package in Xenial: Fix Released Status in qgis source package in Xenial: Fix Released Status in reconf-inetd source package in Xenial: Won't Fix Status in shared-mime-info source package in Xenial: Fix Released Status in sphinx source package in Xenial: Fix Released Status in syslog-ng-incubator source package in Xenial: Fix Released Status in tex-common source package in Xenial: Fix Released Status in wokkel source package in Xenial: Fix Released Status in xpdf source package in Xenial: Fix Released Status in yorick source package in Xenial: Fix Released Status in appstream source package in Bionic: Fix Released Status in bumblebee source package in Bionic: Fix Released Status in clutter-imcontext source package in Bionic: Won't Fix Status in django-countries source package in Bionic: Fix Released Status in dochelp source package in Bionic: Fix Released Status in dovecot source package in Bionic: Fix Released Status in fusiondirectory source package in Bionic: Fix Released Status in gdk-pixbuf source package in Bionic: Fix Released Status in glib2.0 source package in Bionic: Fix Released Status in gosa source package in Bionic: Won't Fix Status in guile-2.0 source package in Bionic: Fix Released Status in guile-2.2 source package in Bionic: Fix Released Status in hicolor-icon-theme source package in Bionic: Fix
[Touch-packages] [Bug 1773213] Re: U1 login dialog missing link to the privacy policy
** Description changed: The U1 login for g-o-a is missing a link to the privacy policy. + + [Impact] + + * No way to view the privacy policy for Ubuntu One + + [Test Case] + + * Open gnome-control-center + * Select "Online Accounts" on the left + * Select "Ubuntu Single Sign-On" under "Add an account" + * Not you should see a link to open the Privacy Policy on the bottom left of the dialog. + * Verify when clicking the window a browser window opens with our data privacy page + + [Regression Potential] + + * None -- 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/1773213 Title: U1 login dialog missing link to the privacy policy Status in gnome-online-accounts package in Ubuntu: Fix Released Status in gnome-online-accounts source package in Bionic: New Bug description: The U1 login for g-o-a is missing a link to the privacy policy. [Impact] * No way to view the privacy policy for Ubuntu One [Test Case] * Open gnome-control-center * Select "Online Accounts" on the left * Select "Ubuntu Single Sign-On" under "Add an account" * Not you should see a link to open the Privacy Policy on the bottom left of the dialog. * Verify when clicking the window a browser window opens with our data privacy page [Regression Potential] * None To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1773213/+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 1166811] Re: Cannot retweet from friends-app
** Changed in: friends-app (Ubuntu) Assignee: Ken VanDine (ken-vandine) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to friends-app in Ubuntu. https://bugs.launchpad.net/bugs/1166811 Title: Cannot retweet from friends-app Status in Friends: Invalid Status in friends-app package in Ubuntu: Triaged Bug description: I see a tweet in the friends-app window. Clicking on the little twitter bird icon does nothing. This used to bring up a menu which allowed me to retweet, reply, etc. There appears to be no way to do that with friends-app now. Similarly with FB posts, clicking on the F icon does nothing. Note that clicking on the heart does seem to "like" the post. There does appear to be some magical whitespace on right side of each post. Clicking in this area sometimes brings up a reply box, sometimes hides the reply box, and sometimes makes my browser go to the tweet/post in question. To manage notifications about this bug go to: https://bugs.launchpad.net/friends/+bug/1166811/+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 1430075] Re: Allow apps receiving a push import to set the ContentStore
** Changed in: content-hub (Ubuntu) Assignee: Ken VanDine (ken-vandine) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to content-hub in Ubuntu. https://bugs.launchpad.net/bugs/1430075 Title: Allow apps receiving a push import to set the ContentStore Status in content-hub package in Ubuntu: Triaged Bug description: Apps receiving a pull import (one they initiated) can set the ContentStore to have the content delivered to a permanent location. However, apps receiving a push import (initiated from without) cannot, and thus always receive content in the volatile ~/.cache directory. If they wish to save it permanently or be able to modify it, they must move it themselves. Since apps will likely try to share code between the two import paths, I suspect this will cause most apps to ignore the ContentStore and handle file management manually in both cases. We should allow the ContentStore to be set on push imports as well, so that receivers can always make use of it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/content-hub/+bug/1430075/+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 1443982] Re: [phone-app]Allow the user to manually configure a voicemail number
** Changed in: dialer-app (Ubuntu) Assignee: Ken VanDine (ken-vandine) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dialer-app in Ubuntu. https://bugs.launchpad.net/bugs/1443982 Title: [phone-app]Allow the user to manually configure a voicemail number Status in Canonical System Image: Confirmed Status in Ubuntu UX: Triaged Status in dialer-app package in Ubuntu: Confirmed Bug description: Version: ubuntu-touch/stable/bq-aquaris.en r20 krillin As of at least the above version there is no way to configure a voicemail number for the phone manually. If the system is able to pull the voicemail number from the SIM then the 1 button on the dialer has a speed dial functionality of calling voicemail. There is no way to enable this in the case that a voicemail number is not available from the SIM. --- UX comment Users will be able to set a voicemail number in application settings. In this particular case it will be in the phone app. <https://goo.gl/tmgI1H> This is currently work in progress. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1443982/+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 1168943] Re: Friends does not present RT in official way: missing original avatar and pseudo, messages truncated
** Changed in: friends-app (Ubuntu) Assignee: Ken VanDine (ken-vandine) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to friends-app in Ubuntu. https://bugs.launchpad.net/bugs/1168943 Title: Friends does not present RT in official way: missing original avatar and pseudo, messages truncated Status in Friends: Triaged Status in friends-app package in Ubuntu: Triaged Bug description: Hello, When someone I follow on Twitter or Identica RT a tweet from the official way (ie not makes manually a citation with "RT @...") by using "Retweet" option, I expect to see the message in my Timeline as it appears on Twitter website. It means : avatar and pseudo of original author of message retweeted, and below a row which says "Shared" or "RT by @..." and name of user who made the RT. Because RT are a way to make your followers discover new interesting users and be able to follow them. I guess Friends will have soon an option to directly follow an user from a menu coming after click on his avatar or name, so for that we need the original ones, not those of the person who did the RT (see screenshot). Another problem : when you RT a message which is already 140 characters, the way Friends presents : it adds on the beginning of the message "RT @" and name of author, which reduces number of characters available. So often the end of message is truncated : we miss end of sentance, or sometimes URL links are no more correct and can not be visited from the RT. I hope it will be possible to make it like official Twitter behavior :) To manage notifications about this bug go to: https://bugs.launchpad.net/friends/+bug/1168943/+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 1166813] Re: No way to configure friends-app or filter posts
** Changed in: friends-app (Ubuntu) Assignee: Ken VanDine (ken-vandine) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to friends-app in Ubuntu. https://bugs.launchpad.net/bugs/1166813 Title: No way to configure friends-app or filter posts Status in friends-app package in Ubuntu: Triaged Bug description: AFAICT, there is no way to filter posts, even like the old gwibber interface. Say I only want to view my twitter feed, or private messages, or home page, or search for something. Even though the old gwibber button semantics were fuzzy, there's nothing like that at all with friends-app. It's just a firehose of posts. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/friends-app/+bug/1166813/+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 1177943] Re: reply field obscured by OSK
** Changed in: friends-app (Ubuntu) Assignee: Ken VanDine (ken-vandine) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to friends-app in Ubuntu. https://bugs.launchpad.net/bugs/1177943 Title: reply field obscured by OSK Status in friends-app package in Ubuntu: Confirmed Bug description: friends-app 0.90.0bzr13.04.17-0ubuntu1 running on ubuntu-touch image 118 on maguro (galaxy nexus) After I manually configure my twitter account and run the app, I try to reply by selecting the reply field. This brings up the OSK which obscures the entry field and you can see what you are typing. Look at the code in the messaging menu as this has a similar ui and does the scrolling correctly. Steps to reproduce: on device: sudo apt-get install friends-app uoa-create twitter type in username/password in auth ui that comes up account-console edit 1 --enable --service twitter-microblog the in the apps lens, click the search button and type "friends" then launch the app from the launcher, should bring up friends app loaded with twitter messages click on a message and try to reply osk gets obscured To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/friends-app/+bug/1177943/+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 1342031] Re: Rename QML modules to follow qml-module-foo naming
** Changed in: bacon2d (Ubuntu)
Assignee: Ken VanDine (ken-vandine) => (unassigned)
** Changed in: content-hub (Ubuntu)
Assignee: Ken VanDine (ken-vandine) => (unassigned)
** Changed in: qml-box2d (Ubuntu)
Assignee: Ken VanDine (ken-vandine) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to content-hub in Ubuntu.
https://bugs.launchpad.net/bugs/1342031
Title:
Rename QML modules to follow qml-module-foo naming
Status in accounts-qml-module package in Ubuntu:
Fix Released
Status in address-book-app package in Ubuntu:
Fix Released
Status in bacon2d package in Ubuntu:
Triaged
Status in clickmanager-plugin package in Ubuntu:
New
Status in content-hub package in Ubuntu:
New
Status in cordova-ubuntu package in Ubuntu:
New
Status in dee-qt package in Ubuntu:
New
Status in gsettings-qt package in Ubuntu:
New
Status in history-service package in Ubuntu:
New
Status in libhud-qt package in Ubuntu:
Won't Fix
Status in libqofono package in Ubuntu:
Fix Released
Status in libusermetrics package in Ubuntu:
New
Status in mediascanner2 package in Ubuntu:
Fix Released
Status in oxide-qt package in Ubuntu:
New
Status in poppler-qml-plugin package in Ubuntu:
New
Status in qml-box2d package in Ubuntu:
New
Status in qml-friends package in Ubuntu:
New
Status in qt3d-opensource-src package in Ubuntu:
Fix Released
Status in qtconnectivity-opensource-src package in Ubuntu:
Fix Released
Status in qtdeclarative-opensource-src package in Ubuntu:
Fix Released
Status in qtfeedback-opensource-src package in Ubuntu:
Fix Released
Status in qtgrilo package in Ubuntu:
New
Status in qtlocation-opensource-src package in Ubuntu:
Fix Released
Status in qtmultimedia-opensource-src package in Ubuntu:
Fix Released
Status in qtpim-opensource-src package in Ubuntu:
Fix Released
Status in qtquickcontrols-opensource-src package in Ubuntu:
Fix Released
Status in qtsensors-opensource-src package in Ubuntu:
Fix Released
Status in qtsystems-opensource-src package in Ubuntu:
Fix Released
Status in reminders-app package in Ubuntu:
New
Status in solid package in Ubuntu:
New
Status in sync-monitor package in Ubuntu:
New
Status in telephony-service package in Ubuntu:
Triaged
Status in thumbnailer package in Ubuntu:
Fix Released
Status in u1db-qt package in Ubuntu:
Confirmed
Status in ubuntu-download-manager package in Ubuntu:
Triaged
Status in ubuntu-keyboard package in Ubuntu:
New
Status in ubuntu-settings-components package in Ubuntu:
In Progress
Status in ubuntu-system-settings-online-accounts package in Ubuntu:
Fix Released
Status in ubuntu-ui-extras package in Ubuntu:
New
Status in ubuntu-ui-toolkit package in Ubuntu:
Fix Released
Status in ubuntuone-credentials package in Ubuntu:
Fix Released
Status in unity-action-api package in Ubuntu:
Triaged
Status in unity-notifications package in Ubuntu:
New
Status in webbrowser-app package in Ubuntu:
Fix Released
Status in ubuntu-ui-toolkit package in Ubuntu RTM:
Fix Released
Bug description:
UPDATE: This would be a nice to have for Ubuntu 16.04 LTS, since otherwise we
will need to keep the transitional packages until 2018.
UPDATE2: This would be a nice to have for Ubuntu 18.04 LTS, since otherwise
we will need to keep the transitional packages until 2020.
===
The package names of QML modules should be of the format qml-
module-{$modulename}[version], a transition that was started during Qt
5.3 preparation in Ubuntu. For example this could be qml-module-
qtquick-localstorage or qml-module-qtsysteminfo for non versioned
modules, and qml-module-ubuntu-webthing0.3 for versioned/co-
installable modules.
Further details in Debian e-mail:
http://lists.alioth.debian.org/pipermail/pkg-kde-
talk/2014-March/001889.html
For Ubuntu, transitional packages should be put in place for smooth
distribution upgrades, since we're shipping with the old names in previous
Ubuntus. An example of that is at
http://bazaar.launchpad.net/~kubuntu-packagers/kubuntu-packaging/qtsystems-opensource-src/revision/31
- in other words:
- Make the old package a transitional oldlibs package that depends on the new
package
- Add Breaks/Replaces to the new package for the old non-transitional
packages (be careful about the version number specification)
- Keep Multi-Arch: same and Architecture: any for the transitional package
- Write "QML module" instead of "QML plugin"
- Rename also the *.install files
---
One more example on naming:
For example, the "test" (qtdeclarative5-test-plugin) in the old
qtdeclarative5-style package naming became "qttest" (qml-module-
qttest) in the new naming since the path is actually under
/usr/lib/*/qt5/qml/QtTest/
qml-module-qtquick-xmllistmodel has path
/usr/lib/*/qt5/qml/QtQuick/XmlListModel, as an example if yo
[Touch-packages] [Bug 1552774] Re: /var/spool/cron/ should be readwrite for phablet user
** Changed in: lxc-android-config (Ubuntu) Assignee: Ken VanDine (ken-vandine) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc-android-config in Ubuntu. https://bugs.launchpad.net/bugs/1552774 Title: /var/spool/cron/ should be readwrite for phablet user Status in Canonical System Image: Confirmed Status in lxc-android-config package in Ubuntu: Confirmed Bug description: Hi. "crontab -e" is broken unless /var/spool/cron/ is writable. Currently (build 266 vegetahd) this happens: crontab: installing new crontab /var/spool/cron/: mkstemp: Read-only file system crontab: edits left in /tmp/crontab.xvMe2c/crontab phablet@orc:~/ To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1552774/+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 1429693] Re: Provide a ContentItem.delete() method
** Changed in: content-hub (Ubuntu) Assignee: Ken VanDine (ken-vandine) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to content-hub in Ubuntu. https://bugs.launchpad.net/bugs/1429693 Title: Provide a ContentItem.delete() method Status in content-hub package in Ubuntu: Confirmed Bug description: If you import a file with ContentScope.App, you'll get a copy of it in your silo. If it turns out that it's not of the right type, or when you're done with it, it would be nice to be able to delete your copy. At the moment, you can only do such operations via a C++ plugin. It'd be nice to provide an API on the ContentItem that would let you delete the file directly in QML. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/content-hub/+bug/1429693/+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 1324987] Re: implement handler-hints
** Changed in: content-hub (Ubuntu) Assignee: Ken VanDine (ken-vandine) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to content-hub in Ubuntu. https://bugs.launchpad.net/bugs/1324987 Title: implement handler-hints Status in content-hub package in Ubuntu: New Bug description: add support for specific hints in the handler to be able to accept multiple paramenters To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/content-hub/+bug/1324987/+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 979186] Re: vino-server crashed with SIGSEGV in tp_connection_get_contacts_by_handle()
** Changed in: telepathy-glib (Ubuntu) Assignee: Ken VanDine (ken-vandine) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to telepathy-glib in Ubuntu. https://bugs.launchpad.net/bugs/979186 Title: vino-server crashed with SIGSEGV in tp_connection_get_contacts_by_handle() Status in telepathy-glib package in Ubuntu: Confirmed Bug description: Apport report. Tried to share desktop with jabber contact. ProblemType: Crash DistroRelease: Ubuntu 12.04 Package: vino 3.4.0-0ubuntu3 Uname: Linux 3.3.0-1.dmz.1-liquorix-amd64 x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.0.1-0ubuntu1 Architecture: amd64 Date: Wed Apr 11 19:02:56 2012 EcryptfsInUse: Yes ExecutablePath: /usr/lib/vino/vino-server InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64+mac (20111012) ProcCmdline: /usr/lib/vino/vino-server --sm-disable ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, user) LANG=en_GB.UTF-8 SHELL=/usr/bin/zsh SegvAnalysis: Segfault happened at: 0x7f6e9cde6a5d <tp_connection_get_contacts_by_handle+29>: mov0x48(%rdi),%rax PC (0x7f6e9cde6a5d) ok source "0x48(%rdi)" (0x0048) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: vino StacktraceTop: tp_connection_get_contacts_by_handle () from /usr/lib/libtelepathy-glib.so.0 ?? () ?? () ?? () from /usr/lib/libtelepathy-glib.so.0 ?? () from /usr/lib/libtelepathy-glib.so.0 Title: vino-server crashed with SIGSEGV in tp_connection_get_contacts_by_handle() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare vboxusers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/telepathy-glib/+bug/979186/+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 907916] Re: empathy crashed with SIGSEGV in empathy_contact_get_alias()
** Changed in: folks (Ubuntu) Assignee: Ken VanDine (ken-vandine) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to folks in Ubuntu. https://bugs.launchpad.net/bugs/907916 Title: empathy crashed with SIGSEGV in empathy_contact_get_alias() Status in empathy package in Ubuntu: Fix Released Status in folks package in Ubuntu: Confirmed Bug description: This crash occurs when trying to add a new contact and when trying to place a "New call" to a SIP number not in the contact list. ProblemType: Crash DistroRelease: Ubuntu 12.04 Package: empathy 3.3.3-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-6.12-generic 3.2.0-rc6 Uname: Linux 3.2.0-6-generic x86_64 ApportVersion: 1.90-0ubuntu1 Architecture: amd64 CheckboxSubmission: 1e7afd42fe45733e86839c658e18c54d CheckboxSystem: bb422ca46d02494cdbc459927a98bc2f Date: Thu Dec 22 16:02:04 2011 ExecutablePath: /usr/bin/empathy InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha amd64 (20110802) ProcCmdline: empathy SegvAnalysis: Segfault happened at: 0x47e766 <empathy_contact_get_account+22>: cmp %rax,(%rdx) PC (0x0047e766) ok source "%rax" ok destination "(%rdx)" (0xe7894cc689f2894c) not located in a known VMA region (needed writable region)! SegvReason: writing unknown VMA Signal: 11 SourcePackage: empathy StacktraceTop: empathy_contact_get_account (contact=) at empathy-contact.c:978 empathy_new_call_dialog_response (dialog=0x2302a80, response_id=-3) at empathy-new-call-dialog.c:99 g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: empathy crashed with SIGSEGV in empathy_contact_get_account() UpgradeStatus: Upgraded to precise on 2011-11-08 (44 days ago) UserGroups: adm admin cdrom dialout libvirtd lpadmin plugdev sambashare To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/907916/+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 976463] Re: mission-control-5 crashed with SIGABRT in __libc_message()
** Changed in: telepathy-glib (Ubuntu Precise) Assignee: Ken VanDine (ken-vandine) => (unassigned) ** Changed in: telepathy-glib (Ubuntu) Assignee: Ken VanDine (ken-vandine) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to telepathy-glib in Ubuntu. https://bugs.launchpad.net/bugs/976463 Title: mission-control-5 crashed with SIGABRT in __libc_message() Status in telepathy-glib package in Ubuntu: Confirmed Status in telepathy-glib source package in Precise: Confirmed Bug description: Crash when empathy is open ProblemType: Crash DistroRelease: Ubuntu 12.04 Package: telepathy-mission-control-5 1:5.12.0-0ubuntu2 ProcVersionSignature: Ubuntu 3.2.0-22.35-generic-pae 3.2.14 Uname: Linux 3.2.0-22-generic-pae i686 ApportVersion: 2.0-0ubuntu4 Architecture: i386 CrashCounter: 1 Date: Sun Apr 8 10:32:46 2012 ExecutablePath: /usr/lib/telepathy/mission-control-5 InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta i386 (20120328) ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-3.2.0-22-generic-pae root=UUID=8d150169-5e88-4885-9b44-d1a61449b3c6 ro quiet splash vt.handoff=7 ProcEnviron: SHELL=/bin/bash PATH=(custom, no user) LANG=fr_FR.UTF-8 Signal: 6 SourcePackage: telepathy-mission-control-5 Title: mission-control-5 crashed with SIGABRT in raise() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/telepathy-glib/+bug/976463/+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 864764] Re: empath forgets accounts 11.10
** Changed in: telepathy-mission-control-5 (Ubuntu) Assignee: Ken VanDine (ken-vandine) => (unassigned) -- 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/864764 Title: empath forgets accounts 11.10 Status in telepathy-mission-control-5 package in Ubuntu: Confirmed Bug description: After a logout, all account information inside empathy is lost.empathy doesnot remebers the accounts using 11.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/telepathy-mission-control-5/+bug/864764/+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 1163658] Re: Duplicate Online Accounts launchers
** Changed in: gnome-control-center-signon (Ubuntu)
Assignee: Ken VanDine (ken-vandine) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gnome-control-center-
signon in Ubuntu.
https://bugs.launchpad.net/bugs/1163658
Title:
Duplicate Online Accounts launchers
Status in gnome-control-center-signon package in Ubuntu:
Fix Committed
Bug description:
gnome-control-center-signon ships both gnome-credentials-panel.desktop
and credentials-preferences.desktop in /usr/share/applications. This
results in two launchers with the same icon and name ("Online
Accounts") showing up in the Unity Dash, GNOME Shell's Activities
Overview and elsewhere. One launches a standalone Ubuntu Online
Accounts app ; the other launches the integrated System Settings
panel.
Perhaps the standalone launcher should be OnlyShowIn=GNOME; and the
integrated one be NotShowIn=GNOME; as the Ubuntu GNOME (UG) developers
would prefer to have System Settings to generally follow the GNOME
design when a user runs GNOME Shell (in other words, UG want the
standalone version but not the integrated one). If you do this,
perhaps the launcher should be renamed 'Ubuntu Online Accounts' so
that it's distinguishable from the other 'Online Accounts' launcher
(with a different icon) shipped as part of GNOME (gnome-online-
accounts). UG currently needs to ship both UOA and GOA.
Alternatively, the .desktop's could be shipped in two different binary
packages. To reduce confusion you may want to have those two packages
conflict with each other.
ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: gnome-control-center-signon 0.1.5-0ubuntu1
ProcVersionSignature: Ubuntu 3.8.0-15.25-generic 3.8.4
Uname: Linux 3.8.0-15-generic x86_64
ApportVersion: 2.9.2-0ubuntu5
Architecture: amd64
Date: Tue Apr 2 22:22:42 2013
MarkForUpload: True
SourcePackage: gnome-control-center-signon
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center-signon/+bug/1163658/+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 1165239] Re: visual response of buttons
** Changed in: friends-app (Ubuntu) Assignee: Ken VanDine (ken-vandine) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to friends-app in Ubuntu. https://bugs.launchpad.net/bugs/1165239 Title: visual response of buttons Status in friends-app package in Ubuntu: Triaged Bug description: One does not know if a button is clicked. A visual feedback signal is useful (for example while refreshing). In addition, it should be recognized that the mouse pointer is over a button. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/friends-app/+bug/1165239/+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 1161546] Re: Disabled accounts data appears in timeline
** Changed in: friends-app (Ubuntu) Assignee: Ken VanDine (ken-vandine) => (unassigned) ** Changed in: gwibber Assignee: Ken VanDine (ken-vandine) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to friends-app in Ubuntu. https://bugs.launchpad.net/bugs/1161546 Title: Disabled accounts data appears in timeline Status in Friends: Expired Status in Gwibber: Invalid Status in friends-app package in Ubuntu: Incomplete Bug description: If you toggle off an online account, it doesn't remove posts from timeline To repeat: Add an online account, eg facebook Start gwibber --Timeline fills up with facebook posts Close gwibber Toggle account off in online accounts (both setting 'gwibber' to off, or turning off the entire account) gwibber still contains the previous data from the account EDIT: It appears that if I completely remove the account from online accounts the data is removed from gwibber.. Is this intended? If I disable an account I simply get no new data from the data source, and I must remove the account completely to remove the data? (If so, what about the other account integration points I may want to keep?) To manage notifications about this bug go to: https://bugs.launchpad.net/friends/+bug/1161546/+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 1166815] Re: "gwibber" is still offered by command-not-found
** Changed in: friends-app (Ubuntu) Assignee: Ken VanDine (ken-vandine) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to friends-app in Ubuntu. https://bugs.launchpad.net/bugs/1166815 Title: "gwibber" is still offered by command-not-found Status in friends-app package in Ubuntu: Triaged Bug description: After dist-upgrade'ing, the gwibber command goes away. friends-app is the replacement. However, dist-upgrade will remove the 'gwibber' package and not leave you with friends-app command. Type 'gwibber' at the cli and command-not-found will tell you that 'gwibber' is part of the 'gwibber' package. Re-apt-get that package but you still don't get a 'gwibber' command, so command-not-found will again tell you to install 'gwibber'. However the 'gwibber' package *does* give you friends-app. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/friends-app/+bug/1166815/+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 1421241] Re: OOM score for apps waiting on content hub should be adjusted
** Changed in: content-hub (Ubuntu) Assignee: Ken VanDine (ken-vandine) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to content-hub in Ubuntu. https://bugs.launchpad.net/bugs/1421241 Title: OOM score for apps waiting on content hub should be adjusted Status in Canonical System Image: Confirmed Status in Ubuntu Application Launcher: New Status in content-hub package in Ubuntu: Confirmed Status in qtmir package in Ubuntu: Confirmed Bug description: I happens that the app gets killed by OOM while it is being put into background importing something from the content hub. I think apps waiting on something from the content hub should have a better OOM score to make it less likely. Even if the app is restarted automatically after picking content from the hub, the transfer will fail because it lost the pointer to the transfer object. On bq, if apps have some data in it, this becomes really a problem. For example it's close to impossible to add a new contact to telegram if there are many apps openened, because Telegram seems to have a higher OOM score than most other things, and it gets killed while the user picks some contact from the address book. The user has to manually close all other apps, sometimes even reboot before being able to do that again. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1421241/+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 1364452] Re: People's own phone number isn't where they expect to find it
** Changed in: ubuntu-system-settings (Ubuntu) Assignee: Ken VanDine (ken-vandine) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to address-book-app in Ubuntu. https://bugs.launchpad.net/bugs/1364452 Title: People's own phone number isn't where they expect to find it Status in Canonical System Image: Confirmed Status in address-book-app package in Ubuntu: Triaged Status in ubuntu-system-settings package in Ubuntu: Confirmed Bug description: Twenty people were given an Ubuntu phone and asked to find their own phone number. (10 were iPhone users, 8 Android, 1 Windows Phone, and 1 feature phone user.) The first place they looked: - 9 in the Contacts app - 5 in System Settings "Phone" screen - 3 in System Settings "About" screen - 2 in the Dialer app contacts screen - 1 in System Settings "Cellular" screen. So, our current placement of the phone number in the "About" screen (bug 1221908) is suboptimal. Instead it should be in the Contacts app, and possibly in the "Phone" screen. Where the phone is dual SIM, both phone numbers should be shown. Only once that is done, it should be removed from the "About" screen. <https://goo.gl/XCquqY>: "Address Book should always contain one special contact representing you as the user of the phone ... To indicate its purpose and resilience, the “Me” contact should be denoted by the word “Me” as a caption at the trailing end (with a translation hint stating that it should be extremely short); and the contact’s visual design should be subtly different from other contacts. Apart from those two differences, the contact should be displayed and ordered the same as any other contacts in the list..." To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1364452/+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 1167205] Re: Twitter integration appears to have vanished
** Changed in: unity-lens-friends (Ubuntu) Assignee: Ken VanDine (ken-vandine) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to friends-app in Ubuntu. https://bugs.launchpad.net/bugs/1167205 Title: Twitter integration appears to have vanished Status in friends-app package in Ubuntu: Confirmed Status in unity-lens-friends package in Ubuntu: Triaged Bug description: The online account screen is saying that no application is installed which integrates with the Twitter account ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: friends-twitter 0.1.3daily13.04.05-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-17.27-generic 3.8.6 Uname: Linux 3.8.0-17-generic x86_64 ApportVersion: 2.9.2-0ubuntu5 Architecture: amd64 CheckboxSubmission: 55cafa5b8b82ed224cc59d444cb1fc25 CheckboxSystem: 3e53d3ea5811723345f19eff5070f9ab Date: Wed Apr 10 09:37:19 2013 InstallationDate: Installed on 2012-02-20 (414 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) MarkForUpload: True PackageArchitecture: all SourcePackage: friends UpgradeStatus: Upgraded to raring on 2013-04-05 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/friends-app/+bug/1167205/+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 1166413] Re: friends-app crashes with segmentation fault
** Changed in: friends-app (Ubuntu) Assignee: Ken VanDine (ken-vandine) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to friends-app in Ubuntu. https://bugs.launchpad.net/bugs/1166413 Title: friends-app crashes with segmentation fault Status in friends-app package in Ubuntu: Confirmed Bug description: virtual void FriendsPlugin::registerTypes(const char*) Friends virtual void OnlineAccounts::Plugin::registerTypes(const char*) Ubuntu.OnlineAccounts QQmlComponent: Component is not ready StreamModelPrivate::StreamModelPrivate(StreamModel*) MODEL: "com.canonical.Friends.Streams" account-service-model.cpp 266 update Segmentation fault (core dumped) ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: friends-app 0.90.0bzr13.04.05-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-15.25-generic 3.8.4 Uname: Linux 3.8.0-15-generic x86_64 ApportVersion: 2.9.2-0ubuntu5 Architecture: amd64 Date: Mon Apr 8 21:29:36 2013 InstallationDate: Installed on 2012-06-07 (304 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) MarkForUpload: True SourcePackage: friends-app UpgradeStatus: Upgraded to raring on 2012-12-28 (100 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/friends-app/+bug/1166413/+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 1168892] Re: Special characters like "&" are well posted but not seen on the Friends application
** Changed in: friends-app (Ubuntu) Assignee: Ken VanDine (ken-vandine) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to friends-app in Ubuntu. https://bugs.launchpad.net/bugs/1168892 Title: Special characters like "&" are well posted but not seen on the Friends application Status in Friends: Invalid Status in friends-app package in Ubuntu: Incomplete Bug description: Hello, I know Friends is just in the early beginning of development and that you work actively on it, so it's normal that lots of features from Gwibber are missing (like managing on Friends window someone's timeline, (un)-subscribe, having links automatically reduced with ur1.ca or others, perhaps multi-columns etc...), they will come one by one in the next weeks, so I won't report bugs from that. But there are some "problems" that are real bugs. Here is one : When I add a special character like "&" (symbol for "and") in the compose message window for Identica, no problem in the writing, it shows well and is counted as 1. But after message has been sent, on Friends interface the "&" and all the characters after it don't appear on the message, this one is not complete. It's only a problem of viewing in Friends, because on Identica the whole message is well posted without error (see screenshot with the 3 steps). Thanks ! To manage notifications about this bug go to: https://bugs.launchpad.net/friends/+bug/1168892/+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 1166351] Re: should inform users of service errors in the UI
** Changed in: friends-app (Ubuntu) Assignee: Ken VanDine (ken-vandine) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to friends-app in Ubuntu. https://bugs.launchpad.net/bugs/1166351 Title: should inform users of service errors in the UI Status in friends-app package in Ubuntu: Triaged Bug description: Using the current raring version, my facebook timeline was failing so I killed the friends-service, the UI is empty since. It seems like the dispatcher is hitting a 500 error on the fb servers ... when that happens it would be nice to let the user know in the UI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/friends-app/+bug/1166351/+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 1171670] Re: [indicators] Provide Ability To Post via Message Icon in Global Menu Bar
** Changed in: friends-app (Ubuntu) Assignee: Ken VanDine (ken-vandine) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to friends-app in Ubuntu. https://bugs.launchpad.net/bugs/1171670 Title: [indicators] Provide Ability To Post via Message Icon in Global Menu Bar Status in Friends: Confirmed Status in friends-app: New Status in Ubuntu UX: Triaged Status in friends-app package in Ubuntu: Confirmed Bug description: Using friends in 13.04, installed via `sudo apt-get install friends` In recent versions of Ubuntu (prior to writing this) I was able to click the message icon (currently a snail mail icon) and update my status on Identi.ca (and others) from the menu. Now, i cannot. Please bring that feature back. Thank you for your consideration. To manage notifications about this bug go to: https://bugs.launchpad.net/friends/+bug/1171670/+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 1317627] Re: Content hub experience needs to be implemented using trusted sessions
** Changed in: content-hub (Ubuntu) Assignee: Ken VanDine (ken-vandine) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to content-hub in Ubuntu. https://bugs.launchpad.net/bugs/1317627 Title: Content hub experience needs to be implemented using trusted sessions Status in content-hub package in Ubuntu: Triaged Bug description: This was discovered changing the background image on manta in image u17. STEPS: 1. Open system-settings 2. Click on backgrounds 3. Click on the welcome screen 4. Select Photo/Image 5. Select an image 6. Now try and hit the set button 7. You can't as it lives behind the system-settings app in the sidestage Solution: The full screen app should be given priority while it has focus and the sidestage should be able to be dragged in, on close the sidestage is automatically draw out again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/content-hub/+bug/1317627/+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 1182886] Re: URL Shortener management : provider choice (ur1.ca) and characters count (19 - 22 regarding t.co)
** Changed in: friends-app (Ubuntu) Assignee: Ken VanDine (ken-vandine) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to friends-app in Ubuntu. https://bugs.launchpad.net/bugs/1182886 Title: URL Shortener management : provider choice (ur1.ca) and characters count (19 - 22 regarding t.co) Status in friends-app package in Ubuntu: New Bug description: Hello, I have a question and a potential problem about URL shortening in Friends : For the moment only is.gd service can be used by default (if I'm not wrong). I hope that in the future we will be able to define which one we prefer in a list of many providers, like for example http://ur1.ca Also, there is an issue when posting to Twitter with Friends and using some URL shorteners : Both is.gd and ur1.ca create short redirected links which address has exactly 19 cgaracters. But Twitter automatically transforms ALL links - even already shortened by another provider - through its service t.co Problem : t.co addres have 22 cgaracters... So as Friends counts is.gd for 19, we can write a message up to 138-139-140 characters which will never succeed to be posted in Twitter because with t.co link it will exceed the limit. Solution : for Twitter messages, when a link is made and shortened by is.gd (or in the future ur1.ca / other service), Friends should always count it as 22 characters and let us know on the bottom right the real number of remaining. Of course this does not apply to Identi.ca which does not re-short the links automatically (it can if we modify our options in Identi.ca, for example wih ur1.ca) but it is not the default behavior so Friends should count is.gd or ur1.ca as 19 characters (and non-shortened links on the real number). If the user configured Identi.ca to cross-post to Twitter, it's not Friends problem, it's the user's. But, last case, if on Friends the user wants to send a message in both Twitter AND Identi.ca here there is a choice to make to decide how Friends should act : I would say that we have to take the lower limit and count every link as 22 characters, to be sure it will be posted successfully in the 2 accounts. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/friends-app/+bug/1182886/+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 1425949] Re: Needs to support direct searching of contacts
** Changed in: content-hub (Ubuntu) Assignee: Ken VanDine (ken-vandine) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to content-hub in Ubuntu. https://bugs.launchpad.net/bugs/1425949 Title: Needs to support direct searching of contacts Status in Canonical System Image: Confirmed Status in Dekko: Triaged Status in content-hub package in Ubuntu: Confirmed Bug description: Use case: - contact auto-completion When typing addressees in an email app, you want to be able to use auto-completion from your contacts without disclosing more data than necessary. The only secure way seems to be for the content hub to own the display of matching results, otherwise we're opening ourselves to a brute- force attack to get data on all the contacts. So my proposal would be that, as usual, a content hub operation is started for the search (decorated with originator geometry most likely), the hub queries all relevant data sources and displays a list of matching results. The search query will need to be updated as the user types. Selecting one of those would trigger the actual content exchange. This type of prompt could not gain focus (as to allow the user to continue typing in the text entry), and would probably need to support some styling properties to make it fit within the originator app. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1425949/+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 1532158] Re: autopkgtest aa-check fail on xenial and vivid+overlay on armhf
** Changed in: content-hub (Ubuntu) Assignee: Ken VanDine (ken-vandine) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to content-hub in Ubuntu. https://bugs.launchpad.net/bugs/1532158 Title: autopkgtest aa-check fail on xenial and vivid+overlay on armhf Status in Canonical System Image: Confirmed Status in content-hub package in Ubuntu: Confirmed Bug description: aa-check test fails in autopkgtest [1] on xenial and vivid+overlay on armhf The error from the log is: adt-run [06:30:03]: test aa-check: [--- content-hub-test-ok failed virtual void com::ubuntu::content::Hub::register_import_export_handler(com::ubuntu::content::ImportExportHandler*) Failed to register object for: "content-hub-test-importer" adt-run [06:30:08]: test aa-check: ---] aa-check FAIL non-zero exit status 1 [1] http://autopkgtest.ubuntu.com/packages/c/content-hub/xenial/armhf/ To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1532158/+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 1542208] Re: With side stage, content hub transfer dialog overlaps with the called app
** Changed in: content-hub (Ubuntu) Assignee: Ken VanDine (ken-vandine) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to content-hub in Ubuntu. https://bugs.launchpad.net/bugs/1542208 Title: With side stage, content hub transfer dialog overlaps with the called app Status in Canonical System Image: Confirmed Status in Ubuntu UX: New Status in content-hub package in Ubuntu: Confirmed Status in unity8 package in Ubuntu: Confirmed Bug description: On a device that supports side stage in landscape more Test Case: 1. Open the contact app 2. Create a new contact 3. Add a photo 4. Select the camera Actual Result The camera controls are hidden behind the transfer window Expected Result The transfer dialog is not visible. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1542208/+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 1625068] Re: aethercast binaries disappeared from the system
** Changed in: ubuntu-system-settings (Ubuntu) Assignee: Ken VanDine (ken-vandine) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-touch-meta in Ubuntu. https://bugs.launchpad.net/bugs/1625068 Title: aethercast binaries disappeared from the system Status in Canonical System Image: Fix Committed Status in aethercast package in Ubuntu: Confirmed Status in ubuntu-system-settings package in Ubuntu: Confirmed Status in ubuntu-touch-meta package in Ubuntu: Fix Released Status in ubuntu-touch-meta package in Ubuntu RTM: Fix Released Bug description: After update to 182, the aethercast binaries disappeared from the system, leaving the external display page in system-settings broken. phablet@ubuntu-phablet:~$ system-image-cli -i current build number: 182 device name: turbo channel: ubuntu-touch/rc-proposed/meizu-pd.en last update: 2016-09-18 20:11:35 version version: 182 version ubuntu: 20160917 version device: 20160824-d33b825 version custom: 20160831-992-8-12 UPDATE: I've been told the change to make aethercast an option suggestion in system-settings caused to not have aethercast pulled in in the image builds. It seems like there are 2 fixes needed: a) Seed aethercast in relevant phone images b) fix system-settings to hide the external display section when aethercast is not around. Currently the button is there but just does nothing. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1625068/+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 1429899] Re: StateSaver should not restore when app launched from content-hub
** Changed in: content-hub (Ubuntu) Assignee: Ken VanDine (ken-vandine) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to content-hub in Ubuntu. https://bugs.launchpad.net/bugs/1429899 Title: StateSaver should not restore when app launched from content-hub Status in content-hub package in Ubuntu: In Progress Status in ubuntu-ui-toolkit package in Ubuntu: Incomplete Bug description: Testing the messaging-app state saving ability that we've been adding from this MR: https://code.launchpad.net/~tiagosh/messaging-app/state-saver2/+merge/250996 deb can be found here: http://jenkins.qa.ubuntu.com/job/generic-mediumtests-builder-vivid-armhf/1669/artifact/work/output/*zip*/output.zip The problem is, when the app is launched from the content-hub, the StateSaver still tries to restore it's previously saved state, but it should not and this causes problems. It should clear the state, the same way it does when launched via url-dispatcher. According to Ken, there are content-hub signals that StateSaver will need to listen to in order to know when the app is being launched by content-hub. To reproucde: 1) install the messaging-app deb from above 2) open messaging-app, swipe from bottom to create a new message 3) type some names in the recipient field, and type some message in the send field 4) do "kill -2 " to kill the messaging-app and save it's state 5) open camera-app and go to the photo roll 6) press "Share" from toolbar and select messaging-app from the list Expected results: - messaging-app should be displayed with a new page showing the photo as an attachment, and nothing else Actual results: - messaging-app shows the restored state from when it was last run (the values entered in Step 3 above) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/content-hub/+bug/1429899/+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 1324985] Re: add mime-type support
** Changed in: content-hub (Ubuntu) Assignee: Ken VanDine (ken-vandine) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to content-hub in Ubuntu. https://bugs.launchpad.net/bugs/1324985 Title: add mime-type support Status in Canonical System Image: In Progress Status in content-hub package in Ubuntu: In Progress Bug description: post RTM we need to be able to specify either Category types or specific mime-types for import/export/share handlers in the hub To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1324985/+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 1433297] Re: tests could fail without failing the test suite
** Changed in: content-hub (Ubuntu) Assignee: Ken VanDine (ken-vandine) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to content-hub in Ubuntu. https://bugs.launchpad.net/bugs/1433297 Title: tests could fail without failing the test suite Status in content-hub package in Ubuntu: In Progress Bug description: Currently we could have individual test failures that do not fail the test suite. Running individual tests will show the proper failure count, but when run as part of the full suite (make test) the failed test won't be reported. I went through them and it doesn't look like we have any current failures, but this issue will prevent us from catching failures in the future. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/content-hub/+bug/1433297/+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 1471998] Re: [enhancement] Support copy-paste between X and Mir
** Changed in: content-hub (Ubuntu) Status: In Progress => Won't Fix ** Changed in: content-hub (Ubuntu) Assignee: Ken VanDine (ken-vandine) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to content-hub in Ubuntu. https://bugs.launchpad.net/bugs/1471998 Title: [enhancement] Support copy-paste between X and Mir Status in Canonical System Image: Fix Released Status in Libertine: Fix Released Status in Libertine devel series: Fix Released Status in Libertine trunk series: Fix Released Status in Mir: Fix Released Status in content-hub package in Ubuntu: Won't Fix Status in libertine package in Ubuntu: Fix Released Status in mir package in Ubuntu: Fix Released Status in qtmir package in Ubuntu: Fix Released Status in qtubuntu package in Ubuntu: Fix Released Bug description: X applications should be able to paste from Mir applications and vice versa. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1471998/+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 1541609] Re: Process got into a state where no downloads occur
** Changed in: ubuntu-system-settings (Ubuntu) Assignee: Ken VanDine (ken-vandine) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-download-manager in Ubuntu. https://bugs.launchpad.net/bugs/1541609 Title: Process got into a state where no downloads occur Status in Canonical System Image: Fix Released Status in ubuntu-download-manager package in Ubuntu: In Progress Status in ubuntu-system-settings package in Ubuntu: In Progress Bug description: Went to settings > Updates and asked to Install all updates, there were 3 apps available Left the panel Cam back some mins later, the first app had finished and was gone from the list. The next two were there in a new state Asked to instal the first app , progress bar appeared but nothing happened. From the attached u-d-m log I see it attempted the download but then just exited after the timer fired. Then tried to download a new app from the store. The UI changed to show it should install but no progress changes. In this case I did not see a new log created. Going back into the updates panel I see log files being created each time without issuing a new request. Arale on rc-proposed Was on cellular data at the time, wifi was off To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1541609/+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 1656252] Re: Applications fail to start on the second use
** Changed in: camera-app (Ubuntu) Assignee: Ken VanDine (ken-vandine) => (unassigned) ** Changed in: address-book-app (Ubuntu) Assignee: Ken VanDine (ken-vandine) => (unassigned) ** Changed in: gallery-app (Ubuntu) Assignee: Ken VanDine (ken-vandine) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to camera-app in Ubuntu. https://bugs.launchpad.net/bugs/1656252 Title: Applications fail to start on the second use Status in Canonical System Image: Fix Released Status in address-book-app package in Ubuntu: In Progress Status in camera-app package in Ubuntu: In Progress Status in gallery-app package in Ubuntu: In Progress Status in ubuntu-app-launch package in Ubuntu: Invalid Status in unity8 package in Ubuntu: Invalid Status in webbrowser-app package in Ubuntu: New Bug description: zesty desktop unity8 session snap 349 Test Case: 1. Launch the webbrowser from the app scope 2. close it (or the app crashes) 3. Launch the webbrowser from the app scope Expected result: It starts twice Actual result It does not always starts and it hangs on the launch window (blank window, with the webbrowser icon and a spinning loading icon) When it occurs it is very reproducible and a reboot of the machine is required to make it work again. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1656252/+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 934291] Re: Deleting or stopping print jobs does not work
@odyx do you think the patch in comment #53 is suitable for debian? I'd like to avoid a delta with debian if possible, so i'll defer sponsoring this until we have some agreement on the fix. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/934291 Title: Deleting or stopping print jobs does not work Status in gnome-control-center: Unknown Status in cups package in Ubuntu: Invalid Status in cups-pk-helper package in Ubuntu: In Progress Status in gnome-control-center package in Ubuntu: Invalid Bug description: Deleting or stopping print jobs through the "gnome-control-center -> printers" menu is not possible. (Black rectangle for stopping can be pressed, nothing happens.) Deleting with cups via webinterface does work. ( http://localhost:631/ ) Please let me know which information to provide. Cheers ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: gnome-control-center 1:3.2.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.0.0-16.28-generic 3.0.17 Uname: Linux 3.0.0-16-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 1.23-0ubuntu4 Architecture: amd64 Date: Fri Feb 17 16:47:32 2012 InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to oneiric on 2011-12-17 (61 days ago) usr_lib_gnome-control-center: deja-dup 22.0~bzr1290.37~oneiric1 gnome-bluetooth3.2.0-0ubuntu2 indicator-datetime 0.3.1-0ubuntu1.1 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/934291/+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 961679] Re: gtkrc is producing light menus from dark elements
** Also affects: ubuntu-themes (Ubuntu Xenial) 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/961679 Title: gtkrc is producing light menus from dark elements Status in ubuntu-themes package in Ubuntu: Fix Released Status in ubuntu-themes source package in Xenial: New Bug description: Examples - Right click on any window's title bar In app window menus of gtk 2 apps, examples - synaptic, browsers where global menus aren't used, vlc with no global menu, ect. Right click in a browser's menu bar Systray right click menus The in app window context menu of gtk2 windows is correctly light, maybe there is no way to have both, ie., it's either all dark or all light? The choice here would be to go with all dark if there is no other way ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: light-themes 0.1.8.31-0ubuntu1 [modified: usr/share/themes/Ambiance/gtk-2.0/gtkrc usr/share/themes/Ambiance/gtk-3.0/apps/nautilus.css usr/share/themes/Ambiance/gtk-3.0/gtk-widgets.css usr/share/themes/Ambiance/gtk-3.0/gtk.css usr/share/themes/Ambiance/gtk-3.0/settings.ini usr/share/themes/Ambiance/metacity-1/close.png usr/share/themes/Ambiance/metacity-1/close_focused_normal.png usr/share/themes/Ambiance/metacity-1/close_focused_prelight.png usr/share/themes/Ambiance/metacity-1/close_focused_pressed.png usr/share/themes/Ambiance/metacity-1/metacity-theme-1.xml] ProcVersionSignature: Ubuntu 3.2.0-19.30-generic-pae 3.2.11 Uname: Linux 3.2.0-19-generic-pae i686 NonfreeKernelModules: nvidia ApportVersion: 1.94.1-0ubuntu2 Architecture: i386 Date: Wed Mar 21 17:42:27 2012 InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta i386 (20120301) PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: light-themes UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/961679/+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 1664205] Re: Copy-paste and text selection doesn't work when caps-lock is on
** Also affects: nux (Ubuntu Xenial) Importance: Undecided Status: New -- 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/1664205 Title: Copy-paste and text selection doesn't work when caps-lock is on Status in nux package in Ubuntu: Fix Released Status in nux source package in Xenial: New Bug description: [Impact] Text entry doesn't properly accept Ctrl+[letter] based shortcuts when Caps Lock is on [Test case] 0) Set Caps-Lock on in your keyboard 1) Open dash, and write something 2) Ctrl+A should select all the text, Ctrl+C should copy, Ctrl+V should paste and Ctrl+X should cut Currently they don't work unless caps-lock is turned off [Possible regression] Ctrl+[letter] shortcuts or Ins based shortcuts for text selection handling won't work anymore To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nux/+bug/1664205/+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 1715719] Re: systemd v232+ journals aren't compatible with journalctrl from 229
** Description changed: - systemd v232+ journals aren't compatible with journalctrl from 229 + In my attempt to snap gnome-logs, I've run into an issue where gnome- + logs fails to get the journal when run on an artful host. The snap is + built in a xenial chroot against xenial + gnome-3-24 backports PPA. The + same snap does work when run on a 16.04 host. - This normally isn't a problem, but in trying to create a snap for gnome- - logs I've run into a situation where we need to build the snap for 16.04 - which has libsystemd0=229. This snap works fine if the host is running - 16.04 as well. But on an artful host, the snap fails to access the - journal. I've tested backporting v232 from zesty to xenial and building - my snap with libsystem0 232. This works fine on 16.04 and 17.10 hosts. + artful has libsystemd0 234 and xenial has libsystemd0 229. I took a + stab at building libsystemd0 232 on xenial then build the snap with + libsystemd0 232. The resulting snap works fine on 16.04 and 17.10 + hosts. + + To summarize, we need a libsystemd0 built for xenial bundled in the + gnome-logs snap that is compatible with the running systemd on the host. + The basic rebuild of 232 for xenial is compatible with systemd from + xenial through artful. But we want to be sure backporting that in a + supported PPA is not a bad idea. Ideally we would just cherry pick + whatever 229 is lacking in our PPA. @xnox suggested v232+ journals are built with more features enabled. -- 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/1715719 Title: systemd v232+ journals aren't compatible with journalctrl from 229 Status in systemd package in Ubuntu: New Bug description: In my attempt to snap gnome-logs, I've run into an issue where gnome- logs fails to get the journal when run on an artful host. The snap is built in a xenial chroot against xenial + gnome-3-24 backports PPA. The same snap does work when run on a 16.04 host. artful has libsystemd0 234 and xenial has libsystemd0 229. I took a stab at building libsystemd0 232 on xenial then build the snap with libsystemd0 232. The resulting snap works fine on 16.04 and 17.10 hosts. To summarize, we need a libsystemd0 built for xenial bundled in the gnome-logs snap that is compatible with the running systemd on the host. The basic rebuild of 232 for xenial is compatible with systemd from xenial through artful. But we want to be sure backporting that in a supported PPA is not a bad idea. Ideally we would just cherry pick whatever 229 is lacking in our PPA. @xnox suggested v232+ journals are built with more features enabled. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1715719/+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 1715719] [NEW] systemd v232+ journals aren't compatible with journalctrl from 229
Public bug reported: systemd v232+ journals aren't compatible with journalctrl from 229 This normally isn't a problem, but in trying to create a snap for gnome- logs I've run into a situation where we need to build the snap for 16.04 which has libsystemd0=229. This snap works fine if the host is running 16.04 as well. But on an artful host, the snap fails to access the journal. I've tested backporting v232 from zesty to xenial and building my snap with libsystem0 232. This works fine on 16.04 and 17.10 hosts. @xnox suggested v232+ journals are built with more features enabled. ** Affects: systemd (Ubuntu) Importance: Undecided Assignee: Dimitri John Ledkov (xnox) Status: New ** Changed in: systemd (Ubuntu) Assignee: (unassigned) => Dimitri John Ledkov (xnox) -- 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/1715719 Title: systemd v232+ journals aren't compatible with journalctrl from 229 Status in systemd package in Ubuntu: New Bug description: systemd v232+ journals aren't compatible with journalctrl from 229 This normally isn't a problem, but in trying to create a snap for gnome-logs I've run into a situation where we need to build the snap for 16.04 which has libsystemd0=229. This snap works fine if the host is running 16.04 as well. But on an artful host, the snap fails to access the journal. I've tested backporting v232 from zesty to xenial and building my snap with libsystem0 232. This works fine on 16.04 and 17.10 hosts. @xnox suggested v232+ journals are built with more features enabled. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1715719/+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 1708141] Re: Zoom control in gnome-maps has misaligned boraders
** Description changed: - GNOME Maps has vertically joined buttons for zoom control. Looks fine + GNOME Maps has vertically linked buttons for zoom control. Looks fine with Adwaita, but with Ambiance the border doesn't align when joined vertically. See attached screenshots. ** Summary changed: - Zoom control in gnome-maps has misaligned boraders + Vertically linked button borders incorrect -- 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/1708141 Title: Vertically linked button borders incorrect Status in ubuntu-themes package in Ubuntu: New Bug description: GNOME Maps has vertically linked buttons for zoom control. Looks fine with Adwaita, but with Ambiance the border doesn't align when joined vertically. See attached screenshots. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1708141/+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 1708141] [NEW] Vertically linked button borders incorrect
Public bug reported: GNOME Maps has vertically linked buttons for zoom control. Looks fine with Adwaita, but with Ambiance the border doesn't align when joined vertically. See attached screenshots. ** Affects: ubuntu-themes (Ubuntu) Importance: Undecided Status: New ** Tags: gnome-17.10 ** Attachment added: "Ambiance" https://bugs.launchpad.net/bugs/1708141/+attachment/4925790/+files/GNOME%20Maps%20-%20Ambiance.png ** Tags added: gnome-17.10 -- 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/1708141 Title: Vertically linked button borders incorrect Status in ubuntu-themes package in Ubuntu: New Bug description: GNOME Maps has vertically linked buttons for zoom control. Looks fine with Adwaita, but with Ambiance the border doesn't align when joined vertically. See attached screenshots. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1708141/+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 1675012] [NEW] [content-hub] not switching to picking mode when launched by the peer picker
Public bug reported: When choose webbrowser-app as a source for content from the peer picker when the browser is not already running, it doesn't go into picking mode. However, if the browser is already running it switches nicely to picking mode. Maybe a race condition at startup missing the signal. ** Affects: webbrowser-app (Ubuntu) Importance: Undecided Status: New -- 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/1675012 Title: [content-hub] not switching to picking mode when launched by the peer picker Status in webbrowser-app package in Ubuntu: New Bug description: When choose webbrowser-app as a source for content from the peer picker when the browser is not already running, it doesn't go into picking mode. However, if the browser is already running it switches nicely to picking mode. Maybe a race condition at startup missing the signal. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1675012/+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 1673550] Re: Windows not remembering previous size on unity8
** Changed in: ubuntu-system-settings (Ubuntu) Assignee: Jonas G. Drange (jonas-drange) => Ken VanDine (ken-vandine) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1673550 Title: Windows not remembering previous size on unity8 Status in Canonical System Image: New Status in ubuntu-system-settings package in Ubuntu: Incomplete Status in unity8 package in Ubuntu: New Bug description: running u8 desktop session Steps to reproduce: - open u-s-s - resize the window to 2 column mode - close the app with X from window control - restart the app Expected results: - u-s-s should open at the size it was last closed at Actutual results: - u-s-s window is smaller only showing one column This may be related to limiting the max size which we used to have? I think we should remove all max sizing restrictions on the app, and bring back the maximize button which is not displayed either. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1673550/+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 1650022] Re: We need a "close" action for killing an app in a trust prompt
@mpt from my understanding of the original designs, content picking was one of the use cases. There was a desire to open the source app in a trust prompt for the duration of the content picking operation. Keeping the users work flow from switching focus to another app, we are embedding the source app in the app requesting the content. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1650022 Title: We need a "close" action for killing an app in a trust prompt Status in Canonical System Image: New Status in Ubuntu UX: Incomplete Status in unity8 package in Ubuntu: Confirmed Bug description: The original designs for trust prompts included a close action in the header to close apps that were opened in a trust session. This is particularly important when apps might not behave well or hang, there is no way out. The close action is like a back button to take you back out of the app. We're close to landing trust session support in content-hub, where we'll open source apps for content picking in a trust prompt. We've found apps that have a tendency to hang, leaving the user no way out besides killing both the source and destination apps. Clearly those apps need some fixing, but we need to give the user an easy way out. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1650022/+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 1656358] Re: dash crashes if an app is launched with system's u-a-l instead of unity8-session.u-a-l
I can confirm this bug on xenial+overlay+silo 2129, however slightly different. This doesn't crash the dash: ubuntu-app-launch ubuntu-calculator-app_ubuntu-calculator-app_26 This does crash the dash: ubuntu-app-launch ubuntu-calculator-app -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1656358 Title: dash crashes if an app is launched with system's u-a-l instead of unity8-session.u-a-l Status in Canonical System Image: New Status in unity8 package in Ubuntu: New Bug description: zesty + unity8-session 349 Test Case: 1. Launch an app from the command line with system's ual. For example $ ubuntu-app-launch ubuntu-calculator-app_ubuntu-calculator-app_26 Expected result The app fails to launch but the dash doesn't crash Actual result The app fails to launch and the dash crashes. Launching with unity8-session.u-a-l works as expected. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1656358/+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 1656252] Re: frequently applications fails to start
I can confirm that removing single instance from the desktop file works around it. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1656252 Title: some applications fail to start twice Status in Canonical System Image: Confirmed Status in unity8 package in Ubuntu: Confirmed Bug description: zesty desktop unity8 session snap 349 Test Case: 1. Launch the webbrowser from the app scope 2. close it 3. Launch the webbrowser from the app scope Expected result: It starts twice Actual result It does not always starts and it hangs on the launch window (blank window, with the webbrowser icon and a spinning loading icon) When it occurs it is very reproducible and a reboot of the machine is required to make it work again. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1656252/+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 1650022] [NEW] We need a "close" action for killing an app in a trust prompt
Public bug reported: The original designs for trust prompts included a close action in the header to close apps that were opened in a trust session. This is particularly important when apps might not behave well or hang, there is no way out. The close action is like a back button to take you back out of the app. We're close to landing trust session support in content-hub, where we'll open source apps for content picking in a trust prompt. We've found apps that have a tendency to hang, leaving the user no way out besides killing both the source and destination apps. Clearly those apps need some fixing, but we need to give the user an easy way out. ** Affects: unity8 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1650022 Title: We need a "close" action for killing an app in a trust prompt Status in unity8 package in Ubuntu: New Bug description: The original designs for trust prompts included a close action in the header to close apps that were opened in a trust session. This is particularly important when apps might not behave well or hang, there is no way out. The close action is like a back button to take you back out of the app. We're close to landing trust session support in content-hub, where we'll open source apps for content picking in a trust prompt. We've found apps that have a tendency to hang, leaving the user no way out besides killing both the source and destination apps. Clearly those apps need some fixing, but we need to give the user an easy way out. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1650022/+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 1649932] Re: crashes when opening from the peer picker on unity8 desktop
** Attachment added: "_usr_bin_camera-app.1000.crash" https://bugs.launchpad.net/ubuntu/+source/camera-app/+bug/1649932/+attachment/4791620/+files/_usr_bin_camera-app.1000.crash -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to camera-app in Ubuntu. https://bugs.launchpad.net/bugs/1649932 Title: crashes when opening from the peer picker on unity8 desktop Status in camera-app package in Ubuntu: New Bug description: If camera-app is already running when selected in the peer picker, it switches to picking mode just fine. However if camera-app is not running, it crashes on startup when selected from the peer picker. In order to get camera-app to show up in the peer picker, you need a deb built from my branch[1] and run the hook[2] manually once after installing the deb. 1. https://code.launchpad.net/~ken-vandine/camera-app/content-hub_and_add-profile/+merge/313232 2. /usr/lib/x86_64-linux-gnu/content-hub/content-hub-peer-hook upstart log: Loading module: 'libubuntu_application_api_desktop_mirclient.so.3.0.0' Import path added "/usr/lib/x86_64-linux-gnu/camera-app" Camera app directory "/usr/share/camera-app/" qq= QDeclarativeCamera_QML_37(0x224) 0x248c610 Focus mode selection is not supported No media control support for org.qt-project.qt.cameraflashcontrol/5.0 No flash control support No media control support for org.qt-project.qt.cameraexposurecontrol/5.0 No exposure control support No media control support for org.qt-project.qt.cameraflashcontrol/5.0 No flash control support No media control support for org.qt-project.qt.cameraexposurecontrol/5.0 No exposure control support QFileSystemWatcher::removePaths: list is empty DelegateModel::item: index out range 0 0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/camera-app/+bug/1649932/+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 1649932] [NEW] crashes when opening from the peer picker on unity8 desktop
Public bug reported: If camera-app is already running when selected in the peer picker, it switches to picking mode just fine. However if camera-app is not running, it crashes on startup when selected from the peer picker. In order to get camera-app to show up in the peer picker, you need a deb built from my branch[1] and run the hook[2] manually once after installing the deb. 1. https://code.launchpad.net/~ken-vandine/camera-app/content-hub_and_add-profile/+merge/313232 2. /usr/lib/x86_64-linux-gnu/content-hub/content-hub-peer-hook upstart log: Loading module: 'libubuntu_application_api_desktop_mirclient.so.3.0.0' Import path added "/usr/lib/x86_64-linux-gnu/camera-app" Camera app directory "/usr/share/camera-app/" qq= QDeclarativeCamera_QML_37(0x224) 0x248c610 Focus mode selection is not supported No media control support for org.qt-project.qt.cameraflashcontrol/5.0 No flash control support No media control support for org.qt-project.qt.cameraexposurecontrol/5.0 No exposure control support No media control support for org.qt-project.qt.cameraflashcontrol/5.0 No flash control support No media control support for org.qt-project.qt.cameraexposurecontrol/5.0 No exposure control support QFileSystemWatcher::removePaths: list is empty DelegateModel::item: index out range 0 0 ** Affects: camera-app (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to camera-app in Ubuntu. https://bugs.launchpad.net/bugs/1649932 Title: crashes when opening from the peer picker on unity8 desktop Status in camera-app package in Ubuntu: New Bug description: If camera-app is already running when selected in the peer picker, it switches to picking mode just fine. However if camera-app is not running, it crashes on startup when selected from the peer picker. In order to get camera-app to show up in the peer picker, you need a deb built from my branch[1] and run the hook[2] manually once after installing the deb. 1. https://code.launchpad.net/~ken-vandine/camera-app/content-hub_and_add-profile/+merge/313232 2. /usr/lib/x86_64-linux-gnu/content-hub/content-hub-peer-hook upstart log: Loading module: 'libubuntu_application_api_desktop_mirclient.so.3.0.0' Import path added "/usr/lib/x86_64-linux-gnu/camera-app" Camera app directory "/usr/share/camera-app/" qq= QDeclarativeCamera_QML_37(0x224) 0x248c610 Focus mode selection is not supported No media control support for org.qt-project.qt.cameraflashcontrol/5.0 No flash control support No media control support for org.qt-project.qt.cameraexposurecontrol/5.0 No exposure control support No media control support for org.qt-project.qt.cameraflashcontrol/5.0 No flash control support No media control support for org.qt-project.qt.cameraexposurecontrol/5.0 No exposure control support QFileSystemWatcher::removePaths: list is empty DelegateModel::item: index out range 0 0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/camera-app/+bug/1649932/+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 1649696] Re: /usr/include/mirclient/mir_toolkit/events/event.h:24:32: fatal error: mir_toolkit/common.h: No such file or directory
I've confirmed that a reinstall of libmircommon-dev, libmirclient-dev and libmircore-dev seemed to have fixed it. Not sure what was up with that! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1649696 Title: /usr/include/mirclient/mir_toolkit/events/event.h:24:32: fatal error: mir_toolkit/common.h: No such file or directory Status in Mir: Incomplete Status in Mir 0.25 series: Incomplete Status in mir package in Ubuntu: Incomplete Bug description: A header from libmirclient-dev has an include for a file that used to be in libmircommon-dev, which seems to have been removed in 0.25.0+16.04.20161203-0ubuntu1 libmircommon-dev=0.24.1+16.04.20160928-0ubuntu1 did have mir_toolkit/common.h To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1649696/+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
