[Touch-packages] [Bug 2062157] Re: kmod: FTBFS on arm{el, hf}: /usr/include/features-time64.h:26:5: error: #error "_TIME_BITS=64 is allowed only with _FILE_OFFSET_BITS=64"
** Merge proposal linked: https://code.launchpad.net/~zhsj/ubuntu/+source/kmod/+git/kmod/+merge/464608 -- 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/2062157 Title: kmod: FTBFS on arm{el,hf}: /usr/include/features-time64.h:26:5: error: #error "_TIME_BITS=64 is allowed only with _FILE_OFFSET_BITS=64" Status in kmod package in Ubuntu: New Status in kmod package in Debian: New Bug description: Imported from Debian bug http://bugs.debian.org/1065973: Source: kmod Version: 32-1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: sramac...@debian.org https://buildd.debian.org/status/fetch.php?pkg=kmod=armhf=32-1=1709960074=0 libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -include ./config.h -I.. -DSYSCONFDIR=\"/etc\" -DDISTCONFDIR=\"/usr/lib\" -DMODULE_DIRECTORY=\"/lib/modules\" -DABS_TOP_BUILDDIR=\"/<>/build-deb\" -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2 -pipe -DANOTHER_BRICK_IN_THE -Wall -W -Wextra -Wno-inline -Wvla -Wundef -Wformat=2 -Wlogical-op -Wsign-compare -Wmissing-include-dirs -Wold-style-definition -Wpointer-arith -Winit-self -Wdeclaration-after-statement -Wfloat-equal -Wmissing-prototypes -Wstrict-prototypes -Wredundant-decls -Wmissing-declarations -Wmissing-noreturn -Wshadow -Wendif-labels -Wstrict-aliasing=3 -Wwrite-strings -Wno-long-long -Wno-overlength-strings -Wno-unused-parameter -Wno-missing-field-initializers -Wno-unused-result -Wnested-externs -Wchar-subscripts -Wtype-limits -Wuninitialized -fno-common -fdiagnostics-show-option -fvisibility=hidden -ffunction-sections -fdata-sections -g -O2 -Werror=implicit-function-dec laration -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -c ../testsuite/path.c -fPIC -DPIC -o testsuite/.libs/path_la-path.o In file included from /usr/include/features.h:393, from /usr/include/assert.h:35, from ../testsuite/path.c:22: /usr/include/features-time64.h:26:5: error: #error "_TIME_BITS=64 is allowed only with _FILE_OFFSET_BITS=64" 26 | # error "_TIME_BITS=64 is allowed only with _FILE_OFFSET_BITS=64" | ^ Cheers -- Sebastian Ramacher To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kmod/+bug/2062157/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2062157] [NEW] kmod: FTBFS on arm{el, hf}: /usr/include/features-time64.h:26:5: error: #error "_TIME_BITS=64 is allowed only with _FILE_OFFSET_BITS=64"
Public bug reported: Imported from Debian bug http://bugs.debian.org/1065973: Source: kmod Version: 32-1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: sramac...@debian.org https://buildd.debian.org/status/fetch.php?pkg=kmod=armhf=32-1=1709960074=0 libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -include ./config.h -I.. -DSYSCONFDIR=\"/etc\" -DDISTCONFDIR=\"/usr/lib\" -DMODULE_DIRECTORY=\"/lib/modules\" -DABS_TOP_BUILDDIR=\"/<>/build-deb\" -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2 -pipe -DANOTHER_BRICK_IN_THE -Wall -W -Wextra -Wno-inline -Wvla -Wundef -Wformat=2 -Wlogical-op -Wsign-compare -Wmissing-include-dirs -Wold-style-definition -Wpointer-arith -Winit-self -Wdeclaration-after-statement -Wfloat-equal -Wmissing-prototypes -Wstrict-prototypes -Wredundant-decls -Wmissing-declarations -Wmissing-noreturn -Wshadow -Wendif-labels -Wstrict-aliasing=3 -Wwrite-strings -Wno-long-long -Wno-overlength-strings -Wno-unused-parameter -Wno-missing-field-initializers -Wno-unused-result -Wnested-externs -Wchar-subscripts -Wtype-limits -Wuninitialized -fno-common -fdiagnostics-show-option -fvisibility=hidden -ffunction-sections -fdata-sections -g -O2 -Werror=implicit-function-decla ration -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -c ../testsuite/path.c -fPIC -DPIC -o testsuite/.libs/path_la-path.o In file included from /usr/include/features.h:393, from /usr/include/assert.h:35, from ../testsuite/path.c:22: /usr/include/features-time64.h:26:5: error: #error "_TIME_BITS=64 is allowed only with _FILE_OFFSET_BITS=64" 26 | # error "_TIME_BITS=64 is allowed only with _FILE_OFFSET_BITS=64" | ^ Cheers -- Sebastian Ramacher ** Affects: kmod (Ubuntu) Importance: Undecided Status: New ** Affects: kmod (Debian) Importance: Undecided Status: New ** Tags: ftbfs ** Bug watch added: Debian Bug tracker #1065973 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065973 ** Changed in: kmod (Debian) Remote watch: None => Debian Bug tracker #1065973 ** Tags added: ftbfs -- 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/2062157 Title: kmod: FTBFS on arm{el,hf}: /usr/include/features-time64.h:26:5: error: #error "_TIME_BITS=64 is allowed only with _FILE_OFFSET_BITS=64" Status in kmod package in Ubuntu: New Status in kmod package in Debian: New Bug description: Imported from Debian bug http://bugs.debian.org/1065973: Source: kmod Version: 32-1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: sramac...@debian.org https://buildd.debian.org/status/fetch.php?pkg=kmod=armhf=32-1=1709960074=0 libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -include ./config.h -I.. -DSYSCONFDIR=\"/etc\" -DDISTCONFDIR=\"/usr/lib\" -DMODULE_DIRECTORY=\"/lib/modules\" -DABS_TOP_BUILDDIR=\"/<>/build-deb\" -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2 -pipe -DANOTHER_BRICK_IN_THE -Wall -W -Wextra -Wno-inline -Wvla -Wundef -Wformat=2 -Wlogical-op -Wsign-compare -Wmissing-include-dirs -Wold-style-definition -Wpointer-arith -Winit-self -Wdeclaration-after-statement -Wfloat-equal -Wmissing-prototypes -Wstrict-prototypes -Wredundant-decls -Wmissing-declarations -Wmissing-noreturn -Wshadow -Wendif-labels -Wstrict-aliasing=3 -Wwrite-strings -Wno-long-long -Wno-overlength-strings -Wno-unused-parameter -Wno-missing-field-initializers -Wno-unused-result -Wnested-externs -Wchar-subscripts -Wtype-limits -Wuninitialized -fno-common -fdiagnostics-show-option -fvisibility=hidden -ffunction-sections -fdata-sections -g -O2 -Werror=implicit-function-dec laration -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -c ../testsuite/path.c -fPIC -DPIC -o testsuite/.libs/path_la-path.o In file included from /usr/include/features.h:393, from /usr/include/assert.h:35, from ../testsuite/path.c:22: /usr/include/features-time64.h:26:5: error: #error "_TIME_BITS=64 is allowed only with _FILE_OFFSET_BITS=64" 26 | # error "_TIME_BITS=64 is allowed only with _FILE_OFFSET_BITS=64" | ^ Cheers -- Sebastian Ramacher To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kmod/+bug/2062157/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2059417] Re: Sync xz-utils 5.6.1-1 (main) from Debian unstable (main)
It's reverted in Debian https://tracker.debian.org/news/1515519/accepted-xz- utils-561really545-1-source-into-unstable/ Though from the changelog I didn't see the reason. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xz-utils in Ubuntu. https://bugs.launchpad.net/bugs/2059417 Title: Sync xz-utils 5.6.1-1 (main) from Debian unstable (main) Status in xz-utils package in Ubuntu: New Bug description: Please sync xz-utils 5.6.1-1 (main) from Debian unstable (main) Hello! I am one of the upstream maintainers for XZ Utils. Version 5.6.1 was recently released and uploaded to Debian as a bugfix only release. Notably, this fixes a bug that causes Valgrind to issue a warning on any application dynamically linked with liblzma. This includes a lot of important applications. This could break build scripts and test pipelines that expect specific output from Valgrind in order to pass. Additionally, this fixes a small typo for the man pages translations for Brazilian Portuguese, German, French, Korean, Romanian, and Ukrainian, and removes the need for patches applied for version 5.6.0-0.2. The other bugfixes in this release have no impact on Ubuntu. They involve building with CMake or when building on a system without Landlock system calls defined (these are defined in Ubuntu). Changelog entries since current noble version 5.6.0-0.2: xz-utils (5.6.1-1) unstable; urgency=medium * Non-maintainer upload. * Import 5.6.1 (Closes: #1067708). * Takeover maintenance of the package. -- Sebastian Andrzej Siewior Wed, 27 Mar 2024 22:53:21 +0100 Excerpt from the NEWS entry from upstream: 5.6.1 (2024-03-09) * liblzma: Fixed two bugs relating to GNU indirect function (IFUNC) with GCC. The more serious bug caused a program linked with liblzma to crash on start up if the flag -fprofile-generate was used to build liblzma. The second bug caused liblzma to falsely report an invalid write to Valgrind when loading liblzma. * xz: Changed the messages for thread reduction due to memory constraints to only appear under the highest verbosity level. * Build: - Fixed a build issue when the header file was present on the system but the Landlock system calls were not defined in . - The CMake build now warns and disables NLS if both gettext tools and pre-created .gmo files are missing. Previously, this caused the CMake build to fail. * Minor improvements to man pages. * Minor improvements to tests. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xz-utils/+bug/2059417/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2017076] Re: default Chinese font in snap apps is ugly
> The first screenshot after the description is one from firefox showing an issue, reading the comments my understanding is that the report was about the firefox issue which has been resolved now Yes :) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fontconfig in Ubuntu. https://bugs.launchpad.net/bugs/2017076 Title: default Chinese font in snap apps is ugly Status in Snappy: Confirmed Status in fontconfig package in Ubuntu: Invalid Status in language-selector package in Ubuntu: Invalid Bug description: After installs Ubuntu 23.04 with Chinese language selected, the default font is chosen to AR PL UMing CN, which is very ugly. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: fontconfig 2.14.1-3ubuntu3 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CloudArchitecture: x86_64 CloudID: none CloudName: none CloudPlatform: none CloudSubPlatform: config CurrentDesktop: ubuntu:GNOME Date: Thu Apr 20 14:18:45 2023 InstallationDate: Installed on 2023-04-20 (0 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) ProcEnviron: LANG=zh_CN.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: fontconfig UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/2017076/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2020749] Re: Please merge console-setup 1.221 into mantic
PPA for review https://launchpad.net/~zhsj/+archive/ubuntu/console- setup-merge-lp2020749 ** Changed in: console-setup (Ubuntu) Status: New => In Progress ** Merge proposal linked: https://code.launchpad.net/~zhsj/ubuntu/+source/console-setup/+git/console-setup/+merge/443641 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/2020749 Title: Please merge console-setup 1.221 into mantic Status in console-setup package in Ubuntu: In Progress Bug description: console-setup (1.221) unstable; urgency=medium * Team upload. [ Updated translations ] * Belarusian (be.po) by Viktar Siarheichyk * Bengali (bn.po) by Indrani Roy * Norwegian Nynorsk (nn.po) by Yngve Spjeld-Landro console-setup (1.220) unstable; urgency=medium * Team upload. [ Updated translations ] * Norwegian Bokmal (nb.po) by Kjetil Sørlund * Norwegian Nynorsk (nn.po) by Kjetil Sørlund console-setup (1.219) unstable; urgency=medium [ Updated translations ] * Georgian (ka.po) by Temuri Doghonadze console-setup (1.218) unstable; urgency=medium * Team upload. [ Updated translations ] * German (de.po) by Holger Wansing * Vietnamese (vi.po) by tictactoe To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/2020749/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2020749] Re: Please merge console-setup 1.221 into mantic
** Merge proposal linked: https://code.launchpad.net/~zhsj/ubuntu/+source/console-setup/+git/console-setup/+merge/443584 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/2020749 Title: Please merge console-setup 1.221 into mantic Status in console-setup package in Ubuntu: New Bug description: console-setup (1.221) unstable; urgency=medium * Team upload. [ Updated translations ] * Belarusian (be.po) by Viktar Siarheichyk * Bengali (bn.po) by Indrani Roy * Norwegian Nynorsk (nn.po) by Yngve Spjeld-Landro console-setup (1.220) unstable; urgency=medium * Team upload. [ Updated translations ] * Norwegian Bokmal (nb.po) by Kjetil Sørlund * Norwegian Nynorsk (nn.po) by Kjetil Sørlund console-setup (1.219) unstable; urgency=medium [ Updated translations ] * Georgian (ka.po) by Temuri Doghonadze console-setup (1.218) unstable; urgency=medium * Team upload. [ Updated translations ] * German (de.po) by Holger Wansing * Vietnamese (vi.po) by tictactoe To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/2020749/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2020749] [NEW] Please merge console-setup 1.221 into mantic
Public bug reported: console-setup (1.221) unstable; urgency=medium * Team upload. [ Updated translations ] * Belarusian (be.po) by Viktar Siarheichyk * Bengali (bn.po) by Indrani Roy * Norwegian Nynorsk (nn.po) by Yngve Spjeld-Landro console-setup (1.220) unstable; urgency=medium * Team upload. [ Updated translations ] * Norwegian Bokmal (nb.po) by Kjetil Sørlund * Norwegian Nynorsk (nn.po) by Kjetil Sørlund console-setup (1.219) unstable; urgency=medium [ Updated translations ] * Georgian (ka.po) by Temuri Doghonadze console-setup (1.218) unstable; urgency=medium * Team upload. [ Updated translations ] * German (de.po) by Holger Wansing * Vietnamese (vi.po) by tictactoe ** Affects: console-setup (Ubuntu) Importance: Undecided Assignee: Shengjing Zhu (zhsj) Status: New ** Changed in: console-setup (Ubuntu) Assignee: (unassigned) => Shengjing Zhu (zhsj) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/2020749 Title: Please merge console-setup 1.221 into mantic Status in console-setup package in Ubuntu: New Bug description: console-setup (1.221) unstable; urgency=medium * Team upload. [ Updated translations ] * Belarusian (be.po) by Viktar Siarheichyk * Bengali (bn.po) by Indrani Roy * Norwegian Nynorsk (nn.po) by Yngve Spjeld-Landro console-setup (1.220) unstable; urgency=medium * Team upload. [ Updated translations ] * Norwegian Bokmal (nb.po) by Kjetil Sørlund * Norwegian Nynorsk (nn.po) by Kjetil Sørlund console-setup (1.219) unstable; urgency=medium [ Updated translations ] * Georgian (ka.po) by Temuri Doghonadze console-setup (1.218) unstable; urgency=medium * Team upload. [ Updated translations ] * German (de.po) by Holger Wansing * Vietnamese (vi.po) by tictactoe To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/2020749/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2017076] Re: default Chinese font in snap apps is ugly
Oh, I miss that the lunar desktop image installs firefox snap from latest/stable/ubuntu-23.04 branch. So, if I install firefox from latest/stable channel (which uses core20), then Noto CJK is rightfully selected. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fontconfig in Ubuntu. https://bugs.launchpad.net/bugs/2017076 Title: default Chinese font in snap apps is ugly Status in Snappy: New Status in fontconfig package in Ubuntu: New Status in language-selector package in Ubuntu: New Bug description: After installs Ubuntu 23.04 with Chinese language selected, the default font is chosen to AR PL UMing CN, which is very ugly. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: fontconfig 2.14.1-3ubuntu3 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CloudArchitecture: x86_64 CloudID: none CloudName: none CloudPlatform: none CloudSubPlatform: config CurrentDesktop: ubuntu:GNOME Date: Thu Apr 20 14:18:45 2023 InstallationDate: Installed on 2023-04-20 (0 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) ProcEnviron: LANG=zh_CN.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: fontconfig UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/2017076/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2017076] Re: default Chinese font in snap apps is ugly
@seb128, I think you mean esr/stable channel? esr channel which uses core20 is using Noto font. See the attachment. ** Attachment added: "screenshot" https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/2017076/+attachment/5666489/+files/2023-04-22_00-34.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fontconfig in Ubuntu. https://bugs.launchpad.net/bugs/2017076 Title: default Chinese font in snap apps is ugly Status in Snappy: New Status in fontconfig package in Ubuntu: New Status in language-selector package in Ubuntu: New Bug description: After installs Ubuntu 23.04 with Chinese language selected, the default font is chosen to AR PL UMing CN, which is very ugly. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: fontconfig 2.14.1-3ubuntu3 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CloudArchitecture: x86_64 CloudID: none CloudName: none CloudPlatform: none CloudSubPlatform: config CurrentDesktop: ubuntu:GNOME Date: Thu Apr 20 14:18:45 2023 InstallationDate: Installed on 2023-04-20 (0 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) ProcEnviron: LANG=zh_CN.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: fontconfig UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/2017076/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2017076] Re: default Chinese font is ugly
@Gunnar Hjalmarsson: I have attached the screenshot at https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/2017076/comments/2 + Both Firefox and snap-store are displayed with UMing + The webpage in Firefox is displayed with UMing + Non-snap applications uses Noto ** Summary changed: - default Chinese font is ugly + default Chinese font in snap apps is ugly -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fontconfig in Ubuntu. https://bugs.launchpad.net/bugs/2017076 Title: default Chinese font in snap apps is ugly Status in fontconfig package in Ubuntu: Incomplete Bug description: After installs Ubuntu 23.04 with Chinese language selected, the default font is chosen to AR PL UMing CN, which is very ugly. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: fontconfig 2.14.1-3ubuntu3 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CloudArchitecture: x86_64 CloudID: none CloudName: none CloudPlatform: none CloudSubPlatform: config CurrentDesktop: ubuntu:GNOME Date: Thu Apr 20 14:18:45 2023 InstallationDate: Installed on 2023-04-20 (0 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) ProcEnviron: LANG=zh_CN.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: fontconfig UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/2017076/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2017076] Re: default Chinese font is ugly
Hi, indeed I forget the store is also snap. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fontconfig in Ubuntu. https://bugs.launchpad.net/bugs/2017076 Title: default Chinese font is ugly Status in fontconfig package in Ubuntu: New Bug description: After installs Ubuntu 23.04 with Chinese language selected, the default font is chosen to AR PL UMing CN, which is very ugly. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: fontconfig 2.14.1-3ubuntu3 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CloudArchitecture: x86_64 CloudID: none CloudName: none CloudPlatform: none CloudSubPlatform: config CurrentDesktop: ubuntu:GNOME Date: Thu Apr 20 14:18:45 2023 InstallationDate: Installed on 2023-04-20 (0 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) ProcEnviron: LANG=zh_CN.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: fontconfig UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/2017076/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2017076] Re: default Chinese font is ugly
We should let Noto CJK has higher priority. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fontconfig in Ubuntu. https://bugs.launchpad.net/bugs/2017076 Title: default Chinese font is ugly Status in fontconfig package in Ubuntu: New Bug description: After installs Ubuntu 23.04 with Chinese language selected, the default font is chosen to AR PL UMing CN, which is very ugly. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: fontconfig 2.14.1-3ubuntu3 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CloudArchitecture: x86_64 CloudID: none CloudName: none CloudPlatform: none CloudSubPlatform: config CurrentDesktop: ubuntu:GNOME Date: Thu Apr 20 14:18:45 2023 InstallationDate: Installed on 2023-04-20 (0 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) ProcEnviron: LANG=zh_CN.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: fontconfig UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/2017076/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2017076] Re: default Chinese font is ugly
** Attachment added: "screenshot" https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/2017076/+attachment/5665408/+files/2023-04-20_14-14.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fontconfig in Ubuntu. https://bugs.launchpad.net/bugs/2017076 Title: default Chinese font is ugly Status in fontconfig package in Ubuntu: New Bug description: After installs Ubuntu 23.04 with Chinese language selected, the default font is chosen to AR PL UMing CN, which is very ugly. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: fontconfig 2.14.1-3ubuntu3 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CloudArchitecture: x86_64 CloudID: none CloudName: none CloudPlatform: none CloudSubPlatform: config CurrentDesktop: ubuntu:GNOME Date: Thu Apr 20 14:18:45 2023 InstallationDate: Installed on 2023-04-20 (0 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) ProcEnviron: LANG=zh_CN.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: fontconfig UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/2017076/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2017076] [NEW] default Chinese font is ugly
Public bug reported: After installs Ubuntu 23.04 with Chinese language selected, the default font is chosen to AR PL UMing CN, which is very ugly. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: fontconfig 2.14.1-3ubuntu3 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CloudArchitecture: x86_64 CloudID: none CloudName: none CloudPlatform: none CloudSubPlatform: config CurrentDesktop: ubuntu:GNOME Date: Thu Apr 20 14:18:45 2023 InstallationDate: Installed on 2023-04-20 (0 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) ProcEnviron: LANG=zh_CN.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: fontconfig UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: fontconfig (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lunar wayland-session -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fontconfig in Ubuntu. https://bugs.launchpad.net/bugs/2017076 Title: default Chinese font is ugly Status in fontconfig package in Ubuntu: New Bug description: After installs Ubuntu 23.04 with Chinese language selected, the default font is chosen to AR PL UMing CN, which is very ugly. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: fontconfig 2.14.1-3ubuntu3 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CloudArchitecture: x86_64 CloudID: none CloudName: none CloudPlatform: none CloudSubPlatform: config CurrentDesktop: ubuntu:GNOME Date: Thu Apr 20 14:18:45 2023 InstallationDate: Installed on 2023-04-20 (0 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) ProcEnviron: LANG=zh_CN.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: fontconfig UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/2017076/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2016950] Re: ubuntu 23.o4 新安装ssh默认端口修改不成功
Since ubuntu 22.10, openssh-server uses socket activation. You can read more at /usr/share/doc/openssh-server/README.Debian.gz Copying here: Socket-based activation with systemd By default, socket-based activation is used on systems that use systemd. The provided ssh.socket unit file sets ListenStream=22. If you need to have it listen on a different address or port, then you will need to do this as follows (modifying ListenStream to match your requirements): mkdir -p /etc/systemd/system/ssh.socket.d cat >/etc/systemd/system/ssh.socket.d/listen.conf < openssh (Ubuntu) ** Changed in: openssh (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/2016950 Title: ubuntu 23.o4 新安装ssh默认端口修改不成功 Status in openssh package in Ubuntu: Invalid Bug description: ubuntu 23.04新安装的系统,安装openssh-server 后,修改默认22端口不成功。 ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: ubuntu-release-upgrader-core 1:23.04.5 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Wed Apr 19 13:01:31 2023 InstallationDate: Installed on 2022-01-02 (471 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211105) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: Upgraded to lunar on 2022-11-12 (158 days ago) VarLogDistupgradeXorgFixuplog: INFO:root:/usr/bin/do-release-upgrade running INFO:root:No xorg.conf, exiting mtime.conffile..etc.update-manager.release-upgrades: 2022-11-13T20:00:56.608141 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2016950/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2016596] Re: Unit sshd.service could not be found
Ha, ok. Just documented here that I'm in trouble with this since I have some legacy scripts with `service sshd restart`... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/2016596 Title: Unit sshd.service could not be found Status in openssh package in Ubuntu: Invalid Bug description: Despite ssh.service has an Alias for sshd.service, but systemd reports "Unit sshd.service could not be found". ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: openssh-server 1:9.0p1-1ubuntu8 ProcVersionSignature: Ubuntu 6.2.0-1003.3-kvm 6.2.6 Uname: Linux 6.2.0-1003-kvm x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CloudArchitecture: x86_64 CloudBuildName: server CloudID: lxd CloudName: lxd CloudPlatform: lxd CloudSerial: 20230414 CloudSubPlatform: LXD socket API v. 1.0 (/dev/lxd/sock) Date: Mon Apr 17 11:00:23 2023 ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) TERM=xterm-256color SourcePackage: openssh UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2016596/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2016596] [NEW] Unit sshd.service could not be found
Public bug reported: Despite ssh.service has an Alias for sshd.service, but systemd reports "Unit sshd.service could not be found". ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: openssh-server 1:9.0p1-1ubuntu8 ProcVersionSignature: Ubuntu 6.2.0-1003.3-kvm 6.2.6 Uname: Linux 6.2.0-1003-kvm x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CloudArchitecture: x86_64 CloudBuildName: server CloudID: lxd CloudName: lxd CloudPlatform: lxd CloudSerial: 20230414 CloudSubPlatform: LXD socket API v. 1.0 (/dev/lxd/sock) Date: Mon Apr 17 11:00:23 2023 ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) TERM=xterm-256color SourcePackage: openssh UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: openssh (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cloud-image lunar -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/2016596 Title: Unit sshd.service could not be found Status in openssh package in Ubuntu: New Bug description: Despite ssh.service has an Alias for sshd.service, but systemd reports "Unit sshd.service could not be found". ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: openssh-server 1:9.0p1-1ubuntu8 ProcVersionSignature: Ubuntu 6.2.0-1003.3-kvm 6.2.6 Uname: Linux 6.2.0-1003-kvm x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CloudArchitecture: x86_64 CloudBuildName: server CloudID: lxd CloudName: lxd CloudPlatform: lxd CloudSerial: 20230414 CloudSubPlatform: LXD socket API v. 1.0 (/dev/lxd/sock) Date: Mon Apr 17 11:00:23 2023 ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) TERM=xterm-256color SourcePackage: openssh UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2016596/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2015778] Re: conffile prompt during release upgrade
/etc/gprofng.rc is not conffile in kinetic... -- 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/2015778 Title: conffile prompt during release upgrade Status in binutils package in Ubuntu: New Status in binutils source package in Lunar: New Bug description: I was upgrading from Kinetic to Lunar today and received a question about a configuration file I had not touched. Setting up binutils-common:amd64 (2.40-2ubuntu3) ...^M ^M Configuration file '/etc/gprofng.rc'^M ==> File on system created by you or by a script.^M ==> File also in package provided by package maintainer.^M What would you like to do about it ? Your options are:^M Y or I : install the package maintainer's version^M N or O : keep your currently-installed version^M D : show the differences between the versions^M Z : start a shell to examine the situation^M The default action is to keep your current version.^M *** gprofng.rc (Y/I/N/O/D/Z) [default=N] ? d^M ^[[?1h^[=^M--- /etc/gprofng.rc 2022-12-01 03:11:36.0 -0800^[[m^M +++ /etc/gprofng.rc.dpkg-new2023-03-05 00:47:46.0 -0800^[[m^M @@ -1,4 +1,4 @@^[[m^M -# Copyright (C) 2021 Free Software Foundation, Inc.^[[m^M +# Copyright (C) 2021-2023 Free Software Foundation, Inc.^[[m^M #^[[m^M # This file is free software; you can redistribute it and/or modify^[[m^M # it under the terms of the GNU General Public License as published by^[[m^M ^M^[[K^[[?1l^[>^M Configuration file '/etc/gprofng.rc'^M ==> File on system created by you or by a script.^M ==> File also in package provided by package maintainer.^M What would you like to do about it ? Your options are:^M Y or I : install the package maintainer's version^M N or O : keep your currently-installed version^M D : show the differences between the versions^M Z : start a shell to examine the situation^M The default action is to keep your current version.^M *** gprofng.rc (Y/I/N/O/D/Z) [default=N] ? i^M Installing new version of config file /etc/gprofng.rc ...^M To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/2015778/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1567744] Re: USB NICs get too long name for ifupdown aliases or bridge names
I don't understand why this is a won't fix bug. If users pick a long NIC name by themselves, then it's users' responsibility to fix it. But apparently this is not the case, it's an unexpected behavior caused by internal conflicts of different linux components. -- 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/1567744 Title: USB NICs get too long name for ifupdown aliases or bridge names Status in systemd package in Ubuntu: Won't Fix Bug description: I have a USB NIC that is connected to my denial system. I tried to create an alias, and after reboot, it wasn't created. When I manually try to bring it up I have the error. /e/n/i: auto enx000ec688b79f iface enx000ec688b79f inet static address 10.90.90.1 netmask 255.255.255.0 auto enx000ec688b79f:1 iface enx000ec688b79f:1 inet static address 192.168.100.1 netmask 255.255.255.0 ubuntu@maas00:~$ sudo ifup enx000ec688b79f ubuntu@maas00:~$ sudo ifup enx000ec688b79f:1 RTNETLINK answers: Numerical result out of range Failed to bring up enx000ec688b79f:1. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1567744/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1922025] [NEW] package initramfs-tools 0.136ubuntu6.3 failed to install/upgrade: 已安装 initramfs-tools 软件包 post-installation 脚本 子进程返回错误状态 1
Public bug reported: linux-image-5.8.0-48-generic also appear in the error list. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: initramfs-tools 0.136ubuntu6.3 ProcVersionSignature: Ubuntu 5.8.0-48.54~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-48-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Mar 31 16:19:59 2021 ErrorMessage: 已安装 initramfs-tools 软件包 post-installation 脚本 子进程返回错误状态 1 InstallationDate: Installed on 2021-02-16 (43 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.4 SourcePackage: initramfs-tools Title: package initramfs-tools 0.136ubuntu6.3 failed to install/upgrade: 已安装 initramfs-tools 软件包 post-installation 脚本 子进程返回错误状态 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package 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/1922025 Title: package initramfs-tools 0.136ubuntu6.3 failed to install/upgrade: 已安装 initramfs-tools 软件包 post-installation 脚本 子进程返回错误状态 1 Status in initramfs-tools package in Ubuntu: New Bug description: linux-image-5.8.0-48-generic also appear in the error list. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: initramfs-tools 0.136ubuntu6.3 ProcVersionSignature: Ubuntu 5.8.0-48.54~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-48-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Mar 31 16:19:59 2021 ErrorMessage: 已安装 initramfs-tools 软件包 post-installation 脚本 子进程返回错误状态 1 InstallationDate: Installed on 2021-02-16 (43 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.4 SourcePackage: initramfs-tools Title: package initramfs-tools 0.136ubuntu6.3 failed to install/upgrade: 已安装 initramfs-tools 软件包 post-installation 脚本 子进程返回错误状态 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/1922025/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1746582] Re: package lvm2 2.02.176-4.1ubuntu2 failed to install/upgrade: installed lvm2 package post-installation script subprocess returned error exit status 1
Thanks to Yevhen (yevhen.b) I fixed it by sudo apt purge lvm2 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1746582 Title: package lvm2 2.02.176-4.1ubuntu2 failed to install/upgrade: installed lvm2 package post-installation script subprocess returned error exit status 1 Status in lvm2 package in Ubuntu: Confirmed Bug description: I *think* this was from trying to install python-guestfs ProblemType: Package DistroRelease: Ubuntu 18.04 Package: lvm2 2.02.176-4.1ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.8-0ubuntu7 Architecture: amd64 Date: Wed Jan 31 09:56:36 2018 ErrorMessage: installed lvm2 package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2017-06-28 (217 days ago) InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) Python3Details: /usr/bin/python3.6, Python 3.6.4, python3-minimal, 3.6.4-1 PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4 RelatedPackageVersions: dpkg 1.19.0.5ubuntu1 apt 1.6~alpha7ubuntu1 SourcePackage: lvm2 Title: package lvm2 2.02.176-4.1ubuntu2 failed to install/upgrade: installed lvm2 package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to bionic on 2018-01-30 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1746582/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1838229] Re: ppd updating unexpectedly after printing job finished
This problem makes the settings of the driver UI saving failed and inconvenient to users. Please tell us the reasons for this problem in order to solve the problem. And our PPD file contains repetitive KeyWords as below, we wonder if it is the reason of the problem. Please confirm and We are looking forward for your reply. PPD Files Detail(repetitive KeyWords of "RIBlack","RICyan", "RIMagenta", "RIYellow") --- *PJLINQ RIBlack: "GAMMAK" *PJLINQ RICyan: "GAMMAC" *PJLINQ RIMagenta: "GAMMAM" *PJLINQ RIYellow: "GAMMAY" *SNMPOID RIBlack: ".1.3.6.1.4.1.367.3.2.1.2.18.2.1.7.1.1" *SNMPOID RICyan: ".1.3.6.1.4.1.367.3.2.1.2.18.2.1.7.1.2" *SNMPOID RIMagenta: ".1.3.6.1.4.1.367.3.2.1.2.18.2.1.7.1.3" *SNMPOID RIYellow: ".1.3.6.1.4.1.367.3.2.1.2.18.2.1.7.1.4" ... *OpenGroup: AdjustColorDensity/Adjust Color Density *OpenUI *RICyan/C: PickOne *OrderDependency: 130 AnySetup *RICyan *DefaultRICyan: 1 ※ppd loading target keyword(expected result) *RICyan 1/1: "%% RICyan=1" *RICyan 2/2: "%% RICyan=2" *RICyan 3/3: "%% RICyan=3" *RICyan 4/4: "%% RICyan=4" *RICyan 5/5: "%% RICyan=5" *RICyan 6/6: "%% RICyan=6" *RICyan 7/7: "%% RICyan=7" *RICyan 8/8: "%% RICyan=8" *RICyan 9/9: "%% RICyan=9" *CloseUI: *RICyan *OpenUI *RIMagenta/M: PickOne *OrderDependency: 130 AnySetup *RIMagenta *DefaultRIMagenta: 1 ※ppd loading target keyword(expected result) *RIMagenta 1/1: "%% RIMagenta=1" *RIMagenta 2/2: "%% RIMagenta=2" *RIMagenta 3/3: "%% RIMagenta=3" *RIMagenta 4/4: "%% RIMagenta=4" *RIMagenta 5/5: "%% RIMagenta=5" *RIMagenta 6/6: "%% RIMagenta=6" *RIMagenta 7/7: "%% RIMagenta=7" *RIMagenta 8/8: "%% RIMagenta=8" *RIMagenta 9/9: "%% RIMagenta=9" *CloseUI: *RIMagenta *OpenUI *RIYellow/Y: PickOne *OrderDependency: 130 AnySetup *RIYellow *DefaultRIYellow: 1 ※ppd loading target keyword(expected result) *RIYellow 1/1: "%% RIYellow=1" *RIYellow 2/2: "%% RIYellow=2" *RIYellow 3/3: "%% RIYellow=3" *RIYellow 4/4: "%% RIYellow=4" *RIYellow 5/5: "%% RIYellow=5" *RIYellow 6/6: "%% RIYellow=6" *RIYellow 7/7: "%% RIYellow=7" *RIYellow 8/8: "%% RIYellow=8" *RIYellow 9/9: "%% RIYellow=9" *CloseUI: *RIYellow *OpenUI *RIBlack/K: PickOne *OrderDependency: 130 AnySetup *RIBlack *DefaultRIBlack: 1 ※ppd loading target keyword(expected result) *RIBlack 1/1: "%% RIBlack=1" *RIBlack 2/2: "%% RIBlack=2" *RIBlack 3/3: "%% RIBlack=3" *RIBlack 4/4: "%% RIBlack=4" *RIBlack 5/5: "%% RIBlack=5" *RIBlack 6/6: "%% RIBlack=6" *RIBlack 7/7: "%% RIBlack=7" *RIBlack 8/8: "%% RIBlack=8" *RIBlack 9/9: "%% RIBlack=9" *CloseUI: *RIBlack *CloseGroup: AdjustColorDensity ... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1838229 Title: ppd updating unexpectedly after printing job finished Status in cups package in Ubuntu: New Bug description: Ubuntu 16.04LTS OS Version: 16.04.5 CUPS Version: 2.1.3 Ghostscript Version: 9.18 ppd updating unexpectedly after printing job finished We(RICOH printer driver developer) got a bug report from the users of our printer: We changed the UI setting(DefaultRICyan, DefaultRIMagenta, DefaultRIYellow, DefaultRIBlack) of the RICOH driver. And confirmed the PPD setting(DefaultRICyan, DefaultRIMagenta, DefaultRIYellow, DefaultRIBlack) in etc/cups/ppds/.ppd was changed correctly before printing. When the printing job completed, We expected the PPD file is same with the one before printing. But after printing job completed, a part of setting in etc/cups/ppds/.ppd(DefaultRICyan, DefaultRIMagenta, DefaultRIYellow, DefaultRIBlack) was changed unexpectedly. It seems be changed to the value in /usr/share/ppd/ricoh/.ppd. According to the "CUPS Error Log" and the open source of CUPS, it seems that CUPS Updated the PPD Setting after the printing job. We doubt that CUPS didn't find a part of the keyword we changed in the PPD file. Error Log == D [19/Jul/2019:19:05:52 +0800] cupsdSetBusyState: newbusy="Printing jobs and dirty files", busy="Active clients, printing jobs, and dirty files" D [19/Jul/2019:19:05:52 +0800] [Job 2] PID 2714 (/usr/lib/cups/filter/gstoraster) exited with no errors. D [19/Jul/2019:19:05:52 +0800] [Job 2] CUPS_SC_CMD_SNMP_GET_NEXT: 25 (.1.3.6.1.2.1.43.8.2.1.13) D [19/Jul/2019:19:05:52 +0800] [Job 2] Returning .1.3.6.1.2.1.43.8.2.1.13.1.1 D [19/Jul/2019:19:05:52 +0800] [Job 2] CUPS_SC_CMD_SNMP_GET_NEXT: 29 (.1.3.6.1.2.1.43.8.2.1.13.1.1) D [19/Jul/2019:19:05:52 +0800] [Job 2] Returning .1.3.6.1.2.1.43.8.2.1.14.1.1 1 D [19/Jul/2019:19:05:52 +0800] [Job 2] CUPS_SC_CMD_SNMP_GET_NEXT: 25 (.1.3.6.1.2.1.43.8.2.1.13) D [19/Jul/2019:19:05:52 +0800] [Job 2] Returning .1.3.6.1.2.1.43.8.2.1.13.1.1 D [19/Jul/2019:19:05:52 +0800] [Job 2] CUPS_SC_CMD_SNMP_GET_NEXT: 29
[Touch-packages] [Bug 1838229] [NEW] ppd updating unexpectedly after printing job finished
Public bug reported: Ubuntu 16.04LTS OS Version: 16.04.5 CUPS Version: 2.1.3 Ghostscript Version: 9.18 ppd updating unexpectedly after printing job finished We(RICOH printer driver developer) got a bug report from the users of our printer: We changed the UI setting(DefaultRICyan, DefaultRIMagenta, DefaultRIYellow, DefaultRIBlack) of the RICOH driver. And confirmed the PPD setting(DefaultRICyan, DefaultRIMagenta, DefaultRIYellow, DefaultRIBlack) in etc/cups/ppds/.ppd was changed correctly before printing. When the printing job completed, We expected the PPD file is same with the one before printing. But after printing job completed, a part of setting in etc/cups/ppds/.ppd(DefaultRICyan, DefaultRIMagenta, DefaultRIYellow, DefaultRIBlack) was changed unexpectedly. It seems be changed to the value in /usr/share/ppd/ricoh/.ppd. According to the "CUPS Error Log" and the open source of CUPS, it seems that CUPS Updated the PPD Setting after the printing job. We doubt that CUPS didn't find a part of the keyword we changed in the PPD file. Error Log == D [19/Jul/2019:19:05:52 +0800] cupsdSetBusyState: newbusy="Printing jobs and dirty files", busy="Active clients, printing jobs, and dirty files" D [19/Jul/2019:19:05:52 +0800] [Job 2] PID 2714 (/usr/lib/cups/filter/gstoraster) exited with no errors. D [19/Jul/2019:19:05:52 +0800] [Job 2] CUPS_SC_CMD_SNMP_GET_NEXT: 25 (.1.3.6.1.2.1.43.8.2.1.13) D [19/Jul/2019:19:05:52 +0800] [Job 2] Returning .1.3.6.1.2.1.43.8.2.1.13.1.1 D [19/Jul/2019:19:05:52 +0800] [Job 2] CUPS_SC_CMD_SNMP_GET_NEXT: 29 (.1.3.6.1.2.1.43.8.2.1.13.1.1) D [19/Jul/2019:19:05:52 +0800] [Job 2] Returning .1.3.6.1.2.1.43.8.2.1.14.1.1 1 D [19/Jul/2019:19:05:52 +0800] [Job 2] CUPS_SC_CMD_SNMP_GET_NEXT: 25 (.1.3.6.1.2.1.43.8.2.1.13) D [19/Jul/2019:19:05:52 +0800] [Job 2] Returning .1.3.6.1.2.1.43.8.2.1.13.1.1 D [19/Jul/2019:19:05:52 +0800] [Job 2] CUPS_SC_CMD_SNMP_GET_NEXT: 29 (.1.3.6.1.2.1.43.8.2.1.13.1.1) D [19/Jul/2019:19:05:52 +0800] [Job 2] Returning .1.3.6.1.2.1.43.8.2.1.14.1.1 1 D [19/Jul/2019:19:05:52 +0800] [Job 2] CUPS_SC_CMD_SNMP_GET_NEXT: 34 (.1.3.6.1.4.1.367.3.2.1.2.11.3.1.2) D [19/Jul/2019:19:05:52 +0800] [Job 2] Returning .1.3.6.1.4.1.367.3.2.1.2.11.3.1.2.1 D [19/Jul/2019:19:05:52 +0800] [Job 2] CUPS_SC_CMD_SNMP_GET_NEXT: 36 (.1.3.6.1.4.1.367.3.2.1.2.11.3.1.2.1) D [19/Jul/2019:19:05:52 +0800] [Job 2] Returning .1.3.6.1.4.1.367.3.2.1.2.11.3.1.2.2 D [19/Jul/2019:19:05:52 +0800] [Job 2] CUPS_SC_CMD_SNMP_GET_NEXT: 36 (.1.3.6.1.4.1.367.3.2.1.2.11.3.1.2.2) D [19/Jul/2019:19:05:52 +0800] [Job 2] Returning .1.3.6.1.4.1.367.3.2.1.2.13.3.0 D [19/Jul/2019:19:05:52 +0800] [Job 2] CUPS_SC_CMD_SNMP_GET: 38 (.1.3.6.1.4.1.367.3.2.1.2.18.2.1.7.1.1) D [19/Jul/2019:19:05:52 +0800] [Job 2] Returning .1.3.6.1.4.1.367.3.2.1.2.18.2.1.7.1.1 6 D [19/Jul/2019:19:05:52 +0800] [Job 2] PPD: DefaultRIBlack=5※ppd loading unexpectedly D [19/Jul/2019:19:05:52 +0800] [Job 2] CUPS_SC_CMD_SNMP_GET: 38 (.1.3.6.1.4.1.367.3.2.1.2.18.2.1.7.1.2) D [19/Jul/2019:19:05:52 +0800] [Job 2] Returning .1.3.6.1.4.1.367.3.2.1.2.18.2.1.7.1.2 6 D [19/Jul/2019:19:05:52 +0800] [Job 2] PPD: DefaultRICyan=5※ppd loading unexpectedly D [19/Jul/2019:19:05:52 +0800] [Job 2] CUPS_SC_CMD_SNMP_GET: 38 (.1.3.6.1.4.1.367.3.2.1.2.18.2.1.7.1.3) D [19/Jul/2019:19:05:52 +0800] [Job 2] Returning .1.3.6.1.4.1.367.3.2.1.2.18.2.1.7.1.3 6 D [19/Jul/2019:19:05:52 +0800] [Job 2] PPD: DefaultRIMagenta=5 ※ppd loading unexpectedly D [19/Jul/2019:19:05:52 +0800] [Job 2] CUPS_SC_CMD_SNMP_GET: 38 (.1.3.6.1.4.1.367.3.2.1.2.18.2.1.7.1.4) D [19/Jul/2019:19:05:52 +0800] [Job 2] Returning .1.3.6.1.4.1.367.3.2.1.2.18.2.1.7.1.4 6 D [19/Jul/2019:19:05:52 +0800] [Job 2] PPD: DefaultRIYellow=5 ※ppd loading unexpectedly D [19/Jul/2019:19:05:52 +0800] [Job 2] Waiting for status monitor to stop D [19/Jul/2019:19:05:53 +0800] [Job 2] Status monitor stopped D [19/Jul/2019:19:05:53 +0800] [Job 2] Job finished ... I [19/Jul/2019:19:05:53 +0800] Expiring subscriptions... D [19/Jul/2019:19:05:53 +0800] cupsdMarkDirty(---J-) D [19/Jul/2019:19:05:53 +0800] cupsdSetBusyState: newbusy="Printing jobs and dirty files", busy="Printing jobs and dirty files" D [19/Jul/2019:19:05:53 +0800] cupsdSetBusyState: newbusy="Printing jobs and dirty files", busy="Printing jobs and dirty files" D [19/Jul/2019:19:05:53 +0800] cupsdMarkDirty(S) D [19/Jul/2019:19:05:53 +0800] cupsdSetBusyState: newbusy="Printing jobs and dirty files", busy="Printing jobs and dirty files" D [19/Jul/2019:19:05:53 +0800] cupsdMarkDirty(---J-) D [19/Jul/2019:19:05:53 +0800] cupsdSetBusyState: newbusy="Printing jobs and dirty files", busy="Printing jobs and dirty files" D [19/Jul/2019:19:05:53 +0800] cupsdMarkDirty(---J-) D [19/Jul/2019:19:05:53 +0800] cupsdSetBusyState: newbusy="Printing jobs and dirty files", busy="Printing jobs and dirty files" I [19/Jul/2019:19:05:53 +0800] Updating keywords in PPD file for
[Touch-packages] [Bug 1835596] [NEW] incorrect argument to file_printable in [PATCH] PR/62
Public bug reported: In last patch below +From d65781527c8134a1202b2649695d48d5701ac60b Mon Sep 17 00:00:00 2001 +From: Christos Zoulas +Date: Mon, 18 Feb 2019 17:46:56 + +Subject: [PATCH] PR/62: spinpx: limit size of file_printable. +=== +--- file-5.32.orig/src/readelf.c 2019-03-13 12:38:58.854781641 -0400 file-5.32/src/readelf.c2019-03-13 12:39:43.450945506 -0400 +@@ -725,7 +725,7 @@ do_core_note(struct magic_set *ms, unsig + if (file_printf(ms, ", from '%.31s', pid=%u, uid=%u, " + "gid=%u, nlwps=%u, lwp=%u (signal %u/code %u)", + file_printable(sbuf, sizeof(sbuf), +- CAST(char *, pi.cpi_name)), ++ RCAST(char *, pi.cpi_name), sizeof(pi.cpi_name)), + elf_getu32(swap, pi.cpi_pid), + elf_getu32(swap, pi.cpi_euid), + elf_getu32(swap, pi.cpi_egid), +@@ -1564,7 +1564,8 @@ dophn_exec(struct magic_set *ms, int cla + return -1; + if (interp[0]) + if (file_printf(ms, ", interpreter %s", +- file_printable(ibuf, sizeof(ibuf), interp)) == -1) ++ file_printable(ibuf, sizeof(ibuf), interp, sizeof(interp))) ++ == -1) + return -1; + return 0; + } sizeof(interp) is passed to file_printable as the `slen' parameter, since interp is of type `char *', sizeof(interp) will be 8 or 4 const value for different pointer types, this makes the `interpreter' extraction for elf file limited to 8 bytes under x64. A example for this, under ubuntu 18.04: $ file /bin/dash /bin/dash: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/l, for GNU/Linux 3.2.0, BuildID[sha1]=a783260e3a5fe0afdae77417eea7f bf8d645219e, stripped notice that the interpreter portion is `/lib64/l', which is 8 bytes long and only a part of the actual interpreter path. the `slen' parameter here should be something like `sizeof(char) * length_of_buffer' instead of sizeof(char *). ** Affects: file (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to file in Ubuntu. https://bugs.launchpad.net/bugs/1835596 Title: incorrect argument to file_printable in [PATCH] PR/62 Status in file package in Ubuntu: New Bug description: In last patch below +From d65781527c8134a1202b2649695d48d5701ac60b Mon Sep 17 00:00:00 2001 +From: Christos Zoulas +Date: Mon, 18 Feb 2019 17:46:56 + +Subject: [PATCH] PR/62: spinpx: limit size of file_printable. +=== +--- file-5.32.orig/src/readelf.c 2019-03-13 12:38:58.854781641 -0400 file-5.32/src/readelf.c 2019-03-13 12:39:43.450945506 -0400 +@@ -725,7 +725,7 @@ do_core_note(struct magic_set *ms, unsig + if (file_printf(ms, ", from '%.31s', pid=%u, uid=%u, " + "gid=%u, nlwps=%u, lwp=%u (signal %u/code %u)", + file_printable(sbuf, sizeof(sbuf), +-CAST(char *, pi.cpi_name)), ++RCAST(char *, pi.cpi_name), sizeof(pi.cpi_name)), + elf_getu32(swap, pi.cpi_pid), + elf_getu32(swap, pi.cpi_euid), + elf_getu32(swap, pi.cpi_egid), +@@ -1564,7 +1564,8 @@ dophn_exec(struct magic_set *ms, int cla + return -1; + if (interp[0]) + if (file_printf(ms, ", interpreter %s", +-file_printable(ibuf, sizeof(ibuf), interp)) == -1) ++file_printable(ibuf, sizeof(ibuf), interp, sizeof(interp))) ++== -1) + return -1; + return 0; + } sizeof(interp) is passed to file_printable as the `slen' parameter, since interp is of type `char *', sizeof(interp) will be 8 or 4 const value for different pointer types, this makes the `interpreter' extraction for elf file limited to 8 bytes under x64. A example for this, under ubuntu 18.04: $ file /bin/dash /bin/dash: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/l, for GNU/Linux 3.2.0, BuildID[sha1]=a783260e3a5fe0afdae77417eea7f bf8d645219e, stripped notice that the interpreter portion is `/lib64/l', which is 8 bytes long and only a part of the actual interpreter path. the `slen' parameter here should be something like `sizeof(char) * length_of_buffer' instead of sizeof(char *). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/file/+bug/1835596/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages
[Touch-packages] [Bug 1771757] [NEW] Ubuntu doesn't detect device on USB 3.1 Gen 2 port
Public bug reported: Ubuntu does't detect the device when I plug a USB Flash drive onto the USB 3.1 Gen 2 port on my motherboard. I can't find the device in lsusb output. If I reboot the system with the drive plugged, I can mount the drive in file manager. If I unplug and plug it again, Ubuntu doesn't detect the device. My motherboard is ASUS ROG STRIX B360-G. Tried stock bionic and latest v4.16/v4.17 mainline kernels. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 Uname: Linux 4.16.9-041609-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: KDE Date: Thu May 17 15:19:47 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: kubuntu DkmsStatus: virtualbox, 5.2.10, 4.15.0-20-generic, x86_64: installed virtualbox, 5.2.10, 4.16.9-041609-generic, x86_64: installed ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Baffin [Polaris11] [1002:67ff] (rev cf) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Baffin [Radeon RX 560] [1043:04be] InstallationDate: Installed on 2018-03-03 (74 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180303) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.16.9-041609-generic root=UUID=3fd33ecf-eee9-442d-b5e6-8c9e4344b643 ro resume=UUID=3fd33ecf-eee9-442d-b5e6-8c9e4344b643 resume_offset=34816 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/23/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0602 dmi.board.asset.tag: Default string dmi.board.name: ROG STRIX B360-G GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0602:bd03/23/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXB360-GGAMING:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 ** Affects: ubuntu Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic kubuntu ** Package changed: xorg (Ubuntu) => ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1771757 Title: Ubuntu doesn't detect device on USB 3.1 Gen 2 port Status in Ubuntu: New Bug description: Ubuntu does't detect the device when I plug a USB Flash drive onto the USB 3.1 Gen 2 port on my motherboard. I can't find the device in lsusb output. If I reboot the system with the drive plugged, I can mount the drive in file manager. If I unplug and plug it again, Ubuntu doesn't detect the device. My motherboard is ASUS ROG STRIX B360-G. Tried stock bionic and latest v4.16/v4.17 mainline kernels. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 Uname: Linux 4.16.9-041609-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: KDE Date: Thu May 17 15:19:47 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: kubuntu DkmsStatus: virtualbox, 5.2.10, 4.15.0-20-generic, x86_64: installed virtualbox, 5.2.10, 4.16.9-041609-generic, x86_64: installed ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Baffin [Polaris11] [1002:67ff] (rev cf) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Baffin [Radeon RX 560] [1043:04be] InstallationDate: Installed on 2018-03-03 (74 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180303) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.16.9-041609-generic root=UUID=3fd33ecf-eee9-442d-b5e6-8c9e4344b643 ro resume=UUID=3fd33ecf-eee9-442d-b5e6-8c9e4344b643 resume_offset=34816 SourcePackage:
Re: [Touch-packages] [Bug 1752938] Re: Upgrading Ubuntu 18.04 disables GPU hardware acceleration
The original bug I reported was a duplicate of bug #1751414. It has been fixed. Lately I've upgraded from 17.10 to 18.08 for my laptop. I don't have this issue. My laptop has Intel GPU though. On Sun, 29 Apr 2018, 2:15 am Patyrk Zajdler, <1752...@bugs.launchpad.net> wrote: > I'm experiencing the same issue - no hardware acceleration. > > I have an askubuntu.com question open with plenty of information and logs. > > https://askubuntu.com/questions/1029205/video-playback-performance-issue-ubuntu-18-04 > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1752938 > > Title: > Upgrading Ubuntu 18.04 disables GPU hardware acceleration > > Status in xorg package in Ubuntu: > Confirmed > > Bug description: > I don't know which package causes this problem. The thing is ugrading > Ubuntu 18.04 disables my GPU hardware acceleration. > > glxinfo_before_upgrade > OpenGL vendor string: X.Org > OpenGL renderer string: Radeon RX 560 Series (POLARIS11 / DRM 3.23.0 / > 4.15.0-10-generic, LLVM 5.0.1) > OpenGL core profile version string: 4.5 (Core Profile) Mesa 17.3.3 > > glxinfo_after_upgrade > OpenGL vendor string: VMware, Inc. > OpenGL renderer string: llvmpipe (LLVM 5.0, 256 bits) > OpenGL core profile version string: 3.3 (Core Profile) Mesa 17.3.3 > > This problem is reproducible. > > Steps to reproduce: > 1. Install Ubuntu 18.04 daily live. I've tried Kubuntu 18.04 Feb 26's > daily live(the installer in Mar 1 crashes which prevents me from installing > it) and Xubuntu 18.04 Mar 2's daily live. Ubuntu is utilizing my GPU in > live cd session and after the fresh install Ubuntu is also utilizing my GPU. > 2. Reboot into the newly installed system, do a dist-upgrade and reboot > again. Opengl renderer falls back to llvmpipe. > > ProblemType: Bug > DistroRelease: Ubuntu 18.04 > Package: xorg 1:7.7+19ubuntu5 > ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 > Uname: Linux 4.15.0-10-generic x86_64 > ApportVersion: 2.20.8-0ubuntu10 > Architecture: amd64 > BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' > CompositorRunning: None > CurrentDesktop: XFCE > Date: Sat Mar 3 00:58:35 2018 > DistUpgraded: Fresh install > DistroCodename: bionic > DistroVariant: ubuntu > ExtraDebuggingInterest: Yes, if not too technical > GraphicsCard: >Advanced Micro Devices, Inc. [AMD/ATI] Baffin [Polaris11] [1002:67ff] > (rev cf) (prog-if 00 [VGA controller]) > Subsystem: ASUSTeK Computer Inc. Baffin [Radeon RX 560] [1043:04be] > InstallationDate: Installed on 2018-03-02 (0 days ago) > InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 > (20180302) > MachineType: Gigabyte Technology Co., Ltd. B85M-D3V-A > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic.efi.signed > root=UUID=d2dcc7eb-84ca-4102-9ae1-239de26d113c ro quiet splash vt.handoff=1 > Renderer: Software > SourcePackage: xorg > Symptom: display > UpgradeStatus: No upgrade log present (probably fresh install) > dmi.bios.date: 02/12/2015 > dmi.bios.vendor: American Megatrends Inc. > dmi.bios.version: F2 > dmi.board.asset.tag: To be filled by O.E.M. > dmi.board.name: B85M-D3V-A > dmi.board.vendor: Gigabyte Technology Co., Ltd. > dmi.board.version: x.x > dmi.chassis.asset.tag: To Be Filled By O.E.M. > dmi.chassis.type: 3 > dmi.chassis.vendor: Gigabyte Technology Co., Ltd. > dmi.chassis.version: To Be Filled By O.E.M. > dmi.modalias: > dmi:bvnAmericanMegatrendsInc.:bvrF2:bd02/12/2015:svnGigabyteTechnologyCo.,Ltd.:pnB85M-D3V-A:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnB85M-D3V-A:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: > dmi.product.family: To be filled by O.E.M. > dmi.product.name: B85M-D3V-A > dmi.product.version: To be filled by O.E.M. > dmi.sys.vendor: Gigabyte Technology Co., Ltd. > version.compiz: compiz N/A > version.libdrm2: libdrm2 2.4.90-1 > version.libgl1-mesa-dri: libgl1-mesa-dri 17.3.3-0ubuntu1 > version.libgl1-mesa-glx: libgl1-mesa-glx 17.3.3-0ubuntu1 > version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu2 > version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A > version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 > version.xserver-xorg-video-intel: xserver-xorg-video-intel > 2:2.99.917+git20171229-1 > version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1752938/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1752938 Title: Upgrading Ubuntu 18.04 disables GPU hardware acceleration Status in xorg package in Ubuntu: Confirmed Bug description: I don't know which package causes this
[Touch-packages] [Bug 1752938] [NEW] Upgrading Ubuntu 18.04 disables GPU hardware acceleration
Public bug reported: I don't know which package causes this problem. The thing is ugrading Ubuntu 18.04 disables my GPU hardware acceleration. glxinfo_before_upgrade OpenGL vendor string: X.Org OpenGL renderer string: Radeon RX 560 Series (POLARIS11 / DRM 3.23.0 / 4.15.0-10-generic, LLVM 5.0.1) OpenGL core profile version string: 4.5 (Core Profile) Mesa 17.3.3 glxinfo_after_upgrade OpenGL vendor string: VMware, Inc. OpenGL renderer string: llvmpipe (LLVM 5.0, 256 bits) OpenGL core profile version string: 3.3 (Core Profile) Mesa 17.3.3 This problem is reproducible. Steps to reproduce: 1. Install Ubuntu 18.04 daily live. I've tried Kubuntu 18.04 Feb 26's daily live(the installer in Mar 1 crashes which prevents me from installing it) and Xubuntu 18.04 Mar 2's daily live. Ubuntu is utilizing my GPU in live cd session and after the fresh install Ubuntu is also utilizing my GPU. 2. Reboot into the newly installed system, do a dist-upgrade and reboot again. Opengl renderer falls back to llvmpipe. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: XFCE Date: Sat Mar 3 00:58:35 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Baffin [Polaris11] [1002:67ff] (rev cf) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Baffin [Radeon RX 560] [1043:04be] InstallationDate: Installed on 2018-03-02 (0 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180302) MachineType: Gigabyte Technology Co., Ltd. B85M-D3V-A ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic.efi.signed root=UUID=d2dcc7eb-84ca-4102-9ae1-239de26d113c ro quiet splash vt.handoff=1 Renderer: Software SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/12/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B85M-D3V-A dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF2:bd02/12/2015:svnGigabyteTechnologyCo.,Ltd.:pnB85M-D3V-A:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnB85M-D3V-A:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: B85M-D3V-A dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.90-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.3.3-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 17.3.3-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic reproducible single-occurrence ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1752938 Title: Upgrading Ubuntu 18.04 disables GPU hardware acceleration Status in xorg package in Ubuntu: New Bug description: I don't know which package causes this problem. The thing is ugrading Ubuntu 18.04 disables my GPU hardware acceleration. glxinfo_before_upgrade OpenGL vendor string: X.Org OpenGL renderer string: Radeon RX 560 Series (POLARIS11 / DRM 3.23.0 / 4.15.0-10-generic, LLVM 5.0.1) OpenGL core profile version string: 4.5 (Core Profile) Mesa 17.3.3 glxinfo_after_upgrade OpenGL vendor string: VMware, Inc. OpenGL renderer string: llvmpipe (LLVM 5.0, 256 bits) OpenGL core profile version string: 3.3 (Core Profile) Mesa 17.3.3 This problem is reproducible. Steps to reproduce: 1. Install Ubuntu 18.04 daily live. I've tried Kubuntu 18.04 Feb 26's daily live(the installer in Mar 1 crashes which prevents me from installing it) and Xubuntu 18.04 Mar 2's daily live. Ubuntu is utilizing my GPU in live cd session and after the fresh install Ubuntu is also utilizing my GPU. 2. Reboot into the newly installed system, do a dist-upgrade and reboot again. Opengl renderer falls back to llvmpipe. ProblemType: Bug DistroRelease: Ubuntu 18.04
[Touch-packages] [Bug 1583801] Re: No sound via headphones (headset) when Ubuntu boots with them plugged in
It turns out I run into another problem. Pluseaudio doesn't prefer headphone in some cases, have to select headphone manually for once to fix it. Anyway the bug doesn't affect kernel v4.15. -- 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/1583801 Title: No sound via headphones (headset) when Ubuntu boots with them plugged in Status in alsa-driver package in Ubuntu: Confirmed Bug description: The bug is twofold, first when computer boots if the headset (headphones with built-in mic, one audio jack) is plugged in, then there is no sound (via headphones or otherwise). If you plug headphones out and back in, then it usually works as expected. The second scenario is the same, except that plugging out and back in again doesn't help. In that case, I just restart the laptop, then plug them back in again and it works. In all cases, microphone works. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: crunch 3248 F pulseaudio CurrentDesktop: Unity Date: Thu May 19 22:13:20 2016 InstallationDate: Installed on 2016-05-07 (12 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: crunch 3248 F pulseaudio Symptom_Jack: Black Headphone Out, Left Symptom_Type: No sound at all Title: [XPS 15 9550, Realtek ALC3266, Black Headphone Out, Left] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/07/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.02.00 dmi.board.name: 0N7TVV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 15 9550 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1583801/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1583801] Re: No sound via headphones (headset) when Ubuntu boots with them plugged in
uhh, well. I don't have this problem with kernel v4.14. After I upgrade to kernel v4.15-rc8, I run into this again. -- 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/1583801 Title: No sound via headphones (headset) when Ubuntu boots with them plugged in Status in alsa-driver package in Ubuntu: Confirmed Bug description: The bug is twofold, first when computer boots if the headset (headphones with built-in mic, one audio jack) is plugged in, then there is no sound (via headphones or otherwise). If you plug headphones out and back in, then it usually works as expected. The second scenario is the same, except that plugging out and back in again doesn't help. In that case, I just restart the laptop, then plug them back in again and it works. In all cases, microphone works. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: crunch 3248 F pulseaudio CurrentDesktop: Unity Date: Thu May 19 22:13:20 2016 InstallationDate: Installed on 2016-05-07 (12 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: crunch 3248 F pulseaudio Symptom_Jack: Black Headphone Out, Left Symptom_Type: No sound at all Title: [XPS 15 9550, Realtek ALC3266, Black Headphone Out, Left] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/07/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.02.00 dmi.board.name: 0N7TVV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 15 9550 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1583801/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1583801] Re: No sound via headphones (headset) when Ubuntu boots with them plugged in
I have this problem on Dell Inspiron 7370(Realtek ALC3254) when using Xubuntu 17.10(4.13 kernel). After upgrading to Ubuntu mainline kernel 4.14, the problem seems gone. -- 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/1583801 Title: No sound via headphones (headset) when Ubuntu boots with them plugged in Status in alsa-driver package in Ubuntu: Confirmed Bug description: The bug is twofold, first when computer boots if the headset (headphones with built-in mic, one audio jack) is plugged in, then there is no sound (via headphones or otherwise). If you plug headphones out and back in, then it usually works as expected. The second scenario is the same, except that plugging out and back in again doesn't help. In that case, I just restart the laptop, then plug them back in again and it works. In all cases, microphone works. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: crunch 3248 F pulseaudio CurrentDesktop: Unity Date: Thu May 19 22:13:20 2016 InstallationDate: Installed on 2016-05-07 (12 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: crunch 3248 F pulseaudio Symptom_Jack: Black Headphone Out, Left Symptom_Type: No sound at all Title: [XPS 15 9550, Realtek ALC3266, Black Headphone Out, Left] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/07/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.02.00 dmi.board.name: 0N7TVV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 15 9550 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1583801/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1647526] [NEW] [Ubuntu phone]Display error in language page.
Public bug reported: Information: system-image-cli -i current build number: 485 device name: krillin channel: ubuntu-touch/rc-proposed/bq-aquaris.en last update: 2016-12-05 16:23:15 version version: 485 version ubuntu: 20161203 version device: 20160606-ab415b2 version custom: 20160831-991-38-18 Step: 1.New flash device and boot the phone 2.In language page, scroll up to the top 3.Check the language list of "C" Actual reuslt: It's only shows the "C" captical.(Please see the attachment.) Expect result: Should be a language. ** Affects: ubuntu-ui-toolkit (Ubuntu) Importance: Undecided Status: New ** Attachment added: "screenshot20161205_084924989.png" https://bugs.launchpad.net/bugs/1647526/+attachment/4787831/+files/screenshot20161205_084924989.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1647526 Title: [Ubuntu phone]Display error in language page. Status in ubuntu-ui-toolkit package in Ubuntu: New Bug description: Information: system-image-cli -i current build number: 485 device name: krillin channel: ubuntu-touch/rc-proposed/bq-aquaris.en last update: 2016-12-05 16:23:15 version version: 485 version ubuntu: 20161203 version device: 20160606-ab415b2 version custom: 20160831-991-38-18 Step: 1.New flash device and boot the phone 2.In language page, scroll up to the top 3.Check the language list of "C" Actual reuslt: It's only shows the "C" captical.(Please see the attachment.) Expect result: Should be a language. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1647526/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1647295] [NEW] Can not Send / Receive MMS.
Public bug reported: Information: system-image-cli -i current build number: 485 device name: krillin channel: ubuntu-touch/rc-proposed/bq-aquaris.en last update: 2016-12-05 16:23:15 version version: 485 version ubuntu: 20161203 version device: 20160606-ab415b2 version custom: 20160831-991-38-18 Issue 1: Between Ubuntu deveice send/receive MMS. Step: 1.DUT open message app and edit a MMS 2.Send the MMS to other ubuntu device Actual result: Can not send and receive MMS on both side. ~ Issue 2: Between ubuntu device and ios/android device send/receive MMS Step: 1.Ubuntu device open message app and edit a MMS 2.Send the MMS to ios/android device 3.ios/android device edit a MMS and send it to ubuntu device Actual result: After step 2, the ubuntu device display "Failed!" on message page, but ios/android device can receive MMS successful. After step 3, send successfully on ios/android device. but the ubuntu device can not receive the MMS. ** Affects: messaging-app (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to messaging-app in Ubuntu. https://bugs.launchpad.net/bugs/1647295 Title: Can not Send / Receive MMS. Status in messaging-app package in Ubuntu: New Bug description: Information: system-image-cli -i current build number: 485 device name: krillin channel: ubuntu-touch/rc-proposed/bq-aquaris.en last update: 2016-12-05 16:23:15 version version: 485 version ubuntu: 20161203 version device: 20160606-ab415b2 version custom: 20160831-991-38-18 Issue 1: Between Ubuntu deveice send/receive MMS. Step: 1.DUT open message app and edit a MMS 2.Send the MMS to other ubuntu device Actual result: Can not send and receive MMS on both side. ~ Issue 2: Between ubuntu device and ios/android device send/receive MMS Step: 1.Ubuntu device open message app and edit a MMS 2.Send the MMS to ios/android device 3.ios/android device edit a MMS and send it to ubuntu device Actual result: After step 2, the ubuntu device display "Failed!" on message page, but ios/android device can receive MMS successful. After step 3, send successfully on ios/android device. but the ubuntu device can not receive the MMS. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/messaging-app/+bug/1647295/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1644643] [NEW] apt failed to run due to link time reference error
Public bug reported: After update apt and its related library to 1.2.15 from 1.2.10ubuntu1, I get following message when I try to invoke apt: apt-get: relocation error: /usr/lib/x86_64-linux-gnu/libapt- private.so.0.0: symbol _ZlsRSoRKN3APT9PrettyPkgE, version APTPKG_5.0 not defined in file libapt-pkg.so.5.0 with link time reference 1.2.10 do not have this problem. Now I manually downgrade from 1.2.15 to 1.2.10 to solve this problem. Ubuntu release: Description:Ubuntu 16.04.1 LTS Release:16.04 what I expect to happen: apt would show the helper message what happened instead: apt shows me the line on above ** Affects: apt (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1644643 Title: apt failed to run due to link time reference error Status in apt package in Ubuntu: New Bug description: After update apt and its related library to 1.2.15 from 1.2.10ubuntu1, I get following message when I try to invoke apt: apt-get: relocation error: /usr/lib/x86_64-linux-gnu/libapt- private.so.0.0: symbol _ZlsRSoRKN3APT9PrettyPkgE, version APTPKG_5.0 not defined in file libapt-pkg.so.5.0 with link time reference 1.2.10 do not have this problem. Now I manually downgrade from 1.2.15 to 1.2.10 to solve this problem. Ubuntu release: Description: Ubuntu 16.04.1 LTS Release: 16.04 what I expect to happen: apt would show the helper message what happened instead: apt shows me the line on above To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1644643/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1643777] [NEW] [phone] Enable flight mode, the cellular data indicator still be ON in settings.
Public bug reported: Information: phablet@ubuntu-phablet:~$ system-image-cli -i current build number: 22 device name: turbo channel: ubuntu-touch/rc/meizu-pd.en last update: 2016-11-21 16:17:17 version version: 22 version ubuntu: 20161118 version device: 20160824-d33b825 version custom: 20160831-992-8-12 Precondition: SIM cards inserted. Step: 1.Go to system settings, and enable flight mode 2.Go to Cellular settings Panel, and check the cellular data indicator. Actual result: Enable flight mode, the cellular data indicator still be ON. Expect result: The cellular data indicator should be OFF. Related test case: https://prod.practitest.com/p/1548/qtest_runs/6921297/edit ** Affects: indicator-network (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-network in Ubuntu. https://bugs.launchpad.net/bugs/1643777 Title: [phone] Enable flight mode, the cellular data indicator still be ON in settings. Status in indicator-network package in Ubuntu: New Bug description: Information: phablet@ubuntu-phablet:~$ system-image-cli -i current build number: 22 device name: turbo channel: ubuntu-touch/rc/meizu-pd.en last update: 2016-11-21 16:17:17 version version: 22 version ubuntu: 20161118 version device: 20160824-d33b825 version custom: 20160831-992-8-12 Precondition: SIM cards inserted. Step: 1.Go to system settings, and enable flight mode 2.Go to Cellular settings Panel, and check the cellular data indicator. Actual result: Enable flight mode, the cellular data indicator still be ON. Expect result: The cellular data indicator should be OFF. Related test case: https://prod.practitest.com/p/1548/qtest_runs/6921297/edit To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1643777/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1636352] [NEW] [Turbo]Screen flash several times when set flash ON to take photo.
Public bug reported: Information: phablet@ubuntu-phablet:~$ system-image-cli -i current build number: 207 device name: turbo channel: ubuntu-touch/rc-proposed/meizu-pd.en last update: 2014-01-01 20:08:53 version version: 207 version ubuntu: 20161022 version device: 20160824-d33b825 version custom: 20160831-992-8-12 Precondition: This issue only happened on Turbo device. Step: 1. Open Camera app 2. Swipe up from the bottom, tap on the flash and set to "ON" 3. Press the screen to get focus and check the screen flash Actual result: Screen flash several times when get focus. Expect result: Get focus without screen flash. (Can compare with Krillin phenomenon.) ** Affects: qtubuntu-camera (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtubuntu-camera in Ubuntu. https://bugs.launchpad.net/bugs/1636352 Title: [Turbo]Screen flash several times when set flash ON to take photo. Status in qtubuntu-camera package in Ubuntu: New Bug description: Information: phablet@ubuntu-phablet:~$ system-image-cli -i current build number: 207 device name: turbo channel: ubuntu-touch/rc-proposed/meizu-pd.en last update: 2014-01-01 20:08:53 version version: 207 version ubuntu: 20161022 version device: 20160824-d33b825 version custom: 20160831-992-8-12 Precondition: This issue only happened on Turbo device. Step: 1. Open Camera app 2. Swipe up from the bottom, tap on the flash and set to "ON" 3. Press the screen to get focus and check the screen flash Actual result: Screen flash several times when get focus. Expect result: Get focus without screen flash. (Can compare with Krillin phenomenon.) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtubuntu-camera/+bug/1636352/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1634066] [NEW] Screen black when take video with rear camera to send MMS.
Public bug reported: Information: phablet@ubuntu-phablet:~$ system-image-cli -i current build number: 443 device name: arale channel: ubuntu-touch/rc-proposed/meizu.en last update: 2016-10-17 14:09:39 version version: 443 version ubuntu: 20161015 version device: 20160526-af18709 Precondition: This issue only happened on Alare device. Step: 1. Open message app and start a new message 2. Press the "+" icon to add attachment 3. Select Video and chooes Camera 4. Check the rear camera action Actual result: After step 3, rear camera viewfinder is black Expect result: Camera viewfinder should work normal. ** Affects: messaging-app (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to messaging-app in Ubuntu. https://bugs.launchpad.net/bugs/1634066 Title: Screen black when take video with rear camera to send MMS. Status in messaging-app package in Ubuntu: New Bug description: Information: phablet@ubuntu-phablet:~$ system-image-cli -i current build number: 443 device name: arale channel: ubuntu-touch/rc-proposed/meizu.en last update: 2016-10-17 14:09:39 version version: 443 version ubuntu: 20161015 version device: 20160526-af18709 Precondition: This issue only happened on Alare device. Step: 1. Open message app and start a new message 2. Press the "+" icon to add attachment 3. Select Video and chooes Camera 4. Check the rear camera action Actual result: After step 3, rear camera viewfinder is black Expect result: Camera viewfinder should work normal. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/messaging-app/+bug/1634066/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1625024] [NEW] Receive phone call, sound via BT speaker by default.
Public bug reported: Information: phablet@ubuntu-phablet:~$ system-image-cli -i current build number: 63 device name: krillin channel: ubuntu-touch/rc/bq-aquaris.en last update: 2016-09-05 13:29:03 version version: 63 version ubuntu: 20160903 version tag: OTA-13-rc version device: 20160606-ab415b2 version custom: 20160831-991-38-18 https://prod.practitest.com/p/1548/qtest_runs/5967362/edit Precondition: Connect BT speaker with phone. Step: 1. Call DUT from secondary phone. 2. Receive the phone call 3. Check the sound icon is via BT speaker by default, but the BT speaker isn't support to voice call. Expect result: The call should use phone by default, not the BT speaker. ** Affects: telepathy-ofono (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to telepathy-ofono in Ubuntu. https://bugs.launchpad.net/bugs/1625024 Title: Receive phone call, sound via BT speaker by default. Status in telepathy-ofono package in Ubuntu: New Bug description: Information: phablet@ubuntu-phablet:~$ system-image-cli -i current build number: 63 device name: krillin channel: ubuntu-touch/rc/bq-aquaris.en last update: 2016-09-05 13:29:03 version version: 63 version ubuntu: 20160903 version tag: OTA-13-rc version device: 20160606-ab415b2 version custom: 20160831-991-38-18 https://prod.practitest.com/p/1548/qtest_runs/5967362/edit Precondition: Connect BT speaker with phone. Step: 1. Call DUT from secondary phone. 2. Receive the phone call 3. Check the sound icon is via BT speaker by default, but the BT speaker isn't support to voice call. Expect result: The call should use phone by default, not the BT speaker. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/telepathy-ofono/+bug/1625024/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1615965] [NEW] Damaged thumbnail shows on Photo Roll after delete photo.
Public bug reported: Information: phablet@ubuntu-phablet:~$ system-image-cli -i current build number: 413 device name: krillin channel: ubuntu-touch/rc-proposed/bq-aquaris.en last update: 2016-08-23 14:49:50 version version: 413 version ubuntu: 20160823 version device: 20160606-ab415b2 version custom: 20160805-985-38-15 Precondition: DUT storage more than 30 photos on com.ubuntu.camera folder. Step: 1. Launch the camera app 2. Slide left to launch Photo Roll 3. Switch to the thumbnail view (by press the list icon on the right top) 4. Long press one photo and select it by check the checkbox. 5. Select some photos more. 6. Delete these photos. 7. Scroll down the page and then scroll up back. 8. Check the thumbnail. Actual result: The deleted photo shows damaged thumbnail on Photo Roll. Expect result: The deleted photo shouldn't show on Photo Roll ** Affects: camera-app (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to camera-app in Ubuntu. https://bugs.launchpad.net/bugs/1615965 Title: Damaged thumbnail shows on Photo Roll after delete photo. Status in camera-app package in Ubuntu: New Bug description: Information: phablet@ubuntu-phablet:~$ system-image-cli -i current build number: 413 device name: krillin channel: ubuntu-touch/rc-proposed/bq-aquaris.en last update: 2016-08-23 14:49:50 version version: 413 version ubuntu: 20160823 version device: 20160606-ab415b2 version custom: 20160805-985-38-15 Precondition: DUT storage more than 30 photos on com.ubuntu.camera folder. Step: 1. Launch the camera app 2. Slide left to launch Photo Roll 3. Switch to the thumbnail view (by press the list icon on the right top) 4. Long press one photo and select it by check the checkbox. 5. Select some photos more. 6. Delete these photos. 7. Scroll down the page and then scroll up back. 8. Check the thumbnail. Actual result: The deleted photo shows damaged thumbnail on Photo Roll. Expect result: The deleted photo shouldn't show on Photo Roll To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/camera-app/+bug/1615965/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1615956] [NEW] Share photo from Gallery to Tagger, no reaction.
Public bug reported: Information: phablet@ubuntu-phablet:~$ system-image-cli -i current build number: 413 device name: krillin channel: ubuntu-touch/rc-proposed/bq-aquaris.en last update: 2016-08-23 14:49:50 version version: 413 version ubuntu: 20160823 version device: 20160606-ab415b2 version custom: 20160805-985-38-15 Precondition: Some photo on Gallery or Photo roll (include some QR code picture) Path: 1. Launch Gallery or Photo roll 2. Select one or some photos, select share 3. select share to Tagger Actual result: DUT open the tagger app, go to Scan code screen, no share photo reaction. Expect result: Better remove share to Tagger selection from Gallery and Photo roll. ** Affects: gallery-app (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gallery-app in Ubuntu. https://bugs.launchpad.net/bugs/1615956 Title: Share photo from Gallery to Tagger, no reaction. Status in gallery-app package in Ubuntu: New Bug description: Information: phablet@ubuntu-phablet:~$ system-image-cli -i current build number: 413 device name: krillin channel: ubuntu-touch/rc-proposed/bq-aquaris.en last update: 2016-08-23 14:49:50 version version: 413 version ubuntu: 20160823 version device: 20160606-ab415b2 version custom: 20160805-985-38-15 Precondition: Some photo on Gallery or Photo roll (include some QR code picture) Path: 1. Launch Gallery or Photo roll 2. Select one or some photos, select share 3. select share to Tagger Actual result: DUT open the tagger app, go to Scan code screen, no share photo reaction. Expect result: Better remove share to Tagger selection from Gallery and Photo roll. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gallery-app/+bug/1615956/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1613959] [NEW] SIM1 is selected by default after setting outgoing calls as "Ask me each time"
Public bug reported: Information: phablet@ubuntu-phablet:~$ system-image-cli -i current build number: 409 device name: krillin channel: ubuntu-touch/rc-proposed/bq-aquaris.en last update: 2016-08-16 12:51:45 version version: 409 version ubuntu: 20160816 version device: 20160606-ab415b2 version custom: 20160805-985-38-15 Precondition: 1. Insert Dual SIM card and unlock both Steps: 1. Go system-settings > Set outgoing calls to use "Ask me each time" 2. Launch dialer app 3. When pop up "Switch to defaule SIM", select "Later" 4. check the dialer page, SIM1 is selected by default. 5. input a phone number and press "calling" icon 6. pop up "change all call associations to SIM 1?" select "No", and check "Don't ask me again" checkbox Actual result: 1. After step 3, the SIM 1 is select by default, which shouldn't. 2. After step 6, pop up "No SIM card selected" notification. 3. If once switch to SIM2 first and switch back to SIM1, the outgoing call can be made, but the hint "Switch to defaule SIM" doesn't show up ** Affects: dialer-app (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dialer-app in Ubuntu. https://bugs.launchpad.net/bugs/1613959 Title: SIM1 is selected by default after setting outgoing calls as "Ask me each time" Status in dialer-app package in Ubuntu: New Bug description: Information: phablet@ubuntu-phablet:~$ system-image-cli -i current build number: 409 device name: krillin channel: ubuntu-touch/rc-proposed/bq-aquaris.en last update: 2016-08-16 12:51:45 version version: 409 version ubuntu: 20160816 version device: 20160606-ab415b2 version custom: 20160805-985-38-15 Precondition: 1. Insert Dual SIM card and unlock both Steps: 1. Go system-settings > Set outgoing calls to use "Ask me each time" 2. Launch dialer app 3. When pop up "Switch to defaule SIM", select "Later" 4. check the dialer page, SIM1 is selected by default. 5. input a phone number and press "calling" icon 6. pop up "change all call associations to SIM 1?" select "No", and check "Don't ask me again" checkbox Actual result: 1. After step 3, the SIM 1 is select by default, which shouldn't. 2. After step 6, pop up "No SIM card selected" notification. 3. If once switch to SIM2 first and switch back to SIM1, the outgoing call can be made, but the hint "Switch to defaule SIM" doesn't show up To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dialer-app/+bug/1613959/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1613625] [NEW] DUT auto reboot when tap on Emergency Call icon
Public bug reported: Information: phablet@ubuntu-phablet:~$ system-image-cli -i current build number: 409 device name: krillin channel: ubuntu-touch/rc-proposed/bq-aquaris.en last update: 2016-08-16 12:51:45 version version: 409 version ubuntu: 20160816 version device: 20160606-ab415b2 version custom: 20160805-985-38-15 Precondition: 1. DUT in locked page 2. Insert/uninsert SIM card can reproduce this issue both. Path: 1. Swipe to unlock the device page 2. Tap on Emergency Call icon Actual result: Dial panel no reaction anymore and DUT auto reboot. Expect result: Can launch Emergency Call page normal. ** 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 telephony-service in Ubuntu. https://bugs.launchpad.net/bugs/1613625 Title: DUT auto reboot when tap on Emergency Call icon Status in telephony-service package in Ubuntu: New Bug description: Information: phablet@ubuntu-phablet:~$ system-image-cli -i current build number: 409 device name: krillin channel: ubuntu-touch/rc-proposed/bq-aquaris.en last update: 2016-08-16 12:51:45 version version: 409 version ubuntu: 20160816 version device: 20160606-ab415b2 version custom: 20160805-985-38-15 Precondition: 1. DUT in locked page 2. Insert/uninsert SIM card can reproduce this issue both. Path: 1. Swipe to unlock the device page 2. Tap on Emergency Call icon Actual result: Dial panel no reaction anymore and DUT auto reboot. Expect result: Can launch Emergency Call page normal. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/telephony-service/+bug/1613625/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1610874] [NEW] Input "Z" and "T" in the To: field, show all contact with phone number, even the contact name doesn't include "Z" and "T"
Public bug reported: Information: current build number: 402 device name: krillin channel: ubuntu-touch/rc-proposed/bq-aquaris.en last update: 2016-08-08 09:35:04 version version: 402 version ubuntu: 20160806 version device: 20160606-ab415b2 version custom: 20160701-981-38-14 Precondition: Address book contains some contacts with phone number (contact name can be blank or doesn't include "Z" and "T" character) Step: 1. Open message app, input "Z" and "T" character in the To: field Actual result: It show all contact with phone number,even the contact name doesn't include "Z" and "T" character. Expect result: Should show the relative contact. ** Affects: messaging-app (Ubuntu) Importance: Undecided Status: New ** Attachment added: "screenshot20160808_154006651.png" https://bugs.launchpad.net/bugs/1610874/+attachment/4716476/+files/screenshot20160808_154006651.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to messaging-app in Ubuntu. https://bugs.launchpad.net/bugs/1610874 Title: Input "Z" and "T" in the To: field, show all contact with phone number, even the contact name doesn't include "Z" and "T" Status in messaging-app package in Ubuntu: New Bug description: Information: current build number: 402 device name: krillin channel: ubuntu-touch/rc-proposed/bq-aquaris.en last update: 2016-08-08 09:35:04 version version: 402 version ubuntu: 20160806 version device: 20160606-ab415b2 version custom: 20160701-981-38-14 Precondition: Address book contains some contacts with phone number (contact name can be blank or doesn't include "Z" and "T" character) Step: 1. Open message app, input "Z" and "T" character in the To: field Actual result: It show all contact with phone number,even the contact name doesn't include "Z" and "T" character. Expect result: Should show the relative contact. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/messaging-app/+bug/1610874/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1393800] Re: Ubuntu 14.10 shut down slow after sleep
The hardware is a Lenovo x121e. Ditch ModemManager solves the problem. But I would say it is not a proper solution. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1393800 Title: Ubuntu 14.10 shut down slow after sleep Status in modemmanager package in Ubuntu: Confirmed Bug description: I upgraded from 14.04 to 14.10 recently. My laptop does not shut down properly anymore. It used to take only 5 sec to shutdown in 14.04. But now it needs ca. 5 min to shut down after sleep. If it never slept, then shut down process is normal. The message on the shut down screen has something to do with ModemManager: ModemManager: ModemManager is shut down ModemManager: Could not acquire the 'org.freedesktop.ModemManager1' service name it stays like that for ca. 5 min before it suddenly shuts down. I added stop on runlevel [06] to the network-manager.conf file. It did not help. I used shutdown -h now. It did not help. modemmanager: Installed: 1.2.0-1 Candidate: 1.2.0-1 Version table: *** 1.2.0-1 0 500 http://archive.ubuntu.com/ubuntu/ utopic/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: modemmanager 1.2.0-1 ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4 Uname: Linux 3.16.0-24-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CurrentDesktop: KDE Date: Tue Nov 18 15:10:26 2014 InstallationDate: Installed on 2012-03-22 (970 days ago) InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) SourcePackage: modemmanager UpgradeStatus: Upgraded to utopic on 2014-10-24 (25 days ago) mtime.conffile..etc.init.modemmanager.conf: 2014-11-18T10:37:43.218538 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1393800/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1393800] Re: Ubuntu 14.10 shut down slow after sleep
I have the shutdown time improved by editing both /etc/init/modemmanager.conf and /etc/init/network-manager.conf via adding a line to them: kill timeout 1 The original post on that idea is from: http://www.hecticgeek.com/2012/10/speed-up-ubuntu-shutdown-process/ -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1393800 Title: Ubuntu 14.10 shut down slow after sleep Status in modemmanager package in Ubuntu: Confirmed Bug description: I upgraded from 14.04 to 14.10 recently. My laptop does not shut down properly anymore. It used to take only 5 sec to shutdown in 14.04. But now it needs ca. 5 min to shut down after sleep. If it never slept, then shut down process is normal. The message on the shut down screen has something to do with ModemManager: ModemManager: ModemManager is shut down ModemManager: Could not acquire the 'org.freedesktop.ModemManager1' service name it stays like that for ca. 5 min before it suddenly shuts down. I added stop on runlevel [06] to the network-manager.conf file. It did not help. I used shutdown -h now. It did not help. modemmanager: Installed: 1.2.0-1 Candidate: 1.2.0-1 Version table: *** 1.2.0-1 0 500 http://archive.ubuntu.com/ubuntu/ utopic/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: modemmanager 1.2.0-1 ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4 Uname: Linux 3.16.0-24-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CurrentDesktop: KDE Date: Tue Nov 18 15:10:26 2014 InstallationDate: Installed on 2012-03-22 (970 days ago) InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) SourcePackage: modemmanager UpgradeStatus: Upgraded to utopic on 2014-10-24 (25 days ago) mtime.conffile..etc.init.modemmanager.conf: 2014-11-18T10:37:43.218538 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1393800/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1393800] [NEW] Ubuntu 14.10 shut down slow after sleep
Public bug reported: I upgraded from 14.04 to 14.10 recently. My laptop does not shut down properly anymore. It used to take only 5 sec to shutdown in 14.04. But now it needs ca. 5 min to shut down after sleep. If it never slept, then shut down process is normal. The message on the shut down screen has something to do with ModemManager: ModemManager: ModemManager is shut down ModemManager: Could not acquire the 'org.freedesktop.ModemManager1' service name it stays like that for ca. 5 min before it suddenly shuts down. I added stop on runlevel [06] to the network-manager.conf file. It did not help. I used shutdown -h now. It did not help. modemmanager: Installed: 1.2.0-1 Candidate: 1.2.0-1 Version table: *** 1.2.0-1 0 500 http://archive.ubuntu.com/ubuntu/ utopic/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: modemmanager 1.2.0-1 ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4 Uname: Linux 3.16.0-24-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CurrentDesktop: KDE Date: Tue Nov 18 15:10:26 2014 InstallationDate: Installed on 2012-03-22 (970 days ago) InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) SourcePackage: modemmanager UpgradeStatus: Upgraded to utopic on 2014-10-24 (25 days ago) mtime.conffile..etc.init.modemmanager.conf: 2014-11-18T10:37:43.218538 ** Affects: modemmanager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug utopic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1393800 Title: Ubuntu 14.10 shut down slow after sleep Status in “modemmanager” package in Ubuntu: New Bug description: I upgraded from 14.04 to 14.10 recently. My laptop does not shut down properly anymore. It used to take only 5 sec to shutdown in 14.04. But now it needs ca. 5 min to shut down after sleep. If it never slept, then shut down process is normal. The message on the shut down screen has something to do with ModemManager: ModemManager: ModemManager is shut down ModemManager: Could not acquire the 'org.freedesktop.ModemManager1' service name it stays like that for ca. 5 min before it suddenly shuts down. I added stop on runlevel [06] to the network-manager.conf file. It did not help. I used shutdown -h now. It did not help. modemmanager: Installed: 1.2.0-1 Candidate: 1.2.0-1 Version table: *** 1.2.0-1 0 500 http://archive.ubuntu.com/ubuntu/ utopic/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: modemmanager 1.2.0-1 ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4 Uname: Linux 3.16.0-24-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CurrentDesktop: KDE Date: Tue Nov 18 15:10:26 2014 InstallationDate: Installed on 2012-03-22 (970 days ago) InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) SourcePackage: modemmanager UpgradeStatus: Upgraded to utopic on 2014-10-24 (25 days ago) mtime.conffile..etc.init.modemmanager.conf: 2014-11-18T10:37:43.218538 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1393800/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp