[Desktop-packages] [Bug 1815523] Re: The last MESA updates (02/07/19) corrupted output to DisplayLink
Are you still able to reproduce it with the stock bionic kernel? If yes, it's still a bug ** Changed in: mesa (Ubuntu) Status: Invalid => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1815523 Title: The last MESA updates (02/07/19) corrupted output to DisplayLink Status in mesa package in Ubuntu: Incomplete Bug description: Prior to Thursday's "update" from Bionic-Proposed, the MESA was working fine; afterwards, gameplay on STEAM has become choppy and staccato; secondary display via a USB-C through DisplayPort UD3900 (Pluggable) is completely corrupted. See attached picture. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-15-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity:Unity7:ubuntu Date: Mon Feb 11 16:50:58 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: acpi-call, 1.1.0, 4.18.0-15-generic, x86_64: installedError! Could not locate dkms.conf file. File: does not exist. ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:3ea0] (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer Device [1558:1323] InstallationDate: Installed on 2019-01-15 (27 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: System76 Galago Pro ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-15-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/05/2018 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.03 dmi.board.asset.tag: Tag 12345 dmi.board.name: Galago Pro dmi.board.vendor: System76 dmi.board.version: galp3-c dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: System76 dmi.chassis.version: galp3-c dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.03:bd12/05/2018:svnSystem76:pnGalagoPro:pvrgalp3-c:rvnSystem76:rnGalagoPro:rvrgalp3-c:cvnSystem76:ct10:cvrgalp3-c: dmi.product.family: Not Applicable dmi.product.name: Galago Pro dmi.product.sku: Not Applicable dmi.product.version: galp3-c dmi.sys.vendor: System76 version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1815523/+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 1791409] Re: LIRC not working on Ubuntu 18.04
That said, if someone filed a bug against lirc because lirc-setup is broken, that bug is certainly valid. But IMHO, that's a very different story. And since there is a usable work-around it would probably just be closed as fixed upstream. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lirc in Ubuntu. https://bugs.launchpad.net/bugs/1791409 Title: LIRC not working on Ubuntu 18.04 Status in lirc package in Ubuntu: Incomplete Bug description: It appears that the LIRC 0.10.0-2 package for Ubuntu 18.04 (bionic) is not working correctly. The usual configuration menu to select your remote does not come up after installing the package. Saw some other mentions of this issue as well on the forums: https://ubuntuforums.org/showthread.php?t=2396923 This handy blog post shows a workaround of installing an older version (0.9.0) from xenial to get it to work: https://twosortoftechguys.wordpress.com/2018/07/24/make-lirc-work-in- ubuntu-18-04/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lirc/+bug/1791409/+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 1791409] Re: LIRC not working on Ubuntu 18.04
The main issue described in this bug is bogus, as apparent from bug #1788235 However, the configuration script lirc-setup *is* indeed broken . This is fixed in Debian upstream from 0.10.1, but hasn't trickled down. That said, users will still need to read README.Debian, and the process to configure lirc is still very different from what it used to be. Also, most users updating does not need lirc-setup. I'm considering closing this bug as a duplicate or just invalid. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lirc in Ubuntu. https://bugs.launchpad.net/bugs/1791409 Title: LIRC not working on Ubuntu 18.04 Status in lirc package in Ubuntu: Incomplete Bug description: It appears that the LIRC 0.10.0-2 package for Ubuntu 18.04 (bionic) is not working correctly. The usual configuration menu to select your remote does not come up after installing the package. Saw some other mentions of this issue as well on the forums: https://ubuntuforums.org/showthread.php?t=2396923 This handy blog post shows a workaround of installing an older version (0.9.0) from xenial to get it to work: https://twosortoftechguys.wordpress.com/2018/07/24/make-lirc-work-in- ubuntu-18-04/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lirc/+bug/1791409/+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 1815670] Re: Ubuntu 19.04: Severe GObject/GType error and crash
This bug was fixed in the package gst-plugins-good1.0 - 1.15.1-1ubuntu2 --- gst-plugins-good1.0 (1.15.1-1ubuntu2) disco; urgency=medium * Cherry-pick Revert-pulsesrc-Move-to-extended-stream-API.patch: - Back out a feature that depends on an unreleased PulseAudio feature and broke audio recording (LP: #1815670) -- Jeremy Bicha Tue, 12 Feb 2019 23:15:55 -0500 ** Changed in: gst-plugins-good1.0 (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gst-plugins-good1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1815670 Title: Ubuntu 19.04: Severe GObject/GType error and crash Status in gst-plugins-good1.0 package in Ubuntu: Fix Released Bug description: Hello, I am trying to make Audio-recorder to compile and run under Ubuntu 19.04 (Ubuntu Disco Dingo - development branch). 1) A GStreamer bug. This crash occurs if I run a Gstreamer pipleline on the command line (in a terminal window). Like this. $ gst-launch-1.0 -e pulsesrc | fakesink (gst-launch-1.0:8410): GLib-GObject-WARNING **: 21:31:05.365: ../../../gobject/gtype.c:4265: type id '0' is invalid (gst-launch-1.0:8410): GLib-GObject-WARNING **: 21:31:05.365: can't peek value table for type '' which is not currently referenced Caught SIGSEGV Spinning. Please run 'gdb gst-launch-1.0 8410' to continue debugging, Ctrl-C to quit, or Ctrl-\ to dump core. -- 2) Also, it seems that the same bug causes my audio-recorder program crash. It happens in all gtk_button_set_image(...) calls during runtime. gtk_button_set_image(GTK_BUTTON(g_win.recorder_button), GTK_WIDGET(image)); The error message is: (audio-recorder:32368): GLib-GObject-WARNING **: 19:21:52.600: ../../../gobject/gtype.c:4265: type id '0' is invalid (audio-recorder:32368): GLib-GObject-WARNING **: 19:21:52.600: can't peek value table for type '' which is not currently referenced Segmentation fault (core dumped) Please educate me if you want more debug info or stacktrace. My system is: $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu Disco Dingo (development branch) Release: 19.04 Codename: disco My system has very latest updates. Any comments? Kindly Osmo (moma) Antero --- EDIT: This bug report is similar https://gitlab.freedesktop.org/gstreamer/gst-plugins-good/issues/552 --- ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gstreamer1.0-tools 1.15.1-1 ProcVersionSignature: Ubuntu 4.19.0-12.13-generic 4.19.18 Uname: Linux 4.19.0-12-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu20 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Feb 12 21:31:51 2019 ExecutablePath: /usr/bin/gst-launch-1.0 InstallationDate: Installed on 2019-02-04 (8 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190203) SourcePackage: gstreamer1.0 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gst-plugins-good1.0/+bug/1815670/+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 1815711] [NEW] [Dell G7 7588] *ERROR* Fault errors on pipe B: 0x00000080
Public bug reported: Hi, Recently, I installed Ubuntu 18.04 on my Dell G7 7588. From day one, the system has random freezes/crashes (usually a few a day) The way the crashes manifest is that 2 out of my 3 monitors go black and in some cases sound and inputs get stuck. In some rare cases, I can continue to operate on one of the screens. I checked syslog and dmesg, and usually I don't see any messages at the time of the crash, except this one time that input did not freeze and I could run a dmesg. In that case I got this message: Feb 13 15:34:51 morningstar kernel: [ 1593.615704] [drm:gen8_de_irq_handler [i915]] *ERROR* Fault errors on pipe B: 0x0080 Feb 13 15:34:51 morningstar kernel: [ 1593.615999] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe B FIFO underrun Additionally, this message appears on dmesg fairly often: ... Feb 13 15:21:17 morningstar kernel: [ 780.324457] CPU6: Package temperature above threshold, cpu clock throttled (total events = 109) Feb 13 15:21:17 morningstar kernel: [ 780.324457] CPU0: Package temperature above threshold, cpu clock throttled (total events = 109) ... I tried to solve this issue on my own for a while now, without success, here are some of the things I tried: - Updated BIOS to latest version - Installed nvidia 415 graphic drivers - Tested using xwayland - Tried 4.15.0-45-48, 4.19.16 and 4.19.20 kernels (this last one generates problems with the graphic drivers, and does not solve the problem either. - Tried modifying power management profile on the BIOS. - Added splash acpi_rev_override=1 to /etc/default/grub as found here: https://www.reddit.com/r/Dell/comments/63cavx/fixed_nvidia_1050_freezing_in_ubuntu_linux/ - Ran dell diagnostic tools (no errors there) So far none of this things solved the issue. These error messages are the only noticeable things I could find to debug... Can someone help me find a fix or workaround the issue? I've been spending multiple days trying to solve this and I am not making any real progress Please let me know if you need me to submit more information to find the cause of the issue ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 Uname: Linux 4.19.16-041916-generic x86_64 NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 415.27 Thu Dec 20 17:25:03 CST 2018 GCC version: gcc version 7.3.0 (Ubuntu 7.3.0-27ubuntu1~18.04) ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Wed Feb 13 15:51:17 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 415.27, 4.15.0-45-generic, x86_64: installed virtualbox, 5.2.18, 4.15.0-44-generic, x86_64: installed virtualbox, 5.2.18, 4.15.0-45-generic, x86_64: installed virtualbox, 5.2.18, 4.19.16-041916-generic, x86_64: installed ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a day GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation Device [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0825] NVIDIA Corporation GP106M [GeForce GTX 1060 Mobile] [10de:1c20] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell GP106M [GeForce GTX 1060 Mobile] [1028:0825] InstallationDate: Installed on 2018-11-30 (75 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Dell Inc. G7 7588 ProcEnviron: LANGUAGE=en_AU:en TERM=xterm-256color PATH=(custom, no user) LANG=en_AU.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.19.16-041916-generic root=UUID=ed06b2b0-7398-48df-9971-9f5f225c0152 ro quiet splash acpi_rev_override=1 vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/21/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.8.0 dmi.board.name: 0FDMYT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.8.0:bd12/21/2018:svnDellInc.:pnG77588:pvr:rvnDellInc.:rn0FDMYT:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: GSeries dmi.product.name: G7 7588 dmi.product.sku: 0825 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1~18.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev:
[Desktop-packages] [Bug 1808398] Re: top right menu does not display when activated
[Expired for gnome-shell (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1808398 Title: top right menu does not display when activated Status in gnome-shell package in Ubuntu: Expired Bug description: 1) Install Ubuntu 18.04.1 via debbootstrap 2) Install ubuntu-desktop package 3) Install vanilla-desktop package 4) Upgrade to 18.10 using the Software GUI 5) Log into Ubuntu on Wayland 6) Click right end of top bar, menu drops down. 7) Mouse over menu, no visual feedback of focus (as with Ubuntu on Xorg) 8) Interact with menu items - there is no visual feedback. For example - sliding back and forth on the screen brightness slider causes the screen brightness to change as expected but the slider does not reflect changes. Clicking on the right end of the top bar causes the menu to deactivate but before it does, the slider position updates. - click on the user name and nothing appears to happen. Click below it where the submenu would appear causes the submenu to activate. (the logout dialog appears.) I'm not sure if steps 1-4 are required vs. just installing 18.10 but I list it in case this results from left over settings from 18.04 installing via debbootstrap. hbarta@saugage:~$ lsb_release -rd Description: Ubuntu 18.10 Release: 18.10 hbarta@saugage:~$ hbarta@saugage:~$ apt-cache policy gnome-shell mutter xwayland gnome-menus libgnome-menu-3-0:amd64 gnome-shell: Installed: 3.30.1-2ubuntu1.18.10.1 Candidate: 3.30.1-2ubuntu1.18.10.1 Version table: *** 3.30.1-2ubuntu1.18.10.1 500 500 http://archive.ubuntu.com/ubuntu cosmic-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.30.1-2ubuntu1 500 500 http://archive.ubuntu.com/ubuntu cosmic/main amd64 Packages mutter: Installed: 3.30.2-1~ubuntu18.10.1 Candidate: 3.30.2-1~ubuntu18.10.1 Version table: *** 3.30.2-1~ubuntu18.10.1 500 500 http://archive.ubuntu.com/ubuntu cosmic-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.30.1-1 500 500 http://archive.ubuntu.com/ubuntu cosmic/main amd64 Packages xwayland: Installed: 2:1.20.1-3ubuntu2.1 Candidate: 2:1.20.1-3ubuntu2.1 Version table: *** 2:1.20.1-3ubuntu2.1 500 500 http://security.ubuntu.com/ubuntu cosmic-security/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu cosmic-updates/main amd64 Packages 100 /var/lib/dpkg/status 2:1.20.1-3ubuntu2 500 500 http://archive.ubuntu.com/ubuntu cosmic/main amd64 Packages gnome-menus: Installed: 3.13.3-11ubuntu2 Candidate: 3.13.3-11ubuntu2 Version table: *** 3.13.3-11ubuntu2 500 500 http://archive.ubuntu.com/ubuntu cosmic/main amd64 Packages 100 /var/lib/dpkg/status libgnome-menu-3-0: Installed: 3.13.3-11ubuntu2 Candidate: 3.13.3-11ubuntu2 Version table: *** 3.13.3-11ubuntu2 500 500 http://archive.ubuntu.com/ubuntu cosmic/main amd64 Packages 100 /var/lib/dpkg/status hbarta@saugage:~$ Expected behavior: menu provides visual feedback to clicks. Underlying action seems to happen but there is no hint of that or display of submenus. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gnome-shell 3.30.1-2ubuntu1.18.10.1 ProcVersionSignature: Ubuntu 4.18.0-12.13-generic 4.18.17 Uname: Linux 4.18.0-12-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Dec 13 11:41:23 2018 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'command-history' redacted by apport b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: Upgraded to cosmic on 2018-12-13 (0 days ago) mtime.conffile..etc.logrotate.d.apport: 2018-12-12T13:31:49.347693 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1808398/+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 1815709] [NEW] please enable libreoffice-help-id package
Public bug reported: Recently before 6.2 upstream release, translations of Indonesian help has reached around 90%. Please build libreoffice-help-id package so that translation can be easily used by users. ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New -- 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/1815709 Title: please enable libreoffice-help-id package Status in libreoffice package in Ubuntu: New Bug description: Recently before 6.2 upstream release, translations of Indonesian help has reached around 90%. Please build libreoffice-help-id package so that translation can be easily used by users. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1815709/+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 1810382] Re: Gnome software error posting a review for snap app
@azzar1 correct the upstream change made the snaps reviewable, however the ubuntu-reviews plugin suppresses the ODRS plugin so reviews fail to be posted. We should have patched the NOT_REVIEWABLE quick back in. I agree it's easier to move forwards and SRU the ODRS change back to Cosmic (bug 1815708). It's been long enough in Disco now to have some confidence this works well. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1810382 Title: Gnome software error posting a review for snap app Status in gnome-software package in Ubuntu: Triaged Bug description: Received msg: Sorry, something went wrong: Got unknown content type text/html from reviews.ubuntu.com posting a review for snap app. this does not happen for 'normal' apps ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gnome-software 3.30.2-0ubuntu8 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Jan 3 09:06:57 2019 ExecutablePath: /usr/bin/gnome-software InstallationDate: Installed on 2018-10-22 (73 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-limba N/A gnome-software-plugin-snap3.30.2-0ubuntu8 SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1810382/+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 1815708] [NEW] Use ODRS for reviews
Public bug reported: [Impact] The Ubuntu review server is being retired which will cause all Ubuntu package reviews to stop working. We are switching to using the Open Desktop Review Service (https://odrs.gnome.org/). This plugin has existed for sometime in the GNOME Software source, so it is well tested. This change will allow Snap packages to be reviewed (new feature). [Test Case] 1. Open GNOME Software 2. Select a popular app (e.g. Firefox) [Expected Result] Reviews are shown for this package. They will be different to the previous reviews. You are able to create reviews for both .deb and snap apps. [Regression Potential] There is a risk of new bugs encountered in the ODRS plugin. This has been enabled in Disco without major issue and has been used in other distributions for many releases. ** Affects: gnome-software (Ubuntu) Importance: Medium Status: Fix Released ** Affects: gnome-software (Ubuntu Xenial) Importance: Medium Status: New ** Affects: gnome-software (Ubuntu Bionic) Importance: Medium Status: New ** Affects: gnome-software (Ubuntu Cosmic) Importance: Medium Status: New ** Affects: gnome-software (Ubuntu Disco) Importance: Medium Status: Fix Released ** Also affects: gnome-software (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: gnome-software (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: gnome-software (Ubuntu Disco) Importance: Undecided Status: New ** Also affects: gnome-software (Ubuntu Cosmic) Importance: Undecided Status: New ** Changed in: gnome-software (Ubuntu Disco) Status: New => Fix Released ** Changed in: gnome-software (Ubuntu Disco) Importance: Undecided => Medium ** Changed in: gnome-software (Ubuntu Cosmic) Importance: Undecided => Medium ** Changed in: gnome-software (Ubuntu Bionic) Importance: Undecided => Medium ** Changed in: gnome-software (Ubuntu Xenial) Importance: Undecided => Medium -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1815708 Title: Use ODRS for reviews Status in gnome-software package in Ubuntu: Fix Released Status in gnome-software source package in Xenial: New Status in gnome-software source package in Bionic: New Status in gnome-software source package in Cosmic: New Status in gnome-software source package in Disco: Fix Released Bug description: [Impact] The Ubuntu review server is being retired which will cause all Ubuntu package reviews to stop working. We are switching to using the Open Desktop Review Service (https://odrs.gnome.org/). This plugin has existed for sometime in the GNOME Software source, so it is well tested. This change will allow Snap packages to be reviewed (new feature). [Test Case] 1. Open GNOME Software 2. Select a popular app (e.g. Firefox) [Expected Result] Reviews are shown for this package. They will be different to the previous reviews. You are able to create reviews for both .deb and snap apps. [Regression Potential] There is a risk of new bugs encountered in the ODRS plugin. This has been enabled in Disco without major issue and has been used in other distributions for many releases. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1815708/+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 1688018] Re: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6
This is the *nastiest* bug I've ever encountered in the wild on my own in Linux (that has no good solution after this long). Package 1.2.2-0ubuntu0.16.04.4 has disappeared from the mirrors for Xenial (not that anyone should expect a normal user to go through the deep dive that is this subject, once one realizes what is happening). The cipher in use by AWS for Client VPN isn't available in OpenSSL within Trusty Tahr, so running an old Ubuntu distro is also not a viable solution for me. This is about as serious of a bug as I could think of, and we're almost two years in without it being addressed. Hate to be tin-foil-hatty, but this seems like the kind of thing that gets put into software as a result of government-agency interests. How many people around the world expecting their VPN to protect them while viewing content from outside of their nation state are DNS-leaking all over the place to their local ISP? How many companies are leaking private zone DNS names (which often reflect what's running on the target boxes, and would then include information that could be used as part of an attack vector) to their ISP? I understand how open source works, but most people (including me) don't have the ability to work effectively on this nuanced bug. What's the plan? Sorry to sound disgruntled, but I spent about a week on this (coming to terms with understanding the issue, and then trying a number of workarounds). Initially, I accused our CTO of running a broken VPN server (heh), because I could simply not believe that things didn't "just work" in Linux for this extremely common use case. So we don't support pushing "dhcp-option" for DNS in Linux. This works in Mac and in Windows. We need a working/easy way to update our DNS addresses upon connecting to/disconnected from a VPN that users can trust. This bug is so obscene, bwahah, I felt like Linus Torvalds dealing with Nvidia... :-P -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1688018 Title: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6 Status in network-manager package in Ubuntu: Triaged Status in network-manager source package in Xenial: In Progress Status in network-manager source package in Yakkety: Won't Fix Bug description: This was initially opened as #1671606 then later duped to #1639776. Discussion in #1639776 indicate that we need new bug for this so I am opening one ... Please don't mark this as duplicate to #1639776 or other similar bug report. We already lost several months and we are again at beginning ... TL;DR; -> network-manager-1.2.2-0ubuntu0.16.04.4 use DNS defined by VPN (correct). network-manager-1.2.6-0ubuntu0.16.04.1 use DNS from DHCP instead of one defined by VPN (wrong). DNS resolver should query only DNS servers defined by VPN while connection is active. = Test steps / result: - upgraded network-manager to 1.2.6-0ubuntu0.16.04.1 (dnsmasq-base-2.75-1ubuntu0.16.04.2) - restated my laptop to ensure clean start - connected to VPN using openconnect / network-manager-openconnect-gnome Observed results -> DNS queries are forwarded only to DNS servers defined by LAN connection (this is wrong / connection not working at all) - "killall dnsmasq" - dnsmasq get automatically restarted by system Observed results -> most of the the queries are forwarded to DNS servers defined by VPN, but lot of queries get forwarded to DNS servers defined by LAN connection (this is still wrong / DNS leaks, attacker can hijack connection even if VPN is enabled) - I downgraded back network-manager to 1.2.2-0ubuntu0.16.04.4 (dnsmasq-base stay same) - restated my laptop to ensure clean test - connected to same VPN using openconnect Observed results -> DNS queries are forwarded only to DNS servers defined by VPN connection. There are no leaks to LAN DNS server (this is correct behavior). = Paul Smith requested additional details in #1639776. Here are: * If you're using IPv4 vs. IPv6 -> IPv4 only. I have IPv6 set to ignore on all network definition (lan / wifi /vpn) * If you have checked or unchecked the "Use this connection only for resources on its network" -> unchecked on all nw definition * If you have this checked, try unchecking it and see if that makes a difference -> no change if I toggle this option. Behavior is same. * When you say "DNS lookups" please be clear about whether the hostnames being looked up are public (e.g., www.google.com or whatever), on your local LAN, or in the network accessed via the VPN. Does it make a difference which one you choose? -> No difference. * Are you using fully-qualified hostnames, or relying on the DNS domain search path? Does it make a difference if you do it differently? -> I normaly
[Desktop-packages] [Bug 1671606] Re: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6-0ubuntu0.16.04.1
*** This bug is a duplicate of bug 1688018 *** https://bugs.launchpad.net/bugs/1688018 This is the *nastiest* bug I've ever encountered in the wild on my own in Linux (that has no good solution after this long). Package 1.2.2-0ubuntu0.16.04.4 has disappeared from the mirrors for Xenial (not that anyone should expect a normal user to go through the deep dive that is this subject, once one realizes what is happening). The cipher in use by AWS for Client VPN isn't available in OpenSSL within Trusty Tahr, so running an old Ubuntu distro is also not a viable solution for me. This is about as serious of a bug as I could think of, and we're almost two years in without it being addressed. Hate to be tin-foil-hatty, but this seems like the kind of thing that gets put into software as a result of government-agency interests. How many people around the world expecting their VPN to protect them while viewing content from outside of their nation state are DNS-leaking all over the place to their local ISP? How many companies are leaking private zone DNS names (which often reflect what's running on the target boxes, and would then include information that could be used as part of an attack vector) to their ISP? I understand how open source works, but most people (including me) don't have the ability to work effectively on this nuanced bug. What's the plan? Sorry to sound disgruntled, but I spent about a week on this (coming to terms with understanding the issue, and then trying a number of workarounds). Initially I accused our CTO of running a broken VPN server (heh), because I could simply not believe that things didn't "just work" in Linux for this extremely common use case. So we don't support pushing "dhcp-option" for DNS in Linux. This works in Mac and in Windows. We need a working/easy way to update our DNS addresses upon connecting to/disconnected from a VPN that users can trust. This bug is so obscene, bwahah, I felt like Linus Torvalds dealing with Nvidia... :-P -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1671606 Title: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6-0ubuntu0.16.04.1 Status in network-manager package in Ubuntu: Confirmed Status in resolvconf package in Ubuntu: Invalid Bug description: I use my company's cisco vpn via network-manager in Ubuntu 16.04.2 LTS. After recent upgrade of network-manager:amd64 from version 1.2.2-0ubuntu0.16.04.4 to version 1.2.6-0ubuntu0.16.04.1 DNS resolution of VPN's server hostnames does not work. Roll back to version 1.2.2-0ubuntu0.16.04.4 solves the problem. Steps for reproducing: 1. upgrade network-manager:amd64 from version 1.2.2-0ubuntu0.16.04.4 to version 1.2.6-0ubuntu0.16.04.1 2. connect to VPN via network-manager applet 3. nslookop servername.internal --> ** server can't find servername.internal: NXDOMAIN 4. disconnect from VPN via network-manager applet 5. roll back network-manager via command: sudo apt-get install network-manager=1.2.2-0ubuntu0.16.04.4 6. restart network-manager via sudo service network-manager restart 7. connect to VPN via network-manager applet 8. nslookop servername.internal --> the server is resolved correctly ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.2.6-0ubuntu0.16.04.1 ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44 Uname: Linux 4.4.0-66-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: Unity Date: Thu Mar 9 19:49:55 2017 InstallationDate: Installed on 2015-10-05 (520 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.2.6connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1671606/+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 1812266] Re: Keyboard layout indicator does not indicate current layout (18.04 Bionic beaver)
hpp23, the fix is waiting for SRU review for some weeks now https://launchpad.net/ubuntu/bionic/+queue?queue_state=1_text=gnome-shell So we actually care of fixes, like we care about no regress in other things and so being a little conservative before releasing a new version. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1812266 Title: Keyboard layout indicator does not indicate current layout (18.04 Bionic beaver) Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell source package in Bionic: In Progress Status in gnome-shell source package in Cosmic: Fix Released Bug description: Upstream issue: https://gitlab.gnome.org/GNOME/gnome-shell/issues/913 [ Impact ] Keyboard Layout indicator don't display current layout (empty selected drop down box) [ Test case ] 1. Boot 2. Suspend or lock the screen 3. Log again with your user 4. The keyboard indicator should display current layout [ Regression Potential ] Really low, we properly pass a null value instead of an undefined one, without breaking JS. -- Steps to reproduce the bug: 1. After normal boot, suspend or lock. 2. Login again. Result: Keyboard Layout indicator don't display current layout (empty selected drop down box) [ Workarounds ] - Switch with keyboard (Super+space) or mouse. BUT if you then logout on the login screen *when you press the first character* of the password the shown selected keyboard layout resets. - Restart Gnome Shell (Alt+F2 r): https://wiki.gnome.org/Projects/GnomeShell/CheatSheet#Developer_tools - Also asked here https://askubuntu.com/q/1109555/349837 - Similar old bug https://bugs.launchpad.net/gnome-settings-daemon/+bug/531173 $ inxi -SG -! 31 -y80 && cat /etc/default/keyboard && localectl status System:Kernel: 4.15.0-43-generic x86_64 bits: 64 Desktop: Gnome 3.28.3 Distro: Ubuntu 18.04.1 LTS Graphics: Card-1: Intel HD Graphics 520 Card-2: NVIDIA GM108M [GeForce 940M] Display Server: x11 (X.Org 1.19.6 ) drivers: fbdev (unloaded: modesetting,vesa) Resolution: 1920x1080@60.00hz OpenGL: renderer: Mesa DRI Intel HD Graphics 520 (Skylake GT2) version: 4.5 Mesa 18.0.5 # KEYBOARD CONFIGURATION FILE # Consult the keyboard(5) manual page. XKBMODEL="pc105" XKBLAYOUT="es" XKBVARIANT="en" XKBOPTIONS="terminate:ctrl_alt_bksp" BACKSPACE="guess" System Locale: LANG=en_US.UTF-8 LC_NUMERIC=es_AR.UTF-8 LC_MONETARY=es_AR.UTF-8 LC_PAPER=es_AR.UTF-8 LC_NAME=es_AR.UTF-8 LC_ADDRESS=es_AR.UTF-8 LC_TELEPHONE=es_AR.UTF-8 LC_MEASUREMENT=es_AR.UTF-8 LC_IDENTIFICATION=es_AR.UTF-8 VC Keymap: n/a X11 Layout: es X11 Model: pc105 X11 Variant: en X11 Options: terminate:ctrl_alt_bksp To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1812266/+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 1815504] Re: Coordinate Yaru sound theme with GNOME 3.32 Alert Sound feature
I looked into this a bit and the feature worked differently than I thought. If you pick one of the 4 choices, it creates a __custom theme in ~/.local/share/sounds/ (derived from Yaru if Yaru is your selected sound theme) with just the alert sounds overriden. GNOME is looking for help in perhaps updating the the event sound choices here so there is room for Yaru contibutors to help there. https://gitlab.gnome.org/GNOME/gnome-control-center/issues/264 ** Changed in: gnome-control-center (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1815504 Title: Coordinate Yaru sound theme with GNOME 3.32 Alert Sound feature Status in gnome-control-center package in Ubuntu: Invalid Bug description: gnome-control-center 3.32 has a redesigned sound panel which makes the Alert Sound feature more prominent. Ubuntu's Yaru theme includes a sound theme but this isn't represented in the choices in that feature. I think some coordination is necessary here. I cross-filed this bug to https://github.com/ubuntu/yaru/issues/1175 See the attached screenshots. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1815504/+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 1815523] Re: The last MESA updates (02/07/19) corrupted output to DisplayLink
Not sure what happened, but I tried installing the HWE kernel, even those it's not entirely ready, but it did install the new video drivers and that solved it. ** Changed in: mesa (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1815523 Title: The last MESA updates (02/07/19) corrupted output to DisplayLink Status in mesa package in Ubuntu: Invalid Bug description: Prior to Thursday's "update" from Bionic-Proposed, the MESA was working fine; afterwards, gameplay on STEAM has become choppy and staccato; secondary display via a USB-C through DisplayPort UD3900 (Pluggable) is completely corrupted. See attached picture. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-15-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity:Unity7:ubuntu Date: Mon Feb 11 16:50:58 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: acpi-call, 1.1.0, 4.18.0-15-generic, x86_64: installedError! Could not locate dkms.conf file. File: does not exist. ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:3ea0] (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer Device [1558:1323] InstallationDate: Installed on 2019-01-15 (27 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: System76 Galago Pro ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-15-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/05/2018 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.03 dmi.board.asset.tag: Tag 12345 dmi.board.name: Galago Pro dmi.board.vendor: System76 dmi.board.version: galp3-c dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: System76 dmi.chassis.version: galp3-c dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.03:bd12/05/2018:svnSystem76:pnGalagoPro:pvrgalp3-c:rvnSystem76:rnGalagoPro:rvrgalp3-c:cvnSystem76:ct10:cvrgalp3-c: dmi.product.family: Not Applicable dmi.product.name: Galago Pro dmi.product.sku: Not Applicable dmi.product.version: galp3-c dmi.sys.vendor: System76 version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1815523/+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 1815694] Re: GLib-CRITICAL and does not start
** Also affects: inkscape Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to inkscape in Ubuntu. https://bugs.launchpad.net/bugs/1815694 Title: GLib-CRITICAL and does not start Status in Inkscape: New Status in inkscape package in Ubuntu: New Bug description: 1) I try: /snap/bin/inkscape 2) but terminal showed me: ** Gtk:ERROR:../../../../gtk/gtkiconhelper.c:494:ensure_surface_for_gicon: assertion failed (error == NULL): Icon 'image-missing' not present in theme Mint-Y (gtk-icon-theme-error-quark, 0) Emergency save activated! (inkscape:6503): GLib-CRITICAL **: 02:12:42.305: g_path_get_dirname: assertion 'file_name != NULL' failed Emergency save completed. Inkscape will close now. If you can reproduce this crash, please file a bug at www.inkscape.org with a detailed description of the steps leading to the crash, so we can fix it. Gtk-Message: 02:12:42.314: GtkDialog mapped without a transient parent. This is discouraged. 3) Application does not start 4) I use: Linux Mint 19, Cinnamon, 4.15.0-45-generic #48-Ubuntu SMP Tue Jan 29 16:28:13 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/inkscape/+bug/1815694/+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 1815694] Re: GLib-CRITICAL and dosent run
** Description changed: 1) I try: /snap/bin/inkscape 2) but terminal showed me: ** Gtk:ERROR:../../../../gtk/gtkiconhelper.c:494:ensure_surface_for_gicon: assertion failed (error == NULL): Icon 'image-missing' not present in theme Mint-Y (gtk-icon-theme-error-quark, 0) Emergency save activated! (inkscape:6503): GLib-CRITICAL **: 02:12:42.305: g_path_get_dirname: assertion 'file_name != NULL' failed Emergency save completed. Inkscape will close now. If you can reproduce this crash, please file a bug at www.inkscape.org with a detailed description of the steps leading to the crash, so we can fix it. Gtk-Message: 02:12:42.314: GtkDialog mapped without a transient parent. This is discouraged. + 3) Application does not start - 3) I use: Linux Mint 19, Cinnamon, 4.15.0-45-generic #48-Ubuntu SMP Tue Jan 29 16:28:13 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux + 4) I use: Linux Mint 19, Cinnamon, 4.15.0-45-generic #48-Ubuntu SMP Tue + Jan 29 16:28:13 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux ** Summary changed: - GLib-CRITICAL and dosent run + GLib-CRITICAL and does not start -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to inkscape in Ubuntu. https://bugs.launchpad.net/bugs/1815694 Title: GLib-CRITICAL and does not start Status in Inkscape: New Status in inkscape package in Ubuntu: New Bug description: 1) I try: /snap/bin/inkscape 2) but terminal showed me: ** Gtk:ERROR:../../../../gtk/gtkiconhelper.c:494:ensure_surface_for_gicon: assertion failed (error == NULL): Icon 'image-missing' not present in theme Mint-Y (gtk-icon-theme-error-quark, 0) Emergency save activated! (inkscape:6503): GLib-CRITICAL **: 02:12:42.305: g_path_get_dirname: assertion 'file_name != NULL' failed Emergency save completed. Inkscape will close now. If you can reproduce this crash, please file a bug at www.inkscape.org with a detailed description of the steps leading to the crash, so we can fix it. Gtk-Message: 02:12:42.314: GtkDialog mapped without a transient parent. This is discouraged. 3) Application does not start 4) I use: Linux Mint 19, Cinnamon, 4.15.0-45-generic #48-Ubuntu SMP Tue Jan 29 16:28:13 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/inkscape/+bug/1815694/+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 1815694] [NEW] GLib-CRITICAL and does not start
Public bug reported: 1) I try: /snap/bin/inkscape 2) but terminal showed me: ** Gtk:ERROR:../../../../gtk/gtkiconhelper.c:494:ensure_surface_for_gicon: assertion failed (error == NULL): Icon 'image-missing' not present in theme Mint-Y (gtk-icon-theme-error-quark, 0) Emergency save activated! (inkscape:6503): GLib-CRITICAL **: 02:12:42.305: g_path_get_dirname: assertion 'file_name != NULL' failed Emergency save completed. Inkscape will close now. If you can reproduce this crash, please file a bug at www.inkscape.org with a detailed description of the steps leading to the crash, so we can fix it. Gtk-Message: 02:12:42.314: GtkDialog mapped without a transient parent. This is discouraged. 3) Application does not start 4) I use: Linux Mint 19, Cinnamon, 4.15.0-45-generic #48-Ubuntu SMP Tue Jan 29 16:28:13 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux ** Affects: inkscape (Ubuntu) Importance: Undecided Status: New ** Tags: glib-critical -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to inkscape in Ubuntu. https://bugs.launchpad.net/bugs/1815694 Title: GLib-CRITICAL and does not start Status in inkscape package in Ubuntu: New Bug description: 1) I try: /snap/bin/inkscape 2) but terminal showed me: ** Gtk:ERROR:../../../../gtk/gtkiconhelper.c:494:ensure_surface_for_gicon: assertion failed (error == NULL): Icon 'image-missing' not present in theme Mint-Y (gtk-icon-theme-error-quark, 0) Emergency save activated! (inkscape:6503): GLib-CRITICAL **: 02:12:42.305: g_path_get_dirname: assertion 'file_name != NULL' failed Emergency save completed. Inkscape will close now. If you can reproduce this crash, please file a bug at www.inkscape.org with a detailed description of the steps leading to the crash, so we can fix it. Gtk-Message: 02:12:42.314: GtkDialog mapped without a transient parent. This is discouraged. 3) Application does not start 4) I use: Linux Mint 19, Cinnamon, 4.15.0-45-generic #48-Ubuntu SMP Tue Jan 29 16:28:13 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/inkscape/+bug/1815694/+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 1768291] Re: lirc is flooding the syslog with two lines each second
Same as what Chris mentioned. I occasionally use a Hauppauge 950Q USB device that has IR support on my laptop, but I don't keep it plugged in 24/7 since I frequently travel with this laptop. I don't want to mess around with scripts and disable services, so right now my "workaround" is to only install lirc when I want to use it, and uninstall it when I don't need it. The maintainer seems to assume that all IR devices are built in and connected 24/7 since he thinks the only a bad dependency can result in lirc being installed without an IR device connected so he sees nothing wrong with the syslog being spammed with messages about it. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lirc in Ubuntu. https://bugs.launchpad.net/bugs/1768291 Title: lirc is flooding the syslog with two lines each second Status in lirc package in Ubuntu: Triaged Bug description: Hello, in the syslog every second two lines are written: May 1 18:05:19 flupp lircd[1323]: lircd-0.10.0[1323]: Error: Cannot glob /sys/class/rc/rc0/input[0-9]*/event[0-9]* May 1 18:05:19 flupp lircd-0.10.0[1323]: Error: Cannot glob /sys/class/rc/rc0/input[0-9]*/event[0-9]* May 1 18:05:20 flupp lircd[1323]: lircd-0.10.0[1323]: Error: Cannot glob /sys/class/rc/rc0/input[0-9]*/event[0-9]* May 1 18:05:20 flupp lircd-0.10.0[1323]: Error: Cannot glob /sys/class/rc/rc0/input[0-9]*/event[0-9]* May 1 18:05:21 flupp lircd[1323]: lircd-0.10.0[1323]: Error: Cannot glob /sys/class/rc/rc0/input[0-9]*/event[0-9]* May 1 18:05:21 flupp lircd-0.10.0[1323]: Error: Cannot glob /sys/class/rc/rc0/input[0-9]*/event[0-9]* May 1 18:05:22 flupp lircd[1323]: lircd-0.10.0[1323]: Error: Cannot glob /sys/class/rc/rc0/input[0-9]*/event[0-9]* May 1 18:05:22 flupp lircd-0.10.0[1323]: Error: Cannot glob /sys/class/rc/rc0/input[0-9]*/event[0-9]* May 1 18:05:23 flupp lircd[1323]: lircd-0.10.0[1323]: Error: Cannot glob /sys/class/rc/rc0/input[0-9]*/event[0-9]* May 1 18:05:23 flupp lircd-0.10.0[1323]: Error: Cannot glob /sys/class/rc/rc0/input[0-9]*/event[0-9]* May 1 18:05:24 flupp lircd[1323]: lircd-0.10.0[1323]: Error: Cannot glob /sys/class/rc/rc0/input[0-9]*/event[0-9]* May 1 18:05:24 flupp lircd-0.10.0[1323]: Error: Cannot glob /sys/class/rc/rc0/input[0-9]*/event[0-9]* May 1 18:05:25 flupp lircd[1323]: lircd-0.10.0[1323]: Error: Cannot glob /sys/class/rc/rc0/input[0-9]*/event[0-9]* May 1 18:05:25 flupp lircd-0.10.0[1323]: Error: Cannot glob /sys/class/rc/rc0/input[0-9]*/event[0-9]* May 1 18:05:26 flupp lircd[1323]: lircd-0.10.0[1323]: Error: Cannot glob /sys/class/rc/rc0/input[0-9]*/event[0-9]* May 1 18:05:26 flupp lircd-0.10.0[1323]: Error: Cannot glob /sys/class/rc/rc0/input[0-9]*/event[0-9]* May 1 18:05:27 flupp lircd[1323]: lircd-0.10.0[1323]: Error: Cannot glob /sys/class/rc/rc0/input[0-9]*/event[0-9]* May 1 18:05:27 flupp lircd-0.10.0[1323]: Error: Cannot glob /sys/class/rc/rc0/input[0-9]*/event[0-9]* May 1 18:05:28 flupp lircd[1323]: lircd-0.10.0[1323]: Error: Cannot glob /sys/class/rc/rc0/input[0-9]*/event[0-9]* May 1 18:05:28 flupp lircd-0.10.0[1323]: Error: Cannot glob /sys/class/rc/rc0/input[0-9]*/event[0-9]* This is not only annoying as it makes it difficult to use the syslog for checking the system, but also it writes too much data into the log (18MB each day). Also it keeps the hard disc awaken what is bad for standby. Kubuntu 18.04 ii liblirc-client0:amd64 0.10.0-2 amd64infra-red remote control support - client library ii liblirc0:amd640.10.0-2 amd64Infra-red remote control support - Run-time libraries ii lirc 0.10.0-2 amd64Infra-red remote control support - daemons and utils I do not have infrared remote control hardware. But I cannot purge the packages as other packages I want to keep would be removed as well. Deactivating the services in systemd does not help (or I am doing something wrong?) Greetings Gert To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lirc/+bug/1768291/+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 1815693] [NEW] Kubuntu 18.10 Xorg severe memory leak
Public bug reported: Suddenly sometimes during the past two weeks my kubuntu installation has started to freeze up. I can't remember what apt upgrade that caused it, and I have done several the last few days hoping for it to be resolved. I didn't know what was causing it as I hadn't made any other changes expect for the odd apt upgrade. Before that I had just finished a several weeks long session of intense work around the clock without having to reboot even once. Suddenly it is now freezing up within hours. Even without doing anything, just leaving the computer alone. However, yesterday I accidentally discovered that my RAM was filled up. More than filled up, even all swap was full. And before I could close anything down it froze up again. So TLDR; I have today logged the memory consumption while I was handling some bills and linked is a log of constantly increasing Xorg memory usage. So it goes until it chokes the machine and only a hard reboot is possible. My installed RAM is 10GB. Swap is 6GB. Please refer to the linked file to see how the Xorg usage creeps up. https://www.dropbox.com/s/nf1ev2dxdl..._leak.log?dl=0 Please advise what additional information I should post to have this resolved. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.18.0-15.16-generic 4.18.20 Uname: Linux 4.18.0-15-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: KDE Date: Wed Feb 13 01:00:13 2019 DistUpgraded: 2019-02-09 11:54:01,040 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: cosmic DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller]) Subsystem: VMware SVGA II Adapter [15ad:0405] InstallationDate: Installed on 2015-10-22 (1209 days ago) InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 003: ID 80ee:0021 VirtualBox USB Tablet Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-15-generic root=UUID=8959cd47-b52f-4a6e-97bb-5d509e3c2480 ro quiet splash Renderer: Software SourcePackage: xorg UpgradeStatus: Upgraded to cosmic on 2019-02-09 (3 days ago) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic ubuntu ** Attachment added: "Memory usage increase log over a few hours" https://bugs.launchpad.net/bugs/1815693/+attachment/5238125/+files/xorg_leak.log -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1815693 Title: Kubuntu 18.10 Xorg severe memory leak Status in xorg package in Ubuntu: New Bug description: Suddenly sometimes during the past two weeks my kubuntu installation has started to freeze up. I can't remember what apt upgrade that caused it, and I have done several the last few days hoping for it to be resolved. I didn't know what was causing it as I hadn't made any other changes expect for the odd apt upgrade. Before that I had just finished a several weeks long session of intense work around the clock without having to reboot even once. Suddenly it is now freezing up within hours. Even without doing anything, just leaving the computer alone. However, yesterday I accidentally discovered that my RAM was filled up. More than filled up, even all swap was full. And before I could close anything down it froze up again. So TLDR; I have
[Desktop-packages] [Bug 1768597] Re: [needs-packaging] package filemanager-actions missing
filemanager-actions will be available in Ubuntu 19.04 which will be released in April. ** Package changed: nautilus (Debian) => filemanager-actions (Debian) ** Package changed: nautilus-actions (Ubuntu) => filemanager-actions (Ubuntu) ** Changed in: filemanager-actions (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1768597 Title: [needs-packaging] package filemanager-actions missing Status in filemanager-actions package in Ubuntu: Fix Released Status in nautilus package in Ubuntu: Invalid Status in filemanager-actions package in Debian: New Bug description: nautilus-actions was deprecated in favour of filemanager-actions (see https://github.com/GNOME/nautilus-actions ). But 18.04 repositories do not have either of the packages. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/filemanager-actions/+bug/1768597/+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 1814949] Re: gnome-control-center refuses to open if you try to open the Details panels
** Tags removed: third-party-packages ** Tags added: rls-dd-incoming -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1814949 Title: gnome-control-center refuses to open if you try to open the Details panels Status in gnome-control-center package in Ubuntu: Triaged Bug description: Workaround == Run this command in your terminal: gsettings reset org.gnome.ControlCenter last-panel and then avoid opening the Details panels Issue = If you try to open the Details panel, gnome-control-center will crash. It will then refuse to open. Upstream Bug Report === https://gitlab.gnome.org/GNOME/gnome-control-center/issues/285 See also https://gitlab.gnome.org/GNOME/gnome-control-center/merge_requests/387 Original Bug Report === Segmentation fault while trying to run via cli , the gnome setting doesn't working when click on setting menu ProblemType: Crash DistroRelease: Ubuntu 19.04 Package: gnome-control-center 1:3.30.2-4ubuntu2 ProcVersionSignature: Ubuntu 4.19.0-12.13-generic 4.19.18 Uname: Linux 4.19.0-12-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.10-0ubuntu20 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Feb 1 14:38:32 2019 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2017-05-04 (643 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170503) ProcCmdline: gnome-control-center SegvAnalysis: Segfault happened at: 0x7f783f52232d <__GI___libc_free+29>: mov -0x8(%rdi),%rax PC (0x7f783f52232d) ok source "-0x8(%rdi)" (0xfff8) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: gnome-control-center StacktraceTop: __GI___libc_free (mem=0x1) at malloc.c:3085 g_unix_mount_free () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 () () g_type_create_instance () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: gnome-control-center crashed with SIGSEGV in __GI___libc_free() UpgradeStatus: Upgraded to disco on 2018-11-06 (92 days ago) UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1814949/+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 1797524] Re: Confusing notification
Ok, let's close the bug then. It could have been a side effect of adding a printer in settings which has a weird workflow/is a known issue ** Changed in: gnome-software (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1797524 Title: Confusing notification Status in gnome-software package in Ubuntu: Invalid Bug description: Ubuntu 18.04 I've got a strange notification. See the screenshot attached. It's in Polish. In English it would be something like that: "Extra drivers needed... Application Application needs extra drivers" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1797524/+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 1640541] Re: nautilus shows Windows Network but fails to open it
** Changed in: nautilus (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1640541 Title: nautilus shows Windows Network but fails to open it Status in nautilus package in Ubuntu: New Bug description: 1. Open Nautilus 2. Click 'Other Locations' in the sidebar 3. Click 'Windows Network' Expectation: - a list of local servers with Samba shares Actual result: - nothing happens for a while, then a popup saying "Could not get list of shares from the server: No such file or directory" (I'm translating back from lt_LT) journalctl shows these errors: nautilus[8942]: Called "net usershare info" but it failed: Nepavyko paleisti antrinio proceso „net“ (Toks failas ar aplankas neegzistuoja) gvfsd[5799]: mkdir failed on directory /var/cache/samba: Permission denied gvfsd[5799]: dbus_mount_reply: Error from org.gtk.vfs.Mountable.mount(): Nepavyko iš serverio gauti viešinių sąrašo: Toks failas ar aplankas neegzistuoja The samba-common package is not installed (nautilus Recommends gvfs- backends which Suggests samba-common). It would be nice if Nautilus asked me to install samba-common via packagekit or something instead of just failing. (Although just 'samba-common' appears to be insufficient; I still can't browse the Windows Network in Nautilus after I 'apt install samba-common'.) ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: nautilus 1:3.20.3-1ubuntu3.1 ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0 Uname: Linux 4.8.0-26-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Nov 9 18:39:50 2016 GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' b"'890x464+362+407'" InstallationDate: Installed on 2016-09-10 (60 days ago) InstallationMedia: Ubuntu-GNOME 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160720) SourcePackage: nautilus UpgradeStatus: Upgraded to yakkety on 2016-10-15 (25 days ago) usr_lib_nautilus: gnome-terminal 3.20.2-1ubuntu5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1640541/+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 1815480] Re: “Extract Here” only creates empty files (0 bytes) for .zip files created by ownCloud
Is there anything specific I should do? Just extracting the file in Nautilus doesn’t generate any entries in journalctl. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1815480 Title: “Extract Here” only creates empty files (0 bytes) for .zip files created by ownCloud Status in nautilus package in Ubuntu: Incomplete Bug description: For any .zip archive generated by the ownCloud software, it seems that extracting the files using Nautilus results in correctly-named directories/files to be created, but all files are actually empty (0 bytes). The archive can be extracted without issues using file-roller, unzip or 7z: $ unzip -t test.zip Archive: test.zip testing: test/OK testing: test/f1.txt OK testing: test/f2.txt OK testing: test/f3.txt OK No errors detected in compressed data of test.zip. $ unzip test Archive: test.zip creating: test/ extracting: test/f1.txt extracting: test/f2.txt extracting: test/f3.txt $ 7z x test.zip 7-Zip [64] 16.02 : Copyright (c) 1999-2016 Igor Pavlov : 2016-05-21 p7zip Version 16.02 (locale=en_US.UTF-8,Utf16=on,HugeFiles=on,64 bits,4 CPUs Intel(R) Core(TM) i5-5200U CPU @ 2.20GHz (306D4),ASM,AES-NI) Scanning the drive for archives: 1 file, 8656 bytes (9 KiB) Extracting archive: test.zip -- Path = test.zip Type = zip Physical Size = 8656 64-bit = + Everything is Ok Folders: 1 Files: 3 Size: 7850 Compressed: 8656 Expected behavior: Download the attached file “test.zip”, right-click the file in Nautilus and choose “Extract Here”. A directory “test” containing three non-empty files “f1.txt”, “f2.txt” and “f3.txt” should be created. Actual behavior: All three files are empty (0 bytes). Nautilus version: 1:3.26.4-0ubuntu7.1 (cosmic) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1815480/+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 1791409] Re: LIRC not working on Ubuntu 18.04
What's the issue exactly? That the package doesn't show a text interface to configure things anymore? That seems the same than bug #1788235 which has been closed as not being a bug @Alec, the issue you are referring to is different right? ** Changed in: lirc (Ubuntu) Importance: Undecided => High ** Changed in: lirc (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lirc in Ubuntu. https://bugs.launchpad.net/bugs/1791409 Title: LIRC not working on Ubuntu 18.04 Status in lirc package in Ubuntu: Incomplete Bug description: It appears that the LIRC 0.10.0-2 package for Ubuntu 18.04 (bionic) is not working correctly. The usual configuration menu to select your remote does not come up after installing the package. Saw some other mentions of this issue as well on the forums: https://ubuntuforums.org/showthread.php?t=2396923 This handy blog post shows a workaround of installing an older version (0.9.0) from xenial to get it to work: https://twosortoftechguys.wordpress.com/2018/07/24/make-lirc-work-in- ubuntu-18-04/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lirc/+bug/1791409/+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 1815271] Re: Should show old package version
Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem. We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures. At a minimum, we need: 1. The specific steps or actions you took that caused you to encounter the problem. 2. The behavior you expected. 3. The behavior you actually encountered (in as much detail as possible). Thanks! ** Changed in: gnome-software (Ubuntu) Importance: Undecided => Low ** Changed in: gnome-software (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1815271 Title: Should show old package version Status in gnome-software package in Ubuntu: Incomplete Bug description: When clicking a .deb file, it should also show the old version if an old version of the package was already installed. It should also apply to packages to be installed from repositories (not sure if this already works). ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: ubuntu-software 3.30.2-0ubuntu8 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Feb 9 09:49:19 2019 InstallationDate: Installed on 2018-06-23 (230 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-limba N/A gnome-software-plugin-snap3.30.2-0ubuntu8 PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IL SHELL=/bin/bash SourcePackage: gnome-software UpgradeStatus: Upgraded to cosmic on 2018-10-20 (111 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1815271/+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 437288] Re: Nautilus uses a lot of heap memory coping large amounts of data
Thanks for the update, closing the bug then ** Changed in: nautilus (Ubuntu) Status: Incomplete => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/437288 Title: Nautilus uses a lot of heap memory coping large amounts of data Status in Nautilus: New Status in nautilus package in Ubuntu: Fix Released Bug description: Binary package hint: nautilus While copying a lot of data (>250GB), Nautilus uses up a lot of memory. This memory is not given back to the system at any time. Depending on the amount of copying Nautilus uses from 800MB up to 3GB. Now using Ubuntu alpha 6 with Gnome 2.28, but this problemed also showed on my old install (Arch Linux Gnome 2.26) I attached a printscreen of the memory in the .png. Memory in use that time: 2.4GB. Amount of data copied (not cutted) was about 750GB. ProblemType: Bug Architecture: amd64 Date: Sat Sep 26 19:20:11 2009 DistroRelease: Ubuntu 9.10 NonfreeKernelModules: nvidia Package: nautilus 1:2.28.0-0ubuntu2 ProcEnviron: LANG=nl_NL.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-11.36-generic SourcePackage: nautilus Uname: Linux 2.6.31-11-generic x86_64 To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/437288/+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 1814481] Re: bluetooth keyboard not working
** Package changed: xorg (Ubuntu) => bluez (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1814481 Title: bluetooth keyboard not working Status in bluez package in Ubuntu: Confirmed Bug description: I recently got a nice mechanical bluetooth keyboard to use on my thinkpad. It works fine with Android, Windows 10 and Xubuntu 19.04 live, but on my installed xubuntu 18.04, 18.04 live and 18.10 live it only works after calling `sudo evtest /dev/input/eventN`. Xorg.0.log shows it is detected fine, and I can't see anything there after temporarily getting it to work using the evtest trick. 18.515] (II) config/udev: Adding input device Keychron K1 (/dev/input/event23) [18.515] (**) Keychron K1: Applying InputClass "libinput keyboard catchall" [18.515] (II) Using input driver 'libinput' for 'Keychron K1' [18.515] (**) Keychron K1: always reports core events [18.515] (**) Option "Device" "/dev/input/event23" [18.515] (**) Option "_source" "server/udev" [18.516] (II) event23 - Keychron K1: is tagged by udev as: Keyboard [18.516] (II) event23 - Keychron K1: device is a keyboard [18.516] (II) event23 - Keychron K1: device removed [18.524] (II) libinput: Keychron K1: needs a virtual subdevice [18.524] (**) Option "config_info" "udev:/sys/devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:0255.0007/input/input24/event23" [18.524] (II) XINPUT: Adding extended input device "Keychron K1" (type: MOUSE, id 20) [18.524] (**) Option "AccelerationScheme" "none" [18.524] (**) Keychron K1: (accel) selected scheme none/0 [18.524] (**) Keychron K1: (accel) acceleration factor: 2.000 [18.524] (**) Keychron K1: (accel) acceleration threshold: 4 [18.524] (II) event23 - Keychron K1: is tagged by udev as: Keyboard [18.524] (II) event23 - Keychron K1: device is a keyboard [18.524] (**) Keychron K1: Applying InputClass "libinput keyboard catchall" [18.524] (II) Using input driver 'libinput' for 'Keychron K1' [18.524] (**) Keychron K1: always reports core events [18.524] (**) Option "Device" "/dev/input/event23" [18.524] (**) Option "_source" "_driver/libinput" [18.524] (II) libinput: Keychron K1: is a virtual subdevice [18.524] (**) Option "config_info" "udev:/sys/devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:0255.0007/input/input24/event23" [18.524] (II) XINPUT: Adding extended input device "Keychron K1" (type: KEYBOARD, id 21) [18.524] (**) Option "xkb_model" "pc105" [18.524] (**) Option "xkb_layout" "us" [18.524] (**) Option "xkb_variant" "altgr-intl" [18.524] (WW) Option "xkb_options" requires a string value I've also tried using the latest 4.20.6 from mainline-ppa and the latest bluetooth/bluz ppa without success. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-45.48-lowlatency 4.15.18 Uname: Linux 4.15.0-45-lowlatency x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE Date: Sun Feb 3 23:51:29 2019 DistUpgraded: 2019-02-03 21:49:33,752 DEBUG /openCache(), new cache size 92675 DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: virtualbox, 5.2.18, 4.15.0-45-lowlatency, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 620 [17aa:224b] InstallationDate: Installed on 2017-07-24 (559 days ago) InstallationMedia: Xubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215) MachineType: LENOVO 20HFCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-lowlatency root=UUID=8f8366ae-4d29-44cf-9b85-f83f1771eab1 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2019-02-03 (0 days ago) dmi.bios.date: 09/14/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N1WET51W (1.30 ) dmi.board.asset.tag: Not Available dmi.board.name: 20HFCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1WET51W(1.30):bd09/14/2018:svnLENOVO:pn20HFCTO1WW:pvrThinkPadT470s:rvnLENOVO:rn20HFCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T470s dmi.product.name: 20HFCTO1WW dmi.product.version: ThinkPad T470s dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri:
[Desktop-packages] [Bug 1813432] Re: Specific PDF file fails to print to HP m551dn printer
** Changed in: cups (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1813432 Title: Specific PDF file fails to print to HP m551dn printer Status in cups package in Ubuntu: New Bug description: One particular PDF file is failing to print. I have no idea why. When I say failing to print I mean that my computer thinks the file printed but the printer shows no sign of ever having received it. The display of the printer never changes to show that it is receiving or printing a file, and the job log of the printer doesn't show that it was received either. I also checked the printer event log and it doesn't show any events at the time I attempted to print the file. Unfortunately I can't attach the PDF file itself because it contains private information, and I can't find another PDF that exhibits this problem. I even tried generating a new PDF exactly the same way the old one was generated -- with the scan to email PDF function on my scanner -- and the new PDF prints just fine. I tried uploading the PDF directly to the printer with FTP and it prints just fine that way. I enabled CUPS debug mode before attempting to print the file. Attached is the resulting contents of /var/log/cups/error_log. I wish I knew what was going on here but honestly I have no idea. Perhaps you can learn something from the error_log. I hope so. Other files, including other PDFs, do print. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: cups 2.2.10-3 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu19 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Jan 26 17:47:49 2019 InstallationDate: Installed on 2019-01-02 (24 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Lpstat: device for duplex: socket://m551dn.kamens.brookline.ma.us:9100 device for HP_LaserJet_500_color_M551_1637DA_: ipps://m551dn.local:443/ipp/print device for simplex: socket://m551dn.kamens.brookline.ma.us:9100 MachineType: Acer Predator G6-710 Papersize: letter PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/simplex.ppd', '/etc/cups/ppd/HP_LaserJet_500_color_M551_1637DA_.ppd', '/etc/cups/ppd/duplex.ppd'] failed with exit code 2: grep: /etc/cups/ppd/simplex.ppd: Permission denied grep: /etc/cups/ppd/HP_LaserJet_500_color_M551_1637DA_.ppd: Permission denied grep: /etc/cups/ppd/duplex.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-13-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 SourcePackage: cups UpgradeStatus: Upgraded to disco on 2019-01-21 (5 days ago) dmi.bios.date: 05/18/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: R01-A4 dmi.board.name: Predator G6-710 dmi.board.vendor: Acer dmi.chassis.type: 3 dmi.chassis.vendor: Acer dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrR01-A4:bd05/18/2016:svnAcer:pnPredatorG6-710:pvr:rvnAcer:rnPredatorG6-710:rvr:cvnAcer:ct3:cvr: dmi.product.family: Acer Desktop dmi.product.name: Predator G6-710 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1813432/+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 1815323] Re: After Cheese update does not work
** Package changed: tracker (Ubuntu) => cheese (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cheese in Ubuntu. https://bugs.launchpad.net/bugs/1815323 Title: After Cheese update does not work Status in cheese package in Ubuntu: New Bug description: Hello guys After updating the version of Cheese 3.31.90-1 on Ubuntu Disk 19.04 this week it stopped working and the following error message appears as attached image. obs: The guvcview works normally and opens the webcam, since the cheese has failed. Here's the error message when opening the cheese from the terminal: edson@edson-p6540br:~$ cheese (cheese:13425): Clutter-WARNING **: 01:33:18.872: Whoever translated default:LTR did so wrongly. (cheese:13425): GStreamer-CRITICAL **: 01:33:19.200: gst_object_ref: assertion 'object != NULL' failed (cheese:13425): GStreamer-CRITICAL **: 01:33:19.200: gst_object_ref: assertion 'object != NULL' failed (cheese:13425): GStreamer-CRITICAL **: 01:33:19.200: gst_object_ref: assertion 'object != NULL' failed (cheese:13425): GStreamer-CRITICAL **: 01:33:19.204: gst_bin_add: assertion 'GST_IS_ELEMENT (element)' failed (cheese:13425): GStreamer-CRITICAL **: 01:33:19.204: gst_element_link_pads_full: assertion 'GST_IS_ELEMENT (dest)' failed (cheese:13425): GStreamer-CRITICAL **: 01:33:19.204: gst_element_get_static_pad: assertion 'GST_IS_ELEMENT (element)' failed (cheese:13425): GStreamer-CRITICAL **: 01:33:19.204: gst_ghost_pad_new: assertion 'GST_IS_PAD (target)' failed (cheese:13425): GStreamer-CRITICAL **: 01:33:19.204: gst_element_add_pad: assertion 'GST_IS_PAD (pad)' failed (cheese:13425): GStreamer-CRITICAL **: 01:33:19.204: gst_object_unref: assertion 'object != NULL' failed (cheese:13425): cheese-CRITICAL **: 01:33:19.206: cheese_camera_set_error_element_not_found: assertion 'error == NULL || *error == NULL' failed ** Message: 01:33:19.206: cheese-application.vala:211: Error during camera setup: Um ou mais elementos necessários do GStreamer estão faltando: Um ou mais elementos necessários do GStreamer estão faltando: effects_valve. (cheese:13425): GStreamer-CRITICAL **: 01:33:19.229: gst_bin_add: assertion 'GST_IS_ELEMENT (element)' failed (cheese:13425): GStreamer-CRITICAL **: 01:33:19.229: gst_element_link_pads_full: assertion 'GST_IS_ELEMENT (dest)' failed (cheese:13425): GStreamer-CRITICAL **: 01:33:19.230: gst_element_get_static_pad: assertion 'GST_IS_ELEMENT (element)' failed (cheese:13425): GStreamer-CRITICAL **: 01:33:19.230: gst_ghost_pad_new: assertion 'GST_IS_PAD (target)' failed (cheese:13425): GStreamer-CRITICAL **: 01:33:19.230: gst_element_add_pad: assertion 'GST_IS_PAD (pad)' failed (cheese:13425): GStreamer-CRITICAL **: 01:33:19.230: gst_object_unref: assertion 'object != NULL' failed *** Olá Pessoal Após atualização da versão do Cheese 3.31.90-1 no Ubuntu Disco 19.04 esta semana o mesmo deixou de funcionar e aparece a seguinte mensagem de erro conforme imagem em anexo. obs: O guvcview funciona normalmente e abre a webcam, já o cheese falhou. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cheese/+bug/1815323/+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 1815354] Re: BCM 43142 driver not installed - no WiFi
That's not really n-m's fault if the driver is missing... ** Package changed: network-manager (Ubuntu) => ubuntu-drivers-common (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1815354 Title: BCM 43142 driver not installed - no WiFi Status in ubuntu-drivers-common package in Ubuntu: New Bug description: Disco daily Lubuntu 09.02.2019 and Disco daily Kubuntu 10.02.2019 BCM 43142 drivers not installed resulting in no WiFi during and after installation. I was able to attach ethernet cable and use the command line "ubuntu- drivers" command to install the drivers and all worked well after that. Of course if running a machine with no ethernet then this is a huge problem for the user. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1815354/+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 1815378] Re: gvfs spins up sleeping HDD even if all partitions unmounted
Thank you for your bug report, could you maybe report it as well to the gvfs upstream gitlab? https://gitlab.gnome.org/GNOME/gvfs/issues ** Changed in: gvfs (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1815378 Title: gvfs spins up sleeping HDD even if all partitions unmounted Status in gvfs package in Ubuntu: New Bug description: Hi, On my laptop I use : * a SSD for boot and all tasks * a HDD for storing big files The HDD is spun down at startup and the corresponding filesystem is unmounted. I succeed in disabling all services making the HDD periodically wake up. The only problem is that this HDD spins up when I launch thunar for the first time. If I close thunar, spin down the disk, then launch thunar again, the disk stays in sleep mode... I found this thread without answer talking about the same issue : https://forum.xfce.org/viewtopic.php?id=11270 Is there a way to disable thunar first access to umounted partition ? --- I first reported this bug here : https://bugzilla.xfce.org/show_bug.cgi?id=14998 I investigated with help from thunar developers and it appears that this bug is coming from gvfs, because it desapear when I remove gvfs and use thunar without gvfs extension, and it exists also for nautilus (other soft using gvfs). Thank you for your help. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1815378/+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 1815395] Re: GVFS-SMB write problems to SMB2 shares
Thanks for the detailled bug, maybe it would be better if you reported that directly upstream to the people writing the code though https://gitlab.gnome.org/GNOME/gvfs/issues ** No longer affects: ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1815395 Title: GVFS-SMB write problems to SMB2 shares Status in gvfs package in Ubuntu: New Bug description: Summary: I believe there’s a bug in GVFS-SMB (or its implementation in Nautilus) that manifests when writing to SMB2 shares. It occurs inconsistently (but enough to be annoying) in everyday use, but it can be replicated consistently with a simple echo command redirected to a file on the share. This doesn’t happen when using the ‘mount’ command to connect to SMB2 shares. It also doesn’t happen when making an SMB1 connection through Nautilus OR mount. I’ve also tested this against 2 different SMB servers (a Synology DS216J and a share on a Win7 Pro system) and the results are consistent so I don’t believe it’s a server side issue. I don’t know enough about this part of the system to identify where the issue is or fix it, but I’ve included data below to show the basis for my assertions above. The workaround is either going back to SMB1 or mounting my shares with the mount command, but I was hoping someone could take this on and fix it long-term. As Microsoft progressively phases out SMB1, I think this will eventually become a wider scale problem so now would be an opportune time to address it. If there’s any further data I can provide, please let me know. Also, I’m sorry this bug report is so long, but I’m erring on the side of too much detail rather than too little. Detail: On my Ubuntu 18.04 system, when I attempt to echo a string into a file on a GVFS mounted share (left hand nav of Nautilus + Other Locations) and that share is configured to SMB1 (client side left to negotiate, server side locked to SMB1) this works as expected. I tested against SMB shares on both a Synology Diskstation DS216J NAS and a Windows 7 Professional workstation. When I was on Ubuntu 16.04 that was SMB1 only out of the box I didn’t know this problem even existed. Now that I’m on Ubuntu 18.04 and my share was willing to make connection at SMB2 I started to have weird, inconsistent disk problems. Much troubleshooting and analysis later, I can recreate this issue consistently with a simple echo command to a file on the share. To the SMB share on a Synology Diskstation NAS set to SMB1: echo "This is a test." > /run/user/1000/gvfs/smb- share\:server\=diskstation\,share\=fileshare/Test-File-SMB1-GVFS- NAS.txt The command executes with no feedback (other than the return of the prompt awaiting the next command) and the file of the name specified with the contents specified appears at the root of the NAS file share. To the SMB share on a Windows 7 Professional workstation set to SMB1: echo "This is a test." > /run/user/1000/gvfs/smb- share\:server\=hp_laptop\,share\=videos/Test-File-SMB1-GVFS-Win7.txt The command also executes with no feedback (other than the return of the prompt awaiting the next command) and the file of the name specified with the contents specified appears at the root of the “videos” file share on the Win7 workstation. I also took PCAPs of this occurring (attached). What they show is about what I would expect for this operation. Client SMB pings the server in packet 1 who responds in packet 2, queries info on the folder in packet 4 and gets some basic info back in packet 5, queries the filename (to make sure it doesn’t already exist) several times (not sure why), each time getting a name not found reply in packets 6 through 17, then creates the file in packet 18, gets back a success message in packet 19, queries info on the new file in packet 20, gets a success response in packet 21, writes the contents in packet 22, gets a good response in packet 23, queries the file one more time (presumably to make sure the new size is good) in packet 24, gets a response with the info in packet 25, requests the handle be closed in packet 26, and gets an OK to that in packet 27. This is all wonderful. Perhaps slightly inefficient, but I don’t know what’s going on under the hood, so who am I to judge? When I switch to SMB2 on the server side and reconnect via GVFS using Nautilus, things fall apart. To the SMB share on a Synology Diskstation NAS set to SMB2: echo "This is a test." > /run/user/1000/gvfs/smb- share\:server\=diskstation\,share\=fileshare/Test-File-SMB2-GVFS- NAS.txt returns bash: /run/user/1000/gvfs/smb-share:server=diskstation,share=fileshare /Test-File-SMB2-GVFS-NAS.txt: Invalid argument The file is where I expected it, but it is 0 bytes. To the SMB share on a Windows 7
[Desktop-packages] [Bug 1646403] Re: Error message when clicking "Windows Network" needs to be improved
Right, the error is a problem that should be fixed, maybe you can open another bug about the fact that it's failing to list shares too? Could you give the output of those commands? $ nmblookup -M -- - $ nmblookup -M workgroup $ smbtree It looks like the server handling the group is refusing the connection? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1646403 Title: Error message when clicking "Windows Network" needs to be improved Status in nautilus package in Ubuntu: New Bug description: After opening Files, clicking "Other locations" in the sidebar, and clicking the Windows Network icon, I get an error dialog, saying: > Unable to access location > > Failed to retrieve share list from server: No such file or directory Regardless of what is causing the error, there needs to be a better error message. I got the same error message before installing `samba` and now I still get it. The error message should help me discover what is happening and how to fix it. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: nautilus 1:3.20.3-1ubuntu3.1 ProcVersionSignature: Ubuntu 4.8.0-28.30-generic 4.8.6 Uname: Linux 4.8.0-28-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Thu Dec 1 10:11:50 2016 GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' b"'1431x799+309+79'" SourcePackage: nautilus UpgradeStatus: Upgraded to yakkety on 2016-10-13 (48 days ago) usr_lib_nautilus: dropbox2015.10.28 gnome-terminal 3.20.2-1ubuntu5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1646403/+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 1815480] Re: “Extract Here” only creates empty files (0 bytes) for .zip files created by ownCloud
Thank you for your bug report, can you add your journalctl log after triggering the issue? The example attached to the bug extracts fine here, using nautilus or bsdtar from libarchive-tools (libarchive is what nautilus uses as a backend) ** Changed in: nautilus (Ubuntu) Importance: Undecided => Low ** Changed in: nautilus (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1815480 Title: “Extract Here” only creates empty files (0 bytes) for .zip files created by ownCloud Status in nautilus package in Ubuntu: Incomplete Bug description: For any .zip archive generated by the ownCloud software, it seems that extracting the files using Nautilus results in correctly-named directories/files to be created, but all files are actually empty (0 bytes). The archive can be extracted without issues using file-roller, unzip or 7z: $ unzip -t test.zip Archive: test.zip testing: test/OK testing: test/f1.txt OK testing: test/f2.txt OK testing: test/f3.txt OK No errors detected in compressed data of test.zip. $ unzip test Archive: test.zip creating: test/ extracting: test/f1.txt extracting: test/f2.txt extracting: test/f3.txt $ 7z x test.zip 7-Zip [64] 16.02 : Copyright (c) 1999-2016 Igor Pavlov : 2016-05-21 p7zip Version 16.02 (locale=en_US.UTF-8,Utf16=on,HugeFiles=on,64 bits,4 CPUs Intel(R) Core(TM) i5-5200U CPU @ 2.20GHz (306D4),ASM,AES-NI) Scanning the drive for archives: 1 file, 8656 bytes (9 KiB) Extracting archive: test.zip -- Path = test.zip Type = zip Physical Size = 8656 64-bit = + Everything is Ok Folders: 1 Files: 3 Size: 7850 Compressed: 8656 Expected behavior: Download the attached file “test.zip”, right-click the file in Nautilus and choose “Extract Here”. A directory “test” containing three non-empty files “f1.txt”, “f2.txt” and “f3.txt” should be created. Actual behavior: All three files are empty (0 bytes). Nautilus version: 1:3.26.4-0ubuntu7.1 (cosmic) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1815480/+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 1607696] Re: Version string missing in libjpeg.pc
Confirmed, the problem is with the sed added in
http://launchpadlibrarian.net/241403193/libjpeg-
turbo_1.4.2-0ubuntu2_1.4.2-0ubuntu3.diff.gz
sed -e "s/@VERSION@/$(VERSION)/
But ${VERSION} is not defined
** Changed in: libjpeg-turbo (Ubuntu)
Importance: Undecided => Low
** Changed in: libjpeg-turbo (Ubuntu)
Assignee: (unassigned) => Matthias Klose (doko)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libjpeg-turbo in Ubuntu.
https://bugs.launchpad.net/bugs/1607696
Title:
Version string missing in libjpeg.pc
Status in libjpeg-turbo package in Ubuntu:
Confirmed
Bug description:
Proper pkg-config files are installed if I build libjpeg-turbo myself.
The description in the pkg-config file shipped by Ubuntu is also
different from what is in upstream so I assume this is caused by
Ubuntu (/Debian?) patching in a custom pkg-config file before they
were included upstream in https://github.com/libjpeg-turbo/libjpeg-
turbo/pull/53 .
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libjpeg-turbo/+bug/1607696/+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 1815686] [NEW] Seahorse won't show any importet PGP keys
Public bug reported: Upon importing various private and public keys manually, I notice that none of them show up in the section GNUpgp keys no matter what I choose under view. Maybe this is related to this one: https://bugzilla.redhat.com/show_bug.cgi?id=1573829 and might be fixed in a more recent version of seahorse? ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: seahorse 3.30-1 ProcVersionSignature: Ubuntu 4.18.0-15.16-generic 4.18.20 Uname: Linux 4.18.0-15-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.2 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Feb 13 00:00:48 2019 InstallationDate: Installed on 2019-02-10 (2 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: seahorse UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: seahorse (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to seahorse in Ubuntu. https://bugs.launchpad.net/bugs/1815686 Title: Seahorse won't show any importet PGP keys Status in seahorse package in Ubuntu: New Bug description: Upon importing various private and public keys manually, I notice that none of them show up in the section GNUpgp keys no matter what I choose under view. Maybe this is related to this one: https://bugzilla.redhat.com/show_bug.cgi?id=1573829 and might be fixed in a more recent version of seahorse? ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: seahorse 3.30-1 ProcVersionSignature: Ubuntu 4.18.0-15.16-generic 4.18.20 Uname: Linux 4.18.0-15-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.2 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Feb 13 00:00:48 2019 InstallationDate: Installed on 2019-02-10 (2 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: seahorse UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/seahorse/+bug/1815686/+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 1815485] Re: Date format is wrong for English (Denmark) preset
That's coming from the locale definition $ LC_ALL=en_DK.UTF-8 locale d_fmt %Y-%m-%d ** Package changed: language-selector (Ubuntu) => glibc (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to language-selector in Ubuntu. https://bugs.launchpad.net/bugs/1815485 Title: Date format is wrong for English (Denmark) preset Status in glibc package in Ubuntu: New Bug description: The date format is wrong for the "English (Denmark)" preset. It should be DD-MM-, but is currently -MM-DD. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: language-selector-gnome 0.188.1 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Feb 11 17:25:39 2019 InstallationDate: Installed on 2018-11-04 (98 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: language-selector UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1815485/+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 1815670] Re: Ubuntu 19.04: Severe GObject/GType error and crash
Thanks, that looks like a bug in the current 1.15 tarball which is fixed in git and is going to be fixed with the next update https://gitlab.freedesktop.org/gstreamer/gst-plugins-good/commit/4e9a8e58 ** Package changed: gstreamer1.0 (Ubuntu) => gst-plugins-good1.0 (Ubuntu) ** Changed in: gst-plugins-good1.0 (Ubuntu) Importance: Undecided => High ** Changed in: gst-plugins-good1.0 (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gst-plugins-good1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1815670 Title: Ubuntu 19.04: Severe GObject/GType error and crash Status in gst-plugins-good1.0 package in Ubuntu: Fix Committed Bug description: Hello, I am trying to make Audio-recorder to compile and run under Ubuntu 19.04 (Ubuntu Disco Dingo - development branch). 1) A GStreamer bug. This crash occurs if I run a Gstreamer pipleline on the command line (in a terminal window). Like this. $ gst-launch-1.0 -e pulsesrc | fakesink (gst-launch-1.0:8410): GLib-GObject-WARNING **: 21:31:05.365: ../../../gobject/gtype.c:4265: type id '0' is invalid (gst-launch-1.0:8410): GLib-GObject-WARNING **: 21:31:05.365: can't peek value table for type '' which is not currently referenced Caught SIGSEGV Spinning. Please run 'gdb gst-launch-1.0 8410' to continue debugging, Ctrl-C to quit, or Ctrl-\ to dump core. -- 2) Also, it seems that the same bug causes my audio-recorder program crash. It happens in all gtk_button_set_image(...) calls during runtime. gtk_button_set_image(GTK_BUTTON(g_win.recorder_button), GTK_WIDGET(image)); The error message is: (audio-recorder:32368): GLib-GObject-WARNING **: 19:21:52.600: ../../../gobject/gtype.c:4265: type id '0' is invalid (audio-recorder:32368): GLib-GObject-WARNING **: 19:21:52.600: can't peek value table for type '' which is not currently referenced Segmentation fault (core dumped) Please educate me if you want more debug info or stacktrace. My system is: $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu Disco Dingo (development branch) Release: 19.04 Codename: disco My system has very latest updates. Any comments? Kindly Osmo (moma) Antero --- EDIT: This bug report is similar https://gitlab.freedesktop.org/gstreamer/gst-plugins-good/issues/552 --- ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gstreamer1.0-tools 1.15.1-1 ProcVersionSignature: Ubuntu 4.19.0-12.13-generic 4.19.18 Uname: Linux 4.19.0-12-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu20 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Feb 12 21:31:51 2019 ExecutablePath: /usr/bin/gst-launch-1.0 InstallationDate: Installed on 2019-02-04 (8 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190203) SourcePackage: gstreamer1.0 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gst-plugins-good1.0/+bug/1815670/+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 1815670] [NEW] Ubuntu 19.04: Severe GObject/GType error and crash
Public bug reported: Hello, I am trying to make Audio-recorder to compile and run under Ubuntu 19.04 (Ubuntu Disco Dingo - development branch). 1) A GStreamer bug. This crash occurs if I run a Gstreamer pipleline on the command line (in a terminal window). Like this. $ gst-launch-1.0 -e pulsesrc | fakesink (gst-launch-1.0:8410): GLib-GObject-WARNING **: 21:31:05.365: ../../../gobject/gtype.c:4265: type id '0' is invalid (gst-launch-1.0:8410): GLib-GObject-WARNING **: 21:31:05.365: can't peek value table for type '' which is not currently referenced Caught SIGSEGV Spinning. Please run 'gdb gst-launch-1.0 8410' to continue debugging, Ctrl-C to quit, or Ctrl-\ to dump core. -- 2) Also, it seems that the same bug causes my audio-recorder program crash. It happens in all gtk_button_set_image(...) calls during runtime. gtk_button_set_image(GTK_BUTTON(g_win.recorder_button), GTK_WIDGET(image)); The error message is: (audio-recorder:32368): GLib-GObject-WARNING **: 19:21:52.600: ../../../gobject/gtype.c:4265: type id '0' is invalid (audio-recorder:32368): GLib-GObject-WARNING **: 19:21:52.600: can't peek value table for type '' which is not currently referenced Segmentation fault (core dumped) Please educate me if you want more debug info or stacktrace. My system is: $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu Disco Dingo (development branch) Release:19.04 Codename: disco My system has very latest updates. Any comments? Kindly Osmo (moma) Antero --- EDIT: This bug report is similar https://gitlab.freedesktop.org/gstreamer/gst-plugins-good/issues/552 --- ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gstreamer1.0-tools 1.15.1-1 ProcVersionSignature: Ubuntu 4.19.0-12.13-generic 4.19.18 Uname: Linux 4.19.0-12-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu20 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Feb 12 21:31:51 2019 ExecutablePath: /usr/bin/gst-launch-1.0 InstallationDate: Installed on 2019-02-04 (8 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190203) SourcePackage: gstreamer1.0 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gstreamer1.0 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco ** Description changed: Hello, I am trying to make Audio-recorder to compile and run under Ubuntu 19.04 (Ubuntu Disco Dingo - development branch). 1) A GStreamer bug. This crash occurs if I run a Gstreamer pipleline on the command line (in a terminal window). Like this. $ gst-launch-1.0 -e pulsesrc | fakesink (gst-launch-1.0:8410): GLib-GObject-WARNING **: 21:31:05.365: ../../../gobject/gtype.c:4265: type id '0' is invalid (gst-launch-1.0:8410): GLib-GObject-WARNING **: 21:31:05.365: can't peek value table for type '' which is not currently referenced Caught SIGSEGV Spinning. Please run 'gdb gst-launch-1.0 8410' to continue debugging, Ctrl-C to quit, or Ctrl-\ to dump core. -- + 2) Also, it seems that the same bug causes my audio-recorder program crash. + It happens in all gtk_button_set_image(...) calls during runtime. - 2) Also, it seems that the same bug causes my audio-recorder program crash. - It happens in all gtk_button_set_image(...) calls during runtime. - - gtk_button_set_image(GTK_BUTTON(g_win.recorder_but ton), + gtk_button_set_image(GTK_BUTTON(g_win.recorder_button), GTK_WIDGET(image)); The error message is: (audio-recorder:32368): GLib-GObject-WARNING **: 19:21:52.600: ../../../gobject/gtype.c:4265: type id '0' is invalid (audio-recorder:32368): GLib-GObject-WARNING **: 19:21:52.600: can't peek value table for type '' which is not currently referenced Segmentation fault (core dumped) Please educate me if you want more debug info or stacktrace. My system is: $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu Disco Dingo (development branch) Release: 19.04 Codename: disco My system has very latest updates. Any comments? Kindly Osmo (moma) Antero --- EDIT: This bug report is similar - https://gitlab.freedesktop.org/gstre...ood/issues/552 + https://gitlab.freedesktop.org/gstreamer/gst-plugins-good/issues/552 + --- ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gstreamer1.0-tools 1.15.1-1 ProcVersionSignature: Ubuntu 4.19.0-12.13-generic 4.19.18 Uname: Linux 4.19.0-12-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu20 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Feb 12 21:31:51 2019 ExecutablePath: /usr/bin/gst-launch-1.0 InstallationDate: Installed on 2019-02-04 (8 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190203) SourcePackage: gstreamer1.0
[Desktop-packages] [Bug 1764005] Re: Black-screen on boot with nvidia 390 for Budgie, MATE, Xubuntu, Kubuntu
I also have this problem with prime Intel 4200M, Geforce GT 740M using the nvidia 390 driver, on 18.10 (cosmic). Nouveau works, and the intel gpu also works even if I have the 390 driver installed (I used: sudo prime-select intel) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1764005 Title: Black-screen on boot with nvidia 390 for Budgie, MATE, Xubuntu, Kubuntu Status in nvidia-prime package in Ubuntu: Fix Released Bug description: Upgraded from Ubuntu Budgie 17.10 to 18.04. After the plymouth splash left with a black screen. Purged all the nivdia-* packages and rebooted - graphical logon and logged in ok with nouveau. Tried software & updates to reinstall the nvidia 390 drivers. Rebooted. Left at black screen again. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nvidia-driver-390 390.48-0ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 NonfreeKernelModules: wl nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 Date: Sat Apr 14 21:42:04 2018 InstallationDate: Installed on 2016-11-26 (503 days ago) InstallationMedia: budgie-remix 16.10 "Budgie-remix" - amd64 (20161013) SourcePackage: nvidia-graphics-drivers-390 UpgradeStatus: Upgraded to bionic on 2018-04-14 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1764005/+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 1812527] Re: gnome-shell crashes with SIGSEGV in meta_window_actor_is_destroyed(self=NULL) called from _switchWorkspaceDone() [windowManager.js:1787] when running Android emula
I can confirm the same bug on 18.04 and Android Studio + running AVD. Disabling system animation by Tweaks / Appearance / Animations works!! It does not crash anymore... -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1812527 Title: gnome-shell crashes with SIGSEGV in meta_window_actor_is_destroyed(self=NULL) called from _switchWorkspaceDone() [windowManager.js:1787] when running Android emulator (QEMU) Status in gjs package in Ubuntu: Triaged Status in gnome-shell package in Ubuntu: Triaged Bug description: https://errors.ubuntu.com/problem/cb400a6f83ed57af8bb117cf84d5ed6d7e2ffcee https://gitlab.gnome.org/GNOME/gnome-shell/issues/927 Switching workspace with the Android Emulator running will blink the screen as if gnome restarted, if I switch workspace one more time, it will completely crash and I will need to log in again. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.3-0ubuntu0.18.04.4 Uname: Linux 4.20.3-acso x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Jan 19 20:05:34 2019 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2019-01-15 (4 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1812527/+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 1815307] Re: ipp printer isn't shown automatically - adding it errors with a CUPS internal error
Also added the ipptool results of the modified test given in https://github.com/OpenPrinting/cups-filters/issues/22 Seems to me that it is a similar issue. ** Attachment added: "ipp_attr2.txt" https://bugs.launchpad.net/ubuntu/+source/system-config-printer/+bug/1815307/+attachment/5238085/+files/ipp_attr2.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to system-config-printer in Ubuntu. https://bugs.launchpad.net/bugs/1815307 Title: ipp printer isn't shown automatically - adding it errors with a CUPS internal error Status in system-config-printer package in Ubuntu: New Bug description: System: Ubuntu 18.04 system-config-printer version: 1.5.11-1ubuntu printer: Canon iP7250 I expect to be able to see the printer in the panel just as 'lpstat -l -e' or 'driverless' can see them, without the need to especially add a new printer. And if I do need to add it (don't see why that should be the case, but still), I expect that choosing the printer's name under network would result in adding the printer. What happened instead: Canon iP7250 isn't shown in the Printers panel, clicking on add and expanding the network options - it is shown, but when trying to add it (either driverless IPP, LPD via DNS-SD or IPP via DNS-SD) it gives an error about CUPS internal error. `$ lpstat -l -e` gives `Canon_iP7200_series network none ipp://Canon%20iP7200%20series._ipp._tcp.local/` So the system does see it, and `lp -d Canon_iP7200_series /etc/nsswitch.conf` does print (and for a minute the printer is shown in the Printers panel - but then disappears). I can add it by *not* clicking on the printer's name under Network, but rather, click on ipp printer and manually choose Canon -> iP7200 -> CUPS+Gutenprint driver (and not the recommended driverless option - which, if I choose results in that same cryptic error I get when trying to add the printer by clicking on it, as described above). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/system-config-printer/+bug/1815307/+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 1747646] Re: Authentication error with google drive
I can confirm, same issue here. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to deja-dup in Ubuntu. https://bugs.launchpad.net/bugs/1747646 Title: Authentication error with google drive Status in Déjà Dup: Confirmed Status in Duplicity: Confirmed Status in deja-dup package in Ubuntu: Triaged Bug description: Hi, I'm having an issue using deja-dup to back up my laptop to my google drive. When backing only a small folder (eg: ~/Documents) every thing works fine. However when trying to backup my whole home folder (/home/myusername) I get an "Invalid credentials" error after 5-10 min. The back up seems to start normally and my destination folder starts filling with "duplicity-full...difftar.gz" files, but eventually I get the Invalid Credentials error. lsb_release -d Fedora release 27 (Twenty Seven) rpm -q deja-dup duplicity deja-dup-37.1-1.fc27.x86_64 duplicity-0.7.16-1.fc27.x86_64 deja-dup.log attached. I cannot attach deja-dup.gsettings since i can only join 1 file. Will send if needed. To manage notifications about this bug go to: https://bugs.launchpad.net/deja-dup/+bug/1747646/+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 1752813] Re: Pointer speed is too slow even in the fastest setting
Currently the settings are just barely usable at max speed. Is there any
upstream I can coordinate with to try and get this solved? This is a
really annoying issue. Using these same laptops in Windows has a much
faster pointer.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1752813
Title:
Pointer speed is too slow even in the fastest setting
Status in gnome-control-center package in Ubuntu:
New
Bug description:
I use the trackpoint on my Lenovo T460s almost exclusively. Even in
the fastest setting on a 2560x1440 screen it is much too slow. I've
had to add the following udev rule to get it to be usable:
ACTION=="add",
SUBSYSTEM=="input",
ATTR{name}=="TPPS/2 IBM TrackPoint",
ATTR{device/sensitivity}="190",
ATTR{device/speed}="220",
ATTR{device/inertia}="6",
ATTR{device/press_to_select}="0"
And even with this and the speed in the control center set to maximum
it is still a bit slow. Trying to push the sensitivity/speed settings
higher will break the trackpoint and even with these settings it seems
that sometimes on resume from sleep the trackpoint fails. After
cycling suspend/resume again it comes back.
There should be a way to set much higher speed settings for the mouse.
Current settings make trackpoints very hard to use which even carries
risk of hand/arm injuries.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: gnome-control-center 1:3.18.2-1ubuntu6
ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
Uname: Linux 4.13.0-32-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
CurrentDesktop: GNOME
Date: Fri Mar 2 08:47:44 2018
InstallationDate: Installed on 2016-10-27 (490 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64
(20160719)
SourcePackage: gnome-control-center
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1752813/+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 1600622] Re: Screen doesn't lock or go to sleep when certain Chrome tabs are open
Could those having the issue give details on the webpage that create the
issue? Having videos and such blocking lock/suspend is a feature not a
bug...
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-session in Ubuntu.
https://bugs.launchpad.net/bugs/1600622
Title:
Screen doesn't lock or go to sleep when certain Chrome tabs are open
Status in gnome-session package in Ubuntu:
Confirmed
Bug description:
$ lsb_release -rd
Description: Ubuntu 16.04 LTS
Release: 16.04
$ apt-cache policy gnome-session-bin
gnome-session-bin:
Installed: 3.18.1.2-1ubuntu1.16.04.1
Candidate: 3.18.1.2-1ubuntu1.16.04.1
Version table:
*** 3.18.1.2-1ubuntu1.16.04.1 500
500 http://es.archive.ubuntu.com/ubuntu xenial-updates/main amd64
Packages
100 /var/lib/dpkg/status
3.18.1.2-1ubuntu1 500
500 http://es.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
I'm using gnome-session-flashback
What happens:
The screen doesn't lock when having certain pages in Chrome tabs
Expected:
The screen should lock after the configured timeout in settings.
I've been having this issue sice before 14.04, which I recently
upgraded (fresh install) to 16.04.
After fresh install, the screen would turn down and lock the computer
after 10 minutes (or whatever time I setup). At one point it stopped
working. The screen never shuts down unless I manually lock the
session with CTRL-ALT-L.
I've followed the steps in
https://wiki.ubuntu.com/DebuggingScreenLocking#Debugging_procedure
The culprit seems to be that Chrome issues some suspend inhibitions
through dbus when doing certain operations. Many people find this
problem when using Yahoo Mail. I can reproduce it with Odoo. I'm
pretty sure that Chrome is doing something else of what i've found
out.
1) Gnome screen saver works correctly. I can trigger it manually with:
$ gnome-screensaver-command -a
2) Gnome screen saver never receives the "session idle" status
callback.
3) When Chrome is not running, I can manually inhibit the idle status:
$ gnome-session-inhibit --app-id test --reason "manual idle inhibit"
--inhibit-only --inhibit idle:suspend
Inhibiting until Ctrl+C is pressed...
4) I can query the inhibitors:
$ dbus-send --print-reply --dest=org.gnome.SessionManager
/org/gnome/SessionManager org.gnome.SessionManager.GetInhibitorsmethod return
time=1468170482.066533 sender=:1.19 -> destination=:1.1315311 serial=1329103
reply_serial=2
array [
object path "/org/gnome/SessionManager/Inhibitor1686"
]
$ gdbus call --session --dest org.gnome.SessionManager --object-path
/org/gnome/SessionManager/Inhibitor1686 --method
org.gnome.SessionManager.Inhibitor.GetAppId
('test',)
$ gdbus call --session --dest org.gnome.SessionManager --object-path
/org/gnome/SessionManager/Inhibitor1686 --method
org.gnome.SessionManager.Inhibitor.GetReason
('manual idle inhibit',)
$ gdbus call --session --dest org.gnome.SessionManager --object-path
/org/gnome/SessionManager/Inhibitor1686 --method
org.gnome.SessionManager.Inhibitor.GetFlags
(uint32 12,)
12=4(suspend) + 8(idle)
5) When testing, I can inhibit for 70 seconds, idle timeout being 60
(1 minute). After these 70 seconds pass, the screen locks.
6) Regarding Chrome, this is the information I get when querying the
inhibitor:
GetAppId: ('/usr/bin/google-chrome-stable',)
GetReason: ('Uploading data to 10.200.0.163',)
GetFlags: (uint32 4,)
The flags just inhibits suspend, not locking or entering powersaving
mode.
This inhibitor seems to stay for 10-15 seconds, then goes away for
another 30-60 seconds. The screen NEVER locks when this tab is open.
No matter the inhibitor is present or not.
I'm not sure where to go on. If it's a Chrome bug it must be using
other mechanisms to prevent the idle timeout. Any ideas on what to
look for?
Julian.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1600622/+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 1815307] Re: ipp printer isn't shown automatically - adding it errors with a CUPS internal error
** Changed in: system-config-printer (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to system-config-printer in Ubuntu. https://bugs.launchpad.net/bugs/1815307 Title: ipp printer isn't shown automatically - adding it errors with a CUPS internal error Status in system-config-printer package in Ubuntu: New Bug description: System: Ubuntu 18.04 system-config-printer version: 1.5.11-1ubuntu printer: Canon iP7250 I expect to be able to see the printer in the panel just as 'lpstat -l -e' or 'driverless' can see them, without the need to especially add a new printer. And if I do need to add it (don't see why that should be the case, but still), I expect that choosing the printer's name under network would result in adding the printer. What happened instead: Canon iP7250 isn't shown in the Printers panel, clicking on add and expanding the network options - it is shown, but when trying to add it (either driverless IPP, LPD via DNS-SD or IPP via DNS-SD) it gives an error about CUPS internal error. `$ lpstat -l -e` gives `Canon_iP7200_series network none ipp://Canon%20iP7200%20series._ipp._tcp.local/` So the system does see it, and `lp -d Canon_iP7200_series /etc/nsswitch.conf` does print (and for a minute the printer is shown in the Printers panel - but then disappears). I can add it by *not* clicking on the printer's name under Network, but rather, click on ipp printer and manually choose Canon -> iP7200 -> CUPS+Gutenprint driver (and not the recommended driverless option - which, if I choose results in that same cryptic error I get when trying to add the printer by clicking on it, as described above). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/system-config-printer/+bug/1815307/+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 1814889] Re: Dock does not change position nor icon size
Could you add your journalctl log from the session which had the issue? ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Importance: Undecided => Low ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1814889 Title: Dock does not change position nor icon size Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Incomplete Bug description: I cannot change the position of the dock. How to reproduce (on my system): Either: (a) open the settings -> Dock and select a different value for the dock, e.g. "Bottom", or (b) enter "gsettings set org.gnome.shell.extensions.dash-to-dock dock-position BOTTOM" in the command line Expected result: In both cases, the dock should move to the bottom of the screen. Actual result: The dock remains at the same position. Additional observations: 1. I also cannot change the icon size (only tried via GUI, not command line). 2. All the behavior is observed no matter what other settings (auto-hide, show on) I pick. 3. This describes a similar (the same?) problem: https://askubuntu.com/questions/1061924/ubuntu-wont-register-dock-settings-changes-in-18-04#new-answer Screenshots are attached. Please let me know if I should provide additional information. I am a fairly technical user, and I am willing to put in some effort to get this resolved. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell-extension-ubuntu-dock 0.9.1ubuntu18.04.3 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Feb 6 12:51:39 2019 InstallationDate: Installed on 2018-11-20 (77 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1814889/+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 1813893] Re: OpenVPN LZ4 compression not working in Networkmanager
Thank you for your bug report, that's known upstream https://gitlab.gnome.org/GNOME/NetworkManager-openvpn/issues/1 ** Changed in: network-manager-openvpn (Ubuntu) Importance: Undecided => Low ** Changed in: network-manager-openvpn (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-openvpn in Ubuntu. https://bugs.launchpad.net/bugs/1813893 Title: OpenVPN LZ4 compression not working in Networkmanager Status in network-manager-openvpn package in Ubuntu: Triaged Bug description: Hi there, when importing an ovpn profile (from a PFsense in this case) where compression is set to LZ4 it won't work. Network manager won't save the config properly, as it does not seem to support lz4? When I manually use sudo openvpn --config myconfig.ovpn it works just fine. OpenVPN 2.4.6 x86_64-pc-linux-gnu is being used right now. Best regards David To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1813893/+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 1778555] Re: My Webcam does not work with Cheese
The errors are similar to the ones on https://bugzilla.gnome.org/show_bug.cgi?id=795022 Do you have pipewire installed? ** Bug watch added: GNOME Bug Tracker #795022 https://bugzilla.gnome.org/show_bug.cgi?id=795022 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cheese in Ubuntu. https://bugs.launchpad.net/bugs/1778555 Title: My Webcam does not work with Cheese Status in cheese package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: Cheese says that there is no video cam. The same webcam (connected through USB 3) does work in Skype. From dmesg: [1.329876] usb 3-2: New USB device found, idVendor=17a1, idProduct=0128 [1.329877] usb 3-2: New USB device strings: Mfr=32, Product=38, SerialNumber=0 [1.329878] usb 3-2: Product: USB2.0 JPEG WebCam [1.329879] usb 3-2: Manufacturer: TASCORP From dmidecode (about my motherboard): Handle 0x0001, DMI type 1, 27 bytes System Information Manufacturer: Gigabyte Technology Co., Ltd. Product Name: H67A-UD3H Version: Serial Number: UUID: ----1C6F65886700 Wake-up Type: Power Switch SKU Number: Family: $ lsb_release -rd Description: Ubuntu 18.04 LTS Release: 18.04 $ dpkg -s cheese Package: cheese Status: install ok installed Priority: optional Section: gnome Installed-Size: 437 Maintainer: Ubuntu Developers Architecture: amd64 Version: 3.28.0-1ubuntu1 Depends: libc6 (>= 2.4), libcanberra-gtk3-0 (>= 0.25), libcheese-gtk25 (>= 3.18.0), libcheese8 (>= 3.18.0), libclutter-1.0-0 (>= 1.16), libclutter-gtk-1.0-0 (>= 0.91.8), libgdk-pixbuf2.0-0 (>= 2.25.2), libglib2.0-0 (>= 2.39.90), libgnome-desktop-3-17 (>= 3.17.92), libgstreamer1.0-0 (>= 1.0.0), libgtk-3-0 (>= 3.13.7), cheese-common (>= 3.28.0-1ubuntu1), gnome-video-effects Recommends: gvfs, yelp Suggests: gnome-video-effects-frei0r Description: tool to take pictures and videos from your webcam A webcam application that supports image and video capture. Makes it easy to take photos and videos of you, your friends, pets or whatever you want. Allows you to apply fancy visual effects, fine-control image settings and has features such as Multi-Burst mode, Countdown timer for photos. Homepage: https://wiki.gnome.org/Apps/Cheese Original-Maintainer: Debian GNOME Maintainers ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: cheese 3.28.0-1ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Jun 25 19:11:59 2018 InstallationDate: Installed on 2018-06-23 (1 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Gigabyte Technology Co., Ltd. H67A-UD3H ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IL SHELL=/bin/bash RelatedPackageVersions: cheese3.28.0-1ubuntu1 cheese-common 3.28.0-1ubuntu1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/02/2010 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F4 dmi.board.name: H67A-UD3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF4:bd11/02/2010:svnGigabyteTechnologyCo.,Ltd.:pnH67A-UD3H:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnH67A-UD3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: H67A-UD3H dmi.sys.vendor: Gigabyte Technology Co., Ltd. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: porton 1424 F pulseaudio /dev/snd/controlC0: porton 1424 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-06-23 (1 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Gigabyte Technology Co., Ltd. H67A-UD3H Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IL SHELL=/bin/bash ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic root=UUID=521f8f0f-da76-44d7-8d98-2b45259ff93c ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-23-generic N/A linux-backports-modules-4.15.0-23-generic N/A linux-firmware 1.173.1 RfKill: 0: phy0: Wireless LAN Soft blocked: no
[Desktop-packages] [Bug 1810382] Re: Gnome software error posting a review for snap app
Sorry not same problem, I can write a review and i have NO errors ** Attachment added: "Screenshot from 2019-02-12 20-58-50.png" https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1810382/+attachment/5238070/+files/Screenshot%20from%202019-02-12%2020-58-50.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1810382 Title: Gnome software error posting a review for snap app Status in gnome-software package in Ubuntu: Triaged Bug description: Received msg: Sorry, something went wrong: Got unknown content type text/html from reviews.ubuntu.com posting a review for snap app. this does not happen for 'normal' apps ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gnome-software 3.30.2-0ubuntu8 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Jan 3 09:06:57 2019 ExecutablePath: /usr/bin/gnome-software InstallationDate: Installed on 2018-10-22 (73 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-limba N/A gnome-software-plugin-snap3.30.2-0ubuntu8 SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1810382/+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 1746598] Re: [MIR] libnfs
Override component to main libnfs12 3.0.0-2 in disco amd64: universe/libs/optional/100% -> main libnfs12 3.0.0-2 in disco arm64: universe/libs/optional/100% -> main libnfs12 3.0.0-2 in disco armhf: universe/libs/optional/100% -> main libnfs12 3.0.0-2 in disco i386: universe/libs/optional/100% -> main libnfs12 3.0.0-2 in disco ppc64el: universe/libs/optional/100% -> main libnfs12 3.0.0-2 in disco s390x: universe/libs/optional/100% -> main Override [y|N]? y 6 publications overridden. ** Changed in: libnfs (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libnfs in Ubuntu. https://bugs.launchpad.net/bugs/1746598 Title: [MIR] libnfs Status in libnfs package in Ubuntu: Fix Released Bug description: Availability Built for all supported architectures. In sync with Debian. Rationale = gvfs 1.24 added an NFS backend 3 years ago. It was enabled in Debian a year ago, but we can't enable it in Ubuntu until libnfs is promoted to main. The Ubuntu bug for this feature to be enabled in gvfs is LP: #1637988 qemu-block-extra could also enable libnfs support. Security No known CVEs. https://security-tracker.debian.org/tracker/source-package/libnfs https://launchpad.net/ubuntu/+source/libnfs/+cve Quality assurance = - Desktop Packages team is subscribed. - dh_auto_test runs but the tests shipped by upstream cant'b be run at build time since they modify the system. - Autopkgtests are added in 3.0.0-1, running upstream's test suite which includes running tests with valgrind, too. https://bugs.launchpad.net/ubuntu/+source/libnfs https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=libnfs https://github.com/sahlberg/libnfs/issues https://autopkgtest.ubuntu.com/packages/libn/libnfs (failing, never passed: see https://bugs.debian.org/921578 ) https://ci.debian.net/packages/libn/libnfs/ (tests aren't run in Debian because they request machine isolation which isn't implemented there yet) Dependencies No universe binary dependencies Standards compliance 3.9.8, debhelper compat 9, dh7 simple rules Maintenance === Actively maintained: https://github.com/sahlberg/libnfs Not team maintained in Debian. https://tracker.debian.org/pkg/libnfs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libnfs/+bug/1746598/+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 1815095] Re: [MIR] gsound
Override component to main libgsound0 1.0.2-4 in disco amd64: universe/libs/optional/100% -> main libgsound0 1.0.2-4 in disco arm64: universe/libs/optional/100% -> main libgsound0 1.0.2-4 in disco armhf: universe/libs/optional/100% -> main libgsound0 1.0.2-4 in disco i386: universe/libs/optional/100% -> main libgsound0 1.0.2-4 in disco ppc64el: universe/libs/optional/100% -> main libgsound0 1.0.2-4 in disco s390x: universe/libs/optional/100% -> main Override [y|N]? y ** Changed in: gsound (Ubuntu) Importance: Undecided => Low ** Changed in: gsound (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gsound in Ubuntu. https://bugs.launchpad.net/bugs/1815095 Title: [MIR] gsound Status in gsound package in Ubuntu: Fix Released Bug description: Availability Built for all supported architectures. In sync with Debian. Rationale = gsound is a minimal GNOME library to make working with libcanberra easier. gnome-control-center 3.31.90 has a new simplified sound panel which now uses gsound. The Ubuntu Desktop Team wants gnome-control-center 3.32 for Ubuntu 19.04. Other GNOME stuff in main might use gsound in the future but I don't see any definite plans for it. Security No known security issues https://security-tracker.debian.org/tracker/source-package/gsound https://launchpad.net/ubuntu/+source/gsound/+cve Quality assurance = - Ubuntu Desktop Packages is subscribed. https://bugs.launchpad.net/ubuntu/+source/gsound https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=gsound https://gitlab.gnome.org/GNOME/gsound/issues No autopkgtests. No build tests. Dependencies All dependencies are in main Standards compliance 4.3.0, debhelper compat 11, simple dh7 style rules Maintenance === Co-maintained in Debian with the Debian GNOME team https://salsa.debian.org/gnome-team/gsound https://gitlab.gnome.org/GNOME/gsound https://wiki.gnome.org/Projects/GSound It not being actively developed but is a stable mature library. (It's at least more active than libcanberra.) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gsound/+bug/1815095/+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 1810382] Re: Gnome software error posting a review for snap app
@corrado, on 19.04 gnome-software use the ODRS review server and reviewing snaps should work, when you say "same provblem" you mean that you also get the text/html error there? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1810382 Title: Gnome software error posting a review for snap app Status in gnome-software package in Ubuntu: Triaged Bug description: Received msg: Sorry, something went wrong: Got unknown content type text/html from reviews.ubuntu.com posting a review for snap app. this does not happen for 'normal' apps ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gnome-software 3.30.2-0ubuntu8 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Jan 3 09:06:57 2019 ExecutablePath: /usr/bin/gnome-software InstallationDate: Installed on 2018-10-22 (73 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-limba N/A gnome-software-plugin-snap3.30.2-0ubuntu8 SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1810382/+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 1810382] Re: Gnome software error posting a review for snap app
I have the same problem also with Ubuntu 19.04 with all kernels up to Kernel: 5.0.0-05rc6-generic ** Attachment added: "Screenshot from 2019-02-12 20-21-48.png" https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1810382/+attachment/5238052/+files/Screenshot%20from%202019-02-12%2020-21-48.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1810382 Title: Gnome software error posting a review for snap app Status in gnome-software package in Ubuntu: Triaged Bug description: Received msg: Sorry, something went wrong: Got unknown content type text/html from reviews.ubuntu.com posting a review for snap app. this does not happen for 'normal' apps ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gnome-software 3.30.2-0ubuntu8 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Jan 3 09:06:57 2019 ExecutablePath: /usr/bin/gnome-software InstallationDate: Installed on 2018-10-22 (73 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-limba N/A gnome-software-plugin-snap3.30.2-0ubuntu8 SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1810382/+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 1791981] Re: X Server session crash for "No space left on device"
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: xorg-server (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1791981 Title: X Server session crash for "No space left on device" Status in xorg-server package in Ubuntu: Confirmed Bug description: Ubuntu Release: Ubuntu 18.04.1 LTS Package version: xserver-xorg: 1:7.7+19ubuntu7.1 When my laptop resumes after suspend, the desktop session crashes and a new one is started. So each time I lose all open applications and unsaved data! The expected behavior would be obviously to restore the suspended session. I had a look through log files and found that Xorg.0.log ends with the following error lines: [ 6004.019] (II) NVIDIA(0): Setting mode "NULL" [ 6004.026] (EE) modeset(G0): failed to set mode: No space left on device [ 6004.026] (EE) Fatal server error: [ 6004.026] (EE) EnterVT failed for gpu screen 0 [ 6004.027] (EE) [ 6004.027] (EE) Please consult the The X.Org Foundation support at http://wiki.x.org for help. [ 6004.027] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information. [ 6004.027] (EE) [ 6004.065] (EE) Server terminated with error (1). Closing log file. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1791981/+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 1815653] Re: gnome-control-center crashed with SIGSEGV in __GI___libc_free()
*** This bug is a duplicate of bug 1814949 *** https://bugs.launchpad.net/bugs/1814949 ** This bug has been marked a duplicate of bug 1814949 gnome-control-center refuses to open if you try to open the Details panels ** Information type changed from Private to Public -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1815653 Title: gnome-control-center crashed with SIGSEGV in __GI___libc_free() Status in gnome-control-center package in Ubuntu: New Bug description: unity wont boot ProblemType: Crash DistroRelease: Ubuntu 19.04 Package: gnome-control-center 1:3.30.2-4ubuntu2 ProcVersionSignature: Ubuntu 4.18.0-12.13-generic 4.18.17 Uname: Linux 4.18.0-12-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu20 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Feb 12 13:47:12 2019 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2016-10-05 (860 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) ProcCmdline: gnome-control-center ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7efd7e2a132d <__GI___libc_free+29>: mov -0x8(%rdi),%rax PC (0x7efd7e2a132d) ok source "-0x8(%rdi)" (0xfff8) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: gnome-control-center StacktraceTop: __GI___libc_free (mem=0x1) at malloc.c:3085 g_unix_mount_free () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 () () g_type_create_instance () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: gnome-control-center crashed with SIGSEGV in __GI___libc_free() UpgradeStatus: Upgraded to disco on 2018-12-06 (68 days ago) UserGroups: adm cdrom dip lp lpadmin plugdev root sambashare saned scanner sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1815653/+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 1778555] Re: My Webcam does not work with Cheese
Bug confirmed with three computers, each one using Ubuntu 18.04. Webcam works (tested with Camorama) but Cheese can't detect it. >From command line: (cheese:13203): Gtk-WARNING **: 21:16:31.115: Theme parsing error: cheese.css:7:35: The style property GtkScrollbar:min-slider-length is deprecated and shouldn't be used anymore. It will be removed in a future version ** Message: 21:16:31.161: cheese-application.vala:211: Error during camera setup: <> (cheese:13203): cheese-CRITICAL **: 21:16:31.172: cheese_camera_device_get_name: assertion 'CHEESE_IS_CAMERA_DEVICE (device)' failed (cheese:13203): GLib-CRITICAL **: 21:16:31.172: g_variant_new_string: assertion 'string != NULL' failed (cheese:13203): GLib-CRITICAL **: 21:16:31.172: g_variant_ref_sink: assertion 'value != NULL' failed (cheese:13203): GLib-GIO-CRITICAL **: 21:16:31.172: g_settings_schema_key_type_check: assertion 'value != NULL' failed (cheese:13203): GLib-CRITICAL **: 21:16:31.172: g_variant_get_type_string: assertion 'value != NULL' failed (cheese:13203): GLib-GIO-CRITICAL **: 21:16:31.172: g_settings_set_value: key 'camera' in 'org.gnome.Cheese' expects type 's', but a GVariant of type '(null)' was given (cheese:13203): GLib-CRITICAL **: 21:16:31.172: g_variant_unref: assertion 'value != NULL' failed ** (cheese:13203): CRITICAL **: 21:16:31.172: cheese_preferences_dialog_setup_resolutions_for_device: assertion 'device != NULL' failed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cheese in Ubuntu. https://bugs.launchpad.net/bugs/1778555 Title: My Webcam does not work with Cheese Status in cheese package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: Cheese says that there is no video cam. The same webcam (connected through USB 3) does work in Skype. From dmesg: [1.329876] usb 3-2: New USB device found, idVendor=17a1, idProduct=0128 [1.329877] usb 3-2: New USB device strings: Mfr=32, Product=38, SerialNumber=0 [1.329878] usb 3-2: Product: USB2.0 JPEG WebCam [1.329879] usb 3-2: Manufacturer: TASCORP From dmidecode (about my motherboard): Handle 0x0001, DMI type 1, 27 bytes System Information Manufacturer: Gigabyte Technology Co., Ltd. Product Name: H67A-UD3H Version: Serial Number: UUID: ----1C6F65886700 Wake-up Type: Power Switch SKU Number: Family: $ lsb_release -rd Description: Ubuntu 18.04 LTS Release: 18.04 $ dpkg -s cheese Package: cheese Status: install ok installed Priority: optional Section: gnome Installed-Size: 437 Maintainer: Ubuntu Developers Architecture: amd64 Version: 3.28.0-1ubuntu1 Depends: libc6 (>= 2.4), libcanberra-gtk3-0 (>= 0.25), libcheese-gtk25 (>= 3.18.0), libcheese8 (>= 3.18.0), libclutter-1.0-0 (>= 1.16), libclutter-gtk-1.0-0 (>= 0.91.8), libgdk-pixbuf2.0-0 (>= 2.25.2), libglib2.0-0 (>= 2.39.90), libgnome-desktop-3-17 (>= 3.17.92), libgstreamer1.0-0 (>= 1.0.0), libgtk-3-0 (>= 3.13.7), cheese-common (>= 3.28.0-1ubuntu1), gnome-video-effects Recommends: gvfs, yelp Suggests: gnome-video-effects-frei0r Description: tool to take pictures and videos from your webcam A webcam application that supports image and video capture. Makes it easy to take photos and videos of you, your friends, pets or whatever you want. Allows you to apply fancy visual effects, fine-control image settings and has features such as Multi-Burst mode, Countdown timer for photos. Homepage: https://wiki.gnome.org/Apps/Cheese Original-Maintainer: Debian GNOME Maintainers ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: cheese 3.28.0-1ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Jun 25 19:11:59 2018 InstallationDate: Installed on 2018-06-23 (1 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Gigabyte Technology Co., Ltd. H67A-UD3H ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IL SHELL=/bin/bash RelatedPackageVersions: cheese3.28.0-1ubuntu1 cheese-common 3.28.0-1ubuntu1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/02/2010 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F4 dmi.board.name: H67A-UD3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias:
[Desktop-packages] [Bug 1778555] Re: My Webcam does not work with Cheese
** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cheese in Ubuntu. https://bugs.launchpad.net/bugs/1778555 Title: My Webcam does not work with Cheese Status in cheese package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: Cheese says that there is no video cam. The same webcam (connected through USB 3) does work in Skype. From dmesg: [1.329876] usb 3-2: New USB device found, idVendor=17a1, idProduct=0128 [1.329877] usb 3-2: New USB device strings: Mfr=32, Product=38, SerialNumber=0 [1.329878] usb 3-2: Product: USB2.0 JPEG WebCam [1.329879] usb 3-2: Manufacturer: TASCORP From dmidecode (about my motherboard): Handle 0x0001, DMI type 1, 27 bytes System Information Manufacturer: Gigabyte Technology Co., Ltd. Product Name: H67A-UD3H Version: Serial Number: UUID: ----1C6F65886700 Wake-up Type: Power Switch SKU Number: Family: $ lsb_release -rd Description: Ubuntu 18.04 LTS Release: 18.04 $ dpkg -s cheese Package: cheese Status: install ok installed Priority: optional Section: gnome Installed-Size: 437 Maintainer: Ubuntu Developers Architecture: amd64 Version: 3.28.0-1ubuntu1 Depends: libc6 (>= 2.4), libcanberra-gtk3-0 (>= 0.25), libcheese-gtk25 (>= 3.18.0), libcheese8 (>= 3.18.0), libclutter-1.0-0 (>= 1.16), libclutter-gtk-1.0-0 (>= 0.91.8), libgdk-pixbuf2.0-0 (>= 2.25.2), libglib2.0-0 (>= 2.39.90), libgnome-desktop-3-17 (>= 3.17.92), libgstreamer1.0-0 (>= 1.0.0), libgtk-3-0 (>= 3.13.7), cheese-common (>= 3.28.0-1ubuntu1), gnome-video-effects Recommends: gvfs, yelp Suggests: gnome-video-effects-frei0r Description: tool to take pictures and videos from your webcam A webcam application that supports image and video capture. Makes it easy to take photos and videos of you, your friends, pets or whatever you want. Allows you to apply fancy visual effects, fine-control image settings and has features such as Multi-Burst mode, Countdown timer for photos. Homepage: https://wiki.gnome.org/Apps/Cheese Original-Maintainer: Debian GNOME Maintainers ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: cheese 3.28.0-1ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Jun 25 19:11:59 2018 InstallationDate: Installed on 2018-06-23 (1 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Gigabyte Technology Co., Ltd. H67A-UD3H ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IL SHELL=/bin/bash RelatedPackageVersions: cheese3.28.0-1ubuntu1 cheese-common 3.28.0-1ubuntu1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/02/2010 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F4 dmi.board.name: H67A-UD3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF4:bd11/02/2010:svnGigabyteTechnologyCo.,Ltd.:pnH67A-UD3H:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnH67A-UD3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: H67A-UD3H dmi.sys.vendor: Gigabyte Technology Co., Ltd. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: porton 1424 F pulseaudio /dev/snd/controlC0: porton 1424 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-06-23 (1 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Gigabyte Technology Co., Ltd. H67A-UD3H Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IL SHELL=/bin/bash ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic root=UUID=521f8f0f-da76-44d7-8d98-2b45259ff93c ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-23-generic N/A linux-backports-modules-4.15.0-23-generic N/A linux-firmware 1.173.1 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: bionic Uname: Linux 4.15.0-23-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups:
[Desktop-packages] [Bug 1814949] Re: gnome-control-center crashed with SIGSEGV in __GI___libc_free()
I'm reopening this bug, raising its severity and updating the description now that the new glib version has reached disco. ** Changed in: gnome-control-center (Ubuntu) Importance: Low => Critical ** Changed in: gnome-control-center (Ubuntu) Status: Invalid => Triaged ** Summary changed: - gnome-control-center crashed with SIGSEGV in __GI___libc_free() + gnome-control-center refuses to open if you try to open the Details panels ** Description changed: - Segmentation fault while trying to run via cli , the gnome setting - doesn't working when click on setting menu + Workaround + == + Run this command in your terminal: + gsettings reset org.gnome.ControlCenter last-panel + + Issue + = + If you try to open the Details panel, gnome-control-center will crash. + It will then refuse to open. + + Upstream Bug Report + === + https://gitlab.gnome.org/GNOME/gnome-control-center/issues/285 + + See also + https://gitlab.gnome.org/GNOME/gnome-control-center/merge_requests/387 + + Original Bug Report + === + Segmentation fault while trying to run via cli , the gnome setting doesn't working when click on setting menu ProblemType: Crash DistroRelease: Ubuntu 19.04 Package: gnome-control-center 1:3.30.2-4ubuntu2 ProcVersionSignature: Ubuntu 4.19.0-12.13-generic 4.19.18 Uname: Linux 4.19.0-12-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.10-0ubuntu20 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Feb 1 14:38:32 2019 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2017-05-04 (643 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170503) ProcCmdline: gnome-control-center SegvAnalysis: - Segfault happened at: 0x7f783f52232d <__GI___libc_free+29>: mov -0x8(%rdi),%rax - PC (0x7f783f52232d) ok - source "-0x8(%rdi)" (0xfff8) not located in a known VMA region (needed readable region)! - destination "%rax" ok + Segfault happened at: 0x7f783f52232d <__GI___libc_free+29>: mov -0x8(%rdi),%rax + PC (0x7f783f52232d) ok + source "-0x8(%rdi)" (0xfff8) not located in a known VMA region (needed readable region)! + destination "%rax" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: gnome-control-center StacktraceTop: - __GI___libc_free (mem=0x1) at malloc.c:3085 - g_unix_mount_free () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 - () - () - g_type_create_instance () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 + __GI___libc_free (mem=0x1) at malloc.c:3085 + g_unix_mount_free () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 + () + () + g_type_create_instance () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: gnome-control-center crashed with SIGSEGV in __GI___libc_free() UpgradeStatus: Upgraded to disco on 2018-11-06 (92 days ago) UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo ** Description changed: Workaround == Run this command in your terminal: gsettings reset org.gnome.ControlCenter last-panel + + and then avoid opening the Details panels Issue = If you try to open the Details panel, gnome-control-center will crash. It will then refuse to open. Upstream Bug Report === https://gitlab.gnome.org/GNOME/gnome-control-center/issues/285 See also https://gitlab.gnome.org/GNOME/gnome-control-center/merge_requests/387 Original Bug Report === Segmentation fault while trying to run via cli , the gnome setting doesn't working when click on setting menu ProblemType: Crash DistroRelease: Ubuntu 19.04 Package: gnome-control-center 1:3.30.2-4ubuntu2 ProcVersionSignature: Ubuntu 4.19.0-12.13-generic 4.19.18 Uname: Linux 4.19.0-12-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.10-0ubuntu20 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Feb 1 14:38:32 2019 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2017-05-04 (643 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170503) ProcCmdline: gnome-control-center SegvAnalysis: Segfault happened at: 0x7f783f52232d <__GI___libc_free+29>: mov -0x8(%rdi),%rax PC (0x7f783f52232d) ok source "-0x8(%rdi)" (0xfff8) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: gnome-control-center StacktraceTop: __GI___libc_free (mem=0x1) at malloc.c:3085 g_unix_mount_free () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 () () g_type_create_instance () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: gnome-control-center crashed with SIGSEGV in __GI___libc_free() UpgradeStatus: Upgraded to disco on 2018-11-06 (92 days ago)
[Desktop-packages] [Bug 1814261] Re: gpm prevents loging to the console: spurious “Enter” events seems inserted
Seen on linux-image-4.15.0-44-generic and linux-image-4.15.0-45-generic. When /bin/login is exec'd by agetty it tries to read stdin and gets EAGAIN: 5640 write(2, "Password: ", 10)= 10 5640 read(0, 0x7ffcca86a7f0, 511) = -1 EAGAIN (Resource temporarily unavailable) ... 55640 write(2, "\n", 1) = 1 taking that as a failed login attempt it tries again: 55640 write(2, "hilbert login: ", 15) = 15 55640 read(0, 0x7ffcca86a160, 511) = -1 EAGAIN (Resource temporarily unavailable) eventually logging a failed login attempt reverting to linux-image-4.15.0-43-generic also fixes the problem -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gpm in Ubuntu. https://bugs.launchpad.net/bugs/1814261 Title: gpm prevents loging to the console: spurious “Enter” events seems inserted Status in gpm package in Ubuntu: Confirmed Bug description: Hello, When our servers boot, We can't login because of spurious “enter”. We have this problem on virtual and physical machines since: * kernel linux-image-4.15.0-44-generic on bionic * kernel linux-image-4.4.0-142-generic on xenial To reproduce: 1. start an ubuntu server with the specific kernel 2. install GPM 3. on a console 1. type the user name “root” 2. hit “enter” 3. wait few seconds => spurious “Enter” are send to the console 4. Stop gpm.service 5. retry to login on a console => no problem lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.1 LTS Release: 18.04 Codename: bionic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gpm/+bug/1814261/+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 1814895] Re: display blinking and showing content of screen on sleep mode
*** This bug is a duplicate of bug 1570053 *** https://bugs.launchpad.net/bugs/1570053 ** This bug has been marked a duplicate of bug 1570053 Screen content is fully visible after unlocking screen -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1814895 Title: display blinking and showing content of screen on sleep mode Status in xorg package in Ubuntu: New Bug description: In previous versions of Ubuntu(18.04) when I close the laptop by flipping my display, it automatically goes to sleep mode and to turn it on, I have to enter the password. But in this version, when I close(flip the laptop display and make it in sleep mode), and again open and hit enter, it shows a blinking screen which shows all the content of screen without login and doesn't work anything on the screen. To come out from this issue I have to press the lock button from the keyboard and then it goes to the login screen. I should go to sleep mode and should not blink and show the content. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Feb 6 18:31:06 2019 DistUpgraded: Fresh install DistroCodename: cosmic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 620 [17aa:39f1] Subsystem: Lenovo GM108M [GeForce 940MX] [17aa:39f1] InstallationDate: Installed on 2019-02-05 (0 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 005: ID 8087:0a2a Intel Corp. Bus 001 Device 004: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 003: ID 0bda:57f9 Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 80SV ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic root=UUID=978388c7-13b2-4d73-90c2-0bc7490d3638 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/09/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 3JCN30WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Torronto 5C1 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 510-15IKB dmi.modalias: dmi:bvnLENOVO:bvr3JCN30WW:bd04/09/2018:svnLENOVO:pn80SV:pvrLenovoideapad510-15IKB:rvnLENOVO:rnTorronto5C1:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapad510-15IKB: dmi.product.family: IDEAPAD dmi.product.name: 80SV dmi.product.sku: LENOVO_MT_80SV_BU_idea_FM_ dmi.product.version: Lenovo ideapad 510-15IKB dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1814895/+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 1815339] Re: Printer stopped printing paper size 4"x6" after update ghostscript to 9.26
** Changed in: gs-gpl Status: New => Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ghostscript in Ubuntu. https://bugs.launchpad.net/bugs/1815339 Title: Printer stopped printing paper size 4"x6" after update ghostscript to 9.26 Status in GS-GPL: Unknown Status in ghostscript package in Ubuntu: Triaged Bug description: I have an issue with Ghostscript and printing. I use Gutenprint for my Canon MG5440, and I cannot print a photo 4"x6" (or 6"x4"), it does not print anything, however I still able to print A4 paper size. I use Ubuntu 18.04 and Gutenprint 5.3.1. The printing fail with message: [Job 143] Start rendering... [Job 143] Processing page 1... [Job 143] Unable to open the initial device, quitting. [Job 143] Rendering completed ... [Job 143] PID 24869 (/usr/lib/cups/filter/gstoraster) stopped with status 1. ... [Job 143] printer-state-message="Filter failed" [Job 143] printer-state-reasons=none The message "Unable to open the initial device, quitting" comes from Ghostscript. When I downgrade Ghostscript to 9.22, I am again able to print 4"x6" paper size. To downgrade: apt install ghostscript=9.22~dfsg+1-0ubuntu1 libgs9=9.22~dfsg+1-0ubuntu1 libgs9-common=9.22~dfsg+1-0ubuntu1 I found similar issue for HP printer at Debian https://bugs.debian.org /cgi-bin/bugreport.cgi?bug=908205 System info: Description: Ubuntu 18.04.1 LTS Release: 18.04 ghostscript: Installed: 9.26~dfsg+0-0ubuntu0.18.04.4 Candidate: 9.26~dfsg+0-0ubuntu0.18.04.4 Versions: *** 9.26~dfsg+0-0ubuntu0.18.04.4 500 500 http://ua.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 9.22~dfsg+1-0ubuntu1 500 500 http://ua.archive.ubuntu.com/ubuntu bionic/main amd64 Packages cups: Installed: 2.2.7-1ubuntu2.3 Candidate: 2.2.7-1ubuntu2.3 Versions: *** 2.2.7-1ubuntu2.3 500 500 http://ua.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 2.2.7-1ubuntu2.2 500 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 2.2.7-1ubuntu2 500 500 http://ua.archive.ubuntu.com/ubuntu bionic/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/gs-gpl/+bug/1815339/+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 1815339]
The problem is not really to do with the memory available. Because of the way the cups device can change color space, and uses "non-standard" color spaces, we have it claim to be a DeviceN device, so ICC profile validation doesn't error out. But that, as it turns out, ends up with trying to use a default DeviceN fill_rectangle method (which returns an error, because of the nature of DeviceN we can't really provide a functional default implementation). That's what happens with RIP_MAX_CACHE = 128 Using smaller memory size, we go through the clist, and that creates a 32 bit memory device to render the bands, hence bypasses the above problem. I'll need to discuss this with Michael. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ghostscript in Ubuntu. https://bugs.launchpad.net/bugs/1815339 Title: Printer stopped printing paper size 4"x6" after update ghostscript to 9.26 Status in GS-GPL: Unknown Status in ghostscript package in Ubuntu: Triaged Bug description: I have an issue with Ghostscript and printing. I use Gutenprint for my Canon MG5440, and I cannot print a photo 4"x6" (or 6"x4"), it does not print anything, however I still able to print A4 paper size. I use Ubuntu 18.04 and Gutenprint 5.3.1. The printing fail with message: [Job 143] Start rendering... [Job 143] Processing page 1... [Job 143] Unable to open the initial device, quitting. [Job 143] Rendering completed ... [Job 143] PID 24869 (/usr/lib/cups/filter/gstoraster) stopped with status 1. ... [Job 143] printer-state-message="Filter failed" [Job 143] printer-state-reasons=none The message "Unable to open the initial device, quitting" comes from Ghostscript. When I downgrade Ghostscript to 9.22, I am again able to print 4"x6" paper size. To downgrade: apt install ghostscript=9.22~dfsg+1-0ubuntu1 libgs9=9.22~dfsg+1-0ubuntu1 libgs9-common=9.22~dfsg+1-0ubuntu1 I found similar issue for HP printer at Debian https://bugs.debian.org /cgi-bin/bugreport.cgi?bug=908205 System info: Description: Ubuntu 18.04.1 LTS Release: 18.04 ghostscript: Installed: 9.26~dfsg+0-0ubuntu0.18.04.4 Candidate: 9.26~dfsg+0-0ubuntu0.18.04.4 Versions: *** 9.26~dfsg+0-0ubuntu0.18.04.4 500 500 http://ua.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 9.22~dfsg+1-0ubuntu1 500 500 http://ua.archive.ubuntu.com/ubuntu bionic/main amd64 Packages cups: Installed: 2.2.7-1ubuntu2.3 Candidate: 2.2.7-1ubuntu2.3 Versions: *** 2.2.7-1ubuntu2.3 500 500 http://ua.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 2.2.7-1ubuntu2.2 500 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 2.2.7-1ubuntu2 500 500 http://ua.archive.ubuntu.com/ubuntu bionic/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/gs-gpl/+bug/1815339/+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 1814935] Re: Screen not locked when coming out of suspend/hibernate - Dock bar is visible
*** This bug is a duplicate of bug 1769383 *** https://bugs.launchpad.net/bugs/1769383 ** This bug has been marked a duplicate of bug 1769383 Ubuntu dock/launcher is shown on the lock screen -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/1814935 Title: Screen not locked when coming out of suspend/hibernate - Dock bar is visible Status in gnome-screensaver package in Ubuntu: New Bug description: Came back to my computer, screen was locked but application menu (dock?) was still visible. Could start and quit applications, access and select options from the right click menu on the dock. Could see running applications, and view previews of running applications that had multiple windows open. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-screensaver (not installed) ProcVersionSignature: Ubuntu 4.15.0-44.47-generic 4.15.18 Uname: Linux 4.15.0-44-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Feb 6 12:19:48 2019 InstallationDate: Installed on 2018-10-09 (120 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gnome-screensaver Symptom: security Title: Screen not locked when coming out of suspend/hibernate UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1814935/+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 1814889] Re: Dock does not change position nor icon size
It works again after a reboot. So for me, the issue is okay now -- which does not mean things like this should happen. I will let you know in case I find a way to reliably reproduce the behavior. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1814889 Title: Dock does not change position nor icon size Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: New Bug description: I cannot change the position of the dock. How to reproduce (on my system): Either: (a) open the settings -> Dock and select a different value for the dock, e.g. "Bottom", or (b) enter "gsettings set org.gnome.shell.extensions.dash-to-dock dock-position BOTTOM" in the command line Expected result: In both cases, the dock should move to the bottom of the screen. Actual result: The dock remains at the same position. Additional observations: 1. I also cannot change the icon size (only tried via GUI, not command line). 2. All the behavior is observed no matter what other settings (auto-hide, show on) I pick. 3. This describes a similar (the same?) problem: https://askubuntu.com/questions/1061924/ubuntu-wont-register-dock-settings-changes-in-18-04#new-answer Screenshots are attached. Please let me know if I should provide additional information. I am a fairly technical user, and I am willing to put in some effort to get this resolved. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell-extension-ubuntu-dock 0.9.1ubuntu18.04.3 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Feb 6 12:51:39 2019 InstallationDate: Installed on 2018-11-20 (77 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1814889/+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 1815307] Re: ipp printer isn't shown automatically - adding it errors with a CUPS internal error
Added the requested result of the ipptool query ** Attachment added: "ipp-attrs.txt" https://bugs.launchpad.net/ubuntu/+source/system-config-printer/+bug/1815307/+attachment/5238018/+files/ipp-attrs.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to system-config-printer in Ubuntu. https://bugs.launchpad.net/bugs/1815307 Title: ipp printer isn't shown automatically - adding it errors with a CUPS internal error Status in system-config-printer package in Ubuntu: Incomplete Bug description: System: Ubuntu 18.04 system-config-printer version: 1.5.11-1ubuntu printer: Canon iP7250 I expect to be able to see the printer in the panel just as 'lpstat -l -e' or 'driverless' can see them, without the need to especially add a new printer. And if I do need to add it (don't see why that should be the case, but still), I expect that choosing the printer's name under network would result in adding the printer. What happened instead: Canon iP7250 isn't shown in the Printers panel, clicking on add and expanding the network options - it is shown, but when trying to add it (either driverless IPP, LPD via DNS-SD or IPP via DNS-SD) it gives an error about CUPS internal error. `$ lpstat -l -e` gives `Canon_iP7200_series network none ipp://Canon%20iP7200%20series._ipp._tcp.local/` So the system does see it, and `lp -d Canon_iP7200_series /etc/nsswitch.conf` does print (and for a minute the printer is shown in the Printers panel - but then disappears). I can add it by *not* clicking on the printer's name under Network, but rather, click on ipp printer and manually choose Canon -> iP7200 -> CUPS+Gutenprint driver (and not the recommended driverless option - which, if I choose results in that same cryptic error I get when trying to add the printer by clicking on it, as described above). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/system-config-printer/+bug/1815307/+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 1810382] Re: Gnome software error posting a review for snap app
It looks like that since https://gitlab.gnome.org/GNOME/gnome- software/commit/e54b31cc85ddef6f9579cb85bbdf53dbb9d9091d snaps are no longer marked AS_APP_QUIRK_NOT_REVIEWABLE. This because ODRS supports Snap Reviews. Unfortunately, ODRS plugin is disabled for you (and maybe for all cosmic users?) while ubuntu-reviews plugin is still installed/enabled hence the issue. @robert-ancell what's the proper way to fix this? Maybe we should enable ODRS in cosmic and disable ubuntu- reviews? ** Changed in: gnome-software (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1810382 Title: Gnome software error posting a review for snap app Status in gnome-software package in Ubuntu: Triaged Bug description: Received msg: Sorry, something went wrong: Got unknown content type text/html from reviews.ubuntu.com posting a review for snap app. this does not happen for 'normal' apps ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gnome-software 3.30.2-0ubuntu8 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Jan 3 09:06:57 2019 ExecutablePath: /usr/bin/gnome-software InstallationDate: Installed on 2018-10-22 (73 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-limba N/A gnome-software-plugin-snap3.30.2-0ubuntu8 SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1810382/+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 1737750] Re: nvidia-graphics-drivers fail to build [error: implicit declaration of function ‘init_timer’]
Word to the wise: If you successfully compiled the driver, don't update your 18.04 system to the HWE stack. The driver didn't seem to work with the kernel from 18.10 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1737750 Title: nvidia-graphics-drivers fail to build [error: implicit declaration of function ‘init_timer’] Status in nvidia-graphics-drivers-304 package in Ubuntu: In Progress Status in nvidia-graphics-drivers-340 package in Ubuntu: Fix Released Bug description: Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic-canonical-kernel-team-bootstrap/bionic/amd64/n/nvidia-graphics-drivers-304/20171212_030744_5105c@/log.gz i386: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic-canonical-kernel-team-bootstrap/bionic/i386/n/nvidia-graphics-drivers-304/20171212_014232_5105c@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1737750/+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 1815284] Re: Middle click down opens file
Thank you for your bug report. removing that menu was an upstream decision, if you disagree please report the request to them on https://gitlab.gnome.org/GNOME/nautilus/issues ** Changed in: nautilus (Ubuntu) Importance: Undecided => Low ** Changed in: nautilus (Ubuntu) Status: Confirmed => Opinion -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1815284 Title: Middle click down opens file Status in nautilus package in Ubuntu: Opinion Bug description: Ubuntu 18.08 here. In Ubuntu 16.04 I could middle click on a file in Nautilus then drag and drop it to another folder. After that a small dialog appeared if I want to copy or move the file. Now when I press middle click on a file, the file opens immediately and although I can move it to another folder, there's no choice if I want to copy or move the file. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1815284/+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 1810382] Re: Gnome software error posting a review for snap app
Do you always get that "write a review" button for snaps? It's weird, that control is supposed to be hidden there :/ ** Changed in: gnome-software (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1810382 Title: Gnome software error posting a review for snap app Status in gnome-software package in Ubuntu: New Bug description: Received msg: Sorry, something went wrong: Got unknown content type text/html from reviews.ubuntu.com posting a review for snap app. this does not happen for 'normal' apps ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gnome-software 3.30.2-0ubuntu8 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Jan 3 09:06:57 2019 ExecutablePath: /usr/bin/gnome-software InstallationDate: Installed on 2018-10-22 (73 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-limba N/A gnome-software-plugin-snap3.30.2-0ubuntu8 SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1810382/+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 1722886] Re: Include logs, monitors.xml and org.gnome.desktop.* settings in the apport-retrace data
** Changed in: gnome-shell (Ubuntu) Assignee: Didier Roche (didrocks) => (unassigned) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1722886 Title: Include logs, monitors.xml and org.gnome.desktop.* settings in the apport-retrace data Status in gnome-shell package in Ubuntu: Confirmed Bug description: When a bug is submitted to ubuntu about gnome-shell it would be convenient to have such settings. Monitors.xml is quite important to understand the configuration for mutter-related crashes, while other desktop settings (to be filtered- out) could be needed too. Ah, also the logs from journalctl /usr/bin/gnome-shell -b -o short-iso To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1722886/+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 1798612] Re: OSD shows volume level = 100% even if volume > 100% on first press
This is merged and released ** Changed in: gnome-shell (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1798612 Title: OSD shows volume level = 100% even if volume > 100% on first press Status in gnome-shell package in Ubuntu: Fix Released Bug description: [ Impact ] Display bug in volume OSD on volume keypress if volume > 100% (amplified) [ Test Case ] 1. Ensure OSD is not displayed on screen avec volume > 100% via the amplified setting. 2. Press volume + or volume - on your keyboard. -> OSD is shown, but volume level is always 100%. 3. Consecutive key press displays correct volume level. Update to new gnome-shell package and ensure that when OSD is displayed, the volume bar is representing current sound volume at step 2. (so > 100%) [ Regression potential ] If this code change triggers any error, the OSD isn't displayed, but the Shell stays up. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1798612/+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 1799974] Re: [MIR] gupnp
** Changed in: gupnp (Ubuntu) Assignee: Didier Roche (didrocks) => (unassigned) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gupnp in Ubuntu. https://bugs.launchpad.net/bugs/1799974 Title: [MIR] gupnp Status in gupnp package in Ubuntu: New Bug description: * Availability Builds on all supported architectures in Ubuntu and on sync from Debian, the package was in main in the past and needs to be re- promoted * Rationale We would like to enable dlna sharing of media files, which is a GNOME upstream feature and relying on rygel which depends on the gupnp libraries * Security There is an old CVE recorded/fixed https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2009-2174 * Quality assurance - the desktop-packages team is subscribed to the package - the bug lists in upstream, the Debian PTS and launchpad are empty - upstream has a testsuit which is used during build * Dependendies The package uses standard desktop libraries that are already in main * Standards compliance the package is using standard packaging (dh10), the standards-version is 4.2, the package is in sync from Debian * Maintainance Upstream is active and the desktop team is going to look after the package in ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gupnp/+bug/1799974/+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 1815317] Re: Update gnome-online-accounts to 3.31.90
** Changed in: gnome-online-accounts (Ubuntu) Assignee: (unassigned) => Andrea Azzarone (azzar1) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1815317 Title: Update gnome-online-accounts to 3.31.90 Status in gnome-online-accounts package in Ubuntu: New Bug description: We should update gnome-online-accounts to 3.31.90 (Debian experimental has the update). GNOME has dropped its .png icons and replaced them with 128px .svg's. If we did the same, we could drop our binary patch since an .svg isn't a binary file. GNOME also includes a 16px symbolic .svg but I don't think those are used right now. So although getting the 128px .svg from Canonical Design isn't technically a blocker, I think it would be nice to get it for consistency (and simplifying our patches a bit). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1815317/+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
Re: [Desktop-packages] [Bug 1812474] Re: /usr/lib/evolution/evolution-addressbook-factory regularly takes 100% CPU and 100% RAM for a while, making all the system unresponsive
Oh I wasn't notified about Milan's answer. Sure I'll reinstall the addressbook (I've deleted it for now) and get a backtrace - in my copious spare time. Cheers, Xav -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1812474 Title: /usr/lib/evolution/evolution-addressbook-factory regularly takes 100% CPU and 100% RAM for a while, making all the system unresponsive Status in evolution-data-server package in Ubuntu: Incomplete Bug description: /usr/lib/evolution/evolution-addressbook-factory regularly takes 100% CPU and 100% RAM for a while, making all the system unresponsive; the GUI doesn't respond (gnome-shell's clock is stopped, the mouse pointer is stopped) and it lasts for a few minutes, then goes back to normal. If I wait long enough, the addressbook crashes (not enough memory ?). ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: evolution-data-server 3.30.1-1build1 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: GNOME Date: Sat Jan 19 09:59:18 2019 ExecutablePath: /usr/lib/evolution/evolution-data-server/evolution-alarm-notify InstallationDate: Installed on 2017-01-09 (740 days ago) InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Release amd64 (20161012.1) ProcEnviron: PATH=(custom, user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: evolution-data-server UpgradeStatus: Upgraded to cosmic on 2018-10-19 (92 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1812474/+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 1799614] Re: Use new media API
** Changed in: snapd-glib (Ubuntu Bionic) Assignee: (unassigned) => Robert Ancell (robert-ancell) ** Changed in: snapd-glib (Ubuntu Cosmic) Assignee: (unassigned) => Robert Ancell (robert-ancell) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1799614 Title: Use new media API Status in gnome-software package in Ubuntu: Fix Released Status in snapd-glib package in Ubuntu: Fix Released Status in gnome-software source package in Xenial: Fix Committed Status in gnome-software source package in Bionic: Fix Committed Status in snapd-glib source package in Bionic: In Progress Status in gnome-software source package in Cosmic: Fix Committed Status in snapd-glib source package in Cosmic: In Progress Bug description: [Impact] snapd now provides 'media' which replaces the old 'screenshots' data. We need to migrate to this as the old screenshot data will be removed in the future. [Test Case] Run gnome-software with updated snapd-glib and confirm that screenshots and promoted snap banners continue to work. [Regression Potential] Possibility of new errors being introduced in updated code paths. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1799614/+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 1600622] Re: Screen doesn't lock or go to sleep when certain Chrome tabs are open
Submitted a new Chromium bug/feature request (ignore comment #22 above):
https://bugs.chromium.org/p/chromium/issues/detail?id=931235
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-session in Ubuntu.
https://bugs.launchpad.net/bugs/1600622
Title:
Screen doesn't lock or go to sleep when certain Chrome tabs are open
Status in gnome-session package in Ubuntu:
Confirmed
Bug description:
$ lsb_release -rd
Description: Ubuntu 16.04 LTS
Release: 16.04
$ apt-cache policy gnome-session-bin
gnome-session-bin:
Installed: 3.18.1.2-1ubuntu1.16.04.1
Candidate: 3.18.1.2-1ubuntu1.16.04.1
Version table:
*** 3.18.1.2-1ubuntu1.16.04.1 500
500 http://es.archive.ubuntu.com/ubuntu xenial-updates/main amd64
Packages
100 /var/lib/dpkg/status
3.18.1.2-1ubuntu1 500
500 http://es.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
I'm using gnome-session-flashback
What happens:
The screen doesn't lock when having certain pages in Chrome tabs
Expected:
The screen should lock after the configured timeout in settings.
I've been having this issue sice before 14.04, which I recently
upgraded (fresh install) to 16.04.
After fresh install, the screen would turn down and lock the computer
after 10 minutes (or whatever time I setup). At one point it stopped
working. The screen never shuts down unless I manually lock the
session with CTRL-ALT-L.
I've followed the steps in
https://wiki.ubuntu.com/DebuggingScreenLocking#Debugging_procedure
The culprit seems to be that Chrome issues some suspend inhibitions
through dbus when doing certain operations. Many people find this
problem when using Yahoo Mail. I can reproduce it with Odoo. I'm
pretty sure that Chrome is doing something else of what i've found
out.
1) Gnome screen saver works correctly. I can trigger it manually with:
$ gnome-screensaver-command -a
2) Gnome screen saver never receives the "session idle" status
callback.
3) When Chrome is not running, I can manually inhibit the idle status:
$ gnome-session-inhibit --app-id test --reason "manual idle inhibit"
--inhibit-only --inhibit idle:suspend
Inhibiting until Ctrl+C is pressed...
4) I can query the inhibitors:
$ dbus-send --print-reply --dest=org.gnome.SessionManager
/org/gnome/SessionManager org.gnome.SessionManager.GetInhibitorsmethod return
time=1468170482.066533 sender=:1.19 -> destination=:1.1315311 serial=1329103
reply_serial=2
array [
object path "/org/gnome/SessionManager/Inhibitor1686"
]
$ gdbus call --session --dest org.gnome.SessionManager --object-path
/org/gnome/SessionManager/Inhibitor1686 --method
org.gnome.SessionManager.Inhibitor.GetAppId
('test',)
$ gdbus call --session --dest org.gnome.SessionManager --object-path
/org/gnome/SessionManager/Inhibitor1686 --method
org.gnome.SessionManager.Inhibitor.GetReason
('manual idle inhibit',)
$ gdbus call --session --dest org.gnome.SessionManager --object-path
/org/gnome/SessionManager/Inhibitor1686 --method
org.gnome.SessionManager.Inhibitor.GetFlags
(uint32 12,)
12=4(suspend) + 8(idle)
5) When testing, I can inhibit for 70 seconds, idle timeout being 60
(1 minute). After these 70 seconds pass, the screen locks.
6) Regarding Chrome, this is the information I get when querying the
inhibitor:
GetAppId: ('/usr/bin/google-chrome-stable',)
GetReason: ('Uploading data to 10.200.0.163',)
GetFlags: (uint32 4,)
The flags just inhibits suspend, not locking or entering powersaving
mode.
This inhibitor seems to stay for 10-15 seconds, then goes away for
another 30-60 seconds. The screen NEVER locks when this tab is open.
No matter the inhibitor is present or not.
I'm not sure where to go on. If it's a Chrome bug it must be using
other mechanisms to prevent the idle timeout. Any ideas on what to
look for?
Julian.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1600622/+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 1777994] Re: the header xcb/xinput.h is missing
** Changed in: libxcb (Ubuntu Bionic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libxcb in Ubuntu. https://bugs.launchpad.net/bugs/1777994 Title: the header xcb/xinput.h is missing Status in libxcb package in Ubuntu: Fix Released Status in libxcb source package in Bionic: Fix Committed Bug description: [Impact] Allow Qt 5.12 to be compiled with full input support. This allows applications to be built using complex input devices such as drawing pads. This is used in e.g Krita which KDE builds into a Snap package for distribution. Currently Krita does not work with pen input devices with pressure sensitivity. [Test Case] Install Krita with Qt 5.12 from current Snap and note how pressure sensitivity does not work. [Regression Potential] None that I can see, it's just packaging a few new header files. I suspect this means there should be another package, libxcb-xinput-dev perhaps? I already did sudo apt install "libxcb*dev" to get all related dev packages, but none of them provide xcb/xinput.h. The result is that when building Qt from source, it's necessary to use a copy of this file which Qt provides (qtbase/src/3rdparty/xcb/include/xcb/xinput.h), because it's missing from the system. So if you don't give the option -qt-xcb to configure, then Qt will be built without multi-touch support. https://bugreports.qt.io/browse/QTBUG-69045 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libxcb1-dev 1.13-1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Jun 21 08:32:12 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 620 [17aa:3802] Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0cf3:e300 Atheros Communications, Inc. Bus 001 Device 003: ID 06cb:0081 Synaptics, Inc. Bus 001 Device 002: ID 04f2:b5da Chicony Electronics Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 80Y7 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-23-generic root=ZFS=rpool/ROOT/ubuntu ro SourcePackage: libxcb UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/22/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 5NCN38WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo YOGA 920-13IKB dmi.modalias: dmi:bvnLENOVO:bvr5NCN38WW:bd02/22/2018:svnLENOVO:pn80Y7:pvrLenovoYOGA920-13IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct31:cvrLenovoYOGA920-13IKB: dmi.product.family: YOGA 920-13IKB dmi.product.name: 80Y7 dmi.product.version: Lenovo YOGA 920-13IKB dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxcb/+bug/1777994/+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 1767660] Re: Regression 16.04 LTS to 18.04 LTS: Contour Design RollerMouse double click button no longer results in a double click event
That bug would be good to fix for bionic but desktop team as the owner of the component doesn't want to commit to that so deleting the bionic target and tagging rls-bb-notfixing (it doesn't mean it can't/will not be fixed though) ** No longer affects: libinput (Ubuntu Bionic) ** Tags added: rls-bb-notfixing -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libinput in Ubuntu. https://bugs.launchpad.net/bugs/1767660 Title: Regression 16.04 LTS to 18.04 LTS: Contour Design RollerMouse double click button no longer results in a double click event Status in libinput package in Ubuntu: Fix Released Bug description: https://gitlab.freedesktop.org/libinput/libinput/issues/204 --- ### Expected behaviour My "Contour Design RollerMouse Free 2" has a specific button for double click. This button should with one physical click result in double click (button press, button release, button press and button release). This works as expected without issues in Ubuntu 16.04 LTS 4.4.0-119-generic #143-Ubuntu SMP Mon Apr 2 16:08:24 UTC 2018 x86_64 ### Experienced behaviour Only one mouse click is registered (button press and button release). Tested with "xev" and "xinput test" ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-20-generic 4.15.0-20.21 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Apr 28 16:26:08 2018 InstallationDate: Installed on 2018-04-27 (1 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: linux-signed UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1767660/+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 1772811] Re: different behaviors for switch display mode between xenial and bionic
** Changed in: mutter (Ubuntu Bionic) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) ** Changed in: mutter (Ubuntu Disco) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1772811 Title: different behaviors for switch display mode between xenial and bionic Status in OEM Priority Project: Triaged Status in gnome-shell package in Ubuntu: Fix Released Status in mutter package in Ubuntu: Triaged Status in gnome-shell source package in Bionic: New Status in mutter source package in Bionic: New Status in gnome-shell source package in Disco: Fix Released Status in mutter source package in Disco: Triaged Bug description: When the "Fn lock" is enabled, we can switch the video mode by one key: video-key (Fn+F8). But, the key event is too frequent. It's hard to select the wanted video mode. Reproduce steps: Press down the Video-out hotkey Expected results: User can select Video mode precisely by Video-out hotkey Actual results: The speed of switch video mode is too fast makes can not select Video mode precisely Notebook: XPS 13 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1772811/+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 1815615] [NEW] Xorg freeze
Public bug reported: [ 290.765205] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring sdma0 timeout, signaled seq=20358, emitted seq=20361 [ 290.765212] [drm] GPU recovery disabled. [ 485.063911] INFO: task kworker/u32:1:50 blocked for more than 120 seconds. [ 485.063922] Tainted: G OE 4.20.7-042007-generic #201902061234 [ 485.063925] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 485.063929] kworker/u32:1 D050 2 0x8000 [ 485.063952] Workqueue: events_unbound commit_work [drm_kms_helper] [ 485.063955] Call Trace: [ 485.063967] __schedule+0x29e/0x840 [ 485.063971] schedule+0x2c/0x80 [ 485.063974] schedule_preempt_disabled+0xe/0x10 [ 485.063977] __ww_mutex_lock.isra.11+0x3d8/0x760 [ 485.063981] __ww_mutex_lock_slowpath+0x16/0x20 [ 485.063983] ww_mutex_lock+0x34/0x50 [ 485.064115] amdgpu_dm_do_flip+0xeb/0x3a0 [amdgpu] [ 485.064213] amdgpu_dm_atomic_commit_tail+0x738/0xe20 [amdgpu] [ 485.064216] ? __switch_to_asm+0x40/0x70 [ 485.064219] ? __switch_to_asm+0x34/0x70 [ 485.064221] ? wait_for_completion_timeout+0x38/0x140 [ 485.064223] ? __switch_to_asm+0x40/0x70 [ 485.064225] ? __switch_to_asm+0x34/0x70 [ 485.064227] ? __switch_to_asm+0x40/0x70 [ 485.064239] commit_tail+0x42/0x70 [drm_kms_helper] [ 485.064248] commit_work+0x12/0x20 [drm_kms_helper] [ 485.064253] process_one_work+0x20f/0x410 [ 485.064256] worker_thread+0x34/0x400 [ 485.064258] kthread+0x120/0x140 [ 485.064261] ? pwq_unbound_release_workfn+0xd0/0xd0 [ 485.064263] ? __kthread_parkme+0x70/0x70 [ 485.064266] ret_from_fork+0x22/0x40 [ 485.064463] INFO: task kworker/u32:14:2793 blocked for more than 120 seconds. [ 485.064467] Tainted: G OE 4.20.7-042007-generic #201902061234 [ 485.064468] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 485.064470] kworker/u32:14 D0 2793 2 0x8000 [ 485.064483] Workqueue: events_unbound commit_work [drm_kms_helper] [ 485.064484] Call Trace: [ 485.064487] __schedule+0x29e/0x840 [ 485.064489] schedule+0x2c/0x80 [ 485.064491] schedule_timeout+0x258/0x360 [ 485.064584] ? optc1_get_crtc_scanoutpos+0x69/0xa0 [amdgpu] [ 485.064590] dma_fence_default_wait+0x20a/0x280 [ 485.064592] ? dma_fence_release+0xa0/0xa0 [ 485.064595] dma_fence_wait_timeout+0xe7/0x110 [ 485.064598] reservation_object_wait_timeout_rcu+0x201/0x340 [ 485.064663] ? amdgpu_get_vblank_counter_kms+0x111/0x160 [amdgpu] [ 485.064757] amdgpu_dm_do_flip+0x12c/0x3a0 [amdgpu] [ 485.064852] amdgpu_dm_atomic_commit_tail+0x738/0xe20 [amdgpu] [ 485.064855] ? __switch_to_asm+0x40/0x70 [ 485.064857] ? __switch_to_asm+0x34/0x70 [ 485.064859] ? wait_for_completion_timeout+0x38/0x140 [ 485.064861] ? __switch_to_asm+0x40/0x70 [ 485.064863] ? __switch_to_asm+0x34/0x70 [ 485.064865] ? __switch_to_asm+0x40/0x70 [ 485.064876] commit_tail+0x42/0x70 [drm_kms_helper] [ 485.064886] commit_work+0x12/0x20 [drm_kms_helper] [ 485.064889] process_one_work+0x20f/0x410 [ 485.064891] worker_thread+0x34/0x400 [ 485.064894] kthread+0x120/0x140 [ 485.064896] ? pwq_unbound_release_workfn+0xd0/0xd0 [ 485.064898] ? __kthread_parkme+0x70/0x70 [ 485.064901] ret_from_fork+0x22/0x40 [ 538.507722] r8169 :02:00.0: invalid short VPD tag 00 at offset 1 [ 538.507750] pcieport :00:01.3: AER: Multiple Corrected error received: :00:01.0 [ 538.507772] pcieport :00:01.3: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Transmitter ID) [ 538.507781] pcieport :00:01.3: device [1022:15d3] error status/mask=1100/6000 [ 538.507787] pcieport :00:01.3:[ 8] Rollover [ 538.507791] pcieport :00:01.3:[12] Timeout [ 574.828588] RTW: WARN [TXFOVW] [ 574.831312] RTW: WARN [TXFOVW] [ 605.900149] INFO: task kworker/u32:1:50 blocked for more than 120 seconds. [ 605.900156] Tainted: G OE 4.20.7-042007-generic #201902061234 [ 605.900159] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 605.900162] kworker/u32:1 D050 2 0x8000 [ 605.900183] Workqueue: events_unbound commit_work [drm_kms_helper] [ 605.900185] Call Trace: [ 605.900195] __schedule+0x29e/0x840 [ 605.900199] schedule+0x2c/0x80 [ 605.900202] schedule_preempt_disabled+0xe/0x10 [ 605.900204] __ww_mutex_lock.isra.11+0x3d8/0x760 [ 605.900208] __ww_mutex_lock_slowpath+0x16/0x20 [ 605.900210] ww_mutex_lock+0x34/0x50 [ 605.900322] amdgpu_dm_do_flip+0xeb/0x3a0 [amdgpu] [ 605.900420] amdgpu_dm_atomic_commit_tail+0x738/0xe20 [amdgpu] [ 605.900423] ? __switch_to_asm+0x40/0x70 [ 605.900425] ? __switch_to_asm+0x34/0x70 [ 605.900428] ? wait_for_completion_timeout+0x38/0x140 [ 605.900430] ? __switch_to_asm+0x40/0x70 [ 605.900432] ? __switch_to_asm+0x34/0x70 [ 605.900434] ? __switch_to_asm+0x40/0x70 [ 605.900445] commit_tail+0x42/0x70 [drm_kms_helper] [ 605.900455]
[Desktop-packages] [Bug 1815610] [NEW] Purple screen while booting
Public bug reported: I have to enter nouveau.modeset=0 every time I login ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 NonfreeKernelModules: kpatch_livepatch_Ubuntu_4_15_0_29_31_generic_42 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Feb 12 19:33:23 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Device [8086:591b] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:8259] Subsystem: Hewlett-Packard Company GP107M [GeForce GTX 1050 Ti Mobile] [103c:8259] InstallationDate: Installed on 2019-02-11 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bus 001 Device 002: ID 1bcf:2c87 Sunplus Innovation Technology Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP OMEN by HP Laptop ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-29-generic root=UUID=06a4ab36-0cf8-4e0c-9a2d-acc278a88e47 ro quiet splash vt.handoff=1 nouveau.modeset=0 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/07/2017 dmi.bios.vendor: Insyde dmi.bios.version: F.36 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8259 dmi.board.vendor: HP dmi.board.version: 83.46 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.36:bd04/07/2017:svnHP:pnOMENbyHPLaptop:pvrType1ProductConfigId:rvnHP:rn8259:rvr83.46:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Omen dmi.product.name: OMEN by HP Laptop dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic possible-manual-nvidia-install ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1815610 Title: Purple screen while booting Status in xorg package in Ubuntu: New Bug description: I have to enter nouveau.modeset=0 every time I login ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 NonfreeKernelModules: kpatch_livepatch_Ubuntu_4_15_0_29_31_generic_42 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Feb 12 19:33:23 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Device [8086:591b] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:8259] Subsystem: Hewlett-Packard Company GP107M [GeForce GTX 1050 Ti Mobile] [103c:8259] InstallationDate: Installed on 2019-02-11 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bus 001 Device 002: ID 1bcf:2c87 Sunplus Innovation Technology Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP OMEN by HP Laptop ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-29-generic root=UUID=06a4ab36-0cf8-4e0c-9a2d-acc278a88e47 ro quiet splash vt.handoff=1 nouveau.modeset=0 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/07/2017 dmi.bios.vendor: Insyde dmi.bios.version: F.36 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8259 dmi.board.vendor: HP dmi.board.version: 83.46 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias:
[Desktop-packages] [Bug 1789165] Re: Cannot select from web-context menus with mouse click, only with keyboard
Apparently, the problem still persists on some sites, like creating new
folders on Google Drive. So I debugged the issue and finally found that
this problem is created by the "Enable Right Click and Copy" plugin.
That plugin seems anyway to be out of date so I removed it. Should get
used to checking plugins before reporting a problem. Thx
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1789165
Title:
Cannot select from web-context menus with mouse click, only with
keyboard
Status in firefox package in Ubuntu:
Fix Released
Bug description:
On many web-pages that have drop-down menus, I cannot select from them
by mouse. For example, I cannot change the language in google
translate: Goto https://translate.google.com/, select the triangle
next to the default languages, hover over any language and left click
to select it. The drop-down menu disappears, but the language is not
changed. The language is properly selected, when I use the cursor and
enter keys.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: firefox 61.0.1+build1-0ubuntu0.18.04.1
ProcVersionSignature: Ubuntu 4.13.0-43.48-generic 4.13.16
Uname: Linux 4.13.0-43-generic x86_64
AddonCompatCheckDisabled: False
ApportVersion: 2.20.9-0ubuntu7.3
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC1: pia2615 F pulseaudio
/dev/snd/controlC0: pia2615 F pulseaudio
BuildID: 20180704192850
Channel: Unavailable
CurrentDesktop: GNOME
Date: Mon Aug 27 08:33:13 2018
ForcedLayersAccel: False
IncompatibleExtensions:
English (South Africa) Language Pack - langpack-en...@firefox.mozilla.org
English (GB) Language Pack - langpack-en...@firefox.mozilla.org
Default - {972ce4c6-7e08-4474-a285-3208198ce6fd}
InstallationDate: Installed on 2015-11-05 (1025 days ago)
InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
IpRoute:
default via 172.18.63.254 dev wlan0 proto dhcp metric 600
169.254.0.0/16 dev wlan0 scope link metric 1000
172.18.32.0/19 dev wlan0 proto kernel scope link src 172.18.35.9 metric 600
MostRecentCrashID: bp-e5b6347e-45b3-473e-b0cb-4a76a2160808
Plugins: Shockwave Flash - /usr/lib/gnash/libgnashplugin.so
(browser-plugin-gnash)
PrefErrors: Unexpected character ',' whilst parsing int @
/usr/lib/firefox/defaults/pref/vendor-gre.js:8
PrefSources: prefs.js
Profiles: Profile0 (Default) - LastVersion=61.0.1/20180704192850 (In use)
RelatedPackageVersions: browser-plugin-gnash 0.8.11~git20160608-1.4
RunningIncompatibleAddons: True
SourcePackage: firefox
SubmittedCrashIDs:
bp-e5b6347e-45b3-473e-b0cb-4a76a2160808
bp-d8752932-5027-4cfe-a7c0-7901b2160428
bp-1e1c789e-1cf7-4052-81d1-4e73d2160331
bp-0782c33a-b764-45f8-a245-789632150404
bp-fa6dc123-c013-4c2c-b299-a1de32140411
UpgradeStatus: Upgraded to bionic on 2018-05-24 (94 days ago)
dmi.bios.date: 04/15/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 4.6.5
dmi.board.asset.tag: Tag 12345
dmi.board.name: W230SS
dmi.board.vendor: Notebook
dmi.board.version: Not Applicable
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 9
dmi.chassis.vendor: Notebook
dmi.chassis.version: N/A
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd04/15/2014:svnNotebook:pnW230SS:pvrNotApplicable:rvnNotebook:rnW230SS:rvrNotApplicable:cvnNotebook:ct9:cvrN/A:
dmi.product.family: Not Applicable
dmi.product.name: W230SS
dmi.product.version: Not Applicable
dmi.sys.vendor: Notebook
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1789165/+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 1671974] Re: CUPS - Excessive Amounts of UDP Multicast Traffic for BJNP
I have just found the following message in syslog: Feb 12 13:25:56 samsung5-ubuntu colord-sane: message repeated 2 times: [ [bjnp] create_broadcast_socket: ERROR - bind socket to local address failed - Cannot assign requested address] that matches: ● colord.service - Manage, Install and Generate Color Profiles Loaded: loaded (/lib/systemd/system/colord.service; static; vendor preset: enabled) Active: active (running) since Tue 2019-02-12 02:30:41 CET; 11h ago Main PID: 2098 (colord) Tasks: 3 (limit: 4915) Memory: 14.9M CGroup: /system.slice/colord.service └─2098 /usr/lib/colord/colord Feb 12 02:30:41 samsung5-ubuntu systemd[1]: Starting Manage, Install and Generate Color Profiles... Feb 12 02:30:41 samsung5-ubuntu systemd[1]: Started Manage, Install and Generate Color Profiles. Feb 12 02:30:42 samsung5-ubuntu colord[2098]: failed to get session [pid 2118]: No data available Feb 12 02:30:42 samsung5-ubuntu colord-sane[2240]: [bjnp] create_broadcast_socket: ERROR - bind socket to local address failed - Cannot assign requested address This lead me to investigate the SANE scanner and more specifically /etc/sane.d/dll.conf which seems to list image scanner hardware drivers, including canon ones. However, commenting out 'net' or all canon-related lines does not change anything: # systemctl restart colord # systemctl status colord ● colord.service - Manage, Install and Generate Color Profiles Loaded: loaded (/lib/systemd/system/colord.service; static; vendor preset: enabled) Active: active (running) since Tue 2019-02-12 14:21:12 CET; 4s ago Main PID: 31838 (colord) Tasks: 4 (limit: 4915) Memory: 8.0M CGroup: /system.slice/colord.service └─31838 /usr/lib/colord/colord Feb 12 14:21:12 samsung5-ubuntu systemd[1]: Starting Manage, Install and Generate Color Profiles... Feb 12 14:21:12 samsung5-ubuntu systemd[1]: Started Manage, Install and Generate Color Profiles. Feb 12 14:21:13 samsung5-ubuntu colord-sane[31859]: [bjnp] create_broadcast_socket: ERROR - bind socket to local address failed - Cannot assign requested address -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1671974 Title: CUPS - Excessive Amounts of UDP Multicast Traffic for BJNP Status in cups package in Ubuntu: Confirmed Bug description: It appears that the cups-browsed service as of Xenial (version 1.8.3-2ubuntu3.1) sends an excessive amount of UDP multicast requests for ports 8610 (Canon MFNP) and 8612 (Canon BJNP) under unexpected conditions and regardless of a presence or lack of Canon printer devices on the network. This is manifested by enabling UFW, and observing multicast requests being blocked that are sent from the host machine's network IPv4 or IPv6 address to the multicast address, e.g. [UFW BLOCK] IN=wlp3s0 OUT= MAC= SRC= DST=ff02:::::::0001 LEN=64 TC=0 HOPLIMIT=1 FLOWLBL=96642 PROTO=UDP SPT=8612 DPT=8612 LEN=24 IN= OUT=wlan0 SRC=192.168.90.45 DST=192.168.91.255 LEN=44 TOS=0x00 PREC=0x00 TTL=64 ID=7742 DF PROTO=UDP SPT=8612 DPT=8610 LEN=24 Users have observed that the requests can be reproduced when any USB device is plugged/unplugged into the computer, regardless of whether the device has anything to do with printing: https://twitter.com/gertvdijk/status/621790755758178304 https://bugs.kali.org/view.php?id=3094 Just Googling "udp 8612", shows are a large number of results on different websites of people who have observed this behaviour in firewall and traffic logs, and have noticed that it may contribute to network slowdown and latency: https://askubuntu.com/questions/867739/what-is-this-traffic/867786 https://serverfault.com/questions/667376/watchguard-blocking-internal-udp-packets https://jehurst.wordpress.com/2016/01/22/small-victories/ recommends disabling the cups-browsed service to stop these requests: systemctl stop cups-browsed.service systemctl disable cups-browsed.service There are probably two things to address here: 1. Connecting any USB device should not cause these requests unless the device is actually a printer or directly related to printing. 2. Requests independent of connecting USB devices should be rate limited to a degree and/or should be dependent on the actual presence of a Canon printer configured on the network. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1671974/+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 1731594] Re: Ubuntu Dock creates a window button called "OpenGL Renderer" when GNOME Web is playing a video.
*** This bug is a duplicate of bug 1766140 *** https://bugs.launchpad.net/bugs/1766140 ** This bug has been marked a duplicate of bug 1766140 OpenGL Renderer window appears in tab list when playing a video -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1731594 Title: Ubuntu Dock creates a window button called "OpenGL Renderer" when GNOME Web is playing a video. Status in epiphany-browser package in Ubuntu: New Status in gnome-shell package in Ubuntu: New Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: New Bug description: Ubuntu Dock creates a window button called "OpenGL Renderer" when GNOME Web (Epiphany Browser) is playing a video which goes away when you go to a different page that isn't playing a video. Since this shouldn't be happening, is there a way to blacklist it so that it doesn't show up on the Dock? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/epiphany-browser/+bug/1731594/+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 1766140] Re: OpenGL Renderer window appears in tab list when playing a video
Most probably Wayland-specific. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gst-plugins-base1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1766140 Title: OpenGL Renderer window appears in tab list when playing a video Status in epiphany-browser package in Ubuntu: Confirmed Status in gst-plugins-base1.0 package in Ubuntu: Confirmed Bug description: Every time a web page plays a video in Epiphany, a window named "OpenGL Renderer" appears in the gnome-shell alt-tab list (but not in the overview), one for each video. If I have several pages open with several videos, I get several of these phantom windows. Selecting the window in the list does nothing. This started happening sometime during the beta, it didn't happen under 17.10 or after first upgrading to 18.04. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: epiphany-browser 3.28.1-1ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu6 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Apr 23 10:51:07 2018 InstallationDate: Installed on 2015-07-22 (1005 days ago) InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 (20150422) SourcePackage: epiphany-browser UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/epiphany-browser/+bug/1766140/+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 1766140] Re: OpenGL Renderer window appears in tab list when playing a video
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gst-plugins-base1.0 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gst-plugins-base1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1766140 Title: OpenGL Renderer window appears in tab list when playing a video Status in epiphany-browser package in Ubuntu: Confirmed Status in gst-plugins-base1.0 package in Ubuntu: Confirmed Bug description: Every time a web page plays a video in Epiphany, a window named "OpenGL Renderer" appears in the gnome-shell alt-tab list (but not in the overview), one for each video. If I have several pages open with several videos, I get several of these phantom windows. Selecting the window in the list does nothing. This started happening sometime during the beta, it didn't happen under 17.10 or after first upgrading to 18.04. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: epiphany-browser 3.28.1-1ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu6 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Apr 23 10:51:07 2018 InstallationDate: Installed on 2015-07-22 (1005 days ago) InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 (20150422) SourcePackage: epiphany-browser UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/epiphany-browser/+bug/1766140/+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 1766140] Re: OpenGL Renderer window appears in tab list when playing a video
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: epiphany-browser (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gst-plugins-base1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1766140 Title: OpenGL Renderer window appears in tab list when playing a video Status in epiphany-browser package in Ubuntu: Confirmed Status in gst-plugins-base1.0 package in Ubuntu: Confirmed Bug description: Every time a web page plays a video in Epiphany, a window named "OpenGL Renderer" appears in the gnome-shell alt-tab list (but not in the overview), one for each video. If I have several pages open with several videos, I get several of these phantom windows. Selecting the window in the list does nothing. This started happening sometime during the beta, it didn't happen under 17.10 or after first upgrading to 18.04. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: epiphany-browser 3.28.1-1ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu6 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Apr 23 10:51:07 2018 InstallationDate: Installed on 2015-07-22 (1005 days ago) InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 (20150422) SourcePackage: epiphany-browser UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/epiphany-browser/+bug/1766140/+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 1815523] Re: The last MESA updates (02/07/19) corrupted output to DisplayLink
When I install an older kernel, do DKMS modules need to be rebuilt, or do DKMS modules only need to built for newer kernels? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1815523 Title: The last MESA updates (02/07/19) corrupted output to DisplayLink Status in mesa package in Ubuntu: Incomplete Bug description: Prior to Thursday's "update" from Bionic-Proposed, the MESA was working fine; afterwards, gameplay on STEAM has become choppy and staccato; secondary display via a USB-C through DisplayPort UD3900 (Pluggable) is completely corrupted. See attached picture. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-15-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity:Unity7:ubuntu Date: Mon Feb 11 16:50:58 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: acpi-call, 1.1.0, 4.18.0-15-generic, x86_64: installedError! Could not locate dkms.conf file. File: does not exist. ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:3ea0] (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer Device [1558:1323] InstallationDate: Installed on 2019-01-15 (27 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: System76 Galago Pro ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-15-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/05/2018 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.03 dmi.board.asset.tag: Tag 12345 dmi.board.name: Galago Pro dmi.board.vendor: System76 dmi.board.version: galp3-c dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: System76 dmi.chassis.version: galp3-c dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.03:bd12/05/2018:svnSystem76:pnGalagoPro:pvrgalp3-c:rvnSystem76:rnGalagoPro:rvrgalp3-c:cvnSystem76:ct10:cvrgalp3-c: dmi.product.family: Not Applicable dmi.product.name: Galago Pro dmi.product.sku: Not Applicable dmi.product.version: galp3-c dmi.sys.vendor: System76 version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1815523/+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 1671974] Re: CUPS - Excessive Amounts of UDP Multicast Traffic for BJNP
I ha -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1671974 Title: CUPS - Excessive Amounts of UDP Multicast Traffic for BJNP Status in cups package in Ubuntu: Confirmed Bug description: It appears that the cups-browsed service as of Xenial (version 1.8.3-2ubuntu3.1) sends an excessive amount of UDP multicast requests for ports 8610 (Canon MFNP) and 8612 (Canon BJNP) under unexpected conditions and regardless of a presence or lack of Canon printer devices on the network. This is manifested by enabling UFW, and observing multicast requests being blocked that are sent from the host machine's network IPv4 or IPv6 address to the multicast address, e.g. [UFW BLOCK] IN=wlp3s0 OUT= MAC= SRC= DST=ff02:::::::0001 LEN=64 TC=0 HOPLIMIT=1 FLOWLBL=96642 PROTO=UDP SPT=8612 DPT=8612 LEN=24 IN= OUT=wlan0 SRC=192.168.90.45 DST=192.168.91.255 LEN=44 TOS=0x00 PREC=0x00 TTL=64 ID=7742 DF PROTO=UDP SPT=8612 DPT=8610 LEN=24 Users have observed that the requests can be reproduced when any USB device is plugged/unplugged into the computer, regardless of whether the device has anything to do with printing: https://twitter.com/gertvdijk/status/621790755758178304 https://bugs.kali.org/view.php?id=3094 Just Googling "udp 8612", shows are a large number of results on different websites of people who have observed this behaviour in firewall and traffic logs, and have noticed that it may contribute to network slowdown and latency: https://askubuntu.com/questions/867739/what-is-this-traffic/867786 https://serverfault.com/questions/667376/watchguard-blocking-internal-udp-packets https://jehurst.wordpress.com/2016/01/22/small-victories/ recommends disabling the cups-browsed service to stop these requests: systemctl stop cups-browsed.service systemctl disable cups-browsed.service There are probably two things to address here: 1. Connecting any USB device should not cause these requests unless the device is actually a printer or directly related to printing. 2. Requests independent of connecting USB devices should be rate limited to a degree and/or should be dependent on the actual presence of a Canon printer configured on the network. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1671974/+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 1815523] Re: The last MESA updates (02/07/19) corrupted output to DisplayLink
Yeah, I removed the older kernels during a clean-up. How do I re- install one back? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1815523 Title: The last MESA updates (02/07/19) corrupted output to DisplayLink Status in mesa package in Ubuntu: Incomplete Bug description: Prior to Thursday's "update" from Bionic-Proposed, the MESA was working fine; afterwards, gameplay on STEAM has become choppy and staccato; secondary display via a USB-C through DisplayPort UD3900 (Pluggable) is completely corrupted. See attached picture. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-15-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity:Unity7:ubuntu Date: Mon Feb 11 16:50:58 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: acpi-call, 1.1.0, 4.18.0-15-generic, x86_64: installedError! Could not locate dkms.conf file. File: does not exist. ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:3ea0] (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer Device [1558:1323] InstallationDate: Installed on 2019-01-15 (27 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: System76 Galago Pro ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-15-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/05/2018 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.03 dmi.board.asset.tag: Tag 12345 dmi.board.name: Galago Pro dmi.board.vendor: System76 dmi.board.version: galp3-c dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: System76 dmi.chassis.version: galp3-c dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.03:bd12/05/2018:svnSystem76:pnGalagoPro:pvrgalp3-c:rvnSystem76:rnGalagoPro:rvrgalp3-c:cvnSystem76:ct10:cvrgalp3-c: dmi.product.family: Not Applicable dmi.product.name: Galago Pro dmi.product.sku: Not Applicable dmi.product.version: galp3-c dmi.sys.vendor: System76 version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1815523/+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 1813893] Re: OpenVPN LZ4 compression not working in Networkmanager
** Package changed: ubuntu => network-manager-openvpn (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-openvpn in Ubuntu. https://bugs.launchpad.net/bugs/1813893 Title: OpenVPN LZ4 compression not working in Networkmanager Status in network-manager-openvpn package in Ubuntu: New Bug description: Hi there, when importing an ovpn profile (from a PFsense in this case) where compression is set to LZ4 it won't work. Network manager won't save the config properly, as it does not seem to support lz4? When I manually use sudo openvpn --config myconfig.ovpn it works just fine. OpenVPN 2.4.6 x86_64-pc-linux-gnu is being used right now. Best regards David To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1813893/+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 1734541] Re: encrypted home-directory is not unmounted on logout
The bug seems to be present in 16.04.5, too. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1734541 Title: encrypted home-directory is not unmounted on logout Status in ecryptfs-utils package in Ubuntu: Confirmed Status in gdm3 package in Ubuntu: Confirmed Status in gnome-session package in Ubuntu: Confirmed Bug description: Current Situation: If you log out from an user account with an encrypted home directory, it is not automatically unmounted and encrypted again. Expected behaviour: If I log out from an user account with an encrypted home directory, Id expect the homedir to be unmounted and encrypted again. Stepts to reproduce: log into an account with encrypted home directory. (lets call it: user) Log out again log into another account (which has sudo rights, lets call it: user2) and now enter the following into a terminal: user2@ubuntu: sudo su user2@ubuntu: ls -la /home/user you can see the files of the user Reasons: This is a security issue, because as a user you can reasonable expect your data to be safe, if you log out. if you would simply log in as another user but keep your data accessable you would simply switch user, instead of loggin out. Many users only suspend their laptop while carrying it with them. Logging out and suspending the user expects to have at least the home directory encrypted. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gdm3 3.26.1-3ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Nov 26 16:18:39 2017 EcryptfsInUse: Yes ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ecryptfs-utils/+bug/1734541/+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 1813893] [NEW] OpenVPN LZ4 compression not working in Networkmanager
You have been subscribed to a public bug: Hi there, when importing an ovpn profile (from a PFsense in this case) where compression is set to LZ4 it won't work. Network manager won't save the config properly, as it does not seem to support lz4? When I manually use sudo openvpn --config myconfig.ovpn it works just fine. OpenVPN 2.4.6 x86_64-pc-linux-gnu is being used right now. Best regards David ** Affects: network-manager-openvpn (Ubuntu) Importance: Undecided Status: New -- OpenVPN LZ4 compression not working in Networkmanager https://bugs.launchpad.net/bugs/1813893 You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-openvpn in Ubuntu. -- 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 1767660] Re: Regression 16.04 LTS to 18.04 LTS: Contour Design RollerMouse double click button no longer results in a double click event
The 1.12.6 in disco and my PPA should have the quirk installed by default for Contour Design RollerMouse Free 2 and Re:d so it should just work. Hence marking as Fix Released for development release and leaving it up to stable maintainers to decide whether something should/could be done for 18.04. ** Changed in: libinput (Ubuntu) Status: Confirmed => Fix Released ** Changed in: libinput (Ubuntu Bionic) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libinput in Ubuntu. https://bugs.launchpad.net/bugs/1767660 Title: Regression 16.04 LTS to 18.04 LTS: Contour Design RollerMouse double click button no longer results in a double click event Status in libinput package in Ubuntu: Fix Released Status in libinput source package in Bionic: Confirmed Bug description: https://gitlab.freedesktop.org/libinput/libinput/issues/204 --- ### Expected behaviour My "Contour Design RollerMouse Free 2" has a specific button for double click. This button should with one physical click result in double click (button press, button release, button press and button release). This works as expected without issues in Ubuntu 16.04 LTS 4.4.0-119-generic #143-Ubuntu SMP Mon Apr 2 16:08:24 UTC 2018 x86_64 ### Experienced behaviour Only one mouse click is registered (button press and button release). Tested with "xev" and "xinput test" ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-20-generic 4.15.0-20.21 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Apr 28 16:26:08 2018 InstallationDate: Installed on 2018-04-27 (1 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: linux-signed UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1767660/+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 1491073] Re: Invalid data message while opening a file
I'm now using Fedora 29 and I have transmission-gtk 2.94 (d8e60ee44f) and have no issues, maybe it was fixed in this version or it have something to do with Ubuntu. Please check version 2.94. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to transmission in Ubuntu. https://bugs.launchpad.net/bugs/1491073 Title: Invalid data message while opening a file Status in transmission package in Ubuntu: Fix Released Bug description: When I open any file in Transmission I get message that file contain invalid data, but I can open torrent file anyway when I close the message. I think that this is a bug because this happen to every file I open. transmission-gtk 2.84 (14307) Xubuntu 13.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/transmission/+bug/1491073/+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 1767660] Re: Regression 16.04 LTS to 18.04 LTS: Contour Design RollerMouse double click button no longer results in a double click event
A customer would like to get this working on Ubuntu 18.04 LTS. However libinput is not part of the standard HWE backport stack, so I guess the likelihood to get the quirk support for 18.04 LTS is fairly low I guess? I'm going to try my own backport (of the whole libinput 1.12 package) from https://launchpad.net/~timo-jyrinki/+archive/ubuntu/libinput the next time I visit. soname seems to be the same so maybe it'd be drop-in compatible. ** Also affects: libinput (Ubuntu Bionic) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libinput in Ubuntu. https://bugs.launchpad.net/bugs/1767660 Title: Regression 16.04 LTS to 18.04 LTS: Contour Design RollerMouse double click button no longer results in a double click event Status in libinput package in Ubuntu: Fix Released Status in libinput source package in Bionic: Confirmed Bug description: https://gitlab.freedesktop.org/libinput/libinput/issues/204 --- ### Expected behaviour My "Contour Design RollerMouse Free 2" has a specific button for double click. This button should with one physical click result in double click (button press, button release, button press and button release). This works as expected without issues in Ubuntu 16.04 LTS 4.4.0-119-generic #143-Ubuntu SMP Mon Apr 2 16:08:24 UTC 2018 x86_64 ### Experienced behaviour Only one mouse click is registered (button press and button release). Tested with "xev" and "xinput test" ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-20-generic 4.15.0-20.21 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Apr 28 16:26:08 2018 InstallationDate: Installed on 2018-04-27 (1 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: linux-signed UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1767660/+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 1812266] Re: Keyboard layout indicator does not indicate current layout (18.04 Bionic beaver)
Ubuntu 18.04.2 LTS, more than five weeks are now gone with this very annoying bug (that resulted from "fixing" a different bug without rigorous testing). Status: in progress. Nobody seems to bother: either Canonical, or the maintainers. Unbelievable. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1812266 Title: Keyboard layout indicator does not indicate current layout (18.04 Bionic beaver) Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell source package in Bionic: In Progress Status in gnome-shell source package in Cosmic: Fix Released Bug description: Upstream issue: https://gitlab.gnome.org/GNOME/gnome-shell/issues/913 [ Impact ] Keyboard Layout indicator don't display current layout (empty selected drop down box) [ Test case ] 1. Boot 2. Suspend or lock the screen 3. Log again with your user 4. The keyboard indicator should display current layout [ Regression Potential ] Really low, we properly pass a null value instead of an undefined one, without breaking JS. -- Steps to reproduce the bug: 1. After normal boot, suspend or lock. 2. Login again. Result: Keyboard Layout indicator don't display current layout (empty selected drop down box) [ Workarounds ] - Switch with keyboard (Super+space) or mouse. BUT if you then logout on the login screen *when you press the first character* of the password the shown selected keyboard layout resets. - Restart Gnome Shell (Alt+F2 r): https://wiki.gnome.org/Projects/GnomeShell/CheatSheet#Developer_tools - Also asked here https://askubuntu.com/q/1109555/349837 - Similar old bug https://bugs.launchpad.net/gnome-settings-daemon/+bug/531173 $ inxi -SG -! 31 -y80 && cat /etc/default/keyboard && localectl status System:Kernel: 4.15.0-43-generic x86_64 bits: 64 Desktop: Gnome 3.28.3 Distro: Ubuntu 18.04.1 LTS Graphics: Card-1: Intel HD Graphics 520 Card-2: NVIDIA GM108M [GeForce 940M] Display Server: x11 (X.Org 1.19.6 ) drivers: fbdev (unloaded: modesetting,vesa) Resolution: 1920x1080@60.00hz OpenGL: renderer: Mesa DRI Intel HD Graphics 520 (Skylake GT2) version: 4.5 Mesa 18.0.5 # KEYBOARD CONFIGURATION FILE # Consult the keyboard(5) manual page. XKBMODEL="pc105" XKBLAYOUT="es" XKBVARIANT="en" XKBOPTIONS="terminate:ctrl_alt_bksp" BACKSPACE="guess" System Locale: LANG=en_US.UTF-8 LC_NUMERIC=es_AR.UTF-8 LC_MONETARY=es_AR.UTF-8 LC_PAPER=es_AR.UTF-8 LC_NAME=es_AR.UTF-8 LC_ADDRESS=es_AR.UTF-8 LC_TELEPHONE=es_AR.UTF-8 LC_MEASUREMENT=es_AR.UTF-8 LC_IDENTIFICATION=es_AR.UTF-8 VC Keymap: n/a X11 Layout: es X11 Model: pc105 X11 Variant: en X11 Options: terminate:ctrl_alt_bksp To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1812266/+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 1815339] Re: Printer stopped printing paper size 4"x6" after update ghostscript to 9.26
The best solution here is a proper fix by Ghostscript's upstream developers. For the case that this fix will not appear soon, the workaround would be to patch CUPS to supply RIP_MAX_CACHE=0 instead of RIP_MAX_CACHE=128m, so that Ghostscript decides on cache sizes by itself. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ghostscript in Ubuntu. https://bugs.launchpad.net/bugs/1815339 Title: Printer stopped printing paper size 4"x6" after update ghostscript to 9.26 Status in GS-GPL: New Status in ghostscript package in Ubuntu: Triaged Bug description: I have an issue with Ghostscript and printing. I use Gutenprint for my Canon MG5440, and I cannot print a photo 4"x6" (or 6"x4"), it does not print anything, however I still able to print A4 paper size. I use Ubuntu 18.04 and Gutenprint 5.3.1. The printing fail with message: [Job 143] Start rendering... [Job 143] Processing page 1... [Job 143] Unable to open the initial device, quitting. [Job 143] Rendering completed ... [Job 143] PID 24869 (/usr/lib/cups/filter/gstoraster) stopped with status 1. ... [Job 143] printer-state-message="Filter failed" [Job 143] printer-state-reasons=none The message "Unable to open the initial device, quitting" comes from Ghostscript. When I downgrade Ghostscript to 9.22, I am again able to print 4"x6" paper size. To downgrade: apt install ghostscript=9.22~dfsg+1-0ubuntu1 libgs9=9.22~dfsg+1-0ubuntu1 libgs9-common=9.22~dfsg+1-0ubuntu1 I found similar issue for HP printer at Debian https://bugs.debian.org /cgi-bin/bugreport.cgi?bug=908205 System info: Description: Ubuntu 18.04.1 LTS Release: 18.04 ghostscript: Installed: 9.26~dfsg+0-0ubuntu0.18.04.4 Candidate: 9.26~dfsg+0-0ubuntu0.18.04.4 Versions: *** 9.26~dfsg+0-0ubuntu0.18.04.4 500 500 http://ua.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 9.22~dfsg+1-0ubuntu1 500 500 http://ua.archive.ubuntu.com/ubuntu bionic/main amd64 Packages cups: Installed: 2.2.7-1ubuntu2.3 Candidate: 2.2.7-1ubuntu2.3 Versions: *** 2.2.7-1ubuntu2.3 500 500 http://ua.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 2.2.7-1ubuntu2.2 500 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 2.2.7-1ubuntu2 500 500 http://ua.archive.ubuntu.com/ubuntu bionic/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/gs-gpl/+bug/1815339/+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
