Ask Your Question

dave997's profile - activity

2019-01-16 00:39:49 -0500 received badge  Nice Question (source)
2019-01-13 17:45:20 -0500 commented question abrt creates empty folders named with non-printable characters

Done. I was looking for a way to mark it as solution here but couldn't find any, sorry XD

2019-01-13 17:42:43 -0500 commented answer Files and folders with name "� (invalid encoding)"; what does it mean and how to fix it?

I confirm, it's related to abrt. This was the correct solution to my problem too

2019-01-13 17:42:02 -0500 commented answer Files and folders with name "� (invalid encoding)"; what does it mean and how to fix it?

I confirm, it's related to abrt. This was the correct solution to my problem too: link text

2019-01-13 17:40:15 -0500 received badge  Supporter (source)
2019-01-13 09:59:48 -0500 commented question abrt creates empty folders named with non-printable characters

Yep, that workaround seems to fix the problem indeed. All we have to do is to wait for abrt to be patched then. Thank yo

2019-01-13 09:56:04 -0500 received badge  Student (source)
2019-01-13 08:12:35 -0500 asked a question abrt creates empty folders named with non-printable characters

abrt creates empty folders named with non-printable characters Hi there, I've just spent two hours trying to figure ou

2019-01-13 07:08:59 -0500 received badge  Popular Question (source)
2019-01-13 07:08:59 -0500 received badge  Notable Question (source)
2017-06-16 09:42:47 -0500 received badge  Famous Question (source)
2017-06-16 09:42:47 -0500 received badge  Notable Question (source)
2016-11-09 14:29:48 -0500 commented answer kde-connect, firewall policies and connection problems

Thank you, @Aeyoun . I've sent a report at Fedora Bug Report. Let's hope this helps! (developers, users..)

2016-11-09 14:29:47 -0500 commented question kde-connect, firewall policies and connection problems

Sure. I've had much more things to do this month than usual so stayed away for while, but I wasn't going to leave this Forum:)

2016-11-09 14:29:46 -0500 commented answer Windows 8 not booting after Fedora 24 install

Thank you, @yisupeng. Right now, my friend keeps using the F12 workaround when needed, to boot windows 8. So practically never, as he mainly uses Fedora now. I wish I had a test machine in order to make further investigations as you are doing, but unfortunately that is a work computer. Anyway, even after having read what reported in the link you suggested, I can't blame Fedora community's developers, since Microsoft (and its partners) have evidently done a great job in making things annoyingly more complicated than they should have been.

2016-11-09 11:26:23 -0500 received badge  Popular Question (source)
2016-09-30 18:10:26 -0500 asked a question kde-connect, firewall policies and connection problems

Hi there,

after a few emails exchanges with the developer of the KDE-connect application for Android, I've decided to report here the problem, as suggested.

Put briefly, some weeks ago I reinstalled Fedora 24 KDE after some months of use, set everything up again and immediately noticed that KDE-connect was not working any more. I spent some hours making all possible attempts to get it functional without success, then finally gave up - and ended thinking some update had messed up something.

Reality was actually different. When I reinstalled Fedora (using the latest iso), the kde-connect entry in the Firewall settings -> zones -> services was unmarked by default, contrarily to what happened months before with the first install. I don't think this could be seen as a good choice, since such a change of behavior is practically impossible to reveal - and creates problems. In fact, it was actually a case if I discovered what was preventing kde-connect from working.

Personally, I have no more problems henceforth, since I know the story.. So, just out of curiosity and hoping to help someone else, is my firewall behaving not as expected? Maybe my previous Fedora installation (which was on a USB HDD) somehow prevented firewalld from working, hence kde-connected worked immediately? And finally, assuming this being a bug, should I report it to the official Red Hat Bugzilla? Should this be the case, I'd be glad if some more experienced user could give some advice in order to make a useful, visible report (where, how, etc.).

Thank You all, David

2016-09-25 11:52:30 -0500 answered a question Windows 8 not booting after Fedora 24 install

Aah, that makes sense.. I mean, that's not exactly what I wished to hear, but at least gives an explanation to all this situation. I really have to thank you for that.

I'm then gonna look for firmware updates (if any, I don't think so..) and eventually prepare my friend to the possibility of using it as it is. In the mean time, I've found that there's a quick way of accessing that UEFI media boot selection by pressing F12 at startup, I report this just in case to could be useful to others.

In the eventuality of a UEFI firmware bug, as long as you know is there any way of changing that boot sequence in order to avoid the problem? (I know, the answer is most likely to be 'no', but I've still got hope 😅). In the mean time I'm gonna check out those links you posted, analyzing this damned buggy thing in search of a solution..

David

2016-09-24 01:55:35 -0500 asked a question Windows 8 not booting after Fedora 24 install

Hi there.

I'm writing here asking a little bit of time to those of You who want to help me with a very, very strange issue..

Put simply: I installed Fedora 24 Workstation (KDE) on 2 two different UEFI, GPT windows machines (dual boot) using exactly the same procedure (which is the standard one, with manual partitioning and the UEFI partition mounted at /boot/efi. The first (windows 10) works just fine, the other (win 8) not exactly the same..

Grub correctly created an entry for Windows Boot Loader but this simply does not work. A white, still dash appears (you know, like the terminal's blinking one) and everything stops there. I firstly thought of something gone wrong with the chainloader option, but everything seems to be ok. Don't know if this could help, but I also thought of a possible hardware-initialization issue in the win8 startup as grub comes up in a top-left 640x480 px box, instead of filling the screen (maybe windows fails to initialize the GPU because of that?). This laptop does not have any HDD light, but I'm pretty sure it's being used for a while, during the "steady-dash" phase..

And here comes the best. You guess? (unlikely..) If I type exit using GRUB's prompt, a UEFI boot media selection comes out, where I can choose HDD -> then Windows Boot Loader or Fedora. If I choose Windows Boot Loader from there, everything works fine. Except for one, final mystery: it works, but not always. A casual number of attempts of this procedure will finally bring me to a reassuring windows boot logo. Before that, the PC either restarts bringing me back to GRUB or the UEFI media selector fails to start the windows boot-loader and - again - grub pops up. THIS is the thing that is driving me CRAZY: PCs don't work casually. What the hell can cause a similar issue??

I need help since this machine isn't mine, I adviced a friend of mine to install fedora because my own experience was beautiful. So help me if you can, please.

Thank You all in advance, David