[Desktop-packages] [Bug 221363] Re: Policy Kit Unlock Buttons Greyed Out when using NX / VNC / LTSP
I've just installed 16.04LTS and confirmed this problem still exists. And there's no org.freedesktop.SystemToolsBackends.policy in /usr/share/polkit-1/actions. I tried to find related policy, but I couldn't. Is there any workaround to fix this with polkit settings like https://bugs.launchpad.net/ubuntu/+source/policykit/+bug/221363/comments/58 ? Thanks in advance. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to system-tools-backends in Ubuntu. https://bugs.launchpad.net/bugs/221363 Title: Policy Kit Unlock Buttons Greyed Out when using NX / VNC / LTSP Status in FreeNX Server: Fix Released Status in gdm: New Status in PolicyKit: Invalid Status in system-tools-backends: Fix Released Status in ltsp package in Ubuntu: Fix Released Status in policykit package in Ubuntu: Invalid Status in policykit-1 package in Ubuntu: Invalid Status in system-tools-backends package in Ubuntu: Triaged Bug description: I installed 8.04 LTS server on a system. Then installed ubuntu- desktop using apt. Installed Nomachine's NX server and connected to it. The unlock buttons on Users and Groups or Network are greyed out and un-accessible. Tried running from a term 'sudo users-admin' with the same results. Works fine with VNC and NX "Shadow" session however this is not really acceptable as it means a session has to be running on console first. I have tried to enable every option in Authorizations to allow the remote session to have privileges to no avail. output of dpkg relevant packages: ii gnome-system-t 2.22.0-0ubuntu Cross-platform configuration utilities for G ii liboobs-1-42.22.0-0ubuntu GObject based interface to system-tools-back ii policykit 0.7-2ubuntu7 framework for managing administrative polici ii system-tools-b 2.6.0-0ubuntu7 System Tools to manage computer configuratio == Workarounds == 1) *Jaunty or older* From https://bugs.launchpad.net/ubuntu/+source/policykit/+bug/238799/comments/16 (the packages from comment 24 are broken links now): I was able to get access via VNC tunneled through SSH by changing the following settings in policykit. You can do it locally via Authorizations, or you can do it remotely using "sudo ck-launch- session polkit-gnome-authorization" in a terminal window in your tunneled VNC session. This worked on Ubuntu 9.04 Server RC running xubuntu-desktop, so as always YMMV. For system configuration, change all implicit authorizations under org -> freedesktop -> systemtoolsbackends -> Manage System Configuration (org.freedesktop.systemtoolsbackends.set) to "Admin Authentication." For user management, change all implicit authorizations under org -> freedesktop -> systemtoolsbackends -> self -> Change User Configuration (org.freedesktop.systemtoolsbackends.self.set) to "Authentication." Reset gdm by rebooting or running "sudo /etc/init.d/gdm restart" from a terminal window, and you should be able to unlock the user settings control panel and other similarly useful things through your tunneled VNC session. 2) *Karmic or newer* Apply this patch: http://launchpadlibrarian.net/39471473/polkit-systemtools-remote-allow.patch # sudo cp -a /usr/share/polkit-1/actions/org.freedesktop.SystemToolsBackends.policy /usr/share/polkit-1/actions/org.freedesktop.SystemToolsBackends.policy.ori # sudo patch /usr/share/polkit-1/actions/org.freedesktop.SystemToolsBackends.policy polkit-systemtools-remote-allow.patch Then kill polkitd, it will be restarted automatically: # sudo pkill polkitd To manage notifications about this bug go to: https://bugs.launchpad.net/freenx-server/+bug/221363/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1574324] Re: pulseaudio crashes when connecting to bluetooth headphones (due to ubuntu changes?)
Never mind my last post. I did another fresh install, updated, and A2DP didn't work again... Well at least I know using a newer version of Pulse in xenial allows things to work, now to hunt down the patch(es) that fix things. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1574324 Title: pulseaudio crashes when connecting to bluetooth headphones (due to ubuntu changes?) Status in pulseaudio package in Ubuntu: In Progress Status in pulseaudio source package in Xenial: In Progress Status in pulseaudio source package in Yakkety: In Progress Bug description: When I attempt to connect my Jaybird Bluebuds X to Ubuntu 16.04 pulseaudio crashes, this does *NOT* happen with a Jambox which leads me to believe it's an intermittent problem with some hardware. This did not happen on Ubuntu 15.10 (which was an upgrade of 15.04). Ubuntu Release: Description: Ubuntu 16.04 LTS Release: 16.04 Pulseaudio Version: pulseaudio: Installed: 1:8.0-0ubuntu3 Candidate: 1:8.0-0ubuntu3 Version table: *** 1:8.0-0ubuntu3 500 500 http://gb.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status Device info: [bluetooth]# info 44:5E:F3:B4:07:29 Device 44:5E:F3:B4:07:29 Name: BlueBuds X Alias: BlueBuds X Class: 0x240404 Icon: audio-card Paired: yes Trusted: yes Blocked: no Connected: no LegacyPairing: no UUID: Headset (1108--1000-8000-00805f9b34fb) UUID: Audio Sink(110b--1000-8000-00805f9b34fb) UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb) UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb) UUID: Handsfree (111e--1000-8000-00805f9b34fb) UUID: Unknown (80ff--1000-8000-00805f9b34fb) I have also attached a debug dump of Pulseaudio when attempting to connect to the headphones. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1574324/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1588150] Re: Remove webkitgtk from archive
liferea has a RC now that was ported to webkit2gtk. Unfortunately, it regresses Unity support, see bug 1637385 for more info. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/1588150 Title: Remove webkitgtk from archive Status in Bijiben: In Progress Status in Empathy: Confirmed Status in Evolution: Fix Released Status in Geary: Confirmed Status in Liferea: New Status in LightDM Webkit Greeter: Fix Committed Status in bijiben package in Ubuntu: Triaged Status in birdfont package in Ubuntu: Fix Committed Status in cairo-dock-plugins package in Ubuntu: Triaged Status in empathy package in Ubuntu: Triaged Status in evolution package in Ubuntu: Fix Released Status in geary package in Ubuntu: Triaged Status in gnome-web-photo package in Ubuntu: Triaged Status in gtkpod package in Ubuntu: Triaged Status in liferea package in Ubuntu: Triaged Status in lightdm-webkit-greeter package in Ubuntu: In Progress Status in maildir-utils package in Ubuntu: Triaged Status in surf package in Ubuntu: Triaged Status in webkitgtk package in Ubuntu: Triaged Status in xiphos package in Ubuntu: Triaged Status in xombrero package in Ubuntu: Triaged Bug description: webkitgtk is obsolete and has been replaced by webkit2gtk. This requires things to be ported to the new API. To manage notifications about this bug go to: https://bugs.launchpad.net/bijiben/+bug/1588150/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1637385] [NEW] Update to 1.12
Public bug reported: Good news: liferea is ported to webkit2gtk (LP: #1588150) Bad news: https://github.com/lwindolf/liferea/commit/6b9a24b7ea07ae34e4d83c72fa326e6e9f3b3b2a More news: https://github.com/lwindolf/liferea/releases ** Affects: liferea (Ubuntu) Importance: Wishlist Status: New ** Tags: upgrade-software-version -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to liferea in Ubuntu. https://bugs.launchpad.net/bugs/1637385 Title: Update to 1.12 Status in liferea package in Ubuntu: New Bug description: Good news: liferea is ported to webkit2gtk (LP: #1588150) Bad news: https://github.com/lwindolf/liferea/commit/6b9a24b7ea07ae34e4d83c72fa326e6e9f3b3b2a More news: https://github.com/lwindolf/liferea/releases To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/liferea/+bug/1637385/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1637024] Re: fwupd consuming very high cpu after startup/login
Hello, Although it's possible it's a relapse/regression, the more likely situation is another corner case that causes similar symptoms. The mention in kern.log about failing to coldplug UEFI isn't the cause of this, that's expected if your manufacturer doesn't support UEFI capsule updates. A similar bug with Ubuntu 16.10 was just reported upstream here: https://github.com/hughsie/fwupd/issues/70 It has not yet been debugged. If you are technical enough, can you please follow the same steps mentioned in that bug? https://github.com/hughsie/fwupd/issues/70#issuecomment-254816591 That combination of artifacts and steps should hopefully help to narrow down what's going on. Also, please immediately back up the contents of /var/lib/app-info/yaml (and make sure you follow symlinks) as if it's caused by transient metadata in that directory it may clear up on it's own the next day and be hard to reproduce. ** Bug watch added: github.com/hughsie/fwupd/issues #70 https://github.com/hughsie/fwupd/issues/70 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to appstream-glib in Ubuntu. https://bugs.launchpad.net/bugs/1637024 Title: fwupd consuming very high cpu after startup/login Status in appstream-glib package in Ubuntu: New Status in fwupd package in Ubuntu: New Bug description: I believe this may be a regression (relapse of Bug #1591868 ). I upgraded to yakkety the other day without major incident and have all "updates" checked in the Software and Sources GUI. But after booting and logging in just now, I see fwupd consuming two full cores without letup. In kern.log I see this line: fwupd[6242]: Failed to coldplug: UEFI firmware updating not supported ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: fwupd 0.7.2-0ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0 Uname: Linux 4.8.0-26-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Wed Oct 26 19:49:20 2016 InstallationDate: Installed on 2016-07-03 (115 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: fwupd UpgradeStatus: Upgraded to yakkety on 2016-10-25 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/appstream-glib/+bug/1637024/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1593928] Re: I can't open gnome-terminal when using gcin input method after I update the system recently.
[Expired for gnome-terminal (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-terminal (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1593928 Title: I can't open gnome-terminal when using gcin input method after I update the system recently. Status in gnome-terminal package in Ubuntu: Expired Bug description: gnome terminal gcin WTF! ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gnome-terminal 3.18.3-1ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10 Uname: Linux 4.4.0-24-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity Date: Sat Jun 18 14:27:12 2016 InstallationDate: Installed on 2016-06-18 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: gnome-terminal UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1593928/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1637376] [NEW] /usr/lib/gimp/2.0/plug-ins/file-pdf-save:*** Error in `/usr/lib/gimp/2.0/plug-ins/file-pdf-save': double free or corruption (!prev): ADDR ***
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding gimp. This problem was most recently seen with package version 2.8.16-1ubuntu1.1, the problem page at https://errors.ubuntu.com/problem/ee52e01502fa05887900b148295f9903fb759386 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: gimp (Ubuntu) Importance: Undecided Status: New ** Tags: raring saucy trusty utopic vivid xenial -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gimp in Ubuntu. https://bugs.launchpad.net/bugs/1637376 Title: /usr/lib/gimp/2.0/plug-ins/file-pdf-save:*** Error in `/usr/lib/gimp/2.0/plug-ins/file-pdf-save': double free or corruption (!prev): ADDR *** Status in gimp package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gimp. This problem was most recently seen with package version 2.8.16-1ubuntu1.1, the problem page at https://errors.ubuntu.com/problem/ee52e01502fa05887900b148295f9903fb759386 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/gimp/+bug/1637376/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1637377] [NEW] /usr/lib/arm-linux-gnueabihf/cups-pk-helper-mechanism:5:g_variant_valist_new_nnp:g_variant_valist_new_leaf:g_variant_valist_new:g_variant_valist_new:g_variant_ne
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding cups-pk-helper. This problem was most recently seen with package version 0.2.5-2ubuntu2, the problem page at https://errors.ubuntu.com/problem/16e096ca36ef4ba2545d8955434351c296821878 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: cups-pk-helper (Ubuntu) Importance: Undecided Status: New ** Tags: xenial -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups-pk-helper in Ubuntu. https://bugs.launchpad.net/bugs/1637377 Title: /usr/lib/arm-linux-gnueabihf/cups-pk-helper- mechanism:5:g_variant_valist_new_nnp:g_variant_valist_new_leaf:g_variant_valist_new:g_variant_valist_new:g_variant_new_va Status in cups-pk-helper package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding cups-pk-helper. This problem was most recently seen with package version 0.2.5-2ubuntu2, the problem page at https://errors.ubuntu.com/problem/16e096ca36ef4ba2545d8955434351c296821878 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/cups-pk-helper/+bug/1637377/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1635375] Re: First letter doubled in Facebook posts.
Ok, I'm reassigning this to webkit2gtk then. The latest webkit2gtk is in Ubuntu 17.04 Alpha and Ubuntu 16.10 mostly * but not in 16.04 LTS. ** Package changed: epiphany-browser (Ubuntu) => webkit2gtk (Ubuntu) ** Changed in: webkit2gtk (Ubuntu) Status: Confirmed => Fix Released ** Also affects: webkit2gtk (Ubuntu Yakkety) Importance: Undecided Status: New ** Also affects: webkit2gtk (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: webkit2gtk (Ubuntu Xenial) Status: New => Fix Released ** Changed in: webkit2gtk (Ubuntu) Importance: Undecided => Medium ** Changed in: webkit2gtk (Ubuntu Xenial) Importance: Undecided => Medium ** Changed in: webkit2gtk (Ubuntu Yakkety) Importance: Undecided => Medium ** Changed in: webkit2gtk (Ubuntu Yakkety) Status: New => Triaged ** Changed in: webkit2gtk (Ubuntu Xenial) Status: Fix Released => Triaged ** Changed in: webkit2gtk (Ubuntu Yakkety) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to epiphany-browser in Ubuntu. https://bugs.launchpad.net/bugs/1635375 Title: First letter doubled in Facebook posts. Status in elementary OS: New Status in Epiphany Browser: Unknown Status in webkit2gtk package in Ubuntu: Fix Released Status in webkit2gtk source package in Xenial: Triaged Status in webkit2gtk source package in Yakkety: Fix Released Bug description: I am running elementary OS Loki right now, and have been struggling with justifying using the Epiphany browser as my default, but with this bug it is simply impossible. When on Facebook, and typing the first word in a post, or in a sentence, the letter is always doubled, when using the shift key. It is nearly impossible to find any information on the internet about this, and while I would prefer to run Epiphany as default browser, this is a deal breaker for me. To manage notifications about this bug go to: https://bugs.launchpad.net/elementaryos/+bug/1635375/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1604013] Re: FTBFS with GCC 6: narrowing conversion
Fixed in version 0.6.1-1.1 ** Changed in: ibus-unikey (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus-unikey in Ubuntu. https://bugs.launchpad.net/bugs/1604013 Title: FTBFS with GCC 6: narrowing conversion Status in ibus-unikey package in Ubuntu: Fix Released Bug description: Bugs from Debian project (https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=811754) From: Martin MichlmayrTo: sub...@bugs.debian.org Subject: ibus-unikey: FTBFS with GCC 6: narrowing conversion Date: Tue, 19 Jan 2016 17:52:19 -0800 Package: ibus-unikey Version: 0.6.1-1 Severity: important User: debian-...@lists.debian.org Usertags: ftbfs-gcc-6 gcc-6-narrowing This package fails to build with GCC 6. GCC 6 has not been released yet, but it's expected that GCC 6 will become the default compiler for stretch. Note that only the first error is reported; there might be more. You can find a snapshot of GCC 6 in experimental. To build with GCC 6, you can set CC=gcc-6 CXX=g++-6 explicitly. You may be able to find out more about this issue at https://gcc.gnu.org/gcc-6/changes.html > sbuild (Debian sbuild) 0.67.0 (26 Dec 2015) on dl580gen9-02.hlinux ... > /bin/bash ../libtool --tag=CXX --mode=compile g++ -DHAVE_CONFIG_H -I. -I.. -Wall-g -O2 -c -o data.lo data.cpp > libtool: compile: g++ -DHAVE_CONFIG_H -I. -I.. -Wall -g -O2 -c data.cpp -fPIC -DPIC -o .libs/data.o > data.cpp:242:1: error: narrowing conversion of ''\3777670'' from 'char' to 'unsigned char' inside { } [-Wnarrowing] > }; > ^ > > data.cpp:242:1: error: narrowing conversion of ''\3777670'' from 'char' to 'unsigned char' inside { } [-Wnarrowing] > data.cpp:242:1: error: narrowing conversion of ''\3777665'' from 'char' to 'unsigned char' inside { } [-Wnarrowing] > data.cpp:242:1: error: narrowing conversion of ''\3777665'' from 'char' to 'unsigned char' inside { } [-Wnarrowing] > data.cpp:242:1: error: narrowing conversion of ''\3777666'' from 'char' to 'unsigned char' inside { } [-Wnarrowing] > data.cpp:242:1: error: narrowing conversion of ''\3777666'' from 'char' to 'unsigned char' inside { } [-Wnarrowing] > data.cpp:242:1: error: narrowing conversion of ''\3777667'' from 'char' to 'unsigned char' inside { } [-Wnarrowing] > data.cpp:242:1: error: narrowing conversion of ''\3777667'' from 'char' to 'unsigned char' inside { } [-Wnarrowing] > data.cpp:242:1: error: narrowing conversion of ''\3777671'' from 'char' to 'unsigned char' inside { } [-Wnarrowing] > data.cpp:242:1: error: narrowing conversion of ''\3777671'' from 'char' to 'unsigned char' inside { } [-Wnarrowing] > data.cpp:242:1: error: narrowing conversion of ''\3777642'' from 'char' to 'unsigned char' inside { } [-Wnarrowing] > data.cpp:242:1: error: narrowing conversion of ''\3777651'' from 'char' to 'unsigned char' inside { } [-Wnarrowing] > data.cpp:242:1: error: narrowing conversion of ''\312'' from 'char' to 'unsigned char' inside { } [-Wnarrowing] > data.cpp:242:1: error: narrowing conversion of ''\312'' from 'char' to 'unsigned char' inside { } [-Wnarrowing] > data.cpp:242:1: error: narrowing conversion of ''\307'' from 'char' to 'unsigned char' inside { } [-Wnarrowing] > data.cpp:242:1: error: narrowing conversion of ''\307'' from 'char' to 'unsigned char' inside { } [-Wnarrowing] > data.cpp:242:1: error: narrowing conversion of ''\310'' from 'char' to 'unsigned char' inside { } [-Wnarrowing] ... -- Martin Michlmayr Linux for HPE Helion, Hewlett Packard Enterprise To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus-unikey/+bug/1604013/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1637369] [NEW] Can no longer paste a file in nautilus without keyboard
Public bug reported: In file list mode, nautilus used to either have a paste option in the titlebar menu or via a menu that could be opened from a "cog" symbol at the right-hand top of its window (and for a while, via the right-click menu if you right-clicked on whitespace instead of a file name). But the only non-keyboard option I can find in nautilus 1:3.20.3-1ubuntu3.1 now is the right-click menu, but this is not available when the nautilus window is full of filenames (as in the attached screenshot), so pasting is impossible without the keyboard in this case. What happened to the "cog" menu? IIRC correctly this was present until quite recently. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: nautilus 1:3.20.3-1ubuntu3.1 ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1 Uname: Linux 4.8.0-27-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Fri Oct 28 10:42:19 2016 GsettingsChanges: b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'" b'org.gnome.nautilus.window-state' b'geometry' b"'885x494+65+24'" b'org.gnome.nautilus.list-view' b'default-zoom-level' b"'small'" b'org.gnome.nautilus.list-view' b'use-tree-view' b'true' InstallationDate: Installed on 2016-08-12 (76 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160812) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: gnome-terminal 3.20.2-1ubuntu5 ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug package-from-proposed third-party-packages yakkety ** Attachment added: "no paste option.png" https://bugs.launchpad.net/bugs/1637369/+attachment/4768549/+files/no%20paste%20option.png -- 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/1637369 Title: Can no longer paste a file in nautilus without keyboard Status in nautilus package in Ubuntu: New Bug description: In file list mode, nautilus used to either have a paste option in the titlebar menu or via a menu that could be opened from a "cog" symbol at the right-hand top of its window (and for a while, via the right- click menu if you right-clicked on whitespace instead of a file name). But the only non-keyboard option I can find in nautilus 1:3.20.3-1ubuntu3.1 now is the right-click menu, but this is not available when the nautilus window is full of filenames (as in the attached screenshot), so pasting is impossible without the keyboard in this case. What happened to the "cog" menu? IIRC correctly this was present until quite recently. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: nautilus 1:3.20.3-1ubuntu3.1 ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1 Uname: Linux 4.8.0-27-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Fri Oct 28 10:42:19 2016 GsettingsChanges: b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'" b'org.gnome.nautilus.window-state' b'geometry' b"'885x494+65+24'" b'org.gnome.nautilus.list-view' b'default-zoom-level' b"'small'" b'org.gnome.nautilus.list-view' b'use-tree-view' b'true' InstallationDate: Installed on 2016-08-12 (76 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160812) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: gnome-terminal 3.20.2-1ubuntu5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1637369/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1626935] Re: [yakkety] desktop is black and/or flickering after plugging in a second monitor
It looks like this bug is reproducible in VirtualBox by resizing the guest window. After the nautilus update in yakkety-proposed, the bug is fixed for that use case. -- 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/1626935 Title: [yakkety] desktop is black and/or flickering after plugging in a second monitor Status in nautilus package in Ubuntu: Fix Committed Status in nautilus source package in Yakkety: Fix Committed Bug description: [ Description ] Nautilus's wallpaper drawing doesn't respond to changes in monitor configuration. Instead of your wallpaper you see black. [ Fix ] Inside nautilus, the wallpaper widget connects to GTK's "monitors- changed" signal when it is constructed. It does this only once the widget is realized - a "realized" signal handler connects to "monitors-changed". In Yakkety, the "realized" signal handler is connected after the widget is already realized, meaning that the signal handler isn't called and we don't connect to the "monitors- changed" signal. The proposed fix remedies this by checking if we are realized and explicitly calling the signal handler if so. [ QA ] Have multiple monitors. Have only one of them connected. Log in. Plug in one monitor. If it's autoactivated, check you see your background on both monitors. If not, activate it ("Displays") and do the same. [ Regression potential ] I'm not sure why or where the order changed to make the widget be realized earlier, if it matters or if this was always buggy and we got lucky. I would guess a refactoring in Nautilus itself, and so the proposed fix is safe, but watch out for other weirdness. [ Original description ] Using 16.04 daily image: 20160919(downloading date) With testing package for 4.8 kernel: ppa:canonical-kernel-team/unstable Graphic chips: 00:02.0 VGA compatible controller [0300]: Intel Corporation HD Graphics 530 [8086:191b] (rev 06) 01:00.0 3D controller [0302]: NVIDIA Corporation GM107M [GeForce GTX 960M] [10de:139b] (rev ff) Desktop wallpaper on extended display shows black background only, and the hdmi detection is very unstable. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.8.0-14.15-generic 4.8.0-rc7 Uname: Linux 4.8.0-14-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.3-0ubuntu7 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: Fri Sep 23 05:30:30 2016 DistUpgraded: Fresh install DistroCodename: yakkety DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 530 [1028:06e4] InstallationDate: Installed on 2016-09-20 (3 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160919) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f3:21d5 Elan Microelectronics Corp. Bus 001 Device 002: ID 0a5c:6410 Broadcom Corp. Bus 001 Device 004: ID 0c45:6713 Microdia Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 15 9550 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-14-generic.efi.signed root=UUID=d16ac6eb-1b3e-4aa5-813b-57b5c7ef165a ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/07/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.02.00 dmi.board.name: 0N7TVV dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA01:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 15 9550 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160706-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2 To manage notifications about this bug go to:
[Desktop-packages] [Bug 1635375] Re: First letter doubled in Facebook posts.
Note this is already fixed in the latest stable version of WebKitGTK+. We are behind in releasing a security advisory, but you should really make sure you have the latest version, as always. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to epiphany-browser in Ubuntu. https://bugs.launchpad.net/bugs/1635375 Title: First letter doubled in Facebook posts. Status in elementary OS: New Status in Epiphany Browser: Unknown Status in epiphany-browser package in Ubuntu: Confirmed Bug description: I am running elementary OS Loki right now, and have been struggling with justifying using the Epiphany browser as my default, but with this bug it is simply impossible. When on Facebook, and typing the first word in a post, or in a sentence, the letter is always doubled, when using the shift key. It is nearly impossible to find any information on the internet about this, and while I would prefer to run Epiphany as default browser, this is a deal breaker for me. To manage notifications about this bug go to: https://bugs.launchpad.net/elementaryos/+bug/1635375/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1635375] Re: First letter doubled in Facebook posts.
** Bug watch added: GNOME Bug Tracker #764653 https://bugzilla.gnome.org/show_bug.cgi?id=764653 ** Also affects: epiphany-browser via https://bugzilla.gnome.org/show_bug.cgi?id=764653 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to epiphany-browser in Ubuntu. https://bugs.launchpad.net/bugs/1635375 Title: First letter doubled in Facebook posts. Status in elementary OS: New Status in Epiphany Browser: Unknown Status in epiphany-browser package in Ubuntu: Confirmed Bug description: I am running elementary OS Loki right now, and have been struggling with justifying using the Epiphany browser as my default, but with this bug it is simply impossible. When on Facebook, and typing the first word in a post, or in a sentence, the letter is always doubled, when using the shift key. It is nearly impossible to find any information on the internet about this, and while I would prefer to run Epiphany as default browser, this is a deal breaker for me. To manage notifications about this bug go to: https://bugs.launchpad.net/elementaryos/+bug/1635375/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1574324] Re: pulseaudio crashes when connecting to bluetooth headphones (due to ubuntu changes?)
Ok, so it seems that whilst a freshly paired set of Bluebuds X defaults to HFP, I am able to switch to A2DP and have it work properly on a freshly installed and updated Xenial, with the pulseaudio package for Xenial in my PPA. Can anybody else confirm, at least with at least an up to date Xenial and pulse from my PPA? In other news, the fix for *THIS* bug is now in Zesty, and I will be preparing updates for Xenial and Yakkety. The only thing I have to test is whether the previously mentioned patch makes the out of the box experience worth the risk of backporting. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1574324 Title: pulseaudio crashes when connecting to bluetooth headphones (due to ubuntu changes?) Status in pulseaudio package in Ubuntu: In Progress Status in pulseaudio source package in Xenial: In Progress Status in pulseaudio source package in Yakkety: In Progress Bug description: When I attempt to connect my Jaybird Bluebuds X to Ubuntu 16.04 pulseaudio crashes, this does *NOT* happen with a Jambox which leads me to believe it's an intermittent problem with some hardware. This did not happen on Ubuntu 15.10 (which was an upgrade of 15.04). Ubuntu Release: Description: Ubuntu 16.04 LTS Release: 16.04 Pulseaudio Version: pulseaudio: Installed: 1:8.0-0ubuntu3 Candidate: 1:8.0-0ubuntu3 Version table: *** 1:8.0-0ubuntu3 500 500 http://gb.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status Device info: [bluetooth]# info 44:5E:F3:B4:07:29 Device 44:5E:F3:B4:07:29 Name: BlueBuds X Alias: BlueBuds X Class: 0x240404 Icon: audio-card Paired: yes Trusted: yes Blocked: no Connected: no LegacyPairing: no UUID: Headset (1108--1000-8000-00805f9b34fb) UUID: Audio Sink(110b--1000-8000-00805f9b34fb) UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb) UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb) UUID: Handsfree (111e--1000-8000-00805f9b34fb) UUID: Unknown (80ff--1000-8000-00805f9b34fb) I have also attached a debug dump of Pulseaudio when attempting to connect to the headphones. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1574324/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1637236] Re: New upstream microreleases 9.1.24, 9.3.15, 9.5.5
** Branch linked: lp:ubuntu/trusty-proposed/postgresql-9.3 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to postgresql-9.1 in Ubuntu. https://bugs.launchpad.net/bugs/1637236 Title: New upstream microreleases 9.1.24, 9.3.15, 9.5.5 Status in postgresql-9.1 package in Ubuntu: Invalid Status in postgresql-9.3 package in Ubuntu: Invalid Status in postgresql-9.5 package in Ubuntu: Fix Committed Status in postgresql-9.1 source package in Precise: Fix Committed Status in postgresql-9.1 source package in Trusty: Fix Committed Status in postgresql-9.3 source package in Trusty: Fix Committed Status in postgresql-9.5 source package in Xenial: Fix Committed Status in postgresql-9.5 source package in Yakkety: Fix Committed Status in postgresql-9.5 source package in Zesty: Fix Committed Bug description: https://www.postgresql.org/about/news/1712/ As per the standing micro-release exception these should land in stable Ubuntu releases. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postgresql-9.1/+bug/1637236/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1637355] [NEW] package python-gobject-2 2.28.6-12build1 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 1
Public bug reported: I was uninstall python2 and reinstalled ProblemType: Package DistroRelease: Ubuntu 14.04 Package: python-gobject-2 2.28.6-12build1 ProcVersionSignature: Ubuntu 3.13.0-87.133-generic 3.13.11-ckt39 Uname: Linux 3.13.0-87-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.21 Architecture: amd64 Date: Thu Oct 27 18:37:32 2016 DuplicateSignature: package:python-gobject-2:2.28.6-12build1:el subproceso instalado el script post-installation devolvió el código de salida de error 1 ErrorMessage: el subproceso instalado el script post-installation devolvió el código de salida de error 1 InstallationDate: Installed on 2015-12-23 (309 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) RelatedPackageVersions: dpkg 1.17.5ubuntu5.7 apt 1.0.1ubuntu2.15 SourcePackage: pygobject-2 Title: package python-gobject-2 2.28.6-12build1 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 1 UpgradeStatus: Upgraded to trusty on 2016-10-19 (8 days ago) ** Affects: pygobject-2 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package need-duplicate-check third-party-packages trusty -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pygobject-2 in Ubuntu. https://bugs.launchpad.net/bugs/1637355 Title: package python-gobject-2 2.28.6-12build1 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 1 Status in pygobject-2 package in Ubuntu: New Bug description: I was uninstall python2 and reinstalled ProblemType: Package DistroRelease: Ubuntu 14.04 Package: python-gobject-2 2.28.6-12build1 ProcVersionSignature: Ubuntu 3.13.0-87.133-generic 3.13.11-ckt39 Uname: Linux 3.13.0-87-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.21 Architecture: amd64 Date: Thu Oct 27 18:37:32 2016 DuplicateSignature: package:python-gobject-2:2.28.6-12build1:el subproceso instalado el script post-installation devolvió el código de salida de error 1 ErrorMessage: el subproceso instalado el script post-installation devolvió el código de salida de error 1 InstallationDate: Installed on 2015-12-23 (309 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) RelatedPackageVersions: dpkg 1.17.5ubuntu5.7 apt 1.0.1ubuntu2.15 SourcePackage: pygobject-2 Title: package python-gobject-2 2.28.6-12build1 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 1 UpgradeStatus: Upgraded to trusty on 2016-10-19 (8 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pygobject-2/+bug/1637355/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1637352] [NEW] When the system emits a sound, the mouse freezes.
Public bug reported: Every time the system emits a sound the mouse freezes and I use an audio interface MKII Roland Duo-Capture. Before Ubuntu 16.04 it worked properly. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: pulseaudio 1:9.0-2ubuntu2 ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0 Uname: Linux 4.8.0-22-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CasperVersion: 1.379 Date: Fri Oct 28 00:05:29 2016 LiveMediaBuild: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=pt_BR.UTF-8 SHELL=/bin/bash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/15/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.10 dmi.board.name: FM2A55M-VG3+ dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.10:bd12/15/2014:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnFM2A55M-VG3+:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. ** Affects: pulseaudio (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 pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1637352 Title: When the system emits a sound, the mouse freezes. Status in pulseaudio package in Ubuntu: New Bug description: Every time the system emits a sound the mouse freezes and I use an audio interface MKII Roland Duo-Capture. Before Ubuntu 16.04 it worked properly. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: pulseaudio 1:9.0-2ubuntu2 ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0 Uname: Linux 4.8.0-22-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CasperVersion: 1.379 Date: Fri Oct 28 00:05:29 2016 LiveMediaBuild: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=pt_BR.UTF-8 SHELL=/bin/bash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/15/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.10 dmi.board.name: FM2A55M-VG3+ dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.10:bd12/15/2014:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnFM2A55M-VG3+:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1637352/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1637349] [NEW] mines does not resize down
Public bug reported: When playing 30x16 the window was made appropriately larger, but when playing 8x8 the window was not made smaller again. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gnome-mines 1:3.18.2-2 ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21 Uname: Linux 4.4.0-45-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity Date: Fri Oct 28 11:06:28 2016 ExecutablePath: /usr/games/gnome-mines InstallationDate: Installed on 2015-09-08 (415 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) SourcePackage: gnome-mines UpgradeStatus: Upgraded to xenial on 2016-08-05 (83 days ago) ** Affects: gnome-mines (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-mines in Ubuntu. https://bugs.launchpad.net/bugs/1637349 Title: mines does not resize down Status in gnome-mines package in Ubuntu: New Bug description: When playing 30x16 the window was made appropriately larger, but when playing 8x8 the window was not made smaller again. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gnome-mines 1:3.18.2-2 ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21 Uname: Linux 4.4.0-45-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity Date: Fri Oct 28 11:06:28 2016 ExecutablePath: /usr/games/gnome-mines InstallationDate: Installed on 2015-09-08 (415 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) SourcePackage: gnome-mines UpgradeStatus: Upgraded to xenial on 2016-08-05 (83 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-mines/+bug/1637349/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1637032] Re: The screen keeps flashing (even in text terminal mode)
Ok, but I now have a laptop that us unusable even when booting from the liveCD Thanks -- 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/1637032 Title: The screen keeps flashing (even in text terminal mode) Status in xorg package in Ubuntu: New Bug description: After upgrading to 16.10 the screen (Desktop and Terminal)flashes intermittently making the system unusable. I get the same behaviour when booting 16.10 from the LiveCD Booting with the 4.4.0 Kernel still works ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: ubuntu-release-upgrader-core 1:16.10.8 ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1 Uname: Linux 4.8.0-27-generic x86_64 NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: Unity Date: Thu Oct 27 11:56:38 2016 InstallationDate: Installed on 2015-02-15 (619 days ago) InstallationMedia: Ubuntu 12.04.5 LTS "Precise Pangolin" - Release amd64 (20140807) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: Upgraded to yakkety on 2016-10-24 (2 days ago) VarLogDistupgradeAptlog: Error: [Errno 13] Permission denied: '/var/log/dist-upgrade/apt.log' VarLogDistupgradeMainlog: Error: [Errno 13] Permission denied: '/var/log/dist-upgrade/main.log' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1637032/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1637333] [NEW] gnome-terminal crashes when tab is dragged onto another tab's terminal area
Public bug reported: This bug occurs when I drag an existing terminal tab out of the tab bar and drop it onto the text area of the open terminal. Usually occurs by accident, to be honest (when I don't mean to drag the tab at all, for instance) but it's 100% reproducible intentionally. I found several old bug reports on similar issues, but they were either not detailed enough to figure out if they were exactly the same or were closed as duplicates of a bug that no longer exists (https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1442826). Apport generated a report (title: gnome-terminal-server crashed with SIGABRT in g_assertion_message()) for me and then helpfully explained that the bug had already been filed. It redirected me to a bug that doesn't exist (https://bugs.launchpad.net/bugs/1595907) though, so I'm refiling it here. 1. Ubuntu release: spyro@julep:~$ lsb_release -rd Description:Ubuntu 16.04.1 LTS Release:16.04 2. Package version: spyro@julep:~$ apt-cache policy gnome-terminal gnome-terminal: Installed: 3.20.2-1ubuntu3~ubuntu16.04.1 Candidate: 3.20.2-1ubuntu3~ubuntu16.04.1 Version table: *** 3.20.2-1ubuntu3~ubuntu16.04.1 500 500 http://ppa.launchpad.net/gnome3-team/gnome3-staging/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status 3.18.3-1ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages spyro@julep:~$ 3. Expected behavior: Tab should split into a new window (as it does if you drop it onto someplace that's not a gnome-terminal window). At the worst, it should go back to where it was on the tab bar instead of crashing. 4. Actual behavior: The whole gnome-terminal window crashes, losing any activity or work on other tabs. Other open gnome-terminal windows also crash and close. >From /var/log/syslog: Oct 27 14:54:03 julep org.gnome.Terminal[2217]: (gnome-terminal-server:30721): G Lib-GObject-CRITICAL **: g_object_ref: assertion 'G_IS_OBJECT (object)' failed Oct 27 14:54:03 julep org.gnome.Terminal[2217]: (gnome-terminal-server:30721): G tk-CRITICAL **: gtk_container_get_focus_child: assertion 'GTK_IS_CONTAINER (cont ainer)' failed Oct 27 14:54:03 julep org.gnome.Terminal[2217]: (gnome-terminal-server:30721): G Lib-GObject-CRITICAL **: g_object_unref: assertion 'G_IS_OBJECT (object)' failed Oct 27 14:54:03 julep org.gnome.Terminal[2217]: (gnome-terminal-server:30721): G tk-CRITICAL **: gtk_container_get_focus_child: assertion 'GTK_IS_CONTAINER (cont ainer)' failed Oct 27 14:54:03 julep org.gnome.Terminal[2217]: ** Oct 27 14:54:03 julep org.gnome.Terminal[2217]: Gtk:ERROR:/build/gtk+3.0-j0Vp0u/ gtk+3.0-3.20.8/./gtk/gtkwidget.c:5830:gtk_widget_get_frame_clock: assertion fail ed: (window != NULL) Oct 27 14:54:06 julep /usr/lib/gdm3/gdm-x-session[2197]: Activating service name ='org.gnome.Contacts.SearchProvider' Oct 27 14:54:06 julep /usr/lib/gdm3/gdm-x-session[2197]: Activating service name ='org.gnome.Documents' Oct 27 14:54:06 julep /usr/lib/gdm3/gdm-x-session[2197]: Activating service name ='org.gnome.Nautilus' I've also saved the apport-generated crash report if that would be helpful to upload. ** Affects: gnome-terminal (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1637333 Title: gnome-terminal crashes when tab is dragged onto another tab's terminal area Status in gnome-terminal package in Ubuntu: New Bug description: This bug occurs when I drag an existing terminal tab out of the tab bar and drop it onto the text area of the open terminal. Usually occurs by accident, to be honest (when I don't mean to drag the tab at all, for instance) but it's 100% reproducible intentionally. I found several old bug reports on similar issues, but they were either not detailed enough to figure out if they were exactly the same or were closed as duplicates of a bug that no longer exists (https://bugs.launchpad.net/ubuntu/+source/gnome- terminal/+bug/1442826). Apport generated a report (title: gnome-terminal-server crashed with SIGABRT in g_assertion_message()) for me and then helpfully explained that the bug had already been filed. It redirected me to a bug that doesn't exist (https://bugs.launchpad.net/bugs/1595907) though, so I'm refiling it here. 1. Ubuntu release: spyro@julep:~$ lsb_release -rd Description: Ubuntu 16.04.1 LTS Release: 16.04 2. Package version: spyro@julep:~$ apt-cache policy gnome-terminal gnome-terminal: Installed: 3.20.2-1ubuntu3~ubuntu16.04.1 Candidate: 3.20.2-1ubuntu3~ubuntu16.04.1 Version table: *** 3.20.2-1ubuntu3~ubuntu16.04.1 500 500 http://ppa.launchpad.net/gnome3-team/gnome3-staging/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status 3.18.3-1ubuntu1 500 500
[Desktop-packages] [Bug 1637032] Re: The screen keeps flashing (even in text terminal mode)
Not a bug with the release upgrader, rather with the system after upgrading. ** Package changed: ubuntu-release-upgrader (Ubuntu) => xorg (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1637032 Title: The screen keeps flashing (even in text terminal mode) Status in xorg package in Ubuntu: New Bug description: After upgrading to 16.10 the screen (Desktop and Terminal)flashes intermittently making the system unusable. I get the same behaviour when booting 16.10 from the LiveCD Booting with the 4.4.0 Kernel still works ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: ubuntu-release-upgrader-core 1:16.10.8 ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1 Uname: Linux 4.8.0-27-generic x86_64 NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: Unity Date: Thu Oct 27 11:56:38 2016 InstallationDate: Installed on 2015-02-15 (619 days ago) InstallationMedia: Ubuntu 12.04.5 LTS "Precise Pangolin" - Release amd64 (20140807) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: Upgraded to yakkety on 2016-10-24 (2 days ago) VarLogDistupgradeAptlog: Error: [Errno 13] Permission denied: '/var/log/dist-upgrade/apt.log' VarLogDistupgradeMainlog: Error: [Errno 13] Permission denied: '/var/log/dist-upgrade/main.log' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1637032/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1637032] [NEW] The screen keeps flashing (even in text terminal mode)
You have been subscribed to a public bug: After upgrading to 16.10 the screen (Desktop and Terminal)flashes intermittently making the system unusable. I get the same behaviour when booting 16.10 from the LiveCD Booting with the 4.4.0 Kernel still works ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: ubuntu-release-upgrader-core 1:16.10.8 ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1 Uname: Linux 4.8.0-27-generic x86_64 NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: Unity Date: Thu Oct 27 11:56:38 2016 InstallationDate: Installed on 2015-02-15 (619 days ago) InstallationMedia: Ubuntu 12.04.5 LTS "Precise Pangolin" - Release amd64 (20140807) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: Upgraded to yakkety on 2016-10-24 (2 days ago) VarLogDistupgradeAptlog: Error: [Errno 13] Permission denied: '/var/log/dist-upgrade/apt.log' VarLogDistupgradeMainlog: Error: [Errno 13] Permission denied: '/var/log/dist-upgrade/main.log' ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug dist-upgrade package-from-proposed yakkety -- The screen keeps flashing (even in text terminal mode) https://bugs.launchpad.net/bugs/1637032 You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1631191] Re: Display backlight won't turn on after screen timeout
Hello I have new System 76 Oryx Pro 2 (oryp2) with same issue. Im not using Ubuntu but I was asked to still make a post here. I am seeing the same bug using Arch Linux w/ Plasma 5 Kernel: x86_64 Linux 4.8.4-1-ARCH NVIDIA Driver Version: 370.28 DE: KDE5 WM: KWin CPU: Intel Core i7-6700HQ CPU @ 3.5GHz GPU: GeForce GTX 1060 RAM: 16GB -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-367 in Ubuntu. https://bugs.launchpad.net/bugs/1631191 Title: Display backlight won't turn on after screen timeout Status in nvidia-graphics-drivers-367 package in Ubuntu: Confirmed Bug description: Using nVidia driver 367.44 on Skylake Intel Processors, with 1000 series graphics, the backlight won't turn on after turned off by gnome session idle delay (org.gnome.desktop.session idle-delay). or by `xset dpms force off` Resume from suspend is unaffected. This is on a clean install of 16.10 with the 367.44 nVidia driver. This is a regression from the 367.35 driver. 367.48 and 370.28 also exhibit this behavior. This is confirmed on the following hardware: Oryx Pro 2 (oryp2) i7-6700HQ with 1070 Serval 10 (serw10) i7-6700 with 1060 Bonobo 11 (bonw11) i7-6700K with dual 1070 Steps to reproduce: 1. Install a fresh image of Yakkety and 367.44 from the graphics driver team's PPA. 2. Log in to Unity shell 3. Lock screen and wait for dimming. 4. Move the mouse to 'resume' 5. The screen will turn on, but the backlight is still off The current workaround: 1. Hit tty1 (Ctrl+Alt+F1) 2. Hit tty7 (Ctrl+Alt+F7) This will bring Unity back to life. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: nvidia-367 367.44-0ubuntu3 ProcVersionSignature: Ubuntu 4.8.0-19.21-generic 4.8.0-rc8 Uname: Linux 4.8.0-19-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CurrentDesktop: Unity Date: Thu Oct 6 16:17:11 2016 SourcePackage: nvidia-graphics-drivers-367 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-367/+bug/1631191/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1572658] Re: New Huawei Y360-U61 Android
Should be fixed since libmtp 1.1.13 [1]. [1] https://sourceforge.net/p/libmtp/code/ci/490f7c1aca5dd60aaed318ce230ed90500abb59c/ ** Changed in: libmtp (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libmtp in Ubuntu. https://bugs.launchpad.net/bugs/1572658 Title: New Huawei Y360-U61 Android Status in libmtp package in Ubuntu: Fix Committed Bug description: mtp-detect tells me: libmtp version 1.1.3 and Device 0 (VID=12d1 and PID=2567) is UNKNOWN The attempt to connect was successful and creates a lot of internal information! May be this is a valuable contribution. Have a nice dayCharlie To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libmtp/+bug/1572658/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1637107] Re: Wrong audio profile (on a Skylake system), causing volume problems.
You could try upgrading ALSA drivers, instructions here: https://wiki.ubuntu.com/Audio/UpgradingAlsa/DKMS. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1637107 Title: Wrong audio profile (on a Skylake system), causing volume problems. Status in alsa-driver package in Ubuntu: New Bug description: I have a Skylake system (ASRock Z170 Gaming-ITX/ac) with (x)Ubuntu 16.04. My speakers are connected via the SPDIF port, but there is a problem. When I inspect the audio profile (in `pavucontrol`), I see that `Analog Stereo Output (unplugged)` is selected. The speakers play regularly, even if this profile is wrong, but the volume doesn't work correctly - anything above mute will cause the speakers to play at maximum volume. If I choose the `Digital Stereo (IEC958)`, the speakers won't receive any signal at all. Debug info: ~$ lspci -vv # extract 00:1f.3 Audio device: Intel Corporation Sunrise Point-H HD Audio (rev 31) Subsystem: ASRock Incorporation Sunrise Point-H HD Audio Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel ~$ dmesg | grep 00:1f.3 [0.181004] pci :00:1f.3: [8086:a170] type 00 class 0x040300 [0.181034] pci :00:1f.3: reg 0x10: [mem 0xdf14-0xdf143fff 64bit] [0.181062] pci :00:1f.3: reg 0x20: [mem 0xdf12-0xdf12 64bit] [0.181091] pci :00:1f.3: PME# supported from D3hot D3cold [0.181176] pci :00:1f.3: System wakeup disabled by ACPI [0.579846] iommu: Adding device :00:1f.3 to group 8 [3.126041] snd_hda_intel :00:1f.3: bound :00:02.0 (ops i915_audio_component_bind_ops [i915_bpo]) [4.185983] input: HDA Intel PCH Front Mic as /devices/pci:00/:00:1f.3/sound/card0/input11 [4.186034] input: HDA Intel PCH Rear Mic as /devices/pci:00/:00:1f.3/sound/card0/input12 [4.186081] input: HDA Intel PCH Line as /devices/pci:00/:00:1f.3/sound/card0/input13 [4.186135] input: HDA Intel PCH Line Out as /devices/pci:00/:00:1f.3/sound/card0/input14 [4.186188] input: HDA Intel PCH Front Headphone as /devices/pci:00/:00:1f.3/sound/card0/input15 [4.186228] input: HDA Intel PCH HDMI/DP,pcm=3 as /devices/pci:00/:00:1f.3/sound/card0/input16 [4.186267] input: HDA Intel PCH HDMI/DP,pcm=7 as /devices/pci:00/:00:1f.3/sound/card0/input17 [4.186304] input: HDA Intel PCH HDMI/DP,pcm=8 as /devices/pci:00/:00:1f.3/sound/card0/input18 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21 Uname: Linux 4.4.0-45-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl wl ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: saverio3012 F...m pulseaudio /dev/snd/controlC0: saverio3012 F pulseaudio /dev/snd/controlC1: saverio3012 F pulseaudio CurrentDesktop: XFCE Date: Thu Oct 27 10:21:31 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2016-07-11 (108 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Microsoft® LifeCam VX-2000 - Microsoft® LifeCam VX-2000 Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: None of the above Title: [HDA-Intel - HDA Intel PCH, playback] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/30/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P7.10 dmi.board.name: Z170 Gaming-ITX/ac dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP7.10:bd09/30/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ170Gaming-ITX/ac:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1637107/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to :
[Desktop-packages] [Bug 1589605] Re: evolution-calendar-factory uses lots of memory
Still happens in 16.04.1 with Gnome 3.18, the evolution-calendar- factory-subprocess and evolution-source-registry process are the highest ranked in the system monitor, with 12% and 8% of CPU usage and a memory usage of around 100MB. -- 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/1589605 Title: evolution-calendar-factory uses lots of memory Status in evolution package in Ubuntu: Invalid Status in evolution-data-server package in Ubuntu: Confirmed Status in indicator-datetime package in Ubuntu: Expired Bug description: As filed under bug #1342123 (under Canonical System Image, i.e. for mobile installs) by several users, including desktop installs, evolution-calendar-factory (previsouly in 14.04) then evolution-calendar-factory-subprocess (in 16.04) run using several hundreds of megabytes of memory (~ 300 Mio in my case). This might have to do with having lots of linked calendars (Google Agenda or other). Another user on my system has much fewer Google Agendas than me and her memory usage of evolution-calendar-factory-subprocess is less, but still close to 100 Mio. There have been random crashes of the process, mostly directly upon login, always caused by addressing memory out of range. There used to be a workaround by invoking the process a second time, which caused it to exit more or less gracefully. This is not the case anymore in 16.04. Unfortunately, searching Google leads to the bug #1342123 which concerns "Canonical System Image", and several users have replied even though it does not only concern mobile installs, which is not immediately self-evident when you are not aware what "Canonical System Image" stands for… To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1589605/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1636282] Re: network-manager after suspend showing arrow icon instead of wifi icon and showing no wifi networks
I seeing the same as rjb, when I do the "service network-manager restart" once, I see the WiFi icon return and see nearby WiFi networks as well, however I have some VPNs set up and they don't reappear in network manager. I have to go to System Settings -> Network and turn them on there and then they won't show as "connected" when in fact they are. Very annoying. -- 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/1636282 Title: network-manager after suspend showing arrow icon instead of wifi icon and showing no wifi networks Status in network-manager package in Ubuntu: Confirmed Bug description: As requested by Mathieu Trudel-Lapierre (cyphermox) in bug #1589401 I'm creating my own bug report. 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu $ lsb_release -rd Description: Ubuntu 16.04.1 LTS Release: 16.04 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center $ apt-cache policy network-manager network-manager: Installiert: 1.2.2-0ubuntu0.16.04.3 Installationskandidat: 1.2.2-0ubuntu0.16.04.3 Versionstabelle: *** 1.2.2-0ubuntu0.16.04.3 500 500 http://ch.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.1.93-0ubuntu4 500 500 http://ch.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 3) What you expected to happen I'm connected by WiFi only, not by a wired connection. I expect to see the WiFi icon anytime while being connected to my WiFi network. Also, I expect to see all the WiFi networks around me (at least one other network with good reception and about 3 with bad reception). 4) What happened instead After waking up the laptop from suspend, there appears the ethernet icon (arrow symbols) instead of the WiFi icon. Also, in this state there are no other WiFi networks visible in the network-manager. However, the laptop is still connected with my WiFi and the connection works as usual. Using "service network-manager restart" in the console I can get the wireless icon back and all the other networks around me are visible again. This can be reproduced anytime and with 100% "success rate". The problem appeared with Ubuntu 16.10 and was persistent since. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.2.2-0ubuntu0.16.04.3 ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21 Uname: Linux 4.4.0-45-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity Date: Mon Oct 24 20:06:09 2016 EcryptfsInUse: Yes IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-05-15 (161 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) IpRoute: default via 192.168.1.1 dev wlo1 proto static metric 600 169.254.0.0/16 dev wlo1 scope link metric 1000 192.168.1.0/24 dev wlo1 proto kernel scope link src 192.168.1.244 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH wlo1wifi connected/org/freedesktop/NetworkManager/Devices/2 WiNet 2 162de978-4466-46b0-957b-5f9c141d702a /org/freedesktop/NetworkManager/ActiveConnection/1 eno1ethernet unavailable /org/freedesktop/NetworkManager/Devices/0 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.2.2connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1636282/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1637236] Please test proposed package
Hello Martin, or anyone else affected, Accepted postgresql-9.1 into precise-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/postgresql-9.1/9.1.24-0ubuntu0.12.04 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to postgresql-9.1 in Ubuntu. https://bugs.launchpad.net/bugs/1637236 Title: New upstream microreleases 9.1.24, 9.3.15, 9.5.5 Status in postgresql-9.1 package in Ubuntu: Invalid Status in postgresql-9.3 package in Ubuntu: Invalid Status in postgresql-9.5 package in Ubuntu: Fix Committed Status in postgresql-9.1 source package in Precise: Fix Committed Status in postgresql-9.1 source package in Trusty: Fix Committed Status in postgresql-9.3 source package in Trusty: Fix Committed Status in postgresql-9.5 source package in Xenial: Fix Committed Status in postgresql-9.5 source package in Yakkety: Fix Committed Status in postgresql-9.5 source package in Zesty: Fix Committed Bug description: https://www.postgresql.org/about/news/1712/ As per the standing micro-release exception these should land in stable Ubuntu releases. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postgresql-9.1/+bug/1637236/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1637236] Please test proposed package
Hello Martin, or anyone else affected, Accepted postgresql-9.3 into trusty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/postgresql-9.3/9.3.15-0ubuntu0.14.04 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: postgresql-9.1 (Ubuntu Trusty) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to postgresql-9.1 in Ubuntu. https://bugs.launchpad.net/bugs/1637236 Title: New upstream microreleases 9.1.24, 9.3.15, 9.5.5 Status in postgresql-9.1 package in Ubuntu: Invalid Status in postgresql-9.3 package in Ubuntu: Invalid Status in postgresql-9.5 package in Ubuntu: Fix Committed Status in postgresql-9.1 source package in Precise: Fix Committed Status in postgresql-9.1 source package in Trusty: Fix Committed Status in postgresql-9.3 source package in Trusty: Fix Committed Status in postgresql-9.5 source package in Xenial: Fix Committed Status in postgresql-9.5 source package in Yakkety: Fix Committed Status in postgresql-9.5 source package in Zesty: Fix Committed Bug description: https://www.postgresql.org/about/news/1712/ As per the standing micro-release exception these should land in stable Ubuntu releases. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postgresql-9.1/+bug/1637236/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1637236] Please test proposed package
Hello Martin, or anyone else affected, Accepted postgresql-9.5 into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/postgresql-9.5/9.5.5-0ubuntu0.16.04 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: postgresql-9.3 (Ubuntu Trusty) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to postgresql-9.1 in Ubuntu. https://bugs.launchpad.net/bugs/1637236 Title: New upstream microreleases 9.1.24, 9.3.15, 9.5.5 Status in postgresql-9.1 package in Ubuntu: Invalid Status in postgresql-9.3 package in Ubuntu: Invalid Status in postgresql-9.5 package in Ubuntu: Fix Committed Status in postgresql-9.1 source package in Precise: Fix Committed Status in postgresql-9.1 source package in Trusty: Fix Committed Status in postgresql-9.3 source package in Trusty: Fix Committed Status in postgresql-9.5 source package in Xenial: Fix Committed Status in postgresql-9.5 source package in Yakkety: Fix Committed Status in postgresql-9.5 source package in Zesty: Fix Committed Bug description: https://www.postgresql.org/about/news/1712/ As per the standing micro-release exception these should land in stable Ubuntu releases. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postgresql-9.1/+bug/1637236/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1637236] Re: New upstream microreleases 9.1.24, 9.3.15, 9.5.5
Hello Martin, or anyone else affected, Accepted postgresql-9.5 into yakkety-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/postgresql-9.5/9.5.5-0ubuntu0.16.10 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: postgresql-9.5 (Ubuntu Yakkety) Status: In Progress => Fix Committed ** Tags added: verification-needed ** Changed in: postgresql-9.5 (Ubuntu Xenial) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to postgresql-9.1 in Ubuntu. https://bugs.launchpad.net/bugs/1637236 Title: New upstream microreleases 9.1.24, 9.3.15, 9.5.5 Status in postgresql-9.1 package in Ubuntu: Invalid Status in postgresql-9.3 package in Ubuntu: Invalid Status in postgresql-9.5 package in Ubuntu: Fix Committed Status in postgresql-9.1 source package in Precise: Fix Committed Status in postgresql-9.1 source package in Trusty: Fix Committed Status in postgresql-9.3 source package in Trusty: Fix Committed Status in postgresql-9.5 source package in Xenial: Fix Committed Status in postgresql-9.5 source package in Yakkety: Fix Committed Status in postgresql-9.5 source package in Zesty: Fix Committed Bug description: https://www.postgresql.org/about/news/1712/ As per the standing micro-release exception these should land in stable Ubuntu releases. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postgresql-9.1/+bug/1637236/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1637236] Please test proposed package
Hello Martin, or anyone else affected, Accepted postgresql-9.1 into trusty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/postgresql-9.1/9.1.24-0ubuntu0.14.04 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: postgresql-9.1 (Ubuntu Precise) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to postgresql-9.1 in Ubuntu. https://bugs.launchpad.net/bugs/1637236 Title: New upstream microreleases 9.1.24, 9.3.15, 9.5.5 Status in postgresql-9.1 package in Ubuntu: Invalid Status in postgresql-9.3 package in Ubuntu: Invalid Status in postgresql-9.5 package in Ubuntu: Fix Committed Status in postgresql-9.1 source package in Precise: Fix Committed Status in postgresql-9.1 source package in Trusty: Fix Committed Status in postgresql-9.3 source package in Trusty: Fix Committed Status in postgresql-9.5 source package in Xenial: Fix Committed Status in postgresql-9.5 source package in Yakkety: Fix Committed Status in postgresql-9.5 source package in Zesty: Fix Committed Bug description: https://www.postgresql.org/about/news/1712/ As per the standing micro-release exception these should land in stable Ubuntu releases. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postgresql-9.1/+bug/1637236/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1637316] [NEW] Screen flickering/tearing on Ubuntu 16.10 64-bit on kernel version 4.8.0-26-generic
Public bug reported: After upgrading to Ubuntu 16.10 and booting with kernel version 4.8.0-26-generic, I can see screen flickering/tearing. If I boot up using previous kernel version 4.4.0, then this issues do not appear. This is an Intel GPU laptop with an nvidia graphics card. I would be glad to provide more debug information if needed. ** Affects: xserver-xorg-video-intel (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1637316 Title: Screen flickering/tearing on Ubuntu 16.10 64-bit on kernel version 4.8.0-26-generic Status in xserver-xorg-video-intel package in Ubuntu: New Bug description: After upgrading to Ubuntu 16.10 and booting with kernel version 4.8.0-26-generic, I can see screen flickering/tearing. If I boot up using previous kernel version 4.4.0, then this issues do not appear. This is an Intel GPU laptop with an nvidia graphics card. I would be glad to provide more debug information if needed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1637316/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1589401] Re: cannot view wifi networks after re-enabling wifi
After performing some more tests: The triggers for the network-manager showing the arrow icon and no WiFi networks are: - Suspend mode (suspend/wake up) - Hardware wireless button (turn WiFi off/an) - Wireless network in network-manager GUI (deactivate/activate) - Network in network-manager GUI (deactivate/activate) btw: Lock screen has no influence. When I do "service network-manager restart" once (independent of network-manager state) I'm getting rid of the problem. After this I can do everything listed above without loosing the WiFi icon and I'm always able to see the wireless networks around. As soon as I do any of this, it's back to default (meaning that next time you do anything of the listed actions above, the arrow icon will appear and you won't be able to see other wireless networks: - reboot - shut down and boot - log out and log in Again: Lock screen has no influence. -- 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/1589401 Title: cannot view wifi networks after re-enabling wifi Status in NetworkManager: Confirmed Status in network-manager package in Ubuntu: Incomplete Bug description: after re enabling wifi, up-down arrows just like wired network. cannot see any wifi ssid. To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1589401/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1636282] Re: network-manager after suspend showing arrow icon instead of wifi icon and showing no wifi networks
After performing some more tests: The triggers for the network-manager showing the arrow icon and no WiFi networks are: - Suspend mode (suspend/wake up) - Hardware wireless button (turn WiFi off/an) - Wireless network in network-manager GUI (deactivate/activate) - Network in network-manager GUI (deactivate/activate) btw: Lock screen has no influence. When I do "service network-manager restart" once (independent of network-manager state) I'm getting rid of the problem. After this I can do everything listed above without loosing the WiFi icon and I'm always able to see the wireless networks around. As soon as I do any of this, it's back to default (meaning that next time you do anything of the listed actions above, the arrow icon will appear and you won't be able to see other wireless networks: - reboot - shut down and boot - log out and log in Again: Lock screen has no influence. -- 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/1636282 Title: network-manager after suspend showing arrow icon instead of wifi icon and showing no wifi networks Status in network-manager package in Ubuntu: Confirmed Bug description: As requested by Mathieu Trudel-Lapierre (cyphermox) in bug #1589401 I'm creating my own bug report. 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu $ lsb_release -rd Description: Ubuntu 16.04.1 LTS Release: 16.04 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center $ apt-cache policy network-manager network-manager: Installiert: 1.2.2-0ubuntu0.16.04.3 Installationskandidat: 1.2.2-0ubuntu0.16.04.3 Versionstabelle: *** 1.2.2-0ubuntu0.16.04.3 500 500 http://ch.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.1.93-0ubuntu4 500 500 http://ch.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 3) What you expected to happen I'm connected by WiFi only, not by a wired connection. I expect to see the WiFi icon anytime while being connected to my WiFi network. Also, I expect to see all the WiFi networks around me (at least one other network with good reception and about 3 with bad reception). 4) What happened instead After waking up the laptop from suspend, there appears the ethernet icon (arrow symbols) instead of the WiFi icon. Also, in this state there are no other WiFi networks visible in the network-manager. However, the laptop is still connected with my WiFi and the connection works as usual. Using "service network-manager restart" in the console I can get the wireless icon back and all the other networks around me are visible again. This can be reproduced anytime and with 100% "success rate". The problem appeared with Ubuntu 16.10 and was persistent since. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.2.2-0ubuntu0.16.04.3 ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21 Uname: Linux 4.4.0-45-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity Date: Mon Oct 24 20:06:09 2016 EcryptfsInUse: Yes IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-05-15 (161 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) IpRoute: default via 192.168.1.1 dev wlo1 proto static metric 600 169.254.0.0/16 dev wlo1 scope link metric 1000 192.168.1.0/24 dev wlo1 proto kernel scope link src 192.168.1.244 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH wlo1wifi connected/org/freedesktop/NetworkManager/Devices/2 WiNet 2 162de978-4466-46b0-957b-5f9c141d702a /org/freedesktop/NetworkManager/ActiveConnection/1 eno1ethernet unavailable /org/freedesktop/NetworkManager/Devices/0 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.2.2connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to:
[Desktop-packages] [Bug 1636262] Re: package cracklib-runtime 2.9.2-3 failed to install/upgrade: dependency problems - leaving triggers unprocessed
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: cracklib2 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cracklib2 in Ubuntu. https://bugs.launchpad.net/bugs/1636262 Title: package cracklib-runtime 2.9.2-3 failed to install/upgrade: dependency problems - leaving triggers unprocessed Status in cracklib2 package in Ubuntu: Confirmed Bug description: Upon upgrade from 16.04 to 16.10 this error started occurring. I was upgrading via the integrated updater. ProblemType: Package DistroRelease: Ubuntu 16.10 Package: cracklib-runtime 2.9.2-3 ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0 Uname: Linux 4.8.0-26-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 Date: Sat Oct 22 20:43:28 2016 ErrorMessage: dependency problems - leaving triggers unprocessed InstallationDate: Installed on 2016-08-29 (56 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) RelatedPackageVersions: dpkg 1.18.10ubuntu1 apt 1.3.1 SourcePackage: cracklib2 Title: package cracklib-runtime 2.9.2-3 failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: Upgraded to yakkety on 2016-10-23 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cracklib2/+bug/1636262/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1633824] Re: nautilus ignores trash on external drives
** Changed in: nautilus (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1633824 Title: nautilus ignores trash on external drives Status in nautilus package in Ubuntu: Confirmed Bug description: Using nautilus 3.20 as included in Ubuntu 16.10, I can move files to trash in general. However only the items removed from permanently installed drives shows up in the trash virtual folder. In the case of usb removable drives, the .Trash-1000 folder is correctly created, and the files are in there but the nautilus GUI does not show those files in its virtual trash folder. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: nautilus 1:3.20.3-1ubuntu3 ProcVersionSignature: Ubuntu 4.8.0-25.27-generic 4.8.1 Uname: Linux 4.8.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Sun Oct 16 11:48:03 2016 InstallationDate: Installed on 2016-02-19 (239 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: nautilus UpgradeStatus: Upgraded to yakkety on 2016-10-13 (2 days ago) usr_lib_nautilus: gnome-terminal 3.20.2-1ubuntu5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1633824/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1633527] Re: Nautilus 3.20 : deleted items are not shown in Trash folder
*** This bug is a duplicate of bug 1633824 *** https://bugs.launchpad.net/bugs/1633824 ** This bug has been marked a duplicate of bug 1633824 nautilus ignores trash on external drives -- 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/1633527 Title: Nautilus 3.20 : deleted items are not shown in Trash folder Status in nautilus package in Ubuntu: Confirmed Bug description: After a clean installation of Ubuntu 16.10, all files and folders being deleted from mounted ext4 partitions are not shown in the Trash folder. The items being deleted from the /home directory are shown. The deleted items are present in the .Trash-1000 folder of each ext4 partition though. After permanently deleting the folder and again deleting something, the folder is recreated as expected, but the Expunged sub folder is missing and there is still nothing to be seen in the Trash folder. The same behavior occurs when doing it from the installation media. This does not happen in other Linux distributions with GNOME 3.20 desktop environment when using the Nautilus 3.20 file manager. --- ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 DistroRelease: Ubuntu 16.10 GsettingsChanges: org.gnome.nautilus.preferences click-policy 'single' org.gnome.nautilus.preferences show-delete-permanently true org.gnome.nautilus.preferences default-folder-viewer 'list-view' org.gnome.nautilus.window-state maximized true org.gnome.nautilus.list-view default-visible-columns ['name', 'size', 'type', 'date_modified'] InstallationDate: Installed on 2016-10-13 (1 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) NonfreeKernelModules: zfs zunicode zcommon znvpair zavl Package: nautilus 1:3.20.3-1ubuntu3 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0 Tags: yakkety Uname: Linux 4.8.0-22-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True usr_lib_nautilus: gnome-terminal 3.20.2-1ubuntu5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1633527/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1634009] Re: Trash on external HDs inoperative
*** This bug is a duplicate of bug 1633824 *** https://bugs.launchpad.net/bugs/1633824 ** This bug has been marked a duplicate of bug 1633824 nautilus ignores trash on external drives -- 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/1634009 Title: Trash on external HDs inoperative Status in nautilus package in Ubuntu: Confirmed Bug description: Deleting files on the internal drive moves file into Trash can. The Trash icon changes (buldge) indicating files to be expunged. On external HDs this is not the case. Files get moved to the Trash folder but the icon does not change and the menu item to empty trash is inactive. Thus, deleted files on external drives cannot be deleted via the GUI. Deleting from command file (in the .Trash folder) is possible and currently the only way to delete files on external HDs This refers to Nautilus 3.20.3 ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: nautilus 1:3.20.3-1ubuntu3 ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0 Uname: Linux 4.8.0-22-generic x86_64 NonfreeKernelModules: nvidia_uvm wl nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Mon Oct 17 09:10:27 2016 InstallationDate: Installed on 2013-05-17 (1248 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64+mac (20130424) SourcePackage: nautilus UpgradeStatus: Upgraded to yakkety on 2016-10-15 (1 days ago) usr_lib_nautilus: gnome-terminal 3.20.2-1ubuntu5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1634009/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1589401] Re: cannot view wifi networks after re-enabling wifi
Dear all, I have discovered something that may not have been reported in here so far: After a fresh boot, when you suspend the machine, there will be arrows after waking up. If you do "service network-manager restart" once, you'll get the WiFi icon back. From now on you can suspend as many times you like, the WiFi icon will stay there! However, the next time you reboot all this magic is gone. Can anyone reproduce this? -- 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/1589401 Title: cannot view wifi networks after re-enabling wifi Status in NetworkManager: Confirmed Status in network-manager package in Ubuntu: Incomplete Bug description: after re enabling wifi, up-down arrows just like wired network. cannot see any wifi ssid. To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1589401/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1636282] Re: network-manager after suspend showing arrow icon instead of wifi icon and showing no wifi networks
correction: in my description I was referring to Ubuntu 16.10, however it's 16.04.1 as seen on the lsb_release output. So I have found some anomaly in this bug: After a fresh boot, when I suspend the machine, there will be arrows after waking up. If I do "service network-manager restart" once, I'll get the WiFi icon back. From now on I can suspend as many times I like, the WiFi icon will stay there after wake-up! However, the next time I reboot all this magic is gone. -- 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/1636282 Title: network-manager after suspend showing arrow icon instead of wifi icon and showing no wifi networks Status in network-manager package in Ubuntu: Confirmed Bug description: As requested by Mathieu Trudel-Lapierre (cyphermox) in bug #1589401 I'm creating my own bug report. 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu $ lsb_release -rd Description: Ubuntu 16.04.1 LTS Release: 16.04 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center $ apt-cache policy network-manager network-manager: Installiert: 1.2.2-0ubuntu0.16.04.3 Installationskandidat: 1.2.2-0ubuntu0.16.04.3 Versionstabelle: *** 1.2.2-0ubuntu0.16.04.3 500 500 http://ch.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.1.93-0ubuntu4 500 500 http://ch.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 3) What you expected to happen I'm connected by WiFi only, not by a wired connection. I expect to see the WiFi icon anytime while being connected to my WiFi network. Also, I expect to see all the WiFi networks around me (at least one other network with good reception and about 3 with bad reception). 4) What happened instead After waking up the laptop from suspend, there appears the ethernet icon (arrow symbols) instead of the WiFi icon. Also, in this state there are no other WiFi networks visible in the network-manager. However, the laptop is still connected with my WiFi and the connection works as usual. Using "service network-manager restart" in the console I can get the wireless icon back and all the other networks around me are visible again. This can be reproduced anytime and with 100% "success rate". The problem appeared with Ubuntu 16.10 and was persistent since. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.2.2-0ubuntu0.16.04.3 ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21 Uname: Linux 4.4.0-45-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity Date: Mon Oct 24 20:06:09 2016 EcryptfsInUse: Yes IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-05-15 (161 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) IpRoute: default via 192.168.1.1 dev wlo1 proto static metric 600 169.254.0.0/16 dev wlo1 scope link metric 1000 192.168.1.0/24 dev wlo1 proto kernel scope link src 192.168.1.244 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH wlo1wifi connected/org/freedesktop/NetworkManager/Devices/2 WiNet 2 162de978-4466-46b0-957b-5f9c141d702a /org/freedesktop/NetworkManager/ActiveConnection/1 eno1ethernet unavailable /org/freedesktop/NetworkManager/Devices/0 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.2.2connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1636282/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1637236] Re: New upstream microreleases 9.1.24, 9.3.15, 9.5.5
** Changed in: postgresql-9.5 (Ubuntu Zesty) Status: In Progress => Fix Committed ** Changed in: postgresql-9.5 (Ubuntu Zesty) Assignee: (unassigned) => Martin Pitt (pitti) ** Changed in: postgresql-9.5 (Ubuntu Yakkety) Status: New => In Progress ** Changed in: postgresql-9.5 (Ubuntu Yakkety) Assignee: (unassigned) => Martin Pitt (pitti) ** Changed in: postgresql-9.3 (Ubuntu Trusty) Status: New => In Progress ** Changed in: postgresql-9.1 (Ubuntu Trusty) Status: New => In Progress ** Changed in: postgresql-9.1 (Ubuntu Precise) Status: New => In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to postgresql-9.1 in Ubuntu. https://bugs.launchpad.net/bugs/1637236 Title: New upstream microreleases 9.1.24, 9.3.15, 9.5.5 Status in postgresql-9.1 package in Ubuntu: Invalid Status in postgresql-9.3 package in Ubuntu: Invalid Status in postgresql-9.5 package in Ubuntu: Fix Committed Status in postgresql-9.1 source package in Precise: In Progress Status in postgresql-9.1 source package in Trusty: In Progress Status in postgresql-9.3 source package in Trusty: In Progress Status in postgresql-9.5 source package in Xenial: In Progress Status in postgresql-9.5 source package in Yakkety: In Progress Status in postgresql-9.5 source package in Zesty: Fix Committed Bug description: https://www.postgresql.org/about/news/1712/ As per the standing micro-release exception these should land in stable Ubuntu releases. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postgresql-9.1/+bug/1637236/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1637298] [NEW] package firefox 45.0.2+build1-0ubuntu1 failed to install/upgrade: package firefox is not ready for configuration cannot configure (current status 'half-installed
Public bug reported: installing geany via synaptic on 'raspberry pi 3' using lubuntu And while doing so I was using firefox, don't know if its due to this or not? Description:Ubuntu 16.04 LTS Release:16.04 $ apt-cache policy firefox firefox: Installed: 45.0.2+build1-0ubuntu1 Candidate: 49.0+build4-0ubuntu0.16.04.1 Version table: 49.0+build4-0ubuntu0.16.04.1 500 500 http://ports.ubuntu.com xenial-updates/main armhf Packages 500 http://ports.ubuntu.com xenial-security/main armhf Packages *** 45.0.2+build1-0ubuntu1 500 500 http://ports.ubuntu.com xenial/main armhf Packages 500 http://ports.ubuntu.com/ubuntu-ports xenial/main armhf Packages 100 /var/lib/dpkg/status And Bug-Reporter opened asked to report the issue and I choose yes. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: firefox 45.0.2+build1-0ubuntu1 Uname: Linux 4.1.19-v7+ armv7l AddonCompatCheckDisabled: False ApportVersion: 2.20.1-0ubuntu2 Architecture: armhf AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: simrat 1212 F lxpanel BuildID: 20160414070736 CRDA: N/A Channel: Unavailable Date: Fri Oct 28 01:00:02 2016 DuplicateSignature: Processing triggers for man-db (2.7.5-1) ... dpkg: error processing package firefox (--configure): package firefox is not ready for configuration ErrorMessage: package firefox is not ready for configuration cannot configure (current status 'half-installed') ForcedLayersAccel: False IpRoute: default via 192.168.0.1 dev enxb827eb585519 proto static metric 100 192.168.0.0/24 dev enxb827eb585519 proto kernel scope link src 192.168.0.100 metric 100 NoProfiles: True PciNetwork: RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.10ubuntu1 RunningIncompatibleAddons: False SourcePackage: firefox Title: package firefox 45.0.2+build1-0ubuntu1 failed to install/upgrade: package firefox is not ready for configuration cannot configure (current status 'half-installed') UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: firefox (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package armhf need-duplicate-check xenial -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1637298 Title: package firefox 45.0.2+build1-0ubuntu1 failed to install/upgrade: package firefox is not ready for configuration cannot configure (current status 'half-installed') Status in firefox package in Ubuntu: New Bug description: installing geany via synaptic on 'raspberry pi 3' using lubuntu And while doing so I was using firefox, don't know if its due to this or not? Description: Ubuntu 16.04 LTS Release: 16.04 $ apt-cache policy firefox firefox: Installed: 45.0.2+build1-0ubuntu1 Candidate: 49.0+build4-0ubuntu0.16.04.1 Version table: 49.0+build4-0ubuntu0.16.04.1 500 500 http://ports.ubuntu.com xenial-updates/main armhf Packages 500 http://ports.ubuntu.com xenial-security/main armhf Packages *** 45.0.2+build1-0ubuntu1 500 500 http://ports.ubuntu.com xenial/main armhf Packages 500 http://ports.ubuntu.com/ubuntu-ports xenial/main armhf Packages 100 /var/lib/dpkg/status And Bug-Reporter opened asked to report the issue and I choose yes. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: firefox 45.0.2+build1-0ubuntu1 Uname: Linux 4.1.19-v7+ armv7l AddonCompatCheckDisabled: False ApportVersion: 2.20.1-0ubuntu2 Architecture: armhf AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: simrat 1212 F lxpanel BuildID: 20160414070736 CRDA: N/A Channel: Unavailable Date: Fri Oct 28 01:00:02 2016 DuplicateSignature: Processing triggers for man-db (2.7.5-1) ... dpkg: error processing package firefox (--configure): package firefox is not ready for configuration ErrorMessage: package firefox is not ready for configuration cannot configure (current status 'half-installed') ForcedLayersAccel: False IpRoute: default via 192.168.0.1 dev enxb827eb585519 proto static metric 100 192.168.0.0/24 dev enxb827eb585519 proto kernel scope link src 192.168.0.100 metric 100 NoProfiles: True PciNetwork: RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.10ubuntu1 RunningIncompatibleAddons: False SourcePackage: firefox Title: package firefox 45.0.2+build1-0ubuntu1 failed to install/upgrade: package firefox is not ready for configuration cannot configure (current status 'half-installed') UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1637298/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to :
[Desktop-packages] [Bug 1626935] Re: [yakkety] desktop is black and/or flickering after plugging in a second monitor
** Changed in: nautilus (Ubuntu Yakkety) Importance: Undecided => High ** No longer affects: mesa (Ubuntu Yakkety) ** No longer affects: mesa (Ubuntu) ** No longer affects: compiz (Ubuntu Yakkety) ** No longer affects: compiz (Ubuntu) -- 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/1626935 Title: [yakkety] desktop is black and/or flickering after plugging in a second monitor Status in nautilus package in Ubuntu: Fix Committed Status in nautilus source package in Yakkety: Fix Committed Bug description: [ Description ] Nautilus's wallpaper drawing doesn't respond to changes in monitor configuration. Instead of your wallpaper you see black. [ Fix ] Inside nautilus, the wallpaper widget connects to GTK's "monitors- changed" signal when it is constructed. It does this only once the widget is realized - a "realized" signal handler connects to "monitors-changed". In Yakkety, the "realized" signal handler is connected after the widget is already realized, meaning that the signal handler isn't called and we don't connect to the "monitors- changed" signal. The proposed fix remedies this by checking if we are realized and explicitly calling the signal handler if so. [ QA ] Have multiple monitors. Have only one of them connected. Log in. Plug in one monitor. If it's autoactivated, check you see your background on both monitors. If not, activate it ("Displays") and do the same. [ Regression potential ] I'm not sure why or where the order changed to make the widget be realized earlier, if it matters or if this was always buggy and we got lucky. I would guess a refactoring in Nautilus itself, and so the proposed fix is safe, but watch out for other weirdness. [ Original description ] Using 16.04 daily image: 20160919(downloading date) With testing package for 4.8 kernel: ppa:canonical-kernel-team/unstable Graphic chips: 00:02.0 VGA compatible controller [0300]: Intel Corporation HD Graphics 530 [8086:191b] (rev 06) 01:00.0 3D controller [0302]: NVIDIA Corporation GM107M [GeForce GTX 960M] [10de:139b] (rev ff) Desktop wallpaper on extended display shows black background only, and the hdmi detection is very unstable. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.8.0-14.15-generic 4.8.0-rc7 Uname: Linux 4.8.0-14-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.3-0ubuntu7 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: Fri Sep 23 05:30:30 2016 DistUpgraded: Fresh install DistroCodename: yakkety DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 530 [1028:06e4] InstallationDate: Installed on 2016-09-20 (3 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160919) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f3:21d5 Elan Microelectronics Corp. Bus 001 Device 002: ID 0a5c:6410 Broadcom Corp. Bus 001 Device 004: ID 0c45:6713 Microdia Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 15 9550 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-14-generic.efi.signed root=UUID=d16ac6eb-1b3e-4aa5-813b-57b5c7ef165a ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/07/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.02.00 dmi.board.name: 0N7TVV dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA01:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 15 9550 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160706-1ubuntu1 version.xserver-xorg-video-nouveau:
[Desktop-packages] [Bug 1637236] Re: New upstream microreleases 9.1.24, 9.3.15, 9.5.5
Actually no, we can't sync zesty, it'll require a proper upload as Debian already moved to 9.6. ** Changed in: postgresql-9.5 (Ubuntu Zesty) Status: Fix Committed => In Progress ** Changed in: postgresql-9.5 (Ubuntu Zesty) Assignee: Martin Pitt (pitti) => (unassigned) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to postgresql-9.1 in Ubuntu. https://bugs.launchpad.net/bugs/1637236 Title: New upstream microreleases 9.1.24, 9.3.15, 9.5.5 Status in postgresql-9.1 package in Ubuntu: Invalid Status in postgresql-9.3 package in Ubuntu: Invalid Status in postgresql-9.5 package in Ubuntu: In Progress Status in postgresql-9.1 source package in Precise: New Status in postgresql-9.1 source package in Trusty: New Status in postgresql-9.3 source package in Trusty: New Status in postgresql-9.5 source package in Xenial: In Progress Status in postgresql-9.5 source package in Yakkety: New Status in postgresql-9.5 source package in Zesty: In Progress Bug description: https://www.postgresql.org/about/news/1712/ As per the standing micro-release exception these should land in stable Ubuntu releases. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postgresql-9.1/+bug/1637236/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1633855] Re: akonadi fails to start after upgrade to yakkety
I have uploaded what I believe to be a fixed package for akonadi to my PPA https://launchpad.net/~clivejo/+archive/ubuntu/yakkety/+packages?field.name_filter=akonadi_filter=published_filter= Can someone who has this problem, please test that the fix works as expected? Please only use my PPA to test this one package and remove it afterwards. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to akonadi in Ubuntu. https://bugs.launchpad.net/bugs/1633855 Title: akonadi fails to start after upgrade to yakkety Status in akonadi package in Ubuntu: Triaged Status in mysql-5.5 package in Ubuntu: New Status in akonadi source package in Precise: Fix Released Status in mysql-5.5 source package in Precise: New Status in akonadi source package in Trusty: Fix Released Status in mysql-5.5 source package in Trusty: New Status in akonadi source package in Yakkety: New Status in mysql-5.5 source package in Yakkety: New Status in akonadi source package in Zesty: Triaged Status in mysql-5.5 source package in Zesty: New Bug description: After yesterday 15 sept. upgrade to Kubuntu 16.10 Yakkety Yak, kmail fails to start, because akonadi backend fails. Starting akonadi from command line, $ akonadictl start the output contains: stderr: "mysqld: Error on realpath() on '/var/lib/mysql-files' (Error 2 - No such file or directory)\n2016-10-16T11:54:23.365277Z 0 [Warning] The syntax '--log_warnings/-W' is deprecated and will be removed in a future release. Please use '--log_error_verbosity' instead.\n2016-10-16T11:54:23.365377Z 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).\n2016-10-16T11:54:23.365479Z 0 [ERROR] Failed to access directory for --secure-file-priv. Please make sure that directory exists and is accessible by MySQL Server. Supplied value : /var/lib/mysql-files\n2016-10-16T11:54:23.365488Z 0 [ERROR] Aborting\n\n2016-10-16T11:54:23.365508Z 0 [Note] Binlog end\n" The cause is a regression in the file /etc/xdg/akonadi/mysql-global.conf provided by the package akonadi-backend-mysql Diff of the content of mysql-global.conf from Yakkety vs Xenial: diff -u "akonadi-backend-mysql_16.04.3-0ubuntu2_all.deb - mysql-global.conf" "akonadi-backend-mysql_15.12.3-0ubuntu6_all.deb - mysql-global.conf" --- "akonadi-backend-mysql_16.04.3-0ubuntu2_all.deb - mysql-global.conf" 2016-06-24 15:51:12.0 +0200 +++ "akonadi-backend-mysql_15.12.3-0ubuntu6_all.deb - mysql-global.conf" 2016-04-20 10:42:09.0 +0200 @@ -100,5 +100,14 @@ # We use InnoDB, so don't let MyISAM eat up memory key_buffer_size=16K +# KUBUNTU: +# Unset the export dir check as only the full mysql-server package creates it +secure_file_priv= + +# KUBUNTU: +# workaround for 5.7 being more strict with column types +# (reverts to 5.6 behavior) +sql_mode=NO_ENGINE_SUBSTITUTION + [client] default-character-set=utf8 Applying this patch fixes the bug. The "secure_file_priv" setting went missing is referenced in the package changelog: akonadi (4:15.12.3-0ubuntu5) xenial; urgency=medium * kubuntu_disable_secure_file_priv_check.diff: - Set secure_file_priv to empty as that directory is not set in a default kubuntu install -- Philip MuškovacMon, 18 Apr 2016 15:24:43 +0200 Marco Gamberoni To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/akonadi/+bug/1633855/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1637236] Re: New upstream microreleases 9.1.24, 9.3.15, 9.5.5
** Changed in: postgresql-9.5 (Ubuntu Xenial) Status: New => In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to postgresql-9.1 in Ubuntu. https://bugs.launchpad.net/bugs/1637236 Title: New upstream microreleases 9.1.24, 9.3.15, 9.5.5 Status in postgresql-9.1 package in Ubuntu: Invalid Status in postgresql-9.3 package in Ubuntu: Invalid Status in postgresql-9.5 package in Ubuntu: Fix Committed Status in postgresql-9.1 source package in Precise: New Status in postgresql-9.1 source package in Trusty: New Status in postgresql-9.3 source package in Trusty: New Status in postgresql-9.5 source package in Xenial: In Progress Status in postgresql-9.5 source package in Yakkety: New Status in postgresql-9.5 source package in Zesty: Fix Committed Bug description: https://www.postgresql.org/about/news/1712/ As per the standing micro-release exception these should land in stable Ubuntu releases. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postgresql-9.1/+bug/1637236/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1631241] Re: Name resolution stops working after resume from suspend
Hi Martin - not sure if this is related. But this bug report is also indicating problems with dnsmasq when establishing a VPN connection... https://bugs.launchpad.net/ubuntu/+source/openvpn-systemd- resolved/+bug/1636395 Thanks for any help with this. -- 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/1631241 Title: Name resolution stops working after resume from suspend Status in network-manager package in Ubuntu: Confirmed Bug description: After upgrading to Yakkety, when my Ubuntu GNOME laptop resumes from suspend DNS resolution stops working. After resuming, systemd-resolved is running and libnss-resolve is installed, but /etc/resolv.conf contains 127.0.1.1 as the the only name server. The dnsmasq-base package is installed since it is pulled in by both network-manager and lxc1, and both NM and libvirt have spawned instances of dnsmasq: > 1155 pts/2S+ 0:00 grep dnsmasq > 2724 ?S 0:00 dnsmasq -u lxc-dnsmasq --strict-order --bind-interfaces --pid-file=/run/lxc/dnsmasq.pid --listen-address 10.0.3.1 --dhcp-range 10.0.3.2,10.0.3.254 --dhcp-lease-max=253 --dhcp-no-override --except-interface=lo --interface=lxcbr0 --dhcp-leasefile=/var/lib/misc/dnsmasq.lxcbr0.leases --dhcp-authoritative > 2992 ?S 0:00 /usr/sbin/dnsmasq --conf-file=/var/lib/libvirt/dnsmasq/default.conf --leasefile-ro --dhcp-script=/usr/lib/libvirt/libvirt_leaseshelper > 2993 ?S 0:00 /usr/sbin/dnsmasq --conf-file=/var/lib/libvirt/dnsmasq/default.conf --leasefile-ro --dhcp-script=/usr/lib/libvirt/libvirt_leaseshelper > 22879 ?S 0:00 /usr/sbin/dnsmasq --no-resolv --keep-in-foreground --no-hosts --bind-interfaces --pid-file=/var/run/NetworkManager/dnsmasq.pid --listen-address=127.0.1.1 --cache-size=0 --conf-file=/dev/null --proxy-dnssec --enable-dbus=org.freedesktop.NetworkManager.dnsmasq --conf-dir=/etc/NetworkManager/dnsmasq.d Let me know if you need any extra info. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: libnss-resolve 231-9git1 ProcVersionSignature: Ubuntu 4.8.0-17.19-generic 4.8.0-rc7 Uname: Linux 4.8.0-17-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Oct 7 13:52:40 2016 InstallationDate: Installed on 2015-07-22 (443 days ago) InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 (20150422) SourcePackage: systemd UpgradeStatus: Upgraded to yakkety on 2016-10-05 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1631241/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1635996] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1635996/+attachment/4768319/+files/Dependencies.txt -- 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/1635996 Title: Libreoffice temporarily hangs / freezes Ubuntu 16.10 Status in libreoffice package in Ubuntu: Incomplete Status in xserver-xorg-video-intel package in Ubuntu: Incomplete Bug description: Using LibreOffice-Writer and running of the IGP ( (Mesa DRI Intel(R) HD Graphics 530 (Skylake GT2) / Mesa 12.0.3 ) causes LibreOffice and the Ubuntu Desktop interface to become unresponsive every few minutes. This freezing will last for about five seconds before everything works again. When i keep typing while everything freezes the text will appear after the system becomes responsive again. This only happens when i use the Intel HD Graphics 530 IGP. When using the Nvidia Quadro M2000M GPU and it's Nvidia driver for the graphics everything is fine. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: libreoffice-writer 1:5.2.2-0ubuntu2 Uname: Linux 4.8.4-040804-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 Date: Sun Oct 23 19:13:44 2016 InstallationDate: Installed on 2016-03-17 (219 days ago) InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: libreoffice UpgradeStatus: Upgraded to yakkety on 2016-10-04 (19 days ago) --- ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: XFCE DistroRelease: Ubuntu 16.10 InstallationDate: Installed on 2016-03-17 (224 days ago) InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) Package: xserver-xorg-video-intel 2:2.99.917+git20160706-1ubuntu1 PackageArchitecture: amd64 Tags: yakkety Uname: Linux 4.8.4-040804-generic x86_64 UpgradeStatus: Upgraded to yakkety on 2016-10-04 (23 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True --- ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 DistroRelease: Ubuntu 16.10 InstallationDate: Installed on 2016-03-17 (224 days ago) InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) Package: xserver-xorg-video-intel 2:2.99.917+git20160706-1ubuntu1 [origin: unknown] PackageArchitecture: amd64 Tags: yakkety third-party-packages Uname: Linux 4.8.4-040804-generic x86_64 UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. UpgradeStatus: Upgraded to yakkety on 2016-10-04 (23 days ago) UserGroups: _MarkForUpload: True --- ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: XFCE DistroRelease: Ubuntu 16.10 InstallationDate: Installed on 2016-03-17 (224 days ago) InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) Package: xserver-xorg-video-intel 2:2.99.917+git20160706-1ubuntu1 [origin: unknown] PackageArchitecture: amd64 Tags: yakkety third-party-packages Uname: Linux 4.8.4-040804-generic x86_64 UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. UpgradeStatus: Upgraded to yakkety on 2016-10-04 (23 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True --- ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 DistroRelease: Ubuntu 16.10 InstallationDate: Installed on 2016-03-17 (224 days ago) InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) Package: xserver-xorg-video-intel 2:2.99.917+git20160706-1ubuntu1 [origin: unknown] PackageArchitecture: amd64 Tags: yakkety third-party-packages Uname: Linux 4.8.4-040804-generic x86_64 UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. UpgradeStatus: Upgraded to yakkety on 2016-10-04 (23 days ago) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1635996/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1635996] Re: Libreoffice temporarily hangs / freezes Ubuntu 16.10
apport information ** Attachment removed: "JournalErrors.txt" https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1635996/+attachment/4768314/+files/JournalErrors.txt ** Tags added: third-party-packages ** Description changed: Using LibreOffice-Writer and running of the IGP ( (Mesa DRI Intel(R) HD Graphics 530 (Skylake GT2) / Mesa 12.0.3 ) causes LibreOffice and the Ubuntu Desktop interface to become unresponsive every few minutes. This freezing will last for about five seconds before everything works again. When i keep typing while everything freezes the text will appear after the system becomes responsive again. This only happens when i use the Intel HD Graphics 530 IGP. When using the Nvidia Quadro M2000M GPU and it's Nvidia driver for the graphics everything is fine. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: libreoffice-writer 1:5.2.2-0ubuntu2 Uname: Linux 4.8.4-040804-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 Date: Sun Oct 23 19:13:44 2016 InstallationDate: Installed on 2016-03-17 (219 days ago) InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: libreoffice UpgradeStatus: Upgraded to yakkety on 2016-10-04 (19 days ago) --- ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: XFCE DistroRelease: Ubuntu 16.10 InstallationDate: Installed on 2016-03-17 (224 days ago) InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) Package: xserver-xorg-video-intel 2:2.99.917+git20160706-1ubuntu1 PackageArchitecture: amd64 Tags: yakkety Uname: Linux 4.8.4-040804-generic x86_64 UpgradeStatus: Upgraded to yakkety on 2016-10-04 (23 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True + --- + ApportVersion: 2.20.3-0ubuntu8 + Architecture: amd64 + DistroRelease: Ubuntu 16.10 + InstallationDate: Installed on 2016-03-17 (224 days ago) + InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) + Package: xserver-xorg-video-intel 2:2.99.917+git20160706-1ubuntu1 [origin: unknown] + PackageArchitecture: amd64 + Tags: yakkety third-party-packages + Uname: Linux 4.8.4-040804-generic x86_64 + UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. + UpgradeStatus: Upgraded to yakkety on 2016-10-04 (23 days ago) + UserGroups: + + _MarkForUpload: True ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1635996/+attachment/4768316/+files/Dependencies.txt -- 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/1635996 Title: Libreoffice temporarily hangs / freezes Ubuntu 16.10 Status in libreoffice package in Ubuntu: Incomplete Status in xserver-xorg-video-intel package in Ubuntu: Incomplete Bug description: Using LibreOffice-Writer and running of the IGP ( (Mesa DRI Intel(R) HD Graphics 530 (Skylake GT2) / Mesa 12.0.3 ) causes LibreOffice and the Ubuntu Desktop interface to become unresponsive every few minutes. This freezing will last for about five seconds before everything works again. When i keep typing while everything freezes the text will appear after the system becomes responsive again. This only happens when i use the Intel HD Graphics 530 IGP. When using the Nvidia Quadro M2000M GPU and it's Nvidia driver for the graphics everything is fine. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: libreoffice-writer 1:5.2.2-0ubuntu2 Uname: Linux 4.8.4-040804-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 Date: Sun Oct 23 19:13:44 2016 InstallationDate: Installed on 2016-03-17 (219 days ago) InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: libreoffice UpgradeStatus: Upgraded to yakkety on 2016-10-04 (19 days ago) --- ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: XFCE DistroRelease: Ubuntu 16.10 InstallationDate: Installed on 2016-03-17 (224 days ago) InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) Package: xserver-xorg-video-intel 2:2.99.917+git20160706-1ubuntu1 PackageArchitecture: amd64 Tags: yakkety Uname: Linux 4.8.4-040804-generic x86_64 UpgradeStatus: Upgraded to yakkety on 2016-10-04 (23 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True --- ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 DistroRelease: Ubuntu 16.10 InstallationDate: Installed on 2016-03-17 (224 days ago) InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) Package: xserver-xorg-video-intel 2:2.99.917+git20160706-1ubuntu1 [origin: unknown] PackageArchitecture: amd64 Tags: yakkety third-party-packages Uname: Linux 4.8.4-040804-generic x86_64
[Desktop-packages] [Bug 1635996] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1635996/+attachment/4768324/+files/ProcEnviron.txt -- 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/1635996 Title: Libreoffice temporarily hangs / freezes Ubuntu 16.10 Status in libreoffice package in Ubuntu: Incomplete Status in xserver-xorg-video-intel package in Ubuntu: Incomplete Bug description: Using LibreOffice-Writer and running of the IGP ( (Mesa DRI Intel(R) HD Graphics 530 (Skylake GT2) / Mesa 12.0.3 ) causes LibreOffice and the Ubuntu Desktop interface to become unresponsive every few minutes. This freezing will last for about five seconds before everything works again. When i keep typing while everything freezes the text will appear after the system becomes responsive again. This only happens when i use the Intel HD Graphics 530 IGP. When using the Nvidia Quadro M2000M GPU and it's Nvidia driver for the graphics everything is fine. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: libreoffice-writer 1:5.2.2-0ubuntu2 Uname: Linux 4.8.4-040804-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 Date: Sun Oct 23 19:13:44 2016 InstallationDate: Installed on 2016-03-17 (219 days ago) InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: libreoffice UpgradeStatus: Upgraded to yakkety on 2016-10-04 (19 days ago) --- ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: XFCE DistroRelease: Ubuntu 16.10 InstallationDate: Installed on 2016-03-17 (224 days ago) InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) Package: xserver-xorg-video-intel 2:2.99.917+git20160706-1ubuntu1 PackageArchitecture: amd64 Tags: yakkety Uname: Linux 4.8.4-040804-generic x86_64 UpgradeStatus: Upgraded to yakkety on 2016-10-04 (23 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True --- ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 DistroRelease: Ubuntu 16.10 InstallationDate: Installed on 2016-03-17 (224 days ago) InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) Package: xserver-xorg-video-intel 2:2.99.917+git20160706-1ubuntu1 [origin: unknown] PackageArchitecture: amd64 Tags: yakkety third-party-packages Uname: Linux 4.8.4-040804-generic x86_64 UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. UpgradeStatus: Upgraded to yakkety on 2016-10-04 (23 days ago) UserGroups: _MarkForUpload: True --- ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: XFCE DistroRelease: Ubuntu 16.10 InstallationDate: Installed on 2016-03-17 (224 days ago) InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) Package: xserver-xorg-video-intel 2:2.99.917+git20160706-1ubuntu1 [origin: unknown] PackageArchitecture: amd64 Tags: yakkety third-party-packages Uname: Linux 4.8.4-040804-generic x86_64 UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. UpgradeStatus: Upgraded to yakkety on 2016-10-04 (23 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True --- ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 DistroRelease: Ubuntu 16.10 InstallationDate: Installed on 2016-03-17 (224 days ago) InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) Package: xserver-xorg-video-intel 2:2.99.917+git20160706-1ubuntu1 [origin: unknown] PackageArchitecture: amd64 Tags: yakkety third-party-packages Uname: Linux 4.8.4-040804-generic x86_64 UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. UpgradeStatus: Upgraded to yakkety on 2016-10-04 (23 days ago) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1635996/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1635996] JournalErrors.txt
apport information ** Attachment added: "JournalErrors.txt" https://bugs.launchpad.net/bugs/1635996/+attachment/4768320/+files/JournalErrors.txt -- 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/1635996 Title: Libreoffice temporarily hangs / freezes Ubuntu 16.10 Status in libreoffice package in Ubuntu: Incomplete Status in xserver-xorg-video-intel package in Ubuntu: Incomplete Bug description: Using LibreOffice-Writer and running of the IGP ( (Mesa DRI Intel(R) HD Graphics 530 (Skylake GT2) / Mesa 12.0.3 ) causes LibreOffice and the Ubuntu Desktop interface to become unresponsive every few minutes. This freezing will last for about five seconds before everything works again. When i keep typing while everything freezes the text will appear after the system becomes responsive again. This only happens when i use the Intel HD Graphics 530 IGP. When using the Nvidia Quadro M2000M GPU and it's Nvidia driver for the graphics everything is fine. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: libreoffice-writer 1:5.2.2-0ubuntu2 Uname: Linux 4.8.4-040804-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 Date: Sun Oct 23 19:13:44 2016 InstallationDate: Installed on 2016-03-17 (219 days ago) InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: libreoffice UpgradeStatus: Upgraded to yakkety on 2016-10-04 (19 days ago) --- ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: XFCE DistroRelease: Ubuntu 16.10 InstallationDate: Installed on 2016-03-17 (224 days ago) InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) Package: xserver-xorg-video-intel 2:2.99.917+git20160706-1ubuntu1 PackageArchitecture: amd64 Tags: yakkety Uname: Linux 4.8.4-040804-generic x86_64 UpgradeStatus: Upgraded to yakkety on 2016-10-04 (23 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True --- ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 DistroRelease: Ubuntu 16.10 InstallationDate: Installed on 2016-03-17 (224 days ago) InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) Package: xserver-xorg-video-intel 2:2.99.917+git20160706-1ubuntu1 [origin: unknown] PackageArchitecture: amd64 Tags: yakkety third-party-packages Uname: Linux 4.8.4-040804-generic x86_64 UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. UpgradeStatus: Upgraded to yakkety on 2016-10-04 (23 days ago) UserGroups: _MarkForUpload: True --- ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: XFCE DistroRelease: Ubuntu 16.10 InstallationDate: Installed on 2016-03-17 (224 days ago) InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) Package: xserver-xorg-video-intel 2:2.99.917+git20160706-1ubuntu1 [origin: unknown] PackageArchitecture: amd64 Tags: yakkety third-party-packages Uname: Linux 4.8.4-040804-generic x86_64 UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. UpgradeStatus: Upgraded to yakkety on 2016-10-04 (23 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True --- ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 DistroRelease: Ubuntu 16.10 InstallationDate: Installed on 2016-03-17 (224 days ago) InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) Package: xserver-xorg-video-intel 2:2.99.917+git20160706-1ubuntu1 [origin: unknown] PackageArchitecture: amd64 Tags: yakkety third-party-packages Uname: Linux 4.8.4-040804-generic x86_64 UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. UpgradeStatus: Upgraded to yakkety on 2016-10-04 (23 days ago) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1635996/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1635996] JournalErrors.txt
apport information ** Attachment added: "JournalErrors.txt" https://bugs.launchpad.net/bugs/1635996/+attachment/4768323/+files/JournalErrors.txt -- 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/1635996 Title: Libreoffice temporarily hangs / freezes Ubuntu 16.10 Status in libreoffice package in Ubuntu: Incomplete Status in xserver-xorg-video-intel package in Ubuntu: Incomplete Bug description: Using LibreOffice-Writer and running of the IGP ( (Mesa DRI Intel(R) HD Graphics 530 (Skylake GT2) / Mesa 12.0.3 ) causes LibreOffice and the Ubuntu Desktop interface to become unresponsive every few minutes. This freezing will last for about five seconds before everything works again. When i keep typing while everything freezes the text will appear after the system becomes responsive again. This only happens when i use the Intel HD Graphics 530 IGP. When using the Nvidia Quadro M2000M GPU and it's Nvidia driver for the graphics everything is fine. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: libreoffice-writer 1:5.2.2-0ubuntu2 Uname: Linux 4.8.4-040804-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 Date: Sun Oct 23 19:13:44 2016 InstallationDate: Installed on 2016-03-17 (219 days ago) InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: libreoffice UpgradeStatus: Upgraded to yakkety on 2016-10-04 (19 days ago) --- ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: XFCE DistroRelease: Ubuntu 16.10 InstallationDate: Installed on 2016-03-17 (224 days ago) InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) Package: xserver-xorg-video-intel 2:2.99.917+git20160706-1ubuntu1 PackageArchitecture: amd64 Tags: yakkety Uname: Linux 4.8.4-040804-generic x86_64 UpgradeStatus: Upgraded to yakkety on 2016-10-04 (23 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True --- ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 DistroRelease: Ubuntu 16.10 InstallationDate: Installed on 2016-03-17 (224 days ago) InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) Package: xserver-xorg-video-intel 2:2.99.917+git20160706-1ubuntu1 [origin: unknown] PackageArchitecture: amd64 Tags: yakkety third-party-packages Uname: Linux 4.8.4-040804-generic x86_64 UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. UpgradeStatus: Upgraded to yakkety on 2016-10-04 (23 days ago) UserGroups: _MarkForUpload: True --- ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: XFCE DistroRelease: Ubuntu 16.10 InstallationDate: Installed on 2016-03-17 (224 days ago) InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) Package: xserver-xorg-video-intel 2:2.99.917+git20160706-1ubuntu1 [origin: unknown] PackageArchitecture: amd64 Tags: yakkety third-party-packages Uname: Linux 4.8.4-040804-generic x86_64 UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. UpgradeStatus: Upgraded to yakkety on 2016-10-04 (23 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True --- ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 DistroRelease: Ubuntu 16.10 InstallationDate: Installed on 2016-03-17 (224 days ago) InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) Package: xserver-xorg-video-intel 2:2.99.917+git20160706-1ubuntu1 [origin: unknown] PackageArchitecture: amd64 Tags: yakkety third-party-packages Uname: Linux 4.8.4-040804-generic x86_64 UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. UpgradeStatus: Upgraded to yakkety on 2016-10-04 (23 days ago) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1635996/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1635996] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1635996/+attachment/4768318/+files/ProcEnviron.txt ** Attachment removed: "JournalErrors.txt" https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1635996/+attachment/4768317/+files/JournalErrors.txt ** Description changed: Using LibreOffice-Writer and running of the IGP ( (Mesa DRI Intel(R) HD Graphics 530 (Skylake GT2) / Mesa 12.0.3 ) causes LibreOffice and the Ubuntu Desktop interface to become unresponsive every few minutes. This freezing will last for about five seconds before everything works again. When i keep typing while everything freezes the text will appear after the system becomes responsive again. This only happens when i use the Intel HD Graphics 530 IGP. When using the Nvidia Quadro M2000M GPU and it's Nvidia driver for the graphics everything is fine. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: libreoffice-writer 1:5.2.2-0ubuntu2 Uname: Linux 4.8.4-040804-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 Date: Sun Oct 23 19:13:44 2016 InstallationDate: Installed on 2016-03-17 (219 days ago) InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: libreoffice UpgradeStatus: Upgraded to yakkety on 2016-10-04 (19 days ago) --- ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: XFCE DistroRelease: Ubuntu 16.10 InstallationDate: Installed on 2016-03-17 (224 days ago) InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) Package: xserver-xorg-video-intel 2:2.99.917+git20160706-1ubuntu1 PackageArchitecture: amd64 Tags: yakkety Uname: Linux 4.8.4-040804-generic x86_64 UpgradeStatus: Upgraded to yakkety on 2016-10-04 (23 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True --- ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 DistroRelease: Ubuntu 16.10 InstallationDate: Installed on 2016-03-17 (224 days ago) InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) Package: xserver-xorg-video-intel 2:2.99.917+git20160706-1ubuntu1 [origin: unknown] PackageArchitecture: amd64 Tags: yakkety third-party-packages Uname: Linux 4.8.4-040804-generic x86_64 UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. UpgradeStatus: Upgraded to yakkety on 2016-10-04 (23 days ago) UserGroups: _MarkForUpload: True + --- + ApportVersion: 2.20.3-0ubuntu8 + Architecture: amd64 + CurrentDesktop: XFCE + DistroRelease: Ubuntu 16.10 + InstallationDate: Installed on 2016-03-17 (224 days ago) + InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) + Package: xserver-xorg-video-intel 2:2.99.917+git20160706-1ubuntu1 [origin: unknown] + PackageArchitecture: amd64 + Tags: yakkety third-party-packages + Uname: Linux 4.8.4-040804-generic x86_64 + UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. + UpgradeStatus: Upgraded to yakkety on 2016-10-04 (23 days ago) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + _MarkForUpload: True -- 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/1635996 Title: Libreoffice temporarily hangs / freezes Ubuntu 16.10 Status in libreoffice package in Ubuntu: Incomplete Status in xserver-xorg-video-intel package in Ubuntu: Incomplete Bug description: Using LibreOffice-Writer and running of the IGP ( (Mesa DRI Intel(R) HD Graphics 530 (Skylake GT2) / Mesa 12.0.3 ) causes LibreOffice and the Ubuntu Desktop interface to become unresponsive every few minutes. This freezing will last for about five seconds before everything works again. When i keep typing while everything freezes the text will appear after the system becomes responsive again. This only happens when i use the Intel HD Graphics 530 IGP. When using the Nvidia Quadro M2000M GPU and it's Nvidia driver for the graphics everything is fine. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: libreoffice-writer 1:5.2.2-0ubuntu2 Uname: Linux 4.8.4-040804-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 Date: Sun Oct 23 19:13:44 2016 InstallationDate: Installed on 2016-03-17 (219 days ago) InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: libreoffice UpgradeStatus: Upgraded to yakkety on 2016-10-04 (19 days ago) --- ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: XFCE DistroRelease: Ubuntu 16.10 InstallationDate: Installed on 2016-03-17 (224 days ago) InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) Package: xserver-xorg-video-intel
[Desktop-packages] [Bug 1635996] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1635996/+attachment/4768322/+files/Dependencies.txt -- 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/1635996 Title: Libreoffice temporarily hangs / freezes Ubuntu 16.10 Status in libreoffice package in Ubuntu: Incomplete Status in xserver-xorg-video-intel package in Ubuntu: Incomplete Bug description: Using LibreOffice-Writer and running of the IGP ( (Mesa DRI Intel(R) HD Graphics 530 (Skylake GT2) / Mesa 12.0.3 ) causes LibreOffice and the Ubuntu Desktop interface to become unresponsive every few minutes. This freezing will last for about five seconds before everything works again. When i keep typing while everything freezes the text will appear after the system becomes responsive again. This only happens when i use the Intel HD Graphics 530 IGP. When using the Nvidia Quadro M2000M GPU and it's Nvidia driver for the graphics everything is fine. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: libreoffice-writer 1:5.2.2-0ubuntu2 Uname: Linux 4.8.4-040804-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 Date: Sun Oct 23 19:13:44 2016 InstallationDate: Installed on 2016-03-17 (219 days ago) InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: libreoffice UpgradeStatus: Upgraded to yakkety on 2016-10-04 (19 days ago) --- ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: XFCE DistroRelease: Ubuntu 16.10 InstallationDate: Installed on 2016-03-17 (224 days ago) InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) Package: xserver-xorg-video-intel 2:2.99.917+git20160706-1ubuntu1 PackageArchitecture: amd64 Tags: yakkety Uname: Linux 4.8.4-040804-generic x86_64 UpgradeStatus: Upgraded to yakkety on 2016-10-04 (23 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True --- ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 DistroRelease: Ubuntu 16.10 InstallationDate: Installed on 2016-03-17 (224 days ago) InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) Package: xserver-xorg-video-intel 2:2.99.917+git20160706-1ubuntu1 [origin: unknown] PackageArchitecture: amd64 Tags: yakkety third-party-packages Uname: Linux 4.8.4-040804-generic x86_64 UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. UpgradeStatus: Upgraded to yakkety on 2016-10-04 (23 days ago) UserGroups: _MarkForUpload: True --- ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: XFCE DistroRelease: Ubuntu 16.10 InstallationDate: Installed on 2016-03-17 (224 days ago) InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) Package: xserver-xorg-video-intel 2:2.99.917+git20160706-1ubuntu1 [origin: unknown] PackageArchitecture: amd64 Tags: yakkety third-party-packages Uname: Linux 4.8.4-040804-generic x86_64 UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. UpgradeStatus: Upgraded to yakkety on 2016-10-04 (23 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True --- ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 DistroRelease: Ubuntu 16.10 InstallationDate: Installed on 2016-03-17 (224 days ago) InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) Package: xserver-xorg-video-intel 2:2.99.917+git20160706-1ubuntu1 [origin: unknown] PackageArchitecture: amd64 Tags: yakkety third-party-packages Uname: Linux 4.8.4-040804-generic x86_64 UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. UpgradeStatus: Upgraded to yakkety on 2016-10-04 (23 days ago) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1635996/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1635996] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1635996/+attachment/4768321/+files/ProcEnviron.txt ** Attachment removed: "JournalErrors.txt" https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1635996/+attachment/4768320/+files/JournalErrors.txt ** Description changed: Using LibreOffice-Writer and running of the IGP ( (Mesa DRI Intel(R) HD Graphics 530 (Skylake GT2) / Mesa 12.0.3 ) causes LibreOffice and the Ubuntu Desktop interface to become unresponsive every few minutes. This freezing will last for about five seconds before everything works again. When i keep typing while everything freezes the text will appear after the system becomes responsive again. This only happens when i use the Intel HD Graphics 530 IGP. When using the Nvidia Quadro M2000M GPU and it's Nvidia driver for the graphics everything is fine. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: libreoffice-writer 1:5.2.2-0ubuntu2 Uname: Linux 4.8.4-040804-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 Date: Sun Oct 23 19:13:44 2016 InstallationDate: Installed on 2016-03-17 (219 days ago) InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: libreoffice UpgradeStatus: Upgraded to yakkety on 2016-10-04 (19 days ago) --- ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: XFCE DistroRelease: Ubuntu 16.10 InstallationDate: Installed on 2016-03-17 (224 days ago) InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) Package: xserver-xorg-video-intel 2:2.99.917+git20160706-1ubuntu1 PackageArchitecture: amd64 Tags: yakkety Uname: Linux 4.8.4-040804-generic x86_64 UpgradeStatus: Upgraded to yakkety on 2016-10-04 (23 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True --- ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 DistroRelease: Ubuntu 16.10 InstallationDate: Installed on 2016-03-17 (224 days ago) InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) Package: xserver-xorg-video-intel 2:2.99.917+git20160706-1ubuntu1 [origin: unknown] PackageArchitecture: amd64 Tags: yakkety third-party-packages Uname: Linux 4.8.4-040804-generic x86_64 UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. UpgradeStatus: Upgraded to yakkety on 2016-10-04 (23 days ago) UserGroups: _MarkForUpload: True --- ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: XFCE DistroRelease: Ubuntu 16.10 InstallationDate: Installed on 2016-03-17 (224 days ago) InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) Package: xserver-xorg-video-intel 2:2.99.917+git20160706-1ubuntu1 [origin: unknown] PackageArchitecture: amd64 Tags: yakkety third-party-packages Uname: Linux 4.8.4-040804-generic x86_64 UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. UpgradeStatus: Upgraded to yakkety on 2016-10-04 (23 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True + --- + ApportVersion: 2.20.3-0ubuntu8 + Architecture: amd64 + DistroRelease: Ubuntu 16.10 + InstallationDate: Installed on 2016-03-17 (224 days ago) + InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) + Package: xserver-xorg-video-intel 2:2.99.917+git20160706-1ubuntu1 [origin: unknown] + PackageArchitecture: amd64 + Tags: yakkety third-party-packages + Uname: Linux 4.8.4-040804-generic x86_64 + UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. + UpgradeStatus: Upgraded to yakkety on 2016-10-04 (23 days ago) + UserGroups: + + _MarkForUpload: True -- 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/1635996 Title: Libreoffice temporarily hangs / freezes Ubuntu 16.10 Status in libreoffice package in Ubuntu: Incomplete Status in xserver-xorg-video-intel package in Ubuntu: Incomplete Bug description: Using LibreOffice-Writer and running of the IGP ( (Mesa DRI Intel(R) HD Graphics 530 (Skylake GT2) / Mesa 12.0.3 ) causes LibreOffice and the Ubuntu Desktop interface to become unresponsive every few minutes. This freezing will last for about five seconds before everything works again. When i keep typing while everything freezes the text will appear after the system becomes responsive again. This only happens when i use the Intel HD Graphics 530 IGP. When using the Nvidia Quadro M2000M GPU and it's Nvidia driver for the graphics everything is fine. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: libreoffice-writer 1:5.2.2-0ubuntu2 Uname: Linux
[Desktop-packages] [Bug 1635996] JournalErrors.txt
apport information ** Attachment added: "JournalErrors.txt" https://bugs.launchpad.net/bugs/1635996/+attachment/4768317/+files/JournalErrors.txt -- 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/1635996 Title: Libreoffice temporarily hangs / freezes Ubuntu 16.10 Status in libreoffice package in Ubuntu: Incomplete Status in xserver-xorg-video-intel package in Ubuntu: Incomplete Bug description: Using LibreOffice-Writer and running of the IGP ( (Mesa DRI Intel(R) HD Graphics 530 (Skylake GT2) / Mesa 12.0.3 ) causes LibreOffice and the Ubuntu Desktop interface to become unresponsive every few minutes. This freezing will last for about five seconds before everything works again. When i keep typing while everything freezes the text will appear after the system becomes responsive again. This only happens when i use the Intel HD Graphics 530 IGP. When using the Nvidia Quadro M2000M GPU and it's Nvidia driver for the graphics everything is fine. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: libreoffice-writer 1:5.2.2-0ubuntu2 Uname: Linux 4.8.4-040804-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 Date: Sun Oct 23 19:13:44 2016 InstallationDate: Installed on 2016-03-17 (219 days ago) InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: libreoffice UpgradeStatus: Upgraded to yakkety on 2016-10-04 (19 days ago) --- ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: XFCE DistroRelease: Ubuntu 16.10 InstallationDate: Installed on 2016-03-17 (224 days ago) InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) Package: xserver-xorg-video-intel 2:2.99.917+git20160706-1ubuntu1 PackageArchitecture: amd64 Tags: yakkety Uname: Linux 4.8.4-040804-generic x86_64 UpgradeStatus: Upgraded to yakkety on 2016-10-04 (23 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True --- ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 DistroRelease: Ubuntu 16.10 InstallationDate: Installed on 2016-03-17 (224 days ago) InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) Package: xserver-xorg-video-intel 2:2.99.917+git20160706-1ubuntu1 [origin: unknown] PackageArchitecture: amd64 Tags: yakkety third-party-packages Uname: Linux 4.8.4-040804-generic x86_64 UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. UpgradeStatus: Upgraded to yakkety on 2016-10-04 (23 days ago) UserGroups: _MarkForUpload: True --- ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: XFCE DistroRelease: Ubuntu 16.10 InstallationDate: Installed on 2016-03-17 (224 days ago) InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) Package: xserver-xorg-video-intel 2:2.99.917+git20160706-1ubuntu1 [origin: unknown] PackageArchitecture: amd64 Tags: yakkety third-party-packages Uname: Linux 4.8.4-040804-generic x86_64 UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. UpgradeStatus: Upgraded to yakkety on 2016-10-04 (23 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True --- ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 DistroRelease: Ubuntu 16.10 InstallationDate: Installed on 2016-03-17 (224 days ago) InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) Package: xserver-xorg-video-intel 2:2.99.917+git20160706-1ubuntu1 [origin: unknown] PackageArchitecture: amd64 Tags: yakkety third-party-packages Uname: Linux 4.8.4-040804-generic x86_64 UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. UpgradeStatus: Upgraded to yakkety on 2016-10-04 (23 days ago) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1635996/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1635996] Re: Libreoffice temporarily hangs / freezes Ubuntu 16.10
apport information ** Tags added: apport-collected ** Description changed: Using LibreOffice-Writer and running of the IGP ( (Mesa DRI Intel(R) HD Graphics 530 (Skylake GT2) / Mesa 12.0.3 ) causes LibreOffice and the Ubuntu Desktop interface to become unresponsive every few minutes. This freezing will last for about five seconds before everything works again. When i keep typing while everything freezes the text will appear after the system becomes responsive again. This only happens when i use the Intel HD Graphics 530 IGP. When using the Nvidia Quadro M2000M GPU and it's Nvidia driver for the graphics everything is fine. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: libreoffice-writer 1:5.2.2-0ubuntu2 Uname: Linux 4.8.4-040804-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 Date: Sun Oct 23 19:13:44 2016 InstallationDate: Installed on 2016-03-17 (219 days ago) InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: libreoffice UpgradeStatus: Upgraded to yakkety on 2016-10-04 (19 days ago) + --- + ApportVersion: 2.20.3-0ubuntu8 + Architecture: amd64 + CurrentDesktop: XFCE + DistroRelease: Ubuntu 16.10 + InstallationDate: Installed on 2016-03-17 (224 days ago) + InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) + Package: xserver-xorg-video-intel 2:2.99.917+git20160706-1ubuntu1 + PackageArchitecture: amd64 + Tags: yakkety + Uname: Linux 4.8.4-040804-generic x86_64 + UpgradeStatus: Upgraded to yakkety on 2016-10-04 (23 days ago) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + _MarkForUpload: True ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1635996/+attachment/4768313/+files/Dependencies.txt -- 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/1635996 Title: Libreoffice temporarily hangs / freezes Ubuntu 16.10 Status in libreoffice package in Ubuntu: Incomplete Status in xserver-xorg-video-intel package in Ubuntu: Incomplete Bug description: Using LibreOffice-Writer and running of the IGP ( (Mesa DRI Intel(R) HD Graphics 530 (Skylake GT2) / Mesa 12.0.3 ) causes LibreOffice and the Ubuntu Desktop interface to become unresponsive every few minutes. This freezing will last for about five seconds before everything works again. When i keep typing while everything freezes the text will appear after the system becomes responsive again. This only happens when i use the Intel HD Graphics 530 IGP. When using the Nvidia Quadro M2000M GPU and it's Nvidia driver for the graphics everything is fine. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: libreoffice-writer 1:5.2.2-0ubuntu2 Uname: Linux 4.8.4-040804-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 Date: Sun Oct 23 19:13:44 2016 InstallationDate: Installed on 2016-03-17 (219 days ago) InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: libreoffice UpgradeStatus: Upgraded to yakkety on 2016-10-04 (19 days ago) --- ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: XFCE DistroRelease: Ubuntu 16.10 InstallationDate: Installed on 2016-03-17 (224 days ago) InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) Package: xserver-xorg-video-intel 2:2.99.917+git20160706-1ubuntu1 PackageArchitecture: amd64 Tags: yakkety Uname: Linux 4.8.4-040804-generic x86_64 UpgradeStatus: Upgraded to yakkety on 2016-10-04 (23 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True --- ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 DistroRelease: Ubuntu 16.10 InstallationDate: Installed on 2016-03-17 (224 days ago) InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) Package: xserver-xorg-video-intel 2:2.99.917+git20160706-1ubuntu1 [origin: unknown] PackageArchitecture: amd64 Tags: yakkety third-party-packages Uname: Linux 4.8.4-040804-generic x86_64 UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. UpgradeStatus: Upgraded to yakkety on 2016-10-04 (23 days ago) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1635996/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1635996] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1635996/+attachment/4768315/+files/ProcEnviron.txt -- 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/1635996 Title: Libreoffice temporarily hangs / freezes Ubuntu 16.10 Status in libreoffice package in Ubuntu: Incomplete Status in xserver-xorg-video-intel package in Ubuntu: Incomplete Bug description: Using LibreOffice-Writer and running of the IGP ( (Mesa DRI Intel(R) HD Graphics 530 (Skylake GT2) / Mesa 12.0.3 ) causes LibreOffice and the Ubuntu Desktop interface to become unresponsive every few minutes. This freezing will last for about five seconds before everything works again. When i keep typing while everything freezes the text will appear after the system becomes responsive again. This only happens when i use the Intel HD Graphics 530 IGP. When using the Nvidia Quadro M2000M GPU and it's Nvidia driver for the graphics everything is fine. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: libreoffice-writer 1:5.2.2-0ubuntu2 Uname: Linux 4.8.4-040804-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 Date: Sun Oct 23 19:13:44 2016 InstallationDate: Installed on 2016-03-17 (219 days ago) InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: libreoffice UpgradeStatus: Upgraded to yakkety on 2016-10-04 (19 days ago) --- ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: XFCE DistroRelease: Ubuntu 16.10 InstallationDate: Installed on 2016-03-17 (224 days ago) InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) Package: xserver-xorg-video-intel 2:2.99.917+git20160706-1ubuntu1 PackageArchitecture: amd64 Tags: yakkety Uname: Linux 4.8.4-040804-generic x86_64 UpgradeStatus: Upgraded to yakkety on 2016-10-04 (23 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True --- ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 DistroRelease: Ubuntu 16.10 InstallationDate: Installed on 2016-03-17 (224 days ago) InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) Package: xserver-xorg-video-intel 2:2.99.917+git20160706-1ubuntu1 [origin: unknown] PackageArchitecture: amd64 Tags: yakkety third-party-packages Uname: Linux 4.8.4-040804-generic x86_64 UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. UpgradeStatus: Upgraded to yakkety on 2016-10-04 (23 days ago) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1635996/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1635996] JournalErrors.txt
apport information ** Attachment added: "JournalErrors.txt" https://bugs.launchpad.net/bugs/1635996/+attachment/4768314/+files/JournalErrors.txt -- 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/1635996 Title: Libreoffice temporarily hangs / freezes Ubuntu 16.10 Status in libreoffice package in Ubuntu: Incomplete Status in xserver-xorg-video-intel package in Ubuntu: Incomplete Bug description: Using LibreOffice-Writer and running of the IGP ( (Mesa DRI Intel(R) HD Graphics 530 (Skylake GT2) / Mesa 12.0.3 ) causes LibreOffice and the Ubuntu Desktop interface to become unresponsive every few minutes. This freezing will last for about five seconds before everything works again. When i keep typing while everything freezes the text will appear after the system becomes responsive again. This only happens when i use the Intel HD Graphics 530 IGP. When using the Nvidia Quadro M2000M GPU and it's Nvidia driver for the graphics everything is fine. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: libreoffice-writer 1:5.2.2-0ubuntu2 Uname: Linux 4.8.4-040804-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 Date: Sun Oct 23 19:13:44 2016 InstallationDate: Installed on 2016-03-17 (219 days ago) InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: libreoffice UpgradeStatus: Upgraded to yakkety on 2016-10-04 (19 days ago) --- ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: XFCE DistroRelease: Ubuntu 16.10 InstallationDate: Installed on 2016-03-17 (224 days ago) InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) Package: xserver-xorg-video-intel 2:2.99.917+git20160706-1ubuntu1 PackageArchitecture: amd64 Tags: yakkety Uname: Linux 4.8.4-040804-generic x86_64 UpgradeStatus: Upgraded to yakkety on 2016-10-04 (23 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True --- ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 DistroRelease: Ubuntu 16.10 InstallationDate: Installed on 2016-03-17 (224 days ago) InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) Package: xserver-xorg-video-intel 2:2.99.917+git20160706-1ubuntu1 [origin: unknown] PackageArchitecture: amd64 Tags: yakkety third-party-packages Uname: Linux 4.8.4-040804-generic x86_64 UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. UpgradeStatus: Upgraded to yakkety on 2016-10-04 (23 days ago) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1635996/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1637199] Re: File Open/Saveas dialog boxes in Mozilla Firefox do not show network shared folders.
** Package changed: ubuntu => firefox (Ubuntu) ** Tags added: xenial -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1637199 Title: File Open/Saveas dialog boxes in Mozilla Firefox do not show network shared folders. Status in firefox package in Ubuntu: New Bug description: When trying to open or save a file in Mozilla Firefox, only the local folders are displayed in the dialog box. It is necessary that files can also be saved and loaded from network shares. Mozilla Firefox version 49.0 Ubuntu 16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1637199/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 877279] Re: EOG - Image viewer hangs system when opening large image file
Mine will open large graphics zoomed out. When I try to zoom in on them, however, that is when it jams on me. And it really jams. Sometimes I have to unplug the computer just to clear it. This seems to be a fairly new problem on my computer. I used Image viewer for ages with no problem. I'm pretty sure some stupid update is responsible. I guess I will have to make Gimp the default view. What a hassle though. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to eog in Ubuntu. https://bugs.launchpad.net/bugs/877279 Title: EOG - Image viewer hangs system when opening large image file Status in eog package in Ubuntu: Confirmed Bug description: Since upgrade to 11.10, opening large jpg image files causes system to hang. Hard reset required. Happy to supply further information if you let me know what you need. ~ $ apt-cache policy eog eog: Installed: 3.2.0-0ubuntu1 Candidate: 3.2.0-0ubuntu1 Version table: *** 3.2.0-0ubuntu1 0 500 http://au.archive.ubuntu.com/ubuntu/ oneiric/main i386 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: eog 3.2.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4 Uname: Linux 3.0.0-12-generic i686 ApportVersion: 1.23-0ubuntu3 Architecture: i386 Date: Tue Oct 18 20:50:55 2011 EcryptfsInUse: Yes ExecutablePath: /usr/bin/eog InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429) ProcEnviron: PATH=(custom, user) LANG=en_AU.UTF-8 SHELL=/bin/bash SourcePackage: eog UpgradeStatus: Upgraded to oneiric on 2011-10-14 (4 days ago) XsessionErrors: (nautilus:1952): Gtk-CRITICAL **: gtk_action_set_visible: assertion `GTK_IS_ACTION (action)' failed (nautilus:1952): Gtk-CRITICAL **: gtk_action_set_visible: assertion `GTK_IS_ACTION (action)' failed (gnome-shell:1923): Clutter-WARNING **: The actor 'uiGroup' is currently inside an allocation cycle; calling clutter_actor_queue_relayout() is not recommended (gnome-shell:1923): Clutter-WARNING **: The actor 'uiGroup' is currently inside an allocation cycle; calling clutter_actor_queue_relayout() is not recommended To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eog/+bug/877279/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1637199] [NEW] File Open/Saveas dialog boxes in Mozilla Firefox do not show network shared folders.
You have been subscribed to a public bug: When trying to open or save a file in Mozilla Firefox, only the local folders are displayed in the dialog box. It is necessary that files can also be saved and loaded from network shares. Mozilla Firefox version 49.0 Ubuntu 16.04 ** Affects: firefox (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- File Open/Saveas dialog boxes in Mozilla Firefox do not show network shared folders. https://bugs.launchpad.net/bugs/1637199 You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1626935] Re: [yakkety] desktop is black and/or flickering after plugging in a second monitor
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: mesa (Ubuntu Yakkety) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1626935 Title: [yakkety] desktop is black and/or flickering after plugging in a second monitor Status in compiz package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in nautilus package in Ubuntu: Fix Committed Status in compiz source package in Yakkety: Confirmed Status in mesa source package in Yakkety: Confirmed Status in nautilus source package in Yakkety: Fix Committed Bug description: [ Description ] Nautilus's wallpaper drawing doesn't respond to changes in monitor configuration. Instead of your wallpaper you see black. [ Fix ] Inside nautilus, the wallpaper widget connects to GTK's "monitors- changed" signal when it is constructed. It does this only once the widget is realized - a "realized" signal handler connects to "monitors-changed". In Yakkety, the "realized" signal handler is connected after the widget is already realized, meaning that the signal handler isn't called and we don't connect to the "monitors- changed" signal. The proposed fix remedies this by checking if we are realized and explicitly calling the signal handler if so. [ QA ] Have multiple monitors. Have only one of them connected. Log in. Plug in one monitor. If it's autoactivated, check you see your background on both monitors. If not, activate it ("Displays") and do the same. [ Regression potential ] I'm not sure why or where the order changed to make the widget be realized earlier, if it matters or if this was always buggy and we got lucky. I would guess a refactoring in Nautilus itself, and so the proposed fix is safe, but watch out for other weirdness. [ Original description ] Using 16.04 daily image: 20160919(downloading date) With testing package for 4.8 kernel: ppa:canonical-kernel-team/unstable Graphic chips: 00:02.0 VGA compatible controller [0300]: Intel Corporation HD Graphics 530 [8086:191b] (rev 06) 01:00.0 3D controller [0302]: NVIDIA Corporation GM107M [GeForce GTX 960M] [10de:139b] (rev ff) Desktop wallpaper on extended display shows black background only, and the hdmi detection is very unstable. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.8.0-14.15-generic 4.8.0-rc7 Uname: Linux 4.8.0-14-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.3-0ubuntu7 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: Fri Sep 23 05:30:30 2016 DistUpgraded: Fresh install DistroCodename: yakkety DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 530 [1028:06e4] InstallationDate: Installed on 2016-09-20 (3 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160919) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f3:21d5 Elan Microelectronics Corp. Bus 001 Device 002: ID 0a5c:6410 Broadcom Corp. Bus 001 Device 004: ID 0c45:6713 Microdia Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 15 9550 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-14-generic.efi.signed root=UUID=d16ac6eb-1b3e-4aa5-813b-57b5c7ef165a ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/07/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.02.00 dmi.board.name: 0N7TVV dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA01:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 15 9550 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1 version.xserver-xorg-video-intel:
[Desktop-packages] [Bug 1626935] Re: [yakkety] desktop is black and/or flickering after plugging in a second monitor
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: compiz (Ubuntu Yakkety) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1626935 Title: [yakkety] desktop is black and/or flickering after plugging in a second monitor Status in compiz package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in nautilus package in Ubuntu: Fix Committed Status in compiz source package in Yakkety: Confirmed Status in mesa source package in Yakkety: Confirmed Status in nautilus source package in Yakkety: Fix Committed Bug description: [ Description ] Nautilus's wallpaper drawing doesn't respond to changes in monitor configuration. Instead of your wallpaper you see black. [ Fix ] Inside nautilus, the wallpaper widget connects to GTK's "monitors- changed" signal when it is constructed. It does this only once the widget is realized - a "realized" signal handler connects to "monitors-changed". In Yakkety, the "realized" signal handler is connected after the widget is already realized, meaning that the signal handler isn't called and we don't connect to the "monitors- changed" signal. The proposed fix remedies this by checking if we are realized and explicitly calling the signal handler if so. [ QA ] Have multiple monitors. Have only one of them connected. Log in. Plug in one monitor. If it's autoactivated, check you see your background on both monitors. If not, activate it ("Displays") and do the same. [ Regression potential ] I'm not sure why or where the order changed to make the widget be realized earlier, if it matters or if this was always buggy and we got lucky. I would guess a refactoring in Nautilus itself, and so the proposed fix is safe, but watch out for other weirdness. [ Original description ] Using 16.04 daily image: 20160919(downloading date) With testing package for 4.8 kernel: ppa:canonical-kernel-team/unstable Graphic chips: 00:02.0 VGA compatible controller [0300]: Intel Corporation HD Graphics 530 [8086:191b] (rev 06) 01:00.0 3D controller [0302]: NVIDIA Corporation GM107M [GeForce GTX 960M] [10de:139b] (rev ff) Desktop wallpaper on extended display shows black background only, and the hdmi detection is very unstable. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.8.0-14.15-generic 4.8.0-rc7 Uname: Linux 4.8.0-14-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.3-0ubuntu7 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: Fri Sep 23 05:30:30 2016 DistUpgraded: Fresh install DistroCodename: yakkety DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 530 [1028:06e4] InstallationDate: Installed on 2016-09-20 (3 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160919) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f3:21d5 Elan Microelectronics Corp. Bus 001 Device 002: ID 0a5c:6410 Broadcom Corp. Bus 001 Device 004: ID 0c45:6713 Microdia Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 15 9550 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-14-generic.efi.signed root=UUID=d16ac6eb-1b3e-4aa5-813b-57b5c7ef165a ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/07/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.02.00 dmi.board.name: 0N7TVV dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA01:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 15 9550 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1 version.xserver-xorg-video-intel:
[Desktop-packages] [Bug 1637271] [NEW] Desktop background is black after resume from suspend
Public bug reported: Running a standard 16.10 system with Unity 7, Intel i965 graphics, and a secondary external display. This behaviour has been observed under 16.04 and possibly earlier releases as well. Often (though frustratingly not always), when I resume from suspend, my desktop background will be solid black, my wallpaper is not visible. This is *not* the background colour I have selected in the Appearance settings. The system is fully usable when this occurs: cursor, icons, windows, etc. all render fine. If I change any Appearance setting (zoom/tile type, colour, image), it seems to refresh and my wallpaper is restored. Sometimes this only happens on my secondary display, and the wallpaper is still visible on my primary display. Please move this bug as appropriate, I wasn't quite sure what to report this against. Compiz? GNOME? ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xorg 1:7.7+13ubuntu4 Uname: Linux 4.8.0-2.1-liquorix-amd64 x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Thu Oct 27 12:08:50 2016 DistUpgraded: 2016-10-18 18:39:21,612 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)) DistroCodename: yakkety DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems 4th Gen Core Processor Integrated Graphics Controller [1179:fa72] InstallationDate: Installed on 2014-08-03 (815 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: TOSHIBA Satellite P75-A ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-2.1-liquorix-amd64 root=UUID=9b00c4ca-5dfe-4d81-89db-3404d87c8820 ro quiet splash zswap.enabled=1 vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to yakkety on 2016-10-18 (8 days ago) dmi.bios.date: 04/18/2014 dmi.bios.vendor: Insyde Corp. dmi.bios.version: 1.50 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Type2 - Board Product Name1 dmi.board.vendor: Type2 - Board Vendor Name1 dmi.board.version: Type2 - Board Version dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: OEM Chassis Manufacturer dmi.chassis.version: OEM Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvr1.50:bd04/18/2014:svnTOSHIBA:pnSatelliteP75-A:pvrPSPLNU-04702KB:rvnType2-BoardVendorName1:rnType2-BoardProductName1:rvrType2-BoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion: dmi.product.name: Satellite P75-A dmi.product.version: PSPLNU-04702KB dmi.sys.vendor: TOSHIBA 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 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: Wed Oct 19 12:28:06 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id8349 vendor AUO xserver.version: 2:1.18.4-1ubuntu6 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 ubuntu yakkety -- 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/1637271 Title: Desktop background is black after resume from suspend Status in xorg package in Ubuntu: New Bug description: Running a standard 16.10 system with Unity 7, Intel i965 graphics, and a secondary external display. This behaviour has been observed under 16.04 and possibly earlier releases as well. Often (though frustratingly not always), when I resume from suspend, my desktop background will be solid black, my wallpaper is not visible. This is *not* the background colour I have selected in the Appearance settings. The system is fully usable when this occurs: cursor, icons, windows, etc. all render fine. If I change any Appearance setting (zoom/tile type, colour, image), it seems to
[Desktop-packages] [Bug 1342675] Re: Random characters in screen text suddenly disappear
*** This bug is a duplicate of bug 1573959 *** https://bugs.launchpad.net/bugs/1573959 ** This bug has been marked a duplicate of bug 1573959 On-screen text disappears after suspend -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1342675 Title: Random characters in screen text suddenly disappear Status in xserver-xorg-video-intel package in Ubuntu: Incomplete Bug description: While using my machine, characters suddenly disappear. No character in particular, not in any single application in particular, and copying and pasting the text preserves the characters. Scrolling the text out of view and back into view doesn't affect the missing characters. Switching between applications may change the affected characters (possibly due to a redraw operation?) Restarting often solves the problem, but it comes back after a couple of hours working. I've attached a screenshot to show you the problem. I do believe this is different than the bug relating to garbled characters in a number of ways 1. I don't ever get garbled characters 2. Scrolling out/in of the affected text doesn't re-show the missing characters, even navigating inside the application has no effect. 3. It's global, I can even see it on Desktop icon names ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-30.55-generic 3.13.11.2 Uname: Linux 3.13.0-30-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.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: Wed Jul 16 14:48:25 2014 DistUpgraded: 2014-06-29 16:38:35,552 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: virtualbox, 4.3.10, 3.11.0-24-generic, x86_64: installed virtualbox, 4.3.10, 3.13.0-30-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 02) (prog-if 00 [VGA controller]) Subsystem: LG Electronics, Inc. Device [1854:0803] InstallationDate: Installed on 2014-03-28 (109 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: LG Electronics R590-G.ARIBE8 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-30-generic root=UUID=79c2f2b5-87cb-44d0-83fa-d99e73bb0a73 ro quiet splash vt.handoff=7 SourcePackage: xserver-xorg-video-intel UpgradeStatus: Upgraded to trusty on 2014-06-29 (16 days ago) dmi.bios.date: 01/06/2010 dmi.bios.vendor: INSYDE dmi.bios.version: QL4L3I51 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Base Board Product Name dmi.board.vendor: Intel Corp. dmi.board.version: Base Board Version dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDE:bvrQL4L3I51:bd01/06/2010:svnLGElectronics:pnR590-G.ARIBE8:pvr05:rvnIntelCorp.:rnBaseBoardProductName:rvrBaseBoardVersion:cvnChassisManufacturer:ct1:cvrChassisVersion: dmi.product.name: R590-G.ARIBE8 dmi.product.version: 05 dmi.sys.vendor: LG Electronics version.compiz: compiz 1:0.9.11.1+14.04.20140701-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Wed Jul 16 01:52:06 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 560 vendor LGD xserver.version: 2:1.15.1-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1342675/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1327801] Re: Bightness and contrast settings have no effect
As reported at Bug #1340161 the problem is solved for a Canon LiDE 110 scanner using Ubuntu 16.04 and simple-scan 3.20.0=0ubuntu1 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to simple-scan in Ubuntu. https://bugs.launchpad.net/bugs/1327801 Title: Bightness and contrast settings have no effect Status in simple-scan package in Ubuntu: Triaged Bug description: Scanner: Canon, Inc. CanoScan N1240U/LiDE 30 Ubuntu 14.04, Simple Scan version 3.12.1. Adjusting the settings of brightness and contrast has no effect. With the default for scanning in "text" mode being too bright, this makes "Simple Scan" in text mode unusable for me. Brightness and contrast settings don't work in "foto" mode, too. But the default of the foto mode is usable. Brightness setting does work in program "Skanlite". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/1327801/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1579403] Re: Random characters in screen text suddenly disappear after wake from sleep or switching user
*** This bug is a duplicate of bug 1573959 *** https://bugs.launchpad.net/bugs/1573959 ** This bug has been marked a duplicate of bug 1573959 On-screen text disappears after suspend -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1579403 Title: Random characters in screen text suddenly disappear after wake from sleep or switching user Status in xserver-xorg-video-intel package in Ubuntu: Expired Bug description: After wake from sleep or switching user, characters suddenly disappear. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6 Uname: Linux 4.4.0-18-generic x86_64 NonfreeKernelModules: wl .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 BootLog: CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sat May 7 20:51:58 2016 DistUpgraded: 2016-03-03 21:54:17,365 DEBUG enabling apt cron job DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 4.4.0-18-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 4.4.0-21-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 4.4.0-22-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:3978] InstallationDate: Installed on 2015-12-02 (156 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 006: ID 04f3:0446 Elan Microelectronics Corp. Bus 001 Device 003: ID 105b:e065 Foxconn International, Inc. BCM43142A0 Bluetooth module Bus 001 Device 002: ID 0c45:6514 Microdia Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20404 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-18-generic.efi.signed root=UUID=fe6b4e61-411f-4d2c-8503-d340e6c8bd4c ro quiet splash pcie_aspm i915.lvds_downclock=1 i915.i915_enable_rc6=1 i915.i915_enable_fbc=1 vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to xenial on 2016-03-03 (64 days ago) dmi.bios.date: 05/21/2014 dmi.bios.vendor: LENOVO dmi.bios.version: A0CN26WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Lenovo Flex 2-14 dmi.board.vendor: LENOVO dmi.board.version: 31900058 Std dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Flex 2-14 dmi.modalias: dmi:bvnLENOVO:bvrA0CN26WW:bd05/21/2014:svnLENOVO:pn20404:pvrLenovoFlex2-14:rvnLENOVO:rnLenovoFlex2-14:rvr31900058Std:cvnLENOVO:ct10:cvrLenovoFlex2-14: dmi.product.name: 20404 dmi.product.version: Lenovo Flex 2-14 dmi.sys.vendor: LENOVO 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: Fri May 6 18:09:14 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id1094 vendor LGD xserver.version: 2:1.18.3-1ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1579403/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1340161] Re: brightness, contrast for Canon LIDE 110 not working
*** This bug is a duplicate of bug 1327801 *** https://bugs.launchpad.net/bugs/1327801 Brightness and Contrast adjustments for Canon LiDE 110 in Ubuntu 16.04, simple-scan 3.20.0-0ubuntu1 work perfectly! So I think this specific bug is solved, even though others with different scanner models are reporting problems. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to simple-scan in Ubuntu. https://bugs.launchpad.net/bugs/1340161 Title: brightness, contrast for Canon LIDE 110 not working Status in simple-scan package in Ubuntu: Incomplete Bug description: I greatly appreciate the added sliders for brightness, contrast, and quality in the simple-scan preferences. However, for my scanner, they seem to have no effect, and resulting scans of color text documents are still very gray, just as when the brightness and contrast are set to the default values, or in prior version of simple-scan that did not have the sliders. My scanner is a Canon Canoscan LIDE 110. Using xsane, I can easily adjust the brightness and contrast, so I don't believe it is a problem with the scanner itself, but I am happy to perform any tests. I am using simple-scan 3.12.1 in Trusty. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/1340161/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1580463] Update Released
The verification of the Stable Release Update for im-config has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to im-config in Ubuntu. https://bugs.launchpad.net/bugs/1580463 Title: Snap blocks access to system input methods (ibus, fcitx, ...) Status in apparmor package in Ubuntu: Fix Released Status in im-config package in Ubuntu: Fix Released Status in snapd package in Ubuntu: Fix Released Status in apparmor source package in Xenial: Fix Released Status in im-config source package in Xenial: Fix Released Status in snapd source package in Xenial: Fix Released Status in apparmor source package in Yakkety: Fix Released Status in im-config source package in Yakkety: Fix Released Status in snapd source package in Yakkety: Fix Released Bug description: = SRU im-config = [Impact] ibus-daemon by default uses a unix socket name of /tmp/dbus-... that is indistinguishable from dbus-daemon abstract sockets. While dbus-daemon has AppArmor mediation, ibus-daemon does not so it is important that its abstract socket not be confused with dbus-daemon's. By modifying ibus-daemon's start arguments to use "--address 'unix:tmpdir=/tmp/ibus'" AppArmor can continue mediating DBus abstract sockets like normal and also mediate access to the ibus-daemon-specific abstract socket via unix rules. This also tidies up the abstract socket paths so that it is clear which are for ibus-daemon, which for dbus-daemon, etc. The upload simply adjusts 21_ibus.rc to start ibus-daemon with "-- address 'unix:tmpdir=/tmp/ibus'" and adds a comment. No compiled code changes are required. [Test Case] 1. start a unity session before updating to the package in -proposed 2. $ grep IBUS_ADDRESS ~/.config/ibus/bus/*-unix-0 IBUS_ADDRESS=unix:abstract=/tmp/dbus-Vyx8fGFA,guid=28e8e7e89f902c8d4e9d77c5557add76 3. $ lsof -p $(pidof ibus-daemon) | grep '/dbus' ibus-daem 2973 jamie8u unix 0x 0t0 29606 @/tmp/dbus-oxKYpN30 type=STREAM 4. update the package in -proposed and perform '2' and '3'. The IBUS_ADDRESSES should be the same as before 5. logout of unity, then log back in 6. $ grep IBUS_ADDRESS ~/.config/ibus/bus/*-unix-0 IBUS_ADDRESS=unix:abstract=/tmp/ibus/dbus-SpxOl8Fc,guid=06d4bbeb07614c6dffbf221c57473f4e (notice '/tmp/ibus/' in the path) 7. $ lsof -p $(pidof ibus-daemon) | grep '/dbus' ibus-daem 3471 jamie8u unix 0x 0t0 26107 @/tmp/ibus/dbus-SpxOl8Fc type=STREAM ... (notice '@/tmp/ibus/' in the path) In addition to the above, you can test for regressions by opening 'System Settings' under the 'gear' icon in the panel and selecting 'Text Entry'. From there, add an input source on the right, make sure 'Show current input source in the menu bar' is checked, then use the input source panel indicator to change input sources. Extended test case to verify input support still works in unconfined and confined applications: 1. Systems Settings Language Support, if prompted install the complete language support 2. Install Chinese (simple and traditional) 3. sudo apt-get install ibus-pinyin ibus-sunpinyin 4. logout / login 5. System Settings / Text Entry - add Chinese (Pinyin) (IBus) 6. select pinyin from the indicator 7. sudo lsof | grep ibus | grep @ # will use @/tmp/dbus-... 8. open gnome-calculator and try to type something in (should get a pop-up) 9. open evince and try to search a pdf (should get a pop up) 10. upgrade apparmor and im-config from xenial-proposed 11. logout and back in 12. sudo lsof | grep ibus | grep @ # will use @/tmp/ibus/... 13. open gnome-calculator and try to type something in (should get a pop-up) 14. open evince and try to search a pdf (should get a pop up) 15. verify no new apparmor denials [Regression Potential] The regression potential is considered low because there are no compiled code changes and because the changes only occur after ibus- daemon is restarted, which is upon session start, not package upgrade. When it is restarted, the files in ~/.config/ibus/bus/*-unix-0 are updated accordingly for other applications to pick up. This change intentionally requires a change to the unity7 snapd interface, which is in already done. This change intentionally requires a change to apparmor to add a unix rule for communicating with the new ibus address. This is in xenial- proposed 2.10.95-0ubuntu2.3 (and 2.10.95-0ubuntu2.4). The packages changes to im-config use
[Desktop-packages] [Bug 1580463] Re: Snap blocks access to system input methods (ibus, fcitx, ...)
This bug was fixed in the package im-config - 0.29-1ubuntu12.2 --- im-config (0.29-1ubuntu12.2) xenial-proposed; urgency=medium * debian/patches/use-distinguishable-abstract-address.patch: adjust ibus-daemon args to include "--address 'unix:tmpdir=/tmp/ibus'" so it has a mediatable abstract socket path (LP: #1580463) * debian/control: Breaks on apparmor << 2.10.95-0ubuntu2.3 since that adjusts the ibus abstraction to allow applications to communicate with an ibus-daemon started with "--address 'unix:tmpdir=/tmp/ibus'" -- Jamie StrandbogeFri, 07 Oct 2016 11:37:31 + ** Changed in: im-config (Ubuntu Xenial) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to im-config in Ubuntu. https://bugs.launchpad.net/bugs/1580463 Title: Snap blocks access to system input methods (ibus, fcitx, ...) Status in apparmor package in Ubuntu: Fix Released Status in im-config package in Ubuntu: Fix Released Status in snapd package in Ubuntu: Fix Released Status in apparmor source package in Xenial: Fix Released Status in im-config source package in Xenial: Fix Released Status in snapd source package in Xenial: Fix Released Status in apparmor source package in Yakkety: Fix Released Status in im-config source package in Yakkety: Fix Released Status in snapd source package in Yakkety: Fix Released Bug description: = SRU im-config = [Impact] ibus-daemon by default uses a unix socket name of /tmp/dbus-... that is indistinguishable from dbus-daemon abstract sockets. While dbus-daemon has AppArmor mediation, ibus-daemon does not so it is important that its abstract socket not be confused with dbus-daemon's. By modifying ibus-daemon's start arguments to use "--address 'unix:tmpdir=/tmp/ibus'" AppArmor can continue mediating DBus abstract sockets like normal and also mediate access to the ibus-daemon-specific abstract socket via unix rules. This also tidies up the abstract socket paths so that it is clear which are for ibus-daemon, which for dbus-daemon, etc. The upload simply adjusts 21_ibus.rc to start ibus-daemon with "-- address 'unix:tmpdir=/tmp/ibus'" and adds a comment. No compiled code changes are required. [Test Case] 1. start a unity session before updating to the package in -proposed 2. $ grep IBUS_ADDRESS ~/.config/ibus/bus/*-unix-0 IBUS_ADDRESS=unix:abstract=/tmp/dbus-Vyx8fGFA,guid=28e8e7e89f902c8d4e9d77c5557add76 3. $ lsof -p $(pidof ibus-daemon) | grep '/dbus' ibus-daem 2973 jamie8u unix 0x 0t0 29606 @/tmp/dbus-oxKYpN30 type=STREAM 4. update the package in -proposed and perform '2' and '3'. The IBUS_ADDRESSES should be the same as before 5. logout of unity, then log back in 6. $ grep IBUS_ADDRESS ~/.config/ibus/bus/*-unix-0 IBUS_ADDRESS=unix:abstract=/tmp/ibus/dbus-SpxOl8Fc,guid=06d4bbeb07614c6dffbf221c57473f4e (notice '/tmp/ibus/' in the path) 7. $ lsof -p $(pidof ibus-daemon) | grep '/dbus' ibus-daem 3471 jamie8u unix 0x 0t0 26107 @/tmp/ibus/dbus-SpxOl8Fc type=STREAM ... (notice '@/tmp/ibus/' in the path) In addition to the above, you can test for regressions by opening 'System Settings' under the 'gear' icon in the panel and selecting 'Text Entry'. From there, add an input source on the right, make sure 'Show current input source in the menu bar' is checked, then use the input source panel indicator to change input sources. Extended test case to verify input support still works in unconfined and confined applications: 1. Systems Settings Language Support, if prompted install the complete language support 2. Install Chinese (simple and traditional) 3. sudo apt-get install ibus-pinyin ibus-sunpinyin 4. logout / login 5. System Settings / Text Entry - add Chinese (Pinyin) (IBus) 6. select pinyin from the indicator 7. sudo lsof | grep ibus | grep @ # will use @/tmp/dbus-... 8. open gnome-calculator and try to type something in (should get a pop-up) 9. open evince and try to search a pdf (should get a pop up) 10. upgrade apparmor and im-config from xenial-proposed 11. logout and back in 12. sudo lsof | grep ibus | grep @ # will use @/tmp/ibus/... 13. open gnome-calculator and try to type something in (should get a pop-up) 14. open evince and try to search a pdf (should get a pop up) 15. verify no new apparmor denials [Regression Potential] The regression potential is considered low because there are no compiled code changes and because the changes only occur after ibus- daemon is restarted, which is upon session start, not package upgrade. When it is restarted, the files in ~/.config/ibus/bus/*-unix-0 are updated accordingly for other applications to pick up. This change intentionally requires a change to the unity7 snapd interface, which is in
[Desktop-packages] [Bug 1340161] Re: brightness, contrast for Canon LIDE 110 not working
*** This bug is a duplicate of bug 1327801 *** https://bugs.launchpad.net/bugs/1327801 ** This bug has been marked a duplicate of bug 1327801 Bightness and contrast settings have no effect -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to simple-scan in Ubuntu. https://bugs.launchpad.net/bugs/1340161 Title: brightness, contrast for Canon LIDE 110 not working Status in simple-scan package in Ubuntu: Incomplete Bug description: I greatly appreciate the added sliders for brightness, contrast, and quality in the simple-scan preferences. However, for my scanner, they seem to have no effect, and resulting scans of color text documents are still very gray, just as when the brightness and contrast are set to the default values, or in prior version of simple-scan that did not have the sliders. My scanner is a Canon Canoscan LIDE 110. Using xsane, I can easily adjust the brightness and contrast, so I don't believe it is a problem with the scanner itself, but I am happy to perform any tests. I am using simple-scan 3.12.1 in Trusty. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/1340161/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1637236] Re: New upstream microreleases 9.1.24, 9.3.15, 9.5.5
9.5.5 should hit Debian unstable RSN, will sync from there to zesty. ** Also affects: postgresql-9.5 (Ubuntu) Importance: Undecided Status: New ** Also affects: postgresql-9.1 (Ubuntu Zesty) Importance: Undecided Status: New ** Also affects: postgresql-9.3 (Ubuntu Zesty) Importance: Undecided Status: New ** Also affects: postgresql-9.5 (Ubuntu Zesty) Importance: Undecided Status: New ** Also affects: postgresql-9.1 (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: postgresql-9.3 (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: postgresql-9.5 (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: postgresql-9.1 (Ubuntu Yakkety) Importance: Undecided Status: New ** Also affects: postgresql-9.3 (Ubuntu Yakkety) Importance: Undecided Status: New ** Also affects: postgresql-9.5 (Ubuntu Yakkety) Importance: Undecided Status: New ** Also affects: postgresql-9.1 (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: postgresql-9.3 (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: postgresql-9.5 (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: postgresql-9.1 (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: postgresql-9.3 (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: postgresql-9.5 (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: postgresql-9.5 (Ubuntu Zesty) Status: New => Fix Committed ** No longer affects: postgresql-9.1 (Ubuntu Zesty) ** No longer affects: postgresql-9.1 (Ubuntu Yakkety) ** No longer affects: postgresql-9.1 (Ubuntu Xenial) ** Changed in: postgresql-9.1 (Ubuntu) Status: New => Invalid ** No longer affects: postgresql-9.3 (Ubuntu Precise) ** No longer affects: postgresql-9.3 (Ubuntu Xenial) ** No longer affects: postgresql-9.3 (Ubuntu Yakkety) ** No longer affects: postgresql-9.3 (Ubuntu Zesty) ** Changed in: postgresql-9.3 (Ubuntu) Status: New => Invalid ** No longer affects: postgresql-9.5 (Ubuntu Precise) ** No longer affects: postgresql-9.5 (Ubuntu Trusty) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to postgresql-9.1 in Ubuntu. https://bugs.launchpad.net/bugs/1637236 Title: New upstream microreleases 9.1.24, 9.3.15, 9.5.5 Status in postgresql-9.1 package in Ubuntu: Invalid Status in postgresql-9.3 package in Ubuntu: Invalid Status in postgresql-9.5 package in Ubuntu: Fix Committed Status in postgresql-9.1 source package in Precise: New Status in postgresql-9.1 source package in Trusty: New Status in postgresql-9.3 source package in Trusty: New Status in postgresql-9.5 source package in Xenial: New Status in postgresql-9.5 source package in Yakkety: New Status in postgresql-9.5 source package in Zesty: Fix Committed Bug description: https://www.postgresql.org/about/news/1712/ As per the standing micro-release exception these should land in stable Ubuntu releases. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postgresql-9.1/+bug/1637236/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1636514] Re: nautilus crashed with SIGSEGV in gtk_tree_view_set_cursor_on_cell()
** Attachment removed: "JournalErrors.txt" https://bugs.launchpad.net/ubuntu-gnome/+bug/1636514/+attachment/4766992/+files/JournalErrors.txt ** Information type changed from Private to Public -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1636514 Title: nautilus crashed with SIGSEGV in gtk_tree_view_set_cursor_on_cell() Status in Ubuntu GNOME: Invalid Status in nautilus package in Ubuntu: Invalid Bug description: This crash occurred just after I had asked Nautilus to move several large files (in groups) to several different locations. Then I believe that I minimized Nautilus and in a few minutes noticed the crash. ProblemType: Crash DistroRelease: Ubuntu 16.10 Package: nautilus 1:3.22.1-1ubuntu0~yakkety2 [origin: LP-PPA-gnome3-team-gnome3-staging] ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0 Uname: Linux 4.8.0-26-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Oct 25 13:52:09 2016 ExecutablePath: /usr/bin/nautilus InstallationDate: Installed on 2016-05-15 (162 days ago) InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 (20151021) ProcCmdline: nautilus . Signal: 11 SourcePackage: nautilus StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 gtk_tree_view_set_cursor_on_cell () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () ?? () Title: nautilus crashed with SIGSEGV in gtk_tree_view_set_cursor_on_cell() UpgradeStatus: Upgraded to yakkety on 2016-10-19 (5 days ago) UserGroups: adm cdrom dip libvirt libvirtd lpadmin plugdev sambashare sudo usr_lib_nautilus: dropbox2015.10.28 gnome-terminal 3.20.2-1ubuntu5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-gnome/+bug/1636514/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1637244] [NEW] skat.dk login hangs
Public bug reported: When connecting to the Danish tax department skat.dk The login which is using nemlog-in.dk hangs. Only in Ubuntu. Firefox in Windows works. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: firefox 49.0+build4-0ubuntu0.16.04.1 ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21 Uname: Linux 4.4.0-45-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: vh 1676 F pulseaudio BrokenPermissions: datareporting/archived/2016-09/1474817424274.9118c853-9f76-4e76-8668-df114ceb9621.main.jsonlz4 (0o600, wrong owner) saved-telemetry-pings/9118c853-9f76-4e76-8668-df114ceb9621 (0o600, wrong owner) BuildID: 20160920074044 Channel: Unavailable CurrentDesktop: Unity Date: Thu Oct 27 17:39:46 2016 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2014-07-09 (840 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) IpRoute: default via 192.168.242.1 dev wlan0 proto static metric 600 169.254.0.0/16 dev wlan0 scope link metric 1000 192.168.242.0/24 dev wlan0 proto kernel scope link src 192.168.242.30 metric 600 Locales: extensions.sqlite corrupt or missing Plugins: Citrix Receiver for Linux - /opt/Citrix/ICAClient/npica.so (icaclient) Shockwave Flash - /usr/lib/browser-plugin-freshplayer-pepperflash/libfreshwrapper-flashplayer.so (browser-plugin-freshplayer-pepperflash) iTunes Application Detector - /usr/lib/mozilla/plugins/librhythmbox-itms-detection-plugin.so (rhythmbox-mozilla) Java(TM) Plug-in 12.0.0.0 - /usr/lib/jvm/java-9-oracle/lib/amd64/libnpjp2.so Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so PrefSources: prefs.js Profiles: Profile0 (Default) - LastVersion=49.0/20160920074044 (In use) RelatedPackageVersions: icaclient 13.1.0.285639 browser-plugin-freshplayer-pepperflash 0.3.4-3 rhythmbox-mozilla 3.3-1ubuntu7 RunningIncompatibleAddons: False SourcePackage: firefox Themes: extensions.sqlite corrupt or missing UpgradeStatus: Upgraded to xenial on 2016-08-01 (86 days ago) dmi.bios.date: 11/09/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 80ET61WW (2.01 ) dmi.board.name: 03193TG dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr80ET61WW(2.01):bd11/09/2011:svnLENOVO:pn03193TG:pvrThinkPadEdge:rvnLENOVO:rn03193TG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 03193TG dmi.product.version: ThinkPad Edge dmi.sys.vendor: LENOVO ** Affects: firefox (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1637244 Title: skat.dk login hangs Status in firefox package in Ubuntu: New Bug description: When connecting to the Danish tax department skat.dk The login which is using nemlog-in.dk hangs. Only in Ubuntu. Firefox in Windows works. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: firefox 49.0+build4-0ubuntu0.16.04.1 ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21 Uname: Linux 4.4.0-45-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: vh 1676 F pulseaudio BrokenPermissions: datareporting/archived/2016-09/1474817424274.9118c853-9f76-4e76-8668-df114ceb9621.main.jsonlz4 (0o600, wrong owner) saved-telemetry-pings/9118c853-9f76-4e76-8668-df114ceb9621 (0o600, wrong owner) BuildID: 20160920074044 Channel: Unavailable CurrentDesktop: Unity Date: Thu Oct 27 17:39:46 2016 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2014-07-09 (840 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) IpRoute: default via 192.168.242.1 dev wlan0 proto static metric 600 169.254.0.0/16 dev wlan0 scope link metric 1000 192.168.242.0/24 dev wlan0 proto kernel scope link src 192.168.242.30 metric 600 Locales: extensions.sqlite corrupt or missing Plugins: Citrix Receiver for Linux -
[Desktop-packages] [Bug 1637236] Re: New upstream microreleases 9.1.24, 9.3.15, 9.5.5
** Changed in: postgresql-9.5 (Ubuntu Zesty) Assignee: (unassigned) => Martin Pitt (pitti) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to postgresql-9.1 in Ubuntu. https://bugs.launchpad.net/bugs/1637236 Title: New upstream microreleases 9.1.24, 9.3.15, 9.5.5 Status in postgresql-9.1 package in Ubuntu: Invalid Status in postgresql-9.3 package in Ubuntu: Invalid Status in postgresql-9.5 package in Ubuntu: Fix Committed Status in postgresql-9.1 source package in Precise: New Status in postgresql-9.1 source package in Trusty: New Status in postgresql-9.3 source package in Trusty: New Status in postgresql-9.5 source package in Xenial: New Status in postgresql-9.5 source package in Yakkety: New Status in postgresql-9.5 source package in Zesty: Fix Committed Bug description: https://www.postgresql.org/about/news/1712/ As per the standing micro-release exception these should land in stable Ubuntu releases. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postgresql-9.1/+bug/1637236/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1584740] Re: Libreoffice impress hanging and high cpu on slide operations
I've run into this consistently on a Lenovo i7 with 16GB RAM. Libreoffice 5.2.2-0ubuntu1~xenial0 from the libreoffice/ppa. Attempts to adjust memory sizes and object counts don't fix it. Removing allt libreoffice-gtk* works to fix the issue. I tried libreoffice-gtk3 and libreoffice-gtk2 individually and they each have the problem. -- 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/1584740 Title: Libreoffice impress hanging and high cpu on slide operations Status in libreoffice package in Ubuntu: Confirmed Bug description: Steps to reproduce: - Create a presentation in libreoffice impress, 30-100 slides with or without images - Add, copy or delete slides - On those operations LO Impress hangs a lot; sometimes 5 mins or more - Opening and saving works quick Tested on 2 different laptops, both had the same issue. Both did have Intel Graphics, but different ones. It works fine on the same laptop with LO 5.1 on Ubuntu 14.04 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: libreoffice-impress 1:5.1.2-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Mon May 23 12:55:08 2016 InstallationDate: Installed on 2016-04-29 (23 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1584740/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1580463] Re: Snap blocks access to system input methods (ibus, fcitx, ...)
This bug was fixed in the package apparmor - 2.10.95-0ubuntu2.5 --- apparmor (2.10.95-0ubuntu2.5) xenial; urgency=medium * debian/lib/apparmor/functions, debian/apparmor.init, debian/apparmor.service, debian/apparmor.upstart, debian/lib/apparmor/profile-load: Adjust the checks that previously kept AppArmor policy from being loaded while booting a container. Now we attempt to load policy if we're in a LXD or LXC managed container that is using profile stacking inside of a policy namespace. (LP: #1628285) * Fix regression tests for stacking so that the kernel SRU process is not interrupted by failing tests whenever the AppArmor stacking features are backported from the 16.10 kernel or when the 16.04 LTS Enablement Stack receives a 4.8 or newer kernel - debian/patches/r3509-tests-fix-exec_stack-errors-1.patch: Fix the exec_stack.sh test when running on 4.8 or newer kernels (LP: #1628745) - debian/patches/r3558-tests-fix-exec_stack-errors-2.patch: Adjust the exec_stack.sh fix mentioned above to more accurately test kernels older than 4.8 (LP: #1630069) - debian/patches/allow-stacking-tests-to-use-system.patch: Apply this patch earlier in the series, as to match when it was committed upstream, so that the above two patches can be cherry-picked from lp:apparmor -- Tyler HicksFri, 07 Oct 2016 05:21:44 + ** Changed in: apparmor (Ubuntu Xenial) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to im-config in Ubuntu. https://bugs.launchpad.net/bugs/1580463 Title: Snap blocks access to system input methods (ibus, fcitx, ...) Status in apparmor package in Ubuntu: Fix Released Status in im-config package in Ubuntu: Fix Released Status in snapd package in Ubuntu: Fix Released Status in apparmor source package in Xenial: Fix Released Status in im-config source package in Xenial: Fix Committed Status in snapd source package in Xenial: Fix Released Status in apparmor source package in Yakkety: Fix Released Status in im-config source package in Yakkety: Fix Released Status in snapd source package in Yakkety: Fix Released Bug description: = SRU im-config = [Impact] ibus-daemon by default uses a unix socket name of /tmp/dbus-... that is indistinguishable from dbus-daemon abstract sockets. While dbus-daemon has AppArmor mediation, ibus-daemon does not so it is important that its abstract socket not be confused with dbus-daemon's. By modifying ibus-daemon's start arguments to use "--address 'unix:tmpdir=/tmp/ibus'" AppArmor can continue mediating DBus abstract sockets like normal and also mediate access to the ibus-daemon-specific abstract socket via unix rules. This also tidies up the abstract socket paths so that it is clear which are for ibus-daemon, which for dbus-daemon, etc. The upload simply adjusts 21_ibus.rc to start ibus-daemon with "-- address 'unix:tmpdir=/tmp/ibus'" and adds a comment. No compiled code changes are required. [Test Case] 1. start a unity session before updating to the package in -proposed 2. $ grep IBUS_ADDRESS ~/.config/ibus/bus/*-unix-0 IBUS_ADDRESS=unix:abstract=/tmp/dbus-Vyx8fGFA,guid=28e8e7e89f902c8d4e9d77c5557add76 3. $ lsof -p $(pidof ibus-daemon) | grep '/dbus' ibus-daem 2973 jamie8u unix 0x 0t0 29606 @/tmp/dbus-oxKYpN30 type=STREAM 4. update the package in -proposed and perform '2' and '3'. The IBUS_ADDRESSES should be the same as before 5. logout of unity, then log back in 6. $ grep IBUS_ADDRESS ~/.config/ibus/bus/*-unix-0 IBUS_ADDRESS=unix:abstract=/tmp/ibus/dbus-SpxOl8Fc,guid=06d4bbeb07614c6dffbf221c57473f4e (notice '/tmp/ibus/' in the path) 7. $ lsof -p $(pidof ibus-daemon) | grep '/dbus' ibus-daem 3471 jamie8u unix 0x 0t0 26107 @/tmp/ibus/dbus-SpxOl8Fc type=STREAM ... (notice '@/tmp/ibus/' in the path) In addition to the above, you can test for regressions by opening 'System Settings' under the 'gear' icon in the panel and selecting 'Text Entry'. From there, add an input source on the right, make sure 'Show current input source in the menu bar' is checked, then use the input source panel indicator to change input sources. Extended test case to verify input support still works in unconfined and confined applications: 1. Systems Settings Language Support, if prompted install the complete language support 2. Install Chinese (simple and traditional) 3. sudo apt-get install ibus-pinyin ibus-sunpinyin 4. logout / login 5. System Settings / Text Entry - add Chinese (Pinyin) (IBus) 6. select pinyin from the indicator 7. sudo lsof | grep ibus | grep @ # will use @/tmp/dbus-... 8. open gnome-calculator and try to type something in (should get a pop-up) 9. open evince and try to search a pdf
[Desktop-packages] [Bug 1327801] Re: Bightness and contrast settings have no effect
Hello, Same problem for me with Canon MP550 (scanner + printer) with Ubuntu Gnome 16.10. Regards. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to simple-scan in Ubuntu. https://bugs.launchpad.net/bugs/1327801 Title: Bightness and contrast settings have no effect Status in simple-scan package in Ubuntu: Triaged Bug description: Scanner: Canon, Inc. CanoScan N1240U/LiDE 30 Ubuntu 14.04, Simple Scan version 3.12.1. Adjusting the settings of brightness and contrast has no effect. With the default for scanning in "text" mode being too bright, this makes "Simple Scan" in text mode unusable for me. Brightness and contrast settings don't work in "foto" mode, too. But the default of the foto mode is usable. Brightness setting does work in program "Skanlite". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/1327801/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1637235] [NEW] xorg crashes on lock screen
Public bug reported: When I return from a locked screen, I get a the crash dialog "System program problem detected". The related file in /var/log crash shows this in the header lines: ProblemType: Crash Architecture: amd64 Date: Thu Oct 27 10:33:08 2016 DistroRelease: Ubuntu 16.04 ExecutablePath: /usr/lib/xorg/Xorg ExecutableTimestamp: 1473867446 ProcCmdline: /usr/lib/xorg/Xorg -core :1 -seat seat0 -auth /var/run/lightdm/root/:1 -nolisten tcp vt8 -novtswitch ProcCwd: / ProcEnviron: It appears that the xorg instance on vt8 is crashing while starting the lock process; the crash file in /var/crash appears just after locking the screen. I have attached the xorg log from the display that is crashing (Xorg.1.log). There is a related output in the main display log (Xorg.0.log): [ 10248.316] (II) AIGLX: Suspending AIGLX clients for VT switch [ 10248.350] (II) NOUVEAU(G0): NVLeaveVT is called. [ 10254.968] (II) AIGLX: Resuming AIGLX clients after VT switch [ 10254.968] (II) intel(0): switch to mode 1920x1080@60.0 on LVDS2 using pipe 0, position (0, 0), rotation normal, reflection none [ 10255.002] (II) NOUVEAU(G0): NVEnterVT is called. [ 10255.340] (--) synaptics: SynPS/2 Synaptics TouchPad: touchpad found The screen locking appears to be working. VT7 is locked with a re-direct to VT8. I can log back in through VT8 and everything is normal, with the exception of the initial crash and subsequent crash dialog pop-up. Here is some relevant system information: Lenovo ThinkPad W520 Description:Ubuntu 16.04.1 LTS Release:16.04 lightdm: Installed: 1.18.3-0ubuntu1 xorg: Installed: 1:7.7+13ubuntu3 xserver-xorg-video-intel: Installed: 2:2.99.917+git20160325-1ubuntu1.1 xserver-xorg-video-nouveau: Installed: 1:1.0.12-1build2 ** Affects: lightdm (Ubuntu) Importance: Undecided Status: New ** Tags: screen-lock ** Attachment added: "log file of crashed display during locking process" https://bugs.launchpad.net/bugs/1637235/+attachment/4768247/+files/Xorg.1.log -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1637235 Title: xorg crashes on lock screen Status in lightdm package in Ubuntu: New Bug description: When I return from a locked screen, I get a the crash dialog "System program problem detected". The related file in /var/log crash shows this in the header lines: ProblemType: Crash Architecture: amd64 Date: Thu Oct 27 10:33:08 2016 DistroRelease: Ubuntu 16.04 ExecutablePath: /usr/lib/xorg/Xorg ExecutableTimestamp: 1473867446 ProcCmdline: /usr/lib/xorg/Xorg -core :1 -seat seat0 -auth /var/run/lightdm/root/:1 -nolisten tcp vt8 -novtswitch ProcCwd: / ProcEnviron: It appears that the xorg instance on vt8 is crashing while starting the lock process; the crash file in /var/crash appears just after locking the screen. I have attached the xorg log from the display that is crashing (Xorg.1.log). There is a related output in the main display log (Xorg.0.log): [ 10248.316] (II) AIGLX: Suspending AIGLX clients for VT switch [ 10248.350] (II) NOUVEAU(G0): NVLeaveVT is called. [ 10254.968] (II) AIGLX: Resuming AIGLX clients after VT switch [ 10254.968] (II) intel(0): switch to mode 1920x1080@60.0 on LVDS2 using pipe 0, position (0, 0), rotation normal, reflection none [ 10255.002] (II) NOUVEAU(G0): NVEnterVT is called. [ 10255.340] (--) synaptics: SynPS/2 Synaptics TouchPad: touchpad found The screen locking appears to be working. VT7 is locked with a re- direct to VT8. I can log back in through VT8 and everything is normal, with the exception of the initial crash and subsequent crash dialog pop-up. Here is some relevant system information: Lenovo ThinkPad W520 Description:Ubuntu 16.04.1 LTS Release:16.04 lightdm: Installed: 1.18.3-0ubuntu1 xorg: Installed: 1:7.7+13ubuntu3 xserver-xorg-video-intel: Installed: 2:2.99.917+git20160325-1ubuntu1.1 xserver-xorg-video-nouveau: Installed: 1:1.0.12-1build2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1637235/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1637236] [NEW] New upstream microreleases 9.1.24, 9.3.15, 9.5.5
Public bug reported: https://www.postgresql.org/about/news/1712/ As per the standing micro-release exception these should land in stable Ubuntu releases. ** Affects: postgresql-9.1 (Ubuntu) Importance: Undecided Status: New ** Affects: postgresql-9.3 (Ubuntu) Importance: Undecided Status: New ** Also affects: postgresql-9.3 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to postgresql-9.1 in Ubuntu. https://bugs.launchpad.net/bugs/1637236 Title: New upstream microreleases 9.1.24, 9.3.15, 9.5.5 Status in postgresql-9.1 package in Ubuntu: New Status in postgresql-9.3 package in Ubuntu: New Bug description: https://www.postgresql.org/about/news/1712/ As per the standing micro-release exception these should land in stable Ubuntu releases. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postgresql-9.1/+bug/1637236/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1239087] Re: Safely remove is not working (or broken) in Gnome Disks
** CVE added: http://www.cve.mitre.org/cgi- bin/cvename.cgi?name=2016-5195 ** CVE added: http://www.cve.mitre.org/cgi- bin/cvename.cgi?name=2016-7039 ** CVE added: http://www.cve.mitre.org/cgi- bin/cvename.cgi?name=2016-7425 ** CVE added: http://www.cve.mitre.org/cgi- bin/cvename.cgi?name=2016-8658 ** CVE added: http://www.cve.mitre.org/cgi- bin/cvename.cgi?name=2015-7513 ** CVE added: http://www.cve.mitre.org/cgi- bin/cvename.cgi?name=2015-8956 ** CVE added: http://www.cve.mitre.org/cgi- bin/cvename.cgi?name=2016-0823 ** CVE added: http://www.cve.mitre.org/cgi- bin/cvename.cgi?name=2016-1237 ** CVE added: http://www.cve.mitre.org/cgi- bin/cvename.cgi?name=2016-5696 ** CVE added: http://www.cve.mitre.org/cgi- bin/cvename.cgi?name=2016-6327 ** CVE added: http://www.cve.mitre.org/cgi- bin/cvename.cgi?name=2016-6480 ** CVE added: http://www.cve.mitre.org/cgi- bin/cvename.cgi?name=2016-6828 ** CVE added: http://www.cve.mitre.org/cgi- bin/cvename.cgi?name=2016-7117 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-disk-utility in Ubuntu. https://bugs.launchpad.net/bugs/1239087 Title: Safely remove is not working (or broken) in Gnome Disks Status in GNOME Disks: Fix Released Status in udisks: Confirmed Status in gnome-disk-utility package in Ubuntu: Fix Released Status in gnome-disk-utility package in Fedora: Unknown Status in gnome-disk-utility package in openSUSE: Invalid Status in oem-workaround-xhci-quirk-dkms package in openSUSE: Fix Released Bug description: In 12.04 I was able to safely remove USB-stick (make its LED off) and USB-HDD (do a spin down). In 13.04 this option is missed. In 13.10 it is appeared again, but not working as expected: +Gnome Disks normally powers off the USB flash (tested on 4 different flashes and 2 USB cardreaders). - Gnome Disks does not spin down USB HDD (but udisks --detach does) ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gnome-disk-utility 3.8.2-1ubuntu2 ProcVersionSignature: Ubuntu 3.10.0-1.8-generic 3.10.0-rc7 Uname: Linux 3.10.0-1-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.12.5-0ubuntu2 Architecture: i386 Date: Sat Oct 12 13:39:21 2013 InstallationDate: Installed on 2013-03-06 (219 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha i386 (20130306) MarkForUpload: True SourcePackage: gnome-disk-utility UpgradeStatus: Upgraded to saucy on 2013-06-23 (110 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-disk-utility/+bug/1239087/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1239087]
openSUSE-SU-2016:2625-1: An update that solves 12 vulnerabilities and has 19 fixes is now available. Category: security (important) Bug References: 1000287,1001486,1003077,1003925,1003931,1004045,1004418,1004462,881008,909994,911687,922634,951155,960689,978094,980371,986570,989152,991247,991608,991665,993890,993891,994296,994520,994748,994752,994759,996664,999600,32 CVE References: CVE-2015-7513,CVE-2015-8956,CVE-2016-0823,CVE-2016-1237,CVE-2016-5195,CVE-2016-5696,CVE-2016-6327,CVE-2016-6480,CVE-2016-6828,CVE-2016-7117,CVE-2016-7425,CVE-2016-8658 Sources used: openSUSE 13.2 (src):bbswitch-0.8-3.22.1, cloop-2.639-14.22.1, crash-7.0.8-22.1, hdjmod-1.28-18.23.1, ipset-6.23-22.1, kernel-debug-3.16.7-45.1, kernel-default-3.16.7-45.1, kernel-desktop-3.16.7-45.1, kernel-docs-3.16.7-45.2, kernel-ec2-3.16.7-45.1, kernel-obs-build-3.16.7-45.1, kernel-obs-qa-3.16.7-45.1, kernel-obs-qa-xen-3.16.7-45.1, kernel-pae-3.16.7-45.1, kernel-source-3.16.7-45.1, kernel-syms-3.16.7-45.1, kernel-vanilla-3.16.7-45.1, kernel-xen-3.16.7-45.1, pcfclock-0.44-260.22.1, vhba-kmp-20140629-2.22.1, virtualbox-5.0.28-54.2, xen-4.4.4_05-51.2, xtables-addons-2.6-24.1 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-disk-utility in Ubuntu. https://bugs.launchpad.net/bugs/1239087 Title: Safely remove is not working (or broken) in Gnome Disks Status in GNOME Disks: Fix Released Status in udisks: Confirmed Status in gnome-disk-utility package in Ubuntu: Fix Released Status in gnome-disk-utility package in Fedora: Unknown Status in gnome-disk-utility package in openSUSE: Invalid Status in oem-workaround-xhci-quirk-dkms package in openSUSE: Fix Released Bug description: In 12.04 I was able to safely remove USB-stick (make its LED off) and USB-HDD (do a spin down). In 13.04 this option is missed. In 13.10 it is appeared again, but not working as expected: +Gnome Disks normally powers off the USB flash (tested on 4 different flashes and 2 USB cardreaders). - Gnome Disks does not spin down USB HDD (but udisks --detach does) ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gnome-disk-utility 3.8.2-1ubuntu2 ProcVersionSignature: Ubuntu 3.10.0-1.8-generic 3.10.0-rc7 Uname: Linux 3.10.0-1-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.12.5-0ubuntu2 Architecture: i386 Date: Sat Oct 12 13:39:21 2013 InstallationDate: Installed on 2013-03-06 (219 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha i386 (20130306) MarkForUpload: True SourcePackage: gnome-disk-utility UpgradeStatus: Upgraded to saucy on 2013-06-23 (110 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-disk-utility/+bug/1239087/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1239087]
This is an autogenerated message for OBS integration: This bug (922634) was mentioned in https://build.opensuse.org/request/show/437000 13.2 / kernel-source -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-disk-utility in Ubuntu. https://bugs.launchpad.net/bugs/1239087 Title: Safely remove is not working (or broken) in Gnome Disks Status in GNOME Disks: Fix Released Status in udisks: Confirmed Status in gnome-disk-utility package in Ubuntu: Fix Released Status in gnome-disk-utility package in Fedora: Unknown Status in gnome-disk-utility package in openSUSE: Invalid Status in oem-workaround-xhci-quirk-dkms package in openSUSE: Fix Released Bug description: In 12.04 I was able to safely remove USB-stick (make its LED off) and USB-HDD (do a spin down). In 13.04 this option is missed. In 13.10 it is appeared again, but not working as expected: +Gnome Disks normally powers off the USB flash (tested on 4 different flashes and 2 USB cardreaders). - Gnome Disks does not spin down USB HDD (but udisks --detach does) ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gnome-disk-utility 3.8.2-1ubuntu2 ProcVersionSignature: Ubuntu 3.10.0-1.8-generic 3.10.0-rc7 Uname: Linux 3.10.0-1-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.12.5-0ubuntu2 Architecture: i386 Date: Sat Oct 12 13:39:21 2013 InstallationDate: Installed on 2013-03-06 (219 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha i386 (20130306) MarkForUpload: True SourcePackage: gnome-disk-utility UpgradeStatus: Upgraded to saucy on 2013-06-23 (110 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-disk-utility/+bug/1239087/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1239087]
openSUSE-SU-2016:2583-1: An update that solves four vulnerabilities and has 21 fixes is now available. Category: security (important) Bug References: 1000287,1000304,1000907,1001462,1001486,1004418,1004462,1005101,799133,881008,909994,911687,922634,963655,972460,978094,979681,987703,991247,991665,993890,993891,996664,999600,32 CVE References: CVE-2016-5195,CVE-2016-7039,CVE-2016-7425,CVE-2016-8658 Sources used: openSUSE Leap 42.1 (src):drbd-8.4.6-10.1, hdjmod-1.28-26.1, ipset-6.25.1-7.1, kernel-debug-4.1.34-33.1, kernel-default-4.1.34-33.1, kernel-docs-4.1.34-33.3, kernel-ec2-4.1.34-33.1, kernel-obs-build-4.1.34-33.1, kernel-obs-qa-4.1.34-33.1, kernel-obs-qa-xen-4.1.34-33.1, kernel-pae-4.1.34-33.1, kernel-pv-4.1.34-33.1, kernel-source-4.1.34-33.1, kernel-syms-4.1.34-33.1, kernel-vanilla-4.1.34-33.1, kernel-xen-4.1.34-33.1, lttng-modules-2.7.0-4.1, pcfclock-0.44-268.1, vhba-kmp-20140928-7.1 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-disk-utility in Ubuntu. https://bugs.launchpad.net/bugs/1239087 Title: Safely remove is not working (or broken) in Gnome Disks Status in GNOME Disks: Fix Released Status in udisks: Confirmed Status in gnome-disk-utility package in Ubuntu: Fix Released Status in gnome-disk-utility package in Fedora: Unknown Status in gnome-disk-utility package in openSUSE: Invalid Status in oem-workaround-xhci-quirk-dkms package in openSUSE: Fix Released Bug description: In 12.04 I was able to safely remove USB-stick (make its LED off) and USB-HDD (do a spin down). In 13.04 this option is missed. In 13.10 it is appeared again, but not working as expected: +Gnome Disks normally powers off the USB flash (tested on 4 different flashes and 2 USB cardreaders). - Gnome Disks does not spin down USB HDD (but udisks --detach does) ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gnome-disk-utility 3.8.2-1ubuntu2 ProcVersionSignature: Ubuntu 3.10.0-1.8-generic 3.10.0-rc7 Uname: Linux 3.10.0-1-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.12.5-0ubuntu2 Architecture: i386 Date: Sat Oct 12 13:39:21 2013 InstallationDate: Installed on 2013-03-06 (219 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha i386 (20130306) MarkForUpload: True SourcePackage: gnome-disk-utility UpgradeStatus: Upgraded to saucy on 2013-06-23 (110 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-disk-utility/+bug/1239087/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1054204] Re: Libreoffice chooses incorrect font weight
Came across this bug today because I cannot use Ubuntu Medium/Bold correctly in neither Libreoffice (5.1.4-0ubuntu1) nor Inkscape (0.91 r13725) under Kubuntu 16.04. The System was installed from scratch and updates are recent. I have tried the ttf-ubuntu-font-family/xenial package (0.83-0ubuntu2) as well as downloaded Versions from both font.ubuntu.com (0.83 too) and fontsquirrel.com. In LOO I get all weights under the "Ubuntu" Family entry, except "Medium" -- interestingly Light Italic/Italic/Medium Italic/Bold Italic are there and working! Non-Italic only Light, Regular and Bold show up as Styles. There is no separate Light/Medium Family, only Condensed and Mono. In Inkscape, otoh, I have Medium/Medium Italic, but no Bold styles. All available Styles are rendered correctly, i. e. "Regular" is normal, not Medium, etc. In Inkscape I can get a text set to correct Bold style if I enter "Bold" in the Style Dropdown manually. I am sure this is supposedly not the correct place to put this report - maybe someone can point me somewhere better. Maybe it is a regression, though. A quick look into Ubuntu-M.ttf showed the "Ubuntu Light" thing, and I have also read Bug 744812, but found it it also quite dated and complex. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fontconfig in Ubuntu. https://bugs.launchpad.net/bugs/1054204 Title: Libreoffice chooses incorrect font weight Status in Fontconfig: Fix Released Status in Ubuntu Font Family: Invalid Status in fontconfig package in Ubuntu: Fix Released Status in ubuntu-font-family-sources package in Ubuntu: Fix Released Status in ubuntu-font-family-sources source package in Quantal: Fix Released Status in ubuntu-font-family-sources source package in Raring: Fix Released Bug description: How to fix the problem: See comments on wrong "Ubuntu Light" font family being specified in the information of Ubuntu-M.ttf. You can fix the problem manually by installing fontforge program, going to Open dialog, navigating in it to /usr/share/fonts/truetype /ubuntu-font-family/ and opening Ubuntu-M.ttf. In Element -> Font Info, you can fix the family on the first page, and then export the font with File -> Generate Fonts, selecting the type "TrueType". Save to somewhere in your home folder first, accept the warnings, then in a terminal window / command line type: sudo mv Ubuntu-M.ttf /usr/share/fonts/truetype/ubuntu-font-family sudo dpkg-reconfigure fontconfig Attached to this bug report is also a branch of the Ubuntu packaging that includes this manually modified Ubuntu-M.ttf, since the sources seem not to be editable with free tools. Original description: After installing the Ubuntu Font 0.80-0ubuntu3+console from quantal I have the added "Medium" font weight:- /usr/share/fonts/truetype/ubuntu-font-family/UbuntuMono-B.ttf /usr/share/fonts/truetype/ubuntu-font-family/Ubuntu-RI.ttf /usr/share/fonts/truetype/ubuntu-font-family/Ubuntu-MI.ttf /usr/share/fonts/truetype/ubuntu-font-family/Ubuntu-LI.ttf /usr/share/fonts/truetype/ubuntu-font-family/UbuntuMono-RI.ttf /usr/share/fonts/truetype/ubuntu-font-family/Ubuntu-M.ttf /usr/share/fonts/truetype/ubuntu-font-family/UbuntuMono-BI.ttf /usr/share/fonts/truetype/ubuntu-font-family/Ubuntu-B.ttf /usr/share/fonts/truetype/ubuntu-font-family/Ubuntu-L.ttf /usr/share/fonts/truetype/ubuntu-font-family/Ubuntu-C.ttf /usr/share/fonts/truetype/ubuntu-font-family/Ubuntu-BI.ttf /usr/share/fonts/truetype/ubuntu-font-family/UbuntuMono-R.ttf /usr/share/fonts/truetype/ubuntu-font-family/Ubuntu-R.ttf If I install this font and choose "Ubuntu Light" in LibreOffice, it actually picks the "Medium" font weight. If I remove the medium font weight files and restart LibreOffice it chooses the right weight again. It seems related to bug 744812. Screenshots show the issue. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: libreoffice-writer 1:3.6.1~rc2-1ubuntu5 ProcVersionSignature: Ubuntu 3.5.0-15.22-generic 3.5.4 Uname: Linux 3.5.0-15-generic x86_64 ApportVersion: 2.5.2-0ubuntu4 Architecture: amd64 Date: Fri Sep 21 17:34:30 2012 EcryptfsInUse: Yes InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20120102) SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/fontconfig/+bug/1054204/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1626935] Re: [yakkety] desktop is black and/or flickering after plugging in a second monitor
Hello Yung, or anyone else affected, Accepted nautilus into yakkety-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/nautilus/1:3.20.3-1ubuntu3.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation 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: nautilus (Ubuntu Yakkety) 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 nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1626935 Title: [yakkety] desktop is black and/or flickering after plugging in a second monitor Status in compiz package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in nautilus package in Ubuntu: Fix Committed Status in compiz source package in Yakkety: New Status in mesa source package in Yakkety: New Status in nautilus source package in Yakkety: Fix Committed Bug description: [ Description ] Nautilus's wallpaper drawing doesn't respond to changes in monitor configuration. Instead of your wallpaper you see black. [ Fix ] Inside nautilus, the wallpaper widget connects to GTK's "monitors- changed" signal when it is constructed. It does this only once the widget is realized - a "realized" signal handler connects to "monitors-changed". In Yakkety, the "realized" signal handler is connected after the widget is already realized, meaning that the signal handler isn't called and we don't connect to the "monitors- changed" signal. The proposed fix remedies this by checking if we are realized and explicitly calling the signal handler if so. [ QA ] Have multiple monitors. Have only one of them connected. Log in. Plug in one monitor. If it's autoactivated, check you see your background on both monitors. If not, activate it ("Displays") and do the same. [ Regression potential ] I'm not sure why or where the order changed to make the widget be realized earlier, if it matters or if this was always buggy and we got lucky. I would guess a refactoring in Nautilus itself, and so the proposed fix is safe, but watch out for other weirdness. [ Original description ] Using 16.04 daily image: 20160919(downloading date) With testing package for 4.8 kernel: ppa:canonical-kernel-team/unstable Graphic chips: 00:02.0 VGA compatible controller [0300]: Intel Corporation HD Graphics 530 [8086:191b] (rev 06) 01:00.0 3D controller [0302]: NVIDIA Corporation GM107M [GeForce GTX 960M] [10de:139b] (rev ff) Desktop wallpaper on extended display shows black background only, and the hdmi detection is very unstable. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.8.0-14.15-generic 4.8.0-rc7 Uname: Linux 4.8.0-14-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.3-0ubuntu7 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: Fri Sep 23 05:30:30 2016 DistUpgraded: Fresh install DistroCodename: yakkety DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 530 [1028:06e4] InstallationDate: Installed on 2016-09-20 (3 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160919) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f3:21d5 Elan Microelectronics Corp. Bus 001 Device 002: ID 0a5c:6410 Broadcom Corp. Bus 001 Device 004: ID 0c45:6713 Microdia Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 15 9550 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-14-generic.efi.signed root=UUID=d16ac6eb-1b3e-4aa5-813b-57b5c7ef165a ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/07/2016
[Desktop-packages] [Bug 1633855] Re: akonadi fails to start after upgrade to yakkety
** Also affects: akonadi (Ubuntu Zesty) Importance: High Assignee: Clive Johnston (clivejo) Status: Triaged ** Also affects: mysql-5.5 (Ubuntu Zesty) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to akonadi in Ubuntu. https://bugs.launchpad.net/bugs/1633855 Title: akonadi fails to start after upgrade to yakkety Status in akonadi package in Ubuntu: Triaged Status in mysql-5.5 package in Ubuntu: New Status in akonadi source package in Precise: Fix Released Status in mysql-5.5 source package in Precise: New Status in akonadi source package in Trusty: Fix Released Status in mysql-5.5 source package in Trusty: New Status in akonadi source package in Yakkety: New Status in mysql-5.5 source package in Yakkety: New Status in akonadi source package in Zesty: Triaged Status in mysql-5.5 source package in Zesty: New Bug description: After yesterday 15 sept. upgrade to Kubuntu 16.10 Yakkety Yak, kmail fails to start, because akonadi backend fails. Starting akonadi from command line, $ akonadictl start the output contains: stderr: "mysqld: Error on realpath() on '/var/lib/mysql-files' (Error 2 - No such file or directory)\n2016-10-16T11:54:23.365277Z 0 [Warning] The syntax '--log_warnings/-W' is deprecated and will be removed in a future release. Please use '--log_error_verbosity' instead.\n2016-10-16T11:54:23.365377Z 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).\n2016-10-16T11:54:23.365479Z 0 [ERROR] Failed to access directory for --secure-file-priv. Please make sure that directory exists and is accessible by MySQL Server. Supplied value : /var/lib/mysql-files\n2016-10-16T11:54:23.365488Z 0 [ERROR] Aborting\n\n2016-10-16T11:54:23.365508Z 0 [Note] Binlog end\n" The cause is a regression in the file /etc/xdg/akonadi/mysql-global.conf provided by the package akonadi-backend-mysql Diff of the content of mysql-global.conf from Yakkety vs Xenial: diff -u "akonadi-backend-mysql_16.04.3-0ubuntu2_all.deb - mysql-global.conf" "akonadi-backend-mysql_15.12.3-0ubuntu6_all.deb - mysql-global.conf" --- "akonadi-backend-mysql_16.04.3-0ubuntu2_all.deb - mysql-global.conf" 2016-06-24 15:51:12.0 +0200 +++ "akonadi-backend-mysql_15.12.3-0ubuntu6_all.deb - mysql-global.conf" 2016-04-20 10:42:09.0 +0200 @@ -100,5 +100,14 @@ # We use InnoDB, so don't let MyISAM eat up memory key_buffer_size=16K +# KUBUNTU: +# Unset the export dir check as only the full mysql-server package creates it +secure_file_priv= + +# KUBUNTU: +# workaround for 5.7 being more strict with column types +# (reverts to 5.6 behavior) +sql_mode=NO_ENGINE_SUBSTITUTION + [client] default-character-set=utf8 Applying this patch fixes the bug. The "secure_file_priv" setting went missing is referenced in the package changelog: akonadi (4:15.12.3-0ubuntu5) xenial; urgency=medium * kubuntu_disable_secure_file_priv_check.diff: - Set secure_file_priv to empty as that directory is not set in a default kubuntu install -- Philip MuškovacMon, 18 Apr 2016 15:24:43 +0200 Marco Gamberoni To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/akonadi/+bug/1633855/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1478319] Re: Wifi doesn't reconnect to AP if it uses the same SSID than another AP
@jibel, thanks for the log. It looks like wpa_supplicant removes the previous connection due to a timeout before you connect to another Freewifi hotspot, which probably helps to rule out issues. Also, a new DHCP lease is requested after reconnecting in all cases, and it gives you back always the same address, so it seems like network configuration is fine. So all looks good this time. -- 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/1478319 Title: Wifi doesn't reconnect to AP if it uses the same SSID than another AP Status in Canonical System Image: Confirmed Status in network-manager package in Ubuntu: Confirmed Bug description: current build number: 68 device name: arale channel: ubuntu-touch/rc-proposed/meizu.en last update: 2015-07-24 08:00:20 version version: 68 version ubuntu: 20150724 version device: 20150709-8965e37 version custom: 20150716-819-8-42 My ISP (Free in France) provides a hotspot service so that customers can use the connection of any other customer using a generic open Wifi connection (for reference http://www.free.fr/assistance/2303.html - in French) The SSID is called 'FreeWifi' on all the boxes but obviously APs are all different since it's customers' DSL routers. When I connect to one of this access point, suspend the phone and resume it in another location where the SSID is available but from a different AP, the phone doesn't connect to this AP and the list of networks in the network-indicator doesn't refresh and still show the list of network from the previous location. I have to forget the network called 'FreeWifi' and reconnect in order to refresh the list and make it work. It's 100% reproducible. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1478319/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1080502] Re: Failure to burn particular FLAC files to Audio CD
Still a bug in 16.04 based linux mint 18. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to brasero in Ubuntu. https://bugs.launchpad.net/bugs/1080502 Title: Failure to burn particular FLAC files to Audio CD Status in brasero package in Ubuntu: Confirmed Bug description: The files are the album "Requiem for a Dying Star" by EvilWezil. They are in FLAC format as downloaded from Band Camp. They cause the following brasero-session.log: Checking session consistency (brasero_burn_check_session_consistency brasero-burn.c:1739) BraseroNormalize called brasero_job_get_action BraseroNormalize called brasero_job_get_action BraseroNormalize called brasero_job_get_tracks BraseroNormalize called brasero_job_get_action BraseroNormalize called brasero_job_get_session_output_size BraseroNormalize Output set (AUDIO) image = /tmp/brasero_tmp_M6P6NW.cdr BraseroNormalize called brasero_job_get_session_output_size BraseroNormalize called brasero_job_get_tracks BraseroNormalize called brasero_job_tag_lookup BraseroNormalize Analysing track file:///home/dpeale/Organized%20Files/Music/FLAC/EvilWezil/Requiem%20for%20a%20Dying%20Star/EvilWezil%20-%20Requiem%20for%20a%20Dying%20Star%20-%2001%20Overture.flac BraseroNormalize Creating new pipeline BraseroNormalize called brasero_job_set_current_action BraseroNormalize New decoded pad linked BraseroNormalize gstbaseparse.c(2890): gst_base_parse_loop (): /GstPipeline:pipeline20/GstDecodeBin:decodebin20/GstFlacParse:flacparse18: streaming stopped, reason not-negotiated BraseroNormalize called brasero_job_error BraseroNormalize finished with an error BraseroNormalize asked to stop because of an error error = 1 message = "GStreamer encountered a general stream error." BraseroNormalize stopping Session error : GStreamer encountered a general stream error. (brasero_burn_record brasero-burn.c:2856) These files also cause K3B to crash. These files play fine from the hard disk in every player I've tried, but that does not let me listen to this album in my car. I have not been able to find any burning software that can burn these files. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: brasero 3.4.1-0ubuntu3 ProcVersionSignature: Ubuntu 3.5.0-18.29-generic 3.5.7 Uname: Linux 3.5.0-18-generic x86_64 ApportVersion: 2.6.1-0ubuntu6 Architecture: amd64 Date: Sun Nov 18 15:46:16 2012 InstallationDate: Installed on 2011-05-22 (546 days ago) InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1) MarkForUpload: True SourcePackage: brasero UpgradeStatus: Upgraded to quantal on 2012-10-21 (28 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/brasero/+bug/1080502/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1080350] Re: 1002:9552 [Compaq Presario CQ61-320EG Notebook PC] CPU Overheating with ATI driver Radeon HD Mobility graphics
An old thread, I know but I've experienced similar problems. After upgrade from Ubuntu 14.04.3 to 16.04.1 with Xmonad window manager certain undesirable symptoms began to arise. Of course, fglrx was be removed and the xserver-xorg-driver-ati(?) graphics driver was installed instead. In 14.04 I was running the proprietary driver for the Intel part of the hybrid card. After upgrading some icons appear very large while others are normal. The laptop also runs about fifteen degC hotter. This is the most troubling aspect as it is detrimental to the health of the machine. I reverted to Ubuntu 14.04.3 with linux-image-xxx-lts-wily as the latest combination of Ubuntu and linux kernel compatible with fglrx. All very well until dirtyCOW arose, as this kernel is no longer supported. Question: Is this problem related to the others mentioned in this thread? Has there been a resolution since July 2016? The following information may help: Output of lspci -mm | grep VGA is: 00:01.0 "VGA compatible controller" "Advanced Micro Devices, Inc. [AMD/ATI]" "Richland [Radeon HD 8650G]" "Hewlett-Packard Company" "Richland [Radeon HD 8650G]" Output of sudo lshw -C video is *-display UNCLAIMED description: VGA compatible controller product: Richland [Radeon HD 8650G] vendor: Advanced Micro Devices, Inc. [AMD/ATI] physical id: 1 bus info: pci@:00:01.0 version: 00 width: 32 bits clock: 33MHz capabilities: pm pciexpress msi vga_controller bus_master cap_list configuration: latency=0 resources: memory:d000-dfff ioport:5000(size=256) memory:f040-f043 *-display UNCLAIMED description: Display controller product: Sun XT [Radeon HD 8670A/8670M/8690M / R5 M330] vendor: Advanced Micro Devices, Inc. [AMD/ATI] physical id: 0 bus info: pci@:01:00.0 version: 00 width: 64 bits clock: 33MHz capabilities: pm pciexpress msi cap_list configuration: latency=0 resources: memory:e000-efff memory:f030-f033 ioport:4000(size=256) memory:f034-f035 Output of lspci -nnk | grep -i vga -A3 is 00:01.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Richland [Radeon HD 8650G] [1002:990b] DeviceName: RICHLAND (990B) Subsystem: Hewlett-Packard Company Richland [Radeon HD 8650G] [103c:1985] Kernel modules: radeon Am I right in understanding that though the radeon kernel module is loaded it is not being used? If so, what must I do to use it? -- 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/1080350 Title: 1002:9552 [Compaq Presario CQ61-320EG Notebook PC] CPU Overheating with ATI driver Radeon HD Mobility graphics Status in xserver-xorg-driver-ati: Invalid Status in xserver-xorg-video-ati package in Ubuntu: Triaged Bug description: Ever since upgrading from Maverick (with GNOME Classic) to Precise (using Unity 2D since using the default Unity makes the situation worse) my note book regularly overheats with normal usage: I've been regularly using: echo low | sudo tee /sys/class/drm/card0/device/power_profile I've am also using psensor to warn me if the temperature rises above 92°. When 'idle' the temperature is at about 80°. If the CPU is used (merely starting eclipse and letting all the the startup validation processes finish) it quickly rises to 88°. If the usages is sustained (rebuilding a java project) the temperature oscillates between 95° and 98°. If I do anything else that adds to the load (ie. if the temperature is >98° for short period of time), the system freezes, but the everything remains on, fans and CPU temperature stays up. I need to turn off the notebook by keeping the power button pressed. Note that this system overheats /with/ the low power profile. Here are some general stats about this system, please let me know, if I can provide further information: This started after the upgrading from Maverick. I'm currently running Precise with the 2D Unity desktop. WORKAROUND: sudo apt-get -y install gnome-applets && sudo cpufreq- selector --cpu=0 --governor=powersave && sudo cpufreq-selector --cpu=1 --governor=powersave ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: xserver-xorg-video-radeon 1:6.14.99~git20111219.aacbd629-0ubuntu2 ProcVersionSignature: Ubuntu 3.2.0-33.52-generic 3.2.31 Uname: Linux 3.2.0-33-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.0.1-0ubuntu14 Architecture: amd64 CompizPlugins: [core,bailer,detection,composite,opengl,decor,compiztoolbox,grid,resize,snap,vpswitch,move,mousepoll,wall,place,imgpng,gnomecompat,unitymtgrabhandles,regex,session,animation,fade,workarounds,scale,expo,ezoom,unityshell] CompositorRunning: None Date: Sun Nov 18 14:30:50
[Desktop-packages] [Bug 1478319] Re: Wifi doesn't reconnect to AP if it uses the same SSID than another AP
I cannot reproduce the bug on stock krillin running rc-proposed and without the silo 2098 installed. syslog attached. ** Attachment added: "syslog_1478319_20161027.gz" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1478319/+attachment/4768226/+files/syslog_1478319_20161027.gz -- 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/1478319 Title: Wifi doesn't reconnect to AP if it uses the same SSID than another AP Status in Canonical System Image: Confirmed Status in network-manager package in Ubuntu: Confirmed Bug description: current build number: 68 device name: arale channel: ubuntu-touch/rc-proposed/meizu.en last update: 2015-07-24 08:00:20 version version: 68 version ubuntu: 20150724 version device: 20150709-8965e37 version custom: 20150716-819-8-42 My ISP (Free in France) provides a hotspot service so that customers can use the connection of any other customer using a generic open Wifi connection (for reference http://www.free.fr/assistance/2303.html - in French) The SSID is called 'FreeWifi' on all the boxes but obviously APs are all different since it's customers' DSL routers. When I connect to one of this access point, suspend the phone and resume it in another location where the SSID is available but from a different AP, the phone doesn't connect to this AP and the list of networks in the network-indicator doesn't refresh and still show the list of network from the previous location. I have to forget the network called 'FreeWifi' and reconnect in order to refresh the list and make it work. It's 100% reproducible. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1478319/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1611077] Re: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: cups (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1611077 Title: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in cups package in Ubuntu: Confirmed Bug description: No funciona impresión con Hp deskjet 3050 all in one ProblemType: Package DistroRelease: Ubuntu 16.04 Package: cups-daemon 2.1.3-4 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Mon Aug 8 15:29:11 2016 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2015-10-13 (300 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) Lpstat: device for Samsung-ML-2160-Series: usb://Samsung/ML-2160%20Series?serial=Z7C8B8GD4D00JYH MachineType: Gigabyte Technology Co., Ltd. B85M-D3H Papersize: a4 PpdFiles: Samsung-ML-2160-Series: Samsung ML-2160 Series ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic.efi.signed root=UUID=b5bc76e2-d1c3-4343-926f-4d9c78eb24fd ro quiet splash vt.handoff=7 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic.efi.signed root=UUID=b5bc76e2-d1c3-4343-926f-4d9c78eb24fd ro quiet splash vt.handoff=7 RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.12~ubuntu16.04.1 SourcePackage: cups Title: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/19/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: FB dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B85M-D3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrFB:bd06/19/2014:svnGigabyteTechnologyCo.,Ltd.:pnB85M-D3H:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnB85M-D3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: B85M-D3H dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. mtime.conffile..etc.init.d.cups: 2016-07-07T18:45:07.649090 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1611077/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1637174] Re: totem could not play music or video files
Problem had been fixed using this command: sudo apt-get install ubuntu- restricted-extras I am sure some files were missing or not all the formats were downloaded the first time. Thanks for your help. -- 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/1637174 Title: totem could not play music or video files Status in gstreamer1.0 package in Ubuntu: New Bug description: 1) Description: Ubuntu 16.04.1 LTS Release: 16.04 2) totem: Installed: 3.18.1-1ubuntu4 Candidate: 3.18.1-1ubuntu4 Version table: *** 3.18.1-1ubuntu4 500 500 http://sl.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 500 http://cz.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status 3.10.1-1ubuntu4 500 500 http://us.archive.ubuntu.com/ubuntu trusty/main amd64 Packages 3) totem should play audio and video files 4) it is asking for installation of plugins; once i click installed nothing happen after. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: libgstreamer1.0-0 1.8.2-1~ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21 Uname: Linux 4.4.0-45-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity Date: Thu Oct 27 12:39:18 2016 InstallationDate: Installed on 2016-06-17 (132 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) SourcePackage: gstreamer1.0 UpgradeStatus: Upgraded to xenial on 2016-08-04 (83 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1637174/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1637174] Re: totem could not play music or video files
Problem had been fixed using this command: sudo apt-get install ubuntu- restricted-extras I am sure some files were missing or not all the formats were downloaded the first time. Thanks for your help. -- 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/1637174 Title: totem could not play music or video files Status in gstreamer1.0 package in Ubuntu: New Bug description: 1) Description: Ubuntu 16.04.1 LTS Release: 16.04 2) totem: Installed: 3.18.1-1ubuntu4 Candidate: 3.18.1-1ubuntu4 Version table: *** 3.18.1-1ubuntu4 500 500 http://sl.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 500 http://cz.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status 3.10.1-1ubuntu4 500 500 http://us.archive.ubuntu.com/ubuntu trusty/main amd64 Packages 3) totem should play audio and video files 4) it is asking for installation of plugins; once i click installed nothing happen after. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: libgstreamer1.0-0 1.8.2-1~ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21 Uname: Linux 4.4.0-45-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity Date: Thu Oct 27 12:39:18 2016 InstallationDate: Installed on 2016-06-17 (132 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) SourcePackage: gstreamer1.0 UpgradeStatus: Upgraded to xenial on 2016-08-04 (83 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1637174/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1629611] Re: dns server priority broken
** Also affects: network-manager-openvpn Importance: Undecided Status: New ** Also affects: network-manager-vpnc Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1629611 Title: dns server priority broken Status in NetworkManager-OpenVPN: New Status in network-manager-vpnc: New Status in network-manager package in Ubuntu: Confirmed Bug description: network-manager: 1.2.4-0ubuntu1 Yakkety appears to have switched back from resolved to dnsmasq, but it seems server priority/order is broken. Example: In split DNS setups, connecting to VPN will not cause us to query the DNS provided by the VPN first (or only), which should be the proper way to resolve names in that case. Say server.example.com in the public DNS resolves to a.a.a.a and in the private DNS resolves to b.b.b.b. Stuff would work from my normal internet-connection, but connection to VPN would cause stuff to misbehave. I expect to hit the b.b.b.b address but since my normal LAN DNS is being used first, I'm really hitting a.a.a.a. Please let me know how to proceed - Hopefully this can be fixed in time for release. To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager-openvpn/+bug/1629611/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1637174] [NEW] totem could not play music or video files
Public bug reported: 1) Description: Ubuntu 16.04.1 LTS Release:16.04 2) totem: Installed: 3.18.1-1ubuntu4 Candidate: 3.18.1-1ubuntu4 Version table: *** 3.18.1-1ubuntu4 500 500 http://sl.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 500 http://cz.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status 3.10.1-1ubuntu4 500 500 http://us.archive.ubuntu.com/ubuntu trusty/main amd64 Packages 3) totem should play audio and video files 4) it is asking for installation of plugins; once i click installed nothing happen after. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: libgstreamer1.0-0 1.8.2-1~ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21 Uname: Linux 4.4.0-45-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity Date: Thu Oct 27 12:39:18 2016 InstallationDate: Installed on 2016-06-17 (132 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) SourcePackage: gstreamer1.0 UpgradeStatus: Upgraded to xenial on 2016-08-04 (83 days ago) ** Affects: gstreamer1.0 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gstreamer1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1637174 Title: totem could not play music or video files Status in gstreamer1.0 package in Ubuntu: New Bug description: 1) Description: Ubuntu 16.04.1 LTS Release: 16.04 2) totem: Installed: 3.18.1-1ubuntu4 Candidate: 3.18.1-1ubuntu4 Version table: *** 3.18.1-1ubuntu4 500 500 http://sl.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 500 http://cz.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status 3.10.1-1ubuntu4 500 500 http://us.archive.ubuntu.com/ubuntu trusty/main amd64 Packages 3) totem should play audio and video files 4) it is asking for installation of plugins; once i click installed nothing happen after. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: libgstreamer1.0-0 1.8.2-1~ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21 Uname: Linux 4.4.0-45-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity Date: Thu Oct 27 12:39:18 2016 InstallationDate: Installed on 2016-06-17 (132 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) SourcePackage: gstreamer1.0 UpgradeStatus: Upgraded to xenial on 2016-08-04 (83 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1637174/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1636573] Re: xinit flooding syslog
I have this same problem, but my errors are going to my .xsession-errors file, as I'm starting kodi after logging in instead. Maybe the bug is in kodi? I'm using kodi 17 beta 4, with Ubuntu 16.04 and kodi 16.1 I did not have any problems. -- 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/1636573 Title: xinit flooding syslog Status in xorg package in Ubuntu: Confirmed Bug description: I am using xinit (1.3.4-3ubuntu1) to start an X11 session as follows (kodi is a media center): /usr/bin/xinit /usr/bin/dbus-launch --exit-with-session /usr/bin/kodi- standalone -- :1 -nolisten tcp vt8 This used to work fine with Ubuntu 16.04, but since the upgrade to 16.10 lots of log messages are sent to syslog. They are all repetitions of the following two lines: Oct 24 22:54:50 tiger xinit[26430]: extern "Python": function Cryptography_rand_bytes() called, but @ffi.def_extern() was not called in the current subinterpreter. Returning 0. Oct 24 22:54:50 tiger xinit[26430]: extern "Python": function Cryptography_rand_status() called, but @ffi.def_extern() was not called in the current subinterpreter. Returning 0. These messages amount to >200 GB per day, so this is eating up all the disk space. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xorg 1:7.7+13ubuntu4 ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0 Uname: Linux 4.8.0-22-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: KDE Date: Tue Oct 25 18:41:22 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2012-01-06 (1753 days ago) InstallationMedia: Kubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to yakkety on 2016-10-13 (11 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1636573/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp