[solved]lvm volumes no longer auto mount after update to systemd 210-2

Note: I don't have an initramfs, it's a statically compiled kernel. I can get machine to boot if I manually mount all lvm volumes by hand. Thankfully my root was not on the lvm. fstab is as follows :
tmpfs           /tmp    tmpfs   nodev,noatime,nosuid            0 0
LABEL=dump      /dump   ext4    defaults,noatime                0 1
LABEL=home      /home   ext4    defaults,noatime,discard,user_xattr     0 1
LABEL=root      /       ext4    defaults,noatime,discard        0 1
LABEL=var       /var    ext4    defaults,noatime                0 1
LABEL=swap      swap    swap    defaults                        0 0
LABEL=local-compile     /var/abs/local  btrfs   defaults,noatime        0 1
Do I need to make any changes to configuration somewhere for lvm ?
Last edited by anish (2014-03-05 12:15:42)

My guess is that this has nothing to do with LVM at all. See http://cgit.freedesktop.org/systemd/sys … d=v210#n39.

Similar Messages

  • [SOLVED] vi (vim) no longer works properly after updating the system

    After updating the system with pacman -Syu vi stopped working. All syntax colors are gone, and everything is grey. When I press i to enter "insert" mode, editing is not visible. Changes are obscure and you can't tell what you are modifying.  Quitting with :q will still prompt you to use :q! to abort changes, even if no changes were visibly made.
    When scrolling to the beginning or end of a file, the screen flashes with grey glitch like areas.  What happened to my vi!?!?!?!?!?
    This all happened while following the beginner's guide to install arch linux.  I realized this when trying to arbitrarily read a test file I made directly after updating.
    The problems continued to be visible when installing and setting up sudo (those steps are the next steps that require vi)...  I think the sudo installation worked... but my vi is horribly glitchy
    Any ideas?
    Last edited by trusktr (2010-02-19 07:19:55)

    Setting EDITOR does not help in every case. For instance, visudo is by default hard linked to vi. (You can change this, I know. )
    But in fact, vi is only a symlink to ex. So I simply renamed this link and put another symlink to vim (vim-big in my case since I in fact do use the gvim package).
    /usr/bin/vi -> vim-big
    /usr/bin/vi-simple -> ex
    The drawback is that I have to set those links on every vi-update. (But I sure will remember...)
    Last edited by bernarcher (2010-02-19 00:58:57)

  • Trying to email file from adobe reader 11.0 email addresses will not longer auto complete after moving to office 365

    trying to email file from adobe reader 11.0 email addresses will not longer auto complete after moving to office 365. It did work with older versions of outlook. Tried changing to global address book. It will only access global address book offline

    I have the same issue.  On a clean machine with Office 2013 64 bit installed.

  • Ipod classic won't mount after updating to itunes 11.0.2

    ipod classic won't mount after updating to itunes 11.0.2.
    I updated to itunes 11.0.2 today, after delaying it for a looong time (I have it @ work and don't like the new layout).
    Since then, none of my ipods will mount/show up/update. I've tried all USB ports, 3 ipods, 3 cords. Wondering if you know of any issues. I've restarted the mac about 15-20 times today since as soon as I hook up an ipod, itunes immediately spins the beach ball and won't let me click out of it.
    I've restarted the ipods 10+ times each.
    All of the ipods DO show up on my desktop though. Just not in itunes anywhere with 11.0.2.
    One more thing: It's not the cables or the ipods: they both mount fine when connected to my laptop (running old *** 10.4.11 and itunes 9.)
    Machine is a Mac Pro running 10.6.8.

    Finding this Post took some time but I thought it was me talking when I read it. I was having the exact same issue. I have a G3 I've been upgrading like mad, including a Sonnet G4-500 CPU a Maxtor 60gb & 80gb HDs 1gb of RAM a new LaCie Firewire800 PCI card Graphics card etc. the latest was installing Panther 10.3.9 on the new 80gb HD and also swapping out the old CD-ROM and replacing with the (Apple standard) Pioneer DVD-RW DVR-110D combo drive in it's place. got everything up and booted and poof! no burning. Toast worked read/write no problem. iTunes could read and import no problem, but wouldn't burn a CD.
    Downloaded "PatchBurn 3.1.3" installed, re-booted and all is OK in burner land again :>)
    I wanted to just post my additional thanks to the lead to Patchburner, and I'm going to donate to the cause. It's worth a $20 donation just for my joy of not throwing this computer out the window!!

  • Head phone volume controls are not working after updating to ios 6.1 y?

    head phone volume controls are not working after updating to ios 6.1 y?

    I have tried my head phone with other iphone still the same problem may be my head phones has been not working need to chek my iphone with other head phones which are working

  • [SOLVED] Volume groups not showing up after update

    nunikasi wrote:
    Hello!
    I run a arch linux setup with LVM volumes on a LUKS encrypted drive /dev/sda. The header resides in the initramfs-linux-ck.img (So kernel and header are on a USB stick and my hard drive is completely encrypted).
    Everything worked nicely with this setup until today. I ran a
    pacman -Syu
    and the kernel was updated as normal and made a new initramfs-linux-ck.img on the usb stick (mounted in /boot). This is the way I always updated the kernel, and it always worked, but for some reason, after the reboot, and after typing my passphrase I got an error
    ERROR: device '/dev/mapper/nunikasi-root' not found. Skipping fsck.
    This was strange, so I booted the latest arch live-cd and did a
    cryptsetup luksOpen /dev/sda nunikasi --header (pathToHeaderFile)
    and entered the passphrase and still there are no volume groups in /dev/mapper. Am I wrong in thinking that this command should load my volume groups as
    /dev/mapper/nunikasi-root
    and
    /dev/mapper/nunikasi-home
    Running
    vgscan
    also reports no volume groups.
    Additional information:
    Last time I updated the kernel was around 24th of June.
    I did run pacman -r linux before the update, assuming there is no need for it since I run linux-ck. I hope this is not relevant.
    Do you know what went wrong?
    What was the problem?
    As I saw that dm-crypt had a problem with finding my logical volumes, I fired up
    cryptsetup luksOpen /dev/sda nunikasi --header (pathToHeaderFile)
    dhex /dev/mapper/nunikasi
    and found that the lvm metadata was cut in half. So I ran
    dhex /dev/mapper/nunikasi /dev/sda
    and quickly saw that there was an attempt to make a MBR on /dev/sda (I saw the boot signature 55 aa on offset 1FE-1FF). I remembered that I tried to use GParted some days earlier to format a memory stick, and I probably forgot to change from /dev/sda before creating a MBR. This is most probably what happened, and now I had to restore the metadata in some way.
    What was the solution?
    As I had never made a backup of the metadata, I knew that LVM makes one for you and puts it in /etc/lvm/backup/. So I fired up dhex on /dev/mapper/nunikasi and searched for it. Found the offset and did:
    dd if=/dev/mapper/nunikasi count=2148 skip=8928722944 of=lvm-metadata.txt iflag=skip_bytes,count_bytes
    Now I had the metadata backup and the right UUID for my physical volume. Only steps left were:
    pvcreate -ff -u [UUID] —restorefile lvm-metadata.txt /dev/mapper/nunikasi
    vgcfgrestore -f lvm-metadata.txt nunikasi
    vgchange -ay
    And my setup is working again!
    Have a nice day,
    nunikasi
    Last edited by nunikasi (2014-07-07 20:30:16)

    nunikasi wrote:
    clfarron4 wrote:Hmm... Have you tried breaking out an Arch installation disk and having a look with that?
    Yes, I wrote that in the original post.
    Sorry about that. I've just read it again.
    OK, based on the information you've given us (LVM on LUKS, VG=nunikasi and LVs=root,home, backed up header), I would have thought that the commands you issued in your original post would have unlocked it. I'm not going to make any assumptions about the header of the actual LUKS partition though.
    nunikasi wrote:I remember core/filesystems and some other core packages were updated.
    I've had a look through my pacman.log and I can't think of anything that might upset it (that said, I am quite tired). I run 5 (maybe 6) different kernels (3.10, 3.12, 3.14 and 3.15 branches) and I haven't had any problems with finding PVs, VGs and LVs on either of my systems.
    I'm at a loss as to what could be up right now and I'll this thread for tomorrow (because sleep beckons).
    EDIT: Wow. That's quite something.
    Last edited by clfarron4 (2014-07-08 11:21:46)

  • [SOLVED] Thunar (XFCE4) Does not Auto-mount USB Drive

    After reading some posts related to USB auto-mounting in Thunar and yet still having the problem, I decided to post this. Thunar used to detect the USB drives and auto-mount them. These days (I GUESS after moving to systemd), It cannot do so. Still, there is the icon of USB drive on the left side panel, but when I click on it to browse it, I get this error:
    Failed to mount "USB_LABLE".
    Error when getting information for file
    '/media/usbhd-sdc1': Transport endpoint is not connected.
    I am still able to use "sudo mount..." and get the job done, but I would prefer the convenient way it used to work. Here are some information about my system:
    command> cat ~/.xinitrc
    if [ -d /etc/X11/xinit/xinitrc.d ]; then
    for f in /etc/X11/xinit/xinitrc.d/*; do
    [ -x "$f" ] && . "$f"
    done
    unset f
    fi
    exec startxfce4
    command> loginctl show-session $XDG_SESSION_ID
    Id=1
    Timestamp=Sat, 2012-11-10 20:35:51 CET
    TimestampMonotonic=34276379
    DefaultControlGroup=name=systemd:/user/username/1
    VTNr=7
    Display=:0.0
    Remote=no
    RemoteUser=root
    Service=slim
    Leader=297
    Audit=1
    Type=x11
    Class=user
    Active=yes
    State=active
    KillProcesses=no
    IdleHint=no
    IdleSinceHint=0
    IdleSinceHintMonotonic=0
    command> systemctl status polkit
    polkit.service - Authorization Manager
    Loaded: loaded (/usr/lib/systemd/system/polkit.service; static)
    Active: active (running) since ...
    Docs: man:polkit(8)
    Main PID: 305 (polkitd)
    CGroup: name=systemd:/system/polkit.service
    305 /usr/lib/polkit-1/polkitd --no-debug
    command> dmesg
    Attached scsi generic sg1 type 0
    [sdc] 15470592 512-byte logical blocks: (7.92 GB/7.37 GiB)
    [sdc] Write Protect is off
    [sdc] Mode Sense: 23 00 00 00
    [sdc] No Caching mode page present
    [sdc] Assuming drive cache: write through
    [sdc] No Caching mode page present
    [sdc] Assuming drive cache: write through sdc: sdc1
    [sdc] No Caching mode page present
    [sdc] Assuming drive cache: write through
    [sdc] Attached SCSI removable disk
    I'd rather not edit the /etc/fstab; the way Thunar used to behave, was working with every new USB. I wonder if anybody can shed some lights.
    Last edited by Shahab (2012-11-10 21:56:24)

    The error looks suspiciously like one I had not so long ago and it turned out I still had an 11-media-by-label-auto-mount.rule in /etc/udev/rules.d.  Once I removed that and rebooted everything was fine again.

  • [solved] USB drives won't auto mount

    When I plug in a drive, I get this error message:
    Rejected send message, 1 matched rules; type="method_call", sender=":1.24" (uid=1000 pid=4499 comm="exo-mount) interface="org.freedesktop.Hal.Device.Volume" member="Mount" error name="(unset)" requested_reply=0 destination="org.freedesktop.Hal" (uid=0 pid=3069 comm="/usr/sbin/hald)).
    2nd harddrive:
    Rejected send message, 1 matched rules; type="method_call", sender=":1.20" (uid=1000 pid=3537 comm="exo-mount) interface="org.freedesktop.Hal.Device.Volume" member="Mount" error name="(unset)" requested_reply=0 destination="org.freedesktop.Hal" (uid=0 pid=3058 comm="/usr/sbin/hald)).
    There are fixes in other forums, but they are all radically differnet, and the one's I tried aren't working.
    I have an eee pc with xfce and slim.
    I know this is a perimssion problems since auto mount works fine for root. Could anyone tell me the (probably simple) fix for this? Thanks.
    Last edited by Meskarune (2010-04-15 04:21:08)

    HAL:
    http://wiki.archlinux.org/index.php/HAL#Troubleshooting
    Also check your .xinitrc and make sure your lines matches this:
    exec ck-launch-session startxfce4
    Lastly, you can also use udev to automount your drives:
    http://wiki.archlinux.org/index.php/Ude … SB_devices

  • DMG's not auto mounting after download

    I've recently switched to using Safari as my main browser, and I'm having trouble with DMG's not mounting after I successfully download them.
    I do have the option enabled 'Open "safe" files after downloading' turned on, and some files auto-open after downloading them, but not DMG's - and that seems to be what I most frequently download.
    I even tried creating a com.apple.DownloadAssessment.plist file and added DMG to the safe list, as discussed here. But that didn't seem to make any difference either.
    All in all I'm very happy with Safari, but have to get these darned DMG's to auto-mount like they are supposed to.
    Any and all ideas welcomed.

    Ok, I resolved this one myself.
    FlashMount 1.5.2 was the problem. FlashMount is a killer alternative to Apple's Disk Image Mounter in OSX but for some reason with Safari DMG's don't auto mount. There is no problem with Camino, not sure why this is happening which is unfortunate since FlashMount looks to be deprecated.
    FlashMount: Apple's Disk Image Mounter in OSX.

  • Archiso no longer auto-mounts drive

    I'm using a custom installation with archiso..
    It used to boot and auto-mount the drive with archisolabel="XXX" (where XXX is the drive label) to /bootmnt
    Now, updating to newest archiso-git it always brings me into maintanence mode (cannot mount drive at /dev/disk/by-label/arch)
    Typing "mount /dev/disk/by-label/arch /bootmnt; exit" works and finishes the init.
    I've tried setting the drive label on this -- however the new archiso doesn't seem to support that:
    [root@image64 iso]# tune2fs -L arch /dev/sdc1
    tune2fs 1.41.9 (22-Aug-2009)
    tune2fs: Bad magic number in super-block while trying to open /dev/sdc1
    Couldn't find valid filesystem superblock.
    Any ideas what I'm missing here?

    That’s correct Bob and that behaviour is fine for the purpose which it is intended i.e to relink when a job has moved in the filesystem or across workstations. The file selection/highlighting behaviour may just have been a quirk but it was a useful one in some specific scenarios. Mine was (magazine production workflow):
    Images are placed by a layout artist in the format they are supplied (usually JPGs). The job folder is then passed to a prepress operator to perform finished cutouts and retouching. They output a corrected PSD into the same job’s images folder. They alt+tab to Indesign, select the image and got to Relink. The app file browser window opens and the linked JPEG is highlighted. Immediately above/below it is the matching new PSD (if they’re sorted by name). It therefore becomes far less likely that the operator will select the wrong file to relink because of the new PSD’s immediate proximity to the JPG.
    With no highlighting the operator has to scroll/search for the file visually (with one eye on the window title bar to get the ridiculously long but fabulously descriptive filename :) to relink and this not only slows them down but also greatly increases the possibility of a selection error without the visual cue.
    This may sound like a trivial gripe, but when some layouts contain large numbers of images, some of which are visually similar (and therefore can not easily be spotted shifting when the Relink is committed) it becomes an issue.
    To be fair to Adobe:
    1. This is not a normal scenario for the vast majority of users.
    2. It was probably only a happy accident that files were highlighted in the first place.
    Anyway I have a workaround. I asked my picture editor to convert all images to PSD before they’re placed :-)

  • Lacie drive not mounting after updating to 10.4.8

    Hi,
    I have a 160gb Lacie d2 external hd, and after updating my OS to 10.4.8 in October, it will not mount. It's recognized in Disk Utility, but will not mount. I've tried repairing disk permissions from both my current OS and from the installer DVD, but it isn't helping and I keep getting the same message.
    When I first updated to 10.4.8 in October, my computer had problems re-starting (it would get stuck at the blue boot-up screen), so I had to turn it off by holding the power button. Ever since then, the lacie drive won't mount.
    Is there anything else I can do? I've thought about trying Disk Warrior, but if possible I'd like to save the $100 to buy it!
    Any advice? I would really appreciate it.

    What I think.
    The major changes occurred in the 10.4 original Tiger release. Due to the nature of what I believe the problem is 10.4.7 would just be changing how, where and when the issue(s) become most noticeable to you and not solve it. It will leave you hangin' somewhere else. This I/O API does effect everything. I only wanted to finish a movie with iMovie and set some clips at 00:05 f as I have done forever. Bought a new MacBook Pro specifically for OS X.4 and iMovie and all that was over. iMovie as well as many other Universal apps are IMO mostly non functional except at the OS and QT interface. All other Universal apps and devices cause it to choke and sputter as things pass through this very same I/O API that is causing the external HD issues. As for the PB G4, I was believing the age of the machine to be causing these failures then I had noticed many others developing the same issues on newer G4 machines. Most puzzling was the performance hit on the machines with the proper HW especially larger Core Image supported graphics cards as 10.4 has made this a very relevant piece of HW now. The more I read about the how's and why's of the changes in the architecture of the OS in the Developer Connection the more I realized that many issues that seem so unrelated are indeed caused by the same area and or error in this API. iTunes, Safari, iMovie, iPhoto, -.. CPU's, Fans, HD's, jpegs choking G5's and intels-.. plug n play's that worked yesterday not today, same machines/HW new OS.
    Photoshop CS and, an extremely resource greedy, 3D Modeling/database application running in Rosetta works fine. Animating 3D graphics on the fly without so much as a stutter everything calm and quiet. Open Safari and the comp gets too hot to handle the fans are screaming just displaying basic window graphics here at the Apple Discussion boards. Most times this is a text only forum for me as the MPB can't even process the window graphics, often the original posts push-pin graphic is the only one that will display.
    AFAICT Rosetta is just an application with no graphic user interface and it is not Universal Binary therefore avoiding this I/O kit as it was designed for the specific configuration of the MacIntel only and works fine. Apple's iLife and iWork apps especially, as well as any SW using this I/O Kit API for Universal Binary apps don't work properly. Anyone with a later G4 and especially a G5 with a good, Core Image supported, graphics card should be feeling like they have a new machine, not saying "hey my stuff isn't working anymore" or slow imports of files or processing.
    Personally I would:
    Start up from 10.3 install discs, back up my docs to external HD and re-partition the internal HD. At least two, IMO three partitions (do not journal OS partitions) would be the least. Install 10.3.9 on one 10.4+ on the (an)other. Docs on the third. Keep the OS partitions as small as possible while allowing for OS's extra "operating space". 3.9 only requires about 2-5 GB's above required space to install while OS 10.4 seems to need 5-10 GB that is always "free" depending on what you are doing and also allowing for any OS and app. updates that may come before the next OS X release. 3.9 is already maxed so one can assume no new news here.
    My G4's HD set up is 6 partitions as it is now mainly a slave hub between my MBP and my "legacy" products PB G3, serial devices, Zip drives, modems, SCSI devices, scanners, printers old apps/file formats. Apps and HW that are still useful but "max out" at a certain OS/comp configuration are installed on that OS's partition, i.e. QT w/MPEG-2, Virtual PC, or Photoshop plugins that were never developed or not worth the investment for OS X or the current release as they are not used often enough etc.
    5GB-9.2.2, 10GB-10.2, 15GB- 10.3.9, 20GB-10.4.6, 15 GB Apps. 35GB docs. Nothing gets written to any OS partitions unless absolutely required. All OS's share the apps they can (except 9 apps) and document partition. As far as I understand I should be able to use XGrid to use these other computers processors through the MBP. A "super computer" kind of set up with the G4 at the least, but documentation indicates it should work on any OS X so possibly my G3 as well which stopped at 10.1.
    You do not have to duplicate apps and I would install and update all through 3.9 even if you install them in the 10.4 Apps. folder. At most you may need to create a couple of folders in the OS's System Library for Application Support or plug-ins etc. If you fear one OS reading from the other's Library/System files you can unmount the other OS volumes but I have yet to see this happen without intentionally directing the OS to do so.
    I would do all my external back ups and device communication (cameras, HD's MIDI's etc) booting in 10.3 only. For me the G4 booted in Target disk mode seems to be the safest way to access an "external HD" via FW with the MBP. I have had zero problems with this method. A two step process for files that don't reside on the G4 but I'd rather be safe than sorry and I have already lost one HD that was completely unrecoverable (a mechanical rebuild lead to the discovery of overwritten files with driver type data and damaged disk surface from arcing). Small files I just access on the external HD's through G4 over the airport network. I have not used Bonjour in depth yet though will most likely incorporate that into everyday use as I was able to quickly transfer a few very large files to a friends MacBook with it. Used this Just after realizing the MBP lacks IRDA and neither of us had any cables with us.
    The above type of configuration would give you the ability to move forward with 10.4 and easily work around HW, SW and connectivity issues by booting into 10.3 when needed. This is a great way of trouble shooting OS and app issues. My MBP already has a partition waiting for Leopard. If the OS lacks something or has problems of it's own I can boot back into 10.4 quickly and easily. If all is well with Leopard 10.4 will definitely be removed. The G4 will never see Leopard except over a network.
    Sorry to be long winded. Hope this gives you some reasonable ideas. In a nutshell. I believe the problem is that the OS and QT are set to higher, more accurate standards (ISO's MPEG's, SMTP's, IEEE's etc) than in the past and the I/O API is unable to communicate/calculate and transfer the information properly between devices and apps.
    BTW when your LaCie appears to have given up the ghost and will not respond at all, before you toss the whole thing remove the HD and put it in a different enclosure. I have dealt with hundreds of these and the Firewire ports on the PC board become too hot and melt off. Repair is not possible and although this is a known issue with LaCie no attempts have been made to correct this and they will not sell you a service part to repair it. Replacement would require removal and replacement of two screws and two plugs. Most HD's I have removed are Western HD's and work fine in a new enclosure.
    HTH

  • [iPad2] The volume went to zero directly after update iOS 6 @_@

    After update to ios 6.
    The volume went to zero directly when i pressed volume down just once only.
    Is there anyone have the same problem?
    Or maybe there is any setting can solve this problem?

    There have been a few other discussions about this happening when updating the iPad. I haven't seen a fix. There is no specific setting that would affect this but you can try resetting all settings.
    Settings>General>Reset>Reset All Settings. You will have to enter all of your device settings again.... All of the settings in the settings app will have to be re-entered

  • Display no longer functions correctly after update

    After updating this morning (the only package updated being wayland), the display on my main computer (laptop still works fine) no longer works properly. It is a bit difficult to describe the problem: there is a constantly changing display of symbols in various colours, "behind" which the usual terminal messages are still legible, though a bit garbled. This began right after re-boot following the update. Because the problem is apparent immediately when the display starts with the manufacturer's logo, I thought at first my monitor had given up. But the same problem occurs on a replacement monitor, which leads me to think it is a software problem. Any hints -- or even better -- a solution? X won't start, making it pretty useless. I can still ssh into it from my laptop, but a real solution is required. My graphics card is NVidia, if that matters (Intel on my laptop).
    Many thanks!
    Thea
    PS I should add, I have read other posts from today regarding similar display issues, and this one appears to be different, although perhaps related. I retrograded the wayland package, but the problem remains. Wayland was the only package I updated-- that is, the only difference between pre-update (no problems) and post-update (dispaly does not work properly).
    PPS further details:
    1. The problem is already apparent at start-up (push the ON button): the computer (not the monitor) manufacturer name appears, but the display is in dashed lines.
    2. After Arch Linux boot and login, there are 5 vertical bands each about 4cm (1.5 ") wide of "shimmering" pixel colour squares spaced evenly across the screen, the intervening spaces are "normal" -- that is, display correctly and without problem. So to some extent, still workable. X will not start, giving me an error message:(/var/log/Xorg.0.log)
    NVIDIA: Failed to initialize the NVIDIA kernel module
    with the advice to consult kernel.log. However, this log (and all other kernel logs) is empty.
    3. When the monitor goes into standby mode, the "shimmering" bands are still visible.
    Update 1:
    After mesa update this afternoon (21 Feb.) video display returned to normal (ok, mesa depends on wayland) until trying unsuccessfully to start X. Since then (and also after a couple of reboots) the problem is the same. Am hoping the silence on this issue indicates that work is in progress in fixing it.
    Update 2:
    After a night in a cold office (I live in southern Ontario) and a literally cold boot (but no updates), everything appears to be back to normal.
    Still, it would be nice to know what the problem was.
    Update 3:
    So much for magic. This morning (23 Feb.) after normal system update (no obvious problematic packages relating to graphics) the display oroblem returned, as before. Fresh boot made no difference. What's going on??
    Am re-posting this as a new message. Monday, start of the week, who knows, maybe someone can help.
    Last edited by thea (2015-02-23 14:38:28)

    You are probably better discussing web design elsewhere such as on http://forums.mozillazine.org/viewforum.php?f=25
    There have been changes in Firefox as documented for example
    * https://developer.mozilla.org/en-US/docs/Firefox_15_for_developers
    * https://developer.mozilla.org/en-US/docs/Firefox_16_for_developers
    Is the website/application a publicly available one if so are you able to provide a link. Otherwise maybe post an example of code that is affected.
    You may also wish to check the code for validity with for instance http://validator.w3.org/

  • Adobe reader app takes longer to launch after update, why?

    After updating my adobe reader I have found that when every I try to launch the app it takes a significantly longer time to load then it used to. Is this the problem with the app itself or is it because I have updated my ipad to the newer ios system, ios 7?
    Thanks.

    Android 4.4 (KitKat) introduced big changes to SD card support.
    Android KitKat Blocks Some Access to Micro SD Cards
    You can find many other articles regarding the SD card problem by searching on the internet.
    We will be investigating the problem.
    To work around the problem in the meantime, could you copy some of the PDF files from your SD card to internal storage (e.g. /storage/emulated/0/...) and see if Adobe Reader can read from and write changes to PDF files on your internal storage.  (It should work based on my limited testing. But please verify it.)
    You can use any Android File Manager app to move/copy files.  Samsung phones and tablets typically has "My Files" as the built-in File Manager.
    Alternatively, you can transfer the PDF files to Acrobat.com (free cloud storage service) and access them from Adobe Reader.
    Please let us know if any of the suggested approaches work for you.
    Sorry for the inconvenience.

  • Always auto reboot after update 4.3

    im Z1 user from china, after update 4.3, auto reboot once a day,and yesterday i restore factory settings,but auto reboot also....>_<,help me please!

    As per the above advice, please see a step by step guide below:
    1. Download the PC Companion software from http://www.sonymobile.com/gb/tools/pc-companion/
    and install it on your PC.
    2. Install and open PC Companion then select Support Zone.
    3. Phone Software Update.
    4. Start.
    5. Repair Phone
    6. Continue
    7. Accept data removal
    8. Next
    9. Wait for prepare
    10. Select Phone
    11. Follow the connection steps
    Don't forget to mark posts that answers the topic as Accepted Solution. 
    If you find any post helpful, press Kudos.
    What are your thoughts about this forum? Let us know by doing this short survey.
     - Official Sony Xperia Support Staff
    If you're new to our forums make sure that you have read our Discussion guidelines.
    If you want to get in touch with the local support team for your country please visit our contact page.

Maybe you are looking for

  • Files on iPod not recognized by iTunes

    I have several files on the iPod that can not be displayed in the ipod section of iTunes. They were put on the iPod using iTunes, and the iPod has only ever been connected to this one computer. I get to the files on the ipod via artist, but when I co

  • Expense Report stuck in SFA status - on 9.0

    We are getting ready to implement Expense 9.0 and starting to test. We have submitted several expense reports and they are getting stuck in SFA (submission in progess). I checked the knowledge browser on metalink3 and the only thing I saw to check ou

  • Share troublehoot

    how can i fix the share function which is not working - tried both export fcpx project to master file and dvd

  • Personas not fully shown

    i downloaded firefox 8 and persona on top isn't fully visible, i also want more options on my toolbar and when i try to add items on toolbar lay out and press done it disappears, if to hard to solve how do i go back and reset previous toolbar, pleez?

  • How to approach troubleshooting?

    I have a new 10g (9.0.4) AS install on Sun Solaris; the infrastructure (minus the database which is on another server) and the middle tier are both on this box and in different oracle_homes. The infrastructure starts fine and authentication works wel