Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
(totem:3586): Cogl-WARNING **: 18:26:13.085: Shader compilation failed:
0:90(21): warning: `cogl_layer0' used uninitialized
0:103(21): warning: `cogl_layer1' used uninitialized
0:116(21): warning: `cogl_layer2' used uninitialized
0:127(16): error: no function with name 'clutter_gst_sample_video3'
(totem:3586): Cogl-WARNING **: 18:26:13.085: Failed to link GLSL program:
error: linking with uncompiled/unspecialized shader
Can you confirm that this happens for specific videos that previously played correctly?
Also, when did this issue begin? If you can remember fairly accurately then we can have a look at your package log to see if the upgrading or installation of any packages may have caused the problem.
Strange. If you can remember the date it happened, have a look in /var/log/apt/history.log to see if any packages were installed/upgraded just before the issue arose.
Also, close Totem and then have a look at the dot files in your home directory (including .config and .local), and see if there are any called .totem or similar. If there are then rename them, and start Totem again. It could be something in your user config/profile that's causing the issue.
Yup. I came across another one too. The question is though, why did it suddenly start happening when it worked fine before? The only thing I can think of is a software installation/upgrade.
If you want to get rid of a package entirely:
Code:
sudo apt-get --autoremove purge packagename
and then remove the relevant config files/directories in your home directory (although you still haven't told me yet which ones you found).
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.