Ok,
I had a system crash but I was able to find the configs I used for this.
It only applies to sysvinit in the form I did it.
I modifed the file lib/live/config/0170-sysvinit so that it has the
following:
In function Configure_sysvinit:
# Configure autologin
sed -i -e
-=| Daniel Dickinson, 17.01.2015 19:03:49 -0500 |=-
Package: amanda-server Version: 1:3.3.6-4 Severity: serious
Justification: depends on software not in debian
Seen when attemping to do amrmtape, but also occurs when doing
a flush:
an't locate Tie/StdHash.pm: Permission denied at
/usr/share
PM, Michael Biebl wrote:
control: tags -1 moreinfo
Am 08.01.2015 um 22:00 schrieb Daniel Dickinson:
Package: systemd Version: 215-8 Severity: normal
As I mentioned in my previous bug report I've (at least
temporarily) had to switch my system back to sysvinit because of
issues
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I believe, despite this difference in effect that this is a duplicate
of #774329, which is also a permissions issue.
The thing is that the issues are intermittent and therefore either the
permissions are getting changed (unlikely as I have no
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I believe, despite this difference in effect that this is a duplicate
of #775612, which is also a permissions issue.
The thing is that the issues are intermittent and therefore either the
permissions are getting changed (unlikely as I have no
Package: cyrus-common
Version: 2.4.17+caldav~beta10-16
Severity: normal
File: /usr/sbin/cyrus
When using sieve scripts (managed using a Manage Sieve client)
conditions such as
if address :contains From @example.com
fail to be acted on (that is the match fails).
The compilation succeeds so
:
On Thu, Jan 01, 2015 at 09:45:19AM -0500, Daniel Dickinson wrote:
On 01/01/15 05:11 AM, Guido Günther wrote:
On Wed, Dec 31, 2014 at 05:27:03PM -0500, Daniel Dickinson
wrote:
Package: libvirt-bin Version: 1.2.9-7 Severity: grave
Justification: causes non-serious data loss
If libvirt
Package: shorewall
Version: 4.6.4.3-1
Severity: grave
Justification: renders package unusable
A firewall that is never applied is useless hence a bug that stops shorewall
from being applied
under the default init system (systemd) is RC.
In this case the issue is that /etc/init.d/shorewall
Package: shorewall
Version: 4.6.4.3-1
Followup-For: Bug #776680
Despite the debconf setting of invalid_config the config is in fact correct as
evidenced
by the fact that the shorewall compile and shorewall safe-restart commands
compile and
restart the firewall with no complaints or issues.
--
Package: shorewall
Version: 4.6.4.3-1
Followup-For: Bug #776680
The issue appears to be with debconf settings as dpkg-reconfigure shorewall and
then
/etc/init.d/shorewall restart works even dpkg-reconfigure doesn't actually do
any
prompts.
Perhaps it is because shorewall packaging labels the
Package: cifs-utils
Version: 2:5.5-1
Severity: minor
Mounting NTLMv2 shares for which signing is not enabled (e.g. older (including
Wheezy)
Samba deployments, or older Windows, or Windows with signing turned off for
other
compatibility reasons) fails with 'Invalid Paramater'.
This is only a
Package: amanda-server
Version: 1:3.3.6-4
Followup-For: Bug #775612
This bug is rather strange as I have rerun using the exact commandline and now
the command succeeds with no
error message.
I have been getting these messages in some but not all of my emails from
amanda. There is something
Package: amanda-server
Version: 1:3.3.6-4
Severity: serious
Justification: depends on software not in debian
Seen when attemping to do amrmtape, but also occurs when doing a flush:
an't locate Tie/StdHash.pm: Permission denied at /usr/share/perl/5.20/base.pm
line 97.
...propagated at
Package: virt-manager
Version: 1:1.0.1-3
Severity: normal
Attempting to run virt-manager on a remote machine through an SSH tunnel with
X11 forwarding fails.
With --debug output shows:
[Fri, 16 Jan 2015 21:03:02 virt-manager 4327] DEBUG (console:1494) Starting
connect process for proto=spice
Package: virt-manager
Version: 1:1.0.1-3
Followup-For: Bug #775543
I forgot to mention: The error occurs when connecting to a Spice display, not
the virt-manager GUI main window.
That is when looking at video on a running virtual machine instance, but only
when using Spice. VNC displays
do not
Package: xfce4-power-manager
Version: 1.4.1-1
Followup-For: Bug #773743
In case it helps, here is this list of installed packages.
Like I said I don't know what other information I can give you because the only
thing
I did that is 'special' that triggered the bug was enable the suspend option
Package: xfce4-power-manager
Version: 1.4.1-1
Followup-For: Bug #773743
Hi,
Where do I start looking? Also I haven't changed any d-bus or policykit
settings and
this occurs with both systemd and sysvinit.
Please note that when I first reported I hadn't done anything special except
install
Package: systemd
Version: 215-8
Severity: important
I've had to (at least temporarily) switch to sysvinit because systemd fails
to start old-style initscripts on some of my systems. I don't have the time
at present to debug mostly because with systemd I have no idea where to even
start
Package: systemd
Version: 215-8
Severity: normal
As I mentioned in my previous bug report I've (at least temporarily) had
to switch my system back to sysvinit because of issues with initscripts
failing to start on some systems, however I still feel I ought to report
the bugs I've found.
This
Source: network-manager
Version: jessie
Severity: normal
When creating bridges it is not possible to specify the bridge MAC address and
sometimes on boot (actually a reboot rather than fresh boot) network-manager
assigns some random MAC adress to the bridge device instead of the MAC address
of
Package: xfce4-panel
Followup-For: Bug #774440
For whatever reason the problem has gone away and icons now appear in the
notification
area the way they are supposed to.
Regards,
Daniel
-- System Information:
Debian Release: 8.0
APT prefers testing
APT policy: (500, 'testing')
05:00 schrieb Daniel Dickinson:
Package: policykit-1
Version: 0.105-8
Severity: normal
policykit has a hard dependency on libpam-systemd which has a hard
dependency on
systemd AND the dependency is NOT eliminated through the use of systemd-shim.
It is probably intended that systemd-shim
Package: debootstrap
Version: 1.0.66
Severity: normal
The attached version of deboostrap makes exclude also exclude dependencies when
doing dependency resolution. This is necessary in order to exclude systemd and
substitude sysvinit which is *required* for LXC because systemd is currently
Package: debootstrap
Version: 1.0.66
Severity: normal
When using --no-resolve-deps and include and exclude lists deboostrap errors out
with the message that it can't finds deb X where looks like a package
size.
-- System Information:
Debian Release: 8.0
APT prefers testing
APT
Sorry but systemd-shim does NOT eliminate the dependency on libpam-systemd.
This bug should be reopened because the bad dependency is not eliminated
by systemd-shim.
It probably is intended to be and it's probably an unintended packing
error that libpam-systemd is required even when systemd-shim
Package: policykit-1
Version: 0.105-8
Severity: normal
policykit has a hard dependency on libpam-systemd which has a hard dependency on
systemd AND the dependency is NOT eliminated through the use of systemd-shim.
It is probably intended that systemd-shim OUGHT to eliminate the depency on
I think misunderstood you comment to mean you were claiming that with
systemd-shim that systemd doesn't have to be installed. Are what you
actually saying is that you can't avoid having systemd on the system,
but you can use systemd-shim to allow you so can use sysvinit through
appropriate grub
Package: policykit-1
Version: 0.105-8
Severity: normal
Lots of stuff depend on policykit and supposedly one is allowed to create
systemd if
one wants, however currently policykit depends on libpam-systemd which makes it
impossible to have a meaningful desktop without system. libpam-systemd
On 10/12/14 04:21 AM, Daniel Baumann wrote:
another ping on this.. what's the status? can you at least post your patch?
Regards,
Daniel
Hi,
Sorry I was working on this, but then finally got fed up with with the
systemd/gnome pushers (which have already caused me hours of grief with
stuff
Package: byobu
Version: 5.87-1
Followup-For: Bug #774483
The bug only occurs of TERM=screen before launching byobu (e.g. SSH to
remote system from a system running byobu in the local terminal).
If you do something like test if the connection is SSH and if set TERM=xterm if
TERM=screen before the
Package: byobu
Version: 5.87-1
Severity: normal
It is currently impossible by any means (including hand editing .byobu/status
and killing
..byobu directory logging out, and staring over) to disable the date and time
displays
in the tmux status bar.
-- System Information:
Debian Release: 8.0
Package: xfce4-panel
Version: 4.10.1-1
Severity: normal
It looks like some API or something has changed and failed to maintain backwards
compability because a number of applications fail to show up on the system tray
applet which ought to have icons there including hipchat (non-debian) and
On 01/01/15 05:11 AM, Guido Günther wrote:
On Wed, Dec 31, 2014 at 05:27:03PM -0500, Daniel Dickinson wrote:
Package: libvirt-bin
Version: 1.2.9-7
Severity: grave
Justification: causes non-serious data loss
If libvirt-bin has an upgrade requiring a restart it restarts and kills
Package: libvirt-bin
Version: 1.2.9-7
Severity: grave
Justification: causes non-serious data loss
If libvirt-bin has an upgrade requiring a restart it restarts and kills
currently
active guests without first gracefully shutting them down. This can result in
data
loss due to damaged filesystems
On 30/12/14 03:16 PM, Ondřej Surý wrote:
Hi Daniel,
thanks for the time you have spent on this and for the patches.
Could you please send those patches as diffs (or git diffs preferrably),
it's better to have them unmangled by MUAs.
Do you mean .diff attachments? Or do you mean package
).
The third was that in some cases mailboxname creation functions
didn't even consider the domain part of the userid and therefore
didn't handle domain mailbox name construction correctly
.
Author: Daniel Dickinson deb...@daniel.thecshore.com
---
The information above should follow the Patch Tagging
Package: cyrus-caldav
Version: 2.4.17+caldav~beta10-13~dfd2
Severity: normal
Tags: patch
Due to strict interpretation/implementation of HTTP Auth RFC having private
calendars
from multiple accounts accessed by the same instance of a client (e.g. Icedove)
fails
with 403 Forbidden for any
On 26/12/14 08:48 PM, Michael Biebl wrote:
Am 26.12.2014 um 06:11 schrieb Daniel Dickinson:
On 25/12/14 01:27 PM, Michael Biebl wrote:
Messages appeared in journal (journalctl) however there was no output
in
syslog. I have noticed that *none* of the boxes / vms I have upgraded
from
On 23/12/14 04:40 PM, Michael Biebl wrote:
Am 23.12.2014 um 02:49 schrieb Daniel Dickinson:
Package: systemd
Followup-For: Bug #773766
It turns there was a permissions problem on the log file directory
for deluged causing deluged failing to start, however there was a
lack of information
Package: cyrus-caldav
Version: 2.4.17+caldav~beta10-12
Severity: important
Currently cyrus-caldav is unusable as CalDAV/CardDAV support fails with
PROPFIND 405 Method Not Allowed in the server logs.
According to http://permalink.gmane.org/gmane.mail.imap.cyrus/37870
this is most likely caused by
On 25/12/14 01:27 PM, Michael Biebl wrote:
Messages appeared in journal (journalctl) however there was no output
in
syslog. I have noticed that *none* of the boxes / vms I have upgraded
from wheezy to jessie output the journal to syslog. I suppose this may
be a systemd upgrade bug.
Package: amanda-server
Version: 1:3.3.6-4
Severity: normal
File: /usr/sbin/amstatus
amstatus is reporting all kinds of unitialized value errors, which since I have
cron job that runs amstatus regularly to determine if a wake on lan is needed on
clients that might be being backed up, I get tons of
Package: source
Version: 2.4.17+caldav~beta10-12
Severity: important
The package build system incorrectly modifies source files and fails to revert
them
on clean, resulting in a situation where dpkg-buildpackage followed by
make -f debian/rules clean followed by dpkg-buildpackage fails.
This is
of at
+the top-level /dav/ URI (i.e. Lightening requires a full
+path AND issues PROPFIND on the full path rather than as a
+discovery mechanism at the top level. Cyrus currently only
+allows PROPFIND in / or /dav
+
+ -- Daniel Dickinson deb...@daniel.thecshore.com Thu, 25 Dec 2014 22:41:11
-0500
Source: linux
Version: 3.16.0-4
Followup-For: Bug #758870
I have investigated further and determined that /sbin/request-key never gets
called
(I intercepted calls to /sbin/request-key which a program which first logs and
it didn't
even get triggered once despite using NFSv4, in this with
Package: xfce4-settings
Version: 4.10.1-2
Severity: important
Dear Maintainer,
Changing things in 'Startup and Sessions' (e.g. checking or unchecking
items in the startup list, or adding item) fails to actually do anything.
When you exit and reenter the dialogue no change has occurred for
Package: xfce4-power-manager
Version: 1.4.1-1
Severity: important
Suspend mode is never entered via power-manager due to the fact that when it
comes times to suspend an authentication dialogue requesting authorization
to suspend pops up instead of suspend occurring.
This is on a non-laptop so
Package: xfce4-settings
Followup-For: Bug #773739
This bug can be closed. My ~/.config directory had root ownership for
some reason. Will have to investigate if due to debian-installer issue
or an issue with an bad copy (or something wrong with xfce when creating
a config based on defaults at
Package: nut-client
Version: 2.7.2-1+b3
Severity: serious
Justification: Fails to install due to failing to start
The package fails to configure on install due to ups-monitor service
failing to start due to lack of configuration and failed to gracefully
handle case of no valid configuration.
Package: deluged
Version: 1.3.10-2
Followup-For: Bug #770628
Deluged fails to start when doing service restart or
/etc/init.d/deluged restart.
The message says that it is starting via systemctl deluged.service
however no deluged.service file exists which I suspect is why the
service fails to
Package: systemd
Version: 215-8
Severity: important
At least in the instance of deluged for which there is an initscript
in /etc/init.d/deluged but no deluged.service doing
/etc/init.d/deluged start
gives the message starting by systemctl deluged.service
however such a file does not exist
Package: git-daemon-run
Version: jessie
Severity: normal
This packages depend on runit which depends on the existence of inittab
which is not longer true with systemd.
-- System Information:
Debian Release: 8.0
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Package: exim4-daemon-heavy
Version: 4.80-7+deb7u1
Severity: normal
Using exim4-daemon-heavy to use the exiscan patch that allows to use spamd
filtering in acl's fails
with large emails. I don't know the exact cutoff but with a 4.5M email that a
command line invocation
of spamc can process in
Package: owncloud-client
Version: 1.6.2+dfsg-1
Followup-For: Bug #750847
The client is looking for owncloud.png, state-offline.{png|svg},
state-error.{png|svg}, and state-ok.{png|ok}
which according to apt-file do not exist in any package.
-- System Information:
Debian Release: jessie/sid
On 14/06/14 01:45 AM, Daniel Baumann wrote:
Gentle reminder.. did you have time/can you make time for a patch?
Regards,
Daniel
FYI, The fix would only be applicable to systemv not to systemd. Is it
still worth doing?
I haven't boot a live system with systemd yet but from the code I don't
Package: gpa
Version: 0.9.5-1
Severity: normal
Even moving away my keyring does not solve the issue that on start GPA says
The GPME library returned an unexpected error at keytable.c:150. The was:
Unsupported certificate
This is either an installation problem or a bug in GPA.
GPA will now try
On 09/09/14 11:23 PM, NIIBE Yutaka wrote:
On 2014-09-09 at 23:09 -0400, Daniel Dickinson wrote:
The GPME library returned an unexpected error at keytable.c:150. The was:
Unsupported certificate
I think that it is GNOME keyring which gets the connection to
gpg-agent (and produced the error
On 09/09/14 11:57 PM, Daniel Baumann wrote:
On 09/10/2014 03:40 AM, Daniel Dickinson wrote:
FYI, The fix would only be applicable to systemv not to systemd. Is it
still worth doing?
yes. we still support and will support sysvinit for quite some time (at
least until jessie+1 EOL, which
Package: seahorse
Version: 3.12.2-1
Severity: normal
If I remove userid from my private+public key and then do a sync, seahorse
pulls the old
key from the keyserver and adds back the userids before pushing my changes to
the server.
This causes the edit to be undone on the public side of the
Package: seahorse
Version: 3.12.2-1
Severity: normal
Editing userids present on a key fails during passphrase entry when
gnome-keyring's
gpg-agent is active. If you disable gnome-keyring's gpg support then this
issue goes
away (i.e thing work). This problem also affects gpa and is a general
On 28/07/14 09:40 AM, Joachim Breitner wrote:
BTW, what should the FQDN even be here? My laptop doesn’t have a FQDN
that resolves to it, so the concept seems to be dubious at least.
Actually unless your laptop is not connected to a network via DHCP there
is a 90% probability that if
:08 -0400, Daniel Dickinson wrote:
On 28/07/14 09:40 AM, Joachim Breitner wrote:
BTW, what should the FQDN even be here? My laptop doesn’t have a FQDN
that resolves to it, so the concept seems to be dubious at least.
Actually unless your laptop is not connected to a network via DHCP
On 08/09/14 01:18 PM, Daniel Dickinson wrote:
I think you're wrong. Setting hostname via dhcp (usually not enabled)
is different than getting domain from dhcp (usually enabled AIUI).
They are completely configuration items in the dhclient and similar tools.
Sorry, I meant completely
On 08/09/14 01:18 PM, Daniel Dickinson wrote:
I think you're wrong. Setting hostname via dhcp (usually not enabled)
is different than getting domain from dhcp (usually enabled AIUI).
They are completely configuration items in the dhclient and similar tools.
Speaking of which, perhaps
Package: apache2.2-common
Version: 2.2.22-13+deb7u3
Severity: normal
Apache fails to start due to unimplemented function in the default configuration
when run on kfreebsd (at least amd64 but probably all).
The solution is to add
AcceptMutex fcntl
in a file in /etc/apache2/conf.d
Regards,
I have finally got things calmed down I ought to be able to make time
sometime in the next two weeks to work on this and do some personal live
image stuff (i.e. actually use live-build).
I also plan on further investigating the apt thing that causes
'suggests' to end up in the image - from what I
On 05/09/14 07:42 AM, Craig Small wrote:
On Thu, Sep 04, 2014 at 09:21:52AM -0400, Daniel Dickinson wrote:
I will have to further testing to confirm this, but from outside the
jail I can see that procfs is mounted on jail's proc. Since FreeNAS
runs on FreeBSD that looks to me like FreeBSD's
On 01/09/14 06:30 PM, Debian Bug Tracking System wrote:
Thank you for filing a new Bug report with Debian.
This is an automatically generated reply to let you know your message
has been received.
Your message is being forwarded to the package maintainers and other
interested parties for
On 01/09/14 06:36 PM, Debian Bug Tracking System wrote:
Thank you for filing a new Bug report with Debian.
This is an automatically generated reply to let you know your message
has been received.
Your message is being forwarded to the package maintainers and other
interested parties for
On 01/09/14 06:24 PM, Debian Bug Tracking System wrote:
Thank you for filing a new Bug report with Debian.
This is an automatically generated reply to let you know your message
has been received.
Your message is being forwarded to the package maintainers and other
interested parties for
On 01/09/14 06:27 PM, Debian Bug Tracking System wrote:
Thank you for filing a new Bug report with Debian.
This is an automatically generated reply to let you know your message
has been received.
Your message is being forwarded to the package maintainers and other
interested parties for
On 01/09/14 06:21 PM, Debian Bug Tracking System wrote:
Thank you for filing a new Bug report with Debian.
This is an automatically generated reply to let you know your message
has been received.
Your message is being forwarded to the package maintainers and other
interested parties for
On 04/09/14 07:45 AM, Craig Small wrote:
On Sun, Aug 31, 2014 at 10:01:08PM -0400, Daniel Dickinson wrote:
If you install debian/kfreefsd-amd64 inside a freebsd jail (sort of like
LXC/chroot-on-steroids)
then attempts to use the commands from procps gives the error that
/proc/version does
Package: procps
Version: 1:3.3.3-3
Followup-For: Bug #663012
If you install debian/kfreefsd-amd64 inside a freebsd jail (sort of like
LXC/chroot-on-steroids)
then attempts to use the commands from procps gives the error that
/proc/version does not exist
even thogh linprocfs is in fact mounted.
Package: clamav-daemon
Version: 0.98.4+dfsg-0+deb7u2
Severity: normal
/etc/init.d/clamav-deamon uses --name in it's start-stop-daemon calls for stop
and restart.
This fails when process names are not available due to use of certain
virtualized environments
use as kfreebsd in freebsd jail
Package: clamav-freshclam
Version: 0.98.4+dfsg-0+deb7u2
Severity: normal
Use of --name $DAEMON in start-stop-daemon calls to stop/restart/reload the
daemon results in failure to
stop/restart/reload when process names are not available due to limited /proc.
This occurs in a number
of
Package: clamav-milter
Version: 0.98.4+dfsg-0+deb7u2
Severity: normal
Bug #760219 also applies to clamav-milter.
-- Package-specific info:
--- configuration ---
Checking configuration files in /etc/clamav
Config file: clamd.conf
---
LogFile = /var/log/clamav/clamav.log
Package: dovecot-core
Version: 1:2.1.7-7+deb7u1
Severity: normal
File: /etc/init.d/dovecot
The use of --name $DAEMON in start-stop-daemon commands for
stopping/restarting/reloading daemon results
in failures to a) install (due to failure of initscript) and b) failure to
stop/restart/reload
Package: freebsd-nfs-common
Version: 9.0+ds1-11~deb7u1
Severity: normal
File: /etc/init.d/nfsiod
Use of --name $DAEMON in start-stop-daemon start/stop/reload causes those
functions of the initscript
to fail when inside a freebsd jail due to limited /proc for which process names
are not
Package: xfce4-session
Version: 4.10.1-8
Severity: normal
xcfe4-session still recommends xscreensaver despite that fact that for years
xscreensaver has prevented (even
with DPMS settings turned off) prevented xfce's power manager from shutting of
the display or going into
sleep mode due to
Package: xfce4-settings
Version: 4.10.1-2
Severity: normal
With a dual head system setting desktop backgrounds to image lists that are
supposed to change every minutes
results in both displays having only grey background.
Gnome has a similar problem with backgrounds on dual head - perhaps there
Package: libvirt-bin
Version: 1.2.4-3.2
Severity: normal
I observed that libvirt-bin's networks failed to autostart despite being
so configure and when I attempted to manually (via virsh) start the network I
got:
error: Failed to start network vmpriv
error: internal error: Failed to apply
Note that the id mapping issue is not actually caused by the wrong arg
count. The wrong arg count appears to be harmless (no effect). The id
mapping was failing because the nfs server being accessed was in fact
using the wrong domain name.
Regards,
Daniel
--
To UNSUBSCRIBE, email to
Package: smart-notifier
Version: 0.28-5
Severity: wishlist
I got a notice of drive health change which I tracked down in the syslog to
single degree increase
in temperature. That's a little too paranoid for me. I'd like to be able to
skip single degree
temperature (there's that much variation
Package: gnome-control-center
Version: 1:3.12.1-4
Severity: minor
The advertised functionality of the default background (changes to a different
background
periodically) is not present, at least with dual monitor setup. That is the
background just
stays on the same shades of green geometric
Package: gnome-control-center
Version: 1:3.12.1-4
Severity: normal
Right-clicking change background and selecting a background only affects the
primary monitor at
least when you have manually selected what is by default the secondary monitor
as the primary
monitor. Right-clicking on the
Package: nfs-common
Version: 1:1.2.8-6
Severity: normal
idmapd does not work (fails to use correct domain depsite configure in
idmap.conf) because
/etc/request-key.d/id_resolver.conf has incorrect number of arguments. Syslog
says:
Aug 2 22:19:04 host nfsidmap[29796]: Bad arg count. Check
Package: openocd
Version: 0.7.0-2
Severity: normal
Product:Vendor 0403:6001 is incorrectly assigned to plugdev by openocd udev
rules.
This is in fact a generic FTDI serial convert product:vendor and as such should
be
assigned to 'dialout' as with all other ttyUSB devices.
In openOCD it is
if
it is dressed up as technical, which is why the arguments end up being
political.
Regards,
Daniel
On 29/07/14 03:22 AM, Joachim Breitner wrote:
Hi,
Am Dienstag, den 29.07.2014, 00:22 -0400 schrieb Daniel Dickinson:
Yeah but the guy claiming FQDN broken is the same Lennart who seems hell
bent
with libnss-myhostname.
Regards,
Daniel
On Sun, 2014-07-27 at 20:25 +0200, Joachim Breitner wrote:
Hi,
Am Sonntag, den 27.07.2014, 13:53 -0400 schrieb Daniel Dickinson:
Package: libnss-myhostname
Version: 0.3-6
Severity: serious
Takes over names resolution of local host's name
,
Daniel
On Sun, 2014-07-27 at 20:25 +0200, Joachim Breitner wrote:
Hi,
Am Sonntag, den 27.07.2014, 13:53 -0400 schrieb Daniel Dickinson:
Package: libnss-myhostname
Version: 0.3-6
Severity: serious
Takes over names resolution of local host's name and causes apps that
need FQDN
Daniel Dickinson:
Package: libnss-myhostname
Version: 0.3-6
Severity: serious
Takes over names resolution of local host's name and causes apps that
need FQDN instead of just
hostname to fail (becuase myhostname fails to include a domain).
Can you explain the problems in more detai
On 27/07/14 02:25 PM, Joachim Breitner wrote:
Hi,
Am Sonntag, den 27.07.2014, 13:53 -0400 schrieb Daniel Dickinson:
Package: libnss-myhostname
Version: 0.3-6
Severity: serious
Takes over names resolution of local host's name and causes apps that
need FQDN instead of just
hostname
Yeah but the guy claiming FQDN broken is the same Lennart who seems hell
bent on destroying every *nix idiom. I wouldn't go by his opinion.
Regards,
Daniel
On 28/07/14 09:40 AM, Joachim Breitner wrote:
Hi,
Am Montag, den 28.07.2014, 09:21 -0400 schrieb Daniel Dickinson:
On 27/07/14 02
Package: libnss-myhostname
Version: 0.3-6
Severity: serious
Takes over names resolution of local host's name and causes apps that need FQDN
instead of just
hostname to fail (becuase myhostname fails to include a domain).
This is now pulled in by Gnome which means it's bad behviour will break a
On 23/07/14 05:53 AM, Simon McVittie wrote:
On 23/07/14 00:06, Daniel Dickinson wrote:
There is no way to perform actions previously performed from the 'Contact
List' menu because the
top menu bar no longer displays.
Are you using GNOME Shell? If you are, the application menu
that should be remotely relevant.
Regards,
Daniel
On 21/07/14 03:19 AM, Guido Günther wrote:
On Sun, Jul 20, 2014 at 04:19:27AM -0400, Daniel Dickinson wrote:
Package: libvirt-bin
Version: 1.2.4-3
Severity: normal
I have a Wheezy guest I can't shutdown cleanly from libvirt (i.e. without
Package: gnome-control-center
Version: 1:3.8.3-7+b2
Severity: normal
The display settings applet fails to actually be usuable with dual monitors.
Click on the
monitors fails to select that monitor to be operated on (i.e. clicks appear to
have not effect).
Also one cannot drag the monitor to
Package: empathy
Version: 3.12.4-1
Severity: normal
There is no way to perform actions previously performed from the 'Contact List'
menu because the
top menu bar no longer displays. This is perhaps because of incorrect
application of changes
from Ubuntu for Unity (where the menus appear in the
Package: network-manager
Version: 0.9.10.0-1
Severity: normal
On a laptop that was working fine before Jessie and a wifi network for which
other devices have
no issues, network manager keeps dropping the wifi connectin AND does not
automatically reconnect
despite the wifi network being
1 - 100 of 961 matches
Mail list logo
