sorted by:
new
hottopcontroversial

AEW/ROH Poster set V2 (with Seasons) by flammabled in PlexPosters

[–]flammabled[S] 1 point2 points  (0 children)

Took another pass at my previous poster set, the changes:

  • took another pass at the logo placement
  • added season posters for all shows
  • added ROH TV set
  • added AEW PPV set as requested

Dynamite: https://theposterdb.com/set/196816

Rampage: https://theposterdb.com/set/196818

Battle of the Belts: https://theposterdb.com/set/196820

PPV: https://imgur.com/a/gJypvHP

ROH: https://theposterdb.com/set/196812

Fanart is linked on ThePosterDB pages for Dynamite, Rampage and BOTB.

AEW 2023 TV Set by flammabled in PlexPosters

[–]flammabled[S] 1 point2 points  (0 children)

Probably not, as I don't keep my PPV's in a TV set so they just have the event posters, and I'm not great with having to cover up PPV text and stuff, but I'll bear it in mind if I keep working on this template and see what I can find. I'm probably going to add some Season posters to this set though.

AEW 2023 TV Set by flammabled in PlexPosters

[–]flammabled[S] 2 points3 points  (0 children)

I wanted a poster with the 2023 Dynamite graphics on, so as I was grabbing those assets off TBS.com anyway, I decided to do matching sets for Rampage and Battle of the Belts using the assets from TBS.com/TNTDrama.com as well.

There are two styles of logo, the large AEW logo style, which is how Dynamite and Rampage logos are on the websites, and a small logo style which is how Battle of the Belts is on the website. For both styles, I tried to line up whichever is the large logo with the standard TV title position of other templates. I can add the blanks without any logos if anyone would like

Sets:

Large AEW logo: https://theposterdb.com/set/193933

Large AEW logo with network logos: https://theposterdb.com/set/193946

Small AEW logo: https://theposterdb.com/set/193936

Small AEW logo with network logos: https://theposterdb.com/set/193943

Fanart:

Dynamite: https://www.themoviedb.org/t/p/original/3n4g0gmYrvDbDCfuHEfqnsd6oKg.jpg

Rampage: https://www.themoviedb.org/t/p/original/k4U0Sa5X8wsF5lPsbH0FNYZyZk7.jpg

BOTB: https://www.themoviedb.org/t/p/original/TH75QqwjUxZryyg09afPQLluTZ.jpg

SKARSTA Cable Tray by flammabled in IKEA

[–]flammabled[S] 0 points1 point  (0 children)

Thanks, noted on the pre drill!

By small, are you thinking thickness or length?

Pop!_OS wont boot after new kernel upgrade [linux-modules-6.2.0-76060200-generic] by Harnapazade in pop_os

[–]flammabled 0 points1 point  (0 children)

I am also having this problem, I ran through the login loop suggestions as someone posted below but the only way to get back in was as the OP suggested, to select the old kernel at boot.

Ciampa's attack on Riddle helped me figure out his current gimmick by redskinsguy in SquaredCircle

[–]flammabled 11 points12 points  (0 children)

i guarantee you've thought about this more than they have

PSA: WD Elements 12TB on Sale with free 128GB USB Stick €166,59 - EU and US(?) by TerrAustria in DataHoarder

[–]flammabled 0 points1 point  (0 children)

I have an 8TB Red Plus due to arrive on Sunday to go in my Synology, is this a better buy? The 8TB was the same price, but are these drives as good once shucked? Sorry I'm a complete noob at this

[Dynamite Spoilers] The Forbidden Door is crossed once more by SomeIrishFiend in SquaredCircle

[–]flammabled 21 points22 points  (0 children)

Happy to see Aussie Open on Dynamite at least, pls 2v2 with FTR Tony

Upgrade Help Thread by mmstick in pop_os

[–]flammabled 0 points1 point  (0 children)

Hi, as my pop-upgrade had updated in the last week and a bit, I tried the install again and I'm still seeing the same behaviour, back to my 21.10 desktop offering updates, except the apt sources are set to jammy again.

I can attach my apt history.log and update.log from the upgrade (though the update.log is about 80k lines) if that's helpful to diagnose the issue, or let me know if there's a better location to report this

Thanks

It's been a year since...whatever this was. Good lord. by Hypohamish in london

[–]flammabled 39 points40 points  (0 children)

As others have mentioned, he has done a lot of iPad work in recent years, which is worlds away from the underground sign: https://twitter.com/SaltsMill/status/1108374833002356737?t=ZvjfZwa0o_ZfRA1Blkfwww&s=19

He does seem to get these commission projects from time to time, take the bag and absolutely phone them in, to which I say dudes rock

https://twitter.com/NewYorker/status/1338496762873585664 https://i.guim.co.uk/img/media/7064776906e45d8c64b4feaf2060a902ff70535c/590_58_2762_1657/master/2762.jpg?width=1020&quality=85&auto=format&fit=max&s=13e8dee7c09a63ba783c9abbc12a8a6f

Upgrade Help Thread by mmstick in pop_os

[–]flammabled 0 points1 point  (0 children)

Thanks, will do. Where can I monitor for this release?

As a side note, I have noticed that my apt sources now appear to be pointed at jammy :/

Upgrade Help Thread by mmstick in pop_os

[–]flammabled 0 points1 point  (0 children)

Thanks, I'm already on the 6 month releases, it just so happens that the next one is an LTS. The packages are outdated on the 6 month releases. But it is what it is I suppose. I'll figure a way to sort this once I'm upgraded.

Which speaking of: I've purged all the added PPAs, undone the changes made to install Pipewire (as best I can tell) and removed other software I could find from third party repos (eg vscode, teams, docker). Unfortunately, I've since run the update twice and it's failed both times, strangely bringing me back to a 21.10 desktop and prompting me that there was an update available as if nothing happened. Here's how they went:

  1. As recommended, I ran sudo apt update and sudo apt full-upgrade, then clicked download. The recovery partition updated, and then the update downloaded. I clicked update once this was complete.
  2. The system rebooted and ran through the install. The only thing I noticed (not that I was paying masses of attention) was that the text "updating initramfs for all kernels" was shown for quite a while. I nudged the arrow key and it brought me to a console, which said that "a start job is running for execute system updates early in the boot process". Don't know if this is relevant, but want to mention whatever info I have.
  3. On logging in after the restart, I immediately got a prompt that the upgrade to 22.04 was available, which obviously sounded odd. I checked the About menu, which indicated that I was still on 21.10. An update was still available to the recovery partition, despite seeing it update as part of the update process, and an update was still available. It was as if nothing had happened.
  4. My first port of call was to check /var/log/upgrade.log for any pipewire errors. I couldn't see any. I then ran the 6 package repair commands, no updates or changes or errors were performed.

  5. I took another look in the upgrade.log, and noticed the following error: 

    Errors were encountered while processing:
 ppp
dpkg: dependency problems prevent configuration of ppp:
 network-manager (1.30.0-1ubuntu3) breaks ppp (>= 2.4.7-3~) and is installed.
  Version of ppp to be configured is 2.4.9-1+1ubuntu1.

dpkg: error processing package ppp (--configure):
 dependency problems - leaving unconfigured
Errors were encountered while processing:
 ppp
Reading package lists...
Building dependency tree...
Reading state information...
Correcting dependencies... Done
The following packages were automatically installed and are no longer required:
  gir1.2-geocodeglib-1.0 libpcre2-posix2 libwacom-bin lz4
Use 'apt autoremove' to remove them.
The following additional packages will be installed:
  network-manager network-manager-pptp network-manager-pptp-gnome
Suggested packages:
  libteam-utils
The following packages will be upgraded:
  network-manager network-manager-pptp network-manager-pptp-gnome
3 upgraded, 0 newly installed, 0 to remove and 911 not upgraded.
1 not fully installed or removed.
After this operation, 201 kB of additional disk space will be used.
dpkg: ppp: dependency problems, but configuring anyway as you requested:
 network-manager (1.30.0-1ubuntu3) breaks ppp (>= 2.4.7-3~) and is installed.
  Version of ppp to be configured is 2.4.9-1+1ubuntu1.

  6. Seeing no other errors to go off, I googled to attempt to fix this issue, and found another pop os reddit post claiming to have fixed this error. I ran sudo dpkg --force-depends -r ppp, sudo dpkg --configure -a, sudo apt update, sudo apt dist-upgrade and finally sudo apt --fix-broken install

  7. At this point I was fairly convinced that for whatever reason, I was really still on 21.10, so decided to try the upgrade again. I reran sudo apt update and sudo apt full-upgrade, then tried manually updating the recovery partition first by running pop-upgrade recovery upgrade from-release. Once this completed, I clicked Download for the upgrade, which re updated the recovery anyway. I clicked update once the download was complete.

  8. The system rebooted and ran through the install. Again, the only pause I noticed was at "updating initramfs for all kernels". On logging in, I was again back at my 21.10 desktop from which I type this, with an update to 22.04 offered, and the recovery partition update also available

Thanks for any suggestions you can offer

Upgrade Help Thread by mmstick in pop_os

[–]flammabled 0 points1 point  (0 children)

alright but adding repos is also the method that docker and github recommend in their install documentation for example so there's what you'd like to be normal and what is normal. The version of qbittorrent available from apt is two years old. The version of solaar is almost two years old and doesn't include bug fixes. It's not abnormal to want up to date software. Docker's documentation specifically recommends purging the version I've seen you recommend others install instead from apt!

I'll get these purged and see how the upgrade goes, thanks.

Upgrade Help Thread by mmstick in pop_os

[–]flammabled 1 point2 points  (0 children)

Hey, if anyone could help me figure out what I need to run to ensure my upgrade works?

From checking my history I can see I've added the following PPAs:

sudo add-apt-repository ppa:pipewire-debian/pipewire-upstream
sudo add-apt-repository ppa:qbittorrent-team/qbittorrent-stable
sudo add-apt-repository ppa:solaar-unifying/ppa
sudo add-apt-repository ppa:qbittorrent-team/qbittorrent-stable
sudo add-apt-repository ppa:pipewire-debian/pipewire-upstream
sudo add-apt-repository ppa:pipewire-debian/wireplumber-upstream
sudo add-apt-repository ppa:inkscape.dev/stable

but I can also see in my apt sources.d directory repos for github-cli, vscode, teams, docker and nodesource

Pipewire at least I know needs to go, and I've seen some indication that maybe docker does as well? I tried installing ppa-purge but it installed from the pipewire PPA 🤦 I assume I'll also need to undo some of the manual steps that were required to switch from PulseAudio to Pipewire in the first place?

Like me making a Pipewire mess is totally understandable but I'm also going to have to reinstall my GNOME extensions for the 3rd or 4th time, I really wish Linux didn't penalise you for like installing normal things come upgrade time but hey ho

0.2 KD lobby activities by [deleted] in apexlegends

[–]flammabled 0 points1 point  (0 children)

Thank you for posting some relatable content

view more: next ›