[Bug 604497] Re: Evolution doesn't provide GNOME Pilot (Palm) conduits anymore in Maverick
Pedro: "Talked with the desktop team and they say this is not something they're looking to fix since gnome-pilot is quite old and unmaintained upstream, that's why the support was removed from Debian and thus Ubuntu. " I checked at http://live.gnome.org/GnomePilot, gnome-pilot looks quite active, currently preparing for Gnome and thus Evolution 3. Under "Work currently being done" it says "Incorporation of the evolution conduits into the gnome-pilot codebase. ". Thus 2.30 will be the ONLY version of Evolution, that does not have pilot support, because 3.0 will. This is a very ugly regression. And since it looks like we are just talking about a compiling-option, it's easy to fix. -- Evolution doesn't provide GNOME Pilot (Palm) conduits anymore in Maverick https://bugs.launchpad.net/bugs/604497 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 604497] Re: Evolution doesn't provide GNOME Pilot (Palm) conduits anymore in Maverick
just a me too, I still love my Palm TX, just 3 years old. It's my daily companion for contacts, tasks, notes, mail. Can I get the conduits from elsewhere? -- Evolution doesn't provide GNOME Pilot (Palm) conduits anymore in Maverick https://bugs.launchpad.net/bugs/604497 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 652700] Re: bug report after system start-up
** Attachment added: "BootDmesg.txt" https://bugs.launchpad.net/bugs/652700/+attachment/1661179/+files/BootDmesg.txt ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/652700/+attachment/1661180/+files/CurrentDmesg.txt ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/652700/+attachment/1661181/+files/Dependencies.txt ** Attachment added: "GdmLog.txt" https://bugs.launchpad.net/bugs/652700/+attachment/1661182/+files/GdmLog.txt ** Attachment added: "GdmLog1.txt" https://bugs.launchpad.net/bugs/652700/+attachment/1661183/+files/GdmLog1.txt ** Attachment added: "GdmLog2.txt" https://bugs.launchpad.net/bugs/652700/+attachment/1661184/+files/GdmLog2.txt ** Attachment added: "IntelGpuDump.txt" https://bugs.launchpad.net/bugs/652700/+attachment/1661185/+files/IntelGpuDump.txt ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/652700/+attachment/1661186/+files/Lspci.txt ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/652700/+attachment/1661187/+files/Lsusb.txt ** Attachment added: "PciDisplay.txt" https://bugs.launchpad.net/bugs/652700/+attachment/1661188/+files/PciDisplay.txt ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/652700/+attachment/1661189/+files/ProcCpuinfo.txt ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/652700/+attachment/1661190/+files/ProcInterrupts.txt ** Attachment added: "ProcMaps.txt" https://bugs.launchpad.net/bugs/652700/+attachment/1661191/+files/ProcMaps.txt ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/652700/+attachment/1661192/+files/ProcModules.txt ** Attachment added: "ProcStatus.txt" https://bugs.launchpad.net/bugs/652700/+attachment/1661193/+files/ProcStatus.txt ** Attachment added: "RelatedPackageVersions.txt" https://bugs.launchpad.net/bugs/652700/+attachment/1661194/+files/RelatedPackageVersions.txt ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/652700/+attachment/1661195/+files/UdevDb.txt ** Attachment added: "UdevLog.txt" https://bugs.launchpad.net/bugs/652700/+attachment/1661196/+files/UdevLog.txt ** Attachment added: "XorgLog.txt" https://bugs.launchpad.net/bugs/652700/+attachment/1661197/+files/XorgLog.txt ** Attachment added: "XorgLogOld.txt" https://bugs.launchpad.net/bugs/652700/+attachment/1661198/+files/XorgLogOld.txt ** Attachment added: "Xrandr.txt" https://bugs.launchpad.net/bugs/652700/+attachment/1661199/+files/Xrandr.txt ** Attachment added: "i915_error_state.txt" https://bugs.launchpad.net/bugs/652700/+attachment/1661200/+files/i915_error_state.txt ** Attachment added: "peripherals.txt" https://bugs.launchpad.net/bugs/652700/+attachment/1661201/+files/peripherals.txt ** Attachment added: "setxkbmap.txt" https://bugs.launchpad.net/bugs/652700/+attachment/1661202/+files/setxkbmap.txt ** Attachment added: "xdpyinfo.txt" https://bugs.launchpad.net/bugs/652700/+attachment/1661203/+files/xdpyinfo.txt ** Attachment added: "xkbcomp.txt" https://bugs.launchpad.net/bugs/652700/+attachment/1661204/+files/xkbcomp.txt -- bug report after system start-up https://bugs.launchpad.net/bugs/652700 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 652700] [NEW] bug report after system start-up
Public bug reported: Binary package hint: xserver-xorg-video-intel System start-up reports this bug. Gnome desktop edition on lenovo S10-3T netbook. ProblemType: Crash DistroRelease: Ubuntu 10.10 Package: xserver-xorg-video-intel 2:2.12.0-1ubuntu5 ProcVersionSignature: Ubuntu 2.6.35-22.33-generic 2.6.35.4 Uname: Linux 2.6.35-22-generic i686 NonfreeKernelModules: wl Architecture: i386 Chipset: IGDgm DRM.card0.LVDS.1: status: connected enabled: enabled dpms: On modes: 1024x600 edid-base64: AP///wAGr9IjAAATAQSQFg14Aitpl1dVlikhT1QBAQEBAQEBAQEBAQEBAQEBsBMAQEFYGSAYiDEA330YDwAg/gBBVU8KICAgICAgICAg/gBCMTAxQVcwMiBWMyAKALg= DRM.card0.VGA.1: status: disconnected enabled: disabled dpms: On modes: edid-base64: Date: Thu Sep 30 17:47:57 2010 DkmsStatus: bcmwl, 5.60.48.36+bdcom, 2.6.32-24-generic, i686: built bcmwl, 5.60.48.36+bdcom, 2.6.35-22-generic, i686: installed bcmwl, 5.60.48.36+bdcom, 2.6.35-21-generic, i686: installed DumpSignature: 61a54867 (PGTBL_ER: 0x0003) ExecutablePath: /usr/share/apport/apport-gpu-error-intel.py InstallationMedia: Ubuntu-Netbook 10.04 "Lucid Lynx" - Release i386 (20100429.4) InterpreterPath: /usr/bin/python2.6 MachineType: LENOVO INVALID ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-22-generic root=UUID=6d1ae729-592d-481e-bdb1-34185449d811 ro quiet splash ProcCmdline: /usr/bin/python /usr/share/apport/apport-gpu-error-intel.py ProcEnviron: SourcePackage: xserver-xorg-video-intel Title: [IGDgm] GPU lockup 61a54867 (PGTBL_ER: 0x0003) UserGroups: dmi.bios.date: 12/11/2009 dmi.bios.vendor: LENOVO dmi.bios.version: 24CN18WW dmi.board.name: Caucasus2 dmi.board.vendor: LENOVO dmi.board.version: Rev 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Lenovo dmi.chassis.version: Rev 1.0 dmi.modalias: dmi:bvnLENOVO:bvr24CN18WW:bd12/11/2009:svnLENOVO:pnINVALID:pvrLenovoIdeapadS10-3t:rvnLENOVO:rnCaucasus2:rvrRev1.0:cvnLenovo:ct10:cvrRev1.0: dmi.product.name: INVALID dmi.product.version: Lenovo Ideapad S10-3t dmi.sys.vendor: LENOVO glxinfo: Error: [Errno 2] No such file or directory system: distro: Ubuntu codename: maverick architecture: i686 kernel: 2.6.35-22-generic ** Affects: xserver-xorg-video-intel (Ubuntu) Importance: Undecided Status: New ** Tags: apport-crash freeze i386 maverick ubuntu-une -- bug report after system start-up https://bugs.launchpad.net/bugs/652700 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 647992] Re: Restart after "Ruhezustand" caused bug
** Attachment added: "BootDmesg.txt" https://bugs.launchpad.net/bugs/647992/+attachment/1638054/+files/BootDmesg.txt ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/647992/+attachment/1638055/+files/CurrentDmesg.txt ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/647992/+attachment/1638056/+files/Dependencies.txt ** Attachment added: "GdmLog.txt" https://bugs.launchpad.net/bugs/647992/+attachment/1638057/+files/GdmLog.txt ** Attachment added: "GdmLog1.txt" https://bugs.launchpad.net/bugs/647992/+attachment/1638058/+files/GdmLog1.txt ** Attachment added: "GdmLog2.txt" https://bugs.launchpad.net/bugs/647992/+attachment/1638059/+files/GdmLog2.txt ** Attachment added: "IntelGpuDump.txt" https://bugs.launchpad.net/bugs/647992/+attachment/1638060/+files/IntelGpuDump.txt ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/647992/+attachment/1638061/+files/Lspci.txt ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/647992/+attachment/1638062/+files/Lsusb.txt ** Attachment added: "PciDisplay.txt" https://bugs.launchpad.net/bugs/647992/+attachment/1638063/+files/PciDisplay.txt ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/647992/+attachment/1638064/+files/ProcCpuinfo.txt ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/647992/+attachment/1638065/+files/ProcInterrupts.txt ** Attachment added: "ProcMaps.txt" https://bugs.launchpad.net/bugs/647992/+attachment/1638066/+files/ProcMaps.txt ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/647992/+attachment/1638067/+files/ProcModules.txt ** Attachment added: "ProcStatus.txt" https://bugs.launchpad.net/bugs/647992/+attachment/1638068/+files/ProcStatus.txt ** Attachment added: "RelatedPackageVersions.txt" https://bugs.launchpad.net/bugs/647992/+attachment/1638069/+files/RelatedPackageVersions.txt ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/647992/+attachment/1638070/+files/UdevDb.txt ** Attachment added: "UdevLog.txt" https://bugs.launchpad.net/bugs/647992/+attachment/1638071/+files/UdevLog.txt ** Attachment added: "XorgLog.txt" https://bugs.launchpad.net/bugs/647992/+attachment/1638072/+files/XorgLog.txt ** Attachment added: "XorgLogOld.txt" https://bugs.launchpad.net/bugs/647992/+attachment/1638073/+files/XorgLogOld.txt ** Attachment added: "Xrandr.txt" https://bugs.launchpad.net/bugs/647992/+attachment/1638074/+files/Xrandr.txt ** Attachment added: "i915_error_state.txt" https://bugs.launchpad.net/bugs/647992/+attachment/1638075/+files/i915_error_state.txt ** Attachment added: "peripherals.txt" https://bugs.launchpad.net/bugs/647992/+attachment/1638076/+files/peripherals.txt ** Attachment added: "setxkbmap.txt" https://bugs.launchpad.net/bugs/647992/+attachment/1638077/+files/setxkbmap.txt ** Attachment added: "xdpyinfo.txt" https://bugs.launchpad.net/bugs/647992/+attachment/1638078/+files/xdpyinfo.txt ** Attachment added: "xkbcomp.txt" https://bugs.launchpad.net/bugs/647992/+attachment/1638079/+files/xkbcomp.txt -- Restart after "Ruhezustand" caused bug https://bugs.launchpad.net/bugs/647992 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 647992] [NEW] Restart after "Ruhezustand" caused bug
Public bug reported: Binary package hint: xserver-xorg-video-intel Ubuntu 10.10 beta Placed computer in "Ruhezustand", restarted, bug tracker informed about error, no visible issue so far ProblemType: Crash DistroRelease: Ubuntu 10.10 Package: xserver-xorg-video-intel 2:2.12.0-1ubuntu4 ProcVersionSignature: Ubuntu 2.6.35-22.33-generic 2.6.35.4 Uname: Linux 2.6.35-22-generic i686 NonfreeKernelModules: wl Architecture: i386 Chipset: IGDgm DRM.card0.LVDS.1: status: connected enabled: enabled dpms: On modes: 1024x600 edid-base64: AP///wAGr9IjAAATAQSQFg14Aitpl1dVlikhT1QBAQEBAQEBAQEBAQEBAQEBsBMAQEFYGSAYiDEA330YDwAg/gBBVU8KICAgICAgICAg/gBCMTAxQVcwMiBWMyAKALg= DRM.card0.VGA.1: status: disconnected enabled: disabled dpms: Off modes: edid-base64: Date: Sun Sep 26 11:26:53 2010 DkmsStatus: bcmwl, 5.60.48.36+bdcom, 2.6.32-24-generic, i686: built bcmwl, 5.60.48.36+bdcom, 2.6.35-22-generic, i686: installed bcmwl, 5.60.48.36+bdcom, 2.6.35-21-generic, i686: installed DumpSignature: 913d4854 (PGTBL_ER: 0x0003) ExecutablePath: /usr/share/apport/apport-gpu-error-intel.py InstallationMedia: Ubuntu-Netbook 10.04 "Lucid Lynx" - Release i386 (20100429.4) InterpreterPath: /usr/bin/python2.6 MachineType: LENOVO INVALID ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-22-generic root=UUID=6d1ae729-592d-481e-bdb1-34185449d811 ro quiet splash ProcCmdline: /usr/bin/python /usr/share/apport/apport-gpu-error-intel.py ProcEnviron: SourcePackage: xserver-xorg-video-intel Title: [IGDgm] GPU lockup 913d4854 (PGTBL_ER: 0x0003) UserGroups: dmi.bios.date: 12/11/2009 dmi.bios.vendor: LENOVO dmi.bios.version: 24CN18WW dmi.board.name: Caucasus2 dmi.board.vendor: LENOVO dmi.board.version: Rev 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Lenovo dmi.chassis.version: Rev 1.0 dmi.modalias: dmi:bvnLENOVO:bvr24CN18WW:bd12/11/2009:svnLENOVO:pnINVALID:pvrLenovoIdeapadS10-3t:rvnLENOVO:rnCaucasus2:rvrRev1.0:cvnLenovo:ct10:cvrRev1.0: dmi.product.name: INVALID dmi.product.version: Lenovo Ideapad S10-3t dmi.sys.vendor: LENOVO glxinfo: Error: [Errno 2] No such file or directory system: distro: Ubuntu codename: maverick architecture: i686 kernel: 2.6.35-22-generic ** Affects: xserver-xorg-video-intel (Ubuntu) Importance: Undecided Status: New ** Tags: apport-crash freeze i386 maverick ubuntu-une -- Restart after "Ruhezustand" caused bug https://bugs.launchpad.net/bugs/647992 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 366572] Re: Clam TK can't find virus definitions
Added "Hardy Backports" to make sure, the fix is backported to Hardy (LTS). ** Also affects: hardy-backports Importance: Undecided Status: New -- Clam TK can't find virus definitions https://bugs.launchpad.net/bugs/366572 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 366572] Re: Clam TK can't find virus definitions
The problem also exists in ClamTK 3.08 (Ubuntu Hardy LTS). ClamTK says "Signaturen 0 ()", but sudo freshclam ClamAV update process started at Thu May 21 13:08:11 2009 WARNING: Your ClamAV installation is OUTDATED! WARNING: Local version: 0.94.2 Recommended version: 0.95.1 DON'T PANIC! Read http://www.clamav.net/support/faq main.cld is up to date (version: 51, sigs: 545035, f-level: 42, builder: sven) daily.cld is ... Nevertheless, viruses are scanned and seem to be found (as TiKaey reports here: http://www.ubuntu-forum.de/post/263217/clamtk-zeigt-signaturen-0.html#post263217 Once the bug is fixed, please backport to Hardy. -- Clam TK can't find virus definitions https://bugs.launchpad.net/bugs/366572 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 275482] Re: Evolution crashes when editing "Tasks" Priority or Date from Summary Screen
Maybe my bug is the same as this. What I did: Create a new task with due date. Edit task by double-clicking on it. Change due date. Click save button Evolution crashes Version: Ubuntu 8.04.1 Evolution 2.22.3.1-0ubuntu1 -- Evolution crashes when editing "Tasks" Priority or Date from Summary Screen https://bugs.launchpad.net/bugs/275482 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 281956] Re: evolution uses wrong date to switch to daylight saving timezone in timezone Europe/Brussels
I also can conirm this issue in Hardy. System time is no 09:28, Evolution time line in calendar view is 08:28. I did not observe this some time ago, so I think it is related to a wrong switch date. Also an invitation I received for 18:00h was inserted in the calendar at 17:00h. Timezone: Europe/Berlin. -- evolution uses wrong date to switch to daylight saving timezone in timezone Europe/Brussels https://bugs.launchpad.net/bugs/281956 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 253073] Re: HAL does not update Gnome-Power-Manager with battery readings
try to run this command in a terminal: watch --interval=10 acpi -b While this is running, does g-p-m report the correct values? It is my current work around solution. But I have no clue, why this helps. -- HAL does not update Gnome-Power-Manager with battery readings https://bugs.launchpad.net/bugs/253073 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 253073] Re: HAL does not update Gnome-Power-Manager with battery readings
I am using the Hardy Heron Kernel, which is I think 2.6.24. I found 2 Linux bug fixes for a similar issue: http://bugzilla.kernel.org/show_bug.cgi?id=9730 and the linked: http://bugzilla.kernel.org/show_bug.cgi?id=9221 Unfortunately, they require recompiling the kernel, if I understood well, which is for beyond my IT knowledge. Could these fixes be inserted in the next Hardy Kernel update? ** Bug watch added: Linux Kernel Bug Tracker #9221 http://bugzilla.kernel.org/show_bug.cgi?id=9221 ** Also affects: linux via http://bugzilla.kernel.org/show_bug.cgi?id=9221 Importance: Unknown Status: Unknown -- HAL does not update Gnome-Power-Manager with battery readings https://bugs.launchpad.net/bugs/253073 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 253073] Re: HAL does not update Gnome-Power-Manager with battery readings
$ killall gnome-power-manager $ gnome-power-manager --verbose --no-daemon 2>&1 | tee gpm.debug.log.txt at the end of the log I added the command "watch --interval=10 acpi -b" in a 2nd terminal. This caused the hal messages => normally, hal does not produce these messages, thus gpm has no input to change power settings. Another confirmation that somehow I have to tell hal that the battery status has changed! HOW??? ** Attachment added: "$ gnome-power-manager --verbose --no-daemon 2>&1 | tee gpm.debug.log.txt" http://launchpadlibrarian.net/17246586/gpm.debug.log.txt -- HAL does not update Gnome-Power-Manager with battery readings https://bugs.launchpad.net/bugs/253073 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 253073] Re: HAL does not update Gnome-Power-Manager with battery readings
** Attachment added: "$ gconftool --recursive-list /apps/gnome-power-manager > gconftool.out" http://launchpadlibrarian.net/17246560/gconftool.out -- HAL does not update Gnome-Power-Manager with battery readings https://bugs.launchpad.net/bugs/253073 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 253073] Re: HAL does not update Gnome-Power-Manager with battery readings
$ dbus-monitor --session "type='signal',interface='org.freedesktop.PowerManagement'" ###unplug power supply signal sender=org.freedesktop.DBus -> dest=:1.29 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=NameAcquired string ":1.29" signal sender=:1.10 -> dest=(null destination) path=/org/freedesktop/PowerManagement; interface=org.freedesktop.PowerManagement; member=OnBatteryChanged boolean true signal sender=:1.10 -> dest=(null destination) path=/org/freedesktop/PowerManagement; interface=org.freedesktop.PowerManagement; member=PowerSaveStatusChanged boolean true ###plug power supply signal sender=:1.10 -> dest=(null destination) path=/org/freedesktop/PowerManagement; interface=org.freedesktop.PowerManagement; member=OnBatteryChanged boolean false signal sender=:1.10 -> dest=(null destination) path=/org/freedesktop/PowerManagement; interface=org.freedesktop.PowerManagement; member=PowerSaveStatusChanged boolean false NB: no intermediate event to show change in battery power state! -- HAL does not update Gnome-Power-Manager with battery readings https://bugs.launchpad.net/bugs/253073 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 253073] Re: HAL does not update Gnome-Power-Manager with battery readings
$ hal-find-by-capability --capability "battery" /org/freedesktop/Hal/devices/computer_power_supply_battery_BAT1 /org/freedesktop/Hal/devices/computer_power_supply_battery_BAT0 ** Attachment added: "$ hal-find-by-capability --capability "battery" | xargs -n 1 hal-device > hal-batteries.out" http://launchpadlibrarian.net/17246553/hal-batteries.out -- HAL does not update Gnome-Power-Manager with battery readings https://bugs.launchpad.net/bugs/253073 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 253073] Re: HAL does not update Gnome-Power-Manager with battery readings
Now following the instructions according to https://wiki.ubuntu.com/DebuggingGNOMEPowerManager: ** Attachment added: "output of $ gnome-power-bugreport.sh > gnome-power-bugreport.out" http://launchpadlibrarian.net/17246549/gnome-power-bugreport.out -- HAL does not update Gnome-Power-Manager with battery readings https://bugs.launchpad.net/bugs/253073 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 259868] Re: Gnome-Power-Manager ignores drive spin down settings in /etc/laptop-mode/laptop-mode.conf
I have to correct myself. The previously mentioned approach disactivates the features entirely (also LAPTOP_MODE start|stop is not called). I changed it to skip just the HDPARM calls. But this cannot have been the source of my issue, because I saw, that the file power.sh is nearly identical in Feisty and Hardy, so the root cause of the new behavior is somewhere else! The modification of the script can only be regarded as work-around for a still mysterious issue. -- Gnome-Power-Manager ignores drive spin down settings in /etc/laptop-mode/laptop-mode.conf https://bugs.launchpad.net/bugs/259868 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 259868] Re: Gnome-Power-Manager ignores drive spin down settings in /etc/laptop-mode/laptop-mode.conf
I just made the changes from 0.109 to 0.110 manually, this fixes the issue. My proposal: release for Hardy, issue for me is solved. -- Gnome-Power-Manager ignores drive spin down settings in /etc/laptop-mode/laptop-mode.conf https://bugs.launchpad.net/bugs/259868 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 259868] Re: Gnome-Power-Manager ignores drive spin down settings in /etc/laptop-mode/laptop-mode.conf
I found this also discussed in https://bugs.launchpad.net/ubuntu/+source/acpi-support/+bug/250938. Maybe It's fixed in 0.110, but it's not released for Hardy, just for Intrepid (see https://launchpad.net/ubuntu/+source/acpi-support). ** Also affects: acpi-support Importance: Undecided Status: New -- Gnome-Power-Manager ignores drive spin down settings in /etc/laptop-mode/laptop-mode.conf https://bugs.launchpad.net/bugs/259868 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 259868] Re: Gnome-Power-Manager ignores drive spin down settings in /etc/laptop-mode/laptop-mode.conf
===> Comment #3 from Richard Hughes (gnome-power-manager developer, points: 18) 2008-08-21 08:29 UTC [reply] Please file in ubuntu bugtracker -- in upstream g-p-m does not modify the hard drive spin down timeout in any way. thanks. <=== So it's a bug in Ubuntu's GPM. Attachments of acpi-support and laptop-mode.conf are available in the upstream bug report. PS: It is still working in Feisty Fawn, so what changed to Hardy? (I skipped Gibbon) -- Gnome-Power-Manager ignores drive spin down settings in /etc/laptop-mode/laptop-mode.conf https://bugs.launchpad.net/bugs/259868 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 259868] [NEW] Gnome-Power-Manager ignores drive spin down settings in /etc/laptop-mode/laptop-mode.conf
Public bug reported: Binary package hint: gnome-power-manager Laptop mode activated with "ENABLE_LAPTOP_MODE=true" in /etc/default/acpi-support Laptop mode is running when I unplug the power cord (reduced CPU frequency) but also the HD is spun down (which is deactivated in files /etc/laptop-mode/laptop-mode.conf and /etc/default/acpi-support). ** Affects: gnome-power Importance: Unknown Status: Unknown ** Affects: gnome-power-manager (Ubuntu) Importance: Undecided Status: New ** Bug watch added: GNOME Bug Tracker #548735 http://bugzilla.gnome.org/show_bug.cgi?id=548735 ** Also affects: gnome-power via http://bugzilla.gnome.org/show_bug.cgi?id=548735 Importance: Unknown Status: Unknown -- Gnome-Power-Manager ignores drive spin down settings in /etc/laptop-mode/laptop-mode.conf https://bugs.launchpad.net/bugs/259868 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 253073] Re: HAL does not update Gnome-Power-Manager with battery readings
** Bug watch added: freedesktop.org Bugzilla #16798 https://bugs.freedesktop.org/show_bug.cgi?id=16798 ** Also affects: hal via https://bugs.freedesktop.org/show_bug.cgi?id=16798 Importance: Unknown Status: Unknown -- HAL does not update Gnome-Power-Manager with battery readings https://bugs.launchpad.net/bugs/253073 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 253073] Re: HAL does not update Gnome-Power-Manager with battery readings
** Attachment added: "kern.log (only data of today)" http://launchpadlibrarian.net/16675002/kern.log -- HAL does not update Gnome-Power-Manager with battery readings https://bugs.launchpad.net/bugs/253073 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 253073] Re: HAL does not update Gnome-Power-Manager with battery readings
** Attachment added: "lshal > /tmp/lshal.txt" http://launchpadlibrarian.net/16674934/lshal.txt -- HAL does not update Gnome-Power-Manager with battery readings https://bugs.launchpad.net/bugs/253073 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 253073] Re: HAL does not update Gnome-Power-Manager with battery readings
The same as above but with "watch acpi -b" running in parallel 14:57 unpluggd power chord, started "watch acpi -b" -> updated power reading EVERY minute (even though watch is updated every 2s!) 14:59 plugged in power chord ** Attachment added: "hal1.log" http://launchpadlibrarian.net/16674923/hal1.log -- HAL does not update Gnome-Power-Manager with battery readings https://bugs.launchpad.net/bugs/253073 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 253073] Re: HAL does not update Gnome-Power-Manager with battery readings
Now following the instructions of https://wiki.ubuntu.com/DebuggingHal: Computer: Laptop Acer Travelmate 4002LMi 14:48 unplugged power chord (got notification window, laptop-mode is activated (disk turned off <- still need to figure out to stop that) -> no update of power reading in gnome-power-manager 14:52 plugged power chord in again ** Attachment added: "Output of sudo hald --verbose=yes --daemon=no 2>&1 | tee /tmp/hal0.log" http://launchpadlibrarian.net/16674871/hal0.log -- HAL does not update Gnome-Power-Manager with battery readings https://bugs.launchpad.net/bugs/253073 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 253073] Re: HAL does not update Gnome-Power-Manager with battery readings
** Also affects: gnome-power Importance: Undecided Status: New -- HAL does not update Gnome-Power-Manager with battery readings https://bugs.launchpad.net/bugs/253073 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 253073] Re: HAL does not update Gnome-Power-Manager with battery readings
tried with boot option apm=on This caused g-p-m to not update the battery status any more. Note, previously it showed new values, that were all the same. Interestingly, when unplugging the power cord the values were updated. So there must be different mechanisms running for detecting power cord and battery charge changes. The later is not running on my system and apm just makes it worse. -- HAL does not update Gnome-Power-Manager with battery readings https://bugs.launchpad.net/bugs/253073 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 253073] Re: HAL does not update Gnome-Power-Manager with battery readings
One idea that just crosses my mind: Might it be possible, that in the past (so Feisty Fawn) "acpi" was broadcasting the battery status and that now (Hardy Heron) this should be done by "computer_power_supply_battery" (just guessing from the prefix)? In that case, it might be possible, that my laptop (3 years old) does not support that feature. How can I check? I then would have to make acpi do that job instead. How could I do that? As a very ugly work-around I am now running always a script "watch acpi -b", which obviously makes acpi broadcast battery info. -- HAL does not update Gnome-Power-Manager with battery readings https://bugs.launchpad.net/bugs/253073 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 247069] Re: [Hardy] Power data not updated
seems to be a bug in HAL, created an issue there: https://bugs.launchpad.net/ubuntu/+source/hal/+bug/253073 -- [Hardy] Power data not updated https://bugs.launchpad.net/bugs/247069 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 253073] [NEW] HAL does not update Gnome-Power-Manager with battery readings
Public bug reported: Binary package hint: hal the issue is observed in Ubuntu 8.04 (hardy heron) with up to date packages. Gnome-Power-Manager does not update the battery reading of the laptop. I believe something messed up HAL because of the following: When I check the battery manually (acpi -b), lshal -m produces 10:56:42.004: computer_power_supply_battery_BAT0 property battery.remaining_time = 700 (0x2bc) (new) 10:56:42.009: computer_power_supply_battery_BAT0 property battery.charge_level.percentage = 21 (0x15) 10:56:42.013: computer_power_supply_battery_BAT0 property battery.charge_level.rate = 21223 (0x52e7) 10:56:42.016: computer_power_supply_battery_BAT0 property battery.charge_level.current = 13556 (0x34f4) 10:56:42.020: computer_power_supply_battery_BAT0 property battery.reporting.current = 916 (0x394) 10:56:42.022: computer_power_supply_battery_BAT0 property battery.rechargeable.is_charging = true 10:56:42.023: computer_power_supply_battery_BAT0 property battery.reporting.rate = 1434 (0x59a) 10:56:42.025: computer_power_supply_battery_BAT0 property battery.voltage.current = 16706 (0x4142) and gpm updates the battery reading. On Feisty (gpm working) I observed, that lshal -m produces every minute this output: acpi_BAT0 property battery.charge_level.percentage = 93 (0x5d) acpi_BAT0 property battery.remaining_time = 3781 (0xec5) acpi_BAT0 property battery.charge_level.current = 16605 (0x40dd) acpi_BAT0 property battery.voltage.current = 15882 (0x3e0a) acpi_BAT0 property battery.reporting.current = 1122 (0x462) which is missing in 8.04. So g-p-m is not updated regularily on the battery status. Further data: $ apt-cache policy hal hal: Installiert:0.5.11~rc2-1ubuntu8.1 Mögliche Pakete:0.5.11~rc2-1ubuntu8.1 Versions-Tabelle: *** 0.5.11~rc2-1ubuntu8.1 0 500 http://de.archive.ubuntu.com hardy-updates/main Packages 100 /var/lib/dpkg/status 0.5.11~rc2-1ubuntu7 0 500 http://de.archive.ubuntu.com hardy/main Packages $ lsb_release -rd Description:Ubuntu 8.04.1 Release:8.04 ** Affects: hal (Ubuntu) Importance: Undecided Status: New -- HAL does not update Gnome-Power-Manager with battery readings https://bugs.launchpad.net/bugs/253073 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 247069] Re: [Hardy] Power data not updated
Here is another observation: if I unplug the power-cord, it is immediately marked in the display with a dot ("Akkubetrieb"). Only if I call "acpi -b" also the message window "now running on battery" is shown together with an update of the residual time. So a different behavior of the monitor screen and the applet icon. I greatly appreciate any help for further debugging - I am at my whit's end. -- [Hardy] Power data not updated https://bugs.launchpad.net/bugs/247069 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 247069] [NEW] [Hardy] Power data not updated
Public bug reported: Binary package hint: gnome-power-manager gnome-power-manager does not update the graphs of remaining battery time, power consumption etc. unless i invoke an acpi command ("acpi -b"), which makes also HAL talk about the battery. But there are no intermediate HAL communications of the battery status. with "gnome-power-manager --verbose --no-daemon 2>&1 | tee gpm.debug.log.txt" I see a statement [hal_device_property_modified_cb] gpm-cell.c:258 (21:57:22): udi=/org/freedesktop/Hal/devices/computer_power_supply_battery_BAT0, key=battery.reporting.rate, added=0, removed=0, finally=0 If this means there is no battery reporting rate, this might be the cause. Package: Linux Ubuntu Hardy (all updates) Release: Description: Ubuntu 8.04.1, Release: 8.04 $ apt-cache policy gnome-power-manager gnome-power-manager: Installiert:2.22.1-1ubuntu4 ** Affects: gnome-power-manager (Ubuntu) Importance: Undecided Status: New -- [Hardy] Power data not updated https://bugs.launchpad.net/bugs/247069 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 194719] Re: 01_proc_sys_batteries.patch causes a regression making gnome-power-manager not detect the battery properly
I am having exactly this issue: gnome-power-manager does not update power-consumption (shows approx. 6W constantly, was 18W on Feisty), remaining battery time constantly 3h (should be 1:30h - old battery). Plugging / unplugging power is detected. $ dpkg -s hal|grep Version Version: 0.5.11~rc2-1ubuntu8.1 Was the bug reintroduced in subsequent updates? I am not aware of having noticed this issue some weeks ago. I'm also checking https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/194960. -- 01_proc_sys_batteries.patch causes a regression making gnome-power-manager not detect the battery properly https://bugs.launchpad.net/bugs/194719 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 138691] Re: system hangs at shutdown
Here's another observation. On my system, the proprietary fglrx driver causes system hangs when enhanced features are used (e.g. Google Earth). This can be resolved by turning the tickless kernel off with the boot option "nohz=off". Only this, no "acpi=force"! as mentioned in some forums. The side-effect is, that now my system shuts down in a stable way since 3 days. -- system hangs at shutdown https://bugs.launchpad.net/bugs/138691 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 138691] Re: system hangs at shutdown
** Attachment added: "version.log" http://launchpadlibrarian.net/15121556/version.log -- system hangs at shutdown https://bugs.launchpad.net/bugs/138691 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 138691] Re: system hangs at shutdown
** Attachment added: "to mail above" http://launchpadlibrarian.net/15121552/uname-a.log -- system hangs at shutdown https://bugs.launchpad.net/bugs/138691 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 138691] Re: system hangs at shutdown
** Attachment added: "to mail above" http://launchpadlibrarian.net/15121546/lspci-vvnn.log -- system hangs at shutdown https://bugs.launchpad.net/bugs/138691 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 138691] Re: system hangs at shutdown
Same with my Laptop Acer Travelmate 4000 and Ubuntu 8.04. Please note: Ubuntu 7.04 is running perfectly on my system (in parallel), without any special configuration (so it cannot be a BIOS issue) Switching screens with Strg+ALT+F7 and +F8 I see the error message: halt: unable to iterate IDE devices: No such file or directory which is also true, there is no such file in directory /proc (which is existing in Ubuntu 7.04). And the laptop does not turn off. Boot options lapic, acpi=force did not change anything. I realized this issue only after installation of ClamAV, but I guess this is a pure coincidence. >From the attachments you will see, that I am also struggeling with irda, but I guess that's also not connected to this. Following the log files attached: ** Attachment added: "dmesg.log" http://launchpadlibrarian.net/15121541/dmesg.log -- system hangs at shutdown https://bugs.launchpad.net/bugs/138691 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs