Version v0.8.1. Android 16. Pixel 7 Pro.

After scrolling a couple pages (endless scrolling is on) I start seeing "Instance of 'LemmyApiException'". Once it starts, the tiniest amount of scrolling—even upwards—causes the error. I can make a bunch of rapid, itty bitty scrolls, and each one will hide and reshow the error.

What is Thunder doing with the API on every single scroll? Even up? Makes no sense.

I don't have "mark read on scroll" enabled, or anything odd. I haven't changed any settings in weeks, and this started happening just a few days ago. It might only be happening on my home instance. I could test with an alt.

Update: I can't reproduce this using a lemmy.world account

By viewing this post you are infected, and all future clocks you attempt to make will fail to render, too.

Update: It's worse than I thought. It's crashing my VPN! I use the Mullvad VPN app. After that crashes, Thunder crashes. This happens every time.

First, it slows way down and stutters a bit, then turns all black and crashes to my home screen.

Is this happening to anyone else?

Android 16. Pixel 7 Pro.

If not, can you please add a setting to disable it? It's just not for me. At best it's a distraction while I wait for the image to load. At worst, it blocks part of the image.

Android 16, Pixel 7 Pro. My Signal data was getting too bloated, so I backed it up, moved the backup to PC, and verified that signalbackup-tools can decrypt and extract the backup. Cool. Now I want to wipe the data in the app while not losing any settings or contacts or anything.

In the app, I went to Settings > Manage storage > Delete message history. It pops up two separate confirmations, and I hit "Yes" to both. After waiting a bit each time, I did this three time. It hasn't gone well.

• Signal storage settings still says it's using almost 9 GB of data.
• However, Android says Signal is using just 154 MB of user data.
• All of my conversations and messages are still in Signal, but the media in each conversation shows a broken icon.
• The "Review storage" screen in Signal still shows tons of media with thumbnails, but none open. Tapping on one just shows a blank camera roll and black space.

So, I went to "Review storage" and it let me do a select all and delete, saying, "Are you sure you want to do this? This will delete 9 GB of messages". I said yes, and it's still going. I hope this will at least delete the ghost media.

I suppose I could set a message duration in settings and let old chats expire, though I'm not really against keep the text messages. It was just years of cat photos and videos taking up way too much space.

But why isn't this feature working?

Update:

My phone screen turned off and when I re-opened it, the progress spinner on the delete progress is frozen. I can't cancel or anything. I can give it more time, and force close the app if I have to, but it's not looking good.

Update 2

I swiped the app away from the app switcher, and I was able to open it again and see conversations and such. When I opened settings, it showed that it was using 4.7 GB, and when i closed and reopened settings, it was s tiny bit smaller. Sure enough, after waiting a full hour, it now says it's only using 67 MB of storage, and all the thumbnails are gone from the media list. So... success?

I still have years worth of plain text messages, and I guess I don't mind that.

I woke up one day and Fennec wouldn't browse any web page. Like, if I do a search, which goes to DuckDuckGo, I get a loading bar that never goes anywhere. (See screenshot).

If I disable all of my extensions, it'll work again. Then, if I enable them one by one to try to find the culprit that was making Fennec not work, it doesn't break! Until it does, randomly. I basically can't easily reproduce it working or not working.

I switched to IronFox, and installed all the same extensions, and have had no problems for two days.

Extensions:

• JShelter
• UBlock Origin
• Decentraleyes
• Cookie AutoDelete
• Absolute Enable Right Click & Copy

Update #1

I fixed my boot issue, but now I have to fix the issue with snapper not working right.

The boot issue: Something—I don't know what—added a removable drive to fstab, and the error was that drive couldn't be mounted at boot. I have two guesses:

1. I formatted a microSD card using YaST Paritioner sometime before doing the distro upgrade.
2. The drive might have been mounted during the distro upgrade, though I don't think it was.

At any rate, I commented out that line in fstab and it booted right up.

Mullvad is working fine when I boot normally. I guess it was only broken when booting a snapshot from before I upgraded it.

Update #2

I also fixed /.snapshots by adding it to fstab. Now it gets mounted on every boot, and this version of fstab will be in all future snapshots. I just took a manual snapshot for good measure.

I don't know which action caused the issue, so I'm going to list everything I did. I'm new to OpenSUSE Tumbleweed, and I haven't used Linux since like Linux Mint 17.

1. I disabled KWallet because I got tired of typing in a password every time my desktop launched just for wifi passwords. I decided to just let Linux store them in plain text since my whole system is encrypted with LUKS.
2. I did a distro update. (zypper dup) After that succeeded, I logged off and back on.
3. I noticed Mullvad had a new version. They don't officially support OpenSUSE, so I downloaded the new RPM. I ran rpm -e mullvad-vpn to remove the old one. That might have been a mistake since my notes say I used zypper to install it the first time. I installed the new one with zypper. It launched and connected just fine.
4. I had some trouble getting network settings to store/retrieve my wifi password, so I decided to reboot my system since I changed so much stuff.
5. It wouldn't boot. I see a few "BIOS" and "ACPI" errors.
6. Time to try out Snapper! I reboot and choose the most recent snapshot from before tonight.
7. It boots, but when I try snapper rollback I get IO error (.snapshots is not a btrfs subvolume)
8. I get the same error trying to open the YaST snapshot viewer.
9. I check btrfs, and I see @/.snapshots plus a bunch of numbered snapshots, of course.
10. I check fstab, but I don't see an entry mounting anything on /.snapshots.
11. I do see a directory at /.snapshots, but it appears just be an empty directory.

Mullvad seems broken with this snapshot. I can't connect to the internet. The mullvad-daemon won't start, so I think the killswitch is active. I've had to type all this on my phone.

What can I do to fix this? I just want to rollback to this good snapshot, and then I can worry about fixing Mullvad when the filesystem isn't read-only.

One month. That's how long it took me to break my system. ☹️

I've had three comments in my inbox for about a week and every day I try to mark them as read, but it doesn't work. They disappear from the list at first, but then when I refresh they're still there. I get the error in the picture which says, LemmyApiException: couldnt_find_comment_reply

I just went to the website and logged into my instance, and I had no problem marking the comments read from there. They disappeared from my Thunder inbox, too, after a refresh.

I saved one of the comments for debugging purposes, in case there's something we can look at.

Talents:

I had a +10 Vampiric Katana, which was doing real work with the +5 Ring of Arcana.

During the run I found and ID'd a Grim weapon and Ring of Haste plus a bunch more. (Scroll of Divination is great for "finding" all rings for Trinity.)

I was using Grim for the entire ascent, one-shotting almost everything. First blind them, and then when they step into range, you get a guarenteed hit. That was killing almost everything with Grim. With Ring of Energy +4, I never once ran out of armor energy. The Heroic Energy talent was also key.

When I had to fight a scorpion, I could activate Spirit Form for Ring of Haste and chase them down with ease.

It was honestly one of the easiest ascents I've ever had. The flexibility of Trinity is really cool.

During the descent, I used it a bunch for thrown weapons to soften up blind enemies from a distance since I ran out during the run.