Bug#693190: linux-image-3.2.0-4-amd: [regression] Samsung series 9 backlit stopped working in 320-4 kernel
Package: src:linux Version: 3.2.32-1 Severity: important File: linux-image-3.2.0-4-amd Dear Maintainer, I recently did an apt-get upgrade and upgrade from linux-image 320-3 to 320-4 in this update my backlight adjustment stopped working. It is impossible to use software (kde) or keyboard shortcuts to adjust the backlight. The backlight is perpetually at max now. I rebooted and used grub to book the old kernel and confirmed that backlight adjustment works properly in the debian v3 kernel. The main difference between the kernels in dmesg is that in the broken kernel this line becomes visible; [3.708272] samsung_laptop: enabled workaround for brightness stepping quirk Other possibly relevant line from dmesg; [0.00] DMI: SAMSUNG ELECTRONICS CO., LTD. 900X3C/900X4C/900X4D/SAMSUNG_NP1234567890, BIOS P00AAC 04/03/2012 and as mentioned this is a samsung series 9 laptop (a couple of months old) Also possibly relevant info is that other keyboard shortcuts still work, things like adjusting the sound level or enable/disable the touch-pad. -- Package-specific info: ** Version: Linux version 3.2.0-4-amd64 (debian-ker...@lists.debian.org) (gcc version 4.6.3 (Debian 4.6.3-12) ) #1 SMP Debian 3.2.32-1 ** Command line: BOOT_IMAGE=/boot/vmlinuz-3.2.0-4-amd64 root=UUID=02a4fc3d-25c8-4e18-9f98-f888d7107d4c ro quiet ** Not tainted ** Kernel log: [3.701416] iTCO_wdt: Found a Panther Point TCO device (Version=2, TCOBASE=0x0460) [3.701482] iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0) [3.701523] input: PC Speaker as /devices/platform/pcspkr/input/input5 [3.708272] samsung_laptop: enabled workaround for brightness stepping quirk [3.715133] Bluetooth: Core ver 2.16 [3.715151] NET: Registered protocol family 31 [3.715154] Bluetooth: HCI device and connection manager initialized [3.715157] Bluetooth: HCI socket layer initialized [3.715159] Bluetooth: L2CAP socket layer initialized [3.715164] Bluetooth: SCO socket layer initialized [3.725296] Bluetooth: Generic Bluetooth USB driver ver 0.6 [3.725446] usbcore: registered new interface driver btusb [3.728633] i915 :00:02.0: setting latency timer to 64 [3.739042] cfg80211: Calling CRDA to update world regulatory domain [3.780218] Intel(R) Wireless WiFi Link AGN driver for Linux, in-tree: [3.780221] Copyright(c) 2003-2011 Intel Corporation [3.780418] iwlwifi :01:00.0: setting latency timer to 64 [3.780467] iwlwifi :01:00.0: pci_resource_len = 0x2000 [3.780470] iwlwifi :01:00.0: pci_resource_base = c967c000 [3.780472] iwlwifi :01:00.0: HW Revision ID = 0x24 [3.781558] i915 :00:02.0: irq 48 for MSI/MSI-X [3.781566] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010). [3.781568] [drm] Driver supports precise vblank timestamp query. [3.781950] vgaarb: device changed decodes: PCI::00:02.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem [3.783874] iwlwifi :01:00.0: irq 47 for MSI/MSI-X [3.783975] iwlwifi :01:00.0: Detected 6035 Series 2x2 AGN/BT, REV=0xB0 [3.784091] iwlwifi :01:00.0: L1 Enabled; Disabling L0S [3.787506] alg: No test for __gcm-aes-aesni (__driver-gcm-aes-aesni) [3.800325] iwlwifi :01:00.0: device EEPROM VER=0x756, CALIB=0x6 [3.800329] iwlwifi :01:00.0: Device SKU: 0X1f0 [3.800332] iwlwifi :01:00.0: Valid Tx ant: 0X3, Valid Rx ant: 0X3 [3.800647] iwlwifi :01:00.0: Tunable channels: 13 802.11bg, 24 802.11a channels [3.828302] iwlwifi :01:00.0: loaded firmware version 18.168.6.1 [3.828542] Registered led device: phy0-led [3.832805] ieee80211 phy0: Selected rate control algorithm 'iwl-agn-rs' [3.842576] cfg80211: World regulatory domain updated: [3.842578] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp) [3.842581] cfg80211: (2402000 KHz - 2472000 KHz @ 4 KHz), (300 mBi, 2000 mBm) [3.842583] cfg80211: (2457000 KHz - 2482000 KHz @ 2 KHz), (300 mBi, 2000 mBm) [3.842585] cfg80211: (2474000 KHz - 2494000 KHz @ 2 KHz), (300 mBi, 2000 mBm) [3.842587] cfg80211: (517 KHz - 525 KHz @ 4 KHz), (300 mBi, 2000 mBm) [3.842589] cfg80211: (5735000 KHz - 5835000 KHz @ 4 KHz), (300 mBi, 2000 mBm) [3.861241] Linux media interface: v0.10 [3.870009] Linux video capture interface: v2.00 [3.872232] uvcvideo: Found UVC 1.00 device Webcam SC-13HDL11624N (2232:1024) [3.955682] input: Webcam SC-13HDL11624N as /devices/pci:00/:00:1d.0/usb1/1-1/1-1.6/1-1.6:1.0/input/input6 [3.956025] usbcore: registered new interface driver uvcvideo [3.956040] USB Video Class driver (1.1.1) [3.991878] psmouse serio1: elantech: assuming hardware version 4 (with firmware version 0x361f03) [4.028907] psmouse serio1: elantech: Synaptics capabilities query result 0x40, 0x14, 0x0d. [4.111771] input: ETPS/2 Elantech Touchpad
Bug#660120: wvdial doesn't work on armel / armhf platforms
Hello Hector, tested on wheezy today. Seems to solve the wvdial problem! Regards Riggs -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#514880: missing plugins
Package: qca2-plugin-ossl Version: 0.1~20070904-3 I expected the qca2 plugins for blowfish and pbkdf2 to be shipped by debian but it seems they are not. Could you please package+ship those? In the koffice sourcefile; libs/store/KoEncryptedStore.cpp we detect the QCA2 plugins; QCA::isSupported(sha1) QCA::isSupported(pbkdf2(sha1)) QCA::isSupported(blowfish-cfb); The first one returns true on my system, the others return false. The KOffice2 package will have to depend on these plugins if qca2 support will be useful to it at all to it, so it would be nice to get them packaged. dzan...@jotun:kde$dpkg -l *qca2* ||/ Name Version +++-= ii libqca2 2.0.0-4 ii libqca2-dev 2.0.0-4 un libqca2-doc none un libqca2-plugin-cyrus-sasl none un libqca2-plugin-gnupg none ii libqca2-plugin-ossl 0.1~20070904-3 un libqca2-plugin-pkcs11 none -- Thomas Zander -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#513810: hibernate: MacBook hangs after Suspending console(s)
Package: hibernate Version: 1.99-1 Severity: critical Justification: causes serious data loss either suspending to ram or to disk fails and hangs the machine. I have a MacBook 2 (white) with 2.6.26-1-686 cleanly installed (Lenny) just last week. When I call either suspend or hibernate it switches to a text console and prints a couple of lines the last one being the Suspending console(s). Googling shows this is a kernel bug, not sure if that means I should have reported here or to another package. Please reassign if needed. Thanks. -- Package-specific info: --- configuration == /etc/hibernate/common.conf == Verbosity 0 LogFile /var/log/hibernate.log LogVerbosity 1 Distribution debian SaveClock restore-only UnloadBlacklistedModules yes LoadModules auto SwitchToTextMode yes == /etc/hibernate/disk.conf == TryMethod ususpend-disk.conf TryMethod sysfs-disk.conf == /etc/hibernate/hibernate.conf == TryMethod suspend2.conf TryMethod disk.conf TryMethod ram.conf == /etc/hibernate/ram.conf == TryMethod ususpend-ram.conf TryMethod sysfs-ram.conf == /etc/hibernate/suspend2.conf == UseSuspend2 yes Reboot no EnableEscape yes DefaultConsoleLevel 1 Compressor lzf Encryptor none FullSpeedCPU yes Include common.conf == /etc/hibernate/sysfs-disk.conf == UseSysfsPowerState disk Include common.conf == /etc/hibernate/sysfs-ram.conf == UseSysfsPowerState mem Include common.conf == /etc/hibernate/ususpend-both.conf == USuspendMethod both Include common.conf == /etc/hibernate/ususpend-disk.conf == USuspendMethod disk Include common.conf == /etc/hibernate/ususpend-ram.conf == USuspendMethod ram Include common.conf --- /sys/power == /sys/power/disk == [platform] test testproc shutdown reboot == /sys/power/image_size == 524288000 == /sys/power/resume == 8:6 == /sys/power/state == mem disk --- log no hibernate.log file found. -- System Information: Debian Release: 5.0 APT prefers testing APT policy: (850, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.26-1-686 (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/bash Versions of packages hibernate depends on: ii console-tools1:0.2.3dbs-65.1 Linux console and font utilities Versions of packages hibernate recommends: pn dash none (no description available) ii hdparm8.9-3 tune hard disk parameters for high pn uswsusp none (no description available) ii vbetool 1.0-3 run real-mode video BIOS code to a Versions of packages hibernate suggests: pn 915resolution none (no description available) ii kscreensaver 4:3.5.9-3 additional screen savers released -- no debconf information -- Thomas Zander -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#474200: iwlwifi hang
On Wednesday 24. December 2008 23.14.26 Matt Taggart wrote: Hi Thomas, The firmware versions that you mentioned having problems with in #474200 are pretty old, the current firmware-iwlwifi package has much newer. Can you try it and let us know if you still see the problem? well, the bug report is also very old ;) how can reporters close bugs that are no longer valid? Is there any howto on that? ps. didn't I ask to close this report already ? -- Thomas Zander -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#493880: xfonts-100dpi: Helvetica from this package is reported by fc-match to beantialiased
On Wednesday 6. August 2008 10:17:44 Brice Goglin wrote: tags 493880 moreinfo unreproducible thank you On Tue, Aug 05, 2008 at 08:02:54PM +0200, Thomas Zander wrote: 1) make sure you have the package installed. $ dpkg -s xfonts-100dpi Package: xfonts-100dpi Status: install ok installed [...] Version: 1:1.0.0-4 Judging by this line you pasted; file: /usr/share/fonts/X11/75dpi/helvR12.pcf.gz(s) you also have the 75 dpi fonts package installed (xfonts-75dpi) and fontconfig returns that result before the one this report is about. Please deinstall the 75dpi package and run the line again; 2) run fc-match -v helvetica | grep antialias Thanks. ps. this report is based on a clean installed lenny. Just installed it from a netinstall a few days ago. And I didn't change any relevant config files. -- Thomas Zander -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#493880: xfonts-100dpi: Helvetica from this package is reported by fc-match to beantialiased
Package: xfonts-100dpi Version: 1:1.0.0-4 Severity: normal To reproduce type; fc-match -v helvetica | grep antialias If you get 'FcTrue(w)' then you see the problem as a bitmap font can never be antialiased. The direct effect is that Qt4 applications (including KWord2) choose this font based on this variable even when it requests an antialised font (the standard). The effect is that installing this package will make many applications look quite ugly. -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (850, 'testing'), (800, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.25-2-686 (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/bash Versions of packages xfonts-100dpi depends on: ii xfonts-utils 1:7.4+1X Window System font utility progr xfonts-100dpi recommends no packages. Versions of packages xfonts-100dpi suggests: ii xserver-xorg-core [xserver] 2:1.4.2-2 Xorg X server - core server -- no debconf information -- Thomas Zander -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#493880: xfonts-100dpi: Helvetica from this package is reported by fc-match to beantialiased
On Tuesday 5. August 2008 19:49:01 Julien Cristau wrote: On Tue, Aug 5, 2008 at 19:13:10 +0200, Thomas Zander wrote: To reproduce type; fc-match -v helvetica | grep antialias If you get 'FcTrue(w)' then you see the problem as a bitmap font can never be antialiased. And if I don't? Please be more specific. fc-match -s -v helvetica |grep file doesn't seem to list anything from xfonts-100dpi here. What file are you talking about? not grep file, thats not what I wrote. 1) make sure you have the package installed. 2) run fc-match -v helvetica | grep antialias 3) check output. Your output should either be; antialias: FcTrue(w) or it is different. If it is the FcTrue one, then fontconfig is reporting the bitmap font to be antialiased. Something that is impossible for a bitmap font so the font is announced to fontconfig incorrectly. Just FYI; here is the full output of fc-match (without the limiting grep) $fc-match -v Helvetica Pattern has 27 elts (size 32) family: Helvetica(s) style: Regular(s) slant: 0(i)(s) weight: 80(i)(s) width: 100(i)(s) size: 12(f)(s) pixelsize: 11(f)(s) foundry: Adobe(s) antialias: FcTrue(w) hintstyle: 1(i)(w) hinting: FcTrue(w) verticallayout: FcFalse(s) autohint: FcFalse(s) globaladvance: FcTrue(s) file: /usr/share/fonts/X11/100dpi/helvR08.pcf.gz(s) index: 0(i)(s) outline: FcFalse(s) scalable: FcFalse(s) dpi: 75(f)(s) rgba: 1(i)(w) scale: 1(f)(s) charset: : 0001 7fff 0001: 7fff a4844240 1861c183 e00d ff313fff 0002: cfff 000fffc0 8311 02200020 40007380 3800 3f00efc0 4000 0003: 4000 00b0 1000 001e: 03ff f3f3fcf3 3fcf3cf3 033fcf3f 0020: ff3f0fff 06010047 0010 000e 3260 0021: 0208 00040c04 0022: 02240019 0040 0600 0003c037 (s) lang: aa|af|ast|ay|bi|br|bs|ca|ch|co|cs|cy|da|de|en|eo|es|et|eu|fi|fj|fo|fr|fur|fy|ga|gd|gl|gn|gv|haw|ho|hr|hu|ia|ibo|id|ie|io|is|it|ki| kl|kw|la|lb|lt|lv|mg|mh|mi|mt|nb|nds|nl|nn|no|nr|nso|ny|oc|om|pl|pt|rm|ro|se|sk|sl|sm|sma|smj|smn|so|sq|ss|st|sv|sw|tn|to|tr|ts|ven| vo|vot|wa|wen|wo|xh|yap|zu(s) fontversion: 0(i)(s) fontformat: PCF(s) embeddedbitmap: FcTrue(s) decorative: FcFalse(s) -- Thomas Zander -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#478798: network-manager-kde: logging in will go into offline mode
Subject: network-manager-kde: logging in will go into offline mode Package: network-manager-kde Version: 1:0.2.2-1 Severity: serious Justification: unsure *** Please type your report below this line *** Knetwork manager turns off my wifi connection on login. I found two usecases where this happens; * I logout (wifi keeps on working) * I re-login (wifi is take offline) And the second usecase; * I use Start New Session to login a second time and as soon as I do my wifi is taken offline. (knetwork manager even turns to 'offline mode') -- 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/2 CPU cores) 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 network-manager-kde depends on: ii kdelibs4c2a 4:3.5.9.dfsg.1-2+b1 core libraries and binaries for al ii libc62.7-10 GNU C Library: Shared libraries ii libdbus-1-3 1.2.1-1 simple interprocess messaging syst ii libdbus-qt-1-1c2 0.62.git.20060814-2 simple interprocess messaging syst ii libgcc1 1:4.3.0-3 GCC support library ii libhal1 0.5.11~rc2-1Hardware Abstraction Layer - share ii libice6 2:1.0.4-1 X11 Inter-Client Exchange library ii libnl1 1.1-2 library for dealing with netlink s ii libnm-util0 0.6.6-1 network management framework (shar ii libpng12-0 1.2.15~beta5-3 PNG library - runtime ii libqt3-mt3:3.3.8b-5 Qt GUI Library (Threaded runtime v ii libsm6 2:1.0.3-1+b1X11 Session Management library ii libstdc++6 4.3.0-3 The GNU Standard C++ Library v3 ii libx11-6 2:1.0.3-7 X11 client-side library ii libxext6 2:1.0.4-1 X11 miscellaneous extension librar ii network-manager 0.6.6-1 network management framework daemo ii zlib1g 1:1.2.3.3.dfsg-12 compression library - runtime Versions of packages network-manager-kde recommends: ii kwalletmanager4:3.5.9-1 wallet manager for KDE ii network-manager-openvpn 0.3.2svn2855-1 network management framework (Open ii network-manager-vpnc 0.6.4svn2806-1 network management framework (VPNC -- no debconf information -- Thomas Zander -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#474201: KPowersave doesn't suspend/hibernate
On Monday 28. April 2008 02:34:15 Michael Biebl wrote: Can you really reproduce the problem by creating a file ~/.dbus? My guess is that with a .dbus file present apps that start later can't find the running daemon. Maybe it was a missing dbus-x11 package. Did you have this package installed, when you noticed the problem, do you have it installed now? I had that installed before, and still do. -- Thomas Zander signature.asc Description: This is a digitally signed message part.
Bug#474201: KPowersave doesn't suspend/hibernate
On Thursday 24. April 2008 07:12:13 Michael Biebl wrote: Thomas Zander wrote: Would it be an idea to add an rm -f $HOME/.dbus before the try to create a Yes, please remove the ~/.dbus file. There is no need though to create the directory manually in a boot script. dbus-daemon will do that automatically. Ok, let me rephrase my question as my intend apparently didn't come across. I think its a bug [somewhere] that the dbus daemon silently fails when the user has a .dbus file in his homedir. I think this bug should be fixed by deleting that file either in the startup sequence or in the dbus daemon itself. Do you have any suggestions where that could be done? If so, please rename and reassign this task to the appropriate package. -- Thomas Zander signature.asc Description: This is a digitally signed message part.
Bug#474201: KPowersave doesn't suspend/hibernate
On Thursday 10. April 2008 23:46:55 you wrote: please run hald in debug mode (hald --daemon=no --verbose=yes) and attach the output to the bug report. ok. The log doesn't seem to contain a suspend attempt. Could you only send me the relevant log output when you do the suspend attempt. That attempt is at the very end, I indeed saw no reaction in the hal log. I did more digging here, as I am not convinced that searching outside of kpowersave is relevant. [reading .xsession-errors] this is an interresting line; Xsession: X session started for zander at Tue Apr 8 23:01:27 CEST 2008 Unable to create /home/zander/.dbus/session-bus The reason, I found, is that somehow I got a .dbus FILE in my homedir. So obviously the dir could not be created. I bet that file got restored from the backup from another system. Would it be an idea to add an rm -f $HOME/.dbus before the try to create a dir (in the boot scripts)? -- Thomas Zander signature.asc Description: This is a digitally signed message part.
Bug#474201: KPowersave doesn't suspend/hibernate
On Friday 4. April 2008 09:01:29 Michael Biebl wrote: When using the kpowersave systray item I can select to either suspend to disk or suspend to ram. Unfortunately nothing happens when I click either. Well, my screen locks, but nothing more happens. When I type s2ram or s2disk, or even hibernate (all as root) my laptop does get suspended correctly. Which leads me to believe that kpowersave doesn't work together with other debian packages properly. Hi Thomas, your bug report is missing vital information: kernel version, architecture, versions of dependend packages like hal and pm-utils. I can only suggest that you use reportbug (or reportbug-ng) for future bug reports. If only reportbug was intelligent enough to find out that I have exim setup to never do mail and propose to save a file instead... (or start kmail or so) I.e. I tried, but no bug actually gets reported if I use it. Anyway, sorry for not providing more info; I am using 'lenny' Linux lacuna 2.6.24-1-686 #1 SMP Mon Feb 11 14:37:45 UTC 2008 i686 GNU/Linux Just guessing out of the blue: Is your user in group powerdev? No, its not. Which package should I file a bug against to make sure the default (i.e. created in the installer), only non-root user gets auto-added to that group? If not, please add your user to group plugdev and reload dbus (/etc/init.d/dbus force-reload). If that doesn't help, It didn't. I rebooted my machine in the meantime (and promptly forgot I had this mail in my drafts box, thanks for the reminder!) Still no luck. please run hald in debug mode (hald --daemon=no --verbose=yes) and attach the output to the bug report. ok. -- Thomas Zander hald.out.bz2 Description: BZip2 compressed data signature.asc Description: This is a digitally signed message part.
Bug#474200: irmware-iwlwifi: firmware sometimes hangs machine, upgrade needed
On Monday 7. April 2008 21:22:32 Bastian Blank wrote: On Mon, Apr 07, 2008 at 08:20:52PM +0200, Thomas Zander wrote: The versions includes (2.14.1.5 and 4.44.1.20) are the newest. Not sure how they number; but .4 seems higher than .1.5 to me... http://intellinuxwireless.org/iwlwifi/downloads/iwlwifi-3945-ucode-2.14.4 .tgz I used this link and it has helped alleviate crashes and freezes. Its far from perfect, but its better than the previous version. This are different variants of the firmware. Ok, then change the bugreport to firmware variant shipped in debian freezes system, use the above URL since that one doesn't freeze my machine... Or similar. Anyway, feel free to close this report, I reported the freezes and other problems with the shipped version and suggested a working version. Take that as you will :) -- Thomas Zander -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#474200: irmware-iwlwifi: firmware sometimes hangs machine, upgrade needed
On Friday 4. April 2008 12:19:54 Bastian Blank wrote: I went to the intel website and downloaded the newest firmware. A week later I have not seen any of the above problems anymore. Please consider upgrading the firmware in debian to the latest released. The versions includes (2.14.1.5 and 4.44.1.20) are the newest. Not sure how they number; but .4 seems higher than .1.5 to me... http://intellinuxwireless.org/iwlwifi/downloads/iwlwifi-3945-ucode-2.14.4.tgz I used this link and it has helped alleviate crashes and freezes. Its far from perfect, but its better than the previous version. -- Thomas Zander -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#474201: KPowersave doesn't suspend/hibernate
Package: kpowersave Version:0.7.3-1 Severity: important When using the kpowersave systray item I can select to either suspend to disk or suspend to ram. Unfortunately nothing happens when I click either. Well, my screen locks, but nothing more happens. When I type s2ram or s2disk, or even hibernate (all as root) my laptop does get suspended correctly. Which leads me to believe that kpowersave doesn't work together with other debian packages properly. -- Thomas Zander -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#474200: irmware-iwlwifi: firmware sometimes hangs machine, upgrade needed
Package: firmware-iwlwifi Version: 0.10 Severity: grave Justification: causes non-serious data loss The current version made my machine hang after heavy network use. It also refused to properly unload/reload upon hibernate (to disk) causing me to loose my wifi until I rebooted. I went to the intel website and downloaded the newest firmware. A week later I have not seen any of the above problems anymore. Please consider upgrading the firmware in debian to the latest released. -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Machine: Toshiba Techra A8 Kernel: Linux 2.6.24-1-686 (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/bash -- no debconf information -- Thomas Zander -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#386869: gs-gpl: Crash with Floating point exception on pdf
Subject: gs-gpl: Crash with Floating point exception on pdf Package: gs-gpl Version: 8.50-1.1 Severity: normal In a PDF I have (written by Qt4.2) I see the following: # gs output.pdf GPL Ghostscript 8.50 (2005-12-31) Copyright (C) 2005 artofcode LLC, Benicia, CA. All rights reserved. This software comes with NO WARRANTY: see the file PUBLIC for details. Warning: Color name white is not defined Warning: Color name black is not defined Processing pages 1 through 3. Page 1 Floating point exception # -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.17.6pavilion Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Versions of packages gs-gpl depends on: ii gs-common 0.3.9 Common files for different Ghostsc ii libc6 2.3.6-15 GNU C Library: Shared libraries ii libice6 1:1.0.0-3 X11 Inter-Client Exchange library ii libpaper1 1.1.19 Library for handling paper charact ii libsm61:1.0.0-4 X11 Session Management library ii libx11-6 2:1.0.0-7 X11 client-side library ii libxext6 1:1.0.0-4 X11 miscellaneous extension librar ii libxt61:1.0.0-5 X11 toolkit intrinsics library Versions of packages gs-gpl recommends: ii gsfonts 8.14+v8.11+urw-0.2 Fonts for the Ghostscript interpre pn psfontmgr none (no description available) -- no debconf information output.pdf Description: Adobe PDF document
Bug#380513: openoffice.org-writer: 2.0.3 has wrong colors and misses text in anchored frames
Subject: openoffice.org-writer: 2.0.3 has wrong colors and misses text in anchored frames Package: openoffice.org-writer Version: 2.0.3-3 Severity: grave Justification: causes non-serious data loss In upgrading from 2.0.2 to 2.0.3 I found that writer stopped being able to display anchored frames correctly. My ODT document suddenly had the background color turned from red to blue and all my variables (page number/etc) were missing after opening. Printing has the same bugs as on screen info. This is a REGRESSION. -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (x86_64) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.17.6pavilion Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Versions of packages openoffice.org-writer depends on: ii libc6 2.3.6-15 GNU C Library: Shared libraries ii libgcc1 1:4.1.1-8 GCC support library ii libicu34 3.4.1a-1 International Components for Unico ii libstdc++64.1.1-8The GNU Standard C++ Library v3 ii libstlport4.6c2 4.6.2-3STLport C++ class library ii libwpd8c2a0.8.6-1Library for handling WordPerfect d ii openoffice.org-core 2.0.3-3OpenOffice.org office suite archit ii zlib1g1:1.2.3-13 compression library - runtime Versions of packages openoffice.org-writer recommends: pn java-gcj-compat | j2re1.4 | j none (no description available) pn openoffice.org-java-commonnone (no description available) -- no debconf information -- Thomas Zander -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#380513: openoffice.org-writer: 2.0.3 has wrong colors and misses text in anchored frames
On Sunday 30 July 2006 19:35, Rene Engelhard wrote: Thomas Zander wrote: Severity: grave Justification: causes non-serious data loss Wow. And it is grave because _some_ feature doesn't work anymore. Come on... Anchored frames are a basic thing and lots of documents depend on them. If pages stopped working, then thats a grave bug, no? This is only slightly less so. In upgrading from 2.0.2 to 2.0.3 I found that writer stopped being able to And if you mean 2.0.2 - 2.0.3 upgrade, did it also happen in 2.0.3-2? Why are you reporting it against 2.0.3-3 then? It also happened in 2.0.3-2 and I used reportbug only today (as I wanted to upgrade first, see if the problem went away) display anchored frames correctly. My ODT document suddenly had the background color turned from red to blue and all my variables (page number/etc) were missing after opening. Printing has the same bugs as on screen info. This is a REGRESSION. And you don't need to scream. Nah; not screeming; just a poor mans way of making a custom tag. :-) Have a sample document? Sure. I'll attach it. -- Thomas Zander colorful.odt Description: application/vnd.oasis.opendocument.text
Bug#378998: cmake: Dependency broken; please not recommend or require emacs
Package: cmake Severity: normal cmake requires emacsen-common and recommends emacs21 xemacs21 emacsen These are all totally not needed for this tool. I compiled the sources myself and found no such requirement at all. -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.17.6pavilion Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) -- Thomas Zander -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#378998: possible fix
I just noted bug #34 A simple shellscript checking for the availability of dh_installemacsen would have sufficed. -- Thomas Zander -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#344291: libapt-front-dev: depends on missing libtagcoll-dev
Package: libapt-front-dev Severity: grave Justification: renders package unusable doing an install I get; The following packages have unmet dependencies: libapt-front-dev: Depends: libtagcoll-dev (= 1.5) but it is not installable Depends: libtagcoll-dev ( 1.6) but it is not installable The libtagcoll-dev package is (currently) unavailable for the amd64 architecture. -- System Information: Debian Release: testing APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.13.2 Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#344291: libapt-front-dev: depends on missing libtagcoll-dev
Oh, sorry for incorrectly concluding it must be a problem with the libapt. You state that it must be a problem with the amd64 archive, which I'm sorry to say does not mean much to me. Can you please advice where I should open a bugreport so this issue is correctly registered? Thanks On Wednesday 21 December 2005 18:46, you wrote: On Wed, Dec 21, 2005 at 05:00:20PM +0100, Thomas Zander wrote: Package: libapt-front-dev Severity: grave Justification: renders package unusable doing an install I get; The following packages have unmet dependencies: libapt-front-dev: Depends: libtagcoll-dev (= 1.5) but it is not installable Depends: libtagcoll-dev ( 1.6) but it is not installable The libtagcoll-dev package is (currently) unavailable for the amd64 architecture. Then how was libapt-front-dev built? Package: libapt-front Binary: libapt-front-dev Build-Depends: cdbs, debhelper ( 4.1), dh-buildinfo, doxygen, libtool, libapt-pkg-dev, libtagcoll-dev (= 1.5), libtagcoll-dev ( 1.6), pkg-config This looks like a problem with the amd64 archive, not with the libapt-front-dev package. -- Thomas Zander -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
