users July 2015

users@lists.fedoraproject.org

158 participants
187 discussions

fedup 20 -> 21 -> xinit -> KDE -> No mouse/keyboard input
by Rich Emberson 26 Jul '15

26 Jul '15

So, I am now at the point where xinit (calling startkde) has the KDE screen appearing, but ... The pointer-cursor appears but can not be moved by the mouse, and (after some timeout and the login screen appears) keyboard entry fails. What does one do to enable both the mouse and keyboard. Thanks Richard

1 0

fedup 20 -> 21 -> xinit -> error setting MTRR
by Rich Emberson 26 Jul '15

26 Jul '15

What is causing the MTRR error in the xinit output? cat /proc/mtrr 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 Part of xinit output with a number of errors. The MTRR error is the first one: START xinit output .... (==) Log file: "/var/log/Xorg.0.log", Time: Sun Jul 26 11:27:32 2015 (==) 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 startkde: Starting up... Qt: Session management error: networkIdsList argument is NULL Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString) Qt: Session management error: networkIdsList argument is NULL kbuildsycoca5 running... kf5.kded: kded module "proxyscout" has already been found using JSON metadata, please don't install the now unneeded .desktop file ("kded/proxyscout.desktop"). kf5.kded: found kded module "statusnotifierwatcher" by prepending 'kded_' to the library path, please fix your metadata. .... powerdevil: No outputs have backlight property "/home/emberson/.local/share/icc/.." is not an ICC profile "/home/emberson/.local/share/icc/." is not an ICC profile Qt: Session management error: networkIdsList argument is NULL Service started, version: 6.2.0 QDBusConnection: name 'org.freedesktop.UDisks2' had owner '' but we thought it was ':1.27' Unable to get EDID for output "default" QDBusConnection: name 'org.kde.kglobalaccel' had owner '' but we thought it was ':1.9' Failed to create ICC profile on cmsCreateRGBProfile .... Qt: Session management error: networkIdsList argument is NULL Xlib: extension "GLX" missing on display ":0". .... Could not initialize GLX KCrash: Application 'krunner' crashing... KCrash: Attempting to start /usr/libexec/drkonqi from kdeinit Invalid service name "/org/kde/polkit-kde-authentication-agent-1" using: "/org/kde/polkitkdeauthenticationagent1" kcminit not running? If we are running with mobile profile or in another platform other than X11 this is normal. .... kwin_core: screens: 1 desktops: 1 kwin_core: Done. kwin_core: screens: 1 desktops: 1 kwin_core: Done. Invalid pixmap specified. .... kf5.kded: found kded module "touchpad" by prepending 'kded_' to the library path, please fix your metadata. Xlib: extension "GLX" missing on display ":0". kmix: kmixd: Delayed initialization running now kmix: kmixd: Delayed initialization done Xlib: extension "GLX" missing on display ":0". .... Application::crashHandler() called with signal 6; recent crashes: 1 KXMLGUI file found at deprecated location ("/usr/share/kmix/kmixui.rc") -- please use ${KXMLGUI_INSTALL_DIR} to install this file instead. .... END xinit output >From /var/log/X.org.0: Why attempt to load nouveau and nv ? Can not determine screen size. START log [ 109.258] (II) "glx" will be loaded by default. [ 109.258] (II) LoadModule: "glx" [ 109.278] (II) Loading /usr/lib64/nvidia-340xx/xorg/libglx.so [ 110.766] (II) Module glx: vendor="NVIDIA Corporation" [ 110.767] compiled for 4.0.2, module version = 1.0.0 [ 110.767] Module class: X.Org Server Extension [ 110.771] (II) NVIDIA GLX Module 340.76 Thu Jan 22 11:24:42 PST 2015 [ 110.785] (==) Matched nouveau as autoconfigured driver 0 [ 110.785] (==) Matched nv as autoconfigured driver 1 [ 110.785] (==) Matched modesetting as autoconfigured driver 2 [ 110.785] (==) Matched fbdev as autoconfigured driver 3 [ 110.785] (==) Matched vesa as autoconfigured driver 4 [ 110.785] (==) Assigned the driver to the xf86ConfigLayout [ 110.785] (II) LoadModule: "nouveau" [ 110.820] (WW) Warning, couldn't open module nouveau [ 110.820] (II) UnloadModule: "nouveau" [ 110.820] (II) Unloading nouveau [ 110.820] (EE) Failed to load module "nouveau" (module does not exist, 0) [ 110.820] (II) LoadModule: "nv" [ 110.821] (WW) Warning, couldn't open module nv [ 110.821] (II) UnloadModule: "nv" [ 110.821] (II) Unloading nv [ 110.821] (EE) Failed to load module "nv" (module does not exist, 0) [ 110.821] (II) LoadModule: "modesetting" [ 110.821] (II) Loading /usr/lib64/xorg/modules/drivers/modesetting_drv.so [ 110.828] (II) Module modesetting: vendor="X.Org Foundation" [ 110.828] compiled for 1.17.2, module version = 1.17.2 [ 110.828] Module class: X.Org Video Driver [ 110.828] ABI class: X.Org Video Driver, version 19.0 [ 110.828] (II) LoadModule: "fbdev" [ 110.828] (II) Loading /usr/lib64/xorg/modules/drivers/fbdev_drv.so[ 110.838] (II) Module fbdev: vendor="X.Org Foundation" [ 110.838] compiled for 1.17.1, module version = 0.4.3 [ 110.838] Module class: X.Org Video Driver [ 110.838] ABI class: X.Org Video Driver, version 19.0 [ 110.838] (II) LoadModule: "vesa" [ 110.838] (II) Loading /usr/lib64/xorg/modules/drivers/vesa_drv.so [ 110.847] (II) Module vesa: vendor="X.Org Foundation" [ 110.847] compiled for 1.17.1, module version = 2.3.2 [ 110.847] Module class: X.Org Video Driver [ 110.847] ABI class: X.Org Video Driver, version 19.0 [ 110.847] (II) modesetting: Driver for Modesetting Kernel Drivers: kms [ 110.847] (II) FBDEV: driver for framebuffer: fbdev [ 110.847] (II) VESA: driver for VESA chipsets: vesa [ 110.847] (--) using VT number 2 [ 110.853] (EE) open /dev/dri/card0: No such file or directory [ 110.853] (WW) Falling back to old probe method for modesetting [ 110.853] (EE) open /dev/dri/card0: No such file or directory [ 110.853] (II) Loading sub module "fbdevhw" [ 110.853] (II) LoadModule: "fbdevhw" [ 110.853] (II) Loading /usr/lib64/xorg/modules/libfbdevhw.so [ 110.869] (II) Module fbdevhw: vendor="X.Org Foundation" [ 110.869] compiled for 1.17.2, module version = 0.0.2 [ 110.869] ABI class: X.Org Video Driver, version 19.0 [ 110.869] (EE) open /dev/fb0: No such file or directory [ 110.869] (WW) Falling back to old probe method for fbdev [ 110.869] (II) Loading sub module "fbdevhw" [ 110.869] (II) LoadModule: "fbdevhw" [ 110.869] (II) Loading /usr/lib64/xorg/modules/libfbdevhw.so [ 110.869] (II) Module fbdevhw: vendor="X.Org Foundation" [ 110.869] compiled for 1.17.2, module version = 0.0.2 [ 110.869] ABI class: X.Org Video Driver, version 19.0 [ 110.869] (EE) open /dev/fb0: No such file or directory [ 110.869] (EE) Screen 0 deleted because of no matching config section. [ 110.869] (II) UnloadModule: "modesetting" [ 110.869] (EE) Screen 0 deleted because of no matching config section. [ 110.869] (II) UnloadModule: "modesetting" [ 110.869] (EE) Screen 0 deleted because of no matching config section. [ 110.869] (II) UnloadModule: "fbdev" [ 110.869] (II) UnloadSubModule: "fbdevhw" [ 110.869] (II) Loading sub module "vbe" [ 110.869] (II) LoadModule: "vbe" [ 110.869] (II) Loading /usr/lib64/xorg/modules/libvbe.so [ 110.880] (II) Module vbe: vendor="X.Org Foundation" [ 110.880] compiled for 1.17.2, module version = 1.1.0 [ 110.880] ABI class: X.Org Video Driver, version 19.0 [ 110.880] (II) Loading sub module "int10" [ 110.880] (II) LoadModule: "int10" .... [ 111.491] (II) VESA(0): Total Memory: 224 64KB banks (14336kB) [ 111.491] (II) VESA(0): <default monitor>: Using default hsync range of 31.50-48.00 kHz [ 111.491] (II) VESA(0): <default monitor>: Using default vrefresh range of 50.00-70.00 Hz [ 111.491] (II) VESA(0): <default monitor>: Using default maximum pixel clock of 65.00 MHz [ 111.491] (WW) VESA(0): Unable to estimate virtual size [ 111.491] (II) VESA(0): Not using built-in mode "1680x1050" (no mode of this name) [ 111.491] (II) VESA(0): Not using built-in mode "1280x1024" (no mode of this name) [ 111.491] (II) VESA(0): Not using built-in mode "1280x800" (no mode of this name) [ 111.491] (II) VESA(0): Not using built-in mode "1280x720" (no mode of this name) [ 111.491] (II) VESA(0): Not using built-in mode "1024x768" (no mode of this name) [ 111.491] (II) VESA(0): Not using built-in mode "800x600" (no mode of this name) [ 111.491] (II) VESA(0): Not using built-in mode "640x480" (no mode of this name) [ 111.491] (II) VESA(0): Not using built-in mode "640x400" (no mode of this name) [ 111.491] (II) VESA(0): Not using built-in mode "320x400" (no mode of this name) [ 111.491] (II) VESA(0): Not using built-in mode "320x240" (no mode of this name) [ 111.491] (II) VESA(0): Not using built-in mode "320x200" (no mode of this name) [ 111.491] (WW) VESA(0): No valid modes left. Trying less strict filter... [ 111.491] (II) VESA(0): <default monitor>: Using hsync range of 31.50-48.00 kHz [ 111.491] (II) VESA(0): <default monitor>: Using vrefresh range of 50.00-70.00 Hz [ 111.491] (II) VESA(0): <default monitor>: Using maximum pixel clock of 65.00 MHz [ 111.491] (WW) VESA(0): Unable to estimate virtual size [ 111.491] (II) VESA(0): Not using built-in mode "1680x1050" (hsync out of range) [ 111.491] (II) VESA(0): Not using built-in mode "1280x1024" (hsync out of range) [ 111.491] (II) VESA(0): Not using built-in mode "1280x800" (hsync out of range) [ 111.491] (II) VESA(0): Not using built-in mode "640x400" (hsync out of range) [ 111.491] (II) VESA(0): Not using built-in mode "320x400" (hsync out of range) [ 111.491] (II) VESA(0): Not using built-in mode "320x240" (illegal horizontal timings) [ 111.491] (II) VESA(0): Not using built-in mode "320x200" (illegal horizontal timings) [ 111.491] (--) VESA(0): Virtual size is 1280x768 (pitch 1280) [ 111.491] (**) VESA(0): *Built-in mode "1280x720" [ 111.491] (**) VESA(0): *Built-in mode "1024x768" [ 111.491] (**) VESA(0): *Built-in mode "800x600" [ 111.491] (**) VESA(0): *Built-in mode "640x480" [ 111.491] (==) VESA(0): DPI set to (96, 96) [ 111.491] (II) VESA(0): Attempting to use 60Hz refresh for mode "1024x768" (118) [ 111.492] (II) VESA(0): Attempting to use 60Hz refresh for mode "800x600" (115) [ 111.492] (II) VESA(0): Attempting to use 60Hz refresh for mode "640x480" (112) [ 111.493] (**) VESA(0): Using "Shadow Framebuffer" [ 111.493] (II) Loading sub module "shadow" [ 111.493] (II) LoadModule: "shadow" [ 111.493] (II) Loading /usr/lib64/xorg/modules/libshadow.so [ 111.539] (II) Module shadow: vendor="X.Org Foundation" [ 111.539] compiled for 1.17.2, module version = 1.1.0 [ 111.539] ABI class: X.Org ANSI C Emulation, version 0.4 [ 111.539] (II) Loading sub module "fb" [ 111.539] (II) LoadModule: "fb" [ 111.539] (II) Loading /usr/lib64/xorg/modules/libfb.so [ 111.549] (II) Module fb: vendor="X.Org Foundation" [ 111.549] compiled for 1.17.2, module version = 1.0.0 [ 111.549] ABI class: X.Org ANSI C Emulation, version 0.4 [ 111.549] (==) Depth 24 pixmap format is 32 bpp [ 111.549] (II) Loading sub module "int10" [ 111.549] (II) LoadModule: "int10" [ 111.549] (II) Loading /usr/lib64/xorg/modules/libint10.so [ 111.549] (II) Module int10: vendor="X.Org Foundation" [ 111.549] compiled for 1.17.2, module version = 1.0.0 .... END log This happens with kdm mananger enabled. Thanks Richard

1 0

fedaor 20 -> 22 Fail to start
by Patrick Dupre 26 Jul '15

26 Jul '15

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 ===========================================================================

3 6

clean previous fedora
by Patrick Dupre 26 Jul '15

26 Jul '15

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 ===========================================================================

3 2

fedup 20 -> 21 -> 22 -> Plasma closed unexpectedly
by Rich Emberson 26 Jul '15

26 Jul '15

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

1 0

how to have ntp service started at boot time?
by François Patte 26 Jul '15

26 Jul '15

-----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-----

5 4

kernel-PAE-3.19.5-100.fc20.i686
by Patrick Dupre 26 Jul '15

26 Jul '15

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 ===========================================================================

2 1

update breaks configs...
by François Patte 26 Jul '15

26 Jul '15

-----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-----

1 0

Pinentry fails with gpg-agent and SSH
by Jimmy Thrasibule 26 Jul '15

26 Jul '15

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#Agent… ___ Jimmy THRASIBULE <thrasibule.jimmy(a)gmail.com>

1 1

bluetooth.service, F22 Xfce "Failed..."
by Frank Murphy 26 Jul '15

26 Jul '15

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

1 0

← Newer
1
2
3
4
5
6
7
8
9
...
19
Older →

Jump to page: