Arch Linux User Repository

目前通过删除 linuxqq 包自带的 libvips 临时解决了浏览图片时崩溃的问题 PS：感谢 @ayatale 的建议

新的PKGBUILD仍然会崩溃

登陆之后，打开任何一个聊天窗口都会闪退。 错误如下：

[BuglyService.cpp][handleSignal][386]Record map file of thread: 58028
[BuglyService.cpp][handleSignal][396]Dumping of native stack finished.
 235,0001,Record EupInfo
 235,0002,EupInfo has been recorded.
 235,0003,Record native key-value list.
 235,0004,Native key-value list has been recorded.
 235,0005,Record native log.
 235,0000,Native log has not been initiated.
 235,0006,Native log has been recorded.
[BuglyService.cpp][clearEupInfo][283]Clear eupInfo object.
 235,0005,Try to unlock file: /home/stone/.config/QQ/crash_files//../files/native_record_lock
 235,0006,Successfully unlock file: /home/stone/.config/QQ/crash_files//../files/native_record_lock
[BuglyService.cpp][handleSignal][441]Restored signal handlers.

登录QQ 几秒钟后会闪退 但是如果一直不登录得话不会闪退 使用 AppImage 版本的也没有问题

在经过下列步骤后不在崩溃 我不确定是受哪一步的影响

• 下载 AppImage 版本的linuxqq
• 手动安装libvips
• 重启电脑

原问题

这是我的系统信息

NAME="Arch Linux"
PRETTY_NAME="Arch Linux"
ID=arch
BUILD_ID=rolling
ANSI_COLOR="38;2;23;147;209"
HOME_URL="https://archlinux.org/"
DOCUMENTATION_URL="https://wiki.archlinux.org/"
SUPPORT_URL="https://bbs.archlinux.org/"
BUG_REPORT_URL="https://bugs.archlinux.org/"
PRIVACY_POLICY_URL="https://terms.archlinux.org/docs/privacy-policy/"
LOGO=archlinux-logo

这是我的包版本

[situ@wanqq ~]$ pacman -Qs linuxqq
local/linuxqq 2:3.1.0_9572-2
    New Linux QQ based on Electron

这是最后几行的输出

[BuglyService.cpp][handleSignal][382]Stack is succesfully dumped by libUnwind.
[BuglyService.cpp][handleSignal][384]Native stack: 
$$00    pc 0000000000112ea2    /opt/QQ/resources/app/libbugly.so (curl_multi_add_handle+562) [x86_64:testbuildnum:cbed2e9007d63af3186a3beccd076df1]
$$01    pc 000000000002518d    /usr/lib/libcurl.so.4.8.0 (curl_easy_perform+141) [x86_64::d451f4cb61f720129b73327c9ffd8142]
$$02    pc 00000000000d325a    /opt/QQ/resources/app/libbugly.so (_ZN10UploadTask10UploadImplERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEERKSt3mapIS5_S5_St4lessIS5_ESaISt4pairIS6_S5_EEEPKcjRS5_Rl+1722) [x86_64:testbuildnum:cbed2e9007d63af3186a3beccd076df1]
$$03    pc 00000000000d5dfa    /opt/QQ/resources/app/libbugly.so (_ZN10UploadTask11uploadInnerEv+3018) [x86_64:testbuildnum:cbed2e9007d63af3186a3beccd076df1]
$$04    pc 00000000000cf5b6    /opt/QQ/resources/app/libbugly.so (_ZN13UploadManager16uploadTaskRunnerEiiSt6vectorIcSaIcEENSt7__cxx1112basic_stringIcSt11char_traitsIcES1_EES7_St10shared_ptrI14UploadListenerElb+1062) [x86_64:testbuildnum:cbed2e9007d63af3186a3beccd076df1]
$$05    pc 00000000000cfb36    /opt/QQ/resources/app/libbugly.so (_ZN13UploadManager18postSyncUploadTaskEiiSt6vectorIcSaIcEENSt7__cxx1112basic_stringIcSt11char_traitsIcES1_EES7_St10shared_ptrI14UploadListenerElb+518) [x86_64:testbuildnum:cbed2e9007d63af3186a3beccd076df1]
$$06    pc 00000000000e7940    /opt/QQ/resources/app/libbugly.so (_ZN5Bugly18NativeCrashHandler16uploadCrashEventEv+2720) [x86_64:testbuildnum:cbed2e9007d63af3186a3beccd076df1]
$$07    pc 00000000001f3109    /opt/QQ/resources/app/libcrbase.so (_ZN4base13TaskAnnotator7RunTaskEPKcPNS_11PendingTaskE+201) [x86_64::503817fb0ff8bbf55e38d8a08ca7bb25]
$$08    pc 000000000020619d    /opt/QQ/resources/app/libcrbase.so (_ZN4base16sequence_manager8internal35ThreadControllerWithMessagePumpImpl10DoWorkImplEPNS0_7LazyNowE+141) [x86_64::503817fb0ff8bbf55e38d8a08ca7bb25]
$$09    pc 00000000002062bc    /opt/QQ/resources/app/libcrbase.so (_ZN4base16sequence_manager8internal35ThreadControllerWithMessagePumpImpl6DoWorkEv+76) [x86_64::503817fb0ff8bbf55e38d8a08ca7bb25]
$$10    pc 000000000019af16    /opt/QQ/resources/app/libcrbase.so (_ZN4base18MessagePumpDefault3RunEPNS_11MessagePump8DelegateE+70) [x86_64::503817fb0ff8bbf55e38d8a08ca7bb25]
$$11    pc 0000000000205ba5    /opt/QQ/resources/app/libcrbase.so (_ZThn16_N4base16sequence_manager8internal35ThreadControllerWithMessagePumpImpl3RunEbNS_9TimeDeltaE+149) [x86_64::503817fb0ff8bbf55e38d8a08ca7bb25]
$$12    pc 00000000001cf730    /opt/QQ/resources/app/libcrbase.so (_ZN4base7RunLoop3RunEv+560) [x86_64::503817fb0ff8bbf55e38d8a08ca7bb25]
$$13    pc 000000000022aeb3    /opt/QQ/resources/app/libcrbase.so (_ZN4base6Thread10ThreadMainEv+627) [x86_64::503817fb0ff8bbf55e38d8a08ca7bb25]
$$14    pc 00000000002550bb    /opt/QQ/resources/app/libcrbase.so [x86_64::503817fb0ff8bbf55e38d8a08ca7bb25]
$$15    pc 0000000000085bb5    /usr/lib/libc.so.6 [x86_64::95a1804443e852958fe59ed461135ce9]
$$16    pc 0000000000107d90    /usr/lib/libc.so.6 [x86_64::95a1804443e852958fe59ed461135ce9]

[BuglyService.cpp][handleSignal][386]Record map file of thread: 6394
[BuglyService.cpp][handleSignal][396]Dumping of native stack finished.
 235,0001,Record EupInfo
 235,0002,EupInfo has been recorded.
 235,0003,Record native key-value list.
 235,0004,Native key-value list has been recorded.
 235,0005,Record native log.
 235,0000,Native log has not been initiated.
 235,0006,Native log has been recorded.
[BuglyService.cpp][clearEupInfo][283]Clear eupInfo object.
 235,0005,Try to unlock file: /home/situ/.config/QQ/crash_files//../files/native_record_lock
 235,0006,Successfully unlock file: /home/situ/.config/QQ/crash_files//../files/native_record_lock
[BuglyService.cpp][handleSignal][441]Restored signal handlers.

目前通过删除 linuxqq 包自带的 libvips 临时解决了浏览图片时崩溃的问题 PS：感谢 @ayatale 的建议

@ayatale 谢谢，我待会儿改一下 PKGBUILD

@bczhc 我用的霞鹜文楷，好像显示没啥问题 https://i.imgur.com/XmVjCU1.png

sudo pacman -Sy libvips
sudo rm /opt/QQ/resources/app/sharp-lib/libvips-cpp.so.42

这样就不会卡死或崩溃了，用了一会暂时不知道有无别的问题

如果更新 glib2 后发现 Linux QQ 不定时崩溃，请降级 glib2：https://archive.archlinux.org/packages/g/glib2/glib2-2.74.6-1-x86_64.pkg.tar.zst

@Integral 装了，这个问题只有这个linuxqq中有，其他地方正常。

https://i.imgur.com/cITUn6P.png

@bczhc Noto Sans CJK 装了吗？