Bug#309752: kimdaba: Fails to install on Sid
Package: kimdaba Version: 2.0-3 Severity: important When I try to upgrade the kimdaba package on Sid, the system reports this message: The following packages have unmet dependencies: kimdaba: Depends: kdelibs4 (= 4:3.4.0) but 4:3.3.2-6 is to be installed E: Broken packages -- System Information: Debian Release: 3.1 APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.11-1-686-smp Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=UTF-8) Versions of packages kimdaba depends on: ii kdelibs4 4:3.3.2-6 KDE core libraries ii libart-2.0-2 2.3.17-1Library of functions for 2D graphi ii libc62.3.2.ds1-22GNU C Library: Shared libraries an ii libgamin0 [libfam0c102] 0.0.26-1Client library for the gamin file ii libgcc1 1:3.4.3-13 GCC support library ii libice6 4.3.0.dfsg.1-13 Inter-Client Exchange library ii libidn11 0.5.13-1.0 GNU libidn library, implementation ii libjpeg626b-10 The Independent JPEG Group's JPEG ii libpng12-0 1.2.8rel-1 PNG library - runtime ii libqt3c102-mt3:3.3.4-3 Qt GUI Library (Threaded runtime v ii libsm6 4.3.0.dfsg.1-13 X Window System Session Management ii libstdc++5 1:3.3.6-5 The GNU Standard C++ Library v3 ii libx11-6 4.3.0.dfsg.1-13 X Window System protocol client li ii libxext6 4.3.0.dfsg.1-13 X Window System miscellaneous exte ii libxrender1 1:0.8.3-1 X Rendering Extension client libra ii xlibs4.3.0.dfsg.1-13 X Keyboard Extension (XKB) configu ii zlib1g 1:1.2.2-4 compression library - runtime -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#420751: guess solved
Hello. Package: gforge Version: 4.5.14-22 with posgresql8.1 verify /etc/gforge/local.pl are correct. very important: $sys_dbhost = '127.0.0.1' ; $sys_dbname = 'gforge' ; $sys_dbuser = 'gforge' ; $sys_dbpasswd = 'passw' ; active tcp/ip for posgresql an check that. Ex. psql -d gforge -h X.X.X.X -U gforge Them remov or comment out this lines of this files: lines 33,35,36,37,2152,2154,2155 and 2156 of /usr/lib/gforge/bin/db-upgrade.pl lines 21,23,24 and 25 of /usr/lib/gforge/bin/prepare-vhosts-file.pl lines 22,24,25 and 26 of /usr/lib/gforge/plugins/scmsvn/bin/svn_dump.pl them dpkg --configure --pending this it would have solve de problem Thanks for the help. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#420751: gforge-db-postgresql fail during the instalallation
Package: gforge-db-postgresql Version: 4.5.14-22 gforge-db-postgresql Depends: gforge-common, postgresql | postgresql-7.4 | postgresql-8.0 | postgresql-8.1, perl, libdbi-perl, libdbd-pg-perl, libmime-base64-perl, libhtml-parser-perl, libtext-autoformat-perl, libmail-sendmail-perl, debianutils (= 1.7), debconf (= 1.0.32) | debconf-2.0, php4-cli, php4-cgi, php4-pgsql and i have: t-d-a:~# dpkg -l | grep postgresql iF gforge-db-postgresql 4.5.14-22collaborative development tool - database (u iU gforge-shell-postgresql 4.5.14-22collaborative development tool - shell accou ii postgresql-8.1 8.1.8-1 object-relational SQL database, version 8.1 ii postgresql-client-8.18.1.8-1 front-end programs for PostgreSQL 8.1 ii postgresql-client-common 71 manager for multiple PostgreSQL client versi ii postgresql-common71 manager for PostgreSQL database clusters that mean postgresql-8.1, and this should be resolv the dependency but: the first try was: t-d-a:~# aptitude install gforge this fail Setting up gforge-db-postgresql (4.5.14-22) ... but i not have the logs. then i try with: t-d-a:~# aptitude install gforge-db-postgresql Reading package lists... Done Building dependency tree... Done Reading extended state information Initializing package states... Done Reading task descriptions... Done Building tag database... Done No packages will be installed, upgraded, or removed. 0 packages upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Need to get 0B of archives. After unpacking 0B will be used. Writing extended state information... Done Setting up gforge-db-postgresql (4.5.14-22) ... /etc/postgresql/8.1/main//pg_hba.conf replacement already wanted, not changing. Calculating defaults Reading defaults from /etc/gforge/gforge.conf Creating /etc/gforge/gforge.conf Creating /etc/gforge/httpd.conf Creating /etc/gforge/httpd.secrets Creating /etc/gforge/local.inc Creating other includes Package `postgresql' is not installed and no info is available. Use dpkg --info (= dpkg-deb --info) to examine archive files, and dpkg --contents (= dpkg-deb --contents) to list their contents. dpkg: --compare-versions takes three arguments: version relation version Type dpkg --help for help about installing and deinstalling packages [*]; Use `dselect' or `aptitude' for user-friendly package management; Type dpkg -Dhelp for a list of dpkg debug flag values; Type dpkg --force-help for a list of forcing options; Type dpkg-deb --help for help about manipulating *.deb files; Type dpkg --license for copyright license and lack of warranty (GNU GPL) [*]. Options marked [*] produce a lot of output - pipe it through `less' or `more' ! Configuring for PostgreSQL 7.3 Package `postgresql' is not installed and no info is available. Use dpkg --info (= dpkg-deb --info) to examine archive files, and dpkg --contents (= dpkg-deb --contents) to list their contents. dpkg: --compare-versions takes three arguments: version relation version Type dpkg --help for help about installing and deinstalling packages [*]; Use `dselect' or `aptitude' for user-friendly package management; Type dpkg -Dhelp for a list of dpkg debug flag values; Type dpkg --force-help for a list of forcing options; Type dpkg-deb --help for help about manipulating *.deb files; Type dpkg --license for copyright license and lack of warranty (GNU GPL) [*]. Complete log on atach1. i try with dpkg --configure gforge-db-postgresql too. the logs on atach2 I suggest that resolv de confict I am using Debian GNU/Linux 4.0 Stable, kernel 2.6.17-2-686 and libc6 2.3.6.ds1-13 Thanks very much. t-d-a:~# aptitude install gforge-db-postgresql Reading package lists... Done Building dependency tree... Done Reading extended state information Initializing package states... Done Reading task descriptions... Done Building tag database... Done No packages will be installed, upgraded, or removed. 0 packages upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Need to get 0B of archives. After unpacking 0B will be used. Writing extended state information... Done Setting up gforge-db-postgresql (4.5.14-22) ... /etc/postgresql/8.1/main//pg_hba.conf replacement already wanted, not changing. Calculating defaults Reading defaults from /etc/gforge/gforge.conf Creating /etc/gforge/gforge.conf Creating /etc/gforge/httpd.conf Creating /etc/gforge/httpd.secrets Creating /etc/gforge/local.inc Creating other includes Package `postgresql' is not installed and no info is available. Use dpkg --info (= dpkg-deb --info) to examine archive files, and dpkg --contents (= dpkg-deb --contents) to list their contents. dpkg: --compare-versions takes three arguments: version relation version Type dpkg --help for help about installing and deinstalling packages [*]; Use `dselect' or `aptitude' for
Bug#360835: problem in /usr/share/language-env/dot.inputrc
Package: language-env Version: 0.66 Severity: normal I think that the file /usr/share/language-env/es/dot.inputrc does that I cannot write ñ € á, etc in console, the problem is the comments: the file contains: # s comment -*-coding: iso-8859-1;-*- For softwares which use readline library such as bash. END For softwares which use readline library such as bash. END # Sacado del Spanish-COMO set meta-flag on# conservar bit 8 en entrada de teclado set output-meta on # conservar bit 8 en salida por terminal set convert-meta off# no convertir secuencias de escape set horizontal-scroll-mode on and I think it should contains: # s comment -*-coding: iso-8859-1;-*- For softwares which use readline library such as bash. END For softwares which use readline library such as bash. END # Sacado del Spanish-COMO # conservar bit 8 en entrada de teclado set meta-flag on # conservar bit 8 en salida por terminal set output-meta on # no convertir secuencias de escape set convert-meta off set horizontal-scroll-mode on -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.12-1-386 Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) (ignored: LC_ALL set to [EMAIL PROTECTED]) Versions of packages language-env depends on: ii debconf [debconf-2.0] 1.4.71 Debian configuration management sy ii locales 2.3.5-8GNU C Library: National Language ( ii perl 5.8.7-10 Larry Wall's Practical Extraction Versions of packages language-env recommends: ii ncurses-term 5.5-1 Additional terminal type definitio ii tk8.4 [wish] 8.4.12-1 Tk toolkit for Tcl and X11, v8.4 - -- debconf information excluded
Bug#584204: (no subject)
Omar Campagne, try after with: update-rc.d plymouth remove update-rc.d plymouth defaults It works for me. But when I shutdown, console show and after plymouth. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#618713: gally: Gally does not work (Missing language definitios when starting)
Package: gally Version: 0.5.1-1 Severity: grave Justification: renders package unusable -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages gally depends on: ii python 2.6.6-3+squeeze5 interactive high-level object-orie ii python-kde4 4:4.4.5-4Python bindings for the KDE Develo ii python-qt4-phonon 4.8.3-1 Python bindings for Phonon ii python-support 1.0.11 automated rebuilding support for P gally recommends no packages. gally suggests no packages. -- no debconf information When gally is starting, there a message in the application stating: - Missing language definitions. Please download ASL lesson from http://launchpad.net/gally-asl Unfortunally, there is no README file and there is no a clear explanation how to do that. I've tried to go to the web page and download the package and put it where it is supposed to (compressed and uncompressed) and it didn't work either. Thanks. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#675554: version 1.1.3 has no debian package
Package: python-nose Version: 1.1.3 Current version is 1.1.2-3, but version 1.1.3 is already available to pack.
Bug#693512: network-manager: Network manager does not remove default routes
Package: network-manager Version: 0.9.4.0-6 Severity: normal I have 2 connections in my computer: eth0 : physical connectivity wlan0 : wireless connectivity I used to connect to my network through a physical connection but it is not in place anymore, so I decided to connect through wifi (wlan0). Network-manager is not removing the default routing I had before and every time I would like to connect I have to manually remove this route. As far as I understand from the network-manager, this should be automatically done by network-manager (removing and adding default new routes depending on current network connection) Here you have the example: /* System has booted up*/ $ netstat -nr Kernel IP routing table Destination Gateway Genmask Flags MSS Window irtt Iface 0.0.0.0 192.168.2.1 0.0.0.0 UG0 0 0 eth0 192.168.2.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 /* I connect to my wifi connection through network manager in KDE */ # netstat -nr Kernel IP routing table Destination Gateway Genmask Flags MSS Window irtt Iface 0.0.0.0 192.168.2.1 0.0.0.0 UG0 0 0 wlan0 192.168.2.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 192.168.2.0 0.0.0.0 255.255.255.0 U 0 0 0 wlan0 /* As you can see, eth0 configuration routing is still there!!) # route del -net 192.168.2.0 netmask 255.255.255.0 eth0 /* After deleting the default route, it is working again) # netstat -nr Kernel IP routing table Destination Gateway Genmask Flags MSS Window irtt Iface 0.0.0.0 192.168.2.1 0.0.0.0 UG0 0 0 wlan0 192.168.2.0 0.0.0.0 255.255.255.0 U 0 0 0 wlan0 /* Traffic is routed properly */ I have also modified NetworkManager configuration file to be able to manage the eth0 connection (according to http://wiki.debian.org/NetworkManager) with no success: $ cat /etc/NetworkManager/NetworkManager.conf [main] plugins=ifupdown,keyfile [ifupdown] managed=true -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages network-manager depends on: ii adduser3.113+nmu3 ii dbus 1.6.8-1 ii dpkg 1.16.9 ii isc-dhcp-client4.2.4-3 ii libc6 2.13-36 ii libdbus-1-31.6.8-1 ii libdbus-glib-1-2 0.100-1 ii libgcrypt111.5.0-3 ii libglib2.0-0 2.33.12+really2.32.4-3 ii libgnutls262.12.20-2 ii libgudev-1.0-0 175-7.1 ii libnl-3-2003.2.7-4 ii libnl-genl-3-200 3.2.7-4 ii libnl-route-3-200 3.2.7-4 ii libnm-glib40.9.4.0-6 ii libnm-util20.9.4.0-6 ii libpolkit-gobject-1-0 0.105-1 ii libuuid1 2.20.1-5.2 ii lsb-base 4.1+Debian8 ii udev 175-7.1 ii wpasupplicant 1.0-3+b2 Versions of packages network-manager recommends: ii crda 1.1.2-1 ii dnsmasq-base 2.63-4 ii iptables 1.4.16.3-4 ii modemmanager 0.5.2.0-2 ii policykit-1 0.105-1 ii ppp 2.4.5-5.1+b1 Versions of packages network-manager suggests: pn avahi-autoipd none -- Configuration Files: /etc/NetworkManager/NetworkManager.conf changed: [main] plugins=ifupdown,keyfile [ifupdown] managed=true -- 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#651229: console-setup: ckbcomp not found when booting
Package: console-setup Version: 1.75 Severity: important Tags: upstream When booting, you will see the following messages on the console: Tue Dec 6 22:26:34 2011: Setting parameters of disc: (none). Tue Dec 6 22:26:34 2011: Setting preliminary keymap.../bin/setupcon: 939: /bin/setupcon: /usr/bin/ckbcomp: not found Tue Dec 6 22:26:34 2011: done. This seems to be because /usr/bin/ckbcomp is not available at boot time as /usr filesystem is mounted afterwards. Perhaps a good idea will be to move ckbcomp to /bin (as it is needed at boot-time). Thanks. -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.1.0-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages console-setup depends on: ii console-setup-linux 1.75 ii debconf 1.5.41 ii keyboard-configuration 1.75 ii xkb-data2.1-2 console-setup recommends no packages. Versions of packages console-setup suggests: ii locales 2.13-21 ii lsb-base 3.2-28 Versions of packages keyboard-configuration depends on: ii debconf 1.5.41 ii initscripts 2.88dsf-13.13 ii liblocale-gettext-perl 1.05-7+b1 Versions of packages console-setup-linux depends on: ii kbd 1.15.3-7 ii keyboard-configuration 1.75 console-setup-linux suggests no packages. Versions of packages console-setup is related to: ii console-common none ii console-datanone ii console-tools none ii kbd 1.15.3-7 -- debconf information: console-setup/codeset47: # Latin1 and Latin5 - western Europe and Turkic languages keyboard-configuration/modelcode: pc105 keyboard-configuration/unsupported_config_options: true console-setup/fontface47: VGA keyboard-configuration/unsupported_config_layout: true keyboard-configuration/toggle: No toggling console-setup/fontsize-text47: 8x16 keyboard-configuration/compose: No compose key keyboard-configuration/layout: keyboard-configuration/xkb-keymap: es keyboard-configuration/variant: Spain debian-installer/console-setup-udeb/title: keyboard-configuration/switch: No temporary switch console-setup/charmap47: UTF-8 keyboard-configuration/unsupported_options: true keyboard-configuration/altgr: The default for the keyboard layout console-setup/framebuffer_only: keyboard-configuration/ctrl_alt_bksp: false console-setup/codesetcode: Lat15 keyboard-configuration/unsupported_layout: true console-setup/guess_font: keyboard-configuration/variantcode: keyboard-configuration/model: Generic 105-key (Intl) PC keyboard-configuration/layoutcode: es console-setup/store_defaults_in_debconf_db: true console-setup/fontsize-fb47: 8x16 keyboard-configuration/other: keyboard-configuration/store_defaults_in_debconf_db: true keyboard-configuration/optionscode: console-setup/use_system_font: console-setup/fontsize: 8x16 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#688979: ITP: python-doublex -- doublex is a test doubles framework for the Python platform
The description has some mistakes. Please, change it for this one: Description: doublex is a testing library for Python that allows to create mocks, stubs and spies. There are a lot of libraries for mocking in Python, but doublex is both the most complete and the more easy to use. It allows any kind of mocks, stubs and spies in a very pythonic way. It supports properties mocking and other advanced features. . One of the best improvements of this library is that it does not add any kind of public methods to the testing doubles, so it cannot match with any of the real object's functions. 2012/9/27 Miguel Ángel García miguelangel.gar...@gmail.com Package: wnpp Severity: wishlist Owner: Miguel Ángel García miguelangel.gar...@gmail.com * Package name: python-doublex Version : 0.6.1 Upstream Author : David Villa Alises david.vi...@gmail.com * URL : https://bitbucket.org/DavidVilla/python-doublex * License : GPL Programming Lang: Python Description : doublex is a test doubles framework for the Python platform doublex is a test doubles framework for the Python platform. Test doubles frameworks are also called mocking or isolation frameworks. doublex can be used as a testing tool or as a Test Driven Development tool. . It generates stubs, spies, and mock objects using a minimal interface. It support hamcrest matchers both stub definitions and spy checking. All assertions are done using hamcrest assert_that(). Moreover, it’s been designed to make your tests less fragile when possible. -- Miguel Ángel García Martínez http://www.magmax.org Mail miguelangel.gar...@gmail.com | Twitter http://twitter.com/#magmax9 | LinkedIn http://www.linkedin.com/in/miguelangelgarciamartinez | about.me http://about.me/miguelangelgarcia
Bug#743935: base: Once SD card safely removed, sometimes it is no more recognized until restart
Package: base Severity: normal Dear Maintainer, *** Please consider answering these questions, where appropriate *** * What led up to the situation? Formatting a SD card for different purposes and when I remove it safely from the computer, SOMETIMES it is no more recognized again, and when I didn't remove it safely, I don't remember to have this problem... * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? Debian does not recognize again the SD card hardware * What outcome did you expect instead? *** End of the template - remove these lines *** -- System Information: Debian Release: 7.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-4-amd64 (SMP w/2 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#856887: sddm default configuration is not properly taken
Package: sddm Version: 0.13.0-1 Severity: important Tags: upstream Dear Maintainer, sddm default "blue configuration" is not taking properly when the packages is upgraded to version 0.14 or above (bad theme and wrong configuration) Downgrading to version 0.13 makes sddm usable again with the default theme properly setup. Curious thing is when you lock your screen with 0.14, the right blue default theme is displayed (?), but not in the logout. If you need screenshots, just let me know, but it is very easy to reproduce. -- System Information: Debian Release: 9.0 APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 4.9.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages sddm depends on: ii adduser 3.115 ii debconf [debconf-2.0] 1.5.60 ii libc6 2.24-9 ii libgcc1 1:6.3.0-8 ii libpam0g1.1.8-3.5 ii libqt5core5a5.7.1+dfsg-3+b1 ii libqt5dbus5 5.7.1+dfsg-3+b1 ii libqt5gui5 5.7.1+dfsg-3+b1 ii libqt5network5 5.7.1+dfsg-3+b1 ii libqt5qml5 5.7.1-2 ii libqt5quick55.7.1-2 ii libstdc++6 6.3.0-8 ii libsystemd0 232-19 ii libxcb-xkb1 1.12-1 ii libxcb1 1.12-1 ii qml-module-qtquick2 5.7.1-2 ii sddm-theme-breeze [sddm-theme] 4:5.8.4-1 Versions of packages sddm recommends: ii libpam-systemd 232-19 Versions of packages sddm suggests: ii libpam-kwallet5 5.8.4-1 -- debconf information: * shared/default-x-display-manager: sddm sddm/daemon_name: /usr/bin/sddm
Bug#934648: nvidia-kernel-dkms: Nvidia 418.74 does not build with kernel 5.2.0 (put_user_pages)
Package: nvidia-kernel-dkms Version: 418.74-1 Severity: normal Tags: a11y Dear Maintainer, Nvidia 418.74 fails to compile with kernel 5.2.0 after kernel upgrade, therefore nvidia modules cannot be loaded and X system is not working. It seems it may be related to put_user_pages() according to DKMS compilation log (/var/lib/dkms/nvidia-current/418.74/build/make.log -- Package-specific info: uname -a: Linux drizzt 5.2.0-2-amd64 #1 SMP Debian 5.2.7-1 (2019-08-07) x86_64 GNU/Linux /proc/version: Linux version 5.2.0-2-amd64 (debian-ker...@lists.debian.org) (gcc version 8.3.0 (Debian 8.3.0-19)) #1 SMP Debian 5.2.7-1 (2019-08-07) lspci 'display controller [030?]': 01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GK104 [GeForce GTX 760] [10de:1187] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GK104 [GeForce GTX 760] [1043:847a] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel modules: nvidia dmesg: Device node permissions: video:x:44:sddm,miguel OpenGL and NVIDIA library files installed: -rw-r--r-- 1 root root 1337 Jul 2 2018 /etc/X11/xorg.conf lrwxrwxrwx 1 root root 15 Feb 13 23:31 /etc/alternatives/glx -> /usr/lib/nvidia lrwxrwxrwx 1 root root 51 Feb 13 23:31 /etc/alternatives/glx--libEGL.so.1-x86_64-linux-gnu -> /usr/lib/mesa-diverted/x86_64-linux-gnu/libEGL.so.1 lrwxrwxrwx 1 root root 50 Feb 13 23:31 /etc/alternatives/glx--libGL.so.1-x86_64-linux-gnu -> /usr/lib/mesa-diverted/x86_64-linux-gnu/libGL.so.1 lrwxrwxrwx 1 root root 50 Feb 13 23:31 /etc/alternatives/glx--libGL.so.1-x86_64-linux-gnu -> /usr/lib/mesa-diverted/x86_64-linux-gnu/libGL.so.1 lrwxrwxrwx 1 root root 54 Feb 13 23:31 /etc/alternatives/glx--libGLESv2.so.2-x86_64-linux-gnu -> /usr/lib/mesa-diverted/x86_64-linux-gnu/libGLESv2.so.2 lrwxrwxrwx 1 root root 54 Feb 13 23:31 /etc/alternatives/glx--libGLESv2.so.2-x86_64-linux-gnu -> /usr/lib/mesa-diverted/x86_64-linux-gnu/libGLESv2.so.2 lrwxrwxrwx 1 root root 44 Feb 13 23:31 /etc/alternatives/glx--libGLX_indirect.so.0-x86_64-linux-gnu -> /usr/lib/x86_64-linux-gnu/libGLX_nvidia.so.0 lrwxrwxrwx 1 root root 44 Feb 13 23:31 /etc/alternatives/glx--libGLX_indirect.so.0-x86_64-linux-gnu -> /usr/lib/x86_64-linux-gnu/libGLX_nvidia.so.0 lrwxrwxrwx 1 root root 38 Feb 13 23:31 /etc/alternatives/glx--libglxserver_nvidia.so -> /usr/lib/nvidia/libglxserver_nvidia.so lrwxrwxrwx 1 root root 51 Feb 13 23:31 /etc/alternatives/glx--libnvidia-cfg.so.1-x86_64-linux-gnu -> /usr/lib/x86_64-linux-gnu/nvidia/libnvidia-cfg.so.1 lrwxrwxrwx 1 root root 42 Feb 13 23:31 /etc/alternatives/glx--nvidia-blacklists-nouveau.conf -> /etc/nvidia/nvidia-blacklists-nouveau.conf lrwxrwxrwx 1 root root 36 Feb 13 23:31 /etc/alternatives/glx--nvidia-bug-report.sh -> /usr/lib/nvidia/nvidia-bug-report.sh lrwxrwxrwx 1 root root 39 Feb 13 23:31 /etc/alternatives/glx--nvidia-drm-outputclass.conf -> /etc/nvidia/nvidia-drm-outputclass.conf lrwxrwxrwx 1 root root 28 Feb 13 23:31 /etc/alternatives/glx--nvidia-load.conf -> /etc/nvidia/nvidia-load.conf lrwxrwxrwx 1 root root 32 Feb 13 23:31 /etc/alternatives/glx--nvidia-modprobe.conf -> /etc/nvidia/nvidia-modprobe.conf lrwxrwxrwx 1 root root 29 Feb 13 23:31 /etc/alternatives/glx--nvidia_drv.so -> /usr/lib/nvidia/nvidia_drv.so lrwxrwxrwx 1 root root 23 May 15 11:21 /etc/alternatives/nvidia -> /usr/lib/nvidia/current lrwxrwxrwx 1 root root 59 May 15 11:21 /etc/alternatives/nvidia--libEGL_nvidia.so.0-x86_64-linux-gnu -> /usr/lib/x86_64-linux-gnu/nvidia/current/libEGL_nvidia.so.0 lrwxrwxrwx 1 root root 62 May 15 11:21 /etc/alternatives/nvidia--libGLESv2_nvidia.so.2-x86_64-linux-gnu -> /usr/lib/x86_64-linux-gnu/nvidia/current/libGLESv2_nvidia.so.2 lrwxrwxrwx 1 root root 62 May 15 11:21 /etc/alternatives/nvidia--libGLESv2_nvidia.so.2-x86_64-linux-gnu -> /usr/lib/x86_64-linux-gnu/nvidia/current/libGLESv2_nvidia.so.2 lrwxrwxrwx 1 root root 59 May 15 11:21 /etc/alternatives/nvidia--libGLX_nvidia.so.0-x86_64-linux-gnu -> /usr/lib/x86_64-linux-gnu/nvidia/current/libGLX_nvidia.so.0 lrwxrwxrwx 1 root root 59 May 15 11:21 /etc/alternatives/nvidia--libGLX_nvidia.so.0-x86_64-linux-gnu -> /usr/lib/x86_64-linux-gnu/nvidia/current/libGLX_nvidia.so.0 lrwxrwxrwx 1 root root 46 May 15 11:21 /etc/alternatives/nvidia--libglxserver_nvidia.so -> /usr/lib/nvidia/current/libglxserver_nvidia.so lrwxrwxrwx 1 root root 59 May 15 11:21 /etc/alternatives/nvidia--libnvidia-cfg.so.1-x86_64-linux-gnu -> /usr/lib/x86_64-linux-gnu/nvidia/current/libnvidia-cfg.so.1 lrwxrwxrwx 1 root root 58 May 15 11:21 /etc/alternatives/nvidia--libnvidia-ml.so.1-x86_64-linux-gnu -> /usr/lib/x86_64-linux-gnu/nvidia/current/libnvidia-ml.so.1 lrwxrwxrwx 1
Bug#1052012: plasma-workspace: sddm presents a white screen with no background nor buttons
Package: plasma-workspace Version: 4:5.27.8-1 Severity: important X-Debbugs-Cc: mianro...@gmail.com After upgrading from 4:5.27-7-1, sddm because unusuable. Background is ignored (white), there are no button on the screen and the only thing you can see on the screen is the icon showing the user and password field below it (with very tiny asterisks) in a horrible format. -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 6.5.0-1-amd64 (SMP w/20 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages plasma-workspace depends on: ii dbus-user-session [default-dbus-session-bus] 1.14.10-1 ii drkonqi 5.27.8-1 ii frameworkintegration 5.107.0-1 ii gdb-minimal [gdb]13.2-1 ii init-system-helpers 1.65.2 ii iso-codes4.15.0-1 ii kactivitymanagerd5.27.8-1 ii kded55.107.0-1 ii kinit5.107.0-1 ii kio 5.107.0-1 ii kpackagetool55.107.0-1 ii kwin-common 4:5.27.8-1 ii libappstreamqt2 0.16.3-1 ii libc62.37-9 ii libcolorcorrect5 4:5.27.8-1 ii libcrypt11:4.4.36-2 ii libfontconfig1 2.14.2-6 ii libfreetype6 2.13.2+dfsg-1 ii libgcc-s113.2.0-4 ii libgps30 3.25-2 ii libice6 2:1.0.10-1 ii libicu72 72.1-3 ii libkf5activities55.107.0-1 ii libkf5activitiesstats1 5.107.0-1 ii libkf5archive5 5.107.0-1 ii libkf5authcore5 5.107.0-1 ii libkf5baloo5 5.107.0-1 ii libkf5bookmarks5 5.107.0-1 ii libkf5calendarevents55.107.0-1 ii libkf5completion55.107.0-1 ii libkf5config-bin 5.107.0-1 ii libkf5configcore55.107.0-1 ii libkf5configgui5 5.107.0-1 ii libkf5configwidgets5 5.107.0-2 ii libkf5coreaddons55.107.0-1 ii libkf5crash5 5.107.0-1 ii libkf5dbusaddons55.107.0-1 ii libkf5declarative5 5.107.0-1 ii libkf5globalaccel-bin5.107.0-2 ii libkf5globalaccel5 5.107.0-2 ii libkf5guiaddons5 5.107.0-1 ii libkf5holidays5 1:5.107.0-1 ii libkf5i18n5 5.107.0-1+b1 ii libkf5iconthemes55.107.0-1+b1 ii libkf5idletime5 5.107.0-1 ii libkf5jobwidgets55.107.0-1 ii libkf5kcmutils5 5.107.0-2 ii libkf5kexiv2-15.0.0 23.04.2-2 ii libkf5kiocore5 5.107.0-1 ii libkf5kiofilewidgets55.107.0-1 ii libkf5kiogui55.107.0-1 ii libkf5kiowidgets55.107.0-1 ii libkf5networkmanagerqt6 5.107.0-1 ii libkf5newstuff5 5.107.0-1 ii libkf5newstuffcore5 5.107.0-1 ii libkf5newstuffwidgets5 5.107.0-1 ii libkf5notifications5 5.107.0-1 ii libkf5notifyconfig5 5.107.0-1 ii libkf5package5 5.107.0-1 ii libkf5parts5 5.107.0-1 ii libkf5people55.107.0-1 ii
Bug#1053886: apt autoremove removes old kernel (ignoring default configuration)
Package: apt Version: 2.7.3 Severity: normal X-Debbugs-Cc: mianro...@gmail.com Beside the fact that kernel packages should not removed by default (according to /etc/apt/apt.conf.d/01autoremove), older kernel packages are removed after executing 'apt autoremove'. Regards -- Package-specific info: -- apt-config dump -- APT ""; APT::Architecture "amd64"; APT::Build-Essential ""; APT::Build-Essential:: "build-essential"; APT::Install-Recommends "1"; APT::Install-Suggests "0"; APT::Sandbox ""; APT::Sandbox::User "_apt"; APT::Authentication ""; APT::Authentication::TrustCDROM "true"; APT::NeverAutoRemove ""; APT::NeverAutoRemove:: "^firmware-linux.*"; APT::NeverAutoRemove:: "^linux-firmware$"; APT::NeverAutoRemove:: "^linux-image-[a-z0-9]*$"; APT::NeverAutoRemove:: "^linux-image-[a-z0-9]*-[a-z0-9]*$"; APT::VersionedKernelPackages ""; APT::VersionedKernelPackages:: "linux-.*"; APT::VersionedKernelPackages:: "kfreebsd-.*"; APT::VersionedKernelPackages:: "gnumach-.*"; APT::VersionedKernelPackages:: ".*-modules"; APT::VersionedKernelPackages:: ".*-kernel"; APT::Never-MarkAuto-Sections ""; APT::Never-MarkAuto-Sections:: "metapackages"; APT::Never-MarkAuto-Sections:: "tasks"; APT::Move-Autobit-Sections ""; APT::Move-Autobit-Sections:: "oldlibs"; APT::Update ""; APT::Update::Post-Invoke-Success ""; APT::Update::Post-Invoke-Success:: "/usr/bin/test -e /usr/share/dbus-1/system-services/org.freedesktop.PackageKit.service && /usr/bin/test -S /var/run/dbus/system_bus_socket && /usr/bin/gdbus call --system --dest org.freedesktop.PackageKit --object-path /org/freedesktop/PackageKit --timeout 4 --method org.freedesktop.PackageKit.StateHasChanged cache-update > /dev/null; /bin/echo > /dev/null"; APT::Update::Post-Invoke-Success:: "if /usr/bin/test -w /var/cache/swcatalog -a -e /usr/bin/appstreamcli; then appstreamcli refresh --source=os > /dev/null || true; fi"; APT::Architectures ""; APT::Architectures:: "amd64"; APT::Compressor ""; APT::Compressor::. ""; APT::Compressor::.::Name "."; APT::Compressor::.::Extension ""; APT::Compressor::.::Binary ""; APT::Compressor::.::Cost "0"; APT::Compressor::zstd ""; APT::Compressor::zstd::Name "zstd"; APT::Compressor::zstd::Extension ".zst"; APT::Compressor::zstd::Binary "zstd"; APT::Compressor::zstd::Cost "60"; APT::Compressor::zstd::CompressArg ""; APT::Compressor::zstd::CompressArg:: "-19"; APT::Compressor::zstd::UncompressArg ""; APT::Compressor::zstd::UncompressArg:: "-d"; APT::Compressor::lz4 ""; APT::Compressor::lz4::Name "lz4"; APT::Compressor::lz4::Extension ".lz4"; APT::Compressor::lz4::Binary "false"; APT::Compressor::lz4::Cost "50"; APT::Compressor::gzip ""; APT::Compressor::gzip::Name "gzip"; APT::Compressor::gzip::Extension ".gz"; APT::Compressor::gzip::Binary "gzip"; APT::Compressor::gzip::Cost "100"; APT::Compressor::gzip::CompressArg ""; APT::Compressor::gzip::CompressArg:: "-6n"; APT::Compressor::gzip::UncompressArg ""; APT::Compressor::gzip::UncompressArg:: "-d"; APT::Compressor::xz ""; APT::Compressor::xz::Name "xz"; APT::Compressor::xz::Extension ".xz"; APT::Compressor::xz::Binary "xz"; APT::Compressor::xz::Cost "200"; APT::Compressor::xz::CompressArg ""; APT::Compressor::xz::CompressArg:: "-6"; APT::Compressor::xz::UncompressArg ""; APT::Compressor::xz::UncompressArg:: "-d"; APT::Compressor::bzip2 ""; APT::Compressor::bzip2::Name "bzip2"; APT::Compressor::bzip2::Extension ".bz2"; APT::Compressor::bzip2::Binary "bzip2"; APT::Compressor::bzip2::Cost "300"; APT::Compressor::bzip2::CompressArg ""; APT::Compressor::bzip2::CompressArg:: "-6"; APT::Compressor::bzip2::UncompressArg ""; APT::Compressor::bzip2::UncompressArg:: "-d"; APT::Compressor::lzma ""; APT::Compressor::lzma::Name "lzma"; APT::Compressor::lzma::Extension ".lzma"; APT::Compressor::lzma::Binary "xz"; APT::Compressor::lzma::Cost "400"; APT::Compressor::lzma::CompressArg ""; APT::Compressor::lzma::CompressArg:: "--format=lzma"; APT::Compressor::lzma::CompressArg:: "-6"; APT::Compressor::lzma::UncompressArg ""; APT::Compressor::lzma::UncompressArg:: "--format=lzma"; APT::Compressor::lzma::UncompressArg:: "-d"; Dir "/"; Dir::State "var/lib/apt"; Dir::State::lists "lists/"; Dir::State::cdroms "cdroms.list"; Dir::State::extended_states "extended_states"; Dir::State::status "/var/lib/dpkg/status"; Dir::Cache "var/cache/apt"; Dir::Cache::archives "archives/"; Dir::Cache::srcpkgcache "srcpkgcache.bin"; Dir::Cache::pkgcache "pkgcache.bin"; Dir::Etc "etc/apt"; Dir::Etc::sourcelist "sources.list"; Dir::Etc::sourceparts "sources.list.d"; Dir::Etc::main "apt.conf"; Dir::Etc::netrc "auth.conf"; Dir::Etc::netrcparts "auth.conf.d"; Dir::Etc::parts "apt.conf.d"; Dir::Etc::preferences "preferences"; Dir::Etc::preferencesparts "preferences.d"; Dir::Etc::trusted "trusted.gpg"; Dir::Etc::trustedparts "trusted.gpg.d"; Dir::Etc::apt-file-main "apt-file.conf"; Dir::Bin ""; Dir::Bin::methods "/usr/lib/apt/methods"; Dir::Bin::solvers ""; Dir::Bin::solvers:: "/usr/lib/apt/solvers"; Dir::Bin::planners "";
Bug#1062703: firmware-realtek: Direct firmware load for rtl_nic/rtl8125b-2.fw failed with error -2
Package: firmware-realtek Version: 20230625-2 Severity: important X-Debbugs-Cc: mianro...@gmail.com At system boot, the following message is shown: "Direct firmware load for rtl_nic/rtl8125b-2.fw failed with error -2". It seesm that the firmware is not properly loaded by kernel at boot. -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 6.6.13-amd64 (SMP w/20 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled firmware-realtek depends on no packages. firmware-realtek recommends no packages. Versions of packages firmware-realtek suggests: ii initramfs-tools 0.142 -- no debconf information
Bug#1065831: apt tries to uninstall kde & plasma (full-upgrade)
Package: apt Version: 2.7.13+b1 Severity: normal X-Debbugs-Cc: mianro...@gmail.com # apt full-upgrade Reading package lists... Done Building dependency tree... Done Reading state information... Done Calculating upgrade... Error! Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: plasma-workspace : Depends: gdb-minimal but it is not going to be installed or gdb E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages. I don't know why plasma-workspace depends on gdb, but nevertheless, full-upgrade doesn't work. I've seen other users are experimenting the same issue: https://groups.google.com/g/linux.debian.user/c/7gpQImSH-Cs If you mark plasma-workspace as hold, apt is still trying to remove other kde & plasma package (its reverse dependencies). -- Package-specific info: -- apt-config dump -- APT ""; APT::Architecture "amd64"; APT::Build-Essential ""; APT::Build-Essential:: "build-essential"; APT::Install-Recommends "1"; APT::Install-Suggests "0"; APT::Key ""; APT::Key::Assert-Pubkey-Algo ">=rsa2048,ed25519,ed448"; APT::Sandbox ""; APT::Sandbox::User "_apt"; APT::Authentication ""; APT::Authentication::TrustCDROM "true"; APT::NeverAutoRemove ""; APT::NeverAutoRemove:: "^firmware-linux.*"; APT::NeverAutoRemove:: "^linux-firmware$"; APT::NeverAutoRemove:: "^linux-image-[a-z0-9]*$"; APT::NeverAutoRemove:: "^linux-image-[a-z0-9]*-[a-z0-9]*$"; APT::VersionedKernelPackages ""; APT::VersionedKernelPackages:: "linux-.*"; APT::VersionedKernelPackages:: "kfreebsd-.*"; APT::VersionedKernelPackages:: "gnumach-.*"; APT::VersionedKernelPackages:: ".*-modules"; APT::VersionedKernelPackages:: ".*-kernel"; APT::Never-MarkAuto-Sections ""; APT::Never-MarkAuto-Sections:: "metapackages"; APT::Never-MarkAuto-Sections:: "tasks"; APT::Move-Autobit-Sections ""; APT::Move-Autobit-Sections:: "oldlibs"; APT::Update ""; APT::Update::Post-Invoke-Success ""; APT::Update::Post-Invoke-Success:: "/usr/bin/test -e /usr/share/dbus-1/system-services/org.freedesktop.PackageKit.service && /usr/bin/test -S /var/run/dbus/system_bus_socket && /usr/bin/gdbus call --system --dest org.freedesktop.PackageKit --object-path /org/freedesktop/PackageKit --timeout 4 --method org.freedesktop.PackageKit.StateHasChanged cache-update > /dev/null; /bin/echo > /dev/null"; APT::Update::Post-Invoke-Success:: "if /usr/bin/test -w /var/cache/swcatalog -a -e /usr/bin/appstreamcli; then appstreamcli refresh --source=os > /dev/null || true; fi"; APT::Architectures ""; APT::Architectures:: "amd64"; APT::Compressor ""; APT::Compressor::. ""; APT::Compressor::.::Name "."; APT::Compressor::.::Extension ""; APT::Compressor::.::Binary ""; APT::Compressor::.::Cost "0"; APT::Compressor::zstd ""; APT::Compressor::zstd::Name "zstd"; APT::Compressor::zstd::Extension ".zst"; APT::Compressor::zstd::Binary "zstd"; APT::Compressor::zstd::Cost "60"; APT::Compressor::zstd::CompressArg ""; APT::Compressor::zstd::CompressArg:: "-19"; APT::Compressor::zstd::UncompressArg ""; APT::Compressor::zstd::UncompressArg:: "-d"; APT::Compressor::lz4 ""; APT::Compressor::lz4::Name "lz4"; APT::Compressor::lz4::Extension ".lz4"; APT::Compressor::lz4::Binary "false"; APT::Compressor::lz4::Cost "50"; APT::Compressor::gzip ""; APT::Compressor::gzip::Name "gzip"; APT::Compressor::gzip::Extension ".gz"; APT::Compressor::gzip::Binary "gzip"; APT::Compressor::gzip::Cost "100"; APT::Compressor::gzip::CompressArg ""; APT::Compressor::gzip::CompressArg:: "-6n"; APT::Compressor::gzip::UncompressArg ""; APT::Compressor::gzip::UncompressArg:: "-d"; APT::Compressor::xz ""; APT::Compressor::xz::Name "xz"; APT::Compressor::xz::Extension ".xz"; APT::Compressor::xz::Binary "xz"; APT::Compressor::xz::Cost "200"; APT::Compressor::xz::CompressArg ""; APT::Compressor::xz::CompressArg:: "-6"; APT::Compressor::xz::UncompressArg ""; APT::Compressor::xz::UncompressArg:: "-d"; APT::Compressor::bzip2 ""; APT::Compressor::bzip2::Name "bzip2"; APT::Compressor::bzip2::Extension ".bz2"; APT::Compressor::bzip2::Binary "bzip2"; APT::Compressor::bzip2::Cost "300"; APT::Compressor::bzip2::CompressArg ""; APT::Compressor::bzip2::CompressArg:: "-6"; APT::Compressor::bzip2::UncompressArg ""; APT::Compressor::bzip2::UncompressArg:: "-d"; APT::Compressor::lzma ""; APT::Compressor::lzma::Name "lzma"; APT::Compressor::lzma::Extension ".lzma"; APT::Compressor::lzma::Binary "xz"; APT::Compressor::lzma::Cost "400"; APT::Compressor::lzma::CompressArg ""; APT::Compressor::lzma::CompressArg:: "--format=lzma"; APT::Compressor::lzma::CompressArg:: "-6"; APT::Compressor::lzma::UncompressArg ""; APT::Compressor::lzma::UncompressArg:: "--format=lzma";
Bug#335559: knockd: Knockd receive the tcp and udp packets, but it dont execute any command.
Package: knockd Version: 0.5-1 Severity: normal This is the configuracion of knockd.conf, its very simple. [options] logfile = /var/log/knockd.log [helloworld] sequence = 5000:tcp seq_timeout = 10 tcpflags = syn command = /sbin/iptables -A INPUT -s %IP% -p tcp --dport 22 -j ACCEPT When I send a tcp packet to 5000 port, the knockd detect it, but it dont execute the command. [2005-10-24 16:11] starting up, listening on eth0 [2005-10-24 16:11] xxx.xxx.xxx.xxx: helloworld: Stage 1 (I change the IP with xxx) I change the command and write a echo command to a file, a reboot and a lot of other commands, without any success. Where is the problem? Do you need more information? Sorry for my english. Thank you! -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.13.4 Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) Versions of packages knockd depends on: ii libc6 2.3.5-7GNU C Library: Shared libraries an ii libpcap0.80.9.4-1System interface for user-level pa ii logrotate 3.7.1-2Log rotation utility knockd recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#461459: New upstream version available
Package: mail-notification Version: 4.1.dfsg.1-2 Severity: wishlist There is a new upstream version available at http://www.nongnu.org/mailnotify/ Current stable upstream version: 5.0 Current version in Debian Unstable: 4.1.dfsg.1-4.1 The latest version includes a lot of bug fixes and new features, such as: * A consider new mail as read action has been added. * An optional message count has been added over the icon. * A Play a sound when new mail arrives option has been added. * Passwords are now stored using GNOME Keyring. * Gmail label support has been added. * Yahoo! Mail support has been added. * Windows Live Hotmail support has been added. * A number of minor issues have been fixed. * And more, see the NEWS file. It would be great if the Debian package could be updated. Cheers, --- System information. --- Architecture: i386 Kernel: Linux 2.6.22-3-686 Debian Release: lenny/sid 500 testing security.debian.org 500 testing ftp.cl.debian.org 500 testing debian.utalca.cl --- Package information. --- Depends (Version) | Installed =-+-== libart-2.0-2 (= 2.3.18) | 2.3.19-3 libatk1.0-0 (= 1.13.2) | 1.20.0-1 libbonobo2-0 (= 2.15.0) | 2.20.2-1 libbonoboui2-0(= 2.15.1) | 2.20.0-1 libc6 (= 2.6-1) | 2.7-5 libcairo2 (= 1.4.0) | 1.4.10-1+lenny2 libdbus-1-3(= 1.1.1) | 1.1.2-1 libdbus-glib-1-2(= 0.74) | 0.74-1 libeel2-2.18 | 2.18.3-1 libfontconfig1 (= 2.4.0) | 2.5.0-2 libgail-common(= 1.10.1) | 1.20.2-1 libgail18 (= 1.10.1) | 1.20.2-1 libgconf2-4 (= 2.13.5) | 2.20.1-2 libglade2-0 (= 1:2.6.1) | 1:2.6.2-1 libglib2.0-0 (= 2.12.9) | 2.14.3-1 libgmime-2.0-2| 2.2.12-1 libgnome-keyring0(= 0.8) | 2.20.2-1 libgnome2-0 (= 2.17.3) | 2.20.1.1-1 libgnomecanvas2-0 (= 2.11.1) | 2.20.1.1-1 libgnomeui-0 (= 2.17.1) | 2.20.1.1-1 libgnomevfs2-0 (= 1:2.17.90) | 1:2.20.1-1 libgtk2.0-0(= 2.10.12-3) | 2.12.1-1 libice6 (= 1:1.0.0) | 2:1.0.4-1 libnotify1 (= 0.4.4) | 0.4.4-3 libnotify1-gtk2.10| liborbit2 (= 1:2.14.1) | 1:2.14.7-0.1 libpango1.0-0 (= 1.16.5) | 1.18.3-1 libpopt0(= 1.10) | 1.10-3 libsasl2-2| 2.1.22.dfsg1-16 libsm6| 2:1.0.3-1+b1 libx11-6 | 2:1.0.3-7 libxcursor1( 1.1.2) | 1:1.1.9-1 libxext6 | 1:1.0.3-2 libxfixes3 (= 1:4.0.1) | 1:4.0.3-2 libxi6| 2:1.1.3-1 libxinerama1 | 1:1.0.2-1 libxml2 (= 2.6.29) | 2.6.30.dfsg-3 libxrandr2 (= 2:1.2.0) | 2:1.2.2-1 libxrender1 | 1:0.9.4-1 zlib1g (= 1:1.2.3.3.dfsg-1) | 1:1.2.3.3.dfsg-8 gnome-icon-theme | 2.20.0-1 notification-daemon | 0.3.7-1+b1 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#459122: A possible fix (debdiff attached)
Package: quagga
Hi,
I'm sending a candidate patch to fix the problem.
Thanks in advance!
--- System information. ---
Architecture: i386
Kernel: Linux 2.6.22-3-686
Debian Release: lenny/sid
500 testing security.debian.org
500 testing ftp.cl.debian.org
--- Package information. ---
Depends (Version) | Installed
===-+-===
|
--
Miguel Angel Ruiz Manzanohttp://vulcano.mine.nu
Computer Science Student - PUCV - Chile
diff -u quagga-0.99.9/debian/rules quagga-0.99.9/debian/rules
--- quagga-0.99.9/debian/rules
+++ quagga-0.99.9/debian/rules
@@ -30,7 +30,8 @@
fi
# Update config.*
- cp /usr/share/misc/config.{guess,sub} .
+ cp /usr/share/misc/config.guess .
+ cp /usr/share/misc/config.sub .
# according to redhad/quagga.spec as of 2003-08-18
./configure \
@@ -100,7 +101,11 @@
-$(MAKE) distclean
@echo BEGIN CRUFT
- @rm -vf */Makefile doc/quagga.{fns,kys,tmp,pdf,info-*} doc/quagga.info
+ @rm -vf */Makefile doc/quagga.fns doc/quagga.info
+ @rm -vf */Makefile doc/quagga.kys doc/quagga.info
+ @rm -vf */Makefile doc/quagga.tmp doc/quagga.info
+ @rm -vf */Makefile doc/quagga.pdf doc/quagga.info
+ @rm -vf */Makefile doc/quagga.info-* doc/quagga.info
@rm -vf lib/version.c doc/stamp-vti
@rm -vf vtysh/vtysh_cmd.c
@rm -vf doc/fig*.pdf
diff -u quagga-0.99.9/debian/changelog quagga-0.99.9/debian/changelog
--- quagga-0.99.9/debian/changelog
+++ quagga-0.99.9/debian/changelog
@@ -1,3 +1,10 @@
+quagga (0.99.9-2.1) unstable; urgency=low
+
+ * Non-maintainer upload.
+ * debian/rules: fixed bashisms. (Closes: #459122)
+
+ -- Miguel Angel Ruiz Manzano [EMAIL PROTECTED] Mon, 21 Jan 2008 16:21:43
-0300
+
quagga (0.99.9-2) unstable; urgency=low
* Added CVE id for the security bug to the last changelog entry.
signature.asc
Description: OpenPGP digital signature
Bug#459131: A possible fix (debdiff attached)
Package: squid-prefetch
Hi,
I'm sending a patch to fix the problem.
Thanks in advance!
--
Miguel Angel Ruiz Manzanohttp://vulcano.mine.nu
Computer Science Student - PUCV - Chile
diff -Nru squid-prefetch-1.1/debian/changelog
squid-prefetch-1.1/debian/changelog
--- squid-prefetch-1.1/debian/changelog 2006-12-04 17:27:39.0 -0300
+++ squid-prefetch-1.1/debian/changelog 2008-01-21 12:15:33.0 -0300
@@ -1,3 +1,10 @@
+squid-prefetch (1.1-2.1) unstable; urgency=low
+
+ * Non-maintainer upload.
+ * debian/rules: fixed bashisms. (Closes: #459131)
+
+ -- Miguel Angel Ruiz Manzano [EMAIL PROTECTED] Mon, 21 Jan 2008 12:15:15
-0300
+
squid-prefetch (1.1-2) unstable; urgency=medium
* added postinst warning if /etc/squid.conf still exists (closes: #308010)
diff -Nru /tmp/DUXlehluRz/squid-prefetch-1.1/debian/rules
/tmp/G0r8P0vrmE/squid-prefetch-1.1/debian/rules
--- squid-prefetch-1.1/debian/rules 2003-08-11 17:14:17.0 -0400
+++ squid-prefetch-1.1/debian/rules 2008-01-21 12:04:42.0 -0300
@@ -40,7 +40,9 @@
-rm -rf debian/tmp
mkdir -p debian/tmp/DEBIAN debian/tmp/usr/share/doc/$(package)
mkdir -p debian/tmp/usr/sbin debian/tmp/etc/init.d
debian/tmp/usr/share/man/man8
- cp debian/{postinst,prerm,postrm} debian/tmp/DEBIAN/
+ cp debian/postinst debian/tmp/DEBIAN/
+ cp debian/prerm debian/tmp/DEBIAN/
+ cp debian/postrm debian/tmp/DEBIAN/
chmod 755 debian/tmp/DEBIAN/*
cp debian/conffiles debian/tmp/DEBIAN/conffiles
# make install PREFIX=debian/tmp/usr MANDIR=debian/tmp/usr/share/man
signature.asc
Description: OpenPGP digital signature
Bug#459133: A possible fix (debdiff attached)
Package: squidtaild
Hi,
I'm sending a patch to fix the problem.
Thanks in advance!
--
Miguel Angel Ruiz Manzanohttp://vulcano.mine.nu
Computer Science Student - PUCV - Chile
diff -u squidtaild-2.1a6/debian/rules squidtaild-2.1a6/debian/rules
--- squidtaild-2.1a6/debian/rules
+++ squidtaild-2.1a6/debian/rules
@@ -49,7 +49,8 @@
gzip -9f $(tmp)/usr/share/man/man8/squidtaild.8
chmod 644 $(tmp)/etc/squidtaild/squidtaild.conf
cp -r sbin $(tmp)/usr
- chmod -R o+rX $(tmp)/{etc,usr}
+ chmod -R o+rX $(tmp)/etc
+ chmod -R o+rX $(tmp)/usr
touch $(tmp)/usr/share/doc/squidtaild/overview.txt
$(tmp)/etc/squidtaild/history $(tmp)/etc/squidtaild/violators
(for i in
perl_modules/ConfigReader-Simple-0.5/blib/lib/ConfigReader/*.pm; do echo
ConfigReader::`basename $$i .pm` ; pod2text $$i | perl -ne '$$/=;
s/^DESCRIPTION// print'; done)
$(tmp)/usr/share/doc/squidtaild/overview.txt
dh_compress
diff -u squidtaild-2.1a6/debian/changelog squidtaild-2.1a6/debian/changelog
--- squidtaild-2.1a6/debian/changelog
+++ squidtaild-2.1a6/debian/changelog
@@ -1,3 +1,10 @@
+squidtaild (2.1a6-5.1) unstable; urgency=low
+
+ * Non-maintainer upload.
+ * debian/rules: fixed bashisms. (Closes: #459133)
+
+ -- Miguel Angel Ruiz Manzano [EMAIL PROTECTED] Mon, 21 Jan 2008 13:59:12
-0300
+
squidtaild (2.1a6-5) unstable; urgency=low
* Squidtaild start/stop script error (Closes: #336087).
signature.asc
Description: OpenPGP digital signature
Bug#462095: Debian watch file doesn't work
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Package: picard Severity: normal Tags: patch The last upload should fix the watch file problem, but it didn't: [EMAIL PROTECTED]:~/devel/picard/picard-0.9.0$ uscan --verbose --report - -- Scanning for watchfiles in . - -- Found watchfile in ./debian - -- In debian/watch, processing watchfile line: ftp://ftp.musicbrainz.org/pub/musicbrainz/picard/picard-([0-9\.]+).tar.gz uscan warning: In debian/watch no matching files for watch line ftp://ftp.musicbrainz.org/pub/musicbrainz/picard/picard-([0-9\.]+).tar.gz - -- Scan finished I'll send a patch that solves the problem: [EMAIL PROTECTED]:~/devel/picard/picard-0.9.0$ uscan --verbose --report - -- Scanning for watchfiles in . - -- Found watchfile in ./debian - -- In debian/watch, processing watchfile line: http://ftp.musicbrainz.org/pub/musicbrainz/picard/picard-([\d\.]*).tar.gz debian uupdate - -- Found the following matching hrefs: picard-0.7.0.tar.gz picard-0.7.1.tar.gz picard-0.7.2.tar.gz picard-0.9.0.tar.gz Newest version on remote site is 0.9.0, local version is 0.9.0 = Package is up to date - -- Scan finished Thanks in advance! - --- System information. --- Architecture: i386 Kernel: Linux 2.6.22-3-686 Debian Release: lenny/sid 500 testing security.debian.org 500 testing debian.ubiobio.cl - --- Package information. --- Depends (Version) | Installed ===-+-=== | - -- Miguel Angel Ruiz Manzanohttp://vulcano.mine.nu Computer Science Student - PUCV - Chile -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHlfWMdoYiJQ0/2KkRAsVEAKCAYdwSKWOTaYM4/XpQAEj6t93UJACgwJCJ p8tgjLmqDYkD3l7++sHS9sQ= =bnAX -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#462095: My patch
Hi, I'm attaching the patch that solves the problem. Cheers! -- Miguel Angel Ruiz Manzanohttp://vulcano.mine.nu Computer Science Student - PUCV - Chile diff -u picard-0.9.0/debian/changelog picard-0.9.0/debian/changelog --- picard-0.9.0/debian/changelog +++ picard-0.9.0/debian/changelog @@ -1,3 +1,11 @@ +picard (0.9.0-1.1) unstable; urgency=low + + * Non-maintainer upload. + * debian/watch: ++ Updated download page. (Closes: #462095) + + -- Miguel Angel Ruiz Manzano [EMAIL PROTECTED] Tue, 22 Jan 2008 10:56:30 -0300 + picard (0.9.0-1) unstable; urgency=low * Initial upload to debian unstable. diff -u picard-0.9.0/debian/watch picard-0.9.0/debian/watch --- picard-0.9.0/debian/watch +++ picard-0.9.0/debian/watch @@ -2 +2 @@ -ftp://ftp.musicbrainz.org/pub/musicbrainz/picard/picard-([0-9\.]+).tar.gz +http://ftp.musicbrainz.org/pub/musicbrainz/picard/picard-([\d\.]*).tar.gz debian uupdate signature.asc Description: OpenPGP digital signature
Bug#462103: Typo in keepass.desktop
Package: keepassx Severity: normal Tags: patch On keepass.desktop, the GenericName and Comment fields include Plateform and it should be Platform. I'm sending a patch that solves the problem. Cheers! --- System information. --- Architecture: i386 Kernel: Linux 2.6.22-3-686 Debian Release: lenny/sid 500 testing security.debian.org 500 testing debian.ubiobio.cl --- Package information. --- Depends (Version) | Installed ===-+-=== | -- Miguel Angel Ruiz Manzanohttp://vulcano.mine.nu Computer Science Student - PUCV - Chile diff -Nru keepassx-0.2.2/debian/keepass.desktop keepassx-0.2.2/debian/keepass.desktop --- keepassx-0.2.2/debian/keepass.desktop 2007-10-23 13:14:28.0 -0300 +++ keepassx-0.2.2/debian/keepass.desktop 2007-10-23 13:14:28.0 -0300 @@ -1,12 +1,12 @@ [Desktop Entry] Encoding=UTF-8 Name=KeePassX -GenericName=Cross Plateform Password Manager +GenericName=Cross Platform Password Manager GenericName[fr]=Gestionnaire de mot de passe GenericName[de]=Passwortverwaltung Exec=keepass Icon=keepass.xpm -Comment=Cross Plateform Password Manager +Comment=Cross Platform Password Manager Comment[fr]=Gestionnaire de mot de passe Comment[de]=Passwortverwaltung Terminal=false signature.asc Description: OpenPGP digital signature
Bug#459122: A possible fix (debdiff attached)
Lucas,
I'm attaching a new patch.
Thanks!
--
Miguel Angel Ruiz Manzanohttp://vulcano.mine.nu
Computer Science Student - PUCV - Chile
diff -u quagga-0.99.9/debian/rules quagga-0.99.9/debian/rules
--- quagga-0.99.9/debian/rules
+++ quagga-0.99.9/debian/rules
@@ -30,7 +30,8 @@
fi
# Update config.*
- cp /usr/share/misc/config.{guess,sub} .
+ cp /usr/share/misc/config.guess .
+ cp /usr/share/misc/config.sub .
# according to redhad/quagga.spec as of 2003-08-18
./configure \
@@ -100,7 +101,7 @@
-$(MAKE) distclean
@echo BEGIN CRUFT
- @rm -vf */Makefile doc/quagga.{fns,kys,tmp,pdf,info-*} doc/quagga.info
+ @rm -vf */Makefile doc/quagga.fns doc/quagga.info doc/quagga.kys
doc/quagga.tmp doc/quagga.pdf doc/quagga.info-*
@rm -vf lib/version.c doc/stamp-vti
@rm -vf vtysh/vtysh_cmd.c
@rm -vf doc/fig*.pdf
diff -u quagga-0.99.9/debian/changelog quagga-0.99.9/debian/changelog
--- quagga-0.99.9/debian/changelog
+++ quagga-0.99.9/debian/changelog
@@ -1,3 +1,10 @@
+quagga (0.99.9-2.1) unstable; urgency=low
+
+ * Non-maintainer upload.
+ * debian/rules: fixed bashisms. (Closes: #459122)
+
+ -- Miguel Angel Ruiz Manzano [EMAIL PROTECTED] Tue, 22 Jan 2008 14:37:21
-0300
+
quagga (0.99.9-2) unstable; urgency=low
* Added CVE id for the security bug to the last changelog entry.
signature.asc
Description: OpenPGP digital signature
Bug#450028: metalog: debian/watch fails to report upstream's version
I'm attaching a solution to fix the problem. Cheers! -- Miguel Angel Ruiz Manzanohttp://vulcano.mine.nu Computer Science Student - PUCV - Chile diff -u metalog-0.7.0/debian/watch metalog-0.7.0/debian/watch --- metalog-0.7.0/debian/watch +++ metalog-0.7.0/debian/watch @@ -1,2 +1,3 @@ -version=2 -http://osdn.dl.sourceforge.net/sourceforge/metalog/metalog-([0-9.]+)\.tar\.gz debian uupdate +version=3 + +http://sf.net/metalog/metalog-([\d\.]*)\.tar\.gz debian uupdate signature.asc Description: OpenPGP digital signature
Bug#459113: A possible fix (debdiff attached)
Package: opensrs-client
Severity: normal
Tags: patch
Hi,
I'm sending a patch to fix the problem.
Thanks in advance!
--
Miguel Angel Ruiz Manzanohttp://vulcano.mine.nu
Computer Science Student - PUCV - Chile
diff -u opensrs-client-2.9.5/debian/changelog
opensrs-client-2.9.5/debian/changelog
--- opensrs-client-2.9.5/debian/changelog
+++ opensrs-client-2.9.5/debian/changelog
@@ -1,3 +1,10 @@
+opensrs-client (2.9.5-1.1) unstable; urgency=low
+
+ * Non-maintainer upload.
+ * debian/rules: fixed bashisms. (Closes: #459113)
+
+ -- Miguel Angel Ruiz Manzano [EMAIL PROTECTED] Thu, 24 Jan 2008 17:43:44
-0300
+
opensrs-client (2.9.5-1) unstable; urgency=low
* New upstream release.
diff -u opensrs-client-2.9.5/debian/rules opensrs-client-2.9.5/debian/rules
--- opensrs-client-2.9.5/debian/rules
+++ opensrs-client-2.9.5/debian/rules
@@ -67,7 +67,9 @@
cp lib/XML_Codec.pm $(b)/usr/share/perl5
cp -r lib/Core/* $(b)/usr/share/perl5/Core
cp -r lib/OpenSRS/* $(b)/usr/share/perl5/OpenSRS
- cp lib/{CHARLINT,NAMEPREP,RACE}.pm $(b)/usr/share/perl5
+ cp lib/CHARLINT.pm $(b)/usr/share/perl5
+ cp lib/NAMEPREP.pm $(b)/usr/share/perl5
+ cp lib/RACE.pm $(b)/usr/share/perl5
cp -r lib/RACE $(b)/usr/share/opensrs/RACE/
touch install-stamp
signature.asc
Description: OpenPGP digital signature
Bug#293813: gazpacho: Commentary about architecture
Package: gazpacho Version: 0.4.0-1 Followup-For: Bug #293813 Also in i386 architecture, Gazpacho won't start. When I execute it, the following lines appear: GParamString 'icon-name' ** ERROR **: file ../../gobject/pygparamspec.c: line 155 (pyg_param_spec_getattr ): assertion failed: (pyclass != NULL) aborting... Aborted -- System Information: Debian Release: 3.1 APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.8-2-386 Locale: LANG=es_CL, LC_CTYPE=es_CL (charmap=ISO-8859-1) Versions of packages gazpacho depends on: ii python2.3.4-6An interactive high-level object-o ii python-gtk2 2.4.1-2Python bindings for the GTK+ widge -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#291204: ITP: graveman -- gtk graphical cd burning application
Package: wnpp Severity: wishlist * Package name: graveman Version : 0.3.0 Upstream Author : Sylvain cresto [EMAIL PROTECTED] * URL : http://scresto.site.voila.fr/gravemanuk.html * License : GPL Description : gtk graphical cd burning application Graphical tool to burn audio cd. * Frontend for cdrecord , mkisofs, readcd and sox. You can: * Burn audio cd from wav, ogg or mp3. * Duplicate cd audio or cd data. * Create iso images from data cd. * Burn cd data from iso image. * Format cd rewritable. * Burn data cd with files and directories that you choose. * Use drag and drop or integrated file dialog. -- System Information: Debian Release: 3.1 APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.4.27-1-386 aocale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.UTF-8 (charmap=UTF-8) (Include the long descrddiption here.) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#418514: Status of RFP
Dererk wrote: Hi there. Hi Dererk Which is the current status of this ITP? I'm packaging qbittorrent and I'll have a candidate package in two weeks. Greeting, Cheers! -- Miguel Angel Ruiz Manzanohttp://vulcano.mine.nu Computer Science Student - PUCV - Chile signature.asc Description: OpenPGP digital signature
Bug#429035: ITP: libfile-dirwalk-perl -- Perl module to walk through a directory tree and run own code
Package: wnpp Version: 0.3 Severity: wishlist File::DirWalk is a Perl module to walk through a directory tree and run own functions on directories, files and symlinks. -- Miguel Angel Ruiz Manzanohttp://vulcano.mine.nu Computer Science Student - PUCV - Chile Debian Maintainer PGP key 1024D/0D3FD8A9 2005-06-03 signature.asc Description: OpenPGP digital signature
Bug#481558: Error during the build process of ceferino
Gonéri Le Bouder wrote: On Fri, May 16, 2008 at 08:51:29PM -0400, Miguel Angel Ruiz Manzano wrote: Package: ceferino Version: 10.97.8-2 ^ Can you please try 0.97.8-3. Góneri, The correct version was 0.97.8-2. Sorry for the mistake. Anyhow, the problem was fixed with the update of some dependencies. Cheers, Cheers! -- Miguel Angel Ruiz Manzano http://mruiz.openminds.cl Ubuntu Member http://www.ubuntu-cl.org signature.asc Description: OpenPGP digital signature
Bug#480953: Lintian warning fix (debian-rules-ignores-make-clean-error)
Package: nss-updatedb Version: 10-1 During the build process of the version 10-1 I got this lintian warning: W: nss-updatedb source: debian-rules-ignores-make-clean-error line 47 To fix it, I prepared a patch. It would be great if you add it to the next revision of nss-updatedb. Thanks in advance, -- Miguel Angel Ruiz Manzano http://mruiz.openminds.cl Ubuntu Member http://www.ubuntu-cl.org --- debian/rules 2008-05-12 12:29:46.0 -0400 +++ debian/rules.new 2008-05-12 16:46:21.0 -0400 @@ -44,7 +44,8 @@ clean: unpatch dh_testroot rm -f build-stamp - -$(MAKE) distclean +[ ! -f Makefile ] || $(MAKE) distclean + ifneq $(wildcard /usr/share/misc/config.sub) cp -f /usr/share/misc/config.sub config.sub endif signature.asc Description: OpenPGP digital signature
Bug#481558: Error during the build process of ceferino
Package: ceferino Version: 10.97.8-2 During the build process (i386) of the version 0.97.8-2 I got this error: autopoint: *** infrastructure files for version 0.16.1 not found; this is autopoint from GNU gettext-tools 0.17 autopoint: *** Stop. make: *** [config.status] Error 1 dpkg-buildpackage: failure: debian/rules build gave error exit status 2 pbuilder: Failed autobuilding of package - Aborting with an error - unmounting dev/pts filesystem - unmounting proc filesystem - cleaning the build env - removing directory /var/cache/pbuilder/build//6022 and its subdirectories Also I'm attaching the pbuilder build log url [1] It would be great if the maintainer could take a look of this situation. Thanks in advance, [1] http://mruiz.openminds.cl/misc/ceferino_0.97.8-2.build -- Miguel Angel Ruiz Manzano http://mruiz.openminds.cl Ubuntu Member http://www.ubuntu-cl.org signature.asc Description: OpenPGP digital signature
Bug#480481: Patch to fix the desktop file
Hi, I'm attaching a patch to fix the issues with the desktop file. Cheers! -- Miguel Angel Ruiz Manzano http://mruiz.openminds.cl Ubuntu Member http://www.ubuntu-cl.org --- subtitleeditor.desktop.old 2008-05-17 03:05:14.0 -0400 +++ subtitleeditor.desktop 2008-05-17 03:06:09.0 -0400 @@ -1,11 +1,10 @@ [Desktop Entry] -Encoding=UTF-8 Name=Subtitle Editor GenericName=Subtitle Editor Comment=A subtitle editor based to GStreamer and Gtk+ Exec=subtitleeditor Terminal=false -Type=Audio -Icon=subtitleeditor-icon.png +Type=Application +Icon=subtitleeditor Categories=Audio;AudioVideo;AudioVideoEditing; StartupNotify=true signature.asc Description: OpenPGP digital signature
Bug#477946: [Cherokee] cherokee-admin usability issue
I think the javascript solution is better, because it let you submit a set of configuration changes atomically. Greetings, Miguel Angel 2008/4/28 Alvaro Lopez Ortega [EMAIL PROTECTED]: Hi Gunnar, It is a usability issue, indeed. I can think of a couple ways for fixing it: The first one would be to remove the Apply button from the side bar and force the local submit buttons to punch the configuration into the server. The second choice would be to add some Javascript code to warn the user if he tries to leave a modified page without submitting the changes. Since this is the most popular behavior I guess it is simply a better approach. Help from skilled web developer would be greatly appreciated here.. :-) On 28 Apr 2008, at 20:11, Gunnar Wolf wrote: severity 477946 minor thanks Hi, I am copying this message over to the Cherokee upstream mailing list, as I think they might be interested in actually solving the bug. People, please look over at http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=477946 for the actual bug report. I think the bug is rather a usability issue (otherwise, it is an unreproducible bug :) as cherokee-admin _does_ work for me). The thing is, for most screens at least, clicking on 'submit' will only modify cherokee-admin's in-memory representation of the configuration - It won't even cause the server to change its behaviour. Only when you click on 'Apply', on the left panel, are the changes saved and the server status gets changed (AFAICT, it is basically restarted). So, what do I propose, dear upstream community? Maybe it would be good to add some checks, i.e. by Javascript, to remind the user to apply the changes if he navigates away from the page without saving his work? Greetings, -- Gunnar Wolf - [EMAIL PROTECTED] - (+52-55)5623-0154 / 1451-2244 PGP key 1024D/8BB527AF 2001-10-23 Fingerprint: 0C79 D2D1 2C4E 9CE4 5973 F800 D80E F35A 8BB5 27AF ___ Cherokee mailing list [EMAIL PROTECTED] http://cherokee-project.com/cgi-bin/mailman/listinfo/cherokee -- Greetings, alo. http://www.alobbs.com/ ___ Cherokee mailing list [EMAIL PROTECTED] http://cherokee-project.com/cgi-bin/mailman/listinfo/cherokee
Bug#488599: o: xmailbox -- A version of xbiff with animation and sound effects
Package: wnpp Due to lack of time and interest I want to orphan xmailbox. Cheers! -- Miguel Angel Ruiz Manzanohttp://mruiz.openminds.cl Computer Science Student - PUCV - Chile -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#488601: O: hindent -- Reformats HTML code
Package: wnpp Due to lack of time and interest I want to orphan hindent. Cheers! -- Miguel Angel Ruiz Manzanohttp://mruiz.openminds.cl Computer Science Student - PUCV - Chile -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#488603: O: cfi -- Copyright does not exist, book about hacker culture
Package: wnpp Due to lack of time and interest I want to orphan cfi. Cheers! -- Miguel Angel Ruiz Manzanohttp://mruiz.openminds.cl Computer Science Student - PUCV - Chile -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#385063: python-gtk2: inconsistent use of tabs and spaces in indentation in pygtk.py and __init__.py
Package: python-gtk2 Version: 2.8.6-5 Severity: normal inconsistent use of tabs and spaces in indentation in files: /usr/share/python-gtk-2.0/pygtk.py /usr/share/python-support/python-gtk2/gtk-2.0/gtk/__init__.py -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.17-1-686 Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) (ignored: LC_ALL set to [EMAIL PROTECTED]) Versions of packages python-gtk2 depends on: ii libatk1.0-0 1.12.1-1The ATK accessibility toolkit ii libc62.3.6-15GNU C Library: Shared libraries ii libcairo21.2.2-1 The Cairo 2D vector graphics libra ii libfontconfig1 2.3.2-7 generic font configuration library ii libglib2.0-0 2.10.3-3The GLib library of C routines ii libgtk2.0-0 2.8.18-1The GTK+ graphical user interface ii libpango1.0-01.12.3-1+b1 Layout and rendering of internatio ii libx11-6 2:1.0.0-8 X11 client-side library ii libxcursor1 1.1.5.2-5 X cursor management library ii libxext6 1:1.0.0-4 X11 miscellaneous extension librar ii libxfixes3 1:3.0.1.2-4 X11 miscellaneous 'fixes' extensio ii libxi6 1:1.0.0-5 X11 Input extension library ii libxinerama1 1:1.0.1-4 X11 Xinerama extension library ii libxrandr2 2:1.1.0.2-4 X11 RandR extension library ii libxrender1 1:0.9.0.2-4 X Rendering Extension client libra ii python 2.3.5-11An interactive high-level object-o ii python-cairo 1.2.0-1 Python bindings for the Cairo vect ii python-numeric 24.2-5 Numerical (matrix-oriented) Mathem ii python-support 0.3.8 automated rebuilding support for p python-gtk2 recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#513142: ucf/dbconfig warning when package is installed
Hi Michael, Here is the version I use (I think is the lastest one): # dpkg -l | grep dbconfig ii dbconfig-common 1.8.40 common framework for packaging database applications Thanks for your quick reply. Today, I've upgrade the rest of the packages you uploaded yesterday (zabbix-agent zabbix-server-mysql) with same result: Configuring zabbix-agent (1:1.6.2-2) ... Starting Zabbix agent: zabbix_agentd Configurando zabbix-server-mysql (1:1.6.2-2) ... dbconfig-common: writing config to /etc/dbconfig-common/zabbix-server-mysql.conf *** WARNING: ucf was run from a maintainer script that uses debconf, but the script did not pass --debconf-ok to ucf. The maintainer script should be fixed to not stop debconf before calling ucf, and pass it this parameter. For now, ucf will revert to using old-style, non-debconf prompting. Ugh! Please inform the package maintainer about this problem. dbconfig-common: flushing administrative password Starting Zabbix server: zabbix_server Let me know if you need more information. Miguel. On Tue, Jan 27, 2009 at 9:40 AM, Michael Ablassmeier a...@grinser.de wrote: tags 513142 + unreproducible thanks hi Miguel, On Mon, Jan 26, 2009 at 09:34:26PM +0100, Miguel A. Rojas wrote: Configuring zabbix-frontend-php (1:1.6.2-2) ... dbconfig-common: writing config to /etc/dbconfig-common/zabbix-frontend-php.conf *** WARNING: ucf was run from a maintainer script that uses debconf, but the script did not pass --debconf-ok to ucf. The maintainer script should be fixed to not stop debconf before calling ucf, and pass it this parameter. For now, ucf will revert to using old-style, non-debconf prompting. Ugh! Please inform the package maintainer about this problem. I do not know if this happens in a fresh installation of 1.6.2-2 (without upgrade from previous versions) because I just upgraded from the previous version: 1.6.2-1 -- 1.6.2-2 and this error appears. i cant reproduce this error. Neither on a fresh installation, nor on upgrade from 1.6.2-1. The zabbix-frontend-php packages postinst isnt calling ucf anyways. Its only called in postrm on purge (which works nicely too). So i guess it may also be dbconfig-common which produces this warning. What dbconfig-common version are you using? bye, - michael
Bug#513012: Confirmed using old vars in zabbix.conf.php from zabbix developers
Hi, It is confirmed that variable parameters we are using are not the one zabbix are using right now. The reason why DB_* vars are still working is for compatibility reason for older versions. Here you have the link: http://www.zabbix.com/forum/showthread.php?t=11593 Michael, do you want me to report another bug about it or we can reopen this bug and fix it? I really appreciate your work. Very fast to be solved!! Regards.
Bug#535441: nmap fails on large range scan
Package:nmap
Version:4.53-1~bpo40+1
When I execute /usr/bin/nmap --open -n -p 515,631,9100 192.168.7.0/24
http://192.168.4.0/24 2/dev/null | grep ^Interesting | awk '{print
$4}' |cut -d: -f1,
It doesn't show some printers that exists on the net. Example:
ServerName:~# /usr/bin/nmap --open -n -p 515,631,9100 192.168.7.0/24
2/dev/null | grep ^Interesting | awk '{print $4}' |cut -d: -f1
ServerName:~#
We can see that exists a printer with ip 192.168.7.221:
ServerName:~# /usr/bin/nmap --open -n -p 515,631,9100 192.168.7.221
2/dev/null | grep ^Interesting | awk '{print $4}' |cut -d: -f1
192.168.7.221
ServerName:~# nmap 192.168.7.221
Starting Nmap 4.53 ( http://insecure.org ) at 2009-06-24 11:40 CEST
Interesting ports on
pc221-7.21700356.21.andared.cec.junta-andalucia.es (192.168.7.221):
Not shown: 1706 closed ports
PORT STATE SERVICE
21/tcp open ftp
23/tcp open telnet
80/tcp open http
280/tcp open http-mgmt
443/tcp open https
515/tcp open printer
631/tcp open ipp
9100/tcp open jetdirect
MAC Address: 00:0E:7F:36:41:C8 (Hewlett Packard)
If I install namp 4.11 version, i always find the printer with the command:
ServerName:~# /usr/bin/nmap -n -p 515,9100 192.168.7.0/24 | grep -B3
open | grep Interesting | cut -d -f4 | cut -d: -f1
192.168.7.221
ServerName:~# dpkg -l|grep nmap
ii nmap 4.11-1
The Network Mapper
Same problem we can find on 4.62 and 4.68 versions. The bug happens in
a random way, ocassionally it works!
-- System Information:
Debian Release: 4.0
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: 2.6.18-6-686
Locale: LANG=es_ES, LC_CTYPE=es_ES (charmap=UTF-8)
Versions of packages nmap depends on:
ii libc6 2.3.6.ds1-13etch9+b1
GNU C Library: Shared libraries
ii libgcc1 4.1.1-21
GCC support library
ii libpcap0.8 0.9.5-1
System interface for user-level packet capture
ii libpcre36.7+7.4-4
Perl 5 Compatible Regular Expression Library - runtime files
ii libssl0.9.8 0.9.8c-4etch5
SSL shared libraries
ii libstdc++6 4.1.1-21
The GNU Standard C++ Library v3
If you put --send-ip option on 4.53 version, It works correctly. Is
this a bug?, or anew funcion of nmap?
Bug#581525: rt2860: rt2860 doesn't connect to WPA2 networks
Package: linux-2.6 Version: 2.6.32-5 Severity: important File: rt2860 It seems it's not possible to connect to WPA2 wireless networks with the squeezix version of the rt2860 module. I've tested it with both network-manager and wicd. Both of them are unable to authenticate with the correct password. Both have NO problems to connect to WPA-PSK networks. Tested with a Buffalo WZR-HP-G300NH router. No problem connecting to that WPA2 network with other devices. The router encryption is set to WPA/WPA2-Mixed TKIP+AES, using a preshared key. Tested also after updating the rt2860 firmware-ralink to the Debian SID version (v0.24). No luck, either. -- Package-specific info: ** Version: Linux version 2.6.32-trunk-686 (Debian 2.6.32-5) (b...@decadent.org.uk) (gcc version 4.3.4 (Debian 4.3.4-6) ) #1 SMP Sun Jan 10 06:32:16 UTC 2010 ** Command line: root=/dev/sda2 ** Tainted: C (1024) * Module from drivers/staging has been loaded. ** Kernel log: [ 37.592358] domain 0: span 0-1 level SIBLING [ 37.592370] groups: 1 (cpu_power = 589) 0 (cpu_power = 589) [ 37.592399] domain 1: span 0-1 level MC [ 37.592412]groups: 0-1 (cpu_power = 1178) [ 38.332372] integrated sync not supported [ 38.485552] integrated sync not supported [ 38.628599] integrated sync not supported [ 102.927298] rt2860 :01:00.0: firmware: requesting rt2860.bin [ 103.092088] RX DESC f6392000 size = 2048 [ 103.092669] -- RTMPAllocTxRxRingMemory, Status=0 [ 103.096998] -- Error 2 opening /etc/Wireless/RT2860STA/RT2860STA.dat [ 103.097024] 1. Phy Mode = 0 [ 103.097031] 2. Phy Mode = 0 [ 103.118425] RTMPSetPhyMode: channel is out of range, use first channel=1 [ 103.124896] 3. Phy Mode = 0 [ 103.129534] MCS Set = 00 00 00 00 00 [ 103.131161] RTMPInitialize, Status=0 [ 103.131236] 0x1300 = 00073200 [ 113.752162] wlan0: no IPv6 routers present [ 157.719928] ===rt_ioctl_giwscan. 4(4) BSS returned, data-length = 479 [ 194.623011] rt2860 :01:00.0: firmware: requesting rt2860.bin [ 194.634711] RX DESC f6392000 size = 2048 [ 194.635424] -- RTMPAllocTxRxRingMemory, Status=0 [ 194.639958] -- Error 2 opening /etc/Wireless/RT2860STA/RT2860STA.dat [ 194.639974] 1. Phy Mode = 0 [ 194.639981] 2. Phy Mode = 0 [ 194.668230] 3. Phy Mode = 0 [ 194.672891] MCS Set = 00 00 00 00 00 [ 194.674519] RTMPInitialize, Status=0 [ 194.674595] 0x1300 = 000a4260 [ 195.053307] ATL1E :03:00.0: irq 27 for MSI/MSI-X [ 195.053485] ATL1E :03:00.0: ATL1E: eth0 NIC Link is Up100 Mbps Full Duplex [ 195.054063] ADDRCONF(NETDEV_UP): eth0: link is not ready [ 195.054537] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready [ 195.142556] rt2860 :01:00.0: firmware: requesting rt2860.bin [ 195.158459] RX DESC f661d000 size = 2048 [ 195.159166] -- RTMPAllocTxRxRingMemory, Status=0 [ 195.167205] -- Error 2 opening /etc/Wireless/RT2860STA/RT2860STA.dat [ 195.167221] 1. Phy Mode = 0 [ 195.167229] 2. Phy Mode = 0 [ 195.195907] 3. Phy Mode = 0 [ 195.200554] MCS Set = 00 00 00 00 00 [ 195.202229] RTMPInitialize, Status=0 [ 195.202306] 0x1300 = 000a4260 [ 197.569091] ==rt_ioctl_siwfreq::SIOCSIWFREQ[cmd=0x8b04] (Channel=1) [ 197.648862] ===rt_ioctl_giwscan. 1(1) BSS returned, data-length = 170 [ 197.649496] ==rt_ioctl_siwfreq::SIOCSIWFREQ[cmd=0x8b04] (Channel=1) [ 205.812139] eth0: no IPv6 routers present [ 205.980160] wlan0: no IPv6 routers present [ 207.662726] ===rt_ioctl_giwscan. 3(3) BSS returned, data-length = 376 [ 207.663032] ==rt_ioctl_siwfreq::SIOCSIWFREQ[cmd=0x8b04] (Channel=1) [ 217.670142] ===rt_ioctl_giwscan. 3(3) BSS returned, data-length = 376 [ 217.670444] ==rt_ioctl_siwfreq::SIOCSIWFREQ[cmd=0x8b04] (Channel=1) [ 227.682863] ===rt_ioctl_giwscan. 4(4) BSS returned, data-length = 479 [ 227.683174] ==rt_ioctl_siwfreq::SIOCSIWFREQ[cmd=0x8b04] (Channel=1) [ 233.250889] rt2860 :01:00.0: firmware: requesting rt2860.bin [ 233.264040] RX DESC f63ad000 size = 2048 [ 233.264793] -- RTMPAllocTxRxRingMemory, Status=0 [ 233.268723] -- Error 2 opening /etc/Wireless/RT2860STA/RT2860STA.dat [ 233.268735] 1. Phy Mode = 0 [ 233.268740] 2. Phy Mode = 0 [ 233.296695] 3. Phy Mode = 0 [ 233.301337] MCS Set = 00 00 00 00 00 [ 233.302960] RTMPInitialize, Status=0 [ 233.303035] 0x1300 = 000a4260 [ 233.579715] ATL1E :03:00.0: irq 27 for MSI/MSI-X [ 233.579926] ATL1E :03:00.0: ATL1E: eth0 NIC Link is Up100 Mbps Full Duplex [ 233.580565] ADDRCONF(NETDEV_UP): eth0: link is not ready [ 233.581217] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready [ 243.988150] eth0: no IPv6 routers present [ 266.659913] rt2860 :01:00.0: firmware: requesting rt2860.bin [ 266.672411] RX DESC f6333000 size = 2048 [ 266.672991] -- RTMPAllocTxRxRingMemory, Status=0 [ 266.677377] -- Error 2 opening /etc/Wireless/RT2860STA/RT2860STA.dat [ 266.677389] 1. Phy Mode = 0 [ 266.677395] 2. Phy Mode = 0 [ 266.705257] 3. Phy Mode = 0 [ 266.709891] MCS Set = 00 00 00 00 00 [ 266.711516]
Bug#572655: libopenipmi0 depends on non-existing package libglib1.2ldbl
Package: libopenipmi0
Version: 2.0.16-1.1
Severity: grave
# aptitude install libopenipmi0
Reading package lists... Done
Building dependency tree
Reading state information... Done
Reading extended state information... Done
Initializing package states... Done
Reading task descriptions... Done
The following NEW packages will be installed:
libopenipmi0{b}
0 packages upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 579kB of archives. After unpacking 1,466kB will be used.
The following packages have unmet dependencies:
libopenipmi0: Depends: libglib1.2ldbl (= 1.2.10-18) which is a virtual
package.
The following actions will resolve these dependencies:
Keep the following packages at their current version:
1) libopenipmi0 [Not Installed]
Tier: Cancel all user actions (2)
Accept this solution? [Y/n/q/?]
It seems that libglib1.2ldbl does not exist anymore in debian repositories
and source package could not be found.
Could you please fix it?
Thanks.
Bug#599379: Ignore this bug
Hi, This bug was created by mistake. I tried to send my NMU patch to the correct bug (582998), but something didn't work properly. Please ignore it. Thanks, -- Miguel Angel Ruiz Manzano Computer Engineer - PUCV - Chile signature.asc Description: OpenPGP digital signature
Bug#582998: pidgin-sipe: diff for NMU version 1.9.0-1.1
Hi Adam, Do I need to upload the files again? Thanks! -- Miguel Angel Ruiz Manzano Computer Engineer - PUCV - Chile signature.asc Description: OpenPGP digital signature
Bug#642018: alsa-utils: Resampling 44.1 to 48 KHz generates distortion noises
Package: alsa-utils Version: 1.0.24.2-3 Severity: important Dear Maintainer, *** Please consider answering these questions, where appropiate *** * What led up to the situation? It seems the problem has been the update of alsa-utils from 1.0.24.2-1 to 1.0.24.2-3 * What exactly did you do (or not do) that was effective (or ineffective)? I can play 48000 Hz flac music without distortions, but 44100 Hz content generates distortion on the higher frequencies of sound. It didn't happed before the packge upgrade. Confirmed the same on this system (amd64) and on a Atom processor laptop (x86). * What was the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these lines *** -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.0.0-1-rt-amd64 (SMP w/4 CPU cores; PREEMPT) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/dash Versions of packages alsa-utils depends on: ii libasound2 1.0.24.1-4 ii libc6 2.13-21 ii libncursesw5 5.9-1 ii linux-sound-base 1.0.23+dfsg-4 ii lsb-base 3.2-28 ii module-init-tools 3.16-1 ii whiptail 0.52.11-2.1 Versions of packages alsa-utils recommends: ii alsa-base 1.0.23+dfsg-4 ii pciutils 1:3.1.7-12 alsa-utils suggests no packages. -- 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#693512: [Pkg-utopia-maintainers] Bug#693512: network-manager: Network manager does not remove default routes
Hi Michael, Thanks for the troubleshooting. I think we have several options here (as far as I see). We can also combined some of them: - Modify ifupdown to be aware of networkmanager installation (as you suggested) - Modify networkmanager to remove/modify/backup /e/n/i interfaces managed by it (at installation time only or automatically done after the interfaces is managed by networkmanager - this last one is even complex?) - Message in networkmanager at installation time if ifupdown is installed (also include this information in /usr/share/doc) - Modify networkmanager documentation ( http://wiki.debian.org/NetworkManager#Enabling_Interface_Management) to point out Michael suggestion to manually remove references in /e/n/i for interfaces managed by networkmanager (if not done automatically by previous options) What do you think? Regards On Sun, Nov 18, 2012 at 1:39 PM, Michael Biebl bi...@debian.org wrote: On 18.11.2012 13:29, Miguel A. Rojas wrote: # The primary network interface allow-hotplug eth0 iface eth0 inet static address 192.168.2.2 netmask 255.255.255.0 network 192.168.2.0 broadcast 192.168.2.255 gateway 192.168.2.1 # dns-* options are implemented by the resolvconf package, if installed dns-nameservers 85.62.229.131 85.62.229.132 --- As you may see, after networkmanager installation, /etc/network/interfaces was not modified (I do not know if this is the default behaviour). I managed to enable interface managed according to http://wiki.debian.org/NetworkManager#Enabling_Interface_Management. After doing that, networkmanager was able to manage the interface and I suppose it got the information from /etc/network/interfaces. Let me know if you need anything else from my side. I really do not know where this route is coming from. Perhaps I did something wrong in the procedure, but I just followed the standard manuals. So, the problem is basically this: You have eth0 configured in /etc/network/interfaces. This device is now configured *both* by ifupdown and NetworkManager if you set managed=true. So I actually do not recommend that as maintainer of network-manager (contrary to what the wiki says). So, if you want to manage eth0 with NetworkManager it is better to remove the (eth0) configuration from /etc/network/interfaces completely, so ifupdown does no longer touch it. Now, while NetworkManager does not enable a ethernet interface if there is no network link, ifupdown does not care. It simply runs ifup eth0 during boot. This is why your eth0 network device is brought up and you have this route entry. So, in summary, I don't think there is actually a bug in network-manager. It's just the way what happens if you configure your system to use managed=true. Andrew, do you have a better idea how to handle this situation? Could ifup/ifdown be changed to check if managed=true is set and not configure the device in this case? Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth?
Bug#651229: console-setup: ckbcomp not found when booting
Hi Anton, I see you point. I am not an expert on this but here are my thoughts: - If ckbcomp could not be called at boot time... why this is inside in /bin/setupcon (which is called at boot time)? Same idea for the other binaries you mentioned - How is the preliminary keymap precompiled in /etc/console-setup ? Which command should you execute? - Perhaps the warning should mention my 2nd point above and this will avoid this warning. What do you think? Regards
Bug#718778: RFP: doublecmd -- Dual panel file manager.
Package: wnpp Severity: wishlist * Package name: doublecmd Version : 0.5.6b Upstream Author : alexx2000 * URL : http://doublecmd.sourceforge.net * License : GPL, LGPL Programming Lang: FreePascal / Lazarus Description : Dual panel file manager. Double Commander is a cross platform open source file manager with two panels side by side. It is inspired by Total Commander and features some new ideas. Here are some key features of Double Commander: - Unicode support - All operations working in background - Multi-rename tool - Tabbed interface - Custom columns - Internal text editor (F4) with syntax hightlighting - Built in file viewer (F3) to view files of in hex, binary or text format - Archives are handled like subdirectories. You can easily copy files to and from archives. Supported archive types: ZIP, TAR GZ, TGZ, LZMA and also BZ2, RPM, CPIO, DEB, RAR. - Extended search function with full text search in any files - Configurable button bar to start external programs or internal menu commands - Total Commander WCX, WDX and WLX plug-ins support - File operations logging - And more... -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#730262: please, reactivate debian-laespi...@lists.debian.org
Hi I am very interested in the reactivation of the debian-laespi...@lists.debian.org list. The main purpose of this list will be to establish a communication channel for all the things involving the management of La Espiral magazine. Thank you very much. -- Usuario registrado de Debian GNU/Linux nº 416197 http://linuxcounter.net/user/416197.html -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#750549: ipvsadm: unable to load more than one rule
Package: ipvsadm Version: 1:1.26-1 Severity: important Dear Maintainer, I was working in a cluster with pacemker and corosync and lvs to do load balancing. The cluster has two nodes, and lvs needs two virtual servers (IPv4,IPv6) and four real servers (2 IPv4,2 IPv6). I tried inserting rules both using ldirectord and ipvsadm directly. They were unable to add more than one real server per AF. The expectation was that 2 real servers were included per AF. Please, see raw ipvsadm commands below: root@debian:~# ipvsadm -L -n IP Virtual Server version 1.2.1 (size=4096) Prot LocalAddress:Port Scheduler Flags - RemoteAddress:Port Forward Weight ActiveConn InActConn TCP 192.168.1.10:389 rr - 192.168.1.11:389Route 1 0 0 TCP [fc00:1::1]:389 rr - [fc00:1::2]:389 Route 1 0 0 root@debian:~# ipvsadm -A -t 192.168.1.10:389 -s rr Service already exists root@debian:~# ipvsadm --add-server --tcp-service 192.168.1.10:389 --real-server 192.168.1.11 Destination already exists root@debian:~# ipvsadm --add-server --tcp-service 192.168.1.10:389 --real-server 192.168.1.12 Destination already exists root@debian:~# ipvsadm -A -t [fc00:1::1]:389 -s rr Service already exists root@debian:~# ipvsadm --add-server --tcp-service [fc00:1::1]:389 --real-server [fc00:1::2]:80 Destination already exists root@debian:~# ipvsadm --add-server --tcp-service [fc00:1::1]:389 --real-server [fc00:1::3]:80 Destination already exists root@debian:~# ipvsadm -L -n IP Virtual Server version 1.2.1 (size=4096) Prot LocalAddress:Port Scheduler Flags - RemoteAddress:Port Forward Weight ActiveConn InActConn TCP 192.168.1.10:389 rr - 192.168.1.11:389Route 1 0 0 TCP [fc00:1::1]:389 rr - [fc00:1::2]:389 Route 1 0 0 -- System Information: Debian Release: 7.5 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 3.2.0-4-686-pae (SMP w/4 CPU cores) Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages ipvsadm depends on: ii debconf [debconf-2.0] 1.5.49 ii libc6 2.13-38+deb7u1 ii libnl1 1.1-7 ii libpopt0 1.16-7 ii lsb-base 4.1+Debian8+deb7u1 ipvsadm recommends no packages. Versions of packages ipvsadm suggests: pn heartbeat none pn keepalived none ii ldirectord 1:3.9.2-5+deb7u2 -- Configuration Files: /etc/default/ipvsadm changed: AUTO=false DAEMON=none -- debconf information: ipvsadm/kernel_does_not_support_ipvs: ipvsadm/daemon_multicast_interface: eth0 ipvsadm/auto_load_rules: false ipvsadm/daemon_method: none -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#763737: red5-server init script is frozen in system reboot or shutdown
Package: red5-server
Version: 0.9.1-4squeeze1
Severity: normal
When you execute a reboot or shutdown, the system is frozen because the
stop process in red5-server init script doesn't working. It's frozen when
is executing the getent command, in the next line of init script:
DAEMONUID=`getent passwd |grep ^$DAEMONUSER: | awk -F : '{print $3}'`
DAEMONGID=`getent passwd |grep ^$DAEMONUSER: | awk -F : '{print $4}'
However, if you execute this command in the system prompt, you have a
correct result:
# getent passwd |grep ^_red5: | awk -F : '{print $3}'
118
This line in the init script for check that red5 user exist is executed
always but it could be execute only in the start process. I have checked
that when I put this lines only in the start process, and it isn't in a
generic part of init script, the reboot or shutdown system is working
correctly and stop process of red5-server doesn't freeze.
Thank you
-- System Information:
Debian Release: 6.0.7
APT prefers oldstable
APT policy: (500, 'oldstable')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.32-5-amd64 (SMP w/8 CPU cores)
Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.UTF-8 (charmap=UTF-8) (ignored:
LC_ALL set to es_ES.UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages red5-server depends on:
ii adduser 3.112+nmu2 add and remove users and groups
ii default-jre-headles 1:1.6-40 Standard Java or Java
compatible R
ii libred5-java0.9.1-4squeeze1 remote API for Red5 flash
streamin
ii openjdk-6-jre-headl 6b31-1.13.3-1~deb6u1 OpenJDK Java runtime, using
Hotspo
ii sun-java6-jre [java 6.26-0squeeze1 Sun Java(TM) Runtime
Environment (
red5-server recommends no packages.
red5-server suggests no packages.
-- no debconf information
Bug#800938: Bug#799948: Plasma desktop is unable to start (black screen - panic)
Hi Luca, Thanks for the quick answer! Here you have both report you asked for. Hopefully it will help us to know where the issue is. Regards On Sun, Oct 18, 2015 at 9:43 PM, Luca Boccassi <luca.bocca...@gmail.com> wrote: > On Sun, 2015-10-18 at 20:16 +0200, Miguel Angel Rojas wrote: > > Hi all, > > > > > > Vladimir is right, same issue here. Indeed, It is weird to me not so > > many people is currently reporting on it, but it is affecting a lot of > > programs. Something happens when upgrading to version 0.6.x (I agree > > at this point) > > > > > > plasma-desktop is also unable to start and panic (black screen).If you > > update-alternative glx fall back to mesa, the desktop runs just fine > > (of course, without the nvidia drivers) > > > > > > I though it was solved by bug 799948 (ssdm panic too), but again, it > > is not. At least you can "adduser sddm video" and make ssdm-greater > > works as a workaround, but plasma-desktop panics still panics after > > you try to log on. > > > > > > > > It is very easy to check it. Just install a fresh installation of KDE > > and nvidia drivers and you will see a beautiful black screen. Let me > > know if you need additional information but it is quite easy to > > reproduce > > Hi, > > Could you please attach the output of: > > reportbug --template glx-alternative-nvidia > reportbug --template nvidia-driver > > Kind regards, > Luca Boccassi > > -- Package-specific info: Diversions: diversion of /usr/lib/arm-linux-gnueabihf/libGL.so to /usr/lib/mesa-diverted/arm-linux-gnueabihf/libGL.so by glx-diversions diversion of /usr/lib/arm-linux-gnueabihf/libGL.so.1 to /usr/lib/mesa-diverted/arm-linux-gnueabihf/libGL.so.1 by glx-diversions diversion of /usr/lib/arm-linux-gnueabihf/libGL.so.1.2 to /usr/lib/mesa-diverted/arm-linux-gnueabihf/libGL.so.1.2 by glx-diversions diversion of /usr/lib/arm-linux-gnueabihf/libGL.so.1.2.0 to /usr/lib/mesa-diverted/arm-linux-gnueabihf/libGL.so.1.2.0 by glx-diversions diversion of /usr/lib/arm-linux-gnueabihf/libGLESv1_CM.so to /usr/lib/mesa-diverted/arm-linux-gnueabihf/libGLESv1_CM.so by glx-diversions diversion of /usr/lib/arm-linux-gnueabihf/libGLESv1_CM.so.1 to /usr/lib/mesa-diverted/arm-linux-gnueabihf/libGLESv1_CM.so.1 by glx-diversions diversion of /usr/lib/arm-linux-gnueabihf/libGLESv1_CM.so.1.1.0 to /usr/lib/mesa-diverted/arm-linux-gnueabihf/libGLESv1_CM.so.1.1.0 by glx-diversions diversion of /usr/lib/arm-linux-gnueabihf/libGLESv2.so to /usr/lib/mesa-diverted/arm-linux-gnueabihf/libGLESv2.so by glx-diversions diversion of /usr/lib/arm-linux-gnueabihf/libGLESv2.so.2 to /usr/lib/mesa-diverted/arm-linux-gnueabihf/libGLESv2.so.2 by glx-diversions diversion of /usr/lib/arm-linux-gnueabihf/libGLESv2.so.2.0.0 to /usr/lib/mesa-diverted/arm-linux-gnueabihf/libGLESv2.so.2.0.0 by glx-diversions diversion of /usr/lib/i386-linux-gnu/libGL.so to /usr/lib/mesa-diverted/i386-linux-gnu/libGL.so by glx-diversions diversion of /usr/lib/i386-linux-gnu/libGL.so.1 to /usr/lib/mesa-diverted/i386-linux-gnu/libGL.so.1 by glx-diversions diversion of /usr/lib/i386-linux-gnu/libGL.so.1.2 to /usr/lib/mesa-diverted/i386-linux-gnu/libGL.so.1.2 by glx-diversions diversion of /usr/lib/i386-linux-gnu/libGL.so.1.2.0 to /usr/lib/mesa-diverted/i386-linux-gnu/libGL.so.1.2.0 by glx-diversions diversion of /usr/lib/i386-linux-gnu/libGLESv1_CM.so to /usr/lib/mesa-diverted/i386-linux-gnu/libGLESv1_CM.so by glx-diversions diversion of /usr/lib/i386-linux-gnu/libGLESv1_CM.so.1 to /usr/lib/mesa-diverted/i386-linux-gnu/libGLESv1_CM.so.1 by glx-diversions diversion of /usr/lib/i386-linux-gnu/libGLESv1_CM.so.1.1.0 to /usr/lib/mesa-diverted/i386-linux-gnu/libGLESv1_CM.so.1.1.0 by glx-diversions diversion of /usr/lib/i386-linux-gnu/libGLESv2.so to /usr/lib/mesa-diverted/i386-linux-gnu/libGLESv2.so by glx-diversions diversion of /usr/lib/i386-linux-gnu/libGLESv2.so.2 to /usr/lib/mesa-diverted/i386-linux-gnu/libGLESv2.so.2 by glx-diversions diversion of /usr/lib/i386-linux-gnu/libGLESv2.so.2.0.0 to /usr/lib/mesa-diverted/i386-linux-gnu/libGLESv2.so.2.0.0 by glx-diversions diversion of /usr/lib/libGL.so to /usr/lib/mesa-diverted/libGL.so by glx-diversions diversion of /usr/lib/libGL.so.1 to /usr/lib/mesa-diverted/libGL.so.1 by glx-diversions diversion of /usr/lib/libGL.so.1.2 to /usr/lib/mesa-diverted/libGL.so.1.2 by glx-diversions diversion of /usr/lib/libGL.so.1.2.0 to /usr/lib/mesa-diverted/libGL.so.1.2.0 by glx-diversions diversion of /usr/lib/libGLESv1_CM.so to /usr/lib/mesa-diverted/libGLESv1_CM.so by glx-diversions diversion of /usr/lib/libGLESv1_CM.so.1 to /usr/lib/mesa-diverted/libGLESv1_CM.so.1 by glx-diversions diversion of /usr/lib/libGLESv1_CM.so.1.1.0 to /usr/lib/mesa-diverted/libGLESv1_CM.so.1.1.0 by glx-diversions diversion of /usr/l
Bug#799948: Plasma desktop is unable to start (black screen - panic)
Hi Luca, Here you have the report you asked about the plasmashell. I do not know if it could be related to a configuration issue, but again very easy to reproduce. Here you have 2 reports (same error in 2 consecutive log on sessions). These crashes are related to the plasmashell (I manually fixed the workaround by adding the sddm user to the video group) but if you remove it, sddm is the one who crashes. Hope it helps. Application: Plasma (plasmashell), signal: Aborted Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f972f7dc940 (LWP 1799))] Thread 7 (Thread 0x7f9718aeb700 (LWP 1801)): #0 0x7f9729f6252d in poll () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x7f972dfb2252 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #2 0x7f972dfb3ddf in xcb_wait_for_event () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #3 0x7f971ac4c2f9 in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libqxcb.so #4 0x7f972a64b25e in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f972976b0a4 in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #6 0x7f9729f6b06d in clone () from /lib/x86_64-linux-gnu/libc.so.6 Thread 6 (Thread 0x7f971220c700 (LWP 1806)): #0 0x7f972a881391 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #1 0x7f9726d2176d in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f9726d2210b in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f9726d222ec in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f972a881e4b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f972a8282ca in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f972a646374 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f972ce7b055 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #8 0x7f972a64b25e in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7f972976b0a4 in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #10 0x7f9729f6b06d in clone () from /lib/x86_64-linux-gnu/libc.so.6 Thread 5 (Thread 0x7f9709f46700 (LWP 1810)): #0 0x7f97297717fc in __lll_lock_wait () from /lib/x86_64-linux-gnu/libpthread.so.0 #1 0x7f972976d4d4 in _L_lock_986 () from /lib/x86_64-linux-gnu/libpthread.so.0 #2 0x7f972976d336 in pthread_mutex_lock () from /lib/x86_64-linux-gnu/libpthread.so.0 #3 0x7f972614de90 in ?? () from /usr/lib/x86_64-linux-gnu/libGL.so.1 #4 0x7f972615141e in ?? () from /usr/lib/x86_64-linux-gnu/libGL.so.1 #5 0x7f972615181b in ?? () from /usr/lib/x86_64-linux-gnu/libGL.so.1 #6 0x7f97226fafc0 in ?? () from /usr/lib/x86_64-linux-gnu/tls/libnvidia-tls.so.340.93 #7 0x7f9726d654d0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #8 0x7f9726d21cc4 in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #9 0x7f9726d22180 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #10 0x7f9726d222ec in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #11 0x7f972a881e4b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #12 0x7f972a8282ca in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #13 0x7f972a646374 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #14 0x7f972ce7b055 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #15 0x7f972a64b25e in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #16 0x7f972976b0a4 in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #17 0x7f9729f6b06d in clone () from /lib/x86_64-linux-gnu/libc.so.6 Thread 4 (Thread 0x7f97035c8700 (LWP 1814)): #0 0x7f9726d221c2 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f9726d222ec in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f972a881e4b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x7f972a8282ca in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f972a646374 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f972ce7b055 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #6 0x7f972a64b25e in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f972976b0a4 in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #8 0x7f9729f6b06d in clone () from /lib/x86_64-linux-gnu/libc.so.6 Thread 3 (Thread 0x7f9701d32700 (LWP 1815)): #0 0x7f972976f08f in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/x86_64-linux-gnu/libpthread.so.0 #1 0x7f972f222144 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #2 0x7f972f222189 in ?? () from
Bug#799948: Plasma desktop is unable to start (black screen - panic)
> > > I must first say that I am absolutely not familiar with KDE, the QT > environment and how it works. But the thread that raises the abort > doesn't look like it's in the GL libraries code: > > Maybe there's some context I'm missing. Forgive me for asking, but are > you sure this is due to the Nvidia driver packages or glx-alternatives? > > Hi Luca, But indeed, it is! I conducted the same experiments as Vladimir did with the same result. Something is wrong with the glx beyond 0.6.x (bad packaging, new API, new behavior? I don't know). I would recommend to reproduce as it is very easy to do it and you will see what we are talking about. Talking about Bug #799948, is there a reason why sddm user should be included in video? (because it seems to be the workaround) If so, someone should notify sddm guys that is somehow required due to new upstream requirement in nvidia glx packages. We don't have a clear explanation about it. Regards
Bug#799948: Plasma desktop is unable to start (black screen - panic)
Hi all, Vladimir is right, same issue here. Indeed, It is weird to me not so many people is currently reporting on it, but it is affecting a lot of programs. Something happens when upgrading to version 0.6.x (I agree at this point) plasma-desktop is also unable to start and panic (black screen).If you update-alternative glx fall back to mesa, the desktop runs just fine (of course, without the nvidia drivers) I though it was solved by bug 799948 (ssdm panic too), but again, it is not. At least you can "adduser sddm video" and make ssdm-greater works as a workaround, but plasma-desktop panics still panics after you try to log on. It is very easy to check it. Just install a fresh installation of KDE and nvidia drivers and you will see a beautiful black screen. Let me know if you need additional information but it is quite easy to reproduce Regards
Bug#909218: nvidia-xconfig: Files section missing ModulePath entries break GLX upon installing libgl1-nvidia-glx (required by Steam)
Please find logs attached. It appears only an empty or missing xorg.conf will cause the issue with xflock4. I tried before a file with only the Files section, and today I tried also with both sections (with-files) as well as without Files, and again and empty xorg.conf Thanks to you! Miguel On Sun, Sep 30, 2018 at 3:14 PM Andreas Beckmann wrote: > PS: can you repeat the xflock4 test with the working minimal xorg.conf, > too? Including the sleep+stop trick, to produce a well matching logfile? > > Thanks, > > Andreas > -- There are 10 types of geeks: 1s and 0s. X.Org X Server 1.20.1 X Protocol Version 11, Revision 0 Build Operating System: Linux 4.9.0-7-amd64 x86_64 Debian Current Operating System: Linux rapture 4.18.0-1-amd64 #1 SMP Debian 4.18.6-1 (2018-09-06) x86_64 Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.18.0-1-amd64 root=UUID=7e47da94-60c7-43de-aa1b-8f2e4bf73be8 ro nomodeset net.ifnames=0 biosdevname=0 Build Date: 17 August 2018 08:05:00PM xorg-server 2:1.20.1-1 (https://www.debian.org/support) Current version of pixman: 0.34.0 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: "/var/log/Xorg.0.log", Time: Mon Oct 1 22:54:18 2018 (==) Using config file: "/etc/X11/xorg.conf" (==) Using system config directory "/usr/share/X11/xorg.conf.d" (==) No Layout section. Using the first Screen section. (==) No screen section available. Using defaults. (**) |-->Screen "Default Screen Section" (0) (**) | |-->Monitor "" (==) No monitor specified for screen "Default Screen Section". Using a default monitor configuration. (==) Automatically adding devices (==) Automatically enabling devices (==) Automatically adding GPU devices (==) Max clients allowed: 256, resource mask: 0x1f (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist. Entry deleted from font path. (==) FontPath set to: /usr/share/fonts/X11/misc, /usr/share/fonts/X11/100dpi/:unscaled, /usr/share/fonts/X11/75dpi/:unscaled, /usr/share/fonts/X11/Type1, /usr/share/fonts/X11/100dpi, /usr/share/fonts/X11/75dpi, built-ins (**) ModulePath set to "/usr/lib/xorg/modules/linux,/usr/lib/xorg/modules" (II) The server relies on udev to provide the list of input devices. If no devices become available, reconfigure udev or disable AutoAddDevices. (II) Loader magic: 0x557345da3de0 (II) Module ABI versions: X.Org ANSI C Emulation: 0.4 X.Org Video Driver: 24.0 X.Org XInput driver : 24.1 X.Org Server Extension : 10.0 (++) using VT number 7 (II) systemd-logind: logind integration requires -keeptty and -keeptty was not provided, disabling logind integration (II) xfree86: Adding drm device (/dev/dri/card0) (--) PCI:*(9@0:0:0) 10de:1b81:1043:8598 rev 161, Mem @ 0xf600/16777216, 0xe000/268435456, 0xf000/33554432, I/O @ 0xd000/128, BIOS @ 0x/131072 (II) LoadModule: "glx" (II) Loading /usr/lib/xorg/modules/linux/libglx.so (II) Module glx: vendor="NVIDIA Corporation" compiled for 4.0.2, module version = 1.0.0 Module class: X.Org Server Extension (II) NVIDIA GLX Module 390.87 Tue Aug 21 16:10:56 PDT 2018 (II) Applying OutputClass "nvidia" to /dev/dri/card0 loading driver: nvidia (==) Matched nvidia as autoconfigured driver 0 (==) Matched nouveau as autoconfigured driver 1 (==) Matched nv as autoconfigured driver 2 (==) Matched modesetting as autoconfigured driver 3 (==) Matched fbdev as autoconfigured driver 4 (==) Matched vesa as autoconfigured driver 5 (==) Assigned the driver to the xf86ConfigLayout (II) LoadModule: "nvidia" (II) Loading /usr/lib/xorg/modules/drivers/nvidia_drv.so (II) Module nvidia: vendor="NVIDIA Corporation" compiled for 4.0.2, module version = 1.0.0 Module class: X.Org Video Driver (II) LoadModule: "nouveau" (II) Loading /usr/lib/xorg/modules/drivers/nouveau_drv.so (II) Module nouveau: vendor="X.Org Foundation" compiled for 1.20.0, module version = 1.0.15 Module class: X.Org Video Driver ABI class: X.Org Video Driver, version 24.0 (II) LoadModule: "nv" (WW) Warning, couldn't open module nv (EE) Failed to load module "nv" (module does not exist, 0) (II) LoadModule: "modesetting" (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so (II) Module modesetting: vendor="X.Org Foundation" compiled for 1.20.1, module version = 1.20.1 Module class: X.Org Video Driver ABI class: X.Org Video Driver, version 24.0 (II) LoadModule: "fbdev" (II) Loading /usr/lib/xorg/modules/drivers/fbdev_drv.so (II) Module fbdev: vendor="X.Org Foundation" compiled for 1.20.0, module version = 0.5.0 Module class: X.Org Video
Bug#934648: Acknowledgement (nvidia-kernel-dkms: Nvidia 418.74 does not build with kernel 5.2.0 (put_user_pages))
Hi all, It seems the problem is fixed with the new release (418.88) Thanks On Tue, Aug 13, 2019 at 12:42 AM Debian Bug Tracking System < ow...@bugs.debian.org> wrote: > Thank you for filing a new Bug report with Debian. > > You can follow progress on this Bug here: 934648: > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934648. > > This is an automatically generated reply to let you know your message > has been received. > > Your message is being forwarded to the package maintainers and other > interested parties for their attention; they will reply in due course. > > As you requested using X-Debbugs-CC, your message was also forwarded to > mianro...@gmail.com > (after having been given a Bug report number, if it did not have one). > > Your message has been sent to the package maintainer(s): > Debian NVIDIA Maintainers > > If you wish to submit further information on this problem, please > send it to 934...@bugs.debian.org. > > Please do not send mail to ow...@bugs.debian.org unless you wish > to report a problem with the Bug-tracking system. > > -- > 934648: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934648 > Debian Bug Tracking System > Contact ow...@bugs.debian.org with problems >
Bug#207434: Kuule arviointisi.
From: Recas Lopez, Miguel Angel Sent: Sunday, November 3, 2019 11:20 PM Subject: Kuule arviointisi. Työntekijöiden arvio sinulle. Työntekijän arviointi on jätetty sinulle. Suorita seuraavat vaiheet tarkistaaksesi ja vahvistaaksesi arvio: 1. Avaa selain osoitteeseen: https://appriasialforstaff.qwkcheckout.com/ 2. Syötä sivulle käyttäjänimesi, sähköpostiosoitteesi ja salasanasi. 3. lisätietoja lähetetään postilaatikkoosi kohtaan Valitse viimeisin päivämäärä avattavasta luetteloruudusta. 4. Etsi "Työntekijöiden kuittaus" -osa. 5. Vahvista arviointi valitsemalla yksi kolmesta (3) vaihtoehdosta työntekijän kuittauksen osassa. 6. Valitse Tallenna-painike. This e-mail (including attachments) is confidential and may be privileged. Please delete if obtained in error and email confirmation to the sender. Thank you for your cooperation.
Bug#1001991: parole: Parole 4.16.0 does not save playlist
Package: parole Version: 4.16.0-1 Severity: normal Tags: upstream X-Debbugs-Cc: newbadho...@gmail.com Dear Maintainer, parole media player does not save playlist. Steps to reproduce: Add vieos/streams/songs to playlist choose Media>save playlist Nothing is saved -- System Information: Debian Release: 11.2 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-10-amd64 (SMP w/4 CPU threads) Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.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 parole depends on: ii gstreamer1.0-alsa [gstreamer1.0-audiosink] 1.18.4-2 ii gstreamer1.0-libav 1.18.4-3 ii gstreamer1.0-plugins-bad [gstreamer1.0-audiosink] 1.18.4-3 ii gstreamer1.0-plugins-base 1.18.4-2 ii gstreamer1.0-plugins-good [gstreamer1.0-audiosink] 1.18.4-2 ii gstreamer1.0-x 1.18.4-2 ii libc6 2.31-13+deb11u2 ii libcairo2 1.16.0-5 ii libdbus-1-3 1.12.20-2 ii libdbus-glib-1-20.110-6 ii libgdk-pixbuf-2.0-0 2.42.2+dfsg-1 ii libglib2.0-02.66.8-1 ii libgstreamer-plugins-base1.0-0 1.18.4-2 ii libgstreamer1.0-0 1.18.4-2.1 ii libgtk-3-0 3.24.24-4 ii libnotify4 0.7.9-3 ii libtagc01.11.1+dfsg.1-3 ii libx11-62:1.7.2-1 ii libxfce4ui-2-0 4.16.0-1 ii libxfce4util7 4.16.0-1 ii libxfconf-0-3 4.16.0-2 parole recommends no packages. Versions of packages parole suggests: ii gstreamer1.0-plugins-bad 1.18.4-3 ii gstreamer1.0-plugins-ugly 1.18.4-2 -- no debconf information
Bug#1052012: plasma-workspace: sddm presents a white screen with no background nor buttons
Hi there, Downgrading the following packages: - sddm-themes-breeze - sddm-theme-debian-breeze to version 4:5.27.7-2 makes sddm fully usable again with no issues. It seems some changes have been made on version 4:5.27.8-1 that have broken sddm. I hope this helps. Regards
Bug#1040174: nvidia-driver: Can't upgrade to nvidia-driver-525.116.04-1 on debian unstable: build fails
Hi there, I can confirm the bug is there. Libraries are not found and NVIDIA driver fails to build. Regards
Bug#1037422: spamprobe crashing with emails containing an image attached
Package: spamprobe Version: 1.4d-16 Followup-For: Bug #1037422 After upgrading from bullseye to bookworm I've found spamprobe is not working with some emails. I've found that the emails spamprobe is having problems with is the ones with images attached (jpg or png). Whenever it processes one of those emails it fails with: "caught signal 11: quitting Aborted" -- System Information: Debian Release: 12.1 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 6.1.0-10-amd64 (SMP w/16 CPU threads; PREEMPT) 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 spamprobe depends on: ii debconf [debconf-2.0] 1.5.82 ii libc6 2.36-9+deb12u1 ii libdb5.3 5.3.28+dfsg2-1 ii libgcc-s1 12.2.0-14 ii libgif75.2.1-2.5 ii libjpeg62-turbo1:2.1.5-2 ii libpng16-161.6.39-2 ii libstdc++6 12.2.0-14 Versions of packages spamprobe recommends: ii procmail 3.22-27 spamprobe suggests no packages. -- debconf information: * spamprobe/db53_upgrade: spamprobe/db51_upgrade:
Bug#1062703: firmware-realtek: Direct firmware load for rtl_nic/rtl8125b-2.fw failed with error -2
Hi Diederik, My bad. Let me explain again. Taking into account the firmware errors: - Realtek messages are fixed now. There are no actions to be done here. - iwlwifi: If you are still working on a new version containing the -83 file, that should fix some warning messages but not all of them. There is another message (*firmware: failed to load iwl-debug-yoyo.bin (-2)*) that I think is related to bug #966218. This bug has been there for a while, so I don't know what's happening here. Nobody explains what's going on or why this file is not included in the firmware package. Thanks! On Fri, Feb 9, 2024 at 7:48 PM Diederik de Haas wrote: > Control: tag -1 moreinfo > > Hi, > > On Friday, 9 February 2024 19:35:01 CET Miguel A. Rojas wrote: > > A few days ago, I went to > > > https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git > > and update the missing loaded modules. > > > > Indeed, I noticed that I have another messages related to the iwlwifi > > module: "kernel: iwlwifi :00:14.3: firmware: failed to load > > iwlwifi-so-a0-hr-b0-83.ucode (-2)". > > The reason I asked for more dmesg lines is that it likely then tried > (f.e.) > -81, then -79 and then probably succeeded at some point. > The Debian kernel (unfortunately imo) 'promoted' warning/info messages to > errors, which make it appear more severe then they actually are. > > > I think the the root cause is that the current Debian packages firmware > > packages are 6 months old and they need to be updated accordingly. New > > Debian Linux kernel expects a specific version of the firmware or the > > name of the firmware has changed. > > I do think that the old package versions are a problem, so I have been > working > on Merge Requests for updating them. > Version 20230804 would make the -83 file available. > But the device using and older version should still work. If it doesn't > work > with an older version, but it does work with a newer, that's important > info. > > But I'm still a bit confused as this bug is about *realtek* firmware, not > iwlwifi? Can you answer the question I asked previously?
Bug#1062703: firmware-realtek: Direct firmware load for rtl_nic/rtl8125b-2.fw failed with error -2
Hi Diederik, > While 'annoying', this is expected behavior. It tries to load the newest (-83) Yes, this is the expected behavior from our Linux kernel. However, I agree with you and these messages are very annoying and should be removed. > It could be it wouldn't be shown if it had already found one of the earlier logged firmware files. Interesting theory! When the new version of the firmware packages is uploaded, we can check again if the "'iwl-debug-yoyo.bin" message disappears Why are you confused with the numbers? >Bit confused about that version number, but looks like success. And yes, wifi is working fine although I haven't properly done any performance test yet. Regards On Sun, Feb 11, 2024 at 4:15 PM Diederik de Haas wrote: > Hi Miguel, > > On Sunday, 11 February 2024 16:03:20 CET Miguel A. Rojas wrote: > > I forgot to include you the dmesg as promised: > > > > [2.235947] iwlwifi :00:14.3: enabling device ( -> 0002) > > [2.237778] iwlwifi :00:14.3: Detected crf-id 0x1300504, cnv-id > > 0x80401 wfpm id 0x8030 > > [2.237805] iwlwifi :00:14.3: PCI dev 7a70/0074, rev=0x430, > > rfid=0x10a100 > > [2.237845] iwlwifi :00:14.3: firmware: failed to load > > iwlwifi-so-a0-hr-b0-83.ucode (-2) > > [2.237867] iwlwifi :00:14.3: firmware: failed to load > > iwlwifi-so-a0-hr-b0-83.ucode (-2) > > ... more firmware load failures > > [2.238098] iwlwifi :00:14.3: Direct firmware load for > > iwlwifi-so-a0-hr-b0-73.ucode failed with error -2 > > [2.241012] iwlwifi :00:14.3: firmware: direct-loading firmware > > iwlwifi-so-a0-hr-b0-72.ucode > > While 'annoying', this is expected behavior. It tries to load the newest > (-83) > and when it can't find that, it tries an older one and ends up with '-72'. > > > [2.247819] iwlwifi :00:14.3: api flags index 2 larger than > > supported by driver > > [2.247832] iwlwifi :00:14.3: TLV_FW_FSEQ_VERSION: FSEQ Version: > > 0.0.2.36 > > [2.248049] iwlwifi :00:14.3: firmware: failed to load > > iwl-debug-yoyo.bin (-2) > <- > > [2.248067] iwlwifi :00:14.3: firmware: failed to load > > iwl-debug-yoyo.bin (-2) > <- > > This 'iwl-debug-yoyo.bin' is a familiar one, but this file is NOT > available in > the upstream linux-firmware repo. > It could be it wouldn't be shown if it had already found one of the > earlier > logged firmware files. > I might look into this particular issue at some later date. > > > [2.248078] iwlwifi :00:14.3: loaded firmware version > > 72.daa05125.0 so-a0-hr-b0-72.ucode op_mode iwlmvm > > Bit confused about that version number, but looks like success ... > > > [2.653952] iwlwifi :00:14.3: Detected Intel(R) Wi-Fi 6 AX201 > > 160MHz, REV=0x430 > > [2.769070] iwlwifi :00:14.3: WFPM_UMAC_PD_NOTIFICATION: 0x3f > > [2.769102] iwlwifi :00:14.3: WFPM_LMAC2_PD_NOTIFICATION: 0x1f > > [2.769110] iwlwifi :00:14.3: WFPM_AUTH_KEY_0: 0x90 > > [2.769118] iwlwifi :00:14.3: CNVI_SCU_SEQ_DATA_DW9: 0x10 > > [2.769154] iwlwifi :00:14.3: Detected RF HR B3, rfid=0x10a100 > > [2.834751] iwlwifi :00:14.3: base HW address: bc:09:1b:d3:e2:ee > > [2.849492] iwlwifi :00:14.3 wlp0s20f3: renamed from wlan0 > > [6.570171] iwlwifi :00:14.3: WFPM_UMAC_PD_NOTIFICATION: 0x3f > > [6.570263] iwlwifi :00:14.3: WFPM_LMAC2_PD_NOTIFICATION: 0x1f > > [6.570275] iwlwifi :00:14.3: WFPM_AUTH_KEY_0: 0x90 > > [6.570307] iwlwifi :00:14.3: CNVI_SCU_SEQ_DATA_DW9: 0x10 > > [6.644756] iwlwifi :00:14.3: Registered PHC clock: iwlwifi-PTP, > > with index: 0 > > [6.809353] iwlwifi :00:14.3: WFPM_UMAC_PD_NOTIFICATION: 0x3f > > [6.809386] iwlwifi :00:14.3: WFPM_LMAC2_PD_NOTIFICATION: 0x1f > > [6.809397] iwlwifi :00:14.3: WFPM_AUTH_KEY_0: 0x90 > > [6.809408] iwlwifi :00:14.3: CNVI_SCU_SEQ_DATA_DW9: 0x10 > > ... and from this it seems the device appears to be working properly? > > If that's indeed the case then this bug would essentially be a request for > a > new upstream version. > > Cheers, > Diederik
Bug#1065831: apt tries to uninstall kde & plasma (full-upgrade)
Hi Wesley, David, > You keep saying `apt upgrade' yet your command was `apt full-upgrade'. Yes, maybe it didn't express itself properly. After your suggestion about not using "apt full-upgrade" during this t64 migration, I followed your advice and used only "apt upgrade" for individual upgrades. I was referring to this comment you made below: > My advice to you is: don't expect full-upgrade to work until the transitioning > is done. You can do `apt upgrade' without too much hassle. If you feel like it > you can inspect individual upgrades possibilities via `apt list --upgradable' > and upgrade each package individually. Therefore, that's the advice I'm following right now. Now, If I type"apt upgrade" doesn't give me any option to update anything: # apt upgrade Reading package lists... Done Building dependency tree... Done Reading state information... Done Calculating upgrade... Done The following packages were automatically installed and are no longer required: linux-headers-6.6.15-amd64 linux-headers-6.6.15-common linux-image-6.6.15-amd64 linux-kbuild-6.6.15 Use 'apt autoremove' to remove them. The following packages have been kept back: gstreamer1.0-plugins-bad gstreamer1.0-plugins-good gstreamer1.0-plugins-ugly kaddressbook kmail knotes libgstreamer-plugins-bad1.0-0 libkf5akonadisearch-bin libkf5akonadisearch-plugins libkf5messagecomposer5abi1 libkf5messagecore5abi1 libkf5messagelist5abi1 libkf5messageviewer5abi1 libkf5mimetreeparser5abi1 libkf5pimcommonakonadi5abi1 libkf5templateparser5 libkf5webengineviewer5abi1 libkpimaddressbookimportexport5 libldb2 libopenconnect5 libqt5webengine5 ppp samba-libs 0 upgraded, 0 newly installed, 0 to remove and 23 not upgraded. But, in some situations, as you mentioned, individual package upgrades can work and remove some problems. So what I did was to try some "apt upgrade" on individual packages from that list. This time I try the ppp package: # apt upgrade ppp Reading package lists... Done Building dependency tree... Done Reading state information... Done Calculating upgrade... Done The following packages were automatically installed and are no longer required: linux-headers-6.6.15-amd64 linux-headers-6.6.15-common linux-image-6.6.15-amd64 linux-kbuild-6.6.15 Use 'apt autoremove' to remove them. The following packages will be REMOVED: <--- PACKAGE TO BE REMOVED libpcap0.8 The following NEW packages will be installed: libpcap0.8t64 The following packages have been kept back: gstreamer1.0-plugins-bad gstreamer1.0-plugins-good gstreamer1.0-plugins-ugly kaddressbook kmail knotes libgstreamer-plugins-bad1.0-0 libkf5akonadisearch-bin libkf5akonadisearch-plugins libkf5messagecomposer5abi1 libkf5messagecore5abi1 libkf5messagelist5abi1 libkf5messageviewer5abi1 libkf5mimetreeparser5abi1 libkf5pimcommonakonadi5abi1 libkf5templateparser5 libkf5webengineviewer5abi1 libkpimaddressbookimportexport5 libldb2 libopenconnect5 libqt5webengine5 samba-libs The following packages will be upgraded: ppp 1 upgraded, 1 newly installed, 1 to remove and 22 not upgraded. Need to get 511 kB of archives. After this operation, 15.4 kB disk space will be freed. , As you can see here, I'm typing "apt upgrade ppp" and it removes a package in this case: libpcap0.8 (sometimes more packages are removed). Which is good, because libpcap0.8 is replaced by libpcap0.8t64 (as expected in this t64 migration) but "apt upgrade ppp" is REMOVING a package (which contradicts the specification). @David: I will send you the file as you requested. Regards On Mon, Mar 11, 2024 at 5:44 PM Wesley Schwengle wrote: > > Hi Miguel, > > On Mon, Mar 11, 2024 at 05:09:47PM +0100, Miguel Angel Rojas wrote: > > > I do not know, at times I'm also wondering why it doesn't do it, but I > > didn't > > > take time to look at the code to understand what the resolver is doing. > > Also, > > > it was sort of expected. I think we can probably solve this is a more > > > controlled manner. With the current t64 transitioning in unstable it is > > > difficult to track down. Many updates so the situation now may differ > > from the > > > situation in an hour from now. > > > > Yes, it is confusing for me too. Without considering this t64 migration, > > “apt upgrade” should *NOT* remove any package (just upgrading a package > to > > a newer version or install new dependencies). But it is removing packages > > right now! i.e. again, with this t64 migration, it makes the old > libraries > > to be uninstalled and install the new *t64 version. > > > > Any thoughts why “apt upgrade” is removing packages even when > documentation > > says it shouldn’t? or is it a bug? > > You keep saying `apt upgrade' yet your command was `apt full-upgrade'. As > said > earlier, full-upgrade does indeed remove packages to be able to perform an > upgrade. I haven't seen `apt upgrade' do that. So I cannot comment on apt > doing > something wrong when it isn't :) > > Cheers, > Wesley >
Bug#1065831: apt tries to uninstall kde & plasma (full-upgrade)
> I see. It looks like `apt upgrade ' behaves as `apt install > '. Which (to me) is unexpected behaviour, as the man page is quite >clear on its behaviour (man 8 apt-get): Well, clearly it shouldn’t. To begin with, “apt install” should mark a package as manual installed while “apt upgrade” shouldn’t (my assumption). And you’re right that “apt install” can remove a package if needed to satisfy dependencies. On top of that, documentation clearly states that “apt upgrade” should not remove any package, but it does when you specify an individual package to upgrade. If this is not the expected behavior, maybe this is a bug (unless I am missing something here).
Bug#1065831: apt tries to uninstall kde & plasma (full-upgrade)
Control: retitle -1 apt upgrade : it removes packages when it shouldn't. The case you mentioned is a tricky one, yes: *apt upgrade foo+ bar-* (I really don't know how apt handles it internally but having this option is very useful. Of course, I wouldn't remove it). I think it makes a lot of sense for "apt upgrade" to allow packages as arguments. There should be a possibility to upgrade only a set of packages and it comes in handy in some situations (i.e.: t64 upgrade). "apt upgrade" also doesn't mark upgraded packages as manually installed (as expected). But "apt install" does mark them as manually installed (as expected too). Therefore, I see 2 options here: a) Change apt documentation to include the current behaviour. But if so, it should *NOT* remove any packages. b) Remove the possibility to specify packages to upgrade as arguments (which I don't really recommend for the reasons stated above). Anyway, I think some clarification is needed from the developers to shed some light on this. Regards On Tue, Mar 12, 2024 at 3:12 AM Wesley Schwengle wrote: > On Mon, Mar 11, 2024 at 11:32:24PM +0100, Miguel Angel Rojas wrote: > > > I see. It looks like `apt upgrade ' behaves as `apt install > > > '. Which (to me) is unexpected behaviour, as the man page is > > quite > > >clear on its behaviour (man 8 apt-get): > > > > Well, clearly it shouldn’t. To begin with, “apt install” should mark a > > package as manual installed while “apt upgrade” shouldn’t (my > assumption). > > And you’re right that “apt install” can remove a package if needed to > > satisfy dependencies. > > > > On top of that, documentation clearly states that “apt upgrade” should > not > > remove any package, but it does when you specify an individual package to > > upgrade. > > > > If this is not the expected behavior, maybe this is a bug (unless I am > > missing something here). > > I do not know what the bug here is, it could be one of these options: > > 1) apt-get/apt upgrade accepts packages to upgrade where the docs state it >doesn't. The behaviour needs to change to not accept packages. > > 2) apt-get/apt upgrade accepts packages and removes packages to satisfy > deps >where the docs state it doesn't. The behaviour need to change to not > remove >any packages. There is a small edge case where you can say: `apt > upgrade foo >bar-'. Technically, it shouldn't remove packages, yet you want and > instruct >it to remove bar. > > FWIW, aptitude does not remove packages where you call `aptitude > safe-upgrade > foo'. It does remove packages when you call `aptitude full-upgrade foo'. It > also removes bar when you run `aptitude safe-upgrade foo bar-'. > > I'll leave this for the maintainers to answer. > > Cheers, > Wesley > >
Bug#1065831: apt upgrade : it removes packages when it shouldn't.
Control: retitle -1 apt upgrade : it removes packages when it shouldn't.
Bug#1065831: apt tries to uninstall kde & plasma (full-upgrade)
Hi Wesley, >This problem isn't because of apt, the problem is that gdb-minimal/gdb > dependencies cannot be satified. A full-upgrade is the equivalent of a > dist-upgrade which will remove packages to resolve the dependencies. The > problem you are facing is the t64 transition[1][2] where not all packages are > transitioned. I haven't detected any "gdb | gdb-minimal dependencies that can't be satisfied at this point. Everything seems to be OK with those packages. > My advice to you is: don't expect full-upgrade to work until the transitioning > is done. You nail it here! I have managed to upgrade package by package but it is a tedious process until the whole transition is completed. But "apt upgrade" should not remove any packages according to its documentation (man apt) *"upgrade is used to install available upgrades of all packages currently installed on the system from the sources configured via sources.list(5). New packages will be installed if required to satisfy dependencies, but existing packages will never be removed. If an upgrade for apackage requires the remove of an installed package the upgrade for thispackage isn't performed."* Why is this t64 upgrade working then as it is removing deprecated packages for *t64 packages? > This seems to be an more of an actual issue where dependencies are declared but >apt doing something weird. But that is an issue on bookworm where we aren't >getting poluted results because of a transitioning. I'm glad you were able to replicate in bookworm (stable) it but I don't think (at least in this case) it is related to the t64 transition. Same errors on both distributions and I checked that gdb dependencies were satisfied in unstable (I don't have a system running stable). > I don't know either and that question should be redirected to the > plasma-workspace maintainer. good advice! I will. Appreciate your support. Thanks! On Sun, Mar 10, 2024 at 8:20 PM Wesley Schwengle wrote: > On Sun, Mar 10, 2024 at 02:13:34PM +0100, Miguel Angel wrote: > > > # apt full-upgrade > > Reading package lists... Done > > Building dependency tree... Done > > Reading state information... Done > > Calculating upgrade... Error! > > Some packages could not be installed. This may mean that you have > > requested an impossible situation or if you are using the unstable > > distribution that some required packages have not yet been created > > or been moved out of Incoming. > > The following information may help to resolve the situation: > > > > The following packages have unmet dependencies: > > plasma-workspace : Depends: gdb-minimal but it is not going to be > installed or > > gdb > > E: Error, pkgProblemResolver::Resolve generated breaks, this may be > caused by held packages. > > > > This problem isn't because of apt, the problem is that gdb-minimal/gdb > dependencies cannot be satified. A full-upgrade is the equivalent of a > dist-upgrade which will remove packages to resolve the dependencies. The > problem you are facing is the t64 transition[1][2] where not all packages > are > transitioned. > > My advice to you is: don't expect full-upgrade to work until the > transitioning > is done. You can do `apt upgrade' without too much hassle. If you feel > like it > you can inspect individual upgrades possibilities via `apt list > --upgradable' > and upgrade each package individually. That has worked well for me in the > past > week with aptitude, but it requires going through many offered solutions. > > > I've seen other users are experimenting the same issue: > > https://groups.google.com/g/linux.debian.user/c/7gpQImSH-Cs > > This seems to be an more of an actual issue where dependencies are > declared but > apt doing something weird. But that is an issue on bookworm where we aren't > getting poluted results because of a transitioning. It differs from yours > because your apt output says "gdb-minimal but it is not going to be > installed > or gdb" so apt sees the alternative, but cannot install it either. IMHO, > that should > be filed as a seperate bug against apt on bookworm. And if possible > checked on > testing as well. FWIW, I can reproduce it on bookwork with apt, apt-get and > aptitude, where the latter offers a solution to install gdb and not > deinstall > plasma-workspace. > > > I don't know why plasma-workspace depends on gdb > > I don't know either and that question should be redirected to the > plasma-workspace maintainer. > > Cheers, > Wesley > > [1] https://lists.debian.org/debian-devel-announce/2024/02/msg0.html > [2] > https://www.reddit.com/r/debian/comments/1b2ncdn/64bit_time_t_transition_in_progress_in_unstable/ > >
Bug#1065831: document package specifiers for `upgrade`
Hi there, > If "apt upgrade" is saying that it removes packages, that is a bug, yes. @david: it is not a bug, apparently. To put everything in a nutshell: - "apt upgrade" can remove packages - "apt upgrade" accepts specific packages to be upgraded Therefore, this behaviour is expected and documentation needs to be modified. In the meantime, while the documentation is modified, can some developer provide some explanation to the current "apt upgrade" behaviour? (*) Thanks (*) I'm a bit confused because I don't know which of the people involved in this bug are actually a developer of the apt package ;)
Bug#1065831: document package specifiers for `upgrade`
Hi all, >> (modifiers btw is not a good word. I guess it was never documented so far partly as this is a rather advanced feature and mainly because naming things is hard) yes, we brought it up in our conversation but I agree it was not directly related to the subject as it was an apt advanced option. But it was good because we were able to compare different situations (to spice things up). We even talked about "apt-get" and "aptitude" but I understand they are different commands and the purpose was not to compare behaviours among different tools. >> Well, does it really matter who is and who isn't? No, it doesn't as long as they have the right information ;) Of course, the more people involved in the issue, the better perspective we have on the problem. But it is important to know how apt is *currently* behaving to avoid misunderstanding and wrong assumptions (even from my side as well). We discovered that it is a documentation bug but my initial premise when I opened the bug was that the resolver wasn't working properly. With the right information, we usuallly get faster to the solution. Thank you all, guys! >> Nobody is born an APT developer, they are chosen based on their patch offerings! ;)
Bug#1065831: apt tries to uninstall kde & plasma (full-upgrade)
Hi Wesley, Good conversation here. Let me give you some comments from my side: > No, there is (or was) something going on with the dependencies of gdm-minimal > for sure. I think it is related to libdebuginfod1, which has a t64 variant. > This one has a dependency to libelf1 and libdw1. Now the libdebuginfod1t64 > depends on libelf1t64 and libdw1t64. These two replace libelf1 and libdw1, the > former having a relative high count of reverse dependencies. I didn’t catch this one (and I spent a fair amount of time trying to find out what was going on) ;) Thank you for spotting it! > I do not know, at times I'm also wondering why it doesn't do it, but I didn't > take time to look at the code to understand what the resolver is doing. Also, > it was sort of expected. I think we can probably solve this is a more > controlled manner. With the current t64 transitioning in unstable it is > difficult to track down. Many updates so the situation now may differ from the > situation in an hour from now. Yes, it is confusing for me too. Without considering this t64 migration, “apt upgrade” should *NOT* remove any package (just upgrading a package to a newer version or install new dependencies). But it is removing packages right now! i.e. again, with this t64 migration, it makes the old libraries to be uninstalled and install the new *t64 version. Any thoughts why “apt upgrade” is removing packages even when documentation says it shouldn’t? or is it a bug? > I disagree (or agree) to some extent. The gdb-minimal has been held back on my > system for a long time. I removed it after I saw it was a remnant of a KDE > experiment I did. The fact that I can install it now is a change from a couple > of days ago. The bug may be the same, but with how unstable it is now with > this big transition, it's wise to leave it where we are now and break it down > into a more controlled reproduction path, where we don't have so many moving > pieces. Yes, I fully agreed with that! Let’s wait until packages are fully settled down. I have a feeling that it is the same bug but there is no way to probe it with this transition going on. Regards On Mon, Mar 11, 2024 at 3:04 PM Wesley Schwengle wrote: > > Hello Miguel, > > On Mon, Mar 11, 2024 at 09:50:12AM +0100, Miguel Angel Rojas wrote: > > > >This problem isn't because of apt, the problem is that gdb-minimal/gdb > > > dependencies cannot be satified. A full-upgrade is the equivalent of a > > > dist-upgrade which will remove packages to resolve the dependencies. > The > > > problem you are facing is the t64 transition[1][2] where not all > packages > > are > > > transitioned. > > > > I haven't detected any "gdb | gdb-minimal dependencies that can't be > > satisfied at this point. Everything seems to be OK with those packages. > > No, there is (or was) something going on with the dependencies of > gdm-minimal > for sure. I think it is related to libdebuginfod1, which has a t64 variant. > This one has a dependency to libelf1 and libdw1. Now the libdebuginfod1t64 > depends on libelf1t64 and libdw1t64. These two replace libelf1 and libdw1, > the > former having a relative high count of reverse dependencies. > > > > My advice to you is: don't expect full-upgrade to work until the > > transitioning > > > is done. > > > > You nail it here! I have managed to upgrade package by package but it is > a > > tedious process until the whole transition is completed. > > Some of them yes, but often after doing one, you can use `apt upgrade' to > see if it resolved other problems (which in my case it does from time to > time). > > > But "apt upgrade" > > should not remove any packages according to its documentation (man apt) > > That is correct, but you were executing full-upgrade: > > > > On Sun, Mar 10, 2024 at 02:13:34PM +0100, Miguel Angel wrote: > > > > > > > # apt full-upgrade > > > > Reading package lists... Done > > > > Building dependency tree... Done > > > > Reading state information... Done > > > > Calculating upgrade... Error! > > > > Some packages could not be installed. This may mean that you have > > > > requested an impossible situation or if you are using the unstable > > > > distribution that some required packages have not yet been created > > > > or been moved out of Incoming. > > > > The following information may help to resolve the situation: > > > Why is this t64 upgrade working then as it is removing deprecated > packages > > for *t64 packages? > > I do not know, at times I'm also wondering why it doesn't do it, but I > didn't > take time to
Bug#1065831: document package specifiers for `upgrade`
Hi all, >> No. Without a package as an argument it won't. Thanks! You're right. Let me write it down here again: - "apt upgrade" (no argument) will never remove a package, only upgrade or install - "apt upgrade pkg_name" will remove, upgrade or install the required package to satisfy its dependencies. - "apt upgrade foo- bar+": advanced option that can be used to specifically removed or install packages. >> Julian provided an explanation in #74, 20240312113620.ga1944...@debian.org I can't access this link.. >> I'm not a Debian developer, never have been. Just someone who submitted a patch or two. And your comments have been really valuable in figuring out what's going on! Again, my confusion was because this was the first time I reported a bug AND several people jumped in the conversation! It is not usually the case ;) Regards
