[Bug 1810027] Re: Snaps won't start - stack smashing detected
Still not working for me on Ubuntu 16.04: $ vlc & [2] 6877 $ VLC media player 3.0.6 Vetinari (revision 3.0.6-0-g5803e85) [020713b0] main libvlc: Running vlc with the default interface. Use 'cvlc' to use vlc without interface. Qt: Session management error: None of the authentication protocols specified are supported [02106220] main playlist: playlist is empty QObject::~QObject: Timers cannot be stopped from another thread $ snap version snap2.37.2 snapd 2.37.2 series 16 ubuntu 16.04 kernel 4.4.0-142-generic $ snap list Name VersionRev Tracking Publisher Notes core 16-2.37.2 6405 stablecanonicalâś“ core vlc 3.0.6 770 stablevideolanâś“ - $ type vlc vlc is hashed (/snap/bin/vlc) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1810027 Title: Snaps won't start - stack smashing detected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1810027/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 600219] Re: faxgetty segfault
Giuseppe: Do we know that this bug is no longer present in the g++ compiler that will ship with 12.04? If that's the case, I'll just wait it out, running the un-optimized packages, until 12.04 is released. There's no point in chasing a bug that's already been squashed! Mark -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/600219 Title: faxgetty segfault To manage notifications about this bug go to: https://bugs.launchpad.net/hylafax/+bug/600219/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 600219] Re: faxgetty segfault
OK, I just installed the hylafax 6.0.5 deb packages on my Ubuntu 10.04 system, and ran "gdb-wrapper.sh faxgetty -D ttyS0" Now, my process tree shows: root@isabel:/tmp# ps auxw|grep fax uucp 3839 0.0 0.2 4820 1568 ?S17:01 0:00 /usr/sbin/hfaxd -d -i 4559 uucp 4251 0.1 0.2 4944 1956 ?S17:07 0:00 /usr/sbin/hfaxd -d -i 4559 root 4302 0.0 0.0 1832 524 pts/4S17:12 0:00 /bin/sh ./gdb-wrapper.sh faxgetty -D ttyS0 root 4303 0.4 1.2 15192 9404 pts/4S17:12 0:00 gdb -return-child-result -batch -x /tmp/gdb-4302.batch --args faxgetty -D ttyS0 uucp 4308 0.0 0.1 5240 1252 ?Ss 17:12 0:00 /usr/local/sbin/faxgetty -D ttyS0 root 4312 0.0 0.1 3320 792 pts/3S+ 17:13 0:00 grep --color=auto fax root@isabel:/tmp# Now, we wait for the next segfault to occur. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/600219 Title: faxgetty segfault To manage notifications about this bug go to: https://bugs.launchpad.net/hylafax/+bug/600219/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 600219] Re: faxgetty segfault
Giuseppe: I'm not in my office today, but if I have time tomorrow I'll install the new packages and let you know if anything has changed. It may take a week or more to determine if the segfaults are gone. Thanks for all your effort! Mark -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/600219 Title: faxgetty segfault To manage notifications about this bug go to: https://bugs.launchpad.net/hylafax/+bug/600219/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 600219] Re: faxgetty segfault
Adding my two cents. As yaztromo says, segfaults seem to be more likely when the fax is originating from a particular sender. However, for me, when the "problem sender" would try to re-send the same fax, it could segfault in a different place each time. This would suggest that it is nothing in the data stream itself that triggers the error, but something in the control signals being exchanged perhaps? The people in the sending office told me that they have "a lot of problems with that machine (a Konica/Minolta 2900)", but I don't know exactly what that means. What office worker doesn't like to complain about their equipment? I looked up the brochure for the 2900, and it looks like a quality device, and not that old. Perhaps the control/status signals are causing an unexpected condition, or triggering the execution of badly-optimized code that clobbers the "this" pointer? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/600219 Title: faxgetty segfault To manage notifications about this bug go to: https://bugs.launchpad.net/hylafax/+bug/600219/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 600219] Re: faxgetty segfault
Giuseppe: Just to confirm, I am coming up on one week since installing the "-O" compiled packages with no segfaults so far. Could this bug be depending on the CPU type? My system is also an AMD processor, but a more recent one. (Athlon, maybe?) Anyway, I'm hoping I've seen my last segfault. Mark -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/600219 Title: faxgetty segfault To manage notifications about this bug go to: https://bugs.launchpad.net/hylafax/+bug/600219/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
