users December 2017

users@lists.fedoraproject.org

106 participants
85 discussions

Usb stick or disk only read from nautilus
by Antonio M 15 Dec '17

15 Dec '17

Suddenly after last updates any usb stick is only real on my sistems but I can access them from terminal (writing is allowed) .Any idea??

5 9

F27: Gnome network control panel: "Automatically connect to VPN when ..." disappeared
by Dario Lesca 15 Dec '17

15 Dec '17

Into new F27 Gnome Network control panel the function "Automatically connect to VPN when ..." is disappeared. Now I must use "nm-connection-editor" for setup this option (see image) I must fill a bug or this useful function it's moved to another place? Thanks -- Dario Lesca (inviato dal mio Linux Fedora 27 Workstation)

2 2

Questions about Webalizer
by Cristian Sava 13 Dec '17

13 Dec '17

Hi all, I have some problems with Webalizer: 1) It can be manually started but not with cron. 2) I have http and https on the same server and it refuse to show statistics for ssl_access_log I tried to add "LogFile /var/log/httpd/ssl_access_log" to /etc/webalizer.conf with no success (it seems to inspect but it does not update the statistics). I searched with Google but nothing worked for me. What am I missing? Thanks, C.Sava

5 5

Windows 10 update ate Fedora 25 boot info: EFI. LVM, LUKS, oh, my!
by Ted Roche 13 Dec '17

13 Dec '17

Booted into Windows 10 to start the annual TurboTax stuff, and it asked to do an update, as usual. It turned out the "Features Update" was an entirely new version of Windows 10, Fall Creator's Update update, or something. Rebooting to go back into Fedora 25, and the boot menu is gone, replaced with: grub> Trying to follow the clues at: https://fedoraproject.org/wiki/GRUB_2#Encountering_the_dreaded_GRUB_2_boot_… (This is a Dell Inspiron 5558, i5, 12 Gb RAM, 1TB HDD) I've done the following: determined the boot files are on (hd1,gpt6), booted an F25 live USB and found the LVM listed below. Fedora25 is installed in an LUKS-encrypted partition, and is managed with LVM, volgroup is 'fedora' and root is in LV root. I'm guessing on a couple of these settings and would welcome suggestions. Please forgive typos. grub>insmod xfs grub>insmod lvm grub>set root=(dev/fedora/root) grub>linuxefi (hd1,gpt6)/vmlinuz-4.13.16-100.fc255.x86_64 root=/dev/fedora/root ro quiet rhgb rd.luks.uuid=luks-95ed05-2b2b-40ef-8eca-95ca54cf22a7 rd.lvm.lv=root grub>initrdefi (hd1,gpt6)/initramfs-4.13.16-100.fc25.x86_64.img grub>boot I see the LUKS unlock dialog and type the proper password, it chugs along, and after a few I am back at the login screen. Whew! So, I am back up and running. Now, how can I preserve these settings so I never have to type these things again? The fedoraproject page above suggests: grub2-mkconfig -o /boot/grub2/grub.cfg and grub2-install --boot-directory=/boot /dev/sda Finally, my question: are these last two commands correct with all the variations of EFI, GPT, LVM, LUKS etc that is my configration? After all this, I'd really hate to write to the wrong place! -- Ted Roche Ted Roche & Associates, LLC http://www.tedroche.com

11 14

CACHE_ERROR on fedora27 with nouveau driver
by Alex 13 Dec '17

13 Dec '17

Hi, I have a fedora27 system with all updates applied and receiving the following kernel messages. When this happens, the Xwayland screen goes blank with just the mouse cursor in the center after entering the password at the lock screen that is displayed after some period of inactivity. Is this a kernel bug? Driver problem? Here is the video card info from lspci: 06:00.0 VGA compatible controller: NVIDIA Corporation GT218 [GeForce 8400 GS Rev. 3] (rev a2) (prog-if 00 [VGA controller]) I've run abrt-cli and it doesn't show any recent crash. Notice there's a few minutes of time difference between the first two lines and the remaining ones, so not sure if it's related. [Tue Dec 12 13:08:51 2017] nouveau 0000:06:00.0: fifo: DMA_PUSHER - ch 7 [Xwayland[8082]] get 0000000000 put 0000000000 ib_get 00000000 ib_put 00000002 state c0000000 (err: MEM_FAULT) push 00400040 [Tue Dec 12 13:08:51 2017] nouveau 0000:06:00.0: fb: trapped read at 0020010000 on channel 7 [3f4dc000 Xwayland[8082]] engine 05 [PFIFO] client 08 [PFIFO_READ] subclient 00 [PUSHBUF] reason 00000000 [PT_NOT_PRESENT] [Tue Dec 12 13:29:36 2017] nouveau 0000:06:00.0: fifo: CACHE_ERROR - ch 16 [systemd-logind[7733]] subc 5 mthd 0180 data beef0301 [Tue Dec 12 13:29:36 2017] nouveau 0000:06:00.0: fifo: CACHE_ERROR - ch 16 [systemd-logind[7733]] subc 5 mthd 0184 data beef0201 [Tue Dec 12 13:29:36 2017] nouveau 0000:06:00.0: fifo: CACHE_ERROR - ch 16 [systemd-logind[7733]] subc 5 mthd 0188 data beef0201 [Tue Dec 12 13:29:36 2017] nouveau 0000:06:00.0: fifo: CACHE_ERROR - ch 16 [systemd-logind[7733]] subc 4 mthd 0180 data beef0301 [Tue Dec 12 13:29:36 2017] nouveau 0000:06:00.0: fifo: CACHE_ERROR - ch 16 [systemd-logind[7733]] subc 4 mthd 0184 data beef0201 [Tue Dec 12 13:29:36 2017] nouveau 0000:06:00.0: fifo: CACHE_ERROR - ch 16 [systemd-logind[7733]] subc 4 mthd 0188 data beef0201 [Tue Dec 12 13:29:36 2017] nouveau 0000:06:00.0: fifo: CACHE_ERROR - ch 16 [systemd-logind[7733]] subc 4 mthd 018c data beef0201 [Tue Dec 12 13:29:36 2017] nouveau 0000:06:00.0: fifo: CACHE_ERROR - ch 16 [systemd-logind[7733]] subc 3 mthd 0180 data beef0301 [Tue Dec 12 13:29:36 2017] nouveau 0000:06:00.0: fifo: CACHE_ERROR - ch 16 [systemd-logind[7733]] subc 3 mthd 0184 data beef0201 [Tue Dec 12 13:29:36 2017] nouveau 0000:06:00.0: fifo: CACHE_ERROR - ch 16 [systemd-logind[7733]] subc 3 mthd 0188 data beef0201 [Tue Dec 12 13:29:36 2017] nouveau 0000:06:00.0: fifo: CACHE_ERROR - ch 16 [systemd-logind[7733]] subc 3 mthd 018c data beef0201 [Tue Dec 12 13:29:36 2017] nouveau 0000:06:00.0: fifo: CACHE_ERROR - ch 16 [systemd-logind[7733]] subc 3 mthd 0190 data beef0201 [Tue Dec 12 13:29:36 2017] nouveau 0000:06:00.0: fifo: CACHE_ERROR - ch 16 [systemd-logind[7733]] subc 3 mthd 0194 data beef0201 [Tue Dec 12 13:29:36 2017] nouveau 0000:06:00.0: fifo: CACHE_ERROR - ch 16 [systemd-logind[7733]] subc 3 mthd 0198 data beef0201 [Tue Dec 12 13:29:36 2017] nouveau 0000:06:00.0: fifo: CACHE_ERROR - ch 16 [systemd-logind[7733]] subc 3 mthd 019c data beef0201 [Tue Dec 12 13:29:36 2017] nouveau 0000:06:00.0: fifo: CACHE_ERROR - ch 16 [systemd-logind[7733]] subc 3 mthd 01a0 data beef0201 [Tue Dec 12 13:29:36 2017] nouveau 0000:06:00.0: fifo: CACHE_ERROR - ch 16 [systemd-logind[7733]] subc 3 mthd 01a4 data beef0201 [Tue Dec 12 13:29:36 2017] nouveau 0000:06:00.0: fifo: CACHE_ERROR - ch 16 [systemd-logind[7733]] subc 3 mthd 01a8 data beef0201 [Tue Dec 12 13:29:36 2017] nouveau 0000:06:00.0: fifo: CACHE_ERROR - ch 16 [systemd-logind[7733]] subc 3 mthd 01ac data beef0201 [Tue Dec 12 13:29:36 2017] nouveau 0000:06:00.0: fifo: CACHE_ERROR - ch 16 [systemd-logind[7733]] subc 3 mthd 01c0 data beef0201 [Tue Dec 12 13:29:36 2017] nouveau 0000:06:00.0: fifo: CACHE_ERROR - ch 16 [systemd-logind[7733]] subc 3 mthd 01c4 data beef0201 [Tue Dec 12 13:29:36 2017] nouveau 0000:06:00.0: fifo: CACHE_ERROR - ch 16 [systemd-logind[7733]] subc 3 mthd 01c8 data beef0201 [Tue Dec 12 13:29:36 2017] nouveau 0000:06:00.0: fifo: CACHE_ERROR - ch 16 [systemd-logind[7733]] subc 3 mthd 01cc data beef0201 [Tue Dec 12 13:29:36 2017] nouveau 0000:06:00.0: fifo: CACHE_ERROR - ch 16 [systemd-logind[7733]] subc 3 mthd 01d0 data beef0201 [Tue Dec 12 13:29:36 2017] nouveau 0000:06:00.0: fifo: CACHE_ERROR - ch 16 [systemd-logind[7733]] subc 3 mthd 01d4 data beef0201 [Tue Dec 12 13:29:36 2017] nouveau 0000:06:00.0: fifo: CACHE_ERROR - ch 16 [systemd-logind[7733]] subc 3 mthd 01d8 data beef0201 [Tue Dec 12 13:29:36 2017] nouveau 0000:06:00.0: fifo: CACHE_ERROR - ch 16 [systemd-logind[7733]] subc 3 mthd 01dc data beef0201 [Tue Dec 12 13:29:36 2017] nouveau 0000:06:00.0: gr: TRAP_CCACHE 00000001 [FAULT] [Tue Dec 12 13:29:36 2017] nouveau 0000:06:00.0: gr: TRAP_CCACHE 000e0080 00000000 00000000 00000000 00000000 00000004 00000000 [Tue Dec 12 13:29:36 2017] nouveau 0000:06:00.0: gr: 00200000 [] ch 16 [003e8b0000 systemd-logind[7733]] subc 3 class 8597 mthd 13bc data 00000054 [Tue Dec 12 13:29:36 2017] nouveau 0000:06:00.0: fb: trapped read at 002027df00 on channel 16 [3e8b0000 systemd-logind[7733]] engine 00 [PGRAPH] client 05 [CCACHE] subclient 00 [CB] reason 00000006 [NULL_DMAOBJ] [Tue Dec 12 13:29:38 2017] nouveau 0000:06:00.0: gr: PGRAPH TLB flush idle timeout fail [Tue Dec 12 13:29:38 2017] nouveau 0000:06:00.0: gr: PGRAPH_STATUS 00000403 [BUSY DISPATCH CCACHE_PREGEOM] [Tue Dec 12 13:29:38 2017] nouveau 0000:06:00.0: gr: PGRAPH_VSTATUS0: 00000008 [CCACHE] [Tue Dec 12 13:29:38 2017] nouveau 0000:06:00.0: gr: PGRAPH_VSTATUS1: 00000000 [] [Tue Dec 12 13:29:38 2017] nouveau 0000:06:00.0: gr: PGRAPH_VSTATUS2: 00000000 [] [Tue Dec 12 13:29:40 2017] nouveau 0000:06:00.0: gr: PGRAPH TLB flush idle timeout fail

2 2

is my filesystem damaged?
by Neal Becker 12 Dec '17

12 Dec '17

Since last boot, I've got this strange symptom. Filesystem is btrfs. If I list my home dir with dired under emacs I see: -rwxrwxr-x. 1 nbecker nbecker 207 Dec 3 2015 BACKUP.sh -?????????? ? ? ? ? ? .bash_history -?????????? ? ? ? ? ? .bash_history -?????????? ? ? ? ? ? .bash_history -?????????? ? ? ? ? ? .bash_history Attempt to list with ls gives: /usr/bin/ls: cannot access '/home/nbecker/./.bash_history': No such file or directory I think this means there is a directory entry, but the file doesn't exist? Any suggestion to most reliably repair the damage? I don't care about losing the content of this file.

8 19

Default video application
by Alex 12 Dec '17

12 Dec '17

Hi, I have a fedora27 system and having a problem with hdhomerun and video dropout with vlc/videolan. I'm hoping it's a problem that can be solved by choosing a different video player. I've set "Videos" to the default in Settings->Details->Default Applications, but hdhomerun_config_gui still spawns vlc when playing the stream. I've also changed the file associations in the System Settings->Applications->File Associations to use Videos before VLC and it also made no difference. I've also tried from within the Videos app itself, but there doesn't appear to be any type of configuration options there at all. The problem I'm having with hdhomerun has existed since at least fedora24 on this desktop. There's dropout on many broadcast channels and the following is printed repeatedly on the screen: [00007fb500015330] ts demux error: libdvbpsi error (PSI decoder): TS duplicate (received 0, expected 1) for PID 0 I've also tried to get support through the hdhomerun people and they have no idea what's causing it either. Thanks for any ideas

3 3

Powertop autostart on battery use?
by wgelpi＠redhat.com 12 Dec '17

12 Dec '17

Has anyone been successful in setting up powertop[1] to start when you switch from AC to Battery power? [1] https://fedoramagazine.org/saving-laptop-power-with-powertop/

1 0

ESC/P thermal receipt printers and Linux...
by Fernando Cassia 12 Dec '17

12 Dec '17

Running dmesg after plugging my POS-5890K labelled usb thermal receipt printer, it identifies itself as full-speed USB device number 9 using ehci-pci idVendor=0416, idProduct=5011 Mfr=1, Product=2, SerialNumber=3 Product: POS58 USB Printer Manufacturer: GD32 Microelectronics SerialNumber: Printer I found the hard way that these printers are not supported by CUPS by default ... one has to go the extra length to either send esc/p codes manually via your own app http://kg4zqz.blogspot.com/2016/08/escposf-thermal-printer-filter-and.html ...or compile a driver from source, just like 20 years ago for some printers... maybe 2018 will be the year of desktop linux *sarcasm* I've tried this driver and it didn't work... http://scruss.com/blog/2015/07/12/thermal-printer-driver-for-cups-linux-and… (the driver source was fetched by git from its current github repo, so it's not out of date, it's in fact newer than the above blog post) What gives more clues is the small piece of thermal paper that came with the printer with a printout of its self-test (surely from Windows). It reads: 58-IV-U Thermal Printer Version: 58.E-Z04-AA Revised date: 06-Jan-2017 Command Standard: EPSON (ESC/POS) Print mode: Normal mode & Hex Mode Print method: Line Thermal Print width: 384 dots/line Print speed: 90 mm/s Chinese Mode: NO Print density: Level3 Current Codepage:0 Interface Type: USB Current Character: Chinese (GB18030) Alphanumeric Code Page: 0: OEM437 (Std.Europe) 1: Katakana 2:OEM850 (Multilingual) (…) 96:(Thai2) I wonder why the CUPS folks have not released a generic “EPSON ESC/POS” printer driver where the above parameters can be tweaked and entered manually. The driver mentioned above was compiled, and installed but didn’t work. A sample print gave gibberish. A second text-only printing (by clicking the CUPS “print self-test page” read “IF YOU CAN READ THIS YOU’RE USING THE WRONG DRIVER FOR YOUR PRINTER”. A crude bug-finding code it seems… Any ideas before I head over to the CUPS maling list and pull my hair? For instance, this blog post https://mike42.me/blog/2015-03-getting-a-usb-receipt-printer-working-on-lin… talks about using "usblp" but commenters say "usblp" was deprecated (already in 2015) So what does replace usblp? And look, here someone else also pulling his hair. https://stackoverflow.com/questions/45926734/raw-cups-printer-how-to-avoid-… FFS, a line printer was the first type of printer, back in the days of RS232 ports. If we can't get a USB line printer detected and configured and send ASCII to it, we're doomed. All because there's a dozen poorly documented layers of software crap obscuring it... FC

2 1

Trying to solve the click of death issue
by Fulko Hew 11 Dec '17

11 Dec '17

I had to get a new laptop, and it came with a Toshiba MQ01ABD100 drive. To disable the Advanced Power Management and to stop the head unload/clicking I've always used: hdparm -B 255 /dev/sda But on this machine/drive, it doesn't seem to work; or at least it only works for a short while, and then it starts unloading again. More importantly, the next time I try to disable it,it says its disabled, but the drive carries on clicking, and the Load_Cycle_Count still keeps going up. Suggestions anyone? Fulko

4 10

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