[Desktop-packages] [Bug 1377653] Re: HDMI sound output not detected / NVIDIA optimus laptop
Just wanted to chime in to report I have the exact same problem (using Ubuntu 16.04), with the same GPU, GTX 1060 (in an MSI Apache Pro). No matter what I do, I cannot get the HDMI sound device to show up... One thing that changed things for me is if I restart the PC with the HDMI cable plugged in, I do get the HDMI device - but unfortunately it completely messes up the screens (it somehow thinks the external TV is my main monitor, laptop screen becomes unclickable... it really is a mess). Could this be connected to the graphics card drivers? I'm using the latest from the Ubuntu packages, 375. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1377653 Title: HDMI sound output not detected / NVIDIA optimus laptop Status in alsa-driver package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: Hi, not sure if this is an alsa or nvidia/nouveau bug. HDMI audio output doesn't appear in sound settings output panel. Audio works well on internal speakers, but it seems there is no way to make it output to hdmi... The laptop has optimus NVIDIA+Intel. The behaviour is the same with nouveau or nvidia proprietary driver. Please let me know if further testing is required ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6 Uname: Linux 3.13.0-36-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: sam2295 F pulseaudio CurrentDesktop: Unity CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order /var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission denied Date: Sun Oct 5 17:05:35 2014 InstallationDate: Installed on 2014-04-21 (166 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/02/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N56VZ.215 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: N56VZ dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrN56VZ.215:bd11/02/2012:svnASUSTeKCOMPUTERINC.:pnN56VZ:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN56VZ:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: N56VZ dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1377653/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1292041] Re: Lockscreen doesn't turn off the screen
Still getting this on 17.04 too. Running XFCE now, but was previously running Unity. Two monitors, one on VGA, one on DVI, both stay on when display is locked. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/1292041 Title: Lockscreen doesn't turn off the screen Status in OEM Priority Project: Fix Released Status in OEM Priority Project trusty series: Fix Released Status in Unity: Fix Released Status in gnome-screensaver package in Ubuntu: Invalid Status in unity package in Ubuntu: Fix Released Bug description: [ATTENTION] This bug report is strictly for lockscreen. When user activates lockscreen with Ctrl+Alt+L or Super+L shortcut or from indicator-session the screen should blank off after a couple seconds. The new Unity lock screen doesn't turn off the monitor screen. I can wait as long as 10 minutes after activating the lock screen and the monitor still doesn't turn off. Then when I unlock the screen and don't use mouse or keyboard monitor will turn off (it's about 5 seconds after unlocking). To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1292041/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1283003] Re: Bluetooth headset/speakers listed but not selectable in Sound settings
** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio 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: Fix Committed 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 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. To manage notifications about this bug go to: https://bugs.launchpad.net/blueman/+bug/1283003/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1582213] Re: [xenial] Bluetooth device doesn't play any sound in A2DP mode unless set to HSP/HFP first
Also verified again by me using the proposed packages -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio 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: Fix Committed 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: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1582213/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~deskt
[Desktop-packages] [Bug 1283003] Re: Bluetooth headset/speakers listed but not selectable in Sound settings
Verified. Using the proposed packages my bluetooth audio device is no longer randomly unselectable. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio 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: Fix Committed 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 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. To manage notifications about this bug go to: https://bugs.launchpad.net/blueman/+bug/1283003/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1438510] Re: [regression] Bluetooth audio no longer supports A2DP (stuck in HSP/HFP mode)
Verified. Using the proposed packages bluetooth audio no longer randomly refuses to use A2DP mode. ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio 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: Fix Committed 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/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1438510] Re: [regression] Bluetooth audio no longer supports A2DP (stuck in HSP/HFP mode)
Although after some reboots and reconnects I found I could encounter similar bugs, the proposed packages are still much better than what's in xenial at present. It took a lot more effort to confuse and break the bluetooth audio mode than it usually does :) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio 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: Fix Committed 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/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1654448] Re: XPS 13 9360 and 9350, Realtek ALC3246, Headphone audio hiss
Unfortunately that did not work. I can confirm that http://people.canonical.com/~khfeng/lp1654448-artful/ does now remove the 'Headphone Mic Boost' option. However the headphone audio hiss remains, and now we have no workaround... -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1654448 Title: XPS 13 9360 and 9350, Realtek ALC3246, Headphone audio hiss Status in Dell Sputnik: Confirmed Status in alsa-driver package in Ubuntu: Confirmed Status in linux package in Ubuntu: In Progress 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/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1654448] Re: XPS 13 9360 and 9350, Realtek ALC3246, Headphone audio hiss
At a guess the cause of the problem may be some kind of headphone volume boost option that's turned on by default, and weirdly turned off by "'Headphone Mic Boost',0 1". This may not be avoidable interference as much as just excessive volume boost turned on by default. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1654448 Title: XPS 13 9360 and 9350, Realtek ALC3246, Headphone audio hiss Status in Dell Sputnik: Confirmed Status in alsa-driver package in Ubuntu: Confirmed Status in linux package in Ubuntu: In Progress 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/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 797485] Re: SRU: Status Bar Covers File Name at Bottom
The status bar is only being hidden while mouse hovering, it is not removed completely. It's an improvement to the current status. There is no regression here. I tested 1:3.18.4.is.3.14.3-0ubuntu6 in xenial-proposed and verified the fix. ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/797485 Title: SRU: Status Bar Covers File Name at Bottom Status in Nautilus: Fix Released Status in nautilus package in Ubuntu: Fix Released Status in nautilus source package in Xenial: Fix Committed Bug description: [Impact] If using Nautilus without a status bar the selected item title 'floats' at the bottom of the file listing. If you choose the last file item in a list this 'floating' title prevents you seeing the actual title making editing difficult/impossible. This issue is also present in icon view if you have an even number of files on the bottom row it becomes difficult to rename the last file as the status bar covers the text area. [Test Case] Using Ubuntu 16.04.1 open the file manager, click "Home", enable list view and resize the file manager window so that the contents of the home directory just fit vertically and horizontally. Select the last item in the file listing and then move the mouse slowly from left to right and back again several time. You will see the floating status bar will jump from left to right, obscuring details of the selected item. After the patched nautilus package is installed, performing the same test will result on the floating status bar being hidden when the mouse hovers over it. [Regression Potential] None. This patch has been adapted from the following upstream commit: * https://git.gnome.org/browse/nautilus/commit/?id=e66d3ca Packages have been built in a PPA and tested for regressions. [ Other Info ] Binary package hint: nautilus The following possible solutions were considered: * Give the file list a bottom margin of the height of the status bar. * Move status bar to the left side when working with files in that corner. * Do not show status bar while renaming. * Hide the floating bars when hovering over part of the selection. To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/797485/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1698407] Re: Checkboxes not showing on some sites
Have now found that this is the Stylish plugin. Disabling it has made checkboxes appear again, although possibly unstyled. Feedback sent to Stylish devs. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1698407 Title: Checkboxes not showing on some sites Status in firefox package in Ubuntu: Confirmed Bug description: Firefox updated to 54 today, checkboxes are not showing on my private helpdesk application (old version of Kayako) but I have also just noticed on Reddit, specifically the subreddit search box. I also note there are no buttons showing on Gandi.net's login page which is probably related - this occurred in 52 but not 53. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: firefox 54.0+build3-0ubuntu0.16.10.1 ProcVersionSignature: Ubuntu 4.8.0-54.57-generic 4.8.17 Uname: Linux 4.8.0-54-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.3-0ubuntu8.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: simong 2591 F pulseaudio BuildID: 20170612122018 Channel: Unavailable CurrentDesktop: GNOME Date: Fri Jun 16 16:48:19 2017 EcryptfsInUse: Yes Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2016-07-22 (328 days ago) InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) IpRoute: default via 192.168.1.1 dev wlp1s0 proto static metric 600 169.254.0.0/16 dev virbr0 scope link metric 1000 linkdown 192.168.1.0/24 dev wlp1s0 proto kernel scope link src 192.168.1.45 metric 600 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 linkdown Locales: extensions.sqlite corrupt or missing MostRecentCrashID: bp-26c3f5ab-4dd8-4ac4-8d6d-4edaa1170613 Plugins: Shockwave Flash - /usr/lib/adobe-flashplugin/libflashplayer.so (adobe-flashplugin) PrefSources: prefs.js ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash Profiles: Profile0 (Default) - LastVersion=54.0/20170612122018 (In use) RelatedPackageVersions: adobe-flashplugin 1:20170613.2-0ubuntu0.16.10.1 RunningIncompatibleAddons: False SourcePackage: firefox Themes: extensions.sqlite corrupt or missing UpgradeStatus: Upgraded to yakkety on 2016-11-02 (225 days ago) dmi.bios.date: 04/12/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.11 dmi.board.asset.tag: Tag 12345 dmi.board.name: N350DW dmi.board.vendor: CLEVO dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.11:bd04/12/2016:svnPCSpecialistLimited:pnN350DW:pvrNotApplicable:rvnCLEVO:rnN350DW:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A: dmi.product.name: N350DW dmi.product.version: Not Applicable dmi.sys.vendor: PC Specialist Limited To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1698407/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1698282] Re: Totem uses dramatically higher CPU than any other video player
** Changed in: totem Status: Confirmed => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1698282 Title: Totem uses dramatically higher CPU than any other video player Status in Totem: Expired Status in totem package in Ubuntu: Confirmed Bug description: Totem uses dramatically higher CPU than any other video player. Example 1: software playback under Gnome Shell Wayland: totem: 120% (but drops to 80% in Unity7) mplayer: 40% vlc: 40% [all are using ffmpeg for decoding] Example 2: hardware-accelerated playback under Gnome Shell Xorg: totem: 11% gst-play-1.0: 3% [both are using gstreamer-vaapi for decoding] Since the decoding libraries are theoretically the same it sounds like totem's performance problems might be in its rendering path. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: libgstreamer1.0-0 1.12.0-2 ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15 Uname: Linux 4.10.0-22-generic x86_64 ApportVersion: 2.20.5-0ubuntu4 Architecture: amd64 Date: Fri Jun 16 12:57:11 2017 InstallationDate: Installed on 2017-05-03 (44 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502) LogAlsaMixer: Error: command ['/usr/bin/amixer'] failed with exit code 1: amixer: Mixer attach default error: No such file or directory SourcePackage: gstreamer1.0 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/totem/+bug/1698282/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1696965] Re: First renderer process doesn't render page for chromium 59.0.3071.86 in KVM
And for reference, the commit that introduced the problem is https://chromium.googlesource.com/chromium/src/+/d85baf0b71c69bbd181aaefc8a803611e03c8eed ** Changed in: chromium-browser (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1696965 Title: First renderer process doesn't render page for chromium 59.0.3071.86 in KVM Status in chromium-browser package in Ubuntu: In Progress Bug description: Chromium 59.0.3071.86 was promoted to the stable release channel earlier this week, and I have built packages for all supported ubuntu releases at https://launchpad.net/~osomon/+archive/ubuntu/chromium- stable. While they seem to work well on bare metal and in virtualbox virtual machines, we are seeing an issue in KVM guests (e.g. Ubuntu 16.04.2): when launched, the page in the first tab is not rendered at all (the contents remain blank). Refreshing the page doesn't make things any better. But browsing to a different domain in the same tab "fixes" the issue. All URLs are affected: the default URL when opening the browser for the first time is chrome://welcome, and it's not rendered, and so aren't other http URLs when passed on the command line. It looks like the first renderer process is not able to render to screen correctly. The renderer process itself looks okay, it doesn't crash, and I haven't seen anything relevant in the verbose logs. The official google chrome release on the same configuration is not affected, so this problem is specific to our chromium-browser packages. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1696965/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1699752] [NEW] Indicator menu filled up with ballast/multiplicate entries
Public bug reported: Recently more and more unusable entries showed up in the network manager indicator. The "New mobile broadband connection" entry is listed 4 times -four lines each- and 4 specific GSM phones are listed that are not currently around. Currently I have 24 extra lines that I cant use for anything, they make no use, I already have to scroll down at the bottom edge of the screen to find the actual available connections. (see the screenshot) Release: Ubuntu 14.04.5 LTS network-manager-gnome: 0.9.8.8-0ubuntu4.5 I tried to delete all entries from /etc/NetworkManager/system-connections/ but the culprits show up again after a reboot. I also tried to purge and reinstall everything corresponding to the network manager. ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Attachment added: "bazmeg.png" https://bugs.launchpad.net/bugs/1699752/+attachment/4900852/+files/bazmeg.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1699752 Title: Indicator menu filled up with ballast/multiplicate entries Status in network-manager package in Ubuntu: New Bug description: Recently more and more unusable entries showed up in the network manager indicator. The "New mobile broadband connection" entry is listed 4 times -four lines each- and 4 specific GSM phones are listed that are not currently around. Currently I have 24 extra lines that I cant use for anything, they make no use, I already have to scroll down at the bottom edge of the screen to find the actual available connections. (see the screenshot) Release: Ubuntu 14.04.5 LTS network-manager-gnome: 0.9.8.8-0ubuntu4.5 I tried to delete all entries from /etc/NetworkManager/system-connections/ but the culprits show up again after a reboot. I also tried to purge and reinstall everything corresponding to the network manager. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1699752/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 797485] Re: SRU: Status Bar Covers File Name at Bottom
** Patch removed: "Adapted from https://git.gnome.org/browse/nautilus/commit/?id=e66d3ca"; https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/797485/+attachment/4754164/+files/lp787485-hide-floatingbar-on-hover.patch -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/797485 Title: SRU: Status Bar Covers File Name at Bottom Status in Nautilus: Fix Released Status in nautilus package in Ubuntu: Fix Released Status in nautilus source package in Xenial: Fix Committed Bug description: [Impact] If using Nautilus without a status bar the selected item title 'floats' at the bottom of the file listing. If you choose the last file item in a list this 'floating' title prevents you seeing the actual title making editing difficult/impossible. This issue is also present in icon view if you have an even number of files on the bottom row it becomes difficult to rename the last file as the status bar covers the text area. [Test Case] Using Ubuntu 16.04.1 open the file manager, click "Home", enable list view and resize the file manager window so that the contents of the home directory just fit vertically and horizontally. Select the last item in the file listing and then move the mouse slowly from left to right and back again several time. You will see the floating status bar will jump from left to right, obscuring details of the selected item. After the patched nautilus package is installed, performing the same test will result on the floating status bar being hidden when the mouse hovers over it. [Regression Potential] None. This patch has been adapted from the following upstream commit: * https://git.gnome.org/browse/nautilus/commit/?id=e66d3ca Packages have been built in a PPA and tested for regressions. [ Other Info ] Binary package hint: nautilus The following possible solutions were considered: * Give the file list a bottom margin of the height of the status bar. * Move status bar to the left side when working with files in that corner. * Do not show status bar while renaming. * Hide the floating bars when hovering over part of the selection. To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/797485/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1634939] Re: Copy progress popover should close on completion
** Changed in: nautilus (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1634939 Title: Copy progress popover should close on completion Status in Nautilus: Fix Released Status in nautilus package in Ubuntu: Fix Released Bug description: When copying folders/files and the popover progress window opens it pops up in all opened instances of Nautilus. You also need to close the popover on every single window or close every window to get it to disappear. This also applies to the progress-bar in launcher. Expected behavior: copy popover should close after successfully performing the copy operation. Ubuntu 16.10 Nautilus 1:3.20.3-1ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1634939/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1699758] [NEW] lost desk top icons
Public bug reported: I have installed 11.04 Unity but while tweaking with Compiz Sett I lost all desktop icons and dont even see APP menu at top of page the only thing i have is docky. I tryed nautilus -k; killall gnome-panel in terminal and got ~$ nautilus -k; killall gnome-panel Could not parse arguments: Unknown option -k gnome-panel: no process found Any ideas?? ** Affects: gnome-terminal (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1699758 Title: lost desk top icons Status in gnome-terminal package in Ubuntu: New Bug description: I have installed 11.04 Unity but while tweaking with Compiz Sett I lost all desktop icons and dont even see APP menu at top of page the only thing i have is docky. I tryed nautilus -k; killall gnome-panel in terminal and got ~$ nautilus -k; killall gnome-panel Could not parse arguments: Unknown option -k gnome-panel: no process found Any ideas?? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1699758/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 606365] Re: unable to import config with inlined ca, cert, key or tls-auth
** Tags removed: network-manager openvpn ** Tags added: xenial -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-openvpn in Ubuntu. https://bugs.launchpad.net/bugs/606365 Title: unable to import config with inlined ca, cert, key or tls-auth Status in NetworkManager-OpenVPN: Fix Released Status in plasma-nm: Unknown Status in network-manager-openvpn package in Ubuntu: Confirmed Bug description: Binary package hint: network-manager-openvpn-gnome So a client of mine runs an OpenVPN setup. It exported a client.ovpn file but it fails to completely import this file using the network- manager (gnome) on Ubuntu 10.04. When I import the file, it gives me the name ("client") and gateway ("vpn.example.org") on the initial screen. No other fields are populated even though the client.ovpn file also includes a user certificate, server certifikate and a private key. When I go to advanced, some (most) of the settings obviously seem to import correct, others not at all. E.g. none of the TLS settings (key and key direction) are imported. From what I understand I should be able to use this without any additional settings. The following software is installed through aptitude: * openvpn (2.1.0) * openvpn-blacklist * network-manager-openvpn * network-manager-openvpn-gnome To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager-openvpn/+bug/606365/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 606365] Re: unable to import config with inlined ca, cert, key or tls-auth
** Bug watch added: KDE Bug Tracking System #349282 https://bugs.kde.org/show_bug.cgi?id=349282 ** Package changed: network-manager-openvpn (Fedora) => plasma-nm ** Changed in: plasma-nm Importance: Undecided => Unknown ** Changed in: plasma-nm Status: New => Unknown ** Changed in: plasma-nm Remote watch: None => KDE Bug Tracking System #349282 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-openvpn in Ubuntu. https://bugs.launchpad.net/bugs/606365 Title: unable to import config with inlined ca, cert, key or tls-auth Status in NetworkManager-OpenVPN: Fix Released Status in plasma-nm: Unknown Status in network-manager-openvpn package in Ubuntu: Confirmed Bug description: Binary package hint: network-manager-openvpn-gnome So a client of mine runs an OpenVPN setup. It exported a client.ovpn file but it fails to completely import this file using the network- manager (gnome) on Ubuntu 10.04. When I import the file, it gives me the name ("client") and gateway ("vpn.example.org") on the initial screen. No other fields are populated even though the client.ovpn file also includes a user certificate, server certifikate and a private key. When I go to advanced, some (most) of the settings obviously seem to import correct, others not at all. E.g. none of the TLS settings (key and key direction) are imported. From what I understand I should be able to use this without any additional settings. The following software is installed through aptitude: * openvpn (2.1.0) * openvpn-blacklist * network-manager-openvpn * network-manager-openvpn-gnome To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager-openvpn/+bug/606365/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1699761] [NEW] snap apps don't have icons
Public bug reported: With the libreoffice snap from the snap store (version 5.3.2.2-snap1), launcher for the office apps are available in the unity dash/gnome-shell applications list, but they don't have the correct icons associated to them. See attached screenshot. ** Affects: libreoffice (Ubuntu) Importance: Medium Assignee: Olivier Tilloy (osomon) Status: In Progress ** Tags: snap ** Attachment added: "icons.png" https://bugs.launchpad.net/bugs/1699761/+attachment/4900859/+files/icons.png ** Changed in: libreoffice (Ubuntu) Status: New => In Progress ** Changed in: libreoffice (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1699761 Title: snap apps don't have icons Status in libreoffice package in Ubuntu: In Progress Bug description: With the libreoffice snap from the snap store (version 5.3.2.2-snap1), launcher for the office apps are available in the unity dash/gnome- shell applications list, but they don't have the correct icons associated to them. See attached screenshot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1699761/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1696965] Re: First renderer process doesn't render page for chromium 59.0.3071.86 in KVM
« The official google chrome release on the same configuration is not affected, so this problem is specific to our chromium-browser packages. » This is in fact not true. While it happens less often, I've been able to reproduce the issue with google chrome launched without any additional command-line flags. Attaching a screenshot. ** Attachment added: "chrome.png" https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1696965/+attachment/4900861/+files/chrome.png ** Changed in: chromium-browser (Ubuntu) Importance: Critical => High ** Description changed: Chromium 59.0.3071.86 was promoted to the stable release channel earlier this week, and I have built packages for all supported ubuntu releases at https://launchpad.net/~osomon/+archive/ubuntu/chromium-stable. While they seem to work well on bare metal and in virtualbox virtual machines, we are seeing an issue in KVM guests (e.g. Ubuntu 16.04.2): when launched, the page in the first tab is not rendered at all (the contents remain blank). Refreshing the page doesn't make things any better. But browsing to a different domain in the same tab "fixes" the issue. All URLs are affected: the default URL when opening the browser for the first time is chrome://welcome, and it's not rendered, and so aren't other http URLs when passed on the command line. It looks like the first renderer process is not able to render to screen correctly. The renderer process itself looks okay, it doesn't crash, and I haven't seen anything relevant in the verbose logs. - The official google chrome release on the same configuration is not - affected, so this problem is specific to our chromium-browser packages. + The official google chrome release on the same configuration is affected + too, although much less often. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1696965 Title: First renderer process doesn't render page for chromium 59.0.3071.86 in KVM Status in chromium-browser package in Ubuntu: In Progress Bug description: Chromium 59.0.3071.86 was promoted to the stable release channel earlier this week, and I have built packages for all supported ubuntu releases at https://launchpad.net/~osomon/+archive/ubuntu/chromium- stable. While they seem to work well on bare metal and in virtualbox virtual machines, we are seeing an issue in KVM guests (e.g. Ubuntu 16.04.2): when launched, the page in the first tab is not rendered at all (the contents remain blank). Refreshing the page doesn't make things any better. But browsing to a different domain in the same tab "fixes" the issue. All URLs are affected: the default URL when opening the browser for the first time is chrome://welcome, and it's not rendered, and so aren't other http URLs when passed on the command line. It looks like the first renderer process is not able to render to screen correctly. The renderer process itself looks okay, it doesn't crash, and I haven't seen anything relevant in the verbose logs. The official google chrome release on the same configuration is affected too, although much less often. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1696965/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1699772] [NEW] linux-image-4.4.0-81-generic Regression: Oracle Java plugin crashes
Public bug reported: Distribution: Ubuntu 16.04 x64 (Flavour: KDE Neon User Edition 5.10) linux-image-4.4.0-81-generic appears to contain a regression, probably related to the CVE-2017-1000364 fix backport / patch. Using this kernel, the Oracle Java browser plugin always crashes during stack-related actions on initialization. This means, the plugin completely stopped working. It works perfectly fine in linux-image-4.4.0-79-generic (vurlerable to CVE-2017-1000364) as well as linux-image-4.11.6-041106-generic, which also contains a fix for CVE-2017-1000364. uname -a: > Linux Zweiblum 4.4.0-81-generic #104-Ubuntu SMP Wed Jun 14 08:17:06 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux I tested Oracle Java 1.8 u131 as well as 1.6 u64 in Firefox 51.0.1 as well as Iceweasel / Firefox/3.5.16 in a chroot. Using linux-image-4.4.0-81-generic it crashes in all combinations while with both other kernels it works. I was not able to obtain any detailed crash information from Firefox 51.0.1, but Iceweasel 3.5.16 crashed completely, allowing me to obtain a stack trace which shows the relation to stack operations performed by the plugin, even without proper debug symbols: > (gdb) bt full > #0 0x7fa06d805307 in _expand_stack_to(unsigned char*) () from > /opt/java-8-oracle/jre/lib/amd64/server/libjvm.so > No symbol table info available. > #1 0x7fa06d8053ae in os::Linux::manually_expand_stack(JavaThread*, > unsigned char*) () >from /opt/java-8-oracle/jre/lib/amd64/server/libjvm.so > No symbol table info available. > #2 0x7fa06d80cf0b in JVM_handle_linux_signal () from > /opt/java-8-oracle/jre/lib/amd64/server/libjvm.so > No symbol table info available. > #3 0x7fa06d802e13 in signalHandler(int, siginfo*, void*) () from > /opt/java-8-oracle/jre/lib/amd64/server/libjvm.so > No symbol table info available. > #4 I first assumed a bug in the Java plugin, but it works fine in Linux 4.11.6. The crash will be triggered by any applet, for example the test applet at: * https://java.com/en/download/installed8.jsp I'm running the Ubuntu 16.04 based KDE Neon distribution which somehow apparently does not allow me to use apport to report this bug: > $ LANG= apport-cli linux-image-4.4.0-81-generic > > *** Collecting problem information > > The collected information can be sent to the developers to improve the > application. This might take a few minutes. > . > > *** Problem in linux-image-4.4.0-81-generic > > The problem cannot be reported: > > This is not an official KDE package. Please remove any third party package > and try again. If someone can tell me how to get apport working for this package, I can use it to collect additional information, but (unfortunately?) the problem should be fairly easy to reproduce... ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Package changed: mesa (Ubuntu) => linux (Ubuntu) ** CVE added: https://cve.mitre.org/cgi- bin/cvename.cgi?name=2017-1000364 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1699772 Title: linux-image-4.4.0-81-generic Regression: Oracle Java plugin crashes Status in linux package in Ubuntu: Confirmed Bug description: Distribution: Ubuntu 16.04 x64 (Flavour: KDE Neon User Edition 5.10) linux-image-4.4.0-81-generic appears to contain a regression, probably related to the CVE-2017-1000364 fix backport / patch. Using this kernel, the Oracle Java browser plugin always crashes during stack-related actions on initialization. This means, the plugin completely stopped working. It works perfectly fine in linux-image-4.4.0-79-generic (vurlerable to CVE-2017-1000364) as well as linux-image-4.11.6-041106-generic, which also contains a fix for CVE-2017-1000364. uname -a: > Linux Zweiblum 4.4.0-81-generic #104-Ubuntu SMP Wed Jun 14 08:17:06 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux I tested Oracle Java 1.8 u131 as well as 1.6 u64 in Firefox 51.0.1 as well as Iceweasel / Firefox/3.5.16 in a chroot. Using linux-image-4.4.0-81-generic it crashes in all combinations while with both other kernels it works. I was not able to obtain any detailed crash information from Firefox 51.0.1, but Iceweasel 3.5.16 crashed completely, allowing me to obtain a stack trace which shows the relation to stack operations performed by the plugin, even without proper debug symbols: > (gdb) bt full > #0 0x7fa06d805307 in _expand_stack_to(unsigned char*) () from /opt/java-8-oracle/jre/lib/amd64/server/libjvm.so > No symbol table info available. > #1 0x7fa06d8053ae in os::Linux::manually_expand_stack(JavaThread*, unsigned char*) () >from /opt/java-8-oracle/jre/lib/amd64/server/libjvm.so > No symbol table info available. > #2 0x7fa06d80cf0b in JVM_handle_linux_signal () from /opt/java-8-oracle/jre/lib/amd64/server/libjvm.so
[Desktop-packages] [Bug 1698351] Re: Search in Nautilus Files does not allow sorting of results
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nautilus (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1698351 Title: Search in Nautilus Files does not allow sorting of results Status in nautilus package in Ubuntu: Confirmed Bug description: The version of nautilus/Files included with Ubuntu 17.04 no longer allows sorting of search results. Previously, sort was achieved by clicking on the column header titles. This no longer works. It represents a significant regression in the search feature. Thanks. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1698351/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1698351] Re: Search in Nautilus Files does not allow sorting of results
After upgrading to nautilus 1:3.20.3-1ubuntu2~ubuntu16.04.1 with ppa:gnome3-team/gnome3-staging found that can't sort search results either in icon or list view. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1698351 Title: Search in Nautilus Files does not allow sorting of results Status in nautilus package in Ubuntu: Confirmed Bug description: The version of nautilus/Files included with Ubuntu 17.04 no longer allows sorting of search results. Previously, sort was achieved by clicking on the column header titles. This no longer works. It represents a significant regression in the search feature. Thanks. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1698351/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1583801] Re: No sound via headphones (headset) when Ubuntu boots with them plugged in
I can confirm this bug. Works after wake up from suspend - after reboot: dead. So I've to put my computer into suspend mode and then wake it up in order to get sound in the headphone jack. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1583801 Title: No sound via headphones (headset) when Ubuntu boots with them plugged in Status in alsa-driver package in Ubuntu: Confirmed Bug description: The bug is twofold, first when computer boots if the headset (headphones with built-in mic, one audio jack) is plugged in, then there is no sound (via headphones or otherwise). If you plug headphones out and back in, then it usually works as expected. The second scenario is the same, except that plugging out and back in again doesn't help. In that case, I just restart the laptop, then plug them back in again and it works. In all cases, microphone works. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: crunch 3248 F pulseaudio CurrentDesktop: Unity Date: Thu May 19 22:13:20 2016 InstallationDate: Installed on 2016-05-07 (12 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: crunch 3248 F pulseaudio Symptom_Jack: Black Headphone Out, Left Symptom_Type: No sound at all Title: [XPS 15 9550, Realtek ALC3266, Black Headphone Out, Left] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/07/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.02.00 dmi.board.name: 0N7TVV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 15 9550 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1583801/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1699781] [NEW] Unable to install texlive on Artful, failed with dependency issue
Public bug reported: Step: * Run "sudo apt install texlive" on a clean-installed Artful (deployed with MaaS) Error log for fmtutil: http://paste.ubuntu.com/24924512/ Error output from the console: Setting up xterm (324-2ubuntu1) ... update-alternatives: using /usr/bin/xterm to provide /usr/bin/x-terminal-emulator (x-terminal-emulator) in auto mode update-alternatives: using /usr/bin/lxterm to provide /usr/bin/x-terminal-emulator (x-terminal-emulator) in auto mode Setting up texlive-binaries (2017.20170613.44572-2) ... update-alternatives: using /usr/bin/xdvi-xaw to provide /usr/bin/xdvi.bin (xdvi.bin) in auto mode update-alternatives: using /usr/bin/bibtex.original to provide /usr/bin/bibtex (bibtex) in auto mode Setting up tk (8.6.0+9) ... Setting up x11-xserver-utils (7.7+7build1) ... Setting up ps2eps (1.68+binaryfree-2) ... Processing triggers for tex-common (6.06) ... locale: Cannot set LC_ALL to default locale: No such file or directory texlive-base is not ready, delaying updmap-sys call update-language: texlive-base not installed and configured, doing nothing! texlive-base is not ready, skipping fmtutil --all call Setting up texlive-base (2016.20170123-5) ... mktexlsr: Updating /var/lib/texmf/ls-R-TEXLIVEDIST... mktexlsr: Updating /var/lib/texmf/ls-R-TEXMFMAIN... mktexlsr: Updating /var/lib/texmf/ls-R... mktexlsr: Done. /usr/bin/tl-paper: setting paper size for dvips to a4. /usr/bin/tl-paper: setting paper size for dvipdfmx to a4. /usr/bin/tl-paper: setting paper size for xdvi to a4. /usr/bin/tl-paper: setting paper size for pdftex to a4. locale: Cannot set LC_ALL to default locale: No such file or directory Processing triggers for tex-common (6.06) ... locale: Cannot set LC_ALL to default locale: No such file or directory Running updmap-sys. This may take some time... done. Running mktexlsr /var/lib/texmf ... done. Building format(s) --all. This may take some time... fmtutil failed. Output has been stored in /tmp/fmtutil.aUXBfjpw Please include this file if you report a bug. dpkg: error processing package tex-common (--configure): subprocess installed post-installation script returned error exit status 1 No apport report written because the error message indicates its a followup error from a previous failure. dpkg: dependency problems prevent configuration of texlive-fonts-recommended-doc: texlive-fonts-recommended-doc depends on tex-common (>= 6); however: Package tex-common is not configured yet. dpkg: error processing package texlive-fonts-recommended-doc (--configure): dependency problems - leaving unconfigured dpkg: dependency problems prevent configuration of texlive-fonts-recommended: texlive-fonts-recommended depends on tex-common (>= 6); however: Package tex-common is not configured yet. dpkg: error processing package texlive-fonts-recommended (--configure): dependency problems - leaving unconfigured dpkg: dependency problems prevent configuration of texlive: texlive depends on texlive-fonts-recommended (>= 2016.20170123-2); however: Package texlive-fonts-recommended is not configured yet. dpkg: error processing package texlive (--configure): dependency problems - leaving unconfigured dpkg: dependency problems prevent configuration of texlive-generic-recommended: texliveNo apport report written because the error message indicates its a followup error from a previous failure. No apport report written because MaxReports is reached already No apport report written because MaxReports is reached already No apport report written because MaxReports is reached already No apport report written because MaxReports is reached already No apport report written because MaxReports is reached already No apport report written because MaxReports is reached already No apport report written because MaxReports is reached already No apport report written because MaxReports is reached already No apport report written because MaxReports is reached already No apport report written because MaxReports is reached already No apport report written because MaxReports is reached already -generic-recommended depends on tex-common (>= 6); however: Package tex-common is not configured yet. dpkg: error processing packag
[Desktop-packages] [Bug 1416768] Re: Fontconfig error output due to malformed conf file
This doesn't just affect Steam. I see the same error when running Cura (3D printer slicer program). See attached log. ** Attachment added: "Cura-2.6.0.log" https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1416768/+attachment/4900919/+files/Cura-2.6.0.log -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fontconfig in Ubuntu. https://bugs.launchpad.net/bugs/1416768 Title: Fontconfig error output due to malformed conf file Status in One Hundred Papercuts: Confirmed Status in fontconfig package in Ubuntu: Confirmed Bug description: Generating new string page texture 121: 256x256, total string texture memory is 393.22 KB Generating new string page texture 122: 128x256, total string texture memory is 2.79 MB Fontconfig error: "/etc/fonts/conf.d/10-scale-bitmap-fonts.conf", line 70: non-double matrix element Fontconfig error: "/etc/fonts/conf.d/10-scale-bitmap-fonts.conf", line 70: non-double matrix element Fontconfig warning: "/etc/fonts/conf.d/10-scale-bitmap-fonts.conf", line 78: saw unknown, expected number Generating new string page texture 136: 2048x256, total string texture memory is 4.88 MB Installing breakpad exception handler for appid(steamwebhelper)/version(20150130171142) Installing breakpad exception handler for appid(steamwebhelper)/version(1422637902) Above output is produced, eg by steam when running a game. The fontconfig error lines can be verified with "fc-cache -v | grep -i err". The offending section is around original lines 70, 78: false 1.0 matrix pixelsizefixupfactor 0 0 pixelsizefixupfactor size pixelsizefixupfactor Note that the element has 2 child elements when it should only have 1. Removal of the second "pixelsizefixupfactor" solves the error. After this removal neither fc-cache nor steam report an "Fontconfig error:". The documentation for fonts.conf, eg http://linux.die.net/man/5/fonts- conf, suggests that the element should hold 4 elements: > > >This element holds the four elements of an affine transformation. But it appears not to produce an error when only 2 elements are present (and does produce an error here when there are 4, for me). ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: fontconfig-config 2.11.1-0ubuntu3 ProcVersionSignature: Ubuntu 3.16.0-29.39-generic 3.16.7-ckt2 Uname: Linux 3.16.0-29-generic x86_64 ApportVersion: 2.14.7-0ubuntu8.1 Architecture: amd64 CurrentDesktop: KDE Date: Sun Feb 1 00:46:10 2015 InstallationDate: Installed on 2012-11-02 (820 days ago) InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.1) PackageArchitecture: all SourcePackage: fontconfig UpgradeStatus: Upgraded to utopic on 2015-01-28 (3 days ago) modified.conffile..etc.fonts.conf.avail.10.scale.bitmap.fonts.conf: [modified] mtime.conffile..etc.fonts.conf.avail.10.scale.bitmap.fonts.conf: 2015-02-01T00:30:44.308962 To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1416768/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1399077] Re: Cannot show Copy/Move dialogue in Xenial
** Summary changed: - File copy dialog disappears, won't re-show, can't alt-tab to nautilus + Cannot show Copy/Move dialogue in Xenial -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1399077 Title: Cannot show Copy/Move dialogue in Xenial Status in nautilus package in Ubuntu: Confirmed Status in unity package in Ubuntu: Confirmed Bug description: I'm copying a large amount of data from my digital camera (which mounts with gphoto2). With a copy in progress, I alt-tab away to google chrome and then alt-tab back to nautilus. The copy dialog is gone and the menu option on the nautilus icon to "Show copy dialog" does nothing. The copy progress is shown on the icon. In fact Alt-tabbing to nautilus seems to fail while it's in this mode entirely. The focus stays on chrome the whole time. The only way I can get to nautilus is to move chrome out of the way and manually click on the nautilus windows. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: nautilus 1:3.10.1-0ubuntu15 ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7 Uname: Linux 3.16.0-25-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Wed Dec 3 21:35:44 2014 GsettingsChanges: InstallationDate: Installed on 2012-09-26 (799 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120905.2) SourcePackage: nautilus UpgradeStatus: Upgraded to utopic on 2014-10-27 (38 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1399077/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1399077] Re: Cannot show Copy/Move dialogue in Xenial
** Tags added: xenial ** Also affects: unity (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1399077 Title: Cannot show Copy/Move dialogue in Xenial Status in nautilus package in Ubuntu: Confirmed Status in unity package in Ubuntu: Confirmed Bug description: I'm copying a large amount of data from my digital camera (which mounts with gphoto2). With a copy in progress, I alt-tab away to google chrome and then alt-tab back to nautilus. The copy dialog is gone and the menu option on the nautilus icon to "Show copy dialog" does nothing. The copy progress is shown on the icon. In fact Alt-tabbing to nautilus seems to fail while it's in this mode entirely. The focus stays on chrome the whole time. The only way I can get to nautilus is to move chrome out of the way and manually click on the nautilus windows. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: nautilus 1:3.10.1-0ubuntu15 ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7 Uname: Linux 3.16.0-25-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Wed Dec 3 21:35:44 2014 GsettingsChanges: InstallationDate: Installed on 2012-09-26 (799 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120905.2) SourcePackage: nautilus UpgradeStatus: Upgraded to utopic on 2014-10-27 (38 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1399077/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 887821] Re: "Show copy dialog" right click launcher entry doesn't work (on nautilus copy)
This bug is closed. No one will see it. Please mark yourself as affected if you have this bug in Xenial in bug #1399077. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/887821 Title: "Show copy dialog" right click launcher entry doesn't work (on nautilus copy) Status in Unity: Fix Released Status in Unity 5.0 series: Won't Fix Status in nautilus package in Ubuntu: Fix Released Status in unity package in Ubuntu: Fix Released Status in nautilus source package in Precise: Fix Released Status in unity source package in Precise: Invalid Bug description: Impact: the nautilus copy dialog don't get properly focussed by unity Test Case: - log into an unity session - copy a not too small file (so you have time to interact with the copy dialog) - minimize the copy dialog - right click on the corresponding unity-launcher's icon, and pick "show copy dialog" -> the dialog should be displayed Regression testing: Check that there is no focus issue with that dialog and the launcher -- While copying a large (8 gig) file across an SMB network, I minimized it. The right click on the Nautilus Unity bar showed a "Show copy dialog" item. Clicking on that item did nothing. The only way to get the dialog back up was to open one of the two minimized Nautilus windows and then minimize the one on top. After that minimize, then the copy dialog was displayed on top of the other Nautilus window. I couldn't find any way to get the copy dialog back on screen without clicking around somewhat aimlessly displaying and minimizing Nautilus windows until it appeared. The "Show copy dialog" right-click menu appeared to have no affect. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: nautilus 1:3.2.1-0ubuntu2 ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4 Uname: Linux 3.0.0-12-generic x86_64 NonfreeKernelModules: wl fglrx ApportVersion: 1.23-0ubuntu4 Architecture: amd64 Date: Tue Nov 8 18:12:10 2011 ExecutablePath: /usr/bin/nautilus InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/887821/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1399077] Re: Cannot show Copy/Move dialogue in Xenial
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: unity (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1399077 Title: Cannot show Copy/Move dialogue in Xenial Status in nautilus package in Ubuntu: Confirmed Status in unity package in Ubuntu: Confirmed Bug description: I'm copying a large amount of data from my digital camera (which mounts with gphoto2). With a copy in progress, I alt-tab away to google chrome and then alt-tab back to nautilus. The copy dialog is gone and the menu option on the nautilus icon to "Show copy dialog" does nothing. The copy progress is shown on the icon. In fact Alt-tabbing to nautilus seems to fail while it's in this mode entirely. The focus stays on chrome the whole time. The only way I can get to nautilus is to move chrome out of the way and manually click on the nautilus windows. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: nautilus 1:3.10.1-0ubuntu15 ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7 Uname: Linux 3.16.0-25-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Wed Dec 3 21:35:44 2014 GsettingsChanges: InstallationDate: Installed on 2012-09-26 (799 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120905.2) SourcePackage: nautilus UpgradeStatus: Upgraded to utopic on 2014-10-27 (38 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1399077/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1696965] Re: First renderer process doesn't render page for chromium 59.0.3071.86 in KVM
Bug reported upstream: https://bugs.chromium.org/p/chromium/issues/detail?id=735947 ** Changed in: chromium-browser (Ubuntu) Status: In Progress => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1696965 Title: First renderer process doesn't render page for chromium 59.0.3071.86 in KVM Status in chromium-browser package in Ubuntu: Confirmed Bug description: Chromium 59.0.3071.86 was promoted to the stable release channel earlier this week, and I have built packages for all supported ubuntu releases at https://launchpad.net/~osomon/+archive/ubuntu/chromium- stable. While they seem to work well on bare metal and in virtualbox virtual machines, we are seeing an issue in KVM guests (e.g. Ubuntu 16.04.2): when launched, the page in the first tab is not rendered at all (the contents remain blank). Refreshing the page doesn't make things any better. But browsing to a different domain in the same tab "fixes" the issue. All URLs are affected: the default URL when opening the browser for the first time is chrome://welcome, and it's not rendered, and so aren't other http URLs when passed on the command line. It looks like the first renderer process is not able to render to screen correctly. The renderer process itself looks okay, it doesn't crash, and I haven't seen anything relevant in the verbose logs. The official google chrome release on the same configuration is affected too, although much less often. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1696965/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1699800] [NEW] Extension Library Watcher causes Banshee to stall
Public bug reported: The extension Library Watcher causes Banshee to stall and do nothing even when closed and ran again. To reproduce this bug go to Preferences in the Edit menu and there in the Extensions tab click the checkmark for Library Watcher. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: banshee 2.9.0+really2.6.2-7ubuntu2 ProcVersionSignature: Ubuntu 4.8.0-56.61~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-56-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 CurrentDesktop: Unity Date: Thu Jun 22 09:45:26 2017 InstallationDate: Installed on 2017-06-20 (1 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) SourcePackage: banshee UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: banshee (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to banshee in Ubuntu. https://bugs.launchpad.net/bugs/1699800 Title: Extension Library Watcher causes Banshee to stall Status in banshee package in Ubuntu: New Bug description: The extension Library Watcher causes Banshee to stall and do nothing even when closed and ran again. To reproduce this bug go to Preferences in the Edit menu and there in the Extensions tab click the checkmark for Library Watcher. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: banshee 2.9.0+really2.6.2-7ubuntu2 ProcVersionSignature: Ubuntu 4.8.0-56.61~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-56-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 CurrentDesktop: Unity Date: Thu Jun 22 09:45:26 2017 InstallationDate: Installed on 2017-06-20 (1 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) SourcePackage: banshee UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/banshee/+bug/1699800/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 980519] Re: Random log off in Ubuntu 12.04 LTS
the same issue is reflected in ubuntu 16.04 lts ...Any remedy for this issue? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers in Ubuntu. https://bugs.launchpad.net/bugs/980519 Title: Random log off in Ubuntu 12.04 LTS Status in Unity: Fix Released Status in gnome-desktop package in Ubuntu: Confirmed Status in nvidia-graphics-drivers package in Ubuntu: Fix Released Status in unity package in Ubuntu: Fix Released Status in xorg package in Ubuntu: Fix Released Status in Fedora: New Bug description: I get logged off from Ubuntu sometimes. There is no error message or any indication that it is going to log off. The screen goes black, and after 2-4 seconds, i get presented with the Ubuntu Log On Screen. There is no clear pattern (or at least if have not noticed any). One time i am working with Netbeans, another time i am using firefox. This also means that at present i can not clearly say what package might be causing this behaviour. I am fairly sure the problem lies in 12.04 (or more precise - the combination of 12.04 and the hardware i am using). I do not have the same problem running 11.04 or 11.10. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/980519/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1699826] Re: I get this error on login every time - package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error
*** This bug is a duplicate of bug 1688721 *** https://bugs.launchpad.net/bugs/1688721 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1688721, so 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. Please continue to report any other bugs you may find. ** Tags removed: need-duplicate-check ** This bug has been marked a duplicate of bug 1688721 Packages that trigger multiple debconf prompts fail to install -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gconf in Ubuntu. https://bugs.launchpad.net/bugs/1699826 Title: I get this error on login every time - 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: I get this error on login every time ProblemType: Package DistroRelease: Ubuntu 17.04 Package: gconf2-common 3.2.6-3ubuntu7 ProcVersionSignature: Ubuntu 4.10.0-24.28-generic 4.10.15 Uname: Linux 4.10.0-24-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 Date: Thu Jun 22 15:59:10 2017 ErrorMessage: subprocess installed post-installation script returned error exit status 128 InstallationDate: Installed on 2017-06-22 (0 days ago) InstallationMedia: Ubuntu-GNOME 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/1699826/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1699826] [NEW] I get this error on login every time - package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned err
*** This bug is a duplicate of bug 1688721 *** https://bugs.launchpad.net/bugs/1688721 Public bug reported: I get this error on login every time ProblemType: Package DistroRelease: Ubuntu 17.04 Package: gconf2-common 3.2.6-3ubuntu7 ProcVersionSignature: Ubuntu 4.10.0-24.28-generic 4.10.15 Uname: Linux 4.10.0-24-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 Date: Thu Jun 22 15:59:10 2017 ErrorMessage: subprocess installed post-installation script returned error exit status 128 InstallationDate: Installed on 2017-06-22 (0 days ago) InstallationMedia: Ubuntu-GNOME 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 zesty -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gconf in Ubuntu. https://bugs.launchpad.net/bugs/1699826 Title: I get this error on login every time - 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: I get this error on login every time ProblemType: Package DistroRelease: Ubuntu 17.04 Package: gconf2-common 3.2.6-3ubuntu7 ProcVersionSignature: Ubuntu 4.10.0-24.28-generic 4.10.15 Uname: Linux 4.10.0-24-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 Date: Thu Jun 22 15:59:10 2017 ErrorMessage: subprocess installed post-installation script returned error exit status 128 InstallationDate: Installed on 2017-06-22 (0 days ago) InstallationMedia: Ubuntu-GNOME 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/1699826/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1538333] Re: AssertionError in manifest.py: assert filecount == len(self.files_changed)
I have been unable to reproduce this in testing. If you encounter this error, please provide the following: 1) full command line 2) full unencrypted manifest file (attached as a file) 3) detailed (ls -l style) listing of the remote system (attached as a file) 4) as much of the logging as possible, especially the first 200 lines and last 200 lines at -v9 level (attached as a file) NOTE: Comment #5 references a memory error. This is a different bug that we're working on. ** Changed in: duplicity Status: New => Incomplete ** Changed in: duplicity Milestone: None => 0.7.14 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to duplicity in Ubuntu. https://bugs.launchpad.net/bugs/1538333 Title: AssertionError in manifest.py: assert filecount == len(self.files_changed) Status in Duplicity: Incomplete Status in duplicity package in Ubuntu: Confirmed Status in duplicity source package in Zesty: Fix Released Bug description: Duplicity was almost finishing a full backup to a FTP server. When I restarted the backup, the following error occured: root@MyMachine:~# duply MyProfile backup Start duply v1.11, time is 2016-01-26 23:38:21. Using profile '/root/.duply/MyProfile'. Using installed duplicity version 0.7.06, python 2.7.3, gpg 1.4.12 (Home: ~/.gnupg), awk 'mawk 1.3.3 Nov 1996, Copyright (C) Michael D. Brennan', grep 'grep (GNU grep) 2.12', bash 'GNU bash, Version 4.2.37(1)-release (i486-pc-linux-gnu)'. Autoset found secret key of first GPG_KEY entry '' for signing. Checking TEMP_DIR '/tmp' is a folder and writable (OK) Test - Encrypt to '' & Sign with '' (OK) Test - Decrypt (OK) Test - Compare (OK) Cleanup - Delete '/tmp/duply.16938.1453847902_*'(OK) --- Start running command PRE at 23:38:24.349 --- Skipping n/a script '/root/.duply/MyProfile/pre'. --- Finished state OK at 23:38:24.400 - Runtime 00:00:00.051 --- --- Start running command BKP at 23:38:24.447 --- LFTP version is 4.3.6 Reading globbing filelist /root/.duply/MyProfile/exclude Local and Remote metadata are synchronized, no sync needed. Traceback (most recent call last): File "/usr/local/bin/duplicity", line 1532, in with_tempdir(main) File "/usr/local/bin/duplicity", line 1526, in with_tempdir fn() File "/usr/local/bin/duplicity", line 1380, in main do_backup(action) File "/usr/local/bin/duplicity", line 1405, in do_backup globals.archive_dir).set_values() File "/usr/local/lib/python2.7/dist-packages/duplicity/collections.py", line 710, in set_values self.get_backup_chains(partials + backend_filename_list) File "/usr/local/lib/python2.7/dist-packages/duplicity/collections.py", line 835, in get_backup_chains add_to_sets(f) File "/usr/local/lib/python2.7/dist-packages/duplicity/collections.py", line 829, in add_to_sets if new_set.add_filename(filename): File "/usr/local/lib/python2.7/dist-packages/duplicity/collections.py", line 101, in add_filename self.set_manifest(filename) File "/usr/local/lib/python2.7/dist-packages/duplicity/collections.py", line 149, in set_manifest self.set_files_changed() File "/usr/local/lib/python2.7/dist-packages/duplicity/collections.py", line 128, in set_files_changed mf = self.get_manifest() File "/usr/local/lib/python2.7/dist-packages/duplicity/collections.py", line 250, in get_manifest return self.get_local_manifest() File "/usr/local/lib/python2.7/dist-packages/duplicity/collections.py", line 225, in get_local_manifest return manifest.Manifest().from_string(manifest_buffer) File "/usr/local/lib/python2.7/dist-packages/duplicity/manifest.py", line 207, in from_string assert filecount == len(self.files_changed) AssertionError 23:38:36.860 Task 'BKP' failed with exit code '30'. --- Finished state FAILED 'code 30' at 23:38:36.860 - Runtime 00:00:12.412 --- --- Start running command POST at 23:38:36.930 --- Skipping n/a script '/root/.duply/MyProfile/post'. --- Finished state OK at 23:38:36.983 - Runtime 00:00:00.052 --- Probably the version of python got updated in the meantime, but I'm not sure about this. Similar tickets, eventually this bug report is a duplicate of those: - https://bugs.launchpad.net/duplicity/+bug/1485579 - https://bugzilla.redhat.com/show_bug.cgi?id=1288702 To manage notifications about this bug go to: https://bugs.launchpad.net/duplicity/+bug/1538333/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1538333] Re: AssertionError in manifest.py: assert filecount == len(self.files_changed)
I have been unable to reproduce this in testing. If you encounter this error, please provide the following: 1) full command line 2) full unencrypted manifest file (attached as a file) 3) detailed (ls -l style) listing of the remote system (attached as a file) 4) as much of the logging as possible, especially the first 200 lines and last 200 lines at -v9 level (attached as a file) NOTE: Comment #5 references a memory error. This is a different bug that we're working on. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to duplicity in Ubuntu. https://bugs.launchpad.net/bugs/1538333 Title: AssertionError in manifest.py: assert filecount == len(self.files_changed) Status in Duplicity: Incomplete Status in duplicity package in Ubuntu: Confirmed Status in duplicity source package in Zesty: Fix Released Bug description: Duplicity was almost finishing a full backup to a FTP server. When I restarted the backup, the following error occured: root@MyMachine:~# duply MyProfile backup Start duply v1.11, time is 2016-01-26 23:38:21. Using profile '/root/.duply/MyProfile'. Using installed duplicity version 0.7.06, python 2.7.3, gpg 1.4.12 (Home: ~/.gnupg), awk 'mawk 1.3.3 Nov 1996, Copyright (C) Michael D. Brennan', grep 'grep (GNU grep) 2.12', bash 'GNU bash, Version 4.2.37(1)-release (i486-pc-linux-gnu)'. Autoset found secret key of first GPG_KEY entry '' for signing. Checking TEMP_DIR '/tmp' is a folder and writable (OK) Test - Encrypt to '' & Sign with '' (OK) Test - Decrypt (OK) Test - Compare (OK) Cleanup - Delete '/tmp/duply.16938.1453847902_*'(OK) --- Start running command PRE at 23:38:24.349 --- Skipping n/a script '/root/.duply/MyProfile/pre'. --- Finished state OK at 23:38:24.400 - Runtime 00:00:00.051 --- --- Start running command BKP at 23:38:24.447 --- LFTP version is 4.3.6 Reading globbing filelist /root/.duply/MyProfile/exclude Local and Remote metadata are synchronized, no sync needed. Traceback (most recent call last): File "/usr/local/bin/duplicity", line 1532, in with_tempdir(main) File "/usr/local/bin/duplicity", line 1526, in with_tempdir fn() File "/usr/local/bin/duplicity", line 1380, in main do_backup(action) File "/usr/local/bin/duplicity", line 1405, in do_backup globals.archive_dir).set_values() File "/usr/local/lib/python2.7/dist-packages/duplicity/collections.py", line 710, in set_values self.get_backup_chains(partials + backend_filename_list) File "/usr/local/lib/python2.7/dist-packages/duplicity/collections.py", line 835, in get_backup_chains add_to_sets(f) File "/usr/local/lib/python2.7/dist-packages/duplicity/collections.py", line 829, in add_to_sets if new_set.add_filename(filename): File "/usr/local/lib/python2.7/dist-packages/duplicity/collections.py", line 101, in add_filename self.set_manifest(filename) File "/usr/local/lib/python2.7/dist-packages/duplicity/collections.py", line 149, in set_manifest self.set_files_changed() File "/usr/local/lib/python2.7/dist-packages/duplicity/collections.py", line 128, in set_files_changed mf = self.get_manifest() File "/usr/local/lib/python2.7/dist-packages/duplicity/collections.py", line 250, in get_manifest return self.get_local_manifest() File "/usr/local/lib/python2.7/dist-packages/duplicity/collections.py", line 225, in get_local_manifest return manifest.Manifest().from_string(manifest_buffer) File "/usr/local/lib/python2.7/dist-packages/duplicity/manifest.py", line 207, in from_string assert filecount == len(self.files_changed) AssertionError 23:38:36.860 Task 'BKP' failed with exit code '30'. --- Finished state FAILED 'code 30' at 23:38:36.860 - Runtime 00:00:12.412 --- --- Start running command POST at 23:38:36.930 --- Skipping n/a script '/root/.duply/MyProfile/post'. --- Finished state OK at 23:38:36.983 - Runtime 00:00:00.052 --- Probably the version of python got updated in the meantime, but I'm not sure about this. Similar tickets, eventually this bug report is a duplicate of those: - https://bugs.launchpad.net/duplicity/+bug/1485579 - https://bugzilla.redhat.com/show_bug.cgi?id=1288702 To manage notifications about this bug go to: https://bugs.launchpad.net/duplicity/+bug/1538333/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1699800] Re: Extension Library Watcher causes Banshee to stall
Confirmed on Ubuntu 16.10 ** Changed in: banshee (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to banshee in Ubuntu. https://bugs.launchpad.net/bugs/1699800 Title: Extension Library Watcher causes Banshee to stall Status in banshee package in Ubuntu: Confirmed Bug description: The extension Library Watcher causes Banshee to stall and do nothing even when closed and ran again. To reproduce this bug go to Preferences in the Edit menu and there in the Extensions tab click the checkmark for Library Watcher. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: banshee 2.9.0+really2.6.2-7ubuntu2 ProcVersionSignature: Ubuntu 4.8.0-56.61~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-56-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 CurrentDesktop: Unity Date: Thu Jun 22 09:45:26 2017 InstallationDate: Installed on 2017-06-20 (1 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) SourcePackage: banshee UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/banshee/+bug/1699800/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1699800] Re: Extension Library Watcher causes Banshee to stall
Basically, edit file $HOME/.config/banshee-1/addin-db-001/config.xml changing the value of Banshee.LibraryWatcher,1.0 to False -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to banshee in Ubuntu. https://bugs.launchpad.net/bugs/1699800 Title: Extension Library Watcher causes Banshee to stall Status in banshee package in Ubuntu: Confirmed Bug description: The extension Library Watcher causes Banshee to stall and do nothing even when closed and ran again. To reproduce this bug go to Preferences in the Edit menu and there in the Extensions tab click the checkmark for Library Watcher. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: banshee 2.9.0+really2.6.2-7ubuntu2 ProcVersionSignature: Ubuntu 4.8.0-56.61~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-56-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 CurrentDesktop: Unity Date: Thu Jun 22 09:45:26 2017 InstallationDate: Installed on 2017-06-20 (1 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) SourcePackage: banshee UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/banshee/+bug/1699800/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1699800] Re: Extension Library Watcher causes Banshee to stall
As workaround to take back control of banshee without reinstalling it $ sed -i 's/Addin id="Banshee.LibraryWatcher,1.0" enabled="True"/Addin id="Banshee.LibraryWatcher,1.0" enabled="False"/g' $HOME/.config/banshee-1/addin-db-001/config.xml -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to banshee in Ubuntu. https://bugs.launchpad.net/bugs/1699800 Title: Extension Library Watcher causes Banshee to stall Status in banshee package in Ubuntu: Confirmed Bug description: The extension Library Watcher causes Banshee to stall and do nothing even when closed and ran again. To reproduce this bug go to Preferences in the Edit menu and there in the Extensions tab click the checkmark for Library Watcher. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: banshee 2.9.0+really2.6.2-7ubuntu2 ProcVersionSignature: Ubuntu 4.8.0-56.61~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-56-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 CurrentDesktop: Unity Date: Thu Jun 22 09:45:26 2017 InstallationDate: Installed on 2017-06-20 (1 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) SourcePackage: banshee UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/banshee/+bug/1699800/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1699599] Re: [FTBFS] libqmi 1.18.0-1 fails test during build time
** Description changed: After the Debian sync that update libqmi from 1.16.2-1 to 1.18.0-1, the package FTBFS due to a new step in the test setup for the test-generated suite. From the buildlogs: TEST: test-generated... (pid=17634) /libqmi-glib/generated/core: (/<>/src/libqmi-glib/test/.libs/test-generated:17634): GLib-CRITICAL **: g_file_test: assertion 'filename != NULL' failed FAIL Backtrace: #0 0x77113ff1 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x771152ed in g_logv () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7711544f in g_log () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x770fa42a in g_file_test () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x77a1ca03 in __qmi_utils_get_driver (cdc_wdm_path=) at qmi-utils.c:746 #5 0x77a21be7 in device_open_context_step (ctx=0x5576b0f0) at qmi-device.c:2157 #6 0x7b5e in test_fixture_setup (fixture=0x5576ba00) at test-fixture.c:156 #7 0x771352c5 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #8 0x7713549f in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #9 0x7713549f in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #10 0x771356ae in g_test_run_suite () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #11 0x771356d1 in g_test_run () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #12 0x7352 in main (argc=, argv=) at test-generated.c:665 strace: lstat("/sys", {st_dev=makedev(0, 18), st_ino=1, st_mode=S_IFDIR|0555, st_nlink=13, st_uid=0, st_gid=0, st_blksize=4096, st_blocks=0, st_size=0, st_atime=2017-06-21T16:17:32+.691480392, st_mtime=2017-06-19T06:48:49+.50419, st_ctime=2017-06-19T06:48:49+.50419}) = 0 lstat("/sys/class", {st_dev=makedev(0, 18), st_ino=10, st_mode=S_IFDIR|0755, st_nlink=73, st_uid=0, st_gid=0, st_blksize=4096, st_blocks=0, st_size=0, st_atime=2017-06-21T15:46:45+.176007545, st_mtime=2017-06-19T06:48:49+.532000158, st_ctime=2017-06-19T06:48:49+.532000158}) = 0 lstat("/sys/class/usbmisc", {st_dev=makedev(0, 18), st_ino=107497, st_mode=S_IFDIR|0755, st_nlink=2, st_uid=0, st_gid=0, st_blksize=4096, st_blocks=0, st_size=0, st_atime=2017-06-21T15:46:45+.27699, st_mtime=2017-06-21T15:46:45+.196007673, st_ctime=2017-06-21T15:46:45+.196007673}) = 0 lstat("/sys/class/usbmisc/qmi00031419", 0x7ffc6fc9ec20) = -1 ENOENT (No such file or directory) getpeername(2, 0x7ffc6fc9e800, [128]) = -1 ENOTSOCK (Socket operation on non-socket) futex(0x7f2423d66e28, FUTEX_WAKE_PRIVATE, 2147483647) = 0 ioctl(2, TCGETS, {c_iflags=0x4500, c_oflags=0x5, c_cflags=0xbf, c_lflags=0x8a3b, c_line=0, c_cc="\x03\x1c\x7f\x15\x04\x00\x01\x00\x11\x13\x1a\x00\x12\x0f\x17\x16\x00\x00\x00"}) = 0 brk(0x5567ac071000) = 0x5567ac071000 brk(0x5567ac069000) = 0x5567ac069000 write(2, "\n(/build/libqmi-cr4ivg/libqmi-1.18.0/src/libqmi-glib/test/.libs/test-generated:31419): GLib-\33[1;35mCRITICAL\33[0m **: g_file_test: assertion 'filename != NULL' failed\n", 165) = 165 --- SIGTRAP {si_signo=SIGTRAP, si_code=SI_KERNEL} --- +++ killed by SIGTRAP (core dumped) +++ The following (snipped) patch introduced the new test that is now failing: --- libqmi-1.16.2/src/libqmi-glib/qmi-utils.c 2016-07-13 07:27:23.0 -0700 +++ libqmi-1.18.0/src/libqmi-glib/qmi-utils.c 2017-03-21 06:26:54.0 -0700 @@ -1078,27 +720,49 @@ /*/ +gchar * +__qmi_utils_get_driver (const gchar *cdc_wdm_path) +{ +static const gchar *subsystems[] = { "usbmisc", "usb" }; +guint i; +gchar *device_basename; +gchar *driver = NULL; + +device_basename = g_path_get_basename (cdc_wdm_path); + +for (i = 0; !driver && i < G_N_ELEMENTS (subsystems); i++) { +gchar *tmp; +gchar *path; + +/* driver sysfs can be built directly using subsystem and name; e.g. for subsystem + * usbmisc and name cdc-wdm0: + *$ realpath /sys/class/usbmisc/cdc-wdm0/device/driver + */sys/bus/usb/drivers/qmi_wwan + */ +tmp = g_strdup_printf ("/sys/class/%s/%s/device/driver", subsystems[i], device_basename); +path = canonicalize_file_name (tmp); +g_free (tmp); + +if (g_file_test (path, G_FILE_TEST_EXISTS)) +driver = g_path_get_basename (path); +g_free (path); +} + +g_free (device_basename); + +return driver; +} + +/*/ --- libqmi-1.16.2/src/libqmi-glib/qmi-device.c 2016-11-07 01:58:29.0 -0800 +++ libqmi-1.18.0/src/libqmi-glib/qmi-device.c 2017-03-21 06:26:54.0 -0700 @@ -2285,6 +2153,60 @@
[Desktop-packages] [Bug 1699800] Re: Extension Library Watcher causes Banshee to stall
** Bug watch added: GNOME Bug Tracker #784095 https://bugzilla.gnome.org/show_bug.cgi?id=784095 ** Also affects: banshee via https://bugzilla.gnome.org/show_bug.cgi?id=784095 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to banshee in Ubuntu. https://bugs.launchpad.net/bugs/1699800 Title: Extension Library Watcher causes Banshee to stall Status in Banshee: Unknown Status in banshee package in Ubuntu: Confirmed Bug description: The extension Library Watcher causes Banshee to stall and do nothing even when closed and ran again. To reproduce this bug go to Preferences in the Edit menu and there in the Extensions tab click the checkmark for Library Watcher. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: banshee 2.9.0+really2.6.2-7ubuntu2 ProcVersionSignature: Ubuntu 4.8.0-56.61~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-56-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 CurrentDesktop: Unity Date: Thu Jun 22 09:45:26 2017 InstallationDate: Installed on 2017-06-20 (1 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) SourcePackage: banshee UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/banshee/+bug/1699800/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1699599] Re: [FTBFS] libqmi 1.18.0-1 fails test during build time
** Description changed: After the Debian sync that update libqmi from 1.16.2-1 to 1.18.0-1, the package FTBFS due to a new step in the test setup for the test-generated suite. - From the buildlogs: - + == Current FTBFS (from the our artful buildlog) == TEST: test-generated... (pid=17634) /libqmi-glib/generated/core: (/<>/src/libqmi-glib/test/.libs/test-generated:17634): GLib-CRITICAL **: g_file_test: assertion 'filename != NULL' failed FAIL - Backtrace: + + == Expected (from Debian's buildlog) == + TEST: test-generated... (pid=8773) + /libqmi-glib/generated/core: OK + /libqmi-glib/generated/dms/get-ids: OK + /libqmi-glib/generated/dms/uim-get-pin-status: OK + /libqmi-glib/generated/dms/uim-verify-pin: OK + /libqmi-glib/generated/dms/get-time: OK + /libqmi-glib/generated/nas/network-scan: OK + /libqmi-glib/generated/nas/get-cell-location-info: OK + PASS: test-generated + + + == Backtrace == #0 0x77113ff1 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x771152ed in g_logv () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7711544f in g_log () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x770fa42a in g_file_test () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x77a1ca03 in __qmi_utils_get_driver (cdc_wdm_path=) at qmi-utils.c:746 #5 0x77a21be7 in device_open_context_step (ctx=0x5576b0f0) at qmi-device.c:2157 #6 0x7b5e in test_fixture_setup (fixture=0x5576ba00) at test-fixture.c:156 #7 0x771352c5 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #8 0x7713549f in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #9 0x7713549f in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #10 0x771356ae in g_test_run_suite () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #11 0x771356d1 in g_test_run () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #12 0x7352 in main (argc=, argv=) at test-generated.c:665 - strace: + == strace == lstat("/sys", {st_dev=makedev(0, 18), st_ino=1, st_mode=S_IFDIR|0555, st_nlink=13, st_uid=0, st_gid=0, st_blksize=4096, st_blocks=0, st_size=0, st_atime=2017-06-21T16:17:32+.691480392, st_mtime=2017-06-19T06:48:49+.50419, st_ctime=2017-06-19T06:48:49+.50419}) = 0 lstat("/sys/class", {st_dev=makedev(0, 18), st_ino=10, st_mode=S_IFDIR|0755, st_nlink=73, st_uid=0, st_gid=0, st_blksize=4096, st_blocks=0, st_size=0, st_atime=2017-06-21T15:46:45+.176007545, st_mtime=2017-06-19T06:48:49+.532000158, st_ctime=2017-06-19T06:48:49+.532000158}) = 0 lstat("/sys/class/usbmisc", {st_dev=makedev(0, 18), st_ino=107497, st_mode=S_IFDIR|0755, st_nlink=2, st_uid=0, st_gid=0, st_blksize=4096, st_blocks=0, st_size=0, st_atime=2017-06-21T15:46:45+.27699, st_mtime=2017-06-21T15:46:45+.196007673, st_ctime=2017-06-21T15:46:45+.196007673}) = 0 lstat("/sys/class/usbmisc/qmi00031419", 0x7ffc6fc9ec20) = -1 ENOENT (No such file or directory) getpeername(2, 0x7ffc6fc9e800, [128]) = -1 ENOTSOCK (Socket operation on non-socket) futex(0x7f2423d66e28, FUTEX_WAKE_PRIVATE, 2147483647) = 0 ioctl(2, TCGETS, {c_iflags=0x4500, c_oflags=0x5, c_cflags=0xbf, c_lflags=0x8a3b, c_line=0, c_cc="\x03\x1c\x7f\x15\x04\x00\x01\x00\x11\x13\x1a\x00\x12\x0f\x17\x16\x00\x00\x00"}) = 0 brk(0x5567ac071000) = 0x5567ac071000 brk(0x5567ac069000) = 0x5567ac069000 write(2, "\n(/build/libqmi-cr4ivg/libqmi-1.18.0/src/libqmi-glib/test/.libs/test-generated:31419): GLib-\33[1;35mCRITICAL\33[0m **: g_file_test: assertion 'filename != NULL' failed\n", 165) = 165 --- SIGTRAP {si_signo=SIGTRAP, si_code=SI_KERNEL} --- +++ killed by SIGTRAP (core dumped) +++ - The following (snipped) patch introduced the new test that is now - failing: + + == Error source == + The following (snipped) patch introduced the new test that is now failing: --- libqmi-1.16.2/src/libqmi-glib/qmi-utils.c 2016-07-13 07:27:23.0 -0700 +++ libqmi-1.18.0/src/libqmi-glib/qmi-utils.c 2017-03-21 06:26:54.0 -0700 @@ -1078,27 +720,49 @@ /*/ +gchar * +__qmi_utils_get_driver (const gchar *cdc_wdm_path) +{ +static const gchar *subsystems[] = { "usbmisc", "usb" }; +guint i; +gchar *device_basename; +gchar *driver = NULL; + +device_basename = g_path_get_basename (cdc_wdm_path); + +for (i = 0; !driver && i < G_N_ELEMENTS (subsystems); i++) { +gchar *tmp; +gchar *path; + +/* driver sysfs can be built directly using subsystem and name; e.g. for subsystem + * usbmisc and name c
[Desktop-packages] [Bug 996270] Re: Firefox very slow, buggy, drop-down menus don't work
Having trouble getting drop down menus to work and fire fox repeatedly crashes all open programs -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/996270 Title: Firefox very slow, buggy, drop-down menus don't work Status in firefox package in Ubuntu: Confirmed Bug description: After upgrading to 11.10 from 10.04, Firefox has caused many problems: It freezes too often when opening a new tab or scrolling down the open window. When it freezes everything else freezes and the entire OS crashes. None of the menus even pop up or drop down. All I see is a grey little box. Due to this problem, I can't even report a bug. Let me know what I can do. 1. Ubuntu 11.10 2. Firefox 12.0+build1-0ubuntu0.11.10.1 3. Expect the effective/efficient Firefox from Lucid Lynx for multi-purpose use. 4. Bug riddled version that just does not work. Thanks in advance. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/996270/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1699599] Re: libqmi 1.18.0-1 FTBFS on artful due to test failure
** Summary changed: - [FTBFS] libqmi 1.18.0-1 fails test during build time + libqmi 1.18.0-1 FTBFS on artful due to test failure -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libqmi in Ubuntu. https://bugs.launchpad.net/bugs/1699599 Title: libqmi 1.18.0-1 FTBFS on artful due to test failure Status in libqmi package in Ubuntu: New Bug description: After the Debian sync that update libqmi from 1.16.2-1 to 1.18.0-1, the package FTBFS due to a new step in the test setup for the test- generated suite. == Current FTBFS (from the our artful buildlog) == TEST: test-generated... (pid=17634) /libqmi-glib/generated/core: (/<>/src/libqmi-glib/test/.libs/test-generated:17634): GLib-CRITICAL **: g_file_test: assertion 'filename != NULL' failed FAIL == Expected (from Debian's buildlog) == TEST: test-generated... (pid=8773) /libqmi-glib/generated/core: OK /libqmi-glib/generated/dms/get-ids: OK /libqmi-glib/generated/dms/uim-get-pin-status: OK /libqmi-glib/generated/dms/uim-verify-pin: OK /libqmi-glib/generated/dms/get-time: OK /libqmi-glib/generated/nas/network-scan: OK /libqmi-glib/generated/nas/get-cell-location-info: OK PASS: test-generated == Backtrace == #0 0x77113ff1 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x771152ed in g_logv () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7711544f in g_log () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x770fa42a in g_file_test () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x77a1ca03 in __qmi_utils_get_driver (cdc_wdm_path=) at qmi-utils.c:746 #5 0x77a21be7 in device_open_context_step (ctx=0x5576b0f0) at qmi-device.c:2157 #6 0x7b5e in test_fixture_setup (fixture=0x5576ba00) at test-fixture.c:156 #7 0x771352c5 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #8 0x7713549f in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #9 0x7713549f in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #10 0x771356ae in g_test_run_suite () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #11 0x771356d1 in g_test_run () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #12 0x7352 in main (argc=, argv=) at test-generated.c:665 == strace == lstat("/sys", {st_dev=makedev(0, 18), st_ino=1, st_mode=S_IFDIR|0555, st_nlink=13, st_uid=0, st_gid=0, st_blksize=4096, st_blocks=0, st_size=0, st_atime=2017-06-21T16:17:32+.691480392, st_mtime=2017-06-19T06:48:49+.50419, st_ctime=2017-06-19T06:48:49+.50419}) = 0 lstat("/sys/class", {st_dev=makedev(0, 18), st_ino=10, st_mode=S_IFDIR|0755, st_nlink=73, st_uid=0, st_gid=0, st_blksize=4096, st_blocks=0, st_size=0, st_atime=2017-06-21T15:46:45+.176007545, st_mtime=2017-06-19T06:48:49+.532000158, st_ctime=2017-06-19T06:48:49+.532000158}) = 0 lstat("/sys/class/usbmisc", {st_dev=makedev(0, 18), st_ino=107497, st_mode=S_IFDIR|0755, st_nlink=2, st_uid=0, st_gid=0, st_blksize=4096, st_blocks=0, st_size=0, st_atime=2017-06-21T15:46:45+.27699, st_mtime=2017-06-21T15:46:45+.196007673, st_ctime=2017-06-21T15:46:45+.196007673}) = 0 lstat("/sys/class/usbmisc/qmi00031419", 0x7ffc6fc9ec20) = -1 ENOENT (No such file or directory) getpeername(2, 0x7ffc6fc9e800, [128]) = -1 ENOTSOCK (Socket operation on non-socket) futex(0x7f2423d66e28, FUTEX_WAKE_PRIVATE, 2147483647) = 0 ioctl(2, TCGETS, {c_iflags=0x4500, c_oflags=0x5, c_cflags=0xbf, c_lflags=0x8a3b, c_line=0, c_cc="\x03\x1c\x7f\x15\x04\x00\x01\x00\x11\x13\x1a\x00\x12\x0f\x17\x16\x00\x00\x00"}) = 0 brk(0x5567ac071000) = 0x5567ac071000 brk(0x5567ac069000) = 0x5567ac069000 write(2, "\n(/build/libqmi-cr4ivg/libqmi-1.18.0/src/libqmi-glib/test/.libs/test-generated:31419): GLib-\33[1;35mCRITICAL\33[0m **: g_file_test: assertion 'filename != NULL' failed\n", 165) = 165 --- SIGTRAP {si_signo=SIGTRAP, si_code=SI_KERNEL} --- +++ killed by SIGTRAP (core dumped) +++ == Error source == The following (snipped) patch introduced the new test that is now failing: --- libqmi-1.16.2/src/libqmi-glib/qmi-utils.c 2016-07-13 07:27:23.0 -0700 +++ libqmi-1.18.0/src/libqmi-glib/qmi-utils.c 2017-03-21 06:26:54.0 -0700 @@ -1078,27 +720,49 @@ /*/ +gchar * +__qmi_utils_get_driver (const gchar *cdc_wdm_path) +{ +static const gchar *subsystems[] = { "usbmisc", "usb" }; +guint i; +gchar *device_basename; +gchar *driver = NULL; + +device_basename = g_path_get_basename (cdc_wdm_path
[Desktop-packages] [Bug 1673258] Re: Remove aptdaemon and drop or port its reverse-dependencies
** No longer affects: update-notifier (Ubuntu Artful) ** No longer affects: update-manager (Ubuntu Artful) ** No longer affects: ubuntu-mate-welcome (Ubuntu Artful) ** No longer affects: ubuntu-mate-meta (Ubuntu Artful) ** No longer affects: ubiquity (Ubuntu Artful) ** No longer affects: software-properties (Ubuntu Artful) ** No longer affects: sessioninstaller (Ubuntu Artful) ** No longer affects: mythbuntu-control-centre (Ubuntu Artful) ** No longer affects: lubuntu-software-center (Ubuntu Artful) ** No longer affects: language-selector (Ubuntu Artful) ** No longer affects: aptdaemon (Ubuntu Artful) ** No longer affects: apturl (Ubuntu Artful) ** No longer affects: dell-recovery (Ubuntu Artful) ** No longer affects: gnome-software (Ubuntu Artful) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to language-selector in Ubuntu. https://bugs.launchpad.net/bugs/1673258 Title: Remove aptdaemon and drop or port its reverse-dependencies Status in aptdaemon package in Ubuntu: New Status in apturl package in Ubuntu: New Status in dell-recovery package in Ubuntu: New Status in gnome-software package in Ubuntu: New Status in language-selector package in Ubuntu: New Status in lubuntu-software-center package in Ubuntu: New Status in mythbuntu-control-centre package in Ubuntu: New Status in sessioninstaller package in Ubuntu: New Status in software-properties package in Ubuntu: New Status in ubiquity package in Ubuntu: New Status in ubuntu-mate-meta package in Ubuntu: New Status in ubuntu-mate-welcome package in Ubuntu: New Status in update-manager package in Ubuntu: New Status in update-notifier package in Ubuntu: New Status in zeroinstall-injector package in Ubuntu: Fix Released Bug description: aptdaemon is abandoned and unmaintained. It has already been dropped from Debian, but there are several reverse dependencies keeping it in Ubuntu. I will add bug tasks for each of those dependencies, which should be ported or dropped themselves. Then we can get rid of aptdaemon too. See this mailing list thread for more details: https://lists.ubuntu.com/archives/ubuntu-devel/2017-March/039722.html https://bitbucket.org/ubuntu-mate/ubuntu-mate-welcome/issues/48/port- from-aptdaemon-to-packagekit To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aptdaemon/+bug/1673258/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 241736] Re: support EPUB format
And nine years later still no support for ebook. That's what I call active development. Seriously guys, is really that difficult to simply implement a new format??? In NINE YEARS??? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/241736 Title: support EPUB format Status in Evince: Confirmed Status in evince package in Ubuntu: Triaged Bug description: Binary package hint: evince 1) lsb_release -rd Description: Ubuntu Vivid Vervet (development branch) Release: 15.04 2) apt-cache policy evince evince: Installed: 3.14.1-0ubuntu1 Candidate: 3.14.1-0ubuntu1 Version table: *** 3.14.1-0ubuntu1 0 500 http://us.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages 100 /var/lib/dpkg/status 3) What is expected to happen is when one attempts to open an epub file via evince, it does so successfully. 4) What happens instead with the example attachment https://bugs.launchpad.net/ubuntu/+source/evince/+bug/241736/+attachment/4280564/+files/EPUBBestPractices-1_0.epub is evince notes: File type electronic book document (application/epub+zip) is not supported WORKAROUND: Use okular with okular-extra-backends. apt-cache policy okular okular-extra-backends okular: Installed: 4:4.13.3-0ubuntu0.1 Candidate: 4:4.13.3-0ubuntu0.1 Version table: *** 4:4.13.3-0ubuntu0.1 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/universe amd64 Packages 100 /var/lib/dpkg/status 4:4.13.0-0ubuntu1 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty/universe amd64 Packages okular-extra-backends: Installed: 4:4.13.3-0ubuntu0.1 Candidate: 4:4.13.3-0ubuntu0.1 Version table: *** 4:4.13.3-0ubuntu0.1 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/universe amd64 Packages 100 /var/lib/dpkg/status 4:4.13.0-0ubuntu1 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty/universe amd64 Packages WORKAROUND: Use fbreader. apt-cache policy fbreader fbreader: Installed: 0.12.10dfsg-9.1 Candidate: 0.12.10dfsg-9.1 Version table: *** 0.12.10dfsg-9.1 0 500 http://us.archive.ubuntu.com/ubuntu/ vivid/universe amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/evince/+bug/241736/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1699844] [NEW] Onboard settings and scanning problem
Public bug reported: I´ve configured scanning option on onboard. In Version 0.97 there was a bug that doesn´t open keyboard with such configuration In this version (1.4.1) i´m trying to open onboard-settings and it gives me the error: Traceback (most recent call last): File "", line 2, in File "/usr/lib/python3/dist-packages/Onboard/settings.py", line 311, in __init__ builder = LoadUI("settings") File "/usr/lib/python3/dist-packages/Onboard/settings.py", line 71, in LoadUI builder.add_from_file(os.path.join(config.install_dir, filebase+".ui")) File "/usr/lib/python3/dist-packages/gi/types.py", line 43, in function return info.invoke(*args, **kwargs) gi._glib.GError: /usr/share/onboard/settings.ui:2126:1 requires attribute "id" ** Affects: onboard (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to onboard in Ubuntu. https://bugs.launchpad.net/bugs/1699844 Title: Onboard settings and scanning problem Status in onboard package in Ubuntu: New Bug description: I´ve configured scanning option on onboard. In Version 0.97 there was a bug that doesn´t open keyboard with such configuration In this version (1.4.1) i´m trying to open onboard-settings and it gives me the error: Traceback (most recent call last): File "", line 2, in File "/usr/lib/python3/dist-packages/Onboard/settings.py", line 311, in __init__ builder = LoadUI("settings") File "/usr/lib/python3/dist-packages/Onboard/settings.py", line 71, in LoadUI builder.add_from_file(os.path.join(config.install_dir, filebase+".ui")) File "/usr/lib/python3/dist-packages/gi/types.py", line 43, in function return info.invoke(*args, **kwargs) gi._glib.GError: /usr/share/onboard/settings.ui:2126:1 requires attribute "id" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/onboard/+bug/1699844/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1675202] Re: Error Code: F7363-1260 trying to use Netflix on Firefox
I keep getting error code F7363-1260 when trying to use netflix ** Changed in: firefox (Ubuntu) Status: Invalid => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1675202 Title: Error Code: F7363-1260 trying to use Netflix on Firefox Status in firefox package in Ubuntu: Confirmed Bug description: How to watch Netflix using Firefox normally? ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: firefox 52.0.1+build2-0ubuntu0.16.04.1 ProcVersionSignature: Ubuntu 4.8.0-41.44~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-41-generic i686 AddonCompatCheckDisabled: False ApportVersion: 2.20.1-0ubuntu2.5 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tomasz 1555 F pulseaudio BuildID: 20170317212436 Channel: Unavailable CurrentDesktop: Unity Date: Wed Mar 22 23:13:07 2017 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2017-03-21 (1 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release i386 (20170215.2) IpRoute: default via 192.168.1.1 dev wlp5s0 proto static metric 600 169.254.0.0/16 dev wlp5s0 scope link metric 1000 192.168.1.0/24 dev wlp5s0 proto kernel scope link src 192.168.1.103 metric 600 Locales: extensions.sqlite corrupt or missing Plugins: Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so PrefSources: prefs.js [Profile]/extensions/flashli...@stephennolan.com.au/defaults/preferences/prefs.js ProcEnviron: LANGUAGE=pl PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash Profiles: Profile0 (Default) - LastVersion=52.0.1/20170317212436 (In use) RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no RunningIncompatibleAddons: False SourcePackage: firefox Themes: extensions.sqlite corrupt or missing UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/08/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 207 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: K50IN dmi.board.vendor: ASUSTeK Computer Inc. dmi.board.version: 1.0 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer Inc. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr207:bd05/08/2009:svnASUSTeKComputerInc.:pnK50IN:pvr1.0:rvnASUSTeKComputerInc.:rnK50IN:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr: dmi.product.name: K50IN dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK Computer Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1675202/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1576581] Re: New Firefox release hogging CPU
following the firefox PID {{{ top - 11:46:42 up 1 day, 13:37, 3 users, load average: 4.20, 4.02, 4.04 Threads: 64 total, 3 running, 61 sleeping, 0 stopped, 0 zombie %Cpu(s): 20.5 us, 9.1 sy, 0.0 ni, 64.7 id, 5.6 wa, 0.0 hi, 0.0 si, 0.0 st KiB Mem : 32777012 total, 4357160 free, 12640692 used, 15779160 buff/cache KiB Swap:0 total,0 free,0 used. 18872148 avail Mem PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 12094 fermula+ 20 0 2886256 657056 130136 R 90.3 2.0 6:14.75 DOM Worker <--- THIS 11838 fermula+ 20 0 2886256 657056 130136 R 50.3 2.0 3:21.63 Timer 11819 fermula+ 20 0 2886256 657056 130136 R 5.3 2.0 1:33.61 firefox 11853 fermula+ 20 0 2886256 657056 130136 S 0.7 2.0 0:00.77 JS Helper 11889 fermula+ 20 0 2886256 657056 130136 S 0.7 2.0 0:01.42 GLXVsyncThread 11890 fermula+ 20 0 2886256 657056 130136 S 0.7 2.0 0:02.52 GLXVsyncThread 11844 fermula+ 20 0 2886256 657056 130136 S 0.3 2.0 0:00.87 JS Helper 11848 fermula+ 20 0 2886256 657056 130136 S 0.3 2.0 0:00.89 JS Helper 11850 fermula+ 20 0 2886256 657056 130136 S 0.3 2.0 0:00.95 JS Helper 11880 fermula+ 20 0 2886256 657056 130136 S 0.3 2.0 0:04.57 Compositor }}} -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1576581 Title: New Firefox release hogging CPU Status in firefox package in Ubuntu: Confirmed Bug description: Since the new Firefox release into 16.04 yesterday [1] Firefox is constantly using more than 100% CPU. [1] https://launchpad.net/ubuntu/+source/firefox/46.0+build5-0ubuntu0.16.04.2 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: firefox 46.0+build5-0ubuntu0.16.04.2 ProcVersionSignature: Ubuntu 4.4.0-22.38-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: michal 8674 F pulseaudio /dev/snd/controlC0: michal 8674 F pulseaudio BrokenPermissions: greasefi...@b0nk3rz.net/indexes/exclude.dat (0o400) greasefi...@b0nk3rz.net/indexes/include.dat (0o400) greasefi...@b0nk3rz.net/indexes/info.ini (0o400) greasefi...@b0nk3rz.net/indexes/scripts.db (0o400) BuildID: 20160425114621 Channel: Unavailable CurrentDesktop: Unity Date: Fri Apr 29 10:35:53 2016 ForcedLayersAccel: False IncompatibleExtensions: Polski Language Pack - langpack...@firefox.mozilla.org Default - {972ce4c6-7e08-4474-a285-3208198ce6fd} Plugins: Google Talk Plugin Video Renderer - /opt/google/talkplugin/libnpo1d.so (google-talkplugin) Google Talk Plugin - /opt/google/talkplugin/libnpgoogletalk.so (google-talkplugin) Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so IcedTea-Web Plugin (using IcedTea-Web 1.6.2 (1.6.2-3ubuntu1)) - /usr/lib/jvm/java-8-openjdk-amd64/jre/lib/amd64/IcedTeaPlugin.so (icedtea-8-plugin) PrefSources: prefs.js [Profile]/extensions/https-everywhere-...@eff.org/defaults/preferences/preferences.js Profiles: Profile0 (Default) - LastVersion=46.0/20160425114621 (In use) RelatedPackageVersions: google-talkplugin 5.41.0.0-1 icedtea-8-plugin 1.6.2-3ubuntu1 RunningIncompatibleAddons: True SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/15/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A06 dmi.board.name: XPS 12-9Q33 dmi.board.vendor: Dell Inc. dmi.board.version: A06 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA06:bd04/15/2014:svnDellInc.:pnXPS12-9Q33:pvrA06:rvnDellInc
[Desktop-packages] [Bug 1576581] Re: New Firefox release hogging CPU
$ dpkg --list | grep firefox ii firefox 54.0+build3-0ubuntu0.16.04.1 amd64Safe and easy web browser from Mozilla -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1576581 Title: New Firefox release hogging CPU Status in firefox package in Ubuntu: Confirmed Bug description: Since the new Firefox release into 16.04 yesterday [1] Firefox is constantly using more than 100% CPU. [1] https://launchpad.net/ubuntu/+source/firefox/46.0+build5-0ubuntu0.16.04.2 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: firefox 46.0+build5-0ubuntu0.16.04.2 ProcVersionSignature: Ubuntu 4.4.0-22.38-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: michal 8674 F pulseaudio /dev/snd/controlC0: michal 8674 F pulseaudio BrokenPermissions: greasefi...@b0nk3rz.net/indexes/exclude.dat (0o400) greasefi...@b0nk3rz.net/indexes/include.dat (0o400) greasefi...@b0nk3rz.net/indexes/info.ini (0o400) greasefi...@b0nk3rz.net/indexes/scripts.db (0o400) BuildID: 20160425114621 Channel: Unavailable CurrentDesktop: Unity Date: Fri Apr 29 10:35:53 2016 ForcedLayersAccel: False IncompatibleExtensions: Polski Language Pack - langpack...@firefox.mozilla.org Default - {972ce4c6-7e08-4474-a285-3208198ce6fd} Plugins: Google Talk Plugin Video Renderer - /opt/google/talkplugin/libnpo1d.so (google-talkplugin) Google Talk Plugin - /opt/google/talkplugin/libnpgoogletalk.so (google-talkplugin) Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so IcedTea-Web Plugin (using IcedTea-Web 1.6.2 (1.6.2-3ubuntu1)) - /usr/lib/jvm/java-8-openjdk-amd64/jre/lib/amd64/IcedTeaPlugin.so (icedtea-8-plugin) PrefSources: prefs.js [Profile]/extensions/https-everywhere-...@eff.org/defaults/preferences/preferences.js Profiles: Profile0 (Default) - LastVersion=46.0/20160425114621 (In use) RelatedPackageVersions: google-talkplugin 5.41.0.0-1 icedtea-8-plugin 1.6.2-3ubuntu1 RunningIncompatibleAddons: True SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/15/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A06 dmi.board.name: XPS 12-9Q33 dmi.board.vendor: Dell Inc. dmi.board.version: A06 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA06:bd04/15/2014:svnDellInc.:pnXPS12-9Q33:pvrA06:rvnDellInc.:rnXPS12-9Q33:rvrA06:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: XPS 12-9Q33 dmi.product.version: A06 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1576581/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1699599] Re: libqmi 1.18.0-1 FTBFS on artful due to test failure
** Tags added: ftbfs -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libqmi in Ubuntu. https://bugs.launchpad.net/bugs/1699599 Title: libqmi 1.18.0-1 FTBFS on artful due to test failure Status in libqmi package in Ubuntu: New Bug description: After the Debian sync that update libqmi from 1.16.2-1 to 1.18.0-1, the package FTBFS due to a new step in the test setup for the test- generated suite. == Current FTBFS (from the our artful buildlog) == TEST: test-generated... (pid=17634) /libqmi-glib/generated/core: (/<>/src/libqmi-glib/test/.libs/test-generated:17634): GLib-CRITICAL **: g_file_test: assertion 'filename != NULL' failed FAIL == Expected (from Debian's buildlog) == TEST: test-generated... (pid=8773) /libqmi-glib/generated/core: OK /libqmi-glib/generated/dms/get-ids: OK /libqmi-glib/generated/dms/uim-get-pin-status: OK /libqmi-glib/generated/dms/uim-verify-pin: OK /libqmi-glib/generated/dms/get-time: OK /libqmi-glib/generated/nas/network-scan: OK /libqmi-glib/generated/nas/get-cell-location-info: OK PASS: test-generated == Backtrace == #0 0x77113ff1 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x771152ed in g_logv () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7711544f in g_log () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x770fa42a in g_file_test () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x77a1ca03 in __qmi_utils_get_driver (cdc_wdm_path=) at qmi-utils.c:746 #5 0x77a21be7 in device_open_context_step (ctx=0x5576b0f0) at qmi-device.c:2157 #6 0x7b5e in test_fixture_setup (fixture=0x5576ba00) at test-fixture.c:156 #7 0x771352c5 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #8 0x7713549f in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #9 0x7713549f in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #10 0x771356ae in g_test_run_suite () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #11 0x771356d1 in g_test_run () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #12 0x7352 in main (argc=, argv=) at test-generated.c:665 == strace == lstat("/sys", {st_dev=makedev(0, 18), st_ino=1, st_mode=S_IFDIR|0555, st_nlink=13, st_uid=0, st_gid=0, st_blksize=4096, st_blocks=0, st_size=0, st_atime=2017-06-21T16:17:32+.691480392, st_mtime=2017-06-19T06:48:49+.50419, st_ctime=2017-06-19T06:48:49+.50419}) = 0 lstat("/sys/class", {st_dev=makedev(0, 18), st_ino=10, st_mode=S_IFDIR|0755, st_nlink=73, st_uid=0, st_gid=0, st_blksize=4096, st_blocks=0, st_size=0, st_atime=2017-06-21T15:46:45+.176007545, st_mtime=2017-06-19T06:48:49+.532000158, st_ctime=2017-06-19T06:48:49+.532000158}) = 0 lstat("/sys/class/usbmisc", {st_dev=makedev(0, 18), st_ino=107497, st_mode=S_IFDIR|0755, st_nlink=2, st_uid=0, st_gid=0, st_blksize=4096, st_blocks=0, st_size=0, st_atime=2017-06-21T15:46:45+.27699, st_mtime=2017-06-21T15:46:45+.196007673, st_ctime=2017-06-21T15:46:45+.196007673}) = 0 lstat("/sys/class/usbmisc/qmi00031419", 0x7ffc6fc9ec20) = -1 ENOENT (No such file or directory) getpeername(2, 0x7ffc6fc9e800, [128]) = -1 ENOTSOCK (Socket operation on non-socket) futex(0x7f2423d66e28, FUTEX_WAKE_PRIVATE, 2147483647) = 0 ioctl(2, TCGETS, {c_iflags=0x4500, c_oflags=0x5, c_cflags=0xbf, c_lflags=0x8a3b, c_line=0, c_cc="\x03\x1c\x7f\x15\x04\x00\x01\x00\x11\x13\x1a\x00\x12\x0f\x17\x16\x00\x00\x00"}) = 0 brk(0x5567ac071000) = 0x5567ac071000 brk(0x5567ac069000) = 0x5567ac069000 write(2, "\n(/build/libqmi-cr4ivg/libqmi-1.18.0/src/libqmi-glib/test/.libs/test-generated:31419): GLib-\33[1;35mCRITICAL\33[0m **: g_file_test: assertion 'filename != NULL' failed\n", 165) = 165 --- SIGTRAP {si_signo=SIGTRAP, si_code=SI_KERNEL} --- +++ killed by SIGTRAP (core dumped) +++ == Error source == The following (snipped) patch introduced the new test that is now failing: --- libqmi-1.16.2/src/libqmi-glib/qmi-utils.c 2016-07-13 07:27:23.0 -0700 +++ libqmi-1.18.0/src/libqmi-glib/qmi-utils.c 2017-03-21 06:26:54.0 -0700 @@ -1078,27 +720,49 @@ /*/ +gchar * +__qmi_utils_get_driver (const gchar *cdc_wdm_path) +{ +static const gchar *subsystems[] = { "usbmisc", "usb" }; +guint i; +gchar *device_basename; +gchar *driver = NULL; + +device_basename = g_path_get_basename (cdc_wdm_path); + +for (i = 0; !driver && i < G_N_ELEMENTS (subsystems); i++) { +gchar *tmp; +
[Desktop-packages] [Bug 1699847] [NEW] package texlive-base 2015.20160320-1 failed to install/upgrade: package texlive-base is not ready for configuration cannot configure (current status 'half-instal
Public bug reported: Just report it ProblemType: Package DistroRelease: Ubuntu 16.04 Package: texlive-base 2015.20160320-1 ProcVersionSignature: Ubuntu 4.8.0-56.61~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-56-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 Date: Thu Jun 22 19:13:25 2017 ErrorMessage: package texlive-base is not ready for configuration cannot configure (current status 'half-installed') InstallationDate: Installed on 2017-06-12 (9 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: texlive-base Title: package texlive-base 2015.20160320-1 failed to install/upgrade: package texlive-base is not ready for configuration cannot configure (current status 'half-installed') UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.libpaper.d.texlive-base: [deleted] modified.conffile..etc.texmf.texdoctk.texdocrc.defaults: [deleted] ** Affects: texlive-base (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to texlive-base in Ubuntu. https://bugs.launchpad.net/bugs/1699847 Title: package texlive-base 2015.20160320-1 failed to install/upgrade: package texlive-base is not ready for configuration cannot configure (current status 'half-installed') Status in texlive-base package in Ubuntu: New Bug description: Just report it ProblemType: Package DistroRelease: Ubuntu 16.04 Package: texlive-base 2015.20160320-1 ProcVersionSignature: Ubuntu 4.8.0-56.61~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-56-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 Date: Thu Jun 22 19:13:25 2017 ErrorMessage: package texlive-base is not ready for configuration cannot configure (current status 'half-installed') InstallationDate: Installed on 2017-06-12 (9 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: texlive-base Title: package texlive-base 2015.20160320-1 failed to install/upgrade: package texlive-base is not ready for configuration cannot configure (current status 'half-installed') UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.libpaper.d.texlive-base: [deleted] modified.conffile..etc.texmf.texdoctk.texdocrc.defaults: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/texlive-base/+bug/1699847/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1007744] Re: transmission-qt does not have translation
As the translation dirs are wrong when compiling against Qt5 the files aren't found when running transmission-qt. A fix is pretty easy taking a look here: https://github.com/ds9-common/transmission/commit/42c47add88006c5d8a038cf36a3d4bcc3e281274 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to transmission in Ubuntu. https://bugs.launchpad.net/bugs/1007744 Title: transmission-qt does not have translation Status in Transmission: Unknown Status in Ubuntu Translations: Triaged Status in transmission package in Ubuntu: Triaged Bug description: dword@dword-as4741g:~$ lsb_release -rd Description:Ubuntu 12.04 LTS Release:12.04 dword@dword-as4741g:~$ apt-cache policy transmission-qt transmission-qt: 已安装: 2.52-0ubuntu0.12.04.1 候选软件包:2.52-0ubuntu0.12.04.1 版本列表: *** 2.52-0ubuntu0.12.04.1 0 500 http://ppa.launchpad.net/transmissionbt/ppa/ubuntu/ precise/main amd64 Packages 100 /var/lib/dpkg/status 2.51-0ubuntu1 0 500 http://archive.ubuntu.com/ubuntu/ precise/main amd64 Packages It seems that although transmission-gtk is well translated, transmission-qt is not translated at all. The QT based GUI is always shown in English. To manage notifications about this bug go to: https://bugs.launchpad.net/transmission/+bug/1007744/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1699854] [NEW] package libwinpr-handle0.1:amd64 1.1.0~git20140921.1.440916e+dfsg1-10ubuntu1 failed to install/upgrade: O pacote está num estado de inconsistência muito mau; dev
Public bug reported: Bug ProblemType: Package DistroRelease: Ubuntu 17.04 Package: libwinpr-handle0.1:amd64 1.1.0~git20140921.1.440916e+dfsg1-10ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-24.28-generic 4.10.15 Uname: Linux 4.10.0-24-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.1 AptOrdering: libwinpr-handle0.1:amd64: Remove libavahi-ui-gtk3-0:amd64: Remove libfreerdp-primitives1.1:amd64: Remove libwinpr-sysinfo0.1:amd64: Remove NULL: ConfigurePending Architecture: amd64 Date: Thu Jun 22 13:52:31 2017 Dependencies: gcc-6-base 6.3.0-12ubuntu2 libc6 2.24-9ubuntu2.2 libgcc1 1:6.3.0-12ubuntu2 DpkgTerminalLog: dpkg: erro ao processar o pacote libwinpr-handle0.1:amd64 (--remove): O pacote está num estado de inconsistência muito mau; deve reinstalá-lo antes de tentar a remoção. ErrorMessage: O pacote está num estado de inconsistência muito mau; deve reinstalá-lo antes de tentar a remoção. InstallationDate: Installed on 2017-06-07 (14 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412) RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4 SourcePackage: freerdp Title: package libwinpr-handle0.1:amd64 1.1.0~git20140921.1.440916e+dfsg1-10ubuntu1 failed to install/upgrade: O pacote está num estado de inconsistência muito mau; deve reinstalá-lo antes de tentar a remoção. UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: freerdp (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package zesty -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to freerdp in Ubuntu. https://bugs.launchpad.net/bugs/1699854 Title: package libwinpr-handle0.1:amd64 1.1.0~git20140921.1.440916e+dfsg1-10ubuntu1 failed to install/upgrade: O pacote está num estado de inconsistência muito mau; deve reinstalá- lo antes de tentar a remoção. Status in freerdp package in Ubuntu: New Bug description: Bug ProblemType: Package DistroRelease: Ubuntu 17.04 Package: libwinpr-handle0.1:amd64 1.1.0~git20140921.1.440916e+dfsg1-10ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-24.28-generic 4.10.15 Uname: Linux 4.10.0-24-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.1 AptOrdering: libwinpr-handle0.1:amd64: Remove libavahi-ui-gtk3-0:amd64: Remove libfreerdp-primitives1.1:amd64: Remove libwinpr-sysinfo0.1:amd64: Remove NULL: ConfigurePending Architecture: amd64 Date: Thu Jun 22 13:52:31 2017 Dependencies: gcc-6-base 6.3.0-12ubuntu2 libc6 2.24-9ubuntu2.2 libgcc1 1:6.3.0-12ubuntu2 DpkgTerminalLog: dpkg: erro ao processar o pacote libwinpr-handle0.1:amd64 (--remove): O pacote está num estado de inconsistência muito mau; deve reinstalá-lo antes de tentar a remoção. ErrorMessage: O pacote está num estado de inconsistência muito mau; deve reinstalá-lo antes de tentar a remoção. InstallationDate: Installed on 2017-06-07 (14 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412) RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4 SourcePackage: freerdp Title: package libwinpr-handle0.1:amd64 1.1.0~git20140921.1.440916e+dfsg1-10ubuntu1 failed to install/upgrade: O pacote está num estado de inconsistência muito mau; deve reinstalá-lo antes de tentar a remoção. UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/freerdp/+bug/1699854/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1283003] Re: Bluetooth headset/speakers listed but not selectable in Sound settings
Can we get an update for Zesty? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio 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: Fix Committed 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 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. To manage notifications about this bug go to: https://bugs.launchpad.net/blueman/+bug/1283003/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1007744] Re: transmission-qt does not have translation
Thanks Leszek! I've prepared a debdiff and asked for sponsoring. ** Bug watch added: Transmission Trac #4050 https://trac.transmissionbt.com/ticket/4050 ** Changed in: transmission Remote watch: Transmission Trac #7299 => Transmission Trac #4050 ** Bug watch added: Debian Bug tracker #771164 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771164 ** Also affects: transmission (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771164 Importance: Unknown Status: Unknown ** Patch added: "transmission_translation-fix.debdiff" https://bugs.launchpad.net/debian/+source/transmission/+bug/1007744/+attachment/4901118/+files/transmission_translation-fix.debdiff ** Changed in: transmission (Ubuntu) Status: Triaged => In Progress ** Changed in: transmission (Ubuntu) Assignee: (unassigned) => Gunnar Hjalmarsson (gunnarhj) ** Tags removed: saucy ** Tags added: patch ** Bug watch removed: Transmission Trac #7299 https://trac.transmissionbt.com/ticket/7299 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to transmission in Ubuntu. https://bugs.launchpad.net/bugs/1007744 Title: transmission-qt does not have translation Status in Transmission: Unknown Status in Ubuntu Translations: Triaged Status in transmission package in Ubuntu: In Progress Status in transmission package in Debian: Unknown Bug description: dword@dword-as4741g:~$ lsb_release -rd Description:Ubuntu 12.04 LTS Release:12.04 dword@dword-as4741g:~$ apt-cache policy transmission-qt transmission-qt: 已安装: 2.52-0ubuntu0.12.04.1 候选软件包:2.52-0ubuntu0.12.04.1 版本列表: *** 2.52-0ubuntu0.12.04.1 0 500 http://ppa.launchpad.net/transmissionbt/ppa/ubuntu/ precise/main amd64 Packages 100 /var/lib/dpkg/status 2.51-0ubuntu1 0 500 http://archive.ubuntu.com/ubuntu/ precise/main amd64 Packages It seems that although transmission-gtk is well translated, transmission-qt is not translated at all. The QT based GUI is always shown in English. To manage notifications about this bug go to: https://bugs.launchpad.net/transmission/+bug/1007744/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1633380] Re: package cups-browsed 1.8.3-2ubuntu3.1 failed to install/upgrade: подпроцесс установлен сценарий post-installation возвратил код ошибки 1
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: cups-filters (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups-filters in Ubuntu. https://bugs.launchpad.net/bugs/1633380 Title: package cups-browsed 1.8.3-2ubuntu3.1 failed to install/upgrade: подпроцесс установлен сценарий post-installation возвратил код ошибки 1 Status in cups-filters package in Ubuntu: Confirmed Bug description: Help me please ProblemType: Package DistroRelease: Ubuntu 16.04 Package: cups-browsed 1.8.3-2ubuntu3.1 ProcVersionSignature: Ubuntu 4.4.0-43.63-generic 4.4.21 Uname: Linux 4.4.0-43-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CupsErrorLog: Date: Fri Oct 14 11:38:58 2016 ErrorMessage: подпроцесс установлен сценарий post-installation возвратил код ошибки 1 InstallationDate: Installed on 2016-10-12 (1 days ago) InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: Bad file descriptor MachineType: SAMSUNG ELECTRONICS CO., LTD. 300E5EV/300E4EV/270E5EV/270E4EV Papersize: a4 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-43-generic root=UUID=14a9cab6-f083-497f-a700-537d7adbcd31 ro quiet splash vt.handoff=7 RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.12~ubuntu16.04.1 SourcePackage: cups-filters Title: package cups-browsed 1.8.3-2ubuntu3.1 failed to install/upgrade: подпроцесс установлен сценарий post-installation возвратил код ошибки 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/03/2013 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: P05RBF dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: NP270E5V-K03RU dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: FAB1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrP05RBF:bd05/03/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn300E5EV/300E4EV/270E5EV/270E4EV:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP270E5V-K03RU:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1: dmi.product.name: 300E5EV/300E4EV/270E5EV/270E4EV dmi.product.version: 0.1 dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1633380/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 241937] Re: Handle tabs like other gnome apps
** Changed in: firefox Importance: Wishlist => Medium -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/241937 Title: Handle tabs like other gnome apps Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: Confirmed Bug description: Binary package hint: firefox-3.0 I have noticed that dragging tabs in Firefox does not work like in other gnome apps. Basically, you can drag tabs along the tab bar to change their order, like in so many gnome apps. But you can also drag them up and down: if you accidentally drag them up and drop them on the bookmark bar, you add a bookmark for it. and if you accidentally drag it down to the browser area, you load that page again. As you can see in the attached screenshot, the "good" area is quite small compared to the "bad" areas, so it's actually very easy to miss and drop the tab on a wrong place, and perform an action you didn't want. I propose that tabs in Firefox should behave just like gnome apps, and be able to move only left or right. If you don't agree because you like being able to easily adding a bookmark or loading a page, think that the same exact effect can be achieved by dragging the favicon instead of the tab. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/241937/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1694225] Re: [Thinkpad T450s] Click lock effect on trackpoint left button when touchpad is disabled
@anders: Have you tried the kernel 4.12 on fedora? If you still see the issue on fedora, I think the kernel v4.12 fix from redhat/fedora only solves issue in synaptics trackpad (my T450s uses synaptics trackpad so it works on my side). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-synaptics in Ubuntu. https://bugs.launchpad.net/bugs/1694225 Title: [Thinkpad T450s] Click lock effect on trackpoint left button when touchpad is disabled Status in xserver-xorg-input-synaptics package in Ubuntu: Confirmed Bug description: Click lock is a behavior where you do a button click once, the system will register the click as "holding the button". In laptop Thinkpad T450s I have an issue where the disabled touchpad sometimes could trigger the click lock when clicking the trackpoint (red pointing stick)'s left button. Basically it happens randomly when my palm is touching the touchpad while I'm clicking the trackpoint left button. But I found a way to make the bug occurs easily: 1. Disable the touchpad first. You can do this from ubuntu's "Mouse & Touchpad" setting. 2. Put your two fingers on the touchpad (whether your two fingers are tapping or pressing the clickpad, it doesn't matter). You could use your left hand's index and middle finger for this. 3. While your left hand's two fingers are on the touchpad, use your right hand to click the trackpoint's left button once (don't hold it) on the desktop area, then immediately move the cursor with the pointing stick. 4. If the click lock effect gets triggered, you would see you make a selection drag on the desktop area. If the click lock doesn't happen, repeat again the step 3. The evtest log on the trackpoint: $evtest /dev/input/event15 Input driver version is 1.0.1 Input device ID: bus 0x11 vendor 0x2 product 0xa version 0x0 Input device name: "TPPS/2 IBM TrackPoint" Supported events: Event type 0 (EV_SYN) Event type 1 (EV_KEY) Event code 272 (BTN_LEFT) Event code 273 (BTN_RIGHT) Event code 274 (BTN_MIDDLE) Event type 2 (EV_REL) Event code 0 (REL_X) Event code 1 (REL_Y) Properties: Property type 0 (INPUT_PROP_POINTER) Property type 5 (INPUT_PROP_POINTING_STICK) Testing ... (interrupt to exit) Event: time 1496047216.720823, type 1 (EV_KEY), code 272 (BTN_LEFT), value 1 Event: time 1496047216.720823, -- SYN_REPORT Event: time 1496047216.778898, type 1 (EV_KEY), code 272 (BTN_LEFT), value 0 Event: time 1496047216.778898, -- SYN_REPORT Event: time 1496047220.234518, type 1 (EV_KEY), code 272 (BTN_LEFT), value 1 Event: time 1496047220.234518, -- SYN_REPORT If the click lock is not triggered, you would see BTN_LEFT's value 1 & 0: Event: time 1496047216.720823, type 1 (EV_KEY), code 272 (BTN_LEFT), value 1 Event: time 1496047216.778898, type 1 (EV_KEY), code 272 (BTN_LEFT), value 0 But if the click lock is triggered, you would only see value 1: Event: time 1496047220.234518, type 1 (EV_KEY), code 272 (BTN_LEFT), value 1 I am guessing "value 0" means release the button. So when click lock is happening, the button left is not released at all, thus it's producing "hold the button" effect. More Informations: This issue doesn't happen on other OS like Windows, but I can confirm it happens on most modern linux distro and DE I've tried (e.g. ubuntu v17/v16, kubuntu, ubuntu mate, xubuntu, lubuntu, linux mint, fedora, open suse, etc). So this issue must be coming from the synaptic touchpad driver, or maybe from the kernel (?) Also, the issue doesn't occur on older thinkpad models which doesn't use same clickpad type touchpad, e.g. T430 or X230. For newer thinkpad models (e.g. T460, X260, etc) which uses same clickpad design, same issue might exists too (need confirmation though). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/1694225/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1699599] Re: libqmi 1.18.0-1 FTBFS on artful due to test failure
Tracked the error down to glib2.0 version update from 2.52.0-1 to 2.53.1-1 (and later versions). They introduced an additional NULL check to g_file_test [1] that now breaks this particular test, as the code in qmi-utils.c provides a NULL `path` to g_file_test. [1] https://bugzilla.gnome.org/show_bug.cgi?id=755046 ** Bug watch added: GNOME Bug Tracker #755046 https://bugzilla.gnome.org/show_bug.cgi?id=755046 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libqmi in Ubuntu. https://bugs.launchpad.net/bugs/1699599 Title: libqmi 1.18.0-1 FTBFS on artful due to test failure Status in libqmi package in Ubuntu: New Bug description: After the Debian sync that update libqmi from 1.16.2-1 to 1.18.0-1, the package FTBFS due to a new step in the test setup for the test- generated suite. == Current FTBFS (from the our artful buildlog) == TEST: test-generated... (pid=17634) /libqmi-glib/generated/core: (/<>/src/libqmi-glib/test/.libs/test-generated:17634): GLib-CRITICAL **: g_file_test: assertion 'filename != NULL' failed FAIL == Expected (from Debian's buildlog) == TEST: test-generated... (pid=8773) /libqmi-glib/generated/core: OK /libqmi-glib/generated/dms/get-ids: OK /libqmi-glib/generated/dms/uim-get-pin-status: OK /libqmi-glib/generated/dms/uim-verify-pin: OK /libqmi-glib/generated/dms/get-time: OK /libqmi-glib/generated/nas/network-scan: OK /libqmi-glib/generated/nas/get-cell-location-info: OK PASS: test-generated == Backtrace == #0 0x77113ff1 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x771152ed in g_logv () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7711544f in g_log () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x770fa42a in g_file_test () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x77a1ca03 in __qmi_utils_get_driver (cdc_wdm_path=) at qmi-utils.c:746 #5 0x77a21be7 in device_open_context_step (ctx=0x5576b0f0) at qmi-device.c:2157 #6 0x7b5e in test_fixture_setup (fixture=0x5576ba00) at test-fixture.c:156 #7 0x771352c5 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #8 0x7713549f in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #9 0x7713549f in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #10 0x771356ae in g_test_run_suite () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #11 0x771356d1 in g_test_run () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #12 0x7352 in main (argc=, argv=) at test-generated.c:665 == strace == lstat("/sys", {st_dev=makedev(0, 18), st_ino=1, st_mode=S_IFDIR|0555, st_nlink=13, st_uid=0, st_gid=0, st_blksize=4096, st_blocks=0, st_size=0, st_atime=2017-06-21T16:17:32+.691480392, st_mtime=2017-06-19T06:48:49+.50419, st_ctime=2017-06-19T06:48:49+.50419}) = 0 lstat("/sys/class", {st_dev=makedev(0, 18), st_ino=10, st_mode=S_IFDIR|0755, st_nlink=73, st_uid=0, st_gid=0, st_blksize=4096, st_blocks=0, st_size=0, st_atime=2017-06-21T15:46:45+.176007545, st_mtime=2017-06-19T06:48:49+.532000158, st_ctime=2017-06-19T06:48:49+.532000158}) = 0 lstat("/sys/class/usbmisc", {st_dev=makedev(0, 18), st_ino=107497, st_mode=S_IFDIR|0755, st_nlink=2, st_uid=0, st_gid=0, st_blksize=4096, st_blocks=0, st_size=0, st_atime=2017-06-21T15:46:45+.27699, st_mtime=2017-06-21T15:46:45+.196007673, st_ctime=2017-06-21T15:46:45+.196007673}) = 0 lstat("/sys/class/usbmisc/qmi00031419", 0x7ffc6fc9ec20) = -1 ENOENT (No such file or directory) getpeername(2, 0x7ffc6fc9e800, [128]) = -1 ENOTSOCK (Socket operation on non-socket) futex(0x7f2423d66e28, FUTEX_WAKE_PRIVATE, 2147483647) = 0 ioctl(2, TCGETS, {c_iflags=0x4500, c_oflags=0x5, c_cflags=0xbf, c_lflags=0x8a3b, c_line=0, c_cc="\x03\x1c\x7f\x15\x04\x00\x01\x00\x11\x13\x1a\x00\x12\x0f\x17\x16\x00\x00\x00"}) = 0 brk(0x5567ac071000) = 0x5567ac071000 brk(0x5567ac069000) = 0x5567ac069000 write(2, "\n(/build/libqmi-cr4ivg/libqmi-1.18.0/src/libqmi-glib/test/.libs/test-generated:31419): GLib-\33[1;35mCRITICAL\33[0m **: g_file_test: assertion 'filename != NULL' failed\n", 165) = 165 --- SIGTRAP {si_signo=SIGTRAP, si_code=SI_KERNEL} --- +++ killed by SIGTRAP (core dumped) +++ == Error source == The following (snipped) patch introduced the new test that is now failing: --- libqmi-1.16.2/src/libqmi-glib/qmi-utils.c 2016-07-13 07:27:23.0 -0700 +++ libqmi-1.18.0/src/libqmi-glib/qmi-utils.c 2017-03-21 06:26:54.0 -0700 @@ -1078,27 +720,49 @@ /*
[Desktop-packages] [Bug 1007744] Re: transmission-qt does not have translation
** Changed in: transmission (Debian) Status: Unknown => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to transmission in Ubuntu. https://bugs.launchpad.net/bugs/1007744 Title: transmission-qt does not have translation Status in Transmission: Unknown Status in Ubuntu Translations: Triaged Status in transmission package in Ubuntu: In Progress Status in transmission package in Debian: Confirmed Bug description: dword@dword-as4741g:~$ lsb_release -rd Description:Ubuntu 12.04 LTS Release:12.04 dword@dword-as4741g:~$ apt-cache policy transmission-qt transmission-qt: 已安装: 2.52-0ubuntu0.12.04.1 候选软件包:2.52-0ubuntu0.12.04.1 版本列表: *** 2.52-0ubuntu0.12.04.1 0 500 http://ppa.launchpad.net/transmissionbt/ppa/ubuntu/ precise/main amd64 Packages 100 /var/lib/dpkg/status 2.51-0ubuntu1 0 500 http://archive.ubuntu.com/ubuntu/ precise/main amd64 Packages It seems that although transmission-gtk is well translated, transmission-qt is not translated at all. The QT based GUI is always shown in English. To manage notifications about this bug go to: https://bugs.launchpad.net/transmission/+bug/1007744/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1699599] Re: libqmi 1.18.0-1 FTBFS when building against glib2.0-2.53.1-1 (or later)
** Summary changed: - libqmi 1.18.0-1 FTBFS on artful due to test failure + libqmi 1.18.0-1 FTBFS when building against glib2.0-2.53.1-1 (or later) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libqmi in Ubuntu. https://bugs.launchpad.net/bugs/1699599 Title: libqmi 1.18.0-1 FTBFS when building against glib2.0-2.53.1-1 (or later) Status in libqmi package in Ubuntu: New Bug description: After the Debian sync that update libqmi from 1.16.2-1 to 1.18.0-1, the package FTBFS due to a new step in the test setup for the test- generated suite. == Current FTBFS (from the our artful buildlog) == TEST: test-generated... (pid=17634) /libqmi-glib/generated/core: (/<>/src/libqmi-glib/test/.libs/test-generated:17634): GLib-CRITICAL **: g_file_test: assertion 'filename != NULL' failed FAIL == Expected (from Debian's buildlog) == TEST: test-generated... (pid=8773) /libqmi-glib/generated/core: OK /libqmi-glib/generated/dms/get-ids: OK /libqmi-glib/generated/dms/uim-get-pin-status: OK /libqmi-glib/generated/dms/uim-verify-pin: OK /libqmi-glib/generated/dms/get-time: OK /libqmi-glib/generated/nas/network-scan: OK /libqmi-glib/generated/nas/get-cell-location-info: OK PASS: test-generated == Backtrace == #0 0x77113ff1 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x771152ed in g_logv () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7711544f in g_log () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x770fa42a in g_file_test () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x77a1ca03 in __qmi_utils_get_driver (cdc_wdm_path=) at qmi-utils.c:746 #5 0x77a21be7 in device_open_context_step (ctx=0x5576b0f0) at qmi-device.c:2157 #6 0x7b5e in test_fixture_setup (fixture=0x5576ba00) at test-fixture.c:156 #7 0x771352c5 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #8 0x7713549f in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #9 0x7713549f in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #10 0x771356ae in g_test_run_suite () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #11 0x771356d1 in g_test_run () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #12 0x7352 in main (argc=, argv=) at test-generated.c:665 == strace == lstat("/sys", {st_dev=makedev(0, 18), st_ino=1, st_mode=S_IFDIR|0555, st_nlink=13, st_uid=0, st_gid=0, st_blksize=4096, st_blocks=0, st_size=0, st_atime=2017-06-21T16:17:32+.691480392, st_mtime=2017-06-19T06:48:49+.50419, st_ctime=2017-06-19T06:48:49+.50419}) = 0 lstat("/sys/class", {st_dev=makedev(0, 18), st_ino=10, st_mode=S_IFDIR|0755, st_nlink=73, st_uid=0, st_gid=0, st_blksize=4096, st_blocks=0, st_size=0, st_atime=2017-06-21T15:46:45+.176007545, st_mtime=2017-06-19T06:48:49+.532000158, st_ctime=2017-06-19T06:48:49+.532000158}) = 0 lstat("/sys/class/usbmisc", {st_dev=makedev(0, 18), st_ino=107497, st_mode=S_IFDIR|0755, st_nlink=2, st_uid=0, st_gid=0, st_blksize=4096, st_blocks=0, st_size=0, st_atime=2017-06-21T15:46:45+.27699, st_mtime=2017-06-21T15:46:45+.196007673, st_ctime=2017-06-21T15:46:45+.196007673}) = 0 lstat("/sys/class/usbmisc/qmi00031419", 0x7ffc6fc9ec20) = -1 ENOENT (No such file or directory) getpeername(2, 0x7ffc6fc9e800, [128]) = -1 ENOTSOCK (Socket operation on non-socket) futex(0x7f2423d66e28, FUTEX_WAKE_PRIVATE, 2147483647) = 0 ioctl(2, TCGETS, {c_iflags=0x4500, c_oflags=0x5, c_cflags=0xbf, c_lflags=0x8a3b, c_line=0, c_cc="\x03\x1c\x7f\x15\x04\x00\x01\x00\x11\x13\x1a\x00\x12\x0f\x17\x16\x00\x00\x00"}) = 0 brk(0x5567ac071000) = 0x5567ac071000 brk(0x5567ac069000) = 0x5567ac069000 write(2, "\n(/build/libqmi-cr4ivg/libqmi-1.18.0/src/libqmi-glib/test/.libs/test-generated:31419): GLib-\33[1;35mCRITICAL\33[0m **: g_file_test: assertion 'filename != NULL' failed\n", 165) = 165 --- SIGTRAP {si_signo=SIGTRAP, si_code=SI_KERNEL} --- +++ killed by SIGTRAP (core dumped) +++ == Error source == The following (snipped) patch introduced the new test that is now failing: --- libqmi-1.16.2/src/libqmi-glib/qmi-utils.c 2016-07-13 07:27:23.0 -0700 +++ libqmi-1.18.0/src/libqmi-glib/qmi-utils.c 2017-03-21 06:26:54.0 -0700 @@ -1078,27 +720,49 @@ /*/ +gchar * +__qmi_utils_get_driver (const gchar *cdc_wdm_path) +{ +static const gchar *subsystems[] = { "usbmisc", "usb" }; +guint i; +gchar *device_basename; +gchar *driver = NULL; + +device_bas
[Desktop-packages] [Bug 123041] Re: Fw: give it a try
*** This bug is a duplicate of bug 89090 *** https://bugs.launchpad.net/bugs/89090 Hey friend, I have found a really nice thing recently, it is something you might find useful, please give it a try. Here is the link http://bit.do/dw83P Best Wishes, Bartolomeo Nicolotti From: Bug 123041 [mailto:123...@bugs.launchpad.net] Sent: Thursday, June 22, 2017 3:34 PM To: bart.nicolo...@libero.it Subject: DER YOU GO CARRRLOS **Steam Card INC - Please Read!** Okay guys, since a bunch of people are on "Steam Gift Code Cooldown" I'm going to give away a Steam Gift Card in 5 minutes in a different way. Post a RESPONSE to this post here with a number, 1 to 1000.I'll roll a random number, closest one WINS! 5 minutes so GOGOGO RESPOND! EDIT: Make sure your code isn't entered yet. If it is, I'll pick the first one posted. If more than 1000 people put numbers in, then I'll do again with 5000 :p Sent from Mail for Windows 10 ** Attachment added: "BA471F166D213561306D442315E72498.jpg" https://bugs.launchpad.net/bugs/123041/+attachment/4901144/+files/BA471F166D213561306D442315E72498.jpg -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/123041 Title: [EDGY] firefox crashed [@nsTextControlFrame::SetValue] [@nsTextControlFrame::SetProperty] [@nsHTMLInputElement::SetValueInternal] Status in firefox package in Ubuntu: Incomplete Bug description: Binary package hint: firefox ... Firefow Crash It happens that sometimes firefox crashes. It seems that this has begun to happen when I've installed the latest update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/123041/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1698601] Re: package flashplugin-installer 26.0.0.131ubuntu0.17.04.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before att
** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to flashplugin-nonfree in Ubuntu. https://bugs.launchpad.net/bugs/1698601 Title: package flashplugin-installer 26.0.0.131ubuntu0.17.04.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in flashplugin-nonfree package in Ubuntu: New Bug description: The bug happen when I tried do install spotify. ProblemType: Package DistroRelease: Ubuntu 17.04 Package: flashplugin-installer 26.0.0.131ubuntu0.17.04.1 ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15 Uname: Linux 4.10.0-22-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 Date: Sat Jun 17 22:57:30 2017 DuplicateSignature: package:flashplugin-installer:26.0.0.131ubuntu0.17.04.1 Processing triggers for libc-bin (2.24-9ubuntu2) ... dpkg: error processing package flashplugin-installer (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2017-06-15 (2 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4 SourcePackage: flashplugin-nonfree Title: package flashplugin-installer 26.0.0.131ubuntu0.17.04.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flashplugin-nonfree/+bug/1698601/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1698601] Re: package flashplugin-installer 26.0.0.131ubuntu0.17.04.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before att
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to flashplugin-nonfree in Ubuntu. https://bugs.launchpad.net/bugs/1698601 Title: package flashplugin-installer 26.0.0.131ubuntu0.17.04.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in flashplugin-nonfree package in Ubuntu: New Bug description: The bug happen when I tried do install spotify. ProblemType: Package DistroRelease: Ubuntu 17.04 Package: flashplugin-installer 26.0.0.131ubuntu0.17.04.1 ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15 Uname: Linux 4.10.0-22-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 Date: Sat Jun 17 22:57:30 2017 DuplicateSignature: package:flashplugin-installer:26.0.0.131ubuntu0.17.04.1 Processing triggers for libc-bin (2.24-9ubuntu2) ... dpkg: error processing package flashplugin-installer (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2017-06-15 (2 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4 SourcePackage: flashplugin-nonfree Title: package flashplugin-installer 26.0.0.131ubuntu0.17.04.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flashplugin-nonfree/+bug/1698601/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1698639] Re: graphic dont work
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1698639 Title: graphic dont work Status in xorg package in Ubuntu: New Bug description: Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged. cat: /var/log/lightdm/x-0-greeter.log: Nie ma takiego pliku ani katalogu cat: /var/log/lightdm/x-0-greeter.log.old: Nie ma takiego pliku ani katalogu Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.8.0-54.57~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-54-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: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Sun Jun 18 13:06:42 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.8.0-54-generic, x86_64: installed nvidia-381, 381.22, 4.8.0-54-generic, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 2nd Generation Core Processor Family Integrated Graphics Controller [17aa:397d] InstallationDate: Installed on 2017-06-15 (2 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) MachineType: LENOVO HuronRiver Platform ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-54-generic root=UUID=223aa3e7-2866-4e97-adde-818a33f681ad ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/15/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 45CN47WW dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Emerald Lake dmi.board.vendor: LENOVO dmi.board.version: FAB1 dmi.chassis.asset.tag: Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnLENOVO:bvr45CN47WW:bd02/15/2012:svnLENOVO:pnHuronRiverPlatform:pvrIdeapadZ570:rvnLENOVO:rnEmeraldLake:rvrFAB1:cvnLENOVO:ct10:cvr0.1: dmi.product.name: HuronRiver Platform dmi.product.version: Ideapad Z570 dmi.sys.vendor: LENOVO 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 xserver.bootTime: Sat Jun 17 16:52:14 2017 xserver.configfile: default xserver.errors: Failed to load module "nvidia" (module does not exist, 0) xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-1ubuntu6.1~16.04.1 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1698639/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1699890] Re: nautilus crashed with SIGSEGV
** Information type changed from Private to Public -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1699890 Title: nautilus crashed with SIGSEGV Status in nautilus package in Ubuntu: Invalid Bug description: I'm working and open apport... ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: nautilus 1:3.24.1-0ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15 Uname: Linux 4.10.0-22-generic x86_64 ApportVersion: 2.20.5-0ubuntu5 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Jun 22 16:17:31 2017 Disassembly: No hay registros. ExecutablePath: /usr/bin/nautilus InstallationDate: Installed on 2015-07-26 (697 days ago) InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150723) ProcCmdline: /usr/bin/nautilus --gapplication-service Registers: El programa no tiene registros ahora. SegvAnalysis: Failure: invalid literal for int() with base 16: 'programa' Signal: 11 SourcePackage: nautilus Stacktrace: No stack. StacktraceTop: ThreadStacktrace: Title: nautilus crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1699890/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1698547] Re: pasting into gnome-terminal pastes into a different terminal window
Hello and thanks for the bug report. I'm unable to reproduce this bug. Since this does not seem to be a bug that an attacker can trigger, I'm going to make the bug public in hopes that Ubuntu Desktop developers can have a look and see if they can reproduce the issue. Thanks again for the bug report! ** Information type changed from Private Security to Public Security -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1698547 Title: pasting into gnome-terminal pastes into a different terminal window Status in gnome-terminal package in Ubuntu: New Bug description: Ubuntu-Gnome 17.04, latest updates, 28 days uptime Open two or more gnome-terminal windows. Select some text and copy it (source application doesn't matter, could be a terminal, Firefox, etc.). For safety, use text without line breaks, a single character will suffice. Using middle click, paste into one gnome-terminal, then another, and so on. When the bug manifests, all paste events to any gnome-terminal go to one of the terminals. Right clicking and selecting Paste from the drop-down menu is less effective at triggering the bug, but once triggered, right-click paste is also affected. Pasting into other applications is not affected. This bug could cause potentially dangerous commands to be executed in a shell, when the intention was to paste them into a file in a different terminal. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: gnome-terminal 3.20.2-1ubuntu8 Uname: Linux 4.11.0-041100-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 Date: Sun Jun 18 00:02:46 2017 InstallationDate: Installed on 2016-12-02 (196 days ago) InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Release amd64 (20161012.1) ProcEnviron: LANGUAGE=en_AU:en TERM=xterm-256color PATH=(custom, no user) LANG=en_AU.UTF-8 SHELL=/bin/bash SourcePackage: gnome-terminal UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1698547/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1699599] Re: libqmi 1.18.0-1 FTBFS when building against glib2.0-2.53.1-1 (or later)
Upstream patch with DEP3 header. ** Bug watch added: Debian Bug tracker #865579 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865579 ** Also affects: libqmi (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865579 Importance: Unknown Status: Unknown ** Patch added: "fix-g-file-test-null-assertion.diff" https://bugs.launchpad.net/debian/+source/libqmi/+bug/1699599/+attachment/4901192/+files/fix-g-file-test-null-assertion.diff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libqmi in Ubuntu. https://bugs.launchpad.net/bugs/1699599 Title: libqmi 1.18.0-1 FTBFS when building against glib2.0-2.53.1-1 (or later) Status in libqmi package in Ubuntu: New Status in libqmi package in Debian: Unknown Bug description: After the Debian sync that update libqmi from 1.16.2-1 to 1.18.0-1, the package FTBFS due to a new step in the test setup for the test- generated suite. == Current FTBFS (from the our artful buildlog) == TEST: test-generated... (pid=17634) /libqmi-glib/generated/core: (/<>/src/libqmi-glib/test/.libs/test-generated:17634): GLib-CRITICAL **: g_file_test: assertion 'filename != NULL' failed FAIL == Expected (from Debian's buildlog) == TEST: test-generated... (pid=8773) /libqmi-glib/generated/core: OK /libqmi-glib/generated/dms/get-ids: OK /libqmi-glib/generated/dms/uim-get-pin-status: OK /libqmi-glib/generated/dms/uim-verify-pin: OK /libqmi-glib/generated/dms/get-time: OK /libqmi-glib/generated/nas/network-scan: OK /libqmi-glib/generated/nas/get-cell-location-info: OK PASS: test-generated == Backtrace == #0 0x77113ff1 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x771152ed in g_logv () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7711544f in g_log () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x770fa42a in g_file_test () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x77a1ca03 in __qmi_utils_get_driver (cdc_wdm_path=) at qmi-utils.c:746 #5 0x77a21be7 in device_open_context_step (ctx=0x5576b0f0) at qmi-device.c:2157 #6 0x7b5e in test_fixture_setup (fixture=0x5576ba00) at test-fixture.c:156 #7 0x771352c5 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #8 0x7713549f in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #9 0x7713549f in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #10 0x771356ae in g_test_run_suite () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #11 0x771356d1 in g_test_run () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #12 0x7352 in main (argc=, argv=) at test-generated.c:665 == strace == lstat("/sys", {st_dev=makedev(0, 18), st_ino=1, st_mode=S_IFDIR|0555, st_nlink=13, st_uid=0, st_gid=0, st_blksize=4096, st_blocks=0, st_size=0, st_atime=2017-06-21T16:17:32+.691480392, st_mtime=2017-06-19T06:48:49+.50419, st_ctime=2017-06-19T06:48:49+.50419}) = 0 lstat("/sys/class", {st_dev=makedev(0, 18), st_ino=10, st_mode=S_IFDIR|0755, st_nlink=73, st_uid=0, st_gid=0, st_blksize=4096, st_blocks=0, st_size=0, st_atime=2017-06-21T15:46:45+.176007545, st_mtime=2017-06-19T06:48:49+.532000158, st_ctime=2017-06-19T06:48:49+.532000158}) = 0 lstat("/sys/class/usbmisc", {st_dev=makedev(0, 18), st_ino=107497, st_mode=S_IFDIR|0755, st_nlink=2, st_uid=0, st_gid=0, st_blksize=4096, st_blocks=0, st_size=0, st_atime=2017-06-21T15:46:45+.27699, st_mtime=2017-06-21T15:46:45+.196007673, st_ctime=2017-06-21T15:46:45+.196007673}) = 0 lstat("/sys/class/usbmisc/qmi00031419", 0x7ffc6fc9ec20) = -1 ENOENT (No such file or directory) getpeername(2, 0x7ffc6fc9e800, [128]) = -1 ENOTSOCK (Socket operation on non-socket) futex(0x7f2423d66e28, FUTEX_WAKE_PRIVATE, 2147483647) = 0 ioctl(2, TCGETS, {c_iflags=0x4500, c_oflags=0x5, c_cflags=0xbf, c_lflags=0x8a3b, c_line=0, c_cc="\x03\x1c\x7f\x15\x04\x00\x01\x00\x11\x13\x1a\x00\x12\x0f\x17\x16\x00\x00\x00"}) = 0 brk(0x5567ac071000) = 0x5567ac071000 brk(0x5567ac069000) = 0x5567ac069000 write(2, "\n(/build/libqmi-cr4ivg/libqmi-1.18.0/src/libqmi-glib/test/.libs/test-generated:31419): GLib-\33[1;35mCRITICAL\33[0m **: g_file_test: assertion 'filename != NULL' failed\n", 165) = 165 --- SIGTRAP {si_signo=SIGTRAP, si_code=SI_KERNEL} --- +++ killed by SIGTRAP (core dumped) +++ == Error source == The following (snipped) patch introduced the new test that is now failing: --- libqmi-1.16.2/src/libqmi-glib/qmi-utils.c 2016-07-13 07:27:23.0 -0700 +++ libqmi-1.18.0/src/libqmi-glib/qmi-utils.c 2017-03-21 06:
[Desktop-packages] [Bug 1699599] Re: libqmi 1.18.0-1 FTBFS when building against glib2.0-2.53.1-1 (or later)
Debdiff between 1.18.0-1 (Artful) and 1.18.0-1ubuntu1 (to sponsor a new upload). ** Patch added: "libqmi_1.18.0-1_1.18.0-1ubuntu1.debdiff" https://bugs.launchpad.net/debian/+source/libqmi/+bug/1699599/+attachment/4901193/+files/libqmi_1.18.0-1_1.18.0-1ubuntu1.debdiff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libqmi in Ubuntu. https://bugs.launchpad.net/bugs/1699599 Title: libqmi 1.18.0-1 FTBFS when building against glib2.0-2.53.1-1 (or later) Status in libqmi package in Ubuntu: New Status in libqmi package in Debian: Unknown Bug description: After the Debian sync that update libqmi from 1.16.2-1 to 1.18.0-1, the package FTBFS due to a new step in the test setup for the test- generated suite. == Current FTBFS (from the our artful buildlog) == TEST: test-generated... (pid=17634) /libqmi-glib/generated/core: (/<>/src/libqmi-glib/test/.libs/test-generated:17634): GLib-CRITICAL **: g_file_test: assertion 'filename != NULL' failed FAIL == Expected (from Debian's buildlog) == TEST: test-generated... (pid=8773) /libqmi-glib/generated/core: OK /libqmi-glib/generated/dms/get-ids: OK /libqmi-glib/generated/dms/uim-get-pin-status: OK /libqmi-glib/generated/dms/uim-verify-pin: OK /libqmi-glib/generated/dms/get-time: OK /libqmi-glib/generated/nas/network-scan: OK /libqmi-glib/generated/nas/get-cell-location-info: OK PASS: test-generated == Backtrace == #0 0x77113ff1 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x771152ed in g_logv () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7711544f in g_log () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x770fa42a in g_file_test () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x77a1ca03 in __qmi_utils_get_driver (cdc_wdm_path=) at qmi-utils.c:746 #5 0x77a21be7 in device_open_context_step (ctx=0x5576b0f0) at qmi-device.c:2157 #6 0x7b5e in test_fixture_setup (fixture=0x5576ba00) at test-fixture.c:156 #7 0x771352c5 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #8 0x7713549f in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #9 0x7713549f in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #10 0x771356ae in g_test_run_suite () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #11 0x771356d1 in g_test_run () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #12 0x7352 in main (argc=, argv=) at test-generated.c:665 == strace == lstat("/sys", {st_dev=makedev(0, 18), st_ino=1, st_mode=S_IFDIR|0555, st_nlink=13, st_uid=0, st_gid=0, st_blksize=4096, st_blocks=0, st_size=0, st_atime=2017-06-21T16:17:32+.691480392, st_mtime=2017-06-19T06:48:49+.50419, st_ctime=2017-06-19T06:48:49+.50419}) = 0 lstat("/sys/class", {st_dev=makedev(0, 18), st_ino=10, st_mode=S_IFDIR|0755, st_nlink=73, st_uid=0, st_gid=0, st_blksize=4096, st_blocks=0, st_size=0, st_atime=2017-06-21T15:46:45+.176007545, st_mtime=2017-06-19T06:48:49+.532000158, st_ctime=2017-06-19T06:48:49+.532000158}) = 0 lstat("/sys/class/usbmisc", {st_dev=makedev(0, 18), st_ino=107497, st_mode=S_IFDIR|0755, st_nlink=2, st_uid=0, st_gid=0, st_blksize=4096, st_blocks=0, st_size=0, st_atime=2017-06-21T15:46:45+.27699, st_mtime=2017-06-21T15:46:45+.196007673, st_ctime=2017-06-21T15:46:45+.196007673}) = 0 lstat("/sys/class/usbmisc/qmi00031419", 0x7ffc6fc9ec20) = -1 ENOENT (No such file or directory) getpeername(2, 0x7ffc6fc9e800, [128]) = -1 ENOTSOCK (Socket operation on non-socket) futex(0x7f2423d66e28, FUTEX_WAKE_PRIVATE, 2147483647) = 0 ioctl(2, TCGETS, {c_iflags=0x4500, c_oflags=0x5, c_cflags=0xbf, c_lflags=0x8a3b, c_line=0, c_cc="\x03\x1c\x7f\x15\x04\x00\x01\x00\x11\x13\x1a\x00\x12\x0f\x17\x16\x00\x00\x00"}) = 0 brk(0x5567ac071000) = 0x5567ac071000 brk(0x5567ac069000) = 0x5567ac069000 write(2, "\n(/build/libqmi-cr4ivg/libqmi-1.18.0/src/libqmi-glib/test/.libs/test-generated:31419): GLib-\33[1;35mCRITICAL\33[0m **: g_file_test: assertion 'filename != NULL' failed\n", 165) = 165 --- SIGTRAP {si_signo=SIGTRAP, si_code=SI_KERNEL} --- +++ killed by SIGTRAP (core dumped) +++ == Error source == The following (snipped) patch introduced the new test that is now failing: --- libqmi-1.16.2/src/libqmi-glib/qmi-utils.c 2016-07-13 07:27:23.0 -0700 +++ libqmi-1.18.0/src/libqmi-glib/qmi-utils.c 2017-03-21 06:26:54.0 -0700 @@ -1078,27 +720,49 @@ /*/ +gchar * +__qmi_utils_get_driver (const gchar *cdc_wdm_pa
[Desktop-packages] [Bug 788626] Re: Error: Unable to save resume file: File name too long
Issue/bug on Transmission repo: https://github.com/transmission/transmission/issues/122 ** Bug watch added: github.com/transmission/transmission/issues #122 https://github.com/transmission/transmission/issues/122 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to transmission in Ubuntu. https://bugs.launchpad.net/bugs/788626 Title: Error: Unable to save resume file: File name too long Status in Transmission: New Status in transmission package in Ubuntu: Confirmed Bug description: Binary package hint: transmission I'm trying to download a torrent (from http://www.jamendo.com/en/album/48348) but I get the message: "Error: Unable to save resume file: File name too long" and I don't see that there is much I can do about that. It would be nice if transmission dealt with the problem itself and made up a shorter name for itself, as I have no idea how to shorten the name myself. ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: transmission-gtk 2.05-0ubuntu0.2 Uname: Linux 2.6.37-rc4-fireworks2 x86_64 Architecture: amd64 Date: Fri May 27 00:06:46 2011 EcryptfsInUse: Yes ExecutablePath: /usr/bin/transmission InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027) ProcEnviron: LANG=en_AU.utf8 SHELL=/usr/bin/zsh SourcePackage: transmission To manage notifications about this bug go to: https://bugs.launchpad.net/transmission/+bug/788626/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1699599] Re: libqmi 1.18.0-1 FTBFS when building against glib2.0-2.53.1-1 (or later)
** Changed in: libqmi (Debian) Status: Unknown => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libqmi in Ubuntu. https://bugs.launchpad.net/bugs/1699599 Title: libqmi 1.18.0-1 FTBFS when building against glib2.0-2.53.1-1 (or later) Status in libqmi package in Ubuntu: New Status in libqmi package in Debian: New Bug description: After the Debian sync that update libqmi from 1.16.2-1 to 1.18.0-1, the package FTBFS due to a new step in the test setup for the test- generated suite. == Current FTBFS (from the our artful buildlog) == TEST: test-generated... (pid=17634) /libqmi-glib/generated/core: (/<>/src/libqmi-glib/test/.libs/test-generated:17634): GLib-CRITICAL **: g_file_test: assertion 'filename != NULL' failed FAIL == Expected (from Debian's buildlog) == TEST: test-generated... (pid=8773) /libqmi-glib/generated/core: OK /libqmi-glib/generated/dms/get-ids: OK /libqmi-glib/generated/dms/uim-get-pin-status: OK /libqmi-glib/generated/dms/uim-verify-pin: OK /libqmi-glib/generated/dms/get-time: OK /libqmi-glib/generated/nas/network-scan: OK /libqmi-glib/generated/nas/get-cell-location-info: OK PASS: test-generated == Backtrace == #0 0x77113ff1 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x771152ed in g_logv () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7711544f in g_log () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x770fa42a in g_file_test () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x77a1ca03 in __qmi_utils_get_driver (cdc_wdm_path=) at qmi-utils.c:746 #5 0x77a21be7 in device_open_context_step (ctx=0x5576b0f0) at qmi-device.c:2157 #6 0x7b5e in test_fixture_setup (fixture=0x5576ba00) at test-fixture.c:156 #7 0x771352c5 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #8 0x7713549f in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #9 0x7713549f in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #10 0x771356ae in g_test_run_suite () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #11 0x771356d1 in g_test_run () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #12 0x7352 in main (argc=, argv=) at test-generated.c:665 == strace == lstat("/sys", {st_dev=makedev(0, 18), st_ino=1, st_mode=S_IFDIR|0555, st_nlink=13, st_uid=0, st_gid=0, st_blksize=4096, st_blocks=0, st_size=0, st_atime=2017-06-21T16:17:32+.691480392, st_mtime=2017-06-19T06:48:49+.50419, st_ctime=2017-06-19T06:48:49+.50419}) = 0 lstat("/sys/class", {st_dev=makedev(0, 18), st_ino=10, st_mode=S_IFDIR|0755, st_nlink=73, st_uid=0, st_gid=0, st_blksize=4096, st_blocks=0, st_size=0, st_atime=2017-06-21T15:46:45+.176007545, st_mtime=2017-06-19T06:48:49+.532000158, st_ctime=2017-06-19T06:48:49+.532000158}) = 0 lstat("/sys/class/usbmisc", {st_dev=makedev(0, 18), st_ino=107497, st_mode=S_IFDIR|0755, st_nlink=2, st_uid=0, st_gid=0, st_blksize=4096, st_blocks=0, st_size=0, st_atime=2017-06-21T15:46:45+.27699, st_mtime=2017-06-21T15:46:45+.196007673, st_ctime=2017-06-21T15:46:45+.196007673}) = 0 lstat("/sys/class/usbmisc/qmi00031419", 0x7ffc6fc9ec20) = -1 ENOENT (No such file or directory) getpeername(2, 0x7ffc6fc9e800, [128]) = -1 ENOTSOCK (Socket operation on non-socket) futex(0x7f2423d66e28, FUTEX_WAKE_PRIVATE, 2147483647) = 0 ioctl(2, TCGETS, {c_iflags=0x4500, c_oflags=0x5, c_cflags=0xbf, c_lflags=0x8a3b, c_line=0, c_cc="\x03\x1c\x7f\x15\x04\x00\x01\x00\x11\x13\x1a\x00\x12\x0f\x17\x16\x00\x00\x00"}) = 0 brk(0x5567ac071000) = 0x5567ac071000 brk(0x5567ac069000) = 0x5567ac069000 write(2, "\n(/build/libqmi-cr4ivg/libqmi-1.18.0/src/libqmi-glib/test/.libs/test-generated:31419): GLib-\33[1;35mCRITICAL\33[0m **: g_file_test: assertion 'filename != NULL' failed\n", 165) = 165 --- SIGTRAP {si_signo=SIGTRAP, si_code=SI_KERNEL} --- +++ killed by SIGTRAP (core dumped) +++ == Error source == The following (snipped) patch introduced the new test that is now failing: --- libqmi-1.16.2/src/libqmi-glib/qmi-utils.c 2016-07-13 07:27:23.0 -0700 +++ libqmi-1.18.0/src/libqmi-glib/qmi-utils.c 2017-03-21 06:26:54.0 -0700 @@ -1078,27 +720,49 @@ /*/ +gchar * +__qmi_utils_get_driver (const gchar *cdc_wdm_path) +{ +static const gchar *subsystems[] = { "usbmisc", "usb" }; +guint i; +gchar *device_basename; +gchar *driver = NULL; + +device_basename = g_path_get_basename (cdc_wdm_path);
[Desktop-packages] [Bug 606365] Re: unable to import config with inlined ca, cert, key or tls-auth
The original bug as reported was a failure to import certain configuration files using network-mangaer-openvpn. This turned out to be due to the use of inlined key material (comment 24). network-manager- openvpn did not support this as a feature at the time, so was unable to parse this type of configuration file. Support was since added (comment 46). This has been confirmed to work (comments 49, 63, 67, 68 etc). Therefore, this bug as reported has been fixed, so I'm setting it to Fix Released. It may well be that this doesn't solve configuration imports for all users, as is clear from subsequent comments. But we track one issue per bug, since otherwise statements like "this bug is fixed" and "this bug is not fixed" become meaningless, developers cannot track what they are being asked to do, and users end up with wildly varying expectations that can never be met. Note that a failure to import a configuration can be an entire class of bugs, not just one single bug. This bug's original reporter's problem turned out to be "doesn't work with inlined key material". Clearly that's not the only thing wrong here, as adding inlined key material support solved the problem for some, but not others. Of the remaining users here who still have import problems, there may yet be *multiple* underlying bugs. So please don't all pile on to a different bug thinking you're still all affected by the same issue. If you'd like to see your problem fixed, and you'd like to help, then first please read "How to Report Bugs Effectively" (https://www.chiark.greenend.org.uk/~sgtatham/bugs.html) carefully. Take some time to work out exact steps to reproduce your problem, make sure that they really do reproduce, and then paste exact and detailed instructions on how to reproduce your problem into a new bug report. Don't assume that someone else's import failure problem is due to the same underlying bug as your import failure problem. Do link to bugs that you think may be related (such as this one). Don't worry about filing duplicates; in this kind of case it takes far more effort to untangle reports that turn out to have different root causes then it does to mark duplicate bugs if this becomes clear to developers later. I hope this helps. I can't guarantee what will come next, but by filing actionable reports at least you'll be one step closer to real progress. ** Changed in: network-manager-openvpn (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-openvpn in Ubuntu. https://bugs.launchpad.net/bugs/606365 Title: unable to import config with inlined ca, cert, key or tls-auth Status in NetworkManager-OpenVPN: Fix Released Status in plasma-nm: Unknown Status in network-manager-openvpn package in Ubuntu: Fix Released Bug description: Binary package hint: network-manager-openvpn-gnome So a client of mine runs an OpenVPN setup. It exported a client.ovpn file but it fails to completely import this file using the network- manager (gnome) on Ubuntu 10.04. When I import the file, it gives me the name ("client") and gateway ("vpn.example.org") on the initial screen. No other fields are populated even though the client.ovpn file also includes a user certificate, server certifikate and a private key. When I go to advanced, some (most) of the settings obviously seem to import correct, others not at all. E.g. none of the TLS settings (key and key direction) are imported. From what I understand I should be able to use this without any additional settings. The following software is installed through aptitude: * openvpn (2.1.0) * openvpn-blacklist * network-manager-openvpn * network-manager-openvpn-gnome To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager-openvpn/+bug/606365/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1687981] Re: Backport packages for 16.04.3 HWE stack
Hello Timo, or anyone else affected, Accepted vulkan into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/vulkan/1.0.42.0+dfsg1-1ubuntu1~16.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: vulkan (Ubuntu Xenial) Status: New => Fix Committed ** Changed in: libdrm (Ubuntu Xenial) Status: New => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to x11proto-core in Ubuntu. https://bugs.launchpad.net/bugs/1687981 Title: Backport packages for 16.04.3 HWE stack Status in libclc package in Ubuntu: Invalid Status in libdrm package in Ubuntu: Invalid Status in libinput package in Ubuntu: Invalid Status in libwacom package in Ubuntu: Invalid Status in libxfont package in Ubuntu: Invalid Status in libxfont2 package in Ubuntu: Invalid Status in llvm-toolchain-4.0 package in Ubuntu: Invalid Status in mesa package in Ubuntu: New Status in vulkan package in Ubuntu: Invalid Status in wayland package in Ubuntu: Invalid Status in x11proto-core package in Ubuntu: Invalid Status in xfonts-utils package in Ubuntu: New Status in xorg-hwe-16.04 package in Ubuntu: Invalid Status in xorg-server package in Ubuntu: Invalid Status in xorg-server-hwe-16.04 package in Ubuntu: Invalid Status in libclc source package in Xenial: Fix Committed Status in libdrm source package in Xenial: Fix Committed Status in libinput source package in Xenial: New Status in libwacom source package in Xenial: Fix Committed Status in libxfont source package in Xenial: Fix Committed Status in libxfont2 source package in Xenial: Fix Committed Status in llvm-toolchain-4.0 source package in Xenial: Fix Committed Status in mesa source package in Xenial: New Status in vulkan source package in Xenial: Fix Committed Status in wayland source package in Xenial: Fix Committed Status in x11proto-core source package in Xenial: Fix Committed Status in xfonts-utils source package in Xenial: Fix Committed Status in xorg-hwe-16.04 source package in Xenial: New Status in xorg-server source package in Xenial: New Status in xorg-server-hwe-16.04 source package in Xenial: New Bug description: [Impact] *** hwe-16.04 refresh for 16.04.3 *** Revert changes to use debhelper10. xorg-server-hwe-16.04 needs updates - wayland 1.11 (but zesty has 1.12 which mesa needs so backport that) - x11proto-core 7.0.31 - libxfont-dev 2.0.1, which also means backporting libxfont1 (NEW) x-x-i-libinput will not replace -evdev in x-x-i-all-hwe-16.04 because the unity mouse config doesn't work with -libinput. x-x-i-libinput needs newer libinput, which in turn needs libwacom update. Mesa needs llvm-4.0 and libclc, libdrm, wayland updates. [Test case] upgrade from/to stock & old hwe stack, test desktop usage [Regression potential] zesty hasn't blown up [Other information] build order: 1. x11proto-core, libdrm, libxfont, libxfont1, libwacom, llvm-toolchain-4.0, vulkan, wayland 2. libclc, libinput, xorg-server (build-dep libxfont1-dev) 3. mesa, xorg-server-hwe-16.04 4. drivers 5. xorg-hwe-16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libclc/+bug/1687981/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1687981] Please test proposed package
Hello Timo, or anyone else affected, Accepted libdrm into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/libdrm/2.4.76-1~ubuntu16.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to x11proto-core in Ubuntu. https://bugs.launchpad.net/bugs/1687981 Title: Backport packages for 16.04.3 HWE stack Status in libclc package in Ubuntu: Invalid Status in libdrm package in Ubuntu: Invalid Status in libinput package in Ubuntu: Invalid Status in libwacom package in Ubuntu: Invalid Status in libxfont package in Ubuntu: Invalid Status in libxfont2 package in Ubuntu: Invalid Status in llvm-toolchain-4.0 package in Ubuntu: Invalid Status in mesa package in Ubuntu: New Status in vulkan package in Ubuntu: Invalid Status in wayland package in Ubuntu: Invalid Status in x11proto-core package in Ubuntu: Invalid Status in xfonts-utils package in Ubuntu: New Status in xorg-hwe-16.04 package in Ubuntu: Invalid Status in xorg-server package in Ubuntu: Invalid Status in xorg-server-hwe-16.04 package in Ubuntu: Invalid Status in libclc source package in Xenial: Fix Committed Status in libdrm source package in Xenial: Fix Committed Status in libinput source package in Xenial: New Status in libwacom source package in Xenial: Fix Committed Status in libxfont source package in Xenial: Fix Committed Status in libxfont2 source package in Xenial: Fix Committed Status in llvm-toolchain-4.0 source package in Xenial: Fix Committed Status in mesa source package in Xenial: New Status in vulkan source package in Xenial: Fix Committed Status in wayland source package in Xenial: Fix Committed Status in x11proto-core source package in Xenial: Fix Committed Status in xfonts-utils source package in Xenial: Fix Committed Status in xorg-hwe-16.04 source package in Xenial: New Status in xorg-server source package in Xenial: New Status in xorg-server-hwe-16.04 source package in Xenial: New Bug description: [Impact] *** hwe-16.04 refresh for 16.04.3 *** Revert changes to use debhelper10. xorg-server-hwe-16.04 needs updates - wayland 1.11 (but zesty has 1.12 which mesa needs so backport that) - x11proto-core 7.0.31 - libxfont-dev 2.0.1, which also means backporting libxfont1 (NEW) x-x-i-libinput will not replace -evdev in x-x-i-all-hwe-16.04 because the unity mouse config doesn't work with -libinput. x-x-i-libinput needs newer libinput, which in turn needs libwacom update. Mesa needs llvm-4.0 and libclc, libdrm, wayland updates. [Test case] upgrade from/to stock & old hwe stack, test desktop usage [Regression potential] zesty hasn't blown up [Other information] build order: 1. x11proto-core, libdrm, libxfont, libxfont1, libwacom, llvm-toolchain-4.0, vulkan, wayland 2. libclc, libinput, xorg-server (build-dep libxfont1-dev) 3. mesa, xorg-server-hwe-16.04 4. drivers 5. xorg-hwe-16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libclc/+bug/1687981/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1687981] Please test proposed package
Hello Timo, or anyone else affected, Accepted xfonts-utils into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/xfonts- utils/1:7.7+3ubuntu0.16.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: libclc (Ubuntu Xenial) Status: New => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to x11proto-core in Ubuntu. https://bugs.launchpad.net/bugs/1687981 Title: Backport packages for 16.04.3 HWE stack Status in libclc package in Ubuntu: Invalid Status in libdrm package in Ubuntu: Invalid Status in libinput package in Ubuntu: Invalid Status in libwacom package in Ubuntu: Invalid Status in libxfont package in Ubuntu: Invalid Status in libxfont2 package in Ubuntu: Invalid Status in llvm-toolchain-4.0 package in Ubuntu: Invalid Status in mesa package in Ubuntu: New Status in vulkan package in Ubuntu: Invalid Status in wayland package in Ubuntu: Invalid Status in x11proto-core package in Ubuntu: Invalid Status in xfonts-utils package in Ubuntu: New Status in xorg-hwe-16.04 package in Ubuntu: Invalid Status in xorg-server package in Ubuntu: Invalid Status in xorg-server-hwe-16.04 package in Ubuntu: Invalid Status in libclc source package in Xenial: Fix Committed Status in libdrm source package in Xenial: Fix Committed Status in libinput source package in Xenial: New Status in libwacom source package in Xenial: Fix Committed Status in libxfont source package in Xenial: Fix Committed Status in libxfont2 source package in Xenial: Fix Committed Status in llvm-toolchain-4.0 source package in Xenial: Fix Committed Status in mesa source package in Xenial: New Status in vulkan source package in Xenial: Fix Committed Status in wayland source package in Xenial: Fix Committed Status in x11proto-core source package in Xenial: Fix Committed Status in xfonts-utils source package in Xenial: Fix Committed Status in xorg-hwe-16.04 source package in Xenial: New Status in xorg-server source package in Xenial: New Status in xorg-server-hwe-16.04 source package in Xenial: New Bug description: [Impact] *** hwe-16.04 refresh for 16.04.3 *** Revert changes to use debhelper10. xorg-server-hwe-16.04 needs updates - wayland 1.11 (but zesty has 1.12 which mesa needs so backport that) - x11proto-core 7.0.31 - libxfont-dev 2.0.1, which also means backporting libxfont1 (NEW) x-x-i-libinput will not replace -evdev in x-x-i-all-hwe-16.04 because the unity mouse config doesn't work with -libinput. x-x-i-libinput needs newer libinput, which in turn needs libwacom update. Mesa needs llvm-4.0 and libclc, libdrm, wayland updates. [Test case] upgrade from/to stock & old hwe stack, test desktop usage [Regression potential] zesty hasn't blown up [Other information] build order: 1. x11proto-core, libdrm, libxfont, libxfont1, libwacom, llvm-toolchain-4.0, vulkan, wayland 2. libclc, libinput, xorg-server (build-dep libxfont1-dev) 3. mesa, xorg-server-hwe-16.04 4. drivers 5. xorg-hwe-16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libclc/+bug/1687981/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1687981] Re: Backport packages for 16.04.3 HWE stack
Hello Timo, or anyone else affected, Accepted libwacom into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/libwacom/0.22-1~ubuntu16.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: libwacom (Ubuntu Xenial) Status: New => Fix Committed ** Changed in: xfonts-utils (Ubuntu Xenial) Status: New => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to x11proto-core in Ubuntu. https://bugs.launchpad.net/bugs/1687981 Title: Backport packages for 16.04.3 HWE stack Status in libclc package in Ubuntu: Invalid Status in libdrm package in Ubuntu: Invalid Status in libinput package in Ubuntu: Invalid Status in libwacom package in Ubuntu: Invalid Status in libxfont package in Ubuntu: Invalid Status in libxfont2 package in Ubuntu: Invalid Status in llvm-toolchain-4.0 package in Ubuntu: Invalid Status in mesa package in Ubuntu: New Status in vulkan package in Ubuntu: Invalid Status in wayland package in Ubuntu: Invalid Status in x11proto-core package in Ubuntu: Invalid Status in xfonts-utils package in Ubuntu: New Status in xorg-hwe-16.04 package in Ubuntu: Invalid Status in xorg-server package in Ubuntu: Invalid Status in xorg-server-hwe-16.04 package in Ubuntu: Invalid Status in libclc source package in Xenial: Fix Committed Status in libdrm source package in Xenial: Fix Committed Status in libinput source package in Xenial: New Status in libwacom source package in Xenial: Fix Committed Status in libxfont source package in Xenial: Fix Committed Status in libxfont2 source package in Xenial: Fix Committed Status in llvm-toolchain-4.0 source package in Xenial: Fix Committed Status in mesa source package in Xenial: New Status in vulkan source package in Xenial: Fix Committed Status in wayland source package in Xenial: Fix Committed Status in x11proto-core source package in Xenial: Fix Committed Status in xfonts-utils source package in Xenial: Fix Committed Status in xorg-hwe-16.04 source package in Xenial: New Status in xorg-server source package in Xenial: New Status in xorg-server-hwe-16.04 source package in Xenial: New Bug description: [Impact] *** hwe-16.04 refresh for 16.04.3 *** Revert changes to use debhelper10. xorg-server-hwe-16.04 needs updates - wayland 1.11 (but zesty has 1.12 which mesa needs so backport that) - x11proto-core 7.0.31 - libxfont-dev 2.0.1, which also means backporting libxfont1 (NEW) x-x-i-libinput will not replace -evdev in x-x-i-all-hwe-16.04 because the unity mouse config doesn't work with -libinput. x-x-i-libinput needs newer libinput, which in turn needs libwacom update. Mesa needs llvm-4.0 and libclc, libdrm, wayland updates. [Test case] upgrade from/to stock & old hwe stack, test desktop usage [Regression potential] zesty hasn't blown up [Other information] build order: 1. x11proto-core, libdrm, libxfont, libxfont1, libwacom, llvm-toolchain-4.0, vulkan, wayland 2. libclc, libinput, xorg-server (build-dep libxfont1-dev) 3. mesa, xorg-server-hwe-16.04 4. drivers 5. xorg-hwe-16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libclc/+bug/1687981/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1687981] Please test proposed package
Hello Timo, or anyone else affected, Accepted libclc into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/libclc/0.2.0+git20170213-1~16.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to x11proto-core in Ubuntu. https://bugs.launchpad.net/bugs/1687981 Title: Backport packages for 16.04.3 HWE stack Status in libclc package in Ubuntu: Invalid Status in libdrm package in Ubuntu: Invalid Status in libinput package in Ubuntu: Invalid Status in libwacom package in Ubuntu: Invalid Status in libxfont package in Ubuntu: Invalid Status in libxfont2 package in Ubuntu: Invalid Status in llvm-toolchain-4.0 package in Ubuntu: Invalid Status in mesa package in Ubuntu: New Status in vulkan package in Ubuntu: Invalid Status in wayland package in Ubuntu: Invalid Status in x11proto-core package in Ubuntu: Invalid Status in xfonts-utils package in Ubuntu: New Status in xorg-hwe-16.04 package in Ubuntu: Invalid Status in xorg-server package in Ubuntu: Invalid Status in xorg-server-hwe-16.04 package in Ubuntu: Invalid Status in libclc source package in Xenial: Fix Committed Status in libdrm source package in Xenial: Fix Committed Status in libinput source package in Xenial: New Status in libwacom source package in Xenial: Fix Committed Status in libxfont source package in Xenial: Fix Committed Status in libxfont2 source package in Xenial: Fix Committed Status in llvm-toolchain-4.0 source package in Xenial: Fix Committed Status in mesa source package in Xenial: New Status in vulkan source package in Xenial: Fix Committed Status in wayland source package in Xenial: Fix Committed Status in x11proto-core source package in Xenial: Fix Committed Status in xfonts-utils source package in Xenial: Fix Committed Status in xorg-hwe-16.04 source package in Xenial: New Status in xorg-server source package in Xenial: New Status in xorg-server-hwe-16.04 source package in Xenial: New Bug description: [Impact] *** hwe-16.04 refresh for 16.04.3 *** Revert changes to use debhelper10. xorg-server-hwe-16.04 needs updates - wayland 1.11 (but zesty has 1.12 which mesa needs so backport that) - x11proto-core 7.0.31 - libxfont-dev 2.0.1, which also means backporting libxfont1 (NEW) x-x-i-libinput will not replace -evdev in x-x-i-all-hwe-16.04 because the unity mouse config doesn't work with -libinput. x-x-i-libinput needs newer libinput, which in turn needs libwacom update. Mesa needs llvm-4.0 and libclc, libdrm, wayland updates. [Test case] upgrade from/to stock & old hwe stack, test desktop usage [Regression potential] zesty hasn't blown up [Other information] build order: 1. x11proto-core, libdrm, libxfont, libxfont1, libwacom, llvm-toolchain-4.0, vulkan, wayland 2. libclc, libinput, xorg-server (build-dep libxfont1-dev) 3. mesa, xorg-server-hwe-16.04 4. drivers 5. xorg-hwe-16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libclc/+bug/1687981/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1699914] [NEW] oooooooooooooooooooooo
Public bug reported: 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 x86_64 NonfreeKernelModules: wl .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.4 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Fri Jun 23 04:06:36 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.248+bdcom, 4.4.0-31-generic, x86_64: installed bcmwl, 6.30.223.248+bdcom, 4.4.0-72-generic, x86_64: installed bcmwl, 6.30.223.248+bdcom, 4.4.0-75-generic, x86_64: installed bcmwl, 6.30.223.248+bdcom, 4.4.0-78-generic, x86_64: installed GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller [17aa:3a02] Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller [17aa:3a02] InstallationDate: Installed on 2017-04-19 (64 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: LENOVO 20023 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-78-generic root=UUID=02e0e1d1-578e-4a7a-9f63-f0cc470a2454 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/05/2010 dmi.bios.vendor: LENOVO dmi.bios.version: 18CN45WW(V2.54) dmi.board.name: NITU1 dmi.board.vendor: LENOVO dmi.board.version: REFERENCE dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnLENOVO:bvr18CN45WW(V2.54):bd05/05/2010:svnLENOVO:pn20023:pvrLenovoG550:rvnLENOVO:rnNITU1:rvrREFERENCE:cvnNoEnclosure:ct10:cvrN/A: dmi.product.name: 20023 dmi.product.version: Lenovo G550 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12.2+16.04.20160714-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.3-1ubuntu2.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 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Thu Jun 22 22:34:54 2017 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 560 vendor LGD xserver.version: 2:1.18.3-1ubuntu2.2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 third-party-packages ubuntu xenial -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1699914 Title: oo Status in xorg package in Ubuntu: New Bug description: 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 x86_64 NonfreeKernelModules: wl .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.4 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Fri Jun 23 04:06:36 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.248+bdcom, 4.4.0-31-generic, x86_64: installed bcmwl, 6.30.223.248+bdcom, 4.4.0-72-generic, x86_64: installed bcmwl, 6.30.223.248+bdcom, 4.4.0-75-generic, x86_64: installed bcmwl, 6.30.223.248+bdcom, 4.4.0-78-generic, x86_64: installed GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller [17aa:3a02] Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller [17aa:3a02] InstallationDate: Installed on 2017-04-19 (64 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: LENOVO 20023 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-78-generi
[Desktop-packages] [Bug 1698256] Re: Invalid, Meson-generated, valac arguments break the build
I upgraded to the newly released Meson build 0.41.1 (from 0.40.1), and this isn't a problem anymore... -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to simple-scan in Ubuntu. https://bugs.launchpad.net/bugs/1698256 Title: Invalid, Meson-generated, valac arguments break the build Status in simple-scan package in Ubuntu: New Bug description: I'm trying to build simple-scan according to the README file (on Arch). With colord, packagekit, and webp installed, Meson is building invalid args for the main build step, which prevents the project from building. The build declaration (meson.build) generates a Python list of vala_args. The list of args looks OK getting passed into executable(). However, the auto-generated build.ninja is missing the required -D(efine) flags. As a result, it treats some of defines as filenames, and crashes. Vala/Meson/Ninja are new to me, so I'm not sure if the problem is with the build file, or the Meson generator, or what. # ./src/meson.build # If all three packages are installed, they're built into the Python list. Somehow, the -D flags disappear during build generation vala_args = [ '--pkg=posix', '--vapidir=' + meson.current_source_dir () ] dependencies = [ glib_dep, gtk_dep, zlib_dep, cairo_dep, gdk_pixbuf_dep, gusb_dep, sane_dep ] if colord_dep.found () vala_args += [ '-D', 'HAVE_COLORD' ] dependencies += colord_dep endif if packagekit_dep.found () vala_args += [ '-D', 'HAVE_PACKAGEKIT' ] dependencies += packagekit_dep endif if webp_dep.found () and (not colord_dep.found () or webpmux_dep.found ()) # Webpmux only required if colord vala_args += [ '-D', 'HAVE_WEBP' ] dependencies += [ webp_dep, webpmux_dep ] endif simple_scan = executable ('simple-scan', [ 'config.vapi', 'app-window.vala', 'authorize-dialog.vala', 'book.vala', 'book-view.vala', 'page.vala', 'page-view.vala', 'preferences-dialog.vala', 'simple-scan.vala', 'scanner.vala', 'screensaver.vala', 'autosave-manager.vala' ] + resources, dependencies: dependencies, vala_args: vala_args, c_args: [ '-DVERSION="@0@"'.format (meson.project_version ()), '-DGETTEXT_PACKAGE="simple-scan"', '-DLOCALE_DIR="@0@"'.format (localedir), '-DICON_DIR="@0@"'.format (icondir), '-DI_KNOW_THE_PACKAGEKIT_GLIB2_API_IS_SUBJECT_TO_CHANGE' ], link_args: [ '-lm' ], install: true ) # ./build/build.ninja # Snippet of the bad build step. Note the -D flag is missing (at the end) build src/simple-scan@exe/app-window.c src/simple-scan@exe/authorize-dialog.c src/simple-scan@exe/book.c src/simple-scan@exe/book-view.c src/simple-scan@exe/page.c src/simple-scan@exe/page-view.c src/simple-scan@exe/preferences-dialog.c src/simple-scan@exe/simple-scan.c src/simple-scan@exe/scanner.c src/simple-scan@exe/screensaver.c src/simple-scan@exe/autosave-manager.c: vala_COMPILER ../src/config.vapi ../src/app-window.vala ../src/authorize-dialog.vala ../src/book.vala ../src/book-view.vala ../src/page.vala ../src/page-view.vala ../src/preferences-dialog.vala ../src/simple-scan.vala ../src/scanner.vala ../src/screensaver.vala ../src/autosave-manager.vala ARGS = -C --debug --pkg libwebpmux --pkg libwebp --pkg packagekit-glib2 --pkg colord --pkg sane-backends --pkg gusb --pkg gdk-pixbuf-2.0 --pkg cairo --pkg zlib --pkg gtk+-3.0 --target-glib '$ 2.38' --pkg glib-2.0 -d src/simple-scan@exe --gresources=../src/simple-scan.gresource.xml --pkg=posix --vapidir=/home/dan/Projects/simple-scan/src HAVE_COLORD HAVE_PACKAGEKIT -D HAVE_WEBP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/1698256/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1698256] Re: Invalid, Meson-generated, valac arguments break the build
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: simple-scan (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to simple-scan in Ubuntu. https://bugs.launchpad.net/bugs/1698256 Title: Invalid, Meson-generated, valac arguments break the build Status in simple-scan package in Ubuntu: Confirmed Bug description: I'm trying to build simple-scan according to the README file (on Arch). With colord, packagekit, and webp installed, Meson is building invalid args for the main build step, which prevents the project from building. The build declaration (meson.build) generates a Python list of vala_args. The list of args looks OK getting passed into executable(). However, the auto-generated build.ninja is missing the required -D(efine) flags. As a result, it treats some of defines as filenames, and crashes. Vala/Meson/Ninja are new to me, so I'm not sure if the problem is with the build file, or the Meson generator, or what. # ./src/meson.build # If all three packages are installed, they're built into the Python list. Somehow, the -D flags disappear during build generation vala_args = [ '--pkg=posix', '--vapidir=' + meson.current_source_dir () ] dependencies = [ glib_dep, gtk_dep, zlib_dep, cairo_dep, gdk_pixbuf_dep, gusb_dep, sane_dep ] if colord_dep.found () vala_args += [ '-D', 'HAVE_COLORD' ] dependencies += colord_dep endif if packagekit_dep.found () vala_args += [ '-D', 'HAVE_PACKAGEKIT' ] dependencies += packagekit_dep endif if webp_dep.found () and (not colord_dep.found () or webpmux_dep.found ()) # Webpmux only required if colord vala_args += [ '-D', 'HAVE_WEBP' ] dependencies += [ webp_dep, webpmux_dep ] endif simple_scan = executable ('simple-scan', [ 'config.vapi', 'app-window.vala', 'authorize-dialog.vala', 'book.vala', 'book-view.vala', 'page.vala', 'page-view.vala', 'preferences-dialog.vala', 'simple-scan.vala', 'scanner.vala', 'screensaver.vala', 'autosave-manager.vala' ] + resources, dependencies: dependencies, vala_args: vala_args, c_args: [ '-DVERSION="@0@"'.format (meson.project_version ()), '-DGETTEXT_PACKAGE="simple-scan"', '-DLOCALE_DIR="@0@"'.format (localedir), '-DICON_DIR="@0@"'.format (icondir), '-DI_KNOW_THE_PACKAGEKIT_GLIB2_API_IS_SUBJECT_TO_CHANGE' ], link_args: [ '-lm' ], install: true ) # ./build/build.ninja # Snippet of the bad build step. Note the -D flag is missing (at the end) build src/simple-scan@exe/app-window.c src/simple-scan@exe/authorize-dialog.c src/simple-scan@exe/book.c src/simple-scan@exe/book-view.c src/simple-scan@exe/page.c src/simple-scan@exe/page-view.c src/simple-scan@exe/preferences-dialog.c src/simple-scan@exe/simple-scan.c src/simple-scan@exe/scanner.c src/simple-scan@exe/screensaver.c src/simple-scan@exe/autosave-manager.c: vala_COMPILER ../src/config.vapi ../src/app-window.vala ../src/authorize-dialog.vala ../src/book.vala ../src/book-view.vala ../src/page.vala ../src/page-view.vala ../src/preferences-dialog.vala ../src/simple-scan.vala ../src/scanner.vala ../src/screensaver.vala ../src/autosave-manager.vala ARGS = -C --debug --pkg libwebpmux --pkg libwebp --pkg packagekit-glib2 --pkg colord --pkg sane-backends --pkg gusb --pkg gdk-pixbuf-2.0 --pkg cairo --pkg zlib --pkg gtk+-3.0 --target-glib '$ 2.38' --pkg glib-2.0 -d src/simple-scan@exe --gresources=../src/simple-scan.gresource.xml --pkg=posix --vapidir=/home/dan/Projects/simple-scan/src HAVE_COLORD HAVE_PACKAGEKIT -D HAVE_WEBP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/1698256/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1698256] Re: Invalid, Meson-generated, valac arguments break the build
I had the same issue. I'm assuming a regression in Meson, but I haven't checked. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to simple-scan in Ubuntu. https://bugs.launchpad.net/bugs/1698256 Title: Invalid, Meson-generated, valac arguments break the build Status in simple-scan package in Ubuntu: Confirmed Bug description: I'm trying to build simple-scan according to the README file (on Arch). With colord, packagekit, and webp installed, Meson is building invalid args for the main build step, which prevents the project from building. The build declaration (meson.build) generates a Python list of vala_args. The list of args looks OK getting passed into executable(). However, the auto-generated build.ninja is missing the required -D(efine) flags. As a result, it treats some of defines as filenames, and crashes. Vala/Meson/Ninja are new to me, so I'm not sure if the problem is with the build file, or the Meson generator, or what. # ./src/meson.build # If all three packages are installed, they're built into the Python list. Somehow, the -D flags disappear during build generation vala_args = [ '--pkg=posix', '--vapidir=' + meson.current_source_dir () ] dependencies = [ glib_dep, gtk_dep, zlib_dep, cairo_dep, gdk_pixbuf_dep, gusb_dep, sane_dep ] if colord_dep.found () vala_args += [ '-D', 'HAVE_COLORD' ] dependencies += colord_dep endif if packagekit_dep.found () vala_args += [ '-D', 'HAVE_PACKAGEKIT' ] dependencies += packagekit_dep endif if webp_dep.found () and (not colord_dep.found () or webpmux_dep.found ()) # Webpmux only required if colord vala_args += [ '-D', 'HAVE_WEBP' ] dependencies += [ webp_dep, webpmux_dep ] endif simple_scan = executable ('simple-scan', [ 'config.vapi', 'app-window.vala', 'authorize-dialog.vala', 'book.vala', 'book-view.vala', 'page.vala', 'page-view.vala', 'preferences-dialog.vala', 'simple-scan.vala', 'scanner.vala', 'screensaver.vala', 'autosave-manager.vala' ] + resources, dependencies: dependencies, vala_args: vala_args, c_args: [ '-DVERSION="@0@"'.format (meson.project_version ()), '-DGETTEXT_PACKAGE="simple-scan"', '-DLOCALE_DIR="@0@"'.format (localedir), '-DICON_DIR="@0@"'.format (icondir), '-DI_KNOW_THE_PACKAGEKIT_GLIB2_API_IS_SUBJECT_TO_CHANGE' ], link_args: [ '-lm' ], install: true ) # ./build/build.ninja # Snippet of the bad build step. Note the -D flag is missing (at the end) build src/simple-scan@exe/app-window.c src/simple-scan@exe/authorize-dialog.c src/simple-scan@exe/book.c src/simple-scan@exe/book-view.c src/simple-scan@exe/page.c src/simple-scan@exe/page-view.c src/simple-scan@exe/preferences-dialog.c src/simple-scan@exe/simple-scan.c src/simple-scan@exe/scanner.c src/simple-scan@exe/screensaver.c src/simple-scan@exe/autosave-manager.c: vala_COMPILER ../src/config.vapi ../src/app-window.vala ../src/authorize-dialog.vala ../src/book.vala ../src/book-view.vala ../src/page.vala ../src/page-view.vala ../src/preferences-dialog.vala ../src/simple-scan.vala ../src/scanner.vala ../src/screensaver.vala ../src/autosave-manager.vala ARGS = -C --debug --pkg libwebpmux --pkg libwebp --pkg packagekit-glib2 --pkg colord --pkg sane-backends --pkg gusb --pkg gdk-pixbuf-2.0 --pkg cairo --pkg zlib --pkg gtk+-3.0 --target-glib '$ 2.38' --pkg glib-2.0 -d src/simple-scan@exe --gresources=../src/simple-scan.gresource.xml --pkg=posix --vapidir=/home/dan/Projects/simple-scan/src HAVE_COLORD HAVE_PACKAGEKIT -D HAVE_WEBP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/1698256/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1691908] Re: fstab binds appear as mounts (x-gvfs-hide is being ignored)
** Changed in: glib Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1691908 Title: fstab binds appear as mounts (x-gvfs-hide is being ignored) Status in GLib: Incomplete Status in glib2.0 package in Ubuntu: Triaged Bug description: glib2 version 2.52.2+1+gb8bd46bc8-1 (possibly the version before it as well, I haven't tested) causes fstab binds to appear as mounts in Nautilus (and in Deepin Dock - Deepin is based on Gnome). Downgrading to glib2 and glib2-docs 2.52.0-1 resolves this behaviour. I first noted this bug behaviour here: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/452049 Details of my particular system and issue with what I tried to resolve it can be found here: https://bbs.archlinux.org/viewtopic.php?pid=1712030#p1712030 1. Not using Ubuntu. Deepin Desktop 15.4 (Gnome based) on Arch Linux. OS: Arch Linux Kernel: x86_64 Linux 4.10.13-1-ARCH Shell: bash 4.4.12 Resolution: 1920x1200 DE: Deepin 15.4 WM: Deepin WM WM Theme: Arc-Darker GTK Theme: Arc-Darker [GTK2/3] Icon Theme: deepin Font: Noto Sans 11 CPU: Intel Core i5-6500 @ 4x 3.6GHz [27.8°C] GPU: GeForce GTX 950 RAM: 2598MiB / 15990MiB 2. 2.52.2+1+gb8bd46bc8-1 (downgrading to 2.52.0-1 removed the problem). 3. Nautilus to list internal physical drives (my SSD and 1TB HDD) only. 4. Nautilus listed my system disk (as expected) but also listed all of my fstab binds as removable drives (Downloads, Music, Pictures, Videos and Documents although this was not listed as "Documents" but instead listed as the HDD label "Farsight"). Adding x-gvfs-hide did not hide those drives. To manage notifications about this bug go to: https://bugs.launchpad.net/glib/+bug/1691908/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1283003] Re: Bluetooth headset/speakers listed but not selectable in Sound settings
Zesty already contains the latest release (and all fixes): https://launchpad.net/ubuntu/+source/pulseaudio So if you have a problem with zesty, please log a new bug. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio 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: Fix Committed 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 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. To manage notifications about this bug go to: https://bugs.launchpad.net/blueman/+bug/1283003/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1698256] Re: Invalid, Meson-generated, valac arguments break the build
** Changed in: simple-scan (Ubuntu) Status: Confirmed => Triaged ** Changed in: simple-scan (Ubuntu) Importance: Undecided => Critical -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to simple-scan in Ubuntu. https://bugs.launchpad.net/bugs/1698256 Title: Invalid, Meson-generated, valac arguments break the build Status in simple-scan package in Ubuntu: Triaged Bug description: I'm trying to build simple-scan according to the README file (on Arch). With colord, packagekit, and webp installed, Meson is building invalid args for the main build step, which prevents the project from building. The build declaration (meson.build) generates a Python list of vala_args. The list of args looks OK getting passed into executable(). However, the auto-generated build.ninja is missing the required -D(efine) flags. As a result, it treats some of defines as filenames, and crashes. Vala/Meson/Ninja are new to me, so I'm not sure if the problem is with the build file, or the Meson generator, or what. # ./src/meson.build # If all three packages are installed, they're built into the Python list. Somehow, the -D flags disappear during build generation vala_args = [ '--pkg=posix', '--vapidir=' + meson.current_source_dir () ] dependencies = [ glib_dep, gtk_dep, zlib_dep, cairo_dep, gdk_pixbuf_dep, gusb_dep, sane_dep ] if colord_dep.found () vala_args += [ '-D', 'HAVE_COLORD' ] dependencies += colord_dep endif if packagekit_dep.found () vala_args += [ '-D', 'HAVE_PACKAGEKIT' ] dependencies += packagekit_dep endif if webp_dep.found () and (not colord_dep.found () or webpmux_dep.found ()) # Webpmux only required if colord vala_args += [ '-D', 'HAVE_WEBP' ] dependencies += [ webp_dep, webpmux_dep ] endif simple_scan = executable ('simple-scan', [ 'config.vapi', 'app-window.vala', 'authorize-dialog.vala', 'book.vala', 'book-view.vala', 'page.vala', 'page-view.vala', 'preferences-dialog.vala', 'simple-scan.vala', 'scanner.vala', 'screensaver.vala', 'autosave-manager.vala' ] + resources, dependencies: dependencies, vala_args: vala_args, c_args: [ '-DVERSION="@0@"'.format (meson.project_version ()), '-DGETTEXT_PACKAGE="simple-scan"', '-DLOCALE_DIR="@0@"'.format (localedir), '-DICON_DIR="@0@"'.format (icondir), '-DI_KNOW_THE_PACKAGEKIT_GLIB2_API_IS_SUBJECT_TO_CHANGE' ], link_args: [ '-lm' ], install: true ) # ./build/build.ninja # Snippet of the bad build step. Note the -D flag is missing (at the end) build src/simple-scan@exe/app-window.c src/simple-scan@exe/authorize-dialog.c src/simple-scan@exe/book.c src/simple-scan@exe/book-view.c src/simple-scan@exe/page.c src/simple-scan@exe/page-view.c src/simple-scan@exe/preferences-dialog.c src/simple-scan@exe/simple-scan.c src/simple-scan@exe/scanner.c src/simple-scan@exe/screensaver.c src/simple-scan@exe/autosave-manager.c: vala_COMPILER ../src/config.vapi ../src/app-window.vala ../src/authorize-dialog.vala ../src/book.vala ../src/book-view.vala ../src/page.vala ../src/page-view.vala ../src/preferences-dialog.vala ../src/simple-scan.vala ../src/scanner.vala ../src/screensaver.vala ../src/autosave-manager.vala ARGS = -C --debug --pkg libwebpmux --pkg libwebp --pkg packagekit-glib2 --pkg colord --pkg sane-backends --pkg gusb --pkg gdk-pixbuf-2.0 --pkg cairo --pkg zlib --pkg gtk+-3.0 --target-glib '$ 2.38' --pkg glib-2.0 -d src/simple-scan@exe --gresources=../src/simple-scan.gresource.xml --pkg=posix --vapidir=/home/dan/Projects/simple-scan/src HAVE_COLORD HAVE_PACKAGEKIT -D HAVE_WEBP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/1698256/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1663157] Re: Guest session processes are not confined in 16.10 and newer releases
** No longer affects: apparmor (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1663157 Title: Guest session processes are not confined in 16.10 and newer releases Status in Light Display Manager: New Status in lightdm package in Ubuntu: Fix Released Status in lightdm source package in Yakkety: Fix Released Status in lightdm source package in Zesty: Fix Released Status in lightdm source package in Artful: Fix Released Bug description: Processes launched under a lightdm guest session are not confined by the /usr/lib/lightdm/lightdm-guest-session AppArmor profile in Ubuntu 16.10, Ubuntu 17.04, and Ubuntu Artful (current dev release). The processes are unconfined. The simple test case is to log into a guest session, launch a terminal with ctrl-alt-t, and run the following command: $ cat /proc/self/attr/current Expected output, as seen in Ubuntu 16.04 LTS, is: /usr/lib/lightdm/lightdm-guest-session (enforce) Running the command inside of an Ubuntu 16.10 and newer guest session results in: unconfined To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1663157/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1575484] Re: "Set document metadata failed"
also in 16.10 i got this -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1575484 Title: "Set document metadata failed" Status in gedit: Invalid Status in gedit package in Ubuntu: Fix Committed Bug description: Whenever I edit a document via the Terminal, I get these error messages: ** (gedit:12864): WARNING **: Set document metadata failed: Setting attribute metadata::gedit-spell-enabled not supported ** (gedit:12864): WARNING **: Set document metadata failed: Setting attribute metadata::gedit-encoding not supported ** (gedit:12864): WARNING **: Set document metadata failed: Setting attribute metadata::gedit-position not supported Info: OS: Ubuntu 16.04 (Xenial) x64 App version: 3.18.3 - Blossom To manage notifications about this bug go to: https://bugs.launchpad.net/gedit/+bug/1575484/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1699939] [NEW] gvfsd-mtp crashed with SIGSEGV
*** This bug is a duplicate of bug 1689770 *** https://bugs.launchpad.net/bugs/1689770 Public bug reported: As usual, when I connect my Android phone to USB. ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: gvfs-backends 1.32.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15 Uname: Linux 4.10.0-22-generic x86_64 ApportVersion: 2.20.5-0ubuntu5 Architecture: amd64 CrashCounter: 1 CurrentDesktop: GNOME Date: Thu Jun 22 21:49:55 2017 ExecutablePath: /usr/lib/gvfs/gvfsd-mtp InstallationDate: Installed on 2015-04-30 (785 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) ProcCmdline: /usr/lib/gvfs/gvfsd-mtp --spawner :1.6 /org/gtk/gvfs/exec_spaw/4 ProcEnviron: LANG=en_US.UTF-8 LANGUAGE=en_US PATH=(custom, user) SHELL=/bin/bash XDG_RUNTIME_DIR= SegvAnalysis: Segfault happened at: 0x7f4d8876ccc9: mov0x18(%rax),%rax PC (0x7f4d8876ccc9) ok source "0x18(%rax)" (0x0018) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gvfs StacktraceTop: () at /usr/lib/x86_64-linux-gnu/gvfs/libgvfsdaemon.so () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 Title: gvfsd-mtp crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt libvirtd lpadmin plugdev sambashare sudo wireshark ** Affects: gvfs (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash artful third-party-packages -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1699939 Title: gvfsd-mtp crashed with SIGSEGV Status in gvfs package in Ubuntu: New Bug description: As usual, when I connect my Android phone to USB. ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: gvfs-backends 1.32.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15 Uname: Linux 4.10.0-22-generic x86_64 ApportVersion: 2.20.5-0ubuntu5 Architecture: amd64 CrashCounter: 1 CurrentDesktop: GNOME Date: Thu Jun 22 21:49:55 2017 ExecutablePath: /usr/lib/gvfs/gvfsd-mtp InstallationDate: Installed on 2015-04-30 (785 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) ProcCmdline: /usr/lib/gvfs/gvfsd-mtp --spawner :1.6 /org/gtk/gvfs/exec_spaw/4 ProcEnviron: LANG=en_US.UTF-8 LANGUAGE=en_US PATH=(custom, user) SHELL=/bin/bash XDG_RUNTIME_DIR= SegvAnalysis: Segfault happened at: 0x7f4d8876ccc9:mov0x18(%rax),%rax PC (0x7f4d8876ccc9) ok source "0x18(%rax)" (0x0018) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gvfs StacktraceTop: () at /usr/lib/x86_64-linux-gnu/gvfs/libgvfsdaemon.so () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 Title: gvfsd-mtp crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt libvirtd lpadmin plugdev sambashare sudo wireshark To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1699939/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1699942] [NEW] network-manager fails to deprecate addresses
Public bug reported: network manager does not properly deprecate autoconfigured temporary IP addresses when ValidLifetime for a prefix is 0 in router advertisements. This behaviour is non-compliant with RFC 4861 § 6.3.4, which reads: If the prefix is already present in the host's Prefix List as the result of a previously received advertisement, reset its invalidation timer to the Valid Lifetime value in the Prefix Information option. If the new Lifetime value is zero, time-out the prefix immediately. The hosts instead continued to use temporary addresses configured until they reached their timeout, rather than immediately dropping the addresses. It further appears that it is generating new temporary addresses when the previous ones expire, but I have not been monitoring hosts closely enough to tell for sure---I will update on this when I have further information. This problem was discovered on Ubuntu Studio 16.04.2; it is not present on Ubuntu Server (which uses Debian networking scripts). Additional Info: $ lsb_release -rd Description:Ubuntu 16.04.2 LTS Release:16.04 $ apt-cache policy network-manager network-manager: Installed: 1.2.6-0ubuntu0.16.04.1 Candidate: 1.2.6-0ubuntu0.16.04.1 Version table: *** 1.2.6-0ubuntu0.16.04.1 500 500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.2.2-0ubuntu0.16.04.4 500 500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages 1.1.93-0ubuntu4 500 500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1699942 Title: network-manager fails to deprecate addresses Status in network-manager package in Ubuntu: New Bug description: network manager does not properly deprecate autoconfigured temporary IP addresses when ValidLifetime for a prefix is 0 in router advertisements. This behaviour is non-compliant with RFC 4861 § 6.3.4, which reads: If the prefix is already present in the host's Prefix List as the result of a previously received advertisement, reset its invalidation timer to the Valid Lifetime value in the Prefix Information option. If the new Lifetime value is zero, time-out the prefix immediately. The hosts instead continued to use temporary addresses configured until they reached their timeout, rather than immediately dropping the addresses. It further appears that it is generating new temporary addresses when the previous ones expire, but I have not been monitoring hosts closely enough to tell for sure---I will update on this when I have further information. This problem was discovered on Ubuntu Studio 16.04.2; it is not present on Ubuntu Server (which uses Debian networking scripts). Additional Info: $ lsb_release -rd Description: Ubuntu 16.04.2 LTS Release: 16.04 $ apt-cache policy network-manager network-manager: Installed: 1.2.6-0ubuntu0.16.04.1 Candidate: 1.2.6-0ubuntu0.16.04.1 Version table: *** 1.2.6-0ubuntu0.16.04.1 500 500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.2.2-0ubuntu0.16.04.4 500 500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages 1.1.93-0ubuntu4 500 500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1699942/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1699939] Re: gvfsd-mtp crashed with SIGSEGV
*** This bug is a duplicate of bug 1689770 *** https://bugs.launchpad.net/bugs/1689770 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1689770, so 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. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1699939/+attachment/4901254/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1699939/+attachment/4901256/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1699939/+attachment/4901259/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1699939/+attachment/4901260/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1699939/+attachment/4901261/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1699939/+attachment/4901262/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1699939/+attachment/4901263/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1689770 ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1699939 Title: gvfsd-mtp crashed with SIGSEGV Status in gvfs package in Ubuntu: New Bug description: As usual, when I connect my Android phone to USB. ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: gvfs-backends 1.32.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15 Uname: Linux 4.10.0-22-generic x86_64 ApportVersion: 2.20.5-0ubuntu5 Architecture: amd64 CrashCounter: 1 CurrentDesktop: GNOME Date: Thu Jun 22 21:49:55 2017 ExecutablePath: /usr/lib/gvfs/gvfsd-mtp InstallationDate: Installed on 2015-04-30 (785 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) ProcCmdline: /usr/lib/gvfs/gvfsd-mtp --spawner :1.6 /org/gtk/gvfs/exec_spaw/4 ProcEnviron: LANG=en_US.UTF-8 LANGUAGE=en_US PATH=(custom, user) SHELL=/bin/bash XDG_RUNTIME_DIR= SegvAnalysis: Segfault happened at: 0x7f4d8876ccc9:mov0x18(%rax),%rax PC (0x7f4d8876ccc9) ok source "0x18(%rax)" (0x0018) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gvfs StacktraceTop: () at /usr/lib/x86_64-linux-gnu/gvfs/libgvfsdaemon.so () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 Title: gvfsd-mtp crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt libvirtd lpadmin plugdev sambashare sudo wireshark To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1699939/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1019877] Re: Use HTTPS instead of HTTP
** Changed in: firefox Status: Confirmed => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1019877 Title: Use HTTPS instead of HTTP Status in Mozilla Firefox: Invalid Status in firefox package in Ubuntu: Confirmed Bug description: about:config Search: http:// browser.safebrowsing.reportErrorURL;http://%LOCALE%.phish-error.mozilla.com/?hl=%LOCALE% browser.safebrowsing.reportGenericURL;http://%LOCALE%.phish-generic.mozilla.com/?hl=%LOCALE% browser.safebrowsing.reportMalwareErrorURL;http://%LOCALE%.malware-error.mozilla.com/?hl=%LOCALE% browser.safebrowsing.reportMalwareURL;http://%LOCALE%.malware-report.mozilla.com/?hl=%LOCALE% browser.safebrowsing.reportPhishURL;http://%LOCALE%.phish-report.mozilla.com/?hl=%LOCALE% devtools.gcli.jquerySrc;http://ajax.googleapis.com/ajax/libs/jquery/2.1.1/jquery.min.js devtools.gcli.lodashSrc;http://cdnjs.cloudflare.com/ajax/libs/lodash.js/2.4.1/lodash.min.js devtools.gcli.underscoreSrc;http://cdnjs.cloudflare.com/ajax/libs/underscore.js/1.6.0/underscore-min.js On 'app.update.url.manual;http://www.firefox.com' suffix a slash at the end to make it FQDN. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1019877/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 606365] Re: unable to import config with inlined ca, cert, key or tls-auth
network-manager-openvpn was fixed in Xenial with https://launchpad.net/ubuntu/+source/network-manager-openvpn/1.1.93-1 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-openvpn in Ubuntu. https://bugs.launchpad.net/bugs/606365 Title: unable to import config with inlined ca, cert, key or tls-auth Status in NetworkManager-OpenVPN: Fix Released Status in plasma-nm: Unknown Status in network-manager-openvpn package in Ubuntu: Fix Released Status in plasma-nm package in Ubuntu: Fix Released Bug description: Binary package hint: network-manager-openvpn-gnome So a client of mine runs an OpenVPN setup. It exported a client.ovpn file but it fails to completely import this file using the network- manager (gnome) on Ubuntu 10.04. When I import the file, it gives me the name ("client") and gateway ("vpn.example.org") on the initial screen. No other fields are populated even though the client.ovpn file also includes a user certificate, server certifikate and a private key. When I go to advanced, some (most) of the settings obviously seem to import correct, others not at all. E.g. none of the TLS settings (key and key direction) are imported. From what I understand I should be able to use this without any additional settings. The following software is installed through aptitude: * openvpn (2.1.0) * openvpn-blacklist * network-manager-openvpn * network-manager-openvpn-gnome To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager-openvpn/+bug/606365/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 606365] Re: unable to import config with inlined ca, cert, key or tls-auth
plasma-nm was fixed in Wily with https://launchpad.net/ubuntu/+source /plasma-nm/4:5.3.95-0ubuntu1 ** Also affects: plasma-nm (Ubuntu) Importance: Undecided Status: New ** Changed in: plasma-nm (Ubuntu) Importance: Undecided => Medium ** Changed in: network-manager-openvpn (Ubuntu) Importance: High => Medium ** Changed in: plasma-nm (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-openvpn in Ubuntu. https://bugs.launchpad.net/bugs/606365 Title: unable to import config with inlined ca, cert, key or tls-auth Status in NetworkManager-OpenVPN: Fix Released Status in plasma-nm: Unknown Status in network-manager-openvpn package in Ubuntu: Fix Released Status in plasma-nm package in Ubuntu: Fix Released Bug description: Binary package hint: network-manager-openvpn-gnome So a client of mine runs an OpenVPN setup. It exported a client.ovpn file but it fails to completely import this file using the network- manager (gnome) on Ubuntu 10.04. When I import the file, it gives me the name ("client") and gateway ("vpn.example.org") on the initial screen. No other fields are populated even though the client.ovpn file also includes a user certificate, server certifikate and a private key. When I go to advanced, some (most) of the settings obviously seem to import correct, others not at all. E.g. none of the TLS settings (key and key direction) are imported. From what I understand I should be able to use this without any additional settings. The following software is installed through aptitude: * openvpn (2.1.0) * openvpn-blacklist * network-manager-openvpn * network-manager-openvpn-gnome To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager-openvpn/+bug/606365/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1681513] Re: Ubuntu 17.04/17.10: New feature in NetworkManager stops several WiFi adapters from working (MAC Address Randomization issue)
FYI, just found out the hard way that "Device" needs to be lower case!... $ sudo nano /etc/NetworkManager/NetworkManager.conf # Append... - - - - - - - - - - - - - - - - - - - - [device] wifi.scan-rand-mac-address=no - - - - - - - - - - - - - - - - - - - - $ sudo service network-manager restart -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1681513 Title: Ubuntu 17.04/17.10: New feature in NetworkManager stops several WiFi adapters from working (MAC Address Randomization issue) Status in network-manager package in Ubuntu: Confirmed Bug description: According to https://blogs.gnome.org/thaller/2016/08/26/mac-address-spoofing-in-networkmanager-1-4-0/ there is a new privacy feature in the new version of NetworkManager. This privacy feature can cause some USB WiFi adapters to stop working while they used to work with older versions of NetworkManager (Ubuntu 16.10 or older). The purpose of this privacy feature is to get your computer to report a new random MAC address whenever you connect to a WiFi network. This privacy feature is especially useful when you connect to public WiFi networks, so that the operators cannot identify you when you connect multiple times. The downside of this privacy feature is that some USB WiFi adapters misbehave when NetworkManager tries to change their MAC address repeatedly. The result is that those USB WiFi adapters cannot connect anymore to the WiFi network. Original report follows: My Panda USB wi-fi adapter works just fine on 16.10, but when I try to connect to my wi-fi router in 17.04, GNOME network manager reports "Connection failed." I did some tinkering, and noticed that my MAC address for my wifi adapter, according to GNOME, is DIFFERENT every time I make it forget my wifi settings and try to reconnect. Weird, right? Any leads on a possible fix or work-around? I'm running the latest beta of Ubuntu GNOME 17.04, kernel 4.10.0-19-generic, GNOME 3.24.0. https://blogs.gnome.org/thaller/2016/08/26/mac-address-spoofing-in- networkmanager-1-4-0/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1681513/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1699952] [NEW] [Aspire 5750Z, Realtek ALC269VB, Speaker, Internal] Background noise or low volume
Public bug reported: High crackling/popping sound with low volume from laptop speakers when playing any audio video file. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-42.62-generic 4.4.21 Uname: Linux 4.4.0-42-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ankit 1866 F pulseaudio CurrentDesktop: Unity Date: Fri Jun 23 08:55:10 2017 InstallationDate: Installed on 2016-07-14 (343 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Speaker, Internal Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: High background noise, or volume is too low Title: [Aspire 5750Z, Realtek ALC269VB, Speaker, Internal] Background noise or low volume UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/11/2011 dmi.bios.vendor: Acer dmi.bios.version: V1.12 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: JE50_HR dmi.board.vendor: Acer dmi.board.version: Base Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.12 dmi.modalias: dmi:bvnAcer:bvrV1.12:bd07/11/2011:svnAcer:pnAspire5750Z:pvrV1.12:rvnAcer:rnJE50_HR:rvrBaseBoardVersion:cvnAcer:ct10:cvrV1.12: dmi.product.name: Aspire 5750Z dmi.product.version: V1.12 dmi.sys.vendor: Acer ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages xenial -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1699952 Title: [Aspire 5750Z, Realtek ALC269VB, Speaker, Internal] Background noise or low volume Status in alsa-driver package in Ubuntu: New Bug description: High crackling/popping sound with low volume from laptop speakers when playing any audio video file. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-42.62-generic 4.4.21 Uname: Linux 4.4.0-42-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ankit 1866 F pulseaudio CurrentDesktop: Unity Date: Fri Jun 23 08:55:10 2017 InstallationDate: Installed on 2016-07-14 (343 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Speaker, Internal Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: High background noise, or volume is too low Title: [Aspire 5750Z, Realtek ALC269VB, Speaker, Internal] Background noise or low volume UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/11/2011 dmi.bios.vendor: Acer dmi.bios.version: V1.12 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: JE50_HR dmi.board.vendor: Acer dmi.board.version: Base Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.12 dmi.modalias: dmi:bvnAcer:bvrV1.12:bd07/11/2011:svnAcer:pnAspire5750Z:pvrV1.12:rvnAcer:rnJE50_HR:rvrBaseBoardVersion:cvnAcer:ct10:cvrV1.12: dmi.product.name: Aspire 5750Z dmi.product.version: V1.12 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1699952/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 238606] Re: [MASTER] Flash player doesn't work properly on Firefox 3 64bits (crash, gray square)
[Expired for flashplugin-nonfree (Ubuntu) because there has been no activity for 60 days.] ** Changed in: flashplugin-nonfree (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to flashplugin-nonfree in Ubuntu. https://bugs.launchpad.net/bugs/238606 Title: [MASTER] Flash player doesn't work properly on Firefox 3 64bits (crash,gray square) Status in adobe-flashplugin package in Ubuntu: Expired Status in firefox-3.0 package in Ubuntu: Invalid Status in flashplugin-nonfree package in Ubuntu: Expired Bug description: Binary package hint: firefox-3.0 Adobe's Flash plugin doesn't work every time. Some times it work properly, and some times it show just a gray square where it should show the embed flash object. On konqueror it works ok, so this is an issue of Firefox, not of flash. Some info of my system: janus@ernestina:~$ lsb_release -rd Description:Ubuntu 8.04 Release:8.04 janus@ernestina:~$ apt-cache policy flashplugin-nonfree flashplugin-nonfree: Instalados: 9.0.124.0ubuntu2 Candidato: 9.0.124.0ubuntu2 Tabla de versión: *** 9.0.124.0ubuntu2 0 500 http://ftp.usf.edu hardy/multiverse Packages 100 /var/lib/dpkg/status janus@ernestina:~$ apt-cache policy firefox firefox: Instalados: 3.0~rc2+nobinonly-0ubuntu1~fta1~hardy Candidato: 3.0~rc2+nobinonly-0ubuntu1~fta1~hardy Tabla de versión: *** 3.0~rc2+nobinonly-0ubuntu1~fta1~hardy 0 500 http://ppa.launchpad.net hardy/main Packages 100 /var/lib/dpkg/status 3.0~b5+nobinonly-0ubuntu3 0 500 http://ftp.usf.edu hardy/main Packages (I'm using FF3RC2, but it also didn't work properly on FF3RC1 nor FF3b5) ProblemType: Bug Architecture: amd64 Date: Mon Jun 9 13:11:53 2008 DistroRelease: Ubuntu 8.04 NonfreeKernelModules: nvidia Package: firefox-3.0 3.0~rc2+nobinonly-0ubuntu1~fta1~hardy [modified: usr/lib/firefox-3.0/ffox-3-beta-profile-migration-dialog usr/lib/firefox-3.0/firefox] PackageArchitecture: amd64 ProcEnviron: LANGUAGE=es_AR:es PATH=/home/username/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games LANG=es_AR.UTF-8 SHELL=/bin/bash SourcePackage: firefox-3.0 Uname: Linux 2.6.24-18-generic x86_64 UnreportableReason: Este no es un genuino paquete Ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adobe-flashplugin/+bug/238606/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 238606] Re: [MASTER] Flash player doesn't work properly on Firefox 3 64bits (crash, gray square)
[Expired for adobe-flashplugin (Ubuntu) because there has been no activity for 60 days.] ** Changed in: adobe-flashplugin (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to flashplugin-nonfree in Ubuntu. https://bugs.launchpad.net/bugs/238606 Title: [MASTER] Flash player doesn't work properly on Firefox 3 64bits (crash,gray square) Status in adobe-flashplugin package in Ubuntu: Expired Status in firefox-3.0 package in Ubuntu: Invalid Status in flashplugin-nonfree package in Ubuntu: Expired Bug description: Binary package hint: firefox-3.0 Adobe's Flash plugin doesn't work every time. Some times it work properly, and some times it show just a gray square where it should show the embed flash object. On konqueror it works ok, so this is an issue of Firefox, not of flash. Some info of my system: janus@ernestina:~$ lsb_release -rd Description:Ubuntu 8.04 Release:8.04 janus@ernestina:~$ apt-cache policy flashplugin-nonfree flashplugin-nonfree: Instalados: 9.0.124.0ubuntu2 Candidato: 9.0.124.0ubuntu2 Tabla de versión: *** 9.0.124.0ubuntu2 0 500 http://ftp.usf.edu hardy/multiverse Packages 100 /var/lib/dpkg/status janus@ernestina:~$ apt-cache policy firefox firefox: Instalados: 3.0~rc2+nobinonly-0ubuntu1~fta1~hardy Candidato: 3.0~rc2+nobinonly-0ubuntu1~fta1~hardy Tabla de versión: *** 3.0~rc2+nobinonly-0ubuntu1~fta1~hardy 0 500 http://ppa.launchpad.net hardy/main Packages 100 /var/lib/dpkg/status 3.0~b5+nobinonly-0ubuntu3 0 500 http://ftp.usf.edu hardy/main Packages (I'm using FF3RC2, but it also didn't work properly on FF3RC1 nor FF3b5) ProblemType: Bug Architecture: amd64 Date: Mon Jun 9 13:11:53 2008 DistroRelease: Ubuntu 8.04 NonfreeKernelModules: nvidia Package: firefox-3.0 3.0~rc2+nobinonly-0ubuntu1~fta1~hardy [modified: usr/lib/firefox-3.0/ffox-3-beta-profile-migration-dialog usr/lib/firefox-3.0/firefox] PackageArchitecture: amd64 ProcEnviron: LANGUAGE=es_AR:es PATH=/home/username/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games LANG=es_AR.UTF-8 SHELL=/bin/bash SourcePackage: firefox-3.0 Uname: Linux 2.6.24-18-generic x86_64 UnreportableReason: Este no es un genuino paquete Ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adobe-flashplugin/+bug/238606/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1368324] Re: freeze and unable to record a video
[Expired for cheese (Ubuntu) because there has been no activity for 60 days.] ** Changed in: cheese (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cheese in Ubuntu. https://bugs.launchpad.net/bugs/1368324 Title: freeze and unable to record a video Status in cheese package in Ubuntu: Expired Bug description: Recording a video freezes the webcam display, and I get a webm video file of size 0 on the disk. Kamorama works fine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cheese/+bug/1368324/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp