I mean this thing:
This is not the scrollbar (which is on the other side of the window). It seems to show the output of the last command run, but if I scroll back it seems to show "random" lines. The best explanation to its behavior is that it groups outputs that have been produced within a short time of each other but this only applies to the last command.
This appeared when I upgraded to Kubuntu 22.04 (so running Konsole 21.12.3 now).
Any hints?
As the title says. My usual set up is a laptop (Kubuntu 20.04) connected to a fairly recent external display.
I found how to add a script in the notification to turnoff the external display when I lock the screen, but I cannot find an equivalent option or notification when the screen is dimmed or turned off by the power saving behavior. Is there such a thing?
I'll running Kubuntu 20.04 on a laptop using both the laptop screen and a rather recent external monitor (Iiyama PL2796QS) connected with HDMI.
I would like to have the external monitor turned off when I close the lid of the laptop. I have searched the power management options but the external monitor isn't considered.
I have seen this question but this is for a Gnome desktop. My own dconf has very little to show...
Any ideas?
I'm trying to see how much delay is induced by my bluetooth headphones.
So I'm looking for a way to have a short sound generated when I click a button/hit a key. The standard sound test isn't really usable for this, it is too long and not "sharp" enough at the start.
Any suggestions? Or other solutions?
Running (K)ubuntu 20.04, if that makes a difference.
I have a Digital Ocean droplet running Ubuntu Server 16.04. I tried to run a do-release-upgrade (after the mandatory apt update and apt upgrade) but it stops fairly quickly:
Reading cache
Checking package manager
Reading package lists... Done
Building dependency tree
Reading state information... Done
Hit http://ppa.launchpad.net/certbot/certbot/ubuntu xenial InRelease
Hit http://mirrors.digitalocean.com/ubuntu xenial InRelease
Get:1 https://esm.ubuntu.com/infra/ubuntu xenial-infra-security InRelease [7476 B]
Get:2 https://esm.ubuntu.com/infra/ubuntu xenial-infra-updates InRelease [7475 B]
Get:3 http://mirrors.digitalocean.com/ubuntu xenial-updates InRelease [109 kB]
Get:4 http://mirrors.digitalocean.com/ubuntu xenial-backports InRelease [107 kB]
Get:5 http://mirrors.digitalocean.com/ubuntu xenial-security InRelease [109 kB]
Get:6 http://mirrors.digitalocean.com/ubuntu xenial-updates/main amd64 Packages [2048 kB]
Get:7 http://mirrors.digitalocean.com/ubuntu xenial-updates/main i386 Packages [1524 kB]
Get:8 http://mirrors.digitalocean.com/ubuntu xenial-updates/universe amd64 Packages [1220 kB]
Get:9 http://mirrors.digitalocean.com/ubuntu xenial-updates/universe i386 Packages [1086 kB]
Fetched 6218 kB in 0s (0 B/s)
Reading package lists... Done
Building dependency tree
Reading state information... Done
No snaps are installed yet. Try 'snap install hello-world'.
Checking for installed snaps
Calculating snap size requirements
Updating repository information
Third party sources disabled
Some third party entries in your sources.list were disabled. You can
re-enable them after the upgrade with the 'software-properties' tool
or your package manager.
To continue please press [ENTER]
Get:1 https://esm.ubuntu.com/infra/ubuntu bionic-infra-security InRelease [7458 B]
Get:2 https://esm.ubuntu.com/infra/ubuntu bionic-infra-updates InRelease [7457 B]
Fetched 14.9 kB in 0s (0 B/s)
Checking package manager
Reading package lists... Done
Building dependency tree
Reading state information... Done
Invalid package information
After updating your package information, the essential package
'ubuntu-minimal' could not be located. This may be because you have
no official mirrors listed in your software sources, or because of
excessive load on the mirror you are using. See /etc/apt/sources.list
for the current list of configured software sources.
In the case of an overloaded mirror, you may want to try the upgrade
again later.
Is this because the software sources are no longer correct (if so what would be the correct ones)? The official DO mantra is to install a fresh version on another droplet and then switch droplets but I want to avoid this.
Edit: The standard /etc/apt/source.lst on DO points only to DO's mirrors. Peeking at it (before do-release-upgrade restores it due to failure), it appears that all entries are commented out (considered as 3rd party sources?). So where can I find a sources.lst that points to the Canonical repos?
Bonus points for a method to move to 20.04 without the 18.04 step...
PS: the do-release-upgrade on my other droplet running 18.04 worked flawlessly.
I'm using markdown from the repos on Ubuntu 19.10. This seems to be a quite old version:
>markdown -v
This is Markdown, version 1.0.1.
Copyright 2004 John Gruber
http://daringfireball.net/projects/markdown/
It doesn't support useful features such as "fenced" code blocks (line are concatenated as if if only kept the last of the opening backticks and the first of the closing backticks).
When I look for a markdown man page on the web there is obviously a more recent (2008) and more complete version (many more options than in my local man page). Where can I find it? Is its source available somewhere? Searching for markdown on the web is near impossible since you get thousands of hits for markdown syntax cheatsheets.
When I double-click on the title bar of any window, nothing happens. I notice that on the first click I get the Move pointer, and if enabled I get the geometry displays.
Double-click works fine everywhere else, so I don't think it's my mouse(*).
In Window management>Window behavior>Titlebar actions>Title bar, Double-click is set to Maximize (but all other actions seem to be ignored as well).
Known problem? Any working around such as editing some config file somewhere?
My ~/.config/kwinrc:
[MouseBindings]
CommandActiveTitlebar1=Raise
CommandActiveTitlebar2=Start window tab drag
CommandActiveTitlebar3=Operations menu
CommandAll1=Move
CommandAll2=Toggle raise and lower
CommandAll3=Resize
CommandAllKey=Alt
CommandAllWheel=Nothing
CommandInactiveTitlebar1=Activate and raise
CommandInactiveTitlebar2=Start window tab drag
CommandInactiveTitlebar3=Operations menu
CommandTitlebarWheel=Switch to Window Tab to the Left/Right
CommandWindow1=Activate, raise and pass click
CommandWindow2=Activate and pass click
CommandWindow3=Activate and pass click
CommandWindowWheel=Scroll
[Plugins]
kwin4_effect_dialogparentEnabled=false
kwin4_effect_fadeEnabled=false
kwin4_effect_scaleEnabled=true
windowgeometryEnabled=true
[Windows]
ActiveMouseScreen=false
AutoRaise=false
AutoRaiseInterval=750
AutogroupInForeground=true
AutogroupSimilarWindows=false
BorderSnapZone=10
CenterSnapZone=0
ClickRaise=true
DelayFocusInterval=300
FocusPolicy=ClickToFocus
FocusStealingPreventionLevel=1
GeometryTip=true
HideUtilityWindowsForInactive=true
InactiveTabsSkipTaskbar=false
MaximizeButtonLeftClickCommand=Maximize
MaximizeButtonMiddleClickCommand=Maximize (vertical only)
MaximizeButtonRightClickCommand=Maximize (horizontal only)
NextFocusPrefersMouse=false
Placement=Smart
SeparateScreenFocus=false
ShadeHover=false
ShadeHoverInterval=250
SnapOnlyWhenOverlapping=false
TitlebarDoubleClickCommand=Maximize
WindowSnapZone=10
(*) By the way, I don't see any mouse settings to change the double-click delay (but it is fine as it is).
At least go to "classic". I don't want to sidestep the issue with links or bindmounts...
Freshly installed Kubuntu 19.10
I install Kalarm, which drags in 39 other packages, most with "akonadi" or "pim" in their name.
I then try to start Kalarm, and get a panel saying that "The Akonadi personal information management service is not running. This application cannot be used without it.". Just below is a big "Start" button but clicking on it does nothing.
If I start kalarm in a terminal I see:
org.kde.pim.kidentitymanagement: IdentityManager: There was no default identity. Marking first one as default.
org.kde.pim.kalarm: Preferences::setNoAutoStart: Error writing autostart file: "/home/me/.config/autostart/kalarm.autostart.desktop"
org.kde.pim.akonadicore: Unable to execute akonadi_control, falling back to D-Bus auto-launch
Clicking on the Start button adds another:
org.kde.pim.akonadicore: Unable to execute akonadi_control, falling back to D-Bus auto-launch
Creating the /home/me/.config/autostart/kalarm.autostart.desktop removes the 2nd line but doesn't solve the problem.
Any ideas?
Versions:
plasmashell 5.16.5
Qt: 5.12.4
KDE Frameworks: 5.62.0
kf5-config: 1.0
Edit: So installed mariadb and akonadi server (5.11.3). Rebooted. Now starting kalarm says:
org.kde.pim.kidentitymanagement: IdentityManager: There was no default identity. Marking first one as default.
Failed to register /MainApplication on DBus
""
akonadiselftest reports two errors:
Current installation status:
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture Description
+++-=================================-==================-============-==========================================
ii akonadi-backend-mysql 4:19.04.3-0ubuntu3 all MySQL storage backend for Akonadi
un akonadi-backend-postgresql <none> <none> (no description available)
un akonadi-backend-sqlite <none> <none> (no description available)
ii akonadi-server 4:19.04.3-0ubuntu3 amd64 Akonadi PIM storage service
un akonadiconsole <none> <none> (no description available)
un libakonadi-kf5 <none> <none> (no description available)
ii libkf5akonadicontact-data 4:19.04.3-0ubuntu1 all akonadi-contacts - data files
un libkf5akonadicontact5 <none> <none> (no description available)
ii libkf5akonadicontact5abi1:amd64 4:19.04.3-0ubuntu1 amd64 Akonadi contacts access library
ii libkf5akonadicore-bin 4:19.04.3-0ubuntu3 amd64 Tools for Akonadi core library
un libkf5akonadicore5 <none> <none> (no description available)
ii libkf5akonadicore5abi1:amd64 4:19.04.3-0ubuntu3 amd64 Akonadi core library
ii libkf5akonadimime-data 4:19.04.3-0ubuntu1 all akonadi-mime - data files
ii libkf5akonadimime5:amd64 4:19.04.3-0ubuntu1 amd64 Akonadi MIME handling library
ii libkf5akonadiprivate5abi2:amd64 4:19.04.3-0ubuntu3 amd64 libraries for the Akonadi PIM storage serv
ii libkf5akonadisearchpim5:amd64 4:19.04.3-0ubuntu1 amd64 Akonadi search library
un libkf5akonadisocialutils5 <none> <none> (no description available)
ii libkf5akonadiwidgets5abi1:amd64 4:19.04.3-0ubuntu3 amd64 Akonadi widgets library
un libkf5akonadixml5 <none> <none> (no description available)
ii libkf5libkdepimakonadi5:amd64 4:19.04.3-0ubuntu1 amd64 KDE PIM Akonadi library
ii libkf5mailtransportakonadi5:amd64 19.04.3-0ubuntu1 amd64 mail transport service library for akonadi
Fresh install of Kubuntu 19.10 on a new Lenovo P53.
At first the Wifi network works, and I'm able to connect to my home Wifi using the usual password.
The driver manager recommends to install backport-iwlwifi-dkms, which I do, but now the passwords are rejected. I also tried my phone hotspot (that has a rather simple password) and it is rejected too. I can connect to the phone hotspot if I reconfigure it to be password-less.
Password can be displayed and is OK, I even copy/pasted it.
The log of a connection sequence from /var/log/syslog (it seems it tried first to connect using a stored password which is very likely the right one too):
Jan 17 21:45:41 P53 NetworkManager[1121]: <info> [1579293941.9624] device (wlp82s0): Activation: starting connection 'HomeNetwork' (9ca67590-8a02-495c-a7cb-da56076aad08)
Jan 17 21:45:41 P53 NetworkManager[1121]: <info> [1579293941.9627] audit: op="connection-activate" uuid="9ca67590-8a02-495c-a7cb-da56076aad08" name="HomeNetwork" pid=1633 uid=1000 result="success"
Jan 17 21:45:41 P53 kernel: [ 2997.428660] wlp82s0: authenticate with 14:0c:76:bc:ab:68
Jan 17 21:45:41 P53 wpa_supplicant[1122]: wlp82s0: SME: Trying to authenticate with 14:0c:76:bc:ab:68 (SSID='HomeNetwork' freq=5260 MHz)
Jan 17 21:45:41 P53 NetworkManager[1121]: <info> [1579293941.9630] device (wlp82s0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Jan 17 21:45:41 P53 NetworkManager[1121]: <info> [1579293941.9643] manager: NetworkManager state is now CONNECTING
Jan 17 21:45:41 P53 NetworkManager[1121]: <info> [1579293941.9656] device (wlp82s0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Jan 17 21:45:41 P53 NetworkManager[1121]: <info> [1579293941.9664] device (wlp82s0): Activation: (wifi) access point 'HomeNetwork' has security, but secrets are required.
Jan 17 21:45:41 P53 NetworkManager[1121]: <info> [1579293941.9665] device (wlp82s0): state change: config -> need-auth (reason 'none', sys-iface-state: 'managed')
Jan 17 21:45:41 P53 NetworkManager[1121]: <info> [1579293941.9684] device (wlp82s0): state change: need-auth -> prepare (reason 'none', sys-iface-state: 'managed')
Jan 17 21:45:41 P53 NetworkManager[1121]: <info> [1579293941.9687] device (wlp82s0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Jan 17 21:45:41 P53 NetworkManager[1121]: <info> [1579293941.9688] device (wlp82s0): Activation: (wifi) connection 'HomeNetwork' has security, and secrets exist. No new secrets needed.
Jan 17 21:45:41 P53 NetworkManager[1121]: <info> [1579293941.9688] Config: added 'ssid' value 'HomeNetwork'
Jan 17 21:45:41 P53 NetworkManager[1121]: <info> [1579293941.9688] Config: added 'scan_ssid' value '1'
Jan 17 21:45:41 P53 NetworkManager[1121]: <info> [1579293941.9688] Config: added 'bgscan' value 'simple:30:-80:86400'
Jan 17 21:45:41 P53 NetworkManager[1121]: <info> [1579293941.9688] Config: added 'key_mgmt' value 'WPA-PSK WPA-PSK-SHA256 FT-PSK'
Jan 17 21:45:41 P53 NetworkManager[1121]: <info> [1579293941.9689] Config: added 'psk' value '<hidden>'
Jan 17 21:45:41 P53 NetworkManager[1121]: <info> [1579293941.9793] device (wlp82s0): supplicant interface state: inactive -> authenticating
Jan 17 21:45:41 P53 NetworkManager[1121]: <info> [1579293941.9793] device (p2p-dev-wlp82s0): supplicant management interface state: inactive -> authenticating
Jan 17 21:45:41 P53 kernel: [ 2997.433797] wlp82s0: send auth to 14:0c:76:bc:ab:68 (try 1/3)
Jan 17 21:45:42 P53 wpa_supplicant[1122]: wlp82s0: Trying to associate with 14:0c:76:bc:ab:68 (SSID='HomeNetwork' freq=5260 MHz)
Jan 17 21:45:42 P53 NetworkManager[1121]: <info> [1579293942.0044] device (wlp82s0): supplicant interface state: authenticating -> associating
Jan 17 21:45:42 P53 NetworkManager[1121]: <info> [1579293942.0044] device (p2p-dev-wlp82s0): supplicant management interface state: authenticating -> associating
Jan 17 21:45:42 P53 kernel: [ 2997.458775] wlp82s0: authenticated
Jan 17 21:45:42 P53 kernel: [ 2997.461167] wlp82s0: associate with 14:0c:76:bc:ab:68 (try 1/3)
Jan 17 21:45:42 P53 kernel: [ 2997.463098] wlp82s0: RX AssocResp from 14:0c:76:bc:ab:68 (capab=0x111 status=0 aid=4)
Jan 17 21:45:42 P53 wpa_supplicant[1122]: wlp82s0: Associated with 14:0c:76:bc:ab:68
Jan 17 21:45:42 P53 wpa_supplicant[1122]: wlp82s0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
Jan 17 21:45:42 P53 kernel: [ 2997.468796] wlp82s0: associated
Jan 17 21:45:42 P53 NetworkManager[1121]: <info> [1579293942.0195] device (wlp82s0): supplicant interface state: associating -> 4-way handshake
Jan 17 21:45:42 P53 NetworkManager[1121]: <info> [1579293942.0195] device (p2p-dev-wlp82s0): supplicant management interface state: associating -> 4-way handshake
Jan 17 21:45:42 P53 kernel: [ 2997.523928] wlp82s0: Limiting TX power to 17 (20 - 3) dBm as advertised by 14:0c:76:bc:ab:68
Jan 17 21:45:42 P53 kernel: [ 2998.015706] iwlwifi 0000:52:00.0: Unhandled alg: 0x707
Jan 17 21:45:43 P53 kernel: [ 2998.480972] wlp82s0: deauthenticating from 14:0c:76:bc:ab:68 by local choice (Reason: 1=UNSPECIFIED)
Jan 17 21:45:43 P53 wpa_supplicant[1122]: nl80211: kernel reports: NLA_F_NESTED is missing
Jan 17 21:45:43 P53 wpa_supplicant[1122]: wlp82s0: WPA: Failed to set PTK to the driver (alg=3 keylen=16 bssid=14:0c:76:bc:ab:68)
Jan 17 21:45:43 P53 wpa_supplicant[1122]: wlp82s0: CTRL-EVENT-DISCONNECTED bssid=14:0c:76:bc:ab:68 reason=1 locally_generated=1
Jan 17 21:45:43 P53 wpa_supplicant[1122]: wlp82s0: WPA: 4-Way Handshake failed - pre-shared key may be incorrect
Jan 17 21:45:43 P53 wpa_supplicant[1122]: wlp82s0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="HomeNetwork" auth_failures=1 duration=10 reason=WRONG_KEY
Jan 17 21:45:43 P53 wpa_supplicant[1122]: wlp82s0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="HomeNetwork" auth_failures=2 duration=20 reason=CONN_FAILED
Jan 17 21:45:43 P53 wpa_supplicant[1122]: dbus: wpa_dbus_property_changed: no property SessionLength in object /fi/w1/wpa_supplicant1/Interfaces/3
Jan 17 21:45:43 P53 NetworkManager[1121]: <warn> [1579293943.0361] sup-iface[0x55e11c9c6be0,wlp82s0]: connection disconnected (reason -1)
Jan 17 21:45:43 P53 NetworkManager[1121]: <info> [1579293943.0412] device (wlp82s0): supplicant interface state: 4-way handshake -> disconnected
Jan 17 21:45:43 P53 NetworkManager[1121]: <info> [1579293943.0420] device (wlp82s0): Activation: (wifi) disconnected during association, asking for new key
Jan 17 21:45:43 P53 NetworkManager[1121]: <info> [1579293943.0420] device (wlp82s0): state change: config -> need-auth (reason 'supplicant-disconnect', sys-iface-state: 'managed')
Jan 17 21:45:43 P53 NetworkManager[1121]: <info> [1579293943.0424] device (p2p-dev-wlp82s0): supplicant management interface state: 4-way handshake -> disconnected
Jan 17 21:45:43 P53 NetworkManager[1121]: <info> [1579293943.1413] device (wlp82s0): supplicant interface state: disconnected -> inactive
Jan 17 21:45:43 P53 NetworkManager[1121]: <info> [1579293943.1413] device (p2p-dev-wlp82s0): supplicant management interface state: disconnected -> inactive
Jan 17 21:45:54 P53 NetworkManager[1121]: <info> [1579293954.0258] device (wlp82s0): state change: need-auth -> prepare (reason 'none', sys-iface-state: 'managed')
Jan 17 21:45:54 P53 NetworkManager[1121]: <info> [1579293954.0262] device (wlp82s0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Jan 17 21:45:54 P53 NetworkManager[1121]: <info> [1579293954.0265] device (wlp82s0): Activation: (wifi) connection 'HomeNetwork' has security, and secrets exist. No new secrets needed.
Jan 17 21:45:54 P53 NetworkManager[1121]: <info> [1579293954.0265] Config: added 'ssid' value 'HomeNetwork'
Jan 17 21:45:54 P53 NetworkManager[1121]: <info> [1579293954.0265] Config: added 'scan_ssid' value '1'
Jan 17 21:45:54 P53 NetworkManager[1121]: <info> [1579293954.0265] Config: added 'bgscan' value 'simple:30:-80:86400'
Jan 17 21:45:54 P53 NetworkManager[1121]: <info> [1579293954.0265] Config: added 'key_mgmt' value 'WPA-PSK WPA-PSK-SHA256 FT-PSK'
Jan 17 21:45:54 P53 NetworkManager[1121]: <info> [1579293954.0266] Config: added 'psk' value '<hidden>'
Jan 17 21:45:54 P53 NetworkManager[1121]: <info> [1579293954.0372] device (wlp82s0): supplicant interface state: inactive -> scanning
Jan 17 21:45:54 P53 NetworkManager[1121]: <info> [1579293954.0372] device (p2p-dev-wlp82s0): supplicant management interface state: inactive -> scanning
Jan 17 21:45:55 P53 wpa_supplicant[1122]: wlp82s0: SME: Trying to authenticate with 14:0c:76:55:47:d1 (SSID='HomeNetwork' freq=2447 MHz)
Jan 17 21:45:55 P53 kernel: [ 3010.490277] wlp82s0: authenticate with 14:0c:76:55:47:d1
Jan 17 21:45:55 P53 NetworkManager[1121]: <info> [1579293955.0417] device (wlp82s0): supplicant interface state: scanning -> authenticating
Jan 17 21:45:55 P53 NetworkManager[1121]: <info> [1579293955.0417] device (p2p-dev-wlp82s0): supplicant management interface state: scanning -> authenticating
Jan 17 21:45:55 P53 kernel: [ 3010.496321] wlp82s0: send auth to 14:0c:76:55:47:d1 (try 1/3)
Jan 17 21:45:55 P53 wpa_supplicant[1122]: wlp82s0: Trying to associate with 14:0c:76:55:47:d1 (SSID='HomeNetwork' freq=2447 MHz)
Jan 17 21:45:55 P53 kernel: [ 3010.520689] wlp82s0: authenticated
Jan 17 21:45:55 P53 kernel: [ 3010.521092] wlp82s0: associate with 14:0c:76:55:47:d1 (try 1/3)
Jan 17 21:45:55 P53 NetworkManager[1121]: <info> [1579293955.0662] device (wlp82s0): supplicant interface state: authenticating -> associating
Jan 17 21:45:55 P53 NetworkManager[1121]: <info> [1579293955.0662] device (p2p-dev-wlp82s0): supplicant management interface state: authenticating -> associating
Jan 17 21:45:55 P53 kernel: [ 3010.525437] wlp82s0: RX AssocResp from 14:0c:76:55:47:d1 (capab=0x411 status=0 aid=3)
Jan 17 21:45:55 P53 wpa_supplicant[1122]: wlp82s0: Associated with 14:0c:76:55:47:d1
Jan 17 21:45:55 P53 wpa_supplicant[1122]: wlp82s0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
Jan 17 21:45:55 P53 kernel: [ 3010.531546] wlp82s0: associated
Jan 17 21:45:55 P53 NetworkManager[1121]: <info> [1579293955.0822] device (wlp82s0): supplicant interface state: associating -> 4-way handshake
Jan 17 21:45:55 P53 NetworkManager[1121]: <info> [1579293955.0822] device (p2p-dev-wlp82s0): supplicant management interface state: associating -> 4-way handshake
Jan 17 21:45:55 P53 wpa_supplicant[1122]: nl80211: kernel reports: NLA_F_NESTED is missing
Jan 17 21:45:55 P53 wpa_supplicant[1122]: wlp82s0: WPA: Failed to set PTK to the driver (alg=3 keylen=16 bssid=14:0c:76:55:47:d1)
Jan 17 21:45:55 P53 kernel: [ 3010.543158] wlp82s0: deauthenticating from 14:0c:76:55:47:d1 by local choice (Reason: 1=UNSPECIFIED)
Jan 17 21:45:55 P53 wpa_supplicant[1122]: wlp82s0: CTRL-EVENT-DISCONNECTED bssid=14:0c:76:55:47:d1 reason=1 locally_generated=1
Jan 17 21:45:55 P53 wpa_supplicant[1122]: wlp82s0: WPA: 4-Way Handshake failed - pre-shared key may be incorrect
Jan 17 21:45:55 P53 wpa_supplicant[1122]: wlp82s0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="HomeNetwork" auth_failures=1 duration=10 reason=WRONG_KEY
Jan 17 21:45:55 P53 wpa_supplicant[1122]: wlp82s0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="HomeNetwork" auth_failures=2 duration=20 reason=CONN_FAILED
Jan 17 21:45:55 P53 wpa_supplicant[1122]: dbus: wpa_dbus_property_changed: no property SessionLength in object /fi/w1/wpa_supplicant1/Interfaces/3
Jan 17 21:45:55 P53 NetworkManager[1121]: <warn> [1579293955.1000] sup-iface[0x55e11c9c6be0,wlp82s0]: connection disconnected (reason -1)
Jan 17 21:45:55 P53 NetworkManager[1121]: <info> [1579293955.1051] device (wlp82s0): supplicant interface state: 4-way handshake -> disconnected
Jan 17 21:45:55 P53 NetworkManager[1121]: <info> [1579293955.1056] device (wlp82s0): Activation: (wifi) disconnected during association, asking for new key
Jan 17 21:45:55 P53 NetworkManager[1121]: <info> [1579293955.1057] device (wlp82s0): state change: config -> need-auth (reason 'supplicant-disconnect', sys-iface-state: 'managed')
Jan 17 21:45:55 P53 NetworkManager[1121]: <info> [1579293955.1060] device (p2p-dev-wlp82s0): supplicant management interface state: 4-way handshake -> disconnected
Jan 17 21:45:55 P53 NetworkManager[1121]: <info> [1579293955.2052] device (wlp82s0): supplicant interface state: disconnected -> inactive
Jan 17 21:45:55 P53 NetworkManager[1121]: <info> [1579293955.2052] device (p2p-dev-wlp82s0): supplicant management interface state: disconnected -> inactive
Jan 17 21:45:57 P53 NetworkManager[1121]: <warn> [1579293957.0813] device (wlp82s0): no secrets: User canceled the secrets request.
Jan 17 21:45:57 P53 NetworkManager[1121]: <info> [1579293957.0814] device (wlp82s0): state change: need-auth -> failed (reason 'no-secrets', sys-iface-state: 'managed')
Jan 17 21:45:57 P53 NetworkManager[1121]: <info> [1579293957.0817] manager: NetworkManager state is now DISCONNECTED
Jan 17 21:45:57 P53 NetworkManager[1121]: <warn> [1579293957.0824] device (wlp82s0): Activation: failed for connection 'HomeNetwork'
Jan 17 21:45:57 P53 NetworkManager[1121]: <info> [1579293957.0826] device (wlp82s0): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed')
The part of lshw that seems relevant:
*-pci:3
description: PCI bridge
product: Cannon Lake PCH PCI Express Root Port #6
vendor: Intel Corporation
physical id: 1c.5
bus info: pci@0000:00:1c.5
version: f0
width: 32 bits
clock: 33MHz
capabilities: pci pciexpress msi pm normal_decode bus_master cap_list
configuration: driver=pcieport
resources: irq:125 memory:ce200000-ce2fffff
*-network
description: Ethernet interface
product: Intel Corporation
vendor: Intel Corporation
physical id: 0
bus info: pci@0000:52:00.0
logical name: wlp82s0
version: 1a
serial: 94:e6:f7:f4:70:cc
width: 64 bits
clock: 33MHz
capabilities: pm msi pciexpress msix bus_master cap_list ethernet physical
configuration: broadcast=yes driver=iwlwifi driverversion=5.3.0-26-generic firmware=48.4fa0041f.0 latency=0 link=no multicast=yes
resources: irq:17 memory:ce200000-ce203fff
Any ideas?
Otherwise how do I reinstall the previous one?
$$>dkms status
backport-iwlwifi, 7906, 5.3.0-26-generic, x86_64: installed
nvidia, 435.21, 5.3.0-18-generic, x86_64: installed
nvidia, 435.21, 5.3.0-26-generic, x86_64: installed
I'm using Ubuntu 16.04 (actually, Kubuntu and therefore a KDE desktop). I have a pair of BT headphones (AKG Y500). I have configured the device preferences to be these headphones for video and music if they are connected. This works most of the time: pairing the headphones switches the output to them. But from time to time:
Some tests:
Is there some software component I can restart to fix this quickly when it happens?
PS: this is similar to this question, but in my case it works most of the time.
PPS: tried to restart pulseaudio, but the daemon looks seriously hung, it doesn't even disappear after a kill -9
Running Kubuntu 16.04
Sometimes the name resolution gets slow. In previous Ubuntu versions, the problem was usually in resolv.conf and was easy to fix. In 16.04 all the DNS resolution is hidden in a NetworkManager+resolvconf+dsnmasq maze, and I don't know how I can figure out the actual DNS (dig says it's 127.0.1.1).
Could a kind soul explain:
ls -al /etc/resolv.conf
lrwxrwxrwx 1 root root 29 Apr 8 2017 /etc/resolv.conf -> ../run/resolvconf/resolv.conf
cat /etc/resolv.conf
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
# DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
nameserver 127.0.1.1
dpkg -l *dnsmasq*
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture Description
+++-==============-============-============-=================================
un dnsmasq <none> <none> (no description available)
ii dnsmasq-base 2.75-1ubuntu amd64 Small caching DNS proxy and DHCP/
host -v www.ebay.com
Trying "www.ebay.com"
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 46563
;; flags: qr rd ra; QUERY: 1, ANSWER: 3, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;www.ebay.com. IN A
;; ANSWER SECTION:
www.ebay.com. 292 IN CNAME slot9428.ebay.com.edgekey.net.
slot9428.ebay.com.edgekey.net. 10094 IN CNAME e9428.b.akamaiedge.net.
e9428.b.akamaiedge.net. 12 IN A 104.80.20.236
Received 122 bytes from 127.0.1.1#53 in 2 ms
Trying "e9428.b.akamaiedge.net"
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 35831
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;e9428.b.akamaiedge.net. IN AAAA
;; AUTHORITY SECTION:
b.akamaiedge.net. 674 IN SOA n0b.akamaiedge.net. hostmaster.akamai.com. 1564414527 1000 1000 1000 1800
Received 101 bytes from 127.0.1.1#53 in 2 ms
Trying "e9428.b.akamaiedge.net"
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 16147
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;e9428.b.akamaiedge.net. IN MX
;; AUTHORITY SECTION:
b.akamaiedge.net. 992 IN SOA n0b.akamaiedge.net. hostmaster.akamai.com. 1564414845 1000 1000 1000 1800
Received 101 bytes from 127.0.1.1#53 in 2 ms
cat /etc/network/interfaces
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback
cat /etc/hosts | head
127.0.0.1 localhost
127.0.1.1 Xenoid
# The following lines are desirable for IPv6 capable hosts
::1 localhost ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
ff02::3 ip6-allhosts
cat /etc/NetworkManager/NetworkManager.conf
[main]
plugins=ifupdown,keyfile,ofono
dns=dnsmasq
[ifupdown]
managed=false
cat /etc/nsswitch.conf
# /etc/nsswitch.conf
#
# Example configuration of GNU Name Service Switch functionality.
# If you have the `glibc-doc-reference' and `info' packages installed, try:
# `info libc "Name Service Switch"' for information about this file.
passwd: compat
group: compat
shadow: compat
gshadow: files
hosts: files mdns4_minimal [NOTFOUND=return] dns
networks: files
protocols: db files
services: db files
ethers: db files
rpc: db files
netgroup: nis
How can I add language dictionaries to KDE apps? So far they only support some variants of English. There are hints that Hunspell could be used, but according to dpkg -l 'hunspell*', hunspell itself is not installed, while, curiously, hunspell-en-us is). Furthermore, the list of available language packages is small, and doesn't contain major languages such as Spanish or French.
The KDE handbook is a dead-end (broken link...)
Using Kubuntu 16.04
My Firefox windows (started from a Plasma launcher or by Ctrl-N in Firefox) appear without a title bar. Other applications are fine. Using Windows action (Alt-F3) on a Firefox window:
More actions>No Border is checked. I can un-check this but it only applies to the current windowMore actions>Specific applications settings>Appearance & Fixes appear like below. Is it the right way to fix this? Or is there another setting upstream (which would explain what the setting is grayed out?)?
And above all, what could have caused the change?
Using Kubuntu 16.04
My Network Monitor plasmoid suddenly stopped showing usage for the Ethernet link, but it still does for the Wifi. The System Monitor (ksysguardd) displays rates correctly. At some point, even though the plasmoid was broken I could see the graph in the NetworkManager systray widget. I tried another plasmoid (Netspeed?) and it had the same problem. /proc/net/dev has the information (I wrote a short script to use it).
Things could be related to a reboot that upgraded the kernel (currently on 4.13.0-37-generic #42~16.04.1-Ubuntu), but the Ethernet link kept its name.
Running Kubuntu 16.04
Hoping to fix a few issues with KDE apps on Kubuntu 16.04, I added a backports PPA (kubuntu-ppa-ubuntu-backports-xenial), and updated manually a couple of apps (apt-get install --only-upgrade`).
Furthermore it is about time I apply a bunch of regular upgrades, and I'm not confident enough to allow a general upgrade from the PPA.
So
In KDE4 (Kubuntu 14.04) there was a trash directory per file system (on /home it was somewhere under ~, on other filesystems it was (from memory) a /.trash/{id}/. The benefit was that trashing files was quick since they were just moved to that directory.
In KDE5 (Kubuntu 16.04) I only have one trash directory in /home, and deleting things on the second disk is slow (and induces wear in the SSD). Is there a way to configure trash to work as in KDE4?
I'm using a VPS based on Ubuntu 16.04 that comes set up with UFW. One default rule of UFW limits the number of SSH connections (and given the number of attempts I see in the auth.log file, this is a good thing that I do no want to remove).
However this makes it difficult to write scripts that use remote commands to manage the server since these will typically create many connections (one per command).
So is there a way to lift that limit for a handful of trusted IPs?
I use KDE (Kubuntu 14.04), the Oxygen theme and Firefox, and FF46 has several bugs with GTK3, the most annoying being displaying tooltips as dark text over a barely darker background.
So I'am looking for a temporary change in them settings to either have the text in white (but I think the problem is that FF46 isn't using the theme color) or having a lighter background.
As far as I can't tell the tooltip background is not even a solid color but a vertical gradient, from roughly 60,53,48 at the top to 42,37,33 at the bottom and I cannot relate these to some contents of the theme in /usr/share/themes/oxygen-gtk/gtk-3.0/ (kdeglobals, oxygenrc or the two CSS files).
So, where are these colors defined?
At home, depending on room, signal pertubation (many Wifi networks around), and phase of the moon I connect to the modem/router with Ethernet or Wifi. In practice this means either Wifi alone, or Wifi+Ethernet (in which case all traffic goes through the Ethernet interface).
If I change rooms I may have to add/remove the Ethernet link. However this usually breaks any connection (VPN, in particular). The only case where things work OK are adding the Ethernet with an HTTP download in progress (the download switches to the Ethernet interface all by itself).
Is there some utility or network manager setting/manoeuver that I could use to prepare the switch and prevent breaking existing connections?
Strangely these connections will very often survive an Ethernet interruption (unplug Ethernet, move swiftly to other room, plug back Ethernet), even with Wifi switched off.