Ask Your Question

azzemeen's profile - activity

2017-10-03 03:00:50 -0500 commented answer f24 cannot open display: :0 NOT using wayland!?

I tried that as well but it gives me the same error.

2017-10-03 02:58:35 -0500 commented question f24 cannot open display: :0 NOT using wayland!?

Using echo $WAYLAND_DISPLAY results in Type=X11. And since I am using fedora 24 I thought wayland is not active per default.
Also xauth + should work under wayland, right? Nut it just doesn't. I am really stuck here.

2017-10-02 16:09:18 -0500 commented question f24 cannot open display: :0 NOT using wayland!?

I set the DISPLAY variable as a possible fix. Because both DISPLAY and XAUTHORITY were empty.

2017-10-02 03:06:48 -0500 commented answer f24 cannot open display: :0 NOT using wayland!?

Unfortunately beesu runs into the same problem. Also, root used to have access to my regular user's display. It just broke after the last update and I don't know which component causes this problem.

2017-10-01 14:57:21 -0500 commented question f24 cannot open display: :0 NOT using wayland!?

I found this issue while preparing my system for an update. The programs wont work when I invoke them as root su -

2017-10-01 04:23:21 -0500 commented question Optimus with Fedora 26

Is bbswitch installed correctly and loaded? I have the same setup and remember the pain.

2017-09-30 18:02:12 -0500 asked a question f24 cannot open display: :0 NOT using wayland!?

Programs like gedit gparted or even xrandr are failing with the error stated above. Booting into GNOME or KDE won't help. I tried everything that I found on google.

Even xauth + will result in the same error.

export DISPLAY=:0 is set permanently in /etc/environment.

I don't know what I am missing here.

2017-08-19 14:18:47 -0500 received badge  Popular Question (source)
2016-10-02 08:16:53 -0500 answered a question Heating and draining battery while suspended

This is still an issue and seems to be related to the dedicated GPU which will be turned on before the computer suspends. There is a helpful discussion in the bumblebee project where excatly these symptoms are described. See here

2016-10-01 06:07:47 -0500 received badge  Supporter (source)
2016-06-21 18:17:35 -0500 asked a question IBus ignores hotkeys with KDE Plasma

Dear community,

for some reason, IBus keeps ignoring the hotkeys to switch the input method. I am running out of ideas:

What I tried so far:

  1. updating everything
  2. setting the environment variables (I am quite confident, that I got this all right)
  3. changing the hotkeys <alt>space; <strg><alt>space; <strg><alt>m and many more.
  4. calling the IBus daemon using ibus-daemon --xim
  5. checking that there are no conflicts with other hotkey specified in the system preferences

I am grateful for any idea or hint for a good documentation. So far I have searched for hours but it seems that this problem is quite rare.

Best regards

2016-02-05 09:22:34 -0500 received badge  Student (source)
2016-02-05 00:54:34 -0500 asked a question HDMI Playback device not listed, Fedora 23

Hello everyone,

first time for me to ask a question here. Hope I am doing everything right.

My problem is that aplay -l doesn't list the hdmi at all. Video via hdmi is working but there is obviously no sound.

I used the ALSA Information Script to provide the information about my system: System Info

Things I have tried so far:

  • Load snd_hda_codec_hdmi manually as it was not loaded
  • Remove nouveau and install nVidia drivers. Result: System doesn't boot properly
  • Create /etc/modprobe.d/intel.conf and insert options as suggested here
  • Attempted to disable IOMMU by passing iommu=off boot option. Suggested here (This was a rather desperate attempt as I don't understand what IOMMU is actually doing.)

So now I am stuck and I greatly appreciate any hint to get the hdmi sound to work.

Thank you so much.