[Desktop-packages] [Bug 1832988] Re: Intel 8260 Bluetooth not working
** Changed in: linux (Ubuntu) Status: Confirmed => 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/1832988 Title: Intel 8260 Bluetooth not working Status in gnome-bluetooth package in Ubuntu: Invalid Status in gnome-shell package in Ubuntu: Invalid Status in linux package in Ubuntu: Fix Released Bug description: Expected behaviour: I can enable bluetooth in the system settings, and pair with my other devices. Actual behaviour: Always displays as 'off' in the settings dialog, and won't turn on. Bluetooth worked on the same machine with previous Ubuntu releases (18.10) & no hardware changes. "dmesg | grep -i bluetooth" reports the following: ``` [ 14.445902] Bluetooth: Core ver 2.22 [ 14.445918] Bluetooth: HCI device and connection manager initialized [ 14.445921] Bluetooth: HCI socket layer initialized [ 14.445923] Bluetooth: L2CAP socket layer initialized [ 14.445929] Bluetooth: SCO socket layer initialized [ 14.494345] Bluetooth: hci0: Bootloader revision 0.0 build 2 week 52 2014 [ 14.499050] Bluetooth: hci0: Device revision is 5 [ 14.499052] Bluetooth: hci0: Secure boot is enabled [ 14.499053] Bluetooth: hci0: OTP lock is enabled [ 14.499053] Bluetooth: hci0: API lock is enabled [ 14.499054] Bluetooth: hci0: Debug lock is disabled [ 14.499055] Bluetooth: hci0: Minimum firmware build 1 week 10 2014 [ 14.503899] Bluetooth: hci0: Found device firmware: intel/ibt-11-5.sfi [ 14.558347] Bluetooth: hci0: Failed to send firmware data (-38) [ 15.497805] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 15.497806] Bluetooth: BNEP filters: protocol multicast [ 15.497810] Bluetooth: BNEP socket layer initialized ``` "lsb_release -rd" reports the following: ``` Description: Ubuntu 19.04 Release: 19.04 ``` "cat /proc/version_signature" reports the following: ``` Ubuntu 5.0.0-16.17-generic 5.0.8 ``` "apt-cache policy linux-firmware" reports the following: ``` linux-firmware: Installed: 1.178.1 Candidate: 1.178.1 Version table: *** 1.178.1 500 500 http://gb.archive.ubuntu.com/ubuntu disco-updates/main amd64 Packages 500 http://gb.archive.ubuntu.com/ubuntu disco-updates/main i386 Packages 500 http://security.ubuntu.com/ubuntu disco-security/main amd64 Packages 500 http://security.ubuntu.com/ubuntu disco-security/main i386 Packages 100 /var/lib/dpkg/status 1.178 500 500 http://gb.archive.ubuntu.com/ubuntu disco/main amd64 Packages 500 http://gb.archive.ubuntu.com/ubuntu disco/main i386 Packages ``` ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-16-generic 5.0.0-16.17 ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8 Uname: Linux 5.0.0-16-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: martin 2314 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Jun 16 12:31:07 2019 InstallationDate: Installed on 2019-06-02 (13 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 1c7a:0603 LighTuning Technology Inc. Bus 001 Device 003: ID 5986:066d Acer, Inc Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: PC Specialist Limited N15_17RD ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-16-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-5.0.0-16-generic N/A linux-backports-modules-5.0.0-16-generic N/A linux-firmware1.178.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/25/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.11 dmi.board.asset.tag: Tag 12345 dmi.board.name: N15_17RD dmi.board.vendor: CLEVO dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.11:bd12/25/2015:svnPCSpecialistLimited:pnN15_17RD:pvrNotApplicable:rvnCLEVO:rnN15_17RD:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: N15_17RD dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: PC Specialist Limited To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-bluetooth/+bug/1832988/+subscriptions -- Mailing list: https://launchpad.net/~desk
[Desktop-packages] [Bug 1855469] Re: gnome-shell lags on wayland
** Tags added: leak -- 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/1855469 Title: gnome-shell lags on wayland Status in gnome-shell package in Ubuntu: Invalid Bug description: see https://discourse.ubuntu.com/t/boosting-the-real-time-performance- of-gnome-shell-3-34-in-ubuntu-19-10/13095/24 I’m using ubuntu on wayland for a while (Unity and Gnome since Unity abandon). But with ubuntu 19.10 upgrade, Gnome was so slow and laggy that I had thought to downgrade or a new laptop. I switched back to Xorg and now everything is as smoth as usual. I have an intel card, don’t know if it can help. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.1+git20191024-1ubuntu1~19.10.1 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Dec 6 18:54:15 2019 DisplayManager: gdm3 InstallationDate: Installed on 2015-05-23 (1658 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) RelatedPackageVersions: mutter-common 3.34.1+git20191107-1ubuntu1~19.10.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to eoan on 2019-11-03 (33 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1855469/+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 1859774] Re: Full screen window becomes "small" in the upper left of the screen...
An interesting and maybe useful thing I found when I log out and back in again, it comes up in a very much different resolution, though the settings say it is 1920x1080. See the screenshot (not cropped). So when I went to make changes back to what I prefer, I found the 200% was on. It wasn't at 200% before I relogged in. I'll keep you posted. Thanks, Rob ** Attachment added: "Screenshot from 2020-02-14 17-13-34.png" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1859774/+attachment/5328117/+files/Screenshot%20from%202020-02-14%2017-13-34.png -- 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/1859774 Title: Full screen window becomes "small" in the upper left of the screen... Status in gnome-shell package in Ubuntu: Incomplete Bug description: This happens with a number of different programs, so I suspect it is a window manager bug. The best way to describe it is with a screen shot. The only responsive part of the screen is the small window in the upper left. You can hit the little maximize box and it goes back to full screen okay, but after a while it comes back to this. It can be annoying, because sometimes you can't quickly see what happened to the title bar. I'm using Ubuntu 19.10. This has been happening for about a week. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1859774/+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 1861345] Re: Gigabyte x570 Aorus Master with ALC1220 and ESS SABRE 9118 DAC Muted Front speakers 5.1
Please file an upstream bug at https://bugzilla.kernel.org/ Product: Drivers Component: Sound(ALSA) ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1861345 Title: Gigabyte x570 Aorus Master with ALC1220 and ESS SABRE 9118 DAC Muted Front speakers 5.1 Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: Ubuntu 18.04.3 LTS Kernel 5.5.0 pulseaudio: Installed: 1:11.1-1ubuntu7.4 X570 Aorus Master Motherboard. ALC1220 ESS Sabre sound. I have surround 5.1 speakers and the Front Left and Right are Muted. I have to unmute Headphones in alsamixer to hear sound from the front left and right speakers is the workaround. This step should not be required for speakers 5.1 to work. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: richard2533 F pulseaudio /dev/snd/controlC1: richard2533 F pulseaudio /dev/snd/controlC0: richard2533 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-01-28 (2 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) MachineType: Gigabyte Technology Co., Ltd. X570 AORUS MASTER Package: linux (not installed) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-28-generic root=UUID=51fe9653-53b0-475f-836e-a1662c6d8b79 ro quiet splash amd_iommu=on vt.handoff=1 ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13 RelatedPackageVersions: linux-restricted-modules-5.3.0-28-generic N/A linux-backports-modules-5.3.0-28-generic N/A linux-firmware1.173.14 Tags: bionic Uname: Linux 5.3.0-28-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip kvm libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/06/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F11 dmi.board.asset.tag: Default string dmi.board.name: X570 AORUS MASTER dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF11:bd12/06/2019:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSMASTER:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSMASTER:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: X570 AORUS MASTER dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1861345/+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 1859774] Re: Full screen window becomes "small" in the upper left of the screen...
Thanks. Those 3 extensions can be ignored as we do ship those by default. The extra XML files you see sound like backup files I asked you to create in comment #12. I think they are safe to keep and won't be used unless named 'monitors.xml'. As for xrandr, it looks better behaved now. At least you're running at the native resolution. Only a little bit unusual you're not running at the native refresh rate of the monitor: 1920x1080 60.05 + 60.01 59.97 59.96* 59.93 + means the hardware preferred mode * means the current mode I don't think any of these most recent observations explain this bug, but I would be interested to hear if the bug stays away for a while after you remove monitors.xml and log out/in again. -- 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/1859774 Title: Full screen window becomes "small" in the upper left of the screen... Status in gnome-shell package in Ubuntu: Incomplete Bug description: This happens with a number of different programs, so I suspect it is a window manager bug. The best way to describe it is with a screen shot. The only responsive part of the screen is the small window in the upper left. You can hit the little maximize box and it goes back to full screen okay, but after a while it comes back to this. It can be annoying, because sometimes you can't quickly see what happened to the title bar. I'm using Ubuntu 19.10. This has been happening for about a week. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1859774/+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 1857869] Re: Red fill the search stop icon
Reported to Gitlab: https://gitlab.gnome.org/GNOME/nautilus/issues/1375 ** Bug watch added: gitlab.gnome.org/GNOME/nautilus/issues #1375 https://gitlab.gnome.org/GNOME/nautilus/issues/1375 -- 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/1857869 Title: Red fill the search stop icon Status in nautilus package in Ubuntu: New Bug description: 1) Ubuntu 19.10 2) 1:3.34.1-1ubuntu1 3) It might be better if the search stop icon was red filled. Similar to a stop sign. 4) The search stop icon is white filled. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1857869/+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 1860754] Re: ASUS T100HAN boots to a blank screen with a cursor [i965: Failed to submit batchbuffer: Input/output error]
Please test this kernel: https://people.canonical.com/~khfeng/lp1860754/ -- 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/1860754 Title: ASUS T100HAN boots to a blank screen with a cursor [i965: Failed to submit batchbuffer: Input/output error] Status in linux package in Ubuntu: Incomplete Status in mesa package in Ubuntu: Incomplete Bug description: - After installed Ubuntu 19.10 with nomodeset i915.modeset=0, it won't recognize graphic driver. - run udo apt-get install xserver-xorg-video-intel 0 upgraded, 0 newly installed, 0 to remove and 144 not upgraded. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 Uname: Linux 5.3.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jan 24 14:29:01 2020 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:22b0] (rev 20) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series PCI Configuration Registers [1043:1bdd] InstallationDate: Installed on 2020-01-24 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0b05:1807 ASUSTek Computer, Inc. USB2.0 Hub Bus 001 Device 002: ID 05e3:0610 Genesys Logic, Inc. 4-port hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. T100HAN ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic root=/dev/mapper/vgubuntu-root ro nomodeset i915.modeset=0 quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/18/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: T100HAN.221 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: T100HAN dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrT100HAN.221:bd05/18/2016:svnASUSTeKCOMPUTERINC.:pnT100HAN:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnT100HAN:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: T dmi.product.name: T100HAN dmi.product.sku: ASUS-TabletSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860754/+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 1859774] Re: Full screen window becomes "small" in the upper left of the screen...
Thanks Daniel! I looked and somehow the Gnome Extensions page and found the top extension in this screenshot enabled. I can't seem to figure out how to actually uninstall these three extensions. Are they perhaps enstalled by Ubuntu? I have rebooted and went back to straight gnome shell without wayland. The screenshot I put up from libeoffice presenter was not a whole thing. I temporarily forgot how to get the whole thing, as I usually don't want the whole thing, so I just did most of it as you noted. The settings has 1920x1080. I removed the ~/.config/monitors.xml and while I was there I noted some similar files. Could they be causing this? (base) frohro@frohro-260:~/SAM/2018.11.11$ ls -lah ~/.config/monitors* -rw-r--r-- 1 frohro frohro 17K May 1 2019 /home/frohro/.config/monitors-office.xml -rw-r--r-- 1 frohro frohro 3.6K Feb 25 2018 /home/frohro/.config/monitors-v1-backup.xml -rw-r--r-- 1 frohro frohro 934 Oct 24 2017 /home/frohro/.config/monitors-v1-backup.xml~ -rw-r--r-- 1 frohro frohro 2.4K Feb 10 19:16 /home/frohro/.config/monitors.xml~ (base) frohro@frohro-260:~/SAM/2018.11.11$ Here is the output from xrandr. (base) frohro@frohro-260:~/Downloads$ xrandr Screen 0: minimum 320 x 200, current 1920 x 1080, maximum 16384 x 16384 eDP-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 276mm x 155mm 1920x1080 60.05 + 60.0159.9759.96* 59.93 1680x1050 59.9559.88 1600x1024 60.17 1400x1050 59.98 1600x900 59.9959.9459.9559.82 1280x1024 60.02 1440x900 59.89 1400x900 59.9659.88 1280x960 60.00 1440x810 60.0059.97 1368x768 59.8859.85 1360x768 59.8059.96 1280x800 59.9959.9759.8159.91 1152x864 60.00 1280x720 60.0059.9959.8659.74 1024x768 60.0460.00 960x720 60.00 928x696 60.05 896x672 60.01 1024x576 59.9559.9659.9059.82 960x600 59.9360.00 960x540 59.9659.9959.6359.82 800x600 60.0060.3256.25 840x525 60.0159.88 864x486 59.9259.57 800x512 60.17 700x525 59.98 800x450 59.9559.82 640x512 60.02 720x450 59.89 700x450 59.9659.88 640x480 60.0059.94 720x405 59.5158.99 684x384 59.8859.85 680x384 59.8059.96 640x400 59.8859.98 576x432 60.06 640x360 59.8659.8359.8459.32 512x384 60.00 512x288 60.0059.92 480x270 59.6359.82 400x300 60.3256.34 432x243 59.9259.57 320x240 60.05 360x202 59.5159.13 320x180 59.8459.32 DP-1 disconnected (normal left inverted right x axis y axis) HDMI-1 disconnected (normal left inverted right x axis y axis) DP-2 disconnected (normal left inverted right x axis y axis) HDMI-2 disconnected (normal left inverted right x axis y axis) (base) frohro@frohro-260:~/Downloads$ Thanks Daniel! Rob ** Attachment added: "Screenshot from 2020-02-14 14-48-24.png" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1859774/+attachment/5328103/+files/Screenshot%20from%202020-02-14%2014-48-24.png -- 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/1859774 Title: Full screen window becomes "small" in the upper left of the screen... Status in gnome-shell package in Ubuntu: Incomplete Bug description: This happens with a number of different programs, so I suspect it is a window manager bug. The best way to describe it is with a screen shot. The only responsive part of the screen is the small window in the upper left. You can hit the little maximize box and it goes back to full screen okay, but after a while it comes back to this. It can be annoying, because sometimes you can't quickly see what happened to the title bar. I'm using Ubuntu 19.10. This has been happening for about a week. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1859774/+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 1862865] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:
apport-collect 1862865
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.
This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.
** Changed in: linux (Ubuntu)
Status: New => 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/1862865
Title:
i915 :00:02.0: Resetting rcs0 for stuck wait on rcs0
Status in linux package in Ubuntu:
Incomplete
Status in mesa package in Ubuntu:
Invalid
Status in linux source package in Focal:
Incomplete
Status in mesa source package in Focal:
Invalid
Bug description:
Hi,
Every now and again, my session locks up with the following logged:
| i915 :00:02.0: Resetting rcs0 for hang on rcs0
Most of the time, it recovers on it's own but sometimes locks up
completely requring a reboot. When that happens this is logged:
| Feb 2 10:37:23 dharkan kernel: [71018.593184] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:23 dharkan kernel: [71018.593993] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:23 dharkan kernel: [71018.594130] i915 :00:02.0: Resetting
chip for hang on rcs0
| Feb 2 10:37:23 dharkan kernel: [71018.595937] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:23 dharkan kernel: [71018.596728] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:28 dharkan kernel: [71022.816232] Asynchronous wait on fence
i915:compiz[1495]:105ece timed out (hint:intel_atomic_commit_ready+0x0/0x54
[i915])
| Feb 2 10:37:31 dharkan kernel: [71026.593149] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:31 dharkan kernel: [71026.593958] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:31 dharkan kernel: [71026.596916] i915 :00:02.0: Resetting
chip for hang on rcs0
| Feb 2 10:37:31 dharkan kernel: [71026.598661] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:31 dharkan kernel: [71026.599391] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:35 dharkan kernel: [71030.592141] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:39 dharkan kernel: [71034.323140] GpuWatchdog[1860]: segfault
at 0 ip 55689a4eb33d sp 7f69b674d700 error 6 in
chrome[5568968fd000+6abe000]
| Feb 2 10:37:39 dharkan kernel: [71034.323157] Code: 00 79 09 48 8b 7d a0
e8 31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89
ef be 01 00 00 00 ff 50 58 04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03
01 80 bd 7f ff
| Feb 2 10:37:43 dharkan kernel: [71038.592101] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:45 dharkan kernel: [71040.576093] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:47 dharkan kernel: [71042.592066] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:49 dharkan kernel: [71044.576075] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:51 dharkan kernel: [71046.592045] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:53 dharkan kernel: [71048.576098] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:55 dharkan kernel: [71050.592029] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:57 dharkan kernel: [71052.576037] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:59 dharkan kernel: [71054.592034] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:01 dharkan kernel: [71056.576021] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:03 dharkan kernel: [71058.592006] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:04 dharkan kernel: [71059.461584] GpuWatchdog[43507]: segfault
at 0 ip 55ac6731833d sp 7fe71901e700 error 6 in
chrome[55ac6372a000+6abe000]
| Feb 2 10:38:04 dharkan kernel: [71059.461600] Code: 00 79 09 48 8b 7d a0
e8 31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89
ef be 01 00 00 00 ff 50 58 04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03
01 80 bd 7f ff
| Feb 2 10:38:05 dharkan kernel: [71060.575986]
[Desktop-packages] [Bug 1862865] Re: i915 0000:00:02.0: Resetting rcs0 for stuck wait on rcs0
** Package changed: linux-meta-5.4 (Ubuntu Focal) => linux (Ubuntu
Focal)
--
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/1862865
Title:
i915 :00:02.0: Resetting rcs0 for stuck wait on rcs0
Status in linux package in Ubuntu:
Incomplete
Status in mesa package in Ubuntu:
Invalid
Status in linux source package in Focal:
Incomplete
Status in mesa source package in Focal:
Invalid
Bug description:
Hi,
Every now and again, my session locks up with the following logged:
| i915 :00:02.0: Resetting rcs0 for hang on rcs0
Most of the time, it recovers on it's own but sometimes locks up
completely requring a reboot. When that happens this is logged:
| Feb 2 10:37:23 dharkan kernel: [71018.593184] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:23 dharkan kernel: [71018.593993] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:23 dharkan kernel: [71018.594130] i915 :00:02.0: Resetting
chip for hang on rcs0
| Feb 2 10:37:23 dharkan kernel: [71018.595937] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:23 dharkan kernel: [71018.596728] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:28 dharkan kernel: [71022.816232] Asynchronous wait on fence
i915:compiz[1495]:105ece timed out (hint:intel_atomic_commit_ready+0x0/0x54
[i915])
| Feb 2 10:37:31 dharkan kernel: [71026.593149] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:31 dharkan kernel: [71026.593958] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:31 dharkan kernel: [71026.596916] i915 :00:02.0: Resetting
chip for hang on rcs0
| Feb 2 10:37:31 dharkan kernel: [71026.598661] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:31 dharkan kernel: [71026.599391] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:35 dharkan kernel: [71030.592141] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:39 dharkan kernel: [71034.323140] GpuWatchdog[1860]: segfault
at 0 ip 55689a4eb33d sp 7f69b674d700 error 6 in
chrome[5568968fd000+6abe000]
| Feb 2 10:37:39 dharkan kernel: [71034.323157] Code: 00 79 09 48 8b 7d a0
e8 31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89
ef be 01 00 00 00 ff 50 58 04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03
01 80 bd 7f ff
| Feb 2 10:37:43 dharkan kernel: [71038.592101] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:45 dharkan kernel: [71040.576093] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:47 dharkan kernel: [71042.592066] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:49 dharkan kernel: [71044.576075] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:51 dharkan kernel: [71046.592045] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:53 dharkan kernel: [71048.576098] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:55 dharkan kernel: [71050.592029] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:57 dharkan kernel: [71052.576037] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:59 dharkan kernel: [71054.592034] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:01 dharkan kernel: [71056.576021] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:03 dharkan kernel: [71058.592006] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:04 dharkan kernel: [71059.461584] GpuWatchdog[43507]: segfault
at 0 ip 55ac6731833d sp 7fe71901e700 error 6 in
chrome[55ac6372a000+6abe000]
| Feb 2 10:38:04 dharkan kernel: [71059.461600] Code: 00 79 09 48 8b 7d a0
e8 31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89
ef be 01 00 00 00 ff 50 58 04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03
01 80 bd 7f ff
| Feb 2 10:38:05 dharkan kernel: [71060.575986] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:07 dharkan kernel: [71062.591982] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:09 dharkan kernel: [71064.575976] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:11 dharkan kernel: [71066.591956] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:13 dharkan kernel: [71068.575937] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:15 dharkan kernel: [71070.591932] i915 :00:02
[Desktop-packages] [Bug 1852634] Re: Long delay before modal dialogs show
[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/1852634 Title: Long delay before modal dialogs show Status in gnome-shell package in Ubuntu: Expired Bug description: Ubuntu 19.10 with gnome-desktop After upgrading from Ubuntu 19.04 to 19.10, window dialogs take a long time to display. Sample dialogs include "Are you sure you want to delete this file?" or "Do you want to save this file before quitting?". I can consistently reproduce the issue in Nautilus and Sublime Text, but the issue does not exist in Gedit. I've attached three screencasts that demonstrate the problem and a syslog that starts from the computer booting and ends shortly after reproducing the issue in Nautilus file manager. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-08-01 (127 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-shell 3.34.1+git20191024-1ubuntu1~19.10.1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 RelatedPackageVersions: mutter-common 3.34.1+git20191107-1ubuntu1~19.10.1 Tags: eoan Uname: Linux 5.3.0-23-generic x86_64 UpgradeStatus: Upgraded to eoan on 2019-11-01 (35 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-08-01 (127 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-shell 3.34.1+git20191024-1ubuntu1~19.10.1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 RelatedPackageVersions: mutter-common 3.34.1+git20191107-1ubuntu1~19.10.1 Tags: eoan Uname: Linux 5.3.0-24-generic x86_64 UpgradeStatus: Upgraded to eoan on 2019-11-01 (35 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1852634/+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 1856491] Re: after suspend system freezes for a while after mouting new device
[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/1856491 Title: after suspend system freezes for a while after mouting new device Status in gnome-shell package in Ubuntu: Expired Bug description: after plugging in usb device (eg android phone) or mounting local drive ui freezes for a minute, mouse is working but ui doesnt react at all pc has to be suspended for longer time otherwise i couldnt reproduce these problems ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.1+git20191024-1ubuntu1~19.10.1 ProcVersionSignature: Ubuntu 5.3.0-25.27-generic 5.3.13 Uname: Linux 5.3.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Dec 15 22:55:27 2019 DisplayManager: lightdm InstallationDate: Installed on 2019-11-19 (26 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) RelatedPackageVersions: mutter-common 3.34.1+git20191107-1ubuntu1~19.10.1 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/gnome-shell/+bug/1856491/+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 1852863] Re: Don't know
[Expired for mutter (Ubuntu) because there has been no activity for 60 days.] ** Changed in: mutter (Ubuntu) Status: Incomplete => Expired -- 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/1852863 Title: Don't know Status in mutter package in Ubuntu: Expired Bug description: only to start via secured mode ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 3.13.0-92.139-generic 3.13.11-ckt39 Uname: Linux 3.13.0-92-generic i686 .tmp.unity_support_test.1: ApportVersion: 2.20.9-0ubuntu7.9 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Sat Nov 16 19:50:48 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: virtualbox, 5.2.32: added GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Fujitsu Limited. Core Processor Integrated Graphics Controller [10cf:150a] InstallationDate: Installed on 2014-09-25 (1878 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 (20120423) MachineType: FUJITSU LIFEBOOK AH530 ProcEnviron: PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-92-generic root=UUID=3b781983-e52b-4947-831e-3a130b33f860 ro recovery nomodeset Renderer: Software SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/15/2011 dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd. dmi.bios.version: Version 1.18 dmi.board.name: FJNBB06 dmi.board.vendor: FUJITSU dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU dmi.modalias: dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.18:bd04/15/2011:svnFUJITSU:pnLIFEBOOKAH530:pvr:rvnFUJITSU:rnFJNBB06:rvr:cvnFUJITSU:ct10:cvr: dmi.product.name: LIFEBOOK AH530 dmi.sys.vendor: FUJITSU version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 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 xserver.bootTime: Sat Nov 16 11:58:52 2019 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu4.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1852863/+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 1862865] Re: i915 0000:00:02.0: Resetting rcs0 for stuck wait on rcs0
| 00:02.0 VGA compatible controller: Intel Corporation HD Graphics 620 (rev 02)
(prog-if 00 [VGA controller])
| Subsystem: Lenovo ThinkPad X1 Carbon 5th Gen
Linux 5.4.0-9.12
** Also affects: linux-meta-5.4 (Ubuntu)
Importance: Undecided
Status: New
** Changed in: mesa (Ubuntu)
Status: New => Invalid
** Also affects: mesa (Ubuntu Focal)
Importance: Undecided
Status: Invalid
** Also affects: linux-meta-5.4 (Ubuntu Focal)
Importance: Undecided
Status: New
--
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/1862865
Title:
i915 :00:02.0: Resetting rcs0 for stuck wait on rcs0
Status in linux-meta-5.4 package in Ubuntu:
New
Status in mesa package in Ubuntu:
Invalid
Status in linux-meta-5.4 source package in Focal:
New
Status in mesa source package in Focal:
Invalid
Bug description:
Hi,
Every now and again, my session locks up with the following logged:
| i915 :00:02.0: Resetting rcs0 for hang on rcs0
Most of the time, it recovers on it's own but sometimes locks up
completely requring a reboot. When that happens this is logged:
| Feb 2 10:37:23 dharkan kernel: [71018.593184] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:23 dharkan kernel: [71018.593993] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:23 dharkan kernel: [71018.594130] i915 :00:02.0: Resetting
chip for hang on rcs0
| Feb 2 10:37:23 dharkan kernel: [71018.595937] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:23 dharkan kernel: [71018.596728] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:28 dharkan kernel: [71022.816232] Asynchronous wait on fence
i915:compiz[1495]:105ece timed out (hint:intel_atomic_commit_ready+0x0/0x54
[i915])
| Feb 2 10:37:31 dharkan kernel: [71026.593149] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:31 dharkan kernel: [71026.593958] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:31 dharkan kernel: [71026.596916] i915 :00:02.0: Resetting
chip for hang on rcs0
| Feb 2 10:37:31 dharkan kernel: [71026.598661] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:31 dharkan kernel: [71026.599391] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:35 dharkan kernel: [71030.592141] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:39 dharkan kernel: [71034.323140] GpuWatchdog[1860]: segfault
at 0 ip 55689a4eb33d sp 7f69b674d700 error 6 in
chrome[5568968fd000+6abe000]
| Feb 2 10:37:39 dharkan kernel: [71034.323157] Code: 00 79 09 48 8b 7d a0
e8 31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89
ef be 01 00 00 00 ff 50 58 04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03
01 80 bd 7f ff
| Feb 2 10:37:43 dharkan kernel: [71038.592101] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:45 dharkan kernel: [71040.576093] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:47 dharkan kernel: [71042.592066] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:49 dharkan kernel: [71044.576075] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:51 dharkan kernel: [71046.592045] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:53 dharkan kernel: [71048.576098] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:55 dharkan kernel: [71050.592029] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:57 dharkan kernel: [71052.576037] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:59 dharkan kernel: [71054.592034] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:01 dharkan kernel: [71056.576021] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:03 dharkan kernel: [71058.592006] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:04 dharkan kernel: [71059.461584] GpuWatchdog[43507]: segfault
at 0 ip 55ac6731833d sp 7fe71901e700 error 6 in
chrome[55ac6372a000+6abe000]
| Feb 2 10:38:04 dharkan kernel: [71059.461600] Code: 00 79 09 48 8b 7d a0
e8 31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89
ef be 01 00 00 00 ff 50 58 04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03
01 80 bd 7f ff
| Feb 2 10:38:05 dharkan kernel: [71060.575986] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:07 dharkan kernel: [71
[Desktop-packages] [Bug 1844458] Re: Drop transitional flashplugin-downloader package
I agree and tried to get a discussion to kill it going here: https://discourse.ubuntu.com/t/ubuntu-20-04-and-flash/13814/3 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to flashplugin-nonfree in Ubuntu. https://bugs.launchpad.net/bugs/1844458 Title: Drop transitional flashplugin-downloader package Status in flashplugin-nonfree package in Ubuntu: New Bug description: I think the transition is done. It's in 16.04-19.10 as a transitional package. Found this because it made this list: https://discourse.ubuntu.com/t /community-process-for-32-bit-compatibility/12598 I don't want anyone thinking that 32-bit Flash is supported on Linux. Happy to make a debdiff (or if you point me at where the code is - the code here seems out of date) to make a PR. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flashplugin-nonfree/+bug/1844458/+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 1861280] Re: Desktop icons reshuffled on addition & deletion
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-shell-extension-desktop-icons (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-desktop-icons in Ubuntu. https://bugs.launchpad.net/bugs/1861280 Title: Desktop icons reshuffled on addition & deletion Status in gnome-shell-extension-desktop-icons package in Ubuntu: Confirmed Bug description: It may be a bad habit, but for years I have saved temporary files (stuff I don't intend to keep long & some work in progress) to my desktop, where I won't forget them & they are immediately available. For years there was no problem - icons on the desktop stayed where they were. Since 19.10 things have gone crazy (might have started with 19.04 but I can't check that now). Nearly every time a new item is added or removed, some or all of the other items get reshuffled on the desk! I raised this issue on Ubuntu Forum, with details & screenshots (PLEASE LOOK) here: https://ubuntuforums.org/showthread.php?t=2435768 I have run comparison tests, using SHA-verified Live USB stick versions of Ubuntu 18.04.3 & 19.10, which I suppose anybody else can duplicate. My test was to successively "Save-as to desktop" 32 tiny LibO files called 01, 02, 03 etc in that order. With 18.04.3, each item was positioned top-to-bottom in a column at left, then in the next columns to the right after each column was full. Once positioned, no icon moved. With 19.10, icons were positioned clustered top-left but new columns were started before previous columns were full. Nearly every addition caused previous icons to be reshuffled. Frequently the number of columns DIMINISHED when a new icon was added. With 19.10, removing icons causes other items to reshuffle. With 18.04.3, removing icons leaves a gap, which is filled by the next item added. I think the behaviour of 18.04.3 is perfect & the behaviour of 19.10 is an unacceptable regression. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: nautilus 1:3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13 Uname: Linux 5.3.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Jan 29 14:03:30 2020 InstallationDate: Installed on 2014-10-23 (1923 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2019-11-04T18:03:11.954726 usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/1861280/+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 1855469] Re: gnome-shell lags on wayland
There's probably no need to open a kernel bug for this either, because 5.4 is already in Ubuntu 20.04 :) -- 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/1855469 Title: gnome-shell lags on wayland Status in gnome-shell package in Ubuntu: Invalid Bug description: see https://discourse.ubuntu.com/t/boosting-the-real-time-performance- of-gnome-shell-3-34-in-ubuntu-19-10/13095/24 I’m using ubuntu on wayland for a while (Unity and Gnome since Unity abandon). But with ubuntu 19.10 upgrade, Gnome was so slow and laggy that I had thought to downgrade or a new laptop. I switched back to Xorg and now everything is as smoth as usual. I have an intel card, don’t know if it can help. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.1+git20191024-1ubuntu1~19.10.1 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Dec 6 18:54:15 2019 DisplayManager: gdm3 InstallationDate: Installed on 2015-05-23 (1658 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) RelatedPackageVersions: mutter-common 3.34.1+git20191107-1ubuntu1~19.10.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to eoan on 2019-11-03 (33 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1855469/+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 1856516] Re: Excessive memory usage by gnome-shell in 19.10
** Tags added: leak -- 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/1856516 Title: Excessive memory usage by gnome-shell in 19.10 Status in gnome-shell package in Ubuntu: Incomplete Bug description: The gnome-shell process on my system is currently at 5473M VIRT 1224M RSS 566M SHR; this seems a bit excessive. This session has been up for >4 days with a number of suspend/resume cycles in there, so this might be a slow leak? ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.1+git20191024-1ubuntu1~19.10.1 ProcVersionSignature: Ubuntu 5.3.0+bcachefs.git20191120.71cdaa7a-1-generic 5.3.10 Uname: Linux 5.3.0+bcachefs.git20191120.71cdaa7a-1-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Dec 16 16:50:10 2019 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2019-08-29 (109 days ago) InstallationMedia: Ubuntu 19.10 bcachefs (20190828) ProcEnviron: LANG=en_AU.UTF-8 LANGUAGE=en_AU:en PATH=(custom, user) SHELL=/usr/bin/fish XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 3.34.1+git20191107-1ubuntu1~19.10.1 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/gnome-shell/+bug/1856516/+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 1752723] Re: Screen keeps flickering
** Package changed: xorg (Ubuntu) => xserver-xorg-video-intel (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1752723 Title: Screen keeps flickering Status in xserver-xorg-video-intel package in Ubuntu: New Bug description: Trying to see if there was any issues with my graphics drivers, as my laptops screen keeps flickering. It flickers less so on browsers etc, but I just booted up a game on steam and it was flickering constantly, almost enough to give me epilepsy ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-109.132-generic 4.4.98 Uname: Linux 4.4.0-109-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 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 Date: Thu Mar 1 21:50:43 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: nvidia-304, 304.135, 4.4.0-109-generic, x86_64: installed nvidia-304, 304.135, 4.4.0-116-generic, x86_64: installed GraphicsCard: Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer Skylake Integrated Graphics [1558:0941] InstallationDate: Installed on 2016-10-05 (512 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f2:b550 Chicony Electronics Co., Ltd Bus 001 Device 007: ID 8087:0a2b Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: PC Specialist Limited W94_95_97JU ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-109-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/30/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.11 dmi.board.asset.tag: Tag 12345 dmi.board.name: W94_95_97JU dmi.board.vendor: CLEVO dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.11:bd03/30/2016:svnPCSpecialistLimited:pnW94_95_97JU:pvrNotApplicable:rvnCLEVO:rnW94_95_97JU:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.name: W94_95_97JU dmi.product.version: Not Applicable dmi.sys.vendor: PC Specialist Limited version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.83-1~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Mon Feb 26 18:13:11 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id1170 vendor LGD xserver.version: 2:1.18.4-0ubuntu0.7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1752723/+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 1752200] Re: toolbar and the menubar disappear
** Summary changed: - desktop bug + toolbar and the menubar disappear ** Summary changed: - toolbar and the menubar disappear + toolbar and the menubar disappear ** Package changed: xorg (Ubuntu) => unity (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/1752200 Title: toolbar and the menubar disappear Status in unity package in Ubuntu: New Bug description: My notebook show a bug, the toolbar and the menubar has dissapear, after i refresh for the program have sugest ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-36-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Tue Feb 27 21:21:43 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Skylake Integrated Graphics [1025:100c] InstallationDate: Installed on 2017-09-29 (151 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 003: ID 04f2:b520 Chicony Electronics Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Aspire E5-574 ProcEnviron: LANGUAGE=pt_BR:pt:en PATH=(custom, no user) LANG=pt_BR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-36-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/27/2015 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.10 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Zoro_SL dmi.board.vendor: Acer dmi.board.version: V1.10 dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.10:bd11/27/2015:svnAcer:pnAspireE5-574:pvrV1.10:rvnAcer:rnZoro_SL:rvrV1.10:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.family: SKL dmi.product.name: Aspire E5-574 dmi.product.version: V1.10 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.12.3+16.04.20171116-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.83-1~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Tue Feb 27 21:19:48 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.5-0ubuntu2~16.04.1 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1752200/+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 1862459] Re: ubuntu 18 screen flicker/blink
Thanks for the bug report. I can see two possible problems here that might relate to screen flicker: * The i915 kernel driver crashed, in intel_modeset_init * Xorg is using probably the wrong driver 'intel'. It should be using the modesetting driver on a modern system like yours. Please try removing that wrong driver: sudo apt remove xserver-xorg-video-intel or just try logging into "Ubuntu on Wayland" instead. Maybe it's some combination of the above two issues. ** Package changed: xorg (Ubuntu) => linux (Ubuntu) ** Also affects: xserver-xorg-video-intel (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Changed in: xserver-xorg-video-intel (Ubuntu) Status: New => Incomplete -- 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/1862459 Title: ubuntu 18 screen flicker/blink Status in linux package in Ubuntu: Incomplete Status in xserver-xorg-video-intel package in Ubuntu: Incomplete Bug description: Ubuntu screen flicker /blinking on start laptop every time ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-76.86-generic 4.15.18 Uname: Linux 4.15.0-76-generic x86_64 NonfreeKernelModules: wl .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CompositorRunning: None Date: Sat Feb 8 20:50:43 2020 DistUpgraded: 2019-06-27 23:49:46,134 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 4.15.0-76-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company HD Graphics 5500 [103c:80c1] InstallationDate: Installed on 2015-10-17 (1574 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) MachineType: Hewlett-Packard HP Notebook ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-76-generic root=UUID=733f49c2-0b52-4a07-9eea-15cbf15593cf ro quiet splash SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2019-06-27 (225 days ago) dmi.bios.date: 06/04/2015 dmi.bios.vendor: Insyde dmi.bios.version: F.0B dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 80C1 dmi.board.vendor: Hewlett-Packard dmi.board.version: 96.11 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.0B:bd06/04/2015:svnHewlett-Packard:pnHPNotebook:pvrType1ProductConfigId:rvnHewlett-Packard:rn80C1:rvr96.11:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP dmi.product.name: HP Notebook dmi.product.version: Type1ProductConfigId dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 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 xserver.bootTime: Thu Jun 27 18:02:31 2019 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 20049 vendor SDC xserver.version: 2:1.18.4-0ubuntu0.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1862459/+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 1863049] Re: plz rectify this bugs
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! ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- 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/1863049 Title: plz rectify this bugs Status in Ubuntu: Incomplete Bug description: q ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-64.73-generic 4.15.18 Uname: Linux 4.15.0-64-generic x86_64 NonfreeKernelModules: lkp_Ubuntu_4_15_0_64_73_generic_59 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Thu Feb 13 10:20:24 2020 DistUpgraded: 2018-09-13 18:17:06,036 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu DpkgLog: GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. HD Graphics 5500 [1043:19ad] InstallationDate: Installed on 2016-03-08 (1437 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: ASUSTeK COMPUTER INC. X555LAB ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-64-generic root=UUID=a8582c35-8f2e-4581-8019-65e2d7d13535 ro quiet splash SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2018-09-13 (517 days ago) dmi.bios.date: 08/04/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X555LAB.503 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X555LAB dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX555LAB.503:bd08/04/2015:svnASUSTeKCOMPUTERINC.:pnX555LAB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX555LAB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: X dmi.product.name: X555LAB dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 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 xserver.bootTime: Thu Sep 13 14:39:19 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id1116 vendor LGD xserver.version: 2:1.18.4-0ubuntu0.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1863049/+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 1862910] Re: gnome-shell leaking memory in interaction with appimagelauncher
Thanks for that investigation. It's not completely clear to me that upstream bug 294 is/was about leaks. Maybe you should open a new one? https://github.com/TheAssassin/AppImageLauncher/issues ** Summary changed: - gnome-shell leaking memory in interaction with appimagelauncher + gnome-shell leaking memory when a customized AppImageLauncher is running ** Changed in: gnome-shell (Ubuntu) Importance: Undecided => Medium ** Tags added: leak ** Changed in: gnome-shell (Ubuntu) Importance: Medium => Low -- 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/1862910 Title: gnome-shell leaking memory when a customized AppImageLauncher is running Status in gnome-shell package in Ubuntu: New Bug description: Edited description: To replicate the problem (on Ubuntu 19.10 running Ubuntu Gnome) 1. Install AppImageLauncher from https://github.com/TheAssassin/AppImageLauncher/releases by downloading version 2.1.0 deb file (appimagelauncher_2.1.0-travis897.d1be7e7.bionic_amd64.deb) and install it. If necessary run sudo apt install -f to fix missing dependencies. 2. Run it and change the appimage destination location to ~/apps/appimages. It is necessary to change it away from the default setting in order for the problem to appear, though probably the actual destination is not important). Ensure that Auto start auto- integration daemon is selected. 3. Download an appimage (I downloaded Cura 4.4.1 from https://github.com/Ultimaker/Cura/releases/tag/4.4.1) I don't know whether any appimage would do, probably it would. In fact I don't know whether this step and the next need to be done at all. 4. Open it with appimagelauncher (this can be done by double clicking it in nautilus) and tell it to move it and run the application. Then close the application. 5. It may be necessary to reboot at this point I don't know. 6. Logon using Ubuntu (Gnome) and watch the memory usage of gnome- shell. It may take a few minutes to get going but then the memory used will start increasing at several MB/minute. There is an issue open against appimage launcher which is likely the same problem. https://github.com/TheAssassin/AppImageLauncher/issues/294 Original description: On one of my machines which has been upgraded over several years and is now running 19.10 just one of the configured users appears to be seeing a dramatic memory leak in gnome-shell, even when nothing is happening on the UI. Immediately after logging on, using the Ubuntu selection from the logon screen, gnome shell shows as using about 134MB. From there it climbs at about 300MB per hour and after a few hours the machine grinds to a crawl, not surprisingly. This happens even if the user logs on and then the machine is left completely alone. Logout and back in frees all the memory. A test user I have configured sees no such problem. I have uninstalled all extensions apart from the system ones, disabled all the system ones and reset all the gnome settings using dconf reset -f /org/gnome/ to no avail. Also I have removed ~/.local/share/gnome-shell and allowed it to recreate it. Also I have removed .compiz, .config/dconf/user, .gconf, .gnome, .gnome2. I can't see anything obvious in the log. It must be something in my settings that is triggering it as the other user does not see it, but I have run out of ideas on what to try. See also bug #1856516 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.1+git20191024-1ubuntu1~19.10.1 ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13 Uname: Linux 5.3.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Feb 12 08:54:21 2020 DisplayManager: gdm3 InstallationDate: Installed on 2014-10-21 (1939 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20141017) RelatedPackageVersions: mutter-common 3.34.1+git20191107-1ubuntu1~19.10.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to eoan on 2020-01-27 (15 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1862910/+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 1863184] Re: Application does not stay open on Ubuntu 20.04 and closes automatically
Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps: 1. Look in /var/crash for crash files and if found run: ubuntu-bug YOURFILE.crash Then tell us the ID of the newly-created bug. 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. 3. If step 2 also failed then apply the workaround from bug 994921, reboot, reproduce the crash, and retry step 1. Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself. ** Changed in: totem (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1863184 Title: Application does not stay open on Ubuntu 20.04 and closes automatically Status in totem package in Ubuntu: Incomplete Bug description: Hello Ubuntu Team When we click on the totem it opens and closes automatically, as seen in the gif image on the link below. [img]https://i.imgur.com/TYA8hrg.mp4[/img] I tried to report this error by ubuntu-bug -w, but an error message appears that can be seen in the gif image below. [img]https://i.imgur.com/xm9QSb9.mp4[/img] --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-04-28 (291 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Package: totem 3.34.1-2ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Tags: focal Uname: Linux 5.4.0-12-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-02-04 (9 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo XorgLog: Error: [Errno 2] Arquivo ou diretório inexistente: '/var/log/Xorg.0.log' _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1863184/+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 1863083] Re: systemerror detected
Ubuntu 14.04 reached end of standard support in April 2019: https://wiki.ubuntu.com/Releases If you would like to continue with free support then please update to a newer Ubuntu version and tell us if the problem still occurs. If you would like to continue with Ubuntu 14.04 then there is a paid support option detailed at https://www.ubuntu.com/esm ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Won't Fix -- 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/1863083 Title: systemerror detected Status in Ubuntu: Won't Fix Bug description: get message systemerror detected. press button sent nothing heppens on reboot same message don 't know what error is detected ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 4.4.0-148.174~14.04.1-generic 4.4.177 Uname: Linux 4.4.0-148-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.29 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Thu Feb 13 11:12:23 2020 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation 82945G/GZ Integrated Graphics Controller [8086:2772] (rev 02) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:817a] InstallationDate: Installed on 2016-09-26 (1234 days ago) InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140416.2) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-148-generic root=UUID=c763e4d7-fb91-470e-88b9-75aeb931dd49 ro nomode=1 SourcePackage: xorg SystemImageInfo: Error: [Errno 2] Bestand of map bestaat niet: 'system-image-cli' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/01/2006 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0304 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5LD2-VM DH dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0304:bd06/01/2006:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5LD2-VMDH:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.11.3+14.04.20160425-0ubuntu1 version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri N/A version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Thu Feb 13 10:48:03 2020 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputLogitech USB Keyboard KEYBOARD, id 8 inputLogitech USB Keyboard KEYBOARD, id 9 inputDarfon USB Optical Mouse MOUSE, id 10 xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 505 vendor SAM xserver.version: 2:1.16.0-1ubuntu1.2~trusty2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1863083/+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 1863123] Re: Fail to connect bug still persists - Removal tool???
*** This bug is a duplicate of bug 1858280 *** https://bugs.launchpad.net/bugs/1858280 ** This bug has been marked a duplicate of bug 1858280 Firefox reports "cannot connect to internet" message -- 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/1863123 Title: Fail to connect bug still persists - Removal tool??? Status in xorg package in Ubuntu: New Bug description: Any help in removing this bug that randomly mimics connection failure. After x-Diagnose program and reporting this bug, it clears out but always reappears later again and again. Is there a removal tool or program that can clear it out for good? I appreciate any tips or help that I can get. Thank you for your time in reading this report. J.Chosta ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-76.86-generic 4.15.18 Uname: Linux 4.15.0-76-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Thu Feb 13 10:27:26 2020 DistUpgraded: 2018-12-25 11:16:26,692 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RV610 [Radeon HD 2400 PRO] [1002:94c3] (prog-if 00 [VGA controller]) Subsystem: Dell Radeon HD 2400 Pro [1028:0302] InstallationDate: Installed on 2016-08-03 (1289 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: Dell Inc. Dell XPS420 ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-76-generic root=UUID=e737e1ac-8869-44b7-a03f-477223f8 ro drm.debug=0xe plymouth:debug SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2018-12-25 (414 days ago) dmi.bios.date: 03/27/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: A04 dmi.board.name: 0TP406 dmi.board.vendor: Dell Inc. dmi.chassis.type: 7 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA04:bd03/27/2008:svnDellInc.:pnDellXPS420:pvr:rvnDellInc.:rn0TP406:rvr:cvnDellInc.:ct7:cvr: dmi.product.name: Dell XPS420 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 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 xserver.bootTime: Tue Dec 25 08:33:58 2018 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputLogitech Logitech USB Speaker KEYBOARD, id 8 inputLogitech USB-PS/2 Optical Mouse MOUSE, id 9 inputDell Dell USB Keyboard KEYBOARD, id 10 xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-0ubuntu0.8 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1863123/+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 1844458] Re: Drop transitional flashplugin-downloader package
Can we drop all the flash packages before focal becomes 20.04 LTS? I don't think we should have flash in the release at all if we know it won't be supportable after a few months. Thanks -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to flashplugin-nonfree in Ubuntu. https://bugs.launchpad.net/bugs/1844458 Title: Drop transitional flashplugin-downloader package Status in flashplugin-nonfree package in Ubuntu: New Bug description: I think the transition is done. It's in 16.04-19.10 as a transitional package. Found this because it made this list: https://discourse.ubuntu.com/t /community-process-for-32-bit-compatibility/12598 I don't want anyone thinking that 32-bit Flash is supported on Linux. Happy to make a debdiff (or if you point me at where the code is - the code here seems out of date) to make a PR. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flashplugin-nonfree/+bug/1844458/+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 1810541] Re: package flashplugin-installer 32.0.0.101ubuntu0.16.04.1 failed to install/upgrade: problèmes de dépendances - laissé non configuré
*** This bug is a duplicate of bug 1728697 *** https://bugs.launchpad.net/bugs/1728697 ** This bug has been marked a duplicate of bug 1728697 package flashplugin-installer 27.0.0.183ubuntu0.16.04.1 failed to install/upgrade: problemas de dependencias - se deja sin configurar -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to flashplugin-nonfree in Ubuntu. https://bugs.launchpad.net/bugs/1810541 Title: package flashplugin-installer 32.0.0.101ubuntu0.16.04.1 failed to install/upgrade: problèmes de dépendances - laissé non configuré Status in flashplugin-nonfree package in Ubuntu: New Bug description: Error on Ubuntu 16.04 ProblemType: Package DistroRelease: Ubuntu 16.04 Package: flashplugin-installer 32.0.0.101ubuntu0.16.04.1 ProcVersionSignature: Ubuntu 4.15.0-43.46~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Thu Jan 3 06:40:02 2019 DpkgHistoryLog: Start-Date: 2019-01-03 06:39:53 Commandline: /usr/bin/unattended-upgrade Upgrade: tzdata:amd64 (2018g-0ubuntu0.16.04, 2018i-0ubuntu0.16.04) ErrorMessage: problèmes de dépendances - laissé non configuré InstallationDate: Installed on 2018-05-31 (218 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) RelatedPackageVersions: dpkg 1.18.4ubuntu1.5 apt 1.2.29 SourcePackage: flashplugin-nonfree Title: package flashplugin-installer 32.0.0.101ubuntu0.16.04.1 failed to install/upgrade: problèmes de dépendances - laissé non configuré UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flashplugin-nonfree/+bug/1810541/+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 1831203] Re: flash overloads cpu, kills performance
Yes, 100% means an entire core is being used; 117% means the process is multi-threaded and threads are executing on several cores at once, thus the total is above 100%. As for flash's poor performance, that'd be on Adobe to sort out -- given they are only doing security fixes for flash, for only a few months at that, I suspect they won't try to fix performance problems. Thanks ** Changed in: flashplugin-nonfree (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to flashplugin-nonfree in Ubuntu. https://bugs.launchpad.net/bugs/1831203 Title: flash overloads cpu, kills performance Status in flashplugin-nonfree package in Ubuntu: Won't Fix Bug description: Description: Ubuntu 16.04.6 LTS Release: 16.04 # apt-cache policy flashplugin-installer flashplugin-installer: Installed: 32.0.0.192ubuntu0.16.04.1 Candidate: 32.0.0.192ubuntu0.16.04.1 Version table: *** 32.0.0.192ubuntu0.16.04.1 500 500 http://us.archive.ubuntu.com/ubuntu xenial-updates/multiverse amd64 Packages 500 http://security.ubuntu.com/ubuntu xenial-security/multiverse amd64 Packages 100 /var/lib/dpkg/status 11.2.202.616ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu xenial/multiverse amd64 Packages System freezes for ten seconds and/or much longer. I would say "See attached screenshot"... but that doesn't appear to be an option here. Note CPU usage by plugin. Also please note virtual memory usage by firefox, I don't know if it's relevant. I have 8GB RAM. I frequently have a dozen windows and 50+ tabs open. Some windows have many more tabs than others. I have to wonder if this isn't a kernel bug? Or a top bug? How can a system use more than 100% of the CPU? Is it trying to somehow express the fact that I have 8 cores and 117% means something? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flashplugin-nonfree/+bug/1831203/+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 1863142] Re: [nvidia] Xorg crashed with SIGSEGV in xf86ScreenSetCursor(pCurs=NULL)
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nvidia-graphics-drivers (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/1863142 Title: [nvidia] Xorg crashed with SIGSEGV in xf86ScreenSetCursor(pCurs=NULL) Status in nvidia-graphics-drivers package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-440 package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Confirmed Bug description: https://errors.ubuntu.com/problem/ea7655e8bec62deae73df2b30259cb413e61bef9 --- I observed the following on Eoan as well with nvidia drivers older than 440. 1) a windows 10 VM running in a qemu-kvm VM: pc-q35-3.1 machine type, QXL + SPICE: 2) When a host is booted with `prime-select intel` observing guest video output works fine with both virt-viewer (over SPICE) and remmina (over RDP); 3) With `prime-select nvidia` Xorg crashes as described in https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1862895 ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: xserver-xorg-core 2:1.20.7-2ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair 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.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.59 Thu Jan 30 01:00:41 UTC 2020 GCC version: gcc version 9.2.1 20200203 (Ubuntu 9.2.1-28ubuntu1) ApportVersion: 2.20.11-0ubuntu16 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' CurrentDesktop: ubuntu:GNOME Date: Thu Feb 13 20:16:07 2020 DistUpgraded: 2020-02-09 15:34:46,903 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu DkmsStatus: fwts-efi-runtime-dkms, 20.01.00, 5.3.0-29-generic, x86_64: installed (WARNING! Diff between built and installed module!) fwts-efi-runtime-dkms, 20.01.00, 5.4.0-12-generic, x86_64: installed (WARNING! Diff between built and installed module!) nvidia, 440.59, 5.4.0-12-generic, x86_64: installed ExecutablePath: /usr/lib/xorg/Xorg ExecutableTimestamp: 1579009393 GraphicsCard: Intel Corporation HD Graphics 630 [8086:591b] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Razer USA Ltd. HD Graphics 630 [1a58:6755] NVIDIA Corporation GP106M [GeForce GTX 1060 Mobile] [10de:1c20] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Razer USA Ltd. GP106M [GeForce GTX 1060 Mobile] [1a58:6755] InstallationDate: Installed on 2018-05-13 (641 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Razer Blade ProcCmdline: /usr/lib/xorg/Xorg vt2 -displayfd 3 -auth /run/user/1000/gdm/Xauthority -background none -noreset -keeptty -verbose 3 ProcCwd: /home/dima ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-12-generic root=UUID=8c1115d9-2cee-41a9-864f-d4e57d662706 ro rootflags=subvol=@ button.lid_init_state=open amdgpu.dpm=1 amdgpu.ppfeaturemask=0x Signal: 6 SourcePackage: nvidia-graphics-drivers StacktraceTop: System () () () () () at /lib/x86_64-linux-gnu/libpthread.so.0 Title: Xorg crashed with SIGABRT in System() UpgradeStatus: Upgraded to focal on 2020-02-09 (4 days ago) UserGroups: adm cdrom dip libvirt lpadmin lxd microk8s plugdev sambashare sudo dmi.bios.date: 02/22/2018 dmi.bios.vendor: Razer dmi.bios.version: 4.02 dmi.board.name: Razer dmi.board.vendor: Razer dmi.chassis.type: 9 dmi.chassis.vendor: Razer dmi.modalias: dmi:bvnRazer:bvr4.02:bd02/22/2018:svnRazer:pnBlade:pvr6.06:rvnRazer:rnRazer:rvr:cvnRazer:ct9:cvr: dmi.product.family: 1A586755 dmi.product.name: Blade dmi.product.sku: RZ09-01953E72 dmi.product.version: 6.06 dmi.sys.vendor: Razer separator: version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 19.3.3-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.3.3-1ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-
[Desktop-packages] [Bug 1728697] Re: package flashplugin-installer 27.0.0.183ubuntu0.16.04.1 failed to install/upgrade: problemas de dependencias - se deja sin configurar
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: flashplugin-nonfree (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to flashplugin-nonfree in Ubuntu. https://bugs.launchpad.net/bugs/1728697 Title: package flashplugin-installer 27.0.0.183ubuntu0.16.04.1 failed to install/upgrade: problemas de dependencias - se deja sin configurar Status in flashplugin-nonfree package in Ubuntu: Confirmed Bug description: still not resolved ProblemType: Package DistroRelease: Ubuntu 16.04 Package: flashplugin-installer 27.0.0.183ubuntu0.16.04.1 ProcVersionSignature: Ubuntu 4.10.0-37.41~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-37-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 Date: Mon Oct 30 13:35:46 2017 ErrorMessage: problemas de dependencias - se deja sin configurar InstallationDate: Installed on 2017-10-22 (8 days ago) InstallationMedia: Ubuntu-GNOME 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.24 SourcePackage: flashplugin-nonfree Title: package flashplugin-installer 27.0.0.183ubuntu0.16.04.1 failed to install/upgrade: problemas de dependencias - se deja sin configurar UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flashplugin-nonfree/+bug/1728697/+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 1741190] Re: package flashplugin-installer 28.0.0.126ubuntu0.16.04.1 failed to install/upgrade: проблемы зависимостей — оставляем не настроенным
*** This bug is a duplicate of bug 1728697 *** https://bugs.launchpad.net/bugs/1728697 ** This bug has been marked a duplicate of bug 1728697 package flashplugin-installer 27.0.0.183ubuntu0.16.04.1 failed to install/upgrade: problemas de dependencias - se deja sin configurar -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to flashplugin-nonfree in Ubuntu. https://bugs.launchpad.net/bugs/1741190 Title: package flashplugin-installer 28.0.0.126ubuntu0.16.04.1 failed to install/upgrade: проблемы зависимостей — оставляем не настроенным Status in flashplugin-nonfree package in Ubuntu: Confirmed Bug description: happens from time to time ProblemType: Package DistroRelease: Ubuntu 16.04 Package: flashplugin-installer 28.0.0.126ubuntu0.16.04.1 ProcVersionSignature: Ubuntu 4.4.0-104.127-generic 4.4.98 Uname: Linux 4.4.0-104-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.13 Architecture: amd64 Date: Tue Jan 2 16:29:08 2018 ErrorMessage: проблемы зависимостей — оставляем не настроенным InstallationDate: Installed on 2016-10-02 (458 days ago) InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.19 SourcePackage: flashplugin-nonfree Title: package flashplugin-installer 28.0.0.126ubuntu0.16.04.1 failed to install/upgrade: проблемы зависимостей — оставляем не настроенным UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flashplugin-nonfree/+bug/1741190/+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 1863142] Re: [nvidia] Xorg crashed with SIGSEGV in xf86ScreenSetCursor(pCurs=NULL)
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nvidia-graphics-drivers-440 (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/1863142 Title: [nvidia] Xorg crashed with SIGSEGV in xf86ScreenSetCursor(pCurs=NULL) Status in nvidia-graphics-drivers package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-440 package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Confirmed Bug description: https://errors.ubuntu.com/problem/ea7655e8bec62deae73df2b30259cb413e61bef9 --- I observed the following on Eoan as well with nvidia drivers older than 440. 1) a windows 10 VM running in a qemu-kvm VM: pc-q35-3.1 machine type, QXL + SPICE: 2) When a host is booted with `prime-select intel` observing guest video output works fine with both virt-viewer (over SPICE) and remmina (over RDP); 3) With `prime-select nvidia` Xorg crashes as described in https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1862895 ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: xserver-xorg-core 2:1.20.7-2ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair 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.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.59 Thu Jan 30 01:00:41 UTC 2020 GCC version: gcc version 9.2.1 20200203 (Ubuntu 9.2.1-28ubuntu1) ApportVersion: 2.20.11-0ubuntu16 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' CurrentDesktop: ubuntu:GNOME Date: Thu Feb 13 20:16:07 2020 DistUpgraded: 2020-02-09 15:34:46,903 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu DkmsStatus: fwts-efi-runtime-dkms, 20.01.00, 5.3.0-29-generic, x86_64: installed (WARNING! Diff between built and installed module!) fwts-efi-runtime-dkms, 20.01.00, 5.4.0-12-generic, x86_64: installed (WARNING! Diff between built and installed module!) nvidia, 440.59, 5.4.0-12-generic, x86_64: installed ExecutablePath: /usr/lib/xorg/Xorg ExecutableTimestamp: 1579009393 GraphicsCard: Intel Corporation HD Graphics 630 [8086:591b] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Razer USA Ltd. HD Graphics 630 [1a58:6755] NVIDIA Corporation GP106M [GeForce GTX 1060 Mobile] [10de:1c20] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Razer USA Ltd. GP106M [GeForce GTX 1060 Mobile] [1a58:6755] InstallationDate: Installed on 2018-05-13 (641 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Razer Blade ProcCmdline: /usr/lib/xorg/Xorg vt2 -displayfd 3 -auth /run/user/1000/gdm/Xauthority -background none -noreset -keeptty -verbose 3 ProcCwd: /home/dima ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-12-generic root=UUID=8c1115d9-2cee-41a9-864f-d4e57d662706 ro rootflags=subvol=@ button.lid_init_state=open amdgpu.dpm=1 amdgpu.ppfeaturemask=0x Signal: 6 SourcePackage: nvidia-graphics-drivers StacktraceTop: System () () () () () at /lib/x86_64-linux-gnu/libpthread.so.0 Title: Xorg crashed with SIGABRT in System() UpgradeStatus: Upgraded to focal on 2020-02-09 (4 days ago) UserGroups: adm cdrom dip libvirt lpadmin lxd microk8s plugdev sambashare sudo dmi.bios.date: 02/22/2018 dmi.bios.vendor: Razer dmi.bios.version: 4.02 dmi.board.name: Razer dmi.board.vendor: Razer dmi.chassis.type: 9 dmi.chassis.vendor: Razer dmi.modalias: dmi:bvnRazer:bvr4.02:bd02/22/2018:svnRazer:pnBlade:pvr6.06:rvnRazer:rnRazer:rvr:cvnRazer:ct9:cvr: dmi.product.family: 1A586755 dmi.product.name: Blade dmi.product.sku: RZ09-01953E72 dmi.product.version: 6.06 dmi.sys.vendor: Razer separator: version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 19.3.3-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.3.3-1ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-vi
[Desktop-packages] [Bug 1863142] Re: [nvidia] Xorg crashed with SIGSEGV in xf86ScreenSetCursor(pCurs=NULL)
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/1863142 Title: [nvidia] Xorg crashed with SIGSEGV in xf86ScreenSetCursor(pCurs=NULL) Status in nvidia-graphics-drivers package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-440 package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Confirmed Bug description: https://errors.ubuntu.com/problem/ea7655e8bec62deae73df2b30259cb413e61bef9 --- I observed the following on Eoan as well with nvidia drivers older than 440. 1) a windows 10 VM running in a qemu-kvm VM: pc-q35-3.1 machine type, QXL + SPICE: 2) When a host is booted with `prime-select intel` observing guest video output works fine with both virt-viewer (over SPICE) and remmina (over RDP); 3) With `prime-select nvidia` Xorg crashes as described in https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1862895 ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: xserver-xorg-core 2:1.20.7-2ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair 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.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.59 Thu Jan 30 01:00:41 UTC 2020 GCC version: gcc version 9.2.1 20200203 (Ubuntu 9.2.1-28ubuntu1) ApportVersion: 2.20.11-0ubuntu16 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' CurrentDesktop: ubuntu:GNOME Date: Thu Feb 13 20:16:07 2020 DistUpgraded: 2020-02-09 15:34:46,903 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu DkmsStatus: fwts-efi-runtime-dkms, 20.01.00, 5.3.0-29-generic, x86_64: installed (WARNING! Diff between built and installed module!) fwts-efi-runtime-dkms, 20.01.00, 5.4.0-12-generic, x86_64: installed (WARNING! Diff between built and installed module!) nvidia, 440.59, 5.4.0-12-generic, x86_64: installed ExecutablePath: /usr/lib/xorg/Xorg ExecutableTimestamp: 1579009393 GraphicsCard: Intel Corporation HD Graphics 630 [8086:591b] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Razer USA Ltd. HD Graphics 630 [1a58:6755] NVIDIA Corporation GP106M [GeForce GTX 1060 Mobile] [10de:1c20] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Razer USA Ltd. GP106M [GeForce GTX 1060 Mobile] [1a58:6755] InstallationDate: Installed on 2018-05-13 (641 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Razer Blade ProcCmdline: /usr/lib/xorg/Xorg vt2 -displayfd 3 -auth /run/user/1000/gdm/Xauthority -background none -noreset -keeptty -verbose 3 ProcCwd: /home/dima ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-12-generic root=UUID=8c1115d9-2cee-41a9-864f-d4e57d662706 ro rootflags=subvol=@ button.lid_init_state=open amdgpu.dpm=1 amdgpu.ppfeaturemask=0x Signal: 6 SourcePackage: nvidia-graphics-drivers StacktraceTop: System () () () () () at /lib/x86_64-linux-gnu/libpthread.so.0 Title: Xorg crashed with SIGABRT in System() UpgradeStatus: Upgraded to focal on 2020-02-09 (4 days ago) UserGroups: adm cdrom dip libvirt lpadmin lxd microk8s plugdev sambashare sudo dmi.bios.date: 02/22/2018 dmi.bios.vendor: Razer dmi.bios.version: 4.02 dmi.board.name: Razer dmi.board.vendor: Razer dmi.chassis.type: 9 dmi.chassis.vendor: Razer dmi.modalias: dmi:bvnRazer:bvr4.02:bd02/22/2018:svnRazer:pnBlade:pvr6.06:rvnRazer:rnRazer:rvr:cvnRazer:ct9:cvr: dmi.product.family: 1A586755 dmi.product.name: Blade dmi.product.sku: RZ09-01953E72 dmi.product.version: 6.06 dmi.sys.vendor: Razer separator: version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 19.3.3-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.3.3-1ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xse
[Desktop-packages] [Bug 1863142] Re: [nvidia] Xorg crashed with SIGSEGV in xf86ScreenSetCursor(pCurs=NULL)
Tracking in: https://errors.ubuntu.com/problem/ea7655e8bec62deae73df2b30259cb413e61bef9 ** Description changed: + https://errors.ubuntu.com/problem/ea7655e8bec62deae73df2b30259cb413e61bef9 + + --- + I observed the following on Eoan as well with nvidia drivers older than 440. 1) a windows 10 VM running in a qemu-kvm VM: pc-q35-3.1 machine type, QXL + SPICE: 2) When a host is booted with `prime-select intel` observing guest video output works fine with both virt-viewer (over SPICE) and remmina (over RDP); 3) With `prime-select nvidia` Xorg crashes as described in https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1862895 - ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: xserver-xorg-core 2:1.20.7-2ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair 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.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.59 Thu Jan 30 01:00:41 UTC 2020 GCC version: gcc version 9.2.1 20200203 (Ubuntu 9.2.1-28ubuntu1) ApportVersion: 2.20.11-0ubuntu16 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' CurrentDesktop: ubuntu:GNOME Date: Thu Feb 13 20:16:07 2020 DistUpgraded: 2020-02-09 15:34:46,903 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu DkmsStatus: fwts-efi-runtime-dkms, 20.01.00, 5.3.0-29-generic, x86_64: installed (WARNING! Diff between built and installed module!) fwts-efi-runtime-dkms, 20.01.00, 5.4.0-12-generic, x86_64: installed (WARNING! Diff between built and installed module!) nvidia, 440.59, 5.4.0-12-generic, x86_64: installed ExecutablePath: /usr/lib/xorg/Xorg ExecutableTimestamp: 1579009393 GraphicsCard: Intel Corporation HD Graphics 630 [8086:591b] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Razer USA Ltd. HD Graphics 630 [1a58:6755] NVIDIA Corporation GP106M [GeForce GTX 1060 Mobile] [10de:1c20] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Razer USA Ltd. GP106M [GeForce GTX 1060 Mobile] [1a58:6755] InstallationDate: Installed on 2018-05-13 (641 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Razer Blade ProcCmdline: /usr/lib/xorg/Xorg vt2 -displayfd 3 -auth /run/user/1000/gdm/Xauthority -background none -noreset -keeptty -verbose 3 ProcCwd: /home/dima ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-12-generic root=UUID=8c1115d9-2cee-41a9-864f-d4e57d662706 ro rootflags=subvol=@ button.lid_init_state=open amdgpu.dpm=1 amdgpu.ppfeaturemask=0x Signal: 6 SourcePackage: nvidia-graphics-drivers StacktraceTop: System () () () () () at /lib/x86_64-linux-gnu/libpthread.so.0 Title: Xorg crashed with SIGABRT in System() UpgradeStatus: Upgraded to focal on 2020-02-09 (4 days ago) UserGroups: adm cdrom dip libvirt lpadmin lxd microk8s plugdev sambashare sudo dmi.bios.date: 02/22/2018 dmi.bios.vendor: Razer dmi.bios.version: 4.02 dmi.board.name: Razer dmi.board.vendor: Razer dmi.chassis.type: 9 dmi.chassis.vendor: Razer dmi.modalias: dmi:bvnRazer:bvr4.02:bd02/22/2018:svnRazer:pnBlade:pvr6.06:rvnRazer:rnRazer:rvr:cvnRazer:ct9:cvr: dmi.product.family: 1A586755 dmi.product.name: Blade dmi.product.sku: RZ09-01953E72 dmi.product.version: 6.06 dmi.sys.vendor: Razer separator: version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 19.3.3-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.3.3-1ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 -- 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/1863142 Title: [nvidia] Xorg crashed with SIGSEGV in xf86ScreenSetCursor(pCurs=NULL) Status in nvidia-graphics-drivers package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-440 package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu:
[Desktop-packages] [Bug 1863142] Re: Xorg crashed with SIGSEGV in xf86ScreenSetCursor
** Summary changed: - [focal][nvidia][gdm3] Xorg crashes when virt-viewer or remmina are used to connect to a windows10 VM + Xorg crashed with SIGSEGV in xf86ScreenSetCursor ** Information type changed from Private to Public ** No longer affects: gdm3 (Ubuntu) ** Tags added: nvidia ** Summary changed: - Xorg crashed with SIGSEGV in xf86ScreenSetCursor + [nvidia] Xorg crashed with SIGSEGV in xf86ScreenSetCursor(pCurs=NULL) ** Also affects: nvidia-graphics-drivers-440 (Ubuntu) Importance: Undecided Status: New -- 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/1863142 Title: [nvidia] Xorg crashed with SIGSEGV in xf86ScreenSetCursor(pCurs=NULL) Status in nvidia-graphics-drivers package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-440 package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Confirmed Bug description: https://errors.ubuntu.com/problem/ea7655e8bec62deae73df2b30259cb413e61bef9 --- I observed the following on Eoan as well with nvidia drivers older than 440. 1) a windows 10 VM running in a qemu-kvm VM: pc-q35-3.1 machine type, QXL + SPICE: 2) When a host is booted with `prime-select intel` observing guest video output works fine with both virt-viewer (over SPICE) and remmina (over RDP); 3) With `prime-select nvidia` Xorg crashes as described in https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1862895 ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: xserver-xorg-core 2:1.20.7-2ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair 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.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.59 Thu Jan 30 01:00:41 UTC 2020 GCC version: gcc version 9.2.1 20200203 (Ubuntu 9.2.1-28ubuntu1) ApportVersion: 2.20.11-0ubuntu16 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' CurrentDesktop: ubuntu:GNOME Date: Thu Feb 13 20:16:07 2020 DistUpgraded: 2020-02-09 15:34:46,903 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu DkmsStatus: fwts-efi-runtime-dkms, 20.01.00, 5.3.0-29-generic, x86_64: installed (WARNING! Diff between built and installed module!) fwts-efi-runtime-dkms, 20.01.00, 5.4.0-12-generic, x86_64: installed (WARNING! Diff between built and installed module!) nvidia, 440.59, 5.4.0-12-generic, x86_64: installed ExecutablePath: /usr/lib/xorg/Xorg ExecutableTimestamp: 1579009393 GraphicsCard: Intel Corporation HD Graphics 630 [8086:591b] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Razer USA Ltd. HD Graphics 630 [1a58:6755] NVIDIA Corporation GP106M [GeForce GTX 1060 Mobile] [10de:1c20] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Razer USA Ltd. GP106M [GeForce GTX 1060 Mobile] [1a58:6755] InstallationDate: Installed on 2018-05-13 (641 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Razer Blade ProcCmdline: /usr/lib/xorg/Xorg vt2 -displayfd 3 -auth /run/user/1000/gdm/Xauthority -background none -noreset -keeptty -verbose 3 ProcCwd: /home/dima ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-12-generic root=UUID=8c1115d9-2cee-41a9-864f-d4e57d662706 ro rootflags=subvol=@ button.lid_init_state=open amdgpu.dpm=1 amdgpu.ppfeaturemask=0x Signal: 6 SourcePackage: nvidia-graphics-drivers StacktraceTop: System () () () () () at /lib/x86_64-linux-gnu/libpthread.so.0 Title: Xorg crashed with SIGABRT in System() UpgradeStatus: Upgraded to focal on 2020-02-09 (4 days ago) UserGroups: adm cdrom dip libvirt lpadmin lxd microk8s plugdev sambashare sudo dmi.bios.date: 02/22/2018 dmi.bios.vendor: Razer dmi.bios.version: 4.02 dmi.board.name: Razer dmi.board.vendor: Razer dmi.chassis.type: 9 dmi.chassis.vendor: Razer dmi.modalias: dmi:bvnRazer:bvr4.02:bd02/22/2018:svnRazer:pnBlade:pvr6.06:rvnRazer:rnRazer:rvr:cvnRazer:ct9:cvr: dmi.product.family: 1A586755 dmi.product.name: Blade dmi.product.sku: RZ09-01953E72 dmi.product.version: 6.06 dmi.sys.vendor: Razer separator: version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 19.3.3-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.3.3-1ubuntu
[Desktop-packages] [Bug 1859970] Re: Screenshots from an area selection have tinted colour when running wayland
It looks like the upstream bug https://gitlab.gnome.org/GNOME/gnome- shell/issues/1999 was closed without a resolution. It's not "Fix Released" so I have removed the task to avoid confusion. ** No longer affects: gnome-shell -- 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/1859970 Title: Screenshots from an area selection have tinted colour when running wayland Status in gnome-shell package in Ubuntu: Triaged Status in mutter package in Ubuntu: Triaged Bug description: All my screenshots taken on 20.04 with wayland have an orange tint to them. This appears to be the overlay which you get when selecting an area. Full screen screenshots and window screenshots are unaffected, only area screenshots appear to have the problem. Steps to reproduce Login to a wayland session Hold down Shift and Press PrintScreen Select an area to screenshot Navigate to ~/Pictures Open the picture you just took Expected outcome Screenshot of area taken as it would have been on screen Actual outcome Screenshot is taken, but has an orange border and overlay. (see screenshot) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-screenshot 3.33.90-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3 Uname: Linux 5.4.0-9-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Jan 16 11:50:50 2020 InstallationDate: Installed on 2018-02-04 (710 days ago) InstallationMedia: neon userlts "Xenial" - Build amd64 LIVE Binary 20180202-11:07 SourcePackage: gnome-screenshot UpgradeStatus: Upgraded to focal on 2020-01-08 (7 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1859970/+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 1859774] Re: Full screen window becomes "small" in the upper left of the screen...
That screenshot is 1920x1034 so can I assume you cropped it by hand? If not then that's part of the issue. I think the other part of the issue is/was the use of non-native (emulated) modes. This might not have been your choice, but might be caused by the applications themselves... Can you please: * Confirm your chosen settings are 1920x1080 * Confirm you cropped the above screenshot by hand * Attach fresh output from 'xrandr'? * Try removing ~/.config/monitors.xml again. -- 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/1859774 Title: Full screen window becomes "small" in the upper left of the screen... Status in gnome-shell package in Ubuntu: Incomplete Bug description: This happens with a number of different programs, so I suspect it is a window manager bug. The best way to describe it is with a screen shot. The only responsive part of the screen is the small window in the upper left. You can hit the little maximize box and it goes back to full screen okay, but after a while it comes back to this. It can be annoying, because sometimes you can't quickly see what happened to the title bar. I'm using Ubuntu 19.10. This has been happening for about a week. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1859774/+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 1859774] Re: Full screen window becomes "small" in the upper left of the screen...
Please also keep all gnome-shell extensions uninstalled while reproducing this bug. We need to ensure they're not clouding the situation. ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- 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/1859774 Title: Full screen window becomes "small" in the upper left of the screen... Status in gnome-shell package in Ubuntu: Incomplete Bug description: This happens with a number of different programs, so I suspect it is a window manager bug. The best way to describe it is with a screen shot. The only responsive part of the screen is the small window in the upper left. You can hit the little maximize box and it goes back to full screen okay, but after a while it comes back to this. It can be annoying, because sometimes you can't quickly see what happened to the title bar. I'm using Ubuntu 19.10. This has been happening for about a week. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1859774/+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 1756976] Re: package flashplugin-installer 28.0.0.161ubuntu0.16.04.1 failed to install/upgrade: не удалось установить новую версию «/usr/share/doc/flashplugin-installer/changel
Hmm, the error message says no more free space, but the df output shows there's space left. How'd this work out? Thanks ** Changed in: flashplugin-nonfree (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to flashplugin-nonfree in Ubuntu. https://bugs.launchpad.net/bugs/1756976 Title: package flashplugin-installer 28.0.0.161ubuntu0.16.04.1 failed to install/upgrade: не удалось установить новую версию «/usr/share/doc /flashplugin-installer/changelog.gz»: На устройстве не осталось свободного места Status in flashplugin-nonfree package in Ubuntu: Incomplete Bug description: 1 ProblemType: Package DistroRelease: Ubuntu 16.04 Package: flashplugin-installer 28.0.0.161ubuntu0.16.04.1 ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98 Uname: Linux 4.4.0-116-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 Date: Fri Mar 16 06:07:35 2018 ErrorMessage: не удалось установить новую версию «/usr/share/doc/flashplugin-installer/changelog.gz»: На устройстве не осталось свободного места InstallationDate: Installed on 2016-12-12 (462 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RelatedPackageVersions: dpkg 1.18.4ubuntu1.3 apt 1.2.25 SourcePackage: flashplugin-nonfree Title: package flashplugin-installer 28.0.0.161ubuntu0.16.04.1 failed to install/upgrade: не удалось установить новую версию «/usr/share/doc/flashplugin-installer/changelog.gz»: На устройстве не осталось свободного места UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flashplugin-nonfree/+bug/1756976/+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 1862895] Re: [focal][nvidia][gdm3] Xorg crashes when virt-viewer or remmina are used to connect to a windows10 VM
*** This bug is a duplicate of bug 1863142 *** https://bugs.launchpad.net/bugs/1863142 Great, thanks. Let's use bug 1863142. ** This bug has been marked a duplicate of private bug 1863142 -- 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/1862895 Title: [focal][nvidia][gdm3] Xorg crashes when virt-viewer or remmina are used to connect to a windows10 VM Status in gdm3 package in Ubuntu: New Status in xorg-server package in Ubuntu: New Bug description: I observed the following on Eoan as well with nvidia drivers older than 440. 1) a windows 10 VM running in a qemu-kvm VM: pc-q35-3.1 machine type, QXL + SPICE: 2) When a host is booted with `prime-select intel` observing guest video output works fine with both virt-viewer (over SPICE) and remmina (over RDP); 3) With `prime-select nvidia` Remmina: Feb 12 10:15:22 blade gnome-shell[13670]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x2a7 Feb 12 10:15:29 blade org.remmina.Remmina.desktop[14229]: [10:15:29:144] [14229:14825] [ERROR][com.winpr.timezone] - Unable to get current timezone rule Feb 12 10:15:29 blade /usr/lib/gdm3/gdm-x-session[13413]: (EE) Feb 12 10:15:29 blade /usr/lib/gdm3/gdm-x-session[13413]: (EE) Backtrace: Feb 12 10:15:29 blade /usr/lib/gdm3/gdm-x-session[13413]: (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x13c) [0x55685152bd2c] Feb 12 10:15:29 blade /usr/lib/gdm3/gdm-x-session[13413]: (EE) 1: /lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x60) [0x7f482176559f] Feb 12 10:15:29 blade /usr/lib/gdm3/gdm-x-session[13413]: (EE) 2: /usr/lib/xorg/Xorg (RamDacHandleColormaps+0x317) [0x55685144a347] Feb 12 10:15:29 blade /usr/lib/gdm3/gdm-x-session[13413]: (EE) 3: /usr/lib/xorg/Xorg (AddTraps+0x5ab5) [0x5568514a90d5] Feb 12 10:15:29 blade /usr/lib/gdm3/gdm-x-session[13413]: (EE) 4: /usr/lib/xorg/Xorg (ResizeVisualArray+0x25d) [0x5568513be1dd] Feb 12 10:15:29 blade /usr/lib/gdm3/gdm-x-session[13413]: (EE) 5: /usr/lib/xorg/Xorg (AllocARGBCursor+0x198) [0x5568513be478] Feb 12 10:15:29 blade /usr/lib/gdm3/gdm-x-session[13413]: (EE) 6: /usr/lib/xorg/Xorg (AddTraps+0x2303) [0x5568514a1d23] Feb 12 10:15:29 blade /usr/lib/gdm3/gdm-x-session[13413]: (EE) 7: /usr/lib/xorg/Xorg (SendErrorToClient+0x354) [0x5568513caf44] Feb 12 10:15:29 blade /usr/lib/gdm3/gdm-x-session[13413]: (EE) 8: /usr/lib/xorg/Xorg (InitFonts+0x3b4) [0x5568513cefd4] Feb 12 10:15:29 blade /usr/lib/gdm3/gdm-x-session[13413]: (EE) 9: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf3) [0x7f48215841e3] Feb 12 10:15:29 blade /usr/lib/gdm3/gdm-x-session[13413]: (EE) 10: /usr/lib/xorg/Xorg (_start+0x2e) [0x5568513b8a3e] Feb 12 10:15:29 blade /usr/lib/gdm3/gdm-x-session[13413]: (EE) Feb 12 10:15:29 blade /usr/lib/gdm3/gdm-x-session[13413]: (EE) Segmentation fault at address 0x0 Feb 12 10:15:29 blade /usr/lib/gdm3/gdm-x-session[13413]: (EE) Feb 12 10:15:29 blade /usr/lib/gdm3/gdm-x-session[13413]: Fatal server error: Feb 12 10:15:29 blade /usr/lib/gdm3/gdm-x-session[13413]: (EE) Caught signal 11 (Segmentation fault). Server aborting Feb 12 10:15:29 blade /usr/lib/gdm3/gdm-x-session[13413]: (EE) Feb 12 10:15:29 blade /usr/lib/gdm3/gdm-x-session[13413]: (EE) Feb 12 10:15:29 blade /usr/lib/gdm3/gdm-x-session[13413]: Please consult the The X.Org Foundation support Feb 12 10:15:29 blade /usr/lib/gdm3/gdm-x-session[13413]: #011 at http://wiki.x.org Feb 12 10:15:29 blade /usr/lib/gdm3/gdm-x-session[13413]: for help. Feb 12 10:15:29 blade /usr/lib/gdm3/gdm-x-session[13413]: (EE) Please also check the log file at "/home/dima/.local/share/xorg/Xorg.1.log" for additional information. Feb 12 10:15:29 blade /usr/lib/gdm3/gdm-x-session[13413]: (EE) Feb 12 10:15:30 blade /usr/lib/gdm3/gdm-x-session[13413]: (EE) Server terminated with error (1). Closing log file. Feb 12 10:15:30 blade remmina[14229]: org.remmina.Remmina: Fatal IO error 11 (Resource temporarily unavailable) on X server :1. Feb 12 10:15:30 blade gnome-calendar[14118]: gnome-calendar: Fatal IO error 11 (Resource temporarily unavailable) on X server :1. virt-viewer: Feb 12 10:02:09 blade systemd[4463]: Started /usr/bin/virt-viewer -c qemu:///system. Feb 12 10:02:09 blade systemd[1]: Starting Daily apt download activities... Feb 12 10:02:10 blade systemd-resolved[1782]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP. Feb 12 10:02:10 blade systemd-resolved[1782]: message repeated 3 times: [ Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP.] Feb 12 10:02:11 blade apt-get: Libgcrypt warning: missing initializati
[Desktop-packages] [Bug 1838151] Re: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support.
Just checked again and it seems neither upstream Linux nor upstream PulseAudio have landed this yet. Perhaps they don't know about it or have lost track of the patches. To get the ball rolling, anyone affected please open new upstream bugs in both: Linux: https://bugzilla.kernel.org/ PulseAudio: https://gitlab.freedesktop.org/groups/pulseaudio/-/issues and then tell us the new bug IDs. If the Ubuntu kernel team is listening then maybe they can help with this. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1838151 Title: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support. Status in linux package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Triaged Status in Arch Linux: New Bug description: Bluetooth HSP/HFP audio quality is poor on Ubuntu comparative to all other major platforms (Windows, MacOS, ChromeOS, Android, iOS). Modern Bluetooth headsets (such as the Bose QC series headphones, many others) are capable of using HFP 1.6 with mSBC 16kHz audio encoding. As it currently stands, Ubuntu defaults to only supporting HSP headsets using 8kHz CVSD, and is incapable of supporting HFP 1.6 at this time. The ChromiumOS team recently tackled this issue - https://bugs.chromium.org/p/chromium/issues/detail?id=843048 Their efforts may assist in bringing this to Ubuntu, however it appears that there are quite a lot of differences considering they have developed their own audio server solution etc. The Bluetooth Telephony Working Group published the HFP 1.6 spec in May 2011 - https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=238193 Patches have been proposed in the past for this issue to the kernel and PulseAudio: PulseAudio: https://patchwork.freedesktop.org/patch/245272/ Kernel: https://www.spinics.net/lists/linux-bluetooth/msg76982.html It appears that the Chromium OS team applied the same kernel patch: https://chromium.googlesource.com/chromiumos/third_party/kernel/+/77dd0cb94c1713a8a12f6e392955dfa64c430e54 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jnappi 2777 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Jul 27 11:08:29 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2017-11-04 (629 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: Upgraded to disco on 2019-07-18 (9 days ago) dmi.bios.date: 06/07/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R07ET67W (2.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FW000TUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR07ET67W(2.07):bd06/07/2016:svnLENOVO:pn20FW000TUS:pvrThinkPadT460p:rvnLENOVO:rn20FW000TUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460p dmi.product.name: 20FW000TUS dmi.product.sku: LENOVO_MT_20FW_BU_Think_FM_ThinkPad T460p dmi.product.version: ThinkPad T460p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838151/+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 1859260] Re: Cant go back to primary monitor when app indicator menu is open
** Bug watch added: github.com/micheleg/dash-to-dock/issues #743 https://github.com/micheleg/dash-to-dock/issues/743 ** Also affects: dash-to-dock via https://github.com/micheleg/dash-to-dock/issues/743 Importance: Unknown Status: Unknown ** Package changed: gnome-shell (Ubuntu) => gnome-shell-extension- dashtodock (Ubuntu) -- 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/1859260 Title: Cant go back to primary monitor when app indicator menu is open Status in Dash to dock: Unknown Status in GNOME Shell: New Status in gnome-shell-extension-dashtodock package in Ubuntu: Triaged Bug description: This bugs happens if you: 1. Open app indicator menu (top right); 2. Move your cursor to the right monitor; Now you can't go back. The only way is pressing ESC to close app indicator menu so that you can go back to the first monitor. This only happens when ubuntu-dock autohide is on. Maybe it can be useful: https://github.com/micheleg/dash-to- dock/issues/743 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell-extension-ubuntu-dock 67ubuntu19.10.1 ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3 Uname: Linux 5.4.0-9-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Jan 11 00:01:41 2020 InstallationDate: Installed on 2019-12-31 (11 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191230) 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/dash-to-dock/+bug/1859260/+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 1863184] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1863184/+attachment/5328091/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1863184 Title: Application does not stay open on Ubuntu 20.04 and closes automatically Status in totem package in Ubuntu: New Bug description: Hello Ubuntu Team When we click on the totem it opens and closes automatically, as seen in the gif image on the link below. [img]https://i.imgur.com/TYA8hrg.mp4[/img] I tried to report this error by ubuntu-bug -w, but an error message appears that can be seen in the gif image below. [img]https://i.imgur.com/xm9QSb9.mp4[/img] --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-04-28 (291 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Package: totem 3.34.1-2ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Tags: focal Uname: Linux 5.4.0-12-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-02-04 (9 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo XorgLog: Error: [Errno 2] Arquivo ou diretório inexistente: '/var/log/Xorg.0.log' _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1863184/+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 1863184] GstreamerVersions.txt
apport information ** Attachment added: "GstreamerVersions.txt" https://bugs.launchpad.net/bugs/1863184/+attachment/5328089/+files/GstreamerVersions.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1863184 Title: Application does not stay open on Ubuntu 20.04 and closes automatically Status in totem package in Ubuntu: New Bug description: Hello Ubuntu Team When we click on the totem it opens and closes automatically, as seen in the gif image on the link below. [img]https://i.imgur.com/TYA8hrg.mp4[/img] I tried to report this error by ubuntu-bug -w, but an error message appears that can be seen in the gif image below. [img]https://i.imgur.com/xm9QSb9.mp4[/img] --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-04-28 (291 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Package: totem 3.34.1-2ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Tags: focal Uname: Linux 5.4.0-12-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-02-04 (9 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo XorgLog: Error: [Errno 2] Arquivo ou diretório inexistente: '/var/log/Xorg.0.log' _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1863184/+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 1863184] LogAlsaMixer.txt
apport information ** Attachment added: "LogAlsaMixer.txt" https://bugs.launchpad.net/bugs/1863184/+attachment/5328090/+files/LogAlsaMixer.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1863184 Title: Application does not stay open on Ubuntu 20.04 and closes automatically Status in totem package in Ubuntu: New Bug description: Hello Ubuntu Team When we click on the totem it opens and closes automatically, as seen in the gif image on the link below. [img]https://i.imgur.com/TYA8hrg.mp4[/img] I tried to report this error by ubuntu-bug -w, but an error message appears that can be seen in the gif image below. [img]https://i.imgur.com/xm9QSb9.mp4[/img] --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-04-28 (291 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Package: totem 3.34.1-2ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Tags: focal Uname: Linux 5.4.0-12-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-02-04 (9 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo XorgLog: Error: [Errno 2] Arquivo ou diretório inexistente: '/var/log/Xorg.0.log' _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1863184/+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 1863184] Re: Application does not stay open on Ubuntu 20.04 and closes automatically
apport information ** Tags added: apport-collected focal ** Description changed: Hello Ubuntu Team When we click on the totem it opens and closes automatically, as seen in the gif image on the link below. [img]https://i.imgur.com/TYA8hrg.mp4[/img] I tried to report this error by ubuntu-bug -w, but an error message appears that can be seen in the gif image below. [img]https://i.imgur.com/xm9QSb9.mp4[/img] + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu16 + Architecture: amd64 + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 20.04 + InstallationDate: Installed on 2019-04-28 (291 days ago) + InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) + Package: totem 3.34.1-2ubuntu1 + PackageArchitecture: amd64 + ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 + Tags: focal + Uname: Linux 5.4.0-12-generic x86_64 + UpgradeStatus: Upgraded to focal on 2020-02-04 (9 days ago) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + XorgLog: Error: [Errno 2] Arquivo ou diretório inexistente: '/var/log/Xorg.0.log' + _MarkForUpload: True ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1863184/+attachment/5328088/+files/Dependencies.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1863184 Title: Application does not stay open on Ubuntu 20.04 and closes automatically Status in totem package in Ubuntu: New Bug description: Hello Ubuntu Team When we click on the totem it opens and closes automatically, as seen in the gif image on the link below. [img]https://i.imgur.com/TYA8hrg.mp4[/img] I tried to report this error by ubuntu-bug -w, but an error message appears that can be seen in the gif image below. [img]https://i.imgur.com/xm9QSb9.mp4[/img] --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-04-28 (291 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Package: totem 3.34.1-2ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Tags: focal Uname: Linux 5.4.0-12-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-02-04 (9 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo XorgLog: Error: [Errno 2] Arquivo ou diretório inexistente: '/var/log/Xorg.0.log' _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1863184/+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 1863184] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1863184/+attachment/5328092/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1863184 Title: Application does not stay open on Ubuntu 20.04 and closes automatically Status in totem package in Ubuntu: New Bug description: Hello Ubuntu Team When we click on the totem it opens and closes automatically, as seen in the gif image on the link below. [img]https://i.imgur.com/TYA8hrg.mp4[/img] I tried to report this error by ubuntu-bug -w, but an error message appears that can be seen in the gif image below. [img]https://i.imgur.com/xm9QSb9.mp4[/img] --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-04-28 (291 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Package: totem 3.34.1-2ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Tags: focal Uname: Linux 5.4.0-12-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-02-04 (9 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo XorgLog: Error: [Errno 2] Arquivo ou diretório inexistente: '/var/log/Xorg.0.log' _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1863184/+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 1863188] [NEW] Touchpad controls are not shown in System Settings
Public bug reported: The touchpad of this laptop is working fine from the beginning, however the System Settings application at "Mouse & Touchpad" will show only very basic mouse configuration options: Primary button left/right Double-Click speed I can not set the options about two-finger scrolling, tapping, edge, nor even pointer speed. This seems to be a unity-control-center bug because the Gnome Settings app does show the touchpad controls. OS: Ubuntu 19.10 (standard version) with Unity desktop added after installation Here is some info about the device: Notebook: Asus X571 /proc/bus/input/devices N: Name="ELAN1200:00 04F3:3104 Touchpad" P: Phys=i2c-ELAN1200:00 S: Sysfs=/devices/pci:00/:00:15.0/i2c_designware.0/i2c-1/i2c-ELAN1200:00/0018:04F3:3104.0001/input/input11 xinput list ⎡ Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointerid=4[slave pointer (2)] ⎜ ↳ ELAN1200:00 04F3:3104 Touchpadid=11 [slave pointer (2)] xinput list-props 11 Device 'ELAN1200:00 04F3:3104 Touchpad': Device Enabled (198): 1 Coordinate Transformation Matrix (200): 1.00, 0.00, 0.00, 0.00, 1.00, 0.00, 0.00, 0.00, 1.00 libinput Tapping Enabled (335): 0 libinput Tapping Enabled Default (336): 0 libinput Tapping Drag Enabled (337):1 libinput Tapping Drag Enabled Default (338):1 libinput Tapping Drag Lock Enabled (339): 0 libinput Tapping Drag Lock Enabled Default (340): 0 libinput Tapping Button Mapping Enabled (341): 1, 0 libinput Tapping Button Mapping Default (342): 1, 0 libinput Natural Scrolling Enabled (343): 0 libinput Natural Scrolling Enabled Default (344): 0 libinput Disable While Typing Enabled (345):1 libinput Disable While Typing Enabled Default (346):1 libinput Scroll Methods Available (347):1, 1, 0 libinput Scroll Method Enabled (348): 1, 0, 0 libinput Scroll Method Enabled Default (349): 1, 0, 0 libinput Click Methods Available (350): 1, 1 libinput Click Method Enabled (351):1, 0 libinput Click Method Enabled Default (352):1, 0 libinput Middle Emulation Enabled (353):0 libinput Middle Emulation Enabled Default (354):0 libinput Accel Speed (355): 0.00 libinput Accel Speed Default (356): 0.00 libinput Left Handed Enabled (357): 0 libinput Left Handed Enabled Default (358): 0 libinput Send Events Modes Available (320): 1, 1 libinput Send Events Mode Enabled (321):0, 0 libinput Send Events Mode Enabled Default (322):0, 0 Device Node (323): "/dev/input/event8" Device Product ID (324):1267, 12548 libinput Drag Lock Buttons (359): libinput Horizontal Scroll Enabled (360): 1 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: unity-control-center 15.04.0+19.10.20190921-0ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13 Uname: Linux 5.3.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu Date: Fri Feb 14 01:11:48 2020 EcryptfsInUse: Yes InstallationDate: Installed on 2020-01-20 (25 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: unity-control-center UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: unity-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1863188 Title: Touchpad controls are not shown in System Settings Status in unity-control-center package in Ubuntu: New Bug description: The touchpad of this laptop is working fine from the beginning, however the System Settings application at "Mouse & Touchpad" will show only very basic mouse configuration options: Primary button left/right Double-Click speed I can not set the options about two-finger scrolling, tapping, edge, nor even pointer speed. This seems to be a unity-control-center bug because the Gnome Settings app does show the touchpad controls. OS: Ubuntu 19.10 (standard version) with Unity desktop added after installation Here is some info about the device: Notebook: Asus X571 /proc/bus/input/devices N: Name="ELAN1200:00 04F3:3104 Touchpad" P: Phys=i2c-ELAN1200:00 S: Sysfs=/devices/pci:00/:00:15.0/i2c_designware.0/i2c-1/i2c-ELAN1200:00/0018:04F3:3104.0001/input/input11 xinput list ⎡ Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointerid=4[slave pointer (2)] ⎜ ↳ ELAN1200:00 04F3:3104 Touchpadid=11 [slave pointer (2)] xinput list-props 11 Device
[Desktop-packages] [Bug 1863187] Re: Samsung ATIV Smart PC Pro 700T XE700T1C Keyboard Dock touchpad detected as a pointer mouse.
** Attachment added: "xorg log" https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-libinput/+bug/1863187/+attachment/5328079/+files/Xorg.0.log -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-libinput in Ubuntu. https://bugs.launchpad.net/bugs/1863187 Title: Samsung ATIV Smart PC Pro 700T XE700T1C Keyboard Dock touchpad detected as a pointer mouse. Status in xserver-xorg-input-libinput package in Ubuntu: New Bug description: After a fresh install of lubuntu 19.10, touchpad on keyboard dock for the Samsung ATIV Smart PC Pro 700T XE700T1C-A04US is not detected as a touchpad. Under windows, synaptics drivers were used for touchpad functionality. Albeit this computer is about 7 years old. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-libinput/+bug/1863187/+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 1863187] Re: Samsung ATIV Smart PC Pro 700T XE700T1C Keyboard Dock touchpad detected as a pointer mouse.
** Attachment added: "xinput" https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-libinput/+bug/1863187/+attachment/5328078/+files/xinput.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-libinput in Ubuntu. https://bugs.launchpad.net/bugs/1863187 Title: Samsung ATIV Smart PC Pro 700T XE700T1C Keyboard Dock touchpad detected as a pointer mouse. Status in xserver-xorg-input-libinput package in Ubuntu: New Bug description: After a fresh install of lubuntu 19.10, touchpad on keyboard dock for the Samsung ATIV Smart PC Pro 700T XE700T1C-A04US is not detected as a touchpad. Under windows, synaptics drivers were used for touchpad functionality. Albeit this computer is about 7 years old. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-libinput/+bug/1863187/+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 1863187] [NEW] Samsung ATIV Smart PC Pro 700T XE700T1C Keyboard Dock touchpad detected as a pointer mouse.
Public bug reported: After a fresh install of lubuntu 19.10, touchpad on keyboard dock for the Samsung ATIV Smart PC Pro 700T XE700T1C-A04US is not detected as a touchpad. Under windows, synaptics drivers were used for touchpad functionality. Albeit this computer is about 7 years old. ** Affects: xserver-xorg-input-libinput (Ubuntu) Importance: Undecided Status: New ** Tags: libinput mouse touchpad ** Attachment added: "proc input devices" https://bugs.launchpad.net/bugs/1863187/+attachment/5328077/+files/devices.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-libinput in Ubuntu. https://bugs.launchpad.net/bugs/1863187 Title: Samsung ATIV Smart PC Pro 700T XE700T1C Keyboard Dock touchpad detected as a pointer mouse. Status in xserver-xorg-input-libinput package in Ubuntu: New Bug description: After a fresh install of lubuntu 19.10, touchpad on keyboard dock for the Samsung ATIV Smart PC Pro 700T XE700T1C-A04US is not detected as a touchpad. Under windows, synaptics drivers were used for touchpad functionality. Albeit this computer is about 7 years old. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-libinput/+bug/1863187/+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 1863184] Re: Application does not stay open on Ubuntu 20.04 and closes automatically
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal: apport-collect 1863184 When reporting bugs in the future please use apport by using 'ubuntu- bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs. FYI: rather than `ubuntu-bug -w` a `ubuntu-bug totem` may have worked. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1863184 Title: Application does not stay open on Ubuntu 20.04 and closes automatically Status in totem package in Ubuntu: New Bug description: Hello Ubuntu Team When we click on the totem it opens and closes automatically, as seen in the gif image on the link below. [img]https://i.imgur.com/TYA8hrg.mp4[/img] I tried to report this error by ubuntu-bug -w, but an error message appears that can be seen in the gif image below. [img]https://i.imgur.com/xm9QSb9.mp4[/img] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1863184/+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 1860793] Re: [amdgpu] Severe freezes that begin with minor stutters
You mean I should try an older version? Then I think I should try v5.0.x first. As you can see, it takes time to reproduce it again. I don't know how to intentionally reproduce it. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-amdgpu in Ubuntu. https://bugs.launchpad.net/bugs/1860793 Title: [amdgpu] Severe freezes that begin with minor stutters Status in linux package in Ubuntu: Incomplete Status in xserver-xorg-video-amdgpu package in Ubuntu: Incomplete Bug description: It starts with very subtle stuttering that you notice when moving windows around, then keeps getting worse and worse until it starts freezing the UI for many seconds. I could only reproduce it twice in a couple of days. The applications open at the time are usually Atom, Firefox, Hexchat, GNOME Files and occasionally Eye of GNOME. I checked resource consumption at the time of the stutters. Memory consumption was about 50% of 8GB, while the swap partition was nearly full (after a long gaming session). Storage device is a SATA SSD. During the stutters and freezes, CPU usage is normal. Through the process list of System Monitor I cannot see any application overusing resources. Temperatures are also normal. One potentially problematic hardware device is the GPU: AMD RX 560 4GB (open source AMDGPU). Its temperature and fan speed were also normal at the time. I know my system is capable of handling this workload. Also, this is only reproducible on Ubuntu 19.10 Eoan with GNOME. The LTS version of Ubuntu (18.04.3) is unaffected. I have used it for months before switching to the latest non-LTS version. What I've tried to stop the freezes: - Closed all running applications and waited. It didn't improve the situation, so I restarted my user session. The freezes continued, so I performed a system reboot, which finally helped normalize things. I did not try to reproduce this on the Wayland session. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.1+git20191024-1ubuntu1~19.10.1 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 Uname: Linux 5.3.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Jan 24 11:13:56 2020 DisplayManager: gdm3 InstallationDate: Installed on 2019-12-27 (28 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) RelatedPackageVersions: mutter-common 3.34.3-1ubuntu1~19.10.1 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/linux/+bug/1860793/+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 1862549] Re: memory leak when annotating PDFs
The profiler shows that while scrolling through the annotated sample PDF, evince 3.34.1 on Focal spends about 45% of its CPU time in libhunspell-1.7.so.0.0.1, which is not the case for 3.28.4 on Bionic. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1862549 Title: memory leak when annotating PDFs Status in evince package in Ubuntu: Confirmed Bug description: When annotating PDFs or scrolling through larger PDFs that contain lots of annotations, evince claims a large amount of memory and never releases it. This becomes especially apparent when using the highlight feature, i.e. highlighting various parts of the text on the PDF. On a 12-page PDF, not annotated, evince used about 35 MB of RAM and claimed an additional 30 as soon as I used the highlight feature the first time, then this repeats with about the same amount or more for each additional highlight. The interface starts to lag visibly the more memory is allocated. Occasionally, the memory usage goes down by a few percent when scrolling, but it tends to allocate more and more memory until the system runs out of memory. Using the same 12-page PDF with about 100 highlighted lines and quickly scrolling through the document multiple times, evince reached about 6 GB of memory usage in less than one minute. This issue also makes closing documents very slow, taking about 5 to 10 seconds for each gigabyte of memory allocated. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: evince 3.34.1-1build1 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Feb 9 23:13:02 2020 InstallationDate: Installed on 2020-01-30 (10 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200124) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/zsh SourcePackage: evince UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1862549/+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 1863184] [NEW] Application does not stay open on Ubuntu 20.04 and closes automatically
Public bug reported: Hello Ubuntu Team When we click on the totem it opens and closes automatically, as seen in the gif image on the link below. [img]https://i.imgur.com/TYA8hrg.mp4[/img] I tried to report this error by ubuntu-bug -w, but an error message appears that can be seen in the gif image below. [img]https://i.imgur.com/xm9QSb9.mp4[/img] ** Affects: totem (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1863184 Title: Application does not stay open on Ubuntu 20.04 and closes automatically Status in totem package in Ubuntu: New Bug description: Hello Ubuntu Team When we click on the totem it opens and closes automatically, as seen in the gif image on the link below. [img]https://i.imgur.com/TYA8hrg.mp4[/img] I tried to report this error by ubuntu-bug -w, but an error message appears that can be seen in the gif image below. [img]https://i.imgur.com/xm9QSb9.mp4[/img] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1863184/+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 1859926] Re: fonts-noto-color-emoji not making pretty emojis in google chrome
I have the same issue, even on a fresh install. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fonts-noto-color-emoji in Ubuntu. https://bugs.launchpad.net/bugs/1859926 Title: fonts-noto-color-emoji not making pretty emojis in google chrome Status in fonts-noto-color-emoji package in Ubuntu: Confirmed Bug description: Google-Chrome and emoji's is being a weird headache. Something's causing it not to find the right font to make emoji's: "[13743:1:0115/225907.016533:ERROR:child_process_sandbox_support_impl_linux.cc(79)] FontService unique font name matching request did not receive a response. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fonts-noto-color-emoji/+bug/1859926/+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 1853638] Re: BCM57416 NetXtreme-E Dual-Media 10G RDMA Ethernet device seems to be dropping data
I have tried, unsuccessfully, to reproduce this issue internally. Details of my setup below. 1) I have a pair of Dell R210 servers racked (u072 and u073 below), each with a BCM57416 installed: root@u072:~# lspci | grep BCM57416 01:00.0 Ethernet controller: Broadcom Inc. and subsidiaries BCM57416 NetXtreme-E Dual-Media 10G RDMA Ethernet Controller (rev 01) 01:00.1 Ethernet controller: Broadcom Inc. and subsidiaries BCM57416 NetXtreme-E Dual-Media 10G RDMA Ethernet Controller (rev 01) 2) I've matched the firmware version to one that Nivedita reported in a bad system: root@u072:~# ethtool -i enp1s0f0np0 driver: bnxt_en version: 1.10.0 firmware-version: 214.0.253.1/pkg 21.40.25.31 expansion-rom-version: bus-info: :01:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: no supports-priv-flags: no 3) Matched Ubuntu release and kernel version: root@u072:~# lsb_release -dr Description:Ubuntu 18.04.3 LTS Release:18.04 root@u072:~# uname -a Linux u072 5.0.0-37-generic #40~18.04.1-Ubuntu SMP Thu Nov 14 12:06:39 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux 4) Configured the interface into an active-backup bond: root@u072:~# cat /proc/net/bonding/bond0 Ethernet Channel Bonding Driver: v3.7.1 (April 27, 2011) Bonding Mode: fault-tolerance (active-backup) Primary Slave: None Currently Active Slave: enp1s0f1np1 MII Status: up MII Polling Interval (ms): 100 Up Delay (ms): 0 Down Delay (ms): 0 Slave Interface: enp1s0f1np1 MII Status: up Speed: 1 Mbps Duplex: full Link Failure Count: 1 Permanent HW addr: 00:0a:f7:a7:10:61 Slave queue ID: 0 Slave Interface: enp1s0f0np0 MII Status: up Speed: 1 Mbps Duplex: full Link Failure Count: 1 Permanent HW addr: 00:0a:f7:a7:10:60 Slave queue ID: 0 5) Run the provided mtr and netperf test cases with the 1st port selected as active: root@u072:~# ip l set enp1s0f1np1 down root@u072:~# ip l set enp1s0f1np1 up root@u072:~# cat /proc/net/bonding/bond0 | grep Active Currently Active Slave: enp1s0f0np0 a) initiated on u072: root@u072:~# mtr --no-dns --report --report-cycles 60 192.168.1.2 Start: 2020-02-13T20:48:01+ HOST: u072Loss% Snt Last Avg Best Wrst StDev 1.|-- 192.168.1.20.0%600.2 0.2 0.2 0.2 0.0 root@u072:~# netperf -t TCP_RR -H 192.168.1.2 -- -r 1,1 MIGRATED TCP REQUEST/RESPONSE TEST from 0.0.0.0 (0.0.0.0) port 0 AF_INET to 192.168.1.2 () port 0 AF_INET : demo : first burst 0 Local /Remote Socket Size Request Resp. Elapsed Trans. Send Recv Size SizeTime Rate bytes Bytes bytesbytes secs.per sec 16384 131072 11 10.0029040.91 16384 87380 root@u072:~# netperf -t TCP_RR -H 192.168.1.2 -- -r 64,64 MIGRATED TCP REQUEST/RESPONSE TEST from 0.0.0.0 (0.0.0.0) port 0 AF_INET to 192.168.1.2 () port 0 AF_INET : demo : first burst 0 Local /Remote Socket Size Request Resp. Elapsed Trans. Send Recv Size SizeTime Rate bytes Bytes bytesbytes secs.per sec 16384 131072 64 64 10.0028633.36 16384 87380 root@u072:~# netperf -t TCP_RR -H 192.168.1.2 -- -r 128,8192 MIGRATED TCP REQUEST/RESPONSE TEST from 0.0.0.0 (0.0.0.0) port 0 AF_INET to 192.168.1.2 () port 0 AF_INET : demo : first burst 0 Local /Remote Socket Size Request Resp. Elapsed Trans. Send Recv Size SizeTime Rate bytes Bytes bytesbytes secs.per sec 16384 131072 128 819210.0017469.30 16384 87380 b) initiated on u073: root@u073:~# mtr --no-dns --report --report-cycles 60 192.168.1.1 Start: 2020-02-13T20:53:37+ HOST: u073Loss% Snt Last Avg Best Wrst StDev 1.|-- 192.168.1.10.0%600.1 0.1 0.1 0.2 0.0 root@u073:~# netperf -t TCP_RR -H 192.168.1.1 -- -r 1,1 MIGRATED TCP REQUEST/RESPONSE TEST from 0.0.0.0 (0.0.0.0) port 0 AF_INET to 192.168.1.1 () port 0 AF_INET : demo : first burst 0 Local /Remote Socket Size Request Resp. Elapsed Trans. Send Recv Size SizeTime Rate bytes Bytes bytesbytes secs.per sec 16384 87380 11 10.0028514.93 16384 131072 root@u073:~# netperf -t TCP_RR -H 192.168.1.1 -- -r 64,64 MIGRATED TCP REQUEST/RESPONSE TEST from 0.0.0.0 (0.0.0.0) port 0 AF_INET to 192.168.1.1 () port 0 AF_INET : demo : first burst 0 Local /Remote Socket Size Request Resp. Elapsed Trans. Send Recv Size SizeTime Rate bytes Bytes bytesbytes secs.per sec 16384 87380 64 64 10.0027405.88 16384 131072 root@u073:~# netperf -t TCP_RR -H 192.168.1.1 -- -r 128,8192 MIGRATED TCP REQUEST/RESPONSE TEST from 0.0.0.0 (0.0.0.0) port 0 AF_INET to 192.168.1.1 () port 0 AF_INET : demo : first burst 0 Local /Remote Socket Size Request Resp. Elapsed Trans. Send Recv Size SizeTime Rate b
[Desktop-packages] [Bug 1839555] Re: X server backports for PRIME render offloading
adding the -hwe package here just to make it clear that it's actually in
18.04 now, so I won't forget :)
** Also affects: xorg-server-hwe-18.04 (Ubuntu)
Importance: Undecided
Status: New
** Changed in: xorg-server-hwe-18.04 (Ubuntu)
Status: New => Fix Released
--
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/1839555
Title:
X server backports for PRIME render offloading
Status in xorg-server package in Ubuntu:
Fix Released
Status in xorg-server-hwe-18.04 package in Ubuntu:
Fix Released
Bug description:
Configuring PRIME render offloading requires changes to the X server
which have been accepted upstream but are not yet present in any
release. These changes do not break the driver ABI and should be safe
to backport to existing X servers shipped in distributions like
Ubuntu.
The required commits are:
* 7f962c70b6d9c346477f23f6c15211e749110078 - xsync: Add resource inside of
SyncCreate, export SyncCreate
* 37a36a6b5b887d5c5a17a6931ceba8ad5d1bb6d5 - GLX: Add a per-client vendor
mapping
* 8b67ec7cc6fda243480a5a8ca118b66242f3eb2c- GLX: Use the sending client for
looking up XID's
* 56c0a71fdd94a008e5d746261f70a713c4767f93 - GLX: Add a function to change a
clients vendor list
* b4231d69028adc8123801a7552b40a15ea928d1b - GLX: Set
GlxServerExports::{major,minor}Version
These commits must be backported to an X.org X server of at least
version 1.20, as this is the first version with support for server-
side GLVND.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1839555/+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 1863172] [NEW] After selecting unit conversion, number input box does not have focus.
Public bug reported: 1) Ubuntu 19.10 2) 3.34.1+git1.d34dc842 3) If I select "Advanced Mode", and then select "Mass"..."Grams" and then start typing numbers, the numbers should appear in the number input box. 4) The typed numbers do not appear in the number input box because unit conversion box still has focus. ** Affects: gnome-calculator (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-calculator in Ubuntu. https://bugs.launchpad.net/bugs/1863172 Title: After selecting unit conversion, number input box does not have focus. Status in gnome-calculator package in Ubuntu: New Bug description: 1) Ubuntu 19.10 2) 3.34.1+git1.d34dc842 3) If I select "Advanced Mode", and then select "Mass"..."Grams" and then start typing numbers, the numbers should appear in the number input box. 4) The typed numbers do not appear in the number input box because unit conversion box still has focus. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calculator/+bug/1863172/+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 1863175] [NEW] Fluid ounce(fl oz) conversion unit is missing.
Public bug reported: 1) Ubuntu 19.10 2) 3.34.1+git1.d34dc842 3) Ability to convert US Gallons(gal) to fluid ounces(fl oz) 4) There is no fluid ounces conversion unit option. ** Affects: gnome-calculator (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-calculator in Ubuntu. https://bugs.launchpad.net/bugs/1863175 Title: Fluid ounce(fl oz) conversion unit is missing. Status in gnome-calculator package in Ubuntu: New Bug description: 1) Ubuntu 19.10 2) 3.34.1+git1.d34dc842 3) Ability to convert US Gallons(gal) to fluid ounces(fl oz) 4) There is no fluid ounces conversion unit option. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calculator/+bug/1863175/+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 1862910] Re: gnome-shell leaking memory in interaction with appimagelauncher
I have managed to replicate it on another system, it was necessary to change the destination location away from the default in appimagelauncher for the problem to appear. I have updated the description above with detailed procedure for replicating. There is already an open issue against appimagelauncher which is most likely related. https://github.com/TheAssassin/AppImageLauncher/issues/294 ** Description changed: + Edited description: + To replicate the problem (on Ubuntu 19.10 running Ubuntu Gnome) + 1. Install AppImageLauncher from https://github.com/TheAssassin/AppImageLauncher/releases by downloading version 2.1.0 deb file (appimagelauncher_2.1.0-travis897.d1be7e7.bionic_amd64.deb) and install it. If necessary run + sudo apt install -f + to fix missing dependencies. + + 2. Run it and change the appimage destination location to + ~/apps/appimages. It is necessary to change it away from the default + setting in order for the problem to appear, though probably the actual + destination is not important). Ensure that Auto start auto-integration + daemon is selected. + + 3. Download an appimage (I downloaded Cura 4.4.1 from + https://github.com/Ultimaker/Cura/releases/tag/4.4.1) I don't know + whether any appimage would do, probably it would. In fact I don't know + whether this step and the next need to be done at all. + + 4. Open it with appimagelauncher (this can be done by double clicking it + in nautilus) and tell it to move it and run the application. Then close + the application. + + 5. It may be necessary to reboot at this point I don't know. + + 6. Logon using Ubuntu (Gnome) and watch the memory usage of gnome- + session. It may take a few minutes to get going but then the memory + used will start increasing at several MB/minute. + + There is an issue open against appimage launcher which is likely the + same problem. + https://github.com/TheAssassin/AppImageLauncher/issues/294 + + Original description: On one of my machines which has been upgraded over several years and is now running 19.10 just one of the configured users appears to be seeing a dramatic memory leak in gnome-shell, even when nothing is happening on the UI. Immediately after logging on, using the Ubuntu selection from the logon screen, gnome shell shows as using about 134MB. From there it climbs at about 300MB per hour and after a few hours the machine grinds to a crawl, not surprisingly. This happens even if the user logs on and then the machine is left completely alone. Logout and back in frees all the memory. A test user I have configured sees no such problem. I have uninstalled all extensions apart from the system ones, disabled all the system ones and reset all the gnome settings using dconf reset -f /org/gnome/ to no avail. Also I have removed ~/.local/share/gnome-shell and allowed it to recreate it. Also I have removed .compiz, .config/dconf/user, .gconf, .gnome, .gnome2. I can't see anything obvious in the log. It must be something in my settings that is triggering it as the other user does not see it, but I have run out of ideas on what to try. See also bug #1856516 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.1+git20191024-1ubuntu1~19.10.1 ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13 Uname: Linux 5.3.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Feb 12 08:54:21 2020 DisplayManager: gdm3 InstallationDate: Installed on 2014-10-21 (1939 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20141017) RelatedPackageVersions: mutter-common 3.34.1+git20191107-1ubuntu1~19.10.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to eoan on 2020-01-27 (15 days ago) ** Bug watch added: github.com/TheAssassin/AppImageLauncher/issues #294 https://github.com/TheAssassin/AppImageLauncher/issues/294 ** Description changed: Edited description: To replicate the problem (on Ubuntu 19.10 running Ubuntu Gnome) 1. Install AppImageLauncher from https://github.com/TheAssassin/AppImageLauncher/releases by downloading version 2.1.0 deb file (appimagelauncher_2.1.0-travis897.d1be7e7.bionic_amd64.deb) and install it. If necessary run sudo apt install -f to fix missing dependencies. 2. Run it and change the appimage destination location to ~/apps/appimages. It is necessary to change it away from the default setting in order for the problem to appear, though probably the actual destination is not important). Ensure that Auto start auto-integration daemon is selected. 3. Download an appimage (I downloaded Cura 4.4.1 from https://github.com/Ultimaker/Cura/releases/tag/4.4.1) I don't know whether any appimage would do, probably it would. In fact I don't know whether this step and the next need to be done at all. 4. Open it with appimagelauncher (this can be done by double clicking it in
[Desktop-packages] [Bug 1862910] Re: gnome-shell leaking memory in interaction with appimagelauncher
** Summary changed: - gnome-shell leaking memory + gnome-shell leaking memory in interaction with appimagelauncher -- 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/1862910 Title: gnome-shell leaking memory in interaction with appimagelauncher Status in gnome-shell package in Ubuntu: Incomplete Bug description: On one of my machines which has been upgraded over several years and is now running 19.10 just one of the configured users appears to be seeing a dramatic memory leak in gnome-shell, even when nothing is happening on the UI. Immediately after logging on, using the Ubuntu selection from the logon screen, gnome shell shows as using about 134MB. From there it climbs at about 300MB per hour and after a few hours the machine grinds to a crawl, not surprisingly. This happens even if the user logs on and then the machine is left completely alone. Logout and back in frees all the memory. A test user I have configured sees no such problem. I have uninstalled all extensions apart from the system ones, disabled all the system ones and reset all the gnome settings using dconf reset -f /org/gnome/ to no avail. Also I have removed ~/.local/share/gnome-shell and allowed it to recreate it. Also I have removed .compiz, .config/dconf/user, .gconf, .gnome, .gnome2. I can't see anything obvious in the log. It must be something in my settings that is triggering it as the other user does not see it, but I have run out of ideas on what to try. See also bug #1856516 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.1+git20191024-1ubuntu1~19.10.1 ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13 Uname: Linux 5.3.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Feb 12 08:54:21 2020 DisplayManager: gdm3 InstallationDate: Installed on 2014-10-21 (1939 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20141017) RelatedPackageVersions: mutter-common 3.34.1+git20191107-1ubuntu1~19.10.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to eoan on 2020-01-27 (15 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1862910/+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 1527837] Re: "Make Link" operation missing from context menu(Unity7, Xenial)
This option is missing from Nautilus 1:3.34.1-1ubuntu1. Ubuntu 19.10.
Add a "Create Link/Remove Link" to the right click menu. If a user
selects a file and then clicks "Create Link", a file dialog popup would
appear. A user could then select a destination for the link.
** Changed in: nautilus (Ubuntu)
Status: Fix Committed => Confirmed
** Summary changed:
- "Make Link" operation missing from context menu(Unity7, Xenial)
+ "Make Link" operation missing from context menu
--
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/1527837
Title:
"Make Link" operation missing from context menu
Status in Nautilus:
Fix Released
Status in nautilus package in Ubuntu:
Confirmed
Bug description:
In Nautilus 3.15.x create symbolic links ("make link") was removed
from the context menu (not sure why?). The alternate method with
middle-click/drag does not work with mouse-less device
(laptops/netbooks) and the other alternate method, which involves
mouse, keyboard and three fingers simultaneously, is very
inconvenient for normal users and has bugs.
And It doesn't look like upstream is keen to get back this option
very soon. For LTS, its a major regression and Ubuntu should patch it
until they do.
https://bugzilla.gnome.org/show_bug.cgi?id=745575
To manage notifications about this bug go to:
https://bugs.launchpad.net/nautilus/+bug/1527837/+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 1862945] Re: Change desktop - select color no longer possible
Also the help 'Change the wallpaper' does not reflect the setting -> background window -- 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/1862945 Title: Change desktop - select color no longer possible Status in gnome-control-center package in Ubuntu: New Bug description: Open control center - settings - set background - select a solid color is not possible also if stated in the help. Change the desktop and lock screen backgrounds You can change the image used for your backgrounds or set it to be a solid color. corrado@corrado-x5-ff-0104:~$ inxi -Fxx System:Host: corrado-x5-ff-0104 Kernel: 5.4.0-12-generic x86_64 bits: 64 compiler: gcc v: 9.2.1 Desktop: Gnome 3.34.3 wm: gnome-shell dm: GDM3 Distro: Ubuntu 20.04 LTS (Focal Fossa) Machine: Type: Desktop Mobo: ASRock model: H110M-G/M.2 serial: UEFI: American Megatrends v: P1.10 date: 05/11/2017 CPU: Topology: Dual Core model: Intel Core i3-7100 bits: 64 type: MT MCP arch: Kaby Lake rev: 9 L2 cache: 3072 KiB flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 31199 Speed: 800 MHz min/max: 800/3900 MHz Core speeds (MHz): 1: 800 2: 800 3: 800 4: 803 Graphics: Device-1: Intel HD Graphics 630 vendor: ASRock driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:5912 Display: x11 server: X.Org 1.20.7 driver: i915 compositor: gnome-shell resolution: 1920x1080~60Hz OpenGL: renderer: Mesa DRI Intel HD Graphics 630 (Kaby Lake GT2) v: 4.6 Mesa 19.3.3 compat-v: 3.0 direct render: Yes Audio: Device-1: Intel 100 Series/C230 Series Family HD Audio vendor: ASRock driver: snd_hda_intel v: kernel bus ID: 00:1f.3 chip ID: 8086:a170 Device-2: Logitech QuickCam Pro 9000 type: USB driver: snd-usb-audio,uvcvideo bus ID: 1-10:5 chip ID: 046d:0990 Sound Server: ALSA v: k5.4.0-12-generic Network: Device-1: Intel Ethernet I219-V vendor: ASRock driver: e1000e v: 3.2.6-k port: f040 bus ID: 00:1f.6 chip ID: 8086:15b8 IF: enp0s31f6 state: up speed: 100 Mbps duplex: full mac: 70:85:c2:44:7b:86 Drives:Local Storage: total: 2.05 TiB used: 12.48 GiB (0.6%) ID-1: /dev/nvme0n1 vendor: Kingston model: SKC2000M8250G size: 232.89 GiB speed: 31.6 Gb/s lanes: 4 serial: 50026B72823D1475 ID-2: /dev/sda vendor: Toshiba model: DT01ACA100 size: 931.51 GiB speed: 6.0 Gb/s serial: 37PYNGAFS ID-3: /dev/sdb vendor: Hitachi model: HDS721010CLA332 size: 931.51 GiB speed: 3.0 Gb/s serial: JP2940J80Z3D3V Partition: ID-1: / size: 31.25 GiB used: 12.48 GiB (39.9%) fs: ext4 dev: /dev/nvme0n1p5 ID-2: swap-1 size: 8.00 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/sda2 Sensors: System Temperatures: cpu: 27.0 C mobo: 29.5 C Fan Speeds (RPM): fan-1: 0 fan-2: 2343 fan-3: 0 fan-4: 2268 fan-5: 0 fan-6: 0 Voltages: 12v: N/A 5v: N/A 3.3v: 3.49 vbat: 3.15 Info: Processes: 219 Uptime: 24m Memory: 7.49 GiB used: 1.24 GiB (16.6%) Init: systemd v: 244 runlevel: 5 Compilers: gcc: 9.2.1 alt: 9 Shell: bash v: 5.0.11 running in: gnome-terminal inxi: 3.0.37 corrado@corrado-x5-ff-0104:~$ ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.35.90-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Feb 12 14:30:09 2020 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2020-01-04 (39 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200104) 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/1862945/+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 1859774] Re: Full screen window becomes "small" in the upper left of the screen...
This is still happening, so I decided to see if using wayland would help, but it is the same. Here I'm enclosing an interesting screen shot (partial screen only) showing that when you hit f5 in libreoffice presenter, it thinks the screen is the upper left part of the screen. I thought this might be a hint, because, you could look at what routines libreoffice was calling for the slide show, and it might give a hint as to where the problem lies. Rob ** Attachment added: "gnome_bug_2020-02-14_05-22.png" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1859774/+attachment/5328056/+files/gnome_bug_2020-02-14_05-22.png -- 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/1859774 Title: Full screen window becomes "small" in the upper left of the screen... Status in gnome-shell package in Ubuntu: New Bug description: This happens with a number of different programs, so I suspect it is a window manager bug. The best way to describe it is with a screen shot. The only responsive part of the screen is the small window in the upper left. You can hit the little maximize box and it goes back to full screen okay, but after a while it comes back to this. It can be annoying, because sometimes you can't quickly see what happened to the title bar. I'm using Ubuntu 19.10. This has been happening for about a week. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1859774/+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 1863158] [NEW] UTF-8 Encoding errors with Security patch in 2.9.4+dfsg1-6.1ubuntu1.3
Public bug reported: I'm using libxml2 via perl-bindings in XML::LibXML. After upgrading to 2.9.4+dfsg1-6.1ubuntu1.3 my perl-scripts threw many UTF-8 encoding errors, e.g. "Malformed UTF-8 character: \xb0 (unexpected continuation byte 0xb0, with no preceding start byte." Re-installing libxml2.so.2.9.4 from 2.9.4+dfsg1-6.1ubuntu1.2 and linking libxml2.so.2 to this file without changing anything else lead to error- free execution of the perl-scripts: All Unicode characters are ok. At present, I'm not able to reduce the error situation in such a way that a simple perl script can be given which reproduces this error - I'm working on this. I'm also not able to provide an error description using libxml2 directly, without perl. So, please be patient with me and this stumbling bug-report. My system is: Description:Ubuntu 18.04.4 LTS Release:18.04 ** Affects: libxml2 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libxml2 in Ubuntu. https://bugs.launchpad.net/bugs/1863158 Title: UTF-8 Encoding errors with Security patch in 2.9.4+dfsg1-6.1ubuntu1.3 Status in libxml2 package in Ubuntu: New Bug description: I'm using libxml2 via perl-bindings in XML::LibXML. After upgrading to 2.9.4+dfsg1-6.1ubuntu1.3 my perl-scripts threw many UTF-8 encoding errors, e.g. "Malformed UTF-8 character: \xb0 (unexpected continuation byte 0xb0, with no preceding start byte." Re-installing libxml2.so.2.9.4 from 2.9.4+dfsg1-6.1ubuntu1.2 and linking libxml2.so.2 to this file without changing anything else lead to error-free execution of the perl-scripts: All Unicode characters are ok. At present, I'm not able to reduce the error situation in such a way that a simple perl script can be given which reproduces this error - I'm working on this. I'm also not able to provide an error description using libxml2 directly, without perl. So, please be patient with me and this stumbling bug-report. My system is: Description:Ubuntu 18.04.4 LTS Release:18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxml2/+bug/1863158/+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 1863157] [NEW] Petition to bring back file name copy/paste functionality in GTK file chooser
Public bug reported: For a very long time, I've never/rarely needed to hand-type file paths/names - it is extremely slow, error-proning and requiring a lot more work (reading/clicking/moving cursors) to do this simple task. Instead, I use tabs in a terminal to navigate, pwd to print, and copy/paste to another file browser or window to use the full path. In many file browsers (like Thunar), I could also single click on the file, and directly paste it to the address bar and it directly gives the full file name. But this becomes increasingly difficult to do on the GTK file chooser rolled out sometimes ago. The file chooser window first removed the file path address bar, but at least there was a button I can click to show it to copy/paste. Then, even that button disappeared - after many frustrating hours, the only way to show the address bar is "Ctrl+L", after reading many similarly frustrated posts https://www.google.com/search?q=unable+to+type+path+dialog+ubuntu https://www.google.com/search?q=unable+to+type+path+dialog+site%3Aaskubuntu.com&oq=unable+to+type+path+dialog+site https://www.google.com/search?q=can+not+type+path+in+file+selector+linux+site:askubuntu.com >From the long lists of complains that one can find online (I could easily find more), I think this just prove that removing/hiding the address bar is very counter intuitive and should be reverted. I see where this came from - to mimic Mac OS, like most GNOME style/appearance was trying to achieve, and this setting maybe cleaner and easier to attract less experienced users, but for people use Linux for work day-in-and-day-out, this is highly annoying and counter productive. Here I would like to petition to revert the change and bring back the address bar in the file chooser dialog (which is shared among not just GNOME, but other GTK based desktops, such as xfce), or at least bring back the button option. ** Affects: gtk+3.0 (Ubuntu) Importance: Undecided Status: New ** Attachment added: "current file chooser" https://bugs.launchpad.net/bugs/1863157/+attachment/5328055/+files/Screenshot_2020-02-13_14-01-19.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1863157 Title: Petition to bring back file name copy/paste functionality in GTK file chooser Status in gtk+3.0 package in Ubuntu: New Bug description: For a very long time, I've never/rarely needed to hand-type file paths/names - it is extremely slow, error-proning and requiring a lot more work (reading/clicking/moving cursors) to do this simple task. Instead, I use tabs in a terminal to navigate, pwd to print, and copy/paste to another file browser or window to use the full path. In many file browsers (like Thunar), I could also single click on the file, and directly paste it to the address bar and it directly gives the full file name. But this becomes increasingly difficult to do on the GTK file chooser rolled out sometimes ago. The file chooser window first removed the file path address bar, but at least there was a button I can click to show it to copy/paste. Then, even that button disappeared - after many frustrating hours, the only way to show the address bar is "Ctrl+L", after reading many similarly frustrated posts https://www.google.com/search?q=unable+to+type+path+dialog+ubuntu https://www.google.com/search?q=unable+to+type+path+dialog+site%3Aaskubuntu.com&oq=unable+to+type+path+dialog+site https://www.google.com/search?q=can+not+type+path+in+file+selector+linux+site:askubuntu.com From the long lists of complains that one can find online (I could easily find more), I think this just prove that removing/hiding the address bar is very counter intuitive and should be reverted. I see where this came from - to mimic Mac OS, like most GNOME style/appearance was trying to achieve, and this setting maybe cleaner and easier to attract less experienced users, but for people use Linux for work day-in-and-day-out, this is highly annoying and counter productive. Here I would like to petition to revert the change and bring back the address bar in the file chooser dialog (which is shared among not just GNOME, but other GTK based desktops, such as xfce), or at least bring back the button option. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1863157/+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 1838151] Re: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support.
A pity that I have to look for an extra usb microphone while I spent $200+ on a fancy bluetooth headset to have conference calls on my laptop. Reproduced with 3 bluetooth headsets. Quality is so poor on hsp/hfp that it's unusable. Didn't understand why I couldn't make it work decently until I found this bug. Does anyone have a workaround, managed to hack his way out of this bug? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1838151 Title: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support. Status in linux package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Triaged Status in Arch Linux: New Bug description: Bluetooth HSP/HFP audio quality is poor on Ubuntu comparative to all other major platforms (Windows, MacOS, ChromeOS, Android, iOS). Modern Bluetooth headsets (such as the Bose QC series headphones, many others) are capable of using HFP 1.6 with mSBC 16kHz audio encoding. As it currently stands, Ubuntu defaults to only supporting HSP headsets using 8kHz CVSD, and is incapable of supporting HFP 1.6 at this time. The ChromiumOS team recently tackled this issue - https://bugs.chromium.org/p/chromium/issues/detail?id=843048 Their efforts may assist in bringing this to Ubuntu, however it appears that there are quite a lot of differences considering they have developed their own audio server solution etc. The Bluetooth Telephony Working Group published the HFP 1.6 spec in May 2011 - https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=238193 Patches have been proposed in the past for this issue to the kernel and PulseAudio: PulseAudio: https://patchwork.freedesktop.org/patch/245272/ Kernel: https://www.spinics.net/lists/linux-bluetooth/msg76982.html It appears that the Chromium OS team applied the same kernel patch: https://chromium.googlesource.com/chromiumos/third_party/kernel/+/77dd0cb94c1713a8a12f6e392955dfa64c430e54 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jnappi 2777 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Jul 27 11:08:29 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2017-11-04 (629 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: Upgraded to disco on 2019-07-18 (9 days ago) dmi.bios.date: 06/07/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R07ET67W (2.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FW000TUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR07ET67W(2.07):bd06/07/2016:svnLENOVO:pn20FW000TUS:pvrThinkPadT460p:rvnLENOVO:rn20FW000TUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460p dmi.product.name: 20FW000TUS dmi.product.sku: LENOVO_MT_20FW_BU_Think_FM_ThinkPad T460p dmi.product.version: ThinkPad T460p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838151/+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 1863151] [NEW] apparmor messages for libreoffice 1:6.0.7-0ubuntu0.18.04.10 etc
Public bug reported: i have reported 3 bugs for apparmor's libreoffice profile: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1862331 https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1863097 https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1863103 i am afraid i make too much bug reports, so i am going to write other reports here, if they appear. i have now seen this message: Feb 13 20:56:25 dinar-Lenovo-G580 kernel: [29200.067772] audit: type=1400 audit(1581616585.668:272): apparmor="ALLOWED" operation="open" profile="libreoffice-soffice" name="/home/dinar/.config/dconf/user" pid=14211 comm="soffice.bin" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 ** 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/1863151 Title: apparmor messages for libreoffice 1:6.0.7-0ubuntu0.18.04.10 etc Status in libreoffice package in Ubuntu: New Bug description: i have reported 3 bugs for apparmor's libreoffice profile: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1862331 https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1863097 https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1863103 i am afraid i make too much bug reports, so i am going to write other reports here, if they appear. i have now seen this message: Feb 13 20:56:25 dinar-Lenovo-G580 kernel: [29200.067772] audit: type=1400 audit(1581616585.668:272): apparmor="ALLOWED" operation="open" profile="libreoffice-soffice" name="/home/dinar/.config/dconf/user" pid=14211 comm="soffice.bin" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1863151/+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 1859970] Re: Screenshots from an area selection have tinted colour when running wayland
** Changed in: gnome-shell Status: New => 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/1859970 Title: Screenshots from an area selection have tinted colour when running wayland Status in GNOME Shell: Fix Released Status in gnome-shell package in Ubuntu: Triaged Status in mutter package in Ubuntu: Triaged Bug description: All my screenshots taken on 20.04 with wayland have an orange tint to them. This appears to be the overlay which you get when selecting an area. Full screen screenshots and window screenshots are unaffected, only area screenshots appear to have the problem. Steps to reproduce Login to a wayland session Hold down Shift and Press PrintScreen Select an area to screenshot Navigate to ~/Pictures Open the picture you just took Expected outcome Screenshot of area taken as it would have been on screen Actual outcome Screenshot is taken, but has an orange border and overlay. (see screenshot) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-screenshot 3.33.90-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3 Uname: Linux 5.4.0-9-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Jan 16 11:50:50 2020 InstallationDate: Installed on 2018-02-04 (710 days ago) InstallationMedia: neon userlts "Xenial" - Build amd64 LIVE Binary 20180202-11:07 SourcePackage: gnome-screenshot UpgradeStatus: Upgraded to focal on 2020-01-08 (7 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1859970/+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 1846188] Re: Tooltips in Nautilus 3.34's burger menu are out of place (in Wayland sessions only)
** Changed in: gtk Status: Fix Released => 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/1846188 Title: Tooltips in Nautilus 3.34's burger menu are out of place (in Wayland sessions only) Status in GTK+: New Status in gtk+3.0 package in Ubuntu: Fix Committed Status in nautilus package in Ubuntu: Invalid Bug description: Description: Ubuntu Eoan Ermine (development branch) Release: 19.10 In Nautilus, tooltips appear far to the left in the app menu. (Kazam and Peek were unable to record Nautilus) To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1846188/+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 1862895] Re: [focal][nvidia][gdm3] Xorg crashes when virt-viewer or remmina are used to connect to a windows10 VM
Hi Daniel, I submitted a new crash dump via `ubuntu-bug`: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1863142 I'm going to set the status for this one to "New" as I provided the info but maybe it should be duplicated to the new bug. ** Changed in: xorg-server (Ubuntu) Status: Incomplete => New ** Changed in: gdm3 (Ubuntu) Status: Incomplete => New -- 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/1862895 Title: [focal][nvidia][gdm3] Xorg crashes when virt-viewer or remmina are used to connect to a windows10 VM Status in gdm3 package in Ubuntu: New Status in xorg-server package in Ubuntu: New Bug description: I observed the following on Eoan as well with nvidia drivers older than 440. 1) a windows 10 VM running in a qemu-kvm VM: pc-q35-3.1 machine type, QXL + SPICE: 2) When a host is booted with `prime-select intel` observing guest video output works fine with both virt-viewer (over SPICE) and remmina (over RDP); 3) With `prime-select nvidia` Remmina: Feb 12 10:15:22 blade gnome-shell[13670]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x2a7 Feb 12 10:15:29 blade org.remmina.Remmina.desktop[14229]: [10:15:29:144] [14229:14825] [ERROR][com.winpr.timezone] - Unable to get current timezone rule Feb 12 10:15:29 blade /usr/lib/gdm3/gdm-x-session[13413]: (EE) Feb 12 10:15:29 blade /usr/lib/gdm3/gdm-x-session[13413]: (EE) Backtrace: Feb 12 10:15:29 blade /usr/lib/gdm3/gdm-x-session[13413]: (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x13c) [0x55685152bd2c] Feb 12 10:15:29 blade /usr/lib/gdm3/gdm-x-session[13413]: (EE) 1: /lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x60) [0x7f482176559f] Feb 12 10:15:29 blade /usr/lib/gdm3/gdm-x-session[13413]: (EE) 2: /usr/lib/xorg/Xorg (RamDacHandleColormaps+0x317) [0x55685144a347] Feb 12 10:15:29 blade /usr/lib/gdm3/gdm-x-session[13413]: (EE) 3: /usr/lib/xorg/Xorg (AddTraps+0x5ab5) [0x5568514a90d5] Feb 12 10:15:29 blade /usr/lib/gdm3/gdm-x-session[13413]: (EE) 4: /usr/lib/xorg/Xorg (ResizeVisualArray+0x25d) [0x5568513be1dd] Feb 12 10:15:29 blade /usr/lib/gdm3/gdm-x-session[13413]: (EE) 5: /usr/lib/xorg/Xorg (AllocARGBCursor+0x198) [0x5568513be478] Feb 12 10:15:29 blade /usr/lib/gdm3/gdm-x-session[13413]: (EE) 6: /usr/lib/xorg/Xorg (AddTraps+0x2303) [0x5568514a1d23] Feb 12 10:15:29 blade /usr/lib/gdm3/gdm-x-session[13413]: (EE) 7: /usr/lib/xorg/Xorg (SendErrorToClient+0x354) [0x5568513caf44] Feb 12 10:15:29 blade /usr/lib/gdm3/gdm-x-session[13413]: (EE) 8: /usr/lib/xorg/Xorg (InitFonts+0x3b4) [0x5568513cefd4] Feb 12 10:15:29 blade /usr/lib/gdm3/gdm-x-session[13413]: (EE) 9: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf3) [0x7f48215841e3] Feb 12 10:15:29 blade /usr/lib/gdm3/gdm-x-session[13413]: (EE) 10: /usr/lib/xorg/Xorg (_start+0x2e) [0x5568513b8a3e] Feb 12 10:15:29 blade /usr/lib/gdm3/gdm-x-session[13413]: (EE) Feb 12 10:15:29 blade /usr/lib/gdm3/gdm-x-session[13413]: (EE) Segmentation fault at address 0x0 Feb 12 10:15:29 blade /usr/lib/gdm3/gdm-x-session[13413]: (EE) Feb 12 10:15:29 blade /usr/lib/gdm3/gdm-x-session[13413]: Fatal server error: Feb 12 10:15:29 blade /usr/lib/gdm3/gdm-x-session[13413]: (EE) Caught signal 11 (Segmentation fault). Server aborting Feb 12 10:15:29 blade /usr/lib/gdm3/gdm-x-session[13413]: (EE) Feb 12 10:15:29 blade /usr/lib/gdm3/gdm-x-session[13413]: (EE) Feb 12 10:15:29 blade /usr/lib/gdm3/gdm-x-session[13413]: Please consult the The X.Org Foundation support Feb 12 10:15:29 blade /usr/lib/gdm3/gdm-x-session[13413]: #011 at http://wiki.x.org Feb 12 10:15:29 blade /usr/lib/gdm3/gdm-x-session[13413]: for help. Feb 12 10:15:29 blade /usr/lib/gdm3/gdm-x-session[13413]: (EE) Please also check the log file at "/home/dima/.local/share/xorg/Xorg.1.log" for additional information. Feb 12 10:15:29 blade /usr/lib/gdm3/gdm-x-session[13413]: (EE) Feb 12 10:15:30 blade /usr/lib/gdm3/gdm-x-session[13413]: (EE) Server terminated with error (1). Closing log file. Feb 12 10:15:30 blade remmina[14229]: org.remmina.Remmina: Fatal IO error 11 (Resource temporarily unavailable) on X server :1. Feb 12 10:15:30 blade gnome-calendar[14118]: gnome-calendar: Fatal IO error 11 (Resource temporarily unavailable) on X server :1. virt-viewer: Feb 12 10:02:09 blade systemd[4463]: Started /usr/bin/virt-viewer -c qemu:///system. Feb 12 10:02:09 blade systemd[1]: Starting Daily apt download activities... Feb 12 10:02:10 blade systemd-resolved[1782]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP. Feb 12 10:02:10 blade systemd-resolved[1782]: message repeated 3 times: [ Server returned erro
[Desktop-packages] [Bug 1861985] Re: Sync gexiv2 0.12.0-2 (main) from Debian unstable (main)
And now in the Ubuntu Focal archives (https://bugs.launchpad.net/ubuntu/+source/gexiv2/0.12.0-2) ** Changed in: gexiv2 (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gexiv2 in Ubuntu. https://bugs.launchpad.net/bugs/1861985 Title: Sync gexiv2 0.12.0-2 (main) from Debian unstable (main) Status in gexiv2 package in Ubuntu: Fix Released Bug description: Please sync gexiv2 0.12.0-2 (main) from Debian unstable (main) Explanation of the Ubuntu delta and why it can be dropped: * Use python2 instead of python in the autopkg test. Debian switched to use python3. Changelog entries since current focal version 0.10.9-1ubuntu1: gexiv2 (0.12.0-2) unstable; urgency=medium * Drop patch Use-exiv2-version-0.25.patch. Exiv2 version 0.27 is now in Debian unstable. Drop this patch so gexiv2 can build against it. (Closes: #942519, #950169) * Update Standards-Version to 4.5.0. No changes necessary. -- Jason Crain Sun, 02 Feb 2020 04:29:42 -0700 gexiv2 (0.12.0-1) unstable; urgency=medium * New upstream version 0.12.0 * Update d/copyright * Add gexiv2 mailing list to Upstream-Contact. * Update d/rules * Remove dbgsym migration code since migration is complete. * No longer need to specify meson build system since autotools build was removed. * Renamed enable-gtk-doc option to gtk_doc. * Update d/control * Bump debhelper level to 12. * Switch to the 'debhelper-compat' dependency style. Remove the d/compat file. * Update Standards-Version to 4.4.1 No changes necessary. * Add Rules-Requires-Root: no * Update symbols * Dynamically generate d/libgexiv2-2.symbols. Upstream removed the script which kept C++ symbols from being exported due to regressions on OpenBSD (https://gitlab.gnome.org/GNOME/gexiv2/issues/27). Mark all C++ symbols as optional since these aren't part of the API. * Use 'python3' instead of 'python' in autopkgtest. Thanks to Matthias Klose (Closes: #943447) * Install /usr/share/vala/vapi/gexiv2.deps. This file tells vala about dependencies. * Add patch Use-exiv2-version-0.25.patch. This modifies gexiv2 to use exiv2 version 0.25, the version currently in Debian unstable. Upstream is set to use exiv2 version 0.26 or later, which is only currently available in Debian experimental. -- Jason Crain Fri, 01 Nov 2019 02:59:35 -0600 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gexiv2/+bug/1861985/+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 1841563] Re: Update to 0.12.0
gexiv2 0.12.0-2 is in Ubuntu Focal (https://bugs.launchpad.net/ubuntu/+source/gexiv2/0.12.0-2) See also bug 1861985. ** Changed in: gexiv2 (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gexiv2 in Ubuntu. https://bugs.launchpad.net/bugs/1841563 Title: Update to 0.12.0 Status in gexiv2 package in Ubuntu: Fix Released Bug description: The new version requires a newer exiv library version though To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gexiv2/+bug/1841563/+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 1862855] Re: "file does not exist" for existing files
Launchpad is a great place for you to report bugs about the libreoffice snap so you did it right :) Since Canonical delivers both a deb and snap of libreoffice, it's handy for me to know which one you're using. Since you're using the snap, I recommend putting your libreoffice files somewhere in your $HOME directory so that your snap can access them. ** Changed in: libreoffice (Ubuntu) Status: New => Invalid -- 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/1862855 Title: "file does not exist" for existing files Status in libreoffice package in Ubuntu: Invalid Bug description: libreoffice reports files are missing when trying to open them from anywhere but $HOME/Documents/ May be related to Ubuntu moving libreoffice to be a snap package. How to reproduce: $ echo "anything at all" >/tmp/testfile.txt $ libreoffice /tmp/testfile.txt Expected: LibreOffice Writer starts, or I'm prompted for whether I wanted to use --writer or --calc Seen: error message "/tmp/testfile.txt does not exist" ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: libreoffice (not installed) ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: KDE Date: Tue Feb 11 18:14:58 2020 InstallationDate: Installed on 2018-10-30 (469 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: libreoffice UpgradeStatus: Upgraded to eoan on 2019-11-14 (89 days ago) mtime.conffile..etc.logrotate.d.apport: 2018-12-13T12:13:33.355709 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1862855/+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 1862910] Re: gnome-shell leaking memory
I had initially misunderstood which way round you wanted me to check with the seconds setting, but I had checked carefully both ways and have now checked again that I cannot see any discernable leakage with seconds enabled, but I have got it disabled now. I have also confirmed without doubt that it is appimagelauncher daemon that is triggering the problem. With it disabled there is no apparent leakage and with it enabled there is. However, rather irritatingly, I have been unable to replicate this on another machine, so there must be some additional interaction on the failing system. Currently I have no idea what that might be. -- 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/1862910 Title: gnome-shell leaking memory Status in gnome-shell package in Ubuntu: Incomplete Bug description: On one of my machines which has been upgraded over several years and is now running 19.10 just one of the configured users appears to be seeing a dramatic memory leak in gnome-shell, even when nothing is happening on the UI. Immediately after logging on, using the Ubuntu selection from the logon screen, gnome shell shows as using about 134MB. From there it climbs at about 300MB per hour and after a few hours the machine grinds to a crawl, not surprisingly. This happens even if the user logs on and then the machine is left completely alone. Logout and back in frees all the memory. A test user I have configured sees no such problem. I have uninstalled all extensions apart from the system ones, disabled all the system ones and reset all the gnome settings using dconf reset -f /org/gnome/ to no avail. Also I have removed ~/.local/share/gnome-shell and allowed it to recreate it. Also I have removed .compiz, .config/dconf/user, .gconf, .gnome, .gnome2. I can't see anything obvious in the log. It must be something in my settings that is triggering it as the other user does not see it, but I have run out of ideas on what to try. See also bug #1856516 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.1+git20191024-1ubuntu1~19.10.1 ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13 Uname: Linux 5.3.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Feb 12 08:54:21 2020 DisplayManager: gdm3 InstallationDate: Installed on 2014-10-21 (1939 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20141017) RelatedPackageVersions: mutter-common 3.34.1+git20191107-1ubuntu1~19.10.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to eoan on 2020-01-27 (15 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1862910/+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 1863026] Re: Remove my_bool typedef workaround
** Changed in: libodb-mysql (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to redland in Ubuntu. https://bugs.launchpad.net/bugs/1863026 Title: Remove my_bool typedef workaround Status in argus-clients package in Ubuntu: In Progress Status in asterisk package in Ubuntu: In Progress Status in clickhouse package in Ubuntu: In Progress Status in cppdb package in Ubuntu: In Progress Status in dballe package in Ubuntu: In Progress Status in gambas3 package in Ubuntu: In Progress Status in gearmand package in Ubuntu: In Progress Status in gerbera package in Ubuntu: In Progress Status in gnokii package in Ubuntu: In Progress Status in hoel package in Ubuntu: In Progress Status in jabberd2 package in Ubuntu: In Progress Status in kannel package in Ubuntu: In Progress Status in libgda5 package in Ubuntu: In Progress Status in libodb-mysql package in Ubuntu: In Progress Status in lyricue package in Ubuntu: New Status in motion package in Ubuntu: New Status in mysql-8.0 package in Ubuntu: In Progress Status in mysql-ocaml package in Ubuntu: New Status in mysqltcl package in Ubuntu: New Status in opendnssec package in Ubuntu: New Status in opensmtpd-extras package in Ubuntu: New Status in orthanc-mysql package in Ubuntu: New Status in pike8.0 package in Ubuntu: New Status in pvpgn package in Ubuntu: New Status in qt4-x11 package in Ubuntu: New Status in redland package in Ubuntu: New Status in tango package in Ubuntu: New Status in tntdb package in Ubuntu: New Status in voms-mysql-plugin package in Ubuntu: New Status in vtk7 package in Ubuntu: New Status in w1retap package in Ubuntu: New Status in zoneminder package in Ubuntu: New Bug description: During the previous development cycle, when mysql 8 was introduced, too many reverse deps failed due to the my_bool removal. It was then decided to put that back in to let the reverse dependencies build again. Now we should try to drop it one more time, and instead fix the reverse dependencies. Either by updating them, if upstream fixed it, or reintroducing only this my_bool typedef in the reverse dependency itself, instead of in mysql as it's now. This bug will track these tasks: - remove my_bool workaround from Ubuntu's mysql 8 package - fix the build of the reverse dependencies, each one a task of this bug. PPA with test builds: https://launchpad.net/~ahasenack/+archive/ubuntu/mysql8-my-bool- removal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/argus-clients/+bug/1863026/+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 1863026] Re: Remove my_bool typedef workaround
** Changed in: libgda5 (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to redland in Ubuntu. https://bugs.launchpad.net/bugs/1863026 Title: Remove my_bool typedef workaround Status in argus-clients package in Ubuntu: In Progress Status in asterisk package in Ubuntu: In Progress Status in clickhouse package in Ubuntu: In Progress Status in cppdb package in Ubuntu: In Progress Status in dballe package in Ubuntu: In Progress Status in gambas3 package in Ubuntu: In Progress Status in gearmand package in Ubuntu: In Progress Status in gerbera package in Ubuntu: In Progress Status in gnokii package in Ubuntu: In Progress Status in hoel package in Ubuntu: In Progress Status in jabberd2 package in Ubuntu: In Progress Status in kannel package in Ubuntu: In Progress Status in libgda5 package in Ubuntu: In Progress Status in libodb-mysql package in Ubuntu: New Status in lyricue package in Ubuntu: New Status in motion package in Ubuntu: New Status in mysql-8.0 package in Ubuntu: In Progress Status in mysql-ocaml package in Ubuntu: New Status in mysqltcl package in Ubuntu: New Status in opendnssec package in Ubuntu: New Status in opensmtpd-extras package in Ubuntu: New Status in orthanc-mysql package in Ubuntu: New Status in pike8.0 package in Ubuntu: New Status in pvpgn package in Ubuntu: New Status in qt4-x11 package in Ubuntu: New Status in redland package in Ubuntu: New Status in tango package in Ubuntu: New Status in tntdb package in Ubuntu: New Status in voms-mysql-plugin package in Ubuntu: New Status in vtk7 package in Ubuntu: New Status in w1retap package in Ubuntu: New Status in zoneminder package in Ubuntu: New Bug description: During the previous development cycle, when mysql 8 was introduced, too many reverse deps failed due to the my_bool removal. It was then decided to put that back in to let the reverse dependencies build again. Now we should try to drop it one more time, and instead fix the reverse dependencies. Either by updating them, if upstream fixed it, or reintroducing only this my_bool typedef in the reverse dependency itself, instead of in mysql as it's now. This bug will track these tasks: - remove my_bool workaround from Ubuntu's mysql 8 package - fix the build of the reverse dependencies, each one a task of this bug. PPA with test builds: https://launchpad.net/~ahasenack/+archive/ubuntu/mysql8-my-bool- removal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/argus-clients/+bug/1863026/+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 1863026] Re: Remove my_bool typedef workaround
** Changed in: jabberd2 (Ubuntu) Status: New => In Progress ** Changed in: kannel (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to redland in Ubuntu. https://bugs.launchpad.net/bugs/1863026 Title: Remove my_bool typedef workaround Status in argus-clients package in Ubuntu: In Progress Status in asterisk package in Ubuntu: In Progress Status in clickhouse package in Ubuntu: In Progress Status in cppdb package in Ubuntu: In Progress Status in dballe package in Ubuntu: In Progress Status in gambas3 package in Ubuntu: In Progress Status in gearmand package in Ubuntu: In Progress Status in gerbera package in Ubuntu: In Progress Status in gnokii package in Ubuntu: In Progress Status in hoel package in Ubuntu: In Progress Status in jabberd2 package in Ubuntu: In Progress Status in kannel package in Ubuntu: In Progress Status in libgda5 package in Ubuntu: New Status in libodb-mysql package in Ubuntu: New Status in lyricue package in Ubuntu: New Status in motion package in Ubuntu: New Status in mysql-8.0 package in Ubuntu: In Progress Status in mysql-ocaml package in Ubuntu: New Status in mysqltcl package in Ubuntu: New Status in opendnssec package in Ubuntu: New Status in opensmtpd-extras package in Ubuntu: New Status in orthanc-mysql package in Ubuntu: New Status in pike8.0 package in Ubuntu: New Status in pvpgn package in Ubuntu: New Status in qt4-x11 package in Ubuntu: New Status in redland package in Ubuntu: New Status in tango package in Ubuntu: New Status in tntdb package in Ubuntu: New Status in voms-mysql-plugin package in Ubuntu: New Status in vtk7 package in Ubuntu: New Status in w1retap package in Ubuntu: New Status in zoneminder package in Ubuntu: New Bug description: During the previous development cycle, when mysql 8 was introduced, too many reverse deps failed due to the my_bool removal. It was then decided to put that back in to let the reverse dependencies build again. Now we should try to drop it one more time, and instead fix the reverse dependencies. Either by updating them, if upstream fixed it, or reintroducing only this my_bool typedef in the reverse dependency itself, instead of in mysql as it's now. This bug will track these tasks: - remove my_bool workaround from Ubuntu's mysql 8 package - fix the build of the reverse dependencies, each one a task of this bug. PPA with test builds: https://launchpad.net/~ahasenack/+archive/ubuntu/mysql8-my-bool- removal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/argus-clients/+bug/1863026/+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 1863026] Re: Remove my_bool typedef workaround
** Changed in: hoel (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to redland in Ubuntu. https://bugs.launchpad.net/bugs/1863026 Title: Remove my_bool typedef workaround Status in argus-clients package in Ubuntu: In Progress Status in asterisk package in Ubuntu: In Progress Status in clickhouse package in Ubuntu: In Progress Status in cppdb package in Ubuntu: In Progress Status in dballe package in Ubuntu: In Progress Status in gambas3 package in Ubuntu: In Progress Status in gearmand package in Ubuntu: In Progress Status in gerbera package in Ubuntu: In Progress Status in gnokii package in Ubuntu: In Progress Status in hoel package in Ubuntu: In Progress Status in jabberd2 package in Ubuntu: New Status in kannel package in Ubuntu: New Status in libgda5 package in Ubuntu: New Status in libodb-mysql package in Ubuntu: New Status in lyricue package in Ubuntu: New Status in motion package in Ubuntu: New Status in mysql-8.0 package in Ubuntu: In Progress Status in mysql-ocaml package in Ubuntu: New Status in mysqltcl package in Ubuntu: New Status in opendnssec package in Ubuntu: New Status in opensmtpd-extras package in Ubuntu: New Status in orthanc-mysql package in Ubuntu: New Status in pike8.0 package in Ubuntu: New Status in pvpgn package in Ubuntu: New Status in qt4-x11 package in Ubuntu: New Status in redland package in Ubuntu: New Status in tango package in Ubuntu: New Status in tntdb package in Ubuntu: New Status in voms-mysql-plugin package in Ubuntu: New Status in vtk7 package in Ubuntu: New Status in w1retap package in Ubuntu: New Status in zoneminder package in Ubuntu: New Bug description: During the previous development cycle, when mysql 8 was introduced, too many reverse deps failed due to the my_bool removal. It was then decided to put that back in to let the reverse dependencies build again. Now we should try to drop it one more time, and instead fix the reverse dependencies. Either by updating them, if upstream fixed it, or reintroducing only this my_bool typedef in the reverse dependency itself, instead of in mysql as it's now. This bug will track these tasks: - remove my_bool workaround from Ubuntu's mysql 8 package - fix the build of the reverse dependencies, each one a task of this bug. PPA with test builds: https://launchpad.net/~ahasenack/+archive/ubuntu/mysql8-my-bool- removal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/argus-clients/+bug/1863026/+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 1863026] Re: Remove my_bool typedef workaround
** Changed in: gnokii (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to redland in Ubuntu. https://bugs.launchpad.net/bugs/1863026 Title: Remove my_bool typedef workaround Status in argus-clients package in Ubuntu: In Progress Status in asterisk package in Ubuntu: In Progress Status in clickhouse package in Ubuntu: In Progress Status in cppdb package in Ubuntu: In Progress Status in dballe package in Ubuntu: In Progress Status in gambas3 package in Ubuntu: In Progress Status in gearmand package in Ubuntu: In Progress Status in gerbera package in Ubuntu: In Progress Status in gnokii package in Ubuntu: In Progress Status in hoel package in Ubuntu: New Status in jabberd2 package in Ubuntu: New Status in kannel package in Ubuntu: New Status in libgda5 package in Ubuntu: New Status in libodb-mysql package in Ubuntu: New Status in lyricue package in Ubuntu: New Status in motion package in Ubuntu: New Status in mysql-8.0 package in Ubuntu: In Progress Status in mysql-ocaml package in Ubuntu: New Status in mysqltcl package in Ubuntu: New Status in opendnssec package in Ubuntu: New Status in opensmtpd-extras package in Ubuntu: New Status in orthanc-mysql package in Ubuntu: New Status in pike8.0 package in Ubuntu: New Status in pvpgn package in Ubuntu: New Status in qt4-x11 package in Ubuntu: New Status in redland package in Ubuntu: New Status in tango package in Ubuntu: New Status in tntdb package in Ubuntu: New Status in voms-mysql-plugin package in Ubuntu: New Status in vtk7 package in Ubuntu: New Status in w1retap package in Ubuntu: New Status in zoneminder package in Ubuntu: New Bug description: During the previous development cycle, when mysql 8 was introduced, too many reverse deps failed due to the my_bool removal. It was then decided to put that back in to let the reverse dependencies build again. Now we should try to drop it one more time, and instead fix the reverse dependencies. Either by updating them, if upstream fixed it, or reintroducing only this my_bool typedef in the reverse dependency itself, instead of in mysql as it's now. This bug will track these tasks: - remove my_bool workaround from Ubuntu's mysql 8 package - fix the build of the reverse dependencies, each one a task of this bug. PPA with test builds: https://launchpad.net/~ahasenack/+archive/ubuntu/mysql8-my-bool- removal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/argus-clients/+bug/1863026/+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 1849859] Re: smb printing fails
Hi everyone. Any news about this bug? I'm trying just now...but it asks me for credentials with no way to insert username and password -- 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/1849859 Title: smb printing fails Status in cups package in Ubuntu: Confirmed Status in samba package in Ubuntu: Confirmed Status in system-config-printer package in Ubuntu: Confirmed Bug description: when I connect to smb server (nas) permanently appears "Error while getting peer-to-peer dbus connection: Operation was cancelled" The printer at this NAS doesn't work too. "held for authentication KeyError: 'auth-info-required'" The same printer at usb port works fine. Ubuntu development version 20.04 system-config-printer version 1.5.11-4ubuntu1 smbclient version 2:4.10.7+dfsg-0ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1849859/+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 1792424] Re: Left panel flickers like crazy during several seconds after deleting a bunch of files
Please fix the importance. "Importance Low" is clearly wrong (as I pointed out almost a year ago). -- 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/1792424 Title: Left panel flickers like crazy during several seconds after deleting a bunch of files Status in nautilus package in Ubuntu: Confirmed Bug description: I have no idea if there are some requirements to trigger this issue, so I don't know whether you'll be able to reproduce it by just following my steps. Anyway, I can reproduce it 100% of the times: 1. Open some folder in Nautilus 2. Select a few files. Make sure you select quite a few 3. Delete them by pressing the DEL key Expected: Nothing, a part from the files being deleted and disappearing from the displayed folder contents. Observed: During a few seconds after you hit Delete (I guess the time it takes to move the files to Trash and do some associated action, which by the way I don't know what it is that can take so long when deleting just a handful of files), the items in the list of shortcuts in the left panel (see screenshot) start flickering frantically, like crazy. It's pathetic. It looks like the item called "Networks", just below "Trash", disappears and reappears several times very quickly, causing all the items below it to move down and up, hence the flickering. Obviously it makes no sense. Note: there's nothing wrong to be appreciated in my screenshot, it just indicates where the flickering happens. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: nautilus 1:3.18.4.is.3.14.3-0ubuntu6 ProcVersionSignature: Ubuntu 4.4.0-135.161-generic 4.4.140 Uname: Linux 4.4.0-135-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CurrentDesktop: Unity Date: Thu Sep 13 19:24:36 2018 GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'190' b'org.gnome.nautilus.window-state' b'geometry' b"'1044x767+374+165'" b'org.gnome.nautilus.list-view' b'use-tree-view' b'true' b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'date_modified', 'date_accessed', 'owner', 'group', 'permissions', 'mime_type', 'where']" InstallationDate: Installed on 2013-10-11 (1797 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1792424/+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 1792424] Re: Left panel flickers like crazy during several seconds after deleting a bunch of files
Please fix the importance. And to the idiot who set this to low: stop setting the importance of bugs. -- 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/1792424 Title: Left panel flickers like crazy during several seconds after deleting a bunch of files Status in nautilus package in Ubuntu: Confirmed Bug description: I have no idea if there are some requirements to trigger this issue, so I don't know whether you'll be able to reproduce it by just following my steps. Anyway, I can reproduce it 100% of the times: 1. Open some folder in Nautilus 2. Select a few files. Make sure you select quite a few 3. Delete them by pressing the DEL key Expected: Nothing, a part from the files being deleted and disappearing from the displayed folder contents. Observed: During a few seconds after you hit Delete (I guess the time it takes to move the files to Trash and do some associated action, which by the way I don't know what it is that can take so long when deleting just a handful of files), the items in the list of shortcuts in the left panel (see screenshot) start flickering frantically, like crazy. It's pathetic. It looks like the item called "Networks", just below "Trash", disappears and reappears several times very quickly, causing all the items below it to move down and up, hence the flickering. Obviously it makes no sense. Note: there's nothing wrong to be appreciated in my screenshot, it just indicates where the flickering happens. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: nautilus 1:3.18.4.is.3.14.3-0ubuntu6 ProcVersionSignature: Ubuntu 4.4.0-135.161-generic 4.4.140 Uname: Linux 4.4.0-135-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CurrentDesktop: Unity Date: Thu Sep 13 19:24:36 2018 GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'190' b'org.gnome.nautilus.window-state' b'geometry' b"'1044x767+374+165'" b'org.gnome.nautilus.list-view' b'use-tree-view' b'true' b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'date_modified', 'date_accessed', 'owner', 'group', 'permissions', 'mime_type', 'where']" InstallationDate: Installed on 2013-10-11 (1797 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1792424/+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 1848845] Re: [needs-packaging] Silesian LibreOffice version unavailable
** Changed in: libreoffice (Ubuntu) Status: Fix Committed => Fix Released -- 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/1848845 Title: [needs-packaging] Silesian LibreOffice version unavailable Status in libreoffice package in Ubuntu: Fix Released Bug description: Hi, LibreOffice has been available in Silesian since the beginning of September but the language pack is not available in the Ubuntu Repository. Can I request its addition? Thank you! Best, Gregory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1848845/+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 1863123] [NEW] Fail to connect bug still persists - Removal tool???
Public bug reported: Any help in removing this bug that randomly mimics connection failure. After x-Diagnose program and reporting this bug, it clears out but always reappears later again and again. Is there a removal tool or program that can clear it out for good? I appreciate any tips or help that I can get. Thank you for your time in reading this report. J.Chosta ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-76.86-generic 4.15.18 Uname: Linux 4.15.0-76-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Thu Feb 13 10:27:26 2020 DistUpgraded: 2018-12-25 11:16:26,692 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RV610 [Radeon HD 2400 PRO] [1002:94c3] (prog-if 00 [VGA controller]) Subsystem: Dell Radeon HD 2400 Pro [1028:0302] InstallationDate: Installed on 2016-08-03 (1289 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: Dell Inc. Dell XPS420 ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-76-generic root=UUID=e737e1ac-8869-44b7-a03f-477223f8 ro drm.debug=0xe plymouth:debug SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2018-12-25 (414 days ago) dmi.bios.date: 03/27/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: A04 dmi.board.name: 0TP406 dmi.board.vendor: Dell Inc. dmi.chassis.type: 7 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA04:bd03/27/2008:svnDellInc.:pnDellXPS420:pvr:rvnDellInc.:rn0TP406:rvr:cvnDellInc.:ct7:cvr: dmi.product.name: Dell XPS420 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 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 xserver.bootTime: Tue Dec 25 08:33:58 2018 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputLogitech Logitech USB Speaker KEYBOARD, id 8 inputLogitech USB-PS/2 Optical Mouse MOUSE, id 9 inputDell Dell USB Keyboard KEYBOARD, id 10 xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-0ubuntu0.8 xserver.video_driver: radeon ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic 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/1863123 Title: Fail to connect bug still persists - Removal tool??? Status in xorg package in Ubuntu: New Bug description: Any help in removing this bug that randomly mimics connection failure. After x-Diagnose program and reporting this bug, it clears out but always reappears later again and again. Is there a removal tool or program that can clear it out for good? I appreciate any tips or help that I can get. Thank you for your time in reading this report. J.Chosta ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-76.86-generic 4.15.18 Uname: Linux 4.15.0-76-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Thu Feb 13 10:27:26 2020 DistUpgraded: 2018-12-25 11:16:26,692 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RV610 [Radeon HD 2400 PRO] [1002:94c3] (prog-if 00 [VGA controller]) Subsystem: Dell Radeon HD 2400 Pro [1028:0302] InstallationDate: Installed on 2016-08-03 (1289 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: Dell Inc. Dell XPS420 ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-76-generic root=UUID=e737e1ac-8869-44b7-a03f-477223f8 ro drm
[Desktop-packages] [Bug 1245473] Re: Binding ctrl+shift, alt+shift, etc for switching keyboard layout makes shortcuts with ctrl+shift, etc not working in any program
A. Major kudos to nrbrtx for maintaining the patched Xorg PPA - this was a life saver, and I don't believe it was mentioned enough. B. Is this still an issue? Currently - on beta focal, I am using Xorg from Ubuntu (without Norbert's PPA) on KDE Plasma 5.18, and I don't see to have this problem: I have ALT+SHIFT bound to layout change (`setxkbmap -option grp:alt_shift_toggle`), and ALT+SHIFT changes language while ALT+SHIFT+ triggers shortcut (I use Eclipse which defaults to a lot of ALT+SHIFT-* shortcuts). Is anyone on focal or eoan still have this problem (when using Ubuntu or upstream xorg)? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1245473 Title: Binding ctrl+shift, alt+shift, etc for switching keyboard layout makes shortcuts with ctrl+shift, etc not working in any program Status in GNOME Settings Daemon: Fix Released Status in GNOME Shell: Won't Fix Status in Unity: Confirmed Status in X.Org X server: Unknown Status in firefox package in Ubuntu: Confirmed Status in gnome-settings-daemon package in Ubuntu: Triaged Status in gnome-shell package in Ubuntu: Confirmed Status in gnome-terminal package in Ubuntu: Confirmed Status in kubuntu-meta package in Ubuntu: Confirmed Status in unity package in Ubuntu: Triaged Status in gnome-settings-daemon package in ALT Linux: Unknown Status in gnome-settings-daemon package in Debian: New Status in gnome-settings-daemon package in Fedora: Won't Fix Status in gnome-settings-daemon package in openSUSE: Confirmed Bug description: Tried only with ctrl+shift, maybe behaves the same for other modifier key combinations when used as shortcut for switching layouts. - Set ctrl+shift as shortcut for switching keyboard layouts - Try to use ctrl+shift+v, ctrl+shift+c in Terminal -- it doesn't work (actually Terminal window loses focus when ctrl+shift is pressed, and layout is switched) -- For other layout switching problems introduced in Ubuntu 13.10 you can see bug 1218322. -- ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gnome-settings-daemon 3.8.5-0ubuntu11.1 ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6 Uname: Linux 3.11.0-13-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Mon Oct 28 16:40:02 2013 InstallationDate: Installed on 2013-10-23 (5 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MarkForUpload: True SourcePackage: gnome-settings-daemon UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/1245473/+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 58977] Re: Maximizing ignores docked panles with Xinerama
** Changed in: compiz (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/58977 Title: Maximizing ignores docked panles with Xinerama Status in Metacity: Fix Released Status in compiz package in Ubuntu: Fix Released Status in kdebase-workspace package in Ubuntu: Invalid Status in metacity package in Ubuntu: Fix Released Status in metacity package in Debian: Fix Released Bug description: Binary package hint: metacity Hi When I add another screen using Xinerama, the gnome panels remain in the first screen, which is great, but when the panel is aligned vertically near the border between the two screens (either on the right of the left screen, or on the left of the right screen), maximizing a window ignores the panel, and the window is maximized right to the edge of the screen. Steps to reproduce: 1. Use xinerama with the second screen to the right of the first. 2. Add a vertical gnome panel to the right edge of the left screen. 3. maximize a window in the left screen. 4. The screen is maximized right to the edge of the screen, instead of the edge of the panel. To manage notifications about this bug go to: https://bugs.launchpad.net/metacity/+bug/58977/+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 1862459] Re: ubuntu 18 screen flicker/blink
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public -- 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/1862459 Title: ubuntu 18 screen flicker/blink Status in xorg package in Ubuntu: New Bug description: Ubuntu screen flicker /blinking on start laptop every time ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-76.86-generic 4.15.18 Uname: Linux 4.15.0-76-generic x86_64 NonfreeKernelModules: wl .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CompositorRunning: None Date: Sat Feb 8 20:50:43 2020 DistUpgraded: 2019-06-27 23:49:46,134 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 4.15.0-76-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company HD Graphics 5500 [103c:80c1] InstallationDate: Installed on 2015-10-17 (1574 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) MachineType: Hewlett-Packard HP Notebook ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-76-generic root=UUID=733f49c2-0b52-4a07-9eea-15cbf15593cf ro quiet splash SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2019-06-27 (225 days ago) dmi.bios.date: 06/04/2015 dmi.bios.vendor: Insyde dmi.bios.version: F.0B dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 80C1 dmi.board.vendor: Hewlett-Packard dmi.board.version: 96.11 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.0B:bd06/04/2015:svnHewlett-Packard:pnHPNotebook:pvrType1ProductConfigId:rvnHewlett-Packard:rn80C1:rvr96.11:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP dmi.product.name: HP Notebook dmi.product.version: Type1ProductConfigId dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 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 xserver.bootTime: Thu Jun 27 18:02:31 2019 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 20049 vendor SDC xserver.version: 2:1.18.4-0ubuntu0.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1862459/+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 1862553] Re: gnome-control-center crashed with SIGSEGV in cc_panel_get_title_widget()
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security 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/1862553 Title: gnome-control-center crashed with SIGSEGV in cc_panel_get_title_widget() Status in gnome-control-center package in Ubuntu: New Bug description: problem with Ubuntu software centre ver.3.35.2 ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.35.90-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Feb 10 00:28:42 2020 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2020-02-06 (3 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200124) ProcCmdline: gnome-control-center SegvAnalysis: Segfault happened at: 0x55db27c2df87 : mov 0x3f8(%rax),%rax PC (0x55db27c2df87) ok source "0x3f8(%rax)" (0x03f8) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-control-center StacktraceTop: cc_panel_get_title_widget () ?? () ?? () g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: gnome-control-center crashed with SIGSEGV in cc_panel_get_title_widget() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1862553/+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 1863049] Re: plz rectify this bugs
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public -- 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/1863049 Title: plz rectify this bugs Status in xorg package in Ubuntu: New Bug description: q ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-64.73-generic 4.15.18 Uname: Linux 4.15.0-64-generic x86_64 NonfreeKernelModules: lkp_Ubuntu_4_15_0_64_73_generic_59 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Thu Feb 13 10:20:24 2020 DistUpgraded: 2018-09-13 18:17:06,036 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu DpkgLog: GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. HD Graphics 5500 [1043:19ad] InstallationDate: Installed on 2016-03-08 (1437 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: ASUSTeK COMPUTER INC. X555LAB ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-64-generic root=UUID=a8582c35-8f2e-4581-8019-65e2d7d13535 ro quiet splash SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2018-09-13 (517 days ago) dmi.bios.date: 08/04/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X555LAB.503 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X555LAB dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX555LAB.503:bd08/04/2015:svnASUSTeKCOMPUTERINC.:pnX555LAB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX555LAB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: X dmi.product.name: X555LAB dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 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 xserver.bootTime: Thu Sep 13 14:39:19 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id1116 vendor LGD xserver.version: 2:1.18.4-0ubuntu0.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1863049/+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 1863050] Re: package nvidia-340 (not installed) failed to install/upgrade: a tentar sobre-escrever '/lib/udev/rules.d/71-nvidia.rules', que também está no pacote nvidia-kernel-
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public -- 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/1863050 Title: package nvidia-340 (not installed) failed to install/upgrade: a tentar sobre-escrever '/lib/udev/rules.d/71-nvidia.rules', que também está no pacote nvidia-kernel-common-390 390.132-0ubuntu2 Status in nvidia-graphics-drivers-340 package in Ubuntu: New Bug description: package nvidia-340 (not installed) failed to install/upgrade: a tentar sobre-escrever '/lib/udev/rules.d/71-nvidia.rules', que também está no pacote nvidia-kernel-common-390 390.132-0ubuntu2] ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-340 (not installed) ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 Date: Thu Feb 13 02:00:07 2020 ErrorMessage: a tentar sobre-escrever '/lib/udev/rules.d/71-nvidia.rules', que também está no pacote nvidia-kernel-common-390 390.132-0ubuntu2 InstallationDate: Installed on 2020-02-13 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200124) Python3Details: /usr/bin/python3.8, Python 3.8.2rc1, python3-minimal, 3.8.0-3 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu2 apt 1.9.9 SourcePackage: nvidia-graphics-drivers-340 Title: package nvidia-340 (not installed) failed to install/upgrade: a tentar sobre-escrever '/lib/udev/rules.d/71-nvidia.rules', que também está no pacote nvidia-kernel-common-390 390.132-0ubuntu2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1863050/+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 1862549] Re: memory leak when annotating PDFs
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: evince (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1862549 Title: memory leak when annotating PDFs Status in evince package in Ubuntu: Confirmed Bug description: When annotating PDFs or scrolling through larger PDFs that contain lots of annotations, evince claims a large amount of memory and never releases it. This becomes especially apparent when using the highlight feature, i.e. highlighting various parts of the text on the PDF. On a 12-page PDF, not annotated, evince used about 35 MB of RAM and claimed an additional 30 as soon as I used the highlight feature the first time, then this repeats with about the same amount or more for each additional highlight. The interface starts to lag visibly the more memory is allocated. Occasionally, the memory usage goes down by a few percent when scrolling, but it tends to allocate more and more memory until the system runs out of memory. Using the same 12-page PDF with about 100 highlighted lines and quickly scrolling through the document multiple times, evince reached about 6 GB of memory usage in less than one minute. This issue also makes closing documents very slow, taking about 5 to 10 seconds for each gigabyte of memory allocated. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: evince 3.34.1-1build1 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Feb 9 23:13:02 2020 InstallationDate: Installed on 2020-01-30 (10 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200124) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/zsh SourcePackage: evince UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1862549/+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 1863103] [NEW] apparmor messages for libreoffice-oopslash about /tmp/OSL_PIPE_1000_SingleOfficeIPC_a0196a...
Public bug reported: i opened libreoffice writer, then, after some time, clicked a document, to open it in libreoffice, and i see these messages in syslog: Feb 13 16:24:49 dinar-Lenovo-G580 kernel: [17788.979570] audit: type=1400 audit(1581600289.824:108): apparmor="ALLOWED" operation="connect" profile="libreoffice-oopslash" name="/tmp/OSL_PIPE_1000_SingleOfficeIPC_a0196a99a9a51821ceebe3195d43" pid=9969 comm="oosplash" requested_mask="wr" denied_mask="wr" fsuid=1000 ouid=1000 Feb 13 16:24:49 dinar-Lenovo-G580 kernel: [17788.979578] audit: type=1400 audit(1581600289.824:109): apparmor="ALLOWED" operation="file_perm" profile="libreoffice-oopslash" name="/tmp/OSL_PIPE_1000_SingleOfficeIPC_a0196a99a9a51821ceebe3195d43" pid=9969 comm="oosplash" requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000 Feb 13 16:24:49 dinar-Lenovo-G580 kernel: [17788.979581] audit: type=1400 audit(1581600289.824:110): apparmor="ALLOWED" operation="file_perm" profile="libreoffice-oopslash" name="/tmp/OSL_PIPE_1000_SingleOfficeIPC_a0196a99a9a51821ceebe3195d43" pid=9969 comm="oosplash" requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000 Feb 13 16:24:49 dinar-Lenovo-G580 kernel: [17788.979781] audit: type=1400 audit(1581600289.828:111): apparmor="ALLOWED" operation="file_perm" profile="libreoffice-oopslash" name="/tmp/OSL_PIPE_1000_SingleOfficeIPC_a0196a99a9a51821ceebe3195d43" pid=9969 comm="oosplash" requested_mask="w" denied_mask="w" fsuid=1000 ouid=1000 Feb 13 16:24:49 dinar-Lenovo-G580 kernel: [17788.979786] audit: type=1400 audit(1581600289.828:112): apparmor="ALLOWED" operation="file_perm" profile="libreoffice-oopslash" name="/tmp/OSL_PIPE_1000_SingleOfficeIPC_a0196a99a9a51821ceebe3195d43" pid=9969 comm="oosplash" requested_mask="w" denied_mask="w" fsuid=1000 ouid=1000 also there was Feb 13 16:24:50 dinar-Lenovo-G580 kernel: [17789.649828] audit: type=1400 audit(1581600290.496:117): apparmor="ALLOWED" operation="open" profile="libreoffice-soffice" name="/home/dinar/.mozilla/firefox/sge95l3o.default/cert8.db" pid=8829 comm="soffice.bin" requested_mask="w" denied_mask="w" fsuid=1000 ouid=1000 i reported about that type of message: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1862331 . (but this time there is no request for key3.db). also there are messages about the opened document file itself, i am going to write a separate bug about that. ** 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/1863103 Title: apparmor messages for libreoffice-oopslash about /tmp/OSL_PIPE_1000_SingleOfficeIPC_a0196a... Status in libreoffice package in Ubuntu: New Bug description: i opened libreoffice writer, then, after some time, clicked a document, to open it in libreoffice, and i see these messages in syslog: Feb 13 16:24:49 dinar-Lenovo-G580 kernel: [17788.979570] audit: type=1400 audit(1581600289.824:108): apparmor="ALLOWED" operation="connect" profile="libreoffice-oopslash" name="/tmp/OSL_PIPE_1000_SingleOfficeIPC_a0196a99a9a51821ceebe3195d43" pid=9969 comm="oosplash" requested_mask="wr" denied_mask="wr" fsuid=1000 ouid=1000 Feb 13 16:24:49 dinar-Lenovo-G580 kernel: [17788.979578] audit: type=1400 audit(1581600289.824:109): apparmor="ALLOWED" operation="file_perm" profile="libreoffice-oopslash" name="/tmp/OSL_PIPE_1000_SingleOfficeIPC_a0196a99a9a51821ceebe3195d43" pid=9969 comm="oosplash" requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000 Feb 13 16:24:49 dinar-Lenovo-G580 kernel: [17788.979581] audit: type=1400 audit(1581600289.824:110): apparmor="ALLOWED" operation="file_perm" profile="libreoffice-oopslash" name="/tmp/OSL_PIPE_1000_SingleOfficeIPC_a0196a99a9a51821ceebe3195d43" pid=9969 comm="oosplash" requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000 Feb 13 16:24:49 dinar-Lenovo-G580 kernel: [17788.979781] audit: type=1400 audit(1581600289.828:111): apparmor="ALLOWED" operation="file_perm" profile="libreoffice-oopslash" name="/tmp/OSL_PIPE_1000_SingleOfficeIPC_a0196a99a9a51821ceebe3195d43" pid=9969 comm="oosplash" requested_mask="w" denied_mask="w" fsuid=1000 ouid=1000 Feb 13 16:24:49 dinar-Lenovo-G580 kernel: [17788.979786] audit: type=1400 audit(1581600289.828:112): apparmor="ALLOWED" operation="file_perm" profile="libreoffice-oopslash" name="/tmp/OSL_PIPE_1000_SingleOfficeIPC_a0196a99a9a51821ceebe3195d43" pid=9969 comm="oosplash" requested_mask="w" denied_mask="w" fsuid=1000 ouid=1000 also there was Feb 13 16:24:50 dinar-Lenovo-G580 kernel: [17789.649828] audit: type=1400 audit(1581600290.496:117): apparmor="ALLOWED" operation="open" profile="libreoffice-soffice" name="/home/dinar/.mozilla/firefox/sge95l3o.default/cert8.db" pid=8829 comm="soffice.bin" requested_mask="w" denied_mask="w" fsuid=1000 ouid=1000 i reported about that type
[Desktop-packages] [Bug 1853357] Re: display (whole computer?) hangs when I attempt to use DisplayLink with Wayland
This specific bug was fixed upstream, feel free to open another for similar scenarios please. ** Changed in: mutter (Ubuntu Focal) Status: Incomplete => Fix Released -- 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/1853357 Title: display (whole computer?) hangs when I attempt to use DisplayLink with Wayland Status in Mutter: New Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Eoan: Confirmed Status in mutter source package in Focal: Fix Released Bug description: [ Impact ] I am using the DisplayLink driver for Ubuntu provided at https://www.displaylink.com/downloads/ubuntu DisplayLink is working under Xorg, but when I try to use it under Wayland my whole display hangs and I can't even switch to a different VT with Ctrl-Alt-F3 so I think maybe the whole computer is hung? Not certain. [ Test case ] - Install DisplayLink drivers - Start GNOME Shell in wayland mode - Connect to a display-link dock - Expect the shell to work properly and be visible in the external device [ Regression potential ] Wayland session won't work even for standard drm devices I am using the DisplayLink driver for Ubuntu provided at https://www.displaylink.com/downloads/ubuntu, which I think is the only way to get DisplayLink fully working under Ubuntu? That is, DisplayLink didn't work when I installed the evdi-dkms and libevdi0 Ubuntu packages, and I couldn't find any other packages that might be relevant (did I miss something?) so as far as I can tell the only way to get everything that's needed is from displaylink.com. I'm reporting this issue while logged in under Xorg because I can't report it when logged in with my DisplayLink monitors plugged in under Wayland, for obvious reasons. :-/ ProblemType: BugDistroRelease: Ubuntu 19.10 Package: mutter 3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Nov 20 14:08:21 2019 InstallationDate: Installed on 2019-09-12 (69 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)SourcePackage: mutter UpgradeStatus: Upgraded to eoan on 2019-09-20 (61 days ago) modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2019-10-23T16:51:18.143596 To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1853357/+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 1846403] Re: gnome-shell sigsegv in meta_input_device_x11_get_current_tool -> meta_device_manager_x11_translate_event -> meta_clutter_backend_x11_translate_event -> meta_x11_ha
** Changed in: mutter (Ubuntu) Status: New => 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/1846403 Title: gnome-shell sigsegv in meta_input_device_x11_get_current_tool -> meta_device_manager_x11_translate_event -> meta_clutter_backend_x11_translate_event -> meta_x11_handle_event -> handle_host_xevent Status in gnome-shell package in Ubuntu: In Progress Status in mutter package in Ubuntu: Fix Released Status in gnome-shell source package in Eoan: In Progress Status in mutter source package in Eoan: Fix Committed Bug description: [ Impact ] Gnome shell crashes when handling some uncommon X11 events. [ Test case ] No real test case has been found yet, so the test should be based on monitoring the automatic-crash reports at https://errors.ubuntu.com/problem/9ed2d0f16e66799f511ef98bc6ad173a078bdc75 [ Regression potential ] Input events are ignored by gnome-shell --- The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.34.0-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/9ed2d0f16e66799f511ef98bc6ad173a078bdc75 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1846403/+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 1863097] [NEW] apparmor messages for libreoffice about mesa
Public bug reported: i started today an empty libreoffice writer and see 5 messages of this type: Feb 13 15:33:04 dinar-Lenovo-G580 kernel: [14684.517380] audit: type=1400 audit(1581597184.725:87): apparmor="ALLOWED" operation="open" profile="libreoffice-soffice" name="/usr/share/drirc.d/00-mesa- defaults.conf" pid=8830 comm="soffice.bin" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 several days ago i started it by clicking a document, and together with these messages there also was one this: Feb 6 20:47:08 dinar-Lenovo-G580 kernel: [104275.544663] audit: type=1400 audit(1581011228.808:876): apparmor="ALLOWED" operation="open" profile="libreoffice-soffice" name="/home/dinar/.cache/mesa_shader_cache/index" pid=15667 comm="soffice.bin" requested_mask="wrc" denied_mask="wrc" fsuid=1000 ouid=1000 ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New ** Description changed: i started today an empty libreoffice writer and see 5 messages of this type: Feb 13 15:33:04 dinar-Lenovo-G580 kernel: [14684.517380] audit: type=1400 audit(1581597184.725:87): apparmor="ALLOWED" operation="open" profile="libreoffice-soffice" name="/usr/share/drirc.d/00-mesa- defaults.conf" pid=8830 comm="soffice.bin" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 several days ago i started it by clicking a document, and together with these messages there also was one this: Feb 6 20:47:08 dinar-Lenovo-G580 kernel: [104275.544663] audit: type=1400 audit(1581011228.808:876): apparmor="ALLOWED" operation="open" profile="libreoffice-soffice" name="/home/dinar/.cache/mesa_shader_cache/index" pid=15667 comm="soffice.bin" requested_mask="wrc" denied_mask="wrc" fsuid=1000 ouid=1000 - - on that time, there were also messages about firefox's files: - https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1862331 . -- 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/1863097 Title: apparmor messages for libreoffice about mesa Status in libreoffice package in Ubuntu: New Bug description: i started today an empty libreoffice writer and see 5 messages of this type: Feb 13 15:33:04 dinar-Lenovo-G580 kernel: [14684.517380] audit: type=1400 audit(1581597184.725:87): apparmor="ALLOWED" operation="open" profile="libreoffice-soffice" name="/usr/share/drirc.d/00-mesa-defaults.conf" pid=8830 comm="soffice.bin" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 several days ago i started it by clicking a document, and together with these messages there also was one this: Feb 6 20:47:08 dinar-Lenovo-G580 kernel: [104275.544663] audit: type=1400 audit(1581011228.808:876): apparmor="ALLOWED" operation="open" profile="libreoffice-soffice" name="/home/dinar/.cache/mesa_shader_cache/index" pid=15667 comm="soffice.bin" requested_mask="wrc" denied_mask="wrc" fsuid=1000 ouid=1000 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1863097/+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 1855469] Re: gnome-shell lags on wayland
** Changed in: gnome-shell (Ubuntu) Status: Expired => Invalid -- 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/1855469 Title: gnome-shell lags on wayland Status in gnome-shell package in Ubuntu: Invalid Bug description: see https://discourse.ubuntu.com/t/boosting-the-real-time-performance- of-gnome-shell-3-34-in-ubuntu-19-10/13095/24 I’m using ubuntu on wayland for a while (Unity and Gnome since Unity abandon). But with ubuntu 19.10 upgrade, Gnome was so slow and laggy that I had thought to downgrade or a new laptop. I switched back to Xorg and now everything is as smoth as usual. I have an intel card, don’t know if it can help. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.1+git20191024-1ubuntu1~19.10.1 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Dec 6 18:54:15 2019 DisplayManager: gdm3 InstallationDate: Installed on 2015-05-23 (1658 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) RelatedPackageVersions: mutter-common 3.34.1+git20191107-1ubuntu1~19.10.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to eoan on 2019-11-03 (33 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1855469/+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 379367] Re: Gedit adding a newline at the end of file should be configurable
To those who think the default behavior is a "deficiency" or a "bad design decision": it is neither. It is the only correct behavior when dealing with text files. It is not a matter of "simple" vs. "complex" editors either: it is a matter of Windows vs. Unix text format. In the Windows world, text files use CRLF as line _separators_. In the Unix world, text files use LF (newline) as line _terminators_. This is an important distinction, and it implies that a text file _must_ end with a newline character. Otherwise it's not a valid text file. See "Why should text files end with a newline?": https://stackoverflow.com/questions/729692 The argument about this causing problems with PHP is moot. PHP accepts "?>\n" as a valid end-of-code delimiter: it doesn't output the final "\n". Proof: $ echo '' > foo.php $ hd foo.php# Notice the final 0a = LF 3c 3f 70 68 70 20 65 63 68 6f 20 22 66 6f 6f 22 |.| 0015 $ php foo.php | hd # Notice the _lack_ of final LF 66 6f 6f |foo| 0003 $ Note also that in vim you can save a file with no final newline, but for this you have to enable "binary" mode, which makes sense because the file you are saving is no longer a text file. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/379367 Title: Gedit adding a newline at the end of file should be configurable Status in gedit: Fix Released Status in gedit package in Ubuntu: Invalid Bug description: Binary package hint: gedit Ggedit auto adds a newline at the end of file.I hope it can be configurable. I'm not a c/c++ developer, i'm php developer. but I use gedit for my php developing. Gedit auto adds a new line at the end of file, which will cause a problem when the program runs. I hope this action can be configurable. thanks~! ProblemType: Bug Architecture: i386 DistroRelease: Ubuntu 8.10 ExecutablePath: /usr/bin/gedit Package: gedit 2.24.2-0ubuntu1 ProcEnviron: PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games LANG=zh_CN.UTF-8 SHELL=/bin/bash SourcePackage: gedit Uname: Linux 2.6.27-14-generic i686 To manage notifications about this bug go to: https://bugs.launchpad.net/gedit/+bug/379367/+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
