Bug#843845: The bug still exists in version: 3.22.3-2
Package: libgtk-3-0 Version: 3.22.3-2 Severity: normal Dear Maintainer, I just want to confirm that the bug still exists in version: 3.22.3-2.
Bug#843845: libgtk-3-0: Eclipse IDE (Oracle JDK8) crashes with libgtk-3.so.0
Package: libgtk-3-0 Version: 3.22.2-1 Severity: normal Dear Maintainer, After last upgrade at November 2, 2016, when I start Eclipse IDE, which uses Oracle JDK 1.8.0, and start use it, after several operations (like open files or start a server) the IDE crashes. Actually crashes JDK using libgtk-3.so.0 - version 3.22.2-1. I have no such crashes with previous versions of libgtk-3.so.0. Here is a piece of the log (the whole log is 250k): # # A fatal error has been detected by the Java Runtime Environment: # # SIGSEGV (0xb) at pc=0x7f761fcbfd56, pid=9969, tid=0x7f769ce98700 # # JRE version: Java(TM) SE Runtime Environment (8.0_111-b14) (build 1.8.0_111-b14) # Java VM: Java HotSpot(TM) 64-Bit Server VM (25.111-b14 mixed mode linux-amd64 compressed oops) # Problematic frame: # C [libgtk-3.so.0+0x173d56] # # Failed to write core dump. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again # # If you would like to submit a bug report, please visit: # http://bugreport.java.com/bugreport/crash.jsp # The crash happened outside the Java Virtual Machine in native code. # See problematic frame for where to report the bug. # --- T H R E A D --- Current thread (0x7f769400b000): JavaThread "main" [_thread_in_native, id=9970, stack(0x7f769cd98000,0x7f769ce99000)] siginfo: si_signo: 11 (SIGSEGV), si_code: 1 (SEGV_MAPERR), si_addr: 0x3000 Registers: RAX=0x7f769445b550, RBX=0x7f7695c36290, RCX=0x, RDX=0x3000 RSP=0x7f769ce95ae0, RBP=0x7f7696d19890, RSI=0x7f7694346f70, RDI=0x7f7695c36290 R8 =0x017d, R9 =0x0006, R10=0x, R11=0x R12=0x7f7697726640, R13=0x7f7695c36290, R14=0x, R15=0x7f769ce95b00 RIP=0x7f761fcbfd56, EFLAGS=0x00010206, CSGSFS=0x002b0033, ERR=0x0004 TRAPNO=0x000e Top of Stack: (sp=0x7f769ce95ae0) 0x7f769ce95ae0: 7f7697726470 7f761fddd4f6 0x7f769ce95af0: 00300018 9ce95bd0 0x7f769ce95b00: 017f0008 0x7f769ce95b10: 00020002 017b0004 0x7f769ce95b20: 017f0008 0x7f769ce95b30: 36805df85b98de00 0x7f769ce95b40: 7f769ce95bf0 7f7697726640 0x7f769ce95b50: 7f7697726470 7f7694357ce0 0x7f769ce95b60: 7f7697726601 7f7697726640 0x7f769ce95b70: 7f7694357fa0 7f761fddf2e2 0x7f769ce95b80: 0002 0x7f769ce95b90: 36805df85b98de00 0x7f769ce95ba0: 0018 7f7697c223f0 0x7f769ce95bb0: 7f769ce95d70 7f761fd7b651 0x7f769ce95bc0: 7f76943621b0 7f761f934568 0x7f769ce95bd0: 00300020 7f769ce95f20 0x7f769ce95be0: 7f769ce95e60 36805df85b98de00 0x7f769ce95bf0: 7f7694357ce0 0x7f769ce95c00: 7f769ce95d70 0x7f769ce95c10: 7f7697726640 7f769ce95e40 0x7f769ce95c20: 7f7694357fa0 7f76462ca1a4 0x7f769ce95c30: 7f7694357fa0 7f76462ca070 0x7f769ce95c40: 7f7697c22600 0001 0x7f769ce95c50: 7f760002 7f7645fdf119 0x7f769ce95c60: 7f764002 7f7645fdf119 0x7f769ce95c70: 7f769436b910 7f7697726640 0x7f769ce95c80: 7f769430cc70 7f7694358030 0x7f769ce95c90: 7f769ce95e30 7f769ce95d40 0x7f769ce95ca0: 7f7694357ce0 0x7f769ce95cb0: 7f7694357fc0 7f76462e4391 0x7f769ce95cc0: 7f769ce95df0 64a0 0x7f769ce95cd0: 7f7697c22600 7f769ce95d70 Instructions: (pc=0x7f761fcbfd56) 0x7f761fcbfd36: 26 05 21 00 66 0f 1f 44 00 00 53 48 89 fb e8 d7 0x7f761fcbfd46: f3 ff ff 48 85 db 74 1c 48 8b 13 48 85 d2 74 05 0x7f761fcbfd56: 48 3b 02 74 2d 48 89 c6 48 89 df e8 3a 2b f1 ff 0x7f761fcbfd66: 85 c0 75 1e 5b 48 8d 15 a6 f3 27 00 48 8d 35 97 . I upgraded JDK 1.8.0 from version 101 to 111, but there was no effect - the IDE still crashes. But it seems that downgrading libgtk-3 from version 3.22.2-1 to libgtk-3-0_3.22.1-1_amd64.deb and libgtk-3-bin_3.22.1-1_amd64.deb fixes the crash. I am using Debian Stretch, kernel 4.7.0-1-amd64, last upgrade at November 2, 2016. -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.7.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages libgtk-3-0 depends on: ii adwaita-icon-theme 3.22.0-1 ii hicolor-icon-theme 0.15-1 ii
Bug#755286: closed by Holger Levsen hol...@layer-acht.org (Re: Bug#755286: general: Black screen on resume after suspend)
Dear Holger Levsen, Did you read the submission? Or just found a reason to close the bug? Of course there is a possibility this bug to be not exactly debian. BUT the laptop had worked pretty well, including suspend and resume, for a month with Jessie system and a kernel by Ubuntu till an update of DEBIAN packages. So I am pretty sure that this is a bug of a Debian package. Do you know when Debian will release 3.15 kernel? I have been a Debian user for at least 10 years and have seen the same bug several times with several of laptops. The same situation: worked, stop worked, fixed after several months Just wanted to help. Thanks, Aleksandar On 07/21/2014 02:39 PM, Debian Bug Tracking System wrote: This is an automatic notification regarding your Bug report which was filed against the general package: #755286: general: Black screen on resume after suspend It has been closed by Holger Levsen hol...@layer-acht.org. Their explanation is attached below along with your original report. If this explanation is unsatisfactory and you have not received a better one in a separate message then please contact Holger Levsen hol...@layer-acht.org by replying to this email. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#755286: closed by Holger Levsen hol...@layer-acht.org (Re: Bug#755286: general: Black screen on resume after suspend)
On 07/21/2014 03:52 PM, intrigeri wrote: Hi, Aleksandar Nikolov wrote (21 Jul 2014 12:18:16 GMT) : BUT the laptop had worked pretty well, including suspend and resume, for a month with Jessie system and a kernel by Ubuntu till an update of DEBIAN packages. So I am pretty sure that this is a bug of a Debian package. I'm glad this *unsupported* combination of packages used to work for you. Still, it's not supported by Debian, so if it stops working, then, well, you're on your own. Sorry. Do you know when Debian will release 3.15 kernel? You might want to try the 3.15 kernel from Debian experimental. Cheers, Hi I must report the solution: Debian experimental kernels 3.15.x and 3.16.rcX both work well, supporting my video card Intel 4400 + GeForce 730M and including suspend and resume. I was wrong that this is Debian bug and want to thank everybody who referred me to the solution. Thanks again, Aleksandar -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#755286: Bug#755285: marked as done (general: Black screen on resume after suspend)
On 07/19/2014 08:49 PM, Abou Al Montacir wrote: Control: reopen -1 On Sat, 2014-07-19 at 17:03 +, Debian Bug Tracking System wrote: ... Missing information, dupe. Kind regards, Andrei Hi Andrei, I don't think that missing information is enough argument to close a bug. Hi AL Nik, Can you please provide more information about your issue. As the screen is dead I understand that you may have issue to provide the required information depending on your computer skills. Please find below some hints, and maybe Andrei can provide more hints instead of closing this bug again ;) If you have access to another computer, please consider logging into the first one after resume (you need to have sshd installed or any other deamon for remote access) then gain root access and provide output of dmesg and other log files in /var/log like /var/log/pm-powersave.log. I'm not a specialist of such issues, but don't like to have user's request closed abruptly. Cheers, Abou Al Montacir Hi Abou Al Montacir, I tried this experiment: Installed sshd and connected from another computer - it works. But after the lid closed and opened, I cannot connect. The system must be dead, although the fans blows and the power led is on. Further after restart I found that nothing was written in neither dmesg nor pm-powersave.log after the lid is closed and then opened. Best, Aleksandar -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#755286: Bug#755285: marked as done (general: Black screen on resume after suspend)
On 07/20/2014 04:25 PM, Abou Al Montacir wrote: On Sun, 2014-07-20 at 13:10 +0300, Aleksandar Nikolov wrote: I tried this experiment: Installed sshd and connected from another computer - it works. But after the lid closed and opened, I cannot connect. The system must be dead, although the fans blows and the power led is on. This means that your system hanged either during going into sleep mode or when exiting the sleep mode. This is then not a screen issue but a system issue. The fact that fans are on may indicate that the issue happened when exiting suspend mode. But we definitely need more information. Further after restart I found that nothing was written in neither dmesg dmesg does not remember messages from old boot, you need to relay on logs nor pm-powersave.log after the lid is closed and then opened. yes this is normal as you rebooted. Then this file will be filled for the next time but you won't be able to recover it. Normally you should find a /var/log/pm-*.log.1, these files are the ones you need to provide. I marked both dmesg and pm-powersave.log by adding a specific line at the bottom and I am pretty sure that nothing is appended to them or to the renamed ones after lid closed and lid opened. Of course after restart the old files was renamed but my marks was still at the bottom of the old files. Also it could be better if you try using the official Debian kernel, at least while we are investigating the issue. I assume you have good reason to use an other kernel, but we do not support such combinations, so please ensure investigating this bug with: (jessie)root@karim:~# aptitude show linux-image-amd64 Package: linux-image-amd64 State: not installed Version: 3.14+58 Priority: optional Section: kernel Maintainer: Debian Kernel Team debian-ker...@lists.debian.org Architecture: i386 Uncompressed Size: 38.9 k Depends: linux-image-3.14-1-amd64 Provides: linux-latest-modules-3.14-1-amd64 Description: Linux for 64-bit PCs (meta-package) This package depends on the latest Linux kernel and modules for use on PCs with AMD64, Intel 64 or VIA Nano processors. This kernel also runs on a Xen hypervisor. It supports both privileged (dom0) and unprivileged (domU) operation. I DO prefer using standard official kernel, but 3.14 doesn't support my video card - shows a black screen after grub. Thats why I installed 3.15 and 3.16. And all the thing had worked well till update at 07.07. Cheers, Abou Al Montacir Best regards, Aleksandar -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
