Re: GIMP Crash
Ryan Young writes: > Here is the bug info > > ``` > GNU Image Manipulation Program version 2.10.8 In that case, if you are in Debian, you would be send bug report. So that the maintainer can be know what problem is. https://www.debian.org/Bugs/Reporting Actually, you must add contain keywords "Package" and "Version" ;;; Sincerely, Byung-Hee -- ^고맙습니다 _白衣從軍_ 감사합니다_^))//
Re: Gimp crash on screenshot debian bullseye
Opened https://gitlab.gnome.org/GNOME/gimp/issues/3955 bug report upstream Renato Gallo System Engineer sede legale e operativa: Via Privata Cefalonia, 14 - 20156 - Milano (MI) Tel. +39 02 - 87049490 Fax +39 02 - 48677349 Mobile. +39 342 - 6350524 Wi | FreeNumbers: https://freenumbers.way-interactive.com Wi | SMS: https://sms.way-interactive.com Wi | Voip: https://voip.way-interactive.com Asterweb: http://www.asterweb.org Le informazioni contenute in questo messaggio e negli eventuali allegati sono riservate e per uso esclusivo del destinatario. Persone diverse dallo stesso non possono copiare o distribuire il messaggio a terzi. Chiunque riceva questo messaggio per errore è pregato di distruggerlo e di informare immediatamente [ mailto:i...@sigmaware.it | info@ ] asterweb.org - Original Message - From: "Cindy Sue Causey" To: "debian-user" Sent: Wednesday, September 18, 2019 8:26:06 PM Subject: Re: Gimp crash on screenshot debian bullseye UPDATE: Bullseye's *GIMP upgrade now WORKS (for me)!* On 9/18/19, Cindy Sue Causey wrote: > On 9/18/19, Renato Gallo wrote: >> GIMP crash on taking a screenshot > > > Hey, Renato.. I myself tuned out as soon as I saw the word "Kali" the > other day. Didn't realize it was about GIMP.. so YEAH, ME, TOO! DEBIAN > Bullseye upgrade a couple days ago. What didn't click in mind for the first response I posted was that we were possibly both talking about PNG files. My copy failed while trying to click open then edit some Xfce4 printscreen PNG files by right clicking from within Thunar file manager. > PS *VERY COOL* how they do what they do there. I think I took a > printscreen to share in places such as here at Debian-User as an > example for others to potentially pursue in their own projects. > > Did you file a bug report? How they present that crash information > made it look SUPER easy to follow up by reaching out to them directly. > > Me? I, u.. purged mine before pursuing. I was going to try to > regress. Never got the whoosie-what's-it terminal command correct to > step back down to a functional package that I NEED DESPERATELY. So the purging the other day meant I had to reinstall SOMETHING in order to possibly help test why GIMP's upgrade failed. I decided to reinstall the upgrade so I could next gain the skill of a hopefully successful downgrade. Reinstalling the buggy upgrade triggered TWO MORE package downloads/upgrades just now: libgegl-common and libgegl-0.4-0. They must have been the problem because my copy works for PNG, JPEG, and XCF files all opened again from within Thunar. So maybe that will help you now? If not, there's still always those nice bug reporting directions that were in the COOL popup that *my* copy presented, anyway. > PPS I tripped over new apt-get skills in the process so I am SO NOT > complaining! :D > > GIMP does make it look REALLY easy to help them out if you follow > their directions (in case anyone else encounters this). *VERY COOL, > VERY COGNITIVELY FRIENDLY FEATURE!!!* Surprised the doodah out of me > when it popped up because their product has ALWAYS worked flawlessly > for the almost 2 decades I've been playing in their sandbox. > > >> GNU Image Manipulation Program version 2.10.8 >> git-describe: GIMP_2_10_6-294-ga967e8d2c2 >> C compiler: >> Using built-in specs. >> COLLECT_GCC=gcc >> COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/9/lto-wrapper >> OFFLOAD_TARGET_NAMES=nvptx-none:hsa >> OFFLOAD_TARGET_DEFAULT=1 > >> < Rest snipped for brevity > PPPS Learned something else on the fly here: Installs WILL occur even if specifically requested after apt-mark has been used to mark something on hold. That's nice to know. It was a thumbs up since I DID want to install a package while knowing that package had been deliberately placed on momentary hold... purely because we can. It was all about poking around under the Debian hood again since this upgrade fail opportunity unexpectedly presented itself. I think this may be the first package crash I've EVER experienced. Ditto on the *thumbs up* for that because my email inbox hints that time span may go back almost TEN YEARS. :) S regarding my downgrade attempt the other day: If this Debian wiki page is anywhere near correct, I keyed in the right command the other day so I don't know WHY my GIMP downgrade attempt failed: https://wiki.debian.org/RollbackUpdate I'm going to tinker around with that again just for fun and 'cause it left the taste of #FAIL in its tracks. Cindy :) -- Cindy-Sue Causey Talking Rock, Pickens County, Georgia, USA * runs with.. a fabulous new grasp of WHY we use deb-src in apt/apt-get sources *
Re: Gimp crash on screenshot debian bullseye
UPDATE: Bullseye's *GIMP upgrade now WORKS (for me)!* On 9/18/19, Cindy Sue Causey wrote: > On 9/18/19, Renato Gallo wrote: >> GIMP crash on taking a screenshot > > > Hey, Renato.. I myself tuned out as soon as I saw the word "Kali" the > other day. Didn't realize it was about GIMP.. so YEAH, ME, TOO! DEBIAN > Bullseye upgrade a couple days ago. What didn't click in mind for the first response I posted was that we were possibly both talking about PNG files. My copy failed while trying to click open then edit some Xfce4 printscreen PNG files by right clicking from within Thunar file manager. > PS *VERY COOL* how they do what they do there. I think I took a > printscreen to share in places such as here at Debian-User as an > example for others to potentially pursue in their own projects. > > Did you file a bug report? How they present that crash information > made it look SUPER easy to follow up by reaching out to them directly. > > Me? I, u.. purged mine before pursuing. I was going to try to > regress. Never got the whoosie-what's-it terminal command correct to > step back down to a functional package that I NEED DESPERATELY. So the purging the other day meant I had to reinstall SOMETHING in order to possibly help test why GIMP's upgrade failed. I decided to reinstall the upgrade so I could next gain the skill of a hopefully successful downgrade. Reinstalling the buggy upgrade triggered TWO MORE package downloads/upgrades just now: libgegl-common and libgegl-0.4-0. They must have been the problem because my copy works for PNG, JPEG, and XCF files all opened again from within Thunar. So maybe that will help you now? If not, there's still always those nice bug reporting directions that were in the COOL popup that *my* copy presented, anyway. > PPS I tripped over new apt-get skills in the process so I am SO NOT > complaining! :D > > GIMP does make it look REALLY easy to help them out if you follow > their directions (in case anyone else encounters this). *VERY COOL, > VERY COGNITIVELY FRIENDLY FEATURE!!!* Surprised the doodah out of me > when it popped up because their product has ALWAYS worked flawlessly > for the almost 2 decades I've been playing in their sandbox. > > >> GNU Image Manipulation Program version 2.10.8 >> git-describe: GIMP_2_10_6-294-ga967e8d2c2 >> C compiler: >> Using built-in specs. >> COLLECT_GCC=gcc >> COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/9/lto-wrapper >> OFFLOAD_TARGET_NAMES=nvptx-none:hsa >> OFFLOAD_TARGET_DEFAULT=1 > >> < Rest snipped for brevity > PPPS Learned something else on the fly here: Installs WILL occur even if specifically requested after apt-mark has been used to mark something on hold. That's nice to know. It was a thumbs up since I DID want to install a package while knowing that package had been deliberately placed on momentary hold... purely because we can. It was all about poking around under the Debian hood again since this upgrade fail opportunity unexpectedly presented itself. I think this may be the first package crash I've EVER experienced. Ditto on the *thumbs up* for that because my email inbox hints that time span may go back almost TEN YEARS. :) S regarding my downgrade attempt the other day: If this Debian wiki page is anywhere near correct, I keyed in the right command the other day so I don't know WHY my GIMP downgrade attempt failed: https://wiki.debian.org/RollbackUpdate I'm going to tinker around with that again just for fun and 'cause it left the taste of #FAIL in its tracks. Cindy :) -- Cindy-Sue Causey Talking Rock, Pickens County, Georgia, USA * runs with.. a fabulous new grasp of WHY we use deb-src in apt/apt-get sources *
Re: Gimp crash on screenshot debian bullseye
On 9/18/19, Renato Gallo wrote: > GIMP crash on taking a screenshot Hey, Renato.. I myself tuned out as soon as I saw the word "Kali" the other day. Didn't realize it was about GIMP.. so YEAH, ME, TOO! DEBIAN Bullseye upgrade a couple days ago. PS *VERY COOL* how they do what they do there. I think I took a printscreen to share in places such as here at Debian-User as an example for others to potentially pursue in their own projects. Did you file a bug report? How they present that crash information made it look SUPER easy to follow up by reaching out to them directly. Me? I, u.. purged mine before pursuing. I was going to try to regress. Never got the whoosie-what's-it terminal command correct to step back down to a functional package that I NEED DESPERATELY. PPS I tripped over new apt-get skills in the process so I am SO NOT complaining! :D GIMP does make it look REALLY easy to help them out if you follow their directions (in case anyone else encounters this). *VERY COOL, VERY COGNITIVELY FRIENDLY FEATURE!!!* Surprised the doodah out of me when it popped up because their product has ALWAYS worked flawlessly for the almost 2 decades I've been playing in their sandbox. > GNU Image Manipulation Program version 2.10.8 > git-describe: GIMP_2_10_6-294-ga967e8d2c2 > C compiler: > Using built-in specs. > COLLECT_GCC=gcc > COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/9/lto-wrapper > OFFLOAD_TARGET_NAMES=nvptx-none:hsa > OFFLOAD_TARGET_DEFAULT=1 > < Rest snipped for brevity > Cindy :) -- Cindy-Sue Causey Talking Rock, Pickens County, Georgia, USA * runs with.. a fabulous new grasp of WHY we use deb-src in apt/apt-get sources *
Re: Gimp crash on Open File | Kali Linux XFCE
Quoting MMIROJV (2019-09-18 13:55:04) > [lots of debug noise but no question or other comment] Hi MMIROJV, Please report bugs in Kali Linux to the developers of Kali Linux. This is a Debian user mailinglist - feel free to share _user_ experiences with other users here. That inlcudes experiences using Debian in the derived form as redistributed by Kali Linux, but in that case please beware that you are targeting a wider audience, so please mention explicitly - in context, not only in subject - that you don't use regular Debian. Regards, - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature
Re: Gimp crash on Open File | Kali Linux XFCE
GIMP crash on taking a screenshot ``` GNU Image Manipulation Program version 2.10.8 git-describe: GIMP_2_10_6-294-ga967e8d2c2 C compiler: Using built-in specs. COLLECT_GCC=gcc COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/9/lto-wrapper OFFLOAD_TARGET_NAMES=nvptx-none:hsa OFFLOAD_TARGET_DEFAULT=1 Target: x86_64-linux-gnu Configured with: ../src/configure -v --with-pkgversion='Debian 9.2.1-6' --with-bugurl=file:///usr/share/doc/gcc-9/README.Bugs --enable-languages=c,ada,c++,go,brig,d,fortran,objc,obj-c++,gm2 --prefix=/usr --with-gcc-major-version-only --program-suffix=-9 --program-prefix=x86_64-linux-gnu- --enable-shared --enable-linker-build-id --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --libdir=/usr/lib --enable-nls --enable-bootstrap --enable-clocale=gnu --enable-libstdcxx-debug --enable-libstdcxx-time=yes --with-default-libstdcxx-abi=new --enable-gnu-unique-object --disable-vtable-verify --enable-plugin --enable-default-pie --with-system-zlib --with-target-system-zlib=auto --enable-multiarch --disable-werror --with-arch-32=i686 --with-abi=m64 --with-multilib-list=m32,m64,mx32 --enable-multilib --with-tune=generic --enable-offload-targets=nvptx-none,hsa --without-cuda-driver --enable-checking=release --build=x86_64-linux-gnu --host=x86_64-linux-gnu --target=x86_64-linux-gnu Thread model: posix gcc version 9.2.1 20190827 (Debian 9.2.1-6) using GEGL version 0.4.12 (compiled against version 0.4.14) using GLib version 2.60.6 (compiled against version 2.60.6) using GdkPixbuf version 2.38.1 (compiled against version 2.38.1) using GTK+ version 2.24.32 (compiled against version 2.24.32) using Pango version 1.42.3 (compiled against version 1.42.3) using Fontconfig version 2.13.1 (compiled against version 2.13.1) using Cairo version 1.16.0 (compiled against version 1.16.0) ``` > fatal error: Segmentation fault Stack trace: ``` # Stack traces obtained from PID 6172 - Thread 6172 # [New LWP 6173] [New LWP 6174] [New LWP 6175] [New LWP 6176] [New LWP 6177] [New LWP 6178] [New LWP 6179] [New LWP 6180] [New LWP 6181] [New LWP 6182] [New LWP 6197] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". 0x7f79a1c562cc in read () from /lib/x86_64-linux-gnu/libpthread.so.0 Id Target Id Frame * 1 Thread 0x7f799fe15e00 (LWP 6172) "gimp" 0x7f79a1c562cc in read () from /lib/x86_64-linux-gnu/libpthread.so.0 2 Thread 0x7f799eed5700 (LWP 6173) "gmain" 0x7f79a1b71edf in poll () from /lib/x86_64-linux-gnu/libc.so.6 3 Thread 0x7f799dd08700 (LWP 6174) "gdbus" 0x7f79a1b71edf in poll () from /lib/x86_64-linux-gnu/libc.so.6 4 Thread 0x7f798bfff700 (LWP 6175) "async" 0x7f79a1b77279 in syscall () from /lib/x86_64-linux-gnu/libc.so.6 5 Thread 0x7f798b7fe700 (LWP 6176) "worker" 0x7f79a1b77279 in syscall () from /lib/x86_64-linux-gnu/libc.so.6 6 Thread 0x7f798affd700 (LWP 6177) "worker" 0x7f79a1b77279 in syscall () from /lib/x86_64-linux-gnu/libc.so.6 7 Thread 0x7f798a7fc700 (LWP 6178) "worker" 0x7f79a1b77279 in syscall () from /lib/x86_64-linux-gnu/libc.so.6 8 Thread 0x7f7989ffb700 (LWP 6179) "worker" 0x7f79a1b77279 in syscall () from /lib/x86_64-linux-gnu/libc.so.6 9 Thread 0x7f79897fa700 (LWP 6180) "worker" 0x7f79a1b77279 in syscall () from /lib/x86_64-linux-gnu/libc.so.6 10 Thread 0x7f7988ff9700 (LWP 6181) "worker" 0x7f79a1b77279 in syscall () from /lib/x86_64-linux-gnu/libc.so.6 11 Thread 0x7f7973fff700 (LWP 6182) "worker" 0x7f79a1b77279 in syscall () from /lib/x86_64-linux-gnu/libc.so.6 12 Thread 0x7f79737fe700 (LWP 6197) "swap writer" 0x7f79a1b77279 in syscall () from /lib/x86_64-linux-gnu/libc.so.6 Thread 12 (Thread 0x7f79737fe700 (LWP 6197)): #0 0x7f79a1b77279 in syscall () from /lib/x86_64-linux-gnu/libc.so.6 No symbol table info available. #1 0x7f79a1e4895f in g_cond_wait () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 No symbol table info available. #2 0x7f79a22f30cd in ?? () from /usr/lib/x86_64-linux-gnu/libgegl-0.4.so.0 No symbol table info available. #3 0x7f79a1e2689d in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 No symbol table info available. #4 0x7f79a1c4cfb7 in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 No symbol table info available. #5 0x7f79a1b7c49f in clone () from /lib/x86_64-linux-gnu/libc.so.6 No symbol table info available. Thread 11 (Thread 0x7f7973fff700 (LWP 6182)): #0 0x7f79a1b77279 in syscall () from /lib/x86_64-linux-gnu/libc.so.6 No symbol table info available. #1 0x7f79a1e4895f in g_cond_wait () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 No symbol table info available. #2 0x55b3f63ced73 in ?? () No symbol table info available. #3 0x7f79a1e2689d in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 No symbol table info available. #4 0x7f79a1c4cfb7 in start_thread () from
Re: GIMP Crash
Le 17/03/2019 à 01:27, Adam Haas a écrit : > I was working with the Gnu Image Manipulation Program yesterday when a > segmentation fault occurred. Attached is the information spit out in > association with the event. Please let me know what additional > information you need from me and I will pass it along. > > - Adam Haas Hello, Can you send the content of your /etc/apt/sources.list ? Thanks.
