Ask Your Question

Nils Philippsen's profile - activity

2017-11-30 07:39:24 -0500 commented answer <ctrl shift u> not working

I have the same issue on Fedora 27 with the default GNOME Shell on Wayland. Normally, pressing <ctrl+shift+u> gave me an underlined "u", let me type in the Unicode codepoint in hex (still underlined) and finish by pressing return. If I try that now e.g. with the codepoint 1f44d for the thumbs-up character in a shell, pressing <ctrl+shift+u> does nothing, the hex digits aren't underlined and if I press return it will tell me that it doesn't find the command "1f44d":

nils@gibraltar:~> 1f44d
-bash: 1f44d: command not found
nils@gibraltar:~>
2017-04-25 11:59:17 -0500 received badge  Enlightened (source)
2017-04-25 11:59:17 -0500 received badge  Good Answer (source)
2016-08-01 17:45:59 -0500 answered a question How can I remove this Skype sidebar thingy?

I assume you can't do it while Skype is still running, this is where all "legacy" tray icons are kept and there's no other easy way to get to Skype when it's minimized. However, there are some extensions for GNOME Shell that move these icons to the taskbar (if you prefer that, but I haven't tried any of them):

2015-07-08 04:52:13 -0500 received badge  Autobiographer
2014-12-07 14:57:30 -0500 received badge  Nice Answer (source)
2013-12-11 09:28:36 -0500 received badge  Supporter (source)
2013-12-11 09:27:49 -0500 commented question Enable a USB drive in a KVM running VM?

Not sure if you can do this with VMs started from the command line, but in virt-manager you can make USB devices available to running VMs (if not in use by the host or another guest).

2013-12-11 09:25:13 -0500 answered a question How to open an tcp port in firewall for transmission??

A bit more details would be helpful (used Fedora version, your networking setup). Assuming you're on a recent version, i.e. having firewalld and firewall-config, and that it's the firewall on your machine that's the culprit (rather than some other router), try this:

  1. Open firewall-config (that's "Firewall" in the desktop menus I believe).
  2. Type in the requested password (your own or that of the root user, depending on if your user is configured as an administrator or not).
  3. Select Permanent from the Configuration drop-down.
  4. Go to the Services tab, select the transmission-client service.
  5. Click on Add, add 65432 as the port, leave tcp as the protocol and click OK.
  6. Here it may again ask for the password.
  7. In ZonesServices enable the transmission-client service for your network zone (the default zone is shown in the lower right of the window).
  8. OptionsReload firewalld to make the changes effective.
2013-12-11 09:01:07 -0500 answered a question Upgrading 16 to 17 with RAID boot

The only idea I have (preupgrade really can't cope with /boot on RAID) is to do a YUM upgrade[1] from 16 to 17[2] and from there on use fedup -- which should know about /boot on RAID1[3] -- to upgrade to a currently maintained version: Fedora 20 should be out in not quite a week[4], version 18 will be retired about a month after that.

  1. http://fedoraproject.org/wiki/Upgrading_Fedora_using_yum
  2. http://fedoraproject.org/wiki/Upgrading_from_EOL_Fedora_using_yum
  3. http://ohjeezlinux.wordpress.com/2012/11/13/fedup-a-little-background/
  4. http://fedoraproject.org/wiki/Releases/20/Schedule
2013-12-11 08:51:45 -0500 answered a question How to enable old transitive DSO link behaviour?

Not that I think that this is a good idea, but you might try your luck with the --copy-dt-needed-entries option to ld or if that fails /usr/bin/ld.gold which is an alternative implementation contained in binutils.

2013-12-11 08:42:48 -0500 received badge  Editor (source)
2013-12-11 08:42:09 -0500 answered a question Fedora19 update

It maybe that the mirrors aren't up to date or your metadata is somehow else out of sync. To work around this try what randomuser said:

Usually this is temporary, but a yum clean metadata might help.

If that fails you might even try yum clean all.

2013-12-11 08:37:32 -0500 commented answer fedora 19 service management

Sorry for the late reply... I guess this is because you have an intermediate script (usr/local/bin/epcore.sh) which forks the real daemon process, "simple" means you start the process directly (which you may want to do unless your script does anything else besides starting the real process).

2013-11-12 03:26:44 -0500 answered a question fedora 19 service management

This shouldn't be necessary:

Alias=epcore.service

A systemd service unit needs a corresponding .service file, so simply name the file epcore.service, put it into /etc/systemd/system and run systemctl {enable,start,stop,...} epcore.service to manage it.

To reproduce your problem you needn't restart your machine, just use systemctl restart epcore.service and subsequently journalctl _SYSTEMD_UNIT=epcore.service to find the related log entries.

2013-11-09 10:17:57 -0500 commented question grub2-mkconfig renders grub.cfg inoperable

One issue I see is that grub2-mkconfig wouldn't know about your problems with the nouveau driver by itself, you could try adding the missing kernel cmdline parameters to GRUB_CMDLINE_LINUX in /etc/default/grub before running grub2-mkconfig. Your screen staying black may as well be related to the nouveau KMS driver doing something stupid (and disabling it would work around that).

2011-11-21 07:49:29 -0500 answered a question sloppy focus on Fedora 15

tuxfan: You might want to try out "gnome-tweak-tool", sloppy focusing can be enabled in its "Windows" tab. This is easier/safer than setting random keys in gconf-editor.

tjw344: sorry for not commenting directly, but apparently I haven't yet earned enough mojo to do so... anyway: you're right that dconf or rather gsettings is the preferred way now, but some older code still uses gconf (it is used for the window management mode).

2011-11-17 07:21:41 -0500 answered a question Gnome shell crashes after updating to F16 from F15 ?

Do you have any extensions installed? AFAIK, some make the shell crash if you don't have an icon set for your user (if you haven't: <name>-menu, click on the default, placeholder icon, in the "User Accounts" dialog, click on that icon again :-) and select one from the list).

2011-11-15 08:57:32 -0500 received badge  Teacher (source)
2011-11-15 08:06:17 -0500 answered a question systemd runlevels

Hmm, symlinking multi-user.target worked for me, and I wonder why you were successful with runlevel3.target but not multi-user.target as the former is simply a symlink to the latter. This is how I set up a local VM (didn't want to reboot my laptop ;-)), which booted and didn't start X/gdm just fine:

nils@f16:~> ls -l /lib/systemd/system/{runlevel3,multi-user}.target /etc/systemd/system/default.target
lrwxrwxrwx. 1 root root  37 Nov 15 13:40 /etc/systemd/system/default.target -> /lib/systemd/system/multi-user.target
-rw-r--r--. 1 root root 509 Oct 19 12:42 /lib/systemd/system/multi-user.target
lrwxrwxrwx. 1 root root  17 Oct 25 17:22 /lib/systemd/system/runlevel3.target -> multi-user.target

Not sure right now how to make this the permanent default for your user (i.e. so you only had to type "startx"), but this worked for me to start KDE out of multi-user.target:

nils@f16:~> startx /usr/bin/startkde