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;
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
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
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
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
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
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
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
--
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
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
10 matches
Mail list logo
