[Touch-packages] [Bug 1849773] Re: /usr/bin/evince:11:strstr:TextSelectionPainter::hasGlyphLessFont:TextSelectionPainter::endPage:TextPage::drawSelection:poppler_page_render_selection
This bug was fixed in the package poppler - 0.80.0-0ubuntu4 --- poppler (0.80.0-0ubuntu4) focal; urgency=medium * debian/patches/glyphless-font.patch: - Detect glyphless font instead of hardcoding name, also fixes segmentation fault because name was nullptr (LP: #1849773) -- Julian Andres Klode Mon, 16 Dec 2019 21:17:56 +0100 ** Changed in: poppler (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to poppler in Ubuntu. https://bugs.launchpad.net/bugs/1849773 Title: /usr/bin/evince:11:strstr:TextSelectionPainter::hasGlyphLessFont:TextSelectionPainter::endPage:TextPage::drawSelection:poppler_page_render_selection Status in poppler package in Ubuntu: Fix Released Status in poppler source package in Eoan: In Progress Bug description: [Impact] Selecting text in evince crashes for some files in eoan [Test case] Open the pdf in bug 1855596 and select some text. [Regression potential] This adds a check for a null pointer before using the pointer; it's limited to a small function checking if a font is glyphless so there is basically no risk for regressio [Error tracker] The Ubuntu Error Tracker has been receiving reports about a problem regarding evince. This problem was most recently seen with package version 3.34.1-1, the problem page at https://errors.ubuntu.com/problem/da5fffc9beac869c0cf863d931ef170c60bb7d93 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1849773/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 814019] Re: epiphany/empathy-chat crashed with SIGSEGV in gtk_widget_hide()
** Changed in: gtk+3.0 (Ubuntu) Status: Triaged => Incomplete -- 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/814019 Title: epiphany/empathy-chat crashed with SIGSEGV in gtk_widget_hide() Status in Empathy: Expired Status in gtk+3.0 package in Ubuntu: Incomplete Bug description: I group the tabs (IRC + XMPP) and crash. ProblemType: Crash DistroRelease: Ubuntu 11.10 Package: empathy 3.1.3-1ubuntu1 ProcVersionSignature: Ubuntu 3.0.0-5.6-generic 3.0.0-rc7 Uname: Linux 3.0.0-5-generic x86_64 Architecture: amd64 Date: Thu Jul 21 07:07:44 2011 ExecutablePath: /usr/lib/empathy/empathy-chat InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha amd64 (20110531.1) ProcCmdline: /usr/lib/empathy/empathy-chat ProcEnviron: SHELL=/bin/bash LANG=es_CL.UTF-8 SegvAnalysis: Segfault happened at: 0x7f68c84d0589:mov0x70(%rax),%ecx PC (0x7f68c84d0589) ok source "0x70(%rax)" (0xab1a) not located in a known VMA region (needed readable region)! destination "%ecx" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: empathy StacktraceTop: ?? () from /usr/lib/libgtk-3.so.0 gtk_widget_hide () from /usr/lib/libgtk-3.so.0 ?? () from /usr/lib/libgtk-3.so.0 ?? () from /usr/lib/libgtk-3.so.0 ?? () from /usr/lib/libgtk-3.so.0 Title: empathy-chat crashed with SIGSEGV in gtk_widget_hide() UpgradeStatus: Upgraded to oneiric on 2011-07-16 (5 days ago) UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare To manage notifications about this bug go to: https://bugs.launchpad.net/empathy/+bug/814019/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1848571] Re: APT does not honour [trusted=yes] when added to sources.list
[Expired for apt (Ubuntu) because there has been no activity for 60 days.] ** Changed in: apt (Ubuntu) Status: Incomplete => Expired -- 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/1848571 Title: APT does not honour [trusted=yes] when added to sources.list Status in apt package in Ubuntu: Expired Bug description: When adding the PPA for NordVPN the GPG key did not save properly. In order to resolve this, I added [trusted=yes] to sources.list.d/nordvpn.list and sources.list.d/nordvpn.list.save. APT, when running apt update, did not honour this and instead checked the GPG key. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: apt 1.8.1 ProcVersionSignature: Ubuntu 5.0.0-31.33-generic 5.0.21 Uname: Linux 5.0.0-31-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Oct 17 15:19:05 2019 InstallationDate: Installed on 2019-07-21 (87 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: apt UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1848571/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1774757] Re: package libgraphite2-3 1.3.11-2 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libgraphite2-3/changelog.Debian.gz', which is different from ot
[Expired for graphite2 (Ubuntu) because there has been no activity for 60 days.] ** Changed in: graphite2 (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to graphite2 in Ubuntu. https://bugs.launchpad.net/bugs/1774757 Title: package libgraphite2-3 1.3.11-2 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libgraphite2-3/changelog.Debian.gz', which is different from other instances of package libgraphite2-3:i386 Status in graphite2 package in Ubuntu: Expired Bug description: everytime i turn on my pc it shows the error ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libgraphite2-3 1.3.11-2 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 Date: Sat Jun 2 09:52:02 2018 Dependencies: gcc-8-base 8-20180414-1ubuntu2 libc6 2.27-3ubuntu1 libgcc1 1:8-20180414-1ubuntu2 DuplicateSignature: package:libgraphite2-3:1.3.11-2 Unpacking libgraphite2-3:i386 (1.3.11-2) ... dpkg: error processing archive /tmp/apt-dpkg-install-WRx3Ga/12-libgraphite2-3_1.3.11-2_i386.deb (--unpack): trying to overwrite shared '/usr/share/doc/libgraphite2-3/changelog.Debian.gz', which is different from other instances of package libgraphite2-3:i386 ErrorMessage: trying to overwrite shared '/usr/share/doc/libgraphite2-3/changelog.Debian.gz', which is different from other instances of package libgraphite2-3:i386 InstallationDate: Installed on 2018-05-24 (8 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: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.1 SourcePackage: graphite2 Title: package libgraphite2-3 1.3.11-2 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libgraphite2-3/changelog.Debian.gz', which is different from other instances of package libgraphite2-3:i386 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/graphite2/+bug/1774757/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1173915] Re: initctl continuously takes 100% of CPU
Issue finally went away for me after upgrading to 18.04.3 LTS. -- 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/1173915 Title: initctl continuously takes 100% of CPU Status in upstart : Confirmed Status in upstart package in Ubuntu: Confirmed Bug description: Many programs are fairly slow to start on my computer, despite it being relatively new (core i5). Suspecting a heavy CPU usage, I started gnome-system-monitor: all processes were displayed at 0% CPU, but the overall load was 1.33; 1.33; 1.34. Using the "top" command, however, revealed the real CPU use, with the "initctl" process taking 100%CPU, even 1 hour after startup. I upgraded to roaring ringtail before checking this but the symptoms were the same with quantal quetzal, so there is a fair chance the causes were identical. Regards ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: upstart 1.8-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8 Uname: Linux 3.8.0-19-generic x86_64 ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 CheckboxSubmission: 2deefc5fd2f1f0ae2fdd4bd781248a2a CheckboxSystem: daed2f3d6643b4a84b4520a2427f8c2b Date: Sun Apr 28 13:04:05 2013 ExecutablePath: /sbin/initctl InstallationDate: Installed on 2012-12-15 (133 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) MarkForUpload: True ProcEnviron: ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.8.0-19-generic root=UUID=fa624f8f-d9d0-4b09-af8b-88b106aaaf5b ro quiet splash vt.handoff=7 SourcePackage: upstart UpgradeStatus: Upgraded to raring on 2013-04-28 (0 days ago) UpstartBugCategory: System To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/1173915/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1173915] Re: initctl continuously takes 100% of CPU
Have the same issue
1504 root 20 0 103700 87464 1752 R 97.1 0.3 4525:02
initctl
> sudo strace -p `pidof initctl`
$ poll([{fd=3, events=POLLIN}], 1, 3729760780) = 1 ([{fd=3, revents=POLLIN}])
endless repeat...
This report is open since 2013 and I'm reporting in 2019. Is there any solution
to this issue??
Thanks
--
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/1173915
Title:
initctl continuously takes 100% of CPU
Status in upstart :
Confirmed
Status in upstart package in Ubuntu:
Confirmed
Bug description:
Many programs are fairly slow to start on my computer, despite it
being relatively new (core i5). Suspecting a heavy CPU usage, I
started gnome-system-monitor: all processes were displayed at 0% CPU,
but the overall load was 1.33; 1.33; 1.34.
Using the "top" command, however, revealed the real CPU use, with the
"initctl" process taking 100%CPU, even 1 hour after startup.
I upgraded to roaring ringtail before checking this but the symptoms
were the same with quantal quetzal, so there is a fair chance the
causes were identical.
Regards
ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: upstart 1.8-0ubuntu1
ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8
Uname: Linux 3.8.0-19-generic x86_64
ApportVersion: 2.9.2-0ubuntu8
Architecture: amd64
CheckboxSubmission: 2deefc5fd2f1f0ae2fdd4bd781248a2a
CheckboxSystem: daed2f3d6643b4a84b4520a2427f8c2b
Date: Sun Apr 28 13:04:05 2013
ExecutablePath: /sbin/initctl
InstallationDate: Installed on 2012-12-15 (133 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
MarkForUpload: True
ProcEnviron:
ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.8.0-19-generic
root=UUID=fa624f8f-d9d0-4b09-af8b-88b106aaaf5b ro quiet splash vt.handoff=7
SourcePackage: upstart
UpgradeStatus: Upgraded to raring on 2013-04-28 (0 days ago)
UpstartBugCategory: System
To manage notifications about this bug go to:
https://bugs.launchpad.net/upstart/+bug/1173915/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1856592] Re: Nautilus button icons are missing
** Summary changed: - modified graphic of progrwms + Nautilus button icons are missing ** Also affects: ubuntu-themes (Ubuntu) Importance: Undecided Status: New ** Changed in: gtk+3.0 (Ubuntu) Status: Incomplete => New -- 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/1856592 Title: Nautilus button icons are missing Status in gtk+3.0 package in Ubuntu: New Status in ubuntu-themes package in Ubuntu: New Bug description: in some programs th little icons that allow to undo or redo or the icons that allow to go up or down appear like some little squares! I don't know how can I solve this problem! ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-72.81~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-72-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.21 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 Date: Mon Dec 16 17:40:38 2019 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display [8086:0f31] (rev 0e) (prog-if 00 [VGA controller]) Subsystem: Lenovo Atom Processor Z36xxx/Z37xxx Series Graphics & Display [17aa:3905] InstallationDate: Installed on 2019-12-07 (8 days ago) InstallationMedia: Ubuntu 16.04.6 LTS "Xenial Xerus" - Release amd64 (20190227) MachineType: LENOVO 80G0 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-72-generic root=UUID=42ddfb90-969c-4976-998c-893d136068bb ro splash quiet pci=nomsi RESUME=UUID=92781adb-f2a6-4f15-88fc-e1ce801291dd vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/22/2015 dmi.bios.vendor: LENOVO dmi.bios.version: A7CN45WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Lancer 5A6 dmi.board.vendor: LENOVO dmi.board.version: NANANANANO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo G50-30 dmi.modalias: dmi:bvnLENOVO:bvrA7CN45WW:bd01/22/2015:svnLENOVO:pn80G0:pvrLenovoG50-30:rvnLENOVO:rnLancer5A6:rvrNANANANANODPK:cvnLENOVO:ct10:cvrLenovoG50-30: dmi.product.family: IDEAPAD dmi.product.name: 80G0 dmi.product.version: Lenovo G50-30 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.91-2~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Mon Dec 16 17:31:25 2019 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu4.1~16.04.2 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1856592/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1856554] Re: Epic bug which affects keyboard responsiveness (zomg :p)
** Package changed: wayland (Ubuntu) => ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1856554 Title: Epic bug which affects keyboard responsiveness (zomg :p) Status in Ubuntu: Incomplete Bug description: Open terminal. Type /\^/__ (_ character as space) Leave terminal open you might have to snap it on a desktop in a certain way ~ https://bugzilla.redhat.com/show_bug.cgi?id=1674486 https://bugs.launchpad.net/ubuntu/+source/xfce4/+bug/1838154 Keep terminal in a first place of opened windows list. Result: responsive keyboard that doesn't lag better scrolling looks like this even affects loading performance >:] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1856554/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1827644] Re: UPower and battery indicator show wrong information on fully charged ASUS Vivobook X510UR laptop
Even I Have this issue , Battery is showing red Icon / image at 48% . What is this ? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1827644 Title: UPower and battery indicator show wrong information on fully charged ASUS Vivobook X510UR laptop Status in upower package in Ubuntu: Confirmed Bug description: When the ASUS Vivobook X510UR laptop is completely charged, the correct information is displayed on Windows. However, Ubuntu 18.04.2 LTS is unable to detect the true battery state. The GNOME battery indicator usually shows "Estimating..." or "Not charging", when the battery is at 100%. If you use the upower version 0.99.7-2ubuntu0.18.04.1 command "upower -i /org/freedesktop/UPower/devices/battery_BAT0", this is what you get: native-path: BAT0 vendor: ASUSTeK model:ASUS Battery power supply: yes updated: sex 03 mai 2019 14:33:43 -03 (4 seconds ago) has history: yes has statistics: yes battery present: yes rechargeable:yes state: pending-charge warning-level: none energy: 39,191 Wh energy-empty:0 Wh energy-full: 39,26 Wh energy-full-design: 42,082 Wh energy-rate: 12,453 W voltage: 11,52 V percentage: 100% capacity:93,294% technology: lithium-ion icon-name: 'battery-full-charging-symbolic' History (charge): 1556904821100,000 discharging History (rate): 155690482112,453 discharging 15569048183,744 discharging The "state" should be "fully-charged", but instead it is "pending- charge". ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: upower 0.99.7-2ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 4.18.0-18.19~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: GNOME Date: Fri May 3 14:34:14 2019 InstallationDate: Installed on 2018-12-11 (142 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcEnviron: LANGUAGE=pt_BR:pt:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pt_BR.UTF-8 SHELL=/bin/bash SourcePackage: upower UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1827644/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1843479] Re: gzip in Ubuntu Eoan results in Exec format error on WSL1
This bug was fixed in the package gzip - 1.10-0ubuntu4
---
gzip (1.10-0ubuntu4) focal; urgency=high
* Rebuild with binutils 2.33.1-6ubuntu1 (LP: #1843479)
- Build-depend on binutils (>= 2.33.1-6ubuntu1)
* Pass -fstack-protector to mingw build to fix FTBFS
-- Balint Reczey Fri, 13 Dec 2019 16:41:46 +0100
** Changed in: gzip (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to binutils in Ubuntu.
https://bugs.launchpad.net/bugs/1843479
Title:
gzip in Ubuntu Eoan results in Exec format error on WSL1
Status in binutils:
Confirmed
Status in binutils package in Ubuntu:
Fix Released
Status in gzip package in Ubuntu:
Fix Released
Status in binutils source package in Eoan:
Fix Committed
Status in gzip source package in Eoan:
Fix Committed
Bug description:
[Impact]
* Running gzip on WSL1 results in the following error:
$ gzip
-bash: /bin/gzip: cannot execute binary file: Exec format error
* The error occurs frequently in package updates and makes gzip inoperable
on WSL1
* The problem is caused by PT_LOAD offset pointing past the end of file and
the fix is fixing strip to not generate such ELF files and recompiling gzip
with the fixed strip.
[Test Case]
* Check the gzip binary for wrong offset:
$ FILE=/usr/bin/gzip; readelf -W --program-headers $FILE | awk -v
size=$(stat -c %s $FILE) '/^ LOAD/ {if (strtonum($2) > size) {print "wrong
offset ("$2" ("strtonum($2)") points past EOF:" size; exit 1;}}'
[ Regression Potential ]
* The binutils fix could cause binutils to generate invalid ELF files. The
fix is very small and isolated and has been tested and accepted by upstream,
which makes such problems unlikely.
* Bugs in the toolchain in general can make the rebuilt gzip show new
errors, but this generally applies to many SRUs and security updates. The
testing period in proposed should mitigate this risk.
[Originial Bug Text]
Summary:
Running gzip on WSL1 results in the following error:
$ gzip
-bash: /bin/gzip: cannot execute binary file: Exec format error
What I expect to happen:
gzip executes correctly on WSL1.
What happens instead:
gzip fails with an Exec format error.
Notes:
I suspect a change in how gzip is being built for Eoan is causing
issues with ELF parsing on the WSL1 translation layer. For example:
On Disco with gzip 1.9-3:
$ file /bin/gzip
/bin/gzip: ELF 64-bit LSB pie executable, x86-64, version 1 (SYSV),
dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux
3.2.0, BuildID[sha1]=efa859c26eaf8e035efe9a139361e2a60cd17b3e, stripped
On Eoan with gzip 1.10-0ubuntu3:
$ file /bin/gzip
/bin/gzip: ELF 64-bit LSB pie executable, x86-64, version 1 (SYSV),
dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2,
BuildID[sha1]=bc0f5994544c2a469d04c914bf4bf44b4ded6040, for GNU/Linux 3.2.0,
stripped
Eoan ships with gzip 1.10, while Disco ships with gzip 1.9, but I do
not believe this is an issue in 1.10 because this error does not occur
when building gzip from GNU project source on Ubuntu Eoan.
Justifications:
WSL1 will need to be patched in future Windows builds for this change
in ELF. However that patch will likely not be backported to older
builds of Windows, including Windows Enterprise/Server 2019.
To ensure Eoan can run on current and older builds of Windows Ubuntu
should consider looking at how it's building gzip and see if it can be
made to 'play nice' until WSL1 can be updated.
This was originally reported here:
https://github.com/microsoft/WSL/issues/4461
Details:
Description:Ubuntu Eoan Ermine (development branch)
Release:19.10
gzip:
Installed: 1.10-0ubuntu3
Candidate: 1.10-0ubuntu3
Version table:
*** 1.10-0ubuntu3 500
500 http://archive.ubuntu.com/ubuntu eoan/main amd64 Packages
100 /var/lib/dpkg/status
To manage notifications about this bug go to:
https://bugs.launchpad.net/binutils/+bug/1843479/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1814529] Re: apport-bug does nothing after choosing the "Send" option
Although it was reliably reproducable at the time, I can no longer reproduce this bug (using ubuntu-bug version 2.20.9 on Ubuntu Bionic). Perhaps it's been fixed incidentally. ** Changed in: apport (Ubuntu) Status: New => Invalid -- 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/1814529 Title: apport-bug does nothing after choosing the "Send" option Status in apport package in Ubuntu: Invalid Bug description: After running apport-bug as, e.g., `apport-bug apport` (which I attempted to use to file this bug), it (as expected) puts up a dialog box specifying collected information, then shows that information with two options, "Send" and "Don't Send". However, clicking either button closes apport-bug with no visible further effect (and no messages on standard output or standard error). Expected behaviour is for apport- bug to open a page in my Web browser to allow me to file the bug. If I revoke my computer's authorisation at https://launchpad.net/~ais523/+oauth-tokens and then repeat the process, there's no change to the observed behaviour (in particular, apport-bug doesn't ask for a new one). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1814529/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1856622] [NEW] Despite being connected to the Internet, Ubuntu was unable to retrieve any data due to having a "temporary failue in name resolution" every single time until I res
Public bug reported: Despite this laptop's being connected to the network that is connected to the Internet, network manager was saying how the network had "poor name resolution" despite the network working fine. I had to restart BOTH ubuntu and network manager for this to work. network-manager: Installed: 1.20.4-2ubuntu2 Candidate: 1.20.4-2ubuntu2 Version table: *** 1.20.4-2ubuntu2 500 500 http://us.archive.ubuntu.com/ubuntu eoan/main amd64 Packages 100 /var/lib/dpkg/status Ubuntu 19.10 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: network-manager 1.20.4-2ubuntu2 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Dec 16 18:36:40 2019 InstallationDate: Installed on 2019-11-20 (26 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) IpRoute: default via 192.168.43.1 dev wlp2s0 proto dhcp metric 600 169.254.0.0/16 dev wlp2s0 scope link metric 1000 192.168.43.0/24 dev wlp2s0 proto kernel scope link src 192.168.43.201 metric 600 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.apport.crashdb.conf: 2019-11-27T12:43:30.211160 nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.20.4 connected started full enabled enabled enabled enabled enabled ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan ** Attachment added: "Image of what the desktop looked like when the issue was occurring." https://bugs.launchpad.net/bugs/1856622/+attachment/5313074/+files/Screenshot%20from%202019-12-16%2018-26-21.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1856622 Title: Despite being connected to the Internet, Ubuntu was unable to retrieve any data due to having a "temporary failue in name resolution" every single time until I restarted BOTH Ubuntu and the router Status in network-manager package in Ubuntu: New Bug description: Despite this laptop's being connected to the network that is connected to the Internet, network manager was saying how the network had "poor name resolution" despite the network working fine. I had to restart BOTH ubuntu and network manager for this to work. network-manager: Installed: 1.20.4-2ubuntu2 Candidate: 1.20.4-2ubuntu2 Version table: *** 1.20.4-2ubuntu2 500 500 http://us.archive.ubuntu.com/ubuntu eoan/main amd64 Packages 100 /var/lib/dpkg/status Ubuntu 19.10 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: network-manager 1.20.4-2ubuntu2 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Dec 16 18:36:40 2019 InstallationDate: Installed on 2019-11-20 (26 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) IpRoute: default via 192.168.43.1 dev wlp2s0 proto dhcp metric 600 169.254.0.0/16 dev wlp2s0 scope link metric 1000 192.168.43.0/24 dev wlp2s0 proto kernel scope link src 192.168.43.201 metric 600 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.apport.crashdb.conf: 2019-11-27T12:43:30.211160 nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.20.4 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1856622/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1794478] Re: Automatic ipv4 not assigned to bond interface is manual ipv6 is assigned to it
** Changed in: network-manager (Ubuntu Bionic) Assignee: Till Kamppeter (till-kamppeter) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1794478 Title: Automatic ipv4 not assigned to bond interface is manual ipv6 is assigned to it Status in Ubuntu on IBM z Systems: Fix Released Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Bionic: Confirmed Bug description: ---Problem Description--- Bond interface with automatic ipv4 mode and manual ipv6 mode fails to get automatic ipv4 assigned from dhcp server. ---uname output--- Linux NetworkTest 4.15.0-33-generic #36-Ubuntu SMP Wed Aug 15 13:42:17 UTC 2018 s390x s390x s390x GNU/Linux Machine Type = s390x ---Debugger--- A debugger is not configured ---Steps to Reproduce--- When user configures ipv4 as automatic and ipv6 as manual for bond interface automatic ipv4 is not getting assigned. Looks like dhcp client request for ipv4 is not done to dhcp server after maunal ipv6 is assigned quickly to bond interface This issue will not happen in below cases: 1)with ipv4 automatic and ipv6 manual configuration for ethernet or vlan interface. 2)with ipv4 automatic and ipv6 automatic configuration for bond interface 3)with ipv4 automatic and ipv6 disabled configuration for bond interface Configuration: Bond interface, ipv4 automatic mode and ipv6 automatic mode root@NetworkTest:/etc/NetworkManager/system-connections# cat test_bond [connection] id=test_bond uuid=63e54542-5135-47ac-a954-b861c3937be2 type=bond interface-name=test_bond permissions= timestamp=1537944121 [ethernet] mac-address-blacklist= [bond] downdelay=0 fail_over_mac=none miimon=100 mode=active-backup num_grat_arp=0 primary_reselect=always updelay=0 [ipv4] dns-search= method=auto [ipv6] addr-gen-mode=stable-privacy dns-search= method=auto From /var/log/syslog, we can see ip got assigned: Sep 26 06:26:26 NetworkTest dhclient[8663]: DHCPDISCOVER on test_bond to 255.255.255.255 port 67 interval 3 (xid=0x5e04bf1e) Sep 26 06:26:26 NetworkTest dhclient[8663]: DHCPREQUEST of 10.2.3.55 on test_bond to 255.255.255.255 port 67 (xid=0x5e04bf1e) Sep 26 06:26:26 NetworkTest dhclient[8663]: DHCPOFFER of 10.2.3.55 from 10.2.3.1 Sep 26 06:26:26 NetworkTest dhclient[8663]: DHCPACK of 10.2.3.55 from 10.2.3.1 root@NetworkTest:/etc/NetworkManager/system-connections# ip a s test_bond 28: test_bond: mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 02:00:00:b3:b5:22 brd ff:ff:ff:ff:ff:ff inet 10.2.3.55/24 brd 10.2.3.255 scope global dynamic noprefixroute test_bond valid_lft 353sec preferred_lft 353sec inet6 fe80::ff:feb3:b522/64 scope link valid_lft forever preferred_lft forever +++ Bond interface, ipv4 automatic mode and ipv6 manual mode root@NetworkTest:/etc/NetworkManager/system-connections# cat test_bond [connection] id=test_bond uuid=3efb153a-a6e4-48fb-aa04-f0b8cb549bab type=bond interface-name=test_bond permissions= timestamp=1537943300 [ethernet] mac-address-blacklist= [bond] downdelay=0 fail_over_mac=none miimon=100 mode=active-backup num_grat_arp=0 primary_reselect=always updelay=0 [ipv4] dns-search= method=auto [ipv6] addr-gen-mode=stable-privacy address1=fe81::32a5:bc5f:287f:8db8/64 dns-search= method=manual No automatic ip assigned to ipv4 and no requests to dhcp server seen in /var/log/syslog root@NetworkTest:/etc/NetworkManager/system-connections# ip a s test_bond 29: test_bond: mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 02:00:00:b3:b5:22 brd ff:ff:ff:ff:ff:ff inet6 fe81::32a5:bc5f:287f:8db8/64 scope link noprefixroute valid_lft forever preferred_lft forever ==> Correct LP-Package need to be assigned...! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1794478/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1783881] Re: ltp-syscalls: msgstress03 fails because systemd limits number of processes
** Tags added: azure ** Also affects: linux-azure (Ubuntu) Importance: Undecided Status: New ** No longer affects: linux (Ubuntu Cosmic) ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux-azure (Ubuntu Bionic) 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/1783881 Title: ltp-syscalls: msgstress03 fails because systemd limits number of processes Status in ubuntu-kernel-tests: Triaged Status in linux package in Ubuntu: Incomplete Status in linux-azure package in Ubuntu: New Status in systemd package in Ubuntu: Incomplete Status in linux source package in Xenial: New Status in linux-azure source package in Xenial: New Status in systemd source package in Xenial: New Status in linux source package in Bionic: New Status in linux-azure source package in Bionic: New Status in systemd source package in Bionic: New Bug description: As systemd limits the number of processes, this test will fail because it can't fork enough processes. That is limited to when the test is run after logging as user 1000, then running sudo. I guess that logging as root may not cause this to happen. # ./testcases/bin/msgstress03 Fork failed (may be OK if under stress) Fork failed (may be OK if under stress) msgstress031 TFAIL : msgstress03.c:157: Fork failed (may be OK if under stress) # To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1783881/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1856613] Re: apt upgrade wants to install openjdk-11-jre-headless without upgprading anything
Yeah, that happens sometimes, it's a side-effect of how apt's solver works - it can't properly undo everything it did all the time. -- 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/1856613 Title: apt upgrade wants to install openjdk-11-jre-headless without upgprading anything Status in apt package in Ubuntu: New Bug description: Notable, upon logging in, I get this message: ``` 3 packages can be updated. 1 update is a security update. ``` This is fairly misleading, since afaict, the three packages it's listing as "updated" are in fact "new installs" as opposed to "upgrades". However, that isn't the primary point of my bug report. I'm actually relying on that information via: /usr/lib/update-notifier/apt-check 2>&1|sed -e "s/;.*//" /usr/lib/update-notifier/apt-check 2>&1|sed -e "s/.*;//" So, I connect to the box and perform: `apt upgrade`: ``` Hit:1 http://us-east-2.ec2.archive.ubuntu.com/ubuntu bionic InRelease Hit:2 http://us-east-2.ec2.archive.ubuntu.com/ubuntu bionic-updates InRelease Hit:3 http://us-east-2.ec2.archive.ubuntu.com/ubuntu bionic-backports InRelease Hit:4 http://security.ubuntu.com/ubuntu bionic-security InRelease Ign:5 http://debian.neo4j.org/repo stable/ InRelease Get:6 http://debian.neo4j.org/repo stable/ Release [1479 B] Get:7 http://debian.neo4j.org/repo stable/ Release.gpg [819 B] Hit:8 https://repo.zabbix.com/zabbix/4.0/ubuntu bionic InRelease Fetched 2298 B in 1s (4382 B/s) Reading package lists... Done Building dependency tree Reading state information... Done 1 package can be upgraded. Run 'apt list --upgradable' to see it. Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following NEW packages will be installed: libasound2 libasound2-data openjdk-11-jre-headless The following packages have been kept back: cypher-shell 0 upgraded, 3 newly installed, 0 to remove and 1 not upgraded. Need to get 37.8 MB of archives. After this operation, 173 MB of additional disk space will be used. Do you want to continue? [Y/n] n ``` Apt apparently discovered a newer version of `cypher-shell`. That newer version requires `openjdk-11-jre-headless`, so it added that to the list of things to install. That new package requires two additional packages (`libasound2` and `libasound2-data`). `apt` then discovers that this newer version of `cypher-shell` conflicts w/ a manually installed package (`neo4j`). It thus marks `cypher-shell` as `kept-back`, unfortunately, it doesn't discard its plans to install java11. For comparison, `apt-get upgrade` just recognizes that it shouldn't upgrade `cypher-shell`: `apt-get upgrade`: ``` Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following packages have been kept back: cypher-shell 0 upgraded, 0 newly installed, 0 to remove and 1 not upgraded. ``` ``` lsb_release -rd Description: Ubuntu 18.04.3 LTS Release: 18.04 ``` `apt-cache policy apt cypher-shell neo4j openjdk-11-jre-headless:amd64 openjdk-8-jre-headless:amd64`: ``` apt: Installed: 1.6.12 Candidate: 1.6.12 Version table: *** 1.6.12 500 500 http://us-east-2.ec2.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.6.6ubuntu0.1 500 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 1.6.1 500 500 http://us-east-2.ec2.archive.ubuntu.com/ubuntu bionic/main amd64 Packages cypher-shell: Installed: 1.1.12 Candidate: 4.0.0 Version table: 4.0.0 500 500 http://debian.neo4j.org/repo stable/ Packages *** 1.1.12 500 500 http://debian.neo4j.org/repo stable/ Packages 100 /var/lib/dpkg/status ... neo4j: Installed: 1:3.5.13 Candidate: 1:3.5.13 Version table: *** 1:3.5.13 500 500 http://debian.neo4j.org/repo stable/ Packages 100 /var/lib/dpkg/status ... openjdk-11-jre-headless: Installed: (none) Candidate: 11.0.4+11-1ubuntu2~18.04.3 Version table: 11.0.4+11-1ubuntu2~18.04.3 500 500 http://us-east-2.ec2.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 10.0.1+10-3ubuntu1 500 500 http://us-east-2.ec2.archive.ubuntu.com/ubuntu bionic/main amd64 Packages openjdk-8-jre-headless: Installed: 8u222-b10-1ubuntu1~18.04.1 Candidate: 8u222-b10-1ubuntu1~18.04.1 Version table: *** 8u222-b10-1ubuntu1~18.04.1 500 500 http://us-east-2.ec2.archive.ubuntu.com/ubuntu bionic-updates/universe amd64
[Touch-packages] [Bug 1845529] Re: bash completion shows `awk: line 18: function gensub never defined` on `umount /dev/`
This bug was fixed in the package util-linux - 2.34-0.1ubuntu4 --- util-linux (2.34-0.1ubuntu4) focal; urgency=medium * bash-completion/umount: fix completion to not require gawk be present. Thanks to Étienne Mollier for the patch. (LP: #1845529) -- Mathieu Trudel-Lapierre Tue, 03 Dec 2019 15:27:13 -0500 ** Changed in: util-linux (Ubuntu Focal) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1845529 Title: bash completion shows `awk: line 18: function gensub never defined` on `umount /dev/` Status in bash-completion package in Ubuntu: Incomplete Status in gawk package in Ubuntu: Invalid Status in mawk package in Ubuntu: Invalid Status in ubuntu-meta package in Ubuntu: Invalid Status in util-linux package in Ubuntu: Fix Released Status in bash-completion source package in Focal: Incomplete Status in gawk source package in Focal: Invalid Status in mawk source package in Focal: Invalid Status in ubuntu-meta source package in Focal: Invalid Status in util-linux source package in Focal: Fix Released Status in Debian: Confirmed Bug description: Steps to reproduce: 1. Install Ubuntu MATE 19.10 using minimal desktop option 2. Open terminal and enter `umount /dev/s` and then hit Expected result: * bash completion works as expected Actual results: * bash completion does not work : $ umount /dev/awk: line 18: function gensub never defined awk: line 18: function gensub never defined awk: line 18: function gensub never defined awk: line 18: function gensub never defined $ umount /meawk: line 18: function gensub never defined awk: line 18: function gensub never defined awk: line 18: function gensub never defined awk: line 18: function gensub never defined ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: bash-completion 1:2.9-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8 Uname: Linux 5.3.0-10-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: MATE Date: Thu Sep 26 18:46:59 2019 Dependencies: InstallationDate: Installed on 2019-09-26 (0 days ago) InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Beta amd64 (20190926.1) PackageArchitecture: all SourcePackage: bash-completion UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash-completion/+bug/1845529/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1849773] Re: /usr/bin/evince:11:strstr:TextSelectionPainter::hasGlyphLessFont:TextSelectionPainter::endPage:TextPage::drawSelection:poppler_page_render_selection
** Changed in: poppler (Ubuntu Eoan) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to poppler in Ubuntu. https://bugs.launchpad.net/bugs/1849773 Title: /usr/bin/evince:11:strstr:TextSelectionPainter::hasGlyphLessFont:TextSelectionPainter::endPage:TextPage::drawSelection:poppler_page_render_selection Status in poppler package in Ubuntu: Fix Committed Status in poppler source package in Eoan: In Progress Bug description: [Impact] Selecting text in evince crashes for some files in eoan [Test case] Open the pdf in bug 1855596 and select some text. [Regression potential] This adds a check for a null pointer before using the pointer; it's limited to a small function checking if a font is glyphless so there is basically no risk for regressio [Error tracker] The Ubuntu Error Tracker has been receiving reports about a problem regarding evince. This problem was most recently seen with package version 3.34.1-1, the problem page at https://errors.ubuntu.com/problem/da5fffc9beac869c0cf863d931ef170c60bb7d93 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1849773/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1849773] Re: /usr/bin/evince:11:strstr:TextSelectionPainter::hasGlyphLessFont:TextSelectionPainter::endPage:TextPage::drawSelection:poppler_page_render_selection
** Description changed: + [Impact] + Selecting text in evince crashes for some files in eoan + + [Test case] + + Open the pdf in bug 1855596 and select some text. + + [Regression potential] + This adds a check for a null pointer before using the pointer; it's limited to a small function checking if a font is glyphless so there is basically no risk for regressio + + [Error tracker] The Ubuntu Error Tracker has been receiving reports about a problem regarding evince. This problem was most recently seen with package version 3.34.1-1, the problem page at https://errors.ubuntu.com/problem/da5fffc9beac869c0cf863d931ef170c60bb7d93 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. - - Test Case: - 1. Select some text in the document - - Expected result - Text is selected - - Actual result - This crash. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to poppler in Ubuntu. https://bugs.launchpad.net/bugs/1849773 Title: /usr/bin/evince:11:strstr:TextSelectionPainter::hasGlyphLessFont:TextSelectionPainter::endPage:TextPage::drawSelection:poppler_page_render_selection Status in poppler package in Ubuntu: Fix Committed Status in poppler source package in Eoan: In Progress Bug description: [Impact] Selecting text in evince crashes for some files in eoan [Test case] Open the pdf in bug 1855596 and select some text. [Regression potential] This adds a check for a null pointer before using the pointer; it's limited to a small function checking if a font is glyphless so there is basically no risk for regressio [Error tracker] The Ubuntu Error Tracker has been receiving reports about a problem regarding evince. This problem was most recently seen with package version 3.34.1-1, the problem page at https://errors.ubuntu.com/problem/da5fffc9beac869c0cf863d931ef170c60bb7d93 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1849773/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1849773] Re: /usr/bin/evince:11:strstr:TextSelectionPainter::hasGlyphLessFont:TextSelectionPainter::endPage:TextPage::drawSelection:poppler_page_render_selection
That file was for reproducing the original bug fixed by the patch; bug 1855596 contains a file for reproducing this crash. ** Also affects: poppler (Ubuntu Eoan) Importance: Undecided Status: New ** Changed in: poppler (Ubuntu) Status: In Progress => Fix Committed ** Changed in: poppler (Ubuntu Eoan) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to poppler in Ubuntu. https://bugs.launchpad.net/bugs/1849773 Title: /usr/bin/evince:11:strstr:TextSelectionPainter::hasGlyphLessFont:TextSelectionPainter::endPage:TextPage::drawSelection:poppler_page_render_selection Status in poppler package in Ubuntu: Fix Committed Status in poppler source package in Eoan: New Bug description: [Impact] Selecting text in evince crashes for some files in eoan [Test case] Open the pdf in bug 1855596 and select some text. [Regression potential] This adds a check for a null pointer before using the pointer; it's limited to a small function checking if a font is glyphless so there is basically no risk for regressio [Error tracker] The Ubuntu Error Tracker has been receiving reports about a problem regarding evince. This problem was most recently seen with package version 3.34.1-1, the problem page at https://errors.ubuntu.com/problem/da5fffc9beac869c0cf863d931ef170c60bb7d93 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1849773/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1849773] Re: /usr/bin/evince:11:strstr:TextSelectionPainter::hasGlyphLessFont:TextSelectionPainter::endPage:TextPage::drawSelection:poppler_page_render_selection
Attached a test file, created by taking a screenshot, printing the screenshot to PDF, and running the PDF through ocrmypdf. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to poppler in Ubuntu. https://bugs.launchpad.net/bugs/1849773 Title: /usr/bin/evince:11:strstr:TextSelectionPainter::hasGlyphLessFont:TextSelectionPainter::endPage:TextPage::drawSelection:poppler_page_render_selection Status in poppler package in Ubuntu: Fix Committed Status in poppler source package in Eoan: New Bug description: [Impact] Selecting text in evince crashes for some files in eoan [Test case] Open the pdf in bug 1855596 and select some text. [Regression potential] This adds a check for a null pointer before using the pointer; it's limited to a small function checking if a font is glyphless so there is basically no risk for regressio [Error tracker] The Ubuntu Error Tracker has been receiving reports about a problem regarding evince. This problem was most recently seen with package version 3.34.1-1, the problem page at https://errors.ubuntu.com/problem/da5fffc9beac869c0cf863d931ef170c60bb7d93 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1849773/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1849773] Re: /usr/bin/evince:11:strstr:TextSelectionPainter::hasGlyphLessFont:TextSelectionPainter::endPage:TextPage::drawSelection:poppler_page_render_selection
** Attachment added: "Test file containing glyphless font" https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1849773/+attachment/5313067/+files/test-glyphless.pdf -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to poppler in Ubuntu. https://bugs.launchpad.net/bugs/1849773 Title: /usr/bin/evince:11:strstr:TextSelectionPainter::hasGlyphLessFont:TextSelectionPainter::endPage:TextPage::drawSelection:poppler_page_render_selection Status in poppler package in Ubuntu: Fix Committed Status in poppler source package in Eoan: New Bug description: [Impact] Selecting text in evince crashes for some files in eoan [Test case] Open the pdf in bug 1855596 and select some text. [Regression potential] This adds a check for a null pointer before using the pointer; it's limited to a small function checking if a font is glyphless so there is basically no risk for regressio [Error tracker] The Ubuntu Error Tracker has been receiving reports about a problem regarding evince. This problem was most recently seen with package version 3.34.1-1, the problem page at https://errors.ubuntu.com/problem/da5fffc9beac869c0cf863d931ef170c60bb7d93 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1849773/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1849773] Re: /usr/bin/evince:11:strstr:TextSelectionPainter::hasGlyphLessFont:TextSelectionPainter::endPage:TextPage::drawSelection:poppler_page_render_selection
** Package changed: evince (Ubuntu) => poppler (Ubuntu) ** Changed in: poppler (Ubuntu) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to poppler in Ubuntu. https://bugs.launchpad.net/bugs/1849773 Title: /usr/bin/evince:11:strstr:TextSelectionPainter::hasGlyphLessFont:TextSelectionPainter::endPage:TextPage::drawSelection:poppler_page_render_selection Status in poppler package in Ubuntu: In Progress Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding evince. This problem was most recently seen with package version 3.34.1-1, the problem page at https://errors.ubuntu.com/problem/da5fffc9beac869c0cf863d931ef170c60bb7d93 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. Test Case: 1. Select some text in the document Expected result Text is selected Actual result This crash. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1849773/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1855596] Re: NULL ptr dereference in TextSelectionPainter::hasGlyphLessFont() with certain PDF
*** This bug is a duplicate of bug 1849773 *** https://bugs.launchpad.net/bugs/1849773 This is a duplicate of bug 1849773 ** This bug has been marked a duplicate of bug 1849773 /usr/bin/evince:11:strstr:TextSelectionPainter::hasGlyphLessFont:TextSelectionPainter::endPage:TextPage::drawSelection:poppler_page_render_selection -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to poppler in Ubuntu. https://bugs.launchpad.net/bugs/1855596 Title: NULL ptr dereference in TextSelectionPainter::hasGlyphLessFont() with certain PDF Status in poppler package in Ubuntu: Confirmed Bug description: When viewing a certain PDF (which I unfortunately can't share) using evince, a see a crash in libpoppler90. It's a NULL pointer dereference in TextSelectionPainter::hasGlyphLessFont(), because in this certain PDF, for whatever reason, sel->word->getFontName(0) may return NULL. Attached you'll find a proposed patch increasing the robustness in this case. Cheers, Enrik To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1855596/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1847570] Re: PulseAudio automatically switches to HDMI sound output on login
I just want ahead and upgraded to Focal. Definitely fixed here, thanks! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1847570 Title: PulseAudio automatically switches to HDMI sound output on login Status in PulseAudio: New Status in pulseaudio package in Ubuntu: Fix Released Status in pulseaudio source package in Eoan: Triaged Status in pulseaudio source package in Focal: Fix Released Bug description: On my freshly installed eoan system I have two output devices: - HDMI/DisplayPort 2 - GK208 ... - Line Out - Family 17h ... When I login into the system pulseaudio always select the "wrong" one (HDMI) and I need to go to gnome-settings/Sound/Output Device and switch to "line out". This applies to every login/logout not just reboots. I would be good if it would remember this choice so that I have to do it only once. Or maybe (if that is technically possible) just output on both output devices by default - this would be even more user friendly for newbies who will have a hard time finding the right place to change this (or maybe have UI in the volume slider to select outputs if there are more than one? But anyway, my immediate concern is that it should just remember my choice :) Please let me know if I can provide more information. Happy to dig into code if needed but I will need some pointers. --- WORKAROUND Comment out: load-module module-switch-on-port-available load-module module-switch-on-connect from /etc/pulse/default.pa To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1847570/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1856613] [NEW] apt upgrade wants to install openjdk-11-jre-headless without upgprading anything
Public bug reported: Notable, upon logging in, I get this message: ``` 3 packages can be updated. 1 update is a security update. ``` This is fairly misleading, since afaict, the three packages it's listing as "updated" are in fact "new installs" as opposed to "upgrades". However, that isn't the primary point of my bug report. I'm actually relying on that information via: /usr/lib/update-notifier/apt-check 2>&1|sed -e "s/;.*//" /usr/lib/update-notifier/apt-check 2>&1|sed -e "s/.*;//" So, I connect to the box and perform: `apt upgrade`: ``` Hit:1 http://us-east-2.ec2.archive.ubuntu.com/ubuntu bionic InRelease Hit:2 http://us-east-2.ec2.archive.ubuntu.com/ubuntu bionic-updates InRelease Hit:3 http://us-east-2.ec2.archive.ubuntu.com/ubuntu bionic-backports InRelease Hit:4 http://security.ubuntu.com/ubuntu bionic-security InRelease Ign:5 http://debian.neo4j.org/repo stable/ InRelease Get:6 http://debian.neo4j.org/repo stable/ Release [1479 B] Get:7 http://debian.neo4j.org/repo stable/ Release.gpg [819 B] Hit:8 https://repo.zabbix.com/zabbix/4.0/ubuntu bionic InRelease Fetched 2298 B in 1s (4382 B/s) Reading package lists... Done Building dependency tree Reading state information... Done 1 package can be upgraded. Run 'apt list --upgradable' to see it. Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following NEW packages will be installed: libasound2 libasound2-data openjdk-11-jre-headless The following packages have been kept back: cypher-shell 0 upgraded, 3 newly installed, 0 to remove and 1 not upgraded. Need to get 37.8 MB of archives. After this operation, 173 MB of additional disk space will be used. Do you want to continue? [Y/n] n ``` Apt apparently discovered a newer version of `cypher-shell`. That newer version requires `openjdk-11-jre-headless`, so it added that to the list of things to install. That new package requires two additional packages (`libasound2` and `libasound2-data`). `apt` then discovers that this newer version of `cypher-shell` conflicts w/ a manually installed package (`neo4j`). It thus marks `cypher-shell` as `kept-back`, unfortunately, it doesn't discard its plans to install java11. For comparison, `apt-get upgrade` just recognizes that it shouldn't upgrade `cypher-shell`: `apt-get upgrade`: ``` Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following packages have been kept back: cypher-shell 0 upgraded, 0 newly installed, 0 to remove and 1 not upgraded. ``` ``` lsb_release -rd Description:Ubuntu 18.04.3 LTS Release:18.04 ``` `apt-cache policy apt cypher-shell neo4j openjdk-11-jre-headless:amd64 openjdk-8-jre-headless:amd64`: ``` apt: Installed: 1.6.12 Candidate: 1.6.12 Version table: *** 1.6.12 500 500 http://us-east-2.ec2.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.6.6ubuntu0.1 500 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 1.6.1 500 500 http://us-east-2.ec2.archive.ubuntu.com/ubuntu bionic/main amd64 Packages cypher-shell: Installed: 1.1.12 Candidate: 4.0.0 Version table: 4.0.0 500 500 http://debian.neo4j.org/repo stable/ Packages *** 1.1.12 500 500 http://debian.neo4j.org/repo stable/ Packages 100 /var/lib/dpkg/status ... neo4j: Installed: 1:3.5.13 Candidate: 1:3.5.13 Version table: *** 1:3.5.13 500 500 http://debian.neo4j.org/repo stable/ Packages 100 /var/lib/dpkg/status ... openjdk-11-jre-headless: Installed: (none) Candidate: 11.0.4+11-1ubuntu2~18.04.3 Version table: 11.0.4+11-1ubuntu2~18.04.3 500 500 http://us-east-2.ec2.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 10.0.1+10-3ubuntu1 500 500 http://us-east-2.ec2.archive.ubuntu.com/ubuntu bionic/main amd64 Packages openjdk-8-jre-headless: Installed: 8u222-b10-1ubuntu1~18.04.1 Candidate: 8u222-b10-1ubuntu1~18.04.1 Version table: *** 8u222-b10-1ubuntu1~18.04.1 500 500 http://us-east-2.ec2.archive.ubuntu.com/ubuntu bionic-updates/universe amd64 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/universe amd64 Packages 100 /var/lib/dpkg/status 8u162-b12-1 500 500 http://us-east-2.ec2.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages ``` Expected results: as with `apt-get upgrade`, don't try to install jre11. Actual results: tries to install jre11 (it does succeed if I say yes, but that then breaks some customer software which we manually installed which doesn't like java11 -- that's a separate set of bugs, and they aren't packaged, so there's no guidance to apt telling it not to do that). ** Affects: apt (Ubuntu) Importance:
[Touch-packages] [Bug 1849773] [NEW] /usr/bin/evince:11:strstr:TextSelectionPainter::hasGlyphLessFont:TextSelectionPainter::endPage:TextPage::drawSelection:poppler_page_render_selection
You have been subscribed to a public bug: The Ubuntu Error Tracker has been receiving reports about a problem regarding evince. This problem was most recently seen with package version 3.34.1-1, the problem page at https://errors.ubuntu.com/problem/da5fffc9beac869c0cf863d931ef170c60bb7d93 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. Test Case: 1. Select some text in the document Expected result Text is selected Actual result This crash. ** Affects: poppler (Ubuntu) Importance: High Assignee: Julian Andres Klode (juliank) Status: Confirmed ** Tags: eoan focal lts-desktop-wishlist rls-ff-notfixing -- /usr/bin/evince:11:strstr:TextSelectionPainter::hasGlyphLessFont:TextSelectionPainter::endPage:TextPage::drawSelection:poppler_page_render_selection https://bugs.launchpad.net/bugs/1849773 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to poppler in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 269441] Re: Trash always full
I can confirm that this bug is still in ubuntu-mate (version 19.10). when unmounting external drives without emptying trash, the trash icon stays on "full" forever (until the next login) Expected behaviour would be a re-evaluation of the trash state of the mounted devices after any mount/unmount of any drive This papercut has reached the respectable age of 11 years which, of course, is getting a bit embarrassing. :-) I don't know where the trashcan code hides (somewhere in caja ?) I might try to give it a shot if I knew more. Tips anyone ? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/269441 Title: Trash always full Status in Ubuntu MATE: New Status in glib2.0 package in Ubuntu: Confirmed Bug description: I've seen other users having problems with that the trash appears empty even though it isn't. I have the opposite problem: my trash icon on the desktop always appears full, even if empty. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/269441/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1783881] Re: ltp-syscalls: msgstress03 fails because systemd limits number of processes
This failure occurs in the cloud, on amazon aws, it can be reproduced on c4/c5.large abd c5.metal where it passes on c5n.xlarge / i3.metal m3.large m4.large. I will try the suggested steps above on one of the affected flavor types and see if we can get to the bottom of this. ** Changed in: ubuntu-kernel-tests Assignee: (unassigned) => Sean Feole (sfeole) ** Tags added: sqa -- 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/1783881 Title: ltp-syscalls: msgstress03 fails because systemd limits number of processes Status in ubuntu-kernel-tests: Triaged Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Incomplete Status in linux source package in Xenial: New Status in systemd source package in Xenial: New Status in linux source package in Cosmic: Incomplete Bug description: As systemd limits the number of processes, this test will fail because it can't fork enough processes. That is limited to when the test is run after logging as user 1000, then running sudo. I guess that logging as root may not cause this to happen. # ./testcases/bin/msgstress03 Fork failed (may be OK if under stress) Fork failed (may be OK if under stress) msgstress031 TFAIL : msgstress03.c:157: Fork failed (may be OK if under stress) # To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1783881/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1856460] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1856460/+attachment/5313049/+files/CurrentDmesg.txt -- 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/1856460 Title: [ZenBook UX334FL_UX334FL, Realtek ALC294, Mic, Internal] Microphone doesn't work Status in alsa-driver package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: I have a dual boot system with windows 10. In windows I don't find any problem but on Ubuntu the microphone doesn't seem to work or be recognized. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: pulseaudio 1:13.0-1ubuntu1 Uname: Linux 5.3.16-050316-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nesar 2260 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Dec 15 15:04:59 2019 InstallationDate: Installed on 2019-11-26 (19 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH successful Symptom_Card: Audio interno - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nesar 2260 F pulseaudio Symptom_Jack: Mic, Internal Symptom_PulseAudioRecordingTest: PulseAudio recording test through plughw:PCH failed Symptom_Type: No sound at all Title: [ZenBook UX334FL_UX334FL, Realtek ALC294, Mic, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/16/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX334FL.302 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX334FL 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.:bvrUX334FL.302:bd10/16/2019:svnASUSTeKCOMPUTERINC.:pnZenBookUX334FL_UX334FL:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX334FL:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: ZenBook UX334FL_UX334FL dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nesar 2298 F pulseaudio /dev/snd/pcmC0D0p: nesar 2298 F...m pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-11-26 (20 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash Tags: eoan Uname: Linux 5.3.16-050316-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/16/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX334FL.302 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX334FL 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.:bvrUX334FL.302:bd10/16/2019:svnASUSTeKCOMPUTERINC.:pnZenBookUX334FL_UX334FL:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX334FL:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: ZenBook UX334FL_UX334FL 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/1856460/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1856460] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1856460/+attachment/5313051/+files/PulseList.txt -- 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/1856460 Title: [ZenBook UX334FL_UX334FL, Realtek ALC294, Mic, Internal] Microphone doesn't work Status in alsa-driver package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: I have a dual boot system with windows 10. In windows I don't find any problem but on Ubuntu the microphone doesn't seem to work or be recognized. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: pulseaudio 1:13.0-1ubuntu1 Uname: Linux 5.3.16-050316-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nesar 2260 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Dec 15 15:04:59 2019 InstallationDate: Installed on 2019-11-26 (19 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH successful Symptom_Card: Audio interno - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nesar 2260 F pulseaudio Symptom_Jack: Mic, Internal Symptom_PulseAudioRecordingTest: PulseAudio recording test through plughw:PCH failed Symptom_Type: No sound at all Title: [ZenBook UX334FL_UX334FL, Realtek ALC294, Mic, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/16/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX334FL.302 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX334FL 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.:bvrUX334FL.302:bd10/16/2019:svnASUSTeKCOMPUTERINC.:pnZenBookUX334FL_UX334FL:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX334FL:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: ZenBook UX334FL_UX334FL dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nesar 2298 F pulseaudio /dev/snd/pcmC0D0p: nesar 2298 F...m pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-11-26 (20 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash Tags: eoan Uname: Linux 5.3.16-050316-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/16/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX334FL.302 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX334FL 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.:bvrUX334FL.302:bd10/16/2019:svnASUSTeKCOMPUTERINC.:pnZenBookUX334FL_UX334FL:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX334FL:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: ZenBook UX334FL_UX334FL 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/1856460/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1856460] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1856460/+attachment/5313050/+files/ProcCpuinfoMinimal.txt -- 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/1856460 Title: [ZenBook UX334FL_UX334FL, Realtek ALC294, Mic, Internal] Microphone doesn't work Status in alsa-driver package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: I have a dual boot system with windows 10. In windows I don't find any problem but on Ubuntu the microphone doesn't seem to work or be recognized. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: pulseaudio 1:13.0-1ubuntu1 Uname: Linux 5.3.16-050316-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nesar 2260 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Dec 15 15:04:59 2019 InstallationDate: Installed on 2019-11-26 (19 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH successful Symptom_Card: Audio interno - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nesar 2260 F pulseaudio Symptom_Jack: Mic, Internal Symptom_PulseAudioRecordingTest: PulseAudio recording test through plughw:PCH failed Symptom_Type: No sound at all Title: [ZenBook UX334FL_UX334FL, Realtek ALC294, Mic, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/16/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX334FL.302 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX334FL 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.:bvrUX334FL.302:bd10/16/2019:svnASUSTeKCOMPUTERINC.:pnZenBookUX334FL_UX334FL:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX334FL:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: ZenBook UX334FL_UX334FL dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nesar 2298 F pulseaudio /dev/snd/pcmC0D0p: nesar 2298 F...m pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-11-26 (20 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash Tags: eoan Uname: Linux 5.3.16-050316-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/16/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX334FL.302 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX334FL 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.:bvrUX334FL.302:bd10/16/2019:svnASUSTeKCOMPUTERINC.:pnZenBookUX334FL_UX334FL:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX334FL:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: ZenBook UX334FL_UX334FL 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/1856460/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1850932] Re: [SRU] Backport 2.62.3-2
glib2.0/i386 was pretty consistently failing for me. It looks like the new version in unstable is better (https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-eoan-laney- ppa/eoan/i386/g/glib2.0/20191216_173854_41ef9@/log.gz), so I'm uploading that as a new backport to replace the SRU currently in eoan-proposed. ** Description changed: [ Description ] I'm creating this bug report to have a place to describe the proposed - backport of glib2.0 2.62.2-2 from focal. + backport of glib2.0 2.62.3-2 from focal. - The main purpose of this backport (as opposed to -1) is to fix bug - #1844853. + One purpose of this backport is to fix bug #1844853. - But there are several other changes. There are many cherry-picks to - improve the testsuite's reliability. At the time of upload they weren't - in the stable branch, but now they almost all are. These commits can be - considered to be tested under - https://wiki.ubuntu.com/StableReleaseUpdates/GNOME + But there are several other changes. Here's the diff of NEWS: - The two that are not are: + +Overview of changes in GLib 2.62.3 + +== + + + +* Use `poll()` in `g_spawn_sync()` rather than `select()`, which is subject to + + FD limits (#954) + + + +* Fix undefined behaviour with `g_utf8_find_prev_char()` (#1917) + + + +* Bugs fixed: + + - #954 The g_spawn_sync() function uses select() which has limitations + + - #1318 rare failure in gdbus-peer test: invalid uninstantiatable type '(null)' in cast to 'GDBusServer' + + - #1897 glib 2.62.0 fails test 'test_writev_no_vectors' wih gcc7 + + - #1903 use-after-free in mimeapps test causes intermittent segfault during testing + + - #1916 objcopy not used from cross-compilation file in GIO tests + + - #1917 Test utf8-pointer fails with static build, LTO, optimisations, and new GCC + + - !1174 Backport !1164 “use-after-free fix in mimeapps test” to glib-2-62 + + - !1184 Backport !1173 “gvariant: Limit recursion in g_variant_parse()” to glib-2-62 + + - !1194 Backport !1176, !1183, !1188, !1191 to `glib-2-62` + + - !1203 Backport !1192, !1193, !1197 Fixes for gdbus-peer tests to glib-2-62 + + - !1207 Backport !1206 “goption: Relax assertion to avoid being broken by kdeinit5” to glib-2-62 + + - !1215 [2.62] gdbus-peer: Specifically listen on 127.0.0.1 + + - !1219 Backport !1218 “gdb: Fix GHashTable pretty printer off-by-one error” + + - !1222 Backport !1221 “Add NOTE_REVOKE to the list of the monitoring events” to glib-2-62 + + - !1228 Backport !1199 “gunicode: Fix UB in gutf8.c and utf8-pointer test” to glib-2-62 + + + + + +Overview of changes in GLib 2.62.2 + +== + + + +* Bugs fixed: + + - #1896 Use after free when calling g_dbus_connection_flush_sync() in a dedicated thread + + - !1154 Backport !1152 “gwinhttpvfs: Handle g_get_prgname() returning NULL” to glib-2-62 + + - !1156 Backport !1146 Solaris fixes to glib-2-62 - commit 2b1e706b2f0007982f4fe6a70734d4490e4093a3 - Author: Simon McVittie - Date: Tue Oct 29 16:27:53 2019 + - gdbus-server-auth test: Create temporary directory for Unix socket - - This avoids failure to listen on the given address on non-Linux Unix - kernels, where abstract sockets do not exist and so unix:tmpdir is - equivalent to unix:dir. - - To avoid bugs like this one recurring, run most of these tests using - the unix:dir address type, where Linux is equivalent to other Unix - kernels; just do one unix:tmpdir test, to check that we still - interoperate with libdbus when using abstract sockets on Linux. - - Resolves: GNOME/glib#1920 - Fixes: 9f962ebe "Add a test for GDBusServer authentication" - Signed-off-by: Simon McVittie + This release can be considered to be tested under https://wiki.ubuntu.com/StableReleaseUpdates/GNOME - commit 9f962ebeac1d67223579ad0d261c4c8215f7c427 - Author: Simon McVittie - Date: Fri Oct 11 19:02:55 2019 +0100 + There are patches from the upstream master branch rather than this + stable release: - Add a test for GDBusServer authentication - - In particular, if libbdus is available, we test interoperability with - a libdbus client: see GNOME/glib#1831. Because that issue describes a - race condition, we do each test repeatedly to try to hit the failing - case. - - Signed-off-by: Simon McVittie + + Add-a-test-for-GDBusServer-authentication.patch + + gdbus-server-auth-test-Create-temporary-directory-for-Uni.patch + + gdbus-server-auth-test-Include-gcredentialsprivate.h.patch + + Make-ld-executable-configurable.patch - which are both testsuite fixes. There are some additional non-upstream - changes: - -* d/p/debian/mimeapps-test-Mark-as-flaky.patch: - Drop patch, hopefully no longer needed with #941550 fixed -* d/p/debian/taptestrunner-Stop-looking-like-an-executable-script.patch: - Make taptestrunner
[Touch-packages] [Bug 1856460] AlsaInfo.txt
apport information ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1856460/+attachment/5313048/+files/AlsaInfo.txt -- 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/1856460 Title: [ZenBook UX334FL_UX334FL, Realtek ALC294, Mic, Internal] Microphone doesn't work Status in alsa-driver package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: I have a dual boot system with windows 10. In windows I don't find any problem but on Ubuntu the microphone doesn't seem to work or be recognized. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: pulseaudio 1:13.0-1ubuntu1 Uname: Linux 5.3.16-050316-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nesar 2260 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Dec 15 15:04:59 2019 InstallationDate: Installed on 2019-11-26 (19 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH successful Symptom_Card: Audio interno - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nesar 2260 F pulseaudio Symptom_Jack: Mic, Internal Symptom_PulseAudioRecordingTest: PulseAudio recording test through plughw:PCH failed Symptom_Type: No sound at all Title: [ZenBook UX334FL_UX334FL, Realtek ALC294, Mic, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/16/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX334FL.302 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX334FL 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.:bvrUX334FL.302:bd10/16/2019:svnASUSTeKCOMPUTERINC.:pnZenBookUX334FL_UX334FL:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX334FL:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: ZenBook UX334FL_UX334FL dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nesar 2298 F pulseaudio /dev/snd/pcmC0D0p: nesar 2298 F...m pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-11-26 (20 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash Tags: eoan Uname: Linux 5.3.16-050316-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/16/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX334FL.302 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX334FL 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.:bvrUX334FL.302:bd10/16/2019:svnASUSTeKCOMPUTERINC.:pnZenBookUX334FL_UX334FL:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX334FL:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: ZenBook UX334FL_UX334FL 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/1856460/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1850932] Re: [SRU] Backport 2.62.3-2
** Summary changed: - [SRU] Backport 2.62.2-2 + [SRU] Backport 2.62.3-2 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1850932 Title: [SRU] Backport 2.62.3-2 Status in glib2.0 package in Ubuntu: Fix Released Status in glib2.0 source package in Eoan: Fix Committed Bug description: [ Description ] I'm creating this bug report to have a place to describe the proposed backport of glib2.0 2.62.3-2 from focal. One purpose of this backport is to fix bug #1844853. But there are several other changes. Here's the diff of NEWS: +Overview of changes in GLib 2.62.3 +== + +* Use `poll()` in `g_spawn_sync()` rather than `select()`, which is subject to + FD limits (#954) + +* Fix undefined behaviour with `g_utf8_find_prev_char()` (#1917) + +* Bugs fixed: + - #954 The g_spawn_sync() function uses select() which has limitations + - #1318 rare failure in gdbus-peer test: invalid uninstantiatable type '(null)' in cast to 'GDBusServer' + - #1897 glib 2.62.0 fails test 'test_writev_no_vectors' wih gcc7 + - #1903 use-after-free in mimeapps test causes intermittent segfault during testing + - #1916 objcopy not used from cross-compilation file in GIO tests + - #1917 Test utf8-pointer fails with static build, LTO, optimisations, and new GCC + - !1174 Backport !1164 “use-after-free fix in mimeapps test” to glib-2-62 + - !1184 Backport !1173 “gvariant: Limit recursion in g_variant_parse()” to glib-2-62 + - !1194 Backport !1176, !1183, !1188, !1191 to `glib-2-62` + - !1203 Backport !1192, !1193, !1197 Fixes for gdbus-peer tests to glib-2-62 + - !1207 Backport !1206 “goption: Relax assertion to avoid being broken by kdeinit5” to glib-2-62 + - !1215 [2.62] gdbus-peer: Specifically listen on 127.0.0.1 + - !1219 Backport !1218 “gdb: Fix GHashTable pretty printer off-by-one error” + - !1222 Backport !1221 “Add NOTE_REVOKE to the list of the monitoring events” to glib-2-62 + - !1228 Backport !1199 “gunicode: Fix UB in gutf8.c and utf8-pointer test” to glib-2-62 + + +Overview of changes in GLib 2.62.2 +== + +* Bugs fixed: + - #1896 Use after free when calling g_dbus_connection_flush_sync() in a dedicated thread + - !1154 Backport !1152 “gwinhttpvfs: Handle g_get_prgname() returning NULL” to glib-2-62 + - !1156 Backport !1146 Solaris fixes to glib-2-62 This release can be considered to be tested under https://wiki.ubuntu.com/StableReleaseUpdates/GNOME There are patches from the upstream master branch rather than this stable release: + Add-a-test-for-GDBusServer-authentication.patch + gdbus-server-auth-test-Create-temporary-directory-for-Uni.patch + gdbus-server-auth-test-Include-gcredentialsprivate.h.patch + Make-ld-executable-configurable.patch They are sensible backports which I hope are appropriate for SRU. [ QA ] The testsuite fixes will verify themselves during the build and autopkgtest. For the rest of the fixes, please exercise the desktop thoroughly. Log in, log out, run many applications and make sure there are no regressions. [ Regression potential ] test fixes> Build failures or autopkgtest failures. GLib is a central desktop library. Regressions could break any part of the desktop - so QA is important, the SRU exception notwithstanding. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1850932/+subscriptions -- Mailing list: https://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 1856460] Re: [ZenBook UX334FL_UX334FL, Realtek ALC294, Mic, Internal] Microphone doesn't work
Hi Hui, the problem is regarding the internal mic. I've tried different versions of kernel, reloaded the alsa drivers but nothing to do.. This afternnon I tried to remove the nvidia driver and reinstall the 5.3.16 kernel and now it works fine. Regards. Il giorno lun 16 dic 2019 alle ore 08:21 Hui Wang ha scritto: > "the microphone doesn't seem to work or be recognized", do you mean the > internal mic? it is not recognized? I checked the log in the #1, the > internal mic is defined, you should be able to see/find the internal mic > from the gnome-control-center sound-setting. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1856460 > > Title: > [ZenBook UX334FL_UX334FL, Realtek ALC294, Mic, Internal] Microphone > doesn't work > > Status in alsa-driver package in Ubuntu: > New > Status in linux package in Ubuntu: > Incomplete > > Bug description: > I have a dual boot system with windows 10. > In windows I don't find any problem but on Ubuntu the microphone doesn't > seem to work or be recognized. > > ProblemType: Bug > DistroRelease: Ubuntu 19.10 > Package: pulseaudio 1:13.0-1ubuntu1 > Uname: Linux 5.3.16-050316-generic x86_64 > ApportVersion: 2.20.11-0ubuntu8.2 > Architecture: amd64 > AudioDevicesInUse: >USERPID ACCESS COMMAND >/dev/snd/controlC0: nesar 2260 F pulseaudio > CurrentDesktop: ubuntu:GNOME > Date: Sun Dec 15 15:04:59 2019 > InstallationDate: Installed on 2019-11-26 (19 days ago) > InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) > ProcEnviron: >PATH=(custom, no user) >XDG_RUNTIME_DIR= >LANG=it_IT.UTF-8 >SHELL=/bin/bash > SourcePackage: pulseaudio > Symptom: audio > Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH > successful > Symptom_Card: Audio interno - HDA Intel PCH > Symptom_DevicesInUse: >USERPID ACCESS COMMAND >/dev/snd/controlC0: nesar 2260 F pulseaudio > Symptom_Jack: Mic, Internal > Symptom_PulseAudioRecordingTest: PulseAudio recording test through > plughw:PCH failed > Symptom_Type: No sound at all > Title: [ZenBook UX334FL_UX334FL, Realtek ALC294, Mic, Internal] No sound > at all > UpgradeStatus: No upgrade log present (probably fresh install) > dmi.bios.date: 10/16/2019 > dmi.bios.vendor: American Megatrends Inc. > dmi.bios.version: UX334FL.302 > dmi.board.asset.tag: ATN12345678901234567 > dmi.board.name: UX334FL > 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.:bvrUX334FL.302:bd10/16/2019:svnASUSTeKCOMPUTERINC.:pnZenBookUX334FL_UX334FL:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX334FL:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: > dmi.product.family: ZenBook > dmi.product.name: ZenBook UX334FL_UX334FL > 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/1856460/+subscriptions > ** Tags added: apport-collected ** Description changed: I have a dual boot system with windows 10. In windows I don't find any problem but on Ubuntu the microphone doesn't seem to work or be recognized. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: pulseaudio 1:13.0-1ubuntu1 Uname: Linux 5.3.16-050316-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nesar 2260 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Dec 15 15:04:59 2019 InstallationDate: Installed on 2019-11-26 (19 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH successful Symptom_Card: Audio interno - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nesar 2260 F pulseaudio Symptom_Jack: Mic, Internal Symptom_PulseAudioRecordingTest: PulseAudio recording test through plughw:PCH failed Symptom_Type: No sound at all Title: [ZenBook UX334FL_UX334FL, Realtek ALC294, Mic, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/16/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX334FL.302 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX334FL 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.
Re: [Touch-packages] [Bug 1856592] Re: modified graphic of progrwms
I thank you a lot for your answer AFTER :journalctl -b 0 the following lines repeated a lot of times!!! -- Logs begin at Δευ 2019-12-16 17:31:07 EET, end at Δευ 2019-12-16 19:27:48 EET. -- Δεκ 16 17:31:07 f-Lenovo-G50-30 systemd-journald[246]: Runtime journal (/run/log/journal/) is 8.0M, m Δεκ 16 17:31:07 f-Lenovo-G50-30 kernel: microcode: microcode updated early to revision 0x838, date = Δεκ 16 17:31:07 f-Lenovo-G50-30 kernel: Linux version 4.15.0-72-generic (buildd@lcy01-amd64-023) (gcc Δεκ 16 17:31:07 f-Lenovo-G50-30 kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-4.15.0-72-generic root Δεκ 16 17:31:07 f-Lenovo-G50-30 kernel: KERNEL supported cpus: Δεκ 16 17:31:07 f-Lenovo-G50-30 kernel: Intel GenuineIntel Δεκ 16 17:31:07 f-Lenovo-G50-30 kernel: AMD AuthenticAMD Δεκ 16 17:31:07 f-Lenovo-G50-30 kernel: Centaur CentaurHauls Δεκ 16 17:31:07 f-Lenovo-G50-30 kernel: x86/fpu: x87 FPU will use FXSAVE Δεκ 16 17:31:07 f-Lenovo-G50-30 kernel: e820: BIOS-provided physical RAM map: Δεκ 16 17:31:07 f-Lenovo-G50-30 kernel: BIOS-e820: [mem 0x-0x0006efff] usable Δεκ 16 17:31:07 f-Lenovo-G50-30 kernel: BIOS-e820: [mem 0x0006f000-0x0006] ACPI N Δεκ 16 17:31:07 f-Lenovo-G50-30 kernel: BIOS-e820: [mem 0x0007-0x00085fff] usable Δεκ 16 17:31:07 f-Lenovo-G50-30 kernel: BIOS-e820: [mem 0x00086000-0x0009] reserv Δεκ 16 17:31:07 f-Lenovo-G50-30 kernel: BIOS-e820: [mem 0x0010-0x1fff] usable Δεκ 16 17:31:07 f-Lenovo-G50-30 kernel: BIOS-e820: [mem 0x2000-0x200f] reserv Δεκ 16 17:31:07 f-Lenovo-G50-30 kernel: BIOS-e820: [mem 0x2010-0x78235fff] usable Δεκ 16 17:31:07 f-Lenovo-G50-30 kernel: BIOS-e820: [mem 0x78236000-0x784b4fff] reserv Δεκ 16 17:31:07 f-Lenovo-G50-30 kernel: BIOS-e820: [mem 0x784b5000-0x78544fff] type 2 Δεκ 16 17:31:07 f-Lenovo-G50-30 kernel: BIOS-e820: [mem 0x78545000-0x78b44fff] reserv Δεκ 16 17:31:07 f-Lenovo-G50-30 kernel: BIOS-e820: [mem 0x78b45000-0x78c44fff] ACPI N Δεκ 16 17:31:07 f-Lenovo-G50-30 kernel: BIOS-e820: [mem 0x78c45000-0x78c84fff] ACPI d lines 1-23 AFTER: gsettings get org.gnome.desktop.interface icon-theme 'ubuntu-mono-dark' AFTER : dpkg -l | grep icon ii adwaita-icon-theme 3.18.0+p16.04+git20170914.0754 all dummy package to replace default icon theme of GNOME ii hicolor-icon-theme 0.15-0ubuntu1.1 all default fallback theme for FreeDesktop.org icon themes ii humanity-icon-theme 0.6.10.1 all Humanity Icon theme ii libtext-iconv-perl 1.7-5build4 amd64 converts between character sets in Perl ii notify-osd-icons 0.8+15.10.20151016.2-0ubuntu1 all Notify-OSD icons ii suru-icon-theme 14.04+16.04.20180326-0ubuntu1 all Ubuntu Suru Icon theme ii ubuntu-mobile-icons 14.04+16.04.20180326-0ubuntu1 all Ubuntu Mobile Icon theme f@f-Lenovo-G50-30:~$ That's all thank you again -- 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/1856592 Title: modified graphic of progrwms Status in gtk+3.0 package in Ubuntu: Incomplete Bug description: in some programs th little icons that allow to undo or redo or the icons that allow to go up or down appear like some little squares! I don't know how can I solve this problem! ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-72.81~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-72-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.21 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 Date: Mon Dec 16 17:40:38 2019 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display [8086:0f31] (rev 0e) (prog-if 00 [VGA controller]) Subsystem: Lenovo Atom Processor Z36xxx/Z37xxx Series Graphics & Display [17aa:3905] InstallationDate: Installed on 2019-12-07 (8 days ago) InstallationMedia: Ubuntu 16.04.6 LTS "Xenial Xerus" - Release amd64 (20190227) MachineType: LENOVO 80G0 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-72-generic root=UUID=42ddfb90-969c-4976-998c-893d136068bb ro splash quiet pci=nomsi RESUME=UUID=92781adb-f2a6-4f15-88fc-e1ce801291dd vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/22/2015 dmi.bios.vendor: LENOVO dmi.bios.version: A7CN45WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Lancer 5A6 dmi.board.vendor: LENOVO dmi.board.version: NANANANANO
[Touch-packages] [Bug 1855596] Re: NULL ptr dereference in TextSelectionPainter::hasGlyphLessFont() with certain PDF
Bug was introduced by LP #1830473 (Does not handle glyphless fonts, as used by tesseract) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to poppler in Ubuntu. https://bugs.launchpad.net/bugs/1855596 Title: NULL ptr dereference in TextSelectionPainter::hasGlyphLessFont() with certain PDF Status in poppler package in Ubuntu: Confirmed Bug description: When viewing a certain PDF (which I unfortunately can't share) using evince, a see a crash in libpoppler90. It's a NULL pointer dereference in TextSelectionPainter::hasGlyphLessFont(), because in this certain PDF, for whatever reason, sel->word->getFontName(0) may return NULL. Attached you'll find a proposed patch increasing the robustness in this case. Cheers, Enrik To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1855596/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1853661] Re: systemd-timesyncd.server failed with exit code 3
This is actually likely due to a badly written memory card. ** Changed in: systemd (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1853661 Title: systemd-timesyncd.server failed with exit code 3 Status in systemd package in Ubuntu: Invalid Bug description: This happened on a Raspberry Pi 4 on which I had installed the arm64 image from http://cdimage.ubuntu.com/ubuntu-server/eoan/daily- preinstalled/20191122/. Its worth noting I also encountered a crash with cloud-init, bug 1853660, so maybe everything wasn't set up properly. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: systemd 242-7ubuntu3.2 ProcVersionSignature: User Name 5.3.0-1013.15-raspi2 5.3.10 Uname: Linux 5.3.0-1013-raspi2 aarch64 ApportVersion: 2.20.11-0ubuntu8.3 Architecture: arm64 Date: Thu Apr 11 17:08:55 2019 ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=1 cma=64M bcm2708_fb.fbwidth=1824 bcm2708_fb.fbheight=984 bcm2708_fb.fbswap=1 smsc95xx.macaddr=DC:A6:32:37:37:07 vc_mem.mem_base=0x3ec0 vc_mem.mem_size=0x4000 net.ifnames=0 dwc_otg.lpm_enable=0 console=ttyS0,115200 console=tty1 root=LABEL=writable rootfstype=ext4 elevator=deadline rootwait quiet splash SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1853661/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1856592] Re: modified graphic of progrwms
Thank you for your bug report, could you attach the output of those commands to the bug? $ journalctl -b 0 $ gsettings get org.gnome.desktop.interface icon-theme $ dpkg -l | grep icon ** Package changed: xorg (Ubuntu) => gtk+3.0 (Ubuntu) ** Changed in: gtk+3.0 (Ubuntu) Status: New => Incomplete -- 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/1856592 Title: modified graphic of progrwms Status in gtk+3.0 package in Ubuntu: Incomplete Bug description: in some programs th little icons that allow to undo or redo or the icons that allow to go up or down appear like some little squares! I don't know how can I solve this problem! ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-72.81~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-72-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.21 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 Date: Mon Dec 16 17:40:38 2019 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display [8086:0f31] (rev 0e) (prog-if 00 [VGA controller]) Subsystem: Lenovo Atom Processor Z36xxx/Z37xxx Series Graphics & Display [17aa:3905] InstallationDate: Installed on 2019-12-07 (8 days ago) InstallationMedia: Ubuntu 16.04.6 LTS "Xenial Xerus" - Release amd64 (20190227) MachineType: LENOVO 80G0 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-72-generic root=UUID=42ddfb90-969c-4976-998c-893d136068bb ro splash quiet pci=nomsi RESUME=UUID=92781adb-f2a6-4f15-88fc-e1ce801291dd vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/22/2015 dmi.bios.vendor: LENOVO dmi.bios.version: A7CN45WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Lancer 5A6 dmi.board.vendor: LENOVO dmi.board.version: NANANANANO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo G50-30 dmi.modalias: dmi:bvnLENOVO:bvrA7CN45WW:bd01/22/2015:svnLENOVO:pn80G0:pvrLenovoG50-30:rvnLENOVO:rnLancer5A6:rvrNANANANANODPK:cvnLENOVO:ct10:cvrLenovoG50-30: dmi.product.family: IDEAPAD dmi.product.name: 80G0 dmi.product.version: Lenovo G50-30 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.91-2~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Mon Dec 16 17:31:25 2019 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu4.1~16.04.2 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1856592/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1856592] Re: modified graphic of progrwms
I tried many times to find help in internet but maybe I am not abe to explain the real problem I have! -- 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/1856592 Title: modified graphic of progrwms Status in xorg package in Ubuntu: New Bug description: in some programs th little icons that allow to undo or redo or the icons that allow to go up or down appear like some little squares! I don't know how can I solve this problem! ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-72.81~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-72-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.21 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 Date: Mon Dec 16 17:40:38 2019 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display [8086:0f31] (rev 0e) (prog-if 00 [VGA controller]) Subsystem: Lenovo Atom Processor Z36xxx/Z37xxx Series Graphics & Display [17aa:3905] InstallationDate: Installed on 2019-12-07 (8 days ago) InstallationMedia: Ubuntu 16.04.6 LTS "Xenial Xerus" - Release amd64 (20190227) MachineType: LENOVO 80G0 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-72-generic root=UUID=42ddfb90-969c-4976-998c-893d136068bb ro splash quiet pci=nomsi RESUME=UUID=92781adb-f2a6-4f15-88fc-e1ce801291dd vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/22/2015 dmi.bios.vendor: LENOVO dmi.bios.version: A7CN45WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Lancer 5A6 dmi.board.vendor: LENOVO dmi.board.version: NANANANANO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo G50-30 dmi.modalias: dmi:bvnLENOVO:bvrA7CN45WW:bd01/22/2015:svnLENOVO:pn80G0:pvrLenovoG50-30:rvnLENOVO:rnLancer5A6:rvrNANANANANODPK:cvnLENOVO:ct10:cvrLenovoG50-30: dmi.product.family: IDEAPAD dmi.product.name: 80G0 dmi.product.version: Lenovo G50-30 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.91-2~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Mon Dec 16 17:31:25 2019 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu4.1~16.04.2 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1856592/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1856592] Re: modified graphic of progrwms
** Attachment added: "Screenshot from 2019-12-16 17-53-22.png" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1856592/+attachment/5313011/+files/Screenshot%20from%202019-12-16%2017-53-22.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/1856592 Title: modified graphic of progrwms Status in xorg package in Ubuntu: New Bug description: in some programs th little icons that allow to undo or redo or the icons that allow to go up or down appear like some little squares! I don't know how can I solve this problem! ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-72.81~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-72-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.21 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 Date: Mon Dec 16 17:40:38 2019 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display [8086:0f31] (rev 0e) (prog-if 00 [VGA controller]) Subsystem: Lenovo Atom Processor Z36xxx/Z37xxx Series Graphics & Display [17aa:3905] InstallationDate: Installed on 2019-12-07 (8 days ago) InstallationMedia: Ubuntu 16.04.6 LTS "Xenial Xerus" - Release amd64 (20190227) MachineType: LENOVO 80G0 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-72-generic root=UUID=42ddfb90-969c-4976-998c-893d136068bb ro splash quiet pci=nomsi RESUME=UUID=92781adb-f2a6-4f15-88fc-e1ce801291dd vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/22/2015 dmi.bios.vendor: LENOVO dmi.bios.version: A7CN45WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Lancer 5A6 dmi.board.vendor: LENOVO dmi.board.version: NANANANANO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo G50-30 dmi.modalias: dmi:bvnLENOVO:bvrA7CN45WW:bd01/22/2015:svnLENOVO:pn80G0:pvrLenovoG50-30:rvnLENOVO:rnLancer5A6:rvrNANANANANODPK:cvnLENOVO:ct10:cvrLenovoG50-30: dmi.product.family: IDEAPAD dmi.product.name: 80G0 dmi.product.version: Lenovo G50-30 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.91-2~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Mon Dec 16 17:31:25 2019 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu4.1~16.04.2 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1856592/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1856592] Re: modified graphic of progrwms
I hope in your help! -- 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/1856592 Title: modified graphic of progrwms Status in xorg package in Ubuntu: New Bug description: in some programs th little icons that allow to undo or redo or the icons that allow to go up or down appear like some little squares! I don't know how can I solve this problem! ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-72.81~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-72-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.21 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 Date: Mon Dec 16 17:40:38 2019 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display [8086:0f31] (rev 0e) (prog-if 00 [VGA controller]) Subsystem: Lenovo Atom Processor Z36xxx/Z37xxx Series Graphics & Display [17aa:3905] InstallationDate: Installed on 2019-12-07 (8 days ago) InstallationMedia: Ubuntu 16.04.6 LTS "Xenial Xerus" - Release amd64 (20190227) MachineType: LENOVO 80G0 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-72-generic root=UUID=42ddfb90-969c-4976-998c-893d136068bb ro splash quiet pci=nomsi RESUME=UUID=92781adb-f2a6-4f15-88fc-e1ce801291dd vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/22/2015 dmi.bios.vendor: LENOVO dmi.bios.version: A7CN45WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Lancer 5A6 dmi.board.vendor: LENOVO dmi.board.version: NANANANANO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo G50-30 dmi.modalias: dmi:bvnLENOVO:bvrA7CN45WW:bd01/22/2015:svnLENOVO:pn80G0:pvrLenovoG50-30:rvnLENOVO:rnLancer5A6:rvrNANANANANODPK:cvnLENOVO:ct10:cvrLenovoG50-30: dmi.product.family: IDEAPAD dmi.product.name: 80G0 dmi.product.version: Lenovo G50-30 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.91-2~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Mon Dec 16 17:31:25 2019 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu4.1~16.04.2 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1856592/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1856592] [NEW] modified graphic of progrwms
Public bug reported: in some programs th little icons that allow to undo or redo or the icons that allow to go up or down appear like some little squares! I don't know how can I solve this problem! ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-72.81~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-72-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.21 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 Date: Mon Dec 16 17:40:38 2019 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display [8086:0f31] (rev 0e) (prog-if 00 [VGA controller]) Subsystem: Lenovo Atom Processor Z36xxx/Z37xxx Series Graphics & Display [17aa:3905] InstallationDate: Installed on 2019-12-07 (8 days ago) InstallationMedia: Ubuntu 16.04.6 LTS "Xenial Xerus" - Release amd64 (20190227) MachineType: LENOVO 80G0 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-72-generic root=UUID=42ddfb90-969c-4976-998c-893d136068bb ro splash quiet pci=nomsi RESUME=UUID=92781adb-f2a6-4f15-88fc-e1ce801291dd vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/22/2015 dmi.bios.vendor: LENOVO dmi.bios.version: A7CN45WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Lancer 5A6 dmi.board.vendor: LENOVO dmi.board.version: NANANANANO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo G50-30 dmi.modalias: dmi:bvnLENOVO:bvrA7CN45WW:bd01/22/2015:svnLENOVO:pn80G0:pvrLenovoG50-30:rvnLENOVO:rnLancer5A6:rvrNANANANANODPK:cvnLENOVO:ct10:cvrLenovoG50-30: dmi.product.family: IDEAPAD dmi.product.name: 80G0 dmi.product.version: Lenovo G50-30 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.91-2~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Mon Dec 16 17:31:25 2019 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu4.1~16.04.2 xserver.video_driver: modeset ** 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/1856592 Title: modified graphic of progrwms Status in xorg package in Ubuntu: New Bug description: in some programs th little icons that allow to undo or redo or the icons that allow to go up or down appear like some little squares! I don't know how can I solve this problem! ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-72.81~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-72-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.21 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 Date: Mon Dec 16 17:40:38 2019 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display [8086:0f31] (rev 0e) (prog-if 00 [VGA controller]) Subsystem: Lenovo Atom Processor Z36xxx/Z37xxx Series Graphics & Display [17aa:3905] InstallationDate: Installed on 2019-12-07 (8 days ago) InstallationMedia: Ubuntu 16.04.6 LTS "Xenial Xerus" - Release amd64 (20190227) MachineType: LENOVO 80G0 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-72-generic root=UUID=42ddfb90-969c-4976-998c-893d136068bb ro splash quiet pci=nomsi RESUME=UUID=92781adb-f2a6-4f15-88fc-e1ce801291dd vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/22/2015 dmi.bios.vendor: LENOVO dmi.bios.version: A7CN45WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Lancer 5A6 dmi.board.vendor: LENOVO dmi.board.version: NANANANANO DPK dmi.chassis.asset.tag: NO
[Touch-packages] [Bug 1783881] Re: ltp-syscalls: msgstress03 fails because systemd limits number of processes
** Tags added: sru-20191202 ** Tags added: s390x -- 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/1783881 Title: ltp-syscalls: msgstress03 fails because systemd limits number of processes Status in ubuntu-kernel-tests: Triaged Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Incomplete Status in linux source package in Xenial: New Status in systemd source package in Xenial: New Status in linux source package in Cosmic: Incomplete Bug description: As systemd limits the number of processes, this test will fail because it can't fork enough processes. That is limited to when the test is run after logging as user 1000, then running sudo. I guess that logging as root may not cause this to happen. # ./testcases/bin/msgstress03 Fork failed (may be OK if under stress) Fork failed (may be OK if under stress) msgstress031 TFAIL : msgstress03.c:157: Fork failed (may be OK if under stress) # To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1783881/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1855549] Re: ubuntu-wsl: Please recommend show-motd
** Description changed: [ Impact ] * Desktop users of WSL are 'dropped into' the Ubuntu shell instead of logging in to the WSL container, thus they don't see MOTD. Then don't get information about the system's state via desktop notifications either, because the default Ubuntu WSL system does not start the Ubuntu desktop. * To show important system information to users being dropped to a shell directly the show-motd package was created to show MOTD using a /etc/profile.d script. * To have this script in place ubuntu-wsl needs to recommend show-motd. [ Test Case ] * Use 'apt-cache show ubuntu-wsl' to check if ubuntu-wsl recommends update-motd. [ Regression Potential ] * Pulling in a /etc/profile.d script that exits can make the started shell exit immediately. For this reason the shell does not exit in any case. The script can also throw confusing errors. To avoid such errors the script is tested in an autopkgtest and many related packages were fixed where errors were observed. The update-motd package adds Breaks: against related package versions which are known to show errors in MOTD when being run as a regular user. See LP: #1855271 for more details. [ Other Info ] - * The SRU upload to Eoan waits for the acceptance of update-motd to - Eoan and also for the seed merge. + * The update-motd SRU needs to be accepted before this ubuntu-meta SRU because show-motd is a new binary package of update-motd. + * The SRU upload to Eoan waits for the acceptance of update-motd to Eoan and also for the seed merge. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1855549 Title: ubuntu-wsl: Please recommend show-motd Status in ubuntu-meta package in Ubuntu: Fix Released Status in ubuntu-meta source package in Eoan: Fix Committed Bug description: [ Impact ] * Desktop users of WSL are 'dropped into' the Ubuntu shell instead of logging in to the WSL container, thus they don't see MOTD. Then don't get information about the system's state via desktop notifications either, because the default Ubuntu WSL system does not start the Ubuntu desktop. * To show important system information to users being dropped to a shell directly the show-motd package was created to show MOTD using a /etc/profile.d script. * To have this script in place ubuntu-wsl needs to recommend show-motd. [ Test Case ] * Use 'apt-cache show ubuntu-wsl' to check if ubuntu-wsl recommends update-motd. [ Regression Potential ] * Pulling in a /etc/profile.d script that exits can make the started shell exit immediately. For this reason the shell does not exit in any case. The script can also throw confusing errors. To avoid such errors the script is tested in an autopkgtest and many related packages were fixed where errors were observed. The update-motd package adds Breaks: against related package versions which are known to show errors in MOTD when being run as a regular user. See LP: #1855271 for more details. [ Other Info ] * The update-motd SRU needs to be accepted before this ubuntu-meta SRU because show-motd is a new binary package of update-motd. * The SRU upload to Eoan waits for the acceptance of update-motd to Eoan and also for the seed merge. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1855549/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1855092] Re: [SRU] Please set MOTD_SHOWN=pam when MOTD was shown
root@ee-motd-verify:~# login ubuntu Password: Welcome to Ubuntu 19.10 (GNU/Linux 5.0.0-37-generic x86_64) * Documentation: https://help.ubuntu.com * Management: https://landscape.canonical.com * Support:https://ubuntu.com/advantage System information as of Mon Dec 16 14:37:28 UTC 2019 System load:0.7 Processes: 28 Usage of /home: unknown Users logged in: 0 Memory usage: 0%IP address for eth0: 10.84.73.58 Swap usage: 38% 0 updates can be installed immediately. 0 of these updates are security updates. The programs included with the Ubuntu system are free software; the exact distribution terms for each program are described in the individual files in /usr/share/doc/*/copyright. Ubuntu comes with ABSOLUTELY NO WARRANTY, to the extent permitted by applicable law. To run a command as administrator (user "root"), use "sudo ". See "man sudo_root" for details. ubuntu@ee-motd-verify:~$ echo $MOTD_SHOWN pam ubuntu@ee-motd-verify:~$ dpkg -l libpam-modules | cat Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name VersionArchitecture Description +++--==-- ii libpam-modules:amd64 1.3.1-5ubuntu1.19.10.0 amd64Pluggable Authentication Modules for PAM ** Tags removed: verification-needed verification-needed-eoan ** Tags added: verification-done verification-done-eoan -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pam in Ubuntu. https://bugs.launchpad.net/bugs/1855092 Title: [SRU] Please set MOTD_SHOWN=pam when MOTD was shown Status in pam package in Ubuntu: Fix Released Status in pam source package in Eoan: Fix Committed Bug description: [Impact] * Users of containers may never see the MOTD of the container if they are always to the container's shell without PAM being involved. * MOTD contains important information about the system's health including the security updates to be installed thus it is desired to show MOTD in container shells, too. * The fix in update-motd is creating a snippet in /etc/profile.d which shows MOTD, but only if UPDATE_MOTD is not set, to avoid printing MOTD twice. [Test Case] * Log in to the system, where PAM prints the MOTD. * After seeing the MOTD observe MOTD_SHOWN set: $ echo $MOTD_SHOWN pam $ [Regression Potential] * The fix is simple thus it is unlikely to see any regression due to bad implementation. * The newly set environment variable may interact with existing software, but this variable seems to be not used: https://codesearch.debian.net/search?q=MOTD_SHOWN=1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1855092/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1855549] Re: ubuntu-wsl: Please recommend show-motd
Ubuntu-wsl recommends show-motd: root@ee-motd-verify:~# apt show ubuntu-wsl Package: ubuntu-wsl Version: 1.440.1 Priority: optional Section: metapackages Source: ubuntu-meta Origin: Ubuntu Maintainer: Ubuntu Developers Bugs: https://bugs.launchpad.net/ubuntu/+filebug Installed-Size: 50.2 kB Depends: wslu Recommends: dbus-x11, show-motd Supported: 9m Download-Size: 2580 B APT-Sources: http://archive.ubuntu.com/ubuntu eoan-proposed/main amd64 Packages Description: Ubuntu on Windows tools - Windows Subsystem for Linux integration Utilities for integrating Ubuntu well into the WSL environment. . It is also used to help ensure proper upgrades, so it is recommended that it not be removed. N: There is 1 additional record. Please use the '-a' switch to see it ** Tags removed: verification-needed verification-needed-eoan ** Tags added: verification-done verification-done-eoan -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1855549 Title: ubuntu-wsl: Please recommend show-motd Status in ubuntu-meta package in Ubuntu: Fix Released Status in ubuntu-meta source package in Eoan: Fix Committed Bug description: [ Impact ] * Desktop users of WSL are 'dropped into' the Ubuntu shell instead of logging in to the WSL container, thus they don't see MOTD. Then don't get information about the system's state via desktop notifications either, because the default Ubuntu WSL system does not start the Ubuntu desktop. * To show important system information to users being dropped to a shell directly the show-motd package was created to show MOTD using a /etc/profile.d script. * To have this script in place ubuntu-wsl needs to recommend show-motd. [ Test Case ] * Use 'apt-cache show ubuntu-wsl' to check if ubuntu-wsl recommends update-motd. [ Regression Potential ] * Pulling in a /etc/profile.d script that exits can make the started shell exit immediately. For this reason the shell does not exit in any case. The script can also throw confusing errors. To avoid such errors the script is tested in an autopkgtest and many related packages were fixed where errors were observed. The update-motd package adds Breaks: against related package versions which are known to show errors in MOTD when being run as a regular user. See LP: #1855271 for more details. [ Other Info ] * The update-motd SRU needs to be accepted before this ubuntu-meta SRU because show-motd is a new binary package of update-motd. * The SRU upload to Eoan waits for the acceptance of update-motd to Eoan and also for the seed merge. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1855549/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1856574] [NEW] removal of various autopilot packages
Public bug reported: python-fixtures and python-testtools are not built anymore in focal, but still referenced by some Ubuntu-only packages. We need to at least remove autopilot-legacy if we don't want to re-introduce those package, and modify autopilot-gtk to build witout the autopilot-legacy b-d. ** Affects: autopilot-gtk (Ubuntu) Importance: Undecided Status: New ** Affects: autopilot-legacy (Ubuntu) Importance: Undecided Status: New ** Affects: python-fixtures (Ubuntu) Importance: Undecided Status: New ** Affects: python-testtools (Ubuntu) Importance: Undecided Status: New ** Also affects: autopilot-gtk (Ubuntu) Importance: Undecided Status: New ** Also affects: python-testtools (Ubuntu) Importance: Undecided Status: New ** Also affects: python-fixtures (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-testtools in Ubuntu. https://bugs.launchpad.net/bugs/1856574 Title: removal of various autopilot packages Status in autopilot-gtk package in Ubuntu: New Status in autopilot-legacy package in Ubuntu: New Status in python-fixtures package in Ubuntu: New Status in python-testtools package in Ubuntu: New Bug description: python-fixtures and python-testtools are not built anymore in focal, but still referenced by some Ubuntu-only packages. We need to at least remove autopilot-legacy if we don't want to re-introduce those package, and modify autopilot-gtk to build witout the autopilot-legacy b-d. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autopilot-gtk/+bug/1856574/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1855271] Re: Please make /etc/update-motd.d snippets runnable by regular users
Verified 3.192.26.1 on Eoan: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-eoan/eoan/amd64/u/update-motd/20191211_173053_e85d9@/log.gz : autopkgtest [17:30:02]: test show-motd: [--- Welcome to Ubuntu 19.10 (GNU/Linux 5.3.0-24-generic x86_64) * Documentation: https://help.ubuntu.com * Management: https://landscape.canonical.com * Support:https://ubuntu.com/advantage .--.__.--. ( \ / ) \ /\ / \_ \/ _/ /\ (/\) `--' `--' FreedomBox FreedomBox is a pure blend of Debian GNU/Linux. Web interface is available at https://localhost/ . FreedomBox manual is available in /usr/share/doc/freedombox and from the web interface. Successive commands usually process the same argument. 'Alt-.' inserts the last argument of the previous command. GNU readline rocks, read the manual. 25 updates can be installed immediately. 0 of these updates are security updates. To see these additional updates run: apt list --upgradable *** System restart required *** This message is shown once once a day. To disable it please create the /home/ubuntu/.hushlogin file. autopkgtest [17:30:03]: test show-motd: ---] show-motdPASS ** Tags removed: verification-needed verification-needed-eoan ** Tags added: verification-done verification-done-eoan ** Changed in: update-notifier (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-files in Ubuntu. https://bugs.launchpad.net/bugs/1855271 Title: Please make /etc/update-motd.d snippets runnable by regular users Status in base-files package in Ubuntu: Fix Released Status in ubuntu-release-upgrader package in Ubuntu: Fix Released Status in update-notifier package in Ubuntu: Fix Released Status in base-files source package in Eoan: Fix Committed Status in ubuntu-release-upgrader source package in Eoan: Fix Committed Status in update-notifier source package in Eoan: Fix Committed Bug description: [Impact] * /etc/update-motd.d snippets throw errors when a normal user runs them. * This prevents showing MOTD when the user is dropped to a regular user's shell in WSL. [Test Case] * Run update-motd's autopkgtest and observe scripts not throwing errors. [Regression Potential] * The fixes are fairly simple, but to ensure no breakage the scripts are also run as root. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1855271/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1855271] Re: Please make /etc/update-motd.d snippets runnable by regular users
The verification covered all the three SRU-d source packages: Get:1 http://ftpmaster.internal/ubuntu eoan-proposed/main amd64 base-files amd64 10.2ubuntu7.19.10.0 [60.6 kB] ... Get:5 http://ftpmaster.internal/ubuntu eoan-proposed/main amd64 python3-distupgrade all 1:19.10.15.4 [102 kB] Get:6 http://ftpmaster.internal/ubuntu eoan-proposed/main amd64 update-notifier-common all 3.192.26.1 [162 kB] -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-files in Ubuntu. https://bugs.launchpad.net/bugs/1855271 Title: Please make /etc/update-motd.d snippets runnable by regular users Status in base-files package in Ubuntu: Fix Released Status in ubuntu-release-upgrader package in Ubuntu: Fix Released Status in update-notifier package in Ubuntu: Fix Released Status in base-files source package in Eoan: Fix Committed Status in ubuntu-release-upgrader source package in Eoan: Fix Committed Status in update-notifier source package in Eoan: Fix Committed Bug description: [Impact] * /etc/update-motd.d snippets throw errors when a normal user runs them. * This prevents showing MOTD when the user is dropped to a regular user's shell in WSL. [Test Case] * Run update-motd's autopkgtest and observe scripts not throwing errors. [Regression Potential] * The fixes are fairly simple, but to ensure no breakage the scripts are also run as root. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1855271/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1855133] Re: SRU: update python2.7 to the 2.7.17 release
This bug was fixed in the package python-stdlib-extensions - 2.7.17-1~18.04 --- python-stdlib-extensions (2.7.17-1~18.04) bionic-proposed; urgency=medium * SRU: LP: #1855133. * Backport Python 2.7.17 to 18.04 LTS. python-stdlib-extensions (2.7.17-1) unstable; urgency=medium * Python 2.7.17 release (no changes). python-stdlib-extensions (2.7.17~rc1-1) unstable; urgency=medium * Python 2.7.17 release candidate 1. * Bump standards version. -- Matthias Klose Wed, 04 Dec 2019 13:57:29 +0100 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python2.7 in Ubuntu. https://bugs.launchpad.net/bugs/1855133 Title: SRU: update python2.7 to the 2.7.17 release Status in python-stdlib-extensions package in Ubuntu: Fix Released Status in python2.7 package in Ubuntu: Fix Released Status in python-stdlib-extensions source package in Bionic: Fix Released Status in python2.7 source package in Bionic: Fix Released Status in python-stdlib-extensions source package in Eoan: Fix Released Status in python2.7 source package in Eoan: Fix Released Bug description: This is a proposal to backport the Python 2.7.17 release to bionic. - python2.7 - python-stdlib-extensions - python-defaults is not required, but could be used to trigger autopkg tests in the -proposed pocket. The package builds are prepared in https://launchpad.net/~ubuntu-toolchain-r/+archive/ubuntu/ppa/+packages [Impact] Provide an upstream release for Python 2.7. [Regression Potential] There is regression potential, however with a test rebuild of the main portion of the archive no regressions were found. [Test Case] No regressions in the Python test suite, and no regressions in the test rebuild of the main component of the archive (all architectures) As a test, an archive rebuild for main was performed, and no regressions were found with this new package. The archive rebuild also contained updated versions of gcc-7, gcc-8, python-stdlib-extensions and python2.7. The GCC and Python packages should not infer with each other. [Validation] Analyze the build logs for regressions. The OpenStack packaging team is checking OpenStack against the built packages in -proposed. Summary of the test rebuilds: https://people.canonical.com/~doko/ftbfs-report/test-rebuild-20191107-bionic-bionic.html https://people.canonical.com/~doko/ftbfs-report/test-rebuild-20191107-bionic-gcc7-bionic.html The first one is a reference build, the second one the test rebuild with the updated components. There are no additional regressions except for one Python test, which sometimes hangs on the buildds, sometimes passes (test_ttk_guionly). Will be disabled in a follow-up upload. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-stdlib-extensions/+bug/1855133/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1855133] Re: SRU: update python2.7 to the 2.7.17 release
This bug was fixed in the package python-stdlib-extensions - 2.7.17-1~19.10 --- python-stdlib-extensions (2.7.17-1~19.10) eoan-proposed; urgency=medium * SRU: LP: #1855133. * Backport Python 2.7.17 to 19.10 LTS. python-stdlib-extensions (2.7.17-1) unstable; urgency=medium * Python 2.7.17 release (no changes). -- Matthias Klose Wed, 04 Dec 2019 13:57:29 +0100 ** Changed in: python-stdlib-extensions (Ubuntu Eoan) Status: Fix Committed => Fix Released ** Changed in: python-stdlib-extensions (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python2.7 in Ubuntu. https://bugs.launchpad.net/bugs/1855133 Title: SRU: update python2.7 to the 2.7.17 release Status in python-stdlib-extensions package in Ubuntu: Fix Released Status in python2.7 package in Ubuntu: Fix Released Status in python-stdlib-extensions source package in Bionic: Fix Released Status in python2.7 source package in Bionic: Fix Released Status in python-stdlib-extensions source package in Eoan: Fix Released Status in python2.7 source package in Eoan: Fix Released Bug description: This is a proposal to backport the Python 2.7.17 release to bionic. - python2.7 - python-stdlib-extensions - python-defaults is not required, but could be used to trigger autopkg tests in the -proposed pocket. The package builds are prepared in https://launchpad.net/~ubuntu-toolchain-r/+archive/ubuntu/ppa/+packages [Impact] Provide an upstream release for Python 2.7. [Regression Potential] There is regression potential, however with a test rebuild of the main portion of the archive no regressions were found. [Test Case] No regressions in the Python test suite, and no regressions in the test rebuild of the main component of the archive (all architectures) As a test, an archive rebuild for main was performed, and no regressions were found with this new package. The archive rebuild also contained updated versions of gcc-7, gcc-8, python-stdlib-extensions and python2.7. The GCC and Python packages should not infer with each other. [Validation] Analyze the build logs for regressions. The OpenStack packaging team is checking OpenStack against the built packages in -proposed. Summary of the test rebuilds: https://people.canonical.com/~doko/ftbfs-report/test-rebuild-20191107-bionic-bionic.html https://people.canonical.com/~doko/ftbfs-report/test-rebuild-20191107-bionic-gcc7-bionic.html The first one is a reference build, the second one the test rebuild with the updated components. There are no additional regressions except for one Python test, which sometimes hangs on the buildds, sometimes passes (test_ttk_guionly). Will be disabled in a follow-up upload. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-stdlib-extensions/+bug/1855133/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1856257] Re: SIOCSIFFLAGS: Input/output error
Thank you for the update Martin, and the good news. I'll mark this report "Incomplete" for now as the problem appears to have fixed itself; if however the problem re-occurs, please change the Status back to "New". Thank you for uploading your upgrade logs, and for your effort in helping make Ubuntu better. Note to any readers: It could be this report is marked against the wrong package, possibly should be oem-wifi-iwlwifi... ** Changed in: net-tools (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to net-tools in Ubuntu. https://bugs.launchpad.net/bugs/1856257 Title: SIOCSIFFLAGS: Input/output error Status in net-tools package in Ubuntu: Incomplete Bug description: My wifi is no longer working since a recent update (yesterday, I think). When typing “ifconfig -a”, I get (among other connections), the following one, which seems to correspond to my wifi card: ```bash wlp59s0: flags=4098 mtu 1500 ether 5c:87:9c:fa:81:c9 txqueuelen 1000 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 ``` I thus tried to switch it on, but I get the following message: ```bash $ sudo ifconfig wlp59s0 up SIOCSIFFLAGS: Input/output error ``` This error message is not really helpful: I would have expected ifconfig to provide a more user-friendly explanation about what is not working well. Other commands that might be relevant: ```bash $ iwconfig lono wireless extensions. enp0s20f0u1 no wireless extensions. wlp59s0 IEEE 802.11 ESSID:off/any Mode:Managed Access Point: Not-Associated Tx-Power=0 dBm Retry short limit:7 RTS thr:off Fragment thr:off Power Management:on $ rfkill list all 0: hci0: Bluetooth Soft blocked: no Hard blocked: no 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no $ sudo ip link set wlp59s0 up RTNETLINK answers: Input/output error ``` I’m calling apport-collect on this bug to add other relevant information. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Dependencies: gcc-8-base 8.3.0-6ubuntu1~18.04.1 libc6 2.27-3ubuntu1 libgcc1 1:8.3.0-6ubuntu1~18.04.1 libpcre3 2:8.39-9 libselinux1 2.7-2build2 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+berlinetta-cfl-r+X77 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-08-28 (106 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 Package: net-tools 1.60+git20161116.90da8a0-1ubuntu1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.15.0-1065.75-oem 4.15.18 Tags: bionic Uname: Linux 4.15.0-1065-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/net-tools/+bug/1856257/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1808476] Re: Please bump libssl1.1 dependency to at least >= 1.1.1, as headers leak constants
This bug was fixed in the package python2.7 - 2.7.17-1~18.04 --- python2.7 (2.7.17-1~18.04) bionic-proposed; urgency=medium * SRU: LP: #1855133. * Backport Python 2.7.17 to 18.04 LTS. * Don't run the test_ttk_guionly test, hangs on the buildds. python2.7 (2.7.17-1) unstable; urgency=medium * Python 2.7.17 release. python2.7 (2.7.17~rc1-1) unstable; urgency=medium * Python 2.7.17 release candidate 1. - CVE-2019-16056, don't parse domains containing @. Closes: #940901. * Bump standards version. python2.7 (2.7.16-4) unstable; urgency=medium * Update to 20190904 from the 2.7 branch. * Refresh patches. * Drop build dependency on python:any. Addresses: #937569. * Annotate Build-Depends: xvfb and xauth with . Closes: #928514. python2.7 (2.7.16-3) unstable; urgency=medium * Update to 20190708 from the 2.7 branch. * Bump standards version. python2.7 (2.7.16-2) unstable; urgency=high [ Matthias Klose ] * CVE-2019-9636. Fix issue #36216: Add check for characters in netloc that normalize to separators. Closes: #924073. * CVE-2019-9948. Fix issue #35907: Stop urllib exposing the local_file schema (file://). [ Dimitri John Ledkov ] * Bump Build-Depedency and Dependency of libssl-dev and libss1.1 to 1.1.1 or higher. As TLS1.3 constants leak into ssl module, thus one shouldn't mix and match python2.7 & libssl1.1. LP: #1808476 python2.7 (2.7.16-1) unstable; urgency=medium * Python 2.7.16 release. - Now has a version without a trailing '+'. Closes: #914072. python2.7 (2.7.16~rc1-1) unstable; urgency=medium * Python 2.7.16 release candidate 1. python2.7 (2.7.15-9) unstable; urgency=medium * Update to 20190216 from the 2.7 branch. - Backport of TLS 1.3 related fixes from 3.7. * Drop the local TLS 1.3 backports. python2.7 (2.7.15-8) unstable; urgency=medium * Fix typo in autopkg test. python2.7 (2.7.15-7) unstable; urgency=medium * Expect the test_site test failing as in 3.7. python2.7 (2.7.15-6) unstable; urgency=medium * Update to 20190201 from the 2.7 branch. - CVE-2013-1752: Limit imaplib.IMAP4_SSL.readline(). - CVE-2018-14647: _elementtree.c doesn't call XML_SetHashSalt(). Closes: #921039. - CVE-2019-5010: DsO vulnerability exists in the X509 certificate parser. Closes: #921040. * Bump standards version. * Update symbols file. python2.7 (2.7.15-5) unstable; urgency=medium * Update to 20181127 from the 2.7 branch. - Fix issue #20744, running an external 'zip' in shutil.make_archive(). CVE-2018-1000802. Closes: #909673. * Cherrypick in-progress backports to 2.7 branch from 3.6 branch to fix test_ssl assertions with openssl 1.1.1. Resolves autopkgtest failure of the 2.7 with openssl 1.1.1 (Dimitri John Ledkov). * Don't hard code location of netinet/in.h. Closes: #912422. * Update VCS attributes. -- Matthias Klose Thu, 07 Nov 2019 11:07:09 +0100 ** Changed in: python2.7 (Ubuntu Bionic) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2019-16056 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python2.7 in Ubuntu. https://bugs.launchpad.net/bugs/1808476 Title: Please bump libssl1.1 dependency to at least >= 1.1.1, as headers leak constants Status in python2.7 package in Ubuntu: Fix Released Status in python2.7 source package in Bionic: Fix Released Status in python2.7 source package in Cosmic: Fix Released Status in python2.7 source package in Disco: Fix Released Bug description: [Impact] $ python -c 'import ssl; print(ssl.OP_NO_TLSv1_3)' Prints 0, for python2.7 built against 1.1.0 headers, yet prints 536870912 when built against 1.1.1 irrespective of the runtime libssl1.1 library version. This may yield confusion, especially since ssl.OPENSSL_VERSION reports runtime libssl version, not the version of the libssl headers. Such that, e.g. it looks like ssl module is running against 1.1.1, has OP_NO_TLSv1_3 option, yet cannot actually use it to disable TLSv1.3. Also vice versa, python2.7 build against 1.1.1 can be installed with 1.1.0 runtime library, and thus OP_NO_TLSv1_3 might be set, which is not understood by the runtime library. In libpython2.7-stdlib, please bump libssl1.1 version dep to "libssl1.1 (>= 1.1.1)" when building against libssl-dev >= 1.1.1. python3.x are not affected, as they started to exploit 1.1.1-only symbols/features, and thus already have an automatic dep on >= 1.1.1. [Test Case] Make sure the libssl1.1 build-dependency of python2.7 is at least 1.1.1. [Regression Potential] Potentially none, besides the usual regression potential of new rebuilds. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1808476/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to
[Touch-packages] [Bug 1855133] Re: SRU: update python2.7 to the 2.7.17 release
This bug was fixed in the package python2.7 - 2.7.17-1~18.04 --- python2.7 (2.7.17-1~18.04) bionic-proposed; urgency=medium * SRU: LP: #1855133. * Backport Python 2.7.17 to 18.04 LTS. * Don't run the test_ttk_guionly test, hangs on the buildds. python2.7 (2.7.17-1) unstable; urgency=medium * Python 2.7.17 release. python2.7 (2.7.17~rc1-1) unstable; urgency=medium * Python 2.7.17 release candidate 1. - CVE-2019-16056, don't parse domains containing @. Closes: #940901. * Bump standards version. python2.7 (2.7.16-4) unstable; urgency=medium * Update to 20190904 from the 2.7 branch. * Refresh patches. * Drop build dependency on python:any. Addresses: #937569. * Annotate Build-Depends: xvfb and xauth with . Closes: #928514. python2.7 (2.7.16-3) unstable; urgency=medium * Update to 20190708 from the 2.7 branch. * Bump standards version. python2.7 (2.7.16-2) unstable; urgency=high [ Matthias Klose ] * CVE-2019-9636. Fix issue #36216: Add check for characters in netloc that normalize to separators. Closes: #924073. * CVE-2019-9948. Fix issue #35907: Stop urllib exposing the local_file schema (file://). [ Dimitri John Ledkov ] * Bump Build-Depedency and Dependency of libssl-dev and libss1.1 to 1.1.1 or higher. As TLS1.3 constants leak into ssl module, thus one shouldn't mix and match python2.7 & libssl1.1. LP: #1808476 python2.7 (2.7.16-1) unstable; urgency=medium * Python 2.7.16 release. - Now has a version without a trailing '+'. Closes: #914072. python2.7 (2.7.16~rc1-1) unstable; urgency=medium * Python 2.7.16 release candidate 1. python2.7 (2.7.15-9) unstable; urgency=medium * Update to 20190216 from the 2.7 branch. - Backport of TLS 1.3 related fixes from 3.7. * Drop the local TLS 1.3 backports. python2.7 (2.7.15-8) unstable; urgency=medium * Fix typo in autopkg test. python2.7 (2.7.15-7) unstable; urgency=medium * Expect the test_site test failing as in 3.7. python2.7 (2.7.15-6) unstable; urgency=medium * Update to 20190201 from the 2.7 branch. - CVE-2013-1752: Limit imaplib.IMAP4_SSL.readline(). - CVE-2018-14647: _elementtree.c doesn't call XML_SetHashSalt(). Closes: #921039. - CVE-2019-5010: DsO vulnerability exists in the X509 certificate parser. Closes: #921040. * Bump standards version. * Update symbols file. python2.7 (2.7.15-5) unstable; urgency=medium * Update to 20181127 from the 2.7 branch. - Fix issue #20744, running an external 'zip' in shutil.make_archive(). CVE-2018-1000802. Closes: #909673. * Cherrypick in-progress backports to 2.7 branch from 3.6 branch to fix test_ssl assertions with openssl 1.1.1. Resolves autopkgtest failure of the 2.7 with openssl 1.1.1 (Dimitri John Ledkov). * Don't hard code location of netinet/in.h. Closes: #912422. * Update VCS attributes. -- Matthias Klose Thu, 07 Nov 2019 11:07:09 +0100 ** Changed in: python2.7 (Ubuntu Bionic) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2013-1752 ** CVE added: https://cve.mitre.org/cgi- bin/cvename.cgi?name=2018-1000802 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2018-14647 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2019-16056 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2019-5010 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2019-9636 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2019-9948 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python2.7 in Ubuntu. https://bugs.launchpad.net/bugs/1855133 Title: SRU: update python2.7 to the 2.7.17 release Status in python-stdlib-extensions package in Ubuntu: Fix Released Status in python2.7 package in Ubuntu: Fix Released Status in python-stdlib-extensions source package in Bionic: Fix Committed Status in python2.7 source package in Bionic: Fix Released Status in python-stdlib-extensions source package in Eoan: Fix Committed Status in python2.7 source package in Eoan: Fix Released Bug description: This is a proposal to backport the Python 2.7.17 release to bionic. - python2.7 - python-stdlib-extensions - python-defaults is not required, but could be used to trigger autopkg tests in the -proposed pocket. The package builds are prepared in https://launchpad.net/~ubuntu-toolchain-r/+archive/ubuntu/ppa/+packages [Impact] Provide an upstream release for Python 2.7. [Regression Potential] There is regression potential, however with a test rebuild of the main portion of the archive no regressions were found. [Test Case] No regressions in the Python test suite, and no regressions in the test rebuild of the main component of the archive (all architectures) As a test, an archive rebuild for main was performed, and no regressions were found with this
[Touch-packages] [Bug 1855133] Update Released
The verification of the Stable Release Update for python-stdlib- extensions has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python2.7 in Ubuntu. https://bugs.launchpad.net/bugs/1855133 Title: SRU: update python2.7 to the 2.7.17 release Status in python-stdlib-extensions package in Ubuntu: Fix Released Status in python2.7 package in Ubuntu: Fix Released Status in python-stdlib-extensions source package in Bionic: Fix Committed Status in python2.7 source package in Bionic: Fix Released Status in python-stdlib-extensions source package in Eoan: Fix Committed Status in python2.7 source package in Eoan: Fix Released Bug description: This is a proposal to backport the Python 2.7.17 release to bionic. - python2.7 - python-stdlib-extensions - python-defaults is not required, but could be used to trigger autopkg tests in the -proposed pocket. The package builds are prepared in https://launchpad.net/~ubuntu-toolchain-r/+archive/ubuntu/ppa/+packages [Impact] Provide an upstream release for Python 2.7. [Regression Potential] There is regression potential, however with a test rebuild of the main portion of the archive no regressions were found. [Test Case] No regressions in the Python test suite, and no regressions in the test rebuild of the main component of the archive (all architectures) As a test, an archive rebuild for main was performed, and no regressions were found with this new package. The archive rebuild also contained updated versions of gcc-7, gcc-8, python-stdlib-extensions and python2.7. The GCC and Python packages should not infer with each other. [Validation] Analyze the build logs for regressions. The OpenStack packaging team is checking OpenStack against the built packages in -proposed. Summary of the test rebuilds: https://people.canonical.com/~doko/ftbfs-report/test-rebuild-20191107-bionic-bionic.html https://people.canonical.com/~doko/ftbfs-report/test-rebuild-20191107-bionic-gcc7-bionic.html The first one is a reference build, the second one the test rebuild with the updated components. There are no additional regressions except for one Python test, which sometimes hangs on the buildds, sometimes passes (test_ttk_guionly). Will be disabled in a follow-up upload. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-stdlib-extensions/+bug/1855133/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1855133] Re: SRU: update python2.7 to the 2.7.17 release
This bug was fixed in the package python2.7 - 2.7.17-1~19.10 --- python2.7 (2.7.17-1~19.10) eoan-proposed; urgency=medium * SRU: LP: #1855133. * Backport Python 2.7.17 to 19.10. * Don't run the test_ttk_guionly test, hangs on the buildds. python2.7 (2.7.17-1) unstable; urgency=medium * Python 2.7.17 release. -- Matthias Klose Thu, 07 Nov 2019 11:07:09 +0100 ** Changed in: python2.7 (Ubuntu Eoan) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python2.7 in Ubuntu. https://bugs.launchpad.net/bugs/1855133 Title: SRU: update python2.7 to the 2.7.17 release Status in python-stdlib-extensions package in Ubuntu: Fix Released Status in python2.7 package in Ubuntu: Fix Released Status in python-stdlib-extensions source package in Bionic: Fix Committed Status in python2.7 source package in Bionic: Fix Released Status in python-stdlib-extensions source package in Eoan: Fix Committed Status in python2.7 source package in Eoan: Fix Released Bug description: This is a proposal to backport the Python 2.7.17 release to bionic. - python2.7 - python-stdlib-extensions - python-defaults is not required, but could be used to trigger autopkg tests in the -proposed pocket. The package builds are prepared in https://launchpad.net/~ubuntu-toolchain-r/+archive/ubuntu/ppa/+packages [Impact] Provide an upstream release for Python 2.7. [Regression Potential] There is regression potential, however with a test rebuild of the main portion of the archive no regressions were found. [Test Case] No regressions in the Python test suite, and no regressions in the test rebuild of the main component of the archive (all architectures) As a test, an archive rebuild for main was performed, and no regressions were found with this new package. The archive rebuild also contained updated versions of gcc-7, gcc-8, python-stdlib-extensions and python2.7. The GCC and Python packages should not infer with each other. [Validation] Analyze the build logs for regressions. The OpenStack packaging team is checking OpenStack against the built packages in -proposed. Summary of the test rebuilds: https://people.canonical.com/~doko/ftbfs-report/test-rebuild-20191107-bionic-bionic.html https://people.canonical.com/~doko/ftbfs-report/test-rebuild-20191107-bionic-gcc7-bionic.html The first one is a reference build, the second one the test rebuild with the updated components. There are no additional regressions except for one Python test, which sometimes hangs on the buildds, sometimes passes (test_ttk_guionly). Will be disabled in a follow-up upload. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-stdlib-extensions/+bug/1855133/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1856554] Re: Epic bug which affects keyboard responsiveness (zomg :p)
Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem. We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures. At a minimum, we need: 1. The specific steps or actions you took that caused you to encounter the problem. 2. The behavior you expected. 3. The behavior you actually encountered (in as much detail as possible). Please execute the following command only once, as it will automatically gather debugging information, in a terminal: apport-collect 1856554 When reporting bugs in the future please use apport by using 'ubuntu- bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs. ** Changed in: wayland (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1856554 Title: Epic bug which affects keyboard responsiveness (zomg :p) Status in wayland package in Ubuntu: Incomplete Bug description: Open terminal. Type /\^/__ (_ character as space) Leave terminal open you might have to snap it on a desktop in a certain way ~ https://bugzilla.redhat.com/show_bug.cgi?id=1674486 https://bugs.launchpad.net/ubuntu/+source/xfce4/+bug/1838154 Keep terminal in a first place of opened windows list. Result: responsive keyboard that doesn't lag better scrolling looks like this even affects loading performance >:] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wayland/+bug/1856554/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1856257] Re: SIOCSIFFLAGS: Input/output error
Ah, OK ☺ Good. There was a package update this morning, of the “oem-wifi-iwlwifi-mainline-5.1rc1-dkms” package. Because there was “wifi” in the name, I immediately restarted the system. So good news: I got wifi now! If it is of any help, here is the transcript of the installation (which was unusually long). Regards, Martin. ** Attachment added: "upgrade logs" https://bugs.launchpad.net/ubuntu/+source/net-tools/+bug/1856257/+attachment/5312901/+files/wifi -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to net-tools in Ubuntu. https://bugs.launchpad.net/bugs/1856257 Title: SIOCSIFFLAGS: Input/output error Status in net-tools package in Ubuntu: New Bug description: My wifi is no longer working since a recent update (yesterday, I think). When typing “ifconfig -a”, I get (among other connections), the following one, which seems to correspond to my wifi card: ```bash wlp59s0: flags=4098 mtu 1500 ether 5c:87:9c:fa:81:c9 txqueuelen 1000 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 ``` I thus tried to switch it on, but I get the following message: ```bash $ sudo ifconfig wlp59s0 up SIOCSIFFLAGS: Input/output error ``` This error message is not really helpful: I would have expected ifconfig to provide a more user-friendly explanation about what is not working well. Other commands that might be relevant: ```bash $ iwconfig lono wireless extensions. enp0s20f0u1 no wireless extensions. wlp59s0 IEEE 802.11 ESSID:off/any Mode:Managed Access Point: Not-Associated Tx-Power=0 dBm Retry short limit:7 RTS thr:off Fragment thr:off Power Management:on $ rfkill list all 0: hci0: Bluetooth Soft blocked: no Hard blocked: no 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no $ sudo ip link set wlp59s0 up RTNETLINK answers: Input/output error ``` I’m calling apport-collect on this bug to add other relevant information. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Dependencies: gcc-8-base 8.3.0-6ubuntu1~18.04.1 libc6 2.27-3ubuntu1 libgcc1 1:8.3.0-6ubuntu1~18.04.1 libpcre3 2:8.39-9 libselinux1 2.7-2build2 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+berlinetta-cfl-r+X77 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-08-28 (106 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 Package: net-tools 1.60+git20161116.90da8a0-1ubuntu1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.15.0-1065.75-oem 4.15.18 Tags: bionic Uname: Linux 4.15.0-1065-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/net-tools/+bug/1856257/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1856554] [NEW] Epic bug which affects keyboard responsiveness (zomg :p)
Public bug reported: Open terminal. Type /\^/__ (_ character as space) Leave terminal open you might have to snap it on a desktop in a certain way ~ https://bugzilla.redhat.com/show_bug.cgi?id=1674486 https://bugs.launchpad.net/ubuntu/+source/xfce4/+bug/1838154 Keep terminal in a first place of opened windows list. Result: responsive keyboard that doesn't lag better scrolling looks like this even affects loading performance >:] ** Affects: wayland (Ubuntu) Importance: Undecided Status: New ** Summary changed: - Epic bug which affect keyboard responsiveness (zomg :p) + Epic bug which affects keyboard responsiveness (zomg :p) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1856554 Title: Epic bug which affects keyboard responsiveness (zomg :p) Status in wayland package in Ubuntu: New Bug description: Open terminal. Type /\^/__ (_ character as space) Leave terminal open you might have to snap it on a desktop in a certain way ~ https://bugzilla.redhat.com/show_bug.cgi?id=1674486 https://bugs.launchpad.net/ubuntu/+source/xfce4/+bug/1838154 Keep terminal in a first place of opened windows list. Result: responsive keyboard that doesn't lag better scrolling looks like this even affects loading performance >:] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wayland/+bug/1856554/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1843479] Re: gzip in Ubuntu Eoan results in Exec format error on WSL1
Hello Hayden, or anyone else affected,
Accepted gzip into eoan-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/gzip/1.10-0ubuntu3.1
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed. Your feedback will aid us getting this
update out to other Ubuntu users.
If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-eoan to verification-done-eoan. If it does not fix
the bug for you, please add a comment stating that, and change the tag
to verification-failed-eoan. In either case, without details of your
testing we will not be able to proceed.
Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in
advance for helping!
N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.
** Changed in: gzip (Ubuntu Eoan)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to binutils in Ubuntu.
https://bugs.launchpad.net/bugs/1843479
Title:
gzip in Ubuntu Eoan results in Exec format error on WSL1
Status in binutils:
Confirmed
Status in binutils package in Ubuntu:
Fix Released
Status in gzip package in Ubuntu:
In Progress
Status in binutils source package in Eoan:
Fix Committed
Status in gzip source package in Eoan:
Fix Committed
Bug description:
[Impact]
* Running gzip on WSL1 results in the following error:
$ gzip
-bash: /bin/gzip: cannot execute binary file: Exec format error
* The error occurs frequently in package updates and makes gzip inoperable
on WSL1
* The problem is caused by PT_LOAD offset pointing past the end of file and
the fix is fixing strip to not generate such ELF files and recompiling gzip
with the fixed strip.
[Test Case]
* Check the gzip binary for wrong offset:
$ FILE=/usr/bin/gzip; readelf -W --program-headers $FILE | awk -v
size=$(stat -c %s $FILE) '/^ LOAD/ {if (strtonum($2) > size) {print "wrong
offset ("$2" ("strtonum($2)") points past EOF:" size; exit 1;}}'
[ Regression Potential ]
* The binutils fix could cause binutils to generate invalid ELF files. The
fix is very small and isolated and has been tested and accepted by upstream,
which makes such problems unlikely.
* Bugs in the toolchain in general can make the rebuilt gzip show new
errors, but this generally applies to many SRUs and security updates. The
testing period in proposed should mitigate this risk.
[Originial Bug Text]
Summary:
Running gzip on WSL1 results in the following error:
$ gzip
-bash: /bin/gzip: cannot execute binary file: Exec format error
What I expect to happen:
gzip executes correctly on WSL1.
What happens instead:
gzip fails with an Exec format error.
Notes:
I suspect a change in how gzip is being built for Eoan is causing
issues with ELF parsing on the WSL1 translation layer. For example:
On Disco with gzip 1.9-3:
$ file /bin/gzip
/bin/gzip: ELF 64-bit LSB pie executable, x86-64, version 1 (SYSV),
dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux
3.2.0, BuildID[sha1]=efa859c26eaf8e035efe9a139361e2a60cd17b3e, stripped
On Eoan with gzip 1.10-0ubuntu3:
$ file /bin/gzip
/bin/gzip: ELF 64-bit LSB pie executable, x86-64, version 1 (SYSV),
dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2,
BuildID[sha1]=bc0f5994544c2a469d04c914bf4bf44b4ded6040, for GNU/Linux 3.2.0,
stripped
Eoan ships with gzip 1.10, while Disco ships with gzip 1.9, but I do
not believe this is an issue in 1.10 because this error does not occur
when building gzip from GNU project source on Ubuntu Eoan.
Justifications:
WSL1 will need to be patched in future Windows builds for this change
in ELF. However that patch will likely not be backported to older
builds of Windows, including Windows Enterprise/Server 2019.
To ensure Eoan can run on current and older builds of Windows Ubuntu
should consider looking at how it's building gzip and see if it can be
made to 'play nice' until WSL1 can be updated.
This was originally reported here:
https://github.com/microsoft/WSL/issues/4461
Details:
Description:Ubuntu Eoan Ermine (development branch)
Release:19.10
gzip:
Installed: 1.10-0ubuntu3
Candidate: 1.10-0ubuntu3
Version table:
*** 1.10-0ubuntu3 500
500 http://archive.ubuntu.com/ubuntu eoan/main amd64 Packages
100 /var/lib/dpkg/status
To manage notifications about this bug go to:
[Touch-packages] [Bug 1856547] Re: focal live ISO fails to boot in VirtualBox (initramfs write error)
** Package changed: ubuntu => initramfs-tools (Ubuntu) -- 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/1856547 Title: focal live ISO fails to boot in VirtualBox (initramfs write error) Status in initramfs-tools package in Ubuntu: New Bug description: Please see the attached screenshot for a description of the problem. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1856547/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1856547] [NEW] focal live ISO fails to boot in VirtualBox (initramfs write error)
You have been subscribed to a public bug: Please see the attached screenshot for a description of the problem. ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: focal -- focal live ISO fails to boot in VirtualBox (initramfs write error) https://bugs.launchpad.net/bugs/1856547 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1841157] Re: have /usr/bin/oem-getlogs in apport to collect all in one logs
This bug was fixed in the package apport - 2.20.11-0ubuntu14 --- apport (2.20.11-0ubuntu14) focal; urgency=medium * apport/report.py, test/test_report.py: handle the fact that gdb now returns a different error message for truncated core files in some cases. * bin/oem-getlogs: add in script for getting hardware enablement related logs. Thanks to Yuan-Chen Cheng for the code. (LP: #1841157) * apport/hookutils.py: also gather lsusb -v and lsusb -t. Thanks to Yuan-Chen Cheng for the patch. * bin/oem-getlogs: Various pep8 / pyflakes fixes. -- Brian Murray Fri, 13 Dec 2019 08:41:58 -0800 ** Changed in: apport (Ubuntu) Status: In Progress => Fix Released -- 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/1841157 Title: have /usr/bin/oem-getlogs in apport to collect all in one logs Status in Apport: New Status in OEM Priority Project: In Progress Status in apport package in Ubuntu: Fix Released Bug description: plan to use command like $ sudo oem-getlogs to collect all logs that oem project could need. To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/1841157/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1856528] [NEW] Folder not created.
Public bug reported: 1) Ubuntu 19.10 2) tar (GNU tar) 1.30 3) I downloaded the LastPass Universal Linux Installer from the link below. I entered the following command in the terminal: tar xjvf lplinux.tar.bz2 4) I got an error in the terminal. The "lplinux" folder was not created. https://lastpass.com/lplinux.php ** Affects: tar (Ubuntu) Importance: Undecided Status: New ** Attachment added: "no_folder.png" https://bugs.launchpad.net/bugs/1856528/+attachment/5312842/+files/no_folder.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tar in Ubuntu. https://bugs.launchpad.net/bugs/1856528 Title: Folder not created. Status in tar package in Ubuntu: New Bug description: 1) Ubuntu 19.10 2) tar (GNU tar) 1.30 3) I downloaded the LastPass Universal Linux Installer from the link below. I entered the following command in the terminal: tar xjvf lplinux.tar.bz2 4) I got an error in the terminal. The "lplinux" folder was not created. https://lastpass.com/lplinux.php To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tar/+bug/1856528/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
