[Touch-packages] [Bug 1468027] Re: change default CJK fonts to Noto CJK
@tomoe_musashi: Can you please file a new bug about Noto Serif CJK instead of using this one which was closed long ago. There is some related packaging discussion at Debian: https://bugs.debian.org/862276 http://lists.alioth.debian.org/pipermail/pkg-fonts- devel/2017-May/thread.html#19499 I think it's wise to wait until we see the result of that discussion before we change anything in Ubuntu. ** Bug watch added: Debian Bug tracker #862276 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=862276 -- 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/1468027 Title: change default CJK fonts to Noto CJK Status in Ubuntu Seeds: Fix Released Status in kubuntu-meta package in Ubuntu: Fix Released Status in language-selector package in Ubuntu: Fix Released Status in lubuntu-meta package in Ubuntu: Fix Released Status in ubuntu-meta package in Ubuntu: Fix Released Status in xubuntu-meta package in Ubuntu: Fix Released Bug description: just realize that fonts-noto-cjk is available in the repository, finally its packaged. i don't really know about korean community. But for Chinese and Japanese community, i think that the answer is clear. noto-cjk is definitely better what we had before, like fonts- wqy and fonts-droid. Android community had received these complains for years, finally they got them fixed on lollipop. Fedora also set it as default chinese font start from F21. and of course, i still hope that ubuntu could drop those 69-language-selector fontconfig files, just like what F13 did. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-seeds/+bug/1468027/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1575912] Re: [hostname, Realtek ALC269VB, Speaker, Internal] No sound at all after fresh xubuntu 16.04 installation
Additional information: THe L521x shows an Nvidia Audio device - It has an Nvidia Physx GT640M Graphics card, I'm guessing its related to that. aplay -l List of PLAYBACK Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC3260 Analog [ALC3260 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0] Subdevices: 1/1 Subdevice #0: subdevice #0 card 1: NVidia [HDA NVidia], device 3: HDMI 0 [HDMI 0] Subdevices: 1/1 Subdevice #0: subdevice #0 -- 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/1575912 Title: [hostname, Realtek ALC269VB, Speaker, Internal] No sound at all after fresh xubuntu 16.04 installation Status in alsa-driver package in Ubuntu: Confirmed Bug description: Hardware sound device is available, according to: aplay -l sudo lspci https://help.ubuntu.com/16.04/ubuntu-help/sound-nosound.html ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic i686 ApportVersion: 2.20.1-0ubuntu2 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: student1739 F pulseaudio CurrentDesktop: MATE Date: Wed Apr 27 22:06:16 2016 InstallationDate: Installed on 2016-04-24 (3 days ago) InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel failed Symptom_Card: Built-in Audio - HDA Intel Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: student1739 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [hostname, Realtek ALC269VB, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/12/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0703 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: 1001PXD dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: x.xx dmi.chassis.asset.tag: 0x dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer INC. dmi.chassis.version: x.x dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0703:bd04/12/2011:svnASUSTeKComputerINC.:pn1001PXD:pvrx.x:rvnASUSTeKComputerINC.:rn1001PXD:rvrx.xx:cvnASUSTeKComputerINC.:ct10:cvrx.x: dmi.product.name: 1001PXD dmi.product.version: x.x dmi.sys.vendor: ASUSTeK Computer INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1575912/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1693850] Re: libzen wasn't compiled with large file support
> some -D compilation flags that aren't even directly referenced in the codebase FYI impact is on the 32-bit libc usage, _FILE_OFFSET_BITS=64 enabling the libc file API with "off_t" of 64-bit instead of 32-bit. No other interaction. Example of impacted user (+ I got 2 emails with same bug report, no web link): https://sourceforge.net/p/mediainfo/discussion/297610/thread/8893b38f/ -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libzen in Ubuntu. https://bugs.launchpad.net/bugs/1693850 Title: libzen wasn't compiled with large file support Status in libzen package in Ubuntu: Fix Released Status in libzen source package in Xenial: Triaged Status in libzen source package in Yakkety: Triaged Status in libzen source package in Zesty: Triaged Status in libzen source package in Artful: Fix Released Bug description: [Impact] The switch to cmake caused two compilation flags to be accidentally dropped: -D_LARGE_FILES -D_FILE_OFFSET_BITS=64 This causes all file-handling operations in zenlib to fail to work with large files on 32-bit machines. This affects the following reverse-dependencies: - libmediainfo - mediainfo - mediaconch This has been fixed in https://github.com/MediaArea/ZenLib/commit/dc105b3ed035413577d21c979d1998d889350855. [Test Case] Run `mediainfo $filename` where $filename is a file that is larger than 4.2GB. Output will be missing if this bug is present. [Regression Potential] Quite low, since the only thing that's changed here are some -D compilation flags that aren't even directly referenced in the codebase. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libzen/+bug/1693850/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1468027] Re: change default CJK fonts to Noto CJK
Sorry to bother you again but there is a new update for the Noto CJK fonts. Google and Adobe released the Serif fonts for CJK about several weeks ago Noto Serif CJK: http://www.google.com/get/noto/help/cjk/ It is a better serif font in consistency and glyph standard. Ubuntu should seed the new Noto Serif CJK over the current -- 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/1468027 Title: change default CJK fonts to Noto CJK Status in Ubuntu Seeds: Fix Released Status in kubuntu-meta package in Ubuntu: Fix Released Status in language-selector package in Ubuntu: Fix Released Status in lubuntu-meta package in Ubuntu: Fix Released Status in ubuntu-meta package in Ubuntu: Fix Released Status in xubuntu-meta package in Ubuntu: Fix Released Bug description: just realize that fonts-noto-cjk is available in the repository, finally its packaged. i don't really know about korean community. But for Chinese and Japanese community, i think that the answer is clear. noto-cjk is definitely better what we had before, like fonts- wqy and fonts-droid. Android community had received these complains for years, finally they got them fixed on lollipop. Fedora also set it as default chinese font start from F21. and of course, i still hope that ubuntu could drop those 69-language-selector fontconfig files, just like what F13 did. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-seeds/+bug/1468027/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1295567] Re: White block above web content
[Expired for webbrowser-app (Ubuntu) because there has been no activity for 60 days.] ** Changed in: webbrowser-app (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1295567 Title: White block above web content Status in webbrowser-app package in Ubuntu: Expired Bug description: I've seen this a few times. See screenshot. Randomly on various websites I see a white box above the content being rendered. If you tap the screen the website moves up to cover (and fix the issue) the white area. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: webbrowser-app 0.23+14.04.20140319-0ubuntu1 Uname: Linux 3.4.0-5-mako armv7l ApportVersion: 2.13.3-0ubuntu1 Architecture: armhf Date: Fri Mar 21 08:48:55 2014 InstallationDate: Installed on 2014-03-21 (0 days ago) InstallationMedia: Ubuntu Trusty Tahr (development branch) - armhf (20140321) ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= SHELL=/bin/bash SourcePackage: webbrowser-app UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1295567/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1693693] Re: Stuck on a black screen after logging out of Gnome Shell
Curious. I can't reproduce this problem with artful today. Everything works better and I can't see what if any relevant packages changed. ** Changed in: unity-greeter (Ubuntu) Status: New => Incomplete ** Changed in: lightdm (Ubuntu) Status: New => Incomplete ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1693693 Title: Stuck on a black screen after logging out of Gnome Shell Status in gnome-shell package in Ubuntu: Incomplete Status in lightdm package in Ubuntu: Incomplete Status in unity-greeter package in Ubuntu: Incomplete Bug description: Stuck on a black screen after logging out of Gnome Shell. Logging in via ssh shows gnome-shell is no longer running. But if I press Ctrl+Alt+F7 then the login screen (unity-greeter) comes up (and the login sound plays). ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.24.2-0ubuntu4 ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11 Uname: Linux 4.10.0-21-generic x86_64 ApportVersion: 2.20.5-0ubuntu4 Architecture: amd64 Date: Fri May 26 14:34:05 2017 DisplayManager: lightdm GsettingsChanges: b'org.gnome.shell' b'app-picker-view' b'uint32 1' b'org.gnome.shell' b'favorite-apps' b"['firefox.desktop', 'chromium-browser.desktop', 'gnome-control-center.desktop', 'org.gnome.Terminal.desktop', 'rhythmbox.desktop', 'yelp.desktop', 'org.gnome.Nautilus.desktop', 'org.gnome.Software.desktop']" b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" b'org.gnome.desktop.interface' b'scaling-factor' b'uint32 1' InstallationDate: Installed on 2017-05-03 (23 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1693693/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1283003] Re: Bluetooth headset/speakers listed but not selectable in Sound settings
** Changed in: pulseaudio (Ubuntu Xenial) Status: Triaged => In Progress ** Changed in: pulseaudio (Ubuntu Xenial) Assignee: (unassigned) => Daniel van Vugt (vanvugt) ** Changed in: pulseaudio (Ubuntu) Assignee: Daniel van Vugt (vanvugt) => (unassigned) ** Description changed: [Impact] Bluetooth headset/speakers are listed but not selectable in Sound settings (the correct device's options don't appear in the right pane). Hence no Bluetooth audio is unusable. [Test Case] 1. Pair a Bluetooth audio device with Ubuntu. 2. Go to Sound settings and try to select the device. - Expected: The Bluetooth audio device is selectable (is usable). + Expected: The Bluetooth audio device is selectable (its options appear in the right pane when clicked and the selection stays on that device). [Regression Potential] Low. The SRU focuses on Bluetooth logic in pulseaudio, so that is the main area affected. A combination of related A2DP bugs in pulseaudio in xenial means it is difficult to get working at all without this patch. So highly unlikely Bluetooth audio support could get worse. Since pulseaudio itself is being modified there is always a regression potential in support for other audio devices, but several audio devices have been tested and all continue to work well with the patch. [Other notes] Related to bug 1438510 and bug 1582213. Possibly others too. The debdiff which fixes this is attached to bug 1582213. Please note that Bluetooth and Bluetooth audio support in xenial is still not perfect. This SRU only aims to address a few of the most troublesome issues. Please consider the fact that this is an incremental improvement and some people are still likely to experience some bugs related to pulseaudio and Bluetooth, even after this SRU. The patch was authored by Luke Yelavich with help from Konrad Zapałowicz. And it has received further testing over the past two months by Konrad, Jim Hodapp and Daniel van Vugt. The debdiff proposed here only changes the changelog wording from Luke's original PPA. [Original Description] Hi, I found a bug in Ubuntu 14.04 ! I tried to pair a bluetooth stereo headset (A2DP compatible). The pairing process goes well, but after that I can't select it on the audio preferences. When I select it, it only shows the last selected item options and don't do anything. (he should switch to the headset output). I must mention that it worked very well on Ubuntu 12.04. This bug can be in the bluetooth stack or in unity-control-center or maybe pulseaudio. I actually have no idea. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1283003 Title: Bluetooth headset/speakers listed but not selectable in Sound settings Status in Blueman: New Status in blueman package in Ubuntu: Fix Released Status in bluez package in Ubuntu: Invalid Status in gnome-bluetooth package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Fix Released Status in blueman source package in Xenial: New Status in gnome-bluetooth source package in Xenial: New Status in pulseaudio source package in Xenial: In Progress Bug description: [Impact] Bluetooth headset/speakers are listed but not selectable in Sound settings (the correct device's options don't appear in the right pane). Hence no Bluetooth audio is unusable. [Test Case] 1. Pair a Bluetooth audio device with Ubuntu. 2. Go to Sound settings and try to select the device. Expected: The Bluetooth audio device is selectable (its options appear in the right pane when clicked and the selection stays on that device). [Regression Potential] Low. The SRU focuses on Bluetooth logic in pulseaudio, so that is the main area affected. A combination of related A2DP bugs in pulseaudio in xenial means it is difficult to get working at all without this patch. So highly unlikely Bluetooth audio support could get worse. Since pulseaudio itself is being modified there is always a regression potential in support for other audio devices, but several audio devices have been tested and all continue to work well with the patch. [Other notes] Related to bug 1438510 and bug 1582213. Possibly others too. The debdiff which fixes this is attached to bug 1582213. Please note that Bluetooth and Bluetooth audio support in xenial is still not perfect. This SRU only aims to address a few of the most troublesome issues. Please consider the fact that this is an incremental improvement and some people are still likely to experience some bugs related to pulseaudio and Bluetooth, even after this SRU. The patch was authored by Luke Yelavich with help from Konrad Zapałowicz. And it has received further testing over the past two months by Konrad, Jim Hodapp and Daniel van Vugt. The debdiff proposed here only c
[Touch-packages] [Bug 1582213] Re: [xenial] Bluetooth device doesn't play any sound in A2DP mode unless set to HSP/HFP first
** Changed in: pulseaudio (Ubuntu Xenial) Status: Triaged => Fix Released ** Changed in: pulseaudio (Ubuntu Xenial) Status: Fix Released => In Progress ** Changed in: pulseaudio (Ubuntu) Assignee: Daniel van Vugt (vanvugt) => (unassigned) ** Changed in: pulseaudio (Ubuntu Xenial) Assignee: (unassigned) => Daniel van Vugt (vanvugt) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1582213 Title: [xenial] Bluetooth device doesn't play any sound in A2DP mode unless set to HSP/HFP first Status in bluez package in Ubuntu: Invalid Status in pulseaudio package in Ubuntu: Fix Released Status in pulseaudio source package in Xenial: In Progress Bug description: [Impact] Bluetooth device doesn't play any sound in A2DP mode unless set to HSP/HFP first. A2DP is the high quality profile used for Bluetooth speakers and music in general. [Test Case] 1. Pair a Bluetooth audio device with Ubuntu. 2. Verify in Sound settings you have it set to A2DP mode. 3. Turn off and then on the Bluetooth device. 4. Verify the device has reconnected and if not, force it to in the Bluetooth indicator menu. 5. Open Sound settings again, select the device and verify it's reappeared in A2DP mode. 6. Click 'Test Sound'. Expected: Sound can be heard from the Bluetooth device. [Regression Potential] Low. The SRU focuses on Bluetooth logic in pulseaudio, so that is the main area affected. A combination of related A2DP bugs in pulseaudio in xenial means it is difficult to get working at all without this patch. So highly unlikely Bluetooth audio support could get worse. Since pulseaudio itself is being modified there is always a regression potential in support for other audio devices, but several audio devices have been tested and all continue to work well with the patch. [Other notes] Related to bug 1283003 and bug 1438510. Possibly others too. Please note that Bluetooth and Bluetooth audio support in xenial is still not perfect. This SRU only aims to address a few of the most troublesome issues. Please consider the fact that this is an incremental improvement and some people are still likely to experience some bugs related to pulseaudio and Bluetooth, even after this SRU. The patch was authored by Luke Yelavich with help from Konrad Zapałowicz. And it has received further testing over the past two months by Konrad, Jim Hodapp and Daniel van Vugt. The debdiff proposed here only changes the changelog wording from Luke's original PPA. [Original Description] I have a Sennheiser MM 450-X headset. In 15.10, connection & playback was straightforward. In 16.04, the headset connects, and shows up as default playback device on `pavucontrol`, but there is no sound. A functional workaround is to, after having connected it, to go the `Configuration` tab, and in the `Profile` dropdown, to choose `... HSP/HFP`, which will make them play as expected (but in low quality), then switch to `... A2DP Sink` (they will play in high quality). ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: pulseaudio-module-bluetooth 1:8.0-0ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: myuser2936 F pulseaudio /dev/snd/controlC2: myuser2936 F pulseaudio /dev/snd/controlC0: myuser2936 F pulseaudio Date: Mon May 16 14:18:58 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2016-03-11 (66 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160224) PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/22/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: F2A88XN-WIFI dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF5:bd04/22/2015:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnF2A88XN-WIFI:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor
[Touch-packages] [Bug 1438510] Re: [regression] Bluetooth audio no longer supports A2DP (stuck in HSP/HFP mode)
** Changed in: pulseaudio (Ubuntu Xenial) Status: Triaged => In Progress ** Changed in: pulseaudio (Ubuntu) Assignee: Daniel van Vugt (vanvugt) => (unassigned) ** Changed in: pulseaudio (Ubuntu Xenial) Assignee: (unassigned) => Daniel van Vugt (vanvugt) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1438510 Title: [regression] Bluetooth audio no longer supports A2DP (stuck in HSP/HFP mode) Status in PulseAudio: Confirmed Status in bluez package in Ubuntu: Invalid Status in pulseaudio package in Ubuntu: Fix Released Status in bluez source package in Vivid: Won't Fix Status in pulseaudio source package in Vivid: Won't Fix Status in pulseaudio source package in Xenial: In Progress Bug description: [Impact] Bluetooth audio seemingly refuses to support A2DP (stuck in HSP/HFP mode). A2DP is the high quality profile used for Bluetooth speakers and music in general. [Test Case] 1. Pair a Bluetooth audio device with Ubuntu. 2. Go to Sound settings and check the device's current "Mode". 3. If the current Mode is not yet A2DP then try to set it to A2DP Expected: The mode is either A2DP by default or can be set to it. [Regression Potential] Low. The SRU focuses on Bluetooth logic in pulseaudio, so that is the main area affected. A combination of related A2DP bugs in pulseaudio in xenial means it is difficult to get working at all without this patch. So highly unlikely Bluetooth audio support could get worse. Since pulseaudio itself is being modified there is always a regression potential in support for other audio devices, but several audio devices have been tested and all continue to work well with the patch. [Other notes] Related to bug 1283003 and bug 1582213. Possibly others too. The debdiff which fixes this is attached to bug 1582213. Please note that Bluetooth and Bluetooth audio support in xenial is still not perfect. This SRU only aims to address a few of the most troublesome issues. Please consider the fact that this is an incremental improvement and some people are still likely to experience some bugs related to pulseaudio and Bluetooth, even after this SRU. The patch was authored by Luke Yelavich with help from Konrad Zapałowicz. And it has received further testing over the past two months by Konrad, Jim Hodapp and Daniel van Vugt. The debdiff proposed here only changes the changelog wording from Luke's original PPA. [Original Description] Just installed 15.04 fresh from the latest ISO (beta2). I'm bummed to see my bluetooth headset (Bose Soundlink overear) seems to have regressed in functionality. In 14.10, I was able to set the output profile either to a2dp or hsp/hfp (telephony duplex). In 15.04, it only works in telephony duplex mode. I can't get high fidelity sound playback to work at all. This thread seems to be related, though the workaround within did not solve the problem for me: https://bbs.archlinux.org/viewtopic.php?id=194006 The bug is still present in 16.04 LTS and 16.10. To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1438510/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1672955] Re: unity-system-compositor crashed with SIGSEGV in libinput_device_config_accel_is_available() from libinput_device_config_accel_set_speed() from mir::input::evdev::Lib
** Changed in: mir/0.26 Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1672955 Title: unity-system-compositor crashed with SIGSEGV in libinput_device_config_accel_is_available() from libinput_device_config_accel_set_speed() from mir::input::evdev::LibInputDevice::apply_settings() Status in Canonical System Image: Fix Committed Status in Mir: Fix Committed Status in Mir 0.26 series: Fix Released Status in Unity System Compositor: Invalid Status in mir package in Ubuntu: Fix Released Status in unity-system-compositor package in Ubuntu: Invalid Status in mir source package in Xenial: Fix Committed Status in unity-system-compositor source package in Xenial: Invalid Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding unity-system-compositor. This problem was most recently seen with package version 0.9.1+17.04.20170216-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/fcf5550475fb0478d6eb2a307f03705ef1ed398a 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 you can request it at http://forms.canonical.com/reports/. It seems that the configuration change is requested just a moment before the device gets removed. The change actions are serialized, depending on where there memory of mir::input::DefaultDevice is allocated the segfault either occurs inside the lambda or inside underlying mir::input::LibInputDevice in the platform. The activities on input dispatch device removal and reconfiguration are serialized inside the input thread, so we just need to clean the action queue (or have multiple queues) before removing the devices. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1672955/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1675138] Re: Please transition to Boost 1.62
** Changed in: mir/0.26 Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1675138 Title: Please transition to Boost 1.62 Status in Mir: Fix Committed Status in Mir 0.26 series: Fix Released Status in mir package in Ubuntu: Fix Released Status in mir source package in Xenial: Fix Committed Bug description: There is an ongoing transition to Boost 1.62 and mir is one of the last affected packages: http://people.canonical.com/~ubuntu-archive/transitions/html/boost1.62.html To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1675138/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1675357] Re: Mir sending key repeat events continually to nested shell after VT switch (causes Unity8 lockup for a while)
** Changed in: mir/0.26 Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1675357 Title: Mir sending key repeat events continually to nested shell after VT switch (causes Unity8 lockup for a while) Status in Canonical System Image: In Progress Status in Mir: Fix Committed Status in Mir 0.26 series: Fix Released Status in mir package in Ubuntu: Fix Released Status in qtmir package in Ubuntu: Invalid Status in unity8 package in Ubuntu: Invalid Status in mir source package in Xenial: Fix Committed Status in qtmir source package in Xenial: Invalid Status in unity8 source package in Xenial: Invalid Bug description: Steps: * log in to unity8 * Ctrl+Alt+F* to a different vt, or log in to a different user session * go back to the unity8 vt Expected: * session is locked, but working Current: * unity8 starts spinning for a time proportional to the period it was inactive * if it was inactive long enough, it doesn't seem to recover at all It seems it's "catching up" in some way, maybe with input, maybe frames. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: unity8 8.15+17.04.20170321-0ubuntu1 [origin: LP-PPA-ci-train-ppa-service-2555] ProcVersionSignature: Ubuntu 4.10.0-13.15-generic 4.10.1 Uname: Linux 4.10.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity:Unity7 Date: Thu Mar 23 11:36:39 2017 InstallationDate: Installed on 2016-05-06 (320 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: unity8 UpgradeStatus: Upgraded to zesty on 2016-11-22 (120 days ago) Causes: The mir::input::KeyRepeatDispatcher is running inside the nested mirserver even though there is another instance running inside the host server. A few months ago qtmir used to replace the key repeater by replacing mirs dispatcher. And key repeat is not disabled within the nested server. So both the host and the nested server are producing repeat events. Now due to a logic error inside mirserver the key repeat dispatcher is not hooked up to the input device hub when running inside the nested server. The input device hub would tell the key repeater when devices get removed - i.e. due to vt switching. So it never notices that the devices go away continues to produce those events indefinitely. This applies to all currently pressed buttons. I.e. you can open an edit field and press 'w' while simultaneously pressing Ctrl+Alt+FX to switch to another VT. On return 'w' will be repeated indefinitely. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1675357/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1677239] Re: mir_demo_standalone_render_overlays fails to link
** Changed in: mir/0.26 Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1677239 Title: mir_demo_standalone_render_overlays fails to link Status in Mir: Fix Committed Status in Mir 0.26 series: Fix Released Status in mir package in Ubuntu: Fix Released Status in mir source package in Xenial: Fix Committed Bug description: https://mir-jenkins.ubuntu.com/job/build-2-binpkg- mir/arch=amd64,compiler=gcc,platform=mesa,release=zesty/4453/console 11:41:20 [ 52%] Linking CXX executable ../../../../bin/mir_demo_standalone_render_overlays.bin 11:41:20 cd /<>/mir-0.26.1+17.04.20170209.1+zesty4503bzr4124/obj-x86_64-linux-gnu/src/platforms/android/utils && /usr/bin/cmake -E cmake_link_script CMakeFiles/mir_demo_standalone_render_overlays.dir/link.txt --verbose=1 11:41:20 /usr/lib/ccache/c++ -g -O2 -fdebug-prefix-map=/<>/mir-0.26.1+17.04.20170209.1+zesty4503bzr4124=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -pthread -g -std=c++14 -Werror -Wall -fno-strict-aliasing -pedantic -Wnon-virtual-dtor -Wextra -fPIC -flto -ffat-lto-objects -Wl,-Bsymbolic-functions -Wl,-z,relro -Wl,--as-needed -Wl,--no-undefined CMakeFiles/mir_demo_standalone_render_overlays.dir/render_overlays.cpp.o -o ../../../../bin/mir_demo_standalone_render_overlays.bin -rdynamic ../../../../lib/libmirplatform.so.16 ../../../../lib/libmircommon.so.7 ../../../capnproto/libmircapnproto.a -lkj -lcapnp ../../../../lib/libmircore.so.1 -lboost_date_time -lboost_system -lboost_program_options -lboost_filesystem -ldl -lEGL -lGLESv2 -lGLESv2 -L/lib/x86_64-linux-gnu -ludev -ludev 11:41:21 //usr/lib/x86_64-linux-gnu/libmirclient.so.9: undefined reference to `MirInputDeviceStateEvent::device_pressed_keys_for_index(unsigned long, unsigned long) const@MIR_COMMON_0.25_PRIVATE' 11:41:21 //usr/lib/x86_64-linux-gnu/libmirclient.so.9: undefined reference to `MirPointerEvent::set_x(float)@MIR_COMMON_0.25_PRIVATE' 11:41:21 //usr/lib/x86_64-linux-gnu/libmirclient.so.9: undefined reference to `MirTouchEvent::pressure(unsigned long) const@MIR_COMMON_0.25_PRIVATE' To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1677239/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1685186] Re: [SRU] Mir needs to be updated to 0.26 in 16.04LTS
** Changed in: mir (Ubuntu Xenial) Status: Incomplete => In Progress ** Changed in: mir (Ubuntu Xenial) Importance: Undecided => High ** Changed in: mir (Ubuntu Xenial) Assignee: (unassigned) => Alan Griffiths (alan-griffiths) ** Changed in: mir (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 mir in Ubuntu. https://bugs.launchpad.net/bugs/1685186 Title: [SRU] Mir needs to be updated to 0.26 in 16.04LTS Status in mir package in Ubuntu: Fix Released Status in mir source package in Xenial: In Progress Bug description: [Impact] Snap development using Mir has been using the "stable phone overlay" PPA which is both inconvenient and a legacy of the cancelled Unity8 project. It would greatly simplify things if Mir were updated in the Xenial archive. [Test Case] Build a Mir client snap (e.g. lp:~albaguirre/+snap/mir-client-demos) against "Primary Ubuntu Archive" and deploy as described in https://developer.ubuntu.com/en/snappy/guides/mir-snaps/ Expected: the client apps start and are visible on screen Actual: the client apps don't start and are not visible on screen [Regression Potential] Mir has two categories of dependent project: 1 Unity8 and unity-system-compositor "server" packages 2 toolkits and other "clients" of Mir "Server" packages from the archive will stop working in the LTS as they will continue using the earlier libmirserver.so.38 (from Mir 0.21) which doesn't work with the libmirclient.so.9 from Mir 0.26. This is unimportant as these packages were provided as an "early experience", not for serious use. "Client" packages are dependent only on libmirclient.so.9 which is ABI stable. The principle type of regression would be FTBFS where APIs have been deprecated in 0.26. The linked 0.26.3 release has these deprecations disabled for 16.04. The packages are available in silo: https://bileto.ubuntu.com/#/ticket/2736 notes: A recursive search or rdependencies identifies the following packages in category 1: camera-app-autopilot gallery-app-autopilot indicator-network-autopilot indicators-client qtdeclarative5-qtmir-plugin qtmir-android qtmir-desktop qtmir-tests ubuntu-desktop-mir ubuntu-experience-tests ubuntu-pocket-desktop ubuntu-push-autopilot ubuntu-touch ubuntu-touch-session unity8 unity8-autopilot unity8-desktop-session-mir unity-scope-click-autopilot unity-system-compositor unity-system-compositor-autopilot Anyone wanting these packages should switch to the "unity8-desktop- session" preview package in 17.04 where they are far more functional. [Alternatives] If we want to keep everything working in Xenial, we *could* bump the libmirclient SONAME to libmirclient.so.10. This would result in libmirclient9 being NBS, but continuing to work against the Mir servers available in 16.04[*] (until and unless they are rebuilt). However, this does not enable the desired result for IoT deployments of toolkits (GTK, Qt etc) and other clients working against servers (specifically miral-kiosk) built against the updated libraries. To work for IoT these would need to rebuilt from source - at which point they (and their dependencies) would stop working against the servers in category 1. [*] with the exception of the servers provided in mir-examples, these would only work with clients linking against libmirclient.so.10. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mir/+bug/1685186/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1694182] [NEW] changrd to gentoo
Public bug reported: system is all messed up, dvd inop, just totally lost on this system and it seem like I can't even remove it ! ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.8.0-53.56~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-53-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Sun May 28 22:42:20 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Skylake Integrated Graphics [103c:81eb] InstallationDate: Installed on 2017-05-09 (19 days ago) InstallationMedia: Ubuntu-GNOME 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f2:b56c Chicony Electronics Co., Ltd Bus 001 Device 002: ID 8087:0a2a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Notebook ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-53-generic.efi.signed root=UUID=5cba8a50-d750-4c6f-8fe1-84ddc229f60e ro quiet splash SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/01/2016 dmi.bios.vendor: Insyde dmi.bios.version: F.17 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 81EB dmi.board.vendor: HP dmi.board.version: 61.35 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.17:bd09/01/2016:svnHP:pnHPNotebook:pvrType1ProductConfigId:rvnHP:rn81EB:rvr61.35:cvnHP:ct10:cvrChassisVersion: dmi.product.name: HP Notebook dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-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 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug 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/1694182 Title: changrd to gentoo Status in xorg package in Ubuntu: New Bug description: system is all messed up, dvd inop, just totally lost on this system and it seem like I can't even remove it ! ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.8.0-53.56~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-53-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Sun May 28 22:42:20 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Skylake Integrated Graphics [103c:81eb] InstallationDate: Installed on 2017-05-09 (19 days ago) InstallationMedia: Ubuntu-GNOME 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f2:b56c Chicony Electronics Co., Ltd Bus 001 Device 002: ID 8087:0a2a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Notebook ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-53-generic.efi.signed root=UUID=5cba8a50-d750-4c6f-8fe1-84ddc229f60e ro quiet splash SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/01/2016 dmi.bios.vendor: Insyde dmi.bios.version: F.17 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 81EB dmi.board.vendor: HP dmi.board.version: 61.35 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.17:bd09/01/2016:svnHP:pnHPNotebook:pvrType1ProductConfigId:rvnHP:rn81EB:rvr61.35:cvnHP:ct
[Touch-packages] [Bug 1690980] Re: No pop-up window to warn users that system should not reboot or shutdown while installing security updates
** Changed in: oem-priority Status: In Progress => Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1690980 Title: No pop-up window to warn users that system should not reboot or shutdown while installing security updates Status in OEM Priority Project: Triaged Status in OEM Priority Project xenial series: New Status in unattended-upgrades package in Ubuntu: Incomplete Bug description: Title: No pop-up window to warn users that system should not reboot or shutdown while installing security updates Summary: No pop-up window to warn users that system should not reboot or shutdown while installing security updates Steps: 1. trigger unattended-upgrades 2. reboot or shutdown system while installing packages Expected results: There is a pop-up window to warn users that system should not reboot or shutdown Actual results: There is no pop-up window to warn users Additional information: $ apt-cache policy unattended-upgrades unattended-upgrades: Installed: 0.90 Candidate: 0.90ubuntu0.5 $ lsb_release -rd Description:Ubuntu 16.04 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1690980/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1616651] Re: gnome-shell assert failure: *** Error in `/usr/bin/gnome-shell': free(): invalid pointer: 0x00000000082dcf30 *** in g_strfreev() from g_themed_icon_finalize() from g
** Summary changed: - gnome-shell assert failure: *** Error in `/usr/bin/gnome-shell': free(): invalid pointer: 0x082dcf30 *** + gnome-shell assert failure: *** Error in `/usr/bin/gnome-shell': free(): invalid pointer: 0x082dcf30 *** in g_strfreev() from g_themed_icon_finalize() from g_object_unref() from desktop_entry_unref() -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libgweather in Ubuntu. https://bugs.launchpad.net/bugs/1616651 Title: gnome-shell assert failure: *** Error in `/usr/bin/gnome-shell': free(): invalid pointer: 0x082dcf30 *** in g_strfreev() from g_themed_icon_finalize() from g_object_unref() from desktop_entry_unref() Status in libgweather: Confirmed Status in Ubuntu GNOME: Fix Committed Status in gnome-shell package in Ubuntu: Invalid Status in libgweather package in Ubuntu: Fix Released Status in libgweather source package in Zesty: In Progress Bug description: [Impact] Backport git patch that fixes memory corruption in libgweather that is causing gnome-shell to crash. This is particularly bad on wayland as it causes the user to lose their sessions I believe this should also fix bug 1688208 and potentially a couple of other high ranking crashes on errors.ubuntu.com. I have not however found reliable reproducers for those other bugs. [Test Case] After update of libgweather 1. Ensure org.gnome.Weather.Application locations is not set (as per default setting) 2. Disable Location Services 3. gnome-shell should not crash [Regression Potential] Low, the patch merely fixes a refcounting bug. Given the high impact of this bug, this is an important fix. === original bug report This happened while installing Xfce with Synaptic. chris@localhost:~$ lsb_release -rd Description: Ubuntu 16.04.1 LTS Release: 16.04 chris@localhost:~$ apt-cache policy gnome-shell gnome-shell: Installed: 3.18.5-0ubuntu0.1 Candidate: 3.18.5-0ubuntu0.1 Version table: *** 3.18.5-0ubuntu0.1 500 500 http://us.archive.ubuntu.com/ubuntu xenial-updates/universe amd64 Packages 100 /var/lib/dpkg/status 3.18.4-0ubuntu3 500 500 http://us.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages ProblemType: CrashDistroRelease: Ubuntu 16.04 Package: gnome-shell 3.18.5-0ubuntu0.1 ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15 Uname: Linux 4.4.0-34-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AssertionMessage: *** Error in `/usr/bin/gnome-shell': free(): invalid pointer: 0x082dcf30 *** CrashCounter: 1 CurrentDesktop: GNOME Date: Wed Aug 24 16:21:37 2016 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2014-10-24 (670 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Signal: 6SourcePackage: gnome-shell StacktraceTop: __libc_message (do_abort=do_abort@entry=2, fmt=fmt@entry=0x7fabad1e06b0 "*** Error in `%s': %s: 0x%s ***\n") at ../sysdeps/posix/libc_fatal.c:175 malloc_printerr (ar_ptr=, ptr=, str=0x7fabad1dd48f "free(): invalid pointer", action=3) at malloc.c:5007 _int_free (av=, p=, have_lock=0) at malloc.c:3868 __GI___libc_free (mem=) at malloc.c:2969 g_strfreev () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: gnome-shell assert failure: *** Error in `/usr/bin/gnome-shell': free(): invalid pointer: 0x082dcf30 *** UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo XsessionErrors: x-session-manager[7610]: CRITICAL: We failed, but the fail whale is dead. Sorry x-session-manager[14832]: CRITICAL: We failed, but the fail whale is dead. Sorry x-session-manager[5188]: CRITICAL: We failed, but the fail whale is dead. Sorry To manage notifications about this bug go to: https://bugs.launchpad.net/libgweather/+bug/1616651/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1694179] [NEW] package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128
Public bug reported: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 ProblemType: Package DistroRelease: Ubuntu 17.04 Package: gconf2-common 3.2.6-3ubuntu7 ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11 Uname: Linux 4.10.0-21-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 Date: Sun May 28 21:46:28 2017 ErrorMessage: subprocess installed post-installation script returned error exit status 128 InstallationDate: Installed on 2017-05-28 (0 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4 SourcePackage: gconf Title: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gconf (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package need-duplicate-check zesty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gconf in Ubuntu. https://bugs.launchpad.net/bugs/1694179 Title: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 Status in gconf package in Ubuntu: New Bug description: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 ProblemType: Package DistroRelease: Ubuntu 17.04 Package: gconf2-common 3.2.6-3ubuntu7 ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11 Uname: Linux 4.10.0-21-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 Date: Sun May 28 21:46:28 2017 ErrorMessage: subprocess installed post-installation script returned error exit status 128 InstallationDate: Installed on 2017-05-28 (0 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4 SourcePackage: gconf Title: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1694179/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1654448] Re: XPS 13 9360 and 9350, Realtek ALC3246, Headphone audio hiss
@kaihengfeng: I found the problem was only really noticeable with earbuds. Headphones tended to hide the problem. Although it's also worth noting the workaround 'amixer -c 0 set 'Headphone Mic Boost',0 1' sounds like it's working because it actually reduces the audio output volume/gain. With the workaround enabled, ALL audio is quieter so (like using big headphones) the problem could become unnoticeable just because of that. So saying the problem and the solution are directly related to 'Headphone Mic Boost' might be a red herring. -- 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/1654448 Title: XPS 13 9360 and 9350, Realtek ALC3246, Headphone audio hiss Status in Dell Sputnik: New Status in alsa-driver package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: Pertaining to 16.04 on a dell XPS 13 9360 ii alsa-base 1.0.25+dfsg-0ubuntu5 Advanced Linux Sound Architecture Driver Version k4.4.0-57-generic. When headphones are plugged in, there is a clearly audible hiss (white noise). This is present as soon as the headphones are plugged in, whether 'headphones' or 'headset' are selected from the pop-up box. Using alsamixer to debug the issue reveals that it is related to "Headphone Mic Boost" - the default setting is: dB gain 0.00, 0.00. If this is changed to: 10.00, 10.00 (one notch up) the hiss disappears. 20.00, 20.00 cause a louder hiss and 30.00, 30.00 causes an even louder hiss with high frequency audio artifacts. When the headphones are removed and plugged back in the Headphone Mic Boost setting returns to dB gain 0 and the problem also returns. This (problem and workaround) has been reported in the wild: https://news.ycombinator.com/item?id=13050843 and https://www.reddit.com/r/Dell/comments/4j1zz4/headphones_have_static_noise_with_ubuntu_1604_on/ for example To manage notifications about this bug go to: https://bugs.launchpad.net/dell-sputnik/+bug/1654448/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1628474] Re: keyboard keys in GtkShortcuts should have different color than background
Yes, sorry, you are right. It's still broken in 'menu > Keyboard Shortcuts'. I was looking in 'menu > Help > Advanced > Keyboard shortcuts' where the keys look fine. Same app, different help screen. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1628474 Title: keyboard keys in GtkShortcuts should have different color than background Status in ubuntu-themes package in Ubuntu: Confirmed Bug description: Many GNOME apps have a new Keyboard Shortcuts popup window available in their app menu (this feature was introduced in GTK 3.20). Ambiance and Radiance don't style this window correctly - there's no contrast between the displayed keyboard keys and the background. I'm attaching screenshots of evince's Keyboard Shortcuts popup (available in Help > Keyboard Shortcuts) with Ambiance and Adwaita. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1628474/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 405294] Re: A2DP Bluetooth audio skips terribly ["Skipping NNN us (= MMM bytes) in audio stream"]
** Summary changed: - A2DP Bluetooth audio skips terribly + A2DP Bluetooth audio skips terribly ["Skipping NNN us (= MMM bytes) in audio stream"] -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/405294 Title: A2DP Bluetooth audio skips terribly ["Skipping NNN us (= MMM bytes) in audio stream"] Status in PulseAudio: Confirmed Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: As I upgraded to the Karmic alpha, bluetooth audio (via a2dp) stopped working properly. It was working fine in Jaunty. My headphones are detected and configured by pulse, but the audio skips as if it's spending half of each second paused. Music is buffered so that after I click stop on rhythmbox (or whatever--it happens with whatever player I use) the audio continues until it's caught up. syslog is full of the following lines: Jul 27 08:55:45 carlin1 pulseaudio[3218]: alsa-source.c: Increasing minimal latency to 1.00 ms Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 15128 us (= 2668 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 36586 us (= 6452 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 35593 us (= 6276 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 36597 us (= 6452 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 32601 us (= 5748 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 32589 us (= 5748 bytes) in audio stream This is with bluez 4.45-0ubuntu4 pulseaudio1:0.9.15-4ubuntu2 0 pulseaudio version 1:0.9.16~test2-0ubuntu1~ppa3 from ubuntu-audio-dev didn't help. To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/405294/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1616695] Re: Bluetooth signal is unusably poor
*** This bug is a duplicate of bug 405294 *** https://bugs.launchpad.net/bugs/405294 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 405294, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 405294 A2DP Bluetooth audio skips terribly -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1616695 Title: Bluetooth signal is unusably poor Status in bluez package in Ubuntu: Confirmed Bug description: Brand new Macbook Pro 12,1. Brand new Ubuntu 16.04 install (from scratch). In MacOS the machine can connect to my bluetooth speaker from across the room and play A2DP no trouble at all. In Ubuntu 16.04 I have to literally hold up the macbook 1 inch away from the speaker to get it to connect and play, and even then it's a bit choppy. Turning off Wifi seems to help a bit, which leads me to think this is some kind of transmit power issue. Syslog is chock full of warnings about skipping audio: Aug 24 16:22:32 badassm pulseaudio[4655]: [bluetooth] module-bluez5-device.c: Skipping 206099 us (= 36352 bytes) in audio stream Aug 24 16:22:32 badassm pulseaudio[4655]: [bluetooth] module-bluez5-device.c: Skipping 382089 us (= 67400 bytes) in audio stream Aug 24 16:22:33 badassm pulseaudio[4655]: [bluetooth] module-bluez5-device.c: Skipping 394108 us (= 69520 bytes) in audio stream Aug 24 16:22:33 badassm pulseaudio[4655]: [bluetooth] module-bluez5-device.c: Skipping 328125 us (= 57880 bytes) in audio stream Aug 24 16:22:33 badassm pulseaudio[4655]: [bluetooth] module-bluez5-device.c: Skipping 59087 us (= 10420 bytes) in audio stream Aug 24 16:22:33 badassm pulseaudio[4655]: [bluetooth] module-bluez5-device.c: Skipping 14036 us (= 2472 bytes) in audio stream Aug 24 16:22:34 badassm pulseaudio[4655]: [bluetooth] module-bluez5-device.c: Skipping 247134 us (= 43592 bytes) in audio stream Aug 24 16:22:34 badassm pulseaudio[4655]: [bluetooth] module-bluez5-device.c: Skipping 342190 us (= 60360 bytes) in audio stream Aug 24 16:22:34 badassm pulseaudio[4655]: [bluetooth] module-bluez5-device.c: Skipping 172035 us (= 30344 bytes) in audio stream Aug 24 16:22:35 badassm pulseaudio[4655]: [bluetooth] module-bluez5-device.c: Skipping 803140 us (= 141672 bytes) in audio stream Aug 24 16:22:36 badassm pulseaudio[4655]: [bluetooth] module-bluez5-device.c: Skipping 651085 us (= 114848 bytes) in audio stream Aug 24 16:22:36 badassm pulseaudio[4655]: [bluetooth] module-bluez5-device.c: Skipping 202043 us (= 35640 bytes) in audio stream Aug 24 16:22:36 badassm pulseaudio[4655]: [bluetooth] module-bluez5-device.c: Skipping 265112 us (= 46764 bytes) in audio stream $ cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=16.04 DISTRIB_CODENAME=xenial DISTRIB_DESCRIPTION="Ubuntu 16.04.1 LTS" $ uname -a Linux badassm 4.4.0-34-generic #53-Ubuntu SMP Wed Jul 27 16:06:39 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux $ lsusb Bus 002 Device 002: ID 05ac:8406 Apple, Inc. Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 05ac:0273 Apple, Inc. Bus 001 Device 003: ID 05ac:8290 Apple, Inc. Bus 001 Device 006: ID 045e:00db Microsoft Corp. Natural Ergonomic Keyboard 4000 V1.0 Bus 001 Device 005: ID 05e3:0608 Genesys Logic, Inc. Hub Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub $ hciconfig hci0: Type: BR/EDR Bus: USB BD Address: 98:01:A7:A8:D4:6A ACL MTU: 1021:8 SCO MTU: 64:1 UP RUNNING PSCAN RX bytes:5198 acl:2 sco:0 events:269 errors:0 TX bytes:7021 acl:2 sco:0 commands:218 errors:0 [bluetooth]# show Controller 98:01:A7:A8:D4:6A Name: badassm Alias: badassm Class: 0x1c010c Powered: yes Discoverable: no Pairable: yes UUID: Headset AG(1112--1000-8000-00805f9b34fb) UUID: Generic Attribute Profile (1801--1000-8000-00805f9b34fb) UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb) UUID: OBEX File Transfer(1106--1000-8000-00805f9b34fb) UUID: Generic Access Profile(1800--1000-8000-00805f9b34fb) UUID: OBEX Object Push (1105--1000-8000-00805f9b34fb) UUID: PnP Information (1200--1000-8000-00805f9b34fb) UUID: A/V Remote Control Tar
[Touch-packages] [Bug 1520615] Re: Use of Ubuntu logo as default app icon dilutes the brand
** Changed in: ubuntu-themes (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1520615 Title: Use of Ubuntu logo as default app icon dilutes the brand Status in Canonical System Image: Confirmed Status in Click Package Index: Invalid Status in Snap Store: Triaged Status in Software Center Agent: Invalid Status in ubuntu-sdk-ide package in Ubuntu: New Status in ubuntu-themes package in Ubuntu: Confirmed Status in ubuntu-touch-meta package in Ubuntu: New Bug description: Currently, MyApps and CPI are using the "placeholder-app-icon.png" from the Suru theme, which is a basic greyscale image, including a version of the Ubuntu logo. Showing this logo as the app icon for apps which have no icon, implies they are officially supported apps by Ubuntu, and dilutes the brand and trademark, when they are not actually such apps, particularly when they have no function directly linked to any part of Ubuntu. Instead, a better representation would be a generic representation of an app window or similar. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1520615/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1553669] Re: Annoying call from message
** Tags added: wily xenial ** Changed in: bluez (Ubuntu) Status: Incomplete => Confirmed ** Summary changed: - Annoying call from message + Annoying "call from" message -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1553669 Title: Annoying "call from" message Status in bluez package in Ubuntu: Confirmed Bug description: I have a bluetooth Bose OE SoundLink working on Kubuntu 15.10 but each time I initially connect to listen to an audio or video, I hear an annoying "Call from" on my headset. My headset seems to think a connection to a phone call is taking place. This is annoying because the audio will start to play and after a little while the "call from" voice talks over the audio. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1553669/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1630850] Re: package initramfs-tools 0.125ubuntu3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
This just occurred for me after using tasksel to switch from Ubuntu Mate to Xubuntu. I simply deselected one, waited for the process to finish, then reinstalled and re-ran tasksel. I did get an intitramfs related error when reinstalling tassel, but I ignored it and continued to install Xubuntu. Xubuntu seemed to install successfully with no errors, and I am currently using it to type this note. The error occurred immediately after logging into the new Xubuntu installation. I know nothing else. Cheers! -- 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/1630850 Title: package initramfs-tools 0.125ubuntu3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in initramfs-tools package in Ubuntu: Confirmed Bug description: Plugged a Logitech wireless mouse dongle into a USB3 port ProblemType: Package DistroRelease: Ubuntu 16.10 Package: initramfs-tools 0.125ubuntu3 ProcVersionSignature: Ubuntu 4.8.0-14.15-generic 4.8.0-rc7 Uname: Linux 4.8.0-14-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 AptOrdering: NULL: ConfigurePending Architecture: amd64 Date: Wed Oct 5 19:27:14 2016 DpkgTerminalLog: Setting up initramfs-tools (0.125ubuntu3) ... sudoupdate-initramfs: deferring update (trigger activated) cp: cannot create regular file '/cdrom/casper/initrd.gz.new': No such file or directory dpkg: error processing package initramfs-tools (--configure): subprocess installed post-installation script returned error exit status 1 ErrorMessage: subprocess installed post-installation script returned error exit status 1 PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.10ubuntu1 apt 1.3~rc4ubuntu1 SourcePackage: initramfs-tools Title: package initramfs-tools 0.125ubuntu3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1630850/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1479030] Re: unity-system-compositor crashes with SIGABRT in google::protobuf::internal::LogMessage::Finish
Confirmed on 17.04, repeatedly. ** Changed in: unity-system-compositor Status: Expired => Confirmed ** Changed in: unity-system-compositor (Ubuntu) Status: Expired => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-system-compositor in Ubuntu. https://bugs.launchpad.net/bugs/1479030 Title: unity-system-compositor crashes with SIGABRT in google::protobuf::internal::LogMessage::Finish Status in Unity System Compositor: Confirmed Status in unity-system-compositor package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding unity-system-compositor. This problem was most recently seen with version 0.0.5+15.10.20150722-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/17e8c095201d404cdb3a785f4870e95f200fea1d contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/unity-system-compositor/+bug/1479030/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1680957] Re: [Inspiron 5559] No sound at all
** Summary changed: - [Inspiron 5559, Intel Skylake HDMI, Digital Out, HDMI] No sound at all + [Inspiron 5559] No sound at all -- 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/1680957 Title: [Inspiron 5559] No sound at all Status in pulseaudio package in Ubuntu: Confirmed Bug description: missing audio output ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: pulseaudio 1:8.0-0ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: shaon 3414 F pulseaudio CurrentDesktop: Unity Date: Sat Apr 8 02:26:22 2017 InstallationDate: Installed on 2017-04-07 (0 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: pulseaudio Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: shaon 3414 F pulseaudio Symptom_Jack: Digital Out, HDMI Symptom_PulsePlaybackTest: PulseAudio playback test failed Symptom_Type: No sound at all Title: [Inspiron 5559, Intel Skylake HDMI, Digital Out, HDMI] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/08/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.8 dmi.board.name: 0664DJ dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.8:bd02/08/2017:svnDellInc.:pnInspiron5559:pvr:rvnDellInc.:rn0664DJ:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.name: Inspiron 5559 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1680957/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1694047] Re: [Inspiron 5559, Realtek ALC3234, Speaker, Internal] No sound at all
*** This bug is a duplicate of bug 1680957 *** https://bugs.launchpad.net/bugs/1680957 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1680957, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1680957 [Inspiron 5559] No sound at all -- 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/1694047 Title: [Inspiron 5559, Realtek ALC3234, Speaker, Internal] No sound at all Status in pulseaudio package in Ubuntu: New Bug description: After upgrading from ubuntu 16.10 to 17.04, my laptop sound system is not working. How to fix? Please give some solutions. Thanks ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: pulseaudio 1:10.0-1ubuntu2 ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11 Uname: Linux 4.10.0-21-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: hemant 2325 F pulseaudio CurrentDesktop: Unity:Unity7 Date: Sat May 27 21:10:46 2017 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-osp1-20150720-0 InstallationDate: Installed on 2016-10-14 (225 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20150720-04:06 SourcePackage: pulseaudio Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: hemant 2325 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_PulsePlaybackTest: PulseAudio playback test failed Symptom_Type: No sound at all Title: [Inspiron 5559, Realtek ALC3234, Speaker, Internal] No sound at all UpgradeStatus: Upgraded to zesty on 2017-05-26 (0 days ago) dmi.bios.date: 06/08/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.1 dmi.board.name: 07JM0H dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.1:bd06/08/2016:svnDellInc.:pnInspiron5559:pvr:rvnDellInc.:rn07JM0H:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Inspiron 5559 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1694047/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1693850] Re: libzen wasn't compiled with large file support
** Description changed: - The switch to cmake caused two compilation flags to be accidentally dropped: + The switch to cmake caused two compilation flags to be accidentally dropped: -D_LARGE_FILES -D_FILE_OFFSET_BITS=64 This causes all file-handling operations in zenlib to fail to work with - large files. This affects the following reverse-dependencies: + large files on 32-bit machines. This affects the following reverse- + dependencies: - libmediainfo - mediainfo - mediaconch This has been fixed in https://github.com/MediaArea/ZenLib/commit/dc105b3ed035413577d21c979d1998d889350855. + + [Test Case] + + Run `mediainfo $filename` where $filename is a file that is larger than + 4.2GB. Output will be missing if this bug is present. + + [Regression Potential] + + Quite low, since the only thing that's changed here are some -D + compilation flags that aren't even directly referenced in the codebase. ** Description changed: + [Impact] + The switch to cmake caused two compilation flags to be accidentally dropped: -D_LARGE_FILES -D_FILE_OFFSET_BITS=64 This causes all file-handling operations in zenlib to fail to work with large files on 32-bit machines. This affects the following reverse- dependencies: - libmediainfo - mediainfo - mediaconch This has been fixed in https://github.com/MediaArea/ZenLib/commit/dc105b3ed035413577d21c979d1998d889350855. [Test Case] Run `mediainfo $filename` where $filename is a file that is larger than 4.2GB. Output will be missing if this bug is present. [Regression Potential] Quite low, since the only thing that's changed here are some -D compilation flags that aren't even directly referenced in the codebase. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libzen in Ubuntu. https://bugs.launchpad.net/bugs/1693850 Title: libzen wasn't compiled with large file support Status in libzen package in Ubuntu: Fix Released Status in libzen source package in Xenial: Triaged Status in libzen source package in Yakkety: Triaged Status in libzen source package in Zesty: Triaged Status in libzen source package in Artful: Fix Released Bug description: [Impact] The switch to cmake caused two compilation flags to be accidentally dropped: -D_LARGE_FILES -D_FILE_OFFSET_BITS=64 This causes all file-handling operations in zenlib to fail to work with large files on 32-bit machines. This affects the following reverse-dependencies: - libmediainfo - mediainfo - mediaconch This has been fixed in https://github.com/MediaArea/ZenLib/commit/dc105b3ed035413577d21c979d1998d889350855. [Test Case] Run `mediainfo $filename` where $filename is a file that is larger than 4.2GB. Output will be missing if this bug is present. [Regression Potential] Quite low, since the only thing that's changed here are some -D compilation flags that aren't even directly referenced in the codebase. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libzen/+bug/1693850/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1693819] Re: dhclient DHCPv6 does not work with interface alias
** Changed in: isc-dhcp (Debian) Status: Unknown => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1693819 Title: dhclient DHCPv6 does not work with interface alias Status in isc-dhcp package in Ubuntu: New Status in isc-dhcp source package in Trusty: New Status in isc-dhcp source package in Xenial: New Status in isc-dhcp source package in Yakkety: New Status in isc-dhcp source package in Zesty: New Status in isc-dhcp source package in Artful: New Status in isc-dhcp package in Debian: New Bug description: [Impact] The isc-dhcp-client dhclient program does not work with interface alias names, e.g. eth0:1. It fails immediately. [Test Case] On trusty through artful, find an interface that is connected to a network that has a DHCPv6 server on it. First verify it can get a DHCPv6 address, e.g.: $ sudo dhclient -6 -v ens7 that should successfully set up a DHCPv6 address on the interface. Then release the interface: $ sudo dhclient -6 -v -r ens7 Now, try again but use the interface alias, e.g.: $ sudo dhclient -6 -v ens7:1 It should succeed, but it will fail with: no link-local IPv6 address for ens7:1 [Regression Potential] Changing how isc-dhcp handles (enumerates/lists/compares) interface names may lead to isc-dhcp using the wrong interface or failing to find the correct interface to use. However, if the only change is to strip the alias part from the interface during comparison, the possibility of error should be small, since all interface aliases point back to the same physical interface. [Other Info] This bug exists in the upstream isc-dhcp; the ISC has no public bug tracker, and only accepts bug reports via private email, which has been sent. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1693819/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1694063] Re: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gconf (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gconf in Ubuntu. https://bugs.launchpad.net/bugs/1694063 Title: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 Status in gconf package in Ubuntu: Confirmed Bug description: i think this bug came up when i restarted my laptop after i tried to install chrome from the official site and it got stuck saying installing and it never installed ProblemType: Package DistroRelease: Ubuntu 17.04 Package: gconf2-common 3.2.6-3ubuntu7 ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11 Uname: Linux 4.10.0-21-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 Date: Sat May 27 21:56:41 2017 ErrorMessage: subprocess installed post-installation script returned error exit status 128 InstallationDate: Installed on 2017-05-27 (0 days ago) InstallationMedia: Lubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4 SourcePackage: gconf Title: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1694063/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1616695] Re: Bluetooth signal is unusably poor
Such a pain this one! not an Ubuntu specific issue as so many other people have already confirmed! I could reproduce it on a debian (jessie). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1616695 Title: Bluetooth signal is unusably poor Status in bluez package in Ubuntu: Confirmed Bug description: Brand new Macbook Pro 12,1. Brand new Ubuntu 16.04 install (from scratch). In MacOS the machine can connect to my bluetooth speaker from across the room and play A2DP no trouble at all. In Ubuntu 16.04 I have to literally hold up the macbook 1 inch away from the speaker to get it to connect and play, and even then it's a bit choppy. Turning off Wifi seems to help a bit, which leads me to think this is some kind of transmit power issue. Syslog is chock full of warnings about skipping audio: Aug 24 16:22:32 badassm pulseaudio[4655]: [bluetooth] module-bluez5-device.c: Skipping 206099 us (= 36352 bytes) in audio stream Aug 24 16:22:32 badassm pulseaudio[4655]: [bluetooth] module-bluez5-device.c: Skipping 382089 us (= 67400 bytes) in audio stream Aug 24 16:22:33 badassm pulseaudio[4655]: [bluetooth] module-bluez5-device.c: Skipping 394108 us (= 69520 bytes) in audio stream Aug 24 16:22:33 badassm pulseaudio[4655]: [bluetooth] module-bluez5-device.c: Skipping 328125 us (= 57880 bytes) in audio stream Aug 24 16:22:33 badassm pulseaudio[4655]: [bluetooth] module-bluez5-device.c: Skipping 59087 us (= 10420 bytes) in audio stream Aug 24 16:22:33 badassm pulseaudio[4655]: [bluetooth] module-bluez5-device.c: Skipping 14036 us (= 2472 bytes) in audio stream Aug 24 16:22:34 badassm pulseaudio[4655]: [bluetooth] module-bluez5-device.c: Skipping 247134 us (= 43592 bytes) in audio stream Aug 24 16:22:34 badassm pulseaudio[4655]: [bluetooth] module-bluez5-device.c: Skipping 342190 us (= 60360 bytes) in audio stream Aug 24 16:22:34 badassm pulseaudio[4655]: [bluetooth] module-bluez5-device.c: Skipping 172035 us (= 30344 bytes) in audio stream Aug 24 16:22:35 badassm pulseaudio[4655]: [bluetooth] module-bluez5-device.c: Skipping 803140 us (= 141672 bytes) in audio stream Aug 24 16:22:36 badassm pulseaudio[4655]: [bluetooth] module-bluez5-device.c: Skipping 651085 us (= 114848 bytes) in audio stream Aug 24 16:22:36 badassm pulseaudio[4655]: [bluetooth] module-bluez5-device.c: Skipping 202043 us (= 35640 bytes) in audio stream Aug 24 16:22:36 badassm pulseaudio[4655]: [bluetooth] module-bluez5-device.c: Skipping 265112 us (= 46764 bytes) in audio stream $ cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=16.04 DISTRIB_CODENAME=xenial DISTRIB_DESCRIPTION="Ubuntu 16.04.1 LTS" $ uname -a Linux badassm 4.4.0-34-generic #53-Ubuntu SMP Wed Jul 27 16:06:39 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux $ lsusb Bus 002 Device 002: ID 05ac:8406 Apple, Inc. Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 05ac:0273 Apple, Inc. Bus 001 Device 003: ID 05ac:8290 Apple, Inc. Bus 001 Device 006: ID 045e:00db Microsoft Corp. Natural Ergonomic Keyboard 4000 V1.0 Bus 001 Device 005: ID 05e3:0608 Genesys Logic, Inc. Hub Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub $ hciconfig hci0: Type: BR/EDR Bus: USB BD Address: 98:01:A7:A8:D4:6A ACL MTU: 1021:8 SCO MTU: 64:1 UP RUNNING PSCAN RX bytes:5198 acl:2 sco:0 events:269 errors:0 TX bytes:7021 acl:2 sco:0 commands:218 errors:0 [bluetooth]# show Controller 98:01:A7:A8:D4:6A Name: badassm Alias: badassm Class: 0x1c010c Powered: yes Discoverable: no Pairable: yes UUID: Headset AG(1112--1000-8000-00805f9b34fb) UUID: Generic Attribute Profile (1801--1000-8000-00805f9b34fb) UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb) UUID: OBEX File Transfer(1106--1000-8000-00805f9b34fb) UUID: Generic Access Profile(1800--1000-8000-00805f9b34fb) UUID: OBEX Object Push (1105--1000-8000-00805f9b34fb) UUID: PnP Information (1200--1000-8000-00805f9b34fb) UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb) UUID: IrMC Sync (1104--1000-8000-00805f9b34fb) UUID: Audio Sink(110b--1000-8000-00805f9b34fb) UUID: Audio Source (110a--1000-8000-00805f9b34fb) UUID: Vendor specific (5005--1000-8000-0002ee01) UUID: Message Notification Se.. (1133--1000-8000-00805f9b34fb) UUID: Phonebook Access Server (112f--1000-8000-00805f9b34fb) UUID: Messa
[Touch-packages] [Bug 1694156] Re: systemd-resolved and libvirt dnsmasq instance get into a busy loop when a query is issued for a URI or SRV record
Trying to understand why the dnsmasq is registered in /etc/resolv.conf at all, I find that it's listed in /etc/resolvconf/resolv.conf.d/tail. So 192.168.122.1 being listed as a global DNS server is a result of local configuration, which means this problem is at least partly self- inflicted. If I remove this from /etc/resolvconf/resolv.conf.d/tail and restart systemd-resolved, I no longer see 192.168.122.1 listed at all in systemd-resolve --status. So there is no longer any DNS loop; OTOH, I also no longer get DNS resolution of the names of my VMs. While this works around the original symptom (which is still a bug somewhere, due to the correct handling of A/CNAME/MX but wrong handling of SRV/URI), there also needs to be a proper way to register libvirt's dnsmasq as an auxiliary DNS server for the VMs. -- 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/1694156 Title: systemd-resolved and libvirt dnsmasq instance get into a busy loop when a query is issued for a URI or SRV record Status in dnsmasq package in Ubuntu: New Status in libvirt package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: I have a zesty system that uses systemd-resolved, as per default, which also has dnsmasq configured for use on interface virbr0 for my libvirt bridge. This system is also part of a Kerberos realm. Recent versions of Kerberos do a lookup of a URI RR, à la: $ nslookup -q=URI _kerberos.dodds.net Server: 127.0.0.53 Address: 127.0.0.53#53 Non-authoritative answer: *** Can't find _kerberos.dodds.net: No answer Authoritative answers can be found from: $ There is no URI DNS record published for this domain, so the lack of response is correct. However, systemd-resolved and dnsmasq then get in a busy loop, passing the same query back and forth between each other. (Confirmed with wireshark.) If I query SRV records under the same domain (which is also part of what kerberos does), these positive results are correctly returned to the client, but systemd-resolved and dnsmasq again get into a busy loop. If I query a URI record for a domain /other than/ what I have configured as my DNS search domain, there is no busy loop. If I query other kinds of records (whether they return results or not), such as A, CNAME, and MX records, there is no busy loop. /etc/resolv.conf looks like: # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8) # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN # 127.0.0.53 is the systemd-resolved stub resolver. # run "systemd-resolve --status" to see details about the actual nameservers. domain dodds.net search dodds.net nameserver 127.0.0.53 nameserver 192.168.122.1 systemd-resolve says: $ systemd-resolve --status Global DNS Servers: 192.168.122.1 DNS Domain: dodds.net DNSSEC NTA: 10.in-addr.arpa 16.172.in-addr.arpa 168.192.in-addr.arpa 17.172.in-addr.arpa 18.172.in-addr.arpa 19.172.in-addr.arpa 20.172.in-addr.arpa 21.172.in-addr.arpa 22.172.in-addr.arpa 23.172.in-addr.arpa 24.172.in-addr.arpa 25.172.in-addr.arpa 26.172.in-addr.arpa 27.172.in-addr.arpa 28.172.in-addr.arpa 29.172.in-addr.arpa 30.172.in-addr.arpa 31.172.in-addr.arpa corp d.f.ip6.arpa home internal intranet lan local private test [...] Link 2 (wlan2) Current Scopes: DNS LLMNR/IPv4 LLMNR/IPv6 LLMNR setting: yes MulticastDNS setting: no DNSSEC setting: no DNSSEC supported: no DNS Servers: 192.168.0.1 DNS Domain: dodds.net $ I'm not sure where this bug lies. Both DNS servers are by design configured not to cache results, in order to avoid cache poisoning and information leaks, so neither DNS server can detect that they've already asked for the record and don't need to recurse. I think it's probably a bug for dnsmasq to be configured as a server for resolving 'dodds.net' - I have nowhere specified that this is appropriate and this potentially conflicts with legitimate records in this domain. But it also must be a bug that SRV/URI records result in recursion but A/CNAME/MX records do not. To manage notifications about
[Touch-packages] [Bug 1694156] [NEW] systemd-resolved and libvirt dnsmasq instance get into a busy loop when a query is issued for a URI or SRV record
Public bug reported: I have a zesty system that uses systemd-resolved, as per default, which also has dnsmasq configured for use on interface virbr0 for my libvirt bridge. This system is also part of a Kerberos realm. Recent versions of Kerberos do a lookup of a URI RR, à la: $ nslookup -q=URI _kerberos.dodds.net Server: 127.0.0.53 Address:127.0.0.53#53 Non-authoritative answer: *** Can't find _kerberos.dodds.net: No answer Authoritative answers can be found from: $ There is no URI DNS record published for this domain, so the lack of response is correct. However, systemd-resolved and dnsmasq then get in a busy loop, passing the same query back and forth between each other. (Confirmed with wireshark.) If I query SRV records under the same domain (which is also part of what kerberos does), these positive results are correctly returned to the client, but systemd-resolved and dnsmasq again get into a busy loop. If I query a URI record for a domain /other than/ what I have configured as my DNS search domain, there is no busy loop. If I query other kinds of records (whether they return results or not), such as A, CNAME, and MX records, there is no busy loop. /etc/resolv.conf looks like: # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8) # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN # 127.0.0.53 is the systemd-resolved stub resolver. # run "systemd-resolve --status" to see details about the actual nameservers. domain dodds.net search dodds.net nameserver 127.0.0.53 nameserver 192.168.122.1 systemd-resolve says: $ systemd-resolve --status Global DNS Servers: 192.168.122.1 DNS Domain: dodds.net DNSSEC NTA: 10.in-addr.arpa 16.172.in-addr.arpa 168.192.in-addr.arpa 17.172.in-addr.arpa 18.172.in-addr.arpa 19.172.in-addr.arpa 20.172.in-addr.arpa 21.172.in-addr.arpa 22.172.in-addr.arpa 23.172.in-addr.arpa 24.172.in-addr.arpa 25.172.in-addr.arpa 26.172.in-addr.arpa 27.172.in-addr.arpa 28.172.in-addr.arpa 29.172.in-addr.arpa 30.172.in-addr.arpa 31.172.in-addr.arpa corp d.f.ip6.arpa home internal intranet lan local private test [...] Link 2 (wlan2) Current Scopes: DNS LLMNR/IPv4 LLMNR/IPv6 LLMNR setting: yes MulticastDNS setting: no DNSSEC setting: no DNSSEC supported: no DNS Servers: 192.168.0.1 DNS Domain: dodds.net $ I'm not sure where this bug lies. Both DNS servers are by design configured not to cache results, in order to avoid cache poisoning and information leaks, so neither DNS server can detect that they've already asked for the record and don't need to recurse. I think it's probably a bug for dnsmasq to be configured as a server for resolving 'dodds.net' - I have nowhere specified that this is appropriate and this potentially conflicts with legitimate records in this domain. But it also must be a bug that SRV/URI records result in recursion but A/CNAME/MX records do not. ** Affects: dnsmasq (Ubuntu) Importance: Undecided Status: New ** Affects: libvirt (Ubuntu) Importance: Undecided Status: New ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Also affects: dnsmasq (Ubuntu) Importance: Undecided Status: New ** Also affects: libvirt (Ubuntu) Importance: Undecided Status: New ** Summary changed: - systemd-resolved and libvirt dnsmasq instance get into a busy loop when a query is issued for a URI record + systemd-resolved and libvirt dnsmasq instance get into a busy loop when a query is issued for a URI or SRV record -- 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/1694156 Title: systemd-resolved and libvirt dnsmasq instance get into a busy loop when a query is issued for a URI or SRV record Status in dnsmasq package in Ubuntu: New Status in libvirt package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: I have a zesty system that uses systemd-resolved, as per default, which also has dnsmasq configured for use on interface virbr0 for my libvirt bridge. This system is also part of a Kerberos realm. Recent versions of Kerberos do a lookup of a URI RR, à la: $ nslookup -q=URI _kerberos.dodds.net Server: 127.0.0.53 Address:
[Touch-packages] [Bug 1692561] Re: Version 4.5 has been released
This is not an Ubuntu GNOME issue. ** No longer affects: ubuntu-gnome -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to shadow in Ubuntu. https://bugs.launchpad.net/bugs/1692561 Title: Version 4.5 has been released Status in shadow package in Ubuntu: New Bug description: Version 4.5 has just been released so it would be nice to get it into the repositories some time soon: https://github.com/shadow- maint/shadow/releases/tag/4.5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1692561/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1692561] Re: Version 4.5 has been released
** Also affects: ubuntu-gnome Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to shadow in Ubuntu. https://bugs.launchpad.net/bugs/1692561 Title: Version 4.5 has been released Status in Ubuntu GNOME: New Status in shadow package in Ubuntu: New Bug description: Version 4.5 has just been released so it would be nice to get it into the repositories some time soon: https://github.com/shadow- maint/shadow/releases/tag/4.5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-gnome/+bug/1692561/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1100546] Re: Power indicator favours 'not present' mouse over laptop battery level
Ping! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-power in Ubuntu. https://bugs.launchpad.net/bugs/1100546 Title: Power indicator favours 'not present' mouse over laptop battery level Status in indicator-power package in Ubuntu: Fix Released Status in indicator-power source package in Xenial: New Bug description: [Impact] * It's very annoying to see the mouse battery instead of the system battery on indicator bar. [Test Case] * Using Logitech Wireless Mouse M325 or other wireless mouse can see this issue. [Regression Potential] * No regression as I know. [Other Info] * This is a SRU request for Ubuntu 16.04 (xenial). The power indicator shows the battery level for cordless mice and keyboards, even when it cannot identify the battery level. This is a problem as it seems to favour showing a "not present" mouse status over the laptop battery level in the top bar. I haven't done a good job of explaining it, so check out the screenshot - it will explain all :) Basically, the laptop battery should be shown in the top bar if the mouse/keyboard is "not present". Also hiding the mouse and keyboard when the battery level is unknown would also be useful too :) ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: indicator-power 12.10.6daily12.11.21.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-0.3-generic 3.8.0-rc3 Uname: Linux 3.8.0-0-generic x86_64 ApportVersion: 2.8-0ubuntu1 Architecture: amd64 Date: Thu Jan 17 10:11:16 2013 InstallationDate: Installed on 2012-12-14 (33 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20121214) MarkForUpload: True SourcePackage: indicator-power UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1100546/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1670036] Re: Misapplied patches in 4.0.6-2ubuntu0.1 break reading and writing JPEG compressed files
** Summary changed: - Misapplied patches in 4.0.6-2ubuntu01 break reading and writing JPEG compressed files + Misapplied patches in 4.0.6-2ubuntu0.1 break reading and writing JPEG compressed files ** Changed in: tiff (Ubuntu) Assignee: (unassigned) => Marc Deslauriers (mdeslaur) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tiff in Ubuntu. https://bugs.launchpad.net/bugs/1670036 Title: Misapplied patches in 4.0.6-2ubuntu0.1 break reading and writing JPEG compressed files Status in LibTIFF: New Status in tiff package in Ubuntu: Confirmed Bug description: The patches applied to libtiff 4.0.6 in 4.0.6-2ubuntu01 seem to break JPEG tiff read and write. To reproduce: $ tiffcp -c jpeg k2a.tif x.tif (where k2a.tif is a simple uncompressed RGB strip tiff) appears to work. However, x.tif, the output, will now not read without warnings: $ tiffcp x.tif y.tif TIFFFetchNormalTag: Warning, ASCII value for tag "JPEGTables" does not end in null byte. Forcing it to be null. JPEGLib: Warning, Premature end of JPEG file. This was working fine until a couple of days ago, so I guess it's one of the most recent patches. Some packages using libtiff seem to be broken too. For example, openslide, which uses libtiff to load jp2k-compressed slide images, is no longer working: $ openslide-write-png CMU-1-Small-Region.svs 0 0 0 100 100 x.png TIFFFetchNormalTag: Warning, ASCII value for tag "JPEGTables" does not end in null byte. Forcing it to be null. TIFFFetchNormalTag: Warning, ASCII value for tag "JPEGTables" does not end in null byte. Forcing it ... repeats 8 more times openslide-write-png: Premature end of JPEG file and x.png is not a valid PNG image. The test .svs image may be downloaded here: http://openslide.cs.cmu.edu/download/openslide-testdata/Aperio/ To manage notifications about this bug go to: https://bugs.launchpad.net/libtiff/+bug/1670036/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1694149] [NEW] ssl error using urllib2
Public bug reported: On Ubuntu 14.04.5 LTS with python 2.7.5-5ubuntu3 and libpython2.7-stdlib 2.7.6-8ubuntu0.3, using this little example program: #!/usr/bin/python import urllib2 USER_AGENT = 'Mozilla/5.0 (Windows NT 6.3; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/41.0.2272.101 Safari/537.36' defaultHeaders = {'User-Agent':USER_AGENT, 'Accept':"text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,*/*;q=0.8", 'Accept-Encoding':'gzip,deflate,sdch', 'Accept-Language':'en-US,en;q=0.8'} url = "https://ga.video.cdn.pbs.org/videos/ask-old-house/dcf0b26c-f7d1-4b1f-b1cf-2e521aa5e796/110577/hd-mezzanine-16x9/zq3zp3pg_ask1524-cove-16x9-hls-192-2500k.m3u8"; req = urllib2.Request(url.encode('utf-8'), None, defaultHeaders) response = urllib2.urlopen(req, timeout=30) I get this result: $ python /tmp/urllib2-error.py Traceback (most recent call last): File "/tmp/urllib2-error.py", line 15, in response = urllib2.urlopen(req, timeout=30) File "/usr/lib/python2.7/urllib2.py", line 127, in urlopen return _opener.open(url, data, timeout) File "/usr/lib/python2.7/urllib2.py", line 404, in open response = self._open(req, data) File "/usr/lib/python2.7/urllib2.py", line 422, in _open '_open', req) File "/usr/lib/python2.7/urllib2.py", line 382, in _call_chain result = func(*args) File "/usr/lib/python2.7/urllib2.py", line 1222, in https_open return self.do_open(httplib.HTTPSConnection, req) File "/usr/lib/python2.7/urllib2.py", line 1184, in do_open raise URLError(err) urllib2.URLError: ** Affects: python-defaults (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-defaults in Ubuntu. https://bugs.launchpad.net/bugs/1694149 Title: ssl error using urllib2 Status in python-defaults package in Ubuntu: New Bug description: On Ubuntu 14.04.5 LTS with python 2.7.5-5ubuntu3 and libpython2.7-stdlib 2.7.6-8ubuntu0.3, using this little example program: #!/usr/bin/python import urllib2 USER_AGENT = 'Mozilla/5.0 (Windows NT 6.3; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/41.0.2272.101 Safari/537.36' defaultHeaders = {'User-Agent':USER_AGENT, 'Accept':"text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,*/*;q=0.8", 'Accept-Encoding':'gzip,deflate,sdch', 'Accept-Language':'en-US,en;q=0.8'} url = "https://ga.video.cdn.pbs.org/videos/ask-old-house/dcf0b26c-f7d1-4b1f-b1cf-2e521aa5e796/110577/hd-mezzanine-16x9/zq3zp3pg_ask1524-cove-16x9-hls-192-2500k.m3u8"; req = urllib2.Request(url.encode('utf-8'), None, defaultHeaders) response = urllib2.urlopen(req, timeout=30) I get this result: $ python /tmp/urllib2-error.py Traceback (most recent call last): File "/tmp/urllib2-error.py", line 15, in response = urllib2.urlopen(req, timeout=30) File "/usr/lib/python2.7/urllib2.py", line 127, in urlopen return _opener.open(url, data, timeout) File "/usr/lib/python2.7/urllib2.py", line 404, in open response = self._open(req, data) File "/usr/lib/python2.7/urllib2.py", line 422, in _open '_open', req) File "/usr/lib/python2.7/urllib2.py", line 382, in _call_chain result = func(*args) File "/usr/lib/python2.7/urllib2.py", line 1222, in https_open return self.do_open(httplib.HTTPSConnection, req) File "/usr/lib/python2.7/urllib2.py", line 1184, in do_open raise URLError(err) urllib2.URLError: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-defaults/+bug/1694149/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1694147] [NEW] el sistema operativo no carga correctamente
Public bug reported: el mismo error en el arranque del grub ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.8.0-53.56~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-53-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Sun May 28 13:42:22 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Skylake Integrated Graphics [1043:12a0] InstallationDate: Installed on 2017-05-12 (16 days ago) InstallationMedia: Ubuntu-GNOME 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 13d3:3414 IMC Networks Bus 001 Device 003: ID 0bda:57de Realtek Semiconductor Corp. Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. X441UA ProcEnviron: LANGUAGE=es_CO:es PATH=(custom, no user) LANG=es_CO.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-53-generic root=UUID=a7a8e101-a485-4ef5-ba0b-926df14f3b42 ro vesafb.invalid=1 pci=nomsi Renderer: Software SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/13/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X441UA.305 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X441UA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX441UA.305:bd09/13/2016:svnASUSTeKCOMPUTERINC.:pnX441UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX441UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: X441UA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-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: Fri May 12 07:39:17 2017 xserver.configfile: default xserver.errors: open /dev/dri/card0: No such file or directory open /dev/dri/card0: No such file or directory Screen 0 deleted because of no matching config section. AIGLX: reverting to software rendering xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.18.4-1ubuntu6.1~16.04.1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug 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/1694147 Title: el sistema operativo no carga correctamente Status in xorg package in Ubuntu: New Bug description: el mismo error en el arranque del grub ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.8.0-53.56~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-53-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Sun May 28 13:42:22 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Skylake Integrated Graphics [1043:12a0] InstallationDate: Installed on 2017-05-12 (16 days ago) InstallationMedia: Ubuntu-GNOME 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 13d3:3414 IMC Networks Bus 001 Device 003: ID 0bda:57de Realtek Semiconductor Corp. Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. X441UA ProcEnviron: LANGUAGE=es_CO:es PATH=(custom, no user
[Touch-packages] [Bug 882825] Re: Does not save the configuration file under ~/.config/
https://git.gnome.org/browse/gegl/commit/?id=751218ccfe ** Changed in: gegl (Ubuntu) Status: New => Fix Released ** Changed in: gnome-games (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bash in Ubuntu. https://bugs.launchpad.net/bugs/882825 Title: Does not save the configuration file under ~/.config/ Status in The Gimp: Fix Released Status in adobe-flashplugin package in Ubuntu: New Status in bash package in Ubuntu: New Status in bzr package in Ubuntu: Fix Released Status in compiz package in Ubuntu: Confirmed Status in dbus package in Ubuntu: New Status in dia package in Ubuntu: New Status in gconf package in Ubuntu: Triaged Status in gegl package in Ubuntu: Fix Released Status in gimp package in Ubuntu: Confirmed Status in gl-117 package in Ubuntu: New Status in gnome-games package in Ubuntu: Fix Released Status in gnupg package in Ubuntu: New Status in gvfs package in Ubuntu: Confirmed Status in hydrogen package in Ubuntu: New Status in nautilus package in Ubuntu: Triaged Status in onboard package in Ubuntu: Fix Released Status in python-launchpadlib package in Ubuntu: Invalid Status in shotwell package in Ubuntu: Fix Released Status in synaptic package in Ubuntu: Triaged Status in thunderbird package in Ubuntu: New Status in w3m package in Ubuntu: New Status in xchat package in Ubuntu: Triaged Bug description: It does not save the configuration file(s) and/or the cache under the right location for configuration file storage which is under ~/.config/ and ~/.cache/ To manage notifications about this bug go to: https://bugs.launchpad.net/gimp/+bug/882825/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1553669] Re: Annoying call from message
I can confirm that its still exists in ubuntu 16.04 (well kubuntu 16.04 - but i guess that bluetooth is the same) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1553669 Title: Annoying call from message Status in bluez package in Ubuntu: Incomplete Bug description: I have a bluetooth Bose OE SoundLink working on Kubuntu 15.10 but each time I initially connect to listen to an audio or video, I hear an annoying "Call from" on my headset. My headset seems to think a connection to a phone call is taking place. This is annoying because the audio will start to play and after a little while the "call from" voice talks over the audio. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1553669/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1694133] [NEW] package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128
Public bug reported: Please fix it, It crashes suddenly in my system i.e. Dell inspiron 3542!! ProblemType: Package DistroRelease: Ubuntu 17.04 Package: gconf2-common 3.2.6-3ubuntu7 ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11 Uname: Linux 4.10.0-21-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 Date: Sun May 28 20:38:06 2017 ErrorMessage: subprocess installed post-installation script returned error exit status 128 InstallationDate: Installed on 2017-05-28 (0 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4 SourcePackage: gconf Title: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gconf (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package need-duplicate-check zesty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gconf in Ubuntu. https://bugs.launchpad.net/bugs/1694133 Title: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 Status in gconf package in Ubuntu: New Bug description: Please fix it, It crashes suddenly in my system i.e. Dell inspiron 3542!! ProblemType: Package DistroRelease: Ubuntu 17.04 Package: gconf2-common 3.2.6-3ubuntu7 ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11 Uname: Linux 4.10.0-21-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 Date: Sun May 28 20:38:06 2017 ErrorMessage: subprocess installed post-installation script returned error exit status 128 InstallationDate: Installed on 2017-05-28 (0 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4 SourcePackage: gconf Title: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1694133/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1685186] Re: [SRU] Mir needs to be updated to 0.26 in 16.04LTS
** Changed in: mir (Ubuntu) Status: Fix Released => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1685186 Title: [SRU] Mir needs to be updated to 0.26 in 16.04LTS Status in mir package in Ubuntu: In Progress Status in mir source package in Xenial: Incomplete Bug description: [Impact] Snap development using Mir has been using the "stable phone overlay" PPA which is both inconvenient and a legacy of the cancelled Unity8 project. It would greatly simplify things if Mir were updated in the Xenial archive. [Test Case] Build a Mir client snap (e.g. lp:~albaguirre/+snap/mir-client-demos) against "Primary Ubuntu Archive" and deploy as described in https://developer.ubuntu.com/en/snappy/guides/mir-snaps/ Expected: the client apps start and are visible on screen Actual: the client apps don't start and are not visible on screen [Regression Potential] Mir has two categories of dependent project: 1 Unity8 and unity-system-compositor "server" packages 2 toolkits and other "clients" of Mir "Server" packages from the archive will stop working in the LTS as they will continue using the earlier libmirserver.so.38 (from Mir 0.21) which doesn't work with the libmirclient.so.9 from Mir 0.26. This is unimportant as these packages were provided as an "early experience", not for serious use. "Client" packages are dependent only on libmirclient.so.9 which is ABI stable. The principle type of regression would be FTBFS where APIs have been deprecated in 0.26. The linked 0.26.3 release has these deprecations disabled for 16.04. The packages are available in silo: https://bileto.ubuntu.com/#/ticket/2736 notes: A recursive search or rdependencies identifies the following packages in category 1: camera-app-autopilot gallery-app-autopilot indicator-network-autopilot indicators-client qtdeclarative5-qtmir-plugin qtmir-android qtmir-desktop qtmir-tests ubuntu-desktop-mir ubuntu-experience-tests ubuntu-pocket-desktop ubuntu-push-autopilot ubuntu-touch ubuntu-touch-session unity8 unity8-autopilot unity8-desktop-session-mir unity-scope-click-autopilot unity-system-compositor unity-system-compositor-autopilot Anyone wanting these packages should switch to the "unity8-desktop- session" preview package in 17.04 where they are far more functional. [Alternatives] If we want to keep everything working in Xenial, we *could* bump the libmirclient SONAME to libmirclient.so.10. This would result in libmirclient9 being NBS, but continuing to work against the Mir servers available in 16.04[*] (until and unless they are rebuilt). However, this does not enable the desired result for IoT deployments of toolkits (GTK, Qt etc) and other clients working against servers (specifically miral-kiosk) built against the updated libraries. To work for IoT these would need to rebuilt from source - at which point they (and their dependencies) would stop working against the servers in category 1. [*] with the exception of the servers provided in mir-examples, these would only work with clients linking against libmirclient.so.10. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mir/+bug/1685186/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1694131] [NEW] problème cart graphique
Public bug reported: Problème avec carte graphique radéon HD 5000 cherche pilote. Merci ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62 Uname: Linux 4.4.0-78-generic i686 .tmp.unity_support_test.1: ApportVersion: 2.20.1-0ubuntu2.6 Architecture: i386 BootLog: /dev/sda1: clean, 231682/30269440 files, 3997297/121047808 blocks [[0m[0;31m* [0m] (1 of 7) A start job is running for Network Manager (21s / 1min 43s) CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Sun May 28 16:40:08 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Cedar [Radeon HD 5000/6000/7350/8350 Series] [1002:68f9] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Radeon HD 5450 [1043:0386] InstallationDate: Installed on 2017-05-21 (6 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1) MachineType: System manufacturer System Product Name ProcEnviron: LANGUAGE=fr_FR PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-78-generic root=UUID=58213a0b-ae70-4cbf-92f9-7f61e83b1926 ro nomodeset splash quiet nopat vesafb.invalid=1 Renderer: Software SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/11/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0602 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5KPL-AM SE dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0602:bd09/11/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5KPL-AMSE:rvrX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Sun May 28 16:11:57 2017 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputLITEON Technology USB Keyboard KEYBOARD, id 8 inputLITEON Technology USB Keyboard KEYBOARD, id 9 inputLogitech Optical USB Mouse MOUSE, id 10 xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-0ubuntu0.2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug compiz-0.9 i386 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/1694131 Title: problème cart graphique Status in xorg package in Ubuntu: New Bug description: Problème avec carte graphique radéon HD 5000 cherche pilote. Merci ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62 Uname: Linux 4.4.0-78-generic i686 .tmp.unity_support_test.1: ApportVersion: 2.20.1-0ubuntu2.6 Architecture: i386 BootLog: /dev/sda1: clean, 231682/30269440 files, 3997297/121047808 blocks [[0m[0;31m* [0m] (1 of 7) A start job is running for Network Manager (21s / 1min 43s) CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Sun May 28 16:40:08 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Cedar [Radeon HD 5000/6000/7350/8350 Series] [1002:68f9] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Radeon HD 5450 [1043:0386] InstallationDate: Installed on
[Touch-packages] [Bug 1675357] Re: Mir sending key repeat events continually to nested shell after VT switch (causes Unity8 lockup for a while)
This bug was fixed in the package mir - 0.26.3+17.10.20170526.3-0ubuntu1 --- mir (0.26.3+17.10.20170526.3-0ubuntu1) artful; urgency=medium [ Daniel van Vugt ] * New upstream release 0.26.3 (https://launchpad.net/mir/+milestone/0.26.3) - Enhancements: . Make deprecations optional (and default to off for builds on 16.04 LTS) . Added support for building on Ubuntu 17.10 artful. - Bugs fixed: . Mir needs to be updated to 0.26 in 16.04LTS (LP: #1685186) . unity-system-compositor crashed with SIGSEGV in libinput_device_config_accel_is_available() from libinput_device_config_accel_set_speed() from mir::input::evdev::LibInputDevice::apply_settings() (LP: #1672955) . Please transition to Boost 1.62 (LP: #1675138) . Mir sending key repeat events continually to nested shell after VT switch (causes Unity8 lockup for a while) (LP: #1675357) . mir_demo_standalone_render_overlays fails to link (LP: #1677239) -- Alan Griffiths Fri, 26 May 2017 16:57:20 + ** Changed in: mir (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1675357 Title: Mir sending key repeat events continually to nested shell after VT switch (causes Unity8 lockup for a while) Status in Canonical System Image: In Progress Status in Mir: Fix Committed Status in Mir 0.26 series: Fix Committed Status in mir package in Ubuntu: Fix Released Status in qtmir package in Ubuntu: Invalid Status in unity8 package in Ubuntu: Invalid Status in mir source package in Xenial: Fix Committed Status in qtmir source package in Xenial: Invalid Status in unity8 source package in Xenial: Invalid Bug description: Steps: * log in to unity8 * Ctrl+Alt+F* to a different vt, or log in to a different user session * go back to the unity8 vt Expected: * session is locked, but working Current: * unity8 starts spinning for a time proportional to the period it was inactive * if it was inactive long enough, it doesn't seem to recover at all It seems it's "catching up" in some way, maybe with input, maybe frames. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: unity8 8.15+17.04.20170321-0ubuntu1 [origin: LP-PPA-ci-train-ppa-service-2555] ProcVersionSignature: Ubuntu 4.10.0-13.15-generic 4.10.1 Uname: Linux 4.10.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity:Unity7 Date: Thu Mar 23 11:36:39 2017 InstallationDate: Installed on 2016-05-06 (320 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: unity8 UpgradeStatus: Upgraded to zesty on 2016-11-22 (120 days ago) Causes: The mir::input::KeyRepeatDispatcher is running inside the nested mirserver even though there is another instance running inside the host server. A few months ago qtmir used to replace the key repeater by replacing mirs dispatcher. And key repeat is not disabled within the nested server. So both the host and the nested server are producing repeat events. Now due to a logic error inside mirserver the key repeat dispatcher is not hooked up to the input device hub when running inside the nested server. The input device hub would tell the key repeater when devices get removed - i.e. due to vt switching. So it never notices that the devices go away continues to produce those events indefinitely. This applies to all currently pressed buttons. I.e. you can open an edit field and press 'w' while simultaneously pressing Ctrl+Alt+FX to switch to another VT. On return 'w' will be repeated indefinitely. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1675357/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1685186] Re: [SRU] Mir needs to be updated to 0.26 in 16.04LTS
This bug was fixed in the package mir - 0.26.3+17.10.20170526.3-0ubuntu1 --- mir (0.26.3+17.10.20170526.3-0ubuntu1) artful; urgency=medium [ Daniel van Vugt ] * New upstream release 0.26.3 (https://launchpad.net/mir/+milestone/0.26.3) - Enhancements: . Make deprecations optional (and default to off for builds on 16.04 LTS) . Added support for building on Ubuntu 17.10 artful. - Bugs fixed: . Mir needs to be updated to 0.26 in 16.04LTS (LP: #1685186) . unity-system-compositor crashed with SIGSEGV in libinput_device_config_accel_is_available() from libinput_device_config_accel_set_speed() from mir::input::evdev::LibInputDevice::apply_settings() (LP: #1672955) . Please transition to Boost 1.62 (LP: #1675138) . Mir sending key repeat events continually to nested shell after VT switch (causes Unity8 lockup for a while) (LP: #1675357) . mir_demo_standalone_render_overlays fails to link (LP: #1677239) -- Alan Griffiths Fri, 26 May 2017 16:57:20 + ** Changed in: mir (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 mir in Ubuntu. https://bugs.launchpad.net/bugs/1685186 Title: [SRU] Mir needs to be updated to 0.26 in 16.04LTS Status in mir package in Ubuntu: Fix Released Status in mir source package in Xenial: Incomplete Bug description: [Impact] Snap development using Mir has been using the "stable phone overlay" PPA which is both inconvenient and a legacy of the cancelled Unity8 project. It would greatly simplify things if Mir were updated in the Xenial archive. [Test Case] Build a Mir client snap (e.g. lp:~albaguirre/+snap/mir-client-demos) against "Primary Ubuntu Archive" and deploy as described in https://developer.ubuntu.com/en/snappy/guides/mir-snaps/ Expected: the client apps start and are visible on screen Actual: the client apps don't start and are not visible on screen [Regression Potential] Mir has two categories of dependent project: 1 Unity8 and unity-system-compositor "server" packages 2 toolkits and other "clients" of Mir "Server" packages from the archive will stop working in the LTS as they will continue using the earlier libmirserver.so.38 (from Mir 0.21) which doesn't work with the libmirclient.so.9 from Mir 0.26. This is unimportant as these packages were provided as an "early experience", not for serious use. "Client" packages are dependent only on libmirclient.so.9 which is ABI stable. The principle type of regression would be FTBFS where APIs have been deprecated in 0.26. The linked 0.26.3 release has these deprecations disabled for 16.04. The packages are available in silo: https://bileto.ubuntu.com/#/ticket/2736 notes: A recursive search or rdependencies identifies the following packages in category 1: camera-app-autopilot gallery-app-autopilot indicator-network-autopilot indicators-client qtdeclarative5-qtmir-plugin qtmir-android qtmir-desktop qtmir-tests ubuntu-desktop-mir ubuntu-experience-tests ubuntu-pocket-desktop ubuntu-push-autopilot ubuntu-touch ubuntu-touch-session unity8 unity8-autopilot unity8-desktop-session-mir unity-scope-click-autopilot unity-system-compositor unity-system-compositor-autopilot Anyone wanting these packages should switch to the "unity8-desktop- session" preview package in 17.04 where they are far more functional. [Alternatives] If we want to keep everything working in Xenial, we *could* bump the libmirclient SONAME to libmirclient.so.10. This would result in libmirclient9 being NBS, but continuing to work against the Mir servers available in 16.04[*] (until and unless they are rebuilt). However, this does not enable the desired result for IoT deployments of toolkits (GTK, Qt etc) and other clients working against servers (specifically miral-kiosk) built against the updated libraries. To work for IoT these would need to rebuilt from source - at which point they (and their dependencies) would stop working against the servers in category 1. [*] with the exception of the servers provided in mir-examples, these would only work with clients linking against libmirclient.so.10. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mir/+bug/1685186/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1672955] Re: unity-system-compositor crashed with SIGSEGV in libinput_device_config_accel_is_available() from libinput_device_config_accel_set_speed() from mir::input::evdev::Lib
This bug was fixed in the package mir - 0.26.3+17.10.20170526.3-0ubuntu1 --- mir (0.26.3+17.10.20170526.3-0ubuntu1) artful; urgency=medium [ Daniel van Vugt ] * New upstream release 0.26.3 (https://launchpad.net/mir/+milestone/0.26.3) - Enhancements: . Make deprecations optional (and default to off for builds on 16.04 LTS) . Added support for building on Ubuntu 17.10 artful. - Bugs fixed: . Mir needs to be updated to 0.26 in 16.04LTS (LP: #1685186) . unity-system-compositor crashed with SIGSEGV in libinput_device_config_accel_is_available() from libinput_device_config_accel_set_speed() from mir::input::evdev::LibInputDevice::apply_settings() (LP: #1672955) . Please transition to Boost 1.62 (LP: #1675138) . Mir sending key repeat events continually to nested shell after VT switch (causes Unity8 lockup for a while) (LP: #1675357) . mir_demo_standalone_render_overlays fails to link (LP: #1677239) -- Alan Griffiths Fri, 26 May 2017 16:57:20 + ** Changed in: mir (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1672955 Title: unity-system-compositor crashed with SIGSEGV in libinput_device_config_accel_is_available() from libinput_device_config_accel_set_speed() from mir::input::evdev::LibInputDevice::apply_settings() Status in Canonical System Image: Fix Committed Status in Mir: Fix Committed Status in Mir 0.26 series: Fix Committed Status in Unity System Compositor: Invalid Status in mir package in Ubuntu: Fix Released Status in unity-system-compositor package in Ubuntu: Invalid Status in mir source package in Xenial: Fix Committed Status in unity-system-compositor source package in Xenial: Invalid Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding unity-system-compositor. This problem was most recently seen with package version 0.9.1+17.04.20170216-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/fcf5550475fb0478d6eb2a307f03705ef1ed398a 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 you can request it at http://forms.canonical.com/reports/. It seems that the configuration change is requested just a moment before the device gets removed. The change actions are serialized, depending on where there memory of mir::input::DefaultDevice is allocated the segfault either occurs inside the lambda or inside underlying mir::input::LibInputDevice in the platform. The activities on input dispatch device removal and reconfiguration are serialized inside the input thread, so we just need to clean the action queue (or have multiple queues) before removing the devices. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1672955/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1677239] Re: mir_demo_standalone_render_overlays fails to link
This bug was fixed in the package mir - 0.26.3+17.10.20170526.3-0ubuntu1 --- mir (0.26.3+17.10.20170526.3-0ubuntu1) artful; urgency=medium [ Daniel van Vugt ] * New upstream release 0.26.3 (https://launchpad.net/mir/+milestone/0.26.3) - Enhancements: . Make deprecations optional (and default to off for builds on 16.04 LTS) . Added support for building on Ubuntu 17.10 artful. - Bugs fixed: . Mir needs to be updated to 0.26 in 16.04LTS (LP: #1685186) . unity-system-compositor crashed with SIGSEGV in libinput_device_config_accel_is_available() from libinput_device_config_accel_set_speed() from mir::input::evdev::LibInputDevice::apply_settings() (LP: #1672955) . Please transition to Boost 1.62 (LP: #1675138) . Mir sending key repeat events continually to nested shell after VT switch (causes Unity8 lockup for a while) (LP: #1675357) . mir_demo_standalone_render_overlays fails to link (LP: #1677239) -- Alan Griffiths Fri, 26 May 2017 16:57:20 + ** Changed in: mir (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1677239 Title: mir_demo_standalone_render_overlays fails to link Status in Mir: Fix Committed Status in Mir 0.26 series: Fix Committed Status in mir package in Ubuntu: Fix Released Status in mir source package in Xenial: Fix Committed Bug description: https://mir-jenkins.ubuntu.com/job/build-2-binpkg- mir/arch=amd64,compiler=gcc,platform=mesa,release=zesty/4453/console 11:41:20 [ 52%] Linking CXX executable ../../../../bin/mir_demo_standalone_render_overlays.bin 11:41:20 cd /<>/mir-0.26.1+17.04.20170209.1+zesty4503bzr4124/obj-x86_64-linux-gnu/src/platforms/android/utils && /usr/bin/cmake -E cmake_link_script CMakeFiles/mir_demo_standalone_render_overlays.dir/link.txt --verbose=1 11:41:20 /usr/lib/ccache/c++ -g -O2 -fdebug-prefix-map=/<>/mir-0.26.1+17.04.20170209.1+zesty4503bzr4124=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -pthread -g -std=c++14 -Werror -Wall -fno-strict-aliasing -pedantic -Wnon-virtual-dtor -Wextra -fPIC -flto -ffat-lto-objects -Wl,-Bsymbolic-functions -Wl,-z,relro -Wl,--as-needed -Wl,--no-undefined CMakeFiles/mir_demo_standalone_render_overlays.dir/render_overlays.cpp.o -o ../../../../bin/mir_demo_standalone_render_overlays.bin -rdynamic ../../../../lib/libmirplatform.so.16 ../../../../lib/libmircommon.so.7 ../../../capnproto/libmircapnproto.a -lkj -lcapnp ../../../../lib/libmircore.so.1 -lboost_date_time -lboost_system -lboost_program_options -lboost_filesystem -ldl -lEGL -lGLESv2 -lGLESv2 -L/lib/x86_64-linux-gnu -ludev -ludev 11:41:21 //usr/lib/x86_64-linux-gnu/libmirclient.so.9: undefined reference to `MirInputDeviceStateEvent::device_pressed_keys_for_index(unsigned long, unsigned long) const@MIR_COMMON_0.25_PRIVATE' 11:41:21 //usr/lib/x86_64-linux-gnu/libmirclient.so.9: undefined reference to `MirPointerEvent::set_x(float)@MIR_COMMON_0.25_PRIVATE' 11:41:21 //usr/lib/x86_64-linux-gnu/libmirclient.so.9: undefined reference to `MirTouchEvent::pressure(unsigned long) const@MIR_COMMON_0.25_PRIVATE' To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1677239/+subscriptions -- Mailing list: https://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 1693944] Re: package openssh-server 1:7.2p2-4ubuntu2.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Hello Seth, Thank you so much for your fast response! I think that I found the error on line 64...It used to say: X11 Forwarding I think that because there was no "yes" or "no," that's why the error came up I added "yes" and now everything seems to be working fine. Have a wonderful weekend and thank you again--I've never had a major problem like this before and I wasn't sure if anyone would respond at all, but you did and your reply was extremely helpful! Best wishes Emily > On May 26, 2017, at 8:12 PM, Seth Arnold <1693...@bugs.launchpad.net> wrote: > > Hello, one of your logs indicates a problem: > > /etc/ssh/sshd_config line 64: miss... > > Sadly the actual error has been left out of the logs. But hopefully you > can spot what's wrong on line 64. > > Thanks > > ** Attachment removed: "DpkgTerminalLog.txt" > > https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1693944/+attachment/4884332/+files/DpkgTerminalLog.txt > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1693944 > > Title: > package openssh-server 1:7.2p2-4ubuntu2.2 failed to install/upgrade: > subprocess installed post-installation script returned error exit > status 1 > > Status in openssh package in Ubuntu: > New > > Bug description: > I was doing a normal update and got this error message at the end. > > I'm new to Ubuntu and I honestly don't know what the problem could be. > I've not had problems with OpenSSH before > > ProblemType: Package > DistroRelease: Ubuntu 16.04 > Package: openssh-server 1:7.2p2-4ubuntu2.2 > ProcVersionSignature: Ubuntu 4.4.0-77.98-generic 4.4.59 > Uname: Linux 4.4.0-77-generic x86_64 > ApportVersion: 2.20.1-0ubuntu2.6 > Architecture: amd64 > Date: Fri May 26 18:39:19 2017 > ErrorMessage: subprocess installed post-installation script returned error > exit status 1 > InstallationDate: Installed on 2016-10-06 (232 days ago) > InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 > (20160719) > RelatedPackageVersions: > dpkg 1.18.4ubuntu1.2 > apt 1.2.20 > SourcePackage: openssh > Title: package openssh-server 1:7.2p2-4ubuntu2.2 failed to install/upgrade: > subprocess installed post-installation script returned error exit status 1 > UpgradeStatus: No upgrade log present (probably fresh install) > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1693944/+subscriptions -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1693944 Title: package openssh-server 1:7.2p2-4ubuntu2.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in openssh package in Ubuntu: New Bug description: I was doing a normal update and got this error message at the end. I'm new to Ubuntu and I honestly don't know what the problem could be. I've not had problems with OpenSSH before ProblemType: Package DistroRelease: Ubuntu 16.04 Package: openssh-server 1:7.2p2-4ubuntu2.2 ProcVersionSignature: Ubuntu 4.4.0-77.98-generic 4.4.59 Uname: Linux 4.4.0-77-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 Date: Fri May 26 18:39:19 2017 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2016-10-06 (232 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: openssh Title: package openssh-server 1:7.2p2-4ubuntu2.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1693944/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1693895] Re: ubuntu budgie suspend to ram fails on Macbook Pro Ret
This seems the normal case --- May 28 12:37:49 mbpr15 systemd[1]: Started Suspend. May 28 12:37:49 mbpr15 systemd[1]: sleep.target: Unit not needed anymore. Stoppi ng. May 28 12:37:49 mbpr15 systemd[1]: Stopped target Sleep. May 28 12:37:49 mbpr15 systemd[1]: tlp-sleep.service: Unit not needed anymore. S topping. May 28 12:37:49 mbpr15 systemd[1]: Stopping TLP suspend/resume... May 28 12:37:49 mbpr15 systemd[1]: Reached target Suspend. May 28 12:37:49 mbpr15 systemd[1]: suspend.target: Unit is bound to inactive uni t systemd-suspend.service. Stopping, too. May 28 12:37:49 mbpr15 systemd[1]: Stopped target Suspend. May 28 12:37:49 mbpr15 systemd[1]: Started Run anacron jobs at resume. --- -- 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/1693895 Title: ubuntu budgie suspend to ram fails on Macbook Pro Ret Status in systemd package in Ubuntu: New Bug description: A default installation of Ubuntu Budgie fails to suspend to RAM. Workaround: sudo apt-get install pm-utils => Suspend works ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: systemd 232-21ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11 Uname: Linux 4.10.0-21-generic x86_64 NonfreeKernelModules: wl nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 CurrentDesktop: Budgie:GNOME Date: Fri May 26 20:13:16 2017 InstallationDate: Installed on 2017-05-25 (0 days ago) InstallationMedia: Ubuntu-Budgie 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: Apple Inc. MacBookPro10,1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-21-generic.efi.signed root=UUID=873566f9-4c01-4dae-8ca9-99c95dfbe269 ro quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/21/2012 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP101.88Z.00EE.B03.1212211437 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-C3EC7CD22292981F dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro10,1 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-C3EC7CD22292981F dmi.modalias: dmi:bvnAppleInc.:bvrMBP101.88Z.00EE.B03.1212211437:bd12/21/2012:svnAppleInc.:pnMacBookPro10,1:pvr1.0:rvnAppleInc.:rnMac-C3EC7CD22292981F:rvrMacBookPro10,1:cvnAppleInc.:ct10:cvrMac-C3EC7CD22292981F: dmi.product.name: MacBookPro10,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1693895/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1689825] Re: gnome-keyring not unlocked on boot
same for me here by starting with the terminal $google-chrome [6136:6136:0528/125519.901742:ERROR:browser_main_loop.cc(279)] Gtk: Im Modulpfad »adwaita« konnte keine Themen-Engine gefunden werden, [6136:6136:0528/125519.902002:ERROR:browser_main_loop.cc(279)] Gtk: Im Modulpfad »adwaita« konnte keine Themen-Engine gefunden werden, Gkr-Message: secret service operation failed: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. Gkr-Message: secret service operation failed: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. [6136:6136:0528/125701.104195:ERROR:CONSOLE(0)] "Error in event handler for (unknown): TypeError: Cannot read property 'id' of undefined at inject_code (chrome-extension://mhcmfkkjmkcfgelgdpndepmimbmkbpfp/js/cs_inject.js:17:13)", source: https://www.google.de/_/chrome/newtab?espv=2&ie=UTF-8 (0) after $sudo apt install gnome-themes-standard I got less error messages but still a long delay $ google-chrome Gkr-Message: secret service operation failed: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. Gkr-Message: secret service operation failed: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. from post #17 I tried this $ google-chrome --password-store=basic And the browser started immediately :-D -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libgnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1689825 Title: gnome-keyring not unlocked on boot Status in gnome-keyring package in Ubuntu: Confirmed Status in libgnome-keyring package in Ubuntu: Confirmed Bug description: 1) Release: 16.04.2 2) gnome-keyring: 3.18.3-0ubuntu2 3) Login. gnome-keyring unlocks "login" features including for google chrome 4) gnome-keyring is not unlocked, chrome takes 2 minutes to open and with no secure password features(sync) functioning. For the past couple days, chrome on Ubuntu 16.04 takes a REALLY long time (maybe 2 minutes) to start. Once chrome is started, I am not able to sync and any secure password features are broken. I found out this is due to gnome-keyring not being unlocked at login. There's also no way to unlock the "login" portion of the keyring from the running daemon by default. I have to kill the gnome-keyring process and start without "--login" as a parameter. Then the "login" section shows up which I'm able to unlock. From there chrome starts up instantly but asks the following: Enter password to unlock your login keyring The login keyring did not get unlocked when you logged into your computer After that, all of it's sync and secure features are functional. Starting google-chrome-stable from a command line at boot without running the above workaround shows the following error messages: Gkr-Message: secret service operation failed: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. Gkr-Message: secret service operation failed: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. [4364:4393:0510/100407.740292:ERROR:token_service_table.cc(130)] Failed to decrypt token for service AccountId-108842767310111573264 [4364:4445:0510/100407.740292:ERROR:gcm_store_impl.cc(929)] Failed to restore security token. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gnome-keyring 3.18.3-0ubuntu2 ProcVersionSignature: Ubuntu 4.8.0-52.55~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-52-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: GNOME-Flashback:Unity Date: Wed May 10 09:43:37 2017 SourcePackage: gnome-keyring UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1689825/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1693895] Re: ubuntu budgie suspend to ram fails on Macbook Pro Ret
Was a bit euphoric about the workaround. Suspend does not work even with pm-utils installed. The machine blanks the display but other than that works continuously. With the lid closed, the laptop might overheat. So this issue is endangering the hardware. Current workaround: Don't suspend, turn off. -- 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/1693895 Title: ubuntu budgie suspend to ram fails on Macbook Pro Ret Status in systemd package in Ubuntu: New Bug description: A default installation of Ubuntu Budgie fails to suspend to RAM. Workaround: sudo apt-get install pm-utils => Suspend works ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: systemd 232-21ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11 Uname: Linux 4.10.0-21-generic x86_64 NonfreeKernelModules: wl nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 CurrentDesktop: Budgie:GNOME Date: Fri May 26 20:13:16 2017 InstallationDate: Installed on 2017-05-25 (0 days ago) InstallationMedia: Ubuntu-Budgie 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: Apple Inc. MacBookPro10,1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-21-generic.efi.signed root=UUID=873566f9-4c01-4dae-8ca9-99c95dfbe269 ro quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/21/2012 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP101.88Z.00EE.B03.1212211437 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-C3EC7CD22292981F dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro10,1 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-C3EC7CD22292981F dmi.modalias: dmi:bvnAppleInc.:bvrMBP101.88Z.00EE.B03.1212211437:bd12/21/2012:svnAppleInc.:pnMacBookPro10,1:pvr1.0:rvnAppleInc.:rnMac-C3EC7CD22292981F:rvrMacBookPro10,1:cvnAppleInc.:ct10:cvrMac-C3EC7CD22292981F: dmi.product.name: MacBookPro10,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1693895/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1694109] [NEW] X server freezes with all NVIDIA open source driver releases (340.102, 375.66, 381.22)
Public bug reported: Hello, I have Dell XPX L502X with Nvidia GT 540M card i.e. 6 years old hardware whose driver is still not working, this is amazing :( The X server freezes with all NVIDIA open source driver releases (340.102, 375.66, 381.22). This report is for NVIDIA driver version 340.102. X Server freezes at any time keyboard and mouse hangs and last resort used to be to power down with power key forcefully which may destroy HDD also :( I even tried proprietary NVIDIA drivers also but they had shown the same behaviour. Without the NVIDIA drivers in place I can't use CUDA toolkit. Please let me know if someone need any further info apart from attached file. Thanks Br aksgaur ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11 Uname: Linux 4.8.0-36-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.102 Mon Jan 16 13:06:29 PST 2017 GCC version: gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4) .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Sun May 28 11:42:45 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.8.0-36-generic, x86_64: installed bbswitch, 0.8, 4.8.0-53-generic, x86_64: installed nvidia-340, 340.102, 4.8.0-36-generic, x86_64: installed nvidia-340, 340.102, 4.8.0-53-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell 2nd Generation Core Processor Family Integrated Graphics Controller [1028:050e] NVIDIA Corporation GF108M [GeForce GT 540M] [10de:0df4] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell GF108M [GeForce GT 540M] [1028:050e] InstallationDate: Installed on 2017-05-01 (26 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) MachineType: Dell Inc. Dell System XPS L502X ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-36-generic root=UUID=e35ef27e-882a-4ccf-9430-7246671359cb ro rootflags=subvol=@ quiet splash SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/07/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A12 dmi.board.name: 0NJT03 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA12:bd09/07/2012:svnDellInc.:pnDellSystemXPSL502X:pvr:rvnDellInc.:rn0NJT03:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: Dell System XPS L502X dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A 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 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug possible-manual-nvidia-install 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/1694109 Title: X server freezes with all NVIDIA open source driver releases (340.102, 375.66, 381.22) Status in xorg package in Ubuntu: New Bug description: Hello, I have Dell XPX L502X with Nvidia GT 540M card i.e. 6 years old hardware whose driver is still not working, this is amazing :( The X server freezes with all NVIDIA open source driver releases (340.102, 375.66, 381.22). This report is for NVIDIA driver version 340.102. X Server freezes at any time keyboard and mouse hangs and last resort used to be to power down with power key forcefully which may destroy HDD also :( I even tried proprietary NVIDIA drivers also but they had shown the same behaviour. Without the NVIDIA drivers in place I can't use CUDA toolkit. Please let me know if someone need any further info apart from attached file. Thanks Br aksgaur ProblemType: Bug
[Touch-packages] [Bug 1670036] Re: Misapplied patches in 4.0.6-2ubuntu01 break reading and writing JPEG compressed files
** Information type changed from Public to Public Security ** Tags added: regression-update -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tiff in Ubuntu. https://bugs.launchpad.net/bugs/1670036 Title: Misapplied patches in 4.0.6-2ubuntu01 break reading and writing JPEG compressed files Status in LibTIFF: New Status in tiff package in Ubuntu: Confirmed Bug description: The patches applied to libtiff 4.0.6 in 4.0.6-2ubuntu01 seem to break JPEG tiff read and write. To reproduce: $ tiffcp -c jpeg k2a.tif x.tif (where k2a.tif is a simple uncompressed RGB strip tiff) appears to work. However, x.tif, the output, will now not read without warnings: $ tiffcp x.tif y.tif TIFFFetchNormalTag: Warning, ASCII value for tag "JPEGTables" does not end in null byte. Forcing it to be null. JPEGLib: Warning, Premature end of JPEG file. This was working fine until a couple of days ago, so I guess it's one of the most recent patches. Some packages using libtiff seem to be broken too. For example, openslide, which uses libtiff to load jp2k-compressed slide images, is no longer working: $ openslide-write-png CMU-1-Small-Region.svs 0 0 0 100 100 x.png TIFFFetchNormalTag: Warning, ASCII value for tag "JPEGTables" does not end in null byte. Forcing it to be null. TIFFFetchNormalTag: Warning, ASCII value for tag "JPEGTables" does not end in null byte. Forcing it ... repeats 8 more times openslide-write-png: Premature end of JPEG file and x.png is not a valid PNG image. The test .svs image may be downloaded here: http://openslide.cs.cmu.edu/download/openslide-testdata/Aperio/ To manage notifications about this bug go to: https://bugs.launchpad.net/libtiff/+bug/1670036/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp