Bug#1031200: /usr/sbin/faxgetty: Re: hylafax-server: faxgetty.service doesn't work with iaxmodem
Hello Benoit, thank you for adding this information. The problem is indeed that one: udev is not triggering any event when the IAX modem device is created. This lead to a not existing dev-%i.device and hence, to a non activation of the faxgetty by systemd. The solution is to start the device manually. In your case, if the IAX modem are started at boot, you may just leave the changes you have done to the unit, and enable it for starting at boot time. I am looking for a different approach that could starts faxgetty when an IAX device is created, and stops it when it is removed. I do not have a solution yet. Bye, Giuseppe
Bug#1064499: The correct error message is: 452 Error writing to file: No such file or directory.
Well, it seems that message was a red herring. Enabling more verbose logging, this is what is shown in the ltfp transmission: Resolving host address... IPv6 is not supported or configured 1 address found: $NASIP Connecting to nas ($NASIP) port 21 <--- 220 NAS FTP server ready. ---> FEAT <--- 211- Extensions supported: <--- AUTH TLS <--- PBSZ <--- PROT <--- CCC <--- SIZE <--- MDTM <--- REST STREAM <--- MFMT <--- TVFS <--- MLST <--- MLSD <--- 211 End. ---> USER $username <--- 331 Password required for mantide. ---> PASS $password <--- 230 User $username logged in. ---> PWD <--- 257 "/" is current directory. ---> MKD backupftp <--- 550 backupftp: Permission denied. ---> MKD backupftp/backup-mantide <--- 550 backupftp/backup-mantide: File exists. ---> MKD backupftp/backup-mantide/ <--- 550 backupftp/backup-mantide: File exists. mkdir: Access failed: 550 backupftp/backup-mantide: File exists. (backupftp/backup-mantide/) ---> TYPE I <--- 200 Type set to I. ---> PASV <--- 227 Entering Passive Mode ($NASIP,217,122) Connecting data socket to ($NASIP) port 55674 Data connection established ---> STOR backupftp/backup-mantide/duplicity-full.20240223T070031Z.vol2.difftar.gpg <--- 150 Opening BINARY mode data connection for 'backupftp/backup-mantide/duplicity-full.20240223T070031Z.vol2.difftar.gpg'. <--- 452 Error writing to file: No such file or directory. Closing data socket ---> SIZE backupftp/backup-mantide/duplicity-full.20240223T070031Z.vol2.difftar.gpg <--- 213 346300416 copy: put rolled back to 349027744, seeking get accordingly copy: put rolled back to 346300416, seeking get accordingly ---> PASV <--- 227 Entering Passive Mode ($NASIP,217,21) Connecting data socket to ($NASIP) port 55573 Data connection established ---> REST 346300416 <--- 350 Restarting at 346300416. Send STORE or RETRIEVE to initiate transfer. ---> STOR backupftp/backup-mantide/duplicity-full.20240223T070031Z.vol2.difftar.gpg <--- 150 Opening BINARY mode data connection for 'backupftp/backup-mantide/duplicity-full.20240223T070031Z.vol2.difftar.gpg'. <--- 452 Error writing to file: No such file or directory. Closing data socket ---> SIZE backupftp/backup-mantide/duplicity-full.20240223T070031Z.vol2.difftar.gpg <--- 213 346300416 copy: put rolled back to 346445592, seeking get accordingly copy: put rolled back to 346300416, seeking get accordingly ---> PASV <--- 227 Entering Passive Mode ($NASIP,217,47) Connecting data socket to ($NASIP) port 55599 Data connection established ---> REST 346300416 <--- 350 Restarting at 346300416. Send STORE or RETRIEVE to initiate transfer. ---> STOR backupftp/backup-mantide/duplicity-full.20240223T070031Z.vol2.difftar.gpg <--- 150 Opening BINARY mode data connection for 'backupftp/backup-mantide/duplicity-full.20240223T070031Z.vol2.difftar.gpg'. <--- 452 Error writing to file: No such file or directory. Closing data socket ---> SIZE backupftp/backup-mantide/duplicity-full.20240223T070031Z.vol2.difftar.gpg <--- 213 346300416 copy: put rolled back to 346455728, seeking get accordingly copy: put rolled back to 346300416, seeking get accordingly ---> PASV <--- 227 Entering Passive Mode ($NASIP,217,13) Connecting data socket to ($NASIP) port 55565 Data connection established ---> REST 346300416 <--- 350 Restarting at 346300416. Send STORE or RETRIEVE to initiate transfer. ---> STOR backupftp/backup-mantide/duplicity-full.20240223T070031Z.vol2.difftar.gpg <--- 150 Opening BINARY mode data connection for 'backupftp/backup-mantide/duplicity-full.20240223T070031Z.vol2.difftar.gpg'. <--- 452 Error writing to file: No such file or directory. Closing data socket ---> SIZE backupftp/backup-mantide/duplicity-full.20240223T070031Z.vol2.difftar.gpg <--- 213 346300416 copy: put rolled back to 346445592, seeking get accordingly copy: put rolled back to 346300416, seeking get accordingly ---> PASV <--- 227 Entering Passive Mode ($NASIP,217,163) Connecting data socket to ($NASIP) port 55715 Data connection established ---> REST 346300416 <--- 350 Restarting at 346300416. Send STORE or RETRIEVE to initiate transfer. ---> STOR backupftp/backup-mantide/duplicity-full.20240223T070031Z.vol2.difftar.gpg <--- 150 Opening BINARY mode data connection for 'backupftp/backup-mantide/duplicity-full.20240223T070031Z.vol2.difftar.gpg'. <--- 452 Error writing to file: No such file or directory. Closing data socket ---> SIZE backupftp/backup-mantide/duplicity-full.20240223T070031Z.vol2.difftar.gpg <--- 213 346300416 copy: put rolled back to 346444144, seeking get accordingly copy: put rolled back to 346300416, seeking get accordingly ---> PASV <--- 227 Entering Passive Mode ($NASIP,216,246) Connecting data socket to ($NASIP) port 55542 Data connection established ---> REST 346300416 <--- 350 Restarting at 346300416. Send STORE or RETRIEVE to initiate transfer. ---> STOR
Bug#1064499: using lftp backend, backup fails with error message: mkdir: Access failed: 550 $dirname: File exists
Package: duplicity Version: 0.8.22-1+b3 Severity: important Hello, I had a backup configured and running since a few months. It is failing since 12 February with this error: --- Start running command BKP at 2024-02-23 08:00:30.967 --- Attempt of put Nr. 1 failed. BackendException: Error running 'lftp -c "source /srv/nfs/misc/tmp/duplicity-rf7ep785-tempdir/mkstemp-b5gnn5mu-1; mkdir -p backupftp/backup-mantide/; put /srv/nfs/misc/tmp/duplicity-rf7ep785- tempdir/mktemp-2uh27izg-4 -o backupftp/backup-mantide/duplicity- full.20240223T070031Z.vol2.difftar.gpg"': returned 1, with output: mkdir: Access failed: 550 backupftp/backup-mantide: File exists. (backupftp/backup-mantide/) put: /srv/nfs/misc/tmp/duplicity-rf7ep785-tempdir/mktemp-2uh27izg-4: Fatal error: max-retries exceeded The URL I am using is: ftp://user:password@host/backupftp/backup-mantide' It seems that duplicity issues the mkdir command before copying any file, but now this mkdir command is failing since the directory already exists. The source might be a change in lftp command (lftp version is 4.9.2-2+b1). This would be strange since lftp package hasn't changed since July 2022. Thank you, Giuseppe
Bug#1060672: kodi: High CPU usage even when idle
Hello Vasyl, here is some information and a stack trace of the kodi thread that keep consuming CPU. >From what I understand, the problem is in the renderer code, but I am calling kodi in standalone, so I think the renderer should not used at all. top output (with thread view): --- top - 08:23:42 up 12 days, 17:25, 1 user, load average: 0,17, 0,34, 0,54 Threads: 507 total, 1 running, 506 sleeping, 0 stopped, 0 zombie %Cpu(s): 3,9 us, 0,6 sy, 0,0 ni, 94,0 id, 0,5 wa, 0,0 hi, 0,0 si, 0,0 st MiB Mem : 32005,4 total, 3096,0 free, 5365,6 used, 26530,5 buff/cache MiB Swap: 1904,0 total,681,9 free, 1222,1 used. 26639,7 avail Mem PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 3517230 giuseppe 20 0 2901040 108596 43788 S 11,6 0,3 9,02 kodi.bin 3517231 giuseppe 21 1 2901040 108596 43788 S 0,0 0,3 0:00.00 Announce 3517236 giuseppe 21 1 2901040 108596 43788 S 0,0 0,3 0:37.17 Lirc 3517279 giuseppe 21 1 2901040 108596 43788 S 0,0 0,3 0:49.54 libinput 3517280 giuseppe 39 19 2901040 108596 43788 S 0,0 0,3 0:00.00 kodi.bi:disk$0 3517281 giuseppe 20 0 2901040 108596 43788 S 0,0 0,3 0:16.58 kodi.bin:gdrv0 3517282 giuseppe 20 0 2901040 108596 43788 S 0,0 0,3 0:02.67 ActiveAE 3517283 giuseppe 20 0 2901040 108596 43788 S 0,0 0,3 0:01.61 AESink 3517284 giuseppe 20 0 2901040 108596 43788 S 0,0 0,3 0:00.00 FDEventMonitor 3517301 giuseppe 20 0 2901040 108596 43788 S 0,0 0,3 0:45.26 DetectDVDMedia 3517302 giuseppe 20 0 2901040 108596 43788 S 0,0 0,3 0:22.80 kodi.bin 3517303 giuseppe 21 1 2901040 108596 43788 S 0,0 0,3 1:35.60 PeripBusUSBUdev 3517304 giuseppe 21 1 2901040 108596 43788 S 0,3 0,3 15:36.00 PeripBusCEC 3517305 giuseppe 21 1 2901040 108596 43788 S 0,0 0,3 0:02.54 PeripBusAddon 3517306 giuseppe 20 0 2901040 108596 43788 S 0,0 0,3 14:05.19 PeripEventScan 3517307 giuseppe 20 0 2901040 108596 43788 S 0,0 0,3 0:00.87 kodi.bin 3517308 giuseppe 20 0 2901040 108596 43788 S 0,0 0,3 0:46.74 kodi.bin 3517309 giuseppe 20 0 2901040 108596 43788 S 0,0 0,3 0:03.63 kodi.bin 3517310 giuseppe 20 0 2901040 108596 43788 S 0,0 0,3 0:02.75 kodi.bin 3517311 giuseppe 20 0 2901040 108596 43788 S 0,0 0,3 0:06.63 kodi.bin 3517312 giuseppe 20 0 2901040 108596 43788 S 0,0 0,3 0:02.63 kodi.bin 3517313 giuseppe 20 0 2901040 108596 43788 S 0,0 0,3 0:04.14 kodi.bin 3517314 giuseppe 20 0 2901040 108596 43788 S 0,0 0,3 0:00.78 kodi.bin 3517318 giuseppe 20 0 2901040 108596 43788 S 0,0 0,3 0:11.37 EventServer 3517319 giuseppe 20 0 2901040 108596 43788 S 0,0 0,3 0:10.68 TCPServer 3517320 giuseppe 21 1 2901040 108596 43788 S 0,0 0,3 0:03.45 kodi.bin 3517331 giuseppe 20 0 2901040 108596 43788 S 0,0 0,3 0:02.15 kodi.bin 3517225 giuseppe 20 02576836836 S 0,0 0,0 0:00.00 kodi --- systemd output: --- $ systemctl status kodi ● kodi.service - Kodi DLNA server Loaded: loaded (/etc/systemd/system/kodi.service; enabled; preset: enabled) Active: active (running) since Mon 2024-01-15 19:51:25 CET; 3 days ago Main PID: 3517222 (kodi-standalone) Tasks: 29 (limit: 38330) Memory: 164.8M CPU: 9h 2min 20.842s CGroup: /system.slice/kodi.service ├─3517222 /bin/sh /usr/bin/kodi-standalone ├─3517225 /bin/sh /usr/bin/kodi --standalone └─3517230 /usr/lib/x86_64-linux-gnu/kodi/kodi.bin --standalone gen 15 19:51:26 mantide kodi-standalone[3517230]: JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock gen 15 19:51:26 mantide kodi-standalone[3517230]: JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock gen 16 16:32:17 mantide kodi-standalone[3517230]: WARNING: Unhandled message: interface=org.freedesktop.DBus, path=/org/freedesktop/DBus, member=ActivatableServicesChanged gen 16 16:32:18 mantide kodi-standalone[3517230]: WARNING: Unhandled message: interface=org.freedesktop.DBus, path=/org/freedesktop/DBus, member=ActivatableServicesChanged gen 16 16:32:20 mantide kodi-standalone[3517230]: WARNING: Unhandled message: interface=org.freedesktop.DBus, path=/org/freedesktop/DBus, member=ActivatableServicesChanged gen 16 16:32:23 mantide kodi-standalone[3517230]: WARNING: Unhandled message: interface=org.freedesktop.DBus, path=/org/freedesktop/DBus, member=ActivatableServicesChanged gen 16 16:32:39 mantide kodi-standalone[3517230]: WARNING: Unhandled message: interface=org.freedesktop.DBus, path=/org/freedesktop/DBus, member=ActivatableServicesChanged gen 16 16:38:59 mantide
Bug#1060457: /usr/sbin/exim4: SIGSEGV when remote smtp reject the message
Hello Andreas, Il giorno ven, 12/01/2024 alle 18.15 +0100, Andreas Metzler ha scritto: [...] > Is this a regression in 4.96-15+deb12u4? i.e. can you still reprroduce > the issue after downgrading exim4-daemon-heavy to 4.96-15+deb12u3 [1] > (and re-reproduce after upgrading again)? I am going to downgrade the package and let it run for a week. I'll report here. Thank you, Giuseppe
Bug#1060672: kodi: High CPU usage even when idle
Hello Vasyl, I am trying kodi on a DELL PowerEdge T20, CPU E3-1225 v3 @3.20GHz, 32Gb of RAM, Debian GNU/Linux 12 (bookworm). Thank you, Giuseppe
Bug#1060672: kodi: High CPU usage even when idle
Package: kodi Version: 2:20.1+dfsg-1 Severity: normal Dear Maintainer, I intalled kodi a few days back in order to access all my media from a TV. I executed and configured it using its GUI. Then I stopped it and run the standalone version from a systemd unit in order to have it running all time. I noticed that while nobody is using kodi from my TV, i.e., during nights, the CPU usage is constantly about 8-12% for kodi.bin process. Why? Is there anything that can be changed on the configuration in order to stop this high CPU usage? Just for reference, the CPU is Intel(R) Xeon(R) E3-1225 v3 @3.20GHz. Thank you, Giuseppe -- System Information: Debian Release: 12.4 APT prefers stable-security APT policy: (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.1.0-17-amd64 (SMP w/4 CPU threads; PREEMPT) Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.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 kodi depends on: ii kodi-bin 2:20.1+dfsg-1 ii kodi-data 2:20.1+dfsg-1 Versions of packages kodi recommends: ii kodi-repository-kodi [kodi-repository] 2:20.1+dfsg-1 ii kodi-visualization-spectrum 20.2.0+ds1-1 kodi suggests no packages. -- no debconf information
Bug#983831: Dead link at https://www.debian.org/consultants/
Hello Scott, we are checking this bug report very late, I am sorry for that. Il giorno mar, 02/03/2021 alle 02.32 +, Scott C. MacCallum ha scritto: > Package: www.debian.org > Name: www.callpaul.eu > URL: www.callpaul.eu > Location: Line 1733, Col 23 [...] As of today, the link is working. It has a self signed certificate, but it is working. May I just close this bug report? Thank you, Giuseppe
Bug#1054214: gnome: caps-lock for upper case accented letters does not work anymore
Package: gnome
Version: 1:44+1
Severity: normal
Dear Maintainer,
in the Italian keyboard, we have some keys that only display lowercase
letters. As
an example, the key on the right of the "P" key has four symbols: è é { [.
In order to have the "è" character, I just press the key; in order to have
the "é" I press shift+key; in order to have "[" I press altgr+key; in order
to have "{" I press altgr+shift+key.
For the uppercase letter "È" I used to press the capslock+key. In order to
have the uppercase "É" I used to press the capslock+shift+key.
I just updated from debian 12 stable (bookworm) to testing (trixie) and now I
cannot type any more these keys in UPPERCASE: even using the capslock, the
displayed letter is lowercase.
On the Linux console, i.e., without the gnome graphical desktop running, the
behaviour is unchanged, so everything work as before.
Bye,
Giuseppe
-- System Information:
Debian Release: trixie/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 6.5.0-1-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=it_IT.utf8, LC_CTYPE=it_IT.utf8 (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 gnome depends on:
ii avahi-daemon 0.8-11
ii cheese 44.1-1
ii cups-pk-helper 0.2.6-1+b1
ii desktop-base 12.0.6+nmu1
ii evolution 3.50.0-1
ii evolution-plugins 3.50.0-1
ii file-roller 43.0-1
ii gnome-calendar 45.0-1
ii gnome-clocks 45.0-1
ii gnome-color-manager 3.36.0-2
ii gnome-core 1:44+1
ii gnome-maps 45.0-1
ii gnome-music 45.0-1
ii gnome-photos 43.0-2
ii gnome-sound-recorder 43~beta-1
ii gnome-tweaks 42~beta-4
ii gnome-weather 45.0-1
ii gstreamer1.0-libav 1.22.6-1
ii gstreamer1.0-plugins-ugly 1.22.6-1
ii libgsf-bin 1.14.50-1
ii libproxy1-plugin-networkmanager 0.4.18-1.2
ii libreoffice-calc 4:7.5.6-1
ii libreoffice-gnome 4:7.5.6-1
ii libreoffice-impress 4:7.5.6-1
ii libreoffice-writer 4:7.5.6-1
ii network-manager-gnome 1.34.0-1
ii orca 45.1-2
ii rhythmbox 3.4.7-1
ii rhythmbox-plugin-cdrecorder 3.4.7-1
ii rhythmbox-plugins 3.4.7-1
ii rygel-playbin 0.42.4-1+b1
ii rygel-tracker 0.42.4-1+b1
ii seahorse 43.0-1
ii simple-scan 44.0-1
ii totem-plugins 43.0-2
ii xdg-user-dirs-gtk 0.11-1
Versions of packages gnome recommends:
ii gnome-games 1:44+1
ii gnome-initial-setup 45.0-1
ii gnome-remote-desktop 44.2-6
ii transmission-gtk 3.00-2.1+deb12u1
Versions of packages gnome suggests:
ii alacarte 3.50.0-1
pn firefox-esr-l10n-all | firefox-l10n-all
ii goobox 3.6.0-11
ii polari 45.0-1
ii vinagre 3.22.0-8.1
pn webext-ublock-origin-firefox | webext-ublock-origin-chromium
Versions of packages gnome-core depends on:
ii adwaita-icon-theme 45.0-1
ii at-spi2-core 2.50.0-1
ii baobab 45.0-1
ii dconf-cli 0.40.0-4
ii dconf-gsettings-backend 0.40.0-4
ii eog 45.0-1
ii evince 45.0-1
ii evolution-data-server 3.50.0-1
ii fonts-cantarell 0.303.1-1
ii gdm3 45.0.1-1
ii gkbd-capplet 3.28.1-1
ii glib-networking 2.78.0-1
ii gnome-backgrounds 45.0-1
ii gnome-bluetooth-sendto 42.6-1
ii gnome-calculator 1:45.0.2-1
ii gnome-characters 45.0-1
ii gnome-contacts 45.0-1
ii gnome-control-center 1:45.0-2
ii gnome-disk-utility 45.0-1
ii gnome-font-viewer 45.0-1
ii gnome-keyring 42.1-1+b2
ii gnome-logs 45~beta-2
ii gnome-menus 3.36.0-1.1
ii gnome-online-accounts 3.48.0-2
ii gnome-session 45.0-1
ii gnome-settings-daemon 45.0-1
ii gnome-shell 44.5-2
ii gnome-shell-extensions 44.0-2
ii gnome-software 45.0-1
ii gnome-sushi 45.0-1
ii gnome-system-monitor 45.0.2-1
ii gnome-terminal
Bug#1053704: assertion failed: perl:amd64 not marked as install despite no auto_inst
Package: crossgrader
Version: 0.0.3+nmu3
Severity: normal
Hello,
crossgrader second stage stops with assertion failed. This is an attempt of
switching from i386 to amd64 on Debian 12 machine.
Complete output is:
root@aristotele:~# crossgrader amd64 --second-stage --force-unavailable
Installing initramfs binary architecture check hook...
arch check hook already installed.
Hook installation failed.
Hit http://security.debian.org/debian-security bookworm-security InRelease
Hit http://ftp.debian.org/debian bookworm InRelease
Ign https://download.webmin.com/download/newkey/repository stable InRelease
Get:1 https://download.webmin.com/download/newkey/repository stable Release
[16.0 kB]
Get:2 https://download.webmin.com/download/newkey/repository stable Release.gpg
[819 B]
Err https://download.webmin.com/download/newkey/repository stable Release.gpg
The following signatures couldn't be verified because the public key is not
available: NO_PUBKEY 2D223B918916F2A2
Fetched 16.8 kB in 0s (0 B/s)
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/debian_crossgrader/crossgrader.py", line
175, in __init__
self._apt_cache.update(apt.progress.text.AcquireProgress())
File "/usr/lib/python3/dist-packages/apt/cache.py", line 603, in update
raise FetchFailedException()
apt.cache.FetchFailedException
Ignoring...
Couldn't find linux-image-6.1.0-9-686-pae:amd64, ignoring...
Couldn't find linux-image-6.1.0-12-686-pae:amd64, ignoring...
Couldn't find linux-image-686-pae:amd64, ignoring...
Couldn't find linux-image-6.1.0-13-686-pae:amd64, ignoring...
364 targets found.
Do you want to continue [y/N]? Y
Could not mark perl:amd64 for install, fixing manually.
Traceback (most recent call last):
File "/usr/bin/crossgrader", line 33, in
sys.exit(load_entry_point('debian-crossgrader==0.0.3', 'console_scripts',
'crossgrader')())
^
File "/usr/lib/python3/dist-packages/debian_crossgrader/__main__.py", line
258, in main
second_stage(args)
File "/usr/lib/python3/dist-packages/debian_crossgrader/__main__.py", line
112, in second_stage
crossgrader.cache_package_debs(targets)
File "/usr/lib/python3/dist-packages/debian_crossgrader/crossgrader.py", line
581, in cache_package_debs
assert target.marked_install, \
AssertionError: perl:amd64 not marked as install despite no auto_inst
Thank you,
Giuseppe
Bug#1039522: usrmerge: cannot complete upgrade to bookworm because of #842145
Hi Luca, Il giorno mar, 27/06/2023 alle 00.04 +0100, Luca Boccassi ha scritto: > The solution is provided in that bug: > > > Since convert-usrmerge can be run in a chroot on the NFS server maybe it > > would be easier to just make it fail if the > > root is NFS-mounted. > > Just like in the overlay or container cases, instead of converting the > client, convert the server first. Thank you for pointing this out, I did not really understand that sentence until now. So there is a workaround when your NFS server is a Linux machine and you may use chroot on it, at least. Thank you, Giuseppe
Bug#1039522: usrmerge: cannot complete upgrade to bookworm because of #842145
Hi Marco, Il giorno lun, 26/06/2023 alle 23.10 +0200, Marco d'Itri ha scritto: > On Jun 26, Giuseppe Sacco wrote: > > Warning: NFS detected, /usr/lib/usrmerge/convert-usrmerge will not be run > > automatically. See #842145 for details. > What is the purpose of opening this new bug about the same issue? The original bug report does not offer any details, nor solution about the problem. Moreover, it does mention a problem about an old debian release (stretch). This is a quite old bug that probably people think it cannot be really still open. A new report, about bookworm, may probably be more easily found in an Internet search. BTW, 7 years ago you wrote that you didn't had any environment to test this. If this still stands, I may give you access to this machine, if required. Just send me a private e-mail with an ssh public key. Or, I may try any suggestion you might have. Bye, Giuseppe
Bug#1039522: usrmerge: cannot complete upgrade to bookworm because of #842145
Package: usrmerge Version: 35 Severity: normal Dear Maintainer, while upgrading a diskless system, I've got this message: root@aristotele:~# dpkg --configure --pending Configurazione di usrmerge (35)... Warning: NFS detected, /usr/lib/usrmerge/convert-usrmerge will not be run automatically. See #842145 for details. E: usrmerge failed. dpkg: errore nell'elaborare il pacchetto usrmerge (--configure): il sottoprocesso installato pacchetto usrmerge script post-installation ha restituito lo stato di errore 1 Si sono verificati degli errori nell'elaborazione: usrmerge stopping the upgrade. In fact, the upgrade cannot continue with usrmerge enable. I tried removing usrmerge and putting it on hold using dpkg --set-selections, but then "apt upgrade" stop again here: preparativi per estrarre .../usr-is-merged_35_all.deb... ** * * The usr-is-merged package cannot be installed because this system does * not have a merged /usr. * * Please install the usrmerge package to convert this system to merged-/usr. * * For more information please read https://wiki.debian.org/UsrMerge. * ** dpkg: errore nell'elaborare l'archivio /var/cache/apt/archives/usr-is-merged_35_all.deb (--unpack): il sottoprocesso nuovo pacchetto usr-is-merged script pre-installation ha restituito lo stato di errore 1 Si sono verificati degli errori nell'elaborazione: /var/cache/apt/archives/usr-is-merged_35_all.deb E: Sub-process /usr/bin/dpkg returned an error code (1) and the whole process cannot go any further. Bye, Giuseppe -- System Information: Debian Release: 12.0 APT prefers stable-security APT policy: (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.1.0-9-amd64 (SMP w/8 CPU threads; PREEMPT) Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.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 usrmerge depends on: ii libfile-find-rule-perl 0.34-3 ii perl 5.36.0-7 usrmerge recommends no packages. usrmerge suggests no packages. -- no debconf information
Bug#1037251: Acknowledgement (assert ""win && m_cr"" failed in Init(): invalid dc for wxOverla)
Hello, I noticed this problem arise when I try to bring to front the pwsafe window. When that window is partially overlapped and hidden by another window, I click on the border of pwsafe window to bring it to front. Here is when the error message appears. If I click inside the pwsafe window, the problem does not show up. Bye, Giuseppe
Bug#1038802: Acknowledgement (evince: does not show up when in a SSH/X11 forward)
Hello, I went to the remote machine's desktop and found the evince window opened. It seems that the X11 tunnel, managed by SSH, is completely ignored by evince. Bye, Giuseppe
Bug#1038802: evince: does not show up when in a SSH/X11 forward
Package: evince Version: 43.1-2+b1 Severity: normal Dear Maintainer, I just updated debian from 11 to 12 and now I found this problem. It might not be really due to evince, but it is shown by evince. When I connect from a debian 12 machine to a second debian 12 machine with command "ssh -X debian12.domain.tld" I cannot run evince any more. If I do, the command does not show any window. It just stay there, wasting CPU cycles. This used to work with debian 11, but I also switched from Xorg to Wayland on both machines. I don't know if this is related, though. Thank you, Giuseppe -- System Information: Debian Release: 12.0 APT prefers stable-security APT policy: (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.1.0-9-amd64 (SMP w/8 CPU threads; PREEMPT) Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.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 evince depends on: ii dconf-gsettings-backend [gsettings-backend] 0.40.0-4 ii evince-common43.1-2 ii gsettings-desktop-schemas43.0-1 ii libatk1.0-0 2.46.0-5 ii libc62.36-9 ii libcairo-gobject21.16.0-7 ii libcairo21.16.0-7 ii libevdocument3-4 43.1-2+b1 ii libevview3-3 43.1-2+b1 ii libgdk-pixbuf-2.0-0 2.42.10+dfsg-1+b1 ii libglib2.0-0 2.74.6-2 ii libgnome-desktop-3-2043.2-2 ii libgtk-3-0 3.24.37-2 ii libhandy-1-0 1.8.1-1 ii libpango-1.0-0 1.50.12+ds-1 ii libpangocairo-1.0-0 1.50.12+ds-1 ii libsecret-1-00.20.5-3 ii shared-mime-info 2.2-1 Versions of packages evince recommends: ii dbus-user-session [default-dbus-session-bus] 1.14.6-1 ii dbus-x11 [dbus-session-bus] 1.14.6-1 Versions of packages evince suggests: ii gvfs 1.50.3-1 pn nautilus-sendto ii poppler-data 0.4.12-1 ii unrar1:6.2.6-1 -- no debconf information
Bug#1037251: assert ""win && m_cr"" failed in Init(): invalid dc for wxOverla
Package: passwordsafe Version: 1.16.0+dfsg-4 Severity: normal Dear Maintainer, since a few weeks, while using pwsafe, I get this message: An assertion failed! ./src/gtk/overlay.cpp(98): assert ""win && m_cr"" failed in Init(): invalid dc for wxOverlay then I have to press the "stop" button and restart pwsafe. Thank you, Giuseppe -- System Information: Debian Release: 12.0 APT prefers testing-security APT policy: (500, 'testing-security'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.1.0-9-amd64 (SMP w/4 CPU threads; PREEMPT) Locale: LANG=it_IT.utf8, LC_CTYPE=it_IT.utf8 (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 passwordsafe depends on: ii libc6 2.36-9 ii libgcc-s1 12.2.0-14 ii libmagic1 1:5.44-3 ii libqrencode4 4.1.1-1 ii libstdc++6 12.2.0-14 ii libuuid1 2.38.1-5+b1 ii libwxbase3.2-1 3.2.2+dfsg-2 ii libwxgtk3.2-1 3.2.2+dfsg-2 ii libx11-6 2:1.8.4-2 ii libxerces-c3.2 3.2.4+debian-1 ii libxtst6 2:1.2.3-1.1 ii libykpers-1-1 1.20.0-3 ii passwordsafe-common 1.16.0+dfsg-4 Versions of packages passwordsafe recommends: pn xvkbd passwordsafe suggests no packages. -- no debconf information
Bug#1036971: pwsafe: empty window after internal timeout or screen blank
Hello Bill, thank you for your quick reply. Il giorno mer, 31/05/2023 alle 09.13 -0400, Bill Blough ha scritto: > If I understand your report correctly, this sounds like expected > behavior - the program will lock itself in order to protect your > passwords. [...] I am sorry I did not explain it correctly. The database is locked, and this is the behaviour I want, so I am happy with that. The problem is that when I get back to pwsafe window while the database is locked, I am not prompted for the password until I select Unlock from the menu. Prior to switching gnome from X11 to Wayland, and with the same version on a different machine, the prompt is automatic: when I put the focus to pwsafe window while the database is locked, a new window appear asking for the database password. Bye, Giuseppe
Bug#1036971: pwsafe: empty window after internal timeout or screen blank
Package: passwordsafe Version: 1.16.0+dfsg-4 Severity: normal Dear Maintainer, after running pwsafe, it select the default keystore, prompts for the password and displays the keystore content in the GUI. After some time the window automatically disappear but I may get it back using Alt-Tab key. Once the window is shown again, it is empty: it does not list the keystore content and it does not prompt for the keystore password either. Here, if I open the File menu and select the 'Unlock Safe' menu item, I see the keystore content correctly. I did not find any configuration option that could prevent the password prompt when getting back the pswafe window. Is this an error? Thank you, Giuseppe -- System Information: Debian Release: 12.0 APT prefers testing-security APT policy: (500, 'testing-security'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.1.0-9-amd64 (SMP w/4 CPU threads; PREEMPT) Locale: LANG=it_IT.utf8, LC_CTYPE=it_IT.utf8 (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 passwordsafe depends on: ii libc6 2.36-9 ii libgcc-s1 12.2.0-14 ii libmagic1 1:5.44-3 ii libqrencode4 4.1.1-1 ii libstdc++6 12.2.0-14 ii libuuid1 2.38.1-5+b1 ii libwxbase3.2-1 3.2.2+dfsg-2 ii libwxgtk3.2-1 3.2.2+dfsg-2 ii libx11-6 2:1.8.4-2 ii libxerces-c3.2 3.2.4+debian-1 ii libxtst6 2:1.2.3-1.1 ii libykpers-1-1 1.20.0-3 ii passwordsafe-common 1.16.0+dfsg-4 Versions of packages passwordsafe recommends: pn xvkbd passwordsafe suggests no packages. -- no debconf information
Bug#1036635: default papersize is always "letter"
Hello, Il giorno mer, 24/05/2023 alle 00.19 +0900, Osamu Aoki ha scritto: [...] > Hi, I tried with all pointing to "a4", but I get "letter". > ```sh > $ ls -l /etc/papersize > -rw-r--r-- 1 root root 3 May 23 23:24 /etc/papersize > $ cat /etc/papersize > a4 > $ LANG=ja_JP.UTF-8 LC_ALL=ja_JP.UTF-8 LC_PAPER=ja_JP.UTF-8 PAPERSIZE=a4 > PAPERCONF=/etc/papersize paperconf -d > letter > ``` > There is something wrong? Or am I doing things wrong? [...] you are asking for the default paper size, i.e., the one to be used when no configuration file is available. If you want the current paper size as per /etc/papersize, please remove the final "-d" from your command. It this what you were looking for? Bye, Giuseppe
Bug#1033285: unblock: libpaper/1.1.29
Hello Sebastian, Il giorno mer, 22/03/2023 alle 21.18 +0100, Sebastian Ramacher ha scritto: > Control: tags -1 moreinfo > > On 2023-03-21 12:03:30 +0100, Giuseppe Sacco wrote: > > Package: release.debian.org > > Severity: normal > > User: release.debian@packages.debian.org > > Usertags: unblock > > > > Please unblock package libpaper. This new version only includes non-code > > changes: a few typos corrections in manual pages and a new language > > translation. > > > > [ Reason ] > > While this is not a necessary update, it would benefits users without > > having any functional impact. > > > > [ Impact ] > > ditto > > > > [ Tests ] > > nothing > > > > [ Risks ] > > No code changes are present. There should not be any risks. > > > > [ Checklist ] > > [ X ] all changes are documented in the d/changelog > > [ X ] I reviewed all changes and I approve them > > [ X ] attach debdiff against the package in testing > > > > [ Other info ] > > nothing > > > > Thank you very much, > > Giuseppe > > > > unblock libpaper/1.1.29 > > > > > diff -Nru libpaper-1.1.28/debian/changelog libpaper- > > 1.1.29/debian/changelog > > --- libpaper-1.1.28/debian/changelog2019-06-26 00:04:32.0 > > +0200 > > +++ libpaper-1.1.29/debian/changelog2023-03-17 14:44:15.0 > > +0100 > > @@ -1,3 +1,14 @@ > > +libpaper (1.1.29) unstable; urgency=medium > > + > > + * Fix for parallel build. See #857058 > > How does this upload fix parallel building? The diff only contains > changes to translations? > You are right, that was my mistake. I've got a bug about parallel build and started fixing it, but later on I found the problem had already been fixed by another patch already applied, so I reverted my unnecessary changes and I forgot to the remove the line from changelog. My bad. Bye, Giuseppe
Bug#1033285: unblock: libpaper/1.1.29
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package libpaper. This new version only includes non-code changes: a few typos corrections in manual pages and a new language translation. [ Reason ] While this is not a necessary update, it would benefits users without having any functional impact. [ Impact ] ditto [ Tests ] nothing [ Risks ] No code changes are present. There should not be any risks. [ Checklist ] [ X ] all changes are documented in the d/changelog [ X ] I reviewed all changes and I approve them [ X ] attach debdiff against the package in testing [ Other info ] nothing Thank you very much, Giuseppe unblock libpaper/1.1.29 diff -Nru libpaper-1.1.28/debian/changelog libpaper-1.1.29/debian/changelog --- libpaper-1.1.28/debian/changelog 2019-06-26 00:04:32.0 +0200 +++ libpaper-1.1.29/debian/changelog 2023-03-17 14:44:15.0 +0100 @@ -1,3 +1,14 @@ +libpaper (1.1.29) unstable; urgency=medium + + * Fix for parallel build. See #857058 + * Added romanian translation. See #1032333 + * Updated standards-version to 4.6.0 (no changes) + * Update papersize manual page. See #959403 + * Update paperconf manual page. See #959404 + * Update paperconfig manual page. See #959405 + + -- Giuseppe Sacco Fri, 17 Mar 2023 14:44:15 +0100 + libpaper (1.1.28) unstable; urgency=medium * Completely fixed #927226. diff -Nru libpaper-1.1.28/debian/control libpaper-1.1.29/debian/control --- libpaper-1.1.28/debian/control 2016-07-16 18:06:42.0 +0200 +++ libpaper-1.1.29/debian/control 2023-03-17 14:29:31.0 +0100 @@ -2,7 +2,7 @@ Section: libs Priority: optional Maintainer: Giuseppe Sacco -Standards-Version: 3.9.8 +Standards-Version: 4.6.0 Build-Depends: autotools-dev, dpkg-dev (>= 1.16.1~), debhelper (>= 9), dh-autoreconf, dh-exec(>= 0.3), po-debconf, autoconf Package: libpaper1 diff -Nru libpaper-1.1.28/debian/po/ro.po libpaper-1.1.29/debian/po/ro.po --- libpaper-1.1.28/debian/po/ro.po 1970-01-01 01:00:00.0 +0100 +++ libpaper-1.1.29/debian/po/ro.po 2023-03-17 14:22:38.0 +0100 @@ -0,0 +1,316 @@ +# Mesajele în limba română pentru pachetul libpaper. +# Romanian translation of libpaper. +# Copyright © 2023 THE PACKAGE'S COPYRIGHT HOLDER +# This file is distributed under the same license as the libpaper package. +# +# Remus-Gabriel Chelu , 2023. +# +# Cronologia traducerii fișierului „libpaper”: +# Traducerea inițială, făcută de R-GC, pentru versiunea libpaper 1.1.28(2009-07-18). +# Actualizare a traducerii pentru versiunea Y, făcută de X, Y(anul). +# +msgid "" +msgstr "" +"Project-Id-Version: libpaper 1.1.28\n" +"Report-Msgid-Bugs-To: eppes...@debian.org\n" +"POT-Creation-Date: 2007-07-18 19:50+0200\n" +"PO-Revision-Date: 2023-02-26 11:30+0100\n" +"Last-Translator: Remus-Gabriel Chelu \n" +"Language-Team: Romanian \n" +"Language: ro\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Plural-Forms: nplurals=3; plural=(n==1 ? 0 : n==0 || (n!=1 && n%100>=1 && " +"n%100<=19) ? 1 : 2);\n" +"X-Bugs: Report translation errors to the Language-Team address.\n" +"X-Generator: Poedit 3.2.2\n" + +# R-GC, scrie: +# cum multe dintre dimensiunile ce apar aici, +# au nume englezești(a se citi, americane), +# ce traduse, nu ne spun mare lucru și care +# pe aici pe colo, induc în eroare, am extras +# dimensiunile acestora (în milimetri), din +# pagina de Wikipedia: +# <https://en.wikipedia.org/wiki/Paper_size> +#. Type: select +#. Choices +#: ../libpaper1.templates:2001 +msgid "letter" +msgstr "Letter(scrisoare) [216 x 279mm]" + +#. Type: select +#. Choices +#: ../libpaper1.templates:2001 +msgid "a4" +msgstr "A4 [210 x 297mm]" + +#. Type: select +#. Choices +#: ../libpaper1.templates:2001 +msgid "note" +msgstr "Note(notă) [220 x 280mm]" + +#. Type: select +#. Choices +#: ../libpaper1.templates:2001 +msgid "legal" +msgstr "Legal [216 x 356mm]" + +#. Type: select +#. Choices +#: ../libpaper1.templates:2001 +msgid "executive" +msgstr "Executive [184 x 267mm]" + +#. Type: select +#. Choices +#: ../libpaper1.templates:2001 +msgid "halfletter" +msgstr "Half Letter(½ scrisoare) [140 x 216mm]" + +#. Type: select +#. Choices +#: ../libpaper1.templates:2001 +msgid "halfexecutive" +msgstr "Half Executive(½ executiv) [130 x 184mm]" + +#. Type: select +#. Choices +#: ../libpaper1.templates:2001 +msgid "11x17" +msgstr "11x17 [279 x 432mm]" + +#. Type: select +#. Choices +#: ../libpaper1.templates:2001 +msgid "statement" +msgstr "Statement(declarație) [140 x 216mm]" + +#. Type:
Bug#1031200: hylafax-server: faxgetty.service doesn't work with iaxmodem
Il giorno dom, 19/02/2023 alle 19.26 +, debian-bu...@dc0wh17f.mooo.com ha scritto: > Hi Giuseppe, > > [...] > > Could you please verify if any of the proposed configuration works also > > when adding/removing a new IAX device when iaxmodem is already up and > > running? > Same. I think the behavior is not a systemd issue but an issue of iaxmodem. > Once iaxmodem is started, it reads all available config files and assigns > any existing symlinks to a new device of /dev/pts/. It doesn't check if > it's already running and just overwrites existing symlinks. It doesn't > terminate itself either, so any previously started process of iaxmodem > remains still active. So, when I type /usr/bin/iaxmodem two times, the > result with two available configfiles under /etc/iaxmodem is four iaxmodem > processes running at the same time. > > As far as I understand the code of iaxmodem.c this is the intended behavior > (which, for me, is wrong). Maybe I should file a bug report against iaxmodem > first before we work on faxgetty's systemd unit - what do you think? you may probably just write to iaxmodem-users mailing lists. I already contacted the author there and he is aware of this Debian bug. Bye, Giuseppe
Bug#1031200: hylafax-server: faxgetty.service doesn't work with iaxmodem
Hello Tino, Il giorno mar, 14/02/2023 alle 12.54 +, debian-bu...@dc0wh17f.mooo.com ha scritto: > [...] > > The question is: could you confirm that you cannot > > add/remove/start/stop > > IAX devices without stopping the iaxmodem.service? In other words, no > > (device) events would be possibile once iaxmodem is started? > No. You can add/remove devices with a seperate call of iaxmodem > while iaxmodem.service is running. You can even (re)start > running devices. There is no lock or similar for a device once iaxmodem > is started. Could you please verify if any of the proposed configuration works also when adding/removing a new IAX device when iaxmodem is already up and running? Thank you, Giuseppe
Bug#1031200: hylafax-server: faxgetty.service doesn't work with iaxmodem
Hi Tino, Il giorno lun, 13/02/2023 alle 22.47 +, debian-bu...@dc0wh17f.mooo.com ha scritto: > Hello Giuseppe, > from my point of view all we need is a logical OR (||) in this systemd > unit. Unfortunately I couldn't find such an option in systemd's manpages. > So, I gave it a shot and tried this: > > [Unit] > Description=HylaFAX faxgetty %I > BindsTo=iaxmodem.service || dev-%i.device > After=network.target [...] The problem is if we may just wait for iaxmodem or if we need to wait for the device. The dev-%i.device has events when udev sends them, but since that path is not a real device, no udev events are sent. This probably means that using dev-%i.device on any systemd unit is useless. So, I am wondering if the minimal working unit is just [Unit] Description=HylaFAX faxgetty %I BindsTo=iaxmodem.service After=iaxmodem.service The question is: could you confirm that you cannot add/remove/start/stop IAX devices without stopping the iaxmodem.service? In other words, no (device) events would be possibile once iaxmodem is started? Thank you, Giuseppe
Bug#1031200: hylafax-server: faxgetty.service doesn't work with iaxmodem
Hello, Il giorno lun, 13/02/2023 alle 10.41 +, debian-bu...@dc0wh17f.mooo.com ha scritto: > Hello Giuseppe, > thank you for working on this and responding so quickly. > Yes, the Wants line is also working with two or more iax modems. Does iaxmodem create the link in /dev when you configure the line, or when it starts up? Is the link present when iaxmodem service is stopped? Thank you, Giuseppe
Bug#1031200: hylafax-server: faxgetty.service doesn't work with iaxmodem
Hello Tino, I will ask on the udev mailing list in order to find the best solution. I do have a question, is this "Wants" line working even when you have more then one IAX modem? > Wants=iaxmodem.service dev-%i.device Thank you, Giuseppe
Bug#1027681: hylafax: FTBFS with tiff 4.5.0+
Hello László, Il giorno dom, 08/01/2023 alle 09.02 +0100, László Böszörményi (GCS) ha scritto: > Hi Giuseppe., > > On Sun, Jan 1, 2023 at 10:23 PM Giuseppe Sacco wrote: > > Il giorno dom, 01/01/2023 alle 20.20 +0100, László Böszörményi ha scritto: > > You are right about upstream, but there is fork named hylafax+ that is > > quite > > active. See https://hylafax.sourceforge.io/ > > I'll have a look at that project and see if a patch is already available. > As I didn't get the result from you, I went on and checked it myself. > I attach a ready to use and tested patch for you as I don't want to > delay the tiff transition any further. another patch has been provided by hylafax+ developer, see https://sourceforge.net/p/hylafax/mailman/message/37757510/ I am going to check both patches and shortly upload a fixed package. Thank you, Giuseppe
Bug#1027444: linux-signed-amd64: system crash after loading radeon module
found 1027444 5.10.149+2 thanks I checked the system with an old kernel and I found the same problem. I think the problem was sitting there ever since but only arose one week ago when some other package triggered it. Bye, Giuseppe
Bug#1027681: hylafax: FTBFS with tiff 4.5.0+
Hello Laszlo, thank you for reporting the problem. Il giorno dom, 01/01/2023 alle 20.20 +0100, László Böszörményi ha scritto: > Source: hylafax > Version: 3:6.0.7-3.1 > Severity: important [...] > These are private to tiff itself from now on. You can copy these to > your source, but I'm interested if this package is worth keeping in > the archive. Last maintainer upload was in March 2020 and popcon is > 418 only. Upstream seems to be dead for ten years. You are right about upstream, but there is fork named hylafax+ that is quite active. See https://hylafax.sourceforge.io/ I'll have a look at that project and see if a patch is already available. Thank you, Giuseppe
Bug#1027444: linux-signed-amd64: system crash after loading radeon module
Source: linux-signed-amd64 Version: 6.0.12-1 Severity: important Dear Maintainer, I am using Debian testing on a DELL Precision M4700. After today upgrade, while the system was running but the screen was blanked, the system become unusable: the fans were spinning at maximum speed, the screen was black, no SSH login was possible, nothing could be done for unlocking it. I powered off the laptop using the power botton and started it again. After the grub screen and normal kernel output, the system blocked again. I tried a few times getting the same result. Booting without the default option "quiet", I saw that the last printed line was: [drm] radeon kernel modesetting enabled. The only way to boot the system again was adding parameter "module.blacklist=radeon" on the grub parameters for the linux kernel. The same behaviour happena with both kernel 6.0.0-5 and 6.0.0-6. I do not have tried with older kernel. All details follows: The video adapter PCI: 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Chelsea XT GL [FirePro M4000] (prog-if 00 [VGA controller]) Subsystem: Dell Chelsea XT GL [FirePro M4000] Flags: bus master, fast devsel, latency 0, IRQ 11, IOMMU group 1 Memory at e000 (64-bit, prefetchable) [size=256M] Memory at f7e0 (64-bit, non-prefetchable) [size=256K] I/O ports at e000 [size=256] Expansion ROM at 000c [disabled] [size=128K] Capabilities: Kernel modules: radeon, amdgpu The list of updated packages, today: -rw-r--r-- 1 root root4199 31 dic 06.31 /var/lib/dpkg/info/python3-pkg-resources.list -rw-r--r-- 1 root root 314 31 dic 06.31 /var/lib/dpkg/info/python3-setuptools-whl.list -rw-r--r-- 1 root root 234 31 dic 06.31 /var/lib/dpkg/info/gcc-12-base:amd64.list -rw-r--r-- 1 root root 233 31 dic 06.31 /var/lib/dpkg/info/gcc-12-base:i386.list -rw-r--r-- 1 root root 700 31 dic 06.31 /var/lib/dpkg/info/libstdc++6:amd64.list -rw-r--r-- 1 root root 690 31 dic 06.31 /var/lib/dpkg/info/libstdc++6:i386.list -rw-r--r-- 1 root root 187 31 dic 06.31 /var/lib/dpkg/info/libquadmath0:amd64.list -rw-r--r-- 1 root root 181 31 dic 06.31 /var/lib/dpkg/info/libquadmath0:i386.list -rw-r--r-- 1 root root 175 31 dic 06.31 /var/lib/dpkg/info/libgomp1:amd64.list -rw-r--r-- 1 root root 169 31 dic 06.31 /var/lib/dpkg/info/libgomp1:i386.list -rw-r--r-- 1 root root 187 31 dic 06.31 /var/lib/dpkg/info/libgfortran5:amd64.list -rw-r--r-- 1 root root 181 31 dic 06.31 /var/lib/dpkg/info/libgfortran5:i386.list -rw-r--r-- 1 root root 181 31 dic 06.31 /var/lib/dpkg/info/libatomic1:amd64.list -rw-r--r-- 1 root root 175 31 dic 06.31 /var/lib/dpkg/info/libatomic1:i386.list -rw-r--r-- 1 root root 173 31 dic 06.31 /var/lib/dpkg/info/libcc1-0:amd64.list -rw-r--r-- 1 root root 172 31 dic 06.31 /var/lib/dpkg/info/libitm1:amd64.list -rw-r--r-- 1 root root 175 31 dic 06.31 /var/lib/dpkg/info/libasan8:amd64.list -rw-r--r-- 1 root root 175 31 dic 06.31 /var/lib/dpkg/info/liblsan0:amd64.list -rw-r--r-- 1 root root 175 31 dic 06.31 /var/lib/dpkg/info/libtsan2:amd64.list -rw-r--r-- 1 root root 178 31 dic 06.31 /var/lib/dpkg/info/libubsan1:amd64.list -rw-r--r-- 1 root root 519 31 dic 06.31 /var/lib/dpkg/info/g++-12.list -rw-r--r-- 1 root root 41909 31 dic 06.31 /var/lib/dpkg/info/libstdc++-12-dev:amd64.list -rw-r--r-- 1 root root 263 31 dic 06.31 /var/lib/dpkg/info/libobjc4:amd64.list -rw-r--r-- 1 root root 984 31 dic 06.31 /var/lib/dpkg/info/libobjc-12-dev:amd64.list -rw-r--r-- 1 root root1171 31 dic 06.31 /var/lib/dpkg/info/gfortran-12.list -rw-r--r-- 1 root root 401 31 dic 06.31 /var/lib/dpkg/info/libgfortran-12-dev:amd64.list -rw-r--r-- 1 root root8899 31 dic 06.31 /var/lib/dpkg/info/libgcc-12-dev:amd64.list -rw-r--r-- 1 root root2359 31 dic 06.31 /var/lib/dpkg/info/gcc-12.list -rw-r--r-- 1 root root 320 31 dic 06.31 /var/lib/dpkg/info/cpp-12.list -rw-r--r-- 1 root root 130 31 dic 06.31 /var/lib/dpkg/info/libx32ubsan1.list -rw-r--r-- 1 root root 100 31 dic 06.31 /var/lib/dpkg/info/libx32gcc-s1.list -rw-r--r-- 1 root root 302 31 dic 06.31 /var/lib/dpkg/info/libx32stdc++6.list -rw-r--r-- 1 root root 139 31 dic 06.31 /var/lib/dpkg/info/libx32quadmath0.list -rw-r--r-- 1 root root 124 31 dic 06.31 /var/lib/dpkg/info/libx32itm1.list -rw-r--r-- 1 root root 127 31 dic 06.31 /var/lib/dpkg/info/libx32gomp1.list -rw-r--r-- 1 root root 133 31 dic 06.31 /var/lib/dpkg/info/libx32atomic1.list -rw-r--r-- 1 root root 181 31 dic 06.31 /var/lib/dpkg/info/libgccjit0:amd64.list -rw-r--r-- 1 root root 126 31 dic 06.31 /var/lib/dpkg/info/lib32ubsan1.list -rw-r--r-- 1 root root 97 31 dic 06.31 /var/lib/dpkg/info/lib32gcc-s1.list -rw-r--r-- 1 root root 296 31 dic 06.31 /var/lib/dpkg/info/lib32stdc++6.list -rw-r--r-- 1 root root 135 31 dic 06.31
Bug#1020430: usrmerge: cannot handle "open" binary when both kbd and xdg-utils are installed
Il giorno mer, 21/09/2022 alle 23.29 +0100, Luca Boccassi ha scritto: > On Wed, 21 Sep 2022 21:46:19 +0200 Giuseppe Sacco > wrote: > > Il giorno mer, 21/09/2022 alle 18.26 +0200, Ansgar ha scritto: > > > [...] > > > Is /bin/open a symlink to openvt on your system? > > > > > > > Yes, it is. > > Looks like leftover cruft from kbd < 2.0.4-4 - can you manually delete > /bin/open and then install usrmerge again? Yes, this made the whole process complete without other errors. The machine has been originally installed with Debian 6 and then updated many times, but I made sure no old packages were left installed. So, the kbd was the latest one, and "dpkg -S /bin/open" correctly identified the file belonged to kbd package. Should this bug be filed against kbd in order to remove old links when updated? Bye, Giuseppe signature.asc Description: This is a digitally signed message part
Bug#1020430: usrmerge: cannot handle "open" binary when both kbd and xdg-utils are installed
Il giorno mer, 21/09/2022 alle 18.26 +0200, Ansgar ha scritto: > [...] > Is /bin/open a symlink to openvt on your system? > Yes, it is. Bye, Giuseppe
Bug#1020430: usrmerge: cannot handle "open" binary when both kbd and xdg-utils are installed
Package: usrmerge Version: 30 Severity: normal Dear Maintainer, while installing this package on a system that has both kbd and xdg-utils packages, it stops with this error message: Continuare? [S/n] s Lettura dei changelog... Fatto Estrazione dei template dai pacchetti: 100% Preconfigurazione dei pacchetti in corso Configurazione di usrmerge (30)... FATAL ERROR: Both /bin/open and /usr/bin/open exist. You can try correcting the errors reported and running again /usr/lib/usrmerge/convert-usrmerge until it will complete without errors. Do not install or update other Debian packages until the program has been run successfully. E: usrmerge failed. dpkg: errore nell'elaborare il pacchetto usrmerge (--configure): il sottoprocesso installato pacchetto usrmerge script post-installation ha restituito lo stato di errore 1 Si sono verificati degli errori nell'elaborazione: usrmerge needrestart is being skipped since dpkg has failed E: Sub-process /usr/bin/dpkg returned an error code (1) Please note that kbd is version 2.3.0-3 and xdg-utils is 1.1.3-4.1 Bye, Giuseppe -- System Information: Debian Release: bookworm/sid APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'testing'), (500, 'stable') merged-usr: no Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.19.0-1-amd64 (SMP w/8 CPU threads; PREEMPT) Kernel taint flags: TAINT_WARN Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.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 usrmerge depends on: ii libfile-find-rule-perl 0.34-2 ii perl5.34.0-5 usrmerge recommends no packages. usrmerge suggests no packages. -- no debconf information
Bug#996355: libvirt: When apparmor is enabled and VM uses LVM, cannot start QEMU VMs anymore
Source: libvirt
Severity: important
Dear Maintainer,
since a few weeks all VMs stopped working. This is on a Debian 11 installed
on March from testing distribution, eventually updated to stable once
bullseye has been released.
All VM use LVM volumes as disks. Now, when libvirt tries to start them, it
stops with this error that I found in /var/log/libvirt/qemu/ad.log (text
wrapped by me)
2021-10-13T09:02:14.020416Z qemu-system-x86_64: -blockdev
{"driver":"host_device","filename":"/dev/vg/ad","aio":"threads"a
,"node-name":"libvirt-3-storage","cache":{"direct":false,"no-flush":true},
"auto-read-only":true,"discard":"unmap"}: Could not open '/dev/vg/ad':
Permission denied
2021-10-13 09:02:14.098+: shutting down, reason=failed
at the same time I see an error in syslog from apparmor (again, text
wrapped by me):
audit: type=1400 audit(1634115229.330:59): apparmor="DENIED"
operation="open" profile="libvirt-2351395b-d8e8-4b8f-8c2f-59787002e863"
name="/dev/dm-3" pid=6720 comm="qemu-system-x86" requested_mask="r"
denied_mask="r" fsuid=64055 ouid=64055
I looked for any solutions on the Internet and found that the apparmor
profile is rebuilt from a template configured in
/etc/apparmor.d/libvirt/TEMPLATE.qemu,
so I tried to add new rules for my LVM volumes:
profile LIBVIRT_TEMPLATE flags=(attach_disconnected) {
#include
/dev/vg/ad rk,
/dev/vg/db rk,
/dev/vg/db-dati rk,
/dev/vg/os rk,
/dev/vg/os-dati rk,
}
but it did not work. I don't know if this is important, but please note
that I used the volume names found in the qemu error message even if they
are not the ones from the apparmor error message. In fact they are links:
lrwxrwxrwx 1 root root 7 13 ott 11.02 /dev/vg/ad -> ../dm-3
Thank you very much,
Giuseppe
-- System Information:
Debian Release: 11.1
APT prefers stable-security
APT policy: (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 5.10.0-9-amd64 (SMP w/4 CPU threads)
Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.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
Bug#973365: On MacBook Pro (P8600) wifi card with BCM4322 chipset does not work
Hello Roger, Il giorno lun, 31/05/2021 alle 00.09 +0900, Roger Shimizu ha scritto: > control: tags -1 +moreinfo > > On Thu, Oct 29, 2020 at 10:45 PM Giuseppe Sacco wrote: [...] > > Hello, > > on an Apple MacBook Pro running debian testing (kernel package is > > version 5.9.1-1), I have this card: > > > > # lspci | fgrep Netw > > 02:00.0 Network controller: Broadcom Inc. and subsidiaries BCM4322 > > 802.11a/b/g/n Wireless LAN Controller (rev 01) > > > > The card is recognized and managed by the broadcom-sta driver but it > > does not displays the list of available networks: > > You may try latest 6.30.223.271-16 or its backports version. > If it still doesn't work for you, you may try b43 driver [1] > > [1] https://wiki.debian.org/bcm43xx I just tested both solutions, but the problem is still there. Because of this, I am forced to use an external USB WiFi card instead of the internal one. Thank you, Giuseppe
Bug#981337: tomcat9: cannot set JAVA_HOME in /etc/default/tomcat9 when using systemd service unit
Package: tomcat9 Version: 9.0.31-1~deb10u3 Severity: normal Dear Maintainer, on a debian stable new installation, changing the JAVA_HOME property in /etc/default/tomcat9 does not work, i.e. the java used is the default one. In order to set a non default JAVA_HOME I had to add the lines: [Service} Environment="JAVA_HOME=/usr/lib/jvm/adoptopenjdk-8-hotspot-amd64" in its override file, i.e. /etc/systemd/system/tomcat9.service.d/00_javahome.conf . Thank you, Giuseppe -- System Information: Debian Release: 10.7 APT prefers stable APT policy: (500, 'stable'), (500, 'oldstable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-13-amd64 (SMP w/4 CPU cores) Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8), LANGUAGE=it_IT.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages tomcat9 depends on: ii lsb-base10.2019051400 ii systemd 241-7~deb10u5 ii tomcat9-common 9.0.31-1~deb10u3 ii ucf 3.0038+nmu1 Versions of packages tomcat9 recommends: ii libtcnative-1 1.2.21-1 Versions of packages tomcat9 suggests: pn tomcat9-admin pn tomcat9-docs pn tomcat9-examples pn tomcat9-user -- no debconf information
Bug#978220: Bug#964198: hylafax: diff for NMU version 3:6.0.7-3.1
Hello Bastien, thank you very much for your NMU. Bye, Giuseppe
Bug#973365: On MacBook Pro (P8600) wifi card with BCM4322 chipset does not work
Package: broadcom-sta Version: 6.30.223.271-15 Severity: major Hello, on an Apple MacBook Pro running debian testing (kernel package is version 5.9.1-1), I have this card: # lspci | fgrep Netw 02:00.0 Network controller: Broadcom Inc. and subsidiaries BCM4322 802.11a/b/g/n Wireless LAN Controller (rev 01) The card is recognized and managed by the broadcom-sta driver but it does not displays the list of available networks: # iw wlp2s0 info Interface wlp2s0 ifindex 3 wdev 0x1 addr d8:a2:5e:94:71:2f type managed wiphy 0 txpower 200.00 dBm # iw wlp2s0 scan # iwlist wlp2s0 scanning wlp2s0No scan results some errors are collected by dmesg: # dmesg | fgrep wl [6.264433] wl: loading out-of-tree module taints kernel. [6.264438] wl: module license 'MIXED/Proprietary' taints kernel. [6.295680] wl: module verification failed: signature and/or required key missing - tainting kernel [6.483541] wlan0: Broadcom BCM432b 802.11 Hybrid Wireless Controller 6.30.223.271 (r587334) [6.736188] wl :02:00.0 wlp2s0: renamed from wlan0 [ 51.038418] ERROR @wl_notify_scan_status : [ 51.038423] wlp2s0 Scan_results error (-22) [ 71.069924] ERROR @wl_notify_scan_status : [ 71.069929] wlp2s0 Scan_results error (-22) [ 100.036085] ERROR @wl_notify_scan_status : [ 100.036089] wlp2s0 Scan_results error (-22) [ 143.072119] ERROR @wl_notify_scan_status : [ 143.072124] wlp2s0 Scan_results error (-22) [ 207.044072] ERROR @wl_notify_scan_status : [ 207.044077] wlp2s0 Scan_results error (-22) [ 302.052066] ERROR @wl_notify_scan_status : [ 302.052071] wlp2s0 Scan_results error (-22) [ 423.136013] ERROR @wl_notify_scan_status : [ 423.136016] wlp2s0 Scan_results error (-22) [ 544.127948] ERROR @wl_notify_scan_status : [ 544.127950] wlp2s0 Scan_results error (-22) [ 583.360026] ERROR @wl_notify_scan_status : [ 583.360029] wlp2s0 Scan_results error (-22) [ 633.348078] ERROR @wl_notify_scan_status : [ 633.348084] wlp2s0 Scan_results error (-22) A more detailed output of lspci is: # lspci -vv -s 02:00.0 02:00.0 Network controller: Broadcom Inc. and subsidiaries BCM4322 802.11a/b/g/n Wireless LAN Controller (rev 01) Subsystem: Apple Inc. AirPort Extreme Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort+ SERR- Capabilities: [e8] MSI: Enable- Count=1/1 Maskable- 64bit+ Address: Data: Capabilities: [d0] Express (v1) Endpoint, MSI 00 DevCap: MaxPayload 128 bytes, PhantFunc 0, Latency L0s <4us, L1 unlimited ExtTag+ AttnBtn- AttnInd- PwrInd- RBE+ FLReset- SlotPowerLimit 0.000W DevCtl: CorrErr- NonFatalErr- FatalErr- UnsupReq- RlxdOrd- ExtTag+ PhantFunc- AuxPwr- NoSnoop- MaxPayload 128 bytes, MaxReadReq 128 bytes DevSta: CorrErr+ NonFatalErr- FatalErr- UnsupReq- AuxPwr- TransPend- LnkCap: Port #0, Speed 2.5GT/s, Width x1, ASPM L0s L1, Exit Latency L0s <4us, L1 <64us ClockPM+ Surprise- LLActRep- BwNot- ASPMOptComp- LnkCtl: ASPM L0s L1 Enabled; RCB 64 bytes, Disabled- CommClk+ ExtSynch- ClockPM+ AutWidDis- BWInt- AutBWInt- LnkSta: Speed 2.5GT/s (ok), Width x1 (ok) TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt- Capabilities: [100 v1] Advanced Error Reporting UESta: DLP- SDES- TLP- FCP- CmpltTO+ CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol- UEMsk: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol- UESvrt: DLP+ SDES- TLP- FCP+ CmpltTO- CmpltAbrt- UnxCmplt- RxOF+ MalfTLP+ ECRC- UnsupReq- ACSViol- CESta: RxErr- BadTLP- BadDLLP- Rollover- Timeout- AdvNonFatalErr+ CEMsk: RxErr- BadTLP- BadDLLP- Rollover- Timeout- AdvNonFatalErr+ AERCap: First Error Pointer: 0e, ECRCGenCap+ ECRCGenEn- ECRCChkCap+ ECRCChkEn- MultHdrRecCap- MultHdrRecEn- TLPPfxPres- HdrLogCap- HeaderLog: 0001 00a8000f d3203088 Capabilities: [13c v1] Virtual Channel Caps: LPEVC=0 RefClk=100ns PATEntryBits=1 Arb:Fixed- WRR32- WRR64- WRR128- Ctrl: ArbSelect=Fixed Status: InProgress- VC0:Caps: PATOffset=00 MaxTimeSlots=1 RejSnoopTrans- Arb:Fixed- WRR32- WRR64- WRR128- TWRR128- WRR256- Ctrl: Enable+ ID=0 ArbSelect=Fixed TC/VC=ff Status: NegoPending- InProgress- Capabilities: [160 v1] Device Serial Number 71-2f-5e-ff-ff-94-d8-a2 Capabilities: [16c
Bug#968001: tightvnc-java: Invalid module description, or, may java module be mixed with other JARs in /usr/share/java?
Hello Sven, Il giorno lun, 12/10/2020 alle 23.09 +0200, Sven Geuer ha scritto: > Hello Guiseppe, > > I believe I solved the issue. I'll send you another unreleased version > of tighvnc-java in a separate email for you to test it. Indeed the problem seems to be solved, in fact, now a different problem appears on a package :-) $ java --module-path /usr/share/java \ --add-modules javafx.controls \ -Djavafx.preloader=lu.nowina.nexu.NexUPreLoader \ -Dglass.accessible.force=false -jar Neos.jar Error occurred during initialization of boot layer java.lang.module.FindException: Two versions of module jdom1 found in /usr/share/java (jdom1-1.1.3.jar and jdom1.jar) $ ls -l /usr/share/java/jdom* -rw-r--r-- 1 root root 156912 2 nov 2018 /usr/share/java/jdom1-1.1.3.jar lrwxrwxrwx 1 root root 15 2 nov 2018 /usr/share/java/jdom1.jar -> jdom1-1.1.3.jar Thanks, Giuseppe signature.asc Description: This is a digitally signed message part
Bug#968001: tightvnc-java: Invalid module description, or, may java module be mixed with other JARs in /usr/share/java?
Hello Sven, Il giorno sab, 03/10/2020 alle 18.39 +0200, Sven Geuer ha scritto: > Hello Guiseppe, [...] > As I don't possess any specific java knowledge I cannot judge whether > this will fix the issue you reported. I will send you the deb file > attached to a separate email and would like to ask you to test whether > it fixes this bug for you. If it doesn't, I am afraid there is little > what can be done, as upstream is dead. them problem is still there. I'll try to get some more help from other java developers and, possibly, I'll gather a patch. The current error is similar to the original one: $ java --module-path /usr/share/java \ --add-modules javafx.controls \ -Djavafx.preloader=lu.nowina.nexu.NexUPreLoader \ -Dglass.accessible.force=false -jar Neos.jar Error occurred during initialization of boot layer java.lang.module.FindException: Unable to derive module descriptor for /usr/share/java/tightvncviewer.jar Caused by: java.lang.module.InvalidModuleDescriptorException: CapsContainer.class found in top-level directory (unnamed package not allowed in module) Thank you, Giuseppe
Bug#963689: Acknowledgement (linux-image-5.6.0-2-powerpc: stuck at 'pmac32_cpufreq' when booting)
Hello, it seems I found the problem as explained in the upstream bug I opened[1]. Waiting for a fix, a possibile workaround proposed by kernel developers is to unset CONFIG_VMAP_STACK. Is it possible to change this configuration option for powerpc (32bit) architecture? Thank you, Giuseppe [1]https://github.com/linuxppc/issues/issues/326
Bug#968001: tightvnc-java: Invalid module description, or, may java module be mixed with other JARs in /usr/share/java?
Package: tightvnc-java Version: 1.2.7-9 Severity: important Dear Maintainer, the package seems to be incorrect for recent JDKs. Here is an example of running a different program that uses the new modules architecture. While scanning the java directory I get this error message, and my application is not run at all. $ java --module-path /usr/share/java \ --add-modules javafx.controls \ -Djavafx.preloader=lu.nowina.nexu.NexUPreLoader \ -Dglass.accessible.force=false -jar nexu.jar Error occurred during initialization of boot layer java.lang.module.FindException: Unable to derive module descriptor for /usr/share/java/tightvncviewer.jar Caused by: java.lang.module.InvalidModuleDescriptorException: HTTPConnectSocketFactory.class found in top-level directory (unnamed package not allowed in module) in my tests, this happens with any java version since 11. Bye, Giuseppe -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.7.0-2-amd64 (SMP w/8 CPU threads) Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled tightvnc-java depends on no packages. Versions of packages tightvnc-java recommends: ii bc 1.07.1-2+b2 Versions of packages tightvnc-java suggests: ii tightvncserver 1:1.3.9-10
Bug#963689: How may I collect information for debugging this problem?
Hello kernel developers, I wish to collect more information about this problem. How may I achieve it? I tried many boot parameters but no more messages have been printed. Is there anything I may do? Should I use specially crafted initrd images? Thank you, Giuseppe
Bug#963689: linux-image-5.6.0-2-powerpc: stuck at 'pmac32_cpufreq' when booting
package src:linux found 963689 5.7.6-1 thanks I just found a new kernel in sid. This new 5.7 kernel has the same problem as the previous 5.6.0-2 Bye, Giuseppe
Bug#963689: linux-image-5.6.0-2-powerpc: stuck at 'pmac32_cpufreq' when booting
Package: src:linux Version: 5.6.14-2 Severity: important Dear Maintainer, I just updated an Apple PowerBook G4 from debian 8 (latest officially released version for powerpc) to unstable. The latest running kernel il 3.16 while the new 5.6.0 does not boot the machine. While booting, the last lines shown on the screen are: pmac32_cpufreq: registering PowerMac CPU frequency driver pamc32_cpufreq: Low: 667 MHz, High: 867 Mhz, Boot: 667 MHz then no more lines are printed. I waited about 5 minutes before powring off the machine. Rebooting with old kernel works. How may I collect more information? Bye, Giuseppe -- Package-specific info: ** Kernel log: boot messages should be attached ** Model information revision: 3.2 (pvr 8001 0302) platform: PowerMac model : PowerBook3,5 machine : PowerBook3,5 motherboard : PowerBook3,5 MacRISC2 MacRISC Power Macintosh Device Tree model: PowerBook3,5 ** Network interface configuration: *** /etc/network/interfaces: auto lo iface lo inet loopback auto eth0 iface eth0 inet dhcp ** PCI devices: :00:0b.0 Host bridge [0600]: Apple Inc. UniNorth 1.5 AGP [106b:002d] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- Reset+ 16bInt+ PostWrite+ 16-bit legacy interface ports at 0001 Capabilities: [a0] Power Management version 1 Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0+,D1+,D2+,D3hot+,D3cold+) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- Bridge: PM- B3+ Kernel driver in use: yenta_cardbus Kernel modules: yenta_socket 0002:24:0b.0 Host bridge [0600]: Apple Inc. UniNorth 1.5 Internal PCI [106b:002f] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- TAbort- SERR- TAbort- SERR- pn grub-ieee1275 pn linux-doc-5.6 pn mkvmlinuz Versions of packages linux-image-5.6.0-2-powerpc is related to: pn firmware-amd-graphics pn firmware-atheros pn firmware-bnx2 pn firmware-bnx2x pn firmware-brcm80211 pn firmware-cavium pn firmware-intel-sound pn firmware-intelwimax pn firmware-ipw2x00 pn firmware-ivtv pn firmware-iwlwifi pn firmware-libertas ii firmware-linux-nonfree0.43 pn firmware-misc-nonfree pn firmware-myricom pn firmware-netxen pn firmware-qlogic pn firmware-realtek pn firmware-samsung pn firmware-siano pn firmware-ti-connectivity pn xen-hypervisor -- no debconf information
Bug#959820: firefox-esr: FTBFS, cannot compile on debian buster + security updates
Package: firefox-esr Version: 68.7.0esr-1~deb10u1 Severity: major The building process on debian 10 i386 stops with an error during linking. I just downloaded and rebuilt the package on a freshly installed QEMU VM and got an error. I was trying to rebuild it with a specific GCC optimization, this way: # dpkg-source -x firefox-esr_68.7.0esr-1~deb10u1.dsc # apt-get build-dep firefox-esr # apt-get install build-essential # cd firefox-esr-68.7.0esr # time env DEB_CFLAGS_MAINT_APPEND="-march=pentium4" dpkg-buildpackage -uc -us and the build process fails with this error: /usr/bin/g++ -o ../../dist/bin/plugin-container -Wdate-time -D_FORTIFY_SOURCE=2 -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=2 -fstack-protector-strong -Wall -Wempty-body -Wignored-qualifiers -Woverloaded-virtual -Wpointer-arith -Wsign-compare -Wtype-limits -Wunreachable-code -Wwrite-strings -Wno-invalid-offsetof -Wc++1z-compat -Wduplicated-cond -Wimplicit-fallthrough -Wno-error=maybe-uninitialized -Wno-error=deprecated-declarations -Wno-error=array-bounds -Wno-error=coverage-mismatch -Wno-error=free-nonheap-object -Wno-error=multistatement-macros -Wno-error=class-memaccess -Wformat -Wformat-overflow=2 -fno-sized-deallocation -O2 -fdebug-prefix-map=/mnt/firefox-esr-68.7.0esr=. -fstack-protector-strong -Wformat -Werror=format-security -march=pentium4 -fno-schedule-insns2 -fno-lifetime-dse -fno-delete-null-pointer-checks -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=2 -fstack-protector-strong -fno-exceptions -fno-strict-aliasing -fno-rtti -ffunction-sections -fdata-sections -fno-exceptions -fno-math-errno -pthread -pipe -freorder-blocks -O2 -fomit-frame-pointer -funwind-tables /mnt/firefox-esr-68.7.0esr/build-browser/ipc/app/plugin-container.list -lpthread -Wl,-z,relro -Wl,--as-needed -Wl,--as-needed -Wl,--compress-debug-sections=zlib -Wl,--reduce-memory-overheads -Wl,--no-keep-memory -Wl,--stats -fstack-protector-strong -Wl,-z,noexecstack -Wl,-z,text -Wl,-z,relro -Wl,-z,nocopyreloc -Wl,-Bsymbolic-functions -Wl,--build-id=sha1 -rdynamic -Wl,-rpath-link,/mnt/firefox-esr-68.7.0esr/build-browser/dist/bin -Wl,-rpath-link,/usr/lib -pie ../../config/external/nspr/pr/libnspr4.so ../../config/external/nspr/libc/libplc4.so ../../config/external/nspr/ds/libplds4.so ../../toolkit/library/libxul.so -ldl /usr/bin/ld: ../../toolkit/library/libxul.so: undefined reference to `gtk_file_chooser_set_do_overwrite_confirmation' /usr/bin/ld: ../../toolkit/library/libxul.so: undefined reference to `gtk_main_iteration' /usr/bin/ld: ../../toolkit/library/libxul.so: undefined reference to `gtk_page_setup_new' /usr/bin/ld: ../../toolkit/library/libxul.so: undefined reference to `gtk_page_setup_set_left_margin' /usr/bin/ld: ../../toolkit/library/libxul.so: undefined reference to `gtk_dialog_get_content_area' /usr/bin/ld: ../../toolkit/library/libxul.so: undefined reference to `gtk_print_unix_dialog_get_selected_printer' /usr/bin/ld: ../../toolkit/library/libxul.so: undefined reference to `gdk_event_copy' /usr/bin/ld: ../../toolkit/library/libxul.so: undefined reference to `gtk_print_unix_dialog_get_page_setup' /usr/bin/ld: ../../toolkit/library/libxul.so: undefined reference to `gtk_combo_box_new_with_entry' /usr/bin/ld: ../../toolkit/library/libxul.so: undefined reference to `gtk_radio_button_get_type' /usr/bin/ld: ../../toolkit/library/libxul.so: undefined reference to `gtk_print_job_set_source_file' /usr/bin/ld: ../../toolkit/library/libxul.so: undefined reference to `gtk_window_resize' /usr/bin/ld: ../../toolkit/library/libxul.so: undefined reference to `gtk_button_new_with_label' /usr/bin/ld: ../../toolkit/library/libxul.so: undefined reference to `gtk_window_iconify' /usr/bin/ld: ../../toolkit/library/libxul.so: undefined reference to `gtk_render_background' /usr/bin/ld: ../../toolkit/library/libxul.so: undefined reference to `gdk_flush' /usr/bin/ld: ../../toolkit/library/libxul.so: undefined reference to `gtk_plug_get_type' /usr/bin/ld: ../../toolkit/library/libxul.so: undefined reference to `gtk_selection_data_get_target' /usr/bin/ld: ../../toolkit/library/libxul.so: undefined reference to `gtk_style_context_get_property' /usr/bin/ld: ../../toolkit/library/libxul.so: undefined reference to `gdk_window_process_updates' /usr/bin/ld: ../../toolkit/library/libxul.so: undefined reference to `gtk_file_chooser_set_current_name' /usr/bin/ld: ../../toolkit/library/libxul.so: undefined reference to `gtk_widget_get_style_context' /usr/bin/ld: ../../toolkit/library/libxul.so: undefined reference to `gtk_print_settings_set_duplex' /usr/bin/ld: ../../toolkit/library/libxul.so: undefined reference to `gtk_window_unmaximize' /usr/bin/ld: ../../toolkit/library/libxul.so: undefined reference to `gtk_widget_path_get_object_type' /usr/bin/ld: ../../toolkit/library/libxul.so: undefined reference to `gtk_icon_set_unref' /usr/bin/ld: ../../toolkit/library/libxul.so: undefined reference to `gtk_print_settings_has_key' /usr/bin/ld:
Bug#959659: gnome-screensaver: Typos in Italian localization
Package: gnome-screensaver Version: 3.6.1-10 Severity: minor Tags: l10n patch upstream Dear Maintainer, one of the Italian sentences was missing the initial letter, so I checked the complete translation and added a few more simple changes. Please find attached a patch that you may just put in debian/patches. Bye, Giuseppe -- System Information: Debian Release: 10.3 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-8-amd64 (SMP w/8 CPU cores) Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8), LANGUAGE=it_IT.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages gnome-screensaver depends on: ii dbus-user-session [default-dbus-session-bus] 1.12.16-1 ii dbus-x11 [dbus-session-bus] 1.12.16-1 ii gsettings-desktop-schemas 3.28.1-1 ii libc6 2.28-10 ii libcairo2 1.16.0-4 ii libdbus-1-3 1.12.16-1 ii libdbus-glib-1-2 0.110-4 ii libgdk-pixbuf2.0-02.38.1+dfsg-1 ii libglib2.0-0 2.58.3-2+deb10u2 ii libgnome-desktop-3-17 3.30.2.1-2 ii libgnomekbd8 3.26.1-1 ii libgtk-3-03.24.5-1 ii libpam0g 1.3.1-5 ii libsystemd0 241-7~deb10u3 ii libx11-6 2:1.6.7-1 ii libxext6 2:1.3.3-1+b2 ii libxklavier16 5.4-4 ii libxxf86vm1 1:1.1.4-1+b2 Versions of packages gnome-screensaver recommends: ii gnome-power-manager 3.30.0-2 ii libpam-gnome-keyring 3.28.2-5 ii xfce4-power-manager 1.6.1-1 gnome-screensaver suggests no packages. -- no debconf information Index: gnome-screensaver-3.6.1/po/it.po === --- gnome-screensaver-3.6.1.orig/po/it.po +++ gnome-screensaver-3.6.1/po/it.po @@ -77,7 +77,7 @@ msgstr[1] "Il salvaschermo è rimasto at #: ../src/gnome-screensaver-command.c:258 #, c-format msgid "The screensaver is not currently active.\n" -msgstr "l salvaschermo non è attivo al momento.\n" +msgstr "Il salvaschermo non è attivo al momento.\n" #: ../src/gnome-screensaver-dialog.c:57 msgid "Show debugging output" @@ -166,7 +166,7 @@ msgstr "Errore durante il cambiamento de #: ../src/gnome-screensaver-dialog.c:198 msgid "You must choose a longer password" -msgstr "È necessario scegliere una password più lunga." +msgstr "È necessario scegliere una password più lunga" #: ../src/gnome-screensaver-dialog.c:199 msgid "Password has been already used. Choose another." @@ -183,7 +183,7 @@ msgstr "Le password non corrispondono" #: ../src/gnome-screensaver-dialog.c:267 msgid "Checking…" -msgstr "Controllo..." +msgstr "Controllo…" #: ../src/gnome-screensaver-dialog.c:309 ../src/gs-auth-pam.c:457 msgid "Authentication failed." @@ -262,7 +262,7 @@ msgstr "Il tasto BlocNum è attivo." #: ../src/gs-lock-plug.c:1350 msgid "S_witch User…" -msgstr "_Cambia utente..." +msgstr "_Cambia utente…" #: ../src/gs-lock-plug.c:1359 msgid "Log _Out"
Bug#956439: ITP: hylafaxplus -- enterprise-class open-source system for sending and receiving facsimiles
Package: wnpp Severity: normal Hello, I intend to package hylafax+ using the package name hylafaxplus. The software is published at https://hylafax.sourceforge.io/ Bye, Giuseppe
Bug#373148: hylafax-server: Failed to properly detect high-speed data carrier
Hi Paolo Il giorno mer, 14/06/2006 alle 08.48 +0200, Paolo ha scritto: > On Tue, Jun 13, 2006 at 04:08:12PM +0200, Giuseppe Sacco wrote: > > > > Could you please provide a complete log with SessionTracing at 0xFFF? > > yep. Need to do a cleanup first. HDD is almost full after those long send > list. I'll provide details as soon as I get it. It's been a long time since you did not update this bug report. Many hylafax new versions have been released without any new report about this bug. Would you mind to close this bug report and reopen it, eventually, if you still may reproduce it on the latest version? Thank you, Giuseppe
Bug#952319: hylafax: FTBFS: Incompatible TIFF Library.
Hello Lucas, thank you for reporting this problem. I already fixed it in the new package I am working on since a week. I should upload a fixed version in a few days. Bye, Giuseppe
Bug#937734: Updated Italian debconf PO translation
Package: dbconfig-common Version: 2.0.12 Hello Paul, here is the updated Italian PO translation. It has been reviewed by the Italian translators team. Bye, Giuseppe it.po.bz2 Description: application/bzip
Bug#927226: libpaper1: Fresh RC1 install doesn't configure /etc/papersize
Hello Thorsten, thank you very much for your testing. Indeed the bug required more fixing than what I did. I did follow your steps for reproducing it, and now I have a new package that fix it. If you want to try it, please fetch it here: https://eppesuigoccas.homedns.org/~giuseppe/debian/libpaper1_1.1.27_amd64.deb https://eppesuigoccas.homedns.org/~giuseppe/debian/libpaper-utils_1.1.27_amd64.deb or dget https://eppesuigoccas.homedns.org/~giuseppe/debian/libpaper_1.1.27.dsc Bye, Giuseppe
Bug#931023: unblock: libpaper/1.1.27
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package libpaper 1.1.26 has a circular dependency in debian/rules that skips the creation of an important file: libpaper1.config. The new package fixes this problem and make use of DPKG_EXPORT_BUILDFLAGS. source debdiff is attached unblock libpaper/1.1.27 -- System Information: Debian Release: 10.0 APT prefers testing APT policy: (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-5-amd64 (SMP w/8 CPU cores) Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8), LANGUAGE=it_IT.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled diff -Nru libpaper-1.1.26/configure.ac libpaper-1.1.27/configure.ac --- libpaper-1.1.26/configure.ac2018-12-11 11:50:29.0 +0100 +++ libpaper-1.1.27/configure.ac2019-06-23 21:26:40.0 +0200 @@ -1,6 +1,6 @@ dnl Process this file with autoconf to produce a configure script. -AC_INIT([libpaper], [1.1.26]) +AC_INIT([libpaper], [1.1.27]) AC_CONFIG_SRCDIR([configure.ac]) AM_INIT_AUTOMAKE([no-define]) AM_CONFIG_HEADER(config.h) diff -Nru libpaper-1.1.26/debian/changelog libpaper-1.1.27/debian/changelog --- libpaper-1.1.26/debian/changelog2018-12-11 11:50:45.0 +0100 +++ libpaper-1.1.27/debian/changelog2019-06-23 21:27:03.0 +0200 @@ -1,3 +1,10 @@ +libpaper (1.1.27) unstable; urgency=medium + + * Fixed a circular dependency in debian/rules that left libpaper1.config +not built. See #927226. + + -- Giuseppe Sacco Sun, 23 Jun 2019 21:27:03 +0200 + libpaper (1.1.26) unstable; urgency=medium * Check for ucf presence in the postrm script. See #916197 and #916198. diff -Nru libpaper-1.1.26/debian/rules libpaper-1.1.27/debian/rules --- libpaper-1.1.26/debian/rules2018-12-02 22:28:23.0 +0100 +++ libpaper-1.1.27/debian/rules2019-06-23 21:27:03.0 +0200 @@ -6,6 +6,9 @@ include /usr/share/dpkg/architecture.mk +DPKG_EXPORT_BUILDFLAGS = 1 +include /usr/share/dpkg/buildflags.mk + package:= $(firstword $(shell dh_listpackages)) prefix := $(CURDIR)/debian/tmp share := /usr/share @@ -24,20 +27,9 @@ native_paperconf := debian/build-native/src/paperconf endif -cflags := -g -Wall -ifeq (,$(findstring noopt,$(DEB_BUILD_OPTIONS))) -cflags += -O2 -else -cflags += -O0 -endif - -export CFLAGS=$(cflags) -export CXXFLAGS=$(cflags) - version:= $(shell dpkg-parsechangelog | \ sed -ne 's/^Version: *\([0-9]\+:\)*//p') - tag: cvs tag -c -F $(subst .,_,debian_version_$(version)) ifeq ($(findstring -,$(version)),) @@ -57,7 +49,7 @@ endif touch $@ -build-indep: config debian/libpaper1.config +build-indep: config libpaper1.config-stamp $(MAKE) -C debian/build ifneq ($(DEB_BUILD_GNU_TYPE),$(DEB_HOST_GNU_TYPE)) $(MAKE) -C debian/build-native @@ -67,15 +59,16 @@ build-arch:build-indep build: build-arch -debian/libpaper1.config: build-arch - exec > $@.new \ - && sed -n '1,/^__BEGIN_PAPERSPECS__/p' $@ \ - && $(native_paperconf) -amns \ - && sed -n '/^__END_PAPERSPECS__/,$$p' $@ - mv $@.new $@ +libpaper1.config-stamp: + exec > debian/libpaper1.config.new \ + && sed -n '1,/^__BEGIN_PAPERSPECS__/p' debian/libpaper1.config \ + && cat lib/paperspecs \ + && sed -n '/^__END_PAPERSPECS__/,$$p' debian/libpaper1.config + mv debian/libpaper1.config.new debian/libpaper1.config + touch libpaper1.config-stamp clean: checkroot - rm -f *-stamp + rm -f *-stamp build-indep [ ! -f Makefile ] || $(MAKE) distclean rm -rf debian/build debian/build-native dh_autoreconf_clean
Bug#927226: libpaper1: Fresh RC1 install doesn't configure /etc/papersize
Hello Thorsten, Voip, and Jacob, I think the problem has been solved in version 1.1.27, currently in unstable. I would really appreciate if you could test it, as well as I did. If this package passes your tests, I will ask for an unblock that will let the package migrate to testing/buster in a few days. Bye, Giuseppe Il giorno mar, 16/04/2019 alle 16.35 +0200, Thorsten Ehlers ha scritto: > Package: libpaper1 > Version: 1.1.26 > Severity: normal > Tags: d-i > > Dear Maintainer, > >* What led up to the situation? > > I did a fresh installation with RC1 Debian installer > >* What exactly did you do (or not do) that was effective (or > ineffective)? > > I chose German/Germany locale in the install process but got a > "letter" instead > of "a4" default in /etc/papersize > >* What was the outcome of this action? > > bad formatted prints > > I had to start "dpkg-reconfigure libpaper1" manually and choose A4 > here, this > should be part of the installation process. In fact it was in earlier > alpha > versions of the installer.
Bug#927226: libpaper1: Fresh RC1 install doesn't configure /etc/papersize
Hello Thorsten, it seems the problem raises while building the package; it is not related to the new installer (as I was initially thinking). In fact, while building the package, make displays a notice about a circular dependency of debian/libpaper1.config and build-arch. Indeed, make is right. I am going to check debian/rules file in order to fix the problem. Thank you, Giuseppe
Bug#929599: calendarserver: missing dependency on libpython-dev
Package: calendarserver Version: 9.2+dfsg-1 Severity: important Hello Rahul, I just installed the package, changed the configuration file in order to start it, then start it. The server did not start because of this error (shown by journalctl): mag 26 21:28:01 mantide systemd[1]: Starting LSB: Calendar and Contacts Server... mag 26 21:28:02 mantide calendarserver[18826]: usr/lib/python2.7/dist-packages/twext/python/__pycache__/_cffi_twext_python_sacl_xe128630fxbbd600c.c:2:20: fatal error: Python.h: File o directory non esistente mag 26 21:28:02 mantide calendarserver[18826]: #include mag 26 21:28:02 mantide calendarserver[18826]: ^ mag 26 21:28:02 mantide calendarserver[18826]: compilation terminated. mag 26 21:28:02 mantide systemd[1]: Started LSB: Calendar and Contacts Server. Installing package libpython-dev solved the problem. Bye, Giuseppe -- System Information: Debian Release: 9.9 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.9.0-9-amd64 (SMP w/4 CPU cores) Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8), LANGUAGE=it_IT.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages calendarserver depends on: ii adduser 3.115 ii lsb-base 9.20161125 ii memcached1.4.33-1+deb9u1 ii python 2.7.13-2 ii python-crypto2.6.1-7 ii python-dateutil 2.7.3-3 ii python-kerberos 1.1.14-2 ii python-openssl 16.2.0-1 ii python-pg80001.10.6-1 ii python-psutil5.5.1-1 ii python-pycalendar1:2.1~git20161130.0.e68e150-1 ii python-service-identity 16.0.0-2 ii python-setproctitle 1.1.10-1+b2 ii python-sqlparse 0.2.4-1 ii python-twext 1:0.1~git20161216.0.b90293c-2 ii python-twisted 18.9.0-3 ii python-twisted-core 18.9.0-3 ii python-tz2019.1-1 ii python-xattr 0.9.6-1 ii python-zope.interface4.3.2-1+b2 ii ssl-cert 1.0.39 Versions of packages calendarserver recommends: pn python-pam calendarserver suggests no packages. -- Configuration Files: /etc/caldavd/resources.xml changed: /etc/default/calendarserver changed: start_calendarserver=yes -- no debconf information
Bug#913629: mpt-status only works on controller 0
Package: mpt-status Version: 1.2.0-8 Severity: normal Hello, if you have more than one SCSI controller, depending on the order they are loaded at boot, the mpt-status does not work. As an example, if the the machine with these controllers agenzia-480:~# lspci | grep SCS 03:00.0 SCSI storage controller: LSI Logic / Symbios Logic SAS1068E PCI-Express Fusion-MPT SAS (rev 08) 07:08.0 SCSI storage controller: LSI Logic / Symbios Logic 53c1030 PCI-X Fusion-MPT Dual Ultra320 SCSI (rev c1) load the drivers in this (problematic) order: agenzia-480:~# cat /proc/mpt/summary ioc0: LSI53C1020A A1, FwRev=01032700h, Ports=1, MaxQ=255, IRQ=16 ioc1: LSISAS1068E B3, FwRev=00192f00h, Ports=1, MaxQ=266, IRQ=16 mpt-status does not work. See: agenzia-480:~# mpt-status -u0 -p Checking for SCSI ID:0 Checking for SCSI ID:1 Checking for SCSI ID:2 Checking for SCSI ID:3 Checking for SCSI ID:4 Checking for SCSI ID:5 Checking for SCSI ID:6 Checking for SCSI ID:7 Checking for SCSI ID:8 Checking for SCSI ID:9 Checking for SCSI ID:10 Checking for SCSI ID:11 Checking for SCSI ID:12 Checking for SCSI ID:13 Checking for SCSI ID:14 Checking for SCSI ID:15 Nothing found, contact the author agenzia-480:~# mpt-status -u1 -p Checking for SCSI ID:0 Checking for SCSI ID:1 Checking for SCSI ID:2 Checking for SCSI ID:3 Checking for SCSI ID:4 Checking for SCSI ID:5 Checking for SCSI ID:6 Checking for SCSI ID:7 Checking for SCSI ID:8 Checking for SCSI ID:9 Checking for SCSI ID:10 Checking for SCSI ID:11 Checking for SCSI ID:12 Checking for SCSI ID:13 Checking for SCSI ID:14 Checking for SCSI ID:15 Nothing found, contact the author If you reboot the machine and the scsi drivers are loaded in the reverse (correct?) order, i.e.: agenzia-480:~# cat /proc/mpt/summary ioc0: LSISAS1068E B3, FwRev=00192f00h, Ports=1, MaxQ=266, IRQ=16 ioc1: LSI53C1020A A1, FwRev=01032700h, Ports=1, MaxQ=255, IRQ=16 the command work: agenzia-480:~# mpt-status ioc0 vol_id 0 type IM, 2 phy, 278 GB, state OPTIMAL, flags ENABLED ioc0 phy 1 scsi_id 8 SEAGATE ST3300656SS HS0A, 279 GB, state ONLINE, flags NONE ioc0 phy 0 scsi_id 1 SEAGATE ST3300656SS HS0A, 279 GB, state ONLINE, flags NONE Please note that I have no other parameters: agenzia-480:~# LC_ALL=C cat /etc/default/mpt-statusd cat: /etc/default/mpt-statusd: No such file or directory This is on debian stretch 9.5, kernel 4.9.0-8-686, but the problem was present even with debian 8 and debian 7. Bye, Giuseppe P.S. the license file states that the source was downloaded from https://www.drugphish.ch/~ratz/mpt-status/ , but it seems that this page is not available.
Bug#900054: enabling DLL builds
Hello djcj, > > sure, but I have to check if that option would not be a problem on other platforms. Did you already test it on other platform as well? Thank you, Giuseppe
Bug#879382: RFP: pgadmin4 -- graphical administration tool for PostgreSQL, generation 4
Hello Christoph, I would like to help maintaining this new packages. Is there any preliminary version I might work on? Thank you, Giuseppe
Bug#879382: RFP: pgadmin4 -- graphical administration tool for PostgreSQL, generation 4
Il giorno gio, 30/11/2017 alle 11.28 +0100, Christoph Berg ha scritto:[...] > I'm just weeding through the needed python dependencies, but I think > the big problem will be properly packaging and/or collecting the > licenses of the metric ton of JS libraries bundled. Ok. Is there already a list of those libraries? I might start writing such a list, and then checking all licenses. Bye, Giuseppe
Bug#859630: java.security.AccessControlException: access denied ("java.io.FilePermission" "/usr/bin/xprop" "execute")
Package: icedtea-netx
Version: 1.6.2-3.1
Severity: normal
Every time I run this command, I get the exception below. The xprop
command is available, but default java policy deny its execution.
How shoud I change the java policy?
giuseppe@supergulp:~$ itweb-settings
java.security.AccessControlException: access denied ("java.io.FilePermission"
"/usr/bin/xprop" "execute")
at
java.security.AccessControlContext.checkPermission(AccessControlContext.java:472)
at
java.security.AccessController.checkPermission(AccessController.java:884)
at java.lang.SecurityManager.checkPermission(SecurityManager.java:549)
at java.lang.SecurityManager.checkExec(SecurityManager.java:796)
at java.lang.ProcessBuilder.start(ProcessBuilder.java:1018)
at java.lang.Runtime.exec(Runtime.java:620)
at java.lang.Runtime.exec(Runtime.java:450)
at java.lang.Runtime.exec(Runtime.java:347)
at org.GNOME.Accessibility.AtkWrapper.(AtkWrapper.java:34)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
at
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
at java.lang.Class.newInstance(Class.java:442)
at java.awt.Toolkit.loadAssistiveTechnologies(Toolkit.java:805)
at java.awt.Toolkit.getDefaultToolkit(Toolkit.java:886)
at
javax.swing.UIManager.getSystemLookAndFeelClassName(UIManager.java:611)
at
net.sourceforge.jnlp.controlpanel.ControlPanel.main(ControlPanel.java:426)
at
net.sourceforge.jnlp.controlpanel.CommandLine.main(CommandLine.java:508)
Thanks,
Giuseppe
Bug#855833: [Pkg-utopia-maintainers] Bug#855833: network-manager: wired connection in DHCP require a restart of networking.service
Hello Michael, I tried both of your suggestions, but none worked. [...] > So, it seems this is a problem with dhclient or the interaction with > dhclient. > Can you test version 1.6.2-1 from unstable as a first step. > If that still fails, please try the builtin dhcp implementation. You > can > use a drop-in config file for that: > > # cat /etc/NetworkManager/conf.d/dhcp.conf > [main] > dhcp=internal This is a long excerpt of the syslog using network-manager from unstable and using internal dhcp client. Feb 22 20:35:38 uefi systemd[1]: Reached target Network (Pre). Feb 22 20:35:38 uefi systemd[1]: Starting Raise network interfaces... Feb 22 20:35:38 uefi systemd[1]: Starting Network Manager... Feb 22 20:35:38 uefi NetworkManager[787]: [1487792138.2614] NetworkManager (version 1.6.2) is starting... Feb 22 20:35:38 uefi NetworkManager[787]: [1487792138.2614] Read config: /etc/NetworkManager/NetworkManager.conf (etc: dhcp.conf) Feb 22 20:35:38 uefi NetworkManager[787]: [1487792138.2656] manager[0x55e849d30040]: monitoring kernel firmware directory '/lib/firmware'. Feb 22 20:35:38 uefi NetworkManager[787]: [1487792138.2656] monitoring ifupdown state file '/run/network/ifstate'. Feb 22 20:35:38 uefi NetworkManager[787]: [1487792138.2679] dns-mgr[0x55e849d24180]: init: dns=default, rc-manager=resolvconf Feb 22 20:35:38 uefi NetworkManager[787]: [1487792138.2706] rfkill1: found WiFi radio killswitch (at /sys/devices/pci:00/:00:1c.1/:03:00.0/ieee80211/phy0/rfkill1) (driver iwlwifi) Feb 22 20:35:38 uefi NetworkManager[787]: [1487792138.2707] rfkill0: found WiFi radio killswitch (at /sys/devices/platform/dell-laptop/rfkill/rfkill0) (platform driver dell-laptop) Feb 22 20:35:38 uefi NetworkManager[787]: [1487792138.2896] manager[0x55e849d30040]: WiFi hardware radio set enabled Feb 22 20:35:38 uefi NetworkManager[787]: [1487792138.2896] manager[0x55e849d30040]: WWAN hardware radio set enabled Feb 22 20:35:38 uefi systemd[1]: Started Network Manager. Feb 22 20:35:38 uefi systemd[1]: Starting Network Manager Script Dispatcher Service... Feb 22 20:35:38 uefi systemd[1]: Starting Network Manager Wait Online... Feb 22 20:35:38 uefi systemd[1]: Started Network Manager Script Dispatcher Service. Feb 22 20:35:38 uefi NetworkManager[787]: [1487792138.3459] init! Feb 22 20:35:38 uefi NetworkManager[787]: [1487792138.3461] management mode: unmanaged Feb 22 20:35:38 uefi NetworkManager[787]: [1487792138.3464] devices added (path: /sys/devices/pci:00/:00:19.0/net/eth0, iface: eth0) Feb 22 20:35:38 uefi NetworkManager[787]: [1487792138.3464] device added (path: /sys/devices/pci:00/:00:19.0/net/eth0, iface: eth0): no ifupdown configuration found. Feb 22 20:35:38 uefi NetworkManager[787]: [1487792138.3464] devices added (path: /sys/devices/pci:00/:00:1c.1/:03:00.0/net/wlan0, iface: wlan0) Feb 22 20:35:38 uefi NetworkManager[787]: [1487792138.3464] device added (path: /sys/devices/pci:00/:00:1c.1/:03:00.0/net/wlan0, iface: wlan0): no ifupdown configuration found. Feb 22 20:35:38 uefi NetworkManager[787]: [1487792138.3464] devices added (path: /sys/devices/virtual/net/lo, iface: lo) Feb 22 20:35:38 uefi NetworkManager[787]: [1487792138.3464] device added (path: /sys/devices/virtual/net/lo, iface: lo): no ifupdown configuration found. Feb 22 20:35:38 uefi NetworkManager[787]: [1487792138.3464] end _init. Feb 22 20:35:38 uefi NetworkManager[787]: [1487792138.3465] settings: loaded plugin ifupdown: (C) 2008 Canonical Ltd. To report bugs please use the NetworkManager mailing list. (/usr/lib/x86_64-linux-gnu/NetworkManager/libnm-settings-plugin-ifupdown.so) Feb 22 20:35:38 uefi NetworkManager[787]: [1487792138.3465] settings: loaded plugin keyfile: (c) 2007 - 2016 Red Hat, Inc. To report bugs please use the NetworkManager mailing list. Feb 22 20:35:38 uefi NetworkManager[787]: [1487792138.3465] (1238702208) ... get_connections. Feb 22 20:35:38 uefi NetworkManager[787]: [1487792138.3465] (1238702208) ... get_connections (managed=false): return empty list. [...] Feb 22 20:35:38 uefi systemd[1]: Started Raise network interfaces. Feb 22 20:35:38 uefi systemd[1]: Reached target Network. Feb 22 20:35:38 uefi systemd[1]: Reached target Host and Network Name Lookups. [...] Feb 22 20:35:38 uefi NetworkManager[787]: [1487792138.6080] get unmanaged devices count: 0 Feb 22 20:35:38 uefi NetworkManager[787]: [1487792138.7596] settings: hostname: using hostnamed Feb 22 20:35:38 uefi NetworkManager[787]: [1487792138.7596] settings: hostname changed from (none) to "uefi" Feb 22 20:35:38 uefi NetworkManager[787]: [1487792138.7598] dhcp-init: Using DHCP client 'internal' Feb 22 20:35:38 uefi NetworkManager[787]: [1487792138.7598] manager: WiFi disabled by radio killswitch; enabled by state file Feb 22 20:35:38 uefi NetworkManager[787]: [1487792138.7599] manager: WWAN enabled by radio killswitch; enabled by
Bug#855833: network-manager: wired connection in DHCP require a restart of networking.service
Package: network-manager Version: 1.6.0-1 Severity: important Dear Maintainer, since about 3 weeks, network-manager does not correctly manage a wired interface via DHCP. This is a Debian testing machine updated every morning, so something changed about that date. Now, the wireless connection works perfectly, but wired connection keep disconnecting even before obtaining an address from DHCP server. This is an excerpt of what is shown in syslog: Feb 22 09:21:06 uefi NetworkManager[3982]: [1487751666.5288] manager: (eth0): new Ethernet device (/org/freedesktop/NetworkManager/Devices/2) Feb 22 09:21:06 uefi NetworkManager[3982]: [1487751666.5302] device (eth0): state change: unmanaged -> unavailable (reason 'managed') [10 20 2] Feb 22 09:21:06 uefi kernel: [ 86.351530] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready Feb 22 09:21:08 uefi NetworkManager[3982]: [1487751668.0652] device (eth0): link connected Feb 22 09:21:08 uefi NetworkManager[3982]: [1487751668.0658] device (eth0): state change: unavailable -> disconnected (reason 'carrier-changed') [20 30 40] Feb 22 09:21:08 uefi kernel: [ 87.885772] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx Feb 22 09:21:08 uefi kernel: [ 87.885808] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready Feb 22 09:21:08 uefi NetworkManager[3982]: [1487751668.0667] policy: auto-activating connection 'DHCP' Feb 22 09:21:08 uefi NetworkManager[3982]: [1487751668.0675] device (eth0): Activation: starting connection 'DHCP' (431bd46c-b763-42b8-8b57-2106b1453ebd) Feb 22 09:21:08 uefi NetworkManager[3982]: [1487751668.0678] device (eth0): state change: disconnected -> prepare (reason 'none') [30 40 0] Feb 22 09:21:08 uefi NetworkManager[3982]: [1487751668.0679] manager: NetworkManager state is now CONNECTING Feb 22 09:21:08 uefi NetworkManager[3982]: [1487751668.0683] device (eth0): state change: prepare -> config (reason 'none') [40 50 0] Feb 22 09:21:08 uefi NetworkManager[3982]: [1487751668.0686] device (eth0): state change: config -> ip-config (reason 'none') [50 70 0] Feb 22 09:21:08 uefi NetworkManager[3982]: [1487751668.0691] dhcp4 (eth0): activation: beginning transaction (timeout in 45 seconds) Feb 22 09:21:08 uefi NetworkManager[3982]: [1487751668.0701] dhcp4 (eth0): dhclient started with pid 3998 Feb 22 09:21:08 uefi kernel: [ 87.891242] e1000e :00:19.0 eth0: changing MTU from 1500 to 1400 Feb 22 09:21:08 uefi dhclient[3998]: DHCPREQUEST of 192.168.245.3 on eth0 to 255.255.255.255 port 67 Feb 22 09:21:09 uefi avahi-daemon[703]: Joining mDNS multicast group on interface eth0.IPv6 with address fe80::baca:3aff:febe:c618. Feb 22 09:21:09 uefi avahi-daemon[703]: New relevant interface eth0.IPv6 for mDNS. Feb 22 09:21:09 uefi avahi-daemon[703]: Registering new address record for fe80::baca:3aff:febe:c618 on eth0.*. Feb 22 09:21:12 uefi dhclient[3998]: DHCPREQUEST of 192.168.245.3 on eth0 to 255.255.255.255 port 67 Feb 22 09:21:12 uefi NetworkManager[3982]: [1487751672.0658] device (eth0): state change: ip-config -> unavailable (reason 'carrier-changed') [70 20 40] Feb 22 09:21:12 uefi NetworkManager[3982]: [1487751672.0981] dhcp4 (eth0): canceled DHCP transaction, DHCP client pid 3998 Feb 22 09:21:12 uefi NetworkManager[3982]: [1487751672.0982] dhcp4 (eth0): state changed unknown -> done Feb 22 09:21:12 uefi avahi-daemon[703]: Withdrawing address record for fe80::baca:3aff:febe:c618 on eth0. Feb 22 09:21:12 uefi avahi-daemon[703]: Leaving mDNS multicast group on interface eth0.IPv6 with address fe80::baca:3aff:febe:c618. Feb 22 09:21:12 uefi avahi-daemon[703]: Interface eth0.IPv6 no longer relevant for mDNS. Then, network manager start again, in a loop, without obtaining the address. Ths only solution I found is to execute thwse two commands (in this order): # systemctl restart NetworkManager.service # systemctl restart networking.service then, eth0 get the address via DHCP and everything works. So, maybe, the solution is to added a dependency on networking.service in systemd unit file /lib/systemd/system/NetworkManager.service. Currently it contains this contraints: Wants=network.target After=network-pre.target dbus.service Before=network.target maybe, it should be changed in Wants=network.target After=network-pre.target dbus.service networking.service Before=network.target Bye, Giuseppe -- System Information: Debian Release: 9.0 APT prefers testing APT policy: (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.9.0-1-amd64 (SMP w/8 CPU cores) Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages network-manager depends on: ii adduser3.115 ii dbus 1.10.16-1 ii init-system-helpers1.47 ii libaudit1 1:2.6.7-1 ii libbluetooth3 5.43-1 ii
Bug#790355: hylafax: please make the build reproducible
Hello Chris, Il giorno dom, 14/08/2016 alle 10.30 +0100, Chris Lamb ha scritto: > Dear Maintainer, > > Source: hylafax > > Version: 3:6.0.6-6 > > Tags: patch > > There hasn't seem to be any update on this bug in 412 days, in which > time the Reproducible Builds effort has come on a long way. :) > > Would you consider applying this patch and uploading? I am working on a new upload. I hope to make it in a few weeks. Thanks, Giuseppe
Bug#808624: Invalid argument while starting daemon
Package: xen-hypervisor-4.4-amd64 Version: 4.4.1-9+deb8u3 Severity: important I just upgraded a machine used for hosting a few VM with Xen. The machine was running debian squeeze, so I updated to wheezy and then jessie. Xen is now version 4.4, cpu is 64 bits, dom0 is 32 bits userland with 64 bits kernel 3.16.0-4-amd64. Grub correctly load Xen and dom-0, in fact: # cd /sys/hypervisor/version; cat major minor extra 4 4 .1 During boot, Xen does not start. This is its status in systemd log: # systemctl status xen.service ● xen.service - LSB: Xen daemons Loaded: loaded (/etc/init.d/xen) Active: failed (Result: timeout) since lun 2015-12-21 15:34:04 CET; 38min ago Process: 28167 ExecStart=/etc/init.d/xen start (code=killed, signal=TERM) dic 21 15:29:04 centrum xenstored[28191]: Checking store ... dic 21 15:29:04 centrum xenstored[28191]: Checking store complete. dic 21 15:29:04 centrum xenstored[28191]: Checking store ... dic 21 15:29:04 centrum xenstored[28191]: Checking store complete. dic 21 15:29:04 centrum xen[28167]: Starting Xen daemons: xenstored xenconsoled init-dom0FATAL: Failed to initialize dom0 state: Inappropriate ioctl for device dic 21 15:34:04 centrum systemd[1]: xen.service start operation timed out. Terminating. dic 21 15:34:04 centrum systemd[1]: Failed to start LSB: Xen daemons. dic 21 15:34:04 centrum systemd[1]: Unit xen.service entered failed state. Log files in /var/log/xen aren't touched: no information has been printed there after debian upgrade. Some operation take forever, like centrum:/tmp# time xenstore-write "/local/domain/0/name" "Domain-0" (never return: I killed it after 30 minutes) and this xenstore-write command that take forever is the reason for systemd setting the status as "timeout". How may I solve, or better debug, this problem? Thank you very much, Giuseppe
Bug#804778: evolution-dbg seems not working
Package: evolution-dbg Version: 3.18.1-1 Severity: important I opened a bug upstream, and I am asked about providing information on an evolution SIGSEGV, so I installed all evolution*-dbg packages and run evolution via gdb. The problem is that gdb command "bt full" does not correctly show files and line numbers. More information is available at https://bugzilla.gnome.org/show_bug.cgi?id=757789 Thanks, Giuseppe P.S. Should I reassign this bug report against evolution source package?
Bug#786514: hylafax-client-dbg: hylafax regression - sending broken since upgrade to jessie
Hello Herrmann, with wheezy, were you using users with password stored in hosts.hfaxd? Was this file changed during upgrade? Could you please send output of command ls -l /etc/hylafax/ Otherwise, if you are using PAM, please provide output of command cat /etc/pam.d/hylafax Thanks, Giuseppe -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#786514: hylafax-client-dbg: hylafax regression - sending broken since upgrade to jessie
This is rather interesting: so you are telling me that users may connect without any problem, but they get an error only when sending faxes. I believe that your client uses the same FTP like protocol for sending and receiving faxes. So I would say that this is not an authentication problem. Moreover, according to your hosts.hfaxd, you are using IP authentication, without any password request, so the message you are seeing in syslog is misleading, just ignore it. Since you say that the problem is a message about wrong password, and since you may reproduce it even using sendfax, I would like to ask you to make another test and send me its output. Just try to send a FAX in verbose mode: sendfax -a 'now + 1 hour' -i test-hylafax -k 'now + 2 minutes' -vv -d 999888777 /etc/issue Bye, Giuseppe -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#778772: Changelogs shown do not include a correct charset for displaying them
Package: tracker.debian.org Severity: normal Hello, while displaying changelog from the web interface I see that many characters are not shown correctly because they have a different charset than browser default. Could you please specify the (utf8) charset in the HTTP response or elsewhere? Thanks, Giuseppe -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#777499: shotwell: uses 100% cpu for minutes at startup on a recent cpu
tags 777499 - moreinfo thanks Hi Jörg, these are the answers for your questions, I believe: giuseppe@uefi:~$ ls -l .local/share/shotwell/data/photo.db -rw-r--r-- 1 giuseppe giuseppe 29169664 feb 8 21:46 .local/share/shotwell/data/photo.db giuseppe@uefi:~$ sqlite3 .local/share/shotwell/data/photo.db select count(*) from PhotoTable; 88212 Thanks for working on this subject. Bye, Giuseppe signature.asc Description: This is a digitally signed message part
Bug#777499: shotwell: uses 100% cpu for minutes at startup on a recent cpu
Package: shotwell Version: 0.20.1-1 Severity: important Dear Maintainer, I loaded a large photo collection on shotwell and now it become almost useless since it takes really a lot of time to startup. Moreover it seems that while being at 95% (this is the progress bar status where it stay for about 80 seconds when the program starts) it uses 100% cpu. After about 80 seconds at 95%, it jumps to 99% and keep using 100% cpu for about 30 seconds. I tried to run it via gdb after installing all -dbg packages (for shotwell and dependancies) and, if I press control-c during the 100% cpu usage, I always get this backtrace: (gdb) bt #0 0x77b8cfac in gee_tree_set_check_subtree (node=0x6403ba90, self=0x63d3bbc0) at treeset.c:2561 #1 gee_tree_set_check_subtree (self=0x63d3bbc0, node=0x6403bc10) at treeset.c:2578 #2 0x77b8cf01 in gee_tree_set_check_subtree (node=0x6403b130, self=0x63d3bbc0) at treeset.c:2582 #3 gee_tree_set_check_subtree (self=0x63d3bbc0, node=0x6403be90) at treeset.c:2578 #4 0x77b8cef2 in gee_tree_set_check_subtree (node=0x6403e520, self=0x63d3bbc0) at treeset.c:2578 #5 gee_tree_set_check_subtree (self=0x63d3bbc0, node=0x64040ea0) at treeset.c:2578 #6 0x77b8cef2 in gee_tree_set_check_subtree (node=0x64047b20, self=0x63d3bbc0) at treeset.c:2578 #7 gee_tree_set_check_subtree (self=0x63d3bbc0, node=0x64054c90) at treeset.c:2578 #8 0x77b8d0b1 in gee_tree_set_check_subtree (node=0x6403ac10, self=0x63d3bbc0) at treeset.c:2582 #9 gee_tree_set_check_subtree (node=0x64070930, self=0x63d3bbc0) at treeset.c:2578 #10 gee_tree_set_check_subtree (self=0x63d3bbc0, node=0x640048a0) at treeset.c:2582 #11 0x77b8cf01 in gee_tree_set_check_subtree (node=0x63f32730, self=0x63d3bbc0) at treeset.c:2582 #12 gee_tree_set_check_subtree (self=0x63d3bbc0, node=0x640e4200) at treeset.c:2578 #13 0x77b8fa5c in gee_tree_set_check (self=0x63d3bbc0) at treeset.c:2502 #14 gee_tree_set_real_add (base=0x63d3bbc0, item=optimized out) at treeset.c:1335 #15 0x77b276ea in gee_abstract_multi_map_real_set (base=0x55ba3c10, key=optimized out, value=0x5bc3fda0) at abstractmultimap.c:998 #16 0x5580c0c0 in media_source_collection_real_notify_contents_altered (base=0x5bc3fda0, added=0x6403ba00, removed=0x1) at src/MediaDataRepresentation.c:3822 #17 0x557589b6 in library_photo_source_collection_real_notify_contents_altered (base=0x118, added=0x6403ba00, removed=0x1) at src/Photo.c:22748 #18 0x5566854b in data_collection_real_add_many (self=0x55bfa440, objects=optimized out, monitor=0x0, monitor_target=0x0) at src/core/DataCollection.c:1013 #19 0x55759800 in library_photo_init (monitor=0x556ea0b0 _aggregate_progress_monitor_monitor_progress_monitor, monitor_target=0x560dd4d0) at src/Photo.c:24846 #20 0x556eaf0e in library_exec (mounts=0x55bad3d0, mounts_length1=0) at src/main.c:1100 #21 0x556eb9f8 in _vala_main (args=0x7fffe268, args_length1=1) at src/main.c:1964 #22 0x555db560 in main (argc=optimized out, argv=optimized out) at src/main.c:2046 (gdb) I do not know if media_source_collection_real_notify_contents_altered() calls many time libgee, or if gee_abstract_multi_map_real_set is just called once, but this seems to be where the problem is. Do you have any suggestion in order to better trace the problem? Thanks, Giuseppe -- System Information: Debian Release: 8.0 APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/8 CPU cores) Locale: LANG=it_IT.utf8, LC_CTYPE=it_IT.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages shotwell depends on: ii dbus-x111.8.12-3 ii libatk1.0-0 2.14.0-1 ii libc6 2.19-13 ii libcairo-gobject2 1.14.0-2.1 ii libcairo2 1.14.0-2.1 ii libexif12 0.6.21-2 ii libgdk-pixbuf2.0-0 2.31.1-2+b1 ii libgee-0.8-20.16.1-1 ii libgexiv2-2 0.10.2-2 ii libglib2.0-02.42.1-1 ii libgomp14.9.1-19 ii libgphoto2-62.5.4-1.1+b2 ii libgphoto2-port10 2.5.4-1.1+b2 ii libgstreamer-plugins-base1.0-0 1.4.4-2 ii libgstreamer1.0-0 1.4.4-2 ii libgtk-3-0 3.14.5-1 ii libgudev-1.0-0 215-10 ii libjavascriptcoregtk-3.0-0 2.4.8-1 ii libjson-glib-1.0-0 1.0.2-1 ii liblcms2-2 2.6-3+b3 ii libpango-1.0-0 1.36.8-3 ii libpangocairo-1.0-0 1.36.8-3 ii libraw100.16.0-9+b1 ii
Bug#767673: fglrx-driver: gnome-session fails to start. Major opcode 141 (RANDR) Minor opcode 13 (RRChangeOutputProperty).
Hello, I think the problem is in clutter package: when gnome-shell starts, it load the cogl library in order to manage the screen. This library include a few drivers and select the best one based on some heuristic (based on the GL engine found). When running fglrx, the cogl library uses the GLES2 driver. This driver start checking the GL engine and stop when testing the RRChangeOutputProperty. If you want to easily reproduce the problem, just start X11 (I use an xfce4 desktop) and then execute this command in an xterm: env COGL_DEBUG=all COGL_DRIVER=gles2 LIBGL_DEBUG=verbose \ MESA_DEBUG=1 gnome-shell --replace This will try to start gnome-shell and then fail. Its output is: giuseppe@uefi:~$ env COGL_DEBUG=all COGL_DRIVER=gles2 LIBGL_DEBUG=verbose MESA_DEBUG=1 gnome-shell --replace Cogl-Message: [WINSYS] ./cogl-xlib-renderer.c:410 Outputs: Cogl-Message: [WINSYS] ./cogl-xlib-renderer.c:449 LVDS: +0+0x1920x1080 mm=344x194 dpi=141,8x141,4 subpixel_order=horizontal_rgb refresh_rate=60,006 Cogl-Message: [WINSYS] ./cogl-xlib-renderer.c:410 Outputs: Cogl-Message: [WINSYS] ./cogl-xlib-renderer.c:449 LVDS: +0+0x1920x1080 mm=344x194 dpi=141,8x141,4 subpixel_order=horizontal_rgb refresh_rate=60,006 libEGL warning: DRI2: failed to authenticate libGL: Can't open configuration file /home/giuseppe/.drirc: File o directory non esistente. libGL: Can't open configuration file /home/giuseppe/.drirc: File o directory non esistente. Cogl-Message: [WINSYS] ./winsys/cogl-winsys-egl.c:181EGL Extensions: EGL_MESA_configless_context EGL_KHR_surfaceless_context Cogl-Message: [WINSYS] ./winsys/cogl-winsys-egl.c:181EGL Extensions: EGL_MESA_configless_context EGL_KHR_surfaceless_context Cogl-Message: [WINSYS] ./driver/gl/gles/cogl-driver-gles.c:275 Checking features GL_VENDOR: VMware, Inc. GL_RENDERER: Gallium 0.4 on llvmpipe (LLVM 3.5, 256 bits) GL_VERSION: OpenGL ES 3.0 Mesa 10.3.2 GL_EXTENSIONS: GL_EXT_blend_minmax GL_EXT_multi_draw_arrays GL_EXT_texture_compression_dxt1 GL_EXT_texture_format_BGRA GL_OES_compressed_ETC1_RGB8_texture GL_OES_depth24 GL_OES_element_index_uint GL_OES_fbo_render_mipmap GL_OES_mapbuffer GL_OES_rgb8_rgba8 GL_OES_standard_derivatives GL_OES_stencil8 GL_OES_texture_3D GL_OES_texture_npot GL_OES_EGL_image GL_OES_depth_texture GL_OES_packed_depth_stencil GL_EXT_texture_type_2_10_10_10_REV GL_OES_get_program_binary GL_APPLE_texture_max_level GL_EXT_discard_framebuffer GL_EXT_read_format_bgra GL_NV_fbo_color_attachments GL_OES_EGL_image_external GL_OES_vertex_array_object GL_ANGLE_texture_compression_dxt3 GL_ANGLE_texture_compression_dxt5 GL_EXT_texture_rg GL_EXT_unpack_subimage GL_NV_draw_buffers GL_NV_read_buffer GL_EXT_map_buffer_range GL_OES_depth_texture_cube_map GL_OES_surfaceless_context GL_EXT_color_buffer_float GL_EXT_separate_shader_objects GL_EXT_shader_integer_mix Cogl-Message: [WINSYS] ./cogl-gpu-info.c:569 Driver package = Unknown, vendor = Mesa, architecture = LLVM Pipe cogl_matrix_init_identity: Matrix type: COGL_MATRIX_TYPE_IDENTITY, flags: 400 1,00 0,00 0,00 0,00 0,00 1,00 0,00 0,00 0,00 0,00 1,00 0,00 0,00 0,00 0,00 1,00 Inverse: - not available cogl_matrix_init_identity: Matrix type: COGL_MATRIX_TYPE_IDENTITY, flags: 400 1,00 0,00 0,00 0,00 0,00 1,00 0,00 0,00 0,00 0,00 1,00 0,00 0,00 0,00 0,00 1,00 Inverse: - not available cogl_matrix_init_identity: Matrix type: COGL_MATRIX_TYPE_IDENTITY, flags: 400 1,00 0,00 0,00 0,00 0,00 1,00 0,00 0,00 0,00 0,00 1,00 0,00 0,00 0,00 0,00 1,00 Inverse: - not available cogl_matrix_scale: Matrix type: DIRTY, flags: 510 1,00 -0,00 0,00 0,00 0,00 -1,00 0,00 0,00 0,00 -0,00 1,00 0,00 0,00 -0,00 0,00 1,00 Inverse: - not available cogl_matrix_init_identity: Matrix type: COGL_MATRIX_TYPE_IDENTITY, flags: 400 1,00 0,00 0,00 0,00 0,00 1,00 0,00 0,00 0,00 0,00 1,00 0,00 0,00 0,00 0,00 1,00 Inverse: - not available cogl_matrix_frustum: Matrix type: DIRTY, flags: 540 1,299038 0,00 0,00 0,00 0,00 1,732051 0,00 0,00 0,00 0,00 -1,002002 -0,200200 0,00 0,00 -1,00 0,00 Inverse: - not available cogl_matrix_perspective: Matrix type: DIRTY, flags: 540 1,299038 0,00 0,00 0,00 0,00 1,732051 0,00 0,00 0,00 0,00 -1,002002 -0,200200 0,00 0,00 -1,00 0,00 Inverse: - not available cogl_matrix_init_from_array: Matrix type: DIRTY, flags: 701 0,769800 0,00
Bug#772084: unblock: hylafax/3:6.0.6-6
Package: release.debian.org
User: release.debian@packages.debian.org
Usertags: unblock
Severity: normal
Please unblock package hylafax
I uploaded version 3:6.0.6-6 of hylafax and would like to have it
accepted in jessie. The changes between the version in jessie
(3:6.0.6-5) and the one just uploaded in unstable only fix an RC bug:
#768840: hylafax-server: removes files that were installed by another
package: /var/spool/hylafax/{bin, etc}
The fix is in a postrm script. diff between jessie and unstable version
is:
--- hylafax-6.0.6-5/debian/hylafax-server.postrm2013-03-10
18:14:49.0 +0100
+++ hylafax-6.0.6-6/debian/hylafax-server.postrm2014-12-04
22:34:47.0 +0100
@@ -9,11 +9,6 @@
then
[ -x $USERDEL ] $USERDEL faxmaster
fi
-#
-# This will remove the directory that holds a copy of the real
-# debian configuration in /etc/hylafax
-[ -d /var/spool/hylafax/etc ] rm -rf /var/spool/hylafax/etc
-[ -L /var/spool/hylafax/bin ] rm /var/spool/hylafax/bin
for i in /etc/hylafax/setup.cache /etc/hylafax/setup.modem \
/var/spool/hylafax/status/any.info /var/spool/hylafax/dev/null \
@@ -23,8 +18,6 @@
do
[ -e $i -o -L $i ] rm $i
done
-
-[ -d /var/spool/hylafax/bin ] rmdir --ignore-fail-on-non-empty
/var/spool/hylafax/bin
fi
exit 0
and is documented in changelog as this:
+hylafax (3:6.0.6-6) unstable; urgency=medium
+
+ * Don't remove files managed by dpkg when purging package.
+
+ -- Giuseppe Sacco eppes...@debian.org Thu, 04 Dec 2014 22:47:58 +0100
+
Thank you,
Giuseppe
unblock hylafax/3:6.0.6-6
-- System Information:
Debian Release: jessie/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.16.0-4-amd64 (SMP w/8 CPU cores)
Locale: LANG=it_IT.utf8, LC_CTYPE=it_IT.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#770875: Sponsorship for saga package
Hi Johan, I checked your package and I am willing to sponsor its upload. I noticed that you are not accepting parallel building. Is this done on purpose? Just for testing it, I added --parallel the the first dh command in debian/rules and build time went from 18 to about 7 minutes when running dpkg-buildpackage with -j8 option on amd64 arch. I would not change your package now, but I suggest you to investigate if with a parallel build the resulting package is ok or if anything is wrong. In a next version you might then add this option. Would you like me to upload your package, or have you already another sponsor or a different planning? Bye, Giuseppe -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#763279: vlc: src/searching.c:566: dvdnav_get_position: asserzione (signed)*pos != -1 non riuscita.
Package: libdvdnav Version: 5.0.1-1 Severity: important Hi Debian Multimedia Maintainers, while trying to play a DVD I got this error message: ~$ vlc VLC media player 2.1.5 Rincewind (revision 2.1.4-49-gdab6cb5) [0xf71458] main libvlc: Esecuzione di vlc con l'interfaccia predefinita. Usa 'cvlc' per utilizzare vlc senza interfaccia. libdvdnav: Using dvdnav version 5.0.1 libdvdnav: DVD disk reports itself with Region mask 0x00fd. Regions: 2 [...] Fontconfig warning: FcPattern object size does not accept value 0 Fontconfig warning: FcPattern object size does not accept value 0 [0x7fc9c0001248] main vout display error: Failed to resize display [0x7fc9dc0009b8] main input error: ES_OUT_RESET_PCR called Fontconfig warning: FcPattern object size does not accept value 0 Fontconfig warning: FcPattern object size does not accept value 0 vlc: src/searching.c:566: dvdnav_get_position: asserzione (signed)*pos != -1 non riuscita. Annullato I browsed a little bit on the network in order to find information about this problem, and I found that in ubuntu there seems to be a fix already committed but not yet included in a package. Please see https://bugs.launchpad.net/ubuntu/+source/libdvdnav/+bug/1236939 It seems this will be fixed in 5.0.2, but since Debian is approaching a freeze, I hope the fix could be backported now to 5.0.1. Bye, Giuseppe -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#758994: Can't install package because Unit virtlockd.service cannot be reloaded because it is inactive
Package: libvirt-daemon-system Version: 1.2.7-10+b1 Severity: important Today I updated my Jessie machine and got this error: giuseppe@blatta:~$ sudo env LANG=C apt-get -f install [...] Setting up libvirt-daemon-system (1.2.7-10+b1) ... Job for virtlockd.service failed. See 'systemctl status virtlockd.service' and 'journalctl -xn' for details. dpkg: error processing package libvirt-daemon-system (--configure): subprocess installed post-installation script returned error exit status 1 dpkg: dependency problems prevent configuration of libvirt-bin: libvirt-bin depends on libvirt-daemon-system (= 1.2.7-10+b1); however: Package libvirt-daemon-system is not configured yet. dpkg: error processing package libvirt-bin (--configure): dependency problems - leaving unconfigured Errors were encountered while processing: libvirt-daemon-system libvirt-bin E: Sub-process /usr/bin/dpkg returned an error code (1) As you may see, package cannot be configured and stopped the machine upgrade. More information, as suggested by the error message, are: giuseppe@blatta:~$ env LANG=C systemctl status virtlockd.service virtlockd.service - Virtual machine lock manager Loaded: loaded (/lib/systemd/system/virtlockd.service; static) Active: inactive (dead) Docs: man:virtlockd(8) http://libvirt.org Aug 23 17:32:14 blatta systemd[1]: Unit virtlockd.service cannot be reloaded because it is inactive. Aug 23 17:32:42 blatta systemd[1]: Unit virtlockd.service cannot be reloaded because it is inactive. Aug 23 17:32:48 blatta systemd[1]: Unit virtlockd.service cannot be reloaded because it is inactive. Aug 23 17:35:03 blatta systemd[1]: Unit virtlockd.service cannot be reloaded because it is inactive. giuseppe@blatta:~$ env LANG=C journalctl -xn -- Logs begin at Sat 2014-08-23 17:00:42 CEST, end at Sat 2014-08-23 17:35:11 CEST. -- Aug 23 17:33:42 blatta pcscd[12247]: 0008 readerfactory.c:1046:RFInitializeReader() Open Port 0x20 Failed (usb:0a5c/5802:libudev:0:/dev/bus/usb/ Aug 23 17:33:42 blatta pcscd[12247]: 0003 readerfactory.c:338:RFAddReader() Broadcom Corp 5880 [Broadcom USH w/touch sensor] (0123456789ABCD) init f Aug 23 17:35:01 blatta CRON[12354]: pam_unix(cron:session): session opened for user root by (uid=0) Aug 23 17:35:01 blatta /USR/SBIN/CRON[12355]: (root) CMD (command -v debian-sa1 /dev/null debian-sa1 1 1) Aug 23 17:35:01 blatta CRON[12354]: pam_unix(cron:session): session closed for user root Aug 23 17:35:02 blatta sudo[12357]: giuseppe : TTY=pts/0 ; PWD=/home/giuseppe ; USER=root ; COMMAND=/usr/bin/env LANG=C apt-get -f install Aug 23 17:35:02 blatta sudo[12357]: pam_unix(sudo:session): session opened for user root by giuseppe(uid=0) Aug 23 17:35:03 blatta systemd[1]: Unit virtlockd.service cannot be reloaded because it is inactive. Aug 23 17:35:03 blatta sudo[12357]: pam_unix(sudo:session): session closed for user root Aug 23 17:35:11 blatta pcscd[12247]: 88578856 commands.c:1068:CmdPowerOff Card absent or mute Bye, Giuseppe -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#758875: A few bugs from the very first usage in Italian
Package: lyx Version: 2.0.6-1+b2 Hello, I just installed LyX and had a first look at its welcome page, i.e., the content shown when you run it without arguments. My user is in Italian, so I got an Italian document. The first problem is that at point 3, the text suggest to check the menu ViewDVI in order to see how great it is the printed output, but I cannot see and DVI in the View menu. I think the correct menuitem is ViewDisplay(Other formats)DVI or ViewPDF. The second problem is that selecting any of the mentioned menuitem, I get a box that display this error message: ...ry to proceed from here, type x to quit.} You need to specify a language, either as a global option or as an optional argument to the \usepackage command; You shouldn't try to proceed from here, type x to quit. So, I cannot see any printed document. The third problem is in the Italian translation, still at point 3 of the list shown in the document, the word constatrlo should be constatarlo. Moreover, the welcome page says that the menu is called View (as in the English GUI probably), while the real menu is called Vista. All other references to menu names are correctly translated into Italian and match the real menu names. Bye, Giuseppe -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#739443: This package include ATI drivers in beta
Hi all, from what I understood, this driver is shipped by AMD as a beta version. Would it be possibile to have a Debian package with the latest AMD stable driver, as well? Thanks, Giuseppe -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#741332: glx does not work anymore
Package: fglrx-driver Version: 1:14.2~beta1.3-1 Severity: important Hi Fglrx packaging team, since latest package upgrade, my ATI video card does not work any more correctly. This is what happen: giuseppe@blatta:~$ fglrxinfo X Error of failed request: BadRequest (invalid request code or no such operation) Major opcode of failed request: 155 (GLX) Minor opcode of failed request: 19 (X_GLXQueryServerString) Serial number of failed request: 12 Current serial number in output stream: 12 In Xorg.0.log I see: [ 15083.502] (II) glx will be loaded by default. [ 15083.502] (II) LoadModule: glx [ 15083.502] (II) Loading /usr/lib/xorg/modules/linux/libglx.so [ 15083.503] (II) Module glx: vendor=Advanced Micro Devices, Inc. [ 15083.503]compiled for 6.9.0, module version = 1.0.0 [ 15083.504] Loading extension GLX [ 15083.504] (==) Matched ati as autoconfigured driver 0 [ 15083.504] (==) Matched modesetting as autoconfigured driver 1 [ 15083.504] (==) Matched fbdev as autoconfigured driver 2 [ 15083.504] (==) Matched vesa as autoconfigured driver 3 [ 15083.504] (==) Assigned the driver to the xf86ConfigLayout and the libglx should be the right one: giuseppe@blatta:~$ ls -l /usr/lib/xorg/modules/linux/libglx.so \ /etc/alternatives/glx--linux-libglx.so /usr/lib/fglrx/fglrx-libglx.so lrwxrwxrwx 1 root root 30 feb 12 11:53 /etc/alternatives/glx--linux-libglx.so - /usr/lib/fglrx/fglrx-libglx.so -rw-r--r-- 1 root root 579920 feb 28 13:30 /usr/lib/fglrx/fglrx-libglx.so lrwxrwxrwx 1 root root 38 feb 12 11:53 /usr/lib/xorg/modules/linux/libglx.so - /etc/alternatives/glx--linux-libglx.so My xorg.conf file is attached. Thank you very much, Giuseppe Section ServerLayout Identifier Layout di base Screen 0 DELL Precision M4700 0 0 EndSection Section Module EndSection Section InputClass Identifier TouchPad DELL Precision M4700 Driver synaptics MatchIsTouchpad yes Option Protocol auto-dev Option SHMConfig on Option LeftEdge 110 Option RightEdge 1930 Option TopEdge 150 Option BottomEdge 1400 Option PressureMotionMinZ 25 Option PressureMotionMaxZ 50 Option EdgeMotionMinZ 25 Option EdgeMotionMaxZ 50 Option TapButton1 1 Option TapButton2 3 Option VertTwoFingerScroll 1 Option HorizTwoFingerScroll 1 EndSection Section Monitor Identifier CMN 5553 DisplaySize 344194 Option VendorName CMN Option ModelName 15b1 Option DPMS true EndSection Section Device Identifier AMD Radeon HD 7700M Series Driver fglrx BusID PCI:1:0:0 EndSection Section Screen Identifier DELL Precision M4700 Device AMD Radeon HD 7700M Series MonitorCMN 5553 DefaultDepth 24 SubSection Display Viewport 0 0 Depth 24 EndSubSection EndSection
Bug#727790: rhythmbox: Trace/breakpoint trap while listing songs from remote server
Package: rhythmbox Version: 3.0-1 Severity: normal Dear Maintainer, the program quit while listing songs from a remote server. I traced the program using gdb after installing the -dbg package. This is the final output [] (rhythmbox:16723): libsoup-WARNING **: (soup-uri.c:221):soup_uri_new_with_base: runtime check failed: (SOUP_URI_IS_VALID (base)) [New Thread 0x7fff990ec700 (LWP 16875)] [Thread 0x7fff990ec700 (LWP 16875) exited] (rhythmbox:16723): libsoup-WARNING **: (soup-uri.c:221):soup_uri_new_with_base: runtime check failed: (SOUP_URI_IS_VALID (base)) [New Thread 0x7fff988eb700 (LWP 16876)] (rhythmbox:16723): GLib-GObject-WARNING **: value -1,00 of type `gdouble' is invalid or out of range for property `task-progress' of type `gdouble' [Thread 0x7fff988eb700 (LWP 16876) exited] (rhythmbox:16723): libsoup-WARNING **: (soup-uri.c:221):soup_uri_new_with_base: runtime check failed: (SOUP_URI_IS_VALID (base)) [New Thread 0x7fff980ea700 (LWP 16877)] (rhythmbox:16723): GLib-GObject-WARNING **: value -1,00 of type `gdouble' is invalid or out of range for property `task-progress' of type `gdouble' [Thread 0x7fff980ea700 (LWP 16877) exited] (rhythmbox:16723): GLib-GIO-ERROR **: Schema 'org.gnome.rhythmbox.source' has no child 'source' Program received signal SIGTRAP, Trace/breakpoint trap. 0x7fffeffb7e8d in g_logv () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 (gdb) bt #0 0x7fffeffb7e8d in g_logv () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7fffeffb8072 in g_log () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7115b14d in g_settings_get_child () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 #3 0x7fffce0a007d in rb_daap_source_connection_cb (connection=optimized out, result=1, reason=0x0, source=0xb41b20) at rb-daap-source.c:642 #4 0x7fffcde71b98 in ?? () from /usr/lib/libdmapsharing-3.0.so.2 #5 0x70278157 in ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #6 0x70290248 in g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #7 0x70290f32 in g_signal_emit () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #8 0x7fffcde7260a in ?? () from /usr/lib/libdmapsharing-3.0.so.2 #9 0x7fffeffb0ea6 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #10 0x7fffeffb11f8 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #11 0x7fffeffb129c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #12 0x711486e4 in g_application_run () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 #13 0x77ad6ba2 in rb_application_run (app=0x61c000, argc=argc@entry=1, argv=argv@entry=0x7fffe2c8) at rb-application.c:646 #14 0x00400f82 in main (argc=1, argv=0x7fffe2c8) at main.c:95 Thanks, Giuseppe -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.10-3-amd64 (SMP w/8 CPU cores) Locale: LANG=it_IT.utf8, LC_CTYPE=it_IT.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages rhythmbox depends on: ii dbus1.6.16-1 ii gnome-icon-theme3.8.3-1 ii gstreamer1.0-plugins-base 1.2.0-1 ii gstreamer1.0-plugins-good 1.2.0-1 ii gstreamer1.0-x 1.2.0-1 ii libatk1.0-0 2.10.0-2 ii libc6 2.17-93 ii libcairo-gobject2 1.12.16-2 ii libcairo2 1.12.16-2 ii libgdk-pixbuf2.0-0 2.28.2-1 ii libgirepository-1.0-1 1.36.0-2+b1 ii libglib2.0-02.36.4-1 ii libgstreamer-plugins-base1.0-0 1.2.0-1 ii libgstreamer1.0-0 1.2.0-1 ii libgtk-3-0 3.8.4-1 ii libgudev-1.0-0 204-5 ii libice6 2:1.0.8-2 ii libjavascriptcoregtk-3.0-0 2.2.0-2 ii libjson-glib-1.0-0 0.16.2-1 ii libnotify4 0.7.6-1 ii libpango-1.0-0 1.32.5-5+b1 ii libpangocairo-1.0-0 1.32.5-5+b1 ii libpeas-1.0-0 1.8.1-1 ii librhythmbox-core8 3.0-1 ii libsm6 2:1.2.1-2 ii libsoup-gnome2.4-1 2.42.2-6 ii libsoup2.4-12.42.2-6 ii libtdb1 1.2.12-1 ii libtotem-plparser17 3.4.5-1 ii libwebkitgtk-3.0-0 2.2.0-2 ii libx11-62:1.6.2-1 ii libxml2 2.9.1+dfsg1-3 ii media-player-info 19-1 ii rhythmbox-data 3.0-1 ii zlib1g 1:1.2.8.dfsg-1 Versions of packages rhythmbox recommends: ii avahi-daemon 0.6.31-2 ii gstreamer1.0-plugins-ugly 1.2.0-1 ii gstreamer1.0-pulseaudio1.2.0-1 ii gvfs-backends 1.16.3-1+b1 ii notification-daemon
Bug#721312: evolution will not start
It seems that message The OpenGL version could not be determined is part of a different package named cogl and providing a library (libcogl.so.12) used by evolution. May the bug should be reassigned to that package? Bye, Giuseppe
Bug#722161: COGL does not work with fglrx
Package: libcogl12 Version: 1.14.0-3 Severity: important Hi Rico, today, after upgrading from stable to testing, a few gnome programs stopped working. Since one of them is evolution, I googled about the problem and found an already opened bug (see #721312). After debugging a little bit, I found that the error message The OpenGL version could not be determined is emitted by the libcogl12 library. The reason of the error message is in source file cogl/cogl-context.c, in function _cogl_context_get_gl_version (CoglContext *context) because function call context-glGetString (GL_VERSION) returns NULL. I do not think the problem is just on that function call, since even avoiding it by the use of COGL_OVERRIDE_GL_VERSION variable, all programs eventually segfaults. As in: giuseppe@blatta:/tmp/cogl-1.14.0$ sudo tail -f /var/log/syslog giuseppe@blatta:/tmp/cogl-1.14.0$ COGL_OVERRIDE_GL_VERSION=1.4 cheese (cheese:11268): GLib-CRITICAL **: g_strsplit: assertion `string != NULL' failed Sep 8 17:31:15 blatta kernel: [ 2608.342244] cheese[11268]: segfault at 0 ip 7fba4ff424cc sp 7fff87ffceb0 error 4 in libcogl.so.12.1.1[7fba4ff11000+97000] Errore di segmentazione or giuseppe@blatta:/tmp/cogl-1.14.0$ COGL_OVERRIDE_GL_VERSION=1.4 evolution (evolution:11274): GLib-CRITICAL **: g_strsplit: assertion `string != NULL' failed Sep 8 17:31:58 blatta kernel: [ 2651.672205] evolution[11274]: segfault at 0 ip 7f0db84b64cc sp 7fff308feda0 error 4 in libcogl.so.12.1.1[7f0db8485000+97000] Errore di segmentazione These are my GLX information: giuseppe@blatta:/tmp/cogl-1.14.0$ fglrxinfo display: :0 screen: 0 OpenGL vendor string: Advanced Micro Devices, Inc. OpenGL renderer string: AMD Radeon HD 7700M Series OpenGL version string: 4.3.12438 Compatibility Profile Context FireGL 8.982.13 giuseppe@blatta:/tmp/cogl-1.14.0$ glxinfo | head -14 name of display: :0 display: :0 screen: 0 direct rendering: Yes server glx vendor string: ATI server glx version string: 1.4 server glx extensions: GLX_ARB_multisample, GLX_EXT_import_context, GLX_EXT_texture_from_pixmap, GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_OML_swap_method, GLX_SGI_make_current_read, GLX_SGI_swap_control, GLX_SGIS_multisample, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, GLX_SGIX_visual_select_group client glx vendor string: ATI client glx version string: 1.4 client glx extensions: GLX_ARB_create_context, GLX_ARB_create_context_profile, I am unable to keep investigaing on this subject right now, but if you need any test by my side on this machine, just let me know. Thanks, Giuseppe -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.10-2-amd64 (SMP w/8 CPU cores) Locale: LANG=it_IT.utf8, LC_CTYPE=it_IT.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages libcogl12 depends on: ii libc6 2.17-92+b1 ii libegl1-mesa [libegl1-x11] 9.1.6-2 ii libgdk-pixbuf2.0-0 2.28.2-1 ii libgl1-mesa-glx 9.1.6-2 ii libglib2.0-02.36.4-1 ii libx11-62:1.6.1-1 ii libxcomposite1 1:0.4.4-1 ii libxdamage1 1:1.1.4-1 ii libxext62:1.3.2-1 ii libxfixes3 1:5.0.1-1 ii libxrandr2 2:1.4.1-1 ii multiarch-support 2.17-92+b1 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#719130: hylafax: wrong subject in some failure messages
Hi Ben, When mailing results from recieved faxes some but not all failures have a subject line that indicates success. See attached email for sample. What subject would you write instead of Fax received from ? Thanks, Giuseppe -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#529629: Add a note about ext3 option data change from ordered to writeback
Hi David, Il giorno sab, 30/03/2013 alle 12.27 -0400, David Prévot ha scritto: [...] Starting with 2.6.30 kernels, ext3 default mount option is now data=writeback instead of data=ordered. If you have data=ordered in /etc/fstab then you will not be able to mount read/write your file system after upgrading kernel from 2.6.29. Thanks for reporting this. From what I understand, this will have to be mentioned in the Squeeze release notes. Is this issue still relevant for Wheezy? I suspect it isn’t and advise the RN wizard to close it (I may do so myself next time I come across this bug report unless more information is provided). Could you please better explain what kind of more information do you request? The bug report is still valid since squeeze release notes were never updated in order to mention it and its workaround. It might not be releant for wheezy since the default squeeze kernel is 2.6.30, but this does not means that this bug should be closed: it must stay opened at least as a reference for people upgrading from squeeze. Bye, Giuseppe -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#694276: hylafax-server: Expects sendmail in /usr/lib/sendmail
Hi Simon, Il giorno dom, 25/11/2012 alle 15.18 +0100, Giuseppe Sacco ha scritto: Hi Simon, Il giorno dom, 25/11/2012 alle 01.25 +, Simon Richter ha scritto: [...] when installing hylafax-server, the postinst complains about a lack of /usr/lib/sendmail. As sendmail lives in /usr/sbin/sendmail, according to policy, this should be changed (breaks with current citadel-mta). As far as I know, all MTA need to include both /usr/sbin/sendmail and /usr/lib/sendmail. Pleae have a look at http://release.debian.org/wheezy/rc_policy.txt, point 5 (General), letter l (Mail). I am not an expert of MTA, and I never heard of citadel-mta, so I cannot better check about it. Could you please verify that it is an MTA providing all required commands? do you have any news about this report? Thanks, Giuseppe -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#685230: unblock hylafax 3:6.0.6-4
Hi Julien, Il giorno ven, 01/03/2013 alle 11.31 +0100, Julien Cristau ha scritto: On Fri, Mar 1, 2013 at 08:00:27 +0100, Joachim Wiedorn wrote: [...] The next step is creating hylafax 6.0.6-5 as mentioned by Ivo De Decker. Should I already prepare these updated package of hylafax now? If possible, yes. The new hylafax version has been uploaded 5 days ago to unstable. The diff against the testing version are the ones already agreed upon, i.e., a very small subset of what was already in unstable. Could you please check if the package may be unblocked? Moreover, I checked the capi4hylafax package that is currently waiting for a pre approval requested on 28 January by Joachim Wiedorn, and I would gladly upload it after the approval. These two packages, if migrated to testing, would really be right ones for the next release. Thanks, Giuseppe -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#685230: unblock hylafax 3:6.0.6-4
Hi Joachim, Il 10/03/13 20.03, Joachim Wiedorn ha scritto: Hello Guiseppe, [...] I have already uploaded this package to mentors.d.n for sponsoring. Do you have time to review and sponsor this upload? If not I can write RFS. See: https://mentors.debian.net/package/hylafax I checked your package diff, rebuilt the package and tested it. Then I uploaded it, so hopefully it should enter unstable. Tomorrow I will also check capi4hylafax -19. If you still need a sponsor, I'll gladly upload the package. Thanks, Giuseppe -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#685230: unblock hylafax 3:6.0.6-4
Il giorno ven, 01/03/2013 alle 08.00 +0100, Joachim Wiedorn ha scritto: [...] The next step is creating hylafax 6.0.6-5 as mentioned by Ivo De Decker. Should I already prepare these updated package of hylafax now? I have been waiting for capi4hylafax being accepted, but now I think I'll package and upload hylafax 6.0.6-5 with only wheezy changes during this week end. The diff I'll use is almost what Ivo suggested in http://lists.debian.org/debian-release/2012/12/msg00886.html Bye, Giuseppe -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#661482: fixed in hylafax 3:6.0.6-2
Il giorno dom, 23/12/2012 alle 17.27 +0100, Ivo De Decker ha scritto: Hi Joachim, On Sat, Dec 22, 2012 at 10:44:31PM +0100, Joachim Wiedorn wrote: Ivo De Decker wrote on 2012-12-22 22:05: This is caused by this line in hylafax-server.postinst: chown uucp:uucp /var/spool/hylafax As this directory is also shipped by capi4hylafax, piuparts doesn't accept this. Then I see the only way that capi4hylafax check for this directory in postinst and only if it cannot be found it must be created, right? Well, for hylafax, /var/spool/hylafax should really be owned by uucp:uucp. So maybe the ownership of this dir should be changed in capi4hylafax, so that is also ships the directory with the same ownership. Then there is no conflict anymore. +1 for this proposal. Let's way a comment by Joachim. Bye, Giuseppe -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#695536: libpaper1: Does not configure properly on unitialized systems
[Please keep me in CC] Hi Debian TeX Maintainers, this new bug has been opened against libpaper, but since it is about texlive-base as well, I wonder if you can manage to explain what is happening. I may update libpaper in order to simply ignore errors in other package scripts, but I prefer to notify all package maintainers for fixing any problem. Il giorno dom, 09/12/2012 alle 22.44 +0100, Thomas Prokosch ha scritto: [...] libpaper1 does not configure properly on newly set up systems: I am using multistrap to build an ARM image from scratch on i386 hardware. However, during unpacking on the real ARM hardware with dpkg --configure -a, libpaper1 fails to unpack properly. The symptoms are as follows: dpkg output: === Setting up libpaper1:armhf (1.1.24+nmu2) ... Creating config file /etc/papersize with new version /usr/bin/tl-paper: setting paper size for dvipdfm to a4. Running mktexlsr. This may take some time... done. Building format(s) --refresh. This may take some time... fmtutil-sys failed. Output has been stored in /tmp/fmtutil.KI8wk5at Please include this file if you report a bug. run-parts: /etc/libpaper.d/texlive-base exited with return code 1 dpkg: error processing libpaper1:armhf (--configure): subprocess installed post-installation script returned error exit status 1 === The output of the mentioned file simply complains about the fact that the following file is missing from the file system: === /usr/share/texlive/texmf/texconfig/tcfmgr.map === Thank you very much, Giuseppe -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#695271: libpaper1: harmful purge action in M-A:same package
Thanks for pointing this out. [...] The postrm purge removes /etc/papersize. In a setting where you can purge libpaper1:i386 while still using libpaper1:amd64 this causes trouble. The bug is currently unreproducible due to ucf lacking M-A:foreign. As soon as ucf gains that flag, this bug is RC. What is the correct action sequence? When libpaper in i386 is purged while in amd64 is still installed, is there any already clarified documentation on how to act in those context? Should I make the purge fails or should I just remove the package without purging the configuration? What happen if, later on, the amd64 version is removed without purge? Should I remember the old purge request and purge the configuration at this later moment? And, in the opposite way, what if a first request of uninstall does not require to purge the configuration, while the second uninstall require to purge: should the second one really purge the configuration or should it keep it because of the first one requiring to keep it? Bye, Giuseppe -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#694276: hylafax-server: Expects sendmail in /usr/lib/sendmail
Hi Simon, Il giorno dom, 25/11/2012 alle 01.25 +, Simon Richter ha scritto: [...] when installing hylafax-server, the postinst complains about a lack of /usr/lib/sendmail. As sendmail lives in /usr/sbin/sendmail, according to policy, this should be changed (breaks with current citadel-mta). As far as I know, all MTA need to include both /usr/sbin/sendmail and /usr/lib/sendmail. Pleae have a look at http://release.debian.org/wheezy/rc_policy.txt, point 5 (General), letter l (Mail). I am not an expert of MTA, and I never heard of citadel-mta, so I cannot better check about it. Could you please verify that it is an MTA providing all required commands? Thanks, Giuseppe -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#692530: [regression] option -h of smbldap-usershow doesn't show non date fields
package: smbldap-tools version: 0.9.7-1 severity: important Hi, using smbldap-usershow username display all ldap attributes for the specified user name. Date fields are shown in integer form. Using the -h switch, date fields are shown as year/month/day. But now, when specifing -h all other fields are shown empty: # smbldap-usershow user | grep -v Password dn: uid=user,ou=People,dc=agenziaf27,dc=local objectClass: top,person,organizationalPerson,posixAccount,shadowAccount,inetOrgPerson,sambaSamAccount cn: Joe User sn: User uid: user uidNumber: 1025 gidNumber: 1012 homeDirectory: /home/user loginShell: /bin/bash gecos: Joe User givenName: Luca sambaLogonTime: 0 sambaLogoffTime: 2147483647 sambaKickoffTime: 2147483647 sambaPwdCanChange: 0 displayName: Joe User sambaSID: S-1-5-21-3226313530-99-1361587490-1037 sambaAcctFlags: [U] sambaPwdLastSet: 1351504942 sambaPwdMustChange: 1351418542 shadowLastChange: 15642 shadowMax: -1 # smbldap-usershow -h user | grep -v Password dn: uid=user,ou=People,dc=agenziaf27,dc=local objectClass: ,, cn: sn: uid: uidNumber: gidNumber: homeDirectory: loginShell: gecos: givenName: sambaLogonTime: sambaLogoffTime: 2038/1/19 sambaKickoffTime: 2038/1/19 sambaPwdCanChange: 1970/1/1 displayName: sambaSID: sambaAcctFlags: sambaPwdLastSet: 2012/10/29 sambaPwdMustChange: 2012/10/28 shadowLastChange: 2012/10/29 shadowMax: -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#691329: smbldap-grouplist fails: Can't use string (['gid','cn']) as an ARRAY ref while strict refs in use
package: smbldap-tools version: 0.9.7-1 severity: important On a wheezy box, with local ldap, I get this error message: # smbldap-grouplist Use of qw(...) as parentheses is deprecated at /usr/share/perl5/smbldap_tools.pm line 1423, DATA line 558. gid |cn | Can't use string (['gid','cn']) as an ARRAY ref while strict refs in use at /usr/share/perl5/Convert/ASN1/_encode.pm line 269. # I know the problem is in a file (_encode.pm) from a different package, but I *think* this is due to a call from smbldap-tools with wrong parameters. Bye, Giuseppe -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#682824: hylafax: needs update for wheezy
Hi Thijs, Il giorno dom, 14/10/2012 alle 16.00 +0200, Thijs Kinkhorst ha scritto: This security issue was fixed in unstable, thanks for that, but wheezy is still lacking the fix. This is because the unstable version cannot migrate due to it containing many auxilliary fixes. Could you coordinate with the release team to make an upload to testing-proposed-updates with the security fix? A few days ago I prepared a package for t-p-u. A diff that explain the package changes is already appended to the unblock request. See #685230. If you may check the diff and unblock the freeze exception, please do it. Thanks, Giuseppe -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#685230: unblock hylafax 3:6.0.6-4
Hi Cyril and Julien, this a diff from the version currently sitting in testing (6.0.6-1) and a possible upload to t-p-u (6.0.6-2~wheezy1). As you may see, I limited all changes to what is strictly required in order to fix two really important bugs already corrected in unstable. If you approve this, then I will upload the packages to t-p-u. Thanks, Giuseppe diff -ruN 6.0.6-1/debian/changelog 6.0.6-2~wheezy1/debian/changelog --- 6.0.6-1/debian/changelog2012-06-20 09:19:56.0 +0200 +++ 6.0.6-2~wheezy1/debian/changelog2012-10-13 00:12:55.0 +0200 @@ -1,3 +1,10 @@ +hylafax (3:6.0.6-2~wheezy1) testing-proposed-updates; urgency=high + + * Added restricted deletion flag on tmp directory (Closes: #682824) + * Update postinst and postrm scripts for hylafax-client (Closes: #661482) + + -- Giuseppe Sacco eppes...@debian.org Fri, 12 Oct 2012 22:02:09 + + hylafax (3:6.0.6-1) unstable; urgency=low * New upstream relase. Converted to 6.0 branch instead of 6.1 since the diff -ruN 6.0.6-1/debian/hylafax-client.postinst 6.0.6-2~wheezy1/debian/hylafax-client.postinst --- 6.0.6-1/debian/hylafax-client.postinst 2012-01-16 09:31:30.0 +0100 +++ 6.0.6-2~wheezy1/debian/hylafax-client.postinst 2012-10-12 23:55:15.0 +0200 @@ -38,6 +38,9 @@ ucf $newfile /etc/hylafax/pagesizes fi +# register config file with package name to ucf +ucfr hylafax-client /etc/hylafax/pagesizes + rm -f $newfile # diff -ruN 6.0.6-1/debian/hylafax-client.postrm 6.0.6-2~wheezy1/debian/hylafax-client.postrm --- 6.0.6-1/debian/hylafax-client.postrm2010-06-20 00:29:50.0 +0200 +++ 6.0.6-2~wheezy1/debian/hylafax-client.postrm2012-10-12 23:53:34.0 +0200 @@ -4,8 +4,9 @@ if [ $1 = purge ]; then [ -d /etc/hylafax ] rm -f /etc/hylafax/pagesizes -rmdir --ignore-fail-on-non-empty /etc/hylafax -if which ucf /dev/null 21; then - ucf --purge /etc/hylafax/pagesizes -fi +#rmdir --ignore-fail-on-non-empty /etc/hylafax + +# clear and deregister config file out from ucf database +which ucf /dev/null ucf --purge /etc/hylafax/pagesizes +which ucfr /dev/null ucfr --purge hylafax-client /etc/hylafax/pagesizes fi diff -ruN 6.0.6-1/debian/rules 6.0.6-2~wheezy1/debian/rules --- 6.0.6-1/debian/rules2012-06-17 14:47:42.0 +0200 +++ 6.0.6-2~wheezy1/debian/rules2012-10-13 00:08:17.0 +0200 @@ -224,6 +224,7 @@ do chmod 755 $(d_server)/var/spool/hylafax/$$i; done chmod 775 $(d_server)/var/spool/hylafax chmod 4777 $(d_server)/var/spool/hylafax/tmp + chmod og+t $(d_server)/var/spool/hylafax/tmp chmod 755 $(d_server)/var/spool/hylafax/dev chown uucp $(d_server)/etc/hylafax/hosts.hfaxd chmod 600 $(d_server)/etc/hylafax/hosts.hfaxd signature.asc Description: This is a digitally signed message part
Bug#690238: Installing DI beta2 on DELL PowerEdge T620 with RAID controller H710 and an LTO3 connected to a SAS controller
Package: installation-reports Boot method: USB memory stick with ISO image embedded Image version: http://hammurabi.acc.umu.se/cdimage/wheezy_di_beta2/amd64/iso-cd/debian-wheezy-DI-b2-amd64-netinst.iso Date: 2012-10-11 Machine: DELL PowerEdge T620 Processor: Intel(R) Xeon(R) CPU E5-2650 0 @ 2.00GHz Memory: 32GB Partitions: Disk /dev/sda: 599.6 GB, 599550590976 bytes 255 heads, 63 sectors/track, 72891 cylinders, total 1170997248 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x000177d3 Device Boot Start End Blocks Id System /dev/sda1 *2048 487423 242688 83 Linux /dev/sda2 487424 1170995199 585253888 8e Linux LVM File systemTipo 1K-blocchi Usati Disponib. Uso% Montato su rootfs rootfs 4866816 698424 3924272 16% / udev devtmpfs 10240 0 10240 0% /dev tmpfs tmpfs 3297080288 3296792 1% /run /dev/mapper/agenzia--f27-root ext44866816 698424 3924272 16% / tmpfs tmpfs 5120 0 5120 0% /run/lock tmpfs tmpfs 6594140 0 6594140 0% /run/shm /dev/sda1 ext2 227431 17606197691 9% /boot /dev/mapper/agenzia--f27-home ext4 27266916 532036 25367840 3% /home /dev/mapper/agenzia--f27-samba ext4 44826400 791072 41789288 2% /srv/samba /dev/mapper/agenzia--f27-tmp ext32882592 69900 2666260 3% /tmp /dev/mapper/agenzia--f27-var ext4 38971192 929624 36088596 3% /var Output of lspci -knn (or lspci -nn): 00:00.0 Host bridge [0600]: Intel Corporation Sandy Bridge DMI2 [8086:3c00] (rev 07) Subsystem: Dell Device [1028:04cf] 00:01.0 PCI bridge [0604]: Intel Corporation Sandy Bridge IIO PCI Express Root Port 1a [8086:3c02] (rev 07) Kernel driver in use: pcieport 00:02.0 PCI bridge [0604]: Intel Corporation Sandy Bridge IIO PCI Express Root Port 2a [8086:3c04] (rev 07) Kernel driver in use: pcieport 00:03.0 PCI bridge [0604]: Intel Corporation Sandy Bridge IIO PCI Express Root Port 3a in PCI Express Mode [8086:3c08] (rev 07) Kernel driver in use: pcieport 00:05.0 System peripheral [0880]: Intel Corporation Sandy Bridge Address Map, VTd_Misc, System Management [8086:3c28] (rev 07) Subsystem: Dell Device [1028:04cf] 00:05.2 System peripheral [0880]: Intel Corporation Sandy Bridge Control Status and Global Errors [8086:3c2a] (rev 07) Subsystem: Dell Device [1028:04cf] 00:11.0 PCI bridge [0604]: Intel Corporation Patsburg PCI Express Virtual Root Port [8086:1d3e] (rev 05) Kernel driver in use: pcieport 00:16.0 Communication controller [0780]: Intel Corporation Patsburg HECI Controller #1 [8086:1d3a] (rev 05) Subsystem: Dell Device [1028:04cf] 00:16.1 Communication controller [0780]: Intel Corporation Patsburg HECI Controller #2 [8086:1d3b] (rev 05) Subsystem: Dell Device [1028:04cf] 00:1a.0 USB Controller [0c03]: Intel Corporation Patsburg USB2 Enhanced Host Controller #2 [8086:1d2d] (rev 05) Subsystem: Dell Device [1028:04cf] Kernel driver in use: ehci_hcd 00:1c.0 PCI bridge [0604]: Intel Corporation Patsburg PCI Express Root Port 1 [8086:1d10] (rev b5) Kernel driver in use: pcieport 00:1c.4 PCI bridge [0604]: Intel Corporation Patsburg PCI Express Root Port 5 [8086:1d18] (rev b5) Kernel driver in use: pcieport 00:1c.7 PCI bridge [0604]: Intel Corporation Patsburg PCI Express Root Port 8 [8086:1d1e] (rev b5) Kernel driver in use: pcieport 00:1d.0 USB Controller [0c03]: Intel Corporation Patsburg USB2 Enhanced Host Controller #1 [8086:1d26] (rev 05) Subsystem: Dell Device [1028:04cf] Kernel driver in use: ehci_hcd 00:1e.0 PCI bridge [0604]: Intel Corporation 82801 PCI Bridge [8086:244e] (rev a5) 00:1f.0 ISA bridge [0601]: Intel Corporation Patsburg LPC Controller [8086:1d41] (rev 05) Subsystem: Dell Device [1028:04cf] 00:1f.2 SATA controller [0106]: Intel Corporation Patsburg 6-Port SATA AHCI Controller [8086:1d02] (rev 05) Subsystem: Dell Device [1028:04cf] Kernel driver in use: ahci 01:00.0 Serial Attached SCSI controller [0107]: LSI Logic / Symbios Logic SAS2008 PCI-Express Fusion-MPT SAS-2 [Falcon] [1000:0072] (rev 03) Subsystem: Dell Device [1028:1f1c] Kernel driver in use: mpt2sas 02:00.0 RAID bus controller [0104]: LSI Logic / Symbios Logic MegaRAID SAS TB [1000:005b] (rev 01) Subsystem: Dell Device [1028:1f35] 06:00.0 Ethernet controller [0200]: Intel Corporation Device [8086:1521] (rev 01) Subsystem: Dell Device [1028:04cf] Kernel driver in use: igb 06:00.1 Ethernet controller [0200]: Intel Corporation Device [8086:1521] (rev
Bug#685230: unblock hylafax 3:6.0.6-4
Il giorno lun, 01/10/2012 alle 10.23 +0200, Julien Cristau ha scritto: [...] The BTS thinks #661482 and #682824 are RC bugs affecting the version in testing. You are right, I am going to prepare and updated package during this weekend. Thanks, Giuseppe -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#685230: unblock hylafax 3:6.0.6-4
Hi Julien, could you please explain why you would remove hylafax from wheezy (I am probably missing something here)? Isn't the package currently in testing good enough? All RC bugs have been already solved. If you think it is compulsory to fix these bugs on the wheezy version, than I may prepare an upload as suggested by Cyril. Bye, Giuseppe -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
