users February 2015

users@lists.fedoraproject.org

139 participants
172 discussions

Moving old Thunderbird and Firefox in to new setup
by Mickey 05 Feb '15

05 Feb '15

Fedora 20 / KDE Moving old setting of Thunderbird and Firefox into a new setup of Fedora 20 KDE. Thunderbird: In new setup of thunderbird Send contents of the Mail folder to Trash Can. Thunderbird: Take contents of Old Thunderbird Mail folder , Copy and Drag into the new Mail Folder. Also move Abook from Old to New setup. Is this correct ? Firefox: Send places.sqlite in new Setup to Trash Can, Copy From old Firefox the places.sqlite and Drag into New Firefox Setup. For the Bookmarks. Is this Correct ? Well none of that is working in the User Setup of Fedora 20 / KDE

3 2

what is the process number of a "running application" ?
by Angelo Moreschini 05 Feb '15

05 Feb '15

Hi, I would like to know the process number of an application that actually is running (Netbeans in my case), with the purpose to kill it (when is froze). But am am not able to know this process number.. - In the window of gnome-system-monitor the name "netbeans" isn't. - The command line : "ps aux | grep netbeans", give me a full page of references.. Could I know a simple way to have this information ? Thank you Regards Angelo

10 11

Re: SOLVED mdadm: Cannot get exclusive access to /dev/md127
by Rich Emberson 04 Feb '15

04 Feb '15

Thanks for the help! cryptsetup luksClose luks-ab8911f9-b3a4-4f33-8b10-7e52c7217ae9 did the trick. Steps Remove entry from /etc/fstab # vi /etc/fstab then following sequence of commands: # lsof +d /raid1/ <nothing> # lsof +D /raid1/ <nothing> # df </raid1 does not show up> # mount </raid1 does not show up> # cryptsetup luksClose luks-ab8911f9-b3a4-4f33-8b10-7e52c7217ae9 <nothing> # cryptsetup luksClose luks-ab8911f9-b3a4-4f33-8b10-7e52c7217ae9 <Device luks-ab8911f9-b3a4-4f33-8b10-7e52c7217ae9 is not active.> # wipefs -a /dev/md127 <nothing> # mdadm -S /dev/md127 <nothing> # mdadm --misc --zero-superblock /dev/sdd1 <nothing> # mdadm --misc --zero-superblock /dev/sdc1 <nothing> # ls /raid1/ <nothing> # touch /raid1/foo <nothing> # ls /raid1/ <foo> # rm /raid1/foo # lsof +d /home <lots of entries> # lsof +d /raid1/ <nothing> # umount /raid1/ <nothing> # umount -f /raid1/ <nothing> # /bin/rm -rf /raid1/ <nothing> # lsof | grep md127 <nothing> Now fdisk, partprobe, mkfs.ext4, fsck, mkdir /mountpoint, mount for each disk that was part of the raid group. Again, thanks

1 0

Blocking POODLE
by Matthew Saltzman 04 Feb '15

04 Feb '15

SSLLabs reports a couple of servers of mine have SSL v3 enabled and are vulnerable to POODLE. I followed instructions for Apache httpd at https://scotthelme.co.uk/sslv3-goes-to-the-dogs-poodle-kills-off-protocol/, but that does not seem to cure the problem. SSLLabs still reports the servers as vulnerable. Does anyone know what I'm missing? The server also runs Trac and Subversion servers and a separate vhost runs Jenkins. Does something special need to be done for those services? (These are, in fact, RHEL 7 servers running httpd-2.2.15-39.el6.x86_64, but I hope someone here will know what's going on.) Thanks in advance. -- Matthew Saltzman Clemson University Math Sciences mjs AT clemson DOT edu

3 8

Fedora 21 shutting down after logging in?
by Richard Shaw 03 Feb '15

03 Feb '15

I'm troubleshooting some video problems with a used laptop I got for cheap. For the day is was pretty nice, Dell Latitude D620 with Nvidia Quadro graphics (the problem I'm troubleshooting). I was looking through the journal when I saw this shortly after logging in: Feb 03 17:47:15 localhost.localdomain systemd-logind[676]: Removed session c1. Feb 03 17:47:15 localhost.localdomain systemd[1364]: Stopping Default. Feb 03 17:47:15 localhost.localdomain systemd[1364]: Stopped target Default. Feb 03 17:47:15 localhost.localdomain systemd[1364]: Stopping Basic System. Feb 03 17:47:15 localhost.localdomain systemd[1364]: Stopped target Basic System. Feb 03 17:47:15 localhost.localdomain systemd[1364]: Stopping Paths. Feb 03 17:47:15 localhost.localdomain systemd[1364]: Stopped target Paths. Feb 03 17:47:15 localhost.localdomain systemd[1364]: Stopping Timers. Feb 03 17:47:15 localhost.localdomain systemd[1364]: Stopped target Timers. Feb 03 17:47:15 localhost.localdomain systemd[1364]: Stopping Sockets. Feb 03 17:47:15 localhost.localdomain systemd[1364]: Stopped target Sockets. Feb 03 17:47:15 localhost.localdomain systemd[1364]: Starting Shutdown. Feb 03 17:47:15 localhost.localdomain systemd[1364]: Reached target Shutdown. Feb 03 17:47:15 localhost.localdomain systemd[1364]: Starting Exit the Session... Feb 03 17:47:15 localhost.localdomain systemd[1364]: Received SIGRTMIN+24 from PID 2173 (kill). Why does systemd think I'm trying to shut down the computer right after logging in? The computer doesn't actually shut down and I'll get a usable desktop after what I assumed was a hard lock but it takes well over 5 minutes, I haven't put a stopwatch to it. Thanks, Richard

3 9

Re: NETDEV WATCHDOG: internal(r8152): transmit queue 0 timed out
by poma 03 Feb '15

03 Feb '15

On 16.01.2015 10:37, Hayes Wang wrote: > poma [mailto:pomidorabelisima@gmail.com] >> Sent: Friday, January 16, 2015 4:25 PM > [...] >>> This looks like a USB problem. Is there a way to get usb (or >>> NetworkManager) to reinitialize the driver when this happens? >> >> I would ask these people for advice, therefore. > > Our hw engineers need to analyse the behavior of the device. > However, I don't think you have such instrument to provide > the required information. If we don't know the reason, we > couldn't give you the proper solution. Besides, your solution > would work if and only if reloading the driver is helpful. > > The issue have to debug from the hardware, and I have no idea > about what the software could do before analysing the hw. Maybe > you could try the following driver first to check if it is useful. > > http://www.realtek.com.tw/downloads/downloadsView.aspx?Langid=2&PNid=13&PFi… > > Best Regards, > Hayes > Thanks for your response, Mr. Hayes. Mr. Sean, please download and check if "timeout" is still present with built RTL8153 module from REALTEK site, as Mr. Hayes proposed. http://www.realtek.com.tw/downloads/downloadsView.aspx?Langid=2&PNid=13&PFi… r8152.53-2.03.0.tar.bz2 Procedure - should be equal for both, Fedora 21 & 20: $ uname -r 3.17.8-300.fc21.x86_64 $ su -c 'yum install kernel-devel' $ tar xf r8152.53-2.03.0.tar.bz2 $ cd r8152-2.03.0/ $ make $ su # cp 50-usb-realtek-net.rules /etc/udev/rules.d/ # udevadm trigger --action=add # modprobe -rv r8152 # cp r8152.ko /lib/modules/$(uname -r)/updates/ # depmod # modprobe -v r8152 poma

2 4

yum update errors wine-core
by Paul Cartwright 03 Feb '15

03 Feb '15

Is this just me, or should I wait for package updates?? updated fedora21 x86_64 .. when I try to update I get: --> Finished Dependency Resolution Error: Package: wine-core-1.7.35-3.1.i686 (@home_DarkPlayer_Pipelight) Requires: libgphoto2_port.so.10(LIBGPHOTO2_5_0) Removing: libgphoto2-2.5.3-9.fc21.i686 (@fedora) libgphoto2_port.so.10(LIBGPHOTO2_5_0) Updated By: libgphoto2-2.5.7-1.fc21.i686 (updates) ~libgphoto2_port.so.12(LIBGPHOTO2_5_0) Error: Package: wine-core-1.7.35-3.1.x86_64 (@home_DarkPlayer_Pipelight) Requires: libgphoto2_port.so.10(LIBGPHOTO2_5_0)(64bit) Removing: libgphoto2-2.5.3-9.fc21.x86_64 (@koji-override-0/$releasever) libgphoto2_port.so.10(LIBGPHOTO2_5_0)(64bit) Updated By: libgphoto2-2.5.7-1.fc21.x86_64 (updates) ~libgphoto2_port.so.12(LIBGPHOTO2_5_0)(64bit) Error: Package: wine-core-1.7.35-3.1.i686 (@home_DarkPlayer_Pipelight) Requires: libgphoto2_port.so.10 Removing: libgphoto2-2.5.3-9.fc21.i686 (@fedora) libgphoto2_port.so.10 Updated By: libgphoto2-2.5.7-1.fc21.i686 (updates) ~libgphoto2_port.so.12 Error: Package: wine-core-1.7.35-3.1.x86_64 (@home_DarkPlayer_Pipelight) Requires: libgphoto2_port.so.10()(64bit) Removing: libgphoto2-2.5.3-9.fc21.x86_64 (@koji-override-0/$releasever) libgphoto2_port.so.10()(64bit) Updated By: libgphoto2-2.5.7-1.fc21.x86_64 (updates) ~libgphoto2_port.so.12()(64bit) You could try using --skip-broken to work around the problem whats wrong? -- Paul Cartwright Registered Linux User #367800 and new counter #561587

2 2

What are *.xz compressed kernel modules for (Fedora 21)
by Kevin Wilson 03 Feb '15

03 Feb '15

Hi, I have Fedora 21 (x86_64). Under /usr/lib/modules/3.17.4-302.fc21.x86_64/kernel, all the kernel module are in compressed form. (xz files). Under /usr/lib/modules/3.17.4-302.fc21.x86_64/kernel, the kernel modules are in the *.ko form What are the *.xz compressed kernel modules for ? In fedora 20 we had only *.ko files under /lib/modules. It seems to me that after booting, when running modprobe, only the *.ko modules are used. Just wonder what would happen If I would (accidentally or by purpose) delete the /lib/modules folder in fedora 21 (I don't intend to do it before getting an answer here...) Regards, Kevin

3 2

F20: No sound unless root ??
by sean darcy 03 Feb '15

03 Feb '15

I'm trying to play some sound as a user. But pulseaudio can't find any outputs: $ aplay -l aplay: device_list:268: no soundcards found... But, as root, aplay sees the integrated sound card: # aplay -l **** List of PLAYBACK Hardware Devices **** card 0: SB [HDA ATI SB], device 0: VT2020 Analog [VT2020 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: SB [HDA ATI SB], device 1: VT2020 Digital [VT2020 Digital] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: SB [HDA ATI SB], device 2: VT2020 Alt Analog [VT2020 Alt Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 I'd just use root if I could, by pulseaudio doesn't like that. sean

3 4

Re: mdadm: Cannot get exclusive access to /dev/md127
by Rich Emberson 03 Feb '15

03 Feb '15

Tried: # wipefs -a /dev/md127 which did not word, so I next tried: # wipefs -f -a /dev/md127 /dev/md127: 6 bytes were erased at offset 0x00000000 (crypto_LUKS): 4c 55 4b 53 ba be and then # mdadm -S /dev/md127 mdadm: Cannot get exclusive access to /dev/md127:Perhaps a running process, mounted filesystem or active volume group? but the filesystem is still mounted. curious, that creating an encrypted raid system on fedora seems to be an irreversible action. Now, with part of the raid file system "wipefs"-ed, above, I fear rebooting and hanging when it does not come up. Richard

2 1

Jump to page: