thanks a lot for the quick upload.
Now that wpasupplicant 2.10 is more widely available, I've seen this issue
popping up at several places. I'm not sure if it's only related to FRITZ!Boxes
but those alone are extremely popular in Germany, so I would have hated if the
next LTS potentially breaks
If it's enabled in the toolchain, is there still a need to explicitly
enable it (like in this case via --enable-lto) in individual packages?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1967782
Public bug reported:
Please consider syncing the following changes from Debian
https://tracker.debian.org/news/1315963/accepted-network-manager-1364-2-source-into-unstable/
For more background see https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=1003907
Seeing that Ubuntu 22.04 will ship
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995655 maybe?
** Bug watch added: Debian Bug tracker #995655
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995655
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I have to add, that I don't have such a NIS or LDAP setup to test this
myself.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1934393
Title:
systemd-logind network access is blocked, and breaks
@Dan: have you actually confirmed, that building and running userdbd
solves those issues with NIS and LDAP?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1934393
Title:
systemd-logind network
> Other than the obvious approach of enabling systemd-userdb for Ubuntu,
I don't see how that would help, given that sytemd-userdb.service has
RestrictAddressFamilies=AF_UNIX AF_NETLINK AF_INET AF_INET6
You basically have the same issue as with systemd-logind.service. Or am I
missing
1) Include drop-in conf files for systemd-logind and systemd-udevd to
remove the networking sandbox
Those drop-in configs should be shipped in the nis package. I don't see
a reason to ship a drop-in for systemd-udevd, fwiw.
--
You received this bug notification because you are a member of
** Bug watch added: Debian Bug tracker #878625
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=878625
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1915502
Title:
"systemd --user" fails to
See also https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=878625
Am Do., 10. Juni 2021 um 20:23 Uhr schrieb Michael Biebl :
>
> The relevant upstream bug report afaics is
> https://github.com/systemd/systemd/issues/7074
>
> Am Do., 10. Juni 2021 um 20:14 Uhr schrieb Michael Biebl
The relevant upstream bug report afaics is
https://github.com/systemd/systemd/issues/7074
Am Do., 10. Juni 2021 um 20:14 Uhr schrieb Michael Biebl :
>
> Am Do., 10. Juni 2021 um 14:50 Uhr schrieb Dan Streetman
> <1915...@bugs.launchpad.net>:
> >
> > Ok, so it does soun
Am Do., 10. Juni 2021 um 14:50 Uhr schrieb Dan Streetman
<1915...@bugs.launchpad.net>:
>
> Ok, so it does sound like this and bug 1916235 are the same issue. And
> this might be 'as designed', since upstream systemd wants systemd-logind
> to talk to systemd-userdb instead of directly connecting to
Turns out, the missing fsck progress bar is a regression:
https://github.com/systemd/systemd/issues/17157
** Bug watch added: github.com/systemd/systemd/issues #17157
https://github.com/systemd/systemd/issues/17157
--
You received this bug notification because you are a member of Ubuntu
>From my personal POV, I consider the progress bar more important then the
>ability to interrupt fsck with CTRL+C.
Nowadays, SSDs are much more common and enable_periodic_fsck = 0 has been the
default for many years now. So this is much less of an issue today then it was
back in 2015, I think.
As for text-only boot: Maybe we could convince upstream to enable
verbose mode once an fsck takes longer then say 30s (similar to how the
eye-of-cyclon animation kicks in when services take a long time to
start). With something like that implemented, dropping fsckd might be an
option, I think.
--
I would be happy to see this patch merged upstream.
There was an attempt a few years ago:
https://lists.freedesktop.org/archives/systemd-devel/2015-March/029186.html
Eventually it was removed again:
https://github.com/systemd/systemd/commit/96d9117ad2db7d8c13f7898127eee8939e88daf1
root@pluto:~# systemctl list-jobs
JOB UNIT TYPE STATE
126 systemd-update-utmp-runlevel.service start waiting
33 setvtrgb.service start waiting
1 graphical.target start waiting
135 plymouth-quit-wait.service
I have the same issue afaics (plymouth get's stuck when docked).
plymouth splash can't be dismissed with ESC.
I installed openssh-server and the system is perfectly accessible
remote. Didn't have time yet to further debug this, as I only have a
smartphone as second device, so debugging via SSH is
Ok, I need to take that back. It also just happened to me when undocked (i.e.
no external monitor).
Just appears to happen less often.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1872159
Title:
It would be good adding this information to the upstream bug tracker.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1803993
Title:
Password appears on the VT1 screen
To manage
@rbalint if you can reliably reproduce the issue, it would probably be a
good idea if you follow up on that upstream bug tracker
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1803993
Title:
Looking at the discussion at
https://gitlab.freedesktop.org/xorg/xserver/issues/857#note_201402 this
might be a bug in plymouth which is supposedly fixed in plymouth 0.9.4.
Could users who can reliably reproduce the issue post if they have
plymouth installed and if so, which version?
** Bug
Public bug reported:
https://github.com/grpc/grpc/issues/11195
The grpc library is broken as it has been compiled with
"-Bsymbolic-functions". This makes the library unusuable.
-Wl,-Bsymbolic-functions should be stripped from LD_FLAGS when building on
Ubuntu.
** Affects: grpc (Ubuntu)
In Debian, the values in debian/control are only used when the package is
uploaded intially to the archive. The override entry is created from that.
Changing the contents of the archive override is done by the ftp-masters. If
you later change the contents of debian/control does not have an
Public bug reported:
Packages shipping gobject introspection should be in the dedicated
section "introspection". This archive section was added a while ago, see
also the corresponding entry in the debian policy 3.9.3.0:
2.6. Version 3.9.3.0
Released February, 2012.
/etc/systemd/system/sockets.target.wants/snapd.socket
/etc/systemd/system/timers.target.wants/snapd.refresh.timer
/etc/systemd/system/multi-user.target.wants/snapd.firstboot.service
/etc/systemd/system/multi-user.target.wants/snapd.refresh.timer
Public bug reported:
snapd.postrm has some custom clean up routines, but not the init-system-helper
generated code.
I'm not sure if the omission of #DEBHELPER# is deliberately or an oversight.
If the former, the package should clean up the dangling symlinks manually when
removed.
ProblemType:
Public bug reported:
Hi,
the following conffile is marked as obsolete in my dpkg status db
/etc/bash_completion.d/ufw 50de7ccdcddb779093156f133d9c0a5e obsolete
Ufw now ships /usr/share/bash-completion/completions/ufw, so the
conffile should be removed on upgrades.
ProblemType: Bug
https://www.freedesktop.org/wiki/Software/systemd/NetworkTarget/ has
more information on this topic.
Ideally openntpd would handle networks coming and going more gracefully.
A dependency on network-online.target is only a band-aid.
--
You received this bug notification because you are a member
Public bug reported:
The following files are marked obsolete after the upgrade to 16.04:
/etc/init/pulseaudio.conf 6244f8d452b29be7d17219b2db34138f obsolete
/etc/init.d/pulseaudio df2873ee4f4673d53e3562a0de6e8aa0 obsolete
/etc/default/pulseaudio 777f75f5521eab11c647da5c55544b1b obsolete
Public bug reported:
The following conffiles were not cleaned up after the upgrade to 16.04:
/etc/bash_completion.d/gdbus 3c6022ac0bf85f2f374358a52456e803 obsolete
/etc/bash_completion.d/gsettings ed6dbd29972bb65275e46f1cb1ac5062 obsolete
/etc/bash_completion.d/gresource
@pitti: will /etc/systemd/system/tmp.mount override a /tmp mount point
from /etc/fstab (/run vs /etc)?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1545707
Title:
Error message "Operation failed:
An explicit reload should not be necessary for "enable".
I also can't reproduce the problem:
$ cp /usr/share/systemd/tmp.mount /etc/systemd/system/tmp2.mount
$ systemctl enable tmp2.mount
Created symlink from /etc/systemd/system/local-fs.target.wants/tmp2.mount to
man bootup(7)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1532553
Title:
/etc/halt.local has become /usr/sbin/halt.local
To manage notifications about this bug go to:
fwiw, halt-local.service was hooked up in final.target and contains the
following:
[Unit]
Description=/usr/sbin/halt.local Compatibility
ConditionFileIsExecutable=/usr/sbin/halt.local
DefaultDependencies=no
After=shutdown.target
Before=final.target
To apply that to my
Add a native service file and hook it up in the shutdown.target. That's
the cleanest solution.
/etc/systemd/system/foo.service
[Unit]
Description=Run service on shutdown
[Service]
ExecStart=/bin/true
[Install]
WantedBy=shutdown.target
--
You received this bug notification because you are a
Or make that
WantedBy=final.target, if you want to execute it during late shutdown.
See man systemd.special(7)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1532553
Title:
/etc/halt.local has
Before the introduction of systemd in Debian and Ubuntu, /etc/halt.local was
not supported at all.
Neither sysvinit nor upstart executed that file/script. So I'm mildly suprised,
when you say "it always worked".
We decided to not introduce support for this legacy, sysv specific
service, which
Public bug reported:
The package declares a dependency on systemd-shim.
With systemd being the default init, this dependency is no longer required and
actually wanted.
The dependency on systemd-services should also either be replaced with a
dependency on systemd (or libpam-systemd, depending on
Public bug reported:
systemd-services is a virtual package provided by systemd for
transitional purposes.
Please update the dependency to directly depend on systemd instead (or
if a dependency on a working logind session is required, a dependency on
libpam-systemd might be more suitable)
**
Public bug reported:
Now that policykit-1 uses libpam-systemd/logind, please drop the
dependency on consolekit.
** Affects: polkit-qt5-1 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
ExecStop=/bin/true was my first idea, but Martin rightfully pointed out, that
this doesn't influence KillMode, i.e. we need KillMode=none.
With that KillMode setting, I think we can actually drop ExecStop=/bin/true, so
what remains is
KillMode=none
systemd has a final killing spree, before it
(In reply to Simon McVittie from comment #7)
(In reply to Simon McVittie from comment #6)
Perhaps it would be better to make the stop command exit
nonzero?
Straw man:
ExecStop=/bin/sh -c echo Stopping the system dbus-daemon is not supported.
Reboot the system instead.; exit 1
...
dbus would be stopped by the final killing spree.
This usually looks like this
stop individual services in reverse order
Sending SIGTERM to remaining processes...
Sending SIGKILL to remaining processes...
Unmounting file systems.
All filesystems unmounted.
Deactivating swaps.
All swaps
This is what -n is for.
Incidentally, this is also used in rsyslog.service file for systemd.
2015-03-29 14:25 GMT+02:00 Hadmut Danisch had...@danisch.de:
Public bug reported:
Hi,
it's rather a feature request than a bug report:
I had to package several network services in docker images
Sorry, meant Before=network.target, of course...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1431774
Title:
cifs mount hangs on shutdown - NetworkManager needs to stop after
network.target
To
Let me chime in here as maintainer of NM in Debian: The reason why we
ship the patch, which removes Wants/Before=network.target is, that this
lead to dependency cycles if services/sysv init scripts in rcS
(sysinit.target) had Should-Start/Required-Start: $network, like for
example
Fred, please don't subscribe random people and spam them with email.
Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1431609
Title:
systemd session for gnome-shell with Wayland backend
To
2014-07-08 14:01 GMT+02:00 Dimitri John Ledkov launch...@surgut.co.uk:
systemd unit for which reload similarly sends SIGHUP. In debian
unstable a native systemd unit is added for rsyslog, for which reload
similarly just sends SIGHUP.
That is not true. The rsyslog.service file in Debian's
2014-07-08 14:25 GMT+02:00 Michael Biebl mbi...@gmail.com:
This is an action only implemented by the SysV init script. That means
it currently actually relies on the SysV init script even when booted
with systemd.
In Debian, SysV init scripts are still mandatory, so this is sort-of
ok, even
Also related
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=672218
--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Bug watch added: Debian Bug tracker #672218
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=672218
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1331891
Title:
[systemd]
Do you think it's a good idea if systemd-shim lies about the version number?
It's not like it is implementing the full systemd (D-Bus) API.
Somehow I have the feeling it would be better/cleaner if systemd-shim would
export its own version number (maybe with distinct prefix) so clients can find
Hi Richard!
(In reply to comment #9)
I'm pretty sure we work around the kernel bug in new releases -- the problem
was tat the kernel sometimes changed the reporting data units between suspend
and resume. If this doesn't work with a new kernel and upower, than please
reopen. Thanks.
Which
2011/2/19 bugbot 654...@bugs.launchpad.net:
Hey Michael,
Thanks for testing maverick during its development period. Unfortunately it
looks like this bug report didn't get attention during the maverick
development period. But I see there's not been more comments on the bug
since the
2010/12/21 ingo 688...@bugs.launchpad.net:
On Tue, 2010-12-21 at 12:41 +, Scott James Remnant wrote:
General note: ubuntu-devel is *NOT* the correct list to discuss Upstart
changes unless they're unique to Ubuntu.
Wouldn't it be fair to inform Debian about those problems before they
2010/12/20 James Hunt 688...@bugs.launchpad.net:
3) Modify all upstart configs for services which are slow to stop such that
they stop on unmount-filesystem,
rather than stop on runlevel [016].
- What about single user mode? I guess when switching to runlevel 1 we
want to stop services
2010/12/20 James Hunt 688...@bugs.launchpad.net:
3) Modify all upstart configs for services which are slow to stop such that
they stop on unmount-filesystem,
rather than stop on runlevel [016].
- What about single user mode? I guess when switching to runlevel 1 we
want to stop services
2010/12/16 Clint Byrum cl...@fewbar.com:
/etc/init.d/sendsigs has this code:
# Upstart jobs have their own stop on clauses that sends
# SIGTERM/SIGKILL just like this, so if they're still running,
# they're supposed to be
for pid in $(initctl list | sed -n -e
2010/12/16 Clint Byrum cl...@fewbar.com:
/etc/init.d/sendsigs has this code:
# Upstart jobs have their own stop on clauses that sends
# SIGTERM/SIGKILL just like this, so if they're still running,
# they're supposed to be
for pid in $(initctl list | sed -n -e
2010/12/14 Clint Byrum cl...@fewbar.com:
I do think the appropriate fix is to have umountfs emit an 'unmounting-
filesystems' event and anything that does a 'start on local-filesystems'
or 'start on filesystem' should also 'stop on unmounting-filesystems',
What do you do about services which
2010/12/14 Clint Byrum cl...@fewbar.com:
I do think the appropriate fix is to have umountfs emit an 'unmounting-
filesystems' event and anything that does a 'start on local-filesystems'
or 'start on filesystem' should also 'stop on unmounting-filesystems',
What do you do about services which
Public bug reported:
I'm using mysql-server-5.1 on a 10.04 LTS installation.
The mysql db is around 27GB and on a separate partition mounted as
/var/lib/mysql.
On shutdown I get the following error message:
Checking for running unattended-upgrades: * Asking all remaining processes to
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mysql-5.1 in ubuntu.
https://bugs.launchpad.net/bugs/688541
Title:
race condition on shutdown (leads to corrupted fs)
--
Ubuntu-server-bugs mailing list
2010/12/10 Ante Karamatić iv...@grad.hr:
Suggestion: make umountfs wait for all upstart jobs to finish.
Doesn't that conflict though with what is written in
/etc/init.d/sendsigs:
# Upstart jobs have their own stop on clauses that sends
# SIGTERM/SIGKILL just like this, so if
Public bug reported:
I'm using mysql-server-5.1 on a 10.04 LTS installation.
The mysql db is around 27GB and on a separate partition mounted as
/var/lib/mysql.
On shutdown I get the following error message:
Checking for running unattended-upgrades: * Asking all remaining processes to
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/688541
Title:
race condition on shutdown (leads to corrupted fs)
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
2010/12/10 Ante Karamatić iv...@grad.hr:
Suggestion: make umountfs wait for all upstart jobs to finish.
Doesn't that conflict though with what is written in
/etc/init.d/sendsigs:
# Upstart jobs have their own stop on clauses that sends
# SIGTERM/SIGKILL just like this, so if
Public bug reported:
Binary package hint: xorg
The following conffileS are marked obsolete but are not removed on upgrades:
# dpkg -s x11-common | grep obsolete
/etc/gdm/failsafeInstall afb4035f60712f98883b1123229139a7 obsolete
/etc/gdm/failsafeHelpmsg 1d6b344ddc6910632b09a2bce2ec93a5 obsolete
** Attachment added: BootDmesg.txt
https://bugs.launchpad.net/bugs/654353/+attachment/1670419/+files/BootDmesg.txt
** Attachment added: CurrentDmesg.txt
https://bugs.launchpad.net/bugs/654353/+attachment/1670420/+files/CurrentDmesg.txt
** Attachment added: DRM.card0.SVIDEO.1.txt
I can confirm the behaviour, when on battery. The hard disk spin downs
are much too aggressive. Imho we also need to evaluate if the power
saving justify this hook after all. One compromise could be, to install
the harddrive hook but disable it by default.
I can't confirm the problem though, when
Public bug reported:
Binary package hint: tomboy
In version 1.1.1-0ubuntu1, tomboy got a dependency on libnunit2.4-cil, which in
turn pulls another 10 Mb of depencies here.
A dependency on nunit does not seem correct and should be removed.
ProblemType: Bug
Architecture: i386
Date: Mon Feb 1
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/38592789/Dependencies.txt
--
New dep on libnunit2.4-cil pulls 10Mb of dependencies
https://bugs.launchpad.net/bugs/515306
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Public bug reported:
I'm having this file in /etc/udev/rules.d/
# ls -la /etc/udev/rules.d/65-libmtp.rules
-rw-r--r-- 1 root root 4641 2006-12-18 03:16 /etc/udev/rules.d/65-libmtp.rules
As libmtp8 ships its rules file in /lib/udev/rules.d nowadays, I can
only assume that the file in /etc was
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/37836825/Dependencies.txt
--
/etc/udev/rules.d/65-libmtp.rules not migrated/removed on upgrades
https://bugs.launchpad.net/bugs/506791
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Public bug reported:
Binary package hint: hplip
I just upgraded a system from karmic to lucid.
After the upgrade I still have the file
/etc/udev/rules.d/56-hpmud_support.rules, although this file is marked obsolete
and hplip now ships this file in /lib/udev/rules.d
I did not modify this file,
** Attachment added: BootDmesg.txt
http://launchpadlibrarian.net/37837050/BootDmesg.txt
** Attachment added: CurrentDmesg.txt
http://launchpadlibrarian.net/37837051/CurrentDmesg.txt
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/37837052/Dependencies.txt
**
I just checked hplip.preinst. There is a bug in the conffile removal code.
See http://wiki.debian.org/DpkgConffileHandling how to correctly handle this.
In my specifc case
dpkg-query -W -f='${Conffiles}' hplip | sed -n -e \'
/etc/udev/rules.d/56-hpmud_support.rules's/.* //p\
will yield
Public bug reported:
Binary package hint: util-linux
util-linux ships native upstart jobs.
After the upgrade the sysv init script
/etc/init.d/hwclock.sh and the symlinks
/etc/rc0.d/K25hwclock.sh /etc/rc6.d/K25hwclock.sh
are not removed.
hwclock.sh is marked as obsolete:
/etc/init.d/hwclock.sh
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/32266946/Dependencies.txt
--
obsolete init script hwclock.sh after upstart migration
https://bugs.launchpad.net/bugs/434767
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
The package also still ships the directory
/lib/udev/rules.d
which is no longer required as the udev rules file has been removed/replaced.
--
obsolete init script hwclock.sh after upstart migration
https://bugs.launchpad.net/bugs/434767
You received this bug notification because you are a member
Public bug reported:
Binary package hint: bluez
bluetoothd is started via udev here, but it does not want to die on SIGTERM:
r...@pluto:~ # ps aux | grep bluetoothd
root 2946 0.1 0.2 3704 1712 ?Ss 21:51 0:00
/usr/sbin/bluetoothd --udev
r...@pluto:~ # kill -15 2946
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/32273148/Dependencies.txt
--
bluetoothd does not die on SIGTERM
https://bugs.launchpad.net/bugs/434852
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
** Bug watch added: bugzilla.adiscon.com/ #144
http://bugzilla.adiscon.com/show_bug.cgi?id=144
** Changed in: rsyslog
Status: Fix Released = Unknown
** Changed in: rsyslog
Remote watch: bugzilla.adiscon.com/ #133 = bugzilla.adiscon.com/ #144
--
Don't run as root
Public bug reported:
If dbus is not running (e.g. in my karmic chroot environment), I get
this nasty error message on each apt operation:
# apt-get update
...
Failed to open connection to system message bus: Failed to connect to socket
/var/run/dbus/system_bus_socket: No such file or directory
** Attachment added: dont_run_packagekit_update_when_dbus_not_running.patch
http://launchpadlibrarian.net/28036899/dont_run_packagekit_update_when_dbus_not_running.patch
--
Don't fail if dbus is not running
https://bugs.launchpad.net/bugs/388623
You received this bug notification because
2009/4/6 Martyn Russell mar...@lanedo.com:
Not having tracker-processes is a packaging bug, it is available from
0.6.92 onwards, but it wasn't included. There is a bug about it here
somewhere :)
Those two warnings above are fine to ignore.
The logs you show above is with QDBM failing to
Hi,
maybe you want to enable the new-style evolution plugin.
For that you have to build-depend on
evolution-dev (= 2.25.5)
and
evolution-data-server-dev (= 2.25.5)
I couldn't test this on Debian though, as the required b-deps are not
there yet.
Martyn, Philip, will the old-style evolution
2009/2/17 Daniel Holbach daniel.holb...@ubuntu.com:
Just FYI: the procps change was in Debian already, other than that great
work! :)
In a future version these files could get installed too:
dh_install: usr/share/man/man1/tracker-services.1 exists in debian/tmp but is
not installed to
FYI
http://packages.debian.org/experimental/tracker
http://git.debian.org/?p=users/biebl/tracker.git;a=summary (experimental branch)
I decided to *not* move libtracker-common and libtracker-module into
separate binary packages until they are moved to /usr/lib/ (and not
/usr/lib/tracker)
Cheers,
2009/1/29 Alexander Sack a...@jwsdot.com:
Michael, what's your opinion on status for init.d script?
The Debian network-manager init script has a status option.
Which reminds me, that it would probably be a good idea if Debian and
Ubuntu used the same name for the sysv init script
-prefer_odt2txt.patch
- Use odt2txt to index OpenOffice documents. Closes: #478091
-- Michael Biebl [EMAIL PROTECTED] Sun, 25 May 2008 02:20:25 +0200
Cheers,
Michael
--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
--
Tracker
2008/5/5 Emilio Pozuelo Monfort [EMAIL PROTECTED]:
I'll add untex to tracker's recommends
It already is (at least in the Debian package). Maybe you should just
sync the Ubuntu package.
Cheers,
Michael
--
Why is it that all of the instruments seeking intelligent life in the
universe are
2008/3/12, Saïvann Carignan [EMAIL PROTECTED]:
Thanks for your fast confirmation! Is there somebody else that can
confirm that this bug is fixed in Gutsy? Michael Biebl?
Yep, seems to be fixed (for me).
Michael
--
Why is it that all of the instruments seeking intelligent life
Public bug reported:
After upgrading from firefox 2 to 3beta3 (where the conffiles now are in
/etc/firefox-3.0), I still have a lot of cruft in /etc/firefox and /etc
/mozilla-firefox:
Package: firefox
Status: install ok installed
Priority: optional
Section: web
Installed-Size: 128
Maintainer:
2008/2/14, mikko sorri [EMAIL PROTECTED]:
Acer Aspire 1362 laptop, Hardy with latest updates.
Messages in user.log every time after boot:
Feb 14 16:31:38 mikkojakaisa dhcdbd: Started up.
Feb 14 16:31:41 mikkojakaisa dhcdbd: message_handler: message handler not
found under
2007/10/5, Emilio Pozuelo Monfort [EMAIL PROTECTED]:
The gnome-searchtool icon is in the tango-icon-theme, human-icon-theme,
and gnome-icon-theme. Maybe we should depend on any of them.
Michael, what do you think about this? Do you have any preference?
I changed the icon name to system-search
2007/12/27, Emilio Pozuelo Monfort [EMAIL PROTECTED]:
I think just is a keyword, so it won't act as a search term.
that's correct, just is a stop word. see also
/usr/share/tracker/languages/stopwords.en
Jamie, can you confirm that? If that's correct, we should improve the
documentation or
2007/12/21, Emilio Pozuelo Monfort [EMAIL PROTECTED]:
Note that if I enter 'foo' in the applet search box, then close it, and
then open it again, 'foo' is selected, but hasn't the cursor input. It
should have it.
Works for me. If I search for foo, close it, open it again, foo is
selected. If
2007/12/21, Emilio Pozuelo Monfort [EMAIL PROTECTED]:
BTW this is about closing the applet, not where it's displayed.
IMHO it doesn't need an [X] to close it, but it should be closed if I
click outside it, as NetworkManager (and others such as gnome-power-
manager, although g-p-m looks more
1 - 100 of 165 matches
Mail list logo
