Hi,
This extension seems to work with Python 3 after one import change:
-from MediaInfoDLL import *
+from MediaInfoDLL3 import *
After that, it also needs a dependency change from python-mediainfodll
to python3-mediainfodll.
Hi,
Martin updated packaging for Python 3 before 1.22.1 was uploaded to Unstable:
https://salsa.debian.org/debian-mate-team/caja-dropbox/commit/8694f61e85248792de2bbacd11c4999860125c17
Hi,
The migration to Python 3 and GI had been done in caja-dropbox 1.22.0.
I guess we can close this?
Hi,
Upstream has a workaround for this crash at [1], you might want to use it as a
patch.
Also this report can be probably merged with [2].
[1]
https://github.com/lanoxx/tilda/commit/daa64f579b4d544cb7da614612f1d35c461b43be
[2] https://bugs.debian.org/904309
Hi,
Here's a quick patch from upstream commit, it should fix the crash:
https://github.com/mate-desktop/mate-power-manager/commit/7facec455d825d317caffb8cafc4e4fec60065d9.patch
Hi,
It's fixed in upstream releases 1.18.1 and 1.16.1.
For now, here's the patch from upstream commit:
https://github.com/mate-desktop/mate-utils/commit/550229e422cd88fe39473f41cebe6cef12f6c8fb.patch
Hi,
I'd like to know if there's any progress on uploading the new
version to jessie-security. Just want to check if the update
would fix https://bugs.debian.org/831851 as well.
Hi,
> This is because your CPU architecture is not 32 bit, and not i586 or lower.
> I'm sure if you set that by hand, you will be able to reproduce that.
Yes, I know. Just wanted to confirm that upgrade is safe on 64-bit systems :)
Hi,
This doesn't happen even in VirtualBox working on a host with an old Core 2 Duo
(both host and guest Debian installations are 64-bit). The upgrade went fine.
reassign 807878 libpam-systemd 215-17+deb8u4
forcemerge 732209 807878
thanks
Hi,
This is the same old bug in libpam-systemd that upstream
does not want to fix and maintainers here claim it's not
reproducible. Check [1] and all the merged reports there
for more details.
[1]
Hi,
This is an old bug in libpam-systemd which maintainers still refuse to
acknowledge
(and upstream refuses to consider it a bug).
Unfortunately, mate-settings-daemon is just another victim of it. It's at a
level below us
and we can't fix it ourselves.
If you know how to patch Debian
Hi,
> We are working to migrate binutils version 2.25.90.20151209-1 into
> testing asap. If everything goes well it should be the case after the
> 13:52 UTC dinstall run, so a few hours after that on the mirrors.
>
> In the meantime fetching and installing this version from sid, should
> solve
Source: glib2.0
Version: 2.46.0-2
Severity: critical
Justification: breaks functionality of many file managers
Control: forwarded -1 https://bugzilla.gnome.org/show_bug.cgi?id=749314
Control: tags -1 stretch sid upstream
Control: affects -1 caja nemo nautilus thunar
Steps to reproduce:
1. Move
Source: gtk+2.0
Version: 2.24.25-3
Severity: serious
Control: tags -1 jessie patch
Control: affects -1 eom
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
Hi,
This is due to API changes in libmate-desktop 1.10. You just need to wait
for mate-screensaver 1.10 to migrate to unstable and testing - it will be
built fine against libmate-desktop 1.10.
Ouch. Looks like [1] needs to be ported to Jessie (and to Wheezy, just in case).
[1]
http://anonscm.debian.org/cgit/pkg-mate/mate-control-center.git/commit/?h=debian/experimentalid=c16fd256bc172511fb180a6b6e8e0e5bb3c7b44e
Ah... it's about unstable - sorry, I misread. Disregard the previous comment. :)
The new mate-settings-daemon-dev package is available only in 1.10.
It's just a matter of uploading mate-control-center 1.10 from experimental
to reflect that change. Should be settled soon I think.
Hi,
There are duplicate lines in mate-applets.install and
mate-applets-common.install:
usr/share/dbus-1/
usr/share/man/
usr/share/mate-panel/
usr/share/polkit-1/
They need to be removed from one of the files. Check the upstream files:
Hi,
There are duplicate lines in python-caja.install and python-caja-common.install:
usr/share/doc/
usr/share/gtk-doc/html/
They need to be removed from python-caja.install. Check the upstream files:
https://github.com/mate-desktop/debian-packages/tree/master/python-caja/debian
Hi,
I've already fixed it upstream [1] - you can pick the patch from there.
[1]
https://github.com/mate-desktop/debian-packages/commit/7265a33f984ee8099e41f02c898fed4741821f7f
Hi,
Sorry, my mistake - set too old version in Replaces/Breaks field.
This commit might fix the problem:
https://github.com/mate-desktop/debian-packages/commit/c73060e541bfbb137782921bd28e6a13aa117a47
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of
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,
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
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,
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:
Hi,
Glad to hear the new patch is working for you. It is not clear
though whether the maintainer will apply it, because, as you can
see, this bug report has been closed due to the arrival of the new
version of GTK+2. This new version has a workaround for the mutex
issue [1], which allows the
Hi,
Ok, I've managed to reproduce it... to some extent. If I set it to load a
notebook
on app start (either Default Notebook or Open Last Notebook settings), it
crashes with the same mutex-related error message. If I set it to open without
any notebooks and then manually open a notebook via the
Hi,
Try this new debdiff (in the attachment) and see if it works for you.
keepnote-new-debdiff
Description: Binary data
Hi,
Guys, thanks for spotting this. Indeed, I haven't tested keepnote with
creating a new notebook (my bad).
Unfortunately, as I've tried to dig deeper into the issue, I found out that
keepnote now simply segfaults on start:
keepnote[3028]: segfault at 0 ip (null) sp 7fff4794a738
Follow-up:
Ok, I've found out that the segfaults were caused by GTK+3 hack [1] which
I've been testing yesterday and haven't turned off afterwards.
Now keepnote and other Python apps run fine, so I'll continue investigating
the mutex issue.
Don't ask me how a GTK+3 hack could possibly affect
Hi,
I have applied Your patch. Keepnote 0.7.8-1.2 builded successfully, but
after package installation problem with starting application still exist.
I'm using Debian Testing
I've just tried it in another Debian Testing VM, and it worked for me.
Note that you don't need to use sudo for
Hi,
I've converted the upstream patch into a debdiff so it could be
applied to the package. The debdiff is in the attachment.
Hope to see it accepted ASAP.
gtk2-debdiff
Description: Binary data
tags 763602 patch
thanks
Hi,
The crash is due to some recent changes in GLib = 2.41 [1].
I'm attaching the debdiff with the patch for this bug.
Hope to see it accepted ASAP.
[1] https://bugzilla.gnome.org/show_bug.cgi?id=735428
mirage-debdiff
Description: Binary data
Hi,
Dammit, this is worse than I thought. It's not fixed by applying a workaround
patch [1] to GTK+2 (like it's been fixed in every other app failing with the
same
attempt to unlock... message). It still crashes even with the patched GTK+2.
[1] https://bugs.debian.org/763690
tags 763625 patch
thanks
Hi,
The crash is due to some recent changes in GLib = 2.41 [1].
I'm attaching the debdiff with the patch for this bug.
Hope to see it accepted ASAP.
[1] https://bugzilla.gnome.org/show_bug.cgi?id=735428
keepnote-debdiff
Description: Binary data
tags 763735 patch
thanks
Hi,
The crash is due to some recent changes in GLib = 2.41 [1].
I'm attaching the debdiff with the patch for this bug.
Hope to see it accepted ASAP.
[1] https://bugzilla.gnome.org/show_bug.cgi?id=735428
bp-debdiff
Description: Binary data
Here's more detailed backtrace (in the attachment).
gdb-brasero-backtrace
Description: Binary data
tags 762453 patch
thanks
Fixed by applying the fix [1] from upstream.
The debdiff is in the attachment.
Hope to see it accepted soon. Thanks in advance.
[1]
https://git.gnome.org/browse/brasero/commit/?id=4ef90701cfbc1dfdef71299d495339185d1b910a
brasero-debdiff
Description: Binary data
tags 756205 patch
thanks
Since it's not known when gvfs 1.20.4 (and 1.22) will be released,
I've decided to convert the upstream commit [1] into debdiff which
can be applied to gvfs 1.20.3-1.
Before that, I've tested the behavior of gvfsd-metadata as suggested
by gvfs developer in [2]. The
One of gvfs developers posted a patch [1] which might fix this bug.
[1] https://bugzilla.gnome.org/show_bug.cgi?id=637095#c50
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
This indeed looks like a bug in 1.15, because 1.13 and 1.14 recognize the
expired certificate:
$ wget www.cloudflarechallenge.com
--2014-08-19 13:41:45-- http://www.cloudflarechallenge.com/
Resolving www.cloudflarechallenge.com (www.cloudflarechallenge.com)...
107.170.194.215
Connecting to
This bug isn't on expired certificates, but on the revoked ones.
The www.cloudflarechallenge.com test is now obsolete because the
certificate has expired (wget 1.15 checks that, so no bugs here
for expired certificates). Two tests with revoked certificates
are still working:
Due to the lack of attention from the maintainer, I guess people will indeed
have to download the patch and build the fixed version on their own.
Source: gdebi
Version: 0.9.5.4
Severity: serious
Steps to reproduce:
1. Have some non-en_US locale currently set in your system. I have ru_RU for
example.
2. sudo apt-get install dpkg-dev devscripts build-essential
3. sudo apt-get build-dep gdebi
4. apt-get source gdebi
5. cd gdebi-0.9.5.4
6.
I see there's a new fixed version waiting at
http://mentors.debian.net/package/virtualbox
Package: virtualbox-guest-x11
Version: 4.3.12-dfsg-1
Severity: serious
I'm running Debian Testing in Virtualbox.
With the recent updates, virtualbox-guest-x11 is removed if you upgrade
xserver-xorg-core
to version 2:1.15.99.904-1, because virtualbox-guest-x11 needs
xorg-video-abi-15 - but
Hmm, I can't reproduce it anymore with lightdm-gtk-greeter 1.8.4-1 (Testing).
I wonder why you keep patching an old, outdated and unstable version,
when there's the new one (2.0.x) available. There's even a bug report [1]
about that.
[1] https://bugs.debian.org/740231
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe.
Is this the reason the package has been removed from Testing?
Maybe it's time to apply the proposed patch?
I can reproduce it. The greeter just froze after I've entered my username and
password. I've switched to the console using Ctrl-Alt-F1, killed -9 the greeter,
and it logged into DE session just fine.
I've checked that libpam-systemd is installed.
I've looked in all the logs mentioned in the
Is this the reason ifuse has been removed from Testing?
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Package: synaptic
Version: 0.80.4
Severity: serious
If you press any keys too early while Synaptic is still starting
(i.e. not showing the window yet), it will crash.
It can be seen the following gdb log. I started pressing the random
keys immediately after issuing the run command in gdb. First
Dear Maintainer, please apply this patch mentioned above [1], it will make
things easier.
Ubuntu and Mint already applied it and it works fine.
[1] https://bugs.debian.org/731300#33
Can't reproduce it.
Run dmesg after that and check the last lines of the output for the hints about
the cause of segfault. If it says something about libgtk-3.so then you've
probably
been hit by a known bug in gtk3-engines-unico [1] and need to change your
GTK+ theme to something not using
Don't know about the fresh installations, but today's upgrading VLC from
2.1.1-1 to 2.1.2.-1
went fine. No glitches.
Errors like the one reported are usually fixed with
$ dpkg --configure -a
and/or
$ apt-get -f install
For reference, you can use the Ambiance Crunchy set of themes. [1]
Recently, it's been updated for GTK+ 3.8, and it still uses Unico. It
looks fine in the current beta of Ubuntu Saucy (so, please, no theming
is totally broken arguments) which uses the latest build of
gtk3-engines-unico.
I
Hi,
This patch is just temporary workaround and it is not
included in the upstream version.
The upstream have thrown away a lot of code in [1], so the patch
wouldn't even work anymore, because it looks like the code responsible
for crashes was just removed with a lot of other stuff.
These
Hi,
it builds and GTK-3 apps start again
Well, then it can be considered as a fix for this bug and the ones
merged with it.
theming is totally broken
It may depend on the themes themselves. If the theme simply wasn't
updated for GTK+3.8, it may very well look ugly. What themes did you
58 matches
Mail list logo
