Its look like the issue is on usage the connect/pair command.
When use a bluetoothctl 'connect' command, the connection is
established, with info:
[CHG] Device ServicesResolved: yes
[CHG] Device Paired: yes
Connection successful
but the [LinkKey] section is not stored in 'info' file.
When use
This bug was fixed in the package shadow - 1:4.5-1.1ubuntu2
---
shadow (1:4.5-1.1ubuntu2) disco; urgency=medium
* debian/patches/1013_extrausers_deluser.patch
- add --extrausers option to "userdel" (LP: #1659534)
-- Michael Vogt Fri, 22 Mar 2019 19:32:50
+0100
** Changed in
** Changed in: python
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gdb in Ubuntu.
https://bugs.launchpad.net/bugs/1348275
Title:
gdb message "Got object file from memory but can't read symbo
** Description changed:
+ [Impact]
+ Pinning on local-only package versions is ignored, causing them to be
upgraded.
+
+ [Test case]
+ The integration tests include an automated test case that contains a package
called coolstuff in three versions. We are specifying a Pin for the installed
one,
This has been fixed now. Marking it as such.
** Project changed: snappy => snapd
** Changed in: snapd
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libseccomp in Ubuntu.
https://b
This updated debdiff for xenial ran a full autopkgtest run of snapd on
16.04 without errors.
** Patch added: "Slightly more updated debdiff for xenial with PR#11121"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1819728/+attachment/5249168/+files/systemd_229-4ubuntu21.19.debdiff
--
** Bug watch added: Debian Bug tracker #914694
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914694
** Also affects: iptables (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914694
Importance: Unknown
Status: Unknown
--
You received this bug notification becaus
Forgot to write that even microphone does not work at all
Il lunedì 25 marzo 2019, 02:40:52 CET, Daniel van Vugt
ha scritto:
Can you please run:
dpkg -l > allpackages.txt
and then attach 'allpackages.txt'?
--
You received this bug notification because you are subscribed to the bug
Here some logs
hp@hp-desktop:~$ sudo apt remove timidity
Lettura elenco dei pacchetti... Fatto
Generazione albero delle dipendenze
Lettura informazioni sullo stato... Fatto
Il pacchetto "timidity" non è installato e quindi non è stato rimosso
0 aggiornati, 0 installati, 0 da rimuovere e 5 n
Public bug reported:
[IMPACT]
Xenial uses systemd as default now, debian salsa
4a49edf26d405726041bee12a42d6f064145c87e, introduce a shell script,
taking advantage of systemctl directly if systemd is active by still keeping
Sysv init script as fallback only.
While there is no 'real' impact, I
** Tags removed: sts
--
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/1612294
Title:
Boot messages in /var/log/syslog are out of order and with mostly
"useless" timestamp
** Changed in: systemd (Ubuntu Trusty)
Status: Confirmed => Invalid
** Changed in: systemd (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.la
** Tags removed: sts
--
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/1627950
Title:
Stopped (with error) ... messages on encrypted LVM shutdown
Status in systemd:
Unknow
(In reply to Kai-Heng Feng from comment #9)
> My intention is to ask you to try adding this entry to pin-code-database.xml:
>
See https://gitlab.gnome.org/GNOME/gnome-bluetooth/merge_requests/14
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, whic
This bug was fixed in the package systemd - 240-6ubuntu3
---
systemd (240-6ubuntu3) disco; urgency=medium
* virt: detect WSL environment as a container (LP: #1816753)
* debian/control: Update Vcs-{Browser|Git} to Ubuntu's packaging repository
* debian/gbp.conf: Set tag format to
Uploaded into xenial upload queue. Now waiting for SRU verificaition
team to approve the upload for rsyslog to start building into xenial-
proposed for the testing phase.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsyslog
** Description changed:
[IMPACT]
- Xenial uses systemd as default now, debian salsa
4a49edf26d405726041bee12a42d6f064145c87e, introduce a shell script,
+ Xenial uses systemd as default now, debian salsa
4a49edf26d405726041bee12a42d6f064145c87e, introduce a shell script,
taking advantage
** Description changed:
[IMPACT]
Xenial uses systemd as default now, debian salsa
4a49edf26d405726041bee12a42d6f064145c87e, introduce a shell script,
taking advantage of systemctl directly if systemd is active by still keeping
Sysv init script as fallback only.
While there is no 'r
Hello Eric, or anyone else affected,
Accepted rsyslog into xenial-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/rsyslog/8.16.0-1ubuntu3.1 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://
Are there additional steps that need to occur?
** Changed in: iptables (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iptables in Ubuntu.
https://bugs.launchpad.net/bugs/1820114
Tit
FYI, I cannot reproduce this with even less memory:
$ iptables --version
iptables v1.6.1
$ free
totalusedfree shared buff/cache available
Mem: 265712 114824 667441024 84144 36024
Swap: 0 0
The xenial version was also run on i386 with the full snapd testsuite
without issues.
--
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/1819728
Title:
Please backport "fix ra
** Changed in: mesa (Ubuntu)
Status: New => Invalid
** Description changed:
https://github.com/intel/intel-vaapi-driver/issues/451
- https://bugzilla.freedesktop.org/show_bug.cgi?id=110232
+ https://bugzilla.freedesktop.org/show_bug.cgi?id=110232 (No Mesa)
https://gitlab.gnome.org/GNOM
See LP: #1818862
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1821525
Title:
totem assert failure: totem: totem: gen9_mfd.c:649:
gen9_hcpd_get_reference_picture_frame_id:
$ ./remove-package -m "1.8.2 abandoned, will wait for 1.8.3 (LP: #1820317)" -s
disco-proposed iptables
Removing packages from disco-proposed:
iptables 1.8.2-4ubuntu1 in disco
iptables 1.8.2-4ubuntu1 in disco amd64
iptables 1.8.2-4ubuntu1 in disco arm64
This is now uploaded (together with #1816753) to xenial-proposed and is
currently in the UNAPPROVED queue).
--
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/1819728
Title:
P
** No longer affects: totem
** No longer affects: mesa
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1821525
Title:
totem assert failure: totem: totem: gen9_mfd.c:649:
ge
Hello larsen, or anyone else affected,
Accepted apt into trusty-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/apt/1.0.1ubuntu2.23 in
a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.ubu
I took a look at this and found that:
a) firewalld root-unittests autopkgtests fail when using either iptables 1.6 or
1.8 in release due to https://bugzilla.redhat.com/show_bug.cgi?id=1601610 and
the failure is: "2019-03-24 17:30:19 ERROR: COMMAND_FAILED: '/sbin/ipset add
foobar 10.1.2.0/22' fa
I upload 0.6.3-5ubuntu4 for the Depends/Recommends update but expect it
to fail due to the ipset issues. I filed bug 1821596 for that.
** Changed in: firewalld (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packa
Created attachment 143768
Debug trace.
I got debug traces. Please see attached file.
PID needs to be checked is 2602.
After that this process was exited with "i965: Failed to submit batchbuffer:
Bad address".
At that time I repeated to copy and delete of files by rsync.
Note: This is occurred on
Thanks for filling out the FFe! It's really a bit late for such a big change,
especially that it seems not only Kubuntu seeds Qt5 (seeded-in-ubuntu mentions
also studio, mate, lubuntu etc.).
You mentioned rebuilds of packages that build-depend on qtbase and
qtdeclarative private packages: after
Public bug reported:
Okay the has happened recently at least since march 18, 2019 iso and
march 22, 2019 iso are both effected very similar to one of my
previously reported bugs .. which was related to xorg not being
installed ..
back ground .. PC is lenovo sl 500 with evo860 SSD drive
3 partio
** Description changed:
[IMPACT]
Xenial uses systemd as default now, debian salsa
4a49edf26d405726041bee12a42d6f064145c87e, introduce a shell script,
taking advantage of systemctl directly if systemd is active by still keeping
Sysv init script as fallback only.
While there is no 'r
** Description changed:
[IMPACT]
Xenial uses systemd as default now, debian salsa
4a49edf26d405726041bee12a42d6f064145c87e, introduce a shell script,
taking advantage of systemctl directly if systemd is active by still keeping
Sysv init script as fallback only.
While there is no 'r
this bug was filed from sda6 partition..
with this command and the following errors generated
ubuntu-bug
cat: /var/log/lightdm/x-0-greeter.log: No such file or directory
cat: /var/log/lightdm/x-0-greeter.log.old: No such file or directory
(/usr/lib/firefox/firefox:5674): dconf-WARNING **: 11:31:0
** Description changed:
+ [Impact]
+
+ * Without the introduced fallbacks u-u could not upgrade particular package
sets from -security. It could be observed in Cosmic with systemd security
updates failing to install in:
+
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a849
Hello Søren, or anyone else affected,
Accepted systemd into cosmic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/239-7ubuntu10.11 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://
** Description changed:
- This is part of the reason why the autopkgtes installing all security updates
is failing for cosmic with 1.10ubuntu1:
+ [Impact]
+
+ * Without the fix u-u could not upgrade particular packages from -security.
It could be observed in Cosmic with systemd security update
Hello Søren, or anyone else affected,
Accepted systemd into xenial-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/229-4ubuntu21.19 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://
Hello Søren, or anyone else affected,
Accepted systemd into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/237-3ubuntu10.17 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://
Hello Michael, or anyone else affected,
Accepted systemd into xenial-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/229-4ubuntu21.19 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
https:
Hi Łukasz!
I have not yet rebuilt reverse dependencies, but if there is a chance of
getting this FFe approved I can add them to the PPA tomorrow.
If you are not going to approve this, then no problem for me personally,
we will land 5.12.2 (or even .3) at the beginning of next release cycle.
--
Hello Michael, or anyone else affected,
Accepted systemd into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/237-3ubuntu10.17 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
https:
Hello Michael, or anyone else affected,
Accepted systemd into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/237-3ubuntu10.17 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
https:
I have enabled the "proposed" repository and installed apt
"1.0.1ubuntu2.23". Though, even after another "apt-get update", "apt-get
upgrade" still wants to downgrade my "burp" package.
It's noticeable that "policy's output" now contains a different
"Candidate" version number.
# dpkg -l apt
(snip
Well, the version of apt is irrelevant. The version of libapt-pkg4.12 is
what matters - is that one upgraded too?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1821308
Title:
Public bug reported:
Starting with systemd 237-3ubuntu10.14, the testcase test-seccomp is
failing on Bionic on ppc64el with the error messages:
Operating on architecture: ppc
Failed to add n/a() rule for architecture ppc, skipping: Bad address
Operating on architecture: ppc64
Failed to add n/a()
> Well, the version of apt is irrelevant. The version of libapt-pkg4.12 is
> what matters - is that one upgraded too?
I didn't see a hint this package should be updated.
Have updated libapt-pkg4.12 now (to 1.0.1ubuntu2.23) and there is no false
downgrade anymore.
Thanks!
--
You received this bu
** Changed in: iptables (Debian)
Status: Unknown => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iptables in Ubuntu.
https://bugs.launchpad.net/bugs/1820317
Title:
The firewalld autopackage tests fai
The test case also passed successfully on the autopkgtest for
1.0.1ubuntu2.23
Check that local-only versions can be pinned correctly (LP: #1821308)
Test for successful execution of apt-cache policy coolstuff … PASS
Test for correctness of file /tmp/tmp.PtSrwfN8WU/rootdir/tmp/testsuccess.output
…
I'm afraid that this is by design, to prevent a malicious user from
dumping basically anything into one of the crontab directories.
An attacker once compromised a debian.org host by triggering a crafted
core dump in one of the crontab directories, and the daemon kept trying
to execute lines until
** Also affects: unattended-upgrades (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: unattended-upgrades (Ubuntu Cosmic)
Importance: Undecided
Status: New
** Changed in: unattended-upgrades (Ubuntu Cosmic)
Status: New => Fix Released
--
You received
Public bug reported:
I have apt configured to load a wide variety of sources; my apt is using
a local squid-deb-proxy on the same system, and the source that is
failing is hosted on an archive mirror on my LAN.
Today I noticed unexpected results from apt-get update:
# apt-get update
Hit:1 http:/
Note only DHCP configuration exhibits this particular issue. The cause
is that when "dhcp4" is set to "yes" in the /etc/netplan/*.yaml config
file, netplan would generate a temporary per-interface yaml file under
/run/netplan, which matches interface using MAC address. While I don't
see this specif
** Description changed:
+ [Impact]
+
+ * Unattended-upgrades crashes while auto-removing kernel packages.
+
+ [Test Case]
+
+ 1. Install kernel packages to be automatically removed:
+ # eatmydata apt install linux-image-unsigned-4.18.0-13-generic
linux-image-unsigned-4.18.0-14-generic linux
Public bug reported:
Unattended-upgrades keeps versioned kernel packages because they don't
match known kernel package patterns:
...
Keeping auto-removable linux-modules-4.18.0-14-generic package(s) because it
would also remove the following packages which should be kept in this step:
linux-ima
** Description changed:
[Impact]
This bug is the master bug for a one time SRU of ufw to the new 0.36
release. Typically patches would be individually backported like normal,
but the new 'prepend' command feature is the impetus for this SRU and it
contains most of the code changes. Ot
FYI, I've reuploaded 0.36 to bionic-proposed and cosmic-proposed after
updating this master bug's description.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ufw in Ubuntu.
https://bugs.launchpad.net/bugs/1811129
Title:
up
FYI, I've reuploaded 0.36 to bionic-proposed and cosmic-proposed after
updating the master bug's description.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ufw in Ubuntu.
https://bugs.launchpad.net/bugs/1368411
Title:
Can
Hmm, but linux-image-unsigned-$foo should not be installed in the first
place.
** Changed in: apt (Ubuntu)
Status: New => Triaged
** Changed in: apt (Ubuntu)
Importance: Undecided => Low
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, wh
Public bug reported:
When I report a bug in Ubuntu I get the following errors.
(apport-gtk:16883): Gtk-WARNING **: 18:54:44.036: Theme parsing error:
gtk-widgets.css:3135:13: 'max-width' is not a valid property name
(apport-gtk:16883): Gtk-WARNING **: 18:54:44.037: Theme parsing error:
gtk-widge
You have been subscribed to a public bug:
Hello,
I have my ubuntu desktop set to boot text only mode.
it seems a removable hard drive was pplugged into my machine some time ago.
On every boot the boot takes a minute and a half to search to see if that drive
is plugged in.
I ran systemd-analyze
You have been subscribed to a public bug:
I'm uncertain which package is causing the problem, though I strongly
suspect it may be nvidia related.
This laptop runs 18.10 just fine, but attempting to boot 19.04 from a
USB disk (tried multiple USB boot disks) results in a blank screen after
Grub. Th
** Package changed: ubuntu => systemd (Ubuntu)
--
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/1821462
Title:
Ubuntu 19.04 Desktop:slow boot
Status in systemd package in U
** Package changed: ubuntu => xorg (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1821426
Title:
Ubuntu 19.14 disco will not boot on Dell Precision5530
Status in xo
** Also affects: gnome-bluetooth (Ubuntu)
Importance: Undecided
Status: New
** Changed in: gnome-bluetooth (Ubuntu)
Status: New => Confirmed
** Changed in: oem-priority
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touc
Please run:
apport-collect 1821426
to send us more information about the machine.
Please also try these potential workarounds and let us know which one(s)
work:
(a) Edit /etc/gdm3/custom.conf and uncomment the line:
#WaylandEnable=false
and reboot.
(b) Disable integrated graphics/G
*** This bug is a duplicate of bug 1818862 ***
https://bugs.launchpad.net/bugs/1818862
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1818862, so it is being marked as such. Please look
Public bug reported:
I'm experiencing a repeating crackling noise after 19.04 upgrade that
start just after the boot and before the login.
I tried a bunch of fixes for pulseaudio I found googling, including this one
https://wiki.archlinux.org/index.php/PulseAudio/Troubleshooting#Glitches.2C_skip
You seem to be booting in recovery mode, which will also break graphics
support in its own way :/
Please:
1. Reboot and as soon as the purple screen appears tap Escape. Now
choose a normal kernel and not recovery.
2. Reproduce the problem.
3. Reboot again into recovery mode if you need to.
4.
** Description changed:
I'm experiencing a repeating crackling noise after 19.04 upgrade that
start just after the boot and before the login.
I tried a bunch of fixes for pulseaudio I found googling, including this one
https://wiki.archlinux.org/index.php/PulseAudio/Troubleshooting#Glitc
Well, this design is wrong then, because I'm talking about /etc/crontab ,not
about /etc/cron.d directory. System crontab ( /etc/crontab ) is protected by
access rights, so it can't be changed by malicious user.
And any error causes cron almost stop working, because in my case
/etc/crontab contai
Thanks for the bug report. Since pulseaudio is unchanged (the same
version) in 19.04 from 18.10 I think we can exclude that as a possible
cause.
1. The first idea I have about possible causes is a kernel change (and
the kernel has changed a lot). Please try some older kernels from here:
https:/
You have been subscribed to a public bug:
Okay the has happened recently at least since march 18, 2019 iso and
march 22, 2019 iso are both effected very similar to one of my
previously reported bugs .. which was related to xorg not being
installed ..
back ground .. PC is lenovo sl 500 with evo86
[Expired for gdk-pixbuf (Ubuntu) because there has been no activity for
60 days.]
** Changed in: gdk-pixbuf (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gdk-pixbuf in Ubuntu.
h
It appears the problem is related to lightdm and PAM:
Mar 25 23:26:07 zlink2 lightdm[840]: PAM unable to dlopen(pam_kwallet.so):
/lib/security/pam_kwallet.so: cannot open shared object file: No such file or
directory
Mar 25 23:26:07 zlink2 lightdm[840]: PAM adding faulty module: pam_kwallet.so
M
Please have a look to see if any of the existing bug reports might be
the same issue:
https://bugs.launchpad.net/ubuntu/+source/kwallet-pam
** Also affects: lightdm (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touc
It sounds like the solution might be a simple matter of adding 'derk' to
/etc/group on line:
nopasswdlogin:x:132:
So that becomes:
nopasswdlogin:x:132:derk
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubun
journalctl -b-1 > prevboot3.txt post group change .. no joy ..also
makes machine wide open no passwd required
.. i will revert this
On Tue, Mar 26, 2019 at 12:35 AM Daniel van Vugt <
daniel.van.v...@canonical.com> wrote:
> It sounds like the solution might be a simple matter of adding 'derk
the above comment .. is perhaps a bit brief .. in spite of the log
showing a pam pass no login screen was available .. it was blanked out
.. gone just a cursor and that also disappeared after a bit .. (still
using testing partition sda6 for all this)
--
You received this bug notification because
81 matches
Mail list logo
