[Done] No cinnamon panel after upgrade to mageia 7

This forum is dedicated to basic help and support :

Ask here your questions about basic installation and usage of Mageia. For example you may post here all your questions about getting Mageia isos and installing it, configuring your printer, using your word processor etc.

Try to ask your questions in the right sub-forum with as much details as you can gather. the more precise the question will be, the more likely you are to get a useful answer

[Done] No cinnamon panel after upgrade to mageia 7

Postby JJF » Jul 2nd, '19, 07:49

I network successfully upgraded the fully updated Mageia 6 to 7.
In a dual screen set-up, I used to use cinnamon as my standard environment.
After upgrade and reboot there was no Cinnamon panel so that I was unable to manoeuvre across application and / nor logout or shut-down.
I rebooted and logged using Plasma. Opened MCC for update but there was no need to update.
Removing, reboot and reinstalled Cinnamon resulted in the same problem: no panel in Cinnamon.
Please advice.
jjf
Last edited by JJF on Oct 2nd, '19, 10:18, edited 3 times in total.
JJF
 
Posts: 216
Joined: Feb 13th, '14, 11:42

Re: No cinnamon panel after upgrade to mageia 7

Postby isadora » Jul 2nd, '19, 08:30

From errata i learn:
Cinnamon Desktop

Cinnamon requires *cinnamon-screensaver* to be added manually after install. Choose another desktop at login (ie:IceWM-session), set up online media and add the *cinnamon-screensaver* package. Than logout, change to *Cinnamon* desktop and log in.


https://wiki.mageia.org/en/Mageia_7_Err ... on_Desktop
..........bird from paradise..........

Perfection is achieved, not when there is nothing more to add, but when there is nothing left to take away.
—Antoine de Saint-Exupéry
User avatar
isadora
 
Posts: 2742
Joined: Mar 25th, '11, 16:03
Location: Netherlands

Re: No cinnamon panel after upgrade to mageia 7

Postby JJF » Jul 2nd, '19, 09:52

Cinnamon screen saver already installed
JJF
 
Posts: 216
Joined: Feb 13th, '14, 11:42

Re: No cinnamon panel after upgrade to mageia 7

Postby martinw » Jul 2nd, '19, 09:57

I think that errata is out of date, and anyway only applied to clean installs.

In my experience, Cinnamon is very bad at maintaining compatibility of its user configuration files between releases. Try adding a new user on your system and log in as that user. Do you get a working panel then?
martinw
 
Posts: 609
Joined: May 14th, '11, 10:59

Re: No cinnamon panel after upgrade to mageia 7

Postby JJF » Jul 2nd, '19, 19:17

OK. Cinnamon worked for a new user
The question still exists, how do I use this fact to implement Cinnamon to the original user
Tks
jjf
JJF
 
Posts: 216
Joined: Feb 13th, '14, 11:42

Re: No cinnamon panel after upgrade to mageia 7

Postby JJF » Jul 2nd, '19, 19:41

Further to my previous reply. Yes New user cinnamon session get a workin panel
[BTW Cinnamon (software Rendering} session ended with empty panel with no widgets]
Any clue?
JJF
 
Posts: 216
Joined: Feb 13th, '14, 11:42

Re: No cinnamon panel after upgrade to mageia 7

Postby martinw » Jul 2nd, '19, 21:09

To get a clean start, you should delete the following hidden directories in your home directory:
Code: Select all
.cinnamon
.config/cinnamon-session
.local/share/cinnamon

There's probably just one thing that needs changing, but it would likely take more time to figure out what than to reconfigure from scratch.
martinw
 
Posts: 609
Joined: May 14th, '11, 10:59

Re: No cinnamon panel after upgrade to mageia 7

Postby JJF » Jul 3rd, '19, 09:10

Deleting the 3 directories did not help.
I got:

Cinnamon just crashed . Do you want to restart cinnamon Yes No

(I saw this message also before deleting the 3directories as adviced)

When logging as another user, cinnamon with its panel is displayed in the "slave" screen while when I login i.e. Plasma, the main screen is the "master"

I guess it has to do with the dual screen and the naster screen is defined differently ,but I have no idea where to look for

Any idea? jjf
JJF
 
Posts: 216
Joined: Feb 13th, '14, 11:42

Re: No cinnamon panel after upgrade to mageia 7

Postby martinw » Jul 3rd, '19, 09:29

For the other user, start the Cinnamon system settings tool from the main menu, click on the Display icon in the Hardware section, and you should be able to reassign the primary display.

For your original user, guessing a bit here, but try deleting the
Code: Select all
.config/dconf
.config/nemo
.local/share/nemo

directories.
martinw
 
Posts: 609
Joined: May 14th, '11, 10:59

Re: No cinnamon panel after upgrade to mageia 7

Postby JJF » Jul 3rd, '19, 19:18

Thanks but your guess did not solve the problem.
At the moment, I do not get neither the desktop nor the panel. I only get the
cinnamon just crashed ....
message with just the splash screen
any better idea?
JJF
 
Posts: 216
Joined: Feb 13th, '14, 11:42

Re: No cinnamon panel after upgrade to mageia 7

Postby JJF » Jul 3rd, '19, 22:13

I found the file: org.cinnamon.settings.xml in the directory /usr/share/glib-2.0/schemas
<?xml version="1.0" encoding="UTF-8"?>
<schemalist>
<schema path="/org/cinnamon/settings-daemon/plugins/xrandr/" id="org.cinnamon.settings-daemon.plugins.xrandr" gettext-domain="cinnamon-settings-daemon">
<key type="s" name="default-configuration-file">
<default>'/etc/cinnamon-settings-daemon/xrandr/monitors.xml'</default>
<summary>File for default configuration for RandR</summary>
<description>The XRandR plugin will look for a default configuration in the file specified by this key. This is similar to the ~/.config/monitors.xml that normally gets stored in users' home directories. If a user does not have such a file, or has one that does not match the user's setup of monitors, then the file specified by this key will be used instead.</description>
</key>
<key name="default-monitors-setup" enum="org.cinnamon.settings-daemon.CsdXrandrBootBehaviour">
<default>'follow-lid'</default>
<summary>Whether to turn off specific monitors after boot</summary>
<description>clone' will display the same thing on all monitors, 'dock' will switch off the internal monitor, 'do-nothing' will use the default Xorg behaviour (extend the desktop in recent versions). The default, 'follow-lid', will choose between 'do-nothing' and 'dock' depending on whether the lid is (respectively) open or closed.</description>
</key>
</schema>
</schemalist.


I need help to make use of it
Can you help?
JJF
 
Posts: 216
Joined: Feb 13th, '14, 11:42

Re: No cinnamon panel after upgrade to mageia 7

Postby martinw » Jul 4th, '19, 00:53

Do you have a .config/monitors.xml file in your home directory? If so, that could be the culprit.
martinw
 
Posts: 609
Joined: May 14th, '11, 10:59

Re: No cinnamon panel after upgrade to mageia 7

Postby JJF » Jul 4th, '19, 17:30

Indeed, there is a "monitors.xml" file in the ./config directory.
Question:
If I'll replace the current monitors.xml file with the above quoted file, will it affect other desktop? i.e. Plasma?
I am using other desktops , Plasma, Gnome, when running into trouble with Cinnamon .
Please advice
jjf
JJF
 
Posts: 216
Joined: Feb 13th, '14, 11:42

Re: No cinnamon panel after upgrade to mageia 7

Postby JJF » Jul 4th, '19, 19:50

Some progress and more info

While logged in Plasma, I replaced the "monitors.xls" with the new one, than logged out and logged in in Cinnamon
The desktop was shown in the 2 screens, but no panel or launcher. I could not exit and / or reboot. I forced shut-down using the computer power button

I restarted the computer and logged in in Cinnamon as the "faulty" user . No desktop and no panel. just the splash screen.I forced shut-down using the computer power button

I restarted the computer and logged in in Plasma with the "faulty" user.Every thing was normal.

logged out Plasma and logged in in Cinnamon. the desktop was there in the 2 screens but no panel

I double clicked the "computer " icon on the cinnamon desktop and could use the available console. This enabled me to launch applications i.e MCC, firefox, Kwrite etc. Some application could be launched by double kliking their icons on the desktop.
B U T
Without the panel or launcher I could not logout or shut-down. I had to force shut-down using the computer power button
Does this info useful?
JJF
 
Posts: 216
Joined: Feb 13th, '14, 11:42

Re: No cinnamon panel after upgrade to mageia 7

Postby martinw » Jul 4th, '19, 19:52

What I would do is move that file up a level into your home directory, then log out and log back in again. If Cinnamon is then working properly, adjust the display settings as you want in the Cinnamon system settings. If there's any problem, you can always move the file back. Even if it prevents all other DEs from working (which I very much doubt), if you press Ctrl-Alt-F3 at the login screen, you will get a text login prompt, where you can log in and move the file back again by
Code: Select all
mv monitors.xml .config/monitors.xml
martinw
 
Posts: 609
Joined: May 14th, '11, 10:59

Re: No cinnamon panel after upgrade to mageia 7

Postby JJF » Jul 5th, '19, 09:15

Thanks.
BUT monitors.xml already placed in the ./config directory.
I described the situation after monitors.xml was placed in the ./config directory
What now?
jjf
JJF
 
Posts: 216
Joined: Feb 13th, '14, 11:42

Re: No cinnamon panel after upgrade to mageia 7

Postby doktor5000 » Jul 5th, '19, 16:11

You should simply rename ~/.config/monitors.xml to something else, you can recreate it later once you got a working session again.
Cauldron is not for the faint of heart!
Caution: Hot, bubbling magic inside. May explode or cook your kittens!
----
Disclaimer: Beware of allergic reactions in answer to unconstructive complaint-type posts
User avatar
doktor5000
 
Posts: 17629
Joined: Jun 4th, '11, 10:10
Location: Leipzig, Germany

Re: No cinnamon panel after upgrade to mageia 7

Postby JJF » Jul 6th, '19, 22:15

This did not solve the problem

I can recall when I had problem setting 2 screen, it ended with custom xrandr as follows:
Code: Select all
xrandr
Screen 0: minimum 320 x 200, current 2560 x 1024, maximum 32767 x 32767
VGA1 connected primary 1280x1024+0+0 (normal left inverted right x axis y axis) 0mm x 0mm
   1280x1024_60   60.0*
   1280x1024      60.0 
   1280x960_60    60.0 
   1152x864_60    60.0 
   1024x768       60.0 
   1024x768_60    60.0 
   832x624_60     60.0 
   800x600        60.3     56.2 
   800x600_60     60.0 
   640x480        59.9 
HDMI1 disconnected (normal left inverted right x axis y axis)
HDMI2 connected 1280x1024+1280+0 (normal left inverted right x axis y axis) 376mm x 301mm
   1280x1024      75.0*+   60.0 
   1280x960       60.0 
   1280x800       74.9     59.9 
   1152x864       75.0     60.0 
   1280x768       74.9     60.0 
   1280x720       60.0 
   1024x768       75.1     70.1     60.0 
   1024x576       60.0 
   800x600        72.2     75.0     60.3     56.2 
   848x480        60.0 
   640x480        75.0     72.8     60.0 
   720x400        70.1 
VIRTUAL1 disconnected (normal left inverted right x axis y axis)

which worked perfect since then. (or it might have been replaced by mageia update sometime in between 2014 and now)
Anyway, I am unable to check whether cinnamon uses this file and where is its "run" version
Could this be the source of the problem, as a new cinnamon user is OK?

jjf
Last edited by isadora on Jul 7th, '19, 08:20, edited 1 time in total.
Reason: Placed command-output in between [CODE]-tags for better readability ;)
JJF
 
Posts: 216
Joined: Feb 13th, '14, 11:42

Re: No cinnamon panel after upgrade to mageia 7

Postby martinw » Jul 8th, '19, 10:04

If I'm not mistaken, Cinnamon uses ~/.config/monitors.xml to store the xrandr information.
Not sure what else to suggest. As Cinnamon is working for the new user, it still seems likely that there is some old configuration file that's causing the problem.
martinw
 
Posts: 609
Joined: May 14th, '11, 10:59

Re: No cinnamon panel after upgrade to mageia 7

Postby JJF » Jul 8th, '19, 11:35

Is there a way to create a panel or a launcher using command line? (I am able to access root command line when logging in after logging out from plasma)
I, also, guess that at certain point during boot there is message indicating why cinnamom can't open the panel. How do I find this message?
Tks
JJF
JJF
 
Posts: 216
Joined: Feb 13th, '14, 11:42

Re: No cinnamon panel after upgrade to mageia 7

Postby doktor5000 » Jul 8th, '19, 13:32

You can also try this, after logging in as the user with the missing panel: https://community.linuxmint.com/tutorial/view/2195

On how you find the messages from cinnamon, login as that user, and then either as that user or as root run journalctl -ab and look at the end of the log for that boot. Also have a look at ~/.xsession-errors as it might have some pointers.
Cauldron is not for the faint of heart!
Caution: Hot, bubbling magic inside. May explode or cook your kittens!
----
Disclaimer: Beware of allergic reactions in answer to unconstructive complaint-type posts
User avatar
doktor5000
 
Posts: 17629
Joined: Jun 4th, '11, 10:10
Location: Leipzig, Germany

Re: No cinnamon panel after upgrade to mageia 7

Postby JJF » Jul 9th, '19, 19:36

The situation is as follows:
When I boot directly to cinnamon I get only flash screen; No panel, no desktop, no menu and no launcher.To exit I have to hardware reset the computer.
If I login to cinnamon after I've logged out of plasma, I get the desktop split into the 2 screens, but no panel, no menu and no launcher. I am able to access the console if I double click the computer icon. To exit I cat only reboot or push the on/off button. "gsetting etc".... as suggested by doktor5000 did not do any good.

I did not manage to find /.xsession-error. Waht is iys full path?

I attach the journal -b results of both when directly boot into cinnamon as well as logging in after logging out of plasma respectively

Code: Select all
journalctl_boot_cinnamon.txt
Jul 09 18:24:08 localhost.localdomain kernel: sd_pico[1530]: segfault at 7f9e35b24010 ip 00007f9e3735dd1e sp 00007ffc869b6338 error 4 in libttspico.so.0.0.0[7f9e3735b000+3b000]
Jul 09 18:25:10 localhost.localdomain kwalletd5[2627]: Wallet failed to get opened by PAM, error code is -9
Jul 09 18:25:38 localhost.localdomain kernel: cinnamon[2935]: segfault at 0 ip 00007fb0e6114eee sp 00007fff8bc82c50 error 4 in libupower-glib.so.3.0.1[7fb0e6113000+13000]
Jul 09 18:26:58 localhost.localdomain pulseaudio[2834]: XIO:  fatal IO error 11 (Resource temporarily unavailable) on X server ":0"
Jul 09 18:26:58 localhost.localdomain at-spi-bus-launcher[2748]: XIO:  fatal IO error 11 (Resource temporarily unavailable) on X server ":0"
Jul 09 18:26:58 localhost.localdomain cpupower[3597]: Error setting new values. Common errors:
Jul 09 18:26:58 localhost.localdomain sddm[2019]: Authentication error: "Process crashed"
Jul 09 18:26:58 localhost.localdomain sddm[2019]: Authentication error: "Process crashed"



Code: Select all
journalctl_cinnamon_Login_After_plasma_logout.txt

Jul 09 18:27:58 localhost.localdomain kernel: sd_pico[1402]: segfault at 7f6e88bb7010 ip 00007f6e8a3f0d1e sp 00007fff069f91b8 error 4 in libttspico.so.0.0.0[7f6e8a3ee000+3b000]
Jul 09 18:28:46 localhost.localdomain ksmserver[2810]: Qt: Session management error: networkIdsList argument is NULL
Jul 09 18:28:50 localhost.localdomain kwalletd5[2648]: Wallet failed to get opened by PAM, error code is -9
Jul 09 18:28:57 localhost.localdomain kwin_x11[2832]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 924, resource id: 27262984, major code: 3 (GetWindowAttributes), minor code: 0
Jul 09 18:28:57 localhost.localdomain kwin_x11[2832]: qt.qpa.xcb: QXcbConnection: XCB error: 9 (BadDrawable), sequence: 925, resource id: 27262984, major code: 14 (GetGeometry), minor code: 0
Jul 09 18:28:57 localhost.localdomain kwin_x11[2832]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 1083, resource id: 27263004, major code: 3 (GetWindowAttributes), minor code: 0
Jul 09 18:28:57 localhost.localdomain kwin_x11[2832]: qt.qpa.xcb: QXcbConnection: XCB error: 9 (BadDrawable), sequence: 1084, resource id: 27263004, major code: 14 (GetGeometry), minor code: 0
Jul 09 18:28:57 localhost.localdomain kwin_x11[2832]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 1089, resource id: 60817412, major code: 18 (ChangeProperty), minor code: 0
Jul 09 18:28:57 localhost.localdomain kwin_x11[2832]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 1093, resource id: 60817413, major code: 18 (ChangeProperty), minor code: 0
Jul 09 18:28:57 localhost.localdomain kwin_x11[2832]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 1097, resource id: 12582917, major code: 18 (ChangeProperty), minor code: 0
Jul 09 18:29:04 localhost.localdomain kwin_x11[2832]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 1917, resource id: 69206018, major code: 18 (ChangeProperty), minor code: 0
Jul 09 18:29:09 localhost.localdomain /hp-systray[2940]: hp-systray[2940]: error: option -s not recognized
Jul 09 18:29:12 localhost.localdomain kwin_x11[2832]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 2097, resource id: 4194359, major code: 18 (ChangeProperty), minor code: 0
Jul 09 18:29:27 localhost.localdomain kwin_x11[2832]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 3445, resource id: 35651590, major code: 19 (DeleteProperty), minor code: 0
Jul 09 18:29:27 localhost.localdomain kwin_x11[2832]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 3455, resource id: 35651590, major code: 19 (DeleteProperty), minor code: 0
Jul 09 18:29:27 localhost.localdomain kwin_x11[2832]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 3456, resource id: 35651590, major code: 18 (ChangeProperty), minor code: 0
Jul 09 18:29:27 localhost.localdomain kwin_x11[2832]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 3457, resource id: 35651590, major code: 19 (DeleteProperty), minor code: 0
Jul 09 18:29:27 localhost.localdomain kwin_x11[2832]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 3458, resource id: 35651590, major code: 19 (DeleteProperty), minor code: 0
Jul 09 18:29:27 localhost.localdomain kwin_x11[2832]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 3459, resource id: 35651590, major code: 19 (DeleteProperty), minor code: 0
Jul 09 18:29:27 localhost.localdomain kwin_x11[2832]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 3460, resource id: 35651590, major code: 7 (ReparentWindow), minor code: 0
Jul 09 18:29:27 localhost.localdomain kwin_x11[2832]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 3461, resource id: 35651590, major code: 6 (ChangeSaveSet), minor code: 0
Jul 09 18:29:27 localhost.localdomain kwin_x11[2832]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 3462, resource id: 35651590, major code: 2 (ChangeWindowAttributes), minor code: 0
Jul 09 18:29:27 localhost.localdomain kwin_x11[2832]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 3463, resource id: 35651590, major code: 10 (UnmapWindow), minor code: 0
Jul 09 18:30:00 localhost.localdomain kdeinit5[4031]: Qt: Session management error: networkIdsList argument is NULL
Jul 09 18:30:01 localhost.localdomain plasmashell[2857]: qt.qpa.xcb: QXcbConnection: XCB error: 2 (BadValue), sequence: 2188, resource id: 71303215, major code: 141 (Unknown), minor code: 3
Jul 09 18:30:02 localhost.localdomain plasmashell[2857]: qt.qpa.xcb: QXcbConnection: XCB error: 2 (BadValue), sequence: 2195, resource id: 58720262, major code: 141 (Unknown), minor code: 3
Jul 09 18:30:24 localhost.localdomain kwin_x11[2832]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 18997, resource id: 33554659, major code: 18 (ChangeProperty), minor code: 0
Jul 09 18:30:24 localhost.localdomain kwin_x11[2832]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 19002, resource id: 33554660, major code: 18 (ChangeProperty), minor code: 0
Jul 09 18:42:29 localhost.localdomain kwin_x11[2832]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 47252, resource id: 90177595, major code: 18 (ChangeProperty), minor code: 0
Jul 09 18:42:32 localhost.localdomain kwin_x11[2832]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 47695, resource id: 37748743, major code: 18 (ChangeProperty), minor code: 0
Jul 09 18:42:32 localhost.localdomain kwin_x11[2832]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 47699, resource id: 73400325, major code: 18 (ChangeProperty), minor code: 0
Jul 09 18:42:32 localhost.localdomain kwin_x11[2832]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 47703, resource id: 44040197, major code: 18 (ChangeProperty), minor code: 0
Jul 09 18:42:32 localhost.localdomain kwin_x11[2832]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 47707, resource id: 35651600, major code: 18 (ChangeProperty), minor code: 0
Jul 09 18:42:32 localhost.localdomain kwin_x11[2832]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 47711, resource id: 39845893, major code: 18 (ChangeProperty), minor code: 0
Jul 09 18:42:32 localhost.localdomain kwin_x11[2832]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 47715, resource id: 12582919, major code: 18 (ChangeProperty), minor code: 0
Jul 09 18:42:32 localhost.localdomain kwin_x11[2832]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 47719, resource id: 75497477, major code: 18 (ChangeProperty), minor code: 0
Jul 09 18:42:32 localhost.localdomain kwin_x11[2832]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 47720, resource id: 92274695, major code: 15 (QueryTree), minor code: 0
Jul 09 18:42:32 localhost.localdomain kwin_x11[2832]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 47755, resource id: 92276562, major code: 18 (ChangeProperty), minor code: 0
Jul 09 18:42:32 localhost.localdomain kwin_x11[2832]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 47798, resource id: 52428812, major code: 18 (ChangeProperty), minor code: 0
Jul 09 18:42:32 localhost.localdomain kwin_x11[2832]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 47854, resource id: 58720272, major code: 18 (ChangeProperty), minor code: 0
Jul 09 18:42:32 localhost.localdomain kwin_x11[2832]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 47910, resource id: 56623120, major code: 18 (ChangeProperty), minor code: 0
Jul 09 18:42:32 localhost.localdomain kwin_x11[2832]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 47964, resource id: 54525968, major code: 18 (ChangeProperty), minor code: 0
Jul 09 18:42:32 localhost.localdomain kwin_x11[2832]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 47993, resource id: 31457300, major code: 18 (ChangeProperty), minor code: 0
Jul 09 18:42:32 localhost.localdomain kwin_x11[2832]: qt.qpa.xcb: QXcbConnection: XCB error: 8 (BadMatch), sequence: 48012, resource id: 71303215, major code: 42 (SetInputFocus), minor code: 0
Jul 09 18:42:32 localhost.localdomain kwin_x11[2832]: qt.qpa.xcb: QXcbConnection: XCB error: 8 (BadMatch), sequence: 48044, resource id: 71303215, major code: 42 (SetInputFocus), minor code: 0
Jul 09 18:42:32 localhost.localdomain kwin_x11[2832]: qt.qpa.xcb: QXcbConnection: XCB error: 8 (BadMatch), sequence: 48051, resource id: 71303171, major code: 42 (SetInputFocus), minor code: 0
Jul 09 18:42:32 localhost.localdomain kwin_x11[2832]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 48205, resource id: 41943045, major code: 18 (ChangeProperty), minor code: 0
Jul 09 18:42:34 localhost.localdomain kscreen_backend_launcher[2836]: The X11 connection broke (error 1). Did the X11 server die?
Jul 09 18:42:34 localhost.localdomain at-spi-bus-launcher[3096]: XIO:  fatal IO error 11 (Resource temporarily unavailable) on X server ":0"
Jul 09 18:42:34 localhost.localdomain kuiserver5[3390]: The X11 connection broke (error 1). Did the X11 server die?
Jul 09 18:42:34 localhost.localdomain kactivitymanagerd[2904]: The X11 connection broke (error 1). Did the X11 server die?
Jul 09 18:42:34 localhost.localdomain kdeconnectd[6472]: The X11 connection broke (error 1). Did the X11 server die?
Jul 09 18:42:34 localhost.localdomain kglobalaccel5[2818]: The X11 connection broke (error 1). Did the X11 server die?
Jul 09 18:42:51 localhost.localdomain kwalletd5[6568]: Wallet failed to get opened by PAM, error code is -9
Jul 09 18:43:06 localhost.localdomain kernel: cinnamon[6797]: segfault at 0 ip 00007f4ec8246eee sp 00007ffe317cc5d0 error 4 in libupower-glib.so.3.0.1[7f4ec8245000+13000]


The first list tells me
Code: Select all
 XIO:  fatal IO error 11 (Resource temporarily unavailable) on X server ":0"


and the 2nd list tells me
Code: Select all
 XIO:  fatal IO error 11 (Resource temporarily unavailable) on X server ":0"
The X11 connection broke (error 1). Did the X11 server die?



Unfortunately I am unable to conclude where to further look or how to further trace the error source. I need a close guidance to do that
Can you help?

JJF
Last edited by isadora on Jul 9th, '19, 23:13, edited 2 times in total.
Reason: Placed command-output in between [CODE]-tags for better readability ;)
JJF
 
Posts: 216
Joined: Feb 13th, '14, 11:42

Re: No cinnamon panel after upgrade to mageia 7

Postby doktor5000 » Jul 10th, '19, 18:07

JJF wrote:I did not manage to find /.xsession-error. Waht is iys full path?

~/.xsession-errors is basically the full path, you can just copy&paste that into your terminal.
~ equates to /home/username so this would become /home/jjf/.xsession-errors if your username is jjf.


JJF wrote:Jul 09 18:25:38 localhost.localdomain kernel: cinnamon[2935]: segfault at 0 ip 00007fb0e6114eee sp 00007fff8bc82c50 error 4 in libupower-glib.so.3.0.1[7fb0e6113000+13000]

[...]

Jul 09 18:25:38 localhost.localdomain kernel: cinnamon[2935]: segfault at 0 ip 00007fb0e6114eee sp 00007fff8bc82c50 error 4 in libupower-glib.so.3.0.1[7fb0e6113000+13000]


This might be part of the issue. See e.g. https://forums.linuxmint.com/viewtopic.php?t=289494
Although if that would be the cause, then I don't get how it works for a different user on the same system without issues.

Apart from that the short log excerpts are not really that helpful, I'd suggest actually attaching the full log after regular boot to cinnamon
Code: Select all
journalctl -ab > /tmp/journal.log

and then attach the whole /tmp/journal.log here.

Can you please also check whether you have a file ~/.Xauthority ? Best as root post the output of

Code: Select all
ls -al /home/*/.X*
Cauldron is not for the faint of heart!
Caution: Hot, bubbling magic inside. May explode or cook your kittens!
----
Disclaimer: Beware of allergic reactions in answer to unconstructive complaint-type posts
User avatar
doktor5000
 
Posts: 17629
Joined: Jun 4th, '11, 10:10
Location: Leipzig, Germany

Re: No cinnamon panel after upgrade to mageia 7

Postby JJF » Jul 11th, '19, 21:04

Doktor5000
I tried to follow your instructions, but as I was unable to open terminal after cinnamon boot, as there is only the flash screen , I restarted and logged in into plasma in order to copy and submit the required files

both Xsession-error and journal -ab are tremendously long!!! and exceed the allowed number of lines in a reply .
I noticed that there are numerous identical lines in both files but I don't have a practical method to delete duplicate lines

If I logout of plasm and thereafter login to cinnamon, I can open the terminal and get these files from within cinnamom. Could it be usefull?

please advice


Code: Select all
ls -al /home/*/.X*
-rw------- 1 jacob jacob 132 Jul 11 21:14 /home/jacob/.Xauthority
-rw------- 1 jacob jacob 176 Feb 28  2016 /home/jacob/.Xauthority.6lOsu
-rw------- 1 jacob jacob  66 Jul 26  2017 /home/jacob/.Xauthority.uxjkg




best
jjf
JJF
 
Posts: 216
Joined: Feb 13th, '14, 11:42

Re: No cinnamon panel after upgrade to mageia 7

Postby doktor5000 » Jul 14th, '19, 03:08

Permissions for the .Xauthority files look fine, should not be the issue I thought it could be.
JJF wrote:both Xsession-error and journal -ab are tremendously long!!! and exceed the allowed number of lines in a reply .

Just attach the whole files.
Cauldron is not for the faint of heart!
Caution: Hot, bubbling magic inside. May explode or cook your kittens!
----
Disclaimer: Beware of allergic reactions in answer to unconstructive complaint-type posts
User avatar
doktor5000
 
Posts: 17629
Joined: Jun 4th, '11, 10:10
Location: Leipzig, Germany

Next

Return to Basic support

Who is online

Users browsing this forum: No registered users and 1 guest

cron