Bug#1031847: gnome-shell: Gnome crashes when laptop connected to ThinkPad Universal Thunderbolt 4 Dock (40B0), Oh no! Something has gone wrong error appears.
Clarification: pasted output in previous mail is not consistent, `reportbug --template gnome-shell` was done with colord patched, but then I reinstalled it, rebooted machine and copied output of `$ dpkg --list | grep colord` to the email. Sorry for confusion. All the best, Kuba
Bug#1031847: gnome-shell: Gnome crashes when laptop connected to ThinkPad Universal Thunderbolt 4 Dock (40B0), Oh no! Something has gone wrong error appears.
> Kuba (or anyone else who can reproduce this), please could you try with mutter-related packages (at least libmutter-11-0) upgraded to the version 43.3-3+1+g8c42befe7 that I have uploaded to <https://people.debian.org/~smcv/bug1031847/>? I have updated and it has resolved the crash :) > You might still need the colord packages from there *as well*, I'm not 100% sure how necessary the colord change is. I did test with and without updated colord, patch is not required to resolve the crash (only mutter patch is required) Below is output of packages installed with docking station working as expected: $ dpkg --list | grep colord ii colord 1.4.6-2.1 amd64system service to manage device colour profiles -- system daemon ii colord-data 1.4.6-2.1 all system service to manage device colour profiles -- data files ii gir1.2-colord-1.0:amd64 1.4.6-2.1 amd64GObject introspection data for the colord library ii libcolord-gtk4-1:amd64 0.3.0-3 amd64GTK4 convenience library for interacting with colord ii libcolord2:amd641.4.6-2.1 amd64system service to manage device colour profiles -- runtime $ reportbug --template gnome-shell Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: Kuba To: Debian Bug Tracking System Subject: gnome-shell: none Package: gnome-shell Version: 43.3-1 Severity: wishlist X-Debbugs-Cc: lxk...@wp.pl -- System Information: Debian Release: bookworm/sid APT prefers testing-debug APT policy: (500, 'testing-debug'), (500, 'testing'), (100, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.1.0-3-amd64 (SMP w/16 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages gnome-shell depends on: ii dconf-gsettings-backend [gsettings-backend] 0.40.0-4 ii gir1.2-accountsservice-1.0 22.08.8-6 ii gir1.2-adw-1 1.2.2-1 ii gir1.2-atk-1.0 2.46.0-5 ii gir1.2-atspi-2.0 2.46.0-5 ii gir1.2-freedesktop 1.74.0-3 ii gir1.2-gcr-3 3.41.1-1+b1 ii gir1.2-gdesktopenums-3.0 43.0-1 ii gir1.2-gdkpixbuf-2.0 2.42.10+dfsg-1+b1 ii gir1.2-gdm-1.0 43.0-3 ii gir1.2-geoclue-2.0 2.6.0-2 ii gir1.2-glib-2.0 1.74.0-3 ii gir1.2-gnomebluetooth-3.042.5-3 ii gir1.2-gnomedesktop-3.0 43.2-1 ii gir1.2-graphene-1.0 1.10.8-1 ii gir1.2-gstreamer-1.0 1.22.0-2 ii gir1.2-gtk-3.0 3.24.36-4 ii gir1.2-gtk-4.0 4.8.3+ds-2 ii gir1.2-gweather-4.0 4.2.0-1 ii gir1.2-ibus-1.0 1.5.27-5 ii gir1.2-mutter-11 43.3-3+1+g8c42befe7 ii gir1.2-nm-1.01.42.2-1 ii gir1.2-nma-1.0 1.10.6-1 ii gir1.2-pango-1.0 1.50.12+ds-1 ii gir1.2-polkit-1.0122-3 ii gir1.2-rsvg-2.0 2.54.5+dfsg-1 ii gir1.2-soup-3.0 3.2.2-1 ii gir1.2-upowerglib-1.00.99.20-2 ii gir1.2-webkit2-4.1 2.38.5-1 ii gnome-backgrounds43.1-1 ii gnome-settings-daemon43.0-4 ii gnome-shell-common 43.3-1 ii gsettings-desktop-schemas43.0-1 ii gstreamer1.0-pipewire0.3.65-3 ii libatk-bridge2.0-0 2.46.0-5 ii libatk1.0-0 2.46.0-5 ii libc62.36-8 ii libcairo21.16.0-7 ii libecal-2.0-23.46.4-1 ii libedataserver-1.2-273.46.4-1 ii libgcr-base-3-1 3.41.1-1+b1 ii libgdk-pixbuf-2.0-0 2.42.10+dfsg-1+b1 ii libgirepository-1.0-11.74.0-3 ii libgjs0g 1.74.2-1 ii libgles2 1.6.0-1 ii libglib2.0-0 2.74.5-1 ii libglib2.0-bin 2.74.5-1 ii libgnome-autoar-0-0 0.4.3-1 ii
Bug#1031847: gnome-shell: Gnome crashes when laptop connected to ThinkPad Universal Thunderbolt 4 Dock (40B0), Oh no! Something has gone wrong error appears.
> I'm not going to be able to reproduce this myself, and probably neither are other GNOME maintainers, because the crash only happens when you have a Thunderbolt display connected (or perhaps even a specific type of Thunderbolt display). I am happy to help with testing. > Kuba, please could you try the packages from here? https://people.debian.org/~smcv/bug1031847/ Just tested colord version you linked, the issue still occurs (did not paste stack trace but it looks the same as one I posted originally). Just for clarity, the steps I used : 1) installed downloaded packages with `dpkg -i`, 2) rebooted machine, 3) logged in and connected dock station. $ dpkg --list | grep colord ii colord 1.4.6-2+7+g66cc43cf amd64system service to manage device colour profiles -- system daemon ii colord-data 1.4.6-2+7+g66cc43cf all system service to manage device colour profiles -- data files ii gir1.2-colord-1.0:amd64 1.4.6-2+7+g66cc43cf amd64GObject introspection data for the colord library ii libcolord-gtk4-1:amd64 0.3.0-3 amd64GTK4 convenience library for interacting with colord ii libcolord2:amd641.4.6-2+7+g66cc43cf amd64system service to manage device colour profiles -- runtime logs: 2023-02-25T15:30:12.128 31038027 user@1000.service -[2536] STATS Running GNOME Shell (using mutter 43.3) as a Wayland display server 2023-02-25T15:30:13.974 32884593 user@1000.service -[2536] STATS GNOME Shell started at Sat Feb 25 2023 15:30:13 GMT+0100 (Central European Standard Time) 2023-02-25T15:30:35.491 54873564 - kernel[-] INFO thunderbolt 0-3: new device found, vendor=0x108 device=0x2031 2023-02-25T15:30:38.655 58037256 user@1000.service -[2536] WARNING g_hash_table_steal_extended: assertion 'hash_table != NULL' failed 2023-02-25T15:30:38.657 58039278 user@1000.service -[2536] STATS Created gbm renderer for '/dev/dri/card1' 2023-02-25T15:30:38.657 58039349 user@1000.service -[2536] WARNING Secondary GPU initialization failed (Failed to create gbm_surface: Operation not permitted). Falling back to GPU-less mode instead, so the secondary monitor may be slow to update. 2023-02-25T15:30:38.875 58257792 user@1000.service gnome-shell[2536] INFO free(): double free detected in tcache 2 2023-02-25T15:30:38.875 58257792 user@1000.service gnome-shell[2536] INFO malloc_consolidate(): unaligned fastbin chunk detected 2023-02-25T15:30:39.130 58512009 packagekit.service PackageKit[1433] DEBUG search-file transaction /5748_bccacdad from uid 1000 finished with success after 457ms 2023-02-25T15:30:54.317 73699365 session-c3.scope gnome-session-binary[5797] ERROR Unrecoverable failure in required component org.gnome.Shell.desktop $ sudo coredumpctl list TIME PID UID GID SIG COREFILE EXE SIZE Sat 2023-02-25 15:30:39 CET 2536 1000 1000 SIGABRT present /usr/bin/gnome-shell 17.5M Sat 2023-02-25 15:30:43 CET 5182 113 122 SIGABRT present /usr/bin/gnome-shell 12.1M Sat 2023-02-25 15:30:52 CET 5841 113 122 SIGABRT present /usr/bin/gnome-shell 10.8M Sat 2023-02-25 15:30:54 CET 6357 113 122 SIGABRT present /usr/bin/gnome-shell 10.8M > I suspect that Thunderbolt docks will become increasingly widespread during the Debian 12 release's lifetime, so it would be good to get this fixed before the next phase of the freeze I agree. I am available to help with testing. All the best, Kuba On Sat, Feb 25, 2023 at 1:42 PM Simon McVittie wrote: > Control: reassign -1 libcolord2 1.4.6-2.1 > Control: affects -1 + gnome-shell liblcms2-2 > Control: forwarded -1 https://github.com/hughsie/colord/pull/146 > Control: tags -1 + patch > > On Fri, 24 Feb 2023 at 10:33:42 +, Simon McVittie wrote: > > On Fri, 24 Feb 2023 at 05:50:06 +0100, Kuba wrote: > > > Bug is described here: > https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/6162 > > > and if I understand correctly, it is diagnosed as some dependency > issue. > > > > From the linked issue report it looks like this is a bug in lcms fixed by > > <https://github.com/mm2/Little-CMS/issues/344>, combined with a bug in > > colord fixed by <https://github.com/hughsie/colord/pull/146>. > > On closer inspection, Debian's lcms2 already has the patch to fix that bug, > so this is purely a colord issue. It's possible that this regressed when > lcms2 was updated in January. > > Anyone who doesn't have the right hardware will probably not be able > to reproduce this. Kuba, please could you try the packages from here? > https://people.debian.org/~smcv/bug1031847/ > > (Those test packages have the patch referenced here, plus the patche
Bug#1031847: gnome-shell: Gnome crashes when laptop connected to ThinkPad Universal Thunderbolt 4 Dock (40B0), Oh no! Something has gone wrong error appears.
Package: gnome-shell Version: 43.3-1 Severity: important X-Debbugs-Cc: lxk...@wp.pl Bug is described here: https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/6162 and if I understand correctly, it is diagnosed as some dependency issue. The crash occures every time both when the system is powered on connected to the dock (the moment login screen is beginning to be displayed), and also when dock is connected to the system which is already loged in. same happens with version 43.2-2 logs: 2023-02-24T05:10:57.774 66659682 - kernel[-] INFO thunderbolt 0-3: new device found, vendor=0x108 device=0x2031 2023-02-24T05:10:57.774 66659753 - kernel[-] INFO thunderbolt 0-3: Lenovo ThinkPad Thunderbolt 4 Dock 2023-02-24T05:11:01.867 70753222 user@1000.service -[2534] WARNING g_hash_table_steal_extended: assertion 'hash_table != NULL' failed 2023-02-24T05:11:01.870 70755611 user@1000.service -[2534] STATS Created gbm renderer for '/dev/dri/card1' 2023-02-24T05:11:01.870 70755697 user@1000.service -[2534] WARNING Secondary GPU initialization failed (Failed to create gbm_surface: Operation not permitted). Falling back to GPU-less mode instead, so the secondary monitor may be slow to update. 2023-02-24T05:11:02.074 70960398 user@1000.service gnome-shell[2534] INFO free(): double free detected in tcache 2 2023-02-24T05:11:02.074 70960398 user@1000.service gnome-shell[2534] INFO malloc_consolidate(): unaligned fastbin chunk detected 2023-02-24T05:11:02.112 70998396 init.scope systemd[1] INFO Created slice system-systemd\x2dcoredump.slice - Slice /system/systemd-coredump. 2023-02-24T05:11:02.140 71026377 init.scope systemd[1] INFO Started systemd- coredump@0-4996-0.service - Process Core Dump (PID 4996/UID 0). 2023-02-24T05:11:02.908 71794339 systemd-coredump@0-4996-0.service systemd- coredump[5000] CRITICAL null 2023-02-24T05:11:02.949 71834655 user@1000.service gnome-shell[3080] INFO (EE) failed to read Wayland events: Connection reset by peer ... $ sudo coredumpctl list TIME PID UID GID SIG COREFILE EXE SIZE Fri 2023-02-24 05:11:02 CET 2534 1000 1000 SIGABRT present /usr/bin/gnome- shell 17.9M Fri 2023-02-24 05:11:06 CET 5136 113 122 SIGABRT present /usr/bin/gnome- shell 11.9M Fri 2023-02-24 05:11:14 CET 5716 113 122 SIGABRT present /usr/bin/gnome- shell 12.0M Fri 2023-02-24 05:11:16 CET 6190 113 122 SIGABRT present /usr/bin/gnome- shell 11.8M $ sudo DEBUGINFOD_URLS="https://debuginfod.debian.net; coredumpctl debug -r 2534 PID: 2534 (gnome-shell) UID: 1000 (doubleloop) GID: 1000 (doubleloop) Signal: 6 (ABRT) Timestamp: Fri 2023-02-24 05:11:02 CET (3min 13s ago) Command Line: /usr/bin/gnome-shell Executable: /usr/bin/gnome-shell Control Group: /user.slice/user-1000.slice/user@1000.service/session.slice/org.gnome.Shell@wayland.service Unit: user@1000.service User Unit: org.gnome.Shell@wayland.service Slice: user-1000.slice Owner UID: 1000 (doubleloop) Boot ID: 7639b4595d8145d49b41c42e90656ad2 Machine ID: ae7bc147e6524501b468de6ed742a1a0 Hostname: floydP1d Storage: /var/lib/systemd/coredump/core.gnome- shell.1000.7639b4595d8145d49b41c42e90656ad2.2534.167721186200.zst (present) Size on Disk: 17.9M Message: Process 2534 (gnome-shell) of user 1000 dumped core. Module libnss_mymachines.so.2 from deb systemd-252.5-2.amd64 Module libnss_myhostname.so.2 from deb systemd-252.5-2.amd64 Module libudev.so.1 from deb systemd-252.5-2.amd64 Module libsystemd.so.0 from deb systemd-252.5-2.amd64 Stack trace of thread 2534: #0 0x7f6e31aa9ccc __pthread_kill_implementation (libc.so.6 + 0x8accc) #1 0x7f6e31a5aef2 __GI_raise (libc.so.6 + 0x3bef2) #2 0x7f6e31a45472 __GI_abort (libc.so.6 + 0x26472) #3 0x7f6e31a9e2d0 __libc_message (libc.so.6 + 0x7f2d0) #4 0x7f6e31ab364a malloc_printerr (libc.so.6 + 0x9464a) #5 0x7f6e31ab40ac malloc_consolidate (libc.so.6 + 0x950ac) #6 0x7f6e31ab66b8 _int_malloc (libc.so.6 + 0x976b8) #7 0x7f6e31ab7799 __GI___libc_malloc (libc.so.6 + 0x98799) #8 0x7f6e31a9476c __GI__IO_file_doallocate (libc.so.6 + 0x7576c) #9 0x7f6e31aa1f50 __GI__IO_doallocbuf (libc.so.6 + 0x82f50) #10 0x7f6e31aa1318 _IO_new_file_overflow (libc.so.6 + 0x82318) #11 0x7f6e31aa04de _IO_new_file_xsputn (libc.so.6 + 0x814de) #12 0x7f6e31a954a9 __GI__IO_fputs (libc.so.6 + 0x764a9) #13 0x7f6e32b45325 n/a (libglib-2.0.so.0 + 0x5b325) #14 0x7f6e32b47de2 g_printerr (libglib-2.0.so.0 + 0x5dde2) #15
Bug#1004426: Acknowledgement (linux-image-5.10.0-10-amd64: webcam Live! Cam Sync HD VF0770 unusable after updating to linux-image-5.10.0-10)
> Is this the same problem as reported in bug #1003236? Yes, it looks the same. On Thu, Jan 27, 2022 at 2:51 PM Debian Bug Tracking System < ow...@bugs.debian.org> wrote: > Thank you for filing a new Bug report with Debian. > > You can follow progress on this Bug here: 1004426: > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004426. > > This is an automatically generated reply to let you know your message > has been received. > > Your message is being forwarded to the package maintainers and other > interested parties for their attention; they will reply in due course. > > As you requested using X-Debbugs-CC, your message was also forwarded to > lxk...@wp.pl > (after having been given a Bug report number, if it did not have one). > > Your message has been sent to the package maintainer(s): > Debian Kernel Team > > If you wish to submit further information on this problem, please > send it to 1004...@bugs.debian.org. > > Please do not send mail to ow...@bugs.debian.org unless you wish > to report a problem with the Bug-tracking system. > > -- > 1004426: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004426 > Debian Bug Tracking System > Contact ow...@bugs.debian.org with problems >
Bug#871648: qemu-system-x86: /usr/bin/qemu-system-i386 eats slowly but surely all the Dom0 memory
This bug can be can be 'disarmed' by using below settings (or I shuld say comment this settings): #apic = 1 #sdl = 0 #usbdevice = 'tablet' I think that the main problem is param 'usbdevice=' . I watched two machines with commented above options - problem solved... Please check it.
Bug#767712: vlc-nox: vlc vlsub does not seem to work
On Sun, 02 Nov 2014 02:06:52 + Chris Bainbridge < chris.bainbri...@gmail.com> wrote: > Package: vlc-nox > Version: 2.2.0~pre4-1+b1 > Severity: normal > > Dear Maintainer, > > View > Download subtitles > Search by hash / Search by name, neither seems to > work. Search by hash shows "Calculating movie hash" next to a white box > (progress bar?) and nothing happens. Remote API changed and this package is outdated, download updated version from project page and install it manually: https://github.com/exebetche/vlsub
Bug#838847: ffmpeg depends on libx265-79 but it is not a package available in main or backports for jessie
Package: ffmpeg Version: 3.0.2-4~bpo8+1 Severity: important Dear Maintainer, Trying to install ffmpeg from backports which has worked in the past no breaks on a dependency error for the package libx265-79. Steps to duplicate: docker run -i -t debian:jessie bash >echo 'deb http://httpredir.debian.org/debian jessie-backports main' >> >/etc/apt/sources.list > apt-get update > apt-get install -t jessie-backports ffmpeg Looks like the package used to be available in the repos from some old images I have: apt-cache show libx265-79 Package: libx265-79 Status: install ok installed Priority: optional Section: libs Installed-Size: 10798 Maintainer: Debian Multimedia MaintainersArchitecture: amd64 Multi-Arch: same Source: x265 Version: 1.9-3~bpo8+1 Depends: libc6 (>= 2.15), libnuma1, libstdc++6 (>= 4.1.1) Description: H.265/HEVC video stream encoder (shared library) libx265 is an encoding library for creating H.265/High Efficiency Video Coding (HEVC) video streams. . This package contains the shared library. Description-md5: 9a85cf11805d7cd3e922b7e2ad8ea348 Homepage: http://x265.org -- System Information: Debian Release: 8.2 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.4.0-38-generic (SMP w/4 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/dash Init: unable to detect
Bug#729659: general: problem with laptop suspend after dist-upgrade
Package: general Severity: normal Dear Maintainer, After running apt-get dist-upgrade, my laptop does not suspend properly: Problems: 1) key shortcut - used to work (standard shortcut, worked out of the box), now instead suspending, it causes screen lock 2) menu option - used to be above power off option (in gnome menu, this in top right), now disapeared 3) closing lid - does nothing, used to suspend when I type some magical command (found on http://askubuntu.com/questions/1792 /how-can-i-suspend-hibernate-from-command-line): dbus-send --system --print-reply \ --dest=org.freedesktop.UPower \ /org/freedesktop/UPower \ org.freedesktop.UPower.Suspend system suspends propperly laptop: Lenovo thinkpad t61p Chears, Kuba -- System Information: Debian Release: jessie/sid APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'unstable'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.11-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#508259: linux-image-2.6.18-6-k7: Local kernel panic exploit
Package: linux-image-2.6.18-6-k7 Version: 2.6.18.dfsg.1-23 Severity: critical Tags: security Justification: breaks the whole system These exploit freezess all my Debian/Ubuntu machines: http://www.milw0rm.com/exploits/7091 -- System Information: Debian Release: 4.0 APT prefers stable APT policy: (500, 'stable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-6-k7 Locale: LANG=pl_PL.UTF-8, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8) Versions of packages linux-image-2.6.18-6-k7 depends on: ii coreutils5.97-5.3The GNU core utilities ii debconf [debconf-2.0]1.5.11etch2 Debian configuration management sy ii initramfs-tools [linux-initr 0.85i tools for generating an initramfs ii module-init-tools3.3-pre4-2 tools for managing Linux kernel mo Versions of packages linux-image-2.6.18-6-k7 recommends: ii libc6-i686 2.3.6.ds1-13etch7 GNU C Library: Shared libraries [i -- debconf information: linux-image-2.6.18-6-k7/preinst/initrd-2.6.18-6-k7: linux-image-2.6.18-6-k7/prerm/removing-running-kernel-2.6.18-6-k7: true linux-image-2.6.18-6-k7/postinst/kimage-is-a-directory: linux-image-2.6.18-6-k7/postinst/depmod-error-2.6.18-6-k7: false linux-image-2.6.18-6-k7/preinst/abort-overwrite-2.6.18-6-k7: linux-image-2.6.18-6-k7/preinst/failed-to-move-modules-2.6.18-6-k7: linux-image-2.6.18-6-k7/preinst/lilo-initrd-2.6.18-6-k7: true linux-image-2.6.18-6-k7/postinst/depmod-error-initrd-2.6.18-6-k7: false linux-image-2.6.18-6-k7/postinst/old-system-map-link-2.6.18-6-k7: true linux-image-2.6.18-6-k7/preinst/abort-install-2.6.18-6-k7: shared/kernel-image/really-run-bootloader: true linux-image-2.6.18-6-k7/postinst/create-kimage-link-2.6.18-6-k7: true linux-image-2.6.18-6-k7/postinst/old-dir-initrd-link-2.6.18-6-k7: true linux-image-2.6.18-6-k7/postinst/bootloader-test-error-2.6.18-6-k7: linux-image-2.6.18-6-k7/preinst/lilo-has-ramdisk: * linux-image-2.6.18-6-k7/preinst/already-running-this-2.6.18-6-k7: linux-image-2.6.18-6-k7/preinst/elilo-initrd-2.6.18-6-k7: true linux-image-2.6.18-6-k7/prerm/would-invalidate-boot-loader-2.6.18-6-k7: true linux-image-2.6.18-6-k7/preinst/bootloader-initrd-2.6.18-6-k7: true linux-image-2.6.18-6-k7/preinst/overwriting-modules-2.6.18-6-k7: true linux-image-2.6.18-6-k7/postinst/bootloader-error-2.6.18-6-k7: linux-image-2.6.18-6-k7/postinst/old-initrd-link-2.6.18-6-k7: true -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#432292: Text file identified as bzip compressed data, version: T
Package: file Version: 4.12-1sarge1 Severity: normal A text file with a content like like this: BZT 120 163 ABOUT 75 YRDS LEFT ROLL #2508834 Was reported as a: bzip compressed data, version: T Unfortunately this stopped amavis from checking this file and dropped entire email message. -- System Information: Debian Release: 3.1 Architecture: i386 (i686) Kernel: Linux 2.6.8-2-686 Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Versions of packages file depends on: ii libc6 2.3.2.ds1-22sarge6 GNU C Library: Shared libraries an ii libmagic1 4.12-1sarge1 File type determination library us ii zlib1g1:1.2.2-4.sarge.2 compression library - runtime -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#384684: postfix: Postfix 2.3.2 from unstable - option alternate_config_directories doesn't work
Package: postfix Version: 2.3.2-1 Severity: normal I have compiled Postfix from unstable, using apt-get tool and found out that option alternate_config_directories doesn't work. Starting/Restarting with /etc/init.d/postfix start/restart, doesn't include my second configuration. The settings worked fine with compiled postfix version from stable. -- System Information: Debian Release: 3.1 Architecture: i386 (i686) Kernel: Linux 2.6.8-2-k7 Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Versions of packages postfix depends on: ii adduser 3.63 Add and remove users and groups ii debconf [debconf-2.0] 1.4.30.13 Debian configuration management sy ii dpkg 1.10.28Package maintenance system for Deb ii libc6 2.3.2.ds1-22sarge3 GNU C Library: Shared libraries an ii libdb4.3 4.3.27-2 Berkeley v4.3 Database Libraries [ ii libsasl2 2.1.19-1.5sarge1 Authentication abstraction library ii libssl0.9.7 0.9.7e-3sarge1 SSL shared libraries ii lsb-base 3.1-9bpo1 Linux Standard Base 3.1 init scrip ii netbase 4.21 Basic TCP/IP networking system ii ssl-cert 1.0-11 Simple debconf wrapper for openssl -- debconf information: postfix/master_upgrade_warning: postfix/db_upgrade_warning: true * postfix/mailname: fabrykahostingu.pl postfix/tlsmgr_upgrade_warning: postfix/dynamicmaps_upgrade_warning: postfix/recipient_delim: + * postfix/main_mailer_type: Internet Site postfix/transport_map_warning: postfix/relayhost: postfix/procmail: true postfix/bad_recipient_delimiter: * postfix/chattr: false * postfix/root_address: root postfix/rfc1035_violation: false postfix/mynetworks: 64.34.175.88/32 * postfix/destinations: postfix/nqmgr_upgrade_warning: postfix/not_configured: postfix/mailbox_limit: 0 postfix/protocols: all -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#384684: Closed
My mistake. I have forgot that I have changed postfix file in /etc/init.d/ to start second postfix instance. I have done some reading alternate_config_directoriesc option is to let postfix servers cooperate, and this way, everything works fine. Sorry for the trouble, Kuba -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]