fedaor 20 -> 22 Fail to start
by Patrick Dupre
hello,
After an update from fedora 20 to fedora 22, I get:
a started job is running for wait for plymouth boot screen to quit
It running for 15 mn!
It is probably a graphic issue.
Dell Inspiron 9400.
How can I fix it?
Thank.
===========================================================================
Patrick DUPRÉ | | email: pdupre(a)gmx.com
Laboratoire de Physico-Chimie de l'Atmosphère | |
Université du Littoral-Côte d'Opale | |
Tel. (33)-(0)3 28 23 76 12 | | Fax: 03 28 65 82 44
189A, avenue Maurice Schumann | | 59140 Dunkerque, France
===========================================================================
8 years, 9 months
clean previous fedora
by Patrick Dupre
Hello,
I can still some packages in the /var/cache/yum
form previous versions (19)
How can I clean these packages?
Thank.
===========================================================================
Patrick DUPRÉ | | email: pdupre(a)gmx.com
Laboratoire de Physico-Chimie de l'Atmosphère | |
Université du Littoral-Côte d'Opale | |
Tel. (33)-(0)3 28 23 76 12 | | Fax: 03 28 65 82 44
189A, avenue Maurice Schumann | | 59140 Dunkerque, France
===========================================================================
8 years, 9 months
fedup 20 -> 21 -> 22 -> Plasma closed unexpectedly
by Rich Emberson
Also see MTRR issue below.
On 07/25/2015 07:01 PM, Ed Greshko wrote:
You're a KDE user and quite a bit has changed. One question and one
suggestion....
Q. Just for information... Are you using kdm or sddm as your display
manager?
How does one find which display manager is being used?
Suggestion....
After reboot, login from a different machine and create a fresh user. Then
login as that new user to see if you have the same issue.
New in "xinit" output:
START
...
(==) Using config directory: "/etc/X11/xorg.conf.d"
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
error setting MTRR (base = 0xfb000000, size = 0x00e00000, type = 1) Invalid
argument (22)
Failed to close file descriptor: Could not close fd 11
Failed to close file descriptor: Could not close fd 11
...
END
Contents of /proc/mtrr
START
reg00: base=0x000000000 ( 0MB), size= 4096MB, count=1: write-back
reg01: base=0x100000000 ( 4096MB), size= 1024MB, count=1: write-back
reg02: base=0x0c0000000 ( 3072MB), size= 1024MB, count=1: uncachable
END
What is MTRR?
I assume that the error is not a good-thing.
Also, curiously, when I switch to graphical mode
ln -sf /lib/systemd/system/graphical.target
/etc/systemd/system/default.target
and then reboot....
hoping to get the graphicial login ... just to see if I can
pick the desktop there...
after the reboot the system has been set back to the
multi-user.target
Thanks
Richard
8 years, 9 months
how to have ntp service started at boot time?
by François Patte
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Bonjour,
I want to have ntp service running on my machine, so I enabled this
service:
systemctl enable ntpd.service
systemctl start ntpd.service
But, every time I reboot my machine, ntp is dead....
systemctl status ntpd.service
● ntpd.service - Network Time Service
Loaded: loaded (/usr/lib/systemd/system/ntpd.service; enabled)
Active: inactive (dead)
How to have running automatically?
Thank you
- --
François Patte
UFR de mathématiques et informatique
Laboratoire CNRS MAP5, UMR 8145
Université Paris Descartes
45, rue des Saints Pères
F-75270 Paris Cedex 06
Tél. +33 (0)1 8394 5849
http://www.math-info.univ-paris5.fr/~patte
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iEYEARECAAYFAlW0808ACgkQdE6C2dhV2JVrWwCfdSytq2jgzTvqnXz/NGKHJXGL
qFAAn0LXLUIOLAozKLVBb4z158bFBtDV
=M0F2
-----END PGP SIGNATURE-----
8 years, 9 months
kernel-PAE-3.19.5-100.fc20.i686
by Patrick Dupre
Hello,
Where can I get the rpm package:
kernel-PAE-3.19.5-100.fc20.i686 ?
Thank
===========================================================================
Patrick DUPRÉ | | email: pdupre(a)gmx.com
Laboratoire de Physico-Chimie de l'Atmosphère | |
Université du Littoral-Côte d'Opale | |
Tel. (33)-(0)3 28 23 76 12 | | Fax: 03 28 65 82 44
189A, avenue Maurice Schumann | | 59140 Dunkerque, France
===========================================================================
8 years, 9 months
update breaks configs...
by François Patte
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Bonjour,
I updated my system (f21) yesterday and I lost some configurations in
my home directory...
1- xfce: I configured my desktop appearence to have only icons of
removable devices, when I plug an usb key/drive, or when I put a
CD/DVD in the tray. I have now only one choice: no icon at all or all
my home directory is displayed on the desktop...
2- thunderbird is now unable to open http links in firefox if I have
such a link in a mail... I went on mozilla config pages, but all what
is said does not work or does not exist (for instance a button to
click to make firefox my default browser...)
Who can help me?
Thank you.
- --
François Patte
UFR de mathématiques et informatique
Laboratoire CNRS MAP5, UMR 8145
Université Paris Descartes
45, rue des Saints Pères
F-75270 Paris Cedex 06
Tél. +33 (0)1 8394 5849
http://www.math-info.univ-paris5.fr/~patte
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iEYEARECAAYFAlW0s6MACgkQdE6C2dhV2JWUaACgsuuWOoYyTJtnF65PK1CdXJxC
BIMAnA5f1FhuSoRRGPhQbzR89bdoZ3+5
=+2qF
-----END PGP SIGNATURE-----
8 years, 9 months
Pinentry fails with gpg-agent and SSH
by Jimmy Thrasibule
Hello,
I'm running Fedora 22. I'm trying to setup GnuPG to have my SSH
connections authenticated using my PGP authentication subkey that is
located on my Yubikey Neo.
I have a systemd unit starting the gpg-agent as following:
/usr/bin/gpg-agent --homedir=%h/.gnupg --daemon --use-standard-socket
And I have enabled SSH support in the configuration:
enable-ssh-support
pinentry-program /usr/bin/pinentry-gtk
Other parts of the setup include adding the [keygrip][1] of my key to
the ~/.gnupg/sshcontrol file, adding my [public key][2] to the remote
host and declaring the [environment variables][3].
Globally looking at the various logs the setup wants to work, I can
see that SSH is finding the key but actually failing to sign with it.
If I look at the logs from gpg-agent, I can see that it is failing to
launch the pinentry program and therefore, no requesting for the PIN
code:
2015-07-22 23:23:28 gpg-agent[6758] DBG: error calling pinentry:
Ioctl() inappropriate for a device <Pinentry>
2015-07-22 23:23:28 gpg-agent[6758] DBG: chan_8 -> BYE
2015-07-22 23:23:28 gpg-agent[6758] DBG: chan_7 -> CAN
2015-07-22 23:23:28 gpg-agent[6758] DBG: chan_7 <- ERR 100663573
The IPC call was canceled <SCD>
2015-07-22 23:23:28 gpg-agent[6758] smartcard signing failed:
Ioctl() inappropriate for a device
2015-07-22 23:23:28 gpg-agent[6758] ssh sign request failed:
Ioctl() inappropriate for a device <Pinentry>
What we see here is that when used in combination with SSH, some ioctl
call is failing while calling pinentry. However if I run the
following:
$ echo "Test" | gpg2 -s
The PIN window is popping up and it's all working fine.
Can you help me understand what's going on with this setup and SSH?
[1]: https://lists.gnupg.org/pipermail/gnupg-users/2012-July/045059.html
[2]: https://lists.gnupg.org/pipermail/gnupg-users/2012-July/045115.html
[3]: https://www.gnupg.org/documentation/manuals/gnupg/Agent-Examples.html#Age...
___
Jimmy THRASIBULE <thrasibule.jimmy(a)gmail.com>
8 years, 9 months
bluetooth.service, F22 Xfce "Failed..."
by Frank Murphy
Anyone seeing the "Failed.." line after doing a status.
bz search on the failed line produced nothing.
So what does it mean..?
systemctl status bluetooth
systemd[1]: Starting Bluetooth service...
Jul 26 07:46:16 ...... bluetoothd[2544]: Bluetooth daemon 5.29
Jul 26 07:46:16 ...... systemd[1]: Started Bluetooth service.
Jul 26 07:46:16 ...... bluetoothd[2544]: Starting SDP server
Jul 26 07:46:16 ...... bluetoothd[2544]: Bluetooth management interface
1.10 initialized
Jul 26 07:46:16 ...... bluetoothd[2544]: Failed to
obtain handles for "Service Changed" characteristic
Jul 26 07:46:16 ...... bluetoothd[2544]: Endpoint registered:
sender=:1.45 path=/MediaEndpoint/A2DPSource
Jul 26 07:46:16 ...... bluetoothd[2544]: Endpoint registered:
sender=:1.45 path=/MediaEndpoint/A2DPSink
some further testing:
bluetoothctl
connect mymacaddress
Attempting to connect to mymacaddress
[CHG] Device mymacaddress Connected: yes
Failed to connect: org.bluez.Error.NotAvailable
[CHG] Device mymacaddress Connected: no
but: in xfce-terminal
obexfs -b mymacaddress /home/me/myphone/
It mounts audio & photo folders from phone.
___
Regards
Frank Murphy
8 years, 9 months
fedup 20 -> 21 -> 22 -> Plasma closed unexpectedly
by Rich Emberson
Again, fedora upgrades using fedup ...
Starting with Fedora 20, did
... stuff ...
> fedup --network 21 --product=nonproduct
... stuff ...
> fedup --network 22 --product=nonproduct
So, now rebooted and it started.
I have all my machines in multi-user mode just
in case there is an issue with X.
Now tried to start X ... and there was an issue.
X starts but there is no mouse control (pointer on screen
but the mouse does not move it) and after a minute or
less I get an widget stating that the Plasma desktop
closed unexpectedly.
I have to login from another machine to do a reboot.
rpm -qa --qf '%{NAME} %{VERSION}-%{RELEASE} %{ARCH}\n' | grep plasma
plasma-workspace 5.3.2-2.fc22 x86_64
plasma-nm-openswan 5.3.2-1.fc22 x86_64
plasma-nm-vpnc 5.3.2-1.fc22 x86_64
plasma-nm-openvpn 5.3.2-1.fc22 x86_64
plasma-milou 5.3.2-1.fc22 x86_64
plasma-breeze-common 5.3.2-1.fc22 noarch
plasma-breeze 5.3.2-1.fc22 x86_64
plasma-nm-openconnect 5.3.2-1.fc22 x86_64
kf5-plasma 5.11.0-1.fc22 x86_64
plasma-nm 5.3.2-1.fc22 x86_64
kdeplasma-addons 5.3.2-1.fc22 x86_64
plasma-desktop 5.3.2-3.fc22 x86_64
plasma-pk-updates 0.2-1.fc22 x86_64
kde-settings-plasma 22-11.fc22 noarch
plasma-nm-l2tp 5.3.2-1.fc22 x86_64
plasma-desktop-doc 5.3.2-3.fc22 noarch
plasma-nm-pptp 5.3.2-1.fc22 x86_64
plasma-systemsettings 5.3.2-1.fc22 x86_64
rpm -qa --qf '%{NAME} %{VERSION}-%{RELEASE} %{ARCH}\n' | grep kmod
akmod-nvidia-340xx 340.76-2.fc22.12 x86_64
kmod-libs 21-1.fc22 x86_64
akmods 0.5.3-2.fc22 noarch
kmodtool 1-23.fc22 noarch
kmod 21-1.fc22 x86_64
xorg-x11-drv-nvidia-340xx-kmodsrc 340.76-1.fc22 x86_64
As user (not root):
qdbus --system
:1.0
org.freedesktop.systemd1
:1.1
org.freedesktop.login1
:1.10
:1.15
:1.2
org.freedesktop.Avahi
:1.3
org.freedesktop.ModemManager1
:1.4
org.freedesktop.problems.daemon
:1.5
org.fedoraproject.FirewallD1
:1.6
com.redhat.ifcfgrh1
org.freedesktop.NetworkManager
:1.7
:1.8
org.freedesktop.PolicyKit1
org.freedesktop.DBus
dmesg | grep -i nouv
[ 0.000000] Command line: BOOT_IMAGE=/vmlinuz-4.0.8-300.fc22.x86_64
root=UUID=19fd15d5-0e5d-4019-bf06-4dac9744be1b ro
rd.luks.uuid=luks-2a80faec-d21d-4a06-80fe-ad5a445d8aa1
vconsole.font=latarcyrheb-sun16
rd.luks.uuid=luks-8597ed23-e47c-427d-834c-e2fc5ec21bd3 rhgb quiet
nouveau.modeset=0 rd.driver.blacklist=nouveau video=vesa:off
[ 0.000000] Kernel command line:
BOOT_IMAGE=/vmlinuz-4.0.8-300.fc22.x86_64
root=UUID=19fd15d5-0e5d-4019-bf06-4dac9744be1b ro
rd.luks.uuid=luks-2a80faec-d21d-4a06-80fe-ad5a445d8aa1
vconsole.font=latarcyrheb-sun16
rd.luks.uuid=luks-8597ed23-e47c-427d-834c-e2fc5ec21bd3 rhgb quiet
nouveau.modeset=0 rd.driver.blacklist=nouveau video=vesa:off
/sbin/lsmod |grep nouveau
<nothing returned>
I notice that there were some mail threads discussing
something like this but I could not find one this
the solution.
Thanks
Richard
8 years, 9 months