users August 2015

users@lists.fedoraproject.org

161 participants
192 discussions

Q about Environment files of systemd
by JD 14 Aug '15

14 Aug '15

Just wondering why some values of EnvironmentFile variable in the services files are as follows (output of grep): /usr/lib/systemd/system/irda.service:EnvironmentFile=-/etc/sysconfig/irda /usr/lib/systemd/system/sshd.service:EnvironmentFile=/etc/sysconfig/sshd So, what's with the hyphen after = ?? What does it mean?

8 29

Asus UX303LA - fedora 21 - external monitor via mini display port not recognized
by CS DBA 13 Aug '15

13 Aug '15

All; I've installed Fedora 21 on an Asus UX303LA. Most everything works great but I cannot get it to recognize an external monitor via the mini display port. I checked dmesg and saw no change when I plug the monitor in. I also booted with the monitor plugged in but still no luck. Thoughts? Thanks in advance

1 0

F22 - Xfce monitor mirroring
by Robert Moskowitz 13 Aug '15

13 Aug '15

When I plug my external monitor in, the mirroring option is greyed out. This worked fine in F21. I DO have a challenge in that my Belkin KVM is only seems to be allowing 1024x768, eventhough the manual says it supports higher resolution. But this worked fine in F21. And even if I force the laptop panel to 1024x768, mirroring is still not available. Where might I find a control to fix this?

1 2

F22: KDE to Gnome?
by Rich Emberson 13 Aug '15

13 Aug '15

Upgraded from F20 KDE environment using fedup --network 22 --product=nonproduct and X/KDE has rendering/refresh/redraw issues. Application widgets and KDE pop menus are not draw, or, at best some edge or corner is drawn. In an xterm, the line being entered is drawn, but nothing else - move the window and the content disappears. System description at bottom. Information points: 1) With F20, KDE worked fine on this machine. 2) Upgraded KDE system has above rendering issues 3) Remotely logging into broken system and launching X application which displays on remote machine works just fine. 4) Booting from a F22 KDE Live dvd has *SAME* rendering issue. 5) Booting from a F22 Gnome Workstation Live dvd has *NO* rendering issues. Information point 2: Seems to imply that the X.org SW is working fine; the X protocol (X <-> app) is good. Information point 4: Yea, the F22 Workstation dvd seems to work. Question: Do the two Live dvds (KDE and Gnome) use the same nouveau driver? If the two dvds use the same nouveau driver, then it might be argued that its a KDE issue. The machine has a Nvidia graphics board, but it is not being used; was not used with F20 KDE and not being used for broken F22 KDE. So, if it is a KDE issue (on this particular machine) then what to do? In particular, it looks like on this machine I will be using Gnome or some other window manager but not KDE for F22. Options: 1) Attempt to use Nvidia graphics on broken F22 KDE machine. There are many sites that describe how to disable nouveau and enable Nvidia. But, 1) there does not seem to be a site specifically addressing what to do when using F22 and 2) the sites are not consistent (use rpmfusion vs Nvidia site for driver, what needs to be done to disable nouveau (grub/blacklist,...), etc.). Also, there is no guarantee that a KDE rendering issue will be fixed by switching to Nvidia card. 2) Attempt to install F22 Workstation on existing broken F22 KDE machine. If one uses the F22 Gnome Workstation dvd to "install to harddrive" will it allow you to select which disk to install on (my /home has already been backed up)? I assume this will set Gnome as the desktop into which the system boots. Or, is there some dnf command which will install the Workstation so that the system boots into Gnome. 3) Re-install F20 (KDE) and then upgrade to F22 Workstation. This is the most time consuming, but it appears to be rather straight forward. install F20 from dvd fedup --network 22 --product=workstation Question: Which option above is the most likely to succeed? Question: Once the system is working as F22 Gnome Workstation, can I then install and try out other window managers (e.g., xfce)? Advice sought. Thanks Richard System: > uname -a Linux olympia 4.1.3-201.fc22.x86_64 #1 SMP Wed Jul 29 19:50:22 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux hardware (board, cpu, Nvidia graphics board (not used), etc.) # /sbin/lshw -c display *-display description: VGA compatible controller product: G73 [GeForce 7300 GT] vendor: NVIDIA Corporation physical id: 0 bus info: pci at 0000:01:00.0 version: a1 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress vga_controller bus_master cap_listrom configuration: driver=nouveau latency=0 resources: irq:29 memory:fd000000-fdffffff memory:d0000000-dfffffff memory:fc000000-fcffffff ioport:bc00(size=128) memory:fe8e0000-fe8fffff Display driver > rpm -qa --qf '%{NAME} %{VERSION}-%{RELEASE} %{ARCH}\n' | grep nouv xorg-x11-drv-nouveau 1.0.11-2.fc22 x86_64 X.org software libX11 1.6.3-1.fc22 x86_64 xorg-x11-server-Xorg 1.17.2-2.fc22 x86_64 etc. Desktop (KDE, Gnome, etc.) kde-runtime-libs 15.04.2-1.fc22 x86_64 kde-runtime 15.04.2-1.fc22 x86_64 etc. Monitor Early on, I swapped out the monitor to a different one and still got the same problem

1 1

F22 Android phone access
by Robert Moskowitz 13 Aug '15

13 Aug '15

In F21, I attached my Samsung SG4 via USB (making sure it was unlocked) and waited. First it should mounting the Verizon Install CD, then this timed out and the phone was accessable. Now in F22 (with Xfce), after the Verizon Install CD, nothing. Perhaps there was something I installed on advise here, but I can't find any notes on it. Anyone have the magic goo for accessing your phone on F22?

2 2

A plea to users who report bugs
by Michael Schwendt 13 Aug '15

13 Aug '15

In many bugs reports, one can observe that the reporters don't tell - whether a problem is reproducible, - how often it occurs, - how to reproduce it (if known). In lots of other cases, bug reporters are completely silent and don't give any background details at all. They only let ABRT dump files into bugzilla. We -- the Fedora Community -- can do better than that. Everyone, *please* spend a few seconds on mentioning a few details, even if you only confirm that it has been a spontaneous crash that happened only once.

2 1

Moving Firefox settings from F21 to F22
by Robert Moskowitz 13 Aug '15

13 Aug '15

My cheat sheet that I used in going from F20 to F21 is not working on F21 to F22. To restore Firefox: ~/.mozilla/firefox/xxxxxxxx.default/ move: places.sqlite permissions.sqlite formhistory.sqlite cookies.sqlite cert8.db mimeTypes.rdf save-session: sessionstore.js =============== No sessionstore.js actually anymore in F21 to move. My bookmarks, history, etc. Do not seem to be moved. I cannot find any F22 help on this, and interestingly Firefox on my F21 is 39.0.0 and on F22 it is 39.0.3 (of course don't know what originally came with F21).

3 9

backup snapshot
by Diogene Laerce 13 Aug '15

13 Aug '15

Hi, After a sad experience with a system update, I would like to ask if there is a software on Fedora or more generally on Linux which would allow me to make a complete snapshot of the system ? Something as easy of use as the snapshot feature in VirtualBox would be great.. But near would do as well. Kind regards, -- “One original thought is worth a thousand mindless quotings.” “Le vrai n'est pas plus sûr que le probable.” Diogene Laerce

10 22

[Slightly OT] The Linux Vendor Firmware Project needs 15 minutes of your time
by Richard Hughes 13 Aug '15

13 Aug '15

Hi all, For the LVFS project, I need vendors making hardware to submit firmware files with carefully written metadata so that they can be downloaded in Fedora 23 securely and automatically. I also need those vendors to either use a standardized flashing protocol (e.g. DFU or UEFI) or to open the device specifications enough to allow flashing firmware without signing an NDA. Over the last couple of months I’ve been emailing various tech companies trying to get hold of the right people to implement this. So far the reaction from companies has been enthusiastic and apathetic in equal measures. I’ve had a few vendors testing the process, but I can’t share those names just yet as most companies have been testing with unreleased hardware. This is where you come in. On your Linux computer right now, think about what hardware you own that works in Linux that you know has user-flashable firmware? What about your BIOS, your mouse, or your USB3 hub? Your network card, your RAID card, or your video card? Things I want you to do: * Find the vendor on the internet, and either raise a support case or send an email. Try and find a technical contact, not just some sales or marketing person * Tell the vendor that you would like firmware updates when using Linux, and that you’re not able to update the firmware booting to Windows or OS-X * Tell the vendor that you’re more likely to buy from them again if firmware updates work on Linux * Inform the vendor about the LVFS project : https://beta-lvfs.rhcloud.com/ At all times I need you to be polite and courteous, after all we’re asking the vendor to spend time (money) on doing something extra for a small fraction of their userbase. Ignoring one email from me is easy, but getting tens or hundreds of support tickets about the same issue is a great way to get an issue escalated up to the people that can actually make changes. So please, spend 15 minutes opening a support ticket or sending an email to a vendor now. Happy to take questions or comments, thanks. Richard.

1 0

Does DNF use yum.repo.d?
by Robert Moskowitz 13 Aug '15

13 Aug '15

Where does dnf keep its repo configuration, or does it use /etc/yum.repo.d? Which I see is still there. As I want to change it to use my local repos.

3 3

← Newer
1
...
9
10
11
12
13
14
15
...
20
Older →

Jump to page: