Gotit - thanks!
On Fri, 2020-07-17 at 15:36 +, Kai Kasurinen wrote:
> This bug report is being closed due to your last comment regarding this
> being fixed. For future reference you can manage the status of your own
> bugs by clicking on the current status in the yellow line and then
>
Dug further on this and the issue is an ancient TLS version being used
on the server, so this bug can be closed. BTW is there any way for me
to close the bug myself since I filed it? Thnx -
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Indeed it was - 20.10 does not have this issue. Hopefully we can get a
backport to focal...
Anyway thanks a ton!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1880018
Title:
Notifications
Public bug reported:
Upon upgrade to focal notifications are black text on very dark grey
background, rendering them unreadable. I've attached a screenshot of
how it looks after the upgrade.
Hovering over the notification in the popup makes the text turn the
correct light color.
To make it
Got bit by this as well, recall fixing it a few years ago but must have
clobbered my changes on upgrade bionic -> eoan? Having VirtualBox
installed broke it, fix was to comment out this line in
/lib/systemdd/system/systemd-timesyncd.service.d and restart systemd:
You can close this, after recent updates it is now opening fine.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1860827
Title:
[snap] chromium does not open
To manage notifications about this bug
Public bug reported:
Just upgraded to fossa. When clicking chromium-browser, title bar
switches to "Chromium Web Browser", spins for awhile and then disappears
nothing opens.
If it helps, running 'chromium-browser' at CLI is:
mark@zynxps:~$ chromium-browser
Failed to move to new namespace: PID
Public bug reported:
Just upgraded from eoan -> fossa to test. Incoming mail is configured
to use STARTTLS over port 143 and works fine in eoan and bionic.
But in fossa, upon startup IMAP immediately fails with error message:
'The reported error was "Error performing TLS handshake: An
I went ahead and properly filed but 1860824 so this one can be closed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1860823
Title:
IMAP with STARTTLS is broken
To manage notifications about this
Public bug reported:
Just upgraded from eoan -> fossa to test. Incoming mail is configured
to use STARTTLS over port 143 and works fine in eoan and bionic.
But in fossa, upon startup IMAP immediately fails with error message:
The reported error was “Error performing TLS handshake: An
Somehow this went the the wrong package; hopefully someone can reassign
it was intended to go to the 'evolution' package directly.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1860823
Title:
IMAP
When av LTS is relkeased, is is considered according to it's promise: 6 years.
But yet, after 3.5 years, here we are.
Someone else said it works fine in Eoan.
...who approved this SRU?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Thanks, was really surprised to see this happen in an LTS release. Any
Ubuntu devs reading this, can we get a backport?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1841646
Title:
White text on
Same behavior here, after unattended upgrade. This renders Evolution
pretty much unusable with dark theme.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1841646
Title:
White text on white
Hilko, you probably know this but it looks like in the original thread
here:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/759725
...that this could be fixed thusly:
To have this automatically happen with each new kernel, create
/etc/kernel/postinst.d/statoverride:
#!/bin/sh
Absolutely baffling that it is allowed for stuff like this to be removed
without anyone considering the ramifications for the users... what is
software without usefulness to its users?
Anyway maybe the solution to this is an AppImage? Compile a binary with
all dependent libs in the same folder
Tested against a win2012 server, readonly SMB share. Working here.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1576187
Title:
backuppc/smb: BackupPC failes to backup SMB shares after smbclient
Thanks much - once PPA is up I can try spinning up a vanilla xenial and
test this week.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1576187
Title:
backuppc/smb: BackupPC failes to backup SMB
This is fixed in Bionic 18.04, however the parameter
"$Conf{BackupZeroFilesIsFatal} = 0" parameter for SMB Xfer, needs to be
changed for upgrading hosts that had it previously set to 1.
Relevant post at Debian bug #820693:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=820963#82
--
You
This is still an issue in Bionic.
It has been fixed upstream in 3.3.2 (Bionic currently is 3.3.1), see
last post by upstream here:
https://github.com/backuppc/backuppc/issues/21
Patch is here: https://github.com/backuppc/backuppc/pull/22
Looks like smbclient output was changed, which broke some
Same, getting hard lockups on boot. Images from everywhere else work
beautifully.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1546108
Title:
Latest Vagrant box for Ubuntu Xenial is failing to
Also Confirmed - vendor issue, not Ubuntu - BIOS upgrade fixed
brightness / suspend issues as well for me. Everything now works
flawlessly.
A bit OT but in case others arrive here via google: the V5-122P BIOS
updates *require* you to be running Windows 8 or newer. If you aren't
dual booting
Fixed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/540645
Title:
no fsck messages shown in details mode (no splash on cmdline)
To manage notifications about this bug go to:
Thanks Steve for taking the time to explain. This is exactly it -
people think that plymouth is only annoying graphical stuff without
realizing that upstart is replacing the System-V init entirely - already
has for the symlinks in /etc/init.d. And the way upstart communicates
with the display
On Oct 9, 2012, at 2:46 PM, Steve Langasek steve.langa...@canonical.com wrote:
On Tue, Oct 09, 2012 at 09:03:00PM -, Michael Neuffer wrote:
Could you perhaps update your package to version 2.41?
2.42 now.
Surprise, surprise.
@Steve: Would you then consider picking up the change
I read some other thread regarding Ubuntu making plymouth a too-strong
dependency. et. al., so I guesss this is our bug. Most importantly, this:
https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/556372
...to which you ignored your users? And this:
TL;DR please give your users an exact explanation as to why you made
plymouth such a strong dependency. This is ridiculous to those of us
who don't understand the specifics which must be happening here. Please
fully explain this decision.
--
You received this bug notification because you are a
And BTW, there are *multiple* bugs regarding crypsetup. To wit:
https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/556372
Is this correct? I see similar complaints nestled within a myriad of
other bug threads similar to this one.
--
You received this bug notification because you are a
*nod* ... after only four years (not even one LTS cycle), we have begun
the upgrade process back to debian. Debian testing appears to be much
more stable than ubuntu these days. Less updates too.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
*** This bug is a duplicate of bug 540645 ***
https://bugs.launchpad.net/bugs/540645
It *is* true, we can tap esc but no fsck progress is given.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
*** This bug is a duplicate of bug 540645 ***
https://bugs.launchpad.net/bugs/540645
Rants aside, I'm willing to look at the sources again and send a diff to
support /etc/defaults/rcS line. We already change files all over the
place for ubuntu - another option is no big deal. It's only two
Does the desktop theme on Precise provide a progress bar? If anyone can
chime in, please do otherwise I'll test it myself later this week in a
VM.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/765735
:
* Added --fsck-console parameter to use console progress bar. To
enable, add FSCKCONSOLE=yes to /etc/defaults/rcS.
My PPA package is still sitting on Launchpad here:
https://launchpad.net/~mark-syminet/+archive/syminet/+packages
If this seems a good approach, I'm willing to spend the time
:
* Added --fsck-console parameter to use console progress bar. To
enable, add FSCKCONSOLE=yes to /etc/defaults/rcS.
My PPA package is still sitting on Launchpad here:
https://launchpad.net/~mark-syminet/+archive/syminet/+packages
If this seems a good approach, I'm willing to spend the time
Horrible. We do not see this idiocy on Debian Systems, it is an UBUNTU
problem. Apparently they re-packaged it without knowing what they are
doing. Mint exists because why. Please make your changes much miloder,
and concern yourself with the source. If they aren't doing it, then
your new ideas
*milder ... sorry for the rant too but I've been venting awhile. I
think many people have. Stop reinventing the wheel please and follow
your own upstream - they already do most of the work for you.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I suspect this is related to the mountall binary package?
Which deserves to be condemned to all hell.
How DARE the packagers INFECT a distribution with a binary
upon startup, other than the kernel?
The only binary code upon turning on any computer,
should be the kernel.
Everything else
I could fix this myself if it wasn't for unbelievably
ridiculous shit like this:
On Ubuntu:
root@38r8:~# set |wc -l
6705
…on standard Debian:
4r6s1:~# set | wc -l
50
4r6s1:~#
…really? *Really*?
On Sep 23, 2012, at 4:50 PM, Dmitrijs Ledkovs wrote:
On 23 September 2012 23:43,
Just got bit by this one again, clean lucid install. The fix is to rm
-f /etc/gshadow.lock.
sudo do-release-upgrade finishes with this:
The upgrade has aborted. Your system could be in an unusable state. A
recovery will run now (dpkg --configure -a).
Setting up dbus (1.4.18-1ubuntu1) ...
Same exact errors here.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1004606
Title:
virsh create-snapshot fails to create external snapshot
To manage notifications about this bug go to:
OK - thanks!
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dbconfig-common in Ubuntu.
https://bugs.launchpad.net/bugs/670526
Title:
phpmyadmin broken after hardy - lucid upgrade
To manage notifications about this bug go to:
OK - thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/670526
Title:
phpmyadmin broken after hardy - lucid upgrade
To manage notifications about this bug go to:
Hello Clint, going to have to say user error on this one apologies for
the false alarm - someone had a line in a script that was changing stuff
in /etc/udev which bonked things. Did a fresh Precise reinstall from
the mini.iso and no issues, also a Lucid - Precise upgrade to confirm
and indeed...
Still no progress bar in Precise. This really is bad, particularly on
server because we get stuck with very long fscks on large disks and the
progress bar is critical during unexpected downtimes. We need to be
able to provide at least rough ETA's for our bosses/customers, and have
assurance the
Still no progress bar in Precise... possible xref bug 765735
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/540645
Title:
no fsck messages shown in details mode (no splash on cmdline)
To manage
I'm getting exactly these symptoms after a test upgrade from vanilla Lucid -
Precise.
Upon reboot, the iface is indeed reachable and I can ssh into it within about
10 seconds but
on the monitor it says Waiting up to 60 more seconds for network
configuration... error,
and hangs there for a
We have servers which are all automatically configured by adding simple static
entries to /etc/network/interfaces. Upon reboot, it's network reachable within
about ten seconds while the monitor is hung saying, Waiting 60 more seconds
for network configuration... - but it is pingable and
sorry, that should be add this line to /etc/modprobe.d/blacklist-
framebuffer.conf :
blacklist vga16fb
...superfast VM console now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/582145
Title:
Same problem here. Workaround was to add the following line to
/etc/modprobe.d/blacklist.conf:
blacklist vga16fb
reboot, and vnc works as it should.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@Serge correct - for security (and portability) reasons, we've decided
to run ssh only and nothing else on the hosts - all other services run
on guests - so the host is using one of it's own guests as it's DNS
server. It's backup nameservers are on different hosts which are
usually up, so we
@Serge correct - for security (and portability) reasons, we've decided
to run ssh only and nothing else on the hosts - all other services run
on guests - so the host is using one of it's own guests as it's DNS
server. It's backup nameservers are on different hosts which are
usually up, so we
But what if your DNS servers, are also your guests?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in Ubuntu.
https://bugs.launchpad.net/bugs/599342
Title:
Temporary failure in name resolution
To manage notifications about
Might stand to rephrase:
What if your DNS servers, are your guests?
And btw? Thanks for all you do.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in Ubuntu.
https://bugs.launchpad.net/bugs/599342
Title:
Temporary
But what if your DNS servers, are also your guests?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/599342
Title:
Temporary failure in name resolution
To manage notifications about this bug go to:
Might stand to rephrase:
What if your DNS servers, are your guests?
And btw? Thanks for all you do.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/599342
Title:
Temporary failure in name
I can't believe you guys actually blackholed stdout during fsck... I updated
the code for this to provide for a status bar, like it should be with e2fsck
-C0 -y as its been since like, forever:
https://launchpad.net/~mark-syminet/+archive/syminet
...not applying this to any machine
You can't cross reference and/or reassign this bug over to the proper
place for them? I am having same issue here... back to google I go...
--
Dell Mini 9 Hibernate does not work
https://bugs.launchpad.net/bugs/550028
You received this bug notification because you are a member of Ubuntu
Bugs,
Possible cross reference bug #477106:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/477106
--
Dell Mini 9 Hibernate does not work
https://bugs.launchpad.net/bugs/550028
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
OK thanks, the fix I posted worked easily enough over here. I might mention
that I was using a /root/.my.cnf for auto-login to mysql. When being asked
questions by dbconfig I leave the passwd blank and usually that seems to work
just fine. So if you aren't hearing this from others, then
OK thanks, the fix I posted worked easily enough over here. I might mention
that I was using a /root/.my.cnf for auto-login to mysql. When being asked
questions by dbconfig I leave the passwd blank and usually that seems to work
just fine. So if you aren't hearing this from others, then
Hello, sure, here you go (I removed my exit 0; at the top):
=== snip ===
#!/bin/bash -e
# It is possible that Debconf has
Hello, sure, here you go (I removed my exit 0; at the top):
=== snip ===
#!/bin/bash -e
# It is possible that Debconf has
What Ingo said - for servers, not having a console progress bar is *terrible*,
since for servers we often aren't physically there. So even with e.g. remote
VNC access we get nothing but a blank screen and have no idea if it's actually
even doing a fsck, or locked up for some other reason.
Public bug reported:
Binary package hint: mysql-server-5.1
Hardy - Lucid upgrade, after which phpmyadmin warns about mysql-server5.0
whereas
the php library is 5.1 and thus conflicts. OK, lets upgrade - but mysql
upgrade fails due to
what looks like a typo in the postrm script:
===
Public bug reported:
Binary package hint: phpmyadmin
Lucid: 4:3.3.2-1
After upgrade hardy - lucid phpmyadmin complains that controluser is
invalid and logins fail.
These commands fixed it:
dpkg --purge phpmyadmin
apt-get install phpmyadmin
However more bugs/errors/warnings after being able
Public bug reported:
Binary package hint: phpmyadmin
Lucid: 4:3.3.2-1
Upgrade Hardy - Lucid.
Try to restart with fresh install:
dpkg --purge phpmyadmin
drop phpmyadmin database
apt-get install phpmyadmin
But upon login this message appears at the bottom of the screen in glaring red
Public bug reported:
Binary package hint: mysql-server-5.1
Hardy - Lucid upgrade, after which phpmyadmin warns about mysql-server5.0
whereas
the php library is 5.1 and thus conflicts. OK, lets upgrade - but mysql
upgrade fails due to
what looks like a typo in the postrm script:
===
Public bug reported:
Binary package hint: phpmyadmin
Lucid: 4:3.3.2-1
Hardy - Lucid upgrade, tried a fresh install with
dpkg --purge phpmyadmin
drop database phpmyadmin
apd-get install phpmyadmin
But we are still greeted by a scary red warning banner at the bottom of the
phpmyadmin login
Same problem here. If the newer kernel is required, then why isn't it a
dependency when going from Hardy - Lucid?
--
After upgrade from Karmic boot fails, mountall and udevd fail
https://bugs.launchpad.net/bugs/516684
You received this bug notification because you are a member of Ubuntu
Bugs,
Same here - switched a few kvm guests from ide - virtio disks. Ran
apt-get upgrade and voila, broken packaging system. The patch provided
by nutznboltz up there solved the issue.
--
grub-pc.postinst script fails to detect virtio vda disk in KVM guest
https://bugs.launchpad.net/bugs/604335
You
What Sam said. php-mdb2 installed OK but it isn't enough - additional
packages are required depending upon which DB you're using:
php-mdb2 - PHP PEAR module to provide a common API for supported RDBMS
php-mdb2-driver-mysql - PHP PEAR module to provide a MySQL driver for MDB2
OK, so what's happening is that people are doing apt-get install
roundcube. When they go through dbconfig-common to configure their
database for mysql, it's implicit that roundcube knows it's supposed to
be using mysql - but it wants to use sqlite.
Looking closer, it's obvious now but not when
shitty solution. WWhy are you7 here?
--
Wrong compilation of asterisk-mp3
https://bugs.launchpad.net/bugs/589307
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Same error here, upgrading from karmic - lucid all of our music on hold files
went silent. Worked around this here by converting the mp3's to .sln files:
apt-get remove asterisk-mp3
apt-get install sox libsox-fmt-all mpg321
# convert mp3 to wav
mpg321 -w myfile.mp3 myfile.wav
# convert wav
I had the same situation here, it turns out it was a stuck useradd process -
destroying it got useradd working again, something like this:
killall -9 userdel
rm -f /etc/*lock
In my case the stuck useradd was caused by a bug in my own script, but
for the others, if it was caused by the
Same here. Installing dahdi-linux by hand first worked for me:
apt-get install dahdi-linux
...then install asterisk and it was ok so seems to be something in the order in
which it's installing packages.
It's a different bug, no time to check but also had the following
happen:
Same here:
Do you want to continue [Y/n]?
Preconfiguring packages ...
(Reading database ... 45584 files and directories currently installed.)
Preparing to replace unattended-upgrades 0.52ubuntu1 (using
.../unattended-upgrades_0.52ubuntu1_all.deb) ...
Unpacking replacement unattended-upgrades
77 matches
Mail list logo
