users July 2012

users@lists.fedoraproject.org

252 participants
266 discussions

F17, power switch offers no choices??
by Fred Smith 02 Jul '12

02 Jul '12

I haven't used Fedora on my netbook since F14, I used Centos 6 in that interim. however, both centos 6 and fedora (back when I used it) allowd one to press the netbook's power switch, while logged in, and got a dialog offering choices like shutdown, log off, standby, hibernate. how, on F17 though, it just does a shutdown, depending on which desktop/session I'm in. (in gnome it seems to just go to standby mode, while in lxde or xfce (or MATE, which I've installed) it just shuts down. I assume this is an artifact of systemd, but have no clue how to hack it to make it once again offer the choices. thanks! Fred -- ---- Fred Smith -- fredex(a)fcshome.stoneham.ma.us ----------------------------- "For him who is able to keep you from falling and to present you before his glorious presence without fault and with great joy--to the only God our Savior be glory, majesty, power and authority, through Jesus Christ our Lord, before all ages, now and forevermore! Amen." ----------------------------- Jude 1:24,25 (niv) -----------------------------

7 12

wodim and audiomaster
by JD 02 Jul '12

02 Jul '12

The example given in the wodim man page for how to use the audiomaster option in wodim requires that you have 2 drives, one containing the source and one the target media to be written. If you have only one drive, and your all the .inf files for each track and the audio.cddb and audio.cdindex, .... etc. are in the same dir where the wav files are, how can I then use the -audiomaster option. So far I have tried and it keeps complaining that stdin is a tty.

1 0

Fwd: Systemctl hates mysqld: Fails writing to /tmp
by R. G. Newbury 02 Jul '12

02 Jul '12

Sent from my iPhone Begin forwarded message: > From: "R. G. Newbury" <newbury(a)mandamus.org> > Date: 1 July, 2012 12:50:57 PM EDT > To: Fedora-List <users-request(a)lists.fedoraproject.org> > Subject: Systemctl hates mysqld: Fails writing to /tmp > > I am stumped. I have a puzzler which needs the brain-power and knowledge which hands around here. > > Systemctl on fedora 16 will NOT start mysqld. > > Startup fails with a permissions error, attempting to write to /tmp, which is chmod 1777, that is, world writeable and readable! There is nothing wrong with the mysql setup. If I run each command from the command line, mysqld starts without problem. That is to say: there is nothing wrong with the mysqld setup. I repeat: there is nothing wrong with the mysqld setup. > > In order to avoid unhelpful responses/questions relating to the many many many other ways in which one can have mysqld fail to start, I list some of the sanity checks which I have used to ensure that everything lines up properly: I have checked my.cnf and use the same command line switches, and folders and permissions throughout. Everything run as root. Selinux disabled. And mysqld *will* start properly from the commandline, just NOT by way of systemctl. > > *** Proof of Setup > # mkdir /var/log/mysqld > mkdir: cannot create directory `/var/log/mysqld': File exists > # chown -R mysql:mysql /var/log/mysqld > # chmod -R 777 /var/log/mysqld > # chown -R mysql:mysql /run/mysqld > # chmod -R 777 /run/mysqld > # chmod -R 1777 /tmp > # killall mysqld > mysqld: no process found > > **** Replicate mysqld.service commands: > > # /usr/libexec/mysqld-prepare-db-dir > # /usr/bin/mysqld_safe --nowatch --datadir=/var/lib/mysql --socket=/var/lib/mysql/mysql.sock --pid-file=/run/mysqld/mysqld.pid --basedir=/usr/ --log-error=/var/log/mysqld/mysqld.log > # /usr/libexec/mysqld-wait-ready $MAINPID > > **** and mysqld STARTS > # ps -ae | grep mysqld > 20853 pts/3 00:00:00 mysqld > > At this point, I can use the console mysql client, etc. etc. > So the mysqld setup is correct. But this is not what happens under systemctl > > ******** COMPARE AND CONTRAST ******* > # killall mysqld > > # systemctl start mysqld.service > Job failed. See system logs and 'systemctl status' for details. > > *** Edited *** Failure is: > Process: 25762 ExecStartPost=/usr/libexec/mysqld-wait-ready $MAINPID (code=exited, status=1/FAILURE) > > *** Comment out the exec-post command (which is not supposed to be required) and reload: > > # systemctl start mysqld.service > > ******* Note that it gives no error....as appears above > ******** Yes the service IS disabled atm, because of this testing > # systemctl status mysqld.service > mysqld.service - MySQL database server > Loaded: loaded (/lib/systemd/system/mysqld.service; disabled) > Active: failed since Sun, 01 Jul 2012 12:05:22 -0400; 5s ago > Process: 26943 ExecStart=/usr/bin/mysqld_safe --nowatch --datadir=/var/lib/mysql --socket=/var/lib/mysql/mysql.sock --pid-file=/run/mysqld/mysqld.pid --basedir=/usr/ --log-error=/var/log/mysqld/mysqld.log (code=exited, status=0/SUCCESS) > Process: 26927 ExecStartPre=/usr/libexec/mysqld-prepare-db-dir (code=exited, status=0/SUCCESS) > Main PID: 27128 (code=exited, status=1/FAILURE) > CGroup: name=systemd:/system/mysqld.service > > SO, the operation was a success but the patient died... > > **** mysqld.log > > **** First the command line startup and shutdown: > > 120701 12:15:30 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql > 120701 12:15:30 [Note] Plugin 'FEDERATED' is disabled. > 120701 12:15:30 InnoDB: The InnoDB memory heap is disabled > 120701 12:15:30 InnoDB: Mutexes and rw_locks use GCC atomic builtins > 120701 12:15:30 InnoDB: Compressed tables use zlib 1.2.5 > 120701 12:15:30 InnoDB: Using Linux native AIO > 120701 12:15:30 InnoDB: Initializing buffer pool, size = 128.0M > 120701 12:15:30 InnoDB: Completed initialization of buffer pool > 120701 12:15:30 InnoDB: highest supported file format is Barracuda. > 120701 12:15:30 InnoDB: Waiting for the background threads to start > 120701 12:15:31 InnoDB: 1.1.8 started; log sequence number 5950198631 > 120701 12:15:31 [Note] Server hostname (bind-address): '127.0.0.1'; port: 3306 > 120701 12:15:31 [Note] - '127.0.0.1' resolves to '127.0.0.1'; > 120701 12:15:31 [Note] Server socket created on IP: '127.0.0.1'. > 120701 12:15:31 [Note] Event Scheduler: Loaded 0 events > 120701 12:15:31 [Note] /usr/libexec/mysqld: ready for connections. > Version: '5.5.24' socket: '/var/lib/mysql/mysql.sock' port: 3306 MySQL Community Server (GPL) > 120701 12:16:08 [Note] /usr/libexec/mysqld: Normal shutdown > > 120701 12:16:08 [Note] Event Scheduler: Purging the queue. 0 events > 120701 12:16:08 InnoDB: Starting shutdown... > 120701 12:16:09 InnoDB: Shutdown completed; log sequence number 5950198631 > 120701 12:16:09 [Note] /usr/libexec/mysqld: Shutdown complete > 120701 12:16:08 [Note] Event Scheduler: Purging the queue. 0 events > 120701 12:16:08 InnoDB: Starting shutdown... > > **** All as expected > **** Systemctl startup: > > 20701 12:23:23 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql > 120701 12:23:23 [Note] Plugin 'FEDERATED' is disabled. > 120701 12:23:23 InnoDB: The InnoDB memory heap is disabled > 120701 12:23:23 InnoDB: Mutexes and rw_locks use GCC atomic builtins > 120701 12:23:23 InnoDB: Compressed tables use zlib 1.2.5 > 120701 12:23:23 InnoDB: Using Linux native AIO > > ********** HERE IS THE ERROR > > ^G/usr/libexec/mysqld: Can't create/write to file '/tmp/ibVcsIip' (Errcode: 13) > 120701 12:23:23 InnoDB: Error: unable to create temporary file; errno: 13 > 120701 12:23:23 [ERROR] Plugin 'InnoDB' init function returned error. > 120701 12:23:23 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed. > 120701 12:23:23 [ERROR] Unknown/unsupported storage engine: InnoDB > 120701 12:23:23 [ERROR] Aborting > > 120701 12:23:23 [Note] /usr/libexec/mysqld: Shutdown complete > > I can find NO other error messages. /tmp is 1777: completely world writeable, but systemctl/mysqld cannot write there. > > Sorry for the length. Can anyone shed ANY light on this? > > (And for all our sakes when replying, please PLEASE PLEASE chop off at the least everything above the 'HERE IS THE ERROR LINE'. It is all background and setup and not relevant to the actual error. It only shows *where* the error appears. > > ATM, my workaround is to disable mysqld.service, and start mysqld as an /etc/rc.d/init.d service by calling mysqld-prepare-db-dir and mysqld_safe from there. It's a bodge (and that's what I call it!) And without mysql, my mythbox is useless. And Spain v Italy is this afternoon! > > I want to know why mysqld cannot write to /tmp when started by systemctl. (Anyone know if Lennart reads this list?) > > > Geoff > > >

1 0

Fedora 17, not possible to add kernel parameters to GRUB 2
by agraham 01 Jul '12

01 Jul '12

Hello, I've installed F17 (in a VM) and on first boot, it is not possible to modify any kernel parameters. There appears to be 2 problems: Note: 1. I've never actually logged in to the VM. 2. no updates have been done 3. I've connecting to the VM via tigervnc client Problem 1. ========= On the very first boot, at the grub 2 to menu, I press 'e' to edit grub, but I cannot move the cursor to the "linux" line because it is always on the wrong position, so you cannot see what you are editing. Problem 2. ========= Making any changes to the kernel parameter line (locks up grub) and requires a hard boot. I would assume that these basic tests must have been tested as part of Q/A so I must be doing something wrong I know I can boot the machine and manually configure grub2, but the above should work "out of the box" from the first installation of an F17 ISO image. Any suggestions. Thanks. Albert.

5 10

Alacarte Fedora 17
by Martin Sharpe 01 Jul '12

01 Jul '12

> When applying any changes to the gnome applications menu via alacarte the file - applications.menu, > in the directory /home/user-name/.config/menus is modified (by alacarte) but no change to the menu occurs. > (for example showing or hiding a menu item). To make this work correctly alacarte needs to modify the file > applications-gnome.menu to allow items to change in the menu. This requires a simple change to the file > MenuEditor.py in the alacarte source code replacing the single occurance of applications.menu with > applications-gnome.menu. > The best way to do this is to download the source rpm and extract the archive then extract the alacarte source > and modify the file and create the new archive to overwrite the old one then use rpmbuild to build a new alacarte > rpm module and use yum to reinstall this module. Once done alacarte works ok. > One more thing. > I upgraded from Fedora 15 to Fedora 17 and am running Fedora on VmWorkstation in Windows. > After turning off the forced fallback mode and logging off and back in again gnome 3 works in the normal mode > except for 3-D effects. Having got used to the fallback mode this is very different and my first real experience of the > new gnome 3 shell. Overall Fedora 17 works fine in VmWorkstation apart from some problems with mouse operations. > For example to resize windows I can only use the diagonals not the sides and when using software like the advanced tweak tool > menu selections act a little like x-windows menu selections requiring one to press the return key to get the menu to stay. > Anybody had similar problems?

1 0

Disk troubles - which disk is that ?
by Development discussions related to Fedora 01 Jul '12

01 Jul '12

I'm getting so app pausing, and found disk errors in the messages log: ---- [ 5205.549112] ata3.00: exception Emask 0x50 SAct 0x1 SErr 0x280901 action 0x6 frozen [ 5205.549115] ata3.00: irq_stat 0x08000000, interface fatal error [ 5205.549118] ata3: SError: { RecovData UnrecovData HostInt 10B8B BadCRC } [ 5205.549120] ata3.00: failed command: READ FPDMA QUEUED [ 5205.549124] ata3.00: cmd 60/08:00:ad:d2:cd/00:00:43:00:00/40 tag 0 ncq 4096 in [ 5205.549125] res 40/00:04:ad:d2:cd/00:00:43:00:00/40 Emask 0x50 (ATA bus error) [ 5205.549127] ata3.00: status: { DRDY } [ 5205.549130] ata3: hard resetting link [ 5206.007042] ata3: softreset failed (device not ready) ---- .. repeats, slight difference in SErr How do I translate ata3 or ata3.00 into the logical disk eg /dev/sdN ? Further on: ---- [ 5282.931436] ata3.00: status: { DRDY } [ 5282.931437] ata3.00: failed command: READ FPDMA QUEUED [ 5282.931440] ata3.00: cmd 60/08:d8:ac:8d:c7/00:00:33:00:00/40 tag 27 ncq 4096 in [ 5282.931441] res 40/00:f4:c4:8d:c7/00:00:33:00:00/40 Emask 0x50 (ATA bus error) [ 5282.931443] ata3.00: status: { DRDY } [ 5282.931444] ata3.00: failed command: READ FPDMA QUEUED [ 5282.931447] ata3.00: cmd 60/08:e0:b4:8d:c7/00:00:33:00:00/40 tag 28 ncq 4096 in [ 5282.931448] res 40/00:f4:c4:8d:c7/00:00:33:00:00/40 Emask 0x50 (ATA bus error) ---- Also, I seen sd 2:0:0:0: as the disk label, how would you convert that to /dev/sdN disk ? Cheers, Dave.

2 2

Alacarte Fedora 17
by Martin Sharpe 01 Jul '12

01 Jul '12

When applying any changes to the gnome applications menu via alacarte the file - applications.menu, in the directory /home/user-name/.config/menus is modified (by alacarte) but no change to the menu occurs (for example showing or hiding a menu item) To make this work correctly alacarte needs to modify the file applications-gnome.menu to allow items to change in the menu. This requires a simple change to the file MenuEditor.py in the alacarte source code replacing the single occurance of applications.menu with applications-gnome.menu. The best way to do this is to download the source rpm and extract the archive then extract the alacarte source and modify the file and create the new archive to overwrite the old one then use rpmbuild to build a new alacarte rpm module and use yum to reinstall this module. Once done alacarte works ok. One more thing. I upgraded from Fedora 15 to Fedora 17 and am running Fedora on VmWorkstation in Windows. After turning off the forced fallback mode and logging off and back in again gnome 3 works in the normal mode except for 3-D effects. Having got used to the fallback mode this is very different and my first real experience of the new gnome 3 shell. Overall Fedora 17 works fine in VmWorkstation apart from some problems with mouse operations. For example to resize windows I can only use the diagonals not the sides and when using software like the advanced tweak tool menu selections act a little like x-windows menu selections requiring one to press the return key to get the menu to stay. Anybody had similar problems?

1 0

Message when running yum update
by JD 01 Jul '12

01 Jul '12

# yum -y update Loaded plugins: auto-update-debuginfo, downloadonly, etckeeper, langpacks, presto, priorities, product-id, refresh-packagekit, : subscription-manager Updating certificate-based repositories. Unable to read consumer identity This machine has not been registered and therefore has no access to security and other critical updates. Please register using subscription-manager. ----------------------------------------------------------------------------- This is the first time I see the registration thing. Why is this being done? Why does anyone have to register their machine? I see no reason for this other than monitoring people's machines. This is totally unacceptable.

12 33

How to manually install an httpd module? SELinix denial?
by Georgios Petasis 01 Jul '12

01 Jul '12

Hi all, I am trying to install Apache Rivet under Fedora 17 (http://tcl.apache.org/rivet/static/download.html). Everything seems as expected, except for starting httpd. Httpd does not start, I get an error in apache logs: [Sun Jul 01 20:05:13 2012] [error] (20014)Internal error: mod_rivet: init.tcl must be installed correctly for Apache Rivet to function: can't find package RivetTcl exactly 2.1 (/usr/lib64/rivet2.1/site-packages/mod_rivet) Of course file /usr/lib64/rivet2.1/site-packages/mod_rivet/init.tcl exists: -rw-r--r--. root root system_u:object_r:lib_t:s0 /usr/lib64/rivet2.1/site-packages/mod_rivet/init.tcl The audit log shows: type=SERVICE_START msg=audit(1341162429.242:416): pid=0 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg=' comm="httpd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed' How to solve this? I thing that I have a selinux denial. How to enable a custom apache module to work? George

2 2

using cdrdao
by JD 01 Jul '12

01 Jul '12

Just for fun, I thought I would try to run cdrdao to burn a .bin file (via a .cue file): $ cdrdao write --overburn --device /dev/sg1 --driver generic-mmc 'Into The Unknown.2.cue' Cdrdao version 1.2.3 - (C) Andreas Mueller <andreas(a)daneb.de> Into The Unknown.2.cue:1: Warning, ignoring CDTEXTFILE... /dev/sg1: Slimtype DVD A DS8A1P Rev: CH71 Using driver: Generic SCSI-3/MMC - Version 2.0 (options 0x0000) Starting write at speed 24... Pausing 10 seconds - hit CTRL-C to abort. Process can be aborted with QUIT signal (usually CTRL-\). WARNING: No super user permission to setup real time scheduling. Turning BURN-Proof on Enabling JustSpeed. Executing power calibration... Power calibration successful. The bin file size is 771573600 bytes. After almost 30 minutes, the drive is still spinning at high speed, drive light flashes on and off, and no other messages are being emitted. At 24X write speed, it should not take this long. There are no error messages in /var/log/messages.

2 1

Jump to page: