Bug#955858: gparted: does not start, 'unable to init server', tmp.mount does not exist
Package: gparted Version: 1.5.0-1+b1 Followup-For: Bug #955858 X-Debbugs-Cc: contrapunc...@disroot.org Dear Maintainer, I have the same issue (cannot launch gparted from the XFCE applications menu), with the difference that when I start gparted from the command line, I get - ``` Invalid MIT-MAGIC-COOKIE-1 key (gpartedbin:16042): Gtk-WARNING **: 10:04:45.522: cannot open display: :0.0 ``` > What display server / desktop environment are you using? xorg v1:7.7+23 and xfce4 v4.18 -- System Information: Debian Release: trixie/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 6.7.12-amd64 (SMP w/12 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages gparted depends on: ii gparted-common 1.5.0-1 ii libatkmm-1.6-1v5 2.28.4-1+b1 ii libc62.38-13 ii libcairomm-1.0-1v5 1.14.5-1 ii libgcc-s114-20240330-1 ii libglib2.0-0t64 2.80.2-2 ii libglibmm-2.4-1t64 2.66.7-1 ii libgtk-3-0t643.24.42-1 ii libgtkmm-3.0-1t643.24.9-1 ii libpangomm-1.4-1v5 2.46.4-1+b1 ii libparted-fs-resize0t64 3.6-4 ii libparted2t643.6-4 ii libsigc++-2.0-0v52.12.1-2 ii libstdc++6 14-20240330-1 ii libuuid1 2.40.1-8.1 ii pkexec 124-2 gparted recommends no packages. Versions of packages gparted suggests: pn dmraid ii dmsetup2:1.02.196-1+b1 ii dosfstools 4.2-1.1 ii e2fsprogs 1.47.1-1 ii exfatprogs 1.2.2-1 pn gpart pn jfsutils pn kpartx pn mtools ii ntfs-3g1:2022.10.3-1+b1 pn reiser4progs pn reiserfsprogs pn udftools ii xfsprogs 6.8.0-2 ii yelp 42.2-1+b2 -- no debconf information
Bug#1072382: nextcloud-desktop: Randomly starts, keeps restarting on exit
Package: nextcloud-desktop Version: 3.11.0-1.1+b1 Severity: normal X-Debbugs-Cc: contrapunc...@disroot.org Dear Maintainer, The Nextcloud desktop application often seems to start of its own accord, and frequently restarts when I exit it (by right clicking the tray icon - Exit Nextcloud). -- System Information: Debian Release: trixie/sid APT prefers testing APT policy: (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 6.7.12-amd64 (SMP w/12 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages nextcloud-desktop depends on: ii libc6 2.38-11 ii libcloudproviders0 0.3.6-1 ii libgcc-s1 14-20240330-1 ii libglib2.0-0t642.80.2-2 ii libkf5archive5 5.115.0-2 ii libnextcloudsync0t64 3.11.0-1.1+b1 ii libqt5core5t64 5.15.10+dfsg-7.2+b1 ii libqt5dbus5t64 5.15.10+dfsg-7.2+b1 ii libqt5gui5t64 5.15.10+dfsg-7.2+b1 ii libqt5keychain10.14.3-1 ii libqt5network5t64 5.15.10+dfsg-7.2+b1 ii libqt5qml5 5.15.10+dfsg-2+b2 ii libqt5quick5 5.15.10+dfsg-2+b2 ii libqt5quickcontrols2-5 5.15.10+dfsg-2+b2 ii libqt5sql5-sqlite 5.15.10+dfsg-7.2+b1 ii libqt5svg5 5.15.10-2+b2 ii libqt5webenginecore5 5.15.15+dfsg-2+b1 ii libqt5webenginewidgets55.15.15+dfsg-2+b1 ii libqt5widgets5t64 5.15.10+dfsg-7.2+b1 ii libssl3t64 3.2.1-3 ii libstdc++6 14-20240330-1 ii nextcloud-desktop-common 3.11.0-1.1 ii nextcloud-desktop-l10n 3.11.0-1.1 ii qml-module-qt-labs-platform5.15.10+dfsg-2+b2 ii qml-module-qtgraphicaleffects 5.15.10-2+b2 ii qml-module-qtqml 5.15.10+dfsg-2+b2 ii qml-module-qtqml-models2 5.15.13+dfsg-2 ii qml-module-qtquick-controls2 5.15.10+dfsg-2+b2 ii qml-module-qtquick-layouts 5.15.10+dfsg-2+b2 ii qml-module-qtquick-window2 5.15.10+dfsg-2+b2 ii qml-module-qtquick25.15.10+dfsg-2+b2 Versions of packages nextcloud-desktop recommends: ii nextcloud-desktop-doc 3.11.0-1.1 nextcloud-desktop suggests no packages. -- no debconf information
Bug#1019417: Problem reproduced
I observed the OOM problem again in my fresh Debian linux installation. The steps to reproduce it are as follows 1. Install Debian 2. Connect to a wifi network 3. Wait for wpa_supplicant to use all the memory and observe the OOM killer message
Bug#1007106: reportbug: please make the meaning of the a11y tag clearer
On 3/14/2022 12:53 AM, Samuel Thibault wrote: Hello, Simon McVittie wrote: For instance, the bug that prompted me to open this one is a deadlock (or something) in interacting with Pipewire's PulseAudio-compatible server, which makes the game Minetest (among others) take a long time to start and have no sound. That certainly makes it hard to access normal functionality of minetest, but it doesn't seem like a bug that needs particular attention from accessibility experts... Oops, indeed! Can anyone suggest a wording that makes the intention of the tag clearer, without "othering" the people who particularly need bugs with this tag to be fixed? I've cc'd debian-accessibility in the hope that someone on that list has a better idea. Thanks for the notice! 1 a11y This bug is relevant to the accessibility of the package. Perhaps simply adding 1 a11y This bug is relevant to the accessibility of the package for disabled users. ? Or rephrasing to make it shorter: 1 a11y This bug affects disabled users. Or an alternative: 1 a11y This tag refers to peoples with disabilities Would be nice if native English speakers could help properly phrasing this! :) -- John Doe
Bug#1002976: installation-reports: Installer Does Not Provide Screen Reader in Accessible Installation
On 1/17/2022 1:13 AM, D.J.J. Ring, Jr. wrote: Here's the message, i didn't include the bug address. I'm new We've all been there!!! :) Please understand that it is as frustrated for you as it is for us. P.S. Apologies for the crossposting, from now on I will only send to this bug report. -- John Doe
Bug#996097: fcitx: Devanagari iTrans input method missing after update
Package: fcitx Version: 1:4.2.9.8-3 Severity: normal Tags: l10n X-Debbugs-Cc: contrapunc...@disroot.org Dear Maintainer, After an update, the Devanagari iTrans input method is no longer available in fcitx. Additionally, the fcitx system tray icon no longer appears in the XFCE panel. -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-8-amd64 (SMP w/4 CPU threads) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages fcitx depends on: ii fcitx-bin 1:4.2.9.8-3 ii fcitx-data 1:4.2.9.8-3 ii fcitx-modules 1:4.2.9.8-3 Versions of packages fcitx recommends: ii fcitx-config-gtk 0.4.10-3 ii fcitx-frontend-all 1:4.2.9.8-3 ii fcitx-frontend-fbterm 0.2.0-3+b1 ii fcitx-ui-classic 1:4.2.9.8-3 ii fcitx-ui-light 0.1.3-3+b1 ii im-config 0.48-1 ii kde-config-fcitx 0.5.6-2 Versions of packages fcitx suggests: ii fcitx-m17n 0.2.4-2 ii fcitx-tools 1:4.2.9.8-3
Bug#985666: alsa-utils: no sound after installation
On 3/21/2021 7:50 PM, Samuel Thibault wrote: Nick Gawronski, le dim. 21 mars 2021 13:45:37 -0500, a ecrit: What else can I try to see if the sound is working are samples provided to test with? You could use aplay from alsa-utils on a .wav file. In other words, are you able to play any sound on the installed system (the one you installed without a DE (Mate/Gnome...)). -- John Doe
Bug#983835: base-installer: hostname= is ignored if reverse-dns exists
On 3/2/2021 6:15 PM, Phil Dibowitz wrote: On 3/2/21 1:58 AM, Holger Wansing wrote: Am 2. März 2021 09:52:06 MEZ schrieb Cyril Brulebois : The preseed doc[2] suggests the former is behind the (bare) hostname alias. Try setting the latter? Yes, the installation-guide under https://www.debian.org/releases/bullseye/amd64/apbs04.en.html even explicitly states this, indeed: # If you want to force a hostname, regardless of what either the DHCP # server returns or what the reverse DNS entry for the IP is, uncomment # and adjust the following line. #d-i netcfg/hostname string somehost Thanks for pointing that out! Don't know how I missed that. However, that requires a per-host preseed, where as with kernel command line I can have the same preseed for all my hosts (or at least all hosts in a certain category) and simply just pass in a hostname in the tftpseed (which has to be host specific anyway and for me is already generated by my provisioning system). So perhaps it would be useful to have a like netcfg/hostname_priority flag where one can choose a priority order? +1 -- John Doe
Bug#981585: sxiv: crashes if launched from Emacs
Package: sxiv Version: 26-1~bpo10+1 Severity: important Dear Maintainer, I launched sxiv from Emacs using `async-shell-command` and this command line - `find ... -type f ... -print0 | xargs -0 sxiv -ifo` It opens, I'm able to browse images, but a few seconds later it crashes and I see the following output - ``` XIO: fatal IO error 88 (Socket operation on non-socket) on X server ":0" after 8379 requests (8378 known processed) with 2 events remaining. XIO: fatal IO error 88 (Socket operation on non-socket) on X server ":0" after 8379 requests (8378 known processed) with 2 events remaining. ``` I tried running it from a terminal, but could not reproduce it. M-x emacs-version - GNU Emacs 26.1 (build 2, x86_64-pc-linux-gnu, GTK+ Version 3.24.5) of 2019-09-23, modified by Debian I tested with sxiv v25-1 from Stable and with a backported v26-1 from Testing. -- System Information: Debian Release: 10.7 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-13-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages sxiv depends on: ii libc6 2.28-10 ii libexif12 0.6.21-5.1+deb10u5 ii libfontconfig1 2.13.1-2 ii libgif7 5.1.4-3 ii libimlib2 1.5.1-1 ii libx11-62:1.6.7-1+deb10u1 ii libxft2 2.3.2-2 sxiv recommends no packages. Versions of packages sxiv suggests: ii imagemagick 8:6.9.10.23+dfsg-2.1+deb10u1 ii imagemagick-6.q16 [imagemagick] 8:6.9.10.23+dfsg-2.1+deb10u1 ii libjpeg-turbo-progs [libjpeg-progs] 1:1.5.2-2+deb10u1 -- no debconf information
Bug#975273: RFP: nethack-vulture -- Isometric tiles interface for NetHack
Package: wnpp Severity: wishlist * Package name: nethack-vulture Version : ? Upstream Author : ? * URL : https://github.com/DanielT/Vulture * License : Nethack General Public License Programming Lang: C++ Description : Isometric tiles interface for NetHack This is one of the best-looking GUIs for NetHack. I seem to remember it was in Debian before, could not find any information about why it was removed, hope to see it available again.
Bug#974715: gnome-maps: Search returns no results
Package: gnome-maps Version: 3.30.3.1-0+deb10u1 Severity: normal Dear Maintainer, Steps - 1. Open gnome-maps 2. Type something in the search bar (I've tried POI names that I know exist, as well as common terms like "hospital") 3. Press Enter A popup appears with a spinner, and always ends with "No results found." -- System Information: Debian Release: 10.6 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-12-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages gnome-maps depends on: ii dconf-gsettings-backend [gsettings-backend] 0.30.1-2 ii geoclue-2.0 2.5.2-1 ii gir1.2-champlain-0.120.12.16-3 ii gir1.2-clutter-1.0 1.26.2+dfsg-10 ii gir1.2-cogl-1.0 1.22.2-6 ii gir1.2-gdkpixbuf-2.0 2.38.1+dfsg-1 ii gir1.2-geoclue-2.0 2.5.2-1 ii gir1.2-geocodeglib-1.0 3.26.1-1 ii gir1.2-gfbgraph-0.2 0.2.3-3 ii gir1.2-glib-2.0 1.58.3-2 ii gir1.2-goa-1.0 3.30.1-2 ii gir1.2-gtk-3.0 3.24.5-1 ii gir1.2-gtkchamplain-0.12 0.12.16-3 ii gir1.2-gtkclutter-1.01.8.4-4 ii gir1.2-gweather-3.0 3.28.2-2 ii gir1.2-rest-0.7 0.8.1-1 ii gir1.2-secret-1 0.18.7-1 ii gir1.2-soup-2.4 2.64.2-2 ii gir1.2-webkit2-4.0 2.28.4-1~deb10u1 ii gjs 1.54.3-1 ii libc62.28-10 ii libchamplain-0.12-0 0.12.16-3 ii libfolks25 0.11.4-1+b2 ii libgee-0.8-2 0.20.1-2 ii libgeocode-glib0 3.26.1-1 ii libglib2.0-0 2.58.3-2+deb10u2 ii libglib2.0-bin 2.58.3-2+deb10u2 ii librest-0.7-00.8.1-1 ii libxml2 2.9.4+dfsg1-7+b3 gnome-maps recommends no packages. gnome-maps suggests no packages. -- no debconf information
Bug#974203: qtractor: Crashes on launch
Package: qtractor Version: 0.9.5-1 Severity: important Dear Maintainer, Qtractor crashes randomly when I try to start it, whether via applications menu or terminal. Usually, the GUI is not even visible when the crash occurs. The command I use is `LANG=C qtractor`, and yet the errors I got used my system's German locale - ``` $ LANG=C qtractor Speicherzugriffsfehler $ LANG=C qtractor Abgebrochen ``` I experienced this on the Debian Stable version, and tried to build a version from Testing sources. I'm not sure if that succeeded (the resulting binary reported the same version numbers as Stable) - however, if it did, then this problem seems to exist in the Testing version, too. -- System Information: Debian Release: 10.6 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-12-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages qtractor depends on: ii jackd 5+nmu1 ii libasound21.1.8-1 ii libc6 2.28-10 ii libgcc1 1:8.3.0-6 ii libglib2.0-0 2.58.3-2+deb10u2 ii libgtk2.0-0 2.24.32-3 ii libjack-jackd2-0 [libjack-0.125] 1.9.12~dfsg-2 ii liblilv-0-0 0.24.2~dfsg0-2 ii liblo70.29-1+b11 ii libmad0 0.15.1b-10 ii libogg0 1.3.2-1+b1 ii libqt5core5a 5.11.3+dfsg1-1+deb10u4 ii libqt5gui55.11.3+dfsg1-1+deb10u4 ii libqt5widgets55.11.3+dfsg1-1+deb10u4 ii libqt5x11extras5 5.11.3-2 ii libqt5xml55.11.3+dfsg1-1+deb10u4 ii librubberband21.8.1-7 ii libsamplerate00.1.9-2 ii libsndfile1 1.0.28-6 ii libstdc++68.3.0-6 ii libsuil-0-0 0.10.0~dfsg0-1 ii libvorbis0a 1.3.6-2 ii libvorbisenc2 1.3.6-2 ii libvorbisfile31.3.6-2 ii zlib1g1:1.2.11.dfsg-1 qtractor recommends no packages. qtractor suggests no packages. -- no debconf information
Bug#974019: libkf5screen7: Desktop no more handled
Exact same problem here. I was able to recover normal behavior by only downgrading libkdecoration2-5v5:amd64 to version 4:5.17.5-2, so this is definitively a libkdecoration2 issue. For inexperienced user (like myself) struggling to solve this issue, you can download the file here http://ftp.debian.org/debian/pool/main/k/kdecoration/libkdecorations2-5v5_5.17.5-2_amd64.deb and install it with sudo apt install ./libkdecorations2-5v5_5.17.5-2_amd64.deb Best Victor
Bug#969598: reportbug: does not include a .desktop file
Package: reportbug Version: 7.7.0 Severity: wishlist Dear Maintainer, reportbug does not seem to include a .desktop file. `dpkg -L reportbug` confirms this. As a result, users cannot run it from the applications menu. Please include one in the package. -- Package-specific info: ** Environment settings: EDITOR="emacsclient" INTERFACE="text" ** /home/anon/.reportbugrc: reportbug_version "7.7.0" mode standard ui text realname "John Doe" email "contrapunc...@disroot.org" smtphost "disroot.org" smtpuser "contrapunctus" smtptls -- System Information: Debian Release: bullseye/sid APT prefers testing-debug APT policy: (500, 'testing-debug'), (500, 'testing'), (300, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 5.7.0-2-amd64 (SMP w/4 CPU threads) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_IN, LC_CTYPE=en_IN (charmap=UTF-8), LANGUAGE=en_IN:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages reportbug depends on: ii apt2.1.10 ii python33.8.2-3 ii python3-reportbug 7.7.0 ii sensible-utils 0.0.12+nmu1 reportbug recommends no packages. Versions of packages reportbug suggests: pn claws-mail pn debconf-utils pn debsums pn dlocate ii emacs-bin-common 1:26.3+1-2 ii exim4-daemon-light [mail-transport-agent] 4.94-7 ii file 1:5.38-5 ii gnupg 2.2.20-1 pn python3-urwid pn reportbug-gtk ii xdg-utils 1.1.3-2 Versions of packages python3-reportbug depends on: ii apt2.1.10 ii file 1:5.38-5 ii python33.8.2-3 ii python3-apt2.1.3 ii python3-debian 0.1.37 ii python3-debianbts 3.0.2 ii python3-requests 2.23.0+dfsg-2 ii sensible-utils 0.0.12+nmu1 python3-reportbug suggests no packages. -- no debconf information
Bug#969087: lightdm-settings: does not open
Package: lightdm-settings Version: 1.4.2+dfsg.1-1 Severity: important Dear Maintainer, I've tried to open lightdm-settings from the applications menu as well as from a terminal (`$ gksudo lightdm-settings`). I'm prompted for a password, but the application never shows up afterwards. -- System Information: Debian Release: bullseye/sid APT prefers testing-debug APT policy: (500, 'testing-debug'), (500, 'testing'), (400, 'unstable'), (100, 'experimental') Architecture: i386 (i686) Kernel: Linux 5.7.0-2-686 (SMP w/4 CPU threads) Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages lightdm-settings depends on: ii python3 3.8.2-3 ii python3-setproctitle 1.1.10-2 ii python3-xapp 2.0.1-2 lightdm-settings recommends no packages. lightdm-settings suggests no packages. -- no debconf information
Bug#969077: lightdm: does not unlock keyring on login
Package: lightdm Version: 1.26.0-7 Severity: normal Dear Maintainer, My login and keyring passwords are the same. I expected that the keyring will be automatically unlocked on login, but this does not happen with lightdm. I've tried sddm, and it unlocked the keyring automatically on login. -- System Information: Debian Release: bullseye/sid APT prefers testing-debug APT policy: (500, 'testing-debug'), (500, 'testing'), (400, 'unstable'), (100, 'experimental') Architecture: i386 (i686) Kernel: Linux 5.7.0-2-686 (SMP w/4 CPU threads) Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages lightdm depends on: ii adduser3.118 ii dbus 1.12.20-1 ii debconf [debconf-2.0] 1.5.74 ii libaudit1 1:2.8.5-3+b1 ii libc6 2.31-3 ii libgcrypt201.8.6-2 ii libglib2.0-0 2.64.4-1 ii libpam-systemd [logind]246-2 ii libpam0g 1.3.1-5 ii libxcb11.14-2 ii libxdmcp6 1:1.1.2-3 ii lightdm-gtk-greeter [lightdm-greeter] 2.0.8-1 ii lsb-base 11.1.0 Versions of packages lightdm recommends: ii xserver-xorg 1:7.7+20 Versions of packages lightdm suggests: ii accountsservice 0.6.55-2 ii upower 0.99.11-2 ii xserver-xephyr 2:1.20.8-2 -- debconf information: * shared/default-x-display-manager: lightdm lightdm/daemon_name: /usr/sbin/lightdm
Bug#950830: #950830 installation-reports: Preseeding language+country+locale not working in Buster
On 8/2/2020 3:10 PM, Holger Wansing wrote: Hi, one wrote (7 Feb 2020 08:39:02): d-i debian-installer/language string en d-i debian-installer/countrystring CH d-i debian-installer/locale string en_US.UTF-8 From my testing this should be basically the correct parameters, however when looking at https://d-i.debian.org/doc/installation-guide/en.amd64/apbs04.html there are just spaces between the fields, no tabs. Maybe that's the problem? Do you have a chance to give it a try? (Maybe also try a bullseye image? However, the format of the preseeding parameters did not change between Buster and Bullseye.) For me the below preseed snippet works on Buster and Bullseye: # The values can also be preseeded individually for greater flexibility. d-i debian-installer/language string C d-i debian-installer/country string EN d-i debian-installer/locale string C # Optionally specify additional locales to be generated. d-i localechooser/supported-locales multiselect en_US.UTF-8, ... -- John Doe
Bug#966478: git-email: Unhelpful error message
Package: git-email Version: 1:2.28.0+next.20200726-1 Severity: wishlist Dear Maintainer, I had set smtpserver and smtpuser, but not smtpencryption; git send-email failed to send email and returned this unhelpful error message. ``` $ git send-email --to="some...@somewhere.org" --suppress-cc=all HEAD^ /tmp/path-to-my-git.patch Password for 'smtp://m...@disroot.org:25': Command unknown: 'AUTH' at /usr/lib/git-core/git-send-email line 1565. ``` After setting smtpencryption, the command worked. I'd like git send-email to inform the user why this may have happened, and what they can do. -- System Information: Debian Release: bullseye/sid APT prefers testing-debug APT policy: (500, 'testing-debug'), (500, 'testing'), (400, 'unstable'), (100, 'experimental') Architecture: i386 (i686) Kernel: Linux 5.6.0-2-686 (SMP w/4 CPU threads) Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages git-email depends on: ii git 1:2.28.0+next.20200726-1 Versions of packages git-email recommends: ii libauthen-sasl-perl2.1600-1 ii libemail-valid-perl1.202-1 ii libio-socket-ssl-perl 2.067-1 ii libmailtools-perl 2.21-1 ii libnet-smtp-ssl-perl 1.04-1 ii perl 5.30.3-4 Versions of packages git-email suggests: pn git-doc -- no debconf information
Bug#961125: vga= deprecated with grub2
Package: debian-installer Version: debian-bullseye-DI-alpha2-amd64-netinst.iso qemu-system-x86_64 -cdrom debian-bullseye-DI-alpha2-amd64-netinst.iso -nographic -vga none -m 1024 At the Debian install prompt pressing the escape key get me to the boot prompt. boot: install console=ttyS0,115200n8 DEBIAN_FRONTEND=text gfxpayload=text Undefined video mode number: 314 Press to see video modes available, to continue, or wait 30 sec If I use 'vga=none' the above is suppressed but Debian will not start properly after installation by saying that 'vga=none' is deprecated and that 'set gfxpayload=text' should be used instead. How can I specify 'set gfxpayload=text' to the boot prompt above? In other words, how can i emulate 'vga=none' when this argument is deprecated when installing Debian. -- John Doe
Bug#960390: x86_64: No serial port output
On 5/13/2020 12:28 PM, Alper Nebi Yasak wrote: On 13/05/2020 03:43, Punit Agrawal wrote: Incidentally, this does not work if '-m 1024' is missing. Kernel boot fails to find 'init'. I suspect that the Qemu default RAM configuration is not sufficient to unpack the initrd. Thanks, that's it. I haven't noticed it the first time around because I normally run virtual machines with virt-manager... The default RAM is 128MiB and the messages also say "Initramfs unpacking failed: write error". Based on this, updated version of Alper's instructions now launch the DI without the need to extract the kernel / initrd. $ qemu-system-x86_64 -cdrom *.iso -nographic -vga none -m 1024 Edit the 'Install' option (by removing 'quiet' and 'vga=788') into: /install.amd/vmlinuz initrd=/install.amd/initrd.gz --- console=ttyS0 (BTW, we need console=ttyS0 here because /proc/consoles only has tty0. The exact opposite happens on arm64 VMs: there /proc/consoles only has ttyAMA0 so debian-installer only launches on the serial console and not on the graphics window.) I also'd like to point out that instead of modifying grub at the install prompt, pressing the escape key and typing at the boot prompt the below works for me (pressing the 'escape' key instead of the 'tab' key): boot: install console=ttyS0,115200n8 DEBIAN_FRONTEND=text vga=none From Buster onwords, /etc/default/grub does not need to be modified at all after installation. What transpired in this thread is that modifying grub at installation time is not reflected at run time. -- John Doe
Bug#960390: x86_64: No serial port output
On 5/12/2020 12:02 PM, Punit Agrawal wrote:
john doe writes:
On 5/12/2020 11:36 AM, Punit Agrawal wrote:
john doe writes:
[...]
This does not start the Debian installer. The issue reported is that the
grub shipping with DI does not output to serial console and hence can't
be used with "-nographic". It's maybe that the same issue is faced when
installing on hardware with no display but I have not confirmed this.
The aim is to be able to install debian in a VM using the iso images
That is exactly what I'm doing! :)
Thanks for clarifying. Sorry I misunderstood your reply.
-nographic -cdrom *.iso -kernel kernel-path -append
"console=ttyS0,115200n8 ..."
Okay, you want something working out of the box but note that what you
want is already possible if you use the proper arguments.
The above parameters do not launch the installer from the iso here. I am
not quite sure what the right arguments are. I wonder if
"root=" to the kernel will do the trick. Will give that a
try.
I did get what you were complaning about, I was simply providing a
workaround to get you going.
I worked around this by using the graphical install and enabling serial
output in the installed image but I think this can be made to work
out-of-box and we shouldn't need a workaround. Fingers crossed.
The below command get me directly to the language selection screen which
I belaeve is what you want?:
qemu-system-x86_64 -drive file=debian.img,format=raw -m 1024 -boot d
-nographic -cdrom debian-bullseye-DI-alpha2-amd64-netinst.iso -kernel
vmlinuz -append "console=ttyS0,115200n8 DEBIAN_FRONTEND=text" -initrd
initrd.gz
I extract all files ('vmlinuxz','initrd.gz') from the iso but they can
also be found online.
--
John Doe
Bug#960390: x86_64: No serial port output
On 5/12/2020 11:36 AM, Punit Agrawal wrote: john doe writes: On 5/12/2020 11:01 AM, Colin Watson wrote: [...] Unless I'm missing something, it does work for me with something like: -nographic -cdrom *.iso -kernel kernel-path -append "console=ttyS0,115200n8 ..." This does not start the Debian installer. The issue reported is that the grub shipping with DI does not output to serial console and hence can't be used with "-nographic". It's maybe that the same issue is faced when installing on hardware with no display but I have not confirmed this. The aim is to be able to install debian in a VM using the iso images That is exactly what I'm doing! :) (e.g. [0]) without requiring graphical UI. This is already possible when using arm64 and armhf DI images but seems to be missing some configuration in the installer for x86_64. Okay, you want something working out of the box but note that what you want is already possible if you use the proper arguments. Hope this clarifies the report. I did get what you were complaning about, I was simply providing a workaround to get you going. [0] https://cdimage.debian.org/cdimage/bullseye_di_alpha2/amd64/iso-cd/debian-bullseye-DI-alpha2-amd64-netinst.iso Again it is working if you specify the kernel boot parameter that Debian requires. -- John Doe
Bug#960390: x86_64: No serial port output
On 5/12/2020 11:01 AM, Colin Watson wrote: Control: reassign -1 debian-installer On Tue, May 12, 2020 at 05:32:51PM +0900, Punit Agrawal wrote: Package: grub2 Grub does not output to serial port when running in a VM launched using Qemu when run as part of the Debian Installer. This prevents installation of Debian in a VM when running without a GUI. In this specific instance, I was trying to install Debian in a VM over ssh. To reproduce the problem, run $ qemu-system-x86_64 -cdrom debian-10.3.0-amd64-netinst.iso -nographic The BIOS / Firmware outputs to the serial port but no further progress is seen on the serial console. Dropping the `-nographic` shows that Debian Installer is launched in a graphical window waiting for input. Once installed without `-nographic`, the following changes to /etc/default/grub and running `sudo update-grub` enabled serial output. GRUB_TERMINAL=console GRUB_SERIAL_COMMAND="serial --speed=11520 --unit=0 --word=8 --parity=no --stop=1 The behaviour was seen on both Buster and Bullseye based Debian Installer images on x86_64. It was also consistent for both legacy and UEFI firmware. The installer supplies its own GRUB configuration for the installer images themselves; and its "grub-installer" component then has code to at least attempt to configure the installed system's GRUB to use serial output if the installer itself was using serial output. So I think either way this is something that would need to be fixed in the installer. Reassigning there. Unless I'm missing something, it does work for me with something like: -nographic -cdrom *.iso -kernel kernel-path -append "console=ttyS0,115200n8 ..." '-serial' might also be needed. -- John Doe
Bug#954200: DI encrypted LVM, discard option crypttab file
Package: debian-installer Version: debian-10.3.0-amd64-netinst.iso After installing debian-10.3.0-amd64-netinst.iso with encrypted LVM, the crypttab file is populated with the discard' option in the fourth field. According to (1), the discard option has security implication: "discard Allow discard requests to be passed through the encrypted block device. This improves performance on SSD storage but has security implications." I would suggest that the debian-installer populates the first two mandatory fields of '/etc/crypttab'. 1) https://www.freedesktop.org/software/systemd/man/crypttab.html -- John Doe
Bug#944114: Missing directory spec in Remap secdeb rule
Package: apt-cacher-ng
Version: 3.2-2
Upon installation of AC-NG, the remap rule ('secdeb') for debian
security is missing the directory spec ('/debian-security'):
Rong remap rule without directory spec:
Remap-secdeb: security.debian.org ; security.debian.org
deb.debian.org/debian-security
Working remap rule with directory spec:
Remap-secdeb: security.debian.org /debian-security ; security.debian.org
deb.debian.org/debian-security
If the directory spec is not included in the remap rule the following
error comes up:
"Err:1 http://localhost:3142/debian-security buster/updates InRelease
503 DNS error for hostname debian-security: No address associated
with hostname. If debian-security refers to a configured cache
repository, please check the corresponding configuration file. [IP: ::1
3142]
Reading package lists... Done
W: Failed to fetch
http://localhost:3142/debian-security/dists/buster/updates/InRelease
503 DNS error for hostname debian-security: No address associated with
hostname. If debian-security refers to a configured cache repository,
please check the corresponding configuration file. [IP: ::1 3142]
W: Some index files failed to download. They have been ignored, or old
ones used instead."
For testing purposes, the client is on the same host as apt-cacher-ng.
The repository spec '/debian-security' was chosen because it is per
default appended when installing Debian Buster (10) using a preseed file.
As an aside:
In the remap rule above I would suggest adding
'deb.debian.org/debian-security' in the MurgeURL component, so my
suggested remap rule would look like:
Remap-secdeb: deb.debian.org/debian-security security.debian.org
/debian-security ; security.debian.org deb.debian.org/debian-security
--
John Doe
Bug#942028: Bootloader file located in same directory as ldlinux.c32
Package: debian-installer-10-netboot-amd64 Version: 20190702+deb10u1 Following the recommendation of (1) and (2) the pxelinux.0 (bootloader) file should be in the same directory as the ldlinux.c32 library: "On the TFTP server, create the directory "/tftpboot", and copy "pxelinux.0" (from the Syslinux distribution) and any kernel or initrd images that you want to boot. [5.00+] Also copy "ldlinux.c32" from the Syslinux distribution to the "/tftpboot" directory on the TFTP server." Sadly, Debian does not follows those guidelines and creates an issue if you want to install Debian 10 (Buster) using PXE boot with the local tftp server of Qemu for Windows. The issue only manifest itself on Windows, steps to reproduce: - Copy the text directory from this very package into the root directory of Qemu's local tftp server - For sake of completeness, recreate the symlinks Windows way: del /q ldlinux.c32 del /q pxelinux.0 rmdir /q /S pxelinux.cfg mklink ldlinux.c32 debian-installer\amd64\boot-screens/ldlinux.c32 mklink pxelinux.0 debian-installer\amd64\pxelinux.0 mklink /D pxelinux.cfg debian-installer\amd64\pxelinux.cfg - Start Qemu with the following command: qemu-system-x86_64 -boot n -net user,tftp=,bootfile=pxelinux.0 - Error message "Failed to load ldlinux.c32 Boot failed: press a key to retry, or wait for reset..." - Workaround: Given that ldlinux.c32 is in 'debian-installer/amd64/boot-screens' and not in the root directory of the tftp server the only workaround is to copy ldlinux.c32 in the root directory of the tftp server by doing: del /q ldlinux.c32 echo F|xcopy /S /Q /Y /F debian-installer\amd64\boot-screens\ldlinux.c32 If ldlinux.c32 is in the same directory as pxelinux.0 it works. See also (3) and (4) for more context. Note that all commands are to be executed in the tftp root directory. 1) https://wiki.syslinux.org/wiki/index.php?title=PXELINUX 2) https://www.syslinux.org/archives/2019-September/026536.html 3) https://lists.debian.org/debian-boot/2019/09/msg00152.html 4) https://lists.debian.org/debian-user/2019/09/msg00817.html -- John Doe
Bug#924037: Please add anacron back to task-desktop and task-laptop
On 3/8/2019 7:17 PM, Holger Wansing wrote: > Hi, > > Ian Jackson wrote: >> Package: task-desktop >> Version: 3.49 >> >> The rationale for this change is IMO not correct. >> >> Michael Biebl wrote: >> | all important cron jobs have a corresponding .timer unit >> >> This is not a sufficient condition. Firstly, it is necessary for all >> cron jobs, not just ones considered `important', to have a >> corresponding timer unit, for this change to be correct. >> >> Secondly, this change simply breaks systems without systemd. If >> (which I deny) it is a good idea to change this for systemd systems, >> measures should be taken to arrange that non-systemd systems still get >> anacron. For example, a dependency on systemd-sysv | anacron >> >> (Thirdly, and tangentially, for reasons explored further in the >> debian-devel thread, systemd timer units are not a suitable >> replacement for many applications.) >> >> Also I think that when changes are being made which might break >> non-systemd systems, the Debian Ecosystem Init Diversity team >> debian-init-divers...@chiark.greenend.org.uk >> should be consulted so that the appropriate fixes can be developed. > > I tend to follow this proposal (also looking at the corresponding > discussion on d-devel). > >> Finally, this change is rather late wrt the freeze. > > Since this is just a revert of a recent change, this can be considered > causing no harm. > > > Any objections? > kibi? > I'm probably missing something here, this change have never had the green light to go ahead in the first place. -- John Doe
Bug#884364: ibus: Need to press S-SPC twice to change IM
Package: ibus Version: 1.5.14-3 Severity: important Dear Maintainer, I need to press S-SPC (Super-Space) twice for IBus to switch input methods. This makes it inconvenient to frequently switch between input methods. -- Package-specific info: default-display-manager: /usr/sbin/lightdm ibus is /usr/bin/ibus ibus-setup is /usr/bin/ibus-setup im-config -l => ibus xim im-config -m => default missing ibus ibus XMODIFIERS=@im=ibus GTK_IM_MODULE=ibus QT4_IM_MODULE=xim QT_IM_MODULE=ibus XDG_DATA_DIRS=/usr/share/gnome:/usr/local/share/:/usr/share/ XDG_MENU_PREFIX= PATH=~/bin:/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games ls -l /usr/lib/ibus/ total 432 -rwxr-xr-x 1 root root 13724 May 20 2017 ibus-dconf -rwxr-xr-x 1 root root 34204 Dec 10 2016 ibus-engine-m17n -rwxr-xr-x 1 root root 9628 May 20 2017 ibus-engine-simple -rwxr-xr-x 1 root root 1925 Jan 14 2017 ibus-engine-table -rwxr-xr-x 1 root root 26012 Dec 10 2016 ibus-setup-m17n -rwxr-xr-x 1 root root 1068 Jan 14 2017 ibus-setup-table -rwxr-xr-x 1 root root 234932 May 20 2017 ibus-ui-gtk3 -rwxr-xr-x 1 root root 99824 May 20 2017 ibus-x11 -- System Information: Debian Release: 9.3 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 3.16.0-4-686-pae (SMP w/4 CPU cores) Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages ibus depends on: ii adwaita-icon-theme 3.22.0-1+deb9u1 ii dconf-cli0.26.0-2+b1 ii dconf-gsettings-backend [gsettings-backend] 0.26.0-2+b1 ii gir1.2-gtk-3.0 3.22.11-1 ii gir1.2-ibus-1.0 1.5.14-3 ii libatk1.0-0 2.22.0-1 ii libc62.24-11+deb9u1 ii libcairo21.14.8-1 ii libdconf10.26.0-2+b1 ii libgdk-pixbuf2.0-0 2.36.5-2+deb9u1 ii libglib2.0-0 2.50.3-2 ii libgtk-3-0 3.22.11-1 ii libibus-1.0-51.5.14-3 ii libnotify4 0.7.7-2 ii libpango-1.0-0 1.40.5-1 ii libpangocairo-1.0-0 1.40.5-1 ii librsvg2-common 2.40.16-1+b1 ii libx11-6 2:1.6.4-3 ii libxi6 2:1.7.9-1 ii python3 3.5.3-1 ii python3-gi 3.22.0-2 Versions of packages ibus recommends: ii ibus-gtk1.5.14-3 ii ibus-gtk3 1.5.14-3 ii im-config 0.30-1 ii libqt5gui5 5.7.1+dfsg-3+b1 Versions of packages ibus suggests: pn ibus-clutter pn ibus-doc pn ibus-qt4 ii libqt5gui55.7.1+dfsg-3+b1 -- no debconf information
Bug#868495: passwordsafe: Program difficult to close
Package: passwordsafe Version: 1.00+dfsg-1 Severity: normal Dear Maintainer, (I'm using Cinnamon, for what it's worth.) Starting Password Safe, and pressing Escape or the Close Window keybind (e.g. Alt-F4) at the initial Safe Combination Entry dialog exits as expected. After entering the passphrase, pressing the Close Window key combination also exits as expected. However, if the database is locked after it was unlocked (e.g. after the timeout, or by minimizing with "Lock password database on minimize" enabled), it becomes difficult to close the application. Pressing Escape or Alt-F4 minimizes it. Ctrl-q and Ctrl-w do not work. The only way to quit is by minimizing the program by pressing Escape or Alt-F4, then right-clicking the program in the taskbar and selecting Close, which is cumbersome, obscure, and unexpected. -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (990, 'testing'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 4.11.0-1-686-pae (SMP w/4 CPU cores) Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages passwordsafe depends on: ii libc62.24-12 ii libgcc1 1:7.1.0-9 ii libstdc++6 7.1.0-9 ii libuuid1 2.29.2-1 ii libwxbase3.0-0v5 3.0.2+dfsg-4 ii libwxgtk3.0-0v5 3.0.2+dfsg-4 ii libx11-6 2:1.6.4-3 ii libxerces-c3.1 3.1.4+debian-2 ii libxtst6 2:1.2.3-1 ii libykpers-1-11.17.3-1 ii passwordsafe-common 1.00+dfsg-1 Versions of packages passwordsafe recommends: ii xvkbd 3.3-1+b1 passwordsafe suggests no packages. -- debconf-show failed
Bug#754129: RFP: lutris -- An open gaming platform for Linux
Package: wnpp Severity: wishlist * Package name: Lutris * Home page: https://lutris.net/ * License: GPLv3 * Description: (from the website) Lutris is an open gaming platform for Linux. It helps you install and manage your games in a unified interface. Our goal is to support every game which runs on Linux,from native to Windows games (via Wine) to emulators and browser games.
Bug#244582: Version 2.5 is out
Version 2.5 is out!!! http://sourceforge.net/projects/ufoai/files/UFO_AI%202.x/2.5/ Now is totally a free (as in freedom) game. Please, put it in official repositories. Thanks!
Bug#244582: ITP: ufoai -- UFO: Alien Invasion - build your team and stop the aliens
I hope to see finally this beautiful game in Debian repositories. 2014-06-13 0:05 GMT+02:00 Markus Koschany a...@gambaru.de: It's almost done now. License status is finally green. They just have to release 2.5 which I hope happens still in time for the freeze...
Bug#707958: qbittorrent crashes after starting the download (doesn't happen usually)
Package: qbittorrent Version: 2.9.8-1 Severity: important Here's the output: Couldn't set environment variable... Peer ID: -qB2980- HTTP user agent is qBittorrent v2.9.8 * Catching SIGSEGV, please report a bug at http://bug.qbittorrent.org and provide the following backtrace: qBittorrent version: v2.9.8 stack trace: /lib/x86_64-linux-gnu/libc.so.6 : ()+0x324f0 [0x7f96fd3124f0] qbittorrent : TorrentFilesModel::updateFilesPriorities(std::vectorint, std::allocatorint const)+0x58 [0x5238b8] qbittorrent : PropertiesWidget::loadDynamicData()+0xa44 [0x51aed4] qbittorrent() [0x5da2fd] /usr/lib/x86_64-linux-gnu/libQtCore.so.4 : QMetaObject::activate(QObject*, QMetaObject const*, int, void**)+0x2bf [0x7f96fdf9b54f] /usr/lib/x86_64-linux-gnu/libQtCore.so.4 : QObject::event(QEvent*)+0x9c [0x7f96fdf9a85c] /usr/lib/x86_64-linux-gnu/libQtGui.so.4 : QApplicationPrivate::notify_helper(QObject*, QEvent*)+0xac [0x7f96fe7fa70c] /usr/lib/x86_64-linux-gnu/libQtGui.so.4 : QApplication::notify(QObject*, QEvent*)+0x13a [0x7f96fe7feb8a] /usr/lib/x86_64-linux-gnu/libQtCore.so.4 : QCoreApplication::notifyInternal(QObject*, QEvent*)+0x8e [0x7f96fdf85b5e] /usr/lib/x86_64-linux-gnu/libQtCore.so.4 : ()+0x1ada52 [0x7f96fdfb6a52] /usr/lib/x86_64-linux-gnu/libQtCore.so.4 : ()+0x1aac04 [0x7f96fdfb3c04] /usr/lib/x86_64-linux-gnu/libQtCore.so.4 : ()+0x1aac21 [0x7f96fdfb3c21] /lib/x86_64-linux-gnu/libglib-2.0.so.0 : g_main_context_dispatch()+0x135 [0x7f96fc142355] /lib/x86_64-linux-gnu/libglib-2.0.so.0 : ()+0x4a688 [0x7f96fc142688] /lib/x86_64-linux-gnu/libglib-2.0.so.0 : g_main_context_iteration()+0x34 [0x7f96fc142744] /usr/lib/x86_64-linux-gnu/libQtCore.so.4 : QEventDispatcherGlib::processEvents(QFlagsQEventLoop::ProcessEventsFlag)+0x66 [0x7f96fdfb4276] /usr/lib/x86_64-linux-gnu/libQtGui.so.4 : ()+0x27e83e [0x7f96fe89b83e] /usr/lib/x86_64-linux-gnu/libQtCore.so.4 : QEventLoop::processEvents(QFlagsQEventLoop::ProcessEventsFlag)+0x2f [0x7f96fdf848af] /usr/lib/x86_64-linux-gnu/libQtCore.so.4 : QEventLoop::exec(QFlagsQEventLoop::ProcessEventsFlag)+0x138 [0x7f96fdf84b38] /usr/lib/x86_64-linux-gnu/libQtCore.so.4 : QCoreApplication::exec()+0x88 [0x7f96fdf89cf8] qbittorrent : main()+0xca5 [0x480f05] /lib/x86_64-linux-gnu/libc.so.6 : __libc_start_main()+0xfd [0x7f96fd2feead] qbittorrent() [0x4898e1] Segmentation fault It doesn't segfault all the time, it only happened 3 or 4 times. Also it always happens randomly (at least I couldn't find the cause). -- System Information: Debian Release: 7.0 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-4-amd64 (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages qbittorrent depends on: ii geoip-database 20130213-1 ii libboost-filesystem1.49.0 1.49.0-3.2 ii libboost-system1.49.0 1.49.0-3.2 ii libc6 2.13-38 ii libgcc11:4.7.2-5 ii libqt4-dbus4:4.8.2+dfsg-11 ii libqt4-network 4:4.8.2+dfsg-11 ii libqt4-xml 4:4.8.2+dfsg-11 ii libqtcore4 4:4.8.2+dfsg-11 ii libqtgui4 4:4.8.2+dfsg-11 ii libssl1.0.01.0.1e-2 ii libstdc++6 4.7.2-5 ii libtorrent-rasterbar6 0.15.10-1+b1 ii python 2.7.3-4 qbittorrent recommends no packages. Versions of packages qbittorrent suggests: pn qbittorrent-dbg none -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#689328: strongswan: New upstream versison (5.0.0) available
Package: strongswan Severity: wishlist strongswan is now available in version 5.0.0. witgh several improvements -- System Information: Debian Release: 6.0.6 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.5.4.ja1 (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 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#500512: strange workaround
Hello, I also have the problem that in the SIP INVITE message according to wireshark the Message Body - Connection Information does show the eth0 IP address instead of the VPN tun0 IP address. My strange workaround is: Unplug the ethernet cable for eth0 before starting the call. This results in eth0 to be not RUNNING anymore according to ifconfig and the Connection Information to contain the correct VPN tun0 IP address! Linphone than retries to sent the SIP INVITE messages. So if I now plug in the ethernet cable again, linphone continues to retry to send the SIP INVITE message with the correct Connection Information and finally the call is established successfully. I'm using linphone 3.3.2. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#518786: Found in next version of kdebase
I'm experiencing the same effect in the next version of kdebase. 4:3.5.10.dfsg.1-2. Laptop monitor + external TFT. Using twinview, non-free nvidia drivers. It worked flawlessly until my last update. Before the update, each window maximized to the size of the monitor it was in. Now any maximized window it's the size of both monitors. The kde options under the Multiple monitors don't have any effect. Debian Sid, Amd64. Package: kdebase Status: install ok installed Priority: optional Section: kde Installed-Size: 68 Maintainer: Debian Qt/KDE Maintainers debian-qt-...@lists.debian.org Architecture: all Version: 4:3.5.10.dfsg.1-2 Depends: kappfinder (= 4:3.5.10.dfsg.1-2), kate (= 4:3.5.10.dfsg.1-2), kcontrol (= 4:3.5.10.dfsg.1-2), kdebase-bin (= 4:3.5.10.dfsg.1-2), kdebase-data (= 4:3.5.10.dfsg.1-2), kdebase-kio-plugins (= 4:3.5.10.dfsg.1-2), kdepasswd (= 4:3.5.10.dfsg.1-2), kdeprint (= 4:3.5.10.dfsg.1-2), kdesktop (= 4:3.5.10.dfsg.1-2), kfind (= 4:3.5.10.dfsg.1-2), khelpcenter (= 4:3.5.10.dfsg.1-2), kicker (= 4:3.5.10.dfsg.1-2), klipper (= 4:3.5.10.dfsg.1-2), kmenuedit (= 4:3.5.10.dfsg.1-2), konqueror-nsplugins (= 4:3.5.10.dfsg.1-2), konqueror (= 4:3.5.10.dfsg.1-2), konsole (= 4:3.5.10.dfsg.1-2), kpager (= 4:3.5.10.dfsg.1-2), kpersonalizer (= 4:3.5.10.dfsg.1-2), ksmserver (= 4:3.5.10.dfsg.1-2), ksplash (= 4:3.5.10.dfsg.1-2), ksysguard (= 4:3.5.10.dfsg.1-2), ktip (= 4:3.5.10.dfsg.1-2), kwin (= 4:3.5.10.dfsg.1-2), libkonq4 (= 4:3.5.10.dfsg.1-2), hal | kfreebsd-gnu | hurd, pmount | kfreebsd-gnu | hurd Recommends: kdm (= 4:3.5.10.dfsg.1-2) Suggests: kdebase-doc-html (= 4:3.5.10.dfsg.1-2) Package: kwin Status: install ok installed Priority: optional Section: kde Installed-Size: 3888 Maintainer: Debian Qt/KDE Maintainers debian-qt-...@lists.debian.org Architecture: amd64 Source: kdebase Version: 4:3.5.10.dfsg.1-2 Replaces: kdeartwork-theme-window ( 4:3.4.0), kdebase ( 4:3.0.0) Provides: x-window-manager Depends: kdelibs4c2a (= 4:3.5.9), libart-2.0-2 (= 2.3.18), libaudio2, libc6 (= 2.2.5), libfontconfig1 (= 2.4.0), libfreetype6 (= 2.2.1), libgcc1 (= 1:4.1.1), libice6 (= 1:1.0.0), libidn11 (= 0.5.18), libjpeg62, libpng12-0 (= 1.2.13-4), libqt3-mt (= 3:3.3.8b), libsm6, libstdc++6 (= 4.1.1), libx11-6, libxcomposite1 (= 1:0.3-1), libxcursor1 ( 1.1.2), libxdamage1 (= 1:1.1), libxext6, libxfixes3 (= 1:4.0.1), libxft2 ( 2.1.1), libxi6, libxinerama1, libxrandr2 (= 2:1.2.99.2), libxrender1, libxt6, zlib1g (= 1:1.1.4) Suggests: kdebase-bin (= 4:3.5.10.dfsg.1-2), kdebase-data ( 4:3.5.10.dfsg.1), kdebase-data ( 4:3.5.10.dfsg.2), kdesktop (= 4:3.5.10.dfsg.1-2), kicker (= 4:3.5.10.dfsg.1-2), kpager (= 4:3.5.10.dfsg.1-2), kpersonalizer (= 4:3.5.10.dfsg.1-2), ksmserver (= 4:3.5.10.dfsg.1-2), ksplash (= 4:3.5.10.dfsg.1-2)
Bug#373089: sarge backport
Hi, I´m new to the list and i have a question: Will that run on Debian Sarge? Can i make it run as daemon? Thanks a lot! -- .''`. John Doe : :' : LUGS: http://www.cafelug.org.ar/ http://www.lugsam.org.ar/ `. ``BLOG: http://www.los10binarios.com.ar/ `- UIN: 92831439 JID: [EMAIL PROTECTED] MSN: [EMAIL PROTECTED] Experiencia compartida, es experiencia adquirida.
