Bug#1031080: nvidia-driver: OpenCL compiler dorsn't wok since version 520
Le lundi 13 février 2023 à 12:20 +0100, Andreas Beckmann a écrit : > On 13/02/2023 11.59, Pascal Obry wrote: > > openat(AT_FDCWD, "/usr/lib/x86_64-linux-gnu/libnvidia-nvvm.so.4", > > O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory) > > Please try OpenCL again install after installing libnvidia-nvvm4. No change on my side: === CL_PROGRAM_BUILD_LOG === Preferred work group size multiple (kernel) Warp size (NV) 32 Max sub-groups per work group 0 And the strace output section: ioctl(5, _IOC(_IOC_NONE, 0, 0x22, 0), 0x7ffe9d70f980) = 0 ioctl(4, _IOC(_IOC_READ|_IOC_WRITE, 0x46, 0x29, 0x10), 0x7ffe9d70fa40) = 0 mmap(0x205a0, 2097152, PROT_NONE, MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x205a0 munmap(0x7f3676d9e000, 2494464) = 0 ioctl(5, _IOC(_IOC_NONE, 0, 0x1a, 0), 0x7ffe9d70fd80) = 0 ioctl(4, _IOC(_IOC_READ|_IOC_WRITE, 0x46, 0x2a, 0x20), 0x7ffe9d70ebe0) = 0 write(1, " Preferred work group size mult"..., 4096 Preferred work group size multiple (kernel) Warp size (NV) 32 Max sub-groups per work group 0 -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://photos.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B
Bug#1031080: nvidia-driver: OpenCL compiler dorsn't wok since version 520
0.0) cl_khr_fp64 0x40 (1.0.0) cl_khr_3d_image_writes 0x40 (1.0.0) cl_khr_byte_addressable_store 0x40 (1.0.0) cl_khr_icd 0x40 (1.0.0) cl_khr_gl_sharing 0x40 (1.0.0) cl_nv_compiler_options 0x40 (1.0.0) cl_nv_device_attribute_query 0x40 (1.0.0) cl_nv_pragma_unroll 0x40 (1.0.0) cl_nv_copy_opts 0x40 (1.0.0) cl_khr_gl_event 0x40 (1.0.0) cl_nv_create_buffer 0x40 (1.0.0) cl_khr_int64_base_atomics 0x40 (1.0.0) cl_khr_int64_extended_atomics 0x40 (1.0.0) cl_nv_kernel_attribute 0x40 (1.0.0) cl_khr_device_uuid 0x40 (1.0.0) cl_khr_pci_bus_info 0x40 (1.0.0) cl_khr_external_semaphore 0x9000 (0.9.0) cl_khr_external_memory 0x9000 (0.9.0) cl_khr_external_semaphore_opaque_fd0x9000 (0.9.0) cl_khr_external_memory_opaque_fd 0x9000 (0.9.0) NULL platform behavior clGetPlatformInfo(NULL, CL_PLATFORM_NAME, ...) NVIDIA CUDA clGetDeviceIDs(NULL, CL_DEVICE_TYPE_ALL, ...) Success [NV] clCreateContext(NULL, ...) [default]Success [NV] clCreateContextFromType(NULL, CL_DEVICE_TYPE_DEFAULT) No platform clCreateContextFromType(NULL, CL_DEVICE_TYPE_CPU) No devices found in platform clCreateContextFromType(NULL, CL_DEVICE_TYPE_GPU) No platform clCreateContextFromType(NULL, CL_DEVICE_TYPE_ACCELERATOR) No devices found in platform clCreateContextFromType(NULL, CL_DEVICE_TYPE_CUSTOM) Invalid device type for platform clCreateContextFromType(NULL, CL_DEVICE_TYPE_ALL) No platform ICD loader properties ICD loader Name OpenCL ICD Loader ICD loader Vendor OCL Icd free software ICD loader Version 2.3.1 ICD loader Profile OpenCL 3.0 So it seems that only the CL compiler is broken. Thanks, -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://photos.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B
Bug#1031080: nvidia-driver: OpenCL compiler dorsn't wok since version 520
Hello, Just to say that I have the same issue. This is on darktable when trying to build the OpenCL programs. I'm using: $ apt-cache policy nvidia-driver nvidia-driver: Installed: 525.85.12-1 Candidate: 525.85.12-1 Thanks, -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://photos.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B
Bug#994971: closed by Debian FTP Masters (reply to Andreas Beckmann ) (Bug#994971: fixed in nvidia-graphics-drivers 470.63.01-1)
Hello ! Just installed 470.63.01-1 this morning and I can confirm that the issue is fixed. I have OpenCL activated without any other action. Thanks a lot for the quick resolution. Have a nice day, -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://www.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B signature.asc Description: This is a digitally signed message part
Bug#994971: OpenCL not working with latest Nvidia driver
Hi Klaus, > Thats caused as the modprobe config was dropped. Without, the needed > modules are not loaded automatically anymore. > > A simple `modprobe nvidia-current-uvm` fixes the issue temporarily. > However, the modprobe config needs to come back. Will test this. > By the way, I would rate this as a normal bug instead of grave. I fully agree by re-reading the rating description. Sorry for that. Thanks, -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://www.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B signature.asc Description: This is a digitally signed message part
Bug#994971: OpenCL not working with latest Nvidia driver
Package: nvidia-driver Version: 470.57.02-3 Severity: grave I'm currently using GNU/Debian sid. The current NVidia driver is 470.57.02-2 and OpenCL is working fine. $ clinfo Number of platforms 1 Platform Name NVIDIA CUDA Platform Vendor NVIDIA Corporation Platform Version OpenCL 3.0 CUDA 11.4.94 ... There is a new version available 470.57.02-3 and when installed OpenCL is not supported. clinfo report that there is 0 platform supported/detected. I have this issue with kernel 5.10.0-8-amd64 and new 5.14. The only solution I have found at this point is to revert the NVidia driver to 470.57.02-3 and kernel 5.10. I cannot tell if this is a kernel issue or an NVidia driver one. Maybe someone with more knowledge on this area could help finding out. Thanks, -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://www.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B
Bug#953854: workaround works for me too
For what is worth, the workaround: rm /usr/lib/gimp/2.0/plug-ins/pagecurl/pagecurl Works for me too. -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://www.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B
Bug#892994: chromium 65.x issue with proxy
Hello, Just a note that I still have the same issue with Chromium 69.0.3497.92 Thanks, -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://photos.obry.net http://www.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B
Bug#892994: closed by Michael Gilbert <mgilb...@debian.org> (Bug#892994: fixed in chromium-browser 66.0.3359.117-1)
Sadly this is not fixed by latest version of chromium. I have tested 66.0.3359.117-1 and now 66.0.3359.139-1 and in both cases I have the same issue. And again reverting to 62.0.3202.89-1 (in testing) fix the issue. Can this ticket be reopened? Thanks, -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://photos.obry.net http://www.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B
Bug#892994: chromium 65.x issue with proxy
And when I do chrome://net-internals/#proxy I get: <<< Effective proxy settings Use DIRECT connections. Source: SYSTEM FAILED >>> So no surprise after all, the proxy settings are not retrieved from the OS configuration (GNOME for me). Is there something to do about this? Thanks, -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://photos.obry.net http://www.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B
Bug#895508: closed by Jeremy Bicha <jbi...@debian.org> (Bug#895504: fixed in evolution 3.28.1-2)
Fixed now indeed. Thanks for the quick fix. -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://www.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B signature.asc Description: This is a digitally signed message part
Bug#895508: evolution no quoting when repling to message
Package: evolution Version: 3.28.1-1 After updating evolution to 3.28.1-1 in unstable branch yesterday when replying to a message the original message is not quoted anymore. Reverting to evolution/testing 3.28.0-4 fixed this issue. It seems a recent regression in 3.28.1. Please let me know if you need more information. Thanks! -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://photos.obry.net http://www.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B
Bug#892994: chromium 65.x issue with proxy
Same issue with version 66.0.3359.26-2. And reverting back to 62.0.3202.89-1 makes chromium working with proxy again. Am I the only one to have this issue? I'm wondering, but since this is 100% reproducible I doubt... Thanks, -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://www.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B
Bug#892994: chromium 65.x issue with proxy
Package: chromium Version: 65.0.3325.146 After updating chromium to version 65.0.3325.146 (Unstable) I'm not able to connect with a computer behind a proxy. When I revert to 62.0.3202.89 all is fine. The error message is: <<< The web page is not available ERR_CONNECTION_TIMED_OUT Google Chrome could not load the web page because ... <http://savage.nps.edu> took too long to respond. The website may be down or you may be experiencing issues with your Internet connection. >>> I don't have this issue with Chromium 65.x when there is no proxy. So it seems related to the proxy. The proxy on my machine is properly set and for example I can connect to Internet with Epiphany which uses the same proxy and with Chromium 62.x which is also using the same proxy. I have tested after removing ~/.config/chromium to be sure that an old staled configuration was not in the equation. Please let me know if you need more information. Thanks! -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://photos.obry.net http://www.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B
Bug#888952: nvidia-driver and opencl
Hello! I confirm that this is fixed with nvidia-modprobe 384.111-2. Thanks a lot! -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://www.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B
Bug#888952: nvidia-driver and opencl
Andreas, > Are there any hardening settings enabled on your system that could > prevent this setuid executable from doing its job? > * filesystems mounted with option nosuid > * apparmor > * selinux > ... Yes apparmor is installed. > BTW, which version of the nvidia-modprobe package do you have > installed? Latest version: $ apt-cache policy nvidia-modprobe nvidia-modprobe: Installed: 384.111-1 Candidate: 384.111-1 Version table: *** 384.111-1 750 700 http://ftp.fr.debian.org/debian testing/contrib amd64 Packages 750 http://ftp.fr.debian.org/debian unstable/contrib amd64 Packages 100 /var/lib/dpkg/status 375.26-1 650 650 http://ftp.fr.debian.org/debian stable/contrib amd64 Packages Current nvidia driver in sid is 384.111-4. Thanks, -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://www.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B
Bug#888952: nvidia-driver and opencl
Hi Hiromasa, I found a reproduce step. Could you try this? > I can reproduce with those steps indeed. Thanks a lot! -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://photos.obry.net http://www.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B
Bug#888952: nvidia-driver and opencl
Hello Andreas, Thanks for your feedback. I have just rebooted and tested as you proposed: First, unload is not possible as nvidia is in use. $ sudo modprobe -r nvidia [sudo] password for obry: modprobe: FATAL: Module nvidia_drm is in use. modprobe: FATAL: Error running remove command for nvidia $ lsmod | grep nvidia nvidia_drm 53248 4 drm_kms_helper192512 1 nvidia_drm drm 438272 7 nvidia_drm,drm_kms_helper nvidia_modeset860160 9 nvidia_drm nvidia 13168640 594 nvidia_modeset $ nvidia-modprobe -u Let's check clinfo: $ clinfo Number of platforms 0 Not working, so let's run clinfo as root: $ sudo clinfo Number of platforms 1 Platform Name NVIDIA CUDA Platform Vendor NVIDIA Corporation Platform VersionOpenCL 1.2 CUDA 9.0.282 Platform ProfileFULL_PROFILE Platform Extensions cl_khr_global_int32_base_atomics cl_khr_global_int32_extended_atomics cl_khr_local_int32_base_atomics cl_khr_local_int32_extended_atomics cl_khr_fp64 cl_khr_byte_addressable_store cl_khr_icd cl_khr_gl_sharing cl_nv_compiler_options cl_nv_device_attribute_query cl_nv_pragma_unroll cl_nv_copy_opts cl_khr_gl_event cl_nv_create_buffer Platform Extensions function suffix NV Platform Name NVIDIA CUDA Number of devices 1 Device Name Quadro M1000M Device Vendor NVIDIA Corporation ... All fine now. And running clinfo as user also works fine at this stage and this until I reboot. And the permissions bits are ok: $ ls -la /usr/bin/nvidia-modprobe -rwsr-xr-x 1 root root 34904 Jan 13 16:43 /usr/bin/nvidia-modprobe Please let me know if you want me to do some more testing. This seems fishy and I can assure you that I have the same issue on two different computers. Regards, -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://www.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B
Bug#888952: nvidia-driver and opencl
Package: nvidia-driver Version: 384.111-4 Since 384.111-3 (for sure, maybe even with older version) OpenCL is not activated at boot. That is, after I log: $ clinfo Number of platforms 0 What I found (by chance) is that running clinfo as root works: $ sudo clinfo Number of platforms 1 Platform Name NVIDIA CUDA Platform Vendor NVIDIA Corporation Platform VersionOpenCL 1.2 CUDA 9.0.282 Platform ProfileFULL_PROFILE Platform Extensions cl_khr_global_int32_base_atomics cl_khr_global_int32_extended_atomics cl_khr_local_int32_base_atomics cl_khr_local_int32_extended_atomics cl_khr_fp64 cl_khr_byte_addressable_store cl_khr_icd cl_khr_gl_sharing cl_nv_compiler_options cl_nv_device_attribute_query cl_nv_pragma_unroll cl_nv_copy_opts cl_khr_gl_event cl_nv_create_buffer Platform Extensions function suffix NV ... And *after that* a clinfo as a user works too: $ clinfo Number of platforms 1 Platform Name NVIDIA CUDA ... I don't understand why clinfo as root seems to "unblock" something. Any idea? I have reproduced this 2 times, so I'm pretty sure about the above report even if it seems strange. Let me know if you want me to do some more testing. -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://www.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B
Bug#882801: chromium: segfaults like crazy
Does it runs if started with --disable-extensions ? I'm asking as I have a similar problem and this workaround works for me. Note that it may be the same issue as: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1702501 As described on this ticket it seems to be due to an issue with the integrated with the cast plugin. Another workaround is to stop all network connection before starting chromium. You may want to test this too. Regards, -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://www.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B
Bug#883785: libvirtd 3.10 segfault when starting a VM
Package: libvirt Version: 3.10 Severity: grave With libvirt version 3.10 I cannot start a VM. Reverting to 3.0 (Debian/stable) all is fine. This was initially found in GNOME-Boxes but I have been able to reproduce on the command line using virsh. Note also that I had the same issue with 3.9. On one console: $ LIBVIRT_DEBUG=1 gdb /usr/sbin/libvirtd On a second console, I tried to start the VM: $ virsh start boxes-winxp Then I got this exception from libvirtd: Thread 5 "libvirtd" received signal SIGSEGV, Segmentation fault. [Switching to Thread 0x7febad4a5700 (LWP 7867)] 0x7feb94b109c8 in virStorageFileReportBrokenChain () from /usr/lib/libvirt/connection-driver/libvirt_driver_storage.so (gdb) bt #0 0x7feb94b109c8 in virStorageFileReportBrokenChain () from /usr/lib/libvirt/connection-driver/libvirt_driver_storage.so #1 0x7feb7d266da3 in qemuDomainDetermineDiskChain () from /usr/lib/libvirt/connection-driver/libvirt_driver_qemu.so #2 0x7feb7d28eec2 in qemuProcessPrepareHost () from /usr/lib/libvirt/connection-driver/libvirt_driver_qemu.so #3 0x7feb7d294b71 in qemuProcessStart () from /usr/lib/libvirt/connection-driver/libvirt_driver_qemu.so #4 0x7feb7d2f5201 in ?? () from /usr/lib/libvirt/connection-driver/libvirt_driver_qemu.so #5 0x7feb7d2f58e6 in ?? () from /usr/lib/libvirt/connection-driver/libvirt_driver_qemu.so #6 0x7febb9e5e077 in virDomainCreate (domain=0x7feb980008c0) at ../../../src/libvirt-domain.c:6531 #7 0x56190ba2ed9c in ?? () #8 0x7febb9ec697c in virNetServerProgramDispatchCall (msg=0x56190d9e7590, client=0x56190d9e6fb0, server=0x56190d9d00f0, prog=0x56190d9e4f40) at ../../../src/rpc/virnetserverprogram.c:437 #9 virNetServerProgramDispatch (prog=0x56190d9e4f40, server=0x56190d9d00f0, client=0x56190d9e6fb0, msg=0x56190d9e7590) at ../../../src/rpc/virnetserverprogram.c:307 #10 0x56190ba3e988 in ?? () #11 0x7febb9da1c01 in virThreadPoolWorker ( opaque=opaque@entry=0x56190d9ce9f0) at ../../../src/util/virthreadpool.c:167 #12 0x7febb9da0f78 in virThreadHelper (data=) at ../../../src/util/virthread.c:206 #13 0x7febb68b0519 in start_thread (arg=0x7febad4a5700) at pthread_create.c:456 #14 0x7febb65f2a5f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:97 (gdb) I noticed that running with 3.0 I had a message saying that /dev/sr0 is not accessible. And indeed I do not have a CDROM on this machine. The .xml were migrated from a machine with a CDROM to this new one. Removing: Seems to fix the issue. Yet, libvirt should not crash on this. And the backtrace makes sense with this fix BTW. Please let me know if you need additional information. Thanks, -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://www.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B
Bug#883313: OpenCL clCreateContext fails in 384.x
This bug is actually the same as: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883303 And the same fix works for me: cd /usr/lib/x86_64-linux-gnu sudo ln -s nvidia/current/libnvidia-ptxjitcompiler.so.1 . So after all that seems a simple packaging issue. Thanks, -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://www.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B
Bug#883313: OpenCL clCreateContext fails in 384.x
Package: nvidia-driver Version: 384.98-2 Severity: grave With the latest update (384.x) OpenCL does not work, it is possible to reproduce the issue with clinfo: clCreateContext(NULL, ...) [default] The same error is reported by other applications like darktable. This was working with the version 375.x. Let me know if you need additional information or do some testing on my side. Thanks, -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://www.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B
Bug#873765: same issue for me
I have the same issue since a month now. Any idea to when the GNOME Shell 3.26 will be part of Debian/unstable. Thanks, -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://photos.obry.net http://www.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B
Bug#847590:
And the new version 24.2.0-5 just released is working fine. -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://www.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B
Bug#847590: Acknowledgement (gnome-session crash with latest nvidia driver (375.20))
Ok I found a way to workaround this issue. Downgrading libmozjs-24-0 to the version in testing 24.2.0-3 fixed the issue: $ sudo apt-get install libmozjs-24-0/testing For the record the first non working version is 24.2.0-4. Regards, -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://www.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B
Bug#847590: gnome-session crash with latest nvidia driver (375.20)
Package: gnome-session Version: 3.22.2-1 $ dmesg | grep segfault [ 59.938290] gnome-session-f[2051]: segfault at 0 ip 7fcdc197ea29 sp 7ffcdd4ebab0 error 4 in libgtk-3.so.0.2200.4[7fcdc169c000+6f7000] Am fully up-to-date on Debian/sid. The crash started to occur after the update of this morning where my nvidia driver went from 367.57 to 375.20-4. At this time I cannot log anymore. I get a black screen with the mouse in the middle. The mouse is moving but that's all. Let me know if you need more information. Thanks, -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://photos.obry.net http://www.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B
Bug#843973: brightness set to max when activating screen profile
Package: gnome-color-manager Version: 3.22.2 Since some updates on Debian/sid the brightness is not properly reset on resume after suspend or at boot time. That is, the brightness is always reset to its maximum value. Am fully up-to-date on Debian/sid. Note that this can easily be reproduced by opening the gnome-color- manager and disabling/enabling the screen profile. Each time the profile is activated the brightness is reset to max. Let me know if you need more information. Thanks, -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://www.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B
Bug#837449: brightness not properly reset after suspend
Hi Michael, > gnome-power-manager no longer handles any brightness settings, so > it's most likely not the right package you filed it against. Ok, do you have any idea about the package responsible for this? Thanks, -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://www.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B signature.asc Description: This is a digitally signed message part
Bug#838758: [Pkg-kde-extras] Bug#838758: liblensfun1 packaging
Hi Pino, > What's "acm", and how should it be used? Adobe Camera Model. > Are you sure you have deb-src lines in your /etc/apt/sources.list (or > in any *.list file in /etc/apt/sources.list.d/) for the unstable > distribution, other than stable? Indeed, my bad :( I had commented out the deb-src line for testing and unstable. Fixing that I get the sources for 0.3.2 and It seems that the LF_DIST_MODEL_ACM is not part of this version. It is on the master branch. This ticket can be closed. Sorry for the noise! -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://www.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B signature.asc Description: This is a digitally signed message part
Bug#838758: liblensfun1 packaging
Package: liblensfun1 Version: 0.3.2-3 I was trying to get the "acm" support working in liblensfun. It should be in version 0.3.2 according to the up stream. But it does not work and liblensfun seems to be refusing to understand the model="acm". So, today in unstable we have: $ apt-cache policy liblensfun1 liblensfun1: Installed: 0.3.2-3 Candidate: 0.3.2-3 Version table: *** 0.3.2-3 750 700 http://ftp.fr.debian.org/debian testing/main amd64 Packages 750 http://ftp.fr.debian.org/debian unstable/main amd64 Packages 100 /var/lib/dpkg/status Which looks like the latest lensfun released version, but getting the source I see that 0.2.8 is used! Am I checking incorrectly or is this explaining why acm support in not in liblensfun1? $ apt-get source liblensfun1 Reading package lists... Done Picking 'lensfun' as source package instead of 'liblensfun1' NOTICE: 'lensfun' packaging is maintained in the 'Svn' version control system at: svn://anonscm.debian.org/pkg-kde/kde-extras/lensfun/trunk Need to get 641 kB of source archives. Get:1 http://ftp.fr.debian.org/debian stable/main lensfun 0.2.8-2 (dsc) [1,532 B] Get:2 http://ftp.fr.debian.org/debian stable/main lensfun 0.2.8-2 (tar) [629 kB] Get:3 http://ftp.fr.debian.org/debian stable/main lensfun 0.2.8-2 (diff) [11.0 kB] Fetched 641 kB in 0s (1,220 kB/s) gpgv: Signature made Mon 08 Sep 2014 09:07:05 AM CEST gpgv:using DSA key 4CD1F6A6207F2F7A gpgv: Can't check signature: No public key dpkg-source: warning: failed to verify signature on ./lensfun_0.2.8-2.dsc dpkg-source: info: extracting lensfun in lensfun-0.2.8 dpkg-source: info: unpacking lensfun_0.2.8.orig.tar.bz2 dpkg-source: info: unpacking lensfun_0.2.8-2.debian.tar.xz -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://www.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B
Bug#838200: (gnome-software:15001): Gs-ERROR **: CSS parsing error: not a number
Same for me. I'm on Debian/unstable with gnome-software 3.20.2. -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://www.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B
Bug#837449: brightness not properly reset after suspend
Package: gnome-power-manager Version: 3.21.91-1 Since recent updates on Debian/sid the brightness is not properly reset on resume after suspend or at boot time. That is, the brightness is always reset to its maximum value. Am fully up-to-date on Debian/sid. Let me know if you need more information. Thanks, -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://www.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B
Bug#836210: duplicate and workaround
Michael, I confirm that this is a duplicate of 835822. I also confirm that the workaround is working for me. I think that this ticket can safely be marked as duplicated and closed. Thanks! -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://www.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B
Bug#836212: fixed with today update
A transient issue. All seems to be working fine now with the gnome- shell 3.21.91-2 update. Feel free to close this ticket. Thanks, -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://www.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B
Bug#836212: gnome-shell no more ICC profile for the screen
Package: gnome-shell Version: 3.21.91-1 Since the update of GNOME Shell this morning I have no more ICC profile loaded for my screen. My card is an NVIDIA and I'm using the proprietary driver.gnome-color- manager In the color setting of the GNOME Control Center I do not see my screen listed. I do have printers. So it seems that the issue is only about screen. Note that before updating GNOME Shell I had an update of gnome-color- manager (version 3.21.91 too) and the screen profile was still working. Let me know if you need additional information. -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://www.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B
Bug#836210: network-manager no more wifi
Package: network-manager Version: 1.4.0-3 With the recent update of network-manager I cannot connect to any Wifi hotspot. The list of hotspot is fine, but when I click on any of them nothing happens. In the journal I have: ERROR @wl_cfg80211_scan : WLC_SCAN error (-22 Reverting to 1.2.4-2 solves the issue. So it seems that there is a bug introduced in NM 1.4. Let me know if you need additional information. -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://www.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B
Bug#834455: gnome-terminal: Window height decreases by 1 line with each typed character if multiple tabs are opened
I have the exact same issue since the recent gnome-terminal update. Regards, -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://www.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B
Bug#829677: GNOME Boxes cannot starts VMs
Indeed all is working now. Thanks a lot! -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://www.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B
Bug#829677: GNOME Boxes cannot starts VMs
Package: gnome-boxes Version: 3.20.2-2 Since a recent update I cannot start my virtual machines (all of them). After some time gnome-boxes send a message "Failed to start...". In the syslog I have: libvirtd[11010]: Failed to connect socket to '/run/user/1000/libvirt/virtlogd-sock': No such file or directory libvirtd[11010]: Failed to connect socket to '/run/user/1000/libvirt/virtlogd-sock': No such file or directory org.gnome.Boxes[4789]: (gnome-boxes:10925): Boxes-WARNING **: machine.vala:606: Failed to start debian-live-8: Unable to start domain: Failed to connect socket to '/run/user/1000/libvirt/virtlogd-sock': No such file or directory libvirtd[3571]: libvirt version: 2.0.0, package: 1 (Guido Günther <a...@sigxcpu.org> Fri, 01 Jul 2016 17:54:01 +0200) I did not find a report on Debian for this issue. But I have found this issue reported here: https://bugzilla.redhat.com/show_bug.cgi?id=1351995 It seems that libaudit1 should be upgraded to 2.6.2 (currently 2.6.1 on Debian/sid). So maybe this is just about upgrading this package after all. Let me know if more information is needed. Regards, -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://photos.obry.net http://www.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B
Bug#823785: gnome-shell: segfault shortly after login drops user to console
I have the very same issue. I'm using all packages from GNUI/Debian/sid. GNOME-Shell: 3.20.2-1 nvidia: 352.79-7 Thanks! -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://photos.obry.net http://www.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B
Bug#821110: evolution-ews: password not accepted any more after security-upgrading the system
Hello, I have the same issue and the workaround is also working on my side. Thanks for this workaround Ulrich! -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://v2p.fr.eu.org http://www.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B
Bug#680169: evolution: Evolution hangs when retrieving email
I have the same very same issue. The workaround does not work for me as it also occurs when my computer is back from sleep. In this case the network is reset and Evolution start checking e-mails in all accounts (I have also quite a lot of them). I have to kill Evolution and restart it. Nothing better for now. -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://v2p.fr.eu.org http://www.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B
Bug#812396: Info received (Bug#812396: Acknowledgement (nvidia-kernel-dkms: fail to load nvidia-uvm.))
Confirmed. This is working for me on 349.16-2 Thanks for the quick fix. -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://v2p.fr.eu.org http://www.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B
Bug#812396: Acknowledgement (nvidia-kernel-dkms: fail to load nvidia-uvm.)
] nvidia_uvm: Unknown symbol nvUvmInterfaceAddressSpaceDestroy (err -22) [ 548.197578] nvidia_uvm: no symbol version for nvUvmInterfaceRegisterUvmCallbacks [ 548.197579] nvidia_uvm: Unknown symbol nvUvmInterfaceRegisterUvmCallbacks (err -22) [ 548.197583] nvidia_uvm: no symbol version for nvUvmInterfaceGetGpuArch [ 548.197584] nvidia_uvm: Unknown symbol nvUvmInterfaceGetGpuArch (err -22) [ 548.197589] nvidia_uvm: no symbol version for nvUvmInterfaceChannelAllocate [ 548.197590] nvidia_uvm: Unknown symbol nvUvmInterfaceChannelAllocate (err -22) [ 548.197596] nvidia_uvm: no symbol version for nvUvmInterfaceDupAllocation [ 548.197597] nvidia_uvm: Unknown symbol nvUvmInterfaceDupAllocation (err -22) [ 548.197604] nvidia_uvm: no symbol version for nvUvmInterfaceSessionCreate [ 548.197605] nvidia_uvm: Unknown symbol nvUvmInterfaceSessionCreate (err -22) [ 550.908745] nvidia_uvm: no symbol version for nvUvmInterfaceChannelDestroy [ 550.908749] nvidia_uvm: Unknown symbol nvUvmInterfaceChannelDestroy (err -22) [ 550.908758] nvidia_uvm: no symbol version for nvUvmInterfaceQueryCaps [ 550.908759] nvidia_uvm: Unknown symbol nvUvmInterfaceQueryCaps (err -22) [ 550.908771] nvidia_uvm: no symbol version for nvUvmInterfaceMemoryAllocSys [ 550.908772] nvidia_uvm: Unknown symbol nvUvmInterfaceMemoryAllocSys (err -22) [ 550.908778] nvidia_uvm: no symbol version for nvUvmInterfaceMemoryCpuMap [ 550.908779] nvidia_uvm: Unknown symbol nvUvmInterfaceMemoryCpuMap (err -22) [ 550.908786] nvidia_uvm: no symbol version for nvUvmInterfaceKillChannel [ 550.908787] nvidia_uvm: Unknown symbol nvUvmInterfaceKillChannel (err -22) [ 550.908795] nvidia_uvm: no symbol version for nvUvmInterfaceMemoryCpuUnMap [ 550.908796] nvidia_uvm: Unknown symbol nvUvmInterfaceMemoryCpuUnMap (err -22) [ 550.908804] nvidia_uvm: no symbol version for nvUvmInterfaceAddressSpaceCreateMirrored [ 550.908805] nvidia_uvm: Unknown symbol nvUvmInterfaceAddressSpaceCreateMirrored (err -22) [ 550.908835] nvidia_uvm: no symbol version for nvUvmInterfaceServiceDeviceInterruptsRM [ 550.908836] nvidia_uvm: Unknown symbol nvUvmInterfaceServiceDeviceInterruptsRM (err -22) [ 550.908843] nvidia_uvm: no symbol version for nvUvmInterfaceDeRegisterUvmOps [ 550.908844] nvidia_uvm: Unknown symbol nvUvmInterfaceDeRegisterUvmOps (err -22) [ 550.908851] nvidia_uvm: no symbol version for nvUvmInterfaceMemoryFree [ 550.908851] nvidia_uvm: Unknown symbol nvUvmInterfaceMemoryFree (err -22) [ 550.908858] nvidia_uvm: no symbol version for nvUvmInterfaceGetUvmPrivRegion [ 550.908859] nvidia_uvm: Unknown symbol nvUvmInterfaceGetUvmPrivRegion (err -22) [ 550.908867] nvidia_uvm: no symbol version for nvUvmInterfaceGetAttachedUuids [ 550.908868] nvidia_uvm: Unknown symbol nvUvmInterfaceGetAttachedUuids (err -22) [ 550.908877] nvidia_uvm: no symbol version for nvUvmInterfaceSessionDestroy [ 550.908878] nvidia_uvm: Unknown symbol nvUvmInterfaceSessionDestroy (err -22) [ 550.908885] nvidia_uvm: no symbol version for nvUvmInterfaceCheckEccErrorSlowpath [ 550.908886] nvidia_uvm: Unknown symbol nvUvmInterfaceCheckEccErrorSlowpath (err -22) [ 550.908892] nvidia_uvm: no symbol version for nvUvmInterfaceAddressSpaceCreate [ 550.908893] nvidia_uvm: Unknown symbol nvUvmInterfaceAddressSpaceCreate (err -22) [ 550.908900] nvidia_uvm: no symbol version for nvUvmInterfaceCopyEngineAllocate [ 550.908901] nvidia_uvm: Unknown symbol nvUvmInterfaceCopyEngineAllocate (err -22) [ 550.908907] nvidia_uvm: no symbol version for nvUvmInterfaceAddressSpaceDestroy [ 550.908908] nvidia_uvm: Unknown symbol nvUvmInterfaceAddressSpaceDestroy (err -22) [ 550.908915] nvidia_uvm: no symbol version for nvUvmInterfaceRegisterUvmCallbacks [ 550.908916] nvidia_uvm: Unknown symbol nvUvmInterfaceRegisterUvmCallbacks (err -22) [ 550.908922] nvidia_uvm: no symbol version for nvUvmInterfaceGetGpuArch [ 550.908923] nvidia_uvm: Unknown symbol nvUvmInterfaceGetGpuArch (err -22) [ 550.908930] nvidia_uvm: no symbol version for nvUvmInterfaceChannelAllocate [ 550.908931] nvidia_uvm: Unknown symbol nvUvmInterfaceChannelAllocate (err -22) [ 550.908940] nvidia_uvm: no symbol version for nvUvmInterfaceDupAllocation [ 550.908941] nvidia_uvm: Unknown symbol nvUvmInterfaceDupAllocation (err -22) [ 550.908950] nvidia_uvm: no symbol version for nvUvmInterfaceSessionCreate [ 550.908951] nvidia_uvm: Unknown symbol nvUvmInterfaceSessionCreate (err -22) -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://v2p.fr.eu.org http://www.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B
Bug#812107: nvidia uvm invalid argument
Andreas, > Running reportbug on the system where that actually happened would > have collected valueable system information and logfiles for > debugging. I have a new report using reportbug, see: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812396 Let me know if you need additional information or testing on my side. Regards, -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://v2p.fr.eu.org http://www.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B
Bug#812396: nvidia-kernel-dkms: fail to load nvidia-uvm.
Package: nvidia-kernel-dkms Version: 349.16-1 Severity: grave Tags: upstream Justification: renders package unusable Dear Maintainer, The issue is reported by programs like darktable, for example here is the ouptut on the console: $ darktable modprobe: ERROR: could not insert 'nvidia_current_uvm': Invalid argument modprobe: ERROR: ../libkmod/libkmod-module.c:977 command_do() Error running install command for nvidia_uvm modprobe: ERROR: could not insert 'nvidia_uvm': Operation not permitted The same output can be reproduced by just trying to modprob nvidia-uvm: $ sudo modprobe nvidia-uvm modprobe: ERROR: could not insert 'nvidia_current_uvm': Invalid argument modprobe: ERROR: ../libkmod/libkmod-module.c:977 command_do() Error running install command for nvidia_uvm modprobe: ERROR: could not insert 'nvidia_uvm': Operation not permitted This issue was first seen in nvidia 346.96 and now in 349.16. So current version for testing 340.96-4 does not have this issue. Please let me know if you need me do some more testing. Regards, -- Package-specific info: uname -a: Linux pascal 4.3.0-1-amd64 #1 SMP Debian 4.3.3-7 (2016-01-19) x86_64 GNU/Linux /proc/version: Linux version 4.3.0-1-amd64 (debian-ker...@lists.debian.org) (gcc version 5.3.1 20160114 (Debian 5.3.1-6) ) #1 SMP Debian 4.3.3-7 (2016-01-19) /proc/driver/nvidia/version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 349.16 Wed Apr 8 00:17:22 PDT 2015 GCC version: gcc version 5.3.1 20160121 (Debian 5.3.1-7) lspci 'VGA compatible controller [0300]': 01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GK107GLM [Quadro K1100M] [10de:0ff6] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell GK107GLM [Quadro K1100M] [1028:05cc] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: nvidia Kernel modules: nvidia dmesg: [0.00] Console: colour VGA+ 80x25 [0.259753] vgaarb: setting as boot device: PCI::01:00.0 [0.259754] vgaarb: device added: PCI::01:00.0,decodes=io+mem,owns=io+mem,locks=none [0.259755] vgaarb: loaded [0.259756] vgaarb: bridge control possible :01:00.0 [0.521399] Linux agpgart interface v0.103 [9.811401] nvidia: module license 'NVIDIA' taints kernel. [9.817502] vgaarb: device changed decodes: PCI::01:00.0,olddecodes=io+mem,decodes=none:owns=io+mem [9.817842] [drm] Initialized nvidia-drm 0.0.0 20150116 for :01:00.0 on minor 0 [9.817846] NVRM: loading NVIDIA UNIX x86_64 Kernel Module 349.16 Wed Apr 8 00:17:22 PDT 2015 [ 11.203080] snd_hda_intel :01:00.1: Handle VGA-switcheroo audio client [ 11.679577] input: HDA NVidia HDMI/DP,pcm=3 as /devices/pci:00/:00:01.0/:01:00.1/sound/card1/input17 [ 11.679625] input: HDA NVidia HDMI/DP,pcm=7 as /devices/pci:00/:00:01.0/:01:00.1/sound/card1/input18 [ 103.476413] nvidia_uvm: no symbol version for nvUvmInterfaceChannelDestroy [ 103.476417] nvidia_uvm: Unknown symbol nvUvmInterfaceChannelDestroy (err -22) [ 103.476424] nvidia_uvm: no symbol version for nvUvmInterfaceQueryCaps [ 103.476425] nvidia_uvm: Unknown symbol nvUvmInterfaceQueryCaps (err -22) [ 103.476436] nvidia_uvm: no symbol version for nvUvmInterfaceMemoryAllocSys [ 103.476437] nvidia_uvm: Unknown symbol nvUvmInterfaceMemoryAllocSys (err -22) [ 103.476443] nvidia_uvm: no symbol version for nvUvmInterfaceMemoryCpuMap [ 103.476444] nvidia_uvm: Unknown symbol nvUvmInterfaceMemoryCpuMap (err -22) [ 103.476450] nvidia_uvm: no symbol version for nvUvmInterfaceKillChannel [ 103.476450] nvidia_uvm: Unknown symbol nvUvmInterfaceKillChannel (err -22) [ 103.476457] nvidia_uvm: no symbol version for nvUvmInterfaceMemoryCpuUnMap [ 103.476458] nvidia_uvm: Unknown symbol nvUvmInterfaceMemoryCpuUnMap (err -22) [ 103.476465] nvidia_uvm: no symbol version for nvUvmInterfaceAddressSpaceCreateMirrored [ 103.476466] nvidia_uvm: Unknown symbol nvUvmInterfaceAddressSpaceCreateMirrored (err -22) [ 103.476493] nvidia_uvm: no symbol version for nvUvmInterfaceServiceDeviceInterruptsRM [ 103.476494] nvidia_uvm: Unknown symbol nvUvmInterfaceServiceDeviceInterruptsRM (err -22) [ 103.476501] nvidia_uvm: no symbol version for nvUvmInterfaceDeRegisterUvmOps [ 103.476502] nvidia_uvm: Unknown symbol nvUvmInterfaceDeRegisterUvmOps (err -22) [ 103.476508] nvidia_uvm: no symbol version for nvUvmInterfaceMemoryFree [ 103.476508] nvidia_uvm: Unknown symbol nvUvmInterfaceMemoryFree (err -22) [ 103.476514] nvidia_uvm: no symbol version for nvUvmInterfaceGetUvmPrivRegion [ 103.476515] nvidia_uvm: Unknown symbol nvUvmInterfaceGetUvmPrivRegion (err -22) [ 103.476522] nvidia_uvm: no symbol version for nvUvmInterfaceGetAttachedUuids [ 103.476523] nvidia_uvm: Unknown symbol nvUvmInterfaceGetAttachedUuids (err -22) [ 103.476531] nvidia_uvm: no symbol
Bug#812396: Info received (Bug#812396: Acknowledgement (nvidia-kernel-dkms: fail to load nvidia-uvm.))
And the workaround seems to be: $ sudo modprobe --force-modversion nvidia-current-uvm Which load the module properly. $ lsmod | grep nvidia nvidia_uvm 77824 0 nvidia 8445952 106 nvidia_uvm drm 348160 6 nvidia Regards, -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://v2p.fr.eu.org http://www.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B
Bug#807827: Acknowledgement (evolution shortcut keys not working)
This is fixed in current version. Not sure there was a new version so maybe a transient issue in another package. Anyway, feel free to close this ticket. Regards, -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://v2p.fr.eu.org http://www.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B
Bug#812107: nvidia uvm invalid argument
Hello Andreas, > *How* do you load the module? I'm not loading the module myself actually. > The correct way would be > > modprobe nvidia-uvm > > disregarding any "current" or "legacy-*" in the name. Ok, same error anyway. The error is reported by darktable when starting for example. I had tried to reproduce the error using modprobe to report it without much needed context. Are you saying that you do not have this error on your side? Does: $ modprobe nvidia-uvm works for you with 346.96? Regards, -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://v2p.fr.eu.org http://www.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B
Bug#812107: nvidia uvm invalid argument
Package: nvidia-kernel-dkms Version: 346.96-1 With yesterday update I get: modprobe: ERROR: could not insert 'nvidia_current_uvm': Invalid argument All was fine during installation/compilation: $ ls -al /lib/modules/4.3.0-1-amd64/updates/dkms/nvi* -rw-r--r-- 1 root root 11730792 Jan 20 09:08 /lib/modules/4.3.0-1-amd64/updates/dkms/nvidia-current.ko -rw-r--r-- 1 root root 111776 Jan 20 09:08 /lib/modules/4.3.0-1-amd64/updates/dkms/nvidia-current-uvm.ko But it is not possible to load the nvidia-current-uvm module. -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://v2p.fr.eu.org http://www.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B
Bug#807827: evolution shortcut keys not working
Package: evolution Version: 3.18.2-1 When starting Evolution all is fine. The delete key works as expected or pression [.] goes to next unread message. After some time (sorry no really pattern about when it happens) the keys shortcut are not working. That is I cannot delete a key (nothing happen) or move to next message. I can make this working again sometime by double-clicking on a message. This opens a new window. I then close it and the key are back to working. Sadly even this is working half time. The only real workaround is to close Evolution and open it again. This is quite annoying. I would say that this is "recent", maybe since the move to 3.18. To me it looks like the view listing the threads is loosing the focus. Let me know if you need more information. Thanks. -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://v2p.fr.eu.org http://www.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B
Bug#802655: gnome-color-manager missing primary screen
Hi, > Colour management started working for me today, no idea what change > fixed it. > > (I had to log out and in again for the display to show up in the > settings panel) Likewise. Don't know what has changed. I've seen a colord update one or two days ago and some Gtk libraries and gnome-control-center yesterday. -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://v2p.fr.eu.org http://www.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B
Bug#802655: gnome-color-manager missing primary screen
Some other interresting information: - using lightdm I can see all the screen in gcm - reverting to gdm3/stable I can see all the screen in gcm So it sounds like an issue with gdm3 from testing/unstable version 3.18.0-2 0 Maybe this ticket should be reassigned to gdm3? Regards, -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://v2p.fr.eu.org http://www.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B
Bug#802655: gnome-color-manager missing primary screen
Just a status update to note that this now affects also Debian/testing. Let me know if you need additional information. Regards, -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://v2p.fr.eu.org http://www.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B
Bug#802655: gnome-color-manager missing primary screen
Package: gnome-color-manager Version: 3.18.0-1 Severity: grave Since a recent upgrade (Debian/Sid) the primary screen is not listed in the color manager. I have experienced this issue on two computers. Also the secondary screen when attached is properly listed in the color managed devices. With this bug it is not possible to unset or change the profile for the primary screen. If this can helps: $ gcm-inspect -d (gcm-inspect:5147): Gcm-WARNING **: failed to get XServer profile data: failed to get property (gcm-inspect:5147): Gcm-WARNING **: failed to get XServer protocol version: failed to get property Regards, -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://v2p.fr.eu.org http://www.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B
Bug#800348: empathy crash at startup (segmentation violation)
Confirmed, latest version of Empathy fixes this issue for me. Thanks a lot! -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://v2p.fr.eu.org http://www.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B
Bug#799948: glx-diversions: Upgrade to version 0.6.0 made sddm-greeter crash
Just one precison, I'm using GDM (not sddm) and have the same issue. -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://v2p.fr.eu.org http://www.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B
Bug#800348: empathy crash at startup (segmentation violation)
Package: empathy
Version: 3.12.10-1
I'm using Debian/sid and the crash is due to a recent upgrade on the
system. This very same version was working last Friday (3 days ago).
Here is the last strace log:
futex(0x1721268, FUTEX_WAKE_PRIVATE, 1) = 1
recvmsg(7, 0x7ffd9c6348d0, 0) = -1 EAGAIN (Resource
temporarily unavailable)
poll([{fd=4, events=POLLIN}, {fd=6, events=POLLIN}, {fd=7,
events=POLLIN}, {fd=17, events=POLLIN}, {fd=21, events=POLLIN}], 5, 0)
= 1 ([{fd=6, revents=POLLIN}])
read(6, "\1\0\0\0\0\0\0\0", 16) = 8
sendmsg(17, {msg_name(0)=NULL,
msg_iov(2)=[{"l\2\1\1\330\2\0\0A\0\0\0\37\0\0\0\6\1s\0\5\0\0\0:1.17\0\0\0"...,
48}, {"\6aa{sv}\0\314\2\0\0\250\0\0\0-\0\0\0org.freedesk"..., 728}],
msg_controllen=0, msg_flags=0}, MSG_NOSIGNAL) = 776
write(2, "\n(empathy:16832): GLib-GIO-CRITI"..., 110
(empathy:16832): GLib-GIO-CRITICAL **: g_task_propagate_boolean:
assertion 'task->result_set == TRUE' failed
) = 110
--- SIGSEGV {si_signo=SIGSEGV, si_code=SEGV_MAPERR, si_addr=0x8} ---
+++ killed by SIGSEGV +++
Segmentation fault
--
Pascal Obry / Magny Les Hameaux (78)
The best way to travel is by means of imagination
http://v2p.fr.eu.org
http://www.obry.net
gpg --keyserver keys.gnupg.net --recv-key F949BD3B
Bug#799948: glx-diversions: Upgrade to version 0.6.0 made sddm-greeter crash
Same for me. I confirm that reverting glx-diversion and *nvidia* from unstable to testing fixes this issue. > sudo apt-get install -t testing glx-alternative-nvidia/testing > glx-diversions/testing nvidia-kernel-dkms/testing nvidia-driver/testing > nvidia-driver-bin/testing xserver-xorg-video-nvidia/testing > libegl1-nvidia/testing nvidia-vdpau-driver/testing libgles1-nvidia/testing > libnvidia-eglcore/testing libnvidia-eglcore/testing Didn't tried the Guy suggestion. -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://v2p.fr.eu.org http://www.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B
Bug#761360: possible fix.
Le vendredi 27 mars 2015 à 10:11 +0100, Adi Kriegisch a écrit : I had a similar issue on a fresh setup with NVidia drivers from backports. After resume fonts disappeared and graphic/rendering was 'unstable'. I added 'NVreg_RegisterForACPIEvents=1' to the NVidia kernel modules' options and all the issues were gone. Maybe this helps? In /etc/modprobe.d/nvidia-kernel-common.conf: - options nvidia NVreg_DeviceFileUID=0 NVreg_DeviceFileGID=44 NVreg_DeviceFileMode=0660 + options nvidia NVreg_DeviceFileUID=0 NVreg_DeviceFileGID=44 NVreg_DeviceFileMode=0660 NVreg_RegisterForACPIEvents=1 NVreg_EnableMSI=1 Didn't change anything for me. With the added parameters I still have the garbage in the display when resuming from suspend. -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://v2p.fr.eu.org http://www.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#768896: nvidia-driver: resume from suspend breaks GNOME wallpaper
And also same issue with current experimental Nvidia version 343.36. -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://v2p.fr.eu.org http://www.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#761360: [nvidia-driver] Garbaged screen after suspend to RAM
Same issue with current experimental package 343.36. -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://v2p.fr.eu.org http://www.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#768896: duplicate report
BTW, this is a duplicate of : 761360 -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://v2p.fr.eu.org http://www.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#761360: Bug#768896: nvidia-driver: resume from suspend breaks GNOME wallpaper
Andreas, Control: tag -1 moreinfo upstream Please try the new driver packages available at https://people.debian.org/~anbe/340.58/ Something like adding a new package source deb https://people.debian.org/~anbe/340.58/ ./ should work. (I cannot upload them to unstable currently since I'm waiting for another bugfix in the packaging to migrate to testing.) Just a question. I'm using 343.22 which is a version greater than 340.58 and have the issue. Do you confirm that this is normal and that 340.58 should fix this issue? Is that a specific Debian patch added into this version? Regards, -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://v2p.fr.eu.org http://www.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#765812: closed by Jordi Mallach jo...@debian.org (Bug#765812: fixed in evolution-data-server 3.12.7.1-2)
Yes, I can confirm that this bug is fixed now. Thanks a lot! -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://v2p.fr.eu.org http://www.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#763517: patches breaking color management
In fact no, it is not fixed it was a testing procedure on my side. Sorry! How to reopen this ticket? I have attached a picture of the wrong output from Debian (CUPS 1.7.5) and the correct from Ubuntu (CUPS 1.7.2). We clearly see the purple color cast on the print from Debian (the base picture is BW). Thanks, -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://v2p.fr.eu.org http://www.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B
Bug#768163: CUPS and CM option
Package: CUPS Version: 1.7.5 I just found out that on the CUPS page when defining (or modifying) a printer the Color Calibration Mode check box only appears only when the language of the desktop is set to English. I found this because I'm French and using a french desktop on GNOME Shell. But this option was on a new box I had installed without all locales, so defaulting to English. I can confirm this, by switching from English to French and back the option Color Calibration Mode is present or not. Attached are two screen shots with the pages in French and in English. The screen shots are taken from the same computer. The only change was the default language. Regards, -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://v2p.fr.eu.org http://www.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B
Bug#765436: GNOME-Shell wallpapers and suspend-to-ram/hibernation
Some people on Arch Linux have the same problem and think that the issue is in the NVIDIA proprietary driver: https://bugs.archlinux.org/task/42511 Regards, -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://v2p.fr.eu.org http://www.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#765436: GNOME-Shell wallpapers and suspend-to-ram/hibernation
The problem exists with all NVIDIA driver I have tested: 340.46-1, 340.46-2, 343.22-1 Anyone as an idea of what could be causing this? Which package/application is in charge of displaying the wallpapers? Thanks, -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://v2p.fr.eu.org http://www.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#765726: nvidia-driver 340.46-1 Unusable with GF108 and GT610
I had a similar issue with 340.46 but all is back to normal with 343.22 on my side. Pascal. -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://v2p.fr.eu.org http://www.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#761360: [nvidia-driver] Garbaged screen after suspend to RAM
I have the same problem. Still an issue with 340.46-1 and 340.46-2 updated this morning. -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://v2p.fr.eu.org http://www.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#761360: [nvidia-driver] Garbaged screen after suspend to RAM
And same problem with 343.22-1 from experimental. -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://v2p.fr.eu.org http://www.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#765436: GNOME-Shell wallpapers and suspend-to-ram/hibernation
Marcus, I also get this problem. But this only seems to affect me desktop system with Nvidia graphics (using the proprietary driver), my work laptop and netbook with Intel graphics doesn't get this problem. I'm on Nvidia too. There's also a problem with the right-click menu on the background. If I right-click after having been to suspend, the menu doesn't appear and after this gnome-shell doesn't respond to any mouse input (can't move windows etc.), keyboard still works, and I can restart gnome-shell (alt+f2 r). After restarting, the desktop background is back to normal as well. Pascal, do you see similar problems? Will pay more attention, I had some strange behavior that do look like this indeed. -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://v2p.fr.eu.org http://www.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#765812: GNOME Evolution SIGSEGV with latest SQLite3
Package: evolution Version: 3.12.7-1 I'm on Debian/sid with all packages up-to-date. After upgrading SQLite3 this morning from 3.8.6-1 to 3.8.7-1 GNOME Evolution crashes with a segmentation violation. I got the hint on SQLite3 by running Evolution under gdb, here is the backtrace: Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 0x7fff64ff9700 (LWP 7212)] 0x in ?? () (gdb) bt #0 0x in ?? () #1 0x7fffee7d757b in ?? () from /usr/lib/x86_64-linux-gnu/libsqlite3.so.0 #2 0x7fffee807f4f in ?? () from /usr/lib/x86_64-linux-gnu/libsqlite3.so.0 #3 0x7fffee80824e in ?? () from /usr/lib/x86_64-linux-gnu/libsqlite3.so.0 #4 0x7fffee83a96e in ?? () from /usr/lib/x86_64-linux-gnu/libsqlite3.so.0 #5 0x7fffee83dbc7 in sqlite3_step () from /usr/lib/x86_64-linux-gnu/libsqlite3.so.0 #6 0x7fffee82c8aa in sqlite3_exec () from /usr/lib/x86_64-linux-gnu/libsqlite3.so.0 #7 0x76d9d3c8 in ?? () from /usr/lib/libcamel-1.2.so.49 #8 0x76d9ee6f in camel_db_select () from /usr/lib/libcamel-1.2.so.49 #9 0x76d9efd4 in camel_db_get_folder_uids () from /usr/lib/libcamel-1.2.so.49 #10 0x76db017d in camel_folder_summary_load_from_db () from /usr/lib/libcamel-1.2.so.49 #11 0x7fffcb5f3888 in ?? () from /usr/lib/evolution-data-server/camel-providers/libcamellocal.so #12 0x7fffcb5e7079 in camel_local_summary_load () from /usr/lib/evolution-data-server/camel-providers/libcamellocal.so #13 0x7fffcb5e4c4c in camel_local_folder_construct () from /usr/lib/evolution-data-server/camel-providers/libcamellocal.so #14 0x7fffcb5f07ff in camel_maildir_folder_new () from /usr/lib/evolution-data-server/camel-providers/libcamellocal.so #15 0x7fffcb5f1590 in ?? () from /usr/lib/evolution-data-server/camel-providers/libcamellocal.so #16 0x76e02817 in camel_store_get_folder_sync () from /usr/lib/libcamel-1.2.so.49 #17 0x7fffc8f0b7b1 in e_mail_session_uri_to_folder_sync () from /usr/lib/evolution/3.12/libemail-engine.so.0 #18 0x7fffc8f18546 in ?? () from /usr/lib/evolution/3.12/libemail-engine.so.0 #19 0x7fffc8f13017 in ?? () from /usr/lib/evolution/3.12/libemail-engine.so.0 #20 0x738852b8 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #21 0x73884925 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #22 0x773400a4 in start_thread (arg=0x7fff64ff9700) at pthread_create.c:309 #23 0x73551c2d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 (gdb) quit Reverting SQLite3 to 3.8.6-1 fixes the problem on my side. Thanks, -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://v2p.fr.eu.org http://www.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#765436: GNOME-Shell wallpapers and suspend-to-ram/hibernation
Package: gnome-shell Version: 3.14.0 I'm on Debian/sid with all packages up-to-date. Since the switch to gnome-shell 3.14.0, when the computer is coming out of suspend-to-ram/hibernation the wallpapers are not properly refreshed. Both wallpapers (standard and the one used on lock screen) are affected they are displayed with random pixels as if using some non initialized memory. After some time (1 minute or 2 minutes) the standard wallpaper is back to normal. But the wallpaper on the lock screen seems to never be displayed properly. I have this issue on 2 computers and on Google+ some guys have the same issue. Thanks, -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://v2p.fr.eu.org http://www.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#764472: cups creates millions of temporary files when printing
Same issue here. I'm monitoring the python process just after a print. Indeed killing .../system-config-printer/scp-dbus-service.py stop the creation of the temp PPD links. Yet this does not occurs every time. Just tried again, first print all was ok, then second print and I saw my disk start working. This time the process was creating the links. So maybe some race conditions somewhere. For sure this is quite a bad issue! Regards, -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://v2p.fr.eu.org http://www.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#763517: Info received (Bug#763517: patches breaking color management)
After upgrading to 1.7.5-4 on Debian/sid I cannot reproduce this issue even though there is nothing to explain this. Maybe a transient issue on color management on Debian/sid? Anyway, I think this can be closed at this time. Thanks, -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://v2p.fr.eu.org http://www.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#763517: patches breaking color management
Package: cups Version: 1.7.5-2 Severity: critical I've been chasing this bug since some time now. The issue has been discussed in the CUPS and printing-architecture mailing-list. For the context. I'm printing on an Epson 3880 since 2 years with an home made profile. And recently I found that my prints were really bad. After investigation I found that reverting to CUPS 1.7.5-1 from testing fixes the problem. I have then found out that one difference with 1.7.5-2 is that the ColorManaged option is now listed as CM-Calibration in /etc/cups/printers.conf. Looking at the GNU/Debian change between 1.7.5-1 and 1.7.5-2 I think that the culprit is the following: [ Till Kamppeter ] * Updated color management extension patch to the newest version from Joseph Simon, especially to fix PPD updates via the web interface (LP: #1362321). (http://metadata.ftp-master.debian.org/changelogs//main/c/cups/cups_1.7.5-3_changelog) It should probably be removed or fixed as it does not only fix the PPD updates via the web interface but also breaks color management done down the piper by the filters. Please let me know if you need more information. I can also do some testing but I've already wasted lot of paper and ink :) Thanks, -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://v2p.fr.eu.org http://www.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#763517: patches breaking color management
Le mardi 30 septembre 2014 à 19:34 +0200, Didier Raboud a écrit : Really bad prints don't qualify for 'critical' bug severity; requalifying to 'important', see [0]. Well it is critical to me as I was preparing an exposition :) -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://v2p.fr.eu.org http://www.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#763517: patches breaking color management
Joe, What filters are you using to print? I assume that you are using the latest version of cups-filters? Yes, I was using CUPS 1.7.5-2 with cups-filters 1.0.58-1. I'm full up-to-date on unstable. And this was not working. After I reverted to CUPS 1.7.5-1 (and still using cups-filters 1.0.58-1) I had correct color rendering. And I found out that the almost only visible change related to color rendering was the CM-Calibration option in 1.7.5-2 vs ColorManaged in 1.7.5-1 in /etc/cups/printers.conf. Let me know if something is still missing. -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://v2p.fr.eu.org http://www.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#754205: poedit: When updating the catalog I get the alert 'An assertion failed'
Same here! -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://v2p.fr.eu.org http://www.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#746643: closed by Andreas Beckmann a...@debian.org (Bug#746643: fixed in nvidia-graphics-drivers 331.79-1)
Working on my side! Thanks for fixing. -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://v2p.fr.eu.org http://www.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#747292: gdm3: Unable to login after last upgrade (version 3.8.4-7): fails to start a GNOME session
Hello Benjamin, You should be able to use systemd just once from your bootloader. Here is a good start: https://wiki.debian.org/systemd Ok, quite easy in fact. Just did it and could connect using gdm3. Thanks a lot! -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://v2p.fr.eu.org http://www.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#747292: gdm3: Unable to login after last upgrade (version 3.8.4-7): fails to start a GNOME session
Hello Benjamin, Pascal, I also successfully tried lightdm. I got your point, and thank you very much for your messages. However, since GDM3 comes with Gnome 3, I am pretty sure it would be comfy for most users to just get GDM3 working stable without installing any other package (even if those packages are better in any way; it is not the point). Also, I am using the **unstable** distribution, and I knew this distribution comes with issues. That’s fine. By the way, I guess my humble role as a GNU/Debian user is to report bugs, and give the most information I can to Maintainers so they can fix those bugs (or not). So, IMHO, running away to install an alternative is not a solution. ;-) Sure, I did not meant to say that it was OK. I was just giving a workaround to be able to continue working using the computer. I fully agree that using lightdm is not a solution :) Yes, I'm also running unstable and there was since this report two new version of gdm3, but all fails the login. Not sure what causes this problem at this point... -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://v2p.fr.eu.org http://www.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#747292: gdm3: Unable to login after last upgrade (version 3.8.4-7): fails to start a GNOME session
Laurent, I think we have identified the issue, basically logind is started/activated too late. We'll try to fix this to preserve compatibility with other initsystem than systemd, but I guess it's a good occasion to start using it if you don't mind :) Sure, ready for anything... I would suggest you to try booting using systemd by setting the init kernel parameter to /lib/systemd/systemd. If it's successful, you can install systemd-sysv and _purge_ systemd-shim and then again reboot. Can you tell me more about the procedure? Is there some Web page explaining that? I must say that this is beyond my current knowledge as I've never change the kernel init parameters. Thanks, -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://v2p.fr.eu.org http://www.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#746643: confirm that it is not fixed in 331.67-2
On a second machine I have the same issue. So this bug is not fixed. The nvidia-uvm module is now found but I get the Invalid parameters message on the two computers I have tested: Any idea? -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://v2p.fr.eu.org http://www.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#746643: confirm that it is not fixed in 331.67-2
To be more precise here is the exact error message reported: modprobe: ERROR: could not insert 'nvidia_uvm': Invalid argument -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://v2p.fr.eu.org http://www.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#747292: gdm3 and session
Just to say that I have the exact same problem with my sid installation. The only workaround I found is to install lightdm which let me open a gnome-shell session. -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://v2p.fr.eu.org http://www.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#747292: gdm3: Unable to login after last upgrade (version 3.8.4-7): fails to start a GNOME session
Benjamin, I am thinking to try another DM (like, say, LightDM or SLiM). Will see if the problem still occurs or not. I will let you know. As reported earlier I have tested this and it works for me. I can definitely connect to my gnome-shell session using lightdm. -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://v2p.fr.eu.org http://www.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#746643: closed by Andreas Beckmann a...@debian.org (Bug#746643: fixed in nvidia-graphics-drivers 331.67-2)
Don't seem to be fixed. After building my OpenCL application was still not working and the nvidia-uvm module was not loaded. Trying to load it manually gave me: # insmod /var/lib/dkms/nvidia-current/331.67/3.14-1-amd64/x86_64/module/nvidia-uvm.ko insmod: ERROR: could not insert module /var/lib/dkms/nvidia-current/331.67/3.14-1-amd64/x86_64/module/nvidia-uvm.ko: Invalid parameters Any idea? -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://v2p.fr.eu.org http://www.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#746643: OpenCL not supported by lastest NVIDIA driver
Package: nvidia-kernel-dkms
Version: 331.67-1
The nvidia-current-uvm.ko is not built and so OpenCL is not available
on GNU/Debian.
I'm using GNU/Debian unstable and kernel 3.14 (but I had the same
issue with 3.13).
Building nvidia-current-uvm.ko manually solves the issue. I have seen
this reported for
Ubuntu but not for Debian.
What I have done to fix the issue is:
# cd /usr/src/nvidia-current-331.67/
# vi dkms.conf
Add at then end:
# uvm
BUILT_MODULE_NAME[1]=nvidia-uvm
DEST_MODULE_NAME[1]=${PACKAGE_NAME}-uvm
BUILT_MODULE_LOCATION[1]=uvm/
DEST_MODULE_LOCATION[1]=/updates/dkms
MAKE[0]+=; make -C uvm module KERNEL_UNAME=${kernelver}
KBUILD_EXTMOD=${dkms_tree}/${PACKAGE_NAME}/${PACKAGE_VERSION}/build/uvm
CLEAN+=; make -C uvm clean
# dkms remove nvidia-current/331.67 -k $(uname -r)
# dkms build nvidia-current/331.67
Then reboot, or:
# insmod /var/lib/dkms/nvidia-current/331.67/$(uname
-r)/x86_64/module/nvidia-current-uvm.ko
Note that all the sources are already in Debian source package, just
that part of it is not built.
--
Pascal Obry / Magny Les Hameaux (78)
The best way to travel is by means of imagination
http://v2p.fr.eu.org
http://www.obry.net
gpg --keyserver keys.gnupg.net --recv-key F949BD3B
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#714422: gnome-shell: 3.8.3 no display shown
Le lundi 17 mars 2014 à 14:41 +, althaser a écrit : Hey, Could you please still reproduce this issue with newer gnome-shell version like 3.8.4-5+b1 ? Tried 3 times, no freeze. Looks like it is fixed. Thanks! -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://v2p.fr.eu.org http://www.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#714422: black screen
Same for me today. Just black screen, looks like a gdm3 issue. Pascal. -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://v2p.fr.eu.org http://www.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#714422: Info received (black screen)
Ok, found another thread about this issue. It is fixed by installing libpam-systemd. Pascal. -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://v2p.fr.eu.org http://www.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#720283: gnome-shell fails to start, clutter problems
Very same issue for me after upgrading yesterday. Pascal. -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://v2p.fr.eu.org http://www.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#652592: Sametime accounts no longer have server setting, and do not connect
Same problem for me. Is there a solution for this problem? Any workaround? Thanks. -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://v2p.fr.eu.org http://www.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#683092: Bad news
After some days of testing it seems that it is a bit better as it crash only 50% (used to me more than 80%) of time during resume from suspend! So there is still some issues with account services I fear! Pascal. -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://v2p.fr.eu.org http://www.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#683092: More data, good news?
Some good news. I have recompiled accountservice yesterday from Git sources and got two wake-up in a raw of my computer without problem. It uses to crash most of the time. So it may be the case that this issue has been fixed in version 0.6.27 or 0.6.28. I'll send another report in 2 or 3 days... Crossing fingers! -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://v2p.fr.eu.org http://www.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#683092: Looks like it is not fixed
I have accountservice 0.6.24-1 from experimental and still have the crash. It happens for me 80% of the time when I resume from suspend. I have also compiler accountservice from Git repository (version 0.6.26) and still have the problem. Looks like this bug does not want to die :( Am I the only one to still have this issue? -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://v2p.fr.eu.org http://www.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B
