Bug#1028305: libcotp12: Update libotp to fix grave bug
Package: libcotp12
Version: 1.2.6-2
Severity: grave
Tags: upstream
Justification: renders package unusable
Dear Maintainer,
libotp, and hence otpclient and possibly other applications using this
library, has a grave bug preventing it to be used. Please update to
1.2.8, released yesterday (a few days after previous buggy version 1.2.7).
More information:
https://github.com/paolostivanin/libcotp/releases/tag/v1.2.8 ("This
release fixes a regression brought with v1.2.7. Users must either update
to this release or rollback to v1.2.6.")
Thanks,
Eugen
Bug#1017798: emacs-el
Hi, I had the same problem, and indeed installing emacs-el solved the issue. Best regards, Eugen
Bug#1005977: fwupd-signed
On 18/02/2022 17:31, Harlan Lieberman-Berg wrote: It looks like this is due to the migration of the efi capsule out to the virtual packages fwupd-signed and fwupd-unsigned. Installing one should fix the problem, but this bug should remain open to fix the underlying Recommends’ bug.-- Indeed, installing fwupd-signed fixes the problem, thank you. Eugen
Bug#1005977: fwupd: Cannot update anymore, fwupdx64.efi... cannot be found
Subject: fwupd: Cannot update anymore, fwupdx64.efi... cannot be found Package: fwupd Version: 1.7.5-1 Severity: grave Justification: renders package unusable Dear Maintainer, fwupd does not work on my system anymore. Here is the error when executing fwupdmgr update: Perform operation? [Y|n]: Downloading? [***] Downloading? [***] Decompressing? [***] Decompressing? [***] Authenticating? [***] Authenticating? [***] /usr/libexec/fwupd/efi/fwupdx64.efi and /usr/libexec/fwupd/efi/fwupdx64.efi.signed cannot be found The update had always worked until a few weeks ago. I do not remember when exactly I updated my system the last time, so I do not know exactly the recent version which introduced the problem for me. Tell me if you need me to check the last versions to see which one precisely exhibits the problem. Thank you, Eugen -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 5.16.0-1-amd64 (SMP w/12 CPU threads; PREEMPT) Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages fwupd depends on: ii libc6 2.33-6 ii libcurl3-gnutls7.81.0-1 ii libefiboot137-6 ii libflashrom1 1.2-5 ii libfwupd2 1.7.5-1 ii libfwupdplugin51.7.5-1 ii libglib2.0-0 2.70.4-1 ii libgnutls303.7.3-4+b1 ii libgudev-1.0-0 237-2 ii libgusb2 0.3.10-1 ii libjcat1 0.1.9-1 ii libjson-glib-1.0-0 1.6.6-1 ii libmbim-glib4 1.26.2-1 ii libmbim-proxy 1.26.2-1 ii libmm-glib01.18.6-1 ii libpolkit-gobject-1-0 0.105-31.1+b1 ii libprotobuf-c1 1.3.3-1+b2 ii libqmi-glib5 1.30.4-1 ii libqmi-proxy 1.30.4-1 ii libsmbios-c2 2.4.3-1 ii libsqlite3-0 3.37.2-2 ii libsystemd0250.3-2 ii libtss2-esys-3.0.2-0 3.1.0-3 ii libxmlb2 0.3.6-2 ii shared-mime-info 2.1-2 Versions of packages fwupd recommends: ii bolt 0.9.2-1 ii dbus 1.12.20-3 pn fwupd-signed ii python33.9.8-1 pn secureboot-db ii udisks22.9.4-1 Versions of packages fwupd suggests: pn gir1.2-fwupd-2.0 -- no debconf information
Bug#998108: reopening 998108
On 21/11/2021 00:43, Christoph Anton Mitterer wrote: On Sat, 2021-11-20 at 15:30 -0800, Josh Triplett wrote: I'm still experiencing this bug regularly, with complete browser UI freezes that require killing and restarting Firefox. Hm perhaps something else? At least I haven't suffered from that particular issue since 94.0-2. 94.0-2 fixed the issue for me too.
Bug#998108: Tracking this bug down
Maybe I am wrong, but, for me, the simplest method to track this bug down is to check the changes between the two versions, 93.0 and 93.0-1+b1. Firefox code has not changed, only one or some libraries it depends on. I thought that the only change is in libvpx version, but, surprisingly, a previous comment mentions that rebuilding firefox with old vpx (libvpx6) still exhibits the bug. I think that libc6 is out of question, because the last package is 19 Sep, too old wrt this bug; the same for gcc-11, the last package being on 21 Oct. Doesn't this (checking the changes) sound like a good approach to find the cause of the problem?
Bug#998108: firefox freezes shortly after start
On Sat, 30 Oct 2021 20:33:31 +0200 Olivier Allard-Jacquin wrote: According to "strace" command, this is look faulted tab open nvidia library, so maybe issue is linker to video acceleration. I do not have nvidia, still I have this problem.
Bug#998108: Freeze with jitsi
I have similar problems. When I go to jitsi, for ex. https://meet.jit.si/toto, firefox is unresponsive: it does not finish loading the tab (the blue point in the tab moves left-right), and clicking anywhere in firefox window (menu, tabs, page content) does not change anything. I need to kill it with ctrl-c (in linux). Nothing is exchanged on the network; CPU is small, cf. 'top' tool: PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 15790 ededu 20 0 3376132 402248 170036 S 13.3 2.5 0:19.66 GeckoMain However, it is the first time I see GeckoMain shown in the first lines of 'top' (13.3% in the example above). Downgrading from 93.0-1+b1 to 93.0-1 fixes the problem.
Bug#947613: [Pkg-utopia-maintainers] Bug#947613: network-manager: Wi-Fi not working (does not get IPv4 address) with 1.22.2-1
On 08/01/2020 16:07, Michael Biebl wrote: Anyone willing to check the proposed fix https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/848b869c6ede3a796872a0b5cd8b2398804c3697 Hi, I tested the proposed patch on top of debian's 1.22.2-1 version. This patch does NOT fix the issue. I would say it is even worse. The network-manager-gnome icon in the task bar (I use awesome window manager) turns around and restarts several times, each time with a different MAC address (as shown by ifconfig) and getting and losing an inet6 address. After around 10 restarts, it finally stops and shows "NetworkManager is not running". I could provide a small video if it helps. Cheers. Eugen
Bug#947613: [Pkg-utopia-maintainers] Bug#947613: network-manager: Wi-Fi not working (does not get IPv4 address) with 1.22.2-1
On 29/12/2019 13:40, Michael Biebl wrote: Can you provide a full, verbose debug log: https://wiki.gnome.org/Projects/NetworkManager/Debugging Which dhcp client do you use: internal, isc-dhcp-client, ...? I made more tests and noticed that when I upgrade from 1.22.0-2 to 1.22.2-1, the IPv4 still works, even if I associate several times to the Internet box. The problem comes when I *restart* my Internet box. So: I have my laptop running and IPv4 ok with 1.22.2-1. I restart my Internet box. Around one minute later, I have an IPv6 address, but no IPv4 address, as shown by syslog: root@snoopy:~# grep IPv /var/log/syslog|tail Dec 30 14:06:04 snoopy avahi-daemon[24644]: Leaving mDNS multicast group on interface wlp1s0.IPv6 with address fe80::bf01:6fea:9592:b415. Dec 30 14:06:04 snoopy avahi-daemon[24644]: Interface wlp1s0.IPv6 no longer relevant for mDNS. Dec 30 14:06:04 snoopy avahi-daemon[24644]: Leaving mDNS multicast group on interface wlp1s0.IPv4 with address 192.168.0.37. Dec 30 14:06:04 snoopy avahi-daemon[24644]: Interface wlp1s0.IPv4 no longer relevant for mDNS. Dec 30 14:07:44 snoopy kernel: [1688643.441802] IPv6: ADDRCONF(NETDEV_CHANGE): wlp1s0: link becomes ready Dec 30 14:07:44 snoopy avahi-daemon[24644]: Joining mDNS multicast group on interface wlp1s0.IPv6 with address fe80::bf01:6fea:9592:b415. Dec 30 14:07:44 snoopy avahi-daemon[24644]: New relevant interface wlp1s0.IPv6 for mDNS. Dec 30 14:07:47 snoopy avahi-daemon[24644]: Leaving mDNS multicast group on interface wlp1s0.IPv6 with address fe80::bf01:6fea:9592:b415. Dec 30 14:07:47 snoopy avahi-daemon[24644]: Joining mDNS multicast group on interface wlp1s0.IPv6 with address 2a01:e0a:290:82e0:5815:8149:bcb4:18b0. Dec 30 14:07:48 snoopy NetworkManager[2495]: [1577711268.6351] policy: set 'chenoisw' (wlp1s0) as default for IPv6 routing and DNS If I restart network-manager-gnome (the icon in the task bar, I use awesome window manager), syslog file insists on IPv6 only: root@snoopy:~# grep IPv /var/log/syslog|tail -11 Dec 30 14:07:48 snoopy NetworkManager[2495]: [1577711268.6351] policy: set 'chenoisw' (wlp1s0) as default for IPv6 routing and DNS Dec 30 14:21:33 snoopy avahi-daemon[24644]: Leaving mDNS multicast group on interface wlp1s0.IPv6 with address 2a01:e0a:290:82e0:5815:8149:bcb4:18b0. Dec 30 14:21:33 snoopy avahi-daemon[24644]: Joining mDNS multicast group on interface wlp1s0.IPv6 with address fe80::bf01:6fea:9592:b415. Dec 30 14:21:33 snoopy avahi-daemon[24644]: Leaving mDNS multicast group on interface wlp1s0.IPv6 with address fe80::bf01:6fea:9592:b415. Dec 30 14:21:33 snoopy avahi-daemon[24644]: Interface wlp1s0.IPv6 no longer relevant for mDNS. Dec 30 14:21:35 snoopy kernel: [1689473.467493] IPv6: ADDRCONF(NETDEV_CHANGE): wlp1s0: link becomes ready Dec 30 14:21:35 snoopy avahi-daemon[24644]: Joining mDNS multicast group on interface wlp1s0.IPv6 with address fe80::bf01:6fea:9592:b415. Dec 30 14:21:35 snoopy avahi-daemon[24644]: New relevant interface wlp1s0.IPv6 for mDNS. Dec 30 14:21:36 snoopy avahi-daemon[24644]: Leaving mDNS multicast group on interface wlp1s0.IPv6 with address fe80::bf01:6fea:9592:b415. Dec 30 14:21:36 snoopy avahi-daemon[24644]: Joining mDNS multicast group on interface wlp1s0.IPv6 with address 2a01:e0a:290:82e0:5815:8149:bcb4:18b0. Dec 30 14:21:38 snoopy NetworkManager[2495]: [1577712098.1291] policy: set 'chenoisw' (wlp1s0) as default for IPv6 routing and DNS root@snoopy:~# ifconfig shows: wlp1s0: flags=4163 mtu 1300 inet6 2a01:e0a:290:82e0:5815:8149:bcb4:18b0 prefixlen 64 scopeid 0x0 inet6 fe80::bf01:6fea:9592:b415 prefixlen 64 scopeid 0x20 ether ... txqueuelen 1000 (Ethernet) RX packets 15747787 bytes 15483453634 (14.4 GiB) [...] Now, I downgrade to previous version: root@snoopy:/home/ededu# dpkg -i *22.* dpkg: warning: downgrading gir1.2-nm-1.0:amd64 from 1.22.2-1 to 1.22.0-2 (Reading database ... 330241 files and directories currently installed.) Preparing to unpack gir1.2-nm-1.0_1.22.0-2_amd64.deb ... Unpacking gir1.2-nm-1.0:amd64 (1.22.0-2) over (1.22.2-1) ... dpkg: warning: downgrading libnm0:amd64 from 1.22.2-1 to 1.22.0-2 Preparing to unpack libnm0_1.22.0-2_amd64.deb ... Unpacking libnm0:amd64 (1.22.0-2) over (1.22.2-1) ... dpkg: warning: downgrading network-manager from 1.22.2-1 to 1.22.0-2 Preparing to unpack network-manager_1.22.0-2_amd64.deb ... Unpacking network-manager (1.22.0-2) over (1.22.2-1) ... Setting up libnm0:amd64 (1.22.0-2) ... Setting up network-manager (1.22.0-2) ... Setting up gir1.2-nm-1.0:amd64 (1.22.0-2) ... Processing triggers for libc-bin (2.29-6) ... Processing triggers for systemd (244-3) ... Processing triggers for dbus (1.12.16-2) ... Processing triggers for man-db (2.9.0-2) ... syslog shows some IPv4 activity: root@snoopy:/home/ededu# grep IPv /var/log/syslog|tail -15 Dec 30 14:21:38 snoopy NetworkManager[2495]: [1577712098.1291] policy: set 'chenoisw' (wlp1s0) as default for
Bug#947613: network-manager: Wi-Fi not working (does not get IPv4 address) with 1.22.2-1
Package: network-manager Version: 1.22.0-2 Severity: grave Justification: renders package unusable Dear Maintainer, I have an Internet box and connect to it through Wi-Fi. After upgrading network-manager to 1.22.2-1, my machine does not get an IPv4 address anymore. Specifically, ifconfig shows: wlp1s0: flags=4163 mtu 1300 inet6 ... prefixlen 64 scopeid 0x0 inet6 ... prefixlen 64 scopeid 0x20 ether ... txqueuelen 1000 (Ethernet) RX packets 14389956 bytes 13801531443 (12.8 GiB) RX errors 0 dropped 14956 overruns 0 frame 0 TX packets 3398391 bytes 958204966 (913.8 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 After downloading an older version of network-manager (from snapshot.debian.org) and downgrading everything works fine: root@snoopy:# dpkg -i *1.22.0-2* dpkg: warning: downgrading gir1.2-nm-1.0:amd64 from 1.22.2-1 to 1.22.0-2 (Reading database ... 330245 files and directories currently installed.) Preparing to unpack gir1.2-nm-1.0_1.22.0-2_amd64.deb ... Unpacking gir1.2-nm-1.0:amd64 (1.22.0-2) over (1.22.2-1) ... dpkg: warning: downgrading libnm0:amd64 from 1.22.2-1 to 1.22.0-2 Preparing to unpack libnm0_1.22.0-2_amd64.deb ... Unpacking libnm0:amd64 (1.22.0-2) over (1.22.2-1) ... dpkg: warning: downgrading network-manager from 1.22.2-1 to 1.22.0-2 Preparing to unpack network-manager_1.22.0-2_amd64.deb ... Unpacking network-manager (1.22.0-2) over (1.22.2-1) ... Setting up libnm0:amd64 (1.22.0-2) ... Setting up network-manager (1.22.0-2) ... Setting up gir1.2-nm-1.0:amd64 (1.22.0-2) ... Processing triggers for libc-bin (2.29-6) ... Processing triggers for systemd (244-3) ... Processing triggers for dbus (1.12.16-2) ... Processing triggers for man-db (2.9.0-2) ... Best regards, Eugen Dedu http://eugen.dedu.free.fr -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 5.2.0-3-amd64 (SMP w/8 CPU cores) Kernel taint flags: TAINT_WARN Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages network-manager depends on: ii adduser3.118 ii dbus 1.12.16-2 ii init-system-helpers1.57 ii libaudit1 1:2.8.5-2+b1 ii libbluetooth3 5.50-1+b1 ii libc6 2.29-6 ii libcurl3-gnutls7.67.0-2 ii libglib2.0-0 2.62.3-2 ii libgnutls303.6.11.1-2 ii libjansson42.12-1 ii libmm-glib01.10.4-0.1 ii libndp01.6-1+b1 ii libnewt0.520.52.21-4 ii libnm0 1.22.0-2 ii libpam-systemd 244-3 ii libpolkit-agent-1-00.105-26 ii libpolkit-gobject-1-0 0.105-26 ii libpsl50.20.2-2 ii libreadline8 8.0-3 ii libselinux13.0-1 ii libsystemd0244-3 ii libteamdctl0 1.29-1 ii libudev1 244-3 ii libuuid1 2.34-0.1 ii policykit-10.105-26 ii udev 244-3 ii wpasupplicant 2:2.9-3+b1 Versions of packages network-manager recommends: ii crda 3.18-1 ii dnsmasq-base [dnsmasq-base] 2.80-1.1 ii iptables 1.8.4-1 ii modemmanager 1.10.4-0.1 pn ppp Versions of packages network-manager suggests: ii isc-dhcp-client 4.4.1-2 pn libteam-utils -- no debconf information
Bug#907518: [RFC] Disable TLSv1.0 by default, but allow enabling it
On 05/12/2018 09:52, Andrej Shadura wrote: Hardcode a minimal version just for wpa-supplicant to TLSv1.0? What about ciphers? Anything else? Hi, In order to make it work with eduroam I have to change in ciphers too like this: MinProtocol = TLSv1.2 -> 1 CipherString = DEFAULT@SECLEVEL=2 -> 1 Best regards, -- Eugen
Bug#910807: webext-ublock-origin: Does not work with firefox
Package: webext-ublock-origin Version: 1.17.0+dfsg-1 Severity: grave Justification: renders package unusable Dear Maintainer, After upgrading to 1.17.0+dfsg-1 version, the package does not work with firefox anymore: it is not shown in Tools->Add-ons, and there is no icon at the right of the URL bar. Regards, Eugen Dedu -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 4.18.0-2-amd64 (SMP w/8 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages webext-ublock-origin depends on: ii fonts-font-awesome 5.0.10+really4.7.0~dfsg-1 Versions of packages webext-ublock-origin recommends: ii firefox 62.0.3-1 Versions of packages webext-ublock-origin suggests: pn ublock-origin-doc -- no debconf information
Bug#899365: [Pkg-mozext-maintainers] Bug#899365: webext-ublock-origin: webext package does not work in Firefox
On 06/07/18 16:19, Sean Whitton wrote: Hello Daniel, On Fri, Jul 06 2018, Daniel Baumann wrote: I've looked at the git repository on salsa, and your last commit: https://salsa.debian.org/daniel-guest/ublock-origin/commit/0b9e4452552ce6243ae088a7880ef4d67c82d5f8 fixes this for sid (provided one has fonts-font-awesome 4.x which got recently re-uploaded; it works flawlessly but doesn't display icons in the popup when using fonts-font-awesome 5.x). would you mind the fix? That is a fix for a different bug. I didn't upload it because this bug is still present, making the package useless. Or is this bug no longer reproducible? I confirm that the commit on salsa above makes ublock origin working with my firefox. -- Eugen
Bug#899365: [Pkg-mozext-maintainers] Bug#899365: webext-ublock-origin: webext package does not work in Firefox
On 06/07/18 14:26, Daniel Baumann wrote: Hi Sean, I've looked at the git repository on salsa, and your last commit: https://salsa.debian.org/daniel-guest/ublock-origin/commit/0b9e4452552ce6243ae088a7880ef4d67c82d5f8 fixes this for sid (provided one has fonts-font-awesome 4.x which got recently re-uploaded; it works flawlessly but doesn't display icons in the popup when using fonts-font-awesome 5.x). would you mind the fix? What a beautiful day! Finally, an Internet without ads again! Thank you for the information! (It did not worked after restarting firefox, no icon in the firefox's toolbar, I had to disable and enable the plugin too.) -- Eugen
Bug#899365: Same thing
Hi, I have the same problem: the extension does not show up in the extension list in Firefox. Do you know how to debug? Cheers, -- Eugen
Bug#745405: [src:opal] Source package contains non-free IETF RFC/I-D
On 16/01/16 12:35, Francesco Poli wrote:
On Sat, 25 Oct 2014 19:53:57 +0200 Eugen Dedu wrote:
tags 745405 pending
Hello,
I see that this bug report has been pending for quite a long time.
I wondered what happened and saw that a changelog entry claims to fix
the issue, but seems to forget the Closes directive:
opal (3.10.10~dfsg2-1) unstable; urgency=low
* Remove one non free document (RFC) from source package.
[...]
-- Eugen Dedu <eugen.d...@pu-pm.univ-fcomte.fr> Mon, 27 Oct 2014 05:51:57
+0200
Maybe this bug report should be closed with a message to
<745405-cl...@bugs.debian.org> having the following pseudo-header:
Source: opal
Source-Version: 3.10.10~dfsg2-1
Do you agree?
Thank you very much for your e-mail. I have forgotten about this bug...
In that commit I removed
plugins/audio/iLBC/iLBC/draft-ietf-avt-ilbc-codec-05.txt file, but it
remains several rfc files. I have forgotten why I have not removed them
too, I think I wanted to investigate more what the problem is, and
afterwards I forgot about them.
I will take care of it soon (probably "find . -name rfc\*.txt -exec rm
{}" is the simplest solution), thank you again!
--
Eugen
Bug#797438: ekiga: FTBFS with g++-5: error: 'cout' is not a member of 'std'
On 30/08/15 20:11, Simon McVittie wrote: Source: ekiga Version: 4.0.1-5 Severity: serious Justification: fails to build from source (but built successfully in the past) I've just sponsored an upload of ptlib to do the libstdc++ transition, and test-built its reverse dependencies. opal and h323plus were successful, Good. but ekiga failed to build: ../../plugins/loudmouth/loudmouth-dialect.cpp: In member function 'void LM::Dialect::on_open_group_chat_submitted(bool, Ekiga::Form)': ../../plugins/loudmouth/loudmouth-dialect.cpp:153:3: error: 'cout' is not a member of 'std' std::cout Should enter the room ' name ' with pseudonym ' pseudo ' std::endl; ^ Makefile:641: recipe for target '../../plugins/loudmouth/loudmouth-dialect.lo' failed Full log attached. I think this is probably because it doesn't include all the headers it should, but in previous versions of libstdc++, the header that declares std::cout happened to be pulled in by a header that this file does include and so the build succeeded. I made a fix for a bug to this upstream, https://git.gnome.org/browse/ekiga/commit/?id=8561e159f2095651d8. I will do an upload as soon as ptlib enters unstable. The ptlib upload is in NEW but should hopefully be processed reasonably soon. I'm uploading source and an amd64 build to https://people.debian.org/~smcv/ if you need them before then. No, there is no need. Thanks, -- Eugen
Bug#778074: Patch for GCC 5 build issue
On 25/06/15 19:27, Martin Michlmayr wrote: tags 778074 + patch thanks Here's a patch for the GCC 5 build issue. Sorry, I'm not sure how best to send patches for packages using quilt. BTW, it seems this issue is no longer present upstream: svn ls svn://svn.code.sf.net/p/opalvoip/code/ptlib/trunk/include/ptlib/ | grep crit It seems this is properly handled in configure now. Thank you very much, I have uploaded it. I forgot to add your name in the changelog, sorry. Kind regards, -- Eugen -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#789024: g++-mingw-w64: Cannot upgrade, wrong dependency
Package: g++-mingw-w64 Version: 4.9.2-10+15.1 Severity: grave Justification: renders package unusable Hi Stephen, With the recent upload in unstable, I cannot upgrade the package anymore: root@snoopy:/home/ededu# apt-get install g++-mingw-w64 ... The following packages have unmet dependencies: g++-mingw-w64 : Depends: gcc-mingw-w64-base (= 4.9.2-20+15.2) but 4.9.2-21+15.2 is to be installed snoopy:~$ apt-cache show gcc-mingw-w64-base Package: gcc-mingw-w64-base Source: gcc-mingw-w64 (15.2) Version: 4.9.2-21+15.2 ... Cheers, Eugen -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 4.0.0-1-amd64 (SMP w/8 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages g++-mingw-w64 depends on: ii g++-mingw-w64-i6864.9.2-21+15.2 ii g++-mingw-w64-x86-64 4.9.2-21+15.2 ii gcc-mingw-w64-base4.9.2-21+15.2 g++-mingw-w64 recommends no packages. g++-mingw-w64 suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#789024: g++-mingw-w64: Cannot upgrade, wrong dependency
On 17/06/15 10:59, Stephen Kitt wrote: In the meantime, I'd be very interested in your feedback on the version that's in experimental, and which is installable as is! It's built with gcc 5... Unfortunately, ekiga does not build currently for windows because I need a recent gtk and the last gtk provided is 3.6. I will do builds again when I have the time to tackle this issue, and let you informed. Thanks, -- Eugen -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#769941: Not because of gstreamer
I often start iceweasel as another user (with sux) and when I load gmail I have this error too: ** (iceweasel:17775): CRITICAL **: gst_app_src_set_size: assertion 'GST_IS_APP_SRC (appsrc)' failed However, iceweasel does not crash. So I think the crash has nothing to do with the assertion failed. I use libgstreamer-plugins-base1.0-0 1.4.4-2 (current unstable). -- Eugen -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#768581: opal: FTBFS in experimental: error: 'CodecID' has not been declared
On 08/11/14 15:24, Andreas Beckmann wrote: Package: opal Version: 3.12.8~dfsg-1 Severity: serious Justification: fails to build from source (but built successfully in the past) Hi, opal/experimental fails to build in a current sid+experimental environment, see https://buildd.debian.org/status/fetch.php?pkg=opalarch=arm64ver=3.12.8~dfsg-1stamp=1414123156 [CC] .common/dyna.cxx In file included from ../common/ffmpeg.cxx:41:0: .../common/ffmpeg.h:123:30: error: 'CodecID' has not been declared virtual bool InitEncoder(CodecID codecId); ^ .../common/ffmpeg.h:124:30: error: 'CodecID' has not been declared virtual bool InitDecoder(CodecID codecId); ^ I could reproduce this rebuilding it for amd64 locally. For me, the version in experimental should be simply removed. Honestly, I prefer spending the little time I have on testing version, and or on version 3.14 or master upstream, as a developer. Kind regards, -- Eugen -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#728452: opal: FTBFS if $HOME does not exist
tags 728452 experimental thanks On 21/10/14 17:49, Mark Purcell wrote: I am trying to fix this bug. Where is the debian repository corresponding to opal v10, used to package opal 3.10.10? As far as I see, http://anonscm.debian.org/viewvc/pkg-voip/opal/ contains only trunk (opal v12 in experimental), not the stable opal (v10). Eugen, It should be under branches, but it looks like it hasn't been created yet. Ok, I made that. Now, about this bug: it appears only in experimental (v3.12). It has nothing to do with unstable version (v3.10). Upstream, this exists only in v3.12, it does not appear in v3.10 and v3.14. So putting low priority, I am fixing opal unstable bugs now... -- Eugen -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#728452: opal: FTBFS if $HOME does not exist
On 19/10/14 16:37, Balint Reczey wrote: Hi Eugen, Hi Mark, I am trying to fix this bug. Where is the debian repository corresponding to opal v10, used to package opal 3.10.10? As far as I see, http://anonscm.debian.org/viewvc/pkg-voip/opal/ contains only trunk (opal v12 in experimental), not the stable opal (v10). Cheers, -- Eugen -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#728452: opal: FTBFS if $HOME does not exist
On 19/10/14 16:37, Balint Reczey wrote: Hi Eugen, Hi everybody, According to https://qa.debian.org/popcon.php?package=opal, libopal-doc has value 0 at Vote column. I think the best is to simply remove the libopal-doc package. The API is available at http://files.opalvoip.org/docs/opal-v3_10 anyway. Do you disagree with this? Cheers, -- Eugen -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#728452: opal: FTBFS if $HOME does not exist
On 19/10/14 16:37, Balint Reczey wrote: Since May there have ben several stable releases starting with 3.14.0. It would be nice if the package could be updated before the freeze. The package cannot be updated, because it breaks API in major ways with each version (even minor one!), and most importantly it breaks ekiga. Ekiga has almost finished the transition, but it is not in releasable state. So I will just fix this bug (FTFBS if HOME inexistent). Note that docs target was removed in v14 and trunk (I suppose it should be replaced with a simple call to doxygen), hence opal-docs package needs to be revisited in the future. Anyway, I will do a debian-only fix. -- Eugen -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#728452: opal: FTBFS if $HOME does not exist
On 19/10/14 16:37, Balint Reczey wrote: Since May there have ben several stable releases starting with 3.14.0. It would be nice if the package could be updated before the freeze. You are right. I am spending a very busy period, I am sorry. I will do it tomorrow. -- Eugen -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#728452: opal: FTBFS if $HOME does not exist
On 03/05/14 06:19, Reinhard Tartler wrote: Control: reopen -1 On Sun, Dec 29, 2013 at 02:30:48PM +1100, Mark Purcell wrote: Version: 3.12.8~dfsg-1 On Fri, 1 Nov 2013 13:47:47 Andreas Beckmann wrote: Why does it call cd with no argument? Thanks Andreas, Upstream have been mucking around with the build environment. Unfortunately, the problem is still there, it just happens only when sbuild is building arch:all packages, that is, the option -A is not passed. Buildds don't pass this option, but this bug for instance prevents building an NMU. I believe the problem is in http://sources.debian.net/src/opal/3.12.8~dfsg-1/make/toplevel.mak.in#L760 Here, the makefile is trying to change to PTLIBDIR. How is this supposed to work? PTLIBDIR is the directory where ptlib is installed. As just written in previous e-mail, I do not think it is worth trying to fix this bug, since 3.12.8 will be replaced it 3.14 in unstable, and 3.12 will just disappear. -- Eugen -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#728452: opal: FTBFS if $HOME does not exist
On 03/05/14 20:02, Reinhard Tartler wrote: On 03.05.2014 13:59, Eugen Dedu wrote: As just written in previous e-mail, I do not think it is worth trying to fix this bug, since 3.12.8 will be replaced it 3.14 in unstable, and 3.12 will just disappear. What's the timeline for having 3.14 in unstable? Normally it should be this summer, and I do my best to have it before september (the freeze). -- Eugen -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#736307: ekiga-dbg: unhandled symlink to directory conversion: /usr/share/doc/PACKAGE
On 22/01/14 04:06, Andreas Beckmann wrote: Package: ekiga-dbg Version: 4.0.1-2 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, an upgrade test with piuparts revealed that your package installs files over existing symlinks and possibly overwrites files owned by other packages. This usually means an old version of the package shipped a symlink but that was later replaced by a real (and non-empty) directory. This kind of overwriting another package's files cannot be detected by dpkg. This was observed on the following upgrade paths: wheezy - jessie For /usr/share/doc/PACKAGE this may not be problematic as long as both packages are installed, ship byte-for-byte identical files and are upgraded in lockstep. But once one of the involved packages gets removed, the other one will lose its documentation files, too, including the copyright file, which is a violation of Policy 12.5: http://www.debian.org/doc/debian-policy/ch-docs.html#s-copyrightfile For other overwritten locations anything interesting may happen. Note that dpkg intentionally does not replace directories with symlinks and vice versa, you need the maintainer scripts to do this. See in particular the end of point 4 in http://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#s-unpackphase It is recommended to use the dpkg-maintscript-helper commands 'dir_to_symlink' and 'symlink_to_dir' (available since dpkg 1.17.2) to perform the conversion, ideally using d/$PACKAGE.mainstscript. See dpkg-maintscript-helper(1) and dh_installdeb(1) for details. From the attached log (usually somewhere in the middle...): 1m42.0s ERROR: FAIL: silently overwrites files via directory symlinks: /usr/share/doc/ekiga-dbg/changelog.Debian.amd64.gz (ekiga-dbg) != /usr/share/doc/ekiga/changelog.Debian.amd64.gz (ekiga) /usr/share/doc/ekiga-dbg/changelog.Debian.gz (ekiga-dbg) != /usr/share/doc/ekiga/changelog.Debian.gz (ekiga) /usr/share/doc/ekiga-dbg/changelog.gz (ekiga-dbg) != /usr/share/doc/ekiga/changelog.gz (ekiga) /usr/share/doc/ekiga-dbg/copyright (ekiga-dbg) != /usr/share/doc/ekiga/copyright (ekiga) Hi Andreas, I spent much time trying to understand and figure how to fix this bug. For now, I think the solution is to: - put /usr/share/doc/ekiga-dbg as symlink to ekiga - add preinst, postinst and postrm with the following line: dpkg-maintscript-helper dir_to_symlink \ pathname new-target prior-version package -- $@ - add Pre-Depends: dpkg (= 1.17.5) I have to test all this, do you agree with the above solution? Anyway, my main concern is: why a so complicated solution for such a minor thing (sometimes in the past someone changed the symlink to a directory)? Is there other solution, for ex. just ship an ekiga-dbg without /usr/share/doc? Why not just fix dpkg instead of forcing all related packages to add preinst, postinst, postrm etc.? Kind regards, -- Eugen -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#736307: ekiga-dbg: unhandled symlink to directory conversion: /usr/share/doc/PACKAGE
tags 736307 pending thanks On 05/03/14 16:59, Eugen Dedu wrote: On 22/01/14 04:06, Andreas Beckmann wrote: Package: ekiga-dbg Version: 4.0.1-2 Severity: serious User: debian...@lists.debian.org Usertags: piuparts [...] From the attached log (usually somewhere in the middle...): 1m42.0s ERROR: FAIL: silently overwrites files via directory symlinks: /usr/share/doc/ekiga-dbg/changelog.Debian.amd64.gz (ekiga-dbg) != /usr/share/doc/ekiga/changelog.Debian.amd64.gz (ekiga) /usr/share/doc/ekiga-dbg/changelog.Debian.gz (ekiga-dbg) != /usr/share/doc/ekiga/changelog.Debian.gz (ekiga) /usr/share/doc/ekiga-dbg/changelog.gz (ekiga-dbg) != /usr/share/doc/ekiga/changelog.gz (ekiga) /usr/share/doc/ekiga-dbg/copyright (ekiga-dbg) != /usr/share/doc/ekiga/copyright (ekiga) Hi Andreas, I spent much time trying to understand and figure how to fix this bug. For now, I think the solution is to: - put /usr/share/doc/ekiga-dbg as symlink to ekiga - add preinst, postinst and postrm with the following line: dpkg-maintscript-helper dir_to_symlink \ pathname new-target prior-version package -- $@ - add Pre-Depends: dpkg (= 1.17.5) I have to test all this, do you agree with the above solution? Anyway, my main concern is: why a so complicated solution for such a minor thing (sometimes in the past someone changed the symlink to a directory)? Is there other solution, for ex. just ship an ekiga-dbg without /usr/share/doc? Why not just fix dpkg instead of forcing all related packages to add preinst, postinst, postrm etc.? After two additional hours, I succeeded to do these modifications and check that it works. Thank you, -- Eugen -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#735600: ekiga: Segmentation fault after libpt2.10.10 upgrade
On 10/02/14 23:49, Sylvain BOILARD wrote: notfixed 735600 2.10.10~dfsg-4 thanks Hi, I still encounter crashes seemingly caused by libpt with Ekiga. Here is the backtrace I get when Ekiga crashes after the program has ran for a while: We plan to use a newer version of ptlib very soon, which had many fixes. I am pretty sure this bug is fixed, since I remember some changes on Contacts. I suggest to wait until this new release appears. Your crash is not related to ptlib upgrade, as far as I see. Are you sure that you did not have the crash before, and now you have it? -- Eugen -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#735791: ekiga: FTBFS: configure: error: Could not find a version of the library!
Control: tag -1 pending Thank you for the info and the patch! On 25/01/14 14:24, Andreas Beckmann wrote: Control: tag -1 patch On 2014-01-25 08:50, Eugen Dedu wrote: To fix the bug I had to modify an .m4 file. The .m4 file alone is not sufficient, I had to modify the configure file too. Because autotools programs changed since the time the configure file was generated, I had two choices: - either I manually patch the configure file with the few lines changed by the modification given by the .m4 file - or I regenerate the configure, but the patch will be huge. There is a third solution: use dh_autoreconf and regenerate configure at compile time I used the first method. For an unknown and mysterious reason, for the two architectures it failed. Multiarch libdir detection by autoconf does not work on i386: host arch is i486-linux-gnu, therefore it searches in /usr/lib/i486-linux-gnu, but multiarch libdir is /usr/lib/i386-linux-gnu. ax_boost_base.m4 is not working correctly for Debian/i386 and needs more patching ... Should I use the second solution? Wouldn't help. Patch attached. -- Eugen -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#735791: ekiga: FTBFS: configure: error: Could not find a version of the library!
On 25/01/14 00:55, Andreas Beckmann wrote: Followup-For: Bug #735791 The problem still occured on i386 and kfreebsd-i386: https://buildd.debian.org/status/fetch.php?pkg=ekigaarch=i386ver=4.0.1-3stamp=1390051917 https://buildd.debian.org/status/fetch.php?pkg=ekigaarch=kfreebsd-i386ver=4.0.1-3stamp=1390052002 To fix the bug I had to modify an .m4 file. The .m4 file alone is not sufficient, I had to modify the configure file too. Because autotools programs changed since the time the configure file was generated, I had two choices: - either I manually patch the configure file with the few lines changed by the modification given by the .m4 file - or I regenerate the configure, but the patch will be huge. I used the first method. For an unknown and mysterious reason, for the two architectures it failed. Should I use the second solution? Best regards, -- Eugen -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#735600: ekiga: Segmentation fault after libpt2.10.10 upgrade
On 16/01/14 20:01, Torquil Macdonald Sørensen wrote: Package: ekiga Version: 4.0.1-2+b2 Severity: grave Justification: renders package unusable After the upgrade of libpt2.10.10 from 2.10.10~dfsg-2.1 to 2.10.10~dfsg-3, Ekiga crashes on every startup, when it registers at ekiga.net. Downgrading to 2.10.10~dfsg-2.1 fixes the problem. Pfff, I will take a look tomorrow... -- Eugen -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#733396: ptlib: FTBFS: ptlib/common/getdate.y:112:18: error: conflicting types for 'PTime_yyparse'
On 08/01/14 14:38, Eugen Dedu wrote: On 07/01/14 09:38, Mark Purcell wrote: [...] I have created a branch to track luyten (2.10.x) separate from trunk: svn://svn.debian.org/pkg-voip/ptlib/branches/ptlib2.10-luyten/ Ok, I will make a commit with the patch from http://sourceforge.net/p/opalvoip/patches/259/, it is smaller than what I proposed above. As I am in holidays, I think I cannot do it before Monday. I am trying to do the upload, but I notice that you has recently modified the repository to track 2.10.11 release (whereas debian unstable has 2.10.10 release). There are two choices now: - either we upload 2.10.11, in that case I cannot do the upload, since I am not DD, but DM. In this case you can add in debian/changelog the following entry that I removed: ptlib (2.10.11~dfsg-1) UNRELEASED; urgency=medium * New Upstream release * Track luyten svn://svn.debian.org/pkg-voip/ptlib/branches/ptlib2.10-luyten/ * NEW package libpt2.10.11 - match soname - or upload 2.10.10, which I can upload myself. Marc, what do you prefer? -- Eugen -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#733396: ptlib: FTBFS: ptlib/common/getdate.y:112:18: error: conflicting types for 'PTime_yyparse'
On 07/01/14 09:38, Mark Purcell wrote: On Fri, 3 Jan 2014 15:16:12 Eugen Dedu wrote: The simplest solution is to apply the upstream fix, http://sourceforge.net/p/opalvoip/code/31087/ I would like to do it, but I am a bit disoriented with the svn repository of ptlib. Mark, could you tell me where are the repositories of trunk and unstable/testing of ptlib? As far as I see, both are in the same place, svn://svn.debian.org/pkg-voip/ptlib/trunk ?! Thanks Eugen, I have created a branch to track luyten (2.10.x) separate from trunk: svn://svn.debian.org/pkg-voip/ptlib/branches/ptlib2.10-luyten/ Ok, I will make a commit with the patch from http://sourceforge.net/p/opalvoip/patches/259/, it is smaller than what I proposed above. As I am in holidays, I think I cannot do it before Monday. -- Eugen -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#733396: ptlib: FTBFS: ptlib/common/getdate.y:112:18: error: conflicting types for 'PTime_yyparse'
On 28/12/13 19:20, David Suárez wrote: Source: ptlib Version: 2.10.10~dfsg-2.1 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20131226 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Hi, The simplest solution is to apply the upstream fix, http://sourceforge.net/p/opalvoip/code/31087/ I would like to do it, but I am a bit disoriented with the svn repository of ptlib. Mark, could you tell me where are the repositories of trunk and unstable/testing of ptlib? As far as I see, both are in the same place, svn://svn.debian.org/pkg-voip/ptlib/trunk ?! -- Eugen -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#729230: doxygen: hangs during ptlib build
On 10/11/13 19:10, Helmut Grohne wrote: On Sun, Nov 10, 2013 at 06:58:35PM +0100, Samuel Thibault wrote: * Check for duplicates, especially #718694 Most probably a duplicate then, indeed, I failed to find it among the open bugs. Removing code#operator/code in the header does fix the issue. Cloning as a bug against ptlib and merging with the duplicate. Thanks for tracking it down! This issue is solved in doxygen 1.8.5-1 sitting in NEW. As soon as it hits sid, you can downgrade the ptlib bug. ^ You mean *close* the ptlib bug, isn't it? -- Eugen -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#724731: pam
Just to say that I had the same problem: gdm3 did not start, a black screen with 2 lines of error were shown. startx showed a black screen with mouse movement only working. Bizarre, startx worked when removing and reinstalling right afterwards gnome-shell gnome-session gdm3 gnome-core; I have not investigated more since then. Installing libpam-systemd makes both work. -- Eugen -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#720824: opal: FTBFS with libav9: h263-1998.cxx:320:27: error: 'CODEC_FLAG_H263P_UMV' was not declared in this scope
On 12/09/13 19:46, Sebastian Ramacher wrote: Control: tags -1 + patch On 2013-09-12 15:36:20, Eugen Dedu wrote: On 12/09/13 15:29, Sebastian Ramacher wrote: On 2013-09-06 16:16:59, Eugen Dedu wrote: On 06/09/13 15:34, Moritz Muehlenhoff wrote: On Sun, Aug 25, 2013 at 03:22:31PM +0200, David Suárez wrote: Source: opal Version: 3.10.10~dfsg-2 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20130825 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Related to current libav9 transition (see #706798). ^ h263-1998.cxx: In member function 'virtual bool H263_RFC2190_EncoderContext::Init()': h263-1998.cxx:606:24: error: 'CODEC_FLAG_H263P_UMV' was not declared in this scope m_context-flags = ~CODEC_FLAG_H263P_UMV; ^ h263-1998.cxx:611:24: error: 'CODEC_FLAG_H263P_AIV' was not declared in this scope m_context-flags = ~CODEC_FLAG_H263P_AIV; ^ h263-1998.cxx:612:24: error: 'CODEC_FLAG_H263P_SLICE_STRUCT' was not declared in this scope m_context-flags = ~CODEC_FLAG_H263P_SLICE_STRUCT; ^ make[5]: *** [/«PKGBUILDDIR»/plugins/../lib_linux_x86_64/plugins/h263_ffmpeg/h263-1998.o] Error 1 This is fixed in the version from experimental (ptlib from experimental is also needed), which compiles fine against current libav. Thank you for this information. Note that ekiga does not yet work with opal/experimental, so opal cannot go to unstable right now. Would it be possible to backport the libav 9 fixes for now? I found some patches on the web that make it compile, but they don't fix plugins/video/common/dyna.cxx which uses dlopen/dlsym to look up the (old) libav symbols (thankfully this is properly fixed in experimental). From what I can tell it might be enough to just replace the loading and calls to Fav* in FFMPEGLibrary with plain calls of av* functions. It is on my TODO list, but I am in short time currently... Please give me all the pointers you have. My plan is to backport the related changes from experimental version to unstable/testing version. I gave it a try and ended up with the attached patch. What do you think of it? Ok, thank you. I will test it and upload it. I took a glance over your patch, without looking in detail, since it will be removed with the version in experimental anyway. -- Eugen -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#720824: opal: FTBFS with libav9: h263-1998.cxx:320:27: error: 'CODEC_FLAG_H263P_UMV' was not declared in this scope
On 12/09/13 19:46, Sebastian Ramacher wrote: Control: tags -1 + patch On 2013-09-12 15:36:20, Eugen Dedu wrote: On 12/09/13 15:29, Sebastian Ramacher wrote: On 2013-09-06 16:16:59, Eugen Dedu wrote: On 06/09/13 15:34, Moritz Muehlenhoff wrote: On Sun, Aug 25, 2013 at 03:22:31PM +0200, David Suárez wrote: Source: opal Version: 3.10.10~dfsg-2 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20130825 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Related to current libav9 transition (see #706798). ^ h263-1998.cxx: In member function 'virtual bool H263_RFC2190_EncoderContext::Init()': h263-1998.cxx:606:24: error: 'CODEC_FLAG_H263P_UMV' was not declared in this scope m_context-flags = ~CODEC_FLAG_H263P_UMV; ^ h263-1998.cxx:611:24: error: 'CODEC_FLAG_H263P_AIV' was not declared in this scope m_context-flags = ~CODEC_FLAG_H263P_AIV; ^ h263-1998.cxx:612:24: error: 'CODEC_FLAG_H263P_SLICE_STRUCT' was not declared in this scope m_context-flags = ~CODEC_FLAG_H263P_SLICE_STRUCT; ^ make[5]: *** [/«PKGBUILDDIR»/plugins/../lib_linux_x86_64/plugins/h263_ffmpeg/h263-1998.o] Error 1 This is fixed in the version from experimental (ptlib from experimental is also needed), which compiles fine against current libav. Thank you for this information. Note that ekiga does not yet work with opal/experimental, so opal cannot go to unstable right now. Would it be possible to backport the libav 9 fixes for now? I found some patches on the web that make it compile, but they don't fix plugins/video/common/dyna.cxx which uses dlopen/dlsym to look up the (old) libav symbols (thankfully this is properly fixed in experimental). From what I can tell it might be enough to just replace the loading and calls to Fav* in FFMPEGLibrary with plain calls of av* functions. It is on my TODO list, but I am in short time currently... Please give me all the pointers you have. My plan is to backport the related changes from experimental version to unstable/testing version. I gave it a try and ended up with the attached patch. What do you think of it? I tested it on my development machine and it works. Do you mind uploading it yourself? -- Eugen -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#720824: opal: FTBFS with libav9: h263-1998.cxx:320:27: error: 'CODEC_FLAG_H263P_UMV' was not declared in this scope
On 13/09/13 13:18, Sebastian Ramacher wrote: Great, thanks for testing it! I can do the upload. Would you mind if I upload it to DELAYED/0 instead of a higher delay? No problem, the sooner the better. -- Eugen -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#720824: opal: FTBFS with libav9: h263-1998.cxx:320:27: error: 'CODEC_FLAG_H263P_UMV' was not declared in this scope
On 12/09/13 15:29, Sebastian Ramacher wrote: On 2013-09-06 16:16:59, Eugen Dedu wrote: On 06/09/13 15:34, Moritz Muehlenhoff wrote: On Sun, Aug 25, 2013 at 03:22:31PM +0200, David Suárez wrote: Source: opal Version: 3.10.10~dfsg-2 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20130825 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Related to current libav9 transition (see #706798). ^ h263-1998.cxx: In member function 'virtual bool H263_RFC2190_EncoderContext::Init()': h263-1998.cxx:606:24: error: 'CODEC_FLAG_H263P_UMV' was not declared in this scope m_context-flags = ~CODEC_FLAG_H263P_UMV; ^ h263-1998.cxx:611:24: error: 'CODEC_FLAG_H263P_AIV' was not declared in this scope m_context-flags = ~CODEC_FLAG_H263P_AIV; ^ h263-1998.cxx:612:24: error: 'CODEC_FLAG_H263P_SLICE_STRUCT' was not declared in this scope m_context-flags = ~CODEC_FLAG_H263P_SLICE_STRUCT; ^ make[5]: *** [/«PKGBUILDDIR»/plugins/../lib_linux_x86_64/plugins/h263_ffmpeg/h263-1998.o] Error 1 This is fixed in the version from experimental (ptlib from experimental is also needed), which compiles fine against current libav. Thank you for this information. Note that ekiga does not yet work with opal/experimental, so opal cannot go to unstable right now. Would it be possible to backport the libav 9 fixes for now? I found some patches on the web that make it compile, but they don't fix plugins/video/common/dyna.cxx which uses dlopen/dlsym to look up the (old) libav symbols (thankfully this is properly fixed in experimental). From what I can tell it might be enough to just replace the loading and calls to Fav* in FFMPEGLibrary with plain calls of av* functions. It is on my TODO list, but I am in short time currently... Please give me all the pointers you have. My plan is to backport the related changes from experimental version to unstable/testing version. -- Eugen -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#720824: opal: FTBFS with libav9: h263-1998.cxx:320:27: error: 'CODEC_FLAG_H263P_UMV' was not declared in this scope
On 06/09/13 15:34, Moritz Muehlenhoff wrote: On Sun, Aug 25, 2013 at 03:22:31PM +0200, David Suárez wrote: Source: opal Version: 3.10.10~dfsg-2 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20130825 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Related to current libav9 transition (see #706798). ^ h263-1998.cxx: In member function 'virtual bool H263_RFC2190_EncoderContext::Init()': h263-1998.cxx:606:24: error: 'CODEC_FLAG_H263P_UMV' was not declared in this scope m_context-flags = ~CODEC_FLAG_H263P_UMV; ^ h263-1998.cxx:611:24: error: 'CODEC_FLAG_H263P_AIV' was not declared in this scope m_context-flags = ~CODEC_FLAG_H263P_AIV; ^ h263-1998.cxx:612:24: error: 'CODEC_FLAG_H263P_SLICE_STRUCT' was not declared in this scope m_context-flags = ~CODEC_FLAG_H263P_SLICE_STRUCT; ^ make[5]: *** [/«PKGBUILDDIR»/plugins/../lib_linux_x86_64/plugins/h263_ffmpeg/h263-1998.o] Error 1 This is fixed in the version from experimental (ptlib from experimental is also needed), which compiles fine against current libav. Thank you for this information. Note that ekiga does not yet work with opal/experimental, so opal cannot go to unstable right now. -- Eugen -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#718473: pcscd: 100% CPU usage
On 02/08/13 10:56, Ludovic Rousseau wrote: Le 01/08/13 07:39, Eugen Dedu a écrit : Subject: pcscd: 100% CPU usage Package: pcscd Version: 1.8.8-3 Severity: grave Dear Maintainer, Hello, Since a few weeks, pcscd has been using 100% CPU, as shown by 'top': PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 2132 root 20 0 312348 5972984 S 99.7 0.1 60:19.06 pcscd 3553 ededu 20 0 1059924 196788 47844 S 2.0 4.9 3:21.04 iceweasel I put this bug as grave because it affects the machine as a whole, feel free to change it to suit your needs. I will need more debug information. Can you: 1. run pcscd inside gdb I have a problem here: (gdb) run Starting program: /usr/sbin/pcscd warning: Could not load shared library symbols for linux-vdso.so.1. Do you need set solib-search-path or set sysroot? [Thread debugging using libthread_db enabled] Using host libthread_db library /lib/x86_64-linux-gnu/libthread_db.so.1. [Inferior 1 (process 7795) exited normally] (gdb) Note also the following output generated a few days ago: snoopy:/home/ededu# pcscd -d -f pcscdaemon.c:233:main() pcscd set to foreground with debug send to stdout 0403 configfile.l:245:DBGetReaderListDir() Parsing conf directory: /etc/reader.conf.d 0071 configfile.l:298:DBGetReaderList() Parsing conf file: /etc/reader.conf.d/libccidtwin 0137 configfile.l:257:DBGetReaderListDir() Skipping non regular file: .. 0036 configfile.l:257:DBGetReaderListDir() Skipping non regular file: . 0050 pcscdaemon.c:525:main() pcsc-lite 1.8.8 daemon ready. 4014 hotplug_libudev.c:260:get_driver() Looking for a driver for VID: 0x1D6B, PID: 0x0001, path: /dev/bus/usb/003/001 0306 hotplug_libudev.c:260:get_driver() Looking for a driver for VID: 0x1D6B, PID: 0x0001, path: /dev/bus/usb/003/001 0333 hotplug_libudev.c:260:get_driver() Looking for a driver for VID: 0x0A5C, PID: 0x4500, path: /dev/bus/usb/003/002 0303 hotplug_libudev.c:260:get_driver() Looking for a driver for VID: 0x413C, PID: 0x8157, path: /dev/bus/usb/003/003 0291 hotplug_libudev.c:260:get_driver() Looking for a driver for VID: 0x0A5C, PID: 0x4500, path: /dev/bus/usb/003/002 0382 hotplug_libudev.c:260:get_driver() Looking for a driver for VID: 0x413C, PID: 0x8158, path: /dev/bus/usb/003/004 0305 hotplug_libudev.c:260:get_driver() Looking for a driver for VID: 0x0A5C, PID: 0x4500, path: /dev/bus/usb/003/002 [...] 0012 hotplug_libudev.c:312:HPAddDevice() Adding USB device: Broadcom Corp 5880 0048 readerfactory.c:978:RFInitializeReader() Attempting startup of Broadcom Corp 5880 [Broadcom USH] (0123456789ABCD) 00 00 using /usr/lib/pcsc/drivers/ifd-ccid.bundle/Contents/Linux/libccid.so 0152 readerfactory.c:868:RFBindFunctions() Loading IFD Handler 3.0 0029 ifdhandler.c:1841:init_driver() Driver version: 1.4.11 0461 ifdhandler.c:1858:init_driver() LogLevel: 0x0003 0015 ifdhandler.c:1869:init_driver() DriverOptions: 0x 0090 ifdhandler.c:83:CreateChannelByNameOrChannel() Lun: 0, device: usb:0a5c/5800:libudev:0:/dev/bus/usb/005/002 0027 ccid_usb.c:230:OpenUSBByName() Using: /usr/lib/pcsc/drivers/ifd-ccid.bundle/Contents/Info.plist 0370 ccid_usb.c:248:OpenUSBByName() ifdManufacturerString: Ludovic Rousseau (ludovic.rouss...@free.fr) 0013 ccid_usb.c:249:OpenUSBByName() ifdProductString: Generic CCID driver 0010 ccid_usb.c:250:OpenUSBByName() Copyright: This driver is protected by terms of the GNU Lesser General Public License version 2.1, or (at your option) any later version. 3376 ccid_usb.c:501:OpenUSBByName() Found interface 0 but expecting 1 0017 ccid_usb.c:503:OpenUSBByName() Wrong interface for USB device 5/2. Checking next one. 0086 ifdhandler.c:117:CreateChannelByNameOrChannel() failed 0015 readerfactory.c:1009:RFInitializeReader() Open Port 0x20 Failed (usb:0a5c/5800:libudev:0:/dev/bus/usb/005/002) 0011 readerfactory.c:312:RFAddReader() Broadcom Corp 5880 [Broadcom USH] (0123456789ABCD) init failed. 0016 readerfactory.c:529:RFRemoveReader() UnrefReader() count was: 1 0012 readerfactory.c:1029:RFUnInitializeReader() Attempting shutdown of Broadcom Corp 5880 [Broadcom USH] (0123456789ABCD) 00 00. 0010 readerfactory.c:905:RFUnloadReader() Unloading reader driver. 0155 hotplug_libudev.c:260:get_driver() Looking for a driver for VID: 0x0A5C, PID: 0x5800, path: /dev/bus/usb/005/002 0036 hotplug_libudev.c:260:get_driver() Looking for a driver for VID: 0x0A5C, PID: 0x5800, path: /dev/bus/usb/005/002 0012 hotplug_libudev.c:312:HPAddDevice() Adding USB device: Broadcom Corp 5880 0037 readerfactory.c:978:RFInitializeReader() Attempting startup of Broadcom Corp 5880 [Contacted SmartCard] (0123456789ABCD) 00 00 using /usr/lib/pcsc/drivers/ifd-ccid.bundle/Contents/Linux/libccid.so 0124 readerfactory.c:868:RFBindFunctions() Loading IFD Handler 3.0 0027 ifdhandler.c
Bug#718473: pcscd: 100% CPU usage
On 02/08/13 11:20, Ludovic Rousseau wrote: Le 02/08/13 11:03, Eugen Dedu a écrit : On 02/08/13 10:56, Ludovic Rousseau wrote: Note also the following output generated a few days ago: I see a seg fault at exit but no infinite loop in the log. That is not the same bug. Can you reproduce the 100% CPU problem using pcscd -d -f now? Strange enough, right now the bug is not reproducible anymore. Could that be because I updated a few packages from unstable? I will re-contact when the bug occurs again. -- Eugen -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#718473: pcscd: 100% CPU usage
On 02/08/13 11:20, Ludovic Rousseau wrote: Le 02/08/13 11:03, Eugen Dedu a écrit : On 02/08/13 10:56, Ludovic Rousseau wrote: Can you: 1. run pcscd inside gdb I have a problem here: (gdb) run Starting program: /usr/sbin/pcscd warning: Could not load shared library symbols for linux-vdso.so.1. Do you need set solib-search-path or set sysroot? [Thread debugging using libthread_db enabled] Using host libthread_db library /lib/x86_64-linux-gnu/libthread_db.so.1. [Inferior 1 (process 7795) exited normally] (gdb) It looks like a known problem :-( http://sourceware.org/bugzilla/show_bug.cgi?id=13097 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=711913 Note also the following output generated a few days ago: I see a seg fault at exit but no infinite loop in the log. That is not the same bug. Can you reproduce the 100% CPU problem using pcscd -d -f now? Ok, I see. Right after a suspend/resume, pcscd goes to 100% CPU. So this is related to suspend/resume. The output generated after the suspend/resume is: 12796601 hotplug_libudev.c:587:HPEstablishUSBNotifications() Device removed 8392 hotplug_libudev.c:260:get_driver() Looking for a driver for VID: 0x1D6B, PID: 0x0001, path: /dev/bus/usb/003/001 00019374 hotplug_libudev.c:260:get_driver() Looking for a driver for VID: 0x1D6B, PID: 0x0001, path: /dev/bus/usb/003/001 [...] 0802 hotplug_libudev.c:260:get_driver() Looking for a driver for VID: 0x1D6B, PID: 0x0002, path: /dev/bus/usb/002/001 0529 hotplug_libudev.c:587:HPEstablishUSBNotifications() Device removed 4667 hotplug_libudev.c:260:get_driver() Looking for a driver for VID: 0x1D6B, PID: 0x0001, path: /dev/bus/usb/003/001 [..] 9838 hotplug_libudev.c:260:get_driver() Looking for a driver for VID: 0x1D6B, PID: 0x0002, path: /dev/bus/usb/002/001 9786 hotplug_libudev.c:587:HPEstablishUSBNotifications() Device removed 2195 hotplug_libudev.c:260:get_driver() Looking for a driver for VID: 0x1D6B, PID: 0x0001, path: /dev/bus/usb/003/001 [...] 1705 hotplug_libudev.c:260:get_driver() Looking for a driver for VID: 0x1D6B, PID: 0x0002, path: /dev/bus/usb/002/001 0460 hotplug_libudev.c:587:HPEstablishUSBNotifications() Device removed 00015193 hotplug_libudev.c:260:get_driver() Looking for a driver for VID: 0x1D6B, PID: 0x0001, path: /dev/bus/usb/003/001 [similar lines] Note that the segmentation fault appears after pressing ctrl-c. -- Eugen -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#718473: pcscd: 100% CPU usage
On 02/08/13 11:58, Ludovic Rousseau wrote: Thanks. It may be a libudev bug. Or a wrong way pcscd uses it. I do not have a laptop to test suspend/resume. So it may be a bit complex to debug. You can install systemd so that pcscd is started only when needed. So if you do not use pcscd at the suspend time you will not have the problem. I prefer to wait in this case. Note that the segmentation fault appears after pressing ctrl-c. I would need a gdb backtrace to debug that. This is really minor, I do not care. Thanks, -- Eugen -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#718473: pcscd: 100% CPU usage
Subject: pcscd: 100% CPU usage Package: pcscd Version: 1.8.8-3 Severity: grave Dear Maintainer, Since a few weeks, pcscd has been using 100% CPU, as shown by 'top': PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 2132 root 20 0 312348 5972984 S 99.7 0.1 60:19.06 pcscd 3553 ededu 20 0 1059924 196788 47844 S 2.0 4.9 3:21.04 iceweasel I put this bug as grave because it affects the machine as a whole, feel free to change it to suit your needs. Kind regards, Eugen -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.5-trunk-amd64 (SMP w/2 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages pcscd depends on: ii libc6 2.17-7 ii libccid [pcsc-ifd-handler] 1.4.11-1 ii libpcsclite11.8.8-3 ii libudev0175-7.2 ii lsb-base4.1+Debian12 pcscd recommends no packages. Versions of packages pcscd suggests: pn systemd none -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#698627: ekiga-dbg: copyright file missing after upgrade (policy 12.5)
fixed 698627 4.0.1-2 thanks On 21/01/13 11:34, Andreas Beckmann wrote: Package: ekiga-dbg Version: 3.2.7-2 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Control: fixed -1 3.2.7-5 Hi, a test with piuparts revealed that your package misses the copyright file after an upgrade from squeeze to wheezy, which is a violation of Policy 12.5: http://www.debian.org/doc/debian-policy/ch-docs.html#s-copyrightfile After the upgrade /usr/share/doc/$PACKAGE/ is just an empty directory. From the attached log (scroll to the bottom...): MISSING COPYRIGHT FILE: /usr/share/doc/ekiga-dbg/copyright # ls -lad /usr/share/doc/ekiga-dbg drwxr-xr-x 2 root root 40 Jan 20 16:07 /usr/share/doc/ekiga-dbg # ls -la /usr/share/doc/ekiga-dbg/ total 0 drwxr-xr-x 2 root root 40 Jan 20 16:07 . drwxr-xr-x 279 root root 5780 Jan 20 16:07 .. Additional info may be available here: http://wiki.debian.org/MissingCopyrightFile This was observed on an upgrade from lenny to squeeze, but seems to be fixed on subsequent updates to wheezy, although I don't see anything related in the changelog. I do not know what happened at that time. But I can say that ekiga 4.0.1-2, scheduled to enter testing, has three files for ekiga-dbg package, cf. current http://packages.debian.org/unstable/ekiga-dbg, click on list of files links at the bottom: [...] /usr/share/doc/ekiga-dbg/changelog.Debian.gz /usr/share/doc/ekiga-dbg/changelog.gz /usr/share/doc/ekiga-dbg/copyright So this issue does not exist on current unstable version of ekiga, scheduled to enter testing. I added the fixed line because it was asked by http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=709687#39. -- Eugen -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#709548: Reproducible here
I have the same problem as the reporter. seahorse, evince (at least) do not work anymore after today's upgrading. evince without argument works, but evince file.pdf yields segmentation fault. snoopy:~$ gsettings get org.gnome.desktop.interface gtk-theme 'Clearlooks-Phenix' snoopy:~$ dpkg -l libcairo2\* Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ NameVersionArchitecture Description +++-===-==-==- ii libcairo2:amd64 1.12.14-4 amd64 The Cairo 2D vector graphics library ii libcairo2-dev 1.12.14-4 amd64 Development files for the Cairo 2D graphics un libcairo2-doc none(no description available) -- Eugen -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#709548: Reproducible here
On 24/05/13 13:44, Eugen Dedu wrote: I have the same problem as the reporter. seahorse, evince (at least) do not work anymore after today's upgrading. evince without argument works, but evince file.pdf yields segmentation fault. snoopy:~$ gsettings get org.gnome.desktop.interface gtk-theme 'Clearlooks-Phenix' snoopy:~$ dpkg -l libcairo2\* Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ NameVersionArchitecture Description +++-===-==-==- ii libcairo2:amd64 1.12.14-4 amd64 The Cairo 2D vector graphics library ii libcairo2-dev 1.12.14-4 amd64 Development files for the Cairo 2D graphics un libcairo2-doc none(no description available) gdb seahorse gives: #0 0x776afbe7 in gtk_style_context_get_valist (context=0x6f8e70, state=state@entry=GTK_STATE_FLAG_DIR_LTR, args=args@entry=0x7fffc308) at /tmp/buildd/gtk+3.0-3.8.2/./gtk/gtkstylecontext.c:1443 #1 0x776f77fa in gtk_theming_engine_get (engine=0x767000, state=GTK_STATE_FLAG_DIR_LTR) at /tmp/buildd/gtk+3.0-3.8.2/./gtk/gtkthemingengine.c:436 #2 0x7fffeacdef33 in _gtk_rounded_box_apply_border_radius () from /usr/lib/x86_64-linux-gnu/gtk-3.0/3.0.0/theming-engines/libunico.so #3 0x7fffeace0c2c in ?? () from /usr/lib/x86_64-linux-gnu/gtk-3.0/3.0.0/theming-engines/libunico.so #4 0x7fffeace2548 in ?? () from /usr/lib/x86_64-linux-gnu/gtk-3.0/3.0.0/theming-engines/libunico.so #5 0x7fffeace722e in ?? () from /usr/lib/x86_64-linux-gnu/gtk-3.0/3.0.0/theming-engines/libunico.so #6 0x776b16e6 in gtk_render_background (context=0x6f8e70, cr=0x7680e0, x=0, y=15, width=15, height=352) at /tmp/buildd/gtk+3.0-3.8.2/./gtk/gtkstylecontext.c:3908 #7 0x776770d3 in gtk_range_draw (widget=0x8662d0, cr=0x7680e0) at /tmp/buildd/gtk+3.0-3.8.2/./gtk/gtkrange.c:2122 ... -- Eugen -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#709548: libgtk-3-0: most recent gtk upload breaks.... (nearly) everything (in GNOME)
On 24/05/13 14:24, Christoph Anton Mitterer wrote: On Fri, 2013-05-24 at 11:35 +0200, Emilio Pozuelo Monfort wrote: $ gsettings get org.gnome.desktop.interface gtk-theme I'm using Clearlooks-Phoenix I should also note that I use gnome-session-fallback... as well as compiz as a WM... not sure though whether this is related and could cause segfaults in those other programs... I also use gnome-fallback, but do not use compiz. -- Eugen -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#709548: libgtk-3-0: most recent gtk upload breaks.... (nearly) everything (in GNOME)
On 24/05/13 14:33, Christoph Anton Mitterer wrote: On Fri, 2013-05-24 at 14:29 +0200, Eugen Dedu wrote: I also use gnome-fallback, but do not use compiz. And you don't see any issues? Yes, as I wrote in my first e-mail (not the second). -- Eugen -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#709548: libgtk-3-0: most recent gtk upload breaks.... (nearly) everything (in GNOME)
On 24/05/13 15:04, Emilio Pozuelo Monfort wrote: On 24/05/13 14:45, Eugen Dedu wrote: On 24/05/13 14:33, Christoph Anton Mitterer wrote: On Fri, 2013-05-24 at 14:29 +0200, Eugen Dedu wrote: I also use gnome-fallback, but do not use compiz. And you don't see any issues? Yes, as I wrote in my first e-mail (not the second). Most likely gtk+ made some changes that broke the themes, which will need to be updated. If you do gsettings set org.gnome.desktop.interface gtk-theme 'Adwaita' this should work fine again. Indeed, it works. -- Eugen -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#709548: libgtk-3-0: most recent gtk upload breaks.... (nearly) everything (in GNOME)
On 24/05/13 15:47, Michael Biebl wrote: Am 24.05.2013 14:24, schrieb Christoph Anton Mitterer: On Fri, 2013-05-24 at 11:35 +0200, Emilio Pozuelo Monfort wrote: $ gsettings get org.gnome.desktop.interface gtk-theme I'm using Clearlooks-Phoenix I should also note that I use Which package is shipping this theme? What gtk engine is that theme using? clearlooks-phenix-theme package. -- Eugen -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#709548: libgtk-3-0: most recent gtk upload breaks.... (nearly) everything (in GNOME)
reassign 709548 clearlooks-phenix-theme thanks Upgrading clearlooks-phenix-theme to 3.0.15 from experimental fixes this issue. Andrew, please upload clearlooks-phenix-theme to unstable as soon as possible, to close this bug. On 24/05/13 15:47, Michael Biebl wrote: Am 24.05.2013 14:24, schrieb Christoph Anton Mitterer: On Fri, 2013-05-24 at 11:35 +0200, Emilio Pozuelo Monfort wrote: $ gsettings get org.gnome.desktop.interface gtk-theme I'm using Clearlooks-Phoenix I should also note that I use Which package is shipping this theme? What gtk engine is that theme using? -- Eugen -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#709548: Info received (Got the same with 'Faience-Ocre' gtk theme)
On 24/05/13 19:29, Loïc FAVORY wrote: The dbus problem is caused by X11 : $ dbus-launch --autolaunch=b3bcc5ac80f295a1a9cf45f65188f990 --binary-syntax --close-stderr Autolaunch error: X11 initialization failed. As I launch it from tty or ssh (I can't execute terminal in Gnome), I presume it's normal. If someone could help me to set Adwaita as GTK from tty, it would be nice. gsettings set org.gnome.desktop.interface gtk-theme 'Adwaita' -- Eugen -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#670405: ekiga: Ekiga crashes on startup
On 09/05/12 12:24, Eugen Dedu wrote: On 25/04/12 12:42, Alberto Garcia wrote: Package: ekiga Version: 3.2.7-4.2 Severity: grave Justification: renders package unusable Since a few weeks ago, Ekiga crashes on startup (shortly after showing the main window) and I cannot use it at all. It doesn't seem to happen 100% of the times, though, but the problem is very easy to reproduce. Could you please send us the -d 4 output when it crashes? Try like this: gdb -- args ekiga -d 4 21|tee log.txt and press of course: thread apply all bt when it crashes More info on http://wiki.ekiga.org/index.php/Debugging_Ekiga#How_to_get_a_stack_backtrace_from_a_crash_or_freeze Be also sure that you have ptlib, opal and ekiga's dbg packages installed. -- Eugen -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#672098: ekiga: ftbfs with GCC-4.7
On 08/05/12 20:58, Matthias Klose wrote: user debian-...@lists.debian.org usertags 672098 + ftbfs-gcc-4.7 thanks The build failure is exposed by building with gcc-4.7/g++-4.7, which is now the default gcc/g++ on x86 architectures. Some hints on fixing these issues can be found at http://gcc.gnu.org/gcc-4.7/porting_to.html This is fixed upstream http://git.gnome.org/browse/ekiga/commit/?id=f81a43f2c4. Mark, are you so kind to make a new upload including this patch, if you feel like the good solution? -- Eugen -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#670405: ekiga: Ekiga crashes on startup
On 25/04/12 12:42, Alberto Garcia wrote: Package: ekiga Version: 3.2.7-4.2 Severity: grave Justification: renders package unusable Since a few weeks ago, Ekiga crashes on startup (shortly after showing the main window) and I cannot use it at all. It doesn't seem to happen 100% of the times, though, but the problem is very easy to reproduce. Thank you for your bug and sorry for answering late. I am pretty sure that this bug is fixed with current development code. Additionally, a new stable release is very near. So I prefer to wait the new release to confirm (or not) that the bug is there. -- Eugen -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#663539: ekiga crash SIP SetUpConnection( BAD ENCODING )
forwarded 663539 https://bugzilla.gnome.org/show_bug.cgi?id=653009 thanks The problem is that it is not reproducible here. Could you answer comment 10? -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#662964: ekiga: uninstallable
On 07/03/12 17:22, Nicolas Évrard wrote:
Package: ekiga
Severity: grave
Justification: renders package unusable
Dear Maintainer,
I tried to install ekiga today. And it did not work:
% sudo aptitude update
… snip Hit and stuff …
% LANG=C sudo aptitude install ekiga
The following NEW packages will be installed:
ekiga{b} libcamel-1.2-29{a} libebook-1.2-12{a} libedataserver-1.2-15{a}
libopal3.6.8{ab}
The following packages are RECOMMENDED but will NOT be installed:
yelp
0 packages upgraded, 5 newly installed, 0 to remove and 27 not upgraded.
Need to get 13.7 MB of archives. After unpacking 31.3 MB will be used.
The following packages have unmet dependencies:
ekiga: Depends: libpt2.6.7 which is a virtual package.
Depends: evolution-data-server but it is not going to be
installed.
libopal3.6.8: Depends: libpt2.6.7 which is a virtual package.
Depends: libsrtp0 but it is not going to be installed.
The following actions will resolve these dependencies:
Keep the following packages at their current version:
1) ekiga [Not Installed]
2) libopal3.6.8 [Not Installed]
And thus the installation fail.
Hi Mark,
Has libpt2.6.7 been removed from unstable??? I fear that something very
wrong happened with this transition.
--
Eugen
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#633132: ekiga-dbg: uninstallable (libpt2.6.7-dbg disappeared)
tags 633132 + pending thanks On 08/07/11 20:49, Julien Cristau wrote: Package: ekiga-dbg Version: 3.2.7-2 Severity: serious Tags: wheezy sid apparently the latest ptlib upload decided to drop its -dbg package, but ekiga-dbg still depends on it. Please fix asap. Thank you for noticing. -- Eugen -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#633132: ekiga-dbg: uninstallable (libpt2.6.7-dbg disappeared)
On 09/07/11 07:30, Mark Purcell wrote: On Fri, 2011-07-08 at 20:13 +0100, Adam D. Barratt wrote: On Fri, 2011-07-08 at 20:49 +0200, Julien Cristau wrote: apparently the latest ptlib upload decided to drop its -dbg package, but ekiga-dbg still depends on it. Please fix asap. Specifically, it looks like you want to be depending on libpt-dbg now. Eugen, Kilian, My doing, I have dropped the version in the package name, as one will only want to install one libpt-dbg at a time. With the ekiga packaging you won't have to make a sourceful change every time ptlib changes API. This is the same as was done earlier with libopal-dbg (#586141). I have just committed the change in svn. Kilian, could you upload the new package? (What about moving ekiga from svn to git? :o)) Thanks, -- Eugen -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#633132: ekiga-dbg: uninstallable (libpt2.6.7-dbg disappeared)
On 09/07/11 21:29, Kilian Krause wrote: Hi Eugen, On Sat, Jul 09, 2011 at 01:39:17PM +0200, Eugen Dedu wrote: On 09/07/11 07:30, Mark Purcell wrote: On Fri, 2011-07-08 at 20:13 +0100, Adam D. Barratt wrote: On Fri, 2011-07-08 at 20:49 +0200, Julien Cristau wrote: apparently the latest ptlib upload decided to drop its -dbg package, but ekiga-dbg still depends on it. Please fix asap. Specifically, it looks like you want to be depending on libpt-dbg now. Eugen, Kilian, My doing, I have dropped the version in the package name, as one will only want to install one libpt-dbg at a time. With the ekiga packaging you won't have to make a sourceful change every time ptlib changes API. This is the same as was done earlier with libopal-dbg (#586141). I have just committed the change in svn. Kilian, could you upload the new package? Thanks! I've done some more finishing touches and will upload the new version into Debian later today. I'm somewhat unsure whether #630266 will bite us yet. Have you looked into this already? libnotify 0.7 works with the latest ekiga, fixed in http://git.gnome.org/browse/ekiga/commit/?id=6a964b088. I suppose backporting it is straightforward, do you have a bit of time to do it? Note that main_window.cpp was called main.cpp in ekiga 3.2.7. -- Eugen -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#572384: opal_3.6.6~dfsg-4/hppa FTBFS: undefined reference
Adam D. Barratt wrote: Hi, On Fri, 2010-03-19 at 09:51 +0100, Eugen Dedu wrote: (If you prefer, we can also wait about one week, when probably another ptlib and opal version are released upstream, and they will be packaged.) That was nearly a month ago, and there doesn't seem to be a new opal release in the archive. (There is a newer ptlib in experimental, from a couple of weeks before your e-mail). Is there any news on getting a newer opal in unstable, or getting this bug otherwise resolved? Yes, I have sent an e-mail upstream to commit a few patches, wait until I test the libraries, and make a release. Let's wait a bit... I hope that this FTFBS will disappear by recompilation. -- Eugen -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#577483: ekiga segfaults whenever I accept a call or my recipient accepts my call
Josselin Mouette wrote: Le dimanche 11 avril 2010 à 23:03 -0400, Andres Cimmarusti a écrit : Ekiga is completely useless in my computer. I can't accept a call because ekiga immediately segfaults (except call backs from 5...@ekiga.net). If I place the call, then when my recipient accepts ekiga in my computer segfaults. My recipient is running a backported ekiga on Lenny while I'm running Squeeze. Curiously this only happens to me. I installed gdb and was trying to catch the trace but if I run gdb -p ekiga's pid, this locks ekiga until I type quit in gdb. You need to type “cont” in gdb for the process to go on once you have attached to it. Or look at http://wiki.ekiga.org/index.php/Debugging_Ekiga#How_to_get_a_stack_backtrace_from_a_crash_or_freeze -- Eugen -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#572384: opal_3.6.6~dfsg-4/hppa FTBFS: undefined reference
John David Anglin wrote: John David Anglin wrote: Moreover, I have downloaded the package from http://packages.debian.org/squeeze/hppa/libpt2.6.5/download and extracted the lib. IIUC, that function is there indeed (the first is on my amd64 machine, the second is hppa extracted file): snoopy:~$ nm -D /usr/lib/libpt.so.2.6-beta7 |grep Trigger 0020d850 T _ZN12PVXMLSession7TriggerEv 0020d840 T _ZThn1096_N12PVXMLSession7TriggerEv snoopy:~$ nm -D libpt.so.2.6.5 |grep Trigger 001abb74 T _ZN12PVXMLSession7TriggerEv 001abb6c T _ZThn1152_N12PVXMLSession7TriggerEv snoopy:~$ The latter symbol is the symbol of interest. Would you run the link command with --trace-symbol=_ZThn1152_N12PVXMLSession7TriggerEv to find the name of the linked file which references the symbol. It may be the link order is bad. /home/dedu/softs/ekiga/ptlib/lib_linux_x86_64/obj/vxml.o: definition of non-virtual thunk to PVXMLSession::Trigger() We need to know which file references the symbol. Does adding -lpt at the end of the g++ link command resolve the problem? Well, I know the source file with the symbol. It's src/ptclib/vxml.cxx, see http://opalvoip.svn.sourceforge.net/viewvc/opalvoip/ptlib/tags/v2_6_5/src/ptclib/vxml.cxx?revision=23495view=markup (If you prefer, we can also wait about one week, when probably another ptlib and opal version are released upstream, and they will be packaged.) -- Eugen -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#572384: opal_3.6.6~dfsg-4/hppa FTBFS: undefined reference
John David Anglin wrote: John David Anglin wrote: John David Anglin wrote: Moreover, I have downloaded the package from http://packages.debian.org/squeeze/hppa/libpt2.6.5/download and extracted the lib. IIUC, that function is there indeed (the first is on my amd64 machine, the second is hppa extracted file): snoopy:~$ nm -D /usr/lib/libpt.so.2.6-beta7 |grep Trigger 0020d850 T _ZN12PVXMLSession7TriggerEv 0020d840 T _ZThn1096_N12PVXMLSession7TriggerEv snoopy:~$ nm -D libpt.so.2.6.5 |grep Trigger 001abb74 T _ZN12PVXMLSession7TriggerEv 001abb6c T _ZThn1152_N12PVXMLSession7TriggerEv snoopy:~$ The latter symbol is the symbol of interest. Would you run the link command with --trace-symbol=_ZThn1152_N12PVXMLSession7TriggerEv to find the name of the linked file which references the symbol. It may be the link order is bad. /home/dedu/softs/ekiga/ptlib/lib_linux_x86_64/obj/vxml.o: definition of non-virtual thunk to PVXMLSession::Trigger() We need to know which file references the symbol. Does adding -lpt at the end of the g++ link command resolve the problem? Well, I know the source file with the symbol. It's src/ptclib/vxml.cxx, see http://opalvoip.svn.sourceforge.net/viewvc/opalvoip/ptlib/tags/v2_6_5/src/ptclib/vxml.cxx?revision=23495view=markup You misunderstood my comment. It's necessary to know which files reference this symbol in order to determine whether this is just an error in the link command, or the linker itself. So you want that I add -lpt at the end of the following line: g++ obj_linux_hppa/main.o -lopal -lpt -lpthread -lrt -lsasl2 -lldap -llber -lldap_r -lssl -lcrypto -lexpat -lSDL -lodbc -lresolv -ldl -lspeexdsp -L ../../lib* -o obj_linux_hppa/simpleopal but on a hppa architecture, is that right? -- Eugen -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#572384: opal_3.6.6~dfsg-4/hppa FTBFS: undefined reference to `non-virtual thunk to PVXMLSession::Trigger()'
Adam D. Barratt wrote: Package: src:opal Version: 3.6.6~dfsg-4 Severity: serious Hi, opal_3.6.6~dfsg-4 fails to build on hppa (tried four times). From the end of the build log: /usr/bin/make PTLIBDIR=/usr OPALDIR=/build/buildd-opal_3.6.6~dfsg-4-hppa-Sy4thE/opal-3.6.6~dfsg -C samples/simple make[1]: Entering directory `/build/buildd-opal_3.6.6~dfsg-4-hppa-Sy4thE/opal-3.6.6~dfsg/samples/simple' g++ -g -O2 -g -Wall -O2 -O3 -DPTRACING=1 -D_REENTRANT -D_GNU_SOURCE=1 -fno-exceptions -I/usr/include/opal -I/usr/include/SDL -I../../include -c main.cxx -o obj_linux_hppa/main.o g++ obj_linux_hppa/main.o -lopal -lpt -lpthread -lrt -lsasl2 -lldap -llber -lldap_r -lssl -lcrypto -lexpat -lSDL -lodbc -lresolv -ldl -lspeexdsp -L ../../lib* -o obj_linux_hppa/simpleopal ../../lib_linux_hppa/libopal.so: undefined reference to `non-virtual thunk to PVXMLSession::Trigger()' ../../lib_linux_hppa/libopal.so: undefined reference to `non-virtual thunk to PVXMLSession::OnEndRecording(PString const)' ../../lib_linux_hppa/libopal.so: undefined reference to `non-virtual thunk to PVXMLSession::RecordEnd()' collect2: ld returned 1 exit status make[1]: *** [obj_linux_hppa/simpleopal] Error 1 make[1]: Leaving directory `/build/buildd-opal_3.6.6~dfsg-4-hppa-Sy4thE/opal-3.6.6~dfsg/samples/simple' make: *** [build/simpleopal] Error 2 dpkg-buildpackage: error: debian/rules build gave error exit status 2 The full log is available at https://buildd.debian.org/fetch.cgi?pkg=opalver=3.6.6%7Edfsg-4arch=hppastamp=1266684365file=log This is very strange. According to http://packages.debian.org/search?keywords=libopal3.6.6, hppa has 3.6.6~dfsg-3 but does not have the latest 3.6.6~dfsg-4. The PVXMLSession::Trigger() functions which give errors are found in ptlib, but in both cases the same ptlib package was used, cf. https://buildd.debian.org/fetch.cgi?pkg=opal;ver=3.6.6~dfsg-3;arch=hppa;stamp=1255622898 and https://buildd.debian.org/fetch.cgi?pkg=opal;ver=3.6.6~dfsg-4;arch=hppa;stamp=1268343033 Unpacking libpt2.6.5 (from .../libpt2.6.5_2.6.5-1_hppa.deb) ... and Unpacking libpt2.6.5 (from .../libpt2.6.5_2.6.5-1_hppa.deb) ... On the other hand, the changes between the two versions of opal package are really non-intrusive, I attach to this e-mail the diff between http://ftp.de.debian.org/debian/pool/main/o/opal/opal_3.6.6~dfsg-3.diff.gz and http://ftp.de.debian.org/debian/pool/main/o/opal/opal_3.6.6~dfsg-4.diff.gz So I would rather expect a failure due to the compiler (4.3-4.4), which is different: Toolchain package versions: libc6-dev_2.9-26 linux-libc-dev_2.6.30-8 g++-4.3_4.3.4-5 gcc-4.3_4.3.4-5 binutils_2.19.91.20090927-1 libstdc++6_4.4.1-6 libstdc++6-4.3-dev_4.3.4-5 and Toolchain package versions: libc6-dev_2.10.2-6 dpkg-dev_1.15.5.6 linux-libc-dev_2.6.32-9 g++-4.4_4.4.3-3 gcc-4.4_4.4.3-3 binutils_2.20.1-2 libstdc++6_4.4.3-3 libstdc++6-4.4-dev_4.4.3-3 Are you aware of such a problem on hppa architecture (the other architectures build well, and there is no #define ...HPPA... in .cpp files)? Maybe this is linked to http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=558999 ? -- Eugen 540,541c540,541 + libtheora-dev, libgsm1-dev, libspeex-dev, libspeexdsp-dev, libcelt-dev, + libcapi20-dev, libavcodec-dev --- + libtheora-dev, libgsm1-dev, libspeex-dev, libspeexdsp-dev, + libcapi20-dev 543c543 + libx264-dev --- + libx264-dev, libcelt-dev 553,554c553,554 +Conflicts: libopal-2.2-ptrace, libopal-2.2-develop, libopal-2.2.0, libopal-snapshot, libopal3.3-beta1 +Replaces: libopal-snapshot, libopal3.3-beta1 --- +Conflicts: libopal-2.2-ptrace, libopal-2.2-develop, libopal-2.2.0, libopal3.3-beta1 +Replaces: libopal3.3-beta1 599,600c599,600 +Replaces: libopal-snapshot-dbg, libopal3.3-beta1-dbg +Conflicts: libopal-snapshot-dbg, libopal3.3-beta1-dbg --- +Replaces: libopal3.3-beta1-dbg +Conflicts: libopal3.3-beta1-dbg 647c647,661 @@ -0,0 +1,301 @@ --- @@ -0,0 +1,315 @@ +opal (3.6.6~dfsg-4) unstable; urgency=low + + [ Eugen Dedu ] + * Disable celt codec, since celt is changing its API and upstream +source does not compile with the new 0.7.0 celt release (Closes: #556832) + * Remove some conflicts with non-official snapshot packages. + * Remove unuseful libavcodec-dev from Build-Depends (it does not bring +any new encoder and hurts non-official packages). + + [ Mark Purcell ] + * Build-Conflicts: libcelt-dev + + -- Mark Purcell m...@debian.org Mon, 01 Feb 2010 17:30:21 +0100 + 971c985 @@ -0,0 +1,67 @@ --- @@ -0,0 +1,70 @@ 990a1005,1007 + +# celt changes its API too fast, so upstream does not keep track with them +DEB_CONFIGURE_EXTRA_FLAGS := --disable-celt
Bug#572384: opal_3.6.6~dfsg-4/hppa FTBFS: undefined reference to `non-virtual thunk to PVXMLSession::Trigger()'
John David Anglin wrote: On Thu, 18 Mar 2010, Carlos O'Donell wrote: On Thu, Mar 18, 2010 at 7:47 AM, Adam D. Barratt a...@adam-barratt.org.uk wrote: ../../lib_linux_hppa/libopal.so: undefined reference to `non-virtual thunk to PVXMLSession::Trigger()' What does this error mean? The symbol was not found by ld. I see in the bug report log: g++ obj_linux_hppa/main.o -lopal -lpt -lpthread -lrt -lsasl2 -lldap -llber -lldap_r -lssl -lcrypto -lexpat -lSDL -lodbc -lresolv -ldl -lspeexdsp -L ../../lib* -o obj_linux_hppa/simpleopal ../../lib_linux_hppa/libopal.so: undefined reference to `non-virtual thunk to PVXMLSession::Trigger()' ../../lib_linux_hppa/libopal.so: undefined reference to `non-virtual thunk to PVXMLSession::OnEndRecording(PString const)' ../../lib_linux_hppa/libopal.so: undefined reference to `non-virtual thunk to PVXMLSession::RecordEnd()' collect2: ld returned 1 exit status make[1]: *** [obj_linux_hppa/simpleopal] Error 1 Check that that the library that is supposed to provide these symbols (libpt?) provides them. Well, the library providing these symbols, libpt, is the same (libpt2.6.5_2.6.5-1_hppa.deb) for opal-3 package, which built successfully, and opal-4 package, which fails, as written in the previous e-mail. Moreover, I have downloaded the package from http://packages.debian.org/squeeze/hppa/libpt2.6.5/download and extracted the lib. IIUC, that function is there indeed (the first is on my amd64 machine, the second is hppa extracted file): snoopy:~$ nm -D /usr/lib/libpt.so.2.6-beta7 |grep Trigger 0020d850 T _ZN12PVXMLSession7TriggerEv 0020d840 T _ZThn1096_N12PVXMLSession7TriggerEv snoopy:~$ nm -D libpt.so.2.6.5 |grep Trigger 001abb74 T _ZN12PVXMLSession7TriggerEv 001abb6c T _ZThn1152_N12PVXMLSession7TriggerEv snoopy:~$ You can see more info about link by adding -Wl,-v -Wl,-debug to the above g++ command. Regarding the tool change differences between 4.3 and 4.4, there is no difference in the handling of thunks in the hppa backend. So, any differences that you see are due to changes to the main GCC code, etc. It may be the references are not present in the 4.3 compiled code. That would have lead to failure for opal-3 package too. Cheers, -- Eugen -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#572384: opal_3.6.6~dfsg-4/hppa FTBFS: undefined reference
John David Anglin wrote: Moreover, I have downloaded the package from http://packages.debian.org/squeeze/hppa/libpt2.6.5/download and extracted the lib. IIUC, that function is there indeed (the first is on my amd64 machine, the second is hppa extracted file): snoopy:~$ nm -D /usr/lib/libpt.so.2.6-beta7 |grep Trigger 0020d850 T _ZN12PVXMLSession7TriggerEv 0020d840 T _ZThn1096_N12PVXMLSession7TriggerEv snoopy:~$ nm -D libpt.so.2.6.5 |grep Trigger 001abb74 T _ZN12PVXMLSession7TriggerEv 001abb6c T _ZThn1152_N12PVXMLSession7TriggerEv snoopy:~$ The latter symbol is the symbol of interest. Would you run the link command with --trace-symbol=_ZThn1152_N12PVXMLSession7TriggerEv to find the name of the linked file which references the symbol. It may be the link order is bad. /home/dedu/softs/ekiga/ptlib/lib_linux_x86_64/obj/vxml.o: definition of non-virtual thunk to PVXMLSession::Trigger() -- Eugen -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#572283: linux-image-2.6.33-2-amd64: Installation error
severity 572283 normal thanks Ben Hutchings wrote: On Wed, 2010-03-03 at 01:30 +0100, Eugen Dedu wrote: severity 572283 critical thanks Ben Hutchings wrote: On Wed, 2010-03-03 at 01:15 +0100, Eugen Dedu wrote: [...] Thanks for the fast help. I have just executed 'dpkg -P linux-base'. So it is now safe to reboot computer (after having issued 'lilo' too), is that right? Should be. Oh, I have just rebooted and it works!! Thanks for the help. I forgot to add critical, so that others can see it before the new uploading. I don't think this is critical: /etc/lilo.conf was not modified and your system would have been bootable even if you did not remove linux-base. Well, using correct severity then. I was scared that it will not boot because I thought that only the new kernel works after the device renaming. -- Eugen -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#571138: Ok for me too
Cannot see the crash anymore, thanks to finding out the culprit! -- Eugen -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#556832: opal: FTBFS: celtcodec.c:55: error: too many arguments to function 'celt_mode_create'
tag 556832 pending thanks We will disable celt codec, upstream does not keep track with it. Eugen Lucas Nussbaum wrote: Source: opal Version: 3.6.6~dfsg-3 Severity: serious User: debian...@lists.debian.org Usertags: qa-ftbfs-20091117 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. [...] make[4]: Entering directory `/build/user-opal_3.6.6~dfsg-3-amd64-mfDJsw/opal-3.6.6~dfsg/plugins/audio/celt' [CC] celtcodec.c celtcodec.c: In function 'init_mode': celtcodec.c:55: warning: passing argument 3 of 'celt_mode_create' makes pointer from integer without a cast celtcodec.c:55: error: too many arguments to function 'celt_mode_create' celtcodec.c: In function 'celt_create_encoder': celtcodec.c:77: error: too few arguments to function 'celt_encoder_create' celtcodec.c: In function 'celt_create_decoder': celtcodec.c:99: error: too few arguments to function 'celt_decoder_create' celtcodec.c: In function 'celt_codec_encoder': celtcodec.c:146: error: 'celt_int16_t' undeclared (first use in this function) celtcodec.c:146: error: (Each undeclared identifier is reported only once celtcodec.c:146: error: for each function it appears in.) celtcodec.c:146: error: expected expression before ')' token celtcodec.c:146: error: too few arguments to function 'celt_encode' celtcodec.c: In function 'celt_codec_decoder': celtcodec.c:176: warning: pointer targets in passing argument 2 of 'celt_decode' differ in signedness make[4]: *** [celtcodec.o] Error 1 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#546886: Decreasing severity
severity 546886 important thanks Decreasing severity, as it affects only one (or few) persons, and is not 100% reproducible. -- Eugen -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#550168: libopal3.6.6-dbg and libopal3.6.4-dbg: error when trying to install together
Simon McVittie wrote: On Fri, 09 Oct 2009 at 11:24:37 +0200, Eugen Dedu wrote: Ralf Treinen wrote: trying to overwrite '/usr/lib/debug/usr/bin/simpleopal', which is also in package libopal3.6.4-dbg 0:3.6.4~dfsg-1 So the problem is that usr/lib/debug/usr/bin/simpleopal is found in two packages: libopal3.6.6-dbg and libopal3.6.4-dbg. The solution is: - either simply remove simpleopal debug file - or create another package, simpleopal-dbg, and put the debug file inside - or make libopal3.6.6-dbg conflicts with libopal3.6.4-dbg The best quality solution is the 2nd, but is it worth to create another (debug) package for that? Having a separate -dbg package for simpleopal does seem like overkill, and I think the ftpmasters would (be correct to) reject it. Either of the other solutions seems viable. Removing debug symbols for simpleopal only impacts the ability to get good stack traces from simpleopal's own code, not from libopal; simpleopal has few users in popcon, and I suspect that if it ever crashes, it's much more likely to be caused by a bug in the library than in simpleopal itself. Having the -dbg packages conflict doesn't seem like a practical problem, because if an Opal-based application (like Ekiga) is crashing, you only need the debug symbols for the version of Opal that it links against, and don't care about the other version; so you'd never need both versions installed at the same time. If you do this you should remember to keep the appropriate Conflicts: entry to ensure a graceful upgrade from lenny to squeeze, though, even after intermediate versions have disappeared from the archive. (Disclaimer: I don't use Opal or know much about it; I'm only looking at its bug list because I was reporting an uninstallability bug, and you seemed to be asking for advice here...) Many thanks for the feedback. I will simply remove simpleopal debug file. If there is a need for it, we will resurrect it. -- Eugen -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#550168: libopal3.6.6-dbg and libopal3.6.4-dbg: error when trying to install together
tags 550168 pending thanks Simon McVittie wrote: On Fri, 09 Oct 2009 at 11:24:37 +0200, Eugen Dedu wrote: Ralf Treinen wrote: trying to overwrite '/usr/lib/debug/usr/bin/simpleopal', which is also in package libopal3.6.4-dbg 0:3.6.4~dfsg-1 So the problem is that usr/lib/debug/usr/bin/simpleopal is found in two packages: libopal3.6.6-dbg and libopal3.6.4-dbg. The solution is: - either simply remove simpleopal debug file - or create another package, simpleopal-dbg, and put the debug file inside - or make libopal3.6.6-dbg conflicts with libopal3.6.4-dbg The best quality solution is the 2nd, but is it worth to create another (debug) package for that? Having a separate -dbg package for simpleopal does seem like overkill, and I think the ftpmasters would (be correct to) reject it. Either of the other solutions seems viable. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#550168: libopal3.6.6-dbg and libopal3.6.4-dbg: error when trying to install together
Ralf Treinen wrote: Package: libopal3.6.4-dbg,libopal3.6.6-dbg Version: libopal3.6.4-dbg/3.6.4~dfsg-1 Version: libopal3.6.6-dbg/3.6.6~dfsg-1 Severity: serious User: trei...@debian.org Usertags: edos-file-overwrite Date: 2009-10-08 Architecture: amd64 Distribution: sid Hi, automatic installation tests of packages that share a file and at the same time do not conflict by their package dependency relationships has detected the following problem: WARNING: The following packages cannot be authenticated! libasound2 libcelt0 libsysfs2 tsconf libts-0.0-0 libdirectfb-1.2-0 libexpat1 libgsm1 libltdl7 libogg0 libx86-1 libsvga1 libsdl1.2debian-alsa libsdl1.2debian odbcinst odbcinst1debian1 unixodbc libpt2.6.4 libspeex1 libspeexdsp1 libtheora0 libopal3.6.4 libpt2.6.5 libopal3.6.6 libopal3.6.4-dbg libopal3.6.6-dbg Authentication warning overridden. Can not write log, openpty() failed (/dev/pts not mounted?) Selecting previously deselected package libasound2. (Reading database ... 10256 files and directories currently installed.) Unpacking libasound2 (from .../libasound2_1.0.21a-1_amd64.deb) ... Selecting previously deselected package libcelt0. Unpacking libcelt0 (from .../libcelt0_0.6.1-1_amd64.deb) ... Selecting previously deselected package libsysfs2. Unpacking libsysfs2 (from .../libsysfs2_2.1.0-6_amd64.deb) ... Selecting previously deselected package tsconf. Unpacking tsconf (from .../archives/tsconf_1.0-7_all.deb) ... Selecting previously deselected package libts-0.0-0. Unpacking libts-0.0-0 (from .../libts-0.0-0_1.0-7_amd64.deb) ... Selecting previously deselected package libdirectfb-1.2-0. Unpacking libdirectfb-1.2-0 (from .../libdirectfb-1.2-0_1.2.8-4_amd64.deb) ... Selecting previously deselected package libexpat1. Unpacking libexpat1 (from .../libexpat1_2.0.1-4_amd64.deb) ... Selecting previously deselected package libgsm1. Unpacking libgsm1 (from .../libgsm1_1.0.13-1_amd64.deb) ... Selecting previously deselected package libltdl7. Unpacking libltdl7 (from .../libltdl7_2.2.6a-4_amd64.deb) ... Selecting previously deselected package libogg0. Unpacking libogg0 (from .../libogg0_1.1.4~dfsg-1_amd64.deb) ... Selecting previously deselected package libx86-1. Unpacking libx86-1 (from .../libx86-1_1.1+ds1-6_amd64.deb) ... Selecting previously deselected package libsvga1. Unpacking libsvga1 (from .../libsvga1_1%3a1.4.3-27_amd64.deb) ... Selecting previously deselected package libsdl1.2debian-alsa. Unpacking libsdl1.2debian-alsa (from .../libsdl1.2debian-alsa_1.2.13-5_amd64.deb) ... Selecting previously deselected package libsdl1.2debian. Unpacking libsdl1.2debian (from .../libsdl1.2debian_1.2.13-5_amd64.deb) ... Selecting previously deselected package odbcinst. Unpacking odbcinst (from .../odbcinst_2.2.11-20_amd64.deb) ... Selecting previously deselected package odbcinst1debian1. Unpacking odbcinst1debian1 (from .../odbcinst1debian1_2.2.11-20_amd64.deb) ... Selecting previously deselected package unixodbc. Unpacking unixodbc (from .../unixodbc_2.2.11-20_amd64.deb) ... Selecting previously deselected package libpt2.6.4. Unpacking libpt2.6.4 (from .../libpt2.6.4_2.6.4-1+b1_amd64.deb) ... Selecting previously deselected package libspeex1. Unpacking libspeex1 (from .../libspeex1_1.2~rc1-1_amd64.deb) ... Selecting previously deselected package libspeexdsp1. Unpacking libspeexdsp1 (from .../libspeexdsp1_1.2~rc1-1_amd64.deb) ... Selecting previously deselected package libtheora0. Unpacking libtheora0 (from .../libtheora0_1.1.1-2_amd64.deb) ... Selecting previously deselected package libopal3.6.4. Unpacking libopal3.6.4 (from .../libopal3.6.4_3.6.4~dfsg-1_amd64.deb) ... Selecting previously deselected package libpt2.6.5. Unpacking libpt2.6.5 (from .../libpt2.6.5_2.6.5-1_amd64.deb) ... Selecting previously deselected package libopal3.6.6. Unpacking libopal3.6.6 (from .../libopal3.6.6_3.6.6~dfsg-1_amd64.deb) ... Selecting previously deselected package libopal3.6.4-dbg. Unpacking libopal3.6.4-dbg (from .../libopal3.6.4-dbg_3.6.4~dfsg-1_amd64.deb) ... Selecting previously deselected package libopal3.6.6-dbg. Unpacking libopal3.6.6-dbg (from .../libopal3.6.6-dbg_3.6.6~dfsg-1_amd64.deb) ... dpkg: error processing /var/cache/apt/archives/libopal3.6.6-dbg_3.6.6~dfsg-1_amd64.deb (--unpack): trying to overwrite '/usr/lib/debug/usr/bin/simpleopal', which is also in package libopal3.6.4-dbg 0:3.6.4~dfsg-1 dpkg-deb: subprocess paste killed by signal (Broken pipe) Processing triggers for man-db ... Errors were encountered while processing: /var/cache/apt/archives/libopal3.6.6-dbg_3.6.6~dfsg-1_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) This is a serious bug as it makes installation fail. Possible solutions are to have the two packages conflict, to rename the common file in one of the two packages, or to remove the file from one package and have this package depend on the other package. File
Bug#546886: ekiga: Won't receive calls nor I can't make call
Javier Barroso wrote: Package: ekiga Version: 3.2.5-1 Severity: grave Justification: renders package unusable Hi, This bug is likely #538738, but I don't known if is the same. There is said about is gnome#579938 bug, but I can't call neither. I'm attaching a gdb trace while ekiga was running with -d 4. Ekiga not crash, but it can't receive calls, and I can't make any new. I'm using SIP protocol. Hi Javier, Could you please tell us if the bug applies to 3.2.6 version currently in sid please? -- Eugen -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#538738: ekiga: Can not register (timeout) on 3.2.1~git20090515.9d0263-1
ael wrote:
Eugen Dedu wrote:
ael wrote:
Package: ekiga
Version: 3.2.1~git20090515.9d0263-1
Severity: grave
Justification: renders package unusable
Ekiga 3.2.1 cannot register with my several sip providers.
The accounts window shows: Could not register (Timeout)
Using another machine running ekiga 2.0.11 IIRC on the same network
and so
behind the same router/firewall, all is well.
Previous versions of ekiga on the machine now running 3.2.1 also
worked properly. The sip servers failing are ekiga, sipgate and
voip. All of this
seems to strongly suggest a 3.2.1 problem.
Hi,
Could you please get a debug output from ekiga v2 so that we can
compare the outputs? It is strange that for ekiga.net the two
versions act differently...
Just tried again with 3.2.1 and it worked :-(
So I am now wondering about whether previous registrations had not
expired. In at least one case, (sipgate) I can log in and see current
registrations. I explicitly deregistered the previous tests and logged
into to sipgate to confirm that they had gone. So it can't be quite
straightforward. Nevertheless, I think I have previously encoutered
similar problems when I have had to wait an hour or more between tests
before getting a successful registration, even when ekiga confirmed
successful deregistration. These long waits make testing so much harder :-(
So I guess this bug report needs to be downgraded to less than grave.
Nevertheless, ekiga does become unusable for an hour or more without any
warning. Sipgate, at least, enforce a minimum registration period of 1
hour, so just setting a small timeout in ekiga doesn't work - at least
in earlier versions.
This is a known issue: http://bugzilla.gnome.org/show_bug.cgi?id=579938
I guess you don't need the diff with a v2 debug now in the light of this
new info.
An oddity just now on registering with sipgate was no less than 3
registrations:
Device type Expire IP SIP-ID
--- -- ----
Ekiga/3.2.1 26.07.2009 22:43h 192.168.0.3:5062 1049215
Ekiga/3.2.1 26.07.2009 22:43h 86.3.134.70:16965 1049215
Ekiga/3.2.1 26.07.2009 22:43h 86.3.134.70:5062 1049215
One of these is the local net address 192.168.*.*. I saw these addresses
on the contacts line for registration on the debug output, which is
presumably how the info was passed. But I normally only see a single
entry with ekiga v2, so something seems astray?
In ekiga v3 you can contact people in your network (LAN), through avahi.
According to my limited ekiga knowledge, ekiga v3 starts registration
on all the interfaces. However, the SIP server should have retained
only one (again, I might be wrong, I do not know much of SIP).
In passing, the use of port 5062 above is deliberate and is the same for
earlier versions of ekiga. It should have no bearing on the bug.
This bug report is getting fuzzy. Sorry.
Additional data point: I can deregister and then register again with
sipgate ekiga.net without waiting at the moment. So even the 1 hour
wait is not reproducible
Summary: I am confused. Things seem to be working just now apart from
the use of 3 addresses rather than 1. {I saw q=? against each of them in
the debug output and guess these indicated an order of preference.}
So what is bug now? Is it that upon changing version, ekiga should be
started twice?
--
Eugen
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#538738: ekiga: Can not register (timeout) on 3.2.1~git20090515.9d0263-1
forwarded 538738 http://bugzilla.gnome.org/show_bug.cgi?id=579938 retitle 538738 becomes unusable after one hour or so severity 538738 normal thanks ael wrote: Eugen Dedu wrote: This is a known issue: http://bugzilla.gnome.org/show_bug.cgi?id=579938 Ok. Maybe this bug is now just a reference to that one. In ekiga v3 you can contact people in your network (LAN), through avahi. Ok. That explains the reserved 192.168.*.* local address. According to my limited ekiga knowledge, ekiga v3 starts registration on all the interfaces. However, the SIP server should have retained only one (again, I might be wrong, I do not know much of SIP). I *think* sipgate are using asterisk, maybe modified, but I am not sure. As far as I can tell, sipgate calls are working (echo tests ok), so maybe it is harmless. So what is bug now? Is it that upon changing version, ekiga should be started twice? As above, I think it is just a reference to the upstream bug. Perhaps it should stay open until the upstream bug is closed? -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#538738: ekiga: Can not register (timeout) on 3.2.1~git20090515.9d0263-1
ael wrote: Package: ekiga Version: 3.2.1~git20090515.9d0263-1 Severity: grave Justification: renders package unusable Ekiga 3.2.1 cannot register with my several sip providers. The accounts window shows: Could not register (Timeout) Using another machine running ekiga 2.0.11 IIRC on the same network and so behind the same router/firewall, all is well. Previous versions of ekiga on the machine now running 3.2.1 also worked properly. The sip servers failing are ekiga, sipgate and voip. All of this seems to strongly suggest a 3.2.1 problem. Hi, Could you please get a debug output from ekiga v2 so that we can compare the outputs? It is strange that for ekiga.net the two versions act differently... -- Eugen -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#537320: (no subject)
I suppose it's an upload error. Mark, could you see what happens please? -- Eugen -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#536021: Ekiga is not installable because it depends on libopal3.6.1
Rafael Almeida wrote: Package: ekiga Version: 3.2.1~git20090515.9d0263-1 Severity: serious Tags: sid Ekiga is depending on libopal3.6.1, but the package is not currently available on sid. However, there is a libopal3.6.3 which ekiga may work with. I am uploading ekiga with new ptlib/opal dependencies, please wait a bit... -- Eugen Dedu -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#533519: libpt2.6.3: Dummy bug not to allow propagation to testing
Package: libpt2.6.3 Severity: critical Justification: breaks unrelated software ptlib 2.6.3 has it seems a critical bug, as shown by ekiga. Until it is fixed, this bug allows ptlib 2.6.1 to still be available from testing, which in turn allows ekiga to be installable. Thanks, Eugen -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 2.6.29-2-amd64 (SMP w/2 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages libpt2.6.3 depends on: ii libc6 2.9-16 GNU C Library: Shared libraries ii libexpat1 2.0.1-4XML parsing C library - runtime li ii libgcc1 1:4.4.0-6 GCC support library ii libldap-2.4-2 2.4.15-1.1 OpenLDAP libraries ii libsasl2-22.1.23.dfsg1-1 Cyrus SASL - authentication abstra ii libsdl1.2debian 1.2.13-4+b1Simple DirectMedia Layer ii libssl0.9.8 0.9.8k-3 SSL shared libraries ii libstdc++64.4.0-6The GNU Standard C++ Library v3 ii unixodbc 2.2.11-16+b1 ODBC tools libraries libpt2.6.3 recommends no packages. Versions of packages libpt2.6.3 suggests: pn libpt2.6.3-plugins-alsa | lib none (no description available) pn libpt2.6.3-plugins-v4l2 | lib none (no description available) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#528952: reopen: Ekiga still uninstallable
tags 528952 pending thanks Alban Crequy wrote: reopen 528952 thanks According to http://www.debian.org/distrib/packages, the package libopal3.6.1 does not exist in Debian Unstable (only in Debian testing). -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#532424: ghostscript: Cannot see/print ps files anymore
Package: ghostscript Version: 8.64~dfsg-6 Severity: grave Justification: renders package unusable I execute a2ps on a text file to generate a .ps file. evince a.ps does not work, I receive errors: fatal internal error -100fatal internal error -100fatal internal error -100 lpr a.ps does not work either (pdftops error). Downgrading ghostscript and libgs8 to testing version (8.64~dfsg-1.1) fixes the problem. -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.29-2-amd64 (SMP w/2 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages ghostscript depends on: ii debconf [debc 1.5.26 Debian configuration management sy ii debianutils 3.1.3 Miscellaneous utilities specific t ii defoma0.11.10-0.2Debian Font Manager -- automatic f ii ghostscript [ 8.64~dfsg-6The GPL Ghostscript PostScript/PDF ii gs-common 8.64~dfsg-6Dummy package depending on ghostsc ii gsfonts 1:8.11+urwcyr1.0.7~pre44-4 Fonts for the Ghostscript interpre ii libc6 2.9-13 GNU C Library: Shared libraries ii libcups2 1.3.10-2 Common UNIX Printing System(tm) - ii libcupsimage2 1.3.10-2 Common UNIX Printing System(tm) - ii libgnutls26 2.6.6-1the GNU TLS library - runtime libr ii libgs88.64~dfsg-6The Ghostscript PostScript/PDF int ii libgssapi-krb 1.7dfsg~beta3-1MIT Kerberos runtime libraries - k ii libjpeg62 6b-14 The Independent JPEG Group's JPEG ii libpng12-01.2.37-1 PNG library - runtime ii libtiff4 3.8.2-11 Tag Image File Format (TIFF) libra ii zlib1g1:1.2.3.3.dfsg-13 compression library - runtime Versions of packages ghostscript recommends: pn psfontmgr none (no description available) Versions of packages ghostscript suggests: ii ghostscript-x8.64~dfsg-6 The GPL Ghostscript PostScript/PDF ii hpijs3.9.4b-1HP Linux Printing and Imaging - gs -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#532424: ghostscript: Cannot see/print ps files anymore
Indeed, it fixed the issue for me too. Thanks, Eugen Jonas Smedegaard wrote: -BEGIN PGP SIGNED MESSAGE- Hash: RIPEMD160 package ghostscript forcemerge 532392 532424 thanks On Tue, Jun 09, 2009 at 11:38:22AM +0200, Eugen Dedu wrote: I execute a2ps on a text file to generate a .ps file. evince a.ps does not work, I receive errors: fatal internal error -100fatal internal error -100fatal internal error -100 lpr a.ps does not work either (pdftops error). Downgrading ghostscript and libgs8 to testing version (8.64~dfsg-1.1) fixes the problem. Thanks for your bugreport. I made an embarrasing error in -6 release. This was fixed today in -7 expected to arrive in unstable in less than 12 hours. This bug is believed to be a dubplicate of 532392, thus force-merging. The releases newer than -1.1 contain many many improvements. If you are eager to use them (or are even hit by some of the bugs fixed by them), I have unofficial packages available by adding the following to your /etc/apt/sources.list: deb http://debian.jones.dk/ sid ghostscript ...there's also a similar one for Lenny, if you want the improved Ghostscript in an otherwise stable environment. ...and to get ahead of you: No, I do not use backports.debian.org, as that concept is too simple for my taste (no support for chains of backported build-dependencies). Kind regards, - Jonas - -- * Jonas Smedegaard - idealist og Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iEYEAREDAAYFAkouSpoACgkQn7DbMsAkQLj/2ACfcJ3tPqNlhgleQSeCBfwJxkP0 UoQAoIKWvvBTjSxLslafGZn6PzMBxNEa =pJyp -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#525781: any progress?
Kipp Cannon wrote: Hi, ekiga in testing is still segfaulting on start-up (2009-05-18). Has any progress been made on fixing this? Also, is there a revised estimate for when the fix will be available? Thanks, Everything is in place to upload ekiga v3, which fixes these issues. Only one solution exists: make lobby so that ekiga v3 be uploaded :o) -- Eugen -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#528952: Ekiga uninstallable in sid due to missing libopal-2.2
Jurij Smakov wrote: Package: ekiga Version: 2.0.12-1+nmu1+b1 Severity: serious Tags: sid Hi, The package libopal-2.2 is no longer available in sid, so ekiga is currently not installable, if libopal-2.2 has not been previously installed. If you know for a fact that it will work out of the box with the new libopal package (libopal3.6.1), and do not plan to upload a new version of ekiga in the near future, you can contact debian-release to trigger a binNMU, so it can pick up a dependency on it via shlibdeps. I just wait for someone to upload ekiga (v3, with libopal3.6.1), everything is in place. Could you do it please? -- Eugen -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#525781: [Sid] ekiga started to segfault after pwlib's update to 1.10.10-3
M. Vefa Bicakci wrote: Package: ekiga Version: 2.0.12-1+nmu1+b1 Severity: grave Justification: package is unusable Hello, After the update of pwlib (the source package for libpt-1.10.10*) to 1.10.10-3 in Sid, ekiga started to segfault right after execution. Downgrading libpt-1.10.10* packages to 1.10.10-2 (Squeeze) works around this issue. One thing I noticed was that if ekiga is not configured for a SIP account, then it doesn't segfault. However, once one completes the configuration, it promptly segfaults. Please wait a few days, until ekiga version 3.2 appears into unstable and this bug is fixed... Cheers, -- Eugen Dedu -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#525286: ptlib: Missing entries in debian/copyright.
Charles Plessy wrote: Package: ptlib Severity: serious Justification: Policy 12.5 Dear VoIP Team, In the hope of speeding up and strenghtening the processing of the NEW queue I had a look at your package. The rationale is explained in the proposal in the following wiki page: http://wiki.debian.org/CopyrightReview I noted that the `licencecheck` tool from the `devscipts` pacakges finds some source files that are licenced under a BSD-style licence and that are not documented in debian/copyright. anx159《ptlib-2.4.2》$ licensecheck -r . | grep BSD ../src/ptlib/common/tinyjpeg.h: BSD (3 clause) ../src/ptlib/common/tinyjpeg.cxx: BSD (3 clause) ../src/ptlib/common/tinyjpeg-internal.h: BSD (3 clause) ../src/ptlib/unix/udll.cxx: MPL (v1.0) MIT/X11 (BSD like) ../src/ptclib/udp.h: MIT/X11 (BSD like) ../src/ptclib/speex_echo/misc.h: BSD (3 clause) ../src/ptclib/speex_echo/mdf.c: BSD (3 clause) ../src/ptclib/speex_echo/misc.c: BSD (3 clause) ../src/ptclib/speex_echo/arch.h: BSD (3 clause) ../src/ptclib/speex_echo/speex_echo.h: BSD (3 clause) ../src/ptclib/speex_echo/speex_preprocess.h: BSD (3 clause) ../src/ptclib/speex_echo/preprocess.c: BSD (3 clause) Since the administrators of our FTP archive are also using licensecheck, it is probably safer to re-upload a package with an updated copyright file to prevent rejection of your upload. This will not make ptilb go backwards in the queue. Have a nice day, Hi, I added information about all these files. Mark, if it feels good to you, please update the changelog file accordingly and re-do an upload. -- Eugen -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#476452: Important, since FTBFS
severity 476452 critical thanks I think this is important now, because libltdl3 does not exist anymore in unstable (see http://packages.qa.debian.org/libt/libtool.html). I suppose that many other packages will FTBFS now. -- Eugen -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#519397: cheese: fails to load: segmentation fault in libgstffmpeg.so
Sebastian Dröge wrote: Which version of libavcodec52 do you have installed? I must say I have installed it from debian-multimedia: ii libavcodec52 3:20090222-0.0 library to encode decode multimedia streams - runtim I updated it to: ii libavcodec52 4:0.5.svn20090318- library to encode decode multimedia streams - runtim still gst-inspect does not work. Does gstffmpeg needs debian packages? -- Eugen -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#519397: ekiga too
The same for ekiga: cannot start!!! -- Eugen -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#520773: Wait...
Please wait about one week, we are uploading the 3.2.0 version... -- Eugen -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
