users July 2016

users@lists.fedoraproject.org

133 participants
133 discussions

maintenance mode
by Paolo Galtieri 08 Jul '16

08 Jul '16

I have a Fedora 23 system which I have updated with the latest updates. I rebooted the system and ran *sudo dnf upgrade --refresh* RPM Fusion for Fedora 23 - Free 584 kB/s | 457 kB 00:00 RPM Fusion for Fedora 23 - Nonfree - Updates 1.0 kB/s | 257 B 00:00 RPM Fusion for Fedora 23 - Free - Updates 552 B/s | 257 B 00:00 Adobe Systems Incorporated 7.1 kB/s | 1.8 kB 00:00 Fedora 23 - x86_64 - VirtualBox 253 kB/s | 74 kB 00:00 RPM Fusion for Fedora 23 - Nonfree 119 kB/s | 156 kB 00:01 google-chrome 46 kB/s | 3.5 kB 00:00 Dependencies resolved. Nothing to do. Complete! I rebooted the system at this point and went int emergency maintenance mode. I ran journalctl -xb, but I don't know what to look for. One of the last entries says: Received SIGRTMIN+21 from process 322(plymouthd) I found bug 1254874 which refers to SIGRTMIN+21, but the bug was closed as not a bug. Can someone tell me what I need to do to fix the system so it boots correctly? All the partitions are mounted so I don't think it's due to filesystem corruption. Any help is appreciated. Paolo

1 0

Fedora 24 - Grub2 permanent cmdline changes
by Earl Ramirez 08 Jul '16

08 Jul '16

Good day All, Recently I have performed a clean install of Fedora 24 and I will like to make some persistent changes to grub2, in the past (Fedora 23) I would modify /etc/sysconfig/grub and append the changes to the GRUB_CMDLINE and run grub2-mkconfig -o /boot/efi/EFI/fedora/grub.cfg and I would be okay. However when I try to get /etc/sysconfig/grub which is a symbolic link to /etc/default/grub I no long see the options to make the changes, Instead I see this content in both /etc/default/grub # # DO NOT EDIT THIS FILE # # It is automatically generated by grub2-mkconfig using templates # from /etc/grub.d and settings from /etc/default/grub # ### BEGIN /etc/grub.d/00_header ### set pager=1 if [ -s $prefix/grubenv ]; then load_env fi if [ "${next_entry}" ] ; then set default="${next_entry}" set next_entry= save_env next_entry set boot_once=true else set default="${saved_entry}" fi if [ x"${feature_menuentry_id}" = xy ]; then menuentry_id_option="--id" else **snip** I have checked the F24 docs on modify grub2 and I see that it still advise on editing GRUB_CMDLINE from /etc/sysconfig/grub. Can someone shed some light on making persistent changes to the grub cmdline on F24. Thanks in advance.

6 11

Chrome blocks hibernation
by Patrick O'Callaghan 08 Jul '16

08 Jul '16

This is weird. A few days ago I found that my desktop system (F23 fully updated) would no longer hibernate. A glance at "journal -xe" showed a bunch of lines like: Jun 14 00:50:51 bree audit[12591]: SECCOMP auid=1000 uid=1000 gid=1000 ses=1 subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 pid=12591 comm="chrome" exe="/opt/google/chrome/chrome" sig=0 arch=c000003e syscall=273 compat=0 ip=0 Jun 14 00:50:51 bree kernel: audit: type=1326 audit(1465861851.266:7800): auid=1000 uid=1000 gid=1000 ses=1 subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 pid=12591 comm="chrome" exe="/opt/google/chrome/chrome" sig=0 arch=c00 Jun 14 00:50:59 bree audit[12599]: SECCOMP auid=1000 uid=1000 gid=1000 ses=1 subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 pid=12599 comm="chrome" exe="/opt/google/chrome/chrome" sig=0 arch=c000003e syscall=273 compat=0 ip=0 Jun 14 00:50:59 bree kernel: audit: type=1326 audit(1465861859.424:7801): auid=1000 uid=1000 gid=1000 ses=1 subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 pid=12599 comm="chrome" exe="/opt/google/chrome/chrome" sig=0 arch=c00 Jun 14 00:51:07 bree audit[12603]: SECCOMP auid=1000 uid=1000 gid=1000 ses=1 subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 pid=12603 comm="chrome" exe="/opt/google/chrome/chrome" sig=0 arch=c000003e syscall=273 compat=0 ip=0 Jun 14 00:51:07 bree kernel: audit: type=1326 audit(1465861867.128:7802): auid=1000 uid=1000 gid=1000 ses=1 subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 pid=12603 comm="chrome" exe="/opt/google/chrome/chrome" sig=0 arch=c00 Jun 14 00:51:20 bree audit[12608]: SECCOMP auid=1000 uid=1000 gid=1000 ses=1 subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 pid=12608 comm="chrome" exe="/opt/google/chrome/chrome" sig=0 arch=c000003e syscall=273 compat=0 ip=0 Jun 14 00:51:20 bree kernel: audit: type=1326 audit(1465861880.130:7803): auid=1000 uid=1000 gid=1000 ses=1 subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 pid=12608 comm="chrome" exe="/opt/google/chrome/chrome" sig=0 arch=c00 Jun 14 00:52:09 bree audit[12646]: SECCOMP auid=1000 uid=1000 gid=1000 ses=1 subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 pid=12646 comm="chrome" exe="/opt/google/chrome/chrome" sig=0 arch=c000003e syscall=273 compat=0 ip=0 Jun 14 00:52:09 bree kernel: audit: type=1326 audit(1465861929.397:7804): auid=1000 uid=1000 gid=1000 ses=1 subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 pid=12646 comm="chrome" exe="/opt/google/chrome/chrome" sig=0 arch=c00 Jun 14 00:52:25 bree audit[12662]: SECCOMP auid=1000 uid=1000 gid=1000 ses=1 subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 pid=12662 comm="chrome" exe="/opt/google/chrome/chrome" sig=0 arch=c000003e syscall=273 compat=0 ip=0 Jun 14 00:52:25 bree kernel: audit: type=1326 audit(1465861945.701:7805): auid=1000 uid=1000 gid=1000 ses=1 subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 pid=12662 comm="chrome" exe="/opt/google/chrome/chrome" sig=0 arch=c00 Jun 14 00:52:25 bree audit[12667]: SECCOMP auid=1000 uid=1000 gid=1000 ses=1 subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 pid=12667 comm="chrome" exe="/opt/google/chrome/chrome" sig=0 arch=c000003e syscall=273 compat=0 ip=0 Jun 14 00:52:25 bree kernel: audit: type=1326 audit(1465861945.768:7806): auid=1000 uid=1000 gid=1000 ses=1 subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 pid=12667 comm="chrome" exe="/opt/google/chrome/chrome" sig=0 arch=c00 and when I killed Chrome then hibernation worked again. So one question is: what is the magic incantation to stop these alarms from Chrome? However another question is how is this even possible? A process with normal user privileges can prevent the system from hibernating? Is this right? poc

3 8

2 of 4 systems messed up after dnf system-upgrade
by Greg Woods 07 Jul '16

07 Jul '16

I have upgraded 4 systems (two laptops and two desktops, all different hardware) from F23 to F24. Two of them are working fine, and the others seem to be badly messed up in the area of package management. The main symptom I see is that google-chrome-stable was uninstalled during the upgrade, and I can't reinstall it: [root@cobweb yum.repos.d]# dnf install google-chrome-stable --allowerasing Last metadata expiration check: 0:08:42 ago on Sun Jul 3 17:09:12 2016. Error: nothing provides /usr/bin/foomatic-rip needed by redhat-lsb-printing-4.1-32.fc24.x86_64 [root@cobweb yum.repos.d]# I also get "no matching packages" responses to "dnf list" on packages that are already installed: root@cobweb yum.repos.d]# dnf clean all 72 files removed [root@cobweb yum.repos.d]# dnf list cups* Fedora 24 - x86_64 8.3 MB/s | 47 MB 00:05 google-chrome 55 kB/s | 3.5 kB 00:00 Adobe Systems Incorporated 17 kB/s | 1.8 kB 00:00 RPM Fusion for Fedora 24 - Free 839 kB/s | 326 kB 00:00 RPM Fusion for Fedora 24 - Nonfree 311 kB/s | 64 kB 00:00 Steam for Fedora 28 kB/s | 7.9 kB 00:00 Dropbox Repository 25 kB/s | 2.4 kB 00:00 RPM Fusion for Fedora 24 - Nonfree - Updates 131 kB/s | 18 kB 00:00 Fedora 24 - x86_64 - Updates 7.3 MB/s | 8.0 MB 00:01 RPM Fusion for Fedora 24 - Free - Updates 272 kB/s | 75 kB 00:00 Last metadata expiration check: 0:00:02 ago on Sun Jul 3 17:09:12 2016. Error: No matching Packages to list [root@cobweb yum.repos.d]# rpm -qa | grep cups cups-filesystem-2.1.0-2.fc23.noarch python3-cups-1.9.72-8.fc24.x86_64 cups-libs-2.1.0-2.fc23.x86_64 cups-client-2.1.0-2.fc23.x86_64 cups-libs-2.1.0-2.fc23.i686 python2-cups-1.9.72-8.fc24.x86_64 cups-filters-libs-1.6.0-1.fc23.x86_64 cups-pk-helper-0.2.5-6.fc23.x86_64 [root@cobweb yum.repos.d]# Here, dnf fails to even list packages that "rpm -q" shows are already on the system that should match the pattern. Anybody seen this or have a clue what I can do other than a full reinstall? Thanks, --Greg

6 12

Strange messages from sudo dnf repoquery --unsatisfied after upgrade from F23 to F24.
by Stephen Morris 07 Jul '16

07 Jul '16

Hi, I have issued the command specified in the subject as recommended on site https://fedoraproject.org/wiki/DNF_system_upgrade to see if there are any old packages that should be removed because they would not be working properly anyway, and received the following messages which to me make no sense, unless I am completely misinterpreting the message. The kernel mentioned in the first message is the last of the Fedora 23 kernels that is still installed after the upgrade to F24, while the kernel listed in the 2nd message is the kernel installed by a sudo dnf upgrade issued the day after the upgrade to F24. Hence the bottom line is both kernels mentioned in the messages are installed, so why is dnf reporting that it can't find them? package kmod-nvidia-4.5.7-200.fc23.x86_64-2:367.27-1.fc24.x86_64 requires kernel-uname-r = 4.5.7-200.fc23.x86_64, but none of the providers can be installed package kernel-4.6.3-300.fc24.x86_64 requires kernel-core-uname-r = 4.6.3-300.fc24.x86_64, but none of the providers can be installed regards, Steve

4 10

Really excessive screen behavior
by Robert Moskowitz 07 Jul '16

07 Jul '16

System is F22 with Xfce In the past, occasionally I would get what looks like a ScreenSaver popping over what I am viewing. It almost looks legit in content. It goes away if I <alt-tab> to another task then <alt-tab> back. QEMM seems to make it worst (running an 'old' F21/Xfce image there for a specific purpose). Well with a recent update, I am now getting this flashing regularly. It make using the system very hard. It is much worst in my QEMM image than the main image. I have looked at the Screensaver settings, and there is nothing there to indicate a problem. Plus I don't think it is really Screensaver which is set to lock the screen immediately (after 10 min of inactivity) which is not the case here. Any idea where I should look? Yes, I know that I need to update to recent Fedora. That is on for later this week. I hope....

6 17

Is the Vivacious Colors theme supported by Fedora?
by Paul Smith 07 Jul '16

07 Jul '16

Dear All, Is the Vivacious Colors theme supported by Fedora? Thanks in advance, Paul

1 0

ssh questions/issue
by bruce 07 Jul '16

07 Jul '16

Hi/morn guys... Searching for answers/opinions on how to allow multiple users to access a number of different boxes via ssh, using ssh keys.. Say I have 5 boxes on my network, box1 box2 box3 box4 box5 Each box has a generic user - user1, with limited perms/access On my local box, i create a pub/private ssh key. I copy the pub key to each box.. From my local box, I can then ssh -using the priv/pub key into box1. From box1, can I then hop/ssh over to box2, using the pub key for the user1 that I created/installed? I'm trying to figure out how I can hop between boxes as needed without having to have lots of pub/private keys ... (Viewed some articles that seem to indicate I can do this) Thoughts/comments..

3 2

How to change the GNOME colors theme from XFCE
by Paul Smith 07 Jul '16

07 Jul '16

Dear All, I am running F24 with XFCE. How to change the scheme of colors of GNOME applications? Thanks in advance, Paul

1 0

postgresql-setup upgrade returns error
by arnaud gaboury 07 Jul '16

07 Jul '16

I am left with a broken postgresql since my upgrade to Fedora 24. Starting the service retruns this error: # /usr/libexec/postgresql-ctl start -D /db/pgsql/data -s -w -t 270 FATAL: 22023: database files are incompatible with server DETAIL: The data directory was initialized by PostgreSQL version 9.4, which is not compatible with this version 9.5.3. LOCATION: ValidatePgVersion, miscinit.c:1364 pg_ctl: could not start server Examine the log output. Note: my data are in /db/pgsql/data --------------------------------------------- # postgresql-setup --upgrade * Upgrading database. ERROR: pg_upgrade tool failed ERROR: Upgrade failed. * See /var/lib/pgsql/upgrade_postgresql.log for detai ------------------------------------------ ------------------------------------ # cat /var/lib/pgsql/upgrade_postgresql.log -- connection to database failed: could not connect to server: No such file or directory Is the server running locally and accepting connections on Unix domain socket "/home/postgres/.s.PGSQL.5432"? could not connect to old postmaster started with the command: "/usr/lib64/pgsql/postgresql-9.4/bin/pg_ctl" -w -l "pg_upgrade_server.log" -D "/db/pgsql/data-old" -o "-p 5432 -b -c listen_addresses='' -c unix_socket_permissions=0700 -c unix_socket_directories='/home/postgres'" start Failure, exiting --------------------------------------------- What am I supposed to do now? It seems a trick would be to install last version 9.4.8 alongside, then run both 9.4.8 and 9.5 with my data for 9.4 and new empty data base for 9.5, then dump from older to new one db. Is it correct? Anyway to make postgresql-setup works ? Thank you for help google.com/+arnaudgabourygabx

2 1

← Newer
1
...
7
8
9
10
11
12
13
14
Older →

Jump to page: