[Bug 1683151] Re: gqrx-sdr segfault during startup due to invalid thread support
I have 17.10 and I do not see the bug. For 17.04 I had to recompile gr- osmosdr (libgnuradio-osmosdr) to avoid crash, for 17.10 I run the packaged version. A terminaldump and ldd results below: mjacek@mjacek-u1710:~$ gqrx linux; GNU C++ version 6.2.0 20161027; Boost_106200; UHD_003.009.005-0-unknown gr-osmosdr 0.1.4 (0.1.4) gnuradio 3.7.10 built-in source types: file osmosdr fcd rtl rtl_tcp uhd miri hackrf bladerf rfspace airspy soapy redpitaya FM demod gain: 1.52789 IQ DCR alpha: 1.04166e-05 Using audio backend: auto BookmarksFile is /home/mjacek/.config/gqrx/bookmarks.csv gr-osmosdr 0.1.4 (0.1.4) gnuradio 3.7.10 built-in source types: file osmosdr fcd rtl rtl_tcp uhd miri hackrf bladerf rfspace airspy soapy redpitaya Using device #0 Realtek RTL2838UHIDIR SN: 0001 ... mjacek@mjacek-u1710:~$ ldd `which gqrx` linux-vdso.so.1 => (0x7fffdb5a2000) libQt5Network.so.5 => /usr/lib/x86_64-linux-gnu/libQt5Network.so.5 (0x7fa79307) libboost_system.so.1.62.0 => /usr/lib/x86_64-linux-gnu/libboost_system.so.1.62.0 (0x7fa792e6c000) libboost_program_options.so.1.62.0 => /usr/lib/x86_64-linux-gnu/libboost_program_options.so.1.62.0 (0x7fa792bef000) libgnuradio-runtime.so.3.7.10 => /usr/lib/x86_64-linux-gnu/libgnuradio-runtime.so.3.7.10 (0x7fa792906000) libgnuradio-pmt.so.3.7.10 => /usr/lib/x86_64-linux-gnu/libgnuradio-pmt.so.3.7.10 (0x7fa7926b1000) libgnuradio-analog.so.3.7.10 => /usr/lib/x86_64-linux-gnu/libgnuradio-analog.so.3.7.10 (0x7fa79242) libgnuradio-blocks.so.3.7.10 => /usr/lib/x86_64-linux-gnu/libgnuradio-blocks.so.3.7.10 (0x7fa791f5f000) libgnuradio-digital.so.3.7.10 => /usr/lib/x86_64-linux-gnu/libgnuradio-digital.so.3.7.10 (0x7fa791c23000) libgnuradio-fft.so.3.7.10 => /usr/lib/x86_64-linux-gnu/libgnuradio-fft.so.3.7.10 (0x7fa7919f4000) libgnuradio-filter.so.3.7.10 => /usr/lib/x86_64-linux-gnu/libgnuradio-filter.so.3.7.10 (0x7fa79171b000) libgnuradio-osmosdr.so.0.1.4 => /usr/lib/x86_64-linux-gnu/libgnuradio-osmosdr.so.0.1.4 (0x7fa79142b000) libpulse.so.0 => /usr/lib/x86_64-linux-gnu/libpulse.so.0 (0x7fa7911db000) libpulse-simple.so.0 => /usr/lib/x86_64-linux-gnu/libpulse-simple.so.0 (0x7fa790fd6000) libQt5Widgets.so.5 => /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 (0x7fa790792000) libQt5Gui.so.5 => /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5 (0x7fa79002b000) libQt5Core.so.5 => /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 (0x7fa78f8e2000) libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6 (0x7fa78f55c000) libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x7fa78f206000) libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 (0x7fa78efef000) libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7fa78ec0f000) libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x7fa78e9f) libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x7fa78e7d3000) libvolk.so.1.3 => /usr/lib/x86_64-linux-gnu/libvolk.so.1.3 (0x7fa78e46b000) libboost_filesystem.so.1.62.0 => /usr/lib/x86_64-linux-gnu/libboost_filesystem.so.1.62.0 (0x7fa78e252000) libboost_thread.so.1.62.0 => /usr/lib/x86_64-linux-gnu/libboost_thread.so.1.62.0 (0x7fa78e02b000) liblog4cpp.so.5 => /usr/lib/x86_64-linux-gnu/liblog4cpp.so.5 (0x7fa78ddee000) librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x7fa78dbe6000) /lib64/ld-linux-x86-64.so.2 (0x7fa7938a3000) libfftw3f.so.3 => /usr/lib/x86_64-linux-gnu/libfftw3f.so.3 (0x7fa78d7e3000) libfftw3f_threads.so.3 => /usr/lib/x86_64-linux-gnu/libfftw3f_threads.so.3 (0x7fa78d5dc000) libgnuradio-iqbalance.so.0 => /usr/lib/x86_64-linux-gnu/libgnuradio-iqbalance.so.0 (0x7fa78d3ca000) libosmosdr.so.0 => /usr/lib/x86_64-linux-gnu/libosmosdr.so.0 (0x7fa78d1c5000) libgnuradio-fcd.so.3.7.10 => /usr/lib/x86_64-linux-gnu/libgnuradio-fcd.so.3.7.10 (0x7fa78cfac000) libgnuradio-fcdproplus.so.3.7.10 => /usr/lib/x86_64-linux-gnu/libgnuradio-fcdproplus.so.3.7.10 (0x7fa78cd98000) librtlsdr.so.0 => /usr/lib/x86_64-linux-gnu/librtlsdr.so.0 (0x7fa78cb89000) libgnuradio-uhd.so.3.7.10 => /usr/lib/x86_64-linux-gnu/libgnuradio-uhd.so.3.7.10 (0x7fa78c93c000) libuhd.so.003 => /usr/lib/x86_64-linux-gnu/libuhd.so.003 (0x7fa78c01f000) libmirisdr.so.0 => /usr/lib/x86_64-linux-gnu/libmirisdr.so.0 (0x7fa78be1a000) libhackrf.so.0 => /usr/lib/x86_64-linux-gnu/libhackrf.so.0 (0x7fa78bc14000) libbladeRF.so.1 => /usr/lib/x86_64-linux-gnu/libbladeRF.so.1 (0x7fa78b9e) libairspy.so.0 => /usr/lib/x86_64-linux-gnu/libairspy.so.0 (0x7fa78b7d9000) libSoapySDR.so.0.6 =>
[Bug 1685778] Re: PDFChain Segmentation Fault error on start, Ubuntu 17.04
Maybe it helps: Reading symbols from /usr/bin/pdfchain...(no debugging symbols found)...done. (gdb) run Starting program: /usr/bin/pdfchain [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [New Thread 0x7fffea2ee700 (LWP 14109)] [New Thread 0x7fffe9aed700 (LWP 14110)] [New Thread 0x7fffe8ead700 (LWP 14111)] PDF Chain 0.4.4.2 - A graphical user interface for the PDF Toolkit [New Thread 0x7fffdb5a2700 (LWP 14113)] [New Thread 0x7fffdada1700 (LWP 14114)] [New Thread 0x7fffd95e8700 (LWP 14115)] [New Thread 0x7fffd88f9700 (LWP 14117)] [New Thread 0x7fffd2582700 (LWP 14118)] [New Thread 0x7fffd1d81700 (LWP 14119)] Thread 1 "pdfchain" received signal SIGSEGV, Segmentation fault. 0x74adb360 in g_slist_find () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 (gdb) info stack #0 0x74adb360 in g_slist_find () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x75575a5b in gtk_radio_button_set_group () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 #2 0x779e3552 in Gtk::RadioButton::set_group(Gtk::RadioButtonGroup&) () from /usr/lib/x86_64-linux-gnu/libgtkmm-3.0.so.1 #3 0x77a60447 in Gtk::RadioButtonGroup::add(Gtk::RadioButton&) () from /usr/lib/x86_64-linux-gnu/libgtkmm-3.0.so.1 #4 0x779e306a in Gtk::RadioButton::RadioButton(Gtk::RadioButtonGroup&, Glib::ustring const&, bool) () from /usr/lib/x86_64-linux-gnu/libgtkmm-3.0.so.1 #5 0x555f86a2 in ?? () #6 0x5560bcc1 in ?? () #7 0x5560dd3a in ?? () #8 0x555d492a in ?? () #9 0x7606e3f1 in __libc_start_main (main=0x555d4880, argc=1, argv=0x7fffdf18, init=, fini=, rtld_fini=, stack_end=0x7fffdf08) at ../csu/libc-start.c:291 #10 0x555d49ba in ?? () (gdb) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1685778 Title: PDFChain Segmentation Fault error on start, Ubuntu 17.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pdfchain/+bug/1685778/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1682499] Re: disable dnssec
This helped me only partially - I still have issues with DNS lookup. It seems that the systemd-resolved is broken from the very idea. After solving DNSSEC problem, I see now a switching problem - if one DNS does not respond, resolved switches to another one, which may be a local DNS not serving all the information, however it responds RELIABLY with "REFUSED" for majority of queries! Thus, resolved is stuck with this "reliable" DNS, refusing almost all queries until reboot (or networking reload). There are so many bugs filled about resolved that somebody should gather them in one place and do something. Moreover, tracing problems is not easy - they are intermittent, depending on current server load. For some people in fixed setup bug may be nonexistent; when travelling across well-configured, simple and non- overloaded networks everything is OK. Then, at some hour, some connection - I start having to reload network every time I start reading mail. For now many people are switching to alternative resolver - e.g. "unbound"; what is going on with resolved looks like sabotage. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1682499 Title: disable dnssec To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1682499/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1654918] Re: No Internet access with default of Automatic (DHCP)
Regarding my previous post (#24)... Seems that everything is back to abnormal. After logging out and re- logging again bug was back. This time soft disconnecting and reconnecting network (from NManager) helped to regain access to network, but this was not always the remedy. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1654918 Title: No Internet access with default of Automatic (DHCP) To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1654918/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1654918] Re: No Internet access with default of Automatic (DHCP)
Ubuntu 17.04 on a Dell E6530, fresh install with copying of some networkmanager setup in /etc/ from good old Ubuntu 16.04.01 LTS and using the same home partition. My version of this bug is really miraculous. It was here for a week, today disappeared. For a week I had problems with ONE of the four locations where I connect to the net: - home-wifi (OK) - home-cable (OK) - work-cable (BAD) - work-wifi (OK). Problems only with 17.04, 16.04 working flawlessly. Problem was repeatable - nslookup working until I started firefox. Firefox showing Google home page ONCE, then all requests showing "unavailable", even reloading the home page. Also any later nslookup failing with "REFUSED". Two days ago I upgraded following to "zesty-proposed", but it did NOT help for yesterday. Maybe it needed time Upgraded the following packages: libnss-resolve (232-21ubuntu2) to 232-21ubuntu3 libpam-systemd (232-21ubuntu2) to 232-21ubuntu3 libsystemd0 (232-21ubuntu2) to 232-21ubuntu3 libsystemd0:i386 (232-21ubuntu2) to 232-21ubuntu3 libudev1 (232-21ubuntu2) to 232-21ubuntu3 systemd (232-21ubuntu2) to 232-21ubuntu3 systemd-sysv (232-21ubuntu2) to 232-21ubuntu3 udev (232-21ubuntu2) to 232-21ubuntu3 Maybe today (Sat) my work net services are less/more overloaded, so DNS query timing is different? I will see again on Mon. Anyway, strange - it seems that some timing or some combination of circumstances break the local DNS system -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1654918 Title: No Internet access with default of Automatic (DHCP) To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1654918/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1027392] Re: Apport refuses to acknowledge 'Ignore future problems of this type' when ticked
I am on 16.04.1 LTS, x86_64, apport version 2.20.1-0ubuntu2.5, and the bug is still here. I have an unresolvable problem with hp printer, appearing only when I forget to switch printer on, and I want to ignore this forever. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1027392 Title: Apport refuses to acknowledge 'Ignore future problems of this type' when ticked To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1027392/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 670796] Re: weather indicator does not wake up after suspend
Recalling my experience with this indicator, I believe the problem appears almost always when the first refresh happens with network not ready (e.g. WiFi not yet fully connected) and does not happen with cable (which is connected before I start my session). This may as well cover the case of wake-up from suspend (this time even with cable), but I rarely let my comp suspend. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/670796 Title: weather indicator does not wake up after suspend -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 783860] [NEW] minimize all does not obey non_minimizable window rule
Public bug reported: Binary package hint: unity When pressing super-D to show desktop (or by mousing upper right corner), widnows which are set as 'no-minimize-match' in compiz window rules do minimize. The same rule worked as expected in 10.10, problem emerged after upgrade. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: unity 3.8.12-0ubuntu1 ProcVersionSignature: Ubuntu 2.6.38-9.43-generic 2.6.38.4 Uname: Linux 2.6.38-9-generic x86_64 NonfreeKernelModules: nvidia Architecture: amd64 CompizPlugins: [core,bailer,detection,composite,opengl,decor,grid,imgpng,compiztoolbox,commands,gnomecompat,staticswitcher,dbus,resize,annotate,place,obs,vpswitch,unitymtgrabhandles,snap,session,mousepoll,move,regex,wall,winrules,animation,expo,workarounds,fade,scale,unityshell] Date: Tue May 17 10:20:25 2011 InstallationMedia: Ubuntu 10.04 LTS Lucid Lynx - Release amd64 (20100429) ProcEnviron: LANGUAGE=pl_PL:en PATH=(custom, user) LANG=pl_PL.UTF-8 SHELL=/bin/bash SourcePackage: unity UpgradeStatus: Upgraded to natty on 2011-05-05 (11 days ago) ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug natty running-unity -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/783860 Title: minimize all does not obey non_minimizable window rule -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 783860] Re: minimize all does not obey non_minimizable window rule
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/783860 Title: minimize all does not obey non_minimizable window rule -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 771308] Re: unity top bar using incorrect color scheme and icon set intermittantly
I had noticed the problem also in Maverick (it could have started after switching to maverick-proposed upgrade set, but I'm not sure). It happened occassionally that after login the colour/icon setup was incorrect (same set as in the screenshot above). I usually killed the Xserver and loged in again to get it straight. Now I am at natty, so I can't repeat the maverick problem. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/771308 Title: unity top bar using incorrect color scheme and icon set intermittantly -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
