Bug#1028192: gajim: Gajim 1.6.0-1 crashes on connect
Package: gajim Version: 1.6.1-2 Followup-For: Bug #1028192 X-Debbugs-Cc: n.vi...@gmail.com Dear Maintainer, I can also still reproduce this bug. It happens always when gajim tries to connect, including after I remove all its local settings/cache and enter my login information in a fresh setup. Thread 20 "pool-org.gajim." received signal SIGSEGV, Segmentation fault. [Switching to Thread 0x7fff59b276c0 (LWP 5488)] 0x730a81d0 in ?? () from /lib/x86_64-linux-gnu/libstdc++.so.6 (gdb) bt #0 0x730a81d0 in () at /lib/x86_64-linux-gnu/libstdc++.so.6 #1 0x730a8511 in () at /lib/x86_64-linux-gnu/libstdc++.so.6 #2 0x730a8607 in __gxx_personality_v0 () at /lib/x86_64-linux-gnu/libstdc++.so.6 #3 0x71508131 in __libunwind_Unwind_Resume () at /lib/x86_64-linux-gnu/libunwind.so.8 #4 0x7fffd089b34a in __gnu_cxx::new_allocator::~new_allocator() (this=, __in_chrg=) at /usr/include/c++/11/ext/new_allocator.h:89 #5 std::allocator::~allocator() (this=, __in_chrg=) at /usr/include/c++/11/bits/allocator.h:174 #6 std::_Vector_base >::_Vector_impl::~_Vector_impl() (this=, __in_chrg=) at /usr/include/c++/11/bits/stl_vector.h:128 #7 std::_Vector_base >::~_Vector_base() (this=, __in_chrg=) at /usr/include/c++/11/bits/stl_vector.h:337 #8 std::vector >::~vector() (this=, __in_chrg=) at /usr/include/c++/11/bits/stl_vector.h:683 #9 envvar_config_extension::get_config(libproxy::url const&) (this=, dst=) at ./libproxy/modules/config_envvar.cpp:60 #10 0x7fffd0891e52 in libproxy::proxy_factory::get_config(libproxy::url&, std::vector >&, std::__cxx11::basic_string, std::allocator >&) (this=0x2c8b070, realurl=..., config=std::vector of length 0, capacity 0, ignore="") at ./libproxy/proxy.cpp:265 #11 0x7fffd0892287 in libproxy::proxy_factory::get_proxies(std::__cxx11::basic_string, std::allocator > const&) (this=0x2c8b070, realurl="none://coaxion.net:5222") at ./libproxy/proxy.cpp:206 #12 0x7fffd0892751 in px_proxy_factory_get_proxies(pxProxyFactory_*, char const*) (self=0x2c8b070, url=url@entry=0x251b500 "none://coaxion.net:5222") at ./libproxy/proxy.cpp:465 #13 0x7fffd8cc061f in get_libproxy_proxies (task=0x2ac8190 [GTask], source_object=0x1872620, task_data=0x251b500, cancellable=) at ../proxy/libproxy/glibproxyresolver.c:153 #14 0x76a90793 in g_task_thread_pool_thread (thread_data=0x2ac8190, pool_data=) at ../../../gio/gtask.c:1454 #15 0x76d736ca in g_thread_pool_thread_proxy (data=) at ../../../glib/gthreadpool.c:352 #16 0x76d72cfd in g_thread_proxy (data=0x17f6300) at ../../../glib/gthread.c:831 #17 0x77d13fd4 in start_thread (arg=) at ./nptl/pthread_create.c:442 #18 0x77d9466c in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81 (gdb) -- System Information: Debian Release: bookworm/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.1.0-2-amd64 (SMP w/16 CPU threads; PREEMPT) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_GB.UTF-8, LC_CTYPE=el_GR.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages gajim depends on: ii desktop-file-utils 0.26-1 ii gir1.2-gst-plugins-base-1.0 1.20.5-1 ii gir1.2-gtk-3.0 3.24.36-1 ii gir1.2-gtksource-4 4.8.4-4 ii python3 3.11.1-1 ii python3-cairo1.20.1-5 ii python3-cryptography 38.0.4-2 ii python3-css-parser 1.0.8-1 ii python3-gi 3.42.2-3 ii python3-gi-cairo 3.42.2-3 ii python3-idna 3.3-1 ii python3-keyring 23.9.3-2 ii python3-nbxmpp 4.0.1-1 ii python3-packaging23.0-1 ii python3-pil 9.4.0-1+b1 ii python3-precis-i18n 1.0.5-1 Versions of packages gajim recommends: ii alsa-utils 1.2.8-1 ii aspell-el [aspell-dictionary] 0.50-3-7 ii aspell-en [aspell-dictionary] 2018.04.16-0-1 ii ca-certificates 20211016 ii dbus1.14.4-1 ii fonts-noto-color-emoji 2.038-1 ii gajim-omemo 2.9.0-1 ii gajim-openpgp 1.5.0-1 ii gir1.2-farstream-0.20.2.9-1 ii gir1.2-geoclue-2.0 2.6.0-2 ii gir1.2-gsound-1.0 1.0.3-2 ii gir1.2-gspell-1 1.12.0-1+b1 ii gir1.2-gstreamer-1.01.20.5-1 ii gir1.2-gupnpigd-1.0 1.2.0-3 ii gir1.2-secret-1 0.20.5-3 ii gstreamer1.0-gl 1.20.5-1 ii gstreamer1.0-nice 0.1.18-2 ii gst
Bug#1007006: libreoffice-writer: Using deadkeys at the end of a line, but not the end of a page, goes to the next line
Package: libreoffice-writer Version: 1:7.3.1-1 Severity: normal X-Debbugs-Cc: n.vi...@gmail.com Dear Maintainer, When I am typing in LibreOffice Writer, I might be editing / adding things to a previous line. If I am at the end of a line, but there are more lines below, and at that point I type a deadkey character, I get the deadkey indicator at the end of the line, but the cursor goes to the line below and I cannot continue typing my character. Theoretically, I should type the dead key in question, see the deadkey indicator on the screen, and type the next character(s), so that the deadkey indicator goes away and I see what I meant to type. You can see an example on the following video. Here I am typing in Greek, trying to type the word εξής. The ή is typed using deadkeys: first the accent key, which displays an underlined accent (the deadkey indicator), then the η key, which removes the underlined accent and displays the character ή instead. http://ahiru.eu/~vivia/a_DpQmvaQPqItNoRJb3-dA.mp4 If I am typing in the middle of a line, or at the end of a document, it behaves fine. This is a major usability issue in languages like Greek where deadkeys are used extensively when typing, but it also affects the usage of e.g. the Compose key. It is especially annoying when someone wants to put a signature at the end of a document and continue writing the text, or first write the headers/layout and then fill in the content, like in my video, because when typing out a text, the cursor is normally going to the end of the line. -- Package-specific info: -- System Information: Debian Release: bookworm/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.16.0-1-amd64 (SMP w/16 CPU threads; PREEMPT) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_GB.UTF-8, LC_CTYPE=el_GR.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages libreoffice-writer depends on: ii libabw-0.1-1 0.1.3-1 ii libc62.33-7 ii libe-book-0.1-1 0.1.3-2 ii libepubgen-0.1-1 0.1.1-1 ii libetonyek-0.1-1 0.1.10-3 ii libgcc-s112-20220302-1 ii libicu67 67.1-7 ii libmwaw-0.3-30.3.21-1 ii libodfgen-0.1-1 0.1.8-2 ii libreoffice-base-core1:7.3.1-1 ii libreoffice-common 1:7.3.1-1 ii libreoffice-core 1:7.3.1-1 ii librevenge-0.0-0 0.0.4-6+b1 ii libstaroffice-0.0-0 0.0.7-1 ii libstdc++6 12-20220302-1 ii libuno-cppu3 1:7.3.1-1 ii libuno-cppuhelpergcc3-3 1:7.3.1-1 ii libuno-sal3 1:7.3.1-1 ii libuno-salhelpergcc3-3 1:7.3.1-1 ii libwpd-0.10-10 0.10.3-2 ii libwpg-0.3-3 0.3.3-1 ii libwps-0.4-4 0.4.12-2 ii libxml2 2.9.13+dfsg-1 ii ucf 3.0043 ii uno-libs-private 1:7.3.1-1 ii zlib1g 1:1.2.11.dfsg-2 Versions of packages libreoffice-writer recommends: ii libreoffice-math 1:7.3.1-1 Versions of packages libreoffice-writer suggests: ii default-jre [java8-runtime] 2:1.11-72 ii fonts-crosextra-caladea 20130214-2.1 ii fonts-crosextra-carlito 20130920-1.1 ii libreoffice-base1:7.3.1-1 ii libreoffice-java-common 1:7.3.1-1 ii openjdk-11-jre [java8-runtime] 11.0.14+9-1 ii openjdk-8-jre [java8-runtime] 8u312-b07-1 Versions of packages libreoffice-core depends on: ii fontconfig 2.13.1-4.4 ii fonts-opensymbol2:102.12+LibO7.3.1-1 ii libabsl20210324 0~20210324.2-2 ii libboost-locale1.74.0 1.74.0-14 ii libc6 2.33-7 ii libcairo2 1.16.0-5 ii libclucene-contribs1v5 2.3.3.4+dfsg-1+b1 ii libclucene-core1v5 2.3.3.4+dfsg-1+b1 ii libcups22.4.1op1-1 ii libcurl3-gnutls 7.82.0-1 ii libdbus-1-3 1.14.0-1 ii libdconf1 0.40.0-3 ii libeot0 0.01-5+b1 ii libepoxy0 1.5.9-2 ii libexpat1 2.4.7-1 ii libexttextcat-2.0-0 3.4.5-1 ii libfontconfig1 2.13.1-4.4 ii libfreetype62.11.1+dfsg-1 ii libgcc-s1 12-20220302-1 ii libglib2.0-02.70.4-1 ii libgpgmepp6 1.16.0-1.2 ii libgraphite2-3 1.3.14-1 ii libgstreamer-plugins-base1.0-0 1.20.0-2 ii libgstreamer1.0-0 1.20.0-1 ii libharfbuzz-icu02.7.4-1 ii libharfbuzz0b 2.7.4-1 ii libhunspell-1.7-0 1.7.0-4 ii libhyphen0 2.8.8-7 ii libice6
Bug#975572: linux: Enable mxc4005 driver
Source: linux Severity: wishlist X-Debbugs-Cc: n.vi...@gmail.com The mxc4005 module is disabled by default, so the accelerometer in my tablet doesn't work unless I manually build the module. Tablet is Chuwi Hi10 X. -- System Information: Debian Release: bullseye/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.9.0-2-amd64 (SMP w/8 CPU threads) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=el_GR.UTF-8, LC_CTYPE=el_GR.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#975524: task-lxqt-desktop: Should depend on nm-tray and blueman
Package: task-lxqt-desktop Severity: normal X-Debbugs-Cc: n.vi...@gmail.com A default installation of lxqt does not include an applet for network management. If the installation was done using a temporary Ethernet connection and the user now needs to set up WiFi, which is a common scenario for Debian installations, there's no front-end for that. A quick search for semi-novice users usually directs them to wicd, which does not exist in testing or sid. Similarly, there's no applet for setting up Bluetooth connections. Manually installing nm-tray and blueman greatly enhances the usability of lxqt, but they should be installed by default. -- System Information: Debian Release: bullseye/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.9.0-2-amd64 (SMP w/8 CPU threads) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=el_GR.UTF-8, LC_CTYPE=el_GR.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages task-lxqt-desktop depends on: pn lxqt ii sddm 0.19.0-2 pn sddm-theme-debian-elarun | sddm-theme-debian-elarun ii task-desktop 3.61 ii tasksel 3.61 Versions of packages task-lxqt-desktop recommends: ii hunspell-en-us 1:2019.10.06-1 ii hyphen-en-us2.8.8-7 ii libreoffice-calc1:7.0.3-4 pn libreoffice-gtk3 ii libreoffice-help-en-us 1:7.0.3-4 ii libreoffice-impress 1:7.0.3-4 pn libreoffice-qt5 ii libreoffice-writer 1:7.0.3-4 ii mythes-en-us1:7.0.1-1 pn orca pn synaptic ii system-config-printer 1.5.12-1 pn xsane task-lxqt-desktop suggests no packages.
Bug#960123: fastboot -w fails with "mke2fs failed: 1"
Package: fastboot Version: 1:8.1.0+r23-5 Severity: normal Dear Maintainer, I connected my Fairphone 3 to my computer using USB and tried using "fastboot -w". The command failed with the following error message: Invalid erase-block-size 512: must be a power of 2 and at least 4096. Invalid logical-block-size 512: must be a power of 2 and at least 4096. mke2fs 1.45.6 (20-Mar-2020) /tmp/TemporaryFile-GmJtWH: Unimplemented ext2 library function while setting up superblock /usr/lib/android-sdk/platform-tools/mke2fs failed with status 1 mke2fs failed: 1 error: Cannot generate image for userdata I then retried with the version of fastboot that I downloaded from developer.android.com and it worked fine. -- System Information: Debian Release: bullseye/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.6.0-1-amd64 (SMP w/16 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=el_GR.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages fastboot depends on: ii android-libadb 1:8.1.0+r23-5 ii android-libbase1:8.1.0+r23-5 ii android-libcutils 1:8.1.0+r23-5 ii android-libf2fs-utils 8.1.0+r23-2 ii android-libsparse 1:8.1.0+r23-5 ii android-libutils 1:8.1.0+r23-5 ii android-libziparchive 1:8.1.0+r23-5 ii libc6 2.30-7 ii libgcc-s1 [libgcc1]10.1.0-1 ii libgcc11:10.1.0-1 ii libstdc++6 10.1.0-1 Versions of packages fastboot recommends: ii android-sdk-platform-tools 27.0.0+12 fastboot suggests no packages. -- no debconf information
Bug#913395: seabios: Build coreboot-targeted binaries
(Accidentally hit "reply" instead of "reply all", resending) On 10/11/2018 16.10, Michael Tokarev wrote: > > I was planning to remove seabios source package completely, and instead > build all qemu-related firmware from qemu source (which includes seabios > too), - for now the only user of seabios in debian is qemu. > Do you have other uses of seabios? Hi and thanks for your quick reply! I was actually planning to start adding coreboot packages to Debian, initially for a very limited set of platforms. The thing is that it's not easy at all to build seabios from inside coreboot. It either requires internet access at build time, which makes it impossible to properly debianise, or needs tweaking in coreboot's already extremely convoluted build system. Having a seabios image already in the system and picking it up directly as a payload is by far the easiest way to include it. signature.asc Description: OpenPGP digital signature
Bug#913395: seabios: Build coreboot-targeted binaries
Package: seabios
Version: 1.11.1-1
Severity: wishlist
Tags: patch
Dear Maintainer,
It would be nice if seabios could build (and install) coreboot-targeted
binaries.
I achieved that with the patch I am attaching (against debian/rules).
Best regards,
Vivia Nikolaidou
-- System Information:
Debian Release: buster/sid
APT prefers unstable-debug
APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.18.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=el_GR.UTF-8 (charmap=UTF-8), LANGUAGE=
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
-- no debconf information
*** seabios-1.11.1/debian/rules Tue Apr 10 07:59:17 2018
--- seabios-1.11.1-coreboot/debian/rulesSat Nov 10 13:01:05 2018
***
*** 12,18
VGABIOSES = cirrus stdvga virtio vmware qxl isavga
VGABIOS_TARGETS = $(addprefix build/vgabios-, $(addsuffix .bin, $(VGABIOSES)))
! BIOS_TARGETS = build/bios.bin build/bios-256k.bin ${VGABIOS_TARGETS}
BUILD_TARGETS = $(BIOS_TARGETS) build/optionrom-stamp
build build-arch build-indep: $(BUILD_TARGETS)
--- 12,18
VGABIOSES = cirrus stdvga virtio vmware qxl isavga
VGABIOS_TARGETS = $(addprefix build/vgabios-, $(addsuffix .bin, $(VGABIOSES)))
! BIOS_TARGETS = build/bios.bin build/bios-256k.bin build/bios-coreboot.bin
${VGABIOS_TARGETS}
BUILD_TARGETS = $(BIOS_TARGETS) build/optionrom-stamp
build build-arch build-indep: $(BUILD_TARGETS)
***
*** 37,47
--- 37,68
rm -f $@; ln $$d/$1.bin $@
endef
+ # common rule to build any bios.
+ # $1: config options to put into .config without CONFIG_ prefix
+ # $@: where to put output; build dir will be $(basename $@)
+ define build-bios-coreboot
+ +set -e; d=$(basename $@); \
+ if [ ! -e $$d/.config.old ]; then \
+ rm -rf $$d; mkdir -p $$d; \
+ for x in $1; do \
+ case $$x in \
+(*=n) echo "# CONFIG_$${x%=*} is not set";; \
+(*) echo CONFIG_$$x;; \
+ esac; \
+ done > $$d/.config; \
+ $(MAKE) -j1 KCONFIG_CONFIG=$(CURDIR)/$$d/.config OUT=$$d/ olddefconfig; \
+ fi; \
+ $(MAKE) KCONFIG_CONFIG=$(CURDIR)/$$d/.config OUT=$$d/
EXTRAVERSION="-${DEB_VERSION_RELEASE}"; \
+ rm -f $@; ln $$d/bios.bin.elf $@
+ endef
+
build/bios.bin:
# A stripped-down version of bios, to fit in 128Kb, for qemu <= 1.7
$(call build-bios,bios,QEMU=y ROM_SIZE=128 PVSCSI=n BOOTSPLASH=n
USB_OHCI=n USB_XHCI=n USB_UAS=n XEN=n SDCARD=n TCGBIOS=n MPT_SCSI=n PVSCSI=n
NVME=n USE_SMM=n VGAHOOKS=n)
build/bios-256k.bin:
$(call build-bios,bios,QEMU=y ROM_SIZE=256)
+ build/bios-coreboot.bin:
+ $(call build-bios-coreboot,COREBOOT=y DEBUG_SERIAL=y VGA_COREBOOT=y
BUILD_BGAVIOS=y)
# upstream ships .hex files in tarball, result of iasl compilation
# ensure it is actually built during build
Bug#904702: ITP: megadown -- Bash script for downloading files from mega.nz and megacrypter
Package: wnpp Severity: wishlist Owner: Vivia Nikolaidou * Package name: megadown Version : 0~20180705-+git83c53dd Upstream Author : A. L. Vivar * URL : https://github.com/tonikelope/megadown * License : GPLv3 Programming Lang: Bash, Python Description : Bash script for downloading files from mega.nz and megacrypter This package contains a Bash script, and a Python helper, which download files from mega.nz and megacrypter. It can be useful for embedding inside other scripts that programmatically download stuff from mega.nz. I am planning to maintain it closely with Debian Developers associated with PureOS. I am not seeking a sponsor at this time.
Bug#901462: seabios: SeaBIOS fails to build from source on sid and testing
>From this error message:
build/src/fw/ssdt-misc.dsl.i 4: DefinitionBlock ("ssdt-misc.aml",
"SSDT", 0x01, "BXPC", "BXSSDTSUSP", 0x1)
Error6155 -
Invalid OEM Table ID ^ (Length cannot exceed 8 characters)
Examining the shipped .hex files, I noticed that the TableID string is
truncated to 8 characters only, e.g. in ssdt-misc.hex :
static unsigned char ssdp_misc_aml[] = {
0x53, 0x53, 0x44, 0x54, 0x62, 0x01, 0x00, 0x00,
0x01, 0x7f, 0x42, 0x58, 0x50, 0x43, 0x00, 0x00,
0x42, 0x58, 0x53, 0x53, 0x44, 0x54, 0x53, 0x55,
0x01, 0x00, 0x00, 0x00, 0x49, 0x4e, 0x54, 0x4c,
Therefore, I assume that the TableID argument can safely be truncated.
This patch fixes the build for me. I confirmed by building on Debian
stable with and without the patch and comparing the .hex files I got
in both cases, they are identical.
diff --git a/src/fw/ssdt-misc.dsl b/src/fw/ssdt-misc.dsl
index acc850e..d1d2c9e 100644
--- a/src/fw/ssdt-misc.dsl
+++ b/src/fw/ssdt-misc.dsl
@@ -1,6 +1,6 @@
ACPI_EXTRACT_ALL_CODE ssdp_misc_aml
-DefinitionBlock ("ssdt-misc.aml", "SSDT", 0x01, "BXPC", "BXSSDTSUSP", 0x1)
+DefinitionBlock ("ssdt-misc.aml", "SSDT", 0x01, "BXPC", "BXSSDTSU", 0x1)
{
/
diff --git a/src/fw/ssdt-pcihp.dsl b/src/fw/ssdt-pcihp.dsl
index cb24c11..518a5eb 100644
--- a/src/fw/ssdt-pcihp.dsl
+++ b/src/fw/ssdt-pcihp.dsl
@@ -1,6 +1,6 @@
ACPI_EXTRACT_ALL_CODE ssdp_pcihp_aml
-DefinitionBlock ("ssdt-pcihp.aml", "SSDT", 0x01, "BXPC", "BXSSDTPCIHP", 0x1)
+DefinitionBlock ("ssdt-pcihp.aml", "SSDT", 0x01, "BXPC", "BXSSDTPC", 0x1)
{
/
On 13 June 2018 at 16:49, Vivia Nikolaidou wrote:
> Package: seabios
> Version: 1.11.1-1
> Severity: serious
> Justification: Policy 4.15
>
> Dear Maintainer,
>
> SeaBIOS fails to build from source when building on sid and testing.
>
> The error message is:
>
> =
> Compiling IASL src/fw/q35-acpi-dsdt.hex
> build/src/fw/q35-acpi-dsdt.dsl.i446: Method(CPEJ, 2, NotSerialized) {
> Remark 2146 - Method Argument is never used ^ (Arg0)
>
> build/src/fw/q35-acpi-dsdt.dsl.i446: Method(CPEJ, 2, NotSerialized) {
> Remark 2146 - Method Argument is never used ^ (Arg1)
>
> ASL Input: build/src/fw/q35-acpi-dsdt.dsl.i - 515 lines, 28284 bytes, 413
> keywords
> AML Output:build/src/fw/q35-acpi-dsdt.aml - 7506 bytes, 239 named
> objects, 174 executable opcodes
> Listing File: build/src/fw/q35-acpi-dsdt.lst - 259530 bytes
> Hex Dump: build/src/fw/q35-acpi-dsdt.hex - 70865 bytes
>
> Compilation complete. 0 Errors, 0 Warnings, 2 Remarks, 445 Optimizations
> Compiling IASL src/fw/ssdt-misc.hex
> build/src/fw/ssdt-misc.dsl.i 4: DefinitionBlock ("ssdt-misc.aml",
> "SSDT", 0x01, "BXPC", "BXSSDTSUSP", 0x1)
> Error6155 -
> Invalid OEM Table ID ^ (Length cannot exceed 8 characters)
>
> ASL Input: build/src/fw/ssdt-misc.dsl.i - 102 lines, 2567 bytes, 35
> keywords
> Listing File: build/src/fw/ssdt-misc.lst - 8417 bytes
> Hex Dump: build/src/fw/ssdt-misc.hex - 4098 bytes
> =
>
> Older SeaBIOS releases are also failing. Workaround is to build the package
> using a stretch chroot.
>
> -- System Information:
> Debian Release: buster/sid
> APT prefers unstable-debug
> APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1,
> 'experimental-debug'), (1, 'experimental')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
>
> Kernel: Linux 4.16.0-2-amd64 (SMP w/20 CPU cores)
> Locale: LANG=el_GR.UTF-8, LC_CTYPE=el_GR.UTF-8 (charmap=UTF-8), LANGUAGE=
> (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
> LSM: AppArmor: enabled
>
> -- no debconf information
Bug#901547: seabios: Source tarball ships compiled binaries
On 15 June 2018 at 14:43, Chris Lamb wrote: > Michael Tokarev wrote: > >> We ensure the pre-built files are not used during build, and the source >> of them is included, so we comply to DFSG. > > Indeed, I don't see a DFSG violation here.. Vivia? OK then, seems I had misunderstood the DFSG. Sorry for the noise, feel free to close this one.
Bug#901547: seabios: Source tarball ships compiled binaries
Package: seabios
Version: 1.11.1-1
Severity: serious
Justification: Policy 2.1.2
Dear Maintainer,
I just noticed that the source tarball of seabios includes some compiled
binaries:
$ ls src/fw/*.hex
src/fw/acpi-dsdt.hex src/fw/ssdt-misc.hex src/fw/ssdt-pcihp.hex src/fw/ssdt-
proc.hex
In debian/rules, these files are moved away and rebuilt:
# move out shipped .hex files and rebuild them
mkdir -p build/src/fw
for f in ${FW_FILES}; do [ -f $$f.sav -o ! -f $$f ] || mv $$f $$f.sav;
done
rm -f ${FW_FILES}
make OUT=build/ ${FW_FILES}
touch $@
They should not be shipped at all, they should just be built when packaging.
-- System Information:
Debian Release: buster/sid
APT prefers unstable-debug
APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.16.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=el_GR.UTF-8 (charmap=UTF-8), LANGUAGE=
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
-- no debconf information
Bug#901462: seabios: SeaBIOS fails to build from source on sid and testing
Package: seabios
Version: 1.11.1-1
Severity: serious
Justification: Policy 4.15
Dear Maintainer,
SeaBIOS fails to build from source when building on sid and testing.
The error message is:
=
Compiling IASL src/fw/q35-acpi-dsdt.hex
build/src/fw/q35-acpi-dsdt.dsl.i446: Method(CPEJ, 2, NotSerialized) {
Remark 2146 - Method Argument is never used ^ (Arg0)
build/src/fw/q35-acpi-dsdt.dsl.i446: Method(CPEJ, 2, NotSerialized) {
Remark 2146 - Method Argument is never used ^ (Arg1)
ASL Input: build/src/fw/q35-acpi-dsdt.dsl.i - 515 lines, 28284 bytes, 413
keywords
AML Output:build/src/fw/q35-acpi-dsdt.aml - 7506 bytes, 239 named objects,
174 executable opcodes
Listing File: build/src/fw/q35-acpi-dsdt.lst - 259530 bytes
Hex Dump: build/src/fw/q35-acpi-dsdt.hex - 70865 bytes
Compilation complete. 0 Errors, 0 Warnings, 2 Remarks, 445 Optimizations
Compiling IASL src/fw/ssdt-misc.hex
build/src/fw/ssdt-misc.dsl.i 4: DefinitionBlock ("ssdt-misc.aml", "SSDT",
0x01, "BXPC", "BXSSDTSUSP", 0x1)
Error6155 -
Invalid OEM Table ID ^ (Length cannot exceed 8 characters)
ASL Input: build/src/fw/ssdt-misc.dsl.i - 102 lines, 2567 bytes, 35 keywords
Listing File: build/src/fw/ssdt-misc.lst - 8417 bytes
Hex Dump: build/src/fw/ssdt-misc.hex - 4098 bytes
=
Older SeaBIOS releases are also failing. Workaround is to build the package
using a stretch chroot.
-- System Information:
Debian Release: buster/sid
APT prefers unstable-debug
APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1,
'experimental-debug'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.16.0-2-amd64 (SMP w/20 CPU cores)
Locale: LANG=el_GR.UTF-8, LC_CTYPE=el_GR.UTF-8 (charmap=UTF-8), LANGUAGE=
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
-- no debconf information
Bug#900497: libgl1-mesa-dri: Causes random freezes in plasmashell
Package: libgl1-mesa-dri Severity: critical Tags: patch upstream Justification: breaks unrelated software Dear Maintainer, Currently, with the mesa driver and xorg 1.20, plasmashell randomly freezes every few seconds. The bug has been reported as: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900352 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900149 but it is actually a bug in mesa. It is fixed by this upstream commit: https://cgit.freedesktop.org/mesa/mesa/commit/?id=fe2edb25dd5628c395a65b60998f11e839d2b458 I just applied said patch locally and rebuilt mesa, and I can confirm that it fixes the issue. Best regards, Vivia Nikolaidou -- Package-specific info: glxinfo: name of display: :0 display: :0 screen: 0 direct rendering: Yes server glx vendor string: SGI server glx version string: 1.4 server glx extensions: GLX_ARB_create_context, GLX_ARB_create_context_no_error, GLX_ARB_create_context_profile, GLX_ARB_create_context_robustness, GLX_ARB_fbconfig_float, GLX_ARB_framebuffer_sRGB, GLX_ARB_multisample, GLX_EXT_create_context_es2_profile, GLX_EXT_create_context_es_profile, GLX_EXT_fbconfig_packed_float, GLX_EXT_framebuffer_sRGB, GLX_EXT_import_context, GLX_EXT_libglvnd, GLX_EXT_no_config_context, GLX_EXT_texture_from_pixmap, GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_INTEL_swap_event, GLX_MESA_copy_sub_buffer, GLX_OML_swap_method, GLX_SGIS_multisample, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, GLX_SGIX_visual_select_group, GLX_SGI_make_current_read, GLX_SGI_swap_control client glx vendor string: Mesa Project and SGI client glx version string: 1.4 client glx extensions: GLX_ARB_context_flush_control, GLX_ARB_create_context, GLX_ARB_create_context_profile, GLX_ARB_create_context_robustness, GLX_ARB_fbconfig_float, GLX_ARB_framebuffer_sRGB, GLX_ARB_get_proc_address, GLX_ARB_multisample, GLX_EXT_buffer_age, GLX_EXT_create_context_es2_profile, GLX_EXT_create_context_es_profile, GLX_EXT_fbconfig_packed_float, GLX_EXT_framebuffer_sRGB, GLX_EXT_import_context, GLX_EXT_texture_from_pixmap, GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_INTEL_swap_event, GLX_MESA_copy_sub_buffer, GLX_MESA_multithread_makecurrent, GLX_MESA_query_renderer, GLX_MESA_swap_control, GLX_OML_swap_method, GLX_OML_sync_control, GLX_SGIS_multisample, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, GLX_SGIX_visual_select_group, GLX_SGI_make_current_read, GLX_SGI_swap_control, GLX_SGI_video_sync GLX version: 1.4 GLX extensions: GLX_ARB_create_context, GLX_ARB_create_context_profile, GLX_ARB_create_context_robustness, GLX_ARB_fbconfig_float, GLX_ARB_framebuffer_sRGB, GLX_ARB_get_proc_address, GLX_ARB_multisample, GLX_EXT_buffer_age, GLX_EXT_create_context_es2_profile, GLX_EXT_create_context_es_profile, GLX_EXT_fbconfig_packed_float, GLX_EXT_framebuffer_sRGB, GLX_EXT_import_context, GLX_EXT_texture_from_pixmap, GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_INTEL_swap_event, GLX_MESA_copy_sub_buffer, GLX_MESA_multithread_makecurrent, GLX_MESA_query_renderer, GLX_MESA_swap_control, GLX_OML_swap_method, GLX_OML_sync_control, GLX_SGIS_multisample, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, GLX_SGIX_visual_select_group, GLX_SGI_make_current_read, GLX_SGI_swap_control, GLX_SGI_video_sync Extended renderer info (GLX_MESA_query_renderer): Vendor: Intel Open Source Technology Center (0x8086) Device: Mesa DRI Intel(R) HD Graphics 5300 (Broadwell GT2) (0x161e) Version: 18.1.0 Accelerated: yes Video memory: 3072MB Unified memory: yes Preferred profile: core (0x1) Max core profile version: 4.5 Max compat profile version: 3.0 Max GLES1 profile version: 1.1 Max GLES[23] profile version: 3.1 OpenGL vendor string: Intel Open Source Technology Center OpenGL renderer string: Mesa DRI Intel(R) HD Graphics 5300 (Broadwell GT2) OpenGL core profile version string: 4.5 (Core Profile) Mesa 18.1.0 OpenGL core profile shading language version string: 4.50 OpenGL core profile context flags: (none) OpenGL core profile profile mask: core profile OpenGL core profile extensions: GL_3DFX_texture_compression_FXT1, GL_AMD_conservative_depth, GL_AMD_draw_buffers_blend, GL_AMD_seamless_cubemap_per_texture, GL_AMD_shader_trinary_minmax, GL_AMD_vertex_shader_layer, GL_AMD_vertex_shader_viewport_index, GL_ANGLE_texture_compression_dxt3, GL_ANGLE_texture_compression_dxt5, GL_APPLE_object_purgeable, GL_ARB_ES2_compatibility, GL_ARB_ES3_1_compatibility, GL_ARB_ES3_2_compatibility, GL_ARB_ES3_compatibility, GL_ARB_arrays_of_arrays, GL_ARB_base_instance, GL_ARB_blend_func_extended, GL_ARB_buffer_storage, GL_ARB_clear_buffer_object, GL_ARB_clear_texture, GL_ARB_clip_control, GL_ARB_compressed_texture_pixel_storage, GL_ARB_compute_shader, GL_ARB_conditional_render_inverted
Bug#894458: python3-distutils: fails to upgrade from sid
Package: python3-distutils Version: 3.6.5~rc1-3 Severity: serious Justification: Policy 7.6.1 Dear Maintainer, When trying to do a routine dist-upgrade, the package python3-distutils fails with the following error message: Unpacking python3-distutils (3.6.5-1) over (3.6.5~rc1-3) ... dpkg: error processing archive /var/cache/apt/archives/python3-distutils_3.6.5-1_all.deb (--unpack): trying to overwrite '/usr/lib/python3.6/distutils/__init__.py', which is also in package libpython3.6-stdlib:amd64 3.6.5-1 -- System Information: Debian Release: buster/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.15.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=el_GR.UTF-8 (charmap=UTF-8), LANGUAGE= (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages python3-distutils depends on: ii python3 3.6.5~rc1-1 iu python3-lib2to3 3.6.5-1 python3-distutils recommends no packages. python3-distutils suggests no packages. -- no debconf information
Bug#889994: sogo: GPG signed emails are not displayed
Package: sogo Version: 3.2.6-2 Severity: normal Tags: upstream Dear Maintainer, The SOGo version in stable (3.2.6) has a bug where PGP signed emails are not displayed properly; only the headers are displayed, but the body appears to be empty. According to the upstream bug report, it is fixed in version 3.2.10: https://sogo.nu/bugs/bug_relationship_graph.php?bug_id=4201&graph=relation Please backport the relevant fix from testing to stable. Thank you very much, Vivia Nikolaidou -- System Information: Debian Release: 9.3 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.9.0-5-amd64 (SMP w/2 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=el_GR.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages sogo depends on: ii adduser 3.115 ii init-system-helpers 1.48 ii libc62.24-11+deb9u1 ii libcurl3-gnutls 7.52.1-5+deb9u4 ii libgcc1 1:6.3.0-18 ii libglib2.0-0 2.50.3-2 ii libgnustep-base1.24 1.24.9-3.1 ii libgnutls30 3.5.8-5+deb9u3 ii liblasso32.5.0-5+b1 ii libmemcached11 1.0.18-4.1 ii libobjc4 6.3.0-18 ii libsbjson2.3 2.3.2-3 ii libsope1 3.2.6-1 ii lsb-base 9.20161125 ii sogo-common 3.2.6-2 ii systemd 232-25+deb9u1 ii tmpreaper1.6.13+nmu1+b2 ii zip 3.0-11+b1 Versions of packages sogo recommends: ii memcached 1.4.33-1 Versions of packages sogo suggests: ii default-mysql-server1.0.2 ii mariadb-server-10.1 [virtual-mysql-server] 10.1.26-0+deb9u1 -- Configuration Files: /etc/sogo/sogo.conf [Errno 13] Permission denied: '/etc/sogo/sogo.conf' -- no debconf information
Bug#795593: systemsettings: Also happens with Alt+F1 Activate Application Launcher, but it also implicitly maps the Win key
Dear Maintainer, The initial bug reported should be now fixed: https://bugs.kde.org/show_bug.cgi?id=347352 My bug is actually a combination of two different issues, both upstream, and both different from the one initially reported here. One is this: https://bugs.kde.org/show_bug.cgi?id=346918 which is still under discussion upstream. The other is not a bug, just an undocumented feature: https://forum.kde.org/viewtopic.php?t=137574 Dumping more information in case someone else runs into this bug: chmod -w ~/.config/kglobalshortcutsrc doesn't work, the file still manages to get overwritten. Making a small shell script in .config/autostart-scripts that would sed away the offending input in ~/.config/kglobalshortcutsrc also doesn't work, because the substitution apparently happens after the script is executed. In any case, this bug can be closed. Maybe a different one can be opened for the Alt+F1 shortcut. Best regards, Vivia Nikolaidou On 8 February 2018 at 23:55, Vivia Nikolaidou wrote: > Package: systemsettings > Version: 4:5.10.5-2 > Followup-For: Bug #795593 > > Dear Maintainer, > > I have this with the Alt+F1 shortcut to Activate Application Launcher. > However, what I actually care about is the Left Win button. For some reason, > the Left Win button is also set to Activate Application Launcher even though > systemsettings claims it's Alt+F1. I go to systemsettings, set Activate > Application Launcher to None, then the Left Win key is also free for me to > use as Compose. I have tried setting it to a couple of other values apart > from Alt+F1 and they also seem to hijack my Left Win key without asking me. > > -- System Information: > Debian Release: buster/sid > APT prefers unstable-debug > APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, > 'experimental-debug'), (1, 'experimental') > Architecture: amd64 (x86_64) > Foreign Architectures: i386 > > Kernel: Linux 4.14.0-3-amd64 (SMP w/20 CPU cores) > Locale: LANG=el_GR.UTF-8, LC_CTYPE=el_GR.UTF-8 (charmap=UTF-8), > LANGUAGE=en_US (charmap=UTF-8) > Shell: /bin/sh linked to /bin/dash > Init: systemd (via /run/systemd/system) > LSM: AppArmor: enabled > > Versions of packages systemsettings depends on: > pn kio > ii libc6 2.26-6 > pn libkf5auth5 > pn libkf5completion5 > pn libkf5configcore5 > pn libkf5configgui5 > pn libkf5configwidgets5 > ii libkf5coreaddons5 5.37.0-3 > pn libkf5dbusaddons5 > pn libkf5i18n5 > pn libkf5iconthemes5 > pn libkf5itemviews5 > pn libkf5kcmutils5 > pn libkf5khtml5 > pn libkf5kiowidgets5 > pn libkf5service-bin > pn libkf5service5 > pn libkf5widgetsaddons5 > pn libkf5windowsystem5 > pn libkf5xmlgui5 > ii libqt5core5a 5.9.2+dfsg-7 > ii libqt5dbus5 5.9.2+dfsg-7 > ii libqt5gui55.9.2+dfsg-7 > ii libqt5widgets55.9.2+dfsg-7 > ii libstdc++67.3.0-1 > pn qml-module-org-kde-kirigami2 > pn qml-module-qtquick-controls > pn qml-module-qtquick-layouts > pn qml-module-qtquick2 > > systemsettings recommends no packages. > > systemsettings suggests no packages. > > -- no debconf information
Bug#795593: systemsettings: Also happens with Alt+F1 Activate Application Launcher, but it also implicitly maps the Win key
Package: systemsettings Version: 4:5.10.5-2 Followup-For: Bug #795593 Dear Maintainer, I have this with the Alt+F1 shortcut to Activate Application Launcher. However, what I actually care about is the Left Win button. For some reason, the Left Win button is also set to Activate Application Launcher even though systemsettings claims it's Alt+F1. I go to systemsettings, set Activate Application Launcher to None, then the Left Win key is also free for me to use as Compose. I have tried setting it to a couple of other values apart from Alt+F1 and they also seem to hijack my Left Win key without asking me. -- System Information: Debian Release: buster/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.14.0-3-amd64 (SMP w/20 CPU cores) Locale: LANG=el_GR.UTF-8, LC_CTYPE=el_GR.UTF-8 (charmap=UTF-8), LANGUAGE=en_US (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages systemsettings depends on: pn kio ii libc6 2.26-6 pn libkf5auth5 pn libkf5completion5 pn libkf5configcore5 pn libkf5configgui5 pn libkf5configwidgets5 ii libkf5coreaddons5 5.37.0-3 pn libkf5dbusaddons5 pn libkf5i18n5 pn libkf5iconthemes5 pn libkf5itemviews5 pn libkf5kcmutils5 pn libkf5khtml5 pn libkf5kiowidgets5 pn libkf5service-bin pn libkf5service5 pn libkf5widgetsaddons5 pn libkf5windowsystem5 pn libkf5xmlgui5 ii libqt5core5a 5.9.2+dfsg-7 ii libqt5dbus5 5.9.2+dfsg-7 ii libqt5gui55.9.2+dfsg-7 ii libqt5widgets55.9.2+dfsg-7 ii libstdc++67.3.0-1 pn qml-module-org-kde-kirigami2 pn qml-module-qtquick-controls pn qml-module-qtquick-layouts pn qml-module-qtquick2 systemsettings recommends no packages. systemsettings suggests no packages. -- no debconf information
Bug#802314: plasma-workspace: plasmashell crashes when adding widgets to desktop
Hi Maximiliano and thanks for your reply! On 8 March 2017 at 15:14, Maximiliano Curia wrote: > > Can you test this issue again against the current versions of kde > plasma-workspace? I just did - it's indeed fixed now. Thanks a lot! Best regards, Vivia
Bug#837646: vim-youcompleteme: Missing python dependencies
Package: vim-youcompleteme Version: 0+20160327+git1b76af4-1 Severity: important Dear Maintainer, After yesterday's upgrade, vim-youcompleteme didn't work anymore. It was spitting errors into the bottom part of vim complaining about missing python modules. I manually apt-get installed python3-future and python3-requests- futures and then it worked. Not sure if there are any further modules missing that I happened to have installed already. Best regards, Vivia Nikolaidou -- System Information: Debian Release: stretch/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.7.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=el_GR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages vim-youcompleteme depends on: ii python-concurrent.futures [python-futures] 3.0.5-2 ii python-requests 2.10.0-2 ii python-requests-futures 0.9.7-1 pn python:any ii vim-gtk [vim-python]2:7.4.2347-1 ii vim-gtk3 [vim-python] 2:7.4.2347-1 ii ycmd0+20160327+gitc3e6904-1+b1 Versions of packages vim-youcompleteme recommends: ii vim-addon-manager 0.5.5 vim-youcompleteme suggests no packages. -- no debconf information
Bug#835922: network-manager: NetworkManager 1.4.0-1 breaks wifi
Package: network-manager Version: 1.4.0-3 Severity: grave Tags: upstream Justification: renders package unusable Dear Maintainer, I upgraded network-manager to 1.4.0-3 this morning and my WiFi stopped working. After searching for a bit, I found that it is an upstream bug, which has already been fixed: https://bugzilla.gnome.org/show_bug.cgi?id=770456 Downgrading network-manager to 1.2.4-2 (package from testing) made WiFi work again. Best regards, Vivia Nikolaidou -- System Information: Debian Release: stretch/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.6.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=el_GR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages network-manager depends on: ii adduser3.115 ii dbus 1.10.10-1 ii init-system-helpers1.42 ii libaudit1 1:2.6.6-1 ii libbluetooth3 5.36-1+b2 ii libc6 2.23-5 ii libglib2.0-0 2.48.1-3 ii libgnutls303.5.3-3 ii libgudev-1.0-0 230-3 ii libmm-glib01.6.0-1 ii libndp01.6-1 ii libnewt0.520.52.18-3 ii libnl-3-2003.2.27-1 ii libnm0 1.4.0-3 ii libpam-systemd 231-5 ii libpolkit-agent-1-00.105-16 ii libpolkit-gobject-1-0 0.105-16 ii libreadline6 6.3-8+b4 ii libselinux12.5-3 ii libsoup2.4-1 2.54.1-1 ii libsystemd0231-5 ii libteamdctl0 1.26-1 ii libuuid1 2.28.1-1 ii lsb-base 9.20160629 ii policykit-10.105-16 ii udev 231-5 ii wpasupplicant 2.5-2+v2.4-2 Versions of packages network-manager recommends: ii crda 3.13-1+b1 ii dnsmasq-base 2.76-3 ii iptables 1.6.0-3 ii iputils-arping 3:20150815-2 ii isc-dhcp-client 4.3.4-1 ii modemmanager 1.6.0-1 ii ppp 2.4.7-1+3 Versions of packages network-manager suggests: pn libteam-utils -- no debconf information
Bug#802830: amsn: non-DFSG file licensed under APSL-1.1
Hi and thanks for reporting the bug. I am the maintainer of aMSN. The whole utils/macosx directory can go away, because obviously there's no use for it on Linux (It should have been removed at the first place). However, given that now aMSN is obsolete, I've requested for the whole package to be removed [1]. Thanks, Vivia [1]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=803288 On 24 October 2015 at 00:46, Dmitry Smirnov wrote: > Source: amsn > Version: 0.98.9-1 > Severity: important > > According to its header, the following file is licensed as non-DFSG > APSL-1.1 [1] license: > > utils/macosx/make_dmg/openUp.c > > Also right next to it there is a pre-built binary > "utils/macosx/make_dmg/openUp" which would be nice to remove from tarball > as well. > > Please investigate. > > [1]: > https://wiki.debian.org/DFSGLicenses#Apple_Public_Source_License_.28APSL.29 > > -- > Regards, > Dmitry Smirnov > GPG key : 4096R/53968D1B
Bug#803288: RM: amsn -- ROM; deprecated, servers down, can't be used anymore
Package: ftp.debian.org Severity: normal Hi, please remove amsn (and amsn-data). It was relying on using Microsoft's Windows Live Messenger servers to connect. However, Microsoft deprecated that service in favor of Skype. Therefore, amsn can now be removed, as it cannot be used anymore. Thanks!
Bug#802314: plasma-workspace: plasmashell crashes when adding widgets to desktop
Package: plasma-workspace Version: 4:5.4.2-1 Severity: important Dear Maintainer, I want to add a widget (any widget) to my desktop, but when I try to do so, plasmashell crashes. Steps to reproduce: 1) Unlock widgets (if locked) 2) Right click the desktop 3) Select "Add widgets..." 4) Select a widget from the list that appears on the left side of the screen 5) Drag it to the desktop I then receive a plasmashell crash with the following backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7ffab6ad0940 (LWP 1482))] Thread 6 (Thread 0x7ffa9b1d2700 (LWP 1527)): #0 __libc_enable_asynccancel () at ../nptl/sysdeps/unix/sysv/linux/x86_64/cancellation.S:65 #1 0x7ffab1271522 in poll () at ../sysdeps/unix/syscall-template.S:81 #2 0x7ffaae0311dc in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7ffaae0312ec in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7ffab1b90e4b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7ffab1b372ca in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7ffab1955374 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7ffab418a055 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #8 0x7ffab195a25e in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7ffab0a7a0a4 in start_thread (arg=0x7ffa9b1d2700) at pthread_create.c:309 #10 0x7ffab127a06d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 Thread 5 (Thread 0x7ffa91cf7700 (LWP 1548)): #0 0x7ffab1b90680 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #1 0x7ffaae030c11 in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7ffaae031180 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7ffaae0312ec in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7ffab1b90e4b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7ffab1b372ca in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7ffab1955374 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7ffab418a055 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #8 0x7ffab195a25e in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7ffab0a7a0a4 in start_thread (arg=0x7ffa91cf7700) at pthread_create.c:309 #10 0x7ffab127a06d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 Thread 4 (Thread 0x7ffa8b3bc700 (LWP 1574)): #0 0x7ffab1b8ee3c in QTimerInfoList::timerWait(timespec&) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #1 0x7ffab1b9022e in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7ffaae03076d in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7ffaae03110b in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7ffaae0312ec in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7ffab1b90e4b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7ffab1b372ca in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7ffab1955374 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7ffab418a055 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #9 0x7ffab195a25e in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7ffab0a7a0a4 in start_thread (arg=0x7ffa8b3bc700) at pthread_create.c:309 #11 0x7ffab127a06d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 Thread 3 (Thread 0x7ffa89b27700 (LWP 1602)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7ffab6531144 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #2 0x7ffab6531189 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #3 0x7ffab0a7a0a4 in start_thread (arg=0x7ffa89b27700) at pthread_create.c:309 #4 0x7ffab127a06d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 Thread 2 (Thread 0x7ffa82ff2700 (LWP 1675)): #0 0x7ffaae075859 in g_mutex_lock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7ffaae0302b4 in g_main_context_release () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7ffaae031196 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7ffaae0312ec in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7ffab1b90e4b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7ffab1b372ca in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6
Bug#759288: RM: libmimic -- ROM; obsolete
On Sat, 03 Oct 2015 19:08:52 +0100 Sebastian =?ISO-8859-1?Q?Dr=F6ge?= wrote: > On Mon, 25 Aug 2014 23:12:54 +0200 Luciano Bello wrote: > > > Please, remove src:libmimic, since nobody is using it and it is used to be > > necessary for some code which found other ways. The code is old, the upstream is > > dead. > > is there any actual reason to remove it? The code is old but it seems > to work well enough. Unless it's completely buggy or similar, I don't > see a reason for it to be removed. I actually see a reason for it to NOT be removed - aka, a valid use case. I am a developer of (now obsolete) aMSN. We used libmimic for the video conferencing function. We also had a feature called "webcam logs" - aka, dump the libmimic-encoded video file into the hard drive and play it back later. People would then ask how to play back these files outside of aMSN, and we'd tell them to use GStreamer to play them back and/or convert them to another, more useful format. We wanted to keep our code cross-platform in a simpler way, so instead of using the system-wide libmimic, we'd just ship our own variant in the code. Well, now that the servers are dead, aMSN is pretty much obsolete. Therefore, one does need the system-wide libmimic in order to access these old webcam logs. We still do occasionally get people asking how to do that. On the other hand, the code has always worked well enough for us, and in fact it's one of the most stable pieces of code that I've ever seen. We only ever found one bug, encountered by one single person on a Mac, due to endianness - but the person certainly wasn't the first person to use libmimic on a big endian machine. So, if the package isn't really breaking anything or having bugs, and if there are some valid use cases for it, I think it would be wrong to have it removed.
Bug#779208: debian-installer: Remove /dev/sdX installer entry from fstab
Oh it's already fixed, cool! Thanks a lot :) On 25 February 2015 at 15:24, Cyril Brulebois wrote: > Hi, > > and thanks for your report. > > Vivia Nikolaidou (2015-02-25): >> Package: debian-installer >> Severity: important >> Tags: d-i >> >> Hello, >> >> I noticed that debian-installer leaves a /dev/sdX entry in /etc/fstab >> inside the newly installed system. This entry corresponds to the >> medium that Debian was installed from. > > This is fixed through: > https://lists.debian.org/debian-boot/2015/01/msg00361.html > > This update will be merged into RC2. > > I'm closing this bug report accordingly. ;) > > Mraw, > KiBi. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#779208: debian-installer: Remove /dev/sdX installer entry from fstab
It is not clear in my initial email, so I'm writing back with a clarification: The /dev/sdc entries that I pasted from fstab were commented manually by us. The installer had left the uncommented entries in fstab. On 25 February 2015 at 15:13, Vivia Nikolaidou wrote: > Package: debian-installer > Severity: important > Tags: d-i > > Hello, > > I noticed that debian-installer leaves a /dev/sdX entry in /etc/fstab inside > the newly installed system. This entry corresponds to the medium that Debian > was installed from. In my case, I just installed Debian stable on one of our > servers (not the machine I am writing from, so please disregard the System > Information below). The installer left these lingering entries on fstab: > > #/dev/sdc1 /media/usb0 autorw,user,noauto 0 0 > #/dev/sdc2 /media/usb1 autorw,user,noauto 0 0 > > It was a machine with several hard drives and RAID. Installing a later kernel > from backports and rebooting the system made it unable to mount / and /swap, > until we finally booted from the old kernel and removed these entries. > > I've seen various other issues emerge from this issue, one example is here: > http://forums.debian.net/viewtopic.php?t=65395 > > It might have an easy workaround, but I believe that the entries that > correspond to the installer should be removed from /etc/fstab when > debian-installer is still running and right before it boots into the new > system. > > Also, please disregard the system information below, the machine that the > issue appeared in is: > # uname -a > Linux tourbina 3.16.0-0.bpo.4-amd64 #1 SMP Debian 3.16.7-ckt4-3~bpo70+1 > (2015-02-12) x86_64 GNU/Linux > # cat /etc/debian_version > 7.8 > # ls -l /bin/sh > lrwxrwxrwx 1 root root 4 Mar 1 2012 /bin/sh -> dash > # echo $LANG > en_US.UTF-8 > # echo $LC_CTYPE > el_GR.UTF-8 > # ps -eo pid,comm |head > PID COMMAND > 1 init > > Best regards, > > Vivia > > -- System Information: > Debian Release: 8.0 > APT prefers unstable > APT policy: (700, 'unstable'), (600, 'experimental') > Architecture: amd64 (x86_64) > Foreign Architectures: i386 > > Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) > Locale: LANG=el_GR.UTF-8, LC_CTYPE=el_GR.UTF-8 (charmap=UTF-8) > Shell: /bin/sh linked to /bin/dash > Init: systemd (via /run/systemd/system) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#779208: debian-installer: Remove /dev/sdX installer entry from fstab
Package: debian-installer Severity: important Tags: d-i Hello, I noticed that debian-installer leaves a /dev/sdX entry in /etc/fstab inside the newly installed system. This entry corresponds to the medium that Debian was installed from. In my case, I just installed Debian stable on one of our servers (not the machine I am writing from, so please disregard the System Information below). The installer left these lingering entries on fstab: #/dev/sdc1 /media/usb0 autorw,user,noauto 0 0 #/dev/sdc2 /media/usb1 autorw,user,noauto 0 0 It was a machine with several hard drives and RAID. Installing a later kernel from backports and rebooting the system made it unable to mount / and /swap, until we finally booted from the old kernel and removed these entries. I've seen various other issues emerge from this issue, one example is here: http://forums.debian.net/viewtopic.php?t=65395 It might have an easy workaround, but I believe that the entries that correspond to the installer should be removed from /etc/fstab when debian-installer is still running and right before it boots into the new system. Also, please disregard the system information below, the machine that the issue appeared in is: # uname -a Linux tourbina 3.16.0-0.bpo.4-amd64 #1 SMP Debian 3.16.7-ckt4-3~bpo70+1 (2015-02-12) x86_64 GNU/Linux # cat /etc/debian_version 7.8 # ls -l /bin/sh lrwxrwxrwx 1 root root 4 Mar 1 2012 /bin/sh -> dash # echo $LANG en_US.UTF-8 # echo $LC_CTYPE el_GR.UTF-8 # ps -eo pid,comm |head PID COMMAND 1 init Best regards, Vivia -- System Information: Debian Release: 8.0 APT prefers unstable APT policy: (700, 'unstable'), (600, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=el_GR.UTF-8, LC_CTYPE=el_GR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#689243: amsn: Please consider enabling autoresizedp by default
Hi, Thank you for the suggestion. Applied in SVN r12418. Best regards, Vivia On Sun, Sep 30, 2012 at 9:17 PM, Steven Chamberlain wrote: > Package: amsn > Version: 0.98.9-1 > Severity: wishlist > Tags: patch > > Hi, > > aMSN 0.98.9 seems to use a new retrieval method for user display > pictures, and this allows for them to be much larger than the > traditional 96x96px size. > > In some cases a user's display picture will be so large it fills the > chat window almost completely and/or most of the picture is cropped. > Right-clicking allows the size to be reduced temporarily, but after some > time (conversation times out / resumes) it can return to being oversized. > > There is a configuration option autoresizedp that seems to preserve the > original behaviour of aMSN 0.98.3 (display picture will default to > 96x96px). Please consider enabling it by default (patch attached). > > (Otherwise, this new upstream version is working very well so far, thank > you for repackaging it!) > > -- System Information: > Debian Release: 6.0.5 > APT prefers testing-proposed-updates > APT policy: (500, 'testing-proposed-updates'), (500, 'testing') > Architecture: amd64 (x86_64) > > Kernel: Linux 3.2.0-3+dsdt2-amd64 (SMP w/4 CPU cores) > Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) > Shell: /bin/sh linked to /bin/dash > > Versions of packages amsn depends on: > ii amsn-data0.98.9-1Data files for aMSN > ii libc62.13-35 Embedded GNU C Library: > Shared lib > ii libgcc1 1:4.7.1-7 GCC support library > ii libglib2.0-0 2.32.3-1GLib library of C routines > ii libgssdp-1.0-3 0.12.1-2GObject-based library for SSDP > ii libgupnp-1.0-4 0.18.3-1GObject-based library for UPnP > ii libgupnp-igd-1.0-4 0.2.1-2 library to handle UPnP IGD > port ma > ii libjpeg8 8d-1Independent JPEG Group's > JPEG runt > ii libpng12-0 1.2.49-1PNG library - runtime > ii libsoup2.4-1 2.38.1-2HTTP library implementation > in C - > ii libstdc++6 4.7.1-7 GNU Standard C++ Library v3 > ii libx11-6 2:1.5.0-1 X11 client-side library > ii libxml2 2.8.0+dfsg1-5 GNOME XML library > ii tcl-tls 1.5.0.dfsg-10 the TLS OpenSSL extension > to Tcl > ii tcl8.5 8.5.11-2Tcl (the Tool Command > Language) v8 > ii tk8.58.5.11-2Tk toolkit for Tcl and X11, > v8.5 - > ii zlib1g 1:1.2.7.dfsg-13 compression library - runtime -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
