1
00:00:00,160 --> 00:00:05,759
The Linux Challenge 2026 edition was

2
00:00:03,040 --> 00:00:08,320
supposed to be a three-part series.

3
00:00:05,759 --> 00:00:11,360
>> The setup, a taskoff challenge episode

4
00:00:08,320 --> 00:00:12,160
testing day-to-day usability, and a

5
00:00:11,360 --> 00:00:15,040
conclusion.

6
00:00:12,160 --> 00:00:18,560
>> But then the first week was full of so

7
00:00:15,040 --> 00:00:20,480
many unexpected highs and lows. We knew

8
00:00:18,560 --> 00:00:22,160
there had to be another video,

9
00:00:20,480 --> 00:00:25,199
especially after the Linux community

10
00:00:22,160 --> 00:00:26,855
exploded after I picked Pop OS again.

11
00:00:25,199 --> 00:00:29,119
And while Luke and I seem to have

12
00:00:26,855 --> 00:00:31,599
[music] been praised for our choices, I

13
00:00:29,119 --> 00:00:33,360
can tell you guys firsthand that it has

14
00:00:31,599 --> 00:00:35,280
not been a smooth ride for me.

15
00:00:33,360 --> 00:00:37,600
>> Meanwhile, things were going so great

16
00:00:35,280 --> 00:00:40,320
for me, I decided to dip my toes even

17
00:00:37,600 --> 00:00:42,320
further, attempting some more complex

18
00:00:40,320 --> 00:00:44,239
tasks that I didn't expect to [music] go

19
00:00:42,320 --> 00:00:44,719
super well, just to see what would

20
00:00:44,239 --> 00:00:47,440
happen.

21
00:00:44,719 --> 00:00:48,960
>> And I ended up trying some other dros,

22
00:00:47,440 --> 00:00:51,200
which addressed some of my issues with

23
00:00:48,960 --> 00:00:53,199
Pop OS, but uh also ended up being

24
00:00:51,200 --> 00:00:55,199
frustrating in their own ways. But what

25
00:00:53,199 --> 00:00:56,480
is even more frustrating is that they

26
00:00:55,199 --> 00:00:58,800
aren't letting me be the one.

27
00:00:56,480 --> 00:01:01,039
>> It's a segue to our sponsor,

28
00:00:58,800 --> 00:01:03,760
>> Threat Locker. Threat Locker helps

29
00:01:01,039 --> 00:01:05,680
organizations stay in control as AI

30
00:01:03,760 --> 00:01:08,240
becomes part of the workplace because

31
00:01:05,680 --> 00:01:10,960
it's important to limit what AI tools

32
00:01:08,240 --> 00:01:13,280
can do and what they can access. Threat

33
00:01:10,960 --> 00:01:15,520
Locker zero trust controls help reduce

34
00:01:13,280 --> 00:01:18,520
these risks. Learn more at our link down

35
00:01:15,520 --> 00:01:18,520
below.

36
00:01:24,799 --> 00:01:29,040
I feel like I've got to start this by

37
00:01:26,720 --> 00:01:32,960
explaining my brain deadad choice of

38
00:01:29,040 --> 00:01:35,520
Papo. It was amazing how many people got

39
00:01:32,960 --> 00:01:38,000
angry at me for picking the same DRO

40
00:01:35,520 --> 00:01:40,000
that screwed me over last time. But if

41
00:01:38,000 --> 00:01:43,040
you guys remember, I actually used

42
00:01:40,000 --> 00:01:45,040
Mangaro last time after I was assured

43
00:01:43,040 --> 00:01:47,759
that the bug that I encountered when I

44
00:01:45,040 --> 00:01:50,479
was setting up Pop OS was a one-time

45
00:01:47,759 --> 00:01:53,040
fluke. And then I got piled on for being

46
00:01:50,479 --> 00:01:55,600
so quick to abandon it. So this is me

47
00:01:53,040 --> 00:01:57,920
putting aside my past experience after

48
00:01:55,600 --> 00:01:59,920
seeing so many people listicles and chat

49
00:01:57,920 --> 00:02:02,880
bots that still recommend it. That

50
00:01:59,920 --> 00:02:05,119
willingness to try again is a good thing

51
00:02:02,880 --> 00:02:07,280
for Linux. I mean if everybody bailed

52
00:02:05,119 --> 00:02:09,599
after one bad experience, there would be

53
00:02:07,280 --> 00:02:11,440
no distros left to try. Nothing is

54
00:02:09,599 --> 00:02:14,080
perfect. And unfortunately that goes

55
00:02:11,440 --> 00:02:16,000
especially for Pop OS. System 76 has

56
00:02:14,080 --> 00:02:18,000
spent the last couple of years hard at

57
00:02:16,000 --> 00:02:21,360
work on a new desktop environment,

58
00:02:18,000 --> 00:02:23,920
Cosmic, and it's been a challenge.

59
00:02:21,360 --> 00:02:25,599
>> Lionus, Cosmic is basically in beta.

60
00:02:23,920 --> 00:02:28,720
Don't you know that it's not ready yet?

61
00:02:25,599 --> 00:02:30,640
>> No, I didn't. For one thing, where does

62
00:02:28,720 --> 00:02:34,000
it say that? The thing that I downloaded

63
00:02:30,640 --> 00:02:36,720
was called LTS or long-term support.

64
00:02:34,000 --> 00:02:38,239
That's like the opposite of beta. I

65
00:02:36,720 --> 00:02:41,200
would have had to journey to a random

66
00:02:38,239 --> 00:02:43,760
blog post from back in September of 2025

67
00:02:41,200 --> 00:02:46,239
to discover that Cosmic is now in public

68
00:02:43,760 --> 00:02:49,280
beta. Number two, maybe this is a hot

69
00:02:46,239 --> 00:02:51,120
take, but maybe if System 76, a

70
00:02:49,280 --> 00:02:53,040
commercial entity, not a random open

71
00:02:51,120 --> 00:02:55,200
source contributor, knows that it's not

72
00:02:53,040 --> 00:02:57,040
ready for prime time, instead of blaming

73
00:02:55,200 --> 00:02:58,959
me, we should probably blame the company

74
00:02:57,040 --> 00:03:01,200
that shipped it. And you know what?

75
00:02:58,959 --> 00:03:02,720
Yeah, I could have come across some of

76
00:03:01,200 --> 00:03:04,480
the Linux YouTube channels that have

77
00:03:02,720 --> 00:03:06,400
highlighted these issues. But a key

78
00:03:04,480 --> 00:03:08,640
element of the Linux challenge is

79
00:03:06,400 --> 00:03:10,959
highlighting that unless you know to ask

80
00:03:08,640 --> 00:03:13,680
the question, is this DRO's desktop

81
00:03:10,959 --> 00:03:16,000
environment in beta, it can be hard for

82
00:03:13,680 --> 00:03:18,480
new Penguin Curious users to find the

83
00:03:16,000 --> 00:03:20,080
right answers. So, as we keep going,

84
00:03:18,480 --> 00:03:22,480
it's important to think of the Linux

85
00:03:20,080 --> 00:03:25,599
challenge not as an attack on Linux, but

86
00:03:22,480 --> 00:03:28,000
as more of a pen test for how friendly

87
00:03:25,599 --> 00:03:30,159
it is to newbies. My Basite adventure

88
00:03:28,000 --> 00:03:32,640
started a bit better than Lionus at

89
00:03:30,159 --> 00:03:36,000
first. But if you remember in part one,

90
00:03:32,640 --> 00:03:38,720
I mounted my SMB share. I was shocked at

91
00:03:36,000 --> 00:03:40,640
how easy it was to find cuz normally on

92
00:03:38,720 --> 00:03:43,519
Windows I would have to type in the

93
00:03:40,640 --> 00:03:45,440
address bar and find it versus on Basite

94
00:03:43,519 --> 00:03:48,000
I just clicked on network and it found

95
00:03:45,440 --> 00:03:50,959
it right away. But I didn't realize that

96
00:03:48,000 --> 00:03:53,040
that wasn't mounting it. That was just

97
00:03:50,959 --> 00:03:55,280
creating a shortcut. This means my read

98
00:03:53,040 --> 00:03:57,680
and write permissions were all over the

99
00:03:55,280 --> 00:04:00,319
place and I couldn't save some files to

100
00:03:57,680 --> 00:04:02,159
my network drive if I clicked on that

101
00:04:00,319 --> 00:04:03,680
shortcut. To solve this, I had to do

102
00:04:02,159 --> 00:04:06,480
some Googling and I found out that I

103
00:04:03,680 --> 00:04:09,040
needed to modify my FS tab file to point

104
00:04:06,480 --> 00:04:11,680
the network location to the Mnt folder

105
00:04:09,040 --> 00:04:14,080
on my drive. So, I did that. But then I

106
00:04:11,680 --> 00:04:16,639
noticed that I had two, both of which

107
00:04:14,080 --> 00:04:18,400
were still behaving like a shortcut. I

108
00:04:16,639 --> 00:04:20,400
tried at least a dozen different options

109
00:04:18,400 --> 00:04:22,560
in order to mount the share correctly.

110
00:04:20,400 --> 00:04:24,080
None of which ultimately succeeded or

111
00:04:22,560 --> 00:04:26,400
should have even been necessary if you

112
00:04:24,080 --> 00:04:28,560
ask me. Opening context menus on icons,

113
00:04:26,400 --> 00:04:31,440
shortcuts, or applications is a great

114
00:04:28,560 --> 00:04:34,000
tool. And it seems like a big oversight

115
00:04:31,440 --> 00:04:35,919
on the Bazite team to not include a

116
00:04:34,000 --> 00:04:38,000
quick mount option that just works.

117
00:04:35,919 --> 00:04:38,320
Instead, I want to fab myself in the

118
00:04:38,000 --> 00:04:40,479
head.

119
00:04:38,320 --> 00:04:42,320
>> Meanwhile, I was having a grand old time

120
00:04:40,479 --> 00:04:44,400
on Cashy. And since I felt more

121
00:04:42,320 --> 00:04:46,560
comfortable than the other two guys, I

122
00:04:44,400 --> 00:04:48,800
decided to get a little bit daring. I

123
00:04:46,560 --> 00:04:50,720
uninstalled my entire Cinnamon desktop

124
00:04:48,800 --> 00:04:52,560
environment on purpose [music]

125
00:04:50,720 --> 00:04:54,960
to see if I would run into any

126
00:04:52,560 --> 00:04:57,280
challenges. It took about 20 minutes max

127
00:04:54,960 --> 00:04:59,600
before I was up and running with KDE

128
00:04:57,280 --> 00:05:01,360
Plasma. And my only issue was that I had

129
00:04:59,600 --> 00:05:03,759
to clean up some small things [music]

130
00:05:01,360 --> 00:05:05,840
left over from Cinnamon. Uh like a an

131
00:05:03,759 --> 00:05:07,840
additional sound icon that was in the

132
00:05:05,840 --> 00:05:09,440
bottom tray because I had two sound

133
00:05:07,840 --> 00:05:11,600
icons and they could conflict and stuff.

134
00:05:09,440 --> 00:05:14,400
And that was honestly also really easy

135
00:05:11,600 --> 00:05:17,280
to do. So, no big deal. As for my gaming

136
00:05:14,400 --> 00:05:20,080
adventures, my first real challenge in

137
00:05:17,280 --> 00:05:21,919
this Linux challenge was probably my own

138
00:05:20,080 --> 00:05:24,160
fault. I had read some stuff online

139
00:05:21,919 --> 00:05:25,520
saying that I could do it, but I think I

140
00:05:24,160 --> 00:05:28,720
was trying to be a little bit more

141
00:05:25,520 --> 00:05:30,000
optimistic than realistic. I had a

142
00:05:28,720 --> 00:05:31,680
Windows game drive [music]

143
00:05:30,000 --> 00:05:33,440
previously that I just kind of left

144
00:05:31,680 --> 00:05:37,520
alone and tried to use on Linux, which

145
00:05:33,440 --> 00:05:40,080
means that it was formatted in NTFS. Um,

146
00:05:37,520 --> 00:05:42,320
I just added it to my Steam library and

147
00:05:40,080 --> 00:05:44,240
Linux and tried to go. All my games

148
00:05:42,320 --> 00:05:46,720
showed up perfect and everything seemed

149
00:05:44,240 --> 00:05:48,320
fine at first. Some games even ran okay,

150
00:05:46,720 --> 00:05:50,000
but I started to notice some glitches

151
00:05:48,320 --> 00:05:52,080
and even some games that I had freshly

152
00:05:50,000 --> 00:05:53,680
installed on that drive just wouldn't

153
00:05:52,080 --> 00:05:54,960
work. It would just you click play and

154
00:05:53,680 --> 00:05:57,120
it [music] just wouldn't launch

155
00:05:54,960 --> 00:06:00,080
sometimes. It turns out that while Linux

156
00:05:57,120 --> 00:06:01,520
can still use NTFS and there's been some

157
00:06:00,080 --> 00:06:03,600
ongoing development to make it even

158
00:06:01,520 --> 00:06:06,319
smoother, even since we started this

159
00:06:03,600 --> 00:06:09,440
challenge, I can say in my experience,

160
00:06:06,319 --> 00:06:11,520
it was uh kind of rough, especially when

161
00:06:09,440 --> 00:06:13,360
used with Proton. Proton doesn't seem to

162
00:06:11,520 --> 00:06:15,039
like it. So, in my opinion, if you want

163
00:06:13,360 --> 00:06:18,000
to play games off [music] of an NTFS

164
00:06:15,039 --> 00:06:21,280
drive, just don't. At least not right

165
00:06:18,000 --> 00:06:23,360
now. My gaming experiences were mostly

166
00:06:21,280 --> 00:06:24,720
smooth with two major exceptions,

167
00:06:23,360 --> 00:06:26,960
though. One of which I'm actually going

168
00:06:24,720 --> 00:06:28,560
to save for the conclusion cuz it's kind

169
00:06:26,960 --> 00:06:30,080
of a spicy one. So, make sure you get

170
00:06:28,560 --> 00:06:32,160
subscribed for that. But the other was

171
00:06:30,080 --> 00:06:34,479
actually the first game that I tried to

172
00:06:32,160 --> 00:06:37,600
fully play on Linux. Poppy Playtime

173
00:06:34,479 --> 00:06:40,160
Chapter 5. I wanted to stream it, but I

174
00:06:37,600 --> 00:06:43,199
was getting no audio and no picture,

175
00:06:40,160 --> 00:06:44,960
which is not ideal for a stream. Oh no.

176
00:06:43,199 --> 00:06:47,039
Are we not going to be able to play? But

177
00:06:44,960 --> 00:06:49,520
then it suddenly just popped in and

178
00:06:47,039 --> 00:06:51,199
started working fine. I played it for a

179
00:06:49,520 --> 00:06:52,880
little while and then the same thing

180
00:06:51,199 --> 00:06:56,319
happened again. Look, all the friends

181
00:06:52,880 --> 00:06:58,240
are here. Isn't this amazing? Oh, well,

182
00:06:56,319 --> 00:07:00,560
it turns out that the pre-rendered

183
00:06:58,240 --> 00:07:02,160
cutscenes weren't working. Proton, which

184
00:07:00,560 --> 00:07:04,400
is the compatibility layer that allows

185
00:07:02,160 --> 00:07:07,280
non-native Linux titles to work on

186
00:07:04,400 --> 00:07:11,280
Linux, is missing proprietary licenses

187
00:07:07,280 --> 00:07:13,199
for H.264 and H.265 video codecs. What

188
00:07:11,280 --> 00:07:16,080
was the solution? A community fork

189
00:07:13,199 --> 00:07:18,319
called Proton GE, which thankfully was

190
00:07:16,080 --> 00:07:20,240
in the Basite store. That's a pretty

191
00:07:18,319 --> 00:07:22,639
simple fix, but it's also one that

192
00:07:20,240 --> 00:07:24,880
highlights how unrealistic some Linux

193
00:07:22,639 --> 00:07:27,199
evangelists can be about the experience.

194
00:07:24,880 --> 00:07:29,039
No, in many cases, it doesn't just work

195
00:07:27,199 --> 00:07:30,960
out of the box. And users who don't

196
00:07:29,039 --> 00:07:33,199
treat fixing their operating system as a

197
00:07:30,960 --> 00:07:35,919
hobby will be looking for someone to

198
00:07:33,199 --> 00:07:38,560
blame for this hassle. So, is it Linux,

199
00:07:35,919 --> 00:07:43,280
Valve, Mob [music] Entertainment, the

200
00:07:38,560 --> 00:07:45,520
user, maybe all, or hear me out, none?

201
00:07:43,280 --> 00:07:47,599
It's easy to jump on the blame bandwagon

202
00:07:45,520 --> 00:07:49,919
and hate on some developers for not

203
00:07:47,599 --> 00:07:52,319
prioritizing Linux, but ask yourself

204
00:07:49,919 --> 00:07:55,360
this. If 50% of your customers were on

205
00:07:52,319 --> 00:07:57,199
Windows and the other 48% are on Xbox

206
00:07:55,360 --> 00:07:59,520
and PlayStation, would you be stoked on

207
00:07:57,199 --> 00:08:02,160
hiring a fourth group of employees whose

208
00:07:59,520 --> 00:08:04,800
job it is to deal with the other 2%?

209
00:08:02,160 --> 00:08:07,199
Especially knowing that those 2% are not

210
00:08:04,800 --> 00:08:09,680
running one OS, but are probably running

211
00:08:07,199 --> 00:08:11,680
different flavors of OS. I mean, maybe

212
00:08:09,680 --> 00:08:14,240
you would, but it's more important to

213
00:08:11,680 --> 00:08:16,479
remember that just like the users, many

214
00:08:14,240 --> 00:08:19,280
companies don't treat fixing operating

215
00:08:16,479 --> 00:08:22,240
systems like a hobby. Okay, so then we

216
00:08:19,280 --> 00:08:24,080
blame Valve. No, obviously not. It's

217
00:08:22,240 --> 00:08:26,000
super cool that they have put so much

218
00:08:24,080 --> 00:08:29,599
support into Proton, but the fact that

219
00:08:26,000 --> 00:08:31,599
they've paid so much already is not a

220
00:08:29,599 --> 00:08:34,159
good argument that they should just

221
00:08:31,599 --> 00:08:36,080
obviously pay even more for these

222
00:08:34,159 --> 00:08:37,839
commercial video codecs. The point I'm

223
00:08:36,080 --> 00:08:40,240
trying to make here is that enjoying the

224
00:08:37,839 --> 00:08:42,640
Linux experience requires a no blame

225
00:08:40,240 --> 00:08:44,959
mindset. Some stuff's going to work and

226
00:08:42,640 --> 00:08:47,360
some stuff won't. It's not anybody's

227
00:08:44,959 --> 00:08:49,120
fault. Everyone is doing their best. So

228
00:08:47,360 --> 00:08:52,160
with that in mind, throw out what I said

229
00:08:49,120 --> 00:08:54,880
earlier cuz I'm not mad at system 76. In

230
00:08:52,160 --> 00:08:57,600
fact, I left Pop OS on my main desktop

231
00:08:54,880 --> 00:08:59,600
just for the ls and it mostly worked for

232
00:08:57,600 --> 00:09:01,519
most things. With that said, when it

233
00:08:59,600 --> 00:09:03,440
came time to install Linux on my other

234
00:09:01,519 --> 00:09:05,680
systems, I did opt for something

235
00:09:03,440 --> 00:09:07,839
different. Starting with Basite on my

236
00:09:05,680 --> 00:09:09,680
home theater PC. It's just too bad the

237
00:09:07,839 --> 00:09:11,600
Linux curse followed me there as well.

238
00:09:09,680 --> 00:09:13,120
Um, Basite has different versions of

239
00:09:11,600 --> 00:09:15,200
their installer depending on the brand

240
00:09:13,120 --> 00:09:17,680
of your GPU and whether or not you want

241
00:09:15,200 --> 00:09:20,800
the Steam OS full screen experience.

242
00:09:17,680 --> 00:09:22,480
Well, I've got an NVIDIA GPU and yeah, I

243
00:09:20,800 --> 00:09:24,720
want that experience. That's kind of the

244
00:09:22,480 --> 00:09:27,600
point of it on a home the PC. So, I

245
00:09:24,720 --> 00:09:30,480
picked this one. And um, let's put it

246
00:09:27,600 --> 00:09:31,680
this way. The Basite team feels that I

247
00:09:30,480 --> 00:09:33,519
should have known the one that I

248
00:09:31,680 --> 00:09:36,000
selected would result in a completely

249
00:09:33,519 --> 00:09:38,560
unusable experience. But to me, that's

250
00:09:36,000 --> 00:09:41,839
actually not that obvious. Coming from

251
00:09:38,560 --> 00:09:44,240
the Windows Google normie world where a

252
00:09:41,839 --> 00:09:47,360
stable service like Gmail was labeled

253
00:09:44,240 --> 00:09:49,519
beta for 5 years, it's not that

254
00:09:47,360 --> 00:09:52,640
unreasonable to think that you can daily

255
00:09:49,519 --> 00:09:55,120
drive a beta and have a mostly

256
00:09:52,640 --> 00:09:56,800
functioning experience. In Linux, that's

257
00:09:55,120 --> 00:09:59,760
an expectation that needs to be

258
00:09:56,800 --> 00:10:02,560
completely thrown out the window. Here,

259
00:09:59,760 --> 00:10:04,320
beta seems to mean this is broken and if

260
00:10:02,560 --> 00:10:06,560
you're not a developer, you should

261
00:10:04,320 --> 00:10:08,880
probably just download the LTS, which

262
00:10:06,560 --> 00:10:10,640
might also be beta.

263
00:10:08,880 --> 00:10:12,720
Clearly, we've got to reach a middle

264
00:10:10,640 --> 00:10:14,399
ground here. And Basite seems to agree

265
00:10:12,720 --> 00:10:16,000
because they have updated the messaging

266
00:10:14,399 --> 00:10:17,920
on their site. Anyway, that happened

267
00:10:16,000 --> 00:10:19,519
later. So to get my system up and

268
00:10:17,920 --> 00:10:21,519
running, I ended up doing what many

269
00:10:19,519 --> 00:10:23,839
Linux people do and switching to a

270
00:10:21,519 --> 00:10:26,720
Radeon card, which was completely

271
00:10:23,839 --> 00:10:29,279
painless. Why run Bazite when I could

272
00:10:26,720 --> 00:10:30,959
just run Steam OS on the Steam machine

273
00:10:29,279 --> 00:10:32,640
that we built on this channel like a

274
00:10:30,959 --> 00:10:33,600
couple months ago? I can't believe I

275
00:10:32,640 --> 00:10:35,360
forgot about this thing. I've been

276
00:10:33,600 --> 00:10:37,200
meaning to install it. I actually ended

277
00:10:35,360 --> 00:10:40,800
up throwing Steam OS on my home theater

278
00:10:37,200 --> 00:10:44,959
PC. Nice. Okay. Is it a bit of a hack to

279
00:10:40,800 --> 00:10:47,519
just switch out your hardware? Yes, but

280
00:10:44,959 --> 00:10:49,120
also no, because a lot of Linux gamers

281
00:10:47,519 --> 00:10:50,720
would go out of their way to choose

282
00:10:49,120 --> 00:10:52,560
compatible hardware in the first place.

283
00:10:50,720 --> 00:10:54,000
So, I'm pretending I did that. First, I

284
00:10:52,560 --> 00:10:56,560
want to see how well this integrates

285
00:10:54,000 --> 00:11:01,360
with my system here. Let's hit power

286
00:10:56,560 --> 00:11:04,320
toggle for the PC. No way.

287
00:11:01,360 --> 00:11:07,200
Did Valve seriously bake in support for

288
00:11:04,320 --> 00:11:09,040
this old Microsoft IR receiver, which

289
00:11:07,200 --> 00:11:10,560
was child's play to get working, and

290
00:11:09,040 --> 00:11:12,160
it's been kind of awesome from the

291
00:11:10,560 --> 00:11:14,320
couch. Nothing further to report there.

292
00:11:12,160 --> 00:11:15,760
As for my laptop, I decided it was

293
00:11:14,320 --> 00:11:18,160
finally time to practice what I preach

294
00:11:15,760 --> 00:11:21,360
and go for good oldfashioned trustworthy

295
00:11:18,160 --> 00:11:23,440
Ubuntu. Sort of Kubuntu is actually

296
00:11:21,360 --> 00:11:25,519
Ubuntu, but with the KDE desktop

297
00:11:23,440 --> 00:11:27,200
environment, which I find quite

298
00:11:25,519 --> 00:11:29,200
comfortable to navigate, sort of. I

299
00:11:27,200 --> 00:11:31,519
mean, first I have to get to the desktop

300
00:11:29,200 --> 00:11:34,079
and day one was kind of terrible. After

301
00:11:31,519 --> 00:11:36,959
completing setup, it just black screened

302
00:11:34,079 --> 00:11:39,440
and it sat there for hours and I was

303
00:11:36,959 --> 00:11:40,880
like, come on, man. This is ridiculous.

304
00:11:39,440 --> 00:11:42,640
Then [music] I came down in the morning

305
00:11:40,880 --> 00:11:44,720
and it was like Santa had visited

306
00:11:42,640 --> 00:11:47,519
because it was magically sitting at the

307
00:11:44,720 --> 00:11:49,839
login screen and it's been downright

308
00:11:47,519 --> 00:11:51,279
pretty solid ever since with a bit of a

309
00:11:49,839 --> 00:11:53,040
learning curve. For example, I did run

310
00:11:51,279 --> 00:11:55,200
into issues getting some applications to

311
00:11:53,040 --> 00:11:57,920
work due to downloading the wrong

312
00:11:55,200 --> 00:12:00,640
package. Debian packages, snap packages,

313
00:11:57,920 --> 00:12:03,120
and flat packs will all work on Kubuntu.

314
00:12:00,640 --> 00:12:05,040
But I figured, okay, well, Debian makes

315
00:12:03,120 --> 00:12:07,519
the most sense since Kubuntu is based on

316
00:12:05,040 --> 00:12:10,160
Debian. But then after I installed OBS,

317
00:12:07,519 --> 00:12:12,000
I realized I had no option to select the

318
00:12:10,160 --> 00:12:14,000
display that I wanted to screen capture.

319
00:12:12,000 --> 00:12:16,639
The solution, use the flatp pack

320
00:12:14,000 --> 00:12:18,480
installer apparently. Okay, but where?

321
00:12:16,639 --> 00:12:20,399
The top result, as far as I can tell,

322
00:12:18,480 --> 00:12:22,800
doesn't convey that it's a flatp pack.

323
00:12:20,399 --> 00:12:24,240
Oh, right. I need to enable flatp pack

324
00:12:22,800 --> 00:12:26,053
search. Except that wasn't the solution

325
00:12:24,240 --> 00:12:27,839
either because Whand, which Kubuntu

326
00:12:26,053 --> 00:12:30,079
[music] uses as part of its desktop

327
00:12:27,839 --> 00:12:32,399
environment, has a privacy thing built

328
00:12:30,079 --> 00:12:34,240
in that no likey [music] screen capture.

329
00:12:32,399 --> 00:12:36,000
Now, it can be worked around, but

330
00:12:34,240 --> 00:12:37,760
threads like this one are a great

331
00:12:36,000 --> 00:12:40,959
example of how troubleshooting can often

332
00:12:37,760 --> 00:12:42,880
be a guess and check experience because

333
00:12:40,959 --> 00:12:44,480
there are like five different solutions

334
00:12:42,880 --> 00:12:46,880
in here, and I actually can no longer

335
00:12:44,480 --> 00:12:48,560
remember which one worked. Of course,

336
00:12:46,880 --> 00:12:49,839
though, it's important to point out that

337
00:12:48,560 --> 00:12:52,800
every problem that we're having with

338
00:12:49,839 --> 00:12:55,360
Linux can also be a problem with

339
00:12:52,800 --> 00:12:57,279
Windows. But the fact that Microsoft is

340
00:12:55,360 --> 00:13:01,040
also bad doesn't mean that we shouldn't

341
00:12:57,279 --> 00:13:04,160
be honest about issues or like level of

342
00:13:01,040 --> 00:13:06,399
tinkering required with Linux. My

343
00:13:04,160 --> 00:13:08,480
laptop, for example, running Mint and a

344
00:13:06,399 --> 00:13:11,120
very simple use case of basically just

345
00:13:08,480 --> 00:13:12,560
loading a browser hasn't required any

346
00:13:11,120 --> 00:13:14,560
tinkering this whole time and hasn't

347
00:13:12,560 --> 00:13:16,800
really had any problems. my desktop

348
00:13:14,560 --> 00:13:18,639
running Cache OS. I've intentionally

349
00:13:16,800 --> 00:13:20,800
tried to like put myself in harm's way

350
00:13:18,639 --> 00:13:23,279
and ran into [music] some really complex

351
00:13:20,800 --> 00:13:26,079
scenarios that have been fun to diagnose

352
00:13:23,279 --> 00:13:28,720
and work through, but there are things

353
00:13:26,079 --> 00:13:30,959
that are quite simple on Windows and

354
00:13:28,720 --> 00:13:35,680
very easy to do that are more

355
00:13:30,959 --> 00:13:38,639
complicated on Linux, and that's okay.

356
00:13:35,680 --> 00:13:41,120
But trying to hide that fact in order to

357
00:13:38,639 --> 00:13:43,600
recruit more Windows users to join the

358
00:13:41,120 --> 00:13:46,000
community, I think does more harm than

359
00:13:43,600 --> 00:13:48,639
good, especially when they are

360
00:13:46,000 --> 00:13:50,639
unfortunately fairly often met with

361
00:13:48,639 --> 00:13:52,880
hostility from the community when they

362
00:13:50,639 --> 00:13:54,720
then run into these problems and are

363
00:13:52,880 --> 00:13:56,880
unequipped to deal with. I think there

364
00:13:54,720 --> 00:13:59,040
are some obviously extremely bright

365
00:13:56,880 --> 00:14:01,519
lights in the Linux community that bring

366
00:13:59,040 --> 00:14:03,440
a lot of hope and joy and fun to the

367
00:14:01,519 --> 00:14:08,320
whole experience of learning Linux. But

368
00:14:03,440 --> 00:14:11,360
there is a lot of negative

369
00:14:08,320 --> 00:14:15,279
communication on forums, on Reddit,

370
00:14:11,360 --> 00:14:16,880
elsewhere. It's very off-putting for new

371
00:14:15,279 --> 00:14:19,680
Linux community members, which we're

372
00:14:16,880 --> 00:14:22,800
going to be seeing a lot more of soon,

373
00:14:19,680 --> 00:14:24,639
uh to receive that type of energy. The

374
00:14:22,800 --> 00:14:27,440
the biggest thing that didn't work for

375
00:14:24,639 --> 00:14:29,519
me was just software compatibility. But

376
00:14:27,440 --> 00:14:32,399
with some time and effort, I did manage

377
00:14:29,519 --> 00:14:34,160
to find either an alternative way uh to

378
00:14:32,399 --> 00:14:36,160
get the Windows native version working

379
00:14:34,160 --> 00:14:39,920
for my admittedly somewhat basic

380
00:14:36,160 --> 00:14:41,600
software suite. I didn't I use Adobe

381
00:14:39,920 --> 00:14:44,320
Premiere for editing. And one of the

382
00:14:41,600 --> 00:14:46,160
many fun ways that Adobe is kind of ass

383
00:14:44,320 --> 00:14:48,079
is that it just doesn't work on Linux.

384
00:14:46,160 --> 00:14:49,920
Now, I tried messing around with bottles

385
00:14:48,079 --> 00:14:52,320
a bit, which allows you to run Windows

386
00:14:49,920 --> 00:14:54,320
software on Linux, but that was

387
00:14:52,320 --> 00:14:56,320
obviously still a no-go, which then sent

388
00:14:54,320 --> 00:14:58,160
me looking for alternatives. Da Vinci

389
00:14:56,320 --> 00:15:00,160
Resolve has a Linux build, though it's

390
00:14:58,160 --> 00:15:02,800
only officially supported on Rocky Linux

391
00:15:00,160 --> 00:15:05,440
of all things. Still, Rocky Linux is a

392
00:15:02,800 --> 00:15:08,480
lot closer to Basite than Windows is. So

393
00:15:05,440 --> 00:15:10,560
maybe, and yeah, after 2 hours of

394
00:15:08,480 --> 00:15:13,279
trying, I got her up and running, but

395
00:15:10,560 --> 00:15:14,639
not the way I thought. See, I just tried

396
00:15:13,279 --> 00:15:17,519
installing it like a Windows

397
00:15:14,639 --> 00:15:19,519
application. Download and run.

398
00:15:17,519 --> 00:15:21,839
>> But Basite, as I learned, is an

399
00:15:19,519 --> 00:15:24,000
immutable operating system similar to

400
00:15:21,839 --> 00:15:26,079
Steam OS. This means core operating

401
00:15:24,000 --> 00:15:28,079
system files and permissions are locked

402
00:15:26,079 --> 00:15:30,320
down in such a way that the user either

403
00:15:28,079 --> 00:15:32,720
can't screw them up or they can but then

404
00:15:30,320 --> 00:15:34,880
they'll reset themselves after a reboot.

405
00:15:32,720 --> 00:15:36,959
Unfortunately, this same lockdown

406
00:15:34,880 --> 00:15:38,639
applies to some software installers,

407
00:15:36,959 --> 00:15:40,320
which then means that they can't alter

408
00:15:38,639 --> 00:15:42,000
the files that they need to. The

409
00:15:40,320 --> 00:15:44,160
solution was for me to beat my head

410
00:15:42,000 --> 00:15:46,480
against a wall until I found this

411
00:15:44,160 --> 00:15:48,959
6-inute video about a simple command to

412
00:15:46,480 --> 00:15:51,360
run. Hey, software installed. But then I

413
00:15:48,959 --> 00:15:53,920
ran into the same problem as Poppy

414
00:15:51,360 --> 00:15:56,639
Playtime. Depending on the file that I

415
00:15:53,920 --> 00:16:00,000
was trying to play or export, it

416
00:15:56,639 --> 00:16:01,759
wouldn't work. Freaking curse you video

417
00:16:00,000 --> 00:16:04,320
codecs.

418
00:16:01,759 --> 00:16:06,399
So I then tried Kaden Live, which is

419
00:16:04,320 --> 00:16:08,079
fine for basic editing, but if I want to

420
00:16:06,399 --> 00:16:10,160
be a power user, it's just not quite

421
00:16:08,079 --> 00:16:12,000
there yet. And for stills, neither is

422
00:16:10,160 --> 00:16:15,199
 You know what? I'm going to be the

423
00:16:12,000 --> 00:16:17,839
one to say it. sucks. With that

424
00:16:15,199 --> 00:16:20,880
said, I still want to emphasize the

425
00:16:17,839 --> 00:16:22,720
gratitude that I feel and you, Elijah, I

426
00:16:20,880 --> 00:16:24,000
know you feel it too, toward the open

427
00:16:22,720 --> 00:16:26,959
source community, whether it's

428
00:16:24,000 --> 00:16:28,800
applications or drivers or Linux in

429
00:16:26,959 --> 00:16:30,720
general. The fact that people are

430
00:16:28,800 --> 00:16:32,639
stepping up against the corporate

431
00:16:30,720 --> 00:16:34,880
overlords who are limiting our choices,

432
00:16:32,639 --> 00:16:37,576
feasting on our wallets, and then spying

433
00:16:34,880 --> 00:16:40,880
on us for good measure is amazing and

434
00:16:37,576 --> 00:16:43,279
[music] it's admirable. However, context

435
00:16:40,880 --> 00:16:45,279
matters. And when we're evaluating the

436
00:16:43,279 --> 00:16:47,680
experience of switching to Linux, we're

437
00:16:45,279 --> 00:16:50,079
doing so from a user perspective. And so

438
00:16:47,680 --> 00:16:52,880
we do have to point out things that

439
00:16:50,079 --> 00:16:54,320
might not be ideal. Just try to

440
00:16:52,880 --> 00:16:56,560
understand that it comes from a place of

441
00:16:54,320 --> 00:16:58,560
love and appreciation, not from a place

442
00:16:56,560 --> 00:17:00,720
of hate. Everybody involved in the Linux

443
00:16:58,560 --> 00:17:02,160
challenge today is rooting for Linux to

444
00:17:00,720 --> 00:17:04,160
succeed. And it's actually been really

445
00:17:02,160 --> 00:17:06,720
exciting to see so many social media

446
00:17:04,160 --> 00:17:08,720
posts of people who have joined the

447
00:17:06,720 --> 00:17:11,199
challenge alongside us, even though we

448
00:17:08,720 --> 00:17:13,839
didn't ask anybody to. But as exciting

449
00:17:11,199 --> 00:17:16,400
as all of that is, part of succeeding in

450
00:17:13,839 --> 00:17:18,240
this is taking off the blinders and

451
00:17:16,400 --> 00:17:20,640
being honest about the areas where

452
00:17:18,240 --> 00:17:22,240
things need to improve. And it's

453
00:17:20,640 --> 00:17:24,400
actually been pretty cool to see that

454
00:17:22,240 --> 00:17:26,559
some of our observations are already

455
00:17:24,400 --> 00:17:28,400
resulting in clearer documentation

456
00:17:26,559 --> 00:17:30,640
that's going to help pave the path for

457
00:17:28,400 --> 00:17:33,520
future users. Now, I know we're

458
00:17:30,640 --> 00:17:35,600
releasing part two like way past the one

459
00:17:33,520 --> 00:17:37,200
month point already, huh? Elijah was

460
00:17:35,600 --> 00:17:39,520
busy fixing our environmental chamber

461
00:17:37,200 --> 00:17:41,120
among other things. But we do still have

462
00:17:39,520 --> 00:17:42,799
more videos lined up for the series. And

463
00:17:41,120 --> 00:17:45,039
as you guys can see, even though we're

464
00:17:42,799 --> 00:17:47,039
past the month, uh there will be some

465
00:17:45,039 --> 00:17:48,400
surprises in the future parts. Part

466
00:17:47,039 --> 00:17:50,480
three is going to have us do some fun

467
00:17:48,400 --> 00:17:51,919
challenges. And then part four is going

468
00:17:50,480 --> 00:17:54,000
to be the conclusion where we sit down

469
00:17:51,919 --> 00:17:56,080
on the couch together and talk about our

470
00:17:54,000 --> 00:17:58,240
final thoughts. Oh, and we'll probably

471
00:17:56,080 --> 00:18:00,640
also talk about our segue to our

472
00:17:58,240 --> 00:18:03,280
sponsor, Threat Locker. Threat Locker

473
00:18:00,640 --> 00:18:05,200
helps organizations stay in control as

474
00:18:03,280 --> 00:18:07,360
AI becomes part of the workplace.

475
00:18:05,200 --> 00:18:10,080
Companies everywhere are adopting AI

476
00:18:07,360 --> 00:18:12,480
tools to move faster. But it's pretty

477
00:18:10,080 --> 00:18:15,200
critical to control what those tools can

478
00:18:12,480 --> 00:18:17,200
do, what they can access, and where they

479
00:18:15,200 --> 00:18:19,840
can send data. Threat Locker gives your

480
00:18:17,200 --> 00:18:22,080
organization zero trust controls to help

481
00:18:19,840 --> 00:18:24,160
to limit AI's reach inside your

482
00:18:22,080 --> 00:18:26,320
environment, including what applications

483
00:18:24,160 --> 00:18:28,320
can run and what resources they can

484
00:18:26,320 --> 00:18:30,880
interact with. So, if your organization

485
00:18:28,320 --> 00:18:33,120
is taking advantage of AI, you want to

486
00:18:30,880 --> 00:18:35,600
do so without opening the door to

487
00:18:33,120 --> 00:18:37,440
unnecessary risk. And you can start by

488
00:18:35,600 --> 00:18:39,440
using a zerorust approach to cyber

489
00:18:37,440 --> 00:18:41,600
security and checking out threat locker

490
00:18:39,440 --> 00:18:43,520
using our link in the description below.

491
00:18:41,600 --> 00:18:44,880
If you guys enjoyed this video, go check

492
00:18:43,520 --> 00:18:47,039
out part one. [music] We talked through

493
00:18:44,880 --> 00:18:49,280
the choices that we made and the

494
00:18:47,039 --> 00:18:50,880
installation process. It's over a month

495
00:18:49,280 --> 00:18:52,160
old at this point, which I know we said

496
00:18:50,880 --> 00:18:53,840
we were only going to do a one-mon

497
00:18:52,160 --> 00:18:55,280
challenge, but maybe that gives you a

498
00:18:53,840 --> 00:18:58,160
little hint [music] as to what our

499
00:18:55,280 --> 00:18:58,160
conclusion might