Description of problem:
Just started MATE in a VM.
Version-Release number of selected component:
Thread no. 1 (9 frames)
#4 dconf_engine_change_completed at dconf-engine.c:893
#5 dconf_gdbus_method_call_done at dconf-gdbus-thread.c:230
#6 g_simple_async_result_complete at gsimpleasyncresult.c:777
#7 g_dbus_connection_call_done at gdbusconnection.c:5333
#8 g_simple_async_result_complete at gsimpleasyncresult.c:777
#9 complete_in_idle_cb at gsimpleasyncresult.c:789
#13 g_main_context_iteration at gmain.c:3420
#14 dconf_gdbus_worker_thread at dconf-gdbus-thread.c:81
#15 g_thread_proxy at gthread.c:798
Created attachment 685044 [details]
Created attachment 685045 [details]
Created attachment 685046 [details]
Created attachment 685047 [details]
Created attachment 685048 [details]
Created attachment 685049 [details]
Created attachment 685050 [details]
Created attachment 685051 [details]
Created attachment 685052 [details]
Created attachment 685053 [details]
Created attachment 685054 [details]
Please run yum update and reopen this bug if you still experience issues.
Yes, the bug is still there after the update. Why close the bug and especially why NOTABUG?
Sorry. What are the steps to reproduce?
I meet this bug too. In the beginning MATE started to work but recently mate-panel is chrashing repeatedly each time when I log in intro a MATE session.
Gnome3 works, but I am a passionate gnome3 hater. This bug locks me back to RHEL6 and Gnome2. I am intended to switch to F18/MATE as it becomes stable.
Do you need some files? (I have 24 abrt directories with component=mate-panel)
(In reply to comment #15)
> I meet this bug too. In the beginning MATE started to work but recently
> mate-panel is chrashing repeatedly each time when I log in intro a MATE
> Gnome3 works, but I am a passionate gnome3 hater. This bug locks me back to
> RHEL6 and Gnome2. I am intended to switch to F18/MATE as it becomes stable.
> Do you need some files? (I have 24 abrt directories with
Hopefully mate-window-manager-1.5.3-3.fc18 helps.
And MATE on F18 is pretty darn stable.
There are a round of MATE updates coming shortly via upstream.
mate-window-manager-1.5.3-3.fc18 has been submitted as an update for Fedora 18.
mate-window-manager-1.5.3-3.fc18 is installed, and a new mwm session appeared in the gdm session menu.
When I choose MATE, get the mate-panel dying syndrome.
When I choose Mwm, I am getting a single window probably the workspace selector or alike. With right-clicking on the root window, I got some menu, clicking on the new window I got a terminal window.
typing mate-session resulted in the mate-panel crashing syndrome again.
So I am confused. Can you give some hint on resolving the issue. (My first idea to remove temporarily all window managers except mwm. Maybe I will try it tonight - Brno time, thus CET.)
Which is the right display manager for mate?
It is crashing with lightdm and gdm.
Perhaps my home directory wrt mate is screwed up?!
(I run gnome2 (from RHEL6) and gnome3 (from F18) and seen some MATE migration tool in my session startup even without asking for it.)
I'll try to rename anll mate specific directories in my home as next step.
renaming .mateconf to ,mateconf ,
.mateconfd to ,mateconfd
not changed anything, mate-panel still crashed.
Will retry yum reinstall @mate again.
No luck. BTW this time gnome3 come up with Applications instead of Activities - the most hated Gnome3 component.
Maybe I can give up hopes and go the gome3 way?
I left out (among other seeming unnecessary) features from kernel:
extfs4 (a braindamage for desktops like btrfs but less crappy)
ipv6 (my WL-1500R has no ipv6 support at all)
fuse (a resource hog, I prefer in-kernel filesystems instead of the userspace)
Any of them is a must for MATE?
mate-window-manager-1.5.3-3.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report.
I just realized you're running rawhide and asking for stability. Please yum downgrade mate-panel. The recent updates to libmatkbd, mate-panel, etc. etc. not worth it. Use what's in F18.
Sorry I misdirected by bug a bit.
Here is my environment:
[bne@panther ~]$ cat /etc/redhat-release
Fedora release 18 (Spherical Cow)
[bne@panther ~]$ uname -r
So (f18) 3.7.4 based cut-down kernel.
[bne@panther ~]$ rpm -q mate-panel
[bne@panther ~]$ sudo yum repolist enabled
Loaded plugins: langpacks, presto, refresh-packagekit
repo id repo name status
adobe-linux-x86_64 Adobe Systems Incorporated 2
beaker-client/18 Beaker Client - Fedora18 18
fedora/18/x86_64 Fedora 18 - x86_64 33868
google-chrome google-chrome 3
qa-tools QA Tools Incubator 207
rhpkg/18 rhpkg for Fedora 18 9
updates/18/x86_64 Fedora 18 - x86_64 - Updates 10827
updates-testing/18/x86_64 Fedora 18 - x86_64 - Test Updates 13967
updates-testing-debuginfo/18/x86_64 Fedora 18 - x86_64 - Test Updates Debug 1728
And mate-panel is steadily crashing.
So re-address my complaints to F18 released, please.
(I have no intention to sit on the bleeding edge...)
In the end I persuaded mate-session to start
with this .xinitrc file
and ran startx
(in english, not german as MATE decided when started trough gdm), now I feel a bit better.
lightdm was crashing, had to switch to gnome, but after the first login the session selection disappeared and swicthed the locale to German.
While I am not completely frustrated with German - Ja, ich spreche ein wenigh Deutch - hard to say I am satisfied with it.
My efforts to install a fresh F18 failed, while I wanted to start with a clean install as this copy was made trough F17 in F18Beta time and there are no miracles, it has some issues.
Looks like I understood the issue in the end.
By removing the mate-file-manager I made my mate-desktop unusable, however IMHO
any file manager is only an optional part of an x-session - consider the security aspects - , and the crash of mate-panel in this case is a bug, and probably means some mate-panel related file is in mate-file-manager or in in a package depending on it like mate-vfs. ( I removed the startuo of file-manager from my startup, and it is functional without it but must be installed ATM)
(BTW the same is true for Gnome3, but gnome2 is exempt of this issue.)
mate-panel-1.5.5-1.fc18 has been submitted as an update for Fedora 18.
* should fix your issue,
* was pushed to the Fedora 18 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing mate-panel-1.5.5-1.fc18'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).
mate-panel-1.5.5-1.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report.