steam-libs -> mesa -> libllvm17t64->
/usr/lib/x86_64-linux-gnu/libLLVM-17.so.1
steam-libs:i386 -> mesa:i386 -> libllvm17t64:i386 ->
/usr/lib/i386-linux-gnu/libLLVM-17.so.1
sudo add-apt-repository ppa:oibaf/graphics-drivers
steam-libs -> mesa -> libllvm18
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2063207
Title:
libllvm18:i386 conflicts with libllvm18
To manage notifications about this bug go to:
The fix hasn't been released yet.
"Fix Committed" status means the source has been updated but hasn't been
released in a package.
"Fix Released" status means the new package has the fix.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I have a Dell XPS 13 running Kubuntu 22.04. Keyboard works fine on fresh
boot but the keyboard doesnt work at all after resuming from suspend.
linux-image-6.5.0-27-generic is the kernel I started having the problem
with.
Booting an older 6.5 kernel and keyboard works again after resume.
--
You
That last comment 'don't forget gaps (new line) between pinning rules,
w/o the gap pinning doesn't work correctly" was the cause of my issue. I
now have gparted 1.5.0 installed. Thank you for responding to my issue.
I now know all about app pinning - something new for me.
--
You received this
I'm afraid that approach doesn't resolve the error. Thanks though. It is
interesting.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2060120
Title:
Unmet dependencies cause gparted to fail to
Public bug reported:
1) Ubuntu Noble Numbat (development branch) Release:24.04
2) gparted 1.5.0-1
3) Expected gparted to install.
4) Install failed with 'Depends: gparted-common (= 1.5.0-1) but 1.5.0-1build2
is to be installed'
5) Output from terminal:
$ sudo apt-get install gparted
Public bug reported:
i have a laptop sata drive i used for a file system on windows upgraded
so now its going to be my side loader,
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: ubiquity 22.04.15
ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
Uname: Linux 5.15.0-25-generic
Same for me. I try to add workaroung in #22 but
May 2 15:02:12 KLINGON wpa_supplicant[10086]: SSL: SSL3 alert: write (local
SSL3 detected an error):fatal:internal error
May 2 15:02:12 KLINGON wpa_supplicant[10086]: OpenSSL: openssl_handshake -
SSL_connect error:0A0C0103:SSL routines::internal
Public bug reported:
Ubuntu 21.04 (Canonical Gnome Desktop not flavour). Installed openbox
(3.6.1-9+deb11u1) and lxappearance (0.6.3-1) from standard repos.
Launching immediately segfaults.
Rebuilding the package still segfaults.
It seems to be having issues parsing:
FWIW Upgrading worked fine, system boots normally and everything works
apart from a Failed to start MokListXRT, out of resources message before
the window manager loads.
This is on a Thinkpad with EFI v2.31 by Lenovo
--
You received this bug notification because you are a member of Ubuntu
Bugs,
it is no longer in right-click menu.
bug is fixed for good.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/90851
Title:
Firefox does not set KDE wallpaper
To manage notifications about this bug go
Adding a "me too". Upgraded from 18 to 20 (both LTS) and am now getting
this same error (with identical traceback as above).
It seems that /usr/share/software-
center/softwarecenter/distro/__init__.py calls
platform.linux_distribution(), which no longer exists.
>From stackoverflow (where all of
I've upgraded 4 systems from 18.04 to 20.04, and only one has shown this
behavior. Will attach an strace of the focal process. I ran the strace
for approximately 30 seconds.
** Attachment added: "strace of the python focal process, while bug is
occurring"
I also tried fractional scaling; got the same delay. And when I tried
adjusting the resolution to 1920x1080 directly with the resolution
setting instead of 200% magnification, I got the delay again. So the
only fast adjustment is with magnification and no fractional scaling.
Attached is the
This one is a bit of an improvement. Boot time to a working desktop was
about 3 minutes. But most interesting was that I could change my display
resolution almost instantly with a 200% magnification. Attempting to
change by adjusting the resolution directly (from 3840x2160 to
2560x1440) caused the
I just tested the latest kernel, and it is worse. This time it didn't
even make it to the login screen, and I let it run for 5 minutes. dmesg
from that boot attempt is attached.
Given the lack of success at booting kernels from 5.3 - 5.7, I'm
wondering whether this 2015 iMac is going to be a
I just tested rc4, and now I can no longer log in; same as with rc2. So
to summarize, I cannot get past the login screen with versions rc2 and
rc4, whereas I could with rc3
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
5.7-rc3 boots on my iMac. It gets past the login screen (unlike rc2),
but it still has the slow boot problem.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1874104
Title:
Very slow boot, wake from
I can report that kernel 5.7.0-050700-rc3 now boots (but very slowly).
Unlike rc2, it gets past the login screen.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1875211
Title:
Cannot be past login
I made a separate report of the 5.7-rc2 kernel bug to ubuntu-bug linux
as you requested. I will also try to monitor the upstream rc kernels and
run tests on them as you have requested.
I agree that the slow boot bug is likely connected to the AMD video card
in my iMac, and thus to the amdgpu
Attached is the dmesg from kernel 5.4.0.26, which boots slowly on this
iMac, but at least boots all the way to a working desktop. You can
contrast this to the dmesg of 5.7.0-050700-rc2, which won't boot past
the login screen.
** Attachment added: "dmesg for 5.4.0-26 boot"
Public bug reported:
This is an extension of the "slow boot" bug I reported earlier [Bug
1874104]. I have been working with Jouni Mettala, and he was asking me
to try the most recent kernels, including the latest in development
(5.7.0-050700-rc2). This one not only boots very slowly, but also, I
Instructions were to include information from About in Settings.
Screenshot attached.
** Attachment added: "About my late 2015 27" iMac with the kernel booting
issues"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1875211/+attachment/5360987/+files/About%20my%20computer.png
--
You
I forgot to send you the proper dmesg for the boot of kernel 5.3rc-1. It
is attached. This kernel was not only slow, but it didn't pick up my
wireless card. This was the only kernel I tried that did this.
** Attachment added: "dmesg for 5.3rc1 boot"
I will report the login bug as a new one. As far as bisection past
identifying the line of progression to identify the last kernel that
works and the first one that doesn't, I looked at the further steps one
would have to take and I don't think that my technical capability is up
to it. I have
It is possible to login with kernel 5.6. The bootup is slow, but it does
boot and gets past the login screen. I have attached the dmesg from that
boot, and will send the systemd analysis in the next message.
** Attachment added: "dmesg.0 for 5.6 boot"
Attached is the SystemD analysis for the 5.6 boot. It looks pretty
similar to that of all the kernels I have tried that are 5.3 or newer.
** Attachment added: "SystemD critical chain and blame outputs: 5.6 kernel"
I did the bisection and found that the bad kernels started at 5.3-rc1.
The last 5.2 kernel, 5.2.21, was good. I have attached the SystemD
analysis here of the boots of both kernels. You can see from it that the
problem in rc1 is related to the gpu-manager service.
I will attach the dmesg log of
I should add that I tested kernels 5.2.15, 5.2.18 and 5.2.20 as well.
All were OK, so the good-bad line is clearly after 5.2.21.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1874104
Title:
Very
Here is the dmesg log for the bad boot of 5.3-rc1.
** Attachment added: "Log of 5.3-rc1 kernel boot"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874104/+attachment/5359789/+files/dmesg.0
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Finally, a second dmesg for the 5.2 kernel boot.(I'm not sure whether
dmesg or dmesg.0 is the right one.
** Attachment added: "dmesg.0 for 5.2 boot (I hope)"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874104/+attachment/5359527/+files/dmesg.0
--
You received this bug notification
This time with the last fast kernel, 5.2. The bootup was slightly slower
than with 4.15, but I think this might relate to snap module loading. I
should also point out that the difference between kernels 4.15, 5.1 and
5.2 vs the kernels after 5.3 is more than what is indicated by the
SystemD
Next is the first of two dmesg logs for the 5.2 kernel.
** Attachment added: "dmesg for 5.2 boot (I hope)"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874104/+attachment/5359510/+files/dmesg
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Next, dmesg.0
** Attachment added: "dmesg.0 for 5.3 boot (I hope)"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874104/+attachment/5359503/+files/dmesg.0
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Next, a dmesg for that boot. Not sure which it is so I'll send two.
** Attachment added: "dmesg for 5.3 boot (I hope)"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874104/+attachment/5359502/+files/dmesg
--
You received this bug notification because you are a member of Ubuntu
Bugs,
I uninstalled Virtualbox and tested kernels 5.1 and 5.2. Both showed
fast boots similar to 4.15. I then tested 5.3 by downloading it from the
ppa/mailine. This is where the slow boot started. I have attached two
dmesg's and a systemd analysis of the critical chain and blame for
kernel 5.3. I can't
I hope this is what you were looking for. In your message, you noted
that the login bug is likely a separate issue and it could be reported
as new. I thought that this is what I already did. If not, should I
report it again? And with what attachments? Thanks.
** Attachment added: "dmesg.0"
Thanks for the quick reply. I installed and tested 5.7-rc2 as per
instructions. The new kernel booted up to the login screen, but as
slowly as 5.4.0-25. (Over 2 minutes to the login screen.) When I logged
in with my password, all that happened was that I was returned to the
login screen. I tried
Public bug reported:
I upgraded a Ubuntu 18.04 installation to 20.04 beta on my late 2015 5k
27" iMac. The new 5.4 kernel was installed and has been updated a few
times. The former LTS kernel (4.15) was retained. When I start up the
computer with the new kernel, the process is very slow and it
apport information
** Tags added: apport-collected
** Description changed:
Related to
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1845677/comments/14
Audio works and the volume seems reasonable however the audio is
noticeably missing bass giving everything a high treble
** Also affects: linux (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/1872108
Title:
Bass not on working Lenovo ThinkPad X1 Carbon 7th gen
Public bug reported:
Related to
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1845677/comments/14
Audio works and the volume seems reasonable however the audio is
noticeably missing bass giving everything a high treble sound.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package:
Is it intentional, that package "gnome-shell-extension-prefs" package is
no longer being installed automatically in 20.04/Gnome Shell 3.36?
** Also affects: gnome-shell (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Maybe it is unrelated but whenever I activate any Gnome Extension on
20.04. it causes my lockscreen to enter an endless loop of crashing and
restarting. This can be triggered by pressing Super+L or waiting for the
timer to put the screen to sleep. As soon as you log back in, it throws
you back to
Oh, forgot to mention, the second installation attempt with previous
installation removed succeeded without error.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1820795
Title:
Ubuntu installer
Name entered was "localadmin" without the quotes
Machine name was "vader-l"
Don't believe I made any typos. I did a minimal install following this,
but with multiple changes. I first made sure to remove the btrfs '@'
subvolume and I also did a minimal install with no updates downloaded.
If I
Public bug reported:
Custom partition installation settings.
Opted to download updates and install 3rd party drivers.
Installing alongside Windows 10 and over an existing installation.
Current boot partition set to be formatted as EXT4 and mounted to /boot
Current root partition not formatted,
I realize the issue reported was related to 18.04, but I am also having
this same issue on 18.10.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1760349
Title:
Cannot log in to public open Wifi
As mentioned in the above askubuntu posting, removing the nvidia driver
got me past the problem.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1798790
Title:
Ubuntu 18.10 hangs at "started
See attachment re ls -l /home/dlf/.local/lib/python2.7/site-
packages/six.py
** Attachment added: "sixpy"
https://bugs.launchpad.net/ubuntu/+source/sagemath/+bug/1793731/+attachment/5191452/+files/sixpy
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Package changed: ubuntu => sagemath (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1793731
Title:
Sagemath installed via Synaptic package manager crashes from command
line
To manage
Public bug reported:
Downloaded and installed Sagemath, Sagemath Jupyter with Synaptic pkg
manager to OS Ubuntu 18. Crashes from command line. I have crash
report if anyone wants to see it.
Problem solved by downloading and installing directly from SageMath
mirror site.
** Affects: ubuntu
Crash report attached.
** Attachment added: "crash_report"
https://bugs.launchpad.net/ubuntu/+bug/1793731/+attachment/5191389/+files/crash_report
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
versions.
I reported this as a bug because users of recent stable kernels will not
be able to install Virtualbox through apt and presumably Ubuntu itself
will move to one such kernel sometime in the future.
~ Fox
--
You received this bug notification because you are a member of Ubuntu
Bugs
(bus, devfn) instead of pci_get_bus_and_slot(bus, devfn)
has fixed the compile error, though I am not sure if this is
correct -- perhaps I should have used pci_get_domain_bus_and_slot(0, bus, devfn)
instead.
Sorry if this is already covered ground.
~ Fox
---
~$ uname -r
4.19.0-rc3-fox+
fox
Public bug reported:
After attempting an install from instructions on https://luarocks.org/
for version 3.0.0 failed, I fell back to the version in Ubuntu's
packages. This failed to install. On Ubuntu 18.04.1 LTS
luarocks:
Installed: (none)
Candidate: 2.4.2+dfsg-1
Version table:
Public bug reported:
Running Ubuntu 18.04 Server virtual machine with UEFI enabled there
appears to be graphical issues (pixels in wrong place).
These issues can be temporarily fixed by changing the gfxmode in grub
config. But from time to time Ubuntu boots into a machine that has
pixels in
Here is a copy of a working /boot/grub/grub.cfg file that fixed a
problem.
When using QEMU, apply some of this config to broken one (UUIDs will not be the
same for you!!)
and then when grub menu appears press enter on Ubuntu option to enter non
broken machine. If you let grub timeout play out
** Attachment added: "Screenshot of graphical problem"
https://bugs.launchpad.net/ubuntu/+bug/1781987/+attachment/5164236/+files/qemu.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1781987
Public bug reported:
This bug came up after an update and restart.
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: linux-modules-4.15.0-24-generic 4.15.0-24.26~16.04.1
ProcVersionSignature: Ubuntu 4.15.0-24.26~16.04.1-generic 4.15.18
Uname: Linux 4.15.0-24-generic x86_64
ApportVersion:
Public bug reported:
Prior packagings of libcppunit-dev included cppunit-config which could
be used to determine proper compilation and link flags. (In fact this
is used by autoconf's AM_PATH_CPPUNIT to configure cppunit in auto
make).
This appears to be missing in bionic.
Public bug reported:
I don't know much, the system just sent me the message and told me to
report it.
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: linux-image-4.13.0-45-generic 4.13.0-45.50~16.04.1
ProcVersionSignature: Ubuntu 4.13.0-45.50~16.04.1-generic 4.13.16
Uname: Linux
I honestly don't know. The initial patches from April 12th of 2017 were all
I needed and I haven't messed with it since.
On Wed, Jun 6, 2018, 09:20 Andreas Hasenack,
wrote:
> @mark-fox, were those two patches the only changes you needed, or was
> the change to the awk script (re
This exact issue started happening to me a couple days ago. I didn't
notice any apparent cause. When I click or press any key, the screen
goes black for a second, then reloads with a system alert sound to the
normal login screen. After a successful login, the screen flashes the
"Switch to Greeter"
@cjjefcoat
Thanks for your advice,I have meet the same issue in virtualbox after the
ubuntu 14.04 kernel update to 116.
After downgrade the gcc to 4.8.4, and reinstall the 116 kernel and
virtualbox 5.2,it work!
** Attachment added: "Virtualbox errror info"
Anytime I have a video playing, or my laptop has been on a while, if I
touch the screen all my programs close and I get logged out.
Trying to turn off the screen via XINPUT does not work, disabling the
touchscreen does NOTHING now that ubuntu runs on wayland.
Running Ubuntu 17 right now
--
You
Public bug reported:
I ran 'Software Updater" on 9/5 and got this result. It said "current
status =half-installed" or similar language. I can only hope this this
thing will boot next time.
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: linux-image-extra-4.4.0-77-generic 4.4.0-77.98
Thank you Joseph I executed the 3 command line steps you outlined and I
think it fixed my issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1698599
Title:
package linux-image-4.10.0-22-generic
Fixed in - linux-image-3.13.0-123-generic
** Changed in: linux (Ubuntu)
Status: Incomplete => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1699460
Title:
Jetty - Service
I tried this so as to be ready for the next problem, but install does
not like the armhf bit - wants amd64.
-- Original Message --
From: Olivier Tilloy
To: rbayer...@juno.com
Subject: [Bug 1702407] Re: Startup crash after upgrading to 59.0.3071.109
That seems to have fixed the problem - Chromium is running as before the
update.
-- Original Message --
From: Olivier Tilloy
To: rbayer...@juno.com
Subject: [Bug 1702407] Re: Startup crash after upgrading to 59.0.3071.109 on
xenial
Date: Thu, 06 Jul
Turned off WiFi, Chromium browser comes up with home page (google).
Seems OK. Turn on WiFi, and it crashes.
-- Original Message --
From: Olivier Tilloy
To: rbayer...@juno.com
Subject: [Bug 1702407] Re: Startup crash after upgrading to 59.0.3071.109
No LSB modules are available.
Distributor ID:Ubuntu
Description:Ubuntu 16.04.2 LTS
Release:16.04
Codename:xenial
Linux rohan-T500 4.4.0-83-generic #106-Ubuntu SMP Mon Jun 26 17:54:43 UTC 2017
x86_64 x86_64 x86_64 GNU/Linux
chromium-browser:
Installed:
I cannot believe I am the only one to experience this bug. Is there
anything I should try which I have not yet tried?
** Changed in: chromium-browser (Ubuntu)
Status: New => Invalid
** Converted to question:
Public bug reported:
After I updated Chromium to the latest version today, it crashed as soon
as executed. When executed from a terminal, I got:
Received signal 11 SEGV_MAPERR 0010
#0 0x7f5c4b92d425 base::debug::StackTrace::StackTrace()
#1 0x7f5c4b92d80b
#2 0x7f5c4bc58390
#3
This issue looks to have been resolved in linux-image-3.13.0-123-generic
uname -a
Linux dev.ha247.co.uk 3.13.0-123-generic #172-Ubuntu SMP Mon Jun 26 18:04:35
UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
service jetty restart
* Stopping Jetty servlet engine (was reachable on
Public bug reported:
Please accept my apologies if the below information is vague.
Description:Ubuntu 14.04.5 LTS
Release:14.04
Ubuntu 3.13.0-121.170-generic 3.13.11-ckt39
After upgrading to linux-image-3.13.0-121-generic, jetty fails to start.
/var/log/jetty/out.log shows "Service
Public bug reported:
ubuntu 17.04 under vmware player on windows7 trying to set screen
resolution when applying setting the error occurred
uname -a
Linux ubuntu 4.10.0-19-generic #21-Ubuntu SMP Thu Apr 6 17:04:57 UTC 2017
x86_64 x86_64 x86_64 GNU/Linux
ProblemType: Package
DistroRelease:
I am running Ubuntu 17.04 Unity, and I get "unknown application" in
Writer regardless of whether I start it up from the dock or from a
document. With Calc, I only get it when starting up from a document. Not
sure it matters, but my 17.04 is an upgrade from 16.10, not a fresh
install. I have a
And the second part of the patch.
** Patch added: "Part 1/1"
https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/1680224/+attachment/4860739/+files/patch_1.diff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Ian produced a patch that addresses the problem, at least as far as I've
tested it. Whether the target is properly escaped or quoted, it works as
expected.
The patches (to AutoFS 5.1.2, available from git.kernel.org) are
attached and will likely be integrated into AutoFS 5.1.3.
** Patch added:
** Tags added: trusty
** Summary changed:
- postfixadmin dependencies not well defined (requires mysql-server or
postgresql, removes MariaDB)
+ postfixadmin requires non-existant package postgresql-server
** Summary changed:
- postfixadmin requires non-existant package postgresql-server
+
** Changed in: postfixadmin (Ubuntu Trusty)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1321955
Title:
postfixadmin dependencies not well defined (requires
** Tags added: trusty xenial
** Changed in: postfixadmin (Ubuntu)
Status: Fix Released => In Progress
** Changed in: postfixadmin (Ubuntu)
Assignee: (unassigned) => Michael Fox (belldandu)
--
You received this bug notification because you are a member of Ubuntu
Bugs,
*** This bug is a duplicate of bug 1321955 ***
https://bugs.launchpad.net/bugs/1321955
** This bug has been marked a duplicate of bug 1321955
postfixadmin dependencies not well defined (requires mysql-server or
postgresql, removes MariaDB)
--
You received this bug notification because
** Description changed:
Ubuntu Releases affected
Ubuntu 16.04.X LTS (Xenial Xerus)
Ubuntu 14.04.X LTS (Trusty Tahr)
Currently the package Requires either postgresql or mysql.
Mariadb is a dropin replacement for mysql and is made by the same team.
Currently postfixadmin will
*** This bug is a duplicate of bug 1682003 ***
https://bugs.launchpad.net/bugs/1682003
** This bug has been marked a duplicate of bug 1682003
postfixadmin dependencies missing mariadb
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Public bug reported:
Ubuntu Releases affected
Ubuntu 16.04.X LTS (Xenial Xerus)
Ubuntu 14.04.X LTS (Trusty Tahr)
Currently the package Requires either postgresql or mysql.
Mariadb is a dropin replacement for mysql and is made by the same team.
Currently postfixadmin will remove mariadb in favor
I would rather make it less confusing for others if possible. So i will do
what you said.
On Apr 11, 2017 11:49 PM, "Nish Aravamudan"
wrote:
> As to mariadb, https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=778794
> is the Debian bug, and was fixed in 2.93-1,
I was however planning to fix both
On Apr 11, 2017 11:49 PM, "Nish Aravamudan"
wrote:
> As to mariadb, https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=778794
> is the Debian bug, and was fixed in 2.93-1, which is in 16.10 and on.
>
> I would suggest, I think,
I'm tired of this not being fixed. So i'm fixing it myself.
** Changed in: postfixadmin (Ubuntu)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1321955
Title:
Wow 3 years no fix
** Changed in: postfixadmin (Ubuntu)
Assignee: (unassigned) => Michael Fox (belldandu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1321955
Title:
postfixad
Thanks Josh. I actually tried using ASCII codes for the characters the
day I filed the report. No dice. I've managed to make contact with Ian,
an (the?) autofs maintainer. He thinks he's narrowed the problem down to
a particular commit. If we make any progress, I'll share it here.
--
You
Experimenting with this a bit, shares with spaces in their names work
fine, but anything with $ or & fails. Ampersands are particularly
troublesome, crashing the automounter if not escaped properly.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Public bug reported:
This is probably related to #385244.
I've been unable to get a Windows administrative share (ie. C$) mounted
through Autofs. Non-administrative shares work fine. Administrative
shares are accessible with the same credentials from other Windows 10
workstations and through
We are experiencing the same symptoms with sudo (v1.8.16) as have been
previously reported in this bug.
On an Ubuntu 16.04 system short hostnames don't work in the sudoers file when
the 'fqdn' option is true (as it is by default). The documentation indicates
that the short form should still
+1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1567807
Title:
nova delete doesn't work with EFI booted VMs
To manage notifications about this bug go to:
Same problem. New install of 16.04.1.
$ gedit --> shows menu
$ sudo gedit --> does NOT show menu
$ gksudo gedit --> does NOT show menu
$ sudo -i ... # gedit --> does NOT show menu
This happens whether the menus are set for the title bar OR for the top of the
screen.
Tried reinstalling gedit. No
I get this same error on every file I've customized in /etc. Very
frustrating for trying to automate upgrades via Ansible.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1640274
Title:
1 - 100 of 857 matches
Mail list logo