Bug#942292: exim4.template.conf for clean buster install av_scanner incorrect
On 14/10/2019 16:50, Marc Haber wrote: On Mon, Oct 14, 2019 at 09:23:17AM +0100, Adam D. Barratt wrote: On 2019-10-14 01:21, Serge Rijkers wrote: exim4.template.conf contains: av_scanner = clamd: /var/run/clamav/clamd.ctl clean buster clamav-daemon uses /run/clamav/clamd.ctl For a on tech-savvy user this is difficult to diagnose possibly exim4.template.conf should contain: av_scanner = clamd:/run/clamav/clamd.ctl Debian Policy requires that /var/run be a symlink to /run, so that change should make no difference. I tested again with the symlink in place. It does make a difference. Also, the configuration option is commented in the default file, and there is not even a macro to enable it. So, who enables this already knows her way around things. Apparently, I am one of those who knows my way around things. Even so, this av_scanner = thing bit me. And yes, I figured it out quickly. This should, IMO, be fixed in unstable and testing (it's a no-brainer one-line change), but I don't think we should do this in stable. That seems fair enough. Regards, Serge Rijkers
Bug#942292: exact error message from exim4 in mainlog
below is the exact error in mainlog with /var/run symlink in in place 1iJnUT-0005ZN-Je malware acl condition: clamd /var/run/clamav/clamd.ctl : unable to connect to UNIX socket (/var/run/clamav/clamd.ctl): No such file or directory regards, Serge Rijkers
Bug#942292: exim4.template.conf for clean buster install av_scanner incorrect
On 14/10/2019 10:23, Adam D. Barratt wrote: Control: tags -1 + moreinfo On 2019-10-14 01:21, Serge Rijkers wrote: exim4.template.conf contains: av_scanner = clamd: /var/run/clamav/clamd.ctl clean buster clamav-daemon uses /run/clamav/clamd.ctl For a on tech-savvy user this is difficult to diagnose possibly exim4.template.conf should contain: av_scanner = clamd:/run/clamav/clamd.ctl Debian Policy requires that /var/run be a symlink to /run, so that change should make no difference. Regards, Adam I would like to point out that a clean buster install does not create the symlink, so the change would make a difference. I feel that a package should not depend on erratic behavior elsewhere in the system. Clamd-daemon uses /run not /var/run exim should reflect that change. Ultimately a new user installing buster runs into this problem. Whether this is fixed in exin, clamd or debian installer is metter for debate. should i report this elsewhere?
Bug#942292: exim4.template.conf for clean buster install av_scanner incorrect
On 14/10/2019 10:23, Adam D. Barratt wrote: Control: tags -1 + moreinfo On 2019-10-14 01:21, Serge Rijkers wrote: exim4.template.conf contains: av_scanner = clamd: /var/run/clamav/clamd.ctl clean buster clamav-daemon uses /run/clamav/clamd.ctl For a on tech-savvy user this is difficult to diagnose possibly exim4.template.conf should contain: av_scanner = clamd:/run/clamav/clamd.ctl Debian Policy requires that /var/run be a symlink to /run, so that change should make no difference. Regards, Adam I have also created the symlink to/run in /var and retested with av_scanner = /var/run/clamav/clamd.ctl wihich then fails again.
Bug#942292: exim4.template.conf for clean buster install av_scanner incorrect
Package: exim4 Version: 4.92-8+deb10u3 Severity: normal Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? A clean install of buster as an smtp mail server * What exactly did you do (or not do) that was effective (or ineffective)? exim4.template.conf contains: av_scanner = clamd: /var/run/clamav/clamd.ctl clean buster clamav-daemon uses /run/clamav/clamd.ctl For a on tech-savvy user this is difficult to diagnose possibly exim4.template.conf should contain: av_scanner = clamd:/run/clamav/clamd.ctl instead. * What was the outcome of this action? Changing this to the above made clamd scanning from exim4 operational is was not before. * What outcome did you expect instead? -- Package-specific info: Exim version 4.92 #3 built 27-Sep-2019 16:09:35 Copyright (c) University of Cambridge, 1995 - 2018 (c) The Exim Maintainers and contributors in ACKNOWLEDGMENTS file, 2007 - 2018 Berkeley DB: Berkeley DB 5.3.28: (September 9, 2013) Support for: crypteq iconv() IPv6 PAM Perl Expand_dlfunc GnuTLS move_frozen_messages Content_Scanning DANE DKIM DNSSEC Event OCSP PRDR PROXY SOCKS TCP_Fast_Open Lookups (built-in): lsearch wildlsearch nwildlsearch iplsearch cdb dbm dbmjz dbmnz dnsdb dsearch ldap ldapdn ldapm mysql nis nis0 passwd pgsql sqlite Authenticators: cram_md5 cyrus_sasl dovecot plaintext spa tls Routers: accept dnslookup ipliteral iplookup manualroute queryprogram redirect Transports: appendfile/maildir/mailstore/mbx autoreply lmtp pipe smtp Malware: f-protd f-prot6d drweb fsecure sophie clamd avast sock cmdline Fixed never_users: 0 Configure owner: 0:0 Size of off_t: 8 Configuration file search path is /etc/exim4/exim4.conf:/var/lib/exim4/config.autogenerated Configuration file is /var/lib/exim4/config.autogenerated # /etc/exim4/update-exim4.conf.conf # # Edit this file and /etc/mailname by hand and execute update-exim4.conf # yourself or use 'dpkg-reconfigure exim4-config' # # Please note that this is _not_ a dpkg-conffile and that automatic changes # to this file might happen. The code handling this will honor your local # changes, so this is usually fine, but will break local schemes that mess # around with multiple versions of the file. # # update-exim4.conf uses this file to determine variable values to generate # exim configuration macros for the configuration file. # # Most settings found in here do have corresponding questions in the # Debconf configuration, but not all of them. # # This is a Debian specific file dc_eximconfig_configtype='smarthost' dc_other_hostnames='tregare.net' dc_local_interfaces='192.168.0.110 ; 127.0.0.1 ; ::1' dc_readhost='tregare.net' dc_relay_domains='' dc_minimaldns='false' dc_relay_nets='192.168.0.0/24' dc_smarthost='smtp.ziggo.nl' CFILEMODE='644' dc_use_split_config='false' dc_hide_mailname='true' dc_mailname_in_oh='true' dc_localdelivery='maildir_home' mailname:tregare.net # /etc/default/exim4 EX4DEF_VERSION='' # 'combined' - one daemon running queue and listening on SMTP port # 'no' - no daemon running the queue # 'separate' - two separate daemons # 'ppp' - only run queue with /etc/ppp/ip-up.d/exim4. # 'nodaemon' - no daemon is started at all. # 'queueonly' - only a queue running daemon is started, no SMTP listener. # setting this to 'no' will also disable queueruns from /etc/ppp/ip-up.d/exim4 QUEUERUNNER='combined' # how often should we run the queue QUEUEINTERVAL='30m' # options common to quez-runner and listening daemon COMMONOPTIONS='' # more options for the daemon/process running the queue (applies to the one # started in /etc/ppp/ip-up.d/exim4, too. QUEUERUNNEROPTIONS='' # special flags given to exim directly after the -q. See exim(8) QFLAGS='' # Options for the SMTP listener daemon. By default, it is listening on # port 25 only. To listen on more ports, it is recommended to use # -oX 25:587:10025 -oP /run/exim4/exim.pid SMTPLISTENEROPTIONS='-oX 25:465:587 -oP /run/exim4/exim.pid' -- System Information: Debian Release: 10.1 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-6-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=C.UTF-8 (charmap=locale: Cannot set LC_ALL to default locale: No such file or directory UTF-8), LANGUAGE=en_US:en (charmap=locale: Cannot set LC_ALL to default locale: No such file or directory UTF-8) Shell: /bin/sh linked to /usr/bin/bash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages exim4 depends on: ii debconf [debconf-2.0] 1.5.71 ii exim4-base 4.92-8+deb10u3 ii exim4-daemon-heavy 4.92-8+deb10u3 exim4 recommends no packages. exim4 suggests no packages. -- debconf information: perl: warning: Setting locale failed. perl: warning: Please check that your locale settings: LANGUAGE = "en_US:en", LC_ALL = (unset), LC_MONETARY =
Bug#781103: libwacom-common: gnome control applet not detecting tablet
Package: libwacom-common Version: 0.8-1 Followup-For: Bug #781103 Dear Maintainer, using libwacom 8.1 on kernel 4.0.0-2-amd64 the gnome control panel applet no longer recognizes my Intuos 5 Pro tablet. I cannot use the applet. - xinput list shows all devices that the tablet has. xsetwacom works as expected. * What led up to the situation? I upgraded to a kernel later that 3.17 and the wacom gnome applet no longer recognises my intuos 5 pro. I am currently running 4.0.0-2-am64 kernel. * What exactly did you do (or not do) that was effective (or ineffective)? Action 1) reverting too old kernel 3.16 kernel Action 22) I downloaded the libwacom 0.15 tar ball from sourceforge. Compiled and installed it in /usr/local/lib. I have renamed /usr/lib/x86_64-linux-gnu/libwacom.so.2.1.0 and symlinked to 2.4.2 version in /usr/local/lib * What was the outcome of this action? 1) On 3.16 kernel applet works. 2) On 4.0.0-2 kernel with libwacom 0.15 gnome applet works Clearly my hack is far from elegant and when libwacom updates I will need to remove my /usr/local/lib version. -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.0.0-2-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Init: systemd (via /run/systemd/system) -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#753132: libnfs4: cannot access nfsmount using xbmc from debian
Package: libnfs4 Version: 1.9.3-3 Severity: important Dear Maintainer, I am reporting the exact same issue as bug number 749123. The proposed fix using libnfs 1.9.3-3 does not solve the issue. Bug 749123 has been archived so could not be reopened. I am adding a relevant section from xbmc.log % -- snip --% 14:35:31 T:140626280572672 DEBUG: Loading: libnfs.so.4 14:35:31 T:140626280572672 DEBUG: NFS: Context for not open - get anew context. 14:35:31 T:140626280572672 ERROR: NFS: Failed to mount nfs share:(nfs_mount_async failed) 14:35:32 T:140627785025856 DEBUG: -- Window Init (DialogBusy.xml)-- 14:35:34 T:140627785025856 DEBUG: -- Window Deinit (DialogBusy.xml) -- 14:35:39 T:140627785025856 DEBUG: ProcessMouse: trying mouse actionleftclick 14:35:42 T:140627785025856 DEBUG: ProcessMouse: trying mouse actionleftclick 14:35:42 T:140626280572672 DEBUG: NFS: Context for 172.16.50.142/home/rss/dvd not open - get a new context. 14:35:42 T:140626280572672 DEBUG: NFS: Connected to server 172.16.50.142 and export /home/rss/dvd 14:35:42 T:140626280572672 DEBUG: NFS: chunks: r/w 65536/65536 14:35:42 T:140626280572672 ERROR: Failed to open(//) nfs_opendir_async failed 14:35:42 T:140627785025856 ERROR: GetDirectory - Error getting nfs://172.16.50.142/home/rss/dvd/ 14:35:42 T:140627785025856 ERROR: CGUIDialogFileBrowser::GetDirectory(nfs://172.16.50.142/home/rss/dvd/) failed %-- end snip --% Mounting the shares locally as the user works using fstab. The following is in my fstab: %-- snip --% 172.16.50.142:/home/rss/dvd /home/rss/mnt/video_kb nfs tcp,rsize=32768,wsize=8192,intr,noatime,user,noauto,rw 0 0 %-- end snip --% -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.14-8.dmz.1-liquorix-amd64 (SMP w/8 CPU cores; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages libnfs4 depends on: ii libc6 2.19-4 ii multiarch-support 2.19-4 libnfs4 recommends no packages. libnfs4 suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#753132: Acknowledgement (libnfs4: cannot access nfsmount using xbmc from debian)
Dear maintainer It seems like Archlinux users have had the same problem. I am adding a link to their bugreport https://bugs.archlinux.org/task/40867 It looks like upstream is not reacting maybe their discussion and patch help regards Serge Rijkers -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#753132: libnfs and xbmc
Dear Maintainer, libnfs is definitely the culprit here using apt-src and the information I gathered from archlinux bug thread, I patched libnfs.c. I now have xbmc working as expected. Upstream master actually contains this fix. Upstream maintainer has stated the he plans a release in the next few days. see https://github.com/sahlberg/libnfs/issues/78 As you can see from that was 2 weeks ago. Which does not fit my definition of a few days. I hope this helps. Regards Serge Rijkers -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#753132: libnfs4: cannot access nfsmount using xbmc from debian
Dear Ronnie and Ritesh, I hope Ritesh has the 1.9.4 release of libnfs in the debian archive soon. In the meantime I have checked the libnfs.c on github tag release 1.9.4. It contains the local modification I used to get libnfs and xbmc to play together. I expect that the new release will fix the issue permanently. FYI i already use insecure in my exports file, so I do not expect any issues in that regard. Thank you both for your efforts, Regards Serge Rijkers On 06/30/2014 12:19 AM, ronnie sahlberg wrote: Please try libnfs version 1.9.4 which has just been released. If this version also fails, can you check that you have set the export to insecure in /etc/exports for the shares on the server? Also, can you collect a network trace with wireshark showing the failure? regards ronnie sahlberg On Sun, Jun 29, 2014 at 12:10 PM, Ritesh Raj Sarraf r...@researchut.com wrote: Hello Serge, Thank you for following on this bug report. I'm CCing upstream to seek their opinion. Thanks, Ritesh On 06/29/2014 07:07 PM, Serge Rijkers wrote: Dear Maintainer, I am reporting the exact same issue as bug number 749123. The proposed fix using libnfs 1.9.3-3 does not solve the issue. Bug 749123 has been archived so could not be reopened. I am adding a relevant section from xbmc.log % -- snip --% 14:35:31 T:140626280572672 DEBUG: Loading: libnfs.so.4 14:35:31 T:140626280572672 DEBUG: NFS: Context for not open - get anew context. 14:35:31 T:140626280572672 ERROR: NFS: Failed to mount nfs share:(nfs_mount_async failed) 14:35:32 T:140627785025856 DEBUG: -- Window Init (DialogBusy.xml)-- 14:35:34 T:140627785025856 DEBUG: -- Window Deinit (DialogBusy.xml) -- 14:35:39 T:140627785025856 DEBUG: ProcessMouse: trying mouse actionleftclick 14:35:42 T:140627785025856 DEBUG: ProcessMouse: trying mouse actionleftclick 14:35:42 T:140626280572672 DEBUG: NFS: Context for 172.16.50.142/home/rss/dvd not open - get a new context. 14:35:42 T:140626280572672 DEBUG: NFS: Connected to server 172.16.50.142 and export /home/rss/dvd 14:35:42 T:140626280572672 DEBUG: NFS: chunks: r/w 65536/65536 14:35:42 T:140626280572672 ERROR: Failed to open(//) nfs_opendir_async failed 14:35:42 T:140627785025856 ERROR: GetDirectory - Error getting nfs://172.16.50.142/home/rss/dvd/ 14:35:42 T:140627785025856 ERROR: CGUIDialogFileBrowser::GetDirectory(nfs://172.16.50.142/home/rss/dvd/) failed %-- end snip --% Mounting the shares locally as the user works using fstab. The following is in my fstab: %-- snip --% 172.16.50.142:/home/rss/dvd /home/rss/mnt/video_kb nfs tcp,rsize=32768,wsize=8192,intr,noatime,user,noauto,rw 0 0 %-- end snip --% -- Ritesh Raj Sarraf RESEARCHUT - http://www.researchut.com Necessity is the mother of invention. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#747366: Extra Information on loading nvidia-uvm
Dear Maintainer, Browsing on the net gave me the following tip load the module with force-modversion I tried modprobe --force-modversion nvidia-uvm which allows the module to load. opencl accelleration using cuda now works again. As a workaround this seeems somewhat brute force. I hope this information helps -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#747366: nvidia-driver: nvidia-uvm module is present but fails on load
Source: nvidia-driver Version: 331.67-2 Severity: important Dear Maintainer, Some of the applications that I use are opencl enabled. I find that since installing 331.67-2 version of the driver opencl no longer works This is due a load failure nvidia-uvm kernel module. The module is present in my kernel. folliwing is output of modinfo nvidia-uwn % -- snip root@rissa:~# modinfo nvidia-uvm filename: /lib/modules/3.14-2.dmz.1-liquorix-amd64/updates/dkms/nvidia-uvm.ko supported: external license:MIT depends: vermagic: 3.14-2.dmz.1-liquorix-amd64 SMP preempt mod_unload modversions % - end snip following is output of modprobe -v nvida-uvm %-- snip root@rissa:~# modprobe -v nvidia-uvm insmod /lib/modules/3.14-2.dmz.1-liquorix-amd64/updates/dkms/nvidia-current.ko insmod /lib/modules/3.14-2.dmz.1-liquorix-amd64/updates/dkms/nvidia-uvm.ko modprobe: ERROR: could not insert 'nvidia_uvm': Invalid argument % end snip The previous version of the package 331.67-1 failed build the nvidia-uvm module. reverting to 331.49-1 version of nvidia drivers manually restored functionality. reverting to 331.49-1 no longer works. The dkms build of kernel module for 331.49-1 fails. -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.14-2.dmz.1-liquorix-amd64 (SMP w/8 CPU cores; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#747366: additional info dmesg output of nvidia-uvm on kernel boot
Dear Maintainer attached dmesg output of nvidia_uvm module on kernel boot % --- snip rss@rissa:~$ dmesg | grep nvidia_uvm nvidia_uvm: no symbol version for nvUvmInterfaceChannelDestroy nvidia_uvm: Unknown symbol nvUvmInterfaceChannelDestroy (err -22) nvidia_uvm: no symbol version for nvUvmInterfaceQueryCaps nvidia_uvm: Unknown symbol nvUvmInterfaceQueryCaps (err -22) nvidia_uvm: no symbol version for nvUvmInterfaceMemoryAllocSys nvidia_uvm: Unknown symbol nvUvmInterfaceMemoryAllocSys (err -22) nvidia_uvm: no symbol version for nvUvmInterfaceMemoryCpuMap nvidia_uvm: Unknown symbol nvUvmInterfaceMemoryCpuMap (err -22) nvidia_uvm: no symbol version for nvUvmInterfaceKillChannel nvidia_uvm: Unknown symbol nvUvmInterfaceKillChannel (err -22) nvidia_uvm: no symbol version for nvUvmInterfaceAddressSpaceCreateMirrored nvidia_uvm: Unknown symbol nvUvmInterfaceAddressSpaceCreateMirrored (err -22) nvidia_uvm: no symbol version for nvUvmInterfaceServiceDeviceInterruptsRM nvidia_uvm: Unknown symbol nvUvmInterfaceServiceDeviceInterruptsRM (err -22) nvidia_uvm: no symbol version for nvUvmInterfaceDeRegisterUvmOps nvidia_uvm: Unknown symbol nvUvmInterfaceDeRegisterUvmOps (err -22) nvidia_uvm: no symbol version for nvUvmInterfaceGetUvmPrivRegion nvidia_uvm: Unknown symbol nvUvmInterfaceGetUvmPrivRegion (err -22) nvidia_uvm: no symbol version for nvUvmInterfaceGetAttachedUuids nvidia_uvm: Unknown symbol nvUvmInterfaceGetAttachedUuids (err -22) nvidia_uvm: no symbol version for nvUvmInterfaceSessionDestroy nvidia_uvm: Unknown symbol nvUvmInterfaceSessionDestroy (err -22) nvidia_uvm: no symbol version for nvUvmInterfaceCheckEccErrorSlowpath nvidia_uvm: Unknown symbol nvUvmInterfaceCheckEccErrorSlowpath (err -22) nvidia_uvm: no symbol version for nvUvmInterfaceCopyEngineAllocate nvidia_uvm: Unknown symbol nvUvmInterfaceCopyEngineAllocate (err -22) nvidia_uvm: no symbol version for nvUvmInterfaceAddressSpaceDestroy nvidia_uvm: Unknown symbol nvUvmInterfaceAddressSpaceDestroy (err -22) nvidia_uvm: no symbol version for nvUvmInterfaceRegisterUvmCallbacks nvidia_uvm: Unknown symbol nvUvmInterfaceRegisterUvmCallbacks (err -22) nvidia_uvm: no symbol version for nvUvmInterfaceGetGpuArch nvidia_uvm: Unknown symbol nvUvmInterfaceGetGpuArch (err -22) nvidia_uvm: no symbol version for nvUvmInterfaceChannelAllocate nvidia_uvm: Unknown symbol nvUvmInterfaceChannelAllocate (err -22) nvidia_uvm: no symbol version for nvUvmInterfaceSessionCreate nvidia_uvm: Unknown symbol nvUvmInterfaceSessionCreate (err -22) nvidia_uvm: no symbol version for nvUvmInterfaceChannelDestroy nvidia_uvm: Unknown symbol nvUvmInterfaceChannelDestroy (err -22) nvidia_uvm: no symbol version for nvUvmInterfaceQueryCaps nvidia_uvm: Unknown symbol nvUvmInterfaceQueryCaps (err -22) nvidia_uvm: no symbol version for nvUvmInterfaceMemoryAllocSys nvidia_uvm: Unknown symbol nvUvmInterfaceMemoryAllocSys (err -22) nvidia_uvm: no symbol version for nvUvmInterfaceMemoryCpuMap nvidia_uvm: Unknown symbol nvUvmInterfaceMemoryCpuMap (err -22) nvidia_uvm: no symbol version for nvUvmInterfaceKillChannel nvidia_uvm: Unknown symbol nvUvmInterfaceKillChannel (err -22) nvidia_uvm: no symbol version for nvUvmInterfaceAddressSpaceCreateMirrored nvidia_uvm: Unknown symbol nvUvmInterfaceAddressSpaceCreateMirrored (err -22) nvidia_uvm: no symbol version for nvUvmInterfaceServiceDeviceInterruptsRM nvidia_uvm: Unknown symbol nvUvmInterfaceServiceDeviceInterruptsRM (err -22) nvidia_uvm: no symbol version for nvUvmInterfaceDeRegisterUvmOps nvidia_uvm: Unknown symbol nvUvmInterfaceDeRegisterUvmOps (err -22) nvidia_uvm: no symbol version for nvUvmInterfaceGetUvmPrivRegion nvidia_uvm: Unknown symbol nvUvmInterfaceGetUvmPrivRegion (err -22) nvidia_uvm: no symbol version for nvUvmInterfaceGetAttachedUuids nvidia_uvm: Unknown symbol nvUvmInterfaceGetAttachedUuids (err -22) nvidia_uvm: no symbol version for nvUvmInterfaceSessionDestroy nvidia_uvm: Unknown symbol nvUvmInterfaceSessionDestroy (err -22) nvidia_uvm: no symbol version for nvUvmInterfaceCheckEccErrorSlowpath nvidia_uvm: Unknown symbol nvUvmInterfaceCheckEccErrorSlowpath (err -22) nvidia_uvm: no symbol version for nvUvmInterfaceCopyEngineAllocate nvidia_uvm: Unknown symbol nvUvmInterfaceCopyEngineAllocate (err -22) nvidia_uvm: no symbol version for nvUvmInterfaceAddressSpaceDestroy nvidia_uvm: Unknown symbol nvUvmInterfaceAddressSpaceDestroy (err -22) nvidia_uvm: no symbol version for nvUvmInterfaceRegisterUvmCallbacks nvidia_uvm: Unknown symbol nvUvmInterfaceRegisterUvmCallbacks (err -22) nvidia_uvm: no symbol version for nvUvmInterfaceGetGpuArch nvidia_uvm: Unknown symbol nvUvmInterfaceGetGpuArch (err -22) nvidia_uvm: no symbol version for nvUvmInterfaceChannelAllocate nvidia_uvm: Unknown symbol nvUvmInterfaceChannelAllocate (err -22) nvidia_uvm: no symbol version for nvUvmInterfaceSessionCreate nvidia_uvm: Unknown symbol nvUvmInterfaceSessionCreate (err -22) nvidia_uvm: no symbol version for nvUvmInterfaceChannelDestroy nvidia_uvm:
Bug#613573: What makes me think is xorg
Downgrading solves the problem. It seems to be kde specific. i.e. gnome apps work. However, an error in a kde app should never segfault the x server -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#613573:
I do not have a log. X segfault and restarts nothing in the log. reverting to older xserver which als downgrades mesa, radeon, and a hole bunch of other stuff i.e. dongrade with dependancies resolved in not trivial. regards rss -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#613573: sid xserver-xorg 1:7.6+3 + radeon + konversatin segfault X
On Tue, 2011-02-15 at 20:09 +0100, Julien Cristau wrote: On Tue, Feb 15, 2011 at 19:38:19 +0100, Serge Rijkers wrote: Package: xorg Version: 1:7.6+3 Severity: normal currently running on liquorix kernel bu it also happens on stock kernel from sid. many kde based apps crash on opening or when a dialog is opened. konversatino segfaults X on launch. k3b segfaults x when you try to select an image to burn. Oh, and please include some log from the crash. Cheers, Julien Thats the point xserver xfaults black console screen and login prompt from gdm no log nothing. just gone -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#613573: Log: how do you want to add a log add one as attachment to an email or paste.
I will need to force an error and save the log. So it will take some time :) rss -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#613573: Log
I will force an error and paste Which logs do you want? Xorg.1.log i would guess. Do you need anything else? regards rss -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#508302: bug #508302
adding cat /proc/mtd and ls /boot % start --% inconnu:~# cat /proc/mtd dev:size erasesize name mtd0: 0004 0002 RedBoot mtd1: 0002 0002 SysConf mtd2: 0002 0002 Loader mtd3: 0014 0002 Kernel mtd4: 0062 0002 Ramdisk mtd5: 0002 0002 FIS directory inconnu:~# ls /boot System.map-2.6.18-6-ixp4xx initrd.img-2.6.18-6-ixp4xx.bak System.map-2.6.26-1-ixp4xx initrd.img-2.6.26-1-ixp4xx apex.flash initrd.img.old config-2.6.18-6-ixp4xx vmlinuz config-2.6.26-1-ixp4xx vmlinuz-2.6.18-6-ixp4xx initrd.img vmlinuz-2.6.26-1-ixp4xx initrd.img-2.6.18-6-ixp4xx vmlinuz.old inconnu:~# % end --% -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#508302: bug #508302
Oops, forget -l switch on ls % start % inconnu:~# ls -l /boot total 11452 -rw-r--r-- 1 root root 636580 Oct 16 19:32 System.map-2.6.18-6-ixp4xx -rw-r--r-- 1 root root 787178 Nov 28 13:55 System.map-2.6.26-1-ixp4xx -rw-r--r-- 1 root root 42892 May 21 2008 apex.flash -rw-r--r-- 1 root root 46325 Oct 15 11:28 config-2.6.18-6-ixp4xx -rw-r--r-- 1 root root 61634 Nov 26 19:17 config-2.6.26-1-ixp4xx lrwxrwxrwx 1 root root 26 Dec 9 19:40 initrd.img - initrd.img-2.6.26-1-ixp4xx -rw-r--r-- 1 root root 2104347 Dec 1 17:37 initrd.img-2.6.18-6-ixp4xx -rw-r--r-- 1 root root 3255463 Nov 30 23:34 initrd.img-2.6.18-6-ixp4xx.bak -rw-r--r-- 1 root root 2127708 Dec 9 21:04 initrd.img-2.6.26-1-ixp4xx lrwxrwxrwx 1 root root 26 Feb 27 2008 initrd.img.old - initrd.img-2.6.18-6-ixp4xx lrwxrwxrwx 1 root root 23 Dec 9 19:40 vmlinuz - vmlinuz-2.6.26-1-ixp4xx -rw-r--r-- 1 root root 1186748 Oct 16 19:32 vmlinuz-2.6.18-6-ixp4xx -rw-r--r-- 1 root root 1422160 Nov 28 13:55 vmlinuz-2.6.26-1-ixp4xx lrwxrwxrwx 1 root root 23 Feb 27 2008 vmlinuz.old - vmlinuz-2.6.18-6-ixp4xx inconnu:~# % start % -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#508302: Info received (bug #508302)
Martin, I have no idea which image I used. The only thing that I can say is that I used an image from your unofficial pages at the time. my lost and found on my root device /dev/sda1 in an ext3 partition created on 22 dec 2006. So that is the date that my NSLU2 was installed using an image from your website. At the time that was not a debian official installer but an image that you could install to run debian. Maybe that is what is biting me now. I will try your suggestion with upslug2. and the image you suggest. Do I let you and the bug report know what the result was? Regards Serge Rijkers -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#508302: Suggested image
Dear Michael, I have just reflashed as per you suggestion. Yes, the link you offered worked! I now have a 2.6.26 kernel running on my NSLU2. That means in effect that the base installer image I ran at the time had a too small root partition for a modern kernel. Thank you for supplying me with a running image that works. I guess the bug can be closed now. If there are any steps that I can take to assist in narrowing the users with this problem and therby aking your excellent suggestion available to them please let me know! Thank you! Regards Serge Rijkers -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#366865: evolution start loads processor at 100%
Package: evolution Version: 2.6.1-2 Severity: normal starting evolution loads processor to 100% with dbus error messages. this make the system unresponsive. I am unsure whether this is caused by a plugin. I am using the exchange connection and 2 imap connections. The system functions barely. Sluggish behavior. When exection of Evolution is halted(^Z) the system is becomes responsive. Evolution shutdown can lasts up to 3+ minutes. The system is barly usable to unusable in the meantime. In a continous loop the following error message appears: libnm_glib_dbus_init: error, org.freedesktop.DBus.Error.NoReply raised: No reply within specified time I have tried to report this as grave but the rportbug has classified this as normal. Email functionality using evolution is unusable. My alternatives are by preference: - for imap mutt - for exchange webmail. This is im my view normal use of Evolution. This bug/glitch makes Evolution as a software package irrelevant (not worthy of consideratino for use.) I have seen a previous report that is simalar and the bug has been declared solved. I am willing to assist in resolution. i.e. will help in testing or trial and error resolution. Any information that I can supply, up to and including creating a build envirnment to test patches that are sent, I am willing to implement, -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.15 Locale: LANG=C, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Versions of packages evolution depends on: ii dbus 0.61-5 simple interprocess messaging syst ii evolution-dat 1.6.1-2evolution database backend server ii gconf22.14.0-1 GNOME configuration database syste ii gnome-icon-th 2.14.2-1 GNOME Desktop icon theme ii gtkhtml3.83.10.1-1 HTML rendering/editing library - b ii libart-2.0-2 2.3.17-1 Library of functions for 2D graphi ii libatk1.0-0 1.11.4-2 The ATK accessibility toolkit ii libaudiofile0 0.2.6-6Open-source version of SGI's audio ii libavahi-clie 0.6.9-8+b1 Avahi client library ii libavahi-comm 0.6.9-8+b1 Avahi common library ii libavahi-glib 0.6.9-8+b1 Avahi glib integration library ii libbonobo2-0 2.14.0-1 Bonobo CORBA interfaces library ii libbonoboui2- 2.14.0-2 The Bonobo UI library ii libc6 2.3.6-7GNU C Library: Shared libraries ii libcairo2 1.0.4-2The Cairo 2D vector graphics libra ii libcamel1.2-8 1.6.1-2The Evolution MIME message handlin ii libcomerr21.38+1.39-WIP-2006.04.09-1 common error description library ii libdbus-1-2 0.61-5 simple interprocess messaging syst ii libdbus-glib- 0.61-5 simple interprocess messaging syst ii libebook1.2-5 1.6.1-2Client library for evolution addre ii libecal1.2-3 1.6.1-2Client library for evolution calen ii libedataserve 1.6.1-2Utility library for evolution data ii libedataserve 1.6.1-2GUI utility library for evolution ii libesd-alsa0 0.2.36-3 Enlightened Sound Daemon (ALSA) - ii libfontconfig 2.3.2-5.1 generic font configuration library ii libfreetype6 2.1.10-3 FreeType 2 font engine, shared lib ii libgail-commo 1.8.11-2 GNOME Accessibility Implementation ii libgail17 1.8.11-2 GNOME Accessibility Implementation ii libgconf2-4 2.14.0-1 GNOME configuration database syste ii libgcrypt11 1.2.2-1LGPL Crypto library - runtime libr ii libglade2-0 1:2.5.1-2 library to load .glade files at ru ii libglib2.0-0 2.10.2-2 The GLib library of C routines ii libgnome-keyr 0.4.9-1GNOME keyring services library ii libgnome-pilo 2.0.12-1.6 Support libraries for gnome-pilot ii libgnome2-0 2.14.1-1 The GNOME 2 library - runtime file ii libgnomecanva 2.14.0-2 A powerful object-oriented display ii libgnomeprint 2.12.1-3 The GNOME 2.2 print architecture - ii libgnomeprint 2.12.1-3 GNOME 2.2 print architecture User ii libgnomeui-0 2.14.1-1 The GNOME 2 libraries (User Interf ii libgnomevfs2- 2.14.1-1 GNOME virtual file-system (runtime ii libgnutls13 1.3.5-1+b1 the GNU TLS library - runtime libr ii libgpg-error0 1.2-1 library for common error values an ii libgtk2.0-0 2.8.17-2 The GTK+ graphical user
Bug#366865: [EMAIL PROTECTED]
Dear Maintainer, I am willing to assist in tracking down and squashing this problem. FYI I am running a debian sid on a HP nw8240 notebook/desktop replacement system. Any assitance I can provide short of debugging c/c++ code I am willing to supply. This means if I recieve instructions to try thing I will try to comply. What I will not do is step through code line by line. Regards Serge Rijkers -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
