Thanks Christian for your detailed responses. After reading through
those links I do agree that it makes the most sense to only autostart
once as it is designed. I do think though that a failed autostart
attempt shouldn't be considered an autostart and create the file but as
you mentioned I don't t
Public bug reported:
If a libvirt network is set to autostart and upon boot there is an issue
starting the network, the file located at
/run/libvirt/network/autostarted is not removed. Thus, the network will
never autostart again if the libvirt service is restarted. This was
observed due to the ne
Public bug reported:
Went to run updates and error said I didn't have enough source
repositories, or they were busy. Try again later.
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: ubuntu-release-upgrader-core 1:24.04.22 [origin: unknown]
ProcVersionSignature: Ubuntu 6.8.0-48.48-generic 6.
Our wide-ranging media presence across several platforms guarantees that we
provide innovative, high-impact marketing solutions that provide value for our
partners.
https://africa.businessinsider.com/local/10-best-csgo-gambling-sites-top-cs2-gamble-websites/5shlqfl
--
You received this bug noti
Our top priority is the safety and well-being of our community, and we are
committed to offering comprehensive support to those who have experienced
damage from Eat-and-Run incidents.
https://www.toto-system.com/
--
You received this bug notification because you are a member of Ubuntu
Bugs, wh
Public bug reported:
Description:Ubuntu 22.04.4 LTS
Release:22.04
~$ apt-cache policy pkgname
N: Unable to locate package pkgname
I get the what seems to be a permanent message: "Software catalog is
being downloaded"
Seems to me that something has gone wrong as Ubuntu tried to
autom
+1 makes sense. Thanks for doing this validation @chris.macnaughton
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1883112
Title:
rbd-target-api crashes with python TypeError
To manage notifications
I've filed https://bugs.launchpad.net/charm-mysql-router/+bug/1973177 is
track this seperatly
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1907250
Title:
[focal] charm becomes blocked with workload
One of the causes of a charm going into a "Failed to connect to MySQL"
state is that a connection to the database failed when the db-router
charm attempted to restart the db-router service. Currently the charm
will only retry the connection in response to one return code from the
mysql. The return
Are you saying it is in 22.04? I thought I read it was not in it.
Richard Young
Virtualization and Linux Lead
Executive IT Specialist
IBM Systems Lab Services
[2D barcode - encoded with contact information] Mobile:
1-262-893-8662
E-mail:ryou...@us.ibm.com
Public bug reported:
[Impact]
* ceph-iscsi on Focal talking to a Pacific or later Ceph cluster
* rbd-target-api service fails to start if there is a blocklist
entry for the unit.
* When the rbd-target-api service starts it checks if any of the
ip addresses on the machine it is running o
*** This bug is a duplicate of bug 1883112 ***
https://bugs.launchpad.net/bugs/1883112
** This bug has been marked a duplicate of bug 1883112
rbd-target-api crashes with python TypeError
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Public bug reported:
While testing using openstack, guests failed to launch and these denied
messages were logged:
[ 8307.089627] audit: type=1400 audit(1649684291.592:109):
apparmor="DENIED" operation="mknod" profile="swtpm"
name="/run/libvirt/qemu/swtpm/11-instance-000b-swtpm.sock"
pid=1412
** Patch added: "ceph-iscsi-deb.diff"
https://bugs.launchpad.net/ubuntu/+source/ceph-iscsi/+bug/1965280/+attachment/5569987/+files/ceph-iscsi-deb.diff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/
Verification on impish failed due to
https://bugs.launchpad.net/ubuntu/+source/ceph-iscsi/+bug/1965280
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1883112
Title:
rbd-target-api crashes with python
Public bug reported:
The rbd-target-api fails to start on Ubuntu Impish (21.10) and later.
This appears to be caused by a werkzeug package revision check in rbd-
target-api. The check is used to decide whather to add an
OpenSSL.SSL.Context or a ssl.SSLContext. The code comment suggests that
ssl.SS
Tested successfully on focal with 3.4-0ubuntu2.1
Tested with ceph-iscsi charms functional tests which were previously
failing.
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 20.04.4 LTS
Release:20.04
Codename: focal
$ apt-cache policy c
** Patch added: "gw-deb.diff"
https://bugs.launchpad.net/ubuntu/+source/ceph-iscsi/+bug/1883112/+attachment/5569162/+files/gw-deb.diff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1883112
Title:
Thank you for the update Robie. I proposed the deb diff based on the fix
that had landed upstream because I (wrongly) thought that was what the
SRU policy required. I think it makes more sense to go for the minimal
fix you suggest.
--
You received this bug notification because you are a member of
** Description changed:
+ [Impact]
+
+ * rbd-target-api service fails to start if there is a blocklist
+entry for the unit making the service unavailable.
+
+ * When the rbd-target-api service starts it checks if any of the
+ip addresses on the machine it is running on are listed as
+
** Patch added: "deb.diff"
https://bugs.launchpad.net/ubuntu/+source/ceph-iscsi/+bug/1883112/+attachment/5562748/+files/deb.diff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1883112
Title:
rbd-
** Changed in: ceph-iscsi (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1883112
Title:
rbd-target-api crashes with python TypeError
To manage notifications
Public bug reported:
Failed to stop timidity.service: Unit timidity.service not loaded.
invoke-rc.d: initscript timidity, action "stop" failed.
dpkg: error processing package timidity-daemon (--configure):
installed timidity-daemon package post-installation script subprocess returned
error exit
s/The issue appears when using the mysql to/The issue appears when using
the mysql shell to/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1954306
Title:
Action `remove-instance` works but appears t
I don't think this is a charm bug. The issue appears when using the
mysql to remove a node from the cluster. From what I can see you cannot
persist group_replication_force_members and is correctly unset. So the
error being reported seems wrong
https://pastebin.ubuntu.com/p/sx6ZB3rs6r/
root@juju-1
** Also affects: mysql-8.0 (Ubuntu)
Importance: Undecided
Status: New
** Changed in: charm-mysql-innodb-cluster
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/19
Perhaps I'm missing something but this does not seem to be a bug in the
rabbitmq-server charm. It may be easier to observe there but the root
cause is elsewhere.
** Changed in: charm-rabbitmq-server
Status: New => Invalid
--
You received this bug notification because you are a member of U
Tested successfully on focal victoria using 1:11.0.0-0ubuntu1~cloud1 . I
created an encrypted volume and attached it to a VM.
cinder type-create LUKS
cinder encryption-type-create --cipher aes-xts-plain64 --key_size 512
--control_location front-end LUKS nova.volume.encryptors.luks.LuksEncryptor
c
Tested successfully on focal wallaby using 2:12.0.0-0ubuntu2~cloud0 . I
created an encrypted volume and attached it to a VM.
cinder type-create LUKS
cinder encryption-type-create --cipher aes-xts-plain64 --key_size 512
--control_location front-end LUKS nova.volume.encryptors.luks.LuksEncryptor
c
Tested successfully on hirsute using 2:12.0.0-0ubuntu2 . I created an
encrypted volume and attached it to a VM.
cinder type-create LUKS
cinder encryption-type-create --cipher aes-xts-plain64 --key_size 512
--control_location front-end LUKS nova.volume.encryptors.luks.LuksEncryptor
cinder create
: charm-layer-ovn
Status: New => Confirmed
** Changed in: charm-layer-ovn
Importance: Undecided => High
** Changed in: charm-layer-ovn
Assignee: (unassigned) => Liam Young (gnuoy)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subs
** Changed in: charm-neutron-gateway
Assignee: (unassigned) => Liam Young (gnuoy)
** Changed in: charm-neutron-gateway
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchp
** Changed in: charm-neutron-gateway
Status: Invalid => Confirmed
** Changed in: neutron (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1944424
Titl
A patch was introduced [0] "..which sets the backup gateway
device link down by default. When the VRRP sets the master state in
one host, the L3 agent state change procedure will
do link up action for the gateway device.".
This change causes an issue when using keepalived 2.X (focal+) which
is fix
** Also affects: neutron (Ubuntu)
Importance: Undecided
Status: New
** Changed in: neutron (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/1943863
Title
Fixed in Ubuntu 20.04! You just need to add a link-scope route for your
gateway, as documented: https://netplan.io/examples/#reaching-a
-directly-connected-gateway
network:
ethernets:
ens3:
dhcp4: true
addresses: [ "2602:ff75:7:34fd::/128" ]
routes:
- to: "2602:ff75
I rebuilt the snd-usb-audio module with the linked patch and it does
indeed fix the problem for me. The patch addresses bugs that make all
USB audio devices totally unusable, and is a definite regression in
5.10.0-1017.18:
1. For devices with no quirks, you get a null pointer dereference when you
I have tested the rocky scenario that was failing for me. Trilio on
Train + OpenStack on Rocky. The Trilio functional test to snapshot a
server failed without the fix and passed once python3-oslo.messaging
8.1.0-0ubuntu1~cloud2.2 was installed and services restarted
** Tags removed: verification-r
Public bug reported:
"Install RELEASE" Icon appeared and persisted on the dock after a fresh
install of Ubuntu 20.10. The system is dual booting with Windows 10.
ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: ubiquity 20.10.13.1
ProcVersionSignature: Ubuntu 5.8.0-44.50-generic 5.8.18
Unam
Public bug reported:
It seems that updating the role attribute of a connection has no affect
on existing connections. For example when investigating another bug I
needed to disable rbac but to get that to take effect I needed to either
restart the southbound listener or the ovn-controller.
fwiw t
Public bug reported:
When using Openstack Ussuri with OVN 20.03 and adding a floating IP
address to a port the ovn-controller on the hypervisor repeatedly
reports:
2021-03-02T10:33:35.517Z|35359|ovsdb_idl|WARN|transaction error:
{"details":"RBAC rules for client
\"juju-eab186-zaza-d26c8c079cc7-
Public bug reported:
wayland was installed as a dependancy, tried to fix manually, had to
reinstall kubuntu from scratch, now firmware is out of date
ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: ubiquity 20.10.13 [modified:
lib/partman/automatically_partition/question]
ProcVersionSignat
I have tested the package in victoria proposed (0.3.0-0ubuntu2) and it
passed. I verified it by deploying the octavia charm and running its
focal victoria functional tests which create an ovn loadbalancer and
check it is functional.
The log of the test run is here:
https://openstack-ci-
reports.u
I have tested the package in groovy proposed (0.3.0-0ubuntu2) and it
passed. I verified it by deploying the octavia charm and running its
groovy victoria functional tests which create an ovn loadbalancer and
check it is fuctional.
The log of the test run is here:
https://openstack-ci-
reports.ubu
https://code.launchpad.net/~gnuoy/ubuntu/+source/ovn-octavia-
provider/+git/ovn-octavia-provider/+merge/397023
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1896603
Title:
ovn-octavia-provider: Cann
** Description changed:
- Kuryr-Kubernetes tests running with ovn-octavia-provider started to fail
- with "Provider 'ovn' does not support a requested option: OVN provider
- does not support allowed_cidrs option" showing up in the o-api logs.
+ [Impact]
- We've tracked that to check [1] getting
** Also affects: ovn-octavia-provider (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/1896603
Title:
ovn-octavia-provider: Cannot create listener d
I have tested focal and groovy and is only happening on groovy. I have
not tried Hirsute.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1904199
Title:
[groovy-victoria] "gwcli /iscsi-targets/ create
I don;t think this is a charm issue. It looks like an incompatibility
between ceph-isci and python3-werkzeug in groovy.
# /usr/bin/rbd-target-api
* Serving Flask app "rbd-target-api" (lazy loading)
* Environment: production
WARNING: This is a development server. Do not use it in a production
I've submitted a PR
https://lore.kernel.org/linux-media/20210102101209.ga32...@gofer.mess.org/T/#t
This has to be merged by Mauro (linux-media). Then Linus has to merge it.
Finally, it needs to be merged into the stable tree. So it may be some time.
--
You received this bug notification because
I am using Ubuntu 20.04.1 LTS 64 bit on an Intel mobile CPU and Gnome
3.36.8 (Kernel 5.4.0-58-generic).
irqbalance is still installed by default.
The frequently used Gnome Extension "cpufreq" shows a permanent warning
that irqbalance is active.
If I uninstall irqbalance the warning is gone.
Sin
Thank you @wesnewell and @kaihengfeng for testing this!
Now that we know the patch works, I'll send the patch upstream and it'll
be included in the stable kernels as well.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.l
Thanks for that.
It seems very possible that this issue is solved by this patch:
https://patchwork.linuxtv.org/project/linux-
media/patch/20201221091929.26504-1-s...@mess.org/
Would you be able to test this patch please? There are instructions for
compiling the kernel here.
https://wiki.ubuntu.c
Thanks for that. It looks like on 5.8.8 it has not loaded the rc keymap
at all. It looks like a default mce keymap with the default rc-6
protocol enabled.
So for some reason /etc/rc_map.cfg did not get processed at all. That's
super odd. Let's try and see what udevd does when you plug in the
devi
Actually you said "on newer systems it does not enable the nec
protocol". That is odd.
what is the output of ir-keytable on newer (broken) systems?
also what is the kernel config on broken systems (not sure how to see that on
ubuntu)
--
You received this bug notification because you are a membe
Thank you for that.
With evtest I mean the evtest tool from the evtest package:
https://packages.ubuntu.com/focal/evtest
when you run ir-keytable there is an line which says "Input device:
/dev/input/event..". Use that as an argument to evtest:
evtest /dev/input/event19
There will be some outpu
Hello, the author of those commits here. It's not clear to me how those
commits broke things. Either something else changed, or there is
something subtle going on.
The following bits of information would be very useful.
1. Is the issue intermittent or consistent, i.e. does booting with a new kern
Public bug reported:
No idea what or where the crash occurred,
ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: ubiquity 20.10.13
ProcVersionSignature: Ubuntu 5.8.0-1006.9-raspi 5.8.14
Uname: Linux 5.8.0-1006-raspi aarch64
ApportVersion: 2.20.11-0ubuntu50
Architecture: arm64
CasperMD5CheckRe
Public bug reported:
The install crashed.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: ubiquity 20.04.15.2
ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
Uname: Linux 5.4.0-42-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubun
Public bug reported:
I have turned off Hypervisor platform in Windows 10 before attempting
the VM installation.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ubiquity 18.04.14.15
ProcVersionSignature: Ubuntu 5.4.0-42.46~18.04.1-generic 5.4.44
Uname: Linux 5.4.0-42-generic x86_64
ApportVer
none
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1551599
Title:
Remove button missing after package installation
To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpa
none
** Changed in: hundredpapercuts
Assignee: (unassigned) => Lawrence Young (lorenzojoven)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1551599
Title:
Remove button missing after pack
Still having this issue on a Dell OptiPlex 9020, with 2 monitors
connected using DisplayPort > DVI adapters. Not sure if that's
contributing to the issue though.
Computer boots fine when 1 screen is connected, hangs on the ubuntu
splash screen when a cold boot is performed, however curiously boots
Yep thats the traceback I'm seeing.
Charm shows:
2020-06-10 12:45:57 ERROR juju-log amqp:40: Hook error:
Traceback (most recent call last):
File
"/var/lib/juju/agents/unit-masakari-0/.venv/lib/python3.6/site-packages/charms/reactive/__init__.py",
line 74, in main
bus.dispatch(restricted=r
It seems sqlalchemy-utils may have been removed recently in error
https://git.launchpad.net/ubuntu/+source/masakari/tree/debian/changelog?id=4d933765965f3d02cd68c696cc69cf53b7c6390d#n3
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
ht
Public bug reported:
Package seems to be missing a dependency on sqlalchemy-utils *1. The
issue shows itself when running masakari-manage with the new 'taskflow'
section enabled *2
*1
https://opendev.org/openstack/masakari/src/branch/stable/ussuri/requirements.txt#L29
*2 https://review.opendev.o
Actually I was able to make it work! I needed to remove
"options snd-hda-intel dmic_detect=0"
from /etc/modprobe.d/alsa-base.conf
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1840725
Title:
Micro
This does not work for me. My Hardware Devices were listed as follows
List of CAPTURE Hardware Devices
card 0: PCH [HDA Intel PCH], device 0: ALC285 Analog [ALC285 Analog]
Subdevices: 0/1
Subdevice #0: subdevice #0
Added to line to /etc/modprobe.d/alsa-base.conf and my internal mic
I have the hp spectre x360 13 convertible and the update to 20.04 did
not work for me either.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1840725
Title:
Microphone not working in Ubuntu 18.04.3 LT
HAving looked into it further it seems to be the name of the node that
has changed.
juju deploy cs:bionic/ubuntu bionic-ubuntu
juju deploy cs:focal/ubuntu focal-ubuntu
juju run --unit bionic-ubuntu/0 "sudo apt install --yes crmsh pacemaker"
juju run --unit focal-ubuntu/0 "sudo apt install --yes c
Public bug reported:
Testing of masakari on focal zaza tests failed because the test checks
that all pacemaker nodes are online. This check failed due the
appearance of a new node called 'node1' which was marked as offline. I
don't know where that node came from or what is supposed to represent
bu
The source option was not set properly for the ceph application leading
to the python rbd lib being way ahead of the ceph cluster.
** Changed in: charm-glance
Assignee: Liam Young (gnuoy) => (unassigned)
** Changed in: charm-glance
Status: New => Invalid
** Changed in:
** Also affects: glance (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/1873741
Title:
Using ceph as a backing store fails on ussuri
To manage not
Thank you!
On Sun, Mar 22, 2020 at 11:45 PM Kai-Heng Feng
wrote:
> https://lkml.org/lkml/2020/3/23/29
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1860303
>
> Title:
> Backlight brightness cannot be adjusted using
It works! Keyboard keys adjust brightness and I found no obvious issues
otherwise
dmesg attached for reference
On Fri, Mar 13, 2020 at 1:10 PM Kai-Heng Feng
wrote:
> Can you please test this kernel:
> https://people.canonical.com/~khfeng/lp1860303/
>
> --
> You received this bug notification be
Is this what you need?
On Mon, Mar 9, 2020 at 7:25 AM Kai-Heng Feng
wrote:
> Please test latest drm-tip kernel with kernel parameter "drm.debug=0xe"
> and attach dmesg:
> https://kernel.ubuntu.com/~kernel-ppa/mainline/drm-tip/current/
>
> --
> You received this bug notification because you are s
I got it figured out and the kernel at
https://people.canonical.com/~acelan/bugs/lp1861521/ did not fix the
issue.
On Fri, Mar 6, 2020 at 7:48 PM Jared Young wrote:
> I installed from the .deb files and this did not make a difference for the
> backlight, however the volume keys on the ke
There is another user reporting the same problem with a Samsung 950 Pro
M.2 2280 512gb PCIe 3.0 SSD MZ-V5P512BW:
https://wiki.raptorcs.com/wiki/User:Tle
** Description changed:
I am booting an Ubuntu Server 19.10 image (ubuntu-19.10-live-server-
- ppc64el.iso downloade Jan 18, 2020) on a DVD t
Public bug reported:
I am booting an Ubuntu Server 19.10 image (ubuntu-19.10-live-server-
ppc64el.iso downloade Jan 18, 2020) on a DVD to install Ubuntu on a
RaptorCS Blackbird with an IBM Power9 CPU (ppc64el/ppc64le architecture)
with an Samsung 970 EVO Plus M.2 SSD attached via an PCIe v4 adapte
I installed from the .deb files and this did not make a difference for the
backlight, however the volume keys on the keyboard no longer work.
I am not experienced in testing different kernels so it is possible that I
messed up the install. I did not apply the .patch files.
On Tue, Mar 3, 2020 at
** Summary changed:
- rbd pool name is hardcoded
+ Checks fail when creating an iscsi target
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1864838
Title:
skipchecks=true is needed when deployed on
Public bug reported:
See https://docs.ceph.com/docs/master/rbd/iscsi-target-cli/ and the
line:
"If not using RHEL/CentOS or using an upstream or ceph-iscsi-test
kernel, the skipchecks=true argument must be used. This will avoid the
Red Hat kernel and rpm checks:"
** Affects: ceph-iscsi (Ubuntu)
There are no extensions or scripts that I have installed to handle the
backlight.
I did not include acpi_backlight=vendor as a kernel parameter at the same
time as i915.enable_dpcd_backlight=1. The only kernel parameters currently
are "i915.enable_dpcd_backlight=1 quiet splash". Should I try both
This kernel parameter does make the backlight respond to keyboard input, as
well as manually changing the brightness values in
`/sys/class/backlight/intel_backlight/brightness`. However the behavior is
odd. Adjusting the brightness using the keyboard results in erratic changes
rather than a smooth
, Mike Young.
On Sat, 8 Feb 2020, 02:31 Balint Reczey
wrote:
> Do you still observe the issue on 19.10 or later?
> I'm reassigning to a package more related to the potential bug.
>
> ** Package changed: shadow (Ubuntu) => gnome-shell (Ubuntu)
>
> ** Changed in: gnome-shel
Yes. AMOLED multitouch (3840 x 2160) panel
On Tue, Feb 4, 2020, 1:06 AM Kai-Heng Feng
wrote:
> Is it an OLED panel?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1860303
>
> Title:
> Backlight brightness cannot be
Public bug reported:
ceilometer-collector fails to stop if it cannot connect to message
broker.
To reproduce (assuming amqp is running on localhost):
1) Comment out the 'oslo_messaging_rabbit' section from
/etc/ceilometer/ceilometer.conf. This will trigger ceilometer-collector to look
locally f
Public bug reported:
OS Ubuntu focal fossa 20.04
On boot error message - Apparmor Failed to start profiles.
Steps attempted to correct
1.sudo as status
lee@lee-desktop:~$ sudo aa-status
apparmor module is loaded.
53 profiles are loaded.
51 profiles are in enforce mode.
/sbin/dhclient
/sna
erformed a partial upgrade from Ubuntu 18.04 to 20.04
Regards,Faustin
** Changed in: mariadb-10.3 (Ubuntu) Status: New => Incomplete
Regards,--
Lee Young,
--
Lee Young, K5LY
FOC #2062, CW Ops #1124, FISTS #15371, SKCC #7448
CW Forever!
--
You received this bug notification because you
Public bug reported:
mysql cannot be installed, missing files
mariadb cannot install because of erroer with uninstalling mysql.
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: mariadb-common 1:10.3.21-2
ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3
Uname: Linux 5.4.0-9-generic x
Public bug reported:
lee@lee-desktop:~$ sudo apt-get install mysql-server
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages were automatically installed and are no longer required:
icoutils libglade2-0 liblouis14 libnfs12 libus
Public bug reported:
I cannot adjust the screen brightness using the keyboard keys or
changing /sys/call/backlight/intel_backlight/brightness values. I've
only been able to adjust the backlight using xrandr.
Followed bug report on
https://wiki.ubuntu.com/Kernel/Debugging/Backlight#Diagnostic_Tec
Sahid pointed out that the swift-init will traverse a search path and
start a daemon for every config file it finds so no change to the init
script is needed. Initial tests suggest this completely covers my use
case. I will continue testing and report back. I will mark the bug as
invalid for the mo
Hi Sahid,
In our deployment for swift global replication we have two account services.
One for local and one for replication:
# cat /etc/swift/account-server/1.conf
[DEFAULT]
bind_ip = 0.0.0.0
bind_port = 6002
workers = 1
[pipeline:main]
pipeline = recon account-server
[filter:recon]
use = egg
Hi Cory, the init script update is to support swift global replication.
The upstream code and the proposed changes to the charm support the
feature in mitaka so ideally the support would go right back to trusty-
mitaka.
--
You received this bug notification because you are a member of Ubuntu
Bugs
** Description changed:
- On swift proxy servers there are three groups of services: account,
+ On swift storage servers there are three groups of services: account,
container and object.
Each of these groups is comprised of a number of services, for instance:
server, auditor, replicator
Public bug reported:
On swift proxy servers there are three groups of services: account,
container and object.
Each of these groups is comprised of a number of services, for instance:
server, auditor, replicator etc
Each service has its own init script but all the services in a group are
configu
I can confirm that the disco proposed repository fixes this issue.
I have run the openstack teams mojo spec for disco stein which fails due
to this bug. I then reran the test with the charms configured to install
from the disco proposed repository and the bug was fixed and the tests
passed.
Log f
Hi Christian,
Thanks for your comments. I'm sure you spotted it but just to make it
clear, the issue occurs with bonded and unbonded dpdk interfaces. I've emailed
upstream here *1.
Thanks
Liam
*1 https://mail.openvswitch.org/pipermail/ovs-discuss/2019-July/048997.html
--
You received thi
* sudo apt-get install xfonts-100dpi
Fixed this for me on Ubuntu 18.04.2 LTS
July 2019
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1016777
Title:
dotty missing labels and context menu is broken
1 - 100 of 2642 matches
Mail list logo
