WEBVTT Kind: captions Language: en 00:00:01.100 --> 00:00:04.519 align:start position:0% covering<00:00:02.100> the<00:00:02.220> week's<00:00:02.429> top<00:00:02.700> textbooks<00:00:03.529> like 00:00:04.519 --> 00:00:04.529 align:start position:0% covering the week's top textbooks like 00:00:04.529 --> 00:00:07.940 align:start position:0% covering the week's top textbooks like Linux<00:00:05.040> bias<00:00:05.509> Samsung<00:00:06.509> users<00:00:06.960> unplug<00:00:07.290> your 00:00:07.940 --> 00:00:07.950 align:start position:0% Linux bias Samsung users unplug your 00:00:07.950 --> 00:00:11.150 align:start position:0% Linux bias Samsung users unplug your Ethernet<00:00:08.660> millions<00:00:09.660> of<00:00:09.870> Samsung<00:00:10.380> blu-ray<00:00:10.679> and 00:00:11.150 --> 00:00:11.160 align:start position:0% Ethernet millions of Samsung blu-ray and 00:00:11.160 --> 00:00:13.700 align:start position:0% Ethernet millions of Samsung blu-ray and DVD<00:00:11.700> players<00:00:12.000> are<00:00:12.269> being<00:00:12.420> bricked<00:00:12.870> all<00:00:13.139> around 00:00:13.700 --> 00:00:13.710 align:start position:0% DVD players are being bricked all around 00:00:13.710 --> 00:00:14.740 align:start position:0% DVD players are being bricked all around the<00:00:13.920> world 00:00:14.740 --> 00:00:14.750 align:start position:0% the world 00:00:14.750 --> 00:00:16.519 align:start position:0% the world Entertainment<00:00:15.750> has<00:00:15.870> become<00:00:16.199> one<00:00:16.379> of<00:00:16.410> the 00:00:16.519 --> 00:00:16.529 align:start position:0% Entertainment has become one of the 00:00:16.529 --> 00:00:18.590 align:start position:0% Entertainment has become one of the biggest<00:00:16.800> tools<00:00:17.250> for<00:00:17.640> keeping<00:00:18.000> sane<00:00:18.300> during 00:00:18.590 --> 00:00:18.600 align:start position:0% biggest tools for keeping sane during 00:00:18.600 --> 00:00:20.450 align:start position:0% biggest tools for keeping sane during these<00:00:18.869> trying<00:00:19.289> times<00:00:19.410> but<00:00:20.010> while<00:00:20.160> many 00:00:20.450 --> 00:00:20.460 align:start position:0% these trying times but while many 00:00:20.460 --> 00:00:22.400 align:start position:0% these trying times but while many companies<00:00:20.760> are<00:00:21.029> aggressively<00:00:21.720> pushing<00:00:22.109> their 00:00:22.400 --> 00:00:22.410 align:start position:0% companies are aggressively pushing their 00:00:22.410 --> 00:00:25.250 align:start position:0% companies are aggressively pushing their streaming<00:00:22.830> services<00:00:23.570> others<00:00:24.570> still<00:00:24.840> prefer 00:00:25.250 --> 00:00:25.260 align:start position:0% streaming services others still prefer 00:00:25.260 --> 00:00:27.320 align:start position:0% streaming services others still prefer owning<00:00:25.680> the<00:00:25.769> media<00:00:26.099> they<00:00:26.310> buy<00:00:26.490> in<00:00:26.820> physical 00:00:27.320 --> 00:00:27.330 align:start position:0% owning the media they buy in physical 00:00:27.330 --> 00:00:30.410 align:start position:0% owning the media they buy in physical form<00:00:27.630> that<00:00:28.010> mostly<00:00:29.010> means<00:00:29.250> DVDs<00:00:29.789> and<00:00:30.029> blu-ray 00:00:30.410 --> 00:00:30.420 align:start position:0% form that mostly means DVDs and blu-ray 00:00:30.420 --> 00:00:32.330 align:start position:0% form that mostly means DVDs and blu-ray discs<00:00:30.900> which<00:00:31.080> of<00:00:31.320> course<00:00:31.380> require 00:00:32.330 --> 00:00:32.340 align:start position:0% discs which of course require 00:00:32.340 --> 00:00:35.360 align:start position:0% discs which of course require appropriate<00:00:33.120> devices<00:00:33.510> to<00:00:33.960> play<00:00:34.079> them<00:00:34.410> but 00:00:35.360 --> 00:00:35.370 align:start position:0% appropriate devices to play them but 00:00:35.370 --> 00:00:37.580 align:start position:0% appropriate devices to play them but what<00:00:35.640> if<00:00:35.790> those<00:00:36.059> devices<00:00:36.570> all<00:00:37.050> suddenly 00:00:37.580 --> 00:00:37.590 align:start position:0% what if those devices all suddenly 00:00:37.590 --> 00:00:39.799 align:start position:0% what if those devices all suddenly stopped<00:00:37.890> working<00:00:37.920> for<00:00:38.579> no<00:00:38.760> apparent<00:00:38.940> reason 00:00:39.799 --> 00:00:39.809 align:start position:0% stopped working for no apparent reason 00:00:39.809 --> 00:00:42.590 align:start position:0% stopped working for no apparent reason that's<00:00:40.530> the<00:00:40.829> rather<00:00:41.010> eerie<00:00:41.489> and<00:00:41.820> frustrating 00:00:42.590 --> 00:00:42.600 align:start position:0% that's the rather eerie and frustrating 00:00:42.600 --> 00:00:44.930 align:start position:0% that's the rather eerie and frustrating situation<00:00:43.320> that<00:00:43.500> owners<00:00:43.890> of<00:00:43.920> Samsung<00:00:44.640> blu-ray 00:00:44.930 --> 00:00:44.940 align:start position:0% situation that owners of Samsung blu-ray 00:00:44.940 --> 00:00:47.229 align:start position:0% situation that owners of Samsung blu-ray players<00:00:45.450> are<00:00:45.780> now<00:00:46.020> experiencing 00:00:47.229 --> 00:00:47.239 align:start position:0% players are now experiencing 00:00:47.239 --> 00:00:50.270 align:start position:0% players are now experiencing experiencing<00:00:48.239> around<00:00:49.140> the<00:00:49.320> world<00:00:49.590> with<00:00:49.980> no 00:00:50.270 --> 00:00:50.280 align:start position:0% experiencing around the world with no 00:00:50.280 --> 00:00:53.660 align:start position:0% experiencing around the world with no answer<00:00:50.789> or<00:00:51.030> solution<00:00:51.690> yet<00:00:51.899> insight<00:00:52.670> there 00:00:53.660 --> 00:00:53.670 align:start position:0% answer or solution yet insight there 00:00:53.670 --> 00:00:54.979 align:start position:0% answer or solution yet insight there doesn't<00:00:54.030> seem<00:00:54.059> to<00:00:54.239> be<00:00:54.420> any<00:00:54.570> common 00:00:54.979 --> 00:00:54.989 align:start position:0% doesn't seem to be any common 00:00:54.989 --> 00:00:56.479 align:start position:0% doesn't seem to be any common denominator<00:00:55.500> other<00:00:55.800> than<00:00:56.070> the<00:00:56.160> fact<00:00:56.399> that 00:00:56.479 --> 00:00:56.489 align:start position:0% denominator other than the fact that 00:00:56.489 --> 00:00:57.979 align:start position:0% denominator other than the fact that it's<00:00:56.699> happening<00:00:56.850> across<00:00:57.390> a<00:00:57.510> number<00:00:57.840> of 00:00:57.979 --> 00:00:57.989 align:start position:0% it's happening across a number of 00:00:57.989 --> 00:01:00.619 align:start position:0% it's happening across a number of Samsung's<00:00:58.620> Wi-Fi<00:00:59.250> or<00:00:59.579> Ethernet<00:00:59.820> connected 00:01:00.619 --> 00:01:00.629 align:start position:0% Samsung's Wi-Fi or Ethernet connected 00:01:00.629 --> 00:01:03.560 align:start position:0% Samsung's Wi-Fi or Ethernet connected blu-ray<00:01:01.079> and<00:01:01.350> DVD<00:01:01.859> players<00:01:02.239> it<00:01:03.239> doesn't 00:01:03.560 --> 00:01:03.570 align:start position:0% blu-ray and DVD players it doesn't 00:01:03.570 --> 00:01:06.800 align:start position:0% blu-ray and DVD players it doesn't appear<00:01:03.870> to<00:01:03.899> matter<00:01:04.170> which<00:01:04.530> model<00:01:05.570> the<00:01:06.570> most 00:01:06.800 --> 00:01:06.810 align:start position:0% appear to matter which model the most 00:01:06.810 --> 00:01:08.870 align:start position:0% appear to matter which model the most common<00:01:07.260> behavior<00:01:07.860> reported<00:01:08.430> is<00:01:08.580> that<00:01:08.729> the 00:01:08.870 --> 00:01:08.880 align:start position:0% common behavior reported is that the 00:01:08.880 --> 00:01:11.120 align:start position:0% common behavior reported is that the players<00:01:09.150> reboot<00:01:09.720> themselves<00:01:10.470> after<00:01:10.770> a<00:01:10.799> few 00:01:11.120 --> 00:01:11.130 align:start position:0% players reboot themselves after a few 00:01:11.130 --> 00:01:14.020 align:start position:0% players reboot themselves after a few seconds<00:01:11.610> causing<00:01:12.510> an<00:01:12.630> inescapable<00:01:13.200> boot<00:01:13.770> loop 00:01:14.020 --> 00:01:14.030 align:start position:0% seconds causing an inescapable boot loop 00:01:14.030 --> 00:01:16.760 align:start position:0% seconds causing an inescapable boot loop others<00:01:15.030> have<00:01:15.270> reported<00:01:15.720> hearing<00:01:15.869> noises<00:01:16.290> as 00:01:16.760 --> 00:01:16.770 align:start position:0% others have reported hearing noises as 00:01:16.770 --> 00:01:18.800 align:start position:0% others have reported hearing noises as if<00:01:16.920> the<00:01:17.070> players<00:01:17.340> were<00:01:17.640> reading<00:01:18.030> empty<00:01:18.450> disc 00:01:18.800 --> 00:01:18.810 align:start position:0% if the players were reading empty disc 00:01:18.810 --> 00:01:21.649 align:start position:0% if the players were reading empty disc slots<00:01:19.490> given<00:01:20.490> the<00:01:20.580> mysterious<00:01:21.150> and<00:01:21.390> sudden 00:01:21.649 --> 00:01:21.659 align:start position:0% slots given the mysterious and sudden 00:01:21.659 --> 00:01:23.539 align:start position:0% slots given the mysterious and sudden appearance<00:01:22.110> of<00:01:22.229> the<00:01:22.409> bug<00:01:22.590> some<00:01:22.979> people<00:01:23.369> have 00:01:23.539 --> 00:01:23.549 align:start position:0% appearance of the bug some people have 00:01:23.549 --> 00:01:25.310 align:start position:0% appearance of the bug some people have different<00:01:23.939> theories<00:01:24.119> on<00:01:24.299> what<00:01:24.720> caused<00:01:25.049> it 00:01:25.310 --> 00:01:25.320 align:start position:0% different theories on what caused it 00:01:25.320 --> 00:01:28.160 align:start position:0% different theories on what caused it some<00:01:26.280> blame<00:01:26.580> an<00:01:26.850> overnight<00:01:27.210> firmware<00:01:27.750> update 00:01:28.160 --> 00:01:28.170 align:start position:0% some blame an overnight firmware update 00:01:28.170 --> 00:01:30.380 align:start position:0% some blame an overnight firmware update but<00:01:28.409> the<00:01:28.530> range<00:01:28.799> of<00:01:29.009> devices<00:01:29.549> covered<00:01:29.939> is<00:01:30.090> so 00:01:30.380 --> 00:01:30.390 align:start position:0% but the range of devices covered is so 00:01:30.390 --> 00:01:33.080 align:start position:0% but the range of devices covered is so wide<00:01:30.689> and<00:01:31.049> random<00:01:31.799> that<00:01:32.340> it<00:01:32.490> seems<00:01:32.759> less 00:01:33.080 --> 00:01:33.090 align:start position:0% wide and random that it seems less 00:01:33.090 --> 00:01:35.870 align:start position:0% wide and random that it seems less likely<00:01:33.470> some<00:01:34.470> believe<00:01:34.770> it<00:01:34.979> may<00:01:35.130> be<00:01:35.189> an<00:01:35.430> expired 00:01:35.870 --> 00:01:35.880 align:start position:0% likely some believe it may be an expired 00:01:35.880 --> 00:01:38.210 align:start position:0% likely some believe it may be an expired ssl<00:01:36.540> security<00:01:37.140> certificate<00:01:37.740> in<00:01:37.890> the<00:01:37.920> firmware 00:01:38.210 --> 00:01:38.220 align:start position:0% ssl security certificate in the firmware 00:01:38.220 --> 00:01:40.730 align:start position:0% ssl security certificate in the firmware which<00:01:38.759> could<00:01:39.150> explain<00:01:39.329> why<00:01:39.869> no<00:01:40.200> amount<00:01:40.470> of 00:01:40.730 --> 00:01:40.740 align:start position:0% which could explain why no amount of 00:01:40.740 --> 00:01:43.160 align:start position:0% which could explain why no amount of resetting<00:01:41.310> the<00:01:41.430> device<00:01:41.729> to<00:01:42.030> factory<00:01:42.479> settings 00:01:43.160 --> 00:01:43.170 align:start position:0% resetting the device to factory settings 00:01:43.170 --> 00:01:46.490 align:start position:0% resetting the device to factory settings seems<00:01:43.770> to<00:01:44.009> work<00:01:44.930> unfortunately<00:01:45.930> Samsung 00:01:46.490 --> 00:01:46.500 align:start position:0% seems to work unfortunately Samsung 00:01:46.500 --> 00:01:48.740 align:start position:0% seems to work unfortunately Samsung remains<00:01:46.829> unresponsive<00:01:47.299> despite<00:01:48.299> the<00:01:48.509> growing 00:01:48.740 --> 00:01:48.750 align:start position:0% remains unresponsive despite the growing 00:01:48.750 --> 00:01:51.230 align:start position:0% remains unresponsive despite the growing number<00:01:49.200> of<00:01:49.229> complaints<00:01:49.860> possibly<00:01:50.729> due<00:01:50.880> to<00:01:50.909> how 00:01:51.230 --> 00:01:51.240 align:start position:0% number of complaints possibly due to how 00:01:51.240 --> 00:01:53.660 align:start position:0% number of complaints possibly due to how it<00:01:51.420> happened<00:01:51.810> during<00:01:51.960> the<00:01:52.200> weekend<00:01:52.670> given 00:01:53.660 --> 00:01:53.670 align:start position:0% it happened during the weekend given 00:01:53.670 --> 00:01:55.700 align:start position:0% it happened during the weekend given global<00:01:54.030> conditions<00:01:54.329> it's<00:01:54.960> understandable 00:01:55.700 --> 00:01:55.710 align:start position:0% global conditions it's understandable 00:01:55.710 --> 00:01:58.300 align:start position:0% global conditions it's understandable how<00:01:56.009> owners<00:01:56.310> are<00:01:56.700> not<00:01:56.909> so<00:01:57.270> amused 00:01:58.300 --> 00:01:58.310 align:start position:0% how owners are not so amused 00:01:58.310 --> 00:01:59.980 align:start position:0% how owners are not so amused especially<00:01:58.880> if<00:01:59.000> it<00:01:59.149> will<00:01:59.329> require<00:01:59.689> them<00:01:59.930> to 00:01:59.980 --> 00:01:59.990 align:start position:0% especially if it will require them to 00:01:59.990 --> 00:02:04.450 align:start position:0% especially if it will require them to turn<00:02:00.409> in<00:02:00.590> the<00:02:00.680> device<00:02:01.009> for<00:02:01.430> manual<00:02:01.880> servicing