Bug#942914: caja-mediainfo: Python2 removal in sid/bullseye
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.
Bug#885263: caja-dropbox: Depends on unmaintained pygtk
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
Bug#885263: caja-dropbox: Depends on unmaintained pygtk
Hi, The migration to Python 3 and GI had been done in caja-dropbox 1.22.0. I guess we can close this?
Bug#925483: tilda: does not start (segfault) (under Wayland)
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
Bug#870121: mate-power-manager: sometimes hits not-reached assertion on startup
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
Bug#865890: mate-utils FTBFS: error: unknown type name 'GdictContext'
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
Bug#820965: marked as pending
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.
Bug#823748: tar: illegal hardware instruction breaks apt-get upgrade
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 :)
Bug#823748: tar: illegal hardware instruction breaks apt-get upgrade
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.
Bug#807878: gnome: Gnome freezes when root windows are open on user screen.
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] https://bugs.debian.org/732209
Bug#818600: mate-settings-daemon cannot create file /run/user//dconf/user and fills up the memory (24 GB!)
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 packages, you can try to patch libpam-systemd with the patch from [1]. If you don't know how, I recommend reading an excellent article about it [2]. [1] https://github.com/linuxmint/systemd-betsy/commit/f7ab85f1e1169ac1598dfc1fba1c01063840b3c5.patch [2] https://raphaelhertzog.com/2011/07/04/how-to-prepare-patches-for-debian-packages/
Bug#808181: Re[2]: Bug#808181: libc6: Upgrade can make the linker unusable
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 the issue. Thanks, that version solved the issue indeed. Compilation goes fine now.
Bug#800941: regression in 2.46: can't restore a just-trashed file
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 some file to trash using a file manager or gvfs-trash tool. Tested with the following file managers: Caja, Nemo, Nautilus, Thunar. 2. Browse trash and try to restore the file. The file manager complains that it can't determine the original location of the file, and so doesn't restore it. This is a regression in 2.46 since restoring worked fine in 2.44. The problem is that "trash::orig-path" and "trash::deletion-date" attributes are not added to the trashed file. Without that the file manager can't determine the original location of the file, and hence can't restore it. You can check the file attributes by printing the moved file's info: gvfs-info trash:///file_name Check the upstream report [1] for more details. [1] https://bugzilla.gnome.org/show_bug.cgi?id=749314
Bug#799275: [GDK] patch - avoid integer overflow when allocating a large block of memory
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 had been fixed [2] in GTK+3, but the commit never made it to GTK+2 branch. I've converted it into a patch for GTK+2. The debdiff is in the attachment. Please apply it in Jessie. [1] https://github.com/mate-desktop/eom/issues/93 [2] https://git.gnome.org/browse/gtk+/commit?id=894b1ae76a32720f4bb3d39cf460402e3ce331d6 gtk2-gdk-debdiff Description: Binary data
Bug#796452: mate-screensaver: FTBFS: error: too many arguments to function 'mate_rr_screen_new'
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.
Bug#796424: mate-control-center: FTBFS: error: Package requirements (mate-settings-daemon = 1.5.2) were not met
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
Bug#796424: mate-control-center: FTBFS: error: Package requirements (mate-settings-daemon = 1.5.2) were not met
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.
Bug#789348: mate-applets: Unable to install mate-applets because of a file conflict in mate-applets-common
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: https://github.com/mate-desktop/debian-packages/tree/master/mate-applets/debian
Bug#789626: python-caja: fails to install, trying to overwrite other packages 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
Bug#789444: mate-indicator-applet: Cannot install mate-indicator-applet due to duplicate .mo file in both the packages
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
Bug#789346: mate-sensors-applet: Cannot install mate-sensors-applet-common because a .mo file is also present in mate-sensors-applet
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 unsubscribe. Trouble? Contact listmas...@lists.debian.org
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#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#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-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
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/
Bug#763625: keepnote fails with Attempt to unlock mutex that was not locked
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 affected apps run normally even without patching the apps themselves. Of course, I think the apps should use GDK threads correctly, but given the amount of the affected apps out there, the workaround in GTK+ seems to be more convenient solution for the users. Thanks for the testing BTW :) [1] https://git.gnome.org/browse/gtk+/commit/?h=gtk-2-24id=fbf38d16bcc26630f0f721d266509f5bc292f606 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#763625: keepnote fails with Attempt to unlock mutex that was not locked
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 menu item, it doesn't crash. I'm yet to figure out what's the difference here.
Bug#763625: keepnote fails with Attempt to unlock mutex that was not locked
Hi, Try this new debdiff (in the attachment) and see if it works for you. keepnote-new-debdiff Description: Binary data
Bug#763625: keepnote fails with Attempt to unlock mutex that was not locked
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 error 14 in python2.7[40+31c000] This is probably due to some recent updates in Debian Testing, because some other Python apps crash with segfault as well. If I'll manage to find a fix or a workaround, I'll continue the investigation.
Bug#763625: keepnote fails with Attempt to unlock mutex that was not locked
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 Python apps that are using GTK+2 - I have no idea :) [1] https://bugs.debian.org/744249#127
Bug#763625: keepnote fails with Attempt to unlock mutex that was not locked
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 apt-get source, for applying the patch and for building the package. A simple sequence of commands - $ apt-get source keepnote $ patch -p0 ./keepnote-debdiff $ cd keepnote-0.7.8 $ debuild -us -uc - would work just fine. And just in case, check lines 277 and 279 in /usr/bin/keepnote. They should contain gtk.gdk.threads_enter() and gtk.gdk.threads_leave(), correspondingly - wrapping around gtk.main() call. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#763690: libgtk2.0-0: Many (all?) gtk2 applications segfault when using threads
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
Bug#763602: Crashes on startup with Attempt to unlock mutex that was not locked
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
Bug#763050: geany: Does not start, Attempt to unlock mutex that was not locked instead
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
Bug#763625: keepnote fails with Attempt to unlock mutex that was not locked
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
Bug#763735: blueproximity: Fails to start with Attempt to unlock mutex that was not locked error
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
Bug#762453: brasero: doesn't even start (segfault)
Here's more detailed backtrace (in the attachment). gdb-brasero-backtrace Description: Binary data
Bug#762453: brasero: doesn't even start (segfault)
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
Bug#756205: gvfs-daemons: gvfsd-metadata continuously does disk accesses
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 patch indeed fixes the issue. The debdiff is in the attachment. Hope to see it accepted soon. Thanks in advance. [1] https://git.gnome.org/browse/gvfs/commit/?h=gnome-3-12id=23341281b7e7f3d92ea1f3d6dffc156a8adb03bc [2] https://bugzilla.gnome.org/show_bug.cgi?id=637095#c47 gvfs-debdiff Description: Binary data
Bug#756205: gvfs-daemons: gvfsd-metadata continuously does disk accesses
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
Bug#745836: wget: certificate revocation is not checked
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 www.cloudflarechallenge.com (www.cloudflarechallenge.com)|107.170.194.215|:80... connected. HTTP request sent, awaiting response... 301 Moved Permanently Location: https://www.cloudflarechallenge.com/ [following] --2014-08-19 13:41:46-- https://www.cloudflarechallenge.com/ Connecting to www.cloudflarechallenge.com (www.cloudflarechallenge.com)|107.170.194.215|:443... connected. ERROR: The certificate of 'www.cloudflarechallenge.com' is not trusted. The certificate has expired
Bug#745836: Re[2]: Bug#745836: wget: certificate revocation is not checked
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: https://revoked.grc.com/ https://www.vinc17.net:4434/ Ah, that's another matter, thanks for pointing it out. In this case, wget 1.13 (from Wheezy) and 1.14 behave just like 1.15: they download index.html right away.
Bug#722989: gsmartcontrol 0.8.7-2
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.
Bug#757078: gdebi FTBFS when the locale is not en_US
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. debuild -us -uc The build process will fail as shown in the first attachment (build_log_with_locale_ru_RU.txt). Now try the same with locale set to en_US (but do a cleanup first): 7. debuild clean 8. LC_ALL=en_US.UTF-8 debuild -us -uc The build process will succeed as shown in the second attachment (build_log_with_locale_en_US.txt).monsta@jessica:~/3/gdebi-0.9.5.4$ debuild -us -uc dpkg-buildpackage -rfakeroot -D -us -uc dpkg-buildpackage: Ð¿Ð°ÐºÐµÑ Ð¸ÑÑ Ð¾Ð´Ð½ÑÑ ÑекÑÑов gdebi dpkg-buildpackage: веÑÑÐ¸Ñ Ð¸ÑÑ Ð¾Ð´Ð½ÑÑ ÑекÑÑов 0.9.5.4 dpkg-buildpackage: source distribution unstable dpkg-buildpackage: иÑÑ Ð¾Ð´Ð½Ñе ÑекÑÑÑ Ð¸Ð·Ð¼ÐµÐ½ÐµÐ½Ñ Luca Falavigna dktrkr...@debian.org dpkg-source --before-build gdebi-0.9.5.4 dpkg-buildpackage: аÑÑ Ð¸ÑекÑÑÑа Ñзла amd64 fakeroot debian/rules clean dh clean --with python3 --buildsystem pybuild dh_testdir -O--buildsystem=pybuild debian/rules override_dh_auto_clean make[1]: Ð²Ñ Ð¾Ð´ в каÑалог «/home/monsta/3/gdebi-0.9.5.4» dh_auto_clean I: pybuild base:170: python3.4 setup.py clean running clean removing '/home/monsta/3/gdebi-0.9.5.4/.pybuild/pythonX.Y_3.4/build' (and everything under it) 'build/bdist.linux-x86_64' does not exist -- can't clean it 'build/scripts-3.4' does not exist -- can't clean it rm -rf build GDebi/Version.py po/mo make[1]: вÑÑ Ð¾Ð´ из каÑалога «/home/monsta/3/gdebi-0.9.5.4» dh_clean -O--buildsystem=pybuild dpkg-source -b gdebi-0.9.5.4 dpkg-source: инÑо: иÑполÑзÑеÑÑÑ ÑоÑÐ¼Ð°Ñ Ð¸ÑÑ Ð¾Ð´Ð½Ð¸ÐºÐ° «3.0 (native)» dpkg-source: инÑо: ÑбоÑка gdebi в gdebi_0.9.5.4.tar.xz dpkg-source: инÑо: ÑбоÑка gdebi в gdebi_0.9.5.4.dsc debian/rules build dh build --with python3 --buildsystem pybuild dh_testdir -O--buildsystem=pybuild dh_auto_configure -O--buildsystem=pybuild I: pybuild base:170: python3.4 setup.py config running config dh_auto_build -O--buildsystem=pybuild I: pybuild base:170: /usr/bin/python3 setup.py build running build running build_py creating /home/monsta/3/gdebi-0.9.5.4/.pybuild/pythonX.Y_3.4/build/GDebi copying GDebi/GDebiKDE.py - /home/monsta/3/gdebi-0.9.5.4/.pybuild/pythonX.Y_3.4/build/GDebi copying GDebi/DebPackage.py - /home/monsta/3/gdebi-0.9.5.4/.pybuild/pythonX.Y_3.4/build/GDebi copying GDebi/Version.py - /home/monsta/3/gdebi-0.9.5.4/.pybuild/pythonX.Y_3.4/build/GDebi copying GDebi/__init__.py - /home/monsta/3/gdebi-0.9.5.4/.pybuild/pythonX.Y_3.4/build/GDebi copying GDebi/SimpleGtkbuilderApp.py - /home/monsta/3/gdebi-0.9.5.4/.pybuild/pythonX.Y_3.4/build/GDebi copying GDebi/GDebiCommon.py - /home/monsta/3/gdebi-0.9.5.4/.pybuild/pythonX.Y_3.4/build/GDebi copying GDebi/GDebiCli.py - /home/monsta/3/gdebi-0.9.5.4/.pybuild/pythonX.Y_3.4/build/GDebi copying GDebi/KDEAptDialogs.py - /home/monsta/3/gdebi-0.9.5.4/.pybuild/pythonX.Y_3.4/build/GDebi copying GDebi/GDebiGtk.py - /home/monsta/3/gdebi-0.9.5.4/.pybuild/pythonX.Y_3.4/build/GDebi running build_scripts creating build creating build/scripts-3.4 copying and adjusting gdebi - build/scripts-3.4 copying and adjusting gdebi-gtk - build/scripts-3.4 copying and adjusting gdebi-kde - build/scripts-3.4 changing mode of build/scripts-3.4/gdebi from 644 to 755 changing mode of build/scripts-3.4/gdebi-gtk from 644 to 755 changing mode of build/scripts-3.4/gdebi-kde from 644 to 755 Merging translations into build/gdebi.desktop. Merging translations into build/gdebi-kde.desktop. make[1]: Entering directory '/home/monsta/3/gdebi-0.9.5.4/po' XGETTEXT_ARGS=--msgid-bugs-address=sebastian.heinl...@web.de intltool-update -r -g gdebi; an: . done. ar: ... done. ast: ... done. bg: ... done. bn: ... done. bs: ... done. ca: ... done. ca@valencia: ... done. cs: ... done. da: ... done. de: ... done. el: ... done. en_AU: ... done. en_CA: ... done. en_GB: ... done. eo: ... done. es: done. et: ... done. eu: ... done. fa: . done. fi: ... done. fo: ... done. fr: ... done. gl: ... done. he: ... done. hr: ... done. hu: ... done. hy: . done. id: ... done. it: ... done. ja: ... done. ko: ... done. ku: . done. lt: ... done. mr: .
Bug#754220: virtualbox: FTBFS with GCC 4.9 as default
I see there's a new fixed version waiting at http://mentors.debian.net/package/virtualbox
Bug#755067: xserver-xorg-core upgrade wants to remove virtualbox-guest-x11 due to incompatible ABI version
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 xserver-xorg-core now provides xorg-video-abi-18. Please upgrade or rebuild the Guest Additions to reflect these ABI changes.
Bug#741236: can't reproduce it now
Hmm, I can't reproduce it anymore with lightdm-gtk-greeter 1.8.4-1 (Testing).
Bug#742790: is it worth it?
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. Trouble? Contact listmas...@lists.debian.org
Bug#722989: bug 722989
Is this the reason the package has been removed from Testing? Maybe it's time to apply the proposed patch?
Bug#741236: +1
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 comments above, but haven't found any errors in these logs in my system.
Bug#731077: (no subject)
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
Bug#741154: Synaptic crashes if you start pressing keys too early during program start
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 part of keystrokes went into gdb console, and later Synaptic window appeared, gained focus and crashed upon receiving the rest of the keyboard input. $ sudo gdb synaptic [sudo] password for monsta: GNU gdb (GDB) 7.6.1 (Debian 7.6.1-1) Copyright (C) 2013 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type show copying and show warranty for details. This GDB was configured as x86_64-linux-gnu. For bug reporting instructions, please see: http://www.gnu.org/software/gdb/bugs/... Reading symbols from /usr/sbin/synaptic...(no debugging symbols found)...done. (gdb) run Starting program: /usr/sbin/synaptic warning: Could not load shared library symbols for linux-vdso.so.1. Do you need set solib-search-path or set sysroot? a[Thread debugging using libthread_db enabled] Using host libthread_db library /lib/x86_64-linux-gnu/libthread_db.so.1. dasdasdasd (synaptic:4804): Gtk-WARNING **: GtkNotebook 0xa12340 is mapped but visible child GtkLabel 0x9b1e80 is not mapped (synaptic:4804): Gtk-WARNING **: GtkNotebook 0xa12340 is mapped but visible child GtkLabel 0xa59320 is not mapped (synaptic:4804): Gtk-WARNING **: GtkNotebook 0xa12340 is mapped but visible child GtkLabel 0xa59be0 is not mapped (synaptic:4804): Gtk-WARNING **: GtkNotebook 0xa12340 is mapped but visible child GtkLabel 0xa59d20 is not mapped (synaptic:4804): Gtk-WARNING **: GtkNotebook 0xa12340 is mapped but visible child GtkLabel 0xaa11d0 is not mapped (synaptic:4804): Gtk-WARNING **: GtkNotebook 0xa12340 is mapped but visible child GtkLabel 0x9b1e80 is not mapped (synaptic:4804): Gtk-WARNING **: GtkNotebook 0xa12340 is mapped but visible child GtkLabel 0xa59320 is not mapped (synaptic:4804): Gtk-WARNING **: GtkNotebook 0xa12340 is mapped but visible child GtkLabel 0xa59be0 is not mapped (synaptic:4804): Gtk-WARNING **: GtkNotebook 0xa12340 is mapped but visible child GtkLabel 0xa59d20 is not mapped (synaptic:4804): Gtk-WARNING **: GtkNotebook 0xa12340 is mapped but visible child GtkLabel 0xaa11d0 is not mapped (synaptic:4804): GLib-GObject-CRITICAL **: g_object_set_data: assertion `G_IS_OBJECT (object)' failed (synaptic:4804): GLib-GObject-WARNING **: invalid (NULL) pointer instance (synaptic:4804): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed (synaptic:4804): Gtk-WARNING **: GtkNotebook 0xa12340 is mapped but visible child GtkLabel 0x9b1e80 is not mapped (synaptic:4804): Gtk-WARNING **: GtkNotebook 0xa12340 is mapped but visible child GtkLabel 0xa59320 is not mapped (synaptic:4804): Gtk-WARNING **: GtkNotebook 0xa12340 is mapped but visible child GtkLabel 0xa59be0 is not mapped (synaptic:4804): Gtk-WARNING **: GtkNotebook 0xa12340 is mapped but visible child GtkLabel 0xa59d20 is not mapped (synaptic:4804): Gtk-WARNING **: GtkNotebook 0xa12340 is mapped but visible child GtkLabel 0xaa11d0 is not mapped Program received signal SIGSEGV, Segmentation fault. 0x00467ae6 in ?? () (gdb) bt full #0 0x00467ae6 in ?? () No symbol table info available. #1 0x0046c239 in ?? () No symbol table info available. #2 0x0046c832 in ?? () No symbol table info available. #3 0x004358c4 in ?? () No symbol table info available. #4 0x00435bfb in ?? () No symbol table info available. #5 0x755cea03 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 No symbol table info available. #6 0x755cdea6 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 No symbol table info available. #7 0x755ce1f8 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 No symbol table info available. #8 0x755ce29c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 No symbol table info available. #9 0x77003435 in gtk_main_iteration () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 No symbol table info available. #10 0x0042a735 in ?? () No symbol table info available. #11 0x77adbcad in OpProgress::OverallProgress(unsigned long long, unsigned long long, unsigned long long, std::string const) () from /usr/lib/x86_64-linux-gnu/libapt-pkg.so.4.12 No symbol table info available. #12 0x77afd122 in pkgDepCache::readStateFile(OpProgress*) () from /usr/lib/x86_64-linux-gnu/libapt-pkg.so.4.12 No symbol table info available. #13 0x77afdcf2 in pkgDepCache::Update(OpProgress*) () from /usr/lib/x86_64-linux-gnu/libapt-pkg.so.4.12 No symbol table info
Bug#731300: patch needs to be applied
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
Bug#735898: pavucontrol segmentation fault
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 unico. If not, posting the relevant lines here won't hurt anyway. [1] http://bugs.debian.org/706330
Bug#733190: upgrading went fine though
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
Bug#706330: A set of themes for reference
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 suggest updating gtk3-engines-unico to the same version (revision 150). It's not that hard. [1] http://box-look.org/content/show.php/?content=136162 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#706330: Re: Some applications segfaults after upgrade to 3.8.0-1
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 changes were applied a year ago. I think it makes more sense to upload a newer version (pre-release of 1.0.3 from trunk) than to apply patches to the older (much older) one. [1] http://bazaar.launchpad.net/~unico-team/unico/trunk/revision/136 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#706330: Re: Some applications segfaults after upgrade to 3.8.0-1
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 test, and what was broken? -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
