Disable changing workspace loop - configuration

Lets say I have two workspaces and the fist one is active.
If I change workspace ctrl+alt+→ twice, I change to workspace 2 then 1 again.
What I want is to disable that feature. When I am on workspace two, I want it to be blocked to it when moving to the right.
I know it is possible to do it on ubuntu but I did not manage to find the option on xubuntu.

If still needed: open xfce4-settings, go to 'Window Manager Tweaks', switch to 'Workspaces' tab and disable 'Wrap workspaces depending on actual desktop layout' and 'Wrap workspaces when the first or the last workspace is reached' options.

with this method you can work with only one workspace but it will do. Add xfce workspace applet to the panel right click it and add only 1 workspace there or go into xfce4 setting , workspace and add only 1 workspace and you are done

Related

Google Chrome On Startup Option Disabled

following an update of my LENOVO T14s laptop, Chrome starts on the setting page and I can't change it back to other options. I tried looking and it says I need to delete a registry key or something, but all the paths provided to get to that are not correct for me.
Anyone can help?
For me this happened due to this (the on startup options is on main page of settings menu you just need to scroll down)
, check if same is the issue for you, click on the 3 dots next to the link and change the link.
If not you will be better of uninstalling and reinstalling chrome from scratch rather then messing with registry (if you have synced your google account with chrome no settings, bookmarks or password will be lost after reinstalling, you will only need to log in)

Policy to prevent adding users of Chrome

In the Chrome UI, there's an avatar displayed next to the settings dots which when pressed allows the user to perform actions related to users of Chrome. They can add a user. If they go into 'other people' settings they can remove a previously added user. And the user can chose to sign in if they want to sync things like bookmarks across devices.
There's also a guest option, which allows a guest user to have their own temporary profile; this allows someone to use Chrome without messing up the other persons history, bookmarks or cookies. This guest account can be turned off by using the BrowserGuestModeEnabled Chrome policy.
How can I prevent the user from adding additional accounts (or removing any that are in place)? I thought maybe BrowserSignin would work, but it doesn't seem to be what I want.
I found it. BrowserAddPersonEnabled
Paste this:
REG ADD HKLM\SOFTWARE\Policies\Google\Chrome /v BrowserAddPersonEnabled /t REG_DWORD /d 0
in the command prompt (run it as an administrator).

Chrome only works on the first session for multi-session logins

I haven't found anything looking like a good answer to my problem, so I'll articulate my own question:
On a Terminal-/Remote Desktop Server (2012 R2), we have a problem running Chrome where there are multiple sessions for the same user. (e.g. a shared "Front Desk" AD user where 2 or 3 people at work may be logged into 4 or 5 RDP sessions with the same user account)
The first launch of Chrome works fine for whichever session opens it. None of the other sessions can use Chrome, however, at least not until the initially launched program instance is closed.
I found an explanation followed by a very unsexy suggestion in the Chromium forums (https://code.google.com/p/chromium/issues/detail?id=160676), so I'm trying to ask here instead in hope that there is a better and more intuitive solution to the problem.
Thank you!
I've solved by, for each concurrent session needed:
In chrome click on Manage people, then Add person, checking Create a desktop shortcut for this user.
Chrome will create a desktop shortcut with the Target property such as:
"C:\......\chrome.exe" --profile-directory="Profile 1"
Edit the Target property of the created desktop shortcut and add a unique folder value for the --user-data parameter:
"C:\......\chrome.exe" --profile-directory="Profile 1" --user-data-dir="C:\temp\user1"
I don't see your log or any other trace clue.
One of my guess chrome's user data directory was locked by the chrome opened.
You might try open the chrome from cmd with this command:
chrome.exe --user-data-dir="C:\temp\user1"
It is starting chrome with a new user data directory.
Workaround details for this issue are here:
https://code.google.com/p/chromium/issues/detail?id=160676
You may want to uncheck the option that lets Chrome run in the background even if "closed"
Click on the Chrome menu (or press Alt+E) Select Settings Click on the link titled ‘Show advanced settings‘ Under the section headed ‘System‘ untick the box next to “Continue running background apps when Google Chrome is closed”

right-click-then-open-with works but simple left-click does not

At some point in the last couple of days a bug seems to have materialised in my app's Google Drive integration, despite me not having changed anything, and usage remaining fairly constant.
When you left click one of the app's documents in Drive a new about:blank tab opens showing the app's icon and the text "Sorry, an error occurred while opening this file. Please try again. [XXXXX]" where [XXXXX] is a short string that seems to be different every time. The create new works fine, and if you use the right-click menu and open with it also works fine.
All of this makes me think that there is a bug in the latest javascript update to Google Drive's main interface.
In terms of debugging, in the apiconsole the app has...
The initiate oauth2 option unchecked
The allow multiple files option unchecked
Mobile browser support checked
24 mime-types, 61 primary extensions, and 1 secondary extension registered
If it is a bug as Claudio has mentioned, I believe Google Drive SDK documentation needs to be updated too, since 'open' action is described only for "Open With" option:
https://developers.google.com/drive/integrate-open
I'm wondering how to trigger the proper action when registred mime-type can be managed by more than one installed application? Is there a way to set the default open action - or the application which created it will be used as the default? What's happen if you reach the application web by typing the url (not from UI Drive UI create action) and save the content on Drive, since you may be already authorized to do it?

chrome extension: open an website with different account in each tab

I have several accounts for a website and currently I want to write an extension that I can open all the accounts simultaneously in chrome, each tab for one account.
So that means I want each tab with a separate cookie system, is it doable? If so please suggest the API I should use, thanks!
Go to Chrome Preferences. There is a Users section where you can add users. Each new user will have its own cookie jar, so you can log in to a site as many different users at once. It makes new chrome windows, but it seems you cannot drag a tab onto a window of another user.
According to Chrome documentation, you can modify HTTP headers (including cookies) in the onBeforeSendHeaders event handler. So, you need to store new cookies for every account by means of the onHeadersReceived event handler, and then substitute them for every tab in outgoing requests.
There even exists an extension which seems doing almost the thing you want - Chrome Cookie Switcher.
Also I have found an answer that may be helpful for your task: Associate a custom user agent to a specific Google Chrome page/tab.
I really don't think Chrome allows extensions to do this. If I recall correctly, extensions can inspect and block requests, but they can't modify them, such as changing cookies on the fly for each tab.
I suggest you use the --user-data-dir command-line option of Chrome. It allows you to keep several separate profiles, each in its own directory, and then you only need to start chrome with the proper option:
# run this command to use the first profile
google-chrome --user-data-dir=/home/binchen/my_chrome_profiles/my_profile_1
# run this command to use the second profile
google-chrome --user-data-dir=/home/binchen/my_chrome_profiles/my_profile_2
...
Each profile will be in its own Chrome window, with its own cookie store, instead of its own tab, but it's easier than writing an extension.
Lastly, if the website you're mentioning is Google, you can keep several Google accounts open at the same time.