[Desktop-packages] [Bug 1748273] Re: [snap] Shortcuts to XDG folders are not localized and point to non-existing folders under $SNAP_USER_DATA/
+1, the same issue -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1748273 Title: [snap] Shortcuts to XDG folders are not localized and point to non- existing folders under $SNAP_USER_DATA/ Status in libreoffice package in Ubuntu: Confirmed Bug description: I am using: libreoffice (candidate) 6.0.0.3 from 'canonical' installed The first thing I try is to open a file, but the filepicker is freezed and can't change the folder. Looking in the terminal I have this message: snow /snap/bin/libreoffice (soffice:19124): GLib-GIO-WARNING **: Error creating IO channel for /proc/self/mountinfo: Permission denied (g-file-error-quark, 2) I only can try creating new files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1748273/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1749398] [NEW] Update libva: 2.0.0 --> 2.1.1 before release 18.04 bionic
Public bug reported: Libva 2.1.0 has been released: https://github.com/intel/libva/releases ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libva2 2.0.0-2 Uname: Linux 4.14.0-18.2-liquorix-amd64 x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 Date: Wed Feb 14 11:46:06 2018 InstallationDate: Installed on 2017-08-28 (169 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: libva UpgradeStatus: Upgraded to bionic on 2018-02-08 (5 days ago) ** Affects: libva (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic third-party-packages -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libva in Ubuntu. https://bugs.launchpad.net/bugs/1749398 Title: Update libva: 2.0.0 --> 2.1.1 before release 18.04 bionic Status in libva package in Ubuntu: New Bug description: Libva 2.1.0 has been released: https://github.com/intel/libva/releases ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libva2 2.0.0-2 Uname: Linux 4.14.0-18.2-liquorix-amd64 x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 Date: Wed Feb 14 11:46:06 2018 InstallationDate: Installed on 2017-08-28 (169 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: libva UpgradeStatus: Upgraded to bionic on 2018-02-08 (5 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libva/+bug/1749398/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1722086] [NEW] LIBGL_DRI3_DISABLE=1 not needed anymore (?)
Public bug reported: >From /usr/bin/chromium-browser: # Work around crbug.com/415681 lsmod |grep ^i915\ >/dev/null && export LIBGL_DRI3_DISABLE=1 As written on the bug page, it seems to be not an issue anymore. I commented out that line, and it seems that Chromium works well. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: chromium-browser 63.0.3223.8-0ubuntu1~ppa6~17.10.1 [modified: usr/bin/chromium-browser] [origin: LP-PPA-saiarcot895-chromium-dev] ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: KDE Date: Sun Oct 8 18:41:30 2017 InstallationDate: Installed on 2017-09-08 (29 days ago) InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170908) SourcePackage: chromium-browser ThirdParty: True UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.chromium-browser: [deleted] ** Affects: chromium-browser (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful third-party-packages -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1722086 Title: LIBGL_DRI3_DISABLE=1 not needed anymore (?) Status in chromium-browser package in Ubuntu: New Bug description: From /usr/bin/chromium-browser: # Work around crbug.com/415681 lsmod |grep ^i915\ >/dev/null && export LIBGL_DRI3_DISABLE=1 As written on the bug page, it seems to be not an issue anymore. I commented out that line, and it seems that Chromium works well. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: chromium-browser 63.0.3223.8-0ubuntu1~ppa6~17.10.1 [modified: usr/bin/chromium-browser] [origin: LP-PPA-saiarcot895-chromium-dev] ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: KDE Date: Sun Oct 8 18:41:30 2017 InstallationDate: Installed on 2017-09-08 (29 days ago) InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170908) SourcePackage: chromium-browser ThirdParty: True UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.chromium-browser: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1722086/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1722086] Re: LIBGL_DRI3_DISABLE=1 not needed anymore (?)
I run Chromium with custom flags, from chrome://gpu: /usr/lib/chromium-browser/chromium-browser --ppapi-flash-path=/usr/lib /adobe-flashplugin/libpepflashplayer.so --ppapi-flash-version --enable- pinch --ignore-gpu-blacklist --enable-experimental-canvas-features --enable-accelerated-2d-canvas --force-display-list-2d-canvas --force- gpu-rasterization --enable-fast-unload --enable-accelerated-vpx-decode --enable-tcp-fastopen --javascript-harmony --enable-checker-imaging --v8 -cache-options=code --v8-cache-strategies-for-cache-storage=aggressive --enable-zero-copy --ui-enable-zero-copy --enable-native-gpu-memory- buffers --enable-webgl-image-chromium --flag-switches-begin --enable- accelerated-mjpeg-decode --enable-accelerated-video --force-gpu- rasterization --use-simple-cache-backend=on --enable-tcp-fastopen --enable-zero-copy --ignore-gpu-blacklist --v8-cache-options=code --v8 -cache-strategies-for-cache-storage=aggressive --enable- features=SharedArrayBuffer --flag-switches-end -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1722086 Title: LIBGL_DRI3_DISABLE=1 not needed anymore (?) Status in chromium-browser package in Ubuntu: New Bug description: From /usr/bin/chromium-browser: # Work around crbug.com/415681 lsmod |grep ^i915\ >/dev/null && export LIBGL_DRI3_DISABLE=1 As written on the bug page, it seems to be not an issue anymore. I commented out that line, and it seems that Chromium works well. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: chromium-browser 63.0.3223.8-0ubuntu1~ppa6~17.10.1 [modified: usr/bin/chromium-browser] [origin: LP-PPA-saiarcot895-chromium-dev] ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: KDE Date: Sun Oct 8 18:41:30 2017 InstallationDate: Installed on 2017-09-08 (29 days ago) InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170908) SourcePackage: chromium-browser ThirdParty: True UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.chromium-browser: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1722086/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1722086] Re: LIBGL_DRI3_DISABLE=1 not needed anymore (?)
$ glxinfo | grep OpenGL OpenGL vendor string: Intel Open Source Technology Center OpenGL renderer string: Mesa DRI Intel(R) HD Graphics (Cherrytrail) OpenGL core profile version string: 4.5 (Core Profile) Mesa 17.2.2 OpenGL core profile shading language version string: 4.50 OpenGL core profile context flags: (none) OpenGL core profile profile mask: core profile OpenGL core profile extensions: OpenGL version string: 3.0 Mesa 17.2.2 OpenGL shading language version string: 1.30 OpenGL context flags: (none) OpenGL extensions: OpenGL ES profile version string: OpenGL ES 3.1 Mesa 17.2.2 OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.10 OpenGL ES profile extensions: -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1722086 Title: LIBGL_DRI3_DISABLE=1 not needed anymore (?) Status in chromium-browser package in Ubuntu: New Bug description: From /usr/bin/chromium-browser: # Work around crbug.com/415681 lsmod |grep ^i915\ >/dev/null && export LIBGL_DRI3_DISABLE=1 As written on the bug page, it seems to be not an issue anymore. I commented out that line, and it seems that Chromium works well. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: chromium-browser 63.0.3223.8-0ubuntu1~ppa6~17.10.1 [modified: usr/bin/chromium-browser] [origin: LP-PPA-saiarcot895-chromium-dev] ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: KDE Date: Sun Oct 8 18:41:30 2017 InstallationDate: Installed on 2017-09-08 (29 days ago) InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170908) SourcePackage: chromium-browser ThirdParty: True UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.chromium-browser: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1722086/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1722086] Re: LIBGL_DRI3_DISABLE=1 not needed anymore (?)
I've ran https://web.bsemark.com benchmark with and without LIBGL_DRI3_DISABLE=1, and thr results are the same https://web.basemark.com/result/?4HOntFuD https://web.basemark.com/result/?4HOoWD6P -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1722086 Title: LIBGL_DRI3_DISABLE=1 not needed anymore (?) Status in chromium-browser package in Ubuntu: New Bug description: From /usr/bin/chromium-browser: # Work around crbug.com/415681 lsmod |grep ^i915\ >/dev/null && export LIBGL_DRI3_DISABLE=1 As written on the bug page, it seems to be not an issue anymore. I commented out that line, and it seems that Chromium works well. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: chromium-browser 63.0.3223.8-0ubuntu1~ppa6~17.10.1 [modified: usr/bin/chromium-browser] [origin: LP-PPA-saiarcot895-chromium-dev] ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: KDE Date: Sun Oct 8 18:41:30 2017 InstallationDate: Installed on 2017-09-08 (29 days ago) InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170908) SourcePackage: chromium-browser ThirdParty: True UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.chromium-browser: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1722086/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1241988] Re: All pyqt5 quick examples fails with shader program link error
*** This bug is a duplicate of bug 941826 *** https://bugs.launchpad.net/bugs/941826 The newer version of deepin-screenshot does not have this problem on Ubuntu 16.04, 17.04 and 17.10 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-319-updates in Ubuntu. https://bugs.launchpad.net/bugs/1241988 Title: All pyqt5 quick examples fails with shader program link error Status in nvidia-graphics-drivers-319-updates package in Ubuntu: Triaged Bug description: $ lsb_release -rd Description: Ubuntu 13.10 Release: 13.10 $ apt-cache policy pyqt5-doc pyqt5-doc: Installed: 5.0.1-1ubuntu1 Candidate: 5.0.1-1ubuntu1 Version table: *** 5.0.1-1ubuntu1 0 500 http://no.archive.ubuntu.com/ubuntu/ saucy/universe amd64 Packages 100 /var/lib/dpkg/status Graphics driver: $ apt-cache policy nvidia-319-updates nvidia-319-updates: Installed: 319.60-0ubuntu1 Candidate: 319.60-0ubuntu1 Version table: *** 319.60-0ubuntu1 0 500 http://no.archive.ubuntu.com/ubuntu/ saucy/restricted amd64 Packages 100 /var/lib/dpkg/status All examples under /usr/share/doc/pyqt5-doc/examples/quick/ fails on shader compilation, example: /usr/share/doc/pyqt5-doc/examples/quick/tutorials/extending/chapter1-basics$ python3 chapter1-basics.py QOpenGLShaderProgram: could not create shader program QOpenGLShader: could not create shader QSGMaterialShader: Shader compilation failed: "" QOpenGLShaderProgram::uniformLocation( qt_Matrix ): shader program is not linked QOpenGLShaderProgram: could not create shader program QOpenGLShader: could not create shader QSGMaterialShader: Shader compilation failed: "" QOpenGLShaderProgram::uniformLocation( matrix ): shader program is not linked QOpenGLShaderProgram::uniformLocation( textureScale ): shader program is not linked QOpenGLShaderProgram::uniformLocation( color ): shader program is not linked QOpenGLShaderProgram::uniformLocation( alphaMin ): shader program is not linked QOpenGLShaderProgram::uniformLocation( alphaMax ): shader program is not linked QOpenGLShaderProgram::uniformLocation( fontScale ): shader program is not linked QOpenGLShaderProgram::uniformLocation( vecDelta ): shader program is not linked Segmentation fault (core dumped) $ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-319-updates/+bug/1241988/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1731550] Re: module-switch-on-connect switches to virtual devices
I don't think that Ubuntu developers can do anything with it, they will not disable propper handling of USB dongles to allow PulseEffects work properly and solve https://github.com/wwmm/pulseeffects/issues/99 ** Bug watch added: github.com/wwmm/pulseeffects/issues #99 https://github.com/wwmm/pulseeffects/issues/99 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1731550 Title: module-switch-on-connect switches to virtual devices Status in pulseaudio package in Ubuntu: Confirmed Bug description: The module-switch-on-connect module that has been enabled by default in Artful is causing virtual devices added by PulseEffects (https://github.com/wwmm/pulseeffects) to be activated and set to the default/failsafe device. This also changes which device the system volume control changes. It should only automatically switch when a physical audio device is plugged in. If there is no way to detect this automatically, then I would say this should not be the default configuration, or it should be added as an optional preference. In the meantime, I have worked around the issue by copying /etc/pulse/default.pa into ~/.config/pulse and commenting out loading the module. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1731550/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1737012] [NEW] Chromium random segfaults: error 4 in libnspr4.so
Public bug reported: [109127.127307] chromium-browse[15588]: segfault at a1 ip 7f298eb57cc3 sp 7ffc956c8fc0 Just random and seldom crashes. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: chromium-browser 62.0.3202.94-0ubuntu0.17.10.1388 ProcVersionSignature: Ubuntu 4.13.0-18.21-generic 4.13.13 Uname: Linux 4.13.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 CurrentDesktop: XFCE DRM.card0-DVI-D-1: enabled: enabled dpms: On status: connected edid-base64: AP///wBBDAHBomUAAC4aAQOAMx14KtkFpVdRnicPUFS9SwDRwJUAlQ+zAIHAgYCBQAEBAjqAGHE4LUBYLEUA/R4RAAAe/wBVSEIxNjQ2MDI2MDE4/ABQSEwgMjM3RTcKICAg/QA4TB5TEQAKICAgICAgANk= modes: 1920x1080 1680x1050 1280x1024 1280x1024 1440x900 1440x900 1280x960 1280x720 1024x768 1024x768 800x600 800x600 640x480 640x480 640x480 640x480 720x400 DRM.card0-HDMI-A-1: enabled: disabled dpms: On status: disconnected edid-base64: modes: DRM.card0-VGA-1: enabled: disabled dpms: On status: disconnected edid-base64: modes: Date: Thu Dec 7 21:10:33 2017 Desktop-Session: 'xubuntu' '/etc/xdg/xdg-xubuntu:/etc/xdg:/usr/share/kubuntu-default-settings/kf5-settings:/etc/xdg' '/usr/share/xubuntu:/usr/share/xfce4:/home/user/.local/share/flatpak/exports/share:/var/lib/flatpak/exports/share:/usr/local/share:/usr/share:/var/lib/snapd/desktop:/var/lib/snapd/desktop:/usr/share' DetectedPlugins: Env: 'None' 'None' InstallationDate: Installed on 2017-08-28 (101 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) Load-Avg-1min: 2.98 Load-Processes-Running-Percent: 0.2% MachineType: ASUS All Series ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.13.0-18-generic.efi.signed root=UUID=355fccdc-c430-43b5-929b-f38e35136c1c ro rootflags=subvol=@ quiet splash vt.handoff=7 SourcePackage: chromium-browser UpgradeStatus: Upgraded to artful on 2017-09-16 (81 days ago) dmi.bios.date: 03/10/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0801 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: AM1I-A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0801:bd03/10/2016:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnAM1I-A:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS modified.conffile..etc.default.chromium-browser: [deleted] ** Affects: chromium-browser (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1737012 Title: Chromium random segfaults: error 4 in libnspr4.so Status in chromium-browser package in Ubuntu: New Bug description: [109127.127307] chromium-browse[15588]: segfault at a1 ip 7f298eb57cc3 sp 7ffc956c8fc0 Just random and seldom crashes. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: chromium-browser 62.0.3202.94-0ubuntu0.17.10.1388 ProcVersionSignature: Ubuntu 4.13.0-18.21-generic 4.13.13 Uname: Linux 4.13.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 CurrentDesktop: XFCE DRM.card0-DVI-D-1: enabled: enabled dpms: On status: connected edid-base64: AP///wBBDAHBomUAAC4aAQOAMx14KtkFpVdRnicPUFS9SwDRwJUAlQ+zAIHAgYCBQAEBAjqAGHE4LUBYLEUA/R4RAAAe/wBVSEIxNjQ2MDI2MDE4/ABQSEwgMjM3RTcKICAg/QA4TB5TEQAKICAgICAgANk= modes: 1920x1080 1680x1050 1280x1024 1280x1024 1440x900 1440x900 1280x960 1280x720 1024x768 1024x768 800x600 800x600 640x480 640x480 640x480 640x480 720x400 DRM.card0-HDMI-A-1: enabled: disabled dpms: On status: disconnected edid-base64: modes: DRM.card0-VGA-1: enabled: disabled dpms: On status: disconnected edid-base64: modes: Date: Thu Dec 7 21:10:33 2017 Desktop-Session: 'xubuntu' '/etc/xdg/xdg-xubuntu:/etc/xdg:/usr/share/kubuntu-default-settings/kf5-settings:/etc/xdg' '/usr/share/xubuntu:/usr/share/xfce4:/home/user/.local/share/flatpak/exports/share:/var/lib/flatpak/exports/share:/usr/local/share:/usr/share:/var/lib/snapd/desktop:/var/lib/snapd/desktop:/usr/share' DetectedPlugins: Env: 'None' 'None' InstallationDate: Installed on 2017-08-28 (101 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) Load-Avg-1min: 2.98 Load-Processes-Running-Percent: 0.2% MachineType: ASUS All Series ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.13.0-18-generic.efi.signed root=UUID=355fccdc-c430-43b5-929b-f38e35136c1c r
[Desktop-packages] [Bug 1739509] [NEW] Why was gstreamer0.10 dropped from Ubuntu
Public bug reported: Why was gstreamer0.10 dropped from Ubuntu? It is still available in debian and many applications do use it https://packages.debian.org/search?keywords=libgstreamer0.10&searchon=names&suite=all§ion=all , e.g. proprietary eTXT Antiplagiat. ** Affects: gstreamer0.10 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gstreamer0.10 in Ubuntu. https://bugs.launchpad.net/bugs/1739509 Title: Why was gstreamer0.10 dropped from Ubuntu Status in gstreamer0.10 package in Ubuntu: New Bug description: Why was gstreamer0.10 dropped from Ubuntu? It is still available in debian and many applications do use it https://packages.debian.org/search?keywords=libgstreamer0.10&searchon=names&suite=all§ion=all , e.g. proprietary eTXT Antiplagiat. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer0.10/+bug/1739509/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1737012] Re: Chromium random segfaults: error 4 in libnspr4.so
> Do you know what triggers the crash (e.g. loading a certain type of web > content, …)? No. And so cannot try reproducing with other versions or proprietary Chrome. > Is the latest update (63.0.3239.84-0ubuntu0.17.10.1) also affected? I did not see them. But as I met those segfaults very rarely, may be new ones will still happen one day. > Do you get crash reports in /var/crash ? Will look for them a bit later if they were there and have not been deleted. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1737012 Title: Chromium random segfaults: error 4 in libnspr4.so Status in chromium-browser package in Ubuntu: Incomplete Bug description: [109127.127307] chromium-browse[15588]: segfault at a1 ip 7f298eb57cc3 sp 7ffc956c8fc0 Just random and seldom crashes. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: chromium-browser 62.0.3202.94-0ubuntu0.17.10.1388 ProcVersionSignature: Ubuntu 4.13.0-18.21-generic 4.13.13 Uname: Linux 4.13.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 CurrentDesktop: XFCE DRM.card0-DVI-D-1: enabled: enabled dpms: On status: connected edid-base64: AP///wBBDAHBomUAAC4aAQOAMx14KtkFpVdRnicPUFS9SwDRwJUAlQ+zAIHAgYCBQAEBAjqAGHE4LUBYLEUA/R4RAAAe/wBVSEIxNjQ2MDI2MDE4/ABQSEwgMjM3RTcKICAg/QA4TB5TEQAKICAgICAgANk= modes: 1920x1080 1680x1050 1280x1024 1280x1024 1440x900 1440x900 1280x960 1280x720 1024x768 1024x768 800x600 800x600 640x480 640x480 640x480 640x480 720x400 DRM.card0-HDMI-A-1: enabled: disabled dpms: On status: disconnected edid-base64: modes: DRM.card0-VGA-1: enabled: disabled dpms: On status: disconnected edid-base64: modes: Date: Thu Dec 7 21:10:33 2017 Desktop-Session: 'xubuntu' '/etc/xdg/xdg-xubuntu:/etc/xdg:/usr/share/kubuntu-default-settings/kf5-settings:/etc/xdg' '/usr/share/xubuntu:/usr/share/xfce4:/home/user/.local/share/flatpak/exports/share:/var/lib/flatpak/exports/share:/usr/local/share:/usr/share:/var/lib/snapd/desktop:/var/lib/snapd/desktop:/usr/share' DetectedPlugins: Env: 'None' 'None' InstallationDate: Installed on 2017-08-28 (101 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) Load-Avg-1min: 2.98 Load-Processes-Running-Percent: 0.2% MachineType: ASUS All Series ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.13.0-18-generic.efi.signed root=UUID=355fccdc-c430-43b5-929b-f38e35136c1c ro rootflags=subvol=@ quiet splash vt.handoff=7 SourcePackage: chromium-browser UpgradeStatus: Upgraded to artful on 2017-09-16 (81 days ago) dmi.bios.date: 03/10/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0801 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: AM1I-A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0801:bd03/10/2016:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnAM1I-A:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS modified.conffile..etc.default.chromium-browser: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1737012/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1722086] Re: LIBGL_DRI3_DISABLE=1 not needed anymore (?)
Done. https://github.com/saiarcot895/chromium-ubuntu-build/issues/24 (I thought that you package the PPA...) ** Bug watch added: github.com/saiarcot895/chromium-ubuntu-build/issues #24 https://github.com/saiarcot895/chromium-ubuntu-build/issues/24 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1722086 Title: LIBGL_DRI3_DISABLE=1 not needed anymore (?) Status in chromium-browser package in Ubuntu: Invalid Bug description: From /usr/bin/chromium-browser: # Work around crbug.com/415681 lsmod |grep ^i915\ >/dev/null && export LIBGL_DRI3_DISABLE=1 As written on the bug page, it seems to be not an issue anymore. I commented out that line, and it seems that Chromium works well. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: chromium-browser 63.0.3223.8-0ubuntu1~ppa6~17.10.1 [modified: usr/bin/chromium-browser] [origin: LP-PPA-saiarcot895-chromium-dev] ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: KDE Date: Sun Oct 8 18:41:30 2017 InstallationDate: Installed on 2017-09-08 (29 days ago) InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170908) SourcePackage: chromium-browser ThirdParty: True UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.chromium-browser: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1722086/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1012277] Re: Closing laptop lid should not blank external monitor
Confirm the bug with the dafault Xubuntu theme. $ env GTK_THEME=Abiword solves the problem, no more flickering -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-power-manager in Ubuntu. https://bugs.launchpad.net/bugs/1012277 Title: Closing laptop lid should not blank external monitor Status in gnome-power-manager package in Ubuntu: Confirmed Bug description: I'm using Precise Pangolin installed from scratch, with the latest updates. txelu@txelu-acer:~$ lsb_release -rd Description:Ubuntu 12.04 LTS Release:12.04 My problem is that I have my laptop connected to an external monitor, and if I started Ubuntu with the lid open I can't close, because not only the laptop screen goes blank, but also the external monitor. As a curious detail if I close the lid right after switching on the laptop, before Ubuntu starts up, it works as expected. Of course, I have set the Energy configuration to do nothing on closing the lid, and I agree that the laptop screen in that situation should go black, but not the external screen. There is a similar bug filled against previous versions of Ubuntu (#416236) that was considered a regression, but in that case there was a workaround using gconf-editor to manually edit the settings for the gnome-power-manager, but there is no such a entry now in 12.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/1012277/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1685639] [NEW] network-manager-gnome must depend on dnsmasq for WiFi/Ethernet hotspots to work
Public bug reported: There is a button in network-manager-gnome GUI that starts a WiFi hotspot, but it does not work out of the box on Ubuntu GNOME 17.04 untill dnsmasq is installed manually. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: network-manager-gnome 1.4.2-1ubuntu4 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Apr 23 19:22:02 2017 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2017-04-22 (1 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412) IpRoute: default via 192.168.1.1 dev enx582c80139263 proto static metric 100 192.168.1.0/24 dev enx582c80139263 proto kernel scope link src 192.168.1.100 metric 100 NetworkManager.conf: [main] plugins=ifupdown,keyfile [ifupdown] managed=false NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true ProcEnviron: TERM=xterm-256color PATH=(custom, no username) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash SourcePackage: network-manager-applet UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH enx582c80139263 ethernet connected /org/freedesktop/NetworkManager/Devices/4 Проводное соединение 2 543da71d-1383-469f-95b0-114ce014d787 /org/freedesktop/NetworkManager/ActiveConnection/7 wlp3s0 wifi disconnected /org/freedesktop/NetworkManager/Devices/2 -- -- -- enp2s0 ethernet unavailable /org/freedesktop/NetworkManager/Devices/1 -- -- -- lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/0 -- -- -- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.4.4connected started full enabled enabled enabled enabled enabled ** Affects: network-manager-applet (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages zesty -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/1685639 Title: network-manager-gnome must depend on dnsmasq for WiFi/Ethernet hotspots to work Status in network-manager-applet package in Ubuntu: New Bug description: There is a button in network-manager-gnome GUI that starts a WiFi hotspot, but it does not work out of the box on Ubuntu GNOME 17.04 untill dnsmasq is installed manually. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: network-manager-gnome 1.4.2-1ubuntu4 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Apr 23 19:22:02 2017 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2017-04-22 (1 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412) IpRoute: default via 192.168.1.1 dev enx582c80139263 proto static metric 100 192.168.1.0/24 dev enx582c80139263 proto kernel scope link src 192.168.1.100 metric 100 NetworkManager.conf: [main] plugins=ifupdown,keyfile [ifupdown] managed=false NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true ProcEnviron: TERM=xterm-256color PATH=(custom, no username) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash SourcePackage: network-manager-applet UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH enx582c80139263 ethernet connected /org/freedesktop/NetworkManager/Devices/4 Проводное соединение 2 543da71d-1383-469f-95b0-114ce014d787 /org/freedesktop/NetworkManager/ActiveConnection/7 wlp3s0 wifi disconnected /org/freedesktop/NetworkManager/Devices/2 -- -- -- enp2s0 ethernet unavailable /org/freedesktop/NetworkMana
[Desktop-packages] [Bug 1768595] [NEW] invalid CPU instruction in chromium built with LLVM 6.0
Public bug reported: Chromium crashed randomly: $ dmesg [ 7383.735592] traps: chromium-browse[15302] trap invalid opcode ip:55da81b19cc5 sp:7fff229f1c88 error:0 in chromium-browser[55da7f11b000+838f000] It has happened only once so far and I can't reproduce the crash. Maybe it is somehow connected with clang bugs which lead to chromium being unable to start on i586 due to invalid CPU instructions (opcodes): https://bugzilla.altlinux.org/show_bug.cgi?id=34742 https://bugzilla.altlinux.org/show_bug.cgi?id=34722 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: chromium-browser 65.0.3325.181-0ubuntu1 Uname: Linux 4.16.6-041606-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: XFCE DRM.card0-DVI-D-1: enabled: enabled dpms: On status: connected edid-base64: AP///wBBDAHBomUAAC4aAQOAMx14KtkFpVdRnicPUFS9SwDRwJUAlQ+zAIHAgYCBQAEBAjqAGHE4LUBYLEUA/R4RAAAe/wBVSEIxNjQ2MDI2MDE4/ABQSEwgMjM3RTcKICAg/QA4TB5TEQAKICAgICAgANk= modes: 1920x1080 1680x1050 1280x1024 1280x1024 1440x900 1440x900 1280x960 1280x720 1024x768 1024x768 800x600 800x600 640x480 640x480 640x480 640x480 720x400 DRM.card0-HDMI-A-1: enabled: disabled dpms: On status: disconnected edid-base64: modes: DRM.card0-VGA-1: enabled: disabled dpms: On status: disconnected edid-base64: modes: Date: Wed May 2 19:30:26 2018 Desktop-Session: 'xubuntu' '/etc/xdg/xdg-xubuntu:/etc/xdg:/usr/share/kubuntu-default-settings/kf5-settings:/etc/xdg' '/usr/share/xfce4:/usr/share/xubuntu:/usr/local/share:/usr/share:/var/lib/snapd/desktop:/var/lib/snapd/desktop:/usr/share' DetectedPlugins: Env: 'None' 'None' InstallationDate: Installed on 2017-08-28 (247 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) Load-Avg-1min: 1.87 Load-Processes-Running-Percent: 0.2% MachineType: ASUS All Series ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.16.6-041606-generic root=UUID=355fccdc-c430-43b5-929b-f38e35136c1c ro rootflags=subvol=@ SourcePackage: chromium-browser UpgradeStatus: Upgraded to bionic on 2018-02-08 (83 days ago) dmi.bios.date: 03/10/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0801 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: AM1I-A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0801:bd03/10/2016:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnAM1I-A:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS modified.conffile..etc.default.chromium-browser: [deleted] ** Affects: chromium-browser (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1768595 Title: invalid CPU instruction in chromium built with LLVM 6.0 Status in chromium-browser package in Ubuntu: New Bug description: Chromium crashed randomly: $ dmesg [ 7383.735592] traps: chromium-browse[15302] trap invalid opcode ip:55da81b19cc5 sp:7fff229f1c88 error:0 in chromium-browser[55da7f11b000+838f000] It has happened only once so far and I can't reproduce the crash. Maybe it is somehow connected with clang bugs which lead to chromium being unable to start on i586 due to invalid CPU instructions (opcodes): https://bugzilla.altlinux.org/show_bug.cgi?id=34742 https://bugzilla.altlinux.org/show_bug.cgi?id=34722 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: chromium-browser 65.0.3325.181-0ubuntu1 Uname: Linux 4.16.6-041606-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: XFCE DRM.card0-DVI-D-1: enabled: enabled dpms: On status: connected edid-base64: AP///wBBDAHBomUAAC4aAQOAMx14KtkFpVdRnicPUFS9SwDRwJUAlQ+zAIHAgYCBQAEBAjqAGHE4LUBYLEUA/R4RAAAe/wBVSEIxNjQ2MDI2MDE4/ABQSEwgMjM3RTcKICAg/QA4TB5TEQAKICAgICAgANk= modes: 1920x1080 1680x1050 1280x1024 1280x1024 1440x900 1440x900 1280x960 1280x720 1024x768 1024x768 800x600 800x600 640x480 640x480 640x480 640x480 720x400 DRM.card0-HDMI-A-1: enabled: disabled dpms: On status: disconnected edid-base64: modes: DRM.card0-VGA-1: enabled: disabled dpms: On status: disconnected edid-base64: modes: Date: Wed May 2 19:30:26 2018 Desktop-Session: 'xubuntu' '/etc/xdg/xdg-xubuntu:/etc/xdg:/usr/share/kubuntu-default-settings/kf5-settings:/etc/xdg' '/usr/share/xfce4:/usr/share/xubuntu:/usr/local/share:/usr/share:/var/lib/snapd/desktop:/var/lib/snapd/desktop:/usr/share' DetectedPlugins: Env: 'None' 'None' InstallationDate: Installed on 20
[Desktop-packages] [Bug 1615213] [NEW] MIME application/octet-stream not binded to Video players
Public bug reported: OS: Ubuntu 16.04.1 DE: Unity .TOD (application/octet-stream) files are nor associated with Video players by default. E.g. they are correctly opened by Totem video player. By default the system considers them to be text files. Also reported this bug to freedesktop: https://bugs.freedesktop.org/show_bug.cgi?id=97419 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xdg-utils 1.1.1-1ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15 Uname: Linux 4.4.0-34-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity Date: Sat Aug 20 13:23:07 2016 InstallationDate: Installed on 2016-07-17 (34 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all SourcePackage: xdg-utils UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: xdg-utils (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-utils in Ubuntu. https://bugs.launchpad.net/bugs/1615213 Title: MIME application/octet-stream not binded to Video players Status in xdg-utils package in Ubuntu: New Bug description: OS: Ubuntu 16.04.1 DE: Unity .TOD (application/octet-stream) files are nor associated with Video players by default. E.g. they are correctly opened by Totem video player. By default the system considers them to be text files. Also reported this bug to freedesktop: https://bugs.freedesktop.org/show_bug.cgi?id=97419 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xdg-utils 1.1.1-1ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15 Uname: Linux 4.4.0-34-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity Date: Sat Aug 20 13:23:07 2016 InstallationDate: Installed on 2016-07-17 (34 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all SourcePackage: xdg-utils UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdg-utils/+bug/1615213/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1399333] Re: Berkley Packet Filter handling, error with ESET NOD32 Antivirus 4 and Chromium
Did you try a newer kernel?
sudo apt update
sudo apt install linux-generic-lts-xenial
sudo reboot
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1399333
Title:
Berkley Packet Filter handling, error with ESET NOD32 Antivirus 4 and
Chromium
Status in chromium-browser package in Ubuntu:
New
Bug description:
I installed ESET NOD32 Antivirus 4 Business Edition on my Xubuntu.
After that, Chromium browser has stopped working ("awgh" error or
something like that). According to help I've tried to use new default
profile, without success. After uninstalling ESET NOD32 it has started
to work again.
So I contacted ESET to tell them they've got a bug in their application. To
my surprise, they replied no they had not, and, quote:
"""
...That is a bug in Berkley Packet Filter handling. SRWare Iron browser is
suffering this issue, too. Other browsers do not, it is not a problem of ESET
NOD32...
"""
So now I am handing it over to you, guys...
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: chromium-browser 39.0.2171.65-0ubuntu0.14.04.1.1064
ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2
Uname: Linux 3.13.0-29-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.5
Architecture: amd64
CurrentDesktop: XFCE
Date: Thu Dec 4 21:09:46 2014
ExecutablePath: /usr/lib/chromium-browser/chromium-browser
InstallationDate: Installed on 2013-10-26 (404 days ago)
InstallationMedia: Xubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016)
SourcePackage: chromium-browser
UpgradeStatus: Upgraded to trusty on 2014-06-11 (176 days ago)
modified.conffile..etc.default.chromium.browser: [deleted]
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1399333/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1696965] Re: First renderer process doesn't render page for chromium 59.0.3071.86 in KVM
Google compiles Chrome using Clang, but the Ubuntu packages is built using gcc, ofc ourse, it should not be the reason of the bug, but still why not to swith to clang? Are VAAPI patches applied to the ubuntu package? Maybe they are the reason? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1696965 Title: First renderer process doesn't render page for chromium 59.0.3071.86 in KVM Status in chromium-browser package in Ubuntu: New Bug description: Chromium 59.0.3071.86 was promoted to the stable release channel earlier this week, and I have built packages for all supported ubuntu releases at https://launchpad.net/~osomon/+archive/ubuntu/chromium- stable. While they seem to work well on bare metal and in virtualbox virtual machines, we are seeing an issue in KVM guests (e.g. Ubuntu 16.04.2): when launched, the page in the first tab is not rendered at all (the contents remain blank). Refreshing the page doesn't make things any better. But browsing to a different domain in the same tab "fixes" the issue. All URLs are affected: the default URL when opening the browser for the first time is chrome://welcome, and it's not rendered, and so aren't other http URLs when passed on the command line. It looks like the first renderer process is not able to render to screen correctly. The renderer process itself looks okay, it doesn't crash, and I haven't seen anything relevant in the verbose logs. The official google chrome release on the same configuration is not affected, so this problem is specific to our chromium-browser packages. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1696965/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1241988] Re: All pyqt5 quick examples fails with shader program link error
*** This bug is a duplicate of bug 941826 *** https://bugs.launchpad.net/bugs/941826 Yes, the problem exists, I am using MAUI (mauilinux.org), Ubuntu 16.04 with Qt 5.7, I get this error only in deepin-screenshot from https://launchpad.net/~leaeasy/+archive/ubuntu/dde I tried to rebuild the package (because it was build with another version of Qt), the rebuild was successfull, but the error resists. Get this with both nvidia-375 and nvidia-381. When I switch to Intel Graphics on the same machine, deepin-screenshot works well,not OpenGL errors occur. I did not have this issue beforehand with nvidia. I will try to conact Nvidia... -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-319-updates in Ubuntu. https://bugs.launchpad.net/bugs/1241988 Title: All pyqt5 quick examples fails with shader program link error Status in nvidia-graphics-drivers-319-updates package in Ubuntu: Triaged Bug description: $ lsb_release -rd Description: Ubuntu 13.10 Release: 13.10 $ apt-cache policy pyqt5-doc pyqt5-doc: Installed: 5.0.1-1ubuntu1 Candidate: 5.0.1-1ubuntu1 Version table: *** 5.0.1-1ubuntu1 0 500 http://no.archive.ubuntu.com/ubuntu/ saucy/universe amd64 Packages 100 /var/lib/dpkg/status Graphics driver: $ apt-cache policy nvidia-319-updates nvidia-319-updates: Installed: 319.60-0ubuntu1 Candidate: 319.60-0ubuntu1 Version table: *** 319.60-0ubuntu1 0 500 http://no.archive.ubuntu.com/ubuntu/ saucy/restricted amd64 Packages 100 /var/lib/dpkg/status All examples under /usr/share/doc/pyqt5-doc/examples/quick/ fails on shader compilation, example: /usr/share/doc/pyqt5-doc/examples/quick/tutorials/extending/chapter1-basics$ python3 chapter1-basics.py QOpenGLShaderProgram: could not create shader program QOpenGLShader: could not create shader QSGMaterialShader: Shader compilation failed: "" QOpenGLShaderProgram::uniformLocation( qt_Matrix ): shader program is not linked QOpenGLShaderProgram: could not create shader program QOpenGLShader: could not create shader QSGMaterialShader: Shader compilation failed: "" QOpenGLShaderProgram::uniformLocation( matrix ): shader program is not linked QOpenGLShaderProgram::uniformLocation( textureScale ): shader program is not linked QOpenGLShaderProgram::uniformLocation( color ): shader program is not linked QOpenGLShaderProgram::uniformLocation( alphaMin ): shader program is not linked QOpenGLShaderProgram::uniformLocation( alphaMax ): shader program is not linked QOpenGLShaderProgram::uniformLocation( fontScale ): shader program is not linked QOpenGLShaderProgram::uniformLocation( vecDelta ): shader program is not linked Segmentation fault (core dumped) $ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-319-updates/+bug/1241988/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1701462] [NEW] window buttons disappear on KDE with libunity9
Public bug reported: This bug has been in the upstream bugtracker for about 2 years: https://bugs.chromium.org/p/chromium/issues/detail?id=375650 To reproduce: - use KDE 5 - sudo apt install libunity9 - set Chromium/Chrome to not use system window decoration - maximize the window - it will not have window control buttons (attaching a screenshot from the upstream bug) libunity9 is a dependency of pidgin, brasero etc. I think that libunity9 should be a recomended dependency for pidgin, brasero etc. so that it could be easily removed without removing those programs. ** Affects: chromium-browser (Ubuntu) Importance: Undecided Status: New ** Attachment added: "0bc449d5-d59c-41ae-9661-028c1c779906.png" https://bugs.launchpad.net/bugs/1701462/+attachment/4906251/+files/0bc449d5-d59c-41ae-9661-028c1c779906.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1701462 Title: window buttons disappear on KDE with libunity9 Status in chromium-browser package in Ubuntu: New Bug description: This bug has been in the upstream bugtracker for about 2 years: https://bugs.chromium.org/p/chromium/issues/detail?id=375650 To reproduce: - use KDE 5 - sudo apt install libunity9 - set Chromium/Chrome to not use system window decoration - maximize the window - it will not have window control buttons (attaching a screenshot from the upstream bug) libunity9 is a dependency of pidgin, brasero etc. I think that libunity9 should be a recomended dependency for pidgin, brasero etc. so that it could be easily removed without removing those programs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1701462/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1696965] Re: First renderer process doesn't render page for chromium 59.0.3071.86 in KVM
Just curious to better understand how stable packages get to the repositories, does this bug block Chromium 59 from being moved to mainline repositories? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1696965 Title: First renderer process doesn't render page for chromium 59.0.3071.86 in KVM Status in chromium-browser package in Ubuntu: Confirmed Bug description: Chromium 59.0.3071.86 was promoted to the stable release channel earlier this week, and I have built packages for all supported ubuntu releases at https://launchpad.net/~osomon/+archive/ubuntu/chromium- stable. While they seem to work well on bare metal and in virtualbox virtual machines, we are seeing an issue in KVM guests (e.g. Ubuntu 16.04.2): when launched, the page in the first tab is not rendered at all (the contents remain blank). Refreshing the page doesn't make things any better. But browsing to a different domain in the same tab "fixes" the issue. All URLs are affected: the default URL when opening the browser for the first time is chrome://welcome, and it's not rendered, and so aren't other http URLs when passed on the command line. It looks like the first renderer process is not able to render to screen correctly. The renderer process itself looks okay, it doesn't crash, and I haven't seen anything relevant in the verbose logs. The official google chrome release on the same configuration is affected too, although much less often. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1696965/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1664147] Re: Chromium on trusty too outdated; not supported by gmail
Can you please post $ glxinfo | grep OpenGL and $ dmesg | grep -i drm Chromium creates multiple processes when working, and above is the crash of the GPU sub-process. Maybe it tries to use GPU acceleration, but fails to do ot, and the GPU is not blacklisted or you set it to ignore the blacklist in chrome://flags Also try dropping chrome://flags to default -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1664147 Title: Chromium on trusty too outdated; not supported by gmail Status in chromium-browser package in Ubuntu: Fix Released Bug description: As of Feb 13 2017, the chromium version on trusty is 53.x which is at least a couple of versions behind chrome-stable. Gmail displays this message, "This version of Chrome is no longer supported. Please upgrade to asupported browser." Core functionality in gmail works fine, but I'm not sure of security ramifications of running an old browser, particularly when google advises against it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1664147/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
