Bug#681315: still not fixed?!
Control: tags -1 wheezy jessie stretch This utterly absurd issue has been fixed in Ubuntu almost 3 years ago [1] by committing a simple patch, but the bug is still here, in all Debian releases. Is this package even maintained these days? [1] https://bugs.launchpad.net/bugs/1071915
Bug#786395: drag and drop to bookmarks in side pane does not work
Source: caja Version: 1.8.2-3 Severity: normal Tags: jessie stretch sid upstream fixed-upstream Control: forwarded -1 https://github.com/mate-desktop/caja/issues/345 Currently you can't drag'n'drop files to the bookmarks that are shown in the left side pane in Caja 1.8.x. The upstream commit [1] fixes that. [1] https://github.com/mate-desktop/caja/commit/ec0c8f4143d900db6968b5a73a45a08a925b6f06
Bug#785611: a typo in aptoncd.desktop file
Source: aptoncd Version: 0.1.98+bzr117-1.4 Severity: minor The .desktop file has a typo in Comment section and in its translation for en_CA locale: Comment=Create a Installation Disc Comment[en_CA]=Create a Installation Disc It should be: Create an Installation Disc It's interesting that the translation for en_GB locale is ok: Comment[en_GB]=Create an Installation Disc
Bug#783162: mate-screenshot shows wrong error message when UI load fails
Source: mate-utils Version: 1.8.1+dfsg1-2 Severity: important Tags: jessie sid When the loading of UI file fails for some reason, mate-screenshot always shows the message that says UI file is missing. This is incorrect. As you can see in the upstream bug report [1], the reporter got this message but the UI file was actually there. In order to show the real cause of the error, mate-screenshot needs to be patched. The patch is available in the upstream pull request [2]. [1] https://github.com/mate-desktop/mate-utils/issues/97 [2] https://github.com/mate-desktop/mate-utils/pull/98
Bug#763669: adwaita-icon-theme: circular dependency hell
Hi Michael, Not release critical. Restoring previous severity. Are you sure? This might break Wheezy - Jessie upgrades...
Bug#763669: adwaita-icon-theme: circular dependency hell
tags 763669 jessie sid severity 763669 serious thanks Half a year passed, Jessie is getting close to release, and this is still not fixed?! Come on.
Bug#782189: marco doesn't receive keybindings change notifications with GLib = 2.43
Source: marco Version: 1.8.2+dfsg1-6 Severity: important With the latest GLib changes [1], if an app reads some data from GSettings before connecting there, it actually won't receive any notifications from GSettings afterwards. The issue was partially fixed for Marco (see [2]), but it turned out that the keybindings change notifications still didn't work. It was caused by using different instances of GSettings for listening to the changes and reading the values. The upstream pull request [3] fixes this issue for Marco, making the keybindings change notifications work with GLib = 2.43. [1] https://git.gnome.org/browse/glib/commit/?id=8ff5668a458344da22d30491e3ce726d861b3619 [2] https://bugs.debian.org/778694 [3] https://github.com/mate-desktop/marco/pull/190
Bug#782194: marco does not apply workspace name changes
Source: marco Version: 1.8.2+dfsg1-6 Severity: important Tags: jessie sid Due to a logic error, Marco does not apply workspace name changes when it receives the notifications for them. This happens with any version of GLib, it's not related to the known GLib 2.43 issue. The upstream pull request [1] fixes the problem. [1] https://github.com/mate-desktop/marco/pull/188
Bug#781303: no Set Preferred Applications in Common Tasks in Russian and Ukrainian locales
Source: mate-control-center Version: 1.8.3+dfsg1-1 Severity: important Tags: jessie sid upstream patch Control: forwarded -1 https://github.com/mate-desktop/mate-control-center/issues/154 Due to the wrong .desktop file name in Russian and Ukrainian .po files, m-c-c cannot find that file and therefore does not show Set Preferred Applications in the Common Tasks on the left pane. If you run m-c-c from the terminal in one of these locales, you'll see an error message: ** (mate-control-center:9674): WARNING **: get_actions_list() - PROBLEM - Can't load mate-default-applications.desktop The patch that fixes the issue is in the attachment.Index: mate-control-center-1.8.3+dfsg1/po/ru.po === --- mate-control-center-1.8.3+dfsg1.orig/po/ru.po +++ mate-control-center-1.8.3+dfsg1/po/ru.po @@ -31,7 +31,7 @@ msgstr msgid [ 'Change Theme;mate-appearance-properties.desktop', 'Set Preferred Applications;mate-default-applications-properties.desktop' ] -msgstr [ 'Изменить тему;mate-appearance-properties.desktop', 'Выставить предпочтительные приложения;mate-default-applications.desktop'] +msgstr [ 'Изменить тему;mate-appearance-properties.desktop', 'Выставить предпочтительные приложения;mate-default-applications-properties.desktop'] #: ../org.mate.control-center.gschema.xml.in.in.h:2 msgid Task names and associated .desktop files Index: mate-control-center-1.8.3+dfsg1/po/uk.po === --- mate-control-center-1.8.3+dfsg1.orig/po/uk.po +++ mate-control-center-1.8.3+dfsg1/po/uk.po @@ -28,7 +28,7 @@ msgstr msgid [ 'Change Theme;mate-appearance-properties.desktop', 'Set Preferred Applications;mate-default-applications-properties.desktop' ] -msgstr [ 'Змінити тему;mate-appearance-properties.desktop', 'Виставити бажані додатки;mate-default-applications.desktop'] +msgstr [ 'Змінити тему;mate-appearance-properties.desktop', 'Виставити бажані додатки;mate-default-applications-properties.desktop'] #: ../org.mate.control-center.gschema.xml.in.in.h:2 msgid Task names and associated .desktop files
Bug#781316: please build m-s-a with nvidia sensors support
Source: mate-sensors-applet Version: 1.8.0+dfsg1-1 Severity: wishlist Since libxnvctrl0 and libxnvctrl-dev are in the main section (rather than contrib), m-s-a can be safely built with nvidia sensors support without the need to move it to contrib. It will require a simple build-dep on libxnvctrl-dev and a new mate-sensors-applet-nvidia binary package which will depend on libxnvctrl0. No nvidia-settings (which is in contrib) required.
Bug#781246: desktop item launcher is flawed
Source: mate-desktop Version: 1.8.1+dfsg1-2 Severity: normal As stated in GLib docs [1], running g_spawn_async with G_SPAWN_DO_NOT_REAP_CHILD flag requires adding a child watch function like g_child_watch_add afterwards to prevent the child from becoming a zombie. Current desktop item launcher does not do that. It even ignores the child PID completely, regardless of the result of the function call. The upstream pull request [2] fixes the issue. [1] https://developer.gnome.org/glib/stable/glib-Spawning-Processes.html#GSpawnFlags [2] https://github.com/mate-desktop/mate-desktop/pull/167
Bug#781247: some applications with pkexec cannot be started from m-c-c
Source: mate-control-center Version: 1.8.3+dfsg1-1 Severity: normal Tags: upstream jessie sid Control: forwarded -1 https://github.com/mate-desktop/mate-control-center/issues/51 Applications whose .desktop files have exec pkexec ... command cannot be started from m-c-c. The upstream pull request [1] fixes the issue by setting the do not reap child flag when calling the desktop item launcher. Note that the fix will only work if the fix from [2] is applied first. [1] https://github.com/mate-desktop/mate-control-center/pull/153 [2] https://bugs.debian.org/781246
Bug#780844: mate-power-statistics crashes when you unplug a wireless device which has a battery
Source: mate-power-manager Version: 1.8.1+dfsg1-4 Severity: important Due to an incompatibility with upower 0.99 (API has been changed), mate-power-statistics crashes when you unplug a wireless device which has a battery (e.g. mouse). Steps to reproduce: 1. Attach a wireless mouse to your laptop (e.g. Logitech M235, M525). 2. Start mate-power-statistics. It will show info about both the laptop battery power level and the mouse battery power level. 3. Unplug the mouse's wireless dongle. 4. mate-power-statistics crashes. It has been reported that it can be reproduced on a desktop as well (with just a wireless mouse). Note: your wireless device should be able to report power statistics, or else you might not be able to reproduce the issue. The upstream pull request [1] fixes the problem. It has been tested by several users with various wireless mice on both laptops and desktops. [1] https://github.com/mate-desktop/mate-power-manager/pull/133
Bug#780780: various parts of mate-media don't receive GSettings notifications with GLib = 2.43
Source: mate-media Version: 1.8.0+dfsg1-3 Severity: important Tags: jessie sid With the latest GLib changes [1], if an app reads some data from GSettings before connecting there, it actually won't receive any notifications from GSettings afterwards. The upstream pull request [2] fixes the issue for various parts of mate-media, making them connect to GSettings before reading the data. [1] https://git.gnome.org/browse/glib/commit/?id=8ff5668a458344da22d30491e3ce726d861b3619 [2] https://github.com/mate-desktop/mate-media/pull/58
Bug#780791: filebrowser plugin doesn't receive GSettings notifications with GLib = 2.43
Source: pluma Version: 1.8.1+dfsg1-2 Severity: important Tags: jessie sid With the latest GLib changes [1], if an app reads some data from GSettings before connecting there, it actually won't receive any notifications from GSettings afterwards. The upstream pull request [2] fixes the issue for Pluma's filebrowser plugin, making it connect to GSettings before reading the data. [1] https://git.gnome.org/browse/glib/commit/?id=8ff5668a458344da22d30491e3ce726d861b3619 [2] https://github.com/mate-desktop/pluma/pull/110
Bug#780731: caja crashes after usb drive eject if any bookmarks are present
Source: caja Version: 1.8.2-2 Severity: important Tags: jessie sid Steps to reproduce (from LP bug [1]): --- To reproduce the bug you need : A usb stick connected and recognized in caja and at least one bookmark appearing in the left side of caja, normally the bookmark will appear under the usb stick 1) in the caja window appearing when the usb stick in inserted, click on the eject button to unmount the usb stick = a bug makes the bookmark sticking to the pointer (to see it move the pointer a little bit 2) place the sticky bookmark in front of its real place (the sticky bookmark is supposed to be right in front of the real bookmark) 3) click = caja crashes --- The upstream pull request [2] should fix it. [1] https://bugs.launchpad.net/bugs/1377967 [2] https://github.com/mate-desktop/caja/pull/396
Bug#780500: atril: warning message directs user to non-existent URL
Hi, I've sent a pull request with the fix upstream: https://github.com/mate-desktop/atril/pull/133
Bug#780580: group names in m-c-c are not localized
Source: mate-control-center Version: 1.8.3+dfsg1-1 Severity: normal Tags: jessie sid upstream Control: forwarded -1 https://github.com/mate-desktop/mate-control-center/issues/108 As you can see on the screenshot in the upstream bug report, group names in m-c-c are not localized. This is easily fixed by a commit [1] which is proposed to be accepted upstream. I've tested that commit in Jessie - works perfectly. The patch is very small and does not require any additional dependencies because m-c-c already depends on mate-menus. In fact, you can even apply this patch without rebuilding the package - just apply it to /etc/xdg/menus/matecc.menu file. [1] https://github.com/rezso/mate-control-center/commit/5ebc88406f51fe36bfb03319f1d4fb5edb55
Bug#774546: fixed in upower 0.99.2-2
Hi Martin, Thanks for pushing the fix. Can you please patch upower in Jessie (0.99.1-3.1) as well? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#780399: m-s-d crashes due to unsafe access to list elements
Source: mate-settings-daemon Version: 1.8.2-1 Severity: important Tags: jessie upstream Control: forwarded -1 https://github.com/mate-desktop/mate-settings-daemon/issues/67 Due to unsafe access to list elements, m-s-d tries to dereference NULL pointer and crashes. The upstream pull request [1] should fix the issue. [1] https://github.com/mate-desktop/mate-settings-daemon/pull/101
Bug#780333: mate-search-tool and mate-disk-usage-analyzer don't receive GSettings notifications with GLib = 2.43
Source: mate-utils Version: 1.8.1+dfsg1-2 Severity: important Tags: jessie sid With the latest GLib changes [1], if an app reads some data from GSettings before connecting there, it actually won't receive any notifications from GSettings afterwards. The upstream pull request [2] fixes the issue for mate-search-tool and mate-disk-usage-analyzer , making them connect to GSettings before reading the data. [1] https://git.gnome.org/browse/glib/commit/?id=8ff5668a458344da22d30491e3ce726d861b3619 [2] https://github.com/mate-desktop/mate-utils/pull/95
Bug#772125: policykit-1: patch - work around systemd injecting broken XDG_RUNTIME_DIR
Hi Simon, Well, it's easy to find the answer if you look at the mentioned upstream commit. It's a workaround for the notorious bug [1] which upstream systemd developers still refuse to fix. True, there was some patch in systemd 204, but since then a lot of versions passed by, and it seems that the latest systemd versions still set XDG_RUNTIME_DIR to the wrong value sometimes. The most known consequence of it is the impact on dconf, which makes various user-level software behave wrong (e.g. eat 100% CPU or a lot of memory, freeze completely, etc.) [2][3][4][5][6]. [1] https://bugzilla.redhat.com/show_bug.cgi?id=753882 [2] https://bugs.debian.org/732209 [3] https://bugs.debian.org/766464 [4] https://bugs.debian.org/767173 [5] https://bugs.debian.org/769889 [6] https://bugs.debian.org/772910
Bug#780205: patch - fix crash with long one-line XML documents
Source: gtksourceview2 Version: 2.10.5-2 Severity: important Tags: jessie sid patch upstream Control: forwarded -1 https://bugzilla.gnome.org/show_bug.cgi?id=607677 Control: affects -1 pluma Steps to reproduce: 1. Open a long one-line XML document (e.g. [1]) 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 [2]. 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). This has been reported upstream and fixed in [3], but the commit never made it to GTK+2 version of gtksourceview. I've made a patch from that commit, it applies cleanly to the current version of gtksourceview2 in Jessie and actually fixes the crash. The debdiff is in the attachment. Hope to see it accepted soon. Thanks in advance. [1] http://pastebin.com/nNdYzFXE [2] http://pastebin.com/YgDT0iKh [3] https://git.gnome.org/browse/gtksourceview/commit/?id=abef41da8c541c814bf631f69c92e0c431c610ad gsv-debdiff Description: Binary data
Bug#778824: fixed in marco 1.8.2+dfsg1-5
Hi Mike, Please also include the second PR which I mentioned in the comment, https://github.com/mate-desktop/marco/pull/179 It does the same as the first one, but for the preview widget. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#779916: m-s-d segfaults when you click on a11y tray icon
Hi Mike, I presume this is a follow-up of #775212 [1]? Oh, I actually never saw that one. Well, these patches actually never made it to 1.8 branch upstream. They're in the master branch. As opposed to that, my PR cleanly applies to 1.8 branch as it modifies the file that exists there (plugins/a11y-keyboard/msd-a11y-preferences-dialog.c). -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#774546: [segfault] gnome-power-statistics crashes easily.
reassign 774546 upower 0.99.1-3.1 tags 774546 - moreinfo + jessie sid severity 774546 important affects 774546 gnome-power-manager mate-power-manager retitle 774546 uninitialized pointer causes segfault thanks Hi, Thanks for testing and confirming the fix. I'm reassigning the bug to upower and will attach the debdiff with the fix later.
Bug#774546: patch - NULL-initialize two pointers, avoid crash
Hi, Two uninitialized pointers in upower's code cause segfault of gnome-power-statistics and mate-power-statistics in some situations (steps to reproduce are described above in the original report). The attached debdiff fixes that. Hope to see it accepted soon. Thanks in advance. up-debdiff Description: Binary data
Bug#779916: m-s-d segfaults when you click on a11y tray icon
Source: mate-settings-daemon Version: 1.8.2-1 Severity: important Tags: jessie sid upstream Control: forwarded -1 https://github.com/mate-desktop/mate-settings-daemon/issues/70 If you toggle the enable key in org.mate.accessibility-keyboard schema and then click on the icon that shows up in the notification area, m-s-d will segfault. In some systems it didn't happen right after clicking on the icon, but rather after clicking on any checkbox in the dialog that shows up. In either case, the upstream pull request [1] fixes the problem. [1] https://github.com/mate-desktop/mate-settings-daemon/pull/97
Bug#779870: mate-notification-daemon: Notifications fly away
Hi, PS: m-n-d kept using ca. 60% of the CPU, I had to kill the process (I only realised that some time later, because of fan noise). Can you check the ownership of /run/user/1000/dconf/user file when m-n-d starts eating CPU? Is it owned by you or by root:root? Also check whether ~/.xsession-errors file contains any messages like this: dconf-CRITICAL **: unable to create file '/run/user/1000/dconf/user' -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#779821: m-u-s has a memleak and an out-of-bounds array access
Source: mate-user-share Version: 1.8.0+dfsg1-2 Severity: important Tags: jessie sid If bluetooth is disabled in the build, there's a logic flaw in Caja extension that leads to an out-of-bounds array access. Also there's a memleak in the http backend. Both issues are fixed in the upstream pull request [1]. There's no dedicated 1.8 branch upstream but I think these changed can be safely applied to 1.8. [1] https://github.com/mate-desktop/mate-user-share/pull/22
Bug#779829: maximus doesn't receive GSettings notifications with GLib = 2.43
Source: mate-netbook Version: 1.8.1-3 Severity: important With the latest GLib changes [1], if an app reads some data from GSettings before connecting there, it actually won't receive any notifications from GSettings afterwards. The upstream pull request [2] fixes the issue for maximus, making it connect to GSettings before reading the data. [1] https://git.gnome.org/browse/glib/commit/?id=8ff5668a458344da22d30491e3ce726d861b3619 [2] https://github.com/mate-desktop/mate-netbook/pull/20
Bug#779856: mate-dictionary has double-free error
Source: mate-utils Version: 1.8.1+dfsg1-1 Severity: important Tags: jessie sid Due to a logic flaw, mate-dictionary tool tries to free the same memory twice, leading to a crash. The upstream pull request [1] fixes that. [1] https://github.com/mate-desktop/mate-utils/pull/90
Bug#779848: atril forgets to unlock a locked mutex
Source: atril Version: 1.8.1+dfsg1-3 Severity: important At one point in the code it forgets to unlock a locked mutex. That might lead to unwanted consequences in some other parts of code. The upstream pull request [1] fixes that. [1] https://github.com/mate-desktop/atril/pull/129
Bug#779850: m-u-s doesn't receive GSettings notifications with GLib = 2.43
Source: mate-user-share Version: 1.8.0+dfsg1-2 Severity: important Tags: jessie sid With the latest GLib changes [1], if an app reads some data from GSettings before connecting there, it actually won't receive any notifications from GSettings afterwards. The upstream pull request [2] fixes the issue for m-u-s, making it connect to GSettings before reading the data. [1] https://git.gnome.org/browse/glib/commit/?id=8ff5668a458344da22d30491e3ce726d861b3619 [2] https://github.com/mate-desktop/mate-user-share/pull/29
Bug#779854: GList extensions in mate-panel have a NULL pointer dereference
Source: mate-panel Version: 1.8.1+dfsg1-3 Severity: important Tags: jessie sid Due to a logic flaw, one of GList extensions in mate-panel has a NULL pointer dereference (in case the element isn't found in the list). The upstream pull request [1] fixes that. [1] https://github.com/mate-desktop/mate-panel/pull/288
Bug#779719: m-p-m does not handle UP_DEVICE_STATE_UNKNOWN device state
Source: mate-power-manager Version: 1.8.1+dfsg1-3 Severity: important Tags: jessie sid The upower-related code in m-p-m does not handle UP_DEVICE_STATE_UNKNOWN device state. It leads to an assert (and program abort) if such state is received. The upstream pull request [1] fixes that. [1] https://github.com/mate-desktop/mate-power-manager/pull/131
Bug#774546: [segfault] gnome-power-statistics crashes easily.
tags 774546 moreinfo thanks Hi, Please run bt full in gdb prompt right after the crash and post the result.
Bug#774546: Re[2]: [segfault] gnome-power-statistics crashes easily.
Hi, Okay, it looks familiar. Can you try rebuilding upower with the patch from [1] and check whether the crash still happens with the patched upower? [1] http://paste.fedoraproject.org/192697/42539076/
Bug#779570: mate-desktop doesn't receive GSettings notifications with GLib = 2.43
Source: libmatekbd Version: 1.8.1+dfsg1-2 Severity: important With the latest GLib changes [1], if an app reads some data from GSettings before connecting there, it actually won't receive any notifications from GSettings afterwards. The upstream pull request [2] fixes the issue for mate-desktop, making it connect to GSettings before reading the data. [1] https://git.gnome.org/browse/glib/commit/?id=8ff5668a458344da22d30491e3ce726d861b3619 [2] https://github.com/mate-desktop/mate-desktop/pull/163
Bug#779570: whoops
reassign 779570 mate-desktop 1.8.1+dfsg1-2 thanks Dammit, that's what happens when you do copy/paste while being tired at work. :)
Bug#778824: marco tries to load incorrect missing icon and might abort
A similar fix is needed for the preview widget: https://github.com/mate-desktop/marco/pull/179
Bug#779095: libmatekbd doesn't receive GSettings notifications with GLib = 2.43
Source: libmatekbd Version: 1.8.0-2 Severity: important With the latest GLib changes [1], if an app reads some data from GSettings before connecting there, it actually won't receive any notifications from GSettings afterwards. The upstream pull request [2] fixes the issue for libmatekbd, making it connect to GSettings before reading the data. It's filed against git master but should apply cleanly to 1.8.x as well (there's no 1.8 branch upstream). [1] https://git.gnome.org/browse/glib/commit/?id=8ff5668a458344da22d30491e3ce726d861b3619 [2] https://github.com/mate-desktop/libmatekbd/pull/22
Bug#778824: marco tries to load incorrect missing icon and might abort
Source: marco Version: 1.8.2+dfsg1-4 Severity: important Tags: jessie sid Marco tries to load the gtk-missing-image icon instead of image-missing one. If that icon isn't present in the current icon theme, an assert will trigger the abort of Marco. The upstream pull request [1] fixes the issue. [1] https://github.com/mate-desktop/marco/pull/177
Bug#778826: m-s-m patch contains a typo
Source: mate-session-manager Version: 1.8.1-7 Severity: minor Tags: jessie sid patch 0001_msmgnome-Allow-users-to-disable-one-or-both-compatib.patch contains a typo (componnent instead of component). Attaching a patch for this patch :) that fixes it.diff -Nru mate-session-manager-1.8.1/debian/patches/0001_msmgnome-Allow-users-to-disable-one-or-both-compatib.patch mate-session-manager-1.8.1/debian/patches/0001_msmgnome-Allow-users-to-disable-one-or-both-compatib.patch --- mate-session-manager-1.8.1/debian/patches/0001_msmgnome-Allow-users-to-disable-one-or-both-compatib.patch 2015-01-21 14:32:27.0 +0300 +++ mate-session-manager-1.8.1/debian/patches/0001_msmgnome-Allow-users-to-disable-one-or-both-compatib.patch 2015-02-20 13:52:15.0 +0300 @@ -9,26 +9,26 @@ mate-session/msm-gnome.c| 41 + 2 files changed, 41 insertions(+), 5 deletions(-) -diff --git a/data/org.mate.session.gschema.xml.in.in b/data/org.mate.session.gschema.xml.in.in -index 2415c67..14e8da4 100644 a/data/org.mate.session.gschema.xml.in.in -+++ b/data/org.mate.session.gschema.xml.in.in +Index: mate-session-manager-1.8.1/data/org.mate.session.gschema.xml.in.in +=== +--- mate-session-manager-1.8.1.orig/data/org.mate.session.gschema.xml.in.in mate-session-manager-1.8.1/data/org.mate.session.gschema.xml.in.in @@ -30,6 +30,11 @@ _summaryRequired session components/_summary _descriptionList of components that are required as part of the session. (Each element names a key under /org/mate/desktop/session/required_components). The Startup Applications preferences tool will not normally allow users to remove a required component from the session, and the session manager will automatically add the required components back to the session at login time if they do get removed./_description /key +key name=gnome-compat-startup type=as + default[ 'keyring', 'smproxy' ]/default -+ _summaryControl gnome compatibility componnent startup/_summary ++ _summaryControl gnome compatibility component startup/_summary + _descriptionControl which compatibility components to start./_description +/key child name=required-components schema=org.mate.session.required-components/ /schema schema id=org.mate.session.required-components path=/org/mate/desktop/session/required-components/ -diff --git a/mate-session/msm-gnome.c b/mate-session/msm-gnome.c -index 661d9e3..72f5493 100644 a/mate-session/msm-gnome.c -+++ b/mate-session/msm-gnome.c +Index: mate-session-manager-1.8.1/mate-session/msm-gnome.c +=== +--- mate-session-manager-1.8.1.orig/mate-session/msm-gnome.c mate-session-manager-1.8.1/mate-session/msm-gnome.c @@ -37,9 +37,13 @@ #include gtk/gtk.h
Bug#778817: mate-session might crash if no required applications found
Source: mate-session-manager Version: 1.8.1-7 Severity: important Tags: jessie sid Due to a logic flaw, mate-session might crash if no required applications are found. This is not very common case, but it should be fixed anway. The upstream pull request [1] fixes the issue. [1] https://github.com/mate-desktop/mate-session-manager/pull/71
Bug#778816: mate-maximus undecorates maximized windows even when this option is disabled
Source: mate-netbook Version: 1.8.1-3 Severity: normal Tags: jessie sid upstream Control: forwarded -1 https://github.com/mate-desktop/mate-netbook/issues/12 mate-maximus 1.8.x undecorates maximized windows even when this option is disabled in dconf-editor. The upstream pull request [1] fixes this issue, making mate-maximus respect undecorate setting. [1] https://github.com/mate-desktop/mate-netbook/pull/17
Bug#778835: m-n-d sometimes segfaults in notify_stack_set_location
Source: mate-notification-daemon Version: 1.8.1-2 Severity: important Tags: jessie sid upstream Control: forwarded -1 https://github.com/mate-desktop/mate-notification-daemon/issues/39 Due to some logic flaws in the code, m-n-d sometimes segfaults in notify_stack_set_location function. The upstream pull request [1] fixes the issue. [1] https://github.com/mate-desktop/mate-notification-daemon/pull/47
Bug#778775: session manager and capplet don't receive GSettings notifications with GLib = 2.43
Source: mate-session-manager Version: 1.8.1-7 Severity: important With the latest GLib changes [1], if an app reads some data from GSettings before connecting there, it actually won't receive any notifications from GSettings afterwards. The upstream pull request [2] fixes the issue for both session manager and capplet, making them connect to GSettings before reading the data. [1] https://git.gnome.org/browse/glib/commit/?id=8ff5668a458344da22d30491e3ce726d861b3619 [2] https://github.com/mate-desktop/mate-session-manager/pull/73
Bug#778809: daemon and capplet don't receive GSettings notifications with GLib = 2.43
Source: mate-notification-daemon Version: 1.8.1-2 Severity: important With the latest GLib changes [1], if an app reads some data from GSettings before connecting there, it actually won't receive any notifications from GSettings afterwards. The upstream pull request [2] fixes the issue for both daemon and capplet, making them connect to GSettings before reading the data. [1] https://git.gnome.org/browse/glib/commit/?id=8ff5668a458344da22d30491e3ce726d861b3619 [2] https://github.com/mate-desktop/mate-notification-daemon/pull/46
Bug#778694: marco doesn't receive GSettings notifications with GLib = 2.43
Source: marco Version: 1.8.2+dfsg1-4 Severity: important With the latest GLib changes [1], if an app reads some data from GSettings before connecting there, it actually won't receive any notifications from GSettings afterwards. The upstream pull request [2] fixes the issue for Marco, making it connect to GSettings before reading the data. [1] https://git.gnome.org/browse/glib/commit/?id=8ff5668a458344da22d30491e3ce726d861b3619 [2] https://github.com/mate-desktop/marco/pull/175
Bug#778691: m-s-d doesn't receive GSettings notifications with GLib = 2.43
Source: mate-settings-daemon Version: 1.8.2-1 Severity: important With the latest GLib changes [1], if an app reads some data from GSettings before connecting there, it actually won't receive any notifications from GSettings afterwards. The upstream pull request [2] fixes the issue for m-s-d, making it connect to GSettings before reading the data. [1] https://git.gnome.org/browse/glib/commit/?id=8ff5668a458344da22d30491e3ce726d861b3619 [2] https://github.com/mate-desktop/mate-settings-daemon/pull/96
Bug#732209: unable to create file '/run/user/1000/dconf/user': Permission denied
Weird... today I'm able to reproduce it with gksu pluma again, 100%. I'm out of clues :-/
Bug#732209: unable to create file '/run/user/1000/dconf/user': Permission denied
Hi Miklos, For some reason, now I'm having trouble reproducing the ownership change of /run/user/1000/dconf/user to root using my method from [1]. I've tried it on two Jessie installations, one has traditional sysvinit and another has systemd-sysv. Both systems are fully updated, the version of systemd is 215-11. Can you confirm whether your method (in Gnome session) still works in the current Jessie or not? Does /run/user/1000/dconf/user get owned by root? [1] https://bugs.debian.org/766464
Bug#772910: mate-settings-daemon: Massive memory leak
Hi, Can you still reproduce it in the current Jessie? Does the ownership of /run/user/1000/dconf/user change to root:root?
Bug#767173: gnome-shell: Display freezes but mouse stays operational
Hi Michael, Can you still reproduce it with the latest Jessie updates? (make sure systemd is 215-11) Does the ownership of /run/user/1000/dconf/user change to root:root?
Bug#768110: Re[2]: Bug#768110: wget: strange progress display with certain locale settings
Hi, I understand this but the release team does not allow new upstream versions for jessie since November (1.16.1 released 2014-12-08).:( Sorry. I see... But then maybe cherry-pick a patch from there to 1.16-1 and file an unblock request?
Bug#745697: Re[2]: Bug#745697: dmraid: Module dm-raid45 does not exist. It should not be forced to load in hook.
Hi, You can try filing an unblock request, like described in https://release.debian.org/jessie/freeze_policy.html
Bug#777142: patch - make gdk_event_apply_filters function safe against changes in filter list
Source: gtk+2.0 Version: 2.24.25-1 Severity: critical Justification: breaks unrelated software Tags: jessie sid patch Control: forwarded -1 https://bugzilla.gnome.org/show_bug.cgi?id=635380 Control: affects -1 mate-control-center Hi, A serious flaw in gdk_event_apply_filters function is causing weird crashes in various software. For example, mate-display-properties crashes when the screen resolution is changed or a new monitor is plugged in [1]. Some other older bugs like [2] and [3] also might be caused by this one. I've cherry-picked a patch from GTK+3 and adapted it to GTK+2. The patch fixes the issue for good. I've tested it with mate-display-properties - it doesn't crash anymore after GTK+2 is patched. The debdiff is in the attachment. Hope to see it accepted soon. Thanks in advance. [1] https://bugs.debian.org/760445 [2] https://bugs.debian.org/708559 [3] https://bugs.debian.org/718269 gtk2-debdiff Description: Binary data
Bug#745697: dmraid: Module dm-raid45 does not exist. It should not be forced to load in hook.
Hi, Any progress on this? The patch is attached as you can see, and Ubuntu LTS has this issue resolved already. Why not fix it in Jessie as well?
Bug#768110: wget: strange progress display with certain locale settings
Hi, Please migrate 1.61.1-1 to Jessie. I don't like wget spamming my terminal emulator while downloading large files.
Bug#768110: wget: strange progress display with certain locale settings
I meant 1.16.1-1 of course :)
Bug#708559: might be a bug in GTK+2
Hi, I'm not completely sure, but the presence of gdk_event_apply_filters function very close to the beginning of the backtrace indicates that it might be a bug in GTK+2 [1]. As the bug reporter mentioned there, This may result in very obscure bugs and/or crashes. BTW, the bug is still not fixed in GTK+2, they've pushed the fix only to GTK+3. [1] https://bugzilla.gnome.org/show_bug.cgi?id=635380
Bug#767973: imagemagick: desktop file icon is still not displayed
Hi, There's another reason why it should be hidden, explained in [1] by Michael Biebl: display.im6 looks really alien with it's custom X toolkit, missing Font Antialiasing, and completely different interface behaviour. He mentioned Gnome, but you can easily find out that it looks alien in other DEs as well. [1] https://bugs.debian.org/675453#40
Bug#773097: mate-notification-daemon: the notification window theme is not changeable
title 773097 mate-notification-daemon: the notification window theme is not changeable tags 773097 moreinfo thanks Hi, Some additional info is needed. Please run mate-notification-properties from the terminal, try changing the theme and the position, and post the output from the terminal here (or use pastebin and post the link). -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#776696: please update GTK+3 to 3.14.7
Source: gtk+3.0 Version: 3.14.5-1 Severity: wishlist Hi, GTK+3 version 3.14.7 is available upstream. Can you please package it? This will fix bugs like [1] and [2]. [1] https://bugs.debian.org/771205 [2] https://bugs.debian.org/773135 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#776581: please update cppcheck to 1.68
Package: cppcheck Version: 1.67-1 Severity: wishlist Hi, A new version of cppcheck is available upstream. Can you please package it? Changelog: http://sourceforge.net/p/cppcheck/news/2015/01/cppcheck-168/
Bug#772910: mate-settings-daemon: Massive memory leak
Hi, This is weird, I can reproduce it 100% with gksu pluma (even without arguments, i.e. not opening any file). Did you use gksu or gksudo BTW? Also can you please post the output of aptitude search ~isystemd and aptitude search ~isysv? Here's what I have in one of my VMs: monsta@jessica:~$ aptitude search ~isystemd i dh-systemd - debhelper add-on to handle systemd unit files i A libpam-systemd - system and service manager - PAM module i libsystemd-daemon-dev - systemd utility library (transitional package) i A libsystemd-dev - systemd utility library - development files i libsystemd-login-dev - systemd login utility library (transitional package) i A libsystemd0- systemd utility library i A libsystemd0:i386 - systemd utility library i A systemd- system and service manager iBA systemd-sysv - system and service manager - SysV links monsta@jessica:~$ aptitude search ~isysv iBA systemd-sysv - system and service manager - SysV links i sysv-rc- System-V-like runlevel change mechanism i sysvinit - System-V-like init utilities - transitional package i sysvinit-utils - System-V-like utilities And here's some more output following your comment at bug 732209: monsta@jessica:~$ ps -p1 f PID TTY STAT TIME COMMAND 1 ?Ss 0:01 /sbin/init monsta@jessica:~$ systemctl | head UNIT LOAD ACTIVE SUB DESCRIPTION proc-sys-fs-binfmt_misc.automount loaded active waiting Arbitrary Executable File Formats File System Automount Point sys-devices-pci:00-:00:01.1-ata2-host1-target1:0:0-1:0:0:0-block-sr0.device loaded active plugged VBOX_CD-ROM sys-devices-pci:00-:00:03.0-net-eth0.device loaded active plugged 82540EM Gigabit Ethernet Controller (PRO/1000 MT Desktop Adapter) sys-devices-pci:00-:00:05.0-sound-card0.device loaded active plugged 82801AA AC'97 Audio Controller sys-devices-pci:00-:00:0d.0-ata3-host2-target2:0:0-2:0:0:0-block-sda-sda1.device loaded active plugged VBOX_HARDDISK 1 sys-devices-pci:00-:00:0d.0-ata3-host2-target2:0:0-2:0:0:0-block-sda-sda2.device loaded active plugged VBOX_HARDDISK 2 sys-devices-pci:00-:00:0d.0-ata3-host2-target2:0:0-2:0:0:0-block-sda-sda5.device loaded active plugged VBOX_HARDDISK 5 sys-devices-pci:00-:00:0d.0-ata3-host2-target2:0:0-2:0:0:0-block-sda.device loaded active plugged VBOX_HARDDISK sys-devices-platform-serial8250-tty-ttyS0.device loaded active plugged /sys/devices/platform/serial8250/tty/ttyS0
Bug#758430: caja: crashes after several hours of use
Hi, Does it still happen in the current Debian? I'm asking because I suspect it might be a GLib bug, and GLib has been updated to 2.42 since August 2014. If it's still reproducible, can you please install caja-dbg (for more debug info) and post the backtrace again? Oh, and use bt full instead of bt please.
Bug#772910: mate-settings-daemon: Massive memory leak
Hi, Just out of curiosity, what init system are you using? Usually, these weird bugs only occur when using something like systemd-shim and any other of these hacky systemd work arounds. Well, I have one system with systemd-shim + sysvinit-core and a few ones with systemd as init. I can reproduce the issue (as I described in [1] ) in all of them. [1] https://bugs.debian.org/766464
Bug#772910: mate-settings-daemon: Massive memory leak
reassign 772910 libpam-systemd 215-8 forcemerge 732209 772910 thanks Hi, Well, looking at the description, I see this is the same bug that has been found in various situations before [1][2][3]. Especially this line hints that: Think it might be because I used the plugin for Caja allowing to fire files as root. If these files were the simple text ones, then they've been opened with Pluma, and we have exactly [2] here. So, I'm merging this report with these ones. [1] https://bugs.debian.org/732209 [2] https://bugs.debian.org/766464 [3] https://bugs.debian.org/769889
Bug#773135: libgtk-3-0: Oversized icons with SVG icon themes
Hi, It happens not only with SVG-only icon themes, but also with other icon themes that happen to have an icon or two in SVG format. Also looks like it's fixed upstream now [1]. [1] https://bugzilla.gnome.org/show_bug.cgi?id=741259
Bug#773710: libindicator3-dev: please drop dependency on libindicator-dev
Package: libindicator3-dev Version: 0.5.0-2 Severity: normal Hi, This dependency has been introduced as a solution for a bug [1]. Actually, all that was needed is to correct the path in the Cflags field in a .pc file. But now it seems that the mentioned path has been corrected in [2] already, so there's no need to keep this dependency anymore. Can you please drop it? Thanks in advance. [1] https://bugs.launchpad.net/bugs/803136 [2] http://sources.debian.net/src/libindicator/0.5.0-2/libindicator/indicator3-0.4.pc.in.in/
Bug#732209: unable to create file '/run/user/1000/dconf/user': Permission denied
Hi, Can you please provide step-by-step instructions, how to setup the test environment (which packages are installed, which environment is running) and which commands to use to trigger the problem. The best way I know is to run MATE's text editor (pluma) via gksu, as I've described in [1]. I ran it under MATE desktop environment, but it will probably trigger the issue under other DEs as well. You can easily set up a minimal MATE environment by installing the mate-desktop-environment-core meta-package. After that, only installing pluma is needed. Please also look at the comments by Linas Vepstas in that bug report. [1] https://bugs.debian.org/766464 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#772125: policykit-1: patch - work around systemd injecting broken XDG_RUNTIME_DIR
Source: policykit-1 Version: 0.105-8 Severity: normal Tags: patch jessie sid Hi, This is the patch from the newer upstream version [1], intended for the current version of policykit-1 in Jessie/Sid. Also, the last patch in the series has been slightly changed in order for this new patch to apply cleanly. The debdiff is in the attachment. [1] http://cgit.freedesktop.org/polkit/commit/?id=8635ffc16aeff6a07d675f861fe0dea03ea81d7e polkit-debdiff Description: Binary data
Bug#732209: unable to create file '/run/user/1000/dconf/user': Permission denied
found 732209 217-3 thanks Also tried systemd 217-3 from Experimental, the issue is still present.
Bug#732209: dconf-CRITICAL **: unable to create file '/run/user/1000/dconf/user': Permission denied.
Hi, BTW, this only happens with GNOME sessions. With other window managers (e.g. LXDE, Openbox) it does *not*. Therefore, I do not think it's a systemd bug, rather it's related to GNOME. Do you agree to reassign this bug against either the 'gnome-session' or the 'gnome-shell' package? No, I don't agree. I can reproduce it 100% in MATE desktop environment and also in Cinnamon, see [1]. I'm actually thinking of merging that bug report with this one. Please read the comments from Linas Vepstas there, they confirm that it's not a desktop environment or a text editor itself that causes it. Also, systemd had been messing up the ownership of /run/user/1000/dconf/user in the past, see [2]. [1] https://bugs.debian.org/766464 [2] https://bugs.debian.org/731300
Bug#732209: dconf-CRITICAL **: unable to create file '/run/user/1000/dconf/user': Permission denied.
Hi, I just decided to nofity all the participants here, in case this new info might be interesting or useful :)
Bug#732209: dconf-CRITICAL **: unable to create file '/run/user/1000/dconf/user': Permission denied.
reassign 732209 libpam-systemd 215-6 thanks Hi, Messing with /run/user/1000/dconf/user ownership seems to be the work of libpam-systemd - somewhat similar things had been happening before, as reported in [1] (and the merged reports). See also another bug report [2] about the similar issue. [1] https://bugs.debian.org/731300 [2] https://bugs.debian.org/766464
Bug#767906: libgtk-3-0: Size of menus on screen top is not properly calculated
Hi, Yes, I see it now. The upstream bug report says Looks like this is result after enabling csd for GtkMenu. Is there a Debian bug report for [1]? Looks like it's still not fixed. [1] https://bugzilla.gnome.org/show_bug.cgi?id=726030
Bug#766464: gksu pluma any_file sets the ownership of /run/user/1000/dconf/user to root:root
Hi, Thank you so much for investigating this issue. I've been busy with my job and various bugs so I never had the time to look into it. However, I've checked systemd's source code and found out the mentioned commit [1] is already there. No wonder - the commit is one year old, and the version of systemd in Debian Testing is already 215. You can check the code yourself to see that (just remember that pam-module.c has been renamed to pam_systemd.c). Also, Debian maintainers have made a lot of patches for systemd, but the only patch that modifies the files in question is [2], and it seems to be minor. So, either the mentioned commit didn't fix the problem completely, or there were some more changes along the way that made the problem appear again. [1] http://cgit.freedesktop.org/systemd/systemd/commit/?id=baae0358f349870544884e405e82e4be7d8add9f [2] http://sources.debian.net/src/systemd/215-6/debian/patches/Start-logind-on-demand-via-libpam-systemd.patch
Bug#766100: In XFCE, menu from system tray icon does not stay open
Should be fixed in GTK+ 3.14.5, see https://bugs.debian.org/767055
Bug#765964: mate-panel: Some notification menus hide on mouse up in notification area
Looks like this can be closed as it's fixed in GTK+ 3.14.5, see https://bugs.debian.org/767055
Bug#767906: libgtk-3-0: Size of menus on screen top is not properly calculated
Hi, Is this really fixed? The scroll buttons test [1] (I've found the link at [2]) still shows these scroll buttons when its window is maximized, even after the upgrade of GTK+ to 3.14.5 from Sid. [1] https://github.com/lanoxx/gtk-menu-scroll-test [2] https://bugzilla.gnome.org/show_bug.cgi?id=726030
Bug#770436: libcryptui: patch - fix logic flaw in the prompt recipients dialog
Source: libcryptui Version: 3.12.2-1 Severity: important Tags: patch Hi, The prompt recipients dialog has been broken in one commit [1]. The attached patch fixes the logic there and makes seahorse-tool's encrypt command work again. Therefore, seahorse plugins for both Nautilus and Nemo should start working as well. Hope to see it accepted soon. Thanks in advance. [1] https://github.com/GNOME/libcryptui/commit/cd74aa6bf810a5ce0935d2ec89d6db64dbbde24d#diff-f0ea8a1eef5386b0149314d2a1743e85L202 libcryptui-debdiff Description: Binary data
Bug#757152: python-pyatspi: Should depond on at-spi2-core OR qt-at-spi
Aha, looks like I've found the culprit responsible for Cinnamon indirectly depending on Qt libs :-/ $ aptitude why libqtgui4 i cinnamon Depends caribou i A caribouDepends python-pyatspi i A python-pyatspi Depends qt-at-spi i A qt-at-spi Depends libqtgui4 (= 4:4.8~)
Bug#768651: libaudio2: fails to update - trying to overwrite shared '/usr/share/doc/libaudio2/changelog.Debian.gz'
Hi, I have no idea why a package with such a serious issue has been allowed to migrate to Testing, but here's a fix anyway: get the previous version (both amd64 and i386) from snapshot.debian.org [1] and install it via dpkg. After that, you can hold it for a while using apt-mark (preventing it from the upgrade). [1] http://snapshot.debian.org/package/nas/1.9.4-1/#libaudio2_1.9.4-1
Bug#763933: gtk+3.0: cursor bar vanishes or produces rendering artefacts
Hi, I can't reproduce this in gedit with GTK+ 3.14.4 (from Sid). Can you check this? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#763602: please accept the patch to prevent auto-removal of this package
Dear Maintainer(s), Even though this bug is marked as fixed by recent GTK+2 changes, Package Tracking System still says this package will be removed in 4-5 days due to this very bug. So please accept my patch and release a new version of the package to prevent that. Thanks in advance. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#766464: gksu pluma any_file sets the ownership of /run/user/1000/dconf/user to root:root
Hi, The issue does not occur with leafpad nor mousepad as both don't use dconf under their bonnet. Ahh... I had no idea. Thanks for pointing that out. And gedit indeed uses dconf, and I've managed to reproduce this issue there, though for some reason it's not always reproducible. Please track this issue down further. Try to find out, what application / library really changes ownership on /run/user/1000/dconf/user (you can use the strace command for that). Ok, I'll try that. BTW, do you have any idea how gksu might be related to that? (In particular, why gksu triggers the bug while gksudo doesn't)
Bug#744249: libgtk-3-0: gtk 3.12 breaks usability by forcing client side decorations on X11
retitle 744249 CSD windows cannot be resized under many window managers found 744249 3.14.3-1 thanks Hi, Looks like every window manager's developers will have to fix this in their code. I've found an old commit in Mutter's code [1] which fixes the resizing of windows whose titlebar is currently offscreen, and by coincidence, it also fixes the resizing of CSD windows (even though CSD didn't even exist when that commit has been pushed). Muffin, the Cinnamon's WM which is a fork of Mutter, inherited this fix. The code from that commit has been used in Metacity as well [2]. I've pushed this fix to Marco [3], so MATE developers should look at it soon (I hope). As for the other WMs like WindowMaker, I'm not familiar with their code, so it's hard to say what changes need to be made in order to fix this. [1] https://git.gnome.org/browse/mutter/commit/?id=526bc34bba20b5f8d3055f2fb668a36a21357443 [2] https://git.gnome.org/browse/metacity/commit/?id=c9099b4a90932a22c86b960c8b4dc7cd1458defe [3] https://github.com/mate-desktop/marco/pull/142
Bug#751075: marco: hard to resize certain windows (e.g. devhelp)
unmerge 751075 reassign 751075 marco 1.8.2+dfsg1-1 retitle 751075 CSD windows cannot be resized under Marco forwarded 751075 https://github.com/mate-desktop/marco/issues/138 thanks Hi, I've decided to unmerge this one because it seems that the issue has to be fixed in each window manager separately, see [1]. I've pushed the fix for Marco upstream [2]. [1] https://bugs.debian.org/744249#236 [2] https://github.com/mate-desktop/marco/pull/142
Bug#745988: gthumb 3.3.x uses header bars, breaking compatibility with non-GNOME environments
Hi, There's one more issue with gthumb and other CSD apps from Gnome: you can't resize their window under many (almost all) window managers. https://bugs.debian.org/744249
Bug#766100: In XFCE, menu from system tray icon does not stay open
Hi, I confirm this - the same happens in MATE 1.8 with nm-applet. Only the left-click menu is affected though, the right-click one still works fine.
Bug#766464: gksu pluma any_file sets the ownership of /run/user/1000/dconf/user to root:root
Package: pluma Version: 1.8.1+dfsg1-2 Severity: important Steps to reproduce: 0. Have a Debian Testing installation, fully updated, with pluma installed. 1. Run gksu pluma any_file. Even the files in your ~ will do. 2. ls -l /run/user/1000/dconf/user 3. Notice that the ownership of that file changed from you:you to root:root. You might also need to do some additional steps, like saving the file or simply opening the preferences dialog. But with the latest Testing updates I've found out it's enough to just run the editor. Impact on the system: Various unrelated apps might start eating 100% CPU or a lot of memory, or break in other ways. If run from the console, they will show you this: (dconf-editor:2593): dconf-CRITICAL **: unable to create file '/run/user/1000/dconf/user': Permission denied. dconf will not work properly. Additional note: Does NOT happen if you use gksudo instead of gksu. Why reported against pluma instead of gksu: I've tried a couple of other text editors - leafpad, mousepad - and they don't exhibit such a behavior, /run/user/1000/dconf/user stays owned by me. Feel free to reassign the report if you think I've missed something.
Bug#763034: libgtk-3-0: Regression in GTK+ 3.12 in handling CSS-defined selected_bg_color
tags 763034 confirmed forwarded 763034 https://bugzilla.gnome.org/show_bug.cgi?id=738841 thanks Hi, You didn't include cont...@bugs.debian.org as the recipient so tags and forwarded commands didn't work. I hope my message fixes that. :) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#745487: apt python library leak memory and file descriptors
Hi, What is the current state of this in Jessie? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#744249: libgtk-3-0: gtk 3.12 breaks usability by forcing client side decorations on X11
Strangely, I can't seem to find any upstream bugs about the inability to resize CSD windows. How come...?
Bug#744249: libgtk-3-0: gtk 3.12 breaks usability by forcing client side decorations on X11
Hi, I think a misunderstanding has occurred here. ... If GTK3 forces CSD on non-Gnome apps that don't use it explicitly, that IS a bug in GTK3. But if ONLY Gnome apps get CSD, that could be seen as a bug in THEM (or in Gnome) and not in GTK3. Indeed, I didn't get it right... The situation was/is like this: - GTK+ 3.12 forced CSD on all dialog windows and subwindows, making it impossible to resize them with a mouse in the environments other than Gnome Shell. This included not only Gnome apps, but any other GTK+3 apps as well (e.g. Synaptic). - GTK+ 3.14 removed [1] that feature. Now all the dialog windows have CSD only if GTK+ decides it works best in the current environment. In practice it means the dialogs in _all_ GTK+3 apps don't have forced CSD anymore if you're using MATE, Xfce, LXDE, etc. (in other words - not Gnome Shell) - In both GTK+ 3.12 and 3.14, most of the Gnome apps still have CSD in their _main_ windows. That means they're still not resizable with a mouse in the environments other than Gnome Shell, and that's still a bug. [1] http://blogs.gnome.org/mclasen/2014/07/28/a-talk-in-9-images/
Bug#744249: libgtk-3-0: gtk 3.12 breaks usability by forcing client side decorations on X11
Hi, Looking at the GtkHeaderBar source code, it does not appear to be the case that Gtk is forcing client side decorations. 3.12 did for GtkDialog under at least some circumstances, but 3.14 does not appear to use CSD for GtkDialog under non-GNOME. Yes, the subject of this bug report isn't correct anymore. But as I said in my previous letter (to Tsu Jan), the inability to resize any windows that _have_ CSD is still present in 3.14. Since this is basically the same issue that has been reported originally, I think this bug should be kept open. Just the title needs to be changed. One possibility would be to detect GNOME Shell (or some we like CSDs GSetting that GNOME Shell could set), use CSD in Shell, and use WM decorations / no title in the GtkHeaderBar on non-Shell Yes, that's what I'm thinking about. GTK+ 3.14 already has the logic that enables or disables CSD in dialog windows, depending on the current environment. Similar logic might be used to use either WM decorations or CSD. That would solve this bug for good (you would be able to resize the windows normally with a mouse). So, it is likely that someone who advocates this change will have to do the research, propose a solution/design that makes sense and is implementable, and implement it. We've already seen in this bug's discussion that attempts to patch in design changes via a GtkModule are not sufficiently robust to be a good solution. Yes, our experiments so far led to two results, both not acceptable as a good solution yet: - the headerbar is removed completely, taking any app-specific buttons with it, making the app completely or partially unusable. The only control that's not removed is the fallback app menu which is converted to the classic menu. Not a good solution. - the headerbar is not removed, therefore some apps have duplicated window title (in WM decorations and in the headerbar). This doesn't break the functionality but doesn't _look_ good either. Since at least one headerbar item (the app menu) can be converted to the conventional menu, I was hoping to find a way to do the same for the other headerbar buttons (excluding WM controls of course) and therefore get rid of the headerbar in the end. Of course, this would be also paired with the aforementioned logic (leave the headerbars alone in Gnome Shell, convert them in other environments). That would not only solve this bug with window resizing, but also make Gnome apps look less out-of-place in the environments other than Gnome Shell. The fact that GNOME 3.14 adds the gtk-dialogs-use-header GSetting and the gtk_application_prefers_app_menu() function (and hence GtkDialog no longer uses CSD, and some apps' menu structures go back to being more traditional, under non-GNOME) indicates that there is upstream interest in this sort of thing. Oh, that's interesting, I didn't know about gtk_application_prefers_app_menu(). In regard to what had been said above, it would certainly be nice to have some kind of gtk_application_prefers_headerbar() function as well. :) As for now, I don't know whether someone comes up with a reasonable solution, but I'm already afraid we might run out of time due to the coming freeze of Jessie.
Bug#763050: geany: Does not start, Attempt to unlock mutex that was not locked instead
Hi, First of all, thanks for the patch. I suggest making a debdiff from this patch so the maintainers would be able to include it in the package. It will be faster than waiting for the upstream to release a new version. If you need some info about making a debdiff, check this article: http://raphaelhertzog.com/2011/07/04/how-to-prepare-patches-for-debian-packages/
