The last eclipse-cdt update has broken my c++ perspective
by luca paganotti
Hi all, I'm searching help about the last eclipse-cdt update carried out on
my fedora 20 box.
It seems I'm not able anymore to load my existing c++ projects, nor create
new ones. I've tried to uninstall and then reinstall all my eclipse
environment few times. I've also tried to rollback to the previous yum
transaction. The c perspective is absent. I've tried also to issue eclipse
with the -clean switch. But no hope for the time being. The last cdt update
is about eclipse-cdt 8.3.0-2 x86_64 and was performed on 2015-03-22.
Is there someone kind to help or drive me to the right source of info?
Thank you for any answer and forgive my italianish ...
9 years, 1 month
current laptop recommendations
by Ian Malone
Anyone have any good suggestions for a new laptop with good Linux
compatibility? My current one is about 8 years old (IIRC), not looking
for anything superspecced to replaced it, just annoyances like reduced
battery life and the wifi switch playing up are starting to build up
(plus people have poked the screen one too many times). It's a 13.3"
screen with 100GB hard drive and I guess I'd be hoping to find
something similar with a maximum budget of about £500.
--
imalone
http://ibmalone.blogspot.co.uk
9 years, 1 month
hdparm problem
by JD
The command and error message are:
# time hdparm --verbose --user-master m --security-erase-enhanced
thepassword /dev/sdc
security_password="thepassword"
/dev/sdc:
Issuing SECURITY_ERASE command, password="thepassword", user=master
outgoing cdb: 85 08 0e 00 00 00 01 00 00 00 00 00 00 40 ec 00
SG_IO: ATA_16 status=0x0, host_status=0x0, driver_status=0x0
SG_IO: sb[]: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00
incoming_data: 7a 42 ff 3f 37 c8 10 00 00 00 00 00 3f 00 00 00 00 00 00
00 20 20 20 20 57 20 2d 44 58 57 31 56 35 45 4b 33 45 41 33 38 00 00 00
40 00 00 31 30 30 2e 41 31 31 30 44 57 20 43 44 57 30 32 50 4e 58 56 30
2d 45 30 34 41 30 54 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20
20 20 20 10 80 00 40 00 2f 01 40 00 00 00 00 07 00 ff 3f 10 00 3f 00 10
fc fb 00 00 01 ff ff ff 0f 00 00 07 00 03 00 78 00 78 00 78 00 78 00 00
00 00 00 00 00 00 00 00 00 00 00 1f 00 0e ff 04 00 4c 00 44 00 fe 03 00
00 6b 74 69 7d 23 61 6b 74 49 bc 23 61 7f 40 bb 00 bb 00 80 00 fe ff 00
00 00 00 00 00 00 00 00 00 00 00 00 00 b0 88 e0 e8 00 00 00 00 00 00 00
00 03 60 00 00 01 50 e2 4e 90 5e 21 ff 00 00 00 00 00 00 00 00 00 00 00
00 00 00 18 40 18 40 00 00 00 00 00 00 00 00 00 00 00 00 00 00 27 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 04 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 35 70 00 00 00 00 00 40 00 00 00 00 00 00 00
00 00 00 00 00 00 00 50 14 00 00 00 00 00 00 00 00 3e 10 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 01 00 00 10 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 a5 bd
SG_IO: desc[]: 00 00
ATA_16 stat=00 err=00 nsect=00 lbal=00 lbam=00 lbah=00 dev=00
outgoing cdb: 85 06 20 00 00 00 00 00 00 00 00 00 00 40 f3 00
SG_IO: ATA_16 status=0x2, host_status=0x0, driver_status=0x8
SG_IO: sb[]: 72 01 00 1d 00 00 00 0e 09 0c 00 00 00 00 00 00 00 00 00
00 40 50 00 00 00 00 00 00 00 00 00 00
SG_IO: desc[]: 09 0c 00 00 00 00 00 00 00 00 00 00 40 50
ATA_16 stat=50 err=00 nsect=00 lbal=00 lbam=00 lbah=00 dev=40
oflags.bits.lob_all=0x8a, flags={ feat nsect command }
oflags.bits.hob_all=0x00, flags={ }
outgoing cdb: 85 0a 06 00 00 00 01 00 00 00 00 00 00 40 f4 00
outgoing_data: 03 00 68 64 70 61 72 6d 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00
SG_IO: ATA_16 status=0x2, host_status=0x0, driver_status=0x8
SG_IO: sb[]: 72 0b 00 00 00 00 00 0e 09 0c 00 04 00 01 00 00 00 00 00
00 40 51 00 00 00 00 00 00 00 00 00 00
SG_IO: desc[]: 09 0c 00 04 00 01 00 00 00 00 00 00 40 51
ATA_16 stat=51 err=04 nsect=01 lbal=00 lbam=00 lbah=00 dev=40
I/O error, ata_op=0xf4 ata_status=0x51 ata_error=0x04
SECURITY_ERASE: Input/output error
real 0m3.56s
user 0m0.00s
sys 0m0.00s
However, I have no problem running
dd if=/dev/zero of=/dev/sdc bs=1G (PS: I have 8GB ram, and less that
1GB is used before I start the command).
So, am hoping an hdparm guru will offer some insight.
9 years, 1 month
yum check error elfutils
by Stephen Davies
Since upgrading from Fedora 20 to 21 (using fedup), I get the following:
[root@mustang ~]# yum check
Loaded plugins: langpacks
elfutils-libs-0.161-2.fc21.i686 has missing requires of
elfutils-libelf(x86-32) = ('0', '0.161', '2.fc21')
elfutils-libs-0.161-6.fc20.x86_64 is a duplicate with
elfutils-libs-0.161-2.fc21.i686
Error: check all
What must I do to fix this?
Cheers and thanks,
Stephen
--
9 years, 1 month
I broke Yum (by messing with Python libs)
by Martin Cigorraga
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
9 years, 1 month
Polkit General Protection Fault
by Arthur Dent
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
9 years, 1 month
SELinux is preventing abrt-dump-journ from read access on the file /usr/lib64/libreport.so.0.
by Lawrence E Graves
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_pipe_tmp_t,
postfix_qmgr_tmp_t, postfix_smtp_tmp_t, postfix_smtpd_tmp_t,
postfix_virtual_tmp_t, postgresql_tmp_t, pppd_tmp_t, prelink_exec_t,
prelink_tmp_t, prelude_lml_tmp_t, proc_t, procmail_tmp_t, psad_tmp_t,
pulseaudio_tmpfs_t, puppet_tmp_t, puppetmaster_tmp_t, qpidd_tmp_t,
racoon_tmp_t, realmd_tmp_t, rhev_agentd_tmp_t, rhsmcertd_tmp_t,
ricci_tmp_t, rlogind_tmp_t, rolekit_tmp_t, rpm_script_tmp_t, rpm_tmp_t,
rsync_tmp_t, rtas_errd_tmp_t, samba_net_tmp_t, sblim_tmp_t,
secadm_sudo_tmp_t, sectool_tmp_t, selinux_munin_plugin_tmp_t,
semanage_tmp_t, sendmail_tmp_t, services_munin_plugin_tmp_t,
session_dbusd_tmp_t, sge_tmp_t, shell_exec_t, shorewall_tmp_t,
slapd_tmp_t, smbd_tmp_t, smoltclient_tmp_t, smsd_tmp_t, snort_tmp_t,
sosreport_tmp_t, soundd_tmp_t, spamc_tmp_t, spamd_tmp_t,
speech-dispatcher_tmp_t, squid_tmp_t, squirrelmail_spool_t, src_t,
ssh_agent_tmp_t, ssh_keygen_tmp_t, ssh_tmpfs_t, staff_sudo_tmp_t,
stapserver_tmp_t, stunnel_tmp_t, svirt_tmp_t, svnserve_tmp_t,
swat_tmp_t, swift_tmp_t, sysadm_passwd_tmp_t, sysadm_sudo_tmp_t,
syslogd_tmp_t, syslogd_var_run_t, system_conf_t, system_cronjob_tmp_t,
system_db_t, system_dbusd_tmp_t, system_mail_tmp_t,
system_munin_plugin_tmp_t, tcpd_tmp_t, telepathy_gabble_tmp_t,
telepathy_idle_tmp_t, telepathy_logger_tmp_t,
telepathy_mission_control_tmp_t, telepathy_msn_tmp_t,
telepathy_salut_tmp_t, telepathy_sofiasip_tmp_t,
telepathy_stream_engine_tmp_t, telepathy_sunshine_tmp_t, telnetd_tmp_t,
tetex_data_t, textrel_shlib_t, tgtd_tmp_t, thumb_tmp_t, tmp_t,
tomcat_tmp_t, tuned_tmp_t, tvtime_tmp_t, tvtime_tmpfs_t, udev_tmp_t,
uml_tmp_t, uml_tmpfs_t, unconfined_munin_plugin_tmp_t,
update_modules_tmp_t, user_cron_spool_t, user_fonts_t, user_mail_tmp_t,
user_tmp_t, usr_t, uucpd_tmp_t, var_log_t, var_spool_t, varnishd_tmp_t,
virt_qemu_ga_tmp_t, virt_tmp_t, vmtools_tmp_t, vmware_host_tmp_t,
vmware_tmp_t, vmware_tmpfs_t, vpnc_tmp_t, w3c_validator_tmp_t,
webadm_tmp_t, webalizer_tmp_t, wireshark_tmp_t, wireshark_tmpfs_t,
xauth_tmp_t, xend_tmp_t, xenstored_tmp_t, xserver_tmpfs_t, ypbind_tmp_t,
ypserv_tmp_t, zabbix_tmp_t, zarafa_deliver_tmp_t, zarafa_indexer_tmp_t,
zarafa_server_tmp_t, zarafa_var_lib_t, zebra_tmp_t.
Then execute:
restorecon -v '/usr/lib64/libreport.so.0'
***** Plugin catchall (1.31 confidence) suggests **************************
If you believe that abrt-dump-journ should be allowed read access on the
libreport.so.0 file by default.
Then you should report this as a bug.
You can generate a local policy module to allow this access.
Do
allow this access for now by executing:
# grep abrt-dump-journ /var/log/audit/audit.log | audit2allow -M mypol
# semodule -i mypol.pp
Additional Information:
Source Context system_u:system_r:abrt_dump_oops_t:s0
Target Context system_u:object_r:unlabeled_t:s0
Target Objects /usr/lib64/libreport.so.0 [ file ]
Source abrt-dump-journ
Source Path abrt-dump-journ
Port <Unknown>
Host Jehovah.local
Source RPM Packages
Target RPM Packages libreport-2.3.0-6.fc21.x86_64
Policy RPM selinux-policy-3.13.1-105.3.fc21.noarch
Selinux Enabled True
Policy Type targeted
Enforcing Mode Enforcing
Host Name Jehovah.local
Platform Linux Jehovah.local 3.18.9-200.fc21.x86_64 #1 SMP
Mon Mar 9 15:10:50 UTC 2015 x86_64 x86_64
Alert Count 1
First Seen 2015-03-19 22:13:10 MDT
Last Seen 2015-03-19 22:13:10 MDT
Local ID 30c2fda6-73d3-4d79-9b33-e1716706cf30
Raw Audit Messages
type=AVC msg=audit(1426824790.624:30): avc: denied { read } for pid=729
comm="abrt-dump-journ" name="libreport.so.0" dev="sda3" ino=167087
scontext=system_u:system_r:abrt_dump_oops_t:s0
tcontext=system_u:object_r:unlabeled_t:s0 tclass=file permissive=0
Hash: abrt-dump-journ,abrt_dump_oops_t,unlabeled_t,file,read
--
All things are workable but don't all things work.
Prov. 3:5 & 6
9 years, 1 month
Strane UUID problem
by Heinz Diehl
Hi,
F21, fully updated, no longer boots cleanly. After to tries, I found the
culprit:
suddenly, the physical device (/dev/sda) has got a UUID, and it's the same as
the one /home has. So no wonder that /home can't be mounted. I have not the
slightest clue what could have given /dev/sda a UUID.
So how to remove it?
Thanks,
Heinz.
9 years, 1 month
gnucash and keyring in fedora 21
by Stuart McGraw
I'm not sure if this is a Fedora question or a Gnucash
question but I thought I'd start here...
I just installed fedora 21 and gnucash (a personal finance
app) from the f21 yum repo. Quite frequently when I start
gnucash I will be asked for a password to unlock my keyring.
How do I disable that "feature"? Googling didn't really
turn up anything helpful.
I don't need password protection on the gnucash app and
the whole concept is rather silly given that all its data
is stored in an unencrypted xml file.
9 years, 1 month
Is SMART really that dumb?
by Tom Horsley
So, SMART reports it has N pending sectors. This must mean
it knows exactly which sectors those are, but nothing in
the SMART interface is willing to tell you what sectors it
is talking about?
You could maybe correlate them with the filesystem
structures and find out what files they might be
affecting (or if they are just in free space),
but that's not useful information for SMART to report?
Please tell me I'm the one who is an idiot and I've
just overlooked the obvious here :-).
9 years, 1 month