Bug#956811: [3dprinter-general] Bug#956811: Bug#956811: Confirmed

2021-01-21 Thread Riccardo Gagliarducci
Thank you Gregor,
I'm using Appimage (which works fine).
I plan to switch to Bullseye very soon: I will definitely try the package and 
post the results here.

However, I find these reports interesting: at least it is known that there is a 
problem with this package.
I've been using Debian for years, but I don't know what the package management 
policies are, I'd just like to point out
that right now, the package is useless.

If I try to run cura using:
QT_QUICK_CONTROLS_STYLE=material cura

I get a some warnings and the UI is still broken: 
https://www.brixelstudio.it/Cura.png


Thank you,
Riccardo

ps. I accidentally sent my personal data in a previous e-mail: I wrote to 
owner@... is it right? Who can I contact to
delete my phone number? Thanks!



On Thu, 21 Jan 2021 20:39:32 +0100 Gregor Riepl  wrote:
> > The stable debian Buster is shipping a very old version...
> > https://packages.debian.org/buster/cura
> 
> Well... I'm sorry to say, but it's very, very unlikely that buster will
> receive an updated Cura version. New package versions usually land in
> sid and testing, and a new Debian stable release will happen later this
> year anyway.
> 
> If you'd like to run a current version of Cura (that works a little bit
> better than the outdated one in buster), I warmly recommend that you
> update to bullseye now and help with testing. As a matter of fact, I
> think Debian testing is much more suited for desktop use than stable.
> 
> If you just want to "make it work", you can use the AppImage provided by
> UltiMaker, of course.
> 
> That being said, the rendering issue is still present in 4.8. If the
> upstream patch won't help, we'll have to go back and see if anything can
> be done on the Debian side.
> 
> In the meantime, can you try running Cura with the theme override I
> mentioned? Perhaps it will help for now.
>



Bug#956811: Confirmed

2021-01-20 Thread Riccardo Gagliarducci
I do confirm that the bug is present now in the cura package (v. 3.3.1) and 
makes the software unusable.

This has been reported to Cura developers:
https://github.com/Ultimaker/Cura/issues/6841

It is not related to video card (it does not work with modern intel or nvidia).
Using Debian 10, 4.19.0-13-amd64 #1 SMP Debian 4.19.160-2 (2020-11-28) x86_64 
GNU/Linux

Thank you,
Riccardo



Bug#904917: Gnome randomly crash and restart to login.

2018-11-30 Thread Riccardo Gagliarducci
Dear maintainer,

on the Dell G5 system this is a relevant dmesg log of a gnome crash /
restart.

Thank you,
Ricky


[   50.196800] nouveau :01:00.0: firmware: direct-loading firmware
nvidia/gp106/gr/fecs_bl.bin
[   50.197146] nouveau :01:00.0: firmware: direct-loading firmware
nvidia/gp106/gr/fecs_inst.bin
[   50.197393] nouveau :01:00.0: firmware: direct-loading firmware
nvidia/gp106/gr/fecs_data.bin
[   50.197627] nouveau :01:00.0: firmware: direct-loading firmware
nvidia/gp106/gr/fecs_sig.bin
[   50.197870] nouveau :01:00.0: firmware: direct-loading firmware
nvidia/gp106/gr/gpccs_bl.bin
[   50.198150] nouveau :01:00.0: firmware: direct-loading firmware
nvidia/gp106/gr/gpccs_inst.bin
[   50.198298] nouveau :01:00.0: firmware: direct-loading firmware
nvidia/gp106/gr/gpccs_data.bin
[   50.198394] nouveau :01:00.0: firmware: direct-loading firmware
nvidia/gp106/gr/gpccs_sig.bin
[   50.199588] nouveau :01:00.0: firmware: direct-loading firmware
nvidia/gp106/sec2/image.bin
[   50.199878] nouveau :01:00.0: firmware: direct-loading firmware
nvidia/gp106/sec2/desc.bin
[   50.200022] nouveau :01:00.0: firmware: direct-loading firmware
nvidia/gp106/sec2/sig.bin
[   50.202673] nouveau :01:00.0: firmware: direct-loading firmware
nvidia/gp106/acr/ucode_load.bin
[   50.203144] nouveau :01:00.0: firmware: direct-loading firmware
nvidia/gp106/acr/ucode_unload.bin
[   50.203509] nouveau :01:00.0: firmware: direct-loading firmware
nvidia/gp106/acr/bl.bin
[   50.203671] nouveau :01:00.0: firmware: direct-loading firmware
nvidia/gp106/acr/unload_bl.bin
[   50.204262] nouveau :01:00.0: firmware: direct-loading firmware
nvidia/gp106/nvdec/scrubber.bin
[   52.352010] nouveau :01:00.0: secboot: error during falcon
reset: -110
[   52.352023] nouveau :01:00.0: gr: init failed, -110
[   52.885053] fuse init (API version 7.27)
[   55.621474] Bluetooth: RFCOMM TTY layer initialized
[   55.621486] Bluetooth: RFCOMM socket layer initialized
[   55.621495] Bluetooth: RFCOMM ver 1.11
[   58.296647] rfkill: input handler disabled
[   61.275809] pci_raw_set_power_state: 9 callbacks suppressed
[   61.275811] nouveau :01:00.0: Refused to change power state,
currently in D3
[  241.914334] rfkill: input handler enabled
[  242.243702] nouveau :01:00.0: Refused to change power state,
currently in D3
[  243.782266] nouveau :01:00.0: firmware: direct-loading firmware
nvidia/gp106/nvdec/scrubber.bin
[  245.823526] nouveau :01:00.0: secboot: error during falcon
reset: -110
[  245.823539] nouveau :01:00.0: gr: init failed, -110
[  253.707510] nouveau :01:00.0: Refused to change power state,
currently in D3
[  254.370102] nouveau :01:00.0: firmware: direct-loading firmware
nvidia/gp106/nvdec/scrubber.bin
[  256.415398] nouveau :01:00.0: secboot: error during falcon
reset: -110
[  256.415406] nouveau :01:00.0: gr: init failed, -110
[  257.889260] rfkill: input handler disabled
[  264.783277] nouveau :01:00.0: Refused to change power state,
currently in D3



Bug#904917: general: Gnome randomly crash and restart to login.

2018-11-13 Thread Riccardo Gagliarducci
I have used gnome on the previus cited Lenovo Laptop without extension
for some months and gnome is generally more stable BUT occasionaly I
had the same identical crash. Nvidia drivers were loaded.


I had setup the same identical system on a Dell G5, withOUT nvidia
drivers but nouveau only and I suffer the same identical trouble, about
once every day.

Gnome exensions are enabled:
- Freon
- GsConnect

I do 3d graphics but crash is totally indipendent and happens even on a
soft use (mail, browser, ecc...).

Here some info. I'll post dmesg info next crash.

Thank you,
Riccardo


# lsmod | grep nouveau
nouveau  2162688  1
mxm_wmi16384  1 nouveau
ttm   131072  1 nouveau
drm_kms_helper196608  2 i915,nouveau
drm   471040  23 drm_kms_helper,i915,ttm,nouveau
i2c_algo_bit   16384  2 i915,nouveau
video  45056  4 dell_wmi,dell_laptop,i915,nouveau
wmi28672  6
dell_wmi,wmi_bmof,dell_smbios,dell_wmi_descriptor,mxm_wmi,nouveau
button 16384  1 nouveau


# lspci -nnk | grep -iA2 vga 
00:02.0 VGA compatible controller [0300]: Intel Corporation Device
[8086:3e9b]
Subsystem: Dell Device [1028:0825]
Kernel driver in use: i915
--
01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GP106M
[GeForce GTX 1060] [10de:1c20] (rev a1)
Kernel driver in use: nouveau
Kernel modules: nouveau






Il giorno dom, 29/07/2018 alle 15.50 +0200, Riccardo Gagliarducci ha
scritto:
> Package: general
> Severity: grave
> Justification: causes non-serious data loss
> 
> Dear Maintainer,
> 
> on Lenovo laptop ideapad 520 Gnome randomly crash and, after some
> seconds of
> text, the system ask me to login to gnome, as if I had access to it
> during
> boot.
> All the opened software and data is gone.
> 
> It happens 1 to 4 times a day.
> 
> I have consulted the syslog, kern, Xorg but I can't find any hints on
> the
> package is causing the error.
> 
> 
> The laptop harware is:
> Intel® Core™ i7-8550U CPU @ 1.80GHz × 8
> 
> and double graphic card:
> 
> VGA compatible controller: Intel Corporation UHD Graphics 620
> (Kabylake
> GT2)(rev 07)
> Subsystem: Lenovo UHD Graphics 620
> Kernel driver in use: i915
> 
> 3D controller: NVIDIA Corporation GP108M [GeForce MX150] (rev
> ff)
> Kernel modules: nvidia
> 
> The system is Debian GNU/Linux buster/sid 64 bit using bumblebee and
> Nvidia
> driver Version: 390.48.
> 
> 
> Thank you,
> Riccardo
> 
> 
> 
> -- System Information:
> Debian Release: buster/sid
>   APT prefers testing
>   APT policy: (500, 'testing'), (2, 'unstable')
> Architecture: amd64 (x86_64)
> 
> Kernel: Linux 4.16.0-2-amd64 (SMP w/8 CPU cores)
> Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8),
> LANGUAGE=it_IT.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash



Bug#904917: general: Gnome randomly crash and restart to login.

2018-08-05 Thread Riccardo Gagliarducci
I'm leaving for holidays, may I freeze this bug until end of August?

In dmsg, I found: 
[ 6737.746966] gnome-shell[2131]: segfault at 663466343778 ip
7f0a52cf3c31 sp 7ffd58e51e98 error 4 in libgobject-
2.0.so.0.5600.1[7f0a52cbe000+52000]

But I'd like to investigate more...
Thank you,
Riccardo


Il giorno sab, 04/08/2018 alle 02.21 +0200, Simon Richter ha scritto:
> Hi,
> 
> On 04.08.2018 01:32, Riccardo Gagliarducci wrote:
> 
> > after firmware update it still happens ~once a day,
> > still without doing anything particular.
> 
> Is anything listed in the kernel log?
> 
> After a crash, log back in, then, as root:
> 
> # cat /proc/uptime
> 
> The first number is the number of seconds the system is running.
> 
> # dmesg
> 
> This will dump the kernel logfile to the console. At the beginning of
> each line is a timestamp. The uptime you got earlier gives you a
> rough
> estimate which lines are recent, these have a good chance of being
> related.
> 
>Simon
> 



Bug#904917: general: Gnome randomly crash and restart to login.

2018-08-03 Thread Riccardo Gagliarducci
Thank you,
after firmware update it still happens ~once a day,
still without doing anything particular.
RG

Il giorno dom, 29/07/2018 alle 11.03 -0300, Henrique de Moraes Holschuh
ha scritto:
> On Sun, 29 Jul 2018, Riccardo Gagliarducci wrote:
> > on Lenovo laptop ideapad 520 Gnome randomly crash and, after some
> > seconds of
> 
> Are you using the latest version of the ideapad 520 firmware
> (BIOS/UEFI
> and EC) ?  If not, please upgrade it.
> 



Bug#904917: general: Gnome randomly crash and restart to login.

2018-07-29 Thread Riccardo Gagliarducci
Package: general
Severity: grave
Justification: causes non-serious data loss

Dear Maintainer,

on Lenovo laptop ideapad 520 Gnome randomly crash and, after some seconds of
text, the system ask me to login to gnome, as if I had access to it during
boot.
All the opened software and data is gone.

It happens 1 to 4 times a day.

I have consulted the syslog, kern, Xorg but I can't find any hints on the
package is causing the error.


The laptop harware is:
Intel® Core™ i7-8550U CPU @ 1.80GHz × 8

and double graphic card:

VGA compatible controller: Intel Corporation UHD Graphics 620 (Kabylake
GT2)(rev 07)
Subsystem: Lenovo UHD Graphics 620
Kernel driver in use: i915

3D controller: NVIDIA Corporation GP108M [GeForce MX150] (rev ff)
Kernel modules: nvidia

The system is Debian GNU/Linux buster/sid 64 bit using bumblebee and Nvidia
driver Version: 390.48.


Thank you,
Riccardo



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

Kernel: Linux 4.16.0-2-amd64 (SMP w/8 CPU cores)
Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8),
LANGUAGE=it_IT.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash


Bug#855940: alacarte: Python context internal state bug. Syslog

2017-02-23 Thread Riccardo Gagliarducci
Package: alacarte
Version: 3.11.91-2
Severity: normal

Dear Maintainer,

checking /var/log/syslog I discover that:

Feb 23 10:32:29 triceratopo alacarte-made-7.desktop[1599]: ERROR: Python
context internal state bug. this should not happen!
Feb 23 10:32:29 triceratopo alacarte-made-7.desktop[1599]: ERROR: Python
context internal state bug. this should not happen!
Feb 23 10:32:29 triceratopo alacarte-made-7.desktop[1599]: ERROR: Python
context internal state bug. this should not happen!
Feb 23 10:32:29 triceratopo alacarte-made-7.desktop[1599]: ERROR: Python
context internal state bug. this should not happen!

The log reports this line hundreds of times each seconds,
ending with a huge log:

root@triceratopo:/var/log# ls -lah syslog
-rw-r- 1 root adm 766M feb 23 15:40 syslog

I do expect:
alacarte not causing this error
limit the report of this error

alacarte version is
3.11.91-2
status is
Ok, installed


Thank you,
Riccardo



-- System Information:
Debian Release: 8.7
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.16.0-4-amd64 (SMP w/8 CPU cores)
Locale: LANG=it_IT.utf8, LC_CTYPE=it_IT.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages alacarte depends on:
ii  gir1.2-gdkpixbuf-2.0  2.31.1-2+deb8u5
ii  gir1.2-glib-2.0   1.42.0-2.2
ii  gir1.2-gmenu-3.0  3.13.3-6
ii  gir1.2-gtk-3.03.14.5-1+deb8u1
ii  gnome-menus   3.13.3-6
ii  python-gi 3.14.0-1
pn  python:any

alacarte recommends no packages.

alacarte suggests no packages.

-- no debconf information