Cant find the background apps tray in Pop!_OS - linux

All apps like "Steam", "Slack", "Anydesk" and etc. They were all displaying in black/white in a tray at my panel.
The update for POP!_OS was pending for a few weeks, so "what the heck, let's do this!"...
It was an instant regret when the PC rebooted... all GNOME extensions were GONE! I was not expecting this to happen... =/
I managed to remember most of the extensions I had running before, so I installed them all.
Didn't take me too much time to realize that the background apps are not showing anymore. They don't show in the dash, nor the panel or anywhere else besides the System Monitor.
The gnome extension Dash to Panel is active, as it may be related I'm posting this screen shot showing that all possible areas are "Visible".
How can I display the background apps again?

Well, silly me...
I really don't know the reason for it, but seems like the package https://github.com/ubuntu/gnome-shell-extension-appindicator was uninstalled during the update.
So the solution for the issue was:
Installing this extension: $sudo apt install gnome-shell-extension-appindicator
Enabling it in the gnome extensions manager: Ubuntu Appindicators
I hope it helps someone! =)

Related

jitsi cannot share certain applications (screensharing)

the problem I'll be describing might be caused by different reasons:
on linux opensuse leap 15.1 gnome (wayland) I can share e.g. mupdf but not evince or libreoffice in chromium jitsi session with screen share application window
another participant on windows tried to share a pdf document using microsoft office 365 and it seemed to show on his browser, but not on the other conference participants' browsers (one chromium on linux as in 1., the other firefox on windows), so he could not share his screen
I could not find any information on this topic using search machines. So I would appreciate if there is any answer on this out there in the community.
Looking forward to solving this ...
Cheers
JFM
PS: on the setup described in 1. also obs studio fails to screencast, maybe there is something related to this system setup causing this problem, some video driver setting e.g.?
This is probably related to Wayland, which has more restrictions than classic Gnome. Since you are having the same issue with OBS this sounds like this a classic Wayland permission issue.
I know they are working on implementing screen sharing support via pipewire but no idea how far this is.
You might try to switch back to Gnome on the X-Server until this is properly implemented.

pygame running very slowly 12fps - Upgraded laptop

I'm relatively new to using python have used pygame as a place to better understand how everything comes together.
I recently upgraded my laptop form a 2012 Macbook to the 2019.
Just wondering why the games I made on my 2012 are running soo much slower on my 2019 macbook. Managing packages with conda.
I don't know much but I suspect it may have to do with either
The comp resolution upgrade (which I'm doubtful)
method of installation of pygame
Initially, I Downloaded python3 with homebrew and then installed pygame (pygame would show a blank screen)
I then installed conda and managed packages through it.
I doubt it has to do with the way I have written it, I'm sure it's quite inefficient but I was achieving fps's of 60 for the same code.
If someone could guide me to where to find out more information It would be greatly appreciated.
Cheers.
This seems to be a problem with how MacOS run Pygame. While your game is running, right-click it's icon in the Dock and select Show in Finder. Then in the Folder that shows up, you will see the Python Interpreter executable. Right-click it and click Get Info, and under General check the Open in Low Resolution.
Now your game should run fine. And no, Pygame's resolution will not be "Low".
I resolved this issue by launching pygame in fullscreen. More of a workaround but a solution nonetheless.
Also if you do choose to do this be sure to create a key to exit the screen otherwise you'll need to restart your computer.

Ubuntu 10.04 Update Manager freezes

So I have a lot of VM's with ubuntu 10.04 which recently went off of support.
I don't really care that it went off of support but the window that Ubuntu is showing to tell me this fact is freezing up, and it keeps launching more and more copies of Update manager to tell me this fact.
Including a screenshot of the message. When I click close it just freezes and I have to manually kill the process, but then it comes back later. Any suggestion on how I remove the warning?
So I should have googled better.
The solution to this is from https://askubuntu.com/questions/122165/10-10-irritating-updater-message
Just open software sources and set Release Upgrade to Never under the Updates tab.This stops the message from recurring. Thats it.

Open website from within eclipse's internal browser?

Could anyone help me with opening web pages from within Eclipse's internal (embedded) browser? I'm running Linux (tiling window manager) and Eclipse-3.7.2 side-by-side with browser and it's a pain.
I want this to be able to comfortably read requirements from my code and at the same time code. This could be a question for superuser but it's Eclipse related so I guess I have better shot for an answer here.
Thanks in advance.
edit: I'm running gentoo linux and swt-3.7.1 with compiled in xulrunner support.
edit2: adding picture of gui menu in response to answer bellow.
Open Window / Customize Perspective... menu then on "Command Group Availability" tab find "Web Browser" entry and make sure it is checked. Then confirm that "Web Browser" is also checked on "Tool Bar Visibility" tab. Then you should see a web browser globe icon on toolbar that would open a web browser editor in the IDE.
Though you'll have to change settings on your picture to use "Internal Web Browser" then it will be opened as an Eclipse editor.
I know the question is old but I just had the same problem and was able to find the soloution.
The internal browser of SWT is using the webkitgtk browser engine. Because you're running gentoo I suppose you currently have net-libs/webkit-gtk:3 installed which is incompatible with SWT. But this is no problem because you can install the compatible net-libs/webkit-gtk:2 in a new slot.
Just install it like this:
emerge net-libs/webkit-gtk:2
After the package is installed the internal webbrowser is working again (for me)
Regards
Martin
On Ubuntu 13.04 using Eclipse it automagically worked, I was not sure which webkit I was missing, so I installed all that seemed relevant, if someone has pinpointed which it is, please comment,
Regards,
Gabriel Medina
aptitude install libqt4-webkit libqt5webkit5 libqtscript4-webkit libqtwebkit4 libswt-webkit-gtk-3-jni libwebkitgtk-1.0-0 libwebkitgtk-3.0-0

Android emulator constantly rebooting on Ubuntu Maverick

and thank you for your time.
I am using Titanium Appcelerator to write an app for Android, and as compared to Windows, where the emulator was quite stable, in Linux I get the following symptoms:
emulator restart with no reason, sometimes after a runtime error, sometimes right after launching my app, and sometimes just right after booting completely after being launched
emulator informs that "process $1 is not responding", where $1 is generally the system process, but sometimes may be acore, or the calendar. This may happen while installing my app on the emulator, right after loading it, or right after unlocking the screen.
As it is easy to imagine, testing code like this can be quite difficult, so I was wondering, has anyone else stumbled upon this problem, and/or know how it could be solved?
Thank you very much in advance, and pls let me know of any info I should provide.
Leo
You should verify that the emulator is working fine without Appcelerator first. Definitely update to the latest SDK (r8) and create a new emulator AVD and see if the problem is there without Appcelerator.
I think I found a solution, but I don't claim it is universally valid: I just erased the virtual device created under Titanium, changed the project file for it to use SDK 1.4.2, and had it launched again under 1.4.2. It certainly didn't build my app, but at least it created a new virtual device, which I use now to build against 1.5.0, working like a charm so far.
Thanks again Manfred for pointing me in the right direction!

Resources