Bug#745965: [nautilus] File corruption in MPT transfer.

2014-04-26 Thread Fenix

Package: nautilus
Version: 3.8.2-2
Severity: important

--- Please enter the report below this line. ---

  Hi.

  I usually transfer video files from mi smartphone (SG SII) to my PC 
using MPT (Media Transfer Protocol).


  Today, one of the file throw an error trying to open it, so I have 
checked the file and it have not the same byte size.


  I have checked some other video files and all have a corruption size.

  If I send the file directly from the smartphone to the web and 
download it again, it have the same size from the smartphone and it is 
open correctly.




--- System information. ---
Architecture: i386
Kernel:   Linux 2.6.38-2-686

Debian Release: jessie/sid
  500 testing security.debian.org
  500 testing oktan.ls.fi.upm.es
  500 testing ftp.de.debian.org
  500 stable  dl.google.com

--- Package information. ---
Depends (Version) | Installed
=-+-
libatk1.0-0   (>= 1.32.0) | 2.12.0-1
libc6(>= 2.7) | 2.18-4
libcairo-gobject2 (>= 1.10.0) | 1.12.16-2
libcairo2 (>= 1.10.0) | 1.12.16-2
libexempi3 (>= 2.2.0) | 2.2.1-1
libexif12 | 0.6.21-1
libgail-3-0(>= 3.0.0) | 3.12.0-4
libgdk-pixbuf2.0-0(>= 2.25.2) | 2.30.6-1
libglib2.0-0  (>= 2.35.9) | 2.40.0-2
libgnome-desktop-3-7   (>= 3.6.1) | 3.8.4-2
libgtk-3-0(>= 3.7.10) | 3.12.0-4
libnautilus-extension1a (>= 2.91) | 3.8.2-2
libnotify4 (>= 0.7.0) | 0.7.6-2
libpango-1.0-0(>= 1.20.0) | 1.36.3-1
libpangocairo-1.0-0   (>= 1.14.0) | 1.36.3-1
libselinux1 (>= 1.32) | 2.2.2-1
libtracker-sparql-0.16-0  (>= 0.10.0) | 0.16.2-1+b2
libx11-6  | 2:1.6.2-1
libxml2(>= 2.7.4) | 2.9.1+dfsg1-3
nautilus-data(>= 3.8) | 3.8.2-2
nautilus-data(<< 3.9) | 3.8.2-2
shared-mime-info(>= 0.50) | 1.2-1
desktop-file-utils   (>= 0.7) | 0.22-1
gvfs   (>= 1.3.2) | 1.20.1-1
libglib2.0-data   | 2.40.0-2
gsettings-desktop-schemas  (>= 3.8.0) | 3.8.2-2


Recommends (Version) | Installed
-+-===
eject| 2.1.5+deb1+cvs20081104-13.1
librsvg2-common  | 2.40.2-1
gvfs-backends| 1.20.1-1
gnome-icon-theme-symbolic| 3.12.0-1
gnome-sushi  | 3.10.0-1+b1


Suggests   (Version) | Installed
-+-===
brasero(>= 2.26) | 3.8.0-2+b1
eog  | 3.12.0-1
evince   | 3.12.0-1
 OR pdf-viewer   |
totem|
 OR mp3-decoder  |
xdg-user-dirs|
tracker  |


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org



Bug#681006: [synfigstudio] Mouse doesn't work at draw window, so I can't draw or select anything at it.

2012-07-09 Thread Fenix

Package: synfigstudio
Version: 0.63.05-1
Severity: important

--- Please enter the report below this line. ---


The program worked fine weeks ago. But suddenly mouse doesn't work in 
the work (I can't clic) window, only.


In other window: tools, key time it works fine.


I just see a GTK error message in console execution:


(synfigstudio:12490): GLib-GObject-CRITICAL **: Object class 
gtkmm__CustomObject_N6studio15ValueBase_EntryE doesn't implement 
property 'editing-canceled' from interface 'GtkCellEditable'




Thanks.



--- System information. ---
Architecture: i386
Kernel:   Linux 2.6.38-2-686

Debian Release: wheezy/sid
  500 testing security.debian.org
  500 testing ftp.de.debian.org
  500 testing debian-multimedia.informatik.uni-erlangen.de

--- Package information. ---
Depends(Version) | Installed
-+-==
libatkmm-1.6-1   (>= 2.22.1) | 2.22.6-1
libc6   (>= 2.8) | 2.13-33
libcairo2 (>= 1.2.4) | 1.12.2-2
libcairomm-1.0-1  (>= 1.6.4) | 1.10.0-1
libgcc1 (>= 1:4.1.1) | 1:4.7.1-2
libglib2.0-0 (>= 2.12.0) | 2.32.3-1
libglibmm-2.4-1c2a  (>= 2.31.22) | 2.32.0-1
libgtk2.0-0   (>= 2.8.0) | 2.24.10-1
libgtkmm-2.4-1c2a  (>= 1:2.24.0) | 1:2.24.2-1
libpangomm-1.4-1 (>= 2.27.1) | 2.28.4-1
libsigc++-2.0-0c2a(>= 2.0.2) | 2.2.10-0.2
libstdc++6  (>= 4.6) | 4.7.1-2
libsynfig0   | 0.63.05-1


Recommends   (Version) | Installed
==-+-===
synfig-examples| 0.63.05-1


Package's Suggests field is empty.






--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org



Bug#709779: [synfigstudio] Segment Violation after Synfig core update

2013-05-25 Thread Fenix

Package: synfigstudio
Version: 0.63.05-1
Severity: grave

--- Please enter the report below this line. ---

After the update of Synfig core to 0.64, Synfigstudio break down with a 
segmentation fault.


---
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0xb0affb40 (LWP 6437)]
0x083a42f9 in studio::WorkAreaTarget::next_tile(int&, int&) ()
---

I've clean and recreate ~/.synfig.

I've seen that a synfigstudio update to 0.64 is imminent in testing. 
Maybe it fix the problem... but would be Synfigstudio depend of core 
0.63 as maximum and not permit to update to 0.64?




--- System information. ---
Architecture: i386
Kernel:   Linux 2.6.38-2-686

Debian Release: jessie/sid
  500 testing security.debian.org
  500 testing ftp.de.debian.org
  500 testing debian-multimedia.informatik.uni-erlangen.de
  500 stable  dl.google.com

--- Package information. ---
Depends(Version) | Installed
-+-==
libatkmm-1.6-1   (>= 2.22.1) | 2.22.6-1
libc6   (>= 2.8) | 2.17-3
libcairo2 (>= 1.2.4) | 1.12.14-4
libcairomm-1.0-1  (>= 1.6.4) | 1.10.0-1
libgcc1 (>= 1:4.1.1) | 1:4.8.0-7
libglib2.0-0 (>= 2.12.0) | 2.36.1-2build1
libglibmm-2.4-1c2a  (>= 2.31.22) | 2.32.1-1
libgtk2.0-0   (>= 2.8.0) | 2.24.10-2
libgtkmm-2.4-1c2a  (>= 1:2.24.0) | 1:2.24.2-1
libpangomm-1.4-1 (>= 2.27.1) | 2.28.4-1
libsigc++-2.0-0c2a(>= 2.0.2) | 2.2.10-0.2
libstdc++6  (>= 4.6) | 4.8.0-7
libsynfig0   | 0.64.0-1


Recommends   (Version) | Installed
==-+-===
synfig-examples| 0.64.0-1


Package's Suggests field is empty.


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org



Bug#705290: [chromium] Bug confirmed... by me. :)

2013-05-25 Thread Fenix

Package: chromium
Version: 26.0.1410.43-1

--- Please enter the report below this line. ---

  Hi.

  I have the same issue.

  After Jessie update HTML5 videos (Youtube) don't reproduce sound. 
Flash videos, yes.


  I think that could be a PulseAudio error, but I don't know if is 
PulseAudio bug or Chromium bug. If someone could confirm that using 
Pulseaudio (instead of pure ALSA) have the same problem could bring light.




--- System information. ---
Architecture: i386
Kernel:   Linux 2.6.38-2-686

Debian Release: jessie/sid
  500 testing security.debian.org
  500 testing ftp.de.debian.org
  500 testing debian-multimedia.informatik.uni-erlangen.de
  500 stable  dl.google.com

--- Package information. ---
Depends (Version) | Installed
=-+-===
gconf-service | 3.2.5-1+build1
libasound2(>= 1.0.16) | 1.0.25-4
libatk1.0-0   (>= 1.12.4) | 2.8.0-2
libbz2-1.0| 1.0.6-4
libc6   (>= 2.11) | 2.17-3
libcairo2  (>= 1.6.0) | 1.12.14-4
libcups2   (>= 1.4.0) | 1.5.3-5
libdbus-1-3   (>= 1.2.14) | 1.6.10-1
libevent-2.0-5 (>= 2.0.10-stable) | 2.0.19-stable-3
libexpat1  (>= 2.0.1) | 2.1.0-3
libflac8   (>= 1.2.1) | 1.2.1-6
libfontconfig1 (>= 2.9.0) | 2.9.0-7.1
libfreetype6   (>= 2.3.9) | 2.4.9-1.1
libgcc1  (>= 1:4.1.1) | 1:4.8.0-7
libgconf-2-4  (>= 2.31.1) | 3.2.5-1+build1
libgcrypt11(>= 1.4.5) | 1.5.0-5
libgdk-pixbuf2.0-0(>= 2.22.0) | 2.28.1-1
libglib2.0-0  (>= 2.26.0) | 2.36.1-2build1
libgnome-keyring0 (>= 2.22.2) | 3.4.1-1
libgtk2.0-0   (>= 2.24.0) | 2.24.10-2
libjpeg8  (>= 8c) | 8d-1
libnspr4(>= 2:4.9-2~) | 2:4.9.6-1
libnss3 (>= 2:3.13.4-2~)  | 2:3.14.3-1
 OR libnss3-1d(>= 3.12.3) | 2:3.14.3-1
libpango1.0-0 (>= 1.22.0) | 1.30.0-1
libpulse0 (>= 0.99.1) | 2.0-6.1
libspeechd2   | 0.7.1-6.2
libspeex1(>= 1.2~beta3-1) | 1.2~rc1-7
libstdc++6   (>= 4.6) | 4.8.0-7
libudev0 (>= 146) | 175-7.2
libx11-6  (>= 2:1.4.99.1) | 2:1.5.0-1
libxcomposite1   (>= 1:0.3-1) | 1:0.4.3-2
libxdamage1(>= 1:1.1) | 1:1.1.3-2
libxext6  | 2:1.3.1-2
libxfixes3| 1:5.0-4
libxml2(>= 2.7.4) | 2.8.0+dfsg1-7+nmu1
libxrandr2   (>= 2:1.2.0) | 2:1.3.2-2
libxrender1   | 1:0.9.7-1
libxslt1.1(>= 1.1.25) | 1.1.26-14.1
libxss1   | 1:1.2.2-1
xdg-utils | 1.1.0~rc1+git20111210-7
chromium-inspector| 26.0.1410.43-1


Package's Recommends field is empty.

Suggests   (Version) | Installed
-+-===
chromium-l10n| 26.0.1410.43-1


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org



Bug#709809: [file-roller] Freeze when try to package a FIFO file.

2013-05-25 Thread Fenix

Package: file-roller
Version: 3.4.2-1
Severity: normal

--- Please enter the report below this line. ---

To reproduce the error:

$ mkfifo test

Try to package that file from Nautilus, for example.

File-roller opens, create the temp package file and show the progress 
window forever and ever.


If you close the file-roller popup the process continue in background 
and need a kill -15 to finish it.


If you try to package that type of file with others have the same issue.




--- System information. ---
Architecture: i386
Kernel:   Linux 2.6.38-2-686

Debian Release: jessie/sid
  500 testing security.debian.org
  500 testing ftp.de.debian.org
  500 testing debian-multimedia.informatik.uni-erlangen.de
  500 stable  dl.google.com

--- Package information. ---
Depends   (Version) | Installed
===-+-
libc6  (>= 2.4) | 2.17-3
libcairo2(>= 1.2.4) | 1.12.14-4
libgdk-pixbuf2.0-0  (>= 2.22.0) | 2.28.1-1
libglib2.0-0(>= 2.30.0) | 2.36.1-2build1
libgtk-3-0   (>= 3.0.2) | 3.4.2-6
libmagic1   | 1:5.14-2
libnautilus-extension1a   (>= 2.91) | 3.4.2-1+build1
libpango1.0-0   (>= 1.14.0) | 1.30.0-1
dconf-gsettings-backend | 0.12.1-3
 OR gsettings-backend   |
bzip2   | 1.0.6-4
p7zip-full  | 9.20.1~dfsg.1-4
nautilus-data  (>= 3.0) | 3.4.2-1+build1


Recommends(Version) | Installed
===-+-===
gnome-icon-theme  (>= 2.18) | 3.4.0-2
gvfs| 1.12.3-4


Suggests   (Version) | Installed
-+-===
arj  | 3.10.22-11
binutils | 2.22-8
cpio | 2.11+dfsg-0.1
lha  |
lzip |
lzma | 9.22-2
lzop | 1.03-3
ncompress| 4.2.4.4-7
rpm2cpio | 4.10.3.1-1
rzip |
sharutils| 1:4.11.1-2
unace| 1.2b-10
unalz|
unrar| 1:4.2.4-0.3
 OR p7zip-rar| 9.20.1~ds.1-3
unzip| 6.0-9
xz-utils | 5.1.1alpha+20120614-2
zip  | 3.0-7
zoo  |


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org



Bug#673146: [synfigstudio] Crash at starting.

2012-05-16 Thread Fenix

Package: synfigstudio
Version: 0.62.00-1
Severity: grave

--- Please enter the report below this line. ---

  Hi, when I start Synfigstudio, it throws me the next messages:


~$ synfigstudio

   Synfig Studio: iniciando aplicación...

synfig(18267) [14:29:28] información: Cargando módulos desde 
/etc/synfig/synfig_modules.cfg


(synfigstudio:18267): GLib-GObject-CRITICAL **: Object class 
gtkmm__CustomObject_N6studio15ValueBase_EntryE doesn't implement 
property 'editing-canceled' from interface 'GtkCellEditable'
GLib (gthread-posix.c): Unexpected error from C library during 
'pthread_cond_timedwait': Argumento inválido.  Aborting.

Abortado




--- System information. ---
Architecture: i386
Kernel:   Linux 2.6.38-2-686

Debian Release: wheezy/sid
  500 testing security.debian.org
  500 testing ftp.de.debian.org
  500 testing debian-multimedia.informatik.uni-erlangen.de

--- Package information. ---
Depends(Version) | Installed
-+-==
libatk1.0-0  (>= 1.20.0) | 2.4.0-2
libc6  (>= 2.3.6-6~) | 2.13-32
libcairo2 (>= 1.2.4) | 1.12.2-1
libcairomm-1.0-1  (>= 1.6.4) | 1.10.0-1
libfontconfig1(>= 2.8.0) | 2.9.0-3
libfreetype6  (>= 2.2.1) | 2.4.9-1
libgcc1 (>= 1:4.1.1) | 1:4.7.0-7
libglib2.0-0 (>= 2.12.0) | 2.32.2-1
libglibmm-2.4-1c2a   (>= 2.22.0) | 2.32.0-1
libgtk2.0-0   (>= 2.8.0) | 2.24.10-1
libgtkmm-2.4-1c2a  (>= 1:2.18.0) | 1:2.24.2-1
libltdl7 (>= 2.2.6b) | 2.4.2-1
libpango1.0-0(>= 1.14.0) | 1.30.0-1
libpangomm-1.4-1 (>= 2.26.0) | 2.28.4-1
libpng12-0 (>= 1.2.13-4) | 1.2.49-1
libsigc++-2.0-0c2a(>= 2.0.2) | 2.2.10-0.1
libstdc++6(>= 4.4.0) | 4.7.0-7
libsynfig0   | 0.62.00-2+b1
libsynfigapp0| 0.62.00-1
libx11-6 | 2:1.4.99.901-2
libxml++2.6-2(>= 2.24.0) | 2.34.2-1
libxml2  (>= 2.6.27) | 2.7.8.dfsg-9
libxrender1  | 1:0.9.7-1
zlib1g  (>= 1:1.1.4) | 1:1.2.7.dfsg-1


Recommends   (Version) | Installed
==-+-===
synfig-examples| 0.62.00-2


Package's Suggests field is empty.






--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org



Bug#855198: [obs-studio] Requested i386 architecture

2017-02-15 Thread Fenix

Package: obs-studio
Severity: wishlist

--- Please enter the report below this line. ---


Dear maintainer:

Any chance to get this package officially into i386 architecture?



   Greetings and thanks.



--- System information. ---
Architecture: Kernel:   Linux 4.9.0-1-686-pae

Debian Release: 9.0
  500 testing ftp.de.debian.org
  50 testing www.deb-multimedia.org



Bug#825850: [systemd] Long time to load accounts-daemon.service and issue with X

2016-05-30 Thread Fenix

Package: systemd
Version: 230-1
Severity: normal

--- Please enter the report below this line. ---


   Dear maintainer:


After 229.6 (I waited that 230-1 fix it, but it is the same) update I 
have a strange issue. First, as you can see the accounts-daemon.service 
takes a lot of time to load:



--
53.366s accounts-daemon.service
15.657s ModemManager.service
15.655s timidity.service
 14.075s loadcpufreq.service
 12.843s networking.service
  9.097s irqbalance.service
  9.041s dev-sda2.device
  8.415s fancontrol.service
  8.323s console-kit-log-system-start.service
  8.277s mono-xsp2.service
  8.243s firewall.service
  8.240s vboxdrv.service
  8.231s lm-sensors.service
  8.220s avahi-daemon.service
  8.208s alsa-restore.service
  8.160s gdomap.service
  8.159s iio-sensor-proxy.service
  8.159s klogd.service
  6.378s NetworkManager.service
  4.550s systemd-modules-load.service
  3.724s systemd-udevd.service
  3.213s console-screen.service
  2.988s polkitd.service
  2.452s packagekit.service
  2.282s binfmt-support.service
  1.684s gdm.service
  1.540s systemd-logind.service
  1.534s wpa_supplicant.service
  1.509s ntp.service
  1.486s keyboard-setup.service
  1.397s systemd-tmpfiles-setup-dev.service
  1.320s systemd-journald.service
  1.125s xfstt.service
  1.116s colord.service
   951ms dev-hugepages.mount
   950ms dev-mqueue.mount
   949ms sys-kernel-debug.mount
   923ms systemd-remount-fs.service
   895ms systemd-tmpfiles-setup.service
   830ms systemd-update-utmp.service
   796ms apt-daily.service
   480ms kmod-static-nodes.service
   478ms systemd-journal-flush.service
   441ms vboxautostart-service.service
   432ms vboxballoonctrl-service.service
   420ms systemd-udev-trigger.service
   407ms muroard.service
   393ms darkice.service
   354ms systemd-tmpfiles-clean.service
   345ms systemd-user-sessions.service
   307ms udisks2.service
   302ms rc-local.service
   265ms upower.service
   255ms systemd-sysctl.service
   243ms vboxweb-service.service
   233ms proc-sys-fs-binfmt_misc.mount
   218ms console-kit-daemon.service
   216ms 
dev-disk-by\x2duuid-91cc575f\x2d9cd7\x2d49c8\x2d91cd\x2d998cc528f7ef.swap

   143ms console-setup.service
   139ms user@1000.service
   104ms systemd-random-seed.service
75ms hddtemp.service
53ms cpufrequtils.service
41ms rtkit-daemon.service
35ms decnet.service
15ms nullmailer.service
13ms autofs.service
12ms sysklogd.service
 8ms systemd-update-utmp-runlevel.service
--


In the boot, systemd show me the message: A start job is running for 
Accouns Service ([a time counter up of one minute]).




Anyway, the gdm3 show me the login for the X and I can login right. But 
the real problem is that about one minute to be in the X, the system 
throws me out to the first text console. I need to enter again with 
ALT-F2. But in this situation only Gnome3 works (he reset one time after 
hang). If I use XFCE the system hangout.





Here is the critial-chain:

--
graphical.target @1min 4.934s
└─accounts-daemon.service @11.567s +53.366s
  └─basic.target @11.465s
└─sockets.target @11.465s
  └─cups.socket @11.465s
└─sysinit.target @11.386s
  └─swap.target @11.386s

└─dev-disk-by\x2duuid-91cc575f\x2d9cd7\x2d49c8\x2d91cd\x2d998cc528f7ef.swap 
@11.169s


└─dev-disk-by\x2duuid-91cc575f\x2d9cd7\x2d49c8\x2d91cd\x2d998cc528f7ef.device 
@11.1

--



I have not activate the systemd journal.



If you need more or extra information , please, feel free to ask.



Thanks.






--- System information. ---
Architecture: i386
Kernel:   Linux 4.5.0-2-686-pae

Debian Release: stretch/sid
  500 testing www.deb-multimedia.org
  500 testing ftp.de.debian.org
  500 stable  dl.google.com

--- Package information. ---
Depends (Version) | Installed
=-+-==
libacl1 (>= 2.2.51-8) | 2.2.52-3
libaudit1(>= 1:2.2.1) | 1:2.5.2-1
libblkid1 (>= 2.17.2) | 2.28-5
libcap2   (>= 1:2.10) | 1:2.25-1
libcryptsetup4   (>= 2:1.4.3) | 2:1.7.0-2
libdbus-1-3(>= 1.1.1) | 1.10.8-1
libkmod2  (>= 5~) | 22-1.1
libpam0g(>= 0.99.7.1) | 1.1.8-3.2
libselinux1(>= 2.1.9) | 2.5-3
libsystemd-journal0 (= 208-8) | 215-17
libudev1 (>= 

Bug#816314: Fix patch for 816314.

2016-04-05 Thread Fenix


Dear maintainer:

As the new version didn't fix this bug, I looked to the code and I find 
the problem (at least for me, but I really don't know how this error has 
been hidden just now. Maybe the old libusb masked the error in the code?).


The problem is in protocol.c

In the code:

--
case Tag_Appl_Prot_Id:
memset(datatypes,0,size * sizeof(uint16));
for ( j = i+1; p.packet.data[3*j] == Tag_Data_Type_Id; j++ ) {
datatypes[j-i-1] = get_uint16(p.packet.data + 3*j + 1);
}
--


The outing condition for the FOR loop throws the segmentation because 
didn't check the limit of j.



I fixed it checking first the counter 'j' and adjust it to the limit of 
the data.



--
case Tag_Appl_Prot_Id:
memset(datatypes,0,size * sizeof(uint16));
for ( j = i+1; (j<=size) && (p.packet.data[3*j] == Tag_Data_Type_Id); 
j++ ) {

datatypes[j-i-1] = get_uint16(p.packet.data + 3*j + 1);
}
--


I attach the patch file that fix this bug.

This is my first time I send a patch, so maybe it doesn't correct. If 
you need more information or anything else feel free to ask.



Thanks.
commit da9c57e496f5b88d875329e57fb7d47b3b5e84a9
Author: Fenix 
Date:   Wed Apr 6 00:25:15 2016 +0200

Fix #816314 error Segmentation Fault

diff --git a/src/protocol.c b/src/protocol.c
index 37f66b4..a0c0b36 100644
--- a/src/protocol.c
+++ b/src/protocol.c
@@ -583,7 +583,7 @@ garmin_read_a000_a001 ( garmin_unit * garmin )
 	  break;
 	case Tag_Appl_Prot_Id:
 	  memset(datatypes,0,size * sizeof(uint16));
-	  for ( j = i+1; p.packet.data[3*j] == Tag_Data_Type_Id; j++ ) {
+	  for ( j = i+1; (j<=size) && (p.packet.data[3*j] == Tag_Data_Type_Id); j++ ) {
 	datatypes[j-i-1] = get_uint16(p.packet.data + 3*j + 1);
 	  }
 	  garmin_assign_protocol(garmin,data,datatypes);


Bug#827922: calibre: Failed startup: Failed to load icu with error: No module named icu

2016-06-30 Thread Fenix

Hi, Martin. :)



On Thu, 30 Jun 2016 11:14:16 +0200 Martin Pitt  wrote:

Fenix [2016-06-30 10:47 +0200]:
> There is not plugins directory inside /usr/lib/calibre/calibre/

Do you actually have calibre-bin installed? The calibre package
depends on this, so it's actually fairly hard to not have it..



   Yes, it's installed.


   But I think there is a problem with it for the i386 (I have it, too 
as Andrzej) architecture.


   As you mentioned, I look at the package report and if you see at 
https://packages.debian.org/stretch/i386/calibre-bin/filelist it is "empty".


   There is a problem with the compilation of the package. MIPS and 
Powerpc have the same problem.




Bug#772748: [synfig] Interface doesn't accept changes in all parameters.

2014-12-10 Thread Fenix

Package: synfig
Version: 0.64.2-1
Severity: grave

--- Please enter the report below this line. ---


Hi!

There is a bug at interface that let to change any value.

Here is more info:

--
http://www.synfig.org/forums/viewtopic.php?f=15&t=6044&p=24734#p24734
--


I don't know it the patch is in unstable version 0.42.2-2, but if that 
version doesn't go to testing, it'll made the frozen package mostly non 
usable.



Thanks.




--- System information. ---
Architecture: i386
Kernel:   Linux 3.14-1-686-pae

Debian Release: 8.0
  500 testing security.debian.org
  500 testing oktan.ls.fi.upm.es
  500 testing ftp.de.debian.org
  500 stable  dl.google.com

--- Package information. ---
Depends   (Version) | Installed
===-+-=
libboost-program-options1.55.0  | 1.55.0+dfsg-3
libc6  (>= 2.8) | 2.19-13
libgcc1(>= 1:4.1.1) | 1:4.9.1-19
libstdc++6 (>= 4.6) | 4.9.1-19
libsynfig0  (>= 0.64.1) | 0.64.2-1


Package's Recommends field is empty.

Suggests (Version) | Installed
==-+-===
synfigstudio   | 0.64.2-1
synfig-examples| 0.64.2-1


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org



Bug#805554: [nvidia-legacy-304xx-driver] X fails to start

2015-11-19 Thread Fenix

Package: nvidia-legacy-304xx-driver
Version: 304.128-8
Severity: important



Dear Maintainer,

Since the last update (I think I had the 340 legacy, but, I supposed 
that Nvidia drop my device to 304 legacy), it is not possible to me to 
get up the X with Nvidia 304 legacy driver.


When X try to start, the screen get flickering with the text login. 
After some time (minutes), the screen stop to flickering in the text login.


I saw that 304.6 had some problems and I thought that it was my problem, 
but the problem persist with 304.8.


I see in journalctl (I don't know why Reportbug shows here the 
Xorg.x.logs files. Byt I leave them in case they help) this:


__
NVIDIA: Could not open the device file /dev/nvidiactl (No such file or
directory)
__

After that message, the log inform of the failed to initialize the 
nvidia kernel module.


As you can see, I added the user Debian-gdm to the group 'video', as I 
saw that it could be a problem of access. But didn't fix the problem.


I have purged all packaged related to Nvidia and 304 legacy driver and 
reinstalled. I used a new xorg.conf file (the one here works until the 
update) but didn't work, too.



If you need more information, please, feel free with requests.




-- Package-specific info:
uname -a:
Linux calisto 4.2.0-1-686-pae #1 SMP Debian 4.2.6-1 (2015-11-10) i686 
GNU/Linux


/proc/version:
Linux version 4.2.0-1-686-pae (debian-ker...@lists.debian.org) (gcc 
version 4.9.3 (Debian 4.9.3-5) ) #1 SMP Debian 4.2.6-1 (2015-11-10)


/proc/driver/nvidia/version:
NVRM version: NVIDIA UNIX x86 Kernel Module  304.128  Wed Aug 26 
10:41:50 PDT 2015

GCC version:  gcc version 4.9.3 (Debian 4.9.3-5)

lspci 'VGA compatible controller [0300]':
04:00.0 VGA compatible controller [0300]: NVIDIA Corporation G73 
[GeForce 7300 GT] [10de:0393] (rev a1) (prog-if 00 [VGA controller])
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Latency: 0, Cache Line Size: 16 bytes
Interrupt: pin A routed to IRQ 16
Region 0: Memory at df00 (32-bit, non-prefetchable) [size=16M]
Region 1: Memory at e000 (64-bit, prefetchable) [size=256M]
Region 3: Memory at de00 (64-bit, non-prefetchable) [size=16M]
Region 5: I/O ports at e800 [size=128]
Expansion ROM at ddfe [disabled] [size=128K]
Capabilities: 
Kernel driver in use: nvidia

dmesg:
[0.00] Console: colour VGA+ 80x25
[0.130985] vgaarb: setting as boot device: PCI::04:00.0
[0.130985] vgaarb: device added: 
PCI::04:00.0,decodes=io+mem,owns=io+mem,locks=none

[0.130985] vgaarb: loaded
[0.130985] vgaarb: bridge control possible :04:00.0
[0.966249] Linux agpgart interface v0.103
[   12.224780] nvidia: module license 'NVIDIA' taints kernel.
[   12.247927] vgaarb: device changed decodes: 
PCI::04:00.0,olddecodes=io+mem,decodes=none:owns=io+mem
[   12.248410] [drm] Initialized nvidia-drm 0.0.0 20150116 for 
:04:00.0 on minor 0
[   12.248419] NVRM: loading NVIDIA UNIX x86 Kernel Module  304.128  Wed 
Aug 26 10:41:50 PDT 2015


Device node permissions:
crw-rw+ 1 root video 226, 0 Nov 19 11:17 /dev/dri/card0
video:x:44:fenix,Debian-gdm

OpenGL and NVIDIA library files installed:
-rw-r--r-- 1 root root 4162 Nov 19 11:26 /etc/X11/xorg.conf
lrwxrwxrwx 1 root root   15 Nov 19 11:12 /etc/alternatives/glx -> 
/usr/lib/nvidia
lrwxrwxrwx 1 root root   47 Nov 19 11:10 
/etc/alternatives/glx--libEGL.so-i386-linux-gnu -> 
/usr/lib/mesa-diverted/i386-linux-gnu/libEGL.so
lrwxrwxrwx 1 root root   49 Nov 19 11:12 
/etc/alternatives/glx--libEGL.so.1-i386-linux-gnu -> 
/usr/lib/mesa-diverted/i386-linux-gnu/libEGL.so.1
lrwxrwxrwx 1 root root   46 Nov 19 11:10 
/etc/alternatives/glx--libGL.so-i386-linux-gnu -> 
/usr/lib/mesa-diverted/i386-linux-gnu/libGL.so
lrwxrwxrwx 1 root root   46 Nov 19 11:10 
/etc/alternatives/glx--libGL.so-i386-linux-gnu -> 
/usr/lib/mesa-diverted/i386-linux-gnu/libGL.so
lrwxrwxrwx 1 root root   41 Nov 19 11:12 
/etc/alternatives/glx--libGL.so.1-i386-linux-gnu -> 
/usr/lib/i386-linux-gnu/nvidia/libGL.so.1
lrwxrwxrwx 1 root root   41 Nov 19 11:12 
/etc/alternatives/glx--libGL.so.1-i386-linux-gnu -> 
/usr/lib/i386-linux-gnu/nvidia/libGL.so.1
lrwxrwxrwx 1 root root   55 Nov 19 11:12 
/etc/alternatives/glx--libGLESv1_CM.so.1-i386-linux-gnu -> 
/usr/lib/mesa-diverted/i386-linux-gnu/libGLESv1_CM.so.1
lrwxrwxrwx 1 root root   55 Nov 19 11:12 
/etc/alternatives/glx--libGLESv1_CM.so.1-i386-linux-gnu -> 
/usr/lib/mesa-diverted/i386-linux-gnu/libGLESv1_CM.so.1
lrwxrwxrwx 1 root root   52 Nov 19 11:12 
/etc/alternatives/glx--libGLESv2.so.2-i386-linux-gnu -> 
/usr/lib/mesa-diverted/i386-linux-gnu/libGLESv2.so.2
lrwxrwxrwx 1 root root   52 N

Bug#816314: [garmin-forerunner-tools] Segmentation fault

2016-02-29 Thread Fenix

Package: garmin-forerunner-tools
Version: 0.10repacked-7
Severity: important

--- Please enter the report below this line. ---


Dear maintainer:

All programs (garmin-get-info, garmin-save-runs) of 
garmin-forerunner-tools packages throws me a Segmentation Fault.


With old versions it worked fine.


$ garmin-get-info

Violación de segmento

$ garmin-get-info -v

[garmin] libusb_init succeeded
[garmin] found VID 091e, PID 0003[garmin] libusb_open = 0x8079430
[garmin] libusb_set_configuration[1] succeeded
[garmin] libusb_claim_interface[0] succeeded
[garmin] libusb_get_config_descriptor_by_value succeeded
[garmin] intr IN  = 1
[garmin] bulk OUT = 2
[garmin] bulk IN  = 3





 
  (null)
 
 
  
  
  
 




$ valgrind garmin-get-info

==2586== Use of uninitialised value of size 4
==2586==at 0x406B600: garmin_open (in /usr/lib/libgarmintools.so.4.2.0)
==2586==by 0x40747C1: garmin_init (in /usr/lib/libgarmintools.so.4.2.0)
==2586==by 0x80485B9: ??? (in /usr/bin/garmin_get_info)
==2586==by 0x40C870D: (below main) (in 
/lib/i386-linux-gnu/i686/cmov/libc-2.21.so)

==2586==
==2586== Invalid read of size 4
==2586==at 0x406B603: garmin_open (in /usr/lib/libgarmintools.so.4.2.0)
==2586==by 0x40747C1: garmin_init (in /usr/lib/libgarmintools.so.4.2.0)
==2586==by 0x80485B9: ??? (in /usr/bin/garmin_get_info)
==2586==by 0x40C870D: (below main) (in 
/lib/i386-linux-gnu/i686/cmov/libc-2.21.so)

==2586==  Address 0xc0012 is not stack'd, malloc'd or (recently) free'd
==2586==
==2586==
==2586== Process terminating with default action of signal 11 (SIGSEGV)
==2586==  Access not within mapped region at address 0xC0012
==2586==at 0x406B603: garmin_open (in /usr/lib/libgarmintools.so.4.2.0)
==2586==by 0x40747C1: garmin_init (in /usr/lib/libgarmintools.so.4.2.0)
==2586==by 0x80485B9: ??? (in /usr/bin/garmin_get_info)
==2586==by 0x40C870D: (below main) (in 
/lib/i386-linux-gnu/i686/cmov/libc-2.21.so)

==2586==  If you believe this happened as a result of a stack
==2586==  overflow in your program's main thread (unlikely but
==2586==  possible), you can try to increase the size of the
==2586==  main thread stack using the --main-stacksize= flag.
==2586==  The main thread stack size used in this run was 8388608.
==2586==
==2586== HEAP SUMMARY:
==2586== in use at exit: 16,069 bytes in 31 blocks
==2586==   total heap usage: 1,277 allocs, 1,246 frees, 622,195 bytes 
allocated

==2586==
==2586== LEAK SUMMARY:
==2586==definitely lost: 0 bytes in 0 blocks
==2586==indirectly lost: 0 bytes in 0 blocks
==2586==  possibly lost: 192 bytes in 4 blocks
==2586==still reachable: 15,877 bytes in 27 blocks
==2586== suppressed: 0 bytes in 0 blocks
==2586== Rerun with --leak-check=full to see details of leaked memory
==2586==
==2586== For counts of detected and suppressed errors, rerun with: -v
==2586== Use --track-origins=yes to see where uninitialised values come from
==2586== ERROR SUMMARY: 2 errors from 2 contexts (suppressed: 0 from 0)



Thanks.




--- System information. ---
Architecture: i386
Kernel:   Linux 4.3.0-1-686-pae

Debian Release: stretch/sid
  500 testing www.deb-multimedia.org
  500 testing security.debian.org
  500 testing ftp.de.debian.org
  500 stable  dl.google.com

--- Package information. ---
Depends  (Version) | Installed
==-+-==
libc6 (>= 2.4) | 2.21-9
libusb-0.1-4 (>= 2:0.1.12) | 2:0.1.12-28


Package's Recommends field is empty.

Package's Suggests field is empty.



Bug#853768: [kdenlive] Segment violation at start with Nvidia device

2017-01-31 Thread Fenix

Package: kdenlive
Version: 16.12.1-1
Severity: normal

--- Please enter the report below this line. ---

Dear maintainer:

When I start up Kdenlive I get a segmentation fault:

--
:~$ kdenlive
OpenGL vendor:  "NVIDIA Corporation"
OpenGL renderer:  "GeForce GT 730/PCIe/SSE2"
OpenGL Threaded:  true
OpenGL ARG_SYNC:  true
OpenGL OpenGLES:  false
QOpenGLFunctions created with non-current context
Violación de segmento
:~$

--



It seems that there is a bug with version 16.12.1 and Nvidia devices 
(https://bugs.kde.org/show_bug.cgi?id=375128)



At least for me, 16.12.1-1 is affected.



Thanks.


PS: I set severity to normal as it seems only Nvidia users are affected.



--- System information. ---
Architecture: Kernel:   Linux 4.9.0-1-686-pae

Debian Release: 9.0
  500 testing ftp.de.debian.org50 testing 
www.deb-multimedia.org

--- Package information. ---
Depends  (Version) | Installed
==-+-===
kio| 5.28.0-1
libc6(>= 2.15) | 2.24-8
libgcc1 (>= 1:4.2) | 1:6.3.0-5
libgl1-mesa-glx| 13.0.3-1
 OR libgl1 | libglu1-mesa 
| 9.0.0-2.1
 OR libglu1| libkf5archive5 
(>= 4.96.0) | 5.28.0-1

libkf5attica5  (>= 4.96.0) | 5.28.0-1
libkf5auth5(>= 4.96.0) | 5.28.0-1
libkf5bookmarks5   (>= 4.96.0) | 5.28.0-1
libkf5codecs5  (>= 4.96.0) | 5.28.0-1
libkf5completion5  (>= 4.97.0) | 5.28.0-1
libkf5configcore5  (>= 4.98.0) | 5.28.0-1
libkf5configgui5   (>= 4.97.0) | 5.28.0-1
libkf5configwidgets5   (>= 4.96.0) | 5.28.0-1
libkf5coreaddons5 (>= 4.100.0) | 5.28.0-1
libkf5crash5   (>= 5.15.0) | 5.28.0-1
libkf5dbusaddons5  (>= 4.97.0) | 5.28.0-1
libkf5filemetadata3 (>= 5.0.2+git20140925) | 5.28.0-1
libkf5guiaddons5   (>= 4.96.0) | 5.28.0-1
libkf5i18n5(>= 4.97.0) | 5.28.0-1
libkf5iconthemes5  (>= 5.25.0) | 5.28.0-1
libkf5itemviews5   (>= 4.96.0) | 5.28.0-1
libkf5jobwidgets5  (>= 4.96.0) | 5.28.0-1
libkf5kiocore5 (>= 4.96.0) | 5.28.0-1
libkf5kiofilewidgets5  (>= 4.96.0) | 5.28.0-1
libkf5kiowidgets5  (>= 4.99.0) | 5.28.0-1
libkf5newstuff5(>= 4.95.0) | 5.28.0-1
libkf5notifications5   (>= 4.96.0) | 5.28.0-1
libkf5notifyconfig5(>= 4.96.0) | 5.28.0-1
libkf5service-bin  | 5.28.0-1
libkf5service5 (>= 4.96.0) | 5.28.0-1
libkf5solid5   (>= 4.97.0) | 5.28.0-2
libkf5sonnetui5(>= 4.96.0) | 5.28.0-1
libkf5textwidgets5  (>= 5.0.0) | 5.28.0-1
libkf5widgetsaddons5   (>= 5.16.0) | 5.28.0-1
libkf5xmlgui5  (>= 4.98.0) | 5.28.0-1
libmlt++3   (>= 6.4.1) | 6.4.1-1
libmlt6 (>= 6.4.1) | 6.4.1-1
libqt5concurrent5   (>= 5.0.2) | 5.7.1+dfsg-3
libqt5core5a(>= 5.7.0) | 5.7.1+dfsg-3
libqt5dbus5 (>= 5.0.2) | 5.7.1+dfsg-3
libqt5gui5  (>= 5.7.0) | 5.7.1+dfsg-3
libqt5network5  (>= 5.0.2) | 5.7.1+dfsg-3
libqt5qml5  (>= 5.0.2) | 5.7.1-2
libqt5quick5(>= 5.6.1) | 5.7.1-2
libqt5script5  (>= 5.6.0~beta) | 
5.7.1~20161021+dfsg-2

libqt5svg5 (>= 5.6.0~beta) | 5.7.1~20161021-2
libqt5widgets5  (>= 5.7.0) | 5.7.1+dfsg-3
libqt5xml5  (>= 5.0.2) | 5.7.1+dfsg-3
libstdc++6  (>= 4.1.1) | 6.3.0-5
libv4l-0(>= 0.5.0) | 1.10.1-1
kdenlive-data(= 16.12.1-1) | 16.12.1-1
qml-module-qtquick2| 5.7.1-2
qml-module-qtquick-controls| 5.7.1~20161021-2
kinit  | 5.28.0-1
kded5  | 5.28.0-1
oxygen-icon-theme  | 5:5.28.0-1
melt  

Bug#840342: [ace-of-penguins] Freecell No Longer Runs, Nvidia Legacy-304xx video driver

2016-12-19 Thread Fenix

On 17/12/16 02:03, Andreas Beckmann wrote:


Hi,

I just uploaded 304.134 to sid, it should appear on the mirrors later
today. Please test it to see whether this bug is now fixed.



   Hi.

   I'm sorry, but I can't check this. Weeks ago my GT7300 died, so I 
sent Nvidia Corp. to the hell, I went to the shop and bought... a Nvidia 
again :). But this one works with the non-legacy driver.




Bug#842926: [musescore] Segment violation when Musescore opens with wizard (start center) active.

2016-11-02 Thread Fenix

Package: musescore
Version: 2.0.3+dfsg1-2
Severity: normal


Dear maintainer:

When I try to open Musescore I get a segmentation fault. When I try 
to open again, I get a message for get the last session. If I select 
"yes", the program runs correctly. If I select "no", the start center 
tries to open again and I get the segment violation.


If I uncheck the 'show start center' (I don't know if those are 
exactly the words in english. It is the wizard init window) option in 
the configuration, Musescore works fine.


It seems that something goes wrong with the 'start center' window.



Thanks.




--- System information. ---
Architecture: i386
Kernel:   Linux 4.7.0-1-686-pae

Debian Release: stretch/sid
  500 testing www.deb-multimedia.org   500 testing 
ftp.de.debian.org

--- Package information. ---
Depends   (Version) | Installed
===-+-
desktop-file-utils  | 0.23-1
libqt5sql5-sqlite   | 5.6.1+dfsg-3+b1
musescore-common  (= 2.0.3+dfsg1-2) | 2.0.3+dfsg1-2
qml-module-qtquick-controls | 5.6.1-3
qml-module-qtquick-dialogs  | 5.6.1-3
qml-module-qtquick-layouts  | 5.6.1-3
qml-module-qtquick2 | 5.6.1-11
shared-mime-info| 1.7-1
xdg-utils   | 1.1.1-1
libasound2  (>= 1.0.16) | 1.1.2-1
libc6 (>= 2.16) | 2.24-5
libfreetype6 (>= 2.2.1) | 2.6.3-3+b1
libgcc1  (>= 1:4.2) | 1:6.2.0-10
libportaudio2   (>= 19+svn20101113) | 19+svn20140130-1.1
libpulse0   (>= 0.99.1) | 9.0-4
libqt5core5a (>= 5.6.1) | 5.6.1+dfsg-3+b1
libqt5gui5  (>= 5.6.0~beta) | 5.6.1+dfsg-3+b1
libqt5help5 (>= 5.6.0~beta) | 5.6.1-4
libqt5network5   (>= 5.0.2) | 5.6.1+dfsg-3+b1
libqt5printsupport5  (>= 5.0.2) | 5.6.1+dfsg-3+b1
libqt5qml5   (>= 5.0.2) | 5.6.1-11
libqt5quick5 (>= 5.6.1) | 5.6.1-11
libqt5svg5  (>= 5.6.0~beta) | 5.6.1-2
libqt5webkit5 (>= 5.6.0~rc) | 5.6.1+dfsg-5
libqt5widgets5  (>= 5.6.0~beta) | 5.6.1+dfsg-3+b1
libqt5xml5   (>= 5.0.2) | 5.6.1+dfsg-3+b1
libqt5xmlpatterns5   (>= 5.0.2) | 5.6.1-2
libsndfile1 (>= 1.0.20) | 1.0.27-1
libstdc++6 (>= 5.2) | 6.2.0-10
libvorbisfile3   (>= 1.1.2) | 1.3.5-3
qtbase-abi-5-6-1| zlib1g 
(>= 1:1.1.4) | 1:1.2.8.dfsg-2+b3



Recommends(Version) | Installed
===-+-===
pulseaudio-utils| 9.0-4


Suggests(Version) | Installed
=-+-===
fluid-soundfont-gm| 3.1-5
timgm6mb-soundfont| 1.3-2



Bug#840342: [nvidia-legacy-304xx-driver] Confirmation

2016-10-13 Thread Fenix
lized nvidia-drm 0.0.0 20150116 for :04:00.0 on 
minor 0
[   11.307131] NVRM: loading NVIDIA UNIX x86 Kernel Module  304.132  Fri Sep 16 
11:22:35 PDT 2016

Device node permissions:
crw-rw+ 1 root video 226,   0 Oct 13 13:46 /dev/dri/card0
crw-rw-rw-  1 root root  195,   0 Oct 13 13:47 /dev/nvidia0
crw-rw-rw-  1 root root  195, 255 Oct 13 13:47 /dev/nvidiactl
video:x:44:fenix

OpenGL and NVIDIA library files installed:
-rw-r--r-- 1 root root  217 Feb 27  2016 /etc/X11/xorg.conf
lrwxrwxrwx 1 root root   15 Jul 20 09:50 /etc/alternatives/glx -> 
/usr/lib/nvidia
lrwxrwxrwx 1 root root   47 Feb 26  2016 
/etc/alternatives/glx--libEGL.so-i386-linux-gnu -> 
/usr/lib/mesa-diverted/i386-linux-gnu/libEGL.so
lrwxrwxrwx 1 root root   49 Jul 20 09:50 
/etc/alternatives/glx--libEGL.so.1-i386-linux-gnu -> 
/usr/lib/mesa-diverted/i386-linux-gnu/libEGL.so.1
lrwxrwxrwx 1 root root   46 Feb 26  2016 
/etc/alternatives/glx--libGL.so-i386-linux-gnu -> 
/usr/lib/mesa-diverted/i386-linux-gnu/libGL.so
lrwxrwxrwx 1 root root   46 Feb 26  2016 
/etc/alternatives/glx--libGL.so-i386-linux-gnu -> 
/usr/lib/mesa-diverted/i386-linux-gnu/libGL.so
lrwxrwxrwx 1 root root   41 Jul 20 09:50 
/etc/alternatives/glx--libGL.so.1-i386-linux-gnu -> 
/usr/lib/i386-linux-gnu/nvidia/libGL.so.1
lrwxrwxrwx 1 root root   41 Jul 20 09:50 
/etc/alternatives/glx--libGL.so.1-i386-linux-gnu -> 
/usr/lib/i386-linux-gnu/nvidia/libGL.so.1
lrwxrwxrwx 1 root root   55 Jul 20 09:50 
/etc/alternatives/glx--libGLESv1_CM.so.1-i386-linux-gnu -> 
/usr/lib/mesa-diverted/i386-linux-gnu/libGLESv1_CM.so.1
lrwxrwxrwx 1 root root   55 Jul 20 09:50 
/etc/alternatives/glx--libGLESv1_CM.so.1-i386-linux-gnu -> 
/usr/lib/mesa-diverted/i386-linux-gnu/libGLESv1_CM.so.1
lrwxrwxrwx 1 root root   52 Jul 20 09:50 
/etc/alternatives/glx--libGLESv2.so.2-i386-linux-gnu -> 
/usr/lib/mesa-diverted/i386-linux-gnu/libGLESv2.so.2
lrwxrwxrwx 1 root root   52 Jul 20 09:50 
/etc/alternatives/glx--libGLESv2.so.2-i386-linux-gnu -> 
/usr/lib/mesa-diverted/i386-linux-gnu/libGLESv2.so.2
lrwxrwxrwx 1 root root   49 Jul 20 09:50 
/etc/alternatives/glx--libXvMCNVIDIA.so.1-i386-linux-gnu -> 
/usr/lib/i386-linux-gnu/nvidia/libXvMCNVIDIA.so.1
lrwxrwxrwx 1 root root   57 Jul 20 09:50 
/etc/alternatives/glx--libXvMCNVIDIA_dynamic.so.1-i386-linux-gnu -> 
/usr/lib/i386-linux-gnu/nvidia/libXvMCNVIDIA_dynamic.so.1
lrwxrwxrwx 1 root root   49 Jul 20 09:50 
/etc/alternatives/glx--libnvidia-cfg.so.1-i386-linux-gnu -> 
/usr/lib/i386-linux-gnu/nvidia/libnvidia-cfg.so.1
lrwxrwxrwx 1 root root   25 Jul 20 09:50 
/etc/alternatives/glx--linux-libglx.so -> /usr/lib/nvidia/libglx.so
lrwxrwxrwx 1 root root   36 Jul 20 09:50 
/etc/alternatives/glx--nvidia-bug-report.sh -> 
/usr/lib/nvidia/nvidia-bug-report.sh
lrwxrwxrwx 1 root root   39 Jul 20 09:50 
/etc/alternatives/glx--nvidia-drm-outputclass.conf -> 
/etc/nvidia/nvidia-drm-outputclass.conf
lrwxrwxrwx 1 root root   32 Jul 20 09:50 
/etc/alternatives/glx--nvidia-modprobe.conf -> /etc/nvidia/nvidia-modprobe.conf
lrwxrwxrwx 1 root root   29 Jul 20 09:50 
/etc/alternatives/glx--nvidia_drv.so -> /usr/lib/nvidia/nvidia_drv.so
lrwxrwxrwx 1 root root   22 Feb 26  2016 /etc/alternatives/libGL.so-master 
-> /usr/lib/mesa-diverted
lrwxrwxrwx 1 root root   28 Jul  1 10:36 /etc/alternatives/nvidia -> 
/usr/lib/nvidia/legacy-304xx
lrwxrwxrwx 1 root root   54 Jul  1 10:36 
/etc/alternatives/nvidia--libGL.so.1-i386-linux-gnu -> 
/usr/lib/i386-linux-gnu/nvidia/legacy-304xx/libGL.so.1
lrwxrwxrwx 1 root root   54 Jul  1 10:36 
/etc/alternatives/nvidia--libGL.so.1-i386-linux-gnu -> 
/usr/lib/i386-linux-gnu/nvidia/legacy-304xx/libGL.so.1
lrwxrwxrwx 1 root root   62 Jul  1 10:36 
/etc/alternatives/nvidia--libXvMCNVIDIA.so.1-i386-linux-gnu -> 
/usr/lib/i386-linux-gnu/nvidia/legacy-304xx/libXvMCNVIDIA.so.1
lrwxrwxrwx 1 root root   70 Jul  1 10:36 
/etc/alternatives/nvidia--libXvMCNVIDIA_dynamic.so.1-i386-linux-gnu -> 
/usr/lib/i386-linux-gnu/nvidia/legacy-304xx/libXvMCNVIDIA_dynamic.so.1
lrwxrwxrwx 1 root root   38 Jul  1 10:36 
/etc/alternatives/nvidia--libglx.so -> /usr/lib/nvidia/legacy-304xx/libglx.so
lrwxrwxrwx 1 root root   62 Jul  1 10:36 
/etc/alternatives/nvidia--libnvidia-cfg.so.1-i386-linux-gnu -> 
/usr/lib/i386-linux-gnu/nvidia/legacy-304xx/libnvidia-cfg.so.1
lrwxrwxrwx 1 root root   61 Jul  1 10:36 
/etc/alternatives/nvidia--libnvidia-ml.so.1-i386-linux-gnu -> 
/usr/lib/i386-linux-gnu/nvidia/legacy-304xx/libnvidia-ml.so.1
lrwxrwxrwx 1 root root   64 Jul  1 10:36 
/etc/alternatives/nvidia--libvdpau_nvidia.so.1-i386-linux-gnu -> 
/usr/lib/i386-linux-gnu/nvidia/legacy-304xx/libvdpau_nvidia.so.1
lrwxrwxrwx 1 root root   43 Jul  1 10:36 
/etc/alternatives/nvidia--nv-control-dpy -> 
/usr/lib/nvidia/legacy-304xx/nv-control-dpy
lrwxrwxrwx 1 root root   49 Jul  1 10:36 

Bug#840342: [nvidia-legacy-304xx-driver] Confirmation

2016-10-14 Thread Fenix

On 13/10/16 15:40, Luca Boccassi wrote:



Thanks for the pointer, this looks indeed like an upstream issue.
Nothing much we can do until they fix it. Unfortunately the package has
already migrated to testing so we'll have to wait. Given how broken it
is I assume it won't take long.




Hi, Luca, don't worry.

As said Markus Koschany, and as you said meanwhile Nvidia fixes 
this, probably the best is that each one makes a manual setback to 
304.131.8 from Snapshots.


That is what I did and, of course, all works fine again.


Thanks and greetings.



Bug#816314: [Pkg-running-devel] Bug#816314: fixed in garmin-forerunner-tools 0.10repacked-9

2016-04-15 Thread Fenix

On 15/04/16 06:53, Christian PERRIER wrote:

Quoting Chris AtLee (ch...@atlee.ca):

I'm still getting a segfault in the latest version. Here's the traceback:

Program received signal SIGSEGV, Segmentation fault.
0x77bba378 in garmin_open (garmin=garmin@entry=0x7fffe350) at
usb_comm.c:137
137 usb_comm.c: No such file or directory.
(gdb) where
#0  0x77bba378 in garmin_open (garmin=garmin@entry=0x7fffe350)
at usb_comm.c:137
#1  0x77bc3180 in garmin_init (garmin=garmin@entry=0x7fffe350,
 verbose=) at protocol.c:1186
#2  0x00400725 in main (argc=, argv=)
 at garmin_save_runs.c:36



We may need to check this with Fenix, who provided the patch I
used. Sadly, I'm not in position to test myself




  Hi.

  I just went to re-open this. :)


  I don't know if that is important, but I see that in the master is 
not my change. Is it possible that the repacked9 is in real repacked8 again?




Bug#816314: [Pkg-running-devel] Bug#816314: fixed in garmin-forerunner-tools 0.10repacked-9

2016-04-15 Thread Fenix

Oooops.

I think that I know what happens. I just did clone [ 
git://git.debian.org/git/pkg-running/garmin-forerunner-tools.git ] 
thinking that the master branch was updated until the last repackage.


I just see that the patches is inside de Debian/patches and not applied 
to the source code.



So, was me who was seeing a non updated code. I'm sorry. I didn't know 
the Debian workflow.



I'm going to update the code with the patches, and try to say something.



Bug#816314: Fix patch for libusb1.0 update.

2016-04-16 Thread Fenix


Hi.


I have fixed this. There were two problems in usb_comm.c when the 
update to libusb1.0:



	1) It seems libusb1.0 changes the addres of the endpoint to talk to. 
The code made a bit operation that makes the device unachievable.


	2) There were core code of libusb that only was execute with the -v 
(verbose) option, because an incorrect conditional anidation.



   The patch I attach fix the two problems and works for me (now with 
libusb1.0 :P). I have tested garmin_get_info, garmin_save_runs and 
garmin_gpx. If you need more information about this fix, please, feel 
free to ask.




   Thanks. :)
diff --git a/src/usb_comm.c b/src/usb_comm.c
index f00f6d9..9c5afa3 100644
--- a/src/usb_comm.c
+++ b/src/usb_comm.c
@@ -72,9 +72,8 @@ garmin_open ( garmin_unit * garmin )
   }
 }
 cnt = libusb_get_device_list(ctx,&dl);
-
+
 for (i = 0; i < cnt; ++i) {
-  {
 struct libusb_device_descriptor descriptor;
 struct libusb_config_descriptor *config;
 
@@ -97,22 +96,28 @@ garmin_open ( garmin_unit * garmin )
 	  if ( err ) {
 	printf("libusb_open failed: %s\n",libusb_error_name(err));
 garmin->usb.handle = NULL;
-	  } else if ( garmin->verbose != 0 ) {
-	printf("[garmin] libusb_open = %p\n",garmin->usb.handle);
+	  } else {
+	  if ( garmin->verbose != 0 ) {
+printf("[garmin] libusb_open = %p\n",garmin->usb.handle);
+	  }
 
-err = libusb_set_configuration(garmin->usb.handle,1);
+  err = libusb_set_configuration(garmin->usb.handle,1);
 if ( err ) {
-  printf("libusb_set_configuration failed: %s\n",
+printf("libusb_set_configuration failed: %s\n",
  libusb_error_name(err));
-} else if ( garmin->verbose != 0 ) {
-  printf("[garmin] libusb_set_configuration[1] succeeded\n");
+} else {
+		if ( garmin->verbose != 0 ) {
+	  printf("[garmin] libusb_set_configuration[1] succeeded\n");
+		}
 
   err = libusb_claim_interface(garmin->usb.handle,0);
   if ( err ) {
 printf("libusb_claim_interface failed: %s\n",
libusb_error_name(err));
-  } else if ( garmin->verbose != 0 ) {
-printf("[garmin] libusb_claim_interface[0] succeeded\n");
+  } else {
+		if ( garmin->verbose != 0 ) {
+ printf("[garmin] libusb_claim_interface[0] succeeded\n");
+		}
 
 err = libusb_get_config_descriptor_by_value(di,1,&config);
 if ( err ) {
@@ -127,12 +132,10 @@ garmin_open ( garmin_unit * garmin )
   }
 
 	  if ( !err ) {
-
 	/* 
 	   We've succeeded in opening and claiming the interface 
 	   Let's set the bulk and interrupt in and out endpoints. 
 	*/
-
 	for ( i = 0; 
 		  i < config->interface->altsetting->bNumEndpoints;
 		  i++ ) {
@@ -142,25 +145,22 @@ garmin_open ( garmin_unit * garmin )
 	  switch ( ep->bmAttributes & LIBUSB_TRANSFER_TYPE_MASK ) {
 	  case LIBUSB_TRANSFER_TYPE_BULK:
 		if ( ep->bEndpointAddress & LIBUSB_ENDPOINT_DIR_MASK ) {
-		  garmin->usb.bulk_in = 
-		ep->bEndpointAddress & LIBUSB_ENDPOINT_ADDRESS_MASK;
+		  garmin->usb.bulk_in = ep->bEndpointAddress;
 		  if ( garmin->verbose != 0 ) {
-		printf("[garmin] bulk IN  = %d\n",garmin->usb.bulk_in);
+		printf("[garmin] bulk IN  = 0x%02x\n",garmin->usb.bulk_in);
 		  }
 		} else {
-		  garmin->usb.bulk_out = 
-		ep->bEndpointAddress & LIBUSB_ENDPOINT_ADDRESS_MASK;
+		  garmin->usb.bulk_out = ep->bEndpointAddress;
 		  if ( garmin->verbose != 0 ) {
-		printf("[garmin] bulk OUT = %d\n",garmin->usb.bulk_out);
+		printf("[garmin] bulk OUT = 0x%02x\n",garmin->usb.bulk_out);
 		  }
 		}
 		break;
 	  case LIBUSB_TRANSFER_TYPE_INTERRUPT:
 		if ( ep->bEndpointAddress & LIBUSB_ENDPOINT_DIR_MASK ) {
-		  garmin->usb.intr_in = 
-		ep->bEndpointAddress & LIBUSB_ENDPOINT_ADDRESS_MASK;
+		  garmin->usb.intr_in = ep->bEndpointAddress;
 		  if ( garmin->verbose != 0 ) {
-		printf("[garmin] intr IN  = %d\n",garmin->usb.intr_in);
+		printf("[garmin] intr IN  = 0x%02x\n",garmin->usb.intr_in);
 		  }
 		}
 		break;
@@ -174,10 +174,10 @@ garmin_open ( garmin_unit * garmin )
 
 	  break;
 	}
-  }
 
   if ( garmin->usb.handle != NULL ) break;
 }
+
 libusb_free_device_list (dl, 1);
   }
 
@@ -187,6 +187,7 @@ garmin_open ( garmin_unit * garmin )
  it to NULL.
   */
 
+
   if ( garmin->usb.handle != NULL && err != 0 ) {
 if ( garmin->verbose != 0 ) {
   printf("[garmin] (err = %d) libusb_close(%p)\n",err,garmin->usb.handle);
@@ -273,6 +274,7 @@ garmin_read ( garmin_unit * garmin, garmin_packet * p )
 sizeof(garmin_packet),
 &r,
 INTR_TIMEOUT);
+
   /* 
 	 If the packet is a "Pid_Data_Available" packet, we need to read
 	 from the 

Bug#816314: [Pkg-running-devel] Bug#816314: Fix patch for libusb1.0 update.

2016-04-17 Thread Fenix

Hi. I comment beween quotes. :)



On 17/04/16 09:26, Christian PERRIER wrote:



@@ -97,22 +96,28 @@ garmin_open ( garmin_unit * garmin )
  if ( err ) {
printf("libusb_open failed: %s\n",libusb_error_name(err));
  garmin->usb.handle = NULL;
- } else if ( garmin->verbose != 0 ) {
-   printf("[garmin] libusb_open = %p\n",garmin->usb.handle);
+ } else {
+ if ( garmin->verbose != 0 ) {
+printf("[garmin] libusb_open = %p\n",garmin->usb.handle);
+ }


I'm not really skilled in C, but isn't that just cosmetic?



   No, it isn't just cosmetic. The problem is that structure is a bit 
ugly (I agree). Original makes:



if (error) {
[...]
} else if (only_execute_when_user_wants_verbosity) {
 print message
 err = execute_core_function_libusb

 if (err) {
  [...]
 } else if (only_execute_when_user_wants_verbosity) {
  [...]
 }
}


In that situation, the function (execute_core_function_libusb) of 
libusb library only are executed when the user runs the program with -v 
main parameter (wants verbosity).


You could safe the {} of the if (verbosity] condition as it is just 
contain one sentence. Make something like:



   if (error) {
   } else {
   if (verbosity) print message
   err = execute_core_function_libusb

   if (err) {
   [...]
   } else {
 if (verbosity) print message
 err = execute_core_function_libusb
   }
   }


   But I prefer mark the block of code with {} for readbility, 
specially in that situation.


   I'm not skilled C programmer, too (I used lng time ago :)), but 
I probably didn't make that structure. I'd just make:



   If (error) {
  [...]
   } else {
  if (verbosity) print message
  err = execute_core_function_1_libusb
   }

   If (not error) {
 if (verbosity) print message
 err = execute_core_function__n_libusb
   }


   Probably is better for readbility, but it is less efficient. So, I 
preferred to maintain the original structure and make a "quick fix".








-err = libusb_set_configuration(garmin->usb.handle,1);
+  err = libusb_set_configuration(garmin->usb.handle,1);


Ditto


  if ( err ) {
-  printf("libusb_set_configuration failed: %s\n",
+printf("libusb_set_configuration failed: %s\n",


Ditto

And so on

I'd be happy to apply the patch, of course, but do you think that it
can be "cleaned"?

I can try to do it myself but..I'm a bit afraid to break things
doing so.





  I agree. Of course can be cleaned. :)

  I can clean the non-functional cosmetic (unintentional from me) 
changes of the patch: lines, blanks...



  Maybe you want to add to this conversation the person who makes the 
libusb1.0 port as I'm not skilled with libusb (only learned the needed 
to make this fix). As I said, the fix works for me and the tests I made 
goes fine, but maybe there is something I did not consider.




  I'll try to make the re-patch along today.



  Thanks. :)



Bug#816314: Fix patch v2 for libusb1.0 update.

2016-04-17 Thread Fenix


Hi.

I attach the previous patch cleaned of unfunctional cosmetic changes.

As I said in my previous message, I maintain the complex anidation 
of the original conditional structure. It is ugly, but it works. Anyway, 
if you think it should be refactor, we can make it a bit more readable.


   So, I'm keeping from previuos patch (libusb1.0_fix.patch):

   1) The elimination of a duplicate mark of block {} in the main for 
(this is cosmetic but is really ugly keep it. :))


   2) The changes for the else block in the conditional blocks 
(Functional change).


   3) The changes that pass the new (for libusb1.0) endpoints 
directions of the device (functional change). In this, I change too the 
printed messages for a better understanding for verbose purpose 
(cosmetic but I think it's neccesary for good verbosity).




   If you have any question or suggestion, please, feel free to ask.

   As I said in my last message, could be a good idea that the original 
patcher of the port to libusb1.0 checks this patch. I suppose he is 
experience with libusb, and I could overlook something related with.



   Thanks.  :)
diff --git a/src/usb_comm.c b/src/usb_comm.c
index f00f6d9..8931f09 100644
--- a/src/usb_comm.c
+++ b/src/usb_comm.c
@@ -74,7 +74,6 @@ garmin_open ( garmin_unit * garmin )
 cnt = libusb_get_device_list(ctx,&dl);
 
 for (i = 0; i < cnt; ++i) {
-  {
 struct libusb_device_descriptor descriptor;
 struct libusb_config_descriptor *config;
 
@@ -97,22 +96,28 @@ garmin_open ( garmin_unit * garmin )
 	  if ( err ) {
 	printf("libusb_open failed: %s\n",libusb_error_name(err));
 garmin->usb.handle = NULL;
-	  } else if ( garmin->verbose != 0 ) {
-	printf("[garmin] libusb_open = %p\n",garmin->usb.handle);
+	  } else {
+	  if ( garmin->verbose != 0 ) {
+printf("[garmin] libusb_open = %p\n",garmin->usb.handle);
+	  }
 
 err = libusb_set_configuration(garmin->usb.handle,1);
 if ( err ) {
   printf("libusb_set_configuration failed: %s\n",
  libusb_error_name(err));
-} else if ( garmin->verbose != 0 ) {
-  printf("[garmin] libusb_set_configuration[1] succeeded\n");
+} else {
+		if ( garmin->verbose != 0 ) {
+	  printf("[garmin] libusb_set_configuration[1] succeeded\n");
+		}
 
   err = libusb_claim_interface(garmin->usb.handle,0);
   if ( err ) {
 printf("libusb_claim_interface failed: %s\n",
libusb_error_name(err));
-  } else if ( garmin->verbose != 0 ) {
-printf("[garmin] libusb_claim_interface[0] succeeded\n");
+  } else {
+		if ( garmin->verbose != 0 ) {
+ printf("[garmin] libusb_claim_interface[0] succeeded\n");
+		}
 
 err = libusb_get_config_descriptor_by_value(di,1,&config);
 if ( err ) {
@@ -142,25 +147,22 @@ garmin_open ( garmin_unit * garmin )
 	  switch ( ep->bmAttributes & LIBUSB_TRANSFER_TYPE_MASK ) {
 	  case LIBUSB_TRANSFER_TYPE_BULK:
 		if ( ep->bEndpointAddress & LIBUSB_ENDPOINT_DIR_MASK ) {
-		  garmin->usb.bulk_in = 
-		ep->bEndpointAddress & LIBUSB_ENDPOINT_ADDRESS_MASK;
+		  garmin->usb.bulk_in = ep->bEndpointAddress;
 		  if ( garmin->verbose != 0 ) {
-		printf("[garmin] bulk IN  = %d\n",garmin->usb.bulk_in);
+		printf("[garmin] bulk IN  = 0x%02x\n",garmin->usb.bulk_in);
 		  }
 		} else {
-		  garmin->usb.bulk_out = 
-		ep->bEndpointAddress & LIBUSB_ENDPOINT_ADDRESS_MASK;
+		  garmin->usb.bulk_out = ep->bEndpointAddress;
 		  if ( garmin->verbose != 0 ) {
-		printf("[garmin] bulk OUT = %d\n",garmin->usb.bulk_out);
+		printf("[garmin] bulk OUT = 0x%02x\n",garmin->usb.bulk_out);
 		  }
 		}
 		break;
 	  case LIBUSB_TRANSFER_TYPE_INTERRUPT:
 		if ( ep->bEndpointAddress & LIBUSB_ENDPOINT_DIR_MASK ) {
-		  garmin->usb.intr_in = 
-		ep->bEndpointAddress & LIBUSB_ENDPOINT_ADDRESS_MASK;
+		  garmin->usb.intr_in = ep->bEndpointAddress;
 		  if ( garmin->verbose != 0 ) {
-		printf("[garmin] intr IN  = %d\n",garmin->usb.intr_in);
+		printf("[garmin] intr IN  = 0x%02x\n",garmin->usb.intr_in);
 		  }
 		}
 		break;
@@ -174,7 +176,6 @@ garmin_open ( garmin_unit * garmin )
 
 	  break;
 	}
-  }
 
   if ( garmin->usb.handle != NULL ) break;
 }


Bug#947361: krita: Keyboard doesn't respond after some popups (f.e show color selector) are opened.

2020-12-24 Thread Fenix
Package: krita
Followup-For: Bug #947361
X-Debbugs-Cc: fenix...@gmail.com

Dear Maintainer,

I've just checked this issue in current Debian Testing Krita version and it was
fixed.

I'm closing this issue.


Thanks!



-- System Information:
Debian Release: bullseye/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 5.9.0-5-amd64 (SMP w/12 CPU threads)
Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages krita depends on:
ii  krita-data1:4.4.1+dfsg-1
ii  libc6 2.31-5
ii  libexiv2-27   0.27.3-3
ii  libfftw3-double3  3.3.8-2
ii  libgcc-s1 10.2.1-1
ii  libgif7   5.1.9-1
ii  libgsl25  2.6+dfsg-2
ii  libheif1  1.9.1-1
ii  libilmbase25  2.5.3-2
ii  libjpeg62-turbo   1:2.0.5-1.1
ii  libkf5completion5 5.74.0-2
ii  libkf5configcore5 5.74.0-2
ii  libkf5configgui5  5.74.0-2
ii  libkf5coreaddons5 5.74.0-2
ii  libkf5crash5  5.74.0-2
ii  libkf5guiaddons5  5.74.0-3
ii  libkf5i18n5   5.74.0-3
ii  libkf5itemviews5  5.74.0-2
ii  libkf5widgetsaddons5  5.74.0-3
ii  libkf5windowsystem5   5.74.0-2
ii  liblcms2-22.9-4+b1
ii  libopencolorio1v5 1.1.1~dfsg0-7
ii  libopenexr25  2.5.3-2
ii  libopenjp2-7  2.3.1-1
ii  libpng16-16   1.6.37-3
ii  libpoppler-qt5-1  20.09.0-3
ii  libpython3.9  3.9.1-1
ii  libqt5concurrent5 5.15.2+dfsg-2
ii  libqt5core5a  5.15.2+dfsg-2
ii  libqt5dbus5   5.15.2+dfsg-2
ii  libqt5gui55.15.2+dfsg-2
ii  libqt5multimedia5 5.15.2-2
ii  libqt5network55.15.2+dfsg-2
ii  libqt5printsupport5   5.15.2+dfsg-2
ii  libqt5qml55.15.2+dfsg-2
ii  libqt5quick5  5.15.2+dfsg-2
ii  libqt5quickwidgets5   5.15.2+dfsg-2
ii  libqt5svg55.15.2-2
ii  libqt5widgets55.15.2+dfsg-2
ii  libqt5x11extras5  5.15.2-2
ii  libqt5xml55.15.2+dfsg-2
ii  libquazip5-1  0.9.1-1
ii  libraw20  0.20.2-1
ii  libstdc++610.2.1-1
ii  libtiff5  4.1.0+git201212-1
ii  libx11-6  2:1.6.12-1
ii  zlib1g1:1.2.11.dfsg-2

Versions of packages krita recommends:
ii  krita-gmic   2.4.5-1.1+b1
ii  python3-pyqt55.15.2+dfsg-1+b1
ii  python3-sip  4.19.24+dfsg-1+b2
ii  qml-module-qtmultimedia  5.15.2-2

Versions of packages krita suggests:
ii  colord  1.4.4-2
ii  ffmpeg  7:4.3.1-5
pn  krita-l10n  

-- no debconf information



Bug#947361: krita: Keyboard doesn't respond after some popups (f.e show color selector) are opened.

2019-12-25 Thread Fenix

Package: krita
Version: 1:4.2.8.2+dfsg-1
Severity: normal

Dear Maintainer,

Krita seems to have problems with some popups docks, for example 
color selector, minimal shade selector... After this controls are showed 
if they are hidden just moving the pointer outside its domain, keyboard 
doesn't respond anymore, unless you change to another program or window.


Brush preset, for example, works fine. This type of popup are close
clicking outside and not just moving pointer outside.


   * What led up to the situation?

1.- Create new image.
2.- Open, for example, a color selector (Shift + I)
3.- Select a color and move the cursor outside the selector. It 
will be vanished.
4.- Try to open again the color selector with Shift + I or made 
something with keyboard: change to full screen, undo action (ctrl-z)...

5.- The keyboard will not repond.
6.- Change to another program and back to Krita (Krita must lost the
focus).
7.- Try again show color selector (Shift + I). It will work again.


   * What exactly did you do (or not do) that was effective (or
 ineffective)?

If enter key is pressed just before choosing color in color 
selector and with the pointer inside the control (for not hide it), the 
keyboard works fine: accept other shourtuts. But if the popup is hide 
only moving the pointer outside its domain, the keyboard will be stucked 
into Krita. And only come back after loosing the focus into another 
program or window.




Thanks.



-- System Information:
Debian Release: bullseye/sid
  APT prefers testing-debug
  APT policy: (500, 'testing-debug'), (500, 'testing')
Architecture: i386 (i686)

Kernel: Linux 5.3.0-3-686-pae (SMP w/2 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=es_ES.utf8, LC_CTYPE=es_ES.utf8 (charmap=UTF-8), 
LANGUAGE=es_ES.utf8 (charmap=UTF-8)

Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages krita depends on:
ii  krita-data 1:4.2.8.2+dfsg-1
ii  libboost-system1.67.0  1.67.0-13+b1
ii  libc6  2.29-3
ii  libexiv2-140.25-4
ii  libfftw3-double3   3.3.8-2
ii  libgcc11:9.2.1-21
ii  libgif75.1.9-1
ii  libgsl23   2.5+dfsg-6+b1
ii  libheif1   1.6.0-1
ii  libilmbase24   2.3.0-6
ii  libjpeg62-turbo1:1.5.2-2+b1
ii  libkf5archive5 5.62.0-1
ii  libkf5completion5  5.62.0-1+b1
ii  libkf5configcore5  5.62.0-1+b1
ii  libkf5configgui5   5.62.0-1+b1
ii  libkf5coreaddons5  5.62.0-1
ii  libkf5crash5   5.62.0-1+b1
ii  libkf5guiaddons5   5.62.0-2
ii  libkf5i18n55.62.0-1
ii  libkf5itemviews5   5.62.0-1+b1
ii  libkf5widgetsaddons5   5.62.0-1+b1
ii  libkf5windowsystem55.62.0-2+b1
ii  liblcms2-2 2.9-3+b1
ii  libopencolorio1v5  1.1.1~dfsg0-5
ii  libopenexr24   2.3.0-6
ii  libpng16-161.6.37-1
ii  libpoppler-qt5-1   0.71.0-6
ii  libpython3.7   3.7.5-2
ii  libqt5concurrent5  5.12.5+dfsg-2
ii  libqt5core5a   5.12.5+dfsg-2
ii  libqt5dbus55.12.5+dfsg-2
ii  libqt5gui5 5.12.5+dfsg-2
ii  libqt5multimedia5  5.12.5-1
ii  libqt5network5 5.12.5+dfsg-2
ii  libqt5printsupport55.12.5+dfsg-2
ii  libqt5qml5 5.12.5-3
ii  libqt5quick5   5.12.5-3
ii  libqt5quickwidgets55.12.5-3
ii  libqt5svg5 5.12.5-2
ii  libqt5widgets5 5.12.5+dfsg-2
ii  libqt5x11extras5   5.12.5-1
ii  libqt5xml5 5.12.5+dfsg-2
ii  libquazip5-1   0.7.6-6
ii  libraw19   0.19.5-1
ii  libstdc++6 9.2.1-21
ii  libtiff5   4.1.0+git191117-1
ii  libx11-6   2:1.6.8-1
ii  zlib1g 1:1.2.11.dfsg-1+b1

Versions of packages krita recommends:
ii  krita-gmic   2.4.5-1+b1
ii  python3-pyqt55.13.2+dfsg-1
ii  python3-sip  4.19.19+dfsg-2+b1
ii  qml-module-qtmultimedia  5.12.5-1

Versions of packages krita suggests:
ii  colord  1.4.3-4
ii  ffmpeg  7:4.2.1-2
pn  krita-l10n  

-- no debconf information



Bug#934038: ASSERT: "mImg == qImg->constBits()" in file common.cpp, line 63

2019-09-28 Thread Fenix

Package: kdenlive
Version: 19.08.1-2
Followup-For: Bug #934038

Dear Maintainer,

I'm be able to reproduce this error following the OP steps:

1.- Open Kdenlive.
2.- Add a title clip.
3.- Create a text label.
4.- Press OK

I get the same error and Kdenlive die.

I attach debug info and backtrace:

---
:~$ gdb kdenlive
GNU gdb (Debian 8.3-1) 8.3
Copyright (C) 2019 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 


This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "i686-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.

For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from kdenlive...
Reading symbols from /usr/lib/debug/.build-
id/98/a3e4a1cb2ea19fe8b08e997af4a2532590b1fb.debug...
(gdb) run
Starting program: /usr/bin/kdenlive
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/i386-linux-gnu/libthread_db.so.1".
[New Thread 0xabda0b40 (LWP 5927)]
[New Thread 0xaaba3b40 (LWP 5928)]
[New Thread 0xa9299b40 (LWP 5929)]
[New Thread 0xa88ffb40 (LWP 5930)]
[New Thread 0xa78ebb40 (LWP 5931)]
WARNING : Fails to parse  "avcolour_space"
WARNING : Fails to parse  "avcolor_space"
WARNING : Fails to parse  "avdeinterlace"
WARNING : Fails to parse  "swscale"
"avfilter.abench" is blacklisted
"avfilter.acompressor" is blacklisted
"avfilter.adelay" is blacklisted
"avfilter.aecho" is blacklisted
"avfilter.aemphasis" is blacklisted
"avfilter.aeval" is blacklisted
"avfilter.afade" is blacklisted
"avfilter.afftfilt" is blacklisted
"avfilter.agate" is blacklisted
"avfilter.ametadata" is blacklisted
"avfilter.arealtime" is blacklisted
"avfilter.ashowinfo" is blacklisted
"avfilter.channelmap" is blacklisted
"avfilter.chorus" is blacklisted
"avfilter.earwax" is blacklisted
"avfilter.volume" is blacklisted
"avfilter.volumedetect" is blacklisted
"avfilter.ass" is blacklisted
"avfilter.atadenoise" is blacklisted
"avfilter.avgblur" is blacklisted
"avfilter.bbox" is blacklisted
"avfilter.bench" is blacklisted
"avfilter.blackdetect" is blacklisted
"avfilter.blackframe" is blacklisted
"avfilter.boxblur" is blacklisted
"avfilter.bwdif" is blacklisted
"avfilter.chromakey" is blacklisted
"avfilter.colorkey" is blacklisted
"avfilter.colormatrix" is blacklisted
"avfilter.colorspace" is blacklisted
"avfilter.convolution" is blacklisted
"avfilter.crop" is blacklisted
"avfilter.cropdetect" is blacklisted
"avfilter.curves" is blacklisted
"avfilter.datascope" is blacklisted
"avfilter.dctdnoiz" is blacklisted
"avfilter.deband" is blacklisted
"avfilter.deflate" is blacklisted
"avfilter.deinterlace_vaapi" is blacklisted
"avfilter.deshake" is blacklisted
"avfilter.despill" is blacklisted
"avfilter.doubleweave" is blacklisted
"avfilter.drawbox" is blacklisted
"avfilter.drawgraph" is blacklisted
"avfilter.drawgrid" is blacklisted
"avfilter.drawtext" is blacklisted
"avfilter.elbg" is blacklisted
"avfilter.eq" is blacklisted
"avfilter.fade" is blacklisted
"avfilter.field" is blacklisted
"avfilter.fieldhint" is blacklisted
"avfilter.fieldorder" is blacklisted
"avfilter.find_rect" is blacklisted
"avfilter.floodfill" is blacklisted
"avfilter.fspp" is blacklisted
"avfilter.gblur" is blacklisted
"avfilter.geq" is blacklisted
"avfilter.hflip" is blacklisted
"avfilter.hqdn3d" is blacklisted
"avfilter.hqx" is blacklisted
"avfilter.hue" is blacklisted
"avfilter.hwdownload" is blacklisted
"avfilter.idet" is blacklisted
"avfilter.il" is blacklisted
"avfilter.lenscorrection" is blacklisted
"avfilter.loop" is blacklisted
"avfilter.lumakey" is blacklisted
"avfilter.lut" is blacklisted
"avfilter.lutrgb" is blacklisted
"avfilter.lutyuv" is blacklisted
"avfilter.mcdeint" is blacklisted
"avfilter.metadata" is blacklisted
"avfilter.negate" is blacklisted
"avfilter.nlmeans" is blacklisted
"avfilter.nnedi" is blacklisted
"avfilter.owdenoise" is blacklisted
"avfilter.pad" is blacklisted
"avfilter.perspective" is blacklisted
"avfilter.phase" is blacklisted
"avfilter.pixscope" is blacklisted
"avfilter.pp" is blacklisted
"avfilter.pp7" is blacklisted
"avfilter.prewitt" is blacklisted
"avfilter.realtime" is blacklisted
"avfilter.removegrain" is blacklisted
"avfilter.removelogo" is blacklisted
"avfilter.roberts" is blacklisted
"avfilter.rotate" is blacklisted
"avfilter.scale_vaapi" is blacklisted
"avfilter.showinfo" is blacklisted
"avfilter.shuffleframes" is blacklisted
"avfilter.sidedata" is blacklisted
"avfilter.signalstats" is blacklisted
"avfilter.sobel" is blacklisted
"avfilter.stereo3d" is blacklisted
"avfilter.super2xsai" is blacklisted
"avfilter.swapuv" is blacklisted
"a

Bug#939121: blender: Crash on init

2019-09-01 Thread Fenix

Package: blender
Version: 2.80+dfsg-3
Severity: important

Dear Maintainer,

After 2.80 upgrade Blender crash on init showing this messages:


Normal console execution:

---
fenix@calisto:~$ blender
blender(BLI_system_backtrace+0x37) [0x1298bd7]
blender(+0x157daea) [0x1a79aea]
blender(draw_outliner+0x864) [0x1a7c704]
blender(+0x1587307) [0x1a83307]
blender(ED_region_do_draw+0x88b) [0x19e5e3b]
blender(wm_draw_update+0x480) [0x14a75f0]
blender(WM_main+0x41) [0x14a4a61]
blender(main+0x2e5) [0x10247f5]
/lib/i386-linux-gnu/libc.so.6(__libc_start_main+0xf1) [0xb3e22b41]
blender(_start+0x31) [0x1059271]
BLI_assert failed: /build/blender-
kMunq6/blender-2.80+dfsg/source/blender/editors/space_outliner/outliner_draw.c:1032,
outliner_draw_restrictbuts(), at '(restrict_column_offset * ((void)0,
U.widget_unit) + (0.45f * U.widget_unit)) ==
outliner_restrict_columns_width(soops)'
Abortado
---


Factory settings

---
fenix@calisto:~$ blender --factory-startup
blender(BLI_system_backtrace+0x37) [0x11e8bd7]
blender(+0x157daea) [0x19c9aea]
blender(draw_outliner+0x864) [0x19cc704]
blender(+0x1587307) [0x19d3307]
blender(ED_region_do_draw+0x88b) [0x1935e3b]
blender(wm_draw_update+0x480) [0x13f75f0]
blender(WM_main+0x41) [0x13f4a61]
blender(main+0x2e5) [0xf747f5]
/lib/i386-linux-gnu/libc.so.6(__libc_start_main+0xf1) [0xb3e78b41]
blender(_start+0x31) [0xfa9271]
BLI_assert failed: 
/build/blender-kMunq6/blender-2.80+dfsg/source/blender/editors/space_outliner/outliner_draw.c:1032, 
outliner_draw_restrictbuts(), at '(restrict_column_offset * ((void)0, 
U.widget_unit) + (0.45f * U.widget_unit)) == 
outliner_restrict_columns_width(soops)'

Abortado

---



With debug messages:
---
fenix@calisto:~$ blender -d --debug-all --log-level -1
Switching to fully guarded memory allocator.
Blender 2.80 (sub 75)
argv[0] = blender
argv[1] = -d
argv[2] = --debug-all
argv[3] = --log-level
argv[4] = -1

Note: No (valid) '/home/fenix/.config/blender/2.80/config/startup.blend' 
found,

fall back to built-in default.

read file
  Version 280 sub 39 date unknown hash unknown
graph_id_tag_update: id=SCScene flags=LEGACY_0 source=USER_EDIT
ED_screen_refresh: set screen
graph_id_tag_update: id=SCScene flags=COPY_ON_WRITE source=RELATIONS
graph_id_tag_update: id=OBCube flags=TRANSFORM, GEOMETRY, COPY_ON_WRITE
source=RELATIONS
graph_id_tag_update: id=MECube flags=LEGACY_0 source=RELATIONS
graph_id_tag_update: id=MECube flags=COPY_ON_WRITE source=RELATIONS
graph_id_tag_update: id=MAMaterial flags=COPY_ON_WRITE source=RELATIONS
graph_id_tag_update: id=NTShader Nodetree flags=COPY_ON_WRITE 
source=RELATIONS
graph_id_tag_update: id=NTShader Nodetree flags=COPY_ON_WRITE 
source=RELATIONS

graph_id_tag_update: id=OBLight flags=TRANSFORM, GEOMETRY, COPY_ON_WRITE
source=RELATIONS
graph_id_tag_update: id=LALight flags=COPY_ON_WRITE source=RELATIONS
graph_id_tag_update: id=OBCamera flags=TRANSFORM, GEOMETRY, COPY_ON_WRITE
source=RELATIONS
graph_id_tag_update: id=CACamera flags=COPY_ON_WRITE source=RELATIONS
graph_id_tag_update: id=GRMaster Collection flags=COPY_ON_WRITE
source=RELATIONS
graph_id_tag_update: id=GRCollection flags=COPY_ON_WRITE source=RELATIONS
graph_id_tag_update: id=WOWorld flags=COPY_ON_WRITE source=RELATIONS
graph_id_tag_update: id=NTShader Nodetree flags=COPY_ON_WRITE 
source=RELATIONS
graph_id_tag_update: id=NTShader Nodetree flags=COPY_ON_WRITE 
source=RELATIONS

graph_id_tag_update: id=SCScene flags=COPY_ON_WRITE source=VISIBILITY
graph_id_tag_update: id=OBCube flags=TRANSFORM, GEOMETRY, COPY_ON_WRITE
source=VISIBILITY
graph_id_tag_update: id=MECube flags=LEGACY_0 source=VISIBILITY
graph_id_tag_update: id=MECube flags=COPY_ON_WRITE source=VISIBILITY
graph_id_tag_update: id=MAMaterial flags=COPY_ON_WRITE source=VISIBILITY
graph_id_tag_update: id=NTShader Nodetree flags=COPY_ON_WRITE 
source=VISIBILITY
graph_id_tag_update: id=NTShader Nodetree flags=COPY_ON_WRITE 
source=VISIBILITY

graph_id_tag_update: id=OBLight flags=TRANSFORM, GEOMETRY, COPY_ON_WRITE
source=VISIBILITY
graph_id_tag_update: id=LALight flags=COPY_ON_WRITE source=VISIBILITY
graph_id_tag_update: id=OBCamera flags=TRANSFORM, GEOMETRY, COPY_ON_WRITE
source=VISIBILITY
graph_id_tag_update: id=CACamera flags=COPY_ON_WRITE source=VISIBILITY
graph_id_tag_update: id=GRMaster Collection flags=COPY_ON_WRITE
source=VISIBILITY
graph_id_tag_update: id=GRCollection flags=COPY_ON_WRITE source=VISIBILITY
graph_id_tag_update: id=WOWorld flags=COPY_ON_WRITE source=VISIBILITY
graph_id_tag_update: id=NTShader Nodetree flags=COPY_ON_WRITE 
source=VISIBILITY
graph_id_tag_update: id=NTShader Nodetree flags=COPY_ON_WRITE 
source=VISIBILITY

Depsgraph built in 0.001231 seconds.
graph_id_tag_update: id=SCScene flags=COPY_ON_WRITE source=VISIBILITY
graph_id_tag_update: id=OBCube flags=TRANSFORM, GEOMETRY, COPY_ON_WRITE
source=VISIBILITY
graph_id_tag_update: id=MECube flags=LEGACY_0 source=VISIBILITY
graph_id_tag_update: id=MECube flags=COPY_ON_WRITE source=VISIBILITY
grap

Bug#939121: blender: Crash on init

2019-09-01 Thread Fenix

Followup-For: Bug #939121
Package: blender
Version: 2.80+dfsg-3

Dear Maintainer,

   Maybe this can help. I've downloaded upstream compilation and that 
version is starting fine:



Version:

---
fenix@calisto:~/Aplicaciones/blender-2.80-linux-glibc224-i686$ ./blender -v
Blender 2.80 (sub 75)
build date: 2019-07-29
build time: 15:18:54
build commit date: 2019-07-29
build commit time: 14:47
build hash: f6cb5f54494e
build platform: Linux
build type: Release
build c flags:  -Wall -Wcast-align -Werror=implicit-function-
declaration -Werror=return-type -Werror=vla -Wstrict-prototypes -Wmissing-
prototypes -Wno-char-subscripts -Wno-unknown-pragmas -Wpointer-arith 
-Wunused-
parameter -Wwrite-strings -Wlogical-op -Wundef -Winit-self -Wnonnull 
-Wmissing-
include-dirs -Wno-div-by-zero -Wtype-limits -Wformat-signedness 
-Wuninitialized

-Wredundant-decls -Wshadow -Wno-error=unused-but-set-variable  -fuse-ld=gold
-std=gnu11   -msse -pipe -fPIC -funsigned-char -fno-strict-aliasing -msse2
build c++ flags:  -Wredundant-decls -Wall -Wno-invalid-offsetof 
-Wno-
sign-compare -Wlogical-op -Winit-self -Wmissing-include-dirs 
-Wno-div-by-zero
-Wtype-limits -Werror=return-type -Werror=implicit-function-declaration 
-Wno-

char-subscripts -Wno-unknown-pragmas -Wpointer-arith -Wunused-parameter
-Wwrite-strings -Wundef -Wformat-signedness -Wuninitialized -Wundef 
-Wmissing-

declarations  -fuse-ld=gold -std=c++11   -msse -pipe -fPIC -funsigned-char
-fno-strict-aliasing -msse2
build link flags:  -Wl,--version-script='/home/sources/blender-
release/source/creator/blender.map'
build system: CMake


Execution:

---
fenix@calisto:~/Aplicaciones/blender-2.80-linux-glibc224-i686$ ./blender
found bundled python: /home/fenix/Aplicaciones/blender-2.80-linux-
glibc224-i686/2.80/python
---



Thanks.



-- System Information:
Debian Release: bullseye/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)

Kernel: Linux 5.2.0-2-686-pae (SMP w/2 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=es_ES.utf8, LC_CTYPE=es_ES.utf8 (charmap=UTF-8), 
LANGUAGE=es_ES.utf8 (charmap=UTF-8)

Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages blender depends on:
ii  blender-data  2.80+dfsg-3
ii  fonts-dejavu  2.37-1
ii  libavcodec58  10:4.2-dmo1
ii  libavdevice58 10:4.2-dmo1
ii  libavformat58 10:4.2-dmo1
ii  libavutil56   10:4.2-dmo1
ii  libboost-locale1.67.0 1.67.0-13
ii  libc6 2.28-10
ii  libfftw3-double3  3.3.8-2
ii  libfreetype6  2.9.1-4
ii  libgcc1   1:9.2.1-4
ii  libgl11.1.0-1+b1
ii  libglew2.12.1.0-4+b1
ii  libgomp1  9.2.1-4
ii  libilmbase23  2.2.1-2+b1
ii  libjack-jackd2-0 [libjack-0.125]  1.9.12~dfsg-2+b1
ii  libjemalloc2  5.1.0-3
ii  libjpeg62-turbo   1:1.5.2-2+b1
ii  libopenal11:1.19.1-1+b1
ii  libopencolorio1v5 1.1.1~dfsg0-3
ii  libopenexr23  2.2.1-4.1+b1
ii  libopenimageio2.0 2.0.10~dfsg0-1
ii  libopenjp2-7  2.3.0-2
ii  libopenvdb5.2 5.2.0-5.1
ii  libpcre3  2:8.39-12+b1
ii  libpng16-16   1.6.37-1
ii  libpython3.7  3.7.4-3
ii  libsndfile1   1.0.28-6
ii  libspnav0 0.2.3-1+b2
ii  libstdc++69.2.1-4
ii  libswscale5   10:4.2-dmo1
ii  libtbb2   2019~U8-1
ii  libtiff5  4.0.10+git190818-1
ii  libx11-6  2:1.6.7-1
ii  libxfixes31:5.0.3-1
ii  libxi62:1.7.9-1
ii  libxml2   2.9.4+dfsg1-7+b3
ii  libxxf86vm1   1:1.1.4-1+b2
ii  zlib1g1:1.2.11.dfsg-1+b1

blender recommends no packages.

blender suggests no packages.

-- no debconf information



Bug#939121: blender: Crash on init

2019-09-02 Thread Fenix

On 2/9/19 4:32, Philip Chung wrote:


On 9/1/19 4:49 AM, Fenix wrote:

Package: blender
Version: 2.80+dfsg-3
Severity: important

Dear Maintainer,

 After 2.80 upgrade Blender crash on init showing this messages:

[...]

ii  libavcodec58  10:4.2-dmo1
ii  libavdevice58 10:4.2-dmo1
ii  libavformat58 10:4.2-dmo1
ii  libavutil56   10:4.2-dmo1
[...]
ii  libswscale5   10:4.2-dmo1


Your FFmpeg packages are from deb-multimedia.org ("dmo" version
numbers). These are third-party packages that are known to cause
problems with other programs. [1]

Please try installing the official packages from testing by explicitly
specifying the version to apt-get:



Hi, Philip. Thanks for your comment.

Yes, I was aware about DMO packages.

I've installed official libav packages but I'm afraid the problem 
persists in the same way:



---
fenix@calisto:~$ blender
blender(BLI_system_backtrace+0x37) [0x125bbd7]
blender(+0x157daea) [0x1a3caea]
blender(draw_outliner+0x864) [0x1a3f704]
blender(+0x1587307) [0x1a46307]
blender(ED_region_do_draw+0x88b) [0x19a8e3b]
blender(wm_draw_update+0x480) [0x146a5f0]
blender(WM_main+0x41) [0x1467a61]
blender(main+0x2e5) [0xfe77f5]
/lib/i386-linux-gnu/libc.so.6(__libc_start_main+0xf1) [0xb3f7bb41]
blender(_start+0x31) [0x101c271]
BLI_assert failed: 
/build/blender-kMunq6/blender-2.80+dfsg/source/blender/editors/space_outliner/outliner_draw.c:1032, 
outliner_draw_restrictbuts(), at '(restrict_column_offset * ((void)0, 
U.widget_unit) + (0.45f * U.widget_unit)) == 
outliner_restrict_columns_width(soops)'

Abortado

---



The abort is just trying to running and seems related with the 
outliner, as far as I know it is anything with video codecs.




I attach debug information:

---
fenix@calisto:~$ gdb /usr/bin/blender
GNU gdb (Debian 8.3-1) 8.3
Copyright (C) 2019 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
<http://gnu.org/licenses/gpl.html>

This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "i686-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.

For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /usr/bin/blender...
Reading symbols from 
/usr/lib/debug/.build-id/ed/2fa1e95845d3d4739199fa078faf0c0953bd61.debug...

run
(gdb) run
Starting program: /usr/bin/blender
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/i386-linux-gnu/libthread_db.so.1".
[New Thread 0xa3dffb40 (LWP 3138)]
[New Thread 0xa31e7b40 (LWP 3139)]
[New Thread 0xa1501b40 (LWP 3140)]
[New Thread 0xa0d00b40 (LWP 3141)]
[New Thread 0x9fccbb40 (LWP 3142)]
[New Thread 0x9f9ffb40 (LWP 3143)]
[Thread 0x9fccbb40 (LWP 3142) exited]
[New Thread 0x9f1feb40 (LWP 3144)]
[Thread 0x9f1feb40 (LWP 3144) exited]
[New Thread 0x9f1feb40 (LWP 3145)]
[New Thread 0x8e9a4b40 (LWP 3146)]
[New Thread 0x8e7a3b40 (LWP 3147)]
[New Thread 0x8d36fb40 (LWP 3148)]
/usr/bin/blender(BLI_system_backtrace+0x37) [0x119cbd7]
/usr/bin/blender(+0x157daea) [0x197daea]
/usr/bin/blender(draw_outliner+0x864) [0x1980704]
/usr/bin/blender(+0x1587307) [0x1987307]
/usr/bin/blender(ED_region_do_draw+0x88b) [0x18e9e3b]
/usr/bin/blender(wm_draw_update+0x480) [0x13ab5f0]
/usr/bin/blender(WM_main+0x41) [0x13a8a61]
/usr/bin/blender(main+0x2e5) [0xf287f5]
/lib/i386-linux-gnu/libc.so.6(__libc_start_main+0xf1) [0xb3f90b41]
/usr/bin/blender(_start+0x31) [0xf5d271]
BLI_assert failed: 
/build/blender-kMunq6/blender-2.80+dfsg/source/blender/editors/space_outliner/outliner_draw.c:1032, 
outliner_draw_restrictbuts(), at '(restrict_column_offset * ((void)0, 
U.widget_unit) + (0.45f * U.widget_unit)) == 
outliner_restrict_columns_width(soops)'


Thread 1 "blender" received signal SIGABRT, Aborted.
0xb7fd5871 in __kernel_vsyscall ()
(gdb) bt
#0  0xb7fd5871 in __kernel_vsyscall ()
#1  0xb3fa5382 in __libc_signal_restore_set (set=0xbfffec3c)
at ../sysdeps/unix/sysv/linux/internal-signals.h:84
#2  0xb3fa5382 in __GI_raise (sig=6) at 
../sysdeps/unix/sysv/linux/raise.c:48

#3  0xb3f8f2b6 in __GI_abort () at abort.c:79
#4  0x0197db1f in outliner_draw_restrictbuts
(block=block@entry=0x8dd92f04, scene=scene@entry=0xa03e3004, 
view_layer=view_layer@entry=0xa02c32c4, ar=0x9fd377c4, soops=0x9fd37904, 
props_active_parent=..., lb=) at 
/usr/include/i386-linux-gnu/bits/stdio2.h:100

#5  0x01980704 in draw_outliner (C=0xa15201f4)
at ./source/blender/e

Bug#900187: kdenlive: Color clip is always white

2018-05-27 Thread Fenix

Package: kdenlive
Version: 18.04.1-1
Severity: normal

Dear Maintainer,

   After last update, Color clip is always showed and rendered as white 
color, whatever color you previous set.


   To reproduce the error just add a non-white Color Clip to a project. 
It is showed and rendered as white color.




Thanks.



-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)

Kernel: Linux 4.16.0-1-686-pae (SMP w/2 CPU cores)
Locale: LANG=es_ES.utf8, LC_CTYPE=es_ES.utf8 (charmap=UTF-8), 
LANGUAGE=es_ES.utf8 (charmap=UTF-8)

Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages kdenlive depends on:
ii  ffmpeg   7:3.4.2-2+b1
ii  kded55.45.0-1
ii  kdenlive-data18.04.1-1
ii  kinit5.45.0-1
ii  kio  5.45.0-1
ii  libc62.27-3
ii  libgcc1  1:8.1.0-3
ii  libgl1   1.0.0+git20180308-2
ii  libglu1-mesa [libglu1]   9.0.0-2.1
ii  libkf5archive5   5.45.0-1
ii  libkf5attica55.45.0-1
ii  libkf5auth5  5.45.0-1
ii  libkf5bookmarks5 5.45.0-1
ii  libkf5codecs55.45.0-1
ii  libkf5completion55.45.0-1
ii  libkf5configcore55.45.0-1
ii  libkf5configgui5 5.45.0-1
ii  libkf5configwidgets5 5.45.0-1
ii  libkf5coreaddons55.45.0-1
ii  libkf5crash5 5.45.0-1
ii  libkf5dbusaddons55.45.0-1
ii  libkf5filemetadata3  5.45.0-1
ii  libkf5guiaddons5 5.45.0-1
ii  libkf5i18n5  5.45.0-1
ii  libkf5iconthemes55.45.0-1
ii  libkf5itemviews5 5.45.0-1
ii  libkf5jobwidgets55.45.0-1
ii  libkf5kiocore5   5.45.0-1
ii  libkf5kiofilewidgets55.45.0-1
ii  libkf5kiowidgets55.45.0-1
ii  libkf5newstuff5  5.45.0-1
ii  libkf5newstuffcore5  5.45.0-1
ii  libkf5notifications5 5.45.0-2
ii  libkf5notifyconfig5  5.45.0-2
ii  libkf5service-bin5.45.0-1
ii  libkf5service5   5.45.0-1
ii  libkf5solid5 5.45.0-1
ii  libkf5sonnetui5  5.45.0-1
ii  libkf5textwidgets5   5.45.0-2
ii  libkf5widgetsaddons5 5.45.0-1
ii  libkf5xmlgui55.45.0-1
ii  libmlt++36.8.0-1
ii  libmlt6  6.8.0-1
ii  libqt5concurrent55.10.1+dfsg-7
ii  libqt5core5a 5.10.1+dfsg-7
ii  libqt5dbus5  5.10.1+dfsg-7
ii  libqt5gui5   5.10.1+dfsg-7
ii  libqt5network5   5.10.1+dfsg-7
ii  libqt5qml5   5.10.1-4
ii  libqt5quick5 5.10.1-4
ii  libqt5script55.10.1+dfsg-2
ii  libqt5svg5   5.10.1-2
ii  libqt5webkit55.212.0~alpha2-9+b1
ii  libqt5widgets5   5.10.1+dfsg-7
ii  libqt5xml5   5.10.1+dfsg-7
ii  libstdc++6   8.1.0-3
ii  libv4l-0 1.14.2-1
ii  melt 6.8.0-1
ii  qml-module-qtquick-controls  5.10.1-2
ii  qml-module-qtquick2  5.10.1-4

Versions of packages kdenlive recommends:
ii  breeze-icon-theme  4:5.46.0-1
ii  dvdauthor  0.7.0-2
ii  dvgrab 3.5+git20160707.1.e46042e-1
ii  frei0r-plugins 1.6.1-2
ii  genisoimage9:1.1.11-3+b2
ii  oxygen-icon-theme  5:5.46.0-1
ii  recordmydesktop0.3.8.1+svn602-1+b2
ii  swh-plugins0.4.17-2

Versions of packages kdenlive suggests:
pn  khelpcenter  

-- no debconf information



Bug#1040586: krita: Krita Comics Manager crashes creating new template or page

2023-07-07 Thread Fenix F.
Package: krita
Version: 1:5.1.5+dfsg-2
Severity: normal
X-Debbugs-Cc: fenix...@gmail.com

Dear Maintainer,


   * What led up to the situation?

Creating new page with Krita Comic Manager Docker plugin throws exceptions:

   * How reproduce the error:

 1) Open Comics Manager Docker from Settings/Dockers.
 2) Create new project.
 3) Create new page and Create Template. We get error.

  If you paste a previous template, you get other error creating a new page.


  These is the errors:

   1) Creating a new template throws:


TypeError
Python 3.11.4: /usr/bin/python3
Fri Jul  7 20:12:19 2023

A problem occurred in a Python script.  Here is the sequence of
function calls leading up to the error, in the order they occurred.

/usr/share/krita/pykrita/comics_project_management_tools/comics_template_dialog.py
in
slot_create_template(self=)
  112
  113 if create.exec_() == QDialog.Accepted:
  114 if (create.prepare_krita_file()):
  115 self.fill_templates()
  116
create =

create.prepare_krita_file = >

/usr/share/krita/pykrita/comics_project_management_tools/comics_template_dialog.py
in
prepare_krita_file(self=)
  298 mB =
self.marginBottomUnit.pixelsForUnit(self.marginBottom.value(),
self.DPI.value())
  299
  300 template = Application.createDocument((wBase + bL + bR), (hBase +
bT + bB), self.templateName.text(), "RGBA", "U8", "sRGB built-in",
self.DPI.value())
  301
  302 backgroundName = i18n("Background")
template undefined
builtinApplication = 
Application.createDocument = 
wBase = 2480.314960629921
bL = 59.055118110236215
bR = 59.055118110236215
hBase = 3507.874015748031
bT = 118.11023622047243
bB = 118.11023622047243
self =

self.templateName = 
self.templateName.text = 
self.DPI = 
self.DPI.value = 
TypeError: createDocument(self, int, int, str, str, str, str, float): argument
1 has unexpected type 'float'
__cause__ = None
__class__ = 
__context__ = None
__delattr__ = 
__dict__ = {}
__dir__ = 
__doc__ = 'Inappropriate argument type.'
__eq__ = 
__format__ = 
__ge__ = 
__getattribute__ = 
__getstate__ = 
__gt__ = 
__hash__ = 
__init__ = 
__init_subclass__ = 
__le__ = 
__lt__ = 
__ne__ = 
__new__ = 
__reduce__ = 
__reduce_ex__ = 
__repr__ = 
__setattr__ = 
__setstate__ = 
__sizeof__ = 
__str__ = 
__subclasshook__ = 
__suppress_context__ = False
__traceback__ = 
add_note = 
args = ("createDocument(self, int, int, str, str, str, str, float):
argument 1 has unexpected type 'float'",)
with_traceback = 

The above is a description of an error in a Python program.  Here is
the original traceback:

Traceback (most recent call last):
  File
"/usr/share/krita/pykrita/comics_project_management_tools/comics_template_dialog.py",
line 114, in slot_create_template
if (create.prepare_krita_file()):
^^^
  File
"/usr/share/krita/pykrita/comics_project_management_tools/comics_template_dialog.py",
line 300, in prepare_krita_file
template = Application.createDocument((wBase + bL + bR), (hBase + bT + bB),
self.templateName.text(), "RGBA", "U8", "sRGB built-in", self.DPI.value())
^^^
TypeError: createDocument(self, int, int, str, str, str, str, float): argument
1 has unexpected type 'float'



  2) Creating a page using a previous template throws:



TypeError
Python 3.11.4: /usr/bin/python3
Fri Jul  7 20:15:31 2023

A problem occurred in a Python script.  Here is the sequence of
function calls leading up to the error, in the order they occurred.

/usr/share/krita/pykrita/comics_project_management_tools/comics_project_manager_docker.py
in
paint(self=, painter=,
option=,
index=)
   94 thumbImage = icon.pixmap(imageSizeHighDPI).toImage()
   95 thumbImage.setDevicePixelRatio(self.devicePixelRatioF)
   96 painter.drawImage(QRect(leftSideThumbnail, topSizeThumbnail,
imageSize.width(), imageSize.height()), thumbImage)
   97
   98 labelWidth = rect.width()-decoratonSize.width()-(margin*3)
painter = 
painter.drawImage = 
global QRect = 
leftSideThumbnail = 19.0
topSizeThumbnail = 4.0
imageSize = PyQt5.QtCore.QSize(90, 128)
imageSize.width = 
imageSize.height = 
thumbImage = 
TypeError: arguments did not match any overloaded call:
  QRect(): too many arguments
  QRect(aleft: int, atop: int, awidth: int, aheight: int): argument 1 has
unexpected type 'float'
  QRect(atopLeft: QPoint, abottomRight: QPoint): argument 1 has unexpected type
'float'
  QRect(atopLeft: QPoint, asize: QSize): argument 1 has unexpected type 'float'
  QRect(a0

Bug#1040586: krita: Krita Comics Manager crashes creating new template or page

2023-07-07 Thread Fenix F.
Package: krita
Version: 1:5.1.5+dfsg-2
Followup-For: Bug #1040586
X-Debbugs-Cc: fenix...@gmail.com
Patch: yes

Dear Maintainer,


I have been doing some test and it seems that something changed the way floats
are cast automatically to integers.

I have done a force casting and this workaround works for me. I attach patch
showing the changes.

But I really don't where this come from. My knowledge about PyQt5 and Krita
is limited.

I hope this helps to find a better fix.


Greetings.


-- System Information:
Debian Release: trixie/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 6.3.0-1-amd64 (SMP w/12 CPU threads; PREEMPT)
Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages krita depends on:
ii  krita-data1:5.1.5+dfsg-2
ii  libc6 2.37-3
ii  libexiv2-27   0.27.6-1
ii  libfftw3-double3  3.3.10-1
ii  libgcc-s1 13.1.0-6
ii  libgif7   5.2.1-2.5
ii  libgsl27  2.7.1+dfsg-5
ii  libheif1  1.16.2-1+b1
ii  libimath-3-1-29   3.1.6-1
ii  libjpeg62-turbo   1:2.1.5-2
ii  libjxl0.7 0.7.0-10
ii  libkf5completion5 5.107.0-1
ii  libkf5configcore5 5.107.0-1
ii  libkf5configgui5  5.107.0-1
ii  libkf5coreaddons5 5.107.0-1
ii  libkf5crash5  5.107.0-1
ii  libkf5guiaddons5  5.107.0-1
ii  libkf5i18n5   5.107.0-1
ii  libkf5itemviews5  5.107.0-1
ii  libkf5widgetsaddons5  5.107.0-1
ii  libkf5windowsystem5   5.107.0-1
ii  libkseexpr4   4.0.4.0-4
ii  libkseexprui4 4.0.4.0-4
ii  liblcms2-22.14-2
ii  libmypaint-1.5-1  1.6.0-2
ii  libopencolorio2.1 2.1.2+dfsg1-4+b3
ii  libopenexr-3-1-30 3.1.5-5
ii  libopenjp2-7  2.5.0-2
ii  libpng16-16   1.6.40-1
ii  libpoppler-qt5-1  22.12.0-2+b1
ii  libpython3.11 3.11.4-1
ii  libqt5core5a  5.15.8+dfsg-12
ii  libqt5dbus5   5.15.8+dfsg-12
ii  libqt5gui55.15.8+dfsg-12
ii  libqt5multimedia5 5.15.8-2
ii  libqt5network55.15.8+dfsg-12
ii  libqt5printsupport5   5.15.8+dfsg-12
ii  libqt5qml55.15.8+dfsg-3
ii  libqt5quick5  5.15.8+dfsg-3
ii  libqt5quickwidgets5   5.15.8+dfsg-3
ii  libqt5sql55.15.8+dfsg-12
ii  libqt5sql5-sqlite 5.15.8+dfsg-12
ii  libqt5svg55.15.8-3
ii  libqt5widgets55.15.8+dfsg-12
ii  libqt5x11extras5  5.15.8-2
ii  libqt5xml55.15.8+dfsg-12
ii  libquazip5-1  0.9.1-3
ii  libraw20  0.20.2-2.1
ii  libstdc++613.1.0-6
ii  libtiff6  4.5.1-1
ii  libturbojpeg0 1:2.1.5-2
ii  libwebp7  1.2.4-0.2
ii  libx11-6  2:1.8.6-1
ii  zlib1g1:1.2.13.dfsg-1

Versions of packages krita recommends:
ii  krita-gmic   2.9.4-4+b4
ii  python3-pyqt55.15.9+dfsg-1
ii  python3-sip  4.19.25+dfsg-5+b1
ii  qml-module-qtmultimedia  5.15.8-2

Versions of packages krita suggests:
ii  colord  1.4.6-2.2
ii  ffmpeg  7:5.1.3-1
pn  krita-l10n  

-- no debconf information
--- comics_project_manager_docker.py	2023-07-08 02:12:56.806462080 +0200
+++ comics_project_manager_docker_fix.py	2023-07-08 02:03:24.677998546 +0200
@@ -93,7 +93,8 @@
 topSizeThumbnail = ((rect.height()-imageSize.height())/2)+rect.top()
 thumbImage = icon.pixmap(imageSizeHighDPI).toImage()
 thumbImage.setDevicePixelRatio(self.devicePixelRatioF)
-painter.drawImage(QRect(leftSideThumbnail, topSizeThumbnail, imageSize.width(), imageSize.height()), thumbImage)
+
+painter.drawImage(QRect(int(leftSideThumbnail), int(topSizeThumbnail), int(imageSize.width()), int(imageSize.height())), thumbImage)
 
 labelWidth = rect.width()-decoratonSize.width()-(margin*3)
 
@@ -136,8 +137,8 @@
 
 descRect = QRect(textRect.left(), textRect.bottom()+margin, labelWidth, (rect.bottom()-margin) - (textRect.bottom()+margin))
 if textRect.bottom()+metrics.height() < rect.bottom():
-textRect.setBottom(textRect.bottom()+(margin/2))
-textRect.setLeft(textRect.left()-(margin/2))
+textRect.setBottom(int(textRect.bottom()+(margin/2)))
+textRect.setLeft(int(textRect.left()-(margin/2)))
 painter.setOpacity(0.4)
 painter.drawLine(textRect.bottomLeft(), textRect.bottomRight())
 painter.setOpacity(1.0)
--- comics_template_dialog.py	2023-07-08 02:12:45.802376577 +0200
+++ comics_template_dialog_fix.py	2023-07-08 01:50:55.808011929 +0200
@@ -296,8 +296,8 @@
 bB = self.bleedBottomUnit.pixelsForUnit(self.bleedBottom.value(), self.DPI.value())
 mT = self.marginTopUnit.pixelsForUnit(self.marginTop.value

Bug#1055779: manuskript: Crash selecting templates

2023-11-11 Thread Fenix F.
Package: manuskript
Version: 0.15.0-1
Severity: normal
X-Debbugs-Cc: fenix...@gmail.com

Dear Maintainer,

   * What led up to the situation?

   1) Open Manuskript.
   2) Select one template, for example, Empty Fiction.
   3) Select another template, for example, Short Story.
   4) Select Empty Fiction again.

   Manuskript crash with this log:

---
CRITICAL> An unhandled exception has occurred!
Traceback (most recent call last):
  File "/usr/share/manuskript/manuskript/ui/welcome.py", line 260, in
changeTemplate
self.updateTemplate()
  File "/usr/share/manuskript/manuskript/ui/welcome.py", line 329, in
updateTemplate
self.updateWordCount()
  File "/usr/share/manuskript/manuskript/ui/welcome.py", line 370, in
updateWordCount
self.template[1][templateIndex][1])
^^^
IndexError: list index out of range
---


-- System Information:
Debian Release: trixie/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 6.5.0-4-amd64 (SMP w/12 CPU threads; PREEMPT)
Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.UTF-8 (charmap=UTF-8), LANGUAGE=es
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages manuskript depends on:
ii  libqt5svg5  5.15.10-2
ii  python3 3.11.4-5+b1
ii  python3-enchant 3.2.2-1
ii  python3-lxml4.9.3-1
ii  python3-markdown3.4.4-1
ii  python3-pyqt5   5.15.10+dfsg-1
ii  python3-pyqt5.qtwebkit  5.15.10+dfsg-1
ii  zlib1g  1:1.2.13.dfsg-3

Versions of packages manuskript recommends:
ii  pandoc  2.17.1.1-3

Versions of packages manuskript suggests:
pn  texlive-latex-recommended  

-- no debconf information



Bug#1041343: krita: Dead keys are not working

2023-07-17 Thread Fenix F.
Package: krita
Version: 1:5.1.5+dfsg-2+b1
Severity: normal
X-Debbugs-Cc: fenix...@gmail.com

Dear Maintainer,


   * What led up to the situation?

Pressing dead key for example acute accent is not working in whole Krita
input: naming layers, Text tool...

   * What exactly did you do (or not do) that was effective (or
 ineffective)?

Naming a layer or entering text in Text tool. For example: 'á'


   * What was the outcome of this action?

   Dead key did nothing, it just show the simple letter. Instead of, for
example, 'á' it is obtained and showed 'a'.

   * What outcome did you expect instead?

   Get the right letter: á.


-- System Information:
Debian Release: trixie/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 6.3.0-1-amd64 (SMP w/12 CPU threads; PREEMPT)
Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.UTF-8 (charmap=UTF-8), LANGUAGE=es
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages krita depends on:
ii  krita-data1:5.1.5+dfsg-2
ii  libc6 2.37-5
ii  libexiv2-27   0.27.6-1
ii  libfftw3-double3  3.3.10-1
ii  libgcc-s1 13.1.0-6
ii  libgif7   5.2.1-2.5
ii  libgsl27  2.7.1+dfsg-5
ii  libheif1  1.16.2-1+b1
ii  libimath-3-1-29   3.1.6-1
ii  libjpeg62-turbo   1:2.1.5-2
ii  libjxl0.7 0.7.0-10
ii  libkf5completion5 5.107.0-1
ii  libkf5configcore5 5.107.0-1
ii  libkf5configgui5  5.107.0-1
ii  libkf5coreaddons5 5.107.0-1
ii  libkf5crash5  5.107.0-1
ii  libkf5guiaddons5  5.107.0-1
ii  libkf5i18n5   5.107.0-1
ii  libkf5itemviews5  5.107.0-1
ii  libkf5widgetsaddons5  5.107.0-1
ii  libkf5windowsystem5   5.107.0-1
ii  libkseexpr4   4.0.4.0-4
ii  libkseexprui4 4.0.4.0-4
ii  liblcms2-22.14-2
ii  libmypaint-1.5-1  1.6.0-2
ii  libopencolorio2.1 2.1.2+dfsg1-4+b3
ii  libopenexr-3-1-30 3.1.5-5
ii  libopenjp2-7  2.5.0-2
ii  libpng16-16   1.6.40-1
ii  libpoppler-qt5-1  22.12.0-2+b1
ii  libpython3.11 3.11.4-1
ii  libqt5core5a  5.15.8+dfsg-12
ii  libqt5dbus5   5.15.8+dfsg-12
ii  libqt5gui55.15.8+dfsg-12
ii  libqt5multimedia5 5.15.8-2
ii  libqt5network55.15.8+dfsg-12
ii  libqt5printsupport5   5.15.8+dfsg-12
ii  libqt5qml55.15.8+dfsg-3
ii  libqt5quick5  5.15.8+dfsg-3
ii  libqt5quickwidgets5   5.15.8+dfsg-3
ii  libqt5sql55.15.8+dfsg-12
ii  libqt5sql5-sqlite 5.15.8+dfsg-12
ii  libqt5svg55.15.8-3
ii  libqt5widgets55.15.8+dfsg-12
ii  libqt5x11extras5  5.15.8-2
ii  libqt5xml55.15.8+dfsg-12
ii  libquazip5-1  0.9.1-3
ii  libraw23  0.21.1-4
ii  libstdc++613.1.0-6
ii  libtiff6  4.5.1-1
ii  libturbojpeg0 1:2.1.5-2
ii  libwebp7  1.2.4-0.2
ii  libx11-6  2:1.8.6-1
ii  zlib1g1:1.2.13.dfsg-1

Versions of packages krita recommends:
ii  krita-gmic   2.9.4-4+b4
ii  python3-pyqt55.15.9+dfsg-1
ii  python3-sip  4.19.25+dfsg-5+b1
ii  qml-module-qtmultimedia  5.15.8-2

Versions of packages krita suggests:
ii  colord  1.4.6-2.2
ii  ffmpeg  7:5.1.3-1
pn  krita-l10n  

-- no debconf information



Bug#954142: mypaint: does not start

2020-03-17 Thread Fenix F.
Package: mypaint
Version: 2.0.0-1
Followup-For: Bug #954142

   Same here.

   It seems a problem with mypaintlib.so name library. In my system the
name is
_mypaintlib.cpython-38-i386-linux-gnu.so and it is expected: _mypaintlib.so

   As dirty workaround, making a symbolic link allow running Mypaint:

   # ln -s _mypaintlib.cpython-38-i386-linux-gnu.so _mypaintlib.so



-- System Information:
Debian Release: bullseye/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)

Kernel: Linux 5.4.0-4-686-pae (SMP w/2 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE,
TAINT_UNSIGNED_MODULE
Locale: LANG=es_ES.utf8, LC_CTYPE=es_ES.utf8 (charmap=UTF-8),
LANGUAGE=es_ES.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages mypaint depends on:
ii  gir1.2-gtk-3.0  3.24.14-1
ii  libc6   2.29-10
ii  libgcc-s1   10-20200304-1
ii  libgdk-pixbuf2.0-0  2.40.0+dfsg-3
ii  libglib2.0-02.62.5-1
ii  libgomp110-20200304-1
ii  liblcms2-2  2.9-4+b1
ii  libmypaint-1.5-11.5.1-1
ii  libpng16-16 1.6.37-2
ii  libstdc++6  10-20200304-1
ii  mypaint-brushes 2.0.2+ds1-1
ii  mypaint-data2.0.0-1
ii  python3 3.7.5-3
ii  python3-gi  3.34.0-6
ii  python3-gi-cairo3.34.0-6
ii  python3-numpy   1:1.17.4-5

Versions of packages mypaint recommends:
ii  mypaint-data-extras  2.0.0-1
ii  shared-mime-info 1.10-1

mypaint suggests no packages.

-- no debconf information


Bug#954142: mypaint: does not start

2020-03-27 Thread Fenix F.
Package: mypaint
Followup-For: Bug #954142

Dear Maintainer,

As you said, the python3 update to 3.8.2 works for me respect this Mypaint
issue. Now it is not required the symbolic link, and Mypaint works flawless.



Thanks.



-- System Information:
Debian Release: bullseye/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)

Kernel: Linux 5.4.0-4-686-pae (SMP w/2 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE,
TAINT_UNSIGNED_MODULE
Locale: LANG=es_ES.utf8, LC_CTYPE=es_ES.utf8 (charmap=UTF-8),
LANGUAGE=es_ES.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages mypaint depends on:
ii  gir1.2-gtk-3.0  3.24.14-1
ii  libc6   2.30-2
ii  libgcc-s1   10-20200324-1
ii  libgdk-pixbuf2.0-0  2.40.0+dfsg-3
ii  libglib2.0-02.64.1-1
ii  libgomp110-20200324-1
ii  liblcms2-2  2.9-4+b1
ii  libmypaint-1.5-11.5.1-1
ii  libpng16-16 1.6.37-2
ii  libstdc++6  10-20200324-1
ii  mypaint-brushes 2.0.2+ds1-1
ii  mypaint-data2.0.0-1
ii  python3 3.8.2-2
ii  python3-gi  3.34.0-6
ii  python3-gi-cairo3.34.0-6
ii  python3-numpy   1:1.17.4-5

Versions of packages mypaint recommends:
ii  mypaint-data-extras  2.0.0-1
ii  shared-mime-info 1.10-1

mypaint suggests no packages.

-- no debconf information



Bug#1095113: krita: Krita freezes and eventually crashes when trying to open a file browser.

2025-02-03 Thread Fenix F.
Package: krita
Version: 1:5.2.6+dfsg-3
Severity: normal
X-Debbugs-Cc: fenix...@gmail.com

Dear Maintainer,


   * What led up to the situation?

When Krita tries to open a file browser, for example, after pressing
'Export File' or selecting the recording directory in Recorder, Krita
starts to freeze.
The Krita process reaches 100% CPU usage and, after some time, finally crashes.

This is the crash message; I don’t know if it’s useful:

--
Application: Krita (krita), signal: Segmentation fault

[KCrash Handler]
#4  0x7f452a2dcc04 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f452a50ad12 in QObjectPrivate::~QObjectPrivate() () from
/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7f452a2a7cc1 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7f452a45ccc1 in QSettings::QSettings(QSettings::Scope, QString
const&, QString const&, QObject*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7f452b38b683 in QFileDialogPrivate::saveSettings() () from
/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#9  0x7f452b38be69 in QFileDialog::~QFileDialog() () from
/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#10 0x7f44ba3fb26a in ?? () from /usr/lib/x86_64-linux-
gnu/kritaplugins/kritarecorderdocker.so
#11 0x7f452a5185d2 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#12 0x7f452b25a936 in QAbstractButton::clicked(bool) () from
/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#13 0x7f452b25abae in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#14 0x7f452b25c799 in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#15 0x7f452b25c9dc in QAbstractButton::mouseReleaseEvent(QMouseEvent*) ()
from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#16 0x7f452b1a6038 in QWidget::event(QEvent*) () from /lib/x86_64-linux-
gnu/libQt5Widgets.so.5
#17 0x7f452b163052 in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#18 0x7f452b16b39a in QApplication::notify(QObject*, QEvent*) () from
/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#19 0x7f452c7abcce in KisApplication::notify(QObject*, QEvent*) () from
/lib/x86_64-linux-gnu/libkritaui.so.19
#20 0x7f452a4ddcd8 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() from /lib/x86_64-linux-gnu/libQt5Core.so.5
#21 0x7f452b169402 in QApplicationPrivate::sendMouseEvent(QWidget*,
QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer&, bool, bool) ()
from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#22 0x7f452b1bfffa in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#23 0x7f452b1c350f in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#24 0x7f452b163052 in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#25 0x7f452c7abcce in KisApplication::notify(QObject*, QEvent*) () from
/lib/x86_64-linux-gnu/libkritaui.so.19
#26 0x7f452a4ddcd8 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() from /lib/x86_64-linux-gnu/libQt5Core.so.5
#27 0x7f452a944d23 in
QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*)
() from /lib/x86_64-linux-gnu/libQt5Gui.so.5
#28 0x7f452a9166fc in
QWindowSystemInterface::sendWindowSystemEvents(QFlags)
() from /lib/x86_64-linux-gnu/libQt5Gui.so.5
#29 0x7f4524ef392e in ?? () from /lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#30 0x7f45281ca81f in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#31 0x7f45281cca57 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#32 0x7f45281cd1c0 in g_main_context_iteration () from /lib/x86_64-linux-
gnu/libglib-2.0.so.0
#33 0x7f452a53abed in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib/x86_64-linux-gnu/libQt5Core.so.5
#34 0x7f452a4dc642 in
QEventLoop::exec(QFlags) () from
/lib/x86_64-linux-gnu/libQt5Core.so.5
#35 0x7f452a4e5062 in QCoreApplication::exec() () from /lib/x86_64-linux-
gnu/libQt5Core.so.5
#36 0x562a823f05f0 in ?? ()
#37 0x7f4529c33d68 in ?? () from /lib/x86_64-linux-gnu/libc.so.6
#38 0x7f4529c33e25 in __libc_start_main () from /lib/x86_64-linux-
gnu/libc.so.6
#39 0x562a823f1d31 in ?? ()
[Inferior 1 (process 7407) detached]
--



   Thanks.


-- System Information:
Debian Release: trixie/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 6.12.11-amd64 (SMP w/12 CPU threads; PREEMPT)
Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.UTF-8 (charmap=UTF-8), LANGUAGE=es
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages krita depends on:
ii  krita-data   1:5.2.6+dfsg-3
ii  libc62.40-6
ii  libexiv2-28  0.28.3+dfsg-2
ii  libfftw3-double3 3.3.10-2+b1
ii  libfontconfig1   2.15.0-2
ii  libfreetype6 2.13.3+dfsg-1
ii  libfribidi0

Bug#1095602: libqt5core5t64: Apps like Krita and VLC freeze and eventually crash when opening a file dialog.

2025-02-09 Thread Fenix F.
El dom, 9 feb 2025 a las 20:56, Dmitry Shachnev () escribió:
>
> Hi Fenix!

Hi, Dmitry.


> Can you please install libqt5core5t64-dbgsym package and generate the stack
> trace again? That should make it much more useful. Please see [1] for details
> on how to add the debug repository, from where it can be installed.

  Sure! Sorry for the lack of information in my report.


Here is the trace with symbols in libqt5core5t64:

--
#5  0x7f61752a15e9 in std::terminate() () from
/lib/x86_64-linux-gnu/libstdc++.so.6
No symbol table info available.
#6  0x7f61752b3288 in __cxa_throw () from
/lib/x86_64-linux-gnu/libstdc++.so.6
No symbol table info available.
#7  0x7f616e291341 in qBadAlloc () at global/qglobal.cpp:3388
No locals.
#8  0x7f616e295ebd in QByteArray::reallocData
(this=this@entry=0x7f616db5c068, alloc=2147483627, options=...,
options@entry=...)
   at text/qbytearray.cpp:1853
   x = 0x0
#9  0x7f616e44eca4 in QByteArray::reserve (this=0x7f616db5c068,
asize=2147483626)
   at ../../include/QtCore/../../src/corelib/text/qbytearray.h:533
No locals.
#10 QtStringBuilder::appendToByteArray (a=..., b=...)
   at ../../include/QtCore/../../src/corelib/text/qstringbuilder.h:457
   len = 2147483626
   it = 
#11 0x7f616e45191d in operator+= (a=..., b=...)
   at ../../include/QtCore/../../src/corelib/text/qstringbuilder.h:474
No locals.
#12 QSettingsPrivate::iniEscapedString (str=..., result=...,
codec=codec@entry=0x0) at io/qsettings.cpp:678
   ch = 
   needsQuotes = 
   escapeNextIfDigit = 
   useCodec = 
   i = 536870896
   startPos = 
   unicode = 
#13 0x7f616e45ac8b in QSettingsPrivate::iniEscapedStringList
(strs=..., result=..., codec=0x0) at io/qsettings.cpp:723
   i = 4
#14 QConfFileSettingsPrivate::writeIniFile
(this=this@entry=0x7f61649f61c0, device=..., map=...) at
io/qsettings.cpp:1896
   block = {d = 0x7f5f93803010}
   value = 
   j = 
   realSection = {d = 0x7f616491a3f0}
   ents = @0x7f61648b44d8: {d = 0x7f616491a260}
   j = 0
   iniMap = 
   i = {i = 0x7f61648b44b0}
   eol = 
   sectionCount = 1
   sections = {d = 0x7f616491a3c0}
   writeError = false
#15 0x7f616e45c155 in QConfFileSettingsPrivate::syncConfFile
(this=this@entry=0x7f61649f61c0,
confFile=confFile@entry=0x7f61648ba1f0)
   at io/qsettings.cpp:1516
   ok = false
   mergedKeys = {d = 0x7f616491a0a0}
   sf = { = { = { =
{_vptr.QObject = 0x7f616e7824a0 ,
   static staticMetaObject = {d = {superdata = {direct =
0x0}, stringdata = 0x7f616e6b8a20 ,
   data = 0x7f616e6b8900 ,
   static_metacall = 0x7f616e516620
,
   relatedMetaObjects = 0x0, extradata = 0x0}}, d_ptr
= {d = 0x7f61645daf50}, static staticQtMetaObject = {d = {
   superdata = {direct = 0x0}, stringdata =
0x7f616e6bb9c0 ,
   data = 0x7f616e6b8b40 ,
static_metacall = 0x0, relatedMetaObjects = 0x0, extradata = 0x0}}},
 static staticMetaObject = {d = {superdata = {direct =
0x7f616e77c140 },
 stringdata = 0x7f616e6a80a0
, data = 0x7f616e6a7fa0
,
 static_metacall = 0x7f616e401c90
,
 relatedMetaObjects = 0x0, extradata = 0x0}}}, static
staticMetaObject = {d = {superdata = {
 direct = 0x7f616e781940
}, stringdata = 0x7f616e6a7f40
,
   data = 0x7f616e6a7f00 ,
   static_metacall = 0x7f616e3f9f50
,
   relatedMetaObjects = 0x0, extradata = 0x0}}}, static
staticMetaObject = {d = {superdata = {
   direct = 0x7f616e7817a0
}, stringdata = 0x7f616e6a87e0
,
 data = 0x7f616e6a87a0 ,
 static_metacall = 0x7f616e416fb0
,
 relatedMetaObjects = 0x0, extradata = 0x0}}}
   readOnly = 
   lockFile = {d_ptr = {d = 0x7f6164835cb0}}
   fileInfo = {d_ptr = {d = 0x7f61648e4c60}}
   mustReadFile = 
   createFile = 
#16 0x7f616e45c2fb in QConfFileSettingsPrivate::sync
(this=this@entry=0x7f61649f61c0) at io/qsettings.cpp:1368
   locker = 
   confFile = 0x7f61648ba1f0
   __for_range = @0x7f61649f6250: {d = 0x7f6164943b60}
   __for_begin = 0x7f6164943b78
   __for_end = 0x7f6164943b98
#17 0x7f616e45c665 in QConfFileSettingsPrivate::initAccess
(this=0x7f61649f61c0) at io/qsettings.cpp:960
No locals.
#18 QConfFileSettingsPrivate::QConfFileSettingsPrivate
(this=0x7f61649f61c0, format=, scope=,
   organization=..., application=...) at io/qsettings.cpp:1186
   org = {d = 0x7f6164861620}
   appFile = {d = 0x7f61647e2210}
   orgFile = {d = 0x7f616472f120}
   systemPath = {path = {d = 0x7f61641dee50}, userDefined = false}
   org = 
   appFile = 
   orgFile = 
   systemPath = 
   userPath = 
   dirs = 
   paths = 
   dir = 
   __for_range = 
   __for_begin = 
   __for_end = 
   dir = 
   __for_range = 
   

Bug#1090920: digimend-dkms: Huion tablet buttons configured with xsetwacom stop working after last update.

2024-12-20 Thread Fenix F.
Package: digimend-dkms
Version: 13-3
Severity: normal
X-Debbugs-Cc: fenix...@gmail.com

Dear Maintainer,

   After last DIGImend update, tablet buttons stop working.

   Executing xsetwacom to see the devices, only show two devices: Stylus and
Eraser, but not PAD.

-
fenix@Helios:~/bin$ xsetwacom --list devices
HID 256c:006d stylusid: 8   type: STYLUS
HID 256c:006d eraserid: 15  type: ERASER
-

This is showed when tablet (Huion H950P) is plugged:

-
dic 20 21:15:37 Helios kernel: usb 1-5: USB disconnect, device number 18
dic 20 21:15:45 Helios kernel: usb 1-5: new full-speed USB device number 19
using xhci_hcd
dic 20 21:15:45 Helios kernel: usb 1-5: New USB device found, idVendor=0416,
idProduct=3f00, bcdDevice= 0.00
dic 20 21:15:46 Helios kernel: usb 1-5: New USB device strings: Mfr=1,
Product=2, SerialNumber=0
dic 20 21:15:46 Helios kernel: usb 1-5: Product: WPM USB
dic 20 21:15:46 Helios kernel: usb 1-5: Manufacturer: Nuvoton
dic 20 21:15:46 Helios kernel: input: Nuvoton WPM USB as
/devices/pci:00/:00:01.3/:03:00.0/usb1/1-5/1-5:1.0/0003:0416:3F00.001B/input/input39
dic 20 21:15:46 Helios kernel: hid-generic 0003:0416:3F00.001B: input,hidraw0:
USB HID v1.10 Device [Nuvoton WPM USB] on usb-:03:00.0-5/input0
dic 20 21:15:46 Helios mtp-probe[7977]: checking bus 1, device 19:
"/sys/devices/pci:00/:00:01.3/:03:00.0/usb1/1-5"
dic 20 21:15:46 Helios mtp-probe[7977]: bus: 1, device: 19 was not an MTP
device
dic 20 21:15:46 Helios systemd-logind[817]: Watching system buttons on
/dev/input/event2 (Nuvoton WPM USB)
dic 20 21:15:46 Helios mtp-probe[7990]: checking bus 1, device 19:
"/sys/devices/pci:00/:00:01.3/:03:00.0/usb1/1-5"
dic 20 21:15:46 Helios mtp-probe[7990]: bus: 1, device: 19 was not an MTP
device
dic 20 21:15:47 Helios kernel: usb 1-5: USB disconnect, device number 19
dic 20 21:15:48 Helios kernel: usb 1-5: new full-speed USB device number 20
using xhci_hcd
dic 20 21:15:48 Helios kernel: usb 1-5: New USB device found, idVendor=256c,
idProduct=006d, bcdDevice= 0.00
dic 20 21:15:48 Helios kernel: usb 1-5: New USB device strings: Mfr=5,
Product=6, SerialNumber=0
dic 20 21:15:48 Helios kernel: hid-generic 0003:256C:006D.001C:
hiddev0,hidraw0: USB HID v1.11 Device [HID 256c:006d] on
usb-:03:00.0-5/input0
dic 20 21:15:48 Helios kernel: input: HID 256c:006d as
/devices/pci:00/:00:01.3/:03:00.0/usb1/1-5/1-5:1.1/0003:256C:006D.001D/input/input40
dic 20 21:15:48 Helios kernel: hid-generic 0003:256C:006D.001D: input,hidraw1:
USB HID v1.11 Device [HID 256c:006d] on usb-:03:00.0-5/input1
dic 20 21:15:48 Helios mtp-probe[7999]: checking bus 1, device 20:
"/sys/devices/pci:00/:00:01.3/:03:00.0/usb1/1-5"
dic 20 21:15:48 Helios mtp-probe[7999]: bus: 1, device: 20 was not an MTP
device
-

    This shows lsusb:

-
fenix@Helios:~/bin$ lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 003: ID 1bcf:08a0 Sunplus Innovation Technology Inc. Gaming
mouse [Philips SPK9304]
Bus 001 Device 004: ID 1a2c:4c5e China Resource Semico Co., Ltd USB Keyboard
Bus 001 Device 020: ID 256c:006d
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
-


   This command throw error because there is no tablet pad devices found:

--
xsetwacom --set "HID 256c:006d Pad pad" Button 12 "key e"
--

   So binding buttons is not allowed before the update.



I've changed the xorg configuration to rotate the tablet (Option
added) (I'm left handed and
need the buttons at the right):

--
Section "InputClass"
Identifier "Huion tablets with Wacom driver"
MatchUSBID "5543:006e|256c:006e|256c:006d|256c:0064|256c:006f"
MatchDevicePath "/dev/input/event*"
MatchIsKeyboard "false"
Driver "wacom"
Option "Rotate" "half"
EndSection
--


Thanks.


-- System Information:
Debian Release: trixie/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 6.11.10-amd64 (SMP w/12 CPU threads; PREEMPT)
Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.UTF-8 (charmap=UTF-8), LANGUAGE=es
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages digimend-dkms depends on:
ii  dkms  3.0.13-1
ii  xserver-xorg-input-wacom  1.2.2-3

digimend-dkms recommends no packages.

digimend-dkms suggests no packages.

-- no debconf information

-- debsums errors found:
debsums: changed file /usr/share/X11/xorg.conf.d/50-digimend.conf
(from digimend-dkms package)



Bug#1095602: libqt5core5t64: Apps like Krita and VLC freeze and eventually crash when opening a file dialog.

2025-02-09 Thread Fenix F.
Package: libqt5core5t64
Version: 5.15.15+dfsg-2
Severity: normal
X-Debbugs-Cc: fenix...@gmail.com

Dear Maintainer,

   * What led up to the situation?

  Opening a file browser in an app (I tested two: Krita and VLC)
causes the process to reach 100% CPU usage, freezing the app. After
trying to open a file browser again, the app eventually crashes.

Steps to reproduce:

   1) Open VLC.
   2) Select "Open new file".
   3) While the file dialog popup is opening, the process reach 100% of CPU
(check with top) and VLC freeze.
   4) Close the file browser popup.
   5) Try opening a file again.
   6) This time, the app crash pass a time.


  This is part ot the coredump crash information:

-
#5  0x7fb06f2a15e9 in std::terminate() () from /lib/x86_64-linux-
gnu/libstdc++.so.6
#6  0x7fb06f2b3288 in __cxa_throw () from /lib/x86_64-linux-
gnu/libstdc++.so.6
#7  0x7fb063a91341 in qBadAlloc() () from /lib/x86_64-linux-
gnu/libQt5Core.so.5
#8  0x7fb063a95ebd in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#9  0x7fb063c4eca4 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#10 0x7fb063c5191d in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#11 0x7fb063c5ac8b in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#12 0x7fb063c5c155 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#13 0x7fb063c5c2fb in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#14 0x7fb063c5c665 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#15 0x7fb063c5ccc1 in QSettings::QSettings(QSettings::Scope, QString
const&, QString const&, QObject*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#16 0x7fb06918bf77 in QFileDialogPrivate::restoreFromSettings() () from
/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#17 0x7fb06918e14b in QFileDialogPrivate::init(QFileDialogArgs const&) ()
from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#18 0x7fb06918f010 in QFileDialog::QFileDialog(QFileDialogArgs const&) ()
from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#19 0x7fb06918f4d3 in QFileDialog::getOpenFileUrls(QWidget*, QString
const&, QUrl const&, QString const&, QString*, QFlags,
QStringList const&) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
-


This is the information of systemd coredump:
-
  PID: 3490 (vlc)
   UID: 1000 (fenix)
   GID: 1000 (fenix)
Signal: 6 (ABRT)
 Timestamp: Sun 2025-02-09 16:30:44 CET (1h 21min ago)
  Command Line: /usr/bin/vlc --started-from-file
Executable: /usr/bin/vlc
 Control Group: /user.slice/user-1000.slice/user@1000.service/app.slice/app-
vlc@1591eddb96c640ff8e19e64122b073fa.service
  Unit: user@1000.service
 User Unit: app-vlc@1591eddb96c640ff8e19e64122b073fa.service
 Slice: user-1000.slice
 Owner UID: 1000 (fenix)
   Boot ID: 7abe9fc8f968426da238f1074e82f047
Machine ID: 64b8d1039800478493ec6e13ee8442f9
  Hostname: Helios
   Storage:
/var/lib/systemd/coredump/core.vlc.1000.7abe9fc8f968426da238f1074e82f047.3490.173911504400.zst
(present)
  Size on Disk: 129.1M
   Message: Process 3490 (vlc) of user 1000 dumped core.

Module libblkid.so.1 from deb util-linux-2.40.4-2.amd64
Module libudev.so.1 from deb systemd-257.2-3.amd64
Module libmount.so.1 from deb util-linux-2.40.4-2.amd64
Module libuuid.so.1 from deb util-linux-2.40.4-2.amd64
Module libatomic.so.1 from deb gcc-14-14.2.0-12.amd64
Module libzstd.so.1 from deb libzstd-1.5.6+dfsg-2.amd64
Module libarchive.so.13 from deb libarchive-3.7.4-1.1.amd64
Module libgcc_s.so.1 from deb gcc-14-14.2.0-12.amd64
Module libstdc++.so.6 from deb gcc-14-14.2.0-12.amd64
Module libsystemd.so.0 from deb systemd-257.2-3.amd64
Stack trace of thread 3494:
#0  0x7fb0722a9dcc n/a (libc.so.6 + 0x93dcc)
#1  0x7fb072255d02 raise (libc.so.6 + 0x3fd02)
#2  0x7fb07223e4f0 abort (libc.so.6 + 0x284f0)
#3  0x7fb06f2a1a3d n/a (libstdc++.so.6 + 0xa1a3d)
#4  0x7fb06f2b300a n/a (libstdc++.so.6 + 0xb300a)
#5  0x7fb06f2a15e9 _ZSt9terminatev (libstdc++.so.6 +
0xa15e9)
#6  0x7fb06f2b3288 __cxa_throw (libstdc++.so.6 + 0xb3288)
#7  0x7fb063a91341 _Z9qBadAllocv (libQt5Core.so.5 +
0x91341)
#8  0x7fb063a95ebd n/a (libQt5Core.so.5 + 0x95ebd)
#9  0x7fb063c4eca4 n/a (libQt5Core.so.5 + 0x24eca4)
#10 0x7fb063c5191d n/a (libQt5Core.so.5 + 0x25191d)
#11 0x7fb063c5ac8b n/a (libQt5Core.so.5 + 0x25ac8b)
#12 0x7fb063c5c155 n/a (libQt5Core.so.5 + 0x25c155)
#13 0x7fb063c5c2fb n/a (libQt5Core.so.5 + 0x25c2fb)
#14 0x7fb063c5c665 n/a (libQt5Core.so.5 + 0x25c6

Bug#1095602: libqt5core5t64: Apps like Krita and VLC freeze and eventually crash when opening a file dialog.

2025-02-11 Thread Fenix F.
El mar, 11 feb 2025 a las 13:47, Dmitry Shachnev
() escribió:

> It looks like it crashes when trying to allocate memory for a large string:
> it says len = 2147483626, which is almost 2 GB.
>
> I found a similar issue described here [1], and the reporter solved it by
> removing ~/.config/QtProject.conf file which was too large. Maybe it’s the
> same in your case?


   $ du -h QtProject.conf
530MQtProject.conf

Wow. I think you hit the nail on the head. :)


> Can you try to remove or move it?
> If you decide to remove, maybe first look at its content and check which
> field is so long, it may shed more light on this issue.

   This is the content of QtProject.conf and the cause of the unusual size:

--
[FileDialog]
history=@Invalid()
lastVisited=file:///home/fenix/Dibujo/daily_drawing_challenges/2022_10_17_1283_D/
qtVersion=6.7.2
shortcuts=file:, file:///home/fenix, file:///home/fenix/Escritorio,
file:///home/fenix/Descargas, file:///home/fenix/MÃÂÃ
Â[this is repeated lot, lot... lot of
times]ÃÂsica
sidebarWidth=230
treeViewHeader=@ByteArray(\0\0\0\xff\0\0\0\0\0\0\0\x1\0\0\0\0\0\0\0\0\x1\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\x3\xf9\0\0\0\x4\x1\x1\0\0\0\0\0\0\0\0\0\0\0\0\0\0\x64\xff\xff\xff\xff\0\0\0\x81\0\0\0\0\0\0\0\x4\0\0\x2\xa0\0\0\0\x1\0\0\0\0\0\0\0\xa9\0\0\0\x1\0\0\0\0\0\0\0\x42\0\0\0\x1\0\0\0\0\0\0\0n\0\0\0\x1\0\0\0\0\0\0\x3\xe8\0\xff\xff\xff\xff)
viewMode=Detail
--

That line has 141,065 characters! The incorrect part of the line
should simply be: file:///home/fenix/Música.

It seems something went wrong with the encoding of the Spanish 'ú'
character in 'Música,'
which is the KDE standard directory for 'Music.' If I'm not mistaken,
this folder is created the first
time KDE runs and is locale-based. However, I don't know how to
determine when this issue
occurs or what caused it.

After moving QtProject.conf (I also had a lock file
QtProject.conf.lock reamining of the last crash), I opened VLC, and
this is the content it was recreated with:

--
[FileDialog]
history=@Invalid()
lastVisited=/home/fenix
qtVersion=5.15.15
viewMode=Detail
--

And it works flawlessly. Krita also runs fine as expected.

If I open a Qt6 app, such as Kate, qtVersion displays the correct
latest version:

--
[FileDialog]
history=@Invalid()
lastVisited=file:///tmp/
qtVersion=6.7.2
viewMode=Detail
--

I don't know which app created the shortcuts tag so I can't try to
replicate it. I'm not sure
if this provides any useful information to you or if it can be
considered a bug. I keep
this bug report open in case you need more details. However, if you
believe this isn't a
potential bug, please feel free to close it.



Thank you very much!