[Bug 110111] Re: snapscan e25 doesn"t work

2008-10-26 Thread Paul Fee
Hello, I've tested an Agfa Snapscan e52 scanner with kubuntu 8.10 (release candidate) and found the scanner to work without issue. sane-find-scanner found the device: found USB scanner (vendor=0x06bd [AGFA], product=0x20fd [ SNAPSCAN e52 ]) at libusb:004:002 /etc/sane.d/snapscan.conf required

[Bug 278471] Re: Screen flickers with KDE4

2008-10-24 Thread Paul Fee
Does this issue affect kubuntu 8.04 with KDE4.1.2 (installed via http://ppa.launchpad.net/kubuntu-members-kde4/ubuntu)? I've been getting flickers (as if the DVI signal had been removed and then added again). However unlike the other posts here, "xrandr -q" does not reproduce the flicker. Also t

[Bug 212388] Re: python2.5 crashed with DBusException in call_blocking()

2008-10-03 Thread Paul Fee
Same bug observed on kubuntu 8.10 amd64 beta. At the time, adept was applying updates. Guidance reported that the power had been removed, which wasn't the case and then the reported python exception occurred. -- python2.5 crashed with DBusException in call_blocking() https://bugs.launchpad.net/

[Bug 153571] Re: getaddrinfo manpage doesn't match glibc implementation when hints is NULL

2008-09-17 Thread Paul Fee
Hello Matthias, I downloaded Hardy's libc6-dev source package (2.7-10ubuntu3), same extraction steps as above (except 2.7 instead of 2.5). Also checked getaddrinfo manpage (in manpages-posix-dev, 2.16-1). In the glibc source code: ./include/netdb.h:#define AI_DEFAULT(AI_V4MAPPED | AI_ADDRCON

[Bug 110111] Re: snapscan e25 doesn"t work

2009-01-10 Thread Paul Fee
Hi Tim, True, it doesn't "just work". For starters you need to get the firmware (snape52.bin) for the scanner. There's a high chance Ubuntu won't be able to distribute this due to licensing restrictions, therefore it's difficult to make this scanner work out of the box. It would be nice if Ubun

[Bug 316739] [NEW] package koffice-data-kde4 1:1.9.98.2-0ubuntu3~intrepid2 failed to install/upgrade: trying to overwrite `/usr/share/icons/oxygen/16x16/actions/object-order-back.png', which is also i

2009-01-13 Thread Paul Fee
Public bug reported: Binary package hint: koffice2 Using Intrepid with KDE4.2 PPA. Package conflicts prevent "apt-get upgrade" from working normally. dpkg override options required to ignore the conflict due to /usr/share/icons/oxygen/16x16/actions/object-order-back.png being packaged in both k

[Bug 316739] Re: package koffice-data-kde4 1:1.9.98.2-0ubuntu3~intrepid2 failed to install/upgrade: trying to overwrite `/usr/share/icons/oxygen/16x16/actions/object-order-back.png', which is also in

2009-01-13 Thread Paul Fee
** Attachment added: "DpkgTerminalLog.gz" http://launchpadlibrarian.net/21161132/DpkgTerminalLog.gz -- package koffice-data-kde4 1:1.9.98.2-0ubuntu3~intrepid2 failed to install/upgrade: trying to overwrite `/usr/share/icons/oxygen/16x16/actions/object-order-back.png', which is also in pack

[Bug 306908] Re: [ppa] openoffice.org-kde broken - latest openoffice.org-kde causes crash

2009-01-13 Thread Paul Fee
Files can also be opened by specifying the document on the command line, e.g. $ oowriter However the lack of the File/Open dialogue is an obvious gap. The File/Save option has worse behaviour, the pointer focus is grabbed preventing most desktop interaction. Alt-tab still works to switch to a

[Bug 285158] Re: digikam crashed with SIGSEGV in std::map, std::allocator > >::find()

2009-01-13 Thread Paul Fee
** Visibility changed to: Public -- digikam crashed with SIGSEGV in std::map, std::allocator > >::find() https://bugs.launchpad.net/bugs/285158 You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to digikam-kde4 in ubuntu. -- kubuntu-bugs mailing lis

[Bug 285158] Re: digikam crashed with SIGSEGV in std::map, std::allocator > >::find()

2009-01-13 Thread Paul Fee
I installed digikam 2:0.10.0~beta8-0ubuntu1~intrepid~ppa1, it's a noticeable improvement compared to beta1. Having browsed around the various features available I was unable to make it crash. I'd consider this bug fixed. -- digikam crashed with SIGSEGV in std::map, std::allocator > >::find() ht

[Bug 285158] Re: digikam crashed with SIGSEGV in std::map, std::allocator > >::find()

2009-01-13 Thread Paul Fee
Fix available in digikam PPA. ** Changed in: digikam-kde4 (Ubuntu) Status: Incomplete => Fix Released -- digikam crashed with SIGSEGV in std::map, std::allocator > >::find() https://bugs.launchpad.net/bugs/285158 You received this bug notification because you are a member of Kubuntu Bugs,

[Bug 153571] getaddrinfo manpage doesn't match glibc implementation when hints is NULL

2007-10-17 Thread Paul Fee
Public bug reported: Binary package hint: manpages-posix-dev Writing an application that looks up IPv6 addresses, I noticed use of NULL for the hints field of getaddrinfo() as decribed in the manpage does not correspond with implementation. Extracted the source as follows: $ apt-get source libc6

[Bug 153571] Re: getaddrinfo manpage doesn't match glibc implementation when hints is NULL

2007-10-17 Thread Paul Fee
** Also affects: glibc (Ubuntu) Importance: Undecided Status: New -- getaddrinfo manpage doesn't match glibc implementation when hints is NULL https://bugs.launchpad.net/bugs/153571 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for

[Bug 153571] Re: getaddrinfo manpage doesn't match glibc implementation when hints is NULL

2009-10-09 Thread Paul Fee
ichael Kerrisk (mtk-manpages) ** Changed in: glibc (Ubuntu) Assignee: (unassigned) => Paul Fee (pfee) -- getaddrinfo manpage doesn't match glibc implementation when hints is NULL https://bugs.launchpad.net/bugs/153571 You received this bug notification because you are a member of Ubuntu

[Bug 153571] Re: getaddrinfo manpage doesn't match glibc implementation when hints is NULL

2009-10-09 Thread Paul Fee
Ulrich Drepper has responded to say that choice of defaults is deliberate. Therefore the behaviour in glibc won't be changing. Next task is to get the getaddrinfo manpage updated to state why there's a discrepancy between the glibc implementation and the POSIX standard. ** Also affects: glibc vi

[Bug 153571] Re: getaddrinfo manpage doesn't match glibc implementation when hints is NULL

2009-08-27 Thread Paul Fee
Thanks for the update. The getaddrinfo manpage on Ubuntu 9.04 has text. "Specifying hints as NULL is equivalent to setting ai_socktype and ai_protocol to 0; ai_family to AF_UNSPEC; and ai_flags to (AI_V4MAPPED | AI_ADDRCONFIG)." I notice there are two getaddrinfo manpages, section 3 and 3posix.

[Bug 153571] Re: getaddrinfo manpage doesn't match glibc implementation when hints is NULL

2009-08-27 Thread Paul Fee
Posix manpage describes the standard, not the glibc implementation. ** Changed in: manpages-posix (Ubuntu) Status: New => Invalid ** Changed in: manpages-posix (Ubuntu) Assignee: (unassigned) => Paul Fee (pfee) -- getaddrinfo manpage doesn't match glibc implementation wh

[Bug 153571] Re: getaddrinfo manpage doesn't match glibc implementation when hints is NULL

2009-08-27 Thread Paul Fee
Awaiting feedback from upstream. http://sourceware.org/bugzilla/show_bug.cgi?id=10567 ** Changed in: glibc (Ubuntu) Status: Incomplete => In Progress -- getaddrinfo manpage doesn't match glibc implementation when hints is NULL https://bugs.launchpad.net/bugs/153571 You received this bug

[Bug 2088289] Re: GCC14 -fhardened clashes with default flags

2024-11-15 Thread Paul Fee
Related to bug 2080267. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2088289 Title: GCC14 -fhardened clashes with default flags To manage notifications about this bug go to: https://bugs.launchpad

[Bug 2088289] [NEW] GCC14 -fhardened clashes with default flags

2024-11-15 Thread Paul Fee
Public bug reported: GCC 14 introduces the -fhardened flag as an umbrella for enabling a collection of security hardening flags. Ubuntu already enriches the compiler flags with -D_FORTIFY_SOURCE=3 without the user interaction. However when GCC sees both -fhardened and -D_FORTIFY_SOURCE specified

[Bug 2089259] [NEW] GCC14 C++ CTAD failure due to ambiguous overload

2024-11-21 Thread Paul Fee
Public bug reported: While using a C++ compile time fixed_string library, I encountered an issue with Ubuntu's version of GCC 14. I tried a number of combinations: * GCC-13, C++20: Pass * GCC-13, C++23: Pass * GCC-14, C++20: Pass * GCC-14, C++23: Fail Same results on both Ubuntu 24.04 (g++-14 14