Bug#737185: axe: Build-depends on deprecated Tcl 8.4
On Fri, Jan 31, 2014 at 10:39:34AM +0400, Sergei Golovan wrote: > Package: axe > Version: 6.1.2-16 > Severity: serious > Tags: patch > > Dear Maintainer, > > We are about to drop Tcl/Tk 8.4 from Debian, and your axe package build > depends on tcl8.4-dev. > > The attached patch replaces tcl8.4-dev by tcl-dev in build dependencies, > which makes it build successfully for unstable where tcl-dev pulls tcl8.5-dev, > but not in experimental where tcl-dev depends on tcl8.6-dev, so I had to > define USE_INTERP_RESULT macro also. > > If you don't mind, I could do NMU with these changes. [...] Hi, Thanks for taking the time to make this patch! Please go ahead and NMU, as I actually have not been using this package for years now. If you like, you could take over as maintainer too. T -- Two wrongs don't make a right; but three rights do make a left... -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#691078: motion keeps restarting after recent upgrade, and appears unable to find some av codec
Correction: I reinstalled the system, however, motion was not happy with the target directory permissions. Once I fixed that, it started to work properly. In short, on a freshly installed Wheezy system, motion now works fine. Next up, I usually change my distro to "testing" ... will do so with my fingers crossed in a day or two. Thanks. On Tue, Nov 6, 2012 at 11:38 AM, gregor herrmann wrote: > Control: tag -1 - moreinfo > >> >> [UPGRADE] ffmpeg:amd64 7:0.11.1-dmo5 -> 7:1.0-dmo1 >> >> [UPGRADE] gstreamer0.10-ffmpeg:amd64 0.10.13-5 -> 1:0.10.13-dmo1 >> >> [UPGRADE] libxine2-ffmpeg:amd64 1.2.2-4 -> 1:1.2.2-dmo3 >> >> [UPGRADE] libavcodec54:amd64 7:0.11.1-dmo5 -> 7:1.0-dmo1 >> >> [UPGRADE] libavdevice54:amd64 7:0.11.1-dmo5 -> 7:1.0-dmo1 >> >> [UPGRADE] libavformat54:amd64 7:0.11.1-dmo5 -> 7:1.0-dmo1 >> >> [UPGRADE] libavutil51:amd64 7:0.11.1-dmo5 -> 7:1.0-dmo1 >> > -dmoN means that you are using packages from deb-multimedia.org. >> > Do you have the same problem when you use the packages from Debian >> > proper? >> Just reinstalled my whole system. On this newly installed and updated >> wheezy system, motion doesn't even start capturing properly! > > Thanks for checking! > >> I am using the same conf file I was using till several days ago when >> it was working fine. Now when I start motion, it just spits out the >> initialization lines on the prompt and then does nothing at all. With >> the above dmo1 packages it was at least capturing some image, albeit >> at a much slower rate. > > Ok, now we at least know that there is a real problem in some Debian > package. Sorry that it won't be me who tackles it, but at least that > step is done. > > > Cheers, > gregor > > -- > .''`. Homepage: http://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06 > : :' : Debian GNU/Linux user, admin, and developer - http://www.debian.org/ > `. `' Member of VIBE!AT & SPI, fellow of the Free Software Foundation Europe >`- NP: Eric Clapton: After Midnight -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#691078: motion keeps restarting after recent upgrade, and appears unable to find some av codec
On Sun, Nov 4, 2012 at 12:54 PM, gregor herrmann wrote: > Control: tag -1 + moreinfo > > On Sat, 20 Oct 2012 23:21:37 -0400, H. S. wrote: > >> Earlier (till yesterday, part of the output included something like: >> Oct 18 09:40:28 red motion: [0] ffmpeg LIBAVCODEC_BUILD 3482368 >> LIBAVFORMAT_BUILD 3478784 >> >> That line is missing from the console output now (and also from the one >> I quoted above). I believe this is due to my recent Debian updates. Apt >> log shows the following changes since last night which may be related >> to this problem: >> [UPGRADE] ffmpeg:amd64 7:0.11.1-dmo5 -> 7:1.0-dmo1 >> [UPGRADE] gstreamer0.10-ffmpeg:amd64 0.10.13-5 -> 1:0.10.13-dmo1 >> [UPGRADE] libxine2-ffmpeg:amd64 1.2.2-4 -> 1:1.2.2-dmo3 >> [UPGRADE] libavcodec54:amd64 7:0.11.1-dmo5 -> 7:1.0-dmo1 >> [UPGRADE] libavdevice54:amd64 7:0.11.1-dmo5 -> 7:1.0-dmo1 >> [UPGRADE] libavformat54:amd64 7:0.11.1-dmo5 -> 7:1.0-dmo1 >> [UPGRADE] libavutil51:amd64 7:0.11.1-dmo5 -> 7:1.0-dmo1 > > > -dmoN means that you are using packages from deb-multimedia.org. > Do you have the same problem when you use the packages from Debian > proper? > Just reinstalled my whole system. On this newly installed and updated wheezy system, motion doesn't even start capturing properly! I am using the same conf file I was using till several days ago when it was working fine. Now when I start motion, it just spits out the initialization lines on the prompt and then does nothing at all. With the above dmo1 packages it was at least capturing some image, albeit at a much slower rate. Thanks. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#691078: motion keeps restarting after recent upgrade, and appears unable to find some av codec
Package: motion Version: 3.2.12-3.2 Severity: grave Justification: renders package unusable Dear Maintainer, *** Please consider answering these questions, where appropriate *** * What led up to the situation? Possibly my recent upgraded to my Debian system. * What exactly did you do (or not do) that was effective (or ineffective)? Tried various output vide formats (mpeg4, avi, flv). Problem remained the same. Tried switching off video exports altogether. Did not help either. * What was the outcome of this action? See above. * What outcome did you expect instead? *** End of the template - remove these lines *** Essentially, when I started motion today, it would not keep capturing images and would not export to a video either. The output on the console is the following: [0] Processing thread 0 - config file /etc/motion/motion.conf [0] Motion 3.2.12 Started [0] ffmpeg LIBAVCODEC_BUILD 3482368 LIBAVFORMAT_BUILD 3478784 [0] Thread 1 is from /etc/motion/motion.conf [1] Thread 1 started [1] cap.driver: "uvcvideo" [1] cap.card: "UVC Camera (046d:0990)" [1] cap.bus_info: "usb-:00:12.2-2" [1] cap.capabilities=0x0401 [1] - VIDEO_CAPTURE [1] - STREAMING [1] Config palette index 8 (YU12) doesn't work. [1] Supported palettes: [1] 0: MJPG (MJPEG) [1] 1: YUYV (YUV 4:2:2 (YUYV)) [1] Selected palette YUYV [0] motion-httpd/3.2.12 running, accepting connections [0] motion-httpd: waiting for data on port TCP 8080 [1] Test palette YUYV (640x480) [1] Using palette YUYV (640x480) bytesperlines 1280 sizeimage 614400 colorspace 0008 [1] found control 0x00980900, "Brightness", range 0,255 [1] "Brightness", default 128, current 128 [1] found control 0x00980901, "Contrast", range 0,255 [1] "Contrast", default 32, current 32 [1] found control 0x00980902, "Saturation", range 0,255 [1] "Saturation", default 32, current 32 [1] found control 0x00980913, "Gain", range 0,255 [1] "Gain", default 0, current 0 [1] mmap information: [1] frames=4 [1] 0 length=614400 [1] 1 length=614400 [1] 2 length=614400 [1] 3 length=614400 [1] Using V4L2 [1] Resizing pre_capture buffer to 1 items [1] Started stream webcam server in port 60080 [1] avcodec_open - could not open codec: Invalid argument [1] ffopen_open error creating (new) file [/usr/local/motionvideo/01-20121020213958.swf]: Invalid argument [1] File of type 1 saved to: /usr/local/motionvideo/01-20121020213958-01.jpg [1] Thread exiting [1] Calling vid_close() from motion_cleanup [1] Closing video device /dev/video0 [0] Motion thread 1 restart [1] Thread 1 started [1] cap.driver: "uvcvideo" [1] cap.card: "UVC Camera (046d:0990)" [1] cap.bus_info: "usb-:00:12.2-2" [1] cap.capabilities=0x0401 [1] - VIDEO_CAPTURE [1] - STREAMING [1] Config palette index 8 (YU12) doesn't work. [1] Supported palettes: [1] 0: MJPG (MJPEG) [1] 1: YUYV (YUV 4:2:2 (YUYV)) [1] Selected palette YUYV [1] Test palette YUYV (640x480) [1] Using palette YUYV (640x480) bytesperlines 1280 sizeimage 614400 colorspace 0008 [1] found control 0x00980900, "Brightness", range 0,255 [1] "Brightness", default 128, current 128 [1] found control 0x00980901, "Contrast", range 0,255 [1] "Contrast", default 32, current 32 [1] found control 0x00980902, "Saturation", range 0,255 [1] "Saturation", default 32, current 32 [1] found control 0x00980913, "Gain", range 0,255 [1] "Gain", default 0, current 0 [1] mmap information: [1] frames=4 [1] 0 length=614400 [1] 1 length=614400 [1] 2 length=614400 [1] 3 length=614400 [1] Using V4L2 [1] Resizing pre_capture buffer to 1 items [1] Started stream webcam server in port 60080 ^C^C[0] httpd - Finishing [0] httpd Closing [0] httpd thread exit ^C[1] Thread exiting [1] Calling vid_close() from motion_cleanup [1] Closing video device /dev/video0 [0] Motion terminating - Earlier (till yesterday, part of the output included something like: Oct 18 09:40:28 red motion: [0] ffmpeg LIBAVCODEC_BUILD 3482368 LIBAVFORMAT_BUILD 3478784 That line is missing from the console output now (and also from the one I quoted above). I believe this is due to my recent Debian updates. Apt log shows the following changes since last night which may be related to this problem: [UPGRADE] ffmpeg:amd64 7:0.11.1-dmo5 -> 7:1.0-dmo1 [UPGRADE] gstreamer0.10-ffmpeg:amd64 0.10.13-5 -> 1:0.10.13-dmo1 [UPGRADE] libxine2-ffmpeg:amd64 1.2.2-4 -> 1:1.2.2-dmo3 [UPGRADE] libavcodec54:amd64 7:0.11.1-dmo5 -> 7:1.0-dmo1 [UPGRADE] libavdevice54:amd64 7:0.11.1-dmo5 -> 7:1.0-dmo1 [UPGRADE] libavformat54:amd64 7:0.11.1-dmo5 -> 7:1.0-dmo1 [UPGRADE] libavutil51:amd64 7:0.11.1-dmo5 -> 7:1.0-dmo1 Thanks. -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-3-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Ver
Bug#630094: gdc looks for cc1d in wrong path
On Sat, Jun 11, 2011 at 03:29:12AM +0200, Matthias Klose wrote: > wait until -3 is built OK, thanks for the quick response! BTW, I notice that gdc ships with D version 1 support by default. Is there any plan to release a build with D version 2 support anytime soon? Thanks! --T -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#630094: gdc looks for cc1d in wrong path
Package: gdc-4.4
Version: 1.063-4.4.6-2
Severity: serious
$ gdc hash.d
gdc: error trying to exec 'cc1d': execvp: No such file or directory
$ strace gdc hash.d
execve("/usr/bin/gdc", ["gdc", "hash.d"], [/* 21 vars */]) = 0
[... snipped ...]
stat("/mnt/1/usr/bin/../lib/gcc/x86_64-linux-gnu/4.4.6/cc1d", 0x7fff976f3240) =
-1 ENOENT (No such file or directory)
stat("/mnt/1/usr/bin/../lib/gcc/cc1d", 0x7fff976f3240) = -1 ENOENT (No such
file or directory)
stat("/usr/libexec/gcc/x86_64-linux-gnu/4.4.6/cc1d", 0x7fff976f3240) = -1
ENOENT (No such file or directory)
stat("/usr/libexec/gcc/x86_64-linux-gnu/cc1d", 0x7fff976f3240) = -1 ENOENT (No
such file or directory)
stat("/usr/lib/gcc/x86_64-linux-gnu/4.4.6/cc1d", 0x7fff976f3240) = -1 ENOENT
(No such file or directory)
stat("/usr/lib/gcc/x86_64-linux-gnu/cc1d", 0x7fff976f3240) = -1 ENOENT (No such
file or directory)
stat("/mnt/1/usr/bin/../lib/gcc/x86_64-linux-gnu/4.4.6/../../../../x86_64-linux-gnu/bin/x86_64-linux-gnu/4.4.6/cc1d",
0x7fff976f3240) = -1 ENOENT (No such file or directory)
stat("/mnt/1/usr/bin/../lib/gcc/x86_64-linux-gnu/4.4.6/../../../../x86_64-linux-gnu/bin/cc1d",
0x7fff976f3240) = -1 ENOENT (No such file or directory)
vfork(gdc: error trying to exec 'cc1d': execvp: No such file or directory
) = 27254
--- SIGCHLD (Child exited) @ 0 (0) ---
wait4(27254, [{WIFEXITED(s) && WEXITSTATUS(s) == 255}], 0, NULL) = 27254
stat("/tmp/ccjeVKQM.s", {st_mode=S_IFREG|0600, st_size=0, ...}) = 0
unlink("/tmp/ccjeVKQM.s") = 0
exit_group(1) = ?
>From the strace, it seems that gdc is looking for cc1d under the '4.4.6'
subdirectory in gcc/x86_64-linux-gnu, but the gdc-4.4 package ships cc1d
in a different directory:
$ dpkg -L gdc-4.4
[... snipped ...]
/usr/lib/gcc/x86_64-linux-gnu
/usr/lib/gcc/x86_64-linux-gnu/4.4
/usr/lib/gcc/x86_64-linux-gnu/4.4/cc1d
[... snipped ...]
Manually adding a symlink 4.4.6 -> 4.4 in /usr/lib/gcc/x86_64-linux-gnu
fixes the problem.
--T
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#600481: vim removes contents of encrypted files without warning if gnupg key has expired
Package: vim Version: 2:7.2.445+hg~cb94c42c0e1a-1 Severity: critical Justification: causes serious data loss Trying to open a gnupg encrypted text file in vim when the GnuPG key is expired results in deletion of the contents of the file. Vim gives no warning that the contents will be lost, at least I did not see any. This happened repeatedly until I renewd my gnupg key. After the key renewal, editing of gnupg encrypted text files worked properly as before. Good thing I have backups of my important files, else the loss of contents would have been a serious problem. -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (700, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/4 CPU cores) Locale: LANG=en_CA.utf8, LC_CTYPE=en_CA.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages vim depends on: ii libacl1 2.2.49-4Access control list shared library ii libc62.11.2-6Embedded GNU C Library: Shared lib ii libgpm2 1.20.4-3.3 General Purpose Mouse - shared lib ii libncurses5 5.7+20100313-4 shared libraries for terminal hand ii libselinux1 2.0.96-1SELinux runtime shared libraries ii vim-common 2:7.2.445+hg~cb94c42c0e1a-1 Vi IMproved - Common files ii vim-runtime 2:7.2.445+hg~cb94c42c0e1a-1 Vi IMproved - Runtime files vim recommends no packages. Versions of packages vim suggests: pn ctags (no description available) pn vim-doc(no description available) ii vim-scripts 20091011 plugins for vim, adding bells and -- 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#567588: kino seg faults and dies when creating video segment in FX tab
Package: kino Version: 1.3.4-1 Justification: renders package unusable Severity: grave *** Please type your report below this line *** Hi. Whenever I try to create a video effect (over-writing a sequence of frames with all-black video, or creating a title sequence for some duraction of the video) and then click on "Render" button in FX tab, Kino segfaults and dies. This is the message it gives: - Kino experienced a segmentation fault. Dumping stack from the offending thread Obtained 10 stack frames. kino [0x8078d91] [0xb77e1400] kino(_ZN5Frame9EncodeRGBEPh+0x146) [0x80a7446] kino(_ZN10PageMagick11StartRenderEv+0x811) [0x80e9a11] kino(on_togglebutton_magick_start_toggled+0x34) [0x80ea174] /usr/lib/libgobject-2.0.so.0(g_cclosure_marshal_VOID__VOID+0x7c) [0xb6e1491c] /usr/lib/libgobject-2.0.so.0(g_closure_invoke+0x1b2) [0xb6e06f62] /usr/lib/libgobject-2.0.so.0 [0xb6e1b3a8] /usr/lib/libgobject-2.0.so.0(g_signal_emit_valist+0x7bd) [0xb6e1c72d] /usr/lib/libgobject-2.0.so.0(g_signal_emit+0x26) [0xb6e1cba6] Done dumping - exiting. - I am using dv files in the video. In one instance, I was using a dv file created artifically (it has no sound) and in the other instance I was using raw dv files captured from a mini-dv camcorder (this one has normal audio). What is going wrong here, any ideas? Thanks and regards. ->HS -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (990, 'testing'), (300, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.32-trunk-686 (SMP w/1 CPU core) Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages kino depends on: ii libasound2 1.0.21a-1 shared library for ALSA applicatio ii libatk1.0-01.28.0-1 The ATK accessibility toolkit ii libavc1394-0 0.5.3-1+b2control IEEE 1394 audio/video devi ii libavcodec52 5:0.5+svn20100115-0.0 library to encode decode multimedi ii libavformat52 5:0.5+svn20100115-0.0 ffmpeg file format library ii libavutil494:0.5+svn20090706-5 ffmpeg utility library ii libc6 2.10.2-2 GNU C Library: Shared libraries ii libcairo2 1.8.8-2 The Cairo 2D vector graphics libra ii libdv4 1.0.0-2 software library for DV format dig ii libfontconfig1 2.8.0-2 generic font configuration library ii libfreetype6 2.3.11-1 FreeType 2 font engine, shared lib ii libgcc11:4.4.2-9 GCC support library ii libglade2-01:2.6.4-1 library to load .glade files at ru ii libglib2.0-0 2.22.4-1 The GLib library of C routines ii libgtk2.0-02.18.3-1 The GTK+ graphical user interface ii libice62:1.0.6-1 X11 Inter-Client Exchange library ii libiec61883-0 1.2.0-0.1 an partial implementation of IEC 6 ii libpango1.0-0 1.26.2-1 Layout and rendering of internatio ii libquicktime1 3:1.1.4-0.0 library for reading and writing Qu ii libraw1394-11 2.0.5-1 library for direct access to IEEE ii libsamplerate0 0.1.7-3 Audio sample rate conversion libra ii libsm6 2:1.1.1-1 X11 Session Management library ii libstdc++6 4.4.2-9 The GNU Standard C++ Library v3 ii libswscale05:0.5+svn20100115-0.0 ffmpeg video scaling library ii libx11-6 2:1.3.3-1 X11 client-side library ii libxext6 2:1.1.1-2 X11 miscellaneous extension librar ii libxml22.7.6.dfsg-2+b1 GNOME XML library ii libxv1 2:1.0.5-1 X11 Video extension library ii zlib1g 1:1.2.3.4.dfsg-3 compression library - runtime Versions of packages kino recommends: ii curl 7.19.7-1 Get a file from an HTTP, HTTPS or ii ffmpeg 5:0.5+svn20100115-0.0 audio/video encoder, streaming ser ii gawk 1:3.1.6.dfsg-4GNU awk, a pattern scanning and pr ii mawk 1.3.3-15 a pattern scanning and text proces Versions of packages kino suggests: pn ffmpeg2theora (no description available) ii lame 3.98.2-0.5 LAME Ain't an MP3 Encoder ii mjpegtools 1:1.9.0-0.6 MJPEG video capture/editting/playb ii sox 14.3.0-1.1 Swiss army knife of sound processi ii udev 150-2 /dev/ and hotplug management daemo ii vorbis-tools 1.2.0-6 several Ogg Vorbis tools -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact
Bug#525781: Ekiga segfaults in Testing as well (after updating libpt)
I am experiencing the segfaulting of Ekiga as well since yesterday. I notice that libpt was updated yesterday. from aptitude log: Aptitude 0.4.11.11: log report Mon, May 11 2009 10:06:12 -0400 . . [UPGRADE] libpt-1.10.10 1.10.10-2 -> 1.10.10-3 [UPGRADE] libpt-1.10.10-plugins-alsa 1.10.10-2 -> 1.10.10-3 [UPGRADE] libpt-1.10.10-plugins-v4l 1.10.10-2 -> 1.10.10-3 . . Ekiga was working fine before this update. Thanks. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#522598: work around to improve the situation a bit - NOT
After I sent my previous post, I experimented a bit more. Even though the work around that I posted earlier worked in audacious, it did not work later in the day when I tested with mplayer and flash videos on some websites. Just though to clear this up and exclude any false leads. Thanks. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#522598: work around to improve the situation a bit
Hello, Just a little followup. Discovered from https://fedoraproject.org/wiki/Features/GlitchFreeAudio that following helps the situation a bit: The PulseAudio sound server has been rewritten to use timer-based audio scheduling instead of the traditional interrupt-driven approach. Timer-based scheduling may expose issues in some Alsa drivers. To turn timer-based scheduling off, replace the line load-module module-hal-detect in /etc/pulse/default.pa by load-module module-hal-detect tsched=0 After the above modification, I still get following messages in syslog: Apr 21 20:36:31 red pulseaudio[16799]: module-alsa-sink.c: ALSA woke us up to write new data to the device, but there was actually nothing to write! Most likely this is an ALSA driver bug. Please report this issue to the PulseAudio developers. Apr 21 20:37:02 red last message repeated 14 times but the sound chopping appears to have gone and sound plays smoothly now. Regards. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#522598: more info: this appears only on PCI sound card as sink
Hello, Just some additional information. I have noticed that the problem I have described occurs only when an application is sending the audio to my PCI audio card. The card is: $> lspci | grep audio 02:0c.0 Multimedia audio controller: Ensoniq 5880B [AudioPCI] (rev 02) $> aplay -L front:CARD=AudioPCI,DEV=0 Ensoniq AudioPCI, ES1371 DAC2/ADC Front speakers rear:CARD=AudioPCI,DEV=0 Ensoniq AudioPCI, ES1371 DAC1 Rear speakers surround40:CARD=AudioPCI,DEV=0 Ensoniq AudioPCI, ES1371 DAC2/ADC 4.0 Surround output to Front and Rear speakers iec958:CARD=AudioPCI,DEV=0 Ensoniq AudioPCI, ES1371 DAC2/ADC IEC958 (S/PDIF) Digital Audio Output $> aplay -l List of PLAYBACK Hardware Devices card 0: default [Microsoft LifeChat LX-3000 ], device 0: USB Audio [USB Audio] Subdevices: 1/1 Subdevice #0: subdevice #0 card 1: AudioPCI [Ensoniq AudioPCI], device 0: ES1371/1 [ES1371 DAC2/ADC] Subdevices: 1/1 Subdevice #0: subdevice #0 card 1: AudioPCI [Ensoniq AudioPCI], device 1: ES1371/2 [ES1371 DAC1] Subdevices: 1/1 Subdevice #0: subdevice #0 The problem does not occur if I send audio from an application to the other device (USB headset, LX-3000). Thanks. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#522598: pulseaudio: sound choppy after recent upgrade, syslog filling with messages
Package: pulseaudio Version: 0.9.14-2 Justification: renders package unusable Severity: grave *** Please type your report below this line *** After a recent upgrade, all audio is interrupted with short pauses, making sound choppy. It affects video as well (mplayer, gxine, youtube, etc.). Videos (avi files, youtube videos) and audio and also video telephony is not working properly anymore. I have noticed that /var/log/syslog is filling with these message: . . . Apr 4 23:16:40 red last message repeated 81 times Apr 4 23:16:47 red last message repeated 21 times Apr 4 23:16:48 red pulseaudio[6096]: module-alsa-sink.c: ALSA woke us up to write new data to the device, but there was actually nothing to write! Most likely this is an ALSA driver bug. Please report this issue to the PulseAudio developers. Apr 4 23:16:48 red pulseaudio[6096]: module-rtp-send.c: Failed to push chunk into memblockq. Apr 4 23:17:00 red last message repeated 34 times Apr 4 23:17:01 red /USR/SBIN/CRON[9643]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Apr 4 23:17:01 red pulseaudio[6096]: module-rtp-send.c: Failed to push chunk into memblockq. Apr 4 23:17:10 red last message repeated 24 times . . . Thanks. -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (990, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.26-1-686 (SMP w/1 CPU core) Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages pulseaudio depends on: ii adduser 3.110 add and remove users and groups ii consolekit0.3.0-2framework for defining and trackin ii libasound21.0.19-1 shared library for ALSA applicatio ii libasyncns0 0.3-1 Asyncronous name service query lib ii libc6 2.9-4 GNU C Library: Shared libraries ii libcap2 1:2.16-4 support for getting/setting POSIX. ii libdbus-1-3 1.2.12-1 simple interprocess messaging syst ii libgdbm3 1.8.3-4GNU dbm database routines (runtime ii libltdl3 1.5.26-4 A system independent dlopen wrappe ii liboil0.3 0.3.15-1 Library of Optimized Inner Loops ii libpolkit-dbus2 0.9-3 library for accessing PolicyKit vi ii libpolkit20.9-3 library for accessing PolicyKit ii libpulsecore9 0.9.14-2 PulseAudio sound server core ii libsamplerate00.1.7-2audio rate conversion library ii libsndfile1 1.0.18-2 Library for reading/writing audio ii libspeexdsp1 1.2~rc1-1 The Speex extended runtime library ii libwrap0 7.6.q-16 Wietse Venema's TCP wrappers libra ii lsb-base 3.2-22 Linux Standard Base 3.2 init scrip Versions of packages pulseaudio recommends: ii gstreamer0.10-pulseaudio 0.10.14-2 GStreamer plugin for PulseAudio ii libasound2-plugins1.0.19-2 ALSA library additional plugins ii padevchooser 0.9.3-2PulseAudio Device Chooser ii paprefs 0.9.6-2PulseAudio Preferences ii pulseaudio-esound-compat 0.9.14-2 PulseAudio ESD compatibility layer ii pulseaudio-module-hal 0.9.14-2 HAL device detection module for Pu ii pulseaudio-module-x11 0.9.14-2 X11 module for PulseAudio sound se Versions of packages pulseaudio suggests: ii paman0.9.4-1 PulseAudio Manager ii pavucontrol 0.9.6+svn20080426-1 PulseAudio Volume Control ii pavumeter0.9.3-1 PulseAudio Volume Meter ii pulseaudio-utils 0.9.14-2Command line tools for the PulseAu -- 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#518557: Wrong path in hal-synce-rndis
Package: synce-hal
Version: 0.13.1-1
Severity: serious
Justification: makes rndis devices unusable
Hi, there is an error in /usr/lib/hal/hal-synce-rndis: the path to /var
is prefixed with /usr, with the result that dhclient is unable to create
the pidfile and the lease file, so that HAL doesn't think the device is
connected.
% grep /var /usr/lib/hal/hal-synce-rndis
pidfile = "/usr/var/run/dhclient-synce-"+iface+".pid"
leasefile = "/usr/var/run/dhclient-synce-"+iface+".lease"
pidfile = "/usr/var/run/dhclient-synce-"+iface+".pid"
leasefile = "/usr/var/run/dhclient-synce-"+iface+".lease"
%
>From a cursory look at the source, this appears to be caused by running
configure with --prefix=/usr, since line 950 in the configure script
reads:
localstatedir='${prefix}/var'
So when $prefix is set to /usr in debian/rules, localstatedir gets set
to /usr/var/, which is non-existent.
The configure script probably has to be coaxed to do the right thing by
explicitly specifying localstatedir=/var, or something along those
lines.
T
--
The easy way is the wrong way, and the hard way is the stupid way. Pick one.
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#486017: Acknowledgement (iceowl-extension does not work in icedove)
Hi, I couldn't wait longer for this bug to be removed and tried installed the Lightning extension from Mozilla. It is on version 0.8 now. I downloaded the XPI file and added this from the Tools->Addons from within Icedove (Thunderbird) and the extension worked right out of the box. So, if anybody wants the extension, the one available from Mozilla, ver 0.8, works perfectly with Debian Lenny. ->HS On Thu, Jun 12, 2008 at 8:42 PM, Debian Bug Tracking System < [EMAIL PROTECTED]> wrote: > > Thank you for filing a new Bug report with Debian. > > This is an automatically generated reply to let you know your message > has been received. > > Your message is being forwarded to the package maintainers and other > interested parties for their attention; they will reply in due course. > > Your message has been sent to the package maintainer(s): > Alexander Sack <[EMAIL PROTECTED]> > > If you wish to submit further information on this problem, please > send it to [EMAIL PROTECTED], as before. > > Please do not send mail to [EMAIL PROTECTED] unless you wish > to report a problem with the Bug-tracking system. > > > -- > 486017: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=486017 > Debian Bug Tracking System > Contact [EMAIL PROTECTED] with problems >
Bug#486017: Acknowledgement (iceowl-extension does not work in icedove)
Hello Richar, Just checking if you were able to do something about this bug. It has been quite a while since last activity on this bug. Regards, ->HS
Bug#486017: Acknowledgement (iceowl-extension does not work in icedove)
Hi Richard, I did as you suggested in your other reply to this bug (I didn't get a copy to my gmail account thus couldn't reply to that directly), but it didn't work. I removed closed icedove, remove the rdf file, and started icedove. However, icedown then detected no extensions at all. I was expecting at least the enigmail extension, which always worked. I then closed icedove, restored the rdf file and started icedove again. It detected the enigmail extension but not the iceowl extension. :( ->HS
Bug#486017: iceowl-extension does not work in icedove
Package: iceowl-extension Version: 0.7-2 Severity: grave Justification: renders package unusable *** Please type your report below this line *** I just noticed that Debian has iceowl-extension package. I removed lightning extension that I was using (I had installed it from within thunderbird and thus was not a system wide install), and installed iceowl-extension. But after installing it and restarting Icedove, the calendar is not being shown in the mail client, it is as if the extension was never installed. What am I missing here? In case it is important, I had 0.8 version of lightning prior to removing it and installing iceowl-extension. -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.24-1-686 (SMP w/1 CPU core) Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages iceowl-extension depends on: ii icedove 2.0.0.14-1 free/unbranded thunderbird mail/ne ii libc6 2.7-10 GNU C Library: Shared libraries ii libgcc1 1:4.3.0-5 GCC support library ii libnspr4-0d 4.7.1-1NetScape Portable Runtime Library ii libstdc++64.3.0-5The GNU Standard C++ Library v3 iceowl-extension recommends no packages. -- no debconf information
Bug#474882: xscavenger: FTBFS: scav.c:561: internal compiler error: in build2_stat, at tree.c:3116
severity 474882 important thanks Hi, this appears to be a bug in gcc 4.3 (I don't think "internal compiler error" is the fault of the code; even if the code is wrong, the compiler should not encounter an internal error). I'll downgrade this to important while I investigate why it's failing in this way. --T On Mon, Apr 07, 2008 at 10:53:34PM +0200, Lucas Nussbaum wrote: > Package: xscavenger > Version: 1.4.4-5 > Severity: serious > User: [EMAIL PROTECTED] > Usertags: qa-ftbfs-20080407 qa-ftbfs > Justification: FTBFS on i386 > > Hi, > > During a rebuild of all packages in sid, your package failed to build on i386. > > This rebuild was done with gcc 4.3 instead of gcc 4.2, because gcc 4.3 is now > the default on most architectures (even if it's not the case on i386 yet). > Feel free to downgrade this bug to 'important' if your package is only built > on i386, and this bug is specific to gcc 4.3 (i.e the package builds fine with > gcc 4.2). > > Relevant part: > > make[1]: Entering directory `/build/user/xscavenger-1.4.4/src' > > gcc -m32 -g -O2 -fno-strict-aliasing -O2 -g -pipe -Wall -Wno-pointer-sign > > -Dlinux -D__i386__ -D_POSIX_C_SOURCE=199309L > > -D_POSIX_SOURCE -D_XOPEN_SOURCE > > -D_BSD_SOURCE -D_SVID_SOURCE > > -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 > > -DFUNCPROTO=15 -DNARROWPROTO > > -DLIBNAME=\"/usr/lib/games/xscavenger\" -c -o anim.o anim.c > > anim.c: In function 'animprocess': > > anim.c:613: warning: 'by' may be used uninitialized in this function > > anim.c:613: warning: 'bx' may be used uninitialized in this function > > gcc -m32 -g -O2 -fno-strict-aliasing -O2 -g -pipe -Wall -Wno-pointer-sign > > -Dlinux -D__i386__ -D_POSIX_C_SOURCE=199309L > > -D_POSIX_SOURCE -D_XOPEN_SOURCE > > -D_BSD_SOURCE -D_SVID_SOURCE > > -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 > > -DFUNCPROTO=15 -DNARROWPROTO > > -DLIBNAME=\"/usr/lib/games/xscavenger\" -c -o edit.o edit.c > > gcc -m32 -g -O2 -fno-strict-aliasing -O2 -g -pipe -Wall -Wno-pointer-sign > > -Dlinux -D__i386__ -D_POSIX_C_SOURCE=199309L > > -D_POSIX_SOURCE -D_XOPEN_SOURCE > > -D_BSD_SOURCE -D_SVID_SOURCE > > -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 > > -DFUNCPROTO=15 -DNARROWPROTO > > -DLIBNAME=\"/usr/lib/games/xscavenger\" -c -o scav.o scav.c > > scav.c: In function 'paintlevel': > > scav.c:561: internal compiler error: in build2_stat, at tree.c:3116 > > Please submit a full bug report, > > with preprocessed source if appropriate. > > See for instructions. > > make[1]: *** [scav.o] Error 1 > > The full build log is available from: >http://people.debian.org/~lucas/logs/2008/04/07 > > A list of current common problems and possible solutions is available at > http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! > > About the archive rebuild: The rebuild was done on about 50 AMD64 nodes > of the Grid'5000 platform, using a clean chroot containing a sid i386 > environment. Internet was not accessible from the build systems. > > -- > | Lucas Nussbaum > | [EMAIL PROTECTED] http://www.lucas-nussbaum.net/ | > | jabber: [EMAIL PROTECTED] GPG: 1024D/023B3F4F | > > -- Never wrestle a pig. You both get covered in mud, and the pig likes it. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#460768: patch
On Tue, Jan 29, 2008 at 10:40:58PM +0800, Ying-Chun Liu (PaulLiu) wrote: > tags 460768 + patch > thanks > > Dear all, > > I made a patch for transition to gnome2. It seems not hard. :) > > The rest is to adjust the Build-Depends field in debian/control. For > example, depends on libgnomeui-dev instead of libgnome-dev. [...] Thanks for the help! I've uploaded the fixed package to the queue. --T signature.asc Description: Digital signature
Bug#460768: Upload pending
tags 460768 + pending thanks T -- Guns don't kill people. Bullets do. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#456631: Bug is X server problem
Hi, just a note that this bug is almost certainly an X server bug: downgrading to ratpoison 1.4.0.dfsg-7 does not fix the problem, I still get the same symptoms. T -- English is useful because it is a mess. Since English is a mess, it maps well onto the problem space, which is also a mess, which we call reality. Similarly, Perl was designed to be a mess, though in the nicests of all possible ways. -- Larry Wall -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#456631: Ratpoison command-line locks up X server
Package: ratpoison Version: 1.4.2-1 Severity: serious Hi, I'm not sure if this is a ratpoison bug or an X server bug (or both?). After upgrading to the latest version of the X server, the ratpoison command-line (C-t :) will lock up the X server after you hit Enter. The only way to regain control is to 'Ctrl-Alt-SysRq r' to force kernel control of keyboard/mouse, then 'Ctrl-Alt-SysRq k' to kill the X server forcefully. The other C-t commands work properly, though, which is strange. Trying to quit ratpoison by using C-t :quit will hang the X server, but manually killing ratpoison (kill $pid) will gracefully exit the X server. Relevant packages: ii xserver-xorg-core 2:1.4.1~git20071212-1 Xorg X server - core server ii xserver-xorg-video-ati 1:6.6.193-3X.Org X server -- ATI display driver T -- Heads I win, tails you lose. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#454638: libc6 unusable on kernel 2.6.9 due to opendir/O_CLOEXEC problems
Package: libc6 Version: 2.7-3 Severity: grave Justification: renders system (mostly) unusable Hi, I upgraded libc6 to 2.7-3 using apt-get on a system running kernel 2.6.9 with SMP (unfortunately I don't have the option of changing this kernel, it's provided by my colo provider), and dpkg crashed with "Unknown error 530". Subsequently, everything that scanned directories crashed with the same error (ls, dpkg, etc.). Eventually, I found out that the filesystem was still intact; I could cd into directories, and ls works on the current directory. My current shell (presumably still linked to the old shared lib) can still scan directories (`echo /path/name/*` works). Pathnames that referenced individual files also worked; but any new process besides my current shell that used opendir() crashed with the same error. Then I found this: http://www.nabble.com/-Bug-libc-5227--New:-opendir-and-O_CLOEXEC-problems-with-Linux-2.6.9-5.ELsmp-kernel-t4705183.html It seems that glibc 2.7 has problems with opendir() and O_CLOEXEC on kernel 2.6.9 with SMP enabled. Downgrading to glibc2.6 fixed all my problems. I presume libc6 2.7 works on the most recent kernels, but it's very not-nice for people running 2.6.9 with smp to upgrade libc6 and find their system almost completely unusable. T -- "How are you doing?" "Doing what?" -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#452718: ttf-opensymbol non-installable
Package: ttf-opensymbol Version: 1:2.3.0.dfsg-3 Severity: serious Hi, upgrading to ttf-opensymbol with apt-get gives me: Setting up ttf-opensymbol (1:2.3.0.dfsg-3) ... Updating fontconfig cache... /var/lib/dpkg/info/ttf-opensymbol.postinst: line 98: 4969 Segmentation fault fc-cache -fs dpkg: error processing ttf-opensymbol (--configure): subprocess post-installation script returned error exit status 139 Errors were encountered while processing: ttf-opensymbol This is with fontconfig 2.5.0-2. Looks like a fontconfig bug, but filing against ttf-opensymbol since it seems to be the only font causing problems. Feel free to reassign if necessary, thanks. T -- People tell me I'm stubborn, but I refuse to accept it! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#446775: k3b crashes when attempting to add a flac file to make an audio CD
Package: k3b Version: 1.0.3-2 Severity: grave Justification: renders package unusable *** Please type your report below this line *** If I try to make a new Audio CD project and try to add a flac file to the project, k3b crashes. This has happened on two different systems running Debian Testing and different kernels. Another user on debian user mailing list has confirmed this. This started happening only after an update of the systems within the last week or so. Here are the last few lines I get if I run k3b from a terminal: -- kdecore (KAction): WARNING: KActionCollection::operator+=(): function is severely deprecated. KCrash: Application 'k3b' crashing... -- Here is the backtrace I get from the k3b crash tool windows: -- (no debugging symbols found) Using host libthread_db library "/lib/i686/cmov/libthread_db.so.1". (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 0xb65b26c0 (LWP 10820)] [New Thread 0xb4011b90 (LWP 10894)] [New Thread 0xb56c9b90 (LWP 10856)] [New Thread 0xb5ecab90 (LWP 10855)] (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) 0xb7fdc7f2 in ?? () from /lib/ld-linux.so.2 #0 0xb7fdc7f2 in ?? () from /lib/ld-linux.so.2 #1 0xb66a4567 in poll () from /lib/i686/cmov/libc.so.6 #2 0xb6932f53 in ?? () from /usr/lib/libX11.so.6 #3 0x08263fb0 in ?? () #4 0x0001 in ?? () #5 0x in ?? () #6 0xb69dcb24 in ?? () from /usr/lib/libX11.so.6 #7 0x08263a70 in ?? () #8 0xb69dcb24 in ?? () from /usr/lib/libX11.so.6 #9 0x08263a70 in ?? () #10 0x091f in ?? () #11 0x0020 in ?? () #12 0x in ?? () - I have been making audio CDs from home recordings for quite some while now. This is the first time this has happened. Please let me know if you need any additional information. thanks, ->HS -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.21-2-686 (SMP w/1 CPU core) Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages k3b depends on: ii cdparanoia 3.10+debian~pre0-5 audio extraction tool for sampling ii cdrdao 1:1.2.2-7 records CDs in Disk-At-Once (DAO) i
Bug#443647: xkb-data missing some characters in gurmukhi (gur) keymap
Package: xkb-data
Version: 1.0~cvs.20070721-1
Severity: grave
Justification: renders package unusable
*** Please type your report below this line ***
Hello,
xkb-data 'gur' keymap is missing two characters (there may be more, however,
that I may have not come across yet!) from Gurmukhi making it impossible to
correctly type an article.
The two characters are:
1) Unicode character: 0A72 (addak), which is ੱ
2) Unicode character: 0A5C (Rharha), which is ੜ
To get (2) above by typing SHIFT+A30 (I am not sure where it should go
according to the standard based on which others are placed on a keyboard,
but I am guessing it can be put as SHIFT+A30), line no. 50 in
/etc/X11/xkb/symbols/gur may be changed to the following:
key { [], [ 0x1000A30, 0x1000A5C
] };
The first one is a bit tricky. It appears that it should be mapped to the
key "X" on the US querty keyboard. Here is one way
to get this, by modifying line 58 of xkb-data package to the following (this
key already has two chars. assigned to it, so
addak will have to typed using the modifier key):
key { [], [ 0x1000A02, 0x1000A70, 0x1000A71
] };
The above two are just suggestions on how get around the problem. The
maintainer, of course, is free to research if a better method, or a correct
one, exists to solve this problem.
Thanks,
->HS
-- System Information:
Debian Release: lenny/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.6.21-2-686 (SMP w/1 CPU core)
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
-- no debconf information
Bug#418109: Python upgrade bug
Package: python2.4-minimal
Version: 2.4.4-3
Severity: serious
Justification: breaks upgrade
Hi, the latest python upgrade fails:
Setting up python2.4-minimal (2.4.4-3) ...
Linking and byte-compiling packages for runtime python2.4...
Traceback (most recent call last):
File "/usr/bin/pycentral", line 1373, in ?
main()
File "/usr/bin/pycentral", line 1363, in main
if action.check_args(global_options):
File "/usr/bin/pycentral", line 971, in check_args
for rt in get_installed_runtimes():
File "/usr/bin/pycentral", line 196, in get_installed_runtimes
supported = pyversions.supported_versions()
File "/usr/share/pycentral-data/pyversions.py", line 98, in supported_versions
value = read_default('supported-versions')
File "/usr/share/pycentral-data/pyversions.py", line 22, in read_default
value = config.get('DEFAULT', name)
UnboundLocalError: local variable 'config' referenced before assignment
dpkg: error processing python2.4-minimal (--configure):
subprocess post-installation script returned error exit status 1
Errors were encountered while processing:
python2.4-minimal
Installed packages:
ii python-minimal 2.4.4-2A minimal subset of the Python
language (default version)
iU python2.42.4.4-3An interactive high-level
object-oriented language (version 2.4)
iF python2.4-minimal2.4.4-3A minimal subset of the Python
language (version 2.4)
ii python 2.4.4-2An interactive high-level
object-oriented language (default version)
ii python-central 0.5.13 register and build utility for
Python packages
T
--
There is no gravity. The earth sucks.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#396631: Same problem with latest version of apache2/libapr1
On Tue, Dec 19, 2006 at 09:55:39AM +0100, Andreas Barth wrote: [...] > I uploaded packages for this architecture now on > http://people.debian.org/~aba/apr/ - the changes-file is signed by me > so that you know it was really me. [...] I just tested it. It works flawlessly! I'm not sure why building on the server itself doesn't work... I'd like to track that down, although I don't think it's related to this bug. My locally-built package seems to be unable to correctly process apache's Include directives, so maybe this is related to filesystem access. T -- Life is unfair. Ask too much from it, and it may decide you don't deserve what you have now either. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#396631: Same problem with latest version of apache2/libapr1
On Tue, Dec 19, 2006 at 12:46:52AM +0100, Andreas Barth wrote: > * H. S. Teoh ([EMAIL PROTECTED]) [061218 19:39]: > > On Fri, Dec 15, 2006 at 05:53:38PM -0600, Peter Samuelson wrote: > > > > > > [H. S. Teoh] > > > > Hi, the old patch (currently in unstable) already works---my test was > > > > invalid because I upgraded apache2 but forgot to upgrade libapr1. Do > > > > you still want me to test the new patch? > > > > > > Ahh - great to hear! Yes, If it's convenient for you, please do test > > > my new patch. It's a little bit cleaner than the old one, and it does > > > fix one bug, unless I'm completely misreading it. > > [... > > > > Hi, I just tried to build libapr1 with the new patch, but I'm unable to > > test it because I'm getting unrelated errors (apache2 doesn't load its > > configuration correctly and doesn't start... I don't think this is > > related to the patch, probably a build environment problem). > > Which architecture do you use? [...] i686. But it runs on a modified kernel that my colo provider uses for running virtual servers. I'm not sure if this makes a difference in the build. All I did was `apt-get source libapr1`, copy the new patch into debian/patches, and run `dpkg-buildpackage -r fakeroot`. T -- IBM = I Blame Microsoft -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#396631: Same problem with latest version of apache2/libapr1
On Fri, Dec 15, 2006 at 05:53:38PM -0600, Peter Samuelson wrote: > > [H. S. Teoh] > > Hi, the old patch (currently in unstable) already works---my test was > > invalid because I upgraded apache2 but forgot to upgrade libapr1. Do > > you still want me to test the new patch? > > Ahh - great to hear! Yes, If it's convenient for you, please do test > my new patch. It's a little bit cleaner than the old one, and it does > fix one bug, unless I'm completely misreading it. [... Hi, I just tried to build libapr1 with the new patch, but I'm unable to test it because I'm getting unrelated errors (apache2 doesn't load its configuration correctly and doesn't start... I don't think this is related to the patch, probably a build environment problem). T -- If a person can't communicate, the very least he could do is to shut up. -- Tom Lehrer, on people who bemoan their communication woes with their loved ones. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#396631: Same problem with latest version of apache2/libapr1
On Thu, Dec 14, 2006 at 10:42:21PM -0600, Peter Samuelson wrote: > > [H. S. Teoh] > > Hi, the fix for #396631 to libapr1 does not work. Apache2 still > > serves 0 bytes when running on a 2.4 kernel (on my virtual colo > > host). Please look into this problem. Thanks! > > My old patch is slightly buggy - can you try rebuilding apr 1.2.7-8.1 > with this updated version of debian/patches/015_sendfile_lfs.dpatch? [...] Hi, the old patch (currently in unstable) already works---my test was invalid because I upgraded apache2 but forgot to upgrade libapr1. Do you still want me to test the new patch? T -- Klein bottle for rent ... inquire within. -- Stephen Mulraney -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#396631: Same problem with latest version of apache2/libapr1
reopen 396631 thanks Hi, the fix for #396631 to libapr1 does not work. Apache2 still serves 0 bytes when running on a 2.4 kernel (on my virtual colo host). Please look into this problem. Thanks! T -- Not all rumours are as misleading as this one. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#402625: Broken upgrade path
Package: asymptote-doc Version: 1.18-2 Severity: serious Justification: Breaks upgrade path, should be fixed before release I notice that asymptote has been split into two packages, asymptote and asymptote-doc. Unfortunately, something went wrong with the split, causing following problem when upgrading from asymptote (1.14-1): Unpacking asymptote-doc (from .../asymptote-doc_1.18-2_all.deb) ... dpkg: error processing /var/cache/apt/archives/asymptote-doc_1.18-2_all.deb (--unpack): trying to overwrite `/usr/share/doc-base/asymptote', which is also in package asymptote Preparing to replace asymptote 1.14-1 (using .../asymptote_1.18-2_i386.deb) ... Unpacking replacement asymptote ... Errors were encountered while processing: /var/cache/apt/archives/asymptote-doc_1.18-2_all.deb E: Sub-process /usr/bin/dpkg returned an error code (1) T -- Windows: the ultimate triumph of marketing over technology. -- Adrian von Bidder -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#401017: Bug is not HTTP-dependent
Hi, I'm also seeing this bug on my virtual colocated server. It doesn't seem to be specific to HTTP; I use FTP-only apt sources and I'm still seeing the bug: Hit ftp://ftp.us.debian.org unstable Release.gpg Hit ftp://ftp.us.debian.org unstable Release Hit ftp://ftp.us.debian.org unstable/main Packages/DiffIndex Hit ftp://ftp.us.debian.org unstable/contrib Packages/DiffIndex Hit ftp://ftp.us.debian.org unstable/main Sources/DiffIndex Hit ftp://ftp.us.debian.org unstable/contrib Sources/DiffIndex 99% [Sources bzip2 0] (...hangs forever...) Hope this helps to track down the problem. T -- The easy way is the wrong way, and the hard way is the stupid way. Pick one. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#392189: Apache2 cannot spawn child processes: segfault
Package: apache2-common Version: 2.2.3-2 Severity: grave Justification: renders package unusable I just upgraded to 2.2.3-2, and apache2 no longer starts due to various configuration issues. As I have a rather complicated apache2 setup, I decided to back up /etc/apache2 and re-install a clean new configuration so that I can start with something that works. Unfortunately, the default installation (without any customization) has a broken configuration: apache2: Syntax error on line 185 of /etc/apache2/apache2.conf: Syntax error on line 1 of /etc/apache2/mods-enabled/php5.load: API module structure `php5_module' in file /usr/lib/apache2/modules/libphp5.so is garbled - perhaps this is not an Apache module DSO? To fix this, I temporarily disabled php5 with `a2dismod php5`. After this apache2 starts, but then all child processes segfault. Snippet of /var/log/apache2/error.log: [Tue Oct 10 09:34:34 2006] [notice] child pid 20918 exit signal Segmentation fault (11) [Tue Oct 10 09:34:34 2006] [notice] child pid 20917 exit signal Segmentation fault (11) [Tue Oct 10 09:34:34 2006] [notice] child pid 20916 exit signal Segmentation fault (11) [Tue Oct 10 09:34:34 2006] [notice] child pid 20914 exit signal Segmentation fault (11) [Tue Oct 10 09:34:34 2006] [notice] child pid 20913 exit signal Segmentation fault (11) [Tue Oct 10 09:34:34 2006] [notice] child pid 20912 exit signal Segmentation fault (11) [Tue Oct 10 09:34:34 2006] [notice] child pid 20911 exit signal Segmentation fault (11) [Tue Oct 10 09:34:34 2006] [notice] child pid 20909 exit signal Segmentation fault (11) [Tue Oct 10 09:34:34 2006] [notice] child pid 20908 exit signal Segmentation fault (11) [Tue Oct 10 09:34:34 2006] [notice] child pid 20907 exit signal Segmentation fault (11) Typical process list: 29242 ?Rs 0:23 /usr/sbin/apache2 -k start 2426 ?Z 0:00 [apache2] 2496 ?Z 0:00 [apache2] 2497 ?Z 0:00 [apache2] 2498 ?Z 0:00 [apache2] 2499 ?Z 0:00 [apache2] 2500 ?Z 0:00 [apache2] 2501 ?Z 0:00 [apache2] 2502 ?Z 0:00 [apache2] 2503 ?Z 0:00 [apache2] 2504 ?Z 0:00 [apache2] 2505 ?Z 0:00 [apache2] 2506 ?Z 0:00 [apache2] 2507 ?Z 0:00 [apache2] 2508 ?Z 0:00 [apache2] 2509 ?Z 0:00 [apache2] 2510 ?Z 0:00 [apache2] 2511 ?Z 0:00 [apache2] 2512 ?Z 0:00 [apache2] 2513 ?Z 0:00 [apache2] 2514 ?Z 0:00 [apache2] 2515 ?Z 0:00 [apache2] 2516 ?Z 0:00 [apache2] 2518 ttyp0S+ 0:00 grep apache2 2519 ?Z 0:00 [apache2] 2520 ?Z 0:00 [apache2] 2521 ?Z 0:00 [apache2] 2523 ?R 0:00 /usr/sbin/apache2 -k start Relevant packages: pi apache2-mpm-prefork 2.2.3-2Traditional model for Apache HTTPD 2.1 ii apache2-utils 2.2.3-2utility programs for webservers ii apache2.2-common2.2.3-2Next generation, scalable, extendable web se ii libapache2-mod-php5 5.1.6-3server-side, HTML-embedded scripting language (apache 2.0 module) T -- To provoke is to call someone stupid; to argue is to call each other stupid. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#388695: geda-gschem: "Probably parenthesis mismatch in" errors in gschem
On 9/22/06, Hamish Moffatt <[EMAIL PROTECTED]> wrote: On Thu, Sep 21, 2006 at 11:12:42PM -0400, H. S. wrote:> (here is the bug again here for geda-gschem, instead of for geda)Thanks. geda-gschem 20060906 should be in etch in a day or two. Can youtry it again then and see if the problem is solved? I updated the geda packages last night. I have tried playing around with gschem for a while and the problems I was facing have gone.Here the versions I now have:$> dpkg -l *geda* | grep ^ii ii geda 20060123-1 GNU EDA -- Electronics design softwareii geda-doc 20060906-1 Documentation for GNU EDA -- Electronics desii geda-examples 20060906-1 GNU EDA -- Electronics design software -- ex ii geda-gattrib 20060906-1 GNU EDA -- Electronics design software -- atii geda-gnetlist 20060906-1 GNU EDA -- Electronics design software -- neii geda-gschem 20060906-1 GNU EDA -- Electronics design software -- sc ii geda-gsymcheck 20060906-1 GNU EDA -- Electronics design software -- syii geda-symbols 20060906-1 Symbols for GNU EDA -- Electronics design soii geda-utils 20060906-1 GNU EDA -- Electronics design software -- ut ii libgdgeda6 2.0.15-3 GNU EDA -- Electronics design software -- gdii libgeda20 20060906-1 GNU EDA -- Electronics design software -- liThanks a ton for solving the problem. Your help is much appreciated. regards,->HS system-gafrc is provided by geda-symbols, which is already updated in etch. However system-gschemrc is not yet. I suspect the skew betweenthem is causing the problem. I will tighten the dependencies in thefuture.> ii geda-gschem20060123-1 GNU EDA -- Electronics design software -- > sc> ii geda-symbols 20060906-1 Symbols for GNU EDA -- Electronics design> sothanks,Hamish--Hamish Moffatt VK3SB <[EMAIL PROTECTED] > <[EMAIL PROTECTED]>
Bug#388695: geda-gschem: "Probably parenthesis mismatch in" errors in gschem
Package: geda-gschem
Version: 20060123-1
Severity: grave
Justification: renders package unusable
*** Please type your report below this line ***
Hello,
(here is the bug again here for geda-gschem, instead of for geda)
If I try to start gschem, I get these errors:
--
$> gschem
gEDA/gschem version 20060123
gEDA/gschem comes with ABSOLUTELY NO WARRANTY; see COPYING for more details.
This is free software, and you are welcome to redistribute it under certain
conditions; please see the COPYING file for more details.
Probably parenthesis mismatch in /etc/gEDA/system-gafrc
Most recently read form: (postscript-prolog ${GEDADATA}/prolog.ps)
Probably parenthesis mismatch in /etc/gEDA/system-gschemrc
Most recently read form: ([EMAIL PROTECTED] ([EMAIL PROTECTED] [EMAIL PROTECTED]
/system-gafrc))
Probably parenthesis mismatch in /usr/share/gEDA/scheme/gschem.scm
Most recently read form: ([EMAIL PROTECTED] global-keymap (quote ()))
Tried to get an invalid color: 0
Tried to get an invalid color: 7
Tried to get an invalid color: 0
Tried to get an invalid color: 7
--
and if I start gschem with a .sch file, I get the above errors and the
schematic is not shown. In both cases, a window opens but it has no menus
on it. So I cannot open pre-existing files at all. If I open a new file,
in the add component dialogbox I cannot see the preview of the components
selected.
I haven't changed any config file.
This behaviour was shown right after installing these package on my Debian Etch
box. The versions that I have installed are:
$> dpkg -l geda* | grep ^ii
ii
geda
20060123-1 GNU EDA -- Electronics design
software
ii geda-doc
20060906-1 Documentation for GNU EDA --
Electronics des
ii geda-examples 20060906-1 GNU EDA -- Electronics design software -- ex
ii geda-gattrib 20060123-1 GNU EDA -- Electronics design software -- at
ii geda-gnetlist 20060123-1 GNU EDA -- Electronics design software -- ne
ii geda-gschem 20060123-1 GNU EDA -- Electronics design software -- sc
ii geda-gsymcheck 20060123-1 GNU EDA -- Electronics design software -- sy
ii geda-symbols 20060906-1 Symbols for GNU EDA -- Electronics design so
ii geda-utils 20060123-1 GNU EDA -- Electronics design software -- ut
-- System Information:
Debian Release: testing/unstable
APT prefers testing
APT policy: (500, 'testing')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.16-2-686
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8)
Versions of packages geda-gschem depends on:
ii
geda-symbols
20060906-1 Symbols for GNU EDA -- Electronics
ii
guile-1.6-libs
1.6.8-4 Main Guile libraries
ii
libatk1.0-0
1.12.2-1 The ATK accessibility toolkit
ii
libc6
2.3.6.ds1-4 GNU C Library: Shared libraries
ii
libcairo2
1.2.4-1 The Cairo 2D vector graphics libra
ii
libfontconfig1
2.3.2-7 generic font configuration library
ii
libgdgeda6
2.0.15-3 GNU EDA -- Electronics design soft
ii libgeda20 [libgeda-25] 20060123-1 GNU EDA -- Electronics design soft
ii
libglib2.0-0
2.12.3-2 The GLib library of C routines
ii
libgtk2.0-0
2.8.20-1 The GTK+ graphical user interface
ii
libguile-ltdl-1
1.6.8-4 Guile's patched version of libtool
ii
libice6
1:1.0.1-2 X11 Inter-Client Exchange library
ii
libpango1.0-0
1.12.3-1+b1 Layout and rendering of internatio
ii
libpng12-0
1.2.8rel-5.2 PNG library - runtime
ii
libqthreads-12
1.6.8-4 QuickThreads library for Guile
ii
libsm6
1:1.0.1-2 X11 Session Management library
ii
libstroke0
0.5.1-5 mouse strokes library -- runtime f
ii
libx11-6
2:1.0.0-8 X11 client-side library
ii
libxcursor1
1.1.7-4 X cursor management library
ii
libxext6
1:1.0.1-2 X11 miscellaneous extension librar
ii
libxi6
1:1.0.1-3 X11 Input extension library
ii
libxinerama1
1:1.0.1-4.1 X11 Xinerama extension library
ii
libxrandr2
2:1.1.0.2-4 X11 RandR extension library
ii
libxrender1
1:0.9.1-3 X Rendering Extension client libra
ii
zlib1g
1:1.2.3-13 compression library - runtime
geda-gschem recommends no packages.
-- no debconf information
Bug#388649: "Probably parenthesis mismatch in" errors in geda
On 9/21/06, Hamish Moffatt <[EMAIL PROTECTED]> wrote: On Thu, Sep 21, 2006 at 02:39:56PM -0400, H. S. wrote:> Package: geda> Version: 20060123-1> Severity: grave> Justification: renders package unusableHi,This bug is with gschem so please report it against gschem. Done. I have also answered your other queries in the new bug report. Thanks, ->HS Then I would get gschem's dependency information (eg your libgeda20 andgeda-symbols versions). Could you please tell me your versions of those two?I suspect the problem could be that etch (testing) now has geda-symbolsfrom gEDA 20060906, while the other packages are still 20060123.Have you modified any of the configuration files? Perhaps you could report this bug again against geda-gschem. Then Iwould get your configuration files also.ThanksHamish--Hamish Moffatt VK3SB <[EMAIL PROTECTED] > <[EMAIL PROTECTED]>
Bug#388649: "Probably parenthesis mismatch in" errors in geda
Package: geda
Version: 20060123-1
Severity: grave
Justification: renders package unusable
*** Please type your report below this line ***
Hello,
If I try to start gschem, I get these errors:
--
$> gschem
gEDA/gschem version 20060123
gEDA/gschem comes with ABSOLUTELY NO WARRANTY; see COPYING for more details.
This is free software, and you are welcome to redistribute it under certain
conditions; please see the COPYING file for more details.
Probably parenthesis mismatch in /etc/gEDA/system-gafrc
Most recently read form: (postscript-prolog ${GEDADATA}/prolog.ps)
Probably parenthesis mismatch in /etc/gEDA/system-gschemrc
Most recently read form: ([EMAIL PROTECTED] ([EMAIL PROTECTED] [EMAIL PROTECTED] /system-gafrc))
Probably parenthesis mismatch in /usr/share/gEDA/scheme/gschem.scm
Most recently read form: ([EMAIL PROTECTED] global-keymap (quote ()))
Tried to get an invalid color: 0
Tried to get an invalid color: 7
Tried to get an invalid color: 0
Tried to get an invalid color: 7
--
and if I start gschem with a .sch file, I get the above erros and the the schematic is not shown. In both cases, a
window opens but it has no menus on it. So I cannot open pre-existing
files at all. If I open a new file, in the add component dialogbox, I
cannot see the preview of the components selected.
-- System Information:
Debian Release: testing/unstable
APT prefers testing
APT policy: (500, 'testing')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.16-2-686
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8)
Versions of packages geda depends on:
ii
geda-doc
20060906-1 Documentation for GNU EDA -- Elect
ii
geda-gnetlist
20060123-1 GNU EDA -- Electronics design soft
ii
geda-gschem
20060123-1 GNU EDA -- Electronics design soft
ii
libatk1.0-0
1.12.2-1 The ATK accessibility toolkit
ii
libc6
2.3.6.ds1-4 GNU C Library: Shared libraries
ii
libcairo2
1.2.4-1 The Cairo 2D vector graphics libra
ii
libfontconfig1
2.3.2-7 generic font configuration library
ii
libglib2.0-0
2.12.3-2 The GLib library of C routines
ii
libgtk2.0-0
2.8.20-1 The GTK+ graphical user interface
ii
libpango1.0-0
1.12.3-1+b1 Layout and rendering of internatio
ii
libx11-6
2:1.0.0-8 X11 client-side library
ii
libxcursor1
1.1.7-4 X cursor management library
ii
libxext6
1:1.0.1-2 X11 miscellaneous extension librar
ii
libxi6
1:1.0.1-3 X11 Input extension library
ii
libxinerama1
1:1.0.1-4.1 X11 Xinerama extension library
ii
libxrandr2
2:1.1.0.2-4 X11 RandR extension library
ii
libxrender1
1:0.9.1-3 X Rendering Extension client libra
geda recommends no packages.
-- no debconf information
Bug#346041: All 2.3.0-* versions are affected
found 346041 2.3.0-1 2.3.0-2 thanks Prevent bad version of cons from making it into a release. :-/ --T -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#346041: Cons dependency scanning broken
Package: cons Version: 2.3.0-2 Severity: serious I just found out that the dependency code in Cons 2.3.0 is broken. It was working in 2.2.0. If anyone has any dependency problems with cons, downgrade to 2.2.0-4. --T -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#317217: Merge bugs
# Merge bugs: these are the same issue severity 317217 grave merge 316593 317217 thanks T -- It is widely believed that reinventing the wheel is a waste of time; but I disagree: without wheel reinventers, we would be still be stuck with wooden horse-cart wheels. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#320705: ayttm: MSN chat problem: cannot connect due to "bad cookies"
Package: ayttm Version: 0.4.6+26-1 Severity: grave Justification: renders package unusable *** Please type your report below this line *** Since quite a few weeks ago, I am not able to connect to MSN messenger. The login try fails with the message: Could not connect to MSN HTTPS server (bad cookies) Apparently, there is a patch for this. Not sure if it works in all cases. The patch is mentioned on ayttm's mailing list. Thanks, ->HS -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (500, 'testing'), (500, 'stable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.11-1-686 Locale: LANG=en_GB.ISO-8859-15, LC_CTYPE=en_GB.ISO-8859-15 (charmap=ISO-8859-15) Versions of packages ayttm depends on: ii libaspell150.60.2+20050121-3 The GNU Aspell spell-checker runti ii libaudiofile0 0.2.6-6 Open-source version of SGI's audio ii libc6 2.3.2.ds1-22 GNU C Library: Shared libraries an ii libesd-alsa0 [libesd0] 0.2.36-1 Enlightened Sound Daemon (ALSA) - ii libgcc11:4.0.1-2 GCC support library ii libgdk-pixbuf2 0.22.0-8 The GdkPixBuf image library, gtk+ ii libglib1.2 1.2.10-10 The GLib library of C routines ii libgpgme6 0.3.16-2 GPGME - GnuPG Made Easy ii libgtk1.2 1.2.10-17 The GIMP Toolkit set of widgets fo ii libltdl3 1.5.6-6 A system independent dlopen wrappe ii libssl0.9.70.9.7e-3 SSL shared libraries ii libstdc++5 1:3.3.5-13The GNU Standard C++ Library v3 ii libx11-6 4.3.0.dfsg.1-14 X Window System protocol client li ii libxext6 4.3.0.dfsg.1-14 X Window System miscellaneous exte ii libxi6 4.3.0.dfsg.1-14 X Window System Input extension li ii libxpm44.3.0.dfsg.1-14 X pixmap library ii xlibs 4.3.0.dfsg.1-14 X Keyboard Extension (XKB) configu ayttm recommends no packages. __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#318526: Bug not fixed
reopen 318526 thanks Ack, previous upload did not actually include the bugfix. Reopening until actual fix. T -- This sentence is false. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#306254: Bugs pending
tags 306254 + pending thanks Per-arch uploads now in the queue, hopefully this will make it into testing before sarge is released. T -- If you compete with slaves, you become a slave. -- Norbert Wiener -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#306254: [installer@ftp-master.debian.org: axe_6.1.2-14_hppa.changes REJECTED]
Hi, I got this message from ftp-master. I'm not sure what happened...? BTW, thanks for making the builds for me. - Forwarded message from Debian Installer <[EMAIL PROTECTED]> - From: Debian Installer <[EMAIL PROTECTED]> To: Hwei Sheng Teoh <[EMAIL PROTECTED]> Subject: axe_6.1.2-14_hppa.changes REJECTED Date: Fri, 29 Apr 2005 04:02:13 -0400 Rejected: axe_6.1.2-14_hppa.changes: a file with this name already exists in the Accepted directory. Rejected: axe_6.1.2-14_hppa.deb file already exists in the Accepted directory. === If you don't understand why your files were rejected, or if the override file requires editing, reply to this email. - End forwarded message - T -- Frank disagreement binds closer than feigned agreement. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#306254: axe: FTBFS: "Failed to satisfy Build-Depends dependency for axe: libxaw-dev"
On Mon, Apr 25, 2005 at 11:42:50AM +0200, Andreas Jochens wrote: [...] > When building 'axe' in a clean 'testing' chroot, > I get the following error: > > Building axe testing main amd64... > Reading Package Lists... > Building Dependency Tree... > Package libxaw-dev is not available, but is referred to by another package. > This may mean that the package is missing, has been obsoleted, or > is only available from another source > However the following packages replace it: > libxaw7-dev libxaw6-dev > E: Package libxaw-dev has no installation candidate > E: Failed to satisfy Build-Depends dependency for axe: libxaw-dev > > The new version 6.1.2-14 in 'sid' does not have this problem. [...] Yes, I have already fixed this problem in 6.1.2-14, but it is not getting into testing. This package is non-free, and unfortunately that means people aren't very inclined to build it on the various archs for me. Also, I don't think this bug should affect the RC bug count for sarge, since it *is* non-free after all. Is there any reason for severity: serious here, other than the fact that the fixed package hasn't made it into testing yet? T -- Today's society is one of specialization: as you grow, you learn more and more about less and less. Eventually, you know everything about nothing. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#300168: more related bugs: "" and "is protected within this context"
(I am not sure if I am right in mentioning additional bugs in this bug report. Please correct me if this is not the convention and I will file a separate one.) Below I have listed new bugs I found and the solutions to fix them (except of one). Just FYI, I have these packages now installed: > dpkg -l *superlu* *arpack* *blas* | grep ^ii ii libsuperlu33.0-2 Direct solution of large, sparse systems of ii libsuperlu3-de 3.0-2 Direct solution of large, sparse systems of ii arpack++ 2.1-5 Object-oriented version of the ARPACK packag ii libarpack2 2.1-8 Fortran77 subroutines to solve large scale e ii libarpack2-dev 2.1-8 Fortran77 subroutines to solve large scale e ii refblas3 1.2-6 Basic Linear Algebra Subroutines 3, shared l ii refblas3-dev 1.2-6 Basic Linear Algebra Subroutines 3, static l Continuing with the examples of ARPACK++, here is another bug: Line 34 of /usr/share/doc/arpack++/examples/matrices/nonsym/lnmatrxa.h is: m = INT(sqrt(n/2)); With this line, the compiler gives the error: #--- /usr/share/doc/arpack++/examples/matrices/nonsym/lnmatrxa.h: In function `void BrusselatorMatrix(FLOAT, FLOAT, FLOAT, FLOAT, FLOAT, INT, INT&, FLOAT*&, INT*&, INT*&) [with FLOAT = double, INT = int]': ansymshf.cc:71: instantiated from here /usr/share/doc/arpack++/examples/matrices/nonsym/lnmatrxa.h:35: error: call of overloaded `sqrt(int)' is ambiguous /usr/include/bits/mathcalls.h:157: error: candidates are: double sqrt(double) /usr/include/c++/3.3/cmath:550: error: long double std::sqrt(long double) /usr/include/c++/3.3/cmath:546: error: float std::sqrt(float) #--- The error is I guess removed by typecasting the argument of 'sqrt' function to double by modifying the line mentioned to: m = INT(sqrt( ((double)n) / 2)); So that took care of that. But is this even advisable? Afterall, 'n' is a template parameter. Anyhow, if I did that change, the compilation progressed further, but I then got these two more rather serious errors(only part of the compiler output here): #--- /usr/include/arpack++/arlgnsym.h: In constructor ` ARluNonSymGenEig::ARluNonSymGenEig(int, ARluNonSymMatrix&, ARluNonSymMatrix&, char*, int, FLOAT, int, FLOAT*, bool) [with FLOAT = double]': areig.h:773: instantiated from `int AREig(FLOAT*, FLOAT*, FLOAT*, int, int, FLOAT*, int*, int*, int, FLOAT*, int*, int*, int, char*, int, FLOAT, int, FLOAT*, bool) [with FLOAT = double]' ansymgre.cc:87: instantiated from here /usr/include/arpack++/arlgnsym.h:193: error: no matching function for call to ` ARluNonSymGenEig::DefineParameters(int, int&, ARluNonSymPencil*, , ARluNonSymPencil*, , char*&, int&, double&, int&, double*&, bool&)' /usr/include/arpack++/argeig.h:128: error: candidates are: void ARGenEig::DefineParameters(int, int, FOP*, typename ARStdEig::TypeOPx, FB*, void (FB::*)(TYPE*, TYPE*), char*, int, FLOAT, int, TYPE*, bool) [with FLOAT = double, TYPE = double, FOP = ARluNonSymPencil, FB = ARluNonSymPencil] /usr/include/arpack++/armat.h: In member function `void ARluNonSymPencil::DefineMatrices(ARluNonSymMatrix&, ARluNonSymMatrix&) [with TYPE = double, FLOAT = double]': areig.h:191: instantiated from `int AREig(FLOAT*, FLOAT*, FLOAT*, int, int, FLOAT*, int*, int*, int, FLOAT*, int*, int*, int, char*, int, FLOAT, int, FLOAT*, bool) [with FLOAT = double]' ansymgre.cc:87: instantiated from here /usr/include/arpack++/armat.h:25: error: `int ARMatrix::m' is protected /usr/include/arpack++/arlnspen.h:675: error: within this context /usr/include/arpack++/armat.h:25: error: `int ARMatrix::m' is protected /usr/include/arpack++/arlnspen.h:675: error: within this context /usr/include/arpack++/armat.h:25: error: `int ARMatrix::n' is protected /usr/include/arpack++/arlnspen.h:675: error: within this context /usr/include/arpack++/armat.h:25: error: `int ARMatrix::n' is protected /usr/include/arpack++/arlnspen.h:675: error: within this context #--- The first error above is the now familiar one of "". That is solved by putting "&" in before the 4th and 6th arguments of DefineParameters function at line 193 of /usr/include/arpack++/arlgnsym.h and making lines 193~196 of this file as: %< %< DefineParameters(A.ncols(), nevp, &Pencil, &ARluNonSymPencil::MultInvBAv, &Pencil, &ARluNonSymPencil::MultBv, whichp, ncvp, tolp, maxitp, residp, ishiftp); %< %< That leaves us with the second type of errors that a variable "is protected within this context". That happens because the class ARluNonSymPencil(in arlnspen.h) contains ARluNonSymMatrix* A and ARluNonSymMatrix* B (as protected members). And the c
Bug#300168: solution to the "" compiler error
By expicitly making the fourth argument of
DefineParameters in /usr/include/arpack++/arlsnsym.h (line
144, IIRC) as an address(by preceding it with a "&") made
the compiler happy. Here is the relevant portion I have in
this file now which compiles okay:
//**
template
inline ARluNonSymStdEig::
ARluNonSymStdEig(int nevp, ARluNonSymMatrix& A,
char* whichp, int ncvp, FLOAT tolp,
int maxitp, FLOAT* residp, bool ishiftp)
{
NoShift();
//followin modified by HS,19Mar2005, to remove compiler error
//DefineParameters(A.ncols(), nevp, &A,
ARluNonSymMatrix::MultMv,
// whichp, ncvp, tolp, maxitp, residp,
ishiftp);
DefineParameters(A.ncols(), nevp, &A,
&ARluNonSymMatrix::MultMv,
whichp, ncvp, tolp, maxitp, residp,
ishiftp);
} // Long constructor (regular mode).
///*
Though that "" compiler error is gone, but
running "make simple" in examples/nonsym directory then
gave a "default agrument already given" compiler error in
/usr/include/arpack++/arlgnsym.h. This was solved by
removing the initialization of the second default argument
at line 131 of this file in the definition:
ChangeShift(FLOAT sigmaRp, FLOAT sigmaIp = 0.0)
The revised definition now that works for me is:
///***
template
inline void ARluNonSymGenEig::
//modified by HS,19Mar2005, to remove "default argument"
compiler error
//ChangeShift(FLOAT sigmaRp, FLOAT sigmaIp = 0.0)
ChangeShift(FLOAT sigmaRp, FLOAT sigmaIp)
///***
Once solving this, I am not facing other problems related
to linking. It appears that I do not have SuperLU package
installed. However, to compile simple.cc it doesn't seem
to be necessary to have it installed according to the
README file in
/usr/share/doc/arpack++/examples/areig/nonsym/. Oh well, I
need to install that and see if that solves these linker
problems. But I digress from the topic of this bug :)
->HS
__
Do you Yahoo!?
Yahoo! Small Business - Try our new resources site!
http://smallbusiness.yahoo.com/resources/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#300168: arpack++: fails to comple simple.cc example given in "nonsym" examples directory
Package: arpack++ Version: 2.1-5 Severity: grave Justification: renders package unusable *** Please type your report below this line *** I am trying to comple an example that is included in the package. The compiler fails with an error (see below). What I did was: 1) Copied the /usr/share/doc/arpack++/examples/areig/nonsym to a temporary directory 2) Copied the /usr/share/doc/arpack++/Makefile.inc to the same directory 3) Edited the Makefile.inc to have the following lines: ARPACKPP_DIR = /usr/share/doc/arpack++ #ARPACKPP_INC = $(ARPACKPP_DIR)/include ARPACKPP_INC = /usr/include/arpack++ 4) Edited the Makefile to have the following lines #include ../../../Makefile.inc include Makefile.inc 5) And tried to compile the simple.cc program: $> make simple 6) And compile had a problem with this error (full compiler output is given as PS): /usr/include/arpack++/arlsnsym.h:144: error: no matching function for call to ` ARluNonSymStdEig::DefineParameters(int, int&, ARluNonSymMatrix*, , char*&, int&, double&, int&, double*&, bool&)' Do I need to change something else too to make this example program run? Here are other relevant packages I am using: ii g++ 3.3.5-1The GNU C++ compiler ii arpack++2.1-5 Object-oriented version of the ARPACK package Thanks, ->HS PS. Full compiler output: $> make simple g++ -O -I/usr/include/arpack++ -I/usr/share/doc/arpack++/examples/areig -I/usr/share/doc/arpack++/examples/matrices/nonsym -I/usr/include/arpack++ -c simple.cc In file included from /usr/include/arpack++/arlsmat.h:26, from /usr/include/arpack++/arlspen.h:28, from /usr/include/arpack++/arlsmat.h:18, from areig.h:364, from simple.cc:20: /usr/include/arpack++/arhbmat.h:400:8: warning: extra tokens at end of #endif directive In file included from /usr/include/arpack++/arlgnsym.h:26, from areig.h:369, from simple.cc:20: /usr/include/arpack++/argnsym.h:40: warning: `ARNonSymGenEig::TypeBx' is implicitly a typename /usr/include/arpack++/argnsym.h:40: warning: implicit typename is deprecated, please see the documentation for details In file included from areig.h:369, from simple.cc:20: /usr/include/arpack++/arlgnsym.h:132: error: default argument given for parameter 2 of `void ARluNonSymGenEig::ChangeShift(FLOAT, FLOAT)' /usr/include/arpack++/arlgnsym.h:54: error: after previous specification in ` virtual void ARluNonSymGenEig::ChangeShift(FLOAT, FLOAT)' simple.cc: In function `int main()': simple.cc:53: error: `cout' undeclared (first use this function) simple.cc:53: error: (Each undeclared identifier is reported only once for each function it appears in.) simple.cc:53: error: `endl' undeclared (first use this function) /usr/include/arpack++/arlsnsym.h: In constructor ` ARluNonSymStdEig::ARluNonSymStdEig(int, ARluNonSymMatrix&, char*, int, FLOAT, int, FLOAT*, bool) [with FLOAT = double]': areig.h:628: instantiated from `int AREig(FLOAT*, FLOAT*, FLOAT*, int, int, FLOAT*, int*, int*, int, char*, int, FLOAT, int, FLOAT*, bool) [with FLOAT = double]' simple.cc:49: instantiated from here /usr/include/arpack++/arlsnsym.h:144: error: no matching function for call to ` ARluNonSymStdEig::DefineParameters(int, int&, ARluNonSymMatrix*, , char*&, int&, double&, int&, double*&, bool&)' /usr/include/arpack++/arseig.h:137: error: candidates are: void ARStdEig::DefineParameters(int, int, FOP*, void (FOP::*)(TYPE*, TYPE*), char*, int, FLOAT, int, TYPE*, bool) [with FLOAT = double, TYPE = double, FOP = ARluNonSymMatrix] /usr/include/arpack++/arlnsmat.h: In member function `void ARluNonSymMatrix::ClearMem() [with TYPE = double]': /usr/include/arpack++/arlnsmat.h:116: instantiated from `ARluNonSymMatrix::~ARluNonSymMatrix() [with TYPE = double]' areig.h:623: instantiated from `int AREig(FLOAT*, FLOAT*, FLOAT*, int, int, FLOAT*, int*, int*, int, char*, int, FLOAT, int, FLOAT*, bool) [with FLOAT = double]' simple.cc:49: instantiated from here /usr/include/arpack++/arlnsmat.h:207: warning: deleting `void*' is undefined make: *** [simple.o] Error 1 -- System Information: Debian Release: 3.1 APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.9.20041123.hs Locale: LANG=en_GB.ISO-8859-15, LC_CTYPE=en_GB.ISO-8859-15 (charmap=ISO-8859-15) Versions of packages arpack++ depends on: ii libarpack2-dev2.1-8 Fortran77 subroutines to solve lar -- no debconf information __ Do you Yahoo!? Make Yahoo! your home page http://www.yahoo.com/r/hs -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
