smeg

Most of the games I played back in the day had some way of resuming your progress at a later date, whether that was an actual save system, a password system, or even a hidden warp zone. What were you supposed to do for longer games that had no way at all of resuming your progress after switching the console off? Get good enough at the start of it that you could play the game faster and eventually complete it in one go, or just leave the console on overnight and continue the next day?

(and yes, my Mega Drive is currently sitting powered on because I couldn't think of a better way to keep my progress)

Background: I've been running Linux Mint XFCE for a couple of years now, Windows 10 has been sitting unused on a separate drive but it turns out the one thing I need it for works passably in a VM so it's time to bin it. I've used Fedora Atomic (UBlue) on some laptops and I like it so that seems like a good candidate to replace the Windows install, and Mint can hang around for when I need a "normal" Linux install.

Worry: I tried dual-booting them together on a laptop before and I couldn't get grub to recognise both installs, it only detected the most recently installed one and after an evening of running commands way beyond my knowledge I gave up. I'm hoping that's just because I installed them on the same disk though.

Question: does anyone successfully dual-boot a Fedora Atomic install and a "normal" install? If so then what did you do to set it up and did you encounter any issues? And if you're feeling extra helpful, do you have any pro tips for setting up shared storage between the two distros or backups for either?

I've stopped using Google Photos but haven't really found a suitable android app (or two separate ones) which can replace two main features:

1. One-click post-processing - I think Google called it something like "auto awesome", basically a single button which slightly tweaked brightness, contrast, and presumably a few other things to make snaps look a bit better
2. Automatic backup - I've tried proton drive but the app is a bit slow to load thumbnails, and critically it's a one-way copy so you have to manually re-delete everything from your phone

Any recommendations for apps which can replace these features? Doesn't have to be all-in-one, and FOSS is preferred!

I tried to launch a game from Heroic on the Deck for the first time in a month or so and it's loading for a few seconds and then exiting.

• Same from game mode or desktop
• Same for different proton versions
• Same for Epic, GOG, and Amazon games
• Same after reinstalling a game
• Other Steam and non-Steam games run fine

I've probably applied several updates since I last ran a game so no doubt a huge number of things have changed since the last good state. I can't see anyone else reporting similar issues so I know it's very optimistic from me, but does anyone have any suggestions? Even an idea of how to get some logs out would be useful!

Many in the Proton community have been asking for an update on the Proton Drive SDK — especially developers eager to help build new clients or to integrate Drive into their apps. Linux users will be happy to hear that this SDK is a step toward offering a client, something we know is highly anticipated. Today, we’re sharing an early preview of our SDK work.

Important: This SDK is a work in progress. It’s not ready for production use or third-party apps yet. We’re sharing it to give you a look at what we’re building and to get insights on how you could use it — not for you to start building with it just yet.

cross-posted from the Linux phones community as nobody there knew

Has anyone actually successfully installed PostmarketOS on an old device recently? I've had a long struggle through trying to prepare a Nexus 7 (2012) and the result seems to be a dead device before I even got to actually installing PostmarketOS.

The rough steps I followed are listed here:

• Create backups
• Get SBK
• Build and prepare U-Boot
  • Actually flashing U-Boot seems to be where things went wrong
    • Running ./run_bootloader.sh -s T30 -t ./bct/grouper.bct -b ../re-crypt/repart-block.bin or ./run_bootloader.sh -s T30 -t ./bct/grouper.bct -b ../generated-wheelie-blobs/AndroidRoot/blob.bin from fusee-tools hung on waiting for bootloader to initialize
    • Running ./run_bootloader.sh -s T30 -t ./bct/grouper.bct -b ../u-boot/u-boot-dtb-tegra.bin failed like this
    • skipping that step and running ./utils/nvflash_v1.13.87205 --resume --rawdevicewrite 0 1024 ../re-crypt/repart-block.bin hung on [resume mode]
    • Consulting a different version of the docs and running ./wheelie --blob ./generated-wheelie-blobs/AndroidRoot/blob.bin seemed to work so I ran ./nvflash --resume --rawdevicewrite 0 1024 ./re-crypt/repart-block.bin which also seemed to work
    • I then powered off as instructed and the device has been completely unresponsive since

I've tried connecting to a charger, disconnecting and reconnecting the battery, and every combination of holding down buttons but it appears to be completely dead. Any suggestions as to what I did wrong or anything I might be able to do now? Obviously it's not the end of the world to have lost a 13 year old tablet that was just gathering dust, but at the moment I'm not feeling positive about ever trying this again on another device!

cross-posted from the Linux phones community as nobody there knew

Has anyone actually successfully installed PostmarketOS on an old device recently? I've had a long struggle through trying to prepare a Nexus 7 (2012) and the result seems to be a dead device before I even got to actually installing PostmarketOS.

The rough steps I followed are listed here:

• Create backups
• Get SBK
• Build and prepare U-Boot
  • Actually flashing U-Boot seems to be where things went wrong
    • Running ./run_bootloader.sh -s T30 -t ./bct/grouper.bct -b ../re-crypt/repart-block.bin or ./run_bootloader.sh -s T30 -t ./bct/grouper.bct -b ../generated-wheelie-blobs/AndroidRoot/blob.bin from fusee-tools hung on waiting for bootloader to initialize
    • Running ./run_bootloader.sh -s T30 -t ./bct/grouper.bct -b ../u-boot/u-boot-dtb-tegra.bin failed like this
    • skipping that step and running ./utils/nvflash_v1.13.87205 --resume --rawdevicewrite 0 1024 ../re-crypt/repart-block.bin hung on [resume mode]
    • Consulting a different version of the docs and running ./wheelie --blob ./generated-wheelie-blobs/AndroidRoot/blob.bin seemed to work so I ran ./nvflash --resume --rawdevicewrite 0 1024 ./re-crypt/repart-block.bin which also seemed to work
    • I then powered off as instructed and the device has been completely unresponsive since

I've tried connecting to a charger, disconnecting and reconnecting the battery, and every combination of holding down buttons but it appears to be completely dead. Any suggestions as to what I did wrong or anything I might be able to do now? Obviously it's not the end of the world to have lost a 13 year old tablet that was just gathering dust, but at the moment I'm not feeling positive about ever trying this again on another device!

Has anyone actually successfully installed PostmarketOS on an old device recently? I've had a long struggle through trying to prepare a Nexus 7 (2012) and the result seems to be a dead device before I even got to actually installing PostmarketOS.

The rough steps I followed are listed here:

• Create backups
• Get SBK
• Build and prepare U-Boot
  • Actually flashing U-Boot seems to be where things went wrong
    • Running ./run_bootloader.sh -s T30 -t ./bct/grouper.bct -b ../re-crypt/repart-block.bin or ./run_bootloader.sh -s T30 -t ./bct/grouper.bct -b ../generated-wheelie-blobs/AndroidRoot/blob.bin from fusee-tools hung on waiting for bootloader to initialize
    • Running ./run_bootloader.sh -s T30 -t ./bct/grouper.bct -b ../u-boot/u-boot-dtb-tegra.bin failed like this
    • skipping that step and running ./utils/nvflash_v1.13.87205 --resume --rawdevicewrite 0 1024 ../re-crypt/repart-block.bin hung on [resume mode]
    • Consulting a different version of the docs and running ./wheelie --blob ./generated-wheelie-blobs/AndroidRoot/blob.bin seemed to work so I ran ./nvflash --resume --rawdevicewrite 0 1024 ./re-crypt/repart-block.bin which also seemed to work
    • I then powered off as instructed and the device has been completely unresponsive since

I've tried connecting to a charger, disconnecting and reconnecting the battery, and every combination of holding down buttons but it appears to be completely dead. Any suggestions as to what I did wrong or anything I might be able to do now? Obviously it's not the end of the world to have lost a 13 year old tablet that was just gathering dust, but at the moment I'm not feeling positive about ever trying this again on another device!

Some posts (e.g. this and this) do not load the images in Summit but load fine in the web ui. Summit gives this error:

stream was reset: PROTOCOL_ERROR

This post contains quite a lot of formatting. It looks fine in the web ui but Summit seems to mess it up (I think maybe it's trying to put it all under one of the >?)

Source and bonus panel

I looked at this post in Summit and it's just showing an image post, but when I view it in the web ui there's a linked article. Have I hidden it in some setting or is Summit not showing the link?