Vladimir:
> I will need to build a reproducer that logs events and submit the
issue upstream.
Thank you for taking this further than I could Vladimir!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/21
Public bug reported:
Description of the problem
When wsdd-server is installed needrestart always reports that it needs to be
restarted.
Steps to reproduce:
1. Start an Ubuntu 24.04 VM.
2. Run sudo apt update && sudo apt install -y needrestart wsdd-server
3. Run sudo needrestart -r l
Expected re
Hello Vladimir:
> I did the first test on the desktop with 2 displays and it did not
have the problem.
Hmph. I do wonder what prevented it from happening. Does the issue have
something to do with resolution or DPI? Or was the desktop somehow
setting environment variables that workaround the issue
I have just tried this in a fresh virtual machine install of Ubuntu
25.04 and the problem also happens (see the attached screenshot where
the Java window is much smaller than everything else and has a broken
title bar and borders after the scaling has been changed).
** Attachment added: "Screensho
Vladimir:
Just to check, were you trying to reproduce this issue on Ubuntu 25.04? I am
also using a Wayland session. The problem is highly reproducible for me - I've
attached a screencast demonstrating the problem. In the screencast also note
how the pointer size is huge on the borders of the Ja
Public bug reported:
Description of the problem
Using any fractional scaling makes the UI of Java programs very small compared
to everything else on the desktop.
Steps to reproduce:
1. apt install -y default-jre
2. Go to
https://docs.oracle.com/javase/tutorial/uiswing/examples/components/index.
** Description changed:
Description of the problem
While in the middle of a copy the network interface (which uses the r8169
driver) went offline. Downing and then upping the interface restored
connectivity.
Steps to reproduce:
1. Check out a large subversion repository over HTTPS?
(This is still happening in Ubuntu 25.04's GNOME)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2079823
Title:
Caps lock confused after suspend and resume
To manage notifications about this bug go
Public bug reported:
Description of the problem
In Ubuntu 24.10 it was sufficient to edit /etc/sysctl.d/10-magic-sysrq.conf to
override the default sysrq enablement mask at boot. In Ubuntu 25.04 doing this
no longer works because any kernel.sysrq value set in that file is overridden
by the valu
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/2107640/+attachment/5873737/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/2107640/+attachment/5873741/+files/UdevDb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2107640
Title:
Rx
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/2107640/+attachment/5873742/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2107640
Ti
Apport report attached.
** Changed in: linux (Ubuntu)
Status: Incomplete => New
** Description changed:
Description of the problem
Checking out a private subversion repo reliably triggers receive errors in
the r8169 driver when using an onboard Realtek NIC.
Steps to reproduce:
apport information
** Attachment added: "Lsusb-t.txt"
https://bugs.launchpad.net/bugs/2107640/+attachment/5873733/+files/Lsusb-t.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2107640
Title:
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/2107640/+attachment/5873740/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2107640
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/2107640/+attachment/5873739/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/210
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/2107640/+attachment/5873738/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2107640
apport information
** Attachment added: "PciMultimedia.txt"
https://bugs.launchpad.net/bugs/2107640/+attachment/5873735/+files/PciMultimedia.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/21076
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/2107640/+attachment/5873732/+files/Lsusb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2107640
Title:
Rx e
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/2107640/+attachment/5873736/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2107640
apport information
** Attachment added: "Lsusb-v.txt"
https://bugs.launchpad.net/bugs/2107640/+attachment/5873734/+files/Lsusb-v.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2107640
Title:
apport information
** Attachment added: "Lspci-vt.txt"
https://bugs.launchpad.net/bugs/2107640/+attachment/5873731/+files/Lspci-vt.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2107640
Title:
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/2107640/+attachment/5873730/+files/Lspci.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2107640
Title:
Rx e
apport information
** Attachment added: "Card1.Codecs.codec.0.txt"
https://bugs.launchpad.net/bugs/2107640/+attachment/5873729/+files/Card1.Codecs.codec.0.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.
apport information
** Attachment added: "Card0.Codecs.codec.2.txt"
https://bugs.launchpad.net/bugs/2107640/+attachment/5873728/+files/Card0.Codecs.codec.2.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.
apport information
** Tags added: apport-collected noble
** Description changed:
Description of the problem
Checking out a private subversion repo reliably triggers receive errors in
the r8169 driver when using an onboard Realtek NIC.
Steps to reproduce:
1. Do an svn checkout of a la
Public bug reported:
Description of the problem
Checking out a private subversion repo reliably triggers receive errors in the
r8169 driver when using an onboard Realtek NIC.
Steps to reproduce:
1. Do an svn checkout of a large private repo over HTTPS.
Expected result:
No errors to be triggered
@renanrodrigo
I thoroughly enjoyed reading your investigation and explanation of what
is happening and why. You also predicted one of the questions I had
while reading: "[...] why it's not happening to other python packages
that are seeded? Well it may be! haha" - haha indeed! Perhaps seeded
packa
Something to note is that in the "normal" server install case the
ubuntu-pro-client is part of default install and is somehow provided as
part of the install media ISO. In the "minimal" server install case
ubuntu-pro-client is NOT part of the default packages and has to be
installed manually after
OK I've just tested a "normal" (i.e. non-minimal) install from
ubuntu-24.04.2-live-server-amd64.iso in a VMM VM and after I log in and
run sudo -s, systemctl restart apt-news.service and check dmesg the
AppArmor denials are there. Doing a minimal server install, logging in,
running sudo -s, apt ins
Andreas:
> My guess is that at some point a local change was perhaps made to one
of the python files, and that invalidated the cache. Or maybe the post-
install script had failed before, and didn't update the cache files.
I see. Just to check, it's never the case that the cache is somehow
generat
Andreas:
Thanks for the prompt reply your suggestion has fixed the problem. The only
thing to note is that after the reinstall the following appeared on dmesg
[693175.025594] kauditd_printk_skb: 29 callbacks suppressed
[693175.025596] audit: type=1400 audit(1744704729.950:1332): apparmor="STATUS"
Hi John,
Thanks for the (rapid) update and clarifying all the options. Waiting until May
is fine for me - I'm just happy to know the warning will be fixed in the
lifetime of 24.04 :-)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
h
This sounds similar to https://github.com/canonical/ubuntu-pro-
client/issues/3193 but I can see the installed package already has the
changes of https://github.com/canonical/ubuntu-pro-
client/commit/bd8e2b05c0907a8e39d8e28e6a76f4f6303838a2 inside
/etc/apparmor.d/ubuntu_pro_apt_news .
--
You rec
Public bug reported:
Description of the problem
Every night AppArmor denial logs related to trying to write to
/lib/python3/dist-packages/uaclient/__pycache__/ are reported in the kernel
logs.
Steps to reproduce:
1. Install latest server version of Ubuntu 24.04?
Expected result:
Kernel logs t
Public bug reported:
Description of the problem
While in the middle of a copy the network interface (which uses the r8169
driver) went offline. Downing and then upping the interface restored
connectivity.
Steps to reproduce:
1. Check out a large subversion repository over HTTPS?
Expected resul
OpenZFS 2.2.7 backport patch to fix "memcpy: detected field-spanning
write" warning.
** Patch added: "zil-flex-2.2.7.patch"
https://bugs.launchpad.net/zfs/+bug/2089324/+attachment/5870271/+files/zil-flex-2.2.7.patch
--
You received this bug notification because you are a member of Ubuntu
Bug
I've just run into this with Ubuntu 24.04.2. As previously mentioned it
was initially fixed in OpenZFS 2.3.0 (the commit that went in for that
tag is
https://github.com/openzfs/zfs/commit/6f50f8e16b7c4a3f1925b41e3d47b479cd7b2d9f
). The fix was also backported to OpenZFS 2.2.7 (the commit for that i
You're welcome Mike but the real hero is Sergey who linked the GitHub
issue over in
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2084963/comments/4
. If only it had been posted here maybe more people would have been able
to test it sooner...
--
You received this bug notification because y
Does the patch mentioned in
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2085162/comments/5
help anyone else?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2081384
Title:
bluetooth headphone
Thanks to
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2084963/comments/4
I've been able to manually rebuild the bluez debs with a patch of
commit
https://github.com/bluez/bluez/commit/366a8c522b648f47147de4852c5c030d69b916b3
and my headphone connection woes have been solved. I'll attach t
In fact bug #2081384 might be a better duplicate.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2085162
Title:
Bluetooth headphones connect erratically
To manage notifications about this bug go to:
This might be related to bug #2084337 ...
** Changed in: alsa-driver (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2085162
Title:
Bluetooth headphones connect
Looks like this is actually related to bluez in some fashion. Here's what I'm
seeing while running
journalctl -fu bluetooth
Nov 05 21:14:30 lenovo bluetoothd[374859]: src/profile.c:ext_connect()
Hands-Free Voice gateway failed connect to 11:22:33:44:55:66: Connection
refused (111)
Nov 05 21:14:3
** Also affects: bluez (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2085162
Title:
Bluetooth headphones connect erratically
To manage notificat
Public bug reported:
Description of the problem
A pair of Sony Sony WH-H900N Bluetooth headphones often refuses to re-connect
with a Lenovo V15 G2 ALC laptop. These headphones pair without trouble to a
MacBook Pro and an Android phone.
Step to reproduce:
1. Put the headphones into discovery mod
We have seen this on a bionic (18.04) and xenial (16.04) hosts. Does
this definitely not impact focal as well?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1870514
Title:
update containerd:amd64 1.
(For anyone who comes across this one of the upstream issues
(https://github.com/docker/docker-credential-
helpers/issues/103#issuecomment-576854271 ) mentions the problem goes
away if `pass` package is also installed and this seemed to make the
issue disappear for me too)
** Bug watch added: gith
Samba 4.11 (which looks like it will be in 20.04) now defaults the min
protocol to SMB2_02
(https://www.samba.org/samba/history/samba-4.11.0.html )...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1697
** Tags added: bionic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1813003
Title:
Invalid free while running docker build
To manage notifications about this bug go to:
https://bugs.launchpad.net/u
** Tags added: bionic xenial
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1836022
Title:
Cannot start containers after docker.io update
To manage notifications about this bug go to:
https://bugs.l
I think this is documented as not working when you are using systemd in
the file itself:
$ cat /etc/default/docker
$ head -8 /etc/default/docker
# Docker Upstart and SysVinit configuration file
#
# THIS FILE DOES NOT APPLY TO SYSTEMD
#
# Please see the documentation for "systemd drop-ins":
#
Further information:
Doing things like docker stop will hang and won't actually stop the running
container (but won't spit out an error message or exit with a non-zero return
code). docker kill fails to change the state of the system in a similar way.
In my case restarting the docker daemon jus
I've also seen this on multiple machines since yesterday and just like
the reporter the machines are Xenial and Bionic:
>From /var/log/apt.history.log on a Xenial machine:
Commandline: /usr/bin/unattended-upgrade
Install: containerd:amd64 (1.2.6-0ubuntu1~16.04.3, automatic)
Upgrade: apport:amd64
diff --git a/secretservice/secretservice_linux.go
b/secretservice/secretservice_linux.go
index 95a1310..383b0c2 100644
--- a/secretservice/secretservice_linux.go
+++ b/secretservice/secretservice_linux.go
@@ -93,7 +93,7 @@ func (h Secretservice) List() (map[string]string, error) {
var list
I agree with @anatoly.borodin - in fact the commit
https://github.com/docker/docker-credential-
helpers/commit/73e5f5dbfea31ee3b8ebbf189785fa69731c and pull request
https://github.com/docker/docker-credential-
helpers/pull/29/commits/79f93e5e69abc2ead458d19f4577b64b7e35c504 are the
same fix. It
Public bug reported:
Description of the problem:
Running docker build generates a warning that an invalid free was performed.
Steps to reproduce:
sudo apt-get install docker-compose
sudo docker build -f Dockerfile.build
https://github.com/docker-library/hello-world.git
Expected results:
Docke
Public bug reported:
Description of the problem
It appears that cron will go on to crash if it finds a crontab owned by uid who
does not map to a valid user.
Steps to reproduce:
1. Create a crontab with an Active Directory user set up via SSSD?
2. Switch AD domains so user's uid is entirely diff
As predicted 4.11.0-1015-azure #15-Ubuntu doesn't have the problem and
you see output like this:
[ 24.635325] sd 1:0:0:0: Attached scsi generic sg2 type 0
[ 24.638674] sd 1:0:0:0: [sdb] 500118192 512-byte logical blocks: (256 GB/238
GiB)
[ 24.641194] sd 1:0:0:0: [sdb] Write Protect is off
[
Joshua - I'm fairly certain it should be fixed in 4.11 - will reply when
I have a chance.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1679898
Title:
[Hyper-V] Ubuntu VM crash during Hyper-V backup
Perhaps in addition to the DVD fix 4.4 needs a few more of the patches
listed on https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-
stable.git/log/drivers/scsi/storvsc_drv.c?h=v4.9.65 ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed t
I see this issue too. It is easy to get with a 4.4 kernel if you have an
SSD hooked up to the Windows host and then you connect the SSD to the
Hyper-V VM via the SCSI controller in passthrough mode. Error messages
will look like this:
[ 20.476616] sd 3:0:0:0: [sdb] Synchronizing SCSI cache
[ 3
Closer inspection suggests that the glusterfs-common package in 16.04
doesn't have this problem...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1717143
Title:
glusterfs-common depends on architectu
Wild guess: this might be because you have only one network interface
that is set to use DHCP but the DHCP server is set not to return any
routers. See https://github.com/systemd/systemd/issues/3752 for this
type of scenario.
** Bug watch added: github.com/systemd/systemd/issues #3752
https://g
Public bug reported:
Description of the problem:
While trying to install the 32 bit version of glusterfs-common on a 64 bit
system (for testing purposes) on Ubuntu 14.04 on Travis (which only provides 64
bit environments) I ran into the following:
The following packages have unmet dependencies:
@fmyhr:
After grovelling through the fio commits I've come across
https://github.com/axboe/fio/commit/1e7f82e20c088e3f564ad24e37bb873b7ac37d3a
which says old versions of fio had problems reaching compressability
targets with large (above 64k) blocksizes which matches this launchpad
bug's scenario
Lim:
Can you confirm you were using fio-2.2.10 on Ubuntu 16.04)
William:
Since Lim has found this issue in the fio for Ubuntu 14.04 but it appears to be
fixed in the fio for 16.04 how does Lim proceed to close this?
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Something else to bear in mind is that because you aren't using direct=1
(see http://fio.readthedocs.io/en/latest/fio_doc.html#cmdoption-arg-
direct ) there's nothing (other than size) stopping your I/O being
entirely cached in RAM thus creating unrealistically fast speeds. Worse
still, there's a g
Lim:
The output you included says otherwise:
testlog: (g=0): rw=read, bs=4K-4K/4K-4K/4K-4K, ioengine=sync, iodepth=1
fio-2.1.3
I guess the main points are: Can this still be reproduced and if so can
what were the steps? Further, can it still be reproduced with stock fio
on Ubuntu 16.04 or later o
On Ubuntu 16.04 with fio-2.2.10 I cannot reproduce running against the
nullblk device. I doubled up the dashes and ran like so:
modprobe null_blk gb=100
cat < fio-iolog-file
fio version 2 iolog
/dev/nullb0 add
/dev/nullb0 open
/dev/nullb0 read 5898366976 4096
/dev/nullb0 read 72397074432 4096
/de
@zbyszek-in: would you be willing to take patches that upstream refuse?
There's a fix for this via
https://github.com/sitsofe/systemd/commit/ee26c33ede684138ba9fdc7f286bfa402860aff3
but upstream have a clear "no more changes will ever be made to systemd
provided storage udev rules" rule :
https://g
Attach patch to solve PMP attached device persistent naming
** Patch added: "ee26c33ede684138ba9fdc7f286bfa402860aff3.patch"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1611945/+attachment/4874796/+files/ee26c33ede684138ba9fdc7f286bfa402860aff3.patch
--
You received this bug notif
** Summary changed:
- Missing libtalloc2 version dependency
+ Old libtalloc2 version dependency
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1605209
Title:
Old libtalloc2 version dependency
To ma
Closer inspection shows that the problem is the *version* of libtalloc2
installed - the samba packages already have a dependency on libtalloc2 itself
but only require 2.0.4~git20101213 or newer. The problem occurred because the
version of libtalloc wasn't upgraded but Samba seemingly requires it
** Summary changed:
- Missing libtalloc2 dependency
+ Missing libtalloc2 version dependency
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1605209
Title:
Missing libtalloc2 version dependency
To ma
I thought everything in /sys was built by udev rules? If so any path
changes could be down to changes there rather than in the kernel.
http://cdimage.ubuntu.com/daily-live/20160811/ is likely a new yaketty
build but use at your own risk etc.
--
You received this bug notification because you are
I should also note 14.04 live CDs are also available:
http://releases.ubuntu.com/14.04/ .
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1611945
Title:
/dev/disk/by-path not properly populated for (e
A quick search digs up that the path is created by this:
https://github.com/systemd/systemd/blob/09541e49ebd17b41482e447dd8194942f39788c0/src/udev/udev-builtin-path_id.c#L349
. This code in that region was added in
https://github.com/systemd/systemd/commit/ba86822db70d9ffd02ad78cd02b237ff8c569c7a
I guess it would also be good to have the same output for different disk
in the same enclosure...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1611945
Title:
/dev/disk/by-path not properly populate
Chris:
Could you attach the output of
sudo udevadm test /sys/class/block/sda
?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1611945
Title:
/dev/disk/by-path not properly populated for (e)SATA port
Just a quick note: using
sudo -s
or
su -
before using service will work around the issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1605290
Title:
Please add --system to initctl calls from servi
Adding patch that always uses the system upstart session.
** Patch added: "initctl-system.patch"
https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/1605290/+attachment/4704733/+files/initctl-system.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, whic
Public bug reported:
Description of the problem:
If the user is using the service command they are almost certainly trying to
control system daemons but can wind up looking at only user session daemons.
Steps to reproduce:
1. Install KUbuntu 14.04.
2. Graphically log in as a regular user.
3. Run
Others appear to be seeing the same issue too:
https://answers.launchpad.net/ubuntu/+question/291448 .
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1605209
Title:
Missing libtalloc2 dependency
To
Another report of the same problem:
http://askubuntu.com/questions/772730/samba-software-caused-connection-
abort .
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1605209
Title:
Missing libtalloc2 de
Public bug reported:
Description of the problem:
Samba crashes if libtalloc2 is not installed when a share is accessed by a
non-Linux system.
Steps to reproduce:
1. Install KUbuntu 14.04.
2. Get a root terminal up and type
apt-get update
apt-get install samba
3. Add the following to end of /etc/
Further investigation on what I was seeing showed this to be a race
between X starting and the intel i915 graphics kernel module being
loaded (because it's not built into the kernel).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
htt
Attaching partial backtrace.
#0 0xa44e87f4 in seeked_cb (player=0xa4803280, provider=0x2) at
mpris2-provider.c:787
#5 0xa6fcb497 in (instance=0xa4803280, detailed_signal=0x7559f6ec
"seeked") at /build/glib2.0-Spm2To/glib2.0-2.48.0/./gobject/gsignal.c:3481
#1 0xa6fb229c in g_cclosure_mars
This appears to be https://bugs.freedesktop.org/show_bug.cgi?id=94677
...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1568604
Title:
Mouse cursor lost when unlocking with Intel graphics
To manage
** Attachment added: "auth.log"
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1250875/+attachment/4645857/+files/auth.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1250875
Title:
Li
** Attachment added: "lightdm.log"
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1250875/+attachment/4645856/+files/lightdm.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1250875
Title
I've just seen this on Ubuntu 16.04 on an EeePC and in one start up
configuration it always happens and autologin always fails.
It seems to be highly dependent on what else is happening as lightdm is
starting. When the problem occurs looking at the lightdm log shows that
it is trying to log using
Changing component to cups-filters.
** Package changed: lsb (Ubuntu) => cups-filters (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1573893
Title:
Can't use Epson XP-310 printer with 16.04
Till: Could you undo fixed released on cups-filters? It looks like the
cups-filters-lsb has already been deleted
(http://www.ubuntuupdates.org/package/core/xenial/main/base/cups-
filters-lsb ) but the epson debs still depend on lsb which doesn't
exist.
--
You received this bug notification becaus
Looking closer this sounds like a duplicate of bug #1536353 ...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1573893
Title:
Can't use Epson XP-310 printer with 16.04 no lsb
To manage notifications
Changing component. I'm also seeing this on 16.04 trying to use a
WF-3520 printer - it learns about the epson-inkjet-printer-201212w deb
from Epson but the deb can't be installed because xenial no longer has
an lsb package:
# apt-get install epson-inkjet-printer-201212w
Reading package lists... Do
Chris Leach started posted patches that would fix some of what is needed
to support this on open-iscsi mailing list
(https://groups.google.com/d/msg/open-iscsi/vWbi_LTMEeM/P8-oUDkb14YJ )
but they stalled and are incomplete (https://groups.google.com/d/msg
/open-iscsi/kgjck_GixsM/U_FqTbYhCgAJ ).
--
This isn't an error only an informational message:
http://unix.stackexchange.com/a/244150/134856 .
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1271430
Title:
dm-0: WRITE SAME failed. Manually zero
I don't see this in Ubuntu 14.04 as it uses SNA and UXA is going to die
so I think we can finally close this.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/745608
Title:
[915GM] font corruption on I
Screenshots and logs for linux.testing.mara...@gmail.com are on a system running
Kernel 3.11.0-12-generic #19-Ubuntu
xorg-intel 2:2.99.904-0ubuntu2
SNA is on: intel(0): SNA initialized with Eaglelake (gen4.5) backend
Chipset is a Q45/Q43.
linux.testing.marantz:
I've add you to the CC list of this
1 - 100 of 3157 matches
Mail list logo
