Ask Your Question

MaoTao's profile - activity

2019-02-27 00:51:57 -0600 received badge  Popular Question (source)
2019-02-27 00:51:57 -0600 received badge  Notable Question (source)
2019-02-13 02:56:30 -0600 received badge  Popular Question (source)
2019-02-13 02:56:30 -0600 received badge  Notable Question (source)
2018-12-19 06:40:36 -0600 received badge  Popular Question (source)
2018-12-15 11:24:34 -0600 asked a question gsettings don't work

gsettings don't work I have been trying to set different things with gsettings, but nothing ever happens. Always i get t

2018-12-14 06:03:11 -0600 received badge  Notable Question (source)
2018-12-14 06:03:11 -0600 received badge  Famous Question (source)
2018-12-14 06:03:11 -0600 received badge  Popular Question (source)
2018-08-07 14:37:37 -0600 received badge  Popular Question (source)
2018-08-03 19:14:15 -0600 received badge  Nice Question (source)
2018-07-27 02:01:29 -0600 received badge  Famous Question (source)
2018-07-12 23:08:30 -0600 received badge  Notable Question (source)
2018-07-12 23:08:30 -0600 received badge  Famous Question (source)
2018-07-02 05:39:51 -0600 received badge  Notable Question (source)
2018-04-29 05:50:14 -0600 received badge  Popular Question (source)
2018-03-19 10:06:22 -0600 received badge  Nice Answer (source)
2018-03-18 07:16:05 -0600 answered a question Why is gnome-tweak-tool not opening?

Try this:

sudo vim $(which gnome-tweak-tool) (or sudo gedit $(which gnome-tweak-tool) if you prefer)

and delete "env " from the shebang at the first line leaving only #!/usr/bin/python3

Save, and open again.

2018-03-17 18:45:52 -0600 commented question Boot gets stuck at "Starting Switch Root"

It should Reach Target Switch Root before Starting Switch Root.

I would first check the dependences of the Switch Root target unit file. Could be a configuration issue.

2018-03-16 17:38:27 -0600 commented question 15 minute wait after grub2 menu before kernel messages appear, Dell PE R420, RAID-5 Fed 27
2018-03-16 16:37:38 -0600 commented question 15 minute wait after grub2 menu before kernel messages appear, Dell PE R420, RAID-5 Fed 27

That's the easy part sudo modprobe "name of the module here". The hard one is to check and find the proper one. It could be a module (driver) for the RAID controller, or for the SAS drives. Google and manufacturers specifications/instructions could help.

2018-03-16 16:19:21 -0600 commented question 15 minute wait after grub2 menu before kernel messages appear, Dell PE R420, RAID-5 Fed 27

If this is the first time you go with SAS drives and RAID 5 on an already operating system, i would check for proper kernel modules. Maybe they are missing from your system, or you need to modprobe them.

2018-03-16 16:06:43 -0600 answered a question How to extend LVM partition on Fedora 27?

I haven't ever used blivet, but as a general guideline i would suggest first of all, make sure your fedora filesystem is unmounted when you try such operations, secondary i would put part (or whole) of that 102.02GiB free space into a new volume group, and then added it to the fedora volume group, creating a bigger logical volume for fedora as a whole.

2018-03-15 14:36:05 -0600 asked a question Packet Tracer 7.1.1 for Fedora workaround

I have download Packet Tracer 7.1.1 64-bit (which is for Ubuntu 14.04). I run the script installer and all works great.

The problem is that it doesn't start. After a check with ldd it seems that it misses libcrypto.so.1.0.0. I can't find this specific library in official repos.

I checked my system and it is installed by Anaconda Python 3, so i copied it. If i run packettracer from terminal nothing happens nor i get any log in journal. If i run it from /opt/pt/bin where is installed with ./PacketTracer7 i get seg fault. Running a check with ldd again it says that the library copied from Anaconda is the wrong version.

So i managed to to get the original library file from an Ubuntu 14.04. Checked with ldd again all looking fine, except when i try to run it from terminal again with packettracer nothing happens.

If i run it as ./PacketTracer7 it starts normally, but after a few seconds i get a seg fault again.

Any ideas ?

------------------------------------UPDATE----------------------------------------------

Finally i was able to solve the issue. In order to make it work for Fedora 27, you need totally four shared libraries, which you just copy to /lib64 and run a sudo ldconfing

The libraries are: libcrypto.so.1.0.0, libicuuc.so.52, libicui18n.so.52 and libicudata.so.52

They all need to be 64-bit x8664. The way i obtain them is by a live image of Ubuntu 14.04 64-bit x8664 on a USB.

2018-01-02 16:19:02 -0600 answered a question Removed global pip dependencies broke dnf

I would try to revert to a previous state as a first step:

sudo dnf history list and after sudo dnf history rollback <transaction ID> or sudo dnf history undo <transaction ID>

If those don't help, i would consider using a live media system (DVD drive or USB) with which you could repair by installing the required binaries, in order to make your system work again.

2017-12-21 20:44:39 -0600 received badge  Popular Question (source)
2017-12-12 09:42:56 -0600 received badge  Popular Question (source)
2017-12-12 09:42:56 -0600 received badge  Notable Question (source)
2017-11-17 15:30:41 -0600 commented question Fedora 26 -> 27 Error

Indeed, i just removed the package, and all went smooth with the system upgrade. Probably it was installed as a dependecy.

2017-11-17 03:48:17 -0600 asked a question Fedora 26 -> 27 Error

Hello community,

When i try to upgrade i get this unpleasant error:

Error: 
 Problem 1: package ceph-devel-compat-1:10.2.7-2.fc26.x86_64 requires libcephfs-devel = 1:10.2.7-2.fc26, but none of the providers can be installed
  - libcephfs-devel-1:10.2.7-2.fc26.x86_64 does not belong to a distupgrade repository
  - problem with installed package ceph-devel-compat-1:10.2.7-2.fc26.x86_64

I have both of mentioned packages above installed in my system. What is the actual problem here?

Just point me to a direction, so i can try to fix it please.

2017-10-12 06:47:10 -0600 commented question RTNETLINK error

Under the new kernel version 4.13.5-200.fc26.x86_64 i get the same erro/warnings. But after typing echo $? it returns 0, meaning that the script did the configuration. I tested it with downloading a large file over http. The downloading speed was the the correct as configured. So i' m closing this, since it seems that it works, and error/warning has to do with something else.

2017-10-06 12:22:02 -0600 commented answer RTNETLINK error

I updated with the script. Or the new kernel is "buggy" and have to wait for some update, or there something drastically changed to networking in the kernel with 4.13 version.

2017-10-06 09:47:58 -0600 asked a question RTNETLINK error

Hi, i' m using the Wondershaper script for a long time now with no issues. After the last kernel update to 4.13.4-200.fc26.x86_64, if i try to activate the script i get the following error message:

RTNETLINK answers: Invalid argument
We have an error talking to the kernel

After a search with the above error, i noticed that it has to do usually with cases of static IP configuration. I haven't changed anything to my IP settings, and still use DHCP. I checked the IP/subnet mask/default gateway/DNS and all look correct from a math point of view.

I did reset the modem, it leased to me an new IP, but still i get the same issues.

-Edit-

I rolled to the previous kernel 4.12.14-300.fc26.x86_64 and all works fine.

Here is the script as requested

#!/bin/bash 

# Wonder Shaper

function show_help {
  echo "Wonder Shaper 1.2.1"
  echo
  echo "Usage: $0 [device] clean|[upload speed in Kb/s] [download speed in Kb/s]"
  echo "Example: $0 eth0 20 500"
  echo
  echo "https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora&component=wondershaper"
  exit
}

if [ $# -eq 0 ]; then
    show_help;
fi

if [ $# -eq 1 ]; then
  tc -s qdisc ls dev $1
  tc -s class ls dev $1
  exit
fi

if [ $# -eq 2 ]; then
  tc qdisc del dev $2 root    2> /dev/null > /dev/null
  tc qdisc del dev $2 ingress 2> /dev/null > /dev/null
  echo Wondershaper queues have been cleared.
  exit
fi

if [ $# -ne 3 ]; then
    show_help;
fi

# Set the following values to somewhat less than your actual download
# and uplink speed. In kilobits. Also set the device that is to be shaped.
DOWNLINK=$3
UPLINK=$2
DEV=$1

# low priority OUTGOING traffic - you can leave this blank if you want
# low priority source netmasks
NOPRIOHOSTSRC=

# low priority destination netmasks
NOPRIOHOSTDST=

# low priority source ports
NOPRIOPORTSRC=

# low priority destination ports
NOPRIOPORTDST=

#########################################################

# clean existing down- and uplink qdiscs, hide errors
tc qdisc del dev $DEV root    2> /dev/null > /dev/null
tc qdisc del dev $DEV ingress 2> /dev/null > /dev/null

if [ "$1" = "stop" ] 
then 
    exit
fi

###### uplink

# install root CBQ

tc qdisc add dev $DEV root handle 1: cbq avpkt 1000 bandwidth 10mbit 

# shape everything at $UPLINK speed - this prevents huge queues in your
# DSL modem which destroy latency:
# main class

tc class add dev $DEV parent 1: classid 1:1 cbq rate ${UPLINK}kbit \
allot 1500 prio 5 bounded isolated 

# high prio class 1:10:

tc class add dev $DEV parent 1:1 classid 1:10 cbq rate ${UPLINK}kbit \
   allot 1600 prio 1 avpkt 1000

# bulk and default class 1:20 - gets slightly less traffic, 
#  and a lower priority:

tc class add dev $DEV parent 1:1 classid 1:20 cbq rate $[9*$UPLINK/10]kbit \
   allot 1600 prio 2 avpkt 1000

# 'traffic we hate'

tc class add dev $DEV parent 1:1 classid 1:30 cbq rate $[8*$UPLINK/10]kbit \
   allot 1600 prio 2 avpkt 1000

# all ...
(more)
2017-08-06 17:58:59 -0600 commented question DRM - Screen black out

I haven't enter BIOS since months. As i wrote before, everything works fine until that random moment, on a random day where the screen goes black for couple of seconds and then back to normal.

2017-08-06 17:12:58 -0600 commented question DRM - Screen black out

I haven't install any proprietary driver. I just upgraded from F25 to F26. The issue started many days after the upgrade, so i don't relate it to the upgrade. I just run my daily dnf -b --allowerasing update

2017-08-06 13:13:42 -0600 asked a question DRM - Screen black out

Hey, it's been about ten days now where my screen is going black, and it always happens twice with a few seconds difference. There is not any periodical pattern. I use F26 under Wayland, all default drivers, and the with the same GPU for years now.

Here are the logs right after it happened today again:

Aug 06 20:52:26 192.168.1.2 gnome-shell[1479]: Failed to apply DRM plane transform 0: Invalid argument
Aug 06 20:52:36 192.168.1.2 gnome-shell[1479]: Failed to apply DRM plane transform 0: Invalid argument
Aug 06 20:52:37 192.168.1.2 kernel: [drm:si_dpm_set_power_state [radeon]] *ERROR* si_restrict_performance_levels_before_switch failed

Is there a software issue or could i be facing a hardware failure and i should start looking for a new GPU soon?

2017-07-23 08:08:35 -0600 received badge  Popular Question (source)
2017-07-22 08:46:06 -0600 asked a question Viber problem

I downloaded the viber.rpm file from Viber's site, i install it using sudo rpm -Uvh viber.rpm and when i try to run it i get a crash error. Here is the output from journactl:

Jul 22 15:07:18 192.168.1.3 viber.desktop[3119]: QSqlDatabasePrivate::removeDatabase: connection 'ConfigureDBConnection' is still in use, all queries will cease to work.
Jul 22 15:07:20 192.168.1.3 viber.desktop[3119]: Qt WebEngine ICU data not found at /opt/viber/resources. Trying parent directory...
Jul 22 15:07:20 192.168.1.3 viber.desktop[3119]: Qt WebEngine resources not found at /opt/viber/resources. Trying parent directory...
Jul 22 15:07:20 192.168.1.3 viber.desktop[3119]: Qt WebEngine ICU data not found at /opt/viber/resources. Trying parent directory...
Jul 22 15:07:20 192.168.1.3 viber.desktop[3119]: Qt WebEngine resources not found at /opt/viber/resources. Trying parent directory...
Jul 22 15:07:21 192.168.1.3 viber.desktop[3119]: qt.network.ssl: QSslSocket: cannot resolve CRYPTO_num_locks
Jul 22 15:07:21 192.168.1.3 viber.desktop[3119]: qt.network.ssl: QSslSocket: cannot resolve CRYPTO_set_id_callback
Jul 22 15:07:21 192.168.1.3 viber.desktop[3119]: qt.network.ssl: QSslSocket: cannot resolve CRYPTO_set_locking_callback
Jul 22 15:07:21 192.168.1.3 viber.desktop[3119]: qt.network.ssl: QSslSocket: cannot resolve ERR_free_strings
Jul 22 15:07:21 192.168.1.3 viber.desktop[3119]: qt.network.ssl: QSslSocket: cannot resolve EVP_CIPHER_CTX_cleanup
Jul 22 15:07:21 192.168.1.3 viber.desktop[3119]: qt.network.ssl: QSslSocket: cannot resolve EVP_CIPHER_CTX_init
Jul 22 15:07:21 192.168.1.3 viber.desktop[3119]: qt.network.ssl: QSslSocket: cannot resolve sk_new_null
Jul 22 15:07:21 192.168.1.3 viber.desktop[3119]: qt.network.ssl: QSslSocket: cannot resolve sk_push
Jul 22 15:07:21 192.168.1.3 viber.desktop[3119]: qt.network.ssl: QSslSocket: cannot resolve sk_free
Jul 22 15:07:21 192.168.1.3 viber.desktop[3119]: qt.network.ssl: QSslSocket: cannot resolve sk_num
Jul 22 15:07:21 192.168.1.3 viber.desktop[3119]: qt.network.ssl: QSslSocket: cannot resolve sk_pop_free
Jul 22 15:07:21 192.168.1.3 viber.desktop[3119]: qt.network.ssl: QSslSocket: cannot resolve sk_value
Jul 22 15:07:21 192.168.1.3 viber.desktop[3119]: qt.network.ssl: QSslSocket: cannot resolve SSL_library_init
Jul 22 15:07:21 192.168.1.3 viber.desktop[3119]: qt.network.ssl: QSslSocket: cannot resolve SSL_load_error_strings
Jul 22 15:07:21 192.168.1.3 viber.desktop[3119]: qt.network.ssl: QSslSocket: cannot resolve SSL_get_ex_new_index
Jul 22 15:07:21 192.168.1.3 viber.desktop[3119]: qt.network.ssl: QSslSocket: cannot resolve SSLv23_client_method
Jul 22 15:07:21 192.168.1.3 viber.desktop[3119]: qt.network.ssl: QSslSocket: cannot resolve SSLv23_server_method
Jul 22 15:07:21 192.168.1.3 viber.desktop[3119]: qt.network.ssl: QSslSocket ...
(more)
2017-07-20 10:48:45 -0600 commented answer tracker-extract

Well it worked. I deleted ~/.local/share/tracker and ~/.cache/tracker directories as you suggested. After a reboot, tracker-extract indexed everything from zero, without any issues what so ever.

2017-07-19 14:44:30 -0600 commented answer tracker-extract

Indeed, i don't consider it a major issue, just from time to time i check the journal, and try to fix some things if they seem critical or persistent. I will follow your advice about deleting cache etc, and if it doesn't work i will install the tracker-preferences GUI and manage tracker from there.

2017-07-19 13:23:53 -0600 asked a question tracker-extract

Each time i boot i see my log file populated with messages from tracker-extract. Here is a sample (they are hunderds of them with the same pattern):

Jul 19 19:04:12 192.168.1.3 tracker-extract[1967]: Could not insert metadata for item "file:///home/konstantin/Downloads/Lynda%20-%20C%20Essential%20Training%20with%20Isac%20Artzi/18_01-goodbye.mp4": Unable to insert multiple values for subject `urn:uuid:fec35116-d31f-04ec-f04a-c47260537938' and single valued property `nfo:hasHash' (old_value: '555304', new value: '1155213')

Jul 19 19:04:12 192.168.1.3 tracker-extract[1967]: If the error above is recurrent for the same item/ID, consider running "tracker-extract" in the terminal with the TRACKER_VERBOSITY=3 environment variable, and filing a bug with the additional information

It's always on the same files, and those files happen to be mostly .mp4. I checked the path

/usr/share/mime

and there exists a mp4.xml file.

Also i ran the command as the the log message suggests but nothing changed. After a new boot the same log messages appeared.

Anyone has any fix?

2017-07-07 14:45:33 -0600 commented question Problems mounting a USB hard drive

Could you also run in a terminal udevadm monitor and then plug the USB at the specific port and check the output ?