[Touch-packages] [Bug 2024680] Re: Dell XPS 9730 no sound, I have tried the 22.04 lts same issue
It's fixed in ubuntu 23.10, thanks to kernel 6.5 I guess. -- 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/2024680 Title: Dell XPS 9730 no sound, I have tried the 22.04 lts same issue Status in pulseaudio package in Ubuntu: Confirmed Bug description: I've tried various fixes without success, I did manage to get the NVIDA HDMI in the sound options but I've never had the inbuilt Intel Media Hardware working for sound. 22.04 LTS had the same issue and I've upgraded to the new version 23.04 which looks good. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: pulseaudio 1:16.1+dfsg1-2ubuntu3 ProcVersionSignature: Ubuntu 6.2.0-23.23-generic 6.2.12 Uname: Linux 6.2.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: daniel 2245 F wireplumber /dev/snd/seq:daniel 2241 F pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Jun 22 17:30:27 2023 InstallationDate: Installed on 2023-06-16 (5 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/23/2023 dmi.bios.release: 1.2 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.2 dmi.board.name: 067X4F dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.ec.firmware.release: 1.1 dmi.modalias: dmi:bvnDellInc.:bvr1.2.2:bd03/23/2023:br1.2:efr1.1:svnDellInc.:pnXPS179730:pvr:rvnDellInc.:rn067X4F:rvrA00:cvnDellInc.:ct10:cvr:sku0BDB: dmi.product.family: XPS dmi.product.name: XPS 17 9730 dmi.product.sku: 0BDB dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/2024680/+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 1451103] Re: ubuntu-standard depends on cron
systemd-cron 2;x with it's C++ rewrite in pretty good shape, could be Ubuntu default cron even for 24.04 -- 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/1451103 Title: ubuntu-standard depends on cron Status in ubuntu-meta package in Ubuntu: Confirmed Bug description: ubuntu-standard have a hardcoded dependency on cron package. Instead it should depend on systemd-cron to decrease learning curve for new users and simplify system maintenance: it's much easier if periodic tasks are administered the same way as all other tasks - via standard units. People who need legacy software for some reason could easily install it from the repository. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1451103/+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 2019940] Re: Directly manipulating NetworkManager keyfiles
Please provide output of "cruft-ng" on an updated system. I'm not running Ubuntu. -- 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/2019940 Title: Directly manipulating NetworkManager keyfiles Status in augeas package in Ubuntu: New Status in calamares package in Ubuntu: New Status in cloud-init package in Ubuntu: Invalid Status in cruft package in Ubuntu: Won't Fix Status in cruft-ng package in Ubuntu: New Status in dracut package in Ubuntu: New Status in forensic-artifacts package in Ubuntu: New Status in guestfs-tools package in Ubuntu: New Status in guix package in Ubuntu: New Status in ltsp package in Ubuntu: Invalid Status in netcfg package in Ubuntu: Won't Fix Status in netplan.io package in Ubuntu: Invalid Status in network-manager package in Ubuntu: New Status in refpolicy package in Ubuntu: New Status in sosreport package in Ubuntu: Invalid Status in ubiquity package in Ubuntu: New Status in uhd package in Ubuntu: New Status in vagrant package in Ubuntu: New Bug description: The affected packages can manipulate NetworkManager keyfiles directly on disk, which might not be appropriate anymore on Ubuntu, since the Netplan integration was enabled in NetworkManager (starting with Mantic), migrating any keyfile configuration from /etc/NetworkManager/system-connections/*[.nmconnection] to /etc/netplan/90-NM-*.yaml See Netplan's documentation for how connections are handled: https://netplan.readthedocs.io/en/latest/netplan-everywhere/ PS: Packages were queried using: https://codesearch.debian.net/search?q=%2Fsystem-connections&literal=1&perpkg=1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/augeas/+bug/2019940/+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 1993037] Re: Ubuntu debianutils moved run-parts into /usr/bin, breaking systemd-cron in the course
* Revert move to /usr (no. 5). closes: #992481, #992615, #992639, #992649 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to debianutils in Ubuntu. https://bugs.launchpad.net/bugs/1993037 Title: Ubuntu debianutils moved run-parts into /usr/bin, breaking systemd- cron in the course Status in debianutils package in Ubuntu: New Status in systemd-cron package in Ubuntu: New Bug description: package debianutils keeps run-parts executable in /usr/bin/ while package systemd-cron tries to find it in /bin/ $ which run-parts /usr/bin/run-parts $ dpkg -S `which run-parts` debianutils: /usr/bin/run-parts $ grep =/bin/run /lib/systemd/system/cron* /lib/systemd/system/cron-daily.service:ExecStart=/bin/run-parts --report /etc/cron.daily /lib/systemd/system/cron-hourly.service:ExecStart=/bin/run-parts --report /etc/cron.hourly /lib/systemd/system/cron-monthly.service:ExecStart=/bin/run-parts --report /etc/cron.monthly /lib/systemd/system/cron-weekly.service:ExecStart=/bin/run-parts --report /etc/cron.weekly Because of that, cron-daily.serice gets info "failed" state soon after system reboot. Please resolve the problem to make systemd-cron more usable. Thanks in advance for your help. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debianutils/+bug/1993037/+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 1990113] Re: Increase timeout on test doc-check for RISC-V
At the moment, RISC-V is built with the dpkg nocheck flag so this error does not show up for now. But I'm working on fixing all the nocheck related errors and this patch is part of it. I'll send the patch to Debian instead as it is not urgent. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to json-glib in Ubuntu. https://bugs.launchpad.net/bugs/1990113 Title: Increase timeout on test doc-check for RISC-V Status in json-glib package in Ubuntu: Incomplete Bug description: The doc-check test fails on RISC-V because it is a very slow architecture: fix this by increasing the timeout on this specific test. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/json-glib/+bug/1990113/+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 1990961] Re: package linux-image-5.15.0-48-generic 5.15.0-48.54~20.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
Given your comment and dmesg log full of "PCIe error", this look like a hardware failure. I mark this bug as invalid. ** Changed in: initramfs-tools (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1990961 Title: package linux-image-5.15.0-48-generic 5.15.0-48.54~20.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Status in initramfs-tools package in Ubuntu: Invalid Bug description: Not entirely sure what happened but I believe it was due to my computer switching off as it was booting. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-image-5.15.0-48-generic 5.15.0-48.54~20.04.1 ProcVersionSignature: Ubuntu 5.15.0-46.49~20.04.1-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Sep 23 10:39:58 2022 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 InstallationDate: Installed on 2022-09-06 (21 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3.2 apt 2.0.9 SourcePackage: initramfs-tools Title: package linux-image-5.15.0-48-generic 5.15.0-48.54~20.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1990961/+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 1990113] Re: Increase timeout on test doc-check for RISC-V
The package built successfully here: https://launchpad.net/~alexghiti/+archive/ubuntu/riscv/+sourcepub/13962373/+listing- archive-extra ** Attachment added: "debdiff" https://bugs.launchpad.net/ubuntu/+source/json-glib/+bug/1990113/+attachment/5616956/+files/debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to json-glib in Ubuntu. https://bugs.launchpad.net/bugs/1990113 Title: Increase timeout on test doc-check for RISC-V Status in json-glib package in Ubuntu: New Bug description: The doc-check test fails on RISC-V because it is a very slow architecture: fix this by increasing the timeout on this specific test. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/json-glib/+bug/1990113/+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 1990113] [NEW] Increase timeout on test doc-check for RISC-V
Public bug reported: The doc-check test fails on RISC-V because it is a very slow architecture: fix this by increasing the timeout on this specific test. ** Affects: json-glib (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to json-glib in Ubuntu. https://bugs.launchpad.net/bugs/1990113 Title: Increase timeout on test doc-check for RISC-V Status in json-glib package in Ubuntu: New Bug description: The doc-check test fails on RISC-V because it is a very slow architecture: fix this by increasing the timeout on this specific test. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/json-glib/+bug/1990113/+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 1971901]
*** Bug 53675 has been marked as a duplicate of this bug. *** -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/1971901 Title: dlltool uses non-unique temp filenames Status in binutils: Fix Released Status in Wine: Won't Fix Status in binutils package in Ubuntu: Confirmed Status in binutils-mingw-w64 package in Ubuntu: Confirmed Bug description: Description:Ubuntu 22.04 LTS Release:22.04 binutils-mingw-w64-x86-64 2.38-3ubuntu1+9build1 /usr/bin/x86_64-w64-mingw32-dlltool now encounters errors like tools/winebuild/winebuild -b x86_64-w64-mingw32 -w --implib -o dlls/winmm/libwinmm.delay.a --export \ ../wine-6.0.4/dlls/winmm/winmm.spec Assembler messages: Error: can't open winmm_dll_t.s for reading: No such file or directory /usr/bin/x86_64-w64-mingw32-dlltool: /usr/bin/x86_64-w64-mingw32-as exited with status 1 /usr/bin/x86_64-w64-mingw32-dlltool: failed to open temporary tail file: winmm_dll_t.o: No such file or directory winebuild: /usr/bin/x86_64-w64-mingw32-dlltool failed with status 1 make: *** [Makefile:195227: dlls/winmm/libwinmm.delay.a] Error 1 make: *** Waiting for unfinished jobs tools/winebuild/winebuild -b x86_64-w64-mingw32 -w --implib -o dlls/winmm/libwinmm.cross.a --export \ ../wine-6.0.4/dlls/winmm/winmm.spec Due to dlltool using names like winmm_dll_t.s and winmm_dll_t.o for it's temp file - these are not unique when building libwinmm.delay.a and libwinmm.cross.a in parallel. (This can of course affect any dll wine is building import libs for, winmm is just the one I happaned to get caught on). This is regression newly introduced in binutils 2.38 vs older versions which used getpid() as the basis of their temp name. We just encountered it as part of updating our CI for a winelib application from focal to jammy, but it seems to have been discovered by others already: see https://sourceware.org/bugzilla/show_bug.cgi?id=28885 There is an upstream fix on master (2.39) which is already backported to the binutils-2_38 branch: https://sourceware.org/git/gitweb.cgi?p=binutils- gdb.git;h=99852365513266afdd793289813e8e565186c9e6, so it should just be a matter of cherry-picking. Hopefully the fact it's a regression from impish->jammy and that upstream already backported it to 2.38 might make this a candidate for jammy-updates? To manage notifications about this bug go to: https://bugs.launchpad.net/binutils/+bug/1971901/+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 1982545] Re: FTBFS on riscv64
** Bug watch added: Debian Bug tracker #1015835 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015835 ** Also affects: curl (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015835 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to curl in Ubuntu. https://bugs.launchpad.net/bugs/1982545 Title: FTBFS on riscv64 Status in curl package in Ubuntu: New Status in curl package in Debian: Unknown Bug description: As can be seen here [1], the build on riscv64 fails now that we use gcc12 with the following error: libtool: link: gcc -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Werror-implicit-function-declaration -Wno-system-headers -Wl,-Bsymbolic-functions -Wl,-z -Wl,relro -Wl,-z -Wl,now -o .libs/curl slist_wc.o tool_binmode.o tool_bname.o tool_cb_dbg.o tool_cb_hdr.o tool_cb_prg.o tool_cb_rea.o tool_cb_see.o tool_cb_wrt.o tool_cfgable.o tool_dirhie.o tool_doswin.o tool_easysrc.o tool_filetime.o tool_findfile.o tool_formparse.o tool_getparam.o tool_getpass.o tool_help.o tool_helpers.o tool_hugehelp.o tool_libinfo.o tool_listhelp.o tool_main.o tool_msgs.o tool_operate.o tool_operhlp.o tool_panykey.o tool_paramhlp.o tool_parsecfg.o tool_progress.o tool_strdup.o tool_setopt.o tool_sleep.o tool_urlglob.o tool_util.o tool_vms.o tool_writeout.o tool_writeout_json.o tool_xattr.o ../lib/strtoofft.o ../lib/timediff.o ../lib/nonblock.o ../lib/warnless.o ../lib/curl_ctype.o ../lib/curl_multibyte.o ../lib/version_win32.o ../lib/dynbuf.o ../lib/.libs/libcurl.so -lssl -lcrypto -lz /usr/bin/ld: ../lib/.libs/libcurl.so: undefined reference to `__atomic_exchange_1' collect2: error: ld returned 1 exit status make[4]: *** [Makefile:991: curl] Error 1 There exists a bug report and a fix for that upstream here: https://github.com/curl/curl/pull/9061 I'm currently building a package with this patch here [2]. [1] https://launchpadlibrarian.net/612746451/buildlog_ubuntu-kinetic-riscv64.curl_7.84.0-2_BUILDING.txt.gz [2] https://launchpad.net/~alexghiti/+archive/ubuntu/riscv/+sourcepub/13822857/+listing-archive-extra To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curl/+bug/1982545/+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 1982545] Re: FTBFS on riscv64
The build on riscv64 succeeded, please find attached the corresponding debdiff. ** Attachment added: "debdiff" https://bugs.launchpad.net/ubuntu/+source/curl/+bug/1982545/+attachment/5604725/+files/debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to curl in Ubuntu. https://bugs.launchpad.net/bugs/1982545 Title: FTBFS on riscv64 Status in curl package in Ubuntu: New Bug description: As can be seen here [1], the build on riscv64 fails now that we use gcc12 with the following error: libtool: link: gcc -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Werror-implicit-function-declaration -Wno-system-headers -Wl,-Bsymbolic-functions -Wl,-z -Wl,relro -Wl,-z -Wl,now -o .libs/curl slist_wc.o tool_binmode.o tool_bname.o tool_cb_dbg.o tool_cb_hdr.o tool_cb_prg.o tool_cb_rea.o tool_cb_see.o tool_cb_wrt.o tool_cfgable.o tool_dirhie.o tool_doswin.o tool_easysrc.o tool_filetime.o tool_findfile.o tool_formparse.o tool_getparam.o tool_getpass.o tool_help.o tool_helpers.o tool_hugehelp.o tool_libinfo.o tool_listhelp.o tool_main.o tool_msgs.o tool_operate.o tool_operhlp.o tool_panykey.o tool_paramhlp.o tool_parsecfg.o tool_progress.o tool_strdup.o tool_setopt.o tool_sleep.o tool_urlglob.o tool_util.o tool_vms.o tool_writeout.o tool_writeout_json.o tool_xattr.o ../lib/strtoofft.o ../lib/timediff.o ../lib/nonblock.o ../lib/warnless.o ../lib/curl_ctype.o ../lib/curl_multibyte.o ../lib/version_win32.o ../lib/dynbuf.o ../lib/.libs/libcurl.so -lssl -lcrypto -lz /usr/bin/ld: ../lib/.libs/libcurl.so: undefined reference to `__atomic_exchange_1' collect2: error: ld returned 1 exit status make[4]: *** [Makefile:991: curl] Error 1 There exists a bug report and a fix for that upstream here: https://github.com/curl/curl/pull/9061 I'm currently building a package with this patch here [2]. [1] https://launchpadlibrarian.net/612746451/buildlog_ubuntu-kinetic-riscv64.curl_7.84.0-2_BUILDING.txt.gz [2] https://launchpad.net/~alexghiti/+archive/ubuntu/riscv/+sourcepub/13822857/+listing-archive-extra To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curl/+bug/1982545/+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 1982545] [NEW] FTBFS on riscv64
Public bug reported: As can be seen here [1], the build on riscv64 fails now that we use gcc12 with the following error: libtool: link: gcc -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Werror-implicit-function-declaration -Wno-system-headers -Wl,-Bsymbolic-functions -Wl,-z -Wl,relro -Wl,-z -Wl,now -o .libs/curl slist_wc.o tool_binmode.o tool_bname.o tool_cb_dbg.o tool_cb_hdr.o tool_cb_prg.o tool_cb_rea.o tool_cb_see.o tool_cb_wrt.o tool_cfgable.o tool_dirhie.o tool_doswin.o tool_easysrc.o tool_filetime.o tool_findfile.o tool_formparse.o tool_getparam.o tool_getpass.o tool_help.o tool_helpers.o tool_hugehelp.o tool_libinfo.o tool_listhelp.o tool_main.o tool_msgs.o tool_operate.o tool_operhlp.o tool_panykey.o tool_paramhlp.o tool_parsecfg.o tool_progress.o tool_strdup.o tool_setopt.o tool_sleep.o tool_urlglob.o tool_util.o tool_vms.o tool_writeout.o tool_writeout_json.o tool_xattr.o ../lib/strtoofft.o ../lib/timediff.o ../lib/nonblock.o ../lib/warnless.o ../lib/curl_ctype.o ../lib/curl_multibyte.o ../lib/version_win32.o ../lib/dynbuf.o ../lib/.libs/libcurl.so -lssl -lcrypto -lz /usr/bin/ld: ../lib/.libs/libcurl.so: undefined reference to `__atomic_exchange_1' collect2: error: ld returned 1 exit status make[4]: *** [Makefile:991: curl] Error 1 There exists a bug report and a fix for that upstream here: https://github.com/curl/curl/pull/9061 I'm currently building a package with this patch here [2]. [1] https://launchpadlibrarian.net/612746451/buildlog_ubuntu-kinetic-riscv64.curl_7.84.0-2_BUILDING.txt.gz [2] https://launchpad.net/~alexghiti/+archive/ubuntu/riscv/+sourcepub/13822857/+listing-archive-extra ** Affects: curl (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to curl in Ubuntu. https://bugs.launchpad.net/bugs/1982545 Title: FTBFS on riscv64 Status in curl package in Ubuntu: New Bug description: As can be seen here [1], the build on riscv64 fails now that we use gcc12 with the following error: libtool: link: gcc -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Werror-implicit-function-declaration -Wno-system-headers -Wl,-Bsymbolic-functions -Wl,-z -Wl,relro -Wl,-z -Wl,now -o .libs/curl slist_wc.o tool_binmode.o tool_bname.o tool_cb_dbg.o tool_cb_hdr.o tool_cb_prg.o tool_cb_rea.o tool_cb_see.o tool_cb_wrt.o tool_cfgable.o tool_dirhie.o tool_doswin.o tool_easysrc.o tool_filetime.o tool_findfile.o tool_formparse.o tool_getparam.o tool_getpass.o tool_help.o tool_helpers.o tool_hugehelp.o tool_libinfo.o tool_listhelp.o tool_main.o tool_msgs.o tool_operate.o tool_operhlp.o tool_panykey.o tool_paramhlp.o tool_parsecfg.o tool_progress.o tool_strdup.o tool_setopt.o tool_sleep.o tool_urlglob.o tool_util.o tool_vms.o tool_writeout.o tool_writeout_json.o tool_xattr.o ../lib/strtoofft.o ../lib/timediff.o ../lib/nonblock.o ../lib/warnless.o ../lib/curl_ctype.o ../lib/curl_multibyte.o ../lib/version_win32.o ../lib/dynbuf.o ../lib/.libs/libcurl.so -lssl -lcrypto -lz /usr/bin/ld: ../lib/.libs/libcurl.so: undefined reference to `__atomic_exchange_1' collect2: error: ld returned 1 exit status make[4]: *** [Makefile:991: curl] Error 1 There exists a bug report and a fix for that upstream here: https://github.com/curl/curl/pull/9061 I'm currently building a package with this patch here [2]. [1] https://launchpadlibrarian.net/612746451/buildlog_ubuntu-kinetic-riscv64.curl_7.84.0-2_BUILDING.txt.gz [2] https://launchpad.net/~alexghiti/+archive/ubuntu/riscv/+sourcepub/13822857/+listing-archive-extra To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curl/+bug/1982545/+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 1973607] Re: Please merge logrotate 3.19.0-2 (main) from Debian unstable (main)
** Changed in: logrotate (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to logrotate in Ubuntu. https://bugs.launchpad.net/bugs/1973607 Title: Please merge logrotate 3.19.0-2 (main) from Debian unstable (main) Status in logrotate package in Ubuntu: Invalid Bug description: Please merge logrotate 3.19.0-2 (main) from Debian unstable (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/logrotate/+bug/1973607/+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 1975673] Re: libgpg-error/1.45-2 fails autopkgtest on i386
I think there's another problem: it fails to install gcc-mingw-w64-i686 because autopkgtest tries to install gcc-mingw-w64-i686:i386 which does not exist since it only exists as gcc-mingw-w64-i686:all. I added :all to the test dependency, and then it works, the test passes correctly on i386 \o/ But I'll come up with the proper patch in autopkgtest: it should try :$arch first and then :all in case it does not work. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libgpg-error in Ubuntu. https://bugs.launchpad.net/bugs/1975673 Title: libgpg-error/1.45-2 fails autopkgtest on i386 Status in libgpg-error package in Ubuntu: New Bug description: The failure was introduced by this change in Debian: https://salsa.debian.org/debian/libgpg-error/-/commit/0c11fe4ae16c2800e13758ff1ee64c561354e628 It started to fail for i386 on autopkgtest.u.c: https://autopkgtest.ubuntu.com/packages/libgpg-error/kinetic/i386 https://autopkgtest.ubuntu.com/results/autopkgtest-kinetic/kinetic/i386/libg/libgpg-error/20220523_114919_e3142@/log.gz The relevant log is this: ``` The following packages have unmet dependencies: builddeps:/tmp/autopkgtest.VMjBik/1-autopkgtest-satdep.dsc:i386 : Depends: gcc-mingw-w64-x86-64:i386 but it is not installable E: Unable to correct problems, you have held broken packages. win64 FAIL badpkg [...] autopkgtest [11:49:03]: summary win32 SKIP Test lists explicitly supported architectures, but the current architecture amd64 isn't listed. win64 FAIL badpkg blame: libgpg-error badpkg: Test dependencies are unsatisfiable. A common reason is that your testbed is out of date with respect to the archive, and you need to use a current testbed or run apt-get update or use -U. build PASS ``` As can be seen, the i386/win32 test is skipped while amd64/win64 is executed and fails with "badpkg" error due to not being able to install "gcc-mingw-w64-x86-64:i386". = Even if that can be fixed (https://code.launchpad.net/~ubuntu-release/autopkgtest/+git/development/+merge/423176), the "win64" test is skipped now and "win32" executed, "win32" fails with a "badpkg" error, which probably needs solving in the archive. $ PYTHONPATH=lib/ runner/autopkgtest libgpg-error --apt-pocket=proposed=src:libgpg-error -a i386 -U -- qemu /data/autopkgtest-kinetic-amd64.img [...] win64 SKIP Test lists explicitly supported architectures, but the current architecture i386 isn't listed. [...] The following packages have unmet dependencies: builddeps:/tmp/autopkgtest.8Maso6/1-autopkgtest-satdep.dsc:i386 : Depends: gcc-mingw-w64-i686:i386 but it is not installable Depends: wine32:i386 but it is not going to be installed E: Unable to correct problems, you have held broken packages. win32 FAIL badpkg blame: libgpg-error badpkg: Test dependencies are unsatisfiable. A common reason is that your testbed is out of date with respect to the archive, and you need to use a current testbed or run apt-get update or use -U. Full log: https://paste.ubuntu.com/p/JYHrJpMGbn/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libgpg-error/+bug/1975673/+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 1973607] Re: Please merge logrotate 3.19.0-2 (main) from Debian unstable (main)
The package successfully built in my PPA [1]. Note that I forgot to replace the changelog signoff with mine, please use the following: -- Alexandre Ghiti Mon, 28 Mar 2022 18:31:38 + [1] https://launchpad.net/~alexghiti/+archive/ubuntu/riscv/+sourcepub/13619002/+listing- archive-extra -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to logrotate in Ubuntu. https://bugs.launchpad.net/bugs/1973607 Title: Please merge logrotate 3.19.0-2 (main) from Debian unstable (main) Status in logrotate package in Ubuntu: New Bug description: Please merge logrotate 3.19.0-2 (main) from Debian unstable (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/logrotate/+bug/1973607/+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 1973607] Re: Please merge logrotate 3.19.0-2 (main) from Debian unstable (main)
Please find attached the debdiff between debian package and the ubuntu one. ** Patch added: "debdiff_debian_ubuntu.debdiff" https://bugs.launchpad.net/ubuntu/+source/logrotate/+bug/1973607/+attachment/5590044/+files/debdiff_debian_ubuntu.debdiff ** Tags added: fr-2388 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to logrotate in Ubuntu. https://bugs.launchpad.net/bugs/1973607 Title: Please merge logrotate 3.19.0-2 (main) from Debian unstable (main) Status in logrotate package in Ubuntu: New Bug description: Please merge logrotate 3.19.0-2 (main) from Debian unstable (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/logrotate/+bug/1973607/+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 1973607] Re: Please merge logrotate 3.19.0-2 (main) from Debian unstable (main)
Please find attached the debdiff between old ubuntu version and the new one. ** Patch added: "debdiff_oldubuntu_newubuntu.debdiff" https://bugs.launchpad.net/ubuntu/+source/logrotate/+bug/1973607/+attachment/5590043/+files/debdiff_oldubuntu_newubuntu.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to logrotate in Ubuntu. https://bugs.launchpad.net/bugs/1973607 Title: Please merge logrotate 3.19.0-2 (main) from Debian unstable (main) Status in logrotate package in Ubuntu: New Bug description: Please merge logrotate 3.19.0-2 (main) from Debian unstable (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/logrotate/+bug/1973607/+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 1973607] [NEW] Please merge logrotate 3.19.0-2 (main) from Debian unstable (main)
Public bug reported: Please merge logrotate 3.19.0-2 (main) from Debian unstable (main) ** Affects: logrotate (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to logrotate in Ubuntu. https://bugs.launchpad.net/bugs/1973607 Title: Please merge logrotate 3.19.0-2 (main) from Debian unstable (main) Status in logrotate package in Ubuntu: New Bug description: Please merge logrotate 3.19.0-2 (main) from Debian unstable (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/logrotate/+bug/1973607/+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 1961425] Re: 22.04: FTBFS due to test failure
Just noticed that version 0.8.0-2ubuntu2 ( https://launchpad.net/ubuntu/+source/capnproto/0.8.0-2ubuntu2 ) landed at the start of the month. This version has a patch that fixes the string issue; renameat2 issue remains, but it won't trigger unless building (and running the unit tests) from a ZFS volume. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to capnproto in Ubuntu. https://bugs.launchpad.net/bugs/1961425 Title: 22.04: FTBFS due to test failure Status in The Ubuntu-power-systems project: New Status in capnproto package in Ubuntu: Confirmed Bug description: Hi, capnproto 0.8.0-2ubuntu1 fails on ppc64el : https://launchpad.net/ubuntu/+source/capnproto/0.8.0-2ubuntu1/+build/23090234/+files/buildlog_ubuntu-jammy-ppc64el.capnproto_0.8.0-2ubuntu1_BUILDING.txt.gz Lowering optimization (O3->O2) level makes the failing test pass, for instance adding export DEB_CXXFLAGS_MAINT_APPEND=-O1 export DEB_CXXFLAGS_MAINT_STRIP=-O3 in debian/rules. For the time being that can be the way to go as 0.9.1-2 from Debian Experimental builds fine on Jammy by default with O3. F. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1961425/+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 1961425] Re: 22.04: FTBFS due to test failure
I was looking into this for a few days and failure:
[ TEST ] kj/string-test.c++:31: legacy test: String/Str
kj/string-test.c++:38: failed: expected ("-128 -32768 -2147483648
-9223372036854775808") == (str((signed char)-128, ' ', (signed short)-32768, '
', ((int)-2147483647) - 1, ' ', ((long long)-9223372036854775807ll) - 1)); -128
-32768 -2147483648 -9223372036854775808; str((signed char)-128, ' ', (signed
short)-32768, ' ', ((int)-2147483647) - 1, ' ', ((long
long)-9223372036854775807ll) - 1) = -128 -32768 -214748364( -9223372036854775808
stack: c27f3c60b7b c27f38280d7 764d217568b3 764d216c058f 764d217549e3
764d2175661f 764d216ef643 764d21701a83 764d216c058f 764d216f568b 764d2175314f
764d211017a3 764d21101987
[ FAIL ] kj/string-test.c++:31: legacy test: String/Str (85 μs)
... is caused by the code depending on undefined behavior, which happens
to pass on x64 and arm64 but fails on ppc64el. Reducing optimization
level works but I won't count on it to be stable. But since the problem
is already fixed in 0.9.0 (currently on experimental), we can get the
fix when that version is merged.
There are also a different FTBFS caused by a few test cases that fail
when the unit tests are ran from a ZFS volume. I only hit it after
building on a container backed by ZFS storage, btw. It's caused by a
capnproto component using its own wrapper for system call renameat2()
without implementing the fallback for it on unsupported filesystems (as
renameat2 requires collaboration from the FS layer). It is also fixed in
version 0.9.0.
If 0.9.0 does not arrive in time for the merge freeze, I tentatively
backported these two fixes to 0.8.0. A test branch in
https://code.launchpad.net/~aittner/ubuntu/+source/capnproto/+git/capnproto/+ref/backport-
upstream-fixes
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to capnproto in Ubuntu.
https://bugs.launchpad.net/bugs/1961425
Title:
22.04: FTBFS due to test failure
Status in The Ubuntu-power-systems project:
New
Status in capnproto package in Ubuntu:
Confirmed
Bug description:
Hi,
capnproto 0.8.0-2ubuntu1 fails on ppc64el :
https://launchpad.net/ubuntu/+source/capnproto/0.8.0-2ubuntu1/+build/23090234/+files/buildlog_ubuntu-jammy-ppc64el.capnproto_0.8.0-2ubuntu1_BUILDING.txt.gz
Lowering optimization (O3->O2) level makes the failing test pass, for
instance adding
export DEB_CXXFLAGS_MAINT_APPEND=-O1
export DEB_CXXFLAGS_MAINT_STRIP=-O3
in debian/rules.
For the time being that can be the way to go as 0.9.1-2 from Debian
Experimental
builds fine on Jammy by default with O3.
F.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1961425/+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 1960608] Re: python-pip >= 21.3.1+dfsg-3 fails pip3-root.sh autopkgtest with python3.10
I'm not sure I understand: do I need to enable the sysconfig patch for python3.10 in addition to your fix? Thanks -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dh-python in Ubuntu. https://bugs.launchpad.net/bugs/1960608 Title: python-pip >= 21.3.1+dfsg-3 fails pip3-root.sh autopkgtest with python3.10 Status in dh-python package in Ubuntu: Fix Released Status in python-pip package in Ubuntu: New Status in python3.10 package in Ubuntu: Confirmed Bug description: pip3-root.sh expects world package to be installed in /usr/local/lib/python3.*/dist-packages whereas it is actually installed into /usr/lib/python3.10/site-packages/. It even fails to uninstall the package right after installing it: ubuntu@autopkgtest:~$ sudo python3 -m pip install world Collecting world Using cached world-4.1.1-py3-none-any.whl Collecting atpublic Using cached atpublic-3.0.1-py3-none-any.whl (4.8 kB) Installing collected packages: atpublic, world Successfully installed atpublic-3.0.1 world-4.1.1 WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv ubuntu@autopkgtest:~$ sudo python3 -m pip uninstall world WARNING: Skipping world as it is not installed. WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dh-python/+bug/1960608/+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 1958502] Re: Please merge newt 0.52.21-5 (main) from Debian unstable (main)
New diff that contains the LP bug number in changelog. ** Patch added: "debdiff_oldubuntu_ubuntu.diff" https://bugs.launchpad.net/ubuntu/+source/newt/+bug/1958502/+attachment/5557898/+files/debdiff_oldubuntu_ubuntu.diff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to newt in Ubuntu. https://bugs.launchpad.net/bugs/1958502 Title: Please merge newt 0.52.21-5 (main) from Debian unstable (main) Status in newt package in Ubuntu: New Bug description: Please merge newt 0.52.21-5 (main) from Debian unstable (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/newt/+bug/1958502/+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 1958502] Re: Please merge newt 0.52.21-5 (main) from Debian unstable (main)
New diff that contains the LP bug number in the changelog. ** Patch added: "debdiff_debian_ubuntu.diff" https://bugs.launchpad.net/ubuntu/+source/newt/+bug/1958502/+attachment/5557899/+files/debdiff_debian_ubuntu.diff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to newt in Ubuntu. https://bugs.launchpad.net/bugs/1958502 Title: Please merge newt 0.52.21-5 (main) from Debian unstable (main) Status in newt package in Ubuntu: New Bug description: Please merge newt 0.52.21-5 (main) from Debian unstable (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/newt/+bug/1958502/+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 1958887] Re: Please merge logrotate 3.19.0-1 (main) from Debian unstable (main)
This package successfully built in my PPA [1] and passed autopkgtests in a jammy VM. [1] https://launchpad.net/~alexghiti/+archive/ubuntu/riscv/+packages -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to logrotate in Ubuntu. https://bugs.launchpad.net/bugs/1958887 Title: Please merge logrotate 3.19.0-1 (main) from Debian unstable (main) Status in logrotate package in Ubuntu: New Bug description: Please merge logrotate 3.19.0-1 (main) from Debian unstable (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/logrotate/+bug/1958887/+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 1958887] Re: Please merge logrotate 3.19.0-1 (main) from Debian unstable (main)
** Patch added: "debdiff_oldubuntu_newubuntu.patch" https://bugs.launchpad.net/ubuntu/+source/logrotate/+bug/1958887/+attachment/5557094/+files/debdiff_oldubuntu_newubuntu.patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to logrotate in Ubuntu. https://bugs.launchpad.net/bugs/1958887 Title: Please merge logrotate 3.19.0-1 (main) from Debian unstable (main) Status in logrotate package in Ubuntu: New Bug description: Please merge logrotate 3.19.0-1 (main) from Debian unstable (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/logrotate/+bug/1958887/+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 1958887] Re: Please merge logrotate 3.19.0-1 (main) from Debian unstable (main)
** Patch added: "debdiff_debian_ubuntu.patch" https://bugs.launchpad.net/ubuntu/+source/logrotate/+bug/1958887/+attachment/5557095/+files/debdiff_debian_ubuntu.patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to logrotate in Ubuntu. https://bugs.launchpad.net/bugs/1958887 Title: Please merge logrotate 3.19.0-1 (main) from Debian unstable (main) Status in logrotate package in Ubuntu: New Bug description: Please merge logrotate 3.19.0-1 (main) from Debian unstable (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/logrotate/+bug/1958887/+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 1958887] [NEW] Please merge logrotate 3.19.0-1 (main) from Debian unstable (main)
Public bug reported: Please merge logrotate 3.19.0-1 (main) from Debian unstable (main) ** Affects: logrotate (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to logrotate in Ubuntu. https://bugs.launchpad.net/bugs/1958887 Title: Please merge logrotate 3.19.0-1 (main) from Debian unstable (main) Status in logrotate package in Ubuntu: New Bug description: Please merge logrotate 3.19.0-1 (main) from Debian unstable (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/logrotate/+bug/1958887/+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 1958502] Re: Please merge newt 0.52.21-5 (main) from Debian unstable (main)
** Patch added: "debdiff_oldubuntu_ubuntu.diff" https://bugs.launchpad.net/ubuntu/+source/newt/+bug/1958502/+attachment/790/+files/debdiff_oldubuntu_ubuntu.diff ** Changed in: newt (Ubuntu) Assignee: Alexandre Ghiti (alexghiti) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to newt in Ubuntu. https://bugs.launchpad.net/bugs/1958502 Title: Please merge newt 0.52.21-5 (main) from Debian unstable (main) Status in newt package in Ubuntu: New Bug description: Please merge newt 0.52.21-5 (main) from Debian unstable (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/newt/+bug/1958502/+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 1958502] Re: Please merge newt 0.52.21-5 (main) from Debian unstable (main)
The new package built successfully in my ppa: https://launchpad.net/~alexghiti/+archive/ubuntu/riscv/+sourcepub/13213239/+listing- archive-extra -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to newt in Ubuntu. https://bugs.launchpad.net/bugs/1958502 Title: Please merge newt 0.52.21-5 (main) from Debian unstable (main) Status in newt package in Ubuntu: New Bug description: Please merge newt 0.52.21-5 (main) from Debian unstable (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/newt/+bug/1958502/+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 1958502] Re: Please merge newt 0.52.21-5 (main) from Debian unstable (main)
** Patch added: "debdiff_debian_ubuntu.diff" https://bugs.launchpad.net/ubuntu/+source/newt/+bug/1958502/+attachment/789/+files/debdiff_debian_ubuntu.diff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to newt in Ubuntu. https://bugs.launchpad.net/bugs/1958502 Title: Please merge newt 0.52.21-5 (main) from Debian unstable (main) Status in newt package in Ubuntu: New Bug description: Please merge newt 0.52.21-5 (main) from Debian unstable (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/newt/+bug/1958502/+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 1958502] [NEW] Please merge newt 0.52.21-5 (main) from Debian unstable (main)
Public bug reported: Please merge newt 0.52.21-5 (main) from Debian unstable (main) ** Affects: newt (Ubuntu) Importance: Undecided Assignee: Alexandre Ghiti (alexghiti) Status: New ** Changed in: newt (Ubuntu) Assignee: (unassigned) => Alexandre Ghiti (alexghiti) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to newt in Ubuntu. https://bugs.launchpad.net/bugs/1958502 Title: Please merge newt 0.52.21-5 (main) from Debian unstable (main) Status in newt package in Ubuntu: New Bug description: Please merge newt 0.52.21-5 (main) from Debian unstable (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/newt/+bug/1958502/+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 1952602] Re: Please merge logrotate 3.18.1-2 (main) from Debian unstable (main)
** Patch added: "debdiff_debian_ubuntu1.patch" https://bugs.launchpad.net/ubuntu/+source/logrotate/+bug/1952602/+attachment/5544060/+files/debdiff_debian_ubuntu1.patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to logrotate in Ubuntu. https://bugs.launchpad.net/bugs/1952602 Title: Please merge logrotate 3.18.1-2 (main) from Debian unstable (main) Status in logrotate package in Ubuntu: New Bug description: * Merge from Debian unstable. Remaining changes: - debian/control: Drop mailx to Suggests for Ubuntu; it's only used on request, and we don't configure an MTA by default. - debian/patches/ubuntu/logrotate.conf-use-group-adm.patch: Use group 'adm' by default when rotating logs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/logrotate/+bug/1952602/+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 1952602] Re: Please merge logrotate 3.18.1-2 (main) from Debian unstable (main)
** Patch added: "debdiff_0ubuntu2_1ubuntu1.patch" https://bugs.launchpad.net/ubuntu/+source/logrotate/+bug/1952602/+attachment/5544061/+files/debdiff_0ubuntu2_1ubuntu1.patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to logrotate in Ubuntu. https://bugs.launchpad.net/bugs/1952602 Title: Please merge logrotate 3.18.1-2 (main) from Debian unstable (main) Status in logrotate package in Ubuntu: New Bug description: * Merge from Debian unstable. Remaining changes: - debian/control: Drop mailx to Suggests for Ubuntu; it's only used on request, and we don't configure an MTA by default. - debian/patches/ubuntu/logrotate.conf-use-group-adm.patch: Use group 'adm' by default when rotating logs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/logrotate/+bug/1952602/+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 1952602] [NEW] Please merge logrotate 3.18.1-2 (main) from Debian unstable (main)
Public bug reported: * Merge from Debian unstable. Remaining changes: - debian/control: Drop mailx to Suggests for Ubuntu; it's only used on request, and we don't configure an MTA by default. - debian/patches/ubuntu/logrotate.conf-use-group-adm.patch: Use group 'adm' by default when rotating logs. ** Affects: logrotate (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to logrotate in Ubuntu. https://bugs.launchpad.net/bugs/1952602 Title: Please merge logrotate 3.18.1-2 (main) from Debian unstable (main) Status in logrotate package in Ubuntu: New Bug description: * Merge from Debian unstable. Remaining changes: - debian/control: Drop mailx to Suggests for Ubuntu; it's only used on request, and we don't configure an MTA by default. - debian/patches/ubuntu/logrotate.conf-use-group-adm.patch: Use group 'adm' by default when rotating logs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/logrotate/+bug/1952602/+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 1952591] Re: Please merge kmod 29-1 (main) from Debian unstable (main)
Note that 28-ubuntu5 is only a no-change rebuild. ** Patch added: "debdiff_28ubuntu4_29ubuntu1.patch" https://bugs.launchpad.net/ubuntu/+source/kmod/+bug/1952591/+attachment/5544058/+files/debdiff_28ubuntu4_29ubuntu1.patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to kmod in Ubuntu. https://bugs.launchpad.net/bugs/1952591 Title: Please merge kmod 29-1 (main) from Debian unstable (main) Status in kmod package in Ubuntu: New Bug description: * Merge from Debian unstable. Remaining changes: - Enable testsuite during build. - Build with zstd compression enabled. - Install ubuntu-specific depmod.d and modprobe.d contents. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kmod/+bug/1952591/+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 1952591] Re: Please merge kmod 29-1 (main) from Debian unstable (main)
** Patch added: "debdiff_debian_ubuntu1.patch" https://bugs.launchpad.net/ubuntu/+source/kmod/+bug/1952591/+attachment/5544057/+files/debdiff_debian_ubuntu1.patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to kmod in Ubuntu. https://bugs.launchpad.net/bugs/1952591 Title: Please merge kmod 29-1 (main) from Debian unstable (main) Status in kmod package in Ubuntu: New Bug description: * Merge from Debian unstable. Remaining changes: - Enable testsuite during build. - Build with zstd compression enabled. - Install ubuntu-specific depmod.d and modprobe.d contents. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kmod/+bug/1952591/+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 1952591] [NEW] Please merge kmod 29-1 (main) from Debian unstable (main)
Public bug reported: * Merge from Debian unstable. Remaining changes: - Enable testsuite during build. - Build with zstd compression enabled. - Install ubuntu-specific depmod.d and modprobe.d contents. ** Affects: kmod (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to kmod in Ubuntu. https://bugs.launchpad.net/bugs/1952591 Title: Please merge kmod 29-1 (main) from Debian unstable (main) Status in kmod package in Ubuntu: New Bug description: * Merge from Debian unstable. Remaining changes: - Enable testsuite during build. - Build with zstd compression enabled. - Install ubuntu-specific depmod.d and modprobe.d contents. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kmod/+bug/1952591/+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 1939413] Re: /usr/lib/aarch64-linux-gnu/libprotobuf.a’ generated with LTO version 9.2 instead of the expected 11.0
I was running a few test builds with different combinations of gcc, elfutils and protobuf and trying to make the build fail... but it continues working despite the older elfutils compiled with the newer gcc. Last check was with protobuf-3.12.4-1ubuntu3 (from jammy, 4 days ago) in an impish 0.185-1build1 and then downgraded to a 0.183-8 built with 11.2.0-7ubuntu2 (from impish), but it still does not trigger the issue despite the mismatches. I still could not find the reason. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to protobuf in Ubuntu. https://bugs.launchpad.net/bugs/1939413 Title: /usr/lib/aarch64-linux-gnu/libprotobuf.a’ generated with LTO version 9.2 instead of the expected 11.0 Status in elfutils package in Ubuntu: New Status in mozc package in Ubuntu: Invalid Status in protobuf package in Ubuntu: Triaged Bug description: When trying to build package mozc for arm64 the following error popped up: lto1: fatal error: bytecode stream in file ‘/usr/lib/aarch64-linux- gnu/libprotobuf.a’ generated with LTO version 9.2 instead of the expected 11.0 Why does the library contain LTO information at all? Best regards Heinrich To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/elfutils/+bug/1939413/+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 1944741] Re: HiFive Unmatched partitions are named "Unleashed"
I tested the new packages [1] on a fresh RISC-V image following the test plan in the bug description and validated that the bug was fixed in Impish. [1] https://launchpad.net/ubuntu/+source/util-linux/2.36.1-8ubuntu2/+build/22279841/+files/libfdisk-dev_2.36.1-8ubuntu2_riscv64.deb https://launchpad.net/ubuntu/+source/util-linux/2.36.1-8ubuntu2/+build/22279841/+files/libfdisk1_2.36.1-8ubuntu2_riscv64.deb https://launchpad.net/ubuntu/+source/util-linux/2.36.1-8ubuntu2/+build/22279841/+files/fdisk_2.36.1-8ubuntu2_riscv64.deb ** Tags added: verification-done-impish -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1944741 Title: HiFive Unmatched partitions are named "Unleashed" Status in util-linux package in Ubuntu: New Status in util-linux source package in Impish: Fix Committed Status in util-linux source package in Jammy: New Status in util-linux package in Debian: Confirmed Bug description: [Impact] Both HiFive Unleashed and HiFive Unmatched bootloaders seek for the same UUIDs to load the next stage bootloader: the current name makes partitions on Unmatched board appear as 'Unleashed'. This issue gives the feeling that the Ubuntu RISC-V images made specifically for those 2 boards were assembled in a rushed manner. The attached patch fixes this by removing the 'Unleashed' part of the current name so that it fits both, it was build againt all architectures here: https://launchpad.net/~alexghiti/+archive/ubuntu/riscv/+sourcepub/12783067/+listing-archive-extra [Test Plan] 1. Download the SiFive Unmatched image here: https://cdimage.ubuntu.com/ubuntu-server/daily-preinstalled/pending/impish-preinstalled-server-riscv64+unmatched.img.xz 2. Follow instructions here to launch a riscv64 VM: https://wiki.ubuntu.com/RISC-V 3. Execute the following command: ubuntu@ubuntu:~$ sudo fdisk -l Disk /dev/vda: 40 GiB, 42949672960 bytes, 83886080 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: gpt Disk identifier: 0F66C0C3-A5E4-439B-907E-ABAD106FE4A7 Device Start End Sectors Size Type /dev/vda1 235554 83886046 83650493 39.9G Linux filesystem /dev/vda12 227362 235553 81924M Linux filesystem /dev/vda13 34 2081 20481M HiFive Unleashed FSBL /dev/vda14 208210273 81924M HiFive Unleashed BBL /dev/vda15 10274 227361 217088 106M EFI System Partition table entries are not in disk order. 4. Download and install the new packages that contain the fix here: https://launchpad.net/~alexghiti/+archive/ubuntu/riscv/+files/libfdisk1_2.36.1-8ubuntu4_riscv64.deb https://launchpad.net/~alexghiti/+archive/ubuntu/riscv/+files/libfdisk-dev_2.36.1-8ubuntu4_riscv64.deb https://launchpad.net/~alexghiti/+archive/ubuntu/riscv/+files/fdisk_2.36.1-8ubuntu4_riscv64.deb 5. Re-execute the same command as above: ubuntu@ubuntu:~$ sudo fdisk -l Disk /dev/vda: 40 GiB, 42949672960 bytes, 83886080 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: gpt
[Touch-packages] [Bug 1944741] Re: HiFive Unmatched partitions are named "Unleashed"
** Description changed: - Both HiFive Unleashed and HiFive Unmatched bootloaders seek for the same - UUIDs to load the next stage bootloader: the current name makes partitions - on Unmatched board appear as 'Unleashed'. - - Fix that by removing the 'Unleashed' part of the current name so that it - fits both. - - The attached debdiff contains the patch that was merged upstream - (https://github.com/karelzak/util- - linux/commit/10fd91d389497d8be435cc66abbdeb2eb6ea2f07). + [Impact] + + Both HiFive Unleashed and HiFive Unmatched bootloaders seek for the same + UUIDs to load the next stage bootloader: the current name makes partitions + on Unmatched board appear as 'Unleashed'. + + This issue gives the feeling that the Ubuntu RISC-V images made specifically + for those 2 boards were assembled in a rushed manner. + + The attached patch fixes this by removing the 'Unleashed' part of the current + name so that it fits both, it was build againt all architectures here: + https://launchpad.net/~alexghiti/+archive/ubuntu/riscv/+sourcepub/12783067/+listing-archive-extra + + [Test Plan] + + 1. Download the SiFive Unmatched image here: https://cdimage.ubuntu.com/ubuntu-server/daily-preinstalled/pending/impish-preinstalled-server-riscv64+unmatched.img.xz + 2. Follow instructions here to launch a riscv64 VM: https://wiki.ubuntu.com/RISC-V + 3. Execute the following command: + ubuntu@ubuntu:~$ sudo fdisk -l + Disk /dev/vda: 40 GiB, 42949672960 bytes, 83886080 sectors + Units: sectors of 1 * 512 = 512 bytes + Sector size (logical/physical): 512 bytes / 512 bytes + I/O size (minimum/optimal): 512 bytes / 512 bytes + Disklabel type: gpt + Disk identifier: 0F66C0C3-A5E4-439B-907E-ABAD106FE4A7 + + Device Start End Sectors Size Type + /dev/vda1 235554 83886046 83650493 39.9G Linux filesystem + /dev/vda12 227362 235553 81924M Linux filesystem + /dev/vda13 34 2081 20481M HiFive Unleashed FSBL + /dev/vda14 208210273 81924M HiFive Unleashed BBL + /dev/vda15 10274 227361 217088 106M EFI System + + Partition table entries are not in disk order. + 4. Download and install the new packages that contain the fix here: + https://launchpad.net/~alexghiti/+archive/ubuntu/riscv/+files/libfdisk1_2.36.1-8ubuntu4_riscv64.deb + https://launchpad.net/~alexghiti/+archive/ubuntu/riscv/+files/libfdisk-dev_2.36.1-8ubuntu4_riscv64.deb + https://launchpad.net/~alexghiti/+archive/ubuntu/riscv/+files/fdisk_2.36.1-8ubuntu4_riscv64.deb + 5. Re-execute the same command as above: + ubuntu@ubuntu:~$ sudo fdisk -l + Disk /dev/vda: 40 GiB, 42949672960 bytes, 83886080 sectors + Units: sectors of 1 * 512 = 512 bytes + Sector size (logical/physical): 512 bytes / 512 bytes + I/O size (minimum/optimal): 512 bytes / 512 bytes + Disklabel type: gpt + Disk identifier: 0F66C0C3-A5E4-439B-907E-ABAD106FE4A7 + + Device Start End Sectors Size Type + /dev/vda1 235554 83886046 83650493 39.9G Linux filesystem + /dev/vda12 227362 235553 81924M Linux filesystem + /dev/vda13 34 2081 20481M HiFive FSBL +
[Touch-packages] [Bug 1944741] Re: HiFive Unmatched partitions are named "Unleashed"
I actually missed the translation files that contain the translation of the partition names I changed. Attached the corresponding debdiff that contains all the changes. ** Patch added: "util_linux_debdiff.patch" https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1944741/+attachment/5532128/+files/util_linux_debdiff.patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1944741 Title: HiFive Unmatched partitions are named "Unleashed" Status in util-linux package in Ubuntu: New Status in util-linux source package in Impish: New Status in util-linux package in Debian: Confirmed Bug description: Both HiFive Unleashed and HiFive Unmatched bootloaders seek for the same UUIDs to load the next stage bootloader: the current name makes partitions on Unmatched board appear as 'Unleashed'. Fix that by removing the 'Unleashed' part of the current name so that it fits both. The attached debdiff contains the patch that was merged upstream (https://github.com/karelzak/util- linux/commit/10fd91d389497d8be435cc66abbdeb2eb6ea2f07). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1944741/+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 1944741] Re: HiFive Unmatched partitions are named "Unleashed"
** Tags added: fr-1786 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1944741 Title: HiFive Unmatched partitions are named "Unleashed" Status in util-linux package in Ubuntu: New Status in util-linux package in Debian: Confirmed Bug description: Both HiFive Unleashed and HiFive Unmatched bootloaders seek for the same UUIDs to load the next stage bootloader: the current name makes partitions on Unmatched board appear as 'Unleashed'. Fix that by removing the 'Unleashed' part of the current name so that it fits both. The attached debdiff contains the patch that was merged upstream (https://github.com/karelzak/util- linux/commit/10fd91d389497d8be435cc66abbdeb2eb6ea2f07). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1944741/+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 1944741] Re: HiFive Unmatched partitions are named "Unleashed"
** Patch added: "util_linux_debdiff.patch" https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1944741/+attachment/5527466/+files/util_linux_debdiff.patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1944741 Title: HiFive Unmatched partitions are named "Unleashed" Status in util-linux package in Ubuntu: New Status in util-linux package in Debian: New Bug description: Both HiFive Unleashed and HiFive Unmatched bootloaders seek for the same UUIDs to load the next stage bootloader: the current name makes partitions on Unmatched board appear as 'Unleashed'. Fix that by removing the 'Unleashed' part of the current name so that it fits both. The attached debdiff contains the patch that was merged upstream (https://github.com/karelzak/util- linux/commit/10fd91d389497d8be435cc66abbdeb2eb6ea2f07). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1944741/+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 1944741] Re: HiFive Unmatched partitions are named "Unleashed"
** Bug watch added: Debian Bug tracker #994941 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994941 ** Also affects: util-linux (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994941 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1944741 Title: HiFive Unmatched partitions are named "Unleashed" Status in util-linux package in Ubuntu: New Status in util-linux package in Debian: Unknown Bug description: Both HiFive Unleashed and HiFive Unmatched bootloaders seek for the same UUIDs to load the next stage bootloader: the current name makes partitions on Unmatched board appear as 'Unleashed'. Fix that by removing the 'Unleashed' part of the current name so that it fits both. The attached debdiff contains the patch that was merged upstream (https://github.com/karelzak/util- linux/commit/10fd91d389497d8be435cc66abbdeb2eb6ea2f07). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1944741/+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 1944741] Re: HiFive Unmatched partitions are named "Unleashed"
** Patch added: "util_linux_debdiff.patch" https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1944741/+attachment/5527393/+files/util_linux_debdiff.patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1944741 Title: HiFive Unmatched partitions are named "Unleashed" Status in util-linux package in Ubuntu: New Bug description: Both HiFive Unleashed and HiFive Unmatched bootloaders seek for the same UUIDs to load the next stage bootloader: the current name makes partitions on Unmatched board appear as 'Unleashed'. Fix that by removing the 'Unleashed' part of the current name so that it fits both. The attached debdiff contains the patch that was merged upstream (https://github.com/karelzak/util- linux/commit/10fd91d389497d8be435cc66abbdeb2eb6ea2f07). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1944741/+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 1944741] [NEW] HiFive Unmatched partitions are named "Unleashed"
Public bug reported: Both HiFive Unleashed and HiFive Unmatched bootloaders seek for the same UUIDs to load the next stage bootloader: the current name makes partitions on Unmatched board appear as 'Unleashed'. Fix that by removing the 'Unleashed' part of the current name so that it fits both. The attached debdiff contains the patch that was merged upstream (https://github.com/karelzak/util- linux/commit/10fd91d389497d8be435cc66abbdeb2eb6ea2f07). ** Affects: util-linux (Ubuntu) Importance: Undecided Status: New ** Attachment added: "util-linux_2.36.1-8ubuntu2_source.changes" https://bugs.launchpad.net/bugs/1944741/+attachment/5527390/+files/util-linux_2.36.1-8ubuntu2_source.changes -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1944741 Title: HiFive Unmatched partitions are named "Unleashed" Status in util-linux package in Ubuntu: New Bug description: Both HiFive Unleashed and HiFive Unmatched bootloaders seek for the same UUIDs to load the next stage bootloader: the current name makes partitions on Unmatched board appear as 'Unleashed'. Fix that by removing the 'Unleashed' part of the current name so that it fits both. The attached debdiff contains the patch that was merged upstream (https://github.com/karelzak/util- linux/commit/10fd91d389497d8be435cc66abbdeb2eb6ea2f07). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1944741/+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 1942764] Re: Enable riscv64 build of mesa-opencl-icd
** Tags added: fr-1691 -- 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/1942764 Title: Enable riscv64 build of mesa-opencl-icd Status in mesa package in Ubuntu: In Progress Bug description: Ubuntu release: impish Package version: 21.2.1-2ubuntu1 `mesa-opencl-icd` is needed for `libhmsbeagle` to be installable, so is it possible to enable this package as I have done here: https://launchpad.net/~alexghiti/+archive/ubuntu/riscv/+sourcepub/12687486/+listing- archive-extra ? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1942764/+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 1942764] Re: Enable riscv64 build of mesa-opencl-icd
Please find attached the corresponding debdiff. ** Patch added: "mesa_debdiff.patch" https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1942764/+attachment/5523682/+files/mesa_debdiff.patch -- 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/1942764 Title: Enable riscv64 build of mesa-opencl-icd Status in mesa package in Ubuntu: New Bug description: Ubuntu release: impish Package version: 21.2.1-2ubuntu1 `mesa-opencl-icd` is needed for `libhmsbeagle` to be installable, so is it possible to enable this package as I have done here: https://launchpad.net/~alexghiti/+archive/ubuntu/riscv/+sourcepub/12687486/+listing- archive-extra ? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1942764/+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 1942764] Re: Enable riscv64 build of mesa-opencl-icd
To be completely thorough here, `libhmsbeagle` needs either `mesa- opencl-icd` or some package that can provide `opencl-icd`. `pocl-opencl- icd` used to build on riscv64 and then fulfilled this dependency but some recent changes broke this package (currently investigating). So building `mesa-opencl-icd` is not mandatory for `libhmsbeagle` but as it builds fine on riscv64 , it should be enabled. -- 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/1942764 Title: Enable riscv64 build of mesa-opencl-icd Status in mesa package in Ubuntu: New Bug description: Ubuntu release: impish Package version: 21.2.1-2ubuntu1 `mesa-opencl-icd` is needed for `libhmsbeagle` to be installable, so is it possible to enable this package as I have done here: https://launchpad.net/~alexghiti/+archive/ubuntu/riscv/+sourcepub/12687486/+listing- archive-extra ? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1942764/+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 1942764] [NEW] Enable riscv64 build of mesa-opencl-icd
Public bug reported: Ubuntu release: impish Package version: 21.2.1-2ubuntu1 `mesa-opencl-icd` is needed for `libhmsbeagle` to be installable, so is it possible to enable this package as I have done here: https://launchpad.net/~alexghiti/+archive/ubuntu/riscv/+sourcepub/12687486/+listing- archive-extra ? ** Affects: mesa (Ubuntu) Importance: Undecided Status: New -- 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/1942764 Title: Enable riscv64 build of mesa-opencl-icd Status in mesa package in Ubuntu: New Bug description: Ubuntu release: impish Package version: 21.2.1-2ubuntu1 `mesa-opencl-icd` is needed for `libhmsbeagle` to be installable, so is it possible to enable this package as I have done here: https://launchpad.net/~alexghiti/+archive/ubuntu/riscv/+sourcepub/12687486/+listing- archive-extra ? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1942764/+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 1845046] Re: Bluetooth headphones default to low quality headset mode and fail to switch to A2DP when selected
This issue is real pain and persists even with Ubuntu 20.04 and my Bose QuietComfort 35. Selecting High Fidelity Playback (A2DP Sink) does nothing. I managed to do it once but it seems it stuck with low quality now :( -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1845046 Title: Bluetooth headphones default to low quality headset mode and fail to switch to A2DP when selected Status in bluez package in Ubuntu: Fix Released Status in bluez source package in Bionic: Fix Released Status in bluez source package in Eoan: Fix Released Status in bluez source package in Focal: Fix Released Bug description: [Impact] Whenever I turn on my headphones they'll connect to my computer but I'm able to hear the input audio from my microphone and low quality output audio. I have to disconnect the headphones in the bluetooth devices and reconnect for it to fix the problem. [Test Case] 0. Set up your Bluetooth headphones with Ubuntu. 1. Turn off the headphones. 2. Turn on the headphones. 3. In Settings>Sound verify they have reconnected in A2DP mode (stereo, high quality, no microphone support). [Regression Potential] Low. Only the headset code path is affected and the fix has already been released for some time in BlueZ 5.51 onward. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1845046/+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 1873085] [NEW] initramfs keyboard layout back to qwerty after upgrade
Public bug reported: After initial installation of Ubuntu 20.04 beta two days ago, I was able to unlock my disk at boot with an AZERTY keyboard. Since afternoon upgrade, my initramfs is now in QWERTY and so I need to input my password in QWERTY which is inconvenient. This is my APT log from my last upgrade : ``` Start-Date: 2020-04-15 22:51:43 Commandline: apt upgrade Requested-By: erdnaxe (1000) Install: appstream:amd64 (0.12.10-2, automatic) Upgrade: ubuntu-desktop-minimal:amd64 (1.447, 1.448), libdrm-nouveau2:amd64 (2.4.101-1, 2.4.101-2), libdrm-nouveau2:i386 (2.4.101-1, 2.4.101-2), libllvm9:amd64 (1:9.0.1-11ubuntu1, 1:9.0.1-12), libllvm9:i386 (1:9.0.1-11ubuntu1, 1:9.0.1-12), libsystemd0:amd64 (245.4-2ubuntu1, 245.4-4ubuntu1), grub-common:amd64 (2.04-1ubuntu24, 2.04-1ubuntu25), ubuntu-standard:amd64 (1.447, 1.448), ubuntu-desktop:amd64 (1.447, 1.448), python-matplotlib-data:amd64 (3.1.2-1ubuntu3, 3.1.2-1ubuntu4), python-apt-common:amd64 (1.9.10, 2.0.0), grub2-common:amd64 (2.04-1ubuntu24, 2.04-1ubuntu25), udev:amd64 (245.4-2ubuntu1, 245.4-4ubuntu1), python3-matplotlib:amd64 (3.1.2-1ubuntu3, 3.1.2-1ubuntu4), nautilus-extension-gnome-terminal:amd64 (3.35.91-0ubuntu1, 3.36.1.1-1ubuntu1), grub-pc:amd64 (2.04-1ubuntu24, 2.04-1ubuntu25), libudev1:amd64 (245.4-2ubuntu1, 245.4-4ubuntu1), libudev1:i386 (245.4-2ubuntu1, 245.4-4ubuntu1), systemd-timesyncd:amd64 (245.4-2ubuntu1, 245.4-4ubuntu1), grub-pc-bin:amd64 (2.04-1ubuntu24, 2.04-1ubuntu25), ubuntu-minimal:amd64 (1.447, 1.448), libdrm-amdgpu1:amd64 (2.4.101-1, 2.4.101-2), libdrm-amdgpu1:i386 (2.4.101-1, 2.4.101-2), grub-efi-amd64-bin:amd64 (2.04-1ubuntu24, 2.04-1ubuntu25), python-is-python3:amd64 (3.8.2-3, 3.8.2-4), systemd-sysv:amd64 (245.4-2ubuntu1, 245.4-4ubuntu1), gnome-shell-common:amd64 (3.36.1-4ubuntu1, 3.36.1-5ubuntu1), libpam-systemd:amd64 (245.4-2ubuntu1, 245.4-4ubuntu1), libdrm2:amd64 (2.4.101-1, 2.4.101-2), libdrm2:i386 (2.4.101-1, 2.4.101-2), systemd:amd64 (245.4-2ubuntu1, 245.4-4ubuntu1), libsdl2-2.0-0:amd64 (2.0.10+dfsg1-2ubuntu5, 2.0.10+dfsg1-3), libnss-systemd:amd64 (245.4-2ubuntu1, 245.4-4ubuntu1), grub-efi-amd64-signed:amd64 (1.140+2.04-1ubuntu24, 1.141+2.04-1ubuntu25), gnome-terminal-data:amd64 (3.35.91-0ubuntu1, 3.36.1.1-1ubuntu1), unattended-upgrades:amd64 (2.2, 2.3), libdrm-intel1:amd64 (2.4.101-1, 2.4.101-2), libdrm-intel1:i386 (2.4.101-1, 2.4.101-2), gnome-shell:amd64 (3.36.1-4ubuntu1, 3.36.1-5ubuntu1), libdrm-radeon1:amd64 (2.4.101-1, 2.4.101-2), libdrm-radeon1:i386 (2.4.101-1, 2.4.101-2), apport-symptoms:amd64 (0.22, 0.23), gnome-terminal:amd64 (3.35.91-0ubuntu1, 3.36.1.1-1ubuntu1), python3-apt:amd64 (1.9.10, 2.0.0), libdrm-common:amd64 (2.4.101-1, 2.4.101-2) End-Date: 2020-04-15 22:55:07 ``` ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: initramfs-tools 0.136ubuntu6 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Apr 15 23:17:43 2020 InstallationDate: Installed on 2020-04-13 (2 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/zsh SourcePackage: initramfs-tools UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1873085 Title: initramfs keyboard layout back to qwerty after upgrade Status in initramfs-tools package in Ubuntu: New Bug description: After initial installation of Ubuntu 20.04 beta two days ago, I was able to unlock my disk at boot with an AZERTY keyboard. Since afternoon upgrade, my initramfs is now in QWERTY and so I need to input my password in QWERTY which is inconvenient. This is my APT log from my last upgrade : ``` Start-Date: 2020-04-15 22:51:43 Commandline: apt upgrade Requested-By: erdnaxe (1000) Install: appstream:amd64 (0.12.10-2, automatic) Upgrade: ubuntu-desktop-minimal:amd64 (1.447, 1.448), libdrm-nouveau2:amd64 (2.4.101-1, 2.4.101-2), libdrm-nouveau2:i386 (2.4.101-1, 2.4.101-2), libllvm9:amd64 (1:9.0.1-11ubuntu1, 1:9.0.1-12), libllvm9:i386 (1:9.0.1-11ubuntu1, 1:9.0.1-12), libsystemd0:amd64 (245.4-2ubuntu1, 245.4-4ubuntu1), grub-common:amd64 (2.04-1ubuntu24, 2.04-1ubuntu25), ubuntu-standard:amd64 (1.447, 1.448), ubuntu-desktop:amd64 (1.447, 1.448), python-matplotlib-data:amd64 (3.1.2-1ubuntu3, 3.1.2-1ubuntu4), python-apt-common:amd64 (1.9.10, 2.0.0), grub2-common:amd64 (2.04-1ubuntu24, 2.04-1ubuntu25), udev:amd64 (245.4-2ubuntu1, 245.4-4ubuntu1), python3-matplotlib:amd64 (3.1.2-1ubuntu3, 3.1.2-1ubuntu4), nautilus-
Re: [Touch-packages] [Bug 1744457] Re: Installing systemd-cron removes ubuntu-standard
Reason: the Debian policy Le ven. 18 oct. 2019 18:51, Gabriel de Perthuis <1744...@bugs.launchpad.net> a écrit : > Alternatively, systemd-cron could add a Provides: cron, which is what > bcron does. > > -- 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/1744457 Title: Installing systemd-cron removes ubuntu-standard Status in systemd-cron package in Ubuntu: Confirmed Status in ubuntu-meta package in Ubuntu: New Bug description: Installing systemd-cron removes ubuntu-standard, which has a dependency to cron. # apt show systemd-cron Package: systemd-cron Version: 1.5.12-1 [...] Provides: anacron, cron-daemon [...] Conflicts: anacron, cron-daemon Replaces: anacron, cron [...] # apt show ubuntu-standard Package: ubuntu-standard Version: 1.407 [...] Depends: busybox-static, cpio, cron, dmidecode, dnsutils, dosfstools, ed, file, ftp, hdparm, info, iptables, language-selector-common, libpam-systemd, logrotate, lshw, lsof, ltrace, man-db, mime-support, parted, pciutils, popularity-contest, psmisc, rsync, strace, time, usbutils, wget [...] Is there a reason to why cron is not in the Provides field? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd-cron/+bug/1744457/+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 1836236] [NEW] 9.4ubuntu4.9: Broken package because of missing "#" @ /var/lib/dpkg/info/base-files.postinst +131
Public bug reported: Trying to install this on xenial results in: Setting up base-files (9.4ubuntu4.9) ... /var/lib/dpkg/info/base-files.postinst: 131: /var/lib/dpkg/info/base-files.postinst: Automatically: not found dpkg: error processing package base-files (--configure): subprocess installed post-installation script returned error exit status 127 Errors were encountered while processing: base-files E: Sub-process /usr/bin/dpkg returned an error code (1) Because there is a missing comment "#" at the beginning of line 131 of /var/lib/dpkg/info/base-files.postinst, ie: Automatically added by dh_systemd_start ^-- # ? ** Affects: base-files (Ubuntu) Importance: Undecided Status: New ** Description changed: - Trying to install this on xenial result in: + Trying to install this on xenial results in: Setting up base-files (9.4ubuntu4.9) ... /var/lib/dpkg/info/base-files.postinst: 131: /var/lib/dpkg/info/base-files.postinst: Automatically: not found dpkg: error processing package base-files (--configure): - subprocess installed post-installation script returned error exit status 127 + subprocess installed post-installation script returned error exit status 127 Errors were encountered while processing: - base-files + base-files E: Sub-process /usr/bin/dpkg returned an error code (1) Because there is a missing comment "#" at the beginning of line 131 of /var/lib/dpkg/info/base-files.postinst, ie: Automatically added by dh_systemd_start ^-- # ? ** Description changed: Trying to install this on xenial results in: + Setting up base-files (9.4ubuntu4.9) ... /var/lib/dpkg/info/base-files.postinst: 131: /var/lib/dpkg/info/base-files.postinst: Automatically: not found dpkg: error processing package base-files (--configure): subprocess installed post-installation script returned error exit status 127 Errors were encountered while processing: base-files E: Sub-process /usr/bin/dpkg returned an error code (1) - Because there is a missing comment "#" at the beginning of line 131 of - /var/lib/dpkg/info/base-files.postinst, ie: + + Because there is a missing comment "#" at the beginning of line 131 of /var/lib/dpkg/info/base-files.postinst, ie: Automatically added by dh_systemd_start ^-- # ? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-files in Ubuntu. https://bugs.launchpad.net/bugs/1836236 Title: 9.4ubuntu4.9: Broken package because of missing "#" @ /var/lib/dpkg/info/base-files.postinst +131 Status in base-files package in Ubuntu: New Bug description: Trying to install this on xenial results in: Setting up base-files (9.4ubuntu4.9) ... /var/lib/dpkg/info/base-files.postinst: 131: /var/lib/dpkg/info/base-files.postinst: Automatically: not found dpkg: error processing package base-files (--configure): subprocess installed post-installation script returned error exit status 127 Errors were encountered while processing: base-files E: Sub-process /usr/bin/dpkg returned an error code (1) Because there is a missing comment "#" at the beginning of line 131 of /var/lib/dpkg/info/base-files.postinst, ie: Automatically added by dh_systemd_start ^-- # ? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1836236/+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 1832369] [NEW] AUDIO WORK ONLY WITH AUDIO EXTERNAL. AUDIO DIDNT WORK ON INTERNAL SPEAKER
Public bug reported: HI, I have a thomson THN14B with audio card rt5651 and bluetooth If i list a aplay -l to list all my sound card i get : Liste des Périphériques Matériels PLAYBACK carte 0: Audio [Intel HDMI/DP LPE Audio], périphérique 0: HdmiLpeAudio [Intel HDMI/DP LPE Audio] Sous-périphériques: 1/1 Sous-périphérique #0: subdevice #0 carte 0: Audio [Intel HDMI/DP LPE Audio], périphérique 1: HdmiLpeAudio [Intel HDMI/DP LPE Audio] Sous-périphériques: 1/1 Sous-périphérique #0: subdevice #0 carte 0: Audio [Intel HDMI/DP LPE Audio], périphérique 2: HdmiLpeAudio [Intel HDMI/DP LPE Audio] Sous-périphériques: 1/1 Sous-périphérique #0: subdevice #0 carte 1: bytcrrt5651 [bytcr-rt5651], périphérique 0: 3 [] Sous-périphériques: 0/1 Sous-périphérique #0: subdevice #0 carte 1: bytcrrt5651 [bytcr-rt5651], périphérique 1: Deep-Buffer Audio (*) [] Sous-périphériques: 1/1 Sous-périphérique #0: subdevice #0 I thinks it's a bug with interaction to HDMI and RT5651 who broke my internal speaker sound. Have a nice day ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: pulseaudio 1:12.2-0ubuntu5 ProcVersionSignature: Ubuntu 4.18.0-21.22-generic 4.18.20 Uname: Linux 4.18.0-21-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sandra 1154 F pulseaudio /dev/snd/pcmC1D0c: sandra 1154 F...m pulseaudio /dev/snd/pcmC1D0p: sandra 1154 F...m pulseaudio /dev/snd/controlC0: sandra 1154 F pulseaudio CurrentDesktop: XFCE Date: Tue Jun 11 17:21:59 2019 InstallationDate: Installed on 2019-06-11 (0 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: LANGUAGE=fr_FR PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: Upgraded to cosmic on 2019-06-11 (0 days ago) dmi.bios.date: 01/02/2018 dmi.bios.version: HXFZ-14-BI-Y116CR600-CC34O-001-D dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Cherry Trail CR dmi.board.vendor: AMI Corporation dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 10 dmi.chassis.version: To be filled by O.E.M. dmi.modalias: dmi:bvn:bvrHXFZ-14-BI-Y116CR600-CC34O-001-D:bd01/02/2018:svnThomson:pnTHN14B:pvrTobefilledbyO.E.M.:rvnAMICorporation:rnCherryTrailCR:rvrTobefilledbyO.E.M.:cvn:ct10:cvrTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: THN14B dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Thomson modified.conffile..etc.pulse.daemon.conf: [modified] mtime.conffile..etc.pulse.daemon.conf: 2019-06-11T15:27:04.110034 ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic third-party-packages -- 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/1832369 Title: AUDIO WORK ONLY WITH AUDIO EXTERNAL. AUDIO DIDNT WORK ON INTERNAL SPEAKER Status in pulseaudio package in Ubuntu: New Bug description: HI, I have a thomson THN14B with audio card rt5651 and bluetooth If i list a aplay -l to list all my sound card i get : Liste des Périphériques Matériels PLAYBACK carte 0: Audio [Intel HDMI/DP LPE Audio], périphérique 0: HdmiLpeAudio [Intel HDMI/DP LPE Audio] Sous-périphériques: 1/1 Sous-périphérique #0: subdevice #0 carte 0: Audio [Intel HDMI/DP LPE Audio], périphérique 1: HdmiLpeAudio [Intel HDMI/DP LPE Audio] Sous-périphériques: 1/1 Sous-périphérique #0: subdevice #0 carte 0: Audio [Intel HDMI/DP LPE Audio], périphérique 2: HdmiLpeAudio [Intel HDMI/DP LPE Audio] Sous-périphériques: 1/1 Sous-périphérique #0: subdevice #0 carte 1: bytcrrt5651 [bytcr-rt5651], périphérique 0: 3 [] Sous-périphériques: 0/1 Sous-périphérique #0: subdevice #0 carte 1: bytcrrt5651 [bytcr-rt5651], périphérique 1: Deep-Buffer Audio (*) [] Sous-périphériques: 1/1 Sous-périphérique #0: subdevice #0 I thinks it's a bug with interaction to HDMI and RT5651 who broke my internal speaker sound. Have a nice day ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: pulseaudio 1:12.2-0ubuntu5 ProcVersionSignature: Ubuntu 4.18.0-21.22-generic 4.18.20 Uname: Linux 4.18.0-21-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sandra 1154 F pulseaudio /dev/snd/pcmC1D0c: sandra 1154 F...m pulseaudio /dev/snd/pcmC1D0p: sandra 1154 F...m pulseaudio /dev/snd/controlC0: sandra 1154 F pulseaudio CurrentDesktop: XFCE Date: Tue Jun 11 17:21:59 2019 InstallationDate: Installed on 2019-06-11 (0 days ago) InstallationMedia: Xubuntu 1
[Touch-packages] [Bug 1828454] Re: i18n: Wrong french translation of "Mbits/s" as "Mo/s"
How can it be “Fix Committed” when the upstream file at https://gitlab.freedesktop.org/NetworkManager/NetworkManager/blob/master/po/fr.po still has the wrong translation? -- 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/1828454 Title: i18n: Wrong french translation of "Mbits/s" as "Mo/s" Status in Ubuntu Translations: Fix Committed Status in language-pack-gnome-fr package in Ubuntu: Fix Committed Status in network-manager package in Ubuntu: Fix Committed Bug description: When running "nmcli device wifi", the list of avalaible SSID appears with their rate. In english (LANG=C), the rate unit is "Mbit/s". In french (LANG=fr_FR.UTF-8), it has been translated to "Mo/s", which means "MBytes/s"! Assuming the original (english) unit is correct, then it should stay "Mbit/s" in french. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-translations/+bug/1828454/+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 1827644] Re: UPower and battery indicator show wrong information on fully charged ASUS Vivobook X510UR laptop
I think it's a bug, because all laptops I've ever seen show "fully charged" instead of "not charging" when they hit 100% of the battery. And there's some other strange behavior, like the Gnome indicator eventually being stuck at "Estimating" and, sometimes, if you disconnect the power plug while at 100% and connect it again after that, Upower shows "discharging", as if it didn't recognize the power supply again, which is only fixed by a reboot. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1827644 Title: UPower and battery indicator show wrong information on fully charged ASUS Vivobook X510UR laptop Status in upower package in Ubuntu: New Bug description: When the ASUS Vivobook X510UR laptop is completely charged, the correct information is displayed on Windows. However, Ubuntu 18.04.2 LTS is unable to detect the true battery state. The GNOME battery indicator usually shows "Estimating..." or "Not charging", when the battery is at 100%. If you use the upower version 0.99.7-2ubuntu0.18.04.1 command "upower -i /org/freedesktop/UPower/devices/battery_BAT0", this is what you get: native-path: BAT0 vendor: ASUSTeK model:ASUS Battery power supply: yes updated: sex 03 mai 2019 14:33:43 -03 (4 seconds ago) has history: yes has statistics: yes battery present: yes rechargeable:yes state: pending-charge warning-level: none energy: 39,191 Wh energy-empty:0 Wh energy-full: 39,26 Wh energy-full-design: 42,082 Wh energy-rate: 12,453 W voltage: 11,52 V percentage: 100% capacity:93,294% technology: lithium-ion icon-name: 'battery-full-charging-symbolic' History (charge): 1556904821100,000 discharging History (rate): 155690482112,453 discharging 15569048183,744 discharging The "state" should be "fully-charged", but instead it is "pending- charge". ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: upower 0.99.7-2ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 4.18.0-18.19~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: GNOME Date: Fri May 3 14:34:14 2019 InstallationDate: Installed on 2018-12-11 (142 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcEnviron: LANGUAGE=pt_BR:pt:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pt_BR.UTF-8 SHELL=/bin/bash SourcePackage: upower UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1827644/+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 1827644] Re: UPower and battery indicator show wrong information on fully charged ASUS Vivobook X510UR laptop
The system is up to date, so I think I have the updates installed. The content of /sys/class/power_supply/BAT0/status is "Not charging". -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1827644 Title: UPower and battery indicator show wrong information on fully charged ASUS Vivobook X510UR laptop Status in upower package in Ubuntu: Incomplete Bug description: When the ASUS Vivobook X510UR laptop is completely charged, the correct information is displayed on Windows. However, Ubuntu 18.04.2 LTS is unable to detect the true battery state. The GNOME battery indicator usually shows "Estimating..." or "Not charging", when the battery is at 100%. If you use the upower version 0.99.7-2ubuntu0.18.04.1 command "upower -i /org/freedesktop/UPower/devices/battery_BAT0", this is what you get: native-path: BAT0 vendor: ASUSTeK model:ASUS Battery power supply: yes updated: sex 03 mai 2019 14:33:43 -03 (4 seconds ago) has history: yes has statistics: yes battery present: yes rechargeable:yes state: pending-charge warning-level: none energy: 39,191 Wh energy-empty:0 Wh energy-full: 39,26 Wh energy-full-design: 42,082 Wh energy-rate: 12,453 W voltage: 11,52 V percentage: 100% capacity:93,294% technology: lithium-ion icon-name: 'battery-full-charging-symbolic' History (charge): 1556904821100,000 discharging History (rate): 155690482112,453 discharging 15569048183,744 discharging The "state" should be "fully-charged", but instead it is "pending- charge". ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: upower 0.99.7-2ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 4.18.0-18.19~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: GNOME Date: Fri May 3 14:34:14 2019 InstallationDate: Installed on 2018-12-11 (142 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcEnviron: LANGUAGE=pt_BR:pt:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pt_BR.UTF-8 SHELL=/bin/bash SourcePackage: upower UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1827644/+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 1827644] [NEW] UPower and battery indicator show wrong information on fully charged ASUS Vivobook X510UR laptop
Public bug reported: When the ASUS Vivobook X510UR laptop is completely charged, the correct information is displayed on Windows. However, Ubuntu 18.04.2 LTS is unable to detect the true battery state. The GNOME battery indicator usually shows "Estimating..." or "Not charging", when the battery is at 100%. If you use the upower version 0.99.7-2ubuntu0.18.04.1 command "upower -i /org/freedesktop/UPower/devices/battery_BAT0", this is what you get: native-path: BAT0 vendor: ASUSTeK model:ASUS Battery power supply: yes updated: sex 03 mai 2019 14:33:43 -03 (4 seconds ago) has history: yes has statistics: yes battery present: yes rechargeable:yes state: pending-charge warning-level: none energy: 39,191 Wh energy-empty:0 Wh energy-full: 39,26 Wh energy-full-design: 42,082 Wh energy-rate: 12,453 W voltage: 11,52 V percentage: 100% capacity:93,294% technology: lithium-ion icon-name: 'battery-full-charging-symbolic' History (charge): 1556904821 100,000 discharging History (rate): 1556904821 12,453 discharging 1556904818 3,744 discharging The "state" should be "fully-charged", but instead it is "pending- charge". ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: upower 0.99.7-2ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 4.18.0-18.19~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: GNOME Date: Fri May 3 14:34:14 2019 InstallationDate: Installed on 2018-12-11 (142 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcEnviron: LANGUAGE=pt_BR:pt:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pt_BR.UTF-8 SHELL=/bin/bash SourcePackage: upower UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: upower (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1827644 Title: UPower and battery indicator show wrong information on fully charged ASUS Vivobook X510UR laptop Status in upower package in Ubuntu: New Bug description: When the ASUS Vivobook X510UR laptop is completely charged, the correct information is displayed on Windows. However, Ubuntu 18.04.2 LTS is unable to detect the true battery state. The GNOME battery indicator usually shows "Estimating..." or "Not charging", when the battery is at 100%. If you use the upower version 0.99.7-2ubuntu0.18.04.1 command "upower -i /org/freedesktop/UPower/devices/battery_BAT0", this is what you get: native-path: BAT0 vendor: ASUSTeK model:ASUS Battery power supply: yes updated: sex 03 mai 2019 14:33:43 -03 (4 seconds ago) has history: yes has statistics: yes battery present: yes rechargeable:yes state: pending-charge warning-level: none energy: 39,191 Wh energy-empty:0 Wh energy-full: 39,26 Wh energy-full-design: 42,082 Wh energy-rate: 12,453 W voltage: 11,52 V percentage: 100% capacity:93,294% technology: lithium-ion icon-name: 'battery-full-charging-symbolic' History (charge): 1556904821100,000 discharging History (rate): 155690482112,453 discharging 15569048183,744 discharging The "state" should be "fully-charged", but instead it is "pending- charge". ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: upower 0.99.7-2ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 4.18.0-18.19~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: GNOME Date: Fri May 3 14:34:14 2019 InstallationDate: Installed on 2018-12-11 (142 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcEnviron: LANGUAGE=pt_BR:pt:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pt_BR.UTF-8 SHELL=/bin/bash SourcePackage: upower UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1827644/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net U
[Touch-packages] [Bug 1745032] Re: AC adapter status not detected on Asus ZenBook UX410UAK
This issue also affects Asus Vivobook 15 X510UR. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1745032 Title: AC adapter status not detected on Asus ZenBook UX410UAK Status in gnome-control-center package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Status in linux package in Ubuntu: In Progress Status in upower package in Ubuntu: Confirmed Bug description: === SRU Justification === [Impact] Some Asus laptops report "discharging" when the battery is full and AC is plugged [Test] Charge battery to full, the issue appears. Users report with the patch the behaviour is correct. [Fix] The discharge rate is 0 on those machines. Use that to detect the wrong status report. [Regression Potential] Low. The quirk uses strict DMI to match affected systems. === Original Bug Report === The AC adapter status is incorrectly reported when the battery is fully charged. It always shows as if the adapter is not plugged in. If the battery is drained for a while, the adapter status is shown correctly (both connects and disconnects are shown). ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-31-generic 4.13.0-31.34 ProcVersionSignature: Ubuntu 4.13.0-31.34-generic 4.13.13 Uname: Linux 4.13.0-31-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: abarto 1388 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Jan 23 18:26:18 2018 InstallationDate: Installed on 2018-01-23 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 04f2:b57a Chicony Electronics Co., Ltd Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX410UAK ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-31-generic.efi.signed root=UUID=58ea0561-3f74-4566-9332-5e7021275160 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-31-generic N/A linux-backports-modules-4.13.0-31-generic N/A linux-firmware 1.169.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/08/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX410UAK.306 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX410UAK dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX410UAK.306:bd08/08/2017:svnASUSTeKCOMPUTERINC.:pnUX410UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX410UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: UX dmi.product.name: UX410UAK dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1745032/+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 1796308] [NEW] package libapparmor1:amd64 2.12-4ubuntu5 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configu
Public bug reported: I don't know. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libapparmor1:amd64 2.12-4ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 Date: Fri Oct 5 10:47:23 2018 Dependencies: gcc-8-base 8-20180414-1ubuntu2 libc6 2.27-3ubuntu1 libgcc1 1:8-20180414-1ubuntu2 DuplicateSignature: package:libapparmor1:amd64:2.12-4ubuntu5 Setting up librubberband2:amd64 (1.8.1-7ubuntu2) ... dpkg: error processing package libapparmor1:amd64 (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2018-08-09 (56 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-4.15.0-34-generic root=UUID=46667fc6-e4b4-40a9-969f-70f354598d84 ro quiet splash vt.handoff=1 Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.3ubuntu0.1 SourcePackage: apparmor Syslog: Title: package libapparmor1:amd64 2.12-4ubuntu5 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: apparmor (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic -- 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/1796308 Title: package libapparmor1:amd64 2.12-4ubuntu5 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in apparmor package in Ubuntu: New Bug description: I don't know. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libapparmor1:amd64 2.12-4ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 Date: Fri Oct 5 10:47:23 2018 Dependencies: gcc-8-base 8-20180414-1ubuntu2 libc6 2.27-3ubuntu1 libgcc1 1:8-20180414-1ubuntu2 DuplicateSignature: package:libapparmor1:amd64:2.12-4ubuntu5 Setting up librubberband2:amd64 (1.8.1-7ubuntu2) ... dpkg: error processing package libapparmor1:amd64 (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2018-08-09 (56 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-4.15.0-34-generic root=UUID=46667fc6-e4b4-40a9-969f-70f354598d84 ro quiet splash vt.handoff=1 Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.3ubuntu0.1 SourcePackage: apparmor Syslog: Title: package libapparmor1:amd64 2.12-4ubuntu5 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1796308/+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 1791462] [NEW] package base-files 10.1ubuntu2.2 failed to install/upgrade: O pacote está num mau estado de inconsistência; deve reinstala-lo antes de tentar configura-lo.
Public bug reported: O dpkg foi interrompido, para corrigir o problema tem de correr manualmente 'sudo dpkg --configure -a' alexandre@alexandre-Vostro-1520:~$ sudo dpkg --configure -a dpkg: erro ao processar o pacote base-files (--configure): O pacote está num mau estado de inconsistência; deve reinstala-lo antes de tentar configura-lo. Erros foram encontrados durante o processamento de: base-files alexandre@alexandre-Vostro-1520:~$ sudo apt-get install -f Lendo listas de pacotes... Pronto Construindo árvore de dependências Lendo informação de estado... Pronto 0 pacotes atualizados, 0 pacotes novos instalados, 0 a serem removidos e 30 não atualizados. 1 pacotes não totalmente instalados ou removidos. É preciso baixar 58,2 kB de arquivos. Depois desta operação, 0 B adicionais de espaço em disco serão usados. Obter:1 http://security.ubuntu.com/ubuntu bionic-security/main amd64 base-files amd64 10.1ubuntu2.2 [58,2 kB] Baixados 58,2 kB em 1s (48,9 kB/s) dpkg: erro ao processar o pacote base-files (--configure): O pacote está num mau estado de inconsistência; deve reinstala-lo antes de tentar configura-lo. Erros foram encontrados durante o processamento de: base-files ProblemType: Package DistroRelease: Ubuntu 18.04 Package: base-files 10.1ubuntu2.2 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.2 AptOrdering: base-files:amd64: Configure NULL: ConfigurePending Architecture: amd64 Date: Sat Sep 8 16:36:45 2018 Dependencies: DpkgTerminalLog: dpkg: erro ao processar o pacote base-files (--configure): O pacote está num mau estado de inconsistência; deve reinstala-lo antes de tentar configura-lo. ErrorMessage: O pacote está num mau estado de inconsistência; deve reinstala-lo antes de tentar configura-lo. InstallationDate: Installed on 2018-08-12 (26 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.3ubuntu0.1 SourcePackage: base-files Title: package base-files 10.1ubuntu2.2 failed to install/upgrade: O pacote está num mau estado de inconsistência; deve reinstala-lo antes de tentar configura-lo. UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: base-files (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-files in Ubuntu. https://bugs.launchpad.net/bugs/1791462 Title: package base-files 10.1ubuntu2.2 failed to install/upgrade: O pacote está num mau estado de inconsistência; deve reinstala-lo antes de tentar configura-lo. Status in base-files package in Ubuntu: New Bug description: O dpkg foi interrompido, para corrigir o problema tem de correr manualmente 'sudo dpkg --configure -a' alexandre@alexandre-Vostro-1520:~$ sudo dpkg --configure -a dpkg: erro ao processar o pacote base-files (--configure): O pacote está num mau estado de inconsistência; deve reinstala-lo antes de tentar configura-lo. Erros foram encontrados durante o processamento de: base-files alexandre@alexandre-Vostro-1520:~$ sudo apt-get install -f Lendo listas de pacotes... Pronto Construindo árvore de dependências Lendo informação de estado... Pronto 0 pacotes atualizados, 0 pacotes novos instalados, 0 a serem removidos e 30 não atualizados. 1 pacotes não totalmente instalados ou removidos. É preciso baixar 58,2 kB de arquivos. Depois desta operação, 0 B adicionais de espaço em disco serão usados. Obter:1 http://security.ubuntu.com/ubuntu bionic-security/main amd64 base-files amd64 10.1ubuntu2.2 [58,2 kB] Baixados 58,2 kB em 1s (48,9 kB/s) dpkg: erro ao processar o pacote base-files (--configure): O pacote está num mau estado de inconsistência; deve reinstala-lo antes de tentar configura-lo. Erros foram encontrados durante o processamento de: base-files ProblemType: Package DistroRelease: Ubuntu 18.04 Package: base-files 10.1ubuntu2.2 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.2 AptOrdering: base-files:amd64: Configure NULL: ConfigurePending Architecture: amd64 Date: Sat Sep 8 16:36:45 2018 Dependencies: DpkgTerminalLog: dpkg: erro ao processar o pacote base-files (--configure): O pacote está num mau estado de inconsistência; deve reinstala-lo antes de tentar configura-lo. ErrorMessage: O pacote está num mau estado de inconsistência; deve reinstala-lo antes de tentar configura-lo. InstallationDat
[Touch-packages] [Bug 1787025] [NEW] package systemd-sysv 237-3ubuntu10.3 failed to install/upgrade: installed systemd-shim package post-removal script subprocess returned error exit status 2
Public bug reported: Ocorreu na instalação ProblemType: Package DistroRelease: Ubuntu 18.04 Package: systemd-sysv 237-3ubuntu10.3 ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18 Uname: Linux 4.15.0-30-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Tue Aug 14 11:19:54 2018 ErrorMessage: installed systemd-shim package post-removal script subprocess returned error exit status 2 InstallationDate: Installed on 2013-12-03 (1715 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.3 SourcePackage: systemd Title: package systemd-sysv 237-3ubuntu10.3 failed to install/upgrade: installed systemd-shim package post-removal script subprocess returned error exit status 2 UpgradeStatus: Upgraded to bionic on 2018-08-14 (0 days ago) ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic third-party-packages -- 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/1787025 Title: package systemd-sysv 237-3ubuntu10.3 failed to install/upgrade: installed systemd-shim package post-removal script subprocess returned error exit status 2 Status in systemd package in Ubuntu: New Bug description: Ocorreu na instalação ProblemType: Package DistroRelease: Ubuntu 18.04 Package: systemd-sysv 237-3ubuntu10.3 ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18 Uname: Linux 4.15.0-30-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Tue Aug 14 11:19:54 2018 ErrorMessage: installed systemd-shim package post-removal script subprocess returned error exit status 2 InstallationDate: Installed on 2013-12-03 (1715 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.3 SourcePackage: systemd Title: package systemd-sysv 237-3ubuntu10.3 failed to install/upgrade: installed systemd-shim package post-removal script subprocess returned error exit status 2 UpgradeStatus: Upgraded to bionic on 2018-08-14 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1787025/+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 1787024] [NEW] package dbus 1.12.2-1ubuntu1 failed to install/upgrade: triggers looping, abandoned
Public bug reported: Problem in instalation ProblemType: Package DistroRelease: Ubuntu 18.04 Package: dbus 1.12.2-1ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18 Uname: Linux 4.15.0-30-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Tue Aug 14 08:33:35 2018 ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2013-12-03 (1715 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.3 SourcePackage: dbus Title: package dbus 1.12.2-1ubuntu1 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: Upgraded to bionic on 2018-08-14 (0 days ago) ** Affects: dbus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus in Ubuntu. https://bugs.launchpad.net/bugs/1787024 Title: package dbus 1.12.2-1ubuntu1 failed to install/upgrade: triggers looping, abandoned Status in dbus package in Ubuntu: New Bug description: Problem in instalation ProblemType: Package DistroRelease: Ubuntu 18.04 Package: dbus 1.12.2-1ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18 Uname: Linux 4.15.0-30-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Tue Aug 14 08:33:35 2018 ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2013-12-03 (1715 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.3 SourcePackage: dbus Title: package dbus 1.12.2-1ubuntu1 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: Upgraded to bionic on 2018-08-14 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1787024/+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 1756238] Re: gdebi-gtk broken in 18.04 error: unable to read filedescriptor flags
I have the exact same problem in Ubuntu 18.04.1 tottaly updated, including backports. Mark Smith #26 commentary works with me also. I think the gdebi-gtk when not opened from terminal, crashes when I have to type me password -- 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/1756238 Title: gdebi-gtk broken in 18.04 error: unable to read filedescriptor flags Status in gdebi package in Ubuntu: Triaged Status in vte2.91 package in Ubuntu: Fix Released Status in vte2.91 source package in Bionic: Fix Released Bug description: When using gdebi-gtk to install a .deb the install fails with the message:- dpkg: error: unable to read filedescriptor flags for : Bad file descriptor This only occurs via the gdebi-gtk GUI front end, packages install perfectly if done via the CLI with: sudo gdebi /path/to/packagename.deb To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdebi/+bug/1756238/+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 1698604] [NEW] login will show unmasked password if user types too fast on a slow system
Public bug reported: At the login, from the terminal, the user must login using his username and password. The program first displays " login:", then the user enters his username. Once the user has pressed "enter", he must enter his password. The user may type too quickly before "Password:" appears and thus what he types before "Password:" was displayed will appear on the screen. This occurs when the computer is slow when verifying the login username. Users that are used to fast computer will start typing right their password right after pressing "enter" and the characters will appear on the screen. The result would be something like this: Ubuntu 16.04.2 LTS computername tty2 computername login: myusername mypPassword: People who may look at my screen will see that my password starts with "myp". The other characters typed after that "Password:" was displayed are invisible. The solution would be to make every characters that are typed after the user has entered his password invisible. It could also be a good idea to give the user a sound cue (a PC speaker beep) when he enters a character in the case where he starts typing his password too fast. ** Affects: shadow (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to shadow in Ubuntu. https://bugs.launchpad.net/bugs/1698604 Title: login will show unmasked password if user types too fast on a slow system Status in shadow package in Ubuntu: New Bug description: At the login, from the terminal, the user must login using his username and password. The program first displays " login:", then the user enters his username. Once the user has pressed "enter", he must enter his password. The user may type too quickly before "Password:" appears and thus what he types before "Password:" was displayed will appear on the screen. This occurs when the computer is slow when verifying the login username. Users that are used to fast computer will start typing right their password right after pressing "enter" and the characters will appear on the screen. The result would be something like this: Ubuntu 16.04.2 LTS computername tty2 computername login: myusername mypPassword: People who may look at my screen will see that my password starts with "myp". The other characters typed after that "Password:" was displayed are invisible. The solution would be to make every characters that are typed after the user has entered his password invisible. It could also be a good idea to give the user a sound cue (a PC speaker beep) when he enters a character in the case where he starts typing his password too fast. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1698604/+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 1677540] Re: corrupted mouse pointer icon
1684240 seems to be the same issue. In my case this can be reproduced under Kubuntu with Nvidia. -- 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/1677540 Title: corrupted mouse pointer icon Status in Canonical System Image: New Status in Mir: New Status in libsdl2 package in Ubuntu: Confirmed Status in mir package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Confirmed Bug description: Ubuntu 17.04 unity8 corrupted mouse pointer icon (see attaches screenshot, the mouse pointer is hovering places/Home on the file manager app, the orange block/square) mostly i see when i run apps with Xmir, maybe stuff that uses SDL, mpv, neverball and it's only the arrow pointer, the rest are not affected, resize arrows etc To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1677540/+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 1590844] Re: Call with Bluetooth headset not working [Meizu Pro 5 Ubuntu Edition]
Hello Stephan, Is there a simple / not risky way to update the kernel on ubuntu ? Alexandre, -- 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/1590844 Title: Call with Bluetooth headset not working [Meizu Pro 5 Ubuntu Edition] Status in Canonical System Image: Confirmed Status in turbo: Confirmed Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Status in telephony-service package in Ubuntu: Confirmed Bug description: My bluetooth headset perfectly connects to my Meizu Pro 5. However, the sound quality is so poor (a lot of noise) such that you don't understand your communication partner. Note that the headset works perfectly together with Ubuntu on my Nexus 4. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1590844/+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 1590844] Re: Call with Bluetooth headset not working [Meizu Pro 5 Ubuntu Edition]
** Summary changed: - Bluetooth headset not working with Meizu Pro 5 Ubuntu Edition + Call with Bluetooth headset not working [Meizu Pro 5 Ubuntu Edition] -- 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/1590844 Title: Call with Bluetooth headset not working [Meizu Pro 5 Ubuntu Edition] Status in Canonical System Image: Confirmed Status in turbo: Confirmed Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: New Status in telephony-service package in Ubuntu: New Bug description: My bluetooth headset perfectly connects to my Meizu Pro 5. However, the sound quality is so poor (a lot of noise) such that you don't understand your communication partner. Note that the headset works perfectly together with Ubuntu on my Nexus 4. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1590844/+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 1590844] Re: Bluetooth headset not working with Meizu Pro 5 Ubuntu Edition
@Seth, I don't know at all. I also tied to modify some pulseaudio conf without success. 1. It's working on android --> so the problem come from ubuntu ? 2. Bluez / Bluetooth seems to have same behaviour than the other ubuntu phone (nexus 4 , ...) 3. Pulseaudio / audio is working well with the other sounds (music player, ...) even with Bluetooth 4. Only a call sound with bluetooth is noising. Problem seems to be sound's configuration between telephony service / bluez / pulseaudio If we don't know the service(s) that impact this bug, could it be possible to have a discussion between people working on theses different services in order to understand the link between telephony/bluez/pulseaudio ? These are only assumptions. ** Also affects: telephony-service (Ubuntu) Importance: Undecided Status: New -- 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/1590844 Title: Bluetooth headset not working with Meizu Pro 5 Ubuntu Edition Status in Canonical System Image: Confirmed Status in turbo: Confirmed Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: New Status in telephony-service package in Ubuntu: New Bug description: My bluetooth headset perfectly connects to my Meizu Pro 5. However, the sound quality is so poor (a lot of noise) such that you don't understand your communication partner. Note that the headset works perfectly together with Ubuntu on my Nexus 4. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1590844/+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 1590844] Re: Bluetooth headset not working with Meizu Pro 5 Ubuntu Edition
** Also affects: pulseaudio (Ubuntu) Importance: Undecided Status: New -- 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/1590844 Title: Bluetooth headset not working with Meizu Pro 5 Ubuntu Edition Status in Canonical System Image: Confirmed Status in turbo: Confirmed Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: New Bug description: My bluetooth headset perfectly connects to my Meizu Pro 5. However, the sound quality is so poor (a lot of noise) such that you don't understand your communication partner. Note that the headset works perfectly together with Ubuntu on my Nexus 4. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1590844/+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 1560086] Re: cannot download files with no destination app from webapps
** Changed in: webapps-sprint Milestone: sprint-25 => sprint-26 -- 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/1560086 Title: cannot download files with no destination app from webapps Status in Canonical System Image: Confirmed Status in Ubuntu UX: Triaged Status in The Webapps-core project: New Status in webapps-sprint: In Progress Status in webbrowser-app package in Ubuntu: In Progress Bug description: Using the webbrowser-app I can download any file, and will be prompted to open in an app (if apps that support that content-type exist on the system) or to download the file in the browser. The same behavior should be available webapps but is not. Steps to reproduce: - Open Gmail webapp - Open a message that has an attachment of a file of unsupported type (like a .tar, .click, etc) - click on the file to download Expected results: - I should be prompted to open the file in supported app or to download - If I choose download the file should be downloaded into ~/Downloads by the webbrowser-app Actual results: - I am told that no apps exist to support this type of file and am not allowed to download it To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1560086/+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 1629466] Re: Can't open a PDF from a webapp
*** This bug is a duplicate of bug 1560086 *** https://bugs.launchpad.net/bugs/1560086 This is a duplicate of https://bugs.launchpad.net/webapps- core/+bug/1560086 for which there is a branch in progress, sorry for the delay on this, I will MR it ASAP, ** This bug has been marked a duplicate of bug 1560086 cannot download files with no destination app from webapps -- 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/1629466 Title: Can't open a PDF from a webapp Status in webbrowser-app package in Ubuntu: New Bug description: And potentially any Content Hub file? When trying to open pdfs in the fastmail or reddit webapps, I get the following and the pdf never opens: file:///usr/lib/arm-linux-gnueabihf/qt5/qml/Ubuntu/Content/ContentPeerPicker13.qml:194: TypeError: Cannot read property 'peers' of null file:///usr/share/webbrowser-app/webcontainer/WebappWebview.qml:219: ReferenceError: startDownload is not defined I'm assuming it's the second message that is fatal, so I've opened against webbrowser-app. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1629466/+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 1626345] Re: After rebooting for updates, reboot is still required.
Sure Brian, here it is. I think my case was exactly the same, as I also did a 'apt-get autoremove'. But, the strange think is that the reboot file vanished and the system is no longer asking me for reboots (probably since yesterday), but I didn't do anything specific to try to solve the problem. ** Attachment added: "My /var/log/apt/history.log" https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1626345/+attachment/4749048/+files/history.log -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1626345 Title: After rebooting for updates, reboot is still required. Status in One Hundred Papercuts: Confirmed Status in unattended-upgrades package in Ubuntu: Incomplete Bug description: Yesterday unattended-upgrades required a reboot for kernel updates as expected. But today unattended-upgrades required a reboot even though there were no updates. 2016-09-20 05:20:10,409 INFO Initial blacklisted packages: 2016-09-20 05:20:10,410 INFO Initial whitelisted packages: 2016-09-20 05:20:10,411 INFO Starting unattended upgrades script 2016-09-20 05:20:10,411 INFO Allowed origins are: ['o=Ubuntu,a=xenial-security', 'o=Ubuntu,a=xenial-updates'] 2016-09-20 05:21:13,118 INFO Packages that will be upgraded: linux-generic linux-headers-generic linux-image-generic linux-libc-dev 2016-09-20 05:21:13,119 INFO Writing dpkg log to '/var/log/unattended-upgrades/unattended-upgrades-dpkg.log' 2016-09-20 05:24:17,405 INFO All upgrades installed 2016-09-20 05:24:24,959 WARNING Found /var/run/reboot-required, rebooting 2016-09-21 05:10:54,080 INFO Initial blacklisted packages: 2016-09-21 05:10:54,088 INFO Initial whitelisted packages: 2016-09-21 05:10:54,089 INFO Starting unattended upgrades script 2016-09-21 05:10:54,089 INFO Allowed origins are: ['o=Ubuntu,a=xenial-security', 'o=Ubuntu,a=xenial-updates'] 2016-09-21 05:11:02,624 INFO No packages found that can be upgraded unattended and no pending auto-removals 2016-09-21 05:11:02,624 WARNING Found /var/run/reboot-required, rebooting On this machine (16.04 server) unattended-upgrades is configured to reboot automatically. This also happened on another 16.04 server with default unattended- upgrades configuration. It displayed the ***System restart required*** message. The same on a 14.04 server and a 14.04 desktop. Expected behaviour: Not to do an unnecessary reboot. Let me know what other information I can provide. To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1626345/+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 1626345] Re: After rebooting for updates, reboot is still required.
** Changed in: unattended-upgrades (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1626345 Title: After rebooting for updates, reboot is still required. Status in unattended-upgrades package in Ubuntu: Confirmed Bug description: Yesterday unattended-upgrades required a reboot for kernel updates as expected. But today unattended-upgrades required a reboot even though there were no updates. 2016-09-20 05:20:10,409 INFO Initial blacklisted packages: 2016-09-20 05:20:10,410 INFO Initial whitelisted packages: 2016-09-20 05:20:10,411 INFO Starting unattended upgrades script 2016-09-20 05:20:10,411 INFO Allowed origins are: ['o=Ubuntu,a=xenial-security', 'o=Ubuntu,a=xenial-updates'] 2016-09-20 05:21:13,118 INFO Packages that will be upgraded: linux-generic linux-headers-generic linux-image-generic linux-libc-dev 2016-09-20 05:21:13,119 INFO Writing dpkg log to '/var/log/unattended-upgrades/unattended-upgrades-dpkg.log' 2016-09-20 05:24:17,405 INFO All upgrades installed 2016-09-20 05:24:24,959 WARNING Found /var/run/reboot-required, rebooting 2016-09-21 05:10:54,080 INFO Initial blacklisted packages: 2016-09-21 05:10:54,088 INFO Initial whitelisted packages: 2016-09-21 05:10:54,089 INFO Starting unattended upgrades script 2016-09-21 05:10:54,089 INFO Allowed origins are: ['o=Ubuntu,a=xenial-security', 'o=Ubuntu,a=xenial-updates'] 2016-09-21 05:11:02,624 INFO No packages found that can be upgraded unattended and no pending auto-removals 2016-09-21 05:11:02,624 WARNING Found /var/run/reboot-required, rebooting On this machine (16.04 server) unattended-upgrades is configured to reboot automatically. This also happened on another 16.04 server with default unattended- upgrades configuration. It displayed the ***System restart required*** message. The same on a 14.04 server and a 14.04 desktop. Expected behaviour: Not to do an unnecessary reboot. Let me know what other information I can provide. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1626345/+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 1626345] Re: After rebooting for updates, reboot is still required.
Hello, Brian, I do have that '/var/run/reboot-required.pkgs', it's contents are simply: linux-base -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1626345 Title: After rebooting for updates, reboot is still required. Status in unattended-upgrades package in Ubuntu: Incomplete Bug description: Yesterday unattended-upgrades required a reboot for kernel updates as expected. But today unattended-upgrades required a reboot even though there were no updates. 2016-09-20 05:20:10,409 INFO Initial blacklisted packages: 2016-09-20 05:20:10,410 INFO Initial whitelisted packages: 2016-09-20 05:20:10,411 INFO Starting unattended upgrades script 2016-09-20 05:20:10,411 INFO Allowed origins are: ['o=Ubuntu,a=xenial-security', 'o=Ubuntu,a=xenial-updates'] 2016-09-20 05:21:13,118 INFO Packages that will be upgraded: linux-generic linux-headers-generic linux-image-generic linux-libc-dev 2016-09-20 05:21:13,119 INFO Writing dpkg log to '/var/log/unattended-upgrades/unattended-upgrades-dpkg.log' 2016-09-20 05:24:17,405 INFO All upgrades installed 2016-09-20 05:24:24,959 WARNING Found /var/run/reboot-required, rebooting 2016-09-21 05:10:54,080 INFO Initial blacklisted packages: 2016-09-21 05:10:54,088 INFO Initial whitelisted packages: 2016-09-21 05:10:54,089 INFO Starting unattended upgrades script 2016-09-21 05:10:54,089 INFO Allowed origins are: ['o=Ubuntu,a=xenial-security', 'o=Ubuntu,a=xenial-updates'] 2016-09-21 05:11:02,624 INFO No packages found that can be upgraded unattended and no pending auto-removals 2016-09-21 05:11:02,624 WARNING Found /var/run/reboot-required, rebooting On this machine (16.04 server) unattended-upgrades is configured to reboot automatically. This also happened on another 16.04 server with default unattended- upgrades configuration. It displayed the ***System restart required*** message. The same on a 14.04 server and a 14.04 desktop. Expected behaviour: Not to do an unnecessary reboot. Let me know what other information I can provide. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1626345/+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 1624735] [NEW] PCI/internal sound card not detected
Public bug reported: canot play sound or video ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: alsa-base 1.0.25+dfsg-0ubuntu1.1 ProcVersionSignature: Ubuntu 3.2.0-109.150-generic 3.2.79 Uname: Linux 3.2.0-109-generic i686 AlsaDevices: total 0 crw-rw---T 1 root audio 116, 1 Set 17 21:24 seq crw-rw---T 1 root audio 116, 33 Set 17 21:24 timer AplayDevices: aplay: device_list:252: no soundcards found... ApportVersion: 2.0.1-0ubuntu17.13 Architecture: i386 ArecordDevices: arecord: device_list:252: no soundcards found... AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Sat Sep 17 21:39:37 2016 InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012) MarkForUpload: True PackageArchitecture: all PciMultimedia: ProcEnviron: LANGUAGE=pt:pt_BR:en PATH=(custom, no user) LANG=pt_PT.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: Upgraded to precise on 2016-09-01 (16 days ago) dmi.bios.date: 09/24/98 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: 4.51 PG dmi.board.name: i440BX-W977TF dmi.chassis.type: 2 dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvr4.51PG:bd09/24/98:svn:pn:pvr:rvn:rni440BX-W977TF:rvr:cvn:ct2:cvr: ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 precise running-unity -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1624735 Title: PCI/internal sound card not detected Status in alsa-driver package in Ubuntu: New Bug description: canot play sound or video ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: alsa-base 1.0.25+dfsg-0ubuntu1.1 ProcVersionSignature: Ubuntu 3.2.0-109.150-generic 3.2.79 Uname: Linux 3.2.0-109-generic i686 AlsaDevices: total 0 crw-rw---T 1 root audio 116, 1 Set 17 21:24 seq crw-rw---T 1 root audio 116, 33 Set 17 21:24 timer AplayDevices: aplay: device_list:252: no soundcards found... ApportVersion: 2.0.1-0ubuntu17.13 Architecture: i386 ArecordDevices: arecord: device_list:252: no soundcards found... AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Sat Sep 17 21:39:37 2016 InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012) MarkForUpload: True PackageArchitecture: all PciMultimedia: ProcEnviron: LANGUAGE=pt:pt_BR:en PATH=(custom, no user) LANG=pt_PT.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: Upgraded to precise on 2016-09-01 (16 days ago) dmi.bios.date: 09/24/98 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: 4.51 PG dmi.board.name: i440BX-W977TF dmi.chassis.type: 2 dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvr4.51PG:bd09/24/98:svn:pn:pvr:rvn:rni440BX-W977TF:rvr:cvn:ct2:cvr: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1624735/+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 1599692] Re: [webapp-container] URLs dispatched from an app to a webapp are not opened
** Branch linked: lp:~abreu-alexandre/webbrowser-app/webapp-url- dispatcher-failure -- 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/1599692 Title: [webapp-container] URLs dispatched from an app to a webapp are not opened Status in webapps-sprint: In Progress Status in webbrowser-app package in Ubuntu: New Bug description: There is again a failure when dispatching URLs from an app to a webapp. For example, if in the facebook webapp, one clicks on a specific twitter.com/* url that links to the Twitter webapp, the webapp opens but not to the desired URL. To manage notifications about this bug go to: https://bugs.launchpad.net/webapps-sprint/+bug/1599692/+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 1441547] Re: [HERE] Failed to create a HERE account
** Changed in: webapps-sprint Status: In Progress => Fix Committed -- 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/1441547 Title: [HERE] Failed to create a HERE account Status in Canonical System Image: Confirmed Status in The Savilerow project: Fix Committed Status in webapps-sprint: Fix Committed Status in webbrowser-app package in Ubuntu: Invalid Bug description: arale device, r165, ubuntu-touch/vivid-proposed Steps: 1. Launch HERE maps 2. Go to Settings -> Sign In 3. Tap on "Register for a HERE account" => Dropdown lists can't show and select (Day, Month, Year, Country) And can't continue to register account. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1441547/+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 1579101] Re: no keyboard shortcuts in webapp containers
** Changed in: webapps-sprint Status: In Progress => Fix Released -- 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/1579101 Title: no keyboard shortcuts in webapp containers Status in Canonical System Image: Fix Committed Status in webapps-sprint: Fix Released Status in webbrowser-app package in Ubuntu: Fix Released Bug description: having a keyboard attached to the phone/tablet i can use things like Ctrl-R or Alt+Left/Right to navigate in the webbrowser app ... none of these shortcuts work in webapp-containers though (while scrolling via cursor keys and PgUp and PgDn works) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1579101/+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 1571361] Re: Sharing from webbrowserapp should include title of the page
** Changed in: webapps-core Status: In Progress => Fix Committed -- 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/1571361 Title: Sharing from webbrowserapp should include title of the page Status in Canonical System Image: Fix Released Status in Dekko: Fix Committed Status in The Webapps-core project: Fix Committed Status in webapps-sprint: New Status in content-hub package in Ubuntu: Fix Released Status in messaging-app package in Ubuntu: New Status in webbrowser-app package in Ubuntu: Fix Released Bug description: Sharing a page from webbrowser should include the title of the page, not only the URL. Steps to reproduce: - Open webbrowser - Open a web site - Share it via "share" button in the top right of the browser - Choose one of the possible apps (e.g. Twitter) - It take you to Twitter app, composing a new tweet - The new tweet has only the URL of the web page Ubuntu Phone on Meizu MX4 OTA 10.1 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1571361/+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 1616327] Re: "Browser not supported" ebay.de
*** This bug is a duplicate of bug 1575780 *** https://bugs.launchpad.net/bugs/1575780 ** This bug has been marked a duplicate of bug 1575780 Ebay webapp doesn't display on frieza just displays an error -- 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/1616327 Title: "Browser not supported" ebay.de Status in webbrowser-app package in Ubuntu: New Bug description: Today I wanted to find something on ebay.de with my M10 At first the page opened properly. I wrote in a search field what I was looking for and as a result I received an answer that my browser is no longer supported and that I should use my PC. I'm attaching a screenshot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1616327/+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 1593919] Re: Bluetooth not working with Meizu Pro 5
*** This bug is a duplicate of bug 1590844 *** https://bugs.launchpad.net/bugs/1590844 ** This bug has been marked a duplicate of bug 1590844 Bluetooth headset not working with Meizu Pro 5 Ubuntu Edition -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1593919 Title: Bluetooth not working with Meizu Pro 5 Status in turbo: New Status in bluez package in Ubuntu: Confirmed Bug description: I have problems with bluetooth. When I connect my Jabra Supreme headset, or connect with my car (Ford Fiesta), I only hear a lot of noise. This is both when I make a call, or receive an incoming call. I can hear music via bluetooth without problems on both headset, and in the car. To manage notifications about this bug go to: https://bugs.launchpad.net/turbo/+bug/1593919/+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 1537737] Re: Since Bluez5, headsets don't reconnect audio when reconnecting
Here some logs in attachment (I think in the first 10 minutes) Explanation : How it works : 1. Turn on the headset --> bluetooth connects automatically the headset (already paired in the past) 2. Make a call --> dialer-app show the bluetooth icon by default 3. No sound for the call (even in internal phone speaker), if you switch back to phone speaker option the sound is back in internal phone speaker 4. Switch back to bluetooth --> still no sound 5. Disconnect manually from headset and reconnect (in settings>Bluetooth>device name) 6. Make a call --> The sound is now routed to headset How it should work : 1. Turn on the headset --> bluetooth connects automatically the headset (already paired in the past) 2. Make a call --> dialer-app shows the bluetooth icon by default 3. The sound is routed to the bluetooth headset Alexandre, ** Attachment added: "log-bug-1537737 .zip" https://bugs.launchpad.net/canonical-devices-system-image/+bug/1537737/+attachment/4712251/+files/log-bug-1537737%20.zip -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1537737 Title: Since Bluez5, headsets don't reconnect audio when reconnecting Status in Canonical System Image: Confirmed Status in bluez package in Ubuntu: Confirmed Bug description: Pairing a Bluetooth headset (A2DP) seems to work fine. After pairing, the phone successfully switches to transmit audio over Bluetooth. When disconnecting the Headset again, the phone successfully switches audio back to the integrated speaker. However, on a reconnect without pairing, the headset seems to connect properly, but it doesn't route audio any more to the headset. Despite the headset being connected, audio is still routed to the integrated speaker. A reboot does not seem to help. The only way to get back to Bluetooth audio streaming is to delete the device from the settings, and pair it again, which makes it work once again. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1537737/+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 1590844] Re: Bluetooth headset not working with Meizu Pro 5 Ubuntu Edition
Here is the logs with an other headset Doing a call --> lot of noise / saturated sound in headset Playing music --> sound is good in headset At the beginning of the log, I had to disconnect manually from the headset and reconnect because the sound was not redirected to headset (I think this is an other bug like here --> #1537737 [1]) [1] : https://bugs.launchpad.net/canonical-devices-system-image/+bug/1537737 Alexandre, ** Attachment added: "log-bug-1590844.zip" https://bugs.launchpad.net/canonical-devices-system-image/+bug/1590844/+attachment/4712228/+files/log-bug-1590844.zip -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1590844 Title: Bluetooth headset not working with Meizu Pro 5 Ubuntu Edition Status in Canonical System Image: Confirmed Status in turbo: Confirmed Status in bluez package in Ubuntu: Confirmed Bug description: My bluetooth headset perfectly connects to my Meizu Pro 5. However, the sound quality is so poor (a lot of noise) such that you don't understand your communication partner. Note that the headset works perfectly together with Ubuntu on my Nexus 4. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1590844/+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 1537737] Re: Since Bluez5, headsets don't reconnect audio when reconnecting
I can reproduce this bug on Meizu pro 5 rc-proposed and Nexus 4 rc- proposed (both last revision) In my case if you disconnect manually from the bluetooth device and reconnect to it (in settings>Bluetooth>device name), then the sound is routed well to bluetooth device -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1537737 Title: Since Bluez5, headsets don't reconnect audio when reconnecting Status in Canonical System Image: Confirmed Status in bluez package in Ubuntu: Confirmed Bug description: Pairing a Bluetooth headset (A2DP) seems to work fine. After pairing, the phone successfully switches to transmit audio over Bluetooth. When disconnecting the Headset again, the phone successfully switches audio back to the integrated speaker. However, on a reconnect without pairing, the headset seems to connect properly, but it doesn't route audio any more to the headset. Despite the headset being connected, audio is still routed to the integrated speaker. A reboot does not seem to help. The only way to get back to Bluetooth audio streaming is to delete the device from the settings, and pair it again, which makes it work once again. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1537737/+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 1590844] Re: Bluetooth headset not working with Meizu Pro 5 Ubuntu Edition
These ares different log I get after following the Debugging Bluetooth documentation. With the headset I used (a old one), I didn't get any sound or noise when doing a call with bluetooth I've tested the sound from music app and it worked well with no noise I will try to upload some others logs soon with an other headset or car bluetooth (with the noise) @ Konrad : I hope that I've following well the procedure. I've tried the headset one time without verbose logging (around 18.35 I think) and a second time after enable verbose logging (around 18.45 I think). I've got one error : impossible to edit /etc/init/ofono.override --> Read only file system (even if I used the sudo mount -o remount,rw /) See the attaches files Alexandre, ** Attachment added: "log-bug-1590844.tar" https://bugs.launchpad.net/canonical-devices-system-image/+bug/1590844/+attachment/4711722/+files/log-bug-1590844.tar -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1590844 Title: Bluetooth headset not working with Meizu Pro 5 Ubuntu Edition Status in Canonical System Image: Confirmed Status in turbo: Confirmed Status in bluez package in Ubuntu: Confirmed Bug description: My bluetooth headset perfectly connects to my Meizu Pro 5. However, the sound quality is so poor (a lot of noise) such that you don't understand your communication partner. Note that the headset works perfectly together with Ubuntu on my Nexus 4. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1590844/+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 1593919] Re: Bluetooth not working with Meizu Pro 5
** Also affects: turbo Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1593919 Title: Bluetooth not working with Meizu Pro 5 Status in turbo: New Status in bluez package in Ubuntu: Confirmed Bug description: I have problems with bluetooth. When I connect my Jabra Supreme headset, or connect with my car (Ford Fiesta), I only hear a lot of noise. This is both when I make a call, or receive an incoming call. I can hear music via bluetooth without problems on both headset, and in the car. To manage notifications about this bug go to: https://bugs.launchpad.net/turbo/+bug/1593919/+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 1593919] Re: Bluetooth not working with Meizu Pro 5
** Tags added: turbo -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1593919 Title: Bluetooth not working with Meizu Pro 5 Status in bluez package in Ubuntu: Confirmed Bug description: I have problems with bluetooth. When I connect my Jabra Supreme headset, or connect with my car (Ford Fiesta), I only hear a lot of noise. This is both when I make a call, or receive an incoming call. I can hear music via bluetooth without problems on both headset, and in the car. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1593919/+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 1560086] Re: cannot download files with no destination app from webapps
** Branch linked: lp:~abreu-alexandre/content-hub/types-per-app-id -- 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/1560086 Title: cannot download files with no destination app from webapps Status in Canonical System Image: Confirmed Status in Ubuntu UX: New Status in The Webapps-core project: New Status in webapps-sprint: In Progress Status in webbrowser-app package in Ubuntu: In Progress Bug description: Using the webbrowser-app I can download any file, and will be prompted to open in an app (if apps that support that content-type exist on the system) or to download the file in the browser. The same behavior should be available webapps but is not. Steps to reproduce: - Open Gmail webapp - Open a message that has an attachment of a file of unsupported type (like a .tar, .click, etc) - click on the file to download Expected results: - I should be prompted to open the file in supported app or to download - If I choose download the file should be downloaded into ~/Downloads by the webbrowser-app Actual results: - I am told that no apps exist to support this type of file and am not allowed to download it To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1560086/+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 1570828] Re: Multiple Web Apps crashes when returning from a linked page
here is a stack trace
Thread 1 "webapp-containe" received signal SIGSEGV, Segmentation fault.
0x7fffda2d3c3c in oxide::(anonymous namespace)::TryDispatchMessageToTarget
(target=target@entry=0x0, message=message@entry=0x1252790)
at ../../../oxide/shared/browser/oxide_script_message_contents_helper.cc:47
47for (size_t i = 0; i < target->GetScriptMessageHandlerCount(); ++i) {
(gdb) bt
#0 0x7fffda2d3c3c in oxide::(anonymous
namespace)::TryDispatchMessageToTarget (target=target@entry=0x0,
message=message@entry=0x1252790)
at ../../../oxide/shared/browser/oxide_script_message_contents_helper.cc:47
#1 0x7fffda2d3f53 in
oxide::ScriptMessageContentsHelper::OnReceiveScriptMessage (this=, message=..., render_frame_host=)
at ../../../oxide/shared/browser/oxide_script_message_contents_helper.cc:135
#2 0x7fffda2d4139 in oxide::ScriptMessageContentsHelper::OnMessageReceived
(this=, message=..., render_frame_host=)
at ../../../oxide/shared/browser/oxide_script_message_contents_helper.cc:159
#3 0x7fffd75d9f32 in content::WebContentsImpl::OnMessageReceived
(this=0x1246a20, render_view_host=0x0, render_frame_host=0x12060d0, message=...)
at ../../../content/browser/web_contents/web_contents_impl.cc:631
#4 0x7fffd73a9326 in content::RenderFrameHostImpl::OnMessageReceived
(this=0x12060d0, msg=...) at
../../../content/browser/frame_host/render_frame_host_impl.cc:539
#5 0x7fffd7504a97 in content::RenderProcessHostImpl::OnMessageReceived
(this=0xf6b6d0, msg=...) at
../../../content/browser/renderer_host/render_process_host_impl.cc:1772
#6 0x7fffd9bb9016 in IPC::ChannelProxy::Context::OnDispatchMessage
(this=0xe3dd90, message=...) at ../../../ipc/ipc_channel_proxy.cc:284
#7 0x7fffd928357d in base::Callback::Run() const (this=0x7fffd2c8) at
../../../base/callback.h:389
#8 base::debug::TaskAnnotator::RunTask (this=this@entry=0xd2daf0,
queue_function=queue_function@entry=0x7fffdad2b7b2 "MessageLoop::PostTask",
pending_task=...)
at ../../../base/debug/task_annotator.cc:51
#9 0x7fffd92a1cfe in base::MessageLoop::RunTask (this=this@entry=0xd2d970,
pending_task=...) at ../../../base/message_loop/message_loop.cc:493
#10 0x7fffd92a274d in base::MessageLoop::DeferOrRunPendingTask
(this=this@entry=0xd2d970, pending_task=...) at
../../../base/message_loop/message_loop.cc:502
#11 0x7fffd92a2a18 in base::MessageLoop::DoWork (this=0xd2d970) at
../../../base/message_loop/message_loop.cc:624
#12 0x7fffd6f8977b in oxide::qt::MessagePump::RunOneTask (this=0xd2d730) at
../../../oxide/qt/core/browser/oxide_qt_message_pump.cc:108
#13 0x7668be53 in QObject::event(QEvent*) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#14 0x778a505c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#15 0x778aa516 in QApplication::notify(QObject*, QEvent*) () from
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#16 0x7665c62b in QCoreApplication::notifyInternal(QObject*, QEvent*)
() from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#17 0x7665ea26 in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#18 0x766b2673 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#19 0x74cc91a7 in g_main_context_dispatch () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#20 0x74cc9400 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#21 0x74cc94ac in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#22 0x766b2a7f in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#23 0x76659dea in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#24 0x76661e8c in QCoreApplication::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#25 0x0043c156 in BrowserApplication::run() ()
#26 0x00420aeb in main ()
--
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/1570828
Title:
Multiple Web Apps crashes when returning from a linked page
Status in webapps-sprint:
In Progress
Status in webbrowser-app package in Ubuntu:
In Progress
Bug description:
This bug seems affect Twitter, Facebook and Gmail Web App, so it could
be a webbrowser bug. All of those apps crash when returning from a
linked page.
Steps to reproduce:
- Open Twitter/Facebook/Gmail web app
- On the Twitter/Facebook timeline or on an email, tap on a external link (a
web page, an article from a magazine, ...)
- A new external page pops up from the bottom
- _Magnify_ the text on the page / article
- Tap the button at the top left to return to Twitter/Facebook/Gmail app
- Twitter/Facebook/Gmail crashes instantly.
When you restart the
[Touch-packages] [Bug 1518686] Re: Saving pictures on SD card
Assigning it to the camera-app, since it does not seem to be a webapps problem. ** Also affects: camera-app (Ubuntu) Importance: Undecided Status: New ** Changed in: webapps-core Status: New => Invalid -- 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/1518686 Title: Saving pictures on SD card Status in The Webapps-core project: Invalid Status in camera-app package in Ubuntu: New Bug description: Pictures saved on the SD card was lost. This option in camera does not work and there is no warning. When you try to save on the card, the pictures are lost forever. To manage notifications about this bug go to: https://bugs.launchpad.net/webapps-core/+bug/1518686/+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 1599690] Re: [webapp-container] Overlay created as Popups should not have an "open in the webrowser" button
** Branch linked: lp:~abreu-alexandre/webbrowser-app/remove-open-in- browser-button-in-popups ** Changed in: webapps-sprint Status: Confirmed => In Progress ** Changed in: webbrowser-app (Ubuntu) Status: Confirmed => In Progress -- 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/1599690 Title: [webapp-container] Overlay created as Popups should not have an "open in the webrowser" button Status in webapps-sprint: In Progress Status in webbrowser-app package in Ubuntu: In Progress Bug description: In the webapp container, overlays can be created through a href with target="_blank" or or window.open, the latter usually being used to open a popup window. Those should be treated differently than the usual overlay since they should be considered as part of the website flow and might communicate with the original website through e.g. window.postMessage. For those overlays, it does not make much sense to have a "open in webbrowser" button at the top right. An example of those popups & windows can be found in here maps. 1. go to https://maps.here.com 2. click 'signin' 3. a new overlay is created with the Oxide.NavigationRequest.DispositionNewForegroundTab disposition, 4. if you click 'login with facebook' a new overlay is created but it is created with Oxide.NavigationRequest.DispositionNewPopup disposition and the website uses window.postMessage to handle the full duplex communication between the windows, To manage notifications about this bug go to: https://bugs.launchpad.net/webapps-sprint/+bug/1599690/+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 1560086] Re: cannot download files with no destination app from webapps
** Also affects: webapps-sprint Importance: Undecided Status: New ** Changed in: webapps-sprint Milestone: None => sprint-25 ** Changed in: webapps-sprint Assignee: (unassigned) => Alexandre Abreu (abreu-alexandre) ** Changed in: webapps-sprint Importance: Undecided => High ** Changed in: webapps-sprint Status: New => In Progress -- 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/1560086 Title: cannot download files with no destination app from webapps Status in Canonical System Image: Confirmed Status in Ubuntu UX: New Status in The Webapps-core project: New Status in webapps-sprint: In Progress Status in webbrowser-app package in Ubuntu: In Progress Bug description: Using the webbrowser-app I can download any file, and will be prompted to open in an app (if apps that support that content-type exist on the system) or to download the file in the browser. The same behavior should be available webapps but is not. Steps to reproduce: - Open Gmail webapp - Open a message that has an attachment of a file of unsupported type (like a .tar, .click, etc) - click on the file to download Expected results: - I should be prompted to open the file in supported app or to download - If I choose download the file should be downloaded into ~/Downloads by the webbrowser-app Actual results: - I am told that no apps exist to support this type of file and am not allowed to download it To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1560086/+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 1599695] Re: When running cmake from QtC on a webbrowser-app branch it fails
@Andrew: could you make sure that you select the right Generator in the Run CMake popup "Ubuntu SDK Desktop Kit" is the right one? -- 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/1599695 Title: When running cmake from QtC on a webbrowser-app branch it fails Status in webbrowser-app package in Ubuntu: Incomplete Bug description: When running cmake from QtC on a webbrowser-app branch in Xenial it fails with the following error: CMake Error at src/Ubuntu/CMakeLists.txt:31 (message): Invalid chromium version: '' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1599695/+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 1599695] Re: When running cmake from QtC on a webbrowser-app branch it fails
I run the same versions as you do, yes, I have qmlscene installed, and a local cmake . does work, -- 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/1599695 Title: When running cmake from QtC on a webbrowser-app branch it fails Status in webbrowser-app package in Ubuntu: Incomplete Bug description: When running cmake from QtC on a webbrowser-app branch in Xenial it fails with the following error: CMake Error at src/Ubuntu/CMakeLists.txt:31 (message): Invalid chromium version: '' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1599695/+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 1441547] Re: [HERE] Failed to create a HERE account
** Also affects: webapps-sprint Importance: Undecided Status: New ** Changed in: webapps-sprint Milestone: None => backlog -- 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/1441547 Title: [HERE] Failed to create a HERE account Status in Canonical System Image: Confirmed Status in The Savilerow project: Confirmed Status in webapps-sprint: New Status in webbrowser-app package in Ubuntu: Invalid Bug description: arale device, r165, ubuntu-touch/vivid-proposed Steps: 1. Launch HERE maps 2. Go to Settings -> Sign In 3. Tap on "Register for a HERE account" => Dropdown lists can't show and select (Day, Month, Year, Country) And can't continue to register account. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1441547/+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 1599695] Re: When running cmake from QtC on a webbrowser-app branch it fails
@Olivier: yes, I have. what's your QtC & Ubuntu plugin version? -- 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/1599695 Title: When running cmake from QtC on a webbrowser-app branch it fails Status in webbrowser-app package in Ubuntu: Incomplete Bug description: When running cmake from QtC on a webbrowser-app branch in Xenial it fails with the following error: CMake Error at src/Ubuntu/CMakeLists.txt:31 (message): Invalid chromium version: '' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1599695/+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 1599689] Re: [webapp-container] When sharing a photo to facebook, a "Ubuntu Web App" album is created and used as the target
** Also affects: webapps-core Importance: Undecided Status: New ** Changed in: webapps-core Assignee: (unassigned) => Alexandre Abreu (abreu-alexandre) ** Changed in: webapps-sprint Assignee: (unassigned) => Alexandre Abreu (abreu-alexandre) ** Changed in: webapps-core Importance: Undecided => Medium ** Changed in: webapps-sprint Importance: Undecided => Medium ** Changed in: webbrowser-app (Ubuntu) Importance: Undecided => Medium ** Changed in: webapps-core Status: New => Confirmed ** Changed in: webapps-sprint Status: New => Confirmed ** Changed in: webbrowser-app (Ubuntu) Status: New => Invalid ** No longer affects: webbrowser-app (Ubuntu) -- 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/1599689 Title: [webapp-container] When sharing a photo to facebook, a "Ubuntu Web App" album is created and used as the target Status in The Webapps-core project: Confirmed Status in webapps-sprint: Confirmed Bug description: When sharing a photo to facebook through the content hub, once the upload is successful, one can notice that the photo had been automatically added to an album called "Ubuntu Web App". It seems that the creator of the OAuth token (that acts on behalf of the user), is used as the name of the album for the upload. I couldn't find a reference in the graph API reference anything about that specific behavior: https://developers.facebook.com/docs/graph-api/reference/v2.6/photo This comes from a user report that also mentions a few extra elements that I havent noticed in my tests, here it is for reference: "When you upload a photo to facebook the web app adds a hyperlink with the text "Ubuntu Web App" which takes you to http://not.a.real.website.com/ which redirects you to Website.com." To manage notifications about this bug go to: https://bugs.launchpad.net/webapps-core/+bug/1599689/+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 1599695] [NEW] When running cmake from QtC on a webbrowser-app branch it fails
Public bug reported: When running cmake from QtC on a webbrowser-app branch in Xenial it fails with the following error: CMake Error at src/Ubuntu/CMakeLists.txt:31 (message): Invalid chromium version: '' ** Affects: webbrowser-app (Ubuntu) Importance: Undecided Status: New ** Description changed: - When running cmake from QtC on a webbrowser-app branch it fails with the - following error: + When running cmake from QtC on a webbrowser-app branch in Xenial it + fails with the following error: CMake Error at src/Ubuntu/CMakeLists.txt:31 (message): - Invalid chromium version: '' + Invalid chromium version: '' -- 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/1599695 Title: When running cmake from QtC on a webbrowser-app branch it fails Status in webbrowser-app package in Ubuntu: New Bug description: When running cmake from QtC on a webbrowser-app branch in Xenial it fails with the following error: CMake Error at src/Ubuntu/CMakeLists.txt:31 (message): Invalid chromium version: '' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1599695/+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
