Ubuntu
banshee package

banshee crashes while detecting BPM

Bug #1193667 reported by magowiz
30
This bug affects 5 people
Affects Status Importance Assigned to Milestone
banshee (Ubuntu)
Invalid
Undecided
Unassigned
Raring
Fix Released
Undecided
Chow Loong Jin
soundtouch (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

my banshee crashes just after startup, while the task "detecting BPM" is running , i tried also to delete all banshee data from
~/.cache/banshee-1
~/.config/banshee-1

but it was useless, once I finished to rescan my music library the crash occur.

Here it is the output if banshee is launched from command line :
$ LC_ALL="C" banshee
[Info 19:48:00.203] Running Banshee 2.6.1: [Ubuntu 13.04 (linux-gnu, x86_64) @ 2013-06-20 18:22:04 UTC]

(Banshee:26711): GLib-GObject-WARNING **: attempting to add an interface (AtkComponent) to class (__gtksharp_49_Hyena_Gui_BaseWidgetAccessible) after class_init

(Banshee:26711): GLib-GObject-WARNING **: attempting to add an interface (AtkSelection) to class (__gtksharp_50_Hyena_Data_Gui_Accessibility_ListViewAccessible+601+5b+5bBanshee_Collection_TrackInfo+2c+20Banshee_Core+2c+20Version+3d2_6_0_0+2c+20Culture+3dneutral+2c+20PublicKeyToken+3dnull+5d+5d) after class_init

(Banshee:26711): GLib-GObject-WARNING **: attempting to add an interface (AtkTable) to class (__gtksharp_50_Hyena_Data_Gui_Accessibility_ListViewAccessible+601+5b+5bBanshee_Collection_TrackInfo+2c+20Banshee_Core+2c+20Version+3d2_6_0_0+2c+20Culture+3dneutral+2c+20PublicKeyToken+3dnull+5d+5d) after class_init

(Banshee:26711): GLib-GObject-WARNING **: attempting to add an interface (AtkSelection) to class (__gtksharp_56_Hyena_Data_Gui_Accessibility_ListViewAccessible+601+5b+5bBanshee_Collection_Database_QueryFilterInfo+601+5b+5bSystem_String+2c+20mscorlib+2c+20Version+3d4_0_0_0+2c+20Culture+3dneutral+2c+20PublicKeyToken+3db77a5c561934e089+5d+5d+2c+20Banshee_Services+2c+20Version+3d2_6_0_0+2c+20Culture+3dneutral+2c+20PublicKeyToken+3dnull+5d+5d) after class_init

(Banshee:26711): GLib-GObject-WARNING **: attempting to add an interface (AtkTable) to class (__gtksharp_56_Hyena_Data_Gui_Accessibility_ListViewAccessible+601+5b+5bBanshee_Collection_Database_QueryFilterInfo+601+5b+5bSystem_String+2c+20mscorlib+2c+20Version+3d4_0_0_0+2c+20Culture+3dneutral+2c+20PublicKeyToken+3db77a5c561934e089+5d+5d+2c+20Banshee_Services+2c+20Version+3d2_6_0_0+2c+20Culture+3dneutral+2c+20PublicKeyToken+3dnull+5d+5d) after class_init

(Banshee:26711): GLib-GObject-WARNING **: attempting to add an interface (AtkSelection) to class (__gtksharp_62_Hyena_Data_Gui_Accessibility_ListViewAccessible+601+5b+5bBanshee_Collection_ArtistInfo+2c+20Banshee_Core+2c+20Version+3d2_6_0_0+2c+20Culture+3dneutral+2c+20PublicKeyToken+3dnull+5d+5d) after class_init

(Banshee:26711): GLib-GObject-WARNING **: attempting to add an interface (AtkTable) to class (__gtksharp_62_Hyena_Data_Gui_Accessibility_ListViewAccessible+601+5b+5bBanshee_Collection_ArtistInfo+2c+20Banshee_Core+2c+20Version+3d2_6_0_0+2c+20Culture+3dneutral+2c+20PublicKeyToken+3dnull+5d+5d) after class_init

(Banshee:26711): GLib-GObject-WARNING **: attempting to add an interface (AtkSelection) to class (__gtksharp_68_Hyena_Data_Gui_Accessibility_ListViewAccessible+601+5b+5bBanshee_Collection_YearInfo+2c+20Banshee_Core+2c+20Version+3d2_6_0_0+2c+20Culture+3dneutral+2c+20PublicKeyToken+3dnull+5d+5d) after class_init

(Banshee:26711): GLib-GObject-WARNING **: attempting to add an interface (AtkTable) to class (__gtksharp_68_Hyena_Data_Gui_Accessibility_ListViewAccessible+601+5b+5bBanshee_Collection_YearInfo+2c+20Banshee_Core+2c+20Version+3d2_6_0_0+2c+20Culture+3dneutral+2c+20PublicKeyToken+3dnull+5d+5d) after class_init

(Banshee:26711): GLib-GObject-WARNING **: attempting to add an interface (AtkSelection) to class (__gtksharp_74_Hyena_Data_Gui_Accessibility_ListViewAccessible+601+5b+5bBanshee_Collection_AlbumInfo+2c+20Banshee_Core+2c+20Version+3d2_6_0_0+2c+20Culture+3dneutral+2c+20PublicKeyToken+3dnull+5d+5d) after class_init

(Banshee:26711): GLib-GObject-WARNING **: attempting to add an interface (AtkTable) to class (__gtksharp_74_Hyena_Data_Gui_Accessibility_ListViewAccessible+601+5b+5bBanshee_Collection_AlbumInfo+2c+20Banshee_Core+2c+20Version+3d2_6_0_0+2c+20Culture+3dneutral+2c+20PublicKeyToken+3dnull+5d+5d) after class_init
[Warn 19:48:01.729] Caught an exception - System.ApplicationException: No support GNOME Settings Daemon could be reached. (in `Banshee.MultimediaKeys')
  at Banshee.MultimediaKeys.MultimediaKeysService.Banshee.ServiceStack.IExtensionService.Initialize () [0x00000] in <filename unknown>:0
  at Banshee.ServiceStack.ServiceManager.StartExtension (Mono.Addins.TypeExtensionNode node) [0x00000] in <filename unknown>:0
[Warn 19:48:01.730] Extension `Banshee.MultimediaKeys.MultimediaKeysService' not started: No support GNOME Settings Daemon could be reached.
[Info 19:48:01.822] Updating web proxy from GConf
[Warn 19:48:01.960] Caught an exception - System.ApplicationException: No support GNOME Settings Daemon could be reached. (in `Banshee.MultimediaKeys')
  at Banshee.MultimediaKeys.MultimediaKeysService.Banshee.ServiceStack.IExtensionService.Initialize () [0x00000] in <filename unknown>:0
  at Banshee.ServiceStack.ServiceManager.StartExtension (Mono.Addins.TypeExtensionNode node) [0x00000] in <filename unknown>:0
[Warn 19:48:01.960] Extension `Banshee.MultimediaKeys.MultimediaKeysService' not started: No support GNOME Settings Daemon could be reached.
[Info 19:48:01.961] All services are started 1.500732
[Info 19:48:02.670] AmazonMP3 store redirect URL: https://one.ubuntu.com/music/store/amz/
[Info 19:48:03.436] nereid Client Started
[Info 19:48:03.498] GStreamer version 1.0.6.0, gapless: True, replaygain: True
[Info 19:48:03.630] AppleDeviceSource is ignoring unmounted volume win
[Info 19:48:03.644] AppleDeviceSource is ignoring unmounted volume Riservato per il sistema
[Info 19:48:03.666] AppleDeviceSource is ignoring unmounted volume Disco Floppy
banshee: PeakFinder.cpp:150: int soundtouch::PeakFinder::findCrossingLevel(const float*, float, int, int) const: Assertion `peaklevel >= level' failed.

Native stacktrace:

 banshee() [0x4961e9]
 /lib/x86_64-linux-gnu/libpthread.so.0() [0x3c3b40fbd0]
 /lib/x86_64-linux-gnu/libc.so.6(gsignal+0x37) [0x3c3ac37037]
 /lib/x86_64-linux-gnu/libc.so.6(abort+0x148) [0x3c3ac3a698]
 /lib/x86_64-linux-gnu/libc.so.6() [0x3c3ac2fe03]
 /lib/x86_64-linux-gnu/libc.so.6() [0x3c3ac2feb2]
 /usr/lib/x86_64-linux-gnu/libSoundTouch.so.0(+0x9f75) [0x7fed25104f75]
 /usr/lib/x86_64-linux-gnu/libSoundTouch.so.0(_ZNK10soundtouch10PeakFinder13getPeakCenterEPKfi+0x8a) [0x7fed2510507a]
 /usr/lib/x86_64-linux-gnu/libSoundTouch.so.0(_ZN10soundtouch10PeakFinder10detectPeakEPKfii+0x5f) [0x7fed2510514f]
 /usr/lib/x86_64-linux-gnu/libSoundTouch.so.0(_ZN10soundtouch9BPMDetect6getBpmEv+0x3f) [0x7fed25104d6f]
 /usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstsoundtouch.so(+0x4f22) [0x7fed2530ef22]
 /usr/lib/x86_64-linux-gnu/libgstbase-1.0.so.0() [0x3c5ce327a0]
 /usr/lib/x86_64-linux-gnu/libgstbase-1.0.so.0() [0x3c5ce32f3f]
 /usr/lib/x86_64-linux-gnu/libgstreamer-1.0.so.0() [0x3c5ae5e05a]
 /usr/lib/x86_64-linux-gnu/libgstbase-1.0.so.0() [0x3c5ce33145]
 /usr/lib/x86_64-linux-gnu/libgstreamer-1.0.so.0() [0x3c5ae5e05a]
 /usr/lib/x86_64-linux-gnu/libgstreamer-1.0.so.0(gst_proxy_pad_chain_default+0xbb) [0x3c5ae4fcab]
 /usr/lib/x86_64-linux-gnu/libgstreamer-1.0.so.0() [0x3c5ae5e05a]
 /usr/lib/x86_64-linux-gnu/libgstaudio-1.0.so.0() [0x3c5c618cbc]
 /usr/lib/x86_64-linux-gnu/libgstaudio-1.0.so.0() [0x3c5c618e58]
 /usr/lib/x86_64-linux-gnu/libgstaudio-1.0.so.0(gst_audio_decoder_finish_frame+0x445) [0x3c5c61da55]
 /usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstmad.so(+0x1dcd) [0x7fed240c2dcd]
 /usr/lib/x86_64-linux-gnu/libgstaudio-1.0.so.0() [0x3c5c61acd8]
 /usr/lib/x86_64-linux-gnu/libgstaudio-1.0.so.0() [0x3c5c61b08b]
 /usr/lib/x86_64-linux-gnu/libgstaudio-1.0.so.0() [0x3c5c61c19e]
 /usr/lib/x86_64-linux-gnu/libgstreamer-1.0.so.0() [0x3c5ae5e05a]
 /usr/lib/x86_64-linux-gnu/libgstbase-1.0.so.0(gst_base_parse_push_frame+0x767) [0x3c5ce15617]
 /usr/lib/x86_64-linux-gnu/libgstbase-1.0.so.0(gst_base_parse_finish_frame+0x643) [0x3c5ce18ed3]
 /usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstaudioparsers.so(+0x10500) [0x7fed242d6500]
 /usr/lib/x86_64-linux-gnu/libgstbase-1.0.so.0() [0x3c5ce12f4a]
 /usr/lib/x86_64-linux-gnu/libgstbase-1.0.so.0() [0x3c5ce134bd]
 /usr/lib/x86_64-linux-gnu/libgstbase-1.0.so.0() [0x3c5ce17251]
 /usr/lib/x86_64-linux-gnu/libgstreamer-1.0.so.0() [0x3c5ae8ba71]
 /lib/x86_64-linux-gnu/libglib-2.0.so.0() [0x3c3c46d6f2]
 /lib/x86_64-linux-gnu/libglib-2.0.so.0() [0x3c3c46ceb5]
 /lib/x86_64-linux-gnu/libpthread.so.0() [0x3c3b407f8e]
 /lib/x86_64-linux-gnu/libc.so.6(clone+0x6d) [0x3c3acf9e1d]

Debug info from gdb:

Could not attach to process. If your uid matches the uid of the target
process, check the setting of /proc/sys/kernel/yama/ptrace_scope, or try
again as the root user. For more details, see /etc/sysctl.d/10-ptrace.conf
ptrace: Operation not permitted.
No threads.

=================================================================
Got a SIGABRT while executing native code. This usually indicates
a fatal error in the mono runtime or one of the native libraries
used by your application.
=================================================================

Aborted (core dump created)

Revision history for this message
magowiz (magowiz) wrote :

I forgot to report package version and ubuntu release :
banshee 2.6.1-1
ubuntu 13.04

Revision history for this message
Chow Loong Jin (hyperair) wrote : Re: [Bug 1193667] Re: banshee crashes while detecting BPM

On Sat, Jun 22, 2013 at 05:59:08PM -0000, magowiz wrote:
> I forgot to report package version and ubuntu release :
> banshee 2.6.1-1
> ubuntu 13.04

Please try upgrading to the version in 2.6.1-1.1 (see Bug #1159513), and seeing
if that fixes your isssue. The fix there was for both BPM stuff and transcoding
stuff.

  status incomplete

--
Kind regards,
Loong Jin

Changed in banshee (Ubuntu):
status: New → Incomplete
Revision history for this message
magowiz (magowiz) wrote :

while installing the version you are talking about ( downloaded from here : https://launchpad.net/ubuntu/raring/amd64/banshee/2.6.1-1ubuntu1.1 ) I noticed that it was the same version I've got installed, maybe the output of dpkg -l was truncated since the terminal window was little.
Anyway I have to say that the version 2.6.1-1.1 I upgraded to some days ago introduced this bug. Since before I was using a previous version of banshee (maybe 2.6.1-1) without any crash.

Revision history for this message
Chow Loong Jin (hyperair) wrote :

On Sat, Jun 22, 2013 at 10:41:47PM -0000, magowiz wrote:
> while installing the version you are talking about ( downloaded from here :
> https://launchpad.net/ubuntu/raring/amd64/banshee/2.6.1-1ubuntu1.1 ) I noticed
> that it was the same version I've got installed, maybe the output of dpkg -l
> was truncated since the terminal window was little. Anyway I have to say that
> the version 2.6.1-1.1 I upgraded to some days ago introduced this bug. Since
> before I was using a previous version of banshee (maybe 2.6.1-1) without any
> crash.

Okay, that's odd. Could you downgrade back to 2.6.1-1 and see if that solves the
issue?

"sudo apt-get install banshee=2.6.1-1" should do the trick.

--
Kind regards,
Loong Jin

Revision history for this message
magowiz (magowiz) wrote :

sudo apt-get install banshee=2.6.1-1
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Version '2.6.1-1' for 'banshee' was not found

anyway I was able to download it from here : https://launchpad.net/ubuntu/raring/amd64/banshee/2.6.1-1ubuntu1
and I can confirm that downgrading the issue is solved, so I think last version of banshee (2.6.1-1.1) introduced this bug/regression.

Revision history for this message
Chow Loong Jin (hyperair) wrote :

On Sun, Jun 23, 2013 at 07:49:24AM -0000, magowiz wrote:
> sudo apt-get install banshee=2.6.1-1
> Reading package lists... Done
> Building dependency tree
> Reading state information... Done
> E: Version '2.6.1-1' for 'banshee' was not found

Whoops, I meant 2.6.1-1ubuntu1, but it looks like you got it right anyway.

> anyway I was able to download it from here : https://launchpad.net/ubuntu/raring/amd64/banshee/2.6.1-1ubuntu1
> and I can confirm that downgrading the issue is solved, so I think last version of banshee (2.6.1-1.1) introduced this bug/regression.

2.6.1-1ubuntu1.1, but yeah. I'll look into reverting the BPM portions of the
patch. Does BPM detection work at all for you with the older version?

--
Kind regards,
Loong Jin

Revision history for this message
magowiz (magowiz) wrote :

I'm not really sure I was really using that feature, can you tell me please how can I test if BPM detection is actually working in banshee-2.6.1-1 ? So I can tell you in a few time which is the situation with BPM in older version before reverting to something that doesn't crash but that doesn't actually work.

Revision history for this message
Chow Loong Jin (hyperair) wrote :

On Sun, Jun 23, 2013 at 04:18:37PM -0000, magowiz wrote:
> I'm not really sure I was really using that feature, can you tell me
> please how can I test if BPM detection is actually working in
> banshee-2.6.1-1 ? So I can tell you in a few time which is the
> situation with BPM in older version before reverting to something that
> doesn't crash but that doesn't actually work.

Well, if you press 'e' on one of the tracks, go to the "Extra" tab, and click
"Detect" under "Beats Per Minute", it's supposed to detect the BPM.

I just tried it on 2.6.1-1ubuntu1, but it doesn't ever manage to detect the BPM.
In 2.6.1-1ubuntu1.1, I see the same crash you're seeing. From what I can tell,
this is probably the situation:
 - 2.6.1-1ubuntu1: BPM detection doesn't work at all
 - 2.6.1-1ubuntu1.1: BPM detection re-enabled, but exposes a bug in
   libsoundtouch causes the assertion error.

--
Kind regards,
Loong Jin

Chow Loong Jin (hyperair)
Changed in banshee (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
magowiz (magowiz) wrote :

Yes I can confirm what are you saying , when I click detect the button become inactive and even if I wait a lot I cannot get any result in BPM field. Anyway I still prefer a version with a minor feature not working that a version that crashes on each start.... maybe if I disable Automatically BPM detect option I can avoid crashes also with latest version from ubuntu repositories but at this point the change from 1 to 1.1 is ininfluent.

Anyway, obviously I let to ubuntu developers to take their own decision, if possible the best one is to fix the BPM in a way that doesn't make banshee crashes.
Thank you for your support.

Revision history for this message
Chow Loong Jin (hyperair) wrote :

On Sun, Jun 23, 2013 at 06:44:23PM -0000, magowiz wrote:
> Yes I can confirm what are you saying , when I click detect the button
> become inactive and even if I wait a lot I cannot get any result in BPM
> field. Anyway I still prefer a version with a minor feature not working
> that a version that crashes on each start.... maybe if I disable
> Automatically BPM detect option I can avoid crashes also with latest
> version from ubuntu repositories but at this point the change from 1 to
> 1.1 is ininfluent.
>
> Anyway, obviously I let to ubuntu developers to take their own decision, if possible the best one is to fix the BPM in a way that doesn't make banshee crashes.
> Thank you for your support.

Well, I've marked the raring-proposed update as verification-failed, so the
broken update won't reach the general public.

I'm thinking of just dropping the BPM detection module completely on Raring
until we get a fix for SoundTouch.

--
Kind regards,
Loong Jin

Revision history for this message
magowiz (magowiz) wrote :

what does this imply for users ? banshee package 2.6.1-1.1 will be removed from ubuntu repositories (proposed) ?
Yesterday I tried to do an sudo apt-get upgrade and I still got banshee to upgrade.

Revision history for this message
Chow Loong Jin (hyperair) wrote :

On Mon, Jun 24, 2013 at 07:23:40AM -0000, magowiz wrote:
> what does this imply for users ? banshee package 2.6.1-1.1 will be removed from ubuntu repositories (proposed) ?
> Yesterday I tried to do an sudo apt-get upgrade and I still got banshee to upgrade.

Well, normal users aren't supposed to keep the -proposed repository enabled,
actually. It's only meant for testing to ensure that no regressions occur before
being copied into the -updates pocket (enabled by default).

Uploads which fail the test get removed eventually, or are superseded with an
upload that fixes the issue without regressions.

--
Kind regards,
Loong Jin

Revision history for this message
Chow Loong Jin (hyperair) wrote :

Marking banshee task as invalid -- the issue belongs in soundtouch.

Changed in banshee (Ubuntu):
status: Confirmed → Invalid
Revision history for this message
Chow Loong Jin (hyperair) wrote :

Creating task raring to drop BPM extension entirely, since it currently does not work and/or causes crashes.

Changed in banshee (Ubuntu Raring):
assignee: nobody → Chow Loong Jin (hyperair)
status: New → Confirmed
no longer affects: soundtouch (Ubuntu Raring)
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in soundtouch (Ubuntu):
status: New → Confirmed
Revision history for this message
Brian Murray (brian-murray) wrote : Please test proposed package

Hello magowiz, or anyone else affected,

Accepted banshee into raring-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/banshee/2.6.1-1ubuntu1.2 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

Changed in banshee (Ubuntu Raring):
status: Confirmed → Fix Committed
tags: added: verification-needed
Revision history for this message
magowiz (magowiz) wrote :

I can confirm that now latest version from proposed repository :
- doesn't crash on start anymore
- BPM feature is disabled like this released was supposed to do

So from my point of view this bug is here no longer, as you said it is now a bug that belongs only to soundtouch.

Revision history for this message
Chow Loong Jin (hyperair) wrote : Re: [Bug 1193667] Re: banshee crashes while detecting BPM

On Sat, Jun 29, 2013 at 12:38:45PM -0000, magowiz wrote:
> I can confirm that now latest version from proposed repository :
> - doesn't crash on start anymore
> - BPM feature is disabled like this released was supposed to do
>
> So from my point of view this bug is here no longer, as you said it is
> now a bug that belongs only to soundtouch.

Great, thanks for verifying.

  tags verification-done -verification-needed

--
Kind regards,
Loong Jin

Brian Murray (brian-murray)
tags: added: verification-done
removed: verification-needed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package banshee - 2.6.1-1ubuntu1.2

---------------
banshee (2.6.1-1ubuntu1.2) raring-proposed; urgency=low

  * [13571f2] Disable BPM support.
    It doesn't work prior to the GStreamer patch, and sigabrts with the patch
    due to a SoundTouch bug. (LP: #1193667)

banshee (2.6.1-1ubuntu1.1) raring-proposed; urgency=low

  * [6fe3971] Cherry-pick fix for transcoding exceptions (LP: #1159513)
 -- Chow Loong Jin <email address hidden> Tue, 25 Jun 2013 01:07:25 +0800

Changed in banshee (Ubuntu Raring):
status: Fix Committed → Fix Released
Revision history for this message
Brian Murray (brian-murray) wrote : Update Released

The verification of this Stable Release Update has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regresssions.

Revision history for this message
Chow Loong Jin (hyperair) wrote :

Okay, I figured out the issue. In PeakFinder::getPeakCenter, there are some floating point issues when peakLevel == groundLevel.

At line 199 of PeakFinder.cpp, cutLevel is calculated as 0.70f * peakLevel + 0.30f * groundLevel, which can sometimes end up with cutLevel > groundLevel due to floating point errors, and this triggers the assertion error.

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package soundtouch - 1.7.1-5

---------------
soundtouch (1.7.1-5) unstable; urgency=low

  * Team upload.
  * Fix assertion in findCrossingLevel (LP: #1193667)

 -- Chow Loong Jin <email address hidden> Tue, 10 Dec 2013 12:07:30 +0800

Changed in soundtouch (Ubuntu):
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Subscribing...

Other bug subscribers

Remote bug watches

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