I have installed 3.17-31ubuntu0.10.04.3 on lucid after purging the previous
version including our hand crafted upstart configuration.
- Installation went fine
- I have tested the function as a NIS client successfully
- starting after reboot works, it also survives a suspend/resume cycle
But I
just to add a data point: starting 2012-04-19 my lucid machine is
working with 3.17-31ubuntu0.10.04.3 from proposed with. A few nis
accounts are being used regularly. There have been a large number of
suspend resume cycles and various reboots without any nis related
problems.
--
You received
it is an error for ypbind to not start correctly when the network
interface is managed by network-manager and thus comes up a bit slowly
of course, changing the configuration to not rely on network-manager, as
explained in comment #3 is a workaround
still i would consider this a bug: the
Public bug reported:
on a (freshly installed) system with nis authentication, postfix is no longer
able to read aliases from the nis table mail.aliases.
in 10.04 it worked
symptoms are:
- errors in /var/log/mail.log:
warning: nis:mail.aliases is unavailable. unsupported dictionary type: nis
-
on the system where I had the problem I did this to verify the fix
- removed workarounds in main.cf
- sent emails and verified that they trigger the error and remain in the queue
- installed 2.9.3-2~12.04.4
- bug is gone, mail works normally
** Tags removed: verification-needed
** Tags added:
several people have commented that they have the same or similar
problems
** Changed in: autofs5 (Ubuntu)
Status: Incomplete = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to autofs5 in Ubuntu.
I tested the package from maverick-proposed against the current package
from maverick: both of the problems that were discussed in this bug
report are now gone (squid starts sucessfully with network not being
available yet, resolvconf script reloads the squid configuration and
does not kill squid)
Public bug reported:
this is a leftover issue from bug
https://bugs.launchpad.net/ubuntu/+source/squid/+bug/561750
I am creating a new bug report to leave complicated history behind.
The maverick squid package 2.7.STABLE9-2ubuntu5.1 calls 'reload squid' in
/etc/resolvconf/update-libc.d/squid
well, i guess originally this bug had been about 'reload' not working
correctly (#7), but focus has shifted over time.
To keeps things simple I have created a new bug report for the remaining
maverick problem at
https://bugs.launchpad.net/ubuntu/+source/squid/+bug/809526
--
You received this
this is an issue in maverick only
- lucid already uses 'restart squid' - ok
- natty uses 'reload squid' and this works fine due to some other changes - ok
- I do not know about oneiric but I guess it works like natty
yes, the fix is indeed as you describe it in comment #1.
I applied that fix by
** Changed in: squid (Ubuntu)
Status: Incomplete = New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to squid in Ubuntu.
https://bugs.launchpad.net/bugs/809526
Title:
squid 2.7.STABLE9-2ubuntu5.1, reload kills squid, called in
tested with lucid 10.04.3 - OK
procedure:
with old package
- access the web through squid
- init 1
- init 2
- ps aux | grep squid # - squid not running
with proposed package
- access the web through squid
- init 1
- init 2
- ps aux | grep squid # - squid IS running
- access the web through squid
tested with an up-to-date maverick system
same procedure as above - OK
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to squid in Ubuntu.
https://bugs.launchpad.net/bugs/561779
Title:
squid is not started on runlevel transition 1 - 2
Public bug reported:
Binary package hint: samba-common
on update to jaunty, configuration questions are asked in curses dialog
inside the terminal-window of the update manager.
But debconf is configured to use kde, and questions for other packages
actually have been asked with kde dialogs
**
the question asked in the terminal window was do you want to keep your
smb.conf or install the one provided in the package
below are some excerpts from /var/log/dist-upgrade/term.log (which is in
German, but you will identify what happens)
for other packages where the questions were asked
In my setup this bug causes excessive boot delays. I want to question
the wishlist importance.
--
NIS upstart dependancy broken for lucid
https://bugs.launchpad.net/bugs/569757
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nis in
this bug is still present in karmic
lines in auto.master starting with /- seem to be just ignored
** Changed in: autofs (Ubuntu)
Status: Won't Fix = Confirmed
--
AutoFS direct maps not working with NFSv4 exports
https://bugs.launchpad.net/bugs/369682
You received this bug notification
Indeed, a default install of karmic-autofs has
DISABLE_DIRECT=1
in /etc/default/autofs
This is also documented in /usr/share/doc/autofs/README.direct
A workaround might be to use autofs5.
According to the original poster the behaviour changed at some point in
time. The reason remains
Public bug reported:
Binary package hint: squid
after booting, squid starts normally, and then stops again immediately.
There is no error (see logfile).
After that i can start squid with 'sudo start squid' and it works
flawlessly (this bug report is made through it).
ProblemType: Bug
** Attachment added: squid log file
http://launchpadlibrarian.net/43955964/cache.log
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/43955337/Dependencies.txt
--
squid starts and stops immediately (after upgrade from karmic to lucid)
Public bug reported:
Binary package hint: squid
when you go to runlevel 1 for maintenance with 'telinit 1', squid is
stopped correctly
when you go back to runlevel 2 with 'telinit 2' squid is not started
because /etc/init/squid.conf does not contain a condition for that.
in karmic, squid
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/43958720/Dependencies.txt
--
squid is not started on runlevel transition 1 - 2
https://bugs.launchpad.net/bugs/561779
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
I have an ethernet interface with a static IP address, there is no
traffic routed to the internet over this interface.
Secondly there is a dsl-connection (pppoe) that provides the route to
the internet.
See also attached file /etc/network/interfaces
But I also have changed /etc/default/squid to
** Attachment added: /etc/default/squid
http://launchpadlibrarian.net/44118845/squid
--
squid starts and stops immediately (after upgrade from karmic to lucid)
https://bugs.launchpad.net/bugs/561750
You received this bug notification because you are a member of Ubuntu
Server Team, which is
$ grep squid /var/log/syslog
Apr 14 07:38:33 rechner6 init: squid main process (1086) killed by HUP signal
$ grep init: /var/log/syslog
Apr 14 07:38:33 rechner6 init: squid main process (1086) killed by HUP signal
Apr 14 07:38:33 rechner6 init: ssh main process (1095) terminated with status
255
- there is no respawn option in /etc/init/squid.conf (but I think this
wouldn't normally be a problem, except when squid crashed by itself)
- there is exactly one thing that does something to squid when the dsl-
interface is brought up (I have resolvconf installed which is suggested
by the squid
Runlevel changes have been an essential functionality of unix / linux
for a long time. You could use them for regular administration tasks.
Now this stopped to work. This bug is a regression.
--
squid is not started on runlevel transition 1 - 2
https://bugs.launchpad.net/bugs/561779
You
Public bug reported:
Binary package hint: convmv
Hello!
if you convert to utf-8, files already encoded in utf-8 are skipped
according to the manpage.
This only works when you give the -t option as -t UTF8 but not when
you use -t UTF-8 or -t utf8 or similar.
All versions of the -t option will
** Summary changed:
- when converting to utf-8 autodetection of already utf-8 encoded files only
partly works
+ -t UTF8 and -t UTF-8, resp., show different and unexpected behaviour wrt.
conversion and autodetection
** Description changed:
Binary package hint: convmv
Hello!
- if you
the problem I reported is fixed in the current upstream version 1.10
Bug 46788 reports the same problem differently
--
-t UTF8 and -t UTF-8, resp., show different and unexpected behaviour wrt.
conversion and autodetection
https://launchpad.net/bugs/60238
--
ubuntu-bugs mailing list
Public bug reported:
Hello,
I installed kubuntu from CD on PC. There is no dhcp-server in the net.
Therefore, after installation I use K-SystemSettings- NetworkSettings
to set an IP for the network interface eth0.
Before I do this the first lines of /etc/hosts looks like
127.0.0.1 localhost
Public bug reported:
Binary package hint: hplip
you may be interested in this bug I just reported:
66813
https://launchpad.net/distros/ubuntu/+source/knetworkconf/+bug/66813
** Affects: hplip (Ubuntu)
Importance: Undecided
Status: Unconfirmed
--
does not start because of bad
Public bug reported:
Hello,
I installed kubuntu from CD on PC. There is no dhcp-server in the net.
Therefore, after installation I use K-SystemSettings- NetworkSettings
to set an IP for the network interface eth0.
Before I do this the first lines of /etc/hosts looks like
127.0.0.1 localhost
** Changed in: apt (Ubuntu)
Status: New = Confirmed
--
apt cron.daily script sleeps a random amount of time twice
https://bugs.launchpad.net/bugs/262015
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
did not remember clearly.)
--
Ernst Kloppenburg
Heimerdingen, Germany
--
can't upgrade from hardy to intrepid
https://bugs.launchpad.net/bugs/281218
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu
Public bug reported:
this is probably not a bug in debconf, but in the update process in
general
I started with
- a current hardy system without any foreign packages
- debconf set to use the frontend kde
then I started the upgrade with adept_manager --dist-upgrade-devel
- the first few
Public bug reported:
Binary package hint: gconf2-common
during the upgrade from hardy to intrepid beta this message was output by the
upgrade tool with the caption gconf2-common could not be installed
Unterprozess post-installation script gab den Fehlerwert 139 zurück
** Affects: gconf
Public bug reported:
Binary package hint: update-manager
hello!
about halfway through installing all the updates on an update from hardy
to intrepid beta, after a long period without user interaction, problems
began.
first, error dialogs were displayed for about 5 different packages with
** Attachment added: term.log
http://launchpadlibrarian.net/18577484/term.log
--
crashed during installing packages on upgrade vom hardy to intrepid beta (after
about half of the packages had been upgraded)
https://bugs.launchpad.net/bugs/283942
You received this bug notification because
** Attachment added: main.log
http://launchpadlibrarian.net/18577492/main.log
--
crashed during installing packages on upgrade vom hardy to intrepid beta (after
about half of the packages had been upgraded)
https://bugs.launchpad.net/bugs/283942
You received this bug notification because
** Attachment added: apt-term.log
http://launchpadlibrarian.net/18577503/apt-term.log
--
crashed during installing packages on upgrade vom hardy to intrepid beta (after
about half of the packages had been upgraded)
https://bugs.launchpad.net/bugs/283942
You received this bug notification
** Attachment added: apt.log
http://launchpadlibrarian.net/18577506/apt.log
--
crashed during installing packages on upgrade vom hardy to intrepid beta (after
about half of the packages had been upgraded)
https://bugs.launchpad.net/bugs/283942
You received this bug notification because you
while doing 'dpkg --configure -a' now, I get a lot of the following
errors, which might be related.
*** stack smashing detected ***: /usr/bin/perl terminated
btw., are there any suggestions for getting out of this and completing
the upgrade?
--
crashed during installing packages on upgrade vom
I found a related bug, 270626. They had a similar problem and traced it
down to the debconf KDE frontend not working properly.
Thus my previous bug 283930 is also related (or duplicate?)
The base issue is to keep the debconf kde frontend working during an
upgrade.
My suggestion for a solution
*** This bug is a duplicate of bug 283942 ***
https://bugs.launchpad.net/bugs/283942
** This bug has been marked a duplicate of bug 283942
crashed during installing packages on upgrade vom hardy to intrepid beta
(after about half of the packages had been upgraded)
--
debconf kde
*** This bug is a duplicate of bug 283942 ***
https://bugs.launchpad.net/bugs/283942
** This bug has been marked a duplicate of bug 283942
crashed during installing packages on upgrade vom hardy to intrepid beta
(after about half of the packages had been upgraded)
--
gconf2-common post
in case other people have the same problem and read this, I would like to
contribute here how I did proceed with my installation to recover from the
problem:
- repeatedly called dpkg --configure -a until it succeeded
(better would be to first edit /var/cache/debconf/config.dat as described in
a similar problem (maybe same cause) was discussed in bug 283942
the debconf kde frontend is dysfunctional partway through the kde3-kde4
transition
--
libc6 update fails: stack smashing detected : /usr/bin/perl
https://bugs.launchpad.net/bugs/270626
You received this bug notification because
continuing the recovery notes:
after the upgrade is completed, apport will display a lot of errors concerning
the inability to configure some of the packages.
call dpkg-reconfigure -p hight packagename for each of them manually
(or script it with the information from /var/crash)
--
crashed
the problem no longer occurs in gutsy / partimage 0.6.7
** Changed in: partimage (Ubuntu)
Status: New = Fix Released
--
[apport] partimage crashed with SIGSEGV in start_thread()
https://bugs.launchpad.net/bugs/117393
You received this bug notification because you are a member of Ubuntu
Public bug reported:
I started adept_manager --dist-upgrade-devel and clicked on the version
upgrade button
the upgrade-tool was started and began to download package lists and so
on. After the third step or so it suddenly disappeared without any
message.
I will provide the logs from
** Attachment added: apt.log
http://launchpadlibrarian.net/18447899/apt.log
--
disappears with no error message in preparation stage
https://bugs.launchpad.net/bugs/281891
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
** Attachment added: main.log
http://launchpadlibrarian.net/18447908/main.log
--
disappears with no error message in preparation stage
https://bugs.launchpad.net/bugs/281891
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
the file term.log is empty
--
disappears with no error message in preparation stage
https://bugs.launchpad.net/bugs/281891
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
*** This bug is a duplicate of bug 281891 ***
https://bugs.launchpad.net/bugs/281891
** This bug has been marked a duplicate of bug 281891
disappears with no error message in preparation stage
--
can't upgrade from hardy to intrepid
https://bugs.launchpad.net/bugs/281218
You received
Public bug reported:
after doing the upgrade to intrepid beta (today), logging in via gdm
failed with the message your session lasted less than 10 seconds, ...
The .xsession-errors log has
mkdtemp: private socket dir: Permission denied
The reason was /tmp being unwritable
drwxr-xr-x 14
Public bug reported:
after the upgrade to intrepid beta (today), debconf (in reconfiguring
packages) does not work properly.
I tried to apt-get remove some ispell dictionaries, and was presented
with a dialog to select the active dictionary.
The dialog frontend did not react to user input like
it looks like ^[OB^[OB^
--
dialog frontend shows garbled characters after upgrade to intrepid-beta
https://bugs.launchpad.net/bugs/282310
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Public bug reported:
after upgrade to intrepid beta (2008-12-12), the konsole application no
longer has german menus.
in language-pack-kde-de the relevant file /usr/share/locale-
langpack/de/LC_MESSAGES/konsole.mo is still included
but it is much smaller than before (now: 1934bytes, hardy:
the problem is not the missing kde-l10n-de, but incomplete data in
language-pack-kde-de (see #282332)
--
language-pack-kde-de does not depend on kde-l10n-de
https://bugs.launchpad.net/bugs/268438
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
- what packages were updated? About 1000 :-)
- I did reboot cleanly (reboot initiated by the dist-upgrade tool)
- my fix does persist after reboot
(sorry, my next opportunity to contribute so finding the problem will be
wednesday night GMT)
--
/tmp unwriteable after upgrade to intrepid beta,
Public bug reported:
$ kbluetooth4
KBluetooth4 is already running!
but there is no bluetooth tray icon
** Affects: kdebluetooth (Ubuntu)
Importance: Undecided
Status: New
--
no bluetooth tray icon
https://bugs.launchpad.net/bugs/287233
You received this bug notification because
** Changed in: kdebluetooth (Ubuntu)
Status: New = Confirmed
--
no bluetooth tray icon
https://bugs.launchpad.net/bugs/287233
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Public bug reported:
in some applications, e.g. konsole, kmail the menu items are only
translated partially. Still today 2008-10-23
yes, this is the releveant package, seen from:
$dpkg -S /usr/share/locale-langpack/de/LC_MESSAGES/kmail.mo
language-pack-kde-de-base:
*** This bug is a duplicate of bug 288304 ***
https://bugs.launchpad.net/bugs/288304
** This bug has been marked a duplicate of bug 288304
menu translation partly missing for e.g. konsole, kmail
--
konsole menu translations missing
https://bugs.launchpad.net/bugs/282332
You received this
I can confirm the problem on two different machines with up to date
hardy beta and no foreign software
using kdm and nvidia cards
when a user logs out, kdm tries to start a new xserver, and that one
crashes. restarting kdm produces a new working xserver
the nvidia cards are:
nVidia Corporation
Leo, I suggest that you retitle this bug to, e.g. :
nvidia_drv.so crash during X restart by kdm
--
nvidia_drv.so crash after logout
https://bugs.launchpad.net/bugs/202855
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
this seems to be a kdm problem (it goes away if you use gdm instead)
** Changed in: kdebase (Ubuntu)
Sourcepackagename: linux-restricted-modules-2.6.24 = kdebase
--
nvidia_drv.so crash during X restart by kdm
https://bugs.launchpad.net/bugs/202855
You received this bug notification because you
Public bug reported:
Binary package hint: update-manager
Probably not bug of update-manager but of the upgrade process in
general:
on installation of packages where a conffile has been change manually by
the user, e.g. /etc/bash.bashrc, the installer asks whether the old or
new confffile is to
Public bug reported:
Binary package hint: uswsusp
with gutsy my main harddisk was hda
after upgrade to hardy it is now sda
uswsusp configuration was not automatically changed (which might be tolerable)
BUT: this lead uswsusp to ask interactively during the boot sequence, where to
resume from,
The maintainers consider it a feature!!! This bug has been reported
earlier, e.g. #10662, more than three years ago.
I share the opinion of the reporters: it is a blatant security hole
because nobody expects this from a linux system.
There are more security holes like that when you can edit the
this problem seems to be gone in hardy. Therefore, I suggest to close
the bug. Can anybody confirm?
--
dansguardian start takes more than half a minute
https://bugs.launchpad.net/bugs/126125
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
installing firefox-gnome-support fixed the problem for me in kubuntu
hardy
it is a bug for firefox not to depend on firefox-gnome-support!
--
[KDE] Applications tab in preferences is empty in Firefox-3.0b5
https://bugs.launchpad.net/bugs/220798
You received this bug notification because you
Public bug reported:
With nfs-kernel-server and nfs-utils in hardy i experience the following
problem which looks to me like a bug. The problem was already present in
gutsy, but not in feisty.
- nfs-common assumes that connects to rpc.statd can only come from the
ip address 127.0.0.1
** Summary changed:
- The build-in terminal is not set read-only
+ The built-in terminal is not set read-only
--
The built-in terminal is not set read-only
https://bugs.launchpad.net/bugs/43328
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Am Donnerstag 15 Mai 2008 schrieb Martin Pitt:
Copied to hardy-updates.
** Changed in: friendly-recovery (Ubuntu Hardy)
Status: Fix Committed = Fix Released
why not to hardy-security? It is a security problem that needs to be fixed for
everybody.
--
Ernst Kloppenburg
Heimerdingen
the same problem the original reporter had is still present in hardy.
(the nfs module is automatically loaded only with nfsv3 mounts, not with nfsv4
mounts)
--
(gutsy)Need to modprobe nfs module before mounting nfs4 export
https://bugs.launchpad.net/bugs/117957
You received this bug
with my current edgy-feisty upgrade, all debconf questions are asked in
the terminal because all other frontends failed. Without the terminal
being accessible I were in a quite bad situation.
Therefore, before setting the terminal to readonly, the availability of
a gui debconf frontend would need
unfortunately, that logfile was overwritten because I tried to start
update-manager again to complete the update.
Is there a way to make update-manager believe my (now) feisty-system
is still edgy? Then I could start the upgrade again and try to
reproduce the error.
On Fri, Apr 20, 2007 at
Public bug reported:
Binary package hint: partimage
crashed while accessing an image, error message is Ungültiger
Kompressionsmodus für xy.img (invalid compression)
ProblemType: Crash
Architecture: i386
Date: Mon May 28 18:57:17 2007
DistroRelease: Ubuntu 7.04
ExecutablePath:
** Attachment added: CoreDump.gz
http://librarian.launchpad.net/7859290/CoreDump.gz
** Attachment added: Dependencies.txt
http://librarian.launchpad.net/7859291/Dependencies.txt
** Attachment added: Disassembly.txt
http://librarian.launchpad.net/7859292/Disassembly.txt
** Attachment
and give feedback here
** Tags added: verification-needed
--
Ernst Kloppenburg
Heimerdingen, Germany
--
friendly-recovery drops to a root shell even when a root password is set
https://bugs.launchpad.net/bugs/220986
You received this bug notification because you are a member of Ubuntu
Bugs
I followed steps 5 through 7 of the updated description above (using
friendly-recovery Version: 0.1.2)
It works as expected now: it does ask for the root password
pressing control-D instead of giving the root password brings you back
to selection screen.
--
friendly-recovery drops to a root
when the configuration is done correctly as explained in the first
comment (https://bugs.launchpad.net/ubuntu/+source/unattended-
upgrades/+bug/136720/comments/1), everything works fine, mails are sent.
--
does not send mail despite Unattended-Upgrade::Mail set
** Attachment added: main.log
http://launchpadlibrarian.net/9517378/main.log
--
ERROR not handled expection in KDE frontend: update-manager vanished during
upgrade from feisty to gutsy
https://bugs.launchpad.net/bugs/145351
You received this bug notification because you are a member of
Public bug reported:
While trying to upgrade a kubuntu system from feisty to gutsy, the
upgrade-manager tool crashed and vanished completely. I started the
upgrade with 'adept_manager --version-upgrade' and pressed the version
upgrade button in adept.
The crash occured after the dialog where you
** Attachment added: apt.log
http://launchpadlibrarian.net/9517382/apt.log
--
ERROR not handled expection in KDE frontend: update-manager vanished during
upgrade from feisty to gutsy
https://bugs.launchpad.net/bugs/145351
You received this bug notification because you are a member of Ubuntu
sorry, I forgot to fill in the package name field when I created the bug
--
ERROR not handled expection in KDE frontend: update-manager vanished during
upgrade from feisty to gutsy
https://bugs.launchpad.net/bugs/145351
You received this bug notification because you are a member of Ubuntu
Bugs,
** Attachment added: main_pre_req.log
http://launchpadlibrarian.net/9517383/main_pre_req.log
--
ERROR not handled expection in KDE frontend: update-manager vanished during
upgrade from feisty to gutsy
https://bugs.launchpad.net/bugs/145351
You received this bug notification because you are
Public bug reported:
Binary package hint: unattended-upgrades
(feisty)
I have configured Unattended-Upgrade::Mail and can verify this with:
$ apt-config dump| grep Mail
Unattended-Upgrade::Mail ;
Unattended-Upgrade::Mail:: [EMAIL PROTECTED];
But after a run of /etc/cron.daily/apt, the last
Answer to the first comment (https://bugs.launchpad.net/ubuntu/+source
/unattended-upgrades/+bug/136720/comments/1)
I had defined the mail variable in apt.conf.d/50unattended-upgrades as
Unattended-Upgrade::Mail {
[EMAIL PROTECTED];
};
Now I tried the change you suggested:
to the second comment: mailx _is_ installed and works
--
does not send mail despite Unattended-Upgrade::Mail set
https://bugs.launchpad.net/bugs/136720
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
no, I had not imported the python apt module (I wonder why apt_pkg did
not complain?).
Now I have, and now
email = apt_pkg.Config.Find(Unattended-Upgrade::Mail, )
indeed yields the configured mail address. Very good!
So my configuration really was wrong (with Unattended-Upgrade::Mail
configured
Public bug reported:
Binary package hint: dansguardian
Hello,
dansguardian takes more than half a minute to start. CPU: athlon 2000+, memory:
512MB
I am experiencing this on to different computers.
This behaviour began some weeks ago, maybe because of some feisty
update, but I do not know.
may I set the status of this bug to invalid?
looking at intrepid with kde 4.1.4 from intrepid-updates:
- the german translations for kde4 are there now (without kde-l10n-de
being installed)
- language-pack-kde-de still does not depend on kde-l10n-de which is
correct
--
language-pack-kde-de
Public bug reported:
on update from intrepid to jaunty using 'update-manager -d' some
configuration questions are asked twice
e.g. for package flashplugin-installer the questions concerning the download
an installation
e.g. for package libc6 Running services and programs that are using NSS
the questions for libpam-ck-connector are also asked twice
(sorry, I could not find out how to add a line to the table of affected
packages above)
--
update, configuration questions are asked twice
https://bugs.launchpad.net/bugs/365219
You received this bug notification because you are a
Public bug reported:
Binary package hint: samba-common
on update to jaunty, configuration questions are asked in curses dialog
inside the terminal-window of the update manager.
But debconf is configured to use kde, and questions for other packages
actually have been asked with kde dialogs
**
** Also affects: consolekit (Ubuntu)
Importance: Undecided
Status: New
--
update, configuration questions are asked twice
https://bugs.launchpad.net/bugs/365219
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
Public bug reported:
during upgrade from intrepid to jaunty (using update-manager -d) I had
configured debconf to use the kde frontend
still a number of packages asked questions with red/blue dialogs in the
terminal window emulation of the update-manager instead of using the kde
frontend.
this
1 - 100 of 283 matches
Mail list logo
