Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#69642 - [gitlab-shell] sigsegv
Attached to Project:
Community Packages
Opened by Sergej Pupykin (sergej) - Sunday, 14 February 2021, 22:02 GMT
Last edited by Toolybird (Toolybird) - Friday, 28 April 2023, 21:57 GMT
Opened by Sergej Pupykin (sergej) - Sunday, 14 February 2021, 22:02 GMT
Last edited by Toolybird (Toolybird) - Friday, 28 April 2023, 21:57 GMT
|
DetailsSteps to reproduce:
root@git .ssh]# sudo -u git -- /usr/share/webapps/gitlab-shell/bin/gitlab-shell panic: runtime error: invalid memory address or nil pointer dereference [signal SIGSEGV: segmentation violation code=0x1 addr=0x18 pc=0x55af6776a8ef] goroutine 1 [running]: gitlab.com/gitlab-org/gitlab-shell/internal/logger.Configure(0xc000214280) gitlab.com/gitlab-org/gitlab-shell/internal/logger/logger.go:26 +0x12f main.main() gitlab.com/gitlab-org/gitlab-shell/cmd/gitlab-shell/main.go:48 +0x170 [root@git .ssh]# pacman -U https://archive.archlinux.org/packages/g/gitlab-shell/gitlab-shell-2%3A13.15.0-1-x86_64.pkg.tar.zst gitlab-shell-2%3A13.15.0-1-x86_64 13.1 MiB 4.33 MiB/s 00:03 [##################################################################] 100% gitlab-shell-2%3A13.15.0-1-x86_64.sig 566.0 B 0.00 B/s 00:00 [##################################################################] 100% loading packages... warning: downgrading package gitlab-shell (2:13.16.1-1 => 2:13.15.0-1) resolving dependencies... looking for conflicting packages... Packages (1) gitlab-shell-2:13.15.0-1 Total Installed Size: 72.17 MiB Net Upgrade Size: -18.81 MiB :: Proceed with installation? [Y/n] (1/1) checking keys in keyring [##################################################################] 100% (1/1) checking package integrity [##################################################################] 100% (1/1) loading package files [##################################################################] 100% (1/1) checking for file conflicts [##################################################################] 100% (1/1) checking available disk space [##################################################################] 100% :: Processing package changes... (1/1) downgrading gitlab-shell [##################################################################] 100% If you have previously installed gitlab-shell and now git pull fails on a repo, try changing the shell: usermod -s /usr/share/webapps/gitlab-shell/bin/gitlab-shell gitlab :: Running post-transaction hooks... (1/2) Creating system user accounts... (2/2) Arming ConditionNeedsUpdate... [root@git .ssh]# sudo -u git -- /usr/share/webapps/gitlab-shell/bin/gitlab-shell Only SSH allowed |
This task depends upon
Closed by Toolybird (Toolybird)
Friday, 28 April 2023, 21:57 GMT
Reason for closing: Fixed
Additional comments about closing: See comments
Friday, 28 April 2023, 21:57 GMT
Reason for closing: Fixed
Additional comments about closing: See comments
Comment by Sergej Pupykin (sergej) -
Sunday, 14 February 2021, 22:05 GMT
strange thing that it can be reproduced in lxc container, however I cannot reproduce it on another gitlab installation on physical server
Comment by Anatol Pomozov (anatolik) -
Friday, 26 February 2021, 19:54 GMT
Do you reproduce with newer version of the package? If yes then it makes sense to contact the upstream.
Comment by Sergej Pupykin (sergej) -
Friday, 30 April 2021, 00:18 GMT
gitlab-shell-2:13.17.0-1 looks working