Did update - Evolution will not start SOLVED

mt_arch_user · 2023-12-31 15:56:40

Just did an update:

sudo pacman -Syu

Did a reboot

Logged in and tried to start Evolution from the desktop. Would not start.
Opened terminal window (Konsole)

Got the following result:

[bart@ASU-X99 ~]$ evolution
src/nv_gbm.c:242: GBM-DRV error (nv_gbm_create_device_native): nv_common_gbm_create_device failed (ret=-1)

Segmentation fault (core dumped)
[bart@ASU-X99 ~]$

Now what?

Last edited by mt_arch_user (2024-01-01 00:03:02)

Head_on_a_Stick · 2023-12-31 16:44:56

Downgrade the upgraded packages one at a time to see which one caused the problem. You could also try to obtain a backtrace from the core dump, details on the wiki.

nevim42 · 2023-12-31 16:46:05

In my case it was mesa package. I downgraded to mesa-1:23.3.1-1 and it works

Scimmia · 2023-12-31 16:54:17

https://wiki.archlinux.org/title/Debugg … ing_traces

mt_arch_user · 2023-12-31 23:09:57

All I can get from the core dump is this:

[bart@ASU-X99 ~]$ sudo coredumpctl -1 info evolution
[sudo] password for root: 
           PID: 2400 (evolution)
           UID: 1000 (bart)
           GID: 984 (users)
        Signal: 11 (SEGV)
     Timestamp: Sun 2023-12-31 13:40:16 MST (2h 14min ago)
  Command Line: evolution
    Executable: /usr/bin/evolution
 Control Group: /user.slice/user-1000.slice/user@1000.service/app.slice/app-org.kde.konsole-b98e8cd7518a4f0a8104a7c15b41bed9.scope
          Unit: user@1000.service
     User Unit: app-org.kde.konsole-b98e8cd7518a4f0a8104a7c15b41bed9.scope
         Slice: user-1000.slice
     Owner UID: 1000 (bart)
       Boot ID: 4a41066494304a85ab1350dcae4ebbdd
    Machine ID: 67e6866436094cea8ba2aab255f1c36b
      Hostname: ASU-X99
       Storage: /var/lib/systemd/coredump/core.evolution.1000.4a41066494304a85ab1350dcae4ebbdd.2400.1704055216000000.zst (present)
  Size on Disk: 7.7M
       Message: Process 2400 (evolution) of user 1000 dumped core.
                
                Stack trace of thread 2400:
                #0  0x00007f043b2b3324 n/a (kms_swrast_dri.so + 0x6b3324)
                #1  0x00007f043b7acd94 n/a (kms_swrast_dri.so + 0xbacd94)
                #2  0x00007f043acba376 n/a (kms_swrast_dri.so + 0xba376)
                #3  0x00007f043acc70f4 n/a (kms_swrast_dri.so + 0xc70f4)
                #4  0x00007f043acc76b5 n/a (kms_swrast_dri.so + 0xc76b5)
                #5  0x00007f04e7eb2bc7 n/a (libgbm.so.1 + 0x6bc7)
                #6  0x00007f04e7eb2d91 n/a (libgbm.so.1 + 0x6d91)
                #7  0x00007f04e7eb509d n/a (libgbm.so.1 + 0x909d)
                #8  0x00007f04e7eb28dc n/a (libgbm.so.1 + 0x68dc)
                #9  0x00007f04e7eb2a19 gbm_create_device (libgbm.so.1 + 0x6a19)

So I copied the relevant part of the pacman.log

[2023-12-31T08:24:31-0700] [ALPM] upgraded exempi (2.6.4-1 -> 2.6.5-1)
[2023-12-31T08:24:31-0700] [ALPM] upgraded fontconfig (2:2.14.2-1 -> 2:2.15.0-1)
[2023-12-31T08:24:34-0700] [ALPM] upgraded krb5 (1.20.1-2 -> 1.21.2-2)
[2023-12-31T08:24:34-0700] [ALPM] upgraded systemd-libs (255.1-1 -> 255.2-1)
[2023-12-31T08:24:34-0700] [ALPM] upgraded libseccomp (2.5.4-2 -> 2.5.5-1)
[2023-12-31T08:24:34-0700] [ALPM] upgraded systemd (255.1-1 -> 255.2-1)
[2023-12-31T08:24:35-0700] [ALPM] upgraded mesa (1:23.3.1-1 -> 1:23.3.2-1)
[2023-12-31T08:24:36-0700] [ALPM] upgraded gtk3 (1:3.24.39-1 -> 1:3.24.39-2)
[2023-12-31T08:24:36-0700] [ALPM] upgraded openmpi (4.1.5-5 -> 4.1.6-1)
[2023-12-31T08:24:36-0700] [ALPM] upgraded gnome-settings-daemon (45.0-2 -> 45.1-1)
[2023-12-31T08:24:36-0700] [ALPM] upgraded imagemagick (7.1.1.23-1 -> 7.1.1.24-1)
[2023-12-31T08:24:36-0700] [ALPM] upgraded iputils (20221126-2 -> 20231222-1)
[2023-12-31T08:24:36-0700] [ALPM] upgraded onetbb (2021.10.0-1 -> 2021.11.0-1)
[2023-12-31T08:24:36-0700] [ALPM] upgraded kicad (7.0.9-2 -> 7.0.10-1)
[2023-12-31T08:24:37-0700] [ALPM] upgraded kicad-library (7.0.9-1 -> 7.0.10-1)
[2023-12-31T08:24:46-0700] [ALPM] upgraded kicad-library-3d (7.0.9-1 -> 7.0.10-1)
[2023-12-31T08:24:46-0700] [ALPM] upgraded leptonica (1.83.1-1 -> 1.84.0-1)
[2023-12-31T08:24:46-0700] [ALPM] upgraded libtraceevent (1:1.7.3-1 -> 1:1.8.1-1)
[2023-12-31T08:24:51-0700] [ALPM] upgraded meson (1.3.0-2 -> 1.3.1-1)
[2023-12-31T08:24:51-0700] [ALPM] upgraded ppp (2.5.0-1 -> 2.5.0-2)
[2023-12-31T08:24:51-0700] [ALPM] upgraded python-fastjsonschema (2.19.0-1 -> 2.19.1-1)
[2023-12-31T08:24:51-0700] [ALPM] upgraded python-setuptools (1:69.0.2-1 -> 1:69.0.3-1)
[2023-12-31T08:24:51-0700] [ALPM] upgraded qpdf (11.6.4-1 -> 11.7.0-1)
[2023-12-31T08:24:52-0700] [ALPM] upgraded qt6-base (6.6.1-2 -> 6.6.1-3)
[2023-12-31T08:24:52-0700] [ALPM] upgraded systemd-sysvcompat (255.1-1 -> 255.2-1)

Everything but Evolution seems to be working just fine. I'm using KDE as a desktop enviornment and Evolution is a Gnome package.
@nevim42 referenced mesa but that package seems to be video driver related and my desktop is working well. Do you think mesa is OK?

I'm thinking the files for kicad should be ok.
And fontconfig

The error message indicated gbm_create_device. I don't see that in the list of updates. Isn't there a pacman command to tell me what file contains that program?

If I downgrade any of these packages, will they upgrade again if I do packman -Syu again?

Scimmia · 2023-12-31 23:11:44

Nvidia system, right? See https://bbs.archlinux.org/viewtopic.php … 4#p2140364

mt_arch_user · 2023-12-31 23:35:50

Scimmia wrote:

Nvidia system, right? See https://bbs.archlinux.org/viewtopic.php … 4#p2140364

Yup!
However, the post you refer to would seem to indicate a problem at boot. I have a problem with only one program - Evolution.

Guess I'll try downgrading it and see. Let you know.

Scimmia · 2023-12-31 23:40:39

So instead of fixing the issue by not using swrast, which you shouldn't be using anyway, you want to workaround it by doing a partial update?

mt_arch_user · 2024-01-01 00:02:30

Well, downgrading mesa did the trick.

I'll have to lock out mesa for a while.

Thanks all for the help!

Scimmia · 2024-01-01 00:33:55

I really hope that others coming across this thread realize that that is not a solution and a terrible idea.

c00ter · 2024-01-01 04:35:56

It's a terrible idea.

Newcomers seem to come on with all the gusto that has served army generals for millennia. While their enthusiasm is to be admired...

Old quote:
"You buy 'em books and buy 'em books, but all they ever do is rip the covers and eat the pages."

Last edited by c00ter (2024-01-01 04:36:39)

seth · 2024-01-01 09:42:12

mt_arch_user wrote:

However, the post you refer to would seem to indicate a problem at boot. I have a problem with only one program - Evolution.

"Your example would indicate a burning living room, but for me it's the bedroom. So I don't think that my house is on fire."
You most likely have a static server config (nvidia-settings generated) that plows through with the server, but you still have the exact same core issue - so fix that.
Or, with apologies to c00ter, I'll make arrogant European jokes about American literacy and homeschooling.

Arch Linux

#1 2023-12-31 15:56:40

Did update - Evolution will not start SOLVED

#2 2023-12-31 16:44:56

Re: Did update - Evolution will not start SOLVED

#3 2023-12-31 16:46:05

Re: Did update - Evolution will not start SOLVED

#4 2023-12-31 16:54:17

Re: Did update - Evolution will not start SOLVED

#5 2023-12-31 23:09:57

Re: Did update - Evolution will not start SOLVED

#6 2023-12-31 23:11:44

Re: Did update - Evolution will not start SOLVED

#7 2023-12-31 23:35:50

Re: Did update - Evolution will not start SOLVED

#8 2023-12-31 23:40:39

Re: Did update - Evolution will not start SOLVED

#9 2024-01-01 00:02:30

Re: Did update - Evolution will not start SOLVED

#10 2024-01-01 00:33:55

Re: Did update - Evolution will not start SOLVED

#11 2024-01-01 04:35:56

Re: Did update - Evolution will not start SOLVED

#12 2024-01-01 09:42:12

Re: Did update - Evolution will not start SOLVED

Board footer