This fixed the problem. Thanks! Although, I wonder if this will affect
others who try to upgrade to 24.04 when it releases tomorrow? That's
part of the reason that I went ahead and posted the bug rather than just
waiting for the release date.
--
You received this bug notification because you
No problem. Let me know if you need anything else.
** Attachment added: "sources.list.d.tar.gz"
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2062042/+attachment/5766910/+files/sources.list.d.tar.gz
--
You received this bug notification because you are a member of
Public bug reported:
I receive the message following message when performing a "sudo do-
release-upgrade -d" on both my Ubuntu 23.10 system(s):
Fetched 23.8 kB in 0s (0 B/s)
Reading package lists... Done
Building dependency tree... Done
Will do, thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2047447
Title:
No valid source.list found while upgrading from mantic to noble
To manage notifications about this bug go to:
I can confirm that I have the same issue on two separate 23.10-based
systems, but removing vscode.list from /etc/apt/sources.list.d/ has no
effect. I get the following warning with "sudo do-release-upgrade -d":
Updating repository information
No valid sources.list entry found
While scanning
Public bug reported:
After upgrading my Ubuntu 20.04 systems to the latest updates, which
installed openjdk-8-jdk-headless version 1.8.0_292, I'm getting
exceptions thrown in a variety of my code:
Caused by: java.security.KeyStoreException: Key protection algorithm not
found:
The kazam 1.4.5-3ubuntu0.1 fixes this bug for me. Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1876322
Title:
kazam on Focal: No audio recorded
To manage notifications about this bug go
OK I found out that I had adwaita-icon-theme installed but not adwaita-
icon-theme-full. After installing the latter all my Evolution icons now
exist.
I'm still not sure what other packages I might be missing...
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Also if anyone has any ideas about how to fix my system, other than
reinstalling from scratch, I'm definitely interested...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1883980
Title:
Upgrade
Public bug reported:
Description:Ubuntu 20.04 LTS
Release:20.04
dpkg:
Installed: 1.19.7ubuntu3
Candidate: 1.19.7ubuntu3
Version table:
*** 1.19.7ubuntu3 500
500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages
100 /var/lib/dpkg/status
This past
Public bug reported:
Package Dependency Information:
openshot-qt
Depends: libjs-jquery
Depends: python3-openshot
Depends: python3-pyqt5
Depends: python3-pyqt5.qtsvg
Depends: python3-pyqt5.qtwebkit
Depends: python3-zmq
Depends:
python3:i386
python3
Breaks: openshot
Hey, if my assertion incentivizes someone to figure out how to do that,
I'm more than willing to admit I was wrong :).
The thing is, IMO "fast enough" for a desktop calculator is pretty darn
fast. In my opinion the current integrated DEB version is already slow
enough to be frustrating, so
It is not physically possible to ever get a snap to start as fast as a
native application. The entire purpose of a snap is that it uses its
own set of dependencies, which means that by definition it cannot share
those dependencies with other applications on the system, which means
that they must
I'm not sure why the "is 2s too slow to start" is the question being
asked. Who starts and stops their calculator multiple times in a row?
That's not a realistic use-case for the vast majority.
Most people need a calculator once a day or every few days, and a
desktop calculator is not an
Is this going to be fixed in disco?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1754671
Title:
Full-tunnel VPN DNS leakage regression
To manage notifications about this bug go to:
Although this problem is easy to fix once you know what to do, I don't
know if it should be only "Medium" importance because the impact is
massive: no DNS is available. If you're not technically inclined enough
to know to go poking around /etc/resolv.conf if DNS breaks, you would
never be able to
I've had this happen to me with Ubuntu 18.10 as well.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1793427
Title:
network-manager-fortisslvpn breaks mode of /run/systemd/resolv/stub-
resolv.conf
I wasn't having any problems with Ubuntu 18.04 but ever since I upgraded
to Ubuntu 18.10 gnome-shell seems to crash two out of every three times
the screensaver starts.
I used ubuntu-bug on a /var/crash file but I have no idea what happened
to it: it showed me the info in a window and I said go
I was seeing this same warning. The only overlap of extensions with the
list above and my list (I only use 3 extensions) is 'system-
moni...@paradoxxx.zero.gmail.com'.
I realized I had installed that extension from source rather than
through the extensions website since it needed to be built
This is quite frustrating. I wish it would be addressed... somehow...
(still getting this problem on 18.04 LTS).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1080978
Title:
apport forcefully
Aha, looking at issue #109 then checking journalctl I see:
Oct 09 09:34:34 homebase kernel: NVRM: API mismatch: the client has the version
340.107, but
NVRM: this kernel module has the version
340.106. Please
NVRM: make sure
Seems like it might be related to this:
https://gitlab.gnome.org/GNOME/cogl/issues/1 which similarly was
reported here: https://gitlab.gnome.org/GNOME/gnome-control-
center/issues/109
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: "GDB backtrace for crash in libcogl"
https://bugs.launchpad.net/ubuntu/+source/cogl/+bug/1730241/+attachment/5199322/+files/libcogl-crash.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I just restarted Evolution (but did not reboot my system or make any
other changes) and now Evolution is crashing for me in the identical way
described here. I literally just quit Evolution, it was running fine,
and restarted it and now it just crashes with the same stacktrace shown
above, a null
Public bug reported:
(I'm not able to use ubuntu-bug as it fails with a 503 error trying to
connect to the crash server)
I'm using Ubuntu 18.04.1 on 64bit Intel with:
network-manager1.10.6-2ubuntu1
network-manager-fortisslvpn1.2.8-1build1
Public bug reported:
I'm using Ubuntu 18.04.1 LTS with network-manager-fortisslvpn
1.2.8-1build1 installed.
To do this I simply ran "sudo apt install network-manager-fortisslvpn-
gnome".
After setting up a VPN interface using this plugin, attempting to
connect fails immediately and using
Oops, this problem still occurs with glibc 2.27, my mistake.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1678510
Title:
gprof: get empty output
To manage notifications about this bug go to:
Looks like this is fixed in glibc 2.27.
https://sourceware.org/bugzilla/show_bug.cgi?id=22284
** Bug watch added: Sourceware.org Bugzilla #22284
https://sourceware.org/bugzilla/show_bug.cgi?id=22284
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Also affects: gcc-7 (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/1678510
Title:
gprof: get empty output
To manage notifications about this
Public bug reported:
Anki prints the following warning to stdout on startup:
This is an BETA build - please do not package it up for Linux
distributions
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: anki 2.1.0+dfsg~b36-1
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname:
Sorry it took me so long to respond.
I still see this problem in Ubuntu 17.10. The problem does not occur in
Ubuntu 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/1754726
Title:
anki could
Public bug reported:
sudo apt install anki
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some
I'm not sure why it's being asserted that these two uses are mutually
incompatible, especially since I've been using them in a coordinated way
forever and can still do so (at the expense of junking systemd-resolve
and going back to using dnsmasq and a custom configuration, which is
obviously a big
Andreas: unfortunately disallowing short name lookups is not acceptable:
many environments use short names in embedded URLs all over the place,
and without domain search paths the entire environment is rendered
completely unusable (e.g., URLs are simply https://tools/foo or
https://wiki/foo or
Hi Sebastien, thanks for your interest. This issue is causing me
extreme pain. I believe I'm going to have to reconfigure N-M to use the
old-style dnsmasq setup and throw out systemd-resolve pretty soon.
It's not clear to me whether this is an N-M bug vs. a systemd bug, but
I'm happy to file
Public bug reported:
When I open the gnome-control-center, I see the following menu items
down the left side: Wi-Fi, Bluetooth, Background, Notifications, Search,
Region & Language, Universal Access, Online Accounts, Privacy, Sharing,
Sound, Power, Network, Devices (with a sub-menu). Screenshot
I'm not sure I understand what you mean. In a typical configuration you
never send "foo" to the nameservice, there's always a search domain and
those lookups are always tried first (because the default value for the
ndots is 1). This is handled by the libc resolver linked into every
program,
Public bug reported:
I actually have no idea if this is really a Nautilus issue but didn't
know where else to file it.
I have a fresh install of ubuntu 17.10. I start nautilus (using File).
I right-click on a folder and select "Local Network Share". When I
select "Share this folder" it says
To be clear, they are NOT updated in /etc/resolv.conf. They ARE updated
in /run/NetworkManager/resolv.conf, but that has no effect since we're
not using that for resolution: instead we're using systemd-resolve.
And as I noted above, it does appear that systemd-resolve is notified
about the
Public bug reported:
I connect to work with openvpn through network-manager-openvpn. I'm
selecting automatic (DHCP) to get an IP address, and "Use this
connection only for resources on its network" to support split
tunneling.
In the last few versions of Ubuntu I used, this all worked fine. In
Yes, that version is OK (I'm on 16.10 so mine is a bit newer). If you
check /usr/share/doc/dnsmasq-base/changelog.Debian.gz on your system you
should see info related to this bug in that changelog.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Shawn B it sounds like your issue might be related to this one, since
it's fixed by restarting dnsmasq. Do you have the newer dnsmasq version
(you need dnsmasq-base 2.76-4ubuntu0.1 or better)?
Just to note: it's definitely true that this bug will impact VPN users;
that's how I ran into it.
It sounds like a different bug to me, if changing networkmanager fixes
it without changing dnsmasq. I would file a new Launchpad bug with all
the details you can provide. You can add a comment to this issue with a
link.
In particular, please specify:
* If you're using IPv4 vs. IPv6
* If you
I think the problems being reported by NJ and Lukas at least, are
different issues and you should file a new report about them. I can't
say about GammaPoint because the description there ("DNS leaks") is not
understandable to me.
This issue has the following characteristics: DNS lookups fail,
Just curious if there's more work needed here before this fix moves out
of proposed and into standard updates for xenial / yakkety, or if not
then is there a timeline when that transition is normally expected?
I'm currently recommending to users that they reset NetworkManager by
hand when they
Just to add a note: this issue also occurs when using VPNs: I use
NetworkManager OpenVPN and when I start up the connection I can't
resolve DNS hosts from the VPN DNS server until I run "sudo killall -HUP
NetworkManager" or similar. This has to be done every time the VPN goes
down / comes back
Public bug reported:
This issue happens in Ubuntu 16.04 LTS as well.
When I connect via tun to an OpenVPN server, my DNS lookups do not
succeed even though the OpenVPN service is started correctly and does
provide the correct information. If I force NetworkManager to load its
configuration via
Just want to point out that "chroot installs" or netboot installs are
NOT the only places this breaks. I did a a straightforward upgrade (via
do-release-upgrade) from Ubuntu GNOME 16.04.n (latest packages
installed) to Ubuntu GNOME 16.10, on a standard desktop system where the
wired network was
*** This bug is a duplicate of bug 1545800 ***
https://bugs.launchpad.net/bugs/1545800
In order to recreate this bug I had to do the following:
1. Open nemo
2. Navigate away from the default location, for example to $HOME/Pictures
3. Open a new tab
4. Close the new tab
5. Open a new tab again
Note that there's a more comprehensive patch already available in the
linked Debian bug report (see the remote bug watches box to the right).
My hope would be someone would go even further and update the script to
show some kind of warning, at least, if unknown tags are seen so that
future
Public bug reported:
java-common 0.56ubuntu2
openjdk-8-jre-headless:amd64 8u91-b14-0ubuntu4~16.04.1
Newer versions of openjdk-8-jre-headless provide a .jinfo file that uses
a new tag "jdkhl" (for JDK headless). Since update-java-alternatives
doesn't know anything about that
** Tags added: kernel-fixed-upstream
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1593261
Title:
Using "splash" Linux boot option causes IPMI console view to blank
To manage notifications about
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1593261
Title:
Using "splash" Linux boot option causes IPMI console view to blank
I've tested with 4.7-rc3. I first booted with this kernel without the
"splash" to make sure it booted, then I added back the "splash" and re-
ran update-grub, and booted that. That also worked. I verified by
examining dmesg that the vt.handoff=7 WAS present on the kernel command
line when it
This is a blade server install and getting enough packages installed to
run apport-collect is difficult. I've attached the results of running
dmesg when I see the error (dmesg-bad.out) and when I don't see the
error (dmesg-good.out).
While doing this I discovered the REAL cause of the problem,
** Attachment added: "dmesg output for "good" boot"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1593261/+attachment/4685028/+files/dmesg-good.out
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of
Public bug reported:
I'm using a set of blade servers with SuperMicro BIOS and IPMI console
viewing capabilities. I use the Ubuntu netboot options with a PXE
server to install.
I've installed Ubuntu 12.04 and 14.04 on these systems, and everything
works great.
However, when I install Ubuntu
Looks the same as this bug: https://bugzilla.redhat.com/show_bug.cgi?id=1056820
I tried the suggested workaround of adding "export NO_AT_BRIDGE=1" to .bashrc
and that made the warning message go away.
It looks like the version of ibus that red hat switched to might have
some bug fixes over
I see this error when starting gedit or nemo from the command line.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1526042
Title:
WARNING Couldn't connect to accessibility bus Failed to connect to
A fix for this has been sitting in wily-proposed for about 3 weeks now.
I have no idea what it takes to get through that into a regular update.
It's been handled as Bug #1529445 so look there for more details. Maybe
someone knows how to move it forward through the process?
--
You received this
Public bug reported:
I've been using Pidgin since forever and it's been very stable, but ever
since I've updated to 15.10 I'm getting semi-regular (once or twice a
week) crashes.
Ubuntu GNOME 15.10
Pidgin 1:2.10.11-0ubuntu4
Here's a stack trace from my latest crash a few minutes ago, after I
** Description changed:
I've been using Pidgin since forever and it's been very stable, but ever
since I've updated to 15.10 I'm getting semi-regular (once or twice a
week) crashes.
Ubuntu GNOME 15.10
Pidgin 1:2.10.11-0ubuntu4
Here's a stack trace from my latest crash a few
I tested evolution 3.16.5-1ubuntu3.1 and the problem has been resolved.
Thanks!
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Updating the BIOS seems to have fixed it: no crashes since then. Thanks
for the support!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1476702
Title:
Xorg crash when using Spotify client
To
Public bug reported:
I'm using Evolution 3.16.5-1ubuntu3 in Ubuntu GNOME 15.10, latest
packages.
My email starts by default in Plain Text mode. However sometimes I want
to switch to "HTML" mode. When I do this, I get HTML-formatted email
HOWEVER no matter what I do my font is still always
OK I've updated my bios:
$ sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date
0708
12/25/2012
I used to get crashes just by semi-vigorous scrolling in the Spotify
window but a session of clicking and scrolling so far hasn't reproduced
the crash. I'll keep trying for a while.
Public bug reported:
Ever since I upgraded from Ubuntu GNOME 14.04 to Ubuntu GNOME 15.04,
I've had my entire desktop crash relatively quickly when using Spotify,
if I mess around with the client much. Just starting the client is no
problem, and it plays songs OK, but for a while whenever I
The problem with testing the mainline kernel is that the failure is with
the wireless device, and that uses a proprietary broadcom driver on the
macbook (bcmwl). I'm not sure how to get a copy of that driver that
will work with a newer kernel. However I'll investigate and see what I
can do.
--
I'm not able to compile bmcwl-kernel-source for the latest mainline
kernel (linux-
headers-4.1.0-040100rc4-generic_4.1.0-040100rc4.201505181436_amd64) as
the compilation fails:
/var/lib/dkms/bcmwl/6.30.223.248+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c: I
n function ‘wl_cfg80211_get_station’:
apport information
** Tags added: apport-collected vivid
** Description changed:
I've just installed Ubuntu GNOME 15.04 64bit on my Macbook Pro, and
everything seems to work great including suspend/resume, EXCEPT that
after I resume my wireless network does not start. When the system
apport information
** Attachment added: CRDA.txt
https://bugs.launchpad.net/bugs/1448882/+attachment/4403523/+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/1448882
Title:
Resume
apport information
** Attachment added: IwConfig.txt
https://bugs.launchpad.net/bugs/1448882/+attachment/4403525/+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/1448882
Title:
apport information
** Attachment added: JournalErrors.txt
https://bugs.launchpad.net/bugs/1448882/+attachment/4403526/+files/JournalErrors.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: CurrentDmesg.txt
https://bugs.launchpad.net/bugs/1448882/+attachment/4403524/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1448882
apport information
** Attachment added: UdevDb.txt
https://bugs.launchpad.net/bugs/1448882/+attachment/4403534/+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/1448882
Title:
apport information
** Attachment added: PulseList.txt
https://bugs.launchpad.net/bugs/1448882/+attachment/4403532/+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/1448882
apport information
** Attachment added: ProcModules.txt
https://bugs.launchpad.net/bugs/1448882/+attachment/4403531/+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/1448882
apport information
** Attachment added: ProcInterrupts.txt
https://bugs.launchpad.net/bugs/1448882/+attachment/4403530/+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: Lsusb.txt
https://bugs.launchpad.net/bugs/1448882/+attachment/4403528/+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/1448882
Title:
apport information
** Attachment added: Lspci.txt
https://bugs.launchpad.net/bugs/1448882/+attachment/4403527/+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/1448882
Title:
apport information
** Attachment added: WifiSyslog.txt
https://bugs.launchpad.net/bugs/1448882/+attachment/4403535/+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/1448882
apport information
** Attachment added: RfKill.txt
https://bugs.launchpad.net/bugs/1448882/+attachment/4403533/+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/1448882
Title:
apport information
** Attachment added: ProcCpuinfo.txt
https://bugs.launchpad.net/bugs/1448882/+attachment/4403529/+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/1448882
My macbook is at work but I'll bring it home this weekend and see if I
can do more investigation.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1448882
Title:
Resume on Macbook Pro doesn't restart
Public bug reported:
I've just installed Ubuntu GNOME 15.04 64bit on my Macbook Pro, and
everything seems to work great including suspend/resume, EXCEPT that
after I resume my wireless network does not start. When the system
first wakes up I very briefly see a ? icon for the wireless, then it
Thank you Iain! Is there any possibility this can get backported to
14.04? As an LTS release, it would be REALLY nice to have this fix
there too... I think this patch applies cleanly to 3.11 as well as 3.12.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
If you know of another way, than filing a bug like this one, I urge you
to pursue it...
** Tags added: patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1247366
Title:
Evolution is missing
Just for completeness I'm adding the patch used to fix this issue
upstream.
** Patch added: Patch for Gnome bug 1247366
https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1247366/+attachment/4331521/+files/bug-1247366.patch
--
You received this bug notification because you are a
Well, first it has to get fixed in Ubuntu, in any version: currently
there's no fix even in the upcoming 15.04.
Once that happens we can talk about whether it's possible to backport
it.
** Tags removed: patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Milan Crha has posted a fix for the next release of Evolution, which may
or may not be straightforward to cherry-pick back to the current
release.
See: https://bugzilla.gnome.org/show_bug.cgi?id=743109
and: https://git.gnome.org/browse/evolution/commit/?id=0b91d60
--
You received this bug
Hm. It seems that newer versions of Evolution have completely removed
support for runtime detection of the underlying spam filtering facility
in the plugin, so my simple patch in comment #18 is not sufficient and
more work is needed.
See https://bugzilla.gnome.org/show_bug.cgi?id=743109 for more
I believe this can be fixed with a simple patch to the rules file in the
Evolution Ubuntu package: if we set the BOGOFILTER environment variable
before we run configure then whatever value it has will be used during
the build without checking, and at runtime if the program exists the
plugin will
Is there a reason we can't just go get the patches that Ian Kent already
provided for Fedora (see my link to the Red Hat bugzilla entry, which
contains references to RPM versions that fix the problem) and apply them
here and/or in Debian since the bug exists there as well?
--
You received this
Is there a reason we can't just go get the patches that Ian Kent already
provided for Fedora (see my link to the Red Hat bugzilla entry, which
contains references to RPM versions that fix the problem) and apply them
here and/or in Debian since the bug exists there as well?
--
You received this
I believe this is a duplicate of Bug #1386869
There's a workaround in the comments of that bug. HTH!
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to autofs in Ubuntu.
https://bugs.launchpad.net/bugs/1387459
Title:
autofs stops
This appears to be a bug in the version of autofs that Ubuntu is
shipping. See this report from ArchLinux:
https://bugs.archlinux.org/task/38379
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to autofs in Ubuntu.
Also there's a problem reported in Fedora against 5.0.7, but apparently
still present for 5.0.8:
https://bugzilla.redhat.com/show_bug.cgi?id=1038356
** Bug watch added: Red Hat Bugzilla #1038356
https://bugzilla.redhat.com/show_bug.cgi?id=1038356
--
You received this bug notification because
I believe this is a duplicate of Bug #1386869
There's a workaround in the comments of that bug. HTH!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1387459
Title:
autofs stops working after
This appears to be a bug in the version of autofs that Ubuntu is
shipping. See this report from ArchLinux:
https://bugs.archlinux.org/task/38379
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1386869
Also there's a problem reported in Fedora against 5.0.7, but apparently
still present for 5.0.8:
https://bugzilla.redhat.com/show_bug.cgi?id=1038356
** Bug watch added: Red Hat Bugzilla #1038356
https://bugzilla.redhat.com/show_bug.cgi?id=1038356
--
You received this bug notification because
1 - 100 of 365 matches
Mail list logo
