It's October, 16.04 is a LTS, I updated and goodbye backups...
Thanks to the people reporting, analyzing and fixing this, but I wonder: are
there still critical bugs that make releasing a working bacula version worse
than keeping a non-functioning package in a LTS release?
--
You received this
@salisbury, I tested 3.13.11-03131104-generic, last available from
http://kernel.ubuntu.com/~kernel-ppa/mainline/ for trusty. It works:
Jun 21 14:55:29 bebop kernel: [ 365.133571] usb 3-3: USB disconnect, device
number 3
Jun 21 14:55:34 bebop kernel: [ 370.168060] usb 3-3: new full-speed USB de
Kernel Version: 3.13.0-29.53
Jun 15 01:48:48 bebop kernel: [644505.504141] usb 3-3: new full-speed USB
device number 11 using xhci_hcd
Jun 15 01:48:48 bebop kernel: [644505.538650] usb 3-3: New USB device found,
idVendor=054c, idProduct=0268
Jun 15 01:48:48 bebop kernel: [644505.538660] usb 3-3:
I had the same problem and I'd say the real bug here is that on upgrade the
file /etc/apparmor.d/usr.sbin.mysqld was not updated to allow access to
/run/mysql.[pid|sock]
Reinstalling the mysql package simply replaced the old mysql apparmor profile
with the new one that contains the correct path.
It's a generic note to the bug subscribers and to Bryce Harrington that closed
the bug.
IMHO the bug isn't closed, but there are both a fix and a workaround... so I'm
wondering what to do now.
--
wacom pressure doesn't work in QT applications
https://bugs.launchpad.net/bugs/365420
You received
I can't say the situation is very clear: you asked some "bastian-salmela-gmail"
-is he basse?- for a lspci for a problem that is:
- related to an USB tablet
- recognized by Trolltech to be caused by a QT bug
- it's already fixed in QT 4.6.0
- the linked ubuntu forum thread has a "hack" to fix it (
The bug IS in Qt, and it's been fixed:
http://www.qtsoftware.com/developer/task-
tracker/index_html?method=entry&id=210132
It's planned for release in Qt 4.6.0... any chances for a backport? :-)
--
wacom pressure doesn't work in QT applications
https://bugs.launchpad.net/bugs/365420
You receiv
The same is true for a proxy specified on the command line, i.e.:
export http_proxy=http://192.168.1.254:8080
kpackagekit
doesn't work.
The interesting thing is that even specifying a proxy in the apt.conf.d doesn't
work...
--
kpackagekit doesn't support proxy
https://bugs.launchpad.net/bugs/3
Any news about inclusion or at least reason(s) for not packaging it?
--
[needs-packaging] Packaging request for samba-vscan
https://bugs.launchpad.net/bugs/99045
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing lis
@Onjar Shinde:
I agree in full that the new problem of not being able to receive files
from Symbian devices is a new problem and should be tracked in a
different bug.
But how can you say "This bug is unlike to get fixed on gutsy"??? Let me
try to explain again the problem in gutsy: you people lef
I confirm the problem with a just-upgraded kubuntu 8.04 RC: I can't send
bt files via obex FROM the phone (Nokia E65 and Nokia E61) to the
computer.
That said, the problem isn't the one this bug is about:
/usr/lib/kdebluetooth/servers/kbtobexsrv is present, and the computer
can connect to the phon
So... in debian it's "fix released", here triaged... any news?
I've been using slapd-sql instead of slapd-perl for the problem at hand, so no
problem functionality-wise (on the contrary... I think it's a better solution).
But I must say I'm starting to see problems on how (un)responsive Ubuntu
is
I agree with you that the problem is often manpower, but here we have a bigger
problem: a maybe, especially out of UE, minor feature has been broken by
adopting a beta version of a package. Was it necessary? No. Does it improve
user experience? No. This beta has also other problems, mainly the
I'd like to have some 'official' statement on what the problems are, and
on what is the timeframe for a "supported" solution.
I can compile kdebluetooth myself, but I'm using Kubuntu because it has
a good packaging system, not because I like to compile important
features from scratch because someo
Any news on this problem? I just booted into windows to transfer files
from my cellphone to be able to do end-of-month accounting.
Can we have a backport from hardy (since hardy package don't work in
Gutsy due to kdelibs dependencies)? Or, can we have the old package
back, since the new beta remov
*** This bug is a duplicate of bug 115616 ***
https://bugs.launchpad.net/bugs/115616
I found out I was wrong: maybe I have too many computers... I did remove
EVMS, but from the wrong computer :-P
I *confirm* that you cannot mount some additional partitions (I'd say
regardless of which filesys
Sorry for the late reply...
Yes, basically I have to add a softlink to the new location of saslauthd
socket in the init script, since it gets "purged" with the whole ram-
based /var/run filesystem.
The situation is:
- I have to have the saslauthd socket inside postfix chroot
- If I move the socke
*** This bug is a duplicate of bug 115616 ***
https://bugs.launchpad.net/bugs/115616
This bug is *NOT* a duplicate of bug #115616
The fact that the reporter sees evms errors in /var/log/messages does
NOT mean he can mount XFS volumes by removing it.
I confirm that:
- I don't have EVMS insta
I quite agree with you Scott about a fix being useful for people that install
Feisty's Hylafax without backports.
That said, Hylafax has almost always required/encouraged a good deal of "hand
tuning" of those scripts, for example to have PDFs instead of TIFFs in emails,
so I'm not sure how the f
This exact problems is reported in #79371. I didn't spot it because the
original title is about the PID of saslauthd.
--
Can't use saslauthd to authenticate both postfix and cyrus due to
/var/run/saslauthd being on tmpfs
https://bugs.launchpad.net/bugs/138931
You received this bug notification b
In Feisty there's a note in /etc/default/saslauthd telling the user to
add a parameter to saslauthd command line so that it opens its socket
inside postfix chroot. It's not a perfect solution if you need to use
saslauthd for other programs (cyrus...) since you can't symlink
/var/run/saslauthd to th
Public bug reported:
Binary package hint: sasl2-bin
The problem is quite complex, and has at least 2 easy workarounds. Maybe
updating some docs or comments in /etc/default/saslauthd can be enough.
Scenario
I've set up a server with users in LDAP. Both postfix and cyrus need to
authenticate the
No, the usual day to day operations were and are ok with every package manager
i tried.
I use regularly aptitude, kpackage and obviously adept to update, upgrade and
install packages.
Only the check for a new upgrade program on rookery.ubuntu.com was using a
DIRECT connection and failing.
It ma
The new version installs and seems to run ok. The reported bugs are fixed.
I'll check this version for a few days to see if there are other obvious
problems.
Thanks,
Roberto Maurizzi
--
notify dont' sent pdf attachment, problems with faxrecvd and notify scripts
https://bugs.lau
Public bug reported:
Hylafax server version 4.3.1-3, as shipped with 7.04, has *serious*
problems. It would seems to me that it would qualify for a fixed
package, since it break functionality that was present in previous
releases.
There are 3 problems:
- the default for the BASE64ENCODE does
*** This bug is a duplicate of bug 48682 ***
https://bugs.launchpad.net/bugs/48682
Here the problem is not that proxy settings in the browsers are ignored, but
that the env variable http_proxy is ignored too, but *only* for the upgrade
check.
The effect is insidious because the rest of the p
.3.30-2)
Short version: defining a module to manage perl backend, you can't use
any perl module without getting unresolved symbols errors.
Ciao,
Roberto Maurizzi
** Affects: openldap2.3 (Ubuntu)
Importance: Undecided
Status: New
--
perl backend can't use dynamically
oaded module.
Same applies for 2.3 as shipped in Ubuntu Feisty.
Ciao,
Roberto Maurizzi
--
perl backend can't use dynamically loaded modules (DBI, POSIX...)
https://bugs.launchpad.net/bugs/90812
You received this bug notification because you are a member of Ubuntu
Bugs, which is the b
Public bug reported:
Binary package hint: adept
I was trying to update from Edgy to Feisty on a computer that's on a very
restrictive network (outside access is via http proxy only).
As such I configured both Konqueror and Firefox with a proxy setting script,
and added to /etc/profile an export
I've just tested a rebuild of the openldap package with the 'current' version
of the perl system, and the error is the same.
The error seems to be a real one, not a simple packaging problem...
Ciao,
Roberto
--
perl backend can't use dynamically loaded modules (DBI, POSIX...)
https://launchpa
to the script you get the same error.
Changing the "use"d module changes the situation only slightly, for
example substituting "use POSIX" with "use DBI" you get:
slapd: symbol lookup error: /usr/lib/perl5/auto/DBI/DBI.so: undefined
symbol: Perl_Tstack_sp_ptr
** Also affects: openldap2.2 (Ubuntu)
Importance: Undecided
Status: Unconfirmed
--
perl backend can't use dynamically loaded modules (DBI, POSIX...)
https://launchpad.net/bugs/90812
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubun
32 matches
Mail list logo
