Wikiversity enwikiversity https://en.wikiversity.org/wiki/Wikiversity:Main_Page MediaWiki 1.44.0-wmf.8 first-letter Media Special Talk User User talk Wikiversity Wikiversity talk File File talk MediaWiki MediaWiki talk Template Template talk Help Help talk Category Category talk School School talk Portal Portal talk Topic Topic talk Collection Collection talk Draft Draft talk TimedText TimedText talk Module Module talk 0 281723 2374211 2022-02-10T15:51:18Z Seeaver 2935500 Seeaver moved page [[User:Seeaver/sandbox]] to [[User:Web Design/Progressive enhancement]]: publishing finished draft 2374211 wikitext text/x-wiki #REDIRECT [[User:Web Design/Progressive enhancement]] qfsfenxke5e8ijkqikhjfxy8avm2d9w 2374311 2374211 2022-02-11T04:02:11Z JackBot 238563 Bot: Fixing double redirect to [[Web Design/Progressive enhancement]] 2374311 wikitext text/x-wiki #REDIRECT [[Web Design/Progressive enhancement]] std2i43f97z750k7c508gkrhbizulnq 2379521 2374311 2022-03-02T01:20:51Z Seeaver 2935500 paragraph draft 2379521 wikitext text/x-wiki Text draft for [[Web Design/Progressive enhancement]]: Web developer Jake Archibald describes the situation as "when an elevator fails, it's useless. When an escalator fails, it becomes stairs.", though web developer Anton Bershanskiy does not like this example, as he considers it more of a simile than a metaphor. jq6xcek66kvxqyg6s0wgeamwvyy7qmx 2380011 2379521 2022-03-03T21:36:46Z Seeaver 2935500 /* Vendor forums */ 2380011 wikitext text/x-wiki == Vendor forums == Vendor-hosted forums are unreliable in the long term, since they are more driven by vendors' commercial interests than by community interests. Additionally, they typically use proprietary content management systems, meaning a scraping script would need to be developed individually for each such forum. For example, Apple has blocked users from their support forums for posting data recovery instructions.<ref>[https://www.youtube.com/watch?v=LrILfIE9IB4 ''Jessa Jones CORRECTS Apple on data recovery and gets BANNED!'' (Louis Rossman, 2019)]</ref> Samsung appears to be purging threads of legacy devices. For example, threads of the Galaxy S7 device appear to have been purged at some point, and existing links to such threads redirect to the home page.<ref>https://us.community.samsung.com/t5/Galaxy-S-Phones/s7-Edge-notification-setting/td-p/3396 (last available in 2017)</ref> kqiry5kr5b599sanun558d8y30wmtyi 2380027 2380011 2022-03-04T00:02:42Z Seeaver 2935500 /* 2020 */ 2380027 wikitext text/x-wiki == 2020 == <blockquote> 2020. A year fulfilled with much grief and sorrow, with Australian Wildfires creating destruction, right as Kobe and his daughter were killed in a helicopter crash in January. Then Coronavirus breaks out in America. What next? Oh, just the murder of innocent black lives across the globe, such as Breonna Taylor and George Floyd, which lead to powerful protests, and more Covid cases, and with covid, millions of people go homeless without a place to work, which causes the stock market to obliterate. Oh, and there's more. Chadwick Boseman's Death, Eddie Van Halen's death, and Ruth Bader Ginsburg's death, and now, great. No Halloween, and guess what's coming. The Flu. So, 2020, what other, people will you kill off. What other, sickness will you bring us. And What other crap will hit in your year? </blockquote> <span style=display:none;>65633381</span> f5fj0e7nw9ni40g220bftyh5xml41o4 2380076 2380027 2022-03-04T01:58:05Z Seeaver 2935500 /* MicroSD */ 2380076 wikitext text/x-wiki == MicroSD == [https://www.forensicfocus.com/forums/general/microsd-card-write-protected-itself-changes-vanish-immediately-hardware-level-fault/ Post1], [http://www.cnet.com/forums/discussions/help-usb-flash-drive-suddenly-became-write-protected-592660/%23post-0739af7b-317e-4f78-9bb2-59a3a93640c3 Post2] ([https://archive.today/2016.09.08-150727/www.cnet.com/forums/discussions/help-usb-flash-drive-suddenly-became-write-protected-592660/%23post-0739af7b-317e-4f78-9bb2-59a3a93640c3 archive] / [https://archive.is/4iDTt short URL]) aeh2weoakd0uweab4noi32l0oiblx8g 2380077 2380076 2022-03-04T01:59:00Z Seeaver 2935500 reset 2380077 wikitext text/x-wiki {{user sandbox}} 2agug54p2hovcns7kh5e1zpj7qfr71h 2383024 2380077 2022-03-12T01:28:17Z Seeaver 2935500 /* Semantic web */ 2383024 wikitext text/x-wiki {{user sandbox}} == Semantic web == Inclusive web design (HTML meta tags, preloaded collapsible elements, informational tooltips) are good for web archival. === Case studies === I have noticed these useful design characteristics on these websites, which prevent loss of information when retreived from web archival services (e.g. Internet Archive's Wayback Machine, Archive.Today): * * Client-side screen width (mobile) optimization allows viewing lost websites through the Wayback Machine on more devices. * The Vlare.TV video watch page (alternative video platform) has a pre-loaded, collapsible menu called “More from: (Channel name)” * If a Vlare.TV channel is unavailable for some reason, or in case of deleted videos, the videos listed in that menu could prevent the proof of existence for some videos to vanish into oblivion. I wish YouTube had done that too. That would have saved much information from vanishing. YouTube once had such a menu (2010-2011 and for a short period in early 2019, as far as I can remember), but it didn't use pre-loading but AJAX. * HTML Meta tags * Because YouTube channels since 2013 use no single-page channel layout, different parts of a channel are split to different pages, and an archived channel front page does not visibly include information from the other channel tabs (playlists, discussions, recommended channels, “about” page, etc.). But the first 160 characters of the channel description are included in the HTML meta tags responsible for preview cards on social media such as Twitter. Therefore, if the “About” page of a deleted/suspended channel has not been archived, the first 160 characters of the channel description can still be retrieved from the HTML source code if any other page of the channel is archived. * Tooltips on Twitter's legacy desktop website. * If a Twitter profile front page is archived, the HTML-preloaded tooltips include information such as exact counts (Tweets, Followings, Followers, etc.) and the absolute time (to the minute) of each visible timeline tweet and the join date. * Double-layer design of Twitter's legacy desktop website. * If a tweet page is archived, it also contains the profile page outline in the background. (Full-resolution profile picture and header image, biography text, specified location, specified URL, join date.). This means that if a Twitter account is suspended and only some tweets are archived, the profile outline information is not lost, even if the profile front pages (including “/with_replies”, “/media”, “/likes”) are not archived. * Reddit's “More posts from the (name) community” section under a post: Post preview snippets of other trending posts on the same subreddit. * On a capture on Archive-Today (that switched from PhantomJS to Chromium on 2019-11-29), it stores ~20 snippets under the post. For text posts, the snippets contain the first ~400 characters (rough guess). If that post gets deleted before being archived, some contents could be recovered from archived captures of other recent posts. * BitChute's client-side pagination for tabs on channel pages, trending videos and trending channels. * When the page is loaded, the contents of all tabs are loaded within, which means that one archived page covers all pages. * During normal usage: No extra waiting time when navigating between the tabs, because the information is already pre-loaded, which is awesome. * On BitChute channel pages, the full video descriptions of each listed video are included in the HTML source code, and the contents of the “About” page (total view count, approximate relative channel creation date, channel description, count of uploaded videos, channel category). * BitChute also uses client-side (CSS-powered) screen width optimization. On too narrow screen widths, it just hides the “Most viewed” side bar on the channel page. * I probably forgot to mention some more examples I know, but these are currently all that come to my mind. Some parts of a web page might need JavaScript to show, which isn't supported by Archive.Today, but the information hidden inside a collapsible pre-loaded section using <code>display:none;</code> in-line CSS, or JS-powered client-side pagination can still be retrieved from the HTML source code. I know, these thoughts sound somewhat abstract to the average Internet user, but I just wanted to get this off my chest (in a positive way). p18yfk3qkjzts0ajrmi39tax58hfv97 2383027 2383024 2022-03-12T01:41:42Z Seeaver 2935500 section and diff test 2383027 wikitext text/x-wiki {{user sandbox}} {{Game|developer=LongAnimals & robotJAM|title1=Cyclomaniacs|publisher=Kongregate|platform=Flash|genre=Racing|series=Cyclomaniacs|mode=Single Player|release=August 10, 2009|link(s)=<li>[https://www.kongregate.com/games/longanimals/cyclomaniacs Kongregate] <li>[https://armorgames.com/play/4355/cyclomaniacs Armor Games] <li>[https://www.maxgames.com/game/cyclomaniacs.html Max Games]|image=Cyclomaniacs.jpg}} '''Cyclomaniacs''' is a 2009 bike racing flash game developed by ''LongAnimals'' and ''robotJAM'', published on Kongregate.com. == Achievements and unlockables == Tracks and characters are unlocked through achievements, such as completing the level under a given time without crashing, reaching a number of forward or backward somersaults, wheelie time, consecutive wheelie time, reaching an air time (consecutive or total), and reaching a [[#Stunts and boosting|boost level]]. It could be described as a precursor of Fingersoft's "Hill Climb Racing". The game has 70 achievements in total. Each is rewarded with $200 of in-game money. === Horns (collectible) === Some levels feature "horns", which are collectible yellow circles in the air with the clip-art of a horn. For each collected, a note of "Ode to Joy" (European anthem) is played, and afterwards a constant tone. For some achievements, not necessarily all of them need to be collected. Occasionally, the player needs to bounce using the space bar to reach one. === Characteristics === Physical characteristics such as stability, agility, height, and bounce height vary throughout characters' bikes, making some more capable than others for specific achievements. For example, it is difficult to achieve the ten-second wheelie challenge on the moon level with any other characters than "Cycle King" and "Spoke", whose bikes share the same physical shape. Front wheelie challenges are difficult to be obtained with any other bike than that of "Letter F" with huge front wheel, and "The Bowler Brothers" are more stable and the least likely to land upside down. Their low bounciness also prevents them from hitting their heads in "Outlands: The Caves". "Sir Collin" can rotate as quickly as to be able to perform somersaults from bouncing from stillstand, thus can attain high boost levels. Each character features a horn (not to be confused with collectible in-level "horns"), which is a sound made by pressing the "B" button. Horns are separately unlocked. == Locations and stages == There are six different locations: The Dunes, Volcania, Planetoid, Outlands, Sunset City, and the moon, five of which (all except the Moon) have five stages, the last of which is a chase which can be played with only one predetermined character. In the first four stages of each location, the game plays with nine randomly selected opponents, and 19 on the moon. == Stunts and boosting == While racing, the player gets rewarded for stunts that are wheelies, air time, and somersaults, by charging the "stunt meter". Once it is full, the player's racing speed will be boosted, and a "boost meter" indicates how much boost time is left. If the player manages to fill the ''stunt meter'' before the boost time runs out, the boost will be reinforced. There are five boost levels. The counted duration of each stunt is indicated at the upper right under the ''stunt meter''. More difficult stunts such as longer wheelies and more consecutive somersaults are rewarded with more increase on the ''stunt meter''. If the player crashes, the ''stunt meter'' gets reset and gets spawned on the last checkpoint, which are marked as flags throughout stages. == Upgrades == There are five driving upgrades that apply to all characters' bikes: Top speed, acceleration, braking, boost, and spinning. Each can be upgraded up to ten levels. The cost of upgrading increases exponentially. The last upgrade costs $2000 in-game money. In-game money is earned through achievements, where each is rewarded with $200, and finishing in a good place, where the first is rewarded with $100, the second with $50, the third with $25, and the tenth with $1. On the moon level, where there are twenty racers in total, places 11 to 20 are not rewarded at all ($0). == Further observations == * The camera slightly moves while racing, possibly for a handheld filming effect. *The game features three distinct soundtracks for racing levels that are cycled through (no pun intended) per race, and one for "chase levels" that sounds somewhat like "Benny Hills". *''Autopilot mode'': When leaving the window in which the game plays while holding the "up" arrow key, the game will act as if the key is still held when it is not. This is best tried with "The Bowler Brothers" or "Trikeceratops", whose wide bikes are the least likely to flip upside down, the latter due to egg cargo trailer. * Sneaky start: hit <kbd>↑</kbd> arrow up just before race starts. == Cheat codes == The cheat codes are "Cheese", "Gerbil", "Elvis", and "Haddock" for "low gravity", "super gravity", "auto boost", and "haddock custome" respectively, of which only up to one can be activated at a time. While active, the game disallows earning money and unlocking achievements, meaning that the codes are just to be used for experimenting and fun, not to gain an advantage. [[Category:Games]] [[Category:Racing Games]] [[Category:Kongregate]] ---- '''4 Level Pinball''' is a pinball flash game with four pinball floors on top of each other. The game starts at the first floor, the beach. Above floors have themes of a farm, amusement park, and a shopping mall. Points can be collected by hitting various obstacles on the scene, such as a surfer on the beach, animals on the farm, and a locomotive on the theme park. Objects that have disappeared from hitting reappear when revisiting a floor after leaving. == External links == * [https://www.youtube.com/watch?v=7bDYI207O1Q&t=130s Gameplay video] ---- {{Game|image=Monster Truck Curfew.png|developer=IriySoft|publisher=Addicting Games|platform=Flash|genre=Action|mode=Single Player}} '''Monster Truck Curfew''' is an action flash game published [https://www.addictinggames.com/car/monster-truck-curfew on AddictingGames.com] by IriySoft<ref>In-Game credits ([[#Revision_history|2008 version]])</ref> and published on Addictinggames.com. It involves driving a monster truck through town to get home before midnight while crushing cars for points. == Controls == * '''Up:''' Accelerate * '''Down:''' Decelerate * '''Left/Right:''' Lean == Gameplay == [[File:Monster Truck Curfew Icon.jpeg|thumb]] Monster Truck Curfew has seven levels that you play one after another and must complete in under 10 minutes so that the main character, Suzy, can get home before midnight. In each level, your goal is to race to the end as fast as possible and flatten other vehicles by driving over them to earn points. However, you have to take care to avoid various hazards that appear from time to time; these hazards include pedestrians and animals trying to cross the road, vehicles approaching from a side road, and police cars with their sirens on. If you hit a hazard, or if the truck lands upside down, you'll be sent back to the beginning of the level. == Levels == # Town Road: A short level where the only hazard present is oncoming vehicles from side roads. # Main Road: A slightly longer level where pedestrians and animals will sometimes show up. # City Road: A longer level where police cars start to appear. # Construction Zone: An area where there are lots of obstacles (sand piles, pipes, barrels, etc.) which you'll have to navigate through. No vehicles or pedestrians appear here, but animals show up at certain points. # Construction Road: Another level where police cars appear often, and a few of the obstacles from the previous level also return. # City Outskirts: A level where hazards don't appear very often, but some of the vehicles behave more aggressively than usual. # Forest Road: Another level full of obstacles, this one featuring forest-themed obstacles like dirt piles and logs. Animals appear often as well. == Legacy == The game was played over 21 million times on the German flash game repository "SpielAffe", where it existed under the name "Trick Truck 2", and over 10 million times on "Y8.com".<ref>[http://web.archive.org/web/20160703172132/http://www.spielaffe.de/Spiel/Trick-Truck-2 "Trick Truck 2", SpielAffe.de, July 2016] (Note: SpielAffe.de largely purged their flash game repository around late 2020 to early 2021. The remaining ones such as "Blauer Bomber 2" are apparently served through a flash emulator web app.)</ref><ref>[https://www.y8.com/games/monster_truck_curfew Y8.com] "10,222,596 play times" as of 2021-07-24</ref> == Revision History == {| class=wikitable |+ Revision history |- ! Date (approximate) ! URL ! Changes and distinctions |- | June 2007<ref>[https://www.y8.com/games/monster_truck_curfew Y8.com] "Added on 24 Jun 2007"</ref> | [https://img-hws.y8.com/cloud/y8-flash-game/contents/item_versions/flash_games/2135/original/monster_truck_curfew.swf SWF (764 KB)] ([http://media2.gamesbox.com/games/files/3963.swf mirror]) | Earliest known version, possibly first published one. |- | ~2008 | [https://www.joypadmedia.com/emulator/f/frg/monster-truck-curfew.swf SWF (867 KB)] | * "Rules" button on title screen replaced with "How to play" and "About" * Deers added to level 4 and 7 * Blank space in level 7 filled * Glitch in level 6 with invisible trucks patched. * Skipping intro sequence also ends its audio playback, as intended. * Sound effect for hit magenta-dressed woman pedestrian added * Other minor changes in appearance |- |} == References == <references /> [[Category:Games]] [[Category:Racing Games]] [[Category:Action Games]] [[Category:Addicting Games]] ---- '''Imbossible''' is a jump-and-run flash game released by ''Tastyplay'' in late 2010, where a rabbit jumps through stages and completes challenges such as jumping over invisible blocks to get to a golden carrot owned by a masked boss animal.<ref name=SpielAffe>[http://web.archive.org/web/20121008005406/http://www.spielaffe.de/Spiel/Unmoeglich! ''Imbossible'' on SpielAffe.de, 2012-10-08, 1,167,102 plays]</ref> == Challenges == Challenges the rabbit needs to go through include invisible blocks, completing a stage at a shrinked size, a screen turned upside down, reordered arrow keys, intermittent darkness, automatic intermittent pausing, non-stop running, a sideways-rotated stage, random jumping. In the final bosses castle, several stages have a rotary board which selects a random challenge, and there is a party music level. The final boss is at an indefinitely tall tower which needs to be climbed along the boss. How exactly the game determines when the boss is gives up and the game is unknown, but it appears that a location outside of the viewport above needs to be reached, or the boss might just give up after some time. The secret word at the end is "Aye Aye". == Popularity == ''Imbossible'' was played over a million times on the German former flash game repository ''SpielAffe''.<ref name=SpielAffe /> == References == <references /> == External links == * [https://www.youtube.com/watch?v=Pkawrawj5DI Gameplay footage] [[Category:Games]] [[Category:Platformers]] ---- {{Game|title1=Twin Power|image=Twin Power.jpg|developer=Toonami|publisher=Andkon Arcade|platform=Flash|genre=Shooter|mode=Single Player|release=October 24, 2007|link(s)=<li>[http://www.andkon.com/arcade/shooter/twinpower/ Andkon Arcade] <li>[http://www.onemorelevel.com/game/twin_power One More Level] <li>[https://www.y8.com/games/twin_power Y8]}}'''Twin Power''' is a mid-2000s flash game developed by "Toonami", where obstacles need to be dodged and eliminated by shooting from a spacecraft. Although Flash was discontinued on January 12 2021, Twin Power is still playable through [[BlueMaxima's Flashpoint|BlueMaxima’s Flashpoint]]. == Spacecraft== The spacecraft can be in "attack mode" or "target mode", between which is switched using the "M" button according to the in-game manual, but any of the letters ZXCVBN (lowest row on keyboard) works as well. In "attack mode", the spacecraft shoots straight in frontal direction. When upgraded, smaller ammunitions are fired to the back side to provide some protection against attacks from the rear. In "target mode", bombs are dropped down to protect against hostile rockets from the bottom. When upgraded, ammunition rockets that sound somewhat like fireworks are shot in front direction to attack a wider surface. Shooting speed in "attack mode" is only limited by how fast the space bar button can be pressed in succession. If held down, it will shoot at a fixed speed lower than what is possible with individual presses. In "target mode", shooting speed is constant regardless of whether pressed repeatedly or held down. To upgrade the strength of each mode, the spacecraft needs to collect blue or orange chips respectively. Each can be upgraded to up to five levels, and both are at strength 2/5 at the beginning. A special larger and more circular-shaped chip which alternates between both of these colours allows the space craft to be in both modes simultaneously for ten seconds, hence "twin power". A background voice announces "power up!". ==Gameplay== The spacecraft is controlled with the arrow keys; ammunition is shot with the space bar. If the spacecraft collides with a hazard, all power-ups will be lost and the collected chips are released in the air, and one of three extra lives are lost. The player needs to try to recollect as many chips as possible to regain strength. At the end of each level, there is a final boss which shoots out hazardous small dots that need to be dodged, as those are immune against the spaceship's laser and rocket attacks. [[Category:Games]] [[Category:Shooting Games]] ---- RC car remote control shows speed (virtual number). Battery-powered. Some RC cars use petrol, apparently. . ---- A website is a service, but an operating system should be a product. WindowsAsAService (actually partially a misnomer, since the OS still runs locally) and ChromiumOS would be more like a website than a product. ---- mpioupc6qvupa6d6fpjqfj90f7qwuji 2383028 2383027 2022-03-12T01:47:15Z Seeaver 2935500 /* Lesenacht (Parodie) */ 2383028 wikitext text/x-wiki {{user sandbox}} == Lesenacht (Parodie) == REFRAIN: In der Computer,Computer,Computernacht wir surfen(o.spielen)Heut'bis Mitternacht, es wird kein Auge zugemacht, in der Computer,Computer,Computernacht! 1.Strophe: Ich spiele und ich träume, ich bin ein großer Held, und flieg' mit Super Mario um die ganze Welt!!! REFRAIN: In der Computer,Computer,Computernacht wir surfen(o.spielen)Heut'bis Mitternacht, es wird kein Auge zugemacht, in der Computer,Computer,Computernacht! 2.Strophe: Meine Freundin Suse lacht, was ist hier passiert? Die CD-ROM hat den Computer programmiert! REFRAIN: In der Computer,Computer,Computernacht wir surfen(o.spielen)Heut'bis Mitternacht, es wird kein Auge zugemacht, in der Computer,Computer,Computernacht! 3.Strophe: Und der Stephan neben mir, im schlottern schon die Knie, die Viruswebseite ist so schlimm wie noch nie!!! REFRAIN: In der Computer,Computer,Computernacht wir surfen(o.spielen)Heut'bis Mitternacht, es wird kein Auge zugemacht, in der Computer,Computer,Computernacht! 4.Strophe: ,,Nur eine,eine Webseite noch" bettelt Monika. Der Computer ist von einem Computervirus gerade in Gefahr! REFRAIN: In der Computer,Computer,Computernacht wir surfen(o.spielen)Heut'bis Mitternacht, es wird kein Auge zugemacht, in der Computer,Computer,Computernacht! ---- Parodie zum Lied „Lesenacht“, 2011-02-24. 3z7h6jbr8o0duzv7agqx58er589nqom 2383030 2383028 2022-03-12T01:58:35Z Seeaver 2935500 /* 90-second delay while booting */ 2383030 wikitext text/x-wiki The goal of this page is to list solutions to common issues. == 90-second delay while booting == Such a delay may be caused by an incorrect entry in the <code>/etc/fstab</code> file. This can especially be caused with [[:w:Live USB|live USB operating systems]] used across computers. Enter <code>blkid</code> into the command line terminal, then compare the output with the contents of aforementioned file. One of the entries, such as the entry for the swap file (which contains the word "swap"), may need to be removed or commented out by adding <code>#</code> at the beginning of the line.<ref>[https://forums.linuxmint.com/viewtopic.php?t=327483 ''Boot proces 90 seconds delay'' – LinuxMint Forums, August 2020]</ref> 3mwi2vhxlchl6p0qc7gthje0ysdy1o1 2383031 2383030 2022-03-12T02:02:45Z Seeaver 2935500 /* Mixing desktop environments */ 2383031 wikitext text/x-wiki The goal of this page is to list solutions to common issues. == 90-second delay while booting == Such a delay may be caused by an incorrect entry in the <code>/etc/fstab</code> file. This can especially be caused with [[:w:Live USB|live USB operating systems]] used across computers. Enter <code>blkid</code> into the command line terminal, then compare the output with the contents of aforementioned file. One of the entries, such as the entry for the swap file (which contains the word "swap"), may need to be removed or commented out by adding <code>#</code> at the beginning of the line.<ref>[https://forums.linuxmint.com/viewtopic.php?t=327483 ''Boot proces 90 seconds delay'' – LinuxMint Forums, August 2020]</ref> == Mixing desktop environments == Your preferred desktop environment might lack an essential feature such as the popular "Cinnamon" desktop environment lacking a multiple-row task bar.<ref>[https://forums.linuxmint.com/viewtopic.php?t=162727 ''Enable multiple rows in the daskbar'' – LinuxMint Forums, March 2014]</ref> It is possible to mix parts of desktop environments, such as using the <code>mate-panel</code> while other parts like the task switcher of ''Cinnamon'' are still operational. The ''Cinnamon'' task bar can be set to hide automatically in the configuration, whereas the multiple-row ''Mate'' taskbar can be made to always display on screen. 6zqblik8hbk06tdebio70elq4x2mb6i 2383032 2383031 2022-03-12T02:07:03Z Seeaver 2935500 /* Halting */ 2383032 wikitext text/x-wiki The goal of this page is to list solutions to common issues. == 90-second delay while booting == Such a delay may be caused by an incorrect entry in the <code>/etc/fstab</code> file. This can especially be caused with [[:w:Live USB|live USB operating systems]] used across computers. Enter <code>blkid</code> into the command line terminal, then compare the output with the contents of aforementioned file. One of the entries, such as the entry for the swap file (which contains the word "swap"), may need to be removed or commented out by adding <code>#</code> at the beginning of the line.<ref>[https://forums.linuxmint.com/viewtopic.php?t=327483 ''Boot proces 90 seconds delay'' – LinuxMint Forums, August 2020]</ref> == Mixing desktop environments == Your preferred desktop environment might lack an essential feature such as the popular "Cinnamon" desktop environment lacking a multiple-row task bar.<ref>[https://forums.linuxmint.com/viewtopic.php?t=162727 ''Enable multiple rows in the daskbar'' – LinuxMint Forums, March 2014]</ref> It is possible to mix parts of desktop environments, such as using the <code>mate-panel</code> while other parts like the task switcher of ''Cinnamon'' are still operational. The ''Cinnamon'' task bar can be set to hide automatically in the configuration, whereas the multiple-row ''Mate'' taskbar can be made to always display on screen. == Halting == If your computer halts ("freezes") frequently, the most common causes are tasks consuming high CPU or disk I/O usage. The former can be monitored with the command-line utilities including <code>top</code> (usually bundled), <code>htop</code> (more sophisticated but may require installation first), and the graphical <code>gnome-system-monitor</code>. Disk I/O usage can be monitored with the interactive command-line utility <code>iotop</code>, where the <code>-o</code> parameter hides inactive processes for a better overview. pzctz9tyfry80clq7ksivvt9uzhq4gn 2385301 2383032 2022-03-24T20:49:50Z Seeaver 2935500 /* siop_level */ markdown conversion 2385301 wikitext text/x-wiki == siop_level == ### Question <blockquote> I would like to hack some Samsung mobile phones to keep charging at full speed, even if the screen is turned on. For all Samsung flagships released late 2014 to 2018 (Note 4 to 9; S6 to S9), the maximum charging speed was 15 W. The maximum voltage the charging IC can handle is 10V, while the maximum current is 1.8A . The problem is that these 15W (USB input: 9V 1.67A) are invalidated as soon as the screen is turned on. Then, the total input power is only 6W, even if the charger offers current to spare. These 6 Watts are the **total** input power, which means that if the device needs 4 W, only 2 W remain for the battery. There is nothing that technically prevents these Samsung phones from keeping to charge at full speed while the screen is turned on. (And **during** AlwaysOn display, edge night clock, bootloader menu, during boot, shortly AFTER boot(!) and while displaying the battery charging screen when the device is not booted, in all of those cases, the charge speed is unaffected. So likely,, it has to do with the software asking the charging IC to draw less power.) I own a Powstro quick charger whose quick charging 3.0 (2.0 backwards compatible) port supports 2A at 9V, therefore the phone could draw 9V 1.8A from that charger. But I would be happy with 9V 1.67A. Much better than miserable 9V 0.67A! I have observed that specifically on the Galaxy Note 4, the screen-on limit (during device operation) is sometimes up to 10W, but it varies. I don't know what causes it to. But on newer Samsung mobiles, the limit is 6W. (9V 0.67A or 5V 1.2A. Also 6V 1.0A and anything inbetween if custom input voltage.) Another observation is that if the device negotiated the voltage through QuickCharge 2.0, the current is limited to 1.67A, even if the charger could deliver 2A. It was also 1.67A through a long USB cable with high resistance, which should have dropped the 9 Volts to somewhere in the 7 Volts. Without QuickCharge (manual 9V source), the device refuses to draw more power than 12W at any given voltage: (around 9V 1.33A, 8V 1.5A, 7V 1.7A, 6V 1.8A, 5V 1.8A due to 1.8A current limit.) During boot, it can actually draw **the full 9.8V 1.8A** from a custom voltage source (voltage drop compensated). Therefore, that 12W limitation is also sent by the software to the charging IC. ### How do I make these devices draw 9V 1.67A or even up to 9V 1.8A while the screen is turned on? About the overheating argument: When the battery temperature reaches 35°Celsius, the total input power gets cut down to 10W (9V 1.11A), occasionally 9V 1.0A anyway, even when when the phone is not booted, which means that it is controlled by the charging IC. Samsung's deliberate during-operation limitation of 6W (likely software-induced) while the screen is on, is 100% pointless and disadvantageous. #ChangeMyMind. Good luck. (To whoever had that idea, i.e. Hyun Yeul Lee: If you are reading this, please explain your decision. All your users suffer from this limitation.) In addition, this 6W limitation even existed **before the Galaxy Note 4!** Both S4 and Note 3 from 2013 (max. 6V 1.75A) limit the charging wattage to 6W while the screen is on. Some other mobile phones such as the UleFone Armor 2 (maximum input voltage: 14 V, current: 1.8A; battery itself charges at 10W.) just draws the charger's spare current when the screen is turned on and the USB data lanes are shorted (if not shorted, max.: 0.5 A). This charging behavior is what pretty much every laptop is doing for decades, provided that the power supply is sufficiently strong. This allows charging the battery at the original speed while the device is in use. The additional power needed to power the device itself will not be subtracted from the battery charging speed but drawn **in addition** from the power supply, which is the correct (best) way to do it. </blockquote> ### Answer 14j84nlzdwl6uonysb7tpp67e74a2f3 2385303 2385301 2022-03-24T20:51:50Z Seeaver 2935500 2385303 wikitext text/x-wiki {| class="wikitable sortable" |+ |- !Brand name !Slogan !Establishment year{{efn|Year of the original establishment, not first sold flash storage due to being poorly documented online.}} !Flash storage types !Manufacturing quality{{efn|A higher manufacturing quality increases [[Data loss prevention#flash|reliability in unstable conditions and prolonged data retention]].}} |- |[[SanDisk]] | |1988 |USB, SD, MicroSD, SSD |data-sort-key=4| Very high |- |[[Panasonic]] | |1918 |SD, MicroSD |data-sort-key=4|Very high |- |[[Sony]] | |1946 | |- |[[Transcend]] | |1988 |USB, SD, MicroSD, SSD |data-sort-key=4| Very high |- |[[Toshiba]] |Leading innovation | |USB, SD, MicroSD, SSD |data-sort-key=4| Very high |- |[[Kingston]] | |1987 |USB, SD, MicroSD, CF, SSD |data-sort-key=4| Very high |- |[[Intenso]] | | |USB, SD, MicroSD |data-sort-key=3| High |- |[[Integral]] | | |SD, MicroSD |data-sort-key=2| Moderate |- |[[Verbatim]] | | |USB, SD, MicroSD |data-sort-key=3| High |- |[[Hama]] |The smart solution |1923 |USB, SD, MicroSD |data-sort-key=1| Low |- |[[PNY Technologies]] | |1970 |USB, SD, MicroSD |data-sort-key=2|Moderate |} q5zphde58wawdfu85wk866l9p7yvscu 2385306 2385303 2022-03-24T20:54:23Z Seeaver 2935500 forgot to resume 2385306 wikitext text/x-wiki The goal of this page is to list solutions to common issues. == 90-second delay while booting == Such a delay may be caused by an incorrect entry in the <code>/etc/fstab</code> file. This can especially be caused with [[:w:Live USB|live USB operating systems]] used across computers. Enter <code>blkid</code> into the command line terminal, then compare the output with the contents of aforementioned file. One of the entries, such as the entry for the swap file (which contains the word "swap"), may need to be removed or commented out by adding <code>#</code> at the beginning of the line.<ref>[https://forums.linuxmint.com/viewtopic.php?t=327483 ''Boot proces 90 seconds delay'' – LinuxMint Forums, August 2020]</ref> == Mixing desktop environments == Your preferred desktop environment might lack an essential feature such as the popular "Cinnamon" desktop environment lacking a multiple-row task bar.<ref>[https://forums.linuxmint.com/viewtopic.php?t=162727 ''Enable multiple rows in the daskbar'' – LinuxMint Forums, March 2014]</ref> It is possible to mix parts of desktop environments, such as using the <code>mate-panel</code> while other parts like the task switcher of ''Cinnamon'' are still operational. The ''Cinnamon'' task bar can be set to hide automatically in the configuration, whereas the multiple-row ''Mate'' taskbar can be made to always display on screen. == Halting == If your computer halts ("freezes") frequently, the most common causes are tasks consuming high CPU or disk I/O usage. The former can be monitored with the command-line utilities including <code>top</code> (usually bundled), <code>htop</code> (more sophisticated but may require installation first), and the graphical <code>gnome-system-monitor</code>. Disk I/O usage can be monitored with the interactive command-line utility <code>iotop</code>, where the <code>-o</code> parameter hides inactive processes for a better overview. pzctz9tyfry80clq7ksivvt9uzhq4gn 2385313 2385306 2022-03-24T21:42:37Z Seeaver 2935500 /* Halted window manager */ 2385313 wikitext text/x-wiki The goal of this page is to list solutions to common issues. == 90-second delay while booting == Such a delay may be caused by an incorrect entry in the <code>/etc/fstab</code> file. This can especially be caused with [[:w:Live USB|live USB operating systems]] used across computers. Enter <code>blkid</code> into the command line terminal, then compare the output with the contents of aforementioned file. One of the entries, such as the entry for the swap file (which contains the word "swap"), may need to be removed or commented out by adding <code>#</code> at the beginning of the line.<ref>[https://forums.linuxmint.com/viewtopic.php?t=327483 ''Boot proces 90 seconds delay'' – LinuxMint Forums, August 2020]</ref> == Mixing desktop environments == Your preferred desktop environment might lack an essential feature such as the popular "Cinnamon" desktop environment lacking a multiple-row task bar.<ref>[https://forums.linuxmint.com/viewtopic.php?t=162727 ''Enable multiple rows in the daskbar'' – LinuxMint Forums, March 2014]</ref><ref>[https://forums.linuxmint.com/viewtopic.php?t=239297 Resize panel/taskbar for two rows? - Linux Mint Forums, February 2017]</ref> It is possible to mix parts of desktop environments, such as using the <code>mate-panel</code> while other parts like the task switcher of ''Cinnamon'' are still operational. The ''Cinnamon'' task bar can be set to hide automatically in the configuration, whereas the multiple-row ''Mate'' taskbar can be made to always display on screen. == Halting == If your computer halts ("freezes") frequently, the most common causes are tasks consuming high CPU or disk I/O usage. The former can be monitored with the command-line utilities including <code>top</code> (usually bundled), <code>htop</code> (more sophisticated but may require installation first), and the graphical <code>gnome-system-monitor</code>. Disk I/O usage can be monitored with the interactive command-line utility <code>iotop</code>, where the <code>-o</code> parameter hides inactive processes for a better overview. A high I/O usage may not only caused by reads and writes themselves, but can also be caused by latency. This is not of concern on flash storages, but it is on hard disk drives, since the magnetic head needs an additional fraction of a second to move to the physical location of requested data. == Halted window manager == If the cursor has become unresponsive, and you wish to get out of it without losing your session, try the following: * Go to a different ''[[:w:tty (Unix)|tty]]'', for example, press Ctrl+Alt+F2 to go to tty2. * Type the <code>w</code> command to list active sessions. Notice the content of the <code>FROM</code> column, possibly <code>:0</code>. * Type <code>[process name of desktop environment] --replace --display=:0 2>/dev/null &</code>. Process names for desktop environments include <code>cinnamon</code>, <code>mate-panel</code> or <code>wm-mate</code> ("window manager MATE"), <code>xfwm4</code> (for xfce), and <code>kwin_x11</code> or <code>plasmashell</code> for KDE.<ref>[https://www.reddit.com/r/kde/comments/a5d2ly/how_do_you_properly_restart_kwin_and_plasmashell/ ''How do you properly restart KWin and Plasmashell from the virtual console?'' – /r/KDE, December 2018]</ref> The <code>:0</code> part is from the "FROM" column in the prior command, the <code>2>/dev/null</code> part prevents diagnostic error messages from flooding the command line output, and the <code>&</code> character puts the process in background.<ref>[https://unix.stackexchange.com/questions/31818/what-to-do-when-a-linux-desktop-freezes ''What to do when a Linux desktop freezes?'' - Unix & Linux Stack Exchange]</ref> hmvgi1doiqm9haehpfjixse5ol57qr1 2385331 2385313 2022-03-24T22:31:48Z Seeaver 2935500 /* Mixing desktop environments */ autostart 2385331 wikitext text/x-wiki The goal of this page is to list solutions to common issues. == 90-second delay while booting == Such a delay may be caused by an incorrect entry in the <code>/etc/fstab</code> file. This can especially be caused with [[:w:Live USB|live USB operating systems]] used across computers. Enter <code>blkid</code> into the command line terminal, then compare the output with the contents of aforementioned file. One of the entries, such as the entry for the swap file (which contains the word "swap"), may need to be removed or commented out by adding <code>#</code> at the beginning of the line.<ref>[https://forums.linuxmint.com/viewtopic.php?t=327483 ''Boot proces 90 seconds delay'' – LinuxMint Forums, August 2020]</ref> == Mixing desktop environments == Your preferred desktop environment might lack an essential feature such as the popular "Cinnamon" desktop environment lacking a multiple-row task bar.<ref>[https://forums.linuxmint.com/viewtopic.php?t=162727 ''Enable multiple rows in the daskbar'' – LinuxMint Forums, March 2014]</ref><ref>[https://forums.linuxmint.com/viewtopic.php?t=239297 Resize panel/taskbar for two rows? - Linux Mint Forums, February 2017]</ref> It is possible to mix parts of desktop environments, such as using the <code>mate-panel</code> while other parts like the task switcher of ''Cinnamon'' are still operational. The ''Cinnamon'' task bar can be set to hide automatically in the configuration, whereas the multiple-row ''Mate'' taskbar can be made to always display on screen. In order to start multiple panels automatically, add one of them to the list of programs to start automatically. Typically, it is found in the system control panel, though the location may vary across desktop environments. == Halting == If your computer halts ("freezes") frequently, the most common causes are tasks consuming high CPU or disk I/O usage. The former can be monitored with the command-line utilities including <code>top</code> (usually bundled), <code>htop</code> (more sophisticated but may require installation first), and the graphical <code>gnome-system-monitor</code>. Disk I/O usage can be monitored with the interactive command-line utility <code>iotop</code>, where the <code>-o</code> parameter hides inactive processes for a better overview. A high I/O usage may not only caused by reads and writes themselves, but can also be caused by latency. This is not of concern on flash storages, but it is on hard disk drives, since the magnetic head needs an additional fraction of a second to move to the physical location of requested data. == Halted window manager == If the cursor has become unresponsive, and you wish to get out of it without losing your session, try the following: * Go to a different ''[[:w:tty (Unix)|tty]]'', for example, press Ctrl+Alt+F2 to go to tty2. * Type the <code>w</code> command to list active sessions. Notice the content of the <code>FROM</code> column, possibly <code>:0</code>. * Type <code>[process name of desktop environment] --replace --display=:0 2>/dev/null &</code>. Process names for desktop environments include <code>cinnamon</code>, <code>mate-panel</code> or <code>wm-mate</code> ("window manager MATE"), <code>xfwm4</code> (for xfce), and <code>kwin_x11</code> or <code>plasmashell</code> for KDE.<ref>[https://www.reddit.com/r/kde/comments/a5d2ly/how_do_you_properly_restart_kwin_and_plasmashell/ ''How do you properly restart KWin and Plasmashell from the virtual console?'' – /r/KDE, December 2018]</ref> The <code>:0</code> part is from the "FROM" column in the prior command, the <code>2>/dev/null</code> part prevents diagnostic error messages from flooding the command line output, and the <code>&</code> character puts the process in background.<ref>[https://unix.stackexchange.com/questions/31818/what-to-do-when-a-linux-desktop-freezes ''What to do when a Linux desktop freezes?'' - Unix & Linux Stack Exchange]</ref> 8zn4b7oye1y5v5ir8n8sbm0awu6ho9r 2385393 2385331 2022-03-25T01:56:25Z Seeaver 2935500 Inviting readers to add sections. 2385393 wikitext text/x-wiki The goal of this page is to list solutions to common issues. You are encouraged to add yours here. <!--In future, if this page gets too long, it could be split into sub pages.--> == 90-second delay while booting == Such a delay may be caused by an incorrect entry in the <code>/etc/fstab</code> file. This can especially be caused with [[:w:Live USB|live USB operating systems]] used across computers. Enter <code>blkid</code> into the command line terminal, then compare the output with the contents of aforementioned file. One of the entries, such as the entry for the swap file (which contains the word "swap"), may need to be removed or commented out by adding <code>#</code> at the beginning of the line.<ref>[https://forums.linuxmint.com/viewtopic.php?t=327483 ''Boot proces 90 seconds delay'' – LinuxMint Forums, August 2020]</ref> == Mixing desktop environments == Your preferred desktop environment might lack an essential feature such as the popular "Cinnamon" desktop environment lacking a multiple-row task bar.<ref>[https://forums.linuxmint.com/viewtopic.php?t=162727 ''Enable multiple rows in the daskbar'' – LinuxMint Forums, March 2014]</ref><ref>[https://forums.linuxmint.com/viewtopic.php?t=239297 Resize panel/taskbar for two rows? - Linux Mint Forums, February 2017]</ref> It is possible to mix parts of desktop environments, such as using the <code>mate-panel</code> while other parts like the task switcher of ''Cinnamon'' are still operational. The ''Cinnamon'' task bar can be set to hide automatically in the configuration, whereas the multiple-row ''Mate'' taskbar can be made to always display on screen. In order to start multiple panels automatically, add one of them to the list of programs to start automatically. Typically, it is found in the system control panel, though the location may vary across desktop environments. == Halting == If your computer halts ("freezes") frequently, the most common causes are tasks consuming high CPU or disk I/O usage. The former can be monitored with the command-line utilities including <code>top</code> (usually bundled), <code>htop</code> (more sophisticated but may require installation first), and the graphical <code>gnome-system-monitor</code>. Disk I/O usage can be monitored with the interactive command-line utility <code>iotop</code>, where the <code>-o</code> parameter hides inactive processes for a better overview. A high I/O usage may not only caused by reads and writes themselves, but can also be caused by latency. This is not of concern on flash storages, but it is on hard disk drives, since the magnetic head needs an additional fraction of a second to move to the physical location of requested data. == Halted window manager == If the cursor has become unresponsive, and you wish to get out of it without losing your session, try the following: * Go to a different ''[[:w:tty (Unix)|tty]]'', for example, press Ctrl+Alt+F2 to go to tty2. * Type the <code>w</code> command to list active sessions. Notice the content of the <code>FROM</code> column, possibly <code>:0</code>. * Type <code>[process name of desktop environment] --replace --display=:0 2>/dev/null &</code>. Process names for desktop environments include <code>cinnamon</code>, <code>mate-panel</code> or <code>wm-mate</code> ("window manager MATE"), <code>xfwm4</code> (for xfce), and <code>kwin_x11</code> or <code>plasmashell</code> for KDE.<ref>[https://www.reddit.com/r/kde/comments/a5d2ly/how_do_you_properly_restart_kwin_and_plasmashell/ ''How do you properly restart KWin and Plasmashell from the virtual console?'' – /r/KDE, December 2018]</ref> The <code>:0</code> part is from the "FROM" column in the prior command, the <code>2>/dev/null</code> part prevents diagnostic error messages from flooding the command line output, and the <code>&</code> character puts the process in background.<ref>[https://unix.stackexchange.com/questions/31818/what-to-do-when-a-linux-desktop-freezes ''What to do when a Linux desktop freezes?'' - Unix & Linux Stack Exchange]</ref> 5dmq11btu8zeuh4j690v3lhq25wbgjq 2385394 2385393 2022-03-25T01:57:41Z Seeaver 2935500 Seeaver moved page [[User:Seeaver/sandbox]] to [[Linux/Troubleshooting]]: Resource developed sufficiently for main space. 2385393 wikitext text/x-wiki The goal of this page is to list solutions to common issues. You are encouraged to add yours here. <!--In future, if this page gets too long, it could be split into sub pages.--> == 90-second delay while booting == Such a delay may be caused by an incorrect entry in the <code>/etc/fstab</code> file. This can especially be caused with [[:w:Live USB|live USB operating systems]] used across computers. Enter <code>blkid</code> into the command line terminal, then compare the output with the contents of aforementioned file. One of the entries, such as the entry for the swap file (which contains the word "swap"), may need to be removed or commented out by adding <code>#</code> at the beginning of the line.<ref>[https://forums.linuxmint.com/viewtopic.php?t=327483 ''Boot proces 90 seconds delay'' – LinuxMint Forums, August 2020]</ref> == Mixing desktop environments == Your preferred desktop environment might lack an essential feature such as the popular "Cinnamon" desktop environment lacking a multiple-row task bar.<ref>[https://forums.linuxmint.com/viewtopic.php?t=162727 ''Enable multiple rows in the daskbar'' – LinuxMint Forums, March 2014]</ref><ref>[https://forums.linuxmint.com/viewtopic.php?t=239297 Resize panel/taskbar for two rows? - Linux Mint Forums, February 2017]</ref> It is possible to mix parts of desktop environments, such as using the <code>mate-panel</code> while other parts like the task switcher of ''Cinnamon'' are still operational. The ''Cinnamon'' task bar can be set to hide automatically in the configuration, whereas the multiple-row ''Mate'' taskbar can be made to always display on screen. In order to start multiple panels automatically, add one of them to the list of programs to start automatically. Typically, it is found in the system control panel, though the location may vary across desktop environments. == Halting == If your computer halts ("freezes") frequently, the most common causes are tasks consuming high CPU or disk I/O usage. The former can be monitored with the command-line utilities including <code>top</code> (usually bundled), <code>htop</code> (more sophisticated but may require installation first), and the graphical <code>gnome-system-monitor</code>. Disk I/O usage can be monitored with the interactive command-line utility <code>iotop</code>, where the <code>-o</code> parameter hides inactive processes for a better overview. A high I/O usage may not only caused by reads and writes themselves, but can also be caused by latency. This is not of concern on flash storages, but it is on hard disk drives, since the magnetic head needs an additional fraction of a second to move to the physical location of requested data. == Halted window manager == If the cursor has become unresponsive, and you wish to get out of it without losing your session, try the following: * Go to a different ''[[:w:tty (Unix)|tty]]'', for example, press Ctrl+Alt+F2 to go to tty2. * Type the <code>w</code> command to list active sessions. Notice the content of the <code>FROM</code> column, possibly <code>:0</code>. * Type <code>[process name of desktop environment] --replace --display=:0 2>/dev/null &</code>. Process names for desktop environments include <code>cinnamon</code>, <code>mate-panel</code> or <code>wm-mate</code> ("window manager MATE"), <code>xfwm4</code> (for xfce), and <code>kwin_x11</code> or <code>plasmashell</code> for KDE.<ref>[https://www.reddit.com/r/kde/comments/a5d2ly/how_do_you_properly_restart_kwin_and_plasmashell/ ''How do you properly restart KWin and Plasmashell from the virtual console?'' – /r/KDE, December 2018]</ref> The <code>:0</code> part is from the "FROM" column in the prior command, the <code>2>/dev/null</code> part prevents diagnostic error messages from flooding the command line output, and the <code>&</code> character puts the process in background.<ref>[https://unix.stackexchange.com/questions/31818/what-to-do-when-a-linux-desktop-freezes ''What to do when a Linux desktop freezes?'' - Unix & Linux Stack Exchange]</ref> 5dmq11btu8zeuh4j690v3lhq25wbgjq 2385396 2385394 2022-03-25T01:59:29Z Seeaver 2935500 /* References */ 2385396 wikitext text/x-wiki The goal of this page is to list solutions to common issues. You are encouraged to add yours here. <!--In future, if this page gets too long, it could be split into sub pages.--> == 90-second delay while booting == Such a delay may be caused by an incorrect entry in the <code>/etc/fstab</code> file. This can especially be caused with [[:w:Live USB|live USB operating systems]] used across computers. Enter <code>blkid</code> into the command line terminal, then compare the output with the contents of aforementioned file. One of the entries, such as the entry for the swap file (which contains the word "swap"), may need to be removed or commented out by adding <code>#</code> at the beginning of the line.<ref>[https://forums.linuxmint.com/viewtopic.php?t=327483 ''Boot proces 90 seconds delay'' – LinuxMint Forums, August 2020]</ref> == Mixing desktop environments == Your preferred desktop environment might lack an essential feature such as the popular "Cinnamon" desktop environment lacking a multiple-row task bar.<ref>[https://forums.linuxmint.com/viewtopic.php?t=162727 ''Enable multiple rows in the daskbar'' – LinuxMint Forums, March 2014]</ref><ref>[https://forums.linuxmint.com/viewtopic.php?t=239297 Resize panel/taskbar for two rows? - Linux Mint Forums, February 2017]</ref> It is possible to mix parts of desktop environments, such as using the <code>mate-panel</code> while other parts like the task switcher of ''Cinnamon'' are still operational. The ''Cinnamon'' task bar can be set to hide automatically in the configuration, whereas the multiple-row ''Mate'' taskbar can be made to always display on screen. In order to start multiple panels automatically, add one of them to the list of programs to start automatically. Typically, it is found in the system control panel, though the location may vary across desktop environments. == Halting == If your computer halts ("freezes") frequently, the most common causes are tasks consuming high CPU or disk I/O usage. The former can be monitored with the command-line utilities including <code>top</code> (usually bundled), <code>htop</code> (more sophisticated but may require installation first), and the graphical <code>gnome-system-monitor</code>. Disk I/O usage can be monitored with the interactive command-line utility <code>iotop</code>, where the <code>-o</code> parameter hides inactive processes for a better overview. A high I/O usage may not only caused by reads and writes themselves, but can also be caused by latency. This is not of concern on flash storages, but it is on hard disk drives, since the magnetic head needs an additional fraction of a second to move to the physical location of requested data. == Halted window manager == If the cursor has become unresponsive, and you wish to get out of it without losing your session, try the following: * Go to a different ''[[:w:tty (Unix)|tty]]'', for example, press Ctrl+Alt+F2 to go to tty2. * Type the <code>w</code> command to list active sessions. Notice the content of the <code>FROM</code> column, possibly <code>:0</code>. * Type <code>[process name of desktop environment] --replace --display=:0 2>/dev/null &</code>. Process names for desktop environments include <code>cinnamon</code>, <code>mate-panel</code> or <code>wm-mate</code> ("window manager MATE"), <code>xfwm4</code> (for xfce), and <code>kwin_x11</code> or <code>plasmashell</code> for KDE.<ref>[https://www.reddit.com/r/kde/comments/a5d2ly/how_do_you_properly_restart_kwin_and_plasmashell/ ''How do you properly restart KWin and Plasmashell from the virtual console?'' – /r/KDE, December 2018]</ref> The <code>:0</code> part is from the "FROM" column in the prior command, the <code>2>/dev/null</code> part prevents diagnostic error messages from flooding the command line output, and the <code>&</code> character puts the process in background.<ref>[https://unix.stackexchange.com/questions/31818/what-to-do-when-a-linux-desktop-freezes ''What to do when a Linux desktop freezes?'' - Unix & Linux Stack Exchange]</ref> == References == <references /> seprjor2xehc7dm84mn0u399uyxgv7n 2387783 2385396 2022-04-07T01:16:59Z Seeaver 2935500 /* Password fail delay */ added 2387783 wikitext text/x-wiki The goal of this page is to list solutions to common issues. You are encouraged to add yours here. <!--In future, if this page gets too long, it could be split into sub pages.--> == 90-second delay while booting == Such a delay may be caused by an incorrect entry in the <code>/etc/fstab</code> file. This can especially be caused with [[:w:Live USB|live USB operating systems]] used across computers. Enter <code>blkid</code> into the command line terminal, then compare the output with the contents of aforementioned file. One of the entries, such as the entry for the swap file (which contains the word "swap"), may need to be removed or commented out by adding <code>#</code> at the beginning of the line.<ref>[https://forums.linuxmint.com/viewtopic.php?t=327483 ''Boot proces 90 seconds delay'' – LinuxMint Forums, August 2020]</ref> == Mixing desktop environments == Your preferred desktop environment might lack an essential feature such as the popular "Cinnamon" desktop environment lacking a multiple-row task bar.<ref>[https://forums.linuxmint.com/viewtopic.php?t=162727 ''Enable multiple rows in the daskbar'' – LinuxMint Forums, March 2014]</ref><ref>[https://forums.linuxmint.com/viewtopic.php?t=239297 Resize panel/taskbar for two rows? - Linux Mint Forums, February 2017]</ref> It is possible to mix parts of desktop environments, such as using the <code>mate-panel</code> while other parts like the task switcher of ''Cinnamon'' are still operational. The ''Cinnamon'' task bar can be set to hide automatically in the configuration, whereas the multiple-row ''Mate'' taskbar can be made to always display on screen. In order to start multiple panels automatically, add one of them to the list of programs to start automatically. Typically, it is found in the system control panel, though the location may vary across desktop environments. == Halting == If your computer halts ("freezes") frequently, the most common causes are tasks consuming high CPU or disk I/O usage. The former can be monitored with the command-line utilities including <code>top</code> (usually bundled), <code>htop</code> (more sophisticated but may require installation first), and the graphical <code>gnome-system-monitor</code>. Disk I/O usage can be monitored with the interactive command-line utility <code>iotop</code>, where the <code>-o</code> parameter hides inactive processes for a better overview. A high I/O usage may not only caused by reads and writes themselves, but can also be caused by latency. This is not of concern on flash storages, but it is on hard disk drives, since the magnetic head needs an additional fraction of a second to move to the physical location of requested data. == Halted window manager == If the cursor has become unresponsive, and you wish to get out of it without losing your session, try the following: * Go to a different ''[[:w:tty (Unix)|tty]]'', for example, press Ctrl+Alt+F2 to go to tty2. * Type the <code>w</code> command to list active sessions. Notice the content of the <code>FROM</code> column, possibly <code>:0</code>. * Type <code>[process name of desktop environment] --replace --display=:0 2>/dev/null &</code>. Process names for desktop environments include <code>cinnamon</code>, <code>mate-panel</code> or <code>wm-mate</code> ("window manager MATE"), <code>xfwm4</code> (for xfce), and <code>kwin_x11</code> or <code>plasmashell</code> for KDE.<ref>[https://www.reddit.com/r/kde/comments/a5d2ly/how_do_you_properly_restart_kwin_and_plasmashell/ ''How do you properly restart KWin and Plasmashell from the virtual console?'' – /r/KDE, December 2018]</ref> The <code>:0</code> part is from the "FROM" column in the prior command, the <code>2>/dev/null</code> part prevents diagnostic error messages from flooding the command line output, and the <code>&</code> character puts the process in background.<ref>[https://unix.stackexchange.com/questions/31818/what-to-do-when-a-linux-desktop-freezes ''What to do when a Linux desktop freezes?'' - Unix & Linux Stack Exchange]</ref> == Password fail delay == Linux installations may be shipped with a long password fail delay, meaning an artificial delay until the user is allowed to retry after entering a wrong password. While it is intended to prevent password cracking through brute-forcing, a delay that is too long, such as three seconds, could become annoying from repetition and interfere with workflow. The fail delay is not recommended to be deactivated completely, but can be shortened to something more sufferable like 0.3 seconds. The disadvantage that brute forcing would become faster could be compensated multiple times over by appending one or two characters to the password. However, even at a fail delay of 0.01 seconds, brute forcing would be severely handicapped. As such, a preset fail delay of three seconds appears to be [[:w:Security theater|security theater]]. ;Setting There are multiple system files where the password fail delay may be configurable. Make sure to create a backup copy of of any system file before modifying. The exact used system file may vary depending on operating system distribution and version, but the configuration is typically located at <code>/etc/pam.d/common-auth</code> or <code>/etc/pam.d/login</code>, and the delay value is specified in microseconds. For example, to set the password delay to the tenth of a second, set the pre-existing value in the "login" file, which is presumably 3000000 out of the box, to "100000", as shown here: <pre> # # The PAM configuration file for the Shadow `login' service # # Enforce a minimal delay in case of failure (in microseconds). # (Replaces the `FAIL_DELAY' setting from login.defs) # Note that other modules may require another minimal delay. (for example, # to disable any delay, you should add the nodelay option to pam_unix) auth optional pam_faildelay.so delay=100000 </pre> Alternatively, try adding the new line <code>auth optional pam_faildelay.so delay=100000</code> to the "common-auth" file at this position: <pre> # here are the per-package modules (the "Primary" block) auth optional pam_faildelay.so delay=100000 auth [success=1 default=ignore] pam_unix.so nullok_secure nodelay </pre> <ref>[https://unix.stackexchange.com/questions/2126/why-is-there-a-big-delay-after-entering-a-wrong-password security - Why is there a big delay after entering a wrong password? - Unix & Linux Stack Exchange]</ref> == References == <references /> 74tmq9xbc26ecqlx9z86pwo80f7kjx8 2392352 2387783 2022-05-04T12:44:20Z TheSharpShark 2942382 "/proc/sys/kernel/sysrq" /* sysrq */ 2392352 wikitext text/x-wiki The goal of this page is to list solutions to common issues. You are encouraged to add yours here. <!--In future, if this page gets too long, it could be split into sub pages.--> == 90-second delay while booting == Such a delay may be caused by an incorrect entry in the <code>/etc/fstab</code> file. This can especially be caused with [[:w:Live USB|live USB operating systems]] used across computers. Enter <code>blkid</code> into the command line terminal, then compare the output with the contents of aforementioned file. One of the entries, such as the entry for the swap file (which contains the word "swap"), may need to be removed or commented out by adding <code>#</code> at the beginning of the line.<ref>[https://forums.linuxmint.com/viewtopic.php?t=327483 ''Boot proces 90 seconds delay'' – LinuxMint Forums, August 2020]</ref> == sysrq == Some [[:wikipedia:Magic_SysRq_key|system requests]] might be disabled out of the box due to the [[:wikipedia:bitmask|bitmask]] value in the file <code>/proc/sys/kernel/sysrq</code> being set to a different value than 1, such as 176. A possible reason is to protect inexperienced users. To override this, use the command <code>echo 1 | sudo tee /proc/sys/kernel/sysrq</code>, where the number "1" is piped into "tee", and <code>sudo tee</code> writes the "1" into said system file using root privileges. Directly <code>sudo echo 1 >/proc/sys/kernel/sysrq</code> or <code>sudo printf 1 >/proc/sys/kernel/sysrq</code> does not work if the terminal is not running as root, since text redirection into the file is performed by the terminal, whereas with <code>sudo tee</code>, it is performed by the <code>tee</code> tool using root privileges. == Mixing desktop environments == Your preferred desktop environment might lack an essential feature such as the popular "Cinnamon" desktop environment lacking a multiple-row task bar.<ref>[https://forums.linuxmint.com/viewtopic.php?t=162727 ''Enable multiple rows in the daskbar'' – LinuxMint Forums, March 2014]</ref><ref>[https://forums.linuxmint.com/viewtopic.php?t=239297 Resize panel/taskbar for two rows? - Linux Mint Forums, February 2017]</ref> It is possible to mix parts of desktop environments, such as using the <code>mate-panel</code> while other parts like the task switcher of ''Cinnamon'' are still operational. The ''Cinnamon'' task bar can be set to hide automatically in the configuration, whereas the multiple-row ''Mate'' taskbar can be made to always display on screen. In order to start multiple panels automatically, add one of them to the list of programs to start automatically. Typically, it is found in the system control panel, though the location may vary across desktop environments. == Halting == If your computer halts ("freezes") frequently, the most common causes are tasks consuming high CPU or disk I/O usage. The former can be monitored with the command-line utilities including <code>top</code> (usually bundled), <code>htop</code> (more sophisticated but may require installation first), and the graphical <code>gnome-system-monitor</code>. Disk I/O usage can be monitored with the interactive command-line utility <code>iotop</code>, where the <code>-o</code> parameter hides inactive processes for a better overview. A high I/O usage may not only caused by reads and writes themselves, but can also be caused by latency. This is not of concern on flash storages, but it is on hard disk drives, since the magnetic head needs an additional fraction of a second to move to the physical location of requested data. == Halted window manager == If the cursor has become unresponsive, and you wish to get out of it without losing your session, try the following: * Go to a different ''[[:w:tty (Unix)|tty]]'', for example, press Ctrl+Alt+F2 to go to tty2. * Type the <code>w</code> command to list active sessions. Notice the content of the <code>FROM</code> column, possibly <code>:0</code>. * Type <code>[process name of desktop environment] --replace --display=:0 2>/dev/null &</code>. Process names for desktop environments include <code>cinnamon</code>, <code>mate-panel</code> or <code>wm-mate</code> ("window manager MATE"), <code>xfwm4</code> (for xfce), and <code>kwin_x11</code> or <code>plasmashell</code> for KDE.<ref>[https://www.reddit.com/r/kde/comments/a5d2ly/how_do_you_properly_restart_kwin_and_plasmashell/ ''How do you properly restart KWin and Plasmashell from the virtual console?'' – /r/KDE, December 2018]</ref> The <code>:0</code> part is from the "FROM" column in the prior command, the <code>2>/dev/null</code> part prevents diagnostic error messages from flooding the command line output, and the <code>&</code> character puts the process in background.<ref>[https://unix.stackexchange.com/questions/31818/what-to-do-when-a-linux-desktop-freezes ''What to do when a Linux desktop freezes?'' - Unix & Linux Stack Exchange]</ref> == Password fail delay == Linux installations may be shipped with a long password fail delay, meaning an artificial delay until the user is allowed to retry after entering a wrong password. While it is intended to prevent password cracking through brute-forcing, a delay that is too long, such as three seconds, could become annoying from repetition and interfere with workflow. The fail delay is not recommended to be deactivated completely, but can be shortened to something more sufferable like 0.3 seconds. The disadvantage that brute forcing would become faster could be compensated multiple times over by appending one or two characters to the password. However, even at a fail delay of 0.01 seconds, brute forcing would be severely handicapped. As such, a preset fail delay of three seconds appears to be [[:w:Security theater|security theater]]. ;Setting There are multiple system files where the password fail delay may be configurable. Make sure to create a backup copy of of any system file before modifying. The exact used system file may vary depending on operating system distribution and version, but the configuration is typically located at <code>/etc/pam.d/common-auth</code> or <code>/etc/pam.d/login</code>, and the delay value is specified in microseconds. For example, to set the password delay to the tenth of a second, set the pre-existing value in the "login" file, which is presumably 3000000 out of the box, to "100000", as shown here: <pre> # # The PAM configuration file for the Shadow `login' service # # Enforce a minimal delay in case of failure (in microseconds). # (Replaces the `FAIL_DELAY' setting from login.defs) # Note that other modules may require another minimal delay. (for example, # to disable any delay, you should add the nodelay option to pam_unix) auth optional pam_faildelay.so delay=100000 </pre> Alternatively, try adding the new line <code>auth optional pam_faildelay.so delay=100000</code> to the "common-auth" file at this position: <pre> # here are the per-package modules (the "Primary" block) auth optional pam_faildelay.so delay=100000 auth [success=1 default=ignore] pam_unix.so nullok_secure nodelay </pre> <ref>[https://unix.stackexchange.com/questions/2126/why-is-there-a-big-delay-after-entering-a-wrong-password security - Why is there a big delay after entering a wrong password? - Unix & Linux Stack Exchange]</ref> == References == <references /> g38f5ycg19nunua95vkaacrv6zo4lbo 2392362 2392352 2022-05-04T14:01:29Z Dave Braunschweig 426084 Cleanup 2392362 wikitext text/x-wiki The goal of this page is to list solutions to common issues. You are encouraged to add yours here. <!--In future, if this page gets too long, it could be split into sub pages.--> == 90-second delay while booting == Such a delay may be caused by an incorrect entry in the <code>/etc/fstab</code> file. This can especially be caused with [[:w:Live USB|live USB operating systems]] used across computers. Enter <code>blkid</code> into the command line terminal, then compare the output with the contents of aforementioned file. One of the entries, such as the entry for the swap file (which contains the word "swap"), may need to be removed or commented out by adding <code>#</code> at the beginning of the line.<ref>[https://forums.linuxmint.com/viewtopic.php?t=327483 ''Boot proces 90 seconds delay'' – LinuxMint Forums, August 2020]</ref> == sysrq == Some [[wikipedia:Magic_SysRq_key|system requests]] might be disabled out of the box due to the [[wikipedia:bitmask|bitmask]] value in the file <code>/proc/sys/kernel/sysrq</code> being set to a different value than 1, such as 176. A possible reason is to protect inexperienced users. To override this, use the command <code>echo 1 | sudo tee /proc/sys/kernel/sysrq</code>, where the number "1" is piped into "tee", and <code>sudo tee</code> writes the "1" into said system file using root privileges. Directly <code>sudo echo 1 >/proc/sys/kernel/sysrq</code> or <code>sudo printf 1 >/proc/sys/kernel/sysrq</code> does not work if the terminal is not running as root, since text redirection into the file is performed by the terminal, whereas with <code>sudo tee</code>, it is performed by the <code>tee</code> tool using root privileges. == Mixing desktop environments == Your preferred desktop environment might lack an essential feature such as the popular "Cinnamon" desktop environment lacking a multiple-row task bar.<ref>[https://forums.linuxmint.com/viewtopic.php?t=162727 ''Enable multiple rows in the daskbar'' – LinuxMint Forums, March 2014]</ref><ref>[https://forums.linuxmint.com/viewtopic.php?t=239297 Resize panel/taskbar for two rows? - Linux Mint Forums, February 2017]</ref> It is possible to mix parts of desktop environments, such as using the <code>mate-panel</code> while other parts like the task switcher of ''Cinnamon'' are still operational. The ''Cinnamon'' task bar can be set to hide automatically in the configuration, whereas the multiple-row ''Mate'' taskbar can be made to always display on screen. In order to start multiple panels automatically, add one of them to the list of programs to start automatically. Typically, it is found in the system control panel, though the location may vary across desktop environments. == Halting == If your computer halts ("freezes") frequently, the most common causes are tasks consuming high CPU or disk I/O usage. The former can be monitored with the command-line utilities including <code>top</code> (usually bundled), <code>htop</code> (more sophisticated but may require installation first), and the graphical <code>gnome-system-monitor</code>. Disk I/O usage can be monitored with the interactive command-line utility <code>iotop</code>, where the <code>-o</code> parameter hides inactive processes for a better overview. A high I/O usage may not only caused by reads and writes themselves, but can also be caused by latency. This is not of concern on flash storages, but it is on hard disk drives, since the magnetic head needs an additional fraction of a second to move to the physical location of requested data. == Halted window manager == If the cursor has become unresponsive, and you wish to get out of it without losing your session, try the following: * Go to a different ''[[:w:tty (Unix)|tty]]'', for example, press Ctrl+Alt+F2 to go to tty2. * Type the <code>w</code> command to list active sessions. Notice the content of the <code>FROM</code> column, possibly <code>:0</code>. * Type <code>[process name of desktop environment] --replace --display=:0 2>/dev/null &</code>. Process names for desktop environments include <code>cinnamon</code>, <code>mate-panel</code> or <code>wm-mate</code> ("window manager MATE"), <code>xfwm4</code> (for xfce), and <code>kwin_x11</code> or <code>plasmashell</code> for KDE.<ref>[https://www.reddit.com/r/kde/comments/a5d2ly/how_do_you_properly_restart_kwin_and_plasmashell/ ''How do you properly restart KWin and Plasmashell from the virtual console?'' – /r/KDE, December 2018]</ref> The <code>:0</code> part is from the "FROM" column in the prior command, the <code>2>/dev/null</code> part prevents diagnostic error messages from flooding the command line output, and the <code>&</code> character puts the process in background.<ref>[https://unix.stackexchange.com/questions/31818/what-to-do-when-a-linux-desktop-freezes ''What to do when a Linux desktop freezes?'' - Unix & Linux Stack Exchange]</ref> == Password fail delay == Linux installations may be shipped with a long password fail delay, meaning an artificial delay until the user is allowed to retry after entering a wrong password. While it is intended to prevent password cracking through brute-forcing, a delay that is too long, such as three seconds, could become annoying from repetition and interfere with workflow. The fail delay is not recommended to be deactivated completely, but can be shortened to something more sufferable like 0.3 seconds. The disadvantage that brute forcing would become faster could be compensated multiple times over by appending one or two characters to the password. However, even at a fail delay of 0.01 seconds, brute forcing would be severely handicapped. As such, a preset fail delay of three seconds appears to be [[:w:Security theater|security theater]]. ;Setting There are multiple system files where the password fail delay may be configurable. Make sure to create a backup copy of of any system file before modifying. The exact used system file may vary depending on operating system distribution and version, but the configuration is typically located at <code>/etc/pam.d/common-auth</code> or <code>/etc/pam.d/login</code>, and the delay value is specified in microseconds. For example, to set the password delay to the tenth of a second, set the pre-existing value in the "login" file, which is presumably 3000000 out of the box, to "100000", as shown here: <pre> # # The PAM configuration file for the Shadow `login' service # # Enforce a minimal delay in case of failure (in microseconds). # (Replaces the `FAIL_DELAY' setting from login.defs) # Note that other modules may require another minimal delay. (for example, # to disable any delay, you should add the nodelay option to pam_unix) auth optional pam_faildelay.so delay=100000 </pre> Alternatively, try adding the new line <code>auth optional pam_faildelay.so delay=100000</code> to the "common-auth" file at this position: <pre> # here are the per-package modules (the "Primary" block) auth optional pam_faildelay.so delay=100000 auth [success=1 default=ignore] pam_unix.so nullok_secure nodelay </pre> <ref>[https://unix.stackexchange.com/questions/2126/why-is-there-a-big-delay-after-entering-a-wrong-password security - Why is there a big delay after entering a wrong password? - Unix & Linux Stack Exchange]</ref> == References == <references /> o6oy6ls4dxczn1sjjjovrz0dvx9poh1 2392409 2392362 2022-05-04T21:37:51Z TheSharpShark 2942382 /* Black screen */ 2392409 wikitext text/x-wiki The goal of this page is to list solutions to common issues. You are encouraged to add yours here. <!--In future, if this page gets too long, it could be split into sub pages.--> == 90-second delay while booting == Such a delay may be caused by an incorrect entry in the <code>/etc/fstab</code> file. This can especially be caused with [[:w:Live USB|live USB operating systems]] used across computers. Enter <code>blkid</code> into the command line terminal, then compare the output with the contents of aforementioned file. One of the entries, such as the entry for the swap file (which contains the word "swap"), may need to be removed or commented out by adding <code>#</code> at the beginning of the line.<ref>[https://forums.linuxmint.com/viewtopic.php?t=327483 ''Boot proces 90 seconds delay'' – LinuxMint Forums, August 2020]</ref> == sysrq == Some [[wikipedia:Magic_SysRq_key|system requests]] might be disabled out of the box due to the [[wikipedia:bitmask|bitmask]] value in the file <code>/proc/sys/kernel/sysrq</code> being set to a different value than 1, such as 176. A possible reason is to protect inexperienced users. To override this, use the command <code>echo 1 | sudo tee /proc/sys/kernel/sysrq</code>, where the number "1" is piped into "tee", and <code>sudo tee</code> writes the "1" into said system file using root privileges. Directly <code>sudo echo 1 >/proc/sys/kernel/sysrq</code> or <code>sudo printf 1 >/proc/sys/kernel/sysrq</code> does not work if the terminal is not running as root, since text redirection into the file is performed by the terminal, whereas with <code>sudo tee</code>, it is performed by the <code>tee</code> tool using root privileges. == Mixing desktop environments == Your preferred desktop environment might lack an essential feature such as the popular "Cinnamon" desktop environment lacking a multiple-row task bar.<ref>[https://forums.linuxmint.com/viewtopic.php?t=162727 ''Enable multiple rows in the daskbar'' – LinuxMint Forums, March 2014]</ref><ref>[https://forums.linuxmint.com/viewtopic.php?t=239297 Resize panel/taskbar for two rows? - Linux Mint Forums, February 2017]</ref> It is possible to mix parts of desktop environments, such as using the <code>mate-panel</code> while other parts like the task switcher of ''Cinnamon'' are still operational. The ''Cinnamon'' task bar can be set to hide automatically in the configuration, whereas the multiple-row ''Mate'' taskbar can be made to always display on screen. In order to start multiple panels automatically, add one of them to the list of programs to start automatically. Typically, it is found in the system control panel, though the location may vary across desktop environments. == Halting == If your computer halts ("freezes") frequently, the most common causes are tasks consuming high CPU or disk I/O usage. The former can be monitored with the command-line utilities including <code>top</code> (usually bundled), <code>htop</code> (more sophisticated but may require installation first), and the graphical <code>gnome-system-monitor</code>. Disk I/O usage can be monitored with the interactive command-line utility <code>iotop</code>, where the <code>-o</code> parameter hides inactive processes for a better overview. A high I/O usage may not only caused by reads and writes themselves, but can also be caused by latency. This is not of concern on flash storages, but it is on hard disk drives, since the magnetic head needs an additional fraction of a second to move to the physical location of requested data. == Halted window manager == If the cursor has become unresponsive, and you wish to get out of it without losing your session, try the following: * Go to a different ''[[:w:tty (Unix)|tty]]'', for example, press Ctrl+Alt+F2 to go to tty2. * Type the <code>w</code> command to list active sessions. Notice the content of the <code>FROM</code> column, possibly <code>:0</code>. * Type <code>[process name of desktop environment] --replace --display=:0 2>/dev/null &</code>. Process names for desktop environments include <code>cinnamon</code>, <code>mate-panel</code> or <code>wm-mate</code> ("window manager MATE"), <code>xfwm4</code> (for xfce), and <code>kwin_x11</code> or <code>plasmashell</code> for KDE.<ref>[https://www.reddit.com/r/kde/comments/a5d2ly/how_do_you_properly_restart_kwin_and_plasmashell/ ''How do you properly restart KWin and Plasmashell from the virtual console?'' – /r/KDE, December 2018]</ref> The <code>:0</code> part is from the "FROM" column in the prior command, the <code>2>/dev/null</code> part prevents diagnostic error messages from flooding the command line output, and the <code>&</code> character puts the process in background.<ref>[https://unix.stackexchange.com/questions/31818/what-to-do-when-a-linux-desktop-freezes ''What to do when a Linux desktop freezes?'' - Unix & Linux Stack Exchange]</ref> == Password fail delay == Linux installations may be shipped with a long password fail delay, meaning an artificial delay until the user is allowed to retry after entering a wrong password. While it is intended to prevent password cracking through brute-forcing, a delay that is too long, such as three seconds, could become annoying from repetition and interfere with workflow. The fail delay is not recommended to be deactivated completely, but can be shortened to something more sufferable like 0.3 seconds. The disadvantage that brute forcing would become faster could be compensated multiple times over by appending one or two characters to the password. However, even at a fail delay of 0.01 seconds, brute forcing would be severely handicapped. As such, a preset fail delay of three seconds appears to be [[:w:Security theater|security theater]]. ;Setting There are multiple system files where the password fail delay may be configurable. Make sure to create a backup copy of of any system file before modifying. The exact used system file may vary depending on operating system distribution and version, but the configuration is typically located at <code>/etc/pam.d/common-auth</code> or <code>/etc/pam.d/login</code>, and the delay value is specified in microseconds. For example, to set the password delay to the tenth of a second, set the pre-existing value in the "login" file, which is presumably 3000000 out of the box, to "100000", as shown here: <pre> # # The PAM configuration file for the Shadow `login' service # # Enforce a minimal delay in case of failure (in microseconds). # (Replaces the `FAIL_DELAY' setting from login.defs) # Note that other modules may require another minimal delay. (for example, # to disable any delay, you should add the nodelay option to pam_unix) auth optional pam_faildelay.so delay=100000 </pre> Alternatively, try adding the new line <code>auth optional pam_faildelay.so delay=100000</code> to the "common-auth" file at this position: <pre> # here are the per-package modules (the "Primary" block) auth optional pam_faildelay.so delay=100000 auth [success=1 default=ignore] pam_unix.so nullok_secure nodelay </pre> <ref>[https://unix.stackexchange.com/questions/2126/why-is-there-a-big-delay-after-entering-a-wrong-password security - Why is there a big delay after entering a wrong password? - Unix & Linux Stack Exchange]</ref> == Black screen == On some proprietary graphics drivers, a black screen may occur under when switching away from the graphical user interface (usually tty7) to any other tty (Ctrl+Alt+F[number]) while screen resolution is not set to maximum does result in a black screen with only backlight visible, meaning the screen is still on but nothing is visible. This may also happen after waking up from suspending after a countdown, e.g. <code>sleep 1h; systemctl suspend</code>.<ref>https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-440/+bug/1870758</ref> Adjust the screen resolution blindly by entering <code>xrandr -s 1920x1080</code> or another valid resolution in a terminal running inside X server. Note that for it to work, it has to be a different resolution than the current one. Consider adding screenrescue() { xrandr -s 640x480; xrandr -s 1920x1080; redshift -O 2400; } to ~/.bashrc, to make a more memorable command named "screenrescue" do it. == References == <references /> 2m8zuo0hzpi1cuyd9z58akbn4uvakbb 2392410 2392409 2022-05-04T22:44:10Z TheSharpShark 2942382 /* Black screen */ code tags 2392410 wikitext text/x-wiki The goal of this page is to list solutions to common issues. You are encouraged to add yours here. <!--In future, if this page gets too long, it could be split into sub pages.--> == 90-second delay while booting == Such a delay may be caused by an incorrect entry in the <code>/etc/fstab</code> file. This can especially be caused with [[:w:Live USB|live USB operating systems]] used across computers. Enter <code>blkid</code> into the command line terminal, then compare the output with the contents of aforementioned file. One of the entries, such as the entry for the swap file (which contains the word "swap"), may need to be removed or commented out by adding <code>#</code> at the beginning of the line.<ref>[https://forums.linuxmint.com/viewtopic.php?t=327483 ''Boot proces 90 seconds delay'' – LinuxMint Forums, August 2020]</ref> == sysrq == Some [[wikipedia:Magic_SysRq_key|system requests]] might be disabled out of the box due to the [[wikipedia:bitmask|bitmask]] value in the file <code>/proc/sys/kernel/sysrq</code> being set to a different value than 1, such as 176. A possible reason is to protect inexperienced users. To override this, use the command <code>echo 1 | sudo tee /proc/sys/kernel/sysrq</code>, where the number "1" is piped into "tee", and <code>sudo tee</code> writes the "1" into said system file using root privileges. Directly <code>sudo echo 1 >/proc/sys/kernel/sysrq</code> or <code>sudo printf 1 >/proc/sys/kernel/sysrq</code> does not work if the terminal is not running as root, since text redirection into the file is performed by the terminal, whereas with <code>sudo tee</code>, it is performed by the <code>tee</code> tool using root privileges. == Mixing desktop environments == Your preferred desktop environment might lack an essential feature such as the popular "Cinnamon" desktop environment lacking a multiple-row task bar.<ref>[https://forums.linuxmint.com/viewtopic.php?t=162727 ''Enable multiple rows in the daskbar'' – LinuxMint Forums, March 2014]</ref><ref>[https://forums.linuxmint.com/viewtopic.php?t=239297 Resize panel/taskbar for two rows? - Linux Mint Forums, February 2017]</ref> It is possible to mix parts of desktop environments, such as using the <code>mate-panel</code> while other parts like the task switcher of ''Cinnamon'' are still operational. The ''Cinnamon'' task bar can be set to hide automatically in the configuration, whereas the multiple-row ''Mate'' taskbar can be made to always display on screen. In order to start multiple panels automatically, add one of them to the list of programs to start automatically. Typically, it is found in the system control panel, though the location may vary across desktop environments. == Halting == If your computer halts ("freezes") frequently, the most common causes are tasks consuming high CPU or disk I/O usage. The former can be monitored with the command-line utilities including <code>top</code> (usually bundled), <code>htop</code> (more sophisticated but may require installation first), and the graphical <code>gnome-system-monitor</code>. Disk I/O usage can be monitored with the interactive command-line utility <code>iotop</code>, where the <code>-o</code> parameter hides inactive processes for a better overview. A high I/O usage may not only caused by reads and writes themselves, but can also be caused by latency. This is not of concern on flash storages, but it is on hard disk drives, since the magnetic head needs an additional fraction of a second to move to the physical location of requested data. == Halted window manager == If the cursor has become unresponsive, and you wish to get out of it without losing your session, try the following: * Go to a different ''[[:w:tty (Unix)|tty]]'', for example, press Ctrl+Alt+F2 to go to tty2. * Type the <code>w</code> command to list active sessions. Notice the content of the <code>FROM</code> column, possibly <code>:0</code>. * Type <code>[process name of desktop environment] --replace --display=:0 2>/dev/null &</code>. Process names for desktop environments include <code>cinnamon</code>, <code>mate-panel</code> or <code>wm-mate</code> ("window manager MATE"), <code>xfwm4</code> (for xfce), and <code>kwin_x11</code> or <code>plasmashell</code> for KDE.<ref>[https://www.reddit.com/r/kde/comments/a5d2ly/how_do_you_properly_restart_kwin_and_plasmashell/ ''How do you properly restart KWin and Plasmashell from the virtual console?'' – /r/KDE, December 2018]</ref> The <code>:0</code> part is from the "FROM" column in the prior command, the <code>2>/dev/null</code> part prevents diagnostic error messages from flooding the command line output, and the <code>&</code> character puts the process in background.<ref>[https://unix.stackexchange.com/questions/31818/what-to-do-when-a-linux-desktop-freezes ''What to do when a Linux desktop freezes?'' - Unix & Linux Stack Exchange]</ref> == Password fail delay == Linux installations may be shipped with a long password fail delay, meaning an artificial delay until the user is allowed to retry after entering a wrong password. While it is intended to prevent password cracking through brute-forcing, a delay that is too long, such as three seconds, could become annoying from repetition and interfere with workflow. The fail delay is not recommended to be deactivated completely, but can be shortened to something more sufferable like 0.3 seconds. The disadvantage that brute forcing would become faster could be compensated multiple times over by appending one or two characters to the password. However, even at a fail delay of 0.01 seconds, brute forcing would be severely handicapped. As such, a preset fail delay of three seconds appears to be [[:w:Security theater|security theater]]. ;Setting There are multiple system files where the password fail delay may be configurable. Make sure to create a backup copy of of any system file before modifying. The exact used system file may vary depending on operating system distribution and version, but the configuration is typically located at <code>/etc/pam.d/common-auth</code> or <code>/etc/pam.d/login</code>, and the delay value is specified in microseconds. For example, to set the password delay to the tenth of a second, set the pre-existing value in the "login" file, which is presumably 3000000 out of the box, to "100000", as shown here: <pre> # # The PAM configuration file for the Shadow `login' service # # Enforce a minimal delay in case of failure (in microseconds). # (Replaces the `FAIL_DELAY' setting from login.defs) # Note that other modules may require another minimal delay. (for example, # to disable any delay, you should add the nodelay option to pam_unix) auth optional pam_faildelay.so delay=100000 </pre> Alternatively, try adding the new line <code>auth optional pam_faildelay.so delay=100000</code> to the "common-auth" file at this position: <pre> # here are the per-package modules (the "Primary" block) auth optional pam_faildelay.so delay=100000 auth [success=1 default=ignore] pam_unix.so nullok_secure nodelay </pre> <ref>[https://unix.stackexchange.com/questions/2126/why-is-there-a-big-delay-after-entering-a-wrong-password security - Why is there a big delay after entering a wrong password? - Unix & Linux Stack Exchange]</ref> == Black screen == On some proprietary graphics drivers, a black screen may occur under when switching away from the graphical user interface (usually tty7) to any other tty (Ctrl+Alt+F[number]) while screen resolution is not set to maximum does result in a black screen with only backlight visible, meaning the screen is still on but nothing is visible. This may also happen after waking up from suspending after a countdown, e.g. <code>sleep 1h; systemctl suspend</code>.<ref>https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-440/+bug/1870758</ref> Adjust the screen resolution blindly by entering <code>xrandr -s 1920x1080</code> or another valid resolution in a terminal running inside X server. Note that for it to work, it has to be a different resolution than the current one. Consider adding <code>screenrescue() { xrandr -s 640x480; xrandr -s 1920x1080; redshift -O 2400; }</code> to <code>~/.bashrc</code>, to make a more memorable command named "screenrescue" do it. == References == <references /> 62c9jbksat50fcu88kfit648e4nkrnp 2456096 2392410 2022-12-03T11:43:19Z MathXplore 2888076 added [[Category:Linux]] using [[Help:Gadget-HotCat|HotCat]] 2456096 wikitext text/x-wiki The goal of this page is to list solutions to common issues. You are encouraged to add yours here. <!--In future, if this page gets too long, it could be split into sub pages.--> == 90-second delay while booting == Such a delay may be caused by an incorrect entry in the <code>/etc/fstab</code> file. This can especially be caused with [[:w:Live USB|live USB operating systems]] used across computers. Enter <code>blkid</code> into the command line terminal, then compare the output with the contents of aforementioned file. One of the entries, such as the entry for the swap file (which contains the word "swap"), may need to be removed or commented out by adding <code>#</code> at the beginning of the line.<ref>[https://forums.linuxmint.com/viewtopic.php?t=327483 ''Boot proces 90 seconds delay'' – LinuxMint Forums, August 2020]</ref> == sysrq == Some [[wikipedia:Magic_SysRq_key|system requests]] might be disabled out of the box due to the [[wikipedia:bitmask|bitmask]] value in the file <code>/proc/sys/kernel/sysrq</code> being set to a different value than 1, such as 176. A possible reason is to protect inexperienced users. To override this, use the command <code>echo 1 | sudo tee /proc/sys/kernel/sysrq</code>, where the number "1" is piped into "tee", and <code>sudo tee</code> writes the "1" into said system file using root privileges. Directly <code>sudo echo 1 >/proc/sys/kernel/sysrq</code> or <code>sudo printf 1 >/proc/sys/kernel/sysrq</code> does not work if the terminal is not running as root, since text redirection into the file is performed by the terminal, whereas with <code>sudo tee</code>, it is performed by the <code>tee</code> tool using root privileges. == Mixing desktop environments == Your preferred desktop environment might lack an essential feature such as the popular "Cinnamon" desktop environment lacking a multiple-row task bar.<ref>[https://forums.linuxmint.com/viewtopic.php?t=162727 ''Enable multiple rows in the daskbar'' – LinuxMint Forums, March 2014]</ref><ref>[https://forums.linuxmint.com/viewtopic.php?t=239297 Resize panel/taskbar for two rows? - Linux Mint Forums, February 2017]</ref> It is possible to mix parts of desktop environments, such as using the <code>mate-panel</code> while other parts like the task switcher of ''Cinnamon'' are still operational. The ''Cinnamon'' task bar can be set to hide automatically in the configuration, whereas the multiple-row ''Mate'' taskbar can be made to always display on screen. In order to start multiple panels automatically, add one of them to the list of programs to start automatically. Typically, it is found in the system control panel, though the location may vary across desktop environments. == Halting == If your computer halts ("freezes") frequently, the most common causes are tasks consuming high CPU or disk I/O usage. The former can be monitored with the command-line utilities including <code>top</code> (usually bundled), <code>htop</code> (more sophisticated but may require installation first), and the graphical <code>gnome-system-monitor</code>. Disk I/O usage can be monitored with the interactive command-line utility <code>iotop</code>, where the <code>-o</code> parameter hides inactive processes for a better overview. A high I/O usage may not only caused by reads and writes themselves, but can also be caused by latency. This is not of concern on flash storages, but it is on hard disk drives, since the magnetic head needs an additional fraction of a second to move to the physical location of requested data. == Halted window manager == If the cursor has become unresponsive, and you wish to get out of it without losing your session, try the following: * Go to a different ''[[:w:tty (Unix)|tty]]'', for example, press Ctrl+Alt+F2 to go to tty2. * Type the <code>w</code> command to list active sessions. Notice the content of the <code>FROM</code> column, possibly <code>:0</code>. * Type <code>[process name of desktop environment] --replace --display=:0 2>/dev/null &</code>. Process names for desktop environments include <code>cinnamon</code>, <code>mate-panel</code> or <code>wm-mate</code> ("window manager MATE"), <code>xfwm4</code> (for xfce), and <code>kwin_x11</code> or <code>plasmashell</code> for KDE.<ref>[https://www.reddit.com/r/kde/comments/a5d2ly/how_do_you_properly_restart_kwin_and_plasmashell/ ''How do you properly restart KWin and Plasmashell from the virtual console?'' – /r/KDE, December 2018]</ref> The <code>:0</code> part is from the "FROM" column in the prior command, the <code>2>/dev/null</code> part prevents diagnostic error messages from flooding the command line output, and the <code>&</code> character puts the process in background.<ref>[https://unix.stackexchange.com/questions/31818/what-to-do-when-a-linux-desktop-freezes ''What to do when a Linux desktop freezes?'' - Unix & Linux Stack Exchange]</ref> == Password fail delay == Linux installations may be shipped with a long password fail delay, meaning an artificial delay until the user is allowed to retry after entering a wrong password. While it is intended to prevent password cracking through brute-forcing, a delay that is too long, such as three seconds, could become annoying from repetition and interfere with workflow. The fail delay is not recommended to be deactivated completely, but can be shortened to something more sufferable like 0.3 seconds. The disadvantage that brute forcing would become faster could be compensated multiple times over by appending one or two characters to the password. However, even at a fail delay of 0.01 seconds, brute forcing would be severely handicapped. As such, a preset fail delay of three seconds appears to be [[:w:Security theater|security theater]]. ;Setting There are multiple system files where the password fail delay may be configurable. Make sure to create a backup copy of of any system file before modifying. The exact used system file may vary depending on operating system distribution and version, but the configuration is typically located at <code>/etc/pam.d/common-auth</code> or <code>/etc/pam.d/login</code>, and the delay value is specified in microseconds. For example, to set the password delay to the tenth of a second, set the pre-existing value in the "login" file, which is presumably 3000000 out of the box, to "100000", as shown here: <pre> # # The PAM configuration file for the Shadow `login' service # # Enforce a minimal delay in case of failure (in microseconds). # (Replaces the `FAIL_DELAY' setting from login.defs) # Note that other modules may require another minimal delay. (for example, # to disable any delay, you should add the nodelay option to pam_unix) auth optional pam_faildelay.so delay=100000 </pre> Alternatively, try adding the new line <code>auth optional pam_faildelay.so delay=100000</code> to the "common-auth" file at this position: <pre> # here are the per-package modules (the "Primary" block) auth optional pam_faildelay.so delay=100000 auth [success=1 default=ignore] pam_unix.so nullok_secure nodelay </pre> <ref>[https://unix.stackexchange.com/questions/2126/why-is-there-a-big-delay-after-entering-a-wrong-password security - Why is there a big delay after entering a wrong password? - Unix & Linux Stack Exchange]</ref> == Black screen == On some proprietary graphics drivers, a black screen may occur under when switching away from the graphical user interface (usually tty7) to any other tty (Ctrl+Alt+F[number]) while screen resolution is not set to maximum does result in a black screen with only backlight visible, meaning the screen is still on but nothing is visible. This may also happen after waking up from suspending after a countdown, e.g. <code>sleep 1h; systemctl suspend</code>.<ref>https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-440/+bug/1870758</ref> Adjust the screen resolution blindly by entering <code>xrandr -s 1920x1080</code> or another valid resolution in a terminal running inside X server. Note that for it to work, it has to be a different resolution than the current one. Consider adding <code>screenrescue() { xrandr -s 640x480; xrandr -s 1920x1080; redshift -O 2400; }</code> to <code>~/.bashrc</code>, to make a more memorable command named "screenrescue" do it. == References == <references /> [[Category:Linux]] 86f8vqvu2ucrebm1225uu90t53t0ecr 2694347 2456096 2025-01-04T20:34:22Z Elominius 2911372 "/etc/fstab" might prevent booting. 2694347 wikitext text/x-wiki The goal of this page is to list solutions to common issues. You are encouraged to add yours here. <!--In future, if this page gets too long, it could be split into sub pages.--> == Unable to boot == A possible cause of boot failure are entries to non-existent devices or image files in <code>/etc/fstab</code>. Type in <code>/bin/nano /etc/fstab</code> in the emergency shell to edit the <code>fstab</code> file, then either comment (add <code>#</code> at the beginning of the line) or remove lines that contain entries to non-existent devices or image files. == 90-second delay while booting == Such a delay may be caused by an incorrect entry in the <code>/etc/fstab</code> file. This can especially be caused with [[:w:Live USB|live USB operating systems]] used across computers. Enter <code>blkid</code> into the command line terminal, then compare the output with the contents of aforementioned file. One of the entries, such as the entry for the swap file (which contains the word "swap"), may need to be removed or commented out by adding <code>#</code> at the beginning of the line.<ref>[https://forums.linuxmint.com/viewtopic.php?t=327483 ''Boot proces 90 seconds delay'' – LinuxMint Forums, August 2020]</ref> == sysrq == Some [[wikipedia:Magic_SysRq_key|system requests]] might be disabled out of the box due to the [[wikipedia:bitmask|bitmask]] value in the file <code>/proc/sys/kernel/sysrq</code> being set to a different value than 1, such as 176. A possible reason is to protect inexperienced users. To override this, use the command <code>echo 1 | sudo tee /proc/sys/kernel/sysrq</code>, where the number "1" is piped into "tee", and <code>sudo tee</code> writes the "1" into said system file using root privileges. Directly <code>sudo echo 1 >/proc/sys/kernel/sysrq</code> or <code>sudo printf 1 >/proc/sys/kernel/sysrq</code> does not work if the terminal is not running as root, since text redirection into the file is performed by the terminal, whereas with <code>sudo tee</code>, it is performed by the <code>tee</code> tool using root privileges. == Mixing desktop environments == Your preferred desktop environment might lack an essential feature such as the popular "Cinnamon" desktop environment lacking a multiple-row task bar.<ref>[https://forums.linuxmint.com/viewtopic.php?t=162727 ''Enable multiple rows in the daskbar'' – LinuxMint Forums, March 2014]</ref><ref>[https://forums.linuxmint.com/viewtopic.php?t=239297 Resize panel/taskbar for two rows? - Linux Mint Forums, February 2017]</ref> It is possible to mix parts of desktop environments, such as using the <code>mate-panel</code> while other parts like the task switcher of ''Cinnamon'' are still operational. The ''Cinnamon'' task bar can be set to hide automatically in the configuration, whereas the multiple-row ''Mate'' taskbar can be made to always display on screen. In order to start multiple panels automatically, add one of them to the list of programs to start automatically. Typically, it is found in the system control panel, though the location may vary across desktop environments. == Halting == If your computer halts ("freezes") frequently, the most common causes are tasks consuming high CPU or disk I/O usage. The former can be monitored with the command-line utilities including <code>top</code> (usually bundled), <code>htop</code> (more sophisticated but may require installation first), and the graphical <code>gnome-system-monitor</code>. Disk I/O usage can be monitored with the interactive command-line utility <code>iotop</code>, where the <code>-o</code> parameter hides inactive processes for a better overview. A high I/O usage may not only caused by reads and writes themselves, but can also be caused by latency. This is not of concern on flash storages, but it is on hard disk drives, since the magnetic head needs an additional fraction of a second to move to the physical location of requested data. == Halted window manager == If the cursor has become unresponsive, and you wish to get out of it without losing your session, try the following: * Go to a different ''[[:w:tty (Unix)|tty]]'', for example, press Ctrl+Alt+F2 to go to tty2. * Type the <code>w</code> command to list active sessions. Notice the content of the <code>FROM</code> column, possibly <code>:0</code>. * Type <code>[process name of desktop environment] --replace --display=:0 2>/dev/null &</code>. Process names for desktop environments include <code>cinnamon</code>, <code>mate-panel</code> or <code>wm-mate</code> ("window manager MATE"), <code>xfwm4</code> (for xfce), and <code>kwin_x11</code> or <code>plasmashell</code> for KDE.<ref>[https://www.reddit.com/r/kde/comments/a5d2ly/how_do_you_properly_restart_kwin_and_plasmashell/ ''How do you properly restart KWin and Plasmashell from the virtual console?'' – /r/KDE, December 2018]</ref> The <code>:0</code> part is from the "FROM" column in the prior command, the <code>2>/dev/null</code> part prevents diagnostic error messages from flooding the command line output, and the <code>&</code> character puts the process in background.<ref>[https://unix.stackexchange.com/questions/31818/what-to-do-when-a-linux-desktop-freezes ''What to do when a Linux desktop freezes?'' - Unix & Linux Stack Exchange]</ref> == Password fail delay == Linux installations may be shipped with a long password fail delay, meaning an artificial delay until the user is allowed to retry after entering a wrong password. While it is intended to prevent password cracking through brute-forcing, a delay that is too long, such as three seconds, could become annoying from repetition and interfere with workflow. The fail delay is not recommended to be deactivated completely, but can be shortened to something more sufferable like 0.3 seconds. The disadvantage that brute forcing would become faster could be compensated multiple times over by appending one or two characters to the password. However, even at a fail delay of 0.01 seconds, brute forcing would be severely handicapped. As such, a preset fail delay of three seconds appears to be [[:w:Security theater|security theater]]. ;Setting There are multiple system files where the password fail delay may be configurable. Make sure to create a backup copy of of any system file before modifying. The exact used system file may vary depending on operating system distribution and version, but the configuration is typically located at <code>/etc/pam.d/common-auth</code> or <code>/etc/pam.d/login</code>, and the delay value is specified in microseconds. For example, to set the password delay to the tenth of a second, set the pre-existing value in the "login" file, which is presumably 3000000 out of the box, to "100000", as shown here: <pre> # # The PAM configuration file for the Shadow `login' service # # Enforce a minimal delay in case of failure (in microseconds). # (Replaces the `FAIL_DELAY' setting from login.defs) # Note that other modules may require another minimal delay. (for example, # to disable any delay, you should add the nodelay option to pam_unix) auth optional pam_faildelay.so delay=100000 </pre> Alternatively, try adding the new line <code>auth optional pam_faildelay.so delay=100000</code> to the "common-auth" file at this position: <pre> # here are the per-package modules (the "Primary" block) auth optional pam_faildelay.so delay=100000 auth [success=1 default=ignore] pam_unix.so nullok_secure nodelay </pre> <ref>[https://unix.stackexchange.com/questions/2126/why-is-there-a-big-delay-after-entering-a-wrong-password security - Why is there a big delay after entering a wrong password? - Unix & Linux Stack Exchange]</ref> == Black screen == On some proprietary graphics drivers, a black screen may occur under when switching away from the graphical user interface (usually tty7) to any other tty (Ctrl+Alt+F[number]) while screen resolution is not set to maximum does result in a black screen with only backlight visible, meaning the screen is still on but nothing is visible. This may also happen after waking up from suspending after a countdown, e.g. <code>sleep 1h; systemctl suspend</code>.<ref>https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-440/+bug/1870758</ref> Adjust the screen resolution blindly by entering <code>xrandr -s 1920x1080</code> or another valid resolution in a terminal running inside X server. Note that for it to work, it has to be a different resolution than the current one. Consider adding <code>screenrescue() { xrandr -s 640x480; xrandr -s 1920x1080; redshift -O 2400; }</code> to <code>~/.bashrc</code>, to make a more memorable command named "screenrescue" do it. == References == <references /> [[Category:Linux]] 1nxl32s02ypk44opmglshnmspi0zu9c 2694348 2694347 2025-01-04T20:42:27Z Elominius 2911372 /* Unable to boot */ external editing 2694348 wikitext text/x-wiki The goal of this page is to list solutions to common issues. You are encouraged to add yours here. <!--In future, if this page gets too long, it could be split into sub pages.--> == Unable to boot == A possible cause of boot failure are entries to non-existent devices or image files in <code>/etc/fstab</code>. Type in <code>/bin/nano /etc/fstab</code> in the emergency shell to edit the <code>fstab</code> file, then either comment (add <code>#</code> at the beginning of the line) or remove lines that contain entries to non-existent devices or image files. You can also edit the <code>fstab</code> file from an external Linux installation (on a flash drive, an SSD, or a boot disc). == 90-second delay while booting == Such a delay may be caused by an incorrect entry in the <code>/etc/fstab</code> file. This can especially be caused with [[:w:Live USB|live USB operating systems]] used across computers. Enter <code>blkid</code> into the command line terminal, then compare the output with the contents of aforementioned file. One of the entries, such as the entry for the swap file (which contains the word "swap"), may need to be removed or commented out by adding <code>#</code> at the beginning of the line.<ref>[https://forums.linuxmint.com/viewtopic.php?t=327483 ''Boot proces 90 seconds delay'' – LinuxMint Forums, August 2020]</ref> == sysrq == Some [[wikipedia:Magic_SysRq_key|system requests]] might be disabled out of the box due to the [[wikipedia:bitmask|bitmask]] value in the file <code>/proc/sys/kernel/sysrq</code> being set to a different value than 1, such as 176. A possible reason is to protect inexperienced users. To override this, use the command <code>echo 1 | sudo tee /proc/sys/kernel/sysrq</code>, where the number "1" is piped into "tee", and <code>sudo tee</code> writes the "1" into said system file using root privileges. Directly <code>sudo echo 1 >/proc/sys/kernel/sysrq</code> or <code>sudo printf 1 >/proc/sys/kernel/sysrq</code> does not work if the terminal is not running as root, since text redirection into the file is performed by the terminal, whereas with <code>sudo tee</code>, it is performed by the <code>tee</code> tool using root privileges. == Mixing desktop environments == Your preferred desktop environment might lack an essential feature such as the popular "Cinnamon" desktop environment lacking a multiple-row task bar.<ref>[https://forums.linuxmint.com/viewtopic.php?t=162727 ''Enable multiple rows in the daskbar'' – LinuxMint Forums, March 2014]</ref><ref>[https://forums.linuxmint.com/viewtopic.php?t=239297 Resize panel/taskbar for two rows? - Linux Mint Forums, February 2017]</ref> It is possible to mix parts of desktop environments, such as using the <code>mate-panel</code> while other parts like the task switcher of ''Cinnamon'' are still operational. The ''Cinnamon'' task bar can be set to hide automatically in the configuration, whereas the multiple-row ''Mate'' taskbar can be made to always display on screen. In order to start multiple panels automatically, add one of them to the list of programs to start automatically. Typically, it is found in the system control panel, though the location may vary across desktop environments. == Halting == If your computer halts ("freezes") frequently, the most common causes are tasks consuming high CPU or disk I/O usage. The former can be monitored with the command-line utilities including <code>top</code> (usually bundled), <code>htop</code> (more sophisticated but may require installation first), and the graphical <code>gnome-system-monitor</code>. Disk I/O usage can be monitored with the interactive command-line utility <code>iotop</code>, where the <code>-o</code> parameter hides inactive processes for a better overview. A high I/O usage may not only caused by reads and writes themselves, but can also be caused by latency. This is not of concern on flash storages, but it is on hard disk drives, since the magnetic head needs an additional fraction of a second to move to the physical location of requested data. == Halted window manager == If the cursor has become unresponsive, and you wish to get out of it without losing your session, try the following: * Go to a different ''[[:w:tty (Unix)|tty]]'', for example, press Ctrl+Alt+F2 to go to tty2. * Type the <code>w</code> command to list active sessions. Notice the content of the <code>FROM</code> column, possibly <code>:0</code>. * Type <code>[process name of desktop environment] --replace --display=:0 2>/dev/null &</code>. Process names for desktop environments include <code>cinnamon</code>, <code>mate-panel</code> or <code>wm-mate</code> ("window manager MATE"), <code>xfwm4</code> (for xfce), and <code>kwin_x11</code> or <code>plasmashell</code> for KDE.<ref>[https://www.reddit.com/r/kde/comments/a5d2ly/how_do_you_properly_restart_kwin_and_plasmashell/ ''How do you properly restart KWin and Plasmashell from the virtual console?'' – /r/KDE, December 2018]</ref> The <code>:0</code> part is from the "FROM" column in the prior command, the <code>2>/dev/null</code> part prevents diagnostic error messages from flooding the command line output, and the <code>&</code> character puts the process in background.<ref>[https://unix.stackexchange.com/questions/31818/what-to-do-when-a-linux-desktop-freezes ''What to do when a Linux desktop freezes?'' - Unix & Linux Stack Exchange]</ref> == Password fail delay == Linux installations may be shipped with a long password fail delay, meaning an artificial delay until the user is allowed to retry after entering a wrong password. While it is intended to prevent password cracking through brute-forcing, a delay that is too long, such as three seconds, could become annoying from repetition and interfere with workflow. The fail delay is not recommended to be deactivated completely, but can be shortened to something more sufferable like 0.3 seconds. The disadvantage that brute forcing would become faster could be compensated multiple times over by appending one or two characters to the password. However, even at a fail delay of 0.01 seconds, brute forcing would be severely handicapped. As such, a preset fail delay of three seconds appears to be [[:w:Security theater|security theater]]. ;Setting There are multiple system files where the password fail delay may be configurable. Make sure to create a backup copy of of any system file before modifying. The exact used system file may vary depending on operating system distribution and version, but the configuration is typically located at <code>/etc/pam.d/common-auth</code> or <code>/etc/pam.d/login</code>, and the delay value is specified in microseconds. For example, to set the password delay to the tenth of a second, set the pre-existing value in the "login" file, which is presumably 3000000 out of the box, to "100000", as shown here: <pre> # # The PAM configuration file for the Shadow `login' service # # Enforce a minimal delay in case of failure (in microseconds). # (Replaces the `FAIL_DELAY' setting from login.defs) # Note that other modules may require another minimal delay. (for example, # to disable any delay, you should add the nodelay option to pam_unix) auth optional pam_faildelay.so delay=100000 </pre> Alternatively, try adding the new line <code>auth optional pam_faildelay.so delay=100000</code> to the "common-auth" file at this position: <pre> # here are the per-package modules (the "Primary" block) auth optional pam_faildelay.so delay=100000 auth [success=1 default=ignore] pam_unix.so nullok_secure nodelay </pre> <ref>[https://unix.stackexchange.com/questions/2126/why-is-there-a-big-delay-after-entering-a-wrong-password security - Why is there a big delay after entering a wrong password? - Unix & Linux Stack Exchange]</ref> == Black screen == On some proprietary graphics drivers, a black screen may occur under when switching away from the graphical user interface (usually tty7) to any other tty (Ctrl+Alt+F[number]) while screen resolution is not set to maximum does result in a black screen with only backlight visible, meaning the screen is still on but nothing is visible. This may also happen after waking up from suspending after a countdown, e.g. <code>sleep 1h; systemctl suspend</code>.<ref>https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-440/+bug/1870758</ref> Adjust the screen resolution blindly by entering <code>xrandr -s 1920x1080</code> or another valid resolution in a terminal running inside X server. Note that for it to work, it has to be a different resolution than the current one. Consider adding <code>screenrescue() { xrandr -s 640x480; xrandr -s 1920x1080; redshift -O 2400; }</code> to <code>~/.bashrc</code>, to make a more memorable command named "screenrescue" do it. == References == <references /> [[Category:Linux]] 1is39kmgrd88lvn51nwnern1p8jvezs