[Desktop-packages] [Bug 1218896] Re: [MIR] location-service
Override component to main location-service 3.0.0+16.10.20160811-0ubuntu1 in yakkety: universe/utils -> main libubuntu-location-service-dbg 3.0.0+16.10.20160811-0ubuntu1 in yakkety amd64: universe/debug/optional/100% -> main libubuntu-location-service-dbg 3.0.0+16.10.20160811-0ubuntu1 in yakkety arm64: universe/debug/optional/100% -> main libubuntu-location-service-dbg 3.0.0+16.10.20160811-0ubuntu1 in yakkety armhf: universe/debug/optional/100% -> main libubuntu-location-service-dbg 3.0.0+16.10.20160811-0ubuntu1 in yakkety i386: universe/debug/optional/100% -> main libubuntu-location-service-dbg 3.0.0+16.10.20160811-0ubuntu1 in yakkety powerpc: universe/debug/optional/100% -> main libubuntu-location-service-dbg 3.0.0+16.10.20160811-0ubuntu1 in yakkety ppc64el: universe/debug/optional/100% -> main libubuntu-location-service-dev 3.0.0+16.10.20160811-0ubuntu1 in yakkety amd64: universe/libdevel/optional/100% -> main libubuntu-location-service-dev 3.0.0+16.10.20160811-0ubuntu1 in yakkety arm64: universe/libdevel/optional/100% -> main libubuntu-location-service-dev 3.0.0+16.10.20160811-0ubuntu1 in yakkety armhf: universe/libdevel/optional/100% -> main libubuntu-location-service-dev 3.0.0+16.10.20160811-0ubuntu1 in yakkety i386: universe/libdevel/optional/100% -> main libubuntu-location-service-dev 3.0.0+16.10.20160811-0ubuntu1 in yakkety powerpc: universe/libdevel/optional/100% -> main libubuntu-location-service-dev 3.0.0+16.10.20160811-0ubuntu1 in yakkety ppc64el: universe/libdevel/optional/100% -> main libubuntu-location-service3 3.0.0+16.10.20160811-0ubuntu1 in yakkety amd64: universe/libs/optional/100% -> main libubuntu-location-service3 3.0.0+16.10.20160811-0ubuntu1 in yakkety arm64: universe/libs/optional/100% -> main libubuntu-location-service3 3.0.0+16.10.20160811-0ubuntu1 in yakkety armhf: universe/libs/optional/100% -> main libubuntu-location-service3 3.0.0+16.10.20160811-0ubuntu1 in yakkety i386: universe/libs/optional/100% -> main libubuntu-location-service3 3.0.0+16.10.20160811-0ubuntu1 in yakkety powerpc: universe/libs/optional/100% -> main libubuntu-location-service3 3.0.0+16.10.20160811-0ubuntu1 in yakkety ppc64el: universe/libs/optional/100% -> main ubuntu-location-service-bin 3.0.0+16.10.20160811-0ubuntu1 in yakkety amd64: universe/utils/optional/100% -> main ubuntu-location-service-bin 3.0.0+16.10.20160811-0ubuntu1 in yakkety arm64: universe/utils/optional/100% -> main ubuntu-location-service-bin 3.0.0+16.10.20160811-0ubuntu1 in yakkety armhf: universe/utils/optional/100% -> main ubuntu-location-service-bin 3.0.0+16.10.20160811-0ubuntu1 in yakkety i386: universe/utils/optional/100% -> main ubuntu-location-service-bin 3.0.0+16.10.20160811-0ubuntu1 in yakkety powerpc: universe/utils/optional/100% -> main ubuntu-location-service-bin 3.0.0+16.10.20160811-0ubuntu1 in yakkety ppc64el: universe/utils/optional/100% -> main ubuntu-location-service-doc 3.0.0+16.10.20160811-0ubuntu1 in yakkety amd64: universe/doc/optional/100% -> main ubuntu-location-service-doc 3.0.0+16.10.20160811-0ubuntu1 in yakkety arm64: universe/doc/optional/100% -> main ubuntu-location-service-doc 3.0.0+16.10.20160811-0ubuntu1 in yakkety armhf: universe/doc/optional/100% -> main ubuntu-location-service-doc 3.0.0+16.10.20160811-0ubuntu1 in yakkety i386: universe/doc/optional/100% -> main ubuntu-location-service-doc 3.0.0+16.10.20160811-0ubuntu1 in yakkety powerpc: universe/doc/optional/100% -> main ubuntu-location-service-doc 3.0.0+16.10.20160811-0ubuntu1 in yakkety ppc64el: universe/doc/optional/100% -> main ubuntu-location-service-doc 3.0.0+16.10.20160811-0ubuntu1 in yakkety s390x: universe/doc/optional/100% -> main ubuntu-location-service-examples 3.0.0+16.10.20160811-0ubuntu1 in yakkety amd64: universe/utils/optional/100% -> main ubuntu-location-service-examples 3.0.0+16.10.20160811-0ubuntu1 in yakkety arm64: universe/utils/optional/100% -> main ubuntu-location-service-examples 3.0.0+16.10.20160811-0ubuntu1 in yakkety armhf: universe/utils/optional/100% -> main ubuntu-location-service-examples 3.0.0+16.10.20160811-0ubuntu1 in yakkety i386: universe/utils/optional/100% -> main ubuntu-location-service-examples 3.0.0+16.10.20160811-0ubuntu1 in yakkety powerpc: universe/utils/optional/100% -> main ubuntu-location-service-examples 3.0.0+16.10.20160811-0ubuntu1 in yakkety ppc64el: universe/utils/optional/100% -> main ubuntu-location-service-tests 3.0.0+16.10.20160811-0ubuntu1 in yakkety amd64: universe/utils/optional/100% -> main ubuntu-location-service-tests 3.0.0+16.10.20160811-0ubuntu1 in yakkety arm64: universe/utils/optional/100% -> main ubuntu-location-service-tests 3.0.0+16.10.20160811-0ubuntu1 in yakkety armhf: universe/utils/optional/100% -> main ubuntu-location-service-tests 3.0.0+16.10.20160811-0ubuntu1 in yakkety i386: universe/utils/optional/100% -> main ubuntu-location-service-tests 3.0.0+16.10.20160811-0ubuntu1 in yakkety powerpc: universe/utils/optional/100% -> main ubuntu-l
Re: [Desktop-packages] [Bug 1608820] Re: Cannot use BT speaker - sink is suspended
Could you please test using the version of Pulse for yakkety from my PPA? ppa:themuso/ppa. I've disabled the Ubuntu touch bluetooth patches, and I want to know if this changes anything for you. I'm already working on another bug introduced by those patches in xenial, so its possible that this is something similar. Thanks. -- 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/1608820 Title: Cannot use BT speaker - sink is suspended Status in bluez package in Ubuntu: New Status in pulseaudio package in Ubuntu: Confirmed Bug description: After a fresh boot or resuming from suspend it is possible to connect to a BT speaker but not possible to play anything. Furthermore, if I play a video from youtube, the stream plays fine if the output is the internal speaker, but as soon as I select the BT speaker the stream hangs. It resumes immediately if I switch back to the internal speaker. When I play something over the BT speaker the following lines are logged in the journal: pulseaudio[5340]: [pulseaudio] module-bluez5-device.c: Default profile not connected, selecting off profile bluetoothd[3230]: /org/bluez/hci0/dev_B8_69_C2_3D_56_CE/fd1: fd(24) ready rtkit-daemon[3950]: Supervising 5 threads of 1 processes of 1 users. rtkit-daemon[3950]: Successfully made thread 28532 of process 5340 (n/a) owned by '1000' RT at priority 5. rtkit-daemon[3950]: Supervising 6 threads of 1 processes of 1 users. pulseaudio[5340]: [pulseaudio] bluez5-util.c: Transport TryAcquire() failed for transport /org/bluez/hci0/dev_B8_69_C2_3D_56_CE/fd1 (Operation Not Authorized) kernel: input: B8:69:C2:3D:56:CE as /devices/virtual/input/input26 pulseaudio[5340]: [pulseaudio] sink-input.c: Failed to create sink input: sink is suspended. pulseaudio[5340]: [pulseaudio] sink-input.c: Failed to create sink input: sink is suspended. pulseaudio[5340]: [pulseaudio] sink-input.c: Failed to create sink input: sink is suspended. gnome-session[5383]: ** (zeitgeist-datahub:5874): WARNING **: zeitgeist-datahub.vala:212: Error during inserting events: GDBus.Error:org.gnome.zeitgeist.EngineError.InvalidArgument: Incomplete event: interpretation, manifestation and actor are required wpa_supplicant[3556]: wlan0: WPA: Group rekeying completed with 14:0c:76:71:a1:f4 [GTK=CCMP] pulseaudio[5340]: [pulseaudio] sink-input.c: Failed to create sink input: sink is suspended. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: bluez 5.37-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-33.52-generic 4.4.15 Uname: Linux 4.4.0-33-generic x86_64 ApportVersion: 2.20.3-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Tue Aug 2 09:09:18 2016 InstallationDate: Installed on 2013-09-03 (1063 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902) InterestingModules: rfcomm bnep btusb bluetooth MachineType: ASUSTeK COMPUTER INC. UX32VD ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-33-generic.efi.signed root=UUID=1004226d-a9db-46c7-bd28-eca0806c12f2 ro pcie_aspm=force drm.vblankoffdelay=1 i915.semaphores=1 init=/lib/systemd/systemd-bootchart SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/29/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX32VD.214 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX32VD 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.:bvrUX32VD.214:bd01/29/2013:svnASUSTeKCOMPUTERINC.:pnUX32VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX32VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: UX32VD dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: C4:85:08:A7:45:76 ACL MTU: 310:10 SCO MTU: 64:8 UP RUNNING RX bytes:3492 acl:70 sco:0 events:137 errors:0 TX bytes:4838 acl:64 sco:0 commands:57 errors:0 upstart.bluetooth.override: manual To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1608820/+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 1376300] Re: Scanning works only as root after upgrade to 14.04 LTS, fixable by adding user to group lp
I had the same issue on a fresh install of 16.04, after installing the brother drivers with their automatic script. I ran an strace of simple-scan, as recommended by Kuwanger in the IRC, and found that simple-scan didn't have permission to access some cache files. The problem was that simple-scan's cache files were owned by root, and not accessible by the user. The solution was to run sudo chown -R ~/.cache/simple-scan Of course, replace with the name of your user. I hope that helps! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to simple-scan in Ubuntu. https://bugs.launchpad.net/bugs/1376300 Title: Scanning works only as root after upgrade to 14.04 LTS, fixable by adding user to group lp Status in simple-scan package in Ubuntu: Confirmed Bug description: I have a Brother MFC-7420 printer/scanner combination device. It was working when I had Ubuntu 12.04 LTS installed. I have installed the Brother drivers from the Brother website (brscan2 version 0.2.5-1). When upgrading to Ubuntu 14.04 LTS scanning stopped working as a normal user, neither Simple Scan nor Xsane found the scanner. When launching as root, both were working (e.g. sudo simple-scan). The problem was related to the scanner device (/dev/usb/lp0) belonging to the group lp, with normal users having no access permissions to the device file. When I added my user account to the lp group, it solved the issue. Curiously, sane-find-scanner still cannot find my scanner, but scanimage -L works, as well as simple-scan and xsane. The same problem has been discussed here, concerning Ubuntu 13.10 (I'm running 14.04 LTS 64bit): http://ubuntu.5.x6.nabble.com/xsane-and-simple-scan-only-working-as-root-td5044224.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/1376300/+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 1627641] Re: Backport netplan to xenial
Hello Martin, or anyone else affected, Accepted systemd into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/229-4ubuntu9 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 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: systemd (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 network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1627641 Title: Backport netplan to xenial Status in network-manager package in Ubuntu: Fix Released Status in nplan package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Status in network-manager source package in Xenial: In Progress Status in nplan source package in Xenial: Triaged Status in systemd source package in Xenial: Fix Committed Bug description: For snappy (at first at least) we need to provide netplan in xenial, as for the first snappy GA release we must not use any PPAs any more. netplan's NetworkManager backend depends on two patches to read configuration and connections from /run/NetworkManager/. These will need to be backported for full netplan support; but they are not required for snappy as this will use a snapped NM. However, this will need a temporary hack (https://code.launchpad.net/%7Emorphis/netplan/+git/netplan/+merge/306607) until snaps can actually properly support OS components like NetworkManager. PATCHES: https://git.launchpad.net/~network-manager/network-manager/+git/ubuntu/commit/?h=xenial&id=6dcdb85 https://anonscm.debian.org/cgit/pkg-systemd/systemd.git/commit/?h=ubuntu-xenial&id=4e9c52b0bb REGRESSION POTENTIAL: netplan: The risk for existing installations is practically zero as nplan does not exist in xenial yet and thus will not be pulled in during upgrades. NetworkManager: Nothing in xenial expects/uses /run/NetworkManager/ and as it's an ephemeral tmpfs there is no risk of existing files there. If the patches are broken it could in theory happen that NetworkManager also does not properly read files from /etc/NetworkManager/ any more, so the -proposed package must verify that existing connections still work. systemd: This does change behavior of networkd on restart, but the previous behaviour was arguably buggy. networkd is not being used by default or advertised in Ubuntu 16.04, so this will not affect the vast majority of installations. TEST PLAN: 1. Run "NetworkManager --print-config" and save the output. 2. Install the proposed NetworkManager and confirm that existing connections (from /etc/NetworkManager/system-connections) still work. 3. Run "NetworkManager --print-config" again and verify that the output is the same as in step 1. 4. netplan has a very comprehensive integration test suite run as autopkgtest, which covers NetworkManager (including the /run patches) and network. Confirm that it succeeds. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1627641/+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 1582301] Re: [SRU]fix crash when suspend & resume when using WWAN with PIN set on SIM
This bug was fixed in the package network-manager - 1.2.2-0ubuntu0.16.04.1 --- network-manager (1.2.2-0ubuntu0.16.04.1) xenial; urgency=medium * Rebase to upstream 1.2.2 release, patches: (LP: #1589557) - dnsmasq-vpn-dns-filtering.patch: updated - nm-change-dnsmasq-parameters.diff: updated - 0001-dns-use-DBus-to-make-dnsmasq-nameserver-changes.patch: dropped - lp1574347-re-read-link-type-if-the-name-changed.diff: dropped - libnm-Check-self-still-NMManager-or-not.patch: (LP: #1582301) - libnm-don-t-require-initialized-out_encrypted-argume.patch: (LP: #1575614) -- Aron Xu Sat, 04 Jun 2016 18:27:47 +0800 ** Changed in: network-manager (Ubuntu Xenial) Status: Fix Committed => Fix Released -- 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/1582301 Title: [SRU]fix crash when suspend & resume when using WWAN with PIN set on SIM Status in NetworkManager: Confirmed Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Xenial: Fix Released Bug description: [Impact] There is a rate of crash when doing suspend and resume test when using WWAN with PIN set on SIM. [Test Case] With WWAN enabled, and have PIN set on SIM, doing stress test of suspend & resume, some crash may be observed in network-manager. Also the e.u.c should no longer receive the same crash reports after installing the update. [Regression Potential] The fix is checking a pointer before loop traverse which should be fair safe. -- Original report: The Ubuntu Error Tracker has been receiving reports about a problem regarding network-manager-applet. This problem was most recently seen with version 1.2.0-0ubuntu0.16.04.1, the problem page at https://errors.ubuntu.com/problem/e2c7668fff4fd9f50cb38d0308d51153640d5386 contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1582301/+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 1589557] Update Released
The verification of the Stable Release Update for network-manager has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1589557 Title: [SRU]upstream stable point release 1.2.2 Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Xenial: Fix Released Bug description: [Impact] Upstream releases 1.2.2 as a stable point release to the 1.2.x branch with a handy amount of bug fixes included. Most of the fixes are around the behavior when the status of link has changed. [Test case] After upgrading to 1.2.2, the user be able to use network-manager as usual, nothing that works with 1.2.0 should break with 1.2.2. errors.ubuntu.com should receive less reports than before. [Regression Potential] Code changes in this release are focusing on bug fixes, even there are some patches that aren't trivial they aren't likely to lead to significant regression. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1589557/+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 1606103] Re: modeset driver is missing some modes that the intel driver (and Mir) has
That makes no sense, there is no xf86DefModeSet.c, nor can I find xf86DefaultModes array. You need to build the server with dpkg-buildpackage, not manually with 'make build'. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1606103 Title: modeset driver is missing some modes that the intel driver (and Mir) has Status in linux package in Ubuntu: Invalid Status in xorg-server package in Ubuntu: Confirmed Status in xorg-server package in Debian: New Bug description: My laptop's 4K screen (Dell XPS 15 9550) has these resolutions, according to the intel driver: 3840x2160 60.00 + 3200x1800 60.00 2880x1620 60.00 2560x1440 60.00* 2048x1536 60.00 1920x1440 60.00 1856x1392 60.01 1792x1344 60.01 2048x1152 60.00 1920x1200 59.95 1920x1080 60.0059.93 1600x1200 60.00 1680x1050 59.9559.88 1600x1024 60.17 1400x1050 59.98 1600x900 60.00 1280x1024 60.02 1440x900 59.89 1280x960 60.00 1368x768 60.00 1360x768 59.8059.96 1152x864 60.00 1280x720 60.00 1024x768 60.00 1024x576 60.00 960x540 60.00 800x600 60.3256.25 864x486 60.00 640x480 59.94 720x405 60.00 640x360 60.00 But with the modeset driver, it detects these resolutions: 3840x2160 60.00*+ 2048x1536 60.00 1920x1440 60.00 1856x1392 60.01 1792x1344 60.01 1920x1200 59.95 1920x1080 59.93 1600x1200 60.00 1680x1050 59.9559.88 1600x1024 60.17 1400x1050 59.98 1280x1024 60.02 1440x900 59.89 1280x960 60.00 1360x768 59.8059.96 1152x864 60.00 1024x768 60.0460.00 960x720 60.00 928x696 60.05 896x672 60.01 960x600 60.00 960x540 59.99 800x600 60.0060.3256.25 840x525 60.0159.88 800x512 60.17 700x525 59.98 640x512 60.02 720x450 59.89 640x480 60.0059.94 680x384 59.8059.96 576x432 60.06 512x384 60.00 400x300 60.3256.34 320x240 60.05 It seems to be picking up some extra super-low resolutions (like 320x240) but not the higher 16:9 resolutions. I normally run it at 2560x1440, because the native resolution is too high with an external monitor attached at 1980x1080, but I can't do this with the modeset driver. I'm reporting this as per https://tjaalton.wordpress.com/2016/07/23 /intel-graphics-gen4-and-newer-now-defaults-to-modesetting-driver- on-x/, although note that there are several inaccuracies in that post - there's a typo in ‘cp /usr/share/doc/xserver-xoeg-video- intel/xorg.conf /etc/X11‘, the file doesn't exist in any case if you correct the typo, and I couldn't use ubuntu-bug to report this against xorg-xserver, because ubuntu-bug said the xorg-xserver package doesn't exist. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xorg-server-source (not installed) Uname: Linux 4.6.4-040604-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.2-0ubuntu1 Architecture: amd64 BootLog: 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: Mon Jul 25 11:09:00 2016 DistUpgraded: 2016-07-25 02:38:44,004 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: yakkety DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.4.0-28-generic, x86_64: installed bbswitch, 0.8, 4.6.4-040604-generic, x86_64: installed nvidia-367, 367.35, 4.4.0-28-generic, x86_64: installed nvidia-367, 367.35, 4.6.4-040604-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 530 [1028:06e4] InstallationDate: Installed on 2016-07-04 (20 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) JournalErrors: Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] failed with exit code 1: Hint: You are currently not seeing messages from other users and the system. Users in the 'systemd-journal' group can see all messages. Pass -q to turn off this notice. No journal files were opened due to insufficient permissions. MachineType: Dell Inc. XPS 15 9550 ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.6.
[Desktop-packages] [Bug 1582301] Update Released
The verification of the Stable Release Update for network-manager has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1582301 Title: [SRU]fix crash when suspend & resume when using WWAN with PIN set on SIM Status in NetworkManager: Confirmed Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Xenial: Fix Released Bug description: [Impact] There is a rate of crash when doing suspend and resume test when using WWAN with PIN set on SIM. [Test Case] With WWAN enabled, and have PIN set on SIM, doing stress test of suspend & resume, some crash may be observed in network-manager. Also the e.u.c should no longer receive the same crash reports after installing the update. [Regression Potential] The fix is checking a pointer before loop traverse which should be fair safe. -- Original report: The Ubuntu Error Tracker has been receiving reports about a problem regarding network-manager-applet. This problem was most recently seen with version 1.2.0-0ubuntu0.16.04.1, the problem page at https://errors.ubuntu.com/problem/e2c7668fff4fd9f50cb38d0308d51153640d5386 contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1582301/+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 1589557] Re: [SRU]upstream stable point release 1.2.2
This bug was fixed in the package network-manager - 1.2.2-0ubuntu0.16.04.1 --- network-manager (1.2.2-0ubuntu0.16.04.1) xenial; urgency=medium * Rebase to upstream 1.2.2 release, patches: (LP: #1589557) - dnsmasq-vpn-dns-filtering.patch: updated - nm-change-dnsmasq-parameters.diff: updated - 0001-dns-use-DBus-to-make-dnsmasq-nameserver-changes.patch: dropped - lp1574347-re-read-link-type-if-the-name-changed.diff: dropped - libnm-Check-self-still-NMManager-or-not.patch: (LP: #1582301) - libnm-don-t-require-initialized-out_encrypted-argume.patch: (LP: #1575614) -- Aron Xu Sat, 04 Jun 2016 18:27:47 +0800 ** Changed in: network-manager (Ubuntu Xenial) Status: Fix Committed => Fix Released -- 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/1589557 Title: [SRU]upstream stable point release 1.2.2 Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Xenial: Fix Released Bug description: [Impact] Upstream releases 1.2.2 as a stable point release to the 1.2.x branch with a handy amount of bug fixes included. Most of the fixes are around the behavior when the status of link has changed. [Test case] After upgrading to 1.2.2, the user be able to use network-manager as usual, nothing that works with 1.2.0 should break with 1.2.2. errors.ubuntu.com should receive less reports than before. [Regression Potential] Code changes in this release are focusing on bug fixes, even there are some patches that aren't trivial they aren't likely to lead to significant regression. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1589557/+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 1575614] Re: [SRU]Can't select p12 secret key for TLS auth for 802.1X authentication
This bug was fixed in the package network-manager - 1.2.2-0ubuntu0.16.04.1 --- network-manager (1.2.2-0ubuntu0.16.04.1) xenial; urgency=medium * Rebase to upstream 1.2.2 release, patches: (LP: #1589557) - dnsmasq-vpn-dns-filtering.patch: updated - nm-change-dnsmasq-parameters.diff: updated - 0001-dns-use-DBus-to-make-dnsmasq-nameserver-changes.patch: dropped - lp1574347-re-read-link-type-if-the-name-changed.diff: dropped - libnm-Check-self-still-NMManager-or-not.patch: (LP: #1582301) - libnm-don-t-require-initialized-out_encrypted-argume.patch: (LP: #1575614) -- Aron Xu Sat, 04 Jun 2016 18:27:47 +0800 ** Changed in: network-manager (Ubuntu Xenial) Status: Fix Committed => Fix Released -- 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/1575614 Title: [SRU]Can't select p12 secret key for TLS auth for 802.1X authentication Status in NetworkManager: Fix Released Status in network-manager package in Ubuntu: Fix Released Status in network-manager-applet package in Ubuntu: Fix Released Status in network-manager source package in Xenial: Fix Released Status in network-manager-applet source package in Xenial: Fix Released Bug description: [Impact] Users cannot select TLS certificate when connecting to a network that requires TLS type 802.1X authentication [Test case] STR: 1. Click on Connections icon in status panel 2. Click on Edit connections 3. Select Wired connection 4. Go to 802.1x tab 5. Check the Use 802.1X checkbox 6. Choose TLS 7. Click on Secret key button 8. In file chooser navigate to the folder where key is located and try to select key file - the list is empty For wifi connection: 1. Click on Connections icon in status panel 2. Click on Edit connections 3. Select Wi-Fi connection 4. Go to Wi-Fi Security tab 5. Select WPA & WPA2 Enterprise in the drop-down list 6. Choose TLS 7. Click on (None) next to Private key 8. In file chooser navigate to the folder where key is located and try to select key file - the list is empty [Regression Potential] The fix is quite straight forward and the possibility of causing regression is limited. To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1575614/+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 1627365] Re: Screen frezes, only mouse pointer can move
Jose Barakat, thank you for taking the time to report this and trying to help make Ubuntu better. However, PPA's are not software packages provided by the official Ubuntu repositories. Because of this the Ubuntu project can not support or fix your particular bug. Please report this bug to the provider of the software package. Thanks! If you are interested in learning more about software repositories and Ubuntu, check https://help.ubuntu.com/community/Repositories. ** Changed in: xorg (Ubuntu) Importance: Low => Undecided ** Changed in: xorg (Ubuntu) Status: Incomplete => Invalid -- 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/1627365 Title: Screen frezes, only mouse pointer can move Status in xorg package in Ubuntu: Invalid Bug description: This issue only occurs when I use certain gaming software like Emulation Station, ppsspp and ppsspp-sdl on Fullscreen Mode. As of https://wiki.ubuntu.com/X/Troubleshooting/Freeze says, my symptoms are: - X stops responding to input (sometimes mouse cursor can still move, but clicking has no effect) - The screen displays but does not update. Sometimes there is screen corruption too, sometimes the screen goes black. - Often, X cannot be killed from the console or if it can, it won't restart properly; only a reboot clears the state I can go to TTY with Ctrl+Alt+F1, login and reboot, or go back back to frozen desktop/application with Ctrl+Alt+F7. I would like to reproduce this issue and collect the necessary data over ethernet, but I don't how to do it. - I'm experience this lockup when I go Fullscreen in PPSSPP (Sony PlayStation Portable Emulator), Emulation Station (Frontend for Emulators) and a couple of minutes pass, so I can't go back to Windowed mode. I've tried with VLC fullscreen mode without issues. I'll make a more detailed report of apps later on comments. - I first noticed it aprox. after installing this repos: http://ppa.launchpad.net/canonical-x/vulkan/ubuntu http://ppa.launchpad.net/oibaf/graphics-drivers/ubuntu http://ppa.launchpad.net/graphics-drivers/ppa/ubuntu - I'm using Unity, so I can't be sure if this is happening in other DE's - Like I said before, this happens when switching from fullscreen mode to windowed mode, in some applications. I haven't had problems with streaming video (youtube player, jwplayer, vimeo player, etc...) in fullscreen mode. Thanks! Technical Info. Machine: Lenovo G400s (Laptop) ~$ lsb_release -rd Description: Ubuntu 16.04.1 LTS Release: 16.04 ~$ apt-cache policy xorg xorg: Instalados: 1:7.7+13ubuntu3 Candidato: 1:7.7+13ubuntu3 Tabla de versión: *** 1:7.7+13ubuntu3 500 500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status Phoronix Test Suite v6.4.0 Interactive Benchmarking System Software / Hardware Information Hardware: Processor: Intel Core i3-3110M @ 2.40GHz (4 Cores), Motherboard: LENOVO, Chipset: Intel 3rd Gen Core DRAM, Memory: 6144MB, Disk: 500GB Seagate ST500LT012-9WS14, Graphics: Intel HD 4000 (1000MHz), Audio: Conexant CX20757, Network: Qualcomm Atheros QCA8172 Fast + Qualcomm Atheros AR9485 Wireless Software: OS: Ubuntu 16.04, Kernel: 4.7.2-040702-generic (x86_64), Desktop: Unity 7.4.0, Display Server: X Server 1.18.4, Display Driver: intel 2.99.917, OpenGL: 3.3 Mesa 12.1.0-devel, Compiler: GCC 5.4.0 20160609, File-System: ext4, Screen Resolution: 1366x768 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 Uname: Linux 4.7.2-040702-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 Date: Sat Sep 24 10:11:14 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:3977] InstallationDate: Installed on 2015-07-08 (444 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) MachineType: LENOVO 20244 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.7.2-040702-generic root=UUID=aeda239d-fc39-47e7-a775-53cef3aa6e11 ro quiet splash pciehp.pciehp_force=1 vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/28/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 7BCN36WW(V2
[Desktop-packages] [Bug 1605953] Re: skylake Modesetting Driver on X failure
closing the bug since the original reporter can't debug this anymore if you still have this issue with current yak, make sure you have xdiagnose installed and run 'ubuntu-bug xorg-server' ** Changed in: xorg-server (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1605953 Title: skylake Modesetting Driver on X failure Status in xorg-server package in Ubuntu: Invalid Bug description: with the change away from the intel driver to modeset I get a lot of tearing. This video shows the problem. https://goo.gl/photos/rXNBQ5KR6ZMnhazB9 And the video capture is done in 240fps so its possible to see what is happening more clearly. The test video itself is just a short test video with alternating red/green pictures in 60Hz. What you should see is a somewhat flickering screen but the color should be a consistent orange hue. there should be no pulsing of colors that is more green then back to more red and so on then something is wrong. I have attached the video. if you are uncertain how it should look try to play it directly on a TV. that is with the TV own player not with a computer as that has a lot higher probability of not having any issues with vsync and frame updates. --- .tmp.unity_support_test.0: ApportVersion: 2.20.2-0ubuntu1 Architecture: amd64 BootLog: /dev/sda2: clean, 770076/2416640 files, 3881571/9647872 blocks (K(K 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 DistUpgraded: 2016-04-22 23:31:04,108 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: yakkety DistroRelease: Ubuntu 16.10 DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation HD Graphics 530 [8086:1912] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] HD Graphics 530 [1462:7976] Advanced Micro Devices, Inc. [AMD/ATI] Fiji [Radeon R9 FURY / NANO Series] [1002:7300] (rev c8) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Radeon R9 FURY X [1043:04a0] InstallationDate: Installed on 2015-10-18 (281 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150924) MachineType: MSI MS-7976 Package: xorg-server (not installed) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.7.0-rc7+ root=UUID=75bb5d92-206d-4bb8-a405-150b9b93d6d3 ro quiet splash vt.handoff=7 Tags: yakkety ubuntu regression reproducible compiz-0.9 Uname: Linux 4.7.0-rc7+ x86_64 UpgradeStatus: Upgraded to yakkety on 2016-04-22 (94 days ago) UserGroups: adm cdrom dip libvirt libvirtd lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/22/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.B0 dmi.board.asset.tag: Default string dmi.board.name: Z170A GAMING M7 (MS-7976) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.B0:bd02/22/2016:svnMSI:pnMS-7976:pvr1.0:rvnMSI:rnZ170AGAMINGM7(MS-7976):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.name: MS-7976 dmi.product.version: 1.0 dmi.sys.vendor: MSI version.compiz: compiz 1:0.9.13.0+16.10.20160714.2-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.69-1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.1-3ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.1-3ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1 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+git20160706-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1605953/+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 1627641] Re: Backport netplan to xenial
Hello Martin, or anyone else affected, Accepted network-manager into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/network- manager/1.2.2-0ubuntu0.16.04.2 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 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: network-manager (Ubuntu Xenial) Status: In Progress => Fix Committed -- 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/1627641 Title: Backport netplan to xenial Status in network-manager package in Ubuntu: Fix Released Status in nplan package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Status in network-manager source package in Xenial: Fix Committed Status in nplan source package in Xenial: Triaged Status in systemd source package in Xenial: Fix Committed Bug description: For snappy (at first at least) we need to provide netplan in xenial, as for the first snappy GA release we must not use any PPAs any more. netplan's NetworkManager backend depends on two patches to read configuration and connections from /run/NetworkManager/. These will need to be backported for full netplan support; but they are not required for snappy as this will use a snapped NM. However, this will need a temporary hack (https://code.launchpad.net/%7Emorphis/netplan/+git/netplan/+merge/306607) until snaps can actually properly support OS components like NetworkManager. PATCHES: https://git.launchpad.net/~network-manager/network-manager/+git/ubuntu/commit/?h=xenial&id=6dcdb85 https://anonscm.debian.org/cgit/pkg-systemd/systemd.git/commit/?h=ubuntu-xenial&id=4e9c52b0bb REGRESSION POTENTIAL: netplan: The risk for existing installations is practically zero as nplan does not exist in xenial yet and thus will not be pulled in during upgrades. NetworkManager: Nothing in xenial expects/uses /run/NetworkManager/ and as it's an ephemeral tmpfs there is no risk of existing files there. If the patches are broken it could in theory happen that NetworkManager also does not properly read files from /etc/NetworkManager/ any more, so the -proposed package must verify that existing connections still work. systemd: This does change behavior of networkd on restart, but the previous behaviour was arguably buggy. networkd is not being used by default or advertised in Ubuntu 16.04, so this will not affect the vast majority of installations. TEST PLAN: 1. Run "NetworkManager --print-config" and save the output. 2. Install the proposed NetworkManager and confirm that existing connections (from /etc/NetworkManager/system-connections) still work. 3. Run "NetworkManager --print-config" again and verify that the output is the same as in step 1. 4. netplan has a very comprehensive integration test suite run as autopkgtest, which covers NetworkManager (including the /run patches) and network. Confirm that it succeeds. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1627641/+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 1592721] Re: Don't write search domains to resolv.conf in the case of split DNS
Hello Mathieu, or anyone else affected, Accepted network-manager into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/network- manager/1.2.2-0ubuntu0.16.04.2 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 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: network-manager (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 network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1592721 Title: Don't write search domains to resolv.conf in the case of split DNS Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Xenial: Fix Committed Bug description: [Impact] All VPN users meaning to use split-tunnelling in a situation where leaking DNS data to the internet about what might be behind their VPN is undesirable. [Test case] 1) connect to VPN 2) Use dig to request a name that should be on the VPN 3) Verify (kill -USR1 the dnsmasq binary from NM) that the request has only gone through the VPN nameservers (only its request number should have increased by one) 4) Use dig to request a name off-VPN, such as google.com. 5) Verify (kill -USR1 again) that the request has caused the non-VPN nameserver request number to increase, and that the VPN number has not increased. It is easier to verify this when there is as little traffic as possible on the system, to avoid spurious DNS requests which would make it harder to validate the counters. [Regression potential] This change modifies the way in which DNS nameservers and search domains are passed to dnsmasq, as such, if a VPN is configured in a non-standard way and intended to be used to resolve all network requests (which is typically not the case for split-tunnelling) or if the public network is intended to always resolve all requests while the VPN still provides search domains, one might observe incorrect behavior. Possible failure cases would include failure to resolve names correctly (resulting in NXDOMAIN or REFUSED from dnsmasq) or resolving to the incorrect values (if the wrong nameserver is used). --- Currently, NM will write all search domains to both any DNS-handling plugins running, and also to resolv.conf / resolvconf; in all cases. The issue is that doing so means that in the split-DNS case on VPNs, you might get a negative response from all nameservers, then a new request by glibc with the search tacked on, to nameservers again, which might cause DNS requests for "private" resources (say, on the VPN) to be sent to external, untrusted resolvers, or for DNS queries not meant for VPN nameservers to be sent through the VPN anyway. This is fixable in the case where we have a caching plugin running (such as dnsmasq). dnsmasq will already know about the search domains and use that to limit queries to the right nameservers when a VPN is running. Writing search domains to resolv.conf is unnecessary in this case. We should still write search domains if no caching gets done, as we then need to expect glibc to send requests as it otherwise would. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1592721/+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 1627496] Re: AMD Radeon hardware features or firmware looked over by Linux 3.6.0+ kernel.
Hi all, I must have omitted a few pieces of information in fact : - The description of the bug - Error messages - The text files (logs, ...) I mentioned in my previous post The files are joined as an attachement to this post, and here follow my bug description and error messages extracts. With Linux 4.5.x or below all is good : - Screen resolution of 1600x900 (native screen resolution) - Accelerated 3D graphics on AMD TURKS hardware - Plymouth shows up and animates well both on OS startup and OS shutdown - No scary message in kernel logs (dmesg) With Linux 4.6.x or above all is bad : - Screen resolution of 1152x864 (lower than native) - Software rendered 3D graphics on llvmpipe - Plymouth neither shows up on OS startup nor on OS shutdown - Scary messages in kernel logs (extracts follow) : [5.291603] [drm] Initialized drm 1.1.0 20060810 ... [5.353156] [drm] radeon kernel modesetting enabled. [5.353216] call_modprobe: symbol:kgd2kfd_init 2 [5.359409] CRAT table not found [5.359410] Finished initializing topology ret=0 [5.359425] kfd kfd: Initialized module [5.359614] checking generic (b000 3cc000) vs hw (b000 1000) [5.359615] fb: switching to radeondrmfb from simple [5.359644] Console: switching to colour dummy device 80x25 [5.359926] [drm] initializing kernel modesetting (TURKS 0x1002:0x6840 0x1179:0xFB41 0x00). [5.359936] [drm] register mmio base: 0xC200 [5.359937] [drm] register mmio size: 131072 [5.359957] [ cut here ] [5.359961] WARNING: CPU: 0 PID: 116 at /build/linux-akdJXO/linux-4.8.0/arch/x86/mm/ioremap.c:121 __ioremap_caller+0x1ec/0x370 [5.359962] ioremap on RAM at 0x - 0x0001 [5.359963] Modules linked in: amdkfd radeon(+) r8169 mii i2c_algo_bit ttm drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops ahci(+) libahci drm wmi ehci_pci xhci_pci fjes ehci_hcd video thermal xhci_hcd usbcore usb_common button [5.359978] CPU: 0 PID: 116 Comm: systemd-udevd Not tainted 4.8.0-16-generic #17-Ubuntu [5.359978] Hardware name: TOSHIBA SATELLITE L875-10G/Type2 - Board Product Name1, BIOS 6.50 3/25/2013 [5.359980] 0286 1712e9ce be973f14 8b3f3cebf8c0 [5.359982] be67f93e 8b3f3cebf918 [5.359985] be9cf198 0002 0002 [5.359987] Call Trace: [5.359992] [] ? dump_stack+0x5c/0x78 [5.359995] [] ? __warn+0xbe/0xe0 [5.359997] [] ? pci_map_rom+0x58/0xd0 [5.35] [] ? warn_slowpath_fmt+0x5f/0x80 [5.360040] [] ? igp_read_bios_from_vram+0x57/0xa0 [radeon] [5.360042] [] ? __ioremap_caller+0x1ec/0x370 [5.360044] [] ? pci_map_rom+0x58/0xd0 [5.360075] [] ? radeon_read_bios.isra.2+0x35/0xc0 [radeon] [5.360102] [] ? radeon_get_bios+0x28c/0xfc0 [radeon] [5.360105] [] ? vprintk_emit+0x35a/0x520 [5.360108] [] ? kmem_cache_alloc_trace+0x18d/0x1d0 [5.360145] [] ? evergreen_init+0xf/0x390 [radeon] [5.360173] [] ? radeon_device_init+0x87e/0xcb0 [radeon] [5.360198] [] ? radeon_driver_load_kms+0x95/0x210 [radeon] [5.360217] [] ? drm_dev_register+0x9c/0xc0 [drm] [5.360230] [] ? drm_get_pci_dev+0x88/0x1d0 [drm] [5.360232] [] ? local_pci_probe+0x3f/0x90 [5.360234] [] ? pci_device_probe+0x109/0x160 [5.360237] [] ? driver_probe_device+0x21a/0x420 [5.360240] [] ? __driver_attach+0xda/0xe0 [5.360242] [] ? driver_probe_device+0x420/0x420 [5.360244] [] ? bus_for_each_dev+0x67/0xb0 [5.360246] [] ? bus_add_driver+0x16a/0x260 [5.360248] [] ? 0xc066f000 [5.360249] [] ? driver_register+0x57/0xc0 [5.360251] [] ? 0xc066f000 [5.360253] [] ? do_one_initcall+0x4b/0x190 [5.360255] [] ? kmem_cache_alloc_trace+0x150/0x1d0 [5.360258] [] ? do_init_module+0x5b/0x1ed [5.360261] [] ? load_module+0x1938/0x1ca0 [5.360262] [] ? m_show+0x1b0/0x1b0 [5.360265] [] ? SYSC_finit_module+0xc6/0xf0 [5.360268] [] ? entry_SYSCALL_64_fastpath+0x1e/0xa8 [5.360270] ---[ end trace a3dcc2b343f5d80b ]--- [5.360304] [drm:radeon_get_bios [radeon]] *ERROR* Unable to locate a BIOS ROM [5.360309] radeon :01:00.0: Fatal error during GPU init [5.360312] [drm] radeon: finishing device. [5.360313] [TTM] Memory type 2 has not been initialized [5.361148] scsi host0: ahci [5.367568] radeon: probe of :01:00.0 failed with error -22 I havent got a peanut about what is happenging since Linux 4.6.0 ; any idea ? I have tried to attempt a bissection, but got the timeline messed up, so I will rety in the following days ... Sincerely, Vécu ** Attachment added: "Logs" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1627496/+attachment/4749217/+files/Logs_Attachment.tar.gz -- You received this bug notification because you are a member of Desktop Pac
[Desktop-packages] [Bug 1628014] [NEW] WebExtension fails to install only on ubuntu packaged firefox
Public bug reported: Hi, I have recently developed a WebExtension ( https://addons.mozilla.org /en-US/firefox/addon/surligneur/ ) but the installation from AMO freezes on a **ubuntu packaged firefox**. The download starts but the process freezes on the "Downloading and verifying addon" step (even on a clean profile and/or a clean install). In the browser console I get the following error : A promise chain failed to handle a rejection. Did you forget to '.catch', or did you forget to 'return'? See https://developer.mozilla.org/Mozilla/JavaScript_code_modules/Promise.jsm/Promise Date: Tue Sep 27 2016 11:05:24 GMT+0200 (CEST) Full Message: TypeError: is not iterable Full Stack: AddonInstall.prototype.onStopRequest/<@resource://gre/modules/addons/XPIProvider.jsm:5974:1 Handler.prototype.process@resource://gre/modules/Promise.jsm -> resource://gre/modules/Promise-backend.js:940:21 this.PromiseWalker.walkerLoop@resource://gre/modules/Promise.jsm -> resource://gre/modules/Promise-backend.js:816:7 this.PromiseWalker.scheduleWalkerLoop/<@resource://gre/modules/Promise.jsm -> resource://gre/modules/Promise-backend.js:750:11 Please note that : - I'm using firefox 49 on ubuntu 16.04.1 - Installing the same extension on a Windows system or a Ubuntu system with a firefox directly downloaded from https://www.mozilla.org/en-US/firefox/all/#en-US works correctly. - Load the addon through the about:debugging page works correctly too. Best, Marius ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: firefox 49.0+build4-0ubuntu0.16.04.1 ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19 Uname: Linux 4.4.0-38-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: marius 2137 F pulseaudio /dev/snd/controlC1: marius 2137 F pulseaudio BuildID: 20160920074044 Channel: Unavailable CurrentDesktop: Unity Date: Tue Sep 27 11:55:56 2016 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePlugins: Gnome Shell Integration - /usr/lib/mozilla/plugins/libgnome-shell-browser-plugin.so (gnome-shell) Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so DefaultProfilePrefSources: prefs.js DefaultProfileThemes: extensions.sqlite corrupt or missing EcryptfsInUse: Yes ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-03-30 (180 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323) IpRoute: default via 192.168.1.1 dev wlp4s0 proto static metric 600 169.254.0.0/16 dev wlp4s0 scope link metric 1000 192.168.1.0/24 dev wlp4s0 proto kernel scope link src 192.168.1.6 metric 600 MostRecentCrashID: bp-63a6343e-7c06-4bcb-8343-af7572160218 Profile1Extensions: extensions.sqlite corrupt or missing Profile1IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile1Locales: extensions.sqlite corrupt or missing Profile1Plugins: Gnome Shell Integration - /usr/lib/mozilla/plugins/libgnome-shell-browser-plugin.so (gnome-shell) Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so Profile1PrefSources: prefs.js Profile1Themes: extensions.sqlite corrupt or missing Profiles: Profile0 (Default) - LastVersion=49.0/20160920074044 (In use) Profile1 - LastVersion=49.0/20160920074044 RelatedPackageVersions: gnome-shell 3.18.5-0ubuntu0.1 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no RunningIncompatibleAddons: False SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/29/2010 dmi.bios.vendor: Dell Inc. dmi.bios.version: A14 dmi.board.name: 0Y536R dmi.board.vendor: Dell Inc. dmi.board.version: A14 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A14 dmi.modalias: dmi:bvnDellInc.:bvrA14:bd03/29/2010:svnDellInc.:pnStudioXPS1640:pvrA143:rvnDellInc.:rn0Y536R:rvrA14:cvnDellInc.:ct8:cvrA14: dmi.product.name: Studio XPS 1640 dmi.product.version: A143 dmi.sys.vendor: Dell Inc. ** Affects: firefox (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1628014 Title: WebExtension fails to install only on ubuntu packaged firefox Status in firefox package in Ubuntu: New Bug description: Hi, I have recently developed a WebExtension ( https://addons.mozilla.org /en-US/firefox/addon/surligneur/ ) but the installation from AMO freezes on a **ubuntu packaged firefox**. The download sta
[Desktop-packages] [Bug 1406810] Re: [iMac11,1] Unable to boot
Christopher Penalver, I did test several versions. 12.04 with nomodeset -> stop at the console with an Xorg error (no screen found) 12.04 without nomodeset -> black screen 12.10 with nomodeset -> hang in console mode 12.10 without nomodeset -> black screen 13.04 with nomodeset -> hang in console mode 13.04 without nomodeset -> black screen 11.10 with nomodeset -> black screen 11.10 without nomodeset -> black screen Kernel 4.8.0rc8 with nomodeset -> OK Kernel 4.8.0rc8 without nomodeset -> black screen Please note that grub editing is really sluggish except for 11.10 and 12.04. -- 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/1406810 Title: [iMac11,1] Unable to boot Status in xorg package in Ubuntu: Incomplete Bug description: I'm unable to boot. WORKAROUND: Use kernel parameter: nomodeset The causes a sluggish display and an inability to wake up the screen after going to sleep. --- .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.19 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 DistUpgraded: Fresh install DistroCodename: trusty DistroRelease: Ubuntu 14.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RV770/M98L [Mobility Radeon HD 4850] [1002:944a] (prog-if 00 [VGA controller]) Subsystem: Apple Inc. Device [106b:00b5] InstallationDate: Installed on 2015-01-01 (440 days ago) InstallationMedia: Ubuntu-Server 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.3) MachineType: Apple Inc. iMac11,1 Package: xorg 1:7.7+1ubuntu8.1 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-79-generic root=UUID=f19c8f84-1553-4a36-889a-acfb8a13da9a ro ProcVersionSignature: Ubuntu 3.13.0-79.123-generic 3.13.11-ckt33 Tags: trusty ubuntu compiz-0.9 Uname: Linux 3.13.0-79-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 03/17/10 dmi.bios.vendor: Apple Inc. dmi.bios.version: IM111.88Z.0034.B02.1003171314 dmi.board.name: Mac-F2268DAE dmi.board.vendor: Apple Inc. dmi.chassis.type: 13 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F2268DAE dmi.modalias: dmi:bvnAppleInc.:bvrIM111.88Z.0034.B02.1003171314:bd03/17/10:svnAppleInc.:pniMac11,1:pvr1.0:rvnAppleInc.:rnMac-F2268DAE:rvr:cvnAppleInc.:ct13:cvrMac-F2268DAE: dmi.product.name: iMac11,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.64-1~ubuntu14.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.6 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.6 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1.6 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Wed Mar 16 19:43:11 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.15.1-0ubuntu2.7 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1406810/+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 1627641] Re: Backport netplan to xenial
** Changed in: nplan (Ubuntu Xenial) Status: Triaged => In Progress -- 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/1627641 Title: Backport netplan to xenial Status in network-manager package in Ubuntu: Fix Released Status in nplan package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Status in network-manager source package in Xenial: Fix Committed Status in nplan source package in Xenial: In Progress Status in systemd source package in Xenial: Fix Committed Bug description: For snappy (at first at least) we need to provide netplan in xenial, as for the first snappy GA release we must not use any PPAs any more. netplan's NetworkManager backend depends on two patches to read configuration and connections from /run/NetworkManager/. These will need to be backported for full netplan support; but they are not required for snappy as this will use a snapped NM. However, this will need a temporary hack (https://code.launchpad.net/%7Emorphis/netplan/+git/netplan/+merge/306607) until snaps can actually properly support OS components like NetworkManager. PATCHES: https://git.launchpad.net/~network-manager/network-manager/+git/ubuntu/commit/?h=xenial&id=6dcdb85 https://anonscm.debian.org/cgit/pkg-systemd/systemd.git/commit/?h=ubuntu-xenial&id=4e9c52b0bb REGRESSION POTENTIAL: netplan: The risk for existing installations is practically zero as nplan does not exist in xenial yet and thus will not be pulled in during upgrades. NetworkManager: Nothing in xenial expects/uses /run/NetworkManager/ and as it's an ephemeral tmpfs there is no risk of existing files there. If the patches are broken it could in theory happen that NetworkManager also does not properly read files from /etc/NetworkManager/ any more, so the -proposed package must verify that existing connections still work. systemd: This does change behavior of networkd on restart, but the previous behaviour was arguably buggy. networkd is not being used by default or advertised in Ubuntu 16.04, so this will not affect the vast majority of installations. TEST PLAN: 1. Run "NetworkManager --print-config" and save the output. 2. Install the proposed NetworkManager and confirm that existing connections (from /etc/NetworkManager/system-connections) still work. 3. Run "NetworkManager --print-config" again and verify that the output is the same as in step 1. 4. netplan has a very comprehensive integration test suite run as autopkgtest, which covers NetworkManager (including the /run patches) and network. Confirm that it succeeds. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1627641/+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 1628039] [NEW] ubufox makes Electrolysis stopped.
Public bug reported: Firefox has a new feature https://wiki.mozilla.org/Electrolysis. (abbr. e10s) ubufox makes e10s stopped. xul-ext-ubufox is installed by default so it affects all Ubuntu users. xul-ext-ubufox 3.2-0ubuntu1 ** Affects: ubufox (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubufox in Ubuntu. https://bugs.launchpad.net/bugs/1628039 Title: ubufox makes Electrolysis stopped. Status in ubufox package in Ubuntu: New Bug description: Firefox has a new feature https://wiki.mozilla.org/Electrolysis. (abbr. e10s) ubufox makes e10s stopped. xul-ext-ubufox is installed by default so it affects all Ubuntu users. xul-ext-ubufox 3.2-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubufox/+bug/1628039/+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 1628037] [NEW] HP zBook 15u dock station audio is not working
Public bug reported: Hello, everyone. I have an HP zBook 15u laptop with an HP slim dockstation and had a trouble with sound from the dock: dock has two separate jacks, one for line in and one for line out I solved it with pin retasking for 0x1b (out) and 0x18 (in) Here is my final configuration: #: sudo hdajacksensetest -c 1 -a Pin 0x12 (Internal Mic): present = No Pin 0x13 (Not connected): present = No Pin 0x14 (Internal Speaker): present = No Pin 0x15 (Black Headphone, Right side): present = No Pin 0x16 (Not connected): present = No Pin 0x17 (Not connected): present = No Pin 0x18 (Black Mic, Docking station, Rear side): present = Yes Pin 0x19 (Not connected): present = No Pin 0x1a (Black Mic, Right side): present = No Pin 0x1b (Black Line Out, Docking station, Rear side): present = Yes Pin 0x1d (Not connected): present = No Pin 0x1e (Not connected): present = No and this is the output for the alsa-info.sh script (0x18 may be listed as AUX): http://www.alsa-project.org/db/?f=b1381c8e2468a2928b0768cc66c2c02c3c0ca465 Can't decide if Pin 0x18 should be AUX or mic... Could someone please push this fix into a package (not sure which one)? Additionally, with this fix, I have a very short scratching noise on each boot. Is there anything I can do to fix this? I'm ready to test any additional solutions if needed. Thanks in advance. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19 Uname: Linux 4.4.0-38-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: XFCE Date: Tue Sep 27 13:13:15 2016 InstallationDate: Installed on 2016-01-15 (255 days ago) InstallationMedia: Xubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Type: Only some of inputs are working Title: [HDA-Intel - HDA Intel PCH, recording] Recording problem UpgradeStatus: Upgraded to xenial on 2016-08-03 (55 days ago) dmi.bios.date: 11/05/2015 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: M71 Ver. 01.12 dmi.board.name: 2216 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 96.58 dmi.chassis.asset.tag: 5CG53721SX dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrM71Ver.01.12:bd11/05/2015:svnHewlett-Packard:pnHPZBook15uG2:pvrA3009D510303:rvnHewlett-Packard:rn2216:rvrKBCVersion96.58:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP ZBook 15u G2 dmi.product.version: A3009D510303 dmi.sys.vendor: Hewlett-Packard ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug dock hp xenial zbook -- 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/1628037 Title: HP zBook 15u dock station audio is not working Status in alsa-driver package in Ubuntu: New Bug description: Hello, everyone. I have an HP zBook 15u laptop with an HP slim dockstation and had a trouble with sound from the dock: dock has two separate jacks, one for line in and one for line out I solved it with pin retasking for 0x1b (out) and 0x18 (in) Here is my final configuration: #: sudo hdajacksensetest -c 1 -a Pin 0x12 (Internal Mic): present = No Pin 0x13 (Not connected): present = No Pin 0x14 (Internal Speaker): present = No Pin 0x15 (Black Headphone, Right side): present = No Pin 0x16 (Not connected): present = No Pin 0x17 (Not connected): present = No Pin 0x18 (Black Mic, Docking station, Rear side): present = Yes Pin 0x19 (Not connected): present = No Pin 0x1a (Black Mic, Right side): present = No Pin 0x1b (Black Line Out, Docking station, Rear side): present = Yes Pin 0x1d (Not connected): present = No Pin 0x1e (Not connected): present = No and this is the output for the alsa-info.sh script (0x18 may be listed as AUX): http://www.alsa-project.org/db/?f=b1381c8e2468a2928b0768cc66c2c02c3c0ca465 Can't decide if Pin 0x18 should be AUX or mic... Could someone please push this fix into a package (not sure which one)? Additionally, with this fix, I have a very short scratching noise on each boot. Is there anything I can do to fix this? I'm ready to test any additional solutions if needed. Thanks in advance. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19 Uname: Linux 4.4.0-38-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: XFCE Date: Tue Sep 27 13:13:15 2016 InstallationDate: Installed on 2016-01-15 (255 days ago) InstallationMedia: Xubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) PackageArchitecture: all SourcePackage:
[Desktop-packages] [Bug 1612367] Re: [Touch] Incoming call gets silent randomly
Experienced once again on September 27 at around 10:48. ** Attachment added: "media-hub.log" https://bugs.launchpad.net/ubuntu/+source/media-hub/+bug/1612367/+attachment/4749272/+files/media-hub.log -- 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/1612367 Title: [Touch] Incoming call gets silent randomly Status in Canonical System Image: Confirmed Status in media-hub package in Ubuntu: Confirmed Status in ofono package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: I've experienced this strange issue 4-5 times after OTA-12. It seems pretty random and is hard to reproduce. When I get an incoming call, the screen turns on, the incoming call pop up appears, but there is no sound at all even though the phone is not in silent mode (and also the speaker volume is not set too low). I can accept this call and keep conversing as usual. Once I asked the same caller to call me once again after a few minutes, that time the phone rang as expected. Device: E5, OTA-12, stable channel I can provide necessary logs if this happens again. Which ones should I gather? Possibly related to bug #1614943. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1612367/+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 1627641] Re: Backport netplan to xenial
** Changed in: network-manager (Ubuntu) Importance: Undecided => Wishlist ** Changed in: nplan (Ubuntu) Importance: Undecided => Wishlist ** Changed in: systemd (Ubuntu) Importance: Undecided => Low -- 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/1627641 Title: Backport netplan to xenial Status in network-manager package in Ubuntu: Fix Released Status in nplan package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Status in network-manager source package in Xenial: Fix Committed Status in nplan source package in Xenial: In Progress Status in systemd source package in Xenial: Fix Committed Bug description: For snappy (at first at least) we need to provide netplan in xenial, as for the first snappy GA release we must not use any PPAs any more. netplan's NetworkManager backend depends on two patches to read configuration and connections from /run/NetworkManager/. These will need to be backported for full netplan support; but they are not required for snappy as this will use a snapped NM. However, this will need a temporary hack (https://code.launchpad.net/%7Emorphis/netplan/+git/netplan/+merge/306607) until snaps can actually properly support OS components like NetworkManager. PATCHES: https://git.launchpad.net/~network-manager/network-manager/+git/ubuntu/commit/?h=xenial&id=6dcdb85 https://anonscm.debian.org/cgit/pkg-systemd/systemd.git/commit/?h=ubuntu-xenial&id=4e9c52b0bb REGRESSION POTENTIAL: netplan: The risk for existing installations is practically zero as nplan does not exist in xenial yet and thus will not be pulled in during upgrades. NetworkManager: Nothing in xenial expects/uses /run/NetworkManager/ and as it's an ephemeral tmpfs there is no risk of existing files there. If the patches are broken it could in theory happen that NetworkManager also does not properly read files from /etc/NetworkManager/ any more, so the -proposed package must verify that existing connections still work. systemd: This does change behavior of networkd on restart, but the previous behaviour was arguably buggy. networkd is not being used by default or advertised in Ubuntu 16.04, so this will not affect the vast majority of installations. TEST PLAN: 1. Run "NetworkManager --print-config" and save the output. 2. Install the proposed NetworkManager and confirm that existing connections (from /etc/NetworkManager/system-connections) still work. 3. Run "NetworkManager --print-config" again and verify that the output is the same as in step 1. 4. netplan has a very comprehensive integration test suite run as autopkgtest, which covers NetworkManager (including the /run patches) and network. Confirm that it succeeds. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1627641/+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 1627641] Re: Backport netplan to xenial
Hello Martin, or anyone else affected, Accepted nplan into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/nplan/0.12~16.04 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 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: nplan (Ubuntu Xenial) Status: In Progress => Fix Committed -- 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/1627641 Title: Backport netplan to xenial Status in network-manager package in Ubuntu: Fix Released Status in nplan package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Status in network-manager source package in Xenial: Fix Committed Status in nplan source package in Xenial: Fix Committed Status in systemd source package in Xenial: Fix Committed Bug description: For snappy (at first at least) we need to provide netplan in xenial, as for the first snappy GA release we must not use any PPAs any more. netplan's NetworkManager backend depends on two patches to read configuration and connections from /run/NetworkManager/. These will need to be backported for full netplan support; but they are not required for snappy as this will use a snapped NM. However, this will need a temporary hack (https://code.launchpad.net/%7Emorphis/netplan/+git/netplan/+merge/306607) until snaps can actually properly support OS components like NetworkManager. PATCHES: https://git.launchpad.net/~network-manager/network-manager/+git/ubuntu/commit/?h=xenial&id=6dcdb85 https://anonscm.debian.org/cgit/pkg-systemd/systemd.git/commit/?h=ubuntu-xenial&id=4e9c52b0bb REGRESSION POTENTIAL: netplan: The risk for existing installations is practically zero as nplan does not exist in xenial yet and thus will not be pulled in during upgrades. NetworkManager: Nothing in xenial expects/uses /run/NetworkManager/ and as it's an ephemeral tmpfs there is no risk of existing files there. If the patches are broken it could in theory happen that NetworkManager also does not properly read files from /etc/NetworkManager/ any more, so the -proposed package must verify that existing connections still work. systemd: This does change behavior of networkd on restart, but the previous behaviour was arguably buggy. networkd is not being used by default or advertised in Ubuntu 16.04, so this will not affect the vast majority of installations. TEST PLAN: 1. Run "NetworkManager --print-config" and save the output. 2. Install the proposed NetworkManager and confirm that existing connections (from /etc/NetworkManager/system-connections) still work. 3. Run "NetworkManager --print-config" again and verify that the output is the same as in step 1. 4. netplan has a very comprehensive integration test suite run as autopkgtest, which covers NetworkManager (including the /run patches) and network. Confirm that it succeeds. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1627641/+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 1587154] Re: --working-directory does not work anymore
Apologies if this is a dumb question but does Daniel Alves 'no longer affects' annotation mean that this bug has been fixed in trunk/master, and we should expect a release at some point? Or something else? Thanks for helping me understand the process. -- 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/1587154 Title: --working-directory does not work anymore Status in gnome-terminal package in Ubuntu: Confirmed Bug description: After upgrading from ubuntu 14.04 to 16.04 one of my script the uses --working-directory option stopped working. Simply running: gnome-terminal --working-directory=/tmp Starts the terminal in my home directory. Changing the command to gnome-terminal.real does not solve my problem either. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1587154/+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 1621780] Re: upgrade failure from older nvidia release
I've got proposed turned on, but this bug is still happening to me. test@test-Precision-5510:~$ apt policy libcuda1-367 libcuda1-367: Installed: (none) Candidate: 367.44-0ubuntu0.16.04.2 Version table: 367.44-0ubuntu0.16.04.2 500 500 http://archive.ubuntu.com/ubuntu xenial-proposed/restricted amd64 Packages test@test-Precision-5510:~$ apt policy libcuda1-361 libcuda1-361: Installed: 361.45.11-0ubuntu0.16.04.1 Candidate: 367.44-0ubuntu0.16.04.2 Version table: 367.44-0ubuntu0.16.04.2 500 500 http://archive.ubuntu.com/ubuntu xenial-proposed/restricted amd64 Packages *** 361.45.11-0ubuntu0.16.04.1 100 100 /var/lib/dpkg/status 361.42-0ubuntu2 500 500 http://archive.ubuntu.com/ubuntu xenial/restricted amd64 Packages test@test-Precision-5510:~$ sudo apt dist-upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following packages were automatically installed and are no longer required: firefox-locale-en gir1.2-gcr-3 gir1.2-gdesktopenums-3.0 gir1.2-gnomedesktop-3.0 gir1.2-gtkspell3-3.0 gsettings-desktop-schemas-dev ipxe-qemu kwin-data libasound2-dev libatk-wrapper-java libatk-wrapper-java-jni libcaca-dev libcacard0 libdevmapper-dev libenchant-dev libfam0 libfdt1 libfuse-dev libfwup0 libgconf2-4 libglib2.0-0:i386 libgmpxxv4-4 libgnome2-0 libgnome2-bin libgstreamer-plugins-base0.10-0 libgstreamer-plugins-base0.10-0:i386 libgstreamer0.10-0 libgstreamer0.10-0:i386 libiscsi2 libjs-jquery-ui liblvm2app2.2 libmysqlclient18 libnspr4-dev libnss3-dev liboauth-dev liborc-0.4-0:i386 libparted-fs-resize0 libphonon4qt5-4 libpolkit-gobject-1-dev libpolkit-qt5-1-1 libpopt-dev libpulse-dev libqt4-help libqt4-opengl libqt4-scripttools libqt4-svg libqt4-test libqt5script5 libqtassistantclient4 libqtwebkit4 libreadline5 libsdl1.2-dev libselinux1-dev libsepol1-dev libslang2-dev libspice-server1 libsystemd-dev libtext-unidecode-perl libusbredirparser1 libvoikko1 libxcb-composite0 libxcb-cursor0 libxcb-damage0 libxen-4.6 libxen-dev libxenstore3.0 libxft2:i386 libxkbfile-dev libxml-libxml-perl libxml-namespacesupport-perl libxml-sax-base-perl libxml-sax-perl libxt-dev libxtst6:i386 libxv1:i386 linux-image-extra-4.4.0-21-generic linux-image-extra-4.4.0-22-generic linux-image-extra-4.4.0-28-generic linux-image-extra-4.4.0-31-generic linux-image-extra-4.4.0-33-generic linux-image-extra-4.4.0-34-generic linux-image-extra-4.4.0-36-generic linux-image-extra-4.4.0-37-generic linux-signed-image-4.4.0-21-generic linux-signed-image-4.4.0-22-generic linux-signed-image-4.4.0-28-generic linux-signed-image-4.4.0-31-generic linux-signed-image-4.4.0-33-generic linux-signed-image-4.4.0-34-generic linux-signed-image-4.4.0-36-generic linux-signed-image-4.4.0-37-generic linux-tools-4.4.0-21 linux-tools-4.4.0-21-generic linux-tools-4.4.0-22 linux-tools-4.4.0-22-generic linux-tools-4.4.0-28 linux-tools-4.4.0-28-generic linux-tools-4.4.0-31 linux-tools-4.4.0-31-generic linux-tools-4.4.0-33 linux-tools-4.4.0-33-generic linux-tools-4.4.0-34 linux-tools-4.4.0-34-generic linux-tools-4.4.0-36 linux-tools-4.4.0-36-generic linux-tools-4.4.0-37 linux-tools-4.4.0-37-generic lvm2 nvidia-opencl-icd-361 pyflakes pyflakes3 python-distutils-extra python-pyflakes python3-all python3-distutils-extra python3-icu python3-pam python3-pyflakes python3-pyqt4 python3-sip python3-ssoclient qemu-block-extra qemu-slof qemu-system qemu-system-arm qemu-system-common qemu-system-mips qemu-system-misc qemu-system-ppc qemu-system-sparc qemu-system-x86 qml-module-qtquick-controls qml-module-qtquick-dialogs qml-module-qtquick-privatewidgets rdate seabios seccomp snap-confine syslinux-utils texinfo ttf-dejavu-core ttf-dejavu-extra ubuntu-core-launcher ubuntu-core-security-apparmor ubuntu-core-security-seccomp ubuntu-core-security-utils valgrind watershed xfonts-unifont Use 'sudo apt autoremove' to remove them. The following NEW packages will be installed: libcuda1-367 The following packages will be upgraded: libcuda1-361 1 upgraded, 1 newly installed, 0 to remove and 0 not upgraded. 108 not fully installed or removed. Need to get 0 B/2,695 kB of archives. After this operation, 18.9 MB disk space will be freed. Do you want to continue? [Y/n] y (Reading database ... 585415 files and directories currently installed.) Preparing to unpack .../libcuda1-361_367.44-0ubuntu0.16.04.2_amd64.deb ... Failed to stop var-lib-snapd-lib-gl.mount: Unit var-lib-snapd-lib-gl.mount not loaded. dpkg: warning: subprocess old pre-removal script returned error exit status 5 dpkg: trying script from the new package instead ... dpkg: error processing archive /var/cache/apt/archives/libcuda1-361_367.44-0ubuntu0.16.04.2_amd64.deb (--unpack): there is no script in the new version of the package - giving up Failed to get unit file state for var-lib-snapd-lib-gl.mount: No such file or directory var-lib-snapd-lib
[Desktop-packages] [Bug 1516402] Re: nvidia-304 304.128-0ubuntu0.0.1: nvidia-304 kernel module failed to build
*** This bug is a duplicate of bug 1498146 *** https://bugs.launchpad.net/bugs/1498146 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nvidia-graphics-drivers-304 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-304 in Ubuntu. https://bugs.launchpad.net/bugs/1516402 Title: nvidia-304 304.128-0ubuntu0.0.1: nvidia-304 kernel module failed to build Status in nvidia-graphics-drivers-304 package in Ubuntu: Confirmed Bug description: This occurs on installing Kernel 4.3 on a Asus N56V Laptop, Ubuntu 14.04.3 with Kernel 4.2.0-18 running, trying to install Kernel 4.3 as follow: $ wget http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.3-wily/linux- headers-4.3.0-040300_4.3.0-040300.201511020949_all.deb $ wget http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.3-wily/linux- headers-4.3.0-040300-generic_4.3.0-040300.201511020949_amd64.deb $ wget http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.3-wily/linux- image-4.3.0-040300-generic_4.3.0-040300.201511020949_amd64.deb $ sudo dpkg -i linux-headers-4.3.0*.deb linux-image-4.3.0*.deb It seems to be dependency problems. Hybrid Intel Graphics HD 4000 or 4400 i'm not sure, and nvidia 740M. nvidia-304 304.128-0ubuntu0.0.1: nvidia-304 kernel module failed to build Thank you ProblemType: Package DistroRelease: Ubuntu 14.04 Package: nvidia-304 304.128-0ubuntu0.0.1 ProcVersionSignature: Ubuntu 4.2.0-18.22~14.04.1-generic 4.2.3 Uname: Linux 4.2.0-18-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.18 Architecture: amd64 DKMSKernelVersion: 4.3.0-040300-generic Date: Sun Nov 15 11:03:30 2015 DuplicateSignature: dkms:nvidia-304:304.128-0ubuntu0.0.1:/var/lib/dkms/nvidia-304/304.128/build/nv-procfs.c:610:5: error: void value not ignored as it ought to be InstallationDate: Installed on 2015-04-12 (216 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) PackageVersion: 304.128-0ubuntu0.0.1 RelatedPackageVersions: dpkg 1.17.5ubuntu5.4 apt 1.0.1ubuntu2.10 SourcePackage: nvidia-graphics-drivers-304 Title: nvidia-304 304.128-0ubuntu0.0.1: nvidia-304 kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1516402/+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 1516402] Re: nvidia-304 304.128-0ubuntu0.0.1: nvidia-304 kernel module failed to build
*** This bug is a duplicate of bug 1498146 *** https://bugs.launchpad.net/bugs/1498146 I don't know why this is marked duplicate of bug #1498146. That one talks about build error with version 340 of the driver. This bug is about module loading error in version 304 which still happens today with Ubuntu 16.04. Version 304 is the only version with legacy support for older GeForce series such as 6800 GT. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-304 in Ubuntu. https://bugs.launchpad.net/bugs/1516402 Title: nvidia-304 304.128-0ubuntu0.0.1: nvidia-304 kernel module failed to build Status in nvidia-graphics-drivers-304 package in Ubuntu: Confirmed Bug description: This occurs on installing Kernel 4.3 on a Asus N56V Laptop, Ubuntu 14.04.3 with Kernel 4.2.0-18 running, trying to install Kernel 4.3 as follow: $ wget http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.3-wily/linux- headers-4.3.0-040300_4.3.0-040300.201511020949_all.deb $ wget http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.3-wily/linux- headers-4.3.0-040300-generic_4.3.0-040300.201511020949_amd64.deb $ wget http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.3-wily/linux- image-4.3.0-040300-generic_4.3.0-040300.201511020949_amd64.deb $ sudo dpkg -i linux-headers-4.3.0*.deb linux-image-4.3.0*.deb It seems to be dependency problems. Hybrid Intel Graphics HD 4000 or 4400 i'm not sure, and nvidia 740M. nvidia-304 304.128-0ubuntu0.0.1: nvidia-304 kernel module failed to build Thank you ProblemType: Package DistroRelease: Ubuntu 14.04 Package: nvidia-304 304.128-0ubuntu0.0.1 ProcVersionSignature: Ubuntu 4.2.0-18.22~14.04.1-generic 4.2.3 Uname: Linux 4.2.0-18-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.18 Architecture: amd64 DKMSKernelVersion: 4.3.0-040300-generic Date: Sun Nov 15 11:03:30 2015 DuplicateSignature: dkms:nvidia-304:304.128-0ubuntu0.0.1:/var/lib/dkms/nvidia-304/304.128/build/nv-procfs.c:610:5: error: void value not ignored as it ought to be InstallationDate: Installed on 2015-04-12 (216 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) PackageVersion: 304.128-0ubuntu0.0.1 RelatedPackageVersions: dpkg 1.17.5ubuntu5.4 apt 1.0.1ubuntu2.10 SourcePackage: nvidia-graphics-drivers-304 Title: nvidia-304 304.128-0ubuntu0.0.1: nvidia-304 kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1516402/+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 1516402] Re: nvidia-304 304.128-0ubuntu0.0.1: nvidia-304 kernel module failed to build
*** This bug is a duplicate of bug 1498146 *** https://bugs.launchpad.net/bugs/1498146 Never mind. Original bug was build error. The chat afterwards is concerning Bug #1531151. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-304 in Ubuntu. https://bugs.launchpad.net/bugs/1516402 Title: nvidia-304 304.128-0ubuntu0.0.1: nvidia-304 kernel module failed to build Status in nvidia-graphics-drivers-304 package in Ubuntu: Confirmed Bug description: This occurs on installing Kernel 4.3 on a Asus N56V Laptop, Ubuntu 14.04.3 with Kernel 4.2.0-18 running, trying to install Kernel 4.3 as follow: $ wget http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.3-wily/linux- headers-4.3.0-040300_4.3.0-040300.201511020949_all.deb $ wget http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.3-wily/linux- headers-4.3.0-040300-generic_4.3.0-040300.201511020949_amd64.deb $ wget http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.3-wily/linux- image-4.3.0-040300-generic_4.3.0-040300.201511020949_amd64.deb $ sudo dpkg -i linux-headers-4.3.0*.deb linux-image-4.3.0*.deb It seems to be dependency problems. Hybrid Intel Graphics HD 4000 or 4400 i'm not sure, and nvidia 740M. nvidia-304 304.128-0ubuntu0.0.1: nvidia-304 kernel module failed to build Thank you ProblemType: Package DistroRelease: Ubuntu 14.04 Package: nvidia-304 304.128-0ubuntu0.0.1 ProcVersionSignature: Ubuntu 4.2.0-18.22~14.04.1-generic 4.2.3 Uname: Linux 4.2.0-18-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.18 Architecture: amd64 DKMSKernelVersion: 4.3.0-040300-generic Date: Sun Nov 15 11:03:30 2015 DuplicateSignature: dkms:nvidia-304:304.128-0ubuntu0.0.1:/var/lib/dkms/nvidia-304/304.128/build/nv-procfs.c:610:5: error: void value not ignored as it ought to be InstallationDate: Installed on 2015-04-12 (216 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) PackageVersion: 304.128-0ubuntu0.0.1 RelatedPackageVersions: dpkg 1.17.5ubuntu5.4 apt 1.0.1ubuntu2.10 SourcePackage: nvidia-graphics-drivers-304 Title: nvidia-304 304.128-0ubuntu0.0.1: nvidia-304 kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1516402/+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 1282294] Re: "Cannot open pixbuf loader module file"
Same of Marat Khalili here -- 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/1282294 Title: "Cannot open pixbuf loader module file" Status in gdk-pixbuf package in Ubuntu: Triaged Status in gdk-pixbuf package in Debian: New Bug description: While doing testing on trusty, I keep finding errors like the following in my apt-get -u dist-upgrade output: Preparing to unpack .../indicator-printers_0.1.7+14.04.20140213-0ubuntu1_amd64.deb ... Unpacking indicator-printers (0.1.7+14.04.20140213-0ubuntu1) over (0.1.7daily13.03.01-0ubuntu1) ... (gtk-update-icon-cache-3.0:29671): GdkPixbuf-WARNING **: Cannot open pixbuf loader module file '/usr/lib/x86_64-linux-gnu/gdk- pixbuf-2.0/2.10.0/loaders.cache': No such file or directory This likely means that your installation is broken. Try running the command gdk-pixbuf-query-loaders > /usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders.cache to make things work again for the time being. (gtk-update-icon-cache-3.0:29672): GdkPixbuf-WARNING **: Cannot open pixbuf loader module file '/usr/lib/x86_64-linux-gnu/gdk- pixbuf-2.0/2.10.0/loaders.cache': No such file or directory This likely means that your installation is broken. Try running the command gdk-pixbuf-query-loaders > /usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders.cache to make things work again for the time being. ... Processing triggers for hicolor-icon-theme (0.13-1) ... (gtk-update-icon-cache-3.0:32198): GdkPixbuf-WARNING **: Cannot open pixbuf loader module file '/usr/lib/x86_64-linux-gnu/gdk- pixbuf-2.0/2.10.0/loaders.cache': No such file or directory This likely means that your installation is broken. Try running the command gdk-pixbuf-query-loaders > /usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders.cache to make things work again for the time being. These errors make it difficult to look for errors that I might have introduced in my own packages and if they persist in our final product will make users wonder what is broken and why it is broken. sarnold@sec-trusty-amd64:~$ lsb_release -rd Description: Ubuntu Trusty Tahr (development branch) Release: 14.04 sarnold@sec-trusty-amd64:~$ dpkg -S gdk-pixbuf-query-loaders libgdk-pixbuf2.0-0:amd64: /usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/gdk-pixbuf-query-loaders sarnold@sec-trusty-amd64:~$ apt-cache policy libgdk-pixbuf2.0-0 libgdk-pixbuf2.0-0: Installed: 2.30.5-0ubuntu1 Candidate: 2.30.5-0ubuntu1 Version table: *** 2.30.5-0ubuntu1 0 500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status sarnold@sec-trusty-amd64:~$ dpkg -S /usr/bin/gtk-update-icon-cache-3.0 libgtk-3-bin: /usr/bin/gtk-update-icon-cache-3.0 sarnold@sec-trusty-amd64:~$ apt-cache policy libgtk-3-bin libgtk-3-bin: Installed: 3.10.7-0ubuntu2 Candidate: 3.10.7-0ubuntu2 Version table: *** 3.10.7-0ubuntu2 0 500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status sarnold@sec-trusty-amd64:~$ Thanks ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: libgtk-3-bin 3.10.7-0ubuntu2 ProcVersionSignature: User Name 3.13.0-5.20-generic 3.13.0 Uname: Linux 3.13.0-5-generic x86_64 ApportVersion: 2.13.2-0ubuntu5 Architecture: amd64 Date: Wed Feb 19 14:38:47 2014 InstallationDate: Installed on 2014-01-09 (41 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140108) ProcEnviron: TERM=rxvt-unicode PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gtk+3.0 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdk-pixbuf/+bug/1282294/+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 1609898] Re: dhclient incorrectly assumes a /64 ipv6 prefix
Cherry-picked into xenial branch. ** Changed in: network-manager (Ubuntu Xenial) Status: Triaged => Fix Committed -- 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/1609898 Title: dhclient incorrectly assumes a /64 ipv6 prefix Status in isc-dhcp package in Ubuntu: Fix Committed Status in network-manager package in Ubuntu: Fix Committed Status in isc-dhcp source package in Precise: Fix Released Status in network-manager source package in Precise: Invalid Status in isc-dhcp source package in Trusty: Fix Released Status in network-manager source package in Trusty: Triaged Status in isc-dhcp source package in Xenial: Fix Released Status in network-manager source package in Xenial: Fix Committed Status in isc-dhcp source package in Yakkety: Fix Committed Status in network-manager source package in Yakkety: Fix Committed Status in isc-dhcp package in Debian: Fix Released Bug description: [Impact] clients who get an ipv6 address from a dhcpv6 server assume the address has a /64 prefix, but that is not necessarily true, and if the subnet is different than /64 those clients will not be able to reach other addresses in that /64 prefix because the other systems are not on-link. This /64 assumption of dhclient effectively breaks the client networking for certain addresses. [Test Case] Set up a server with two interface nics, and one client connected to each of those interfaces. On the server, set up a ipv6 subnet on each interface, with a larger prefix than /64, e.g.: 2001:db8:0:0:1::/96 2001:db8:0:0:2::/96 configure dhcpv6 on the server, to provide ipv6 addresses on each interface. Set the server as the default ipv6 route for the clients. Allow the clients to get dhcpv6 ipv6 addresses from the server. The clients will each get a ipv6 address with a /64 prefix, due to the bug in dhclient. Try to ping (or otherwise communicate) between the clients. Since they have /64 prefixes, they think they are on-link with each other, but they are not, so they can't communicate. After the dhclient bug is fixed, repeat the above setup, and the clients will get /128 prefixes instead, and then will be able to communicate with each other, because they will route the traffic to each other through the server. [Regression Potential] Non-standard (i.e. not /64) subnets served by dhcpv6 currently are broken, this fixes that. However, any ipv6 network configurations that rely on the previous incorrect assumed /64 behavior (as described here: https://tools.ietf.org/html/rfc5942#section-5) in order to allow dhcpv6 clients to communicate with other systems inside the subnet, but do not use RA to also provide clients with the actual prefix len, will break. To clarify: a server that provides clients with dhcpv6 addresses, but does not also provide the prefix len via RA, will change behavior; previously, all clients on the subnet could talk directly to each other, with this update the clients cannot talk to each other directly; all traffic between clients will be routed through the default gateway. Further, if the network does not provide a default gateway - for example a local network that is intended only for traffic between local servers - the clients will not be able to talk to each other at all. Note that such configurations *are* broken configurations, that just happened to work before because of incorrect dhcp client behavior; such configurations must be updated to perform RA to provide the prefix len to clients. See comment 30 for details on how to configure radvd to restore network functionality. [Other Info] This is fixed in debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=684009 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1609898/+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 1531151] Re: Can't be inserted into 4.3 kernel
Debian has a patch for this here: https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=809324 ** Bug watch added: Debian Bug tracker #809324 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=809324 ** Also affects: debian via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=809324 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-304 in Ubuntu. https://bugs.launchpad.net/bugs/1531151 Title: Can't be inserted into 4.3 kernel Status in nvidia-graphics-drivers-304 package in Ubuntu: Confirmed Status in Debian: Unknown Bug description: I just installed "nvidia-current", which was probably an error (I'm now using -352) but nevertheless it couldn't be loaded into my 4.3 kernel, on xenial. Jan 05 12:10:54 raleigh.local kernel: mtrr: no MTRR for f100,e0 found Jan 05 12:10:55 raleigh.local kernel: nvidia: Unknown symbol mtrr_del (err 0) Jan 05 12:10:55 raleigh.local kernel: nvidia: Unknown symbol mtrr_add (err 0) Jan 05 12:10:55 raleigh.local kernel: nvidia: Unknown symbol mtrr_del (err 0) Jan 05 12:10:55 raleigh.local kernel: nvidia: Unknown symbol mtrr_add (err 0) If we're providing it then it should be loadable into our shipping kernel. Otherwise maybe stop? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1531151/+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 1628153] [NEW] [W65_67SF, VIA VT1802, Speaker, Internal] No sound at all on most restarts
Public bug reported: On the vast majority of restarts of Ubuntu 16.04 I get no internal sound at all. There are no reported issues in system settings on the only sound card I have. The volume is not muted. On an estimated 1 in 10 restart, the sound works, and both the test sounds get played and other applications work fine. There is no reported errors or messages on the restarts when the sound has failed. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19 Uname: Linux 4.4.0-38-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0p: tony 16160 F...m pulseaudio /dev/snd/controlC1: tony 16160 F pulseaudio /dev/snd/controlC0: tony 16160 F pulseaudio CurrentDesktop: Unity Date: Tue Sep 27 15:56:02 2016 InstallationDate: Installed on 2015-10-29 (334 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0p: tony 16160 F...m pulseaudio /dev/snd/controlC1: tony 16160 F pulseaudio /dev/snd/controlC0: tony 16160 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [W65_67SF, VIA VT1802, Speaker, Internal] No sound at all UpgradeStatus: Upgraded to xenial on 2016-08-13 (45 days ago) dmi.bios.date: 04/01/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.03.03 dmi.board.asset.tag: Tag 12345 dmi.board.name: W65_67SF dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.03.03:bd04/01/2014:svnNotebook:pnW65_67SF:pvrNotApplicable:rvnNotebook:rnW65_67SF:rvrNotApplicable:cvnNotebook:ct9:cvrN/A: dmi.product.name: W65_67SF dmi.product.version: Not Applicable dmi.sys.vendor: Notebook ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1628153 Title: [W65_67SF, VIA VT1802, Speaker, Internal] No sound at all on most restarts Status in alsa-driver package in Ubuntu: New Bug description: On the vast majority of restarts of Ubuntu 16.04 I get no internal sound at all. There are no reported issues in system settings on the only sound card I have. The volume is not muted. On an estimated 1 in 10 restart, the sound works, and both the test sounds get played and other applications work fine. There is no reported errors or messages on the restarts when the sound has failed. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19 Uname: Linux 4.4.0-38-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0p: tony 16160 F...m pulseaudio /dev/snd/controlC1: tony 16160 F pulseaudio /dev/snd/controlC0: tony 16160 F pulseaudio CurrentDesktop: Unity Date: Tue Sep 27 15:56:02 2016 InstallationDate: Installed on 2015-10-29 (334 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0p: tony 16160 F...m pulseaudio /dev/snd/controlC1: tony 16160 F pulseaudio /dev/snd/controlC0: tony 16160 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [W65_67SF, VIA VT1802, Speaker, Internal] No sound at all UpgradeStatus: Upgraded to xenial on 2016-08-13 (45 days ago) dmi.bios.date: 04/01/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.03.03 dmi.board.asset.tag: Tag 12345 dmi.board.name: W65_67SF dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.03.03:bd04/01/2014:svnNotebook:pnW65_67SF:pvrNotApplicable:rvnNotebook:rnW65_67SF:rvrNotApplicable:cvnNotebook:ct9:cvrN/A: dmi.product.n
[Desktop-packages] [Bug 1627641] Please test proposed package
Hello Martin, or anyone else affected, Accepted network-manager into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/network- manager/1.2.2-0ubuntu0.16.04.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 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 network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1627641 Title: Backport netplan to xenial Status in network-manager package in Ubuntu: Fix Released Status in nplan package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Status in network-manager source package in Xenial: Fix Committed Status in nplan source package in Xenial: Fix Committed Status in systemd source package in Xenial: Fix Committed Bug description: For snappy (at first at least) we need to provide netplan in xenial, as for the first snappy GA release we must not use any PPAs any more. netplan's NetworkManager backend depends on two patches to read configuration and connections from /run/NetworkManager/. These will need to be backported for full netplan support; but they are not required for snappy as this will use a snapped NM. However, this will need a temporary hack (https://code.launchpad.net/%7Emorphis/netplan/+git/netplan/+merge/306607) until snaps can actually properly support OS components like NetworkManager. PATCHES: https://git.launchpad.net/~network-manager/network-manager/+git/ubuntu/commit/?h=xenial&id=6dcdb85 https://anonscm.debian.org/cgit/pkg-systemd/systemd.git/commit/?h=ubuntu-xenial&id=4e9c52b0bb REGRESSION POTENTIAL: netplan: The risk for existing installations is practically zero as nplan does not exist in xenial yet and thus will not be pulled in during upgrades. NetworkManager: Nothing in xenial expects/uses /run/NetworkManager/ and as it's an ephemeral tmpfs there is no risk of existing files there. If the patches are broken it could in theory happen that NetworkManager also does not properly read files from /etc/NetworkManager/ any more, so the -proposed package must verify that existing connections still work. systemd: This does change behavior of networkd on restart, but the previous behaviour was arguably buggy. networkd is not being used by default or advertised in Ubuntu 16.04, so this will not affect the vast majority of installations. TEST PLAN: 1. Run "NetworkManager --print-config" and save the output. 2. Install the proposed NetworkManager and confirm that existing connections (from /etc/NetworkManager/system-connections) still work. 3. Run "NetworkManager --print-config" again and verify that the output is the same as in step 1. 4. netplan has a very comprehensive integration test suite run as autopkgtest, which covers NetworkManager (including the /run patches) and network. Confirm that it succeeds. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1627641/+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 1609898] Re: dhclient incorrectly assumes a /64 ipv6 prefix
Hello Dan, or anyone else affected, Accepted network-manager into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/network- manager/1.2.2-0ubuntu0.16.04.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 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 network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1609898 Title: dhclient incorrectly assumes a /64 ipv6 prefix Status in isc-dhcp package in Ubuntu: Fix Committed Status in network-manager package in Ubuntu: Fix Committed Status in isc-dhcp source package in Precise: Fix Released Status in network-manager source package in Precise: Invalid Status in isc-dhcp source package in Trusty: Fix Released Status in network-manager source package in Trusty: Triaged Status in isc-dhcp source package in Xenial: Fix Released Status in network-manager source package in Xenial: Fix Committed Status in isc-dhcp source package in Yakkety: Fix Committed Status in network-manager source package in Yakkety: Fix Committed Status in isc-dhcp package in Debian: Fix Released Bug description: [Impact] clients who get an ipv6 address from a dhcpv6 server assume the address has a /64 prefix, but that is not necessarily true, and if the subnet is different than /64 those clients will not be able to reach other addresses in that /64 prefix because the other systems are not on-link. This /64 assumption of dhclient effectively breaks the client networking for certain addresses. [Test Case] Set up a server with two interface nics, and one client connected to each of those interfaces. On the server, set up a ipv6 subnet on each interface, with a larger prefix than /64, e.g.: 2001:db8:0:0:1::/96 2001:db8:0:0:2::/96 configure dhcpv6 on the server, to provide ipv6 addresses on each interface. Set the server as the default ipv6 route for the clients. Allow the clients to get dhcpv6 ipv6 addresses from the server. The clients will each get a ipv6 address with a /64 prefix, due to the bug in dhclient. Try to ping (or otherwise communicate) between the clients. Since they have /64 prefixes, they think they are on-link with each other, but they are not, so they can't communicate. After the dhclient bug is fixed, repeat the above setup, and the clients will get /128 prefixes instead, and then will be able to communicate with each other, because they will route the traffic to each other through the server. [Regression Potential] Non-standard (i.e. not /64) subnets served by dhcpv6 currently are broken, this fixes that. However, any ipv6 network configurations that rely on the previous incorrect assumed /64 behavior (as described here: https://tools.ietf.org/html/rfc5942#section-5) in order to allow dhcpv6 clients to communicate with other systems inside the subnet, but do not use RA to also provide clients with the actual prefix len, will break. To clarify: a server that provides clients with dhcpv6 addresses, but does not also provide the prefix len via RA, will change behavior; previously, all clients on the subnet could talk directly to each other, with this update the clients cannot talk to each other directly; all traffic between clients will be routed through the default gateway. Further, if the network does not provide a default gateway - for example a local network that is intended only for traffic between local servers - the clients will not be able to talk to each other at all. Note that such configurations *are* broken configurations, that just happened to work before because of incorrect dhcp client behavior; such configurations must be updated to perform RA to provide the prefix len to clients. See comment 30 for details on how to configure radvd to restore network functionality. [Other Info] This is fixed in debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=684009 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1609898/+subscriptions -- Mailing list: https://launchp
[Desktop-packages] [Bug 1592721] Please test proposed package
Hello Mathieu, or anyone else affected, Accepted network-manager into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/network- manager/1.2.2-0ubuntu0.16.04.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 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 network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1592721 Title: Don't write search domains to resolv.conf in the case of split DNS Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Xenial: Fix Committed Bug description: [Impact] All VPN users meaning to use split-tunnelling in a situation where leaking DNS data to the internet about what might be behind their VPN is undesirable. [Test case] 1) connect to VPN 2) Use dig to request a name that should be on the VPN 3) Verify (kill -USR1 the dnsmasq binary from NM) that the request has only gone through the VPN nameservers (only its request number should have increased by one) 4) Use dig to request a name off-VPN, such as google.com. 5) Verify (kill -USR1 again) that the request has caused the non-VPN nameserver request number to increase, and that the VPN number has not increased. It is easier to verify this when there is as little traffic as possible on the system, to avoid spurious DNS requests which would make it harder to validate the counters. [Regression potential] This change modifies the way in which DNS nameservers and search domains are passed to dnsmasq, as such, if a VPN is configured in a non-standard way and intended to be used to resolve all network requests (which is typically not the case for split-tunnelling) or if the public network is intended to always resolve all requests while the VPN still provides search domains, one might observe incorrect behavior. Possible failure cases would include failure to resolve names correctly (resulting in NXDOMAIN or REFUSED from dnsmasq) or resolving to the incorrect values (if the wrong nameserver is used). --- Currently, NM will write all search domains to both any DNS-handling plugins running, and also to resolv.conf / resolvconf; in all cases. The issue is that doing so means that in the split-DNS case on VPNs, you might get a negative response from all nameservers, then a new request by glibc with the search tacked on, to nameservers again, which might cause DNS requests for "private" resources (say, on the VPN) to be sent to external, untrusted resolvers, or for DNS queries not meant for VPN nameservers to be sent through the VPN anyway. This is fixable in the case where we have a caching plugin running (such as dnsmasq). dnsmasq will already know about the search domains and use that to limit queries to the right nameservers when a VPN is running. Writing search domains to resolv.conf is unnecessary in this case. We should still write search domains if no caching gets done, as we then need to expect glibc to send requests as it otherwise would. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1592721/+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 1531151] Re: Can't be inserted into 4.3 kernel
** Changed in: debian Status: Unknown => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-304 in Ubuntu. https://bugs.launchpad.net/bugs/1531151 Title: Can't be inserted into 4.3 kernel Status in nvidia-graphics-drivers-304 package in Ubuntu: Confirmed Status in Debian: Fix Released Bug description: I just installed "nvidia-current", which was probably an error (I'm now using -352) but nevertheless it couldn't be loaded into my 4.3 kernel, on xenial. Jan 05 12:10:54 raleigh.local kernel: mtrr: no MTRR for f100,e0 found Jan 05 12:10:55 raleigh.local kernel: nvidia: Unknown symbol mtrr_del (err 0) Jan 05 12:10:55 raleigh.local kernel: nvidia: Unknown symbol mtrr_add (err 0) Jan 05 12:10:55 raleigh.local kernel: nvidia: Unknown symbol mtrr_del (err 0) Jan 05 12:10:55 raleigh.local kernel: nvidia: Unknown symbol mtrr_add (err 0) If we're providing it then it should be loadable into our shipping kernel. Otherwise maybe stop? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1531151/+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 1628184] [NEW] Cannot cancel changing SSH passphrase in seahorse
Public bug reported: Problem: If a user starts the changing passphrase process in seahorse, but clicks cancel after entering the current passphrase, the passphrase is changed to be empty. Expected: Clicking cancel when prompted to enter a new passphrase should result in no change to the current passphrase. Steps to reproduce: - User has SSH key with nonempty passphrase - Launch seahorse, navigate to SSH key properties, select "Change Passphrase" - Enter current passphrase - Click "Cancel" button twice ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: seahorse 3.18.0-2ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19 Uname: Linux 4.4.0-38-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity Date: Tue Sep 27 11:52:12 2016 ExecutablePath: /usr/bin/seahorse InstallationDate: Installed on 2016-09-23 (3 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) ProcEnviron: PATH=(custom, user) SHELL=/usr/bin/fish LANG=en_US.UTF-8 LANGUAGE=en_US XDG_RUNTIME_DIR= SourcePackage: seahorse UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: seahorse (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to seahorse in Ubuntu. https://bugs.launchpad.net/bugs/1628184 Title: Cannot cancel changing SSH passphrase in seahorse Status in seahorse package in Ubuntu: New Bug description: Problem: If a user starts the changing passphrase process in seahorse, but clicks cancel after entering the current passphrase, the passphrase is changed to be empty. Expected: Clicking cancel when prompted to enter a new passphrase should result in no change to the current passphrase. Steps to reproduce: - User has SSH key with nonempty passphrase - Launch seahorse, navigate to SSH key properties, select "Change Passphrase" - Enter current passphrase - Click "Cancel" button twice ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: seahorse 3.18.0-2ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19 Uname: Linux 4.4.0-38-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity Date: Tue Sep 27 11:52:12 2016 ExecutablePath: /usr/bin/seahorse InstallationDate: Installed on 2016-09-23 (3 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) ProcEnviron: PATH=(custom, user) SHELL=/usr/bin/fish LANG=en_US.UTF-8 LANGUAGE=en_US XDG_RUNTIME_DIR= SourcePackage: seahorse UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/seahorse/+bug/1628184/+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 1627310] Re: Guest session fails to log out
*** This bug is a duplicate of bug 1627304 *** https://bugs.launchpad.net/bugs/1627304 test@test-Standard-PC-i440FX-PIIX-1996:~$ dmesg | grep DENIED [ 50.801345] audit: type=1400 audit(1474991831.922:27): apparmor="DENIED" operation="mknod" profile="/usr/lib/lightdm/lightdm-guest-session" name="/proc/1722/fd/2" pid=1722 comm="lightdm-session" requested_mask="c" denied_mask="c" fsuid=996 ouid=996 [ 50.803080] audit: type=1400 audit(1474991831.922:28): apparmor="DENIED" operation="mknod" profile="/usr/lib/lightdm/lightdm-guest-session" name="/proc/1724/fd/2" pid=1724 comm="lightdm-session" requested_mask="c" denied_mask="c" fsuid=996 ouid=996 [ 50.932125] audit: type=1400 audit(1474991832.054:29): apparmor="DENIED" operation="connect" profile="/usr/lib/lightdm/lightdm-guest-session" pid=1846 comm="initctl" family="unix" sock_type="stream" protocol=0 requested_mask="send receive accept" denied_mask="send accept" addr="@/com/ubuntu/upstart-session/996/1720" peer_addr=none peer="unconfined" [ 50.941490] audit: type=1400 audit(1474991832.062:30): apparmor="DENIED" operation="connect" profile="/usr/lib/lightdm/lightdm-guest-session" pid=1862 comm="initctl" family="unix" sock_type="stream" protocol=0 requested_mask="send receive accept" denied_mask="send accept" addr="@/com/ubuntu/upstart-session/996/1720" peer_addr=none peer="unconfined" [ 50.946784] audit: type=1400 audit(1474991832.066:31): apparmor="DENIED" operation="connect" profile="/usr/lib/lightdm/lightdm-guest-session" pid=1866 comm="initctl" family="unix" sock_type="stream" protocol=0 requested_mask="send receive accept" denied_mask="send accept" addr="@/com/ubuntu/upstart-session/996/1720" peer_addr=none peer="unconfined" [ 50.949328] audit: type=1400 audit(1474991832.070:32): apparmor="DENIED" operation="connect" profile="/usr/lib/lightdm/lightdm-guest-session" pid=1870 comm="initctl" family="unix" sock_type="stream" protocol=0 requested_mask="send receive accept" denied_mask="send accept" addr="@/com/ubuntu/upstart-session/996/1720" peer_addr=none peer="unconfined" [ 50.951780] audit: type=1400 audit(1474991832.074:33): apparmor="DENIED" operation="connect" profile="/usr/lib/lightdm/lightdm-guest-session" pid=1874 comm="initctl" family="unix" sock_type="stream" protocol=0 requested_mask="send receive accept" denied_mask="send accept" addr="@/com/ubuntu/upstart-session/996/1720" peer_addr=none peer="unconfined" [ 50.954141] audit: type=1400 audit(1474991832.074:34): apparmor="DENIED" operation="connect" profile="/usr/lib/lightdm/lightdm-guest-session" pid=1878 comm="initctl" family="unix" sock_type="stream" protocol=0 requested_mask="send receive accept" denied_mask="send accept" addr="@/com/ubuntu/upstart-session/996/1720" peer_addr=none peer="unconfined" [ 62.395078] audit: type=1400 audit(1474991843.538:35): apparmor="DENIED" operation="connect" profile="/usr/lib/lightdm/lightdm-guest-session" pid=2127 comm="initctl" family="unix" sock_type="stream" protocol=0 requested_mask="send receive accept" denied_mask="send accept" addr="@/com/ubuntu/upstart-session/996/1720" peer_addr=none peer="unconfined" [ 62.397757] audit: type=1400 audit(1474991843.542:36): apparmor="DENIED" operation="connect" profile="/usr/lib/lightdm/lightdm-guest-session" pid=2129 comm="dbus-send" family="unix" sock_type="stream" protocol=0 requested_mask="send receive accept" denied_mask="send accept" addr="@/com/ubuntu/upstart-session/996/1720" peer_addr=none peer="unconfined" test@test-Standard-PC-i440FX-PIIX-1996:~$ ** This bug has been marked a duplicate of bug 1627304 User locking problems - guest login crashing -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1627310 Title: Guest session fails to log out Status in lightdm package in Ubuntu: Confirmed Status in xfce4-session package in Ubuntu: Confirmed Bug description: Vanilla Xubuntu install. When logging out from the guest session, everything is closed and the desktop wallpaper is the only thing that remains. The user is never returned to the login screen. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xfce4-session 4.12.1-3ubuntu2 ProcVersionSignature: Ubuntu 4.8.0-11.12-generic 4.8.0-rc6 Uname: Linux 4.8.0-11-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CurrentDesktop: XFCE Date: Sat Sep 24 09:18:31 2016 InstallationDate: Installed on 2016-09-24 (0 days ago) InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160921) SourcePackage: xfce4-session UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CurrentDesktop: XFCE DistroRelease: Ubuntu 16.10 InstallationDate: Installed on 2016-09-24 (0 days ago) InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160921) Package: ligh
[Desktop-packages] [Bug 1618886] Re: unity-gtk-module.service is racy; session services don't stop if session terminates
This isn't quite enough in this situation. - Log in over SSH or in a vt (so there is a logind session alive for your user) - Log into the same user in Unity - Simulate an Xorg crash (pkill -f -SEGV Xorg) - Log back in You don't have GTK_MODULES set properly. The previous gnome-session is lingering. To fix that, something like comment #3 is needed. Such as looping over all 'active' units that are PartOf graphical-session.target and stopping them all. gnome-session needs a fix to its ExecStopPost to not kill the one we just started. I'll upload this and it can be reviewed in the queue. ** Changed in: gnome-session (Ubuntu) Status: Fix Released => Triaged ** Changed in: gnome-session (Ubuntu) Importance: Undecided => High ** Changed in: upstart (Ubuntu) Status: Fix Released => Triaged ** Changed in: upstart (Ubuntu) Importance: Undecided => Medium ** Changed in: gnome-session (Ubuntu) Importance: High => Medium ** Changed in: gnome-session (Ubuntu) Assignee: Martin Pitt (pitti) => Iain Lane (laney) ** Changed in: upstart (Ubuntu) Assignee: Martin Pitt (pitti) => Iain Lane (laney) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1618886 Title: unity-gtk-module.service is racy; session services don't stop if session terminates Status in gnome-session package in Ubuntu: Triaged Status in unity-gtk-module package in Ubuntu: Fix Released Status in upstart package in Ubuntu: Triaged Bug description: Sometimes on session start unity-gtk-module.service runs too late or something, and $GTK_MODULES does not include "unity". It is in "systemctl --user show-environment" but not in a terminal bash. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1618886/+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 1278437] Re: can't move link type .desktop files around on desktop
Still having this issue on 16.04 -- 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/1278437 Title: can't move link type .desktop files around on desktop Status in Nautilus: Fix Released Status in nautilus package in Ubuntu: Fix Released Status in nautilus source package in Xenial: Triaged Bug description: * Impact links can't be moved on the desktop * Test case Save the following as e.g. test.desktop in your ~/Desktop folder and try to move it around on the desktop: [Desktop Entry] Version=1.0 Type=Link Name=test URL=https://launchpad.net/index.html * Regression potential Dnd should keep working -- If I have a .desktop file with Type=Link on my desktop and try to move it around it doesn't stay where I drop it but goes back where it was before and tries to download the URL it is referring to instead. Save the following as e.g. test.desktop in your ~/Desktop folder and try to move it around on the desktop: [Desktop Entry] Version=1.0 Type=Link Name=test URL=https://launchpad.net/index.html This affects at least 13.10 and 14.04. In 13.10 Nautilus crashes if the URL as a file:// URL referring to a file on your desktop. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: nautilus 1:3.10.1-0ubuntu3 ProcVersionSignature: Ubuntu 3.13.0-7.26-generic 3.13.1 Uname: Linux 3.13.0-7-generic i686 ApportVersion: 2.13.2-0ubuntu2 Architecture: i386 CurrentDesktop: Unity Date: Mon Feb 10 14:06:24 2014 GsettingsChanges: InstallationDate: Installed on 2013-10-11 (122 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Beta i386 (20130925.1) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/zsh SourcePackage: nautilus UpgradeStatus: Upgraded to trusty on 2013-12-07 (64 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1278437/+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 1573959] Re: On-screen text disappears after suspend
Similar bug for me too, with i915 driver but on HP Envy 6-1260sf (Core i5-337U) with Xubuntu. In the list of affected applications, we can add Thunar, xfce4-panel and whisker (xfce menu). Switching to VT-1 does NOT work for me, same for reloading xfwm4. So Xubuntu desktop is unusable when the bug happens, and it is very hard to save work in progress because all browsing dialog are also affected. Loggout/loggin restore the font display, but all current unsaved documents are lost. The bug is only present after some suspend/resume but not always. Hardware description : root@draco-ultrabook:~# lshw -sanitize -numeric -C display *-display description: VGA compatible controller produit: 3rd Gen Core processor Graphics Controller [8086:166] fabriquant: Intel Corporation [8086] identifiant matériel: 2 information bus: pci@:00:02.0 version: 09 bits: 64 bits horloge: 33MHz fonctionnalités: msi pm vga_controller bus_master cap_list rom configuration: driver=i915 latency=0 ressources: irq:30 mémoire:c000-c03f mémoire:b000-bfff portE/S:3000(taille=64) root@draco-ultrabook:~# lspci -vvnn -d 8086:0166 00:02.0 VGA compatible controller [0300]: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company 3rd Gen Core processor Graphics Controller [103c:1896] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- [disabled] Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit- Address: fee00018 Data: Capabilities: [d0] Power Management version 2 Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- Capabilities: [a4] PCI Advanced Features AFCap: TP+ FLR+ AFCtrl: FLR- AFStatus: TP- Kernel driver in use: i915 Kernel modules: i915 ** Attachment added: "Corrupted screen on resume from S3 on Xubuntu 16.04" https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1573959/+attachment/4749385/+files/Capture%20d%E2%80%99%C3%A9cran_2016-09-27_07-33-28.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1573959 Title: On-screen text disappears after suspend Status in xserver-xorg-video-intel package in Ubuntu: Confirmed Bug description: After resuming from a suspend, almost all text on screen is not visible. This includes menu items, text in all three boxes (list of folders, list of e-mails, e-mail body) in Thunderbird (with the curious exception of "ffl" in the File menu), top menu in Chromium (but not the menu obtained by pressing the hamburger button), and the menus produced by clicking items in the system tray. Also, the apport dialog had no text except for a few capital letters. ADDITIONAL INFORMATION: * initctl restart unity-panel-service restarts the panel, but the text is still missing * suspend and resume does not fix the issue * Logging out fixes the issue * Other affected applications: ** Chromium file select dialog ** Terminal (entire window) ** ttys 1-6 (Ctrl+Alt+F1, etc.) ** Document viewer (menus) ** Software Updater ** Rhythmbox ** The dialog that appears when you take a screenshot with Ctrl+Alt+PrtSc ** ubuntu-bug ** Nautilus ** LibreOffice Calc (spreadsheet text contents) ** Firefox * Unity dash is not affected. * Skype is not affected. * Mousing over a button in a dialog correctly shows the text. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: unity 7.4.0+16.04.20160415-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 BootLog: CompizPlugins: [core,bailer,detection,composite,opengl,compiztoolbox,decor,gnomecompat,imgpng,place,move,resize,vpswitch,snap,regex,grid,mousepoll,unitymtgrabhandles,animation,session,wall,workarounds,expo,fade,ezoom,scale,unityshell] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sat Apr 23 12:04:57 2016 DistUpgraded: 2016-04-22 09:22:44,147 DEBUG icon theme changed, re-reading DistroCodename: xenial DistroVariant: ubuntu EcryptfsInUse: Yes GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09) (prog-if 00 [VGA controller]) Subsystem: COMPAL Electronics Inc Haswell-ULT Integrated Graphics C
[Desktop-packages] [Bug 1536353] Re: [Regression] Epson's printer driver packages cannot be installed as lsb package is not available anymore
What is the problem? , its hardware or software problem?. Is it possible to use the scanner? Status shows "fix released" and Importance "medium". Confused -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups-filters in Ubuntu. https://bugs.launchpad.net/bugs/1536353 Title: [Regression] Epson's printer driver packages cannot be installed as lsb package is not available anymore Status in lsb: New Status in cups-filters package in Ubuntu: Fix Released Status in epson-inkjet-printer-escpr package in Ubuntu: Fix Released Status in lsb package in Ubuntu: Fix Released Status in cups-filters source package in Xenial: Fix Released Status in epson-inkjet-printer-escpr source package in Xenial: Fix Released Status in lsb source package in Xenial: Fix Released Bug description: [SRU justification] Previous releases were compatible with third-party printer drivers provided in LSB package format (and also as .deb packages depending on the lsb package). As of 16.04, because the LSB specifies ABIs for various libraries that are no longer supported in Ubuntu as obsolete, the packages for the lsb modules have been dropped in both Debian and Ubuntu. This includes dropping of lsb-core, which is the component which provides the LSB-mandated ELF loader path - without which no lsb executable will work. This SRU will restore the bare minimum of LSB compatibility necessary to support known third-party LSB printer driver packages on Ubuntu 16.04. [Regression potential] The reintroduced 'lsb' binary package is known to not fully satisfy the requirements for a complete LSB-compliant system. This is a regression vs. Ubuntu 14.04; so anyone using LSB packages on Ubuntu 14.04 who upgrades to Ubuntu 16.04 may have the upgrade succeed without any warning from the package manager. As there are very few lsb packages in use in the wild, this is considered an acceptable regression, especially as this will land before the first 16.04 point release. [Test case] 1. Download the epsion 201106w printer driver package from http://download.ebz.epson.net/dsc/op/stable/debian/dists/lsb3.2/main/binary-amd64/epson-inkjet-printer-201106w_1.0.1-1lsb3.2_amd64.deb 2. Install the package and confirm that its dependencies are not satisfiable. 3. Enable xenial-proposed. 4. Install the package again and confirm that the dependencies are satisfied. 5. Verify that /opt/epson-inkjet-printer-201106w/cups/lib/filter/epson_inkjet_printer_filter can be run without errors about missing lsb ld.so or missing libraries. Starting with Xenial, lsb compatibility packages were dropped (besides lsb-release and lsb-base): lsb (9.20150826) unstable; urgency=low * Drop all the LSB compatibility packages besides lsb-release and lsb-base - Drop packages-availability checking in lsb-release - Truncate README.Debian to a minimum - Document this in lsb-base.NEWS.Debian * Change the versioning number to avoid any ambiguity; use joeyh's version.date, with version being Debian next stable's -- Didier Raboud Wed, 26 Aug 2015 12:00:00 +0200 The problem is that downloadable printer drivers (like the ones from Openprinting, but also from other available providers) that are suggested when installing a printer on Ubuntu depends on lsb, which is not available anymore: epson-inkjet-printer-201106w: Dépend: lsb (>=3.2) but it is not installable This triggers a regression where it is not possible to setup a printer this way (downloading a driver where no local driver is available) anymore. I see two possible solutions: - Add a proper replaces field to one of the remaining lsb-* packages, to hopefully fix missing lsb package (maybe it would be useful to also replace other compability packages that are not built anymore). - Re-introduce LSB compatibility packages, but that might be an overkill. To manage notifications about this bug go to: https://bugs.launchpad.net/lsb/+bug/1536353/+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 1628198] [NEW] No communcation with graphics card
Public bug reported: Resolution incorrect. Appears to be using on-board graphics. Hardware was working perfectly before with older distros. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16 Uname: Linux 4.4.0-36-generic x86_64 .tmp.unity_support_test.1: ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 BootLog: * Setting up X socket directories... [80G [74G[ OK ] Running 0dns-down to make sure resolv.conf is ok...done. CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Tue Sep 27 23:24:21 2016 DistUpgraded: 2016-08-11 02:26:50,924 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (Failed to execute child process "./xorg_fix_proprietary.py" (No such file or directory)) DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.4.0-34-generic, x86_64: installed nvidia-340, 340.96, 4.4.0-34-generic, x86_64: installed DpkgLog: ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GT218 [GeForce 210] [10de:0a65] (rev a2) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GT218 [GeForce 210] [1043:848e] InstallationDate: Installed on 2015-01-16 (620 days ago) InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64 (20130820.1) MachineType: HP-Pavilion KY789AA-AKL p6175l ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-36-generic root=UUID=495ee15a-c5aa-43dc-80a3-f5133ad56d59 ro quiet drm.debug=0xe plymouth:debug splash vesafb.invalid=1 Renderer: Software SourcePackage: xorg UpgradeStatus: Upgraded to xenial on 2016-08-10 (47 days ago) dmi.bios.date: 05/07/2009 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: 5.22 dmi.board.name: Boston dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr5.22:bd05/07/2009:svnHP-Pavilion:pnKY789AA-AKLp6175l:pvr:rvnMSI:rnBoston:rvr1.0:cvnHewlett-Packard:ct3:cvr: dmi.product.name: KY789AA-AKL p6175l dmi.sys.vendor: HP-Pavilion version.compiz: compiz 1:0.9.12.2+16.04.20160714-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.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Tue Sep 27 23:21:10 2016 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputLogitech USB Receiver KEYBOARD, id 8 inputLogitech USB Receiver KEYBOARD, id 9 xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.18.3-1ubuntu2.3 ** 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/1628198 Title: No communcation with graphics card Status in xorg package in Ubuntu: New Bug description: Resolution incorrect. Appears to be using on-board graphics. Hardware was working perfectly before with older distros. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16 Uname: Linux 4.4.0-36-generic x86_64 .tmp.unity_support_test.1: ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 BootLog: * Setting up X socket directories... [80G [74G[ OK ] Running 0dns-down to make sure resolv.conf is ok...done. CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Tue Sep 27 23:24:21 2016 DistUpgraded: 2016-08-11 02:26:50,924 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (Failed to execute child process "./xorg_fix_proprietary.py" (No such file or directory)) DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.4.0-34-generic, x86_64: installed nvidia-340, 340.96, 4.4.0-34-generic, x86_64: installed DpkgLog:
[Desktop-packages] [Bug 1606144] Re: [Precision 5510, Realtek ALC3266, Black Headphone Out, Left] No sound at all
I am having the same issue with Dell Precision 5510 on Ubuntu 16.04. I've also tried the 4.6.7 and 4.7.5 kernel and it is also not working. -- 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/1606144 Title: [Precision 5510, Realtek ALC3266, Black Headphone Out, Left] No sound at all Status in alsa-driver package in Ubuntu: New Bug description: Sound works on laptop speakers, but there is no sound coming from the headphones jack. The laptop keeps playing from its own speakers instead of using the headphones I've plugged in. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 Uname: Linux 4.4.8-040408-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0c: stian 4028 F...m pulseaudio /dev/snd/controlC0: stian 4028 F pulseaudio CurrentDesktop: Unity Date: Mon Jul 25 10:03:23 2016 InstallationDate: Installed on 2016-06-02 (52 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0c: stian 4028 F...m pulseaudio /dev/snd/controlC0: stian 4028 F pulseaudio Symptom_Jack: Black Headphone Out, Left Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: No sound at all Title: [Precision 5510, Realtek ALC3266, Black Headphone Out, Left] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/07/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.02.00 dmi.board.name: 0N8J4R dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnPrecision5510:pvr:rvnDellInc.:rn0N8J4R:rvrA01:cvnDellInc.:ct9:cvr: dmi.product.name: Precision 5510 dmi.sys.vendor: Dell Inc. mtime.conffile..etc.modprobe.d.alsa-base.conf: 2016-07-25T10:01:11.561836 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1606144/+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 1627903] Re: Can't select .pem file for TLS auth for 802.1X authentication
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: network-manager-applet (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/1627903 Title: Can't select .pem file for TLS auth for 802.1X authentication Status in network-manager-applet package in Ubuntu: Confirmed Bug description: Users cannot select .pem key files of TLS certificate when connecting to a network that requires TLS type 802.1X authentication This is the follow-up report of Bug #1575614, which fixes the p12 files but not some cases for .pem files. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1627903/+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 1628039] Re: ubufox makes Electrolysis stopped.
Already reported: https://launchpad.net/bugs/1627290 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubufox in Ubuntu. https://bugs.launchpad.net/bugs/1628039 Title: ubufox makes Electrolysis stopped. Status in ubufox package in Ubuntu: New Bug description: Firefox has a new feature https://wiki.mozilla.org/Electrolysis. (abbr. e10s) ubufox makes e10s stopped. xul-ext-ubufox is installed by default so it affects all Ubuntu users. xul-ext-ubufox 3.2-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubufox/+bug/1628039/+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 1628133] [NEW] lubuntu beta2 alternate install fails with: "lubuntu-core : Depends: xserver-xorg-input-all but it is not going to be installed"
You have been subscribed to a public bug: Beta installs fail in the middle with: lubuntu-core : Depends: xserver-xorg-input-all but it is not going to be installed ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: iso-testing -- lubuntu beta2 alternate install fails with: "lubuntu-core : Depends: xserver-xorg-input-all but it is not going to be installed" https://bugs.launchpad.net/bugs/1628133 You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg 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 1628039] Re: ubufox makes Electrolysis stopped.
*** This bug is a duplicate of bug 1627290 *** https://bugs.launchpad.net/bugs/1627290 Thx ** This bug has been marked a duplicate of bug 1627290 Firefox 49+ multiprocess windows feature (e10s) is disabled by ubufox -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubufox in Ubuntu. https://bugs.launchpad.net/bugs/1628039 Title: ubufox makes Electrolysis stopped. Status in ubufox package in Ubuntu: New Bug description: Firefox has a new feature https://wiki.mozilla.org/Electrolysis. (abbr. e10s) ubufox makes e10s stopped. xul-ext-ubufox is installed by default so it affects all Ubuntu users. xul-ext-ubufox 3.2-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubufox/+bug/1628039/+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 1628133] Re: lubuntu beta2 alternate install fails with: "lubuntu-core : Depends: xserver-xorg-input-all but it is not going to be installed"
My fault. xserver-xorg-input-vmmouse was removed from Debian as obsolete, and I missed that -input-all still depended on it. Fixing. ** Package changed: lubuntu-meta (Ubuntu) => xorg (Ubuntu) -- 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/1628133 Title: lubuntu beta2 alternate install fails with: "lubuntu-core : Depends: xserver-xorg-input-all but it is not going to be installed" Status in xorg package in Ubuntu: Fix Released Bug description: Beta installs fail in the middle with: lubuntu-core : Depends: xserver-xorg-input-all but it is not going to be installed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1628133/+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 1628133] Re: lubuntu beta2 alternate install fails with: "lubuntu-core : Depends: xserver-xorg-input-all but it is not going to be installed"
fix uploaded, but forgot to include the bug reference. ** Changed in: xorg (Ubuntu) Status: New => Fix Released -- 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/1628133 Title: lubuntu beta2 alternate install fails with: "lubuntu-core : Depends: xserver-xorg-input-all but it is not going to be installed" Status in xorg package in Ubuntu: Fix Released Bug description: Beta installs fail in the middle with: lubuntu-core : Depends: xserver-xorg-input-all but it is not going to be installed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1628133/+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 1620661] Re: GNOME Contacts maps no longer work
Is there any way we can get that fix for Xenial as SRU? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-contacts in Ubuntu. https://bugs.launchpad.net/bugs/1620661 Title: GNOME Contacts maps no longer work Status in gnome-contacts: New Status in gnome-contacts package in Ubuntu: Fix Released Status in libchamplain package in Ubuntu: Fix Released Status in gnome-contacts source package in Xenial: Triaged Status in libchamplain source package in Xenial: Triaged Bug description: HOW TO REPRODUCE: 1. In GNOME Contacts, create a contact with address information. 2. Close GNOME Contacts. 3. Reopen GNOME Contacts, and look for the new contact. RESULT: Where it should be a map, there is a message saying that the mapping service has been discontinued (http://tinyurl.com/jbupetb) ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gnome-contacts 3.18.1-1ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16 Uname: Linux 4.4.0-36-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity Date: Tue Sep 6 16:53:00 2016 InstallationDate: Installed on 2013-01-25 (1319 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) SourcePackage: gnome-contacts UpgradeStatus: Upgraded to xenial on 2016-08-05 (31 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-contacts/+bug/1620661/+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 1620661] Re: GNOME Contacts maps no longer work
@ Khurshid Alam As said in (https://bugzilla.gnome.org/show_bug.cgi?id=769372), upgrading libchamplain to version 0.12.14 will be the appropriate step to take. ** Changed in: libchamplain (Ubuntu Xenial) Importance: Low => High ** Changed in: libchamplain (Ubuntu) Importance: Low => High ** Changed in: gnome-contacts (Ubuntu) Status: Fix Released => Invalid ** Changed in: gnome-contacts (Ubuntu Xenial) Status: Triaged => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-contacts in Ubuntu. https://bugs.launchpad.net/bugs/1620661 Title: GNOME Contacts maps no longer work Status in gnome-contacts: New Status in gnome-contacts package in Ubuntu: Invalid Status in libchamplain package in Ubuntu: Fix Released Status in gnome-contacts source package in Xenial: Invalid Status in libchamplain source package in Xenial: Triaged Bug description: HOW TO REPRODUCE: 1. In GNOME Contacts, create a contact with address information. 2. Close GNOME Contacts. 3. Reopen GNOME Contacts, and look for the new contact. RESULT: Where it should be a map, there is a message saying that the mapping service has been discontinued (http://tinyurl.com/jbupetb) ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gnome-contacts 3.18.1-1ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16 Uname: Linux 4.4.0-36-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity Date: Tue Sep 6 16:53:00 2016 InstallationDate: Installed on 2013-01-25 (1319 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) SourcePackage: gnome-contacts UpgradeStatus: Upgraded to xenial on 2016-08-05 (31 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-contacts/+bug/1620661/+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 1613720] Re: Display arrangement settings are reset after reboot
> The MonitorsUser.xml.txt from the bug suggests your stored config has cloned monitors in 1280x720, is that the correct or the buggy config? Can you try to move ~/.config/monitors.xml away, reconfigure your monitor using system settings and see what config is written in that file/add it to the bug? I would like to use 1366x768 for the laptop display and 1680x1050 for the external monitor which should the to the left of the laptop display. Removing `~/.config/monitors.xml` causes the desired (= maximal) values to be picked as default after reboot, but the arrangement of monitors isn't persisted. Saving the configuration in the display arrangement/resolution dialog doesn't create `~/.config/monitors.xml`. That the file isn't created or overwritten is probably the reason for the behaviour. I don't find `MonitorsUser.xml` with `locate`, so I naively assume that it doesn't exist on the system neither. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1613720 Title: Display arrangement settings are reset after reboot Status in unity-settings-daemon package in Ubuntu: Incomplete Bug description: Display arrangement settings are reset after reboot. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: unity 7.4.0+16.04.20160715-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15 Uname: Linux 4.4.0-34-generic x86_64 NonfreeKernelModules: openafs zfs zunicode zcommon znvpair zavl .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CompizPlugins: »/apps/compiz-1/general/screen0/options/active_plugins« wurde kein Wert zugewiesen CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Tue Aug 16 15:28:45 2016 DistUpgraded: 2016-03-14 15:43:39,246 DEBUG enabling apt cron job DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:3904] InstallationDate: Installed on 2015-12-12 (248 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: LENOVO 20221 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-34-generic root=UUID=791b47e7-915d-4d5a-bce0-d7e9b660a2ab ro rootflags=subvol=ubuntu-main-root SourcePackage: unity UpgradeStatus: Upgraded to xenial on 2016-03-14 (154 days ago) dmi.bios.date: 07/12/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 71CN51WW(V1.21) dmi.board.asset.tag: No Asset Tag dmi.board.name: INVALID dmi.board.vendor: LENOVO dmi.board.version: 3193WIN8 STD MLT dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo IdeaPad Z500 Touch dmi.modalias: dmi:bvnLENOVO:bvr71CN51WW(V1.21):bd07/12/2013:svnLENOVO:pn20221:pvrLenovoIdeaPadZ500Touch:rvnLENOVO:rnINVALID:rvr3193WIN8STDMLT:cvnLENOVO:ct10:cvrLenovoIdeaPadZ500Touch: dmi.product.name: 20221 dmi.product.version: Lenovo IdeaPad Z500 Touch dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12.2+16.04.20160714-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Tue Aug 16 15:22:31 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id5557 vendor CMN xserver.version: 2:1.18.3-1ubuntu2.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1613720/+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 1555569] Re: [snaps] Show human-readable names for store apps
** No longer affects: click-reviewers-tools
--
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/169
Title:
[snaps] Show human-readable names for store apps
Status in Snappy:
New
Status in Software Center Agent:
Fix Released
Status in gnome-software package in Ubuntu:
Triaged
Bug description:
GNOME Software shows the package name from the app (the snap's name
you can't change in the store) instead of the human-readable one (the
one you can edit in the store).
That is, the entry in GNOME Software reads 'ubuntu-calculator-app'
instead of 'Calculator (Unity 7)'. The latter is specified as "Package
title" in the web UI, not sure which field name it's got in the store
API.
It seems, though, that snappy does not have the concept of a human-
readable name and it's using the "description" field for that. I'm not
sure if that's the intention, or if it's expected that any store
clients use the "Package title" from the store API instead.
snapd gives the following information for ubuntu-calculator-app (in this
case, sideloaded):
{
"description" : "Ubuntu Calculator app",
"download_size" : -1,
"icon" : "/2.0/icons/ubuntu-calculator-app.sideload/icon",
"installed_size" : 581341041,
"name" : "ubuntu-calculator-app",
"origin" : "sideload",
"resource" : "/2.0/snaps/ubuntu-calculator-app.sideload",
"status" : "active",
"type" : "app",
vendor" : "",
"version" : "IOBXFFOCRcXL"
}
From James Tait:
The human-readable package display name, “Package name” in the upload
form, maps to the title field in the store API and takes its data from
the same field in a Click manifest, but seemingly has no equivalent in
a Snap manifest. The closest field in snap.yaml appears to be summary,
but I was intending to extract that to tagline and fix bug #1303354 so
we can surface that in the store API.
The description field in the store API maps to the “Tagline” and
“Description” fields in the upload form, and takes its data from the
title and description fields in Click manifests, and the description
field in Snap manifests.
The name field in the store API maps to the unchangeable package name
in the store web UI, and takes its data from the same field in both
Click and Snap manifests, with the author’s short namespace appended
if the extracted package name is unqualified.
To manage notifications about this bug go to:
https://bugs.launchpad.net/snappy/+bug/169/+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 1609898] Re: dhclient incorrectly assumes a /64 ipv6 prefix
http://autopkgtest.ubuntu.com/packages/n/network-manager succeeds again on xenial, thus verified. ** Tags removed: verification-done-precise verification-done-trusty verification-done-xenial verification-done-yakkety verification-needed ** Tags added: verification-done -- 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/1609898 Title: dhclient incorrectly assumes a /64 ipv6 prefix Status in isc-dhcp package in Ubuntu: Fix Committed Status in network-manager package in Ubuntu: Fix Committed Status in isc-dhcp source package in Precise: Fix Released Status in network-manager source package in Precise: Invalid Status in isc-dhcp source package in Trusty: Fix Released Status in network-manager source package in Trusty: Triaged Status in isc-dhcp source package in Xenial: Fix Released Status in network-manager source package in Xenial: Fix Committed Status in isc-dhcp source package in Yakkety: Fix Committed Status in network-manager source package in Yakkety: Fix Committed Status in isc-dhcp package in Debian: Fix Released Bug description: [Impact] clients who get an ipv6 address from a dhcpv6 server assume the address has a /64 prefix, but that is not necessarily true, and if the subnet is different than /64 those clients will not be able to reach other addresses in that /64 prefix because the other systems are not on-link. This /64 assumption of dhclient effectively breaks the client networking for certain addresses. [Test Case] Set up a server with two interface nics, and one client connected to each of those interfaces. On the server, set up a ipv6 subnet on each interface, with a larger prefix than /64, e.g.: 2001:db8:0:0:1::/96 2001:db8:0:0:2::/96 configure dhcpv6 on the server, to provide ipv6 addresses on each interface. Set the server as the default ipv6 route for the clients. Allow the clients to get dhcpv6 ipv6 addresses from the server. The clients will each get a ipv6 address with a /64 prefix, due to the bug in dhclient. Try to ping (or otherwise communicate) between the clients. Since they have /64 prefixes, they think they are on-link with each other, but they are not, so they can't communicate. After the dhclient bug is fixed, repeat the above setup, and the clients will get /128 prefixes instead, and then will be able to communicate with each other, because they will route the traffic to each other through the server. [Regression Potential] Non-standard (i.e. not /64) subnets served by dhcpv6 currently are broken, this fixes that. However, any ipv6 network configurations that rely on the previous incorrect assumed /64 behavior (as described here: https://tools.ietf.org/html/rfc5942#section-5) in order to allow dhcpv6 clients to communicate with other systems inside the subnet, but do not use RA to also provide clients with the actual prefix len, will break. To clarify: a server that provides clients with dhcpv6 addresses, but does not also provide the prefix len via RA, will change behavior; previously, all clients on the subnet could talk directly to each other, with this update the clients cannot talk to each other directly; all traffic between clients will be routed through the default gateway. Further, if the network does not provide a default gateway - for example a local network that is intended only for traffic between local servers - the clients will not be able to talk to each other at all. Note that such configurations *are* broken configurations, that just happened to work before because of incorrect dhcp client behavior; such configurations must be updated to perform RA to provide the prefix len to clients. See comment 30 for details on how to configure radvd to restore network functionality. [Other Info] This is fixed in debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=684009 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1609898/+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 1627769] Re: limits.conf not applied
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: lightdm (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1627769 Title: limits.conf not applied Status in lightdm package in Ubuntu: Confirmed Bug description: Since upgraded to 16.10 Yakkety, modifications in /etc/security/limits.conf are not taken into consideration when logging in the graphical interface. /etc/security/limits.conf: @audio - rtprio 99 @audio - memlockunlimited I tried the same settings in /etc/security/limits.d/audio.conf, to the same results. After logging in Unity, opening a console, the limits are not set: blablack@ideaon:~$ ulimit -l -r max locked memory (kbytes, -l) 64 real-time priority (-r) 0 Reloging to my user via bash DOES apply the limits: blablack@ideaon:~$ ulimit -l -r max locked memory (kbytes, -l) 64 real-time priority (-r) 0 blablack@ideaon:~$ su blablack Password: blablack@ideaon:~$ ulimit -l -r max locked memory (kbytes, -l) unlimited real-time priority (-r) 95 Switching to a console (ctrl+alt+f1) and logging in would apply the limits as well. The exact same setup used to work fine on Xenial 16.04 before upgrade. If you need any more information, please let me know. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: lightdm 1.19.4-0ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-16.17-generic 4.8.0-rc7 Uname: Linux 4.8.0-16-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CurrentDesktop: Unity Date: Mon Sep 26 17:27:10 2016 SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1627769/+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 1508092] Re: [Asus 1011PX, Realtek ALC269VB, Speaker, Internal] no sound from speakers, only headphones
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: alsa-driver (Ubuntu) Status: New => Confirmed -- 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/1508092 Title: [Asus 1011PX, Realtek ALC269VB, Speaker, Internal] no sound from speakers, only headphones Status in alsa-driver package in Ubuntu: Confirmed Bug description: Sound comes out of the headphones when I insert the jack, but does NOT come out of the speakers when I unplug it. This includes sound from any source, including aplay. This is a newly installed Lubuntu daily build (Lubuntu 15.10 "Wily Werewolf" - Alpha i386 20151017.1). If I go back to running from the Live USB install media, the sound works fine from the speakers OR the headphones, as expected. As suggested by https://help.ubuntu.com/community/SoundTroubleshootingProcedure I have tried: * killing and reloading pulseaudio and alsa-mixer * purging (.config/) .pulse/ then killing/reloading and rebooting * installing and reinstalling pavucontrol linux-sound-base alsa-base alsa-utils libasound2 In the installed version I notice that in Volume Control (pavucontrol) the output switches automatically between headphones and speaker when the jack is plugged and unplugged - as one would expect - and in alsamixer I can see the inactive device being muted automatically. However the speaker never issues any sound :( On the contrary in the live usb I notice that alsamixer leaves both outputs active (unmuted) and simply relies on the microswitch in the headphone jack to control whether the speaker can be heard or not. For reference I past the output of the FAILING test case's alsa- info.sh below and attach the output of the WORKING test case's alsa- info.sh ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic i686 ApportVersion: 2.19.1-0ubuntu2 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0c: elda 1480 F...m pulseaudio /dev/snd/pcmC0D0p: elda 1480 F...m pulseaudio /dev/snd/controlC0: elda 1480 F pulseaudio CurrentDesktop: LXDE Date: Tue Oct 20 16:36:58 2015 InstallationDate: Installed on 2015-10-19 (0 days ago) InstallationMedia: Lubuntu 15.10 "Wily Werewolf" - Alpha i386 (20151017.1) JournalErrors: No journal files were found. -- No entries -- PackageArchitecture: all SourcePackage: alsa-driver UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/06/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1301 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: 1015PE dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: x.xx dmi.chassis.asset.tag: 0x dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer INC. dmi.chassis.version: x.x dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1301:bd05/06/2011:svnASUSTeKComputerINC.:pn1011PX:pvrx.x:rvnASUSTeKComputerINC.:rn1015PE:rvrx.xx:cvnASUSTeKComputerINC.:ct10:cvrx.x: dmi.product.name: 1011PX dmi.product.version: x.x dmi.sys.vendor: ASUSTeK Computer INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1508092/+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 1609898] Re: dhclient incorrectly assumes a /64 ipv6 prefix
** Changed in: network-manager (Ubuntu Xenial) Importance: Undecided => Medium ** Changed in: network-manager (Ubuntu Trusty) Importance: Undecided => Medium -- 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/1609898 Title: dhclient incorrectly assumes a /64 ipv6 prefix Status in isc-dhcp package in Ubuntu: Fix Committed Status in network-manager package in Ubuntu: Fix Committed Status in isc-dhcp source package in Precise: Fix Released Status in network-manager source package in Precise: Invalid Status in isc-dhcp source package in Trusty: Fix Released Status in network-manager source package in Trusty: Triaged Status in isc-dhcp source package in Xenial: Fix Released Status in network-manager source package in Xenial: Fix Committed Status in isc-dhcp source package in Yakkety: Fix Committed Status in network-manager source package in Yakkety: Fix Committed Status in isc-dhcp package in Debian: Fix Released Bug description: [Impact] clients who get an ipv6 address from a dhcpv6 server assume the address has a /64 prefix, but that is not necessarily true, and if the subnet is different than /64 those clients will not be able to reach other addresses in that /64 prefix because the other systems are not on-link. This /64 assumption of dhclient effectively breaks the client networking for certain addresses. [Test Case] Set up a server with two interface nics, and one client connected to each of those interfaces. On the server, set up a ipv6 subnet on each interface, with a larger prefix than /64, e.g.: 2001:db8:0:0:1::/96 2001:db8:0:0:2::/96 configure dhcpv6 on the server, to provide ipv6 addresses on each interface. Set the server as the default ipv6 route for the clients. Allow the clients to get dhcpv6 ipv6 addresses from the server. The clients will each get a ipv6 address with a /64 prefix, due to the bug in dhclient. Try to ping (or otherwise communicate) between the clients. Since they have /64 prefixes, they think they are on-link with each other, but they are not, so they can't communicate. After the dhclient bug is fixed, repeat the above setup, and the clients will get /128 prefixes instead, and then will be able to communicate with each other, because they will route the traffic to each other through the server. [Regression Potential] Non-standard (i.e. not /64) subnets served by dhcpv6 currently are broken, this fixes that. However, any ipv6 network configurations that rely on the previous incorrect assumed /64 behavior (as described here: https://tools.ietf.org/html/rfc5942#section-5) in order to allow dhcpv6 clients to communicate with other systems inside the subnet, but do not use RA to also provide clients with the actual prefix len, will break. To clarify: a server that provides clients with dhcpv6 addresses, but does not also provide the prefix len via RA, will change behavior; previously, all clients on the subnet could talk directly to each other, with this update the clients cannot talk to each other directly; all traffic between clients will be routed through the default gateway. Further, if the network does not provide a default gateway - for example a local network that is intended only for traffic between local servers - the clients will not be able to talk to each other at all. Note that such configurations *are* broken configurations, that just happened to work before because of incorrect dhcp client behavior; such configurations must be updated to perform RA to provide the prefix len to clients. See comment 30 for details on how to configure radvd to restore network functionality. [Other Info] This is fixed in debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=684009 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1609898/+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 1359824] Re: libvisio-dev missing dependency on libicu-dev
** Changed in: libvisio (Debian) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libvisio in Ubuntu. https://bugs.launchpad.net/bugs/1359824 Title: libvisio-dev missing dependency on libicu-dev Status in Inkscape: Fix Released Status in libvisio package in Ubuntu: Triaged Status in libvisio package in Debian: Fix Released Bug description: pkg-config reports a missing dependency. Please add Depends: libicu- dev to debian/control to rectify this. $ pkg-config --cflags libvisio-0.1 Package icu-i18n was not found in the pkg-config search path. Perhaps you should add the directory containing `icu-i18n.pc' to the PKG_CONFIG_PATH environment variable Package 'icu-i18n', required by 'libvisio-0.1', not found To manage notifications about this bug go to: https://bugs.launchpad.net/inkscape/+bug/1359824/+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 1556459] Re: [Lenovo ThinkPad W530] Regression: cannot set up 3 display configuration any more (Optimus)
I am experiencing the same issue, using a Thinkpad W520, on 16.04. Two external monitors are connected via DVI. On boot, all three monitors are mirrored, and correctly show the Ubuntu log. After logging in, I get the same error messages: The selected configuration for displays could not be applied could not set the configuration for CRTC 64 and GDBus.Error:org.gtk.GDBus.UnmappedGError.Quark._gsd_2drr_2derror_2dquark.Code2: could not set the configuration for CRTC 64 One of the monitors is disabled. If I enable it using the Unity Settings app, the same error message show up. Tailing -f /var/log/Xorg.0.log while enabling the monitor reveals: [ 451.532] (II) intel(0): resizing framebuffer to 5440x1672 [ 451.582] Cannot do multiple crtcs without X server dirty tracking 2 interface [ 451.582] randr: failed to set shadow slave pixmap [ 451.582] (EE) NOUVEAU(G0): failed to set mode: No space left on device This appears to be the same bug as #1597437. It also seems to have been resolved in Fedora: https://bugzilla.redhat.com/show_bug.cgi?id=1307204. ** Bug watch added: Red Hat Bugzilla #1307204 https://bugzilla.redhat.com/show_bug.cgi?id=1307204 -- 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/1556459 Title: [Lenovo ThinkPad W530] Regression: cannot set up 3 display configuration any more (Optimus) Status in xorg package in Ubuntu: Triaged Bug description: I cannot set up the third monitor any more (it was working beginning of March 2016 with Ubuntu 16.04). The configuration with NVIDIA Optimus starts with builtin display (of Thinkpad W530) and one of (3K) monitors, the second monitor is detected, but not used. The unity configuration tool shows me two message boxes: "The selected configuration for displays could not be applied could not set the configuration for CRTC 64" and "Failed to apply configuration: %s GDBus.Error:org.gtk.GDBus.UnmappedGError.Quark._gsd_2drr_2derror_2dquark.Code2: could not set the configuration for CRTC 64 " The first one I have seen at boot time on login screen (with 3 displays) previously, the second one is new. The third monitor works if Optimus gets disabled in BIOS and the machine runs with Nvidia only ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-12.28-generic 4.4.4 Uname: Linux 4.4.0-12-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Sat Mar 12 18:44:54 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: virtualbox, 5.0.16, 4.4.0-10-generic, x86_64: installed virtualbox, 5.0.16, 4.4.0-11-generic, x86_64: installed virtualbox, 5.0.16, 4.4.0-12-generic, x86_64: installed EcryptfsInUse: Yes ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:21f5] NVIDIA Corporation GK107GLM [Quadro K2000M] [10de:0ffb] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo GK107GLM [Quadro K2000M] [17aa:21f5] InstallationDate: Installed on 2016-02-25 (15 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160225) MachineType: LENOVO 2447MU0 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-12-generic root=UUID=c01ceec8-4b0c-447f-af8f-3e9c4ae90e15 ro rootflags=subvol=@ quiet splash SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/18/2015 dmi.bios.vendor: LENOVO dmi.bios.version: G5ETA3WW (2.63 ) dmi.board.asset.tag: Not Available dmi.board.name: 2447MU0 dmi.board.vendor: LENOVO dmi.board.version: 0B98401 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG5ETA3WW(2.63):bd09/18/2015:svnLENOVO:pn2447MU0:pvrThinkPadW530:rvnLENOVO:rn2447MU0:rvr0B98401WIN:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2447MU0 dmi.product.version: ThinkPad W530 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12.2+16.04.20160209-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.1.2-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.1.2-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.1-1ubuntu4 vers
[Desktop-packages] [Bug 1628283] [NEW] xedid crashed with FileNotFoundError in list(): [Errno 2] No such file or directory: '/lib/firmware/edid'
Public bug reported: When launching xedid as is, it fail with the following stack : draco@draco-ultrabook:/lib/firmware$ xedid Traceback (most recent call last): File "/usr/bin/xedid", line 172, in for fw_edid in fw.list(): File "/usr/lib/python3/dist-packages/xdiagnose/edid.py", line 101, in list for filename in os.listdir(self.EDID_FIRMWARE_PATH): FileNotFoundError: [Errno 2] No such file or directory: '/lib/firmware/edid' If I create the directory /lib/firmware/edid, xedid do not crash anymore. So I expect the directory should be created when installing the xdiagnose package. Additional information: Xubuntu release : Description:Ubuntu 16.04.1 LTS Release:16.04 xdiagnose: Installé : 3.8.4.1 Candidat : 3.8.4.1 Table de version : *** 3.8.4.1 500 500 http://bouyguestelecom.ubuntu.lafibre.info/ubuntu xenial-updates/main amd64 Packages 500 http://bouyguestelecom.ubuntu.lafibre.info/ubuntu xenial-updates/main i386 Packages 100 /var/lib/dpkg/status 3.8.4 500 500 http://bouyguestelecom.ubuntu.lafibre.info/ubuntu xenial/main amd64 Packages 500 http://bouyguestelecom.ubuntu.lafibre.info/ubuntu xenial/main i386 Packages --- ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: XFCE DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2016-05-23 (126 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Package: xdiagnose 3.8.4.1 PackageArchitecture: all ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19 Tags: xenial Uname: Linux 4.4.0-38-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users _MarkForUpload: True ** Affects: xdiagnose (Ubuntu) Importance: Undecided Status: New ** Tags: apport-collected xenial ** Tags added: apport-collected xenial ** Description changed: When launching xedid as is, it fail with the following stack : draco@draco-ultrabook:/lib/firmware$ xedid Traceback (most recent call last): File "/usr/bin/xedid", line 172, in for fw_edid in fw.list(): File "/usr/lib/python3/dist-packages/xdiagnose/edid.py", line 101, in list for filename in os.listdir(self.EDID_FIRMWARE_PATH): FileNotFoundError: [Errno 2] No such file or directory: '/lib/firmware/edid' If I create the directory /lib/firmware/edid, xedid do not crash anymore. So I expect the directory should be created when installing the xdiagnose package. Additional information: Xubuntu release : Description: Ubuntu 16.04.1 LTS Release: 16.04 xdiagnose: Installé : 3.8.4.1 Candidat : 3.8.4.1 Table de version : *** 3.8.4.1 500 500 http://bouyguestelecom.ubuntu.lafibre.info/ubuntu xenial-updates/main amd64 Packages 500 http://bouyguestelecom.ubuntu.lafibre.info/ubuntu xenial-updates/main i386 Packages 100 /var/lib/dpkg/status 3.8.4 500 500 http://bouyguestelecom.ubuntu.lafibre.info/ubuntu xenial/main amd64 Packages 500 http://bouyguestelecom.ubuntu.lafibre.info/ubuntu xenial/main i386 Packages + --- + ApportVersion: 2.20.1-0ubuntu2.1 + Architecture: amd64 + CurrentDesktop: XFCE + DistroRelease: Ubuntu 16.04 + InstallationDate: Installed on 2016-05-23 (126 days ago) + InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) + Package: xdiagnose 3.8.4.1 + PackageArchitecture: all + ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19 + Tags: xenial + Uname: Linux 4.4.0-38-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users + _MarkForUpload: True -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdiagnose in Ubuntu. https://bugs.launchpad.net/bugs/1628283 Title: xedid crashed with FileNotFoundError in list(): [Errno 2] No such file or directory: '/lib/firmware/edid' Status in xdiagnose package in Ubuntu: New Bug description: When launching xedid as is, it fail with the following stack : draco@draco-ultrabook:/lib/firmware$ xedid Traceback (most recent call last): File "/usr/bin/xedid", line 172, in for fw_edid in fw.list(): File "/usr/lib/python3/dist-packages/xdiagnose/edid.py", line 101, in list for filename in os.listdir(self.EDID_FIRMWARE_PATH): FileNotFoundError: [Errno 2] No such file or directory: '/lib/firmware/edid' If I create the directory /lib/firmware/edid, xedid do not crash anymore. So I expect the directory should be created when installing the xdiagnose package. Additional information: Xubuntu release : Description: Ubuntu 16.04.1 LTS Release: 16.04 xdiagnose: Installé : 3.8.4.1 Candidat : 3.8.4.1 Table de version : *** 3.8.4.1 500 500 http://bouyguestelecom.ubuntu.lafibre.info
[Desktop-packages] [Bug 1628283] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1628283/+attachment/4749672/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdiagnose in Ubuntu. https://bugs.launchpad.net/bugs/1628283 Title: xedid crashed with FileNotFoundError in list(): [Errno 2] No such file or directory: '/lib/firmware/edid' Status in xdiagnose package in Ubuntu: New Bug description: When launching xedid as is, it fail with the following stack : draco@draco-ultrabook:/lib/firmware$ xedid Traceback (most recent call last): File "/usr/bin/xedid", line 172, in for fw_edid in fw.list(): File "/usr/lib/python3/dist-packages/xdiagnose/edid.py", line 101, in list for filename in os.listdir(self.EDID_FIRMWARE_PATH): FileNotFoundError: [Errno 2] No such file or directory: '/lib/firmware/edid' If I create the directory /lib/firmware/edid, xedid do not crash anymore. So I expect the directory should be created when installing the xdiagnose package. Additional information: Xubuntu release : Description: Ubuntu 16.04.1 LTS Release: 16.04 xdiagnose: Installé : 3.8.4.1 Candidat : 3.8.4.1 Table de version : *** 3.8.4.1 500 500 http://bouyguestelecom.ubuntu.lafibre.info/ubuntu xenial-updates/main amd64 Packages 500 http://bouyguestelecom.ubuntu.lafibre.info/ubuntu xenial-updates/main i386 Packages 100 /var/lib/dpkg/status 3.8.4 500 500 http://bouyguestelecom.ubuntu.lafibre.info/ubuntu xenial/main amd64 Packages 500 http://bouyguestelecom.ubuntu.lafibre.info/ubuntu xenial/main i386 Packages --- ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: XFCE DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2016-05-23 (126 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Package: xdiagnose 3.8.4.1 PackageArchitecture: all ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19 Tags: xenial Uname: Linux 4.4.0-38-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdiagnose/+bug/1628283/+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 1628283] Re: xedid crashed with FileNotFoundError in list(): [Errno 2] No such file or directory: '/lib/firmware/edid'
I don't know why apport-cli refuse to send the initial crash report, so here it is. ** Attachment added: "Apport crash report for xedid" https://bugs.launchpad.net/ubuntu/+source/xdiagnose/+bug/1628283/+attachment/4749673/+files/_usr_bin_xedid.1000.crash -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdiagnose in Ubuntu. https://bugs.launchpad.net/bugs/1628283 Title: xedid crashed with FileNotFoundError in list(): [Errno 2] No such file or directory: '/lib/firmware/edid' Status in xdiagnose package in Ubuntu: New Bug description: When launching xedid as is, it fail with the following stack : draco@draco-ultrabook:/lib/firmware$ xedid Traceback (most recent call last): File "/usr/bin/xedid", line 172, in for fw_edid in fw.list(): File "/usr/lib/python3/dist-packages/xdiagnose/edid.py", line 101, in list for filename in os.listdir(self.EDID_FIRMWARE_PATH): FileNotFoundError: [Errno 2] No such file or directory: '/lib/firmware/edid' If I create the directory /lib/firmware/edid, xedid do not crash anymore. So I expect the directory should be created when installing the xdiagnose package. Additional information: Xubuntu release : Description: Ubuntu 16.04.1 LTS Release: 16.04 xdiagnose: Installé : 3.8.4.1 Candidat : 3.8.4.1 Table de version : *** 3.8.4.1 500 500 http://bouyguestelecom.ubuntu.lafibre.info/ubuntu xenial-updates/main amd64 Packages 500 http://bouyguestelecom.ubuntu.lafibre.info/ubuntu xenial-updates/main i386 Packages 100 /var/lib/dpkg/status 3.8.4 500 500 http://bouyguestelecom.ubuntu.lafibre.info/ubuntu xenial/main amd64 Packages 500 http://bouyguestelecom.ubuntu.lafibre.info/ubuntu xenial/main i386 Packages --- ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: XFCE DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2016-05-23 (126 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Package: xdiagnose 3.8.4.1 PackageArchitecture: all ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19 Tags: xenial Uname: Linux 4.4.0-38-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdiagnose/+bug/1628283/+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 1628283] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1628283/+attachment/4749670/+files/Dependencies.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdiagnose in Ubuntu. https://bugs.launchpad.net/bugs/1628283 Title: xedid crashed with FileNotFoundError in list(): [Errno 2] No such file or directory: '/lib/firmware/edid' Status in xdiagnose package in Ubuntu: New Bug description: When launching xedid as is, it fail with the following stack : draco@draco-ultrabook:/lib/firmware$ xedid Traceback (most recent call last): File "/usr/bin/xedid", line 172, in for fw_edid in fw.list(): File "/usr/lib/python3/dist-packages/xdiagnose/edid.py", line 101, in list for filename in os.listdir(self.EDID_FIRMWARE_PATH): FileNotFoundError: [Errno 2] No such file or directory: '/lib/firmware/edid' If I create the directory /lib/firmware/edid, xedid do not crash anymore. So I expect the directory should be created when installing the xdiagnose package. Additional information: Xubuntu release : Description: Ubuntu 16.04.1 LTS Release: 16.04 xdiagnose: Installé : 3.8.4.1 Candidat : 3.8.4.1 Table de version : *** 3.8.4.1 500 500 http://bouyguestelecom.ubuntu.lafibre.info/ubuntu xenial-updates/main amd64 Packages 500 http://bouyguestelecom.ubuntu.lafibre.info/ubuntu xenial-updates/main i386 Packages 100 /var/lib/dpkg/status 3.8.4 500 500 http://bouyguestelecom.ubuntu.lafibre.info/ubuntu xenial/main amd64 Packages 500 http://bouyguestelecom.ubuntu.lafibre.info/ubuntu xenial/main i386 Packages --- ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: XFCE DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2016-05-23 (126 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Package: xdiagnose 3.8.4.1 PackageArchitecture: all ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19 Tags: xenial Uname: Linux 4.4.0-38-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdiagnose/+bug/1628283/+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 1628283] JournalErrors.txt
apport information ** Attachment added: "JournalErrors.txt" https://bugs.launchpad.net/bugs/1628283/+attachment/4749671/+files/JournalErrors.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdiagnose in Ubuntu. https://bugs.launchpad.net/bugs/1628283 Title: xedid crashed with FileNotFoundError in list(): [Errno 2] No such file or directory: '/lib/firmware/edid' Status in xdiagnose package in Ubuntu: New Bug description: When launching xedid as is, it fail with the following stack : draco@draco-ultrabook:/lib/firmware$ xedid Traceback (most recent call last): File "/usr/bin/xedid", line 172, in for fw_edid in fw.list(): File "/usr/lib/python3/dist-packages/xdiagnose/edid.py", line 101, in list for filename in os.listdir(self.EDID_FIRMWARE_PATH): FileNotFoundError: [Errno 2] No such file or directory: '/lib/firmware/edid' If I create the directory /lib/firmware/edid, xedid do not crash anymore. So I expect the directory should be created when installing the xdiagnose package. Additional information: Xubuntu release : Description: Ubuntu 16.04.1 LTS Release: 16.04 xdiagnose: Installé : 3.8.4.1 Candidat : 3.8.4.1 Table de version : *** 3.8.4.1 500 500 http://bouyguestelecom.ubuntu.lafibre.info/ubuntu xenial-updates/main amd64 Packages 500 http://bouyguestelecom.ubuntu.lafibre.info/ubuntu xenial-updates/main i386 Packages 100 /var/lib/dpkg/status 3.8.4 500 500 http://bouyguestelecom.ubuntu.lafibre.info/ubuntu xenial/main amd64 Packages 500 http://bouyguestelecom.ubuntu.lafibre.info/ubuntu xenial/main i386 Packages --- ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: XFCE DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2016-05-23 (126 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Package: xdiagnose 3.8.4.1 PackageArchitecture: all ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19 Tags: xenial Uname: Linux 4.4.0-38-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdiagnose/+bug/1628283/+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 1627007] Re: patch - fix reverse search in various terminal apps
Thank you! I made some changes to your debian/changelog entry. In particular, Ubuntu does not have NMUs because all Ubuntu packages are collectively maintained by Ubuntu contributors. And I added this bug number so that the bug will automatically be closed when the package arrives in yakkety. ** Changed in: vte2.91 (Ubuntu) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to vte2.91 in Ubuntu. https://bugs.launchpad.net/bugs/1627007 Title: patch - fix reverse search in various terminal apps Status in Gnome Virtual Terminal Emulator: Fix Released Status in vte2.91 package in Ubuntu: Fix Committed Bug description: [Impact] Due to a regression in vte2.91 0.44.0, reverse search was broken in various terminals like mate-terminal (GTK+3 build) or gnome-terminal. Searching with Ctrl-Shift-G could show you a result or two in the currently visible part of terminal log, but further searching (with scrolling the terminal upwards) stopped working completely. This wasn't fixed in version 0.44.2, so 0.44.2-1ubuntu2 in Ubuntu 16.10 still has this bug. The fix was recently applied upstream, and it would be good to have it backported to 16.10. The debdiff with the fix is in the attachment below. [Test Case] 1. Have Ubuntu 16.10 and mate-terminal or gnome-terminal. 2. Have a lot of text in your terminal window, enough to make the vertical scrollbar show. For example, you can build some package which is built with autotools. You'll get lots of occurrences of the same word, like 'make' or 'installing'. 3. Try searching for some word with reverse search. [Regression Potential] The code change in the patch only affects the search functionality, and that was already broken so you can't break it more. I've tested both forward and reverse search with the patch, and they both work fine now. I consider the regression risk to be quite low here. To manage notifications about this bug go to: https://bugs.launchpad.net/vte/+bug/1627007/+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 1625595] Re: Libre Office Icons unreadability on YY with Intel Drivers
found a work around. I removed libreoffice-kde and install libreoffice- gtk (which will also install libreoffice-gtk2). Launch libreoffice as normal and the icons and menus are working properly. I then uninstalled libreoffice-gtk and libreoffice-gtk2 and reinstalled libreoffice-kde which reproduced the problem in this bug report. Seems only libreoffice-kde is at fault. hope this helps and let me know if i can try anything else. -- 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/1625595 Title: Libre Office Icons unreadability on YY with Intel Drivers Status in libreoffice package in Ubuntu: Confirmed Bug description: glxinfo | grep -i vendor server glx vendor string: SGI client glx vendor string: Mesa Project and SGI Vendor: Intel Open Source Technology Center (0x8086) OpenGL vendor string: Intel Open Source Technology Center To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1625595/+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 1583088] Re: Randomly corrupt characters in Unity8
Screenshot on comment 12 seems very close to behaviour in bug #1573959 , which is present only on Intel graphic cards. Could it be the same bug ? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-desktop in Ubuntu. https://bugs.launchpad.net/bugs/1583088 Title: Randomly corrupt characters in Unity8 Status in Canonical System Image: New Status in gnome-desktop package in Ubuntu: Invalid Status in qtmir package in Ubuntu: Confirmed Status in unity8 package in Ubuntu: Confirmed Bug description: Corrupted characters in text rendering, mainly in Unity8 window titlebars. I think this is a new issue. It only started happening (on xenial desktop) in the past month or two. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1583088/+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 1628314] [NEW] Cups trouble shooter asked me to run a command that doesn't work
Public bug reported: The Cups trouble shooter claimed it couldn't find log files saying it was possible the it wasn't running as an administrator (which was correct). It asked me to run su -c 'journalctl -u cups.service --since="None" --until="2016-09-27 18:17:05"' > troubleshoot-logs.txt which failed for 2 reasons 1. I don't know the cups.service password (so I ran the command as root) 2. the None specification for "--since" is not valid Also the cups logs showed that cups couldn't create /var/spool/cups/tmp/.hplip but didn't say what caused the failure (turns out it already existed - shouldn't be an error!) ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: cups 2.1.3-4 ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19 Uname: Linux 4.4.0-38-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity Date: Tue Sep 27 18:41:10 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2015-05-31 (485 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0bda:57b5 Realtek Semiconductor Corp. Bus 001 Device 005: ID 03f0:0317 Hewlett-Packard LaserJet 1200 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. X551MA Papersize: letter ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-38-generic.efi.signed root=UUID=dadede94-9cd3-484a-963a-db3e27379a9b ro quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: Upgraded to xenial on 2016-08-04 (54 days ago) dmi.bios.date: 08/12/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X551MA.512 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X551MA 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.:bvrX551MA.512:bd08/12/2014:svnASUSTeKCOMPUTERINC.:pnX551MA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX551MA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: X551MA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. ** Affects: cups (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1628314 Title: Cups trouble shooter asked me to run a command that doesn't work Status in cups package in Ubuntu: New Bug description: The Cups trouble shooter claimed it couldn't find log files saying it was possible the it wasn't running as an administrator (which was correct). It asked me to run su -c 'journalctl -u cups.service --since="None" --until="2016-09-27 18:17:05"' > troubleshoot-logs.txt which failed for 2 reasons 1. I don't know the cups.service password (so I ran the command as root) 2. the None specification for "--since" is not valid Also the cups logs showed that cups couldn't create /var/spool/cups/tmp/.hplip but didn't say what caused the failure (turns out it already existed - shouldn't be an error!) ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: cups 2.1.3-4 ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19 Uname: Linux 4.4.0-38-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity Date: Tue Sep 27 18:41:10 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2015-05-31 (485 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0bda:57b5 Realtek Semiconductor Corp. Bus 001 Device 005: ID 03f0:0317 Hewlett-Packard LaserJet 1200 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. X551MA Papersize: letter ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-38-generic.efi.signed root=UUID=dadede94-9cd3-484a-963a-db3e27379a9b ro quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: Upgraded to xenial on 2016-08-04 (54 days ago) dmi.bios.date: 08/12/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X551MA.512 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X551MA 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.:bvrX551MA.512:bd08/12/2014:svnASUSTeKCOMPUTERINC.:pnX551MA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX551MA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: X551MA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.n
[Desktop-packages] [Bug 1572199] Re: cups 2.1.3-4 causes Lubuntu 16.04 to hang on shutdown
** Changed in: cups (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1572199 Title: cups 2.1.3-4 causes Lubuntu 16.04 to hang on shutdown Status in cups package in Ubuntu: Confirmed Bug description: cups 2.1.3-3 does not have this problem. Confirmed on 32 bit virtual and real machines. Problem was reported on VM. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: cups 2.1.3-4 ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6 Uname: Linux 4.4.0-15-generic i686 ApportVersion: 2.20-0ubuntu3 Architecture: i386 CasperVersion: 1.368 CupsErrorLog: CurrentDesktop: LXDE Date: Tue Apr 19 15:12:05 2016 LiveMediaBuild: Lubuntu 16.04 LTS "Xenial Xerus" - Beta i386 (20160323) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added. Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox Papersize: a4 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: file=/cdrom/preseed/username.seed boot=casper initrd=/casper/initrd.lz quiet splash --- SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1572199/+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 1612994] Re: firefox crashes constantly
** Changed in: firefox (Ubuntu) Importance: Undecided => High -- 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/1612994 Title: firefox crashes constantly Status in firefox package in Ubuntu: Confirmed Bug description: firefox crashes constantly firefox crashes constantly firefox crashes constantly firefox crashes constantly firefox crashes constantly ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: firefox 48.0+build2-0ubuntu0.16.04.1 ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15 Uname: Linux 4.4.0-34-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: wadilson 3834 F pulseaudio /dev/snd/controlC0: wadilson 3834 F pulseaudio /dev/snd/controlC2: wadilson 3834 F pulseaudio BrokenPermissions: datareporting/archived/2016-06/1465393881017.a684823d-a5e2-4f08-b88c-9355913c5035.main.jsonlz4 (0o600, wrong owner) datareporting/archived/2016-07/146953450.339095a1-d5c7-4bf3-adc2-59d4d4edcec5.main.jsonlz4 (0o600, wrong owner) datareporting/archived/2016-07/1469546217192.8ab4b38b-ef1e-4ba9-b51a-a38d9fda3697.main.jsonlz4 (0o600, wrong owner) saved-telemetry-pings/8ab4b38b-ef1e-4ba9-b51a-a38d9fda3697 (0o600, wrong owner) BuildID: 20160728203720 Channel: Unavailable CurrentDesktop: Unity Date: Sat Aug 13 18:32:21 2016 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2016-07-25 (18 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) IpRoute: default via 192.168.0.1 dev enp6s2 proto static metric 100 169.254.0.0/16 dev enp6s2 scope link metric 1000 192.168.0.0/24 dev enp6s2 proto kernel scope link src 192.168.0.100 metric 100 IwConfig: enp2s0no wireless extensions. lono wireless extensions. enp6s2no wireless extensions. Locales: extensions.sqlite corrupt or missing MostRecentCrashID: bp-6cf9c0b9-d679-4111-a8ed-3c25b2160813 Plugins: Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so PrefSources: prefs.js ProcEnviron: LANGUAGE=pt_BR: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pt_BR.UTF-8 SHELL=/bin/bash Profiles: Profile0 (Default) - LastVersion=48.0/20160728203720 (In use) RfKill: RunningIncompatibleAddons: False SourcePackage: firefox Themes: extensions.sqlite corrupt or missing UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/15/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0303 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P7H55-M LX dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0303:bd07/15/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP7H55-MLX:rvrX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1612994/+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 1607675] Re: Nautilus cann't access AirPort Time Capsule in Ubuntu 16.04
** Changed in: nautilus (Ubuntu)
Importance: Undecided => Medium
--
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/1607675
Title:
Nautilus cann't access AirPort Time Capsule in Ubuntu 16.04
Status in nautilus package in Ubuntu:
Confirmed
Bug description:
When connecting to my Time Capsule, I'll get an error
"kFPAuthContinue" from server.
While I can mount server with `mount.cifs`:
```
sudo mount.cifs \\10.0.1.1\${user_name} /mnt/ -o user=${user_name},sec=ntlm
```
According to `mount.cifs`'s manual, **the default was sec=ntlm in
mainline kernel version prior to v3.8, and has been changed to
sec=ntlmssp in kernel v3.8+**.
Maybe that's the reason why it works in Ubuntu 14.04 and fails in
Ubuntu 16.04.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1607675/+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 1591268] Re: package libcuda1-361 361.45.11-0ubuntu0.16.04.1 failed to install/upgrade: Unterprozess installiertes pre-removal-Skript gab den Fehlerwert 5 zurück - login loop
** Changed in: nvidia-graphics-drivers-361 (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-361 in Ubuntu. https://bugs.launchpad.net/bugs/1591268 Title: package libcuda1-361 361.45.11-0ubuntu0.16.04.1 failed to install/upgrade: Unterprozess installiertes pre-removal-Skript gab den Fehlerwert 5 zurück - login loop Status in nvidia-graphics-drivers-361 package in Ubuntu: Confirmed Bug description: This drives me crazy, because I even can't purge the libcuda1-361 or nvidia-opencl-icd-361 package from nvidia-361, which got me into a login loop... I am sure this is a duplicate of some other bug, but I didn't find it yet. At least I've got my login back, after disabling my user's dconf configuration: sudo mv ~/.config/dconf/user ~/.config/dconf/user.old How can I get rid of nvidia-361? $ sudo apt purge nvidia-opencl-icd-361 Paketlisten werden gelesen... Fertig Abhängigkeitsbaum wird aufgebaut. Statusinformationen werden eingelesen Fertig Die folgenden Pakete werden ENTFERNT: nvidia-opencl-icd-361* 0 aktualisiert, 0 neu installiert, 1 zu entfernen und 0 nicht aktualisiert. Nach dieser Operation werden 35,6 MB Plattenplatz freigegeben. Möchten Sie fortfahren? [J/n] (Lese Datenbank ... 256069 Dateien und Verzeichnisse sind derzeit installiert.) Entfernen von nvidia-opencl-icd-361 (361.45.11-0ubuntu0.16.04.1) ... Failed to stop var-lib-snapd-lib-gl.mount: Unit var-lib-snapd-lib-gl.mount not loaded. dpkg: Fehler beim Bearbeiten des Paketes nvidia-opencl-icd-361 (--purge): Unterprozess installiertes pre-removal-Skript gab den Fehlerwert 5 zurück Failed to get unit file state for var-lib-snapd-lib-gl.mount: No such file or directory var-lib-snapd-lib-gl.mount is a disabled or a static unit, not starting it. Trigger für libc-bin (2.23-0ubuntu3) werden verarbeitet ... Fehler traten auf beim Bearbeiten von: nvidia-opencl-icd-361 E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libcuda1-361 361.45.11-0ubuntu0.16.04.1 ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10 Uname: Linux 4.4.0-24-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Fri Jun 10 17:58:34 2016 Dependencies: gcc-6-base 6.0.1-0ubuntu1 libc6 2.23-0ubuntu3 libgcc1 1:6.0.1-0ubuntu1 DpkgTerminalLog: Entfernen von libcuda1-361 (361.45.11-0ubuntu0.16.04.1) ... Failed to stop var-lib-snapd-lib-gl.mount: Unit var-lib-snapd-lib-gl.mount not loaded. dpkg: Fehler beim Bearbeiten des Paketes libcuda1-361 (--remove): Unterprozess installiertes pre-removal-Skript gab den Fehlerwert 5 zurück ErrorMessage: Unterprozess installiertes pre-removal-Skript gab den Fehlerwert 5 zurück InstallationDate: Installed on 2016-06-04 (5 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.12~ubuntu16.04.1 SourcePackage: nvidia-graphics-drivers-361 Title: package libcuda1-361 361.45.11-0ubuntu0.16.04.1 failed to install/upgrade: Unterprozess installiertes pre-removal-Skript gab den Fehlerwert 5 zurück UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-361/+bug/1591268/+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 1628317] [NEW] can't change params of automated playlist
Public bug reported: If I create a new auto-playlist, there is no GUI way to change attributes/params, that has been created. I can do that by direct editing of playlists.xml but it's not so easy way for many users. ** Affects: rhythmbox (Ubuntu) Importance: Undecided Status: New ** Description changed: - If I create a new auto-playlist, there is no way to change - attributes/params, that has been created. + If I create a new auto-playlist, there is no GUI way to change + attributes/params, that has been created. I can do that by direct + editing of playlists.xml but it's not so easy way for many users. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/1628317 Title: can't change params of automated playlist Status in rhythmbox package in Ubuntu: New Bug description: If I create a new auto-playlist, there is no GUI way to change attributes/params, that has been created. I can do that by direct editing of playlists.xml but it's not so easy way for many users. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1628317/+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 1628342] [NEW] /usr/bin/nm-connection-editor:ERROR:nm-connection-editor.c:209:connection_editor_validate: assertion failed: (s_con)
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding network-manager-applet. This problem was most recently seen with version 0.9.4.1-0ubuntu2.5, the problem page at https://errors.ubuntu.com/problem/e3785e7c388cc45591609e4ce115461f3eb28d9e contains more details. ** Affects: network-manager-applet (Ubuntu) Importance: Undecided Status: New ** Tags: precise -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/1628342 Title: /usr/bin/nm-connection-editor:ERROR:nm-connection- editor.c:209:connection_editor_validate: assertion failed: (s_con) Status in network-manager-applet package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding network-manager-applet. This problem was most recently seen with version 0.9.4.1-0ubuntu2.5, the problem page at https://errors.ubuntu.com/problem/e3785e7c388cc45591609e4ce115461f3eb28d9e contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1628342/+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 1622303] Re: Fails to unlock/ resumes to black screen
I tried downgrading lightdm (and related packages) to their xenial versions (1.18.x) and the bug persists, so it seems less likely to be directly related to lightdm. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1622303 Title: Fails to unlock/ resumes to black screen Status in light-locker package in Ubuntu: Confirmed Status in lightdm package in Ubuntu: New Status in lightdm-gtk-greeter package in Ubuntu: New Bug description: Lock screen (or suspend) System allows for password to unlock No desktop shown after unlocking ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xfce4-power-manager 1.4.4-4ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16 Uname: Linux 4.4.0-9136-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CurrentDesktop: XFCE Date: Sun Sep 11 10:04:39 2016 InstallationDate: Installed on 2016-06-11 (91 days ago) InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160611) SourcePackage: xfce4-power-manager UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CurrentDesktop: XFCE DistroRelease: Ubuntu 16.10 InstallationDate: Installed on 2016-06-11 (95 days ago) InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160611) Package: light-locker 1.7.0-2ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16 Tags: yakkety Uname: Linux 4.4.0-9136-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/light-locker/+bug/1622303/+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 1583088] Re: Randomly corrupt characters in Unity8
Comments #11 and #12 are not this bug at all. I have hidden those now to avoid confusion. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-desktop in Ubuntu. https://bugs.launchpad.net/bugs/1583088 Title: Randomly corrupt characters in Unity8 Status in Canonical System Image: New Status in gnome-desktop package in Ubuntu: Invalid Status in qtmir package in Ubuntu: Confirmed Status in unity8 package in Ubuntu: Confirmed Bug description: Corrupted characters in text rendering, mainly in Unity8 window titlebars. I think this is a new issue. It only started happening (on xenial desktop) in the past month or two. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1583088/+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 1606103] Re: modeset driver is missing some modes that the intel driver (and Mir) has
Ok, thanks for the info re dpkg-buildpackage. xf86DefModeSet.c is created by hw/xfree86/common/modeline2c.awk. If you run dpkg-buildpackage, you'll find it two places: $ find -name xf86DefModeSet.c ./build-main/hw/xfree86/common/xf86DefModeSet.c ./build-udeb/hw/xfree86/common/xf86DefModeSet.c xf86DefModeSet.c is built using the files hw/xfree86/common/vesamodes and hw/xfree86/common/extramodes. extramodes is modified in the build process by debian/patches/001_fedora_extramodes.patch, so editing extramodes directly means the patch and therefore build fails. The packages do build if I add my missing modes to vesamodes and because all the modes are combined into the one xf86DefModeSet.c, I assume it'll work for testing purposes. dpkg-buildpackage builds a whole bunch of debs: xserver-common_1.18.4-1ubuntu6_all.deb xserver-xorg-core-udeb_1.18.4-1ubuntu6_amd64.udeb xserver-xephyr_1.18.4-1ubuntu6_amd64.deb xserver-xorg-dev_1.18.4-1ubuntu6_amd64.deb xserver-xorg-core_1.18.4-1ubuntu6_amd64.deb xserver-xorg-legacy_1.18.4-1ubuntu6_amd64.deb xserver-xorg-core-dbg_1.18.4-1ubuntu6_amd64.deb xserver-xorg-xmir_1.18.4-1ubuntu6_all.deb It looks like installing xserver-common and xserver-xorg-core should be sufficient to test my changes, is that correct or do I need the udeb or any of the other packages? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1606103 Title: modeset driver is missing some modes that the intel driver (and Mir) has Status in linux package in Ubuntu: Invalid Status in xorg-server package in Ubuntu: Confirmed Status in xorg-server package in Debian: New Bug description: My laptop's 4K screen (Dell XPS 15 9550) has these resolutions, according to the intel driver: 3840x2160 60.00 + 3200x1800 60.00 2880x1620 60.00 2560x1440 60.00* 2048x1536 60.00 1920x1440 60.00 1856x1392 60.01 1792x1344 60.01 2048x1152 60.00 1920x1200 59.95 1920x1080 60.0059.93 1600x1200 60.00 1680x1050 59.9559.88 1600x1024 60.17 1400x1050 59.98 1600x900 60.00 1280x1024 60.02 1440x900 59.89 1280x960 60.00 1368x768 60.00 1360x768 59.8059.96 1152x864 60.00 1280x720 60.00 1024x768 60.00 1024x576 60.00 960x540 60.00 800x600 60.3256.25 864x486 60.00 640x480 59.94 720x405 60.00 640x360 60.00 But with the modeset driver, it detects these resolutions: 3840x2160 60.00*+ 2048x1536 60.00 1920x1440 60.00 1856x1392 60.01 1792x1344 60.01 1920x1200 59.95 1920x1080 59.93 1600x1200 60.00 1680x1050 59.9559.88 1600x1024 60.17 1400x1050 59.98 1280x1024 60.02 1440x900 59.89 1280x960 60.00 1360x768 59.8059.96 1152x864 60.00 1024x768 60.0460.00 960x720 60.00 928x696 60.05 896x672 60.01 960x600 60.00 960x540 59.99 800x600 60.0060.3256.25 840x525 60.0159.88 800x512 60.17 700x525 59.98 640x512 60.02 720x450 59.89 640x480 60.0059.94 680x384 59.8059.96 576x432 60.06 512x384 60.00 400x300 60.3256.34 320x240 60.05 It seems to be picking up some extra super-low resolutions (like 320x240) but not the higher 16:9 resolutions. I normally run it at 2560x1440, because the native resolution is too high with an external monitor attached at 1980x1080, but I can't do this with the modeset driver. I'm reporting this as per https://tjaalton.wordpress.com/2016/07/23 /intel-graphics-gen4-and-newer-now-defaults-to-modesetting-driver- on-x/, although note that there are several inaccuracies in that post - there's a typo in ‘cp /usr/share/doc/xserver-xoeg-video- intel/xorg.conf /etc/X11‘, the file doesn't exist in any case if you correct the typo, and I couldn't use ubuntu-bug to report this against xorg-xserver, because ubuntu-bug said the xorg-xserver package doesn't exist. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xorg-server-source (not installed) Uname: Linux 4.6.4-040604-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.2-0ubuntu1 Architecture: amd64 BootLog: 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: Mon Jul 25 11:09:00 2016 DistUpgraded: 2016-
[Desktop-packages] [Bug 1627852] Re: Xorg assert failure: Xorg: ../../glamor/glamor_fbo.c:189: glamor_pixmap_ensure_fb: Assertion `fbo->tex != 0' failed.
** Information type changed from Private to Public -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1627852 Title: Xorg assert failure: Xorg: ../../glamor/glamor_fbo.c:189: glamor_pixmap_ensure_fb: Assertion `fbo->tex != 0' failed. Status in xorg-server package in Ubuntu: New Bug description: [Steps] I don't know, automatic bug report. I have the displaylink linux drivers installed, btw. I was testing it when this crash appears, so it may be related. ProblemType: Crash DistroRelease: Ubuntu 16.10 Package: xserver-xorg-core 2:1.18.4-1ubuntu6 ProcVersionSignature: Ubuntu 4.8.0-16.17-generic 4.8.0-rc7 Uname: Linux 4.8.0-16-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 AssertionMessage: Xorg: ../../glamor/glamor_fbo.c:189: glamor_pixmap_ensure_fb: Assertion `fbo->tex != 0' failed. BootLog: WARNING: Failed to connect to lvmetad. Falling back to device scanning. /dev/mapper/ubuntu--vg-root: clean, 3210374/15122432 files, 46188509/60467200 blocks CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CrashCounter: 1 Date: Mon Sep 26 22:50:29 2016 DistUpgraded: 2016-09-26 18:59:06,915 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: yakkety DistroVariant: ubuntu ExecutablePath: /usr/lib/xorg/Xorg ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell 3rd Gen Core processor Graphics Controller [1028:058b] InstallationDate: Installed on 2015-02-16 (588 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) MachineType: Dell Inc. Dell System XPS L322X ProcCmdline: /usr/lib/xorg/Xorg -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch ProcEnviron: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-16-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 Signal: 6 SourcePackage: xorg-server StacktraceTop: __assert_fail_base (fmt=, assertion=assertion@entry=0x7f6df1a0a305 "fbo->tex != 0", file=file@entry=0x7f6df1a0a2eb "../../glamor/glamor_fbo.c", line=line@entry=189, function=function@entry=0x7f6df1a0a440 "glamor_pixmap_ensure_fb") at assert.c:92 __GI___assert_fail (assertion=0x7f6df1a0a305 "fbo->tex != 0", file=0x7f6df1a0a2eb "../../glamor/glamor_fbo.c", line=189, function=0x7f6df1a0a440 "glamor_pixmap_ensure_fb") at assert.c:101 ?? () from /usr/lib/xorg/modules/libglamoregl.so ?? () from /usr/lib/xorg/modules/libglamoregl.so glamor_set_pixmap_texture () from /usr/lib/xorg/modules/libglamoregl.so Title: Xorg assert failure: Xorg: ../../glamor/glamor_fbo.c:189: glamor_pixmap_ensure_fb: Assertion `fbo->tex != 0' failed. UpgradeStatus: Upgraded to yakkety on 2016-09-26 (0 days ago) UserGroups: dialout dmi.bios.date: 05/15/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A09 dmi.board.name: 0PJHXN dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA09:bd05/15/2013:svnDellInc.:pnDellSystemXPSL322X:pvr:rvnDellInc.:rn0PJHXN:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: Dell System XPS L322X dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160706-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1627852/+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 1451728] Re: [master] kde-config-telepathy-accounts package install error
Just the answer I needed to hear to uninstall and never attempt to use or suggest using and in fact cant uninstall it so back to the drawing board. Better yet, to the trash with the drawing baord and back to my beloved Windows. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libaccounts-glib in Ubuntu. https://bugs.launchpad.net/bugs/1451728 Title: [master] kde-config-telepathy-accounts package install error Status in Kubuntu PPA: Fix Released Status in Telepathy KDE: Fix Released Status in kaccounts-integration package in Ubuntu: In Progress Status in kaccounts-providers package in Ubuntu: Triaged Status in ktp-accounts-kcm package in Ubuntu: Triaged Status in libaccounts-glib package in Ubuntu: Fix Released Status in kaccounts-providers source package in Wily: Triaged Status in ktp-accounts-kcm source package in Wily: Triaged Bug description: Installing from Kubuntu 15.04 backports: Unpacking kde-config-telepathy-accounts (15.04.0-0ubuntu1~ubuntu15.04~ppa1) over (0.9.0-0ubuntu1) ... dpkg: error processing archive /var/cache/apt/archives/kde-config-telepathy-accounts_15.04.0-0ubuntu1~ubuntu15.04~ppa1_amd64.deb (--unpack): trying to overwrite '/usr/share/accounts/services/facebook-im.service', which is also in package account-plugin-facebook 0.12+15.04.20150415.1-0ubuntu1 dpkg-deb: error: subprocess paste was killed by signal (Broken pipe) To manage notifications about this bug go to: https://bugs.launchpad.net/kubuntu-ppa/+bug/1451728/+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 1627304] Re: User locking problems - guest login crashing
The following fix to the abstraction seems to fix the issue: === modified file 'data/apparmor/abstractions/lightdm' --- data/apparmor/abstractions/lightdm 2015-10-19 10:44:23 + +++ data/apparmor/abstractions/lightdm 2016-09-28 03:39:54 + @@ -95,7 +95,7 @@ unix (receive) peer=(label=unconfined), unix (create), unix (getattr, getopt, setopt, shutdown), - unix (bind, listen) type=stream addr="@/com/ubuntu/upstart-session/**", + unix (bind, listen, accept, receive, send) type=stream addr="@/com/ubuntu/upstart-session/**", unix (bind, listen) type=stream addr="@/tmp/dbus-*", unix (bind, listen) type=stream addr="@/tmp/.ICE-unix/[0-9]*", unix (bind, listen) type=stream addr="@/dbus-vfs-daemon/*", I figure that something (Unity?) is now making more use of the upstart session. So we need to allow all operations on it. I'm not an upstart expert but I figure this is safe to allow? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1627304 Title: User locking problems - guest login crashing Status in apparmor package in Ubuntu: Invalid Status in gnome-session package in Ubuntu: Incomplete Status in lightdm package in Ubuntu: Triaged Status in lightdm-gtk-greeter package in Ubuntu: Incomplete Status in unity-greeter package in Ubuntu: Incomplete Status in xubuntu-default-settings package in Ubuntu: Incomplete Bug description: Vanilla Ubuntu install. Lock user - login to guest account, desktop crashes. Ctrl+Alt+F7 allows you to resume user after unlocking. Add new user - am able to switch between locked users properly. Can logout of one user and be able to resume other locked session. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: lightdm 1.19.4-0ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-14.15-generic 4.8.0-rc7 Uname: Linux 4.8.0-14-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CurrentDesktop: Unity Date: Sat Sep 24 13:38:09 2016 InstallationDate: Installed on 2016-09-24 (0 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160922) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1627304/+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 1627304] Re: User locking problems - guest login crashing
** Branch linked: lp:lightdm -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1627304 Title: User locking problems - guest login crashing Status in apparmor package in Ubuntu: Invalid Status in gnome-session package in Ubuntu: Incomplete Status in lightdm package in Ubuntu: Triaged Status in lightdm-gtk-greeter package in Ubuntu: Incomplete Status in unity-greeter package in Ubuntu: Incomplete Status in xubuntu-default-settings package in Ubuntu: Incomplete Bug description: Vanilla Ubuntu install. Lock user - login to guest account, desktop crashes. Ctrl+Alt+F7 allows you to resume user after unlocking. Add new user - am able to switch between locked users properly. Can logout of one user and be able to resume other locked session. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: lightdm 1.19.4-0ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-14.15-generic 4.8.0-rc7 Uname: Linux 4.8.0-14-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CurrentDesktop: Unity Date: Sat Sep 24 13:38:09 2016 InstallationDate: Installed on 2016-09-24 (0 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160922) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1627304/+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 1622303] Re: Fails to unlock/ resumes to black screen
Sorry, didn't notice this bug go past. I can't think of anything that would have changed in LightDM and the log isn't showing anything going wrong. I was going to suggest you try downgrading LightDM but you've done that. My best guess is the session / light-locker haven't realised they've been unlocked for some reason? Either that or something to do with VT switching (driver issues?). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1622303 Title: Fails to unlock/ resumes to black screen Status in light-locker package in Ubuntu: Confirmed Status in lightdm package in Ubuntu: New Status in lightdm-gtk-greeter package in Ubuntu: New Bug description: Lock screen (or suspend) System allows for password to unlock No desktop shown after unlocking ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xfce4-power-manager 1.4.4-4ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16 Uname: Linux 4.4.0-9136-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CurrentDesktop: XFCE Date: Sun Sep 11 10:04:39 2016 InstallationDate: Installed on 2016-06-11 (91 days ago) InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160611) SourcePackage: xfce4-power-manager UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CurrentDesktop: XFCE DistroRelease: Ubuntu 16.10 InstallationDate: Installed on 2016-06-11 (95 days ago) InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160611) Package: light-locker 1.7.0-2ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16 Tags: yakkety Uname: Linux 4.4.0-9136-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/light-locker/+bug/1622303/+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 1627304] Re: User locking problems - guest login crashing
Note you can test changes like this by running: $ sudoedit /etc/apparmor.d/abstractions/lightdm $ sudo systemctl reload apparmor.service -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1627304 Title: User locking problems - guest login crashing Status in apparmor package in Ubuntu: Invalid Status in gnome-session package in Ubuntu: Incomplete Status in lightdm package in Ubuntu: Triaged Status in lightdm-gtk-greeter package in Ubuntu: Incomplete Status in unity-greeter package in Ubuntu: Incomplete Status in xubuntu-default-settings package in Ubuntu: Incomplete Bug description: Vanilla Ubuntu install. Lock user - login to guest account, desktop crashes. Ctrl+Alt+F7 allows you to resume user after unlocking. Add new user - am able to switch between locked users properly. Can logout of one user and be able to resume other locked session. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: lightdm 1.19.4-0ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-14.15-generic 4.8.0-rc7 Uname: Linux 4.8.0-14-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CurrentDesktop: Unity Date: Sat Sep 24 13:38:09 2016 InstallationDate: Installed on 2016-09-24 (0 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160922) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1627304/+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 1627502] Re: Black screen, cursor shown, wifi connection popup shown
Looking at your seat0-greeter.log seems to show something might be going wrong with unity-settings-daemon / your X server: (unity-settings-daemon:2377): Gdk-WARNING **: unity-settings-daemon: Fatal IO error 11 (Resurssi ei tilapäisesti ole käytettävissä) on X server :0. Did you recently update any drivers? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1627502 Title: Black screen, cursor shown, wifi connection popup shown Status in lightdm package in Ubuntu: New Bug description: My yakkety installation is now for some reason in shape that lightdm only starts with a black screen, although mouse cursor is shown and movable and "wifi networks available" popup is shown at the top right corner. After some while this disappears and the system goes to some sort of tty switching loop where sometimes text cursor is shown and sometimes just blank screen. If I want to recover text console control of machine I need to quickly after booting switch to tty1 and stop lightdm. This started happening last week after some upgrades and a reboot. I've tried reinstalling and everything I can think of, but I can't fix it. Meanwhile using sddm I can't log in to Unity 7 or 8, and gdm doesn't start at all. So I'm using sddm + Plasma now but would like to be also be able to run Unity 7 and Unity 8. I couldn't also use ubuntu-bug since I can't use the browser interface from command line (otherwise it works fine until that point) and it segfaults under Plasma environment while collecting information. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1627502/+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 1607828] Re: Menus, including preference, missing from nautilus 1:3.18.5-0ubuntu1~xenial1
[Expired for nautilus (Ubuntu) because there has been no activity for 60 days.] ** Changed in: nautilus (Ubuntu) Status: Incomplete => Expired -- 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/1607828 Title: Menus, including preference, missing from nautilus 1:3.18.5-0ubuntu1~xenial1 Status in nautilus package in Ubuntu: Expired Bug description: All menus seem, according to the change log, to have been removed from version 1:3.18.5-0ubuntu1~xenial1 of nautilus. A very unfortunate side effect of this is that the preferences menu is no longer available through a short-cut key. [In the modern mode, this is like driving a Tesla on autopilot with the steering wheel removed. It may not often be needed, but when it is…] This affects Ubuntu 16.04. One expected to be able to select the preferences menu via an action key, which was possible with the earlier version. After the update was installed, this was no longer possible. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1607828/+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 1607212] Re: HDMI connection issue (Ubuntu 16.04 and GeForce GTX 960M)
[Expired for xorg (Ubuntu) because there has been no activity for 60 days.] ** Changed in: xorg (Ubuntu) Status: Incomplete => Expired -- 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/1607212 Title: HDMI connection issue (Ubuntu 16.04 and GeForce GTX 960M) Status in xorg package in Ubuntu: Expired Bug description: I'm working with an acer VN7-592G, with an Intel Core i7 Quad-Core- Prozessor and the NVIDIA GeForce GTX 960M. Since the upgrade to Ubuntu 16.04 I have problems with the HDMI connection. If plugged in, the HDMI is recognised (xrandr), but the second monitor shows "no signal". After restarting the lightdm service (sudo service lightdm restart), the second monitor is working in most cases. Sometimes ubuntu freezes after lightdm restart and a hard reset has to be performed. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 361.42 Tue Mar 22 18:10:58 PDT 2016 GCC version: gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.1) .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: Thu Jul 28 08:13:41 2016 DistUpgraded: 2016-06-05 13:36:30,607 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Skylake Integrated Graphics [8086:191b] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Skylake Integrated Graphics [1025:1039] Subsystem: Acer Incorporated [ALI] GM107M [GeForce GTX 960M] [1025:1039] InstallationDate: Installed on 2015-11-24 (246 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) MachineType: Acer Aspire VN7-592G ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic.efi.signed root=UUID=347e424a-f916-4ca8-a254-caa35281e9c3 ro noprompt persistent quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to xenial on 2016-06-05 (52 days ago) dmi.bios.date: 09/25/2015 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.03 dmi.board.asset.tag: No Asset Tag dmi.board.name: Aspire VN7-592G dmi.board.vendor: Acer dmi.board.version: V1.03 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.03 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.03:bd09/25/2015:svnAcer:pnAspireVN7-592G:pvrV1.03:rvnAcer:rnAspireVN7-592G:rvrV1.03:cvnAcer:ct10:cvrV1.03: dmi.product.name: Aspire VN7-592G dmi.product.version: V1.03 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.12.2+16.04.20160714-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Wed Jul 27 09:13:51 2016 xserver.configfile: /etc/X11/xorg.conf xserver.errors: evdev: Dell Dell USB Wired Entry Keyboard: Unable to open evdev device "/dev/input/event7". xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.3-1ubuntu2.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1607212/+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 1598904] Re: X server crashes sporadically with a segfault
[Expired for xorg (Ubuntu) because there has been no activity for 60 days.] ** Changed in: xorg (Ubuntu) Status: Incomplete => Expired -- 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/1598904 Title: X server crashes sporadically with a segfault Status in xorg package in Ubuntu: Expired Bug description: My desktop session crashes sporadically. Often this happens when I leave the computer and the screensaver starts (Euphoria GL screensaver). This bug is not reproducible on demand. Attached is my Xorg log file which seems to indicate that this problem is related to the i915 driver code. --- ApportVersion: 2.14.1-0ubuntu3.21 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: kwin DistUpgraded: 2016-06-15 15:16:54,383 DEBUG enabling apt cron job DistroCodename: trusty DistroRelease: Ubuntu 14.04 DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: No GraphicsCard: Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:5036] InstallationDate: Installed on 2016-05-26 (59 days ago) InstallationMedia: Kubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 (20160217.1) LightdmGreeterLog: QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: No such file or directory QFileSystemWatcher: failed to add paths: /var/lib/lightdm/.config/ibus/bus Bus::open: Can not get ibus-daemon's address. IBusInputContext::createInputContext: no connection to ibus-daemon file:///usr/share/kde4/apps/lightdm-kde-greeter/themes/userbar/main.qml:135: Unable to assign [undefined] to QString usersession LightdmGreeterLogOld: QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: No such file or directory QFileSystemWatcher: failed to add paths: /var/lib/lightdm/.config/ibus/bus Bus::open: Can not get ibus-daemon's address. IBusInputContext::createInputContext: no connection to ibus-daemon file:///usr/share/kde4/apps/lightdm-kde-greeter/themes/userbar/main.qml:135: Unable to assign [undefined] to QString usersession MachineType: LENOVO 20BWS18900 Package: xorg 1:7.7+1ubuntu8.1 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.6.3-040603-generic root=UUID=285091fd-ac1a-4801-8055-c356ab9083a5 ro quiet splash vt.handoff=7 Tags: trusty ubuntu Uname: Linux 4.6.3-040603-generic x86_64 UpgradeStatus: Upgraded to trusty on 2016-06-15 (39 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 03/02/2015 dmi.bios.vendor: LENOVO dmi.bios.version: JBET46WW (1.11 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BWS18900 dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrJBET46WW(1.11):bd03/02/2015:svnLENOVO:pn20BWS18900:pvrThinkPadT450s:rvnLENOVO:rn20BWS18900:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20BWS18900 dmi.product.version: ThinkPad T450s dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.64-1~ubuntu14.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri N/A version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Mon Jul 25 09:49:33 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id1133 vendor LGD xserver.version: 2:1.17.2-1ubuntu9.1~trusty1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1598904/+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 909022]
This bug has only been reported for versions older than KDEPIM 4.14 (at most akonadi-1.3). Can anyone tell if this bug still present? If noone confirms this bug for a recent version of akonadi (part of KDE Applications 15.08 or later), it gets closed in about three months. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to akonadi in Ubuntu. https://bugs.launchpad.net/bugs/909022 Title: Various akonadi processes use 100% CPU and 200% RAM at every KDE session startup Status in Akonadi: Incomplete Status in akonadi package in Ubuntu: Invalid Bug description: On every KDE session startup, a bunch of akonadi-related processes are started. These start hogging the system CPU and RAM shortly after startup, and quickly tie up 100% CPU and 200% RAM (i.e. they use up almost 8G physical RAM and start chewing on swap as well!) In order not to have my 2-core 8G RAM machine completely bogged down by these processes, I have to kill the processes manually, else my session becomes unusable and I have to reset the machine. Ubuntu: up-to-date 11.10 To manage notifications about this bug go to: https://bugs.launchpad.net/akonadi/+bug/909022/+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 862483]
This bug has only been reported for versions older than KDEPIM 4.14 (at most akonadi-1.3). Can anyone tell if this bug still present? If noone confirms this bug for a recent version of akonadi (part of KDE Applications 15.08 or later), it gets closed in about three months. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to akonadi in Ubuntu. https://bugs.launchpad.net/bugs/862483 Title: Unable to read mail after resume due to akonadi hang Status in Akonadi: Incomplete Status in Release Notes for Ubuntu: Fix Released Status in akonadi package in Ubuntu: Confirmed Status in akonadi source package in Oneiric: Won't Fix Status in akonadi source package in Precise: Confirmed Bug description: I few times since upgrading this laptop to KDE 4.7 (and moving from Kmail to Kmail2) I've been unable to read email via imap. When I click on a message it says "Retrieving folder contents, please wait" indefinitely. I tried exiting kmail and restarting it, but still had the same problem. After stopping and starting akonadi using the Akonadi Server Configuration KCM, then it was able to read mail (without restarting kmail2 again). Note: Akonadi version is actually 1.6.1, but I didn't see that option under application version. Reproducible: Sometimes Steps to Reproduce: Suspend laptop, resume laptop, check mail provided via an imap resource. Actual Results: "Retrieving folder contents, please wait" Expected Results: Mail retrieved so I can read it. RELEASE NOTE: Kmail/Kontact cannot reliably retrieve email after a suspend resume cycle. Sometimes after resume, instead of displaying messages, "Retrieving folder contents, please wait" will be persistently displayed. If this occurs, use the Akonadi Server Configuration control module to restart Akonadi. That should resolve this issue. Restarting Kontact/Kmail will not. To access the control module use the search function in Kickoff (K menu) or Quicksand (alt-F2) to find it. To manage notifications about this bug go to: https://bugs.launchpad.net/akonadi/+bug/862483/+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 909022] Re: Various akonadi processes use 100% CPU and 200% RAM at every KDE session startup
** Changed in: akonadi Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to akonadi in Ubuntu. https://bugs.launchpad.net/bugs/909022 Title: Various akonadi processes use 100% CPU and 200% RAM at every KDE session startup Status in Akonadi: Incomplete Status in akonadi package in Ubuntu: Invalid Bug description: On every KDE session startup, a bunch of akonadi-related processes are started. These start hogging the system CPU and RAM shortly after startup, and quickly tie up 100% CPU and 200% RAM (i.e. they use up almost 8G physical RAM and start chewing on swap as well!) In order not to have my 2-core 8G RAM machine completely bogged down by these processes, I have to kill the processes manually, else my session becomes unusable and I have to reset the machine. Ubuntu: up-to-date 11.10 To manage notifications about this bug go to: https://bugs.launchpad.net/akonadi/+bug/909022/+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 862483] Re: Unable to read mail after resume due to akonadi hang
** Changed in: akonadi Status: Unknown => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to akonadi in Ubuntu. https://bugs.launchpad.net/bugs/862483 Title: Unable to read mail after resume due to akonadi hang Status in Akonadi: Incomplete Status in Release Notes for Ubuntu: Fix Released Status in akonadi package in Ubuntu: Confirmed Status in akonadi source package in Oneiric: Won't Fix Status in akonadi source package in Precise: Confirmed Bug description: I few times since upgrading this laptop to KDE 4.7 (and moving from Kmail to Kmail2) I've been unable to read email via imap. When I click on a message it says "Retrieving folder contents, please wait" indefinitely. I tried exiting kmail and restarting it, but still had the same problem. After stopping and starting akonadi using the Akonadi Server Configuration KCM, then it was able to read mail (without restarting kmail2 again). Note: Akonadi version is actually 1.6.1, but I didn't see that option under application version. Reproducible: Sometimes Steps to Reproduce: Suspend laptop, resume laptop, check mail provided via an imap resource. Actual Results: "Retrieving folder contents, please wait" Expected Results: Mail retrieved so I can read it. RELEASE NOTE: Kmail/Kontact cannot reliably retrieve email after a suspend resume cycle. Sometimes after resume, instead of displaying messages, "Retrieving folder contents, please wait" will be persistently displayed. If this occurs, use the Akonadi Server Configuration control module to restart Akonadi. That should resolve this issue. Restarting Kontact/Kmail will not. To access the control module use the search function in Kickoff (K menu) or Quicksand (alt-F2) to find it. To manage notifications about this bug go to: https://bugs.launchpad.net/akonadi/+bug/862483/+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
Re: [Desktop-packages] [Bug 1574324] Re: pulseaudio crashes when connecting to bluetooth headphones (due to ubuntu changes?)
Ok, I've added more logging to module-bluez5-device.c, this time I logged whenever the channels value is set, which helps determine the code flow somewhat. I haven't yet tested with a working headset, but I am not seeing any of the additional lgoging I added when attempting to connect a known non-working headset with touch patches to pulseaudio, which suggests to me that so far, the code doesn't even get that far... I've uploaded an updated package to my PPA with this additional logging. If you can provide logs, either for a working or non-working bluetooth device, that would be great. Thanks. -- 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/1574324 Title: pulseaudio crashes when connecting to bluetooth headphones (due to ubuntu changes?) Status in pulseaudio package in Ubuntu: In Progress Bug description: When I attempt to connect my Jaybird Bluebuds X to Ubuntu 16.04 pulseaudio crashes, this does *NOT* happen with a Jambox which leads me to believe it's an intermittent problem with some hardware. This did not happen on Ubuntu 15.10 (which was an upgrade of 15.04). Ubuntu Release: Description: Ubuntu 16.04 LTS Release: 16.04 Pulseaudio Version: pulseaudio: Installed: 1:8.0-0ubuntu3 Candidate: 1:8.0-0ubuntu3 Version table: *** 1:8.0-0ubuntu3 500 500 http://gb.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status Device info: [bluetooth]# info 44:5E:F3:B4:07:29 Device 44:5E:F3:B4:07:29 Name: BlueBuds X Alias: BlueBuds X Class: 0x240404 Icon: audio-card Paired: yes Trusted: yes Blocked: no Connected: no LegacyPairing: no UUID: Headset (1108--1000-8000-00805f9b34fb) UUID: Audio Sink(110b--1000-8000-00805f9b34fb) UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb) UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb) UUID: Handsfree (111e--1000-8000-00805f9b34fb) UUID: Unknown (80ff--1000-8000-00805f9b34fb) I have also attached a debug dump of Pulseaudio when attempting to connect to the headphones. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1574324/+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 1573720] Re: Unencrypted private keys are insecure error reported even when key is encrypted
network-manager just got updated to 1.2.2 containing a fix for this bug: https://bugs.launchpad.net/ubuntu/+source/network-manager- applet/+bug/1575614 I assume that this issue is actually a duplicate of 1575614. As it seems it required two steps for me to fix this problem: * Update BIOS (here: Dell Precision 5510 updated from 1.2.10 to 1.2.14) Having this I already was able to connect to the protected WLAN... but had to ignore some nag-screens about the "unencrypted" key. * Update network-manager to 1.2.2 (available through system update) Private keys are now visible in the file-chooser and I get no more complaints on the "unencrypted" key. -- 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/1573720 Title: Unencrypted private keys are insecure error reported even when key is encrypted Status in NetworkManager: Incomplete Status in network-manager package in Ubuntu: Triaged Bug description: When I enter an EAP-TLS wifi config, I get the error: "Unencrypted private keys are insecure The selected private key does not appear to be protected by a password. This could allow your security credentials to be compromised. Please select a password-protected private key. (You can password-protect your private key with openssl)" I have verified that my key is, in fact, encrypted, and I have tried using both des3 and aes256. I have also verified the password used to encrypt the key. For a while, it wouldn't even let me save the config. I managed to save it eventually, but now when I try to connect to the saved connection, I get the same error. I am on Ubuntu mate 16.04 network-manager 1.1.93 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.1.93-0ubuntu4 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: MATE Date: Fri Apr 22 13:25:16 2016 InstallationDate: Installed on 2015-08-19 (246 days ago) InstallationMedia: Ubuntu-MATE 15.04 "Vivid Vervet" - Release amd64 (20150422.1) IpRoute: default via 192.168.151.254 dev eth1 proto static metric 100 169.254.0.0/16 dev eth1 scope link metric 1000 192.168.151.0/24 dev eth1 proto kernel scope link src 192.168.151.95 metric 100 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: Upgraded to xenial on 2016-04-22 (0 days ago) nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH eth1ethernet connected /org/freedesktop/NetworkManager/Devices/2 Wired connection 1 ed50d4f9-c810-4be0-b06c-8acd58015c50 /org/freedesktop/NetworkManager/ActiveConnection/0 wlan0 wifi disconnected /org/freedesktop/NetworkManager/Devices/1 -- ---- eth0ethernet unavailable /org/freedesktop/NetworkManager/Devices/3 -- ---- lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/0 -- ---- nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1573720/+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
