Bug#697440: [e17] e17 stable release

2013-01-05 Thread Arthur Magill
Package: e17 Version: 1.7.5 Severity: normal Dear packagers, After many, many years, the Enlightenment team have finally made a stable release: http://www.enlightenment.org/p.php?p=about/e17&l=en Is there any chance of seeing this version packaged for Debian? --- System information. --- Ar

Bug#695928: closed by Scott Howard (Re: Bug#695928: [eagle] unable to run: error loading libssl.so.0.9.8)

2012-12-15 Thread Arthur Magill
It works like a charm - thank you! And for the pointers on multiarch, that's something I've always found confusing. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#695928: [eagle] unable to run: error loading libssl.so.0.9.8

2012-12-14 Thread Arthur Magill
Package: eagle Version: 5.10.0-2 Severity: grave --- Please enter the report below this line. --- Until this week, I have been happily running Eagle. Clearly something changed with a recent upgrade. When I try to start Eagle, I see the following: $ eagle /home/magill/.eagle/bin/eagle: error

Bug#690367: hunspell: Latest version keeps gravitating to Finnish as a language.

2012-10-25 Thread Arthur Magill
Package: iceweasel Version: 10.0.9esr-1 Followup-For: Bug #690367 Dear Maintainer, Let's imagine we're here to fix this bug, rather than snark at users, for a moment. I also see this bug. This report is tagged moreinfo. So, what would you like? What can I/we do to help find a fix? I have been r

Bug#597885: [salome] Problem still present in wheezy

2012-07-26 Thread Arthur Magill
Package: salome Version: 5.1.3-12 This problem is still present. With a clean install of Salome, I see the same error when I try to launch. There is some discussion over here http://www.salome-platform.org/forum/forum_9/395274618 that points to a problem with omniORB (I have 4.1.6-2 installe

Bug#667616: brltty greedily grabs serial ports, ftdi_sio loses connection

2012-04-05 Thread Arthur Magill
Hi Samuel, Can brltty be convinced not to grab this connection? It could, but we don't want to, as it would break brltty for people who use the braille devices with chips using that ID, making the computer completely unusable for them, really not a good thing. True. But as it stands, it make

Bug#667616: brltty greedily grabs serial ports, ftdi_sio loses connection

2012-04-05 Thread Arthur Magill
Package: brltty Severity: important Dear Maintainer, I discovered this bug when connecting a Prologix GPIB-USB device to my computer. Internally, the device uses the common FTDI USB-RS232 bridge. When I connect the device, brltty takes control of the serial port, forcing the ftdi_sio driver to dr

Bug#650183: gdm3: Continuously starts X servers, uses too much CPU time and RAM

2012-03-31 Thread Arthur Magill
Package: gdm3 Version: 3.0.4-4 Followup-For: Bug #650183 Dear Maintainer, I have the same problem. After running an 'apt-get dist-upgrade', with nothing that looked too significant, I have the same bug. According to /var/log/Xorg.*.log, X reached 390 connections before giving up. I have switched

Bug#645137: mayavi2: Can't install Mayavi2 when system uses Python 2.7

2011-10-12 Thread Arthur Magill
Package: mayavi2 Severity: grave Justification: renders package unusable Dear Maintainer, I recently upgraded my system (wheezy) to Python 2.7.2+. Now I can't install Mayavi2. Can Mayavi2 be built against Python 2.7? # python -V Python 2.7.2+ # apt-get update ... # apt-get install mayavi2 Re

Bug#629591: python-nifti: datatype COMPLEX64 not supported

2011-08-29 Thread Arthur Magill
On 08/06/11 13:08, Michael Hanke wrote: Hi, On Wed, Jun 08, 2011 at 12:04:13AM +0200, Arthur Magill wrote: Package: python-nifti Version: 0.20100607.1-3 Severity: normal Datatype COMPLEX64 is not supported. However, this issue was patched upstream here: http://anonscm.debian.org/gitweb/?p

Bug#629591: python-nifti: datatype COMPLEX64 not supported

2011-06-09 Thread Arthur Magill
On 08/06/2011 13:08, Michael Hanke wrote: Thanks for the report. I'll take a look. However, I'd like to recommend that you take a look at NiBabel (python-nibabel) that is the successor of pynifti. It is much more versatile. Michael Reading COMPLEX64 nii files with python-nibabel works perfect

Bug#629591: python-nifti: datatype COMPLEX64 not supported

2011-06-08 Thread Arthur Magill
Hi Michael, Thanks for the suggestion - I wasn't aware of nibable, it looks useful. Now if only it supported Varian FDF as well... Arthur On 08/06/11 13:08, Michael Hanke wrote: Hi, On Wed, Jun 08, 2011 at 12:04:13AM +0200, Arthur Magill wrote: Package: python-nifti Ve

Bug#629591: python-nifti: datatype COMPLEX64 not supported

2011-06-07 Thread Arthur Magill
Package: python-nifti Version: 0.20100607.1-3 Severity: normal Datatype COMPLEX64 is not supported. However, this issue was patched upstream here: http://anonscm.debian.org/gitweb/?p=pkg- exppsy/pynifti.git;a=commit;h=f33a5268671a72d88f80b6a4ed9707064799af73 Some of the patch appears to have mad

Bug#616308: merge with #616312

2011-04-09 Thread Arthur Magill
Could somebody merge this the #616312? (I tried but it didn't seem to work). Also, the reported version is wrong - the problem is with cairo/1.10.2-4 (or -6), the fix is to downgrade to cairo/1.8.10-6. Thanks, Arthur -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org w

Bug#616312: Info received ([libcairo2] same here, Thinkpad W510)

2011-04-09 Thread Arthur Magill
As previous reports said, downgrading to libcairo2-1.8.10-6 (now in from stable) solves the problem - it's like an instant hardware upgrade! Steps to downgrade (I wasn't sure and had to look this up): 1) Add stable to /etc/apt/sources.list. My first two lines now read: deb http://ftp.ch.debian

Bug#616312: [libcairo2] same here, Thinkpad W510

2011-04-08 Thread Arthur Magill
Package: libcairo2 Version: 1.10.2-6 --- Please enter the report below this line. --- My system is Debian Wheezy, kernel 2.6.37-2-amd64 (pulled from unstable), GNOME, NVidia drivers 260.19.44-1 on a Thinkpad W510 laptop with Intel Quad Core Processor i7 720QM, NVidia Quadro FX 880M and 8GB RA

Bug#620733: python-vtk: Cannot "import vtk" - libmysqlclient.so.16 throws error

2011-04-03 Thread Arthur Magill
I think this is an instance of #619085. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#620733: python-vtk: Cannot "import vtk" - libmysqlclient.so.16 throws error

2011-04-03 Thread Arthur Magill
Package: python-vtk Version: 5.6.1-4 Severity: grave Justification: renders package unusable This is a pretty immediate fail - my Python session goes like this: $ python Python 2.6.6 (r266:84292, Dec 26 2010, 22:31:48) [GCC 4.4.5] on linux2 Type "help", "copyright", "credits" or "license" for mor

Bug#598171: eagle: appears in wrong menu under Gnome (Programming)

2010-09-27 Thread Arthur Magill
n 27/09/2010 17:15, Scott Howard wrote: On Mon, Sep 27, 2010 at 3:27 AM, Arthur Magill wrote: Package: eagle Version: 5.10.0-1 Severity: minor Subject says it all. This is a very minor bug. Under Gnome, Eagle appears in the Programming menu, which seems like the wrong place. It also appe

Bug#598171: eagle: appears in wrong menu under Gnome (Programming)

2010-09-27 Thread Arthur Magill
Package: eagle Version: 5.10.0-1 Severity: minor Subject says it all. This is a very minor bug. Under Gnome, Eagle appears in the Programming menu, which seems like the wrong place. It also appears, correctly, under the electronics menu. -- System Information: Debian Release: squeeze/sid APT

Bug#593617: texmaker: Commented-out %\section{} still shows in structure tree

2010-08-19 Thread Arthur Magill
Package: texmaker Version: 1.9.9-2 Severity: normal If I comment out a \section{} or \subsection{} line by adding a % character, the section still shows in the document structure tree (usually on the left of the main window). LaTeX itself builds exactly as I would expect, ignoring the commented ou

Bug#591340: Spelling: dictionary not found

2010-08-02 Thread Arthur Magill
Package: texmaker Version: 1.9.9-2 Severity: important The dictionary (in my case en_GB.dic) is not present in the default location (/usr/share/texmaker). Redirecting to /usr/share/myspell/dicts fixes the problem, but it would be nice if it worked out-of-the-box. -- System Information: Debian R

Bug#583821: wrong bug number

2010-05-30 Thread Arthur Magill
Sorry, this was meant to be in reply to bug #503915. Can someone merge this report into that one? Thx. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#547944: grub-pc: upgrade-from-grub-legacy option to install in a given, hard disk is tricky

2009-11-01 Thread Arthur Magill
ays bad, especially if you haven't fixed it before. Arthur -- Arthur Magill, PhD RF Engineer Centre d'Imagerie BioMédicale (CIBM) Laboratory for Functional and Metabolic Imaging (LIFMET) Ecole Polytechnique Fédérale de Lausanne (EPFL) Station 6, CH F1 532 (Bâtiment CH), CH-1015 Lausan