Re: Polkit General Protection Fault
On Mar 22, 2015 2:54 PM, "Arthur Dent" wrote: > > Hello All, > > I have, for some time, been getting these messages in my logs: > > =8<= > WARNING: General Protection Faults in these executables > traps: polkitd : 2 Time(s) Looks like polkitd crashed twice during your logwatch report interval. If you have the Automatic Bug Reporting Tool (ABRT) installed it should have picked these crashes up and allow you to file a bug for them. I believe polkitd will be automatically started by dbus when it is needed again so you might not ever notice any ill effects. On the other hand, you might find that you are unable to perform administrator actions from the GUI when this happens. It wouldn't affect anything else. > **Unmatched Entries** These are all completely harmless. You should configure logwatch to ignore them and/or file a bug to have them ignored by the default configuration. -T.C. -- 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: checkboxes in f21 gnome apps
On 03/22/2015 02:47 PM, David A. De Graaf wrote: On Fri, Mar 20, 2015 at 04:41:34PM -0600, Stuart McGraw wrote: I just installed Fedora-21 and xfce. Install was from the regular live x64 download, not the xfce spin. I have an odd problem with checkboxes in gui dialogs: they don't show any checkmarks. If I click on a checkbox, a checkmark will appear for a fraction of a second then disappear. From the program's behavior I can tell that the setting got set but it is obviously difficult if one can not see which boxes are checked in a dialog and which aren't. This problem seems to be limited to Gnome apps (the ones with the new -- at least to someone coming from F15 -- and really unpleasant UI design). For example, brasero exhibits the effect but k3b doesn't. Does this problem ring a bell with anyone? Yes, I had this problem today - with kvm, or perhaps virt-manager. I was running a virtual instance of WindowsXP, and wanted to activate the USB port to talk with a TomTom GPS device. When I clicked on the appropriate box, a check appeared, then disappeared. The USB port was, in fact, activated, but that behaviour is quite unsatisfactory. I, too, am running F21 and Xfce4. I studiously avoid Gnome. After considerable playing around I discovered that the missing checkmark effect occurs on whenever an xfce* style is selected in app-menu -> settings -> appearance. Coming from Fedora-15, I tried Gnome in this new F21 install somewhat expecting an improvement in the last three years but it seems they've borked it up even worse -- scrolling with a mouse is now really FUd, the UI take more clicks and uses more space, and the Open menu is a mess. The Gnome project seems completely off the rails. -- 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: I broke Yum (by messing with Python libs)
On 22Mar2015 17:10, Martin Cigorraga wrote: After upgrading some python packages via pip I found I left Yum in a non-working state: [...] I have found it is quite important to completely separate "supplier" package updates (i.e. yum supplied) and user driven package updates and/or additions (i.e. pip). This holds with Perl, Python, etc. In the case of python I strongly advocate making a virtualenv (easier than you'd think) and run pip within that. This has the advantage of: - keeping extra packages completely away from the system packages - lets you use multiple versions of Python as needed (the system Python, other Pythons installed in /usr/local or /opt etc) - with the right permissions, lets you create and maintain the virtualenv area as yourself; I keep a current python2 and python3 virtualenv in my homedir routinely Do not touch the system packages!!! [...] Now, what I did to fix the mess was: 1. Download python-pycurl-7.19.3.1-5.fc21.x86_64.rpm; 2. rpm --nodeps -e python-curl 3. rpm -ivh python-pycurl-7.19.3.1-5.fc21.x86_64.rpm. So far so good, Yum isn't complaining anymore about the library version mismatch; however I would like to know if I proceeded right or if there's still any missing step(s) I should follow to ensure a proper system integrity. Just this: let yum maintain the system python packages and use a virtualenv for your extras. NB: you can set up the virtualenv to live off the system python (or whichever) as a basis, which means that anything you _do_ install with yum is then available for free in the virtualenv. Or you can make it standalone and use the virtualenv pip for aal its extras. Cheers, Cameron Simpson -- 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: I broke Yum (by messing with Python libs)
Yeah, that's it, dnf. And I don't know why they change it neither. I like yum so far, it's simple, clean and stable. But well, so be it. Cheers! :-) -- 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: I broke Yum (by messing with Python libs)
On 03/22/2015 09:37 PM, Sylvia Sánchez wrote: Then there's no need of further work. Anyway, I think yum is going to be dropped. I don't remember right now the name of its substitute tough. Sorry, my memory is terrible. Cheers! I didn't know yum was "breakable"! LoL! I have yet to mess with anything regarding libraries and the like in Fedora, I've been content to just let it go its own way and if I'm tempted to fiddle-faddle with anything I usually do it on a test machine. I think the replacement for yum is called "dnf"?(Dandified Yum...or so they say!) I don't know why they feel they need to replace yum, it's been stable and has worked great since I've been using Fedora...(from around 13 / 14...) I guess progress dictates that all things must change huh?...just my two cents... EGO II -- 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: I broke Yum (by messing with Python libs)
Then there's no need of further work. Anyway, I think yum is going to be dropped. I don't remember right now the name of its substitute tough. Sorry, my memory is terrible. Cheers! -- 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: I broke Yum (by messing with Python libs)
Hey, so far yum seems to work okay, I'm on F21. -M. On Sun, Mar 22, 2015 at 9:40 PM, Sylvia Sánchez wrote: > If you use yum to install something, does it works? > BTW, what Fedora version are you using? > > > Cheers! > -- > 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
Re: I broke Yum (by messing with Python libs)
If you use yum to install something, does it works? BTW, what Fedora version are you using? Cheers! -- 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
Polkit General Protection Fault
Hello All, I have, for some time, been getting these messages in my logs: =8<= WARNING: General Protection Faults in these executables traps: polkitd : 2 Time(s) **Unmatched Entries** polkitd: Acquired the name org.freedesktop.PolicyKit1 on the system bus: 1 Time(s) polkitd: Finished loading, compiling and executing 5 rules: 1 Time(s) polkitd: Loading rules from directory /etc/polkit-1/rules.d: 1 Time(s) polkitd: Loading rules from directory /usr/share/polkit-1/rules.d: 1 Time(s) polkitd: Registered Authentication Agent for unix-session:763 (system bus name :1.1685 [/usr/bin/gnome-shell], object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_GB.UTF-8): 1 Time(s) polkitd: Registered Authentication Agent for unix-session:c1 (system bus name :1.29 [gnome-shell --mode=gdm], object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_GB.UTF-8): 1 Time(s) polkitd: Registered Authentication Agent for unix-session:c2 (system bus name :1.1712 [gnome-shell --mode=gdm], object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_GB.UTF-8): 1 Time(s) polkitd: Unregistered Authentication Agent for unix-session:763 (system bus name :1.1685, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_GB.UTF-8) (disconnected from bus): 1 Time(s) polkitd: Unregistered Authentication Agent for unix-session:c1 (system bus name :1.29, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_GB.UTF-8) (disconnected from bus): 1 Time(s) =8<= Should I be concerned? (and what, if anything, should I do about it?) I am not aware of any undue problems, but it's a scary looking error message... Thanks in advance... Mark -- 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: checkboxes in f21 gnome apps
On Fri, Mar 20, 2015 at 04:41:34PM -0600, Stuart McGraw wrote: > I just installed Fedora-21 and xfce. Install was from > the regular live x64 download, not the xfce spin. > > I have an odd problem with checkboxes in gui dialogs: > they don't show any checkmarks. If I click on a > checkbox, a checkmark will appear for a fraction of > a second then disappear. From the program's behavior > I can tell that the setting got set but it is obviously > difficult if one can not see which boxes are checked > in a dialog and which aren't. > > This problem seems to be limited to Gnome apps (the ones > with the new -- at least to someone coming from F15 -- > and really unpleasant UI design). For example, brasero > exhibits the effect but k3b doesn't. > > Does this problem ring a bell with anyone? Yes, I had this problem today - with kvm, or perhaps virt-manager. I was running a virtual instance of WindowsXP, and wanted to activate the USB port to talk with a TomTom GPS device. When I clicked on the appropriate box, a check appeared, then disappeared. The USB port was, in fact, activated, but that behaviour is quite unsatisfactory. I, too, am running F21 and Xfce4. I studiously avoid Gnome. -- David A. De GraafDATIX, Inc.Hendersonville, NC d...@datix.us www.datix.us "Never be afraid to try something new. Remember that a lone amateur built the Ark. A large group of professionals built the Titanic." -- Dave Barry -- 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
I broke Yum (by messing with Python libs)
Hi all, After upgrading some python packages via pip I found I left Yum in a non-working state: There was a problem importing one of the Python modules required to run yum. The error leading to this problem was: pycurl: libcurl link-time ssl backend (nss) is different from compile-time ssl backend (none/other) Please install a package which provides this module, or verify that the module is installed correctly. It's possible that the above module doesn't match the current version of Python, which is: 2.7.8 (default, Nov 10 2014, 08:19:18) [GCC 4.9.2 20141101 (Red Hat 4.9.2-1)] // Now, what I did to fix the mess was: 1. Download python-pycurl-7.19.3.1-5.fc21.x86_64.rpm; 2. rpm --nodeps -e python-curl 3. rpm -ivh python-pycurl-7.19.3.1-5.fc21.x86_64.rpm. So far so good, Yum isn't complaining anymore about the library version mismatch; however I would like to know if I proceeded right or if there's still any missing step(s) I should follow to ensure a proper system integrity. Thanks and have a nice Sunday! (At least what's left of it :) -Martin -- 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: SELinux is preventing abrt-dump-journ from read access on the file /usr/lib64/libreport.so.0.
On 03/21/2015 02:03 PM, Lawrence E Graves wrote: > SELinux is preventing abrt-dump-journ from read access on the file > /usr/lib64/libreport.so.0. > > * Plugin restorecon (82.4 confidence) suggests > > > If you want to fix the label. > /usr/lib64/libreport.so.0 default label should be lib_t. > Then you can run restorecon. > Do > # /sbin/restorecon -v /usr/lib64/libreport.so.0 > > * Plugin file (7.05 confidence) suggests > ** > > If you think this is caused by a badly mislabeled machine. > Then you need to fully relabel. > Do > touch /.autorelabel; reboot > > * Plugin file (7.05 confidence) suggests > ** > > If you think this is caused by a badly mislabeled machine. > Then you need to fully relabel. > Do > touch /.autorelabel; reboot > > * Plugin catchall_labels (4.59 confidence) suggests > *** > > If you want to allow abrt-dump-journ to have read access on the > libreport.so.0 file > Then you need to change the label on /usr/lib64/libreport.so.0 > Do > # semanage fcontext -a -t FILE_TYPE '/usr/lib64/libreport.so.0' > where FILE_TYPE is one of the following: NetworkManager_tmp_t, > abrt_dump_oops_exec_t, abrt_etc_t, abrt_helper_exec_t, abrt_tmp_t, > abrt_upload_watch_tmp_t, abrt_var_cache_t, abrt_var_lib_t, > abrt_var_run_t, admin_crontab_tmp_t, afs_cache_t, alsa_tmp_t, > amanda_tmp_t, anon_inodefs_t, antivirus_tmp_t, apcupsd_tmp_t, > apmd_tmp_t, arpwatch_tmp_t, asterisk_tmp_t, auditadm_sudo_tmp_t, > automount_tmp_t, awstats_tmp_t, bacula_tmp_t, bin_t, bitlbee_tmp_t, > bluetooth_helper_tmp_t, bluetooth_helper_tmpfs_t, bluetooth_tmp_t, > boinc_project_tmp_t, boinc_tmp_t, boot_t, bootloader_tmp_t, > bugzilla_tmp_t, cardmgr_dev_t, ccs_tmp_t, cdcc_tmp_t, > chrome_sandbox_tmp_t, cinder_api_tmp_t, cinder_backup_tmp_t, > cinder_scheduler_tmp_t, cinder_volume_tmp_t, cloud_init_tmp_t, > cluster_tmp_t, cobbler_tmp_t, cockpit_tmp_t, collectd_script_tmp_t, > colord_tmp_t, comsat_tmp_t, condor_master_tmp_t, condor_schedd_tmp_t, > condor_startd_tmp_t, conman_tmp_t, couchdb_tmp_t, cpu_online_t, > crack_tmp_t, crond_tmp_t, crontab_tmp_t, ctdbd_tmp_t, cups_pdf_tmp_t, > cupsd_lpd_tmp_t, cupsd_tmp_t, cvs_tmp_t, cyphesis_tmp_t, cyrus_tmp_t, > dbadm_sudo_tmp_t, dbskkd_tmp_t, dcc_client_tmp_t, dcc_dbclean_tmp_t, > dccd_tmp_t, dccifd_tmp_t, dccm_tmp_t, ddclient_tmp_t, debugfs_t, > deltacloudd_tmp_t, devicekit_tmp_t, dhcpc_tmp_t, dhcpd_tmp_t, > dirsrv_tmp_t, dirsrvadmin_tmp_t, disk_munin_plugin_tmp_t, > dkim_milter_tmp_t, docker_tmp_t, dovecot_auth_tmp_t, > dovecot_deliver_tmp_t, dovecot_tmp_t, drbd_tmp_t, etc_runtime_t, > etc_t, exim_tmp_t, fail2ban_tmp_t, fenced_tmp_t, firewalld_tmp_t, > firewallgui_tmp_t, fonts_cache_t, fonts_t, fsadm_tmp_t, > fsdaemon_tmp_t, ftpd_tmp_t, ftpdctl_tmp_t, games_tmp_t, games_tmpfs_t, > gconf_tmp_t, geoclue_tmp_t, getty_tmp_t, git_script_tmp_t, > gkeyringd_tmp_t, glance_registry_tmp_t, glance_tmp_t, glusterd_tmp_t, > gpg_agent_tmp_t, gpg_pinentry_tmp_t, gpg_pinentry_tmpfs_t, gpm_tmp_t, > gssd_tmp_t, httpd_php_tmp_t, httpd_suexec_tmp_t, httpd_tmp_t, > inetd_child_tmp_t, inetd_tmp_t, init_tmp_t, initrc_tmp_t, ipsec_tmp_t, > iptables_tmp_t, iscsi_tmp_t, kadmind_tmp_t, kdumpctl_tmp_t, > kdumpgui_tmp_t, keystone_tmp_t, kismet_tmp_t, kismet_tmpfs_t, > klogd_tmp_t, krb5_host_rcache_t, krb5kdc_tmp_t, ktalkd_tmp_t, > l2tpd_tmp_t, ld_so_cache_t, ld_so_t, ldconfig_tmp_t, lib_t, > livecd_tmp_t, locale_t, logrotate_mail_tmp_t, logrotate_tmp_t, > logwatch_mail_tmp_t, logwatch_tmp_t, lpd_tmp_t, lpr_tmp_t, > lsassd_tmp_t, lsmd_plugin_tmp_t, lvm_tmp_t, machineid_t, > mail_munin_plugin_tmp_t, mailman_cgi_tmp_t, mailman_mail_tmp_t, > mailman_queue_tmp_t, man_cache_t, man_t, mandb_cache_t, > mediawiki_tmp_t, mock_tmp_t, mojomojo_tmp_t, mongod_tmp_t, > mount_tmp_t, mozilla_plugin_tmp_t, mozilla_plugin_tmpfs_t, > mozilla_tmp_t, mozilla_tmpfs_t, mpd_tmp_t, mplayer_tmpfs_t, > mscan_tmp_t, munin_script_tmp_t, munin_tmp_t, mysqld_tmp_t, > nagios_eventhandler_plugin_tmp_t, nagios_openshift_plugin_tmp_t, > nagios_system_plugin_tmp_t, nagios_tmp_t, named_tmp_t, netutils_tmp_t, > neutron_tmp_t, nova_ajax_tmp_t, nova_api_tmp_t, nova_cert_tmp_t, > nova_compute_tmp_t, nova_conductor_tmp_t, nova_console_tmp_t, > nova_direct_tmp_t, nova_network_tmp_t, nova_objectstore_tmp_t, > nova_scheduler_tmp_t, nova_vncproxy_tmp_t, nova_volume_tmp_t, > ntop_tmp_t, ntpd_tmp_t, nut_upsd_tmp_t, nut_upsdrvctl_tmp_t, > nut_upsmon_tmp_t, nx_server_tmp_t, openshift_cgroup_read_tmp_t, > openshift_cron_tmp_t, openshift_initrc_tmp_t, openshift_tmp_t, > openvpn_tmp_t, openvswitch_tmp_t, openwsman_tmp_t, > pam_timestamp_tmp_t, passenger_tmp_t, pcp_tmp_t, > pegasus_openlmi_storage_tmp_t, pegasus_tmp_t, piranha_web_tmp_t, > pkcs_slotd_tmp_t, pki_tomcat_tmp_t, podsleuth_tmp_t, > podsleuth_tmpfs_t, policykit_tmp_t, portmap_tmp_t, > postfix_bounce_tmp_t, postfix_cleanup_tmp_t, postfix_local_tmp_t, > postfix_map_tmp_t, postfix_pickup_tmp_t, postfix_p
Re: Strane UUID problem
On 21.03.2015, Chris Murphy wrote: > OK it's a little annoying when you provide so little information from > the very start about what you're trying to do, and what the setup is, Here's what lsblk says before formatting: AME FSTYPE LABEL UUID MOUNTPOINT sda ├─sda1 ext4 6cb0a099-3037-4b82-87ad-e4058dc8944c /boot ├─sda2 xfs 5a16b831-b896-437c-8b8c-95d600ce90e0 / ├─sda3 swap 3f579e51-577f-4f8b-975c-d58aa3063f7e [SWAP] └─sda4 xfs 1dc70566-e597-4c1a-baa8-c652b79c2010 /home sr0 And here afterwards: AME FSTYPE LABEL UUID MOUNTPOINT sdanilfs2 190d8a5e-81c3-461a-8602-1d67a01b59f3 ├─sda1 ext4 6cb0a099-3037-4b82-87ad-e4058dc8944c /boot ├─sda2 xfs 5a16b831-b896-437c-8b8c-95d600ce90e0 / ├─sda3 swap 3f579e51-577f-4f8b-975c-d58aa3063f7e [SWAP] └─sda4 nilfs2 190d8a5e-81c3-461a-8602-1d67a01b59f3 /home sr0 And this is systemd complaining that it can't mount /dev/sda: [] Mar 20 17:11:27 ayna systemd: Mounting /home... Mar 20 17:11:27 ayna kernel: Bluetooth: SCO socket layer initialized Mar 20 17:11:28 ayna kernel: usbcore: registered new interface driver btusb Mar 20 17:11:28 ayna kernel: NILFS version 2 loaded Mar 20 17:11:28 ayna systemd: home.mount mount process exited, code=exited status=32 Mar 20 17:11:28 ayna mount: mount.nilfs2: Error while mounting /dev/sda on /home: Device or resource busy Mar 20 17:11:28 ayna systemd: Failed to mount /home. Mar 20 17:11:28 ayna systemd: Dependency failed for Local File Systems. Mar 20 17:11:28 ayna systemd: Mar 20 17:11:28 ayna systemd: Triggering OnFailure= dependencies of local-fs.target. Mar 20 17:11:28 ayna systemd: Unit home.mount entered failed state. [] I do nothing more than booting into rl 1, formatting /home with nilfs2, set up the correct UUID in fstab, and so reboot. Formatting /home with ext4 or xfs works as expected, the UUID assigned to /dev/sda vanishes. -- 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
