Hi all! I hope this is the right community for this, I have a rather strange issue with Firefox for Android, and I couldn't find any info on this particular bug(?).

For a while now (though I can't really put my finger on since when) I can't grant access in Firefox to location data. The small modal popup appears, but the button that should allow the use of my location just... doesn't do anything. I can press as many times as I want, but the dialog doesn't disappear, the button does not doing anything. I can see it gets pressed, but no effect.

But not always. Sometimes it works, but 90% of the time it won't. There are times when I can spam it till I die, other times the button gets pressed after a while, or after trying different angles to press the button. Yeah, I know, it sounds silly. And also, there are cases where it works right the first touch on the "Allow" button.

This feels even worse in Private Browsing session, tho I don't know is it technically worse, but it definitely feels worse.

I have the latest version of the browser that is available in the Play Store. Android version 14, running Samsung One UI 6.1.

Checking system settings lead to nowhere, it seems every relevant setting is OK, but I haven't changed anything around them in a good while.

As I said, I'm not sure whether a Firefox update or an Android/One UI system update caused this, or what else, it's like from one day to another, which makes it super weird.

Anyone having any idea? I haven't tried full data wipe on Firefox nor reinstalling it, I wouldn't really like to do that, but if there's nothing else, I may try that too.

Thank you guys and have a nice weekend ;)

I know, I know. I really shouldn't use NTFS with Linux if I plan to write to it, especially not my only backup drive, which is my external media drive for libreELEC as well.

So I was moving/copying/renaming stuff through SMB on my libreELEC machine. And then suddenly I noticed 50 episodes of old-school Sonic animated series just... disappeared. Strange, but I continued renaming files, and those too poof nonexistent anymore.

Okay, maybe a Dolphin bug - I thought, since I was using Dolphin for SMB. But same from Android (I'm using Solid Explorer)

Then, Ghost In The Shell Stand Alone Complex too disappeared. Then some episode of Serial Experiments Lain.

Star Trek Discovery? Fucking gone, tho I didn't mind that one. All of the files are 0B. Then Regular Show.

Now, this was the point where I needed to step in. Linux just didn't see the files.

Oh well, I have a Windows 10 PC I use for work so it was a time for bringing the drive "home" and give it some chkdsk, in the meantime I was really hoping it wouldn't just destroy my 4TB backup drive. Wasn't sure it would work, but that was pretty much my only hope and idea. Trying to access those folders and files from Windows gave me error messages before the check.

The check and fix dialog of chkdsk was also kinda fucked, the progressbar jumped around, didn't make any sense BUT it restored my files. Hooray!

Except SAC, it was still unreadable from Windows, but! Linux does see all the episodes so I guess it's a win... of some sort. It sill bothers me there is some - from Windows's point of view - invalid files and folders on my BACKUP disk, but this will be another story.

It turned out, libreELEC is using ntfs-3 (and not 3g), which is famous for this kind of errors - files disappearing and the filesystem becoming funky.

So, I ordered a drive just for my media and media PC, tho no idea how to format it (to be readable from anywhere else - maybe exFAT?)

But this scared me like hell 😅

Just wanted to share this with you guys, there's no moral of the story, except do not use ntfs heavily under Linux, or at least do not write it a lot, which is a known thing since forever, I was just a lazy ass, don't be like me, please, unless you have a Windows machine around and some luck. But relying on these two, well...

Cheers!

Update: I formatted my new media drive to ext4. In the end, it'll be a fixed disk under my TV in a linux box, this seemed to be the best choice. I don't think I'll pick it out and use it elsewhere that much or at all.

Hi guys! Hope this is the appropriate place to ask this question, but here it goes.

I have a Dell Inspiron 7520 laptop with integrated Intel and ATI graphics.

Recently I've installed Debian 12 on it, using Plasma.

Everything is fine and dandy, but there's a problem; when the system comes back from sleep, or I boot up the PC with the lid closed down, the screen never comes back. The system is running, but there is no screen.

Also, it's not just a blank screen, it does not get power, no backlight, no image on the screen if I shine a flashlight onto it and look hard.

Interrestingly, if I switch sessions to any ttys, the screen comes back and the terminal session displays fine. If I Alt+F7 back to the graphical session, the screen turns off again.

In theory, every graphics driver should be installed, I have non-free-firmware in my sources.list, all the packages that the Debian documentation mentions are installed.

Don't know, if relevant, but same on both X11 and Wayland.

Any ideas?

Thanks, guys :)

Some specs of the machine:

• CPU: Intel Core i7 (3rd Gen) 3612QM / 2.1 GHz
• GPU: Intel HD Graphics 4000 + AMD Radeon HD 7730M (switchable*)
• RAM: 16GB**

*: Not sure this switchable thingamajig works, tho. Haven't really tested, the only purpose of this machine is to start OBS and begin outputting video on NDI.

**: Though 16GB is not really supported on paper I guess and had some really funky issues before, not sure what was the real purpose, the system is rock solid since the last few OS installs.

Hey guys!

As you may all know, the Big N soon will shutdown all online services for the 3DS family and the Wii U. Surprising? Not much. But hurts nonetheless.

Though I personally don't really use actively my 3DS (and I also sold out from it a long time ago, still have 2, somewhat functioning O3DSs \:waiting to be repaired), I couldn't help but dust off my working console and went online.

Apart from the nerdgasm I had (since, 7 is my absolute favorite Mario Kart in every possible way) I couldn't help but notice how fucking awful the online was. Same 4-5 japanese dude, fully packed with cheats and hacks.

My heart was broken, but all that doesn't matter. This is why I'm kinda OK with the shutdown, tho I don't know about the other games. I mean, Mario Maker, Mario Kart 8, Splatoon, these all will be gone, and I'm sure lots of people have similar feelings towards their games like I do to MK7. So saying this could sound pretty harsh, but if this is the case with the other games as well - and the Wii U's also a pretty open and used book for hacks nowadays - maybe... it's really time. Honestly, it's just WILD how online gaming on the 3DS (and probably on the Wii U as well) works from today's standpoint.

But I just got off-tracks.

What I really wanted to talk about and just wanted to give a little bit of context for this, is Pretendo.

https://pretendo.network/

If you don't know about Pretendo, it's an open-source Nintendo Network implementation. Basically, you can create a PNID here on the normal way you would create an NNID on your machine, and all your 3DS online services are now routed to Pretendo. Currently, some games, but at least Mario Kart 7 online works, pretty much flawlessly (except Friend functions). But it's real, it works, it's amazing... just really empty.

You can find the list of the compatible games and their states.

It even has some kind of Miiverse alternative too up and running, called Juxtaposition.

Using a modded console, it's just a matter of installing a title. https://pretendo.network/docs/install You can change between Pretendo and Nintendo here.

Though use it at your own risk, as any homebrews that mess with the system in one or another way.

I'm maybe just too excited, but the online services will be killed off anyway, and I just love MK7 way too much, so I'm glad these people made it possible to run custom servers for it.

What do you guys think about it?

Hello guys!

I'm encountering some strange behaviour with audio controls and volumes, nothing extreme serious, just moderate annoyance source, so I thought maybe you can help me sort this one out! Also I hope this is the right community for this...

(intro)

The thing is, I'm running Debian Bookworm, with Plasma and I have a rather strange audio setup. It has its legacy reasons, but I use a sound card (CMI8738/CMI8768, it has 5.1 output), and as for the speakers, I've got a pair of active 2.0 speakers and an active subwoofer (which was a part of a 2.1 system, but now I just use only the woofer). These are connected separately to the card; the stereo pair goes to the green output jack (front) and the subwoofer goes to another, which I think is the center+woofer output.

For some reason, the center and woofer was swapped on my card, or the subwoofer was hooked to the other channel, no idea, but I was managed to change them in pulsaudio's config /usr/share/pulseaudio/alsa-mixer/profile-sets/default.conf and modifying [Mapping analog-surround-*], changing the order of lfe and front-center in channel-map.

Then I noticed I can't really control the woofer, it worked, the setup was working, but not in the way I wanted to. The goal was to make the system actually control the outputs as intended and think about it as a 2.1. Amongst the profiles, there were no 2.1 option, only stereo, quadrophonic, 5.1 and 7.1.

By adding this line to ~/.config/pulse/default.pa...

load-module module-combine channels=3 channel_map=front-left,front-right,lfe ...and also editing ~/.config/pulse/daemon.conf by adding these to it (tho honestly I don't really remember, why)...

remixing-produce-lfe = yes remixing-consume-lfe = yes lfe-crossover-freq = 120 enable-remixing = yes ...I was managed to create a virtual output that behaves actually like 2.1. I can control both left and right channels and also the woofer on its own. Neat!

(the problem)

Now I have two volume controls. One for the "real" output - the 5.1 profile and the virtual one, the 2.1.

In Plasma toolbar, changing the volume with the scroll wheel is unpredictable, or, at least, I haven't really figured out how it works at the moment; sometimes it controls the real output, sometimes the virtual. On my left screen, it usually controls the real, on the right, most of the times it controls the virtual. But it just changed at the moment as I tried out, typing this post. Now both of them controls the real one.

The goal would be to have the real output constantly on 100%, and every volume controlling action should be take place on the virtual output.

Also, another strange thing is that even tho it looks like everything is fine and dandy, the overall output is low. When this happens, usually on the real output the left, right and woofer channels themselves are changed to lower (probably a previous state of the virtual output) volumes.

This all seems pretty random and unpredictable. If it works, it's awesome, and problems doesn't occur for days, but sometimes they do, and I have no idea why.

Any ideas?

(tl;dr)

I'd like to know why my volume controls (scroll wheel, volume keys) have effect on seemingly random outputs, and why do the volume of each channel that is present in my virtual output get change ON the physical setup (so the left, right and subwoofer sliders in the 5.1 output) persistently.

Thanks!

Not sure if it's NSFW tho...

Hi all. Tho I have this problem a long time, I try to ask here too.

When I use PicoProbe for debug my code with Visual Studio Code (or Codium), can't get serial monitor working on the target Pico.

I have hooked up everything correctly, the probe's Rx/Tx GPIOs are connected to the target's UART0 Tx/Rx correctly (checked it, Tx-Rx and Rx-Tx, swapped it, no data at all. Tried to touch the wires to random spots, garbage appeared on the serial monitor, so the probe is probably listening)

Using USB as UART, connected directly to the target device does give me serial output, but through the probe and with UART, absolutely nothing.

I used the 'hello_serial' example project, built it with Codium (or VSCode), using the same plugins the pico_installer would setup. (MS CMake Tools, MS C++ tools and Cortex debug).

Debugging with openocd, or just running the built firmware on it's own and listening to it with the probe has the same result: nothing.

Same on Windows, same on Linux.

Anyone has any idea? I can program the Picos this way, but I really need serial for debugging. I could use two USB cables, but soonly enough that won't work.

Am I missing something? I did lots of search, but this feature should just work.

edit: fixed some typos

Not a major issue at all, just graphical, but I think it's good to know;

Using the app on a phone that has a narrower screen than normal (like Samsung booklike foldables outer display) can cause overflowing in some cases, like comment or post toolbars/button bars, as you can see on the screenshot.

There's no loss in functions.

Some obscure and hidden gem jungle/dnb mixed together, from modarchive.org.

!