Ask Your Question

Jmlevick's profile - activity

2015-11-01 13:38:00 -0500 commented answer firewalld failed on new install fedora 22

This is the right answer and the solution, mark it as accepted OP.

2015-07-15 03:12:43 -0500 received badge  Famous Question (source)
2015-06-09 14:16:27 -0500 asked a question Kernel version discrepancies

Why does this happen?:

image description

image mirror:

I decided to give Ksplice another shot with F22 and although I'm not getting boot errors after running the upgrade this time, I'm getting weird kernel version dicrepancies like in the image, any thoughts?

P.S. Now with F22 DO instances manage their kernels internally, which means upgrading via any method should reflect the most current verision installed.

2015-04-18 09:49:20 -0500 received badge  Notable Question (source)
2015-04-12 05:05:35 -0500 received badge  Popular Question (source)
2015-04-10 14:02:47 -0500 received badge  Necromancer (source)
2015-04-10 00:51:33 -0500 answered a question F21 fails to boot reliably with kernels >= 3.18

Hello everyone!

Recently I came across a very similar issue in my current F21 Setup (BTRFS /, UEFI Machine etc) and found out a "workaround/solution" that I describe in my question:

Could you try what I did please and tell me if your system boots afterwards? This way we could know if we're facing the same issue and then be a step closer to solve it.


2015-04-10 00:51:25 -0500 commented question F21: BTRFS + LUKS won't boot on 3.19.x-x kernel

Fairly similar as I also have a UEFI machine but none of them have listed my workaround so I'm threating it as a different issue until I can confirm otherwise.... The thing is, my main problem is not being able to provide my LUKS password when the system misbehaves. I dunno if with non-encrypted home this would turn out differently.

2015-04-08 17:30:12 -0500 asked a question F21: BTRFS + LUKS won't boot on 3.19.x-x kernel

So I've been reading a little about BTRFS problems with 3.19 kernels here:

and I have a problem that I think may or may not be related:

The thing is, I can't boot my Fedora 21 x86_64 machine with 3.19.3-200 (BTRFS /) it doesn't even ask for the /home LUKS passphrase (/home is a ext4 partition). 3.17.x works fine... Performing a:

btrfs check --repair <partition>

while on initramfs (as recommended on the reddit thread) accomplishes nothing. Pressing "Esc" while booting to hide the plymouth loading screen and see "the log" returns a wierd red and purple mashup of letters:


When the system does boot with this kernel (at the 5th try or so), / filesystem is corrupt, returning cpio errors when unpacking RPM's and never installing them. Using older kernel results in being able to boot and install such packages with no problems, besides using the system normally.

What's happening here?

P.S. On the BTRFS wiki they recommend to apply btrfs-zero-log and on reddit some user mention btrfs scrub, but I'm on a SSD and I dunno how harmful those operations might be (repair itself seems harmful) so... ideas?

EDIT: Removing rhgb quiet from GRUB_CMDLINE_LINUX in /etc/default/grub and regenerating grub's configuration with:

grub2-mkconfig -o /boot/grub2/grub.cfg

"Solves" the issue by letting me hit escape at boot and enter the LUKS passphrase for /home... Then the system boots as normal and everything works as expected. placing again rhgb quiet and regenerating grub's conf leaves me with the same issue commented above. I do not have any propietary graphic drivers installed by the way.

EDIT 2: The system returned to an unbootable state just like that... The "solution"? regenerate grub's conf again (leaved rhgb quiet out of GRUB_CMDLINE_LINUX).

2015-03-27 13:07:33 -0500 marked best answer KDE Windows auto-resize....

Hi, I have a small "bug" on Fedora 16 "Verne" with KDE 4.7 since I installed the distro when it came out as stable:

When I open ANY kind of app that requires a Window to function, it "auto-resizes" and occupy the most of the screen it can, Let's say I open an app with a very small notify window (such as gtk-recordmydesktop) if I don't have anything opened it occupies the Full Screen of the Computer, If I open two apps at the same time, they occupy half and half of the computer's screen each one instead of opening at their normal size (Let's say I open the Konsole and Firefox at the same time, The Half of the screen get's occupied by Firefox and the other half by konsole...

How can I fix this?? Is getting really annoying right now...

2014-01-23 03:48:47 -0500 received badge  Taxonomist
2013-10-22 02:37:08 -0500 received badge  Popular Question (source)
2013-10-22 02:37:08 -0500 received badge  Famous Question (source)
2013-10-22 02:37:08 -0500 received badge  Notable Question (source)
2013-10-21 08:10:55 -0500 received badge  Teacher (source)
2013-10-21 00:43:46 -0500 answered a question I need help outsourcing my business.

Humm... yeah! it seems like a good way to go. What other strategies have you tought about? in the process you should install Fedora Linux in all your machines so you can save some money in Windows licenses and tech support every 3 months or so when the machines start to be really slow with the Microsoft's Operating System.

2013-10-19 19:21:26 -0500 commented question Black Windows in Gnome 3 (suddenly)

Yep, someone already told me at bugzilla ;)

2013-10-19 11:48:36 -0500 answered a question Black Windows in Gnome 3 (suddenly)

As marcindulak pointed out in a comment, this bug report it's relevant for the issue, and a fix it's posted there:

I'll tell you what to do:

1) su -  
2) touch /etc/X11/xorg.conf.d/10-intel.conf    
3) gedit /etc/X11/xorg.conf.d/10-intel.conf

and in that file we have to put te following:

Section "Device"
    Identifier "Intel Graphics"
    Driver "intel"
    Option "AccelMethod" "sna"

We save, reboot and problem solved! at least in my case. There are some cards where the SNA acceleration method it's not supported, so if you still having the problem after this, just change "sna" for "uxa" in the file we've just created.

2013-10-07 08:31:43 -0500 received badge  Notable Question (source)
2013-10-07 08:31:43 -0500 received badge  Famous Question (source)
2013-09-25 21:44:55 -0500 received badge  Famous Question (source)
2013-09-25 13:59:47 -0500 commented question Black Windows in Gnome 3 (suddenly)

Thanks, that seems relevant to this issue. What I don't know is if I have to create a 10-intel.conf as the guy that reports that bug or a 20-intel.conf as the ArchWiki recommends. Also I'm not sure if my card it's compatible with SNA or I have to set that option to UXA. For the moment, I'll create the same file as the one in the bug report and test to see if the problem dissapears. In the meantime I'll be waiting for more answers :)

2013-09-25 10:30:25 -0500 received badge  Notable Question (source)
2013-09-25 08:09:30 -0500 received badge  Popular Question (source)
2013-09-25 06:52:32 -0500 asked a question Black Windows in Gnome 3 (suddenly)

I've been having this problem for a while now; The problem is, when I'm using GTK apps such as GIMP or Firefox, suddenly these apps start to have black menus and sub windows, and then, when I open other app, such app it's fully black. Restarting the shell results in a GNOME crash, so I have to either log out with "Ctrl + Alt + Backspace" or reboot the computer to get normal apps again. A screenshot of the problem:

I don't know what might be causing this, and it's completely random as far as I've experienced. I do not have propietary drivers installed on this system, my lspci it's here:

Kernel: 3.11.1-200.fc19.x86_64 (fedora 19)

Any ideas?

2013-09-25 04:48:13 -0500 received badge  Favorite Question (source)
2013-09-21 13:57:41 -0500 received badge  Famous Question (source)
2013-09-21 13:41:18 -0500 commented answer Kernel 3.11 & BTRFS: system doesn't boot

Thanks for the tip! I already fixed the actual issue but it's good to know how to correctly copy the sosreport.txt file ;)

2013-09-21 13:39:35 -0500 answered a question Kernel 3.11 & BTRFS: system doesn't boot

I've solved it, My process was the following:

1) Reboot into an older kernel, remove the problematic kernel's individual packages as root with rpm -e --nodeps once per package (The removed packages were kernel, kernel-devel, kernel-headers, kernel-modules-extra).

2) Install a newer kernel (a debug one) from rawhide

3) Boot into the debug kernel

4) Ran a 'yum -y update kernel-* --enablerepo=updates-testing', This step updated the older kernel to the problematic one.

5) Install the problematic kernel's individual packages from "updates-testing" repo (in case something was missing. For example in this case, kernel-headers-3.11.x-xxx.fc19.x86_64 did not installed with the update).

6) Remove Rawhide's kernel individual packages and reboot.

7) Booting in the previously problematic kernel (which now works!) And cleaning up the system with:

su -
yum-complete-transaction --cleanup-only
package-cleanup --orphans
package-cleanup --cleandupes
yum repolist
yum clean all
yum makecache
yum -y update

And that's all, now my computer is hapilly booting with 3.11.1-200.fc19.x86_64 I hope this helps anyone who stumbles upon this issue ;)

2013-09-21 08:46:35 -0500 received badge  Notable Question (source)
2013-09-21 07:22:37 -0500 received badge  Popular Question (source)
2013-09-21 05:26:59 -0500 asked a question Kernel 3.11 & BTRFS: system doesn't boot

Today I ran a regular "sudo yum -y update" and Fedora just "blew up in my face" with the following screen after a reboot:

if I issue the "journalctl" command I can see a BTRFS error:

(My system's root partition is in BTRFS).

And as far as I've googled no one had this issue before and to be honest, I don't know how to solve it...

The "sosreport.txt" file just doesn't copy anywhere, I plug a USB in and then run:

cp /run/initramfs/sosreport.txt /dev/sdc1

and the command apparently runs successfully but when I check the USB it is empty, same if I save it to "/var" "/var/log" or "/usr", the file just doesn't appear anywhere. I ran "cat" on such file and it is enormous to photograph it, but I took another pic that might be helpful:

It's worth to mention that I don't have any propietary drivers running on this system and if I boot with the last kernel before the update (which is 3.10.11-200.fc19.x86_64) everything works normally. The problematic kernel version is the 3.11.1-200.fc19.x86_64 one.

Here you have my partition table:

And my lspci output is here:

Does anyone know how to solve this?


P.S. With kernel 3.12.0-0.rc1.git3.1.fc21.x86_64 (a debug kernel from rawhide) the problem is not present.

2013-09-21 04:14:50 -0500 received badge  Popular Question (source)
2013-09-21 04:14:50 -0500 received badge  Famous Question (source)
2013-09-21 04:14:50 -0500 received badge  Notable Question (source)
2013-09-11 17:04:35 -0500 received badge  Notable Question (source)
2013-09-11 17:04:35 -0500 received badge  Famous Question (source)
2013-09-11 17:04:05 -0500 received badge  Notable Question (source)
2013-09-11 17:04:05 -0500 received badge  Famous Question (source)
2013-04-06 21:31:28 -0500 received badge  Popular Question (source)
2013-03-26 02:33:49 -0500 received badge  Popular Question (source)
2013-03-21 17:58:31 -0500 asked a question How to setup No-ip on Fedora?


I want to setup a small Home Server using Fedora 17 (32 Bit) and No-ip because I have a Dynamic IP adress,

This is what am I doing:

1) I create a Host on No-ip:

image description

2) I setup No-ip on my fedora box:

su -
yum install noip
noip2 -C
chkconfig noip --add
chkconfig --levels 35 noip on

NOTE: My no-ip config file it's located at: /etc/no-ip2.conf

Reboot and verify it is running:

su -
service noip status
chkconfig --list | grep noip

(it actually points to my public IP adress)

3) Open Ports on the fedora's firewall:

image description

image description

4) Unlock No-IP on iptables:

su -
iptables -A INPUT -s -p tcp --sport 8243 -j ACCEPT
iptables -A OUTPUT -d -p tcp --dport 8243 -j ACCEPT
service iptables stop
service iptables start
service noip stop
service noip start
service noip status

5) Port Fowarding on the router:

image description

(I get the private IP adress from ifconfig)

6) Verify with Zenmap, Telnet & Ping

image description

NOTE: Here we have an interesting situation: Only the 80 TCP port seems to be open, the other two (111, 8243) are closed, even when they are unlocked on the firewall and fowarded on the router.

image description

PING fails, but as far as I know this is kinda normal right? 'cause ping isn't a DNS test mechanism... Correct me if I'm wrong please:

image description

Additional info:

I have an Apache/PHP setup, so if I go to I see my test.php page, but if I go to or I can't see anything, the browser just tries and tries and then throws an error...

P.S. SELinux is fully Disabled

What am I doing wrong? Please Help me!

Have a nice day.

2013-01-29 19:44:06 -0500 commented answer Random Kernel Panics in Fedora 18 since 3.7.2-204 Why?

As materialdefender2306 points out, with 3.6.10-4 everything is fine... I'll file a bug report while waiting for an answer here.