raspberrypi / Raspberry-Pi-OS-64bit

Repository for containing issues on the 64 bit operating system (as distinct from the 32 bit one)
466 stars 21 forks source link

cubicSDR and the new Raspberry Bullseye (bugs) #199

Open raspi-rick opened 2 years ago

raspi-rick commented 2 years ago

Hello. Today I installed the new Raspberry OS (Bullseye) in my Raspberry Pi 4B. Then I installed CubicSDR v0.2.5 from the repository. This application has a bug that did not happen in the previous version of Raspberry OS. For example, to set the frequency of 150.1 MHz, the input jumps from 149.1 to 151.1 This problem did not happen with the previous version of Raspberry OS, even if the version of CubicSDR is the same. I hope you can fix this bug in the next update of Raspberry OS. Thank you. PS: another bug is that "start recording" and "stop recording" appear in light gray background with white fonts, which is hard to read.

JamesH65 commented 2 years ago

I've edited the original post - it had some really weird formatting in it. Content remains the same.

lurch commented 2 years ago

I suspect this issue probably belongs at https://github.com/RPi-Distro/repo/issues rather than in the 64-bit-beta-issues repo?

raspi-rick commented 2 years ago

This was posted at the request of Kitti at raspberry.com. See below. I am not familiar with GitHub and this is my first post. Please feel free to move this post to a more appropriate section if you think it is necessary. Thanks.

Hi Rick, Thank you for getting in touch. ​Please could you report the issue on the github forums at https://github.com/raspberrypi/Raspberry-Pi-OS-64bit/issues ​Kind regards, ​Kitti

JamesH65 commented 2 years ago

Hmm, tried to transfer the issues, but moving to RPi-Distro does not seem possible, perhaps different organisations?

JamesH65 commented 2 years ago

With regard to the issue, I think this is actually an issue with CubicSDR anyway, we don't have any in house knowledge of it, so are very unlikely to look at it. I'd suggest reporting to the CubicSDR devs.

XECDesign commented 2 years ago

Yeah, this doesn't sound like a Raspberry Pi OS issue. We don't modify that package in any way, so the issue would need to go upstream or to Debian (assuming it also occurs there). If there's a patch that fixes the issues, we could pull it in.