[Desktop-packages] [Bug 1117944] Re: intltool confused by separate build-dir
Last update in the intltool code repo was on 2015-03-09. A year ago. Guess it's unmaintained upstream. Funny that upstream is right here on LP as well... ** Also affects: intltool (Ubuntu) Importance: Undecided Status: New ** Tags added: wily xenial ** Tags added: patch -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to intltool in Ubuntu. https://bugs.launchpad.net/bugs/1117944 Title: intltool confused by separate build-dir Status in intltool: New Status in intltool package in Ubuntu: New Bug description: systemd uses 'intltool-update -m' from intltoolize in its 'make check'. $(top_srcdir)/po/POTFILES.skip contains the name of a generated file (src/core/org.freedesktop.systemd1.policy.in), which will be generated as $(top_builddir)/src/core/org.freedesktop.systemd1.policy.in. If $(builddir)==$(srcdir) than everything works fine. When they are different, there's no way to instruct intltool-update to skip the file. Since the name of the build directory is not known and can be arbitrary, there should be a way to instruct intltool-update to ignore files relative to the $(top_builddir), or something like that. One option would be to turn the file list into a list of globs (**/src/core/org.freedesktop.systemd1.policy.in would work perfectly in our case). To manage notifications about this bug go to: https://bugs.launchpad.net/intltool/+bug/1117944/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1117944] Re: intltool confused by separate build-dir
** Changed in: intltool Status: New => Confirmed ** Changed in: intltool (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to intltool in Ubuntu. https://bugs.launchpad.net/bugs/1117944 Title: intltool confused by separate build-dir Status in intltool: Confirmed Status in intltool package in Ubuntu: Confirmed Bug description: systemd uses 'intltool-update -m' from intltoolize in its 'make check'. $(top_srcdir)/po/POTFILES.skip contains the name of a generated file (src/core/org.freedesktop.systemd1.policy.in), which will be generated as $(top_builddir)/src/core/org.freedesktop.systemd1.policy.in. If $(builddir)==$(srcdir) than everything works fine. When they are different, there's no way to instruct intltool-update to skip the file. Since the name of the build directory is not known and can be arbitrary, there should be a way to instruct intltool-update to ignore files relative to the $(top_builddir), or something like that. One option would be to turn the file list into a list of globs (**/src/core/org.freedesktop.systemd1.policy.in would work perfectly in our case). To manage notifications about this bug go to: https://bugs.launchpad.net/intltool/+bug/1117944/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1540811] Re: [GDK] patch - avoid integer overflow when allocating a large block of memory
Thank you guys! Hope someone from Debian maintainers will take care of it as well... -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1540811 Title: [GDK] patch - avoid integer overflow when allocating a large block of memory Status in GTK+: Fix Released Status in gtk+2.0 package in Ubuntu: Fix Released Status in gtk+3.0 package in Ubuntu: Fix Released Status in gtk+2.0 source package in Precise: Fix Released Status in gtk+3.0 source package in Precise: Fix Released Status in gtk+2.0 source package in Trusty: Fix Released Status in gtk+3.0 source package in Trusty: Fix Released Status in gtk+2.0 source package in Wily: Fix Released Status in gtk+3.0 source package in Wily: Fix Released Status in gtk+2.0 source package in Xenial: Fix Released Status in gtk+3.0 source package in Xenial: Fix Released Status in gtk+2.0 package in Debian: Confirmed Bug description: [Impact] Due to a logic error, an attempt to allocate a large block of memory fails in gdk_cairo_set_source_pixbuf, leading to a crash of the app that called it, for example, eom [1]. This issue had been fixed [2] in GTK+3, but GTK+2 apps that use the mentioned function still crash when trying to allocate a lot of memory. An example of such app is eom (Eye of MATE), an image viewer, which crashes when trying to load a large image. I propose fixing it in current Ubuntu releases with the patch which fixes the crash. The debdiffs are in the attachments in the comments below. [Test Case] Steps to reproduce: 1. Have a 64-bit installation of Ubuntu. 2. Install eom if it isn't installed. 3. Download the archive from the attachment of this post and unpack it. (Firefox doesn't allow me to upload image as is - tries to make thumbnail of it right in the file open dialog, then crashes.) 4. Open the unpacked image (27000_27000_1437947845.png) in eom. 5. eom crashes. The full backtrace is at [3]. You'll also see an error message: "failed to allocate 18446744072330584320 bytes". This huge number appears due to overflow during multiplication of two 32-bit signed integers. In the patch, this error is avoided by using a different memory allocation function. [Regression Potential] After several months of testing the patch in Debian Jessie, Debian Testing and Ubuntu 14.04, I haven't noticed any regressions. [1] https://github.com/mate-desktop/eom/issues/93 [2] https://git.gnome.org/browse/gtk+/commit?id=894b1ae76a32720f4bb3d39cf460402e3ce331d6 [3] https://github.com/mate-desktop/eom/issues/93#issuecomment-141035799 To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1540811/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1540811] Re: [GDK] patch - avoid integer overflow when allocating a large block of memory
** Attachment added: "debdiff with the fix for Trusty" https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1540811/+attachment/4561947/+files/gtk2-gdk-trusty-debdiff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1540811 Title: [GDK] patch - avoid integer overflow when allocating a large block of memory Status in gtk+2.0 package in Ubuntu: New Status in gtk+2.0 package in Debian: Unknown Bug description: [Impact] Due to a logic error, an attempt to allocate a large block of memory fails in gdk_cairo_set_source_pixbuf, leading to a crash of the app that called it, for example, eom [1]. This issue had been fixed [2] in GTK+3, but GTK+2 apps that use the mentioned function still crash when trying to allocate a lot of memory. An example of such app is eom (Eye of MATE), an image viewer, which crashes when trying to load a large image. I propose fixing it in current Ubuntu releases with the patch which fixes the crash. The debdiffs are in the attachments in the comments below. [Test Case] Steps to reproduce: 1. Have a 64-bit installation of Ubuntu. 2. Install eom if it isn't installed. 3. Download the archive from the attachment of this post and unpack it. (Firefox doesn't allow me to upload image as is - tries to make thumbnail of it right in the file open dialog, then crashes.) 4. Open the unpacked image (27000_27000_1437947845.png) in eom. 5. eom crashes. The full backtrace is at [3]. You'll also see an error message: "failed to allocate 18446744072330584320 bytes". This huge number appears due to overflow during multiplication of two 32-bit signed integers. In the patch, this error is avoided by using a different memory allocation function. [Regression Potential] After several months of testing the patch in Debian Jessie, Debian Testing and Ubuntu 14.04, I haven't noticed any regressions. [1] https://github.com/mate-desktop/eom/issues/93 [2] https://git.gnome.org/browse/gtk+/commit?id=894b1ae76a32720f4bb3d39cf460402e3ce331d6 [3] https://github.com/mate-desktop/eom/issues/93#issuecomment-141035799 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1540811/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1540811] [NEW] [GDK] patch - avoid integer overflow when allocating a large block of memory
Public bug reported: [Impact] Due to a logic error, an attempt to allocate a large block of memory fails in gdk_cairo_set_source_pixbuf, leading to a crash of the app that called it, for example, eom [1]. This issue had been fixed [2] in GTK+3, but GTK+2 apps that use the mentioned function still crash when trying to allocate a lot of memory. An example of such app is eom (Eye of MATE), an image viewer, which crashes when trying to load a large image. I propose fixing it in current Ubuntu releases with the patch which fixes the crash. The debdiffs are in the attachments in the comments below. [Test Case] Steps to reproduce: 1. Have a 64-bit installation of Ubuntu. 2. Install eom if it isn't installed. 3. Download the archive from the attachment of this post and unpack it. (Firefox doesn't allow me to upload image as is - tries to make thumbnail of it right in the file open dialog, then crashes.) 4. Open the unpacked image (27000_27000_1437947845.png) in eom. 5. eom crashes. The full backtrace is at [3]. You'll also see an error message: "failed to allocate 18446744072330584320 bytes". This huge number appears due to overflow during multiplication of two 32-bit signed integers. In the patch, this error is avoided by using a different memory allocation function. [Regression Potential] After several months of testing the patch in Debian Jessie, Debian Testing and Ubuntu 14.04, I haven't noticed any regressions. [1] https://github.com/mate-desktop/eom/issues/93 [2] https://git.gnome.org/browse/gtk+/commit?id=894b1ae76a32720f4bb3d39cf460402e3ce331d6 [3] https://github.com/mate-desktop/eom/issues/93#issuecomment-141035799 ** Affects: gtk+2.0 (Ubuntu) Importance: Undecided Status: New ** Affects: gtk+2.0 (Debian) Importance: Unknown Status: Unknown ** Tags: precise trusty wily xenial ** Attachment added: "large image for reproducing the issue" https://bugs.launchpad.net/bugs/1540811/+attachment/4561945/+files/image.tar -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1540811 Title: [GDK] patch - avoid integer overflow when allocating a large block of memory Status in gtk+2.0 package in Ubuntu: New Status in gtk+2.0 package in Debian: Unknown Bug description: [Impact] Due to a logic error, an attempt to allocate a large block of memory fails in gdk_cairo_set_source_pixbuf, leading to a crash of the app that called it, for example, eom [1]. This issue had been fixed [2] in GTK+3, but GTK+2 apps that use the mentioned function still crash when trying to allocate a lot of memory. An example of such app is eom (Eye of MATE), an image viewer, which crashes when trying to load a large image. I propose fixing it in current Ubuntu releases with the patch which fixes the crash. The debdiffs are in the attachments in the comments below. [Test Case] Steps to reproduce: 1. Have a 64-bit installation of Ubuntu. 2. Install eom if it isn't installed. 3. Download the archive from the attachment of this post and unpack it. (Firefox doesn't allow me to upload image as is - tries to make thumbnail of it right in the file open dialog, then crashes.) 4. Open the unpacked image (27000_27000_1437947845.png) in eom. 5. eom crashes. The full backtrace is at [3]. You'll also see an error message: "failed to allocate 18446744072330584320 bytes". This huge number appears due to overflow during multiplication of two 32-bit signed integers. In the patch, this error is avoided by using a different memory allocation function. [Regression Potential] After several months of testing the patch in Debian Jessie, Debian Testing and Ubuntu 14.04, I haven't noticed any regressions. [1] https://github.com/mate-desktop/eom/issues/93 [2] https://git.gnome.org/browse/gtk+/commit?id=894b1ae76a32720f4bb3d39cf460402e3ce331d6 [3] https://github.com/mate-desktop/eom/issues/93#issuecomment-141035799 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1540811/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1540811] Re: [GDK] patch - avoid integer overflow when allocating a large block of memory
** Attachment added: "debdiff with the fix for Precise" https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1540811/+attachment/4561946/+files/gtk2-gdk-precise-debdiff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1540811 Title: [GDK] patch - avoid integer overflow when allocating a large block of memory Status in gtk+2.0 package in Ubuntu: New Status in gtk+2.0 package in Debian: Unknown Bug description: [Impact] Due to a logic error, an attempt to allocate a large block of memory fails in gdk_cairo_set_source_pixbuf, leading to a crash of the app that called it, for example, eom [1]. This issue had been fixed [2] in GTK+3, but GTK+2 apps that use the mentioned function still crash when trying to allocate a lot of memory. An example of such app is eom (Eye of MATE), an image viewer, which crashes when trying to load a large image. I propose fixing it in current Ubuntu releases with the patch which fixes the crash. The debdiffs are in the attachments in the comments below. [Test Case] Steps to reproduce: 1. Have a 64-bit installation of Ubuntu. 2. Install eom if it isn't installed. 3. Download the archive from the attachment of this post and unpack it. (Firefox doesn't allow me to upload image as is - tries to make thumbnail of it right in the file open dialog, then crashes.) 4. Open the unpacked image (27000_27000_1437947845.png) in eom. 5. eom crashes. The full backtrace is at [3]. You'll also see an error message: "failed to allocate 18446744072330584320 bytes". This huge number appears due to overflow during multiplication of two 32-bit signed integers. In the patch, this error is avoided by using a different memory allocation function. [Regression Potential] After several months of testing the patch in Debian Jessie, Debian Testing and Ubuntu 14.04, I haven't noticed any regressions. [1] https://github.com/mate-desktop/eom/issues/93 [2] https://git.gnome.org/browse/gtk+/commit?id=894b1ae76a32720f4bb3d39cf460402e3ce331d6 [3] https://github.com/mate-desktop/eom/issues/93#issuecomment-141035799 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1540811/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1540811] Re: [GDK] patch - avoid integer overflow when allocating a large block of memory
** Attachment added: "debdiff with the fix for Xenial" https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1540811/+attachment/4561950/+files/gtk2-gdk-xenial-debdiff ** Bug watch added: Debian Bug tracker #799275 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=799275 ** Also affects: gtk+2.0 (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=799275 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1540811 Title: [GDK] patch - avoid integer overflow when allocating a large block of memory Status in gtk+2.0 package in Ubuntu: New Status in gtk+2.0 package in Debian: Unknown Bug description: [Impact] Due to a logic error, an attempt to allocate a large block of memory fails in gdk_cairo_set_source_pixbuf, leading to a crash of the app that called it, for example, eom [1]. This issue had been fixed [2] in GTK+3, but GTK+2 apps that use the mentioned function still crash when trying to allocate a lot of memory. An example of such app is eom (Eye of MATE), an image viewer, which crashes when trying to load a large image. I propose fixing it in current Ubuntu releases with the patch which fixes the crash. The debdiffs are in the attachments in the comments below. [Test Case] Steps to reproduce: 1. Have a 64-bit installation of Ubuntu. 2. Install eom if it isn't installed. 3. Download the archive from the attachment of this post and unpack it. (Firefox doesn't allow me to upload image as is - tries to make thumbnail of it right in the file open dialog, then crashes.) 4. Open the unpacked image (27000_27000_1437947845.png) in eom. 5. eom crashes. The full backtrace is at [3]. You'll also see an error message: "failed to allocate 18446744072330584320 bytes". This huge number appears due to overflow during multiplication of two 32-bit signed integers. In the patch, this error is avoided by using a different memory allocation function. [Regression Potential] After several months of testing the patch in Debian Jessie, Debian Testing and Ubuntu 14.04, I haven't noticed any regressions. [1] https://github.com/mate-desktop/eom/issues/93 [2] https://git.gnome.org/browse/gtk+/commit?id=894b1ae76a32720f4bb3d39cf460402e3ce331d6 [3] https://github.com/mate-desktop/eom/issues/93#issuecomment-141035799 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1540811/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1540811] Re: [GDK] patch - avoid integer overflow when allocating a large block of memory
** Attachment added: "debdiff with the fix for Wily" https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1540811/+attachment/4561948/+files/gtk2-gdk-wily-debdiff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1540811 Title: [GDK] patch - avoid integer overflow when allocating a large block of memory Status in gtk+2.0 package in Ubuntu: New Status in gtk+2.0 package in Debian: Unknown Bug description: [Impact] Due to a logic error, an attempt to allocate a large block of memory fails in gdk_cairo_set_source_pixbuf, leading to a crash of the app that called it, for example, eom [1]. This issue had been fixed [2] in GTK+3, but GTK+2 apps that use the mentioned function still crash when trying to allocate a lot of memory. An example of such app is eom (Eye of MATE), an image viewer, which crashes when trying to load a large image. I propose fixing it in current Ubuntu releases with the patch which fixes the crash. The debdiffs are in the attachments in the comments below. [Test Case] Steps to reproduce: 1. Have a 64-bit installation of Ubuntu. 2. Install eom if it isn't installed. 3. Download the archive from the attachment of this post and unpack it. (Firefox doesn't allow me to upload image as is - tries to make thumbnail of it right in the file open dialog, then crashes.) 4. Open the unpacked image (27000_27000_1437947845.png) in eom. 5. eom crashes. The full backtrace is at [3]. You'll also see an error message: "failed to allocate 18446744072330584320 bytes". This huge number appears due to overflow during multiplication of two 32-bit signed integers. In the patch, this error is avoided by using a different memory allocation function. [Regression Potential] After several months of testing the patch in Debian Jessie, Debian Testing and Ubuntu 14.04, I haven't noticed any regressions. [1] https://github.com/mate-desktop/eom/issues/93 [2] https://git.gnome.org/browse/gtk+/commit?id=894b1ae76a32720f4bb3d39cf460402e3ce331d6 [3] https://github.com/mate-desktop/eom/issues/93#issuecomment-141035799 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1540811/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1525170] Re: caja crashed with signal 7
** Package changed: caja (Ubuntu) => gvfs (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1525170 Title: caja crashed with signal 7 Status in gvfs package in Ubuntu: New Bug description: crashed while starting thunderbird ProblemType: Crash DistroRelease: Ubuntu 15.10 Package: caja 1.10.4-1 ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6 Uname: Linux 4.2.0-19-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CurrentDesktop: MATE Date: Fri Dec 11 11:57:59 2015 ExecutablePath: /usr/bin/caja JournalErrors: No journal files were found. -- No entries -- ProcCmdline: caja ProcEnviron: LANGUAGE=de_DE PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash Signal: 7 SourcePackage: caja StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/gio/modules/libgvfsdbus.so ?? () from /usr/lib/x86_64-linux-gnu/gio/modules/libgvfsdbus.so ?? () from /usr/lib/x86_64-linux-gnu/gio/modules/libgvfsdbus.so ?? () from /usr/lib/x86_64-linux-gnu/gio/modules/libgvfsdbus.so ?? () from /usr/lib/x86_64-linux-gnu/gio/modules/libgvfsdbus.so Title: caja crashed with signal 7 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: employee rzcip-m sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1525170/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1404715] Re: evince crashed with SIGSEGV
That's not an update for Trusty. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cairo in Ubuntu. https://bugs.launchpad.net/bugs/1404715 Title: evince crashed with SIGSEGV Status in cairo: Fix Released Status in cairo package in Ubuntu: Fix Released Status in cairo package in Debian: New Bug description: While browsing http://www.eurail.com/sites/eurail.com/files/documents/eurail_railway_map_2014.pdf ProblemType: Crash DistroRelease: Ubuntu 14.10 Package: evince 3.14.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-29.39-generic 3.16.7-ckt2 Uname: Linux 3.16.0-29-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CrashCounter: 1 CurrentDesktop: Unity Date: Sun Dec 21 20:35:56 2014 ExecutablePath: /usr/bin/evince ExecutableTimestamp: 1413470384 InstallationDate: Installed on 2014-12-09 (11 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) KernLog: ProcCmdline: evince /tmp/eurail_railway_map_2014.pdf ProcCwd: /home/mathieu ProcEnviron: XDG_RUNTIME_DIR= SHELL=/bin/bash LANGUAGE=fr_FR PATH=(custom, no user) LANG=fr_FR.UTF-8 SegvAnalysis: Segfault happened at: 0x7f679b821fd5:cmpq $0x0,0x30(%r13) PC (0x7f679b821fd5) ok source "$0x0" ok destination "0x30(%r13)" (0x0030) not located in a known VMA region (needed writable region)! Stack memory exhausted (SP below stack segment) SegvReason: writing NULL VMA Signal: 11 SourcePackage: evince StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libcairo.so.2 ?? () from /usr/lib/x86_64-linux-gnu/libcairo.so.2 ?? () from /usr/lib/x86_64-linux-gnu/libcairo.so.2 ?? () from /usr/lib/x86_64-linux-gnu/libcairo.so.2 ?? () from /usr/lib/x86_64-linux-gnu/libcairo.so.2 Title: evince crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/cairo/+bug/1404715/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1495943] Re: gvfs-trash doesn't add "trash::" attrs to file which is moved to Trash
Ok, all good now :) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1495943 Title: gvfs-trash doesn't add "trash::" attrs to file which is moved to Trash Status in GLib: Fix Released Status in glib2.0 package in Ubuntu: Fix Released Status in gvfs package in Ubuntu: Fix Released Status in glib2.0 package in Debian: Fix Released Bug description: [System] Ubuntu MATE 15.10, fully updated. [Steps to reproduce] 1. Create an empty file: touch ~/test 2. Move it to trash: gvfs-trash ~/test 3. Launch some file manager, browse Trash folder and try to restore the file. I've tested it with the following file managers: Caja, Nemo, Nautilus and Thunar. [Expected result] The file should be restored to its original location. [What happens instead] The file manager complains that it can't determine the original location of the file, and so doesn't restore it. [Details] When moving file to Trash, gvfs-trash does not add trash::orig-path and trash::deletion-date attributes to it. Without that the file manager can't determine the original location of the file, and hence can't restore it. You can check the file attributes by printing the moved file's info: gvfs-info trash:///test [Regression description] Restoring the files has been working fine in Ubuntu 14.04 and 15.04. This bug appeared only in 15.10, so it's a regression. You can see the gvfs-info output from 15.04 and 15.10 in the attachments below. To manage notifications about this bug go to: https://bugs.launchpad.net/glib/+bug/1495943/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1495943] Re: gvfs-trash doesn't add "trash::" attrs to file which is moved to Trash
Thanks, restoring from trash works now. Not sure why the linked Debian bug isn't closed yet... the fix made it into Unstable before Wily anyway. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1495943 Title: gvfs-trash doesn't add "trash::" attrs to file which is moved to Trash Status in GLib: Fix Released Status in glib2.0 package in Ubuntu: Fix Released Status in gvfs package in Ubuntu: Fix Released Status in glib2.0 package in Debian: Confirmed Bug description: [System] Ubuntu MATE 15.10, fully updated. [Steps to reproduce] 1. Create an empty file: touch ~/test 2. Move it to trash: gvfs-trash ~/test 3. Launch some file manager, browse Trash folder and try to restore the file. I've tested it with the following file managers: Caja, Nemo, Nautilus and Thunar. [Expected result] The file should be restored to its original location. [What happens instead] The file manager complains that it can't determine the original location of the file, and so doesn't restore it. [Details] When moving file to Trash, gvfs-trash does not add trash::orig-path and trash::deletion-date attributes to it. Without that the file manager can't determine the original location of the file, and hence can't restore it. You can check the file attributes by printing the moved file's info: gvfs-info trash:///test [Regression description] Restoring the files has been working fine in Ubuntu 14.04 and 15.04. This bug appeared only in 15.10, so it's a regression. You can see the gvfs-info output from 15.04 and 15.10 in the attachments below. To manage notifications about this bug go to: https://bugs.launchpad.net/glib/+bug/1495943/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1495943] Re: gvfs-trash doesn't add "trash::" attrs to file which is moved to Trash
** No longer affects: glib2.0 (Debian) ** Also affects: glib2.0 (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=800941 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1495943 Title: gvfs-trash doesn't add "trash::" attrs to file which is moved to Trash Status in GLib: Incomplete Status in glib2.0 package in Ubuntu: Confirmed Status in gvfs package in Ubuntu: Confirmed Status in glib2.0 package in Debian: Unknown Bug description: [System] Ubuntu MATE 15.10, fully updated. [Steps to reproduce] 1. Create an empty file: touch ~/test 2. Move it to trash: gvfs-trash ~/test 3. Launch some file manager, browse Trash folder and try to restore the file. I've tested it with the following file managers: Caja, Nemo, Nautilus and Thunar. [Expected result] The file should be restored to its original location. [What happens instead] The file manager complains that it can't determine the original location of the file, and so doesn't restore it. [Details] When moving file to Trash, gvfs-trash does not add trash::orig-path and trash::deletion-date attributes to it. Without that the file manager can't determine the original location of the file, and hence can't restore it. You can check the file attributes by printing the moved file's info: gvfs-info trash:///test [Regression description] Restoring the files has been working fine in Ubuntu 14.04 and 15.04. This bug appeared only in 15.10, so it's a regression. You can see the gvfs-info output from 15.04 and 15.10 in the attachments below. To manage notifications about this bug go to: https://bugs.launchpad.net/glib/+bug/1495943/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1495943] Re: gvfs-trash doesn't add "trash::" attrs to file which is moved to Trash
** Bug watch added: Debian Bug tracker #800941 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=800941 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1495943 Title: gvfs-trash doesn't add "trash::" attrs to file which is moved to Trash Status in GLib: Incomplete Status in glib2.0 package in Ubuntu: Confirmed Status in gvfs package in Ubuntu: Confirmed Status in glib2.0 package in Debian: Unknown Bug description: [System] Ubuntu MATE 15.10, fully updated. [Steps to reproduce] 1. Create an empty file: touch ~/test 2. Move it to trash: gvfs-trash ~/test 3. Launch some file manager, browse Trash folder and try to restore the file. I've tested it with the following file managers: Caja, Nemo, Nautilus and Thunar. [Expected result] The file should be restored to its original location. [What happens instead] The file manager complains that it can't determine the original location of the file, and so doesn't restore it. [Details] When moving file to Trash, gvfs-trash does not add trash::orig-path and trash::deletion-date attributes to it. Without that the file manager can't determine the original location of the file, and hence can't restore it. You can check the file attributes by printing the moved file's info: gvfs-info trash:///test [Regression description] Restoring the files has been working fine in Ubuntu 14.04 and 15.04. This bug appeared only in 15.10, so it's a regression. You can see the gvfs-info output from 15.04 and 15.10 in the attachments below. To manage notifications about this bug go to: https://bugs.launchpad.net/glib/+bug/1495943/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1495943] Re: gvfs-trash doesn't add "trash::" attrs to file which is moved to Trash
** Bug watch added: Debian Bug tracker #800941 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=800941 ** Also affects: glib2.0 (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=800941 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1495943 Title: gvfs-trash doesn't add "trash::" attrs to file which is moved to Trash Status in GLib: Incomplete Status in glib2.0 package in Ubuntu: Confirmed Status in gvfs package in Ubuntu: Confirmed Status in glib2.0 package in Debian: Unknown Bug description: [System] Ubuntu MATE 15.10, fully updated. [Steps to reproduce] 1. Create an empty file: touch ~/test 2. Move it to trash: gvfs-trash ~/test 3. Launch some file manager, browse Trash folder and try to restore the file. I've tested it with the following file managers: Caja, Nemo, Nautilus and Thunar. [Expected result] The file should be restored to its original location. [What happens instead] The file manager complains that it can't determine the original location of the file, and so doesn't restore it. [Details] When moving file to Trash, gvfs-trash does not add trash::orig-path and trash::deletion-date attributes to it. Without that the file manager can't determine the original location of the file, and hence can't restore it. You can check the file attributes by printing the moved file's info: gvfs-info trash:///test [Regression description] Restoring the files has been working fine in Ubuntu 14.04 and 15.04. This bug appeared only in 15.10, so it's a regression. You can see the gvfs-info output from 15.04 and 15.10 in the attachments below. To manage notifications about this bug go to: https://bugs.launchpad.net/glib/+bug/1495943/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1493587] Re: Trash does not restore files
*** This bug is a duplicate of bug 1495943 *** https://bugs.launchpad.net/bugs/1495943 ** This bug is no longer a duplicate of bug 1492324 Trash in nautilus could not restore test folder ** This bug has been marked a duplicate of bug 1495943 gvfs-trash doesn't add "trash::" attrs to file which is moved to Trash -- 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/1493587 Title: Trash does not restore files Status in nautilus package in Ubuntu: New Bug description: For some reason, files inside "Trash" cannot be restored. Whenever I try restoring a file that was deleted or moved to trash, I get this error, "Could not determine original location of 'My file'. The item cannot be restored from trash". nautilus: Installed: 1:3.14.2-0ubuntu10 Candidate: 1:3.14.2-0ubuntu10 Version table: *** 1:3.14.2-0ubuntu10 0 500 http://us.archive.ubuntu.com/ubuntu/ wily/main i386 Packages 100 /var/lib/dpkg/status Distributor ID: Ubuntu Description: Ubuntu Wily Werewolf (development branch) Release: 15.10 Codename: wily I expected files in trash can be restored to their original location. Trash was unable to restore files. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: nautilus 1:3.14.2-0ubuntu10 ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3 Uname: Linux 4.1.0-3-generic i686 ApportVersion: 2.18-0ubuntu9 Architecture: i386 Date: Tue Sep 8 18:56:44 2015 GsettingsChanges: InstallationDate: Installed on 2015-05-18 (113 days ago) InstallationMedia: Lubuntu 15.10 "Wily Werewolf" - Alpha i386 (20150517) ProcEnviron: LANGUAGE=en_US TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1493587/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1492324] Re: Trash in nautilus could not restore test folder
*** This bug is a duplicate of bug 1495943 *** https://bugs.launchpad.net/bugs/1495943 ** This bug has been marked a duplicate of bug 1495943 gvfs-trash doesn't add "trash::" attrs to file which is moved to Trash -- 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/1492324 Title: Trash in nautilus could not restore test folder Status in nautilus package in Ubuntu: New Bug description: While running the nautilus testcase for Ubuntu, was unable to restore the "test" folder from trash:/// as instructed. Nautilus stated that it could not determine the original local of the file. I tried creating the test folder in "Documents" to see if the problem existed there. It does. Distributor ID: Ubuntu Description: Ubuntu Wily Werewolf (development branch) Release: 15.10 Codename: wily nautilus: Installed: 1:3.14.2-0ubuntu10 Candidate: 1:3.14.2-0ubuntu10 Version table: *** 1:3.14.2-0ubuntu10 0 500 http://us.archive.ubuntu.com/ubuntu/ wily/main i386 Packages 100 /var/lib/dpkg/status Expected Nautilus to restore folder in "trash" Nautilus failed to restore folder do to not determining the original location. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: nautilus 1:3.14.2-0ubuntu10 ProcVersionSignature: Ubuntu 3.19.0-22.22-generic 3.19.8-ckt1 Uname: Linux 3.19.0-22-generic i686 ApportVersion: 2.18-0ubuntu9 Architecture: i386 Date: Fri Sep 4 11:12:09 2015 GsettingsChanges: InstallationDate: Installed on 2015-05-18 (109 days ago) InstallationMedia: Lubuntu 15.10 "Wily Werewolf" - Alpha i386 (20150517) ProcEnviron: LANGUAGE=en_US TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1492324/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1351890] Re: Changing external screen resolution with dual monitors
Thanks! :) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1351890 Title: Changing external screen resolution with dual monitors Status in GTK+: Fix Released Status in ubuntu-mate: Fix Released Status in gtk+2.0 package in Ubuntu: Fix Released Status in mate-control-center package in Ubuntu: Fix Released Status in gtk+2.0 source package in Precise: Fix Released Status in gtk+2.0 source package in Trusty: Fix Released Status in gtk+2.0 package in Debian: Fix Released Bug description: [Impact] Due to a bug in GTK+2, mate-display-properties crashes when the screen resolution is changed *outside* of it (e.g. by changing the resolution not via that app, but somewhere else). The attached patches fix the issue in GTK+2 and prevent crashing of m-d-p. Since this issue caused much inconvenience for users, the fix should be backported to all current stable releases of Ubuntu. [Test Case] The easiest way to reproduce it is via Virtualbox: 1. Run mate-display-properties in the VM. 2. Make the VM go full-screen. 3. See m-d-p crash. [Regression Potential] After several months of testing the patched version of GTK+2 in Debian Jessie, I found no regressions. I consider the regression risk very low here. There were originally some bugs with a few applications (notably Spotify) crashing. We think we've backported patches to fix that - some refcounting issues - but please check a few apps to see they still work. [ Original report ] Changing extrnal screen resolution with dual mon ProblemType: Crash DistroRelease: Ubuntu 14.10 Package: mate-control-center 1.8.1+dfsg1-4 ProcVersionSignature: Ubuntu 3.16.0-6.11-generic 3.16.0-rc7 Uname: Linux 3.16.0-6-generic i686 ApportVersion: 2.14.5-0ubuntu3 Architecture: i386 CrashCounter: 1 Date: Sun Aug 3 07:09:21 2014 ExecutablePath: /usr/bin/mate-display-properties InstallationDate: Installed on 2014-08-03 (0 days ago) InstallationMedia: Ubuntu MATE 14.10 "Utopic Unicorn" - Alpha i386 (20140731) ProcCmdline: mate-display-properties SegvAnalysis: Skipped: missing required field "Disassembly" Signal: 11 SourcePackage: mate-control-center UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1351890/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1495943] Re: gvfs-trash doesn't add "trash::" attrs to file which is moved to Trash
I've found out that for some reason these "trash::" attributes magically appear if I log out and then log in back (or simply reboot). How come...? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1495943 Title: gvfs-trash doesn't add "trash::" attrs to file which is moved to Trash Status in gvfs package in Ubuntu: Confirmed Bug description: [System] Ubuntu MATE 15.10, fully updated. [Steps to reproduce] 1. Create an empty file: touch ~/test 2. Move it to trash: gvfs-trash ~/test 3. Launch some file manager, browse Trash folder and try to restore the file. I've tested it with the following file managers: Caja, Nemo, Nautilus and Thunar. [Expected result] The file should be restored to its original location. [What happens instead] The file manager complains that it can't determine the original location of the file, and so doesn't restore it. [Details] When moving file to Trash, gvfs-trash does not add trash::orig-path and trash::deletion-date attributes to it. Without that the file manager can't determine the original location of the file, and hence can't restore it. You can check the file attributes by printing the moved file's info: gvfs-info trash:///test [Regression description] Restoring the files has been working fine in Ubuntu 14.04 and 15.04. This bug appeared only in 15.10, so it's a regression. You can see the gvfs-info output from 15.04 and 15.10 in the attachments below. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1495943/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1493587] Re: Trash does not restore files
*** This bug is a duplicate of bug 1492324 *** https://bugs.launchpad.net/bugs/1492324 ** This bug has been marked a duplicate of bug 1492324 Trash in nautilus could not restore test folder -- 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/1493587 Title: Trash does not restore files Status in nautilus package in Ubuntu: New Bug description: For some reason, files inside "Trash" cannot be restored. Whenever I try restoring a file that was deleted or moved to trash, I get this error, "Could not determine original location of 'My file'. The item cannot be restored from trash". nautilus: Installed: 1:3.14.2-0ubuntu10 Candidate: 1:3.14.2-0ubuntu10 Version table: *** 1:3.14.2-0ubuntu10 0 500 http://us.archive.ubuntu.com/ubuntu/ wily/main i386 Packages 100 /var/lib/dpkg/status Distributor ID: Ubuntu Description: Ubuntu Wily Werewolf (development branch) Release: 15.10 Codename: wily I expected files in trash can be restored to their original location. Trash was unable to restore files. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: nautilus 1:3.14.2-0ubuntu10 ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3 Uname: Linux 4.1.0-3-generic i686 ApportVersion: 2.18-0ubuntu9 Architecture: i386 Date: Tue Sep 8 18:56:44 2015 GsettingsChanges: InstallationDate: Installed on 2015-05-18 (113 days ago) InstallationMedia: Lubuntu 15.10 "Wily Werewolf" - Alpha i386 (20150517) ProcEnviron: LANGUAGE=en_US TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1493587/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1495943] Re: gvfs-trash doesn't add "trash::" attrs to file which is moved to Trash
** Attachment added: "gvfs-info log from 15.10 (bad)" https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1495943/+attachment/4465030/+files/trash-15.10.log -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1495943 Title: gvfs-trash doesn't add "trash::" attrs to file which is moved to Trash Status in gvfs package in Ubuntu: New Bug description: [System] Ubuntu MATE 15.10, fully updated. [Steps to reproduce] 1. Create an empty file: touch ~/test 2. Move it to trash: gvfs-trash ~/test 3. Launch some file manager, browse Trash folder and try to restore the file. I've tested it with the following file managers: Caja, Nemo, Nautilus and Thunar. [Expected result] The file should be restored to its original location. [What happens instead] The file manager complains that it can't determine the original location of the file, and so doesn't restore it. [Details] When moving file to Trash, gvfs-trash does not add trash::orig-path and trash::deletion-date attributes to it. Without that the file manager can't determine the original location of the file, and hence can't restore it. You can check the file attributes by printing the moved file's info: gvfs-info trash:///test [Regression description] Restoring the files has been working fine in Ubuntu 14.04 and 15.04. This bug appeared only in 15.10, so it's a regression. You can see the gvfs-info output from 15.04 and 15.10 in the attachments below. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1495943/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1495943] Re: gvfs-trash doesn't add "trash::" attrs to file which is moved to Trash
** Attachment added: "gvfs-info log from 15.04 (good)" https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1495943/+attachment/4465029/+files/trash-15.04.log -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1495943 Title: gvfs-trash doesn't add "trash::" attrs to file which is moved to Trash Status in gvfs package in Ubuntu: New Bug description: [System] Ubuntu MATE 15.10, fully updated. [Steps to reproduce] 1. Create an empty file: touch ~/test 2. Move it to trash: gvfs-trash ~/test 3. Launch some file manager, browse Trash folder and try to restore the file. I've tested it with the following file managers: Caja, Nemo, Nautilus and Thunar. [Expected result] The file should be restored to its original location. [What happens instead] The file manager complains that it can't determine the original location of the file, and so doesn't restore it. [Details] When moving file to Trash, gvfs-trash does not add trash::orig-path and trash::deletion-date attributes to it. Without that the file manager can't determine the original location of the file, and hence can't restore it. You can check the file attributes by printing the moved file's info: gvfs-info trash:///test [Regression description] Restoring the files has been working fine in Ubuntu 14.04 and 15.04. This bug appeared only in 15.10, so it's a regression. You can see the gvfs-info output from 15.04 and 15.10 in the attachments below. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1495943/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1495943] [NEW] gvfs-trash doesn't add "trash::" attrs to file which is moved to Trash
Public bug reported: [System] Ubuntu MATE 15.10, fully updated. [Steps to reproduce] 1. Create an empty file: touch ~/test 2. Move it to trash: gvfs-trash ~/test 3. Launch some file manager, browse Trash folder and try to restore the file. I've tested it with the following file managers: Caja, Nemo, Nautilus and Thunar. [Expected result] The file should be restored to its original location. [What happens instead] The file manager complains that it can't determine the original location of the file, and so doesn't restore it. [Details] When moving file to Trash, gvfs-trash does not add trash::orig-path and trash::deletion-date attributes to it. Without that the file manager can't determine the original location of the file, and hence can't restore it. You can check the file attributes by printing the moved file's info: gvfs-info trash:///test [Regression description] Restoring the files has been working fine in Ubuntu 14.04 and 15.04. This bug appeared only in 15.10, so it's a regression. You can see the gvfs-info output from 15.04 and 15.10 in the attachments below. ** Affects: gvfs (Ubuntu) Importance: Undecided Status: New ** Tags: trash wily -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1495943 Title: gvfs-trash doesn't add "trash::" attrs to file which is moved to Trash Status in gvfs package in Ubuntu: New Bug description: [System] Ubuntu MATE 15.10, fully updated. [Steps to reproduce] 1. Create an empty file: touch ~/test 2. Move it to trash: gvfs-trash ~/test 3. Launch some file manager, browse Trash folder and try to restore the file. I've tested it with the following file managers: Caja, Nemo, Nautilus and Thunar. [Expected result] The file should be restored to its original location. [What happens instead] The file manager complains that it can't determine the original location of the file, and so doesn't restore it. [Details] When moving file to Trash, gvfs-trash does not add trash::orig-path and trash::deletion-date attributes to it. Without that the file manager can't determine the original location of the file, and hence can't restore it. You can check the file attributes by printing the moved file's info: gvfs-info trash:///test [Regression description] Restoring the files has been working fine in Ubuntu 14.04 and 15.04. This bug appeared only in 15.10, so it's a regression. You can see the gvfs-info output from 15.04 and 15.10 in the attachments below. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1495943/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1351890] Re: Changing external screen resolution with dual monitors
Looks good in Trusty. Since Precise has the fix in -proposed already as well, tagging it as verification-done. ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1351890 Title: Changing external screen resolution with dual monitors Status in GTK+: Fix Released Status in ubuntu-mate: Fix Released Status in gtk+2.0 package in Ubuntu: Fix Released Status in mate-control-center package in Ubuntu: Fix Released Status in gtk+2.0 source package in Precise: Fix Committed Status in gtk+2.0 source package in Trusty: Fix Committed Status in gtk+2.0 package in Debian: Fix Released Bug description: [Impact] Due to a bug in GTK+2, mate-display-properties crashes when the screen resolution is changed *outside* of it (e.g. by changing the resolution not via that app, but somewhere else). The attached patches fix the issue in GTK+2 and prevent crashing of m-d-p. Since this issue caused much inconvenience for users, the fix should be backported to all current stable releases of Ubuntu. [Test Case] The easiest way to reproduce it is via Virtualbox: 1. Run mate-display-properties in the VM. 2. Make the VM go full-screen. 3. See m-d-p crash. [Regression Potential] After several months of testing the patched version of GTK+2 in Debian Jessie, I found no regressions. I consider the regression risk very low here. There were originally some bugs with a few applications (notably Spotify) crashing. We think we've backported patches to fix that - some refcounting issues - but please check a few apps to see they still work. [ Original report ] Changing extrnal screen resolution with dual mon ProblemType: Crash DistroRelease: Ubuntu 14.10 Package: mate-control-center 1.8.1+dfsg1-4 ProcVersionSignature: Ubuntu 3.16.0-6.11-generic 3.16.0-rc7 Uname: Linux 3.16.0-6-generic i686 ApportVersion: 2.14.5-0ubuntu3 Architecture: i386 CrashCounter: 1 Date: Sun Aug 3 07:09:21 2014 ExecutablePath: /usr/bin/mate-display-properties InstallationDate: Installed on 2014-08-03 (0 days ago) InstallationMedia: Ubuntu MATE 14.10 "Utopic Unicorn" - Alpha i386 (20140731) ProcCmdline: mate-display-properties SegvAnalysis: Skipped: missing required field "Disassembly" Signal: 11 SourcePackage: mate-control-center UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1351890/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1351890] Re: Changing external screen resolution with dual monitors
Guys, please do something for Trusty... -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1351890 Title: Changing external screen resolution with dual monitors Status in GTK+: Fix Released Status in ubuntu-mate: Fix Released Status in gtk+2.0 package in Ubuntu: Fix Released Status in mate-control-center package in Ubuntu: Fix Released Status in gtk+2.0 source package in Precise: Fix Committed Status in gtk+2.0 source package in Trusty: In Progress Status in gtk+2.0 package in Debian: Fix Released Bug description: [Impact] Due to a bug in GTK+2, mate-display-properties crashes when the screen resolution is changed *outside* of it (e.g. by changing the resolution not via that app, but somewhere else). The attached patches fix the issue in GTK+2 and prevent crashing of m-d-p. Since this issue caused much inconvenience for users, the fix should be backported to all current stable releases of Ubuntu. [Test Case] The easiest way to reproduce it is via Virtualbox: 1. Run mate-display-properties in the VM. 2. Make the VM go full-screen. 3. See m-d-p crash. [Regression Potential] After several months of testing the patched version of GTK+2 in Debian Jessie, I found no regressions. I consider the regression risk very low here. There were originally some bugs with a few applications (notably Spotify) crashing. We think we've backported patches to fix that - some refcounting issues - but please check a few apps to see they still work. [ Original report ] Changing extrnal screen resolution with dual mon ProblemType: Crash DistroRelease: Ubuntu 14.10 Package: mate-control-center 1.8.1+dfsg1-4 ProcVersionSignature: Ubuntu 3.16.0-6.11-generic 3.16.0-rc7 Uname: Linux 3.16.0-6-generic i686 ApportVersion: 2.14.5-0ubuntu3 Architecture: i386 CrashCounter: 1 Date: Sun Aug 3 07:09:21 2014 ExecutablePath: /usr/bin/mate-display-properties InstallationDate: Installed on 2014-08-03 (0 days ago) InstallationMedia: Ubuntu MATE 14.10 "Utopic Unicorn" - Alpha i386 (20140731) ProcCmdline: mate-display-properties SegvAnalysis: Skipped: missing required field "Disassembly" Signal: 11 SourcePackage: mate-control-center UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1351890/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1351890] Re: Changing external screen resolution with dual monitors
Won't happen, Utopic is EOL since 23 July 2015 https://lists.ubuntu.com/archives/ubuntu-announce/2015-July/000197.html -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1351890 Title: Changing external screen resolution with dual monitors Status in GTK+: Fix Released Status in ubuntu-mate: Fix Released Status in gtk+2.0 package in Ubuntu: Fix Released Status in mate-control-center package in Ubuntu: Fix Released Status in gtk+2.0 source package in Precise: Fix Committed Status in gtk+2.0 source package in Trusty: In Progress Status in gtk+2.0 package in Debian: Fix Released Bug description: [Impact] Due to a bug in GTK+2, mate-display-properties crashes when the screen resolution is changed *outside* of it (e.g. by changing the resolution not via that app, but somewhere else). The attached patches fix the issue in GTK+2 and prevent crashing of m-d-p. Since this issue caused much inconvenience for users, the fix should be backported to all current stable releases of Ubuntu. [Test Case] The easiest way to reproduce it is via Virtualbox: 1. Run mate-display-properties in the VM. 2. Make the VM go full-screen. 3. See m-d-p crash. [Regression Potential] After several months of testing the patched version of GTK+2 in Debian Jessie, I found no regressions. I consider the regression risk very low here. There were originally some bugs with a few applications (notably Spotify) crashing. We think we've backported patches to fix that - some refcounting issues - but please check a few apps to see they still work. [ Original report ] Changing extrnal screen resolution with dual mon ProblemType: Crash DistroRelease: Ubuntu 14.10 Package: mate-control-center 1.8.1+dfsg1-4 ProcVersionSignature: Ubuntu 3.16.0-6.11-generic 3.16.0-rc7 Uname: Linux 3.16.0-6-generic i686 ApportVersion: 2.14.5-0ubuntu3 Architecture: i386 CrashCounter: 1 Date: Sun Aug 3 07:09:21 2014 ExecutablePath: /usr/bin/mate-display-properties InstallationDate: Installed on 2014-08-03 (0 days ago) InstallationMedia: Ubuntu MATE 14.10 Utopic Unicorn - Alpha i386 (20140731) ProcCmdline: mate-display-properties SegvAnalysis: Skipped: missing required field Disassembly Signal: 11 SourcePackage: mate-control-center UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1351890/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1351890] Re: Changing external screen resolution with dual monitors
The fix for Trusty is still in that queue - did something wrong happened? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1351890 Title: Changing external screen resolution with dual monitors Status in GTK+: Fix Released Status in ubuntu-mate: Fix Released Status in gtk+2.0 package in Ubuntu: Fix Released Status in mate-control-center package in Ubuntu: Fix Released Status in gtk+2.0 source package in Precise: Fix Committed Status in gtk+2.0 source package in Trusty: In Progress Status in gtk+2.0 package in Debian: Fix Released Bug description: [Impact] Due to a bug in GTK+2, mate-display-properties crashes when the screen resolution is changed *outside* of it (e.g. by changing the resolution not via that app, but somewhere else). The attached patches fix the issue in GTK+2 and prevent crashing of m-d-p. Since this issue caused much inconvenience for users, the fix should be backported to all current stable releases of Ubuntu. [Test Case] The easiest way to reproduce it is via Virtualbox: 1. Run mate-display-properties in the VM. 2. Make the VM go full-screen. 3. See m-d-p crash. [Regression Potential] After several months of testing the patched version of GTK+2 in Debian Jessie, I found no regressions. I consider the regression risk very low here. There were originally some bugs with a few applications (notably Spotify) crashing. We think we've backported patches to fix that - some refcounting issues - but please check a few apps to see they still work. [ Original report ] Changing extrnal screen resolution with dual mon ProblemType: Crash DistroRelease: Ubuntu 14.10 Package: mate-control-center 1.8.1+dfsg1-4 ProcVersionSignature: Ubuntu 3.16.0-6.11-generic 3.16.0-rc7 Uname: Linux 3.16.0-6-generic i686 ApportVersion: 2.14.5-0ubuntu3 Architecture: i386 CrashCounter: 1 Date: Sun Aug 3 07:09:21 2014 ExecutablePath: /usr/bin/mate-display-properties InstallationDate: Installed on 2014-08-03 (0 days ago) InstallationMedia: Ubuntu MATE 14.10 Utopic Unicorn - Alpha i386 (20140731) ProcCmdline: mate-display-properties SegvAnalysis: Skipped: missing required field Disassembly Signal: 11 SourcePackage: mate-control-center UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1351890/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1351890] Re: Changing external screen resolution with dual monitors
Looks good in Precise, waiting for Trusty package so I could tag it as verification-done. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1351890 Title: Changing external screen resolution with dual monitors Status in GTK+: Fix Released Status in ubuntu-mate: Fix Released Status in gtk+2.0 package in Ubuntu: Fix Released Status in mate-control-center package in Ubuntu: Fix Released Status in gtk+2.0 source package in Precise: Fix Committed Status in mate-control-center source package in Precise: Invalid Status in gtk+2.0 source package in Trusty: In Progress Status in mate-control-center source package in Trusty: Invalid Status in gtk+2.0 package in Debian: Fix Released Bug description: [Impact] Due to a bug in GTK+2, mate-display-properties crashes when the screen resolution is changed *outside* of it (e.g. by changing the resolution not via that app, but somewhere else). The attached patches fix the issue in GTK+2 and prevent crashing of m-d-p. Since this issue caused much inconvenience for users, the fix should be backported to all current stable releases of Ubuntu. [Test Case] The easiest way to reproduce it is via Virtualbox: 1. Run mate-display-properties in the VM. 2. Make the VM go full-screen. 3. See m-d-p crash. [Regression Potential] After several months of testing the patched version of GTK+2 in Debian Jessie, I found no regressions. I consider the regression risk very low here. There were originally some bugs with a few applications (notably Spotify) crashing. We think we've backported patches to fix that - some refcounting issues - but please check a few apps to see they still work. [ Original report ] Changing extrnal screen resolution with dual mon ProblemType: Crash DistroRelease: Ubuntu 14.10 Package: mate-control-center 1.8.1+dfsg1-4 ProcVersionSignature: Ubuntu 3.16.0-6.11-generic 3.16.0-rc7 Uname: Linux 3.16.0-6-generic i686 ApportVersion: 2.14.5-0ubuntu3 Architecture: i386 CrashCounter: 1 Date: Sun Aug 3 07:09:21 2014 ExecutablePath: /usr/bin/mate-display-properties InstallationDate: Installed on 2014-08-03 (0 days ago) InstallationMedia: Ubuntu MATE 14.10 Utopic Unicorn - Alpha i386 (20140731) ProcCmdline: mate-display-properties SegvAnalysis: Skipped: missing required field Disassembly Signal: 11 SourcePackage: mate-control-center UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1351890/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 437139] Re: metacity assert failure: metacity:ERROR:core/boxes.c:1161:meta_rectangle_edge_aligns: code should not be reached
** Bug watch added: Debian Bug tracker #510833 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=510833 ** Also affects: metacity (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=510833 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/437139 Title: metacity assert failure: metacity:ERROR:core/boxes.c:1161:meta_rectangle_edge_aligns: code should not be reached Status in metacity: Confirmed Status in metacity package in Ubuntu: Triaged Status in metacity source package in Precise: Triaged Status in metacity package in Debian: Unknown Bug description: Binary package hint: metacity I think this is a new bug ProblemType: Crash Architecture: i386 AssertionMessage: metacity:ERROR:core/boxes.c:1161:meta_rectangle_edge_aligns: code should not be reached Date: Sat Sep 26 13:13:02 2009 DistroRelease: Ubuntu 9.10 ExecutablePath: /usr/bin/metacity Package: metacity 1:2.28.0-0ubuntu1 ProcCmdline: /usr/bin/metacity --replace ProcEnviron: LANG=it_IT.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-11.36-generic Signal: 6 SourcePackage: metacity StacktraceTop: __kernel_vsyscall () raise () from /lib/tls/i686/cmov/libc.so.6 abort () from /lib/tls/i686/cmov/libc.so.6 g_assertion_message () from /lib/libglib-2.0.so.0 ?? () Title: metacity assert failure: metacity:ERROR:core/boxes.c:1161:meta_rectangle_edge_aligns: code should not be reached Uname: Linux 2.6.31-11-generic i686 UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare To manage notifications about this bug go to: https://bugs.launchpad.net/metacity/+bug/437139/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1351890] Re: Changing external screen resolution with dual monitors
Any progress on reviewing the debdiffs? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1351890 Title: Changing external screen resolution with dual monitors Status in GTK+: Fix Released Status in ubuntu-mate: Fix Released Status in gtk+2.0 package in Ubuntu: Fix Released Status in mate-control-center package in Ubuntu: Fix Released Status in gtk+2.0 package in Debian: Fix Released Bug description: Changing extrnal screen resolution with dual mon ProblemType: Crash DistroRelease: Ubuntu 14.10 Package: mate-control-center 1.8.1+dfsg1-4 ProcVersionSignature: Ubuntu 3.16.0-6.11-generic 3.16.0-rc7 Uname: Linux 3.16.0-6-generic i686 ApportVersion: 2.14.5-0ubuntu3 Architecture: i386 CrashCounter: 1 Date: Sun Aug 3 07:09:21 2014 ExecutablePath: /usr/bin/mate-display-properties InstallationDate: Installed on 2014-08-03 (0 days ago) InstallationMedia: Ubuntu MATE 14.10 Utopic Unicorn - Alpha i386 (20140731) ProcCmdline: mate-display-properties SegvAnalysis: Skipped: missing required field Disassembly Signal: 11 SourcePackage: mate-control-center UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1351890/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1473281] Re: MintMenu malplaced when compiz is activated
*** This bug is a duplicate of bug 1419346 *** https://bugs.launchpad.net/bugs/1419346 ** This bug has been marked a duplicate of bug 1419346 mintMenu and MATE Menu are elevated/offset by compiz -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to compiz in Ubuntu. https://bugs.launchpad.net/bugs/1473281 Title: MintMenu malplaced when compiz is activated Status in Compiz: New Status in Linux Mint: New Status in Mate Desktop: New Status in compiz package in Ubuntu: New Bug description: When Compiz is activated in Linux Mint 17.2, the Mintmenu is malplaced - like a centimeter or two over the mate-panel in the bottom, when opened. The problem only appears, when Compiz is activated, and I press the Menubutton. I expected the mintmenu to open like it normally do, - glued closely to the panel, and not jumping around up over the panel. The problem come and go, when Compiz is activated. I had Cube, Animations, Rotate Cube and Expo activated. Linux Mint 17.2 Mate Rafaella 64 bit To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1473281/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 437905] Re: System Administration Services (services-admin) missing
** Tags removed: lucid ** Tags added: trusty utopic vivid wily -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-system-tools in Ubuntu. https://bugs.launchpad.net/bugs/437905 Title: System Administration Services (services-admin) missing Status in gnome-system-tools package in Ubuntu: Triaged Bug description: Binary package hint: gnome-system-tools System---Administration---Services missing I want back the GUI app to config services * System---Administration---Services The name of the GUI is services-admin i run services-admin: juan@karmic:~$ services-admin El programa «services-admin» no está instalado actualmente. Puede instalarlo escribiendo: sudo apt-get install gnome-system-tools services-admin: command not found I want to config my Services with GUI I can't config my Services due to Missing GUI, Packaging problems ProblemType: Bug Architecture: i386 CheckboxSubmission: 5228c0701c3ba13f431ec6aa0b43386c CheckboxSystem: 4263d942d8749f6796fee5f20ef3e914 Date: Sun Sep 27 21:56:04 2009 DistroRelease: Ubuntu 9.10 NonfreeKernelModules: nvidia Package: gnome-system-tools 2.28.0-0ubuntu1 ProcEnviron:  LANG=es_AR.UTF-8  SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-11.36-generic SourcePackage: gnome-system-tools Uname: Linux 2.6.31-11-generic i686 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-system-tools/+bug/437905/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1340687] Re: Please replace current alternate screen scroll patch with the new one, making this scroll permanent
** Tags removed: wily -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to vte in Ubuntu. https://bugs.launchpad.net/bugs/1340687 Title: Please replace current alternate screen scroll patch with the new one, making this scroll permanent Status in vte package in Ubuntu: Fix Released Bug description: Dear maintainers, Please remove 93_add_alt_screen_scroll_toggle.patch and replace it with the new patch from the attachment. This patch adds support for DEC 1007 escape sequence, thus making the alternate screen scroll work always. After applying it, the corresponding patches with the calls to vte_terminal_set_alternate_screen_scroll function can be safely dropped from the terminal applications using GTK2-based vte (e.g. xfce4-terminal). The patch has been adapted from the upstream commit in VTE3 [1]. [1] https://git.gnome.org/browse/vte/commit/?id=9f8c1b88dcd880c2d9e78c93521ee755560a9275 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vte/+bug/1340687/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1340687] Re: Please replace current alternate screen scroll patch with the new one, making this scroll permanent
Hi Martin, This patch does not require changes in other applications. You can leave all GTK+2 terminal apps as is - they will still work as they should even with their corresponding alt.scroll patches enabled. This patch only enables alt.scroll in the temrinal apps that haven't been patched yet, that's all. Actually, the only GTK+2 terminal app that is patched is xfce4-terminal. Other apps like mate-terminal, roxterm-gtk2, lxterminal are not patched. Is there something else needed for SRU here? Let me know, I'll make corrections. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to vte in Ubuntu. https://bugs.launchpad.net/bugs/1340687 Title: Please replace current alternate screen scroll patch with the new one, making this scroll permanent Status in vte package in Ubuntu: Fix Committed Bug description: Dear maintainers, Please remove 93_add_alt_screen_scroll_toggle.patch and replace it with the new patch from the attachment. This patch adds support for DEC 1007 escape sequence, thus making the alternate screen scroll work always. After applying it, the corresponding patches with the calls to vte_terminal_set_alternate_screen_scroll function can be safely dropped from the terminal applications using GTK2-based vte (e.g. xfce4-terminal). The patch has been adapted from the upstream commit in VTE3 [1]. [1] https://git.gnome.org/browse/vte/commit/?id=9f8c1b88dcd880c2d9e78c93521ee755560a9275 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vte/+bug/1340687/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1461082] Re: patch - fix crash with long one-line XML documents
Ok good, proposed packages work perfectly in all four releases. ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtksourceview2 in Ubuntu. https://bugs.launchpad.net/bugs/1461082 Title: patch - fix crash with long one-line XML documents Status in gtksourceview2 package in Ubuntu: Fix Released Status in gtksourceview2 source package in Precise: Fix Committed Status in gtksourceview2 source package in Trusty: Fix Committed Status in gtksourceview2 source package in Utopic: Fix Committed Status in gtksourceview2 source package in Vivid: Fix Committed Status in gtksourceview2 source package in Wily: Fix Released Status in gtksourceview2 package in Debian: Confirmed Bug description: [Impact] When editing a long one-line document with some markup (e.g. XML) with Pluma (or any other editor using gtksourceview2), you cannot delete a selected portion of text because the editor will crash. This has been reported upstream and fixed in [1], but the commit never made it to GTK+2 version of gtksourceview. So, I propose fixing it in current stable Ubuntu releases with the patch which fixes the crash for good. The debdiffs for every stable release are in the attachments below. [Test Case] Steps to reproduce: 1. Open a long one-line XML document (e.g. [2]) with Pluma. Any other editor using gtksourceview2 will also fit I think. 2. Select a portion of text. 3. Press Backspace (or Delete) key. 4. Pluma crashes. The full backtrace is at [3]. If you're running Pluma from the command-line, you'll notice a warning: GtkSourceView-CRITICAL **: Highlighting a single line took too much time, syntax highlighting will be disabled That's the key. The library tries to invalidate the region when text is deleted and the engine is disabled (i.e. syntax highlighting is off). [Regression Potential] After several months of testing the patch in Debian Jessie, I haven't noticed any regressions. [1] https://git.gnome.org/browse/gtksourceview/commit/?id=abef41da8c541c814bf631f69c92e0c431c610ad [2] http://pastebin.com/nNdYzFXE [3] http://pastebin.com/YgDT0iKh To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtksourceview2/+bug/1461082/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1461082] Re: patch - fix crash with long one-line XML documents
I didn't. Every time I see that field auto-changes on rebuild, I take care to remove any debian/control changes from the debdiff. Please recheck and make sure you didn't confuse these patches with someone else's ones. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtksourceview2 in Ubuntu. https://bugs.launchpad.net/bugs/1461082 Title: patch - fix crash with long one-line XML documents Status in gtksourceview2 package in Ubuntu: Fix Released Status in gtksourceview2 source package in Precise: Fix Committed Status in gtksourceview2 source package in Trusty: In Progress Status in gtksourceview2 source package in Utopic: In Progress Status in gtksourceview2 source package in Vivid: In Progress Status in gtksourceview2 source package in Wily: Fix Released Status in gtksourceview2 package in Debian: Confirmed Bug description: [Impact] When editing a long one-line document with some markup (e.g. XML) with Pluma (or any other editor using gtksourceview2), you cannot delete a selected portion of text because the editor will crash. This has been reported upstream and fixed in [1], but the commit never made it to GTK+2 version of gtksourceview. So, I propose fixing it in current stable Ubuntu releases with the patch which fixes the crash for good. The debdiffs for every stable release are in the attachments below. [Test Case] Steps to reproduce: 1. Open a long one-line XML document (e.g. [2]) with Pluma. Any other editor using gtksourceview2 will also fit I think. 2. Select a portion of text. 3. Press Backspace (or Delete) key. 4. Pluma crashes. The full backtrace is at [3]. If you're running Pluma from the command-line, you'll notice a warning: GtkSourceView-CRITICAL **: Highlighting a single line took too much time, syntax highlighting will be disabled That's the key. The library tries to invalidate the region when text is deleted and the engine is disabled (i.e. syntax highlighting is off). [Regression Potential] After several months of testing the patch in Debian Jessie, I haven't noticed any regressions. [1] https://git.gnome.org/browse/gtksourceview/commit/?id=abef41da8c541c814bf631f69c92e0c431c610ad [2] http://pastebin.com/nNdYzFXE [3] http://pastebin.com/YgDT0iKh To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtksourceview2/+bug/1461082/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1404715] Re: evince crashed with SIGSEGV
According to Mint 17.x user, this is still an issue in Trusty (on which Mint 17.x is based): https://github.com/mate-desktop/atril/issues/137 Is the fix going to reach Trusty repos anytime soon? Thanks in advance. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cairo in Ubuntu. https://bugs.launchpad.net/bugs/1404715 Title: evince crashed with SIGSEGV Status in Cairo Graphics Library: Fix Released Status in cairo package in Ubuntu: Fix Committed Status in cairo package in Debian: New Bug description: While browsing http://www.eurail.com/sites/eurail.com/files/documents/eurail_railway_map_2014.pdf ProblemType: Crash DistroRelease: Ubuntu 14.10 Package: evince 3.14.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-29.39-generic 3.16.7-ckt2 Uname: Linux 3.16.0-29-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CrashCounter: 1 CurrentDesktop: Unity Date: Sun Dec 21 20:35:56 2014 ExecutablePath: /usr/bin/evince ExecutableTimestamp: 1413470384 InstallationDate: Installed on 2014-12-09 (11 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) KernLog: ProcCmdline: evince /tmp/eurail_railway_map_2014.pdf ProcCwd: /home/mathieu ProcEnviron: XDG_RUNTIME_DIR=set SHELL=/bin/bash LANGUAGE=fr_FR PATH=(custom, no user) LANG=fr_FR.UTF-8 SegvAnalysis: Segfault happened at: 0x7f679b821fd5:cmpq $0x0,0x30(%r13) PC (0x7f679b821fd5) ok source $0x0 ok destination 0x30(%r13) (0x0030) not located in a known VMA region (needed writable region)! Stack memory exhausted (SP below stack segment) SegvReason: writing NULL VMA Signal: 11 SourcePackage: evince StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libcairo.so.2 ?? () from /usr/lib/x86_64-linux-gnu/libcairo.so.2 ?? () from /usr/lib/x86_64-linux-gnu/libcairo.so.2 ?? () from /usr/lib/x86_64-linux-gnu/libcairo.so.2 ?? () from /usr/lib/x86_64-linux-gnu/libcairo.so.2 Title: evince crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/cairo/+bug/1404715/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 517021] Re: gvfsd-metadata causes 100% CPU usage
Thanks! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/517021 Title: gvfsd-metadata causes 100% CPU usage Status in GVFS: Fix Released Status in gvfs package in Ubuntu: Fix Released Status in gvfs source package in Precise: Fix Released Status in gvfs source package in Trusty: Fix Released Status in gvfs source package in Utopic: Fix Released Status in gvfs source package in Vivid: Fix Released Status in gvfs package in Debian: Fix Released Bug description: Binary package hint: gvfs Failure to write metadata results in an infinite loop that keeps trying to write, thousands of times per second. Steps to reproduce: 1. Open Firefox 2. Save a data: URL (URL that contains the content, with several thousands bytes, often generated by webapps or extensions) as file (There are other ways to run into this problem, e.g. disk full or other error situations. data: URLs are just the easiest way to reproduce.) Actual result: - File is saved - 100% CPU - Extremely high number of file operations by gvfs - billions - Never stops Expected result: Failure to write metadata should just fail, not try again Fix: Patch available and accepted by GNOME https://bugzilla.gnome.org/show_bug.cgi?id=637095 --- Original description --- After installing 9.10 Ubuntu 64bit browsing and opening folder in nautilus or Gnome-commander take several minutes when there are many files in it e.g. 10.000. Interestingly Midnight-commander does not have this problem. Opening such folders does not hang with MC. Using top i can see that gvfsd-metadata is using 100% CPU and when i kill it the computer stops hanging. I am using the 32bit version of Karmic too and there is no such Problem (although tested on a different computer). Please fix this because it is highly annyoing. Right now i am killing it every 20s with the watch command to be able to work at all. To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/517021/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1340687] Re: Please replace current alternate screen scroll patch with the new one, making this scroll permanent
** Tags added: wily -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to vte in Ubuntu. https://bugs.launchpad.net/bugs/1340687 Title: Please replace current alternate screen scroll patch with the new one, making this scroll permanent Status in vte package in Ubuntu: Confirmed Bug description: Dear maintainers, Please remove 93_add_alt_screen_scroll_toggle.patch and replace it with the new patch from the attachment. This patch adds support for DEC 1007 escape sequence, thus making the alternate screen scroll work always. After applying it, the corresponding patches with the calls to vte_terminal_set_alternate_screen_scroll function can be safely dropped from the terminal applications using GTK2-based vte (e.g. xfce4-terminal). The patch has been adapted from the upstream commit in VTE3 [1]. [1] https://git.gnome.org/browse/vte/commit/?id=9f8c1b88dcd880c2d9e78c93521ee755560a9275 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vte/+bug/1340687/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1340687] Re: Please replace current alternate screen scroll patch with the new one, making this scroll permanent
[Impact] The current alternate scroll patch is flawed because the terminal apps using GTK+2 version of VTE library should also be patched in order for the alternate scroll to work. This means that mate-terminal, roxterm- gtk2, lxterminal (and other terminal apps that aren't patched in all Ubuntu releases) don't have the alternate scroll enabled. The proposed new patch that's contained in the debdiffs makes alternate scroll work always, so no patching will be required for any terminal apps. So, the old patch should be replaced with the new one in all current stable releases of Ubuntu. [Test Case] Steps to reproduce: 1. Run mate-terminal or any other non-patched terminal app using GTK+2 version of VTE library. 2. Run man apt-get (any other manpage will work too of course). 3. See that scrolling with mouse wheel doesn't work on the manpage. [Regression Potential] After almost a year of testing the patch in various stable releases of Ubuntu, I found no regressions. I consider the regression risk to be very low here. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to vte in Ubuntu. https://bugs.launchpad.net/bugs/1340687 Title: Please replace current alternate screen scroll patch with the new one, making this scroll permanent Status in vte package in Ubuntu: Confirmed Bug description: Dear maintainers, Please remove 93_add_alt_screen_scroll_toggle.patch and replace it with the new patch from the attachment. This patch adds support for DEC 1007 escape sequence, thus making the alternate screen scroll work always. After applying it, the corresponding patches with the calls to vte_terminal_set_alternate_screen_scroll function can be safely dropped from the terminal applications using GTK2-based vte (e.g. xfce4-terminal). The patch has been adapted from the upstream commit in VTE3 [1]. [1] https://git.gnome.org/browse/vte/commit/?id=9f8c1b88dcd880c2d9e78c93521ee755560a9275 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vte/+bug/1340687/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1340687] Re: Please replace current alternate screen scroll patch with the new one, making this scroll permanent
** Tags added: precise -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to vte in Ubuntu. https://bugs.launchpad.net/bugs/1340687 Title: Please replace current alternate screen scroll patch with the new one, making this scroll permanent Status in vte package in Ubuntu: Confirmed Bug description: Dear maintainers, Please remove 93_add_alt_screen_scroll_toggle.patch and replace it with the new patch from the attachment. This patch adds support for DEC 1007 escape sequence, thus making the alternate screen scroll work always. After applying it, the corresponding patches with the calls to vte_terminal_set_alternate_screen_scroll function can be safely dropped from the terminal applications using GTK2-based vte (e.g. xfce4-terminal). The patch has been adapted from the upstream commit in VTE3 [1]. [1] https://git.gnome.org/browse/vte/commit/?id=9f8c1b88dcd880c2d9e78c93521ee755560a9275 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vte/+bug/1340687/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1351890] Re: Changing external screen resolution with dual monitors
Hmm, not sure why Ubuntu Sponsors Team wasn't auto-subscribed after my debdiffs. Ok, fixed that manually. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1351890 Title: Changing external screen resolution with dual monitors Status in GTK+ GUI Toolkit: Fix Released Status in Ubuntu MATE: Fix Released Status in gtk+2.0 package in Ubuntu: Fix Released Status in mate-control-center package in Ubuntu: Fix Released Status in gtk+2.0 package in Debian: Fix Released Bug description: Changing extrnal screen resolution with dual mon ProblemType: Crash DistroRelease: Ubuntu 14.10 Package: mate-control-center 1.8.1+dfsg1-4 ProcVersionSignature: Ubuntu 3.16.0-6.11-generic 3.16.0-rc7 Uname: Linux 3.16.0-6-generic i686 ApportVersion: 2.14.5-0ubuntu3 Architecture: i386 CrashCounter: 1 Date: Sun Aug 3 07:09:21 2014 ExecutablePath: /usr/bin/mate-display-properties InstallationDate: Installed on 2014-08-03 (0 days ago) InstallationMedia: Ubuntu MATE 14.10 Utopic Unicorn - Alpha i386 (20140731) ProcCmdline: mate-display-properties SegvAnalysis: Skipped: missing required field Disassembly Signal: 11 SourcePackage: mate-control-center UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1351890/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1340687] Re: Please replace current alternate screen scroll patch with the new one, making this scroll permanent
** Attachment added: debdiff with the fix for Trusty https://bugs.launchpad.net/ubuntu/+source/vte/+bug/1340687/+attachment/4409839/+files/vte-trusty-debdiff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to vte in Ubuntu. https://bugs.launchpad.net/bugs/1340687 Title: Please replace current alternate screen scroll patch with the new one, making this scroll permanent Status in vte package in Ubuntu: Confirmed Bug description: Dear maintainers, Please remove 93_add_alt_screen_scroll_toggle.patch and replace it with the new patch from the attachment. This patch adds support for DEC 1007 escape sequence, thus making the alternate screen scroll work always. After applying it, the corresponding patches with the calls to vte_terminal_set_alternate_screen_scroll function can be safely dropped from the terminal applications using GTK2-based vte (e.g. xfce4-terminal). The patch has been adapted from the upstream commit in VTE3 [1]. [1] https://git.gnome.org/browse/vte/commit/?id=9f8c1b88dcd880c2d9e78c93521ee755560a9275 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vte/+bug/1340687/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1340687] Re: Please replace current alternate screen scroll patch with the new one, making this scroll permanent
** Attachment added: debdiff with the fix for Vivid https://bugs.launchpad.net/ubuntu/+source/vte/+bug/1340687/+attachment/4409841/+files/vte-vivid-debdiff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to vte in Ubuntu. https://bugs.launchpad.net/bugs/1340687 Title: Please replace current alternate screen scroll patch with the new one, making this scroll permanent Status in vte package in Ubuntu: Confirmed Bug description: Dear maintainers, Please remove 93_add_alt_screen_scroll_toggle.patch and replace it with the new patch from the attachment. This patch adds support for DEC 1007 escape sequence, thus making the alternate screen scroll work always. After applying it, the corresponding patches with the calls to vte_terminal_set_alternate_screen_scroll function can be safely dropped from the terminal applications using GTK2-based vte (e.g. xfce4-terminal). The patch has been adapted from the upstream commit in VTE3 [1]. [1] https://git.gnome.org/browse/vte/commit/?id=9f8c1b88dcd880c2d9e78c93521ee755560a9275 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vte/+bug/1340687/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1340687] Re: Please replace current alternate screen scroll patch with the new one, making this scroll permanent
** Attachment added: debdiff with the fix for Precise https://bugs.launchpad.net/ubuntu/+source/vte/+bug/1340687/+attachment/4409838/+files/vte-precise-debdiff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to vte in Ubuntu. https://bugs.launchpad.net/bugs/1340687 Title: Please replace current alternate screen scroll patch with the new one, making this scroll permanent Status in vte package in Ubuntu: Confirmed Bug description: Dear maintainers, Please remove 93_add_alt_screen_scroll_toggle.patch and replace it with the new patch from the attachment. This patch adds support for DEC 1007 escape sequence, thus making the alternate screen scroll work always. After applying it, the corresponding patches with the calls to vte_terminal_set_alternate_screen_scroll function can be safely dropped from the terminal applications using GTK2-based vte (e.g. xfce4-terminal). The patch has been adapted from the upstream commit in VTE3 [1]. [1] https://git.gnome.org/browse/vte/commit/?id=9f8c1b88dcd880c2d9e78c93521ee755560a9275 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vte/+bug/1340687/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1340687] Re: Please replace current alternate screen scroll patch with the new one, making this scroll permanent
** Attachment added: debdiff with the fix for Utopic https://bugs.launchpad.net/ubuntu/+source/vte/+bug/1340687/+attachment/4409840/+files/vte-utopic-debdiff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to vte in Ubuntu. https://bugs.launchpad.net/bugs/1340687 Title: Please replace current alternate screen scroll patch with the new one, making this scroll permanent Status in vte package in Ubuntu: Confirmed Bug description: Dear maintainers, Please remove 93_add_alt_screen_scroll_toggle.patch and replace it with the new patch from the attachment. This patch adds support for DEC 1007 escape sequence, thus making the alternate screen scroll work always. After applying it, the corresponding patches with the calls to vte_terminal_set_alternate_screen_scroll function can be safely dropped from the terminal applications using GTK2-based vte (e.g. xfce4-terminal). The patch has been adapted from the upstream commit in VTE3 [1]. [1] https://git.gnome.org/browse/vte/commit/?id=9f8c1b88dcd880c2d9e78c93521ee755560a9275 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vte/+bug/1340687/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1351890] Re: Changing external screen resolution with dual monitors
** Attachment added: updated debdiff for Precise https://bugs.launchpad.net/ubuntu/+source/mate-control-center/+bug/1351890/+attachment/4409106/+files/gtk2-precise-updated-debdiff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1351890 Title: Changing external screen resolution with dual monitors Status in GTK+ GUI Toolkit: Fix Released Status in Ubuntu MATE: Fix Released Status in gtk+2.0 package in Ubuntu: Fix Released Status in mate-control-center package in Ubuntu: Fix Released Status in gtk+2.0 package in Debian: Fix Released Bug description: Changing extrnal screen resolution with dual mon ProblemType: Crash DistroRelease: Ubuntu 14.10 Package: mate-control-center 1.8.1+dfsg1-4 ProcVersionSignature: Ubuntu 3.16.0-6.11-generic 3.16.0-rc7 Uname: Linux 3.16.0-6-generic i686 ApportVersion: 2.14.5-0ubuntu3 Architecture: i386 CrashCounter: 1 Date: Sun Aug 3 07:09:21 2014 ExecutablePath: /usr/bin/mate-display-properties InstallationDate: Installed on 2014-08-03 (0 days ago) InstallationMedia: Ubuntu MATE 14.10 Utopic Unicorn - Alpha i386 (20140731) ProcCmdline: mate-display-properties SegvAnalysis: Skipped: missing required field Disassembly Signal: 11 SourcePackage: mate-control-center UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1351890/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1351890] Re: Changing external screen resolution with dual monitors
** Attachment added: updated debdiff for Trusty https://bugs.launchpad.net/ubuntu/+source/mate-control-center/+bug/1351890/+attachment/4409107/+files/gtk2-trusty-updated-debdiff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1351890 Title: Changing external screen resolution with dual monitors Status in GTK+ GUI Toolkit: Fix Released Status in Ubuntu MATE: Fix Released Status in gtk+2.0 package in Ubuntu: Fix Released Status in mate-control-center package in Ubuntu: Fix Released Status in gtk+2.0 package in Debian: Fix Released Bug description: Changing extrnal screen resolution with dual mon ProblemType: Crash DistroRelease: Ubuntu 14.10 Package: mate-control-center 1.8.1+dfsg1-4 ProcVersionSignature: Ubuntu 3.16.0-6.11-generic 3.16.0-rc7 Uname: Linux 3.16.0-6-generic i686 ApportVersion: 2.14.5-0ubuntu3 Architecture: i386 CrashCounter: 1 Date: Sun Aug 3 07:09:21 2014 ExecutablePath: /usr/bin/mate-display-properties InstallationDate: Installed on 2014-08-03 (0 days ago) InstallationMedia: Ubuntu MATE 14.10 Utopic Unicorn - Alpha i386 (20140731) ProcCmdline: mate-display-properties SegvAnalysis: Skipped: missing required field Disassembly Signal: 11 SourcePackage: mate-control-center UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1351890/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1351890] Re: Changing external screen resolution with dual monitors
** Attachment added: updated debdiff for Utopic https://bugs.launchpad.net/ubuntu/+source/mate-control-center/+bug/1351890/+attachment/4409108/+files/gtk2-utopic-updated-debdiff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1351890 Title: Changing external screen resolution with dual monitors Status in GTK+ GUI Toolkit: Fix Released Status in Ubuntu MATE: Fix Released Status in gtk+2.0 package in Ubuntu: Fix Released Status in mate-control-center package in Ubuntu: Fix Released Status in gtk+2.0 package in Debian: Fix Released Bug description: Changing extrnal screen resolution with dual mon ProblemType: Crash DistroRelease: Ubuntu 14.10 Package: mate-control-center 1.8.1+dfsg1-4 ProcVersionSignature: Ubuntu 3.16.0-6.11-generic 3.16.0-rc7 Uname: Linux 3.16.0-6-generic i686 ApportVersion: 2.14.5-0ubuntu3 Architecture: i386 CrashCounter: 1 Date: Sun Aug 3 07:09:21 2014 ExecutablePath: /usr/bin/mate-display-properties InstallationDate: Installed on 2014-08-03 (0 days ago) InstallationMedia: Ubuntu MATE 14.10 Utopic Unicorn - Alpha i386 (20140731) ProcCmdline: mate-display-properties SegvAnalysis: Skipped: missing required field Disassembly Signal: 11 SourcePackage: mate-control-center UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1351890/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1351890] Re: Changing external screen resolution with dual monitors
There we go. All three debdiffs have been updated to include two more patches mentioned in the comments above (thanks to Sebastien Bacher and Iain Lane). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1351890 Title: Changing external screen resolution with dual monitors Status in GTK+ GUI Toolkit: Fix Released Status in Ubuntu MATE: Fix Released Status in gtk+2.0 package in Ubuntu: Fix Released Status in mate-control-center package in Ubuntu: Fix Released Status in gtk+2.0 package in Debian: Fix Released Bug description: Changing extrnal screen resolution with dual mon ProblemType: Crash DistroRelease: Ubuntu 14.10 Package: mate-control-center 1.8.1+dfsg1-4 ProcVersionSignature: Ubuntu 3.16.0-6.11-generic 3.16.0-rc7 Uname: Linux 3.16.0-6-generic i686 ApportVersion: 2.14.5-0ubuntu3 Architecture: i386 CrashCounter: 1 Date: Sun Aug 3 07:09:21 2014 ExecutablePath: /usr/bin/mate-display-properties InstallationDate: Installed on 2014-08-03 (0 days ago) InstallationMedia: Ubuntu MATE 14.10 Utopic Unicorn - Alpha i386 (20140731) ProcCmdline: mate-display-properties SegvAnalysis: Skipped: missing required field Disassembly Signal: 11 SourcePackage: mate-control-center UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1351890/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1351890] Re: Changing external screen resolution with dual monitors
[Impact] Due to a bug in GTK+2, mate-display-properties crashes when the screen resolution is changed *outside* of it (e.g. by changing the resolution not via that app, but somewhere else). The attached patches fix the issue in GTK+2 and prevent crashing of m-d-p. Since this issue caused much inconvenience for users, the fix should be backported to all current stable releases of Ubuntu. [Test Case] The easiest way to reproduce it is via Virtualbox: 1. Run mate-display-properties in the VM. 2. Make the VM go full-screen. 3. See m-d-p crash. [Regression Potential] After several months of testing the patched version of GTK+2 in Debian Jessie, I found no regressions. I consider the regression risk very low here. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1351890 Title: Changing external screen resolution with dual monitors Status in GTK+ GUI Toolkit: Fix Released Status in Ubuntu MATE: Fix Released Status in gtk+2.0 package in Ubuntu: Fix Released Status in mate-control-center package in Ubuntu: Fix Released Status in gtk+2.0 package in Debian: Fix Released Bug description: Changing extrnal screen resolution with dual mon ProblemType: Crash DistroRelease: Ubuntu 14.10 Package: mate-control-center 1.8.1+dfsg1-4 ProcVersionSignature: Ubuntu 3.16.0-6.11-generic 3.16.0-rc7 Uname: Linux 3.16.0-6-generic i686 ApportVersion: 2.14.5-0ubuntu3 Architecture: i386 CrashCounter: 1 Date: Sun Aug 3 07:09:21 2014 ExecutablePath: /usr/bin/mate-display-properties InstallationDate: Installed on 2014-08-03 (0 days ago) InstallationMedia: Ubuntu MATE 14.10 Utopic Unicorn - Alpha i386 (20140731) ProcCmdline: mate-display-properties SegvAnalysis: Skipped: missing required field Disassembly Signal: 11 SourcePackage: mate-control-center UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1351890/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 517021] Re: gvfsd-metadata causes 100% CPU usage
The only error message I could find in the logs is this: Error: Did not find a parent process that runs as non-root at https://jenkins.qa.ubuntu.com/job/trusty-adt- gvfs/ARCH=amd64,label=adt/152/ What's going on? It seems like internal error on build server, not a regression in gvfs. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/517021 Title: gvfsd-metadata causes 100% CPU usage Status in GVFS: Fix Released Status in gvfs package in Ubuntu: Fix Released Status in gvfs source package in Precise: Fix Released Status in gvfs source package in Trusty: Fix Committed Status in gvfs source package in Utopic: Fix Committed Status in gvfs source package in Vivid: Fix Released Status in gvfs package in Debian: Fix Released Bug description: Binary package hint: gvfs Failure to write metadata results in an infinite loop that keeps trying to write, thousands of times per second. Steps to reproduce: 1. Open Firefox 2. Save a data: URL (URL that contains the content, with several thousands bytes, often generated by webapps or extensions) as file (There are other ways to run into this problem, e.g. disk full or other error situations. data: URLs are just the easiest way to reproduce.) Actual result: - File is saved - 100% CPU - Extremely high number of file operations by gvfs - billions - Never stops Expected result: Failure to write metadata should just fail, not try again Fix: Patch available and accepted by GNOME https://bugzilla.gnome.org/show_bug.cgi?id=637095 --- Original description --- After installing 9.10 Ubuntu 64bit browsing and opening folder in nautilus or Gnome-commander take several minutes when there are many files in it e.g. 10.000. Interestingly Midnight-commander does not have this problem. Opening such folders does not hang with MC. Using top i can see that gvfsd-metadata is using 100% CPU and when i kill it the computer stops hanging. I am using the 32bit version of Karmic too and there is no such Problem (although tested on a different computer). Please fix this because it is highly annyoing. Right now i am killing it every 20s with the watch command to be able to work at all. To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/517021/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1461082] Re: patch - fix crash with long one-line XML documents
** Attachment added: debdiff with the fix for Vivid https://bugs.launchpad.net/ubuntu/+source/gtksourceview2/+bug/1461082/+attachment/4408618/+files/gsv-vivid-debdiff ** Bug watch added: Debian Bug tracker #780205 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=780205 ** Also affects: gtksourceview2 (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=780205 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtksourceview2 in Ubuntu. https://bugs.launchpad.net/bugs/1461082 Title: patch - fix crash with long one-line XML documents Status in gtksourceview2 package in Ubuntu: New Status in gtksourceview2 package in Debian: Unknown Bug description: [Impact] When editing a long one-line document with some markup (e.g. XML) with Pluma (or any other editor using gtksourceview2), you cannot delete a selected portion of text because the editor will crash. This has been reported upstream and fixed in [1], but the commit never made it to GTK+2 version of gtksourceview. So, I propose fixing it in current stable Ubuntu releases with the patch which fixes the crash for good. The debdiffs for every stable release are in the attachments below. [Test Case] Steps to reproduce: 1. Open a long one-line XML document (e.g. [2]) with Pluma. Any other editor using gtksourceview2 will also fit I think. 2. Select a portion of text. 3. Press Backspace (or Delete) key. 4. Pluma crashes. The full backtrace is at [3]. If you're running Pluma from the command-line, you'll notice a warning: GtkSourceView-CRITICAL **: Highlighting a single line took too much time, syntax highlighting will be disabled That's the key. The library tries to invalidate the region when text is deleted and the engine is disabled (i.e. syntax highlighting is off). [Regression Potential] After several months of testing the patch in Debian Jessie, I haven't noticed any regressions. [1] https://git.gnome.org/browse/gtksourceview/commit/?id=abef41da8c541c814bf631f69c92e0c431c610ad [2] http://pastebin.com/nNdYzFXE [3] http://pastebin.com/YgDT0iKh To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtksourceview2/+bug/1461082/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1461082] Re: patch - fix crash with long one-line XML documents
** Attachment added: debdiff with the fix for Precise https://bugs.launchpad.net/ubuntu/+source/gtksourceview2/+bug/1461082/+attachment/4408594/+files/gsv-precise-debdiff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtksourceview2 in Ubuntu. https://bugs.launchpad.net/bugs/1461082 Title: patch - fix crash with long one-line XML documents Status in gtksourceview2 package in Ubuntu: New Status in gtksourceview2 package in Debian: Unknown Bug description: [Impact] When editing a long one-line document with some markup (e.g. XML) with Pluma (or any other editor using gtksourceview2), you cannot delete a selected portion of text because the editor will crash. This has been reported upstream and fixed in [1], but the commit never made it to GTK+2 version of gtksourceview. So, I propose fixing it in current stable Ubuntu releases with the patch which fixes the crash for good. The debdiffs for every stable release are in the attachments below. [Test Case] Steps to reproduce: 1. Open a long one-line XML document (e.g. [2]) with Pluma. Any other editor using gtksourceview2 will also fit I think. 2. Select a portion of text. 3. Press Backspace (or Delete) key. 4. Pluma crashes. The full backtrace is at [3]. If you're running Pluma from the command-line, you'll notice a warning: GtkSourceView-CRITICAL **: Highlighting a single line took too much time, syntax highlighting will be disabled That's the key. The library tries to invalidate the region when text is deleted and the engine is disabled (i.e. syntax highlighting is off). [Regression Potential] After several months of testing the patch in Debian Jessie, I haven't noticed any regressions. [1] https://git.gnome.org/browse/gtksourceview/commit/?id=abef41da8c541c814bf631f69c92e0c431c610ad [2] http://pastebin.com/nNdYzFXE [3] http://pastebin.com/YgDT0iKh To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtksourceview2/+bug/1461082/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1461082] Re: patch - fix crash with long one-line XML documents
** Attachment added: debdiff with the fix for Trusty https://bugs.launchpad.net/ubuntu/+source/gtksourceview2/+bug/1461082/+attachment/4408595/+files/gsv-trusty-debdiff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtksourceview2 in Ubuntu. https://bugs.launchpad.net/bugs/1461082 Title: patch - fix crash with long one-line XML documents Status in gtksourceview2 package in Ubuntu: New Status in gtksourceview2 package in Debian: Unknown Bug description: [Impact] When editing a long one-line document with some markup (e.g. XML) with Pluma (or any other editor using gtksourceview2), you cannot delete a selected portion of text because the editor will crash. This has been reported upstream and fixed in [1], but the commit never made it to GTK+2 version of gtksourceview. So, I propose fixing it in current stable Ubuntu releases with the patch which fixes the crash for good. The debdiffs for every stable release are in the attachments below. [Test Case] Steps to reproduce: 1. Open a long one-line XML document (e.g. [2]) with Pluma. Any other editor using gtksourceview2 will also fit I think. 2. Select a portion of text. 3. Press Backspace (or Delete) key. 4. Pluma crashes. The full backtrace is at [3]. If you're running Pluma from the command-line, you'll notice a warning: GtkSourceView-CRITICAL **: Highlighting a single line took too much time, syntax highlighting will be disabled That's the key. The library tries to invalidate the region when text is deleted and the engine is disabled (i.e. syntax highlighting is off). [Regression Potential] After several months of testing the patch in Debian Jessie, I haven't noticed any regressions. [1] https://git.gnome.org/browse/gtksourceview/commit/?id=abef41da8c541c814bf631f69c92e0c431c610ad [2] http://pastebin.com/nNdYzFXE [3] http://pastebin.com/YgDT0iKh To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtksourceview2/+bug/1461082/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1461082] Re: patch - fix crash with long one-line XML documents
** Attachment added: debdiff with the fix for Utopic https://bugs.launchpad.net/ubuntu/+source/gtksourceview2/+bug/1461082/+attachment/4408603/+files/gsv-utopic-debdiff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtksourceview2 in Ubuntu. https://bugs.launchpad.net/bugs/1461082 Title: patch - fix crash with long one-line XML documents Status in gtksourceview2 package in Ubuntu: New Status in gtksourceview2 package in Debian: Unknown Bug description: [Impact] When editing a long one-line document with some markup (e.g. XML) with Pluma (or any other editor using gtksourceview2), you cannot delete a selected portion of text because the editor will crash. This has been reported upstream and fixed in [1], but the commit never made it to GTK+2 version of gtksourceview. So, I propose fixing it in current stable Ubuntu releases with the patch which fixes the crash for good. The debdiffs for every stable release are in the attachments below. [Test Case] Steps to reproduce: 1. Open a long one-line XML document (e.g. [2]) with Pluma. Any other editor using gtksourceview2 will also fit I think. 2. Select a portion of text. 3. Press Backspace (or Delete) key. 4. Pluma crashes. The full backtrace is at [3]. If you're running Pluma from the command-line, you'll notice a warning: GtkSourceView-CRITICAL **: Highlighting a single line took too much time, syntax highlighting will be disabled That's the key. The library tries to invalidate the region when text is deleted and the engine is disabled (i.e. syntax highlighting is off). [Regression Potential] After several months of testing the patch in Debian Jessie, I haven't noticed any regressions. [1] https://git.gnome.org/browse/gtksourceview/commit/?id=abef41da8c541c814bf631f69c92e0c431c610ad [2] http://pastebin.com/nNdYzFXE [3] http://pastebin.com/YgDT0iKh To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtksourceview2/+bug/1461082/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1461082] [NEW] patch - fix crash with long one-line XML documents
Public bug reported: [Impact] When editing a long one-line document with some markup (e.g. XML) with Pluma (or any other editor using gtksourceview2), you cannot delete a selected portion of text because the editor will crash. This has been reported upstream and fixed in [1], but the commit never made it to GTK+2 version of gtksourceview. So, I propose fixing it in current stable Ubuntu releases with the patch which fixes the crash for good. The debdiffs for every stable release are in the attachments below. [Test Case] Steps to reproduce: 1. Open a long one-line XML document (e.g. [2]) with Pluma. Any other editor using gtksourceview2 will also fit I think. 2. Select a portion of text. 3. Press Backspace (or Delete) key. 4. Pluma crashes. The full backtrace is at [3]. If you're running Pluma from the command-line, you'll notice a warning: GtkSourceView-CRITICAL **: Highlighting a single line took too much time, syntax highlighting will be disabled That's the key. The library tries to invalidate the region when text is deleted and the engine is disabled (i.e. syntax highlighting is off). [Regression Potential] After several months of testing the patch in Debian Jessie, I haven't noticed any regressions. [1] https://git.gnome.org/browse/gtksourceview/commit/?id=abef41da8c541c814bf631f69c92e0c431c610ad [2] http://pastebin.com/nNdYzFXE [3] http://pastebin.com/YgDT0iKh ** Affects: gtksourceview2 (Ubuntu) Importance: Undecided Status: New ** Affects: gtksourceview2 (Debian) Importance: Unknown Status: Unknown ** Tags: precise trusty utopic vivid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtksourceview2 in Ubuntu. https://bugs.launchpad.net/bugs/1461082 Title: patch - fix crash with long one-line XML documents Status in gtksourceview2 package in Ubuntu: New Status in gtksourceview2 package in Debian: Unknown Bug description: [Impact] When editing a long one-line document with some markup (e.g. XML) with Pluma (or any other editor using gtksourceview2), you cannot delete a selected portion of text because the editor will crash. This has been reported upstream and fixed in [1], but the commit never made it to GTK+2 version of gtksourceview. So, I propose fixing it in current stable Ubuntu releases with the patch which fixes the crash for good. The debdiffs for every stable release are in the attachments below. [Test Case] Steps to reproduce: 1. Open a long one-line XML document (e.g. [2]) with Pluma. Any other editor using gtksourceview2 will also fit I think. 2. Select a portion of text. 3. Press Backspace (or Delete) key. 4. Pluma crashes. The full backtrace is at [3]. If you're running Pluma from the command-line, you'll notice a warning: GtkSourceView-CRITICAL **: Highlighting a single line took too much time, syntax highlighting will be disabled That's the key. The library tries to invalidate the region when text is deleted and the engine is disabled (i.e. syntax highlighting is off). [Regression Potential] After several months of testing the patch in Debian Jessie, I haven't noticed any regressions. [1] https://git.gnome.org/browse/gtksourceview/commit/?id=abef41da8c541c814bf631f69c92e0c431c610ad [2] http://pastebin.com/nNdYzFXE [3] http://pastebin.com/YgDT0iKh To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtksourceview2/+bug/1461082/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 517021] Re: gvfsd-metadata causes 100% CPU usage
Would be nice to know the details of that regression as well. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/517021 Title: gvfsd-metadata causes 100% CPU usage Status in GVFS: Fix Released Status in gvfs package in Ubuntu: Fix Released Status in gvfs source package in Precise: Fix Released Status in gvfs source package in Trusty: Fix Committed Status in gvfs source package in Utopic: Fix Committed Status in gvfs source package in Vivid: Fix Released Status in gvfs package in Debian: Fix Released Bug description: Binary package hint: gvfs Failure to write metadata results in an infinite loop that keeps trying to write, thousands of times per second. Steps to reproduce: 1. Open Firefox 2. Save a data: URL (URL that contains the content, with several thousands bytes, often generated by webapps or extensions) as file (There are other ways to run into this problem, e.g. disk full or other error situations. data: URLs are just the easiest way to reproduce.) Actual result: - File is saved - 100% CPU - Extremely high number of file operations by gvfs - billions - Never stops Expected result: Failure to write metadata should just fail, not try again Fix: Patch available and accepted by GNOME https://bugzilla.gnome.org/show_bug.cgi?id=637095 --- Original description --- After installing 9.10 Ubuntu 64bit browsing and opening folder in nautilus or Gnome-commander take several minutes when there are many files in it e.g. 10.000. Interestingly Midnight-commander does not have this problem. Opening such folders does not hang with MC. Using top i can see that gvfsd-metadata is using 100% CPU and when i kill it the computer stops hanging. I am using the 32bit version of Karmic too and there is no such Problem (although tested on a different computer). Please fix this because it is highly annyoing. Right now i am killing it every 20s with the watch command to be able to work at all. To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/517021/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 517021] Re: gvfsd-metadata causes 100% CPU usage
I have the same question as Fantu. Why? :-/ -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/517021 Title: gvfsd-metadata causes 100% CPU usage Status in GVFS: Unknown Status in gvfs package in Ubuntu: Fix Released Status in gvfs source package in Precise: Fix Released Status in gvfs source package in Trusty: Fix Committed Status in gvfs source package in Utopic: Fix Committed Status in gvfs source package in Vivid: Fix Released Status in gvfs package in Debian: Fix Released Bug description: Binary package hint: gvfs Failure to write metadata results in an infinite loop that keeps trying to write, thousands of times per second. Steps to reproduce: 1. Open Firefox 2. Save a data: URL (URL that contains the content, with several thousands bytes, often generated by webapps or extensions) as file (There are other ways to run into this problem, e.g. disk full or other error situations. data: URLs are just the easiest way to reproduce.) Actual result: - File is saved - 100% CPU - Extremely high number of file operations by gvfs - billions - Never stops Expected result: Failure to write metadata should just fail, not try again Fix: Patch available and accepted by GNOME https://bugzilla.gnome.org/show_bug.cgi?id=637095 --- Original description --- After installing 9.10 Ubuntu 64bit browsing and opening folder in nautilus or Gnome-commander take several minutes when there are many files in it e.g. 10.000. Interestingly Midnight-commander does not have this problem. Opening such folders does not hang with MC. Using top i can see that gvfsd-metadata is using 100% CPU and when i kill it the computer stops hanging. I am using the 32bit version of Karmic too and there is no such Problem (although tested on a different computer). Please fix this because it is highly annyoing. Right now i am killing it every 20s with the watch command to be able to work at all. To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/517021/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 517021] Re: gvfsd-metadata causes 100% CPU usage
Thanks Marc :) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/517021 Title: gvfsd-metadata causes 100% CPU usage Status in GVFS: Unknown Status in gvfs package in Ubuntu: Fix Released Status in gvfs source package in Precise: In Progress Status in gvfs source package in Trusty: In Progress Status in gvfs source package in Utopic: In Progress Status in gvfs source package in Vivid: Fix Released Status in gvfs package in Debian: Fix Released Bug description: Binary package hint: gvfs Failure to write metadata results in an infinite loop that keeps trying to write, thousands of times per second. Steps to reproduce: 1. Open Firefox 2. Save a data: URL (URL that contains the content, with several thousands bytes, often generated by webapps or extensions) as file (There are other ways to run into this problem, e.g. disk full or other error situations. data: URLs are just the easiest way to reproduce.) Actual result: - File is saved - 100% CPU - Extremely high number of file operations by gvfs - billions - Never stops Expected result: Failure to write metadata should just fail, not try again Fix: Patch available and accepted by GNOME https://bugzilla.gnome.org/show_bug.cgi?id=637095 --- Original description --- After installing 9.10 Ubuntu 64bit browsing and opening folder in nautilus or Gnome-commander take several minutes when there are many files in it e.g. 10.000. Interestingly Midnight-commander does not have this problem. Opening such folders does not hang with MC. Using top i can see that gvfsd-metadata is using 100% CPU and when i kill it the computer stops hanging. I am using the 32bit version of Karmic too and there is no such Problem (although tested on a different computer). Please fix this because it is highly annyoing. Right now i am killing it every 20s with the watch command to be able to work at all. To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/517021/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 517021] Re: gvfsd-metadata causes 100% CPU usage
Ah dammit, copy/paste error, this is the corresponding Debian bug number. :) Thanks for pointing that out. Unfortunately, LP does not allow us to edit neither comments nor patches/debdiffs. I can only delete the attachments and upload the corrected ones. I'm not sure whether it should be done now since ubuntu-sponsors team is already subscribed to this report. Maybe they'll correct the bug number. If not, I can reupload the debdiffs. As for the UNRELEASED thing, it's what the modern versions of dch put there when you run dch --nmu to indicate a non-maintainer upload. I didn't edit that afterwards. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/517021 Title: gvfsd-metadata causes 100% CPU usage Status in gvfs package in Ubuntu: Confirmed Status in gvfs package in Debian: Fix Released Bug description: Binary package hint: gvfs Failure to write metadata results in an infinite loop that keeps trying to write, thousands of times per second. Steps to reproduce: 1. Open Firefox 2. Save a data: URL (URL that contains the content, with several thousands bytes, often generated by webapps or extensions) as file (There are other ways to run into this problem, e.g. disk full or other error situations. data: URLs are just the easiest way to reproduce.) Actual result: - File is saved - 100% CPU - Extremely high number of file operations by gvfs - billions - Never stops Expected result: Failure to write metadata should just fail, not try again Fix: Patch available and accepted by GNOME https://bugzilla.gnome.org/show_bug.cgi?id=637095 --- Original description --- After installing 9.10 Ubuntu 64bit browsing and opening folder in nautilus or Gnome-commander take several minutes when there are many files in it e.g. 10.000. Interestingly Midnight-commander does not have this problem. Opening such folders does not hang with MC. Using top i can see that gvfsd-metadata is using 100% CPU and when i kill it the computer stops hanging. I am using the 32bit version of Karmic too and there is no such Problem (although tested on a different computer). Please fix this because it is highly annyoing. Right now i am killing it every 20s with the watch command to be able to work at all. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/517021/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 517021] Re: gvfsd-metadata causes 100% CPU usage
Well, I guess I'll need to write SRU Bug Template as well: https://wiki.ubuntu.com/StableReleaseUpdates/#SRU_Bug_Template -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/517021 Title: gvfsd-metadata causes 100% CPU usage Status in gvfs package in Ubuntu: Confirmed Status in gvfs package in Debian: Fix Released Bug description: Binary package hint: gvfs Failure to write metadata results in an infinite loop that keeps trying to write, thousands of times per second. Steps to reproduce: 1. Open Firefox 2. Save a data: URL (URL that contains the content, with several thousands bytes, often generated by webapps or extensions) as file (There are other ways to run into this problem, e.g. disk full or other error situations. data: URLs are just the easiest way to reproduce.) Actual result: - File is saved - 100% CPU - Extremely high number of file operations by gvfs - billions - Never stops Expected result: Failure to write metadata should just fail, not try again Fix: Patch available and accepted by GNOME https://bugzilla.gnome.org/show_bug.cgi?id=637095 --- Original description --- After installing 9.10 Ubuntu 64bit browsing and opening folder in nautilus or Gnome-commander take several minutes when there are many files in it e.g. 10.000. Interestingly Midnight-commander does not have this problem. Opening such folders does not hang with MC. Using top i can see that gvfsd-metadata is using 100% CPU and when i kill it the computer stops hanging. I am using the 32bit version of Karmic too and there is no such Problem (although tested on a different computer). Please fix this because it is highly annyoing. Right now i am killing it every 20s with the watch command to be able to work at all. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/517021/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 517021] Re: gvfsd-metadata causes 100% CPU usage
** Attachment added: debdiff with the fix for Precise https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/517021/+attachment/4380477/+files/gvfs-precise-debdiff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/517021 Title: gvfsd-metadata causes 100% CPU usage Status in gvfs package in Ubuntu: Confirmed Status in gvfs package in Debian: Fix Released Bug description: Binary package hint: gvfs Failure to write metadata results in an infinite loop that keeps trying to write, thousands of times per second. Steps to reproduce: 1. Open Firefox 2. Save a data: URL (URL that contains the content, with several thousands bytes, often generated by webapps or extensions) as file (There are other ways to run into this problem, e.g. disk full or other error situations. data: URLs are just the easiest way to reproduce.) Actual result: - File is saved - 100% CPU - Extremely high number of file operations by gvfs - billions - Never stops Expected result: Failure to write metadata should just fail, not try again Fix: Patch available and accepted by GNOME https://bugzilla.gnome.org/show_bug.cgi?id=637095 --- Original description --- After installing 9.10 Ubuntu 64bit browsing and opening folder in nautilus or Gnome-commander take several minutes when there are many files in it e.g. 10.000. Interestingly Midnight-commander does not have this problem. Opening such folders does not hang with MC. Using top i can see that gvfsd-metadata is using 100% CPU and when i kill it the computer stops hanging. I am using the 32bit version of Karmic too and there is no such Problem (although tested on a different computer). Please fix this because it is highly annyoing. Right now i am killing it every 20s with the watch command to be able to work at all. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/517021/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 517021] Re: gvfsd-metadata causes 100% CPU usage
** Attachment added: debdiff with the fix for Trusty https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/517021/+attachment/4380478/+files/gvfs-trusty-debdiff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/517021 Title: gvfsd-metadata causes 100% CPU usage Status in gvfs package in Ubuntu: Confirmed Status in gvfs package in Debian: Fix Released Bug description: Binary package hint: gvfs Failure to write metadata results in an infinite loop that keeps trying to write, thousands of times per second. Steps to reproduce: 1. Open Firefox 2. Save a data: URL (URL that contains the content, with several thousands bytes, often generated by webapps or extensions) as file (There are other ways to run into this problem, e.g. disk full or other error situations. data: URLs are just the easiest way to reproduce.) Actual result: - File is saved - 100% CPU - Extremely high number of file operations by gvfs - billions - Never stops Expected result: Failure to write metadata should just fail, not try again Fix: Patch available and accepted by GNOME https://bugzilla.gnome.org/show_bug.cgi?id=637095 --- Original description --- After installing 9.10 Ubuntu 64bit browsing and opening folder in nautilus or Gnome-commander take several minutes when there are many files in it e.g. 10.000. Interestingly Midnight-commander does not have this problem. Opening such folders does not hang with MC. Using top i can see that gvfsd-metadata is using 100% CPU and when i kill it the computer stops hanging. I am using the 32bit version of Karmic too and there is no such Problem (although tested on a different computer). Please fix this because it is highly annyoing. Right now i am killing it every 20s with the watch command to be able to work at all. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/517021/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 517021] Re: gvfsd-metadata causes 100% CPU usage
** Attachment added: debdiff with the fix for Utopic https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/517021/+attachment/4380502/+files/gvfs-utopic-debdiff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/517021 Title: gvfsd-metadata causes 100% CPU usage Status in gvfs package in Ubuntu: Confirmed Status in gvfs package in Debian: Fix Released Bug description: Binary package hint: gvfs Failure to write metadata results in an infinite loop that keeps trying to write, thousands of times per second. Steps to reproduce: 1. Open Firefox 2. Save a data: URL (URL that contains the content, with several thousands bytes, often generated by webapps or extensions) as file (There are other ways to run into this problem, e.g. disk full or other error situations. data: URLs are just the easiest way to reproduce.) Actual result: - File is saved - 100% CPU - Extremely high number of file operations by gvfs - billions - Never stops Expected result: Failure to write metadata should just fail, not try again Fix: Patch available and accepted by GNOME https://bugzilla.gnome.org/show_bug.cgi?id=637095 --- Original description --- After installing 9.10 Ubuntu 64bit browsing and opening folder in nautilus or Gnome-commander take several minutes when there are many files in it e.g. 10.000. Interestingly Midnight-commander does not have this problem. Opening such folders does not hang with MC. Using top i can see that gvfsd-metadata is using 100% CPU and when i kill it the computer stops hanging. I am using the 32bit version of Karmic too and there is no such Problem (although tested on a different computer). Please fix this because it is highly annyoing. Right now i am killing it every 20s with the watch command to be able to work at all. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/517021/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 517021] Re: gvfsd-metadata causes 100% CPU usage
Huh... it seems to be that old bug that I've posted a patch for... https://bugs.debian.org/756205#33 The debdiff will probably fail against Ubuntu version, so here's the original commit just in case: https://git.gnome.org/browse/gvfs/commit/?id=23341281b7e7f3d92ea1f3d6dffc156a8adb03bc ** Tags removed: 64bit freeze hang privacy ** Tags added: trusty ** Tags added: utopic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/517021 Title: gvfsd-metadata causes 100% CPU usage Status in gvfs package in Ubuntu: Confirmed Status in gvfs package in Debian: Fix Released Bug description: Binary package hint: gvfs Failure to write metadata results in an infinite loop that keeps trying to write, thousands of times per second. Steps to reproduce: 1. Open Firefox 2. Save a data: URL (URL that contains the content, with several thousands bytes, often generated by webapps or extensions) as file (There are other ways to run into this problem, e.g. disk full or other error situations. data: URLs are just the easiest way to reproduce.) Actual result: - File is saved - 100% CPU - Extremely high number of file operations by gvfs - billions - Never stops Expected result: Failure to write metadata should just fail, not try again Fix: Patch available and accepted by GNOME https://bugzilla.gnome.org/show_bug.cgi?id=637095 --- Original description --- After installing 9.10 Ubuntu 64bit browsing and opening folder in nautilus or Gnome-commander take several minutes when there are many files in it e.g. 10.000. Interestingly Midnight-commander does not have this problem. Opening such folders does not hang with MC. Using top i can see that gvfsd-metadata is using 100% CPU and when i kill it the computer stops hanging. I am using the 32bit version of Karmic too and there is no such Problem (although tested on a different computer). Please fix this because it is highly annyoing. Right now i am killing it every 20s with the watch command to be able to work at all. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/517021/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 517021] Re: gvfsd-metadata causes 100% CPU usage
How to reproduce the issue (and test if the patch works): https://bugzilla.gnome.org/show_bug.cgi?id=637095#c47 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/517021 Title: gvfsd-metadata causes 100% CPU usage Status in gvfs package in Ubuntu: Confirmed Status in gvfs package in Debian: Fix Released Bug description: Binary package hint: gvfs Failure to write metadata results in an infinite loop that keeps trying to write, thousands of times per second. Steps to reproduce: 1. Open Firefox 2. Save a data: URL (URL that contains the content, with several thousands bytes, often generated by webapps or extensions) as file (There are other ways to run into this problem, e.g. disk full or other error situations. data: URLs are just the easiest way to reproduce.) Actual result: - File is saved - 100% CPU - Extremely high number of file operations by gvfs - billions - Never stops Expected result: Failure to write metadata should just fail, not try again Fix: Patch available and accepted by GNOME https://bugzilla.gnome.org/show_bug.cgi?id=637095 --- Original description --- After installing 9.10 Ubuntu 64bit browsing and opening folder in nautilus or Gnome-commander take several minutes when there are many files in it e.g. 10.000. Interestingly Midnight-commander does not have this problem. Opening such folders does not hang with MC. Using top i can see that gvfsd-metadata is using 100% CPU and when i kill it the computer stops hanging. I am using the 32bit version of Karmic too and there is no such Problem (although tested on a different computer). Please fix this because it is highly annyoing. Right now i am killing it every 20s with the watch command to be able to work at all. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/517021/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 517021] Re: gvfsd-metadata causes 100% CPU usage
I'm not sure it'll be possible to backport the patch to Precise. The commit is from 1.20 branch, and Precise has 1.12... -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/517021 Title: gvfsd-metadata causes 100% CPU usage Status in gvfs package in Ubuntu: Confirmed Status in gvfs package in Debian: Fix Released Bug description: Binary package hint: gvfs Failure to write metadata results in an infinite loop that keeps trying to write, thousands of times per second. Steps to reproduce: 1. Open Firefox 2. Save a data: URL (URL that contains the content, with several thousands bytes, often generated by webapps or extensions) as file (There are other ways to run into this problem, e.g. disk full or other error situations. data: URLs are just the easiest way to reproduce.) Actual result: - File is saved - 100% CPU - Extremely high number of file operations by gvfs - billions - Never stops Expected result: Failure to write metadata should just fail, not try again Fix: Patch available and accepted by GNOME https://bugzilla.gnome.org/show_bug.cgi?id=637095 --- Original description --- After installing 9.10 Ubuntu 64bit browsing and opening folder in nautilus or Gnome-commander take several minutes when there are many files in it e.g. 10.000. Interestingly Midnight-commander does not have this problem. Opening such folders does not hang with MC. Using top i can see that gvfsd-metadata is using 100% CPU and when i kill it the computer stops hanging. I am using the 32bit version of Karmic too and there is no such Problem (although tested on a different computer). Please fix this because it is highly annyoing. Right now i am killing it every 20s with the watch command to be able to work at all. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/517021/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1286779] Re: Please migrate libjetty-extra-java to tomcat7
I confirm the issue is fixed in jetty 6.1.26-1ubuntu1.1. Now sudo apt-get install eclipse libjetty-extra does not show any dependency problems. ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to jetty in Ubuntu. https://bugs.launchpad.net/bugs/1286779 Title: Please migrate libjetty-extra-java to tomcat7 Status in One Hundred Papercuts: Fix Released Status in jetty package in Ubuntu: Fix Released Status in jetty source package in Trusty: Fix Committed Status in jetty package in Debian: Fix Released Bug description: libjetty-extra-java still depends on libtomcat6-java which prevents it from being installed alongside other programs which depend on tomcat7. According to the Debian bug report, Eclipse is among these programs. (Another it causes problems for is gradle which cannot currently be installed at the same time as tomcat7. Gradle's explicit dependency on tomcat6 has been removed (see bug 997743for details) and should have fixed it, but since gradle also depends on libjetty-extra-java the issue is still present. ) SRU for 14.04, debdiff in comment #11: [Impact] It is very hard to use this package in conjuction with relevant development tools because they depend on different versions on tomcat which means you can't install both. [Test case] For instance `sudo apt-get install eclipse libjetty-extra` will fail because eclipse wants tomcat7, but libjetty-extra-java currently needs tomcat6. [Regression potential] See analysis in comment #15 - there should not be regression potential. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: libjetty-extra-java 6.1.26-1ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-6.23-generic 3.13.0 Uname: Linux 3.13.0-6-generic i686 ApportVersion: 2.13.2-0ubuntu2 Architecture: i386 CurrentDesktop: Unity Date: Sun Mar 2 11:48:27 2014 InstallationDate: Installed on 2013-10-26 (127 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release i386 (20131021.1) PackageArchitecture: all SourcePackage: jetty UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1286779/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1441474] Re: gnome-keyring-daemon uses a lot of memory
** Also affects: gnome-keyring (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1441474 Title: gnome-keyring-daemon uses a lot of memory Status in The Linux Mint Distribution: New Status in gnome-keyring package in Ubuntu: New Bug description: 1) The version and edition of Linux Mint and version of gnome-keyring: $ cat /etc/lsb-release DISTRIB_ID=LinuxMint DISTRIB_RELEASE=17.1 DISTRIB_CODENAME=rebecca DISTRIB_DESCRIPTION=Linux Mint 17.1 Rebecca $ cinnamon --version Cinnamon 2.4.7 $ dpkg -l gnome-keyring Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==---= ii gnome-keyring 3.10.1-1ubun amd64GNOME keyring services (daemon an 2) How to reproduce it. Start one or more gnome-terminal sessions connected to remote server by ssh and leave them open for at least half an hour or more, e.g. snippet from pstree: |-gnome-terminal(404)-+-bash(463) | |-bash(4195) | |-bash(14698)---ssh(14759) | |-bash(16908) | |-bash(18025) | |-bash(19604) | |-bash(20717)---man(20779)---pager(20795) | |-bash(23307) | |-bash(23607)-+-less(24019) | | `-pstree(24018) 3) The result in an hour or more is gnome-kerying-daemon process is using almost 1/6 of all of the host memory: $ ps -p 32051 -o pcpu,pmem,pid,comm %CPU %MEM PID COMMAND 1.1 15.8 32051 gnome-keyring-d $ cat /proc/32051/cmdline /usr/bin/gnome-keyring-daemon--daemonize--login If freshly started it is using not more than 1MB or less. 4) The expected is to leave the session for days at a time without any need for gnome-keyring-daemon to be restarted. 5) The problem is reproducible always, just have to leave some terminals open for some time. Some remarks: - Tried to reproduce similar behaviour with Ubuntu 14.04 and 14.10 without success. - The same issue was reproducible also in Linux Mint 17 Qiana. In fact the host was upgraded from Quiana to Rebecca some months ago. - Logging out and log-in back resolves the issue as the keyring daemon is restarted. - Attempting to restart just the process results in: /usr/bin/gnome-keyring-daemon -r --daemonize ** Message: couldn't communicate with already running daemon: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. ** Message: Replacing daemon, using directory: /run/user/1000/keyring-PQyeQe GNOME_KEYRING_CONTROL=/run/user/1000/keyring-PQyeQe SSH_AUTH_SOCK=/run/user/1000/keyring-PQyeQe/ssh GPG_AGENT_INFO=/run/user/1000/keyring-PQyeQe/gpg:0:1 GNOME_KEYRING_PID=28477 Password unlock prompt opens for every gnome-terminal window or session opened. To manage notifications about this bug go to: https://bugs.launchpad.net/linuxmint/+bug/1441474/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1440449] Re: GIMP 2.8.10 bug causes severe data loss
** Also affects: gimp (Ubuntu) Importance: Undecided Status: New -- 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/1440449 Title: GIMP 2.8.10 bug causes severe data loss Status in The Linux Mint Distribution: New Status in gimp package in Ubuntu: New Bug description: The current version of GIMP in the repository used by Linux Mint 17.1 is version 2.8.10. This version has an exceptionally serious bug that can result in total loss of image data in an XCF file saved to an SMB share. Upon saving, this bug causes GIMP to corrupt the XCF file with added null bytes or in the worst case replace image data with null bytes. The user is given NO hint that anything has gone wrong. If she then closes that image file and then reopens it again, she will get what appears to be an empty image and a message Can't work on an empty image, add a layer first. This is bug 730211 on GNOME Bugzilla (https://bugzilla.gnome.org/show_bug.cgi?id=730211). Contrary to the experience of some posters in that report's discussion, this bug can irrevocably destroy the user's data. It is therefore of critical importance that the repository package be updated to a version of GIMP with this bug fixed. It seems there has been a bug fix despite that bug report not being closed. It seems the only reliable workaround for GIMP 2.8.10 is to NEVER save to an SMB share. To manage notifications about this bug go to: https://bugs.launchpad.net/linuxmint/+bug/1440449/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1440353] Re: can't join a hidden file to a thunderbird mail
** Also affects: thunderbird (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1440353 Title: can't join a hidden file to a thunderbird mail Status in The Linux Mint Distribution: New Status in thunderbird package in Ubuntu: New Bug description: I'm using Linux MINT + MATE + Mozilla Thunderbird. In a normal configuration, it's impossible to add a hidden file (beginning with .) to a mail with Mozilla Thunderbird. Mozilla Thunderbird open a GTK window to choose which file we want to join to a new mail and in this windows, hidden files don't appear, it's impossible to select one. See too : https://github.com/mate-desktop/caja/issues/399 https://bugzilla.mozilla.org/show_bug.cgi?id=1151096 To manage notifications about this bug go to: https://bugs.launchpad.net/linuxmint/+bug/1440353/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1439736] Re: libreOffice: PDF/A fobids transparency
** Also affects: libreoffice (Ubuntu) Importance: Undecided Status: New -- 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/1439736 Title: libreOffice: PDF/A fobids transparency Status in The Linux Mint Distribution: New Status in libreoffice package in Ubuntu: New Bug description: Mint17 kde 64-bit Problem happens with pretty much any document, including a blank page set to 7x9 with 1 inch margins. Click File-export PDF Check PDF/A box then click export/ok, choose file name, etc. Will create a PDF file which has actual content, but throws up error dialog stating: PDF/A forbids transparency. A transparent object was painted opaque instead. Happens every time. This also causes various printer drivers to crash/gag on documents thanks to Apple's worthless decision to use PDF instead of the incredibly stable Postscript standard. To manage notifications about this bug go to: https://bugs.launchpad.net/linuxmint/+bug/1439736/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1419346] Re: mintMenu is elevated/offset by compiz
Unfortunately, no. The result is the same as with [-1, -1] - as I described above. What's interesting is that MATE's Clock Applet isn't affected by this issue. When you click on it, it always shows the calendar window where it should be - close to the panel. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to compiz in Ubuntu. https://bugs.launchpad.net/bugs/1419346 Title: mintMenu is elevated/offset by compiz Status in Compiz: New Status in The Linux Mint Distribution: Confirmed Status in Ubuntu MATE: Confirmed Status in compiz package in Ubuntu: Confirmed Bug description: When I try to open the mint menu, it's elevated from the bottom mate panel somewhat. It should be seamless against the panel without any space. If you type text in the search box, it will reset to its proper position. If you click the menu after doing this, it will also appear to be normal. If you click it any more, it will go back to having a gap. I've attached an image showing this. This from what I've tested only seems to affect this plugin, and not the regular mate menu. Current setup: * OS: Arch linux * Desktop Environment: Mate * Window Manager: Compiz 0.9.12.1 * Window Decorator: Emerald 0.9 * Graphics card: GTX 760 * Driver: NVidia proprietary To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1419346/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1419346] Re: mintMenu is elevated/offset by compiz
** Tags added: trusty utopic vivid xfce -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to compiz in Ubuntu. https://bugs.launchpad.net/bugs/1419346 Title: mintMenu is elevated/offset by compiz Status in Compiz: New Status in The Linux Mint Distribution: Confirmed Status in Ubuntu MATE: Confirmed Status in compiz package in Ubuntu: Confirmed Bug description: When I try to open the mint menu, it's elevated from the bottom mate panel somewhat. It should be seamless against the panel without any space. If you type text in the search box, it will reset to its proper position. If you click the menu after doing this, it will also appear to be normal. If you click it any more, it will go back to having a gap. I've attached an image showing this. This from what I've tested only seems to affect this plugin, and not the regular mate menu. Current setup: * OS: Arch linux * Desktop Environment: Mate * Window Manager: Compiz 0.9.12.1 * Window Decorator: Emerald 0.9 * Graphics card: GTX 760 * Driver: NVidia proprietary To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1419346/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1419346] Re: mint menu is elevated/offset by compiz
Forgot to add that it's also been reported about mintMenu in Mint 17.1. https://github.com/linuxmint/mintmenu/issues/121 http://forums.linuxmint.com/viewtopic.php?f=206t=183895 ** Also affects: linuxmint Importance: Undecided Status: New ** Also affects: ubuntu-mate Importance: Undecided Status: New ** Also affects: compiz (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to compiz in Ubuntu. https://bugs.launchpad.net/bugs/1419346 Title: mintMenu is elevated/offset by compiz Status in Compiz: New Status in The Linux Mint Distribution: Confirmed Status in Ubuntu MATE: Confirmed Status in compiz package in Ubuntu: Confirmed Bug description: When I try to open the mint menu, it's elevated from the bottom mate panel somewhat. It should be seamless against the panel without any space. If you type text in the search box, it will reset to its proper position. If you click the menu after doing this, it will also appear to be normal. If you click it any more, it will go back to having a gap. I've attached an image showing this. This from what I've tested only seems to affect this plugin, and not the regular mate menu. Current setup: * OS: Arch linux * Desktop Environment: Mate * Window Manager: Compiz 0.9.12.1 * Window Decorator: Emerald 0.9 * Graphics card: GTX 760 * Driver: NVidia proprietary To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1419346/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1419346] Re: mintMenu is elevated/offset by compiz
** Summary changed: - mint menu is elevated/offset by compiz + mintMenu is elevated/offset by compiz ** Changed in: linuxmint Status: New = Confirmed ** Changed in: ubuntu-mate Status: New = Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to compiz in Ubuntu. https://bugs.launchpad.net/bugs/1419346 Title: mintMenu is elevated/offset by compiz Status in Compiz: New Status in The Linux Mint Distribution: Confirmed Status in Ubuntu MATE: Confirmed Status in compiz package in Ubuntu: Confirmed Bug description: When I try to open the mint menu, it's elevated from the bottom mate panel somewhat. It should be seamless against the panel without any space. If you type text in the search box, it will reset to its proper position. If you click the menu after doing this, it will also appear to be normal. If you click it any more, it will go back to having a gap. I've attached an image showing this. This from what I've tested only seems to affect this plugin, and not the regular mate menu. Current setup: * OS: Arch linux * Desktop Environment: Mate * Window Manager: Compiz 0.9.12.1 * Window Decorator: Emerald 0.9 * Graphics card: GTX 760 * Driver: NVidia proprietary To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1419346/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1430901] Re: mouse not working with chromium as of 41.0.2272.76
** Also affects: chromium-browser (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1430901 Title: mouse not working with chromium as of 41.0.2272.76 Status in The Linux Mint Distribution: New Status in chromium-browser package in Ubuntu: New Bug description: - Mouse over links doesn't work. - scrolling via click and drag of scroll bar doesn't work. If I downgrade, everything works normally. sudo dpkg -i /var/cache/apt/archives/chromium-browser_40.0.2214.111-0ubuntu0.14.04.1.1069_amd64.deb /var/cache/apt/archives/chromium-codecs-ffmpeg-extra_40.0.2214.111-0ubuntu0.14.04.1.1069_amd64.deb I thought it was my VM upgrade, but I downgraded that, and it wasn't. I use VirtualBox 4.3.20 r96997 win, and tried the newer VirtualBox-4.3.24-98716-Win, which also didn't work. I suspect it's entirely the browser, but thought I'd mention it just in case. To manage notifications about this bug go to: https://bugs.launchpad.net/linuxmint/+bug/1430901/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1321286] Re: After Installing latest Chromium and plugins in Mint 17 No plugins are listed.
** Also affects: chromium-browser (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1321286 Title: After Installing latest Chromium and plugins in Mint 17 No plugins are listed. Status in The Linux Mint Distribution: New Status in chromium-browser package in Ubuntu: New Bug description: Recently I installed Mint 17 and the latest version of Chromium. Once I installed all the usual plugins for Chromium they were not listed when checked with about:plugins. I removed Chromium and its associated folder and files and the re installed but this too had the same results. To verify the plugins, I installed Chrome and when checked, all the plugins could now be displayed. Is it possible to revert back to an earlier version of Chromium? To manage notifications about this bug go to: https://bugs.launchpad.net/linuxmint/+bug/1321286/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1432184] Re: going to Extensions of Settings crashes Chromium
** Also affects: chromium-browser (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1432184 Title: going to Extensions of Settings crashes Chromium Status in The Linux Mint Distribution: New Status in chromium-browser package in Ubuntu: New Bug description: Today is pi-day, 3-14-15 I am running LM17.1 Rebecca, Mate, 32-bit, on a Gateway T-Series Laptop, Model W3501. I just updated Chromium and the Codecs that were pushed. I open Chromium, go to Settings, go to Extensions to pull down httpseverywhere and the screen goes black and seems unresponsive. Holding down the on button and restarting the machine allows me to reproduce this condition. To manage notifications about this bug go to: https://bugs.launchpad.net/linuxmint/+bug/1432184/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1429279] Re: Evince -pdf close only using Force Quit
** Project changed: linuxmint = evince (Ubuntu) ** Tags added: trusty -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1429279 Title: Evince -pdf close only using Force Quit Status in evince package in Ubuntu: New Bug description: When using Evince to view PDFs it is working but closing PDFs causes Force Quit window to appear. Worked properly with 14.04.1 Problem always happens closing PDFs Using Ubuntu 14.04.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1429279/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1425879] Re: elitebook 840G1 restarts when he is told to shut down
** Changed in: evince (Ubuntu) Status: New = Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1425879 Title: elitebook 840G1 restarts when he is told to shut down Status in evince package in Ubuntu: Invalid Bug description: LTS 14.04 3.13.0-46 generic Has been so since about 1.13.0-38 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: evince 3.10.3-0ubuntu10.1 ProcVersionSignature: Ubuntu 3.13.0-46.75-generic 3.13.11-ckt15 Uname: Linux 3.13.0-46-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.7 Architecture: amd64 CurrentDesktop: Unity Date: Thu Feb 26 09:54:03 2015 InstallationDate: Installed on 2014-07-09 (231 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) SourcePackage: evince UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1425879/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1406239] Re: Evince PDF print generates blank pages on the printer.
*** This bug is a duplicate of bug 1397516 *** https://bugs.launchpad.net/bugs/1397516 ** This bug has been marked a duplicate of bug 1397516 Evince prints blank pages with attached PDF -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1406239 Title: Evince PDF print generates blank pages on the printer. Status in evince package in Ubuntu: New Bug description: I made a PDF (with two pages of content) and then wanted evince to print a copy of it. Out came two blank pages with a few dots here and there. I ran a test print for the printer, and it worked fine. I asked OKULAR to print the file, and it prints. Apparently the problem is with the latest version of evince. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: evince 3.14.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-28.38-generic 3.16.7-ckt1 Uname: Linux 3.16.0-28-generic i686 NonfreeKernelModules: wl ApportVersion: 2.14.7-0ubuntu8 Architecture: i386 CurrentDesktop: Unity Date: Mon Dec 29 15:45:58 2014 InstallationDate: Installed on 2011-10-20 (1166 days ago) InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release i386 (20111012) SourcePackage: evince UpgradeStatus: Upgraded to utopic on 2014-10-29 (60 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1406239/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1415320] Re: gedit acts like it has some internal runaway code active while a cut-buffer is active
** Package changed: evince (Ubuntu) = gedit (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1415320 Title: gedit acts like it has some internal runaway code active while a cut- buffer is active Status in gedit package in Ubuntu: New Bug description: I am a new user with Ubuntu, so there may be some misconfiguration involved that I am not aware of, nor have a clue of fixing. I would ask a support question if I could think of some way to ask it so that it doesn't sound like a bug report. I find it difficult to imagine that a mature program like gedit itself is buggy. I am using 14.10 pretty much as it came. I can view and type quite a bit without problem, but when I begin to cut and paste gedit begins to act flaky. The first symptom is an irratic cursor. It will effectively dissappear. Actually, it acts like it is too busy doing something else to paint the cursor. When I move the cursor with the mouse, I may see it occaisionally flash onto the screen. Editting may continue for a while, but the application's response gets progressively slower. Eventually the application terminates abnormally, and I loose my edit. Another symptom that occurs is my CPU fan kicks into high gear, like it is compensating for a heavy workload. When the problem occurs I can restore gedit to working order by saving the file I am editing, or by switching focus to another window and then back. I've used the browser, compiler, word processor, and terminal without incident. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: evince 3.14.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-29.39-generic 3.16.7-ckt2 Uname: Linux 3.16.0-29-generic x86_64 ApportVersion: 2.14.7-0ubuntu8.1 Architecture: amd64 CurrentDesktop: Unity Date: Tue Jan 27 23:37:00 2015 InstallationDate: Installed on 2015-01-22 (5 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: evince UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1415320/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1419050] Re: gnome-power-statistics crashed with SIGSEGV
** Changed in: gnome-power-manager (Ubuntu) Status: New = Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-power-manager in Ubuntu. https://bugs.launchpad.net/bugs/1419050 Title: gnome-power-statistics crashed with SIGSEGV Status in gnome-power-manager package in Ubuntu: Incomplete Bug description: This is reproduced on a laptop, AC power attached, and using a USB wireless mouse. To reproduce, click on the upper-right corner's mouse icon (appear when using USB wireless mouse) in indicator and Power Statitics window is opened. Click on Mouse tab, then click on Laptop Battery, and next AC power, and it crashes. ProblemType: Crash DistroRelease: Ubuntu 15.04 Package: gnome-power-manager 3.14.1-1ubuntu1 ProcVersionSignature: Ubuntu 3.18.0-11.12-generic 3.18.3 Uname: Linux 3.18.0-11-generic x86_64 ApportVersion: 2.16-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Sat Feb 7 00:07:34 2015 Disassembly: = 0x7fcb973afa49: Cannot access memory at address 0x7fcb973afa49 ExecutablePath: /usr/bin/gnome-power-statistics InstallationDate: Installed on 2015-01-28 (9 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20150127) ProcCmdline: gnome-power-statistics --device /org/freedesktop/UPower/devices/mouse_0003o046DoC52Fx0005 ProcEnviron: PATH=(custom, no user) SHELL=/bin/bash LANG=zh_CN.UTF-8 LANGUAGE=zh_CN: XDG_RUNTIME_DIR=set SegvAnalysis: Segfault happened at: 0x7fcb973afa49:Cannot access memory at address 0x7fcb973afa49 PC (0x7fcb973afa49) ok SP (0x7fff1602ac28) ok Reason could not be automatically determined. Signal: 11 SourcePackage: gnome-power-manager StacktraceTop: ?? () ?? () ?? () ?? () ?? () Title: gnome-power-statistics crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/1419050/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1351890] Re: Changing external screen resolution with dual monitors
Whoops, looks like there are two fixes actually, the second one is in https://git.gnome.org/browse/gtk%2B/commit/?id=22eb70adab72a5c14f063ea15f8195087ff1dcd8 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1351890 Title: Changing external screen resolution with dual monitors Status in GTK+ GUI Toolkit: Fix Released Status in Ubuntu MATE: Fix Released Status in gtk+2.0 package in Ubuntu: Fix Released Status in mate-control-center package in Ubuntu: Fix Released Status in gtk+2.0 package in Debian: Fix Released Bug description: Changing extrnal screen resolution with dual mon ProblemType: Crash DistroRelease: Ubuntu 14.10 Package: mate-control-center 1.8.1+dfsg1-4 ProcVersionSignature: Ubuntu 3.16.0-6.11-generic 3.16.0-rc7 Uname: Linux 3.16.0-6-generic i686 ApportVersion: 2.14.5-0ubuntu3 Architecture: i386 CrashCounter: 1 Date: Sun Aug 3 07:09:21 2014 ExecutablePath: /usr/bin/mate-display-properties InstallationDate: Installed on 2014-08-03 (0 days ago) InstallationMedia: Ubuntu MATE 14.10 Utopic Unicorn - Alpha i386 (20140731) ProcCmdline: mate-display-properties SegvAnalysis: Skipped: missing required field Disassembly Signal: 11 SourcePackage: mate-control-center UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1351890/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1351890] Re: Changing external screen resolution with dual monitors
Iain, I've seen you've added them in Debian Jessie and Ubuntu 15.04, thanks :) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1351890 Title: Changing external screen resolution with dual monitors Status in GTK+ GUI Toolkit: Fix Released Status in Ubuntu MATE: Fix Released Status in gtk+2.0 package in Ubuntu: Fix Released Status in mate-control-center package in Ubuntu: Fix Released Status in gtk+2.0 package in Debian: Fix Released Bug description: Changing extrnal screen resolution with dual mon ProblemType: Crash DistroRelease: Ubuntu 14.10 Package: mate-control-center 1.8.1+dfsg1-4 ProcVersionSignature: Ubuntu 3.16.0-6.11-generic 3.16.0-rc7 Uname: Linux 3.16.0-6-generic i686 ApportVersion: 2.14.5-0ubuntu3 Architecture: i386 CrashCounter: 1 Date: Sun Aug 3 07:09:21 2014 ExecutablePath: /usr/bin/mate-display-properties InstallationDate: Installed on 2014-08-03 (0 days ago) InstallationMedia: Ubuntu MATE 14.10 Utopic Unicorn - Alpha i386 (20140731) ProcCmdline: mate-display-properties SegvAnalysis: Skipped: missing required field Disassembly Signal: 11 SourcePackage: mate-control-center UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1351890/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1351890] Re: Changing external screen resolution with dual monitors
Sebastien, the new segfault seems to be fixed upstream in https://git.gnome.org/browse/gtk+/commit/?h=gtk-2-24id=5efefdb6550b3f00d5ca159c2ff74326bfd0e94b -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1351890 Title: Changing external screen resolution with dual monitors Status in GTK+ GUI Toolkit: Fix Released Status in Ubuntu MATE: Fix Released Status in gtk+2.0 package in Ubuntu: Fix Released Status in mate-control-center package in Ubuntu: Fix Released Status in gtk+2.0 package in Debian: Fix Released Bug description: Changing extrnal screen resolution with dual mon ProblemType: Crash DistroRelease: Ubuntu 14.10 Package: mate-control-center 1.8.1+dfsg1-4 ProcVersionSignature: Ubuntu 3.16.0-6.11-generic 3.16.0-rc7 Uname: Linux 3.16.0-6-generic i686 ApportVersion: 2.14.5-0ubuntu3 Architecture: i386 CrashCounter: 1 Date: Sun Aug 3 07:09:21 2014 ExecutablePath: /usr/bin/mate-display-properties InstallationDate: Installed on 2014-08-03 (0 days ago) InstallationMedia: Ubuntu MATE 14.10 Utopic Unicorn - Alpha i386 (20140731) ProcCmdline: mate-display-properties SegvAnalysis: Skipped: missing required field Disassembly Signal: 11 SourcePackage: mate-control-center UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1351890/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1351890] Re: Changing external screen resolution with dual monitors
Iain, did you mean I need to include the new fix in the debdiffs as well? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1351890 Title: Changing external screen resolution with dual monitors Status in GTK+ GUI Toolkit: Fix Released Status in Ubuntu MATE: Fix Released Status in gtk+2.0 package in Ubuntu: Fix Released Status in mate-control-center package in Ubuntu: Fix Released Status in gtk+2.0 package in Debian: Fix Released Bug description: Changing extrnal screen resolution with dual mon ProblemType: Crash DistroRelease: Ubuntu 14.10 Package: mate-control-center 1.8.1+dfsg1-4 ProcVersionSignature: Ubuntu 3.16.0-6.11-generic 3.16.0-rc7 Uname: Linux 3.16.0-6-generic i686 ApportVersion: 2.14.5-0ubuntu3 Architecture: i386 CrashCounter: 1 Date: Sun Aug 3 07:09:21 2014 ExecutablePath: /usr/bin/mate-display-properties InstallationDate: Installed on 2014-08-03 (0 days ago) InstallationMedia: Ubuntu MATE 14.10 Utopic Unicorn - Alpha i386 (20140731) ProcCmdline: mate-display-properties SegvAnalysis: Skipped: missing required field Disassembly Signal: 11 SourcePackage: mate-control-center UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1351890/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1351890] Re: Changing external screen resolution with dual monitors
Update what? The debdiffs are fine. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1351890 Title: Changing external screen resolution with dual monitors Status in GTK+ GUI Toolkit: Fix Released Status in Ubuntu MATE: Fix Released Status in gtk+2.0 package in Ubuntu: Fix Released Status in mate-control-center package in Ubuntu: Fix Released Status in gtk+2.0 package in Debian: Fix Released Bug description: Changing extrnal screen resolution with dual mon ProblemType: Crash DistroRelease: Ubuntu 14.10 Package: mate-control-center 1.8.1+dfsg1-4 ProcVersionSignature: Ubuntu 3.16.0-6.11-generic 3.16.0-rc7 Uname: Linux 3.16.0-6-generic i686 ApportVersion: 2.14.5-0ubuntu3 Architecture: i386 CrashCounter: 1 Date: Sun Aug 3 07:09:21 2014 ExecutablePath: /usr/bin/mate-display-properties InstallationDate: Installed on 2014-08-03 (0 days ago) InstallationMedia: Ubuntu MATE 14.10 Utopic Unicorn - Alpha i386 (20140731) ProcCmdline: mate-display-properties SegvAnalysis: Skipped: missing required field Disassembly Signal: 11 SourcePackage: mate-control-center UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1351890/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1419050] Re: gnome-power-statistics crashed with SIGSEGV
Aron, because it's not helpful (for developers) without a stacktrace. Actually, I suspect it's the same issue in upower which I fixed today. If you know how to rebuild packages, you can try it: http://paste.fedoraproject.org/192697/42539076/ For the sake of completeness, run the power statistics tool via gdb, then attach the full backtrace here. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-power-manager in Ubuntu. https://bugs.launchpad.net/bugs/1419050 Title: gnome-power-statistics crashed with SIGSEGV Status in gnome-power-manager package in Ubuntu: New Bug description: This is reproduced on a laptop, AC power attached, and using a USB wireless mouse. To reproduce, click on the upper-right corner's mouse icon (appear when using USB wireless mouse) in indicator and Power Statitics window is opened. Click on Mouse tab, then click on Laptop Battery, and next AC power, and it crashes. ProblemType: Crash DistroRelease: Ubuntu 15.04 Package: gnome-power-manager 3.14.1-1ubuntu1 ProcVersionSignature: Ubuntu 3.18.0-11.12-generic 3.18.3 Uname: Linux 3.18.0-11-generic x86_64 ApportVersion: 2.16-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Sat Feb 7 00:07:34 2015 Disassembly: = 0x7fcb973afa49: Cannot access memory at address 0x7fcb973afa49 ExecutablePath: /usr/bin/gnome-power-statistics InstallationDate: Installed on 2015-01-28 (9 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20150127) ProcCmdline: gnome-power-statistics --device /org/freedesktop/UPower/devices/mouse_0003o046DoC52Fx0005 ProcEnviron: PATH=(custom, no user) SHELL=/bin/bash LANG=zh_CN.UTF-8 LANGUAGE=zh_CN: XDG_RUNTIME_DIR=set SegvAnalysis: Segfault happened at: 0x7fcb973afa49:Cannot access memory at address 0x7fcb973afa49 PC (0x7fcb973afa49) ok SP (0x7fff1602ac28) ok Reason could not be automatically determined. Signal: 11 SourcePackage: gnome-power-manager StacktraceTop: ?? () ?? () ?? () ?? () ?? () Title: gnome-power-statistics crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/1419050/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1340067] Re: Drop 20_add_alt_screen_toggle_ui.patch - it does nothing with vte3 = 0.34.9
Brian, the checkbox is confusing because it does nothing. Users will expect it to change some parameter, but the alternate scroll is always turned on and won't be affected by that checkbox. -- 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/1340067 Title: Drop 20_add_alt_screen_toggle_ui.patch - it does nothing with vte3 = 0.34.9 Status in gnome-terminal package in Ubuntu: Fix Released Status in gnome-terminal source package in Trusty: New Status in gnome-terminal source package in Utopic: New Bug description: On 2013-09-30, the alternate scroll mode has been implemented in vte3 upstream [1]. In the same commit, vte_terminal_set_alternate_screen_scroll function has been added which does nothing and is there only for the compatibility with the previously patched Ubuntu's vte3 (the patch has been dropped in vte3 0.34.9-1ubuntu1). Since this function now does nothing, Ubuntu's 20_add_alt_screen_toggle_ui.patch for gnome-terminal does nothing too. It doesn't matter whether you turn the alt.scroll on or off in gnome- terminal's preferences window - the mouse scroll in console apps like man is ALWAYS turned on. Seems like it's always turned on in vte3 = 0.34.9 (again, see [1] for more info). So I propose to drop this 20_add_alt_screen_toggle_ui.patch since it's useless now. [1] https://git.gnome.org/browse/vte/commit/?id=9f8c1b88dcd880c2d9e78c93521ee755560a9275 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1340067/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1351890] Re: Changing external screen resolution with dual monitors
** Attachment added: debdiff for Utopic https://bugs.launchpad.net/ubuntu-mate/+bug/1351890/+attachment/4327235/+files/gtk2-utopic-debdiff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1351890 Title: Changing external screen resolution with dual monitors Status in GTK+ GUI Toolkit: Fix Released Status in Ubuntu MATE: Triaged Status in gtk+2.0 package in Ubuntu: Fix Released Status in mate-control-center package in Ubuntu: Confirmed Status in gtk+2.0 package in Debian: Confirmed Bug description: Changing extrnal screen resolution with dual mon ProblemType: Crash DistroRelease: Ubuntu 14.10 Package: mate-control-center 1.8.1+dfsg1-4 ProcVersionSignature: Ubuntu 3.16.0-6.11-generic 3.16.0-rc7 Uname: Linux 3.16.0-6-generic i686 ApportVersion: 2.14.5-0ubuntu3 Architecture: i386 CrashCounter: 1 Date: Sun Aug 3 07:09:21 2014 ExecutablePath: /usr/bin/mate-display-properties InstallationDate: Installed on 2014-08-03 (0 days ago) InstallationMedia: Ubuntu MATE 14.10 Utopic Unicorn - Alpha i386 (20140731) ProcCmdline: mate-display-properties SegvAnalysis: Skipped: missing required field Disassembly Signal: 11 SourcePackage: mate-control-center UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1351890/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1351890] Re: Changing external screen resolution with dual monitors
** Attachment added: debdiff for Precise https://bugs.launchpad.net/ubuntu-mate/+bug/1351890/+attachment/4327223/+files/gtk2-precise-debdiff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1351890 Title: Changing external screen resolution with dual monitors Status in GTK+ GUI Toolkit: Fix Released Status in Ubuntu MATE: Triaged Status in gtk+2.0 package in Ubuntu: Fix Released Status in mate-control-center package in Ubuntu: Confirmed Status in gtk+2.0 package in Debian: Confirmed Bug description: Changing extrnal screen resolution with dual mon ProblemType: Crash DistroRelease: Ubuntu 14.10 Package: mate-control-center 1.8.1+dfsg1-4 ProcVersionSignature: Ubuntu 3.16.0-6.11-generic 3.16.0-rc7 Uname: Linux 3.16.0-6-generic i686 ApportVersion: 2.14.5-0ubuntu3 Architecture: i386 CrashCounter: 1 Date: Sun Aug 3 07:09:21 2014 ExecutablePath: /usr/bin/mate-display-properties InstallationDate: Installed on 2014-08-03 (0 days ago) InstallationMedia: Ubuntu MATE 14.10 Utopic Unicorn - Alpha i386 (20140731) ProcCmdline: mate-display-properties SegvAnalysis: Skipped: missing required field Disassembly Signal: 11 SourcePackage: mate-control-center UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1351890/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1351890] Re: Changing external screen resolution with dual monitors
** Attachment added: debdiff for Trusty https://bugs.launchpad.net/ubuntu-mate/+bug/1351890/+attachment/4327234/+files/gtk2-trusty-debdiff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1351890 Title: Changing external screen resolution with dual monitors Status in GTK+ GUI Toolkit: Fix Released Status in Ubuntu MATE: Triaged Status in gtk+2.0 package in Ubuntu: Fix Released Status in mate-control-center package in Ubuntu: Confirmed Status in gtk+2.0 package in Debian: Confirmed Bug description: Changing extrnal screen resolution with dual mon ProblemType: Crash DistroRelease: Ubuntu 14.10 Package: mate-control-center 1.8.1+dfsg1-4 ProcVersionSignature: Ubuntu 3.16.0-6.11-generic 3.16.0-rc7 Uname: Linux 3.16.0-6-generic i686 ApportVersion: 2.14.5-0ubuntu3 Architecture: i386 CrashCounter: 1 Date: Sun Aug 3 07:09:21 2014 ExecutablePath: /usr/bin/mate-display-properties InstallationDate: Installed on 2014-08-03 (0 days ago) InstallationMedia: Ubuntu MATE 14.10 Utopic Unicorn - Alpha i386 (20140731) ProcCmdline: mate-display-properties SegvAnalysis: Skipped: missing required field Disassembly Signal: 11 SourcePackage: mate-control-center UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1351890/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1425493] Re: release 2.4 of network-manager-gnome causes greyed out Edit Connections... in nm-applet
** Project changed: linuxmint = network-manager-applet (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/1425493 Title: release 2.4 of network-manager-gnome causes greyed out Edit Connections... in nm-applet Status in network-manager-applet package in Ubuntu: New Bug description: Linux Mint 13 (Maya), MATE 64 bit edition. -r--r--r-- 1 root root 403974 Sep 21 20:30 network-manager-gnome_0.9.4.1-0ubuntu2.3_amd64.deb -r--r--r-- 1 root root 404006 Feb 5 15:18 network-manager-gnome_0.9.4.1-0ubuntu2.4_amd64.deb -r--r--r-- 1 root root 402358 Apr 3 2012 network-manager-gnome_0.9.4.1-0ubuntu2_amd64.deb On Feb 5, 2015, I ran update manager and it installed network- manager-gnome_0.9.4.1-0ubuntu2.4_amd64.deb. Afterwards, when I went to edit my network connections using the panel application launcher nm-applet, the Edit Connetions... text was greyed out. I was expecting it to be black and selectable. After some investigation, I downgraded network-manager-gnome to network-manager-gnome_0.9.4.1-0ubuntu2_amd64.deb and the nm-applet was corrected and back to normal. Again, I was able to consistently upgraded to 2.4 to replicate the problem and downgrade to 2 to correct it. This can possibly qualify as a desktop related issue, so I will open a bug in gethub.com also. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1425493/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1351890] Re: Changing external screen resolution with dual monitors
Thanks. Please apply the patch in Precise, Trusty and Utopic. ** Tags removed: vivid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1351890 Title: Changing external screen resolution with dual monitors Status in GTK+ GUI Toolkit: Fix Released Status in Ubuntu MATE: Triaged Status in gtk+2.0 package in Ubuntu: Fix Released Status in mate-control-center package in Ubuntu: Confirmed Status in gtk+2.0 package in Debian: Confirmed Bug description: Changing extrnal screen resolution with dual mon ProblemType: Crash DistroRelease: Ubuntu 14.10 Package: mate-control-center 1.8.1+dfsg1-4 ProcVersionSignature: Ubuntu 3.16.0-6.11-generic 3.16.0-rc7 Uname: Linux 3.16.0-6-generic i686 ApportVersion: 2.14.5-0ubuntu3 Architecture: i386 CrashCounter: 1 Date: Sun Aug 3 07:09:21 2014 ExecutablePath: /usr/bin/mate-display-properties InstallationDate: Installed on 2014-08-03 (0 days ago) InstallationMedia: Ubuntu MATE 14.10 Utopic Unicorn - Alpha i386 (20140731) ProcCmdline: mate-display-properties SegvAnalysis: Skipped: missing required field Disassembly Signal: 11 SourcePackage: mate-control-center UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1351890/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1340067] Re: Drop 20_add_alt_screen_toggle_ui.patch - it does nothing with vte3 = 0.34.9
Dmitry, it's not just useless, it also adds a confusing checkbox to the preferences dialog (confusing for users). -- 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/1340067 Title: Drop 20_add_alt_screen_toggle_ui.patch - it does nothing with vte3 = 0.34.9 Status in gnome-terminal package in Ubuntu: Fix Released Status in gnome-terminal source package in Trusty: New Status in gnome-terminal source package in Utopic: New Bug description: On 2013-09-30, the alternate scroll mode has been implemented in vte3 upstream [1]. In the same commit, vte_terminal_set_alternate_screen_scroll function has been added which does nothing and is there only for the compatibility with the previously patched Ubuntu's vte3 (the patch has been dropped in vte3 0.34.9-1ubuntu1). Since this function now does nothing, Ubuntu's 20_add_alt_screen_toggle_ui.patch for gnome-terminal does nothing too. It doesn't matter whether you turn the alt.scroll on or off in gnome- terminal's preferences window - the mouse scroll in console apps like man is ALWAYS turned on. Seems like it's always turned on in vte3 = 0.34.9 (again, see [1] for more info). So I propose to drop this 20_add_alt_screen_toggle_ui.patch since it's useless now. [1] https://git.gnome.org/browse/vte/commit/?id=9f8c1b88dcd880c2d9e78c93521ee755560a9275 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1340067/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1286779] Re: Please migrate libjetty-extra-java to tomcat7
I don't mind :) Well, libtomcat7-java conflicts with libtomcat6-java. So, the update of this dependency in libjetty-extra-java will remove libtomcat6-java and any packages that depend on it. That's the only regression I could think of. But then I've checked the dependencies with aptitude: monsta@mint17 ~ $ aptitude why libtomcat6-java i anacronRecommends rsyslog | system-log-daemon p syslog-ng-core Provides system-log-daemon p syslog-ng-core Suggests syslog-ng-mod-stomp p syslog-ng-mod-stompSuggests activemq p activemq Dependslibactivemq-java (= 5.6.0+dfsg-1) p libactivemq-java Dependslibspring-context-java p libspring-context-java Recommends libtomcat6-java So, it shows no packages that directly depend on libtomcat6-java. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to jetty in Ubuntu. https://bugs.launchpad.net/bugs/1286779 Title: Please migrate libjetty-extra-java to tomcat7 Status in One Hundred Papercuts: Fix Released Status in jetty package in Ubuntu: Fix Released Status in jetty package in Debian: Fix Released Bug description: libjetty-extra-java still depends on libtomcat6-java which prevents it from being installed alongside other programs which depend on tomcat7. According to the Debian bug report, Eclipse is among these programs. (Another it causes problems for is gradle which cannot currently be installed at the same time as tomcat7. Gradle's explicit dependency on tomcat6 has been removed (see bug 997743for details) and should have fixed it, but since gradle also depends on libjetty-extra-java the issue is still present. ) SRU for 14.04: [Impact] It is very hard to use this package in conjuction with relevant development tools because they depend on different versions on tomcat which means you can't install both. [Test case] For instance `sudo apt-get install eclipse libjetty-extra` will fail because eclipse wants tomcat7, but libjetty-extra-java currently needs tomcat6. [Regression potential] ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: libjetty-extra-java 6.1.26-1ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-6.23-generic 3.13.0 Uname: Linux 3.13.0-6-generic i686 ApportVersion: 2.13.2-0ubuntu2 Architecture: i386 CurrentDesktop: Unity Date: Sun Mar 2 11:48:27 2014 InstallationDate: Installed on 2013-10-26 (127 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release i386 (20131021.1) PackageArchitecture: all SourcePackage: jetty UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1286779/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1340067] Re: Drop 20_add_alt_screen_toggle_ui.patch - it does nothing with vte3 = 0.34.9
Attached a simple debdiff which removes the obsolete patch. ** Attachment added: This debdiff removes the useless patch. https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1340067/+attachment/4320368/+files/gt-debdiff -- 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/1340067 Title: Drop 20_add_alt_screen_toggle_ui.patch - it does nothing with vte3 = 0.34.9 Status in gnome-terminal package in Ubuntu: Confirmed Bug description: On 2013-09-30, the alternate scroll mode has been implemented in vte3 upstream [1]. In the same commit, vte_terminal_set_alternate_screen_scroll function has been added which does nothing and is there only for the compatibility with the previously patched Ubuntu's vte3 (the patch has been dropped in vte3 0.34.9-1ubuntu1). Since this function now does nothing, Ubuntu's 20_add_alt_screen_toggle_ui.patch for gnome-terminal does nothing too. It doesn't matter whether you turn the alt.scroll on or off in gnome- terminal's preferences window - the mouse scroll in console apps like man is ALWAYS turned on. Seems like it's always turned on in vte3 = 0.34.9 (again, see [1] for more info). So I propose to drop this 20_add_alt_screen_toggle_ui.patch since it's useless now. [1] https://git.gnome.org/browse/vte/commit/?id=9f8c1b88dcd880c2d9e78c93521ee755560a9275 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1340067/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
