New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Tray mode doesn't find device, crashes when searching, device perms issue? - KDE, Ubuntu 16.04.1 #29
Comments
Can you install gir1.2-notify package and tell me if it works? |
Installing the package stops the python error and now the gui silently dies when running a search although I do now get the notification when devices are found. Also, it still won't default to the first discovered device at startup. Watching the terminal messages I can see the device index returns okay right after the gui dies. The process continues to run after the gui dies and no errors are returned. Running it under sudo does work as mentioned before although I still need to run a search and select a device from the gui. |
Attached a strace file if it helps. |
I do not see the attached file. The strace will help me to understand better. Thanks for your feedback. |
Sorry about that. |
@chuqster thank you. Could you also send the errors shown in the terminal, please?. |
Hi, Not getting any errors since adding gir-notify, the tray gui just quietly dies after searching for devices unless I run the command under sudo. See attached for the output I do get. This is just past running a search and after the gui died. Hope that helps! BTW, if there's a way to increase verbosity of output or run it from python interpreter under a debug let me know how and I can do that if it helps. Also, is there anything like a file or device that I have to have any special permissions to? I just ask as it seems fine run under sudo. I'm using Pulse audio. Thanks, |
Just out of curiosity, could you delete the directory |
Hi, Yeah, same results other than it reloaded defaults because the conf file Neat project, by the way. Thanks for doing this! I just started collecting Just a suggestion for a future enhancement if I may. The ability to create Keep up the good work! -Chuck On Sun, Nov 20, 2016 at 5:49 PM, Muammar El Khatib <notifications@github.com
charles@muadib: List of Google Cast devices available in your network:Index Friendly name |
@chuqster I am sorry to get back so late, if you are still using the app, did it ever work for you?. |
Sorry, I missed your response. To be honest I haven't used it much lately.
I've been streaming more from my phone than that computer.
…On Sun, Jan 29, 2017 at 9:56 AM, Muammar El Khatib ***@***.*** > wrote:
@chuqster <https://github.com/chuqster> I am sorry to get back so late,
if you are still using the app, did it ever work for you?.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#29 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AVZTHLjMrtxJk79iQ867ToSpad6b7Xt3ks5rXNLGgaJpZM4K3ZYf>
.
|
Hi Muammar, I'm trying to use this and came across this issue. If you're inclined to reopen, I'm happy to help test, or produce whatever debug outputs you might want. |
@brockrob I am reopening the issue. I would be glad if you could help me to debug this. Thanks. |
Sure thing. I'm on Kali-rolling, kernel 4.11.3, pulse-audio, and KDE plasma. Running mkchromecast from their repo, which mirrors debian-testing:
I didn't dig too hard. It works fine in the command line, but if I run the tray it disappears from the tray after I click the bit to find a chromecast device. There is still an mkchromecast process alive after this happens, however, and the debug output smells like a threading issue at first glance:
Any other info you'd like? |
Any other info you'd like?
That would be enough. I can work with that. I will install Kali and
check it out. Just out of curiosity -- when the icon disappears, you
can still click on the systray menus?. I will get back to you soon.
Thanks.
|
No, it disappears entirely from the systray. Note that if you want to reproduce in kali I have installed KDE and removed gnome. Given that OP was also using KDE, I'm thinking it's worthwhile you do the same? |
Once I set up the vbox I will install only KDE. |
@brockrob you were right about the icon disappearing completely from the systray. I will try to fix this. |
Hi @muammar,
Of course if you'd need any other info let me know. Bests, |
I have the same problem with KDE. I'm using KDE Neon 18.04.
|
Same is happening here as well./Systray Icon disappears when I press the search for devices option, totally gone and not just the icon. |
I just resolved this issue on a fresh install of Kubuntu 18.10 with the following: sudo apt install python3-pip Hopefully that helps anyone else experiencing this. |
I have kind of isolated the issue. The difference in KDE comes between pyqt5 version 5.11.2 and pyqt5 version 5.12.2. When we use pyqt5 v 5.12.2 (latest), the problem comes into play and the icon disappears from the system tray when 'search for media streaming devices' is clicked. This problem does not occur when we use pyqt5 v 5.11.2 i.e. when we install from source and use requirements.txt to install the needed packages. Thus, problem will occur as in my case, when installing from AUR or pretty much any time when not installing from sources. EDIT: Icon problem solves when I run Thus finally, if you're experiencing the problem of disappearing system tray icon, use pip to install the pyqt5 package instead. I hope this helps out a bit. |
I'm running KDE on Manjaro and can confirm installing pyqt5 through pip fixed the system tray crash issue. |
Hello,
So running from a terminal runs perfectly fine and chromecast devices show up in pavucontrol and everything works. In tray mode the chromecast device is never found and running a search will crash. OS is Kubuntu 16.04.1 and I verified all dependencies were met by your specs. Running in debug mode I got the following at search [see below]. Now if I run the same thing under sudo it works. Well, kind of. The Chromecast audio device isn't available in pavucontrol for obvious reasons (ran as root) but a search will find the device, it shows up in the GUI, can be selected and connected to.
charles@muadib:~$ mkchromecast --debug -t
('ALSA device name:', None)
('Google Cast name:', None)
('backends: ', ['ffmpeg', 'avconv', 'parec'])
('ALSA device name:', None)
('Google Cast name:', None)
('backends: ', ['ffmpeg', 'avconv', 'parec'])
USER =charles
PATH =/home/charles/bin:/home/charles/.local/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin
mkchromecast v0.3.6
(':::audio::: chunk_size: ', 1024)
:::audio::: tray =True
Configuration file exist
Using defaults set there
('ffmpeg', 'aac', '192', '44100')
:::audio::: Program /usr/bin/ffmpeg found in /usr/bin/ffmpeg
:::audio::: backend dictionary {'/usr/bin/ffmpeg': 'ffmpeg', 'ffmpeg': 'ffmpeg'}
Selected backend: /usr/bin/ffmpeg
Selected audio codec: aac
Default bitrate used: 192k
Default sample rate used: 44100Hz
:::audio::: command ['/usr/bin/ffmpeg', '-ac', '2', '-ar', '44100', '-f', 'pulse', '-i', 'mkchromecast.monitor', '-acodec', 'aac', '-f', 'adts', '-ac', '2', '-ar', '44100', '-b:a', '192k', '-cutoff', '18000', 'pipe:']
:::cast::: sockets method 192.168.105.153
Configuration file exist
Using defaults set there
(':::systray::: Screen resolution: ', 1920, 1080)
:::systray::: High-DPI screen detected...
Configuration file exist
Using defaults set there
Traceback (most recent call last):
File "/usr/share/mkchromecast/mkchromecast/systray.py", line 259, in search_cast
self.search_notification()
File "/usr/share/mkchromecast/mkchromecast/systray.py", line 878, in search_notification
gi.require_version('Notify', '0.7')
File "/usr/lib/python2.7/dist-packages/gi/init.py", line 102, in require_version
raise ValueError('Namespace %s not available' % namespace)
ValueError: Namespace Notify not available
Aborted (core dumped)
The text was updated successfully, but these errors were encountered: