My copy of Inkscape 0.92.2 has been working fine on my Mac OS Mojave system since installation last year. Now, today, for the first time, it pops up a dialog when I open pre-existing files
When I click "OK" the dialog window closes, and so does the image window. (Inkscape does not quit.) I have tried all combinations of choices in the dialog window, with the same result every time.
The Mac Console utility shows a message from Inkscape:
27366555: RECEIVED OUT-OF-SEQUENCE NOTIFICATION: 0 vs 2743, 513 <private>
There are similar messages from the contextstored process, whatever that is.
This does not occur with every old .svg file on my disk. It has been weeks since I used Inkscape at all, and months since I worked with the protesting files.
Does anyone have experience with this? Does Inkscape update itself automatically? Inkscape's date-last-modified on my system is today, but I did not [consciously] update it. And even so, the current downloadable version is 0.92.4 but mine is 0.92.2. I don't want to upgrade unless I have to, as my current Inkscape continues to work for some other mission-critical needs. Thanks.
I discovered that the problem affects images that were originally imported from a .ai file.
As a workaround I downloaded Inkscape 1.0 Beta 2 (for Mac OS) and opened the .ai file with that, then saved as .svg. The.svg saved by 1.0B2 opens without issue in Inkscape 0.92 on Mac OS.
So, the disease remains undiagnosed, but the symptoms can be treated and eradicated. :-)
Related
Last weekend my iMac stopped working (sorry forget the symptom details). I tried Disk Utility but it was unable to fix the issue. After I restarted in recovery mode I was able fix the SSD and HD partitions but ended up with a third item. My fusion drive seemed to be split. I found an Apple Support document: https://support.apple.com/en-us/HT207584 and ran 'diskutil cs create Macintosh\ HD disk0 disk1' from the terminal. This seemed to fix the drive.
I was able restore from Time Machine back-up. Got my old mail from BackBlaze. Seemed OK. However, downloaded files (with Safari) gave an error "File damaged and can't be opened. Drag to Trash". I found a fix for file-by-file repair, i.e. xattr -cr Path-to_file. Seemed to work but tedious and didn't really fix the problem. I thought I might make an Automator Folder action to fix the apparent problem with the extended attributes (addressed by the xattr) command. However, when I dragged an (any?) action into the workflow pane I get an error "The action 'Ask the Finder Items' was not loaded because it was detected as malware.
I'm starting to think there is a global permission flag that needs to be flipped.
Any suggestions ideas. Thanks.
Update of sorts. Other files restored from Time Machine are complaining to be damaged not just new downloads.
As reported elsewhere I replaced the file /var/db/gkopaque.bundle with the same file from my laptop via Airdrop. So far so good. Files can be opened. Automator also seems to be working.
Im trying very hard to like virtualbox, but so far I find it so much worse than vmplayer in so many ways. If it wouldnt take me hours to install everything back into vmplayer i would have moved back days ago
When I open my ubuntu vm my host OS's (windows 10) toolbar is still visible at the bottom of the screen, cutting off the actual virtualbox toolbar
Please help me
(edit) It is in fullscreen mode already, it just still shows the toolbar/taskbar from the host OS
Open Task Manager of Windows 10, Select "Windows Explorer" and Restart.
Reference Link
I had this same issue. The Windows 10 taskbar was still showing when I had VirtualBox in fullscreen mode, and what caused it for me was I had a program called Rufus (for creating bootable USBs) open and it was keeping the taskbar from hiding. Once I closed Rufus, everything worked as it should. So, maybe you had a program keeping focus on the taskbar, something that needed attention, and wouldn't let the taskbar hide.
I ran into the problem once. Not sure what had caused the that but I managed to find a solution by enabling "task bar" hiding option in host windows 10 machine.
Right Click on Task Bar -> Task Bar Setting -> Enable Task Bar hiding Option.
You are able to switch to fullscreen mode on the VM, this should hide the Host OS.
This image shows you where you can find the option:
If this is not what you are looking for, please elaborate on your problem, maybe add a screenshot showing the problem you are having.
I just experienced this exact problem, namely Windows 10 host taskbar would not go away despite the guest being in full screen. Even though this question is old, since this question got the top google page rank, I thought I would share how I fixed it.
I fixed it by shutting down Virtualbox and then rebooting the Windows 10 host. It is possible as others have pointed out that some app was keeping the taskbar active, but I couldn't find any such app. If it was some rogue app that was just running as a process (with no taskbar presence), the reboot nuked it from orbit and fixed the problem.
After installation virtualbox tools You can press
host + F (in my case Ctrl + F)
buttons to run fullscreen in virtualbox.
When we double-click on a file (extension .AQ9) from our own application (developped in MFC C++), we receive this message:
Windows cannot find "name of the file.AQ9". Make sure you typed the name correctly, and then try again.
But the file opens anyway without problem (we just close the message and continue to work). We maintain this application for quite a while now (several years, like 15 years) and it's just recently that we have this message only in Windows XP. I don't know what changed exactly on our side since we don't know exactly when it started and the application has more than 2 millions line of code. Also, we create the setup using Install Shield, so maybe it's related to this (but we use this for the latest 10 years without any problem)
The file association seems fine, since it opens the file anyway. If the application is already opened and that we double-click on the file, no message is shown.
My guess is that the slight delay of the splash screen may scare Windows XP in thinking that the file cannot be opened but it's like less than a second... If it's the case, is there a way to specify somewhere a "timeout" before this message is shown? At least for our application.
I've also check in the windows event log but there is nothing I can see about this error.
This question looks like this one but he still gets the message when the application is already launched, which is not my case.
I had a similar problem this year, with the same symptoms, and I was able to get rid of the message by removing the "ddeexec" registry entry associated with the sofware (in your case : HKEY_LOCAL_MACHINE\SOFTWARE\Classes\your software.Document\Shell\Open\ddeexec)
I'm not sure why it worked well before. I suspect a windows update to be the culprit :P
I have an MFC based application. I have dragged the file created from my application to say(bottom right) of the desktop, it could be any location on the desktop.
Now if I open up my file again and perform a save operation, it always gets auto aligned to left. My application's files could retain their position on Windows XP.It works all fine there. This issue is on Windows 7 and Windows 8.
On debugging my codebase, I found that the call made to ::MoveFile() (http://msdn.microsoft.com/en-us/library/windows/desktop/aa365239%28v=vs.85%29.aspx), is actually putting the file to left of desktop.
I couldn't get any thing much on this issue. It seems nobody else has faced this problem :(.
Any pointers in this direction - What could be wrong, or if such things needs a completely separate handling and if there is a standard way to do that would be of great help.
Also, MS Word, Wordpad, Notepad all works fine on my win 7 and win 8 machine in the mentioned scenario.
Is there a way to get the console windows full screen in Windows Vista/7?
I'm looking for a distributable C/C++ solution, library, or emulator.
Microsoft's "solution" is to install a VM which is pretty ludicrous.
The relevant super user's question doesn't have good answers.
For those interested, the full screen console mode isn't available due to WDDM drivers which don't support int10 intercepts.
Take the Console2 source code, modify it to strip toolbars and other visual garbage you don't need and run it in full screen mode.
What it does is starts a command-line shell, redirects the output to its own internal buffers, and then draws the text from those buffers using GDI to a bitmap. Same thing the Virtual PC solution would do, excluding the whole "emulating another OS" layer. :-)
Sadly it is not possible any more, even if you copy and install the Full screen video driver for console from XP.
Like you said, the new driver model won’t allow/support it. (So you can also kiss DOS games running without an emulator/VM goodbye.)
Yahh .. Its bit noisy ..but its possible. Simple trick is to go to exact file ,i.e, cmd.exe in C:/ and
copy the cmd.exe and paste it in desktop. The refer this steps,
cmd.exe >Properties > Compatibility > (Then change the mode to Windows 7) > And Save it.
Again,
Open cmd console > Properties > Layout > Width:300 , Height:300 (change to this).
And enjoy full screen mode(full window) !!