Re: what is the process number of a running application ?
On 01/14/2015 09:32 AM, Angelo Moreschini wrote: http://community.linuxmint.com/tutorial/view/50 --- From the command line you can type: |sudo xkill There's no reason to use sudo for xkill. Root can't do anything with xkill that you, as the X session owner, cannot do. xkill doesn't kill an application, it causes the X server to disconnect the client application. Usually that will cause the application to exit, but if it's well and truly stuck, it may continue consuming memory and CPU resources in the background, in which case you'll still need to track it down and kill it. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
GNU Backgammon now works
Afer the latest kernel update: uname -a Linux localhost.localdomain 3.17.8-300.fc21.x86_64 #1 SMP Thu Jan 8 23:32:49 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux I started and was actually able to play a complete game of GNU Backgammon! before this ( since I installed it a few months back) every time I started backgammon, it would paint the window with the board and. CRASH, no matter what I did or tried. -- Paul Cartwright Registered Linux User #367800 and new counter #561587 -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: What happened to the kernel-doc package?
On 14.01.2015 21:36, Ian Pilcher wrote: yum provides /usr/share/doc/kernel* is returning no matches. Fedora Kernel Meeting Minutes for 2013-12-13 https://lists.fedoraproject.org/pipermail/kernel/2013-December/004741.html * Removal of kernel-doc (jwb, 19:19:19) * LINK: http://kojipkgs.fedoraproject.org//packages/kernel/3.13.0/0.rc3.git4.1.fc21/data/logs/x86_64/root.log (jwb, 19:21:37) * kernel-doc subpackage brings in asciidoc and xmlto, which bloat the BuildRequires for the kernel significantly (jwb, 19:24:34) * ACTION: jwb to drop kernel-doc subpackage (jwb, 19:24:44) Local copy of the kernel docs is a very useful phenomenon, but let's be happy that we have a kernel. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: With newer updates to Fedora 20 the wakeup timer does not work...
On 12.01.2015 20:58, dwoody1 wrote: I have Mythtv installed. I setup a wakeup timer that worked in Fedora 19 so the computer would boot up in time to record a show and then shutdown until the next recording was scheduled. But in Fedora 20, with the inclusion of halt into systemd, the wakeup timer does not work. In Fedora 19 the timer needed to be reset in the halt init script after the hwclock was updated. Mythtv has a page describing how to setup the timer but it has not been updated to reflect the systemd requirements. I assume that the shutdown in systemd needs to be modified but I am unsure how. I have searched for wakeup, systemd, mythtv, hwclock and others but have not found what I need to change. Thanks for your help, David There you go. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: f20 :: kernel update :: scriptlet warning
On 13.01.2015 07:52, Adrian Sevcenco wrote: Hi! I just updated today and i got this for the kernel update: Could not determine the kernel command line parameters. Please specify the kernel command line in /etc/kernel/cmdline! warning: %posttrans(kernel-3.17.8-200.fc20.x86_64) scriptlet failed, exit status 1 Non-fatal POSTTRANS scriptlet failure in rpm package kernel-3.17.8-200.fc20.x86_6 Is this ok? Thanks! Adrian There you go. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: MC Midnight Commander: error opening PDF files refers to Dolphin
On 14.01.2015 07:55, Tim wrote: On Mon, 2015-01-12 at 13:23 +0100, A.J. Bonnema wrote: I have always used MC as my commandline filemanager and really like it. However, since Fedora 21, when opening a PDF file it always shows an error that it cannot open /usr/bin/dolphin which is understandable, because by default gnome uses a different file manager (Nautilus I think). I haven't used MC for ages, but can you try simply changing the preferences for what MC uses to open PDF files? MC may have defaulted for using a KDE client, instead of something else. Some things palm off opening files to some other file handler, such as gnome-open, or xdg-open (the latter is less biased towards a particular desktop), which check the file to see what it is, then open it with an appropriate default program. If MC does that, it may be that you need to configure /that/ handler instead of MC. Or, maybe the solution is to reconfigure MC to use that handler to deal with PDF files. Usually, with something more graphical than MC, you can right click on a particular file, then choose what it's opened with, and also have some option for changing the default application for what will open the same type of file. I don't know if MC works that way now, nor whether simply right clicking on some PDF file through your desktop, instead of MC, will let you set default preferences that will apply to MC, as well. Somewhere in there, one of those suggestions ought to do the trick, but write back to the list if you're still stuck. $ xdg-mime query default application/pdf evince.desktop Use xdg-open by default in mc.ext.in if present to open files, fallback on current scheme otherwise https://www.midnight-commander.org/ticket/2118 Opened 5 years ago Last modified 2 years ago -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: what is the process number of a running application ?
On 14.01.2015 18:32, Angelo Moreschini wrote: thank you, I found a very simple as well very elegant way to kill an application, if it has a graphic interface on the screen: http://community.linuxmint.com/tutorial/view/50 --- From the command line you can type: sudo xkill the result of this command is a a particular shape of the cursor that can be used to terminate a program, simply clicking on his window with this cursor.. [?]. It works really very good.. man 1 xkill ... CAVEATS This command does not provide any warranty that the application whose connection to the X server is closed will abort nicely, or even abort at all. All this command does is to close the connection to the X server. Many existing applications do indeed abort when their connection to the X server is closed, but some can choose to continue. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
What happened to the kernel-doc package?
yum provides /usr/share/doc/kernel* is returning no matches. -- Ian Pilcher arequip...@gmail.com I grew up before Mark Zuckerberg invented friendship -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: f20 :: kernel update :: scriptlet warning
On 14.01.2015 23:07, Josh Boyer wrote: On Wed, Jan 14, 2015 at 4:10 PM, poma pomidorabelis...@gmail.com wrote: On 13.01.2015 07:52, Adrian Sevcenco wrote: Hi! I just updated today and i got this for the kernel update: Could not determine the kernel command line parameters. Please specify the kernel command line in /etc/kernel/cmdline! warning: %posttrans(kernel-3.17.8-200.fc20.x86_64) scriptlet failed, exit status 1 Non-fatal POSTTRANS scriptlet failure in rpm package kernel-3.17.8-200.fc20.x86_6 Is this ok? This isn't from the kernel. It's probably from the kernel-install script or something related to it, which is provided by systemd. There you go. Not helpful. Please just have people file bugs. But people like to write on the lists - not you favorite form of communication, but such is life, you know Josh. josh -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Blocking POODLE
On Wed, Jan 14, 2015 at 7:40 PM, Matthew Saltzman m...@clemson.edu wrote: 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.) RHEL servers have support from Red Hat, send an email or pick up the phone. The patches between RHEL and Fedora are documented, but unless someone actually knows the answer it's totally non-obvious how to answer your question other than yes I realize it's 2015, but here's how you use a telephone... -- Chris Murphy -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Blocking POODLE
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 -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: [389-users] Recreating replica agreements
On 01/14/2015 08:01 AM, carne_de_passaro wrote: Hello guys, I am planning to recreate my replica agreements, which today uses SSL on port 636, to use startTLS on port 389. My question is: Do I have to reinitialize the databases of the agreements that I recreate? Danilo, You should not have to reinit your replicas. Ideally, you would just modify an existing agreement, there is no need to delete it and recreate it. You would only need to reinit your replicas if you reloaded the database(like an import for example), but just modifying an agreement should be fine. Mark I'm using the 389-ds-base-1.2.11.15-34.el6_5.x86_64. Thanks in advance. Danilo -- 389 users mailing list 389-users@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/389-users -- 389 users mailing list 389-users@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/389-users
Re: [389-users] Recreating replica agreements
Ok Mark, thank you! Danilo 2015-01-14 12:21 GMT-02:00 Mark Reynolds marey...@redhat.com: On 01/14/2015 08:01 AM, carne_de_passaro wrote: Hello guys, I am planning to recreate my replica agreements, which today uses SSL on port 636, to use startTLS on port 389. My question is: Do I have to reinitialize the databases of the agreements that I recreate? Danilo, You should not have to reinit your replicas. Ideally, you would just modify an existing agreement, there is no need to delete it and recreate it. You would only need to reinit your replicas if you reloaded the database(like an import for example), but just modifying an agreement should be fine. Mark I'm using the 389-ds-base-1.2.11.15-34.el6_5.x86_64. Thanks in advance. Danilo -- 389 users mailing list389-users@lists.fedoraproject.orghttps://admin.fedoraproject.org/mailman/listinfo/389-users -- 389 users mailing list 389-users@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/389-users -- 389 users mailing list 389-users@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/389-users
C/C++ Compiler Invalidly Turning Warnings into Errors?
I have a driver for a wifi usb device that I need to compile because there are no drivers in the kernel, which has been obtained from the vendor of the device. When I attempt to compile the code the compile fails on the grounds that some warnings are being translated into errors. From my perspective these errors should not be happening because, when a debugging module wants to time stamp the build, that is not an error and is perfectly acceptable. How do I get the compiler to stop producing these errors. The messages I get are listed below. Authentication requested [root] for make driver: make ARCH=x86_64 CROSS_COMPILE= -C /lib/modules/3.17.8-300.fc21.x86_64/build M=/usr/local/downloads/dlink/RTL8812AU_linux_v4.3.2_11100.20140411/driver/rtl8812AU_linux_v4.3.2_11100.20140411 modules make[1]: Entering directory '/usr/src/kernels/3.17.8-300.fc21.x86_64' CC [M] /usr/local/downloads/dlink/RTL8812AU_linux_v4.3.2_11100.20140411/driver/rtl8812AU_linux_v4.3.2_11100.20140411/core/rtw_cmd.o CC [M] /usr/local/downloads/dlink/RTL8812AU_linux_v4.3.2_11100.20140411/driver/rtl8812AU_linux_v4.3.2_11100.20140411/core/rtw_security.o CC [M] /usr/local/downloads/dlink/RTL8812AU_linux_v4.3.2_11100.20140411/driver/rtl8812AU_linux_v4.3.2_11100.20140411/core/rtw_debug.o /usr/local/downloads/dlink/RTL8812AU_linux_v4.3.2_11100.20140411/driver/rtl8812AU_linux_v4.3.2_11100.20140411/core/rtw_debug.c: In function ‘dump_drv_version’: /usr/local/downloads/dlink/RTL8812AU_linux_v4.3.2_11100.20140411/driver/rtl8812AU_linux_v4.3.2_11100.20140411/core/rtw_debug.c:66:64: error: macro __DATE__ might prevent reproducible builds [-Werror=date-time] DBG_871X_SEL_NL(sel, build time: %s %s\n, __DATE__, __TIME__); ^ /usr/local/downloads/dlink/RTL8812AU_linux_v4.3.2_11100.20140411/driver/rtl8812AU_linux_v4.3.2_11100.20140411/core/rtw_debug.c:66:1: error: macro __TIME__ might prevent reproducible builds [-Werror=date-time] DBG_871X_SEL_NL(sel, build time: %s %s\n, __DATE__, __TIME__); ^ /usr/local/downloads/dlink/RTL8812AU_linux_v4.3.2_11100.20140411/driver/rtl8812AU_linux_v4.3.2_11100.20140411/core/rtw_debug.c:66:1: error: macro __DATE__ might prevent reproducible builds [-Werror=date-time] /usr/local/downloads/dlink/RTL8812AU_linux_v4.3.2_11100.20140411/driver/rtl8812AU_linux_v4.3.2_11100.20140411/core/rtw_debug.c:66:1: error: macro __TIME__ might prevent reproducible builds [-Werror=date-time] /usr/local/downloads/dlink/RTL8812AU_linux_v4.3.2_11100.20140411/driver/rtl8812AU_linux_v4.3.2_11100.20140411/core/rtw_debug.c:66:1: error: macro __DATE__ might prevent reproducible builds [-Werror=date-time] /usr/local/downloads/dlink/RTL8812AU_linux_v4.3.2_11100.20140411/driver/rtl8812AU_linux_v4.3.2_11100.20140411/core/rtw_debug.c:66:1: error: macro __TIME__ might prevent reproducible builds [-Werror=date-time] cc1: some warnings being treated as errors scripts/Makefile.build:257: recipe for target '/usr/local/downloads/dlink/RTL8812AU_linux_v4.3.2_11100.20140411/driver/rtl8812AU_linux_v4.3.2_11100.20140411/core/rtw_debug.o' failed make[2]: *** [/usr/local/downloads/dlink/RTL8812AU_linux_v4.3.2_11100.20140411/driver/rtl8812AU_linux_v4.3.2_11100.20140411/core/rtw_debug.o] Error 1 Makefile:1377: recipe for target '_module_/usr/local/downloads/dlink/RTL8812AU_linux_v4.3.2_11100.20140411/driver/rtl8812AU_linux_v4.3.2_11100.20140411' failed make[1]: *** [_module_/usr/local/downloads/dlink/RTL8812AU_linux_v4.3.2_11100.20140411/driver/rtl8812AU_linux_v4.3.2_11100.20140411] Error 2 make[1]: Leaving directory '/usr/src/kernels/3.17.8-300.fc21.x86_64' Makefile:1350: recipe for target 'modules' failed make: *** [modules] Error 2 ## Compile make driver error: 2 Please check error Mesg ## attachment: samorris.vcf-- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: what is the process number of a running application ?
thank you, I found a very simple as well very elegant way to kill an application, if it has a graphic interface on the screen: http://community.linuxmint.com/tutorial/view/50 --- From the command line you can type: sudo xkill the result of this command is a a particular shape of the cursor that can be used to terminate a program, simply clicking on his window with this cursor.. [?]. It works really very good.. On Tue, Jan 13, 2015 at 7:49 PM, Gordon Messmer gordon.mess...@gmail.com wrote: On 01/12/2015 09:25 AM, Angelo Moreschini wrote: - In the window of gnome-system-monitor the name netbeans isn't. The name is probably java then. Right-click on any java processes and select Properties. The resulting window will contain the Command Line that invoked the process, and that should tell you whether you're looking at netbeans or some other java process. When you've found it, you can right-click to end or kill the process. You don't need the PID to do so from the gnome-system-monitor. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
[389-users] Recreating replica agreements
Hello guys, I am planning to recreate my replica agreements, which today uses SSL on port 636, to use startTLS on port 389. My question is: Do I have to reinitialize the databases of the agreements that I recreate? I'm using the 389-ds-base-1.2.11.15-34.el6_5.x86_64. Thanks in advance. Danilo -- 389 users mailing list 389-users@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/389-users
