Bug#501820: fglrx-driver breaks DRI for xserver-xorg-video-radeon
Package: fglrx-driver Version: 1:8-7-2 Severity: critical Justification: breaks unrelated software Hi, when fglrx-driver is installed DRI is broken for the open source radeon/ati driver. Here's an excerpt of glxinfo: ~$ LIBGL_DEBUG=verbose glxinfo name of display: :0.0 libGL: XF86DRIGetClientDriverName: 5.3.0 r300 (screen 0) libGL: OpenDriver: trying /usr/lib/dri/r300_dri.so libGL error: dlopen /usr/lib/dri/r300_dri.so failed (/usr/lib/dri/r300_dri.so: undefined symbol: _glapi_Dispatch) libGL error: unable to load driver: r300_dri.so display: :0 screen: 0 direct rendering: No (If you want to find out why, try setting LIBGL_DEBUG=verbose) Kind regards, Felix -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (990, 'unstable'), (500, 'testing'), (500, 'stable'), (101, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.26.3-jawaka (PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages fglrx-driver depends on: ii fglrx-glx 1:8-7-2proprietary libGL for the non-free ii libc6 2.7-14 GNU C Library: Shared libraries ii libgl1-mesa-glx [libgl1] 7.0.3-6A free implementation of the OpenG ii libx11-6 2:1.1.5-2 X11 client-side library ii libxext6 2:1.0.4-1 X11 miscellaneous extension librar ii libxrandr22:1.2.3-1 X11 RandR extension library ii libxrender1 1:0.9.4-2 X Rendering Extension client libra ii xserver-xorg 1:7.3+18 the X.Org X server Versions of packages fglrx-driver recommends: ii fglrx-atieventsd 1:8-7-2external events daemon for the non ii fglrx-glx 1:8-7-2proprietary libGL for the non-free ii fglrx-source 1:8-7-2kernel module source for the non-f Versions of packages fglrx-driver suggests: ii fglrx-control 8.28.8-4 control panel for the ATI graphics -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#501820: [Pkg-fglrx-devel] Bug#501820: fglrx-driver breaks DRI for xserver-xorg-video-radeon
Hi Romain, if it's a wontfix there should at least be a note about the issue in the package documentation. If it's not mentioned anywhere people who have tried (and thus installed ) the fglrx driver will think the radeon driver is broken. At least that's what I thought... Regards, Felix Romain Beauxis wrote: severity 501820 normal tag 501820 wontfix thanks Le Friday 10 October 2008 19:57:50 Felix Homann, vous avez écrit : Hi, Hi ! when fglrx-driver is installed DRI is broken for the open source radeon/ati driver. Here's an excerpt of glxinfo: Yep, this is surely a consequence of the private version of libGL installed by fglrx. Just uninstall it and it should be fixed. Romain -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#485821: qtiplot: Crashes and Symbol `_ZTV9QwtSymbol' has different size...consider re-linking
Package: qtiplot Version: 0.9.4-1 Severity: grave Justification: renders package unusable qtiplot currently crashes when trying to plot. On start, it spits out two warnings: qtiplot: Symbol `_ZTV9QwtSymbol' has different size in shared object, consider re-linking qtiplot: Symbol `_ZTV13QwtPlotPicker' has different size in shared object, consider re-linking which are probably related to the crash. Tested on i386 and amd64. Kind regards, Felix -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (990, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.24.3-yerbouti (SMP w/2 CPU cores; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages qtiplot depends on: ii libaudio2 1.9.1-2 Network Audio System - shared libr ii libc6 2.7-12GNU C Library: Shared libraries ii libfontconfig1 2.6.0-1 generic font configuration library ii libfreetype6 2.3.5-1+b1FreeType 2 font engine, shared lib ii libgcc11:4.3.1-1 GCC support library ii libgl1-mesa-glx [libgl 7.0.3-1 A free implementation of the OpenG ii libglib2.0-0 2.16.3-2 The GLib library of C routines ii libglu1-mesa [libglu1] 7.0.3-1 The OpenGL utility library (GLU) ii libgsl0ldbl1.11-2GNU Scientific Library (GSL) -- li ii libice62:1.0.4-1 X11 Inter-Client Exchange library ii libmuparser0 1.28-2fast mathematical expressions pars ii libmysqlclient15off5.0.51a-7 MySQL database client library ii liborigin0 20080225-2library for reading OriginLab Orig ii libpng12-0 1.2.27-1 PNG library - runtime ii libpq5 8.3.1-2+b1PostgreSQL C client library ii libqt4-core4.4.0-3 transitional package for Qt 4 core ii libqt4-gui 4.4.0-3 transitional package for Qt 4 GUI ii libqt4-qt3support 4.4.0-3 Qt 3 compatibility library for Qt ii libqt4-sql 4.4.0-3 Qt 4 SQL module ii libqwt5-qt45.1.1-1 Qt4 widgets library for technical ii libqwtplot3d-qt4 0.2.7+svn191-23D plotting library based on Qt4/O ii libsm6 2:1.0.3-1+b1 X11 Session Management library ii libsqlite0 2.8.17-4 SQLite shared library ii libsqlite3-0 3.5.9-2 SQLite 3 shared library ii libstdc++6 4.3.1-1 The GNU Standard C++ Library v3 ii libx11-6 2:1.1.4-2 X11 client-side library ii libxcursor11:1.1.9-1 X cursor management library ii libxext6 2:1.0.4-1 X11 miscellaneous extension librar ii libxfixes3 1:4.0.3-2 X11 miscellaneous 'fixes' extensio ii libxi6 2:1.1.3-1 X11 Input extension library ii libxinerama1 2:1.0.3-2 X11 Xinerama extension library ii libxrandr2 2:1.2.2-2 X11 RandR extension library ii libxrender11:0.9.4-1 X Rendering Extension client libra ii libxt6 1:1.0.5-3 X11 toolkit intrinsics library ii python-qt4 4.3.3-3 Python bindings for Qt4 ii python2.4 2.4.5-2 An interactive high-level object-o ii zlib1g 1:1.2.3.3.dfsg-12 compression library - runtime qtiplot recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#473494: libginac1.4: Doesn't work with libcln5=1.2.1-1, undefined symbol: cl_double_to_DF_pointer
Package: libginac1.4 Version: 1.4.1-1+b2 Severity: grave Justification: renders package unusable Hi, libcln5 1.2.1-1 renders libginac1.4.1-1+b2 unusable. Linking is not possible as ld returns: /usr/lib/gcc/x86_64-linux-gnu/4.2.3/../../../../lib64/libginac.so: undefined reference to `cln::cl_double_to_DF_pointer(cln::dfloatjanus const)' Or just start ginsh to see a similar undefined reference error: ginsh: symbol lookup error: /usr/lib/libginac-1.4.so.0: undefined symbol: _ZN3cln23cl_double_to_DF_pointerERKNS_11dfloatjanusE Kind regards, Felix -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (990, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.23.14-yerbouti (SMP w/2 CPU cores; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages libginac1.4 depends on: ii libc6 2.7-10 GNU C Library: Shared libraries ii libcln5 1.2.1-1Class Library for Numbers (C++) ii libgcc1 1:4.3.0-2 GCC support library ii libstdc++64.3.0-2The GNU Standard C++ Library v3 libginac1.4 recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#469221: apt-listchanges: How about a viable solution from a user's point of view?
Pierre Habouzit wrote: Everything seems to be fine afterwards again. of course, and you just trashed your whole history with it, nice... or not. Well, without knowledge of the intrinsics, I was faced with only 3 options: 1. continue using apt-listchanges but trashing the history 2. remove apt-listchanges to get rid of the error messages 3. just live with the error messages (4. Dig into the intrinsics) Option 1 seemed most reasonable to me since apparently nobody feels responsible for fixing the issue! And does it make any difference? Does apt-listchanges behave very different with a trashed history? (I really don't know, could you please elucidate on this? ) the solution is to: $ db4.6_dump /var/lib/apt/listchanges.db | db4.5_load a.db $ mv a.db /var/lib/apt/listchanges.db Thanks, this should have gone in a NEWS file, or at least in the bug tracking system days ago, IMO. Until you find a real solution you could include this information in a NEWS.Debian file. Or one could instead fix python That's what I meant debating responsibilities: You won't fix, Matthias won't fix ...then at least tell the user's what *they* can do to work around this bug in the meantime. Nevertheless, thank you very much for this better solution, I'm gonna use it on my 2nd machine! Kind regards, Felix -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#469221: apt-listchanges: How about a viable solution from a user's point of view?
Pierre Habouzit wrote: it doesn't show changelogs for a package it considers new (as it would else show YEARS of useless changelogs since it's not really changes). So you won't see changelogs for upgrades on your _next_ upgrade of those packages, only for the one after that. Thank you very much for the clarification! Regards, Felix -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#469221: apt-listchanges: How about a viable solution from a user's point of view?
Package: apt-listchanges Version: 2.82 Followup-For: Bug #469221 OK, while you're all apparently busy debating responsibilities, here's something for those bothered by 'bsddb.db.DBRunRecoveryError' messages: sudo aptitude purge apt-listchanges sudo aptitude install apt-listchanges Everything seems to be fine afterwards again. Until you find a real solution you could include this information in a NEWS.Debian file. Regards, Felix -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (990, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.23.14-yerbouti (SMP w/2 CPU cores; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages apt-listchanges depends on: ii apt 0.7.11 Advanced front-end for dpkg ii debconf [debconf-2.0] 1.5.20 Debian configuration management sy ii debianutils 2.28.4 Miscellaneous utilities specific t ii python2.4.4-6An interactive high-level object-o ii python-apt0.7.5 Python interface to libapt-pkg ii python-support0.7.7 automated rebuilding support for P ii ucf 3.005 Update Configuration File: preserv Versions of packages apt-listchanges recommends: ii exim4 4.69-2 meta-package to ease Exim MTA (v4) ii exim4-daemon-light [mail-tran 4.69-2 lightweight Exim MTA (v4) daemon -- debconf information: apt-listchanges/confirm: false apt-listchanges/email-address: root apt-listchanges/which: news apt-listchanges/frontend: pager apt-listchanges/save-seen: true -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#420814: fglrx-driver: Not fixed, yet. Please reopen
Package: fglrx-driver Version: 8.38.6-2 Followup-For: Bug #420814 Hi, although the fglrx-driver issues related to newer versions of xserver-xorg-core are supposed to be resolved since fglrx-driver 8.37.6-1 it never worked on my system. I've even already tried version 8.40.4-2 from experimental or different kernels without success: fglrx-driver together with xserver-xorg-core (2:1.3.0.0.dfsg-12 at the moment) will lead to a black screen and an unresponsive system (I can ssh in, though). I've attached a corresponding the Xorg.0.log. Kind regards, Felix -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (990, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.22.2 (PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages fglrx-driver depends on: ii libc6 2.6.1-1 GNU C Library: Shared libraries ii libgcc1 1:4.2-20070712-1 GCC support library ii libstdc++5 1:3.3.6-15 The GNU Standard C++ Library v3 ii libx11-62:1.0.3-7X11 client-side library ii libxext61:1.0.3-2X11 miscellaneous extension librar ii libxrandr2 2:1.2.1-1X11 RandR extension library ii libxrender1 1:0.9.2-1X Rendering Extension client libra ii xserver-xorg1:7.2-5 the X.Org X server Versions of packages fglrx-driver recommends: ii fglrx-kernel-2.6.22.2 [fglrx- 8.38.6-2 ATI binary kernel module for Linux ii fglrx-kernel-src 8.38.6-2 kernel module source for the ATI g -- no debconf information X Window System Version 1.3.0 Release Date: 19 April 2007 X Protocol Version 11, Revision 0, Release 1.3 Build Operating System: Linux Debian (xorg-server 2:1.3.0.0.dfsg-12) Current Operating System: Linux jawaka 2.6.22.2 #1 PREEMPT Wed Aug 15 12:14:20 CEST 2007 i686 Build Date: 09 August 2007 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Module Loader present Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: /var/log/Xorg.0.log, Time: Thu Aug 16 17:40:00 2007 (==) Using config file: /etc/X11/xorg.conf (==) ServerLayout Default Layout (**) |--Screen Default Screen (0) (**) | |--Monitor Generic Monitor (**) | |--Device ATI Technologies, Inc. M24 1P [Radeon Mobility X600] (**) |--Input Device Generic Keyboard (**) |--Input Device Configured Mouse (**) |--Input Device Synaptics Touchpad (WW) The directory /usr/share/fonts/X11/cyrillic does not exist. Entry deleted from font path. (WW) `fonts.dir' not found (or not valid) in /var/lib/defoma/x-ttcidfont-conf.d/dirs/CID. Entry deleted from font path. (Run 'mkfontdir' on /var/lib/defoma/x-ttcidfont-conf.d/dirs/CID). (WW) Including the default font path /usr/share/fonts/X11/misc,/usr/share/fonts/X11/cyrillic,/usr/share/fonts/X11/100dpi/:unscaled,/usr/share/fonts/X11/75dpi/:unscaled,/usr/share/fonts/X11/Type1,/usr/share/fonts/X11/100dpi,/usr/share/fonts/X11/75dpi,/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType. (**) FontPath set to: /usr/share/fonts/X11/misc, /usr/share/fonts/X11/100dpi/:unscaled, /usr/share/fonts/X11/75dpi/:unscaled, /usr/share/fonts/X11/Type1, /usr/share/fonts/X11/100dpi, /usr/share/fonts/X11/75dpi, /var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType, /usr/share/fonts/X11/misc, /usr/share/fonts/X11/cyrillic, /usr/share/fonts/X11/100dpi/:unscaled, /usr/share/fonts/X11/75dpi/:unscaled, /usr/share/fonts/X11/Type1, /usr/share/fonts/X11/100dpi, /usr/share/fonts/X11/75dpi, /var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType (==) RgbPath set to /etc/X11/rgb (==) ModulePath set to /usr/lib/xorg/modules (II) Open ACPI successful (/var/run/acpid.socket) (II) Loader magic: 0x81e5140 (II) Module ABI versions: X.Org ANSI C Emulation: 0.3 X.Org Video Driver: 1.2 X.Org XInput driver : 0.7 X.Org Server Extension : 0.3 X.Org Font Renderer : 0.5 (II) Loader running on linux (II) LoadModule: pcidata (II) Loading /usr/lib/xorg/modules//libpcidata.so (II) Module pcidata: vendor=X.Org Foundation compiled for 1.3.0, module version = 1.0.0 ABI class: X.Org Video Driver, version 1.2 (++) using VT number 7 (II) PCI: PCI scan (all values are in hex) (II) PCI: 00:00:0: chip 8086,2590 card 1025,0066 rev 03 class 06,00,00 hdr 00 (II) PCI: 00:01:0: chip 8086,2591 card , rev 03 class 06,04,00 hdr 01 (II) PCI: 00:1c:0: chip 8086,2660 card , rev 04 class 06,04,00 hdr 81 (II) PCI: 00:1c:1: chip 8086,2662 card
Bug#420814: Found a solution!
Hi, searching the web I've found an interesting link with a solution to my problem: http://pastebin.ca/644793 The solution is simple but not easy to guess: Remove all lines containing containing PairModes in /etc/ati/amdpcsdb and /etc/X11/xorg.conf. Could you please add a line in README.Debian or wherever it's more appropriate? Kind regards, Felix -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#425476: icedove: Can't send or receive emails after upgrade to 2.0.0.0-3
Package: icedove Version: 2.0.0.0-3 Severity: grave Justification: renders package unusable Hi, I've just upgraded to 2.0.0.0-3. Now, I can't send or receive emails anymore. On start-up icedove alerts Icedove can't connect securely to imap.xxx.xxx because the SSL protocol has been disabled I've configured the server to use TLS if available, though, not SSL. When trying to write an email I get a message An error occured while creating a message compose window. Please try again. I've tried again a couple of times without success. Since an email client that can't send or receive emails is completely useless, I've put severity to grave. Kind regards, Felix Homann -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (990, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.21-yerbouti (SMP w/2 CPU cores; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages icedove depends on: ii debianutils 2.18.2 Miscellaneous utilities specific t ii fontconfig 2.4.2-1.2generic font configuration library ii libatk1.0-0 1.18.0-2 The ATK accessibility toolkit ii libc6 2.5-8GNU C Library: Shared libraries ii libcairo2 1.4.6-1 The Cairo 2D vector graphics libra ii libfontconfig1 2.4.2-1.2generic font configuration library ii libfreetype62.2.1-5 FreeType 2 font engine, shared lib ii libgcc1 1:4.2-20070516-1 GCC support library ii libglib2.0-02.12.12-1The GLib library of C routines ii libgtk2.0-0 2.10.12-2The GTK+ graphical user interface ii libjpeg62 6b-13The Independent JPEG Group's JPEG ii libnspr4-0d 4.6.6-3 NetScape Portable Runtime Library ii libnss3-0d 3.11.5-3+b1 Network Security Service libraries ii libpango1.0-0 1.16.4-1 Layout and rendering of internatio ii libpng12-0 1.2.15~beta5-2 PNG library - runtime ii libstdc++6 4.2-20070516-1 The GNU Standard C++ Library v3 ii libx11-62:1.0.3-7X11 client-side library ii libxcursor1 1:1.1.8-2X cursor management library ii libxext61:1.0.3-2X11 miscellaneous extension librar ii libxfixes3 1:4.0.3-2X11 miscellaneous 'fixes' extensio ii libxft2 2.1.12-2 FreeType-based font drawing librar ii libxi6 1:1.0.1-4X11 Input extension library ii libxinerama11:1.0.2-1X11 Xinerama extension library ii libxrandr2 2:1.2.1-1X11 RandR extension library ii libxrender1 1:0.9.2-1X Rendering Extension client libra ii libxt6 1:1.0.5-3X11 toolkit intrinsics library ii psmisc 22.5-1 Utilities that use the proc filesy ii zlib1g 1:1.2.3-15 compression library - runtime icedove recommends no packages. -- debconf information: icedove/browser: Debian -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#402175: powersaved: Wrong (constant) battery info when AC is unplugged
Package: powersaved Version: 0.14.0-6 Severity: critical Justification: causes serious data loss On my laptop, when the AC adaptor is unplugged 'powersave -B' reports a constant battery state (75% charged, 180 minutes left) no matter what the state according to 'acpi -V' is, it doesn't change a bit. If the AC adaptor is plugged in 'powersave -B' reports values which are comparable with those of 'acpi -V'. I've set the severity to critical since I think that one of the key functions of powersaved for laptop users is to prevent data loss caused by running out of battery. If powersaved constantly sees 75% of capacity it will never trigger the appropriate actions. I don't know when this faulty behaviour started but I remember that it has been working correctly in the past. Kind regards, Felix -- System Information: Debian Release: 4.0 APT prefers unstable APT policy: (990, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18.1-jawaka Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Versions of packages powersaved depends on: ii adduser 3.100 Add and remove users and groups ii dbus 1.0.1-2 simple interprocess messaging syst ii hal 0.5.8.1-4 Hardware Abstraction Layer ii libc62.3.6.ds1-9 GNU C Library: Shared libraries ii libcpufreq0 002-2 shared library to deal with the cp ii libdbus-1-3 1.0.1-2 simple interprocess messaging syst ii libdbus-glib-1-2 0.71-3 simple interprocess messaging syst ii libgcc1 1:4.1.1-20 GCC support library ii libglib2.0-0 2.12.4-2The GLib library of C routines ii libhal1 0.5.8.1-4 Hardware Abstraction Layer - share ii libpowersave10 0.14.0-6power management daemon - shared l ii libstdc++6 4.1.1-20The GNU Standard C++ Library v3 ii lsb-base 3.1-22 Linux Standard Base 3.1 init scrip Versions of packages powersaved recommends: ii acpid 1.0.4-5 Utilities for using ACPI power man ii grub 0.97-20 GRand Unified Bootloader ii hdparm 6.9-1 tune hard disk parameters for high ii kpowersave 0.6.2-4 frontend to powersave for setting ii uswsusp0.3~cvs20060928-4 tools to use userspace software su -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#401341: Starting gnue-appserver fails
Package: gnue-appserver Version: 0.4.3-1 Severity: grave Justification: renders package unusable After a fresh install I get this: Starting gnue-appserver: gnue-appserverTraceback (most recent call last): File /usr/bin/gnue-appserver, line 30, in ? from gnue.appserver import geasRpcServer ImportError: No module named gnue.appserver Kind regards, Felix -- System Information: Debian Release: 4.0 APT prefers unstable APT policy: (990, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18.1-jawaka Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Versions of packages gnue-appserver depends on: ii gnue-common 0.6.1-1GNU Enterprise Common Library for ii python2.4.4-1An interactive high-level object-o gnue-appserver recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#378839: [Pkg-bluetooth-maintainers] Bug#378839: bluez-pcmcia-support: udev support broken
On Tuesday 08 August 2006 04:15, Adeodato Simó wrote: * Felix Homann [Wed, 26 Jul 2006 10:12:11 +0200]: On Tuesday 25 July 2006 16:23, Filippo Giunchedi wrote: okay, I've updated bluetooth.sh and bluez-pcmcia-support.udev again, do you mind trying if it works as expected? It works as expected. Does this mean the bug is fixed in version 3.1-3 of the package, and so the bug can be closed? Yes, it can IMO. Kind regards, Felix
Bug#378839: [Pkg-bluetooth-maintainers] Bug#378839: bluez-pcmcia-support: udev support broken
On Tuesday 25 July 2006 16:23, Filippo Giunchedi wrote:
okay, I've updated bluetooth.sh and bluez-pcmcia-support.udev again, do you
mind trying if it works as expected?
It works as expected.
Also can you paste the relevant udev
database entry for your card?
Here you go:
P: /class/tty/ttyS2
N: ttyS2
E: MANFID=0x025e
E: CARD_ID=0x1000
E: DEVICENAME=
searching the output of udevinfo -e might
help. Only the mapping for $DEVICENAME is left to figure out.
I don't understand what you expect here. As far as I can tell $DEVICENAME
_has_ to be empty since $name is not a valid key (at least not mentioned
in 'man udev'). It is not needed or used anywhere, so I think that
ENV{DEVICENAME}=$name should be removed.
If it was meant as a reaction on Marcel's remark about the DEVICE=`echo
$DEVNAME|sed -e 's_/dev/__'` line in bluetooth.sh you can safely remove
that line and use
/usr/sbin/hciattach $DEVNAME ...
I agree with Marcel in that the script should be renamed
into bluetooth_serial (and every other point he made!).
Kind regards,
Felix
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#378839: [Pkg-bluetooth-maintainers] Bug#378839: bluez-pcmcia-support: udev support broken
On Tuesday 25 July 2006 11:12, Filippo Giunchedi wrote: I've modified the rules file, it is available at http://svn.debian.org/wsvn/pkg-bluetooth/bluez-utils/trunk/debian/bluez-pcm cia-support.udev?op=filerev=0sc=0 and the bluetooth.sh invoked on RUN available at http://svn.debian.org/wsvn/pkg-bluetooth/bluez-utils/trunk/debian/bluetooth .sh?op=filerev=0sc=0 what about the change from DEVPATH to PHYSDEVPATH Felix proposed in bluetooth.sh? Felix: do you mind trying the first file to see if it works for you? It's working, but only if PHYSDEVPATH is used in bluetooth.sh. Kind regards, Felix -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#378839: [Pkg-bluetooth-maintainers] Bug#378839: bluez-pcmcia-support: udev support broken
On Tuesday 25 July 2006 11:12, Filippo Giunchedi wrote: what about the change from DEVPATH to PHYSDEVPATH Felix proposed in bluetooth.sh? Hi again, MANFID=`cat /sys/$PHYSDEVPATH/manf_id`,`cat /sys/$PHYSDEVPATH/card_id` and MANFID=`cat /sys/$DEVPATH/device/manf_id`,`cat /sys/$DEVPATH/device/card_id` seem to be equivalent in this setting. I don't know if either one is prefered or deprecated, but I would now prefer the latter since it's simpler: $DEVPATH - /class/tty/ttyS2 $PHYSDEVPATH - /devices/pci:00/:00:1e.0/:06:01.0/0.0 (on insertion of a SPHINX card) Kind regards, Felix -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#378839: [Pkg-bluetooth-maintainers] Bug#378839: bluez-pcmcia-support: udev support broken
On Tuesday 25 July 2006 13:18, Kay Sievers wrote:
PHYSDEVPATH and the 'device' link are both deprecated and will go away
some day in the future, you better pass the values you want to use in
your script down from udev with $sysfs{}. That is not dependent on a
specific order of devices in sysfs.
Kay
Thanks,
I've attached working (for me) rules+bluetooth.sh. $sysfs{manf_id} and
$sysfs{card_id} are passed to bluetooth.sh.
Kind regards,
Felix
## PCMCIA-Cards
# Brain Boxes BL-620 Bluetooth Adapter
SUBSYSTEM==tty, BUS==pcmcia, SYSFS{prod_id1}==Brain Boxes,
SYSFS{prod_id2}==Bluetooth PC Card, RUN+=/lib/udev/bluetooth.sh
$sysfs{manf_id} $sysfs{card_id}
# Xircom CreditCard Bluetooth Adapter
SUBSYSTEM==tty, BUS==pcmcia, SYSFS{prod_id1}==Xircom,
SYSFS{prod_id3}==CBT, RUN+=/lib/udev/bluetooth.sh $sysfs{manf_id}
$sysfs{card_id}
# Xircom RealPort2 Bluetooth Adapter
SUBSYSTEM==tty, BUS==pcmcia, SYSFS{prod_id1}==Xircom,
SYSFS{prod_id3}==CBT, RUN+=/lib/udev/bluetooth.sh $sysfs{manf_id}
$sysfs{card_id}
# IBM Bluetooth PC Card II
SUBSYSTEM==tty, BUS==pcmcia, SYSFS{prod_id1}==IBM,
SYSFS{prod_id2}==Bluetooth PC Card II, RUN+=/lib/udev/bluetooth.sh
$sysfs{manf_id} $sysfs{card_id}
# TDK Bluetooth PC Card
SUBSYSTEM==tty, BUS==pcmcia, SYSFS{prod_id1}==TDK,
SYSFS{prod_id2}==Bluetooth PC Card II, RUN+=/lib/udev/bluetooth.sh
$sysfs{manf_id} $sysfs{card_id}
# AmbiCom BT2000C Bluetooth PC/CF Card
SUBSYSTEM==tty, BUS==pcmcia, SYSFS{prod_id1}==AmbiCom BT2000C,
SYSFS{prod_id2}==Bluetooth PC/CF Card, RUN+=/lib/udev/bluetooth.sh
$sysfs{manf_id} $sysfs{card_id}
# COM One Platinium Bluetooth PC Card
SUBSYSTEM==tty, BUS==pcmcia, SYSFS{prod_id1}==COM1 SA,
SYSFS{prod_id2}==MC310 CARD, RUN+=/lib/udev/bluetooth.sh $sysfs{manf_id}
$sysfs{card_id}
# Sphinx PICO Card
SUBSYSTEM==tty, BUS==pcmcia, SYSFS{prod_id1}==SPHINX,
SYSFS{prod_id2}==BT-CARD, RUN+=/lib/udev/bluetooth.sh $sysfs{manf_id}
$sysfs{card_id}
# H-Soft blue+Card
SUBSYSTEM==tty, BUS==pcmcia, SYSFS{prod_id1}==H-Soft,
SYSFS{prod_id2}==Blue+CARD, RUN+=/lib/udev/bluetooth.sh $sysfs{manf_id}
$sysfs{card_id}
# Compaq iPAQ Bluetooth Sleeve
SUBSYSTEM==tty, BUS==pcmcia, SYSFS{prod_id1}==CF CARD,
SYSFS{prod_id2}==GENERIC, RUN+=/lib/udev/bluetooth.sh $sysfs{manf_id}
$sysfs{card_id}
# Zoom Bluetooth Card
# Sitecom CN-504 Card
SUBSYSTEM==tty, BUS==pcmcia, SYSFS{prod_id1}==PCMCIA,
SYSFS{prod_id2}==Bluetooth Card, RUN+=/lib/udev/bluetooth.sh $sysfs{manf_id}
$sysfs{card_id}
#
# dtl1_cs
#
# card Nokia Bluetooth Card
SUBSYSTEM==tty, BUS==pcmcia, SYSFS{prod_id1}==Nokia Mobile Phones,
SYSFS{prod_id2}==DTL-1, RUN+=/lib/udev/bluetooth.sh $sysfs{manf_id}
$sysfs{card_id}
SUBSYSTEM==tty, BUS==pcmcia, SYSFS{prod_id1}==Nokia Mobile Phones,
SYSFS{prod_id2}==DTL-4, RUN+=/lib/udev/bluetooth.sh $sysfs{manf_id}
$sysfs{card_id}
# Socket Bluetooth Card
SUBSYSTEM==tty, BUS==pcmcia, SYSFS{prod_id1}==Socket,
SYSFS{prod_id2}==CF+ Personal Network Card, RUN+=/lib/udev/bluetooth.sh
$sysfs{manf_id} $sysfs{card_id}
#
# bt3c_cs
#
# 3Com Bluetooth PC Card
SUBSYSTEM==tty, BUS==pcmcia, SYSFS{prod_id1}==3COM,
SYSFS{prod_id3}==Bluetooth PC Card, RUN+=/lib/udev/bluetooth.sh
$sysfs{manf_id} $sysfs{card_id}
#
# bluecard_cs
#
# LSE041 Bluetooth PC Card
SUBSYSTEM==tty, BUS==pcmcia, SYSFS{prod_id1}==BlueCard,
SYSFS{prod_id2}==LSE041, RUN+=/lib/udev/bluetooth.sh $sysfs{manf_id}
$sysfs{card_id}
# LSE039 Bluetooth Compact Flash Card
SUBSYSTEM==tty, BUS==pcmcia, SYSFS{prod_id1}==WSS,
SYSFS{prod_id2}==LSE039, RUN+=/lib/udev/bluetooth.sh $sysfs{manf_id}
$sysfs{card_id}
# LSE139 Bluetooth Compact Flash Card
SUBSYSTEM==tty, BUS==pcmcia, SYSFS{prod_id1}==BTCFCARD,
SYSFS{prod_id2}==LSE139, RUN+=/lib/udev/bluetooth.sh $sysfs{manf_id}
$sysfs{card_id}
#
# bt950_cs
#
# AmbiCom BT2000E Bluetooth Card
SUBSYSTEM==tty, BUS==pcmcia, SYSFS{prod_id1}==AmbiCom,Inc,
SYSFS{prod_id2}==BT2000E, RUN+=/lib/udev/bluetooth.sh $sysfs{manf_id}
$sysfs{card_id}
# Pretec BT2000E Bluetooth Card
SUBSYSTEM==tty, BUS==pcmcia, SYSFS{prod_id1}==Pretec,
SYSFS{prod_id2}==BT2000E, RUN+=/lib/udev/bluetooth.sh $sysfs{manf_id}
$sysfs{card_id}
# Billionton Bluetooth Card
SUBSYSTEM==tty, BUS==pcmcia, SYSFS{prod_id1}==Compact Flash,
SYSFS{prod_id2}==Bluetooth Card, RUN+=/lib/udev/bluetooth.sh $sysfs{manf_id}
$sysfs{card_id}
#
# btuart_cs
#
# Cyber-blue Compact Flash Card
SUBSYSTEM==tty, BUS==pcmcia, SYSFS{prod_id1}==BT, SYSFS{prod_id2}==,
SYSFS{prod_id3}==, SYSFS{prod_id4}==, RUN+=/lib/udev/bluetooth.sh
$sysfs{manf_id} $sysfs{card_id}
bluetooth.sh
Description: application/shellscript
Bug#378839: [Pkg-bluetooth-maintainers] Bug#378839: bluez-pcmcia-support: udev support broken
On Tuesday 25 July 2006 17:12, Marcel Holtmann wrote: this is nice, but there is no need to run bluetooth.sh on non-serial based Bluetooth cards like the Nokia DTL1 for example. They work perfectly fine without any additional udev rule. The rules are essentially taken from SuSE, I don't know where they got them from. I also don't like that bluetooth.sh tries to run /etc/init.d/bluetooth, because this should not be a task of an udev script. Either Bluetooth is enabled to be started a system boot or not. Agreed! The other thing is that this is not Debian specific. So why does nobody tried to start an upstream discussion on bluez-devel or linux-hotplug mailing list. Very good point!!! Kind regards, Felix -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#378839: [Pkg-bluetooth-maintainers] Bug#378839: bluez-pcmcia-support: udev support broken
On Wednesday 19 July 2006 12:00, Filippo Giunchedi wrote:
[I'm CCing udev maintainer to have some comments (if any)]
On Wed, Jul 19, 2006 at 10:57:04AM +0200, [EMAIL PROTECTED] wrote:
The udev rules supplied by the package don't work. At least on my
system tested with a SPHINX and a Sitecom card.
The solution is to replace ENV{BUS} by ENV{PHYSDEVBUS} in
bluez-pcmcia-support.udev and to correspondingly change $DEVPATH to
$PHYSDEVPATH in bluetooth.sh, i. e. revert to the solution I sent in
#351106.
Marco: comments on this? will this solution work for all cases in your
opinion?
Just one further comment: The solution is propose is not my own invention.
It's what SuSE has been doing for a long time. (I already mentioned this in
#351106.)
Kind regards,
Felix
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#365613: wpasupplicant: Upgrading remote system makes it unmaintainable after reboot
Package: wpasupplicant Version: 0.4.8-4 Severity: critical Justification: breaks the whole system I tried upgrading wpasupplicant from 0.4.7-4 to 0.4.8-4 on a remote system that is connected to the network via a WPA connection using wpa_supplicant. The system is a server only system: It does not have a video card or keyboard but is maintained via SSH. After upgrading everything seemed to work as usual until reboot. After reboot the system could not connect to the network anymore and was therefore unmaintainable. Reason: /etc/wpa_suplicant.conf was renamed without warning. Solution: Don't rename /etc/wpa_supplicant.conf on upgrade. Kind regards, Felix -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
