ubiquity causes battery monitor plasmoid to think new batteries have been added

Bug #331883 reported by Roman Shtylman
18
This bug affects 2 people
Affects Status Importance Assigned to Milestone
debian-installer-utils (Ubuntu)
Fix Released
Medium
Evan
kdebase-workspace (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: kdebase-workspace

During installation, when new disks have been partitioned the battery monitor plasmoid things that new batteries have been inserted and displays information about the new batteries using the same infromation (% charged and such) for each.

this happens when partitioning during the jaunty install

Revision history for this message
Roman Shtylman (shtylman) wrote :
Revision history for this message
Evan (ev) wrote :

As I do not have adequate hardware to test this with myself, can you apply the following patch to /bin/update-dev and let me know if it fixes the issue for you?

Thanks!

Changed in debian-installer-utils:
assignee: nobody → evand
importance: Undecided → Medium
status: New → Incomplete
Changed in kdebase-workspace:
status: New → Invalid
Revision history for this message
Roman Shtylman (shtylman) wrote : Re: [Bug 331883] Re: ubiquity causes battery monitor plasmoid to think new batteries have been added

Patch failed to apply. What version were you patching against? I
installed the latest ubiquity from apt.

~Roman

On Tue, Feb 24, 2009 at 5:14 AM, Evan Dandrea <email address hidden> wrote:
> As I do not have adequate hardware to test this with myself, can you
> apply the following patch to /bin/update-dev and let me know if it fixes
> the issue for you?
>
> Thanks!
>
> ** Attachment added: "update-dev-331883.patch"
>   http://launchpadlibrarian.net/23048249/update-dev-331883.patch
>
> ** Also affects: debian-installer-utils (Ubuntu)
>   Importance: Undecided
>       Status: New
>
> ** Changed in: debian-installer-utils (Ubuntu)
>   Importance: Undecided => Medium
>     Assignee: (unassigned) => Evan Dandrea (evand)
>       Status: New => Incomplete
>
> ** Changed in: kdebase-workspace (Ubuntu)
>       Status: New => Invalid
>
> --
> ubiquity causes battery monitor plasmoid to think new batteries have been added
> https://bugs.launchpad.net/bugs/331883
> You received this bug notification because you are a direct subscriber
> of the bug.
>

Revision history for this message
Evan (ev) wrote :

Sorry, I should have been more clear. You need to apply it against /bin/update-dev in the live environment before running ubiquity.

Revision history for this message
Roman Shtylman (shtylman) wrote :

Right, I tried to do exactly that and the patch was rejected. When I
boot into the live environment, I only update the ubiquity package;
are there other packages I should update before trying to run the
patch?

~Roman

On Thu, Feb 26, 2009 at 4:35 AM, Evan Dandrea <email address hidden> wrote:
> Sorry, I should have been more clear.  You need to apply it against /bin
> /update-dev in the live environment before running ubiquity.
>
> --
> ubiquity causes battery monitor plasmoid to think new batteries have been added
> https://bugs.launchpad.net/bugs/331883
> You received this bug notification because you are a direct subscriber
> of the bug.
>

Revision history for this message
Evan (ev) wrote :

Oh, of course. Sorry, I completely forgot that the ubiquity build scripts modify that file.

Just edit /bin/update-dev and tack the following on any calls to udevadm trigger:
--subsystem-nomatch=power_supply

Revision history for this message
Roman Shtylman (shtylman) wrote :

That does indeed fix it. Thanks.

~Roman

On Thu, Feb 26, 2009 at 11:58 AM, Evan Dandrea <email address hidden> wrote:
> Oh, of course.  Sorry, I completely forgot that the ubiquity build
> scripts modify that file.
>
> Just edit /bin/update-dev and tack the following on any calls to udevadm trigger:
> --subsystem-nomatch=power_supply
>
> --
> ubiquity causes battery monitor plasmoid to think new batteries have been added
> https://bugs.launchpad.net/bugs/331883
> You received this bug notification because you are a direct subscriber
> of the bug.
>

Evan (ev)
Changed in debian-installer-utils (Ubuntu):
status: Incomplete → Fix Committed
Revision history for this message
Mark (mark-wege) wrote :

The bug still exists in current Jaunty beta

Revision history for this message
Mark (mark-wege) wrote :

I have tested current Jaunty better and sometime during install a second battery applet appears in panel

Changed in debian-installer-utils:
status: Fix Committed → New
Revision history for this message
Colin Watson (cjwatson) wrote :

"Fix Committed" means that the change has been applied to a revision control system, but not yet uploaded so that you can see it. Don't undo such a status just because you can't see the fix yet; you shouldn't expect to until it's "Fix Released".

(That said, this mostly shouldn't be required any more now that we try to avoid udevadm trigger in ubiquity; if it is still required in jaunty final, it would be nice to track such cases down.)

Changed in debian-installer-utils (Ubuntu):
status: New → Fix Committed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package debian-installer-utils - 1.67ubuntu1

---------------
debian-installer-utils (1.67ubuntu1) karmic; urgency=low

  [ Colin Watson ]
  * Resynchronise with Debian. Remaining changes:
    - user-params: Don't propagate vga=* or break=* to installed system.
    - Use /proc/self/fd/4 rather than /dev/fd/4 in fetch-url-methods/http;
      the latter doesn't seem to exist in d-i.
    - list-devices: new "usb-partition" type for detecting partitions on USB
      drives.

  [ Evan Dandrea ]
  * Don't include the battery subsystem on calls to udevadm trigger
    (LP: #331883).

  [ Loic Minier ]
  * Add support for listing MMC partitions in list-devices; note that many MMC
    devices in e.g. netbooks or screens are actually connected over USB
    though; LP: #364604.

debian-installer-utils (1.67) unstable; urgency=low

  [ Frans Pop ]
  * Remove myself as uploader.
  * Append .conf extention to /etc/modprobe.d files, as required for
    module-init-tools >= 3.7.

  [ Updated translations ]
  * Italian (it.po) by Milo Casagrande

 -- Colin Watson <email address hidden> Wed, 29 Apr 2009 00:46:18 +0100

Changed in debian-installer-utils (Ubuntu):
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Bug attachments

Remote bug watches

Bug watches keep track of this bug in other bug trackers.