Created attachment 1225804 [details] journalctl Description of problem: Yesterday I updated my Fedora from 24 to 25. Since that time I am not able to log in to gnome as old user. Only way how to log in to gnome is as root or newly created user. I tried both Wayland and X, but none of them let me in. Version-Release number of selected component (if applicable): gnome-session-3.22.1-2.fc25.x86_64 How reproducible: always Steps to Reproduce: 1. Update from F24 to F25 2. Try to log in as old user to Gnome 3. Actual results: After I choose any of old users and insert password, screen is gray (classic log in background) and after few seconds it gets me back to log-in screen. Expected results: Successful log in to Gnome. Additional info:
This seems to be the cause: lis 29 13:13:47 dhcp-2-217.brq.redhat.com gnome-shell[2060]: gdk_pixbuf_new_subpixbuf: assertion 'src_x >= 0 && src_x + width <= src_pixbuf->width' failed lis 29 13:13:47 dhcp-2-217.brq.redhat.com audit[2103]: ANOM_ABEND auid=1000 uid=1000 gid=1000 ses=2 pid=2103 comm="pool" exe="/usr/bin/gnome-shell" sig=6 lis 29 13:13:47 dhcp-2-217.brq.redhat.com org.gnome.Shell.desktop[2060]: ** lis 29 13:13:47 dhcp-2-217.brq.redhat.com org.gnome.Shell.desktop[2060]: St:ERROR:st/st-texture-cache.c:1121:load_sliced_image: assertion failed: (pixbuf != NULL) lis 29 13:13:48 dhcp-2-217.brq.redhat.com abrt-hook-ccpp[2241]: Process 2060 (gnome-shell) of user 1000 killed by SIGABRT - dumping core
The full traceback seems to be in bug 1399486 (provided it's the same crash, but it looks likely).
It seems like there's some issue with gdk-pixbuf loaders and this seems like it might be just another symptom of that. See https://bugzilla.redhat.com/show_bug.cgi?id=1350303#c7
Ales, can you try backing up /usr/lib64/gdk-pixbuf-2.0/2.10.0/loaders.cache and reinstalling gdk-pixbuf2 package, whether that helps? (and whether the new loaders.cache file is different?)
No unfortunately it doesn't help and old loaders.cache file and new one are exactly same.
Created attachment 1225903 [details] loaders.cache
(In reply to Kamil Páral from comment #2) > The full traceback seems to be in bug 1399486 (provided it's the same crash, > but it looks likely). Yes, they are the same.
(In reply to Rui Matos from comment #3) > It seems like there's some issue with gdk-pixbuf loaders and this seems like > it might be just another symptom of that. See > https://bugzilla.redhat.com/show_bug.cgi?id=1350303#c7 Since the loaders.cache in comment 6 looks sane to me (I compared it to mine, especially the SVG loader), I suspect extensions. The 'maps' file in bug 1399486 shows that there are a few. Ales, when you were trying to log in through a newly created user, did you also have the extensions?
(In reply to Debarshi Ray from comment #8) > (In reply to Rui Matos from comment #3) > > It seems like there's some issue with gdk-pixbuf loaders and this seems like > > it might be just another symptom of that. See > > https://bugzilla.redhat.com/show_bug.cgi?id=1350303#c7 > > Since the loaders.cache in comment 6 looks sane to me (I compared it to > mine, especially the SVG loader), I suspect extensions. The 'maps' file in > bug 1399486 shows that there are a few. This stack frame of thread #1 (from bug 1399486) indicates that the SVG was loaded. The variables x, y and width appear to have sane values, and if there was a problem with the loader, I think gdk_pixbuf_loader_write would have failed earlier. #4 0x00007f56c94eb758 in load_sliced_image (result=0x55f4bbcfd0f0, object=<optimized out>, task_data=0x55f4bd019370, cancellable=<optimized out>) at st/st-texture-cache.c:1121 pixbuf = <optimized out> data = 0x55f4bd019370 res = 0x55f4bb6a7ee0 pix = 0x7f56a016b400 width = 512 y = 0 x = 504 loader = 0x55f4bb5b1860 buffer = 0x7f56a005a230 "<?xml version=\"1.0\" encoding=\"UTF-8\" standalone=\"no\"?>\n<!-- Created with Inkscape (http://www.inkscape.org/) -->\n\n<svg\n xmlns:dc=\"http://purl.org/dc/elements/1.1/\"\n xmlns:cc=\"http://creativecommon"... length = 99814 __func__ = "load_sliced_image" So, I think that it could be a faulty Animation object being created from JavaScript with the wrong width and height parameters.
*** Bug 1399486 has been marked as a duplicate of this bug. ***
(In reply to Debarshi Ray from comment #8) > (In reply to Rui Matos from comment #3) > > It seems like there's some issue with gdk-pixbuf loaders and this seems like > > it might be just another symptom of that. See > > https://bugzilla.redhat.com/show_bug.cgi?id=1350303#c7 > > Since the loaders.cache in comment 6 looks sane to me (I compared it to > mine, especially the SVG loader), I suspect extensions. The 'maps' file in > bug 1399486 shows that there are a few. > > Ales, when you were trying to log in through a newly created user, did you > also have the extensions? Old user 'araszka' has some gnome extension and new one is completely clear and doesn't have any.
Kamil helped me to find cause of this issue. We found out that one gnome extension called "text_translator" crashed whole gnome. After we removed directory .local/share/gnome-shell/extensions/text_translator.com, it starts work again. I will attached directory 'text_translator.com' here and you can check what is wrong with this extension.
I wasn't able to attache tar.gz directly, so here is link to my G-drive: https://drive.google.com/a/redhat.com/file/d/0B6oBDMTK_rVpdDBBMW9LVXJwS3c/view?usp=sharing
Created attachment 1226308 [details] text_translator_extension.tar.gz Attaching the extension tarball here. I reproduced the problem in a cleanly installed fully-updated F25 VM. Immediately once I activate that extension, my session is killed and I can log in no more.
This message is a reminder that Fedora 25 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 25. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '25'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 25 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.