The bug is still there as of LibO 7.3.x. Up in comment 12
(https://bugs.documentfoundation.org/show_bug.cgi?id=120663#c12) there
is a nice analysis of the underlying problem why the remote cannot work.
Established that, I think that most users go used to the fact that the
remote functionality
Bug still there. In most situations the remote cannot be used at all.
Not via bluetooth (because of this issue), neither via wifi (because you
typically do presentations at sites where you do not control the wifi
network and traffic to the relevant ports gets blocked). Suggested
upstream some
Public bug reported:
While testing functionalities of knot resolver, I am experiencing issues
in how systemd-resolved interacts with it. I have the caching and
forwarding knot resolver running on a debian machine and systemd-
resolved running on an ubuntu focal machine.
It looks like
Looks like the DNS provided by Cloudflare (1.1.1.1 and 1.0.0.1) has
picked up with standards and is also delivering NXDOMAIN together with
an authority section with a SOA when you query anything in local.
. 86400 IN SOA a.root-servers.net.
nstld.verisign-grs.com.
Thanks, I'll try that and try to report. I have already asked on various
forums if there is any way to replace /only/ the stub resolver (systemd-
resolved) with a more recent version without replacing all the code
related to init and the system initialization and been told there is no
safe way,
Public bug reported:
As discussed on https://gitlab.nic.cz/knot/knot-resolver/-/issues/686,
DNS servers are expected to immediately answer any queries within local
by NXDOMAIN. See
https://datatracker.ietf.org/doc/html/rfc6762#section-22.1 in this
respect. However, while they do so they seem to
Marked by myself the issue as invalid, since when I reported the issue
my understanding of it was to o modest. Will open a new more
appropriate issue.
** Changed in: systemd (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch
Unfortunately, I have no idea on how to bisect this, due to the fact
that there is not an independent repo for systemd-resolved and
attempting to work on the whole systemd seems to dounting and risky as
an experience for me. Is there a ppa with a more recent systemd-
resolved to try on focal
Tested on a manjaro system that being rolling uses the latest systemd.
There is no issue there.
Hence the problem appears to be a systemd-resolved bug specific to the
systemd version shipped with ubuntu 20.04.
Because the issue breaks local resolution via mDNS in some
configurations, I think
Public bug reported:
I have a setup where a host (say A) in the network runs knot-resolver as
a caching nameserver.
Among the other hosts, some of them run ubuntu 20.04 and use systemd-
resolved. The dhcp setup make all these host use A as their nameserver.
The issue with systemd-
The issue is
Public bug reported:
Lack of permissions to access the display causes QT to dump core.
You get
Qt WARNING: could not connect to display
Qt FATAL: This application failed to start because no Qt platform plugin could
be initialized. Reinstalling the application may fix this problem.
Available
Happened again today.
How do you disable dnssec completely in systemd-resolved? resolvectl
does not seem to have an option for that. Is editing resolved.conf and
restarting resolved the only way?
In any case I could not try, I was too much on a hurry and reconfiguring
network manager to use
Public bug reported:
Seen in 20.04.
Trying to connect to the internet using the mobile phone hotspot is
impossible due to systemd-resolved not resolving and reporting things
like:
resolve call failed: DNSSEC validation failed: incompatible-server
and
systemd-resolved[81699]: DNSSEC validation
Still true of the deb packages provided by upstream for Virtualbox
6.1.18.
The problem is really with the packaging on their side which does not
target ubuntu 20.10. In fact, they say so by indicating that they have a
deb up to 19.10 and 20.04.
I guess there is little that ubuntu can do if
Finished my investigation. Guess it is not a bug after all, rather — I
would say — a matter of extremely dispersed documentation plus very
unfriendly behavior from the ISP.
The situation is that even if you put mdns_minimal in front of other
entries in hosts in nsswitch, mdns /is not queried/ if
Host entry in nsswitch.conf is:
files mdns4_minimal [NOTFOUND=return] dns
Note that I do not see the issue anymore, because the ISP has (for the
time being) stopped messing so aggressively with dns.
In any case, I've moved to using dns over tls which systemd.resolved
supports perfectly with
Tested with latest mesa 20.3 from oibaf ppa and issue is still present.
Same behavior is also observed with the zink driver.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
Public bug reported:
Both Matlab and Scilab (which are java based) fail when using the iris
graphics driver. As a workaround you can make them work using
MESA_LOADER_DRIVER_OVERRIDE=i965
There is a bug open for scilab at
https://bugzilla.scilab.org/show_bug.cgi?id=13830 (in fact one of the
The premise is that my ignorance on BT is complete. After some
investigation, it is my understanding that RFCOMM channels are to RFCOMM
communication a bit like ports in TCP and UDP, with the main difference
that while there are really a lot of TCP/UDP ports and some of them are
reserved as "well
Thanks for the analysis!
>From it, I still wonder whether this is a pulseaudio bug, though. Why is
pulseaudio ever binding to RFCOMM channel 3 *before* there is any need
to do so? That is, until I am not connected to any device using channel
3, why is pulseaudio already using it up?
In other
Andrzej, I am CC-ing you on this, because I believe that you were one of
the original corder of the BT code for the impress remote on linux. I
hope that you may able to provide some advice on this. If I'm wrong,
please take my apology for the noise.
--
You received this bug notification because
The bug is also confirmed in the ubuntu launchpad at
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1798400.
Users there are reporting that they are experiencing the issue in ubuntu
(from bionic, I think) and gentoo. This adds to the reports in fedora
and to the confirmation here on arch
Issue still present in LibO 6.4.3.1.
I see the bug as still unconfirmed after more than one year. I wonder if
it could be confirmed, given that the same issue has also been reported
for redhat (https://bugzilla.redhat.com/show_bug.cgi?id=1581879)
--
You received this bug notification because
@John Poole
Can you please indicate that you are also experiencing the issue in the
issue tracker at the document foundation at
https://bugs.documentfoundation.org/show_bug.cgi?id=120663 ?
The issue is still "unconfirmed" there, and until it is "confirmed" by
multiple reporters, there is little
Actually not a bug, for sure not the one indicated for Fedora.
Just a very poor interaction of the Kyocera DEB package with the Disco->Eoan
upgrade.
** Changed in: cups (Ubuntu)
Status: New => Invalid
** Changed in: samba (Ubuntu)
Status: New => Invalid
--
You received this bug
Running cups in debug mode (cupsctl --debug-logging) in the logs I see a
couple of interesting lines:
[Job 1008] PID 2888 (/usr/lib/cups/backend/smb) stopped with status 2.
...
[Job 1008] Unable to connect to CIFS host: NT_STATUS_INVALID_ACCOUNT_NAME
...
[Job 1008] Backend returned status 2
Sorry, could not report the issue from the machine where I have first
experienced the bug. Also marked samba as a possible source for the
issue (from the fedora report). If the issue is the same, it seems fixed
in Fedora.
** Also affects: samba (Ubuntu)
Importance: Undecided
Status: New
Wonder if it could be useful to kindly ask Andrzej Hunt if he can look
into the issue. If I am not wrong he is the author of the current bluez
5 code in Impress.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in
Issue persists with current LibO 6.3.1.2 and most likely due to the fact
that the bluetooth stack on linux (bluez) has changed in the past years
and impress has not cought up.
Problem is now more visible due to the startup tooltips in Impress 6.3.x
which explicitly introduce the impress remote
Cannot test daily builds right now, but 6.3.0 beta 1 still has the issue.
Launching impress reports:
bluetoothd[1386]: RFCOMM server failed for LibreOffice Impress Remote:
rfcomm_bind: Address already in use (98)
in the system logs and then the remote app cannot contact the host.
--
You
Trying to downgrade systemd seems to be impossible. As soon as I try an
apt install --reinstall systemd= apt tries to remove half
of the system...
I have noticed the issue in the past 15 days, I think, but only had time
to look at it more closely right now.
Some notes:
- Trying to upgrade the
Public bug reported:
Recently, hybrid-sleep has been broken on cosmic.
Calling systemctl hybrid-sleep used to work perfectly on my system. Now,
after having saved the state to disk, it switches off the machine rather
than suspending it.
ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package:
Hi Dmitry,
I've been testing the package in cosmic-proposed in the last few days.
Sorry I have not reported earlier, but I encountered a little problem
and I wanted to look better at it for extra safety.
In fact, it was a problem with a single printer of the many I use while
roaming with my
Dimitri, if you can have a package for cosmic with the fix built in a
PPA, I would be glad to try it.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtbase-opensource-src in
Ubuntu.
https://bugs.launchpad.net/bugs/1776173
Hi Dmitry,
thanks for your message and the work as volunteers on Qt packaging.
My message was merely to know if there was any need for a specific bug item
about the backporting and it is great to hear that you were already planning
the backport!
Also, great to hear that 19.04 is going to get
Should a specific bug be opened to ask for this to be officially
backported to Bionic+Cosmic as a bug-fix?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtbase-opensource-src in
Ubuntu.
The issue is also present in cosmic.
Wonder if someone might be kind enough to build a deb with the patch for cosmic
too... Would be very much appreciated!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
1) I confirm that the gray-scale printing option is completely ignored
and that the printer prints always in color (this is definitively a
bug).
2) I confirm that an option to select the printer tray is missing
(though I think this may be a limitation in the qt version shipped with
bionic).
3) I
Still present in 6.2.0 RC 1
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1798400
Title:
Regression: cannot use impress remote over bluetooth with ubuntu
bionic
Status
I think that the issue can be either a bug in the bluetooth stack or
merely something that has /changed/ in the bluetooth stack, that
libreoffice has not tracked properly. Hence, I have also opened a bug
upstream for LibO, mentioning this one.
--
You received this bug notification because you
I have stayed a long time without trying impress remote, so I do not
know exactly when the issue started. However, I am sure that last year
at this time (aka on 16.04) the issue did not exist.
Just tried latest non-RC kernel from mainline 4.18.x and the issue is
still there.
** Changed in: linux
See https://bugzilla.redhat.com/show_bug.cgi?id=1581879
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1798400
Title:
Regression: cannot use impress remote over bluetooth
Public bug reported:
Trying to use the impress remote
(https://wiki.documentfoundation.org/Impress_Remote) over bluetooth with
libreoffice over ubuntu bionic fails.
The handset errors out that it cannot connect with Libreoffice on the
computer even if the bluetooth adapter on the handset and on
Public bug reported:
All kde applications shipped with ubuntu and particularly kubuntu bionic
print via the qt print dialog, that, unfortunately, does not seem to
respect the defaults set for the printer.
Specifically, every time one starts to print the "duplex" option gets
reset to "none" even
Does not work in artful either.
On 17.10, the HSP/HFP option is shown in dropdown menus (pavucontrol,
kde audio config, etc.). However, selecting them does not work and when
one checks again the setting has gone back automatically to a2dp sink.
Please reopen. Otherwise advise whether a new
Made the quick check you suggested. Switching off cups, all printers
disappear both in okular (QT) and firefox. So it looks like the
driverless network printers come from cups.
Weird enough now after the switch off - switch on sequence for cups, I
do not have the driverless printers them in
@Till
Thanks! This is a great explanation. I am sure that it took you some
time to write it in this clear way and I would like to let you know that
I really appreciate it. Things look a bit clearer to me right now.
I am looking forward to seeing method (4) materialize as the current
situation
And I think that the conclusion is the following:
- The KDE print dialog bypasses cups-browsed to list the driverless
network printers, if cups-browsed is not running. In this case it fails
to gather some information such as the "type" of the printer, though.
- For the KDE print dialog not to
One weird phenomenon is that
- if cups-browsed is active, the okular print dialog shows the
driverless printers and indicates their type as driverless
- if cups-browsed is not active, the okular print dialog shows the
driverless printers but fails to indicate their type (type is empty).
--
You
One weird phenomenon is that
- if cups-browsed is active, the okular print dialog shows the
driverless printers and indicates their type as driverless
- if cups-browsed is not active, the okular print dialog shows the
driverless printers but fails to indicate their type (type is empty).
--
You
1) cups-browsed does not appear in ps auxwww
2/3) The driverless printers appear in the print dialog of okular
4) avahi-browse -v -t -r --all returns tons of printers in forms such as
= eth0 IPv4 Lexmark MS610dn _ipps._tcp
local
hostname =
My printing almost always happens from okular which uses a QT print
dialog.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1738432
Title:
Regression, poor user experience,
Thanks for the clarification in the last answer, that is helpful for me
to find out which ones among the many attempts I made to disable the
display of the driverless entries eventually worked (since it could be
nice for me to script enabling/disabling actions to place into some
network
I do not know if I am allowed to publish details of my company intranet
that I expect to be collected with the avahi-browse or the lpstat -v.
I'll try to find out first. In any case, I'll try to provide what I can
when I am again at the office with the newer printers appearing as
driverless
Don't know what I did, but finally I have succeeded disabling the
display of the driverless network printers.
Right before systemd reported cups-browsed as stopped.
Can it be the case that you need /both/ the process stopped /and/ the
BrowseRemoteProtocols in its conf file set to none /at the
Public bug reported:
Recently, my print dialogs have started to include network discoverd
printers in addition to those configured in cups even if the cups-
browsed service is disabled and the BrowseRemoteProtocols option is set
to none.
There does not seem to be any way to disable this behavior
Still here as of 17.04 zesty.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1200124
Title:
ubuntu bug hangs if you are already logged in launchpad
Status in apport
I have occasionally seen this too, in kubuntu 17.04. What is weird is
that it happens only sometimes, and I cannot recognize what triggers the
issue. Last time it went away with a reboot.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
I see it all the time after an upgrade to 17.04. Medium priority seems
an euphemism. This is a true showstopper. It is not just systemd-
resolved taking a whole core. Dnsmasq takes half of another. The cpu
runs hot. In a laptop, batteries drain in a snap.
Has this to do with
I see something similar in 16.10.
Weird enough, issuing an
iwlist wlan0 scan
seems to be enough to get the available connections again
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
Can we safely assume that bug 1675820 is a duplicate of this one?
In that case, dnsmasq seems to operate correctly. In fact, setting the
domain server with an explicit dbus command, that is
sudo qdbus --system org.freedesktop.NetworkManager.dnsmasq
/uk/org/thekelleys/dnsmasq \
Public bug reported:
Occasionally, after a resume from an update, network manager starts
behaving strangely, not setting the DomainServer for the network.
This happens when resuming the laptop to a location where:
- an additional ethernet card (which is the one to use) is attached via USB
-
Yes, but shouldn't this be a dependency of python-apport?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1451808
Title:
apport-collect error: No module named PyQt5.QtCore
Sorry, I'm not understanding your comment.
What I understood is that the systemd developers said "It is not our
responsibility if ubuntu does not boot, this is not a systemd bug! In
fact, the issue in booting is caused by some quota related units,
shipped by Ubuntu, that are not part of systemd".
Systemd devels suggest that the bug is due to downstream (ubuntu), since
they do not ship the quota.service unit (whose removal makes the system
boot again) at all.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in
Got it! Sort of...
Misabling quotas make the system boot reliably.
No clue why. It may not be a race, rather the fact that the initial
quota check is supposed to happen only in certain cases.
No idea. Debugging boot with systemd is beyond my expertise.
Masking the systemd quota.service (the
** Summary changed:
- yakkkety boot is erratic
+ Regression: yakkety does not boot (boots once every 4 attempts)
** Summary changed:
- Regression: yakkety does not boot (boots once every 4 attempts)
+ Regression: yakkety does not boot (boots once every ~4 attempts)
** Attachment added: "The
** Attachment added: "The systemd units when the issue is present"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1635023/+attachment/4767054/+files/systemctl.output.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
Issue is present also moving do mdadm (which is possible for my fake
raid since it uses intel metadata).
When it happens, the boot hangs for 1 minute and a half on
A start job is running for dev-disk-by...
with all disks appearing in turn on the line. After that the machine drops to
an
Public bug reported:
After an upgrade from xenial to yakkety, the system does not boot
reliably. Only 1 boot over 3-4 seems to succeed.
Quite often, the system seems to hang during boot and then drops into an
emergency prompt.
Pressing esc during the boot to show what is going on reveals that
Possibly also related to 1320402 (as the unnecessary resync probably
follows the incorrect stopping of the array).
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1587142
Goes on as of 16.04
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1200124
Title:
ubuntu bug hangs if you are already logged in launchpad
Status in apport package in
@Steve Langasek
A big issue is that the script makes quite arbitrary assumptions on the system,
including the fact that there is an ondemand governor at all.
A large number of modern systems use the intel p-state driver that does
not have an ondemand governor at all! On this systems, the
Please, reopen.
The ondemand script is totally broken for systems with cpu frequency
scaling drivers other than acpi that do not provide an ondemand
governor. Most important its quite arbitrary assumptions cause systems
with the intel p-state driver to have worse performance than they
should.
Since the /etc/init.d/ondemand script has many other issues, including
overriding the settings prepared by /etc/init.d/cpufrequtils, I think
that the best option should be removing it.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
There is another issue:
/etc/init.d/ondemand tries to set the governor to ondemand
unconditionally, even on intel systems with p-state.
Systems with the p-state frequency scaling do not have an ondemand
governor at all. This means that the /etc/init.d/ondemand falls back to
the powersave
I am just realizing that this other problem is already listed as bug
1480320
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to sysvinit in Ubuntu.
https://bugs.launchpad.net/bugs/911206
Title:
/etc/init.d/ondemand
Thanks for the information!
I am a bit surprised by this approach, which looks weird to me. It's a
service basically deciding it "owns" the content of some files without
telling anyone.
In fact, I've always believed that the configuration is in text files
and not in some private database format
===
Authentication is required to manage system services or units.
Multiple identities can be used for authentication:
1. Sergio Callegari (callegar)
2. Sergio Callegari (callegar)
Choose identity to authenticate as (1-2):
Why is the same identity seen as two different identities
Now getting different errors and apport-collect still not working...
apport-collect 1451277
...
Waiting to hear from Launchpad about your decision...
(process:15275): GLib-CRITICAL **: g_slice_set_config: assertion 'sys_page_size
== 0' failed
dpkg-query: no packages found matching linux
I confirm it does not give this error after manually installing python-pyqt5.
Weird. I thought distro support was all python3 by now.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
Seems to work launching
sudo apport-collect
but then starts web browser as root...
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1451808
Title:
apport-collect broken in
Yes, I see the same with the graphical backend. I only reported the text
one, since it was easier.
getent passwd | grep callegar
has a single entry for the user
callegar:x:1000:1000:Sergio Callegari:/home/callegar:/bin/bash
--
You received this bug notification because you are a member
Same happens with kubuntu vivid and sddm. Should this be fixed
individually in each session manager?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/794315
Title:
lightdm
Public bug reported:
To reproduce
systemctl restart some unit
AUTHENTICATING FOR org.freedesktop.systemd1.manage-units ===
Authentication is required to manage system services or units.
Multiple identities can be used for authentication:
1. Sergio Callegari (callegar)
2. Sergio
Public bug reported:
In kubuntu vivid, apport reacts as follows:
apport-collect 1451277
ERROR: Could not import module, is a package upgrade in progress? Error: No
module named PyQt5.QtCore
ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: apport 2.17.2-0ubuntu1
ProcVersionSignature:
:Sergio Callegari:/home/callegar:/bin/bash
stunnel4:x:111:123::/var/run/stunnel4:/bin/false
sshd:x:110:65534::/var/run/sshd:/usr/sbin/nologin
pulse:x:112:119:PulseAudio daemon,,,:/var/run/pulse:/bin/false
clamav:x:113:125::/var/lib/clamav:/bin/false
postfix:x:102:103::/var/spool/postfix:/bin/false
The issue of the network not reconnecting after a suspend cycle is
present also in utopic (14.10).
Maybe it is another bug, but if this is the case, the fact that other
bugs opened on the issue are made duplicate of this should be corrected.
The issue completely breaks the possibility of using
The issue of the network not reconnecting after a suspend cycle is
present also in 14.10 (utopic).
Maybe it is another bug, but if this is the case, the fact that other
bugs opened on the issue are made duplicate of this should be corrected.
The issue completely breaks the possibility of using
I see it on a laptop that does not connect automatically to the wireless
network after wakeup. But I have the same issue also with a desktop with
wired ethernet. So a more appropriate title would be 'network manager
fails to reconnect after resume', because the issue is not wifi
specific.
After
As a further note, the script by aztecjoe works around the issue just
fine.
I would recommend delivering it via an updated network manager package
and not waiting for network manager to have the issue fixed. If and when
the issue is fixed in network manager, the redundant restart should not
be a
Same issue in trusty.
This is in fact a kernel bug: see https://lkml.org/lkml/2014/2/9/316.
Tried mainline (e.g. 3.15.6) and works fine.
There is also another bug in modemmanager/networkmanager. This keeps
rfcomm0 open when the connection is dropped and causes modemmanager to
keep asking the
Dun with network manager has now been broken for a few years. We have
passed from hard kernel crashes on attempts to use it to the current
situation where the functionality is advertised and simply not working.
Now, I am on trusty and I do not know if my case is exactly the one
mentioned in this
Yes, in fact it is a kernel bug.
Working with 3.15.6 from the ppa mainline, modemmanager can see the
modem and you can connect.
So, if you really need bluetooth DUN, just move to a recent kernel.
Unfortunately it is not really enough, because after you have fixed the
kernel bug, you can start
94 matches
Mail list logo
