[Touch-packages] [Bug 2047314] Re: tzdata 2023d release (leap-second.list expiring this week)
I installed tzdata_2023d-0ubuntu0.23.10_all.deb on a 22.04.3 LTS system
with these messages logged.
ntpd[2389941]: leapsecond file ('/usr/share/zoneinfo/leap-seconds.list'):
good hash signature
ntpd[2389941]: leapsecond file ('/usr/share/zoneinfo/leap-seconds.list'):
loaded, expire=2024-06-28T00:00:00Z last=2017-01-01T00:00:00Z ofs=37
Looks good to me! Thanks!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to tzdata in Ubuntu.
https://bugs.launchpad.net/bugs/2047314
Title:
tzdata 2023d release (leap-second.list expiring this week)
Status in tzdata package in Ubuntu:
Fix Released
Status in tzdata source package in Focal:
Fix Committed
Status in tzdata source package in Jammy:
Fix Committed
Status in tzdata source package in Lunar:
Fix Committed
Status in tzdata source package in Mantic:
Fix Committed
Bug description:
[ Impact ]
leap-seconds.list shipped by tzdata 2023c expired on Dec 28th 2023.
The 2023d release contains the following changes:
Briefly:
Ittoqqortoormiit, Greenland changes time zones on 2024-03-31.
Vostok, Antarctica changed time zones on 2023-12-18.
Casey, Antarctica changed time zones five times since 2020.
Code and data fixes for Palestine timestamps starting in 2072.
A new data file zonenow.tab for timestamps starting now.
Changes to future timestamps
Ittoqqortoormiit, Greenland (America/Scoresbysund) joins most of
the rest of Greenland's timekeeping practice on 2024-03-31, by
changing its time zone from -01/+00 to -02/-01 at the same moment
as the spring-forward transition. Its clocks will therefore not
spring forward as previously scheduled. The time zone change
reverts to its common practice before 1981.
Fix predictions for DST transitions in Palestine in 2072-2075,
correcting a typo introduced in 2023a.
Changes to past and future timestamps
Vostok, Antarctica changed to +05 on 2023-12-18. It had been at
+07 (not +06) for years. (Thanks to Zakhary V. Akulov.)
Change data for Casey, Antarctica to agree with timeanddate.com,
by adding five time zone changes since 2020. Casey is now at +08
instead of +11.
Changes to past tm_isdst flags
Much of Greenland, represented by America/Nuuk, changed its
standard time from -03 to -02 on 2023-03-25, not on 2023-10-28.
This does not affect UTC offsets, only the tm_isdst flag.
(Thanks to Thomas M. Steenholdt.)
New data file
A new data file zonenow.tab helps configure applications that use
timestamps dated from now on. This simplifies configuration,
since users choose from a smaller Zone set. The file's format is
experimental and subject to change.
[ Test Plan ]
Test cases were added to autopkgtest to cover the testing:
* python: test_2023d
So the test plan is to check that all autopkgtest succeeds.
[ Other Info ]
The autopkgtest for chrony is flaky on jammy and newer (see bug
#2002910).
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/2047314/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2047314] Re: leap-second.list expiring this week
I have also been watching the days tick down to expiration. I see that this has been fixed in Debian with tzdata 2023c-5+deb12u1. It would be great if an updated package would flow through Ubuntu. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/2047314 Title: leap-second.list expiring this week Status in tzdata package in Ubuntu: Triaged Bug description: It appears the tzdata package has not been updated with the 2023d timezone data. Current distribution is 2023c. leap-seconds.list is expiring Dec 28th 2023, My fix was to download and extract https://data.iana.org/time- zones/releases/tzdata2023d.tar.gz. Then copy the included leap- seconds.list and leapseconds files to /usr/share/zoneinfo. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/2047314/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1960268] Re: SSL handshake failed - VPN SSL broken in 22.04
Can confirm that fix by fru1z #32 works with GlobalProtect 6.0.5-12 running on 22.04! Thanks! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1960268 Title: SSL handshake failed - VPN SSL broken in 22.04 Status in openssl package in Ubuntu: Expired Bug description: I'm trying to connect with global protect VPN but fails at login with: SSL handshake failed Failed to load URL https://... QtNetwork Error 6 Another VPN client does work but the rdp connection to a remote server fails with: transport_connect_tls:freerdp_set_last_error_ex ERRCONNECT_TLS_CONNECT_FAILED --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu76 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE DistroRelease: Ubuntu 21.10 InstallationDate: Installed on 2021-03-19 (325 days ago) InstallationMedia: Kubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) Package: openssl 3.0.1-0ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Tags: wayland-session impish Uname: Linux 5.15.0-18-generic x86_64 UpgradeStatus: Upgraded to impish on 2022-02-04 (3 days ago) UserGroups: adm cdrom dialout dip docker input lpadmin lxd plugdev sambashare sudo uinput _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu76 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-03-19 (325 days ago) InstallationMedia: Kubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) Package: openssl 3.0.1-0ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Tags: wayland-session jammy Uname: Linux 5.15.0-18-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-02-04 (3 days ago) UserGroups: adm cdrom dialout dip docker input lpadmin lxd plugdev sambashare sudo uinput _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1960268/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2007317] [NEW] PCI/internal sound card not detected
Public bug reported: After updating Ubuntu 22.04.1 LTS from kernel 5.15.0-58 to 5.15.0-60 all audio in and out was lost. Using grub to boot to the previous kernel (5.15.0-58) restored proper audio functionality. So the problem appears to be associated with the new kernel. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.15.0-60.66-generic 5.15.78 Uname: Linux 5.15.0-60-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/seq:rreed 1481 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Feb 14 17:07:09 2023 PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: Upgraded to jammy on 2022-06-27 (232 days ago) dmi.bios.date: 09/18/2018 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F10 dmi.board.asset.tag: Default string dmi.board.name: Z370N WIFI-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF10:bd09/18/2018:br5.12:svnGigabyteTechnologyCo.,Ltd.:pnZ370NWIFI:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnZ370NWIFI-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: Default string dmi.product.name: Z370N WIFI dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- 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/2007317 Title: PCI/internal sound card not detected Status in alsa-driver package in Ubuntu: New Bug description: After updating Ubuntu 22.04.1 LTS from kernel 5.15.0-58 to 5.15.0-60 all audio in and out was lost. Using grub to boot to the previous kernel (5.15.0-58) restored proper audio functionality. So the problem appears to be associated with the new kernel. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.15.0-60.66-generic 5.15.78 Uname: Linux 5.15.0-60-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/seq:rreed 1481 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Feb 14 17:07:09 2023 PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: Upgraded to jammy on 2022-06-27 (232 days ago) dmi.bios.date: 09/18/2018 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F10 dmi.board.asset.tag: Default string dmi.board.name: Z370N WIFI-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF10:bd09/18/2018:br5.12:svnGigabyteTechnologyCo.,Ltd.:pnZ370NWIFI:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnZ370NWIFI-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: Default string dmi.product.name: Z370N WIFI dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2007317/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1993651] [NEW] Schema validator reports the wrong child element as missing
Public bug reported:
Here's the repro script:
#!/usr/bin/env python3
import sys
from lxml import etree
XSD = """\
http://www.w3.org/2001/XMLSchema;>
"""
XML = """\
Guido
TechnicalBackup
"""
print("%-20s: %s" % ('Python', sys.version_info))
print("%-20s: %s" % ('lxml.etree', etree.LXML_VERSION))
print("%-20s: %s" % ('libxml used', etree.LIBXML_VERSION))
print("%-20s: %s" % ('libxml compiled', etree.LIBXML_COMPILED_VERSION))
print("%-20s: %s" % ('libxslt used', etree.LIBXSLT_VERSION))
print("%-20s: %s" % ('libxslt compiled', etree.LIBXSLT_COMPILED_VERSION))
schema = etree.XMLSchema(etree.fromstring(XSD))
doc = etree.fromstring(XML)
if not schema.validate(doc):
print(schema.error_log)
# END OF REPRO SCRIPT
Here's the output:
Python : sys.version_info(major=3, minor=10, micro=6, releaselevel='final',
serial=0)
lxml.etree : (4, 9, 1, 0)
libxml used : (2, 9, 14)
libxml compiled : (2, 9, 14)
libxslt used : (1, 1, 35)
libxslt compiled : (1, 1, 35)
:1:0:ERROR:SCHEMASV:SCHEMAV_ELEMENT_CONTENT: Element 'Person': Missing
child element(s). Expected is ( Role ).
# END OF OUTPUT
It's clear from examining the schema and the XML document being
validated that adding a second Role element is not necessary, and would
do nothing to make the document valid. The correct assessment of the
validation is that the required Details child element is missing.
** Affects: libxml2 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libxml2 in Ubuntu.
https://bugs.launchpad.net/bugs/1993651
Title:
Schema validator reports the wrong child element as missing
Status in libxml2 package in Ubuntu:
New
Bug description:
Here's the repro script:
#!/usr/bin/env python3
import sys
from lxml import etree
XSD = """\
http://www.w3.org/2001/XMLSchema;>
"""
XML = """\
Guido
TechnicalBackup
"""
print("%-20s: %s" % ('Python', sys.version_info))
print("%-20s: %s" % ('lxml.etree', etree.LXML_VERSION))
print("%-20s: %s" % ('libxml used', etree.LIBXML_VERSION))
print("%-20s: %s" % ('libxml compiled', etree.LIBXML_COMPILED_VERSION))
print("%-20s: %s" % ('libxslt used', etree.LIBXSLT_VERSION))
print("%-20s: %s" % ('libxslt compiled', etree.LIBXSLT_COMPILED_VERSION))
schema = etree.XMLSchema(etree.fromstring(XSD))
doc = etree.fromstring(XML)
if not schema.validate(doc):
print(schema.error_log)
# END OF REPRO SCRIPT
Here's the output:
Python : sys.version_info(major=3, minor=10, micro=6, releaselevel='final',
serial=0)
lxml.etree : (4, 9, 1, 0)
libxml used : (2, 9, 14)
libxml compiled : (2, 9, 14)
libxslt used : (1, 1, 35)
libxslt compiled : (1, 1, 35)
:1:0:ERROR:SCHEMASV:SCHEMAV_ELEMENT_CONTENT: Element 'Person':
Missing child element(s). Expected is ( Role ).
# END OF OUTPUT
It's clear from examining the schema and the XML document being
validated that adding a second Role element is not necessary, and
would do nothing to make the document valid. The correct assessment of
the validation is that the required Details child element is missing.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libxml2/+bug/1993651/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1988119] Re: Update to systemd 237-3ubuntu10.54 broke dns
this worked for us: https://github.com/joaguas/aksdnsfallback#if-the- above-method-fails-because-dhclient-might-stall-another-alternative-is- to-configure-resolved-to-use-a-fallback-dns-server-which-we-can- hardcode-in-its-configuration -- 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/1988119 Title: Update to systemd 237-3ubuntu10.54 broke dns Status in systemd package in Ubuntu: Confirmed Bug description: Two servers today that updated systemd to "systemd 237-3ubuntu10.54" https://ubuntu.com/security/notices/USN-5583-1 could not resolve dns anymore. no dns servers, normally set through dhcp. Ubuntu 18.04 Temp fix. 1. Edit /etc/systemd/resolved.conf 1. Add/Uncomment # FallbackDNS=168.63.129.16 1. Restart systemd-resolved sudo systemctl restart systemd-resolved.service 1. Confirm dns working with systemd-resolve google.com To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1988119/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1924251] Re: Embedded browser display corruption under Wayland on Pi desktop
This issue is still existing after the fresh installation on raspberry pi 4 8GB desktop. ** Attachment added: "Screenshot from 2022-05-25 00-06-30.png" https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1924251/+attachment/5593004/+files/Screenshot%20from%202022-05-25%2000-06-30.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1924251 Title: Embedded browser display corruption under Wayland on Pi desktop Status in gtk+3.0 package in Ubuntu: Confirmed Status in webkit2gtk package in Ubuntu: Confirmed Status in yelp package in Ubuntu: Confirmed Bug description: On the hirsute Pi desktop, under a wayland session with the "full" KMS overlay enabled, and "kms-modifiers" present in the org.gnome.mutter/experimental-features, the body of a window containing an HTML renderer (e.g. help text or a login page) displays corruption. These reproduction cases may not be entirely reliable given that *some* pages appear to render correctly, but I'll include a couple in the hopes of making it reliably reproducible: 1. Open the Lights Off game 2. Select "Help" from the menu 3. In the help window that appears, select any link "Basics", "Rules", and "Strategy" all reliably reproduce the issue for me, but "Help Translate" doesn't so you may need to click around some links until the corruption appears -- however, once it does even navigating back to the prior page which rendered happily now displays the same corruption. Another reproduction case: 1. Open the Settings application 2. Select the Online Applications option from the left 3. Select the Google entry in the list 4. The login window that appears always displays corruption for me The Microsoft option always reliably corrupts for me, but the Facebook one doesn't so again I wonder how reproducible this may be for others (might be worth trying several options if the first doesn't display corruption). The corruption appears in the form of "shredded" content as if a horizontal stride is set incorrectly somewhere, but only appears in the body of the window; the window decorations are unaffected. I'll attach a screenshot of the corrupted help window to illustrate. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1924251/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1461834] Re: 1024-bit signing keys should be deprecated
> GPG does not provide a way for APT to validate key lengths when the signature is verified, so we did all we could do here. Some pages, like https://launchpad.net/~fnu/+archive/ubuntu/main-fnu/ say "Signing key: 1024R" when you click on "Technical details about this PPA". So launchpad clearly knows, and at the very least it *must* put a big warning on such pages, so as not to fool users into compromising the security of their computers. It's not true to say there's nothing launchpad can do. Since the underlying problem is clearly real, why is this launchpad bug still 'New' and not 'Confirmed' after more than 6 years 2 months? -- 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/1461834 Title: 1024-bit signing keys should be deprecated Status in Launchpad itself: New Status in apt package in Ubuntu: Invalid Status in gnupg2 package in Ubuntu: Confirmed Bug description: 1024-bit RSA was deprecated years ago by NIST[1], Microsoft[2] and more recently by others[3]. 1024-bit signing keys are insufficient to guarantee the authenticity of software distributed from Launchpad.net including PPAs. There should be a mechanism to refuse signing keys below a minimum key length based on key type. 1024-bit signing keys should be deprecated and removed from Launchpad.net itself ASAP. Future projects and PPAs should be disallowed from using 1024-bit signing keys. 1. http://csrc.nist.gov/publications/nistpubs/800-131A/sp800-131A.pdf 2. http://blogs.technet.com/b/pki/archive/2012/06/12/rsa-keys-under-1024-bits-are-blocked.aspx 3. https://threatpost.com/mozilla-1024-bit-cert-deprecation-leaves-107000-sites-untrusted/108114 To manage notifications about this bug go to: https://bugs.launchpad.net/launchpad/+bug/1461834/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1920665] Re: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected"
I understand, thanks Rik. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1920665 Title: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected" Status in mesa package in Ubuntu: Fix Released Status in ubiquity package in Ubuntu: Incomplete Status in mesa source package in Hirsute: Fix Released Status in ubiquity source package in Hirsute: Incomplete Bug description: ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: ubiquity 21.04.11 ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0 Uname: Linux 5.11.0-11-generic x86_64 ApportVersion: 2.20.11-0ubuntu60 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.460 CurrentDesktop: KDE Date: Sun Mar 21 11:53:44 2021 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/kubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Kubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210321) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) Since approximately 16/03/2021 ubiquity from maybe-ubiquity (try install screen) and from the live session is crashing on launch or shortly after. Cases where the crash can be triggered: - Using a Virtualbox VM, where graphics acceleration is handled by mesa with LLVMPIPE - Start the ISO on real hardware in 'safe graphics mode' Cases where the crash is not encountered: - Start the ISO on real intel (HD graphics) hardware with full acceleration. NOTE: The crash can be avoided by downgrading MESA 21.0.x packages to the previous 20.3.4 in hirsute. Try/Install crash: Screen fails to start, or starts then crashes on any user action. The user is presented with: "Installation failed - The installer encountered an unrecoverable error. A desktop session will now be run so that you may investigate the problem or try installing again" Live session crash: The installer does not start from the desktop icon. Starting ubiquity from the terminal results in an "Aborted (core dumped)" message and nothing else. The crash is most commonly "malloc(): unaligned tcache chunk detected", but inevitably from this sort of memory issue can be something like "realloc(): invalid next size" An example /var/log/installer/debug log from a session where both crashes were triggered is below. /var/log/installer/debug Ubiquity 21.04.11 TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. QSocketNotifier: Invalid socket 17 and type 'Read', disabling... QSocketNotifier: Invalid socket 17 and type 'Write', disabling... QSocketNotifier: Invalid socket 17 and type 'Exception', disabling... Your console font configuration will be updated the next time your system boots. If you want to update it now, run 'setupcon' from a virtual console. update-initramfs is disabled since running on read-only media debconf: DbDriver "passwords" warning: could not open /var/cache/debconf/passwords.dat: Permission denied munmap_chunk(): invalid pointer Ubiquity 21.04.11 QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. TEXT Enter the same password twice, so that it can be checked for typing errors. malloc(): unaligned tcache chunk detected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1920665/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1920665] Re: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected"
I downloaded Kubuntu daily build for 2021-04-09 and put the iso on a thumb drive I am using the 'safe graphics' option needed by my system. The on screen display of the initial file check process, with option to skip, still doesn't show. A splash screen eventually shows and flickers a few times before the screen with 'try live' and 'install now' buttons appears. I can now successfully access with the 'live screen' option, also the 'install now' button works. I successfully installed Kubuntu Hippo via the 'install now' button. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1920665 Title: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected" Status in mesa package in Ubuntu: Fix Released Status in ubiquity package in Ubuntu: Incomplete Status in mesa source package in Hirsute: Fix Released Status in ubiquity source package in Hirsute: Incomplete Bug description: ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: ubiquity 21.04.11 ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0 Uname: Linux 5.11.0-11-generic x86_64 ApportVersion: 2.20.11-0ubuntu60 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.460 CurrentDesktop: KDE Date: Sun Mar 21 11:53:44 2021 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/kubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Kubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210321) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) Since approximately 16/03/2021 ubiquity from maybe-ubiquity (try install screen) and from the live session is crashing on launch or shortly after. Cases where the crash can be triggered: - Using a Virtualbox VM, where graphics acceleration is handled by mesa with LLVMPIPE - Start the ISO on real hardware in 'safe graphics mode' Cases where the crash is not encountered: - Start the ISO on real intel (HD graphics) hardware with full acceleration. NOTE: The crash can be avoided by downgrading MESA 21.0.x packages to the previous 20.3.4 in hirsute. Try/Install crash: Screen fails to start, or starts then crashes on any user action. The user is presented with: "Installation failed - The installer encountered an unrecoverable error. A desktop session will now be run so that you may investigate the problem or try installing again" Live session crash: The installer does not start from the desktop icon. Starting ubiquity from the terminal results in an "Aborted (core dumped)" message and nothing else. The crash is most commonly "malloc(): unaligned tcache chunk detected", but inevitably from this sort of memory issue can be something like "realloc(): invalid next size" An example /var/log/installer/debug log from a session where both crashes were triggered is below. /var/log/installer/debug Ubiquity 21.04.11 TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. QSocketNotifier: Invalid socket 17 and type 'Read', disabling... QSocketNotifier: Invalid socket 17 and type 'Write', disabling... QSocketNotifier: Invalid socket 17 and type 'Exception', disabling... Your console font configuration will be updated the next time your system boots. If you want to update it now, run 'setupcon' from a virtual console. update-initramfs is disabled since running on read-only media debconf: DbDriver "passwords" warning: could not open /var/cache/debconf/passwords.dat: Permission denied munmap_chunk(): invalid pointer Ubiquity 21.04.11 QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. TEXT Enter the same password twice, so that it can be checked for typing errors. malloc(): unaligned tcache chunk detected To manage notifications about this bug
[Touch-packages] [Bug 1920665] Re: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected"
Will the mesa fix be available on a daily build? I would like to test it on my hardware. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1920665 Title: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected" Status in mesa package in Ubuntu: Fix Committed Status in ubiquity package in Ubuntu: Incomplete Status in mesa source package in Hirsute: Fix Committed Status in ubiquity source package in Hirsute: Incomplete Bug description: ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: ubiquity 21.04.11 ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0 Uname: Linux 5.11.0-11-generic x86_64 ApportVersion: 2.20.11-0ubuntu60 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.460 CurrentDesktop: KDE Date: Sun Mar 21 11:53:44 2021 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/kubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Kubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210321) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) Since approximately 16/03/2021 ubiquity from maybe-ubiquity (try install screen) and from the live session is crashing on launch or shortly after. Cases where the crash can be triggered: - Using a Virtualbox VM, where graphics acceleration is handled by mesa with LLVMPIPE - Start the ISO on real hardware in 'safe graphics mode' Cases where the crash is not encountered: - Start the ISO on real intel (HD graphics) hardware with full acceleration. NOTE: The crash can be avoided by downgrading MESA 21.0.x packages to the previous 20.3.4 in hirsute. Try/Install crash: Screen fails to start, or starts then crashes on any user action. The user is presented with: "Installation failed - The installer encountered an unrecoverable error. A desktop session will now be run so that you may investigate the problem or try installing again" Live session crash: The installer does not start from the desktop icon. Starting ubiquity from the terminal results in an "Aborted (core dumped)" message and nothing else. The crash is most commonly "malloc(): unaligned tcache chunk detected", but inevitably from this sort of memory issue can be something like "realloc(): invalid next size" An example /var/log/installer/debug log from a session where both crashes were triggered is below. /var/log/installer/debug Ubiquity 21.04.11 TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. QSocketNotifier: Invalid socket 17 and type 'Read', disabling... QSocketNotifier: Invalid socket 17 and type 'Write', disabling... QSocketNotifier: Invalid socket 17 and type 'Exception', disabling... Your console font configuration will be updated the next time your system boots. If you want to update it now, run 'setupcon' from a virtual console. update-initramfs is disabled since running on read-only media debconf: DbDriver "passwords" warning: could not open /var/cache/debconf/passwords.dat: Permission denied munmap_chunk(): invalid pointer Ubiquity 21.04.11 QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. TEXT Enter the same password twice, so that it can be checked for typing errors. malloc(): unaligned tcache chunk detected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1920665/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1920665] Re: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected"
Having installed Ubuntu Hippo Beta [or a recent daily build version] successfully as in post #32 it is possible to install the Kubuntu desktop over it resulting in a working version of Kubuntu Hippo. I suppose this could be seen as a workaround to install a working Kubuntu 2104. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1920665 Title: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected" Status in mesa package in Ubuntu: Confirmed Status in ubiquity package in Ubuntu: Incomplete Status in mesa source package in Hirsute: Confirmed Status in ubiquity source package in Hirsute: Incomplete Bug description: ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: ubiquity 21.04.11 ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0 Uname: Linux 5.11.0-11-generic x86_64 ApportVersion: 2.20.11-0ubuntu60 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.460 CurrentDesktop: KDE Date: Sun Mar 21 11:53:44 2021 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/kubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Kubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210321) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) Since approximately 16/03/2021 ubiquity from maybe-ubiquity (try install screen) and from the live session is crashing on launch or shortly after. Cases where the crash can be triggered: - Using a Virtualbox VM, where graphics acceleration is handled by mesa with LLVMPIPE - Start the ISO on real hardware in 'safe graphics mode' Cases where the crash is not encountered: - Start the ISO on real intel (HD graphics) hardware with full acceleration. NOTE: The crash can be avoided by downgrading MESA 21.0.x packages to the previous 20.3.4 in hirsute. Try/Install crash: Screen fails to start, or starts then crashes on any user action. The user is presented with: "Installation failed - The installer encountered an unrecoverable error. A desktop session will now be run so that you may investigate the problem or try installing again" Live session crash: The installer does not start from the desktop icon. Starting ubiquity from the terminal results in an "Aborted (core dumped)" message and nothing else. The crash is most commonly "malloc(): unaligned tcache chunk detected", but inevitably from this sort of memory issue can be something like "realloc(): invalid next size" An example /var/log/installer/debug log from a session where both crashes were triggered is below. /var/log/installer/debug Ubiquity 21.04.11 TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. QSocketNotifier: Invalid socket 17 and type 'Read', disabling... QSocketNotifier: Invalid socket 17 and type 'Write', disabling... QSocketNotifier: Invalid socket 17 and type 'Exception', disabling... Your console font configuration will be updated the next time your system boots. If you want to update it now, run 'setupcon' from a virtual console. update-initramfs is disabled since running on read-only media debconf: DbDriver "passwords" warning: could not open /var/cache/debconf/passwords.dat: Permission denied munmap_chunk(): invalid pointer Ubiquity 21.04.11 QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. TEXT Enter the same password twice, so that it can be checked for typing errors. malloc(): unaligned tcache chunk detected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1920665/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help :
[Touch-packages] [Bug 1920665] Re: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected"
I've tried, out of interest, an install of Ubuntu (which incidentally also carries the mesa files) from recent daily builds and also of the recently released beta. Ubuntu is not displaying the behaviour that appears with Kubuntu. It is possible to transfer the iso to a usb stick, run it from there in safe graphics mode and do an install to a partition on the PC. As we know at this time this is not possible for Kubuntu. I post this thinking it might be relevant. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1920665 Title: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected" Status in mesa package in Ubuntu: Confirmed Status in ubiquity package in Ubuntu: Confirmed Status in mesa source package in Hirsute: Confirmed Status in ubiquity source package in Hirsute: Confirmed Bug description: ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: ubiquity 21.04.11 ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0 Uname: Linux 5.11.0-11-generic x86_64 ApportVersion: 2.20.11-0ubuntu60 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.460 CurrentDesktop: KDE Date: Sun Mar 21 11:53:44 2021 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/kubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Kubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210321) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) Since approximately 16/03/2021 ubiquity from maybe-ubiquity (try install screen) and from the live session is crashing on launch or shortly after. Cases where the crash can be triggered: - Using a Virtualbox VM, where graphics acceleration is handled by mesa with LLVMPIPE - Start the ISO on real hardware in 'safe graphics mode' Cases where the crash is not encountered: - Start the ISO on real intel (HD graphics) hardware with full acceleration. NOTE: The crash can be avoided by downgrading MESA 21.0.x packages to the previous 20.3.4 in hirsute. Try/Install crash: Screen fails to start, or starts then crashes on any user action. The user is presented with: "Installation failed - The installer encountered an unrecoverable error. A desktop session will now be run so that you may investigate the problem or try installing again" Live session crash: The installer does not start from the desktop icon. Starting ubiquity from the terminal results in an "Aborted (core dumped)" message and nothing else. The crash is most commonly "malloc(): unaligned tcache chunk detected", but inevitably from this sort of memory issue can be something like "realloc(): invalid next size" An example /var/log/installer/debug log from a session where both crashes were triggered is below. /var/log/installer/debug Ubiquity 21.04.11 TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. QSocketNotifier: Invalid socket 17 and type 'Read', disabling... QSocketNotifier: Invalid socket 17 and type 'Write', disabling... QSocketNotifier: Invalid socket 17 and type 'Exception', disabling... Your console font configuration will be updated the next time your system boots. If you want to update it now, run 'setupcon' from a virtual console. update-initramfs is disabled since running on read-only media debconf: DbDriver "passwords" warning: could not open /var/cache/debconf/passwords.dat: Permission denied munmap_chunk(): invalid pointer Ubiquity 21.04.11 QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. TEXT Enter the same password twice, so that it can be checked for typing errors. malloc(): unaligned tcache chunk detected To manage notifications about this bug go to:
[Touch-packages] [Bug 1920665] Re: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected"
** Changed in: mesa (Ubuntu Hirsute) Status: Confirmed => Opinion -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1920665 Title: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected" Status in mesa package in Ubuntu: Opinion Status in ubiquity package in Ubuntu: Confirmed Status in mesa source package in Hirsute: Opinion Status in ubiquity source package in Hirsute: Confirmed Bug description: ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: ubiquity 21.04.11 ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0 Uname: Linux 5.11.0-11-generic x86_64 ApportVersion: 2.20.11-0ubuntu60 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.460 CurrentDesktop: KDE Date: Sun Mar 21 11:53:44 2021 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/kubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Kubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210321) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) Since approximately 16/03/2021 ubiquity from maybe-ubiquity (try install screen) and from the live session is crashing on launch or shortly after. Cases where the crash can be triggered: - Using a Virtualbox VM, where graphics acceleration is handled by mesa with LLVMPIPE - Start the ISO on real hardware in 'safe graphics mode' Cases where the crash is not encountered: - Start the ISO on real intel (HD graphics) hardware with full acceleration. NOTE: The crash can be avoided by downgrading MESA 21.0.x packages to the previous 20.3.4 in hirsute. Try/Install crash: Screen fails to start, or starts then crashes on any user action. The user is presented with: "Installation failed - The installer encountered an unrecoverable error. A desktop session will now be run so that you may investigate the problem or try installing again" Live session crash: The installer does not start from the desktop icon. Starting ubiquity from the terminal results in an "Aborted (core dumped)" message and nothing else. The crash is most commonly "malloc(): unaligned tcache chunk detected", but inevitably from this sort of memory issue can be something like "realloc(): invalid next size" An example /var/log/installer/debug log from a session where both crashes were triggered is below. /var/log/installer/debug Ubiquity 21.04.11 TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. QSocketNotifier: Invalid socket 17 and type 'Read', disabling... QSocketNotifier: Invalid socket 17 and type 'Write', disabling... QSocketNotifier: Invalid socket 17 and type 'Exception', disabling... Your console font configuration will be updated the next time your system boots. If you want to update it now, run 'setupcon' from a virtual console. update-initramfs is disabled since running on read-only media debconf: DbDriver "passwords" warning: could not open /var/cache/debconf/passwords.dat: Permission denied munmap_chunk(): invalid pointer Ubiquity 21.04.11 QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. TEXT Enter the same password twice, so that it can be checked for typing errors. malloc(): unaligned tcache chunk detected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1920665/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1920665] Re: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected"
Unfortunately what Rik is experiencing on a "live session" in his virtual machine with intel graphics using an unnecessary 'safe graphics' mode is slightly different to my necessary use of 'safe graphics' to unsuccessfully boot from a thumbdrive containing the iso. I'm sorry I am not a bug hunter, I am not aware of the protocols. All I can repeat is that a thumb drive containing either a current daily build or the recent beta does not boot correctly. I would guess in my untutored way that some change to the boot process occurred during March. Up until then I had performed test installs without a hitch. I would be happy to give any assistance/info I can but my programming experience is severely limited. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1920665 Title: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected" Status in mesa package in Ubuntu: Confirmed Status in ubiquity package in Ubuntu: Confirmed Status in mesa source package in Hirsute: Confirmed Status in ubiquity source package in Hirsute: Confirmed Bug description: ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: ubiquity 21.04.11 ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0 Uname: Linux 5.11.0-11-generic x86_64 ApportVersion: 2.20.11-0ubuntu60 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.460 CurrentDesktop: KDE Date: Sun Mar 21 11:53:44 2021 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/kubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Kubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210321) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) Since approximately 16/03/2021 ubiquity from maybe-ubiquity (try install screen) and from the live session is crashing on launch or shortly after. Cases where the crash can be triggered: - Using a Virtualbox VM, where graphics acceleration is handled by mesa with LLVMPIPE - Start the ISO on real hardware in 'safe graphics mode' Cases where the crash is not encountered: - Start the ISO on real intel (HD graphics) hardware with full acceleration. NOTE: The crash can be avoided by downgrading MESA 21.0.x packages to the previous 20.3.4 in hirsute. Try/Install crash: Screen fails to start, or starts then crashes on any user action. The user is presented with: "Installation failed - The installer encountered an unrecoverable error. A desktop session will now be run so that you may investigate the problem or try installing again" Live session crash: The installer does not start from the desktop icon. Starting ubiquity from the terminal results in an "Aborted (core dumped)" message and nothing else. The crash is most commonly "malloc(): unaligned tcache chunk detected", but inevitably from this sort of memory issue can be something like "realloc(): invalid next size" An example /var/log/installer/debug log from a session where both crashes were triggered is below. /var/log/installer/debug Ubiquity 21.04.11 TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. QSocketNotifier: Invalid socket 17 and type 'Read', disabling... QSocketNotifier: Invalid socket 17 and type 'Write', disabling... QSocketNotifier: Invalid socket 17 and type 'Exception', disabling... Your console font configuration will be updated the next time your system boots. If you want to update it now, run 'setupcon' from a virtual console. update-initramfs is disabled since running on read-only media debconf: DbDriver "passwords" warning: could not open /var/cache/debconf/passwords.dat: Permission denied munmap_chunk(): invalid pointer Ubiquity 21.04.11 QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other
[Touch-packages] [Bug 1920665] Re: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected"
"malloc(): unaligned tcache chunk detected" does not appear on my PC. I am trying to install from an iso of hippo on a thumb drive. The boot fails before any 'live session' appears. I am not trying to install from a live session, boot fails before that point. I do not think this is the same as the bug reported here. Rik it appears is attemptig to boot from a live session of some sort. My installation breaks down before reaching this point. The iso in the daily build was not failing until some time in March. It has not been right since. There were a number of updates on a regular basis in March. The change is in the boot process rather than in actual installation as the installation has not been begun at the point the bug occurs. I'm no programmer but I can see that installation has not been offered, let alone begun when things go astray. Please review any conclusions so far. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1920665 Title: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected" Status in mesa package in Ubuntu: Confirmed Status in ubiquity package in Ubuntu: Confirmed Status in mesa source package in Hirsute: Confirmed Status in ubiquity source package in Hirsute: Confirmed Bug description: ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: ubiquity 21.04.11 ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0 Uname: Linux 5.11.0-11-generic x86_64 ApportVersion: 2.20.11-0ubuntu60 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.460 CurrentDesktop: KDE Date: Sun Mar 21 11:53:44 2021 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/kubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Kubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210321) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) Since approximately 16/03/2021 ubiquity from maybe-ubiquity (try install screen) and from the live session is crashing on launch or shortly after. Cases where the crash can be triggered: - Using a Virtualbox VM, where graphics acceleration is handled by mesa with LLVMPIPE - Start the ISO on real hardware in 'safe graphics mode' Cases where the crash is not encountered: - Start the ISO on real intel (HD graphics) hardware with full acceleration. NOTE: The crash can be avoided by downgrading MESA 21.0.x packages to the previous 20.3.4 in hirsute. Try/Install crash: Screen fails to start, or starts then crashes on any user action. The user is presented with: "Installation failed - The installer encountered an unrecoverable error. A desktop session will now be run so that you may investigate the problem or try installing again" Live session crash: The installer does not start from the desktop icon. Starting ubiquity from the terminal results in an "Aborted (core dumped)" message and nothing else. The crash is most commonly "malloc(): unaligned tcache chunk detected", but inevitably from this sort of memory issue can be something like "realloc(): invalid next size" An example /var/log/installer/debug log from a session where both crashes were triggered is below. /var/log/installer/debug Ubiquity 21.04.11 TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. QSocketNotifier: Invalid socket 17 and type 'Read', disabling... QSocketNotifier: Invalid socket 17 and type 'Write', disabling... QSocketNotifier: Invalid socket 17 and type 'Exception', disabling... Your console font configuration will be updated the next time your system boots. If you want to update it now, run 'setupcon' from a virtual console. update-initramfs is disabled since running on read-only media debconf: DbDriver "passwords" warning: could not open /var/cache/debconf/passwords.dat: Permission denied munmap_chunk(): invalid pointer Ubiquity 21.04.11 QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' TEXT If more than one person will use this computer, you can
[Touch-packages] [Bug 1920665] Re: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected"
Is there somewhere or somehow I can test your modified version of Kubuntu by downloading it and attempting an install Rik? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1920665 Title: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected" Status in mesa package in Ubuntu: Confirmed Status in ubiquity package in Ubuntu: Confirmed Status in mesa source package in Hirsute: Confirmed Status in ubiquity source package in Hirsute: Confirmed Bug description: ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: ubiquity 21.04.11 ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0 Uname: Linux 5.11.0-11-generic x86_64 ApportVersion: 2.20.11-0ubuntu60 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.460 CurrentDesktop: KDE Date: Sun Mar 21 11:53:44 2021 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/kubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Kubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210321) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) Since approximately 16/03/2021 ubiquity from maybe-ubiquity (try install screen) and from the live session is crashing on launch or shortly after. Cases where the crash can be triggered: - Using a Virtualbox VM, where graphics acceleration is handled by mesa with LLVMPIPE - Start the ISO on real hardware in 'safe graphics mode' Cases where the crash is not encountered: - Start the ISO on real intel (HD graphics) hardware with full acceleration. NOTE: The crash can be avoided by downgrading MESA 21.0.x packages to the previous 20.3.4 in hirsute. Try/Install crash: Screen fails to start, or starts then crashes on any user action. The user is presented with: "Installation failed - The installer encountered an unrecoverable error. A desktop session will now be run so that you may investigate the problem or try installing again" Live session crash: The installer does not start from the desktop icon. Starting ubiquity from the terminal results in an "Aborted (core dumped)" message and nothing else. An example /var/log/installer/debug log from a session where both crashes were triggered is below. /var/log/installer/debug Ubiquity 21.04.11 TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. QSocketNotifier: Invalid socket 17 and type 'Read', disabling... QSocketNotifier: Invalid socket 17 and type 'Write', disabling... QSocketNotifier: Invalid socket 17 and type 'Exception', disabling... Your console font configuration will be updated the next time your system boots. If you want to update it now, run 'setupcon' from a virtual console. update-initramfs is disabled since running on read-only media debconf: DbDriver "passwords" warning: could not open /var/cache/debconf/passwords.dat: Permission denied munmap_chunk(): invalid pointer Ubiquity 21.04.11 QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. TEXT Enter the same password twice, so that it can be checked for typing errors. malloc(): unaligned tcache chunk detected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1920665/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1920665] Re: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected"
It is possible on my PC to install Ubuntu2104beta without encountering this behaviour and I can successfully install the Ubuntu flavour. This bug does happen with the Kubuntu beta and I find it is impossible to install the Kubuntu flavour from the beta iso. It is worth noting that mesa is present in both Ubuntu and Kubuntu. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1920665 Title: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected" Status in mesa package in Ubuntu: Confirmed Status in ubiquity package in Ubuntu: Confirmed Status in mesa source package in Hirsute: Confirmed Status in ubiquity source package in Hirsute: Confirmed Bug description: ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: ubiquity 21.04.11 ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0 Uname: Linux 5.11.0-11-generic x86_64 ApportVersion: 2.20.11-0ubuntu60 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.460 CurrentDesktop: KDE Date: Sun Mar 21 11:53:44 2021 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/kubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Kubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210321) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) Since approximately 16/03/2021 ubiquity from maybe-ubiquity (try install screen) and from the live session is crashing on launch or shortly after. Cases where the crash can be triggered: - Using a Virtualbox VM, where graphics acceleration is handled by mesa with LLVMPIPE - Start the ISO on real hardware in 'safe graphics mode' Cases where the crash is not encountered: - Start the ISO on real intel (HD graphics) hardware with full acceleration. NOTE: The crash can be avoided by downgrading MESA 21.0.x packages to the previous 20.3.4 in hirsute. Try/Install crash: Screen fails to start, or starts then crashes on any user action. The user is presented with: "Installation failed - The installer encountered an unrecoverable error. A desktop session will now be run so that you may investigate the problem or try installing again" Live session crash: The installer does not start from the desktop icon. Starting ubiquity from the terminal results in an "Aborted (core dumped)" message and nothing else. An example /var/log/installer/debug log from a session where both crashes were triggered is below. /var/log/installer/debug Ubiquity 21.04.11 TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. QSocketNotifier: Invalid socket 17 and type 'Read', disabling... QSocketNotifier: Invalid socket 17 and type 'Write', disabling... QSocketNotifier: Invalid socket 17 and type 'Exception', disabling... Your console font configuration will be updated the next time your system boots. If you want to update it now, run 'setupcon' from a virtual console. update-initramfs is disabled since running on read-only media debconf: DbDriver "passwords" warning: could not open /var/cache/debconf/passwords.dat: Permission denied munmap_chunk(): invalid pointer Ubiquity 21.04.11 QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. TEXT Enter the same password twice, so that it can be checked for typing errors. malloc(): unaligned tcache chunk detected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1920665/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1920665] Re: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected"
This is to confirm that kubuntu-21.04-beta-desktop-amd64.iso fails as an installation media on my PC. I have nvidia graphics, amd m/board and am using 'safe graphics' when attempting to boot up the installation media from a thumb drive. The usual "Installation failed" message is displayed. If more info would help please give me any further instructions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1920665 Title: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected" Status in mesa package in Ubuntu: Confirmed Status in ubiquity package in Ubuntu: Confirmed Status in mesa source package in Hirsute: Confirmed Status in ubiquity source package in Hirsute: Confirmed Bug description: ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: ubiquity 21.04.11 ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0 Uname: Linux 5.11.0-11-generic x86_64 ApportVersion: 2.20.11-0ubuntu60 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.460 CurrentDesktop: KDE Date: Sun Mar 21 11:53:44 2021 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/kubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Kubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210321) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) Since approximately 16/03/2021 ubiquity from maybe-ubiquity (try install screen) and from the live session is crashing on launch or shortly after. Cases where the crash can be triggered: - Using a Virtualbox VM, where graphics acceleration is handled by mesa with LLVMPIPE - Start the ISO on real hardware in 'safe graphics mode' Cases where the crash is not encountered: - Start the ISO on real intel (HD graphics) hardware with full acceleration. NOTE: The crash can be avoided by downgrading MESA 21.0.x packages to the previous 20.3.4 in hirsute. Try/Install crash: Screen fails to start, or starts then crashes on any user action. The user is presented with: "Installation failed - The installer encountered an unrecoverable error. A desktop session will now be run so that you may investigate the problem or try installing again" Live session crash: The installer does not start from the desktop icon. Starting ubiquity from the terminal results in an "Aborted (core dumped)" message and nothing else. An example /var/log/installer/debug log from a session where both crashes were triggered is below. /var/log/installer/debug Ubiquity 21.04.11 TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. QSocketNotifier: Invalid socket 17 and type 'Read', disabling... QSocketNotifier: Invalid socket 17 and type 'Write', disabling... QSocketNotifier: Invalid socket 17 and type 'Exception', disabling... Your console font configuration will be updated the next time your system boots. If you want to update it now, run 'setupcon' from a virtual console. update-initramfs is disabled since running on read-only media debconf: DbDriver "passwords" warning: could not open /var/cache/debconf/passwords.dat: Permission denied munmap_chunk(): invalid pointer Ubiquity 21.04.11 QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. TEXT Enter the same password twice, so that it can be checked for typing errors. malloc(): unaligned tcache chunk detected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1920665/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1920665] Re: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected"
kubuntu hirsute daily build 21-03-28 also fails if safe graphics mode is used on a machine with nVidia graphics -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1920665 Title: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected" Status in mesa package in Ubuntu: Confirmed Status in ubiquity package in Ubuntu: Confirmed Status in mesa source package in Hirsute: Confirmed Status in ubiquity source package in Hirsute: Confirmed Bug description: ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: ubiquity 21.04.11 ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0 Uname: Linux 5.11.0-11-generic x86_64 ApportVersion: 2.20.11-0ubuntu60 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.460 CurrentDesktop: KDE Date: Sun Mar 21 11:53:44 2021 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/kubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Kubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210321) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) Since approximately 16/03/2021 ubiquity from maybe-ubiquity (try install screen) and from the live session is crashing on launch or shortly after. Try/Install crash: Screen fails to start, or starts then crashes on any user action. The user is presented with: "Installation failed - The installer encountered an unrecoverable error. A desktop session will now be run so that you may investigate the problem or try installing again" Live session crash: The installer does not start from the desktop icon. Starting ubiquity from the terminal results in an "Aborted (core dumped)" message and nothing else. An example /var/log/installer/debug log from a session where both crashes were triggered is below. /var/log/installer/debug Ubiquity 21.04.11 TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. QSocketNotifier: Invalid socket 17 and type 'Read', disabling... QSocketNotifier: Invalid socket 17 and type 'Write', disabling... QSocketNotifier: Invalid socket 17 and type 'Exception', disabling... Your console font configuration will be updated the next time your system boots. If you want to update it now, run 'setupcon' from a virtual console. update-initramfs is disabled since running on read-only media debconf: DbDriver "passwords" warning: could not open /var/cache/debconf/passwords.dat: Permission denied munmap_chunk(): invalid pointer Ubiquity 21.04.11 QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. TEXT Enter the same password twice, so that it can be checked for typing errors. malloc(): unaligned tcache chunk detected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1920665/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1920665] Re: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected"
I should repeat, I am performing the installation using 'Safe Graphics' mode. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1920665 Title: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected" Status in mesa package in Ubuntu: Confirmed Status in ubiquity package in Ubuntu: Confirmed Status in mesa source package in Hirsute: Confirmed Status in ubiquity source package in Hirsute: Confirmed Bug description: ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: ubiquity 21.04.11 ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0 Uname: Linux 5.11.0-11-generic x86_64 ApportVersion: 2.20.11-0ubuntu60 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.460 CurrentDesktop: KDE Date: Sun Mar 21 11:53:44 2021 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/kubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Kubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210321) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) Since approximately 16/03/2021 ubiquity from maybe-ubiquity (try install screen) and from the live session is crashing on launch or shortly after. Try/Install crash: Screen fails to start, or starts then crashes on any user action. The user is presented with: "Installation failed - The installer encountered an unrecoverable error. A desktop session will now be run so that you may investigate the problem or try installing again" Live session crash: The installer does not start from the desktop icon. Starting ubiquity from the terminal results in an "Aborted (core dumped)" message and nothing else. An example /var/log/installer/debug log from a session where both crashes were triggered is below. /var/log/installer/debug Ubiquity 21.04.11 TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. QSocketNotifier: Invalid socket 17 and type 'Read', disabling... QSocketNotifier: Invalid socket 17 and type 'Write', disabling... QSocketNotifier: Invalid socket 17 and type 'Exception', disabling... Your console font configuration will be updated the next time your system boots. If you want to update it now, run 'setupcon' from a virtual console. update-initramfs is disabled since running on read-only media debconf: DbDriver "passwords" warning: could not open /var/cache/debconf/passwords.dat: Permission denied munmap_chunk(): invalid pointer Ubiquity 21.04.11 QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. TEXT Enter the same password twice, so that it can be checked for typing errors. malloc(): unaligned tcache chunk detected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1920665/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1920665] Re: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected"
I have attempted to install from kubuntu hirsute daily build 21-03-22 kubuntu hirsute daily build 21-03-23 kubuntu hirsute daily build 21-03-24 each version the insstallation fails. Incidentally I noticed another change. While the daily builds were installing correctly a procedure appeared on screen, this no longer happens. After booting the installation media, a self check ran with an on screen display showing the stages the check was passing through. The word Kubuntu appeared on screen and this display was beneath it. Since the installation began to fail, the file check no longer shows and although the word Kubuntu appears it disappears shortly after. As it changed when installation began to fail, maybe there is a connection? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1920665 Title: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected" Status in mesa package in Ubuntu: Confirmed Status in ubiquity package in Ubuntu: Confirmed Status in mesa source package in Hirsute: Confirmed Status in ubiquity source package in Hirsute: Confirmed Bug description: ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: ubiquity 21.04.11 ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0 Uname: Linux 5.11.0-11-generic x86_64 ApportVersion: 2.20.11-0ubuntu60 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.460 CurrentDesktop: KDE Date: Sun Mar 21 11:53:44 2021 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/kubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Kubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210321) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) Since approximately 16/03/2021 ubiquity from maybe-ubiquity (try install screen) and from the live session is crashing on launch or shortly after. Try/Install crash: Screen fails to start, or starts then crashes on any user action. The user is presented with: "Installation failed - The installer encountered an unrecoverable error. A desktop session will now be run so that you may investigate the problem or try installing again" Live session crash: The installer does not start from the desktop icon. Starting ubiquity from the terminal results in an "Aborted (core dumped)" message and nothing else. An example /var/log/installer/debug log from a session where both crashes were triggered is below. /var/log/installer/debug Ubiquity 21.04.11 TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. QSocketNotifier: Invalid socket 17 and type 'Read', disabling... QSocketNotifier: Invalid socket 17 and type 'Write', disabling... QSocketNotifier: Invalid socket 17 and type 'Exception', disabling... Your console font configuration will be updated the next time your system boots. If you want to update it now, run 'setupcon' from a virtual console. update-initramfs is disabled since running on read-only media debconf: DbDriver "passwords" warning: could not open /var/cache/debconf/passwords.dat: Permission denied munmap_chunk(): invalid pointer Ubiquity 21.04.11 QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. TEXT Enter the same password twice, so that it can be checked for typing errors. malloc(): unaligned tcache chunk detected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1920665/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1920665] Re: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected"
It turns out I don't have my latest successful installation of Kubuntu Hirsute. I did a successful install of Ubuntu Hirsute to confirm whether it was only the Kubuntu version that was affected. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1920665 Title: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected" Status in mesa package in Ubuntu: Confirmed Status in ubiquity package in Ubuntu: Confirmed Status in mesa source package in Hirsute: Confirmed Status in ubiquity source package in Hirsute: Confirmed Bug description: ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: ubiquity 21.04.11 ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0 Uname: Linux 5.11.0-11-generic x86_64 ApportVersion: 2.20.11-0ubuntu60 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.460 CurrentDesktop: KDE Date: Sun Mar 21 11:53:44 2021 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/kubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Kubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210321) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) Since approximately 16/03/2021 ubiquity from maybe-ubiquity (try install screen) and from the live session is crashing on launch or shortly after. Try/Install crash: Screen fails to start, or starts then crashes on any user action. The user is presented with: "Installation failed - The installer encountered an unrecoverable error. A desktop session will now be run so that you may investigate the problem or try installing again" Live session crash: The installer does not start from the desktop icon. Starting ubiquity from the terminal results in an "Aborted (core dumped)" message and nothing else. An example /var/log/installer/debug log from a session where both crashes were triggered is below. /var/log/installer/debug Ubiquity 21.04.11 TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. QSocketNotifier: Invalid socket 17 and type 'Read', disabling... QSocketNotifier: Invalid socket 17 and type 'Write', disabling... QSocketNotifier: Invalid socket 17 and type 'Exception', disabling... Your console font configuration will be updated the next time your system boots. If you want to update it now, run 'setupcon' from a virtual console. update-initramfs is disabled since running on read-only media debconf: DbDriver "passwords" warning: could not open /var/cache/debconf/passwords.dat: Permission denied munmap_chunk(): invalid pointer Ubiquity 21.04.11 QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. TEXT Enter the same password twice, so that it can be checked for typing errors. malloc(): unaligned tcache chunk detected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1920665/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1920665] Re: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected"
My nvidia graphics card needs safe mode, but generally installations proceed without problems. The Hirsute daily builds were installing without a hitch until recently. I'll check my most recent successful installation and see if I can find a version number. It was after this that the bug appeared. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1920665 Title: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected" Status in mesa package in Ubuntu: Confirmed Status in ubiquity package in Ubuntu: Confirmed Status in mesa source package in Hirsute: Confirmed Status in ubiquity source package in Hirsute: Confirmed Bug description: ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: ubiquity 21.04.11 ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0 Uname: Linux 5.11.0-11-generic x86_64 ApportVersion: 2.20.11-0ubuntu60 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.460 CurrentDesktop: KDE Date: Sun Mar 21 11:53:44 2021 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/kubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Kubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210321) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) Since approximately 16/03/2021 ubiquity from maybe-ubiquity (try install screen) and from the live session is crashing on launch or shortly after. Try/Install crash: Screen fails to start, or starts then crashes on any user action. The user is presented with: "Installation failed - The installer encountered an unrecoverable error. A desktop session will now be run so that you may investigate the problem or try installing again" Live session crash: The installer does not start from the desktop icon. Starting ubiquity from the terminal results in an "Aborted (core dumped)" message and nothing else. An example /var/log/installer/debug log from a session where both crashes were triggered is below. /var/log/installer/debug Ubiquity 21.04.11 TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. QSocketNotifier: Invalid socket 17 and type 'Read', disabling... QSocketNotifier: Invalid socket 17 and type 'Write', disabling... QSocketNotifier: Invalid socket 17 and type 'Exception', disabling... Your console font configuration will be updated the next time your system boots. If you want to update it now, run 'setupcon' from a virtual console. update-initramfs is disabled since running on read-only media debconf: DbDriver "passwords" warning: could not open /var/cache/debconf/passwords.dat: Permission denied munmap_chunk(): invalid pointer Ubiquity 21.04.11 QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. TEXT Enter the same password twice, so that it can be checked for typing errors. malloc(): unaligned tcache chunk detected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1920665/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1920665] Re: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected"
correction tp post #11: I just re-attempted installing from thumb drive on my hardware with ISO 2021-03-23 crash as with ISO 2021-03-22 and earlier I have nVidia graphics [using safe mode install option] my hardware is home built PC -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1920665 Title: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected" Status in mesa package in Ubuntu: Confirmed Status in ubiquity package in Ubuntu: Confirmed Status in mesa source package in Hirsute: Confirmed Status in ubiquity source package in Hirsute: Confirmed Bug description: ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: ubiquity 21.04.11 ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0 Uname: Linux 5.11.0-11-generic x86_64 ApportVersion: 2.20.11-0ubuntu60 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.460 CurrentDesktop: KDE Date: Sun Mar 21 11:53:44 2021 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/kubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Kubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210321) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) Since approximately 16/03/2021 ubiquity from maybe-ubiquity (try install screen) and from the live session is crashing on launch or shortly after. Try/Install crash: Screen fails to start, or starts then crashes on any user action. The user is presented with: "Installation failed - The installer encountered an unrecoverable error. A desktop session will now be run so that you may investigate the problem or try installing again" Live session crash: The installer does not start from the desktop icon. Starting ubiquity from the terminal results in an "Aborted (core dumped)" message and nothing else. An example /var/log/installer/debug log from a session where both crashes were triggered is below. /var/log/installer/debug Ubiquity 21.04.11 TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. QSocketNotifier: Invalid socket 17 and type 'Read', disabling... QSocketNotifier: Invalid socket 17 and type 'Write', disabling... QSocketNotifier: Invalid socket 17 and type 'Exception', disabling... Your console font configuration will be updated the next time your system boots. If you want to update it now, run 'setupcon' from a virtual console. update-initramfs is disabled since running on read-only media debconf: DbDriver "passwords" warning: could not open /var/cache/debconf/passwords.dat: Permission denied munmap_chunk(): invalid pointer Ubiquity 21.04.11 QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. TEXT Enter the same password twice, so that it can be checked for typing errors. malloc(): unaligned tcache chunk detected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1920665/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1920665] Re: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected"
crash on my hardware with ISO 2021-03-23 no error message appears now I just get a black screen mouse pointer visible -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1920665 Title: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected" Status in mesa package in Ubuntu: Confirmed Status in ubiquity package in Ubuntu: Confirmed Status in mesa source package in Hirsute: Confirmed Status in ubiquity source package in Hirsute: Confirmed Bug description: ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: ubiquity 21.04.11 ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0 Uname: Linux 5.11.0-11-generic x86_64 ApportVersion: 2.20.11-0ubuntu60 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.460 CurrentDesktop: KDE Date: Sun Mar 21 11:53:44 2021 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/kubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Kubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210321) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) Since approximately 16/03/2021 ubiquity from maybe-ubiquity (try install screen) and from the live session is crashing on launch or shortly after. Try/Install crash: Screen fails to start, or starts then crashes on any user action. The user is presented with: "Installation failed - The installer encountered an unrecoverable error. A desktop session will now be run so that you may investigate the problem or try installing again" Live session crash: The installer does not start from the desktop icon. Starting ubiquity from the terminal results in an "Aborted (core dumped)" message and nothing else. An example /var/log/installer/debug log from a session where both crashes were triggered is below. /var/log/installer/debug Ubiquity 21.04.11 TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. QSocketNotifier: Invalid socket 17 and type 'Read', disabling... QSocketNotifier: Invalid socket 17 and type 'Write', disabling... QSocketNotifier: Invalid socket 17 and type 'Exception', disabling... Your console font configuration will be updated the next time your system boots. If you want to update it now, run 'setupcon' from a virtual console. update-initramfs is disabled since running on read-only media debconf: DbDriver "passwords" warning: could not open /var/cache/debconf/passwords.dat: Permission denied munmap_chunk(): invalid pointer Ubiquity 21.04.11 QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. TEXT Enter the same password twice, so that it can be checked for typing errors. malloc(): unaligned tcache chunk detected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1920665/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1920665] Re: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected"
Unfortunately iso 20210322 is producing a crash on my hardware. [see bug 1920712] -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1920665 Title: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected" Status in mesa package in Ubuntu: New Status in ubiquity package in Ubuntu: New Status in mesa source package in Hirsute: New Status in ubiquity source package in Hirsute: New Bug description: ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: ubiquity 21.04.11 ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0 Uname: Linux 5.11.0-11-generic x86_64 ApportVersion: 2.20.11-0ubuntu60 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.460 CurrentDesktop: KDE Date: Sun Mar 21 11:53:44 2021 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/kubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Kubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210321) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) Since approximately 16/03/2021 ubiquity from maybe-ubiquity (try install screen) and from the live session is crashing on launch or shortly after. Try/Install crash: Screen fails to start, or starts then crashes on any user action. The user is presented with: "Installation failed - The installer encountered an unrecoverable error. A desktop session will now be run so that you may investigate the problem or try installing again" Live session crash: The installer does not start from the desktop icon. Starting ubiquity from the terminal results in an "Aborted (core dumped)" message and nothing else. An example /var/log/installer/debug log from a session where both crashes were triggered is below. /var/log/installer/debug Ubiquity 21.04.11 TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. QSocketNotifier: Invalid socket 17 and type 'Read', disabling... QSocketNotifier: Invalid socket 17 and type 'Write', disabling... QSocketNotifier: Invalid socket 17 and type 'Exception', disabling... Your console font configuration will be updated the next time your system boots. If you want to update it now, run 'setupcon' from a virtual console. update-initramfs is disabled since running on read-only media debconf: DbDriver "passwords" warning: could not open /var/cache/debconf/passwords.dat: Permission denied munmap_chunk(): invalid pointer Ubiquity 21.04.11 QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. TEXT Enter the same password twice, so that it can be checked for typing errors. malloc(): unaligned tcache chunk detected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1920665/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1920665] Re: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected"
successfully create a thumb drive from: hirsute-desktop-amd64.iso 2021-03-21 05:492.7GDesktop image for 64-bit PC (AMD64) computers (standard download) boot from thumb drive: "Installation failed - KDialog \n The installer encountered an unrecoverable error. A desktop session will now be run so that you may investigate the problem or try installing again" Installation cannot proceed. I don't have the know how to be able to investigate, unfortunately. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1920665 Title: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected" Status in mesa package in Ubuntu: New Status in ubiquity package in Ubuntu: New Status in mesa source package in Hirsute: New Status in ubiquity source package in Hirsute: New Bug description: ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: ubiquity 21.04.11 ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0 Uname: Linux 5.11.0-11-generic x86_64 ApportVersion: 2.20.11-0ubuntu60 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.460 CurrentDesktop: KDE Date: Sun Mar 21 11:53:44 2021 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/kubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Kubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210321) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) Since approximately 16/03/2021 ubiquity from maybe-ubiquity (try install screen) and from the live session is crashing on launch or shortly after. An example /var/log/installer/debug log from a session where both crashes were triggered is below. /var/log/installer/debug Ubiquity 21.04.11 TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. QSocketNotifier: Invalid socket 17 and type 'Read', disabling... QSocketNotifier: Invalid socket 17 and type 'Write', disabling... QSocketNotifier: Invalid socket 17 and type 'Exception', disabling... Your console font configuration will be updated the next time your system boots. If you want to update it now, run 'setupcon' from a virtual console. update-initramfs is disabled since running on read-only media debconf: DbDriver "passwords" warning: could not open /var/cache/debconf/passwords.dat: Permission denied munmap_chunk(): invalid pointer Ubiquity 21.04.11 QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. TEXT Enter the same password twice, so that it can be checked for typing errors. malloc(): unaligned tcache chunk detected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1920665/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1910480] Re: no audio on fresh install kubuntu groovy
** Changed in: alsa-driver (Ubuntu)
Status: New => Invalid
--
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/1910480
Title:
no audio on fresh install kubuntu groovy
Status in alsa-driver package in Ubuntu:
Invalid
Bug description:
on installing Kubuntu Groovy 'no output or input devices found'
sound appears to be disabled
running ubuntu-debug -s audio does produce sound in both headphone channels
in first part of test but no sound in second part
sound is recognised and working okay if Kubuntu Focal is installed
ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 5.8.0-34.37-generic 5.8.18
Uname: Linux 5.8.0-34-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu50.3
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: bob1071 F pulseaudio
bob1074 F pipewire-media-
/dev/snd/controlC1: bob1074 F pipewire-media-
/dev/snd/seq: bob1070 F pipewire
CasperMD5CheckResult: skip
CurrentDesktop: KDE
Date: Thu Jan 7 03:19:48 2021
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:SB successful
Symptom_Card: Built-in Audio - HDA ATI SB
Symptom_Jack: SPDIF Out, Internal
Symptom_PulsePlaybackTest: PulseAudio playback test failed
Symptom_Type: None of the above
Title: [MBB-895908, Realtek ALC892, SPDIF Out, Internal] Playback problem
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/07/2014
dmi.bios.release: 4.6
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2501
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: M5A99FX PRO R2.0
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: 7354844-001
dmi.chassis.type: 3
dmi.chassis.vendor: NOVATECH LTD
dmi.chassis.version: 1.0
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr2501:bd04/07/2014:br4.6:svnNOVATECHLTD:pnMBB-895908:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnM5A99FXPROR2.0:rvrRev1.xx:cvnNOVATECHLTD:ct3:cvr1.0:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: MBB-895908
dmi.product.sku: SKU
dmi.product.version: 1.0
dmi.sys.vendor: NOVATECH LTD
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1910480/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1910480] Re: no audio on fresh install kubuntu groovy
When I submitted this report I wasn't aware that this issue had been mentioned in the Release Notes (which weren't available at the time) ...that means this report is not required. -- 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/1910480 Title: no audio on fresh install kubuntu groovy Status in alsa-driver package in Ubuntu: New Bug description: on installing Kubuntu Groovy 'no output or input devices found' sound appears to be disabled running ubuntu-debug -s audio does produce sound in both headphone channels in first part of test but no sound in second part sound is recognised and working okay if Kubuntu Focal is installed ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.8.0-34.37-generic 5.8.18 Uname: Linux 5.8.0-34-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bob1071 F pulseaudio bob1074 F pipewire-media- /dev/snd/controlC1: bob1074 F pipewire-media- /dev/snd/seq:bob1070 F pipewire CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Thu Jan 7 03:19:48 2021 PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:SB successful Symptom_Card: Built-in Audio - HDA ATI SB Symptom_Jack: SPDIF Out, Internal Symptom_PulsePlaybackTest: PulseAudio playback test failed Symptom_Type: None of the above Title: [MBB-895908, Realtek ALC892, SPDIF Out, Internal] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/07/2014 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2501 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: M5A99FX PRO R2.0 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: 7354844-001 dmi.chassis.type: 3 dmi.chassis.vendor: NOVATECH LTD dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2501:bd04/07/2014:br4.6:svnNOVATECHLTD:pnMBB-895908:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnM5A99FXPROR2.0:rvrRev1.xx:cvnNOVATECHLTD:ct3:cvr1.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MBB-895908 dmi.product.sku: SKU dmi.product.version: 1.0 dmi.sys.vendor: NOVATECH LTD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1910480/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1910538] [NEW] Cannot set scale of screen
Public bug reported: I have 2 monitors a 2K monitor (2560x1440) and a 4k monitor (3840x2160) both 27inch Obviously to extend display correctly (join displays) I need to put my 4k monitor at scale of 125 and 2K monitor at 100% scale. I arrange two monitors side by side, then select 125% on 4K monitor (Fractional scaling is on) and click apply, both my monitors go to wrong scaling 2K goes to 50% and 4K goes to 200% and displays arrange bottom and top of each other. also login appears on wrong monitor (secondary) instead of selected primary ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/gpu0' .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/mig' .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 455.45.01 Thu Nov 5 23:03:56 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Jan 7 20:41:50 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 455.45.01, 5.4.0-42-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Subsystem: ASUSTeK Computer Inc. UHD Graphics 630 (Desktop) [1043:8694] NVIDIA Corporation TU104 [GeForce RTX 2070 SUPER] [10de:1e84] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ZOTAC International (MCO) Ltd. TU104 [GeForce RTX 2070 SUPER] [19da:4509] MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=e2e0340b-66fb-4930-908c-7e6767941743 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/26/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0229 dmi.board.asset.tag: Default string dmi.board.name: PRIME B360M-K dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0229:bd02/26/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB360M-K:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: ASUS_MB_CNL dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal third-party-packages ubuntu ** Attachment added: "Before clicking on Apply" https://bugs.launchpad.net/bugs/1910538/+attachment/5450200/+files/Screenshot%20from%202021-01-07%2020-51-50.png -- 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/1910538 Title: Cannot set scale of screen Status in xorg package in Ubuntu: New Bug description: I have 2 monitors a 2K monitor (2560x1440) and a 4k monitor (3840x2160) both 27inch Obviously to extend display correctly (join displays) I need to put my 4k monitor at scale of 125 and 2K monitor at 100% scale. I arrange two monitors side by side, then select 125% on 4K monitor (Fractional scaling is on) and click apply, both my monitors go to wrong scaling 2K goes to 50% and 4K goes to 200% and displays arrange bottom and top of each other. also login appears on wrong monitor (secondary) instead of selected primary ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu
[Touch-packages] [Bug 1910539] Re: Cannot set scale of screen
This is screenshot after clicking apply (to access print screen had to click keep changes button too) ** Attachment added: "After click on apply" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1910539/+attachment/5450246/+files/Screenshot%20from%202021-01-07%2020-52-00.png -- 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/1910539 Title: Cannot set scale of screen Status in xorg package in Ubuntu: New Bug description: I have 2 monitors a 2K monitor (2560x1440) and a 4k monitor (3840x2160) both 27inch Obviously to extend display correctly (join displays) I need to put my 4k monitor at scale of 125 and 2K monitor at 100% scale. I arrange two monitors side by side, then select 125% on 4K monitor (Fractional scaling is on) and click apply, both my monitors go to wrong scaling 2K goes to 50% and 4K goes to 200% and displays arrange bottom and top of each other. also login appears on wrong monitor (secondary) instead of selected primary ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/gpu0' .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/mig' .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 455.45.01 Thu Nov 5 23:03:56 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Jan 7 20:41:50 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 455.45.01, 5.4.0-42-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Subsystem: ASUSTeK Computer Inc. UHD Graphics 630 (Desktop) [1043:8694] NVIDIA Corporation TU104 [GeForce RTX 2070 SUPER] [10de:1e84] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ZOTAC International (MCO) Ltd. TU104 [GeForce RTX 2070 SUPER] [19da:4509] MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=e2e0340b-66fb-4930-908c-7e6767941743 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/26/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0229 dmi.board.asset.tag: Default string dmi.board.name: PRIME B360M-K dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0229:bd02/26/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB360M-K:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: ASUS_MB_CNL dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1910539/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1910539] [NEW] Cannot set scale of screen
Public bug reported: I have 2 monitors a 2K monitor (2560x1440) and a 4k monitor (3840x2160) both 27inch Obviously to extend display correctly (join displays) I need to put my 4k monitor at scale of 125 and 2K monitor at 100% scale. I arrange two monitors side by side, then select 125% on 4K monitor (Fractional scaling is on) and click apply, both my monitors go to wrong scaling 2K goes to 50% and 4K goes to 200% and displays arrange bottom and top of each other. also login appears on wrong monitor (secondary) instead of selected primary ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/gpu0' .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/mig' .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 455.45.01 Thu Nov 5 23:03:56 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Jan 7 20:41:50 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 455.45.01, 5.4.0-42-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Subsystem: ASUSTeK Computer Inc. UHD Graphics 630 (Desktop) [1043:8694] NVIDIA Corporation TU104 [GeForce RTX 2070 SUPER] [10de:1e84] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ZOTAC International (MCO) Ltd. TU104 [GeForce RTX 2070 SUPER] [19da:4509] MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=e2e0340b-66fb-4930-908c-7e6767941743 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/26/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0229 dmi.board.asset.tag: Default string dmi.board.name: PRIME B360M-K dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0229:bd02/26/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB360M-K:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: ASUS_MB_CNL dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal third-party-packages ubuntu ** Attachment added: "Before clicking on Apply" https://bugs.launchpad.net/bugs/1910539/+attachment/5450223/+files/Screenshot%20from%202021-01-07%2020-51-50.png -- 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/1910539 Title: Cannot set scale of screen Status in xorg package in Ubuntu: New Bug description: I have 2 monitors a 2K monitor (2560x1440) and a 4k monitor (3840x2160) both 27inch Obviously to extend display correctly (join displays) I need to put my 4k monitor at scale of 125 and 2K monitor at 100% scale. I arrange two monitors side by side, then select 125% on 4K monitor (Fractional scaling is on) and click apply, both my monitors go to wrong scaling 2K goes to 50% and 4K goes to 200% and displays arrange bottom and top of each other. also login appears on wrong monitor (secondary) instead of selected primary ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu
[Touch-packages] [Bug 1767654] Re: [Intel Braswell] Cursor gets stuck on left side of the screen
I'll also add that this problem is still present in kernel 5.8 (no matter if you use "modesetting" or "intel" driver for the Braswell GPU. My current setup: System:Kernel: 5.4.0-58-generic x86_64 bits: 64 compiler: gcc v: 9.3.0 Desktop: Cinnamon 4.6.7 wm: muffin dm: LightDM Distro: Linux Mint 20 Ulyana base: Ubuntu 20.04 focal Machine: Type: Desktop System: ASUSTeK product: E410 v: 0703 serial: Mobo: ASUSTeK model: E410 v: Rev 1.xx serial: UEFI: ASUSTeK (Licensed from AMI) v: 0703 date: 07/07/2017 CPU: Topology: Quad Core model: Intel Celeron N3150 bits: 64 type: MCP arch: Airmont rev: 3 L2 cache: 1024 KiB flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 12800 Speed: 1008 MHz min/max: 480/2080 MHz Core speeds (MHz): 1: 721 2: 1179 3: 2081 4: 2080 Graphics: Device-1: Intel Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:22b1 Display: x11 server: X.Org 1.20.8 driver: modesetting unloaded: fbdev,vesa resolution: 1920x1080~60Hz OpenGL: renderer: Mesa DRI Intel HD Graphics 400 (BSW) v: 4.6 Mesa 21.0.0-devel (git-7de1468 2021-01-01 focal-oibaf-ppa) compat-v: 3.0 direct render: Yes -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1767654 Title: [Intel Braswell] Cursor gets stuck on left side of the screen Status in Linux: New Status in gnome-shell package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: When moving the cursor to the left side of the screen, it stops close to the edge. The cursor still moves over in the area but invisible until I move it out of the area. When it doesn't do this, glitching occurs on the screen where the cursor is until I log out. And on screen cast it shows the cursor going to the side of the screen and moving. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Apr 28 09:49:51 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:22b1] (rev 21) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:2060] InstallationDate: Installed on 2018-04-27 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2a Intel Corp. Bus 001 Device 003: ID 05e3:0610 Genesys Logic, Inc. 4-port hub Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: \\boot\vmlinuz-4.15.0-20-generic root=UUID=c6f92850-287a-4747-ac0d-3af593994183 ro quiet splash vt.handoff=1 initrd=boot\initrd.img-4.15.0-20-generic SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/08/2017 dmi.bios.vendor: Intel Corp. dmi.bios.version: PYBSWCEL.86A.0062.2017.0308.1328 dmi.board.name: NUC5CPYB dmi.board.vendor: Intel Corporation dmi.board.version: H61145-408 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrPYBSWCEL.86A.0062.2017.0308.1328:bd03/08/2017:svn:pn:pvr:rvnIntelCorporation:rnNUC5CPYB:rvrH61145-408:cvn:ct3:cvr: 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 To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1767654/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post
[Touch-packages] [Bug 1767654] Re: [Intel Braswell] Cursor gets stuck on left side of the screen
@tonypanduru I'd like to share a slightly improved workaround on this for those still dealing with the issue. The core problem seems to be that the mouse cursor can go into a negative X position by one pixel when moved to the far left of the screen. With either the now obsolete intel proprietary driver or the current intel modesetting driver, this causes issues (exact symptoms are different for each, but seem to be from the same root cause). My previous workaround got by this by scaling the entire desktop to 99.99% of its former size. This prevented the cursor from getting to the -1 X position, but came at a cost of lost performance and some screen tearing in videos and games. This was due to a bilinear filter being applied by xrandr to the whole desktop to accommodate the slight re- size. The following command avoids this issue and instead merely shifts the entire desktop right one pixel. It still works around the issue, but seems to avoid the overhead of resizing the whole desktop (which preserves display integrity and performance). xrandr --output HDMI-3 --transform 1,0,-1,0,1,0,0,0,1 It would be nice to get a root cause fix for this, but this workaround seems to do the trick with very little downside. As before, replace the "HDMI-3" with the name of your active display (found by running xrandr with no options) and place the command in your ~/.xprofile (or make a startup app entry in your desktop manager). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1767654 Title: [Intel Braswell] Cursor gets stuck on left side of the screen Status in Linux: New Status in gnome-shell package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: When moving the cursor to the left side of the screen, it stops close to the edge. The cursor still moves over in the area but invisible until I move it out of the area. When it doesn't do this, glitching occurs on the screen where the cursor is until I log out. And on screen cast it shows the cursor going to the side of the screen and moving. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Apr 28 09:49:51 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:22b1] (rev 21) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:2060] InstallationDate: Installed on 2018-04-27 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2a Intel Corp. Bus 001 Device 003: ID 05e3:0610 Genesys Logic, Inc. 4-port hub Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: \\boot\vmlinuz-4.15.0-20-generic root=UUID=c6f92850-287a-4747-ac0d-3af593994183 ro quiet splash vt.handoff=1 initrd=boot\initrd.img-4.15.0-20-generic SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/08/2017 dmi.bios.vendor: Intel Corp. dmi.bios.version: PYBSWCEL.86A.0062.2017.0308.1328 dmi.board.name: NUC5CPYB dmi.board.vendor: Intel Corporation dmi.board.version: H61145-408 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrPYBSWCEL.86A.0062.2017.0308.1328:bd03/08/2017:svn:pn:pvr:rvnIntelCorporation:rnNUC5CPYB:rvrH61145-408:cvn:ct3:cvr: 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 To manage notifications about this bug go to:
[Touch-packages] [Bug 1877640] Re: [Zephyrus M GU502GV_GU502GV, Realtek ALC294] No sound in 3.5mm jack headphones.
Same issue with GU502GU with Mint or Pop OS -- 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/1877640 Title: [Zephyrus M GU502GV_GU502GV, Realtek ALC294] No sound in 3.5mm jack headphones. Status in alsa-driver package in Ubuntu: Confirmed Bug description: Ubuntu 18.04.4 LTS dual boot with Windows 10. On Windows all is fine. On Ubuntu i have sound for speakers, but no sound at all for 3.5mm jack headphones. Tried using latest kernel versions for 4.*, 5.*, tried even 5.7-rc4. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 Uname: Linux 5.6.11-050611-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: corsarstl 1728 F pulseaudio /dev/snd/pcmC0D0p: corsarstl 1728 F...m pulseaudio /dev/snd/controlC1: corsarstl 1728 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri May 8 20:25:27 2020 InstallationDate: Installed on 2020-05-07 (0 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1227 F pulseaudio corsarstl 1728 F pulseaudio /dev/snd/controlC1: gdm1227 F pulseaudio corsarstl 1728 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: No sound at all Title: [Zephyrus M GU502GV_GU502GV, Realtek ALC294, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/15/2020 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GU502GV.307 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GU502GV dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGU502GV.307:bd02/15/2020:svnASUSTeKCOMPUTERINC.:pnZephyrusMGU502GV_GU502GV:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGU502GV:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: Zephyrus M dmi.product.name: Zephyrus M GU502GV_GU502GV dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1877640/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1448657] Re: isc-dhcp-server: Can't create PID file /run/dhcp-server/dhcpd.pid: Permission denied
Same problem encountered on Ubuntu 20.04. Fixed after I ran `sudo systemctl mask isc-dhcp-server6.service` -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1448657 Title: isc-dhcp-server: Can't create PID file /run/dhcp-server/dhcpd.pid: Permission denied Status in isc-dhcp package in Ubuntu: Confirmed Bug description: Just upgraded from 14-10 to 15-04, and now see the following in syslog: Apr 26 10:50:08 server kernel: [70470.960718] audit: type=1400 audit(1430045408.725:8): apparmor="DENIED" operation="capable" profile="/usr/sbin/dhcpd" pid=8619 comm="dhcpd" capability=1 capname="dac_ove rride" Apr 26 10:50:08 server sh[8619]: Can't create PID file /run/dhcp-server/dhcpd.pid: Permission denied. Description:Ubuntu 15.04 Release:15.04 isc-dhcp-server: Installed: 4.3.1-5ubuntu2 --- 8x - # cat /etc/default/isc-dhcp-server # Defaults for isc-dhcp-server initscript # sourced by /etc/init.d/isc-dhcp-server # installed at /etc/default/isc-dhcp-server by the maintainer scripts # # This is a POSIX shell fragment # # Path to dhcpd's config file (default: /etc/dhcp/dhcpd.conf). #DHCPD_CONF=/etc/dhcp/dhcpd.conf # Path to dhcpd's PID file (default: /var/run/dhcpd.pid). #DHCPD_PID=/var/run/dhcpd.pid # Additional options to start dhcpd with. # Don't use options -cf or -pf here; use DHCPD_CONF/ DHCPD_PID instead #OPTIONS="" # On what interfaces should the DHCP server (dhcpd) serve DHCP requests? # Separate multiple interfaces with spaces, e.g. "eth0 eth1". INTERFACES="" --- 8x - # ls -la /var/run lrwxrwxrwx 1 root root 4 Oct 24 2013 /var/run -> /run # ls -la /run/dhcp-server/ total 0 drwxr-xr-x 2 dhcpd dhcpd 40 Apr 26 10:59 . drwxr-xr-x 34 root root 1060 Apr 26 11:33 .. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1448657/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1885309] [NEW] package lsb-security 9.20160110ubuntu0.2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configu
Public bug reported: I leave only acknowledgement that I am not fully competent to discern linux issues. My hope is that the additional debug information will provide the details that I can't see. I am relatively competent and comfortable with sysadm-level unix activities, so I'm sure I can execute instructions if provided. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: lsb-security 9.20160110ubuntu0.2 ProcVersionSignature: Ubuntu 4.4.0-179.209-generic 4.4.219 Uname: Linux 4.4.0-179-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.23 Architecture: amd64 Date: Fri Jun 26 12:17:52 2020 DuplicateSignature: package:lsb-security:9.20160110ubuntu0.2 Setting up libnss3:amd64 (2:3.28.4-0ubuntu0.16.04.11) ... dpkg: error processing package lsb-security (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2016-08-14 (1411 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) RelatedPackageVersions: dpkg 1.18.4ubuntu1.6 apt 1.2.32ubuntu0.1 SourcePackage: lsb Title: package lsb-security 9.20160110ubuntu0.2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: lsb (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lsb in Ubuntu. https://bugs.launchpad.net/bugs/1885309 Title: package lsb-security 9.20160110ubuntu0.2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in lsb package in Ubuntu: New Bug description: I leave only acknowledgement that I am not fully competent to discern linux issues. My hope is that the additional debug information will provide the details that I can't see. I am relatively competent and comfortable with sysadm-level unix activities, so I'm sure I can execute instructions if provided. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: lsb-security 9.20160110ubuntu0.2 ProcVersionSignature: Ubuntu 4.4.0-179.209-generic 4.4.219 Uname: Linux 4.4.0-179-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.23 Architecture: amd64 Date: Fri Jun 26 12:17:52 2020 DuplicateSignature: package:lsb-security:9.20160110ubuntu0.2 Setting up libnss3:amd64 (2:3.28.4-0ubuntu0.16.04.11) ... dpkg: error processing package lsb-security (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2016-08-14 (1411 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) RelatedPackageVersions: dpkg 1.18.4ubuntu1.6 apt 1.2.32ubuntu0.1 SourcePackage: lsb Title: package lsb-security 9.20160110ubuntu0.2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lsb/+bug/1885309/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1882864] [NEW] [Latitude 5280, Realtek ALC3253, Speaker, Internal] No sound at all
Public bug reported: It used to work just fine but after some update/change audio only works via HDMI but not through the built-in speaker or audio port anymore. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-101.102-generic 4.15.18 Uname: Linux 4.15.0-101-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Jun 10 11:50:21 2020 EcryptfsInUse: Yes InstallationDate: Installed on 2018-02-24 (836 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.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_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [Latitude 5280, Realtek ALC3253, Speaker, Internal] No sound at all UpgradeStatus: Upgraded to bionic on 2018-09-09 (639 days ago) dmi.bios.date: 08/07/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.3 dmi.board.name: 049W7N dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.3:bd08/07/2017:svnDellInc.:pnLatitude5280:pvr:rvnDellInc.:rn049W7N:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 5280 dmi.sys.vendor: Dell Inc. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1882864 Title: [Latitude 5280, Realtek ALC3253, Speaker, Internal] No sound at all Status in alsa-driver package in Ubuntu: New Bug description: It used to work just fine but after some update/change audio only works via HDMI but not through the built-in speaker or audio port anymore. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-101.102-generic 4.15.18 Uname: Linux 4.15.0-101-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Jun 10 11:50:21 2020 EcryptfsInUse: Yes InstallationDate: Installed on 2018-02-24 (836 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.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_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [Latitude 5280, Realtek ALC3253, Speaker, Internal] No sound at all UpgradeStatus: Upgraded to bionic on 2018-09-09 (639 days ago) dmi.bios.date: 08/07/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.3 dmi.board.name: 049W7N dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.3:bd08/07/2017:svnDellInc.:pnLatitude5280:pvr:rvnDellInc.:rn049W7N:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 5280 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1882864/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1767654] Re: [Intel Braswell] Cursor gets stuck on left side of the screen
I can confirm that the problem is present with both the intel and the modesetting driver on Braswell systems. The exact symptoms differ for each, but in both cases it is triggered when the mouse touches the left limit of the screen. With modesetting, it seems to "stick" until you move the mouse away from the left side. With intel, touching the left side starts a flickering that persists even after you move the mouse away. Mainly, just the mouse cursor flickers, but the whole screen will flicker when doing graphics intensive tasks like fullscreen video or gaming. Sometimes, the mouse flicker can be so bad it becomes nearly invisible. I have made full report on the bug report thread opened by Salvatore. The good news is I found a workaround, you can use xrandr to scale the display to 0.x0. and this prevents the issues in both intel and modesetting. This can be done in your .xprofile in your home directory to take effect at login. It does come with a slight performance penalty, but it's preferable to the glitching that happens otherwise (at least until someone fixes the regression). xrandr --output HDMI-3 --mode 1920x1080 --scale 0.x0. Replace "HDMI-3" with the name of your display (can be found by running xrandr with no options). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1767654 Title: [Intel Braswell] Cursor gets stuck on left side of the screen Status in Linux: New Status in gnome-shell package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: When moving the cursor to the left side of the screen, it stops close to the edge. The cursor still moves over in the area but invisible until I move it out of the area. When it doesn't do this, glitching occurs on the screen where the cursor is until I log out. And on screen cast it shows the cursor going to the side of the screen and moving. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Apr 28 09:49:51 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:22b1] (rev 21) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:2060] InstallationDate: Installed on 2018-04-27 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2a Intel Corp. Bus 001 Device 003: ID 05e3:0610 Genesys Logic, Inc. 4-port hub Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: \\boot\vmlinuz-4.15.0-20-generic root=UUID=c6f92850-287a-4747-ac0d-3af593994183 ro quiet splash vt.handoff=1 initrd=boot\initrd.img-4.15.0-20-generic SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/08/2017 dmi.bios.vendor: Intel Corp. dmi.bios.version: PYBSWCEL.86A.0062.2017.0308.1328 dmi.board.name: NUC5CPYB dmi.board.vendor: Intel Corporation dmi.board.version: H61145-408 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrPYBSWCEL.86A.0062.2017.0308.1328:bd03/08/2017:svn:pn:pvr:rvnIntelCorporation:rnNUC5CPYB:rvrH61145-408:cvn:ct3:cvr: 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 To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1767654/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe :
[Touch-packages] [Bug 1875037] [NEW] Display Bug
Public bug reported: When going to Settings -> Universal Access and selecting "High Contrast" to view the difference in appearance, then switching "High Contrast" to off, the icons do not return to their normal appearance. I did not find a place in this bug submission interface to submit attachments or I would show you screen capture of the changes in the icon appearance. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Apr 25 10:48:21 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 630 (Desktop) [8086:3e92] (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd UHD Graphics 630 (Desktop) [1458:d000] InstallationDate: Installed on 2020-03-31 (24 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200330) MachineType: Gigabyte Technology Co., Ltd. H370 WIFI ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic root=UUID=8d24e3f8-c08c-444a-8467-4f9473fa4a22 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/05/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F14 dmi.board.asset.tag: Default string dmi.board.name: H370N WIFI-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF14:bd06/05/2019:svnGigabyteTechnologyCo.,Ltd.:pnH370WIFI:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnH370NWIFI-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: H370 WIFI dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug corruption focal ubuntu ** Attachment added: "Altered_appearance.png" https://bugs.launchpad.net/bugs/1875037/+attachment/5360327/+files/Altered_appearance.png -- 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/1875037 Title: Display Bug Status in xorg package in Ubuntu: New Bug description: When going to Settings -> Universal Access and selecting "High Contrast" to view the difference in appearance, then switching "High Contrast" to off, the icons do not return to their normal appearance. I did not find a place in this bug submission interface to submit attachments or I would show you screen capture of the changes in the icon appearance. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Apr 25 10:48:21 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 630 (Desktop) [8086:3e92] (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd UHD Graphics 630 (Desktop) [1458:d000] InstallationDate: Installed on 2020-03-31 (24 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200330) MachineType: Gigabyte Technology Co., Ltd. H370 WIFI ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic root=UUID=8d24e3f8-c08c-444a-8467-4f9473fa4a22 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus:
[Touch-packages] [Bug 1030489] Re: Additional Drivers says Wifi is not in use when using open driver
Similar in Ubuntu 20.04 final beta. Shows "This device is not working" and "Do not use device" is selected (and grayed out), but wireless is working. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1030489 Title: Additional Drivers says Wifi is not in use when using open driver Status in software-properties package in Ubuntu: Confirmed Bug description: Hello, I have an internal wifi card BCM43224 and I am using the open-source driver brcmsmac. In Ubuntu Quantal, Additional Drivers says that "The Device is not working" instead of offering the brcmsmac driver. $ lsb_release -rd Description: Ubuntu quantal (development branch) Release: 12.10 $ apt-cache policy software-properties-common software-properties-common: Installed: 0.91 Candidate: 0.91 Version table: *** 0.91 0 500 http://archive.ubuntu.com/ubuntu/ quantal/main amd64 Packages 100 /var/lib/dpkg/status Regards, Aurélien To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1030489/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1868573] [NEW] package libpng12-0 1.2.54-1ubuntu1 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libpng12-0/changelog.Debian.gz', which is different from o
*** This bug is a duplicate of bug 1799215 *** https://bugs.launchpad.net/bugs/1799215 Public bug reported: None ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libpng12-0 1.2.54-1ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-176.206-generic 4.4.211 Uname: Linux 4.4.0-176-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.22 Architecture: amd64 Date: Sun Mar 22 19:46:57 2020 Dependencies: gcc-6-base 6.0.1-0ubuntu1 libc6 2.23-0ubuntu11 libgcc1 1:6.0.1-0ubuntu1 zlib1g 1:1.2.8.dfsg-2ubuntu4.3 DpkgTerminalLog: Preparing to unpack .../libpng12-0_1.2.54-1ubuntu1.1_amd64.deb ... Unpacking libpng12-0:amd64 (1.2.54-1ubuntu1.1) over (1.2.54-1ubuntu1) ... dpkg: error processing archive /var/cache/apt/archives/libpng12-0_1.2.54-1ubuntu1.1_amd64.deb (--unpack): trying to overwrite shared '/usr/share/doc/libpng12-0/changelog.Debian.gz', which is different from other instances of package libpng12-0:amd64 DuplicateSignature: package:libpng12-0:1.2.54-1ubuntu1 Unpacking libpng12-0:amd64 (1.2.54-1ubuntu1.1) over (1.2.54-1ubuntu1) ... dpkg: error processing archive /var/cache/apt/archives/libpng12-0_1.2.54-1ubuntu1.1_amd64.deb (--unpack): trying to overwrite shared '/usr/share/doc/libpng12-0/changelog.Debian.gz', which is different from other instances of package libpng12-0:amd64 ErrorMessage: trying to overwrite shared '/usr/share/doc/libpng12-0/changelog.Debian.gz', which is different from other instances of package libpng12-0:amd64 InstallationDate: Installed on 2016-12-31 (1177 days ago) InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 (20160217.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1.6 apt 1.2.32 SourcePackage: libpng Title: package libpng12-0 1.2.54-1ubuntu1 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libpng12-0/changelog.Debian.gz', which is different from other instances of package libpng12-0:amd64 UpgradeStatus: Upgraded to xenial on 2017-01-01 (1177 days ago) ** Affects: libpng (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package package-conflict xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libpng in Ubuntu. https://bugs.launchpad.net/bugs/1868573 Title: package libpng12-0 1.2.54-1ubuntu1 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libpng12-0/changelog.Debian.gz', which is different from other instances of package libpng12-0:amd64 Status in libpng package in Ubuntu: New Bug description: None ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libpng12-0 1.2.54-1ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-176.206-generic 4.4.211 Uname: Linux 4.4.0-176-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.22 Architecture: amd64 Date: Sun Mar 22 19:46:57 2020 Dependencies: gcc-6-base 6.0.1-0ubuntu1 libc6 2.23-0ubuntu11 libgcc1 1:6.0.1-0ubuntu1 zlib1g 1:1.2.8.dfsg-2ubuntu4.3 DpkgTerminalLog: Preparing to unpack .../libpng12-0_1.2.54-1ubuntu1.1_amd64.deb ... Unpacking libpng12-0:amd64 (1.2.54-1ubuntu1.1) over (1.2.54-1ubuntu1) ... dpkg: error processing archive /var/cache/apt/archives/libpng12-0_1.2.54-1ubuntu1.1_amd64.deb (--unpack): trying to overwrite shared '/usr/share/doc/libpng12-0/changelog.Debian.gz', which is different from other instances of package libpng12-0:amd64 DuplicateSignature: package:libpng12-0:1.2.54-1ubuntu1 Unpacking libpng12-0:amd64 (1.2.54-1ubuntu1.1) over (1.2.54-1ubuntu1) ... dpkg: error processing archive /var/cache/apt/archives/libpng12-0_1.2.54-1ubuntu1.1_amd64.deb (--unpack): trying to overwrite shared '/usr/share/doc/libpng12-0/changelog.Debian.gz', which is different from other instances of package libpng12-0:amd64 ErrorMessage: trying to overwrite shared '/usr/share/doc/libpng12-0/changelog.Debian.gz', which is different from other instances of package libpng12-0:amd64 InstallationDate: Installed on 2016-12-31 (1177 days ago) InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 (20160217.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1.6 apt 1.2.32 SourcePackage: libpng Title: package libpng12-0 1.2.54-1ubuntu1 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libpng12-0/changelog.Debian.gz', which is different from other instances of package libpng12-0:amd64 UpgradeStatus: Upgraded to xenial on 2017-01-01 (1177 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libpng/+bug/1868573/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1868128] [NEW] (Error ID: OOPS-f9a25a1047f367bba335ebdf6c9c0a24)
Public bug reported: trying to reinstall my Ubuntu 18.04 on my Toshiba Satelite 64 bus laptop. I have a loaded flash drive but I keep getting an error message as follows, (Error ID: OOPS-f9a25a1047f367bba335ebdf6c9c0a24) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-91.92-generic 4.15.18 Uname: Linux 4.15.0-91-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.12 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Thu Mar 19 08:43:35 2020 DistUpgraded: 2018-09-05 15:50:48,221 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems 4th Gen Core Processor Integrated Graphics Controller [1179:fa22] InstallationDate: Installed on 2017-04-18 (1065 days ago) InstallationMedia: Ubuntu-GNOME 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: TOSHIBA Satellite C55t-A ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-91-generic root=UUID=1be49583-6218-4da2-9204-c5ae2ac5cebd ro drm.debug=0xe plymouth:debug Renderer: Software SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2018-09-05 (560 days ago) dmi.bios.date: 01/24/2014 dmi.bios.vendor: Insyde Corp. dmi.bios.version: 1.70 dmi.board.name: Portable PC dmi.board.vendor: TOSHIBA dmi.board.version: MP dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: OEM Chassis Manufacturer dmi.chassis.version: OEM Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvr1.70:bd01/24/2014:svnTOSHIBA:pnSatelliteC55t-A:pvrPSCFJU-00T00J:rvnTOSHIBA:rnPortablePC:rvrMP:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion: dmi.product.family: Durban-Curiosity 10S/10SG dmi.product.name: Satellite C55t-A dmi.product.version: PSCFJU-00T00J dmi.sys.vendor: TOSHIBA version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 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 xserver.bootTime: Tue Jun 27 12:22:02 2017 xserver.configfile: default xserver.errors: open /dev/dri/card0: No such file or directory open /dev/dri/card0: No such file or directory Screen 0 deleted because of no matching config section. AIGLX: reverting to software rendering xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.18.4-0ubuntu0.2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic third-party-packages 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/1868128 Title: (Error ID: OOPS-f9a25a1047f367bba335ebdf6c9c0a24) Status in xorg package in Ubuntu: New Bug description: trying to reinstall my Ubuntu 18.04 on my Toshiba Satelite 64 bus laptop. I have a loaded flash drive but I keep getting an error message as follows, (Error ID: OOPS-f9a25a1047f367bba335ebdf6c9c0a24) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-91.92-generic 4.15.18 Uname: Linux 4.15.0-91-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.12 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Thu Mar 19 08:43:35 2020 DistUpgraded: 2018-09-05 15:50:48,221 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems 4th Gen Core Processor Integrated Graphics Controller [1179:fa22] InstallationDate: Installed on 2017-04-18 (1065 days ago) InstallationMedia: Ubuntu-GNOME 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: TOSHIBA Satellite C55t-A ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-91-generic root=UUID=1be49583-6218-4da2-9204-c5ae2ac5cebd ro drm.debug=0xe plymouth:debug Renderer: Software SourcePackage:
[Touch-packages] [Bug 1574120] Re: Notebook doesn't suspend when lid is closed after update to 16.04
@unusedusername I found a snippet somewhere that helped me do things when my lid is closed (or rather when the session is locked). Since your laptop switches to airplane mode something is detecting it so maybe this helps. Put this in a script and run it, then close lid and open lid. Do you get any output? #!/bin/sh iface=org.freedesktop.login1.Session dbus-monitor --system --profile "type=signal,interface=$iface" 2>/dev/null | while read type stamp sender dest path intf member; do case "$member" in *Lock) date echo LOCKED at $stamp ;; *Unlock) date echo UNLOCKED at $stamp ;; *) esac done If it works you could even insert a suspend command and run this in the background to avoid having to use the mouse. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pm-utils in Ubuntu. https://bugs.launchpad.net/bugs/1574120 Title: Notebook doesn't suspend when lid is closed after update to 16.04 Status in pm-utils package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Bug description: My notebook does not suspend after upgrading from 15.10 to 16.04. According to system settings the notebook should suspend when lid is closed but actually this does not happen. Instead it continues to run as if nothing had happened. With the previous versions of ubuntu (14.04-15.10) everything worked fine. My System: HP Pavilion dv7. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: acpi (not installed) ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Sat Apr 23 23:11:15 2016 InstallationDate: Installed on 2015-10-29 (176 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: acpi UpgradeStatus: Upgraded to xenial on 2016-04-22 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pm-utils/+bug/1574120/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 994921] Re: 'ubuntu-bug /var/crash/app.crash' (and even more so, 'apport-cli -c /var/crash/app.crash') should still allow manual bug filing in stable releases
On 2018-11-12, Chao MENG wrote:
> Hello guys,
> I meet a bug when using input method, I drag the input method dialog onto the
> top bar of GNOME, and then I can't drag it anymore; please see the attached
> screenshot ubuntu_input_method_bug.PNG
>
> Sorry that I report a bug here, but I really can't find a place to
> report a bug, I am working and really don't have much time to check
> carefully a so long document
> https://help.ubuntu.com/community/ReportingBugs
>
> ** Attachment added: "ubuntu_input_method_bug.PNG"
>
> https://bugs.launchpad.net/ubuntu/+source/apport/+bug/994921/+attachment/5211824/+files/ubuntu_input_method_bug.PNG
Hi Chao,
Your report is useless here, hence I've removed your attachment, sorry.
* If you know the package name of your "input method" program, please
execute somthing like "ubuntu-bug your_package_name_here" from the terminal.
* If you, unfortunately, don't know that, please execute "ubuntu-bug -w"
from the terminal and follow the instruction (close the intro message
box and click on the window of your "input method" program etc.)
References:
*
https://help.ubuntu.com/community/ReportingBugs#Collecting_information_from_a_specific_package
*
https://help.ubuntu.com/community/ReportingBugs#Collecting_information_about_a_program_with_a_window_open
--
Best wishes,
Bob
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/994921
Title:
'ubuntu-bug /var/crash/app.crash' (and even more so, 'apport-cli -c
/var/crash/app.crash') should still allow manual bug filing in stable
releases
Status in apport package in Ubuntu:
Won't Fix
Status in apport source package in Precise:
Won't Fix
Status in apport source package in Quantal:
Won't Fix
Bug description:
---
WORKAROUND:
comment out line 23 ("'problem_types': ['Bug', 'Package'],") in
'/etc/apport/crashdb.conf'.
---
The crash database work has made it much harder for users to enable apport
bug filing for crashes in stable Ubuntu releases, even for those who could
otherwise contribute useful bug reports. "Comment out line 23 of
/etc/apport/crashdb.conf" is not particularly straightforward.
One thing that would mitigate this is if the users could still run one of the
following commands to manually submit a bug report about a given crash:
1) 'ubuntu-bug /var/crash/application.crash';
2) and even more so, 'apport-cli -c /var/crash/app.crash' (as for now, it
quietly exits without explanation after pressing the 'S' key instead of sending
a crash report, as stated in duplicate bug #992064).
The fact that this is also disabled by the crashdb settings is a tad
inconvenient. I think the manual command should be allowed to work even
post-release.
---
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: apport 2.0.1-0ubuntu7
ProcVersionSignature: Ubuntu 3.2.0-24.37-generic 3.2.14
Uname: Linux 3.2.0-24-generic x86_64
ApportVersion: 2.0.1-0ubuntu7
Architecture: amd64
CheckboxSubmission: 017452a27eca3c8b498abbfa5ef91db9
CheckboxSystem: ecaaad6fa1e0799a0aa1126bf620f39e
Date: Fri May 4 17:17:43 2012
InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64
(20100816.1)
PackageArchitecture: all
ProcEnviron:
TERM=xterm
PATH=(custom, user)
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: apport
UpgradeStatus: Upgraded to precise on 2011-11-08 (178 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/994921/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 994921] Re: 'ubuntu-bug /var/crash/app.crash' (and even more so, 'apport-cli -c /var/crash/app.crash') should still allow manual bug filing in stable releases
** Attachment removed: "ubuntu_input_method_bug.PNG"
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/994921/+attachment/5211824/+files/ubuntu_input_method_bug.PNG
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/994921
Title:
'ubuntu-bug /var/crash/app.crash' (and even more so, 'apport-cli -c
/var/crash/app.crash') should still allow manual bug filing in stable
releases
Status in apport package in Ubuntu:
Won't Fix
Status in apport source package in Precise:
Won't Fix
Status in apport source package in Quantal:
Won't Fix
Bug description:
---
WORKAROUND:
comment out line 23 ("'problem_types': ['Bug', 'Package'],") in
'/etc/apport/crashdb.conf'.
---
The crash database work has made it much harder for users to enable apport
bug filing for crashes in stable Ubuntu releases, even for those who could
otherwise contribute useful bug reports. "Comment out line 23 of
/etc/apport/crashdb.conf" is not particularly straightforward.
One thing that would mitigate this is if the users could still run one of the
following commands to manually submit a bug report about a given crash:
1) 'ubuntu-bug /var/crash/application.crash';
2) and even more so, 'apport-cli -c /var/crash/app.crash' (as for now, it
quietly exits without explanation after pressing the 'S' key instead of sending
a crash report, as stated in duplicate bug #992064).
The fact that this is also disabled by the crashdb settings is a tad
inconvenient. I think the manual command should be allowed to work even
post-release.
---
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: apport 2.0.1-0ubuntu7
ProcVersionSignature: Ubuntu 3.2.0-24.37-generic 3.2.14
Uname: Linux 3.2.0-24-generic x86_64
ApportVersion: 2.0.1-0ubuntu7
Architecture: amd64
CheckboxSubmission: 017452a27eca3c8b498abbfa5ef91db9
CheckboxSystem: ecaaad6fa1e0799a0aa1126bf620f39e
Date: Fri May 4 17:17:43 2012
InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64
(20100816.1)
PackageArchitecture: all
ProcEnviron:
TERM=xterm
PATH=(custom, user)
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: apport
UpgradeStatus: Upgraded to precise on 2011-11-08 (178 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/994921/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1797602] [NEW] systemd incompatible with openresolv and dnsmasq
Public bug reported: Problem: systemd breaks resolvconf-dependent DNS Test case: Install dnsmasq with systemd. Result: The script in /etc/dhcp/dhclient-enter-hooks.d/resolvconf defines the make_resolv_conf() function to pass DHCP information to the /sbin/resolvconf program. The script in /etc/dhcp/dhclient-enter-hooks.d/resolved redefines the make_resolv_conf() function to write DHCP information to /run/systemd/resolved.conf.d/isc-dhcp-v4-$interface.conf As a result, resolvconf never runs, and dnsmasq never receives the DHCP-supplied nameservers. Therefore, DNS resolution is broken. Expected result: DHCP-supplied nameservers should be passed to both resolvconf and to systemd. Workaround: Use the 127.0.0.53 address for the systemd resolver as the dnsmasq upstream server. lsb_release -rd output: Description:Ubuntu 18.04.1 LTS Release:18.04 ** Affects: systemd (Ubuntu) Importance: Undecided Status: New -- 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/1797602 Title: systemd incompatible with openresolv and dnsmasq Status in systemd package in Ubuntu: New Bug description: Problem: systemd breaks resolvconf-dependent DNS Test case: Install dnsmasq with systemd. Result: The script in /etc/dhcp/dhclient-enter-hooks.d/resolvconf defines the make_resolv_conf() function to pass DHCP information to the /sbin/resolvconf program. The script in /etc/dhcp/dhclient-enter-hooks.d/resolved redefines the make_resolv_conf() function to write DHCP information to /run/systemd/resolved.conf.d/isc-dhcp-v4-$interface.conf As a result, resolvconf never runs, and dnsmasq never receives the DHCP-supplied nameservers. Therefore, DNS resolution is broken. Expected result: DHCP-supplied nameservers should be passed to both resolvconf and to systemd. Workaround: Use the 127.0.0.53 address for the systemd resolver as the dnsmasq upstream server. lsb_release -rd output: Description:Ubuntu 18.04.1 LTS Release:18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1797602/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1778464] Re: package ifupdown 0.8.17ubuntu1.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration
This is happening very often - I attempt to load an app and the load fails due to the reported issue. I have not reported this every time it has happened - if I did, you would be hearing from me quite often. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ifupdown in Ubuntu. https://bugs.launchpad.net/bugs/1778464 Title: package ifupdown 0.8.17ubuntu1.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in ifupdown package in Ubuntu: New Bug description: This came about while attempting to insstall VLC from Ubuntu software. The process returned the error and the above summary. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: ifupdown 0.8.17ubuntu1.1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Mon Jun 25 01:19:12 2018 DuplicateSignature: package:ifupdown:0.8.17ubuntu1.1 Setting up ubuntu-software (3.28.1-0ubuntu4.18.04.1) ... dpkg: error processing package ifupdown (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2018-06-24 (1 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.1 SourcePackage: ifupdown Title: package ifupdown 0.8.17ubuntu1.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1778464/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1778464] [NEW] package ifupdown 0.8.17ubuntu1.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration
Public bug reported: This came about while attempting to insstall VLC from Ubuntu software. The process returned the error and the above summary. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: ifupdown 0.8.17ubuntu1.1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Mon Jun 25 01:19:12 2018 DuplicateSignature: package:ifupdown:0.8.17ubuntu1.1 Setting up ubuntu-software (3.28.1-0ubuntu4.18.04.1) ... dpkg: error processing package ifupdown (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2018-06-24 (1 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.1 SourcePackage: ifupdown Title: package ifupdown 0.8.17ubuntu1.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ifupdown (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ifupdown in Ubuntu. https://bugs.launchpad.net/bugs/1778464 Title: package ifupdown 0.8.17ubuntu1.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in ifupdown package in Ubuntu: New Bug description: This came about while attempting to insstall VLC from Ubuntu software. The process returned the error and the above summary. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: ifupdown 0.8.17ubuntu1.1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Mon Jun 25 01:19:12 2018 DuplicateSignature: package:ifupdown:0.8.17ubuntu1.1 Setting up ubuntu-software (3.28.1-0ubuntu4.18.04.1) ... dpkg: error processing package ifupdown (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2018-06-24 (1 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.1 SourcePackage: ifupdown Title: package ifupdown 0.8.17ubuntu1.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1778464/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1579580] Re: ureadahead reports relative path errors in journalctl output
Same on Ubuntu 17.10 with the latest updates and encrypted file system. During boot the process stops at the Ubuntu label with the 5 dots and does nothing else, but generates these messages. Apr 17 19:54:33 L5280 sudo: pam_ecryptfs: pam_sm_authenticate: /home/user1 is already mounted Apr 17 19:54:39 L5280 systemd[1]: Starting Stop ureadahead data collection... Apr 17 19:54:39 L5280 systemd[1]: Stopping Read required files in advance... Apr 17 19:54:39 L5280 systemd[1]: Started Stop ureadahead data collection. Apr 17 19:54:39 L5280 ureadahead[411]: ureadahead:events/fs/open_exec/enable: Ignored relative path Apr 17 19:54:39 L5280 ureadahead[411]: ureadahead:buffer_size_kb: Ignored relative path Apr 17 19:54:39 L5280 ureadahead[411]: ureadahead:tracing_on: Ignored relative path Apr 17 19:54:39 L5280 ureadahead[411]: ureadahead:: Ignored relative path Apr 17 19:54:39 L5280 ureadahead[411]: ureadahead:etc: Ignored relative path Apr 17 19:54:39 L5280 ureadahead[411]: ureadahead:systemd: Ignored relative path Apr 17 19:54:39 L5280 ureadahead[411]: ureadahead:network: Ignored relative path Apr 17 19:54:39 L5280 ureadahead[411]: ureadahead:: Ignored relative path Apr 17 19:54:39 L5280 ureadahead[411]: ureadahead:run: Ignored relative path Apr 17 19:54:39 L5280 ureadahead[411]: ureadahead:systemd: Ignored relative path Apr 17 19:54:39 L5280 ureadahead[411]: ureadahead:: Ignored relative path Apr 17 19:54:39 L5280 ureadahead[411]: ureadahead:usr: Ignored relative path Apr 17 19:54:39 L5280 ureadahead[411]: ureadahead:lib: Ignored relative path Apr 17 19:54:39 L5280 ureadahead[411]: ureadahead:systemd: Ignored relative path Apr 17 19:54:40 L5280 ureadahead[411]: message repeated 2 times: [ ureadahead:class: Ignored relative path] Apr 17 19:54:40 L5280 ureadahead[411]: ureadahead:dmi: Ignored relative path Apr 17 19:54:40 L5280 ureadahead[411]: message repeated 2 times: [ ureadahead:dmi: Ignored relative path] Apr 17 19:54:40 L5280 ureadahead[411]: ureadahead:..: Ignored relative path Apr 17 19:54:40 L5280 ureadahead[411]: message repeated 4 times: [ ureadahead:..: Ignored relative path] And no login screen. I had to hard reset the Dell Latitude 5280 at least 4-5 times before it could proceed to the login screen. ubuntu--vg-swap_1: 0 66871296 linear cryptswap1: 0 66870272 crypt ubuntu--vg-root: 0 907337728 linear sda3_crypt: 0 974217216 crypt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ureadahead in Ubuntu. https://bugs.launchpad.net/bugs/1579580 Title: ureadahead reports relative path errors in journalctl output Status in ureadahead package in Ubuntu: Confirmed Bug description: ureadahead reports relative path errors in my journalctl output. This is currently 4368 lines of useless annoyances in my logs. To see if you have this problem, run: journalctl -b | grep ureadahead | grep relative | wc -l Thanks ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ureadahead 0.100.0-19 ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 Date: Sun May 8 15:55:18 2016 InstallationDate: Installed on 2016-04-04 (34 days ago) InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Beta amd64 (20160325) ProcEnviron: TERM=linux PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ureadahead UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ureadahead/+bug/1579580/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1703377] Re: Gnome online account login prevents paste or autotype
This is reported as a bug in Gnome's bugzilla: https://bugzilla.gnome.org/show_bug.cgi?id=778662 ** Bug watch added: GNOME Bug Tracker #778662 https://bugzilla.gnome.org/show_bug.cgi?id=778662 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1703377 Title: Gnome online account login prevents paste or autotype Status in gnome-online-accounts package in Ubuntu: Confirmed Bug description: On entering Login data to an online account such as google. Using keepass as password manager I now can not enter my password via paste nor via autotype. Trying any of them results in an invalid password. Ubuntu 16.10 - GNOME Shell 3.20.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1703377/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1610517] Re: package hicolo-icon-theme 0.15-ubuntu1 failed to install: upgrade triggers looping
-networking-common_2.48.2-1~ubuntu16.04.1_all.deb ... Unpacking glib-networking-common (2.48.2-1~ubuntu16.04.1) over (2.40.0-1ubuntu0.1) ... Preparing to unpack .../glib-networking_2.48.2-1~ubuntu16.04.1_amd64.deb ... Unpacking glib-networking:amd64 (2.48.2-1~ubuntu16.04.1) over (2.40.0-1ubuntu0.1) ... Preparing to unpack .../python-libproxy_0.4.11-5ubuntu1_all.deb ... Unpacking python-libproxy (0.4.11-5ubuntu1) over (0.4.11-0ubuntu4) ... Selecting previously unselected package libpcre16-3:amd64. Preparing to unpack .../libpcre16-3_2%3a8.38-3.1_amd64.deb ... Unpacking libpcre16-3:amd64 (2:8.38-3.1) ... Selecting previously unselected package libhybris-common1. Preparing to unpack .../libhybris-common1_0.1.0+git20151016+6d424c9-0ubuntu7_amd64.deb ... Unpacking libhybris-common1 (0.1.0+git20151016+6d424c9-0ubuntu7) ... Selecting previously unselected package libhardware2. Preparing to unpack .../libhardware2_0.1.0+git20151016+6d424c9-0ubuntu7_amd64.deb ... Unpacking libhardware2 (0.1.0+git20151016+6d424c9-0ubuntu7) ... Selecting previously unselected package libmedia1. Preparing to unpack .../libmedia1_0.1.0+git20151016+6d424c9-0ubuntu7_amd64.deb ... Unpacking libmedia1 (0.1.0+git20151016+6d424c9-0ubuntu7) ... Selecting previously unselected package libhybris. Preparing to unpack .../libhybris_0.1.0+git20151016+6d424c9-0ubuntu7_amd64.deb ... Unpacking libhybris (0.1.0+git20151016+6d424c9-0ubuntu7) ... Selecting previously unselected package libevdev2:amd64. Preparing to unpack .../libevdev2_1.4.6+dfsg-1_amd64.deb ... Unpacking libevdev2:amd64 (1.4.6+dfsg-1) ... Preparing to unpack .../libwacom2_0.22-1~ubuntu16.04.1_amd64.deb ... Unpacking libwacom2:amd64 (0.22-1~ubuntu16.04.1) over (0.8-1) ... Preparing to unpack .../libwacom-common_0.22-1~ubuntu16.04.1_all.deb ... Unpacking libwacom-common (0.22-1~ubuntu16.04.1) over (0.8-1) ... Selecting previously unselected package libinput-bin. Preparing to unpack .../libinput-bin_1.6.3-1ubuntu1~16.04.1_amd64.deb ... Unpacking libinput-bin (1.6.3-1ubuntu1~16.04.1) ... Selecting previously unselected package libinput10:amd64. Preparing to unpack .../libinput10_1.6.3-1ubuntu1~16.04.1_amd64.deb ... Unpacking libinput10:amd64 (1.6.3-1ubuntu1~16.04.1) ... Preparing to unpack .../libqt5dbus5_5.5.1+dfsg-16ubuntu7.5_amd64.deb ... Unpacking libqt5dbus5:amd64 (5.5.1+dfsg-16ubuntu7.5) over (5.2.1+dfsg-1ubuntu14.3) ... Preparing to unpack .../libqt5network5_5.5.1+dfsg-16ubuntu7.5_amd64.deb ... Unpacking libqt5network5:amd64 (5.5.1+dfsg-16ubuntu7.5) over (5.2.1+dfsg-1ubuntu14.3) ... Preparing to unpack .../libqt5gui5_5.5.1+dfsg-16ubuntu7.5_amd64.deb ... Unpacking libqt5gui5:amd64 (5.5.1+dfsg-16ubuntu7.5) over (5.2.1+dfsg-1ubuntu14.3) ... Selecting previously unselected package libdouble-conversion1v5:amd64. Preparing to unpack .../libdouble-conversion1v5_2.0.1-3ubuntu2_amd64.deb ... Unpacking libdouble-conversion1v5:amd64 (2.0.1-3ubuntu2) ... Processing triggers for hicolor-icon-theme (0.15-0ubuntu1) ... Processing triggers for libglib2.0-0:amd64 (2.48.2-0ubuntu1) ... Processing triggers for libc-bin (2.23-0ubuntu9) ... (Reading database ... 370499 files and directories currently installed.) Removing unity-webapps-common (2.4.17+15.10.20150616-0ubuntu2) ... Removing xul-ext-unity (3.0.0+14.04.20140416-0ubuntu1.14.04.1) ... Removing xul-ext-websites-integration (2.3.6+13.10.20130920.1-0ubuntu1.2) ... Removing libunity-webapps0:amd64 (2.5.0~+16.04.20160201-0ubuntu1) ... Removing unity-webapps-service (2.5.0~+16.04.20160201-0ubuntu1) ... Removing webapp-container (0.23+14.04.20140428-0ubuntu1) ... Removing webbrowser-app (0.23+14.04.20140428-0ubuntu1) ... dpkg: cycle found while processing triggers: chain of packages whose triggers are or may be responsible: gnome-menus -> desktop-file-utils packages' pending triggers which are or may be unresolvable: hicolor-icon-theme: /usr/share/icons/hicolor gnome-menus: /usr/share/applications doc-base: /usr/share/doc-base udev: /lib/udev/hwdb.d libc-bin: ldconfig bamfdaemon: /usr/share/applications libglib2.0-0:amd64: /usr/share/glib-2.0/schemas desktop-file-utils: /usr/share/applications mime-support: /usr/share/applications E: Sub-process /usr/bin/dpkg returned an error code (1) bob@Bob-PC:~$ -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to hicolor-icon-theme in Ubuntu. https://bugs.launchpad.net/bugs/1610517 Title: package hicolo-icon-theme 0.15-ubuntu1 failed to install: upgrade triggers looping Status in hicolor-icon-theme package in Ubuntu: Confirmed Bug description: While running a `do-release-upgrade` from Xubuntu 15.10 to 16.04 something like a post-install hook apparently triggered looping. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: hicolor-icon-theme 0.15-0ubuntu1 ProcVersionSignature: Ubuntu 4.2.0-38.45-generic 4.2.8-ckt10 Uname: Linux 4.2.0-38-generic x86_64 ApportVersion: 2.19.1-0ubun
[Touch-packages] [Bug 1705831] [NEW] package apport 2.20.1-0ubuntu2.6 failed to install/upgrade: subprocess new pre-removal script returned error exit status 139
Public bug reported: crashed when in Chrome window ProblemType: Package DistroRelease: Ubuntu 16.04 Package: apport 2.20.1-0ubuntu2.6 ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70 Uname: Linux 4.4.0-83-generic x86_64 ApportLog: ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 CrashReports: 600:0:116:76641:2017-07-22 09:18:55.509982585 -0700:2017-07-22 09:18:56.509982585 -0700:/var/crash/apport.0.crash Date: Sat Jul 22 09:18:56 2017 ErrorMessage: subprocess new pre-removal script returned error exit status 139 InstallationDate: Installed on 2016-05-04 (444 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: apport Title: package apport 2.20.1-0ubuntu2.6 failed to install/upgrade: subprocess new pre-removal script returned error exit status 139 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: apport (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1705831 Title: package apport 2.20.1-0ubuntu2.6 failed to install/upgrade: subprocess new pre-removal script returned error exit status 139 Status in apport package in Ubuntu: New Bug description: crashed when in Chrome window ProblemType: Package DistroRelease: Ubuntu 16.04 Package: apport 2.20.1-0ubuntu2.6 ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70 Uname: Linux 4.4.0-83-generic x86_64 ApportLog: ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 CrashReports: 600:0:116:76641:2017-07-22 09:18:55.509982585 -0700:2017-07-22 09:18:56.509982585 -0700:/var/crash/apport.0.crash Date: Sat Jul 22 09:18:56 2017 ErrorMessage: subprocess new pre-removal script returned error exit status 139 InstallationDate: Installed on 2016-05-04 (444 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: apport Title: package apport 2.20.1-0ubuntu2.6 failed to install/upgrade: subprocess new pre-removal script returned error exit status 139 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1705831/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1321854] Re: useradd doesn't add the default shell to /etc/passwd entry
I just ran into the same problem on Ubuntu 16.04: $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 16.04.2 LTS Release:16.04 Codename: xenial $ cat /etc/default/useradd SHELL=/bin/bash $ useradd -D GROUP=100 HOME=/home INACTIVE=-1 EXPIRE= SHELL=/bin/bash SKEL=/etc/skel CREATE_MAIL_SPOOL=no $ sudo useradd testuser $ getent passwd testuser testuser:x:1081:1082::/home/testuser: I expected testuser to show /bin/bash for the shell, but that's not the case. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to shadow in Ubuntu. https://bugs.launchpad.net/bugs/1321854 Title: useradd doesn't add the default shell to /etc/passwd entry Status in shadow package in Ubuntu: Triaged Status in shadow source package in Trusty: Triaged Bug description: useradd is not honoring the default shell listed in /etc/defaults/useradd when creating new users. useradd -D showing the defaults. SHELL=/bin/bash # useradd -D GROUP=100 HOME=/home INACTIVE=-1 EXPIRE= SHELL=/bin/bash SKEL=/etc/skel CREATE_MAIL_SPOOL=no Using useradd to create user test1. The /etc/passwd entry has a blank shell field: # useradd test1 # grep test1 /etc/passwd test1:x:2080:2080::/home/test1: Using useradd -s does populate the shell field: # useradd -s /bin/bash test2 #grep test2 /etc/passwd test2:x:2081:2081::/home/test2:/bin/bash Why useradd instead of adduser: puppet uses useradd to do user creation. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: passwd 1:4.1.5.1-1ubuntu9 ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 Date: Wed May 21 17:51:57 2014 Ec2AMI: ami-42dc302a Ec2AMIManifest: (unknown) Ec2AvailabilityZone: us-east-1d Ec2InstanceType: m3.large Ec2Kernel: aki-919dcaf8 Ec2Ramdisk: unavailable ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: shadow UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.default.useradd: 2014-05-21T17:36:05.208686 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1321854/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1461834] Re: 1024-bit signing keys should be deprecated
Sign with two keys then, and try to tell people. After a period of time you could disable the old key (ie no longer sign anything with it) - for anyone who still hasn't updated their configuration their system will still work, but instead of updates they would get errors. Then they would update their config. (Note that all PPA packages are already available through TLS, eg https://launchpad.net/~fnu/+archive/ubuntu/main- fnu/+build/8797131/+files/cmake-qt-gui_2.8.12.2-3_amd64.deb but only for manual download. It is not used automatically by apt, so to be secure you have to identify and manually download a lot of packages. These can be found through the 'View package details' link at the top right on all PPA main pages) -- 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/1461834 Title: 1024-bit signing keys should be deprecated Status in Launchpad itself: New Status in apt package in Ubuntu: Invalid Status in gnupg2 package in Ubuntu: New Bug description: 1024-bit RSA was deprecated years ago by NIST[1], Microsoft[2] and more recently by others[3]. 1024-bit signing keys are insufficient to guarantee the authenticity of software distributed from Launchpad.net including PPAs. There should be a mechanism to refuse signing keys below a minimum key length based on key type. 1024-bit signing keys should be deprecated and removed from Launchpad.net itself ASAP. Future projects and PPAs should be disallowed from using 1024-bit signing keys. 1. http://csrc.nist.gov/publications/nistpubs/800-131A/sp800-131A.pdf 2. http://blogs.technet.com/b/pki/archive/2012/06/12/rsa-keys-under-1024-bits-are-blocked.aspx 3. https://threatpost.com/mozilla-1024-bit-cert-deprecation-leaves-107000-sites-untrusted/108114 To manage notifications about this bug go to: https://bugs.launchpad.net/launchpad/+bug/1461834/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1461834] Re: 1024-bit signing keys should be deprecated
Launchpad could *automatically* create a mirror of any PPA that still uses a 1024 bit key, with a standard suffix to the name, eg xyzppa gets mirrored as xyzppa-newkey. It could then link to it from the page for the original PPA. It would always have all the same source, built files and other content, and the content would only need to be stored once on the server. It would just be a different way of accessing the same PPA. -- 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/1461834 Title: 1024-bit signing keys should be deprecated Status in Launchpad itself: New Status in apt package in Ubuntu: Confirmed Bug description: 1024-bit RSA was deprecated years ago by NIST[1], Microsoft[2] and more recently by others[3]. 1024-bit signing keys are insufficient to guarantee the authenticity of software distributed from Launchpad.net including PPAs. There should be a mechanism to refuse signing keys below a minimum key length based on key type. 1024-bit signing keys should be deprecated and removed from Launchpad.net itself ASAP. Future projects and PPAs should be disallowed from using 1024-bit signing keys. 1. http://csrc.nist.gov/publications/nistpubs/800-131A/sp800-131A.pdf 2. http://blogs.technet.com/b/pki/archive/2012/06/12/rsa-keys-under-1024-bits-are-blocked.aspx 3. https://threatpost.com/mozilla-1024-bit-cert-deprecation-leaves-107000-sites-untrusted/108114 To manage notifications about this bug go to: https://bugs.launchpad.net/launchpad/+bug/1461834/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1461834] Re: 1024-bit signing keys should be deprecated
Updates usually run automatically in the background, including from PPAs, and are unencrypted. This means a man-in-the-middle can gain root access, just by inserting their own version of one of the packages into this network traffic, because updates run as root. They can first obtain the public 1024 bit key from the PPA, then spend as long as they want working out the private key, then sign their false updates with the real private key. A bug that allows complete compromise of most Ubuntu machines without requiring any user involvement is a very serious bug. Why hasn't this even been assigned to anyone, nearly 2 years after it was reported? This makes many PPAs unusable. https://en.wikipedia.org/wiki/Key_size#Asymmetric_algorithm_key_lengths 'RSA claims that 1024-bit keys are likely to become crackable some time between 2006 and 2010' https://www.symantec.com/page.jsp?id=1024-bit-migration-faq#issue In compliance with Certification Authority/Browser forum requirements based on NIST Special Publication 800-131A, at the end of 2013 all web browsers and Certification Authorities (CAs) will no longer sell or support 1024-bit RSA certificates. All certificates less than 2048-bit key length will need to be revoked and replaced with certificates with a higher encryption strength. Network connections are secured with at least 2048 bits. Installing software allows root access and should probably be secured with at least 4096 bits. Any system using keys has to have a way to change to a new key, that's a basic requirement. You could force all 1024 bit keys to 4096 bits - this might break existing updates, but they are already 'broken' by being vulnerable. Or sign with 2 keys, so a new subscriber will only use the newer one, but old subscribers who don't do anything about it will still use the old key. Or re-issue the entire PPA namespace, ie ppa2:... Or do some other such thing, eg update the client to include a newer protocol version number in its requests. A simple workaround for launchpad to apply would be to change the urls in files in /etc/apt/sources.list.d/ to use https://ppa.launchpad.net/ instead of http://ppa.launchpad.net/ (and change the server to support it). This would only need to be done for any PPA still using a 1024 bit key. Then at least the packages would be authenticated by TLS, which already uses 2048 bit keys. ** Also affects: launchpad 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/1461834 Title: 1024-bit signing keys should be deprecated Status in Launchpad itself: New Status in apt package in Ubuntu: Confirmed Bug description: 1024-bit RSA was deprecated years ago by NIST[1], Microsoft[2] and more recently by others[3]. 1024-bit signing keys are insufficient to guarantee the authenticity of software distributed from Launchpad.net including PPAs. There should be a mechanism to refuse signing keys below a minimum key length based on key type. 1024-bit signing keys should be deprecated and removed from Launchpad.net itself ASAP. Future projects and PPAs should be disallowed from using 1024-bit signing keys. 1. http://csrc.nist.gov/publications/nistpubs/800-131A/sp800-131A.pdf 2. http://blogs.technet.com/b/pki/archive/2012/06/12/rsa-keys-under-1024-bits-are-blocked.aspx 3. https://threatpost.com/mozilla-1024-bit-cert-deprecation-leaves-107000-sites-untrusted/108114 To manage notifications about this bug go to: https://bugs.launchpad.net/launchpad/+bug/1461834/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1461834] Re: 1024-bit signing keys should be deprecated
** Tags added: encryption needs-update security vulnerability -- 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/1461834 Title: 1024-bit signing keys should be deprecated Status in apt package in Ubuntu: Confirmed Bug description: 1024-bit RSA was deprecated years ago by NIST[1], Microsoft[2] and more recently by others[3]. 1024-bit signing keys are insufficient to guarantee the authenticity of software distributed from Launchpad.net including PPAs. There should be a mechanism to refuse signing keys below a minimum key length based on key type. 1024-bit signing keys should be deprecated and removed from Launchpad.net itself ASAP. Future projects and PPAs should be disallowed from using 1024-bit signing keys. 1. http://csrc.nist.gov/publications/nistpubs/800-131A/sp800-131A.pdf 2. http://blogs.technet.com/b/pki/archive/2012/06/12/rsa-keys-under-1024-bits-are-blocked.aspx 3. https://threatpost.com/mozilla-1024-bit-cert-deprecation-leaves-107000-sites-untrusted/108114 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1461834/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1447099] Re: /sbin/upstart:indicator-session-unknown-user-error
It's still here, 16.04.1 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upstart in Ubuntu. https://bugs.launchpad.net/bugs/1447099 Title: /sbin/upstart:indicator-session-unknown-user-error Status in upstart : New Status in upstart package in Ubuntu: Fix Released Status in upstart source package in Vivid: Confirmed Status in upstart source package in Wily: Triaged Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding upstart. This problem was most recently seen with version 1.13.2-0ubuntu13, the problem page at https://errors.ubuntu.com/problem/09ab1b2ed4cff7556ed135307deb9f99c107193a contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/1447099/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1639201] Re: Can not resize GEDIT windows by moving window edge
I switched themes from ambiance to adwaita which solved the problem -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1639201 Title: Can not resize GEDIT windows by moving window edge Status in Ubuntu GNOME: Triaged Status in ubuntu-themes package in Ubuntu: Confirmed Bug description: Gedit UBUNTU 16.04.1 GNOME 3-20 GEDIT 3.20.2 Please restore the previously available ability to resize the gedit window by grabbing an edge or corner of the window and moving the edge. I manipulate many text files each day and frequently have several open and visible at the same time on the same monitor. (I have multiple monitors.) The ability to quickly change the dimensions of individual windows is very important, and the "new" GNOME 3 method of: 1. Move mouse to title bar, right click 2. move the "selection" bar -DOWN- several lines, click on the word "resize" 3. --CAREFULLY-- move the mouse --ONLY-- in the direction you want to expand or reduce the window size. 4. More often then NOT, you then get to do this all over again because the computer moved the left side of the window, rather then the right side as you had intended, or the top of the window instead of the bottom, or some sort of vice-versa forcing you to now move your cursor to the top of the screen to reposition the entire window. Much easier to just grab an edge and move THAT edge. I have also noticed that the majority of the applications installed on my system also allow grabbing the window edges, even though most of them also have the "click on a non-existant icon and hope that you get a usable pulldown menu to do something useful." method of selecting options that gnome 3 seems to like. What's worse is where the "help" and "preferences" selections are - especially when you have a multi-monitor sysytem. (But I will have to say, that GNOME 3 is much better than UNITY.) Now if this method of selecting options (Resize, help, preferences, Print, etc) was done to support "Touch screens" then I have to ask, please, PLEASE, provide a user selectable option of "Desktop" or "Touch Screen" so that the user can make their own choice... ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gedit 3.20.2-2ubuntu1~ubuntu16.04.1 [origin: LP-PPA-gnome3-team-gnome3-staging] ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21 Uname: Linux 4.4.0-45-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Nov 4 06:32:16 2016 InstallationDate: Installed on 2014-05-11 (908 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) SourcePackage: gedit UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-gnome/+bug/1639201/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1581342] Re: Bluetooth menu closes immediately after opening
I see this issue on a clean 16.0.4.2 install, I don't have any kind of special input methods installed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-bluetooth in Ubuntu. https://bugs.launchpad.net/bugs/1581342 Title: Bluetooth menu closes immediately after opening Status in indicator-bluetooth package in Ubuntu: Confirmed Bug description: Description: Ubuntu 16.04 LTS Release: 16.04 indicator-bluetooth: 0.0.6+16.04.20160214-0ubuntu1 fcitx: 1:4.2.9.1-1ubuntu1 Steps to reproduce: 1. click on the top-right bluetooth icon 2. the panel opens, but closes immediately I do not observe similar behavior with other indicator menus. If I click on other icons, like network/wifi icon, then move cursor on bluetooth icon, bluetooth menu remains opened when cursor hovers it. I suspect this might have something to do with fcitx, I have fcitx- rime installed, if Rime (a input method) is enabled, during the brief time bluetooth menu is opened, rime is disabled. Any suggestion on how to debug further? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-bluetooth/+bug/1581342/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1664075] [NEW] package ntp 1:4.2.8p4+dfsg-3ubuntu5 [modified: usr/bin/ntpdc usr/bin/ntpq usr/sbin/ntp-keygen usr/sbin/ntpd usr/sbin/ntptime usr/share/doc/ntp/changelog.Debian.gz]
Public bug reported: trying to install tightvnc ProblemType: Package DistroRelease: Ubuntu 16.04 Package: ntp 1:4.2.8p4+dfsg-3ubuntu5 [modified: usr/bin/ntpdc usr/bin/ntpq usr/sbin/ntp-keygen usr/sbin/ntpd usr/sbin/ntptime usr/share/doc/ntp/changelog.Debian.gz] Uname: Linux 4.1.19-v7+ armv7l ApportVersion: 2.20.1-0ubuntu2.1 Architecture: armhf Date: Sun Feb 12 16:15:09 2017 DpkgHistoryLog: Start-Date: 2017-02-12 16:15:01 Commandline: aptdaemon role='role-commit-packages' sender=':1.65' Install: libvncserver1:armhf (0.9.10+dfsg-3build1, automatic), x11vnc:armhf (0.9.13-1.2build1), x11vnc-data:armhf (0.9.13-1.2build1, automatic) DuplicateSignature: package:ntp:1:4.2.8p4+dfsg-3ubuntu5 [modified: usr/bin/ntpdc usr/bin/ntpq usr/sbin/ntp-keygen usr/sbin/ntpd usr/sbin/ntptime usr/share/doc/ntp/changelog.Debian.gz] Processing triggers for man-db (2.7.5-1) ... dpkg: error processing package ntp (--configure): package ntp is not ready for configuration ErrorMessage: package ntp is not ready for configuration cannot configure (current status 'half-installed') KernLog: [1.966493] systemd[1]: systemd 229 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ -LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN) ProcCmdline: 8250.nr_uarts=1 dma.dmachans=0x7f35 bcm2708_fb.fbwidth=1024 bcm2708_fb.fbheight=600 bcm2709.boardrev=0xa22082 bcm2709.serial=0x947ba018 smsc95xx.macaddr=B8:27:EB:7B:A0:18 bcm2708_fb.fbdepth=32 bcm2708_fb.fbswap=1 bcm2709.uart_clock=4800 vc_mem.mem_base=0x3dc0 vc_mem.mem_size=0x3f00 dwc_otg.lpm_enable=0 console=tty1 root=/dev/mmcblk0p2 rootfstype=ext4 elevator=deadline rootwait quiet splash RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.12~ubuntu16.04.1 SourcePackage: ntp Title: package ntp 1:4.2.8p4+dfsg-3ubuntu5 [modified: usr/bin/ntpdc usr/bin/ntpq usr/sbin/ntp-keygen usr/sbin/ntpd usr/sbin/ntptime usr/share/doc/ntp/changelog.Debian.gz] failed to install/upgrade: package ntp is not ready for configuration cannot configure (current status 'half-installed') UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ntp (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package armhf xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/1664075 Title: package ntp 1:4.2.8p4+dfsg-3ubuntu5 [modified: usr/bin/ntpdc usr/bin/ntpq usr/sbin/ntp-keygen usr/sbin/ntpd usr/sbin/ntptime usr/share/doc/ntp/changelog.Debian.gz] failed to install/upgrade: package ntp is not ready for configuration cannot configure (current status 'half-installed') Status in ntp package in Ubuntu: New Bug description: trying to install tightvnc ProblemType: Package DistroRelease: Ubuntu 16.04 Package: ntp 1:4.2.8p4+dfsg-3ubuntu5 [modified: usr/bin/ntpdc usr/bin/ntpq usr/sbin/ntp-keygen usr/sbin/ntpd usr/sbin/ntptime usr/share/doc/ntp/changelog.Debian.gz] Uname: Linux 4.1.19-v7+ armv7l ApportVersion: 2.20.1-0ubuntu2.1 Architecture: armhf Date: Sun Feb 12 16:15:09 2017 DpkgHistoryLog: Start-Date: 2017-02-12 16:15:01 Commandline: aptdaemon role='role-commit-packages' sender=':1.65' Install: libvncserver1:armhf (0.9.10+dfsg-3build1, automatic), x11vnc:armhf (0.9.13-1.2build1), x11vnc-data:armhf (0.9.13-1.2build1, automatic) DuplicateSignature: package:ntp:1:4.2.8p4+dfsg-3ubuntu5 [modified: usr/bin/ntpdc usr/bin/ntpq usr/sbin/ntp-keygen usr/sbin/ntpd usr/sbin/ntptime usr/share/doc/ntp/changelog.Debian.gz] Processing triggers for man-db (2.7.5-1) ... dpkg: error processing package ntp (--configure): package ntp is not ready for configuration ErrorMessage: package ntp is not ready for configuration cannot configure (current status 'half-installed') KernLog: [1.966493] systemd[1]: systemd 229 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ -LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN) ProcCmdline: 8250.nr_uarts=1 dma.dmachans=0x7f35 bcm2708_fb.fbwidth=1024 bcm2708_fb.fbheight=600 bcm2709.boardrev=0xa22082 bcm2709.serial=0x947ba018 smsc95xx.macaddr=B8:27:EB:7B:A0:18 bcm2708_fb.fbdepth=32 bcm2708_fb.fbswap=1 bcm2709.uart_clock=4800 vc_mem.mem_base=0x3dc0 vc_mem.mem_size=0x3f00 dwc_otg.lpm_enable=0 console=tty1 root=/dev/mmcblk0p2 rootfstype=ext4 elevator=deadline rootwait quiet splash RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.12~ubuntu16.04.1 SourcePackage: ntp Title: package ntp 1:4.2.8p4+dfsg-3ubuntu5 [modified: usr/bin/ntpdc usr/bin/ntpq usr/sbin/ntp-keygen usr/sbin/ntpd usr/sbin/ntptime usr/share/doc/ntp/changelog.Debian.gz] failed to install/upgrade: package ntp is not ready for configuration cannot configure (current status 'half-installed') UpgradeStatus: No upgrade
[Touch-packages] [Bug 1654627] [NEW] Windows Rearrange and Resize without User Interactions
Public bug reported: !What I expected to happen Windows stay in the same place with the same dimensions !What happenes (happens) instead Open windows will be re-arranged. Some will be resized, others maximized and some hidden. If workspaces are enabled, some windows will be moved to a different workspace. Some of the ways to reproduce this: * with workspaces enabled, merely switching workspaces (often but not always) * with or without workspaces enabled, if the machine goes to sleep/suspend $ lsb_release -rd Description:Ubuntu 16.04.1 LTS Release:16.04 Problem reproduced on multiple machines less than a year old: * System76 Lemur with external Dell monitor + * 2016 HP Spectre x360 with a standard install of Ubuntu) with no external display Frequency: very (essentially any time I'm away from a machine for more than about ten minutes). !Attempted Solutions * Disable all hot corners/edges, etc. on both machines * turned off the Lemur's internal display (the psuedo disable in System Settings > Display). * turned off workspaces on Lemur The only noticable difference was that it reduced the places I had to hunt for the windows I need to move and resize to begin work again. e.g. put my Development environment back in working order. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35 Uname: Linux 4.4.0-57-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Fri Jan 6 11:03:13 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: virtualbox, 5.0.24, 4.4.0-51-generic, x86_64: installed virtualbox, 5.0.24, 4.4.0-53-generic, x86_64: installed virtualbox, 5.0.24, 4.4.0-57-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer Skylake Integrated Graphics [1558:2425] InstallationDate: Installed on 2016-11-30 (37 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: System76, Inc. Lemur ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-57-generic.efi.signed root=UUID=5a96be43-7cc5-4afd-a77c-7269b753bae3 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/29/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.06RS76 dmi.board.asset.tag: Tag 12345 dmi.board.name: Lemur dmi.board.vendor: System76, Inc. dmi.board.version: lemu6 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: System76, Inc. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.06RS76:bd11/29/2015:svnSystem76,Inc.:pnLemur:pvrlemu6:rvnSystem76,Inc.:rnLemur:rvrlemu6:cvnSystem76,Inc.:ct10:cvrN/A: dmi.product.name: Lemur dmi.product.version: lemu6 dmi.sys.vendor: System76, Inc. version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Mon Dec 26 09:27:59 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 41152 vendor DEL xserver.version: 2:1.18.4-0ubuntu0.2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 ubuntu xenial -- 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/1654627 Title: Windows Rearrange and Resize without User Interactions Status in xorg package in Ubuntu: New Bug description: !What I expected to happen Windows stay in the same place with the same dimensions !What happenes (happens) instead Open windows will be re-arranged. Some will be resized, others maximized and some hidden. If workspaces are enabled, some windows will be moved to a different workspace. Some of the ways
[Touch-packages] [Bug 1502145] Re: Apps can keep screen lit permanently
M10 tablet, OTA13 I had not seen this problem until I installed OTA13. Now my screen never blanks. I pretty much only use the web browser app. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-system-compositor in Ubuntu. https://bugs.launchpad.net/bugs/1502145 Title: Apps can keep screen lit permanently Status in Canonical System Image: Confirmed Status in Oxide: Fix Released Status in Oxide 1.10 series: Fix Released Status in qtmir package in Ubuntu: Confirmed Status in unity-system-compositor package in Ubuntu: Confirmed Status in unity8 package in Ubuntu: Confirmed Bug description: rc-proposed, r140, krillin There are times when it seems the display blanking policy stops working and the display stays on until I press the power button. Steps to reproduce: * install and start Siete * put it in background Expected outcome: * the display is switched off after a predetermined amount of time Actual outcome: * the display stays on forever == Now that apps can request the screen to stay on, they can do so regardless of whether they're focused/visible or not. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1502145/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1595348] Re: Web browser dissapears too often
I have had to unbox my BQM10 tablet (OTA12) again, as my iPad has failed. I (can) only use it for web browsing, and the almost continuous crashing of the browser is very irritating. I can induce it by - switching tabs - double clicking on text to copy it (especially if it seems not to select a word and I do it again) - zooming in with the scroll wheel - trying to copy an url from the address bar -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1595348 Title: Web browser dissapears too often Status in Canonical System Image: New Status in webbrowser-app package in Ubuntu: Confirmed Bug description: M10 tablet.. Ever since upgrading to OTA11 the web browser has become very annoying. If I have, say, 3 tabs on and close one, the browser often dissapears.. I restart it from the apps page and it restarts with all the original tabs, including thecone I tried to close.. I can then closecit again, usually without furthervincident. Or I might open the bookmarks and try to open a new tab, and the browser vanishes. Or, very occasionally I click on a search engine result and 'poof' she is gone! Anyone care to nominate a suitable log file? To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1595348/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1603157] Re: closing a tab while browsing results in closing browsing completely
I have had to unbox my BQM10 tablet (OTA12) again, as my iPad has failed. I (can) only use it for web browsing, and the almost continuous crashing of the browser is very irritating. I can induce it by closing the last tab 3 times out of 5, and by closing the 2nd of 3 almost every time. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1603157 Title: closing a tab while browsing results in closing browsing completely Status in Canonical System Image: Incomplete Status in webbrowser-app package in Ubuntu: Confirmed Bug description: When you are browsing on the internet ( using native browser ) and you have multiple tabs open... then close 1 tab... then the browser closes completely. You have to start up internet again. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1603157/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1586692] Re: bluetooth speakers only work once
*** This bug is a duplicate of bug 1543179 *** https://bugs.launchpad.net/bugs/1543179 ** This bug has been marked a duplicate of bug 1543179 Audio does not get routed to BT headset/speaker -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1586692 Title: bluetooth speakers only work once Status in bluez package in Ubuntu: New Bug description: m10 tablet, OTA10.1 today I am successfully connected to keyboard, mouse, AND bluetooth spakers. All OS beeps and noises are coming out of the bluetooth speakers. If I start podbird, cloudmusic, or one of the radio apps, then they are either silent or the sound comes out of the bluetooth speakers. if I disconnect the bluetooth speakers, and reconnect them, the sound will come from the tablet. The speakers are shown as connected, but don't work. The only way to get them working again is to power down the tablet and restart it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1586692/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1621864] [NEW] Don't run in a default install... PLEASE !!!
Public bug reported: Could someone please explain to me the dumb decision to activate LXC by default in a default install of 16.04LTS ? What's wrong with the obvious process that *IF* I want virtualisation, I can either activate the service or install the package. Why on earth run it by default and waste un-necessary resources on the system ? ** Affects: lxc (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1621864 Title: Don't run in a default install... PLEASE !!! Status in lxc package in Ubuntu: New Bug description: Could someone please explain to me the dumb decision to activate LXC by default in a default install of 16.04LTS ? What's wrong with the obvious process that *IF* I want virtualisation, I can either activate the service or install the package. Why on earth run it by default and waste un-necessary resources on the system ? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1621864/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1603157] Re: closing a tab while browsing results in closing browsing completely
Wretched ubuntvautocorrect.. WWW.it.com should be WWW.itv.com -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1603157 Title: closing a tab while browsing results in closing browsing completely Status in Canonical System Image: Incomplete Status in webbrowser-app package in Ubuntu: Confirmed Bug description: When you are browsing on the internet ( using native browser ) and you have multiple tabs open... then close 1 tab... then the browser closes completely. You have to start up internet again. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1603157/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1603157] Re: closing a tab while browsing results in closing browsing completely
The site Sci gegularly use are: WWW.geograph.organized.uk WWW.face book.cmm WWW.mail.com WWW.BBC.co.uk/news WWW.twitter.com But it has happened after visiting WWW.rot13.com ; WWW.it.com ; WWW.girlgenius.com ; https://groups.google.com/forum/#!forum/uk.rec.sheds ; -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1603157 Title: closing a tab while browsing results in closing browsing completely Status in Canonical System Image: Incomplete Status in webbrowser-app package in Ubuntu: Confirmed Bug description: When you are browsing on the internet ( using native browser ) and you have multiple tabs open... then close 1 tab... then the browser closes completely. You have to start up internet again. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1603157/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1603157] Re: closing a tab while browsing results in closing browsing completely
I have had this problem in OTA11 & OTA12.. It is very frequent, and among the reasons I stopped usingvthe M10 tablet.. I had to dig it out today, and it is no better yet.. It has done cit at least 6 times this evening, and there seems no one particular pagecor site involved. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1603157 Title: closing a tab while browsing results in closing browsing completely Status in Canonical System Image: Incomplete Status in webbrowser-app package in Ubuntu: Confirmed Bug description: When you are browsing on the internet ( using native browser ) and you have multiple tabs open... then close 1 tab... then the browser closes completely. You have to start up internet again. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1603157/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1614462] Re: apt-get upgrade hangs on Xenial
I killed it and tried "sudo dpkg --configure -a", and the same thing repeats itself ! sudo dpkg --configure -a Setting up zfs-doc (0.6.5.6-0ubuntu12) ... Setting up libuutil1linux (0.6.5.6-0ubuntu12) ... Setting up language-selector-common (0.165.4) ... Setting up initramfs-tools (0.122ubuntu8.1) ... update-initramfs: deferring update (trigger activated) Setting up libnvpair1linux (0.6.5.6-0ubuntu12) ... Setting up snapd (2.12+0.16.04) ... Setting up libpq5:amd64 (9.5.4-1.pgdg16.04+1) ... Setting up postgresql-doc-9.5 (9.5.4-1.pgdg16.04+1) ... Setting up postgresql-client-9.5 (9.5.4-1.pgdg16.04+1) ... Setting up postgresql-9.5 (9.5.4-1.pgdg16.04+1) ... Setting up python3-software-properties (0.96.20.3) ... Setting up linux-firmware (1.157.3) ... Setting up libapparmor-perl (2.10.95-0ubuntu2.2) ... Setting up python3-distupgrade (1:16.04.16) ... Setting up software-properties-common (0.96.20.3) ... Setting up libzpool2linux (0.6.5.6-0ubuntu12) ... Setting up apparmor (2.10.95-0ubuntu2.2) ... Installing new version of config file /etc/apparmor.d/abstractions/dbus-session-strict ... update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd Files /var/lib/dpkg/info/apparmor.md5sums and /var/lib/apparmor/profiles/.apparmor.md5sums differ Setting up ubuntu-release-upgrader-core (1:16.04.16) ... Setting up libzfs2linux (0.6.5.6-0ubuntu12) ... Setting up postgresql-contrib-9.5 (9.5.4-1.pgdg16.04+1) ... Setting up zfsutils-linux (0.6.5.6-0ubuntu12) ... Installing new version of config file /etc/cron.d/zfsutils-linux ... zfs-import-cache.service is a disabled or a static unit, not starting it. zfs-import-scan.service is a disabled or a static unit, not starting it. zfs-mount.service is a disabled or a static unit, not starting it. Processing triggers for initramfs-tools (0.122ubuntu8.1) ... update-initramfs: Generating /boot/initrd.img-4.4.0-34-generic W: mdadm: /etc/mdadm/mdadm.conf defines no arrays. it is hanging here, no further output -- 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/1614462 Title: apt-get upgrade hangs on Xenial Status in apt package in Ubuntu: New Bug description: Description: Ubuntu 16.04.1 LTS Release: 16.04 apt 1.2.12 (amd64) Supported modules: *Ver: Standard .deb *Pkg: Debian dpkg interface (Priority 30) Pkg: Debian APT solver interface (Priority -1000) S.L: 'deb' Debian binary tree S.L: 'deb-src' Debian source tree Idx: Debian Source Index Idx: Debian Package Index Idx: Debian Translation Index Idx: Debian dpkg status file Idx: Debian deb file Idx: Debian dsc file Idx: Debian control file Idx: EDSP scenario file During an "apt-get upgrade" run today (2016-08-18), the process has been hanging for over an hour now ! It hangs at mdadm.conf as per below tail of output : Processing triggers for systemd (229-4ubuntu7) ... Processing triggers for ureadahead (0.100.0-19) ... Processing triggers for man-db (2.7.5-1) ... Processing triggers for dbus (1.10.6-1ubuntu3) ... Processing triggers for libc-bin (2.23-0ubuntu3) ... Processing triggers for initramfs-tools (0.122ubuntu8.1) ... update-initramfs: Generating /boot/initrd.img-4.4.0-34-generic W: mdadm: /etc/mdadm/mdadm.conf defines no arrays. it is hanging here, no further output To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1614462/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1614462] Re: apt-get upgrade hangs on Xenial
** Attachment added: "dpkg log" https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1614462/+attachment/4723694/+files/dpkg.log -- 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/1614462 Title: apt-get upgrade hangs on Xenial Status in apt package in Ubuntu: New Bug description: Description: Ubuntu 16.04.1 LTS Release: 16.04 apt 1.2.12 (amd64) Supported modules: *Ver: Standard .deb *Pkg: Debian dpkg interface (Priority 30) Pkg: Debian APT solver interface (Priority -1000) S.L: 'deb' Debian binary tree S.L: 'deb-src' Debian source tree Idx: Debian Source Index Idx: Debian Package Index Idx: Debian Translation Index Idx: Debian dpkg status file Idx: Debian deb file Idx: Debian dsc file Idx: Debian control file Idx: EDSP scenario file During an "apt-get upgrade" run today (2016-08-18), the process has been hanging for over an hour now ! It hangs at mdadm.conf as per below tail of output : Processing triggers for systemd (229-4ubuntu7) ... Processing triggers for ureadahead (0.100.0-19) ... Processing triggers for man-db (2.7.5-1) ... Processing triggers for dbus (1.10.6-1ubuntu3) ... Processing triggers for libc-bin (2.23-0ubuntu3) ... Processing triggers for initramfs-tools (0.122ubuntu8.1) ... update-initramfs: Generating /boot/initrd.img-4.4.0-34-generic W: mdadm: /etc/mdadm/mdadm.conf defines no arrays. it is hanging here, no further output To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1614462/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1614462] [NEW] apt-get upgrade hangs on Xenial
Public bug reported: Description:Ubuntu 16.04.1 LTS Release:16.04 apt 1.2.12 (amd64) Supported modules: *Ver: Standard .deb *Pkg: Debian dpkg interface (Priority 30) Pkg: Debian APT solver interface (Priority -1000) S.L: 'deb' Debian binary tree S.L: 'deb-src' Debian source tree Idx: Debian Source Index Idx: Debian Package Index Idx: Debian Translation Index Idx: Debian dpkg status file Idx: Debian deb file Idx: Debian dsc file Idx: Debian control file Idx: EDSP scenario file During an "apt-get upgrade" run today (2016-08-18), the process has been hanging for over an hour now ! It hangs at mdadm.conf as per below tail of output : Processing triggers for systemd (229-4ubuntu7) ... Processing triggers for ureadahead (0.100.0-19) ... Processing triggers for man-db (2.7.5-1) ... Processing triggers for dbus (1.10.6-1ubuntu3) ... Processing triggers for libc-bin (2.23-0ubuntu3) ... Processing triggers for initramfs-tools (0.122ubuntu8.1) ... update-initramfs: Generating /boot/initrd.img-4.4.0-34-generic W: mdadm: /etc/mdadm/mdadm.conf defines no arrays. it is hanging here, no further output ** 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/1614462 Title: apt-get upgrade hangs on Xenial Status in apt package in Ubuntu: New Bug description: Description: Ubuntu 16.04.1 LTS Release: 16.04 apt 1.2.12 (amd64) Supported modules: *Ver: Standard .deb *Pkg: Debian dpkg interface (Priority 30) Pkg: Debian APT solver interface (Priority -1000) S.L: 'deb' Debian binary tree S.L: 'deb-src' Debian source tree Idx: Debian Source Index Idx: Debian Package Index Idx: Debian Translation Index Idx: Debian dpkg status file Idx: Debian deb file Idx: Debian dsc file Idx: Debian control file Idx: EDSP scenario file During an "apt-get upgrade" run today (2016-08-18), the process has been hanging for over an hour now ! It hangs at mdadm.conf as per below tail of output : Processing triggers for systemd (229-4ubuntu7) ... Processing triggers for ureadahead (0.100.0-19) ... Processing triggers for man-db (2.7.5-1) ... Processing triggers for dbus (1.10.6-1ubuntu3) ... Processing triggers for libc-bin (2.23-0ubuntu3) ... Processing triggers for initramfs-tools (0.122ubuntu8.1) ... update-initramfs: Generating /boot/initrd.img-4.4.0-34-generic W: mdadm: /etc/mdadm/mdadm.conf defines no arrays. it is hanging here, no further output To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1614462/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1610774] [NEW] package initramfs-tools 0.122ubuntu8.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Public bug reported: Seems similar to #1578762 but this error message says "initramfs-tools 0.122ubuntu8.1". This error first appeared when attempting to upgrade my distribution. After the failure to upgrade which this error message announced my system is in fairly flaky condition. uname -a returns "Linux 4.4.0-31-generic #50-Ubuntu SMP Wed Jul 13 00:07:12 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux". I will now do a fresh installation, if I can get my machine to download 16.04.1. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: initramfs-tools 0.122ubuntu8.1 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Sun Aug 7 17:13:03 2016 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2016-04-02 (127 days ago) InstallationMedia: Xubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 (20160217.1) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.12~ubuntu16.04.1 SourcePackage: initramfs-tools Title: package initramfs-tools 0.122ubuntu8.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to xenial on 2016-08-08 (0 days ago) mtime.conffile..etc.initramfs-tools.initramfs.conf: 2016-02-21T15:22:01 ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- 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/1610774 Title: package initramfs-tools 0.122ubuntu8.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in initramfs-tools package in Ubuntu: New Bug description: Seems similar to #1578762 but this error message says "initramfs-tools 0.122ubuntu8.1". This error first appeared when attempting to upgrade my distribution. After the failure to upgrade which this error message announced my system is in fairly flaky condition. uname -a returns "Linux 4.4.0-31-generic #50-Ubuntu SMP Wed Jul 13 00:07:12 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux". I will now do a fresh installation, if I can get my machine to download 16.04.1. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: initramfs-tools 0.122ubuntu8.1 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Sun Aug 7 17:13:03 2016 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2016-04-02 (127 days ago) InstallationMedia: Xubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 (20160217.1) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.12~ubuntu16.04.1 SourcePackage: initramfs-tools Title: package initramfs-tools 0.122ubuntu8.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to xenial on 2016-08-08 (0 days ago) mtime.conffile..etc.initramfs-tools.initramfs.conf: 2016-02-21T15:22:01 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1610774/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1552928] Re: New bottom edge component is harder to flick up
Can't believe you have pushed this out to OTA 13. People paid real money for the devices, it is a bit ripe shipping them unfinished and then delaying important fixes. -- 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/1552928 Title: New bottom edge component is harder to flick up Status in Canonical System Image: Confirmed Status in ubuntu-ui-toolkit package in Ubuntu: Confirmed Bug description: I usually hold the phone in one hand and open the bottom edge by flicking up from the bottom with the thumb. This worked fine with the previous bottom edge, however, with the new one, there seems to be larger amount of dragging required. I keep on failing to open the bottom edge in the messages-app and clock app, now that they use the new component. When dragging very slowly such an big required distance does make sense, but for quick flicks with the thumb, it should also take the speed and/or touch points history into account and reduce the required distance if it detects a fast flick gesture. In the right edge implementation for instance, it tracks the touch points and already activates the gesture after a rather short distance (2 grid units), provided it is a one-way gesture with increasing distance from the edge in each recognized point. Such a logic would imo also make sense for the bottom edge. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1552928/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1567540] Re: ntpd crashed with SIGABRT (was: ntp crashes everytime the network goes up or down.)
Have you finished "thinking about" fixing the broken NTP in Xenial yet ? Its becoming a bit of a joke to be without such a key package (let alone the hacks that have had to be put in place to keep server time accurate !). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/1567540 Title: ntpd crashed with SIGABRT (was: ntp crashes everytime the network goes up or down.) Status in NTP: Fix Released Status in ntp package in Ubuntu: Triaged Status in ntp source package in Xenial: Confirmed Bug description: ntp crashes every time the network goes up or down while the system is running and also crashes after booting up without network. --- ApportVersion: 2.20.1-0ubuntu1 Architecture: amd64 CurrentDesktop: XFCE DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2016-03-12 (26 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160224) NtpStatus: ntpq: read: Connection refused Package: ntp 1:4.2.8p4+dfsg-3ubuntu4 PackageArchitecture: amd64 ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-17-generic root=UUID=306314bc-efcb-4c2d-b0e9-e05ec92ed0f0 ro ProcVersionSignature: Ubuntu 4.4.0-17.33-generic 4.4.6 Tags: xenial Uname: Linux 4.4.0-17-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True --- ApportVersion: 2.20.1-0ubuntu1 Architecture: amd64 CurrentDesktop: XFCE DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2016-03-12 (31 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160224) NtpStatus: ntpq: read: Connection refused Package: ntp 1:4.2.8p4+dfsg-3ubuntu5 PackageArchitecture: amd64 ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-18-generic root=UUID=306314bc-efcb-4c2d-b0e9-e05ec92ed0f0 ro ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6 Tags: xenial Uname: Linux 4.4.0-18-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True --- ApportVersion: 2.20.1-0ubuntu1 Architecture: amd64 CurrentDesktop: XFCE DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2016-04-13 (0 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160412) NtpStatus: ntpq: read: Connection refused Package: ntp 1:4.2.8p4+dfsg-3ubuntu5 PackageArchitecture: amd64 ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-18-generic root=UUID=13f57794-2e19-4a56-836a-94185bba5ec5 ro quiet splash ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6 Tags: xenial Uname: Linux 4.4.0-18-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True --- ApportVersion: 2.20.1-0ubuntu1 Architecture: amd64 CurrentDesktop: XFCE DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2016-04-13 (0 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160412) NtpStatus: ntpq: read: Connection refused Package: ntp 1:4.2.8p4+dfsg-3ubuntu5 PackageArchitecture: amd64 ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-18-generic root=UUID=13f57794-2e19-4a56-836a-94185bba5ec5 ro quiet splash ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6 Tags: xenial Uname: Linux 4.4.0-18-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True --- ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: XFCE DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2016-04-14 (3 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160412) NtpStatus: ntpq: read: Connection refused Package: ntp 1:4.2.8p4+dfsg-3ubuntu5 PackageArchitecture: amd64 ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-20-generic root=UUID=b9c0528f-e81f-4b08-9b31-032f14f72ccd ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-20.36-generic 4.4.6 Tags: xenial Uname: Linux 4.4.0-20-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True --- ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: XFCE DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2016-04-14 (3 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160412) NtpStatus: ntpq: read: Connection refused Package: ntp 1:4.2.8p4+dfsg-3ubuntu5 PackageArchitecture: amd64 ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-20-generic root=UUID=b9c0528f-e81f-4b08-9b31-032f14f72ccd ro quiet splash vt.handoff=7 ProcVersionSignature:
[Touch-packages] [Bug 1597535] [NEW] Lots of errors in console when running Chromium/Firefox with X11 forwarding.
Public bug reported: See attached console transcript. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: dbus 1.6.18-0ubuntu4.3 ProcVersionSignature: Ubuntu 3.19.0-64.72~14.04.1-generic 3.19.8-ckt22 Uname: Linux 3.19.0-64-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.21 Architecture: amd64 Date: Wed Jun 29 14:26:21 2016 InstallationDate: Installed on 2016-02-07 (143 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) SourcePackage: dbus UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: dbus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty ** Attachment added: "May be due to a problem with my System Configuration. I'm not an expert in this area." https://bugs.launchpad.net/bugs/1597535/+attachment/4692493/+files/MobaXterm_192.168.1.22_20160629_144225.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus in Ubuntu. https://bugs.launchpad.net/bugs/1597535 Title: Lots of errors in console when running Chromium/Firefox with X11 forwarding. Status in dbus package in Ubuntu: New Bug description: See attached console transcript. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: dbus 1.6.18-0ubuntu4.3 ProcVersionSignature: Ubuntu 3.19.0-64.72~14.04.1-generic 3.19.8-ckt22 Uname: Linux 3.19.0-64-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.21 Architecture: amd64 Date: Wed Jun 29 14:26:21 2016 InstallationDate: Installed on 2016-02-07 (143 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) SourcePackage: dbus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1597535/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1588534] Re: Tablet stops responding after taking screenshots
Ok, got my Ipad back. Going to pack the M10 away.. It's been interesting, but not much fun.. Like the phone it is just not finished, and not reliable enough to use -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1588534 Title: Tablet stops responding after taking screenshots Status in Canonical System Image: Confirmed Status in Mir: New Status in mir package in Ubuntu: New Status in unity8 package in Ubuntu: New Bug description: M10 tablet, OTA11.. (saw same thing very occasionally in OTA10.1) Sometimes when using the tablet it just stops responding.. No touch actions work at all.. Screen does not update.. Have to power down (longpress on power) and up again. Seen it 5 times in the 2 hours since I got OTA11.. Twice in Web Browser Once in Firefox Once in Dekko Once in Today scope. The firefox occasion it happened when I tried to screenshot.. Got the shutter noise, the vibrating feedback, then everything stopped.. On restarting not onlyvthat screenshot was lost, but so where two more from a few minutes before. No recollection of screngrabbing the other times. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1588534/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1596164] Re: OSK not appearing for text fields in browser
Ok, got my Ipad back. Going to pack the M10 away.. It's been interesting, but not much fun.. Like the phone it is just not finished, and not reliable enough to use -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1596164 Title: OSK not appearing for text fields in browser Status in Canonical System Image: New Status in webbrowser-app package in Ubuntu: New Bug description: There is a web site I visit a lot. Today I have found that pages I have habitually used do not Produce an OSK for text entry unless I kill and restart the browser.. The circumstances are not the same as bug #1582060 because no new tabs are involved. Reloading the page via the address bar does not do it.. You have to kill & restart the browser. Two example pages: http://www.geograph.org.uk/discuss/index.php?=vthread=6=17652=-1#2 http://www.geograph.org.uk/editimage.php?id=5007116 There have been other similar incidents in the past, but today it is happening a lot.. Other web sites have been involved, and the Geograph site has not changed. M10 tablet, OTA11 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1596164/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1595348] Re: Web browser dissapears too often
Ok, got my Ipad back. Going to pack the M10 away.. It's been interesting, but not much fun.. Like the phone it is just not finished, and not reliable enough to use -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1595348 Title: Web browser dissapears too often Status in Canonical System Image: New Status in webbrowser-app package in Ubuntu: New Bug description: M10 tablet.. Ever since upgrading to OTA11 the web browser has become very annoying. If I have, say, 3 tabs on and close one, the browser often dissapears.. I restart it from the apps page and it restarts with all the original tabs, including thecone I tried to close.. I can then closecit again, usually without furthervincident. Or I might open the bookmarks and try to open a new tab, and the browser vanishes. Or, very occasionally I click on a search engine result and 'poof' she is gone! Anyone care to nominate a suitable log file? To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1595348/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1595348] Re: Web browser dissapears too often
** Attachment added: "dmesg" https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1595348/+attachment/4689308/+files/dmesg -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1595348 Title: Web browser dissapears too often Status in Canonical System Image: New Status in webbrowser-app package in Ubuntu: New Bug description: M10 tablet.. Ever since upgrading to OTA11 the web browser has become very annoying. If I have, say, 3 tabs on and close one, the browser often dissapears.. I restart it from the apps page and it restarts with all the original tabs, including thecone I tried to close.. I can then closecit again, usually without furthervincident. Or I might open the bookmarks and try to open a new tab, and the browser vanishes. Or, very occasionally I click on a search engine result and 'poof' she is gone! Anyone care to nominate a suitable log file? To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1595348/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1595348] Re: Web browser dissapears too often
** Attachment added: "dmesg" https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1595348/+attachment/4689307/+files/dmesg -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1595348 Title: Web browser dissapears too often Status in Canonical System Image: New Status in webbrowser-app package in Ubuntu: New Bug description: M10 tablet.. Ever since upgrading to OTA11 the web browser has become very annoying. If I have, say, 3 tabs on and close one, the browser often dissapears.. I restart it from the apps page and it restarts with all the original tabs, including thecone I tried to close.. I can then closecit again, usually without furthervincident. Or I might open the bookmarks and try to open a new tab, and the browser vanishes. Or, very occasionally I click on a search engine result and 'poof' she is gone! Anyone care to nominate a suitable log file? To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1595348/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1595348] Re: Web browser dissapears too often
** Attachment added: "dmesg.0" https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1595348/+attachment/4689306/+files/dmesg.0 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1595348 Title: Web browser dissapears too often Status in Canonical System Image: New Status in webbrowser-app package in Ubuntu: New Bug description: M10 tablet.. Ever since upgrading to OTA11 the web browser has become very annoying. If I have, say, 3 tabs on and close one, the browser often dissapears.. I restart it from the apps page and it restarts with all the original tabs, including thecone I tried to close.. I can then closecit again, usually without furthervincident. Or I might open the bookmarks and try to open a new tab, and the browser vanishes. Or, very occasionally I click on a search engine result and 'poof' she is gone! Anyone care to nominate a suitable log file? To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1595348/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1595348] Re: Web browser dissapears too often
Ok, getting silly now. I powered the,tablet down this morning, and powered up not long ago.. I was scrolling down the daily telegraph's live news feed about the referendum, trying to guess where the music was coming from, when I found myself looking at the Ubuntu boot-up.. Not the white splash screen, but the orange one with the crawling dots. This thing is,too buggy to use reliably. ** Attachment added: "unity8.log.1.gz" https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1595348/+attachment/4689305/+files/unity8.log.1.gz -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1595348 Title: Web browser dissapears too often Status in Canonical System Image: New Status in webbrowser-app package in Ubuntu: New Bug description: M10 tablet.. Ever since upgrading to OTA11 the web browser has become very annoying. If I have, say, 3 tabs on and close one, the browser often dissapears.. I restart it from the apps page and it restarts with all the original tabs, including thecone I tried to close.. I can then closecit again, usually without furthervincident. Or I might open the bookmarks and try to open a new tab, and the browser vanishes. Or, very occasionally I click on a search engine result and 'poof' she is gone! Anyone care to nominate a suitable log file? To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1595348/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1595348] Re: Web browser dissapears too often
I have just restarted the tablet (bug #1595403) and can now scroll the oneplus page. But the browser still closed when I closed a tab with face book in it. So whilst restarting changed summat it has not fixed the underlying g problem -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1595348 Title: Web browser dissapears too often Status in Canonical System Image: New Status in webbrowser-app package in Ubuntu: New Bug description: M10 tablet.. Ever since upgrading to OTA11 the web browser has become very annoying. If I have, say, 3 tabs on and close one, the browser often dissapears.. I restart it from the apps page and it restarts with all the original tabs, including thecone I tried to close.. I can then closecit again, usually without furthervincident. Or I might open the bookmarks and try to open a new tab, and the browser vanishes. Or, very occasionally I click on a search engine result and 'poof' she is gone! Anyone care to nominate a suitable log file? To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1595348/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1595348] Re: Web browser dissapears too often
This page makes the browser die every time. 1. Go to https://oneplus.net/uk/3 2. Start to scroll down The browser will quit. I have done this 6 times out of 6.. There are no new crash dumps submitted automatically -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1595348 Title: Web browser dissapears too often Status in Canonical System Image: New Status in webbrowser-app package in Ubuntu: New Bug description: M10 tablet.. Ever since upgrading to OTA11 the web browser has become very annoying. If I have, say, 3 tabs on and close one, the browser often dissapears.. I restart it from the apps page and it restarts with all the original tabs, including thecone I tried to close.. I can then closecit again, usually without furthervincident. Or I might open the bookmarks and try to open a new tab, and the browser vanishes. Or, very occasionally I click on a search engine result and 'poof' she is gone! Anyone care to nominate a suitable log file? To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1595348/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1595348] Re: Web browser dissapears too often
The entirety of my crash reports does not contain anything like enough incidents for thenumber of times the browser vanishes https://errors.ubuntu.com/user/283f8b8bdd615ba7aa27a0c29ab9114ca6436a0f2b5bf6ba7899f6304e2e61f8544c1475bbfb7a632c8ed01385e993d9a446a2aac1f648334a98eb266356e4e2 I am seeing around 30 incidents a day ** Attachment added: "screenshot20160623_004819648.png" https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1595348/+attachment/4688782/+files/screenshot20160623_004819648.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1595348 Title: Web browser dissapears too often Status in Canonical System Image: New Status in webbrowser-app package in Ubuntu: New Bug description: M10 tablet.. Ever since upgrading to OTA11 the web browser has become very annoying. If I have, say, 3 tabs on and close one, the browser often dissapears.. I restart it from the apps page and it restarts with all the original tabs, including thecone I tried to close.. I can then closecit again, usually without furthervincident. Or I might open the bookmarks and try to open a new tab, and the browser vanishes. Or, very occasionally I click on a search engine result and 'poof' she is gone! Anyone care to nominate a suitable log file? To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1595348/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1595348] [NEW] Web browser dissapears too often
Public bug reported: M10 tablet.. Ever since upgrading to OTA11 the web browser has become very annoying. If I have, say, 3 tabs on and close one, the browser often dissapears.. I restart it from the apps page and it restarts with all the original tabs, including thecone I tried to close.. I can then closecit again, usually without furthervincident. Or I might open the bookmarks and try to open a new tab, and the browser vanishes. Or, very occasionally I click on a search engine result and 'poof' she is gone! Anyone care to nominate a suitable log file? ** Affects: canonical-devices-system-image Importance: Undecided Status: New ** Affects: webbrowser-app (Ubuntu) Importance: Undecided Status: New ** Also affects: webbrowser-app (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1595348 Title: Web browser dissapears too often Status in Canonical System Image: New Status in webbrowser-app package in Ubuntu: New Bug description: M10 tablet.. Ever since upgrading to OTA11 the web browser has become very annoying. If I have, say, 3 tabs on and close one, the browser often dissapears.. I restart it from the apps page and it restarts with all the original tabs, including thecone I tried to close.. I can then closecit again, usually without furthervincident. Or I might open the bookmarks and try to open a new tab, and the browser vanishes. Or, very occasionally I click on a search engine result and 'poof' she is gone! Anyone care to nominate a suitable log file? To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1595348/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1595348] Re: Web browser dissapears too often
** Attachment added: "unity8.log" https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1595348/+attachment/4688781/+files/unity8.log -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1595348 Title: Web browser dissapears too often Status in Canonical System Image: New Status in webbrowser-app package in Ubuntu: New Bug description: M10 tablet.. Ever since upgrading to OTA11 the web browser has become very annoying. If I have, say, 3 tabs on and close one, the browser often dissapears.. I restart it from the apps page and it restarts with all the original tabs, including thecone I tried to close.. I can then closecit again, usually without furthervincident. Or I might open the bookmarks and try to open a new tab, and the browser vanishes. Or, very occasionally I click on a search engine result and 'poof' she is gone! Anyone care to nominate a suitable log file? To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1595348/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1595348] Re: Web browser dissapears too often
https://errors.ubuntu.com/oops/c3ccc770-3808-11e6-b293-fa163ef911dc might help ?field.comment=https://errors.ubuntu.com/oops/c3ccc770-3808-11e6-b293-fa163ef911dc might help ** Attachment added: "unity8.log.1.gz" https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1595348/+attachment/4688780/+files/unity8.log.1.gz -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1595348 Title: Web browser dissapears too often Status in Canonical System Image: New Status in webbrowser-app package in Ubuntu: New Bug description: M10 tablet.. Ever since upgrading to OTA11 the web browser has become very annoying. If I have, say, 3 tabs on and close one, the browser often dissapears.. I restart it from the apps page and it restarts with all the original tabs, including thecone I tried to close.. I can then closecit again, usually without furthervincident. Or I might open the bookmarks and try to open a new tab, and the browser vanishes. Or, very occasionally I click on a search engine result and 'poof' she is gone! Anyone care to nominate a suitable log file? To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1595348/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1588500] Re: Applications with permission for location claim they don't
Response today from the UK met office: Hi Robert, Thanks for your feedback and investigation into our use of http over https. We are aware of a requirement to move over to https. There would be many systems which might be impacted during a change to https so naturally this may take a long time to implement. Thanks Henry Ford Internet Applications -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1588500 Title: Applications with permission for location claim they don't Status in webbrowser-app package in Ubuntu: Won't Fix Bug description: OTA11 - same problem on BQ4.5phone & M10 tablet. Hurray! Location works on the tablet at last.. HERE maps can get a position. But I can't use the location in the browser or a browser-like web app.. It used to work on the phone in OTA10.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1588500/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1574429] Re: keyboard suggestion: support of tab, shift, arrow keys.
Similar to Bug #1518619 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-keyboard in Ubuntu. https://bugs.launchpad.net/bugs/1574429 Title: keyboard suggestion: support of tab, shift, arrow keys. Status in Canonical System Image: Confirmed Status in Ubuntu UX: New Status in ubuntu-keyboard package in Ubuntu: Confirmed Bug description: The touch keyboard could do with: * a tab key, to make it easier to move to the next field on forms * a right hand shift key * keys for copy/paste * arrow keys to move the insertion point. shiftlock-arrow to make selection highlight. You can file these under 'wishlist' & 'accessibility' -the little blue insertion point handle is too fiddly for someone with Parkinsons or poor eyesight, for example. That said the phone/tablet keyboard is far better than stock IOS if you have shakey hands. Still keep presssing p for backspace, mind. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1574429/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1574606] Re: OSK is uncomfortably huge in a tablet in landscape mode
My Sony Z1 tablet had a small key that would shrink the keyboard in portrait - it toggled left, right, and a sort of split with a gap in the middle. That was /cool/ -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-keyboard in Ubuntu. https://bugs.launchpad.net/bugs/1574606 Title: OSK is uncomfortably huge in a tablet in landscape mode Status in Ubuntu UX: New Status in ubuntu-keyboard package in Ubuntu: Confirmed Bug description: When using the BQ M10 tablet in landscape mode, the virtual keyboard stretches from one side of the screen to the other; this makes it quite uncomfortable to use because of the distance one's finger needs to travel (especially when using one single finger to type). Also the height of the keys could be reduced (just leave them as they are on the phone) as they look quite huge compared to the rest of the UI and take up a lot of real estate on screen. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1574606/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1574429] Re: keyboard suggestion: support of tab, shift, arrow keys.
Honourable mention to Bug #156617 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-keyboard in Ubuntu. https://bugs.launchpad.net/bugs/1574429 Title: keyboard suggestion: support of tab, shift, arrow keys. Status in Canonical System Image: Confirmed Status in Ubuntu UX: New Status in ubuntu-keyboard package in Ubuntu: Confirmed Bug description: The touch keyboard could do with: * a tab key, to make it easier to move to the next field on forms * a right hand shift key * keys for copy/paste * arrow keys to move the insertion point. shiftlock-arrow to make selection highlight. You can file these under 'wishlist' & 'accessibility' -the little blue insertion point handle is too fiddly for someone with Parkinsons or poor eyesight, for example. That said the phone/tablet keyboard is far better than stock IOS if you have shakey hands. Still keep presssing p for backspace, mind. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1574429/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1518619] Re: The keyboard should have cursor keys
See also Bug #1574429 where I also suggested tab and another shift key -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-keyboard in Ubuntu. https://bugs.launchpad.net/bugs/1518619 Title: The keyboard should have cursor keys Status in ubuntu-keyboard: New Status in ubuntu-keyboard package in Ubuntu: Confirmed Bug description: There many places, other than the terminal, where users might enter text, in which they might make typoes: - URLs in browsers - messages - ... However, the keyboard only has cursor keys in the terminal app, but nowhere else. At least left/right would be handy to fix typoes. Indeed, trying to move cursor by tap is very dicey, due to phat phingers and absence of a stylus. ... or if this is considered "opinion", maybe it could become a configuration option? Note: even Android has a so-called "hacker's keyboard" app which does have cursor keys (... and other niceties). As Ubuntu phone is a "hacker's phone" by essence, maybe cursor keys should be standard here :-) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-keyboard/+bug/1518619/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1593306] [NEW] keyboard suggestion: support of (C) and (R) characters
Public bug reported: My Goolge nexus phone is the only one I have with any method of typing the copyright sign (U+00A9) and registered sign (U+00AE). Even it does not allow the TM sign (U+2122) Hows about a long-press option on the C key for (C) and the R key for (R) and the T key for (TM) in the same way that accented letters work? ** Affects: canonical-devices-system-image Importance: Undecided Status: New ** Affects: ubuntu-keyboard (Ubuntu) Importance: Undecided Status: New ** Also affects: ubuntu-keyboard (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-keyboard in Ubuntu. https://bugs.launchpad.net/bugs/1593306 Title: keyboard suggestion: support of (C) and (R) characters Status in Canonical System Image: New Status in ubuntu-keyboard package in Ubuntu: New Bug description: My Goolge nexus phone is the only one I have with any method of typing the copyright sign (U+00A9) and registered sign (U+00AE). Even it does not allow the TM sign (U+2122) Hows about a long-press option on the C key for (C) and the R key for (R) and the T key for (TM) in the same way that accented letters work? To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1593306/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1591452] Re: [SideStage] would be nice for main stage app to reflow when sidestage active
I imagine you want to undupe 1591454 as well. Or instead. I created 1591454 and closed this one bcause I could not understand how to link this to the canonical image. They are essentially the same report, done twice out of frustation with laucnchpad -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1591452 Title: [SideStage] would be nice for main stage app to reflow when sidestage active Status in Ubuntu UX: New Status in unity8 package in Ubuntu: Invalid Bug description: look at the screen grab.. The browser on the left has neither resized nor grown a method of scrolling.. The only way to access the 'report a bug' link is to close the side stage, which sort of makes it pointless having it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1591452/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1591454] Re: [sidestage] main window unaware side stage is open
*** This bug is a duplicate of bug 1592404 *** https://bugs.launchpad.net/bugs/1592404 I'll take your word for it, though it is not immediately obvious it is the same bug! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1591454 Title: [sidestage] main window unaware side stage is open Status in Canonical System Image: New Status in unity8 package in Ubuntu: New Bug description: Look at the screen grab.. The browser on the left has neither resized nor grown a method of scrolling.. The only way to access 'report a bug' is to close the side stage, which sort of negates the point. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1591454/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
