[Desktop-packages] [Bug 1656064] Re: package cups-browsed 1.8.3-2ubuntu3.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 5
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: cups-filters (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups-filters in Ubuntu. https://bugs.launchpad.net/bugs/1656064 Title: package cups-browsed 1.8.3-2ubuntu3.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 5 Status in cups-filters package in Ubuntu: Confirmed Bug description: Does not install properly. Cups printer install does not function. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: cups-browsed 1.8.3-2ubuntu3.1 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic i686 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: i386 Date: Thu Jan 12 12:25:25 2017 ErrorMessage: subprocess installed post-installation script returned error exit status 5 InstallationDate: Installed on 2017-01-12 (0 days ago) InstallationMedia: Lubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160720) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: Bad file descriptor MachineType: Dell Inc. Latitude D630 Papersize: letter ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-31-generic root=/dev/mapper/lubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.12~ubuntu16.04.1 SourcePackage: cups-filters Title: package cups-browsed 1.8.3-2ubuntu3.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 5 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/04/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A19 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA19:bd06/04/2013:svnDellInc.:pnLatitudeD630:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Latitude D630 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1656064/+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 1652876] Re: No proprietary driver available for NVIDIA [10de:13b4]
** Changed in: ubuntu-drivers-common (Ubuntu) Assignee: (unassigned) => Alberto Milone (albertomilone) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1652876 Title: No proprietary driver available for NVIDIA [10de:13b4] Status in HWE Next: New Status in ubuntu-drivers-common package in Ubuntu: New Bug description: This is a hybrid graphic system, but there is no proprietary driver available for the NVIDIA graphic card on this system. 01:00.0 3D controller [0302]: NVIDIA Corporation Device [10de:13b4] (rev a2) Subsystem: Dell Device [1028:07a9] Kernel driver in use: nouveau Kernel modules: nvidiafb, nouveau To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1652876/+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 1458322] Re: NetworkManager doesn't hide virtual interfaces (e.g. Docker, VMWare)
Is there any reason the lines creating the menu entry can't just be removed? https://bazaar.launchpad.net/~vcs-imports/network-manager- applet/git-master/view/head:/src/applet.c#L1322 -- 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/1458322 Title: NetworkManager doesn't hide virtual interfaces (e.g. Docker, VMWare) Status in One Hundred Papercuts: Confirmed Status in network-manager package in Ubuntu: Confirmed Bug description: Previously in Ubuntu 14.04 NetworkManager hid the veth interfaces that were created by Docker. Now since I've updated to 15.04 the veth interfaces are listed as Unmanaged under the gnome system tray icon which is kind of annoying. I'm using docker 1.6.2 and network-manager 0.9.10.0-4ubuntu15.1 ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: network-manager 0.9.10.0-4ubuntu15.1 ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6 Uname: Linux 3.19.0-18-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 CurrentDesktop: GNOME Date: Sun May 24 14:22:44 2015 EcryptfsInUse: Yes InstallationDate: Installed on 2013-08-29 (632 days ago) InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64 (20130214) IpRoute: default via 192.168.178.1 dev wlan0 proto static metric 1024 169.254.0.0/16 dev wlan0 scope link metric 1000 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.42.1 192.168.178.0/24 dev wlan0 proto kernel scope link src 192.168.178.40 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: Upgraded to vivid on 2015-05-24 (0 days ago) mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2014-08-19T11:46:06.705439 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/hundredpapercuts/+bug/1458322/+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 1600136] Re: App indicator does not show icon for Qt apps or with custom icons
I think you meant https://codereview.qt-project.org/182310 (not 182307). Thanks for the patch anyway! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to sni-qt in Ubuntu. https://bugs.launchpad.net/bugs/1600136 Title: App indicator does not show icon for Qt apps or with custom icons Status in Qt: In Progress Status in Snappy: New Status in appmenu-qt5 package in Ubuntu: Fix Released Status in libappindicator package in Ubuntu: Fix Released Status in qtbase-opensource-src package in Ubuntu: In Progress Status in snapd package in Ubuntu: In Progress Status in sni-qt package in Ubuntu: Fix Released Bug description: Snaps that use the app indicator area via Qt can't display their icon there. Steps to reproduce and screenshot: https://github.com/nuttyartist/notes/pull/77 Some research: - Uses http://doc.qt.io/qt-5/qsystemtrayicon.html - The indicator icon is created under /tmp under a randomly generated directory name didrocks mentions also: 1. The application says "this is my menu, and here is my icon at that address", the address being /tmp/blablabla 2. appindicator receives the bus messages 3. and says "let's have a look at this icon at that address" 4. BUT! /tmp in the snap is different form system /tmp To manage notifications about this bug go to: https://bugs.launchpad.net/qt/+bug/1600136/+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 1574347] Re: [SRU] Re-read the link type if the name changed
larabi: I came from Fedora, and I had been running it for the last releases on my laptop. Never had any WiFi issues, so there's not anything wrong with my hardware. I recently installed Ubuntu 16.04.1 LTS, but these WiFi issues are quite annoying and I'm contemplating switching back to Fedora. I don't understand how this still hasn't been fixed in an LTS version of the OS. -- 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/1574347 Title: [SRU] Re-read the link type if the name changed Status in NetworkManager: Fix Released Status in OEM Priority Project: Fix Released Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Xenial: Fix Released Bug description: [Impact] NM needs to re-read the DEVTYPE after the device name changed, an example is that WiFi network list disappears from network manager applet [Testcase] 1. Boot the system. It should include a wireless device. 2. In a terminal, run 'nmcli dev'. 3. In the correct case, the line for the wireless device should read "wifi" under the TYPE column. In a failure case, it will read "ethernet". After upgrading to the new version, the repeating the above steps should give expected behavior. [Regression Potential] Potential of causing regression is relatively small for a one line change to re-read a value to be known. --- Problems:- 1. The network manager applet does not show the list of WiFI APs it can find. 2. The network manager applet does not the name of the AP to which it is connected 3. The icon of the applet shows two vertical arrows in opposite direction - the wired connection symbol and NOT the wifi connected icon. Temporary Workaround:- Log out and again log back in. To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1574347/+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 1640558] Re: 16.10 Backup Failure.
[Expired for duplicity (Ubuntu) because there has been no activity for 60 days.] ** Changed in: duplicity (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to duplicity in Ubuntu. https://bugs.launchpad.net/bugs/1640558 Title: 16.10 Backup Failure. Status in duplicity package in Ubuntu: Expired Bug description: A daily backup job run by corn invokes a script that runs duplicity. Since I have upgraded to 16.10 from 16.04 duplicity crashes with the message "killed". It seems that the real problem is in the NVIDIA driver for my screen. The machine does not crash in other situations. Some info Dell XPS 15 L502X, 15,6" FHD, NVIDIA GEFORCE GT 540M GR 2 GB NVIDIA driver version 367.57 X server version 11.0, server vendor version 1.18.4, NV-control version 1.29 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/duplicity/+bug/1640558/+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 1652486] Re: mesa gpu lockup
** Changed in: mesa (Ubuntu Xenial) Importance: Undecided => Medium ** Changed in: mesa (Ubuntu Yakkety) Importance: Undecided => Medium -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1652486 Title: mesa gpu lockup Status in Mesa: Unknown Status in mesa package in Ubuntu: Fix Released Status in mesa source package in Xenial: New Status in mesa source package in Yakkety: New Bug description: package: mesa version: 11.2.0-1ubuntu2.2 release: 16.04.1 / "Xenial" references: * https://bugs.freedesktop.org/show_bug.cgi?id=93649 * https://cgit.freedesktop.org/mesa/mesa/commit/?id=6dc96de3 symptoms: 1. kernel reports "GPU lockup" 2. kernel reports "GPU softreset" 3. immediately frozen display 4. eventual "INFO: task (kworker|Xorg)[/:0-9]+ blocked for more than 120 seconds." 5. computer hanging on system reboot requiring a forced power off Symptoms occur when playing Team Fortress 2. Attachments: 1. mesa source package patch 2. lspci output for video card (ie Radeon HD 7750) 3. kernel log To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1652486/+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 1655828] Re: Mouse flickers and disappears on primary monitor when additional monitor is connected
The label is pretty faded, so I'm not positive on this. But I think it's: Make: DisplayLink Model: E364109 -- 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/1655828 Title: Mouse flickers and disappears on primary monitor when additional monitor is connected Status in xorg package in Ubuntu: Incomplete Bug description: Any time I connect my Acer G236HL LCD monitor with VGA via my Displaylink adapter (DisplayLink driver version 1.2.65), the mouse flickers and disappears in the primary monitor. It displays perfectly on the additional monitor. It also displays perfectly after the additional monitor is disconnected. I see that there are a number of similar bug reports: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1645891 https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1629300 https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1278223 https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1613001 ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xorg 1:7.7+13ubuntu4 ProcVersionSignature: Ubuntu 4.8.0-34.36-generic 4.8.11 Uname: Linux 4.8.0-34-generic x86_64 NonfreeKernelModules: wl .tmp.unity_support_test.0: ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Tue Jan 10 22:34:58 2017 DistUpgraded: 2016-10-23 13:14:39,472 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process "./xorg_fix_proprietary.py" (No such file or directory) (8)) DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-20140620-0 DistroCodename: yakkety DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.248+bdcom, 4.8.0-32-generic, x86_64: installedError! Could not locate dkms.conf file. File: does not exist. bcmwl, 6.30.223.248+bdcom, 4.8.0-34-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 5500 [1028:0665] InstallationDate: Installed on 2016-01-26 (350 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20140620-04:25 MachineType: Dell Inc. XPS 13 9343 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-34-generic root=UUID=485e1110-0879-413f-b537-6b5b97353478 ro quiet splash usbcore.autosuspend=-1 "acpi_osi=Windows 2013" vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to yakkety on 2016-10-23 (79 days ago) XorgLogOld: dmi.bios.date: 08/29/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: A09 dmi.board.name: 0TM99H dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA09:bd08/29/2016:svnDellInc.:pnXPS139343:pvr:rvnDellInc.:rn0TM99H:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 13 9343 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-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6.1 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 xserver.bootTime: Tue Jan 10 20:18:19 2017 xserver.configfile: default xserver.errors: modeset(G0): glamor initialization failed xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id5152 vendor SHP xserver.version: 2:1.18.4-1ubuntu6.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1655828/+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 1565080] Re: ubuntuBSD support
This bug was fixed in the package mesa - 13.0.3-1ubuntu2 --- mesa (13.0.3-1ubuntu2) zesty; urgency=medium * rules: Drop forcing -O2 to fix ppc64el ftbfs, gcc got fixed already. (LP: #1605796) * control: Fix dependencies for ubuntuBSD. (LP: #1565080) * compat,rules: Don't bump compat to 10, breaks applying patches before autoreconf which we need for the Mir EGL platform. -- Timo Aaltonen Thu, 12 Jan 2017 09:49:20 +0200 ** Changed in: mesa (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1565080 Title: ubuntuBSD support Status in mesa package in Ubuntu: Fix Released Bug description: Hi Please could you apply attached patch to make mesa buildable on ubuntuBSD? It just needs to adjust a few dependencies. Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1565080/+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 1605796] Re: mesa FTBFS on ppc64el with -O3 due to ICE
This bug was fixed in the package mesa - 13.0.3-1ubuntu2 --- mesa (13.0.3-1ubuntu2) zesty; urgency=medium * rules: Drop forcing -O2 to fix ppc64el ftbfs, gcc got fixed already. (LP: #1605796) * control: Fix dependencies for ubuntuBSD. (LP: #1565080) * compat,rules: Don't bump compat to 10, breaks applying patches before autoreconf which we need for the Mir EGL platform. -- Timo Aaltonen Thu, 12 Jan 2017 09:49:20 +0200 ** Changed in: mesa (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1605796 Title: mesa FTBFS on ppc64el with -O3 due to ICE Status in gcc-6 package in Ubuntu: Fix Released Status in mesa package in Ubuntu: Fix Released Bug description: Dropping optimization to -O2 allows this build to succeed: https://launchpad.net/ubuntu/+source/mesa/12.0.1-3ubuntu1/+build/10484583 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gcc-6/+bug/1605796/+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 1655556] Re: intel: add support for 16k wide textures
This bug was fixed in the package mesa - 13.0.3-1ubuntu2 --- mesa (13.0.3-1ubuntu2) zesty; urgency=medium * rules: Drop forcing -O2 to fix ppc64el ftbfs, gcc got fixed already. (LP: #1605796) * control: Fix dependencies for ubuntuBSD. (LP: #1565080) * compat,rules: Don't bump compat to 10, breaks applying patches before autoreconf which we need for the Mir EGL platform. -- Timo Aaltonen Thu, 12 Jan 2017 09:49:20 +0200 ** Changed in: mesa (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/166 Title: intel: add support for 16k wide textures Status in mesa package in Ubuntu: Fix Released Bug description: Mesa 13 doesn't support 16k wide textures, needs backports from git. This is needed to support a horizontal monitor array of 3x4k in unity. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/166/+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 1656473] [NEW] /usr/bin/evolution:11:g_type_check_instance_is_fundamentally_a:g_object_unref:g_slist_foreach:e_plugin_lib_enable:e_plugin_enable
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding evolution. This problem was most recently seen with package version 3.22.3-0ubuntu0.1, the problem page at https://errors.ubuntu.com/problem/6389fd1d92d657fd9717f3ff20e9dfa92bb6e4a2 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. ** Affects: evolution (Ubuntu) Importance: Undecided Status: New ** Tags: utopic vivid xenial yakkety -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/1656473 Title: /usr/bin/evolution:11:g_type_check_instance_is_fundamentally_a:g_object_unref:g_slist_foreach:e_plugin_lib_enable:e_plugin_enable Status in evolution package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding evolution. This problem was most recently seen with package version 3.22.3-0ubuntu0.1, the problem page at https://errors.ubuntu.com/problem/6389fd1d92d657fd9717f3ff20e9dfa92bb6e4a2 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1656473/+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 1642413] Re: Chromium uses ~100% of all cores, locks up, and does not exit correctly
** Also affects: chromium-browser Importance: Undecided Status: New ** No longer affects: chromium-browser -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1642413 Title: Chromium uses ~100% of all cores, locks up, and does not exit correctly Status in chromium-browser package in Ubuntu: Incomplete Bug description: whether or not extensions are enabled, after an indeterminate amount of time chromium locks up(tabs are still rendered but browser cannot create new tabs, or navigate in existing ones) and the main process begins using 200-270% of my three cores, chrome task manager shows that no tab is using any memory and when chromium is exited the main thread does not quit and must be killed. I have reinstalled, disabled extensions/plugins, etc... nothing seems to remedy this issue. I memtested my memory and it was fine. It started happening october 2016 --- ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: MATE DRM.card0-HDMI-A-1: enabled: enabled dpms: On status: connected edid-base64: AP///wAi8A4mACANAQOAIht46gyVolZMliUaUFSt74CBgAEBAQEBAQEBAQEBAQEBMCoAmFEAKkAwcBMAUg4RAAAe/QA4TB5TDgAKICAgICAg/ABocCBMMTczMAogICAg/wBDTlAzMzJTMFJICiAgALo= modes: 1280x1024 1280x1024 1152x864 1024x768 1024x768 1024x768 832x624 800x600 800x600 800x600 640x480 640x480 640x480 720x400 DRM.card0-VGA-1: enabled: enabled dpms: On status: connected edid-base64: AP///wA6kwcAAQoRAQMIKxt4CrU0pVZKmiUQUFSvzwCBgIGPlQCVDwEBAQEBAQEBHDmQMGIaJ0BosDYAsQ8RAAAY/gAKICAgICAgICAgICAg/ABNQVctU0VSSUFMCiAg/wAKICAgICAgICAgICAgAHk= modes: 1680x1050 1280x1024 1280x1024 1440x900 1440x900 1024x768 1024x768 1024x768 800x600 800x600 800x600 800x600 640x480 640x480 640x480 720x400 Desktop-Session: 'mate' '/etc/xdg/xdg-mate:/etc/xdg' '/usr/share/mate:/usr/local/share/:/usr/share/:/usr/share/mdm/' DistroRelease: Linux 18.1 Env: 'None' 'None' InstallationDate: Installed on 2016-07-13 (159 days ago) InstallationMedia: Linux Mint 18 "Sarah" - Release amd64 20160628 Load-Avg-1min: 3.87 Load-Processes-Running-Percent: 0.7% MachineType: MSI MS-7786 Package: chromium-browser 55.0.2883.87-0ubuntu0.16.04.1263 [origin: Ubuntu] PackageArchitecture: amd64 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-30-generic root=UUID=5c8e46d1-e26c-4bba-b87b-f092a8a3d7ad ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.8.0-30.32~16.04.1-generic 4.8.6 Tags: serena third-party-packages ThirdParty: True Uname: Linux 4.8.0-30-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip fax floppy lpadmin netdev plugdev sambashare scanner sudo tape vboxusers video _MarkForUpload: True dmi.bios.date: 02/04/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V2.0 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: A55M-P33 (MS-7786) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV2.0:bd02/04/2013:svnMSI:pnMS-7786:pvr1.0:rvnMSI:rnA55M-P33(MS-7786):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.name: MS-7786 dmi.product.version: 1.0 dmi.sys.vendor: MSI etcconfigcpepperflashpluginnonfree: flashso="/usr/lib/pepperflashplugin-nonfree/libpepflashplayer.so" flashversion=`strings $flashso 2> /dev/null | grep LNX | cut -d ' ' -f 2 | sed -e "s/,/./g"` CHROMIUM_FLAGS="$CHROMIUM_FLAGS --ppapi-flash-path=$flashso --ppapi-flash-version=$flashversion" modified.conffile..etc.default.chromium-browser: [deleted] mtime.conffile..etc.chromium-browser.default: 2016-07-13T18:03:09.849211 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1642413/+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 1512027] Re: open of device pixma:MX7600_... failed: invalid argument
The sane project has already confirmed a fix exists in 1.0.25. Unless you go out and buy a Pixma MX7600, you're not gonna have my hardware whether I run apport or not. The apparent motivation to fix bugs in Ubuntu appears anemic at best already, I don't think I'm going to do much harm to that. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to sane-backends in Ubuntu. https://bugs.launchpad.net/bugs/1512027 Title: open of device pixma:MX7600_... failed: invalid argument Status in sane-backends package in Ubuntu: Incomplete Bug description: Up until recently, I've been able to scan fine with my Canon Pixma MX7600. Then I upgraded to Ubuntu Wily and I've started getting: $ scanimage scanimage: open of device pixma:MX7600_192.168.2.107 failed: Invalid argument The device pings and I can get to its HTTP port. Everything appears OK. If I run strace -f -s 256 -o /tmp/trace.txt scanimage the relevant output appears to be: socket(PF_INET, SOCK_DGRAM, IPPROTO_UDP) = 204 connect(204, {sa_family=AF_INET, sin_port=htons(8612), sin_addr=inet_addr("192.168.2.107")}, 16) = 0 sendto(204, "BJNP\2\1\0\0\0\0\0\0\0\0\0\0", 16, 0, NULL, 0) = 16 select(205, [204], NULL, NULL, {4, 0}) = 1 (in [204], left {3, 998257}) recvfrom(204, "BJNP\202\1\0\0\0\0\0\0\0\0\0\20\0\1\10\0\6\4\0\0\205\316\356\343\300\250\2k", 2048, 0, NULL, N ULL) = 32 close(204) write(2, "scanimage: open of device pixma:MX7600_192.168.2.107 failed: Invalid argument\n", 78) = 78 It appears to me that the scanner is responding but the driver doesn't like the response. I'm running sane 1.0.14-11 and sane-utils 1.0.25+git201505. WORKAROUND: Use the PPA from https://launchpad.net/~rolfbensch/+archive/ubuntu/sane-git To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1512027/+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 1553441] Re: Only one monitor working at the time (xorg-amdgpu)
** Tags added: kernel-bug-exists-upstream kernel-bug-exists- upstream-4.10-rc3 ** Changed in: xserver-xorg-video-ati (Ubuntu) Status: Expired => Confirmed ** Summary changed: - Only one monitor working at the time (xorg-amdgpu) + Only one monitor working at the time (xserver-xorg-video-ati) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/1553441 Title: Only one monitor working at the time (xserver-xorg-video-ati) Status in xserver-xorg-video-ati package in Ubuntu: Confirmed Bug description: When external monitor is connected to VGA port (AMD Radeon 7470m) internal laptop monitor stops working. I'm able to set laptop monitor as primary which disables external monitor (and vice-versa). Tried manual switch to mainline Linux 4.5 kernel, same thing. Tested on 14.04, 15.10, 16.04 with same results. WORKAROUND: Use Ubuntu 14.04 with fglrx. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 Uname: Linux 4.5.0-040500rc6-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 5 04:32:48 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: virtualbox, 5.0.14, 4.4.0-10-generic, x86_64: installed virtualbox, 5.0.14, 4.4.0-8-generic, x86_64: installed virtualbox, 5.0.14, 4.5.0-040500rc6-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7640G] [1002:9903] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Trinity [Radeon HD 7640G] [1043:106b] Advanced Micro Devices, Inc. [AMD/ATI] Seymour [Radeon HD 6400M/7400M Series] [1002:6760] (rev ff) (prog-if ff) InstallationDate: Installed on 2016-02-18 (15 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: ASUSTeK COMPUTER INC. K55DR ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.5.0-040500rc6-generic root=UUID=e0064410-4660-40b7-b961-76f320a921a6 ro amdgpu.powerplay=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/07/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 217 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: K55DR 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.:bvr217:bd09/07/2012:svnASUSTeKCOMPUTERINC.:pnK55DR:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnK55DR:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: K55DR dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. 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-1ubuntu3 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.6.1-1ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160218-1ubuntu3 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Sat Mar 5 04:27:41 2016 xserver.configfile: default xserver.errors: RADEON(G0): [XvMC] Failed to initialize extension. xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.1-1ubuntu3 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1553441/+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 1655724] Re: Should not break systemd in trusty, conflicts with snapd
** Branch linked: lp:ubuntu/trusty-proposed/xorg-server-lts-xenial -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server-lts-xenial in Ubuntu. https://bugs.launchpad.net/bugs/1655724 Title: Should not break systemd in trusty, conflicts with snapd Status in xorg-server-lts-xenial package in Ubuntu: Invalid Status in xorg-server-lts-xenial source package in Trusty: Fix Committed Bug description: [Impact] * With introduction of snapd/systemd in trusty, it has become impossible to install xorg-server-lts-xenial simultaniously with snapd/systemd. * In trusty, logind is managed by upstart, and is not restarted on upgrades, therefore the protective breaks in xorg-server-lts-xenial is unnecessary in trusty only. [Testcase] * installing snapd, should not remove xorg-server-lts-xenial To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server-lts-xenial/+bug/1655724/+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 1132063] Re: Mouse settings missing from Mouse & Touchpad dialog
This affects me as well on 16.04. The mouse settings does not show up for bluetooth mouse, but it does show up when a USB mouse is attached and changes there affect both the USB and the bluetooth mouse. So my workaround is to attach a USB mouse, update the settings, then unplug the USB mouse. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1132063 Title: Mouse settings missing from Mouse & Touchpad dialog Status in gnome-control-center package in Ubuntu: Confirmed Status in unity-control-center package in Ubuntu: Triaged Bug description: On up to date Raring alpha, on System Settings > Mouse & Touchpad the Mouse settings are completely missing. The General and Touchpad sections are there but none for mouse. See attached screenshot. xinput --list shows ~$ xinput --list ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ MOSART Semi. 2.4G Keyboard Mouseid=11 [slave pointer (2)] ⎜ ↳ SynPS/2 Synaptics TouchPad id=14 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Power Buttonid=8[slave keyboard (3)] ↳ Sleep Buttonid=9[slave keyboard (3)] ↳ MOSART Semi. 2.4G Keyboard Mouseid=10 [slave keyboard (3)] ↳ Dell Dell USB Keyboard id=12 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=13 [slave keyboard (3)] and from lsusb: Bus 003 Device 002: ID 062a:3286 Creative Labs Nano Receiver [Sandstrom Laser Mouse SMWLL11] ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: gnome-control-center 1:3.6.3-0ubuntu13 ProcVersionSignature: Ubuntu 3.8.0-7.15-generic 3.8.0 Uname: Linux 3.8.0-7-generic i686 ApportVersion: 2.8-0ubuntu4 Architecture: i386 Date: Sat Feb 23 09:40:41 2013 InstallationDate: Installed on 2012-08-01 (205 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha i386 (20120730.1) MarkForUpload: True SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_gnome-control-center: activity-log-manager-control-center 0.9.4-0ubuntu6.1 deja-dup25.5-0ubuntu1 gnome-control-center-signon 0.1.2bzr12.12.05-0ubuntu1 gnome-control-center-unity 1.2daily13.02.15-0ubuntu1 indicator-datetime 12.10.3daily13.02.06-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1132063/+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 1303086] Re: Pointer Speed Missing in Unity Settings for Mouse & Trackpad
*** This bug is a duplicate of bug 1132063 *** https://bugs.launchpad.net/bugs/1132063 This affects me as well on 16.04. The mouse settings does not show up for bluetooth mouse, but it does show up when a USB mouse is attached and changes there affect both the USB and the bluetooth mouse. So my workaround is to attach a USB mouse, update the settings, then unplug the USB mouse. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1303086 Title: Pointer Speed Missing in Unity Settings for Mouse & Trackpad Status in gnome-control-center package in Ubuntu: Confirmed Status in unity-control-center package in Ubuntu: Confirmed Bug description: On updated Ubuntu 14.04 final, the System Settings > Mouse & Touchpad dialog is missing several mouse settings, like the "pointer Speed" setting. See attached screenshot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1303086/+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 1637957] Re: Chromium not working with SAML authentication
Alright, I'll look into updating the whitelist to reflect the new keys. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1637957 Title: Chromium not working with SAML authentication Status in chromium-browser package in Ubuntu: Triaged Bug description: Sync login is failing with SAML authentication. See https://bugs.chromium.org/p/chromium/issues/detail?id=677154 for details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1637957/+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 1656448] [NEW] Remmina high CPU on lock screen
Public bug reported: Using Trusty 14.04.5 on Dell XPS13, when the screen locks then remmina 1.0.0-4ubuntu3 triggers high CPU (fan goes full speed). This happens only when remmina displays a remote desktop (currently another 14.04 vino VNC or a Win7 with RDP). Reproduce: start a remote session, Win+L, the fan speed quickly increases as the background picture slightly dims. Then the backlight turns off and the fan keeps running at max speed. Please note that remmina gui /About shows 0.9.99.1 No support on official Github site as they only support remmina 1.2 ** Affects: remmina (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to remmina in Ubuntu. https://bugs.launchpad.net/bugs/1656448 Title: Remmina high CPU on lock screen Status in remmina package in Ubuntu: New Bug description: Using Trusty 14.04.5 on Dell XPS13, when the screen locks then remmina 1.0.0-4ubuntu3 triggers high CPU (fan goes full speed). This happens only when remmina displays a remote desktop (currently another 14.04 vino VNC or a Win7 with RDP). Reproduce: start a remote session, Win+L, the fan speed quickly increases as the background picture slightly dims. Then the backlight turns off and the fan keeps running at max speed. Please note that remmina gui /About shows 0.9.99.1 No support on official Github site as they only support remmina 1.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/remmina/+bug/1656448/+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 1642413] Re: Chromium uses ~100% of all cores, locks up, and does not exit correctly
This also happens on google chrome browser -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1642413 Title: Chromium uses ~100% of all cores, locks up, and does not exit correctly Status in chromium-browser package in Ubuntu: Incomplete Bug description: whether or not extensions are enabled, after an indeterminate amount of time chromium locks up(tabs are still rendered but browser cannot create new tabs, or navigate in existing ones) and the main process begins using 200-270% of my three cores, chrome task manager shows that no tab is using any memory and when chromium is exited the main thread does not quit and must be killed. I have reinstalled, disabled extensions/plugins, etc... nothing seems to remedy this issue. I memtested my memory and it was fine. It started happening october 2016 --- ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: MATE DRM.card0-HDMI-A-1: enabled: enabled dpms: On status: connected edid-base64: AP///wAi8A4mACANAQOAIht46gyVolZMliUaUFSt74CBgAEBAQEBAQEBAQEBAQEBMCoAmFEAKkAwcBMAUg4RAAAe/QA4TB5TDgAKICAgICAg/ABocCBMMTczMAogICAg/wBDTlAzMzJTMFJICiAgALo= modes: 1280x1024 1280x1024 1152x864 1024x768 1024x768 1024x768 832x624 800x600 800x600 800x600 640x480 640x480 640x480 720x400 DRM.card0-VGA-1: enabled: enabled dpms: On status: connected edid-base64: AP///wA6kwcAAQoRAQMIKxt4CrU0pVZKmiUQUFSvzwCBgIGPlQCVDwEBAQEBAQEBHDmQMGIaJ0BosDYAsQ8RAAAY/gAKICAgICAgICAgICAg/ABNQVctU0VSSUFMCiAg/wAKICAgICAgICAgICAgAHk= modes: 1680x1050 1280x1024 1280x1024 1440x900 1440x900 1024x768 1024x768 1024x768 800x600 800x600 800x600 800x600 640x480 640x480 640x480 720x400 Desktop-Session: 'mate' '/etc/xdg/xdg-mate:/etc/xdg' '/usr/share/mate:/usr/local/share/:/usr/share/:/usr/share/mdm/' DistroRelease: Linux 18.1 Env: 'None' 'None' InstallationDate: Installed on 2016-07-13 (159 days ago) InstallationMedia: Linux Mint 18 "Sarah" - Release amd64 20160628 Load-Avg-1min: 3.87 Load-Processes-Running-Percent: 0.7% MachineType: MSI MS-7786 Package: chromium-browser 55.0.2883.87-0ubuntu0.16.04.1263 [origin: Ubuntu] PackageArchitecture: amd64 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-30-generic root=UUID=5c8e46d1-e26c-4bba-b87b-f092a8a3d7ad ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.8.0-30.32~16.04.1-generic 4.8.6 Tags: serena third-party-packages ThirdParty: True Uname: Linux 4.8.0-30-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip fax floppy lpadmin netdev plugdev sambashare scanner sudo tape vboxusers video _MarkForUpload: True dmi.bios.date: 02/04/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V2.0 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: A55M-P33 (MS-7786) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV2.0:bd02/04/2013:svnMSI:pnMS-7786:pvr1.0:rvnMSI:rnA55M-P33(MS-7786):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.name: MS-7786 dmi.product.version: 1.0 dmi.sys.vendor: MSI etcconfigcpepperflashpluginnonfree: flashso="/usr/lib/pepperflashplugin-nonfree/libpepflashplayer.so" flashversion=`strings $flashso 2> /dev/null | grep LNX | cut -d ' ' -f 2 | sed -e "s/,/./g"` CHROMIUM_FLAGS="$CHROMIUM_FLAGS --ppapi-flash-path=$flashso --ppapi-flash-version=$flashversion" modified.conffile..etc.default.chromium-browser: [deleted] mtime.conffile..etc.chromium-browser.default: 2016-07-13T18:03:09.849211 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1642413/+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 1652410] Re: duja-dup AssertionError: ({1: 'duplicity-full.20161129T015237Z.vol1.difftar'}
found and attached Also I got DEJA_DUP_DEBUG=1 deja-dup --backup | tail -n 1000 > /tmp/deja-dup.log Unsupported use of '='. To run 'deja-dup' with a modified environment, please use 'env DEJA_DUP_DEBUG=1 deja-dup…' david@david-Lenovo-H535 ~> ** Attachment added: "deja-dup.gsettings" https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1652410/+attachment/4804058/+files/deja-dup.gsettings -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to deja-dup in Ubuntu. https://bugs.launchpad.net/bugs/1652410 Title: duja-dup AssertionError: ({1: 'duplicity- full.20161129T015237Z.vol1.difftar'} Status in deja-dup package in Ubuntu: Incomplete Bug description: Deja-dup has never worked for me (last 5 years) always errors. No after a new system reinstall 16.04 I was determined to get it up and running and learn about it's use,and perhaps recover some old data. Still fails with see attached text ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: deja-dup 34.2-0ubuntu1.1 ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35 Uname: Linux 4.4.0-57-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 CurrentDesktop: Unity Date: Fri Dec 23 16:56:43 2016 ExecutablePath: /usr/bin/deja-dup InstallationDate: Installed on 2016-12-02 (21 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) ProcEnviron: PATH=(custom, user) SHELL=/usr/bin/fish LANG=en_CA.UTF-8 LANGUAGE=en_CA:en XDG_RUNTIME_DIR= SourcePackage: deja-dup UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1652410/+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 1637957] Re: Chromium not working with SAML authentication
Patrick, we're not changing the keys back. It's impossible. The old keys were abused by someone and we lost Google API access. We have to fix this another way. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1637957 Title: Chromium not working with SAML authentication Status in chromium-browser package in Ubuntu: Triaged Bug description: Sync login is failing with SAML authentication. See https://bugs.chromium.org/p/chromium/issues/detail?id=677154 for details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1637957/+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 1642413] Re: Chromium uses ~100% of all cores, locks up, and does not exit correctly
grep flags /proc/cpuinfo from an unaffected machine with the same hardware http://dpaste.com/0THCEEE -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1642413 Title: Chromium uses ~100% of all cores, locks up, and does not exit correctly Status in chromium-browser package in Ubuntu: Incomplete Bug description: whether or not extensions are enabled, after an indeterminate amount of time chromium locks up(tabs are still rendered but browser cannot create new tabs, or navigate in existing ones) and the main process begins using 200-270% of my three cores, chrome task manager shows that no tab is using any memory and when chromium is exited the main thread does not quit and must be killed. I have reinstalled, disabled extensions/plugins, etc... nothing seems to remedy this issue. I memtested my memory and it was fine. It started happening october 2016 --- ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: MATE DRM.card0-HDMI-A-1: enabled: enabled dpms: On status: connected edid-base64: AP///wAi8A4mACANAQOAIht46gyVolZMliUaUFSt74CBgAEBAQEBAQEBAQEBAQEBMCoAmFEAKkAwcBMAUg4RAAAe/QA4TB5TDgAKICAgICAg/ABocCBMMTczMAogICAg/wBDTlAzMzJTMFJICiAgALo= modes: 1280x1024 1280x1024 1152x864 1024x768 1024x768 1024x768 832x624 800x600 800x600 800x600 640x480 640x480 640x480 720x400 DRM.card0-VGA-1: enabled: enabled dpms: On status: connected edid-base64: AP///wA6kwcAAQoRAQMIKxt4CrU0pVZKmiUQUFSvzwCBgIGPlQCVDwEBAQEBAQEBHDmQMGIaJ0BosDYAsQ8RAAAY/gAKICAgICAgICAgICAg/ABNQVctU0VSSUFMCiAg/wAKICAgICAgICAgICAgAHk= modes: 1680x1050 1280x1024 1280x1024 1440x900 1440x900 1024x768 1024x768 1024x768 800x600 800x600 800x600 800x600 640x480 640x480 640x480 720x400 Desktop-Session: 'mate' '/etc/xdg/xdg-mate:/etc/xdg' '/usr/share/mate:/usr/local/share/:/usr/share/:/usr/share/mdm/' DistroRelease: Linux 18.1 Env: 'None' 'None' InstallationDate: Installed on 2016-07-13 (159 days ago) InstallationMedia: Linux Mint 18 "Sarah" - Release amd64 20160628 Load-Avg-1min: 3.87 Load-Processes-Running-Percent: 0.7% MachineType: MSI MS-7786 Package: chromium-browser 55.0.2883.87-0ubuntu0.16.04.1263 [origin: Ubuntu] PackageArchitecture: amd64 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-30-generic root=UUID=5c8e46d1-e26c-4bba-b87b-f092a8a3d7ad ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.8.0-30.32~16.04.1-generic 4.8.6 Tags: serena third-party-packages ThirdParty: True Uname: Linux 4.8.0-30-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip fax floppy lpadmin netdev plugdev sambashare scanner sudo tape vboxusers video _MarkForUpload: True dmi.bios.date: 02/04/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V2.0 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: A55M-P33 (MS-7786) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV2.0:bd02/04/2013:svnMSI:pnMS-7786:pvr1.0:rvnMSI:rnA55M-P33(MS-7786):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.name: MS-7786 dmi.product.version: 1.0 dmi.sys.vendor: MSI etcconfigcpepperflashpluginnonfree: flashso="/usr/lib/pepperflashplugin-nonfree/libpepflashplayer.so" flashversion=`strings $flashso 2> /dev/null | grep LNX | cut -d ' ' -f 2 | sed -e "s/,/./g"` CHROMIUM_FLAGS="$CHROMIUM_FLAGS --ppapi-flash-path=$flashso --ppapi-flash-version=$flashversion" modified.conffile..etc.default.chromium-browser: [deleted] mtime.conffile..etc.chromium-browser.default: 2016-07-13T18:03:09.849211 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1642413/+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 1642413] Re: Chromium uses ~100% of all cores, locks up, and does not exit correctly
grep flags /proc/cpuinfo http://dpaste.com/13GJZHH -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1642413 Title: Chromium uses ~100% of all cores, locks up, and does not exit correctly Status in chromium-browser package in Ubuntu: Incomplete Bug description: whether or not extensions are enabled, after an indeterminate amount of time chromium locks up(tabs are still rendered but browser cannot create new tabs, or navigate in existing ones) and the main process begins using 200-270% of my three cores, chrome task manager shows that no tab is using any memory and when chromium is exited the main thread does not quit and must be killed. I have reinstalled, disabled extensions/plugins, etc... nothing seems to remedy this issue. I memtested my memory and it was fine. It started happening october 2016 --- ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: MATE DRM.card0-HDMI-A-1: enabled: enabled dpms: On status: connected edid-base64: AP///wAi8A4mACANAQOAIht46gyVolZMliUaUFSt74CBgAEBAQEBAQEBAQEBAQEBMCoAmFEAKkAwcBMAUg4RAAAe/QA4TB5TDgAKICAgICAg/ABocCBMMTczMAogICAg/wBDTlAzMzJTMFJICiAgALo= modes: 1280x1024 1280x1024 1152x864 1024x768 1024x768 1024x768 832x624 800x600 800x600 800x600 640x480 640x480 640x480 720x400 DRM.card0-VGA-1: enabled: enabled dpms: On status: connected edid-base64: AP///wA6kwcAAQoRAQMIKxt4CrU0pVZKmiUQUFSvzwCBgIGPlQCVDwEBAQEBAQEBHDmQMGIaJ0BosDYAsQ8RAAAY/gAKICAgICAgICAgICAg/ABNQVctU0VSSUFMCiAg/wAKICAgICAgICAgICAgAHk= modes: 1680x1050 1280x1024 1280x1024 1440x900 1440x900 1024x768 1024x768 1024x768 800x600 800x600 800x600 800x600 640x480 640x480 640x480 720x400 Desktop-Session: 'mate' '/etc/xdg/xdg-mate:/etc/xdg' '/usr/share/mate:/usr/local/share/:/usr/share/:/usr/share/mdm/' DistroRelease: Linux 18.1 Env: 'None' 'None' InstallationDate: Installed on 2016-07-13 (159 days ago) InstallationMedia: Linux Mint 18 "Sarah" - Release amd64 20160628 Load-Avg-1min: 3.87 Load-Processes-Running-Percent: 0.7% MachineType: MSI MS-7786 Package: chromium-browser 55.0.2883.87-0ubuntu0.16.04.1263 [origin: Ubuntu] PackageArchitecture: amd64 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-30-generic root=UUID=5c8e46d1-e26c-4bba-b87b-f092a8a3d7ad ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.8.0-30.32~16.04.1-generic 4.8.6 Tags: serena third-party-packages ThirdParty: True Uname: Linux 4.8.0-30-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip fax floppy lpadmin netdev plugdev sambashare scanner sudo tape vboxusers video _MarkForUpload: True dmi.bios.date: 02/04/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V2.0 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: A55M-P33 (MS-7786) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV2.0:bd02/04/2013:svnMSI:pnMS-7786:pvr1.0:rvnMSI:rnA55M-P33(MS-7786):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.name: MS-7786 dmi.product.version: 1.0 dmi.sys.vendor: MSI etcconfigcpepperflashpluginnonfree: flashso="/usr/lib/pepperflashplugin-nonfree/libpepflashplayer.so" flashversion=`strings $flashso 2> /dev/null | grep LNX | cut -d ' ' -f 2 | sed -e "s/,/./g"` CHROMIUM_FLAGS="$CHROMIUM_FLAGS --ppapi-flash-path=$flashso --ppapi-flash-version=$flashversion" modified.conffile..etc.default.chromium-browser: [deleted] mtime.conffile..etc.chromium-browser.default: 2016-07-13T18:03:09.849211 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1642413/+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 1642413] Re: Chromium uses ~100% of all cores, locks up, and does not exit correctly
ps axfuww http://dpaste.com/1Z7642A this is WHILE the lockup is occurring, probably the most useful piece of info here -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1642413 Title: Chromium uses ~100% of all cores, locks up, and does not exit correctly Status in chromium-browser package in Ubuntu: Incomplete Bug description: whether or not extensions are enabled, after an indeterminate amount of time chromium locks up(tabs are still rendered but browser cannot create new tabs, or navigate in existing ones) and the main process begins using 200-270% of my three cores, chrome task manager shows that no tab is using any memory and when chromium is exited the main thread does not quit and must be killed. I have reinstalled, disabled extensions/plugins, etc... nothing seems to remedy this issue. I memtested my memory and it was fine. It started happening october 2016 --- ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: MATE DRM.card0-HDMI-A-1: enabled: enabled dpms: On status: connected edid-base64: AP///wAi8A4mACANAQOAIht46gyVolZMliUaUFSt74CBgAEBAQEBAQEBAQEBAQEBMCoAmFEAKkAwcBMAUg4RAAAe/QA4TB5TDgAKICAgICAg/ABocCBMMTczMAogICAg/wBDTlAzMzJTMFJICiAgALo= modes: 1280x1024 1280x1024 1152x864 1024x768 1024x768 1024x768 832x624 800x600 800x600 800x600 640x480 640x480 640x480 720x400 DRM.card0-VGA-1: enabled: enabled dpms: On status: connected edid-base64: AP///wA6kwcAAQoRAQMIKxt4CrU0pVZKmiUQUFSvzwCBgIGPlQCVDwEBAQEBAQEBHDmQMGIaJ0BosDYAsQ8RAAAY/gAKICAgICAgICAgICAg/ABNQVctU0VSSUFMCiAg/wAKICAgICAgICAgICAgAHk= modes: 1680x1050 1280x1024 1280x1024 1440x900 1440x900 1024x768 1024x768 1024x768 800x600 800x600 800x600 800x600 640x480 640x480 640x480 720x400 Desktop-Session: 'mate' '/etc/xdg/xdg-mate:/etc/xdg' '/usr/share/mate:/usr/local/share/:/usr/share/:/usr/share/mdm/' DistroRelease: Linux 18.1 Env: 'None' 'None' InstallationDate: Installed on 2016-07-13 (159 days ago) InstallationMedia: Linux Mint 18 "Sarah" - Release amd64 20160628 Load-Avg-1min: 3.87 Load-Processes-Running-Percent: 0.7% MachineType: MSI MS-7786 Package: chromium-browser 55.0.2883.87-0ubuntu0.16.04.1263 [origin: Ubuntu] PackageArchitecture: amd64 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-30-generic root=UUID=5c8e46d1-e26c-4bba-b87b-f092a8a3d7ad ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.8.0-30.32~16.04.1-generic 4.8.6 Tags: serena third-party-packages ThirdParty: True Uname: Linux 4.8.0-30-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip fax floppy lpadmin netdev plugdev sambashare scanner sudo tape vboxusers video _MarkForUpload: True dmi.bios.date: 02/04/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V2.0 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: A55M-P33 (MS-7786) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV2.0:bd02/04/2013:svnMSI:pnMS-7786:pvr1.0:rvnMSI:rnA55M-P33(MS-7786):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.name: MS-7786 dmi.product.version: 1.0 dmi.sys.vendor: MSI etcconfigcpepperflashpluginnonfree: flashso="/usr/lib/pepperflashplugin-nonfree/libpepflashplayer.so" flashversion=`strings $flashso 2> /dev/null | grep LNX | cut -d ' ' -f 2 | sed -e "s/,/./g"` CHROMIUM_FLAGS="$CHROMIUM_FLAGS --ppapi-flash-path=$flashso --ppapi-flash-version=$flashversion" modified.conffile..etc.default.chromium-browser: [deleted] mtime.conffile..etc.chromium-browser.default: 2016-07-13T18:03:09.849211 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1642413/+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 1642413] Re: Chromium uses ~100% of all cores, locks up, and does not exit correctly
ps axfwww http://dpaste.com/3RXRJBD dmesg |tail -n 50 http://dpaste.com/1RW1DYH -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1642413 Title: Chromium uses ~100% of all cores, locks up, and does not exit correctly Status in chromium-browser package in Ubuntu: Incomplete Bug description: whether or not extensions are enabled, after an indeterminate amount of time chromium locks up(tabs are still rendered but browser cannot create new tabs, or navigate in existing ones) and the main process begins using 200-270% of my three cores, chrome task manager shows that no tab is using any memory and when chromium is exited the main thread does not quit and must be killed. I have reinstalled, disabled extensions/plugins, etc... nothing seems to remedy this issue. I memtested my memory and it was fine. It started happening october 2016 --- ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: MATE DRM.card0-HDMI-A-1: enabled: enabled dpms: On status: connected edid-base64: AP///wAi8A4mACANAQOAIht46gyVolZMliUaUFSt74CBgAEBAQEBAQEBAQEBAQEBMCoAmFEAKkAwcBMAUg4RAAAe/QA4TB5TDgAKICAgICAg/ABocCBMMTczMAogICAg/wBDTlAzMzJTMFJICiAgALo= modes: 1280x1024 1280x1024 1152x864 1024x768 1024x768 1024x768 832x624 800x600 800x600 800x600 640x480 640x480 640x480 720x400 DRM.card0-VGA-1: enabled: enabled dpms: On status: connected edid-base64: AP///wA6kwcAAQoRAQMIKxt4CrU0pVZKmiUQUFSvzwCBgIGPlQCVDwEBAQEBAQEBHDmQMGIaJ0BosDYAsQ8RAAAY/gAKICAgICAgICAgICAg/ABNQVctU0VSSUFMCiAg/wAKICAgICAgICAgICAgAHk= modes: 1680x1050 1280x1024 1280x1024 1440x900 1440x900 1024x768 1024x768 1024x768 800x600 800x600 800x600 800x600 640x480 640x480 640x480 720x400 Desktop-Session: 'mate' '/etc/xdg/xdg-mate:/etc/xdg' '/usr/share/mate:/usr/local/share/:/usr/share/:/usr/share/mdm/' DistroRelease: Linux 18.1 Env: 'None' 'None' InstallationDate: Installed on 2016-07-13 (159 days ago) InstallationMedia: Linux Mint 18 "Sarah" - Release amd64 20160628 Load-Avg-1min: 3.87 Load-Processes-Running-Percent: 0.7% MachineType: MSI MS-7786 Package: chromium-browser 55.0.2883.87-0ubuntu0.16.04.1263 [origin: Ubuntu] PackageArchitecture: amd64 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-30-generic root=UUID=5c8e46d1-e26c-4bba-b87b-f092a8a3d7ad ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.8.0-30.32~16.04.1-generic 4.8.6 Tags: serena third-party-packages ThirdParty: True Uname: Linux 4.8.0-30-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip fax floppy lpadmin netdev plugdev sambashare scanner sudo tape vboxusers video _MarkForUpload: True dmi.bios.date: 02/04/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V2.0 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: A55M-P33 (MS-7786) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV2.0:bd02/04/2013:svnMSI:pnMS-7786:pvr1.0:rvnMSI:rnA55M-P33(MS-7786):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.name: MS-7786 dmi.product.version: 1.0 dmi.sys.vendor: MSI etcconfigcpepperflashpluginnonfree: flashso="/usr/lib/pepperflashplugin-nonfree/libpepflashplayer.so" flashversion=`strings $flashso 2> /dev/null | grep LNX | cut -d ' ' -f 2 | sed -e "s/,/./g"` CHROMIUM_FLAGS="$CHROMIUM_FLAGS --ppapi-flash-path=$flashso --ppapi-flash-version=$flashversion" modified.conffile..etc.default.chromium-browser: [deleted] mtime.conffile..etc.chromium-browser.default: 2016-07-13T18:03:09.849211 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1642413/+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 1553441] Re: Only one monitor working at the time (xorg-amdgpu)
lazanet, in order to allow additional upstream developers to examine the issue, at your earliest convenience, could you please test the latest upstream kernel available from http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D ? Please keep in mind the following: 1) The one to test is at the very top line at the top of the page (not the daily folder). 2) The release names are irrelevant. 3) The folder time stamps aren't indicative of when the kernel actually was released upstream. 4) Install instructions are available at https://wiki.ubuntu.com/Kernel/MainlineBuilds . If testing on your main install would be inconvenient, one may: 1) Install Ubuntu to a different partition and then test this there. 2) Backup, or clone the primary install. If the latest kernel did not allow you to test to the issue (ex. you couldn't boot into the OS) please make a comment in your report about this, and continue to test the next most recent kernel version until you can test to the issue. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this issue is fixed in the mainline kernel, please add the following tags by clicking on the yellow circle with a black pencil icon, next to the word Tags, located at the bottom of the report description: kernel-fixed-upstream kernel-fixed-upstream-X.Y-rcZ Where X, and Y are the first two numbers of the kernel version, and Z is the release candidate number if it exists. If the mainline kernel does not fix the issue, please add the following tags: kernel-bug-exists-upstream kernel-bug-exists-upstream-X.Y-rcZ Please note, an error to install the kernel does not fit the criteria of kernel-bug-exists-upstream. Also, you don't need to apport-collect further unless specifically requested to do so. It is most helpful that after testing of the latest upstream kernel is complete, you mark this report Status Confirmed. Lastly, to keep this issue relevant to upstream, please continue to test the latest mainline kernel as it becomes available. Thank you for your help. ** Tags added: zesty -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/1553441 Title: Only one monitor working at the time (xorg-amdgpu) Status in xserver-xorg-video-ati package in Ubuntu: Expired Bug description: When external monitor is connected to VGA port (AMD Radeon 7470m) internal laptop monitor stops working. I'm able to set laptop monitor as primary which disables external monitor (and vice-versa). Tried manual switch to mainline Linux 4.5 kernel, same thing. Tested on 14.04, 15.10, 16.04 with same results. WORKAROUND: Use Ubuntu 14.04 with fglrx. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 Uname: Linux 4.5.0-040500rc6-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 5 04:32:48 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: virtualbox, 5.0.14, 4.4.0-10-generic, x86_64: installed virtualbox, 5.0.14, 4.4.0-8-generic, x86_64: installed virtualbox, 5.0.14, 4.5.0-040500rc6-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7640G] [1002:9903] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Trinity [Radeon HD 7640G] [1043:106b] Advanced Micro Devices, Inc. [AMD/ATI] Seymour [Radeon HD 6400M/7400M Series] [1002:6760] (rev ff) (prog-if ff) InstallationDate: Installed on 2016-02-18 (15 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: ASUSTeK COMPUTER INC. K55DR ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.5.0-040500rc6-generic root=UUID=e0064410-4660-40b7-b961-76f320a921a6 ro amdgpu.powerplay=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/07/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 217 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: K55DR 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.:bvr217:bd09/07/2012:svnASUSTeKCOMPUTERINC.:pnK55DR:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnK55DR:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: K55DR dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.12.2+16.04.20160209-0ubun
[Desktop-packages] [Bug 1512027] Re: open of device pixma:MX7600_... failed: invalid argument
James Ring, as I don't have your hardware, I can't confirm/deny any results you reported about. Also, not providing requested information regarding your environment doesn't motivate developers to want to fix your problem. ** Description changed: Up until recently, I've been able to scan fine with my Canon Pixma MX7600. Then I upgraded to Ubuntu Wily and I've started getting: $ scanimage scanimage: open of device pixma:MX7600_192.168.2.107 failed: Invalid argument The device pings and I can get to its HTTP port. Everything appears OK. If I run strace -f -s 256 -o /tmp/trace.txt scanimage the relevant output appears to be: socket(PF_INET, SOCK_DGRAM, IPPROTO_UDP) = 204 connect(204, {sa_family=AF_INET, sin_port=htons(8612), sin_addr=inet_addr("192.168.2.107")}, 16) = 0 sendto(204, "BJNP\2\1\0\0\0\0\0\0\0\0\0\0", 16, 0, NULL, 0) = 16 select(205, [204], NULL, NULL, {4, 0}) = 1 (in [204], left {3, 998257}) recvfrom(204, "BJNP\202\1\0\0\0\0\0\0\0\0\0\20\0\1\10\0\6\4\0\0\205\316\356\343\300\250\2k", 2048, 0, NULL, N ULL) = 32 close(204) write(2, "scanimage: open of device pixma:MX7600_192.168.2.107 failed: Invalid argument\n", 78) = 78 It appears to me that the scanner is responding but the driver doesn't like the response. I'm running sane 1.0.14-11 and sane-utils 1.0.25+git201505. + + WORKAROUND: Use the PPA from + https://launchpad.net/~rolfbensch/+archive/ubuntu/sane-git -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to sane-backends in Ubuntu. https://bugs.launchpad.net/bugs/1512027 Title: open of device pixma:MX7600_... failed: invalid argument Status in sane-backends package in Ubuntu: Incomplete Bug description: Up until recently, I've been able to scan fine with my Canon Pixma MX7600. Then I upgraded to Ubuntu Wily and I've started getting: $ scanimage scanimage: open of device pixma:MX7600_192.168.2.107 failed: Invalid argument The device pings and I can get to its HTTP port. Everything appears OK. If I run strace -f -s 256 -o /tmp/trace.txt scanimage the relevant output appears to be: socket(PF_INET, SOCK_DGRAM, IPPROTO_UDP) = 204 connect(204, {sa_family=AF_INET, sin_port=htons(8612), sin_addr=inet_addr("192.168.2.107")}, 16) = 0 sendto(204, "BJNP\2\1\0\0\0\0\0\0\0\0\0\0", 16, 0, NULL, 0) = 16 select(205, [204], NULL, NULL, {4, 0}) = 1 (in [204], left {3, 998257}) recvfrom(204, "BJNP\202\1\0\0\0\0\0\0\0\0\0\20\0\1\10\0\6\4\0\0\205\316\356\343\300\250\2k", 2048, 0, NULL, N ULL) = 32 close(204) write(2, "scanimage: open of device pixma:MX7600_192.168.2.107 failed: Invalid argument\n", 78) = 78 It appears to me that the scanner is responding but the driver doesn't like the response. I'm running sane 1.0.14-11 and sane-utils 1.0.25+git201505. WORKAROUND: Use the PPA from https://launchpad.net/~rolfbensch/+archive/ubuntu/sane-git To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1512027/+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 1642413] Re: Chromium uses ~100% of all cores, locks up, and does not exit correctly
As noted in IRC, paste full process list when it's happening, since none of the chromium processes in the "grep" list are misbehaving. $ ps axfwww And get the end of dmesg $ dmesg |tail -n 50 Also, the vm swappiness might already be set to "10". It happened at default 60 at least once. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1642413 Title: Chromium uses ~100% of all cores, locks up, and does not exit correctly Status in chromium-browser package in Ubuntu: Incomplete Bug description: whether or not extensions are enabled, after an indeterminate amount of time chromium locks up(tabs are still rendered but browser cannot create new tabs, or navigate in existing ones) and the main process begins using 200-270% of my three cores, chrome task manager shows that no tab is using any memory and when chromium is exited the main thread does not quit and must be killed. I have reinstalled, disabled extensions/plugins, etc... nothing seems to remedy this issue. I memtested my memory and it was fine. It started happening october 2016 --- ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: MATE DRM.card0-HDMI-A-1: enabled: enabled dpms: On status: connected edid-base64: AP///wAi8A4mACANAQOAIht46gyVolZMliUaUFSt74CBgAEBAQEBAQEBAQEBAQEBMCoAmFEAKkAwcBMAUg4RAAAe/QA4TB5TDgAKICAgICAg/ABocCBMMTczMAogICAg/wBDTlAzMzJTMFJICiAgALo= modes: 1280x1024 1280x1024 1152x864 1024x768 1024x768 1024x768 832x624 800x600 800x600 800x600 640x480 640x480 640x480 720x400 DRM.card0-VGA-1: enabled: enabled dpms: On status: connected edid-base64: AP///wA6kwcAAQoRAQMIKxt4CrU0pVZKmiUQUFSvzwCBgIGPlQCVDwEBAQEBAQEBHDmQMGIaJ0BosDYAsQ8RAAAY/gAKICAgICAgICAgICAg/ABNQVctU0VSSUFMCiAg/wAKICAgICAgICAgICAgAHk= modes: 1680x1050 1280x1024 1280x1024 1440x900 1440x900 1024x768 1024x768 1024x768 800x600 800x600 800x600 800x600 640x480 640x480 640x480 720x400 Desktop-Session: 'mate' '/etc/xdg/xdg-mate:/etc/xdg' '/usr/share/mate:/usr/local/share/:/usr/share/:/usr/share/mdm/' DistroRelease: Linux 18.1 Env: 'None' 'None' InstallationDate: Installed on 2016-07-13 (159 days ago) InstallationMedia: Linux Mint 18 "Sarah" - Release amd64 20160628 Load-Avg-1min: 3.87 Load-Processes-Running-Percent: 0.7% MachineType: MSI MS-7786 Package: chromium-browser 55.0.2883.87-0ubuntu0.16.04.1263 [origin: Ubuntu] PackageArchitecture: amd64 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-30-generic root=UUID=5c8e46d1-e26c-4bba-b87b-f092a8a3d7ad ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.8.0-30.32~16.04.1-generic 4.8.6 Tags: serena third-party-packages ThirdParty: True Uname: Linux 4.8.0-30-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip fax floppy lpadmin netdev plugdev sambashare scanner sudo tape vboxusers video _MarkForUpload: True dmi.bios.date: 02/04/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V2.0 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: A55M-P33 (MS-7786) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV2.0:bd02/04/2013:svnMSI:pnMS-7786:pvr1.0:rvnMSI:rnA55M-P33(MS-7786):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.name: MS-7786 dmi.product.version: 1.0 dmi.sys.vendor: MSI etcconfigcpepperflashpluginnonfree: flashso="/usr/lib/pepperflashplugin-nonfree/libpepflashplayer.so" flashversion=`strings $flashso 2> /dev/null | grep LNX | cut -d ' ' -f 2 | sed -e "s/,/./g"` CHROMIUM_FLAGS="$CHROMIUM_FLAGS --ppapi-flash-path=$flashso --ppapi-flash-version=$flashversion" modified.conffile..etc.default.chromium-browser: [deleted] mtime.conffile..etc.chromium-browser.default: 2016-07-13T18:03:09.849211 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1642413/+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 1645116] Re: [Brother DCP-J715W] core dumped executing scanimage -L
Sylvain Viart: 1) Would printing via USB provide a WORKAROUND following http://support.brother.com/g/b/downloadhowto.aspx?c=fr&lang=fr&prod=dcpj715w_eu_as&os=128&dlid=dlf006642_000&flang=4&type3=566 ? You would first need to uninstall the brscan software on the 16.10 client so that it doesn't retain any of the network related configurations. 2) To clarify the networked client install instructions from https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1645116/comments/5 you first perform: cd /usr/lib64/ sudo cp -r . /usr/lib then you install the software via: sudo dpkg -i brscan3-0.2.13-1.amd64.deb sudo brsaneconfig3 -a name=scanner model=DCP-J715W ip=192.168.1.27 ** Description changed: In Xubuntu 16.10 I get a core dump executing via a terminal: scanimage -L Erreur de segmentation (core dumped) Errors report: https://errors.ubuntu.com/oops/f494063a-bdc2-11e6-ad54-fa163e30221b With Xubuntu 16.04 I don't have this problem: scanimage -L device `brother3:net1;dev0' is a Brother DCP-J715W DCP-J715W + + The Brother DCP-J715W device is WiFi connected to my router. All the + clients access the device via the network. I installed the latest Brother software from their website: http://support.brother.com/g/b/downloadlist.aspx?c=fr&lang=fr&prod=dcpj715w_eu_as&os=128&flang=English sudo dpkg -i brscan3-0.2.13-1.amd64.deb ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: sane-utils 1.0.25+git20150528-1ubuntu2 ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1 Uname: Linux 4.8.0-27-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: XFCE Date: Sun Nov 27 18:13:36 2016 InstallationDate: Installed on 2016-11-22 (4 days ago) InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) SourcePackage: sane-backends UpgradeStatus: No upgrade log present (probably fresh install) ** Description changed: In Xubuntu 16.10 I get a core dump executing via a terminal: scanimage -L Erreur de segmentation (core dumped) Errors report: https://errors.ubuntu.com/oops/f494063a-bdc2-11e6-ad54-fa163e30221b With Xubuntu 16.04 I don't have this problem: scanimage -L device `brother3:net1;dev0' is a Brother DCP-J715W DCP-J715W The Brother DCP-J715W device is WiFi connected to my router. All the clients access the device via the network. - I installed the latest Brother software from their website: + I installed the latest Brother software on the client from their website: http://support.brother.com/g/b/downloadlist.aspx?c=fr&lang=fr&prod=dcpj715w_eu_as&os=128&flang=English sudo dpkg -i brscan3-0.2.13-1.amd64.deb ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: sane-utils 1.0.25+git20150528-1ubuntu2 ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1 Uname: Linux 4.8.0-27-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: XFCE Date: Sun Nov 27 18:13:36 2016 InstallationDate: Installed on 2016-11-22 (4 days ago) InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) SourcePackage: sane-backends UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to sane-backends in Ubuntu. https://bugs.launchpad.net/bugs/1645116 Title: [Brother DCP-J715W] core dumped executing scanimage -L Status in sane-backends package in Ubuntu: Incomplete Bug description: In Xubuntu 16.10 I get a core dump executing via a terminal: scanimage -L Erreur de segmentation (core dumped) Errors report: https://errors.ubuntu.com/oops/f494063a-bdc2-11e6-ad54-fa163e30221b With Xubuntu 16.04 I don't have this problem: scanimage -L device `brother3:net1;dev0' is a Brother DCP-J715W DCP-J715W The Brother DCP-J715W device is WiFi connected to my router. All the clients access the device via the network. I installed the latest Brother software on the client from their website: http://support.brother.com/g/b/downloadlist.aspx?c=fr&lang=fr&prod=dcpj715w_eu_as&os=128&flang=English sudo dpkg -i brscan3-0.2.13-1.amd64.deb ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: sane-utils 1.0.25+git20150528-1ubuntu2 ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1 Uname: Linux 4.8.0-27-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: XFCE Date: Sun Nov 27 18:13:36 2016 InstallationDate: Installed on 2016-11-22 (4 days ago) InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) SourcePackage: sane-backends UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1645116/+subscriptions -- Mailing list:
[Desktop-packages] [Bug 1637957] Re: Chromium not working with SAML authentication
** Description changed: - In Chromium 53 (tested on Xenial and Yakkety) sync setup fails if the - account login goes through SAML authentication (the setup fails after a - successful SAML login). + Sync login is failing with SAML authentication. See - Apparently this is fixed in release 54, see - https://bugs.chromium.org/p/chromium/issues/detail?id=655960 and - https://bugs.chromium.org/p/chromium/issues/detail?id=571001 for details - about the bug. + https://bugs.chromium.org/p/chromium/issues/detail?id=677154 - Would it be possible to SRU the new version? + for details. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1637957 Title: Chromium not working with SAML authentication Status in chromium-browser package in Ubuntu: Triaged Bug description: Sync login is failing with SAML authentication. See https://bugs.chromium.org/p/chromium/issues/detail?id=677154 for details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1637957/+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 1643544] Re: HP Scanjet 7400c Scanner locks USB2 port
Wolf, could you please test for this issue via http://cdimage.ubuntu.com /daily-live/current/ ? Please retry the apport-collect in this environment and advise to the results. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to sane-backends in Ubuntu. https://bugs.launchpad.net/bugs/1643544 Title: HP Scanjet 7400c Scanner locks USB2 port Status in sane-backends package in Ubuntu: Incomplete Bug description: When trying to scan with the hp7400c (avision backend), the scanner will stop in the middle of the page, no further commands on a USB mouse or keyboard are possible. xsane will throw a I/O device error. This happens on my desktop with ubuntu 16.10 (Kernel 4.8.0-27) and my laptop (kernel 4.4.0-38) NO USB3 hardware is involved in my case, both machines have USB2-ports only, lsmod does NOT show and xhci modules loaded. I tried the command SANE_DEBUG_AVISION=8 SANE_DEBUG_SANEI_USB=5 scanimage > scanfehlerxx.txt and produced the files attached. The key statement might be: [sanei_usb] sanei_usb_read_bulk: trying to read 61054 bytes [sanei_usb] sanei_usb_read_bulk: read failed: No such device (it may have been disconnected) [avision] read 0 bytes [avision] No data arrived. This error occurs as well with Fedora 24, but NOT with debian 8.6. So it may be related with the more recent kernels and their behaviour on the USB ports. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1643544/+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 1540706] Re: Canon DR-F120 - IO Errors
Guy Taylor, the apport-collect is helpful for tracking down any wonky issues that may happen with a different environment than yours after the patch is included in Ubuntu. Despite this, regarding getting a patch included in Ubuntu, one find helpful http://packaging.ubuntu.com/html/fixing-a-bug.html . ** Changed in: sane-backends (Ubuntu) Status: Incomplete => Triaged -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to sane-backends in Ubuntu. https://bugs.launchpad.net/bugs/1540706 Title: Canon DR-F120 - IO Errors Status in sane-backends: Unknown Status in sane-backends package in Ubuntu: Triaged Bug description: The Canon DR-F120 scanner is near completely broken with the current shipped version. This is fixed upstream via: http://anonscm.debian.org/cgit/sane/sane-backends.git/commit/?id=e6b6ad9d4847e86aed8be0837a19bfada881f52d To manage notifications about this bug go to: https://bugs.launchpad.net/sane-backends/+bug/1540706/+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 1574667] Re: Mouse pointer occasionally jumps to the bottom-left corner
Just to add to my previous comment, both things (pointer jumping randomly to the lower left and left-handed touchpad unavailable) happen on the new Acer Aspire whose touchpad doesn't have buttons (or, more precisely, are integrated with the touchpad in a single surface). I have Ubuntu 16.04 on an old Toshiba and that doesn't happen (touchpad with separate buttons). Again, it does not happen in Windows 10 -- 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/1574667 Title: Mouse pointer occasionally jumps to the bottom-left corner Status in xorg package in Ubuntu: Confirmed Bug description: Sometimes the mouse pointer jumps directly to the bottom-left corner of the screen, which results in opening the trash window when clicking. This seems to be related: https://ubuntu-mate.community/t/mouse- pointer-jumps-on-clicking-touchpad/2932. Thanks, MZ ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 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: /dev/sda6: clean, 276587/40779776 files, 15261626/163117056 blocks 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 Apr 25 15:55:54 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell Skylake Integrated Graphics [1028:06b2] InstallationDate: Installed on 2016-04-23 (2 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:07dc Intel Corp. Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 002: ID 064e:920b Suyin Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 5559 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic.efi.signed root=UUID=c5bc0a1d-3fe9-4ae5-81e9-de7d141b419c ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/21/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.5 dmi.board.name: 06CMH7 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.1.5:bd12/21/2015:svnDellInc.:pnInspiron5559:pvr:rvnDellInc.:rn06CMH7:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Inspiron 5559 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-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.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2 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: Mon Apr 25 13:43:44 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id1156 vendor LGD xserver.version: 2:1.18.3-1ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1574667/+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 1637957] Re: Chromium not working with SAML authentication
This broke as a result of http://bazaar.launchpad.net/~chromium-team /chromium-browser/yakkety-working/revision/1271 The solution is to change the API keys back to their previous values. The new key isn't trusted for the purposes of an endpoint used in the SAML auth flow. ** Branch linked: lp:~chromium-team/chromium-browser/yakkety-working -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1637957 Title: Chromium not working with SAML authentication Status in chromium-browser package in Ubuntu: Triaged Bug description: In Chromium 53 (tested on Xenial and Yakkety) sync setup fails if the account login goes through SAML authentication (the setup fails after a successful SAML login). Apparently this is fixed in release 54, see https://bugs.chromium.org/p/chromium/issues/detail?id=655960 and https://bugs.chromium.org/p/chromium/issues/detail?id=571001 for details about the bug. Would it be possible to SRU the new version? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1637957/+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 1656071] Re: Expect Preview in 16.10 When I Press Space, Instead, Nothing Happens.
@seb128 I actually had gnome-sushi installed, and still nothing. Might wanna revise https://help.ubuntu.com/stable/ubuntu-help/files- preview.html to not imply Ubuntu 16.10 does previews unless someone installs gnome-sushi. That article certainly makes it sound like previewing files is part of 16.10. "The built-in preview supports most file formats for documents, images, video, and audio. In the preview, you can scroll through your documents or seek through your video and audio." The words "built-in preview" mean that, at least according to this official Ubuntu documentation, users DON'T have to install any extra packages to get preview. For me, in 16.10, gnome-sushi does nothing either. Only thing that works is gloobus-preview, which as I understand is some sort of derivative of sushi. Gloobus sucks pretty bad. Doesn't let you press arrow keys from file to file. You have to press space twice, then arrow to the next file, then space again, then space again to close preview, then arrow to the next file. Pretty sucky. Please add functional preview to default Nautilus, as ubuntu.com/stable promises, or don't promise it as a "built-in" function. -- 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/1656071 Title: Expect Preview in 16.10 When I Press Space, Instead, Nothing Happens. Status in nautilus package in Ubuntu: New Bug description: https://help.ubuntu.com/stable/ubuntu-help/files-preview.html Supposedly, a preview should happen when you press space in nautilus with a file highlighted. Instead, nothing happens. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1656071/+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 1540706] Re: Canon DR-F120 - IO Errors
** Description changed: The Canon DR-F120 scanner is near completely broken with the current - shipped version, and git head, of sane. + shipped version. + + This is fixed upstream via: + http://anonscm.debian.org/cgit/sane/sane-backends.git/commit/?id=e6b6ad9d4847e86aed8be0837a19bfada881f52d -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to sane-backends in Ubuntu. https://bugs.launchpad.net/bugs/1540706 Title: Canon DR-F120 - IO Errors Status in sane-backends: Unknown Status in sane-backends package in Ubuntu: Triaged Bug description: The Canon DR-F120 scanner is near completely broken with the current shipped version. This is fixed upstream via: http://anonscm.debian.org/cgit/sane/sane-backends.git/commit/?id=e6b6ad9d4847e86aed8be0837a19bfada881f52d To manage notifications about this bug go to: https://bugs.launchpad.net/sane-backends/+bug/1540706/+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 1654044] Re: /usr/bin/evolution:11:webkit_editor_paste_clipboard_targets_cb:request_targets_received_func:selection_received:g_closure_invoke:signal_emit_unlocked_R
** Changed in: evolution Status: Confirmed => Fix Released ** Changed in: evolution Importance: Medium => Critical -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/1654044 Title: /usr/bin/evolution:11:webkit_editor_paste_clipboard_targets_cb:request_targets_received_func:selection_received:g_closure_invoke:signal_emit_unlocked_R Status in Evolution: Fix Released Status in evolution package in Ubuntu: Triaged Status in evolution source package in Yakkety: Triaged Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding evolution. This problem was most recently seen with package version 3.22.3-0ubuntu0.1, the problem page at https://errors.ubuntu.com/problem/d7254ed93e5e4954abf5ab6d0f2d68dba28f5cf7 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/evolution/+bug/1654044/+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 1474563] Re: 1:15/1:16 fails to report support for nvidia 304 have terminated
Galen Thurber (godfree2), as requested in https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1474563/comments/40 please do not apport-collect with different hardware. Instead, file a new report. Despite this, could you please advise to my question from #40? ** Changed in: xorg (Ubuntu) Status: New => Incomplete ** Attachment removed: ".proc.driver.nvidia.params.txt" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1474563/+attachment/4803627/+files/.proc.driver.nvidia.params.txt ** Attachment removed: "BootDmesg.txt" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1474563/+attachment/4803628/+files/BootDmesg.txt ** Attachment removed: "BootLog.txt" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1474563/+attachment/4803629/+files/BootLog.txt ** Attachment removed: "CurrentDmesg.txt" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1474563/+attachment/4803630/+files/CurrentDmesg.txt ** Attachment removed: "Dependencies.txt" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1474563/+attachment/4803631/+files/Dependencies.txt ** Attachment removed: "DpkgLog.txt" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1474563/+attachment/4803632/+files/DpkgLog.txt ** Attachment removed: "LightdmDisplayLog.txt" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1474563/+attachment/4803633/+files/LightdmDisplayLog.txt ** Attachment removed: "LightdmLog.txt" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1474563/+attachment/4803634/+files/LightdmLog.txt ** Attachment removed: "Lspci.txt" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1474563/+attachment/4803635/+files/Lspci.txt ** Attachment removed: "NvidiaBugReportLog.txt" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1474563/+attachment/4803637/+files/NvidiaBugReportLog.txt ** Attachment removed: "Lsusb.txt" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1474563/+attachment/4803636/+files/Lsusb.txt ** Attachment removed: "ProcCpuinfo.txt" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1474563/+attachment/4803638/+files/ProcCpuinfo.txt ** Attachment removed: "ProcEnviron.txt" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1474563/+attachment/4803639/+files/ProcEnviron.txt ** Attachment removed: "ProcInterrupts.txt" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1474563/+attachment/4803640/+files/ProcInterrupts.txt ** Attachment removed: "ProcModules.txt" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1474563/+attachment/4803641/+files/ProcModules.txt ** Attachment removed: "UdevDb.txt" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1474563/+attachment/4803642/+files/UdevDb.txt ** Attachment removed: "UdevLog.txt" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1474563/+attachment/4803643/+files/UdevLog.txt ** Attachment removed: "XorgLog.txt" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1474563/+attachment/4803644/+files/XorgLog.txt ** Attachment removed: "XorgLogOld.txt" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1474563/+attachment/4803645/+files/XorgLogOld.txt ** Attachment removed: "Xrandr.txt" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1474563/+attachment/4803646/+files/Xrandr.txt ** Attachment removed: "nvidia-bug-report.log.gz" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1474563/+attachment/4803647/+files/nvidia-bug-report.log.gz ** Attachment removed: "xdpyinfo.txt" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1474563/+attachment/4803648/+files/xdpyinfo.txt ** Attachment removed: "xserver.devices.txt" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1474563/+attachment/4803649/+files/xserver.devices.txt ** Description changed: The conclusion is that xorg versions above 1:12 fail to support legacy driver 304. Therefore it should be reported in release notes for users of such hardware that they will be unable to use hardware 3D acceleration. --- .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: u'/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 304.131 Sun Nov 8 21:43:33 PST 2015 GCC version: gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04.3) ApportVersion: 2.14.1-0ubuntu3.21 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE DistUpgraded: 2015-04-21 17:09:45,057 DEBUG enabling apt cron job DistroCodename: trusty DistroRelease: Ubuntu 14.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation G71 [GeForce 7900 GS] [10de:0292] (rev a1) (prog-if 00 [VGA controller]) Subsystem: NVIDIA Corporation Device [10de:0370] InstallationDate: Installed on 2013-06-24 (1164 days ago) InstallationMedia: Xubuntu 12.04.2 L
[Desktop-packages] [Bug 378958] Re: xorg 100% cpu when scrolling in rdesktop
Péter (xfaeznimltegstg), as this report is closed, it doesn't affect you. However, regarding your issue, it will help immensely if you filed a new report with Ubuntu by ensuring you have the package xdiagnose installed, and that you click the Yes button for attaching additional debugging information running the following from a terminal: ubuntu-bug xorg Also, please feel free to subscribe me to it. For more on why this is helpful, please see https://wiki.ubuntu.com/ReportingBugs. ** Attachment removed: "Xorg.0.log.old" https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/378958/+attachment/4803586/+files/Xorg.0.log.old ** Attachment removed: "Xorg.0.log" https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/378958/+attachment/4803585/+files/Xorg.0.log ** Attachment removed: "lspci_out" https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/378958/+attachment/4803584/+files/lspci_out -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/378958 Title: xorg 100% cpu when scrolling in rdesktop Status in xserver-xorg-video-ati package in Ubuntu: Invalid Bug description: After upgrading from Ubuntu 8.10 to 9.04, my rdesktops to Windows servers are unusable. Screen refreshes inside rdesktop are awfully slow. Scrolling a logfile causes xorg to take 100% cpu. I'm using Ubuntu 9.04 as default as possible, no xorg.conf editing or other vga drivers. I have a ThinkPad Z60m with an ATI x600 mobility: root@tp:~# lspci |grep -i vga 01:00.0 VGA compatible controller: ATI Technologies Inc M24 1P [Radeon Mobility X600] Very easy to reproduce with default settings: - launch laptop from Ubuntu 9.04 live cd - open rdesktop or tsclient to a Windows machine - open a large logfile or a putty window - watch how the screen in building up line per line, slowing down even more near the buttom of the screen I tested other ThinkPads with other vga cards, they don't have this issue. - Z61m with ATI x1400 = ok - R61 with nVidia = ok A few more observations: - 2D and 3D in Ubuntu works fine with the new default driver (great job :-) - Visual Effects (Compiz?) work fine, on 'normal' and even 'extra', but have no effect on the reported issue. I always disable the visial effects. - scrolling in other applications works fine and fast (FF3, gedit, terminal,...) - I use rdesktop in a windowed mode (1280x960), RDPv5 - I tried rdesktop bitmap caching enable/disable, same for both - when I launch a Windows RDP inside my rdesktop, this 2nd RDP does NOT suffer the same problem To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/378958/+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 1655828] Re: Mouse flickers and disappears on primary monitor when additional monitor is connected
Mauricio Maluff Masi, in addition to 4), could you please provide the full manufacturer and model as noted on the sticker of the DisplayLink adapter itself (not from the Bug Description, or the result of a terminal command)? ** Tags added: xenial ** Description changed: - Any time I connect an additional monitor via my Displaylink adapter, the - mouse flickers and disappears in the primary monitor. It displays - perfectly on the additional monitor. It also displays perfectly after - the additional monitor is disconnected. + Any time I connect my Acer G236HL LCD monitor with VGA via my + Displaylink adapter (DisplayLink driver version 1.2.65), the mouse + flickers and disappears in the primary monitor. It displays perfectly on + the additional monitor. It also displays perfectly after the additional + monitor is disconnected. I see that there are a number of similar bug reports: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1645891 https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1629300 https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1278223 https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1613001 - - I'd be willing to help track it down. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xorg 1:7.7+13ubuntu4 ProcVersionSignature: Ubuntu 4.8.0-34.36-generic 4.8.11 Uname: Linux 4.8.0-34-generic x86_64 NonfreeKernelModules: wl .tmp.unity_support_test.0: - + ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Tue Jan 10 22:34:58 2017 DistUpgraded: 2016-10-23 13:14:39,472 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process "./xorg_fix_proprietary.py" (No such file or directory) (8)) DistributionChannelDescriptor: - # This is a distribution channel descriptor - # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor - canonical-oem-somerville-trusty-amd64-20140620-0 + # This is a distribution channel descriptor + # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor + canonical-oem-somerville-trusty-amd64-20140620-0 DistroCodename: yakkety DistroVariant: ubuntu DkmsStatus: - bcmwl, 6.30.223.248+bdcom, 4.8.0-32-generic, x86_64: installedError! Could not locate dkms.conf file. - File: does not exist. - - bcmwl, 6.30.223.248+bdcom, 4.8.0-34-generic, x86_64: installed + bcmwl, 6.30.223.248+bdcom, 4.8.0-32-generic, x86_64: installedError! Could not locate dkms.conf file. + File: does not exist. + + bcmwl, 6.30.223.248+bdcom, 4.8.0-34-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: - Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) -Subsystem: Dell HD Graphics 5500 [1028:0665] + Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) + Subsystem: Dell HD Graphics 5500 [1028:0665] InstallationDate: Installed on 2016-01-26 (350 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20140620-04:25 MachineType: Dell Inc. XPS 13 9343 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-34-generic root=UUID=485e1110-0879-413f-b537-6b5b97353478 ro quiet splash usbcore.autosuspend=-1 "acpi_osi=Windows 2013" vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to yakkety on 2016-10-23 (79 days ago) XorgLogOld: - + dmi.bios.date: 08/29/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: A09 dmi.board.name: 0TM99H dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA09:bd08/29/2016:svnDellInc.:pnXPS139343:pvr:rvnDellInc.:rn0TM99H:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 13 9343 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-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6.1 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 xserver.bootTime: Tue Jan 10 20:18:19 2017 xserver.configfile: default xserver.errors: modeset(G0): glamor initialization failed xserver.logfile: /var/log/Xorg.0.log xserver.outputs: - product id
[Desktop-packages] [Bug 1642413] Re: Chromium uses ~100% of all cores, locks up, and does not exit correctly
now the lockup is happening regardless of whether or not I go to virtual terminal. someone pls help, I don't know what to do here -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1642413 Title: Chromium uses ~100% of all cores, locks up, and does not exit correctly Status in chromium-browser package in Ubuntu: Incomplete Bug description: whether or not extensions are enabled, after an indeterminate amount of time chromium locks up(tabs are still rendered but browser cannot create new tabs, or navigate in existing ones) and the main process begins using 200-270% of my three cores, chrome task manager shows that no tab is using any memory and when chromium is exited the main thread does not quit and must be killed. I have reinstalled, disabled extensions/plugins, etc... nothing seems to remedy this issue. I memtested my memory and it was fine. It started happening october 2016 --- ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: MATE DRM.card0-HDMI-A-1: enabled: enabled dpms: On status: connected edid-base64: AP///wAi8A4mACANAQOAIht46gyVolZMliUaUFSt74CBgAEBAQEBAQEBAQEBAQEBMCoAmFEAKkAwcBMAUg4RAAAe/QA4TB5TDgAKICAgICAg/ABocCBMMTczMAogICAg/wBDTlAzMzJTMFJICiAgALo= modes: 1280x1024 1280x1024 1152x864 1024x768 1024x768 1024x768 832x624 800x600 800x600 800x600 640x480 640x480 640x480 720x400 DRM.card0-VGA-1: enabled: enabled dpms: On status: connected edid-base64: AP///wA6kwcAAQoRAQMIKxt4CrU0pVZKmiUQUFSvzwCBgIGPlQCVDwEBAQEBAQEBHDmQMGIaJ0BosDYAsQ8RAAAY/gAKICAgICAgICAgICAg/ABNQVctU0VSSUFMCiAg/wAKICAgICAgICAgICAgAHk= modes: 1680x1050 1280x1024 1280x1024 1440x900 1440x900 1024x768 1024x768 1024x768 800x600 800x600 800x600 800x600 640x480 640x480 640x480 720x400 Desktop-Session: 'mate' '/etc/xdg/xdg-mate:/etc/xdg' '/usr/share/mate:/usr/local/share/:/usr/share/:/usr/share/mdm/' DistroRelease: Linux 18.1 Env: 'None' 'None' InstallationDate: Installed on 2016-07-13 (159 days ago) InstallationMedia: Linux Mint 18 "Sarah" - Release amd64 20160628 Load-Avg-1min: 3.87 Load-Processes-Running-Percent: 0.7% MachineType: MSI MS-7786 Package: chromium-browser 55.0.2883.87-0ubuntu0.16.04.1263 [origin: Ubuntu] PackageArchitecture: amd64 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-30-generic root=UUID=5c8e46d1-e26c-4bba-b87b-f092a8a3d7ad ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.8.0-30.32~16.04.1-generic 4.8.6 Tags: serena third-party-packages ThirdParty: True Uname: Linux 4.8.0-30-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip fax floppy lpadmin netdev plugdev sambashare scanner sudo tape vboxusers video _MarkForUpload: True dmi.bios.date: 02/04/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V2.0 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: A55M-P33 (MS-7786) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV2.0:bd02/04/2013:svnMSI:pnMS-7786:pvr1.0:rvnMSI:rnA55M-P33(MS-7786):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.name: MS-7786 dmi.product.version: 1.0 dmi.sys.vendor: MSI etcconfigcpepperflashpluginnonfree: flashso="/usr/lib/pepperflashplugin-nonfree/libpepflashplayer.so" flashversion=`strings $flashso 2> /dev/null | grep LNX | cut -d ' ' -f 2 | sed -e "s/,/./g"` CHROMIUM_FLAGS="$CHROMIUM_FLAGS --ppapi-flash-path=$flashso --ppapi-flash-version=$flashversion" modified.conffile..etc.default.chromium-browser: [deleted] mtime.conffile..etc.chromium-browser.default: 2016-07-13T18:03:09.849211 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1642413/+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 1369162] Re: sane-backend DCP-7065-DN not found
David Oxland, this bug report is being closed due to your last comment https://bugs.launchpad.net/ubuntu/+source/sane- backends/+bug/1369162/comments/3 regarding this being fixed with a reinstall of the software. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time to report this bug and helping to make Ubuntu better. Please submit any future bugs you may find. ** Changed in: sane-backends (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to sane-backends in Ubuntu. https://bugs.launchpad.net/bugs/1369162 Title: sane-backend DCP-7065-DN not found Status in sane-backends package in Ubuntu: Invalid Bug description: Brother Scanner/printer remains unfound/unusable despite all steps taken. These include installation :dpkg i forceall (scannerdrivername) and scanskey ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: libsane 1.0.23-3ubuntu3.1 ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6 Uname: Linux 3.13.0-35-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.4 Architecture: amd64 CurrentDesktop: Unity Date: Sat Sep 13 13:51:15 2014 InstallationDate: Installed on 2014-06-01 (103 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) SourcePackage: sane-backends UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.sane.d.dll.conf: 2014-09-08T16:08:46.568468 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1369162/+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 1574667] Re: Mouse pointer occasionally jumps to the bottom-left corner
Also happening to me. Just bought an Acer Aspire F with intel i3 core. Installed Ubuntu 16.04 (Dual Boot) Touch pad works perfectly well with Windows 10 (ouch) Also I have found impossible to chancge touch pad to left-handed (I know it's another topic, but I have searched TONS of pages and found nothing). Whatever... the pointer jumping randomly and opening Trash can is certainly a BIG issue. Just because of that I avoid using Ubuntu on that laptop as much as possible. -- 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/1574667 Title: Mouse pointer occasionally jumps to the bottom-left corner Status in xorg package in Ubuntu: Confirmed Bug description: Sometimes the mouse pointer jumps directly to the bottom-left corner of the screen, which results in opening the trash window when clicking. This seems to be related: https://ubuntu-mate.community/t/mouse- pointer-jumps-on-clicking-touchpad/2932. Thanks, MZ ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 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: /dev/sda6: clean, 276587/40779776 files, 15261626/163117056 blocks 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 Apr 25 15:55:54 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell Skylake Integrated Graphics [1028:06b2] InstallationDate: Installed on 2016-04-23 (2 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:07dc Intel Corp. Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 002: ID 064e:920b Suyin Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 5559 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic.efi.signed root=UUID=c5bc0a1d-3fe9-4ae5-81e9-de7d141b419c ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/21/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.5 dmi.board.name: 06CMH7 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.1.5:bd12/21/2015:svnDellInc.:pnInspiron5559:pvr:rvnDellInc.:rn06CMH7:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Inspiron 5559 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-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.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2 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: Mon Apr 25 13:43:44 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id1156 vendor LGD xserver.version: 2:1.18.3-1ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1574667/+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 1640320] Re: FTBFS in zesty
I don't see evidence of this error in the amd64 build log at https://launchpadlibrarian.net/298782129/buildlog_ubuntu-zesty-amd64 .location-service_3.0.0+16.10.20160912-0ubuntu2_BUILDING.txt.gz. However, the package does FTBFS due to this bug https://bugs.launchpad.net/ubuntu/+source/googletest/+bug/1644062 Looks like it may need some CMakeLists changes to be compatible with GoogleTest 1.8 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to location-service in Ubuntu. https://bugs.launchpad.net/bugs/1640320 Title: FTBFS in zesty Status in location-service package in Ubuntu: New Bug description: FTBFS in zesty during a no change rebuild against new boost Please see build logs at: https://launchpad.net/ubuntu/+source /location-service/3.0.0+16.10.20160912-0ubuntu2 Please help fix this [ 10%] Building CXX object src/location_service/com/ubuntu/location/CMakeFiles/ubuntu-location-service-connectivity.dir/connectivity/wireless_network.cpp.o cd /<>/location-service-3.0.0+16.10.20160912/obj-x86_64-linux-gnu/src/location_service/com/ubuntu/location && /usr/bin/g++ -DCOM_UBUNTU_LOCATION_SERVICE_HAVE_NET_CPP=1 -DCOM_UBUNTU_LOCATION_SERVICE_HAVE_UBUNTU_PLATFORM_HARDWARE_API -DCOM_UBUNTU_LOCATION_SERVICE_PROVIDERS_GEOCLUE -DCOM_UBUNTU_LOCATION_SERVICE_PROVIDERS_GPS -Dubuntu_location_service_connectivity_EXPORTS -I/<>/location-service-3.0.0+16.10.20160912/3rd-party -I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -I/usr/include/json-c -I/<>/location-service-3.0.0+16.10.20160912/include/location_service -I/<>/location-service-3.0.0+16.10.20160912/src/location_service -I/<>/location-service-3.0.0+16.10.20160912/obj-x86_64-linux-gnu/src/location_service -I/usr/include/ubuntu -g -O2 -fdebug-prefix-map=/<>/location-service-3.0.0+16.10.20160912=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -std=c++11 -Wall -fno-strict-aliasing -pedantic -Wextra -fPIC -Wno-error=unused-local-typedefs -fPIC -o CMakeFiles/ubuntu-location-service-connectivity.dir/connectivity/wireless_network.cpp.o -c /<>/location-service-3.0.0+16.10.20160912/src/location_service/com/ubuntu/location/connectivity/wireless_network.cpp In file included from /<>/location-service-3.0.0+16.10.20160912/src/location_service/com/ubuntu/location/providers/gps/sntp_client.h:21:0, from /<>/location-service-3.0.0+16.10.20160912/src/location_service/com/ubuntu/location/providers/gps/sntp_client.cpp:19: /<>/location-service-3.0.0+16.10.20160912/src/location_service/com/ubuntu/location/providers/gps/android_hardware_abstraction_layer.h:57:14: error: ‘vector’ in namespace ‘std’ does not name a template type std::vector xtra_hosts ^~ /<>/location-service-3.0.0+16.10.20160912/src/location_service/com/ubuntu/location/providers/gps/android_hardware_abstraction_layer.h:59:10: warning: extra ‘;’ [-Wpedantic] }; ^ /<>/location-service-3.0.0+16.10.20160912/src/location_service/com/ubuntu/location/providers/gps/android_hardware_abstraction_layer.h:66:18: error: ‘vector’ in namespace ‘std’ does not name a template type virtual std::vector download_xtra_data(const Configuration& config) = 0; ^~ make -f po/CMakeFiles/pofiles_70.dir/build.make po/CMakeFiles/pofiles_70.dir/depend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/location-service/+bug/1640320/+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 1600136] Re: App indicator does not show icon for Qt apps or with custom icons
The attachment "qdbustrayicon-try-to-save-temp-icons-in-readable- location.debdiff" seems to be a debdiff. The ubuntu-sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff. If the attachment isn't a patch, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issue please contact him.] ** Tags added: patch -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to sni-qt in Ubuntu. https://bugs.launchpad.net/bugs/1600136 Title: App indicator does not show icon for Qt apps or with custom icons Status in Qt: In Progress Status in Snappy: New Status in appmenu-qt5 package in Ubuntu: Fix Released Status in libappindicator package in Ubuntu: Fix Released Status in qtbase-opensource-src package in Ubuntu: In Progress Status in snapd package in Ubuntu: In Progress Status in sni-qt package in Ubuntu: Fix Released Bug description: Snaps that use the app indicator area via Qt can't display their icon there. Steps to reproduce and screenshot: https://github.com/nuttyartist/notes/pull/77 Some research: - Uses http://doc.qt.io/qt-5/qsystemtrayicon.html - The indicator icon is created under /tmp under a randomly generated directory name didrocks mentions also: 1. The application says "this is my menu, and here is my icon at that address", the address being /tmp/blablabla 2. appindicator receives the bus messages 3. and says "let's have a look at this icon at that address" 4. BUT! /tmp in the snap is different form system /tmp To manage notifications about this bug go to: https://bugs.launchpad.net/qt/+bug/1600136/+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 1597437] Re: X with nouveau driver, 2 nvidia cards, 4 monitors, does not use all monitors
I can confirm that the patch in #5 works. I've tested it on the same system (updated to 16.04.1 with all current updates), same video cards, same monitors, as described in the original bug description section above. (long version:) Re #5, thanks for trying this and updating with your result! You've now emboldened me to try this too, but you just say "I compiled the driver", you don't specifically say how :-( So I've got the source folders with the apt source command you mentioned, applied the patch, and from the (patched) xserver-xorg-video- nouveau-1.0.12 folder, I've run .configure but I get the following: [lots of "checking... yes" lines] ... Package xorg-macros was not found in the pkg-config search path. Perhaps you should add the directory containing `xorg-macros.pc' to the PKG_CONFIG_PATH environment variable No package 'xorg-macros' found ... Package xorg-server was not found in the pkg-config search path. Perhaps you should add the directory containing `xorg-server.pc' to the PKG_CONFIG_PATH environment variable No package 'xorg-server' found checking if RANDR is defined... no Package xorg-server was not found in the pkg-config search path. Perhaps you should add the directory containing `xorg-server.pc' to the PKG_CONFIG_PATH environment variable No package 'xorg-server' found checking if RENDER is defined... no Package xorg-server was not found in the pkg-config search path. Perhaps you should add the directory containing `xorg-server.pc' to the PKG_CONFIG_PATH environment variable No package 'xorg-server' found checking if XV is defined... no Package xorg-server was not found in the pkg-config search path. Perhaps you should add the directory containing `xorg-server.pc' to the PKG_CONFIG_PATH environment variable No package 'xorg-server' found checking if DPMSExtension is defined... no Package xorg-server was not found in the pkg-config search path. Perhaps you should add the directory containing `xorg-server.pc' to the PKG_CONFIG_PATH environment variable No package 'xorg-server' found checking if DRI2 is defined... no checking for LIBDRM... yes checking for LIBDRM_NOUVEAU... yes checking for XORG... no configure: error: Package requirements (xorg-server >= 1.8 xproto fontsproto libdrm ) were not met: No package 'xorg-server' found No package 'fontsproto' found Consider adjusting the PKG_CONFIG_PATH environment variable if you installed software in a non-standard prefix. Alternatively, you may set the environment variables XORG_CFLAGS and XORG_LIBS to avoid the need to call pkg-config. See the pkg-config man page for more details. Do you recall which -dev packages you had to install for this to work? Okay google-answering my own question (for other readers)... apt-get install xserver-xorg-dev x11proto-core-dev x11proto-fonts-dev After this, ./configure and make worked, I moved the new src/.libs/nouveau_drv.so to replace the one in /usr/lib/xorg/modules/drivers/ as you said, and upon reboot, the 4th monitor works. Thanks! I've been sitting with it dark for months!!! One concern though, is why is the new version 10x bigger than the old? Is the default ./configure settings set to leave debug flags on or something? and should I have done this differently? $ ls -la nouveau_drv.so* -rw-r--r-- 1 root root 2332552 Jan 13 12:34 nouveau_drv.so -rw-r--r-- 1 root root 214960 Mar 3 2016 nouveau_drv.so.orig But besides that, I'm thrilled. Please, developers, package managers, etc., help get this out to the less techy users out there. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/1597437 Title: X with nouveau driver, 2 nvidia cards, 4 monitors, does not use all monitors Status in xserver-xorg-video-nouveau package in Ubuntu: Confirmed Bug description: Ubuntu 16.04 with two identical nvidia cards and four identical LG monitors. At the graphical login screen only the first 3 monitors appear alive (i.e. have backgrounds and the mouse can move to them). A pop-up appears: "Could not switch the monitor configuration" (bold text with do-not-enter icon) "could not set the configuration for CRTC 64" (normal text) After logging in (gnome flashback Metacity session) the same 3 monitors are alive and the same pop-up appears. Using Applications > System Tools > System Settings > Displays, the 4th monitor is shown in grey and when clicking it, it shows that the slider is off. When turning it to On (leaving default resolution and rotation) and clicking Apply "The selected configuration for displays could not be applied" (bold text with do-not-enter icon) "could not set the configuration for CRTC 64" (normal text) a few seconds later (if the first one is not closed) another pop up with do-not-enter icon: "Failed to apply configuration: %s" "Timeout was reached" or trying again, if the first pop-up is closed within a few
[Desktop-packages] [Bug 1656370] Re: merging symbolic link with target folder of same name destroys folder
I reposted this as a comment for Gnome Bugzilla bug #632323, which was opened in 10/2010 and appears to describe an identical problem. Six years in it doesn't seem to have been addressed. Thanks! -- 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/1656370 Title: merging symbolic link with target folder of same name destroys folder Status in nautilus package in Ubuntu: New Bug description: I recently lost a directory full of valuable files. I'm running ubuntu 16.04 and using nautilus 3.14.3 Here's how to replicate this bug. From a terminal window starting in my home directory: mkdir useful cd useful touch stuff1.txt touch stuff2.txt cd ../Desktop ln -s ../useful/ useful Now I have a symbolic link on my desktop "useful" that links to directory "useful" containing two files. From nautilus: - Go to Desktop, select the link useful - press Ctrl-X to copy - Go to Home - press Ctrl-V to paste - dialog box appears: Merge folder "useful" - press Merge button (the default) directory useful has now been replaced with a symbolic link pointing to itself, and all its contents are gone. Now in nautilus I press Ctrl-Z to undo. Symbolic link "useful" reappears on the Desktop, but the target folder is not reconstructed. Why is this a important bug: 1. Merge dialog gives no indication that the source is a symbolic link. Instead it asks the user if wants to merge the files in two folders. 2. Continuing with the merge is the default option. 3. After the merge the symbolic link survives and the folder and its contents are utterly gone. They cannot be found in the trash. 4. Undo does not restore the folder or its files, just relocates the symbolic link. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1656370/+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 1600136] Re: App indicator does not show icon for Qt apps or with custom icons
Upstream fix for pure Qt apps (when not including appmenu-qt5) is proposed at https://codereview.qt-project.org/#/c/182307/. Here's the patch for the ubuntu package too. ** Also affects: qtbase-opensource-src (Ubuntu) Importance: Undecided Status: New ** Changed in: qtbase-opensource-src (Ubuntu) Status: New => In Progress ** Changed in: qtbase-opensource-src (Ubuntu) Importance: Undecided => High ** Changed in: qtbase-opensource-src (Ubuntu) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) ** Also affects: qt Importance: Undecided Status: New ** Changed in: qt Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) ** Changed in: qt Status: New => In Progress ** Patch added: "qdbustrayicon-try-to-save-temp-icons-in-readable-location.debdiff" https://bugs.launchpad.net/qt/+bug/1600136/+attachment/4803964/+files/qdbustrayicon-try-to-save-temp-icons-in-readable-location.debdiff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to sni-qt in Ubuntu. https://bugs.launchpad.net/bugs/1600136 Title: App indicator does not show icon for Qt apps or with custom icons Status in Qt: In Progress Status in Snappy: New Status in appmenu-qt5 package in Ubuntu: Fix Released Status in libappindicator package in Ubuntu: Fix Released Status in qtbase-opensource-src package in Ubuntu: In Progress Status in snapd package in Ubuntu: In Progress Status in sni-qt package in Ubuntu: Fix Released Bug description: Snaps that use the app indicator area via Qt can't display their icon there. Steps to reproduce and screenshot: https://github.com/nuttyartist/notes/pull/77 Some research: - Uses http://doc.qt.io/qt-5/qsystemtrayicon.html - The indicator icon is created under /tmp under a randomly generated directory name didrocks mentions also: 1. The application says "this is my menu, and here is my icon at that address", the address being /tmp/blablabla 2. appindicator receives the bus messages 3. and says "let's have a look at this icon at that address" 4. BUT! /tmp in the snap is different form system /tmp To manage notifications about this bug go to: https://bugs.launchpad.net/qt/+bug/1600136/+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 1656360] Re: Possible erroneous information in software description
Thanks but that's a bug in the krita snap description not in gnome- software ** Changed in: gnome-software (Ubuntu) Importance: Undecided => Low ** Changed in: gnome-software (Ubuntu) Status: New => Invalid -- 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/1656360 Title: Possible erroneous information in software description Status in gnome-software package in Ubuntu: Invalid Bug description: In the description of Krita (snap package) reads this message "...and due to a bug in Ubuntu, this snap doesn't work with proprietary video drivers, e.g. for NVidia." I'm using NVIDIA 367.57 and works without problems ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: gnome-software 3.20.1+git20161013.0.d77d6cf-0ubuntu2 ProcVersionSignature: Ubuntu 4.8.0-34.36-generic 4.8.11 Uname: Linux 4.8.0-34-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 CurrentDesktop: Unity Date: Fri Jan 13 13:54:12 2017 InstallationDate: Installed on 2016-11-04 (70 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1656360/+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 1656370] Re: merging symbolic link with target folder of same name destroys folder
Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance. ** Changed in: nautilus (Ubuntu) Importance: Undecided => High -- 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/1656370 Title: merging symbolic link with target folder of same name destroys folder Status in nautilus package in Ubuntu: New Bug description: I recently lost a directory full of valuable files. I'm running ubuntu 16.04 and using nautilus 3.14.3 Here's how to replicate this bug. From a terminal window starting in my home directory: mkdir useful cd useful touch stuff1.txt touch stuff2.txt cd ../Desktop ln -s ../useful/ useful Now I have a symbolic link on my desktop "useful" that links to directory "useful" containing two files. From nautilus: - Go to Desktop, select the link useful - press Ctrl-X to copy - Go to Home - press Ctrl-V to paste - dialog box appears: Merge folder "useful" - press Merge button (the default) directory useful has now been replaced with a symbolic link pointing to itself, and all its contents are gone. Now in nautilus I press Ctrl-Z to undo. Symbolic link "useful" reappears on the Desktop, but the target folder is not reconstructed. Why is this a important bug: 1. Merge dialog gives no indication that the source is a symbolic link. Instead it asks the user if wants to merge the files in two folders. 2. Continuing with the merge is the default option. 3. After the merge the symbolic link survives and the folder and its contents are utterly gone. They cannot be found in the trash. 4. Undo does not restore the folder or its files, just relocates the symbolic link. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1656370/+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 1656370] [NEW] merging symbolic link with target folder of same name destroys folder
Public bug reported: I recently lost a directory full of valuable files. I'm running ubuntu 16.04 and using nautilus 3.14.3 Here's how to replicate this bug. From a terminal window starting in my home directory: mkdir useful cd useful touch stuff1.txt touch stuff2.txt cd ../Desktop ln -s ../useful/ useful Now I have a symbolic link on my desktop "useful" that links to directory "useful" containing two files. >From nautilus: - Go to Desktop, select the link useful - press Ctrl-X to copy - Go to Home - press Ctrl-V to paste - dialog box appears: Merge folder "useful" - press Merge button (the default) directory useful has now been replaced with a symbolic link pointing to itself, and all its contents are gone. Now in nautilus I press Ctrl-Z to undo. Symbolic link "useful" reappears on the Desktop, but the target folder is not reconstructed. Why is this a important bug: 1. Merge dialog gives no indication that the source is a symbolic link. Instead it asks the user if wants to merge the files in two folders. 2. Continuing with the merge is the default option. 3. After the merge the symbolic link survives and the folder and its contents are utterly gone. They cannot be found in the trash. 4. Undo does not restore the folder or its files, just relocates the symbolic link. ** Affects: nautilus (Ubuntu) Importance: High Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1656370 Title: merging symbolic link with target folder of same name destroys folder Status in nautilus package in Ubuntu: New Bug description: I recently lost a directory full of valuable files. I'm running ubuntu 16.04 and using nautilus 3.14.3 Here's how to replicate this bug. From a terminal window starting in my home directory: mkdir useful cd useful touch stuff1.txt touch stuff2.txt cd ../Desktop ln -s ../useful/ useful Now I have a symbolic link on my desktop "useful" that links to directory "useful" containing two files. From nautilus: - Go to Desktop, select the link useful - press Ctrl-X to copy - Go to Home - press Ctrl-V to paste - dialog box appears: Merge folder "useful" - press Merge button (the default) directory useful has now been replaced with a symbolic link pointing to itself, and all its contents are gone. Now in nautilus I press Ctrl-Z to undo. Symbolic link "useful" reappears on the Desktop, but the target folder is not reconstructed. Why is this a important bug: 1. Merge dialog gives no indication that the source is a symbolic link. Instead it asks the user if wants to merge the files in two folders. 2. Continuing with the merge is the default option. 3. After the merge the symbolic link survives and the folder and its contents are utterly gone. They cannot be found in the trash. 4. Undo does not restore the folder or its files, just relocates the symbolic link. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1656370/+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 1553441] Re: Only one monitor working at the time (xorg-amdgpu)
** Attachment added: "systemDetails.png" https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1553441/+attachment/4803961/+files/systemDetails.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/1553441 Title: Only one monitor working at the time (xorg-amdgpu) Status in xserver-xorg-video-ati package in Ubuntu: Expired Bug description: When external monitor is connected to VGA port (AMD Radeon 7470m) internal laptop monitor stops working. I'm able to set laptop monitor as primary which disables external monitor (and vice-versa). Tried manual switch to mainline Linux 4.5 kernel, same thing. Tested on 14.04, 15.10, 16.04 with same results. WORKAROUND: Use Ubuntu 14.04 with fglrx. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 Uname: Linux 4.5.0-040500rc6-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 5 04:32:48 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: virtualbox, 5.0.14, 4.4.0-10-generic, x86_64: installed virtualbox, 5.0.14, 4.4.0-8-generic, x86_64: installed virtualbox, 5.0.14, 4.5.0-040500rc6-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7640G] [1002:9903] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Trinity [Radeon HD 7640G] [1043:106b] Advanced Micro Devices, Inc. [AMD/ATI] Seymour [Radeon HD 6400M/7400M Series] [1002:6760] (rev ff) (prog-if ff) InstallationDate: Installed on 2016-02-18 (15 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: ASUSTeK COMPUTER INC. K55DR ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.5.0-040500rc6-generic root=UUID=e0064410-4660-40b7-b961-76f320a921a6 ro amdgpu.powerplay=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/07/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 217 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: K55DR 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.:bvr217:bd09/07/2012:svnASUSTeKCOMPUTERINC.:pnK55DR:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnK55DR:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: K55DR dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. 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-1ubuntu3 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.6.1-1ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160218-1ubuntu3 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Sat Mar 5 04:27:41 2016 xserver.configfile: default xserver.errors: RADEON(G0): [XvMC] Failed to initialize extension. xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.1-1ubuntu3 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1553441/+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 1553441] Re: Only one monitor working at the time (xorg-amdgpu)
Same problem occurs at 17.04 daily build (details tab shows 16.10 for some reason, even though lsbrelease reports right version string) ** Attachment added: "xorglog1704.txt" https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1553441/+attachment/4803960/+files/xorglog1704.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/1553441 Title: Only one monitor working at the time (xorg-amdgpu) Status in xserver-xorg-video-ati package in Ubuntu: Expired Bug description: When external monitor is connected to VGA port (AMD Radeon 7470m) internal laptop monitor stops working. I'm able to set laptop monitor as primary which disables external monitor (and vice-versa). Tried manual switch to mainline Linux 4.5 kernel, same thing. Tested on 14.04, 15.10, 16.04 with same results. WORKAROUND: Use Ubuntu 14.04 with fglrx. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 Uname: Linux 4.5.0-040500rc6-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 5 04:32:48 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: virtualbox, 5.0.14, 4.4.0-10-generic, x86_64: installed virtualbox, 5.0.14, 4.4.0-8-generic, x86_64: installed virtualbox, 5.0.14, 4.5.0-040500rc6-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7640G] [1002:9903] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Trinity [Radeon HD 7640G] [1043:106b] Advanced Micro Devices, Inc. [AMD/ATI] Seymour [Radeon HD 6400M/7400M Series] [1002:6760] (rev ff) (prog-if ff) InstallationDate: Installed on 2016-02-18 (15 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: ASUSTeK COMPUTER INC. K55DR ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.5.0-040500rc6-generic root=UUID=e0064410-4660-40b7-b961-76f320a921a6 ro amdgpu.powerplay=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/07/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 217 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: K55DR 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.:bvr217:bd09/07/2012:svnASUSTeKCOMPUTERINC.:pnK55DR:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnK55DR:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: K55DR dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. 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-1ubuntu3 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.6.1-1ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160218-1ubuntu3 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Sat Mar 5 04:27:41 2016 xserver.configfile: default xserver.errors: RADEON(G0): [XvMC] Failed to initialize extension. xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.1-1ubuntu3 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1553441/+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 1574776] Re: Only one subtitle displayed at any given time
Please: 1. Report to (https://bugzilla.gnome.org/enter_bug.cgi). 2. Paste the new report link here. 3. Set status back to "confirmed". Thank you. ** Changed in: gstreamer1.0 (Ubuntu) Importance: Undecided => Wishlist ** Changed in: gstreamer1.0 (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gstreamer1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1574776 Title: Only one subtitle displayed at any given time Status in gstreamer1.0 package in Ubuntu: Incomplete Bug description: Many of the videos I watch are subtitled foreign works; they generally have multiple subtitles onscreen at once, with one translating the speech and others translating onscreen text. Gstreamer invariably only displays one and more often than not it's the less helpful one, leaving me unable to tell what's been said because "episode 2" is deemed more important information. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: libgstreamer1.0-0 1.8.0-1 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Apr 25 18:25:16 2016 InstallationDate: Installed on 2015-06-28 (302 days ago) InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 (20150422) SourcePackage: gstreamer1.0 UpgradeStatus: Upgraded to xenial on 2016-04-19 (6 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1574776/+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 1656360] [NEW] Possible erroneous information in software description
Public bug reported: In the description of Krita (snap package) reads this message "...and due to a bug in Ubuntu, this snap doesn't work with proprietary video drivers, e.g. for NVidia." I'm using NVIDIA 367.57 and works without problems ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: gnome-software 3.20.1+git20161013.0.d77d6cf-0ubuntu2 ProcVersionSignature: Ubuntu 4.8.0-34.36-generic 4.8.11 Uname: Linux 4.8.0-34-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 CurrentDesktop: Unity Date: Fri Jan 13 13:54:12 2017 InstallationDate: Installed on 2016-11-04 (70 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-software (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug yakkety -- 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/1656360 Title: Possible erroneous information in software description Status in gnome-software package in Ubuntu: New Bug description: In the description of Krita (snap package) reads this message "...and due to a bug in Ubuntu, this snap doesn't work with proprietary video drivers, e.g. for NVidia." I'm using NVIDIA 367.57 and works without problems ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: gnome-software 3.20.1+git20161013.0.d77d6cf-0ubuntu2 ProcVersionSignature: Ubuntu 4.8.0-34.36-generic 4.8.11 Uname: Linux 4.8.0-34-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 CurrentDesktop: Unity Date: Fri Jan 13 13:54:12 2017 InstallationDate: Installed on 2016-11-04 (70 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1656360/+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 1652473] Re: package emacs24 24.5+1-6ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
** Changed in: emacs24 (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to emacs24 in Ubuntu. https://bugs.launchpad.net/bugs/1652473 Title: package emacs24 24.5+1-6ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in emacs24 package in Ubuntu: Confirmed Bug description: Happened during upgrade from 14.04 to 16.04 ProblemType: Package DistroRelease: Ubuntu 16.04 Package: emacs24 24.5+1-6ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35 Uname: Linux 4.4.0-57-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 Date: Sun Dec 25 01:06:41 2016 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2011-08-27 (1946 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha amd64 (20110825) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.15ubuntu0.2 SourcePackage: emacs24 Title: package emacs24 24.5+1-6ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to xenial on 2016-12-25 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/emacs24/+bug/1652473/+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 1652466] Re: Totem can't play videos on Gallium graphics
** Summary changed: - [Xenial] va-driver-all should depend on mesa-va-drivers, otherwise, Totem can't play videos if gstreamer1.0-vaapi is installed on Gallium graphics + Totem can't play videos on Gallium graphics ** Changed in: libva (Ubuntu) Importance: Undecided => Medium ** Also affects: hundredpapercuts Importance: Undecided Status: New ** Also affects: totem (Ubuntu) Importance: Undecided Status: New ** Changed in: totem (Ubuntu) Status: New => Confirmed ** Changed in: totem (Ubuntu) Importance: Undecided => Medium ** Changed in: totem (Ubuntu) Status: Confirmed => Invalid ** Changed in: hundredpapercuts Status: New => Confirmed ** Changed in: hundredpapercuts Importance: Undecided => Medium -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libva in Ubuntu. https://bugs.launchpad.net/bugs/1652466 Title: Totem can't play videos on Gallium graphics Status in One Hundred Papercuts: Confirmed Status in libva package in Ubuntu: Confirmed Status in totem package in Ubuntu: Invalid Bug description: What is the problem: Totem can't play videos if gstreamer1.0-vaapi is installed on Gallium graphics in Xenial because mesa-va-drivers is not installed as a dependency of va-driver-all. Here is the dependency chain in Xenial: gstreamer1.0-vaapi Depends on libva1 libva1 Recommends va-driver-all va-driver-all Depends on i965-va-driver vdpau-va-driver (no mesa-va-drivers!) Here is the terminal output of Totem (with gstreamer1.0-vaapi installed and no mesa-va-drivers): :~$ totem Stream with high frequencies VQ coding libva info: VA-API version 0.39.0 libva info: va_getDriverName() returns 0 libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/radeonsi_drv_video.so libva info: va_openDriver() returns -1 libva info: VA-API version 0.39.0 libva info: va_getDriverName() returns 0 libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/gallium_drv_video.so libva info: va_openDriver() returns -1 libva info: VA-API version 0.39.0 libva info: va_getDriverName() returns 0 When mesa-va-drivers is installed, Totem plays videos just fine. This is fixed in version 1.7.0-2 in Debian and Yakkety. libva (1.7.0-2) unstable; urgency=medium * debian/control: - Add mesa-va-drivers as alternative to Depends of va-driver-all. - Bump Standards-Versions. -- Sebastian Ramacher Wed, 11 May 2016 17:32:06 +0200 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: va-driver-all 1.7.0-1 ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35 Uname: Linux 4.4.0-57-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 CurrentDesktop: Unity Date: Sat Dec 24 21:54:20 2016 InstallationDate: Installed on 2016-04-26 (242 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: libva UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1652466/+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 1649289] Re: LibreOffice Windows All Closing
Again: When opening a recent document from the initial blank document produced by libreoffice --writer on a third external display, while LibreOffice was already running, all LibreOffice windows disappeared The libreoffice command did not exit On control+C, relaunch, no windows appeared On restart of GNOME/Wayland, the recovery dialog appeared after 2 min 10 s, which is 2 min more than normal - This is tedious with bug/1649295 LibreOffice Writer docx fails to load styles - The initial crash that forced a relaunch of LibreOffice was caused by bug1647084 i915 multiple display halt system when moving windows - for unknown reason A LibreOffice calc window jumped from the right external display to the left external display - when it was dragged back across the internal display, the window unexpectedly jumped to the top-left position and GNOME Shell froze -- 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/1649289 Title: LibreOffice Windows All Closing Status in libreoffice package in Ubuntu: New Bug description: Opened one additional Writer document. After several seconds of 100% copu, all LuvbreOffice windows disappears libreoffice process still running (soffice:3429): Gdk-ERROR **: Error reading events from display: Connection reset by peer Fatal exception: Signal 5 Stack: /usr/lib/libreoffice/program/libuno_sal.so.3(+0x394a0)[0x7f72eb0a84a0] /usr/lib/libreoffice/program/libuno_sal.so.3(+0x39611)[0x7f72eb0a8611] /lib/x86_64-linux-gnu/libc.so.6(+0x35860)[0x7f72eacdd860] /lib/x86_64-linux-gnu/libglib-2.0.so.0(+0x50241)[0x7f72e965e241] /lib/x86_64-linux-gnu/libglib-2.0.so.0(g_log_default_handler+0xc7)[0x7f72e965f297] /lib/x86_64-linux-gnu/libglib-2.0.so.0(g_logv+0x1e4)[0x7f72e965f5a4] /lib/x86_64-linux-gnu/libglib-2.0.so.0(g_log+0x8f)[0x7f72e965f7af] /usr/lib/x86_64-linux-gnu/libgdk-3.so.0(+0x84dd9)[0x7f72d68dadd9] /lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_context_check+0x1d9)[0x7f72e96583c9] /lib/x86_64-linux-gnu/libglib-2.0.so.0(+0x4a974)[0x7f72e9658974] /lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_context_iteration+0x2c)[0x7f72e9658aec] /usr/lib/libreoffice/program/libvclplug_gtk3lo.so(+0x3fbd3)[0x7f72d7463bd3] /usr/lib/libreoffice/program/libmergedlo.so(_ZN11Application5YieldEv+0x51)[0x7f72eda16241] /usr/lib/libreoffice/program/libmergedlo.so(_ZN11Application7ExecuteEv+0x45)[0x7f72eda186b5] /usr/lib/libreoffice/program/libmergedlo.so(+0x182f94c)[0x7f72ecaf494c] /usr/lib/libreoffice/program/libmergedlo.so(+0x2756f46)[0x7f72eda1bf46] /usr/lib/libreoffice/program/libmergedlo.so(_Z6SVMainv+0x22)[0x7f72eda1c042] /usr/lib/libreoffice/program/libmergedlo.so(soffice_main+0x8a)[0x7f72ecb1629a] /usr/lib/libreoffice/program/soffice.bin(+0x7ab)[0x55f5731e97ab] /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf1)[0x7f72eacc83f1] /usr/lib/libreoffice/program/soffice.bin(+0x7ea)[0x55f5731e97ea] ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: libreoffice 1:5.2.2-0ubuntu2 ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6 Uname: Linux 4.8.0-30-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Dec 12 06:38:40 2016 SourcePackage: libreoffice UpgradeStatus: Upgraded to yakkety on 2016-11-16 (25 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1649289/+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 1649289] Re: LibreOffice Windows All Closing
Apparently, windows switch displays for no apparent reason. Is it so that LibreOffice moves all window to a non-existing display, ie. hides them? -- 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/1649289 Title: LibreOffice Windows All Closing Status in libreoffice package in Ubuntu: New Bug description: Opened one additional Writer document. After several seconds of 100% copu, all LuvbreOffice windows disappears libreoffice process still running (soffice:3429): Gdk-ERROR **: Error reading events from display: Connection reset by peer Fatal exception: Signal 5 Stack: /usr/lib/libreoffice/program/libuno_sal.so.3(+0x394a0)[0x7f72eb0a84a0] /usr/lib/libreoffice/program/libuno_sal.so.3(+0x39611)[0x7f72eb0a8611] /lib/x86_64-linux-gnu/libc.so.6(+0x35860)[0x7f72eacdd860] /lib/x86_64-linux-gnu/libglib-2.0.so.0(+0x50241)[0x7f72e965e241] /lib/x86_64-linux-gnu/libglib-2.0.so.0(g_log_default_handler+0xc7)[0x7f72e965f297] /lib/x86_64-linux-gnu/libglib-2.0.so.0(g_logv+0x1e4)[0x7f72e965f5a4] /lib/x86_64-linux-gnu/libglib-2.0.so.0(g_log+0x8f)[0x7f72e965f7af] /usr/lib/x86_64-linux-gnu/libgdk-3.so.0(+0x84dd9)[0x7f72d68dadd9] /lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_context_check+0x1d9)[0x7f72e96583c9] /lib/x86_64-linux-gnu/libglib-2.0.so.0(+0x4a974)[0x7f72e9658974] /lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_context_iteration+0x2c)[0x7f72e9658aec] /usr/lib/libreoffice/program/libvclplug_gtk3lo.so(+0x3fbd3)[0x7f72d7463bd3] /usr/lib/libreoffice/program/libmergedlo.so(_ZN11Application5YieldEv+0x51)[0x7f72eda16241] /usr/lib/libreoffice/program/libmergedlo.so(_ZN11Application7ExecuteEv+0x45)[0x7f72eda186b5] /usr/lib/libreoffice/program/libmergedlo.so(+0x182f94c)[0x7f72ecaf494c] /usr/lib/libreoffice/program/libmergedlo.so(+0x2756f46)[0x7f72eda1bf46] /usr/lib/libreoffice/program/libmergedlo.so(_Z6SVMainv+0x22)[0x7f72eda1c042] /usr/lib/libreoffice/program/libmergedlo.so(soffice_main+0x8a)[0x7f72ecb1629a] /usr/lib/libreoffice/program/soffice.bin(+0x7ab)[0x55f5731e97ab] /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf1)[0x7f72eacc83f1] /usr/lib/libreoffice/program/soffice.bin(+0x7ea)[0x55f5731e97ea] ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: libreoffice 1:5.2.2-0ubuntu2 ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6 Uname: Linux 4.8.0-30-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Dec 12 06:38:40 2016 SourcePackage: libreoffice UpgradeStatus: Upgraded to yakkety on 2016-11-16 (25 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1649289/+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 1649105] Re: ubuntu 16.04 conflict with nvidia GeForce 6150SE
Please: 1. Edit the description, so it explains the perceptible consequences of the bug. 2. Set status back to confirmed. Thanks for your help. ** Changed in: xorg (Ubuntu) Status: Confirmed => Incomplete -- 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/1649105 Title: ubuntu 16.04 conflict with nvidia GeForce 6150SE Status in xorg package in Ubuntu: Incomplete Bug description: seems conflictual behaviour between compiz version and available drivers (private and free). No solution found yet to stabilize. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30 Uname: Linux 4.4.0-53-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.2 Architecture: amd64 BootLog: [[0;32m OK [0m] Started LSB: Speech Dispatcher. [[0;32m OK [0m] Started LSB: Set the CPU Frequency Scaling governor to "ondemand". CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Sun Dec 11 18:05:40 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: NVIDIA Corporation C61 [GeForce 6150SE nForce 430] [10de:03d0] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] C61 [GeForce 6150SE nForce 430] [1025:0394] InstallationDate: Installed on 2016-12-01 (9 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 04f9:0027 Brother Industries, Ltd HL-2030 Laser Printer Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: eMachines EL1358 ProcEnviron: LANGUAGE=fr_FR PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-53-generic root=UUID=b5bf3784-f5af-4627-8503-a82a628a8998 ro drm.debug=0xe plymouth:debug SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) XorgLogOld: dmi.bios.date: 04/20/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P01-B1 dmi.board.name: EL1358 dmi.board.vendor: eMachines dmi.chassis.type: 3 dmi.chassis.vendor: eMachines dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP01-B1:bd04/20/2011:svneMachines:pnEL1358:pvr:rvneMachines:rnEL1358:rvr:cvneMachines:ct3:cvr: dmi.product.name: EL1358 dmi.sys.vendor: eMachines version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Sun Dec 11 17:55:46 2016 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputAT Translated Set 2 keyboard KEYBOARD, id 8 inputImPS/2 Generic Wheel Mouse MOUSE, id 9 xserver.errors: Failed to load module "nvidia" (module does not exist, 0) Failed to load module "nvidia" (module does not exist, 0) xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-0ubuntu0.2 xserver.video_driver: nouveau To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1649105/+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 1646956] Re: ping -I support broken in yakkety version 3:20150815-2ubuntu3 (multicast test failure)
** Tags removed: targetmilestone-inin--- ** Tags added: targetmilestone-inin1704 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to iputils in Ubuntu. https://bugs.launchpad.net/bugs/1646956 Title: ping -I support broken in yakkety version 3:20150815-2ubuntu3 (multicast test failure) Status in iputils package in Ubuntu: New Bug description: == Comment: #0 - HARSHA THYAGARAJA - 2016-11-15 03:42:59 == ---Problem Description--- Multicast failing for Shiner interface on Ubuntu 16.10 (bnx2x) Machine Type = S822l1 ---Steps to Reproduce--- On Host: Enable multicast for the test interface 1. echo 0 > /proc/sys/net/ipv4/icmp_echo_ignore_broadcasts 2. ip link set enP5p1s0f1 allmulticast on root@ltciofvtr-s822l1:~# ifconfig enP5p1s0f1 enP5p1s0f1: flags=4675 mtu 1500 inet 170.1.1.20 netmask 255.255.255.0 broadcast 170.1.1.255 inet6 fe80::9abe:94ff:fe5c:f1c1 prefixlen 64 scopeid 0x20 ether 98:be:94:5c:f1:c1 txqueuelen 1000 (Ethernet) RX packets 488 bytes 50254 (50.2 KB) RX errors 0 dropped 442 overruns 0 frame 0 TX packets 25 bytes 2226 (2.2 KB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 device interrupt 226 memory 0x3d400100-3d40017f On Peer: --> catch the Test interface from the multicast group ping 224.0.0.1 -I enP4p1s0f2 | grep 170.1.1.20 ---uname output--- Linux ltciofvtr-s822l1 4.8.0-27-generic #29-Ubuntu SMP Thu Oct 20 21:01:16 UTC 2016 ppc64le ppc64le ppc64le GNU/Linux == Comment: #9 - Kevin W. Rudd - 2016-11-28 15:40:24 == I'm able to replicate this behavior in a KVM environment with Yakkety, so it does not appear to be related to the specific type of interface. From my testing, it looks like the SO_BINDTODEVICE option is not being honored, so both broadcasts and multicasts are going out the default route device instead of the device specified by -I option to ping. I am unable to replicate this on a xenial host with the same 4.8.0-27 kernel version. so I suspect some other setting is interfering with the ability to bind the output to a specific device. From my own testing: Xenial: # ip addr show 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: enp0s6: mtu 1500 qdisc pfifo_fast state UP group default qlen 1000 link/ether 52:54:00:15:b7:ba brd ff:ff:ff:ff:ff:ff inet 10.168.122.139/24 brd 10.168.122.255 scope global enp0s6 valid_lft forever preferred_lft forever inet6 fe80::5054:ff:fe15:b7ba/64 scope link valid_lft forever preferred_lft forever 3: enp0s1: mtu 1500 qdisc pfifo_fast state UP group default qlen 1000 link/ether 52:54:00:e1:35:be brd ff:ff:ff:ff:ff:ff inet 192.168.122.139/24 brd 192.168.122.255 scope global enp0s1 valid_lft forever preferred_lft forever inet6 fe80::5054:ff:fee1:35be/64 scope link valid_lft forever preferred_lft forever # ping -I enp0s6 -i 30 224.0.0.1 PING 224.0.0.1 (224.0.0.1) from 10.168.122.139 enp0s6: 56(84) bytes of data. 64 bytes from 10.168.122.139: icmp_seq=1 ttl=64 time=0.063 ms 64 bytes from 10.168.122.100: icmp_seq=1 ttl=64 time=0.435 ms (DUP!) ^C ... Yakkety: # ip addr show 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: enp0s5: mtu 1500 qdisc pfifo_fast state UP group default qlen 1000 link/ether 52:54:00:be:97:ab brd ff:ff:ff:ff:ff:ff inet 10.168.122.100/24 brd 10.168.122.255 scope global enp0s5 valid_lft forever preferred_lft forever inet6 fe80::5054:ff:febe:97ab/64 scope link valid_lft forever preferred_lft forever 3: enp0s1: mtu 1500 qdisc pfifo_fast state UP group default qlen 1000 link/ether 52:54:00:30:d0:14 brd ff:ff:ff:ff:ff:ff inet 192.168.122.100/24 brd 192.168.122.255 scope global enp0s1 valid_lft forever preferred_lft forever inet6 fe80::5054:ff:fe30:d014/64 scope link valid_lft forever preferred_lft forever # ping -I enp0s5 -i 30 224.0.0.1 PING 224.0.0.1 (224.0.0.1) from 10.168.122.100 enp0s5: 56(84) bytes of data. 64 bytes from 192.168.122.100: icmp_seq=1 ttl=64 time=0.115 ms 64 bytes from 192.168.122.139: icmp_seq=1 ttl=64 time=1.65 ms (DUP!) ^C ... Note that the Yakkety system received answers from the hosts on the 192.168.122 network (the network associated with the route for 224.0.0.1). == Comment
[Desktop-packages] [Bug 1597437] Re: X with nouveau driver, 2 nvidia cards, 4 monitors, does not use all monitors
** Changed in: xserver-xorg-video-nouveau (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/1597437 Title: X with nouveau driver, 2 nvidia cards, 4 monitors, does not use all monitors Status in xserver-xorg-video-nouveau package in Ubuntu: Confirmed Bug description: Ubuntu 16.04 with two identical nvidia cards and four identical LG monitors. At the graphical login screen only the first 3 monitors appear alive (i.e. have backgrounds and the mouse can move to them). A pop-up appears: "Could not switch the monitor configuration" (bold text with do-not-enter icon) "could not set the configuration for CRTC 64" (normal text) After logging in (gnome flashback Metacity session) the same 3 monitors are alive and the same pop-up appears. Using Applications > System Tools > System Settings > Displays, the 4th monitor is shown in grey and when clicking it, it shows that the slider is off. When turning it to On (leaving default resolution and rotation) and clicking Apply "The selected configuration for displays could not be applied" (bold text with do-not-enter icon) "could not set the configuration for CRTC 64" (normal text) a few seconds later (if the first one is not closed) another pop up with do-not-enter icon: "Failed to apply configuration: %s" "Timeout was reached" or trying again, if the first pop-up is closed within a few seconds, the second one is "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" ...and the Displays GUI makes it look like the 4th monitor is enabled but it is still blank. At the time of doing this, /var/log/Xorg.0.log shows: [ 96283.251] resize called 7680 1080 [ 96283.299] Cannot do multiple crtcs without X server dirty tracking 2 interface [ 96283.299] randr: failed to set shadow slave pixmap [ 96283.300] (EE) NOUVEAU(G0): failed to set mode: No space left on device I have also tried this with xrandr command line: $ xrandr --output DVI-I-1-4 --right-of DVI-I-1-3 --auto xrandr: Configure crtc 3 failed ...and the Xorg.0.log at this time is almost the same as above, plus the (I guess) fall back resizing to 3 monitors (5760x1080): [ 96645.224] Cannot do multiple crtcs without X server dirty tracking 2 interface [ 96645.224] randr: failed to set shadow slave pixmap [ 96645.224] (EE) NOUVEAU(G0): failed to set mode: No space left on device [ 96645.227] resize called 0 0 [ 96645.227] -22 [ 96645.228] resize called 0 0 [ 96645.228] -22 [ 96645.229] resize called 7680 1080 [ 96645.281] resize called 5760 1080 I have previously tried to get around this with /etc/X11/xorg.conf with various Xinerama or ZaphodHeads settings but at the moment (of starting this "ubuntu-bug xserver-xorg-core" report) I have no xorg.conf and no ~/.config/monitors.xml. Obviously monitors.xml has been re-created as I test the Displays GUI to describe the pop-ups above, but it was not there at login. The 2-connector video cards to all four monitors are connected with DVI cables. The monitors are LG E2240TI, the video cards are (lspci): 01:00.0 VGA compatible controller: NVIDIA Corporation GF114 [GeForce GTX 560 Ti] (rev a1) 02:00.0 VGA compatible controller: NVIDIA Corporation GF114 [GeForce GTX 560 Ti] (rev a1) ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xserver-xorg-core 2:1.18.3-1ubuntu2.2 ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13 Uname: Linux 4.4.0-28-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: None CurrentDesktop: GNOME-Flashback:Unity Date: Wed Jun 29 12:21:13 2016 DistUpgraded: 2016-06-23 10:16:50,641 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: virtualbox, 5.0.18, 4.4.0-24-generic, x86_64: installed virtualbox, 5.0.18, 4.4.0-28-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: NVIDIA Corporation GF114 [GeForce GTX 560 Ti] [10de:1200] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ZOTAC International (MCO) Ltd. GF114 [GeForce GTX 560 Ti] [19da:1665] NVIDIA Corporation GF114 [GeForce GTX 560 Ti] [10de:1200] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ZOTAC International (MCO) Ltd. GF114 [GeForce GTX 560 Ti] [19da:1665] InstallationDate: Installed on 2015-11-12 (229 days ago) InstallationMedia: Ubuntu-Server 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: System manufacturer System Product Name
[Desktop-packages] [Bug 1656347] [NEW] gnome-software stall remains in RAM after closure on Xubuntu
Public bug reported: Run gnome-software 3.20.1 close program. Program remains in memory 245-251MiB RAM used. Expect program to end when closed. Program can also stall installing programs and will interfere with synaptic & apt-get with a database lock. Also apport-bug will not allow reporting, it reports this error: The problem cannot be reported: This is not an official Ubuntu package. Please remove any third party package and try again. lsb_release -a LSB Version: core-9.20160110ubuntu0.2-amd64:core-9.20160110ubuntu0.2-noarch:printing-9.20160110ubuntu0.2-amd64:printing-9.20160110ubuntu0.2-noarch:security-9.20160110ubuntu0.2-amd64:security-9.20160110ubuntu0.2-noarch Distributor ID: Ubuntu Description:Ubuntu 16.04.1 LTS Release:16.04 Codename: xenial ** Affects: gnome-software (Ubuntu) Importance: Undecided Status: New ** Tags: gnome-software ** Tags added: gnome-software ** Description changed: Run gnome-software 3.20.1 close program. Program remains in memory 245-251MiB RAM used. Expect program to end when closed. Program can also stall installing programs and will interfere with synaptic & apt-get with a database lock. Also apport-bug will not allow reporting, it reports this error: The problem cannot be reported: This is not an official Ubuntu package. Please remove any third party package and try again. + + lsb_release -a + LSB Version: core-9.20160110ubuntu0.2-amd64:core-9.20160110ubuntu0.2-noarch:printing-9.20160110ubuntu0.2-amd64:printing-9.20160110ubuntu0.2-noarch:security-9.20160110ubuntu0.2-amd64:security-9.20160110ubuntu0.2-noarch + Distributor ID: Ubuntu + Description: Ubuntu 16.04.1 LTS + Release: 16.04 + Codename: xenial -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1656347 Title: gnome-software stall remains in RAM after closure on Xubuntu Status in gnome-software package in Ubuntu: New Bug description: Run gnome-software 3.20.1 close program. Program remains in memory 245-251MiB RAM used. Expect program to end when closed. Program can also stall installing programs and will interfere with synaptic & apt-get with a database lock. Also apport-bug will not allow reporting, it reports this error: The problem cannot be reported: This is not an official Ubuntu package. Please remove any third party package and try again. lsb_release -a LSB Version: core-9.20160110ubuntu0.2-amd64:core-9.20160110ubuntu0.2-noarch:printing-9.20160110ubuntu0.2-amd64:printing-9.20160110ubuntu0.2-noarch:security-9.20160110ubuntu0.2-amd64:security-9.20160110ubuntu0.2-noarch Distributor ID: Ubuntu Description: Ubuntu 16.04.1 LTS Release: 16.04 Codename: xenial To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1656347/+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 1581076] Re: Xorg segfaults on start-up on Big Endian PPC hardware
Hello Alex, or anyone else affected, Accepted xorg-server-lts-xenial into trusty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/xorg- server-lts-xenial/2:1.18.4-0ubuntu0.2~trusty2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: xorg-server-lts-xenial (Ubuntu Trusty) Status: New => Fix Committed -- 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/1581076 Title: Xorg segfaults on start-up on Big Endian PPC hardware Status in xorg-server package in Ubuntu: Fix Released Status in xorg-server-lts-xenial package in Ubuntu: New Status in xorg-server-lts-xenial source package in Trusty: Fix Committed Status in xorg-server source package in Xenial: Fix Released Status in xorg-server-lts-xenial source package in Xenial: Invalid Bug description: On my Big Endian PowerPC machine, Xorg segfaults when starting. I have been able to confirm that this does not happen when building Xorg from upstream source, and then further confirmed that the source of the segfault appears to be caused by a non-upstreamed, ubuntu specific patch. When building the xorg-server-1.18.3 deb from source, I commented out the following patches from debian/patches/series to try to isolate the source of the crash. With the following patches not-applied, and the resulting .deb package built, the segfault on start does not occur. 08_xfree86_fix_ia64_inx_outx.diff 105_nvidia_autodetect.patch 168_glibc_trace_to_stderr.patch 188_default_primary_to_first_busid.patch 190_cache-xkbcomp_output_for_fast_start_up.patch 191-Xorg-add-an-extra-module-path.patch 232-xf86compatoutput-valgrind.patch no-nv.patch 228_autobind_gpu.patch xf86-inactive-gpuscreen.patch config-add-no-removal.patch xf86-ignore-conflicting-rr-caps.patch fix-detach-gpu.patch disable-rotation-transform-gpuscreens.patch xmir.patch xmir-desktop-file-hint-flag.patch drm_device_keep_trying.patch xi2-resize-touch.patch xmir-fixes.diff To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1581076/+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 1617925] Please test proposed package
Hello Daniel, or anyone else affected, Accepted xorg-server-lts-xenial into trusty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/xorg- server-lts-xenial/2:1.18.4-0ubuntu0.2~trusty2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1617925 Title: Xmir: Received an unknown 11 event Status in xorg-server package in Ubuntu: Fix Released Status in xorg-server source package in Xenial: Fix Released Bug description: Xmir says: Received an unknown 11 event Received an unknown 11 event Received an unknown 11 event Received an unknown 11 event Received an unknown 11 event Received an unknown 11 event Received an unknown 11 event Received an unknown 11 event Received an unknown 11 event Received an unknown 11 event Received an unknown 11 event Received an unknown 11 event Received an unknown 11 event Received an unknown 11 event Received an unknown 11 event To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1617925/+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 1591356] Please test proposed package
Hello Albert, or anyone else affected, Accepted xorg-server-lts-xenial into trusty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/xorg- server-lts-xenial/2:1.18.4-0ubuntu0.2~trusty2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1591356 Title: keyboard autorepeat in Xmir apps & GTK-on-Mir does not work Status in Canonical System Image: Confirmed Status in GTK+: Fix Released Status in gtk+3.0 package in Ubuntu: Triaged Status in libertine package in Ubuntu: Invalid Status in xorg-server package in Ubuntu: Fix Released Status in gtk+3.0 source package in Xenial: New Status in libertine source package in Xenial: New Status in xorg-server source package in Xenial: Fix Released Status in xorg-server package in Ubuntu RTM: New Bug description: [Impact] Auto key repeating does not work in Libertine X apps which is very frustrating to users. [Test Case] 1. Install xterm in libertine 2. Start xterm from the "Xapps" scope 3. Wait for xterm to appear 4. Press and hold a key See how it only appears once and not multiple times as it should. [Regression Potential] Non observed. Original Description: How to reproduce: * Install xterm in libertine * Start xterm from the "Xapps" scope * Wait for xterm to appear * Press and hold a key * See how it only appears once and not multiple times as it should To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1591356/+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 1617932] Please test proposed package
Hello Daniel, or anyone else affected, Accepted xorg-server-lts-xenial into trusty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/xorg- server-lts-xenial/2:1.18.4-0ubuntu0.2~trusty2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1617932 Title: Xmir with glamor is spending 11% of its CPU time in epoxy_has_gl_extension Status in xorg-server package in Ubuntu: Fix Released Status in xorg-server source package in Xenial: Fix Released Bug description: Xmir with glamor is spending 11% of its CPU time in epoxy_has_gl_extension. This only happens on desktop where the default Xmir renderer uses glamor. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1617932/+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 1619142] Please test proposed package
Hello Timo, or anyone else affected, Accepted xorg-server-lts-xenial into trusty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/xorg- server-lts-xenial/2:1.18.4-0ubuntu0.2~trusty2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1619142 Title: [MRE] Update to 1.18.4 Status in xorg-server package in Ubuntu: Invalid Status in xorg-server-lts-xenial package in Ubuntu: Invalid Status in xorg-server source package in Trusty: Invalid Status in xorg-server-lts-xenial source package in Trusty: Fix Committed Status in xorg-server source package in Xenial: Fix Released Status in xorg-server-lts-xenial source package in Xenial: Invalid Bug description: Update xserver to new minor release 1.18.4 in order to gain bugfixes from upstream. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1619142/+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 1586260] Please test proposed package
Hello Xinxiu, or anyone else affected, Accepted xorg-server-lts-xenial into trusty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/xorg- server-lts-xenial/2:1.18.4-0ubuntu0.2~trusty2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1586260 Title: System freeze & no display if set External monitor as primary (Performance mode) Status in xorg-server package in Ubuntu: Fix Released Status in xorg-server-lts-xenial package in Ubuntu: New Status in xorg-server source package in Trusty: Invalid Status in xorg-server-lts-vivid source package in Trusty: Fix Released Status in xorg-server-lts-xenial source package in Trusty: Fix Committed Status in xorg-server source package in Xenial: Fix Released Status in xorg-server source package in Yakkety: Fix Released Bug description: [Impact] System freeze & no display if set External monitor as primary (Performance mode) [Test case] 1. Setup Graphic mode to Performance mode 2. Plug External monitor with HDMI 3. Set display mode to External monitor only is pass 4. Set display mode to Extend/ Mirror mode Expected results: External monitor can be set as primary normally Actual results: System freeze & no display if set External monitor as primary (Performance mode) [Regression potential] Unknown right now, upstream review pending. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1586260/+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 1590553] Please test proposed package
Hello Daniel, or anyone else affected, Accepted xorg-server-lts-xenial into trusty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/xorg- server-lts-xenial/2:1.18.4-0ubuntu0.2~trusty2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1590553 Title: Xmir -rootless: Buttons are randomly unclickable (popups vanish instantly) Status in xorg-server package in Ubuntu: Fix Released Status in xorg-server source package in Xenial: Fix Released Bug description: Xmir -rootless: Buttons are randomly unclickable I've noticed this in LibreOffice Impress and Chromium browser. Sometimes when clicking buttons, the button just flickers and does nothing. Sometimes it also involves a popup menu flickering and out. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1590553/+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 1613708] Please test proposed package
Hello Victor, or anyone else affected, Accepted xorg-server-lts-xenial into trusty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/xorg- server-lts-xenial/2:1.18.4-0ubuntu0.2~trusty2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1613708 Title: [regression] Xmir: Some buttons are unclickable after rotating the screen Status in Canonical System Image: Fix Released Status in xorg-server package in Ubuntu: Fix Released Status in xorg-server source package in Xenial: Fix Released Bug description: [Impact] XMir clients do not have their input transform matrix modified properly when the screen dimensions and orientation change (ie. rotation). This shows up primarily on Bq M10 tablets which rotate on startup. [Test Case] Install XMir on a device that supports screen rotation. Connect a client (using Libertine is the easiest way to do this). Attempt to use direct or indirect pointer input on the right side of the screen. The bug is it does nothing. [Regression Potential] This change affects only the XMir server. There is potential that XMir functionality is compromized but mainline x.org functionality is unaffected. This XMir patch update is pulled directly from Ubuntu current development release "Yakkety Yak" where it has been in production for more than 6 weeks without apparent regressions. [Other Info] The patch update also includes bugfixes for bug #1617925, bug #1617932, and bug #1591356. This patch differs from the patch in Ubuntu "Yakkety Yak" to compile with Mir 0.21. The only functional difference is an extra message logged when run against Mir 0.24. -- original bug description follows -- Enviroment: current build number: 169 device name: frieza channel: ubuntu-touch/rc-proposed/bq-aquaris-pd.en last update: 2016-08-16 10:23:29 version version: 169 version ubuntu: 20160816 version device: 20160809.0 version custom: 20160805--42-20-vivid Product: BQ M10 FHD Steps to reproduce: 1º Open LibreOffice and try to print something 2º Print settings window appear, try to click on Accept/Cancel/Exit etc 3º Buttons on LibreOffice won't respond 1º Open Firefox 2º Mouse-over on search,downloads,bookmarks etc 3º Seems like mouse-over is not focused and is clicking is not responding Current result: Some Xapps buttons are not responding(tested on Firefox and LibreOffice Writer) Expected result: Add info: This is using xmir from https://launchpad.net/~ci-train-ppa- service/+archive/ubuntu/landing-053/+packages. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1613708/+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 1636397] Please test proposed package
Hello Timo, or anyone else affected, Accepted xorg-server-lts-xenial into trusty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/xorg- server-lts-xenial/2:1.18.4-0ubuntu0.2~trusty2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1636397 Title: Fix modesetting slave output names Status in HWE Next: Fix Released Status in xorg-server package in Ubuntu: Fix Released Status in xorg-server source package in Xenial: Fix Released Status in xorg-server source package in Yakkety: Fix Released Bug description: [Impact] Currently, NVIDIA and modesetting drivers are using same output names, that creates confusion for xrandr clients like gnome-setting-daemon or xrandr utility. When modesetting outputs act as slave for other x-screen (like NVIDIA X-screen here), modesetting driver uses different scheme of output names to avoid kind of confusion we are seeing here. There is a bug in modesetting X-driver gets shipped with X-server, which disables slave output's name scheme. From a reviewed upstream patch: "Commit c7e8d4a6ee9542f56cd241cf7a960fb8223a6b22 had already unifdef MODESETTING_OUTPUT_SLAVE_SUPPORT but commit 9257b1252da9092ddc676fec9aabe2b33dfad272 didn't notice that." so we need to backport that to zesty/yakkety/xenial. [Test Case] Enable dGPU, test that output to DP works. [Regression Potential] There should be none, as this leftover was a simple mistake that shouldn't be there. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1636397/+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 1655724] Re: Should not break systemd in trusty, conflicts with snapd
Hello Dimitri, or anyone else affected, Accepted xorg-server-lts-xenial into trusty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/xorg- server-lts-xenial/2:1.18.4-0ubuntu0.2~trusty2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: xorg-server-lts-xenial (Ubuntu Trusty) Status: In Progress => Fix Committed ** Tags added: verification-needed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server-lts-xenial in Ubuntu. https://bugs.launchpad.net/bugs/1655724 Title: Should not break systemd in trusty, conflicts with snapd Status in xorg-server-lts-xenial package in Ubuntu: Invalid Status in xorg-server-lts-xenial source package in Trusty: Fix Committed Bug description: [Impact] * With introduction of snapd/systemd in trusty, it has become impossible to install xorg-server-lts-xenial simultaniously with snapd/systemd. * In trusty, logind is managed by upstart, and is not restarted on upgrades, therefore the protective breaks in xorg-server-lts-xenial is unnecessary in trusty only. [Testcase] * installing snapd, should not remove xorg-server-lts-xenial To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server-lts-xenial/+bug/1655724/+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 1589535] Re: nm-applet silently timesout on long 'WPA/WPA2 Personal' password input
** Changed in: network-manager-applet (Ubuntu Xenial) 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/1589535 Title: nm-applet silently timesout on long 'WPA/WPA2 Personal' password input Status in Network Manager Applet: Confirmed Status in network-manager-applet package in Ubuntu: Fix Released Status in network-manager-applet source package in Xenial: Confirmed Bug description: 1) ouroumov@Edge:~/Desktop$ lsb_release -rd Description: Ubuntu 16.04 LTS Release: 16.04 2) apt-cache policy is unable to locate the package. 3) Upon entering a long WPA/WPA2 Personal password after clicking the network icon in the top right panel, the connection should be added to network-manager, even if typing the password takes a while. 4) If typing the password takes longer than ~25 seconds, upon clicking the "Connect" button in the password prompt dialog: nothing happens Steps to reproduce: - Install Ubuntu MATE 16.04 LTS (possibly other Ubuntu flavours using nm-applet too) - Run normal post-install full system update and reboot - Click the network icon in the top right corner of the default panel layout - Select from the Wi-Fi network list a network using WPA/WPA2 Personal - Enter the password, wait 30 seconds to click 'connect' Note: While this issue might seem trivial (using 'System -> Preferences -> Internet and Network -> Network Connections' allows one to correctly save the password) (and quickly copy/pasting the password from a text file works too) it is a serious usability problem for many people in France. The default home router Wi-Fi setup in France is WPA/WPA2 Personal with a random 26-character hexadecimal password. It takes a while to type. To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager-applet/+bug/1589535/+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 1619600] Re: [SRU] New stable release 1.8.3
Hello Iain, or anyone else affected, Accepted gst-plugins-good1.0 into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gst- plugins-good1.0/1.8.3-1ubuntu0.3 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Tags removed: verification-failed ** Tags added: verification-needed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gstreamer1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1619600 Title: [SRU] New stable release 1.8.3 Status in gst-libav1.0 package in Ubuntu: Fix Released Status in gst-plugins-bad1.0 package in Ubuntu: Fix Released Status in gst-plugins-base1.0 package in Ubuntu: Fix Released Status in gst-plugins-good1.0 package in Ubuntu: Fix Released Status in gst-plugins-ugly1.0 package in Ubuntu: Fix Released Status in gstreamer-vaapi package in Ubuntu: Fix Released Status in gstreamer1.0 package in Ubuntu: Fix Released Status in gst-libav1.0 source package in Xenial: Fix Committed Status in gst-plugins-bad1.0 source package in Xenial: Fix Committed Status in gst-plugins-base1.0 source package in Xenial: Fix Committed Status in gst-plugins-good1.0 source package in Xenial: Fix Committed Status in gst-plugins-ugly1.0 source package in Xenial: Fix Committed Status in gstreamer-vaapi source package in Xenial: Fix Committed Status in gstreamer1.0 source package in Xenial: Fix Committed Bug description: [ Description ] We should keep up with GStreamer's bugfix releases in the 1.8 series that 16.04 shipped with. [ QA and testing ] Play a range of videos in Totem. Play a range of audio tracks in Rhythmbox. Try to stream audio and/or video. Try to install a missing codec. In all cases, make sure that everything which worked before still works. [ Regression potential ] One of the fixes could be bad. Watch out for it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gst-libav1.0/+bug/1619600/+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 1655724] Re: Should not break systemd in trusty, conflicts with snapd
https://launchpad.net/ubuntu/trusty/+queue?queue_state=1&queue_text= ** Changed in: xorg-server-lts-xenial (Ubuntu Trusty) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server-lts-xenial in Ubuntu. https://bugs.launchpad.net/bugs/1655724 Title: Should not break systemd in trusty, conflicts with snapd Status in xorg-server-lts-xenial package in Ubuntu: Invalid Status in xorg-server-lts-xenial source package in Trusty: In Progress Bug description: [Impact] * With introduction of snapd/systemd in trusty, it has become impossible to install xorg-server-lts-xenial simultaniously with snapd/systemd. * In trusty, logind is managed by upstart, and is not restarted on upgrades, therefore the protective breaks in xorg-server-lts-xenial is unnecessary in trusty only. [Testcase] * installing snapd, should not remove xorg-server-lts-xenial To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server-lts-xenial/+bug/1655724/+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 1512027] Re: open of device pixma:MX7600_... failed: invalid argument
I can't reproduce the bug anymore because I've been using the workaround in the intervening year since I wrote the bug. I think you should have enough information to resolve it. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to sane-backends in Ubuntu. https://bugs.launchpad.net/bugs/1512027 Title: open of device pixma:MX7600_... failed: invalid argument Status in sane-backends package in Ubuntu: Incomplete Bug description: Up until recently, I've been able to scan fine with my Canon Pixma MX7600. Then I upgraded to Ubuntu Wily and I've started getting: $ scanimage scanimage: open of device pixma:MX7600_192.168.2.107 failed: Invalid argument The device pings and I can get to its HTTP port. Everything appears OK. If I run strace -f -s 256 -o /tmp/trace.txt scanimage the relevant output appears to be: socket(PF_INET, SOCK_DGRAM, IPPROTO_UDP) = 204 connect(204, {sa_family=AF_INET, sin_port=htons(8612), sin_addr=inet_addr("192.168.2.107")}, 16) = 0 sendto(204, "BJNP\2\1\0\0\0\0\0\0\0\0\0\0", 16, 0, NULL, 0) = 16 select(205, [204], NULL, NULL, {4, 0}) = 1 (in [204], left {3, 998257}) recvfrom(204, "BJNP\202\1\0\0\0\0\0\0\0\0\0\20\0\1\10\0\6\4\0\0\205\316\356\343\300\250\2k", 2048, 0, NULL, N ULL) = 32 close(204) write(2, "scanimage: open of device pixma:MX7600_192.168.2.107 failed: Invalid argument\n", 78) = 78 It appears to me that the scanner is responding but the driver doesn't like the response. I'm running sane 1.0.14-11 and sane-utils 1.0.25+git201505. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1512027/+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 1654044] Re: /usr/bin/evolution:11:webkit_editor_paste_clipboard_targets_cb:request_targets_received_func:selection_received:g_closure_invoke:signal_emit_unlocked_R
** Also affects: evolution (Ubuntu Yakkety) Importance: Undecided Status: New ** Changed in: evolution (Ubuntu Yakkety) Importance: Undecided => Medium ** Changed in: evolution (Ubuntu Yakkety) Status: New => Triaged -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/1654044 Title: /usr/bin/evolution:11:webkit_editor_paste_clipboard_targets_cb:request_targets_received_func:selection_received:g_closure_invoke:signal_emit_unlocked_R Status in Evolution: Confirmed Status in evolution package in Ubuntu: Triaged Status in evolution source package in Yakkety: Triaged Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding evolution. This problem was most recently seen with package version 3.22.3-0ubuntu0.1, the problem page at https://errors.ubuntu.com/problem/d7254ed93e5e4954abf5ab6d0f2d68dba28f5cf7 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/evolution/+bug/1654044/+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 378958] Re: xorg 100% cpu when scrolling in rdesktop
With xubuntu-16.04.1-desktop-amd64.iso live cd: the bug does *not* appear. With xubuntu-16.10-desktop-amd64.iso live cd: the bug *does* appear. The test detailed: I booted with the usb stick, choosed "try xubuntu", issued a "sudo ufw enable", "sudo apt-get update", (have not issued "dist-upgrade" nor "upgrade"), "sudo apt-get install rdesktop", "rdesktop -u xxuserxx -k hu -g 1400x700 -a 16 -z -P -r clipboard:CLIPBOARD xx.ip.addr.xx". -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/378958 Title: xorg 100% cpu when scrolling in rdesktop Status in xserver-xorg-video-ati package in Ubuntu: Invalid Bug description: After upgrading from Ubuntu 8.10 to 9.04, my rdesktops to Windows servers are unusable. Screen refreshes inside rdesktop are awfully slow. Scrolling a logfile causes xorg to take 100% cpu. I'm using Ubuntu 9.04 as default as possible, no xorg.conf editing or other vga drivers. I have a ThinkPad Z60m with an ATI x600 mobility: root@tp:~# lspci |grep -i vga 01:00.0 VGA compatible controller: ATI Technologies Inc M24 1P [Radeon Mobility X600] Very easy to reproduce with default settings: - launch laptop from Ubuntu 9.04 live cd - open rdesktop or tsclient to a Windows machine - open a large logfile or a putty window - watch how the screen in building up line per line, slowing down even more near the buttom of the screen I tested other ThinkPads with other vga cards, they don't have this issue. - Z61m with ATI x1400 = ok - R61 with nVidia = ok A few more observations: - 2D and 3D in Ubuntu works fine with the new default driver (great job :-) - Visual Effects (Compiz?) work fine, on 'normal' and even 'extra', but have no effect on the reported issue. I always disable the visial effects. - scrolling in other applications works fine and fast (FF3, gedit, terminal,...) - I use rdesktop in a windowed mode (1280x960), RDPv5 - I tried rdesktop bitmap caching enable/disable, same for both - when I launch a Windows RDP inside my rdesktop, this 2nd RDP does NOT suffer the same problem To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/378958/+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 1656320] Re: package mahjongg 1:3.18.0-1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-mahjongg in Ubuntu. https://bugs.launchpad.net/bugs/1656320 Title: package mahjongg 1:3.18.0-1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in gnome-mahjongg package in Ubuntu: New Bug description: Its happening every time I install new updates ProblemType: Package DistroRelease: Ubuntu 16.04 Package: mahjongg 1:3.18.0-1 ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35 Uname: Linux 4.4.0-57-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 Date: Thu Jan 12 13:20:43 2017 DpkgHistoryLog: Start-Date: 2017-01-12 13:20:08 Commandline: aptdaemon role='role-commit-packages' sender=':1.90' Upgrade: libnss3-nssdb:amd64 (2:3.23-0ubuntu0.16.04.1, 2:3.26.2-0ubuntu0.16.04.2), grub-common:amd64 (2.02~beta2-36ubuntu3.2, 2.02~beta2-36ubuntu3.6), snapd:amd64 (2.17.1ubuntu1, 2.20.1ubuntu1), snap-confine:amd64 (1.0.43-0ubuntu1~16.04.1, 2.20.1ubuntu1), grub2-common:amd64 (2.02~beta2-36ubuntu3.2, 2.02~beta2-36ubuntu3.6), libnss3-1d:amd64 (2:3.23-0ubuntu0.16.04.1, 2:3.26.2-0ubuntu0.16.04.2), grub-pc:amd64 (2.02~beta2-36ubuntu3.2, 2.02~beta2-36ubuntu3.6), grub-pc-bin:amd64 (2.02~beta2-36ubuntu3.2, 2.02~beta2-36ubuntu3.6), python3-distupgrade:amd64 (1:16.04.19, 1:16.04.20), ubuntu-release-upgrader-core:amd64 (1:16.04.19, 1:16.04.20), ubuntu-core-launcher:amd64 (1.0.43-0ubuntu1~16.04.1, 2.20.1ubuntu1), ubuntu-release-upgrader-gtk:amd64 (1:16.04.19, 1:16.04.20), unattended-upgrades:amd64 (0.90ubuntu0.2, 0.90ubuntu0.3), libnss3:amd64 (2:3.23-0ubuntu0.16.04.1, 2:3.26.2-0ubuntu0.16.04.2) DuplicateSignature: package:mahjongg:1:3.18.0-1 Processing triggers for ureadahead (0.100.0-19) ... ureadahead will be reprofiled on next reboot dpkg: error processing package mahjongg (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2013-09-10 (1220 days ago) InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64 (20130213) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.15ubuntu0.2 SourcePackage: gnome-mahjongg Title: package mahjongg 1:3.18.0-1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: Upgraded to xenial on 2016-11-11 (63 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-mahjongg/+bug/1656320/+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 1316035] Re: matrox g200eR2 is unclaimed in 14.04
Hp Microserver Gen8 with Ubuntu 16.04 LTS. Same problem. sudo lshw -C display [sudo] password for user: *-display UNCLAIMED description: VGA compatible controller product: MGA G200EH vendor: Matrox Electronics Systems Ltd. physical id: 0.1 bus info: pci@:01:00.1 version: 00 width: 32 bits clock: 33MHz capabilities: pm msi pciexpress vga_controller bus_master cap_list configuration: latency=0 resources: memory:f900-f9ff memory:fbee-fbee3fff memory:fb00-fb7f lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 16.04.1 LTS Release:16.04 Codename: xenial uname -a Linux jenkins04 4.4.0-59-generic #80-Ubuntu SMP Fri Jan 6 17:47:47 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux -- 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/1316035 Title: matrox g200eR2 is unclaimed in 14.04 Status in xorg-server package in Ubuntu: Confirmed Bug description: On a certified Dell PowerEdge T620 server (http://www.ubuntu.com/certification/hardware/201207-11426/) The matrox video card is not recognised: lspci | grep VGA 0a:00.0 VGA compatible controller: Matrox Electronics Systems Ltd. G200eR2 lshw -C display *-display UNCLAIMED description: VGA compatible controller product: G200eR2 vendor: Matrox Electronics Systems Ltd. physical id: 0 bus info: pci@:0a:00.0 version: 00 width: 32 bits clock: 33MHz capabilities: pm vga_controller bus_master cap_list configuration: latency=64 maxlatency=32 mingnt=16 resources: memory:d800-d8ff memory:deffc000-deff memory:de00-de7f Thus xserver is not hardver accelerated. Also /dev/dri and /dev/dri/card0 is missing. kernel module mga is not loaded, although if i manually load by modprobe it works fine modprobe mga lsmod | grep mga mga40811 0 drm 302817 1 mga To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1316035/+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 1656320] [NEW] package mahjongg 1:3.18.0-1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration
Public bug reported: Its happening every time I install new updates ProblemType: Package DistroRelease: Ubuntu 16.04 Package: mahjongg 1:3.18.0-1 ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35 Uname: Linux 4.4.0-57-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 Date: Thu Jan 12 13:20:43 2017 DpkgHistoryLog: Start-Date: 2017-01-12 13:20:08 Commandline: aptdaemon role='role-commit-packages' sender=':1.90' Upgrade: libnss3-nssdb:amd64 (2:3.23-0ubuntu0.16.04.1, 2:3.26.2-0ubuntu0.16.04.2), grub-common:amd64 (2.02~beta2-36ubuntu3.2, 2.02~beta2-36ubuntu3.6), snapd:amd64 (2.17.1ubuntu1, 2.20.1ubuntu1), snap-confine:amd64 (1.0.43-0ubuntu1~16.04.1, 2.20.1ubuntu1), grub2-common:amd64 (2.02~beta2-36ubuntu3.2, 2.02~beta2-36ubuntu3.6), libnss3-1d:amd64 (2:3.23-0ubuntu0.16.04.1, 2:3.26.2-0ubuntu0.16.04.2), grub-pc:amd64 (2.02~beta2-36ubuntu3.2, 2.02~beta2-36ubuntu3.6), grub-pc-bin:amd64 (2.02~beta2-36ubuntu3.2, 2.02~beta2-36ubuntu3.6), python3-distupgrade:amd64 (1:16.04.19, 1:16.04.20), ubuntu-release-upgrader-core:amd64 (1:16.04.19, 1:16.04.20), ubuntu-core-launcher:amd64 (1.0.43-0ubuntu1~16.04.1, 2.20.1ubuntu1), ubuntu-release-upgrader-gtk:amd64 (1:16.04.19, 1:16.04.20), unattended-upgrades:amd64 (0.90ubuntu0.2, 0.90ubuntu0.3), libnss3:amd64 (2:3.23-0ubuntu0.16.04.1, 2:3.26.2-0ubuntu0.16.04.2) DuplicateSignature: package:mahjongg:1:3.18.0-1 Processing triggers for ureadahead (0.100.0-19) ... ureadahead will be reprofiled on next reboot dpkg: error processing package mahjongg (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2013-09-10 (1220 days ago) InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64 (20130213) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.15ubuntu0.2 SourcePackage: gnome-mahjongg Title: package mahjongg 1:3.18.0-1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: Upgraded to xenial on 2016-11-11 (63 days ago) ** Affects: gnome-mahjongg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-mahjongg in Ubuntu. https://bugs.launchpad.net/bugs/1656320 Title: package mahjongg 1:3.18.0-1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in gnome-mahjongg package in Ubuntu: New Bug description: Its happening every time I install new updates ProblemType: Package DistroRelease: Ubuntu 16.04 Package: mahjongg 1:3.18.0-1 ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35 Uname: Linux 4.4.0-57-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 Date: Thu Jan 12 13:20:43 2017 DpkgHistoryLog: Start-Date: 2017-01-12 13:20:08 Commandline: aptdaemon role='role-commit-packages' sender=':1.90' Upgrade: libnss3-nssdb:amd64 (2:3.23-0ubuntu0.16.04.1, 2:3.26.2-0ubuntu0.16.04.2), grub-common:amd64 (2.02~beta2-36ubuntu3.2, 2.02~beta2-36ubuntu3.6), snapd:amd64 (2.17.1ubuntu1, 2.20.1ubuntu1), snap-confine:amd64 (1.0.43-0ubuntu1~16.04.1, 2.20.1ubuntu1), grub2-common:amd64 (2.02~beta2-36ubuntu3.2, 2.02~beta2-36ubuntu3.6), libnss3-1d:amd64 (2:3.23-0ubuntu0.16.04.1, 2:3.26.2-0ubuntu0.16.04.2), grub-pc:amd64 (2.02~beta2-36ubuntu3.2, 2.02~beta2-36ubuntu3.6), grub-pc-bin:amd64 (2.02~beta2-36ubuntu3.2, 2.02~beta2-36ubuntu3.6), python3-distupgrade:amd64 (1:16.04.19, 1:16.04.20), ubuntu-release-upgrader-core:amd64 (1:16.04.19, 1:16.04.20), ubuntu-core-launcher:amd64 (1.0.43-0ubuntu1~16.04.1, 2.20.1ubuntu1), ubuntu-release-upgrader-gtk:amd64 (1:16.04.19, 1:16.04.20), unattended-upgrades:amd64 (0.90ubuntu0.2, 0.90ubuntu0.3), libnss3:amd64 (2:3.23-0ubuntu0.16.04.1, 2:3.26.2-0ubuntu0.16.04.2) DuplicateSignature: package:mahjongg:1:3.18.0-1 Processing triggers for ureadahead (0.100.0-19) ... ureadahead will be reprofiled on next reboot dpkg: error processing package mahjongg (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2013-09-10 (1220 days ago) InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64 (20130213) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.15ubuntu0.2 SourcePackage: gnome-mahjongg Title: package mahjongg 1:3.18.0-1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: Upgraded to xenial on 201
[Desktop-packages] [Bug 1560498] Re: Unity8 using vmwgfx_dri.so crashed in mir::graphics::nested::detail::DisplayBuffer::make_current() -> eglMakeCurrent() -> ... -> dri2_image_get_buffers() [platform
nevertheless thanks for the progress on this one. lots of folks requesting. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1560498 Title: Unity8 using vmwgfx_dri.so crashed in mir::graphics::nested::detail::DisplayBuffer::make_current() -> eglMakeCurrent() -> ... -> dri2_image_get_buffers() [platform_mir.c:138] Status in Mir: Triaged Status in mesa package in Ubuntu: Triaged Status in mir package in Ubuntu: Triaged Status in unity8 package in Ubuntu: Invalid Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding unity8. This problem was most recently seen with version 8.11+16.04.20160310.4-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/7e3f860c1afbbc114bf73f9d7a2966209a25093d contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1560498/+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 1560498] Re: Unity8 using vmwgfx_dri.so crashed in mir::graphics::nested::detail::DisplayBuffer::make_current() -> eglMakeCurrent() -> ... -> dri2_image_get_buffers() [platform
can we please roll back the "importance" to high? i think it meeets the criteria High: A bug which fulfills any of the following criteria: Has a severe impact on a small portion of Ubuntu users (estimated) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1560498 Title: Unity8 using vmwgfx_dri.so crashed in mir::graphics::nested::detail::DisplayBuffer::make_current() -> eglMakeCurrent() -> ... -> dri2_image_get_buffers() [platform_mir.c:138] Status in Mir: Triaged Status in mesa package in Ubuntu: Triaged Status in mir package in Ubuntu: Triaged Status in unity8 package in Ubuntu: Invalid Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding unity8. This problem was most recently seen with version 8.11+16.04.20160310.4-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/7e3f860c1afbbc114bf73f9d7a2966209a25093d contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1560498/+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 1656315] [NEW] nividia driver 304 not loading under Trusty
Public bug reported: Ongoing problem (for nearly one year) with nvidia drivers not installing properly with Trusty. Xorg updates have broken nvidia support for this card. I've asked questions and filed reports to no avail and no solutions. NV7900 card, nv304 driver. Not getting direct rendering nor openGL On this same system Sparky Linux loads nv304 properly but Trusty does not. I've tried using AskUbuntu but they are purging all my requests. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 4.4.0-59.80~14.04.1-generic 4.4.35 Uname: Linux 4.4.0-59-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 304.132 Fri Sep 16 11:02:09 PDT 2016 GCC version: gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04.3) ApportVersion: 2.14.1-0ubuntu3.23 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE CurrentDmesg: [ 15.764684] init: plymouth-upstart-bridge main process ended, respawning [ 15.769251] init: plymouth-upstart-bridge main process (1681) terminated with status 1 [ 15.769259] init: plymouth-upstart-bridge main process ended, respawning Date: Fri Jan 13 09:57:36 2017 DistUpgraded: 2016-09-06 12:12:12,865 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: nvidia-304, 304.132, 4.2.0-42-generic, x86_64: installed nvidia-304, 304.132, 4.4.0-59-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation G71 [GeForce 7900 GT/GTO] [10de:0291] (rev a1) (prog-if 00 [VGA controller]) Subsystem: NVIDIA Corporation Device [10de:c560] InstallationDate: Installed on 2016-02-25 (322 days ago) InstallationMedia: Xubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 (20160217.1) LightdmGreeterLog: ** (lightdm-gtk-greeter:1699): WARNING **: Failed to load user image: Failed to open file '/home/west/.face': Permission denied init: indicator-application main process (1735) killed by TERM signal LightdmGreeterLogOld: ** (lightdm-gtk-greeter:1509): WARNING **: Failed to load user image: Failed to open file '/home/west/.face': Permission denied init: indicator-power main process (1551) killed by TERM signal init: indicator-application main process (1559) killed by TERM signal MachineType: Gigabyte Technology Co., Ltd. GA-78LMT-USB3 6.0 PlymouthDebug: Error: [Errno 13] Permission denied: '/var/log/plymouth-debug.log' ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-59-generic root=UUID=235d26fb-efcc-4956-87be-776b1494d2d3 ro nosplash=1 vt.handoff=7 drm.debug=0xe plymouth:debug SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to trusty on 2016-09-06 (128 days ago) dmi.bios.date: 11/25/2014 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F2 dmi.board.name: GA-78LMT-USB3 6.0 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: SEx dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF2:bd11/25/2014:svnGigabyteTechnologyCo.,Ltd.:pnGA-78LMT-USB36.0:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-78LMT-USB36.0:rvrSEx:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-78LMT-USB3 6.0 dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.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.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Fri Jan 13 09:52:58 2017 xserver.configfile: default xserver.errors: open /dev/fb0: No such file or directory xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.18.3-1ubuntu2.2~trusty3 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty 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/1656315 Title: nividia driver 304 not loading under Trusty Status in xorg package in Ubuntu: New Bug description: Ongoing problem (for nearly one year) with nvidia drivers not installing properly with Trusty. Xorg updates have broken nvidia support for this card. I've asked questions and filed reports to no av
[Desktop-packages] [Bug 1648992] Re: [SRU] Update gnome-calculator to 3.22.2
Uploaded You might get asked to improve the test case - please do that if so. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-calculator in Ubuntu. https://bugs.launchpad.net/bugs/1648992 Title: [SRU] Update gnome-calculator to 3.22.2 Status in gnome-calculator package in Ubuntu: Fix Released Status in gnome-calculator source package in Yakkety: Triaged Bug description: Impact == This update includes the new upstream bugfix 3.22.1 and 3.22.2 releases. https://git.gnome.org/browse/gnome-calculator/tree/NEWS?h=gnome-3-22 https://git.gnome.org/browse/gnome-calculator/log?h=gnome-3-22 Test Case = Regression Potential The uploads are happening under the GNOME Micro Release Exception. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calculator/+bug/1648992/+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 1633408] Re: [SRU] 3.22.0 wont allow cut&paste in history pane
Uploaded, thanks! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-calculator in Ubuntu. https://bugs.launchpad.net/bugs/1633408 Title: [SRU] 3.22.0 wont allow cut&paste in history pane Status in GNOME Calculator: Fix Released Status in gnome-calculator package in Ubuntu: Fix Released Status in gnome-calculator source package in Yakkety: Triaged Bug description: Impact == This update includes the new upstream bugfix 3.22.1 and 3.22.2 releases. https://git.gnome.org/browse/gnome-calculator/tree/NEWS?h=gnome-3-22 https://git.gnome.org/browse/gnome-calculator/log?h=gnome-3-22 Test Case = Regression Potential The uploads are happening under the GNOME Micro Release Exception. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-calculator/+bug/1633408/+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 1619600] Re: [SRU] New stable release 1.8.3
I uploaded -good again. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gst-plugins-base1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1619600 Title: [SRU] New stable release 1.8.3 Status in gst-libav1.0 package in Ubuntu: Fix Released Status in gst-plugins-bad1.0 package in Ubuntu: Fix Released Status in gst-plugins-base1.0 package in Ubuntu: Fix Released Status in gst-plugins-good1.0 package in Ubuntu: Fix Released Status in gst-plugins-ugly1.0 package in Ubuntu: Fix Released Status in gstreamer-vaapi package in Ubuntu: Fix Released Status in gstreamer1.0 package in Ubuntu: Fix Released Status in gst-libav1.0 source package in Xenial: Fix Committed Status in gst-plugins-bad1.0 source package in Xenial: Fix Committed Status in gst-plugins-base1.0 source package in Xenial: Fix Committed Status in gst-plugins-good1.0 source package in Xenial: Fix Committed Status in gst-plugins-ugly1.0 source package in Xenial: Fix Committed Status in gstreamer-vaapi source package in Xenial: Fix Committed Status in gstreamer1.0 source package in Xenial: Fix Committed Bug description: [ Description ] We should keep up with GStreamer's bugfix releases in the 1.8 series that 16.04 shipped with. [ QA and testing ] Play a range of videos in Totem. Play a range of audio tracks in Rhythmbox. Try to stream audio and/or video. Try to install a missing codec. In all cases, make sure that everything which worked before still works. [ Regression potential ] One of the fixes could be bad. Watch out for it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gst-libav1.0/+bug/1619600/+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 1656302] [NEW] USB sound card intermittant/unable to play audio
Public bug reported: I have a EDIROL UA-1A USB soundcard which for the most part under 12.04 worked however after a period of uptime, ALSA calls started failing with messages of this nature: ALSA lib pcm_dmix.c:1022:(snd_pcm_dmix_open) unable to open slave ALSA lib pcm_dmix.c:1022:(snd_pcm_dmix_open) unable to open slave ALSA lib pcm_dmix.c:1022:(snd_pcm_dmix_open) unable to open slave ALSA lib pcm_dmix.c:1022:(snd_pcm_dmix_open) unable to open slave and the kernel ring buffer would have streams of: [673754.825092] xhci_hcd :02:00.0: ERROR Transfer event TRB DMA ptr not part of current TD [673754.830412] xhci_hcd :02:00.0: ERROR Transfer event TRB DMA ptr not part of current TD and: [673429.575699] retire_capture_urb: 596 callbacks suppressed sometimes unplugging/plugging the card would fix this, other times a system reboot was required. Since the upgrade to 14.04 this seems to have got worse in that most of the time it behaves in this manner and the unplugging/plugging approach never works. From a kernel perspective, I was already running a 3.13.x release with 12.04 so there's not been a major update on this front since the upgrade. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: pulseaudio 1:4.0-0ubuntu11.1 ProcVersionSignature: Ubuntu 3.13.0-106.153-generic 3.13.11-ckt39 Uname: Linux 3.13.0-106-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.23 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jon 25970 F pulseaudio /dev/snd/pcmC0D0c: jon 25970 F...m pulseaudio /dev/snd/pcmC0D0p: jon 25970 F...m pulseaudio CurrentDesktop: LXDE Date: Fri Jan 13 12:56:13 2017 InstallationDate: Installed on 2013-07-25 (1268 days ago) InstallationMedia: Ubuntu-Server 12.04.2 LTS "Precise Pangolin" - Release amd64 (20130214) ProcEnviron: LANGUAGE=en_GB:en TERM=xterm PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio Symptom: audio UpgradeStatus: Upgraded to trusty on 2016-12-28 (15 days ago) dmi.bios.date: 02/22/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: X9SBAA dmi.board.vendor: Supermicro dmi.board.version: 0123456789 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 17 dmi.chassis.vendor: Supermicro dmi.chassis.version: 0123456789 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd02/22/2013:svnSupermicro:pnX9SBAA:pvr0123456789:rvnSupermicro:rnX9SBAA:rvr0123456789:cvnSupermicro:ct17:cvr0123456789: dmi.product.name: X9SBAA dmi.product.version: 0123456789 dmi.sys.vendor: Supermicro ** Affects: ubuntu Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages trusty ** Package changed: pulseaudio (Ubuntu) => ubuntu -- 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/1656302 Title: USB sound card intermittant/unable to play audio Status in Ubuntu: New Bug description: I have a EDIROL UA-1A USB soundcard which for the most part under 12.04 worked however after a period of uptime, ALSA calls started failing with messages of this nature: ALSA lib pcm_dmix.c:1022:(snd_pcm_dmix_open) unable to open slave ALSA lib pcm_dmix.c:1022:(snd_pcm_dmix_open) unable to open slave ALSA lib pcm_dmix.c:1022:(snd_pcm_dmix_open) unable to open slave ALSA lib pcm_dmix.c:1022:(snd_pcm_dmix_open) unable to open slave and the kernel ring buffer would have streams of: [673754.825092] xhci_hcd :02:00.0: ERROR Transfer event TRB DMA ptr not part of current TD [673754.830412] xhci_hcd :02:00.0: ERROR Transfer event TRB DMA ptr not part of current TD and: [673429.575699] retire_capture_urb: 596 callbacks suppressed sometimes unplugging/plugging the card would fix this, other times a system reboot was required. Since the upgrade to 14.04 this seems to have got worse in that most of the time it behaves in this manner and the unplugging/plugging approach never works. From a kernel perspective, I was already running a 3.13.x release with 12.04 so there's not been a major update on this front since the upgrade. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: pulseaudio 1:4.0-0ubuntu11.1 ProcVersionSignature: Ubuntu 3.13.0-106.153-generic 3.13.11-ckt39 Uname: Linux 3.13.0-106-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.23 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jon 25970 F pulseaudio /dev/snd/pcmC0D0c: jon 25970 F...m pulseaudio /dev/snd/pcmC0D0p: jon 25970 F...m pulseaudio CurrentDesktop: LXDE Date: Fri Jan 13 12:56:13 2017 InstallationDate: Installed on 2013-07-25 (1268 days ago) InstallationMedia: Ubuntu-Server 12.04.2 LTS "Precise Pangolin" - Release amd64 (20130214) ProcEnviron: LANGUAGE=e
[Desktop-packages] [Bug 1638373] Re: End marker/start marker drop-down menus are empty
** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to inkscape in Ubuntu. https://bugs.launchpad.net/bugs/1638373 Title: End marker/start marker drop-down menus are empty Status in Inkscape: Triaged Status in inkscape package in Ubuntu: Fix Released Status in inkscape source package in Yakkety: Fix Committed Status in inkscape source package in Zesty: Fix Released Bug description: [ Impact ] The dropdown menus for start marker, end marker and mid markers do not contains any arrows to select. I have clean up all local settings and run inkscape fresh but the same problem. This is caused by scour being called during the build, a change inadvertently added in the 0.91-11 upload. The fix used it to just not call scour. [ Test case ] Compare the file /usr/share/inkscape/markers/markers.svg from the built package with upstream's http://bazaar.launchpad.net/~inkscape.dev/inkscape/RELEASE_0_91_BRANCH/download/nicoduf%40yahoo.fr-20110829175757-0rzahc4xhhr2l6u5/markers.svg-20091128124040-aej0x7yhxng1m6ly-449/markers.svg - it should be at the very least equivalent (if not equal), currently it contains only comments. [Regression Potential] noe really Seen in in: - Inkscape 0.91 r13725 on Ubuntu 16.10 - Inkscape 0.91-11 r13725 on Ubuntu 16.10 (official package from yakkety) - DistroRelease: Ubuntu 16.10, Package: inkscape 0.91-11 - Inkscape 0.92, ubuntu 16.04 LTS - Ubuntu 16.04 - upgrade today to 0.92 - Kubuntu 14.04, and recently updated Inkscape to version 0.92.0 To manage notifications about this bug go to: https://bugs.launchpad.net/inkscape/+bug/1638373/+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 1572456] Re: Software (gnome-software) icon shown twice inside Launcher
** Also affects: gnome-software (Ubuntu) Importance: Undecided Status: New -- 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/1572456 Title: Software (gnome-software) icon shown twice inside Launcher Status in gnome-software package in Ubuntu: New Status in unity package in Ubuntu: Confirmed Bug description: Updated today to gnome-software 3.20.1+git20160419.2.b8d2e40.ubuntu-xenial-0ubuntu1 When I launch gnome-software (now Ubuntu Software) I see 2 identical icons inside the Launcher. Sometimes if I close and launch gnome-software quickly, I can see 3 or 4 icons. = How to reproduce = * install updates (gnome-software 3.20.1+git20160419.2.b8d2e40.ubuntu-xenial-0ubuntu1) * launch Ubuntu Software and lock the icon on the Launcher * close and launch again Ubuntu Software many times DistroRelease: Ubuntu 16.04 Package: gnome-software 3.20.1+git20160419.2.b8d2e40.ubuntu-xenial-0ubuntu1 Uname -r: 4.4.0-21-generic Architecture: amd64 CurrentDesktop: Unity To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1572456/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 797485] Re: SRU: Status Bar Covers File Name at Bottom
** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/797485 Title: SRU: Status Bar Covers File Name at Bottom Status in Nautilus: Fix Released Status in nautilus package in Ubuntu: Fix Released Status in nautilus source package in Xenial: Fix Committed Bug description: [Impact] If using Nautilus without a status bar the selected item title 'floats' at the bottom of the file listing. If you choose the last file item in a list this 'floating' title prevents you seeing the actual title making editing difficult/impossible. This issue is also present in icon view if you have an even number of files on the bottom row it becomes difficult to rename the last file as the status bar covers the text area. [Test Case] Using Ubuntu 16.04.1 open the file manager, click "Home", enable list view and resize the file manager window so that the contents of the home directory just fit vertically and horizontally. Select the last item in the file listing and then move the mouse slowly from left to right and back again several time. You will see the floating status bar will jump from left to right, obscuring details of the selected item. After the patched nautilus package is installed, performing the same test will result on the floating status bar being hidden when the mouse hovers over it. [Regression Potential] None. This patch has been adapted from the following upstream commit: * https://git.gnome.org/browse/nautilus/commit/?id=e66d3ca Packages have been built in a PPA and tested for regressions. [ Other Info ] Binary package hint: nautilus The following possible solutions were considered: * Give the file list a bottom margin of the height of the status bar. * Move status bar to the left side when working with files in that corner. * Do not show status bar while renaming. * Hide the floating bars when hovering over part of the selection. To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/797485/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1639180] Re: no login possible after update to nvidia 304.132
BTW: sudo apt-add-repository --remove ppa:graphics-drivers/ppa can (and should) be used instead of: sudo rm /etc/apt/sources.list.d/graphics-drivers-ubuntu-ppa-xenial.list (I just didn't know that apt-add-repository has --remove option.) And the recipe in #68-#69 in only for Ubuntu 16.04.1. -- 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/1639180 Title: no login possible after update to nvidia 304.132 Status in nvidia-graphics-drivers-304 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-304 source package in Xenial: Triaged Status in nvidia-graphics-drivers-legacy-304xx package in Debian: Fix Released Bug description: Ubuntu 16.04 LTS NVIDIA driver: - nvidia-graphics-drivers-304 - update to version 304.132 dpkg.log: upgrade nvidia-304-updates:amd64 304.131-0ubuntu3 304.132-0ubuntu0.16.04.2 - reboot - lightdm login screen - login - a few seconds some flickering - and the lightdm login screen appears again It is not possible to login. Unity is not loading. .xsession-errors: X Error of failed request: BadValue (integer parameter out of range for operation) Major opcode of failed request: 155 (GLX) Minor opcode of failed request: 3 (X_GLXCreateContext) Value in failed request: 0x0 Serial number of failed request: 34 Current serial number in output stream: 35 See also bug 1634802 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1639180/+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 1639180] Re: no login possible after update to nvidia 304.132
Yes, there is: 1. To try PPA: sudo add-apt-repository ppa:graphics-drivers/ppa sudo apt-get update sudo apt-get install nvidia-304=304.134-0ubuntu0.16.04.1 \ nvidia-opencl-icd-304=304.134-0ubuntu0.16.04.1 \ libcuda1-304=304.134-0ubuntu0.16.04.1 \ nvidia-settings=375.26-0ubuntu0~gpu16.04.1 \ libxnvctrl0=375.26-0ubuntu0~gpu16.04.1 2. To revert: sudo rm /etc/apt/sources.list.d/graphics-drivers-ubuntu-ppa-xenial.list sudo apt-get update sudo apt-get install nvidia-304=304.131-0ubuntu3 \ nvidia-opencl-icd-304=304.131-0ubuntu3 \ libcuda1-304=304.131-0ubuntu3 \ nvidia-settings=361.42-0ubuntu1 \ libxnvctrl0=361.42-0ubuntu1 (Note 1: This recipe is valid now. It refers specific versions that are in Ubuntu 16.04.1 and in PPA _now_. Not sure if it will work later, if a repository removes old versions.) (Note 2: Every command looking like: part1 \ part2 \ … \ lastPart -- is a single command. You can either paste it all-at-once, or line-by-line (last line is without "\", other lines must end with "\"). Or you may merge it into single line _with removing slashes_ ("part1 part2 … lastPart").) But, as 304.131 works for you, you have no need to explicitly upgrade to 304.134. Just wait until 304.134 will appear itself. (Sorry, first I didn't realize that 304.131 works for you.) -- 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/1639180 Title: no login possible after update to nvidia 304.132 Status in nvidia-graphics-drivers-304 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-304 source package in Xenial: Triaged Status in nvidia-graphics-drivers-legacy-304xx package in Debian: Fix Released Bug description: Ubuntu 16.04 LTS NVIDIA driver: - nvidia-graphics-drivers-304 - update to version 304.132 dpkg.log: upgrade nvidia-304-updates:amd64 304.131-0ubuntu3 304.132-0ubuntu0.16.04.2 - reboot - lightdm login screen - login - a few seconds some flickering - and the lightdm login screen appears again It is not possible to login. Unity is not loading. .xsession-errors: X Error of failed request: BadValue (integer parameter out of range for operation) Major opcode of failed request: 155 (GLX) Minor opcode of failed request: 3 (X_GLXCreateContext) Value in failed request: 0x0 Serial number of failed request: 34 Current serial number in output stream: 35 See also bug 1634802 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1639180/+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 1643544] Re: HP Scanjet 7400c Scanner locks USB2 port
Thanks for your attention. I did a SSO login and opened this issue web page (1643544). Then did the command: apport-collect 1643544 Package sane-backends not installed and no hook available, ignoring Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged. A window pops up "no further information gathered" (see attachment) $ sudo apt-get install sane-backends says that the package cannot be found. I cannot find it in synaptic either. And this page (https://launchpad.net/ubuntu/+source/sane-backends/1.0.25+git20150528-1ubuntu2) says, that it's for USB3 "or fast recent hardware" - which is not available at my system. So - what can I do now. ** Attachment added: "Bildschirmfoto von »2017-01-13 10-52-53«.jpg" https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1643544/+attachment/4803793/+files/Bildschirmfoto%20von%20%C2%BB2017-01-13%2010-52-53%C2%AB.jpg -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to sane-backends in Ubuntu. https://bugs.launchpad.net/bugs/1643544 Title: HP Scanjet 7400c Scanner locks USB2 port Status in sane-backends package in Ubuntu: Incomplete Bug description: When trying to scan with the hp7400c (avision backend), the scanner will stop in the middle of the page, no further commands on a USB mouse or keyboard are possible. xsane will throw a I/O device error. This happens on my desktop with ubuntu 16.10 (Kernel 4.8.0-27) and my laptop (kernel 4.4.0-38) NO USB3 hardware is involved in my case, both machines have USB2-ports only, lsmod does NOT show and xhci modules loaded. I tried the command SANE_DEBUG_AVISION=8 SANE_DEBUG_SANEI_USB=5 scanimage > scanfehlerxx.txt and produced the files attached. The key statement might be: [sanei_usb] sanei_usb_read_bulk: trying to read 61054 bytes [sanei_usb] sanei_usb_read_bulk: read failed: No such device (it may have been disconnected) [avision] read 0 bytes [avision] No data arrived. This error occurs as well with Fedora 24, but NOT with debian 8.6. So it may be related with the more recent kernels and their behaviour on the USB ports. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1643544/+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 1638373] Re: End marker/start marker drop-down menus are empty
Confirmed that the latest proposed package version solved the bug. Package version: inkscape: Installed: 0.91-11ubuntu16.10.1 Candidate: 0.91-11ubuntu16.10.1 Version table: *** 0.91-11ubuntu16.10.1 400 400 http://nl.archive.ubuntu.com/ubuntu yakkety-proposed/main amd64 Packages 100 /var/lib/dpkg/status 0.91-11 500 500 http://nl.archive.ubuntu.com/ubuntu yakkety/main amd64 Packages -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to inkscape in Ubuntu. https://bugs.launchpad.net/bugs/1638373 Title: End marker/start marker drop-down menus are empty Status in Inkscape: Triaged Status in inkscape package in Ubuntu: Fix Released Status in inkscape source package in Yakkety: Fix Committed Status in inkscape source package in Zesty: Fix Released Bug description: [ Impact ] The dropdown menus for start marker, end marker and mid markers do not contains any arrows to select. I have clean up all local settings and run inkscape fresh but the same problem. This is caused by scour being called during the build, a change inadvertently added in the 0.91-11 upload. The fix used it to just not call scour. [ Test case ] Compare the file /usr/share/inkscape/markers/markers.svg from the built package with upstream's http://bazaar.launchpad.net/~inkscape.dev/inkscape/RELEASE_0_91_BRANCH/download/nicoduf%40yahoo.fr-20110829175757-0rzahc4xhhr2l6u5/markers.svg-20091128124040-aej0x7yhxng1m6ly-449/markers.svg - it should be at the very least equivalent (if not equal), currently it contains only comments. [Regression Potential] noe really Seen in in: - Inkscape 0.91 r13725 on Ubuntu 16.10 - Inkscape 0.91-11 r13725 on Ubuntu 16.10 (official package from yakkety) - DistroRelease: Ubuntu 16.10, Package: inkscape 0.91-11 - Inkscape 0.92, ubuntu 16.04 LTS - Ubuntu 16.04 - upgrade today to 0.92 - Kubuntu 14.04, and recently updated Inkscape to version 0.92.0 To manage notifications about this bug go to: https://bugs.launchpad.net/inkscape/+bug/1638373/+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 1619354] Re: [SRU] network-manager-applet
- d/rules: updated in changelog - bug #1651019, for zesty there's a branch needs sponsor as well: https://code.launchpad.net/~network-manager/network-manager/+git/ubuntu-applet/+ref/master - for #1597151 I think it's harmless to ignore since they got verified in yakkety for quite some time... As for the rename, they would make diffs between yakkety and xenial trivial thus I believe it's worthwhile. -- 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/1619354 Title: [SRU] network-manager-applet Status in network-manager-applet package in Ubuntu: Triaged Bug description: [Impact] Several defects in network-manager-applet can lead to crashes under certain circumstance as tracked in errors.ubuntu.com, upstream stable bug fix release 1.2.6 should fix a big portion of the bugs while no feature is being added or changed. [Test Case] After upgrading to 1.2.6, crash cases should be lesser than previous, and no functional regression should be observed. [Regression Potential] Potential of causing regression is minimal as upstream fixes aren't significant in this small package during the stable branch maintenance. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1619354/+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 1645698] Re: [SRU] Upgrade network-manager to latest point release
- d/rules: yes that helped a lot for testing - commenting out patch: in xenial branch we haven't switched to gbp-pq yet, and historically some patches were commented out when not used, and I'm following it - it was believed not useful during a bunch update of n-m 1.2 packages (both debian and ubuntu), but later we switched back to hook up the service in WantedBy=network-online.target dynamically. This change makes it easier to disable the service and is what we have in yakkety, but the change can be dropped if it's not appropriate for SRU. -- 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/1645698 Title: [SRU] Upgrade network-manager to latest point release Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Xenial: Triaged Status in network-manager source package in Yakkety: Fix Committed Bug description: [Impact] This SRU would try to have the latest well-tested upstream point release (1.2.6) of 1.2.x land in Xenial, which is the successor of the current 1.2.2 version, fixing quite some bugs that's suitable to land in the stable branch. https://cgit.freedesktop.org/NetworkManager/NetworkManager/tree/NEWS?h=nm-1-2 [Test Case] After installing the updated version, users should be able to avoid some mem leaks in some cases and have generally improved DNS related experiences. [Regression Potential] This is a bug/regression fix for 1.2.2 and 1.2.4, which is quite complete. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1645698/+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