Recherche avancée

Sur d’autres sites (6221)

• Why X.Org's X Server has stopped working on Google Colab ?

  20 février 2021, par Rahul

  I am Using X server for the virtual screen on Google Colab and capturing that screen with ffmpeg to record it and live stream it to twitch. (for the reinforcement learning project)

  


  


  The above process was completely working till my last use of my Colab notebook (on mid-January 2021), but now (on 19th February 2021) I am using the same notebook and the streaming code has stopped working.

  


  


  I am adding config and log file data below. (I have never seen these files before because it was working, now it's not so I don't have any idea what wrong)

  


  The config file stored at /etc/X11/xorg.conf have the following data :

  


  # nvidia-xconfig: X configuration file generated by nvidia-xconfig
# nvidia-xconfig:  version 418.67

Section "ServerLayout"
    Identifier     "Layout0"
    Screen      0  "Screen0"
    InputDevice    "Keyboard0" "CoreKeyboard"
    InputDevice    "Mouse0" "CorePointer"
EndSection

Section "Files"
EndSection

Section "InputDevice"
    # generated from default
    Identifier     "Mouse0"
    Driver         "mouse"
    Option         "Protocol" "auto"
    Option         "Device" "/dev/mouse"
    Option         "Emulate3Buttons" "no"
    Option         "ZAxisMapping" "4 5"
EndSection

Section "InputDevice"
    # generated from default
    Identifier     "Keyboard0"
    Driver         "kbd"
EndSection

Section "Monitor"
    Identifier     "Monitor0"
    VendorName     "Unknown"
    ModelName      "Unknown"
    HorizSync       28.0 - 33.0
    VertRefresh     43.0 - 72.0
    Option         "DPMS"
EndSection

Section "Device"
    Identifier     "Device0"
    Driver         "nvidia"
    VendorName     "NVIDIA Corporation"
    BoardName      "Tesla T4"
    BusID          "PCI:0:4:0"
    MatchSeat      "seat-1"
EndSection

Section "Screen"
    Identifier     "Screen0"
    Device         "Device0"
    Monitor        "Monitor0"
    DefaultDepth    24
    Option         "AllowEmptyInitialConfiguration" "True"
    SubSection     "Display"
        Virtual     1920 1080
        Depth       24
    EndSubSection
EndSection


  


  The log file stored at /var/log/Xorg.0.log have the following data :

  


  [   464.605] 
X.Org X Server 1.19.6
Release Date: 2017-12-20
[   464.605] X Protocol Version 11, Revision 0
[   464.605] Build Operating System: Linux 4.15.0-124-generic x86_64 Ubuntu
[   464.605] Current Operating System: Linux 9d3fe3949671 4.19.112+ #1 SMP Thu Jul 23 08:00:38 PDT 2020 x86_64
[   464.605] Kernel command line: BOOT_IMAGE=/syslinux/vmlinuz.A init=/usr/lib/systemd/systemd boot=local rootwait ro noresume noswap loglevel=7 noinitrd console=ttyS0 security=apparmor virtio_net.napi_tx=1 systemd.unified_cgroup_hierarchy=false systemd.legacy_systemd_cgroup_controller=false csm.disabled=1 dm_verity.error_behavior=3 dm_verity.max_bios=-1 dm_verity.dev_wait=1 i915.modeset=1 cros_efi loadpin.enabled=0 root=/dev/dm-0 "dm=1 vroot none ro 1,0 4077568 verity payload=PARTUUID=555BDB75-CBD7-CD4A-B24E-29B13D7AC0DF hashtree=PARTUUID=555BDB75-CBD7-CD4A-B24E-29B13D7AC0DF hashstart=4077568 alg=sha256 root_hexdigest=42104d547ac104fb7061529e78f53e4f3e8c3d3cbb040dc6e0f84aad68491347 salt=9dc7f3acc4e2ce65be16356e960c2b21b51a917fa31d2e891fd295490c991e41" mitigations=off
[   464.605] Build Date: 30 November 2020  08:01:56PM
[   464.605] xorg-server 2:1.19.6-1ubuntu4.8 (For technical support please see http://www.ubuntu.com/support) 
[   464.605] Current version of pixman: 0.34.0
[   464.605]    Before reporting problems, check http://wiki.x.org
    to make sure that you have the latest version.
[   464.605] Markers: (--) probed, (**) from config file, (==) default setting,
    (++) from command line, (!!) notice, (II) informational,
    (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[   464.605] (==) Log file: "/var/log/Xorg.0.log", Time: Sat Feb 20 03:10:44 2021
[   464.606] (==) Using config file: "/etc/X11/xorg.conf"
[   464.606] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[   464.607] (==) ServerLayout "Layout0"
[   464.607] (**) |-->Screen "Screen0" (0)
[   464.607] (**) |   |-->Monitor "Monitor0"
[   464.607] (**) |   |-->Device "Device0"
[   464.607] (**) |-->Input Device "Keyboard0"
[   464.607] (**) |-->Input Device "Mouse0"
[   464.607] (==) Automatically adding devices
[   464.607] (==) Automatically enabling devices
[   464.607] (==) Automatically adding GPU devices
[   464.607] (==) Automatically binding GPU devices
[   464.607] (==) Max clients allowed: 256, resource mask: 0x1fffff
[   464.607] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
[   464.607]    Entry deleted from font path.
[   464.607] (WW) The directory "/usr/share/fonts/X11/100dpi/" does not exist.
[   464.607]    Entry deleted from font path.
[   464.607] (WW) The directory "/usr/share/fonts/X11/75dpi/" does not exist.
[   464.607]    Entry deleted from font path.
[   464.607] (WW) The directory "/usr/share/fonts/X11/Type1" does not exist.
[   464.607]    Entry deleted from font path.
[   464.607] (WW) The directory "/usr/share/fonts/X11/100dpi" does not exist.
[   464.607]    Entry deleted from font path.
[   464.607] (WW) The directory "/usr/share/fonts/X11/75dpi" does not exist.
[   464.607]    Entry deleted from font path.
[   464.607] (==) FontPath set to:
    /usr/share/fonts/X11/misc,
    built-ins
[   464.607] (==) ModulePath set to "/usr/lib/xorg/modules"
[   464.607] (WW) Hotplugging is on, devices using drivers 'kbd', 'mouse' or 'vmmouse' will be disabled.
[   464.607] (WW) Disabling Keyboard0
[   464.607] (WW) Disabling Mouse0
[   464.607] (II) Loader magic: 0x556eb77b8020
[   464.607] (II) Module ABI versions:
[   464.607]    X.Org ANSI C Emulation: 0.4
[   464.607]    X.Org Video Driver: 23.0
[   464.607]    X.Org XInput driver : 24.1
[   464.607]    X.Org Server Extension : 10.0
[   464.607] (EE) dbus-core: error connecting to system bus: org.freedesktop.DBus.Error.FileNotFound (Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory)
[   464.609] (--) PCI: (0:0:4:0) 10de:1eb8:10de:12a2 rev 161, Mem @ 0xc0000000/16777216, 0x380000000/268435456, 0x390000000/33554432
[   464.609] (II) no primary bus or device found
[   464.609] (II) LoadModule: "glx"
[   464.609] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[   464.610] (II) Module glx: vendor="X.Org Foundation"
[   464.610]    compiled for 1.19.6, module version = 1.0.0
[   464.610]    ABI class: X.Org Server Extension, version 10.0
[   464.610] (II) LoadModule: "nvidia"
[   464.610] (II) Loading /usr/lib/xorg/modules/drivers/nvidia_drv.so
[   464.610] (II) Module nvidia: vendor="NVIDIA Corporation"
[   464.610]    compiled for 4.0.2, module version = 1.0.0
[   464.610]    Module class: X.Org Video Driver
[   464.610] (II) NVIDIA dlloader X Driver  418.67  Sat Apr  6 02:51:17 CDT 2019
[   464.610] (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
[   464.610] xf86EnableIOPorts: failed to set IOPL for I/O (Operation not permitted)
[   464.610] (II) Loading sub module "fb"
[   464.610] (II) LoadModule: "fb"
[   464.611] (II) Loading /usr/lib/xorg/modules/libfb.so
[   464.611] (II) Module fb: vendor="X.Org Foundation"
[   464.611]    compiled for 1.19.6, module version = 1.0.0
[   464.611]    ABI class: X.Org ANSI C Emulation, version 0.4
[   464.611] (II) Loading sub module "wfb"
[   464.611] (II) LoadModule: "wfb"
[   464.611] (II) Loading /usr/lib/xorg/modules/libwfb.so
[   464.611] (II) Module wfb: vendor="X.Org Foundation"
[   464.611]    compiled for 1.19.6, module version = 1.0.0
[   464.611]    ABI class: X.Org ANSI C Emulation, version 0.4
[   464.611] (II) Loading sub module "ramdac"
[   464.611] (II) LoadModule: "ramdac"
[   464.611] (II) Module "ramdac" already built-in
[   464.637] (EE) NVIDIA: Failed to initialize the NVIDIA kernel module. Please see the
[   464.637] (EE) NVIDIA:     system's kernel log for additional error messages and
[   464.637] (EE) NVIDIA:     consult the NVIDIA README for details.
[   464.662] (EE) NVIDIA: Failed to initialize the NVIDIA kernel module. Please see the
[   464.662] (EE) NVIDIA:     system's kernel log for additional error messages and
[   464.662] (EE) NVIDIA:     consult the NVIDIA README for details.
[   464.662] (EE) No devices detected.
[   464.662] (==) Matched modesetting as autoconfigured driver 0
[   464.662] (==) Matched fbdev as autoconfigured driver 1
[   464.662] (==) Matched vesa as autoconfigured driver 2
[   464.662] (==) Assigned the driver to the xf86ConfigLayout
[   464.662] (II) LoadModule: "modesetting"
[   464.662] (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so
[   464.663] (II) Module modesetting: vendor="X.Org Foundation"
[   464.663]    compiled for 1.19.6, module version = 1.19.6
[   464.663]    Module class: X.Org Video Driver
[   464.663]    ABI class: X.Org Video Driver, version 23.0
[   464.663] (II) LoadModule: "fbdev"
[   464.663] (II) Loading /usr/lib/xorg/modules/drivers/fbdev_drv.so
[   464.663] (II) Module fbdev: vendor="X.Org Foundation"
[   464.663]    compiled for 1.19.3, module version = 0.4.4
[   464.663]    Module class: X.Org Video Driver
[   464.663]    ABI class: X.Org Video Driver, version 23.0
[   464.663] (II) LoadModule: "vesa"
[   464.663] (II) Loading /usr/lib/xorg/modules/drivers/vesa_drv.so
[   464.663] (II) Module vesa: vendor="X.Org Foundation"
[   464.663]    compiled for 1.19.3, module version = 2.3.4
[   464.663]    Module class: X.Org Video Driver
[   464.663]    ABI class: X.Org Video Driver, version 23.0
[   464.663] (II) NVIDIA dlloader X Driver  418.67  Sat Apr  6 02:51:17 CDT 2019
[   464.663] (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
[   464.663] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
[   464.663] (II) FBDEV: driver for framebuffer: fbdev
[   464.663] (II) VESA: driver for VESA chipsets: vesa
[   464.663] xf86EnableIOPorts: failed to set IOPL for I/O (Operation not permitted)
[   464.663] (EE) open /dev/dri/card0: No such file or directory
[   464.663] (WW) Falling back to old probe method for modesetting
[   464.663] (EE) open /dev/dri/card0: No such file or directory
[   464.663] (WW) Falling back to old probe method for fbdev
[   464.663] (II) Loading sub module "fbdevhw"
[   464.663] (II) LoadModule: "fbdevhw"
[   464.663] (II) Loading /usr/lib/xorg/modules/libfbdevhw.so
[   464.663] (II) Module fbdevhw: vendor="X.Org Foundation"
[   464.663]    compiled for 1.19.6, module version = 0.0.2
[   464.663]    ABI class: X.Org Video Driver, version 23.0
[   464.664] (EE) open /dev/fb0: No such file or directory
[   464.664] (WW) Falling back to old probe method for vesa
[   464.664] (WW) VGA arbiter: cannot open kernel arbiter, no multi-card support
[   464.664] (EE) Screen 0 deleted because of no matching config section.
[   464.664] (II) UnloadModule: "modesetting"
[   464.664] (EE) Device(s) detected, but none match those in the config file.
[   464.664] (EE) 
Fatal server error:
[   464.664] (EE) no screens found(EE) 
[   464.664] (EE) 
Please consult the The X.Org Foundation support 
     at http://wiki.x.org
 for help. 
[   464.664] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
[   464.664] (EE) 
[   464.664] (EE) Server terminated with error (1). Closing log file.



  


  I am using this github repo to setup the video-streamer

  


  If anyone wants the colab notebook for the example then I will add it over here.

  


  For this problem I am really not sure where to file an issue for this so that's why I am writing this here.

  


• Anomalie #4402 (Fermé) : Liste de notices

  12 février 2021, par cedric -

  je ferme ce ticket, car un ticket qui référence un wiki qui liste des patches, ça commence à ressembler à un jeu de pistes
  + depuis novembre 2019 ces notices ont été corrigée
  + maintenant proposer une PR pour chaque cas quand on tombe dessus ça sera beaucoup plus efficace

• Data Privacy Day 2021 : Five ways to embrace privacy into your business

  27 janvier 2021, par Matomo Core Team — Community, Privacy

  Welcome to Data Privacy Day 2021 !

  This year we are excited to announce that we are participating as a #PrivacyAware Champion for DPD21 through the National Cyber Security Alliance. This means that on this significant day we are in partnership with hundreds of other organisations and businesses to share a unified message that empowers individuals to “Own Your Privacy” and for organisations to “Respect Privacy.”

  "Last year dawned a new era in the way many businesses operate from a traditional office work setting to a remote working from home environment for employees. This now means it’s more important than ever for your employees to understand how to take ownership of their privacy when working online."

  As a Data Privacy Day #PrivacyAware Champion we would like to provide some practical tips and share examples of how the Matomo team helps employees be privacy aware.

  

  Five ways to embrace privacy into your business

  1. Create a privacy aware culture within your business

  • Get leadership involved.
  • Appoint privacy ambassadors within your team. 
  • Create a privacy awareness campaign where you educate employees on your company privacy policy. 
  • Share messages about privacy around the office/or in meetings online, on internal message boards, in company newsletters, or emails. 
  • Teach new employees their role in your privacy culture and reinforce throughout their career.

  2. Organise privacy awareness training for your employees

  • Invite outside speakers to talk to employees about why privacy matters. 
  • Engage staff by asking them to consider how privacy and data security applies to the work they do on a daily basis.
  • Encourage employees to complete online courses to gain a better understanding of how to avoid privacy risks.

  3. Help employees manage their individual privacy

  • Better security and privacy behaviours at home will translate to better security and privacy practices at work. 
  • Teach employees how to update their privacy and security settings on personal accounts.
  • Use NCSA’s privacy settings page to help them get started

  4. Add privacy to the employee’s toolbox

  • Give your employees actual tools they can use to improve their privacy, such as company-branded camera covers or privacy screens for their devices, or virtual private networks (VPNs) to secure their connections.

  5. Join Matomo and we’ll be your web analytics experts

  • At Matomo, ensuring our users and customers that their privacy is protected is not only a core component of the work we do, it’s why we do what we do ! Find out how.

  Want to find out more about data privacy download your free DPD 2021 Champion Toolkit and read our post on “Why is privacy important”.

  Team Matomo

  2021 Data Privacy Day Toolkit

  Your guide to Data Privacy Day, January 28, 2021

  Free Download