Systemd: why am I waiting for wicd/mysqld?

Recently I moved from init scripts to systemd. The available guide ensured a smooth transition.
Nobody got harmed in the process.
But: booting is slower since then. As can be seen below, I'm waiting quite some time for the mysqld and wicd daemons.
➜ systemd-analyze blame
17482ms mysqld.service
10968ms wicd.service
5786ms gdm.service
4176ms colord.service
3768ms systemd-logind.service
1109ms systemd-vconsole-setup.service
801ms systemd-remount-fs.service
761ms systemd-udevd.service
742ms sys-kernel-debug.mount
723ms console-kit-log-system-start.service
719ms dev-mqueue.mount
706ms systemd-binfmt.service
659ms rc-local.service
640ms dev-hugepages.mount
596ms systemd-user-sessions.service
590ms proc-sys-fs-binfmt_misc.mount
548ms systemd-udev-trigger.service
397ms accounts-daemon.service
308ms polkit.service
246ms systemd-sysctl.service
243ms systemd-tmpfiles-setup.service
186ms udisks.service
107ms upower.service
86ms console-kit-daemon.service
61ms rtkit-daemon.service
22ms udisks2.service
18ms home.mount
13ms tmp.mount
1ms sys-fs-fuse-connections.mount
This seems odd to me. Since systemd starts services in parallel and is capable of starting them 'on the fly' when needed, why should I wait for them at boot?
Is there a way to start stuff like `mysqld.service` and `wicd.service` later? For example, after `gdm.service` is done, allowing me to sign in and do stuff?
As suggested by the guide I made sure all services are started at boot by running
systemctl enable <service-name>
for every service in my former DEAMONS array.
Last edited by A.J.Rouvoet (2012-11-07 22:53:50)

lothar_m wrote:
in my machine netcfg really takes some time too.
$systemd-analyze blame
16072ms netcfg.service
9595ms i2prouter.service
4164ms postgresql.service
2331ms udisks2.service
2010ms systemd-vconsole-setup.service
1896ms systemd-logind.service
Off topic: Nice Blackadder Quote you have as a signature ;-)

Similar Messages

Why lookup method waits for the crossover cable to plugged in?

Hi all,
In solaris 220 machine i am facing the following problem While executing lookup method.
If the crossover cable is properly connected lookup method is working fine.
If the crossover cable is unplugged, lookup method is waiting indefinitely until the cable is plugged in. (Lookup method is not throwing any exception )
Is there any way to avoid this ?
Please help me with this issue..
Thanks in advance...

Hmmm.. well I tried the idea of establishing the connection using the Network Browser feature of Classic os9 under the brand new twin 2.7Ghz powermac I have to the old clone, and found a bunch of missing extensions inc. the Network Browser!
This is an untouched Classic OS9 install of 9.2.2 that came with the Tiger OSX that came with the machine, but using the folders and prefs. ported over from a 10.3.9 machine I was running an account on using the Migration Assistant. The Extensions manager on the new powermac cant find the file cuz it wasnt installed under Tiger, obviously...
Is Apple suggesting not to try networking in the classic layer? Is it an experiment I shoudnt bother with?
I have no idea why an OS 8.5 machine can see the Tiger tower, but not connect... and why the Tiger cant see the old 8.5 thats on the clone Im trying to directly Cat5 cable over to through the network card... this is frustrating... would be nice to get the clone without monitor to be a part of this grouping , to become a lackey/drone/server of sorts....

[solved] systemd times out waiting for dev-null.device on encrypted fs

I have a relatively new install of Arch on my laptop. The relevant sections of the drive setup are a luks encrypted root device (with associated unencrypted /boot), and a large ntfs device encrypted with truecrypt. That contains my home directory, which is shared with the Windows 8 dual-boot on the machine.
I have all this mounted on boot, so my typical usage is to enter my password for the encrypted root, followed by the password for the truecrypt-encrypted data drive, then normal login.
This has been working fine for a couple of weeks. This afternoon I rebooted my machine from Windows to Linux, at which point the secondary encrypted drive failed to mount. The root device mounts fine.
On further examination, in the form of journalctl -xb, I'm getting the following errors after mounting the encrypted root device:
Feb 12 21:29:54 kafka systemd[1]: Job dev-null.device/start timed out.
Feb 12 21:29:54 kafka systemd[1]: Timed out waiting for device dev-null.device.
-- Subject: Unit dev-null.device has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/li … temd-devel
-- Documentation: http://www.freedesktop.org/wiki/Softwar … e9d022f03d
-- Unit dev-null.device has failed.
-- The result is timeout.
Feb 12 21:29:54 kafka systemd[1]: Dependency failed for Cryptography Setup for cryptdata.
-- Subject: Unit [email protected] has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/li … temd-devel
-- Documentation: http://www.freedesktop.org/wiki/Softwar … e9d022f03d
-- Unit [email protected] has failed.
As my root home directory is on the root filesystem, I can still log in as root. If I try to mount or unmount the truecrypt device (located at /data) the command hangs. After removing "auto,x-systemd.automount" from that device from /etc/fstab and rebooting, I have a significant delay at boot, but I can then mount the /data device as normal.
I can't find anything related to this either here or on Google. Any ideas?
Last edited by tealeaf (2014-02-13 12:01:55)

WonderWoofy wrote:A bit OT, but I just want to mention that having your $HOME on ntfs is probably not the best idea either. It may work, but because it is not a POSIX compliant filesystem, there is a good chance you might run into some issues.
Thanks for the warning. Sadly, as there are applications I need for work that only run in Windows, I need to dual boot this machine with Windows 8.1. This is the best option I can find for sharing my home directory, which is also a necessity due to the amount of data I have to share between the systems. I would much rather trust to ntfs-3g-ar and its UserMapping (and all the fiddling with ACLs that I had to do) than to the Windows ext2 drivers I can find. They all seem to be several years out of date. Linux is much better at talking NTFS than Windows is at talking EXT. (To be honest, I'm actually quite impressed with Windows 8 since the upgrade to 8.1. As a long term Arch user and a fan of tiling window managers it's interesting to see Windows moving in the right direction. )
With 'permissions' in the /etc/fstab and the .NTFS-3G/UserMapping file in place it works almost seamlessly. (It took a lot of tinkering with ACLs in Windows and Linux, but it's working very well now. One tip that I'll write here in case it's of use is that you want the last line of the UserMapping file to be a 'generic' mapping. When I didn't have that there were very strange things going on.)
The only two minor problems I have now are:
1) A few applications don't like FUSE filesystems. Steam worked for a while and then broke; reinstalling it failed at every stage. When I checked, it seems that FUSE is a known problem for Steam. (I don't think it's restricted to NTFS.) My response to that was to create /home/.local/$HOME on my root (ext4) filesystem and symlink out to it for troublesome applications.
2) There are a few characters for filenames that Windows doesn't like, making those files inaccessible in Windows. (Colons are the major culprit.) They're usually quite easily renamed. (The exception being my .maildir folder, which I have had to duplicate natively in cygwin.)
Neither of these are anything more than minor niggles. I appreciate the warning, though.
Having said that, if you have an alternative that lets me share a truecrypt-encrypted drive between Linux and Windows that is better than the NTFS-3G approach, I'd love to hear it for future reference.

Systemd Boot Problem - Times out waiting for LVM partitions

At first I had a problem in which the initramfs didn't map LVM partitions to /dev/vg0/lv, only /dev/mapper/vg0-lv. I changed /dev/vg0/root to /dev/mapper/vg0-root in bootloader configuration as a hacky workaround.
Getting closer to a working system, systemd failed boot because my fstab entries are uuids, and for some reason, my LVM volumes aren't showing up in /dev/disk/by-*. My flash drive boot partition shows up in there though.
I replaced the uuids with /dev/mapper/vg0-* and tried again. Now my boot fails with this:
Oct 21 19:19:31 archserver systemd[1]: Job dev-mapper-vg0\x2dmedia.device/start timed out.
Oct 21 19:19:31 archserver systemd[1]: Timed out waiting for device dev-mapper-vg0\x2dmedia.device.
Oct 21 19:19:31 archserver systemd[1]: Dependency failed for /mnt/media.
Oct 21 19:19:31 archserver systemd[1]: Dependency failed for Local File Systems.
Boot log: http://sprunge.us/LEhG
mkinitcpio.conf: http://sprunge.us/QEBK
What should I do?

This may be LVM's incompatibility with anything hotplug (it may not be, your issue sounds more obscure). You need to create your own, local lvm service file. I'll tell you how. This is /usr/lib/systemd/system/lvm.service:
[Unit]
Description=LVM activation
DefaultDependencies=no
Requires=systemd-udev-settle.service
After=systemd-udev-settle.service
Before=basic.target shutdown.target
Conflicts=shutdown.target
[Service]
ExecStart=/sbin/vgchange --available y
Type=oneshot
TimeoutSec=0
RemainAfterExit=yes
[Install]
WantedBy=basic.target
Create /etc/systemd/system/lvm_local.service:
[Unit]
Description=LVM activation
DefaultDependencies=no
Requires=dev-something-something1.device
After=dev-something-something1.device
Requires=dev-something-something2.device
After=dev-something-something2.device
Before=basic.target shutdown.target
Conflicts=shutdown.target
[Service]
ExecStart=/sbin/vgchange --available y
Type=oneshot
TimeoutSec=0
RemainAfterExit=yes
[Install]
WantedBy=basic.target
No, what to you put in those "something-something1" places above? For each LVM physical volume, run 'systemctl status /dev/disk/by-uuid/$UUID' where $UUID is the UUID of your physical volume. You'll get a status output showing the exact name of the correct .device unit. Then 'systemctl enable lvm_local.service'.
This speeds up boot and makes sure lvm is properly initialized. After writing all this, I am unsure if this is at all related to your problem, as your volume group is activated in initramfs and the links should be set up by udev.

[SOLVED] dmraid "Timed out waiting for device" at boot

Created a bug report with solution proposal: https://bugs.archlinux.org/task/33166
I created a virtual machine to demonstrate the problem
https://docs.google.com/open?id=0B40Hp1 … WZUQ21xZk0
The root and the other mount points are all on one raid disk. Although the root mounts quickly, other mount points cause timeouts at boot time.
dmraid prints that all /dev/mapper/isw_* devices are created.
I think /dev/disk/by-uuid/* links are created too, but for some reason systemd doesn't see them.
After boot I can execute "mount -a" without errors.
here's my fstab:
tmpfs /tmp tmpfs nodev,nosuid 0 0
UUID=e89249d8-49a5-415b-8f9b-97de5cfbe82d / ext3 defaults
UUID=c37f8bdd-3d6c-495f-bf8a-5ef059e55254 swap swap defaults 0 0
UUID=91988343-dd89-43b9-8975-babb0b9510a2 /media/ARCHLINUXNEW ext4 nofail 0 1
UUID=62C813E9C813B9ED /media/distrpart ntfs-3g rw,nofail
UUID=E0A1-D623 /media/realboot vfat rw,codepage=866,iocharset=utf8,umask=002,noatime,nofail
# journalctl -b
Dec 15 00:25:24 localhost kernel: firewire_core 0000:05:03.0: created device fw0: GUID 0011d800017a5dd7, S400
Dec 15 00:26:50 localhost systemd[1]: Job dev-disk-by\x2duuid-E0A1\x2dD623.device/start timed out.
Dec 15 00:26:50 localhost systemd[1]: Timed out waiting for device dev-disk-by\x2duuid-E0A1\x2dD623.device.
Dec 15 00:26:50 localhost systemd[1]: Dependency failed for /media/realboot.
Dec 15 00:26:50 localhost systemd[1]: Job media-realboot.mount/start failed with result 'dependency'.
Dec 15 00:26:50 localhost systemd[1]: Job dev-disk-by\x2duuid-E0A1\x2dD623.device/start failed with result 'timeout'.
Dec 15 00:26:50 localhost systemd[1]: Job dev-disk-by\x2duuid-62C813E9C813B9ED.device/start timed out.
Dec 15 00:26:50 localhost systemd[1]: Timed out waiting for device dev-disk-by\x2duuid-62C813E9C813B9ED.device.
Dec 15 00:26:50 localhost systemd[1]: Dependency failed for /media/distrpart.
Dec 15 00:26:50 localhost systemd[1]: Job media-distrpart.mount/start failed with result 'dependency'.
Dec 15 00:26:50 localhost systemd[1]: Job dev-disk-by\x2duuid-62C813E9C813B9ED.device/start failed with result 'timeout'.
Dec 15 00:26:50 localhost systemd[1]: Job dev-disk-by\x2duuid-91988343\x2ddd89\x2d43b9\x2d8975\x2dbabb0b9510a2.device/start timed out.
Dec 15 00:26:50 localhost systemd[1]: Timed out waiting for device dev-disk-by\x2duuid-91988343\x2ddd89\x2d43b9\x2d8975\x2dbabb0b9510a2.device.
Dec 15 00:26:50 localhost systemd[1]: Dependency failed for /media/ARCHLINUXNEW.
Dec 15 00:26:50 localhost systemd[1]: Job media-ARCHLINUXNEW.mount/start failed with result 'dependency'.
Dec 15 00:26:50 localhost systemd[1]: Dependency failed for File System Check on /dev/disk/by-uuid/91988343-dd89-43b9-8975-babb0b9510a2.
Dec 15 00:26:50 localhost systemd[1]: Job systemd-fsck@dev-disk-by\x2duuid-91988343\x2ddd89\x2d43b9\x2d8975\x2dbabb0b9510a2.service/start failed with result 'dependency
Dec 15 00:26:50 localhost systemd[1]: Job dev-disk-by\x2duuid-91988343\x2ddd89\x2d43b9\x2d8975\x2dbabb0b9510a2.device/start failed with result 'timeout'.
Dec 15 00:26:50 localhost systemd[1]: Dependency failed for /dev/disk/by-uuid/c37f8bdd-3d6c-495f-bf8a-5ef059e55254.
Dec 15 00:26:50 localhost systemd[1]: Reached target Swap.
Note the 1.5 minute pause
# mount | grep /dev/mapper
/dev/mapper/isw_ebaifefjbf_Volume0p9 on / type ext3 (rw,relatime,stripe=64,data=ordered)
/dev/mapper/isw_ebaifefjbf_Volume0p1 on /media/realboot type vfat (rw,noatime,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp866,iocharset=utf8,shortname=mixed,errors=remount-ro)
/dev/mapper/isw_ebaifefjbf_Volume0p8 on /media/ARCHLINUXNEW type ext4 (rw,relatime,stripe=64,data=ordered)
/dev/mapper/isw_ebaifefjbf_Volume0p5 on /media/distrpart type fuseblk (rw,nosuid,nodev,relatime,user_id=0,group_id=0,allow_other,blksize=4096)
Last edited by leniviy (2012-12-22 16:06:25)

I've ran into exactly same problem lately, but finally solved it.
Setup: Intel Fake RAID, mirror, partitioned as:
/dev/mapper/isw_dfjeffgfaj_rootvol1 /boot
/dev/mapper/isw_dfjeffgfaj_rootvol2 /
/dev/mapper/isw_dfjeffgfaj_rootvol3 /home (dm-crypted)
In /etc/fstab i had following mountpoints:
# file /etc/fstab
/dev/mapper/isw_dfjeffgfaj_rootvolp2 / ext4 rw,relatime,data=ordered 0 1
/dev/mapper/isw_dfjeffgfaj_rootvolp1 /boot ext4 rw,relatime,data=ordered 0 2
and boot hung on waiting for /dev/mapper/isw_dfjeffgfaj_rootvolp1. Solution involves changing dev path to UUID:
# file /etc/fstab
/dev/mapper/isw_dfjeffgfaj_rootvolp2 / ext4 rw,relatime,data=ordered 0 1
UUID=44809529-11d9-4f53-9652-7b97ed077225 /boot ext4 rw,relatime,data=ordered 0 2
For some reason symlinks /dev/mapper/isw* are not present during systemd mount.

Wait for Event FIPP - Completed Logically Deleted

Hi WF Experts,
We have a WF for Release of payments.
It has 1 Fork with 2 parallel branches (both necessary).
1 Branch has the approval process for Amount release and the other branch calling the Account assignment approval Subworkflow.
The approval process branch has the until loop with increment counter and it picks the agents within the loop until a loop condition is reached and thereby till no more approvals required.
The other branch, before calling the subworkflow, it checks a WAIT FOR EVENT FIPP->COMPLETED with container element FIPPID.
Both these branches needs to be completed so that the forks gets ended and the wf comes out of the fork.
The approval process branch is working perfectly. But in the other branch the WAIT FOR EVENT FIPP->COMPLETED gets logically deleted and thereby, this branch does not go firther to start the Account assignment approval Subworkflow. This way the Fork with the 2 necessary branches does not end, and thereby, the WF stops here and could not go further to set release indicators (Which is a backgorund task).This will confirm the end of WF process.
When I pass the WI ID for this Wait event in the SWIA, it shows the status as CANCELLED.
The WF User log as a whole shows the status as COMPLETED as all the approvers has approved the release.
Why is the Wait for Event gets logically deleted ?Please advice.
Edited by: Sameer Anwar on Jun 12, 2011 9:17 AM
Edited by: Sameer Anwar on Jun 12, 2011 9:21 AM

Dear Experts,
Any update on this . I am unable to sort this out why the Workflow is getting stopped.
-Anwar

Timed out waiting for device sys-subsystem-net-devices-enp69s0.device

Hi all,
Since quite some time I have been waiting for Arch Linux to startup (and shutdown), and today I wanted to figure out what was going wrong. I found out that I could find the boot log file with journalctl, and this seems to be the issue:
Oct 13 21:01:52 localhost systemd[1]: Job sys-subsystem-net-devices-enp69s0.device/start timed out.
Oct 13 21:01:52 localhost systemd[1]: Timed out waiting for device sys-subsystem-net-devices-enp69s0.device.
Oct 13 21:01:52 localhost systemd[1]: Dependency failed for dhcpcd on enp69s0.
Oct 13 21:01:52 localhost systemd[1]: Starting Network.
Oct 13 21:01:52 localhost systemd[1]: Reached target Network.
Oct 13 21:01:52 localhost systemd[1]: Mounting /mnt/homesrv/storage...
Now, enp69s0 is my LAN network interface, which I barely use, and my WLAN connection is handled by NetworkManager. However, I can't find out what I'm supposed to do to stop this behaviour. I tried:
systemctl disable sys-subsystem-net-devices-enp69s0.device
But that does not seem to solve anything. Can anyone help me out?
Last edited by Hmail (2013-10-13 19:09:53)

Andreaskem wrote:Maybe try "systemctl disable [email protected]".
That did the trick! I didn't want to disable the device because I might use it once in a while.
The shutdown issue is not solved yet, but that seems to be an issue with a samba share that is unmounted after the network services are shutdown. I'll delve in the wiki to figure out how to fix that. But for now, I can at least start my machine up within seconds. Thanks a lot!

Encrypted btrfs array, systemd not waiting for partitions [workaround]

Hi,
I have a non-root btrfs filesystem spannig over two encrypted partitions:
/etc/crypttab:
graid1 /dev/sdc3 /etc/crypto/graid1 timeout=15
graid2 /dev/sdb2 /etc/crypto/graid2 timeout=15
/etc/fstab:
/dev/mapper/graid1 /mnt/raid btrfs defaults,device=/dev/mapper/graid1,device=/dev/mapper/graid2 0 0
When booting I get
A start job is running for dev-mapper-graid2.device (10s / no limit)
Adding a nofail option to fstab makes the system bootable again but obviously the raid filesystem is not mounted. A mount -a in an interactive root shell mounts the filesystem just fine.
My first guess was that systemd is ignorant to (among other things) the fact that all btrfs partitions must be present when mouning a btrfs array, not just the first one and it tries to "optimise" the boot process by starting the mount as soon as the first device is up via crypttab systemd automagick (systemd-crypto or whatever that unit parsing crypttab is called). Since debugging of systemd is black magick (no errors, warnings, fails or anything useful yielded from two-hour debugging using the wiki and extensive ddg'ing) I went the trial-and-error way.
I found out that systemd somewhat "virtualises" the fstab to it's units, namely mount units, so I tried to gently hint it that it should really wait for the cryptsetup.target to finish so that all partitions are ready before it tries to mount the array:
/etc/systemd/system/mnt-raid.mount:
[Unit]
Description=/mnt/raid
Wants=cryptsetup.target
After=cryptsetup.target
AssertPathExists=/dev/mapper/graid1 // I was hoping these would force the unit to FAIL
AssertPathExists=/dev/mapper/graid2 // in order for it to be at least a little debuggable. Guess what.
[Mount]
What=/dev/mapper/graid1
Where=/mnt/raid
Type=btrfs
Options=defaults,relatime,compress=lzo,device=/dev/mapper/graid1,device=/dev/mapper/graid2
Along with this unit I also commented out the line in fstab since it took precedence* every time even though the systemd documentation specifically says otherwise: If a mount point is configured in both /etc/fstab and a unit file that is stored below /usr, the former will take precedence. If the unit file is stored below /etc, it will take precedence. This means: native unit files take precedence over traditional configuration files, but this is superseded by the rule that configuration in /etc will always take precedence over configuration in /usr.
*) I figured that much by trial-and-error approach, having the mount unit already present and listed in systemctl list-unit-files but removing the nofail option from fstab resulted in above mentioned "a start job is running" red line of death.
After bootup systemctl list-units says:
dev-mapper-graid1.device loaded inactive dead start dev-mapper-graid1.device
mnt-raid.mount loaded inactive dead start /mnt/raid
(these lines were not present when booting without the unit file).
Since the unit did not "fail" and there are no logs in journalctl -u mnt-raid.mount and running SYSTEMD_LOG_LEVEL=debug systemctl start mnt-raid.mount yields only unseful:
Calling manager for StartUnit on mnt-raid.mount, replace
Sent message type=method_call sender=n/a destination=org.freedesktop.systemd1 object=/org/freedesktop/systemd1 interface=org.freedesktop.systemd1.Manager member=StartUnit cookie=1 reply_cookie=0 error=n/a
Sent message type=method_call sender=n/a destination=org.freedesktop.systemd1 object=/org/freedesktop/systemd1 interface=org.freedesktop.systemd1.Manager member=GetUnit cookie=2 reply_cookie=0 error=n/a
Sent message type=method_call sender=n/a destination=org.freedesktop.systemd1 object=/org/freedesktop/systemd1/unit/mnt_2draid_2emount interface=org.freedesktop.DBus.Properties member=Get cookie=3 reply_cookie=0 error=n/a
Adding /org/freedesktop/systemd1/job/59 to the set
Got message type=signal sender=n/a destination=n/a object=/org/freedesktop/systemd1/job/59 interface=org.freedesktop.DBus.Properties member=PropertiesChanged cookie=2 reply_cookie=0 error=n/a
Got D-Bus request: org.freedesktop.DBus.Properties.PropertiesChanged() on /org/freedesktop/systemd1/job/59
Got message type=signal sender=n/a destination=n/a object=/org/freedesktop/systemd1/job/58 interface=org.freedesktop.DBus.Properties member=PropertiesChanged cookie=3 reply_cookie=0 error=n/a
Got D-Bus request: org.freedesktop.DBus.Properties.PropertiesChanged() on /org/freedesktop/systemd1/job/58
... and hangs indefinitely, I'm really running out of ideas. I did not find any information on how to debug a dead unit since it's apparently not considered an errorneous state.
I'm stuck. I don't know what to do next except for making workarounds like manually mounting the filesystem via some kind of (now defunct - why?) /etc/rc.local mechanism. How do I find out what's happening when systemd starts the mount unit? How do I get the output from the commands it runs (like mount and possibly others)? I have no idea whether the custom mount unit of mine works and the problem is elsewhere or doesn't, or ... whatever.
(off-topic: exactly how does systemd "optimise" anything? Ever since Arch moved to systemd my boot time tripled, all troubles got way more frustrating and 4 out of 5 of them were due to some systemd "goodie". What happened to KISS? systemd sure is Stupid but I kinda miss the Simple part...)
Last edited by mr.MikyMaus (2015-04-01 13:22:11)

Thanks! The Arch bug isn't directly related to my problem but the comment in systemd's bugreport was, well, "helpful", if you can call it that.
UUID in fstab indeed works but I have only vague idea why and from Lennart's style of commentary I have a really bad feeling. Last time I had this feeling was a couple of years ago when I needed to solve a problem with Windows and contacted Microsoft support. They also used this language style and words like "this is intended, this is considered to be like this, you need to" and similar but no explanation why is it this way and why is it deviating from what is expected behaviour from user's point of view.

[Solved] systemd does not wait for the unit to finish

My problem is described in the title. I have made a test by enabling the following unit:
[Unit]
Description=/etc/rc.local Compatibility
[Service]
Type=forking
ExecStart=/bin/sleep 1000
TimeoutSec=0
RemainAfterExit=yes
After=network.target
[Install]
WantedBy=multi-user.target
The unit is well started (a process sleep 1000 exists). But with a type=forking, systemd is supposed to hang in this case. Instead, the graphical.target is launched, systemctl list-units mention it as dead, but the display manager is started before the sleep 1000 completes. Ho can I force systemd to wait?
Last edited by olive (2015-03-16 16:49:34)

olive, now you're making even less sense. I didn't say the sleep example was stupid and I didn't question your reasons for doing/wanting this.
I suggested you add "Before=display-manager.service" and you respond "I added Before=graphical.target and it didn't change anything."
I also tried to explain why systemd has no reason to delay the display-manager.service. You could have asked for further clarification, as berbae has now done. Let's try a longer explanation.
Service startup
Services can be started in different ways, as configured with Type=. This determines when a service is considered "started" (or when the service's start-up is considered finished). When a service reaches this state (some time after being started), units that are supposed to start After= this service will be started (and no sooner).
With simple systemd has no further information about the start-up process. It launches whatever you specify in ExecStart and this is the main process that continues to run till the service stops. systemd assumes this type of service is started immediately. All the other types have some way for the process to indicate to systemd (either directly or indirectly) when it has finished starting.
Actually oneshot is also a bit special and that is where RemainAfterExit comes in. For oneshot, systemd waits for the process to exit before it starts any follow-up units (and with multiple ExecStarts I assume it waits for all of them). So that automatically leads to the scheme in berbae's last post. However, with RemainAfterExit, the unit remains active even though the process has exited, so this makes it look more like "normal" service with
begin of unit/startup ---- end of startup ------ end of unit
This is the relevant behavior for this thread. First sleep starts, then after 1000 seconds, start-up finishes and follow-up units will be started. Then either the unit dies, or (with RemainAfterExit) it stays "active".
The man page describes how "end of startup" is determined for each Type.
Targets
Targets are meant to group units together, to provide synchronization points (and replace runlevels). When you start a target, all its units will be started (in parallel if possible). The man page says:
Unless DefaultDependencies= is set to false, target units will
implicitly complement all configured dependencies of type Wants=,
Requires=, RequiresOverridable= with dependencies of type After= if the
units in question also have DefaultDependencies=true.
This means that (by default) when a target is requested, all it units are started first. Only after all units have finished starting, the target itself will be started (and since the target doesn't do anything by itself, this startup is basically instantaneous). Without this dependency, the order between the target and its units is unspecified, so in theory the target could finish starting immediately while its units are still being started.
Back to olive
graphical.target has these DefaultDependencies, so it is not started until all its units (like display-manager.service) and other After= dependencies (like multi-user.target) have finished starting. Your sleep service has to be started before multi-user.target starts (again due to default target dependencies). So first display-manager and the sleep service are started and after 1000 seconds, the sleep service finishes starting and then (assuming all other dependencies were quicker) multi-user.target is started and graphical.target as well (assuming display-manager didn't need 1000 seconds).
If you want display-manager.service after the sleep service, add a Before/After line to specify that (this was your original goal and my suggestion).
olive wrote wrote:However, units that are parts of the graphical target are still launched before the graphical target become active. I am still unable to completely delay the starts of the graphical target before a specific unit completes.
It should be clear now how this works. "units that are part of the graphical target" can only mean "units that are wanted/required by the graphical target" but that is basically all the units that are started when you boot your system, because multi-user.target is a part of graphical.target. And your sleep service is a part of multi-user.target, so in fact you're saying you want to delay starting the sleep service until the sleep service completes
What you probably intended was to delay all units that are a part of graphical.target but not of multi-user.target until after the sleep service. I can't think of an easy (or even good) way to do this and this post is already too long, so I'll table that for now.

Why my Firefox always lack and why I have to wait for minutes to open a page?

Dear customer support officer,
Why my Firefox always lack after I have update with Window 7 Service Pack 1? ... and why I have to wait for minutes to open a page?
I discovered from the "Task Manager", every time when Firefox is lack, it took up 100% of my "CPU Useage".
Below, kindly find my version spec for your investigation convenience. Many thanks in advance for your prompt support : )
Sincerely yours,
Charmayne
Application Basics
Name
Firefox
Version
5.0
User Agent
Mozilla/5.0 (Windows NT 6.1; WOW64; rv:5.0) Gecko/20100101 Firefox/5.0
Profile Directory
Open Containing Folder
Enabled Plugins
about:plugins
Build Configuration
about:buildconfig
Extensions
Name
Version
Enabled
ID
Better Facebook!
5.852
true
[email protected]
Java Console
6.0.20
true
{CAFEEFAC-0016-0000-0020-ABCDEFFEDCBA}
Java Console
6.0.22
true
{CAFEEFAC-0016-0000-0022-ABCDEFFEDCBA}
Java Console
6.0.23
true
{CAFEEFAC-0016-0000-0023-ABCDEFFEDCBA}
Java Console
6.0.24
true
{CAFEEFAC-0016-0000-0024-ABCDEFFEDCBA}
Java Console
6.0.26
true
{CAFEEFAC-0016-0000-0026-ABCDEFFEDCBA}
RealPlayer Browser Record Plugin
14.0.3
false
{ABDE892B-13A8-4d1b-88E6-365A6E755758}
Modified Preferences
Name
Value
accessibility.blockautorefresh
true
accessibility.typeaheadfind
true
accessibility.typeaheadfind.flashBar
0
browser.history_expire_days.mirror
180
browser.places.smartBookmarksVersion
2
browser.startup.homepage
http://www.google.com/webhp?hl=en
browser.startup.homepage_override.buildID
20110615151330
browser.startup.homepage_override.mstone
rv:5.0
browser.tabs.loadInBackground
false
dom.disable_open_during_load
false
extensions.lastAppVersion
5.0
keyword.URL
http://mystart.incredimail.com/?loc=ff_address_bar&a=ICetqQnqJ0&search=
network.cookie.prefsMigrated
true
places.database.lastMaintenance
1311818987
places.history.expiration.transient_current_max_pages
64401
places.last_vacuum
1298980389
print.print_printer
Microsoft XPS Document Writer
print.printer_Microsoft_XPS_Document_Writer.print_bgcolor
false
print.printer_Microsoft_XPS_Document_Writer.print_bgimages
false
print.printer_Microsoft_XPS_Document_Writer.print_command
print.printer_Microsoft_XPS_Document_Writer.print_downloadfonts
false
print.printer_Microsoft_XPS_Document_Writer.print_edge_bottom
0
print.printer_Microsoft_XPS_Document_Writer.print_edge_left
0
print.printer_Microsoft_XPS_Document_Writer.print_edge_right
0
print.printer_Microsoft_XPS_Document_Writer.print_edge_top
0
print.printer_Microsoft_XPS_Document_Writer.print_evenpages
true
print.printer_Microsoft_XPS_Document_Writer.print_footercenter
print.printer_Microsoft_XPS_Document_Writer.print_footerleft
&PT
print.printer_Microsoft_XPS_Document_Writer.print_footerright
&D
print.printer_Microsoft_XPS_Document_Writer.print_headercenter
print.printer_Microsoft_XPS_Document_Writer.print_headerleft
&T
print.printer_Microsoft_XPS_Document_Writer.print_headerright
&U
print.printer_Microsoft_XPS_Document_Writer.print_in_color
true
print.printer_Microsoft_XPS_Document_Writer.print_margin_bottom
0.5
print.printer_Microsoft_XPS_Document_Writer.print_margin_left
0.5
print.printer_Microsoft_XPS_Document_Writer.print_margin_right
0.5
print.printer_Microsoft_XPS_Document_Writer.print_margin_top
0.5
print.printer_Microsoft_XPS_Document_Writer.print_oddpages
true
print.printer_Microsoft_XPS_Document_Writer.print_orientation
0
print.printer_Microsoft_XPS_Document_Writer.print_pagedelay
500
print.printer_Microsoft_XPS_Document_Writer.print_paper_data
1
print.printer_Microsoft_XPS_Document_Writer.print_paper_height
11.00
print.printer_Microsoft_XPS_Document_Writer.print_paper_size_type
0
print.printer_Microsoft_XPS_Document_Writer.print_paper_size_unit
0
print.printer_Microsoft_XPS_Document_Writer.print_paper_width
8.50
print.printer_Microsoft_XPS_Document_Writer.print_reversed
false
print.printer_Microsoft_XPS_Document_Writer.print_scaling
1.00
print.printer_Microsoft_XPS_Document_Writer.print_shrink_to_fit
false
print.printer_Microsoft_XPS_Document_Writer.print_to_file
false
print.printer_Microsoft_XPS_Document_Writer.print_unwriteable_margin_bottom
0
print.printer_Microsoft_XPS_Document_Writer.print_unwriteable_margin_left
0
print.printer_Microsoft_XPS_Document_Writer.print_unwriteable_margin_right
0
print.printer_Microsoft_XPS_Document_Writer.print_unwriteable_margin_top
0
privacy.sanitize.migrateFx3Prefs
true
security.default_personal_cert
Select Automatically
security.warn_viewing_mixed
false
Graphics
Adapter Description
NVIDIA GeForce G102M
Vendor ID
10de
Device ID
0873
Adapter RAM
512
Adapter Drivers
nvd3dumx,nvwgf2umx,nvwgf2umx nvd3dum,nvwgf2um,nvwgf2um
Driver Version
8.15.11.8631
Driver Date
7-1-2009
Direct2D Enabled
Blocked on your graphics driver. Try updating your graphics driver to version 257.21 or newer.
DirectWrite Enabled
false (6.1.7601.17563, font cache n/a)
WebGL Renderer
(WebGL unavailable)
GPU Accelerated Windows
0/1

upgrade your browser to Firefox 8 and check
* getfirefox.com

Hi, why can't I use the iMessage on my iPhone? I've already had my apple id email on it but it keeps saying "waiting for activation" always like that. No progress. Could anybody help me on this? Cheers

Hi, why can't I use the iMessage on my iPhone? I've already had my apple id email on it but it keeps saying "waiting for activation" always like that. No progress. Could anybody help me on this? Cheers

I have an old iPod Touch with old software that can no longer be updated:
iOS version 6.1.6
I've been searching for a solution to my iMessage login problem for months and tried everything from those frustrating links and all the tips from other users.
Here is what finally worked:
1) Settings > Privacy > Location Services > On
2) Settings > General > Date & Time > Set Automatically > On
3) Reboot device until Apple logo appears
4) Settings > Messages > Sign In

HT201413 Why is it my songs or none of my information appearing in my ipod? What can i do? its been a whole 2 days connected to my itunes and it still says waiting for items to copy

Why is it my songs or none of my information appearing in my ipod? What can i do? its been a whole 2 days connected to my itunes and it still says waiting for items to copy

my iPad it get stuck on step 8 with a prompt that says "waiting to copy items" it stays on like that for hours
Reset your iPad.
Hold the On/Off Sleep/Wake button and the Home button down at the same time for at least ten seconds, until the Apple logo appears.
I recently upgraded to to the iOS 5 on my iMac and iPad
You don't need to manually sync using iOS 5.
Help here > Apple - iCloud - Learn how to set up iCloud on all your devices.
Message was edited by: Carolyn

Why does Lightroom 4.3 use very high cpu when waiting for user to click OK?

I saved metadata for 52 photos.
Lightroom 4.3 couldn't save metadata for 2 of the photos and opened a window to tell me so. (It had no problem saving metadata on second attempt.)
While it waited for my response and wasn't doing any work, it was using over 50% of my CPU.
Why?
Windows 7 is 32-bit Professional.
Processor: Intel Core i5 750 Processor 2.66 GHz
Here's my system info as reported by Lightroom.
Lightroom version: 4.3 [865747]
Operating system: Windows 7 Business Edition
Version: 6.1 [7601]
Application architecture: x86
System architecture: x86
Logical processor count: 4
Processor speed: 2.7 GHz
Built-in memory: 3579.4 MB
Real memory available to Lightroom: 716.8 MB
Real memory used by Lightroom: 710.9 MB (99.1%)
Virtual memory used by Lightroom: 847.9 MB
Memory cache size: 2.0 MB
Maximum thread count used by Camera Raw: 4
System DPI setting: 96 DPI
Desktop composition enabled: Yes
Displays: 1) 1920x1080
Application folder: C:\Program Files\Adobe\Adobe Photoshop Lightroom 4.3
Library Path: D:\Users\Calvin\Pictures\My Lightroom\lightroom\lightroom4\lightroom4.lrcat
Settings Folder: C:\Users\Calvin\AppData\Roaming\Adobe\Lightroom
Adapter #1: Vendor : 10de
    Device : 640
    Subsystem : c9593842
    Revision : a1
    Video Memory : 1007
AudioDeviceIOBlockSize: 1024
AudioDeviceName: Speakers (Realtek High Definition Audio)
AudioDeviceNumberOfChannels: 2
AudioDeviceSampleRate: 44100
Build: Uninitialized
Direct2DEnabled: false
GL_ALPHA_BITS: 0
GL_BLUE_BITS: 8
GL_GREEN_BITS: 8
GL_MAX_3D_TEXTURE_SIZE: 2048
GL_MAX_TEXTURE_SIZE: 8192
GL_MAX_TEXTURE_UNITS: 4
GL_MAX_VIEWPORT_DIMS: 8192,8192
GL_RED_BITS: 8
GL_RENDERER: GeForce 9500 GT/PCIe/SSE2
GL_SHADING_LANGUAGE_VERSION: 3.30 NVIDIA via Cg compiler
GL_VENDOR: NVIDIA Corporation
GL_VERSION: 3.3.0
OGLEnabled: true
OGLPresent: true
GL_EXTENSIONS: GL_ARB_arrays_of_arrays GL_ARB_base_instance GL_ARB_blend_func_extended GL_ARB_clear_buffer_object GL_ARB_color_buffer_float GL_ARB_compatibility GL_ARB_compressed_texture_pixel_storage GL_ARB_conservative_depth GL_ARB_copy_buffer GL_ARB_copy_image GL_ARB_debug_output GL_ARB_depth_buffer_float GL_ARB_depth_clamp GL_ARB_depth_texture GL_ARB_draw_buffers GL_ARB_draw_elements_base_vertex GL_ARB_draw_instanced GL_ARB_ES2_compatibility GL_ARB_ES3_compatibility GL_ARB_explicit_attrib_location GL_ARB_explicit_uniform_location GL_ARB_fragment_coord_conventions GL_ARB_fragment_layer_viewport GL_ARB_fragment_program GL_ARB_fragment_program_shadow GL_ARB_fragment_shader GL_ARB_framebuffer_no_attachments GL_ARB_framebuffer_object GL_ARB_framebuffer_sRGB GL_ARB_geometry_shader4 GL_ARB_get_program_binary GL_ARB_half_float_pixel GL_ARB_half_float_vertex GL_ARB_imaging GL_ARB_instanced_arrays GL_ARB_internalformat_query GL_ARB_internalformat_query2 GL_ARB_invalidate_subdata GL_ARB_map_buffer_alignment GL_ARB_map_buffer_range GL_ARB_multisample GL_ARB_multitexture GL_ARB_occlusion_query GL_ARB_occlusion_query2 GL_ARB_pixel_buffer_object GL_ARB_point_parameters GL_ARB_point_sprite GL_ARB_program_interface_query GL_ARB_provoking_vertex GL_ARB_robust_buffer_access_behavior GL_ARB_robustness GL_ARB_sampler_objects GL_ARB_seamless_cube_map GL_ARB_separate_shader_objects GL_ARB_shader_bit_encoding GL_ARB_shader_objects GL_ARB_shader_texture_lod GL_ARB_shading_language_100 GL_ARB_shading_language_420pack GL_ARB_shading_language_include GL_ARB_shading_language_packing GL_ARB_shadow GL_ARB_stencil_texturing GL_ARB_sync GL_ARB_texture_border_clamp GL_ARB_texture_buffer_object GL_ARB_texture_buffer_range GL_ARB_texture_compression GL_ARB_texture_compression_rgtc GL_ARB_texture_cube_map GL_ARB_texture_env_add GL_ARB_texture_env_combine GL_ARB_texture_env_crossbar GL_ARB_texture_env_dot3 GL_ARB_texture_float GL_ARB_texture_mirrored_repeat GL_ARB_texture_multisample GL_ARB_texture_non_power_of_two GL_ARB_texture_query_levels GL_ARB_texture_rectangle GL_ARB_texture_rg GL_ARB_texture_rgb10_a2ui GL_ARB_texture_storage GL_ARB_texture_storage_multisample GL_ARB_texture_swizzle GL_ARB_texture_view GL_ARB_timer_query GL_ARB_transpose_matrix GL_ARB_uniform_buffer_object GL_ARB_vertex_array_bgra GL_ARB_vertex_array_object GL_ARB_vertex_attrib_binding GL_ARB_vertex_buffer_object GL_ARB_vertex_program GL_ARB_vertex_shader GL_ARB_vertex_type_2_10_10_10_rev GL_ARB_viewport_array GL_ARB_window_pos GL_ATI_draw_buffers GL_ATI_texture_float GL_ATI_texture_mirror_once GL_S3_s3tc GL_EXT_texture_env_add GL_EXT_abgr GL_EXT_bgra GL_EXT_bindable_uniform GL_EXT_blend_color GL_EXT_blend_equation_separate GL_EXT_blend_func_separate GL_EXT_blend_minmax GL_EXT_blend_subtract GL_EXT_compiled_vertex_array GL_EXT_Cg_shader GL_EXT_depth_bounds_test GL_EXT_direct_state_access GL_EXT_draw_buffers2 GL_EXT_draw_instanced GL_EXT_draw_range_elements GL_EXT_fog_coord GL_EXT_framebuffer_blit GL_EXT_framebuffer_multisample GL_EXTX_framebuffer_mixed_formats GL_EXT_framebuffer_multisample_blit_scaled GL_EXT_framebuffer_object GL_EXT_framebuffer_sRGB GL_EXT_geometry_shader4 GL_EXT_gpu_program_parameters GL_EXT_gpu_shader4 GL_EXT_multi_draw_arrays GL_EXT_packed_depth_stencil GL_EXT_packed_float GL_EXT_packed_pixels GL_EXT_pixel_buffer_object GL_EXT_point_parameters GL_EXT_provoking_vertex GL_EXT_rescale_normal GL_EXT_secondary_color GL_EXT_separate_shader_objects GL_EXT_separate_specular_color GL_EXT_shadow_funcs GL_EXT_stencil_two_side GL_EXT_stencil_wrap GL_EXT_texture3D GL_EXT_texture_array GL_EXT_texture_buffer_object GL_EXT_texture_compression_dxt1 GL_EXT_texture_compression_latc GL_EXT_texture_compression_rgtc GL_EXT_texture_compression_s3tc GL_EXT_texture_cube_map GL_EXT_texture_edge_clamp GL_EXT_texture_env_combine GL_EXT_texture_env_dot3 GL_EXT_texture_filter_anisotropic GL_EXT_texture_integer GL_EXT_texture_lod GL_EXT_texture_lod_bias GL_EXT_texture_mirror_clamp GL_EXT_texture_object GL_EXT_texture_shared_exponent GL_EXT_texture_sRGB GL_EXT_texture_sRGB_decode GL_EXT_texture_storage GL_EXT_texture_swizzle GL_EXT_timer_query GL_EXT_vertex_array GL_EXT_vertex_array_bgra GL_EXT_import_sync_object GL_IBM_rasterpos_clip GL_IBM_texture_mirrored_repeat GL_KHR_debug GL_KTX_buffer_region GL_NV_blend_square GL_NV_conditional_render GL_NV_copy_depth_to_color GL_NV_copy_image GL_NV_depth_buffer_float GL_NV_depth_clamp GL_NV_ES1_1_compatibility GL_NV_explicit_multisample GL_NV_fence GL_NV_float_buffer GL_NV_fog_distance GL_NV_fragment_program GL_NV_fragment_program_option GL_NV_fragment_program2 GL_NV_framebuffer_multisample_coverage GL_NV_geometry_shader4 GL_NV_gpu_program4 GL_NV_half_float GL_NV_light_max_exponent GL_NV_multisample_coverage GL_NV_multisample_filter_hint GL_NV_occlusion_query GL_NV_packed_depth_stencil GL_NV_parameter_buffer_object GL_NV_parameter_buffer_object2 GL_NV_path_rendering GL_NV_pixel_data_range GL_NV_point_sprite GL_NV_primitive_restart GL_NV_register_combiners GL_NV_register_combiners2 GL_NV_shader_buffer_load GL_NV_texgen_reflection GL_NV_texture_barrier GL_NV_texture_compression_vtc GL_NV_texture_env_combine4 GL_NV_texture_expand_normal GL_NV_texture_multisample GL_NV_texture_rectangle GL_NV_texture_shader GL_NV_texture_shader2 GL_NV_texture_shader3 GL_NV_transform_feedback GL_NV_vertex_array_range GL_NV_vertex_array_range2 GL_NV_vertex_buffer_unified_memory GL_NV_vertex_program GL_NV_vertex_program1_1 GL_NV_vertex_program2 GL_NV_vertex_program2_option GL_NV_vertex_program3 GL_NVX_conditional_render GL_NVX_gpu_memory_info GL_SGIS_generate_mipmap GL_SGIS_texture_lod GL_SGIX_depth_texture GL_SGIX_shadow GL_SUN_slice_accum GL_WIN_swap_hint WGL_EXT_swap_control

I don't think so.
I have enough experience with LR to know what to expect for various activities.
Previews for all photos had been rendered long before I initiated the Save Metadata.
Metadata for 50 of the 52 files had already been written.
The high cpu had gone on for at least 5 minutes.   I switched to another app imediately after initiating the Save Metadata for the 52 files and only went back to LR when I heard my CPU fan running for a long time.
When I got back to LR, I saw the "Could not save metadata" window. I clicked "Show in Library" and OK. As soon as I did that, CPU usage went back to normal.
I've experienced the exact same scenario, where LR can't save metadata for all photos and I've never had LR get stuck consuming a very large amount of CPU.
As a test, I selected 118 other photos, changed metadata for all of them and then selected all and saved metadata. LR took about 20 seconds to save metadata for all 118 and LR CPU usage never went above 17%. The difference is that LR did not show the "Could not save metadata" window.

Why does File Explorer Seem to Wait for End-to-End Confirmation?

For quite a few versions now, when copying large blocks of files from place to place it seems like Explorer adds an arbitrary delay or maybe waits for confirmation internally that every file has been actually written to the disk before continuing.
On a modern computer with plenty of RAM for cache and a massively powerful SSD-based I/O system (capable of sustaining gigabytes per second of throughput),
why should we ever wait for a copy of a few hundred megabytes of files? Theoretically it should complete in a second or two.
In fact, back on XP one could observe exactly the behavior I'm describing - file transfers - especially on hard disk but even over the network - would proceed at a very breakneck pace.
Yet it's not uncommon to see miniscule transfer speeds while copying groups of files that even the oldest, cheapest hard drive could sustain...
What's the setting to have Explorer stop waiting and just get on with the copy, filling the cache with the data to be written later? Some of us don't want to wait that extra minute to get the job done. I know whomever programmed the cutesy
little graph wants to make sure we all see it, but...
-Noel
Detailed how-to in my eBooks:
Configure The Windows 7 "To Work" Options
Configure The Windows 8 "To Work" Options

Start Firefox in <u>[[Safe Mode|Safe Mode]]</u> to check if one of the extensions (Firefox/Tools > Add-ons > Extensions) or if hardware acceleration is causing the problem (switch to the DEFAULT theme: Firefox/Tools > Add-ons > Appearance).
*Do NOT click the Reset button on the Safe mode start window or otherwise make changes.
*https://support.mozilla.org/kb/Safe+Mode
*https://support.mozilla.org/kb/Troubleshooting+extensions+and+themes
You can check for problems with the places.sqlite database file in the Firefox Profile Folder.
*http://kb.mozillazine.org/Bookmarks_history_and_toolbar_buttons_not_working_-_Firefox
*https://support.mozilla.org/kb/Bookmarks+not+saved#w_fix-the-bookmarks-file
You can check for problems with the sessionstore.js and sessionstore.bak files in the Firefox Profile Folder that store session data.
Delete the sessionstore.js file and possible sessionstore-##.js files with a number and sessionstore.bak in the Firefox Profile Folder.
*Help > Troubleshooting Information > Profile Directory: Open Containing Folder
*http://kb.mozillazine.org/Profile_folder_-_Firefox
Deleting sessionstore.js will cause App Tabs and Tab Groups and open and closed (undo) tabs to get lost, so you will have to create them again (make a note or bookmark them).
*http://kb.mozillazine.org/Multiple_profile_files_created
Create a new profile as a test to check if your current profile is causing the problems.
See "Creating a profile":
*https://support.mozilla.org/kb/profile-manager-create-and-remove-firefox-profiles
*http://kb.mozillazine.org/Standard_diagnostic_-_Firefox#Profile_issues
If the new profile works then you can transfer some files from an existing profile to the new profile, but be careful not to copy corrupted files.
*http://kb.mozillazine.org/Transferring_data_to_a_new_profile_-_Firefox

I just updated my iphone to IOS 7 and cannot get my imessage to work, it keeps saying "waiting for activation" nothing i have read online has helped me try to fix the problem. why is it doing this and how can i fix it?

I just updated my iphone to IOS 7 and cannot get my imessage to work, it keeps saying "waiting for activation" nothing i have read online has helped me try to fix the problem. why is it doing this and how can i fix it?

Here's a good troubleshooting article about imessage "waiting for activation".
http://support.apple.com/kb/TS4268

Systemd: why am I waiting for wicd/mysqld?

Similar Messages

Maybe you are looking for