页次: 1
qq版本:linuxqq_3.1.0-9572_x86_64.AppImage
日志信息:
[BuglyService.cpp][handleSignal][382]Stack is succesfully dumped by libUnwind.
[BuglyService.cpp][handleSignal][384]Native stack:
$$00 pc 0000000000c5bcff /tmp/.mount_linuxqI0CUFn/resources/app/sharp-lib/libvips-cpp.so.42 (g_type_check_instance_is_fundamentally_a+16) [x86_64::5bab1f582ff5846e6cfc1a0d80955e1e]
[BuglyService.cpp][handleSignal][386]Record map file of thread: 20403
[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/zhanguichen/.config/QQ/crash_files//../files/native_record_lock
235,0006,Successfully unlock file: /home/zhanguichen/.config/QQ/crash_files//../files/native_record_lock
[BuglyService.cpp][handleSignal][441]Restored signal handlers.
暂时找不到解决方法,来论坛请教一下大家
离线
glib 更新了导致自带的 libvips崩了,解决办法就是降级 glib或者别用 appimage. 用 aur的 linuxqq, 那个已经修复了.用bwrap版的话,删掉qq自己带的 resources/app/sharp-lib/libvips-cpp.so.42
离线
glib 更新了导致自带的 libvips崩了,解决办法就是降级 glib或者别用 appimage. 用 aur的 linuxqq, 那个已经修复了.用bwrap版的话,删掉qq自己带的 resources/app/sharp-lib/libvips-cpp.so.42
谢谢大佬,确实重装了就解决了
离线
glib 更新了导致自带的 libvips崩了,解决办法就是降级 glib或者别用 appimage. 用 aur的 linuxqq, 那个已经修复了.用bwrap版的话,删掉qq自己带的 resources/app/sharp-lib/libvips-cpp.so.42
大佬你好,我装的是AUR的linuxqq,在登录之后过了几十秒也会闪退,日志信息如下。
刚运行linuxqq时,日志有错误信息的标准输出:
(process:5364): VIPS-WARNING **: 10:03:28.935: unable to load "/usr/lib/vips-modules-8.14/vips-magick.so" -- libMagickCore-7.Q16HDRI.so.10: 无法打开共享对象文件: 没有那个文件或目录
(process:5364): GModule-CRITICAL **: 10:03:28.935: g_module_make_resident: assertion 'module != NULL' failed
(process:5364): VIPS-WARNING **: 10:03:28.937: unable to load "/usr/lib/vips-modules-8.14/vips-openslide.so" -- libopenslide.so.0: 无法打开共享对象文件: 没有那个文件或目录
(process:5364): GModule-CRITICAL **: 10:03:28.937: g_module_make_resident: assertion 'module != NULL' failed
Gtk-Message: 10:03:28.976: Failed to load module "appmenu-gtk-module"
libva error: vaGetDriverNameByIndex() failed with unknown libva error, driver_name = (null)
登录之后一段时间的日志有一大堆标准输出,最后的堆栈输出:
[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 000000000002502d /usr/lib/libcurl.so.4.8.0 (curl_easy_perform+141) [x86_64::e8163b1aecf5658a6f09adceef0d03de]
$$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: 6075
[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/csu_cangkui/.config/QQ/crash_files//../files/native_record_lock
235,0006,Successfully unlock file: /home/csu_cangkui/.config/QQ/crash_files//../files/native_record_lock
[BuglyService.cpp][handleSignal][441]Restored signal handlers.
请问这个也是因为glib导致的吗?解决方案是否同样需要降级glib?个人认为libvips应该也是出了问题的,原因不确定。
离线
glib 更新了导致自带的 libvips崩了,解决办法就是降级 glib或者别用 appimage. 用 aur的 linuxqq, 那个已经修复了.用bwrap版的话,删掉qq自己带的 resources/app/sharp-lib/libvips-cpp.so.42
我的linuxqq就是直接从AUR里面装的,aur/linuxqq 2:3.1.0_9572-2 (+51 10.52)
离线
sukanka 说:glib 更新了导致自带的 libvips崩了,解决办法就是降级 glib或者别用 appimage. 用 aur的 linuxqq, 那个已经修复了.用bwrap版的话,删掉qq自己带的 resources/app/sharp-lib/libvips-cpp.so.42
我的linuxqq就是直接从AUR里面装的,aur/linuxqq 2:3.1.0_9572-2 (+51 10.52)
你应该用过QQ自带的更新,请删除 `~/.config/QQ` 下面的热更新文件,重启QQ,另外记得关闭 QQ自己的更新。
离线
csu_cangkui 说:sukanka 说:glib 更新了导致自带的 libvips崩了,解决办法就是降级 glib或者别用 appimage. 用 aur的 linuxqq, 那个已经修复了.用bwrap版的话,删掉qq自己带的 resources/app/sharp-lib/libvips-cpp.so.42
我的linuxqq就是直接从AUR里面装的,aur/linuxqq 2:3.1.0_9572-2 (+51 10.52)
你应该用过QQ自带的更新,请删除 `~/.config/QQ` 下面的热更新文件,重启QQ,另外记得关闭 QQ自己的更新。
QQ自带的检测更新目前是关闭的。请问热更新涉及~/.config/QQ目录下面的哪些文件?是Cache目录吗?
离线
请问热更新涉及~/.config/QQ目录下面的哪些文件?是Cache目录吗?
我不知道,如果你不想去找的话,可以删除整个 `~/.config/QQ` 文件夹
离线
csu_cangkui 说:sukanka 说:glib 更新了导致自带的 libvips崩了,解决办法就是降级 glib或者别用 appimage. 用 aur的 linuxqq, 那个已经修复了.用bwrap版的话,删掉qq自己带的 resources/app/sharp-lib/libvips-cpp.so.42
我的linuxqq就是直接从AUR里面装的,aur/linuxqq 2:3.1.0_9572-2 (+51 10.52)
你应该用过QQ自带的更新,请删除 `~/.config/QQ` 下面的热更新文件,重启QQ,另外记得关闭 QQ自己的更新。
有个很难受的点,就是这版本QQ的设置是在登陆后才可以修改的,但登陆完进去默认热更新是开启的,每次等我更改完应该是已经更新完毕了。所以虽然我清空`~/.config/QQ`后能用,但下次开机后就又不行了。
离线
csu_cangkui 说:请问热更新涉及~/.config/QQ目录下面的哪些文件?是Cache目录吗?
我不知道,如果你不想去找的话,可以删除整个 `~/.config/QQ` 文件夹
3Q, 解决了
离线
找了好久,解决了
离线
页次: 1