Was able to 'solve' the issue through
sudo apt-get purge linux-image-6.5.0-35-generic
reboot # into the 6.5.0-28-generic kernel
sudo apt update;sudo apt upgrade
reboot # into the 6.5.0-35-generic kernel
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
diff /boot/config-6.5.0-35-generic /boot/config-6.5.0-28-generic
3c3
< # Linux/x86 6.5.0-35-generic Kernel Configuration
---
> # Linux/x86 6.5.0-28-generic Kernel Configuration
51c51
< CONFIG_VERSION_SIGNATURE="Ubuntu 6.5.0-35.35~22.04.1-generic 6.5.13"
---
> CONFIG_VERSION_SIGNATURE="Ubuntu
Tried as well in (initramfs) to load the kernel module for lvm and lvm
vgchange -ay but this does nothing in (initramfs) making the system also
not recoverable when starting with the 6.5.0-35-generic kernel
** Attachment added: "showing the last error messages before it drops into
initramfs"
Public bug reported:
Product: Ubuntu 22.04
Component: Kernel 6.5.0-35-generic
Summary: The kernel 6.5.0-35-generic in Ubuntu 22.04 fails to load the
LVM module, causing the root file system to not be found and the system
to boot into (initramfs).
Steps to Reproduce:
Install Ubuntu 22.04 with
Public bug reported:
After upgrading from Ubuntu 23.10 to 24.04 following the instructions in
https://help.ubuntu.com/community/NobleUpgrades#Upgrading_Ubuntu_Desktops_to_24.04_LTS
(that is, with update-manager -d), everything went smooth.
However, in the bottom left part of the login screen it
This bug happend to me as I had modified my.cnf file instead of puting
the modifications in the mysql.conf.d folder.
a good reminder to always use the .d directories.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
no conecta el socket
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: mysql-server-8.0 8.0.26-0ubuntu0.20.04.3
ProcVersionSignature: Ubuntu 5.11.0-36.40~20.04.1-generic 5.11.22
Uname: Linux 5.11.0-36-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.20
Architecture:
apport information
** Attachment added: "acpidump.txt"
https://bugs.launchpad.net/bugs/1945112/+attachment/5528373/+files/acpidump.txt
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1945112/+attachment/5528371/+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/1945112
Title:
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1945112/+attachment/5528372/+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/1945112
apport information
** Attachment added: "PulseList.txt"
https://bugs.launchpad.net/bugs/1945112/+attachment/5528369/+files/PulseList.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1945112
apport information
** Attachment added: "RfKill.txt"
https://bugs.launchpad.net/bugs/1945112/+attachment/5528370/+files/RfKill.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1945112
Title:
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1945112/+attachment/5528368/+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/1945112
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1945112/+attachment/5528367/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1945112/+attachment/5528366/+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/1945112
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1945112/+attachment/5528365/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1945112/+attachment/5528364/+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/1945112
apport information
** Attachment added: "Lsusb-v.txt"
https://bugs.launchpad.net/bugs/1945112/+attachment/5528363/+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/1945112
Title:
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1945112/+attachment/5528361/+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/1945112
Title:
apport information
** Attachment added: "Lsusb-t.txt"
https://bugs.launchpad.net/bugs/1945112/+attachment/5528362/+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/1945112
Title:
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1945112/+attachment/5528359/+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/1945112
Title:
apport information
** Attachment added: "Lspci-vt.txt"
https://bugs.launchpad.net/bugs/1945112/+attachment/5528360/+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/1945112
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1945112/+attachment/5528358/+files/IwConfig.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1945112
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1945112/+attachment/5528356/+files/CRDA.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1945112
Title:
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1945112/+attachment/5528357/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Tags added: apport-collected
** Description changed:
see https://unix.stackexchange.com/questions/437468/bluetooth-headset-
volume-too-low-only-in-arch
==Reproducer==
1) install Ubuntu 20.4
2) pair with a set of Apple AirPods
3) try to listen to some
The laptop hardware this is done on is a Dell XPS-13, though I suppose
this shouldn't make a difference.
** Attachment added: "lspci-vnvn.log according to bug reporting instructions"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1945112/+attachment/5528180/+files/lspci-vnvn.log
--
Public bug reported:
see https://unix.stackexchange.com/questions/437468/bluetooth-headset-
volume-too-low-only-in-arch
==Reproducer==
1) install Ubuntu 20.4
2) pair with a set of Apple AirPods
3) try to listen to some video
4) put volume up to maximum and repeat 3)
5) turn on volume boost and
This bug is still present in Ubuntu 20.04 LTS Desktop 64-bit, after 12
years.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/272293
Title:
[hardy] Key repeat gets randomly turned off.
To manage
*** This bug is a duplicate of bug 1872908 ***
https://bugs.launchpad.net/bugs/1872908
I have the same issue as Alexandre, proceeded with autoupdate and
sudednly my PC stopped recognizing my wifi adapter.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Public bug reported:
Remote machine 100km further away
Computer is updating
End user thinks computer is slow and pulls the power plug from the computer
Turns out computer was updating the kernel
Starts machine
Grub can't find any kernels anymore and drops into Grub CLI
The process of finding the
Here is the machine info from Landscape:
Distribution: Ubuntu 18.04.5 LTS (bionic)
Hardware:
Processor: Intel(R) Celeron(R) CPU N3150 @ 1.60GHz
Memory: 8 GiB RAM
Storage:Model: SanDisk SDSSDX24
Size: 240 GB
Network:Model: Wireless 3160
MAC: f4:06:69:x:x:x
IP:
*** This bug is a duplicate of bug 1767299 ***
https://bugs.launchpad.net/bugs/1767299
Thrashing and system lockup are possible to achieve with Firefox on a
default Ubuntu install with much more memory than this. E.g. mine has
16G.
This might not be argued to be a bug with the upstream
Public bug reported:
When updating the ubuntu-release-upgrader
Ubuntu italian:
Impossibile calcolare l'avanzamento
Si è verificato un problema irresolubile durante il calcolo
dell'avanzamento.
Nel caso fosse un altro problema, segnalare un bug eseguendo in un
terminale il seguente comando:
As recommended by the Gnome-shell developers a bug upstream with Mutter is
opened.
https://gitlab.gnome.org/GNOME/mutter/-/issues/1356
** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #1356
https://gitlab.gnome.org/GNOME/mutter/-/issues/1356
--
You received this bug notification
Also I'm happy to use a workaround. I'm just a bit disappointed that devilspie
no longer works.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1888098
Title:
Ubuntu 20.04 gnome-shell places windows
Thank you for your further input Daniel.
The issue is that the stable version of ChromisPOS that I'm using the
source code was destroyed by a commit error.
I'm working together with the developer providing resources to get the
unstable version production ready but that is taking more time than I
I have had this issue with my C270 on Windows and now on Ubuntu 20.04. So it's
mainly a Logitech issue, but on Windows I fixed it by fixing the mic on 16000
hz. On Ubuntu I tried chaging etc/pulse/daemon.conf to ; default-sample-rate =
16000
; alternate-sample-rate = 16000
and it did not work.
Reported this Upstream under
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/3011
** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #3011
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/3011
--
You received this bug notification because you are a member of Ubuntu
Bugs,
This is interesting. When running gnome-shell in Wayland the window
placement seems to be correct. I've been testing it a bit.
Unfortunately Wayland doesn't allow for remote desktop access so I can't
help my customers when something goes wrong.
--
You received this bug notification because you
Wish me luck, fingers crossed. I'm going to create the issue on Gnome's
bug tracker now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1888098
Title:
Ubuntu 20.04 gnome-shell places windows on
@Daniel van Vugt
Thanks for your understanding and advice.
Do you have any recommendations for an alternative window manager that is:
- Officially Supported by Canonical under the support contract
- Touchscreen Friendly
- Secure
- Has a sidebar on the left (the product I sell is designed around
And the cashier side
** Attachment added: "Cashier side of the setup"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1888098/+attachment/5394700/+files/Bug1888098_opposingScreensCashier.jpeg
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
So you can see what the system looks like when installed
** Attachment added: "Opposing Screens Customer"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1888098/+attachment/5394699/+files/Bug1888098_opposingScreensCashier.jpeg
--
You received this bug notification because you
And before anyone starts anything about freeloading.
I donate several thousand euros per year and a lot of my time to open
source projects.
So, let's not go there.
Once again thank you.
I hope that it's much clearer now what is not working as expected in
Ubuntu 20.04's iteration of Gnome
And here is proof that there are no extensions enabled
** Attachment added: "No Extensions enabled"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1888098/+attachment/5394697/+files/Bug1888098_ProofAllExtensionsDisabled.jpeg
--
You received this bug notification because you are
Some more fun, the onscreen keyboard follows the misplaced dialog box to
the non-touchable monitor.
** Attachment added: "Screen Keyboard opens on non touchable area"
Here is an extra treat so you can see why block Caribou is very
necessary and the gnome onscreen keyboard implementation makes the
system completely unusable.
** Attachment added: "Extra treat why the block caribou extension was on."
Here is a photo so you can see that the Center New Window option does
nothing. At least it stopped doing the Easter Egg of putting things
halfway between two monitors that's a plus. :D
** Attachment added: "Photo Center new window doesn't do anything"
Thanks for have a new look at this
Oh and I forgot to mention this is with the option
Center New Windows turned ON in Gnome Tweak Tool
Which should theoretically do the same as the DCONF edit line, right?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Here is a photo so it's easier to understand what the issue is.
** Attachment added: "Photo of the issue faced"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1888098/+attachment/5394688/+files/2020-07-21_Bug%20-1888098_GnomeWindowPlacementBug.png
--
You received this bug
Removing the extensions has the same effect.
Block Caribou 36 is necessary as the Point of Sale system (Open source)
already has all the buttons and keyboard that are necessary for the use
of the Point of Sale system. Yet it contains text entry fields which pop
up the on-screen keyboard. There
Public bug reported:
Ubuntu 20.04 LTS
gnome-shell:
Geïnstalleerd: 3.36.3-1ubuntu1~20.04.2
What I expected to happen:
When clicking a button on the primary screen to open a new window in any
application, that window should always open on the same monitor.
What happened instead:
Gnome-shell
This still affect LTS 18.04
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1635463
Title:
pip freeze includes "pkg-resources==0.0.0"
To manage notifications about this bug go to:
Public bug reported:
Ubuntu 20.04 LTS
gnome-tweaks 3.34.0-2ubuntu1
AOC USB monitor
Bus 002 Device 002: ID 17e9:ff10 DisplayLink I1659FWUX
What I expected to happen:
When the USB3.0 Displaylink monitor is plugged in and gnome-tweaks installed
the display remains on and attached as a monitor
There is a workaround via
xinput map-to-output "Weida Hi-Tech CoolTouch® System" eDP-1
There needs to be some kind of detection to do this automatically and
create a systemD systemctl file.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Here is the xinput list-props while the second screen (AOC) is disconnected
Here the touch works as expected
xinput list-props 11
Device 'Weida Hi-Tech CoolTouch® System':
Device Enabled (169): 1
Coordinate Transformation Matrix (171): 0.50, 0.00, 0.50,
0.00,
There is a regression of this bug in Ubuntu 20.04 using the default Gnome
desktop
Setup is a Shuttle POS P511
using a Weida CoolTouch controller with driver integrated into the Linux kernel
Second screen is a AOC USB-3.1 Display Link monitor without display
capabilities only (no touch).
When
Can confirm that these steps BEFORE REBOOTING lead to a working 18.04
system after the 16.04 upgrade fails.
Maybe these steps could be added to the upgrade script
In psudocode:
if [ error due to systemd1.service ] then;
sudo mv /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service
Thanks, after loosing 4 terabytes of data due to buggy BTRFS, I moved
away from the file system back to ext4. I still have the machine on a
shelf for the day BTRFS becomes stable or gains recovery tools, so I can
recover and access the data again.
If you want to test this specific case then
Public bug reported:
Hi,
Yesterday we upgraded from 5.7.29-0ubuntu0.18.04.1 to
5.7.30-0ubuntu0.18.04.1 (via unattended-upgrade) on Ubuntu 18.04 and
slurmdbd (https://packages.ubuntu.com/bionic/admin/slurmdbd) started
segfaulting.
Upon inspection, the slurmdbd crash is caused by a change of
I am also attaching the SLURM stored procedure which triggers the bug.
It’s obviously a bit more complicated than my minimal example :-)
** Attachment added: "slurmprocedure.txt"
https://bugs.launchpad.net/ubuntu/+source/mysql-5.7/+bug/1877442/+attachment/5367971/+files/slurmprocedure.txt
--
@ddstreet did you have a chance to look at this?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1815684
Title:
[SRU] Please accept zeroc-ice to supported releases
To manage notifications about this
Hi Dan,
I have uploaded the 3.7.3 packages to
https://launchpad.net/~y-jose/+archive/ubuntu/zeroc-ice
I installed mumble with 3.7.3 and didn't find any issue (but I'm not
mumble expert, just did a default install).
I also check that mumble source build works with the new zeroc-ice 3.7.3
Hi Dan,
We have released 3.7.3, what should we do at this point, get first this
3.7.2 uploaded or skip it and try to get 3.7.3 in?
3.7.3 is binary compatible and include a few bug fixes and enhancements
see https://github.com/zeroc-ice/ice/blob/3.7/CHANGELOG-3.7.md#changes-
in-ice-373
let me
Public bug reported:
Grub installer fails on every install try, frustrating
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ubiquity 18.04.14.12
ProcVersionSignature: Ubuntu 5.0.0-23.24~18.04.1-generic 5.0.15
Uname: Linux 5.0.0-23-generic i686
ApportVersion: 2.20.9-0ubuntu7.7
Architecture:
Isn't
bluetoothctl
the current alternative to hidd?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/281580
Title:
[Intrepid] New Bluetooth Wizard fails to pair with devices:
reintroduce hidd
To
Public bug reported:
no information on why or where to install the grub-installer, several
failed attempts
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ubiquity 18.04.14.12
ProcVersionSignature: Ubuntu 5.0.0-23.24~18.04.1-generic 5.0.15
Uname: Linux 5.0.0-23-generic i686
ApportVersion:
Done
https://github.com/storaged-project/udisks/issues/723
** Bug watch added: github.com/storaged-project/udisks/issues #723
https://github.com/storaged-project/udisks/issues/723
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The Source code file location where this happens I'm pretty sure is
here:
/src/disks/gduwindow.c
/*
*/
static void
eject_cb (UDisksDrive *drive,
GAsyncResult *res,
gpointer
Public bug reported:
Use case: As a user of hot swap-able SATA disks using a Harddrive Riser
over eSATA. I need a safe, easy and convenient way to remove the hot
swap-able SATA disk without rebooting and without having to go to the
command line.
When attempting to eject an harddisk or a solid
Translation of the Error message to English:
Removal of the medium has failed
Error ejecting /dev/sdi: Command-line `eject"/dev/sdi"' exited with a non-zero
status 1:
eject: could not eject, last error:
Incorrect ioctl() for device
(udisks-error-quark, 0)
So you can see in the error message
Hi, I have new installation of Ubuntu 18.04.3 LTS (xubuntu). It has
ristretto 0.8.2 and the bug still occurs there. It's nice to have fixed
the bug, but I don't understand why the LTS users should have work with
the buggy version until next LTS. Any plans to fix it in current LTS? Or
do I miss an
So I took over the screen and see that there is a user prompt to
upgrade.
I chose the regular updates which included an update for the unattended
upgrade package.
I'll try to cancel and restart the Landscape process with the new
unattended-upgrade package.
ii unattended-upgrades
Now 14 days into the upgrade. There has been no timeout of the process and it's
still chugging along doing absolutely nothing at all.
(see screenshot)
** Attachment added: "14 days in still no upgrade or timeout"
Still running now 72 hours later with no progress.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1853056
Title:
LANDSCAPE: Upgrade from disco to eoan running for 24 hours with no
progress
To
Public bug reported:
LANDSCAPE the licensed version is having troubles upgrading a Disco to
Eoan machine. It's been running for 24 hours with no progress.
Steps to reproduce
* Click on Computers
* Choose the computer to release upgrade
* Click on Packages
* Among the selected computers, 1 can be
Here is the htop output of the machine 24 hours after clicking the
upgrade button in Landscape.
** Attachment added: "HTOP output of the machine"
https://bugs.launchpad.net/ubuntu/+source/landscape-client/+bug/1853056/+attachment/5306325/+files/2019-11-18htopUnattendedUpgrade24hours.png
--
root 1068 0.0 0.5 122408 22240 ?Ssl nov17 0:00
/usr/bin/python3 /usr/share/unattended-upgrades/unattended-upgrade-shutdown
--wait-for-signal
root 1125 0.2 0.7 47792 29684 ?Snov17 4:40
/usr/bin/python3 /usr/bin/landscape-client --daemon --pid-file
systemctl status landscape-client.service
\u25cf landscape-client.service - LSB: Landscape client daemons
Loaded: loaded (/etc/init.d/landscape-client; generated)
Active: active (running) since Sun 2019-11-17 20:05:13 CET; 1 day 2h ago
Docs: man:systemd-sysv-generator(8)
Tasks: 8
systemctl status unattended-upgrades.service
\u25cf unattended-upgrades.service - Unattended Upgrades Shutdown
Loaded: loaded (/lib/systemd/system/unattended-upgrades.service; enabled;
vendor preset: enabled)
Active: active (running) since Sun 2019-11-17 20:05:12 CET; 1 day 2h ago
Screenshot showing the lack of progress. Current time of the screenshot
is 22:00 GMT+1
** Attachment added: "24 hours no progress in the upgrade from Disco to Eoan"
I saved one 14.04.5 machine for this purpose.
Will I be able to enabled -proposed for 14.04.5 even though it's now out of
support?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1670291
Title:
Hello Thomas, is this still valid with latest SW? Thank you.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1017243
Title:
Program received signal SIGBUS, Bus error.
To manage notifications about
Hi Simon,
I have updated the description to include the changes to debian files, I
have also limited the changes to debian files to the minimum and get rid
of a few things that are not required for the SRU:
There are separate branches in our packaging repository for bionic and
cosmic backports:
Updated debdiff for Ice 3.7.2 bionic backport
** Description changed:
[Impact]
* zeroc-ice (3.7.2-4) includes various bug fixes for problems reported in
3.7.1 the most important fixes that can affect Ubuntu users are:
* Fixed a bug in IceGrid that could result in an
Updated debdiff for Ice 3.7.2 cosmic backport
** Patch added: "cosmic-debdiff.diff"
https://bugs.launchpad.net/ubuntu/+source/zeroc-ice/+bug/1815684/+attachment/5273498/+files/cosmic-debdiff.diff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Description changed:
[Impact]
* zeroc-ice (3.7.2-4) includes various bug fixes for problems reported in
3.7.1 the most important fixes that can affect Ubuntu users are:
* Fixed a bug in IceGrid that could result in an infinite loop
when Ice.ChangeUser is set and
** Description changed:
[Impact]
* zeroc-ice (3.7.2-4) includes various bug fixes for problems reported in
3.7.1 the most important fixes that can affect Ubuntu users are:
* Fixed a bug in IceGrid that could result in an infinite loop
when Ice.ChangeUser is set and
** Description changed:
[Impact]
- * zeroc-ice (3.7.2-4) includes various bug fixes for problems reported in
-3.7.1 the most important fixes that can affect Ubuntu users are:
-
-* Fixed a bug in IceGrid that could result in an infinite loop
- when Ice.ChangeUser is set
Hi Simon, I have updated the description as requested
** Description changed:
- zeroc-ice (3.7.2-4) corresponds to a new upstream microrelease. This
- package is already available in Ubuntu Disco and Debian Buster.
+ [Impact]
- Upstream packages are thoroughly tested before each release, and
Public bug reported:
What Happened:
When upgrading from 18.10 -> 19.04 about 10 minutes into the upgrade a dialog
box shows up to remove old packages at this point the HDMI output and ssh
servers are disabled so the only way to continue the upgrade is to physically
go to the machine and plug
Confirmed the same problem, ubuntu 18.04.2 LTS AMD64, when trying to
connect to "eduroam" in several sites in several countries.
I have to say this is pretty annoying.
Same message as mentioned before:
124171.865640] wlan0: Limiting TX power to 20 (20 - 0) dBm as advertised by
ac:a3:1e:c5:84:a0
** Patch added: "debdiff for cosmic"
https://bugs.launchpad.net/ubuntu/+source/zeroc-ice/+bug/1815684/+attachment/5238093/+files/zeroc-ice_3.7.1-2_3.7.2-4.debdiff
** Changed in: zeroc-ice (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a
Public bug reported:
zeroc-ice (3.7.2-4) corresponds to a new upstream microrelease. This
package is already available in Ubuntu Disco and Debian Buster.
Upstream packages are thoroughly tested before each release, and binary
compatibility testing is done as part of the release process we
This is a problem with the user having upstream 3.6 package, and trying
to install Ubuntu 3.5 packages, both packages were not compatible and
install common files.
Starting with 3.6 new version of packaging for upstream and debian are
compatible and are in fact using the same source repository.
the package version is no longer supported
** Changed in: zeroc-ice (Ubuntu)
Status: New => Invalid
** Changed in: zeroc-ice (Ubuntu)
Assignee: (unassigned) => José Gutiérrez de la Concha (y-jose)
--
You received this bug notification because you are a member of Ubuntu
Bugs,
This is a problem with the user having upstream 3.6 package, and trying
to install Ubuntu 3.5 packages, both packages were not compatible and
install common files.
Starting with 3.6 new version of packaging for upstream and debian are
compatible and are in fact using the same source repository.
Public bug reported:
/usr/lib/x86_64-linux-gnu/indicator-printers/indicator-printers-service
Printer is Epson TM-T88V Thermal Roll Receipt printer
indicator-printers-service
Description:Ubuntu 16.04.5 LTS
Release:16.04
indicator-printers:
Geïnstalleerd:
When is the fix going to be released? 18.04.1LTS takes still around 10
seconds to complete after
sudo systemctl start nameofser{TAB}
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1471723
Title:
1 - 100 of 1420 matches
Mail list logo
