In Ubuntu Gnome, RDP is now the default protocol for Remote Desktop (& in my quick test, seems to work OK), but is the same possible in Xubuntu? I’m guessing the answer’s “No”, but thought I’d ask anyway.
I’m connecting from either Manjaro Cinnamon (latest Remmina) or Ubuntu Gnome.
There are tutorials out there for xrdp, but I want to connect to the logged in session, not a new session.
The compose key completely stopped working for me in Ubuntu 18.04 a couple of months ago. It’s happened before, but there has usually been a way of getting it to work again (e.g. restarting ibus), but this time I can’t get it to work at all.
Previously, I thought it was connected with resuming from suspend as a new session or a reboot would (mostly, but not always) bring it back, but now it seems gone for good.
How can I get it back/diagnose this?
Other answers here seem to be about other versions or xim (which I don’t think I’ve used in this 18.04 install) or rely on answers with no explanation. The main bug report that’s mentioned is also about xim and has a very high signal to noise ratio - many different situations and solutions are mentioned, including installing ibus.
Why does Ubuntu in particular have such a problem with it? I’ve had it happen once or twice in Solus, but I’ve not had it completely stop working.
In 16.04 the Onboard on-screen keyboard was available by default, but it looks like it was dropped (because of Gnome integration problems?).
Question 1: Can anyone confirm was onboard replaced by caribou?
Having done a fresh install of 18.04, looking in Synaptic it seems I have neither onboard nor caribou installed and switching on Screen Keyboard in Universal Access does nothing.
Question 2: Is this normal?
Question 3: Given I only use it occasionally when using unfamiliar keyboards (e.g. Greek), which will be less problematic?
I’m also using Budgie desktop, though the base install is the vanilla 18.04 with Gnome.
I have a couple of programs I use occasionally that use Mono (Cross-platform version of MS .NET). The fonts in these programs are always far too small, much like the default in Wine. Unlike Wine though there isn’t any obvious way of changing them. Can it be done?
I’ve been having problems with Seahorse lately. I suspect an update, but can’t say exactly when it started. It may also be two co-incidental problems.
In Thunderbird I use the Enigmail add-on to sign messages using PGP key. When you type in the passphrase there is an option to have it remembered (presumably by Seahorse), but this doesn’t work any more. Every session it asks for the passphrase again.
In Nemo (or Nautilus) if I do an adhoc connection to a SMB share and choose an option to remember the password, it is not saved.
If I run Seahorse (Passwords and Keys) there is no Passwords section, only Certificates, PGP Keys and Secure Shell. On the other 16.04 system I have, there is a Passwords section and the keys are in ~/.gnome2/keyrings/. On this computer (upgraded from 14.04) the keys are in ~/.local/share/keyrings/ and there is no ~/.gnome2/keyrings/ folder. I see references to both, but which is right?
Also if I choose to create a new item in the GUI, the options for creating a new Password Keyring or Stored Password (which are available on the clean install) are missing.
Context: Ubuntu 16.04.2 (64-bit) with sound over (NVIDIA GTX1070) HDMI to a receiver.
I don’t generally have problems with sound and I’ve played a few Unity engine games (32 and 64-bit) from Steam with no problem in the past, but with this game I get no sound at all. I’m following up with the developers, but their Linux release is fairly new and I suspect they don’t know too much about Linux in general.
I use Quod Libet with ALSA so a while ago I set up a panel indicator to show me what use is being made of the sound hardware (the output of cat /proc/asound/NVidia/pcm7p/sub0/hw_params), so when the game starts I can see the output going from closed to the usual S32LE — 6 channels — 48.0kHz* but nothing comes out of the speakers.
It’s a 32-bit game, but the developer kindly tried a 64-bit build with the same results.
My hopes aren’t high of getting a solution here; just that someone might have seen something similar. Next stop is the Unity forums I suppose.
[I think it would be good for searching if we had a unity-game-engine tag here, since it’s used quite a lot, but I don’t have 300 reputation :-( I’ve seen other posts use unity which is misleading.]
*Full output:
access: MMAP_INTERLEAVED
format: S32_LE
subformat: STD
channels: 6
rate: 48000 (48000/1)
period_size: 1360
buffer_size: 2720
I have a script that creates a new log file each week that can be called from other scripts with a log file parameter. Without any arguments it creates a log with the name of the parent process in ~/bin/log. This works fine in a terminal, but in a cron job it fails complaining that the function default-log is “not a valid identifier”.
The function seems trivial and everything it does works fine outside the function. I can easily work around this as the function is only called twice and I can just substitute the whole 2 lines, but I’d still like to understand what’s going on.
Other details:
weekly-log "$LOG") but all the echoed paths, etc. in my debugging look fine
#!/bin/bash
#
# Start fresh logfile each Monday using the supplied path/name
# or create in ~/bin/logs with the name of the calling script
LOG=""
PARENT="$(ps -o comm= $PPID)"
DATEFORMAT="+%a %e %b %Y %I:%M:%S %P %Z"
# Thu 26 Jan 2017 01:52:49 pm AEDT
# Debugging—these all look OK
echo "Args: $*"
echo "PPID: $PPID"
echo "PARENT: $PARENT"
echo "HOME: $HOME"
echo "Default LOG: $HOME/bin/log/$(basename "$PARENT").log"
mkdir -p "$HOME/bin/log"
function default-log {
mkdir -p "$HOME/bin/log"
LOG="$HOME/bin/log/$(basename "$PARENT").log"
}
if [ $# -eq 0 ] ; then
echo "No args"
default-log
# mkdir -p "$HOME/bin/log"
# LOG="$HOME/bin/log/$(basename "$PARENT").log"
else
DIR=$(dirname "$1")
# dirname returns "." for invalid path!
if [ ! "$DIR" = "." ] && [ -d "$DIR" ] ; then
LOG="$1"
else
echo "Invalid path"
default-log
# mkdir -p "$HOME/bin/log"
# LOG="$HOME/bin/log/$(basename "$PARENT").log"
echo "Invalid path to log file: $1" 2>&1 | tee "$LOG"
fi
fi
# Create new log or append
if [[ $(date +%u) -eq 1 ]] ; then
echo "--------------------------------" 2>&1 | tee "$LOG"
else
echo 2>&1 | tee -a "$LOG"
echo "--------------------------------" 2>&1 | tee -a "$LOG"
fi
echo $(date "$DATEFORMAT") 2>&1 | tee -a "$LOG"
echo "" 2>&1 | tee -a "$LOG"
I have a Wacom Bamboo tablet which has a touchpad function I almost never use—it mostly gets in the way. I have a script which switches that function off, run via a .desktop file in ~/.config/autostart. This works fine and I have no problem running the script from a terminal either.
The problem is that after resuming from suspend, the touch function reactivates. Prior to upgrading to 16.04, this script was called from /etc/pm/sleep.d/wacom which switched it off again. After upgrading I’ve tried doing the same thing using systemd (/lib/systemd/system-sleep/wacom), but there seems to be something very different about the context in which it’s run because the command produces puzzling errors.
Syslog shows wacom_set_report: ran out of retries (last error = -32) and error -32 seems to mean “communication pipe broken”.
Logging output shows that even getting the status fails—xsetwacom get "$DEVICE" touch* returns no output when it should report “on” or “off”. Running the command to switch off touch (xsetwacom set "$DEVICE" touch off) returns “Failed to open Display .”.
I also get this—warning: commands will be executed using /bin/sh but the script runs fine for me using sh.
I’ve tried adding a sleep command before calling the script but it doesn’t seem to help. I’ve called it using at (at now + 1 min -f), but the result is the same—even though it’s running well after resume the script still can’t even get the device status. I tried putting the status command into a while loop, but it never broke out of the loop (no status was returned), yet at the same time I could run the command successfully in a terminal.
I’ve also tried putting the command directly in /lib/systemd/system-sleep/wacom.
This is fairly trivial, but annoying that this used to work, but now doesn’t.
·
*DEVICE="Wacom Bamboo 2FG 6x8 Finger touch" as returned by xsetwacom list dev.
Some time back I installed ubuntu-gnome-desktop in Ubuntu 16.04 (possibly 14.04, since upgraded?) and it used to work fine. Now if I choose that session at the lightdm greeter I get a desktop which I think is actually Unity (XDG_CURRENT_DESKTOP=unity), although there is no launcher or top panel and windows don’t have widgets. If I run gnome-shell --replace in a terminal the Unity launcher and top panel appear. I’ve tried purging the package and reinstalling it, but nothing changes (in fact very little seems to be removed or reinstalled).
/usr/share/xsessions contains a gnome.desktop with Exec=gnome-session --session=gnome which sounds right.
Edit: I tried removing most/all of the contents ~/.config/autostart and then gnome-shell --replace does start gnome. Still don’t understand why the session starts Unity though. XDG_CURRENT_DESKTOP still says unity.
As a fresh install, 16.04 has been OK, but as an upgrade it seems very, very buggy.
Edit 2: After installing budgie-desktop from the budgie-remix PPA I get the same result. I guess the common denominator is Gnome.
Edit 3: Guest logins show the same behaviour—Unity, xfce and fluxbox work fine; Gnome and budgie don’t. This seems to rule out another commonly offered solution: deleting ~/.config or ~/.cache.
What is going on here?
[While researching this problem I have found a work-around, but I’m still curious to see if anyone can explain why this is happening.]
In the past I’m certain I’d added mediainfo-gui to the Open With list using Nemo. I’ve no idea what Nemo actually does when you do this, but it was working fine in Nemo, Thunar and Nautilus. Recently I noticed the association had disappeared, but when I tried to add it back it didn’t work. I tried doing it via command line, using mimeopen -d on a target file. This worked, but when I set the default back to the program I wanted, Mediainfo disappeared again.
I wonder if part of the problem is that /usr/share/application/mediainfo-gui.desktop has a Mimetype= line that contains no mimetypes? My workaround was to copy mimetypes from vlc.desktop (possibly overkill?) and then run sudo update-desktop-database.
[Ubuntu 14.04.4]
KTorrent once used to ask me what program to use (and I could tell it to use Nautilus), but now it only ever opens Banshee...which is less than useful.
Can anyone tell me how to explain to its tiny KDE brain that I want to use Nautilus to browse a folder?
Edit: after belatedly checking ~/.local/share/applications/mimeapps.list it did only list banshee and vlc for inode/directory, though why this is so is a mystery. After changing the setting KTorrent then once again asked me for a choice of program and I could check the ‘remember this choice’ checkbox.