[Bug 1007273] Re: autofs does not start automatically after reboot
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. https://bugs.launchpad.net/bugs/1007273 Title: autofs does not start automatically after reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autofs5/+bug/1007273/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1068036] Re: postfix (precise) has lost the ability to lookup aliases in 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: verification-done -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to postfix in Ubuntu. https://bugs.launchpad.net/bugs/1068036 Title: postfix (precise) has lost the ability to lookup aliases in NIS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/1068036/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1068036] [NEW] postfix (precise) has lost the ability to lookup aliases in NIS
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 - and mail is not forwarded Obviously some build switch was changed between 10.04 and 12.04. In 10.04: $ postconf -m | grep nis nis In 12.04 the output is empty. But still in 12.04 the postfix.postinst skript looks for nis and creates an appropriate mail.cf entry for lookup in nis:mail.aliases $ lsb_release -rd Description:Ubuntu 12.04.1 LTS Release:12.04 $ apt-cache policy postfix postfix: Installiert: 2.9.3-2~12.04.3 ** Affects: postfix (Ubuntu) Importance: Undecided Status: New ** Tags: regression-release -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to postfix in Ubuntu. https://bugs.launchpad.net/bugs/1068036 Title: postfix (precise) has lost the ability to lookup aliases in NIS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/1068036/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 993259] Re: ypbind does not start on boot
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 management of the dependency of nis on a working network interface is not correctly done ** Changed in: nis (Ubuntu) Status: Invalid = Confirmed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nis in Ubuntu. https://bugs.launchpad.net/bugs/993259 Title: ypbind does not start on boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nis/+bug/993259/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 569757] Re: NIS upstart dependency broken for lucid
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 this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nis in Ubuntu. https://bugs.launchpad.net/bugs/569757 Title: NIS upstart dependency broken for lucid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nis/+bug/569757/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 569757] Re: NIS upstart dependency broken for lucid
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 noticed that there isn't any log output, neither in the console messages at boot time nor in the syslog. I injected an error by misspecifying the nis domain. This also did not produce any output anywhere that might help to debug. I think (but I am no sure) that you would see more output with the current stock nis package. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nis in Ubuntu. https://bugs.launchpad.net/bugs/569757 Title: NIS upstart dependency broken for lucid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nis/+bug/569757/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 561779] Re: squid is not started on runlevel transition 1 - 2
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 - works -- 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid/+bug/561779/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 561779] Re: squid is not started on runlevel transition 1 - 2
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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid/+bug/561779/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 809526] Re: squid 2.7.STABLE9-2ubuntu5.1, reload kills squid, called in /etc/resolvconf/update-libc.d/squid
** 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 /etc/resolvconf/update-libc.d/squid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid/+bug/809526/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 809526] Re: squid 2.7.STABLE9-2ubuntu5.1, reload kills squid, called in /etc/resolvconf/update-libc.d/squid
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 hand months ago and it was used daily. -- 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 /etc/resolvconf/update-libc.d/squid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid/+bug/809526/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 809526] [NEW] squid 2.7.STABLE9-2ubuntu5.1, reload kills squid, called in /etc/resolvconf/update-libc.d/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 This kills squid. The syslog shows squid main process (nnn) killed by HUP signal I freshly installed squid and squid-common after purging them, nothing was changed after installation, system was rebooted before test ** Affects: squid (Ubuntu) Importance: Undecided Status: 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 /etc/resolvconf/update-libc.d/squid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid/+bug/809526/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 561750] Re: squid starts and stops immediately (after upgrade from karmic to lucid)
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 bug notification because you are a member of Ubuntu Server Team, which is subscribed to squid in Ubuntu. https://bugs.launchpad.net/bugs/561750 Title: squid starts and stops immediately (after upgrade from karmic to lucid) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid/+bug/561750/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 561750] Re: squid starts and stops immediately (after upgrade from karmic to lucid)
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) Thanks Clint for finally fixing this bug. -- 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/561750 Title: squid starts and stops immediately (after upgrade from karmic to lucid) -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 569757] Re: NIS upstart dependancy broken for lucid
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 ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 561779] Re: squid is not started on runlevel transition 1 - 2
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 received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to squid in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 561750] Re: squid starts and stops immediately (after upgrade from karmic to lucid)
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 prevent squid from doing the DNS tests during start (there are no error messages in /var/log/squid attached earlier). ** Attachment added: /etc/network/interfaces http://launchpadlibrarian.net/44118835/interfaces -- 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 subscribed to squid in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 561750] Re: squid starts and stops immediately (after upgrade from karmic to lucid)
** 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 subscribed to squid in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 561750] Re: squid starts and stops immediately (after upgrade from karmic to lucid)
$ 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 Apr 14 07:38:35 rechner6 init: anacron main process (1296) killed by TERM signal Apr 14 07:38:35 rechner6 init: plymouth-stop pre-start process (2288) terminated with status 1 -- 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 subscribed to squid in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 561750] Re: squid starts and stops immediately (after upgrade from karmic to lucid)
- 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 package) /etc/resolvconf/update-libc.d/squid which contains the command 'invoke-rc.d squid reload' This command does the wrong thing, it stops squid: r...@rechner6:~# start squid squid start/running, process 3328 (now squid is usable) r...@rechner6:~# /etc/resolvconf/update-libc.d/squid Rather than invoking init scripts through /etc/init.d, use the service(8) [...] r...@rechner6:~# status squid squid stop/waiting (the squid/cache.log shows the normal shutdown sequence) ** Attachment added: /var/log/squid/cache.log http://launchpadlibrarian.net/44224116/cache.log -- 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 subscribed to squid in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 561750] [NEW] squid starts and stops immediately (after upgrade from karmic to lucid)
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 DistroRelease: Ubuntu 10.04 Package: squid 2.7.STABLE7-1ubuntu11 ProcVersionSignature: Ubuntu 2.6.32-19.28-generic 2.6.32.10+drm33.1 Uname: Linux 2.6.32-19-generic i686 NonfreeKernelModules: fglrx Architecture: i386 Date: Mon Apr 12 21:12:34 2010 ProcEnviron: LANGUAGE= PATH=(custom, user) LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: squid ** Affects: squid (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 lucid -- 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 subscribed to squid in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 561750] Re: squid starts and stops immediately (after upgrade from karmic to lucid)
** 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) https://bugs.launchpad.net/bugs/561750 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to squid in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 561779] [NEW] squid is not started on runlevel transition 1 - 2
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 would stop on entering runlevel 1 and be started again on entering runlevel 2 ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: squid 2.7.STABLE7-1ubuntu11 ProcVersionSignature: Ubuntu 2.6.32-19.28-generic 2.6.32.10+drm33.1 Uname: Linux 2.6.32-19-generic i686 NonfreeKernelModules: fglrx Architecture: i386 Date: Mon Apr 12 21:48:49 2010 ProcEnviron: LANGUAGE= PATH=(custom, user) LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: squid ** Affects: squid (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 lucid -- 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 squid in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 561779] Re: squid is not started on runlevel transition 1 - 2
** 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 squid in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 369682] Re: AutoFS direct maps not working with NFSv4 exports
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 unclear to me after having looked at the last 4 package versions. This bug should be closed as invalid. -- AutoFS direct maps not working with NFSv4 exports https://bugs.launchpad.net/bugs/369682 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to autofs in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 369682] Re: AutoFS direct maps not working with NFSv4 exports
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 because you are a member of Ubuntu Server Team, which is subscribed to autofs in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 365259] Re: on update to jaunty, configuration questions are asked in curses dialog but debconf is configured to use kde
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 correctly in a kde debconf window, the questions also appear in the term.log but in a different format. As an example I show the output for dnsmasq at the bottom === [...] Vorbereiten zum Ersetzen von samba-common 2:3.2.3-1ubuntu3.5 (durch .../samba-common_2%3a3.3.2-1ubuntu3_i386.deb) ... b) ... Entpacke Ersatz für samba-common ... [...] Richte samba-common ein (2:3.3.2-1ubuntu3) ... momentanen Version. Installiere neue Version der Konfigurationsdatei /etc/dhcp3/dhclient-enter-hooks.d/samba ... Paket-Konfiguration ┌──┤ Samba Server ├──┐ ││ │ Eine neue Version der │ │ Konfigurationsdatei│ │ /etc/samba/smb.conf ist│ │ verfügbar, aber die installierte │ │ Version wurde verändert. │ ││ │ Ok │ ││ └┘ ─┤ Samba Server ├ mit smb.conf Version des Paket-Betreuers ins ↑ aktuell installierte Version be ▮ Ok ─ Richte samba-common ein (2:3.3.2-1ubuntu3) ... Installiere neue Version der Konfigurationsdatei /etc/dhcp3/dhclient-enter-hooks.d/samba ... Replacing config file /etc/samba/smb.conf with new version === [...] Richte dnsmasq ein (2.47-3) ... Installiere neue Version der Konfigurationsdatei /etc/init.d/dnsmasq ... Installiere neue Version der Konfigurationsdatei /etc/default/dnsmasq ... e Version herausgegeben. Was möchten Sie damit machen? Ihre Wahlmöglichkeiten sind: Y oder I : Die Version des Paket-Betreuers installieren N oder O : Die momentan installierte Version beibehalten D : Die Unterschiede zwischen den Versionen anzeigen Z : Prozess in den Hintergrund, um die Situation zu begutachten Der Standardweg ist das Beibehalten der momentanen Version. *** dnsmasq.conf (Y/I/N/O/D/Z) [Vorgabe=N] ? *** dnsmasq.conf (Y/I/N/O/D/Z) [Vorgabe=N] ? y Installiere neue Version der Konfigurationsdatei /etc/dnsmasq.conf ... [...] === -- on update to jaunty, configuration questions are asked in curses dialog but debconf is configured to use kde https://bugs.launchpad.net/bugs/365259 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 365259] [NEW] on update to jaunty, configuration questions are asked in curses dialog but debconf is configured to use kde
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 ** Affects: samba (Ubuntu) Importance: Undecided Status: New -- on update to jaunty, configuration questions are asked in curses dialog but debconf is configured to use kde https://bugs.launchpad.net/bugs/365259 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
