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
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]
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
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
Hi Michael,
Not release critical. Restoring previous severity.
Are you sure? This might break Wheezy - Jessie upgrades...
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.
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
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
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
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
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
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
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
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
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
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
Hi,
I've sent a pull request with the fix upstream:
https://github.com/mate-desktop/atril/pull/133
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
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
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]
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
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
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
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.
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
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
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
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
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
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
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
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
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
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
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]
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]
tags 774546 moreinfo
thanks
Hi,
Please run bt full in gdb prompt right after the crash
and post the result.
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/
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,
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. :)
A similar fix is needed for the preview widget:
https://github.com/mate-desktop/marco/pull/179
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
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.
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
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]
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
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
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
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
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
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,
Weird... today I'm able to reproduce it with gksu pluma again, 100%.
I'm out of clues :-/
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
Hi,
Can you still reproduce it in the current Jessie?
Does the ownership of /run/user/1000/dconf/user change
to root:root?
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?
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?
Hi,
You can try filing an unblock request, like described in
https://release.debian.org/jessie/freeze_policy.html
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
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?
Hi,
Please migrate 1.61.1-1 to Jessie. I don't like wget spamming
my terminal emulator while downloading large files.
I meant 1.16.1-1 of course :)
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
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
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
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
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/
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:~$
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
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
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
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
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,
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
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
found 732209 217-3
thanks
Also tried systemd 217-3 from Experimental, the issue is still present.
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
Hi,
I just decided to nofity all the participants here, in case
this new info might be interesting or useful :)
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.
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
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
Should be fixed in GTK+ 3.14.5, see https://bugs.debian.org/767055
Looks like this can be closed as it's fixed in GTK+ 3.14.5,
see https://bugs.debian.org/767055
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]
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
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
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
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
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
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
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
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
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
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.
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
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
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
Strangely, I can't seem to find any upstream bugs about
the inability to resize CSD windows. How come...?
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
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
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:
201 - 300 of 431 matches
Mail list logo
