[Bug 420447] Re: no sound devices on babbage board with linux-image-2.6.31-100-imx51
What changes are needed to expose the right properties to udev? -- no sound devices on babbage board with linux-image-2.6.31-100-imx51 https://bugs.launchpad.net/bugs/420447 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 420447] Re: no sound devices on babbage board with linux-image-2.6.31-100-imx51
I didn't see any ALSA messages in your boot log so it isn't initializing fully. A section of my bootlog is below. Have you tried it with the sound driver built in? All my testing is using the imx51_defconfig that is in your kernel tree, so the audio is built in, not as modules. I tested with on babbage 2.5 fsl rootfs (not ubuntu) and the audio is coming up and functioning. boot messages: Advanced Linux Sound Architecture Driver Version 1.0.20. sgtl5000-i2c 1-000a: SGTL5000 revision 17 DMA Sound Buffers Allocated:UseIram=1 buf-addr=1ffef000 buf-area=de8a8000 size=24576 DMA Sound Buffers Allocated:UseIram=1 buf-addr=ac26 buf-area=fbe03000 size=24576 asoc: SGTL5000 - imx-ssi-3 mapping ok mmc0: new high speed SDHC card at address 8fe4 mmcblk0: mmc0:8fe4 SU08G 7.40 GiB mmcblk0: p1 p2 ALSA device list: #0: imx-3stack (SGTL5000) -- no sound devices on babbage board with linux-image-2.6.31-100-imx51 https://bugs.launchpad.net/bugs/420447 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 420447] Re: no sound devices on babbage board with linux-image-2.6.31-100-imx51
Could you please attach your defconfig? -- no sound devices on babbage board with linux-image-2.6.31-100-imx51 https://bugs.launchpad.net/bugs/420447 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 420447] Re: no sound devices on babbage board with linux-image-2.6.31-100-imx51
Thanks. My guess: two types of problems at this point: the changes to how the rootfs handles audio and issues with the audio driver as a module. I'll debug the audio driver module problems. For now, I recommend you try building the driver into the rootfs so that you can debug the rootfs issues. I will not likely have much input on that. -- no sound devices on babbage board with linux-image-2.6.31-100-imx51 https://bugs.launchpad.net/bugs/420447 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 420447] Re: no sound devices on babbage board with linux-image-2.6.31-100-imx51
Debugging using fsl rootfs, I see the audio work as a module just fine. I get these messages when it loads: r...@freescale ~$ modprobe -V snd-soc-imx-3stack-sgtl5000 sgtl5000-i2c 1-000a: SGTL5000 revision 17 DMA Sound Buffers Allocated:UseIram=1 buf-addr=1ffef000 buf-area=de9a size=24576 DMA Sound Buffers Allocated:UseIram=1 buf-addr=ac468000 buf-area=fbe08000 size=24576 asoc: SGTL5000 - imx-ssi-3 mapping ok Check using 'lsmod' to make sure all the modules got loaded: r...@freescale ~$ lsmod Module Size Used by snd_soc_imx_3stack_sgtl5000 8320 0 snd_soc_imx 6600 1 snd_soc_imx_3stack_sgtl5000 snd_soc_imx_ssi 6288 1 snd_soc_imx_3stack_sgtl5000 snd_soc_sgtl5000 13356 1 snd_soc_imx_3stack_sgtl5000 snd_soc_core 48040 3 snd_soc_imx_3stack_sgtl5000,snd_soc_imx,snd_soc_sgtl5000 snd_pcm78545 3 snd_soc_imx,snd_soc_sgtl5000,snd_soc_core snd_page_alloc 7588 1 snd_pcm snd_timer 22332 1 snd_pcm snd55188 4 snd_soc_imx_3stack_sgtl5000,snd_soc_core,snd_pcm,snd_timer soundcore 8168 1 snd So I suggest that you do 'lsmod' to make sure all the modules got loaded. If they did, then it is rootfs issues. -- no sound devices on babbage board with linux-image-2.6.31-100-imx51 https://bugs.launchpad.net/bugs/420447 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 420447] Re: no sound devices on babbage board with linux-image-2.6.31-100-imx51
Regarding the rename, I am sympathetic and the case you are making for it is sound (pardon the pun). I just don't have the time. Keep in mind that it is one platform for you (imx-3stack-sgtl5000) but for me it is seven (sgtl5000, ak4647, ak5702, etc). Also if I rename all those file, it makes it harder to diff between 2.6.28 and 2.6.31. -- no sound devices on babbage board with linux-image-2.6.31-100-imx51 https://bugs.launchpad.net/bugs/420447 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 420447] Re: no sound devices on babbage board with linux-image-2.6.31-100-imx51
Are you plugged into the right jack? If you are used to the Babbage1 board, it's easy to plug the headphone into the wrong jack. The headset and headphone jacks swapped somewhere between BBG1 and BBG2.5. They weren't even labeled on BBG1, but they're labeled on BBG2.5 (in tiny, tiny print). The jack closer to the corner of the board (marked HDPHONE) is for stereo headphones. The jack next to it is for a headset with one channel of audio and a mic (HDSET). Regarding DVI monitors, I strongly that recommend everybody remove those two resistors (#11) even if sound seems to be working. The real problem is that some I2C reads/writes will fail, so you could get sound that is *mostly* working. -- no sound devices on babbage board with linux-image-2.6.31-100-imx51 https://bugs.launchpad.net/bugs/420447 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 420447] Re: no sound devices on babbage board with linux-image-2.6.31-100-imx51
I'm attaching another patch that allows the audio codec to power down when not in use. The problem was that Line In was always enabled, so always powered up. ** Attachment added: 0005-sgtl5000-add-line-in-function.patch http://launchpadlibrarian.net/33050170/0005-sgtl5000-add-line-in-function.patch -- no sound devices on babbage board with linux-image-2.6.31-100-imx51 https://bugs.launchpad.net/bugs/420447 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 420447] Re: no sound devices on babbage board with linux-image-2.6.31-100-imx51
I'm attaching two patches to give you what we have of the audio port. These patches apply cleanly to your fsl-imx51 branch. Playback and record work. There is an issue with your regulator stuff that breaks things somewhat. You will see a boot error that occurs when imx-3stack-sgtl5000.c calls regulator_get. That's something that needs to get fixed in your regulator stuff. Audio functionality will be broken until this is fixed as the audio does not completely initialize. There is another issue with a loud pop happening when boot up occurs. This is because the 'Line In Jack' widget is on all the time. I'm working on fixing this. As is, audio works, but will never completely power down, so it becomes an issue with power consumption also. -- no sound devices on babbage board with linux-image-2.6.31-100-imx51 https://bugs.launchpad.net/bugs/420447 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 420447] Re: no sound devices on babbage board with linux-image-2.6.31-100-imx51
** Attachment added: 0001-ENGR00107785-sgtl5000-adc-power-savings.patch http://launchpadlibrarian.net/32991149/0001-ENGR00107785-sgtl5000-adc-power-savings.patch -- no sound devices on babbage board with linux-image-2.6.31-100-imx51 https://bugs.launchpad.net/bugs/420447 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 420447] Re: no sound devices on babbage board with linux-image-2.6.31-100-imx51
** Attachment added: 0002-sgtl5000-audio-more-porting-to-2.6.31.patch http://launchpadlibrarian.net/32991169/0002-sgtl5000-audio-more-porting-to-2.6.31.patch -- no sound devices on babbage board with linux-image-2.6.31-100-imx51 https://bugs.launchpad.net/bugs/420447 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 420447] Re: no sound devices on babbage board with linux-image-2.6.31-100-imx51
Just to be completely clear about the regulator issue, I have attached a patch. This is not a solution so I named it something that no normal human would consider merging and pushing. This patch puts #if 0 around the regulator initialization part if imx-3stack-sgtl5000's probe so that the audio driver can finish initializing. This is just for demonstration and debug purposes so please don't push it. The real solution is in the regulator code. ** Attachment added: A hack to allow audio to initialize. The real solution is to fix the regulator code. http://launchpadlibrarian.net/32992361/0004-AUDIO-HACK-DO-NOT-MERGE.patch -- no sound devices on babbage board with linux-image-2.6.31-100-imx51 https://bugs.launchpad.net/bugs/420447 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 420447] Re: no sound devices on babbage board with linux-image-2.6.31-100-imx51
What kind of boot messages do you get when ALSA starts up? -- no sound devices on babbage board with linux-image-2.6.31-100-imx51 https://bugs.launchpad.net/bugs/420447 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 420447] Re: no sound devices on babbage board with linux-image-2.6.31-100-imx51
Some boards have I2C errors when a DVI monitor is plugged in. This can prevent register access to the sgtl5000 audio codec when the audio driver is initializing. The symptom is that you will see in the boot messages some I2C errors and a message that it has not successfully id'd the sgtl5000. The workaround is to take two resistors off the board (this is OK for babbage 2.0 and 2.5): R284 and R287. They are located on the top side of the board about 1cm from the DVI connector on either side of U33. This will cut the I2C connection to the DVI connection so that it will not be able to read the EDID. So specifying the video mode in the kernel command line is necessary if you are not already doing so, i.e. video=mxcfb:1024x768...@60. -- no sound devices on babbage board with linux-image-2.6.31-100-imx51 https://bugs.launchpad.net/bugs/420447 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 420447] Re: no sound devices on babbage board with linux-image-2.6.31-100-imx51
I checked. I was wrong about the command line. It will default to 1024x768. Sorry for the static. -- no sound devices on babbage board with linux-image-2.6.31-100-imx51 https://bugs.launchpad.net/bugs/420447 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 396716] Re: [ARM] default user audio goes to /dev/null
*** This bug is a duplicate of bug 420447 *** https://bugs.launchpad.net/bugs/420447 9.04 has audio support. This is not a duplicate. the bug 420447 appears to be a bug in the 2.6.30 kernel port. It builds fine in the 2.6.28 kernel and the release 9.04 has sgtl5000 audio built in the kernel. In fact, if I do the group changes I listed above, audio works without rebuilding the kernel. So audio is there in the kernel and it does not get detected properly. Maybe my methods of fixing it are wrong. But if the group defaults are right, that does not explain why audio did not come up by default on the 9.04 default install. -- [ARM] default user audio goes to /dev/null https://bugs.launchpad.net/bugs/396716 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 407119] Re: audio stuttering during desktop-login.org but only just after login
It appears that it is the vorbis decode that gets behind. If I change the login sound to be a 7 second sine uncompressed wav file in the Sound Preferences, the sine wave plays flawlessly. So I think this is a priority problem where the vorbis decoder gets behind because too much stuff is happening at login. Is there some way of adjusting priority so that decode gets higher cpu priority at this time? Are there other experiments I could be doing that would help pin this down or optimise the configuration? How does priority for things like audio decoders get set? Is the playback going through gstreamer at this time? -- audio stuttering during desktop-login.org but only just after login https://bugs.launchpad.net/bugs/407119 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 407119] Re: audio stuttering during desktop-login.org but only just after login
** Attachment added: The app that plays the Ubuntu desktop login sound sets the period to whatever minimum is allowed by the driver. This change sets period size high enough value that we will never have ssi underruns then. http://launchpadlibrarian.net/29729382/0001-ENGR00114681-pcm-set-minimum-period-to-2k.patch -- audio stuttering during desktop-login.org but only just after login https://bugs.launchpad.net/bugs/407119 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 407119] [NEW] audio stuttering during desktop-login.org but only just after login
Public bug reported: Platform: Babbage 2.0 Release: Jaunty with all the current upgrades. I uninstalled pulseaudio to save cpu. I also patched the audio driver to increase the minimal audio period size to 2K. Patch is attached. Symptom: 1. Log onto Ubuntu. The desktop-login.org sound will play with huge amounts of stuttering. 2. There is no stuttering if you play same file later. Open the Sound Preferences app, click on the Sounds tab, click on the arrow next to 'Login'. The desktop-login.org will play _without_ stuttering. What I figured out so far: At first I thought this was due to SSI underruns. So I fixed the underruns, but the stuttering remained. The app that is playing the audio was requesting a 64 byte audio buffer period. This is the minimum audio buffer period that the audio driver allows. That was causing SSI underruns. So I fixed that in the audio driver, I made the minimum audio period 2K bytes. The patch is attached (1 line changed in patch). But the error remains. It only happens during the initial login. I think this is new behavior for Jaunty but can't prove that at this time. ** Affects: gdm (Ubuntu) Importance: Undecided Status: New -- audio stuttering during desktop-login.org but only just after login https://bugs.launchpad.net/bugs/407119 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 396716] [NEW] default user audio goes to /dev/null
Public bug reported: Release: Ubuntu 9.04 on Babbage1 I'm not changing anything from the 9.04 release. After install, audio is defaulting to /dev/null The volume control applet's heading says Volume Control: Playback: Null Output (PulseAudio Mixer) The problem is that the default user that was created during install isn't a member of the audio group. Same can be said for video. Default groups after a install for the install user are: ubuntu(the default user was named ubuntu in my case) adm dialout cdrom plugdev lpadmin admin sambashare Doing this added my default user ubuntu to the audio and video groups to enable audio and video playback. sudo usermod -a -G audio,video ubuntu ** Affects: ubuntu Importance: Undecided Status: New -- default user audio goes to /dev/null https://bugs.launchpad.net/bugs/396716 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 392716] Re: notification area applets crash on login
In the Babbage1 case, the kernel, rootfs, and initrd are unchanged. I have changed redboot only. So no kernel config changes or changes to the initrd scripts/modules. ifconfig shows a loopback device in the failing case. And networking is working. In the Babbage2 case there is no initrd, so yes something is not being set up and the kernel config is different. For now I'm focusing on Babbage1 case as there are less variables there. I will follow the DebuggingProgramCrash proceedure and post the results. -- notification area applets crash on login https://bugs.launchpad.net/bugs/392716 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 392716] Re: notification area applets crash on login
I have gone back and forth between redboot versions that work/don't work using dd. I can do fis list and fc -l and capture the results and compare good to bad and see that the listed information is not changed. -- notification area applets crash on login https://bugs.launchpad.net/bugs/392716 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 392716] Re: notification area applets crash on login
I also have replicated the bug using the vmlinuz and initrd from /boot. I copied them to a host machine, used gzip -d to decompress the initrd, and uploaded them using tftp with redboot, adding the unchanged exec line. So I really think the only change here (in the Babbage1 case) is redboot, not what we're loading. load -r -b 0x100 -h 10.81.71.15 /home/r80115/Public/try-booting-default-initrd/initrd load -r -b 0x10 -h 10.81.71.15 /home/r80115/Public/try-booting-default-initrd/vmlinuz exec -r 0x100 -s 0x0098F400 -c root=UUID=e804fd17-9603-4f56-b08c-1073da858aff ro -- notification area applets crash on login https://bugs.launchpad.net/bugs/392716 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 392716] Re: notification area applets crash on login
Yeah, that's fine, I agree it is good to be real exact about what changed and what didn't, so I'm totally fine with any questions you have on my setup. Are you seeing the failure of the applets after login? I started down the path of DebuggingProgramCrash, not sure which program to pursue as the crashing one. Also difficult since by the time the system is up it has already crashed. I guess if I add a serial console to the exec line I can set up gdb to monitor something before I log into gnome. Hopefully that will be early enough. Any suggestions on which to tell gdb to monitor? My networking is totally working. I must have a MAC address since DHCP is giving me an IP address. I ran ifconfig ifcfg-bad on a failing system and ifconfig ifcfg-good after going back to the happy redboot. No real diff between the two files (except # of bytes/packages tx/rx). So I even got the same IP address from DHCP. -- notification area applets crash on login https://bugs.launchpad.net/bugs/392716 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 392716] [NEW] notification area applets crash on login
Public bug reported: Binary package hint: gnome-applets Release: Ubuntu 9.04 (modified, see below) on Babbage1 or Babbage2. The error is that notification applets reliably crash on login. We get about 10 message windows that say variations of The panel encountered a problem while loading OAFIID:GNOME_ClockApplet. Other applets that crashed were: WorkspaceSwitcherApplet, TrashApplet, WindowListApplet, FastUserSwitchApplet, ShowDesktopApplet, Mixer, IndicatorApplet, and NotificationAreaApplet. Babbage1: Booting with default release 9.04 from Canonical is fine. If I switch out the Redboot for a newer RedBoot (200925), the notification area applets all crash. We are looking to see what changed in RedBoot to cause this. The system is functional and stable, networking works, etc so any insights on what could cause these applets to crash on an otherwise apparently functional system would be helpful. To reproduce on Babbage1, take the Ubuntu 9.04 release and change the redboot. I have attached our 200925 redboot image. To update the redboot on the mmc card from a host (if it is /dev/sdc): # dd if=mx51_babbage_redboot-no-padding.bin of=/dev/sdc bs=512 seek=2 Babbage2: Release: Ubuntu 9.04 with an updated kernel image, no initrd, updated redboot If we boot with an ethernet cable plugged in, no error. Booting without the ethernet cable causes all the notification area applets to crash on login. ** Affects: gnome-applets (Ubuntu) Importance: Undecided Status: New -- notification area applets crash on login https://bugs.launchpad.net/bugs/392716 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 392716] Re: notification area applets crash on login
** Attachment added: Updated RedBoot for babbage1 http://launchpadlibrarian.net/28442516/mx51_babbage_redboot-no-padding.bin ** Description changed: Binary package hint: gnome-applets Release: Ubuntu 9.04 (modified, see below) on Babbage1 or Babbage2. - The error is that notification applets reliably crash on login. We get about 10 message windows that say variations of The panel encountered - a problem while loading OAFIID:GNOME_ClockApplet. Other applets that crashed were: WorkspaceSwitcherApplet, TrashApplet, WindowListApplet, FastUserSwitchApplet, ShowDesktopApplet, Mixer, IndicatorApplet, and NotificationAreaApplet. + The error is that notification applets reliably crash on login. We get + about 10 message windows that say variations of The panel encountered a + problem while loading OAFIID:GNOME_ClockApplet. Other applets that + crashed were: WorkspaceSwitcherApplet, TrashApplet, WindowListApplet, + FastUserSwitchApplet, ShowDesktopApplet, Mixer, IndicatorApplet, and + NotificationAreaApplet. Babbage1: Booting with default release 9.04 from Canonical is fine. If I switch out the Redboot for a newer RedBoot (200925), the notification area applets all crash. We are looking to see what changed in RedBoot to cause this. The system is functional and stable, networking works, etc so any insights on what could cause these applets to crash on an otherwise apparently functional system would be helpful. To reproduce on Babbage1, take the Ubuntu 9.04 release and change the redboot. I have attached our 200925 redboot image. To update the redboot on the mmc card from a host (if it is /dev/sdc): # dd if=mx51_babbage_redboot-no-padding.bin of=/dev/sdc bs=512 seek=2 Babbage2: Release: Ubuntu 9.04 with an updated kernel image, no initrd, updated redboot - If we boot with an ethernet cable plugged in, no error. Booting without the ethernet cable plugged in causes all the notification area applets to crash on login. + If we boot with an ethernet cable plugged in, no error. Booting without the ethernet cable causes all the notification area applets to crash on login. -- notification area applets crash on login https://bugs.launchpad.net/bugs/392716 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
