I'm hoping this isnt too much of a problem, but I want to make sure.
I'm creating an autorun CD that when put in, will launch a Flash Video with links for customers to navigate through.
I've created my autorun.inf file in the root directory of the CD with the following info in it:
[autorun]
open=catmenu.exe
However, when I try and run the file on an other computer I still get the options screen 'run program or open to view files'. If I click 'run program' then it launches like normal. I think this is just the computer overiding the autorun feature, but I've never made a CD before so I cant be sure. Is there a way to bypass this 'run or view' option or is that just the way it is?
The autorun is determined by the operating system. For Windows 7 as an example - you can go to the Control Panel | AutoPlay and change the settings for each type of media (software, music, video). It is generally safest to work with the "Ask me" option or "Take no action"
Related
I'm developing my own task switcher in QML. When I change the code (main.qml) and press Alt+Tab, the KDE task switcher stays the same even if its preview from the System Settings shows the changes. The task switcher gets updated only after the next login.
I use Kubuntu 22.10, KDE 5.26.5 and my Task switcher is in ~/.local/share/kwin/tabbox/ folder.
Is there a way to apply QML code changes or to notify KDE about the source code being modified? Or is there another way to develop a task switcher (not invoking it by Alt+Tab)?
I tried removing qmlcache rm -rf ~/.cache/*qmlcache*, but it didn't help.
Restarting KWin should work: kwin_x11 --replace (if you're on X11; afaik it's not possible to restart the window manager on Wayland).
You can also try qdbus org.kde.KWin /KWin org.kde.KWin.reconfigure.
So Google Colab has a file-explorer UI pane to the left side.
How do you change the file-explorer on the left in Google Colab to just "go down" into a folder?!?!?!?!?!?!
Or, how do you change the working directory in the file-explorer UI in Google Colab?!?!?!?!?
There doesn't seem to be any relevant buttons or menu options.
Nothing happens when I try to run the console command !cd /content.
I've seen this and this answer. When I run %cd /content, the working directory in the console gets changed, but it seems that that has nothing to do with the file explorer.
Here's an example. Say that I accidentally click this button...
Now, my working directory is severely bogged, and it's not at all obvious that my previous directory was in /content/.
How do I change it back?
Refreshing the page works for me.
I have designed a GUI that I want to run as soon as I turn on my Raspberry Pi. It is currently set up to automatically log in as user on startup, but if that makes the process more difficult I can change that. My Raspi runs on Raspbian 10 (buster), which has made things difficult since I can only find tutorials for Raspbian 8 or so.
I have tried modifying autostart folder, but it is not in the same location as it was in previous Raspbian versions and doesn't seem to be working the way it used to. Tutorials have said to create a .desktop file in /home/pi/.config/autostart but I don't have a .config folder, or at least it's hidden. For me, autostart is in /etc/xdg/autostart and when I try to create a new file here using nano in the terminal, I get the message [Directory '/etc/xdg/autostart' is not writable] and it doesn't save my file.
I have also tried calling my script in /etc/rc.local but it did nothing. Some have said it doesn't work for GUIs.
Here's what I type into terminal:
$ nano /etc/xdg/autostart/gui.desktop
and a new file pops up, but at the bottom I get the warning [Directory '/etc/xdg/autostart' is not writable]
How can I get my GUI script to run on startup with Raspbian 10 (buster)?
There are a number of issues here, first when you are looking at tutorials recognize that Linux distros are built in layers, for simplicity let's say your "layer stack" looks like this: kernel, systemd, x11, xdg, lxde. The kernel boots, then starts systemd, which then starts x11 (and a lot of other stuff), x11 starts xdg (and some other stuff, I think), lxde is started by either x11 or xdg I'm not sure which.
You want to add something to this process, you can do it at the kernel level (bad idea), at they systemd level (probably not right unless its a daemon), at the x11 level (still probably bad as you still don't have a user session yet), or at the xdg or lxde level.
xdg is probably the right place as it has all you need ( a gui, a user session) while being common (xdg will still work if you switch window managers, probably)
With that out of the way, why isn't your solution of modifying xdg working? It's because '/etc/xdg/autostart' is a system configuration directory. Any changes made to it will apply to all users. You may want this, but the system is trying to protect other users on your system and only allows root to make changes to everyone. If you want to do that use "sudo" (documented elsewhere on stack exchange and the internet). If you want to do it just for you use ~/.config/autostart, (https://wiki.archlinux.org/index.php/XDG_Autostart) you might need to create that directory with "mkdir ~/.config/" and then "emacs ~/.config/autostart"
Would it be better to have the python program run in a terminal window from startup? That way you would see what it is doing in case of errors.
If so, perhaps check this out https://stackoverflow.com/a/61730679/7575617
By the way, in the file manager, hit CTRL+H to toggle viewing hidden files and folders.
I'm an android developer. I acquired recently a Samsung Galaxy S3 (I9300) and I am having some problems with it.
The error management doesn't work. I mean, when an app crashes, it doesn't show "Force close", the phone just freezes.
I had an HTC before; I use it when I'm developing too, and with the same malfunctioning app, my HTC shows me force close, but the S3 freezes and I have to restart it.
As you can imagine, this is very annoying.
I found a temporary solution, but it affects wifi. Using this app
https://play.google.com/store/apps/details?id=com.issess.fastforceclose&feature=search_result#?t=W251bGwsMSwyLDEsImNvbS5pc3Nlc3MuZmFzdGZvcmNlY2xvc2UiXQ..
and enabling "old fast force close" seems to solve the problem, but it has wifi related problems.
Things I have tried
Clean ROM, wiping data and Dalvik cache (it works at the beginning, but suddenly the phone freezes and when I restart, the error management doesn't work any more)
Delete all apps
What am I missing? How can I resolve this?
see http://forum.xda-developers.com/showthread.php?t=1843837 , especially post #8
quoting:
I finally figured out what "Fast Force Close" app is doing to stop the freeze. It does something rather simple: it basically "hides" the /data/log folder, by moving it aside, and replacing it by a symlink. And this then also, causes Wifi to not connect after a reboot (dunno why)
mv /data/log /data/log_backup
ln -s /dev/null /data/log
To "disable" the fix, it just does the reverse.
Anyway, this got me thinking that the solution was somehow related to stuff happening in that folder. And one of the things happening in that folder, on a Force Close, is that it receives the output of the dumpstate command:
dumpstate -k -t -n -z -d -o /data/log/dumpstate_app_error
So, my solution for the "Freeze instead of Force Close dialog" issue is to put some files in the /data/log folder, with such permissions that dumpstate can not do its thing.
I found this to solve the issue, but I don't know if there are side effects.
If you want to implement this, you can do it in many ways (e.g. even through terminal emulator or probably some root file explorer). I'm attaching a flashable zip that will do this for you. (see XDA link)
Apart from some boilerplate code, the essential bit is this (in updater-script in the zip):
ui_print("Apply fix...");
delete("/data/log/dumpstate_app_error");
delete("/data/log/dumpstate_app_error.txt.gz");
delete("/data/log/dumpstate_app_error.txt.gz.tmp");
package_extract_file("placeholder", "/data/log/dumpstate_app_error");
package_extract_file("placeholder", "/data/log/dumpstate_app_error.txt.gz");
package_extract_file("placeholder", "/data/log/dumpstate_app_error.txt.gz.tmp");
set_perm(0, 0, 0400, "/data/log/dumpstate_app_error");
set_perm(0, 0, 0400, "/data/log/dumpstate_app_error.txt.gz");
set_perm(0, 0, 0400, "/data/log/dumpstate_app_error.txt.gz.tmp");
The issue was resolved for me by updating the phone to the latest available android version.
I recently switched to a different computer for my programming. it was another collegue's computer and was not reformated. i installed xCode on it. This is the first time i've tried to update an app of ours on this machine. i archived w/out errors and i validated w/out errors. when i go to submit, i get these two errors:
*Unable to create configuration directory: /Users/username/.itmstransporter
*Your home folder must be writable in order to save run-time configuration data. Please
ensure your home folder exists and is writable.
i am not a mac OS person and can barely get around on a mac. a coworker checked and i do have read/write permisions for /Users directory.
can i fix this or do i need to re-install xCode or the OS?
I belive this is because your username on that machine can not write to your home directory (some how)..
Try opening a finder window and "get info" on your home folder. (from finder, Cmd-N opens a window, right click on the folder in the left that is your user name, that is your home folder, and select get info. Right click might not work, if it does not work, use ctrl-click.)
In the "get info" dialog, at the bottom you will see "Sharing & Permissions" you may have to turn the triangle by clicking on it. In the list, make sure your username has Read & Write prifileges, if not, you need to add them by logging in as an admin and changing them.
This photo is just for reference, but you can see justin (me) has Read & Write, that is what you need on your home directory.