Public bug reported:
As demonstrated in the attached screenshot (taken in Ubuntu 15.04),
there appears to be too little space between the day and the time. The
"1" looks at first glance to be part of the time.
** Affects: indicator-datetime (Ubuntu)
Importance: Undecided
Status:
I am dealing with the same flickering issue as described above, and am
using the same hardware. If there is any information I can provide,
please let me know.
Casey
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg
I would like to note that this is still/again a problem in 2019 on
Ubuntu 19.04. (I didn't notice it on 18.10, but maybe I just missed
it.) I agree with pretty much everything that gdi2k wrote above,
particularly that the following seemingly simple change would remove a
significant annoyance for
Thanks for following up. Here it is.
** Attachment added: "mountinfo"
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1915091/+attachment/5462047/+files/mountinfo
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in
Could it be relevant that /var/snap is a bind-mount? To clarify, I have
a relatively small root partition and a large data partition, and bind-
mount various directories that require a lot of space -- like /var/snap,
/var/lib/snapd, /home -- from the data partition.
--
You received this bug
Hello: This affects my server(s), 14.04.2 LTS. In fact I just logged in
and got information that was 11 days old. I rely on the welcome message
especially to tell me when I need to REBOOT for some automatically-
installed (perhaps security) updates to be fully applied. Perhaps a
wiser sysadmin
I also get this same issue (I have the Dell XPS 15 too, as David White
above - it's the 9530 model). UI Scaling is set to 2x and looks fine
everywhere except the cursor. Cursor is correct size in Google Chrome
however as reported above. The workaround of restarting unity works, but
is not ideal.
Public bug reported:
The issue is as described in the summary. My device is now working fine,
however this fix is clearly some sort of bug, so I figured it would be
helpful to report. If someone feels like working on it and wants any log
files just let me know! Not sure what would actually be
This is what I've got installed ^^
c@mawhrin-skel:~/omnibus-layers$ dpkg -l | grep pcscd
ii pcscd 1.8.14-1ubuntu1
amd64Middleware to access a smart card using PC/SC
(daemon side)
--
You received this bug notification
Public bug reported:
In xenial, pcscd CPU utilization occasionally goes haywire:
PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND
?
Anything else I can do to help?
Thanks,
Casey
[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812087
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pcsc-lite in Ubuntu.
https://bugs.launchpad.net/bugs/1551897
Title
It starts consuming 100% CPU after this:
02341452 hotplug_libudev.c:642:HPEstablishUSBNotifications() USB Device removed
0217 hotplug_libudev.c:619:HPEstablishUSBNotifications()
0068 hotplug_libudev.c:642:HPEstablishUSBNotifications() USB Device removed
0149
Oh, here's /var/log/syslog from unplugging and replugging in my camera.
I Ctrl-C killed pcscd after it went to 100% each time.
pcscd segfaulted.
Mar 4 12:04:11 mawhrin-skel pcscd: debuglog.c:289:DebugLogSetLevel() debug
level=debug
Mar 4 12:04:13 mawhrin-skel kernel: [14604.513268] usb 3-1:
Ran it with gdb, reproduced, and then interrupted when it started
consuming 100% CPU:
Thread 1 "pcscd" received signal SIGINT, Interrupt.
0x774e2853 in select () from /lib/x86_64-linux-gnu/libc.so.6
(gdb) bt
#0 0x774e2853 in select () from /lib/x86_64-linux-gnu/libc.so.6
#1
Recompiling with --disable-libudev gets rid of the 100% CPU problem and
I can still use my smartcard.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pcsc-lite in Ubuntu.
https://bugs.launchpad.net/bugs/1551897
Title:
I ran pcscd as you suggested, capturing output. Made sure the smart card
was working by using my SSH key. I was then able to reproduce the 100%
cpu condition by plugging in my Logitech USB webcam.
Attached the output, but I redacted the hex dumps before posting here
because I'm not sure if they
** Attachment added: "pcscd binary and core dump"
https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/1551897/+attachment/4588521/+files/pcscd-core-bin.tar.bz2
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
Here's a core dump with the corresponding pcscd binary I built from
source, which was taken in the above-mentioned gdb session.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pcsc-lite in Ubuntu.
I'm not seeing the symbolic links error, but I am seeing this when
trying to start a trusty container on xenial:
https://github.com/lxc/lxd/issues/1836
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
When is this going to be fixed upstream? I'm having to remount on the
host and restart containers quite often. I can't imagine this will be a
good user experience for new LXD users on xenial.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
Still seeing this on xenial enough that I've written a script to perform
the umounting when LXD gets stuck. Do I even need binfmt_misc on my
system? Can I just remove it or would that break something?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
I apt purge'ed binfmt-support from my system and I'm still able to
comment here :) We'll see if this fixes the issue.
If it does, why was it even installed on my system by default to begin
with?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
For any poor soul who wanders here, here is the best known workaround
for this issue I've seen to date:
22-09-2016 15:23:18 < stgraber!~stgraber@ubuntu/member/stgraber: cmars:
if you mask (systemctl mask) the systemd units related to binfmt
(systemctl -a | grep binfmt) and reboot, then the
nicely researched and documented bug. Why not fixed three years later? I
hit this (or seeminly this same bug) doing an install of server 18.04.2
yesterday. I needed to enable ssh for remote install and lowered debconf
priority. This gave me some good clues I'll now try some work-arounds.
--
You
Public bug reported:
After upgrading to 20.04 I decided to remove packages that I don't need
or use.
I was surprised to find that mysql client, server and common packages
were installed, as I could not remember having installed mysql -- I
don't use it or develop for it...
When I removed them,
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-6236
--
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/962082
Title:
Profiles that require duplex audio like
Public bug reported:
While investigating a potentially compromised system, I ran `bash
--version` and got the following:
`GNU bash, version 4.4.20(1)-release (x86_64-pc-linux-gnu)`
Disquieting, given that I had just installed a package named
`bash_4.4.18-2ubuntu1.3_amd64.deb`. I downloaded the
Public bug reported:
I've encountered this issue on several fresh installations of Ubuntu
16.04.1 on different machines. Typically, the machine becomes
unresponsive to the keyboard presses or to mouse clicks; however, it
does respond to mouse movement. I am unable to open a text console to
I am getting the same issue, same error. Crashes once I reach the
progress screen of 18.04 installation.
Syslog report:
..
Apr 28 20:26:54 ubuntu localechooser: info: Set debian-installer/locale =
'en_CA.UTF-8'
Apr 28 20:26:54 ubuntu localechooser: info: System locale
29 matches
Mail list logo