[Bug 1582871] [NEW] fraunhoffer glitches
Public bug reported: im guessing this is the right package here.(the hell theres no liblame...) -heaven forbid we use non-free COMMON codecs here, but Im getting a weird glitch and its been happening for some years now. Maybe upstream debian code. You play music. time passes. You hear glitches in the music like brownout or a bad tape. But these are mp3s...you replay the file position and it sounds fine. process repeats. my files are otherwise fine. ---and I cant use mp3 diags to fix my files, it keeps saying it needs to reload. this should never be. Im thinking its a glitch in the codec somewhere. happens randomly but peridically repeatable when playing back music. Im on SATA 8mb buffered drive with GIGS of RAM and hardly nuthin running. This shouldnt be happening. Dunno if vorbis has this issue because all of my hardware(even itunes) prefers mp3. nightengale more specifically is restricted now to free only and im not seeing the option for plugin as non-free mp3 support. ubu plays FREE codecs fine, so y use nightengale? (pointless drivel) but multiple projects are affected by this. rpmfusion was notified of this but shrugs shoulders as what to do. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1582871 Title: fraunhoffer glitches To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1582871/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1582866] [NEW] systemctl glitches
Public bug reported: getting weird complaints on boot but I cant diagnose them. This was not the case on install. note that I have cloned the drive onto a smaller laptop and I had boot issues because of it, so maybe CZ has some issues copying data somewhere.But that shouldnt affect the system. /proc is created on boot, right? or is there a way to re-create it? -- systemd-modules-load.service: sysctl: cannot stat /proc/sys/status: No such file or directory sysctl: cannot stat /proc/sys/systemd-modules-load/service: No such file or directory [me@livingroom] ~ $ sudo sysctl status systemd-network.service sysctl: cannot stat /proc/sys/status: No such file or directory sysctl: cannot stat /proc/sys/systemd-network/service: No such file or directory [me@livingroom] ~ $ sudo sysctl status sysctl: cannot stat /proc/sys/status: No such file or directory [me@livingroom] ~ $ -- yet these exact processes complain and FAIL to load. hmmm ** Affects: systemd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1582866 Title: systemctl glitches To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1582866/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1581719] [NEW] banshee aborts on horse-poo
Public bug reported: plugging in a i(phone in this case) anything while listening to banshee causes internal failure, removal of device and banshee to abort. iirc, banshee should pick up the device. its a 5s. I have force disabled pulse and am on alsa. instructions for this are elsewhere. touche for this but pulse is as busted as gnome3. THIS SHOULD NOT HAPPEN. hardware is internal to the motherboard and REMOVAL NOTICES are beligerent and acinine and NONSENSE. NOTHING is REMOVED. ALC 889 INTEL driver on CrossHairV(mind you a known SIN board but..) MUST certainly be broken. also whist reporting this one: Unhandled Exception: System.ExecutionEngineException: Couldn't create thread at (wrapper managed-to-native) System.Threading.ThreadPool:RequestWorkerThread () at System.Threading.ThreadPoolWorkQueue.EnsureThreadRequested () <0x7f8adf834790 + 0x00044> in :0 at System.Threading.ThreadPoolWorkQueue.Dispatch () <0x7f8adf834cc0 + 0x000fc> in :0 at System.Threading._ThreadPoolWaitCallback.PerformWaitCallback () <0x7f8adf836530 + 0x8> in :0 Unhandled Exception: System.ExecutionEngineException: Couldn't create thread at (wrapper managed-to-native) System.Threading.ThreadPool:RequestWorkerThread () at System.Threading.ThreadPoolWorkQueue.EnsureThreadRequested () <0x7f8adf834790 + 0x00044> in :0 at System.Threading.ThreadPoolWorkQueue.Dispatch () <0x7f8adf834cc0 + 0x000fc> in :0 at System.Threading._ThreadPoolWaitCallback.PerformWaitCallback () <0x7f8adf836530 + 0x8> in :0 yes I have caps (500) but if your threading over 500 we have an issue. you are trying to forkbomb the system. only fedora as native prevention and mitigation techniques that work OOBE.YOu have to force them on debian based systems. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1581719 Title: banshee aborts on horse-poo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1581719/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
