Sideloaded Custom Viewer (Multi-Issue) crashes after splash on KINDLE FIRE

We have successfully used the Adobe Digital Publishing suite and pushed our application to the iTunes App Store and the Android Marketplace.
Now, however, we are using the Viewer Builder to create an APK for the Amazon App Store.
The Viewer Builder process is the same as for the Android, and we are able to download and sign the YOURAPPNAME-AndroidViewer.apk.
We have sideloaded the APK to the Kindle Fire and succesfully installed it - but on load it REPEATEDLY crashes after the Splash screen.
These two comments also indicate the SAME BEHAVIOR:
http://forums.adobe.com/message/4050646#4050646
http://forums.adobe.com/message/4098598#4098598
...and they are from over a month ago.
The Kindle Fire is already, in only 3 months, the biggest and fastest selling Android tablet.
I haven't seen anything on the Adobe site or elsewhere about anyone having published a Viewer-Builder-built custom viewer to the Kindle Fire.
So... What is the status, Adobe?
<3,
A patient customer.

It's odd to say this, but that crash on the Amazon Fire is actually working as designed. The .apk file you create is built to allow for in-app purchases (even if it's free). If you sideload this unwrapped .apk file to your Fire, it will crash because -- as I understand it -- Amazon still hasn't enabled in-app purchases yet, so the unwrapped .apk file is basically looking for a sandbox that doesn't exist. However, if you submit the .apk file to Amazon, they will wrap it, and it should work as designed. If you want to test it, you can ask Amazon to send you the wrapped version, but it's easier just to submit it and test the live version before you announce its availability.
I went through this process with my DPS Tips app. It's now approved and in the Amazon Appstore. I haven't updated the publishing process doc yet. I was hoping to wait until Amazon got its subscriptions and in-app purchases up and running.

Similar Messages

Illustrator/indesign and premire pro cc 2014 crashes after splash screen

Hi, I can't figure out whats going on, I had CC running fine, the 2014 updates came and all software except photoshop crash after the splash screen. I have done everything I could think of. Verified fonts, I've uninstalled and re-installed creative cloud and the software. I ran adobe cleaner which get rid of the original CC software (I didn't want that to happen) I've deleted preferences, ran disk permissions and repair. CS6 software install and runs.
I am lost to say the least as to why photoshop CC 2014 works and yet, the others crash. Any Ideas?
Thanks.

Hi camdude,
Can you send the Adobe Illustrator CC 2014 crash logs to me at [email protected]
The steps to get the crash log are:
1) Open the finder app.
2) Press command +shift + g to open the "Go to the folder" dialog.
3) In the text edit field type "~/Library/Logs/DiagnosticReports".
4) This will take you the DiagnosticReports folder.
5) Please share the latest crash log file from this folder.
With Best Regards,
Raghuveer

Premiere CC crashing after splash page

Hello the following error message occurs after the splash page :
Adobe Premiere Pro CC quit unexpectedly. Click Reopen to open the application again. Click Report to see more detailed information and send a report to Apple.
The partial report is :
Process:         Adobe Premiere Pro CC [1266]
Path:            /Applications/Adobe Premiere Pro CC/Adobe Premiere Pro CC.app/Contents/MacOS/Adobe Premiere Pro CC
Identifier:      com.adobe.AdobePremierePro
Version:         7.1.0 (7.1.0)
Code Type:       X86-64 (Native)
Parent Process: launchd [220]
Responsible:     Adobe Premiere Pro CC [1266]
User ID:         503
Date/Time:       2013-11-21 20:03:35.365 -0500
OS Version:      Mac OS X 10.9 (13A3017)
Report Version: 11
Anonymous UUID: 9E9F4796-3DAD-DB63-3E56-479EC2D554DB
Sleep/Wake UUID: B8B8A6E9-1B55-43D9-9813-C2826D6321CD
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: EXC_I386_GPFLT
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0   com.adobe.dvaworkspace.framework    0x0000000106787535 dvaworkspace::workspace::Workspace::~Workspace() + 85
1   com.adobe.UIFramework.framework    0x000000010479a44f UIF::WorkspaceImpl::~WorkspaceImpl() + 15
2   com.adobe.UIFramework.framework    0x0000000104794b06 UIF::Workspace::~Workspace() + 38
3   libsystem_c.dylib             0x00007fff88f31841 __cxa_finalize + 177
4   libsystem_c.dylib             0x00007fff88f31aec exit + 22
5   com.adobe.AdobePremierePro        0x00000001000016ab start + 59
I’ve tried many un installs...re-installs. no luck.
Getting rid of permissions. no luck.
Installed lastest Java. no luck
Language settings to US English. no luck
The only thing that DOES work is changing users.
What's wrong with my old user profile? Premiere CS6 works in it? I've just migrated MBP's BTW.
Any ideas? This is VERY common I'm reading. Users are fed up. Adobe, please answer.

I'm not sure what you mean by "new user setting." User profile? Adobe Premiere Pro Prefs? Frankly, even if that detail were clear, I probably wouldn't have a good answer. I'm a tester, not a developer, and installation and program launch are not my areas of expertise.
The error message from AE specifying that it could not rename a file makes me wonder if it's a permissions issue with the old user profile. I know you reported "Getting rid of permissions. no luck." Can you elaborate on what you mean by that?
There's no arguing your point have Premiere Pro (and other apps) have had some issues running on Mavericks. In your first post, you listed off a few of them. To that list, you should add third party plug-ins (see, for example, Post #18 in this thread) and graphics drivers. Only a fraction of these issues are within Adobe's power to rectify; Premiere Pro resolved at least on such issue with the 7.1 update that was released about a week after Mavericks went live.
It's not uncommon for major new versions of operating systems to introduce problems--not only bugs within the new OS itself but curveballs for various programs, drivers, plug-ins, etc. Such issues take time to understand and address. If Mavericks has proven too disruptive in your case, then you might consider rolling back to 10.8. Several regulars on this forum have stated that they typically wait until at least the first patch.

After Effect CS6 crashes after splash screen

I cannot get After Effects to open. When I try to open the software, I get a splash screen, and then the window opens, but the it stops responding before the interface can appear. I thought the issue may have been my virus protection (norton), so I tried shutting down my firewall and restarting my computer. This seemed to work for me the first time I tried it; After Effect opened and everything seemed to work fine, but the next time I started the computer and opened the software it continued to crash, and what I thought was the solution no longer worked. Premiere, Photoshop,and Audition work fine. However, the trial version of FX Home's software, Hitfilm 2, gives me the same problem as well. I have tried alot to get both of these programs to work with no success. I would appreciate any suggestions as to how I might fix this.
Computer spec:
win 7 64-bit
intel i7 960 3.2ghz
12 gb ddr3
nvidia 560 ti

Updated to 310.7 from 306.97, but still no luck. When after effect stops responding there is sometimes a dialog box asking me if I want to send my information. This dialog box does not always appear every time I try to open after effects, but when it does, this is the additional information it gives me:
Files that help describe the problem:
C:\Users\Owner\AppData\Local\Temp\WER9F1C.tmp.WERInternalMetadata.xml
C:\Users\Owner\AppData\Local\Temp\WER193B.tmp.appcompat.txt
C:\Users\Owner\AppData\Local\Temp\WER19AA.tmp.mdmp
However I can't find these files on my computer. This is also the same information I get when trying to open FX Home's software, except when I try to open that software I do not get a splash screen or window, the .exe shows up for a few seconds in the task manager and disappears.

Captivate 5 crashes after splash screen

I've downloaded the trial version of Captivate 5 and every time I try to start the program, I can't get passed the splash screen.
I'm running:
Win7 Home Premium, 64-bit
i5 2.27 GHz
4 GB RAM
350+ GB memory available
Upon initial launch, program crashed and produced an error message: "Adobe Captivate is not responding." I changed the AdobeCaptivate.exe file properties to "Run this program in compatibility for: (tried all options)" and "Run this program as an administrator" and no luck. Making the file compatible to a previous OS version caused the file to simply freeze (rather than crash) but prevented the Trial Activation prompt when operating as compatible for versions earlier than Vista.
I've tried uninstalling and reinstalling 6 times, after following various recommendations on potential fixes. Have also tried:
Cleaner tool - http://www.adobe.com/support/contact/cs5clean.html
AdobeNotificationsDllFieldReplacementTool.exe
Deleting the "amt3.log" file from the temp folder (saw this in a previous post, I guess to look for process errors)
The only "error" message listed in the entire amt3.log file is "Sequence Error! PreValidate called after Validate!" towards the very end of the log sequence. I'm at the end of my rope here. I almost purchased Captivate 5 without downloading the trial version first. I'd still like to purchase it but not if I can't even get the trial version to work.
Someone please help. Thanks.

Hi and welcome to this forum.
It sounds like you've tried most of the usual fixes for this installation issue.
I'm only a regular user like yourself but I know that the Adobe developers watch this forum closely for any issues like the one you're having. They'll usually chime in pretty quickly to offer assistance via some kind of screen sharing session so that they can investigate what's happening.
Stay tuned and be patient. Help is on the way, but even developers need a weekend.

CS5 crashes after splash screen

Every time I load my CS5 Application it crashes right after the splash screen. The log says:
Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Application Specific Information:
*** error for object 0x10f1f6e00: incorrect checksum for freed object - object was probably modified after being freed.
Any suggestions on how to get past this?
Hardware Overview:
Model Name: Mac Pro
Model Identifier: MacPro3,1
Processor Name: Quad-Core Intel Xeon
Processor Speed: 2.8 GHz
Number Of Processors: 2
Total Number Of Cores: 8
L2 Cache (per processor): 12 MB
Memory: 12 GB
Bus Speed: 1.6 GHz
System Version: Mac OS X 10.6.3 (10D573)

Ok, so if this happens to you here is the solution:
The problem relates to the installed fonts you have. There is no way of knowing exactly which one it is without trial and error enabling and disabling. What worked for me was using a font-managing software like Font Book and having it validate all your fonts. From there delete or disable any questionable ones with errors. Not all fonts with errors create this problem, so it is possible to re-introduce fonts and isolate the one(s) that cause the crash.

Encore CS3 crashes after splash screen

I have purchased a new computer and have installed Adobe Master Collection CS3 and am using the Windows 7 system. I created a movie project in Premier Pro CS3 and rendered the movie and received the message at the end of rendering that said "Application failed to retun a video frame". I assumed the program couldn't open the Encore program and so I tried to open it separately. It would start up then crashes when it gets to the loading of the blue ray part of the program. I don't know if I am looking at two separate issues or just one. Please help!

If Jeff's Roxio Fix does not solve the issue, then consider this: failure to return video frame is often a sign that there is a gap in the video.
Do you have ganged Assets on one Timeline?
Have you checked 100% that your Audio is EXACTLY (and I mean 100%) the same Duration, down to the Audio Unit, with the Duration of the Video, or shorter? One extra Audio Unit can get you a gap in a ganged Timeline.
Good luck,
Hunt

NEED HELP!! LOGIC CRASHES AFTER splash screen plss hel

hey i recently updated to osx 10.6.6 and since then my logic pro has been acting up. But it has come to the point to where now it doesnt even open it crashes right after checking midi drivers. here is the report if anyone can pleasee helpp
Process: Logic Pro [483]
Path: /Applications/Logic Pro.app/Contents/MacOS/Logic Pro
Identifier: com.apple.logic.pro
Version: 8.0.2 (1502.22)
Build Info: Logic-15022200~9
Code Type: X86 (Native)
Parent Process: launchd [410]
Date/Time: 2011-01-23 18:53:35.804 -0500
OS Version: Mac OS X 10.6.6 (10J567)
Report Version: 6
Interval Since Last Report: 406669 sec
Crashes Since Last Report: 78
Per-App Interval Since Last Report: 367569 sec
Per-App Crashes Since Last Report: 59
Anonymous UUID: A3586FC6-6081-439D-A15C-C8042C0882EB
Exception Type: EXCBADACCESS (SIGABRT)
Exception Codes: KERNINVALIDADDRESS at 0x0000000049b45b69
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Application Specific Information:
abort() called
Thread 0 Crashed: Dispatch queue: com.apple.main-thread
0 libSystem.B.dylib 0x9128a176 __kill + 10
1 libSystem.B.dylib 0x9128a168 kill$UNIX2003 + 32
2 libSystem.B.dylib 0x9131c89d raise + 26
3 libSystem.B.dylib 0x91332951 __abort + 124
4 libSystem.B.dylib 0x913329cd abortreportnp + 0
5 com.apple.logic.pro 0x002b37ff 0x1000 + 2828287
6 libSystem.B.dylib 0x9128f46b _sigtramp + 43
7 ??? 0x0000000b 0 + 11
8 com.apple.logic.pro 0x00020cff 0x1000 + 130303
9 com.apple.logic.pro 0x00021f94 0x1000 + 135060
10 com.apple.logic.pro 0x00032e0b 0x1000 + 204299
11 com.apple.logic.pro 0x002b741e 0x1000 + 2843678
12 com.apple.logic.pro 0x002b75e3 0x1000 + 2844131
13 com.apple.logic.pro 0x00012e8c 0x1000 + 73356
14 com.apple.logic.pro 0x0019534e 0x1000 + 1655630
15 com.apple.logic.pro 0x004d3c78 0x1000 + 5057656
16 com.apple.logic.pro 0x0051f9db 0x1000 + 5368283
17 com.apple.logic.pro 0x005205f9 0x1000 + 5371385
18 com.apple.AppKit 0x94753040 -[NSDocument readFromURL:ofType:error:] + 743
19 com.apple.logic.pro 0x00520410 0x1000 + 5370896
20 com.apple.AppKit 0x9463eddd -[NSDocument initWithContentsOfURL:ofType:error:] + 311
21 com.apple.AppKit 0x9463e981 -[NSDocumentController makeDocumentWithContentsOfURL:ofType:error:] + 383
22 com.apple.logic.pro 0x0053d6d3 0x1000 + 5490387
23 com.apple.AppKit 0x9463e739 -[NSDocumentController openDocumentWithContentsOfURL:display:error:] + 886
24 com.apple.logic.pro 0x004d8b79 0x1000 + 5077881
25 com.apple.Foundation 0x923d5588 nsnotecallback + 345
26 com.apple.CoreFoundation 0x9851f793 __CFXNotificationPost + 947
27 com.apple.CoreFoundation 0x9851f19a _CFXNotificationPostNotification + 186
28 com.apple.Foundation 0x923ca384 -[NSNotificationCenter postNotificationName:object:userInfo:] + 128
29 com.apple.Foundation 0x923d7789 -[NSNotificationCenter postNotificationName:object:] + 56
30 com.apple.AppKit 0x94423422 -[NSApplication _postDidFinishNotification] + 125
31 com.apple.AppKit 0x94423332 -[NSApplication _sendFinishLaunchingNotification] + 74
32 com.apple.AppKit 0x9457a4ed -[NSApplication(NSAppleEventHandling) _handleAEOpen:] + 274
33 com.apple.AppKit 0x9457a10d -[NSApplication(NSAppleEventHandling) _handleCoreEvent:withReplyEvent:] + 101
34 com.apple.Foundation 0x9240a7a4 -[NSAppleEventManager dispatchRawAppleEvent:withRawReply:handlerRefCon:] + 511
35 com.apple.Foundation 0x9240a568 _NSAppleEventManagerGenericHandler + 228
36 com.apple.AE 0x92dc8f58 aeDispatchAppleEvent(AEDesc const*, AEDesc*, unsigned long, unsigned char*) + 166
37 com.apple.AE 0x92dc8e57 dispatchEventAndSendReply(AEDesc const*, AEDesc*) + 43
38 com.apple.AE 0x92dc8d61 aeProcessAppleEvent + 197
39 com.apple.HIToolbox 0x97a07389 AEProcessAppleEvent + 50
40 com.apple.AppKit 0x943f39ca _DPSNextEvent + 1420
41 com.apple.AppKit 0x943f2fce -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 156
42 com.apple.AppKit 0x943b5247 -[NSApplication run] + 821
43 com.apple.prokit 0x0210df5c NSProApplicationMain + 326
44 com.apple.logic.pro 0x00003942 0x1000 + 10562
45 com.apple.logic.pro 0x00003869 0x1000 + 10345
Thread 1: Dispatch queue: com.apple.libdispatch-manager
0 libSystem.B.dylib 0x9124f982 kevent + 10
1 libSystem.B.dylib 0x9125009c dispatch_mgrinvoke + 215
2 libSystem.B.dylib 0x9124f559 dispatch_queueinvoke + 163
3 libSystem.B.dylib 0x9124f2fe dispatch_workerthread2 + 240
4 libSystem.B.dylib 0x9124ed81 pthreadwqthread + 390
5 libSystem.B.dylib 0x9124ebc6 start_wqthread + 30
Thread 2: com.apple.CFSocket.private
0 libSystem.B.dylib 0x912480c6 select$DARWIN_EXTSN + 10
1 com.apple.CoreFoundation 0x98540c83 __CFSocketManager + 1091
2 libSystem.B.dylib 0x9125685d pthreadstart + 345
3 libSystem.B.dylib 0x912566e2 thread_start + 34
Thread 3:
0 libSystem.B.dylib 0x912290fa machmsgtrap + 10
1 libSystem.B.dylib 0x91229867 mach_msg + 68
2 com.apple.audio.midi.CoreMIDI 0x025090c1 XServerMachPort::ReceiveMessage(int&, void*, int&) + 155
3 com.apple.audio.midi.CoreMIDI 0x0252797a MIDIProcess::RunMIDIInThread() + 150
4 com.apple.audio.midi.CoreMIDI 0x0250a2d9 XThread::RunHelper(void*) + 17
5 com.apple.audio.midi.CoreMIDI 0x02509ca6 CAPThread::Entry(CAPThread*) + 96
6 libSystem.B.dylib 0x9125685d pthreadstart + 345
7 libSystem.B.dylib 0x912566e2 thread_start + 34
Thread 4:
0 libSystem.B.dylib 0x9124ea12 _workqkernreturn + 10
1 libSystem.B.dylib 0x9124efa8 pthreadwqthread + 941
2 libSystem.B.dylib 0x9124ebc6 start_wqthread + 30
Thread 5:
0 libSystem.B.dylib 0x9124ea12 _workqkernreturn + 10
1 libSystem.B.dylib 0x9124efa8 pthreadwqthread + 941
2 libSystem.B.dylib 0x9124ebc6 start_wqthread + 30
Thread 6:
0 libSystem.B.dylib 0x9124ea12 _workqkernreturn + 10
1 libSystem.B.dylib 0x9124efa8 pthreadwqthread + 941
2 libSystem.B.dylib 0x9124ebc6 start_wqthread + 30
Thread 7:
0 libSystem.B.dylib 0x912570a6 _semwaitsignal + 10
1 libSystem.B.dylib 0x91282ee5 nanosleep$UNIX2003 + 188
2 libSystem.B.dylib 0x91282e23 usleep$UNIX2003 + 61
3 com.apple.AppKit 0x9455cfe1 -[NSUIHeartBeat _heartBeatThread:] + 2039
4 com.apple.Foundation 0x923d5bf0 -[NSThread main] + 45
5 com.apple.Foundation 0x923d5ba0 _NSThread__main_ + 1499
6 libSystem.B.dylib 0x9125685d pthreadstart + 345
7 libSystem.B.dylib 0x912566e2 thread_start + 34
Thread 0 crashed with X86 Thread State (32-bit):
eax: 0x00000000 ebx: 0x913328e1 ecx: 0xbfffde9c edx: 0x9128a176
edi: 0x1ed7c800 esi: 0x251df830 ebp: 0xbfffdeb8 esp: 0xbfffde9c
ss: 0x0000001f efl: 0x00000286 eip: 0x9128a176 cs: 0x00000007
ds: 0x0000001f es: 0x0000001f fs: 0x00000000 gs: 0x00000037
cr2: 0x010b7818

Hi, ish1919.
Have you updated the drivers for your hardware? An OS update sometimes needs later drivers. Older ones can cause conflicts. Check the manufacturer website [eg. RME] for your hardware and get the latest version.
Hope this helps.
Scorpii.

Premiere Pro CS5 and After Effects CS5 crash after splash screen

Im am fed up with this ive done everything i can and no one seems to know whats wrong, i installed CS5 on my macbook and imac i7, and they both worked for a while but then suddenly my imac i7 cs5 stopped working and kept crashing, my macbook continues to work just fine, ive even done a system reinstally and reinstalled os x and yes it would work for a little and then stop, they both have the same programs, whats weird is when i create a new user with admin privileges on my imac it would work fine but i deleted some files in the main account trying to fix the problem and no it wont work in the second account so here i am doing a system reinstally one last time. i called adobe they were no help at all literally, i called apple they did as much as they could i mean apple really made me feel like they tried, so here i am can anyone help?

Ok so i figured it out, the problem is my downloaded fonts from the internet. What sucks is that adobe cs4 applications ran perfectly fine with them, but now cs5 doesnt . I uninstalled my downloaded fonts and guess what?! it worked! I wonder why cs4 starts up with no problems with the same fonts and cs5 cant, thats just stupid...

[SOLVED] Amarok 2.0.1 crashes after splash screen

i have no clue what is going on here, but amarok 2.0.1 crashes every time i try to run it. so if someone could at least give me a little insite......
[nick@grim ~]$ amarok
amarok(15659)/kdecore (KSycoca) KSycocaPrivate::openDatabase: Trying to open ksycoca from "/var/tmp/kdecache-nick/ksycoca4"
amarok(15659)/kdecore (KLibLoader) kde4Factory: The library "" does not offer a qt_plugin_instance function.
amarok(15659)/kdecore (KLibLoader) kde3Factory: The library "" does not offer an "init_phonon_xine" function.
amarok(15659) Phonon::KdePlatformPlugin::createBackend: using backend: "Xine"
amarok(15659)/kdecore (KLibLoader) findLibraryInternal: plugins should not have a 'lib' prefix: "libamarok_collection-mtpcollection.so"
amarok(15659)/kdecore (KLibLoader) findLibraryInternal: plugins should not have a 'lib' prefix: "libamarok_collection-sqlcollection.so"
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
090128 10:11:06 InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
amarok(15659)/kdecore (KLibLoader) findLibraryInternal: plugins should not have a 'lib' prefix: "libamarok_collection-ipodcollection.so"
amarok(15659)/kdecore (KLibLoader) findLibraryInternal: plugins should not have a 'lib' prefix: "libamarok_collection-daapcollection.so"
QDBusObjectPath: invalid path ""
Object::connect: No such slot MainWindow::showStatistics()
Object::connect: (receiver name: 'MainWindow')
amarok(15659)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig:
amarok(15659)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig:
amarok(15659)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig:
amarok(15659)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig:
amarok(15659)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig:
QLayout: Attempting to add QLayout "" to MainWindow "MainWindow", which already has a layout
link XMLID_7_ hasn't been detected!
link XMLID_7_ hasn't been detected!
Couldn't resolve property: radialGradient3986
link XMLID_7_ hasn't been detected!
link XMLID_7_ hasn't been detected!
Couldn't resolve property: radialGradient3986
QWidget::insertAction: Attempt to insert null action
QWidget::insertAction: Attempt to insert null action
QWidget::insertAction: Attempt to insert null action
QWidget::insertAction: Attempt to insert null action
QWidget::insertAction: Attempt to insert null action
QWidget::insertAction: Attempt to insert null action
QWidget::insertAction: Attempt to insert null action
<unknown program name>(15657)/: Communication problem with "amarok" , it probably crashed.
Error message was: "org.freedesktop.DBus.Error.NoReply" : " "Message did not receive a reply (timeout by message bus)" "
[nick@grim ~]$ KCrash: crashing... crashRecursionCounter = 2
KCrash: Application Name = amarok path = <unknown> pid = 15659
sock_file=/home/nick/.kde4/socket-grim/kdeinit4__0
also, i have no clue if this is related, but every time i start konsole from ALT+F2, it says "KDEInit could not launch '/usr/bin/konsole'.", but launches it anyways.
Last edited by grimrider (2009-01-28 21:44:54)

anrxc wrote:Don't worry about it too much because amarok crashes all over the place so you are not missing much
I built my own test a few minutes ago to avoid libgpod and mtp, one of the first problems is segfaulting at every exit so it looses many settings like the current playlist. Playlist importing from v1 is still broken, rtsp streams are not recognised (even though it is still the xine engine), there is no EQ, random crashes here and there... If you still want to try it check this build http://aur.archlinux.org/packages.php?ID=19633
haha wow. i guess ill stick w/ 1.4 untill they get this sorted out. was hoping for sumthin new but owell
thanks for the help

CS5 - crash after splash page

I'm working with CS5 Master for Windows. Currently using XP Service Pack 3 and I meet the minimum requirements.
I'll open a program and within 5-10 seconds I receive an "____ has experienced a problem and must close" error message. Some programs are in full working order; the only ones I'm having issues with are Illustrator, Photoshop and InDesign. I've gone through the support files and have tried working around the listed issues (videocard driver, font issues, etc) but nothing has worked.
I've uninstalled and reinstalled CS5 completely, but I'm still having the same problem.
Any ideas? Anyone else having this problem?

Me!
I've posted http://forums.adobe.com/thread/649891 & http://forums.adobe.com/thread/648051

Lightroom 1.4.1 crashes after splash screen

Lightroom gets far enough to show the total number of pictures in the catalog (145024) and then quits. This is the message in the Application Event Log.
"Faulting application lightroom.exe, version 1.4.1.0, faulting module msvcr80.dll, version 8.0.50727.1433, fault address 0x00014584."
I reinstalled 1.4.1. I rebooted. I renamed msvcr80.dll in the lighroom folders and rebooted. I stopped all other programs.
Can I do anything like delete preferences or start with a different catalog? I backed up the catalog yesterday but I'm not sure how to revert to it if I can't open Lightroom.
Bill

Use this document to locate your preference file: http://www.adobe.com/cfusion/knowledgebase/index.cfm?id=333660
Start Lr with a different catalog by holding the Ctrl key while starting Lr.

How can one change the order of the issues (folios) in a custom viewer?

Hi,
I am trying to find how one can determine the order that the issues (folios) will appear in a custom viewer (multi-folio with subscriptions).
I tried to rearrange the order by changing the publication date in the Folio Producer Oorganizer, but it has no effect in the iPad custom viewer.
Thanks

The publication date settings determine the order of the folios in the library, so that should work. Did you update the folios?

Premiere crashes after nested than multi cam

Premiere crashes after nested than multi cam

I am getting the same error, I worked on an hour long Doc with Premiere CC 7.0 doing the same process without issue, now I continually get a "trackItem.ccp-156" serious error crashes. Taking all the media offline in the project and creating a multicam clip from a nest on the timeline still occurs, so i'm guessing it's a project file corruption, and not a media corruption issue. I've tried deleting preferences, deleting media cache and preview files, and the same crash keeps coming up. Creating a new project and bringing in the old sequence still crashes on the same nested clip.

Problems updating folios in multi issue viewer

I created a multi issue viewer app containing two issues. Now I try to update one of these two issues in the DPS Folio Producer Organizer, but the app still shows the old version of the issue.
I update the issue with the "update"-button and deleted the multi issue viewer and re-installed it on my iPad many times, but the multi issue viewer still shows the old version of the changed issue.
Finally I deleted the changed issue in the DPS Folio Producer Organizer, but the multi issue viewer still shows the old version of the issue.
What can I do now?

I suggest calling enterprise support for this, they should be able to help you figure out what is going on. You can find contact information by logging into http://digitalpublishing.acrobat.com/ and looking in the bottom middle of the page.
Neil

Sideloaded Custom Viewer (Multi-Issue) crashes after splash on KINDLE FIRE

Similar Messages

Maybe you are looking for