Bug#973701: network-manager: systemctl restart ModemManager.service wipes /etc/resolve.conf (almost) clean
On Sun, 22 Nov 2020, Matteo F. Vescovi wrote: > On 2020-11-04 at 21:09 (+01), Cristian Ionescu-Idbohrn wrote: > > [...] > > > IMO, my remarks and comments are all _but_ snide and stupid. The > > problem here, as I see it, is this maintainer's _arrogant_ attitude. > > Michael, sorry to say, but Cristian is right: > > I see no snide and stupid comments to the bug report and I'm > actually affected by this weird behaviour since a week or so, I must > admit. Yes, I'm not alone. I noticed this odd behaviour months ago but did not report it, as I expected that kind of _arrogant_ reaction. > I'm still digging in to find the culprit (possibly, a particular > version of NM or MM that introduced the issue) For me, it does not appear ModemManager has anything to do with this, but I can't rule that out. > but I need some more tests with alternative setups to fully > understand the situation (seems like systems with both Wi-Fi and > WWAN are affected). I can reproduce this in another way too. My laptop has both a wifi and a wired chip. When I stick in the cable, the same problem occurs: I loose the DNS configuration in /etc/resolv.conf. I can add that manually, but that should _not_ be expected. Another peculiar behaviour is that if I poweroff connected to the wifi and startup wired connected, I end up having to disconnect the cable and connect it back again to be able to get things (sort of) working again. In both cases (wired/wireless) I rely on the router's DHCP to provide the proper DNS configuration. That may need another bug report, if anyone else is able to reproduce. Cheers, -- Cristian
Bug#973701: network-manager: systemctl restart ModemManager.service wipes /etc/resolve.conf (almost) clean
On Tue, 3 Nov 2020, Michael Biebl wrote: > Am 03.11.2020 um 22:58 schrieb Cristian Ionescu-Idbohrn: > > On Tue, 3 Nov 2020, Michael Biebl wrote: > > > > > > This bug report doesn't contain any relevant information to be > > > useful > > > > Bisides the expected comment, what "relevant information" would I > > need to provide to make this bug report useful? I'd be more than > > happy to provide it. > > Anything which would make this bug report more more useful. Leave > out any snide remarks and stupid comments if you can. One more thing. "snide remarks and stupid comments"? What kind of comments are tolerated in these bug reports or on the mailinglists? In this particular case, I find out that rebooting makes my networkmanager problems go away, but restarting the service _breaks_ the OS. IMO, my remarks and comments are all _but_ snide and stupid. The problem here, as I see it, is this maintainer's _arrogant_ attitude. Period. I'd like to see the leader's comment this, but I doubt he will. -- Cristian
Bug#973701: network-manager: systemctl restart ModemManager.service wipes /etc/resolve.conf (almost) clean
On Wed, 4 Nov 2020, Michael Biebl wrote: > > Is NM the sole application touching /etc/resolv.conf? > No other application adding entries to /etc/resolv.conf which NM > doesn't know about? I don't know. Is there a way to find out? The mark in /etc/resolv.conf: # Generated by NetworkManager clearly points to NetworkManager. Is: dbus-daemon[1092]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.resolve1.service': Unit dbus-org.freedesktop.resolve1.service not found. expected behaviour? -- Cristian
Bug#973701: network-manager: systemctl restart ModemManager.service wipes /etc/resolve.conf (almost) clean
On Tue, 3 Nov 2020, Michael Biebl wrote: > > Anything which would make this bug report more more useful. Leave > out any snide remarks and stupid comments if you can. Alright, one stupid thing is the subject line. Should be: # systemctl restart NetworkManager.service instead (cut/paste error). That empties the contents of: /etc/resolv.conf -> /run/NetworkManager/resolv.conf I can reliably reproduce that. More info: This is a laptop and I'm using its wireless network interface, configured to use dhcp to get the parameters from my home router. The primary dns is the router itself, 192.168.0.1. Besides, I locally configured an additional (secondary) dns 9.9.9.9. `nmcli' confirms that: # nmcli ... DNS configuration: servers: 192.168.0.1 9.9.9.9 interface: wlo1 Still, /etc/resolv.conf is emptied after a service restart. Looking at the journal, I see: Nov 04 09:47:04 debian NetworkManager[2085]: [1604479624.4987] dhcp4 (wlo1): option dhcp_lease_time => '4294967295' --> Nov 04 09:47:04 debian NetworkManager[2085]: [1604479624.4987] dhcp4 (wlo1): option domain_name_servers => '192.168.0.1 192.168.0.1' Nov 04 09:47:04 debian NetworkManager[2085]: [1604479624.4988] dhcp4 (wlo1): option host_name=> 'debian' Nov 04 09:47:04 debian NetworkManager[2085]: [1604479624.4988] dhcp4 (wlo1): option ip_address => '192.168.0.2' Nov 04 09:47:04 debian NetworkManager[2085]: [1604479624.4988] dhcp4 (wlo1): option next_server => '192.168.0.1' Nov 04 09:47:04 debian NetworkManager[2085]: [1604479624.4989] dhcp4 (wlo1): option requested_broadcast_address => '1' Nov 04 09:47:04 debian NetworkManager[2085]: [1604479624.4989] dhcp4 (wlo1): option requested_domain_name => '1' Nov 04 09:47:04 debian NetworkManager[2085]: [1604479624.4989] dhcp4 (wlo1): option requested_domain_name_servers => '1' Nov 04 09:47:04 debian NetworkManager[2085]: [1604479624.4989] dhcp4 (wlo1): option requested_domain_search => '1' Nov 04 09:47:04 debian NetworkManager[2085]: [1604479624.4990] dhcp4 (wlo1): option requested_host_name => '1' Nov 04 09:47:04 debian NetworkManager[2085]: [1604479624.4990] dhcp4 (wlo1): option requested_interface_mtu => '1' Nov 04 09:47:04 debian NetworkManager[2085]: [1604479624.4990] dhcp4 (wlo1): option requested_ms_classless_static_routes => '1' Nov 04 09:47:04 debian NetworkManager[2085]: [1604479624.4991] dhcp4 (wlo1): option requested_nis_domain => '1' Nov 04 09:47:04 debian NetworkManager[2085]: [1604479624.4991] dhcp4 (wlo1): option requested_nis_servers => '1' Nov 04 09:47:04 debian NetworkManager[2085]: [1604479624.4991] dhcp4 (wlo1): option requested_ntp_servers => '1' Nov 04 09:47:04 debian NetworkManager[2085]: [1604479624.4991] dhcp4 (wlo1): option requested_rfc3442_classless_static_routes => '1' Nov 04 09:47:04 debian NetworkManager[2085]: [1604479624.4992] dhcp4 (wlo1): option requested_root_path => '1' Nov 04 09:47:04 debian NetworkManager[2085]: [1604479624.4992] dhcp4 (wlo1): option requested_routers=> '1' Nov 04 09:47:04 debian NetworkManager[2085]: [1604479624.4992] dhcp4 (wlo1): option requested_static_routes => '1' Nov 04 09:47:04 debian NetworkManager[2085]: [1604479624.4992] dhcp4 (wlo1): option requested_subnet_mask => '1' Nov 04 09:47:04 debian NetworkManager[2085]: [1604479624.4993] dhcp4 (wlo1): option requested_time_offset => '1' Nov 04 09:47:04 debian NetworkManager[2085]: [1604479624.4993] dhcp4 (wlo1): option requested_wpad => '1' Nov 04 09:47:04 debian NetworkManager[2085]: [1604479624.4993] dhcp4 (wlo1): option routers => '192.168.0.1' Nov 04 09:47:04 debian NetworkManager[2085]: [1604479624.4993] dhcp4 (wlo1): option subnet_mask => '255.255.255.0' Nov 04 09:47:04 debian NetworkManager[2085]: [1604479624.4994] dhcp4 (wlo1): state changed unknown -> bound Nov 04 09:47:04 debian NetworkManager[2085]: [1604479624.5042] device (wlo1): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed') Nov 04 09:47:04 debian NetworkManager[2085]: [1604479624.5101] device (wlo1): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed') Nov 04 09:47:04 debian NetworkManager[2085]: [1604479624.5111] device (wlo1): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed') Nov 04 09:47:04 debian NetworkManager[2085]: [1604479624.5129] manager: NetworkManager state is now CONNECTED_LOCAL Nov 04 09:47:04 debian NetworkManager[2085]: [1604479624.5207] manager: NetworkManager state is now CONNECTED_SITE Nov 04 09:47:04 debian NetworkManager[2085]: [1604479624.52
Bug#973701: [Pkg-utopia-maintainers] Bug#973701: network-manager: systemctl restart ModemManager.service wipes /etc/resolve.conf (almost) clean
On Tue, 3 Nov 2020, Michael Biebl wrote: > > This bug report doesn't contain any relevant information to be useful Bisides the expected comment, what "relevant information" would I need to provide to make this bug report useful? I'd be more than happy to provide it. -- Cristian
Bug#973701: network-manager: 'systemctl restart ModemManager.service' wipes /etc/resolve.conf (almost) clean
Package: network-manager Version: 1.27.91-1 Severity: grave /etc/resolve.conf includes the expected configuration (WRT nameservers) on bootup. After upgrading network-manager and restarting it, /etc/resolve.conf (which is a symlink to /run/NetworkManager/resolv.conf) is basically wiped out. Includes only this: # Generated by NetworkManager Rebooting brings things to normal. Still, this isn't wintendo. I'd expect better. There are some workarounds (suggested in some other bug reports) that bring the system back to an usable state, but far away from perfect (dhclient wlan0). Duplicated home router nameserver addresses in /etc/resolv.conf: nameserver 192.168.0.1 nameserver 192.168.0.1 which is not what my configuration is. -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (500, 'testing'), (99, 'unstable'), (59, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.9.0-1-amd64 (SMP w/4 CPU threads) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages network-manager depends on: ii adduser 3.118 ii dbus 1.12.20-1 ii libaudit11:2.8.5-3.1 ii libbluetooth35.55-1 ii libc62.31-4 ii libcurl3-gnutls 7.72.0-1 ii libglib2.0-0 2.66.1-2 ii libgnutls30 3.6.15-4 ii libjansson4 2.13.1-1 ii libmm-glib0 1.14.6-0.1 ii libndp0 1.6-1+b1 ii libnewt0.52 0.52.21-4+b2 ii libnm0 1.27.91-1 ii libpam-systemd 246.6-2 ii libpsl5 0.21.0-1.1 ii libreadline8 8.0-4 ii libselinux1 3.1-2+b1 ii libsystemd0 246.6-2 ii libteamdctl0 1.31-1 ii libudev1 246.6-2 ii libuuid1 2.36-3+b2 ii policykit-1 0.105-29 ii udev 246.6-2 ii wpasupplicant2:2.9.0-15 Versions of packages network-manager recommends: ii crda 4.14+git20191112.9856751-1 ii dnsmasq-base [dnsmasq-base] 2.82-1 ii iptables 1.8.5-3 ii modemmanager 1.14.6-0.1 pn ppp Versions of packages network-manager suggests: ii isc-dhcp-client 4.4.1-2.1+b2 pn libteam-utils -- no debconf information Cheers, -- Cristian
Bug#940034: libpam-systemd: Please relax Depends: systemd-sysv (was: Bug#940034: libelogind0: replacing a core system library and conflicting against the default init considered harmful)
On Sun, 29 Sep 2019, Mark Hindley wrote: > On Sat, Sep 28, 2019 at 11:41:56AM +0200, Thorsten Glaser wrote: > > On Sat, 28 Sep 2019, Cristian Ionescu-Idbohrn wrote: > > > > > 1. install sysvinit-core; that removes systemd-sysv but nothing else > > >systemd related > > > > > Souldn't that work? > > > > It would, if but for libpam-systemd having a (somewhat questionable > > but understandable) dependency on systemd-sysv. This is basically > > what spawned this thread. > > > > So we'll not be going there. > > Thorsten is quite right. > > There is already a separate bug concerning the libpam-systemd > systemd-sysv dependency. See https://bugs.debian.org/935304. That > would be a more appropriate place for you to add any comments you > may have regarding this aspect of the behaviour you have observed. Following Mark's advice, here are my findings: On Sun, 29 Sep 2019, Cristian Ionescu-Idbohrn wrote: > > Right. I see now what happens on my systems. I have an older > version of systemd packages installed: > > , > | Version: 238-5 > ` > > which depends on: > > , > | systemd-shim (>= 10-3~) | systemd-sysv > ` > > as I stopped systemd related package updates: > > , [ /etc/apt/preferences.d/no-systemd ] > | Package: systemd systemd-sysv systemd-sysv:i386 libsystemd0 libpam-systemd > | Pin: release o=Debian > | Pin-Priority: -1 > ` > > at the point when systemd-shim was removed. Does it mean that, in my case, the transition to elogind would be easier? Cheers, -- Cristian
Bug#940034: libelogind0: replacing a core system library and conflicting against the default init considered harmful
On Sat, 28 Sep 2019, Thorsten Glaser wrote: > On Sat, 28 Sep 2019, Cristian Ionescu-Idbohrn wrote: > > > 1. install sysvinit-core; that removes systemd-sysv but nothing else > >systemd related > > > Souldn't that work? > > It would, if but for libpam-systemd having a (somewhat questionable > but understandable) dependency on systemd-sysv. This is basically > what spawned this thread. > > So we'll not be going there. Right. I see now what happens on my systems. I have an older version of systemd packages installed: , | Version: 238-5 ` which depends on: , | systemd-shim (>= 10-3~) | systemd-sysv ` as I stopped systemd related package updates: , [ /etc/apt/preferences.d/no-systemd ] | Package: systemd systemd-sysv systemd-sysv:i386 libsystemd0 libpam-systemd | Pin: release o=Debian | Pin-Priority: -1 ` at the point when systemd-shim was removed. Cheers, -- Cristian
Bug#940034: libelogind0: replacing a core system library and conflicting against the default init considered harmful
Mark, On Fri, 27 Sep 2019, Mark Hindley wrote: > > Thanks. The aim of preventing accidental removal of systemd is very > reasonable. However, using this approach the hurdle you create even > to a user who really wants to uninstall is pretty high. Few people > will continue having seen the 'You are about to do something > potentially harmful' warning. > > I think the effect we are after is rather closer to that of apt-mark > hold systemd or dpkg --set-selections systemd hold. Once held, > uninstalling the package requires a specific request to apt. But I > realise this approach will also prevent upgrades. What about doing this as a three steps operation? 1. install sysvinit-core; that removes systemd-sysv but nothing else systemd related 2. reboot; init should now be sysv init 3. install libelogind0 libpam-elogind elogind Souldn't that work? But some stuff needs to be addressed first. Some 100 packages would be removed on my system: , | The following packages will be REMOVED: | akonadi-server* breeze* drkonqi* ettercap-graphical* ffmpegthumbs* | frameworkintegration* gdebi* isenkram* k3b* kactivitymanagerd* kaffeine* | kamera* kamoso* kcachegrind* kde-cli-tools* kde-config-cddb* | kde-config-screenlocker* kde-runtime* kde-style-breeze* kdeconnect* | kdelibs5-plugins* kdesudo* kinit* kio* kmahjongg* kmenuedit* kommander* | kpat* krusader* kwin-common* kwin-style-breeze* libcolorcorrect5* libk3b7* | libkf5akonadicore5abi2* libkf5akonadiwidgets5abi1* libkf5auth5* | libkf5authcore5* libkf5bookmarks5* libkf5cddb5* libkf5configwidgets5* | libkf5declarative5* libkf5iconthemes5* libkf5kcmutils5* libkf5kdegames7* | libkf5kdelibs4support5* libkf5kdelibs4support5-bin* libkf5kiocore5* | libkf5kiofilewidgets5* libkf5kiogui5* libkf5kiowidgets5* | libkf5kmahjongglib5* libkf5newstuff5* libkf5newstuffcore5* | libkf5notifyconfig5* libkf5parts5* libkf5plasma5* libkf5plasmaquick5* | libkf5purpose-bin* libkf5purpose5* libkf5quickaddons5* libkf5runner5* | libkf5sane5* libkf5style5* libkf5texteditor-bin* libkf5texteditor5* | libkf5textwidgets5* libkf5wallet-bin* libkf5xmlgui5* libkf5xmlrpcclient5* | libkscreenlocker5* libkwin4-effect-builtins1* libokular5core8* | libpam-systemd* libpolkit-qt-1-1* libpolkit-qt5-1-1* libprocessui7* | libtaskmanager6* libvirt-daemon-system* libweather-ion7* milou* okular* | packagekit* plasma-desktop* plasma-framework* plasma-integration* | plasma-workspace* policykit-1* polkit-kde-agent-1* | qml-module-org-kde-draganddrop* qml-module-org-kde-kconfig* | qml-module-org-kde-kcoreaddons* qml-module-org-kde-kquickcontrols* | qml-module-org-kde-kquickcontrolsaddons* qml-module-org-kde-kwindowsystem* | qml-module-org-kde-purpose* qml-module-org-kde-qqc2desktopstyle* rasdaemon* | skanlite* skrooge* systemd* udisks2* ` most of them KDE related, but not only. Bug #925344 (filed on Sat, 23 Mar 2019 13:33:24 +, 6 month ago) needs to be resolved in a speedy manner. But, AFAICS, no progress was made since :( Looking at one of the other packages, udisks2, I see direct and indirect dependencies to systemd: , | Depends: dbus, libblockdev-part2, libblockdev-swap2, | libblockdev-loop2, libblockdev-fs2, libpam-systemd, parted, udev, | ^^ | libacl1 (>= 2.2.23), libatasmart4 (>= 0.13), libblockdev-utils2 (>= | 2.20), libblockdev2 (>= 2.20), libc6 (>= 2.7), libglib2.0-0 (>= 2.50), | libgudev-1.0-0 (>= 165), libmount1 (>= 2.30), libpolkit-agent-1-0 (>= | 0.99), libpolkit-gobject-1-0 (>= 0.101), libsystemd0 (>= 209), | ^^^ | libudisks2-0 (>= 2.8.3) ` Those need to be addressed too. Cheers, -- Cristian
Bug#934491: libelogind0: failing to switch from systemd to sysvinit-core/elogind results in libsystemd.so.0 disappearing
On Sat, 21 Sep 2019, Mark Hindley wrote: > On Sat, Sep 21, 2019 at 06:51:16PM +0200, Cristian Ionescu-Idbohrn wrote: > > > Would you, please, start a new bug for this unless you really think > > > it is the same issue (apt being broken by continuing to uninstall > > > libsystemd0 after systemd prerm fails) and I will be happy to help. > > > > I really don't know what to think, but I do really feel this is not > > related to the systemd installed version. Any current systemd version > > should be removed without affecting the state. Am I wrong? > > I have to admit I am not clear exactly what you see is the problem. > Is it that removing systemd is taking lots of other packages with > it? > > Looking at the list of removals I think it is libpolkit-qt-1 that is > taking everything else out becuase it has not been patched to > support the new logind virtual packages. See #925344. > > But I still don't think it is the same as Simon's original bug here. Mark, I think you're right. I'll wait until the polkit-qt packages are patched, and if that does not solve my problem I'll submit a bug. Cheers, -- Cristian
Bug#934491: libelogind0: failing to switch from systemd to sysvinit-core/elogind results in libsystemd.so.0 disappearing
On Sat, 21 Sep 2019, Mark Hindley wrote: > On Sat, Sep 21, 2019 at 04:35:39PM +0200, Cristian Ionescu-Idbohrn wrote: > > I'm interested in this, but my systems (unstable and testing) are > > in a slightly different state. Let's take unstable, for example: > > Thanks for this. However, I really don't see it as relating to > Simon's original report. > > Would you, please, start a new bug for this unless you really think > it is the same issue (apt being broken by continuing to uninstall > libsystemd0 after systemd prerm fails) and I will be happy to help. I really don't know what to think, but I do really feel this is not related to the systemd installed version. Any current systemd version should be removed without affecting the state. Am I wrong? Cheers, -- Cristian
Bug#934491: libelogind0: failing to switch from systemd to sysvinit-core/elogind results in libsystemd.so.0 disappearing
On Sat, 21 Sep 2019, Mark Hindley wrote: > > Removing the pending tag as I don't think there is anything for > elogind to do to fix this. Hi, I'm interested in this, but my systems (unstable and testing) are in a slightly different state. Let's take unstable, for example: , | # apt-cache policy systemd-sysv | systemd-sysv: | Installed: (none) | Candidate: (none) ` , | # apt-cache policy sysvinit-core | sysvinit-core: | Installed: 2.96~beta-1 | Candidate: 2.96~beta-1 ` , | # apt-cache policy systemd | systemd: | Installed: 238-5 | Candidate: 238-5 ` (that is an older version). And that's because i have: , | # cat /etc/apt/preferences.d/no-systemd | Package: systemd systemd-sysv libsystemd0 libpam-systemd | Pin: release o=Debian | Pin-Priority: -1 ` So, pid 1 is already: , | -rwxr-xr-x 1 root root 53176 Aug 24 16:46 /sbin/init ` Systemd stuff was forcibly installed, but systemd is _not_ pid 1. Attempting to install: , | # apt-get install libpam-elogind elogind libelogind0 ` gives me a list of: , | 4 upgraded, 3 newly installed, 97 to remove and 146 not upgraded. ` Most of the packages to be removed are kde-related: , | The following packages will be REMOVED: | akonadi-server breeze drkonqi ffmpegthumbs frameworkintegration k3b | kactivitymanagerd kaffeine kamera kamoso kcachegrind kde-cli-tools | kde-config-cddb kde-config-screenlocker kde-runtime kde-style-breeze | kdeconnect kdelibs5-plugins kdesudo kinit kio kmahjongg kmenuedit kommander | kpat krusader kwin-common kwin-style-breeze libcolorcorrect5 libk3b7 | libkf5akonadicore5abi2 libkf5akonadiwidgets5abi1 libkf5auth5 libkf5authcore5 | libkf5bookmarks5 libkf5cddb5 libkf5configwidgets5 libkf5declarative5 | libkf5iconthemes5 libkf5kcmutils5 libkf5kdegames7 libkf5kdelibs4support5 | libkf5kdelibs4support5-bin libkf5kiocore5 libkf5kiofilewidgets5 | libkf5kiogui5 libkf5kiowidgets5 libkf5kmahjongglib5 libkf5newstuff5 | libkf5newstuffcore5 libkf5notifyconfig5 libkf5parts5 libkf5plasma5 | libkf5plasmaquick5 libkf5purpose-bin libkf5purpose5 libkf5quickaddons5 | libkf5runner5 libkf5sane5 libkf5style5 libkf5texteditor-bin | libkf5texteditor5 libkf5textwidgets5 libkf5wallet-bin libkf5xmlgui5 | libkf5xmlrpcclient5 libkscreenlocker5 libkwin4-effect-builtins1 | libokular5core8 libpam-systemd libpolkit-backend-1-0 libpolkit-qt-1-1 | libpolkit-qt5-1-1 libprocessui7 libsystemd0 libtaskmanager6 libweather-ion7 | milou okular plasma-desktop plasma-framework plasma-integration | plasma-workspace polkit-kde-agent-1 qml-module-org-kde-draganddrop | qml-module-org-kde-kconfig qml-module-org-kde-kcoreaddons | qml-module-org-kde-kquickcontrols qml-module-org-kde-kquickcontrolsaddons | qml-module-org-kde-kwindowsystem qml-module-org-kde-purpose | qml-module-org-kde-qqc2desktopstyle rasdaemon skanlite skrooge systemd | udisks2 ` but not only (some *polkit* among them, I guess kde-related). Of course I could let them be removed and later reinstall them. But that's not smooth/optimal. Still: , | The following additional packages will be installed: | gir1.2-polkit-1.0 libpolkit-agent-1-0 libpolkit-gobject-1-0 policykit-1 ` Looking deeper I notice both libelogind0 and libpam-elogind provide a certain version of systemd packages: , | Package: libelogind0 | Provides: libsystemd0 (= 241.3) ` , | Package: libpam-elogind | Provides: logind (= 241.3-1+debian1) ` but can't help wondering if that is necessary/relevant. Shouldn't they provide _any_ current version of libsystemd0 and logind and remove _any_ earlier versions? Isn't installing the current versions of systemd-related packages an unnecessary step? Cheers, -- Cristian
Bug#915834: fixed in irqbalance 1.5.0-2
On Sat, 12 Jan 2019, Andreas Henriksson wrote:
>
> Source: irqbalance
> Source-Version: 1.5.0-2
>
> We believe that the bug you reported is fixed in the latest version of
> irqbalance, which is due to be installed in the Debian FTP archive.
>
> A summary of the changes between this version and the previous one is
> attached.
[...]
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
>
> Format: 1.8
> Date: Sat, 12 Jan 2019 19:12:28 +0100
> Source: irqbalance
> Binary: irqbalance
> Architecture: source
> Version: 1.5.0-2
> Distribution: unstable
> Urgency: medium
> Maintainer: Debian QA Group
> Changed-By: Andreas Henriksson
> Description:
> irqbalance - Daemon to balance interrupts for SMP systems
> Closes: 915834
> Changes:
> irqbalance (1.5.0-2) unstable; urgency=medium
> .
>* QA Upload.
>* Add debian/patches/fix-permissions-for-unix-socket.patch (Closes:
> #915834)
On a sysv init system, this still fails, as the /run/irqbalance
directory does not exist; strace reveals:
,
| 23507 bind(5, {sa_family=AF_UNIX,
sun_path="/run/irqbalance//irqbalance23507.sock"}, 110
| 23509 <... ioctl resumed> , {B38400 opost isig icanon echo ...}) = 0
| 23507 <... bind resumed> ) = -1 ENOENT (No such file or
directory)
`
It may be a good idea to create that directory _before_ creating the
socket file, for example in the init-script:
mkdir -p /run/irqbalance
Cheers,
--
Cristian
Bug#916678: systemd: Caught , dumped core as pid 2097
Package: systemd Version: 239-13 Severity: critical Justification: breaks the whole system While trying to upgrade postfix* packages I ended up in this mess :( Every attempt (I know off) to get out of it failed :( I also lost the ability to ssh login. , | systemd[1]: Caught , dumped core as pid 2097. | | Broadcast message from systemd-journald@host (Sun 2018-12-16 17:16:09 CET): | | systemd[1]: Freezing execution. | | Failed to reload daemon: Connection reset by peer | Failed to retrieve unit state: Failed to activate service 'org.freedesktop.systemd1': timed out (service_start_timeout=25000ms) | Failed to stop postfix.service: Failed to activate service 'org.freedesktop.systemd1': timed out (service_start_timeout=25000ms) | See system logs and 'systemctl status postfix.service' for details. | Failed to get load state of postfix.service: Failed to activate service 'org.freedesktop.systemd1': timed out (service_start_timeout=25000ms) | invoke-rc.d: initscript postfix, action "stop" failed. | dpkg: warning: old postfix package pre-removal script subprocess returned error exit status 1 | dpkg: trying script from the new package instead ... | Failed to reload daemon: Failed to activate service 'org.freedesktop.systemd1': timed out (service_start_timeout=25000ms) | Failed to retrieve unit state: Failed to activate service 'org.freedesktop.systemd1': timed out (service_start_timeout=25000ms) | Failed to stop postfix.service: Failed to activate service 'org.freedesktop.systemd1': timed out (service_start_timeout=25000ms) | See system logs and 'systemctl status postfix.service' for details. | Failed to get load state of postfix.service: Connection timed out | invoke-rc.d: initscript postfix, action "stop" failed. | dpkg: error processing archive /tmp/user/0/apt-dpkg-install-FfjLf1/12-postfix_3.3.2-1_amd64.deb (--unpack): | new postfix package pre-removal script subprocess returned error exit status 1 | Failed to reload daemon: Failed to activate service 'org.freedesktop.systemd1': timed out (service_start_timeout=25000ms) | Failed to reload daemon: Failed to activate service 'org.freedesktop.systemd1': timed out (service_start_timeout=25000ms) | Failed to retrieve unit state: Connection timed out | Failed to start postfix.service: Failed to activate service 'org.freedesktop.systemd1': timed out (service_start_timeout=25000ms) | See system logs and 'systemctl status postfix.service' for details. | invoke-rc.d: initscript postfix, action "start" failed. | Failed to get properties: Failed to activate service 'org.freedesktop.systemd1': timed out (service_start_timeout=25000ms) | dpkg: error while cleaning up: | installed postfix package post-installation script subprocess returned error exit status 1 | Errors were encountered while processing: | /tmp/user/0/apt-dpkg-install-FfjLf1/12-postfix_3.3.2-1_amd64.deb | [master 985cc4a] committing changes in /etc after apt run | 1 file changed, 2 deletions(-) | Error: Timeout was reached | needrestart is being skipped since dpkg has failed | E: Sub-process /usr/bin/dpkg returned an error code (1) | | root@host:~# systemctl status postfix.service | Failed to get properties: Connection timed out ` I don't really think the segfault had anything to do with the upgrade of the postfix* packages, but with what happened prior to that. libc* packages were upgraded (caused by a dependency from gcc* package upgrades, I guess). I happen to have that documented: , | commit d31bcecaf0c85e3ced155a5b2ad813b65181c365 | Author: root | Date: Sun Dec 16 17:02:44 2018 +0100 | | committing changes in /etc after apt run | | Package changes: | -cpp-7 7.3.0-30 amd64 | -cpp-8 8.2.0-9 amd64 | +cpp-7 7.4.0-1 amd64 | +cpp-8 8.2.0-12 amd64 | -g++-8 8.2.0-9 amd64 | -g++-8-multilib 8.2.0-9 amd64 | +g++-8 8.2.0-12 amd64 | +g++-8-multilib 8.2.0-12 amd64 | -gcc-7 7.3.0-30 amd64 | -gcc-7-base 7.3.0-30 amd64 | -gcc-7-multilib 7.3.0-30 amd64 | -gcc-8 8.2.0-9 amd64 | -gcc-8-base 8.2.0-9 amd64 | -gcc-8-multilib 8.2.0-9 amd64 | +gcc-7 7.4.0-1 amd64 | +gcc-7-base 7.4.0-1 amd64 | +gcc-7-multilib 7.4.0-1 amd64 | +gcc-8 8.2.0-12 amd64 | +gcc-8-base 8.2.0-12 amd64 | +gcc-8-multilib 8.2.0-12 amd64 | -lib32asan4 7.3.0-30 amd64 | -lib32asan5 8.2.0-9 amd64 | -lib32atomic1 8.2.0-9 amd64 | -lib32cilkrts5 7.3.0-30 amd64 | +lib32asan4 7.4.0-1 amd64 | +lib32asan5 8.2.0-12 amd64 | +lib32atomic1 8.2.0-12 amd64 | +lib32cilkrts5 7.4.0-1 amd64 | -lib32gcc-7-dev 7.3.0-30 amd64 | -lib32gcc-8-dev 8.2.0-9 amd64 | -lib32gcc1 1:8.2.0-9 amd64 | -lib32gomp1 8.2.0-9 amd64 | -lib32itm1 8.2.0-9 amd64 | -lib32mpx2 8.2.0-9 amd64 | -lib32quadmath0 8.2.0-9 amd64 | -lib32stdc++-7-dev 7.3.0-30 amd64 | -lib32stdc++-8-dev 8.2.0-9 amd64 | -lib32stdc++6 8.2.0-9 amd64 | -lib32ubsan0 7.3.0-30 amd64 | -lib32ubsan1 8.2.0-9 amd64 | +lib32gcc-7-dev 7.4.
Bug#913552: firehol: Firehol upgrade 3.1.6+ds-4 to 3.1.6+ds-5 leaves firehol broken
On Tue, 13 Nov 2018, Russel Winder wrote: > > > Try this: > > > > https://snapshot.debian.org/binary/firehol/ > > Thanks for the pointer. I run Approx, so I have the history of > packages here anyway. The issue is whether I have to delve into it > for manual installation, or whether the Debian Sid package can be > rescinded. I suspect not, I think Debian is "the only direction is > forward" which is fair enough. That's my experience. > It sounds like usrmerge is becoming a Debian standard, so I might > try it on that one machine. Heads up. A move like that might break other packages too. The other thing you might want to careful with is what I wrote in bug #912624: > Repeating the upgrade process I found out that /etc/firehol/firehol.conf > is _forcebly_ overwritten. So, that's one bug: > > Installing new version of config file /etc/firehol/firehol.conf ... > > I'm asked if I want to keep /etc/default/firehol, though. -- Cristian
Bug#913552: firehol: Firehol upgrade 3.1.6+ds-4 to 3.1.6+ds-5 leaves firehol broken
On Tue, 13 Nov 2018, Russel Winder wrote: > > > It does not look as a solution anyway. > > And the issue does not seem to be a FireHOL issue. > > I guess that we have to stick to package 3.1.6+ds-4 for a while. > > I've held all but one machine on 3.1.6+ds-4 but now need to revert > the one test machine. Aptitude is telling me there is only > 3.1.6+ds-5. Can this version be removed from the repository and > 3.1.6+ds-4 reinstated, or do I just have to manually grab the > packages and install them? Try this: https://snapshot.debian.org/binary/firehol/ -- Cristian
Bug#913552: firehol: Firehol upgrade 3.1.6+ds-4 to 3.1.6+ds-5 leaves firehol broken
On Tue, 13 Nov 2018, Jerome BENOIT wrote: > On 12/11/2018 22:42, Cristian Ionescu-Idbohrn wrote: > > You don't happen to have that "move everything from /bin, /sbin, /lib > > to /usr/..." package installed? > > Do know have the short name (or regular name) of this package ? I guess it's this I was referring to: Package: usrmerge Description-en: Convert the system to the merged /usr directories scheme -- Cristian
Bug#913552: firehol: Firehol upgrade 3.1.6+ds-4 to 3.1.6+ds-5 leaves firehol broken
On Mon, 12 Nov 2018, Russel Winder wrote: > > > Can you get te version og the ffirehol package ? > > |> dpkg -l *firehol* > Desired=Unknown/Install/Remove/Purge/Hold > | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend > |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) > ||/ Name Version Architecture Description > +++-=---= > iF firehol 3.1.6+ds-5 all easy to use but powerful > iptables stateful firewall (program) > ii firehol-common3.1.6+ds-5 all easy to use but powerful > traffic suite (common library) > ii firehol-doc 3.1.6+ds-5 all easy to use but powerful > iptables stateful firewall (docs) > un firehol-tools (no description available) > ii firehol-tools-doc 3.1.6+ds-5 all easy to use but powerful > traffic suite (extra tools docs) You don't happen to have that "move everything from /bin, /sbin, /lib to /usr/..." package installed? My test on the sysV system I use shows the only non-existing/not used variable in /usr/lib/firehol/install.config is: FIREHOL_SHARE_DIR="$DATAROOTDIR/firehol" that is: FIREHOL_SHARE_DIR=/usr/share/firehol -- Cristian
Bug#912768: hplip-data: hp-toolbox fsck
Package: hplip-data
Version: 3.18.10+dfsg0-1
Severity: grave
Justification: renders package unusable
$ hp-toolbox
HP Linux Imaging and Printing System (ver. 3.18.10)
HP Device Manager ver. 15.0
Copyright (c) 2001-15 HP Development Company, LP
This software comes with ABSOLUTELY NO WARRANTY.
This is free software, and you are welcome to distribute it
under certain conditions. See COPYING file for more details.
QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-cii'
\Traceback (most recent call last):
File "/usr/bin/hp-toolbox", line 280, in
toolbox = ui.DevMgr5(__version__, device_uri, None)
File "/usr/share/hplip/ui5/devmgr5.py", line 253, in __init__
self.initUI()
File "/usr/share/hplip/ui5/devmgr5.py", line 324, in initUI
self.DiagnoseQueueAction.setIcon(QIcon(load_pixmap('warning', '16x16')))
AttributeError: 'DevMgr5' object has no attribute 'DiagnoseQueueAction'
Patch here:
https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/1789184/comments/7
seems to help.
-- System Information:
Debian Release: buster/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.18.0-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968), LANGUAGE=en_US:en
(charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
Versions of packages hplip-data depends on:
ii python3 3.6.7-1
ii xz-utils 5.2.2-1.3
hplip-data recommends no packages.
Versions of packages hplip-data suggests:
ii hplip 3.18.10+dfsg0-1
-- no debconf information
-- debsums errors found:
debsums: changed file /usr/share/hplip/ui5/devmgr5.py (from hplip-data package)
Cheers,
--
Cristian
Bug#912765: hplip: hp-doctor broken
Package: hplip
Version: 3.18.10+dfsg0-1
Severity: grave
Justification: renders package unusable
$ hp-doctor
Traceback (most recent call last):
File "/usr/bin/hp-doctor", line 42, in
check_extension_module_env('cupsext')
File "/usr/share/hplip/base/g.py", line 339, in check_extension_module_env
python_ver = xint((sys.version).split(' ')[0]) #find the
current python version ; xint() to convert string to int, returns a list
File "/usr/share/hplip/base/g.py", line 331, in xint
return l
UnboundLocalError: local variable 'l' referenced before assignment
-- System Information:
Debian Release: buster/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.18.0-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968), LANGUAGE=en_US:en
(charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
Versions of packages hplip depends on:
ii adduser3.118
ii cups 2.2.8-5
ii hplip-data 3.18.10+dfsg0-1
ii libc6 2.27-6
ii libcups2 2.2.8-5
ii libdbus-1-31.12.10-1
ii libhpmud0 3.18.10+dfsg0-1
ii libsane-hpaio 3.18.10+dfsg0-1
ii libsane1 1.0.27-3
ii libsnmp30 5.7.3+dfsg-4+b1
ii libusb-1.0-0 2:1.0.22-2
ii lsb-base 9.20170808
ii printer-driver-hpcups 3.18.10+dfsg0-1
ii python33.6.7-1
ii python3-dbus 1.2.8-2+b1
ii python3-gi 3.30.1-2
ii python3-pexpect4.6.0-1
ii python3-pil5.3.0-1
ii python3-reportlab 3.5.9-1
ii wget 1.19.5-2
ii xz-utils 5.2.2-1.3
Versions of packages hplip recommends:
pn avahi-daemon
ii policykit-1 0.105-21
pn printer-driver-postscript-hp
ii sane-utils1.0.27-3
Versions of packages hplip suggests:
pn hplip-doc
ii hplip-gui 3.17.10+repack0-7
ii python3-notify20.3-3
ii system-config-printer 1.5.11-3
-- no debconf information
Cheers,
--
Cristian
Bug#887625: gmime-bin: Illegal seek
Package: gmime-bin
Version: 3.0.5-1
Severity: grave
Justification: renders package unusable
$ strace -f gmime-uuencode file.jpg
...
openat(AT_FDCWD, "/proc/filesystems", O_RDONLY|O_CLOEXEC) = 3
fstat(3, {st_mode=S_IFREG|0444, st_size=0, ...}) = 0
read(3, "nodev\tsysfs\nnodev\trootfs\nnodev\tr"..., 1024) = 370
read(3, "", 1024) = 0
close(3)= 0
access("/etc/selinux/config", F_OK) = -1 ENOENT (No such file or directory)
futex(0x7fe06805ee28, FUTEX_WAKE_PRIVATE, 2147483647) = 0
futex(0x7fe06805ee28, FUTEX_WAKE_PRIVATE, 2147483647) = 0
dup(0) = 3
fstat(3, {st_mode=S_IFCHR|0600, st_rdev=makedev(136, 1), ...}) = 0
fstat(1, {st_mode=S_IFCHR|0600, st_rdev=makedev(136, 1), ...}) = 0
write(1, "begin 600 file.jpg\n", 22begin 600 file.jpg
) = 22
lseek(3, 0, SEEK_CUR) = -1 ESPIPE (Illegal seek)
lseek(3, 0, SEEK_SET) = -1 ESPIPE (Illegal seek)
openat(AT_FDCWD, "/usr/lib/x86_64-linux-gnu/charset.alias", O_RDONLY) = -1
ENOENT (No such file or directory)
open("/usr/lib/x86_64-linux-gnu/gconv/gconv-modules.cache", O_RDONLY) = 4
fstat(4, {st_mode=S_IFREG|0644, st_size=26258, ...}) = 0
mmap(NULL, 26258, PROT_READ, MAP_SHARED, 4, 0) = 0x7fe068eeb000
close(4)= 0
futex(0x7fe0670889e8, FUTEX_WAKE_PRIVATE, 2147483647) = 0
write(2, "gmime-uuencode: Illegal seek\n", 29gmime-uuencode: Illegal seek
) = 29
close(3)= 0
exit_group(1) = ?
+++ exited with 1 +++
-- System Information:
Debian Release: buster/sid
APT prefers testing
APT policy: (500, 'testing'), (99, 'unstable'), (59, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.14.0-2-amd64 (SMP w/8 CPU cores)
Locale: LANG=, LC_CTYPE= (charmap=ANSI_X3.4-1968), LANGUAGE=
(charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/bash
Init: sysvinit (via /sbin/init)
Versions of packages gmime-bin depends on:
ii libassuan0 2.5.1-1
ii libc6 2.26-2
ii libglib2.0-02.54.3-1
ii libgmime-3.0-0 3.0.5-1
ii libgpg-error0 1.27-5
ii libgpgme11 1.10.0-1
ii zlib1g 1:1.2.8.dfsg-5
gmime-bin recommends no packages.
gmime-bin suggests no packages.
-- no debconf information
Cheers,
--
Cristian
Bug#855442: mkchromecast: uninstallable
Package: mkchromecast Version: 0.3.7+git20170130-1 Severity: grave Justification: renders package unusable mkchromecast : Depends: gir1.2-notify but it is not installable Only gir1.2-notify-0.7:amd64 is available in sid. -- System Information: Debian Release: 9.0 APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.9.0-1-amd64 (SMP w/8 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) Versions of packages mkchromecast depends on: ii flac 1.3.2-1 ii lame 1:3.99.5-dmo5 ii python-flask 0.12-1 ii python-psutil5.0.1-1 ii python-pychromecast 0.7.7-2 ii python-pyqt5 5.7+dfsg-5 pn python:any ii sox 14.4.1-5+b1 ii vorbis-tools 1.4.0-10 ii youtube-dl 2017.02.07-1 mkchromecast recommends no packages. Versions of packages mkchromecast suggests: ii ffmpeg 10:3.2.4-dmo2 ii libav-tools 7:3.2.4-1 ii mkchromecast-alsa0.3.6-3 pn mkchromecast-pulseaudio -- no debconf information
Bug#836611: chromium: crash after upgrade 52.0.2743.116-2 -> 53.0.2785.89-1
Package: chromium Version: 53.0.2785.89-1 Severity: grave Justification: renders package unusable Downgrading to 52.0.2743.116-2 makes it usable. All TABs "Aw Snap!" after start :( This is what I do: $ chromium --no-referrers --proxy-server=localhost:8118 --disk-cache-size=0 --disk-cache-dir=/dev/null --media-cache-size=0 --media-cache-dir=/dev/null --cipher-suite-blacklist=0x0033,0x0039,0x009E,0xcc15 --purge-memory-button This is (part of) what I get: Received signal 4 ILL_ILLOPN 55c642090690 #0 0x55c63dab1e5e #1 0x55c63dab2219 #2 0x7f0c91051eb0 #3 0x55c642090690 #4 0x55c63e6ac530 #5 0x55c63e6acd43 #6 0x55c63e6aa8d6 #7 0x55c63e6ab15c #8 0x55c63eeaf43d #9 0x55c63eea32c1 #10 0x55c63eea3f53 #11 0x55c64103fea5 #12 0x55c641040ca1 #13 0x55c6410349d3 #14 0x55c64255 #15 0x55c63e52fc86 #16 0x55c63db1e8fd #17 0x55c642627051 #18 0x55c642627644 #19 0x55c63db1e8fd #20 0x55c63dad0bde #21 0x55c63dad174d #22 0x55c63dad1a18 #23 0x55c63dad3349 #24 0x55c63daea2fa #25 0x55c63dacfa05 #26 0x55c641057010 #27 0x55c63da82861 #28 0x55c63da82dfd #29 0x55c63da81061 #30 0x55c63d6219aa ChromeMain #31 0x7f0c87ed2700 __libc_start_main #32 0x55c63d62186a _start r8: r9: r10: 0022 r11: 0206 r12: 0c38ba21c1f8 r13: 0004 r14: 0c38ba21c210 r15: 55c64507c356 di: 35b3981a1000 si: 0001e000 bp: 0c38ba268000 bx: 0c38ba21c218 dx: 0008 ax: cx: ff60 sp: 7ffc0f300290 ip: 55c642090690 efl: 00010286 cgf: 002b0033 erf: trp: 0006 msk: cr2: [end of stack trace] Received signal 4 ILL_ILLOPN 55c642090690 #0 0x55c63dab1e5e #1 0x55c63dab2219 #2 0x7f0c91051eb0 #3 0x55c642090690 #4 0x55c63e6ac530 #5 0x55c63e6acd43 #6 0x55c63e6aa8d6 Received signal 4 ILL_ILLOPN 55c642090690 #7 0x55c63e6ab15c #8 0x55c63eeaf43d #0 0x55c63dab1e5e #1 0x55c63dab2219 #2 0x7f0c91051eb0 #9 0x55c63eea32c1 #3 0x55c642090690 #4 0x55c63e6ac530 Received signal 6 #10 0x55c63eea3f53 #0 0x55c63dab1e5e #1 0x55c63dab2219 #2 0x7f0c91051eb0 #3 0x7f0c87ee5198 #11 0x55c64103fea5 gsignal #4 0x7f0c87ee661a abort #5 0x55c63db3450a #6 0x55c63db34dc6 #7 0x55c63dab20d3 #8 0x55c63dab2237 # 9# 120x 7f0c91051eb00x 55c641040ca1 #10 0x55c642090690 #11 0x55c63e6ac530 #12 0x55c63e6acd43 #13 0x55c6410349d3 #14 0x55c64255 #15 0x55c63e52fc86 #16 0x55c63db1e8fd #17 0x55c642627051 #18 0x55c642627644 #19 0x55c63db1e8fd #20 0x55c63dad0bde #21 0x55c63dad174d #22 0x55c63dad1a18 #23 0x55c63dad3349 #24 0x55c63daea2fa #25 0x55c63dacfa05 #26 0x55c641057010 #27 0x55c63da82861 #28 0x55c63da82dfd #29 0x55c63da81061 #30 0x55c63d6219aa Received signal 4 ILL_ILLOPN 55c642090690 ChromeMain #31 0x7f0c87ed2700 __libc_start_main #32 0x55c63d62186a #0 0x55c63dab1e5e #1 0x55c63dab2219 Received signal _start6 r8: r9: r10: 0022 r11: 0206 r12: 31e37ba1c1f8 r13: 0004 r14: 31e37ba1c210 r15: 55c64507c354 di: 04b4d7f61000 si: 0001e000# bp: 31e37ba68 bx: 31e37ba1c2180x 55c63dab1e5e dx: 0008 ax: cx: ff60 sp: 7ffc0f300290 ip: 55c642090690 efl: 00010286 cgf: 002b0033 erf: trp: 0006 msk: cr2: [end of stack trace] -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.6.0-1-amd64 (SMP w/8 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) Versions of packages chromium depends on: ii libasound2 1.1.2-1 ii libatk1.0-0 2.21.90-2 ii libavcodec57 10:3.1.3-dmo3 ii libavformat5710:3.1.3-dmo3 ii libavutil55 10:3.1.3-dmo3 ii libc62.23-5 ii libcairo21.14.6-1+b1 ii libcups2 2.1.4-4 ii libdbus-1-3 1.10.10-1 ii libexpat12.2.0-1 ii libfontconfig1 2.11.0-6.7 ii libfreetype6 2.6.3-3+b1 ii libgcc1 1:6.2.0-2 ii libgdk-pixbuf2.0-0 2.34.0-1 ii libglib2.0-0 2.49.6-1 ii libgnome-keyring03.12.0-1+b1 ii libgtk-3-0 3.21.5-3 ii libharfbuzz0b1.2.7-1+b1 ii libjpeg62-turbo 1:1.5.0-1 ii libnettle6 3.2-1 ii libnspr4 2:4.12-6 ii libnss3 2:3.26-1 ii libpango-1.0-0 1.40.2-1 ii libpangocairo-1.0-0 1.40.2-1 ii libpci3 1:3.3.1-1.1 ii libpulse09.0-3 ii libspeechd2 0.8.4-2 ii libstdc++6 6.2.0-2 ii libx11-6 2:1.6.3-1 ii libxcomposite1 1:0.4.4-1 ii libxcursor1 1:1.1.14-1+b1
Bug#835465: [pkg-gnupg-maint] [Reproducible-builds] Bug#835465: python-apt: FTBFS: AptKeyError: recv from 'hkp://localhost:19191' failed for '0xa1bD8E9D78F7FE5C3E65D8AF8B48AD6246925553'
On Fri, 2 Sep 2016, Werner Koch wrote: > On Fri, 2 Sep 2016 15:48, cristian.ionescu-idbo...@axis.com said: > > > Well, not in unstable/sid: > > Well, I thought it was obvious that I speak about upstream 2.1.15 where > this was removed with commit d83ba4897bf217d1045c58d1b99e52bd31c58812 . No, not obvious :( Please, excuse my ignorance. > The systemd stuff is right now Debian specific. I don't really care about systemd stuff. I don't use it freely. I prefer sysV. Well, I'll have to wait and see what happens, I guess. -- Cristian
Bug#835465: [pkg-gnupg-maint] [Reproducible-builds] Bug#835465: python-apt: FTBFS: AptKeyError: recv from 'hkp://localhost:19191' failed for '0xa1bD8E9D78F7FE5C3E65D8AF8B48AD6246925553'
On Fri, 2 Sep 2016, Werner Koch wrote: > On Fri, 2 Sep 2016 10:55, cristian.ionescu-idbo...@axis.com said: > > > For historical reasons it is also possible to start dirmngr in > > a system daemon mode which uses a different directory > > layout. However, this mode is deprecated and may eventually > > be removed. > > > > Will the daemon be used in this context? > > No. That feature as actually been removed recently. Well, not in unstable/sid: # dpkg -L dirmngr | grep bin/dirmngr /usr/bin/dirmngr /usr/bin/dirmngr-client The change, I notice, in both sid and strech (compared to jessie) is that the sysv initscript vanished, but gained a systemd user service /usr/lib/systemd/user/dirmngr.service in sid. I take that as the dirnmgr daemon should _not_ be run by the root user. Jessie starts it per default. > > What about the scenario when one must go through a very strict > > proxy to reach the net? > > dirmngr has options for this. And well, it can also use tor as the > universal proxy ;-) >From what the man pages reveal, the daemon has those options. I can't see the dirmngr-client does. So, I may not have to worry about more configuration knobbs when used through python-apt, do I? How will dirmngr be used by apt then, now that it is installed as a dependency by python-apt? Cheers, -- Cristian
Bug#835465: [Reproducible-builds] Bug#835465: python-apt: FTBFS: AptKeyError: recv from 'hkp://localhost:19191' failed for '0xa1bD8E9D78F7FE5C3E65D8AF8B48AD6246925553'
Hi folks, I'm trying to understand this: On Tue, 30 Aug 2016, Daniel Kahn Gillmor wrote: > > furthermore, recent versions of gnupg (>= 2.1) do not fetch things from > keyservers directly -- if you want modern gpg to talk to the network, > you'll need to ensure that dirmngr is installed. Do you really "want modern gpg to talk to the network", always, or should that be optional. Yet another dependency. Yet another (useless) daemon. Yet more configurations. Makes me worry. `man 8 dirmngr': For historical reasons it is also possible to start dirmngr in a system daemon mode which uses a different directory layout. However, this mode is deprecated and may eventually be removed. Will the daemon be used in this context? Shouldn't that be a Recommends, instead? dirmngr is "Priority: optional". What about the scenario when one must go through a very strict proxy to reach the net? -- Cristian
Bug#835917: kdeconnect: The following packages will be REMOVED?
Package: kdeconnect Version: 0.9g-1 Severity: grave Justification: renders package unusable Since a few days back I see this: , | # apt-get install milou | Reading package lists... Done | Building dependency tree | Reading state information... Done | The following packages were automatically installed and are no longer required: | fonts-noto-hinted frameworkintegration kded5 kinit libcln6 libfakekey0 | libgps22 libkf5baloo5 libkf5balooengine5 libkf5filemetadata-data | libkf5filemetadata3 libkf5idletime5 libkf5js5 libkf5jsembed-data | libkf5jsembed5 libkf5networkmanagerqt6 libkf5screen-bin libkf5screen7 | libkf5sysguard-data libkf5waylandclient5 libkf5waylandserver5 | libkf5xmlrpcclient-data libkf5xmlrpcclient5 libkscreenlocker5 libksgrd7 | libkworkspace5-5 liblmdb0 libplasma-geolocation-interface5 libprocesscore7 | libprocessui7 libqalculate5-data libqalculate5v5 libtaskmanager5 | libweather-ion7 qdbus-qt5 qml-module-org-kde-kcoreaddons | qml-module-org-kde-kwindowsystem qml-module-org-kde-solid | qml-module-qtgraphicaleffects qml-module-qtquick-dialogs | qml-module-qtquick-privatewidgets | Use 'apt autoremove' to remove them. | The following packages will be REMOVED: | kdeconnect plasma-workspace | The following packages will be upgraded: | milou | 1 upgraded, 0 newly installed, 2 to remove and 12 not upgraded. ` If it's not a kdeconnect problem, please reassign this to the relevant package. -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.6.0-1-amd64 (SMP w/8 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) Versions of packages kdeconnect depends on: ii kde-cli-tools 4:5.7.0-1 ii libc6 2.23-5 ii libfakekey00.1-9 ii libkf5configcore5 5.25.0-1 ii libkf5configwidgets5 5.25.0-1 ii libkf5coreaddons5 5.25.0-1 ii libkf5dbusaddons5 5.25.0-1 ii libkf5i18n55.25.0-1 ii libkf5kcmutils55.25.0-1 ii libkf5kiocore5 5.25.0-1 ii libkf5kiofilewidgets5 5.25.0-1 ii libkf5kiowidgets5 5.25.0-1 ii libkf5notifications5 5.25.0-1 ii libkf5service-bin 5.25.0-1 ii libkf5service5 5.25.0-1 ii libkf5waylandclient5 4:5.25.0-1 ii libkf5widgetsaddons5 5.25.0-1 ii libqca-qt5-2 2.1.1-2 ii libqca-qt5-2-plugins 2.1.1-2 ii libqt5core5a 5.6.1+dfsg-3+b1 ii libqt5dbus55.6.1+dfsg-3+b1 ii libqt5gui5 5.6.1+dfsg-3+b1 ii libqt5network5 5.6.1+dfsg-3+b1 ii libqt5qml5 5.6.1-5 ii libqt5widgets5 5.6.1+dfsg-3+b1 ii libqt5x11extras5 5.6.1-2 ii libstdc++6 6.2.0-1 ii libx11-6 2:1.6.3-1 ii libxtst6 2:1.2.2-1+b1 ii plasma-workspace 4:5.6.5.1-1 ii sshfs 2.8-1 kdeconnect recommends no packages. kdeconnect suggests no packages. -- no debconf information Cheers, -- Cristian
Bug#833394: wmweather: URL of data source has changed
On Fri, 5 Aug 2016, Matthieu Weber wrote: > On Thu 04.08.2016 at 10:20:17PM +0200, Cristian Ionescu-Idbohrn wrote: > > On Wed, 3 Aug 2016, Matthieu Weber wrote: > > > > > > The URL of the source of the data used by wmweather has changed, > > > causing the software to exit immediately upon start. > > > > > > The fix is trivial, and a patch is included. > > > > Yeah, I thought of that too. And tested (from strace): > > > > GET /pub/data/observations/metar/decoded/YBRM.TXT HTTP/1.1\r\nHost: > > tgftp.nws.noaa.gov\r\nUser-Agent: wmweather 2.4.5\r\nAccept: > > */*\r\n\r\n > > Remove the "/pub" in the beginning of the path, it shouldn't be there. > > This url works: > http://tgftp.nws.noaa.gov/data/observations/metar/decoded/YBRM.TXT > > This one does not: > http://tgftp.nws.noaa.gov/pub/data/observations/metar/decoded/YBRM.TXT Yes, that does the trick ;) Cheers, -- Cristian
Bug#833394: wmweather: URL of data source has changed
On Wed, 3 Aug 2016, Matthieu Weber wrote: > > The URL of the source of the data used by wmweather has changed, > causing the software to exit immediately upon start. > > The fix is trivial, and a patch is included. Yeah, I thought of that too. And tested (from strace): GET /pub/data/observations/metar/decoded/YBRM.TXT HTTP/1.1\r\nHost: tgftp.nws.noaa.gov\r\nUser-Agent: wmweather 2.4.5\r\nAccept: */*\r\n\r\n HTTP/1.1 404 Not Found\r\nDate: Thu, 04 Aug 2016 19:46:03 GMT\r\nServer: Apache\r\nX-Frame-Options: SAMEORIGIN\r\nX-Content-Type-Options: nosniff\r\nX-XSS-Protection: 1; mode=block\r\nVary: Accept-Encoding\r\nContent-Length: 242\r\nContent-Type: text/html; charset=iso-8859-1\r\nSet-Cookie: NSC_ESNS=10f244c1-39a9-17a3-9678-00e0ed227be8_4120082755_1338136870_043233782597; Path=/; Expires=Thu, 04-Aug-2016 19:46:18 GMT\r\n\r\n\n\n404 Not Found\n\nNot Found\nThe requested URL /pub/data/observations/metar/decoded/YBRM.TXT was not found on this server.\n\n `wget' behaves likewise: wget http://tgftp.nws.noaa.gov/pub/data/observations/metar/decoded/YBRM.TXT --2016-08-04 21:39:59-- http://tgftp.nws.noaa.gov/pub/data/observations/metar/decoded/YBRM.TXT Resolving tgftp.nws.noaa.gov (tgftp.nws.noaa.gov)... 140.90.101.79 Connecting to tgftp.nws.noaa.gov (tgftp.nws.noaa.gov)|140.90.101.79|:80... connected. HTTP request sent, awaiting response... 404 Not Found 2016-08-04 21:40:01 ERROR 404: Not Found. but managed to get sooomething with `curl' a few minutes ago; not any more: curl -qvs http://tgftp.nws.noaa.gov/pub/data/observations/metar/decoded/YBRM.TXT * Trying 140.90.101.79... * Connected to tgftp.nws.noaa.gov (140.90.101.79) port 80 (#0) > GET /pub/data/observations/metar/decoded/YBRM.TXT HTTP/1.1 > Host: tgftp.nws.noaa.gov > User-Agent: curl/7.50.1 > Accept: */* > < HTTP/1.1 404 Not Found < Date: Thu, 04 Aug 2016 19:52:13 GMT < Server: Apache < X-Frame-Options: SAMEORIGIN < X-Content-Type-Options: nosniff < X-XSS-Protection: 1; mode=block < Vary: Accept-Encoding < Content-Length: 242 < Content-Type: text/html; charset=iso-8859-1 < Set-Cookie: NSC_ESNS=1104eaf0-3b1b-17a3-9678-00e0ed227be8_2753958198_0511137557_013169675417; Path=/; Expires=Thu, 04-Aug-2016 19:52:28 GMT < 404 Not Found Not Found The requested URL /pub/data/observations/metar/decoded/YBRM.TXT was not found on this server. * Connection #0 to host tgftp.nws.noaa.gov left intact `wmfrog' manages to get somthing out, using some other url: http://weather.noaa.gov/mgetmetar.php?=YBRM It seems `wmweather' can't handle redirections and there's some fsck at noaa.gov :( Cheers, -- Cristian
Bug#815642: udev-discover: ImportError: could not import gobject (could not find _PyGObject_API object)
Package: udev-discover
Version: 0.2.2-1.2
Severity: grave
Justification: renders package unusable
# udev-discover
/usr/bin/udev-discover:25: PyGIWarning: Gtk was imported without specifying a
version first. Use gi.require_version('Gtk', '3.0') before import to ensure
that the right version gets loaded.
from gi.repository import Gtk, Gdk
Traceback (most recent call last):
File "/usr/bin/udev-discover", line 29, in
from udevdiscover import DeviceFinder, get_subsystems
File "/usr/lib/python2.7/dist-packages/udevdiscover/__init__.py", line 23, in
from devicefinder import DeviceFinder, get_subsystems
File "/usr/lib/python2.7/dist-packages/udevdiscover/devicefinder.py", line
26, in
import gudev
ImportError: could not import gobject (could not find _PyGObject_API object)
-- System Information:
Debian Release: stretch/sid
APT prefers testing
APT policy: (500, 'testing'), (99, 'unstable'), (59, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.3.0-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=, LC_CTYPE= (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/bash
Init: sysvinit (via /sbin/init)
Versions of packages udev-discover depends on:
ii gconf23.2.6-3
ii gir1.2-gconf-2.0 3.2.6-3
ii gir1.2-gdkpixbuf-2.0 2.32.3-1.2
ii gir1.2-gtk-3.03.18.7-1
ii gnome-icon-theme 3.12.0-1
ii python-gconf 2.28.1+dfsg-1.1
ii python-gobject3.18.2-2
ii python-gudev 147.2-3
pn python:any
udev-discover recommends no packages.
udev-discover suggests no packages.
-- no debconf information
Cheers,
--
Cristian
Bug#814427: linux-image-4.3.0-1-amd64: memory leak in rtl_usb
Package: src:linux Version: 4.3.3-7 Severity: critical Tags: upstream Justification: breaks the whole system The bug triggers the oom-killer after memory gets exhausted. Rebooting was the only option left. Feb 10 17:09:01 debian kernel: [91971.006981] expr invoked oom-killer: gfp_mask=0x20858, order=0, oom_score_adj=0 Feb 10 17:13:16 debian kernel: [92224.364209] ssh invoked oom-killer: gfp_mask=0x201da, order=0, oom_score_adj=0 Feb 10 17:17:55 debian kernel: [92494.838897] chromium invoked oom-killer: gfp_mask=0x200da, order=0, oom_score_adj=300 Feb 10 17:18:10 debian kernel: [92512.491930] chromium invoked oom-killer: gfp_mask=0x201da, order=0, oom_score_adj=300 Feb 10 17:18:11 debian kernel: [92512.591229] chromium invoked oom-killer: gfp_mask=0x200da, order=0, oom_score_adj=200 Feb 10 17:18:11 debian kernel: [92512.627263] chromium invoked oom-killer: gfp_mask=0x200da, order=0, oom_score_adj=0 Feb 10 17:18:11 debian kernel: [92512.695305] chromium invoked oom-killer: gfp_mask=0x201da, order=0, oom_score_adj=300 Feb 10 17:18:11 debian kernel: [92518.620065] DOM Worker invoked oom-killer: gfp_mask=0x201da, order=0, oom_score_adj=0 Feb 10 17:19:49 debian kernel: [92616.049141] zsh invoked oom-killer: gfp_mask=0x200da, order=0, oom_score_adj=0 Feb 10 17:19:56 debian kernel: [92623.960756] ssh invoked oom-killer: gfp_mask=0x201da, order=0, oom_score_adj=0 Feb 10 17:19:56 debian kernel: [92624.064644] ssh invoked oom-killer: gfp_mask=0x201da, order=0, oom_score_adj=0 Feb 10 17:19:57 debian kernel: [92624.244884] fping invoked oom-killer: gfp_mask=0x200da, order=0, oom_score_adj=0 Feb 10 17:19:57 debian kernel: [92624.448912] expr invoked oom-killer: gfp_mask=0x200da, order=0, oom_score_adj=0 Feb 10 17:19:57 debian kernel: [92625.881507] chromium invoked oom-killer: gfp_mask=0x200da, order=0, oom_score_adj=300 Feb 10 17:20:07 debian kernel: [92635.538249] chromium invoked oom-killer: gfp_mask=0x200da, order=0, oom_score_adj=300 Feb 10 17:20:08 debian kernel: [92636.414606] Xorg invoked oom-killer: gfp_mask=0x200da, order=0, oom_score_adj=0 Feb 10 17:21:08 debian kernel: [92694.084031] sshd invoked oom-killer: gfp_mask=0x201da, order=0, oom_score_adj=0 Feb 10 17:22:28 debian kernel: [92744.218266] cron invoked oom-killer: gfp_mask=0x20858, order=0, oom_score_adj=0 Feb 10 17:22:28 debian kernel: [92773.248057] smtpd invoked oom-killer: gfp_mask=0x200da, order=0, oom_score_adj=0 Feb 10 17:22:28 debian kernel: [92777.365410] ssh invoked oom-killer: gfp_mask=0x201da, order=0, oom_score_adj=0 Feb 10 17:22:28 debian kernel: [92777.470042] hddtemp invoked oom-killer: gfp_mask=0x200da, order=0, oom_score_adj=0 Feb 10 17:22:28 debian kernel: [92777.514018] cron invoked oom-killer: gfp_mask=0x2040d0, order=0, oom_score_adj=0 Feb 10 17:22:30 debian kernel: [92781.628055] top invoked oom-killer: gfp_mask=0x200da, order=0, oom_score_adj=0 Feb 10 17:26:30 debian kernel: [93018.201374] gconfd-2 invoked oom-killer: gfp_mask=0x200da, order=0, oom_score_adj=0 I found this on the LKML mailing list: https://lkml.org/lkml/2015/12/6/113 FromPeter Wu <> Subject [PATCH] rtlwifi: fix gigantic memleak in rtl_usb DateSun, 6 Dec 2015 18:57:57 +0100 which seems to be related. The device is: Bus 003 Device 007: ID 2001:3308 D-Link Corp. DWA-121 802.11n Wireless N 150 Pico Adapter [Realtek RTL8188CUS] The interface was not set to 'monitor' type, but 'managed'. I ifdowned the wlan0 iface and: # lsmod | egrep rtl rtl8192cu 65536 0 rtl_usb20480 1 rtl8192cu rtl8192c_common49152 1 rtl8192cu rtlwifi77824 3 rtl_usb,rtl8192c_common,rtl8192cu mac80211 626688 3 rtl_usb,rtlwifi,rtl8192cu cfg80211 540672 2 mac80211,rtlwifi usbcore 233472 13 uas,uhci_hcd,rtl_usb,usb_storage,usbserial,ohci_hcd,ehci_hcd,ehci_pci,usbhid,ftdi_sio,rtl8192cu,xhci_hcd,xhci_pci # modprobe -r -v rtl8192cu rmmod rtl8192cu rmmod rtl8192c_common rmmod rtl_usb rmmod rtlwifi rmmod mac80211 rmmod cfg80211 rmmod rfkill vmstat shows memory consumtion stabilized (at least it looks like that). The leak was around 300 k/s. Now it looks like the system is slowly recovering. Is no longer just allocating memory, but deallocating too. Simplified system information follows: -- Package-specific info: ** Version: Linux version 4.3.0-1-amd64 (debian-ker...@lists.debian.org) (gcc version 5.3.1 20160114 (Debian 5.3.1-6) ) #1 SMP Debian 4.3.3-7 (2016-01-19) ** Command line: BOOT_IMAGE=/vmlinuz-4.3.0-1-amd64 root=/dev/mapper/vg0-root ro cgroup_enable=memory swapaccount vga=795 ** Model information sys_vendor: product_name: product_version: chassis_vendor: chassis_version: bios_vendor: Intel Corp. bios_version: BAP6710H.86A.0067.2011.0526.1448 board_vendor: Intel Corporation board_name: DP67BA board_version: AAG10219-300 -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (500, 'testing'), (99, 'unstable'),
Bug#812404: cp: failed to access '/tmp/user/0/mkinitramfs_2ypg84//bin/touch': Too many levels of symbolic links
Package: initramfs-tools
Version: 0.122
Severity: grave
Justification: renders package unusable
Setting up initramfs-tools-core (0.122) ...
Installing new version of config file /etc/initramfs-tools/initramfs.conf ...
Setting up initramfs-tools (0.122) ...
update-initramfs: deferring update (trigger activated)
Processing triggers for initramfs-tools (0.122) ...
update-initramfs: Generating /boot/initrd.img-4.3.0-1-amd64
cp: failed to access '/tmp/user/0/mkinitramfs_2ypg84//bin/touch': Too many
levels of symbolic links
E: /usr/share/initramfs-tools/hooks/fsprotect failed with return 1.
update-initramfs: failed for /boot/initrd.img-4.3.0-1-amd64 with 1.
dpkg: error processing package initramfs-tools (--configure):
subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
initramfs-tools
# ls -al /tmp/user/0/mkinitramfs_Rfce4o/bin/
total 2172
drwxr-xr-x 2 root root4096 Jan 23 10:53 .
drwxr-xr-x 11 root root4096 Jan 23 10:53 ..
-rwxr-xr-x 1 root root 1837392 Jan 22 08:31 busybox
-rwxr-xr-x 1 root root3963 Jan 10 18:58 cryptroot-unlock
-rwxr-xr-x 1 root root 211136 Nov 9 14:35 grep
-rwxr-xr-x 1 root root 244 May 13 2010 is_aufs
-rwxr-xr-x 1 root root 154696 Dec 20 19:02 kmod
lrwxrwxrwx 1 root root 7 Jan 23 10:53 sh -> busybox
lrwxrwxrwx 1 root root 5 Jan 23 10:53 touch -> touch
^^
That should probably be:
touch -> busybox
I don't really understand what's creating the `touch' symlink.
Never mind that, I found two `touch' instances in the mkinitramfs script.
Those can also be replaced with redirections. But, the correct shell
redirection replacement for `touch' is:
>>filepath
not:
>filepath
as the latter will also truncate the 'filepath'.
Here is a patch proposal:
--- mkinitramfs.orig2016-01-18 21:05:05.0 +0100
+++ mkinitramfs 2016-01-23 12:18:26.970456642 +0100
@@ -98,7 +98,7 @@
usage
fi
-touch "$outfile"
+>> "$outfile"
outfile="$(readlink -f "$outfile")"
# And by "version" we really mean path to kernel modules
@@ -273,7 +273,7 @@
fi
# fstab and mtab
-touch "${DESTDIR}/etc/fstab"
+>> "${DESTDIR}/etc/fstab"
ln -s /proc/mounts "${DESTDIR}/etc/mtab"
# module-init-tools
Still, that is not the problem cause. The problem occurs somewhere in
or after `update-initramfs', in a copy operation.
Downgrading to version 0.120 for now.
-- Package-specific info:
-- initramfs sizes
-rw-r--r-- 1 root root 19M Dec 23 14:43 /boot/initrd.img-4.2.0-1-amd64
-rw-r--r-- 1 root root 20M Jan 23 10:57 /boot/initrd.img-4.3.0-1-amd64
-- /proc/cmdline
BOOT_IMAGE=/boot/vmlinuz-4.3.0-1-amd64
root=UUID=86271730-a611-4f51-a4d0-f0028b70b2ce ro cgroup_enable=memory
swapaccount vga=795
...
-- /etc/initramfs-tools/modules
-- /etc/kernel-img.conf
# Kernel image management overrides
# See kernel-img.conf(5) for details
do_symlinks = yes
do_bootloader = no
do_initrd = yes
link_in_boot = no
-- /etc/initramfs-tools/initramfs.conf
MODULES=most
BUSYBOX=y
KEYMAP=n
COMPRESS=gzip
DEVICE=
NFSROOT=auto
-- /etc/initramfs-tools/update-initramfs.conf
update_initramfs=yes
backup_initramfs=no
-- mkinitramfs hooks
/etc/initramfs-tools/hooks/:
reiserfsprogs
/usr/share/initramfs-tools/hooks:
bootcdinitramfshook
busybox
cryptgnupg
cryptkeyctl
cryptopenct
cryptopensc
cryptpassdev
cryptroot
cryptroot-unlock
dmsetup
fsck
fsprotect
fuse
keymap
klibc
kmod
lvm2
mdadm
ntfs_3g
resume
thermal
udev
v86d
zz-busybox
zz_nvidia-blacklists-nouveau
-- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.3.0-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
Versions of packages initramfs-tools depends on:
ii busybox-static [busybox] 1:1.22.0-17
ii cpio 2.11+dfsg-4.1
ii klibc-utils 2.0.4-7
ii kmod 22-1
ii udev 228-4+b1
Versions of packages initramfs-tools recommends:
ii busybox-static [busybox] 1:1.22.0-17
Versions of packages initramfs-tools suggests:
ii bash-completion 1:2.1-4.2
-- no debconf information
Bug#791869: lvm2: updating src:lvm2 from 2.02.111-2.2 to 2.02.122-1 breaks booting, mounting LVs other than / fails
On Mon, 27 Jul 2015, Michael Biebl wrote:
>
> Not sure if that is happening here. But fixing [2] and making sure
> pvscan is run via /bin/systemd-run look like should be done in any
> case.
>
> Michael
>
>
> [2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=783182
Just a minor point here.
I have 2 systems running lvm over raid0.
On one of them (non-systemd init unstable box, but with systemd and
udev 223-2 installed) there's no /bin/systemd-run:
# which systemd-run
/usr/bin/systemd-run
Hardly possible to use _before_ /usr (separate partition) is mounted.
On another system (stretch (104 upgraded, 0 newly installed, 0 to
remove and 141 not upgraded), uptime: 13:09:13 up 840 days, 23:13, 67
^^^
users), the systemd package is not even installed. udev 222-2 and
lvm2 2.02.111-2.2 are installed.
systemd-run is refered to in /lib/udev/rules.d/69-lvm-metad.rules:
ACTION!="remove", ENV{LVM_PV_GONE}=="1", RUN+="/bin/systemd-run
/sbin/lvm pvscan --cache $major:$minor", GOTO="lvm_end"
Cheers,
--
Cristian
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#763784: libsystemd0: is this sane?
Source: libsystemd0 Version: 215-5+b1 Severity: critical Justification: breaks the whole system Looking deeper: Broken policykit-1:amd64 Depends on dbus [ amd64 ] < 1.8.8-1+b1 | 1.9.0-1 > ( ad Considering dbus:amd64 51 as a solution to policykit-1:amd64 16 Reinst Failed early because of systemd:amd64 Reinst Failed because of libpam-systemd:amd64 Yes, I have policykit-1 on hold, as it attempts to make me install systemd, and I have (currently) no use for it. I do _not_ want _any_ systemd packages installed on my system. I'm not interested. The current systemd plague is crippling my system and I don't like it (understatement). Please, pretty please, make this smoother! -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16-1-amd64 (SMP w/8 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/dash -- Cristian -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#761225: subsurface is marked for autoremoval from testing
On Fri, 26 Sep 2014, Debian testing autoremoval watch wrote: > > subsurface 4.0.3-2.1 is marked for autoremoval from testing on 2014-10-11 > > It is affected by these RC bugs: > 761225: subsurface: something is not right :( I do confirm that unstable: subsurface 4.2-3 libgit2-21 0.21.1-1 install and run on testing. So the bug is solved when those unstable packages migrate to testing. Cheers, -- Cristian -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#757758: dkms: sed: -e expression #1, char 6: unknown command: m when installing nvidia
On Fri, 19 Sep 2014, James McCoy wrote: > > Control: tag -1 patch > # system fails to fully boot due to built, but not installed modules > Control: severity -1 serious > > On Sun, Sep 14, 2014 at 03:34:07PM +0200, Cristian Ionescu-Idbohrn wrote: > > The attached patch attempts to correct the error(s) and adds some > > small code improvement. > > > > The bottom line is the arrays 'sa_mc_o' and 'sa_sck_o' are empty and > > `sed' is run without a script. > > Thanks for the patch, Cristian. I had a system that was booting into > maintenance mode because it couldn't find dkms-built modules and this > got things working again. You're most welcome James. I'm glad the patch did help. Let's hope the maintainers will soonish correct that dkms bug so that noone else will have to experience the problems you did. Unfortunately, things are moving slowly out there :( And judging from what `apt-get policy dkms' shows, both testing and unstable seem affected. Cheers, -- Cristian -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#761225: closed by Sylvestre Ledru (Re: Bug#761225: subsurface: something is not right :()
On Fri, 12 Sep 2014, Debian Bug Tracking System wrote: > > This is an automatic notification regarding your Bug report > which was filed against the subsurface package: > > #761225: subsurface: something is not right :( > > It has been closed by Sylvestre Ledru . > This is fixed with subsurface 4.2-2 ;) > > Sylvestre "subsurface : Depends: libgit2-0 (>= 0.20.0) but it is not installable" ^^ ^ Hmm... And that's what I'm trying to upgrade to: subsurface 4.2-2, and hit the wall ;) It has a dependency to: 'libgit2-0 (>= 0.20.0)' ^ a non-existing package. Maybe that should be libgit2-21? Because that is what libgit2-dev depends on? Cheers, -- Cristian -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#761225: subsurface: something is not right :(
Package: subsurface Version: 4.0.3-2.1+b1 Severity: grave Justification: renders package unusable # dpkg --get-selections | egrep libgit2 libgit2-21:amd64install libgit2-dev:amd64 install # apt-cache policy libgit2-dev libgit2-dev: Installed: 0.21.1-1 Candidate: 0.21.1-1 Version table: *** 0.21.1-1 0 500 http://ftp.se.debian.org/debian/ sid/main amd64 Packages 100 /var/lib/dpkg/status # dpkg -s libgit2-21:amd64 Package: libgit2-21 Version: 0.21.1-1 # dpkg -s libgit2-dev Package: libgit2-dev Version: 0.21.1-1 # apt-get install subsurface Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: subsurface : Depends: libgit2-0 (>= 0.20.0) but it is not installable E: Unable to correct problems, you have held broken packages. I'm confused :( -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16-1-amd64 (SMP w/8 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/dash Versions of packages subsurface depends on: ii libc6 2.19-10 ii libdivecomputer0 0.4.2-1 ii libgcc11:4.9.1-13 ii libmarblewidget19 4:4.14.0-2 ii libqt4-network 4:4.8.6+git64-g5dc8b2b+dfsg-2 ii libqt4-svg 4:4.8.6+git64-g5dc8b2b+dfsg-2 ii libqtcore4 4:4.8.6+git64-g5dc8b2b+dfsg-2 ii libqtgui4 4:4.8.6+git64-g5dc8b2b+dfsg-2 ii libqtwebkit4 2.3.2.dfsg-3 ii libsqlite3-0 3.8.6-1 ii libstdc++6 4.9.1-13 ii libxml22.9.1+dfsg1-4 ii libxslt1.1 1.1.28-2 ii libzip20.11.2-1.1 ii zlib1g 1:1.2.8.dfsg-2 subsurface recommends no packages. subsurface suggests no packages. -- no debconf information Cheers, -- Cristian -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#754830: bluez: rfcomm and bluetoothd fail to start
Package: bluez
Version: 5.21-1
Severity: grave
/etc/init.d/bluetooth fails to start.
First:
Starting bluetooth: bluetoothd rfcomm/usr/bin/rfcomm: invalid option --
'f'
After editing the file and removing that option, next thing coms up:
Starting bluetooth: bluetoothd rfcommMissing dev parameter
Still, everything is reported with an [ ok ] message, which is confusing
at best.
I identified two other bug reports pointing in the same direction:
712386 [bluez] invalid option passed to rfcomm tool
737502 bluez: conffiles not removed
reported already on some experimental version.
-- System Information:
Debian Release: jessie/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.14-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash
Versions of packages bluez depends on:
ii dbus 1.8.6-1
ii init-system-helpers 1.19
ii kmod 18-1
ii libc62.19-7
ii libdbus-1-3 1.8.6-1
ii libglib2.0-0 2.40.0-3
ii libreadline6 6.3-6
ii libudev1 204-14
ii lsb-base 4.1+Debian13
ii udev 204-14
bluez recommends no packages.
bluez suggests no packages.
-- Configuration Files:
/etc/init.d/bluetooth [Errno 2] No such file or directory:
'/etc/init.d/bluetooth'
Yes. The attempt to make it work:
--- /etc/init.d/bluetooth.orig 2014-06-27 21:50:43.0 +0200
+++ /etc/init.d/bluetooth.mine 2014-07-14 18:39:02.721719759 +0200
@@ -103,14 +103,17 @@
start_rfcomm()
{
- if [ -x $RFCOMM ] && [ -f $RFCOMM_CONF ] ; then
+# if [ -x $RFCOMM ] && [ -f $RFCOMM_CONF ] ; then
+ if [ -x $RFCOMM ] ; then
# rfcomm must always succeed for now: users
# may not yet have an rfcomm-enabled kernel
if [ "$VERBOSE" != no ]; then
log_progress_msg "${RFCOMM##*/}"
- $RFCOMM -f $RFCOMM_CONF bind all || :
+# $RFCOMM -f $RFCOMM_CONF bind all || :
+ $RFCOMM bind all || :
else
- $RFCOMM -f $RFCOMM_CONF bind all >/dev/null 2>&1 || :
+# $RFCOMM -f $RFCOMM_CONF bind all >/dev/null 2>&1 || :
+ $RFCOMM bind all >/dev/null 2>&1 || :
fi
fi
}
@@ -129,14 +132,17 @@
restart_rfcomm()
{
- if [ -x $RFCOMM ] && [ -f $RFCOMM_CONF ] ; then
+# if [ -x $RFCOMM ] && [ -f $RFCOMM_CONF ] ; then
+ if [ -x $RFCOMM ] ; then
if [ "$VERBOSE" != no ]; then
log_progress_msg "${RFCOMM##*/}"
$RFCOMM unbind all || :
- $RFCOMM -f $RFCOMM_CONF bind all || :
+# $RFCOMM -f $RFCOMM_CONF bind all || :
+ $RFCOMM bind all || :
else
$RFCOMM unbind all >/dev/null 2>&1|| :
- $RFCOMM -f $RFCOMM_CONF bind all >/dev/null 2>&1 || :
+# $RFCOMM -f $RFCOMM_CONF bind all >/dev/null 2>&1 || :
+ $RFCOMM bind all >/dev/null 2>&1 || :
fi
fi
}
-- no debconf information
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#750909: closed by Michael Biebl (Re: Bug#750909: systemd: breaks a big part of my system)
On Mon, 9 Jun 2014, Michael Stapelberg wrote: > Cristian Ionescu-Idbohrn writes: > > Is this a joke or what? > That’s what we thought when we received your original report, but > you seem to be serious. > > Your report is against systemd, but you are complaining about _other > software_ depending on systemd, as far as I can tell. This is not in > our control, so you’re in the wrong place. Please take this > somewhere else. Allright. Got your point, I think. I'll take the hard route and attempt to identify and file bugs against other packages that force dependencies on systemd (and related packages), which doesn't make my life easier at all :( Cheers, -- Cristian -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#750909: closed by Michael Biebl (Re: Bug#750909: systemd: breaks a big part of my system)
On Sun, 8 Jun 2014, Debian Bug Tracking System wrote: > > This is an automatic notification regarding your Bug report > which was filed against the src:systemd package: > > #750909: systemd: breaks a big part of my system > > It has been closed by Michael Biebl . > > Their explanation is attached below along with your original report. > If this explanation is unsatisfactory and you have not received a > better one in a separate message then please contact Michael Biebl > by replying to this email. ... > -- > Diese Nachricht wurde von meinem Android-Mobiltelefon mit K-9 Mail gesendet. Is this a joke or what? -- Cristian -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#750909: systemd: breaks a big part of my system
Source: systemd Severity: critical Justification: breaks unrelated software I've chosen to keep away from systemd and systemd related packages, but I haven't been paying enough attention and ended up with these packages installed on my system: $ dpkg --get-selections | egrep systemd libsystemd-daemon0:amd64install libsystemd-id128-0:amd64install libsystemd-id128-0:i386 install libsystemd-journal0:amd64 install libsystemd-journal0:i386install libsystemd-login0:amd64 install All the above packages are 'Priority: optional'. I also have package policykit-1 on hold, as it's attempting to install more systemd related packages: $ apt-get install policykit-1 Reading package lists... Done Building dependency tree Reading state information... Done The following extra packages will be installed: libpam-systemd systemd systemd-sysv Suggested packages: systemd-ui The following packages will be REMOVED: sysvinit-core The following NEW packages will be installed: libpam-systemd systemd systemd-sysv The following held packages will be changed: policykit-1 The following packages will be upgraded: policykit-1 1 upgraded, 3 newly installed, 1 to remove and 6 not upgraded. policykit-1 is also 'Priority: optional'. I already removed quite a few gnome-related packages from my system as they have dependencies to systemd related packages. I don't use gnome and I can live without. Still... Attempting to purge the systemd related packages leeds to this: # apt-get --purge remove libsystemd-daemon0:amd64 libsystemd-id128-0:amd64 libsystemd-journal0:amd64 libsystemd-login0:amd64 The following information may help to resolve the situation: The following packages have unmet dependencies: policykit-1 : Depends: libpolkit-agent-1-0 (>= 0.105) but it is not going to be installed Depends: libpolkit-backend-1-0 (>= 0.99) but it is not going to be installed Depends: libpolkit-gobject-1-0 (>= 0.101) but it is not going to be installed Depends: consolekit but it is not going to be installed Depends: dbus E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages. Alright... Adding policykit-1 to the list: # apt-get --purge remove libsystemd-daemon0:amd64 libsystemd-id128-0:amd64 libsystemd-journal0:amd64 libsystemd-login0:amd64 policykit-1 ... The following packages will be REMOVED: 2mandvd* accountsservice* alleyoop* alsaplayer-common* audacious* audacious-plugins* audtty* avahi-daemon* avahi-utils* avidemux* avidemux-plugins* avidemux-qt* blender* blueman* bluetooth* bluez* bluez-alsa* bluez-cups* bluez-gstreamer* bochs* bochs-term* bochs-wx* bochs-x* bombono-dvd* cheese* clementine* colord* compiz-gtk* compiz-plugins* consolekit* csmash* cups* cups-core-drivers* cups-daemon* cups-pdf* cups-pk-helper* dbus* dbus-x11* deadbeef* default-jre* devede* digikam* digikam-private-libs* distccmon-gnome* dradio* dvd-slideshow* dvdrip* dvdwizard* ekiga* electric* epiphany-browser* eqonomize* etherape* ettercap-graphical* exo-utils* extremetuxracer* festival* festlex-cmu* festlex-oald* festlex-poslex* festvox-kallpc16k* festvox-rablpc16k* ffmpeg* foomatic-gui* fprintd* freetuxtv* fusion-icon* gcipher* gconf-defaults-service* gconf-editor* gconf2* gcr* gdebi* gimp* gir1.2-accountsservice-1.0* gir1.2-polkit-1.0* gitg* gkdebconf* gksu* gnome-dvb-client* gnome-dvb-daemon* gnome-keyring* gnome-media* gnome-photo-printer* gnome-screensaver* gnome-session-bin* gnome-system-log* gnome-video-effects* gource* gpac* gpac-modules-base* gpointing-device-settings* greenwich* gstreamer0.10-gconf* gstreamer0.10-plugins-good* gstreamer1.0-plugins-bad* gtetrinet* gtick* gurlchecker* guvcview* gwc* gxine* gxineplugin* h264enc* hplip* hplip-cups* hplip-gui* impressive* inkscape* k3b* k3d* kaffeine* kcachegrind* kde-config-cddb* kde-runtime* kdebase-runtime* kdelibs5-plugins* kdepim-runtime* kipi-plugins* kmahjongg* kommander* kpat* libaccountsservice0* libakonadi-calendar4* libakonadi-contact4* libasound2-plugins* libav-tools* libavdevice54* libavdevice55* libbonoboui2-0* libcheese-gtk23* libcheese7* libdv-bin* libestools2.1* libexo-1-0* libfarstream-0.1-0* libfluidsynth1* libgconf2-dev* libgegl-0.2-0* libgksu2-0* libgnome-2-0* libgnome-media-p
Bug#742113: rsyslog: still seeing some odd action 17 suspend/resume messages
On Tue, 15 Apr 2014, Michael Biebl wrote: > Am 15.04.2014 12:52, schrieb Cristian Ionescu-Idbohrn: > > > The other option may be to comment out the xconsole rule in > > rsyslog.conf: > > [..] > > > Wouldn't it? As I know I don't have a consumer on /dev/xconsole. > > Would you agree? > > Sure, if you never use xconsole, that works as well. > I was actually considering shipping with that commented out per default. That'd be a good idea. > Just wasn't sure if this breaks existing setups / expectations from > certain users since as far as I can remember this snippet has always > been in there. Yes, but /etc/rsyslog.conf is a conf-file. A package upgrade will signal that there are differences. The admin will be able to examine and make a decision. > Regarding this bug report, are you ok if we close it? Yes. It's ok to close this. Cheers, -- Cristian -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#742113: rsyslog: still seeing some odd action 17 suspend/resume messages
On Tue, 15 Apr 2014, Michael Biebl wrote: > > Actually, yes. This is expected. If you don't have a consumer on > /dev/xconsole (which I assume you don't have), the pipe will run > full eventually and rsyslog will suspend trying to write to the > pipe. It does retry after a while though. Alright. Got it. > What was fixed was the incorrect way to detect failures when writing > to the pipe. So rsyslog continuously retried without actually > suspending properly. I see. > If you want to suppress those log messages completely, you can set > action.reportSuspension [0] to off. Either globally or per output. > > Does that sufficiently answer your question? Yes. Thanks. > [0] http://www.rsyslog.com/doc/global.html The other option may be to comment out the xconsole rule in rsyslog.conf: --- /etc/rsyslog.conf.orig 2012-03-15 13:39:12.0 +0100 +++ /etc/rsyslog.conf 2014-04-15 12:47:11.0 +0200 @@ -115,7 +115,7 @@ # NOTE: adjust the list below, or you'll go crazy if you have a reasonably # busy site.. # -daemon.*;mail.*;\ - news.err;\ - *.=debug;*.=info;\ - *.=notice;*.=warn |/dev/xconsole +#//#daemon.*;mail.*;\ +#//# news.err;\ +#//# *.=debug;*.=info;\ +#//# *.=notice;*.=warn |/dev/xconsole Wouldn't it? As I know I don't have a consumer on /dev/xconsole. Would you agree? Cheers, -- Cristian -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#742113: rsyslog: still seeing some odd action 17 suspend/resume messages
Package: rsyslog Version: 7.6.3-1 Severity: normal Is this expected? (maybe after log rotation?) Apr 15 08:26:14 anonymous rsyslogd-2359: action 'action 17' resumed (module 'builtin:ompipe') [try http://www.rsyslog.com/e/2359 ] (at 'restart') Apr 15 09:05:05 anonymous rsyslogd-2007: action 'action 17' suspended, next retry is Tue Apr 15 09:05:35 2014 [try http://www.rsyslog.com/e/2007 ] -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (500, 'testing'), (99, 'unstable'), (59, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.2.0-4-amd64 (SMP w/8 CPU cores) Locale: LANG=C, LC_CTYPE= (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/bash Versions of packages rsyslog depends on: ii init-system-helpers 1.18 ii initscripts 2.88dsf-51 ii libc62.18-4 ii libee0 0.4.1-1 ii libestr0 0.1.9-1 ii libjson-c2 0.11-3 ii liblogging-stdlog0 1.0.4-1 ii liblognorm0 0.3.7-1 ii libuuid1 2.20.1-5.7 ii lsb-base 4.1+Debian12 ii zlib1g 1:1.2.8.dfsg-1 Versions of packages rsyslog recommends: ii logrotate 3.8.7-1 Versions of packages rsyslog suggests: ii rsyslog-doc7.6.3-1 pn rsyslog-gnutls pn rsyslog-gssapi pn rsyslog-mongodb pn rsyslog-mysql | rsyslog-pgsql pn rsyslog-relp -- Configuration Files: /etc/logcheck/ignore.d.server/rsyslog [Errno 13] Permission denied: '/etc/logcheck/ignore.d.server/rsyslog' -- no debconf information Cheers, -- Cristian -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#740117: haveged: spinning
Package: haveged Version: 1.7c-1 Severity: grave Justification: renders package unusable Haveged is just spinning and not comming anywhere :( Been watching it for hours doing that. Uses one CPU at 100%. Upstream version 1.9.0 promisses improvements, although I have no idea if those address the problem I'm reporting. Strace shows it stuck in a select loop: 31623 select(5, NULL, [4], NULL, NULL) = 1 (out [4]) 31623 ioctl(4, RNDGETENTCNT, 0x7fffb745da5c) = 0 31623 ioctl(4, RNDADDENTROPY, 0x14cb720) = 0 31623 select(5, NULL, [4], NULL, NULL) = 1 (out [4]) 31623 ioctl(4, RNDGETENTCNT, 0x7fffb745da5c) = 0 31623 ioctl(4, RNDADDENTROPY, 0x14cb720) = 0 31623 select(5, NULL, [4], NULL, NULL) = 1 (out [4]) 31623 ioctl(4, RNDGETENTCNT, 0x7fffb745da5c) = 0 31623 ioctl(4, RNDADDENTROPY, 0x14cb720) = 0 31623 select(5, NULL, [4], NULL, NULL) = 1 (out [4]) 31623 ioctl(4, RNDGETENTCNT, 0x7fffb745da5c) = 0 31623 ioctl(4, RNDADDENTROPY, 0x14cb720) = 0 31623 select(5, NULL, [4], NULL, NULL) = 1 (out [4]) 31623 ioctl(4, RNDGETENTCNT, 0x7fffb745da5c) = 0 31623 ioctl(4, RNDADDENTROPY, 0x14cb720) = 0 31623 select(5, NULL, [4], NULL, NULL) = 1 (out [4]) -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.13-1-amd64 (SMP w/8 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/dash Versions of packages haveged depends on: ii init-system-helpers 1.17 ii libc62.18-3 ii libhavege1 1.7c-1 ii lsb-base 4.1+Debian12 haveged recommends no packages. haveged suggests no packages. -- Configuration Files: /etc/default/haveged changed: DAEMON_ARGS="-w 4096" -- no debconf information Cheers, -- Cristian -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#737481: tesseract-ocr: dependency problem?
Package: tesseract-ocr Version: 3.03.02-2 Followup-For: Bug #737481 There seems to be a dependency problem here. Attempting to install returns immediately. Noop: # apt-get install tesseract-ocr Reading package lists... Done Building dependency tree Reading state information... Done The following extra packages will be installed: tesseract-ocr 0 upgraded, 0 newly installed, 0 to remove and 12 not upgraded. Shows up when trying to install it using dpkg: # dpkg -i /tmp/tesseract-ocr_3.03.02-2/tesseract-ocr_3.03.02-2_amd64.deb (Reading database ... 514431 files and directories currently installed.) Preparing to unpack .../tesseract-ocr_3.03.02-2_amd64.deb ... Unpacking tesseract-ocr (3.03.02-2) over (3.03.02-1) ... dpkg: dependency problems prevent configuration of tesseract-ocr: tesseract-ocr depends on tesseract-ocr-eng (>= 3.03~); however: Version of tesseract-ocr-eng on system is 3.02-2. dpkg: error processing package tesseract-ocr (--install): dependency problems - leaving unconfigured Processing triggers for man-db (2.6.6-1) ... Errors were encountered while processing: tesseract-ocr # apt-get -f install Reading package lists... Done Building dependency tree Reading state information... Done Correcting dependencies...Starting pkgProblemResolver with broken count: 1 Starting 2 pkgProblemResolver with broken count: 1 Investigating (0) tesseract-ocr [ amd64 ] < 3.03.02-2 > ( graphics ) Broken tesseract-ocr:amd64 Depends on tesseract-ocr-eng [ amd64 ] < 3.02-2 > ( graphics ) (>= 3.03~) Removing tesseract-ocr:amd64 because I can't find tesseract-ocr-eng:amd64 Done Done Starting pkgProblemResolver with broken count: 0 Starting 2 pkgProblemResolver with broken count: 0 Done The following package was automatically installed and is no longer required: tesseract-ocr-eng Use 'apt-get autoremove' to remove it. The following packages will be REMOVED: tesseract-ocr 0 upgraded, 0 newly installed, 1 to remove and 12 not upgraded. 1 not fully installed or removed. After this operation, 82.9 kB disk space will be freed. Do you want to continue? [Y/n] -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.12-1-amd64 (SMP w/8 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/dash Versions of packages tesseract-ocr depends on: ii libc6 2.17-97 ii libgcc11:4.8.2-14 ii liblept4 1.70.1-1 ii libstdc++6 4.8.2-14 ii libtesseract3 3.03.02-2 ii tesseract-ocr-eng 3.02-2 ii tesseract-ocr-equ 3.02-2 ii tesseract-ocr-osd 3.02-2 tesseract-ocr recommends no packages. tesseract-ocr suggests no packages. -- no debconf information Cheers, -- Cristian -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#733149: apt-listbugs: breaks after ruby-locale 2.0.9-1 -> 2.1.0-1 upgrade
On Thu, 26 Dec 2013, Francesco Poli wrote: > > > There are a few more bugs (which render the package unusable, for me) > > listed on the http://bugs.debian.org/apt-listbugs. Notable: 730822, > > Bug #730822 is tagged as "pending": it will be fixed in the next upload > (which will happen as soon as I find a little time to finalize > apt-listbugs version 0.1.12). Sounds good. > In the meanwhile you may manually fix the issue as explained in > http://bugs.debian.org/730822#17 I obviously missed that :( I'll try it in a jiffy... Alright. That seems to work :) Thanks. > > 725672. Another ruby package, ruby-soap4r, is blamed for the 725672 > > trouble. > > Bug #725672 is a ruby-soap4r issue, as you correctly noticed. > Unfortunately, I don't have the time to study ruby-soap4r internals and > investigate the issue in the hope to devise a fix. > Please cooperate with ruby-soap4r maintainers to find a solution, if > you are able to help. Unfortunately, my ruby fu isn't that strong :) > > It's a bit messy situation right now. Any chance of sorting this out > > soon? apt-listbugs is quite useful to me. I'd hate to loose it. > > I can understand, but you should be able to use apt-listbugs itself to > work around the issues: after downgrading ruby-locale to version > 2.0.9-1, you may use apt-listbugs to pin it to that version until this > bug is fixed. Already done something like that. I've put apt-listbugs on hold. > For the two other bugs, please see the above described suggestions. Done. Cheers, -- Cristian -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#733149: apt-listbugs: breaks after ruby-locale 2.0.9-1 -> 2.1.0-1 upgrade
Package: apt-listbugs Version: 0.1.11 Severity: grave Justification: renders package unusable And this is what it reports: /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require': cannot load such file -- locale/util/memoizable (LoadError) from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require' from /usr/lib/ruby/vendor_ruby/gettext/class_info.rb:3:in `' from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require' from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require' from /usr/lib/ruby/vendor_ruby/gettext/text_domain_manager.rb:13:in `' from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require' from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require' from /usr/lib/ruby/vendor_ruby/gettext.rb:19:in `' from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require' from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require' from /usr/sbin/apt-listbugs:294:in `' E: Sub-process /usr/sbin/apt-listbugs apt returned an error code (1) E: Failure running script /usr/sbin/apt-listbugs apt Reverting to ruby-locale 2.0.9-1 makes it work again. ruby-locale could, arguably, be blamed for breaking other packages. I don't know :( There are a few more bugs (which render the package unusable, for me) listed on the http://bugs.debian.org/apt-listbugs. Notable: 730822, 725672. Another ruby package, ruby-soap4r, is blamed for the 725672 trouble. It's a bit messy situation right now. Any chance of sorting this out soon? apt-listbugs is quite useful to me. I'd hate to loose it. -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.11-2-amd64 (SMP w/8 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/dash Versions of packages apt-listbugs depends on: ii apt 0.9.14.1 ii ruby 1:1.9.3 ii ruby-debian 0.3.8+b1 ii ruby-gettext 3.0.2-2 ii ruby-httpclient 2.3.3-2 ii ruby-soap4r 2.0.5-2 ii ruby-xmlparser0.7.2-2 ii ruby1.8 [ruby-interpreter]1.8.7.358-9 ii ruby1.9.1 [ruby-interpreter] 1.9.3.484-1 apt-listbugs recommends no packages. Versions of packages apt-listbugs suggests: ii chimera2 [www-browser] 2.0a19-8 ii chromium [www-browser] 31.0.1650.63-1 ii debianutils 4.4 ii elinks [www-browser]0.12~pre6-4 ii epiphany-browser [www-browser] 3.8.2-5 ii iceweasel [www-browser] 24.2.0esr-1 ii links2 [www-browser]2.8-1+b1 ii lynx-cur [www-browser] 2.8.8pre1-1 ii reportbug 6.4.4 ii w3m [www-browser] 0.5.3-13 -- no debconf information Cheers, -- Cristian -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#654939: mtpfs: broken overnight
On Sat, 22 Dec 2012, Vincent Lefevre wrote: [...] > PTP_ERROR_IO: failed to open session, trying again after resetting USB > interface etc. [...] > But the mtp directory is show as: > > d? ? ? ? ? ? mtp/ > > and "mount" says: > > DeviceFs(GT-N7100) on /home/vinc17/mtp type fuse.DeviceFs(GT-N7100) > (rw,nosuid,nodev,relatime,user_id=0,group_id=0) > > Either "mtpfs" from testing works better than go-mtpfs, or there's > a problem with libmtp from GIT. This points more and more twards libmtp and less and less twards mtpfs. The more reasonable thing would be to move this bug to the libmtp package. What do you think? Cheers, -- Cristian -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#654939: mtpfs: broken overnight
On Sat, 22 Dec 2012, Vincent Lefevre wrote: > On 2012-12-22 11:57:06 +0100, Cristian Ionescu-Idbohrn wrote: > > I get much better results with libmtp9 from experimental: > > libmtp9 from experimental and even upstream libmtp from GIT > don't work either (bug 696513). Different error message(s) or the same as before? On Sat, 22 Dec 2012, Vincent Lefevre wrote: > > With mtpfs 1.1-2 and my Galaxy Note II (N7100): > > # mtpfs -o allow_other /media/mtp > Listing raw device(s) > Device 0 (VID=04e8 and PID=6860) is a Samsung GT > P7310/P7510/N7000/I9070/I9100/I9300 Galaxy Tab 7.7/10.1/S2/S3/Nexus/Note/Y. >Found 1 device(s): >Samsung: GT P7310/P7510/N7000/I9070/I9100/I9300 Galaxy Tab > 7.7/10.1/S2/S3/Nexus/Note/Y (04e8:6860) @ bus 8, dev 8 > Attempting to connect device These messages are typical for libmtp9 <= 1.1.3-35-g0ece104-4: > PTP_ERROR_IO: failed to open session, trying again after resetting USB > interface > LIBMTP libusb: Attempt to reset device > LIBMTP PANIC: failed to open session on second attempt > Unable to open raw device 0 I modified /etc/fuse.conf to: -#user_allow_other +user_allow_other I also added myself to the audio, plugdev, fuse groups. I don't mtp-mount as root, but as myself. Could you run 'mtp-detect' and check the output? I'll send output from mine with private mail, shortly. Cheers, -- Cristian -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#654939: mtpfs: broken overnight
On Sat, 22 Dec 2012, Vincent Lefevre wrote: > With mtpfs 1.1-2 and my Galaxy Note II (N7100): > > # mtpfs -o allow_other /media/mtp > Listing raw device(s) > Device 0 (VID=04e8 and PID=6860) is a Samsung GT > P7310/P7510/N7000/I9070/I9100/I9300 Galaxy Tab 7.7/10.1/S2/S3/Nexus/Note/Y. >Found 1 device(s): >Samsung: GT P7310/P7510/N7000/I9070/I9100/I9300 Galaxy Tab > 7.7/10.1/S2/S3/Nexus/Note/Y (04e8:6860) @ bus 8, dev 8 > Attempting to connect device > PTP_ERROR_IO: failed to open session, trying again after resetting USB > interface > LIBMTP libusb: Attempt to reset device > LIBMTP PANIC: failed to open session on second attempt > Unable to open raw device 0 > > With mtpfs 0.9-3+b1, I don't have such an error, but trying to read > /media freezes for about 3 minutes, then I get: > > ls: cannot access /media/mtp: Transport endpoint is not connected I much better results with libmtp9 from experimental: $ apt-cache policy libmtp9 libmtp9: Installed: 1.1.5-1 Candidate: 1.1.5-1 Package pin: (not found) Version table: *** 1.1.5-1 999 500 http://ftp.se.debian.org/debian/ experimental/main i386 Packages $ mtpfs ~/mtpfs Error: Unable to open ~/.mtpz-data for reading. Listing raw device(s) Device 0 (VID=04e8 and PID=6860) is a Samsung Galaxy models (MTP). Found 1 device(s): Samsung: Galaxy models (MTP) (04e8:6860) @ bus 1, dev 6 Attempting to connect device Listing File Information on Device with name: GT-I8160 The irritating message: Error: Unable to open ~/.mtpz-data for reading. (also, accidentaly? the very 1st line in /lib/udev/rules.d/69-libmtp.rules) does not seem to be an error (info/warning? maybe), as it's just scary and has no ill effects. Maybe this: https://groups.google.com/a/chromium.org/group/chromium-os-reviews/browse_thread/thread/af4ef5613b335f83?noredirect=true catch some interest. Cheers, -- Cristian -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#654939: mtpfs: broken overnight
On Sat, 16 Jun 2012, Andrey Rahmatullin wrote: > On Tue, Mar 06, 2012 at 08:32:55PM +0100, Cristian Ionescu-Idbohrn wrote: > > > > Just stopped working. I could use it yesterday, but not today. > > > > The only thing I can recall, which may or may not be related is an > > > > upgrade of util-linux and mount. > > > > > > > > The command 'mtpfs /media/mountpoint' returns exit status succes. > > > > But 'ls' shows something odd: > > > > > > > > d? ? ?? ?? /media/mountpoint > > > It worked for me with -o allow_other (it seemed to work for root > > > without that option). Also, there is 1.1 available and as my new > > > phone only supports MTP I would be glad to adopt the package. > > > > Great. Got a samsung galaxy tab 10.1. Weird thing, to say the least, > > in the context. I'll gladly help with testing, if needed. > So, does -o allow_ther or accessing with root rights work for you? I've > just checked squeeze and it doesn't work there without allow_other or > root privileges too. I use mtpfs 1.1-2. Yes, it works with '-o allow_other', at least for a while. I can list for example: $ ls -l ~/mtpfs/Tablet/Movies but that shows an empty directory (though there are several files in there). As soon as I attempt to copy a file to ~/mtpfs/Tablet/Movies: kernel: [73790.561899] mtpfs[7775]: segfault at 0 ip 0804c431 sp b6978fa0 error 4 in mtpfs[8048000+7000] kernel: [74449.463714] mtpfs[8090]: segfault at 0 ip 0804c431 sp b69dbfa0 error 4 in mtpfs[8048000+7000] Though, with 'gmtp' copying and listing work as expected. gtmp can even show the contents of Tablet/Movies directory. Cheers, -- Cristian -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#666468: huge performance issues after libcairo2 upgrade with google-chrome-stable and chromium
On Wed, 9 May 2012, Juhani Karlsson wrote: > > After upgrade (Preparing to replace libcairo2:i386 1.10.2-7 (using > .../libcairo2_1.12.2-1_i386.deb) ...) huge performance issues with > google-chrome-stableb and chromium. > > If I open many (like 5) tabs at once from bookmarks, browser gets REALLY slow, > almost crashes. Feels like 10x slower than before upgrade. > Actually asks if I want to close some tabs or wait. Before I could > open easily like 50 tabs with good performance (16GB memory in my system). > > ii chromium 18.0.1025.151~r130497-1 ii > chromium-inspector18.0.1025.151~r130497-1 ii > chromium-l10n 18.0.1025.151~r130497-1 ii > google-chrome-stable 17.0.963.83-r127885 Seen that too (wheezy) :( Switching between tabs takes aages. chromium18.0.1025.151~r130497-1 Not sure about the cause, though. Cheers, -- Cristian -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#663910: distcc: won't install + activate
On Fri, 16 Mar 2012, Daniel Hartwig wrote: > On 16 March 2012 01:43, Cristian Ionescu-Idbohrn > wrote: > > > > Yeah, there was something there [/var/log/distccd.log]: > > > > distccd[20344] (main) ERROR: failed to chdir to /tmp/user/0: Permission > > denied > > The location is read from TMPDIR. > > > That seems to be related to the "per user /tmp directory" recent hack. > > Seems like libpam-tmpdir is causing problems with other programs as > well.[1] > > Note that /etc/init.d/distcc is using start-stop-daemon with '--chuid > distccd'. > > [1] http://bugs.debian.org/656750 Yes, but so do many other daemons. Does libpam-tmpdir break all of them? Doensn't seem so, but I might be wrong. > > Sure thing. Â User 'distccd' has no access to /tmp/user/0. Â It should > > chdir to /tmp/user/129 instead. > > By any chance, were you installing via su? Yes. # echo $TMPDIR /tmp/user/0 Cheers, -- Cristian -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#663910: distcc: won't install + activate
On Thu, 15 Mar 2012, Martin Pool wrote: > > please see if there's a message in the logs. Yeah, there was something there [/var/log/distccd.log]: distccd[20344] (main) ERROR: failed to chdir to /tmp/user/0: Permission denied That seems to be related to the "per user /tmp directory" recent hack. uid=129(distccd) gid=65534(nogroup) groups=65534(nogroup) Sure thing. User 'distccd' has no access to /tmp/user/0. It should chdir to /tmp/user/129 instead. Cheers, -- Cristian -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#663910: distcc: won't install + activate
Package: distcc Version: 3.1-4.2 Severity: grave Justification: renders package unusable update-rc.d: warning: distcc stop runlevel arguments (0 1 6) do not match LSB Default-Stop values (1) Starting Distributed Compiler Daemon: distccd/etc/init.d/distcc: start failed with error code 107 ... (warning). failed! invoke-rc.d: initscript distcc, action "start" failed. dpkg: error processing distcc (--configure): subprocess installed post-installation script returned error exit status 107 configured to not write apport reports Errors were encountered while processing: distcc After modification, postinst shows: + '[' -z 'Starting Distributed Compiler Daemon: distccd' ']' + /bin/echo -n 'Starting Distributed Compiler Daemon: distccd' Starting Distributed Compiler Daemon: distccd+ start-stop-daemon --start --quiet --pidfile /var/run/distccd.pid --chuid distccd --exec /usr/bin/distccd -- --pid-file=/var/run/distccd.pid --log-file=/var/log/distccd.log --daemon --allow 127.0.0.1 --listen 127.0.0.1 --nice 10 --jobs 3 + code=107 + log_warning_msg '/etc/init.d/distcc: start failed with error code 107' -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 3.2.0-2-686-pae (SMP w/2 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/bash Versions of packages distcc depends on: ii adduser3.113+nmu1 ii debconf [debconf-2.0] 1.5.41 ii libavahi-client3 0.6.31-1 ii libavahi-common3 0.6.31-1 ii libc6 2.13-27 ii libpopt0 1.16-3 ii lsb-base 3.2+Debian31 ii netbase4.47 distcc recommends no packages. Versions of packages distcc suggests: ii ccache 3.1.7-1 ii dbus 1.4.18-1 ii distcc-pump ii distccmon-gnome 3.1-4.2cii0 -- debconf information: * distcc/daemon-jobs: 3 * distcc/daemon-allow: 127.0.0.1 * distcc/daemon: true * distcc/daemon-zeroconf: false * distcc/daemon-listen: 127.0.0.1 * distcc/daemon-nice: 10 Cheers, -- Cristian -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#654939: mtpfs: broken overnight
On Tue, 6 Mar 2012, Andrey Rahmatullin wrote: > On Sat, Jan 07, 2012 at 01:49:11AM +0100, Cristian Ionescu-Idbohrn wrote: > > Just stopped working. I could use it yesterday, but not today. > > The only thing I can recall, which may or may not be related is an > > upgrade of util-linux and mount. > > > > The command 'mtpfs /media/mountpoint' returns exit status succes. > > But 'ls' shows something odd: > > > > d? ? ?? ?? /media/mountpoint > It worked for me with -o allow_other (it seemed to work for root without > that option). Also, there is 1.1 available and as my new phone only > supports MTP I would be glad to adopt the package. Great. Got a samsung galaxy tab 10.1. Weird thing, to say the least, in the context. I'll gladly help with testing, if needed. Cheers, -- Cristian -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#653302: closed by Benjamin Drung (xul-ext-adblock-plus: conflicting with iceape iceape-browser mozilla-checky mozilla-tabextensions on my system)
On Thu, 1 Mar 2012, Debian Bug Tracking System wrote: > > This is an automatic notification regarding your Bug report > which was filed against the xul-ext-adblock-plus package: > > #653302: xul-ext-adblock-plus: conflicting with iceape iceape-browser > mozilla-checky mozilla-tabextensions on my system > > It has been closed by Benjamin Drung . Unfortunatelly, new conflicts show up: # apt-get install iceape The following packages will be REMOVED: iceweasel-webdeveloper xul-ext-certificatepatrol xul-ext-perspectives xul-ext-webdeveloper So, I suggest to reopen #653302. Cheers, -- Cristian -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#654939: mtpfs: broken overnight
I must also add that I can (in painful way, but still) do file transfers using gmtp. Cheers, -- Cristian -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#654939: mtpfs: broken overnight
Package: mtpfs Version: 1.0-1 Severity: grave Justification: renders package unusable Just stopped working. I could use it yesterday, but not today. The only thing I can recall, which may or may not be related is an upgrade of util-linux and mount. The command 'mtpfs /media/mountpoint' returns exit status succes. But 'ls' shows something odd: d? ? ?? ?? /media/mountpoint and, of course, the remote file system is not accessible. I can use 'fusermount -u /media/mountpoint' to return things to normal, though. Also, attempted to rebuild the mtpfs package, hoping that compiling against fresher dependencies would return things to a functional state. But no joy :( FTBFS (and a few other warnings too): ... configure: WARNING: unrecognized options: --disable-maintainer-mode ... ERROR: ld.so: object 'libfakeroot-sysv.so' from LD_PRELOAD cannot be preloaded: ignored. ... dh_pysupport: This program is deprecated, you should use dh_python2 instead. Migration guide: http://deb.li/dhs2p ... dpkg-shlibdeps: error: no dependency information found for /lib/libusb-0.1.so.4 (used by debian/mtpfs/usr/bin/mtpfs). dh_shlibdeps: dpkg-shlibdeps -Tdebian/mtpfs.substvars debian/mtpfs/usr/bin/mtpfs returned exit code 2 -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 3.1.0-1-686-pae (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages mtpfs depends on: ii fuse-utils2.8.6-4 ii libc6 2.13-24 ii libfuse2 2.8.6-4 ii libglib2.0-0 2.30.2-4 ii libid3tag00.15.1b-10 ii libmad0 0.15.1b-6 ii libmtp9 1.1.1-1 ii libusb-0.1-4 2:0.1.12-20 ii zlib1g1:1.2.3.4.dfsg-3 mtpfs recommends no packages. mtpfs suggests no packages. -- no debconf information Cheers, -- Cristian -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#653302: xul-ext-adblock-plus: conflicting with iceape iceape-browser mozilla-checky mozilla-tabextensions on my system
I just noticed the reported package version is wrong :( -Version: 1.3.10-3 +Version: 2.0.2-1 The package just migrated to wheezy/testing and the conflicts persist. Cheers, -- Cristian -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#653302: xul-ext-adblock-plus: conflicting with iceape iceape-browser mozilla-checky mozilla-tabextensions on my system
Package: xul-ext-adblock-plus Version: 1.3.10-3 Severity: grave Justification: renders package unusable Is this a real problem or just one of those "defensive programming" idioms? -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 3.1.0-1-686-pae (SMP w/2 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/bash Versions of packages xul-ext-adblock-plus depends on: ii iceape 2.0.14-9 ii icedove3.1.16-1 ii iceweasel 7.0.1-4 xul-ext-adblock-plus recommends no packages. xul-ext-adblock-plus suggests no packages. -- no debconf information Cheers, -- Cristian -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#653289: xul-ext-sage: not compatible with Iceweasel 9.0
Package: xul-ext-sage Version: 1.4.12-2 Severity: grave Justification: renders package unusable Similar to bug #652981 and possibly same solution applies. -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 3.1.0-1-686-pae (SMP w/2 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/bash xul-ext-sage depends on no packages. Versions of packages xul-ext-sage recommends: ii iceweasel 7.0.1-4 xul-ext-sage suggests no packages. -- no debconf information Cheers, -- Cristian -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#629854: conspy: could not open either the alternate device files
On Sat, 17 Dec 2011, Jakub Wilk wrote: > Cristian Ionescu-Idbohrn , 2011-06-08, > 23:52: > > Well... showed up kernel 2.6.39-1-686-pae, AFAICT. > > > > /dev/vcsa0: No such file or directory > > /dev/vcc/a0: No such file or directory > > Could you explain what exactly you did that lead to this situation? > > The only way I could reproduce such message was to run conspy with "0" > as argument. However, this is documented to be wrong: "If supplied, > console must be a number in the range 1 .. 63". Right. That's what I probably did (run 'conspy 0'). Mantainer, please close this bug. User error. Cheers, -- Cristian -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#649378: libsoftokn3.so: cannot open shared object file: Permission denied
You're a bit too quick at closing. I still see the blasted message: [111:111:66151334217:ERROR:nss_util.cc(394)] Error initializing NSS without a persistent database: libsoftokn3.so: cannot open shared object file: Permission denied with: chromium15.0.874.121~r109964-1 libc6 2.13-23 libnss3-1d 3.13.1.with.ckbi.1.88-1 Linux 3.1.0-1-686-pae #1 SMP Sun Dec 11 20:40:16 UTC 2011 i686 No crash, though. Cheers, -- Cristian -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#636251: laptop-mode-tools: Enabling laptop mode.../usr/sbin/laptop_mode: line 1143: return: can only return from a function or sourced script
On Tue, 2 Aug 2011, Ritesh Raj Sarraf wrote: > On 08/02/2011 03:18 PM, Cristian Ionescu-Idbohrn wrote: > > Sad :( > > I suppose you know: > > > > # dpkg-reconfigure dash > > > > provides a mekanism to choose the default shell, but you seem to be > > choosing to ignore that. > Debian defaults to dash. Yes. > With dash, I end up covering most of the users setup. Yes. But really... What is there to win by tying the scripts to either dash, bash or whatever, instead of making the said scripts portable, when the effort to do so is so small? > Don't get me wrong. Time is limited. That's why I asked for your help. I don't think you need my help to 'exit 0' instead of 'return 0'. That's a no-brainer. As I said in a previous post, I don't think it makes much sense to use either at the end of the script. You may want some help to make the scripts POSIX complient, consistent and efficient. That's what I can offer help with, if you're interested. > In the past, I've spent too much time in bash vs dash (mawk vs gawk) > compatibility issues. Right. Here is one simple example of what I've been talking about and, in a way, a compatibility non-issue: , [ usr/share/laptop-mode-tools/module-helpers/lm-polling-daemon ] | while ( true ) ; do | sleep $INTERVAL | | /usr/sbin/laptop_mode auto | done ` Now, what is the point with forking a subshell '( true )' just to execute the (built in most shells) command 'true', when the command ':' is guaranteed built in all POSIX complient shells? -while ( true ) ; do +while :; do This command: /usr/sbin/laptop_mode auto can fail (indefinitely) both in a number of known places: usr/sbin/laptop_mode:250: exit 1 usr/sbin/laptop_mode:533: exit 1 usr/sbin/laptop_mode:538: exit 1 usr/sbin/laptop_mode:561: exit 1 ;; and also not yet known places, I presume. The exit status after execution is not validated. Cheers, -- Cristian -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#636251: laptop-mode-tools: Enabling laptop mode.../usr/sbin/laptop_mode: line 1143: return: can only return from a function or sourced script
On Tue, 2 Aug 2011, Ritesh Raj Sarraf wrote: > On 08/02/2011 01:52 PM, Cristian Ionescu-Idbohrn wrote: > > You obviously did not test with bash. Do you plan to? > Nope. Sad :( I suppose you know: # dpkg-reconfigure dash provides a mekanism to choose the default shell, but you seem to be choosing to ignore that. Cheers, -- Cristian -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#636251: [Bug 815201] Re: /usr/sbin/laptop_mode: line 1143: return: can only `return' from a function or sourced script
On Tue, 2 Aug 2011, Ritesh Raj Sarraf wrote: > On 07/28/2011 04:10 AM, Ritesh Raj Sarraf wrote: > > On 07/28/2011 02:57 AM, Eric Belanger wrote: > >> > That would work but I'm not sure if the shell will interpret > >> > the return value as being for the script rather than for the > >> > function itself. How about replacing 'return 0' by 'exit 0' ? > >> > That seems to be better suited for the situation as we are > >> > exiting the script at that point. And it is accepted by bash. > > Great. Thanks. I'll test it out > I think I'll go with exit 0. Line #1089 in 1.58 laptop-mode script > already did exit 0 gracefully. I just can't get what the magic with that 'exit 0' is, other than fooling the user into thinking everything went just fine. > For now, please use exit 0 and report back if it causes any other > problems. Or just don't use anything. And this is why: http://pubs.opengroup.org/onlinepubs/009695399/utilities/sh.html EXIT STATUS The following exit values shall be returned: ... Otherwise, the shell shall return the exit status of the last command it invoked or attempted to invoke (see also the exit utility in Special Built-In Utilities). Cheers, -- Cristian -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#636251: laptop-mode-tools: Enabling laptop mode.../usr/sbin/laptop_mode: line 1143: return: can only return from a function or sourced script
On Tue, 2 Aug 2011, Ritesh Raj Sarraf wrote: > On 08/02/2011 12:10 AM, Cristian Ionescu-Idbohrn wrote: > > failed (disabled, not active). > > ... > > failed (enabled, not active). > > > > Package promises much, but is (sadly) unusable :( Thus removed. > 22:55:01 rrs@champaran:~/devel/apt-offline/apt-offline (debian)$ sudo > /etc/init.d/laptop-mode restart > [sudo] password for rrs: > Disabling laptop mode...done (8514 disabled, not active). > Enabling laptop mode...done (enabled, not active). > 01:20:27 rrs@champaran:~/devel/apt-offline/apt-offline (debian)$ sudo > /etc/init.d/laptop-mode restart > Disabling laptop mode...done (20610 disabled, not active 20610). > Enabling laptop mode...done (20610 enabled, active 20610). Lucky you :) > > Now, it's essential scripting stuff. You just don't do: > > > > return 0; > > > > Maybe: > > > > exit 0 > > > > which would mean "ignore all errors that may have occured", but how > > smart would that be? > Exactly. Can you test and report this? I don't need to test that. It's pretty basic. > > Just skip that all together and handle errors as they may occur, > > instead. That would be smarter, indeed. > This would be better. I haven't tested what the default return is. > If you can test, that'll be great. With the new 1.58 release, the > last snippet in the laptop_mode script is the lm-polling-daemon > invocation. Now its exit status could be different depending on the > various circumstances (number of events, invocations etc). So you > testing will help here. Alright. I'll try something tonight. > > That script is in a deplorable hackish state :( I doubt _all_ > > those forked subshells '(...)' are really necessary, for example. > > Would you be intrested in getting patches? Is there a debian > > repository you keep the code in? > Yes. https://github.com/rickysarraf/laptop-mode-tools Thanks. That would be: $ git clone git://github.com/rickysarraf/laptop-mode-tools.git wouldn't it? > > Kernel: Linux 2.6.39-2-686-pae (SMP w/2 CPU cores) > > Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) > > Shell: /bin/sh linked to /bin/bash > Debian defaults to dash. And that is what laptop-mode-tools tries to > adhere to. Well, you'll have to adhere to whatever "the best of both worlds" may be, and it will "just work" (tm). > But that doesn't mean it shouldn't work with bash. That would be my point too. > Can you try with dash as your system default shell? I'll see what I can do. You obviously did not test with bash. Do you plan to? Cheers, -- Cristian -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#636251: laptop-mode-tools: Enabling laptop mode.../usr/sbin/laptop_mode: line 1143: return: can only `return' from a function or sourced script
Package: laptop-mode-tools Version: 1.58-2 Severity: grave failed (disabled, not active). ... failed (enabled, not active). Package promises much, but is (sadly) unusable :( Thus removed. Now, it's essential scripting stuff. You just don't do: return 0; Maybe: exit 0 which would mean "ignore all errors that may have occured", but how smart would that be? Just skip that all together and handle errors as they may occur, instead. That would be smarter, indeed. That script is in a deplorable hackish state :( I doubt _all_ those forked subshells '(...)' are really necessary, for example. Would you be intrested in getting patches? Is there a debian repository you keep the code in? -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.39-2-686-pae (SMP w/2 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/bash Versions of packages laptop-mode-tools depends on: ii lsb-base 3.2-27 Linux Standard Base 3.2 init scrip ii psmisc22.14-1utilities that use the proc file s ii util-linux2.19.1-4 Miscellaneous system utilities Versions of packages laptop-mode-tools recommends: ii acpid 1:2.0.10-1 Advanced Configuration and Power I ii ethtool 1:2.6.39-1 display or change Ethernet device ii hal 0.5.14-6 Hardware Abstraction Layer ii hdparm9.32-1 tune hard disk parameters for high ii net-tools 1.60-24.1 The NET-3 networking toolkit ii sdparm1.06-3 Output and modify SCSI device para ii udev 172-1 /dev/ and hotplug management daemo ii wireless-tools30~pre9-5 Tools for manipulating Linux Wirel laptop-mode-tools suggests no packages. -- no debconf information Cheers, -- Cristian -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#629854: conspy: could not open either the alternate device files
Package: conspy Version: 1.8-1 Justification: renders package unusable Severity: grave Well... showed up kernel 2.6.39-1-686-pae, AFAICT. /dev/vcsa0: No such file or directory /dev/vcc/a0: No such file or directory AFAIR, worked with 2.6.38. -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.39-1-686-pae (SMP w/2 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/bash Versions of packages conspy depends on: ii libc6 2.13-4 Embedded GNU C Library: Shared lib ii libncurses5 5.9-1 shared libraries for terminal hand conspy recommends no packages. conspy suggests no packages. -- no debconf information Cheers, -- Cristian -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#553380: nano-tiny: trying to overwrite '/usr/share/nano/man-html/nanorc.5.html'
Package: nano-tiny Version: 2.0.9-2 Justification: renders package unusable Severity: grave trying to overwrite '/usr/share/nano/man-html/nanorc.5.html', which is also in package nano 0:2.1.11-2 -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.30-2-686 (SMP w/2 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/bash Versions of packages nano-tiny depends on: ii libc6 2.10.1-3 GNU C Library: Shared libraries ii libslang2 2.2.1-1The S-Lang programming library - r nano-tiny recommends no packages. nano-tiny suggests no packages. -- no debconf information Cheers, -- Cristian -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#548381: epiphany-browser: update-alternatives: error: no alternatives for epiphany-browser
Package: epiphany-browser Version: 2.28.0-2 Justification: renders package unusable Severity: grave dpkg: error processing /var/cache/apt/archives/epiphany-browser_2.28.0-2_i386.deb (--unpack): subprocess new pre-installation script returned error exit status 2 -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.30-1-686 (SMP w/2 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/bash Versions of packages epiphany-browser depends on: ii dbus-x111.2.16-2 simple interprocess messaging syst ii epiphany-browser-data 2.28.0-3 Data files for the GNOME web brows ii gnome-icon-theme2.26.0-1 GNOME Desktop icon theme ii iso-codes 3.10.3-1 ISO language, territory, currency, ii libavahi-client30.6.25-1 Avahi client library ii libavahi-common30.6.25-1 Avahi common library ii libavahi-gobject0 0.6.25-1 Avahi GObject library ii libc6 2.9-26 GNU C Library: Shared libraries ii libdbus-1-3 1.2.16-2 simple interprocess messaging syst ii libdbus-glib-1-20.82-1 simple interprocess messaging syst ii libgconf2-4 2.26.2-3 GNOME configuration database syste ii libgirepository1.0-00.6.5-1 Library for handling GObject intro ii libglib2.0-02.22.0-1 The GLib library of C routines ii libgnome-keyring0 2.26.1-1 GNOME keyring services library ii libgtk2.0-0 2.18.0-1 The GTK+ graphical user interface ii libice6 2:1.0.5-1X11 Inter-Client Exchange library ii libnotify1 [libnotify1-gtk2 0.4.5-1 sends desktop notifications to a n ii libnspr4-0d 4.8-1NetScape Portable Runtime Library ii libnss3-1d 3.12.3.1-1 Network Security Service libraries ii libpango1.0-0 1.26.0-1 Layout and rendering of internatio ii libseed02.28.0-1 GObject JavaScript bindings for th ii libsm6 2:1.1.1-1X11 Session Management library ii libsoup-gnome2.4-1 2.28.0-1 an HTTP library implementation in ii libsoup2.4-12.28.0-1 an HTTP library implementation in ii libwebkit-1.0-2 1.1.15.1-1 Web content engine library for Gtk ii libx11-62:1.2.2-1X11 client-side library ii libxml2 2.7.4.dfsg-2 GNOME XML library ii libxslt1.1 1.1.24-2 XSLT processing library - runtime Versions of packages epiphany-browser recommends: pn yelp (no description available) Versions of packages epiphany-browser suggests: ii mozplugger1.12.1-2 Plugin allowing external viewers t -- no debconf information Cheers, -- Cristian -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#528028: BUG: Bad page state in process md?_resync pfn:
Package: linux-image-2.6.29-1-686 Version: 2.6.29-3 Justification: breaks the whole system Severity: critical I wonder if this is the same thing Neil Brown refers to, here: http://www.spinics.net/lists/raid/msg23053.html The syslog shows first 97 of these: , | May 10 02:10:05 kernel: [107468.160593] BUG: Bad page state in process md9_resync pfn:36243 | May 10 02:10:05 kernel: [107468.160602] page:c16c4860 flags:4000 count:-1 mapcount:0 mapping:(null) index:24 | May 10 02:10:05 kernel: [107468.160610] Pid: 31239, comm: md9_resync Tainted: PB 2.6.29-1-686 #1 | May 10 02:10:05 kernel: [107468.160614] Call Trace: | May 10 02:10:05 kernel: [107468.160626] [] bad_page+0xc6/0xda | May 10 02:10:05 kernel: [107468.160633] [] get_page_from_freelist+0x31b/0x3f3 | May 10 02:10:05 kernel: [107468.160641] [] __alloc_pages_internal+0x98/0x398 | May 10 02:10:05 kernel: [107468.160676] [] r1buf_pool_alloc+0x8f/0x164 [raid1] | May 10 02:10:05 kernel: [107468.160684] [] mempool_alloc+0x27/0xcb | May 10 02:10:05 kernel: [107468.160691] [] bio_add_page+0x28/0x2e | May 10 02:10:05 kernel: [107468.160707] [] sync_request+0x1fd/0x5ee [raid1] | May 10 02:10:05 kernel: [107468.160739] [] md_do_sync+0x6d4/0xb60 [md_mod] | May 10 02:10:05 kernel: [107468.160753] [] autoremove_wake_function+0x0/0x2d | May 10 02:10:05 kernel: [107468.160775] [] md_thread+0xdd/0xf4 [md_mod] | May 10 02:10:05 kernel: [107468.160796] [] md_thread+0x0/0xf4 [md_mod] | May 10 02:10:05 kernel: [107468.160803] [] kthread+0x38/0x5d | May 10 02:10:05 kernel: [107468.160808] [] kthread+0x0/0x5d | May 10 02:10:05 kernel: [107468.160815] [] kernel_thread_helper+0x7/0x10 ` and then continues and alternates with 81 of these: , | May 10 02:10:14 kernel: [107477.308920] BUG: Bad page state in process find pfn:04322 | May 10 02:10:14 kernel: [107477.308928] page:c1086440 flags:4000 count:-1 mapcount:0 mapping:(null) index:1 | May 10 02:10:14 kernel: [107477.308933] Pid: 32146, comm: find Tainted: P B 2.6.29-1-686 #1 | May 10 02:10:14 kernel: [107477.308937] Call Trace: | May 10 02:10:14 kernel: [107477.308946] [] bad_page+0xc6/0xda | May 10 02:10:14 kernel: [107477.308952] [] get_page_from_freelist+0x31b/0x3f3 | May 10 02:10:14 kernel: [107477.308957] [] __alloc_pages_internal+0x98/0x398 | May 10 02:10:14 kernel: [107477.308962] [] find_or_create_page+0x3e/0x76 | May 10 02:10:14 kernel: [107477.308968] [] __getblk+0x137/0x2df | May 10 02:10:14 kernel: [107477.308973] [] ll_rw_block+0xb5/0xc6 | May 10 02:10:14 kernel: [107477.309013] [] search_by_key+0x69/0x560 [reiserfs] | May 10 02:10:14 kernel: [107477.309036] [] search_by_key+0x454/0x560 [reiserfs] | May 10 02:10:14 kernel: [107477.309042] [] __find_get_block+0x168/0x172 | May 10 02:10:14 kernel: [107477.309047] [] __alloc_pages_internal+0x98/0x398 | May 10 02:10:14 kernel: [107477.309052] [] __getblk+0x27/0x2df | May 10 02:10:14 kernel: [107477.309073] [] reiserfs_read_locked_inode+0x64/0x50e [reiserfs] | May 10 02:10:14 kernel: [107477.309093] [] search_by_entry_key+0x14/0x184 [reiserfs] | May 10 02:10:14 kernel: [107477.309114] [] make_cpu_key+0x1c/0x38 [reiserfs] | May 10 02:10:14 kernel: [107477.309134] [] reiserfs_init_locked_inode+0x0/0xe [reiserfs] | May 10 02:10:14 kernel: [107477.309154] [] reiserfs_iget+0x47/0x78 [reiserfs] | May 10 02:10:14 kernel: [107477.309173] [] reiserfs_lookup+0xa7/0xf6 [reiserfs] | May 10 02:10:14 kernel: [107477.309188] [] do_lookup+0xa6/0x116 | May 10 02:10:14 kernel: [107477.309193] [] __link_path_walk+0x523/0x630 | May 10 02:10:14 kernel: [107477.309198] [] mntput_no_expire+0x1a/0xfe | May 10 02:10:14 kernel: [107477.309203] [] dput+0x1a/0x108 | May 10 02:10:14 kernel: [107477.309207] [] path_walk+0x4f/0xa3 | May 10 02:10:14 kernel: [107477.309212] [] do_path_lookup+0x132/0x178 | May 10 02:10:14 kernel: [107477.309216] [] getname+0x5e/0xb0 | May 10 02:10:14 kernel: [107477.309221] [] user_path_at+0x37/0x5f | May 10 02:10:14 kernel: [107477.309227] [] vfs_lstat_fd+0x12/0x38 | May 10 02:10:14 kernel: [107477.309231] [] sys_fstatat64+0x28/0x48 | May 10 02:10:14 kernel: [107477.309237] [] sysenter_do_call+0x12/0x2f ` Continues with 151 of these: , | May 10 02:20:35 kernel: [108097.888004] BUG: soft lockup - CPU#0 stuck for 61s! [pdflush:28304] | May 10 02:20:35 kernel: [108097.888004] Modules linked in: iptable_nat nf_nat iptable_mangle ebtable_filter ebtables hid_gaff hid_pl hid_cypress hid_zpff hid_gyration hid_sony hid_ntrig hid_samsung hid_microsoft hid_tmff hid_monterey hid_ezkey hid_apple hid_a4tech hid_logitech ff_memless hid_cherry hid_sunplus hid_petalynx hid_belkin hid_chicony usbhid hid nvidia(P) xt_multiport binfmt_misc ppdev parport_pc lp parport ipt_ULOG inet_diag acpi_cpufreq cpufreq_powersave cpufreq_stats cpufreq_userspace cpufreq_conservative nf_conntrack_ftp nf_conntrack_irc ipt_LOG xt_limit xt_tcpudp ipt_REJECT xt_stat
Bug#487719: alsamixer: function snd_ctl_open failed for default: No such file or directory
Package: alsa-utils Version: 1.0.16-1 Severity: grave Justification: renders package unusable What about this: # alsamixer alsamixer: function snd_ctl_open failed for default: No such file or directory It worked perfectly well yesterday, before I upgrades these packages: 2008-06-22 13:12:20 upgrade apache2-utils 2.2.9-1 2.2.9-2 2008-06-22 13:12:22 upgrade apache2-mpm-prefork 2.2.9-1 2.2.9-2 2008-06-22 13:12:25 upgrade apache2.2-common 2.2.9-1 2.2.9-2 2008-06-22 13:12:27 upgrade apache2 2.2.9-1 2.2.9-2 2008-06-22 13:12:27 upgrade apache2-doc 2.2.9-1 2.2.9-2 2008-06-22 13:15:47 upgrade apt-cross 0.9.1 0.9.2 2008-06-22 13:15:48 upgrade libcache-apt-perl 0.9.1 0.9.2 2008-06-22 13:15:48 upgrade emdebian-archive-keyring 1.2.0 1.2.1 2008-06-22 13:16:51 upgrade bochs-x 2.3.6-4 2.3.6-5 2008-06-22 13:16:51 upgrade bochs-wx 2.3.6-4 2.3.6-5 2008-06-22 13:16:51 upgrade bochs-term 2.3.6-4 2.3.6-5 2008-06-22 13:16:51 upgrade bochs 2.3.6-4 2.3.6-5 2008-06-22 13:16:52 upgrade bochsbios 2.3.6-4 2.3.6-5 2008-06-22 13:16:52 upgrade bochs-doc 2.3.6-4 2.3.6-5 2008-06-22 13:16:53 upgrade bximage 2.3.6-4 2.3.6-5 2008-06-22 13:19:46 upgrade cups-pdf 2.4.7-3 2.4.7-4 2008-06-22 13:19:47 upgrade bash-completion 20060301-4 20080617.1 2008-06-22 13:19:47 upgrade arj 3.10.22-5 3.10.22-6 2008-06-22 13:19:47 upgrade console-data 2:1.07-3 2:1.07-4 2008-06-22 13:19:49 upgrade debian-reference-en 2.03 2.04 2008-06-22 13:19:49 upgrade debian-reference-common 2.03 2.04 2008-06-22 13:19:49 upgrade oneko 1.2.sakura.6-4 1.2.sakura.6-5 2008-06-22 13:22:27 upgrade aptitude 0.4.11.4-1 0.4.11.6-1 2008-06-22 13:22:29 upgrade acpid 1.0.6-9 1.0.6-10 2008-06-22 13:26:31 upgrade darkstat 3.0.707-2 3.0.708-1 2008-06-22 13:26:31 upgrade elinks 0.11.3-8 0.11.4-1 2008-06-22 13:26:32 upgrade elinks-data 0.11.3-8 0.11.4-1 2008-06-22 13:26:32 upgrade fbset 2.1-22 2.1-23 2008-06-22 13:26:32 upgrade librsync1 0.9.7-2 0.9.7-3 2008-06-22 13:26:32 upgrade libsvga1-dev 1:1.4.3-26 1:1.4.3-27 2008-06-22 13:26:37 upgrade libsvga1 1:1.4.3-26 1:1.4.3-27 2008-06-22 13:26:37 upgrade mysql-common 5.0.51a-7 5.0.51a-8 2008-06-22 13:26:37 upgrade numlockx 1.1-7 1.1-8 2008-06-22 13:26:37 upgrade p7zip-full 4.57~dfsg.1-1 4.58~dfsg.1-1 2008-06-22 13:26:38 upgrade parted-doc 1.7.1-5.1 1.8.8.git.2008.03.24-7 2008-06-22 13:26:38 upgrade svgalibg1 1:1.4.3-26 1:1.4.3-27 2008-06-22 13:28:41 upgrade traceroute 2.0.11-1 2.0.11-2 2008-06-22 13:28:44 upgrade python-ipy 1:0.60-1 1:0.61-1 2008-06-22 13:28:44 upgrade ttf-liberation 1.0-0.1 1.04~beta2-2 2008-06-22 13:28:44 upgrade xfstt 1.7-4 1.7-5 2008-06-22 13:31:57 upgrade cdcd 0.6.6-7 0.6.6-8 2008-06-22 13:31:57 upgrade cpulimit 1.1-10 1.1-11 2008-06-22 13:31:57 upgrade findimagedupes 2.7-3 2.11-1 2008-06-22 13:31:57 upgrade libaprutil1 1.2.12+dfsg-6 1.2.12+dfsg-7 2008-06-22 13:35:48 upgrade libcairo-perl 1.053-1+b1 1.060-1 2008-06-22 13:35:49 upgrade libconfig-general-perl 2.39-1 2.40-1 2008-06-22 13:35:49 upgrade libglib-perl 1:1.181-1+b1 1:1.183-1 2008-06-22 13:35:49 upgrade libgtk2-perl 1:1.181-1+b1 1:1.183-1 2008-06-22 13:35:50 upgrade ppmd 9.1-14 9.1-15 2008-06-22 13:37:12 upgrade sysklogd 1.5-4 1.5-5 2008-06-22 13:37:12 upgrade klogd 1.5-4 1.5-5 2008-06-22 13:37:13 upgrade netcat 1.10-37 1.10-38 2008-06-22 15:14:28 upgrade wmavgload 0.7.0-8 0.7.0-8cii0 2008-06-23 18:41:07 upgrade perl-modules 5.10.0-10 5.10.0-11 2008-06-23 18:41:15 upgrade perl-suid 5.10.0-10 5.10.0-11 2008-06-23 18:41:15 upgrade libperl5.10 5.10.0-10 5.10.0-11 2008-06-23 18:41:16 upgrade perl 5.10.0-10 5.10.0-11 2008-06-23 18:41:21 upgrade perl-base 5.10.0-10 5.10.0-11 2008-06-23 18:41:33 upgrade perl-doc 5.10.0-10 5.10.0-11 2008-06-23 18:41:48 upgrade xulrunner-1.9 1.9~rc2-3 1.9~rc2-4 2008-06-23 18:41:55 upgrade emdebian-tools 1.2.0 1.2.2 2008-06-23 18:41:56 upgrade emdebian-rootfs 1.2.0 1.2.2 2008-06-23 18:41:56 upgrade libemdebian-tools-perl 1.2.0 1.2.2 2008-06-23 18:45:24 upgrade libdevmapper1.02.1 2:1.02.25-1 2:1.02.26-1 2008-06-23 18:45:28 upgrade arping 2.05-2 2.07~pre1-1 2008-06-23 18:45:29 upgrade dmsetup 2:1.02.25-1 2:1.02.26-1 2008-06-23 18:45:29 upgrade libmozjs1d 1.9~rc2-3 1.9~rc2-4 2008-06-23 18:45:29 upgrade mozilla-noscript 1.6-1 1.6.9.3-1 2008-06-23 18:45:30 upgrade numlockx 1.1-8 1.1-9 2008-06-23 18:50:11 upgrade mpg123 0.67-1 1.4.3-2 2008-06-23 18:52:37 upgrade libfaad-dev 2.6.1-2 2.6.1-3 2008-06-23 18:52:37 upgrade libfaad0 2.6.1-2 2.6.1-3 2008-06-23 18:52:38 upgrade libgii1 1:1.0.2-1 1:1.0.2-2 2008-06-23 18:52:38 upgrade libgii1-target-x 1:1.0.2-1 1:1.0.2-2 2008-06-23 18:54:01 upgrade cups-pdf 2.4.7-4 2.4.8-1 2008-06-23 18:54:01 upgrade python-support 0.8.1 0.8.2 2008-06-23 18:54:02 upgrade atool 0.35.0-1 0.35.0-3 2008-06-23 18:54:02 upgrade gqview 2.0.4-2 2.0.4-3 2008-06-23 18:54:04 upgrade libadns1 1.4-0.1 1.4-1 2008-06-23 18:54:04 upgrade libbluetooth2 3.30-1 3.33-1 2008-06-23 18:54:06 upgrade libhdf4g 4.1r4-21.1 4.1r4-22 2008-06-23 18:54:06 upgrade libkpathsea4 2007.dfsg.1-4 2007.dfsg.2-1 2008-06-23 18:54:07 upgrade xchat 2.8.4-2+b1 2.8.6
Bug#456791: sawfish: unable to determine description for dir entry - giving up
Package: sawfish Version: 1:1.3.1-2 Severity: grave Justification: renders package unusable Setting up sawfish (1:1.3.1-2) ... install-info(/usr/share/info/sawfish.info): warning, ignoring confusing INFO-DIR-ENTRY in file. No `START-INFO-DIR-ENTRY' and no `This file documents'. install-info(/usr/share/info/sawfish.info): unable to determine description for `dir' entry - giving up dpkg: error processing sawfish (--configure): subprocess post-installation script returned error exit status 1 Cheers, -- Cristian -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.22-3-686 (SMP w/2 CPU cores) Locale: LANG=C, LC_CTYPE= (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/bash Versions of packages sawfish depends on: ii aterm [x-terminal-emu 1.0.1-2Afterstep XVT - a VT102 emulator f ii eterm [x-terminal-emu 0.9.4.0debian1-2 Enlightened Terminal Emulator ii gnome-terminal [x-ter 2.18.3-1 The GNOME 2 terminal emulator appl ii kterm [x-terminal-emu 6.2.0-46 Multi-lingual terminal emulator fo ii libatk1.0-0 1.20.0-1 The ATK accessibility toolkit ii libaudiofile0 0.2.6-7Open-source version of SGI's audio ii libc6 2.7-4 GNU C Library: Shared libraries ii libcairo2 1.4.12-1 The Cairo 2D vector graphics libra ii libesd0 0.2.36-3 Enlightened Sound Daemon - Shared ii libfontconfig12.5.0-2generic font configuration library ii libglib2.0-0 2.14.4-2 The GLib library of C routines ii libgmp3c2 2:4.2.2+dfsg-1 Multiprecision arithmetic library ii libgtk2.0-0 2.12.3-2 The GTK+ graphical user interface ii libice6 2:1.0.4-1 X11 Inter-Client Exchange library ii libpango1.0-0 1.18.3-1 Layout and rendering of internatio ii librep9 0.17+svn20071210-1 lisp command interpreter ii libsm62:1.0.3-1+b1 X11 Session Management library ii libx11-6 2:1.0.3-7 X11 client-side library ii libxcursor1 1:1.1.9-1 X cursor management library ii libxext6 1:1.0.3-2 X11 miscellaneous extension librar ii libxfixes31:4.0.3-2 X11 miscellaneous 'fixes' extensio ii libxft2 2.1.12-2 FreeType-based font drawing librar ii libxi62:1.1.3-1 X11 Input extension library ii libxinerama1 1:1.0.2-1 X11 Xinerama extension library ii libxrandr22:1.2.2-1 X11 RandR extension library ii libxrender1 1:0.9.4-1 X Rendering Extension client libra ii pterm [x-terminal-emu 0.60-2 PuTTY terminal emulator ii rep-gtk 0.18.cvs20060518-3 GTK binding for librep ii rxvt [x-terminal-emul 1:2.6.4-12 VT102 terminal emulator for the X ii sawfish-data 1:1.3.1-1 sawfish architecture independent d ii xterm [x-terminal-emu 229-1 X terminal emulator ii xvt [x-terminal-emula 2.1-20 X terminal-emulator similar to xte sawfish recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#437020: Bug#437163: Acknowledgement (fails with W: Mandatory parameter bug missing in call)
Please merge the 2 bugs. Something must have happened 'elsewhere' :) I no longer see the: Error retrieving bug reports from the server with the following error message: W: Mandatory parameter 'bug' missing in call to Debbugs::Status::get_bug_status at /usr/local/lib/site_perl/Debbugs/SOAP.pm line 114 Still, that error message is _very_ confusing. There nothing on my boxes called 'Debbugs'. And we all know packages should _never_ install stuff under /usr/local. A proper error message (giving more hope) would be preferred :) Cheers, -- Cristian -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#366843: apache: same problem here...
Followup-For: Bug #366843
Package: apache
Version: 1.3.34-3
...but with the latest unstable package. here is some info:
,
| ...
| + '[' '!' /var/www ']'
| + '[' apache '!=' apache-ssl ']'
| + '[' '!' 80 ']'
| + '[' '!' localhost ']'
| + db_set apache/server-name localhost
| + _db_cmd 'SET apache/server-name' localhost
| + printf '%s\n' 'SET apache/server-namelocalhost'
| + IFS='
| '
| + read -r _db_internal_line
| + RET='10 apache/server-namelocalhost doesn'\''t exist'
| + case ${_db_internal_line%%[ ]*} in
| + return 10
| dpkg: error processing apache (--configure):
| subprocess post-installation script returned error exit status 10
| Errors were encountered while processing:
| apache
| E: Sub-process /usr/bin/dpkg returned an error code (1)
`
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'stable')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.16
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Versions of packages apache depends on:
pn apache-common (no description available)
ii debconf [debconf-2.0] 1.5.3 Debian configuration management sy
ii libc6 2.3.6-19 GNU C Library: Shared libraries
ii libdb4.4 4.4.20-7 Berkeley v4.4 Database Libraries [
ii libexpat1 1.95.8-3.2 XML parsing C library - runtime li
ii libmagic1 4.17-3 File type determination library us
ii logrotate 3.7.1-3Log rotation utility
ii lsb-base 3.1-14 Linux Standard Base 3.1 init scrip
ii mime-support 3.37-1 MIME files 'mime.types' & 'mailcap
ii perl 5.8.8-6.1 Larry Wall's Practical Extraction
apache recommends no packages.
-- no debconf information
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#351549: nvidia-kernel-source: the infamous NVRM: Xid: bugs
Package: nvidia-kernel-source Version: 1.0.8178-1 Severity: critical Justification: breaks unrelated software A lot of patches, no usable solution yet :( These links: http://www.nvnews.net/vbulletin/showthread.php?t=62021 http://www.nvnews.net/vbulletin/showthread.php?s=08d64620617098c50061c4c4711d\ 2e88&t=64205 might shed some light. Still the only working solution I found is: back to the nv driver. No acceleration :( but rock solid. I experience the same problems with the '-legacy' package. Same bad behaviour with the 2.6.15- packages :( /Cristian -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.14-2-686-smp Locale: LANG=C, LC_CTYPE= (charmap=ANSI_X3.4-1968) Versions of packages nvidia-kernel-source depends on: ii debhelper 5.0.22 helper programs for debian/rules ii dpatch2.0.17 patch maintenance system for Debia hi make 3.80-12The GNU version of the "make" util ii sed 4.1.4-5The GNU sed stream editor Versions of packages nvidia-kernel-source recommends: ii devscripts2.9.11 Scripts to make the life of a Debi ii kernel-package10.033 A utility for building Linux kerne ii nvidia-glx1.0.8178-1 NVIDIA binary XFree86 4.x driver -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#324473: mozilla-firefox: 1.0.4-2sarge2 segfaults at startup
Package: mozilla-firefox Version: 1.0.4-2sarge2 Severity: grave Justification: renders package unusable See the attached backtrace. Some extention(s) seem to cause the segfault. If I move the ~/.mozilla directory away, firefox asks me to configure the tab-extension and then starts. But as soon as I try to make it display the sidebar, it segfaults again. Going back to 1.0.4-2sarge1 solves my problem. Cheers, Cristian -- System Information: Debian Release: 3.1 APT prefers testing APT policy: (100, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.10-1-686-smp Locale: LANG=en_US, LC_CTYPE= (charmap=ISO-8859-1) Versions of packages mozilla-firefox depends on: ii debianutils2.8.4 Miscellaneous utilities specific t ii fontconfig 2.3.1-2 generic font configuration library ii libatk1.0-01.8.0-4 The ATK accessibility toolkit ii libc6 2.3.2.ds1-22 GNU C Library: Shared libraries an ii libfontconfig1 2.3.1-2 generic font configuration library ii libfreetype6 2.1.7-2.4 FreeType 2 font engine, shared lib ii libgcc11:3.4.3-13GCC support library ii libglib2.0-0 2.6.4-1 The GLib library of C routines ii libgtk2.0-02.6.4-3 The GTK+ graphical user interface ii libidl00.8.5-1 library for parsing CORBA IDL file ii libjpeg62 6b-10 The Independent JPEG Group's JPEG ii libkrb53 1.3.6-2sarge2 MIT Kerberos runtime libraries ii libpango1.0-0 1.8.1-1 Layout and rendering of internatio ii libpng12-0 1.2.8rel-1PNG library - runtime ii libstdc++5 1:3.3.5-13The GNU Standard C++ Library v3 ii libx11-6 4.3.0.dfsg.1-14 X Window System protocol client li ii libxext6 4.3.0.dfsg.1-14 X Window System miscellaneous exte ii libxft22.1.7-1 FreeType-based font drawing librar ii libxp6 4.3.0.dfsg.1-14 X Window System printing extension ii libxt6 4.3.0.dfsg.1-14 X Toolkit Intrinsics ii psmisc 21.5-1Utilities that use the proc filesy ii xlibs 4.3.0.dfsg.1-14 X Keyboard Extension (XKB) configu ii zlib1g 1:1.2.2-4.sarge.2 compression library - runtime -- no debconf informationProgram received signal SIGSEGV, Segmentation fault. [Switching to Thread -1220925344 (LWP 19359)] 0xb7f79022 in JS_GetClass () from /usr/lib/mozilla-firefox/libmozjs.so (gdb) bt #0 0xb7f79022 in JS_GetClass () from /usr/lib/mozilla-firefox/libmozjs.so #1 0x08463a54 in nsScriptSecurityManager::CheckObjectAccess () #2 0xb7f998a8 in js_ErrorFromException () from /usr/lib/mozilla-firefox/libmozjs.so #3 0xb7f9a7a1 in js_ErrorToException () from /usr/lib/mozilla-firefox/libmozjs.so #4 0xb7f839a0 in js_ContextIterator () from /usr/lib/mozilla-firefox/libmozjs.so #5 0xb7f84109 in js_ReportErrorNumberVA () from /usr/lib/mozilla-firefox/libmozjs.so #6 0xb7f7d66a in JS_ReportErrorNumber () from /usr/lib/mozilla-firefox/libmozjs.so #7 0xb7fa6025 in js_Interpret () from /usr/lib/mozilla-firefox/libmozjs.so #8 0xb7fa1617 in js_Invoke () from /usr/lib/mozilla-firefox/libmozjs.so #9 0x0836d5be in nsXPCWrappedJSClass::CheckForException () #10 0x0836af8b in nsXPCWrappedJS::FindInherited () #11 0xb7f46743 in XPTC_InvokeByIndex () from /usr/lib/mozilla-firefox/libxpcom.so #12 0x0869fb07 in nsEventListenerManager::HandleEventSubType () #13 0x0869ffaa in nsEventListenerManager::HandleEventSubType () #14 0x087a7a31 in nsXULElement::HandleDOMEvent () #15 0x086ab91a in nsEventStateManager::ForceViewUpdate () #16 0x086a0755 in nsEventListenerManager::GetDOM2EventGroup () #17 0x0865550c in nsDOMEventRTTearoff::GetDOM3EventTarget () #18 0xb7f465e5 in XPTC_InvokeByIndex () from /usr/lib/mozilla-firefox/libxpcom.so #19 0x083721de in XPCWrappedNative::CallMethod () #20 0x08379701 in XPC_WN_CallMethod () #21 0xb7fa1546 in js_Invoke () from /usr/lib/mozilla-firefox/libmozjs.so #22 0xb7fab5c9 in js_Interpret () from /usr/lib/mozilla-firefox/libmozjs.so #23 0xb7fa1617 in js_Invoke () from /usr/lib/mozilla-firefox/libmozjs.so #24 0x0836d5be in nsXPCWrappedJSClass::CheckForException () #25 0x0836af8b in nsXPCWrappedJS::FindInherited () #26 0xb7f46743 in XPTC_InvokeByIndex () from /usr/lib/mozilla-firefox/libxpcom.so #27 0x08ad7dfd in nsBrowserStatusFilter::~nsBrowserStatusFilter () #28 0x0890ec1e in nsDocLoaderImpl::FireOnStateChange () #29 0x0890e2a8 in nsDocLoaderImpl::doStopDocumentLoad () #30 0x0890e151 in nsDocLoaderImpl::DocLoaderIsEmpty () #31 0x0890ded8 in nsDocLoaderImpl::~nsDocLoaderImpl () #32 0x083cc15e in nsLoadGroup::Create () #33 0x083cbc19 in nsLoadGroup::Create () #34 0x0890d9de in nsDocLoaderImpl::~nsDocLoaderImpl () #35 0x0890ca31 in nsURILoader::~nsURILoad
Bug#311983: libflash-mozplugin: a couple of segfaults
Package: libflash-mozplugin Version: 0.4.11-4 Severity: grave Justification: renders package unusable URL: http://www.bredbandsbolaget.se/. Segfaults occured in this order: First attempt - no backtrace :( Second attempt: , | Program received signal SIGSEGV, Segmentation fault. | [Switching to Thread 16384 (LWP 14000)] | 0x087f7e88 in nsHTMLReflowState::InitCBReflowState () | (gdb) info stack | #0 0x087f7e88 in nsHTMLReflowState::InitCBReflowState () | #1 0x087f7e27 in nsHTMLReflowState::Init () | #2 0x087f7590 in nsHTMLReflowState::nsHTMLReflowState () | #3 0x085d8ead in nsTableCellReflowState::nsTableCellReflowState () | #4 0x085dabe3 in GetSpaceBetween () | #5 0x085dbbfc in GetSpaceBetween () | #6 0x087f0ded in nsContainerFrame::ReflowChild () | #7 0x085dcda5 in nsTableRowGroupFrame::ReflowChildren () | #8 0x085def24 in nsTableRowGroupFrame::SplitRowGroup () | #9 0x087f0ded in nsContainerFrame::ReflowChild () | #10 0x085c92f5 in nsTableFrame::ReflowChildren () | #11 0x085c6975 in nsTableFrame::IsPrematureSpecialHeightReflow () | #12 0x087f0ded in nsContainerFrame::ReflowChild () | #13 0x085d61a1 in nsTableOuterFrame::IsAutoWidth () | #14 0x085d83b4 in nsTableOuterFrame::IR_CaptionChangedAxis () | #15 0x087eabc5 in nsBlockReflowContext::ReflowBlock () | #16 0x087e5556 in nsBlockFrame::ReflowBlockFrame () | #17 0x087e436c in nsBlockFrame::ReflowLine () | #18 0x087e4088 in nsBlockFrame::ReflowDirtyLines () | #19 0x087e23f6 in nsBlockFrame::IsContainingBlock () | #20 0x087f0ded in nsContainerFrame::ReflowChild () | #21 0x085c029d in nsTableCellFrame::GetColSpan () | #22 0x087f0ded in nsContainerFrame::ReflowChild () | #23 0x085dac73 in GetSpaceBetween () | #24 0x085dbbfc in GetSpaceBetween () | #25 0x087f0ded in nsContainerFrame::ReflowChild () | #26 0x085dcda5 in nsTableRowGroupFrame::ReflowChildren () | #27 0x085def24 in nsTableRowGroupFrame::SplitRowGroup () | #28 0x087f0ded in nsContainerFrame::ReflowChild () | #29 0x085c92f5 in nsTableFrame::ReflowChildren () | #30 0x085c6975 in nsTableFrame::IsPrematureSpecialHeightReflow () | #31 0x087f0ded in nsContainerFrame::ReflowChild () | #32 0x085d61a1 in nsTableOuterFrame::IsAutoWidth () | #33 0x085d83b4 in nsTableOuterFrame::IR_CaptionChangedAxis () | #34 0x087eabc5 in nsBlockReflowContext::ReflowBlock () | #35 0x087e5556 in nsBlockFrame::ReflowBlockFrame () | #36 0x087e436c in nsBlockFrame::ReflowLine () | #37 0x087e4088 in nsBlockFrame::ReflowDirtyLines () | #38 0x087e23f6 in nsBlockFrame::IsContainingBlock () | #39 0x087eabc5 in nsBlockReflowContext::ReflowBlock () | #40 0x087e5556 in nsBlockFrame::ReflowBlockFrame () | #41 0x087e436c in nsBlockFrame::ReflowLine () | #42 0x087e4088 in nsBlockFrame::ReflowDirtyLines () | #43 0x087e23f6 in nsBlockFrame::IsContainingBlock () | #44 0x087f0ded in nsContainerFrame::ReflowChild () | #45 0x087f6b56 in NS_NewCanvasFrame () | #46 0x08844987 in nsBoxToBlockAdaptor::Reflow () | #47 0x08844555 in nsBoxToBlockAdaptor::RefreshSizeCache () | #48 0x085e65f0 in nsBox::UnCollapseChild () | #49 0x085e3163 in nsScrollBoxFrame::CreateScrollingView () | #50 0x085e65f0 in nsBox::UnCollapseChild () | #51 0x085ee3c3 in nsContainerBox::LayoutChildAt () | #52 0x087f4498 in nsGfxScrollFrameInner::Layout () | #53 0x087f4253 in nsGfxScrollFrameInner::LayoutBox () | #54 0x085e65f0 in nsBox::UnCollapseChild () | #55 0x085e9af7 in nsBoxFrame::IsInitialReflowForPrintPreview () | #56 0x087f3609 in nsGfxScrollFrame::GetScrollbarStyles () | #57 0x087f0ded in nsContainerFrame::ReflowChild () | #58 0x0881d259 in ViewportFrame::AdjustReflowStateForScrollbars () | #59 0x08584344 in IncrementalReflow::Dispatch () | #60 0x0858f7d8 in PresShell::ProcessReflowCommands () | #61 0x08590a2c in ReflowEvent::HandleEvent () | #62 0x40118237 in PL_HandleEvent () from /usr/lib/mozilla-firefox/libxpcom.so | #63 0x40118164 in PL_ProcessPendingEvents () |from /usr/lib/mozilla-firefox/libxpcom.so | #64 0x40119df9 in nsEventQueueImpl::NotifyObservers () |from /usr/lib/mozilla-firefox/libxpcom.so | #65 0x085693b5 in nsBaseWidget::FreeNativeData () | #66 0x4065edbf in g_vasprintf () from /usr/lib/libglib-2.0.so.0 | #67 0x40639582 in g_main_depth () from /usr/lib/libglib-2.0.so.0 | #68 0x4063a5f8 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 | #69 0x4063a930 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 | #70 0x4063aed3 in g_main_loop_run () from /usr/lib/libglib-2.0.so.0 | #71 0x4031ebb3 in gtk_main () from /usr/lib/libgtk-x11-2.0.so.0 | #72 0x085696f8 in nsAppShell::ReleaseGlobals () | #73 0x08a0f844 in nsAppShellService::AttemptingQuit () | #74 0x08c148a0 in xre_main () | #75 0x0834b1d4 in main () ` Third attempt: , | Program received signal SIGSEGV, Segmentation fault. | [Switching to Thread 16384 (LWP 18739)] | 0x411b7bac in Text::doText () from /usr/lib/libflash.so.0 | (gdb) info stack | #0 0x411b7bac in Text::doText () from /usr/lib/libflash.so.0 | #1 0x411b7866 in Text::execute () from /usr/
Bug#303998: xmms: Segmentation fault
Package: xmms Version: 1.2.10+cvs20050209-2 Severity: grave Justification: renders package unusable , | ... | (no debugging symbols found) | [New Thread 32771 (LWP 1564)] | Message: device: default | [New Thread 49156 (LWP 1565)] | | Program received signal SIGSEGV, Segmentation fault. | [Switching to Thread 16384 (LWP 1561)] | 0x0806e8f1 in check_ctrlsocket () | (gdb) bt | #0 0x0806e8f1 in check_ctrlsocket () | #1 0x08081285 in idle_func () | #2 0x401faec4 in g_main_set_poll_func () from /usr/lib/libglib-1.2.so.0 | #3 0x401fa03d in g_get_current_time () from /usr/lib/libglib-1.2.so.0 | #4 0x401fa4f4 in g_get_current_time () from /usr/lib/libglib-1.2.so.0 | #5 0x401fa724 in g_main_run () from /usr/lib/libglib-1.2.so.0 | #6 0x4010425f in gtk_main () from /usr/lib/libgtk-1.2.so.0 | #7 0x080833a5 in main () ` downgrading to Version: 1.2.10-1.2. Cheers, Cristian -- System Information: Debian Release: 3.1 APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.4.27 Locale: LANG=C, LC_CTYPE= (charmap=ANSI_X3.4-1968) Versions of packages xmms depends on: ii libc62.3.2.ds1-20GNU C Library: Shared libraries an ii libglib1.2 1.2.10-9The GLib library of C routines ii libgtk1.21.2.10-17 The GIMP Toolkit set of widgets fo ii libice6 4.3.0.dfsg.1-12.0.1 Inter-Client Exchange library ii libsm6 4.3.0.dfsg.1-12.0.1 X Window System Session Management ii libssl0.9.7 0.9.7e-3SSL shared libraries ii libx11-6 4.3.0.dfsg.1-12.0.1 X Window System protocol client li ii libxext6 4.3.0.dfsg.1-12.0.1 X Window System miscellaneous exte ii libxi6 4.3.0.dfsg.1-12.0.1 X Window System Input extension li ii xlibs4.3.0.dfsg.1-12 X Keyboard Extension (XKB) configu -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#296189: seahorse: unistallable
Followup-For: Bug #296189 Package: seahorse Version: 0.7.6-2 seahorse.postrm should ignore (not fail) any script argument which is not either remove or purge, so please consider removing lines 51-55. Cheers, Cristian -- System Information: Debian Release: 3.1 APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.4.27 Locale: LANG=C, LC_CTYPE= (charmap=ANSI_X3.4-1968) Versions of packages seahorse depends on: ii debconf [debconf-2.0]1.4.45 Debian configuration management sy ii gconf2 2.8.1-4 GNOME configuration database syste ii libart-2.0-2 2.3.17-1Library of functions for 2D graphi ii libatk1.0-0 1.8.0-4 The ATK accessibility toolkit ii libbonobo2-0 2.8.1-2 Bonobo CORBA interfaces library ii libbonoboui2-0 2.8.1-1 The Bonobo UI library ii libc62.3.2.ds1-20GNU C Library: Shared libraries an ii libeel2-22.8.2-1 Eazel Extensions Library (for GNOM ii libgail-common 1.8.2-1 GNOME Accessibility Implementation ii libgail171.8.2-1 GNOME Accessibility Implementation ii libgconf2-4 2.8.1-4 GNOME configuration database syste ii libglade2-0 1:2.4.2-1 library to load .glade files at ru ii libglib2.0-0 2.6.2-1 The GLib library of C routines ii libgnome2-0 2.8.0-6 The GNOME 2 library - runtime file ii libgnomecanvas2-02.8.0-1 A powerful object-oriented display ii libgnomeui-0 2.8.0-3 The GNOME 2 libraries (User Interf ii libgnomevfs2-0 2.8.3-11The GNOME virtual file-system libr ii libgpg-error01.0-1 library for common error values an ii libgpgme11 1.0.2-1 GPGME - GnuPG Made Easy ii libgtk2.0-0 2.6.2-3 The GTK+ graphical user interface ii libice6 4.3.0.dfsg.1-10 Inter-Client Exchange library ii libldap2 2.1.30-3OpenLDAP libraries ii liborbit21:2.10.5-0.1libraries for ORBit2 - a CORBA ORB ii libpango1.0-01.8.0-3 Layout and rendering of internatio ii libpopt0 1.7-5 lib for parsing cmdline parameters ii libsm6 4.3.0.dfsg.1-10 X Window System Session Management ii libx11-6 4.3.0.dfsg.1-10 X Window System protocol client li ii libxml2 2.6.16-3GNOME XML library ii xlibs4.3.0.dfsg.1-11 X Keyboard Extension (XKB) configu ii zlib1g 1:1.2.2-4 compression library - runtime -- debconf information: * seahorse/SUID: true -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
