[Bug 2070061] Re: Clean up the DEP17 dpkg diversions
Speaking of which, is the following expected (a system that has recently been upgraded to 24.04): ``` # ls -la / insgesamt 84 drwxr-xr-x 21 root root 4096 Jun 24 23:49 . drwxr-xr-x 21 root root 4096 Jun 24 23:49 .. lrwxrwxrwx 1 root root 7 Jan 7 00:36 bin -> usr/bin drwxr-xr-x 2 root root 4096 Apr 8 16:46 bin.usr-is-merged drwxr-xr-x 4 root root 4096 Jun 14 12:19 boot drwxr-xr-x 19 root root 5040 Jun 24 23:46 dev drwxr-xr-x 148 root root 12288 Jun 24 23:48 etc drwxr-xr-x 3 root root 4096 Jan 19 17:12 home lrwxrwxrwx 1 root root 7 Jan 7 00:36 lib -> usr/lib lrwxrwxrwx 1 root root 9 Jan 7 00:36 lib32 -> usr/lib32 lrwxrwxrwx 1 root root 9 Jan 7 00:36 lib64 -> usr/lib64 drwxr-xr-x 2 root root 4096 Apr 8 16:46 lib.usr-is-merged lrwxrwxrwx 1 root root10 Jan 7 00:36 libx32 -> usr/libx32 drwx-- 2 root root 16384 Jan 6 23:19 lost+found drwxr-xr-x 3 root root 4096 Jan 11 21:44 media drwxr-xr-x 6 root root 4096 Jun 2 09:54 mnt drwxr-xr-x 3 root root 4096 Jan 7 21:14 opt dr-xr-xr-x 433 root root 0 Jun 24 23:45 proc drwx-- 9 root root 4096 Jun 14 12:02 root drwxr-xr-x 35 root root 860 Jun 24 23:48 run lrwxrwxrwx 1 root root 8 Jan 7 00:36 sbin -> usr/sbin drwxr-xr-x 2 root root 4096 Apr 8 16:46 sbin.usr-is-merged drwxr-xr-x 2 root root 4096 Feb 28 01:24 srv dr-xr-xr-x 13 root root 0 Jun 24 23:48 sys drwxrwxrwt 20 root root 520 Jun 24 23:51 tmp drwxr-xr-x 14 root root 4096 Aug 8 2023 usr drwxr-xr-x 14 root root 4096 Jun 14 12:23 var ``` Specifically those $foo.usr-is-merged directories? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2070061 Title: Clean up the DEP17 dpkg diversions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/2070061/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967782] Re: Please sync latest changes from 1.36.4-2
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 WiFi for lots of users. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967782 Title: Please sync latest changes from 1.36.4-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1967782/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967782] Re: Please sync latest changes from 1.36.4-2
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 Title: Please sync latest changes from 1.36.4-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1967782/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967782] [NEW] Please sync latest changes from 1.36.4-2
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 wpasupplicant 2.10 it would be good to have this patch. When you sync the changes from Debian, a few remarks on the remaining diff to the Debian package: - isc-dhcp-client Depends NetworkManager defaults to its internal dhcp client (based on sd-network) since a while. Ubuntu doesn't override that default. So either it should explicitly override that default and specify dhclient as preferred dhcp client or it should drop this dependency as Debian does (or at least demote it). - avahi-autoipd Suggests NetworkManager doesn't use avahi-autoipd anymore. See the relevant commit from 2016! https://salsa.debian.org/utopia-team/network-manager/-/commit/d701201bfd5b2d7a6bb1cc81660ae55fd4f4e36b - lto Enabling lto means significantly increased build times. Last time I checked the space savings were miniscule. That's why the Debian doesn't enable lto. - restarting NM on upgrades NM does *not* tear down Ethernet connections on restart. For WiFi connections the situation is different but keep in mind that wpasupplicant.postinst will restart its service anyway ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967782 Title: Please sync latest changes from 1.36.4-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1967782/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1957086] Re: Autopkgtest systemd fail against dnsmasq 2.86 (22.04)
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. https://bugs.launchpad.net/bugs/1957086 Title: Autopkgtest systemd fail against dnsmasq 2.86 (22.04) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1957086/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1934393] Re: systemd-logind network access is blocked, and breaks remote authentication configurations
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 remote authentication configurations To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1934393/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1934393] Re: systemd-logind network access is blocked, and breaks remote authentication configurations
@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 access is blocked, and breaks remote authentication configurations To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1934393/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1934393] Re: systemd-logind network access is blocked, and breaks remote authentication configurations
> 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 something here? -- 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 remote authentication configurations To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1934393/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1934393] Re: systemd-logind network access is blocked, and breaks remote authentication configurations
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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1934393 Title: systemd-logind network access is blocked, and breaks remote authentication configurations To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1934393/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1915502] Re: "systemd --user" fails to start for non-local users
** 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 start for non-local users To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1915502/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1915502] Re: "systemd --user" fails to start for non-local users
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 : > > > > 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 NIS servers; > > > however Debian (and Ubuntu) disable systemd-userdb. > > > > > > @rbalint @ahasenack @mbiebl, since Debian/Ubuntu disable systemd-userdb, > > > should we also adjust the systemd-logind RestrictAddressFamilies= > > > restriction (and IPAddressDeny= and/or IPAddressAllow=) to allow > > > networking? I'm not sure why ProtectHostname= would also be needed, but > > > I assume it's related to the tighter restrictions on systemd-logind. > > > > I think the nis package should ship a drop-in config for > > systemd-logind, allowing network access in systemd-logind. > > This shouldn't be enabled globally for all users. > > > > As for ldap: If you use the new libpam-ldapd, there should be no > > problem, as the network access is delegated to a separate process > > (nscld). -- 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 start for non-local users To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1915502/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1915502] Re: "systemd --user" fails to start for non-local users
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 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 NIS servers; > > however Debian (and Ubuntu) disable systemd-userdb. > > > > @rbalint @ahasenack @mbiebl, since Debian/Ubuntu disable systemd-userdb, > > should we also adjust the systemd-logind RestrictAddressFamilies= > > restriction (and IPAddressDeny= and/or IPAddressAllow=) to allow > > networking? I'm not sure why ProtectHostname= would also be needed, but > > I assume it's related to the tighter restrictions on systemd-logind. > > I think the nis package should ship a drop-in config for > systemd-logind, allowing network access in systemd-logind. > This shouldn't be enabled globally for all users. > > As for ldap: If you use the new libpam-ldapd, there should be no > problem, as the network access is delegated to a separate process > (nscld). ** Bug watch added: github.com/systemd/systemd/issues #7074 https://github.com/systemd/systemd/issues/7074 -- 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 start for non-local users To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1915502/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1915502] Re: "systemd --user" fails to start for non-local users
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 NIS servers; > however Debian (and Ubuntu) disable systemd-userdb. > > @rbalint @ahasenack @mbiebl, since Debian/Ubuntu disable systemd-userdb, > should we also adjust the systemd-logind RestrictAddressFamilies= > restriction (and IPAddressDeny= and/or IPAddressAllow=) to allow > networking? I'm not sure why ProtectHostname= would also be needed, but > I assume it's related to the tighter restrictions on systemd-logind. I think the nis package should ship a drop-in config for systemd-logind, allowing network access in systemd-logind. This shouldn't be enabled globally for all users. As for ldap: If you use the new libpam-ldapd, there should be no problem, as the network access is delegated to a separate process (nscld). -- 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 start for non-local users To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1915502/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880250] Re: Ctrl-C message displayed without any actual disk check
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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880250 Title: Ctrl-C message displayed without any actual disk check To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1880250/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880250] Re: Ctrl-C message displayed without any actual disk check
>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. I think text-only boot (without plymouth and without quiet) has a reasonable enough progress report from fsck. Without fsckd, we'd have no progress report in plymouth and quiet text-only boots. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880250 Title: Ctrl-C message displayed without any actual disk check To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1880250/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880250] Re: Ctrl-C message displayed without any actual disk check
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. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880250 Title: Ctrl-C message displayed without any actual disk check To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1880250/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880250] Re: Ctrl-C message displayed without any actual disk check
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 https://lists.freedesktop.org/archives/systemd-devel/2015-April/030175.html -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880250 Title: Ctrl-C message displayed without any actual disk check To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1880250/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872159] Re: booting with splash hangs when external monitors are connected (pure intel 8th gen laptop)
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 start running 116 system-getty.slice start waiting 2 multi-user.targetstart waiting 6 jobs listed. root@pluto:~# systemctl status plymouth-quit-wait.service ● plymouth-quit-wait.service - Hold until boot process finishes up Loaded: loaded (/lib/systemd/system/plymouth-quit-wait.service; static; vendor preset: enabled) Active: activating (start) since Sun 2020-05-03 18:34:06 CEST; 38min ago Main PID: 721 (plymouth) Tasks: 1 (limit: 19009) Memory: 296.0K CGroup: /system.slice/plymouth-quit-wait.service └─721 /bin/plymouth --wait Mai 03 18:34:06 pluto systemd[1]: Starting Hold until boot process finishes up... Killing the plymouthd process and restarting gdm3 makes the boot complete successfully. -- 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: booting with splash hangs when external monitors are connected (pure intel 8th gen laptop) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1872159/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872159] Re: booting with splash hangs when external monitors are connected (pure intel 8th gen laptop)
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 a bit cumbersome. -- 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: booting with splash hangs when external monitors are connected (pure intel 8th gen laptop) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1872159/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872159] Re: booting with splash hangs when external monitors are connected (pure intel 8th gen laptop)
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: booting with splash hangs when external monitors are connected (pure intel 8th gen laptop) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1872159/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1803993] Re: Password appears on the VT1 screen
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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1803993/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1803993] Re: Password appears on the VT1 screen
@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: Password appears on the VT1 screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1803993/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1803993] Re: Password appears on the VT1 screen
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 watch added: gitlab.freedesktop.org/xorg/xserver/issues #857 https://gitlab.freedesktop.org/xorg/xserver/issues/857 -- 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1803993/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1748586] [NEW] Segfault when library is linked using "-Bsymbolic-functions"
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) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1748586 Title: Segfault when library is linked using "-Bsymbolic-functions" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grpc/+bug/1748586/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1639050] Re: Wrong package section, should be in "introspection"
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 influence on the override file. So, this needs to be assigned to your ftp masters, they need to fix the overrides and should be able to do that in one go. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1639050 Title: Wrong package section, should be in "introspection" To manage notifications about this bug go to: https://bugs.launchpad.net/webapps-sprint/+bug/1639050/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1639050] [NEW] Wrong package section, should be in "introspection"
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. 2.4 New archive sections _education_, _introspection_, and _metapackages_ added. Packages shipping gobject introspection should be named gir1.2-NAMESPACE-VERSION. Based on the output of apt-cache, the following packages are in the wrong section. I didn't file a separate bug for all of them. I would appreciate if you can adjust the archive section for all the following packages in one go. #!/bin/bash while read pkg ; do apt-cache show $pkg | grep Section | grep -v introspection -q && echo $pkg done < <( apt-cache search -n ^gir1.2 | cut -f1 -d' ' ) gir1.2-accounts-1.0 gir1.2-accountsservice-1.0 gir1.2-appindicator-0.1 gir1.2-appindicator3-0.1 gir1.2-atk-1.0 gir1.2-atspi-2.0 gir1.2-bamf-3 gir1.2-cheese-3.0 gir1.2-clutter-1.0 gir1.2-cogl-1.0 gir1.2-coglpango-1.0 gir1.2-colord-1.0 gir1.2-dbusmenu-glib-0.4 gir1.2-dbusmenu-gtk-0.4 gir1.2-dbusmenu-gtk3-0.4 gir1.2-dee-1.0 gir1.2-ebook-1.2 gir1.2-edataserver-1.2 gir1.2-fcitx-1.0 gir1.2-freedesktop gir1.2-gconf-2.0 gir1.2-gdata-0.0 gir1.2-gdesktopenums-3.0 gir1.2-gdkpixbuf-2.0 gir1.2-gkbd-3.0 gir1.2-glib-2.0 gir1.2-gmenu-3.0 gir1.2-gnomebluetooth-1.0 gir1.2-gnomedesktop-3.0 gir1.2-goa-1.0 gir1.2-gtk-2.0 gir1.2-gtk-3.0 gir1.2-gtkclutter-1.0 gir1.2-gtksource-3.0 gir1.2-gtop-2.0 gir1.2-gucharmap-2.90 gir1.2-gudev-1.0 gir1.2-gweather-3.0 gir1.2-hud-2 gir1.2-hud-client-2 gir1.2-ido3-0.1 gir1.2-json-1.0 gir1.2-lightdm-1 gir1.2-messagingmenu-1.0 gir1.2-nautilus-3.0 gir1.2-networkmanager-1.0 gir1.2-notify-0.7 gir1.2-packagekitglib-1.0 gir1.2-pango-1.0 gir1.2-peas-1.0 gir1.2-polkit-1.0 gir1.2-rb-3.0 gir1.2-rest-0.7 gir1.2-rest-extras-0.7 gir1.2-rsvg-2.0 gir1.2-signon-1.0 gir1.2-soup-2.4 gir1.2-telepathyglib-0.12 gir1.2-timezonemap-1.0 gir1.2-totem-1.0 gir1.2-totem-plparser-1.0 gir1.2-unity-5.0 gir1.2-upowerglib-1.0 gir1.2-wnck-3.0 gir1.2-evince-3.0 gir1.2-geocodeglib-1.0 gir1.2-libertine gir1.2-nmgtk-1.0 gir1.2-ubuntu-app-launch-2 gir1.2-anjuta-3.0 gir1.2-atril gir1.2-caja gir1.2-caribou-1.0 gir1.2-champlain-0.12 gir1.2-cryptui-0.0 gir1.2-diodon-1.0 gir1.2-eom gir1.2-evd-0.1 gir1.2-folks-0.6 gir1.2-gdl-3 gir1.2-gssdp-1.0 gir1.2-gtk-vnc-2.0 gir1.2-gtkchamplain-0.12 gir1.2-gupnp-1.0 gir1.2-gupnp-av-1.0 gir1.2-gupnpigd-1.0 gir1.2-indicate-0.7 gir1.2-itl-1.0 gir1.2-keybinder-3.0 gir1.2-maliit-1.0 gir1.2-mate-menu gir1.2-mate-panel gir1.2-mate-polkit gir1.2-matekbd gir1.2-mutter-3.0 gir1.2-spice-client-glib-2.0 gir1.2-spice-client-gtk-3.0 gir1.2-telepathylogger-0.2 gir1.2-urfkill-glib0 gir1.2-v-sim-1.0 gir1.2-gladeui-2.0 gir1.2-grip gir1.2-javascriptcoregtk-3.0 gir1.2-libvirt-glib-1.0 gir1.2-nemo-3.0 gir1.2-snapd-1 gir1.2-webkit-3.0 ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: gir1.2-accounts-1.0 1.22+16.10.20160520.2-0ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0 Uname: Linux 4.8.0-26-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Thu Nov 3 22:02:42 2016 InstallationDate: Installed on 2011-11-10 (1819 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) SourcePackage: libaccounts-glib UpgradeStatus: Upgraded to yakkety on 2016-11-03 (0 days ago) ** Affects: libaccounts-glib (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug yakkety -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1639050 Title: Wrong package section, should be in "introspection" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libaccounts-glib/+bug/1639050/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1622045] Re: /etc/systemd/system/multi-user.target.wants/snapd.* symlinks not cleaned up when package is removed/purged
/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 /etc/systemd/system/multi-user.target.wants/snapd.service /etc/systemd/system/multi-user.target.wants/snapd.boot-ok.service seems to be the complete list -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1622045 Title: /etc/systemd/system/multi-user.target.wants/snapd.* symlinks not cleaned up when package is removed/purged To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1622045/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1622045] [NEW] /etc/systemd/system/multi-user.target.wants/snapd.* symlinks not cleaned up when package is removed/purged
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: Bug DistroRelease: Ubuntu 16.04 Package: snapd 2.14.2~16.04 ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16 Uname: Linux 4.4.0-36-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity Date: Sat Sep 10 01:26:43 2016 InstallationDate: Installed on 2011-11-10 (1764 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) SourcePackage: snapd UpgradeStatus: Upgraded to xenial on 2016-04-21 (141 days ago) ** Affects: snapd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1622045 Title: /etc/systemd/system/multi-user.target.wants/snapd.* symlinks not cleaned up when package is removed/purged To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1622045/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1602834] [NEW] obsolete conffiles not cleaned up on upgrade
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 DistroRelease: Ubuntu 16.04 Package: ufw 0.35-0ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13 Uname: Linux 4.4.0-28-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity Date: Wed Jul 13 22:19:52 2016 InstallationDate: Installed on 2011-11-10 (1706 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) PackageArchitecture: all SourcePackage: ufw UpgradeStatus: Upgraded to xenial on 2016-04-21 (82 days ago) ** Affects: ufw (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1602834 Title: obsolete conffiles not cleaned up on upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ufw/+bug/1602834/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1588915] Re: network dependent services starting before network is up
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 of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1588915 Title: network dependent services starting before network is up To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openvpn/+bug/1588915/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1573296] [NEW] obsolete conffiles not cleaned up on upgrade
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 /etc/bash_completion.d/pulseaudio df1f94a6b961900162bd18532c3c4c22 obsolete Those files should be cleaned up and the sysv init script properly deregistered. ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1573296 Title: obsolete conffiles not cleaned up on upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1573296/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1573299] [NEW] obsolete conffiles not cleaned up on upgrade
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 305f04df5006e28bbee350d1f9f7f973 obsolete ** Affects: glib2.0 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1573299 Title: obsolete conffiles not cleaned up on upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1573299/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1545707] Re: Error message "Operation failed: No such file or directory" on installing/reconfiguring systemd
@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: No such file or directory" on installing/reconfiguring systemd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1545707/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1545707] Re: Error message "Operation failed: No such file or directory" on installing/reconfiguring systemd
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 /etc/systemd/system/tmp2.mount. -- 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: No such file or directory" on installing/reconfiguring systemd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1545707/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1532553] Re: /etc/halt.local has become /usr/sbin/halt.local
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 /etc/systemd/system/foo.service example: [Unit] Description=Run service on shutdown DefaultDependencies=no After=shutdown.target Before=final.target [Service] ExecStart=/bin/true [Install] WantedBy=final.target Then run "systemctl enable foo.service" and you should be set. -- 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: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1532553/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1532553] Re: /etc/halt.local has become /usr/sbin/halt.local
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: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1532553/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1532553] Re: /etc/halt.local has become /usr/sbin/halt.local
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 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: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1532553/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1532553] Re: /etc/halt.local has become /usr/sbin/halt.local
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 become /usr/sbin/halt.local To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1532553/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1532553] Re: /etc/halt.local has become /usr/sbin/halt.local
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 after a bit of research seems to be Redhat (/sbin/halt.local) and SuSE (/etc/init.d/halt.local) specific. Adding /etc/halt.local to the mix would only confuse things. It's much better to create a native service file with systemd, and it's much easier. -- 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: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1532553/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1518508] [NEW] Update dependency on systemd-services
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) ** Affects: indicator-session (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1518508 Title: Update dependency on systemd-services To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-session/+bug/1518508/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1518507] [NEW] Drop dependency on systemd-shim (and replace system-services)
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 whether it needs logind) or simply dropped. ** Affects: indicator-datetime (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1518507 Title: Drop dependency on systemd-shim (and replace system-services) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1518507/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1448537] [NEW] Please drop dependency on consolekit
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 to Ubuntu. https://bugs.launchpad.net/bugs/1448537 Title: Please drop dependency on consolekit To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/polkit-qt5-1/+bug/1448537/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1438612]
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 unmounts the file systems and I don't think dbus needs to do something special on stop? We might have a problem, if /usr is on NFS and (at least on Debian) dbus-daemon being installed in /usr/bin, which would keep the FS busy. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1438612 Title: remote file systems hang on shutdown, D-BUS stops too early To manage notifications about this bug go to: https://bugs.launchpad.net/dbus/+bug/1438612/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1438612]
(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" > > ... which does work, but logs "Unit dbus.service entered failed state" > during shutdown. It seems better to avoid "crying wolf" if possible, because > it can hide real issues. Spawning a shell (which will burn more cpu cycles then a simple /bin/true), this will also trigger a failure on every shutdown/reboot. Do we really want this? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1438612 Title: remote file systems hang on shutdown, D-BUS stops too early To manage notifications about this bug go to: https://bugs.launchpad.net/dbus/+bug/1438612/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1438612] Re: remote file systems hang on shutdown, D-BUS stops too early
dbus would be stopped by the final killing spree. This usually looks like this Sending SIGTERM to remaining processes... Sending SIGKILL to remaining processes... Unmounting file systems. All filesystems unmounted. Deactivating swaps. All swaps deactivated. Detaching loop devices. All loop devices detached. Detaching DM devices. All DM devices detached. system-shutd[ 51.216341] reboot: Power down own succeeded. Powering off. I don't think, there is anything special that dbus needs to do on stop. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1438612 Title: remote file systems hang on shutdown, D-BUS stops too early To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1438612/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1437821] [NEW] no proper foreground mode
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 : > Public bug reported: > > Hi, > > it's rather a feature request than a bug report: > > I had to package several network services in docker images (and to start > them with supervisor as common practice). While almost all services like > webservers, ldap,... have a running mode without daemonizing, i.e. can > stay in foreground without forking, rsyslog does not seem to have this > (just a debugging mode with setting an environment variable, which, > however, did not run as expected). > > Would be nice to have this in rsyslog as well to be able to start it > from supervisord. > > regards > > ProblemType: Bug > DistroRelease: Ubuntu 14.04 > Package: rsyslog 7.4.4-1ubuntu2.5 > ProcVersionSignature: Ubuntu 3.13.0-48.80-generic 3.13.11-ckt16 > Uname: Linux 3.13.0-48-generic x86_64 > ApportVersion: 2.14.1-0ubuntu3.7 > Architecture: amd64 > CurrentDesktop: XFCE > Date: Sun Mar 29 14:19:56 2015 > InstallationDate: Installed on 2014-08-06 (234 days ago) > InstallationMedia: Ubuntu-Server 14.04.1 LTS "Trusty Tahr" - Release amd64 > (20140722.3) > SourcePackage: rsyslog > UpgradeStatus: No upgrade log present (probably fresh install) > > ** Affects: rsyslog (Ubuntu) > Importance: Undecided > Status: New > > > ** Tags: amd64 apport-bug third-party-packages trusty > > -- > You received this bug notification because you are subscribed to rsyslog > in Ubuntu. > Matching subscriptions: rsyslog-bugs > https://bugs.launchpad.net/bugs/1437821 > > Title: > no proper foreground mode > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1437821/+subscriptions -- 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. https://bugs.launchpad.net/bugs/1437821 Title: no proper foreground mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1437821/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1431774] Re: cifs mount hangs on shutdown - NetworkManager needs to stop after network.target
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 manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1431774/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1431774] Re: cifs mount hangs on shutdown - NetworkManager needs to stop after network.target
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 /etc/init.d/rpcbind in Debian. If there is no such sysv init script Ubuntu, this patch can be dropped indeed. As for Colin's remark in #25, sounds sensible, to add After=network.target to wpa_supplicant.service as well. Have you tried adding that and see if that fixes the problem on shutdown with WiFi? -- 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 manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1431774/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1431609] Re: systemd session for gnome-shell with Wayland backend
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 manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1431609/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1331891] Re: [systemd] /etc/logrotate.d/rsyslog fails to instruct rsyslog to close & reopen fds
** 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] /etc/logrotate.d/rsyslog fails to instruct rsyslog to close & reopen fds To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1331891/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1331891] Re: [systemd] /etc/logrotate.d/rsyslog fails to reload rsyslog
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. https://bugs.launchpad.net/bugs/1331891 Title: [systemd] /etc/logrotate.d/rsyslog fails to instruct rsyslog to close & reopen fds To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1331891/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1331891] Re: [systemd] /etc/logrotate.d/rsyslog fails to reload rsyslog
2014-07-08 14:25 GMT+02:00 Michael Biebl : > 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 though I don't particularly like this situation. > > A solution that would work with all init systems would be something like > > kill -SIGHUP $(cat /var/run/rsyslogd.pid). > > A systemd-only solution would look like this: > > systemctl kill -s HUP rsyslog.service Maybe shipping a small helper script named rsyslog-rotate in /usr/sbin might be the best solution for this. This script could then do the right thing, depending on the init system. E.g. under systemd it runs $ systemctl kill -s HUP rsyslog.service under upstart it runs $ reload rsyslog and under sysvinit $ start-stop-daemon --stop --signal HUP --quiet --pidfile /var/run/rsyslogd.pid --exec /usr/sbin/rsyslogd -- 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. https://bugs.launchpad.net/bugs/1331891 Title: [systemd] /etc/logrotate.d/rsyslog fails to instruct rsyslog to close & reopen fds To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1331891/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1331891] Re: [systemd] /etc/logrotate.d/rsyslog fails to reload rsyslog
2014-07-08 14:01 GMT+02:00 Dimitri John Ledkov : > 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 rsyslog package does *not* have ExecReload set, at least not anymore. The ExecReload setting was removed upstream because a "reload" means that a daemon rereads its configuration, which it no longer does for rsyslog. Which means, you can't run "systemctl reload rsyslog.service". # systemctl reload rsyslog.service Failed to reload rsyslog.service: Job type reload is not applicable for unit rsyslog.service. The logrotate file for rsyslog in Debian currently uses invoke-rc.d rsyslog rotate 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 though I don't particularly like this situation. A solution that would work with all init systems would be something like kill -SIGHUP $(cat /var/run/rsyslogd.pid). A systemd-only solution would look like this: systemctl kill -s HUP rsyslog.service -- 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. https://bugs.launchpad.net/bugs/1331891 Title: [systemd] /etc/logrotate.d/rsyslog fails to instruct rsyslog to close & reopen fds To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1331891/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1196752] Re: Suspend only works once when using upower with logind -- s-shim needs to call /lib/systemd/system-sleep/*
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 out if they are talking to systemd proper or systemd-shim. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1196752 Title: Suspend only works once when using upower with logind -- s-shim needs to call /lib/systemd/system-sleep/* To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1196752/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 531190]
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 version of the Linux kernel and gnome-power-manager are supposed to have those workarounds? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/531190 Title: upower (devkit-power) reporting bad data when AC cable is unplugged To manage notifications about this bug go to: https://bugs.launchpad.net/devicekit-power/+bug/531190/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 654353] Re: obsolete conffiles not removed on upgrade
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 release, which makes me wonder if this is still an issue for you? > Of course it is. Obsolete conffiles don't magically go away. Cheers, Michael -- 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. https://bugs.launchpad.net/bugs/654353 Title: obsolete conffiles not removed on upgrade -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 688541] Re: race condition on shutdown (leads to corrupted fs)
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 release > Squeeze? > (tough I never observed it on Squeeze till now) This doesn't affect Debian as the upstart package in Debian still uses plain sysv compat and there are no native upstart jobs yet. Michael (upstart maintainer in Debian) -- 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. https://bugs.launchpad.net/bugs/688541 Title: race condition on shutdown (leads to corrupted fs) -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 688541] Re: race condition on shutdown (leads to corrupted fs)
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 like mysql? - How do you decide if a service is '"slow" to stop' ? Imho that highly depends on the given hardware, local configuration and the amount of data you are dealing with. A general approach would be preferable. -- 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. https://bugs.launchpad.net/bugs/688541 Title: race condition on shutdown (leads to corrupted fs) -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 688541] Re: race condition on shutdown (leads to corrupted fs)
2010/12/16 Clint Byrum :
>
> /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 "/process [0-9]/s/.*process
> //p"); do
> OMITPIDS="${OMITPIDS:+$OMITPIDS }-o $pid"
> done
>
>
> It uses this to determine which pids not to kill because, presumably, upstart
> should be managing them.
>
> However, this code is flawed. killall5 will kill the children of all of
> these if they are multi process daemons or scripts running things.
This observation is correct. On the other hand, isn't this exactly
what the sendsigs script is for: clean up any remaining, stray
processes which have not been stopped by its corresponding sysv init
script or upstart job (or have been e.g. started by the user)?
But I guess you are right, we should first stop all upstart jobs, give
them time to finish stopping, and then let sendsigs clean up anything
remaining afterwards.
> However, this technique can actually be used to determine if there are
> still jobs that are supposed to be stopped, but haven't finished
> stopping yet. Since they should be listed as stop/(pre-stop|post-
> stop|killed), we can determine exactly which pids we expect to go away.
> Since upstart has its own idea of how long to wait before it kills
> these, we should actually wait indefinitely.
>
> I'm attaching a debdiff that solves the race as far as I can tell,
> though I think it needs a good long look, since it could mean shutdowns
> hang for a long time waiting (I'm especially curious if the pre-stop
> /post-stop's are subject to kill timeout)
This code is still racy, afaics. What about upstart jobs, which are
not stopped by "stop on runlevel [016]"? They could receive their stop
signal at a point when your loop has already been run.
If you don't want to change existing jobs, we probably have to pick up
Ante's suggestion, and do the following in sendsigs:
1) run a for loop to wait for *all* running upstart jobs to stop.
upstart jobs which need to keep running past sendsigs (e.g. plymouth)
need to signal that using a similar mechanism like the killall5
sendsigs.d omit interface. I'd at least give upstart jobs 60secs time
to stop, so big databases etc have enough time to cleanly shutdown
2.) run a for loop and send SIGTERM all remaining processes, but do
*not* add upstart pids to $OMITPIDS
3.) send a final SIGKILL if any processes are left.
Regarding 1.), it would be nice to have a native C implementation in
upstart, instead of running initctl, grep and sleep manually.
--
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.
https://bugs.launchpad.net/bugs/688541
Title:
race condition on shutdown (leads to corrupted fs)
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 688541] Re: race condition on shutdown (leads to corrupted fs)
2010/12/14 Clint Byrum : > > 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 have "start on runlevel [2345]" and the binary is in /usr? There are quite a few examples here: acpid, atd, cron, irqbalance, etc which all have: start on runlevel [2345] stop on runlevel [!2345] Either those jobs are buggy to not specify the "start on (local-)filesystems" dependency or your criteria is not sufficient. Imho the major problem here is, that there is a mixup between dependencies that need to be satisfied to be able to run a job and when (in which runlevels) to start a job. Michael -- 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. https://bugs.launchpad.net/bugs/688541 Title: race condition on shutdown (leads to corrupted fs) -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 688541] Re: race condition on shutdown (leads to corrupted fs)
2010/12/10 Ante Karamatić :
> 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 they're still running,
# they're supposed to be
for pid in $(initctl list | sed -n -e "/process
[0-9]/s/.*process //p"); do
OMITPIDS="${OMITPIDS:+$OMITPIDS }-o $pid"
done
or
# did an upstart job start since we last polled initctl? check
# again on each loop and add any new jobs (e.g., plymouth) to
# the list. If we did miss one starting up, this beats waiting
# 10 seconds before shutting down.
for pid in $(initctl list | sed -n -e "/process
[0-9]/s/.*process //p"); do
OMITPIDS="${OMITPIDS:+$OMITPIDS }-o $pid"
done
--
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.
https://bugs.launchpad.net/bugs/688541
Title:
race condition on shutdown (leads to corrupted fs)
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 688541] Re: race condition on shutdown (leads to corrupted fs)
-- 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 688541] [NEW] race condition on shutdown (leads to corrupted fs)
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 terminate... [80G [74G[ OK ] * All processes ended within 1 seconds [80G [74G[ OK ] * Deconfiguring network interfaces... [80G [74G[ OK ] * Deactivating swap... [80G [74G[ OK ] * Unmounting local filesystems... [80G umount2: Device or resource busy umount: /var/lib/mysql: device is busy. (In some cases useful info about processes that use the device is found by lsof(8) or fuser(1)) umount2: Device or resource busy umount2: Device or resource busy umount: /tmp: device is busy. (In some cases useful info about processes that use the device is found by lsof(8) or fuser(1)) umount2: Device or resource busy [74G[ [31mfail [39;49m] mount: / is busy * Will now restart [ 3369.429751] Restarting system. On the next reboot the file system is corrupt and need to be fsck-ed. I think the problem is, that mysql uses an upstart job (/etc/init/mysql.conf) and has stop on runlevel [016] The rc.conf job is also triggered on runlevel 0 and 6, so they basically run at the same time.As When /etc/rc0.d/S20sendsigs is run, it deliberatly does not wait or kill any upstart jobs. As my mysqld process takes some time to shutdown, S40umountfs and S60umountroot are run before the mysqld has quit. Leading to the fs not being properly unmounted. It is event possible that mysqld is forcefully killed by halt in S90halt if it hasn't stopped by then. This is a serious issue, as it can (and will) lead to data loss. Other upstart jobs, like rsyslog.conf, use the same "stop on runlevel [016]" stanza, so they are probably affected too. ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: mysql-server-5.1 5.1.49-1ubuntu8.1 Uname: Linux 2.6.32-5-686 i686 NonfreeKernelModules: michael_mic arc4 ecb lib80211_crypt_tkip aes_i586 aes_generic lib80211_crypt_ccmp sco bnep rfcomm l2cap binfmt_misc acpi_cpufreq ppdev lp cpufreq_userspace cpufreq_stats vboxnetadp cpufreq_powersave vboxnetflt cpufreq_conservative vboxdrv fuse pcmcia snd_intel8x0m snd_intel8x0 snd_ac97_codec btusb bluetooth rfkill ac97_bus yenta_socket ipw2200 snd_pcm 8139too firewire_ohci snd_seq 8139cp firewire_core sg uhci_hcd snd_timer rsrc_nonstatic libipw snd_seq_device pcmcia_core crc_itu_t parport_pc smsc_ircc2 ehci_hcd mii joydev lib80211 sr_mod parport i2c_i801 irda snd usbcore wbsd soundcore shpchp mmc_core pcspkr rng_core cdrom psmouse container crc_ccitt snd_page_alloc serio_raw pci_hotplug ac battery nls_base processor evdev ppp_generic slhc loop autofs4 ext4 mbcache jbd2 crc16 dm_mod sd_mod crc_t10dif radeon ttm ata_generic drm_kms_helper ata_piix drm i2c_algo_bit libata video thermal i2c_core scsi_mod output thermal_sys button Architecture: i386 Date: Fri Dec 10 13:41:52 2010 ProcEnviron: PATH=(custom, no user) LANG=de_DE.utf8 SHELL=/bin/bash SourcePackage: mysql-5.1 ** Affects: mysql-5.1 (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 maverick -- 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 654353] Re: obsolete conffiles not removed on upgrade
** 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" https://bugs.launchpad.net/bugs/654353/+attachment/1670421/+files/DRM.card0.SVIDEO.1.txt ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/654353/+attachment/1670422/+files/Dependencies.txt ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/654353/+attachment/1670423/+files/Lspci.txt ** Attachment added: "PciDisplay.txt" https://bugs.launchpad.net/bugs/654353/+attachment/1670424/+files/PciDisplay.txt ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/654353/+attachment/1670425/+files/ProcCpuinfo.txt ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/654353/+attachment/1670426/+files/ProcInterrupts.txt ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/654353/+attachment/1670427/+files/ProcModules.txt ** Attachment added: "RelatedPackageVersions.txt" https://bugs.launchpad.net/bugs/654353/+attachment/1670428/+files/RelatedPackageVersions.txt ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/654353/+attachment/1670429/+files/UdevDb.txt ** Attachment added: "UdevLog.txt" https://bugs.launchpad.net/bugs/654353/+attachment/1670430/+files/UdevLog.txt ** Attachment added: "XorgConf.txt" https://bugs.launchpad.net/bugs/654353/+attachment/1670431/+files/XorgConf.txt ** Attachment added: "XorgLog.txt" https://bugs.launchpad.net/bugs/654353/+attachment/1670432/+files/XorgLog.txt ** Attachment added: "XorgLogOld.txt" https://bugs.launchpad.net/bugs/654353/+attachment/1670433/+files/XorgLogOld.txt ** Attachment added: "Xrandr.txt" https://bugs.launchpad.net/bugs/654353/+attachment/1670434/+files/Xrandr.txt ** Attachment added: "glxinfo.txt" https://bugs.launchpad.net/bugs/654353/+attachment/1670435/+files/glxinfo.txt ** Attachment added: "peripherals.txt" https://bugs.launchpad.net/bugs/654353/+attachment/1670436/+files/peripherals.txt ** Attachment added: "setxkbmap.txt" https://bugs.launchpad.net/bugs/654353/+attachment/1670437/+files/setxkbmap.txt ** Attachment added: "xdpyinfo.txt" https://bugs.launchpad.net/bugs/654353/+attachment/1670438/+files/xdpyinfo.txt ** Attachment added: "xkbcomp.txt" https://bugs.launchpad.net/bugs/654353/+attachment/1670439/+files/xkbcomp.txt -- obsolete conffiles not removed on upgrade https://bugs.launchpad.net/bugs/654353 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 654353] [NEW] obsolete conffiles not removed on upgrade
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 /etc/gdm/failsafe-xorg.conf abf92266f0f22cde1b7c7d82b76a5144 obsolete /etc/gdm/failsafeDexconf.old a71e8ab096da4f7a1c3c623b3055ceda obsolete /etc/gdm/failsafeDexconf aa7fbb287298820abd8cd80d28fb62c6 obsolete # ls -la /etc/gdm/failsafe* -rw-r--r-- 1 root root 132 2007-07-26 02:51 /etc/gdm/failsafeBlacklist -rwxr-xr-x 1 root root 8620 2009-03-17 09:59 /etc/gdm/failsafeDexconf -rwxr-xr-x 1 root root 1698 2007-08-01 22:14 /etc/gdm/failsafeHelpmsg -rwxr-xr-x 1 root root 833 2007-07-26 02:51 /etc/gdm/failsafeInstall -rwxr-xr-x 1 root root 8778 2010-03-01 08:54 /etc/gdm/failsafeXinit -rw-r--r-- 1 root root 1574 2007-08-02 00:31 /etc/gdm/failsafe-xorg.conf -rwxr-xr-x 1 root root 4778 2010-03-03 23:46 /etc/gdm/failsafeXServer ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: x11-common 1:7.5+6ubuntu3 ProcVersionSignature: Ubuntu 2.6.35-22.33-generic 2.6.35.4 Uname: Linux 2.6.35-22-generic i686 Architecture: i386 DRM.card0.LVDS.1: status: connected enabled: enabled dpms: On modes: 1680x1050 1400x1050 1280x1024 1440x900 1280x960 1280x854 1280x800 1280x720 1152x768 1024x768 800x600 848x480 720x480 640x480 edid-base64: DRM.card0.VGA.1: status: disconnected enabled: disabled dpms: On modes: edid-base64: Date: Mon Oct 4 04:48:07 2010 DkmsStatus: virtualbox-ose, 3.2.8, 2.6.35-22-generic, i686: installed Lsusb: Bus 004 Device 002: ID 049f:0086 Compaq Computer Corp. Bluetooth Device Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Hewlett-Packard HP compaq nx7000 (DG706A#ABD) PackageArchitecture: all ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-22-generic root=UUID=7d695993-b56d-4cc6-9e66-ec12035e1cc5 ro quiet splash ProcEnviron: LANGUAGE=de_DE:de PATH=(custom, no user) LANG=de_DE.utf8 SHELL=/bin/bash SourcePackage: xorg dmi.bios.date: 07/14/2005 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68BAL Ver. F.55 dmi.board.name: 0860 dmi.board.vendor: COMPAL dmi.board.version: 8051 Version 24.56 dmi.chassis.type: 10 dmi.chassis.vendor: COMPAL dmi.chassis.version: NULL dmi.modalias: dmi:bvnHewlett-Packard:bvr68BALVer.F.55:bd07/14/2005:svnHewlett-Packard:pnHPcompaqnx7000(DG706A#ABD):pvrF.55:rvnCOMPAL:rn0860:rvr8051Version24.56:cvnCOMPAL:ct10:cvrNULL: dmi.product.name: HP compaq nx7000 (DG706A#ABD) dmi.product.version: F.55 dmi.sys.vendor: Hewlett-Packard system: distro: Ubuntu codename: maverick architecture: i686 kernel: 2.6.35-22-generic ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 maverick -- obsolete conffiles not removed on upgrade https://bugs.launchpad.net/bugs/654353 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 606706] Re: Regression: HD spins down all the time after upgrade of pm-utils
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 on mains power. Could you send the output of on_ac_power && echo yes || echo no when on ac and battery? -- Regression: HD spins down all the time after upgrade of pm-utils https://bugs.launchpad.net/bugs/606706 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 515306] Re: New dep on libnunit2.4-cil pulls 10Mb of dependencies
** 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 Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 515306] [NEW] New dep on libnunit2.4-cil pulls 10Mb of dependencies
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 00:09:46 2010 DistroRelease: Ubuntu 10.04 Package: tomboy 1.1.0-0ubuntu5 ProcEnviron: LANGUAGE=de_DE.UTF-8 PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.32-12.16-generic SourcePackage: tomboy Uname: Linux 2.6.32-12-generic i686 ** Affects: tomboy (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 lucid -- 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 Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 506793] Re: /etc/udev/rules.d/56-hpmud_support.rules not migrated/removed on upgrades
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 "obsolete", that's why the md5sum comparison fails and the file is
not removed.
The wiki has appropriate code, that strips "obsolete" and spaces.
--
/etc/udev/rules.d/56-hpmud_support.rules not migrated/removed on upgrades
https://bugs.launchpad.net/bugs/506793
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
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 506793] Re: /etc/udev/rules.d/56-hpmud_support.rules not migrated/removed on upgrades
** 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 ** Attachment added: "Locale.txt" http://launchpadlibrarian.net/37837053/Locale.txt ** Attachment added: "Lspci.txt" http://launchpadlibrarian.net/37837054/Lspci.txt ** Attachment added: "PrintingPackages.txt" http://launchpadlibrarian.net/37837055/PrintingPackages.txt ** Attachment added: "ProcCpuinfo.txt" http://launchpadlibrarian.net/37837056/ProcCpuinfo.txt ** Attachment added: "ProcInterrupts.txt" http://launchpadlibrarian.net/37837057/ProcInterrupts.txt ** Attachment added: "ProcModules.txt" http://launchpadlibrarian.net/37837058/ProcModules.txt ** Attachment added: "UdevDb.txt" http://launchpadlibrarian.net/37837059/UdevDb.txt ** Attachment added: "UdevLog.txt" http://launchpadlibrarian.net/37837060/UdevLog.txt -- /etc/udev/rules.d/56-hpmud_support.rules not migrated/removed on upgrades https://bugs.launchpad.net/bugs/506793 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 506793] [NEW] /etc/udev/rules.d/56-hpmud_support.rules not migrated/removed on upgrades
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, as you can see here: # md5sum /etc/udev/rules.d/56-hpmud_support.rules abcdc51b238c2fe70f973bee434c912e /etc/udev/rules.d/56-hpmud_support.rules # grep 56-hpmud_support.rules /var/lib/dpkg/status /etc/udev/rules.d/56-hpmud_support.rules abcdc51b238c2fe70f973bee434c912e obsolete ProblemType: Bug Architecture: i386 CupsErrorLog: Date: Wed Jan 13 05:42:36 2010 DistroRelease: Ubuntu 10.04 Lpstat: device for DeskJet-940C: usb://HP/DeskJet%20940C?serial=HU2256N253BH device for MP610-series: usb://Canon/MP610%20series device for PDF: cups-pdf:/ Lsusb: Bus 004 Device 002: ID 049f:0086 Compaq Computer Corp. Bluetooth Device Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Hewlett-Packard HP compaq nx7000 (DG706A#ABD) Package: hplip 3.9.12-2ubuntu3 Papersize: a4 PpdFiles: MP610-series: Canon MP610 series Ver.2.80 DeskJet-940C: HP Deskjet 940c, hpcups 3.9.12 PDF: Generic PDF file generator ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-10-generic root=UUID=7d695993-b56d-4cc6-9e66-ec12035e1cc5 ro quiet ProcEnviron: LANGUAGE=de_DE.UTF-8 PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.32-10.14-generic SourcePackage: hplip Tags: lucid Uname: Linux 2.6.32-10-generic i686 dmi.bios.date: 07/14/2005 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68BAL Ver. F.55 dmi.board.name: 0860 dmi.board.vendor: COMPAL dmi.board.version: 8051 Version 24.56 dmi.chassis.type: 10 dmi.chassis.vendor: COMPAL dmi.chassis.version: NULL dmi.modalias: dmi:bvnHewlett-Packard:bvr68BALVer.F.55:bd07/14/2005:svnHewlett-Packard:pnHPcompaqnx7000(DG706A#ABD):pvrF.55:rvnCOMPAL:rn0860:rvr8051Version24.56:cvnCOMPAL:ct10:cvrNULL: dmi.product.name: HP compaq nx7000 (DG706A#ABD) dmi.product.version: F.55 dmi.sys.vendor: Hewlett-Packard ** Affects: hplip (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 lucid -- /etc/udev/rules.d/56-hpmud_support.rules not migrated/removed on upgrades https://bugs.launchpad.net/bugs/506793 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 506791] Re: /etc/udev/rules.d/65-libmtp.rules not migrated/removed on upgrades
** 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 subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 506791] [NEW] /etc/udev/rules.d/65-libmtp.rules not migrated/removed on upgrades
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 not properly migrated/removed when
upgrading from previous versions of libmtp.
As this old file contains a lot of deprecated udev rules, I get a lot of
those warning during boot:
Jan 13 05:25:29 pluto udevd[591]: SYSFS{}= will be removed in a future
udev version, please use ATTR{}= to match the event device, or ATTRS{}=
to match a parent device, in /etc/udev/rules.d/65-libmtp.rules:65
ProblemType: Bug
Architecture: i386
Date: Wed Jan 13 05:34:37 2010
DistroRelease: Ubuntu 10.04
Package: libmtp8 1.0.1-0ubuntu1
ProcEnviron:
LANGUAGE=de_DE.UTF-8
PATH=(custom, no user)
LANG=de_DE.UTF-8
SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-10.14-generic
SourcePackage: libmtp
Tags: lucid
Uname: Linux 2.6.32-10-generic i686
** Affects: libmtp (Ubuntu)
Importance: Undecided
Status: New
** Tags: apport-bug i386 lucid
--
/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 subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 434852] Re: bluetoothd does not die on SIGTERM
** 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. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 434852] [NEW] bluetoothd does not die on SIGTERM
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 ?Shttps://bugs.launchpad.net/bugs/434852 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 434767] Re: obsolete init script hwclock.sh after upstart migration
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 of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 434767] Re: obsolete init script hwclock.sh after upstart migration
** 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 Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 434767] [NEW] obsolete init script hwclock.sh after upstart migration
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 2e480c2fbb71772346116db514831114 obsolete ProblemType: Bug Architecture: i386 Date: Tue Sep 22 19:12:56 2009 DistroRelease: Ubuntu 9.10 Package: util-linux 2.16-1ubuntu3 ProcEnviron: LANGUAGE=de_DE.UTF-8 PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-10.34-generic SourcePackage: util-linux Uname: Linux 2.6.31-10-generic i686 ** Affects: util-linux (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 -- 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 Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 388608] Re: Don't run as root
** 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 https://bugs.launchpad.net/bugs/388608 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 388623] Re: Don't fail if dbus is not running
** 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 you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 388623] [NEW] Don't fail if dbus is not running
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 E: Problem executing scripts APT::Update::Post-Invoke-Success '/usr/bin/dbus-send --system --dest=org.freedesktop.PackageKit --type=method_call /org/freedesktop/PackageKit org.freedesktop.PackageKit.StateHasChanged string:'cache-update'' E: Sub-process returned an error code A simple fix is, to check if dbus is running in /etc/apt/apt.conf.d/20packagekit, before doing the dbus call Trivial patch is attached ** Affects: packagekit (Ubuntu) Importance: Undecided Status: New -- Don't fail if dbus is not running https://bugs.launchpad.net/bugs/388623 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 346912] Re: Tracker does not stop indexing
2009/4/6 Martyn Russell : > 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 index a word. We are not > entirely sure why this happens and a reindex is the only way to fix it. > If it keeps happening, we would like to know if it is ONE file which > causes this or something else? This should be resolved once we move to > SQLite FTS (i.e. remove QDBM). That won't be until 0.7.x though. > I indeed forgot to include tracker-processes in the Debian package. I've split the command line utilities into a separate, optional tracker-utils package. It currently contains /usr/bin/tracker-stats /usr/bin/tracker-search /usr/bin/tracker-tag /usr/bin/tracker-meta-folder /usr/bin/tracker-services /usr/bin/tracker-info /usr/bin/tracker-status /usr/bin/tracker-files /usr/bin/tracker-unique /usr/bin/tracker-query ie, binaries that are not strictly required if you are using graphical frontends. Martyn, I guess this new binary should be added to the binary package tracker though, as trackerd relies on it, right? Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? -- Tracker does not stop indexing https://bugs.launchpad.net/bugs/346912 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 353480] Re: Please merge tracker 0.6.92-1 (main) from Debian unstable
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 plugin be deactivated automatically? >From what I can see in configure.ac, there is Evolution extracter (data-pull):yes (old)(thus always on???) and in src/tracker-indexer/Makefile.am, libtracker-module-evolution.la is built unconditionally, thus always installed. That's confusing me a bit Cheers, Michael -- Forwarded message -- From: Chris Coulson Date: 2009/4/1 Subject: [Bug 353480] Re: Please merge tracker 0.6.92-1 (main) from Debian unstable To: mbi...@gmail.com And here is the diff to the current version in Ubuntu ** Attachment added: "tracker_0.6.92-1ubuntu1 Ubuntu diff.patch" http://launchpadlibrarian.net/24650747/tracker_0.6.92-1ubuntu1%20Ubuntu%20diff.patch -- Please merge tracker 0.6.92-1 (main) from Debian unstable https://bugs.launchpad.net/bugs/353480 You received this bug notification because you are subscribed to tracker in ubuntu. -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? -- Please merge tracker 0.6.92-1 (main) from Debian unstable https://bugs.launchpad.net/bugs/353480 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 329201] Re: Please merge tracker 0.6.90-1 (main) from Debian experimental
2009/2/17 Daniel Holbach : > 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 anywhere > dh_install: usr/share/man/man1/tracker-files.1 exists in debian/tmp but is > not installed to anywhere > dh_install: usr/share/man/man1/tracker-applet.1 exists in debian/tmp but is > not installed to anywhere > dh_install: usr/share/man/man1/tracker-query.1 exists in debian/tmp but is > not installed to anywhere > dh_install: usr/share/man/man1/tracker-status.1 exists in debian/tmp but is > not installed to anywhere > dh_install: usr/share/man/man1/tracker-tag.1 exists in debian/tmp but is not > installed to anywhere > dh_install: usr/share/man/man1/tracker-meta-folder.1 exists in debian/tmp but > is not installed to anywhere > dh_install: usr/share/man/man1/trackerd.1 exists in debian/tmp but is not > installed to anywhere > dh_install: usr/share/man/man1/tracker-thumbnailer.1 exists in debian/tmp but > is not installed to anywhere > dh_install: usr/share/man/man1/tracker-search-tool.1 exists in debian/tmp but > is not installed to anywhere > dh_install: usr/share/man/man1/tracker-unique.1 exists in debian/tmp but is > not installed to anywhere > dh_install: usr/share/man/man1/tracker-search.1 exists in debian/tmp but is > not installed to anywhere > dh_install: usr/share/man/man1/tracker-extract.1 exists in debian/tmp but is > not installed to anywhere > dh_install: usr/share/man/man1/tracker-info.1 exists in debian/tmp but is not > installed to anywhere > dh_install: usr/share/man/man1/tracker-stats.1 exists in debian/tmp but is > not installed to anywhere > dh_install: usr/share/man/man1/tracker-preferences.1 exists in debian/tmp but > is not installed to anywhere > > What do you think? They are installed. list-missing doesn't pick them up because they are gzipped. Cheers, Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? -- Please merge tracker 0.6.90-1 (main) from Debian experimental https://bugs.launchpad.net/bugs/329201 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 329201] Re: Please update tracker search system in Ubuntu 9.04
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, Michael 2009/2/13 Chris Coulson : > Thank you for your bug report. That probably won't happen for 9.04 > though - feature freeze is only a few days away and the Tracker update > has some big changes, which also need some packaging changes too (it > ships extra shared libraries which should go in to new binary packages > etc), a lot of files moved around/changed name etc which messes up the > packaging too. I attempted to package a recent SVN build (in my PPA), > but it still requires more work > > ** Changed in: tracker (Ubuntu) > Importance: Undecided => Wishlist > Status: New => Confirmed > > ** Tags added: update > > -- > Please update tracker search system in Ubuntu 9.04 > https://bugs.launchpad.net/bugs/329201 > You received this bug notification because you are subscribed to tracker > in ubuntu. > -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? -- Please update tracker search system in Ubuntu 9.04 https://bugs.launchpad.net/bugs/329201 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 283416] Re: one should have /etc/init.d/network-manager status option as well
2009/1/29 Alexander Sack : > 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 (NetworkManager vs. network-manager). Would you mind merging the Debian 0.7.0 packages? I think they have some nice improvements (general cruft removal from debian/, symbols files, updated to newer Debian policy (e.g. Homepage field and stuff). Cheers, Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? -- one should have /etc/init.d/network-manager status option as well https://bugs.launchpad.net/bugs/283416 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 117307] Re: Tracker doesn't index openoffice.org files
2008/11/9 Steve Jackson <[EMAIL PROTECTED]>: > o3read is not in Intrepid's repos. Perhaps Tracker filters need to call > odt2txt instead, but this is not installed by default. Copying o3totxt > from Hardy seems to work as a stopgap. > You might want to sync tracker 0.6.6-2 from Debian, where I have already fixed that. The changelog is: tracker (0.6.6-2) unstable; urgency=low * debian/control - Add Build-Depends on pkg-config. - Add Vcs-* fields. - Replace Recommends on o3read with odt2txt. * debian/patches/01-secure_tmpdir.patch - Use mktemp to create a secure tmpdir for the msword filter. Thanks to Jon Dowland for the patch. Closes: #473733 * Add symbols files for libtrackerclient0 and libtracker-gtk0. * debian/patches/02-static_keywords_reply.patch - Make _keywords_reply a static function to not export it in the public API. * debian/patches/03-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 doesn't index openoffice.org files https://bugs.launchpad.net/bugs/117307 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 225611] Re: tracker inconsistecies with .tex files
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 pointed away from Earth? -- tracker inconsistecies with .tex files https://bugs.launchpad.net/bugs/225611 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 81474] Re: usplash: blank screen. does not switch to gdm / kdm
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 in the universe are pointed away from Earth? -- usplash: blank screen. does not switch to gdm / kdm https://bugs.launchpad.net/bugs/81474 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 93360] Re: Dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth1 for sub-path eth1.dbus.get.reason
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 /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.reason > Feb 14 16:31:47 mikkojakaisa dhcdbd: message_handler: message handler not > found under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.host_name > Feb 14 16:31:47 mikkojakaisa dhcdbd: message_handler: message handler not > found under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.nis_domain > Feb 14 16:31:47 mikkojakaisa dhcdbd: message_handler: message handler not > found under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.nis_servers These log messages are only cosmetic. Nothing to worry about. -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? -- Dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth1 for sub-path eth1.dbus.get.reason https://bugs.launchpad.net/bugs/93360 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 191810] [NEW] obsolete conffiles are not removed on upgrade
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: Alexander Sack <[EMAIL PROTECTED]> Architecture: all Source: firefox-3.0 Version: 3.0~b3+nobinonly-0ubuntu1 Depends: firefox-3.0 Conffiles: /etc/gre.d/firefox.conf b4373d803382b2e14e405874ff50f664 obsolete /etc/mozilla-firefox/mozilla-firefoxrc fa562ca63014f5e9dd470a37766376d6 obsolete /etc/mozilla-firefox/pref/firefox.js 9b21e21aa3f8a0ab8f134ba04b8846ff obsolete /etc/mozilla-firefox/profile/bookmarks.html 44e419e6fc9b2a2a954b73708d5223cc obsolete /etc/mozilla-firefox/profile/localstore.rdf ea03cc19c2a3f622fa557cd8ea9da6eb obsolete /etc/mozilla-firefox/profile/search.rdf 26d13f5d96ad118b5de5d234f9d052fa obsolete /etc/mozilla-firefox/profile/mimeTypes.rdf 69cdcb7e0209f2e9d29000ee1c0ee2f0 obsolete /etc/mozilla-firefox/profile/chrome/userChrome-example.css 4788fdaa51b0a238cb21f5c2877ef06d obsolete /etc/mozilla-firefox/profile/chrome/userContent-example.css d3765c7d2de5626529195007f4b7144a obsolete /etc/mozilla-firefox/profile/extensions/Extensions.rdf 4e5887ce2461b9874016a170750c05e1 obsolete /etc/mozilla-firefox/profile/prefs.js 99940ecd258d83b3355ab06fca0ffddb obsolete /etc/firefox/pref/firefox.js fdab5286f88abaccc3a6fa04ab12ef13 obsolete /etc/firefox/firefoxrc e4a7a18bcd5d3a8946ceb797967c4245 obsolete /etc/firefox/profile/prefs.js 99940ecd258d83b3355ab06fca0ffddb obsolete /etc/firefox/profile/chrome/userContent-example.css d3765c7d2de5626529195007f4b7144a obsolete /etc/firefox/profile/chrome/userChrome-example.css 4788fdaa51b0a238cb21f5c2877ef06d obsolete /etc/firefox/profile/mimeTypes.rdf 69cdcb7e0209f2e9d29000ee1c0ee2f0 obsolete /etc/firefox/profile/search.rdf 939dcfba9fa92f86bcacb487df9dede1 obsolete /etc/firefox/profile/localstore.rdf ea03cc19c2a3f622fa557cd8ea9da6eb obsolete /etc/firefox/profile/bookmarks.html ed5cb20b2c5f3e90c524a6c62b6f467e obsolete The obsolete conffiles should be removed/transitioned to the new location. See http://wiki.debian.org/DpkgConffileHandling ** Affects: firefox (Ubuntu) Importance: Undecided Status: New -- obsolete conffiles are not removed on upgrade https://bugs.launchpad.net/bugs/191810 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 148895] Re: No icon in menu
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" in SVN, as proposed by the fd.o icon naming spec. Any compliant desktop environment (Gnome, KDE4 ttbomk) should then correctly display the menu icon. -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? -- No icon in menu https://bugs.launchpad.net/bugs/148895 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 177524] Re: Tracker has a strange behaviour with word "just"
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 something else. show a warning message in t-s-t if the search term is a stop word? -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? -- Tracker has a strange behaviour with word "just" https://bugs.launchpad.net/bugs/177524 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 177027] (no subject)
2007/12/21, Emilio Pozuelo Monfort <[EMAIL PROTECTED]>: > Emilio Pozuelo Monfort wrote: > > I'll try with Compiz and with the new metacity to see if this is fixed. > > Ok, I've tried compiz and it solves these issues. > However, metacity 2.21.5 didn't. > > Michael, are you running compiz, or some kind of desktop effects, or a > different > window manager? > metacity 2.20.1 Cheers, Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? -- notification icon window has no obvious way to close https://bugs.launchpad.net/bugs/177027 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 176892] Re: Select the search box when the tray icon is clicked
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 I then start typing foo is automatically overwritten. Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? -- Select the search box when the tray icon is clicked https://bugs.launchpad.net/bugs/176892 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 177027] Re: notification icon window has no obvious way to close
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 like a menu) does. > FWIW, if I click (on the desktop, another window etc.) the search popup menu goes away automatically. Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? -- notification icon window has no obvious way to close https://bugs.launchpad.net/bugs/177027 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 177027] notification icon window has no obvious way to close
2007/12/17, Dean Sas <[EMAIL PROTECTED]>: > Public bug reported: > > Binary package hint: tracker > > The window that appears when clicking on the tracker notification icon > does not have any obvious way to dismiss it. > > It has no window decoration and no close button. Perhaps it would be a > tiny bit more obvious if it popped up directly under the notification > icon, rather than the top left side of the screen and the two were > visually associated. > Clicking on the icon shows the dialog, clicking on the icon again dismisses it. Btw, the popup dialog is shown directly under the notification icon here. Looks like a Ubuntu specific problem. -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? -- notification icon window has no obvious way to close https://bugs.launchpad.net/bugs/177027 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 176892] Select the search box when the tray icon is clicked
2007/12/17, Emilio Pozuelo Monfort <[EMAIL PROTECTED]>: > > Both of that works for me. > > When I click the tray icon, the text entry field is selected and after > > pressing enter the pop up dialog disappears and t-s-t starts. > > And none works for me. I added some patches but I don't think any of them > affects the applet. Also, I had to remove a couple of build-deps > (libunac1-dev, > libqdbm-dev) but they shouldn't affect either. > > libgtk is the same as in Debian, 2.12.3-2. Any idea on why this is working for > you (I guess you are in Debian) and not in Ubuntu? Yes I'm on Debian sid. gtk version is indeed the same 2.12.3-2. -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? -- Select the search box when the tray icon is clicked https://bugs.launchpad.net/bugs/176892 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 176892] Select the search box when the tray icon is clicked
2007/12/17, David Prieto <[EMAIL PROTECTED]>: > Public bug reported: > > Binary package hint: tracker > > I have been using the Tracker tray icon for a couple of days and many > times I click it and start writing the search terms right away. I think > that the search box should appear selected when you click the icon, and > previous searches highlighted, to make searching handier. > > It would also be convenient to have the box disappear when you perform a > search, e.g. when you enter a search term and hit intro. Both of that works for me. When I click the tray icon, the text entry field is selected and after pressing enter the pop up dialog disappears and t-s-t starts. -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? -- Select the search box when the tray icon is clicked https://bugs.launchpad.net/bugs/176892 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 153319] Re: trackerd always use 100% CPU
2007/11/24, Emmet Caulfield <[EMAIL PROTECTED]>: > Jamie, > > It would simply never occur to me to mount something in a user's home > directory. I therefore misunderstood "index mounted filesystems" to mean > "index mounted filesystems" ;o) > The wording in tracker-preferences is indeed a bit unclear about that point. Do you have a good suggestion how this setting could be named in t-p (best with less than 4-6 words) Cheers, Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? -- trackerd always use 100% CPU https://bugs.launchpad.net/bugs/153319 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
