[Desktop-packages] [Bug 1699441] [NEW] Firefox crashes very often
Public bug reported: My firefox crash like 5 times for hour. I was looking for solution, reinstalling it. Any help ? Add-ons: ubufox%40ubuntu.com:3.2,%7Ba6fd85ed-e919-4a43-a5af-8da18bda539f%7D:2.9.1.1-signed,%7BF5DDF39C-9293-4d5e-9AA8-E04E6DD5E9B4%7D:1.6.3.1-signed.1-signed,%7B972ce4c6-7e08-4474-a285-3208198ce6fd%7D:54.0,ciscowebexstart1%40cisco.com:1.0.9,firebug%40software.joehewitt.com:2.0.19,uBlock0%40raymondhill.net:1.12.4,%7Bd10d0bf8-f5b5-c8b4-a8b2-2b9879e08c5d%7D:2.9.1,e10srollout%40mozilla.org:1.50,aushelper%40mozilla.org:2.0,firefox%40getpocket.com:1.0.5,webcompat%40mozilla.org:1.1,screenshots%40mozilla.org:6.6.0,langpack-en-GB%40firefox.mozilla.org:54.0,langpack-en-ZA%40firefox.mozilla.org:54.0,langpack-pl%40firefox.mozilla.org:54.0,followonsearch%40mozilla.com:0.8.0 AddonsShouldHaveBlockedE10s: 1 BuildID: 20170612122310 ContentSandboxCapabilities: 119 ContentSandboxCapable: 1 ContentSandboxLevel: 2 CrashTime: 1498031970 E10SCohort: disqualified-test EMCheckCompatibility: true EventLoopNestingLevel: 1 FramePoisonBase: 9223372036600930304 FramePoisonSize: 4096 InstallTime: 1497615895 Notes: Ubuntu 16.04.2 LTSFP(D00-L1000-W-T000) OpenGL: Intel Open Source Technology Center -- Mesa DRI Intel(R) Haswell Mobile -- 3.0 Mesa 12.0.6 -- texture_from_pixmap ProductID: {ec8030f7-c20a-464f-9b0e-13a3a9e97384} ProductName: Firefox ReleaseChannel: release SafeMode: 0 SecondsSinceLastCrash: 373 StackTraces: StartupCrash: 0 StartupTime: 1498031599 TelemetryEnvironment: {"build":{"applicationId":"{ec8030f7-c20a-464f-9b0e-13a3a9e97384}","applicationName":"Firefox","architecture":"x86-64","buildId":"20170612122310","version":"54.0","vendor":"Mozilla","platformVersion":"54.0","xpcomAbi":"x86_64-gcc3","hotfixVersion":"20170302.01"},"partner":{"distributionId":"canonical","distributionVersion":"1.0","partnerId":null,"distributor":null,"distributorChannel":null,"partnerNames":["ubuntu "]},"system":{"memoryMB":11931,"virtualMaxMB":null,"cpu":{"count":8,"cores":4,"vendor":"GenuineIntel","family":6,"model":60,"stepping":3,"l2cacheKB":256,"l3cacheKB":6144,"speedMHz":3400,"extensions":["hasMMX","hasSSE","hasSSE2","hasSSE3","hasSSSE3","hasSSE4_1","hasSSE4_2","hasAVX","hasAVX2"]},"os":{"name":"Linux","version":"4.8.0-56-generic","locale":"pl-PL"},"hdd":{"profile":{"model":null,"revision":null},"binary":{"model":null,"revision":null},"system":{"model":null,"revision":null}},"gfx":{"D2DEnabled":null,"DWriteEnabled":null,"ContentBackend":"Skia","adapters":[{"description":"Intel Open Source Technology Center -- Mesa DRI Intel(R) Haswell Mobile ","vendorID":"Intel Open Source Technology Center","deviceID":"Mesa DRI Intel(R) Haswell Mobile ","subsysID":null,"RAM":null,"driver":null,"driverVersion":"3.0 Mesa 12.0.6","driverDate":null,"GPUActive":true}],"monitors":[],"features":{"compositor":"none","gpuProcess":{"status":"unused","settings":{"blocklistEnabled":true,"e10sEnabled":false,"e10sMultiProcesses":1,"e10sCohort":"disqualified-test","telemetryEnabled":false,"locale":"pl","update":{"channel":"release","enabled":true,"autoDownload":true},"userPrefs":{"browser.cache.disk.capacity":358400,"browser.newtabpage.enhanced":true,"browser.startup.page":3},"addonCompatibilityCheckEnabled":true,"isDefaultBrowser":false},"profile":{"creationDate":17244},"addons":{"activeAddons":{"ubu...@ubuntu.com":{"blocklisted":false,"description":"Pakiet Ubuntu Firefox.","name":"Ubuntu Modifications","userDisabled":false,"appDisabled":false,"version":"3.2","scope":8,"type":"extension","foreignInstall":true,"hasBinaryComponents":false,"installDay":16696,"updateDay":16696,"signedState":2,"isSystem":false,"isWebExtension":false},"ciscowebexsta...@cisco.com":{"blocklisted":false,"description":"Join WebEx meetings using Firefox ™","name":"Cisco WebEx Extension","userDisabled":false,"appDisabled":false,"version":"1.0.9","scope":1,"type":"extension","foreignInstall":false,"hasBinaryComponents":false,"installDay":17287,"updateDay":17287,"signedState":2,"isSystem":false,"isWebExtension":true},"fire...@software.joehewitt.com":{"blocklisted":false,"description":"Web Development Evolved. Firebug is free and open source software distributed under the BSD License.","name":"Firebug","userDisabled":false,"appDisabled":false,"version":"2.0.19","scope":1,"type":"extension","foreignInstall":false,"hasBinaryComponents":false,"installDay":17287,"updateDay":17287,"signedState":2,"isSystem":false,"isWebExtension":false},"{a6fd85ed-e919-4a43-a5af-8da18bda539f}":{"blocklisted":false,"description":"Record, edit and play Selenium tests","name":"Selenium IDE","userDisabled":false,"appDisabled":false,"version":"2.9.1.1-signed","scope":1,"type":"extension","foreignInstall":false,"hasBinaryComponents":false,"installDay":17288,"updateDay":17288,"signedState":1,"isSystem":false,"isWebExtension":false},"{F5DDF39C-9293-4d5e-9AA8-E04E6DD5E9B4}":{"blocklisted":false,"description":"A toolbar that helps you find and test SQL injections","name":"HackBar"
[Desktop-packages] [Bug 830348] Re: desktop contents briefly visible on resume from suspend before lock dialog
*** This bug is a duplicate of bug 1280300 *** https://bugs.launchpad.net/bugs/1280300 Yep still get it in 17.04, also to be noted is that while using vmware, the desktop does not lock until I click on something else, causing the vm to lose input focus. So I can leave my computer for far longer than the set lock time and it will not lock until somebody clicks somewhere on the unity launcher or another window. IDK how this has existed since 2011, this is a glaring security bug. -- 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/830348 Title: desktop contents briefly visible on resume from suspend before lock dialog Status in Compiz: New Status in unity-2d: Confirmed Status in gnome-screensaver package in Ubuntu: Incomplete Status in unity-2d package in Ubuntu: Confirmed Bug description: This seems like a recent regression on Oneiric (or perhaps I haven't noticed it before): On resume from suspend, the contents of the desktop are often briefly visible before being hidden behind the lock screen. This is a security problem if there happens to be sensitive information on the screen. =Analysis from mdeslaur= This is likely what happens: 1- Something grabs mouse: ie: virtual machine window, or GTK menu in an application or an indicator 2- Screensaver attempts to start, but cannot get exclusive lock on mouse 3- DPMS turns monitor black 4- User moves mouse, which turns the screen back on 5- Mouse movement causes mouse to get ungrabbed by vm window or gtk menu 6- Screensaver can now grab mouse, and starts This is all related to the fact that X does not have an API that will let the screensaver tell an application to release mouse and keyboard grabs. To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/830348/+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
** Attachment added: "dmesg.txt" https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1654448/+attachment/4900166/+files/dmesg.txt -- 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 972063] Re: [Dell Inspiron N411Z] Bluetooth Headset pairs but does not show up in Sound Settings profile
** Tags added: a2dp -- 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/972063 Title: [Dell Inspiron N411Z] Bluetooth Headset pairs but does not show up in Sound Settings profile Status in bluez package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Incomplete Bug description: Expected Result: After pairing bluetooth headset the device should then show up in > Sound Settings and work like any other audio device Actual Result: Jabra Halo v2 Bluetooth Headset pairs fine but does not show up in sound settings therefore is unusable ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: pulseaudio 1:1.1-0ubuntu13 ProcVersionSignature: Ubuntu 3.2.0-21.34-generic 3.2.13 Uname: Linux 3.2.0-21-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 2.0-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bkerensa 2121 F pulseaudio Date: Mon Apr 2 20:07:36 2012 EcryptfsInUse: Yes InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20120325) ProcEnviron: TERM=xterm LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/24/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A00 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 0VK06J dmi.board.vendor: Dell Inc. dmi.board.version: FAB1 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA00:bd06/24/2011:svnDellInc.:pnDellSystemInspironN411Z:pvr:rvnDellInc.:rn0VK06J:rvrFAB1:cvnDellInc.:ct8:cvr0.1: dmi.product.name: Dell System Inspiron N411Z dmi.sys.vendor: Dell Inc. --- ApportVersion: 2.0.1-0ubuntu12 Architecture: amd64 DistroRelease: Ubuntu 12.04 EcryptfsInUse: Yes InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) InterestingModules: btusb rfcomm bnep bluetooth MachineType: Dell Inc. Dell System Inspiron N411Z Package: pulseaudio PackageArchitecture: amd64 ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-29-generic root=UUID=281cfb17-fceb-4b60-b002-bbadb81bf79b ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.2.0-29.46-generic 3.2.24 Tags: precise running-unity Uname: Linux 3.2.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 06/24/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A00 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 0VK06J dmi.board.vendor: Dell Inc. dmi.board.version: FAB1 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA00:bd06/24/2011:svnDellInc.:pnDellSystemInspironN411Z:pvr:rvnDellInc.:rn0VK06J:rvrFAB1:cvnDellInc.:ct8:cvr0.1: dmi.product.name: Dell System Inspiron N411Z dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: AC:72:89:44:9D:8B ACL MTU: 310:10 SCO MTU: 64:8 UP RUNNING PSCAN RX bytes:828 acl:0 sco:0 events:34 errors:0 TX bytes:637 acl:0 sco:0 commands:33 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/972063/+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 1673984] Re: Can not add google account any more (Zesty)
Ubuntu-session is now unity-session. This again breaks the code. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to signon-ui in Ubuntu. https://bugs.launchpad.net/bugs/1673984 Title: Can not add google account any more (Zesty) Status in Canonical System Image: New Status in signon-ui package in Ubuntu: Fix Released Bug description: After updating Unity-Control-Center to 15.04.0+17.04.20170314-0ubuntu2 and liboxidecore to 1.20.4-0ubuntu1 on Zesty I could not able to add to add Google account. ### How to reproduce: 1. Go online account try adding google account. 2. Infobar will appear for a moment and the it will disappear. Screenshot: https://i.imgur.com/evDPZSv.png 3. The login page doesn't load at all. Running online-accounts-preferences from terminal gives: -- (unity-control-center:7866): credentials-cc-panel-CRITICAL **: cc-credentials-authorization-page.vala:182: Error completing auth session process: GDBus.Error:com.google.code.AccountsSSO.SingleSignOn.Error.UserInteraction: userActionFinished error: 2 -- Installed Packages (Ubuntu 17.04 32 bit): account-plugin-google: 0.13+17.04.20161206-0ubuntu1 signon-ui-x11: 0.17+17.04.20161109-0ubuntu1 unity-control-center: 15.04.0+17.04.20170314-0ubuntu2 unity-control-center-signon: 0.1.9+16.10.20160825-0ubuntu1 All other packages are up-to-date To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1673984/+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 1686189] Re: External monitor connecting problem on Intel graphics card
Thanks for the testing. Can you also try 4.4.71, 4.8, 4.9 as #35 states? -- 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/1686189 Title: External monitor connecting problem on Intel graphics card Status in linux package in Ubuntu: Confirmed Status in xorg package in Ubuntu: Confirmed Bug description: I am facing a problem with Intel Graphics driver. I have external monitor and in display settings the second monitor is detecting but it's not working, so could you email me a solution. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 Uname: Linux 4.4.25-040425-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Tue Apr 25 21:45:16 2017 DistUpgraded: 2017-04-25 21:07:40,819 DEBUG icon theme changed, re-reading DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: i915-4.6.3-4.4.0, 1, 4.4.0-75-generic, x86_64: installed GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:05e9] InstallationDate: Installed on 2017-04-25 (0 days ago) InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803) MachineType: Dell Inc. Inspiron 3537 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.25-040425-generic root=UUID=3914e6d5-5c87-4816-8043-776ef4184d29 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to xenial on 2017-04-25 (0 days ago) dmi.bios.date: 04/30/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 03JPPR dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A08 dmi.modalias: dmi:bvnDellInc.:bvrA08:bd04/30/2014:svnDellInc.:pnInspiron3537:pvrA08:rvnDellInc.:rn03JPPR:rvrA00:cvnDellInc.:ct8:cvrA08: dmi.product.name: Inspiron 3537 dmi.product.version: A08 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Tue Apr 25 21:37:24 2017 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 17900 vendor AUO xserver.version: 2:1.18.4-0ubuntu0.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1686189/+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
Updated, please try again. The new kernel disables "Headphone Mic Boost" completely. -- 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 1699475] [NEW] printing specific PDF document fails due to "Did not find alt setting 1 for intf 0, config 1"
Public bug reported: Printing a specific PDF which I can attach here if necessary (don't want to without a confirmation that it's necessary because it's copyright protected) fails due to Did not find alt setting 1 for intf 0, config 1 appearing in `dmesg` (only if the print fails). Other prints are working fine. It also shows ``` [ 2535.005678] kauditd_printk_skb: 25 callbacks suppressed [ 2535.005679] audit: type=1400 audit(1498040486.444:1211): apparmor="DENIED" operation="open" profile="/usr/share/hplip/systray.py" name="/mnt/data/home/perl5/bin/" pid=7418 comm="python" requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000 [ 2535.005813] audit: type=1400 audit(1498040486.444:1212): apparmor="DENIED" operation="open" profile="/usr/share/hplip/systray.py" name="/mnt/data/home/bin/" pid=7418 comm="python" requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000 [ 2535.005832] audit: type=1400 audit(1498040486.444:1213): apparmor="DENIED" operation="open" profile="/usr/share/hplip/systray.py" name="/mnt/data/home/gradle-2.14/bin/" pid=7418 comm="python" requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000 [ 2535.005856] audit: type=1400 audit(1498040486.444:1214): apparmor="DENIED" operation="open" profile="/usr/share/hplip/systray.py" name="/mnt/data/home/apache-maven-3.3.9/bin/" pid=7418 comm="python" requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000 [ 2535.005878] audit: type=1400 audit(1498040486.444:1215): apparmor="DENIED" operation="open" profile="/usr/share/hplip/systray.py" name="/mnt/data/home/bin/" pid=7418 comm="python" requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000 [ 2535.432178] audit: type=1400 audit(1498040486.872:1216): apparmor="DENIED" operation="file_lock" profile="/usr/share/hplip/toolbox.py" name="/etc/xdg/Trolltech.conf" pid=8707 comm="python" requested_mask="k" denied_mask="k" fsuid=1000 ouid=0 [ 2535.660185] audit: type=1400 audit(1498040487.100:1217): apparmor="DENIED" operation="open" profile="/usr/share/hplip/toolbox.py" name="/mnt/data/home/perl5/bin/" pid=8707 comm="python" requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000 [ 2535.660327] audit: type=1400 audit(1498040487.100:1218): apparmor="DENIED" operation="open" profile="/usr/share/hplip/toolbox.py" name="/mnt/data/home/bin/" pid=8707 comm="python" requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000 [ 2535.660329] audit: type=1400 audit(1498040487.100:1219): apparmor="DENIED" operation="open" profile="/usr/share/hplip/toolbox.py" name="/mnt/data/home/gradle-2.14/bin/" pid=8707 comm="python" requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000 [ 2535.660336] audit: type=1400 audit(1498040487.100:1220): apparmor="DENIED" operation="open" profile="/usr/share/hplip/toolbox.py" name="/mnt/data/home/apache-maven-3.3.9/bin/" pid=8707 comm="python" requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000 ``` `hp-doctor` output is ```> hp-doctor HP Linux Imaging and Printing System (ver. 3.17.6) Self Diagnse Utility and Healing Utility ver. 1.0 Copyright (c) 2001-15 HP Development Company, LP This software comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to distribute it under certain conditions. See COPYING file for more details. HP Linux Imaging and Printing System (ver. 3.17.6) Self Diagnse Utility and Healing Utility ver. 1.0 Copyright (c) 2001-15 HP Development Company, LP This software comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to distribute it under certain conditions. See COPYING file for more details. Checking for Deprecated items No Deprecated items are found Checking for HPLIP updates HP Linux Imaging and Printing System (ver. 3.17.6) HPLIP upgrade latest version ver. 1.0 Copyright (c) 2001-15 HP Development Company, LP This software comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to distribute it under certain conditions. See COPYING file for more details. Latest version of HPLIP is already installed. Checking for Dependencies --- | SYSTEM INFO | --- Kernel: 4.10.0-22-generic #24-Ubuntu SMP Mon May 22 17:43:20 UTC 2017 GNU/Linux Host: richter-Lenovo-IdeaPad-Z500 Proc: 4.10.0-22-generic #24-Ubuntu SMP Mon May 22 17:43:20 UTC 2017 GNU/Linux Distribution: 12 17.04 Bitness: 64 bit --- | HPLIP CONFIGURATION | --- HPLIP-Version: HPLIP 3.17.6 HPLIP-Home: /usr/share/hplip HPLIP-Installation: Auto installation is supported for ubuntu distro 17.04 version Current contents of '/etc/hp/hplip.conf' file: # hplip.conf. Generated from hplip.conf.in by configure. [hplip] version=3.17.6 [dirs] home=/usr/share/hplip run=/var/run ppd=/usr/share/ppd/HP ppdbase=/usr/share/ppd doc=/usr/share/doc/hplip-3.17.6 html=/usr/share/doc/hplip-3.17.6 icon=/usr/share/applications cupsbackend=/usr/lib/cups/backend cupsfilter=/usr/lib/cups/filter drv=/usr/share/cups/drv/hp bin=/usr/bin apparmor
[Desktop-packages] [Bug 1582213] Re: [xenial] Bluetooth device doesn't play any sound in A2DP mode unless set to HSP/HFP first
Is the package in xenial-proposed exactly the same as the one in `ppa :ubuntu-audio-dev/pulse-testing` (based on the version, I'd say so)? If so, then I've been using it for a few weeks now, and it fixed the problem for me. -- 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/
[Desktop-packages] [Bug 1667198] Proposed package upload rejected
An upload of ubuntu-drivers-common to xenial-proposed has been rejected from the upload queue for the following reason: "pycache cruft left on the tree". -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1667198 Title: gpu-manager should also support using custom xorg.conf files for Nvidia Status in HWE Next: New Status in OEM Priority Project: Confirmed Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in ubuntu-drivers-common source package in Xenial: In Progress Bug description: SRU Request: [Impact] Different GPUs may require different options in the xorg.conf file. Currently this is not possible, since the options have been hardcoded in gpu-manager to configure the system automatically. This new (backported) feature allows users to tell gpu-manager to use their own custom xorg.confs for their NVIDIA GPUs. [Test Case] 1) Enable the xenial-proposed repository, and install the ubuntu-drivers-common and the nvidia-prime packages. 2) Install the nvidia driver. 3) Place your configuration file(s) in the /usr/share/gpu-manager.d directory. If you are using a non-hybrid system, you can create the /usr/share /gpu-manager.d/non-hybrid file. In case of a hybrid system, you can specify /usr/share/gpu-manager.d/hybrid-performance and/or /usr/share /gpu-manager.d/hybrid-power-saving, depending on the power profile you intend to apply your settings to. 4) Restart the system and see if it boots correctly. If unsure, please attach your /var/log/gpu-manager.log and /var/log/Xorg.0.log 5) Make sure that the /etc/X11/xorg.conf matches the file you specified in 3) [Regression Potential] Low, the above mentioned changes are already in Artful, and will not affect the system's behaviour unless new configuration files are put in the /usr/share/gpu-manager.d/ directory. __ This feature has been implemented for Intel (ex. gpumanager_uxa), which is parsing kernel parameter to add option in xorg.conf (commit ff3a4e54). And now Nvidia also need this feature to add Option "nvidiaXineramaInfo" "off" to fix some issues. Btw, I'm thinking it might be a more flexible to have a config file which user could add all options as they want so that we could prevent keeping change gpu-manager when some more options are needed in the future. Needed by LP: #1653592 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1667198/+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
Same situation :-(. The hiss is cleary audible, no change. -- 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
This time there are no KHFENG entries in dmesg. ** Attachment added: "new.txt" https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1654448/+attachment/4900217/+files/new.txt -- 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 1585886] Re: WiFi indicator icon disappears in Ubuntu 16.04
it also happen to me, but not every time, when I suspend my laptop and turn it on... usually it comes back when I : "service network-manager restart". But, it also fails sometimes to restore it. If I reboot it comes back again, however, sometimes I simply cannot reboot because it is very inconvenient. Also, sometimes "all of a sudden" it disappears... although it keeps me connected, I feel it is very annoying... is there a solution already that does not include rebooting the system? -- 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/1585886 Title: WiFi indicator icon disappears in Ubuntu 16.04 Status in indicator-applet package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: Confirmed Bug description: Dear all, Can someone confirm an occasionally missing WiFi indicator tray icon? Sometimes it happens that the icon is not displayed although the WiFi connection is working. Please see also the attached screenshot. Warmly, ~Robert To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-applet/+bug/1585886/+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 1201128] Re: missing icons for .directory files
Still an issue on Xenial. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-icon-theme in Ubuntu. https://bugs.launchpad.net/bugs/1201128 Title: missing icons for .directory files Status in gnome-icon-theme package in Ubuntu: Confirmed Status in gnome-menus package in Ubuntu: Confirmed Bug description: Directory files have been shipped with incorrect Icon= fields. For example, ActionGames.directory contains Icon=weather-storm. This should instead read Icon=applications-action (1) which is included in many icon sets (2), leaving this kind of substitution to the theme author using symlinks. Including references to these substitutions directly in the .directory files is an inappropriate and unecessary kludge which breaks themes, including the default one. I've only checked the Games .directory files so far, since that is what I was doing when I encountered the bug, but they all exhibit this problem. I'm using Ubuntu 13.04, but it's the kind of thing that could have been sitting undone for a while. It's probably worth checking whether this bug exists upstream or whether it's been introduced by the Ubuntu team. Upon further checking, Bug #421294 is a particular case of this bug, where the line reads Icon=system-run rather than Icon=applications- puzzles. From this report and Bug #421695 it seems likely that this bug was introduced in Karmic. (1) or similar - I'm not entirely sure on whether this will shake out as applications-action or applications-games-action; Gnome currently goes one way and KDE the other but, either way, symlinks are cheap and it can be sorted out through freedesktop. (2) Ubuntu's own Humanity icon set includes icons of this form, but they are not used because of this bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-icon-theme/+bug/1201128/+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
Does "Headphone Mic Boost" disappear in alsamixer? -- 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
amixer -c 0 set 'Headphone Mic Boost',0 1 does not work, it says "Headphone Mic Boost" not found, so yes, I am however not familiar with alsamixer. Where would I find "Headphone Mic Boost"? -- 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 1676131] Re: Gnome Night Light doesn't work
In the meantime I've done a re-install of ubuntu-gnome 17.04. After that nightlight is working as expected on my primary display. I can chowever onfirm the report that nightlight does noth work on my secondary display, but I guess this is a separate bug. ** Bug watch added: GNOME Bug Tracker #783854 https://bugzilla.gnome.org/show_bug.cgi?id=783854 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1676131 Title: Gnome Night Light doesn't work Status in gnome-control-center package in Ubuntu: Incomplete Bug description: On the first boot of Ubuntu, the night light worked but after restart this option does nothing. I couldn't get any log from the terminal. Ubuntu Gnome 17.04 beta2 gnome-control-center 1:3.24.0-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1676131/+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
Yes it disappears! (forgot to run alsamixer as root). -- 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 1676131] Re: Gnome Night Light doesn't work
The dual monitor problem has been reported upstream as well: https://bugzilla.gnome.org/show_bug.cgi?id=783854 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1676131 Title: Gnome Night Light doesn't work Status in gnome-control-center package in Ubuntu: Incomplete Bug description: On the first boot of Ubuntu, the night light worked but after restart this option does nothing. I couldn't get any log from the terminal. Ubuntu Gnome 17.04 beta2 gnome-control-center 1:3.24.0-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1676131/+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 1699508] [NEW] package ubuntu-software 3.20.1+git20160420.1.ca63436.ubuntu-xenial-0ubuntu2 [modified: usr/share/ubuntu/applications/org.gnome.Software.desktop] failed to instal
Public bug reported: dpkg: error processing package ubuntu-software (--configure): package ubuntu-software is not ready for configuration cannot configure (current status 'half-installed') ... ... ... Errors were encountered while processing: ubuntu-software E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 16.04 Package: ubuntu-software 3.20.1+git20160420.1.ca63436.ubuntu-xenial-0ubuntu2 [modified: usr/share/ubuntu/applications/org.gnome.Software.desktop] ProcVersionSignature: Ubuntu 4.4.0-81.104-generic 4.4.67 Uname: Linux 4.4.0-81-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 Date: Wed Jun 21 18:55:55 2017 DuplicateSignature: package:ubuntu-software:3.20.1+git20160420.1.ca63436.ubuntu-xenial-0ubuntu2 [modified: usr/share/ubuntu/applications/org.gnome.Software.desktop] Processing triggers for mime-support (3.59ubuntu1) ... dpkg: error processing package ubuntu-software (--configure): package ubuntu-software is not ready for configuration ErrorMessage: package ubuntu-software is not ready for configuration cannot configure (current status 'half-installed') InstallationDate: Installed on 2017-02-13 (127 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: gnome-software Title: package ubuntu-software 3.20.1+git20160420.1.ca63436.ubuntu-xenial-0ubuntu2 [modified: usr/share/ubuntu/applications/org.gnome.Software.desktop] failed to install/upgrade: package ubuntu-software is not ready for configuration cannot configure (current status 'half-installed') UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-software (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 gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1699508 Title: package ubuntu-software 3.20.1+git20160420.1.ca63436.ubuntu-xenial- 0ubuntu2 [modified: usr/share/ubuntu/applications/org.gnome.Software.desktop] failed to install/upgrade: package ubuntu-software is not ready for configuration cannot configure (current status 'half-installed') Status in gnome-software package in Ubuntu: New Bug description: dpkg: error processing package ubuntu-software (--configure): package ubuntu-software is not ready for configuration cannot configure (current status 'half-installed') ... ... ... Errors were encountered while processing: ubuntu-software E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 16.04 Package: ubuntu-software 3.20.1+git20160420.1.ca63436.ubuntu-xenial-0ubuntu2 [modified: usr/share/ubuntu/applications/org.gnome.Software.desktop] ProcVersionSignature: Ubuntu 4.4.0-81.104-generic 4.4.67 Uname: Linux 4.4.0-81-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 Date: Wed Jun 21 18:55:55 2017 DuplicateSignature: package:ubuntu-software:3.20.1+git20160420.1.ca63436.ubuntu-xenial-0ubuntu2 [modified: usr/share/ubuntu/applications/org.gnome.Software.desktop] Processing triggers for mime-support (3.59ubuntu1) ... dpkg: error processing package ubuntu-software (--configure): package ubuntu-software is not ready for configuration ErrorMessage: package ubuntu-software is not ready for configuration cannot configure (current status 'half-installed') InstallationDate: Installed on 2017-02-13 (127 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: gnome-software Title: package ubuntu-software 3.20.1+git20160420.1.ca63436.ubuntu-xenial-0ubuntu2 [modified: usr/share/ubuntu/applications/org.gnome.Software.desktop] failed to install/upgrade: package ubuntu-software is not ready for configuration cannot configure (current status 'half-installed') UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1699508/+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 1699508] Re: package ubuntu-software 3.20.1+git20160420.1.ca63436.ubuntu-xenial-0ubuntu2 [modified: usr/share/ubuntu/applications/org.gnome.Software.desktop] failed to install/
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1699508 Title: package ubuntu-software 3.20.1+git20160420.1.ca63436.ubuntu-xenial- 0ubuntu2 [modified: usr/share/ubuntu/applications/org.gnome.Software.desktop] failed to install/upgrade: package ubuntu-software is not ready for configuration cannot configure (current status 'half-installed') Status in gnome-software package in Ubuntu: New Bug description: dpkg: error processing package ubuntu-software (--configure): package ubuntu-software is not ready for configuration cannot configure (current status 'half-installed') ... ... ... Errors were encountered while processing: ubuntu-software E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 16.04 Package: ubuntu-software 3.20.1+git20160420.1.ca63436.ubuntu-xenial-0ubuntu2 [modified: usr/share/ubuntu/applications/org.gnome.Software.desktop] ProcVersionSignature: Ubuntu 4.4.0-81.104-generic 4.4.67 Uname: Linux 4.4.0-81-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 Date: Wed Jun 21 18:55:55 2017 DuplicateSignature: package:ubuntu-software:3.20.1+git20160420.1.ca63436.ubuntu-xenial-0ubuntu2 [modified: usr/share/ubuntu/applications/org.gnome.Software.desktop] Processing triggers for mime-support (3.59ubuntu1) ... dpkg: error processing package ubuntu-software (--configure): package ubuntu-software is not ready for configuration ErrorMessage: package ubuntu-software is not ready for configuration cannot configure (current status 'half-installed') InstallationDate: Installed on 2017-02-13 (127 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: gnome-software Title: package ubuntu-software 3.20.1+git20160420.1.ca63436.ubuntu-xenial-0ubuntu2 [modified: usr/share/ubuntu/applications/org.gnome.Software.desktop] failed to install/upgrade: package ubuntu-software is not ready for configuration cannot configure (current status 'half-installed') UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1699508/+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 1377653] Re: HDMI sound output not detected / NVIDIA optimus laptop
Have a similar issue with my HP Pavilion DV6 Laptop under both Ubuntu 16.04 and Ubuntu Mate 16.04 using pulse audio. Video still displays out of HDMI port to TV but Audio hardware device disappears from sound applet (in my case "mate-volume-control-applet"). Curiously the HDMI device is visible at some level to aplay $ aplay -l List of PLAYBACK Hardware Devices card 0: PCH [HDA Intel PCH], device 0: 92HD81B1X5 Analog [92HD81B1X5 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0] Subdevices: 1/1 Subdevice #0: subdevice #0 Work-Around (temporarily SOLVES issue ... until the next time) --- I have developed the following work-around (for Mate ... but you can adapt it to standard Ubuntu) that recovers the HDMI sound (perhaps it may help users get by and/or some smart developer to track down the root cause):- Step 0: Open your terminal ... Step 1: Kill the (non-detecting) volume control process $ kill -9 $(ps aux |grep -v 'sudo\|grep' |grep -e "mate-volume-control-applet"| awk {'print $2'}) Step 2: Relaunch the volume-control process $ sudo mate-volume-control-applet Step 3: Then at the blinking terminal type ^Z Step 4: Now complete the manual terminal tty disassociation by typing $ bg Step 5: Now when you right click on your "mate-volume-control-applet" go to > Sound Preferences > Hardware Tab > Profile Drop Down ... should now show all the available sound devices including the HDMI output to the TV. --- The volume control applet just seems to forget about the sound hardware, never refreshes nor updates even with the HDMI lead being disconnected and reconnected. -- 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 1686066] Re: Rhythmbox no support for iPod nano 7th gen
Ist jetzt unterstützt. ** Changed in: libgpod (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libgpod in Ubuntu. https://bugs.launchpad.net/bugs/1686066 Title: Rhythmbox no support for iPod nano 7th gen Status in libgpod package in Ubuntu: Fix Released Bug description: I also filed a feature request for Rhythmbox, here the link https://bugzilla.gnome.org/show_bug.cgi?id=781191#c1 Ubuntu 16.04 (64Bit) It seems that libgpod needs to support the new iPod nano 7th gen first, then rhythmbox will support the device. Any chance of that happening? :~$ rhythmbox -D ipod (12:25:32) [0xe624c0] [rb_ipod_plugin_init] rb-ipod-plugin.c:92: RBIpodPlugin initialising (rhythmbox:9839): Gtk-WARNING **: Duplicate child name in GtkStack: Add to Playlist To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libgpod/+bug/1686066/+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 1691693] Re: package libreoffice-common 1:5.2.2-0ubuntu2 failed to install/upgrade: unable to open '/usr/lib/libreoffice/share/gallery/sg36.sdg.dpkg-new': Operation not permitt
Olivier, no, I'm having problems with the current kernel, can't connect to internet, but I'm using a previous one. I thought I had resolved the problems, but did and update yesterday and they are back again. -- 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/1691693 Title: package libreoffice-common 1:5.2.2-0ubuntu2 failed to install/upgrade: unable to open '/usr/lib/libreoffice/share/gallery/sg36.sdg.dpkg-new': Operation not permitted Status in libreoffice package in Ubuntu: Confirmed Bug description: I was trying to upgrade to 17.04 and the error plus loads of others came up. Even after partial upgrade again. ProblemType: Package DistroRelease: Ubuntu 17.04 Package: libreoffice-common 1:5.2.2-0ubuntu2 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 Date: Thu May 18 10:27:56 2017 DuplicateSignature: package:libreoffice-common:1:5.2.2-0ubuntu2 Unpacking libreoffice-common (1:5.3.1-0ubuntu2) over (1:5.2.2-0ubuntu2) ... dpkg: error processing archive /tmp/apt-dpkg-install-lHfAqY/17-libreoffice-common_1%3a5.3.1-0ubuntu2_all.deb (--unpack): unable to open '/usr/lib/libreoffice/share/gallery/sg36.sdg.dpkg-new': Operation not permitted ErrorMessage: unable to open '/usr/lib/libreoffice/share/gallery/sg36.sdg.dpkg-new': Operation not permitted InstallationDate: Installed on 2016-02-19 (453 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4 SourcePackage: libreoffice Title: package libreoffice-common 1:5.2.2-0ubuntu2 failed to install/upgrade: unable to open '/usr/lib/libreoffice/share/gallery/sg36.sdg.dpkg-new': Operation not permitted UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1691693/+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 1699424] Re: very slow performance video driver openGL ATI RV370
Siehe auch: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1694629 -- 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/1699424 Title: very slow performance video driver openGL ATI RV370 Status in gnome-terminal package in Ubuntu: New Bug description: rbeerli@Turbo:/usr/lib/nux$ ./unity_support_test -p OpenGL vendor string: X.Org R300 Project OpenGL renderer string: Gallium 0.4 on ATI RV370 OpenGL version string: 2.1 Mesa 17.0.3 Not software rendered:yes Not blacklisted: yes GLX fbconfig: yes GLX texture from pixmap: yes GL npot or rect textures: yes GL vertex program:yes GL fragment program: yes GL vertex buffer object: yes GL framebuffer object:yes GL version is 1.4+: yes Unity 3D supported: yes All applications are very slow. FF, Thunderbird, Libre, ... Since the upgrade from 16.04 to 17.04 ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: gnome-terminal 3.20.2-1ubuntu8 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 CurrentDesktop: Unity:Unity7 Date: Wed Jun 21 08:17:53 2017 ExecutablePath: /usr/lib/gnome-terminal/gnome-terminal-server InstallationDate: Installed on 2017-05-25 (26 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) 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/1699424/+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 1695403] Re: package hicolor-icon-theme 0.15-0ubuntu1 failed to install/upgrade: triggers looping, abandoned
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: hicolor-icon-theme (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hicolor-icon-theme in Ubuntu. https://bugs.launchpad.net/bugs/1695403 Title: package hicolor-icon-theme 0.15-0ubuntu1 failed to install/upgrade: triggers looping, abandoned Status in hicolor-icon-theme package in Ubuntu: Confirmed Bug description: no more info ProblemType: Package DistroRelease: Ubuntu 16.04 Package: hicolor-icon-theme 0.15-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62 Uname: Linux 4.4.0-78-generic i686 ApportVersion: 2.20.1-0ubuntu2.6 Architecture: i386 Date: Fri Jun 2 19:08:58 2017 Dependencies: ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2015-05-10 (754 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release i386 (20150218.1) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: hicolor-icon-theme Title: package hicolor-icon-theme 0.15-0ubuntu1 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: Upgraded to xenial on 2017-06-02 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hicolor-icon-theme/+bug/1695403/+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 671024] Re: can't connect to more than one openvpn at once
*** This bug is a duplicate of bug 91389 *** https://bugs.launchpad.net/bugs/91389 issue exists in ubuntu 16.10 -- 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/671024 Title: can't connect to more than one openvpn at once Status in network-manager-openvpn package in Ubuntu: Confirmed Status in network-manager-openvpn package in Arch Linux: New Status in network-manager-openvpn package in Gentoo Linux: New Bug description: Binary package hint: network-manager-openvpn Description: Ubuntu 10.04.1 LTS Release: 10.04 network-manager-openvpn: Installé : 0.8-0ubuntu3 Candidat : 0.8-0ubuntu3 Table de version : *** 0.8-0ubuntu3 0 500 http://archive.ubuntu.com/ubuntu/ lucid/universe Packages 100 /var/lib/dpkg/status network-manager: Installé : 0.8-0ubuntu3 Candidat : 0.8-0ubuntu3 Table de version : *** 0.8-0ubuntu3 0 500 http://archive.ubuntu.com/ubuntu/ lucid/main Packages 100 /var/lib/dpkg/status I would like to be able to connect to multiple openvpn in the same time , instead connexion manager greys out the other vpn when one start. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/671024/+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 1673820] Re: package python3-uno 1:5.1.6~rc2-0ubuntu1~xenial1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: libreoffice (Ubuntu) Status: New => Confirmed -- 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/1673820 Title: package python3-uno 1:5.1.6~rc2-0ubuntu1~xenial1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in libreoffice package in Ubuntu: Confirmed Bug description: this occurred after moving my ubuntu installation from an external usb drive to my internal drive ProblemType: Package DistroRelease: Ubuntu 16.04 Package: python3-uno 1:5.1.6~rc2-0ubuntu1~xenial1 ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11 Uname: Linux 4.8.0-36-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 Date: Tue Mar 14 08:52:15 2017 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2017-03-13 (0 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.19 SourcePackage: libreoffice Title: package python3-uno 1:5.1.6~rc2-0ubuntu1~xenial1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1673820/+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 1686344] Re: Mesa 17.0.x stable release
tested to be fine on Intel Kabylake GT3 and AMD R7 260X (Bonaire) -- 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/1686344 Title: Mesa 17.0.x stable release Status in mesa package in Ubuntu: Fix Released Status in mesa source package in Zesty: Fix Committed Bug description: [Impact] Mesa stable release for zesty & backport to xenial. Xenial needs newer libdrm from zesty. These are part of the hwe-16.04 stack refresh. [Test case] Install, run desktop session, test xonotic. the important hw drivers to test: - i965 (Intel) - radeonsi (AMD) [Regression potential] Spec compliance test suites are already run by Intel and others, so feature regressions should not be possible. GLESv1 support has been dropped from the packaging though, but packages that depend on libgles1-mesa have been pushed to proposed to drop the dependency, see bug 1676845 (applies to xenial). 17.0.x has been available for xenial and yakkety users for a while, and so far no-one has complained about driver regressions. [Other info] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1686344/+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 1699529] [NEW] i386 autopkgtests are unstable
Public bug reported: We had this before (maybe for a different reason). libreoffice's i386 autopkgtests are failing a lot of the time now. They are run when dependencies are uploaded, and so if they aren't reliable then they slow down the speed with which these updates can get into the release, because failures have to be manually retried. See: http://autopkgtest.ubuntu.com/packages/libr/libreoffice/artful/i386 ** Affects: libreoffice (Ubuntu) Importance: Undecided Assignee: Olivier Tilloy (osomon) Status: New ** Changed in: libreoffice (Ubuntu) Assignee: (unassigned) => Olivier Tilloy (osomon) -- 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/1699529 Title: i386 autopkgtests are unstable Status in libreoffice package in Ubuntu: New Bug description: We had this before (maybe for a different reason). libreoffice's i386 autopkgtests are failing a lot of the time now. They are run when dependencies are uploaded, and so if they aren't reliable then they slow down the speed with which these updates can get into the release, because failures have to be manually retried. See: http://autopkgtest.ubuntu.com/packages/libr/libreoffice/artful/i386 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1699529/+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 1699529] Re: i386 autopkgtests are unstable
Olivier, would be good if you could look at this if you have some time ... -- 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/1699529 Title: i386 autopkgtests are unstable Status in libreoffice package in Ubuntu: New Bug description: We had this before (maybe for a different reason). libreoffice's i386 autopkgtests are failing a lot of the time now. They are run when dependencies are uploaded, and so if they aren't reliable then they slow down the speed with which these updates can get into the release, because failures have to be manually retried. See: http://autopkgtest.ubuntu.com/packages/libr/libreoffice/artful/i386 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1699529/+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 1689033] Re: A few missing icons in version 2.4.3
** Changed in: gdk-pixbuf Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdk-pixbuf in Ubuntu. https://bugs.launchpad.net/bugs/1689033 Title: A few missing icons in version 2.4.3 Status in gdk-pixbuf: Incomplete Status in easytag package in Ubuntu: Confirmed Status in gdk-pixbuf package in Ubuntu: New Bug description: A few icons are missing in version 2.4.3 for zesty (and probably artful), see https://i.imgur.com/Cl4o36Sr.png To manage notifications about this bug go to: https://bugs.launchpad.net/gdk-pixbuf/+bug/1689033/+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
Launching chromium-browser with --use-gl=ANYSTRING (ANYSTRING really being any string, including invalid GL implementation names such as "foobarbaz", or valid ones such as "swiftshader") makes the issue go away. Note that when passing an invalid GL implementation name, swiftshader appears to be used, so this is the fallback option. -- 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: New 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 1697565] Re: Snaps without icons don't show as installed
Hello Robert, or anyone else affected, Accepted gnome-software into zesty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gnome- software/3.22.7-0ubuntu3.17.04.5 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! ** Tags added: verification-needed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1697565 Title: Snaps without icons don't show as installed Status in gnome-software package in Ubuntu: Fix Released Status in gnome-software source package in Xenial: Fix Committed Status in gnome-software source package in Yakkety: Won't Fix Status in gnome-software source package in Zesty: Fix Committed Status in gnome-software source package in Artful: Fix Released Bug description: [Impact] Snaps without icons don't show in the installed tab. They do show in search, because the icon is sourced from the store. [Test Case] 1. Open GNOME Software 2. Install a snap without an icon (e.g. moon-buggy) 3. Close GNOME Software 4. Open GNOME Software 5. Click "installed" tab Expected result: Installed snap is shown Observed result: Snap is not shown [Regression Potential] The code was refactored to download the store information for installed snaps. This means the store icon shows if the installed snap didn't have one. There is some risk of new bugs being caused by the refactoring. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1697565/+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 1693089] Please test proposed package
Hello Jeremy, or anyone else affected, Accepted desktop-file-utils into trusty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/desktop- file-utils/0.22-1ubuntu1.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 desktop-file-utils in Ubuntu. https://bugs.launchpad.net/bugs/1693089 Title: Cinnamon is not a recognized Desktop Environment before Ubuntu 16.04 LTS Status in desktop-file-utils package in Ubuntu: Fix Released Status in desktop-file-utils source package in Precise: In Progress Status in desktop-file-utils source package in Trusty: Fix Committed Bug description: Note Yes, I know precise is basically unsupported but it might be nice to fix Travis here anyway. Impact -- Cinnamon (and the less popular EDE and LXQt) desktops are not recognized by desktop-file-validate in Ubuntu 12.04 LTS or 14.04 LTS. This is a problem because the very popular Travis service for continuous integration (CI) on platforms like Github still uses 12.04 LTS. Travis does not offer a 16.04 platform and the 14.04 platform is still only in beta. This caused this pull request to fail its CI check: https://travis-ci.org/zdohnal/system-config-printer/builds/222023750 https://github.com/zdohnal/system-config-printer/pull/41 This SRU adds these Desktop Environments to the recognized list for 14.04 LTS: Cinnamon, EDE, LXQt. If accepted, 12.04 LTS will also add TDE. Test Case - 1. Save the following lines in a file named calc.desktop [Desktop Entry] Name=Calculator Exec=gnome-calculator Icon=accessories-calculator Type=Application OnlyShowIn=Cinnamon;LXQt;EDE; Categories=GNOME;GTK;Utility;Calculator; 2. Run desktop-file-validate calc.desktop The command should complete with no error message. A failure would look something like: calc.desktop: error: value "Cinnamon;LXQt;EDE;" for key "OnlyShowIn" in group "Desktop Entry" contains an unregistered value "Cinnamon"; values extending the format should start with "X-" Regression Potential - This only adds a few entries to the list of registered desktop environments. This change is backported from desktop-file-utils 0.23 which is in Ubuntu 16.04 LTS. [racb] Could there be some behaviour change somewhere that was depending somehow on Cinnamon's status being unregistered? For example in a test suite's expected output somewhere? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/desktop-file-utils/+bug/1693089/+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 1663097] Re: Show featured snaps
Hello Robert, or anyone else affected, Accepted gnome-software into zesty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gnome- software/3.22.7-0ubuntu3.17.04.5 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! ** Tags added: verification-needed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1663097 Title: Show featured snaps Status in gnome-software package in Ubuntu: Fix Released Status in gnome-software source package in Xenial: Triaged Status in gnome-software source package in Yakkety: Won't Fix Status in gnome-software source package in Zesty: Fix Committed Status in gnome-software source package in Artful: Fix Released Bug description: [Impact] GNOME Software doesn't show any snaps in the "Editor's Picks" section. snapd added a new feature to return snaps in the "featured" section and should be shown in GNOME Software. [Test Case] 1. Open GNOME Software Expected result: Some of the "Editor's Picks" apps should be snaps. Observed result: There are no snaps shown. [Regression Potential] Some risk of new behaviour adversely affecting GNOME Software startup. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1663097/+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 1688721] Re: Packages that trigger multiple debconf prompts fail to install
Hello Rafael, or anyone else affected, Accepted gnome-software into zesty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gnome- software/3.22.7-0ubuntu3.17.04.5 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: gnome-software (Ubuntu Zesty) Status: Incomplete => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1688721 Title: Packages that trigger multiple debconf prompts fail to install Status in gnome-software package in Ubuntu: Fix Released Status in gnome-software source package in Xenial: Fix Committed Status in gnome-software source package in Yakkety: Fix Committed Status in gnome-software source package in Zesty: Fix Committed Status in gnome-software source package in Artful: Fix Released Bug description: [Impact] Some packages stall on installing. These are packages that generate multiple debconf prompts (the prompts may be empty and so not user visible, e.g. gconf2-common). [Test Case] 1. Remove gconf2-common (warning, may uninstall packages like gnome-terminal): $ sudo apt purge gconf2-common 2. Download the debian package of Chrome from www.google.com/chrome. 3. Install the package (browser will prompt, or double click on package in Nautilus). Expected result: Chrome installs correctly. Observed result: The installation hangs on 51%. [Regression Potential] The debconf conde was modified to support multiple requests. This could expose other debconf issues or break other .deb install code. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1688721/+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
But launching with chromium-browser --use-gl=any, the issue happens again. And I can (sometimes) observe a similar issue with google-chrome when launched with --use-gl=any. -- 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: New 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 1692398] Please test proposed package
Hello Robert, or anyone else affected, Accepted gnome-software into zesty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gnome- software/3.22.7-0ubuntu3.17.04.5 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 gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1692398 Title: Input error can lead to continuous searches Status in gnome-software package in Ubuntu: Fix Released Status in gnome-software source package in Xenial: Fix Committed Status in gnome-software source package in Yakkety: Fix Committed Status in gnome-software source package in Zesty: Fix Committed Status in gnome-software source package in Artful: Fix Released Bug description: [Impact] An input error (e.g. a key being continuously pressed) in the gnome-software search field can lead to continuous searches being sent via snapd. This is beuause there is no limit in this search field. [Test Case] 1. Open GNOME Software 2. Click search button 3. Continuously press and release 't' Expected result: Searches stop after a the search field hits the character limit. Observed result: Searches are continuously generated for each key press (there is no limit). NOTE: Searches are shown in syslog (snapd debug message). [Regression potential] Low. The field is now limited to 100 characters and searches stop after this limit. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1692398/+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 1693089] Re: Cinnamon is not a recognized Desktop Environment before Ubuntu 16.04 LTS
Accepting for Trusty. Precise is EOL, so I'm reluctant to break expectations by touching it. If you think an exception is warranted, perhaps ask ubuntu-release@? ** Description changed: Note Yes, I know precise is basically unsupported but it might be nice to fix Travis here anyway. Impact -- Cinnamon (and the less popular EDE and LXQt) desktops are not recognized by desktop-file-validate in Ubuntu 12.04 LTS or 14.04 LTS. This is a problem because the very popular Travis service for continuous integration (CI) on platforms like Github still uses 12.04 LTS. Travis does not offer a 16.04 platform and the 14.04 platform is still only in beta. This caused this pull request to fail its CI check: https://travis-ci.org/zdohnal/system-config-printer/builds/222023750 https://github.com/zdohnal/system-config-printer/pull/41 This SRU adds these Desktop Environments to the recognized list for 14.04 LTS: Cinnamon, EDE, LXQt. If accepted, 12.04 LTS will also add TDE. Test Case - 1. Save the following lines in a file named calc.desktop [Desktop Entry] Name=Calculator Exec=gnome-calculator Icon=accessories-calculator Type=Application OnlyShowIn=Cinnamon;LXQt;EDE; Categories=GNOME;GTK;Utility;Calculator; 2. Run desktop-file-validate calc.desktop The command should complete with no error message. A failure would look something like: calc.desktop: error: value "Cinnamon;LXQt;EDE;" for key "OnlyShowIn" in group "Desktop Entry" contains an unregistered value "Cinnamon"; values extending the format should start with "X-" Regression Potential - This only adds a few entries to the list of registered desktop environments. This change is backported from desktop-file-utils 0.23 which is in Ubuntu 16.04 LTS. + + [racb] Could there be some behaviour change somewhere that was depending + somehow on Cinnamon's status being unregistered? For example in a test + suite's expected output somewhere? ** Changed in: desktop-file-utils (Ubuntu Trusty) Status: In Progress => Fix Committed ** Tags added: verification-needed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to desktop-file-utils in Ubuntu. https://bugs.launchpad.net/bugs/1693089 Title: Cinnamon is not a recognized Desktop Environment before Ubuntu 16.04 LTS Status in desktop-file-utils package in Ubuntu: Fix Released Status in desktop-file-utils source package in Precise: In Progress Status in desktop-file-utils source package in Trusty: Fix Committed Bug description: Note Yes, I know precise is basically unsupported but it might be nice to fix Travis here anyway. Impact -- Cinnamon (and the less popular EDE and LXQt) desktops are not recognized by desktop-file-validate in Ubuntu 12.04 LTS or 14.04 LTS. This is a problem because the very popular Travis service for continuous integration (CI) on platforms like Github still uses 12.04 LTS. Travis does not offer a 16.04 platform and the 14.04 platform is still only in beta. This caused this pull request to fail its CI check: https://travis-ci.org/zdohnal/system-config-printer/builds/222023750 https://github.com/zdohnal/system-config-printer/pull/41 This SRU adds these Desktop Environments to the recognized list for 14.04 LTS: Cinnamon, EDE, LXQt. If accepted, 12.04 LTS will also add TDE. Test Case - 1. Save the following lines in a file named calc.desktop [Desktop Entry] Name=Calculator Exec=gnome-calculator Icon=accessories-calculator Type=Application OnlyShowIn=Cinnamon;LXQt;EDE; Categories=GNOME;GTK;Utility;Calculator; 2. Run desktop-file-validate calc.desktop The command should complete with no error message. A failure would look something like: calc.desktop: error: value "Cinnamon;LXQt;EDE;" for key "OnlyShowIn" in group "Desktop Entry" contains an unregistered value "Cinnamon"; values extending the format should start with "X-" Regression Potential - This only adds a few entries to the list of registered desktop environments. This change is backported from desktop-file-utils 0.23 which is in Ubuntu 16.04 LTS. [racb] Could there be some behaviour change somewhere that was depending somehow on Cinnamon's status being unregistered? For example in a test suite's expected output somewhere? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/desktop-file-utils/+bug/1693089/+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 1689425] Re: /usr/bin/gnome-software:11:g_source_attach:debconf_accept_cb:socket_source_dispatch:g_main_dispatch:g_main_context_dispatch
Hello errors.ubuntu.com, or anyone else affected, Accepted gnome-software into zesty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gnome- software/3.22.7-0ubuntu3.17.04.5 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! ** Tags added: verification-needed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1689425 Title: /usr/bin/gnome- software:11:g_source_attach:debconf_accept_cb:socket_source_dispatch:g_main_dispatch:g_main_context_dispatch Status in gnome-software package in Ubuntu: Fix Released Status in gnome-software source package in Xenial: Fix Released Status in gnome-software source package in Yakkety: Fix Released Status in gnome-software source package in Zesty: Fix Committed Status in gnome-software source package in Artful: Fix Released Bug description: [Impact] The change to add debconf support (bug 1679435) caused new crashes to occur in errors.ubuntu.com. The stacktrace show this crash occurring when a g_socket_accept generates an error. The exact cause of this failing is unknown, but the fix is to handle this error like any other. [Test Case] 1. Run GNOME Software Expected result: Doesn't crash Observed result: Crashes reported on errors.ubuntu.com [Regression Potential] Low, we not just exit a function when an error occurs instead of crashing. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1689425/+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 1292398] Re: Second screen position isn't saved from one session to another
Same problem, when updating, from 14.04 LTS to 16.04 LTS. Desktop Environment: GNOME-Flashback: Unity (gnome-flashback-metacity) The strange thing is that in 14.04, this did not happen to me. I'm thinking of going back to Trusty. The momentary solution with the script, does not provide solution for the icons on the desktop, these, change their position and overlap, and not put back in their original position. Needs fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1292398 Title: Second screen position isn't saved from one session to another Status in elementary OS: Fix Released Status in GNOME Settings Daemon: Incomplete Status in GNOME Shell: Confirmed Status in Ubuntu GNOME: Confirmed Status in Ubuntu GNOME trusty series: Confirmed Status in Ubuntu GNOME xenial series: Confirmed Status in Ubuntu GNOME Flashback: Confirmed Status in Unity: New Status in gnome-settings-daemon package in Ubuntu: Triaged Status in gnome-shell package in Ubuntu: Triaged Bug description: (Noticed on Ubuntu 14.04 beta 1 GNOME) At work I have a second screen, which I prefer to virtually put on the left side of my laptop screen. Using gnome-control-center I can change the position of the second without problem. But when I disconnect the second screen (to work on another place) and then connect it again OR if I just power off the laptop and turn it on again, the second screen position is set back to the default right position. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gnome-control-center 1:3.6.3-0ubuntu53 ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6 Uname: Linux 3.13.0-17-generic x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Mar 14 08:50:00 2014 InstallationDate: Installed on 2014-03-01 (12 days ago) InstallationMedia: Ubuntu-GNOME 14.04 "Trusty Tahr" - Alpha amd64 (20140226) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_gnome-control-center: deja-dup 29.5-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/elementaryos/+bug/1292398/+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 1699551] [NEW] nm-openvpn connection fails with error: invalid cipher
Public bug reported: I think this is related to the update of network-manager to 1.4.4-1ubuntu3.1. Now I can't connect to my VPN using network-manager-openvpn because it fails with an error about an invalid cipher. The relavant error found int the log are: juin 21 18:26:36 titan nm-openvpn[6585]: Error: pushed cipher not allowed - aes-128-cbc not in AES-128-CBC or AES-256-GCM:AES-128-GCM juin 21 18:26:36 titan nm-openvpn[6585]: OPTIONS ERROR: failed to import crypto options juin 21 18:26:36 titan nm-openvpn[6585]: ERROR: Failed to apply push options juin 21 18:26:36 titan nm-openvpn[6585]: Failed to open tun/tap interface Given the error it seems to be a problem of bad case in the code ?? ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: network-manager-openvpn 1.2.6-2ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-24.28-generic 4.10.15 Uname: Linux 4.10.0-24-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 CurrentDesktop: Unity:Unity7 Date: Wed Jun 21 18:28:20 2017 InstallationDate: Installed on 2016-05-22 (394 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: network-manager-openvpn UpgradeStatus: Upgraded to zesty on 2017-04-14 (68 days ago) ** Affects: network-manager-openvpn (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug zesty -- 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/1699551 Title: nm-openvpn connection fails with error: invalid cipher Status in network-manager-openvpn package in Ubuntu: New Bug description: I think this is related to the update of network-manager to 1.4.4-1ubuntu3.1. Now I can't connect to my VPN using network-manager-openvpn because it fails with an error about an invalid cipher. The relavant error found int the log are: juin 21 18:26:36 titan nm-openvpn[6585]: Error: pushed cipher not allowed - aes-128-cbc not in AES-128-CBC or AES-256-GCM:AES-128-GCM juin 21 18:26:36 titan nm-openvpn[6585]: OPTIONS ERROR: failed to import crypto options juin 21 18:26:36 titan nm-openvpn[6585]: ERROR: Failed to apply push options juin 21 18:26:36 titan nm-openvpn[6585]: Failed to open tun/tap interface Given the error it seems to be a problem of bad case in the code ?? ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: network-manager-openvpn 1.2.6-2ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-24.28-generic 4.10.15 Uname: Linux 4.10.0-24-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 CurrentDesktop: Unity:Unity7 Date: Wed Jun 21 18:28:20 2017 InstallationDate: Installed on 2016-05-22 (394 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: network-manager-openvpn UpgradeStatus: Upgraded to zesty on 2017-04-14 (68 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1699551/+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 1667198] Re: gpu-manager should also support using custom xorg.conf files for Nvidia
Hello Alex, or anyone else affected, Accepted ubuntu-drivers-common into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source /ubuntu-drivers-common/1:0.4.17.3 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: ubuntu-drivers-common (Ubuntu Xenial) Status: In Progress => Fix Committed ** Tags added: verification-needed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1667198 Title: gpu-manager should also support using custom xorg.conf files for Nvidia Status in HWE Next: New Status in OEM Priority Project: Confirmed Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in ubuntu-drivers-common source package in Xenial: Fix Committed Bug description: SRU Request: [Impact] Different GPUs may require different options in the xorg.conf file. Currently this is not possible, since the options have been hardcoded in gpu-manager to configure the system automatically. This new (backported) feature allows users to tell gpu-manager to use their own custom xorg.confs for their NVIDIA GPUs. [Test Case] 1) Enable the xenial-proposed repository, and install the ubuntu-drivers-common and the nvidia-prime packages. 2) Install the nvidia driver. 3) Place your configuration file(s) in the /usr/share/gpu-manager.d directory. If you are using a non-hybrid system, you can create the /usr/share /gpu-manager.d/non-hybrid file. In case of a hybrid system, you can specify /usr/share/gpu-manager.d/hybrid-performance and/or /usr/share /gpu-manager.d/hybrid-power-saving, depending on the power profile you intend to apply your settings to. 4) Restart the system and see if it boots correctly. If unsure, please attach your /var/log/gpu-manager.log and /var/log/Xorg.0.log 5) Make sure that the /etc/X11/xorg.conf matches the file you specified in 3) [Regression Potential] Low, the above mentioned changes are already in Artful, and will not affect the system's behaviour unless new configuration files are put in the /usr/share/gpu-manager.d/ directory. __ This feature has been implemented for Intel (ex. gpumanager_uxa), which is parsing kernel parameter to add option in xorg.conf (commit ff3a4e54). And now Nvidia also need this feature to add Option "nvidiaXineramaInfo" "off" to fix some issues. Btw, I'm thinking it might be a more flexible to have a config file which user could add all options as they want so that we could prevent keeping change gpu-manager when some more options are needed in the future. Needed by LP: #1653592 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1667198/+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 1693089] Re: Cinnamon is not a recognized Desktop Environment before Ubuntu 16.04 LTS
Robie, infinity rejected the Precise upload earlier with basically the same answer. I thought it was worth me asking, but I'm not going to push any further with the Precise update. ** Changed in: desktop-file-utils (Ubuntu Precise) Status: In Progress => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to desktop-file-utils in Ubuntu. https://bugs.launchpad.net/bugs/1693089 Title: Cinnamon is not a recognized Desktop Environment before Ubuntu 16.04 LTS Status in desktop-file-utils package in Ubuntu: Fix Released Status in desktop-file-utils source package in Precise: Won't Fix Status in desktop-file-utils source package in Trusty: Fix Committed Bug description: Note Yes, I know precise is basically unsupported but it might be nice to fix Travis here anyway. Impact -- Cinnamon (and the less popular EDE and LXQt) desktops are not recognized by desktop-file-validate in Ubuntu 12.04 LTS or 14.04 LTS. This is a problem because the very popular Travis service for continuous integration (CI) on platforms like Github still uses 12.04 LTS. Travis does not offer a 16.04 platform and the 14.04 platform is still only in beta. This caused this pull request to fail its CI check: https://travis-ci.org/zdohnal/system-config-printer/builds/222023750 https://github.com/zdohnal/system-config-printer/pull/41 This SRU adds these Desktop Environments to the recognized list for 14.04 LTS: Cinnamon, EDE, LXQt. If accepted, 12.04 LTS will also add TDE. Test Case - 1. Save the following lines in a file named calc.desktop [Desktop Entry] Name=Calculator Exec=gnome-calculator Icon=accessories-calculator Type=Application OnlyShowIn=Cinnamon;LXQt;EDE; Categories=GNOME;GTK;Utility;Calculator; 2. Run desktop-file-validate calc.desktop The command should complete with no error message. A failure would look something like: calc.desktop: error: value "Cinnamon;LXQt;EDE;" for key "OnlyShowIn" in group "Desktop Entry" contains an unregistered value "Cinnamon"; values extending the format should start with "X-" Regression Potential - This only adds a few entries to the list of registered desktop environments. This change is backported from desktop-file-utils 0.23 which is in Ubuntu 16.04 LTS. [racb] Could there be some behaviour change somewhere that was depending somehow on Cinnamon's status being unregistered? For example in a test suite's expected output somewhere? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/desktop-file-utils/+bug/1693089/+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 1636564] Re: Segfault from libX11.so.6.3.0
I have the same problem. See the attached syslog. The x-server almost crashes, and if I wait for a long time I might manage to get back to the login screen. The problem seems to occur mainly in my case when using the Google Chrome browswer. I have an Nvidia card using KMS and Nouveau, and my network connection is via WiFi. I can confirm the problem is distro-inpependent, I use Gentoo Linux. ** Attachment added: "Syslog" https://bugs.launchpad.net/ubuntu/+source/libx11/+bug/1636564/+attachment/4900387/+files/syslog.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libx11 in Ubuntu. https://bugs.launchpad.net/bugs/1636564 Title: Segfault from libX11.so.6.3.0 Status in libx11 package in Ubuntu: Confirmed Bug description: Something went wrong with my Ubuntu 16.04 LTS desktop today. When I got back to the system Mattermost and a Chrome were indicating that the network was not working. I started to look about and it seemed that my main ethernet network connection had lost its IPv4 address somehow. ifconfig and the GUI network manager confirmed this. To try and resolve this I physically removed the connector and the plugged it back in. Shortly after I did this my GUI seemed to die out and I ended up back at the login screen. Once everything had calmed down I logged back in. After some digging about in the logs I noticed the following in /var/log/kern.log Oct 25 13:01:09 thorne-ul-dt kernel: [694321.877561] Mattermost[744]: segfault at 968 ip 7f8a9e257643 sp 7ffe72a3b510 error 4 in libX11.so.6.3.0[7f8a9e22f000+135000] Oct 25 13:01:09 thorne-ul-dt kernel: [694322.029362] chrome[745]: segfault at 968 ip 7fd4b5c73643 sp 7fff94f78d90 error 4 in libX11.so.6.3.0[7fd4b5c4b000+135000] That seemed to be the correct time for the problem I noticed. What exactly caused it I am not sure. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: libx11-6 2:1.6.3-1ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-42.62-generic 4.4.21 Uname: Linux 4.4.0-42-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Tue Oct 25 17:07:28 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [1458:d000] InstallationDate: Installed on 2015-03-12 (592 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) MachineType: Gigabyte Technology Co., Ltd. H81M-DS2V ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-38-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash crashkernel=384M-:128M vt.handoff=7 SourcePackage: libx11 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/11/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F6 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H81M-DS2V 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.:bvrF6:bd08/11/2015:svnGigabyteTechnologyCo.,Ltd.:pnH81M-DS2V:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-DS2V:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: H81M-DS2V dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.1 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.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Tue Oct 25 13:01:04 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id
[Desktop-packages] [Bug 1699557] [NEW] Evolution: send inline images as attachments
Public bug reported: Since I upgraded from Ubuntu 16 to Ubuntu 17, evolution has stopped working when sending HTML messages with inline images, copy/paste an image inside the body not as attachment. Previous to the update, the images were sent and received inside the HTML body and displayed correctly in the email content. Since I upgraded, the images are received as attachments and they aren't displayed inside the HTML message content. The problem seems to be on the HTML sent, because I've tested to receive the messages in different email clients (Evolution and Outlook) and all of them receives the email images in the same way, as attachments, not inside the HTML content. Ubuntu release: 17.04 Evolution version: 3.22.6-1ubuntu1 ** Affects: evolution (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/1699557 Title: Evolution: send inline images as attachments Status in evolution package in Ubuntu: New Bug description: Since I upgraded from Ubuntu 16 to Ubuntu 17, evolution has stopped working when sending HTML messages with inline images, copy/paste an image inside the body not as attachment. Previous to the update, the images were sent and received inside the HTML body and displayed correctly in the email content. Since I upgraded, the images are received as attachments and they aren't displayed inside the HTML message content. The problem seems to be on the HTML sent, because I've tested to receive the messages in different email clients (Evolution and Outlook) and all of them receives the email images in the same way, as attachments, not inside the HTML content. Ubuntu release: 17.04 Evolution version: 3.22.6-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1699557/+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 1670036] Re: Misapplied patches in 4.0.6-2ubuntu0.1 break reading and writing JPEG compressed files
** Changed in: libtiff Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to tiff in Ubuntu. https://bugs.launchpad.net/bugs/1670036 Title: Misapplied patches in 4.0.6-2ubuntu0.1 break reading and writing JPEG compressed files Status in LibTIFF: Fix Released Status in tiff package in Ubuntu: Invalid Status in tiff source package in Trusty: Fix Released Status in tiff source package in Xenial: Fix Released Status in tiff source package in Yakkety: Fix Released Bug description: The patches applied to libtiff 4.0.6 in 4.0.6-2ubuntu01 seem to break JPEG tiff read and write. To reproduce: $ tiffcp -c jpeg k2a.tif x.tif (where k2a.tif is a simple uncompressed RGB strip tiff) appears to work. However, x.tif, the output, will now not read without warnings: $ tiffcp x.tif y.tif TIFFFetchNormalTag: Warning, ASCII value for tag "JPEGTables" does not end in null byte. Forcing it to be null. JPEGLib: Warning, Premature end of JPEG file. This was working fine until a couple of days ago, so I guess it's one of the most recent patches. Some packages using libtiff seem to be broken too. For example, openslide, which uses libtiff to load jp2k-compressed slide images, is no longer working: $ openslide-write-png CMU-1-Small-Region.svs 0 0 0 100 100 x.png TIFFFetchNormalTag: Warning, ASCII value for tag "JPEGTables" does not end in null byte. Forcing it to be null. TIFFFetchNormalTag: Warning, ASCII value for tag "JPEGTables" does not end in null byte. Forcing it ... repeats 8 more times openslide-write-png: Premature end of JPEG file and x.png is not a valid PNG image. The test .svs image may be downloaded here: http://openslide.cs.cmu.edu/download/openslide-testdata/Aperio/ To manage notifications about this bug go to: https://bugs.launchpad.net/libtiff/+bug/1670036/+subscriptions -- Mailing list: https://launchpad.net/~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 1588150] Re: Remove webkitgtk from archive
This bug was fixed in the package bijiben - 3.24.0-0ubuntu1 --- bijiben (3.24.0-0ubuntu1) artful; urgency=medium * New upstream release * debian/control: - Switch to webkit2gtk (LP: #1588150) - Drop obsolete Build-Depends on libedataserverui1.2-dev * Bump dh compat to 10 * Backport 2 patches to fix build: - fix-redundant-decls-warning.patch - fix-format-warning.patch -- Jeremy Bicha Fri, 16 Jun 2017 20:16:51 -0400 ** Changed in: bijiben (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/1588150 Title: Remove webkitgtk from archive Status in Bijiben: Fix Released Status in Empathy: Fix Released Status in Evolution: Fix Released Status in Geary: Fix Released Status in Liferea: Fix Released Status in LightDM Webkit Greeter: Fix Committed Status in bijiben package in Ubuntu: Fix Released Status in birdfont package in Ubuntu: Fix Committed Status in cairo-dock-plugins package in Ubuntu: Triaged Status in empathy package in Ubuntu: Triaged Status in evolution package in Ubuntu: Fix Released Status in geary package in Ubuntu: Triaged Status in gnome-web-photo package in Ubuntu: Triaged Status in gtkpod package in Ubuntu: Triaged Status in liferea package in Ubuntu: Fix Released Status in lightdm-webkit-greeter package in Ubuntu: In Progress Status in maildir-utils package in Ubuntu: Triaged Status in surf package in Ubuntu: Fix Released Status in webkitgtk package in Ubuntu: Triaged Status in xiphos package in Ubuntu: Triaged Status in xombrero package in Ubuntu: Triaged Bug description: webkitgtk is obsolete and has been replaced by webkit2gtk. This requires things to be ported to the new API. To manage notifications about this bug go to: https://bugs.launchpad.net/bijiben/+bug/1588150/+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 1699551] Re: nm-openvpn connection fails with error: invalid cipher
Same error here. -- 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/1699551 Title: nm-openvpn connection fails with error: invalid cipher Status in network-manager-openvpn package in Ubuntu: New Bug description: I think this is related to the update of network-manager to 1.4.4-1ubuntu3.1. Now I can't connect to my VPN using network-manager-openvpn because it fails with an error about an invalid cipher. The relavant error found int the log are: juin 21 18:26:36 titan nm-openvpn[6585]: Error: pushed cipher not allowed - aes-128-cbc not in AES-128-CBC or AES-256-GCM:AES-128-GCM juin 21 18:26:36 titan nm-openvpn[6585]: OPTIONS ERROR: failed to import crypto options juin 21 18:26:36 titan nm-openvpn[6585]: ERROR: Failed to apply push options juin 21 18:26:36 titan nm-openvpn[6585]: Failed to open tun/tap interface Given the error it seems to be a problem of bad case in the code ?? ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: network-manager-openvpn 1.2.6-2ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-24.28-generic 4.10.15 Uname: Linux 4.10.0-24-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 CurrentDesktop: Unity:Unity7 Date: Wed Jun 21 18:28:20 2017 InstallationDate: Installed on 2016-05-22 (394 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: network-manager-openvpn UpgradeStatus: Upgraded to zesty on 2017-04-14 (68 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1699551/+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 1689825] Re: gnome-keyring not unlocked on boot
I am experiencing the same issue on one of my two machines. The 'Password and Keys' padlock icon next to 'Login' remains locked even with the correct password, and I'm unable to use Chrome, access e-mail etc.. I'm no expert but, in case it helps, these are two differences between the two machines I'm aware of... - the machine with the problem has an encrypted installation and the other not. Otherwise both installations are similar (basic 16.04 and not much else) - if I enter "ps aux | grep keyring" I get two 'gnome-keyring-daemon' processes listed on the problem machine (one for user 'lightdm' and one for myself), and only one on the machine without the problem (user is myself) The machine with the problem is almost useless for the moment - would be great to get a solution. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1689825 Title: gnome-keyring not unlocked on boot Status in chromium-browser package in Ubuntu: Invalid Status in gnome-keyring package in Ubuntu: Confirmed Status in libgnome-keyring package in Ubuntu: Confirmed Bug description: 1) Release: 16.04.2 2) gnome-keyring: 3.18.3-0ubuntu2 3) Login. gnome-keyring unlocks "login" features including for google chrome 4) gnome-keyring is not unlocked, chrome takes 2 minutes to open and with no secure password features(sync) functioning. For the past couple days, chrome on Ubuntu 16.04 takes a REALLY long time (maybe 2 minutes) to start. Once chrome is started, I am not able to sync and any secure password features are broken. I found out this is due to gnome-keyring not being unlocked at login. There's also no way to unlock the "login" portion of the keyring from the running daemon by default. I have to kill the gnome-keyring process and start without "--login" as a parameter. Then the "login" section shows up which I'm able to unlock. From there chrome starts up instantly but asks the following: Enter password to unlock your login keyring The login keyring did not get unlocked when you logged into your computer After that, all of it's sync and secure features are functional. Starting google-chrome-stable from a command line at boot without running the above workaround shows the following error messages: Gkr-Message: secret service operation failed: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. Gkr-Message: secret service operation failed: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. [4364:4393:0510/100407.740292:ERROR:token_service_table.cc(130)] Failed to decrypt token for service AccountId-108842767310111573264 [4364:4445:0510/100407.740292:ERROR:gcm_store_impl.cc(929)] Failed to restore security token. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gnome-keyring 3.18.3-0ubuntu2 ProcVersionSignature: Ubuntu 4.8.0-52.55~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-52-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: GNOME-Flashback:Unity Date: Wed May 10 09:43:37 2017 SourcePackage: gnome-keyring UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1689825/+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 1689825] Re: gnome-keyring not unlocked on boot
The only "permanent" (well, it still asks for the password once when opening google-chrome after login) workaround I found was creating a startup item as described here: https://askubuntu.com/a/911896. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1689825 Title: gnome-keyring not unlocked on boot Status in chromium-browser package in Ubuntu: Invalid Status in gnome-keyring package in Ubuntu: Confirmed Status in libgnome-keyring package in Ubuntu: Confirmed Bug description: 1) Release: 16.04.2 2) gnome-keyring: 3.18.3-0ubuntu2 3) Login. gnome-keyring unlocks "login" features including for google chrome 4) gnome-keyring is not unlocked, chrome takes 2 minutes to open and with no secure password features(sync) functioning. For the past couple days, chrome on Ubuntu 16.04 takes a REALLY long time (maybe 2 minutes) to start. Once chrome is started, I am not able to sync and any secure password features are broken. I found out this is due to gnome-keyring not being unlocked at login. There's also no way to unlock the "login" portion of the keyring from the running daemon by default. I have to kill the gnome-keyring process and start without "--login" as a parameter. Then the "login" section shows up which I'm able to unlock. From there chrome starts up instantly but asks the following: Enter password to unlock your login keyring The login keyring did not get unlocked when you logged into your computer After that, all of it's sync and secure features are functional. Starting google-chrome-stable from a command line at boot without running the above workaround shows the following error messages: Gkr-Message: secret service operation failed: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. Gkr-Message: secret service operation failed: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. [4364:4393:0510/100407.740292:ERROR:token_service_table.cc(130)] Failed to decrypt token for service AccountId-108842767310111573264 [4364:4445:0510/100407.740292:ERROR:gcm_store_impl.cc(929)] Failed to restore security token. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gnome-keyring 3.18.3-0ubuntu2 ProcVersionSignature: Ubuntu 4.8.0-52.55~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-52-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: GNOME-Flashback:Unity Date: Wed May 10 09:43:37 2017 SourcePackage: gnome-keyring UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1689825/+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 1698287] Re: i965-va-driver fails to load in a Wayland session
Bugs in gstreamer-vaapi and totem according to upstream. ** Changed in: intel-vaapi-driver (Ubuntu) Status: New => Invalid -- 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/1698287 Title: i965-va-driver fails to load in a Wayland session Status in Libva: New Status in gstreamer-vaapi package in Ubuntu: New Status in intel-vaapi-driver package in Ubuntu: Invalid Status in totem package in Ubuntu: New Bug description: The Intel i965 VA-API driver works well in Xorg sessions (Unity7 and Gnome Shell). But it refuses to load when in a Wayland session: $ totem bbb_sunflower_1080p_60fps_normal.mp4 libva error: va_getDriverName() failed with unknown libva error,driver_name=(null) $ env LIBVA_DRIVER_NAME=i965 totem bbb_sunflower_1080p_60fps_normal.mp4 totem: intel_driver.c:112: intel_driver_init: Assertion `VA_CHECK_DRM_AUTH_TYPE(ctx, VA_DRM_AUTH_DRI1) || VA_CHECK_DRM_AUTH_TYPE(ctx, VA_DRM_AUTH_DRI2) || VA_CHECK_DRM_AUTH_TYPE(ctx, VA_DRM_AUTH_CUSTOM)' failed. Aborted (core dumped) $ gst-play-1.0 bbb_sunflower_1080p_60fps_normal.mp4 Press 'k' to see a list of keyboard shortcuts. Now playing /home/dan/Videos/bbb_sunflower_1080p_60fps_normal.mp4 Redistribute latency... Redistribute latency... ERROR Internal error: could not render surface for file:///home/dan/Videos/bbb_sunflower_1080p_60fps_normal.mp4 ERROR debug information: ../../../gst/vaapi/gstvaapisink.c(1482): gst_vaapisink_show_frame_unlocked (): /GstPlayBin:playbin/GstPlaySink:playsink/GstBin:vbin/GstVaapiSink:vaapisink0 ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: i965-va-driver 1.8.1-1 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 13:40:38 2017 InstallationDate: Installed on 2017-05-03 (44 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502) SourcePackage: intel-vaapi-driver UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/libva/+bug/1698287/+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 465676] Re: Apply button should be inactivated if there are no changes to apply
** Changed in: gnome-control-center (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/465676 Title: Apply button should be inactivated if there are no changes to apply Status in gnome-control-center: Fix Released Status in gnome-control-center package in Ubuntu: Fix Released Bug description: Binary package hint: gnome-control-center The Apply button for the screen resolution config applet should be disabled when the user hasn't changed anything. Or, alternatively, the Apply button should not do anything if the user did not change any setting. The issue is that having it enabled leads to the following endless cycle: 1. Open the Screen resolution config applet from System/Preferences 2. Change the settings of some monitor 3. Click apply 4. Screens are configured correctly 5. Click "maintain configuration" in the countdown dialog that pops up 6. The config applet is still displayed, with the Apply button enabled 7. Not sure what I should do, so click apply -> GOTO 5 This actually happened to my girlfriend. She was able to setup her external monitor all right but she said the countdown dialog would pop up over and over, and that was because she clicked apply over and over... This is on Karmic, updated yesterday. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/465676/+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 386826] Re: monitor canvas should be 'normalized' after each drag'n'drop operation
** Changed in: gnome-control-center (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/386826 Title: monitor canvas should be 'normalized' after each drag'n'drop operation Status in gnome-control-center: Fix Released Status in gnome-control-center package in Ubuntu: Fix Released Bug description: Binary package hint: gnome-control-center Currently, you can drag monitors out of visible space quite easily, and they would never come back so you can't drag them any more. To fix this, I'd propose to normalize (fit to view) the monitor layout after each drag'n'drop operation rather than just at application start. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/386826/+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] [NEW] [FTBFS] libqmi 1.18.0-1 fails test during build time
Public bug reported: 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 @@ ctx->step++; /* Fall down */ +case DEVICE_OPEN_CONTEXT_STEP_DRIVER: +ctx->driver = __qmi_utils_get_driver (ctx->se
[Desktop-packages] [Bug 1585084] Re: Volume notification keeps popping up constantly (the notify-OSD bubble on top-right corner)
Unfortunately I'm experiencing the same problem but with 17.04. The only difference to the previous reports that volume adjustment is happening in almost every second and the notification popup is visible constantly (it is flickering when the volume adjustment happens). So it is quite annoying. When I remove my headphones from the front audio jack, the autonomous volume adjusting stops. Interestingly i have never had similar problems with any of the previous versions of Ubuntu (starting from 12.04). -- 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/1585084 Title: Volume notification keeps popping up constantly (the notify-OSD bubble on top-right corner) Status in pulseaudio package in Ubuntu: Fix Released Bug description: I upgraded to Ubuntu 16.04 yesterday, I did a clean install while preserving the home directory which is mounted in a separate partition. Even during the installation I had constant volume notification bubble appearing on the top-right corner of my screen, it would come and go about twice every minute. I just thought it was due to installing hardware drivers or something but the problem persisted even when I booted into the freshly installed system. I did some searching and two users reported the exact problem. And one more suggested this happens because constant disconnect and reconnect of the sound card which makes sense as the sound settings flashes briefly during every popup. Someone on IRC suggested to kill pulseaudio and thus restart it, that does not fix the issue. I also tried the Live environment thinking it might be due to some old config files in home partition (which was preserved during upgrade), but this problem happens in the live environment as well, which makes sense because it was present during installation as well. Users with the same issue: http://ubuntuforums.org/showthread.php?t=2323815 http://askubuntu.com/questions/773008/constant-volume-osd-in-16-04 http://askubuntu.com/questions/767466/sound-card-being-disconnected-reconnected-constantly Thanks. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: pulseaudio 1:8.0-0ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: sidd 1651 F pulseaudio /dev/snd/controlC0: sidd 1651 F pulseaudio /dev/snd/controlC1: sidd 1651 F pulseaudio CurrentDesktop: Unity Date: Tue May 24 12:31:12 2016 InstallationDate: Installed on 2016-05-23 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/23/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0705 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: M5A97 EVO dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0705:bd08/23/2011:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKComputerINC.:rnM5A97EVO:rvrRev1.xx:cvnToBeFilledByO.E.M.: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: To be filled by O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1585084/+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: + /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 + 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 + 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; +} + +/
[Desktop-packages] [Bug 1453655] Re: desktop icons disappear on Ubuntu 15.04 when clicking Open Dropbox folder
Same issue in Ubuntu 16.10 -- 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/1453655 Title: desktop icons disappear on Ubuntu 15.04 when clicking Open Dropbox folder Status in Nautilus: Fix Released Status in nautilus package in Ubuntu: Fix Released Status in nautilus-dropbox package in Ubuntu: Confirmed Status in nautilus source package in Vivid: Fix Released Status in nautilus source package in Wily: Fix Released Bug description: I've been using both Ubuntu and dropbox for several years. With Ubuntu 15.04 there is a new problem that my desktop icons disappear when I click on the dropbox icon in the status bar and choose Open Dropbox Folder. Then the desktop icons will disappear - but will remain visible in Files -> Desktop. The only way I know to get the desktop icons back is to log out and then log back in again. The bug is 100% reproducible, and it never appeared before 15.04. I also have Copy on my status bar. Clicking on Copy -> Open Copy Folder has no problems. Likewise I can use File with a right click and use Open a New Window and that too is OK. Only dropbox has a problem and only since 15.04 If I can help in any way, please contact me ilan.tal - at - gmail.com [Impact] DE-agnostic programs that invoke nautilus using "nautilus --no-desktop" will make the nautilus-rendered desktop vanish. Dropbox is one such case. [Test Case] 1. Launch nautilus, and make sure it is currently rendering the desktop. 2. Run "nautilus --no-desktop /" 3. See if the desktop vanishes. [Regression Potential] The patch is relatively trivial, only affecting the --no-desktop codepath. As a worst case, --no-desktop would not function correctly in cases where nautilus is not already running (--no-desktop when nautilus is not already running means nautilus should not render the desktop at all). Just to make sure, this additional test case should be used: 1. Kill nautilus, and make sure it doesn't get relaunched. 2. Check to see what the desktop looks like (shouldn't be rendered by nautilus, at least) 3. Launch "nautilus --no-desktop /" 4. Make sure that nautilus really doesn't render a desktop. To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1453655/+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 1699618] [NEW] jetty hangs on startup under latest 3.13.0-121-generic kernel
Public bug reported: I'm afraid I don't have a huge amount of information to share on this one yet, but its another issue I've seen since applying this weeks kernel update. I have a Ubuntu 14.04 host running Solr within Jetty, but this hangs on startup when running the latest kernel: $ sudo service jetty start * Starting Jetty servlet engine. jetty * /var/run/jetty.pid exists, but jetty was not running. Ignoring /var/run/jetty.pid /etc/init.d/jetty: 274: /etc/init.d/jetty: /usr/sbin/rotatelogs: not found * Jetty servlet engine started, reachable on http://hostname-goes-here:8983/. jetty ...fail! $ ps -ef | grep [j]ava root 3389 1 0 23:25 ?00:00:00 jsvc.exec -user jetty -cp /usr/share/java/commons-daemon.jar:/usr/share/jetty/start.jar:/usr/share/jetty/start-daemon.jar:/usr/lib/jvm/default-java/lib/tools.jar -outfile /var/log/jetty/out.log -errfile /var/log/jetty/out.log -pidfile /var/run/jetty.pid -Xmx256m -Djava.awt.headless=true -Djava.library.path=/usr/lib -Djava.io.tmpdir=/var/cache/jetty/data -DSTART=/etc/jetty/start.config -Djetty.home=/usr/share/jetty -Djetty.logs=/var/log/jetty -Djetty.host= -Djetty.port=8983 org.mortbay.jetty.start.daemon.Bootstrap /etc/jetty/jetty-logging.xml /etc/jetty/jetty.xml /etc/jetty/jetty-shared-webapps.xml $ sudo service jetty stop * Stopping Jetty servlet engine (was reachable on http://tenshi-prod-ckan:8983/). jetty * (not running). $ ps -ef | grep [j]ava root 3389 1 0 23:25 ?00:00:00 jsvc.exec -user jetty -cp /usr/share/java/commons-daemon.jar:/usr/share/jetty/start.jar:/usr/share/jetty/start-daemon.jar:/usr/lib/jvm/default-java/lib/tools.jar -outfile /var/log/jetty/out.log -errfile /var/log/jetty/out.log -pidfile /var/run/jetty.pid -Xmx256m -Djava.awt.headless=true -Djava.library.path=/usr/lib -Djava.io.tmpdir=/var/cache/jetty/data -DSTART=/etc/jetty/start.config -Djetty.home=/usr/share/jetty -Djetty.logs=/var/log/jetty -Djetty.host= -Djetty.port=8983 org.mortbay.jetty.start.daemon.Bootstrap /etc/jetty/jetty-logging.xml /etc/jetty/jetty.xml /etc/jetty/jetty-shared-webapps.xml In this instance I can only terminate it with a "sudo kill -9 3389" which causes "Service killed by signal 11" to be logged to /var/log/jetty/out.log This is when booting the 3.13.0-121-generic - booting back into 3.13.0-119-generic sees the service start fine. The host is running OpenJDK 7u131-2.6.9-0ubuntu0.14.04.2. ** Affects: jetty (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to jetty in Ubuntu. https://bugs.launchpad.net/bugs/1699618 Title: jetty hangs on startup under latest 3.13.0-121-generic kernel Status in jetty package in Ubuntu: New Bug description: I'm afraid I don't have a huge amount of information to share on this one yet, but its another issue I've seen since applying this weeks kernel update. I have a Ubuntu 14.04 host running Solr within Jetty, but this hangs on startup when running the latest kernel: $ sudo service jetty start * Starting Jetty servlet engine. jetty * /var/run/jetty.pid exists, but jetty was not running. Ignoring /var/run/jetty.pid /etc/init.d/jetty: 274: /etc/init.d/jetty: /usr/sbin/rotatelogs: not found * Jetty servlet engine started, reachable on http://hostname-goes-here:8983/. jetty ...fail! $ ps -ef | grep [j]ava root 3389 1 0 23:25 ?00:00:00 jsvc.exec -user jetty -cp /usr/share/java/commons-daemon.jar:/usr/share/jetty/start.jar:/usr/share/jetty/start-daemon.jar:/usr/lib/jvm/default-java/lib/tools.jar -outfile /var/log/jetty/out.log -errfile /var/log/jetty/out.log -pidfile /var/run/jetty.pid -Xmx256m -Djava.awt.headless=true -Djava.library.path=/usr/lib -Djava.io.tmpdir=/var/cache/jetty/data -DSTART=/etc/jetty/start.config -Djetty.home=/usr/share/jetty -Djetty.logs=/var/log/jetty -Djetty.host= -Djetty.port=8983 org.mortbay.jetty.start.daemon.Bootstrap /etc/jetty/jetty-logging.xml /etc/jetty/jetty.xml /etc/jetty/jetty-shared-webapps.xml $ sudo service jetty stop * Stopping Jetty servlet engine (was reachable on http://tenshi-prod-ckan:8983/). jetty * (not running). $ ps -ef | grep [j]ava root 3389 1 0 23:25 ?00:00:00 jsvc.exec -user jetty -cp /usr/share/java/commons-daemon.jar:/usr/share/jetty/start.jar:/usr/share/jetty/start-daemon.jar:/usr/lib/jvm/default-java/lib/tools.jar -outfile /var/log/jetty/out.log -errfile /var/log/jetty/out.log -pidfile /var/run/jetty.pid -Xmx256m -Djava.awt.headless=true -Djava.library.path=/usr/lib -Djava.io.tmpdir=/var/cache/jetty/data -DSTART=/etc/jetty/start.config -Djetty.home=/usr/share/jetty -Djetty.logs=/var/log/jetty -Djetty.host= -Djetty.port=8983 org.mortbay.jetty.start.daemon.Bootstrap /etc/jetty/jetty-logging.xml /etc/jetty/jetty.xml /etc/jetty/jetty-shared-webapps.xml In this instance I can only termi
[Desktop-packages] [Bug 1694225] Re: [Thinkpad T450s] Click lock effect on trackpoint left button when touchpad is disabled
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: xserver-xorg-input-synaptics (Ubuntu) Status: New => Confirmed -- 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 1689825] Re: gnome-keyring not unlocked on boot
I uncovered another problematic side effect but I am unsure of the significance; perhaps this will trigger an idea for someone There are three user accounts on my box. Here's a flow: 1) Reboot box 2) Sign in as user 1 3) Examine running processes (as MikeD mentioned in #33) and observe two keyring processes 4) Log out as user 1 5) Log in as user 2 6) Observe that Unity (via upper-right corner power icon thing) shows two checkmarks indicating that both user 1 and user 2 are signed in -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1689825 Title: gnome-keyring not unlocked on boot Status in chromium-browser package in Ubuntu: Invalid Status in gnome-keyring package in Ubuntu: Confirmed Status in libgnome-keyring package in Ubuntu: Confirmed Bug description: 1) Release: 16.04.2 2) gnome-keyring: 3.18.3-0ubuntu2 3) Login. gnome-keyring unlocks "login" features including for google chrome 4) gnome-keyring is not unlocked, chrome takes 2 minutes to open and with no secure password features(sync) functioning. For the past couple days, chrome on Ubuntu 16.04 takes a REALLY long time (maybe 2 minutes) to start. Once chrome is started, I am not able to sync and any secure password features are broken. I found out this is due to gnome-keyring not being unlocked at login. There's also no way to unlock the "login" portion of the keyring from the running daemon by default. I have to kill the gnome-keyring process and start without "--login" as a parameter. Then the "login" section shows up which I'm able to unlock. From there chrome starts up instantly but asks the following: Enter password to unlock your login keyring The login keyring did not get unlocked when you logged into your computer After that, all of it's sync and secure features are functional. Starting google-chrome-stable from a command line at boot without running the above workaround shows the following error messages: Gkr-Message: secret service operation failed: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. Gkr-Message: secret service operation failed: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. [4364:4393:0510/100407.740292:ERROR:token_service_table.cc(130)] Failed to decrypt token for service AccountId-108842767310111573264 [4364:4445:0510/100407.740292:ERROR:gcm_store_impl.cc(929)] Failed to restore security token. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gnome-keyring 3.18.3-0ubuntu2 ProcVersionSignature: Ubuntu 4.8.0-52.55~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-52-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: GNOME-Flashback:Unity Date: Wed May 10 09:43:37 2017 SourcePackage: gnome-keyring UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1689825/+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 1610944] Re: GNOME Online Accounts breaks if you log out (until you reboot)
** Also affects: gnome-session (Ubuntu) Importance: Undecided Status: New ** Changed in: gnome-session (Ubuntu) Importance: Undecided => High ** Changed in: gnome-session (Ubuntu) Status: New => Triaged ** Changed in: gnome-session (Ubuntu) Status: Triaged => Fix Committed ** Also affects: gnome-session (Ubuntu Zesty) Importance: Undecided Status: New ** Also affects: gnome-online-accounts (Ubuntu Zesty) Importance: Undecided Status: New ** Also affects: gnome-session (Ubuntu Yakkety) Importance: Undecided Status: New ** Also affects: gnome-online-accounts (Ubuntu Yakkety) Importance: Undecided Status: New ** Changed in: gnome-session (Ubuntu Yakkety) Importance: Undecided => High ** Changed in: gnome-session (Ubuntu Yakkety) Status: New => Triaged ** Changed in: gnome-session (Ubuntu Zesty) Importance: Undecided => High ** Changed in: gnome-session (Ubuntu Zesty) Status: New => Triaged ** Changed in: gnome-online-accounts (Ubuntu Yakkety) Importance: Undecided => High ** Changed in: gnome-online-accounts (Ubuntu Yakkety) Status: New => Triaged ** Changed in: gnome-online-accounts (Ubuntu Zesty) Importance: Undecided => High ** Changed in: gnome-online-accounts (Ubuntu Zesty) Status: New => Triaged -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1610944 Title: GNOME Online Accounts breaks if you log out (until you reboot) Status in gnome-online-accounts: Confirmed Status in Ubuntu GNOME: Triaged Status in gnome-online-accounts package in Ubuntu: Triaged Status in gnome-session package in Ubuntu: Fix Committed Status in gnome-online-accounts source package in Yakkety: Triaged Status in gnome-session source package in Yakkety: Triaged Status in gnome-online-accounts source package in Zesty: Triaged Status in gnome-session source package in Zesty: Triaged Bug description: Can't add any online accounts in after opened Online accounts + mark is faded, can't click. After reinstalled gnome-online-accounts still has same problem. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: gnome-online-accounts 3.20.3-1 ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15 Uname: Linux 4.4.0-34-generic x86_64 ApportVersion: 2.20.3-0ubuntu5 Architecture: amd64 CurrentDesktop: Budgie:GNOME Date: Mon Aug 8 15:33:45 2016 SourcePackage: gnome-online-accounts UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-online-accounts/+bug/1610944/+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 1699625] [NEW] full-screen mode in GNOME on 16.04, top menu unresponsive
Public bug reported: I switched my Ubuntu 16.04 (Unity) to GNOME recently, and I found that Remmina doesn't work correctly in this desktop environment. The top menu doesn't work properly, the thin grey line is there but the menu doesn't slide down on mouse-over. I notice mention of 'remmina-gnome' package. Is there something extra required to run Remmina on GNOME? ** Affects: remmina (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to remmina in Ubuntu. https://bugs.launchpad.net/bugs/1699625 Title: full-screen mode in GNOME on 16.04, top menu unresponsive Status in remmina package in Ubuntu: New Bug description: I switched my Ubuntu 16.04 (Unity) to GNOME recently, and I found that Remmina doesn't work correctly in this desktop environment. The top menu doesn't work properly, the thin grey line is there but the menu doesn't slide down on mouse-over. I notice mention of 'remmina-gnome' package. Is there something extra required to run Remmina on GNOME? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/remmina/+bug/1699625/+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 1699626] [NEW] please update to remmina 1.2.0
Public bug reported: Current Ubuntu packages are Remmina 1.1.2, and have frequent crashes as well as failing fullscreen mode under GNOME (tested with an updated 16.04 system). Switching to the Remmina 1.2.0 package from the 'remmina-next' PPA clearly fixes the fullscreen problem and looks like it would be a good move. ** Affects: remmina (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to remmina in Ubuntu. https://bugs.launchpad.net/bugs/1699626 Title: please update to remmina 1.2.0 Status in remmina package in Ubuntu: New Bug description: Current Ubuntu packages are Remmina 1.1.2, and have frequent crashes as well as failing fullscreen mode under GNOME (tested with an updated 16.04 system). Switching to the Remmina 1.2.0 package from the 'remmina-next' PPA clearly fixes the fullscreen problem and looks like it would be a good move. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/remmina/+bug/1699626/+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 1650864] Re: In new version fields are not colored as they have to be
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-mines (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-mines in Ubuntu. https://bugs.launchpad.net/bugs/1650864 Title: In new version fields are not colored as they have to be Status in gnome-mines package in Ubuntu: Confirmed Bug description: This is important gameplay feature, and seems that this was changed by somebody newer played mines, wasn't it so? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-mines/+bug/1650864/+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 1610944] Re: GNOME Online Accounts breaks if you log out (until you reboot)
This bug was fixed in the package gnome-session - 3.24.1-0ubuntu5 --- gnome-session (3.24.1-0ubuntu5) artful; urgency=medium * Backport patches from 3.25.3 to kill D-Bus clients on log out. This works around GNOME Online Accounts not working correctly after logging out (LP: #1610944) - 0001-manager-add-bus-daemon-dbus-api-xml-file.patch - 0002-system-add-api-for-detecting-if-this-is-the-last-ses.patch - 0003-manager-kill-off-bus-clients-at-log-out.patch -- Jeremy Bicha Wed, 21 Jun 2017 18:57:12 -0400 ** Changed in: gnome-session (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1610944 Title: GNOME Online Accounts breaks if you log out (until you reboot) Status in gnome-online-accounts: Confirmed Status in Ubuntu GNOME: Triaged Status in gnome-online-accounts package in Ubuntu: Triaged Status in gnome-session package in Ubuntu: Fix Released Status in gnome-online-accounts source package in Yakkety: Triaged Status in gnome-session source package in Yakkety: Triaged Status in gnome-online-accounts source package in Zesty: Triaged Status in gnome-session source package in Zesty: Triaged Bug description: Can't add any online accounts in after opened Online accounts + mark is faded, can't click. After reinstalled gnome-online-accounts still has same problem. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: gnome-online-accounts 3.20.3-1 ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15 Uname: Linux 4.4.0-34-generic x86_64 ApportVersion: 2.20.3-0ubuntu5 Architecture: amd64 CurrentDesktop: Budgie:GNOME Date: Mon Aug 8 15:33:45 2016 SourcePackage: gnome-online-accounts UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-online-accounts/+bug/1610944/+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 1650864] Re: In new version fields are not colored as they have to be
The Gnome devs in their arrogance and "wisdom" have given gnome-mines the same lack of visibility as everything else in the Gnome Desktop. People are starting to use displays that can show over a billion colours and the Gnome devs are trying to make everything entirely grey-and- slightly-darker-grey with no outline. It's awful, and, in this case, makes the application effectively unusable. Correcting the bad decisions of the Gnome team, and making a distribution that was actually fit to be used by human beings, used to be what Ubuntu was all about. I hope they start doing that again. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-mines in Ubuntu. https://bugs.launchpad.net/bugs/1650864 Title: In new version fields are not colored as they have to be Status in gnome-mines package in Ubuntu: Confirmed Bug description: This is important gameplay feature, and seems that this was changed by somebody newer played mines, wasn't it so? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-mines/+bug/1650864/+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 1650864] Re: In new version fields are not colored as they have to be
You can get some washed-out colours, but not the previous gameplay behaviour, by using dconf-editor to set org.gnome.mines.theme to "classic". The Gnome devs even show the old version on their project page. The new version is just terrible. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-mines in Ubuntu. https://bugs.launchpad.net/bugs/1650864 Title: In new version fields are not colored as they have to be Status in gnome-mines package in Ubuntu: Confirmed Bug description: This is important gameplay feature, and seems that this was changed by somebody newer played mines, wasn't it so? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-mines/+bug/1650864/+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 1624317] Re: systemd-resolved breaks VPN with split-horizon DNS
I have successfully backported Thomas Haller's excellent upstream solution as detailed in https://bugzilla.gnome.org/show_bug.cgi?id=783569 This took some time as things have changed quite a bit upstream, but the patch works on the current zesty 17.04 1.4.4-1ubuntu3.1 network-manager! This is a much better fix than the stopgap SetLinkDomains "." bus call based on link type I included in the previous patch. It should be reviewed for current application/submission to the package maintainers as it is basically a direct backport of Haller's fix merged upstream. NOTE: You MUST set the ipv4.dns-priority to a negative number for the network-manager to unseat DNS configurations for other non-VPN interfaces. This patch allows for correct behavior with negative ipv4 .dns-priority: "Negative values have the special effect of excluding other configurations with a greater priority value; so in presence of at least a negative priority, only DNS servers from connections with the lowest priority value will be used." Usage of a negative dns-priority disables DNS configuration for all other interfaces, ensuring there are no DNS leaks over a VPN connection using systemd-resolved. Before Haller's bugfix, this feature did not work with systemd-resolved. To set the ipv4.dns-priority, open the VPN connection profile you have configured through NM like so: sudo nano /etc/NetworkManager/system-connections/ and adding the line (value of -42 recommended by Haller) "dns-priority=-42" so that the file contains something like: [ipv4] dns-priority=-42 dns-search= method=auto Alternatively, use the command sudo nmcli connection modify "" ipv4.dns-priority -42 And you should see that the config file for that connection contains the same line as shown above. After doing so and patching/installing the patched network manager, you should not experience DNS leaks. When I am connected to PIA's servers through network-manager-openvpn using the patched network manager and a negative ipv4.dns-priority set for my VPN connection, the output of systemd-resolved looks like this (notice that the Verizon ISP DNS server was 'unseated' and is absent for the primary wireless link wlo1): Global DNSSEC NTA: 10.in-addr.arpa ...(long list of NTAs omitted)... test Link 4 (tun0) Current Scopes: DNS LLMNR setting: yes MulticastDNS setting: no DNSSEC setting: no DNSSEC supported: no DNS Servers: 209.222.18.222 209.222.18.218 Link 2 (wlo1) Current Scopes: LLMNR/IPv4 LLMNR/IPv6 LLMNR setting: yes MulticastDNS setting: no DNSSEC setting: no DNSSEC supported: no If anyone is curious about support for the routing-only domain in NM, see the following bug https://bugzilla.gnome.org/show_bug.cgi?id=746422 which is about adding support for routing-only domains for systemd- resolved (still work in progress). ** Bug watch added: GNOME Bug Tracker #746422 https://bugzilla.gnome.org/show_bug.cgi?id=746422 ** Patch added: "systemd-resolved-dns-priority-fix.patch" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1624317/+attachment/4900587/+files/systemd-resolved-dns-priority-fix.patch -- 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/1624317 Title: systemd-resolved breaks VPN with split-horizon DNS Status in systemd: New Status in network-manager package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Status in network-manager source package in Artful: Confirmed Status in systemd source package in Artful: Confirmed Bug description: I use a VPN configured with network-manager-openconnect-gnome in which a split-horizon DNS setup assigns different addresses to some names inside the remote network than the addresses seen for those names from outside the remote network. However, systemd-resolved often decides to ignore the VPN’s DNS servers and use the local network’s DNS servers to resolve names (whether in the remote domain or not), breaking the split-horizon DNS. This related bug, reported by Lennart Poettering himself, was closed with the current Fedora release at the time reaching EOL: https://bugzilla.redhat.com/show_bug.cgi?id=1151544 To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1624317/+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 1689825] Re: gnome-keyring not unlocked on boot
Maybe a clearer capture of something amiss... logging in and out and in repeatedly causes the keyring daemon process to be started again and again (as lightdm and as the user). Please see attached. ** Attachment added: "log_in_and_out.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1689825/+attachment/4900608/+files/log_in_and_out.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1689825 Title: gnome-keyring not unlocked on boot Status in chromium-browser package in Ubuntu: Invalid Status in gnome-keyring package in Ubuntu: Confirmed Status in libgnome-keyring package in Ubuntu: Confirmed Bug description: 1) Release: 16.04.2 2) gnome-keyring: 3.18.3-0ubuntu2 3) Login. gnome-keyring unlocks "login" features including for google chrome 4) gnome-keyring is not unlocked, chrome takes 2 minutes to open and with no secure password features(sync) functioning. For the past couple days, chrome on Ubuntu 16.04 takes a REALLY long time (maybe 2 minutes) to start. Once chrome is started, I am not able to sync and any secure password features are broken. I found out this is due to gnome-keyring not being unlocked at login. There's also no way to unlock the "login" portion of the keyring from the running daemon by default. I have to kill the gnome-keyring process and start without "--login" as a parameter. Then the "login" section shows up which I'm able to unlock. From there chrome starts up instantly but asks the following: Enter password to unlock your login keyring The login keyring did not get unlocked when you logged into your computer After that, all of it's sync and secure features are functional. Starting google-chrome-stable from a command line at boot without running the above workaround shows the following error messages: Gkr-Message: secret service operation failed: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. Gkr-Message: secret service operation failed: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. [4364:4393:0510/100407.740292:ERROR:token_service_table.cc(130)] Failed to decrypt token for service AccountId-108842767310111573264 [4364:4445:0510/100407.740292:ERROR:gcm_store_impl.cc(929)] Failed to restore security token. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gnome-keyring 3.18.3-0ubuntu2 ProcVersionSignature: Ubuntu 4.8.0-52.55~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-52-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: GNOME-Flashback:Unity Date: Wed May 10 09:43:37 2017 SourcePackage: gnome-keyring UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1689825/+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 1624317] Re: systemd-resolved breaks VPN with split-horizon DNS
After setting the ipv4.dns-priority of the VPN connection to a negative number and patching the source or installing the conveniently packaged .deb below, you should not experience DNS leaks over NM-VPN. (Output from extended test at https://dnsleaktest.com ) Test complete Query round Progress... Servers found 1 .. 1 2 .. 1 3 .. 1 4 .. 1 5 .. 1 6 .. 1 IP HostnameISP Country 173.239.226.69 ip-69-226-239-173.east.us.northamericancoax.com LogicWeb Inc United States To install the .deb package, simply use: cd ~/Downloads && sudo dpkg -i network-manager_1.4.4-1ubuntu4_amd64.deb NOTE: make sure apt does not replace the package with: sudo apt-mark hold network-manager Make sure to stop all network services and restart the network manager using: sudo service network-manager stop sudo service networking restart sudo service network-manager start To build the source and apply the patch yourself, use the following steps: sudo apt-get build-dep network-manager cd ~/Downloads && mkdir nm-patch && cd nm-patch apt-get source network-manager cd network-manager-1.4.4 cp ~/Downloads/systemd-resolved-dns-priority-fix.patch . patch -p1 < systemd-resolved-dns-priority-fix.patch rm systemd-resolved-dns-priority-fix.patch dpkg-buildpackage -us -uc -b (wait a while, it will take some time to compile) Then install the generated network-manager_1.4.4-1ubuntu .deb package using: cd ../ && sudo dpkg -i ** Attachment added: "network-manager_1.4.4-1ubuntu4_amd64.deb" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1624317/+attachment/4900613/+files/network-manager_1.4.4-1ubuntu4_amd64.deb -- 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/1624317 Title: systemd-resolved breaks VPN with split-horizon DNS Status in systemd: New Status in network-manager package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Status in network-manager source package in Artful: Confirmed Status in systemd source package in Artful: Confirmed Bug description: I use a VPN configured with network-manager-openconnect-gnome in which a split-horizon DNS setup assigns different addresses to some names inside the remote network than the addresses seen for those names from outside the remote network. However, systemd-resolved often decides to ignore the VPN’s DNS servers and use the local network’s DNS servers to resolve names (whether in the remote domain or not), breaking the split-horizon DNS. This related bug, reported by Lennart Poettering himself, was closed with the current Fedora release at the time reaching EOL: https://bugzilla.redhat.com/show_bug.cgi?id=1151544 To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1624317/+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
I have the same problem on a ThinkPad Yoga 14 20FY. I can reproduce it with the touchpad disabled as described in this report. However, I find it much easier to reproduce (nearly 100% of the time) with the touchpad enabled, as follows: 1. With my left finger, hold down the trackpoint’s left button. 2. With my right finger, move the pointer with the trackpad. 3. Release my right finger from the trackpad. 4. Release my left finger from the button. The button has become “stuck” down! 5. Put a finger back on the trackpad. Now the earlier button release gets recognized. evtest on the trackpoint (ETPS/2 Elantech TrackPoint) shows that the trackpoint knows the button is pressed at step 1 and released at step 4, but evtest on the touchpad (ETPS/2 Elantech Touchpad) shows that the touchpad thinks another copy of the button has been pressed at step 1 and not released until step 5. The problem is still present in kernel 4.12-rc6 from the mainline archive. (I haven’t been able to figure out if enabling the new drivers in 4.12 is supposed to require manual configuration, but simply booting into the new kernel didn’t fix it.) -- 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/xse
[Desktop-packages] [Bug 1582213] Re: [xenial] Bluetooth device doesn't play any sound in A2DP mode unless set to HSP/HFP first
Yes, it's exactly the same in code. Only the changelog text was modified. ** 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/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 t
[Desktop-packages] [Bug 1545248] Re: [xrandr]: gnome-settings-daemon 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 gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1545248 Title: [xrandr]: gnome-settings-daemon crashed with SIGSEGV Status in gnome-settings-daemon package in Ubuntu: New Bug description: (Using Gnome shell) When I hot-plug my hdmi external monitor through mini-DP dongle, my screens are messed up. I can obtain the following config : 2nd monitor and laptop screen cloned. But the other setups fail : 2nd monitor only, extended desktop. When reaching these modes, the laptop screen begins to flicker and if I don't quickly press the screens mode- changing key, the X server (?) ends up to a crash (return to GDM). ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: gnome-settings-daemon 3.18.2-0ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-5.20-generic 4.4.1 Uname: Linux 4.4.0-5-generic x86_64 ApportVersion: 2.19.4-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME Date: Sat Feb 13 09:45:01 2016 ExecutablePath: /usr/lib/gnome-settings-daemon/gnome-settings-daemon InstallationDate: Installed on 2014-03-05 (709 days ago) InstallationMedia: Ubuntu-GNOME 14.04 "Trusty Tahr" - Alpha amd64 (20140226) ProcCmdline: /usr/lib/gnome-settings-daemon/gnome-settings-daemon SegvAnalysis: Segfault happened at: 0x7fc4fbba248d:mov(%rax),%r12 PC (0x7fc4fbba248d) ok source "(%rax)" (0x) not located in a known VMA region (needed readable region)! destination "%r12" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-settings-daemon StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libgnome-desktop-3.so.12 ?? () from /usr/lib/x86_64-linux-gnu/libgnome-desktop-3.so.12 ?? () from /usr/lib/x86_64-linux-gnu/libgnome-desktop-3.so.12 ?? () from /usr/lib/gnome-settings-daemon-3.0/libxrandr.so ?? () from /usr/lib/gnome-settings-daemon-3.0/libxrandr.so Title: [xrandr]: gnome-settings-daemon crashed with SIGSEGV UpgradeStatus: Upgraded to xenial on 2015-11-02 (102 days ago) UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1545248/+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)
In my logs, I see the message: "...aborting authentication ...by local choice (Reason: 3=DEAUTH_LEAVING)" (I've listed below the relevant portion of the log file, since the logs above do not include this particular error). The solution posted in comment #1 (https://bugs.launchpad.net/ubuntu/+source/network- manager/+bug/1681513/comments/1) worked for me... $ sudo nano /etc/NetworkManager/NetworkManager.conf # Append... - - - - - - - - - - - - - - - - - - - - [Device] wifi.scan-rand-mac-address=no - - - - - - - - - - - - - - - - - - - - $ sudo service network-manager restart I did not need to install dnsmasq-base, as suggested in comment #24 (https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1681513/comments/24). What is the purpose of installing this? - - - - - - - - - - - - - - - - - - - - SYSTEM INFO - - - - - - - - - - - - - - - - - - - - Linux RS001 4.10.0-22-generic #24-Ubuntu SMP Mon May 22 17:43:20 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 17.04 Release:17.04 Codename: zesty - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - LOG - - - - - - - - - - - - - - - - - - - - Jun 19 19:20:42 MY_COMPUTER NetworkManager[724]: [1497914442.1301] device (wlx00227540404a): supplicant interface state: disconnected -> scanning Jun 19 19:20:43 MY_COMPUTER wpa_supplicant[855]: wlx00227540404a: SME: Trying to authenticate with b4:75:0e:69:96:af (SSID='MY_WIFI' freq=2462 MHz) Jun 19 19:20:43 MY_COMPUTER kernel: [ 3001.130115] wlx00227540404a: authenticate with b4:75:0e:69:96:af Jun 19 19:20:43 MY_COMPUTER kernel: [ 3001.209885] wlx00227540404a: send auth to b4:75:0e:69:96:af (try 1/3) Jun 19 19:20:43 MY_COMPUTER NetworkManager[724]: [1497914443.7071] device (wlx00227540404a): supplicant interface state: scanning -> authenticating Jun 19 19:20:43 MY_COMPUTER kernel: [ 3001.231002] wlx00227540404a: authenticated Jun 19 19:20:45 MY_COMPUTER kernel: [ 3003.003601] wlx00227540404a: aborting authentication with b4:75:0e:69:96:af by local choice (Reason: 3=DEAUTH_LEAVING) Jun 19 19:20:45 MY_COMPUTER NetworkManager[724]: [1497914445.4980] device (wlx00227540404a): Activation: (wifi) association took too long, failing activation Jun 19 19:20:45 MY_COMPUTER NetworkManager[724]: [1497914445.4980] device (wlx00227540404a): state change: config -> failed (reason 'ssid-not-found') [50 120 53] Jun 19 19:20:45 MY_COMPUTER NetworkManager[724]: [1497914445.4984] manager: NetworkManager state is now DISCONNECTED Jun 19 19:20:45 MY_COMPUTER NetworkManager[724]: [1497914445.5053] device (wlx00227540404a): Activation: failed for connection 'MY_WIFI 1' Jun 19 19:20:45 MY_COMPUTER NetworkManager[724]: [1497914445.5111] device (wlx00227540404a): state change: failed -> disconnected (reason 'none') [120 30 0] Jun 19 19:20:45 MY_COMPUTER wpa_supplicant[855]: wlx00227540404a: CTRL-EVENT-DISCONNECTED bssid=b4:75:0e:69:96:af reason=3 locally_generated=1 Jun 19 19:20:45 MY_COMPUTER kernel: [ 3003.063699] IPv6: ADDRCONF(NETDEV_UP): wlx00227540404a: link is not ready Jun 19 19:20:45 MY_COMPUTER NetworkManager[724]: [1497914445.9519] device (wlx00227540404a): set-hw-addr: set MAC address to XX:XX:XX:XX:XX:XX (scanning) Jun 19 19:20:46 MY_COMPUTER kernel: [ 3003.775904] IPv6: ADDRCONF(NETDEV_UP): wlx00227540404a: link is not ready Jun 19 19:20:46 MY_COMPUTER NetworkManager[724]: [1497914446.2947] sup-iface[0x558e6b4676e0,wlx00227540404a]: connection disconnected (reason -3) Jun 19 19:20:46 MY_COMPUTER NetworkManager[724]: [1497914446.2958] device (wlx00227540404a): supplicant interface state: authenticating -> disconnected - - - - - - - - - - - - - - - - - - - - -- 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
[Desktop-packages] [Bug 1681513] Re: Ubuntu 17.04/17.10: New feature in NetworkManager stops several WiFi adapters from working (MAC Address Randomization issue)
I forgot to add, my wi-fi adapter info is: $ lsusb | grep Wireless Bus 001 Device 002: ID 050d:825b Belkin Components F5D8055 N+ Wireless Adapter v2000 [Ralink RT3072] And I believe it is using the following driver/module: $ lsmod rt2x00usb 20480 1 rt2800usb Located at... /lib/modules/4.10.0-22-generic/kernel/drivers/net/wireless/ralink/rt2x00/rt2800usb.ko -- 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 1672619] [NEW] "disable touchpad while typing" doesn't work on xps 13 and some other laptop
You have been subscribed to a public bug: It's reported that there are lots of false action of touch pad as using keyboard on xps 13 with the factory image. The factory image is based on xenial. One propose that install xserver-xorg-input-libinput with modification 90-libinput.conf in /usr/share/X11/xorg.conf.d from ... Section "InputClass" Identifier "libinput touchpad catchall" MatchIsTouchpad "on" MatchDevicePath "/dev/input/event*" Driver "libinput" EndSection ... to ... Section "InputClass" Identifier "libinput touchpad catchall" MatchIsTouchpad "on" MatchDevicePath "/dev/input/event*" Driver "libinput" Option "Tapping" "on" Option "PalmDetection" "on" EndSection ... helps a lot. ** Affects: oem-priority Importance: Critical Status: Triaged ** Affects: xserver-xorg-input-synaptics (Ubuntu) Importance: Undecided Status: New ** Tags: 17.10 -- "disable touchpad while typing" doesn't work on xps 13 and some other laptop https://bugs.launchpad.net/bugs/1672619 You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-synaptics in Ubuntu. -- 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 1699647] Re: package account-plugin-flickr 0.12+16.04.20160126-0ubuntu1 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 2
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to account-plugins in Ubuntu. https://bugs.launchpad.net/bugs/1699647 Title: package account-plugin-flickr 0.12+16.04.20160126-0ubuntu1 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 2 Status in account-plugins package in Ubuntu: New Bug description: i was making updates for packages on virtualmin and i faced and the updating failled so i tried it from terminal with apt-get update but also the process failed i tried some solutions from ask ubuntu forum like apt-get clean , dpkg --configure -a,ps -aux | grep 'apt-get',sudo kill -9 process id,apt-get -f install but all solutions didn't work ProblemType: Package DistroRelease: Ubuntu 16.04 Package: account-plugin-flickr 0.12+16.04.20160126-0ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-54.57~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-54-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 Date: Thu Jun 22 06:51:51 2017 DuplicateSignature: package:account-plugin-flickr:0.12+16.04.20160126-0ubuntu1 Removing g++ (4:5.3.1-1ubuntu1) ... dpkg (subprocess): unable to execute installed pre-removal script (/var/lib/dpkg/info/g++.prerm): Permission denied dpkg: error processing package g++ (--purge): subprocess installed pre-removal script returned error exit status 2 ErrorMessage: subprocess installed pre-removal script returned error exit status 2 InstallationDate: Installed on 2017-06-18 (3 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: account-plugins Title: package account-plugin-flickr 0.12+16.04.20160126-0ubuntu1 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/account-plugins/+bug/1699647/+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 1699647] [NEW] package account-plugin-flickr 0.12+16.04.20160126-0ubuntu1 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 2
Public bug reported: i was making updates for packages on virtualmin and i faced and the updating failled so i tried it from terminal with apt-get update but also the process failed i tried some solutions from ask ubuntu forum like apt-get clean , dpkg --configure -a,ps -aux | grep 'apt-get',sudo kill -9 process id,apt-get -f install but all solutions didn't work ProblemType: Package DistroRelease: Ubuntu 16.04 Package: account-plugin-flickr 0.12+16.04.20160126-0ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-54.57~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-54-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 Date: Thu Jun 22 06:51:51 2017 DuplicateSignature: package:account-plugin-flickr:0.12+16.04.20160126-0ubuntu1 Removing g++ (4:5.3.1-1ubuntu1) ... dpkg (subprocess): unable to execute installed pre-removal script (/var/lib/dpkg/info/g++.prerm): Permission denied dpkg: error processing package g++ (--purge): subprocess installed pre-removal script returned error exit status 2 ErrorMessage: subprocess installed pre-removal script returned error exit status 2 InstallationDate: Installed on 2017-06-18 (3 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: account-plugins Title: package account-plugin-flickr 0.12+16.04.20160126-0ubuntu1 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 2 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: account-plugins (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 account-plugins in Ubuntu. https://bugs.launchpad.net/bugs/1699647 Title: package account-plugin-flickr 0.12+16.04.20160126-0ubuntu1 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 2 Status in account-plugins package in Ubuntu: New Bug description: i was making updates for packages on virtualmin and i faced and the updating failled so i tried it from terminal with apt-get update but also the process failed i tried some solutions from ask ubuntu forum like apt-get clean , dpkg --configure -a,ps -aux | grep 'apt-get',sudo kill -9 process id,apt-get -f install but all solutions didn't work ProblemType: Package DistroRelease: Ubuntu 16.04 Package: account-plugin-flickr 0.12+16.04.20160126-0ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-54.57~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-54-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 Date: Thu Jun 22 06:51:51 2017 DuplicateSignature: package:account-plugin-flickr:0.12+16.04.20160126-0ubuntu1 Removing g++ (4:5.3.1-1ubuntu1) ... dpkg (subprocess): unable to execute installed pre-removal script (/var/lib/dpkg/info/g++.prerm): Permission denied dpkg: error processing package g++ (--purge): subprocess installed pre-removal script returned error exit status 2 ErrorMessage: subprocess installed pre-removal script returned error exit status 2 InstallationDate: Installed on 2017-06-18 (3 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: account-plugins Title: package account-plugin-flickr 0.12+16.04.20160126-0ubuntu1 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/account-plugins/+bug/1699647/+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 1672619] Re: "disable touchpad while typing" doesn't work on xps 13 and some other laptop
** Project changed: xserver-xorg-input-synaptics => xserver-xorg-input- synaptics (Ubuntu) -- 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/1672619 Title: "disable touchpad while typing" doesn't work on xps 13 and some other laptop Status in OEM Priority Project: Triaged Status in xserver-xorg-input-synaptics package in Ubuntu: New Bug description: It's reported that there are lots of false action of touch pad as using keyboard on xps 13 with the factory image. The factory image is based on xenial. One propose that install xserver-xorg-input-libinput with modification 90-libinput.conf in /usr/share/X11/xorg.conf.d from ... Section "InputClass" Identifier "libinput touchpad catchall" MatchIsTouchpad "on" MatchDevicePath "/dev/input/event*" Driver "libinput" EndSection ... to ... Section "InputClass" Identifier "libinput touchpad catchall" MatchIsTouchpad "on" MatchDevicePath "/dev/input/event*" Driver "libinput" Option "Tapping" "on" Option "PalmDetection" "on" EndSection ... helps a lot. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1672619/+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 1672619] Re: "disable touchpad while typing" doesn't work on xps 13 and some other laptop
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: xserver-xorg-input-synaptics (Ubuntu) Status: New => Confirmed -- 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/1672619 Title: "disable touchpad while typing" doesn't work on xps 13 and some other laptop Status in OEM Priority Project: Triaged Status in xserver-xorg-input-synaptics package in Ubuntu: New Bug description: It's reported that there are lots of false action of touch pad as using keyboard on xps 13 with the factory image. The factory image is based on xenial. One propose that install xserver-xorg-input-libinput with modification 90-libinput.conf in /usr/share/X11/xorg.conf.d from ... Section "InputClass" Identifier "libinput touchpad catchall" MatchIsTouchpad "on" MatchDevicePath "/dev/input/event*" Driver "libinput" EndSection ... to ... Section "InputClass" Identifier "libinput touchpad catchall" MatchIsTouchpad "on" MatchDevicePath "/dev/input/event*" Driver "libinput" Option "Tapping" "on" Option "PalmDetection" "on" EndSection ... helps a lot. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1672619/+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 1699652] [NEW] package hplip 3.16.3+repack0-1 failed to install/upgrade: package hplip is not ready for configuration cannot configure (current status 'half-installed')
Public bug reported: this occurs while i run upgrade. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: hplip 3.16.3+repack0-1 ProcVersionSignature: Ubuntu 4.4.0-81.104-generic 4.4.67 Uname: Linux 4.4.0-81-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 CupsErrorLog: Date: Wed Jun 21 18:29:31 2017 DuplicateSignature: package:hplip:3.16.3+repack0-1 Processing triggers for libc-bin (2.23-0ubuntu9) ... dpkg: error processing package hplip (--configure): package hplip is not ready for configuration ErrorMessage: package hplip is not ready for configuration cannot configure (current status 'half-installed') InstallationDate: Installed on 2017-03-17 (96 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added. MachineType: Hewlett-Packard HP 1000 Notebook PC Papersize: letter ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-81-generic.efi.signed root=UUID=be7d26cc-ea3f-4cf5-a643-8abd1b37b276 ro quiet splash vt.handoff=7 RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: hplip Title: package hplip 3.16.3+repack0-1 failed to install/upgrade: package hplip is not ready for configuration cannot configure (current status 'half-installed') UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/16/2014 dmi.bios.vendor: Insyde dmi.bios.version: F.46 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 1854 dmi.board.vendor: Hewlett-Packard dmi.board.version: 64.2A dmi.chassis.asset.tag: 5CG248178R dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.46:bd06/16/2014:svnHewlett-Packard:pnHP1000NotebookPC:pvr06921020571610100:rvnHewlett-Packard:rn1854:rvr64.2A:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: HP 1000 Notebook PC dmi.product.version: 06921020571610100 dmi.sys.vendor: Hewlett-Packard ** Affects: hplip (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 hplip in Ubuntu. https://bugs.launchpad.net/bugs/1699652 Title: package hplip 3.16.3+repack0-1 failed to install/upgrade: package hplip is not ready for configuration cannot configure (current status 'half-installed') Status in hplip package in Ubuntu: New Bug description: this occurs while i run upgrade. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: hplip 3.16.3+repack0-1 ProcVersionSignature: Ubuntu 4.4.0-81.104-generic 4.4.67 Uname: Linux 4.4.0-81-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 CupsErrorLog: Date: Wed Jun 21 18:29:31 2017 DuplicateSignature: package:hplip:3.16.3+repack0-1 Processing triggers for libc-bin (2.23-0ubuntu9) ... dpkg: error processing package hplip (--configure): package hplip is not ready for configuration ErrorMessage: package hplip is not ready for configuration cannot configure (current status 'half-installed') InstallationDate: Installed on 2017-03-17 (96 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added. MachineType: Hewlett-Packard HP 1000 Notebook PC Papersize: letter ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-81-generic.efi.signed root=UUID=be7d26cc-ea3f-4cf5-a643-8abd1b37b276 ro quiet splash vt.handoff=7 RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: hplip Title: package hplip 3.16.3+repack0-1 failed to install/upgrade: package hplip is not ready for configuration cannot configure (current status 'half-installed') UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/16/2014 dmi.bios.vendor: Insyde dmi.bios.version: F.46 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 1854 dmi.board.vendor: Hewlett-Packard dmi.board.version: 64.2A dmi.chassis.asset.tag: 5CG248178R dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.46:bd06/16/2014:svnHewlett-Packard:pnHP1000NotebookPC:pvr06921020571610100:rvnHewlett-Packard:rn1854:rvr64.2A:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: HP 1000 Notebook PC dmi.product.version: 06921020571610100 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/1699652/+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 1699652] Re: package hplip 3.16.3+repack0-1 failed to install/upgrade: package hplip is not ready for configuration cannot configure (current status 'half-installed')
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/1699652 Title: package hplip 3.16.3+repack0-1 failed to install/upgrade: package hplip is not ready for configuration cannot configure (current status 'half-installed') Status in hplip package in Ubuntu: New Bug description: this occurs while i run upgrade. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: hplip 3.16.3+repack0-1 ProcVersionSignature: Ubuntu 4.4.0-81.104-generic 4.4.67 Uname: Linux 4.4.0-81-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 CupsErrorLog: Date: Wed Jun 21 18:29:31 2017 DuplicateSignature: package:hplip:3.16.3+repack0-1 Processing triggers for libc-bin (2.23-0ubuntu9) ... dpkg: error processing package hplip (--configure): package hplip is not ready for configuration ErrorMessage: package hplip is not ready for configuration cannot configure (current status 'half-installed') InstallationDate: Installed on 2017-03-17 (96 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added. MachineType: Hewlett-Packard HP 1000 Notebook PC Papersize: letter ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-81-generic.efi.signed root=UUID=be7d26cc-ea3f-4cf5-a643-8abd1b37b276 ro quiet splash vt.handoff=7 RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: hplip Title: package hplip 3.16.3+repack0-1 failed to install/upgrade: package hplip is not ready for configuration cannot configure (current status 'half-installed') UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/16/2014 dmi.bios.vendor: Insyde dmi.bios.version: F.46 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 1854 dmi.board.vendor: Hewlett-Packard dmi.board.version: 64.2A dmi.chassis.asset.tag: 5CG248178R dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.46:bd06/16/2014:svnHewlett-Packard:pnHP1000NotebookPC:pvr06921020571610100:rvnHewlett-Packard:rn1854:rvr64.2A:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: HP 1000 Notebook PC dmi.product.version: 06921020571610100 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/1699652/+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
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: totem (Ubuntu) Status: New => Confirmed -- 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: Confirmed 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 1672619] Re: "disable touchpad while typing" doesn't work on xps 13 and some other laptop
** Also affects: xserver-xorg-input-synaptics Importance: Undecided Status: New -- 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/1672619 Title: "disable touchpad while typing" doesn't work on xps 13 and some other laptop Status in OEM Priority Project: Triaged Status in Xserver Xorg Input Synaptics: New Status in xserver-xorg-input-synaptics package in Ubuntu: New Bug description: It's reported that there are lots of false action of touch pad as using keyboard on xps 13 with the factory image. The factory image is based on xenial. One propose that install xserver-xorg-input-libinput with modification 90-libinput.conf in /usr/share/X11/xorg.conf.d from ... Section "InputClass" Identifier "libinput touchpad catchall" MatchIsTouchpad "on" MatchDevicePath "/dev/input/event*" Driver "libinput" EndSection ... to ... Section "InputClass" Identifier "libinput touchpad catchall" MatchIsTouchpad "on" MatchDevicePath "/dev/input/event*" Driver "libinput" Option "Tapping" "on" Option "PalmDetection" "on" EndSection ... helps a lot. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1672619/+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 1699664] [NEW] package libnl-3-200:amd64 3.2.27-1ubuntu0.16.04.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempt
Public bug reported: issue in installing packages. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libnl-3-200:amd64 3.2.27-1ubuntu0.16.04.1 ProcVersionSignature: Ubuntu 4.8.0-54.57~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-54-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 Date: Thu Jun 22 01:06:06 2017 Dependencies: gcc-6-base 6.0.1-0ubuntu1 libc6 2.23-0ubuntu7 libgcc1 1:6.0.1-0ubuntu1 DuplicateSignature: package:libnl-3-200:amd64:3.2.27-1ubuntu0.16.04.1 Processing triggers for fontconfig (2.11.94-0ubuntu1.1) ... dpkg: error processing package libnl-3-200:amd64 (--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-04-08 (74 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: libnl3 Title: package libnl-3-200:amd64 3.2.27-1ubuntu0.16.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) ** Affects: libnl3 (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 libnl3 in Ubuntu. https://bugs.launchpad.net/bugs/1699664 Title: package libnl-3-200:amd64 3.2.27-1ubuntu0.16.04.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in libnl3 package in Ubuntu: New Bug description: issue in installing packages. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libnl-3-200:amd64 3.2.27-1ubuntu0.16.04.1 ProcVersionSignature: Ubuntu 4.8.0-54.57~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-54-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 Date: Thu Jun 22 01:06:06 2017 Dependencies: gcc-6-base 6.0.1-0ubuntu1 libc6 2.23-0ubuntu7 libgcc1 1:6.0.1-0ubuntu1 DuplicateSignature: package:libnl-3-200:amd64:3.2.27-1ubuntu0.16.04.1 Processing triggers for fontconfig (2.11.94-0ubuntu1.1) ... dpkg: error processing package libnl-3-200:amd64 (--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-04-08 (74 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: libnl3 Title: package libnl-3-200:amd64 3.2.27-1ubuntu0.16.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/libnl3/+bug/1699664/+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 1699664] Re: package libnl-3-200:amd64 3.2.27-1ubuntu0.16.04.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attemptin
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libnl3 in Ubuntu. https://bugs.launchpad.net/bugs/1699664 Title: package libnl-3-200:amd64 3.2.27-1ubuntu0.16.04.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in libnl3 package in Ubuntu: New Bug description: issue in installing packages. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libnl-3-200:amd64 3.2.27-1ubuntu0.16.04.1 ProcVersionSignature: Ubuntu 4.8.0-54.57~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-54-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 Date: Thu Jun 22 01:06:06 2017 Dependencies: gcc-6-base 6.0.1-0ubuntu1 libc6 2.23-0ubuntu7 libgcc1 1:6.0.1-0ubuntu1 DuplicateSignature: package:libnl-3-200:amd64:3.2.27-1ubuntu0.16.04.1 Processing triggers for fontconfig (2.11.94-0ubuntu1.1) ... dpkg: error processing package libnl-3-200:amd64 (--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-04-08 (74 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: libnl3 Title: package libnl-3-200:amd64 3.2.27-1ubuntu0.16.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/libnl3/+bug/1699664/+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 1589076] Re: Firefox 47 ignores Global Dark Theme option being enabled
Firefox 55 beta supports two new independent about:config settings, widget.chrome.allow-gtk-dark-theme and widget.content.allow-gtk-dark- theme (https://bugzilla.mozilla.org/show_bug.cgi?id=1158076). The former gets you a dark-themed UI without messing up web page content. Official PPA for Firefox beta, if you don’t want to wait: https://launchpad.net/~mozillateam/+archive/ubuntu/firefox-next ** Bug watch added: Mozilla Bugzilla #1158076 https://bugzilla.mozilla.org/show_bug.cgi?id=1158076 -- 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/1589076 Title: Firefox 47 ignores Global Dark Theme option being enabled Status in Mozilla Firefox: Fix Released Status in Ubuntu GNOME: Confirmed Status in firefox package in Ubuntu: Confirmed Status in firefox package in Arch Linux: New Bug description: I had Firefox 46.0.1 installed previously which worked fine and when having the Global Dark Theme enabled was, well, dark, as I like it. However after upgrading to Firefox 47 I have found that Firefox is all completely white, it looks as it would if the Global Dark Theme option in the gnome-tweak-tool were disabled, which it is not, and it is the only application behaving as such. I am running Ubuntu GNOME 16.04 with GNOME 3.20. I have attached a screenshot of what it looks like (though I have blacked out some private stuff). To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1589076/+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 1586761] Re: White text on white backgrounds on most sites with Firefox with dark GTK theme
Firefox 47 worked around this by disabling the dark theme entirely. Firefox 55 beta supports two new independent about:config settings, widget.chrome.allow-gtk-dark-theme and widget.content.allow-gtk-dark- theme (https://bugzilla.mozilla.org/show_bug.cgi?id=1158076). The former gets you a dark-themed UI without messing up web page content. Official PPA for Firefox beta, if you don’t want to wait: https://launchpad.net/~mozillateam/+archive/ubuntu/firefox-next -- 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/1586761 Title: White text on white backgrounds on most sites with Firefox with dark GTK theme Status in Mozilla Firefox: Fix Released Status in Ubuntu GNOME: Confirmed Status in firefox package in Ubuntu: Confirmed Bug description: When running GNOME 3.18 on Ubuntu GNOME 16.04 I found that on some sites the text was black on black so I could only see it through highlighting, on other sites like YouTube for instance though I found that the text was very light grey on white background, still hard to see, but better than having the same colour for the background and the text. But now after upgrading to GNOME 3.20 I have found that with all themes that on YouTube and many other sites the text is white on white background meaning the only way to see it is to highlight it, but in a search box this is very annoying as you can imagine. I am running Firefox version 46.0.1 and have linked a possibly related upstream bug. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1586761/+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 220263] Re: Bad Firefox integration with dark themes
Firefox 47 worked around this by disabling the dark theme entirely. Firefox 55 beta supports two new independent about:config settings, widget.chrome.allow-gtk-dark-theme and widget.content.allow-gtk-dark- theme (https://bugzilla.mozilla.org/show_bug.cgi?id=1158076). The former gets you a dark-themed UI without messing up web page content. Official PPA for Firefox beta, if you don’t want to wait: https://launchpad.net/~mozillateam/+archive/ubuntu/firefox-next ** Bug watch added: Mozilla Bugzilla #1158076 https://bugzilla.mozilla.org/show_bug.cgi?id=1158076 -- 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/220263 Title: Bad Firefox integration with dark themes Status in Mozilla Firefox: Fix Released Status in XULRunner: Confirmed Status in firefox package in Ubuntu: Triaged Bug description: I'm using Mozilla Firefox 3 Beta 5 on Ubuntu 8.04 with a dark theme. Now I see all the input boxes and buttons filled with grey colour. This happened even with Firefox 2, but I solved that problem with a quick guide under the comment "firefox fix" by Proton at the bottom of this page: http://www.gnome- look.org/content/show.php/Grey+Neu?content=60824 In Firefox 3 I can't correct this problem. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/220263/+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 1699670] [NEW] Gnome screensaver lock always responses "incorrect password" when last active window's language is not the language of the password
Public bug reported: Environment: OS - Ubuntu 16.04.2 LTS, DE - GNOME Shell 3.20.4, gnome-screensaver 3.6.1 Prerequisites: - say, you have 2 language layouts installed - their layouts/character tables are completely different, so there is no chance you can type your password correctly using any language keyboard layout (e.g. you have en/ru, but not en/de etc.) Actual behavior: When the screen is being locked while your active window has the language which is not your password language set, you won't be able to log in back. Log in form shows that the language of the password is set (EN in my case) but it always returns 'Incorrect password' message in response to the correct input. Switching language layout using the keyboard shortcut or GUI doesn't help. 'Switch user' trick allows you to log in back though, but it's a crutch. ** Affects: gnome-screensaver (Ubuntu) Importance: Undecided Status: New ** Tags: another incorrect language lock password ** Description changed: Environment: OS - Ubuntu 16.04.2 LTS, DE - GNOME Shell 3.20.4, gnome-screensaver 3.6.1 Prerequisites: - - say, you have 2 language layouts installed - - their layouts/character tables are completely different, so there is no chance you can type your password correctly using any language keyboard layout (e.g. you have en/ru, but not en/de etc.) + - say, you have 2 language layouts installed + - their layouts/character tables are completely different, so there is no chance you can type your password correctly using any language keyboard layout (e.g. you have en/ru, but not en/de etc.) Actual behavior: - When the screen is being locked while your active window has the language which is not your password language set, you won't be able to log in back. Log in form shows that the language of the password is set (EN in my case) but it always returns 'Incorrect password' message in response to correct password input. Switching language layout using keyboard shortcut or GUI doesn't help. + When the screen is being locked while your active window has the language which is not your password language set, you won't be able to log in back. Log in form shows that the language of the password is set (EN in my case) but it always returns 'Incorrect password' message in response to the correct input. Switching language layout using the keyboard shortcut or GUI doesn't help. 'Switch user' trick allows you to log in back though, but it's a crutch. -- 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/1699670 Title: Gnome screensaver lock always responses "incorrect password" when last active window's language is not the language of the password Status in gnome-screensaver package in Ubuntu: New Bug description: Environment: OS - Ubuntu 16.04.2 LTS, DE - GNOME Shell 3.20.4, gnome-screensaver 3.6.1 Prerequisites: - say, you have 2 language layouts installed - their layouts/character tables are completely different, so there is no chance you can type your password correctly using any language keyboard layout (e.g. you have en/ru, but not en/de etc.) Actual behavior: When the screen is being locked while your active window has the language which is not your password language set, you won't be able to log in back. Log in form shows that the language of the password is set (EN in my case) but it always returns 'Incorrect password' message in response to the correct input. Switching language layout using the keyboard shortcut or GUI doesn't help. 'Switch user' trick allows you to log in back though, but it's a crutch. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1699670/+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 1699675] [NEW] Routine check
Public bug reported: See details sent. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.8.0-56.61~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-56-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 BootLog: [[0;32m OK [0m] Started Raise network interfaces. CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Thu Jun 22 06:55:48 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Mobile 4 Series Chipset Integrated Graphics Controller [103c:30db] Subsystem: Hewlett-Packard Company Mobile 4 Series Chipset Integrated Graphics Controller [103c:30db] InstallationDate: Installed on 2017-06-20 (1 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) MachineType: Hewlett-Packard HP EliteBook 6930p PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-56-generic root=UUID=3e3fb406-1314-469f-b398-ce0337c6d0ee ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/11/2009 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68PCU Ver. F.13 dmi.board.name: 30DB dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 87.28 dmi.chassis.asset.tag: CZC9411L52 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68PCUVer.F.13:bd09/11/2009:svnHewlett-Packard:pnHPEliteBook6930p:pvrF.13:rvnHewlett-Packard:rn30DB:rvrKBCVersion87.28:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP EliteBook 6930p dmi.product.version: F.13 dmi.sys.vendor: Hewlett-Packard 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: Thu Jun 22 01:17:26 2017 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-1ubuntu6.1~16.04.1 xserver.video_driver: modeset ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 ubuntu xenial -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1699675 Title: Routine check Status in xorg package in Ubuntu: New Bug description: See details sent. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.8.0-56.61~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-56-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 BootLog: [[0;32m OK [0m] Started Raise network interfaces. CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Thu Jun 22 06:55:48 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Mobile 4 Series Chipset Integrated Graphics Controller [103c:30db] Subsystem: Hewlett-Packard Company Mobile 4 Series Chipset Integrated Graphics Controller [103c:30db] InstallationDate: Installed on 2017-06-20 (1 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) MachineType: Hewlett-Packard HP EliteBook 6930p PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-56-generic root=UUID=3e3fb406-1314-469f-