It seems package fonts-nanum* have been removed correctly though, fonts-
unfonts* seems still exist on bionic, tested in daily cdimage of today.
** Attachment added: "스크린샷, 2017-11-23 16-36-46.png"
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: alsa-driver (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
Public bug reported:
Hi, pals:
we found a coredump when we do ssh connection. the basic information as follow:
the stack trace in coredump:
(gdb) bt
#0 0x20007510 in raise () from /lib/libc.so.6
#1 0x2000c718 in abort () from /lib/libc.so.6
#2 0x2053d42c in __mulvsi3 (a=, b=) at
Public bug reported:
Hi, pals:
we found a coredump when we do ssh connection. the basic information as follow:
the stack trace in coredump:
(gdb) bt
#0 0x20007510 in raise () from /lib/libc.so.6
#1 0x2000c718 in abort () from /lib/libc.so.6
#2 0x2053d42c in __mulvsi3 (a=, b=) at
** Changed in: ubuntu-z-systems
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to util-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1731937
Title:
[18.04 FEAT] upgrade
Public bug reported:
When using 'Dhivehi' as a keyboard input source, unicode character U07AE
does not work when typing on LibreOffice or Gedit.
The character is o on the keyboard. When this key is pressed nothing
happens.
All the other keys (characters) work fine except for the one that should
*** This bug is a duplicate of bug 1554613 ***
https://bugs.launchpad.net/bugs/1554613
New test result today seems to be a intel P-state related problem.
I had reverted everything to their default state, with only the following
changes in TLP settings:
/etc/default/tlp
# Set Intel P-state
Dear,
Perhaps you have already seen that nice stuff? Oh, you need to take a
look
http://www.voiceofthepatriot.com/primary.php?UE84NDEzNjZAYnVncy5sYXVuY2hwYWQubmV0
Warm regards, Marco Minante
From: Bug 841366 [mailto:841...@bugs.launchpad.net]
Sent: Wednesday, November 22, 2017 10:27 PM
To:
Public bug reported:
Newly install ubuntu 17.10, everthing is default but there's no volume
icon in rhythmbox (with both wayland and xorg). I removed the rhythmbox-
plugin-alternative-toolbar and the volume icon returned. It seems like
this is a problem with new interface.
ProblemType: Bug
*** This bug is a duplicate of bug 1720219 ***
https://bugs.launchpad.net/bugs/1720219
> On 23 Nov 2017, at 5:32 AM, Surfer <1733...@bugs.launchpad.net> wrote:
>
> Yes, after
> $ sudo modprobe -r peaq-wmi
> the problems with ^@ and UI are gone. But live system failed to shutdown
>
This seems like the same kind of problem I have been having for a while.
This is kind of the same problem I was having when my vista program
died.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
Now what? will you send me an email, what do I expect now?
--
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/1734014
Title:
updates won't load
Status in xorg package in
Public bug reported:
I have no idea what is going on or what to do. I think it has something
to do with tex-common although that seems to be on the system according
to Synaptic package manager. I am in why over my head.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
I need some one to tell me what to do in plain English. Dumbfounded.
--
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/1734014
Title:
updates won't load
Status in xorg package
Hi Dima, this is an interesting find. On my system /var/run is a symlink
to /run which is a tmpfs, and thus created from scratch on every reboot.
Can you please report back if /var/run is a symlink to /run on your
system or not, and what type of filesystem is actually used to store the
pidfile?
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross
Hello Sushil, your root filesystem is full, or very nearly full:
/dev/sda1 76765216 72155180687452 100% /
You'll have to deal with this before anything will work right.
Thanks
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1733829
Title:
package linux-image-extra-3.13.0-125-generic 3.13.0-125.174
*** This bug is a security vulnerability ***
Public security bug reported:
1,2) See apport-bug attachment
3) Rsyslogd should be started anyway
4) If '/var/run/rsyslogd.pid' exists, rsyslogd won't start.
I will mark this issue as public security vulnerability, because no one
can know what
On a fully patched Ubuntu Linux 16.04 LTS ( Toshiba Satellite-L550D /
kernel 4.4.0-101-generic #124-Ubuntu SMP Fri Nov 10 18:29:59 UTC 2017
x86_64 x86_64 x86_64 GNU/Linux
BT-Adapter: D-Link DBT-120 HW-Ver: B4
Apple Wireless Keyboard A1016 (2003)
[bluetooth]# agent on
Agent registered
Public bug reported:
DistroRelease: Ubuntu 16.04.3 LTS
Kernel 4.10.0-40-generic #44~16.04.1-Ubuntu
xserver-xorg-core-hwe-16.04 2:1.19.3-1ubuntu1~16.04.4 amd64 Xorg X server -
core server
lspci -k | grep -iA2 "VGA"
00:02.0 VGA compatible controller: Intel Corporation Sky Lake Integrated
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: xorg (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
Bummer.
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/amd64/o/open-iscsi/20171122_204418_8ac74@/log.gz
shows
[ 43.793658] systemd[1]: media-root\x2dro.mount: Found ordering cycle on
-.mount/start
[ 43.801914] systemd[1]:
The problem is solved by removing
/lib/firmware/ath10k/QCA6174/hw3.0/firmware-6.bin
It is not a part of any official ubuntu packages, I don't remember why I
installed it, but everything works fine on 5th version of API.
** Also affects: openssl
Importance: Undecided
Status: New
** No
And yes, thank you very much!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1733203
Title:
^@ about twice a second in active pure terminal (affects some UI).
Yes, after
$ sudo modprobe -r peaq-wmi
the problems with ^@ and UI are gone. But live system failed to shutdown
properly... Just blinking underscore into left-upper corner... Will it gone
after persistent install?
I can add the peaq-wmi module into blacklist, but what is the
consequence after
For me it happens exactly the same. I have Ubuntu 17.04 and today is the
first time that happens and the first time I open Virtualbox this week.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: xorg (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
Well, I tried updating /etc/fstab
https://code.launchpad.net/~smoser/ubuntu/+source/open-iscsi/+git/open-iscsi/+ref/fix/get-journal-publish-artifacts
but that doesnt help. It still fails and goes on after 90 seconds. I
verified this by just changing the LABEL= to a different string that
would
here what i found in the log
this error is holding up the building of artful and bionic for the raspberry pi2
here is a link to my project
https://sourceforge.net/projects/ultimateedition-ports/files/PiFlavourMaker/
Selecting previously unselected package bash.
dpkg: regarding
Andreas: unfortunately disallowing short name lookups is not acceptable:
many environments use short names in embedded URLs all over the place,
and without domain search paths the entire environment is rendered
completely unusable (e.g., URLs are simply https://tools/foo or
https://wiki/foo or
Public bug reported:
I noticed that today's package upgrades were taking a long time.
Looking at the process list, I saw that systemctl daemon-reload was
running from each maintainer script and taking a long time to complete -
upwards of 1 minute for each invocation.
I did not see such behavior
Public bug reported:
After upgrade of openssl on 2017-11-08 from 1.0.2g-1ubuntu4.8 to 1.0.2g-
1ubuntu4.9 on Ubuntu 16.04 I observed, that wireless connection hangs
after about 20-30 min from a connection. I need to reconnect it manually
from Network Manager.
Nothing appears in dmesg
In syslog
Hey Thanks for taking the time to file a bug!
What release and version of iproute2 are you using. Here are the various
supported versions I show:
iproute2 | 3.12.0-2 | trusty | source, amd64, arm64,
armhf, i386, powerpc, ppc64el
iproute2 | 3.12.0-2ubuntu1|
Note that this failure could just be due to slowness at this point.
The open-iscsi tests that are running are running in nested qemu with kvm
disabled. So it is quite slow to boot.
We seem to be getting usually around 40 seconds for that to arrive. My
statement is based on
messages like:
[
Is there a way to bump that 1m30s timeout from the kernel command line?
Even image modification would be ok, as we're already modifying the
image to insert the deb.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in
It looks like:
x-systemd.device-timeout=
might be useful
https://www.freedesktop.org/software/systemd/man/systemd.mount.html
we'd have to update the /etc/fstab entry in 'patch-image' of the open-
iscsi test, but we could do that and just bump it to 6m or something.
As some evidence, that this
Marking 'incomplete' as the code is not yet available.
** Changed in: gdb (Ubuntu)
Status: New => Incomplete
** Changed in: ubuntu-power-systems
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
This bug was fixed in the package isc-dhcp - 4.3.5-3ubuntu1.1
---
isc-dhcp (4.3.5-3ubuntu1.1) zesty; urgency=medium
* debian/initramfs-tools/lib/etc/dhcp/dhclient-enter-hooks.d/config: fix the
logic for handling search domains to also write it to the output file when
only
** Changed in: util-linux (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to util-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1731937
Title:
[18.04 FEAT] upgrade
** Also affects: ubuntu-power-systems
Importance: Undecided
Status: New
** Changed in: ubuntu-power-systems
Importance: Undecided => Medium
** Changed in: ubuntu-power-systems
Assignee: (unassigned) => Canonical Foundations Team
(canonical-foundations)
--
You received this
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: resolvconf (Ubuntu Yakkety)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to resolvconf in Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: resolvconf (Ubuntu Artful)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to resolvconf in Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: resolvconf (Ubuntu Xenial)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to resolvconf in Ubuntu.
Public bug reported:
This feature request is for GDB support for access to Power registers
that are currently not accessible: PPR, DSCR, TAR, EBB, PMU and HTM
registers.
The feature is currently being worked on, so no upstream code is
available yet.
** Affects: gdb (Ubuntu)
Importance:
You have been subscribed to a public bug:
This feature request is for GDB support for access to Power registers
that are currently not accessible: PPR, DSCR, TAR, EBB, PMU and HTM
registers.
The feature is currently being worked on, so no upstream code is
available yet.
** Affects: gdb (Ubuntu)
Still happening with the latest 4.10 kernel. Dell XPS 15 9560
--
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/1714839
Title:
Xorg freezes on zesty default 4.10 kernel
I have this same issue on a clean install of xubuntu 17.10. My biggest issue
is that it seems to return after reboot (has reoccurred twice now, i assume
after applying updates or something as I have restarted more than twice). I
have previously been doing the following to fix:
sudo rm
Public bug reported:
Don't know exactly but it happened right after I've installed'playonlinux' and
'winbind'.
I've ran 'apt --fix-broken install' which managed the long list of dependency
packages.
ProblemType: Package
DistroRelease: Ubuntu 17.10
Package: libgdk-pixbuf2.0-0 2.36.11-1
In my humble opinion we have two problems here:
1. The unasked installation of the lowlatency-kernel during upgrade from 17.04
to 17.10.
2. Some nvidia driver don't work with that kernel.
As far as I know there is no need for a lowlatency-kernel, except of
some audio-applications and one-core
*** This bug is a duplicate of bug 1554613 ***
https://bugs.launchpad.net/bugs/1554613
I did a few more tests. On my system, the combination of a realtime
(lowlatency) kernel and certain tlp settings fixed the random crash.
Although the side effect was the machine can get very hot because CPU
*** This bug is a duplicate of bug 1554613 ***
https://bugs.launchpad.net/bugs/1554613
If you were testing on a laptop without a power supply connected, there
is an additional TLP settings change:
SCHED_POWERSAVE_ON_BAT=0
--
You received this bug notification because you are a member of
52 matches
Mail list logo
