Bug#928739: geogebra: poor integration with KDE

2019-05-09 Thread gcab_dzan
Package: geogebra
Version: 4.0.34.0+dfsg1-7
Severity: normal

Dear Maintainer,

   I installed Geogebra on Buster with KDE and just at opening  I noticed that
 characters and graphics display was not up to that of previous versions (I am 
using
Geogebra since long).
   Then on the Algebra pane the properties of the objects are not accessible 
with the right
   click, but only with the double click (but not the Free Objects) or from the 
Edit menu, which presents the full list
   of objects.
   There might be other inconvenients I did not went through yet.
   Thanks for uor attention and work
   Giuliano Cabrele


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

Kernel: Linux 4.19.0-4-amd64 (SMP w/12 CPU cores)
Kernel taint flags: TAINT_CRAP, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US 
(charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages geogebra depends on:
ii  default-jre [java9-runtime] 2:1.11-71
ii  libcommons-collections3-java3.2.2-2
ii  libcommons-math-java2.2-7
ii  libfreehep-graphics2d-java  2.1.1-6
ii  libfreehep-graphicsio-emf-java  2.1.1-emfplus+dfsg1-4
ii  libfreehep-graphicsio-java  2.1.1-5
ii  libfreehep-graphicsio-pdf-java  2.1.1+dfsg-3
ii  libfreehep-graphicsio-svg-java  2.1.1-5
ii  libfreehep-io-java  2.0.2-6
ii  libfreehep-util-java2.0.2-7
ii  libfreehep-xml-java 2.1.2+dfsg1-5
ii  libjfugue-java  4.0.3-4
ii  libjlatexmath-java  1.0.7-3
ii  librhino-java   1.7.7.1-1
ii  mathpiper   0.81f+svn4469+dfsg3-3
ii  openjdk-11-jre [java9-runtime]  11.0.3+1-1

geogebra recommends no packages.

Versions of packages geogebra suggests:
ii  cups  2.2.10-6

-- no debconf information


Bug#927770: lios does not work properly on KDE

2019-04-28 Thread gcab_dzan


> Il 28 aprile 2019 alle 14.14 Samuel Thibault  ha 
> scritto:

> 
> Could you try to install python3-gi-cairo ?
> 
Yes, together with version _2.7-3~0, it works!
Now the thumbnail can be loaded in the central pane, and rotated, can select 
the areas and recognize them.
I am not familiar with lios, but as far as I can tell, now it works as expected.
We can consider the bug solved, thanks indeed for your effort

Giuliano Cabrele



Bug#927770: lios does not work properly on KDE

2019-04-27 Thread gcab_dzan
I downloaded and tried to install ( with dpkg -i) the version that you 
indicated:

the installation did not complete because of the error reported in the 
attachment, and the application did not start.

Maybe I should have disinstalled the previous version first ? or anything else ?
giuliano@a64-tst:~$ su
Password: 
root@a64-tst:/home/giuliano# cd Downloads/
root@a64-tst:/home/giuliano/Downloads# ls
 1553968398633 IMG_20190109_152402.jpg  'Louane 
- Je vole.mp3'
 BSI_Hydrofoil_Aquabike_30Jun20176-small.jpg   IMG_20190411_192056.jpg   
NDP472-KB4054530-x86-x64-AllOS-ENU.exe
 hardware_my_computer_3_99679  lios_2.7-3~0_all.deb  
VID_20170519_180152.mp4
root@a64-tst:/home/giuliano/Downloads# dpkg -i lios_2.7-3~0_all.deb 
dpkg: warning: 'ldconfig' not found in PATH or not executable
dpkg: warning: 'start-stop-daemon' not found in PATH or not executable
dpkg: error: 2 expected programs not found in PATH or not executable
Note: root's PATH should usually contain /usr/local/sbin, /usr/sbin and /sbin
root@a64-tst:/home/giuliano/Downloads# su -
root@a64-tst:~# cd /home/giuliano/Downloads/
root@a64-tst:/home/giuliano/Downloads# ls
 1553968398633 IMG_20190109_152402.jpg  'Louane 
- Je vole.mp3'
 BSI_Hydrofoil_Aquabike_30Jun20176-small.jpg   IMG_20190411_192056.jpg   
NDP472-KB4054530-x86-x64-AllOS-ENU.exe
 hardware_my_computer_3_99679  lios_2.7-3~0_all.deb  
VID_20170519_180152.mp4
root@a64-tst:/home/giuliano/Downloads# dpkg -i lios_2.7-3~0_all.deb 
(Reading database ... 326655 files and directories currently installed.)
Preparing to unpack lios_2.7-3~0_all.deb ...
Unpacking lios (2.7-3~0) over (2.7-2) ...
Setting up lios (2.7-3~0) ...
Sorry: TabError: inconsistent use of tabs and spaces in indentation (main.py, 
line 1109)
dpkg: error processing package lios (--install):
 installed lios package post-installation script subprocess returned error exit 
status 1
Processing triggers for desktop-file-utils (0.23-4) ...
Processing triggers for mime-support (3.62) ...
Processing triggers for man-db (2.8.5-2) ...
Errors were encountered while processing:
 lios
root@a64-tst:/home/giuliano/Downloads# 








Bug#927770: lios does not work properly on KDE

2019-04-26 Thread gcab_dzan
Thanks, Samuel, for the reply.
I am attaching the warning provided as soon as I launch Lios from KDE 
Applications, and what I get after trying to load an image, which appears as an 
icon on the left, but could not expand in the central pane, although I could 
launch the "recognize" by right clicking on it.

I am going to try the version you indicated, and will let you know.

> Il 23 aprile 2019 alle 10.36 Samuel Thibault  ha 
> scritto:
> 
> 
> Hello,
> 
> gcab_d...@libero.it, le mar. 23 avril 2019 01:10:38 +0200, a ecrit:
> > Launching it graphically, it pops an advise that cannot find the hunspell/ 
> > etc.
> > language pack which is instead installed.
> 
> I don't have the issue, could you send a picture of the advice?
> 
> > Launching it from terminal I get the warning reported in the attached. 
> 
> Most warnings should be harmless except
> 
> >   File "/usr/lib/python3/dist-packages/lios/main.py", line 1300, in 
> > ocr_selected_areas
> > progress_step = 1/len(self.imageview.get_selection_list());
> > ZeroDivisionError: division by zero
> 
> which is a no-go :)
> 
> Could you try the package from
> http://people.debian.org/~sthibault/tmp/buster-tmp/lios_2.7-3~0_all.deb
> ?
> 
> Samuel

Bug#927770: lios does not work properly on KDE

2019-04-22 Thread gcab_dzan
Package: lios
Version: 2.7-2
Severity: important

Dear Maintainer,

  I installed Lios on Buster with KDE.

Launching it graphically, it pops an advise that cannot find the hunspell/ etc. 
language pack which is instead installed.

Launching it from terminal I get the warning reported in the attached. 

The lios window opens, I can load an image (as filter ?) and the thumb shows on 
the left column, but no way to get it to appear on the central pane and choose 
the part to recognize.

But I can OCR (in english, at least) the whole image. 

That's much of a pity since lios looks to be the only GUI front-end to 
tesseract working on KDE.

Thus I hope the problem can be solved quickly, and thanks indeed for your 
attention and commitment.

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

Kernel: Linux 4.19.0-4-amd64 (SMP w/12 CPU cores)
Kernel taint flags: TAINT_CRAP, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US 
(charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages lios depends on:
ii  aspell-en2018.04.16-0-1
ii  espeak   1.48.04+dfsg-7
ii  gir1.2-gst-plugins-base-1.0  1.14.4-1
ii  gir1.2-gstreamer-1.0 1.14.4-1
ii  gir1.2-gtk-3.0   3.24.5-1
ii  gir1.2-vte-2.91  0.54.2-2
ii  imagemagick  8:6.9.10.23+dfsg-2
ii  imagemagick-6.q16 [imagemagick]  8:6.9.10.23+dfsg-2
ii  poppler-utils0.71.0-3
ii  python3  3.7.2-1
ii  python3-enchant  2.0.0-1
ii  python3-gi   3.30.4-1
ii  python3-sane 2.8.3-1+b2
ii  python3-speechd  0.9.0-5
ii  tesseract-ocr4.0.0-2

lios recommends no packages.

Versions of packages lios suggests:
pn  cuneiform  

-- no debconf information
giuliano@a64-tst:~$ lios
/usr/lib/python3/dist-packages/lios/ui/gtk/text_view.py:21: PyGIWarning: Gtk 
was imported without specifying a version first. Use gi.require_version('Gtk', 
'3.0') before import to ensure that the right version gets loaded.
  from gi.repository import Gtk
/usr/lib/python3/dist-packages/lios/ui/gtk/print_dialog.py:23: PyGIWarning: 
PangoCairo was imported without specifying a version first. Use 
gi.require_version('PangoCairo', '1.0') before import to ensure that the right 
version gets loaded.
  from gi.repository import PangoCairo
/usr/lib/python3/dist-packages/lios/cam.py:19: PyGIWarning: GstVideo was 
imported without specifying a version first. Use gi.require_version('GstVideo', 
'1.0') before import to ensure that the right version gets loaded.
  from gi.repository import GdkX11, GstVideo
/usr/lib/python3/dist-packages/lios/ui/gtk/terminal.py:21: PyGIWarning: Vte was 
imported without specifying a version first. Use gi.require_version('Vte', 
'2.91') before import to ensure that the right version gets loaded.
  from gi.repository import Gtk, GObject, Vte

(lios:2874): Gtk-WARNING **: 00:01:59.778: Theme parsing error: gtk.css:127:35: 
The style property GtkButton:child-displacement-x is deprecated and shouldn't 
be used anymore. It will be removed in a future version

(lios:2874): Gtk-WARNING **: 00:01:59.778: Theme parsing error: gtk.css:128:35: 
The style property GtkButton:child-displacement-y is deprecated and shouldn't 
be used anymore. It will be removed in a future version

(lios:2874): Gtk-WARNING **: 00:01:59.778: Theme parsing error: gtk.css:129:34: 
The style property GtkCheckButton:indicator-size is deprecated and shouldn't be 
used anymore. It will be removed in a future version

(lios:2874): Gtk-WARNING **: 00:01:59.778: Theme parsing error: gtk.css:132:46: 
The style property GtkScrolledWindow:scrollbars-within-bevel is deprecated and 
shouldn't be used anymore. It will be removed in a future version

(lios:2874): Gtk-WARNING **: 00:01:59.798: Cannot connect attribute 'text' for 
cell renderer class 'lios+ui+gtk+tree_view+CellRendererToggle' since attribute 
does not exist
update_scanner_list Started
TypeError: Couldn't find foreign struct converter for 'cairo.Context'
TypeError: Couldn't find foreign struct converter for 'cairo.Context'
TypeError: Couldn't find foreign struct converter for 'cairo.Context'
TypeError: Couldn't find foreign struct converter for 'cairo.Context'
TypeError: Couldn't find foreign struct converter for 'cairo.Context'
TypeError: Couldn't find foreign struct converter for 'cairo.Context'
TypeError: Couldn't find foreign struct converter for 'cairo.Context'
TypeError: Couldn't find foreign struct converter for 'cairo.Context'
TypeError: Couldn't find foreign struct converter for 'cairo.Context'
TypeError: Couldn't find foreign struct converter for 'cairo.Context'
TypeError: Couldn't find foreign struct 

Bug#926474: [Pkg-samba-maint] Bug#926474: smbclient: Can browse samba shares as root but not as user

2019-04-08 Thread gcab_dzan

Installed winbind (and then also iibpam-winbind, iibnss-winbind) : no change on 
smbtree output command.

The warning about "messaging context" is always there in the first line, 
followed either by nothing, or by only the remote (win xp) shares, or by the 
complete list of shares. The behaviour is quite random and could not grasp 
under which conditions I get one or the other situation. Once the complete list 
has appeared after a long time (some 5 -10 min.). When the local (buster) 
shares are not shown, I cannot browse them from win xp, otherwise I can do that 
flawlessly.

However,  now I realized an unexpected outcome

1) running Dolphin as user, opening /Network/Shared Folders (SMB) I get an 
empty window

2) addressing Dolphin to open smb://casa(=workgroup) I get the error warning

"Internal Error
Please send a full bug report at http://bugs.kde.org
Unknown error condition in stat: File exists"

or instead, going to smb://(user)@(workgroup), i get
"Internal Error
Please send a full bug report at http://bugs.kde.org
libsmbclient reported an error, but did not specify what the problem is. This 
might indicate a severe problem with your network - but also might indicate a 
problem with libsmbclient.
If you want to help us, please provide a tcpdump of the network interface while 
you try to browse (be aware that it might contain private data, so do not post 
it if you are unsure about that - you can send it privately to the developers 
if they ask for it)"

3) but if I address Dolphin to directly go to smb://(remote host) or 
smb://(user)@(remote host) then - after being requested and giving  the 
password - I CAN ACCESS the remote shares, and, as far as I could see, I can 
fully operate r/w as allowed in smb.conf.
Same for the local shares.
Even more surprisingly (it seems that) I can access local and remote shares 
INDEPENDENTLY from whether smbtree lists  them or not.

Given the invitation above to submit a tcpdump report, I installed wireshark 
and took a dump for each of the cases above, together with a snapshot of 
Dolphin in/out put, and I am available to submit them privately if of interest.


Finally, allow me to ask what "messaging context" is? which process is supposed 
to activate that?

Thanks for attention and kind regards


Bug#926474: [Pkg-samba-maint] Bug#926474: smbclient: Can browse samba shares as root but not as user

2019-04-06 Thread gcab_dzan
a) no, winbind is not installed (and is not installed under Stretch 9.8, where 
the samba connection is working perfectly).
b) for the moment, I just set up a point-to-point ethernet cable connection 
with an old pc running winxp, within the same workgroup, and I just use the 
file \etc\hosts to map the addresses (pinging is ok both ways). 
c) don't get what you mean by command; I use smbtree to check that the shares 
on both pc's are visible, after that (normally) I can browse through a file 
manager, and in fact I can do that through Krusader running with root 
privileges.



> Il 6 aprile 2019 alle 21.58 Mathieu Parent  ha scritto:
> 
> 
> Le sam. 6 avr. 2019 à 16:00,  a écrit :
> >
> > Hi, Mathieu, thanks for your reply.
> >
> > I tried either with the new smb.conf (att. smb.conf.up1)  suggested during 
> > installing samba, and with the version taken from previous releases and 
> > which is working flawlessly in Stretch (att. smb.conf.ucf-old). Does not 
> > change the problem.
> 
> Is Winbind installed? Are you using pam_winbind and nss_winbind? What
> is your complete command?
> 
> Regards
> 
> --
> Mathieu Parent



Bug#926474: Fwd: Re: [Pkg-samba-maint] Bug#926474: smbclient: Can browse samba shares as root but not as user

2019-04-06 Thread gcab_dzan

 Messaggio originale --
Da: gcab_d...@libero.it
A: Mathieu Parent 
Data: 6 aprile 2019 alle 15.59
Oggetto: Re: [Pkg-samba-maint] Bug#926474: smbclient: Can browse samba shares 
as root but not as user


Hi, Mathieu, thanks for your reply.

I tried either with the new smb.conf (att. smb.conf.up1)  suggested during 
installing samba, and with the version taken from previous releases and which 
is working flawlessly in Stretch (att. smb.conf.ucf-old). Does not change the 
problem.





 


smb.conf.up1
Description: Binary data


smb.conf.ucf-old
Description: Binary data


Bug#926474: smbclient: Can browse samba shares as root but not as user

2019-04-05 Thread gcab_dzan
Package: smbclient
Version: 2:4.9.5+dfsg-2
Severity: important

Dear Maintainer,

 in a freshly installed testing/buster release, I installed samba + 
smbclient and reproduced the same configuration
 (smb.conf, smbpasswd for root and for user) that is perfectly working on a 
Stretch release installed in a separated partition .
Testparm gives a positive result, and  # pdbedit -w -L correctly provides
root:0::564A9466B5B97FEBE398359543B5B07D:[U 
 ]:LCT-5CA4C2F8:
giuliano:1000::8C869E0D14E71B60877E785FE5F8A299:[U
  ]:LCT-5CA4C312:

Issuing the command smbtree as root I can see the available local and remote 
resources, however issuing the same command
 as user I get
"Unable to initialize messaging context" on the first line,
followed either by nothing, or by an incorrect or partial list of the shares.
Restarting samba (# /usr/sbin/service smbd restart) then smbtree shows all the 
shares, always with the same message on first
line, but I cannot browse them:
Dolphin does not show anything under Samba Shares.

I have quite a limited experience and do not know which other details might be 
of interest.

Thanks for your attention and work
Giuliano Cabrele




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

Kernel: Linux 4.19.0-4-amd64 (SMP w/12 CPU cores)
Kernel taint flags: TAINT_CRAP
Locale: LANG=en_US.UTF-8, LC_CTYPE=C.UTF-8 (charmap=locale: Cannot set LC_ALL 
to default locale: No such file or directory
UTF-8), LANGUAGE=en_US (charmap=locale: Cannot set LC_ALL to default locale: No 
such file or directory
UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages smbclient depends on:
ii  dpkg  1.19.6
ii  libarchive13  3.3.3-4
ii  libbsd0   0.9.1-2
ii  libc6 2.28-8
ii  libpopt0  1.16-12
ii  libreadline7  7.0-5
ii  libsmbclient  2:4.9.5+dfsg-2
ii  libtalloc22.1.14-2
ii  libtevent00.9.37-1
ii  samba-common  2:4.9.5+dfsg-2
ii  samba-libs2:4.9.5+dfsg-2

smbclient recommends no packages.

Versions of packages smbclient suggests:
ii  cifs-utils   2:6.8-2
pn  heimdal-clients  

-- debconf information:
perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
LANGUAGE = "en_US",
LC_ALL = (unset),
LC_TIME = "it_IT.UTF-8",
LC_MONETARY = "it_IT.UTF-8",
LC_CTYPE = "C.UTF-8",
LC_MEASUREMENT = "it_IT.UTF-8",
LANG = "en_US.UTF-8"
are supported and installed on your system.
perl: warning: Falling back to a fallback locale ("en_US.UTF-8").
locale: Cannot set LC_ALL to default locale: No such file or directory


Bug#906194: attaching "make.log"

2018-08-15 Thread gcab_dzan
DKMS make.log for virtualbox-5.2.16 for kernel 4.9.0-7-686-pae (i686)
Tue Aug 14 20:17:45 CEST 2018
make: Entering directory '/usr/src/linux-headers-4.9.0-7-686-pae'
  LD  /var/lib/dkms/virtualbox/5.2.16/build/built-in.o
make[4]: dpkg-architecture: Command not found
  LD  /var/lib/dkms/virtualbox/5.2.16/build/vboxdrv/built-in.o
  CC [M]  /var/lib/dkms/virtualbox/5.2.16/build/vboxdrv/linux/SUPDrv-linux.o
In file included from 
/var/lib/dkms/virtualbox/5.2.16/build/include/VBox/types.h:30:0,
 from 
/var/lib/dkms/virtualbox/5.2.16/build/vboxdrv/linux/../SUPDrvInternal.h:35,
 from 
/var/lib/dkms/virtualbox/5.2.16/build/vboxdrv/linux/SUPDrv-linux.c:32:
/var/lib/dkms/virtualbox/5.2.16/build/include/iprt/types.h:280:9: error: 
unknown type name ‘__uint128_t’
 typedef __uint128_t uint128_t;
 ^~~
/var/lib/dkms/virtualbox/5.2.16/build/include/iprt/types.h:299:9: error: 
unknown type name ‘__int128_t’
 typedef __int128_t int128_t;
 ^~
In file included from 
/var/lib/dkms/virtualbox/5.2.16/build/include/iprt/cpuset.h:31:0,
 from 
/var/lib/dkms/virtualbox/5.2.16/build/include/VBox/sup.h:34,
 from 
/var/lib/dkms/virtualbox/5.2.16/build/vboxdrv/linux/../SUPDrvInternal.h:36,
 from 
/var/lib/dkms/virtualbox/5.2.16/build/vboxdrv/linux/SUPDrv-linux.c:32:
/var/lib/dkms/virtualbox/5.2.16/build/include/iprt/asm.h: In function 
‘ASMAtomicXchgPtr’:
/var/lib/dkms/virtualbox/5.2.16/build/include/iprt/asm.h:540:92: warning: cast 
from pointer to integer of different size [-Wpointer-to-int-cast]
 return (void RT_FAR *)ASMAtomicXchgU64((volatile uint64_t RT_FAR *)(void 
RT_FAR *)ppv, (uint64_t)pv);

^
/var/lib/dkms/virtualbox/5.2.16/build/include/iprt/asm.h:540:12: warning: cast 
to pointer from integer of different size [-Wint-to-pointer-cast]
 return (void RT_FAR *)ASMAtomicXchgU64((volatile uint64_t RT_FAR *)(void 
RT_FAR *)ppv, (uint64_t)pv);
^
In file included from 
/var/lib/dkms/virtualbox/5.2.16/build/include/iprt/cpuset.h:31:0,
 from 
/var/lib/dkms/virtualbox/5.2.16/build/include/VBox/sup.h:34,
 from 
/var/lib/dkms/virtualbox/5.2.16/build/vboxdrv/linux/../SUPDrvInternal.h:36,
 from 
/var/lib/dkms/virtualbox/5.2.16/build/vboxdrv/linux/SUPDrv-linux.c:32:
/var/lib/dkms/virtualbox/5.2.16/build/include/iprt/asm.h: In function 
‘ASMAtomicXchgR0Ptr’:
/var/lib/dkms/virtualbox/5.2.16/build/include/iprt/asm.h:595:88: warning: cast 
from pointer to integer of different size [-Wpointer-to-int-cast]
 return (RTR0PTR)ASMAtomicXchgU64((volatile uint64_t RT_FAR *)(void RT_FAR 
*)ppvR0, (uint64_t)pvR0);

^
/var/lib/dkms/virtualbox/5.2.16/build/include/iprt/asm.h:595:12: warning: cast 
to pointer from integer of different size [-Wint-to-pointer-cast]
 return (RTR0PTR)ASMAtomicXchgU64((volatile uint64_t RT_FAR *)(void RT_FAR 
*)ppvR0, (uint64_t)pvR0);
^
/var/lib/dkms/virtualbox/5.2.16/build/include/iprt/asm.h: In function 
‘ASMAtomicCmpXchgPtrVoid’:
/var/lib/dkms/virtualbox/5.2.16/build/include/iprt/asm.h:968:80: warning: cast 
from pointer to integer of different size [-Wpointer-to-int-cast]
 return ASMAtomicCmpXchgU64((volatile uint64_t RT_FAR *)(void RT_FAR *)ppv, 
(uint64_t)pvNew, (uint64_t)pvOld);

^
/var/lib/dkms/virtualbox/5.2.16/build/include/iprt/asm.h:968:97: warning: cast 
from pointer to integer of different size [-Wpointer-to-int-cast]
 return ASMAtomicCmpXchgU64((volatile uint64_t RT_FAR *)(void RT_FAR *)ppv, 
(uint64_t)pvNew, (uint64_t)pvOld);

 ^
/var/lib/dkms/virtualbox/5.2.16/build/include/iprt/asm.h: In function 
‘ASMAtomicCmpXchgExPtrVoid’:
/var/lib/dkms/virtualbox/5.2.16/build/include/iprt/asm.h:1341:82: warning: cast 
from pointer to integer of different size [-Wpointer-to-int-cast]
 return ASMAtomicCmpXchgExU64((volatile uint64_t RT_FAR *)(void RT_FAR 
*)ppv, (uint64_t)pvNew, (uint64_t)pvOld, (uint64_t RT_FAR *)ppvOld);

  ^
/var/lib/dkms/virtualbox/5.2.16/build/include/iprt/asm.h:1341:99: warning: cast 
from pointer to integer of different size [-Wpointer-to-int-cast]
 return ASMAtomicCmpXchgExU64((volatile uint64_t RT_FAR *)(void RT_FAR 
*)ppv, (uint64_t)pvNew, (uint64_t)pvOld, (uint64_t RT_FAR *)ppvOld);

   ^
/var/lib/dkms/virtualbox/5.2.16/build/include/iprt/asm.h: In function 
‘ASMAtomicReadPtr’:
/var/lib/dkms/virtualbox/5.2.16/build/include/iprt/asm.h:2019:12: warning: cast 

Bug#839236: same problem

2018-01-19 Thread gcab_dzan
Dear Maintainers,

I am having the same problem as that signalled by B.N.S.Robson, on the current 
stable version 0.14.0-4
of sddm.

I have an old desktop i686 (MB ASUS A7V600-X, AMD Athlon XP 2400+, ATI Radeon 
9200) on which
Jessie with KDE4 is running fine.

I tried a clean install, on a separated partition, of Stretch 9.3 with KDE 
desktop.
No error during installation, but at the start-up the graphic login is not 
activated
(screen totally black, and no mouse pointer), and can only log via tty2.

The last line of the dmesg output (file attached) reads
“sddm-greeter[456]: segfault at 4 ip af76076d sp bfe6e500 error 4 in 
libLLVM-3.9.so.1[aee5a000+2d1b000]”

I tried reinstalling with  the Xfce desktop instead of KDE, and it looks ok.

I had the same situation also with Stretch 9.2.1 and filed a bug a couple of 
months ago (#881543). against the package  libllvm3.9.
 And up to now I did not see any follow-up at all.
Now I found that this same bug was signalled more than one year ago, but also 
this is left without
any even minimal comment in the “Unclassified”.

Regards

Giuliano C
[0.00] Linux version 4.9.0-4-686-pae (debian-ker...@lists.debian.org) 
(gcc version 6.3.0 20170516 (Debian 6.3.0-18) ) #1 SMP Debian 4.9.65-3 
(2017-12-03)
[0.00] x86/fpu: Legacy x87 FPU detected.
[0.00] x86/fpu: Using 'eager' FPU context switches.
[0.00] e820: BIOS-provided physical RAM map:
[0.00] BIOS-e820: [mem 0x-0x0009fbff] usable
[0.00] BIOS-e820: [mem 0x0009fc00-0x0009] reserved
[0.00] BIOS-e820: [mem 0x000f-0x000f] reserved
[0.00] BIOS-e820: [mem 0x0010-0x3fffafff] usable
[0.00] BIOS-e820: [mem 0x3fffb000-0x3fffefff] ACPI data
[0.00] BIOS-e820: [mem 0x3000-0x3fff] ACPI NVS
[0.00] BIOS-e820: [mem 0xfec0-0xfec00fff] reserved
[0.00] BIOS-e820: [mem 0xfee0-0xfee00fff] reserved
[0.00] BIOS-e820: [mem 0x-0x] reserved
[0.00] Notice: NX (Execute Disable) protection missing in CPU!
[0.00] SMBIOS 2.3 present.
[0.00] DMI: System Manufacturer System Name/A7V600-X, BIOS ASUS 
A7V600-X ACPI BIOS Revision 1009 06/28/2005
[0.00] e820: update [mem 0x-0x0fff] usable ==> reserved
[0.00] e820: remove [mem 0x000a-0x000f] usable
[0.00] e820: last_pfn = 0x3fffb max_arch_pfn = 0x100
[0.00] MTRR default type: uncachable
[0.00] MTRR fixed ranges enabled:
[0.00]   0-9 write-back
[0.00]   A-E uncachable
[0.00]   F-F write-protect
[0.00] MTRR variable ranges enabled:
[0.00]   0 base 0 mask FC000 write-back
[0.00]   1 disabled
[0.00]   2 disabled
[0.00]   3 disabled
[0.00]   4 disabled
[0.00]   5 disabled
[0.00]   6 disabled
[0.00]   7 base 0F800 mask FFC00 write-combining
[0.00] x86/PAT: Configuration [0-7]: WB  WC  UC- UC  WB  WC  UC- WT  
[0.00] initial memory mapped: [mem 0x-0x03df]
[0.00] Base memory trampoline at [c009b000] 9b000 size 16384
[0.00] BRK [0x03957000, 0x03957fff] PGTABLE
[0.00] BRK [0x03958000, 0x03959fff] PGTABLE
[0.00] BRK [0x0395a000, 0x0395afff] PGTABLE
[0.00] BRK [0x0395b000, 0x0395bfff] PGTABLE
[0.00] RAMDISK: [mem 0x35ec-0x36f57fff]
[0.00] ACPI: Early table checksum verification disabled
[0.00] ACPI: RSDP 0x000F5E30 14 (v00 ASUS  )
[0.00] ACPI: RSDT 0x3FFFB000 30 (v01 ASUS   A7V600-X 
42302E31 MSFT 31313031)
[0.00] ACPI: FACP 0x3FFFB0B2 74 (v01 ASUS   A7V600-X 
42302E31 MSFT 31313031)
[0.00] ACPI: DSDT 0x3FFFB126 003098 (v01 ASUS   A7V600-X 
1000 MSFT 010B)
[0.00] ACPI: FACS 0x3000 40
[0.00] ACPI: BOOT 0x3FFFB030 28 (v01 ASUS   A7V600-X 
42302E31 MSFT 31313031)
[0.00] ACPI: APIC 0x3FFFB058 5A (v01 ASUS   A7V600-X 
42302E31 MSFT 31313031)
[0.00] ACPI: Local APIC address 0xfee0
[0.00] 133MB HIGHMEM available.
[0.00] 889MB LOWMEM available.
[0.00]   mapped low ram: 0 - 379fe000
[0.00]   low ram: 0 - 379fe000
[0.00] Zone ranges:
[0.00]   DMA  [mem 0x1000-0x00ff]
[0.00]   Normal   [mem 0x0100-0x379fdfff]
[0.00]   HighMem  [mem 0x379fe000-0x3fffafff]
[0.00] Movable zone start for each node
[0.00] Early memory node ranges
[0.00]   node   0: [mem 0x1000-0x0009efff]
[0.00]   node   0: [mem 0x0010-0x3fffafff]
[0.00] Initmem setup node 0 [mem 

Bug#881543: -- updating --

2017-11-16 Thread gcab_dzan
Upon various retrials in installation and investigation I could determine the 
following facts.

 a) booting on an installation with KDE selected, the stop point occurred at
“[   31.724333] sddm-greeter[459]: segfault at 4 ip af76076d sp bfeca190 error 
4 in libLLVM-3.9.so.1[aee5a000+2d1b000]”
(see att. dmesg3a.txt)

 b) installing from the DVD without any DE, then adding the non-free ati 
drivers, the X11 and finally the Xfce packages,
I could successfuly boot into the Xfce desktop.

c) adding to the installation above the basic KDE files (unselecting the sddm) 
I could arrive up to the Xfce login prompt,
get the due selection for choosing to start the Plasma environment, and got 
blocked with a
“[  255.753733] ksplashqml[1091]: segfault at 4 ip adc0e76d sp bf8a8040 error 4 
in libLLVM-3.9.so.1[ad308000+2d1b000]”
“[  323.574779] plasmashell[1452]: segfault at 4 ip a92e476d sp bfecb690 error 
4 in libLLVM-3.9.so.1[a89de000+2d1b000]”
(see att. dmesg6a.txt)


So I re-assigned this bug to libLLVM, but I do not have the competence to 
definitely assert that.
## Upon installation of KDE (without smmd) together with Xfce   ###

[0.00] Linux version 4.9.0-4-686-pae (debian-ker...@lists.debian.org) 
(gcc version 6.3.0 20170516 (Debian 6.3.0-18) ) #1 SMP Debian 4.9.51-1 
(2017-09-28)
[0.00] x86/fpu: Legacy x87 FPU detected.
[0.00] x86/fpu: Using 'eager' FPU context switches.
[0.00] e820: BIOS-provided physical RAM map:
[0.00] BIOS-e820: [mem 0x-0x0009fbff] usable
[0.00] BIOS-e820: [mem 0x0009fc00-0x0009] reserved
[0.00] BIOS-e820: [mem 0x000f-0x000f] reserved
[0.00] BIOS-e820: [mem 0x0010-0x3fffafff] usable
[0.00] BIOS-e820: [mem 0x3fffb000-0x3fffefff] ACPI data
[0.00] BIOS-e820: [mem 0x3000-0x3fff] ACPI NVS
[0.00] BIOS-e820: [mem 0xfec0-0xfec00fff] reserved
[0.00] BIOS-e820: [mem 0xfee0-0xfee00fff] reserved
[0.00] BIOS-e820: [mem 0x-0x] reserved
[0.00] Notice: NX (Execute Disable) protection missing in CPU!
[0.00] SMBIOS 2.3 present.
[0.00] DMI: System Manufacturer System Name/A7V600-X, BIOS ASUS 
A7V600-X ACPI BIOS Revision 1009 06/28/2005
[0.00] e820: update [mem 0x-0x0fff] usable ==> reserved
[0.00] e820: remove [mem 0x000a-0x000f] usable
[0.00] e820: last_pfn = 0x3fffb max_arch_pfn = 0x100
[0.00] MTRR default type: uncachable
[0.00] MTRR fixed ranges enabled:
[0.00]   0-9 write-back
[0.00]   A-E uncachable
[0.00]   F-F write-protect
[0.00] MTRR variable ranges enabled:
[0.00]   0 base 0 mask FC000 write-back
[0.00]   1 disabled
[0.00]   2 disabled
[0.00]   3 disabled
[0.00]   4 disabled
[0.00]   5 disabled
[0.00]   6 disabled
[0.00]   7 base 0F800 mask FFC00 write-combining
[0.00] x86/PAT: Configuration [0-7]: WB  WC  UC- UC  WB  WC  UC- WT  
[0.00] initial memory mapped: [mem 0x-0x03df]
[0.00] Base memory trampoline at [c009b000] 9b000 size 16384
[0.00] BRK [0x03957000, 0x03957fff] PGTABLE
[0.00] BRK [0x03958000, 0x03959fff] PGTABLE
[0.00] BRK [0x0395a000, 0x0395afff] PGTABLE
[0.00] BRK [0x0395b000, 0x0395bfff] PGTABLE
[0.00] RAMDISK: [mem 0x35ec4000-0x36f59fff]
[0.00] ACPI: Early table checksum verification disabled
[0.00] ACPI: RSDP 0x000F5E30 14 (v00 ASUS  )
[0.00] ACPI: RSDT 0x3FFFB000 30 (v01 ASUS   A7V600-X 
42302E31 MSFT 31313031)
[0.00] ACPI: FACP 0x3FFFB0B2 74 (v01 ASUS   A7V600-X 
42302E31 MSFT 31313031)
[0.00] ACPI: DSDT 0x3FFFB126 003098 (v01 ASUS   A7V600-X 
1000 MSFT 010B)
[0.00] ACPI: FACS 0x3000 40
[0.00] ACPI: BOOT 0x3FFFB030 28 (v01 ASUS   A7V600-X 
42302E31 MSFT 31313031)
[0.00] ACPI: APIC 0x3FFFB058 5A (v01 ASUS   A7V600-X 
42302E31 MSFT 31313031)
[0.00] ACPI: Local APIC address 0xfee0
[0.00] 133MB HIGHMEM available.
[0.00] 889MB LOWMEM available.
[0.00]   mapped low ram: 0 - 379fe000
[0.00]   low ram: 0 - 379fe000
[0.00] Zone ranges:
[0.00]   DMA  [mem 0x1000-0x00ff]
[0.00]   Normal   [mem 0x0100-0x379fdfff]
[0.00]   HighMem  [mem 0x379fe000-0x3fffafff]
[0.00] Movable zone start for each node
[0.00] Early memory node ranges
[0.00]   node   0: [mem 0x1000-0x0009efff]
[0.00]   node   0: [mem 0x0010-0x3fffafff]
[0.00] Initmem