users November 2016

users@lists.fedoraproject.org

151 participants
154 discussions

X dies : glamor0: Failed to get GLSL version
by sean darcy 19 Nov '16

19 Nov '16

On F24, upgraded to today. I've just built a xeon E3-1245 V5 box , P530 graphics. X dies on startup. I've got the Mesa drivers installed. Any help appreciated, sean .................. [ 3439.054] (II) LoadModule: "glx" [ 3439.079] (II) Loading /usr/lib64/xorg/modules/extensions/libglx.so [ 3439.104] (II) Module glx: vendor="X.Org Foundation" [ 3439.104] compiled for 1.18.4, module version = 1.0.0 [ 3439.104] ABI class: X.Org Server Extension, version 9.0 [ 3439.104] (==) AIGLX enabled [ 3439.104] (==) Matched intel as autoconfigured driver 0 [ 3439.104] (==) Matched intel as autoconfigured driver 1 [ 3439.104] (==) Matched modesetting as autoconfigured driver 2 [ 3439.104] (==) Matched fbdev as autoconfigured driver 3 [ 3439.104] (==) Matched vesa as autoconfigured driver 4 [ 3439.104] (==) Assigned the driver to the xf86ConfigLayout [ 3439.104] (II) LoadModule: "intel" [ 3439.104] (II) Loading /usr/lib64/xorg/modules/drivers/intel_drv.so [ 3439.178] (II) Module intel: vendor="X.Org Foundation" [ 3439.178] compiled for 1.18.3, module version = 2.99.917 [ 3439.178] Module class: X.Org Video Driver [ 3439.178] ABI class: X.Org Video Driver, version 20.0 [ 3439.178] (II) LoadModule: "modesetting" [ 3439.178] (II) Loading /usr/lib64/xorg/modules/drivers/modesetting_drv.so [ 3439.203] (II) Module modesetting: vendor="X.Org Foundation" [ 3439.203] compiled for 1.18.4, module version = 1.18.4 [ 3439.203] Module class: X.Org Video Driver [ 3439.203] ABI class: X.Org Video Driver, version 20.0 [ 3439.203] (II) LoadModule: "fbdev" [ 3439.203] (II) Loading /usr/lib64/xorg/modules/drivers/fbdev_drv.so [ 3439.216] (II) Module fbdev: vendor="X.Org Foundation" [ 3439.216] compiled for 1.18.0, module version = 0.4.3 [ 3439.216] Module class: X.Org Video Driver [ 3439.216] ABI class: X.Org Video Driver, version 20.0 [ 3439.216] (II) LoadModule: "vesa" [ 3439.216] (II) Loading /usr/lib64/xorg/modules/drivers/vesa_drv.so [ 3439.225] (II) Module vesa: vendor="X.Org Foundation" [ 3439.226] compiled for 1.18.0, module version = 2.3.2 [ 3439.226] Module class: X.Org Video Driver [ 3439.226] ABI class: X.Org Video Driver, version 20.0 [ 3439.226] (II) intel: Driver for Intel(R) Integrated Graphics Chipsets: i810, i810-dc100, i810e, i815, i830M, 845G, 854, 852GM/855GM, 865G, 915G, E7221 (i915), 915GM, 945G, 945GM, 945GME, Pineview GM, Pineview G, 965G, G35, 965Q, 946GZ, 965GM, 965GME/GLE, G33, Q35, Q33, GM45, 4 Series, G45/G43, Q45/Q43, G41, B43 [ 3439.226] (II) intel: Driver for Intel(R) HD Graphics: 2000-6000 [ 3439.226] (II) intel: Driver for Intel(R) Iris(TM) Graphics: 5100, 6100 [ 3439.226] (II) intel: Driver for Intel(R) Iris(TM) Pro Graphics: 5200, 6200, P6300 ............ [ 3439.253] (II) Loading sub module "glamoregl" [ 3439.253] (II) LoadModule: "glamoregl" [ 3439.253] (II) Loading /usr/lib64/xorg/modules/libglamoregl.so [ 3439.284] (II) Module glamoregl: vendor="X.Org Foundation" [ 3439.284] compiled for 1.18.4, module version = 1.0.0 [ 3439.284] ABI class: X.Org ANSI C Emulation, version 0.4 [ 3439.284] (II) glamor: OpenGL accelerated X.org driver based. [ 3439.481] (II) glamor: EGL version 1.4 (DRI2): [ 3439.521] (II) modeset(0): glamor initialized ,,,,,,,,,,, [ 3439.616] (WW) glamor0: Failed to get GLSL version [ 3439.616] (EE) modeset(0): Failed to initialize glamor at ScreenInit() time. [ 3439.616] (EE) Fatal server error: [ 3439.616] (EE) AddScreen/ScreenInit failed for driver 0

1 0

Howto reduce the size of /tmp as tmpfs?
by Frédéric Bron 19 Nov '16

19 Nov '16

/tmp uses 8 Gb, that is half of my RAM. Then my RAM is fully occupied as soon as I open Plasma+Firefox+Thunderbird. But /tmp is used at 1% only. Can I reduce it to 4Gb? I do not see any entry in /etc/fstab (have F24). Thanks, Frédéric

6 9

fedup from 20 to 21
by luca paganotti 18 Nov '16

18 Nov '16

Hi, upgrading from fedora 20 to fedora 21 using fedup I encounter an error. I issue the following command and after downloading all the rpm files there is an upgrade test that fails in this way Upgrade test failed with the following problems: insufficient disk space: / needs 3.2G more free space fedup ERROR: Upgrade test failed. I don't know how to manage this problems, googling tells me to find two folders /var/tmp/fedora-release and /var/lib/fedora-release, to copy them in the home directory where I have enough space and make symbolic liks to these two folders. The problem are that I'm not able to find /var/tmp/fedora-release and /var/lib/fedora-release, I'm not able to locate where fedup has store the new F21 rpm files, and then I don't know how to free the fedup needed space 3.2 Gb. Thanks for any answer and sorry for my english.

7 16

md-raid1 + lvm
by Gour 18 Nov '16

18 Nov '16

Hello, I’m new Fedora (f25-beta) user considering to fully (after having Fedora on my netbook) migrate to Fedora. At the moment I run Debian (Sid) and have two hard disks: 1x1TB and 1x2TB (one old 1TB disk recently died) and have the following layout: sda: 1 - BIOS boot 2 - md-raid1 (root, xfs) 3 - md-raid1 (home, xfs) sdb: 1 - BIOS boot 2 - md-raid1 (root, xfs) 3 - md-raid1 (home, xfs) 4 - swap 5 - backup partition Now I’ve a feeling that, somehow, Fedora favours usage of LVM partitions…Otoh, I’ve been told that using LVM on top of RAID(1) might not be the best solution, so wonder whether you recommend to keep the same layout as on Debian or to put my raid-1 volumes in LVM containers? Another concern I have is in regard to separate /boot partition which I was not using on Linux for quite some time, but see that Fedora’s automatic layout does create it? Sincerely, Gour -- One who is able to withdraw his senses from sense objects, as the tortoise draws its limbs within the shell, is firmly fixed in perfect consciousness.

5 7

mailing list footers
by Tim 18 Nov '16

18 Nov '16

I've just noticed that the footers appended to each mail to this list no-longer have a webpage address to the mailing list WWW interface. I don't see one in the headers, either. -- Boilerplate: All mail to my mailbox is automatically deleted, there is no point trying to privately email me, I only get to see the messages posted to the mailing list. less is more when playing with your cat...

1 0

Touchpad Single Finger Scroll Not Working - Not Present
by EGO-II.1 18 Nov '16

18 Nov '16

So I've been delving into the touchpad thing a bit more now that I have a few days off. This is the output of libinput-list-devices: I'm assuming that since all the necessary features I'm looking for are listed as "N/A" then it means something is wrong? (Also because when I got to "Test Your Settings" the option for Two Finger Scrolling is set to OFF but there's STILL no single-finger scroll!...any help at all would be greatly appreciated! Thanks! EGO II [root@jaunt-2019]# libinput-list-devices Device: Power Button Kernel: /dev/input/event2 Group: 1 Seat: seat0, default Capabilities: keyboard Tap-to-click: n/a Tap-and-drag: n/a Tap drag lock: n/a Left-handed: n/a Nat.scrolling: n/a Middle emulation: n/a Calibration: n/a Scroll methods: none Click methods: none Disable-w-typing: n/a Accel profiles: n/a Rotation: n/a Device: Video Bus Kernel: /dev/input/event6 Group: 2 Seat: seat0, default Capabilities: keyboard Tap-to-click: n/a Tap-and-drag: n/a Tap drag lock: n/a Left-handed: n/a Nat.scrolling: n/a Middle emulation: n/a Calibration: n/a Scroll methods: none Click methods: none Disable-w-typing: n/a Accel profiles: n/a Rotation: n/a Device: Sleep Button Kernel: /dev/input/event1 Group: 3 Seat: seat0, default Capabilities: keyboard Tap-to-click: n/a Tap-and-drag: n/a Tap drag lock: n/a Left-handed: n/a Nat.scrolling: n/a Middle emulation: n/a Calibration: n/a Scroll methods: none Click methods: none Disable-w-typing: n/a Accel profiles: n/a Rotation: n/a Device: Integrated Camera Kernel: /dev/input/event15 Group: 4 Seat: seat0, default Capabilities: keyboard Tap-to-click: n/a Tap-and-drag: n/a Tap drag lock: n/a Left-handed: n/a Nat.scrolling: n/a Middle emulation: n/a Calibration: n/a Scroll methods: none Click methods: none Disable-w-typing: n/a Accel profiles: n/a Rotation: n/a Device: AT Translated Set 2 keyboard Kernel: /dev/input/event3 Group: 5 Seat: seat0, default Capabilities: keyboard Tap-to-click: n/a Tap-and-drag: n/a Tap drag lock: n/a Left-handed: n/a Nat.scrolling: n/a Middle emulation: n/a Calibration: n/a Scroll methods: none Click methods: none Disable-w-typing: n/a Accel profiles: n/a Rotation: n/a Device: SynPS/2 Synaptics TouchPad Kernel: /dev/input/event4 Group: 6 Seat: seat0, default Size: 58.88x32.50mm Capabilities: pointer Tap-to-click: disabled Tap-and-drag: enabled Tap drag lock: disabled Left-handed: disabled Nat.scrolling: disabled Middle emulation: n/a Calibration: n/a Scroll methods: *two-finger edge Click methods: none Disable-w-typing: enabled Accel profiles: none Rotation: n/a Device: TPPS/2 IBM TrackPoint Kernel: /dev/input/event5 Group: 7 Seat: seat0, default Capabilities: pointer Tap-to-click: n/a Tap-and-drag: n/a Tap drag lock: n/a Left-handed: disabled Nat.scrolling: disabled Middle emulation: disabled Calibration: n/a Scroll methods: *button Click methods: none Disable-w-typing: n/a Accel profiles: flat *adaptive Rotation: n/a Device: ThinkPad Extra Buttons Kernel: /dev/input/event7 Group: 8 Seat: seat0, default Capabilities: keyboard Tap-to-click: n/a Tap-and-drag: n/a Tap drag lock: n/a Left-handed: n/a Nat.scrolling: n/a Middle emulation: n/a Calibration: n/a Scroll methods: none Click methods: none Disable-w-typing: n/a Accel profiles: n/a Rotation: n/a [root@jaunt-2019]#

5 7

Installer abort after download problem
by christophm30＠gmail.com 18 Nov '16

18 Nov '16

Hi Fedora user list, I am trying to install Fedora 24 for aarch64 in a virtual environment on my amd64 notebook. Unfortunately the installer aborts as it cannot download a package. I am starting the installer with this command: sudo virt-install --name Fedora_24_AArch64 --ram 4096 --arch aarch64 --vcpus 2 --network bridge=virbr0 --disk path=./Fedora_24_AArch64.img,format=raw,size=8 --os-variant fedora22 --graphics none --location https://dl.fedoraproject.org/pub/fedora-secondary/releases/24/Server/aarch6… After configuring the installation the installer starts downloading packages, however at one point a download fails and the installation is aborted (see log output below). I've tried two attempts so far and both got aborted. Further I did not notice any problems with the internet connection. And the failed package can be downloaded without any problems from my notebook. Does anyone know a way to circumvent this problem (e.g. forcing the installer to retry a failed download)? Thanks, Christoph Here is the installation log: [...] Starting package installation process Downloading packages Downloading 484 RPMs, 0 B / 237.99 MiB (0%) done. Downloading 484 RPMs, 0 B / 237.99 MiB (0%) done. Downloading 484 RPMs, 0 B / 237.99 MiB (0%) done. Downloading 484 RPMs, 0 B / 237.99 MiB (0%) done. Downloading 484 RPMs, 538.16 KiB / 237.99 MiB (0%) done. Downloading 484 RPMs, 2.07 MiB / 237.99 MiB (0%) done. Downloading 484 RPMs, 3.95 MiB / 237.99 MiB (1%) done. [...] Downloading 484 RPMs, 163.68 MiB / 237.99 MiB (68%) done. Downloading 484 RPMs, 163.69 MiB / 237.99 MiB (68%) done. Downloading 484 RPMs, 163.94 MiB / 237.99 MiB (68%) done. Downloading 484 RPMs, 164.04 MiB / 237.99 MiB (68%) done. Downloading 484 RPMs, 164.04 MiB / 237.99 MiB (68%) done. ================================================================================ ================================================================================ Error The following error occurred while installing. This is a fatal error and instal lation will be aborted. Failed to download the following packages: Cannot download Packages/r/rolekit-0. 5.1-1.fc24.noarch.rpm: All mirrors were tried Press Enter to exit.

1 1

USB3 Type C -
by Bob Goodwin 17 Nov '16

17 Nov '16

I installed a new MSI mainboard about a month ago that has four USB3 connectors on the back panel that accept nothing I have on hand. Apparently it is known as a "type C" connector. How do I deal with this? Googling has not produced much useful information, I may not have used the right keywords, but I would like to adapt them to the old style conventional connectors on my flash drives, cables, etc. I know this is not strictly a Fedora problem but it is a problem in using my Fedora systems when I can't connect to then. I was not aware of the difference before I bought the board, would appreciate information on how others have dealt with this.. Bob// -- Bob Goodwin - Zuni, Virginia, USA http://www.qrz.com/db/W2BOD box10 FEDORA-25b/64bit LINUX XFCE Fastmail POP3

12 18

evolution tweaks ?
by DJ Delorie 17 Nov '16

17 Nov '16

Just upgraded to F24 and there are a few things about Evolution I don't like... 1. the left-hand calendar pane uses white-on-blue for the "shown" days, as well as the weekday-name rows. How do I change the colors? 2. The "Select Today" button scrolls the big month view window to the start of the current month. How do I make it scroll to the start of the current week instead? I have no need to see what's already happened, but it used to show me the 4-5 upcoming weeks. 3. Scroll wheel in the calendar side pane scrolls the months, but leaves the selection in the same place on the screen - effectively scrolling the months in the big pane. How do I get it to leave the big pane alone until I click on a date? Or at least leave it alone until its 'selection' would bump off the top/bottom of the side pane? (i.e. I want to see the next 4 weeks in the big window, and the next 4 months in the side window).

2 1

getting eclipse-TestNG to work on Fedora 23
by perryh＠pluto.rain.com 17 Nov '16

17 Nov '16

On Fedora 23 with Eclipse and TestNG I am getting an error whenever I try to run a TestNG class. The entire system was updated (using yum (DNF) extender) within the last 24 hours; versions of (what I think are) relevant packages are: eclipse-filesystem 1.0-5.fc23, eclipse-jdt 4.5.2-10.fc23, eclipse-platform 4.5.2-10.fc23, eclipse-testng 6.8.6-6.fc23, testng 6.8.21-2.fc23 Minimal test case (to reproduce): Starting with a completely new workspace: File > New > Project > Java Project enter name "Trivial" Finish Click Yes in the "Open Associated Perspective?" dialog File > New > Package enter name "com.testng.minimalDemo" Finish Right-click "com.testng.minimalDemo" under Trivial/src in Package Explorer Select TestNG > Create TestNG class Select all entries in Annotations Finish This created NewTest.java, which had multiple errors flagged; the first was "The import org.testng cannot be resolved" Applying the first Quick Fix "Add TestNG library" cleared all of those errors, but then Run > Run As > TestNG Test paused for a few seconds and displayed an error box: Couldn't launch TestNG Couldn't contact the RemoteTestNG client. Make sure you don't have an older version of testng.jar on your class path. Reason: Timeout while trying to contact RemoteTestNG I don't have an older version of testng.jar anywhere -- only the one installed by eclipse-testng 6.8.6-6.fc23. The console shows: Error: A JNI error has occurred, please check your installation and try again Exception in thread "main" java.lang.NoClassDefFoundError: com/beust/jcommander/ParameterException at java.lang.Class.getDeclaredMethods0(Native Method) at java.lang.Class.privateGetDeclaredMethods(Class.java:2701) at java.lang.Class.privateGetMethodRecursive(Class.java:3048) at java.lang.Class.getMethod0(Class.java:3018) at java.lang.Class.getMethod(Class.java:1784) at sun.launcher.LauncherHelper.validateMainClass(LauncherHelper.java:544) at sun.launcher.LauncherHelper.checkAndLoadMain(LauncherHelper.java:526) Caused by: java.lang.ClassNotFoundException: com.beust.jcommander.ParameterException at java.net.URLClassLoader.findClass(URLClassLoader.java:381) at java.lang.ClassLoader.loadClass(ClassLoader.java:424) at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331) at java.lang.ClassLoader.loadClass(ClassLoader.java:357) ... 7 more So it seems there are (at least) two bugs in TestNG, and/or in its eclipse plugin, and/or in its Fedora packaging: 1. Clicking Finish in the Create TestNG class dialog should have added the TestNG library to the project if not already there. I should not have had to add it manually. 2. Something in the eclipse-testng plugin should have taken care of whatever additional configuration is needed to avoid that "JNI error". How do I get past this?

1 0

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

Jump to page: