[Desktop-packages] [Bug 1887107] Re: Missing entry for timezone database when setting timezone via the text search
** Changed in: gnome-control-center (Ubuntu) Status: New => Triaged ** Summary changed: - Missing entry for timezone database when setting timezone via the text search + Can't find "Montreal" when setting Time Zone ** Changed in: gnome-control-center (Ubuntu) Importance: Low => Medium -- 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/1887107 Title: Can't find "Montreal" when setting Time Zone Status in gnome-control-center package in Ubuntu: Triaged Bug description: I can't find Montreal in the timezone search box, even though it is present in the /usr/share/zoneinfo database. What I did: Settings > Time & Date > Time Zone > Click in the search box and start typing Mont... What I expected: Autocompletion. What happened: No completion found. $ lsb_release -rd Description: Ubuntu 20.04 LTS Release: 20.04 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.1-1ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Jul 9 23:59:01 2020 ExecutablePath: /usr/bin/gnome-control-center ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash 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/1887107/+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 1103222] Re: Time zone location can't find Hong Kong
** Summary changed: - Time zone location can't find certain cities + Time zone location can't find Hong Kong ** Tags added: focal ** Changed in: gnome-control-center (Ubuntu) Status: New => Triaged ** Changed in: gnome-control-center (Ubuntu) Importance: Undecided => Medium -- 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/1103222 Title: Time zone location can't find Hong Kong Status in gnome-control-center package in Ubuntu: Triaged Bug description: Go to system settings > Time and Date > Clock > tick 'Time in other locations' Click 'Choose Locations...' Click the green plus to add a location and then try putting in Hong Kong Wait a second for it to give you the options to select from Notice that Hong Kong, China does not appear and is not selectable at all and you have to select one of the options it gives you. It only gives you the option to select Hong Kong in Guyana i.e. You can't select the real Hong Kong as a location. No doubt it has problems for other locations... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1103222/+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 1887010] Re: problème de démarrage ordinateur lenovo G50
It appears we do not yet have a full log from this machine. Next time the problem happens, please run: journalctl -b0 > journal.txt and then attach the resulting text file here. ** 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/1887010 Title: problème de démarrage ordinateur lenovo G50 Status in Ubuntu: Incomplete Bug description: Bonjour, En marche, l'ordinateur avec ubuntu 18.04 fonctionne très bien. Il s'éteint facilement. Pour le re démarrer, l'écran reste noir très longtemps, parfois pendant une heure avant de retrouver le bureau et re fonctionner normalement. Le disque dur fonctionne normalement, la barette mémoire aussi que j'ai testé en la remplaçant par une neuve: le problème reste. Je ne comprends pas la cause de ce problème. Pouvez vous m'aider? Merci Hello, When running, the computer with ubuntu 18.04 works very well. It goes out easily. To restart it, the screen remains black for a very long time, sometimes for an hour before finding the office and re-operating normally. The hard drive works normally, the memory module also that I tested by replacing it with a new one: the problem remains. I do not understand the cause of this problem. Can you help me? Thank you (I do not understand English) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-106.107-generic 4.15.18 Uname: Linux 4.15.0-106-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.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: Thu Jul 9 21:48:34 2020 DistUpgraded: 2019-08-20 08:07:14,386 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 5500 [17aa:390c] Subsystem: Lenovo Radeon R5 M330 [17aa:390c] InstallationDate: Installed on 2019-08-14 (330 days ago) InstallationMedia: Ubuntu 16.04.6 LTS "Xenial Xerus" - Release amd64 (20190227) MachineType: LENOVO 80E5 ProcEnviron: LANGUAGE=fr_FR PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-106-generic root=UUID=5732a78d-7e74-4071-9c56-b93ae51ffae3 ro quiet splash SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2019-08-20 (324 days ago) dmi.bios.date: 07/23/2015 dmi.bios.vendor: LENOVO dmi.bios.version: B0CN93WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Lenovo G50-80 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40700 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo G50-80 dmi.modalias: dmi:bvnLENOVO:bvrB0CN93WW:bd07/23/2015:svnLENOVO:pn80E5:pvrLenovoG50-80:rvnLENOVO:rnLenovoG50-80:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoG50-80: dmi.product.family: IDEAPAD dmi.product.name: 80E5 dmi.product.version: Lenovo G50-80 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.101-2~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.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: Wed Jun 24 22:12:46 2020 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu4.3 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1887010/+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 1887001] Re: Mouse suddenly stopped working
Please try these, in any order: 1. Replacing the batteries in your wireless mouse. 2. A wired mouse. 3. sudo apt remove xserver-xorg-input-synaptics ** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) ** Changed in: xorg-server (Ubuntu) Status: New => Incomplete ** Package changed: xorg-server (Ubuntu) => 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/1887001 Title: Mouse suddenly stopped working Status in Ubuntu: Incomplete Bug description: Mouse suddenly stopped working and didn't fix even after a reboot. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Jul 9 19:40:16 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Core Processor Integrated Graphics Controller [103c:146a] InstallationDate: Installed on 2019-05-02 (434 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: Hewlett-Packard HP Pavilion dm4 Notebook PC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic root=UUID=a3b4ba1a-5361-47c5-9d78-b04d395d28b8 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/21/2010 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.23 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 146A dmi.board.vendor: Hewlett-Packard dmi.board.version: 58.27 dmi.chassis.asset.tag: CNU0483ZXV dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnHewlett-Packard:bvrF.23:bd10/21/2010:svnHewlett-Packard:pnHPPaviliondm4NotebookPC:pvr058B11242B1020100:rvnHewlett-Packard:rn146A:rvr58.27:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV dmi.product.name: HP Pavilion dm4 Notebook PC dmi.product.sku: XH124UA#ABA dmi.product.version: 058B11242B1020100 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-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/+bug/1887001/+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 1887018] Re: Xorg crash when I was using Visual Studio code, throwing me back to the login screen
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. ** 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/1887018 Title: Xorg crash when I was using Visual Studio code, throwing me back to the login screen Status in Ubuntu: Incomplete Bug description: Sometimes, when this happens, the computer goes to sleep too. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CompositorRunning: None Date: Thu Jul 9 17:47:23 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 [1028:0810] InstallationDate: Installed on 2020-07-06 (3 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 002: ID 0c45:6a06 Microdia Integrated_Webcam_HD Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 5570 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic root=UUID=b7d02d55-0b33-48b4-8eb2-5217925c5f81 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/20/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.5 dmi.board.name: 09YTN7 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.5:bd02/20/2020:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5570 dmi.product.sku: 0810 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1 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+git20200226-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/+bug/1887018/+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 1886948] Re: Can't calibrate monitor
Please try: sudo apt install argyll ** Changed in: gnome-control-center (Ubuntu) Status: New => Incomplete -- 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/1886948 Title: Can't calibrate monitor Status in gnome-control-center package in Ubuntu: Incomplete Bug description: Description: Ubuntu 20.04 LTS Release: 20.04 Tried to calibrate my monitor with an external device (x-rite huey pro). Process seems to go fine and starts working on the calibration. At about 80% of the progress bar I receive the message (in basque, not sure where to search it in english): Kalibrazioak huts egin du Kalibratzeko behar diren tresnak ez daude instalatuta Kalibrazioaren gailua ken dezakezu Which translates to (free non-official translation) Calibration has failed. The tools needed for calibration are not installed You can remove the calibration device Launching the tool from the command line, I receive these messages: (gnome-control-center:3471): color-cc-panel-WARNING **: 13:28:57.868: calibration failed with code 4: failed to get filename for colprof (gnome-control-center:3471): color-cc-panel-WARNING **: 13:33:46.435: Failed to send Cancel: GDBus.Error:org.freedesktop.ColorHelper.Internal: cannot cancel as status is idle (gnome-control-center:3471): color-cc-panel-WARNING **: 13:33:46.436: failed to start calibrate: failed to calibrate ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Jul 9 13:38:26 2020 InstallationDate: Installed on 2020-06-25 (14 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=eu_ES.UTF-8 SHELL=/bin/bash 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/1886948/+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 1886996] Re: Restore previous configuration after turning off fractional scaling does not work
** Tags added: focal groovy -- 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/1886996 Title: Restore previous configuration after turning off fractional scaling does not work Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Focal: In Progress Bug description: 1. From control center, display panel, enable fractional scaling 2. Set scaling to some fractional value and apply and confirm it. 3. Turn off the fractional scaling switch and apply it 4. Fractional scaling should be reverted to the selected integer scaling. 5. When gnome-shell shows the confirmation dialog, click "Revert Settings" 6. Expect the fractional scaling to be re-enabled and applied as it used to be To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1886996/+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 1884428] Re: calculator won't open (error while loading shared libraries: libgtk-3.so.0: cannot open shared object file: No such file or directory)
hello any update please solve my problem -- 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/1884428 Title: calculator won't open (error while loading shared libraries: libgtk-3.so.0: cannot open shared object file: No such file or directory) Status in gnome-calculator package in Ubuntu: New Status in snapd package in Ubuntu: New Bug description: new bug ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.3.0-59.53~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-59-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Jun 21 18:21:50 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] [1002:15dd] (rev c8) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Radeon RX Vega 11 [1458:d000] MachineType: Gigabyte Technology Co., Ltd. A320M-S2H ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-59-generic root=UUID=38903ee5-fb7c-4faa-ac0c-0a499b16e531 ro quiet splash nomodeset vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/08/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F23 dmi.board.asset.tag: Default string dmi.board.name: A320M-S2H-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF23:bd08/08/2018:svnGigabyteTechnologyCo.,Ltd.:pnA320M-S2H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnA320M-S2H-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: A320M-S2H dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calculator/+bug/1884428/+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 1887222] Re: Plugins bundled with Rhythmbox link to for-sale domain (rhythmbox.org has been drop-caught)
Please apply the following upstream patch in all "possible" rhythmbox releases. https://gitlab.gnome.org/GNOME/rhythmbox/-/commit/64c07859c936df1bc739f21b87f7a56e6f8dd161 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/1887222 Title: Plugins bundled with Rhythmbox link to for-sale domain (rhythmbox.org has been drop-caught) Status in rhythmbox package in Ubuntu: New Bug description: Plugins bundled with Rhythmbox including "Cover Art Search", "FM Radio", and "Python Console" still link to http://www.rhythmbox.org/. Although http://www.rhythmbox.org/ used to redirect to https://wiki.gnome.org/Apps/Rhythmbox (source: https://web.archive.org/web/20200122080148/http://www.rhythmbox.org/), it now redirects to https://www.dropcatch.com/domain/rhythmbox.org, a site that appears to be selling the domain. Note: This is my first bug report! I apologize for attaching files that aren't relevant -- I'm still figuring this out! Most relevant is the PNG attatchment, bugReport.png. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: rhythmbox 3.4.4-1ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jul 11 02:02:53 2020 ExecutablePath: /usr/bin/rhythmbox InstallationDate: Installed on 2020-03-24 (109 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, user) LANG=en_US.UTF-8 SourcePackage: rhythmbox UpgradeStatus: Upgraded to focal on 2020-06-19 (22 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1887222/+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 1878288] Re: wifi settings doesnt launch
[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/1878288 Title: wifi settings doesnt launch Status in gnome-shell package in Ubuntu: Expired Bug description: When I click on the Wifi icon in the top right corner and then Wifi Settings under my wifi adatpernothing happen ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.19 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Tue May 12 16:21:10 2020 InstallationDate: Installed on 2020-01-20 (112 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: Upgraded to focal on 2020-05-11 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1878288/+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 1877540] Re: [HDA-Intel - HDA Intel, playback] volume slider problem for subwoofer
[Expired for alsa-driver (Ubuntu) because there has been no activity for 60 days.] ** Changed in: alsa-driver (Ubuntu) Status: Incomplete => Expired -- 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/1877540 Title: [HDA-Intel - HDA Intel, playback] volume slider problem for subwoofer Status in alsa-driver package in Ubuntu: Expired Bug description: In standard Ubuntu volume settings subwoofer level is alwas set to zero and i cant change it if i run pavucontrol and set separate levels for each channel it works, sound is working, but if i open ubuntu sound settings and touch subwoofer level control then level is instantly set to zero again once i was unable to change subwoofer level in pavucontrol while ubuntu sound settings is opened. after it is closed i can change voluve level of sub before I install pavucontrol front speaker was very quiet nearly mute also in test speakers there is no icon on subwoofer button ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-52.46-generic 5.3.18 Uname: Linux 5.3.0-52-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri May 8 11:00:18 2020 InstallationDate: Installed on 2018-03-04 (795 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180228) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_Card: Dell USB3.0 Dock - Dell USB3.0 Dock Symptom_PulseAudioLog: мая 08 10:26:20 tmpuser-EP43-UD3L dbus-daemon[1168]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.36' (uid=119 pid=1422 comm="/usr/bin/pulseaudio --daemonize=no " label="unconfined") мая 08 10:26:27 tmpuser-EP43-UD3L dbus-daemon[1168]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service' requested by ':1.135' (uid=119 pid=1422 comm="/usr/bin/pulseaudio --daemonize=no " label="unconfined") Symptom_Type: Volume slider, or mixer problems Title: [HDA-Intel - HDA Intel, playback] volume slider problem UpgradeStatus: Upgraded to eoan on 2019-11-07 (183 days ago) dmi.bios.date: 04/16/2009 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F4 dmi.board.name: EP43-UD3L dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF4:bd04/16/2009:svnGigabyteTechnologyCo.,Ltd.:pnEP43-UD3L:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnEP43-UD3L:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: EP43-UD3L dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1877540/+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 1878442] Re: settings menu doesn't open and goes into the login menu
[Expired for gnome-control-center (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-control-center (Ubuntu) Status: Incomplete => Expired -- 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/1878442 Title: settings menu doesn't open and goes into the login menu Status in gnome-control-center package in Ubuntu: Expired Bug description: When I try to open the settings button, it opens a black screen and then goes back into the user login menu, closing all the apps that were opened prior to this. Is there a way to fix this? I tried reinstalling the gnome-center, but it doensn't work and no drivers missing. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1878442/+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 1885346] Re: gnome-shell-calendar-server leaks GBs of memory every few days
Nice! -- 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/1885346 Title: gnome-shell-calendar-server leaks GBs of memory every few days Status in gnome-shell package in Ubuntu: Fix Committed Status in gnome-shell package in Debian: Unknown Bug description: It's been happening repeatedly over the last maybe week? I have to manually kill it about once a day, when I start to feel everything slow down as the OS starts to swap. Actually, I tracked down and fixed a few leaks in the code, and it looks stable so far. I'll submit a patch soon, as well as send the fix upstream to Gnome. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1885346/+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 1885346] Re: gnome-shell-calendar-server leaks GBs of memory every few days
I found the fixes. They are already coming in the next update... ** Tags added: fixed-in-3.36.4 fixed-in-3.37.1 fixed-upstream ** Changed in: gnome-shell (Ubuntu) Assignee: Heewa Barfchin (heewa) => (unassigned) ** Changed in: gnome-shell (Ubuntu) Status: In Progress => Fix Committed -- 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/1885346 Title: gnome-shell-calendar-server leaks GBs of memory every few days Status in gnome-shell package in Ubuntu: Fix Committed Status in gnome-shell package in Debian: Unknown Bug description: It's been happening repeatedly over the last maybe week? I have to manually kill it about once a day, when I start to feel everything slow down as the OS starts to swap. Actually, I tracked down and fixed a few leaks in the code, and it looks stable so far. I'll submit a patch soon, as well as send the fix upstream to Gnome. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1885346/+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 1886812] Re: Mysterious image on first boot lock screen
** Changed in: gnome-shell (Ubuntu) Status: Opinion => Invalid ** Summary changed: - Mysterious image on first boot lock screen + Mysterious image on first boot lock screen when using Flat-Remix-Blue theme -- 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/1886812 Title: Mysterious image on first boot lock screen when using Flat-Remix-Blue theme Status in gnome-shell package in Ubuntu: Invalid Bug description: I'm using Ubuntu 20.04 and noticed a weird behavior. When I define the wallpaper image, ok, now is the same image for the lock screen and wallpaper, but on every first boot I get a mysterious image I don't know where is coming from. Is a beach or something. I already checked my images on home and even removed the wallpaper images from /usr, but the mysterious image is still there. Any tips how can I change it? Thanks! ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-5ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jul 8 08:41:59 2020 DisplayManager: gdm3 InstallationDate: Installed on 2018-03-05 (855 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) RelatedPackageVersions: mutter-common 3.36.3-0ubuntu0.20.04.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-05-09 (60 days ago) modified.conffile..etc.default.apport: [modified] mtime.conffile..etc.default.apport: 2018-03-12T07:12:03.188751 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1886812/+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 1885346] Re: gnome-shell-calendar-server leaks GBs of memory every few days
Sorry for the trouble. I'm trying to follow all the directions I find in several places across 3 organizations (Ubuntu, Gnome, Debian), plus asking people in 3 or 4 different Gnome & Ubuntu related IRC channels, but I'm not always sure what the right thing for to do is. That Gnome maintainer didn't ask me to do anything in relation to fixing this bug, did he? He mentioned that he backported changes that fixed the memory leaks. So the leaks are fixed on the 3.36 branch in the vendor repo. The reason I submitted a patch, however, is that Gnome hasn't cut a new release of the 3.36 branch with the backported fixes yet. So what should Ubuntu/Debian do about the memory leak in the meanwhile? From what I understand of Ubuntu & Debian's package maintenance practices, patches are created to fix bugs in upstream code until upstream releases fixes for them. Is that correct? I'm happy to do what Ubuntu would like in this situation. Please advise. -- 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/1885346 Title: gnome-shell-calendar-server leaks GBs of memory every few days Status in gnome-shell package in Ubuntu: In Progress Status in gnome-shell package in Debian: Unknown Bug description: It's been happening repeatedly over the last maybe week? I have to manually kill it about once a day, when I start to feel everything slow down as the OS starts to swap. Actually, I tracked down and fixed a few leaks in the code, and it looks stable so far. I'll submit a patch soon, as well as send the fix upstream to Gnome. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1885346/+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 1886869] Re: Double dock after screen lock.
That remaining issue sounds like bug 1882353. So please either use bug 1882353 or open a new bug for that issue by running: ubuntu-bug gnome-shell ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => 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/1886869 Title: Double dock after screen lock. Status in gnome-shell package in Ubuntu: Invalid Bug description: After locking my screen and unlocking, i see a double dock. The first one have the trash can icon and the main one doesn't. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..02.00.0: Error: [Errno 21] Es un directorio: '/proc/driver/nvidia/gpus/:02: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.100 Fri May 29 08:45:51 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2) ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 BootLog: Error: [Errno 13] Permiso denegado: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jul 8 15:27:41 2020 DistUpgraded: 2020-04-24 12:10:19,615 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Falló al ejecutar el proceso hijo «./xorg_fix_proprietary.py» (No existe el archivo o el directorio) (8)) DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 440.100, 5.4.0-39-generic, x86_64: installed nvidia, 440.100, 5.4.0-40-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Wani [Radeon R5/R6/R7 Graphics] [1002:9874] (rev e6) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Radeon R7 Graphics [1458:d000] NVIDIA Corporation GK208B [GeForce GT 710] [10de:128b] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd GK208B [GeForce GT 710] [1458:375a] InstallationDate: Installed on 2020-04-04 (94 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. ProcEnviron: LANGUAGE=es_MX:es PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_MX.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic root=UUID=acb80b2e-decc-41c3-b1b0-daa06a3b7465 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-04-24 (75 days ago) dmi.bios.date: 10/09/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: FD dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: F2A68HM-H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrFD:bd10/09/2018:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnF2A68HM-H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1 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+git20200226-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/gnome-shell/+bug/1886869/+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 1886729] Re: Dell displayport YJ3Y6 adapter doesn't drive 4K screen properly
If the same fundamental issue persists in Wayland sessions then it sounds like a hardware limitation or a kernel problem. To help identify which, the Mutter developers might have some suggestions so please report the issue here: https://gitlab.gnome.org/GNOME/mutter/issues ** Changed in: mutter (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/1886729 Title: Dell displayport YJ3Y6 adapter doesn't drive 4K screen properly Status in mutter package in Ubuntu: New Status in xorg-server package in Ubuntu: New Bug description: I have some early dell 4k 60hz screens - the ones which report 2 panels internally for DP 60Hz - horrid hack I know; I recently got a new XPS laptop and put Ubuntu on it. That XPS laptop has two USB-C/thunderbolt ports, so to drive the screens I bought two slightly different DP adapters - one with power passthrough, and a cheaper one that only does DP. The more expensive one 'USB-C to HDMI/DP' drives the monitor happily over DP, though sadly only at 30Hz - can't have everything :/. It reports one monitor as one output: DP-1 in the attached information: DP-1 connected 3840x2160+0+0 (normal left inverted right x axis y axis) 527mm x 296mm 3840x2160 29.98*+ 30.0029.97 1920x1200 59.88 ... The cheaper one reports the single monitor as two distinct outputs, at 60hz interestingly - DP-3-8 connected (normal left inverted right x axis y axis) 1920x2160 59.99 + DP-3-9 connected 1920x2160+7680+0 (normal left inverted right x axis y axis) 527mm x 296mm 1920x2160 59.99*+ 1920x1200 59.88 which in theory if summed together would be one whole screen. But attempting to configure the output results in an error: xrandr --output DP-1 --auto --left-of eDP-1 --output DP-3-9 --auto --right-of DP-3-8 --output DP-3-8 --auto --right-of eDP-1 xrandr: cannot find crtc for output DP-3-8 I'm not sure if this is an intrinsic limitation of the USB-C->DP dongle, or whether there is something that can be done in the software to deal with this 10 year old hardware hack I have sitting on my desktop. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jul 8 11:20:17 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Iris Plus Graphics G7 [8086:8a52] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell Iris Plus Graphics G7 [1028:096d] InstallationDate: Installed on 2020-07-07 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Dell Inc. XPS 13 9300 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/08/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.11 dmi.board.name: 0WX9VX dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.11:bd05/08/2020:svnDellInc.:pnXPS139300:pvr:rvnDellInc.:rn0WX9VX:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9300 dmi.product.sku: 096D dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1 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+git20200226-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/mutter/+bug/1886729/+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 1885346] Re: gnome-shell-calendar-server leaks GBs of memory every few days
Please follow the instructions of the gnome-shell maintainer here: https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/1335 -- 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/1885346 Title: gnome-shell-calendar-server leaks GBs of memory every few days Status in gnome-shell package in Ubuntu: In Progress Status in gnome-shell package in Debian: Unknown Bug description: It's been happening repeatedly over the last maybe week? I have to manually kill it about once a day, when I start to feel everything slow down as the OS starts to swap. Actually, I tracked down and fixed a few leaks in the code, and it looks stable so far. I'll submit a patch soon, as well as send the fix upstream to Gnome. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1885346/+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 1886075] Re: feature request: using mouse wheel like in XFce
Thanks. Please also request the feature upstream at: https://github.com/micheleg/dash-to-dock/issues and then tell us the new issue ID. ** Package changed: gnome-shell (Ubuntu) => gnome-shell-extension- ubuntu-dock (Ubuntu) ** Summary changed: - feature request: using mouse wheel like in XFce + Switch app windows using mouse wheel over dock icon ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1886075 Title: Switch app windows using mouse wheel over dock icon Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: New Bug description: Hello, this is not a BUG, rather a feature request, which possibly shall be placed elsewhere (where?) I'm used to very useful behavior from XFce and that is hovering over various icons in system bars and using the wheel actually performs actions immediately like e.g.: 1) in/decreasing volume while on sound icon 2) switching app windows while on app icon - would be extreme useful here in GNOME since more apps windows are already marked by small dots sou user is very aware that there are more windows... I know there is ALT+~ but when using mouse only its not an option... ... I've searched event through GNOME tweaks, but no luck - have not found it. Any way how to add this behavior? Thanks a lot #McZ ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.3-1ubuntu1~20.04.2 ProcVersionSignature: Ubuntu 5.4.0-39.43-generic 5.4.41 Uname: Linux 5.4.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Jul 2 19:02:17 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-06-19 (12 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) RelatedPackageVersions: mutter-common 3.36.3-0ubuntu0.20.04.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-extension-ubuntu-dock/+bug/1886075/+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 1879053] Re: Fractional Upscaling is descaling Certain Apps
** Changed in: mutter (Ubuntu) Status: New => Incomplete ** Changed in: wine (Ubuntu) Status: New => Incomplete -- 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/1879053 Title: Fractional Upscaling is descaling Certain Apps Status in mutter package in Ubuntu: Incomplete Status in wine package in Ubuntu: Incomplete Bug description: 1) Description: Ubuntu 20.04 LTS Release: 20.04 2) wine-development: Installed: 5.5-3ubuntu1 Candidate: 5.5-3ubuntu1 Same goes for wine stable 5.0. Other Packages foxit 2.4.4.xx, Notepad v7.8.6 3) I'm using a relatively small QHD Display. The Fractional Scaling Feature is really something I've looked forward to and I'm super grateful that it has been implemented. With my setup my life gets easier when having a little zoom but still have a good amount of pixels and nice sharpness on my workspace :D 4) With some apps the fractional scaling has an opposite effect. For example wine apps and foxit reader appear tiny with fractional scaling turned on (I'm using 125%) and the apps shrink compared to 100%. Is this the right place to report the bug or do i need to make a bugreport for every specific app? Kind regards, Tobi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1879053/+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 1880405] Re: High CPU and journal flooded with: JS ERROR: TypeError: null has no properties _onFocusChanged@resource:///org/gnome/shell/ui/closeDialog.js:135:9
^^^ Note the above command is only safe in Xorg sessions, NOT in Wayland sessions. -- 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/1880405 Title: High CPU and journal flooded with: JS ERROR: TypeError: null has no properties _onFocusChanged@resource:///org/gnome/shell/ui/closeDialog.js:135:9 Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Triaged Bug description: O.k. it is an old Lenovo thinkpad T410. However, in 18.04, 19.04 and 19.10 I did face these problems. The sometimes I have to wait 10 seconds to see if a window reacts or not. It is hard to use. Installiert: 3.36.1-5ubuntu2 Installationskandidat: 3.36.2-1ubuntu1~20.04.1 Versionstabelle: 3.36.2-1ubuntu1~20.04.1 500 500 http://it.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages *** 3.36.1-5ubuntu2 100 100 /var/lib/dpkg/status 3.36.1-5ubuntu1 500 500 http://it.archive.ubuntu.com/ubuntu focal/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-5ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME-Classic:GNOME Date: Sun May 24 15:43:34 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-02-05 (109 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1~20.04.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-05-08 (15 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1880405/+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 1877774] Re: gnome-shell crashed with SIGSEGV in _st_theme_node_ensure_background() from st_theme_node_paint_equal() from st_widget_recompute_style() from st_widget_style_chang
Brendan_P, This bug is closed. Please put all further comments in bug 1886672 only. -- 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/184 Title: gnome-shell crashed with SIGSEGV in _st_theme_node_ensure_background() from st_theme_node_paint_equal() from st_widget_recompute_style() from st_widget_style_changed() [when locking the screen] [usually due to dash-to-panel] Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell source package in Focal: Fix Released Bug description: [ Impact ] GNOME shell crashes on extensions loading / updates [ Test case ] - No clear test case, normally may happen during screen locking/unlocking - But crashes should be monitored at https://errors.ubuntu.com/problem/4127e7e714fd28c090da0220de2ff06e71274eda [ Regression potential ] Stylesheet memory could be leaked --- Seems to be reproducible Suspend the computer Start the computer from suspend Start chrome gmail. Has happened two times ProblemType: CrashDistroRelease: Ubuntu 20.10 Package: gnome-shell 3.36.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu33 Architecture: amd64 CasperMD5CheckResult: skip CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Sat May 9 20:00:47 2020 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2020-04-16 (23 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200415.2) ProcCmdline: /usr/bin/gnome-shell RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1 SegvAnalysis: Segfault happened at: 0x7fe1b40c4252 <_st_theme_node_ensure_background+226>: mov(%rax),%r12 PC (0x7fe1b40c4252) ok source "(%rax)" (0x) not located in a known VMA region (needed readable region)! destination "%r12" ok SegvReason: reading NULL VMA Signal: 11SourcePackage: gnome-shell StacktraceTop: _st_theme_node_ensure_background () from /usr/lib/gnome-shell/libst-1.0.so st_theme_node_paint_equal () from /usr/lib/gnome-shell/libst-1.0.so ?? () from /usr/lib/gnome-shell/libst-1.0.so st_widget_style_changed () from /usr/lib/gnome-shell/libst-1.0.so ?? () from /usr/lib/gnome-shell/libst-1.0.so Title: gnome-shell crashed with SIGSEGV in _st_theme_node_ensure_background() 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/gnome-shell/+bug/184/+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 1876530] Re: Screen scales to grandma very unfriendly mode
*** This bug is a duplicate of bug 1875285 *** https://bugs.launchpad.net/bugs/1875285 The data from the original reporter in comment #3 shows this is bug 1875285. ** This bug has been marked a duplicate of bug 1875285 Fractional scaling zooms to 200% and crops half the screen -- 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/1876530 Title: Screen scales to grandma very unfriendly mode Status in mutter package in Ubuntu: Incomplete Bug description: When fractional scaling is active and set to 125% (I only tested this with 125%) and then the switch for fractional scaling is deactivated again, the screen scales well beyond the standard (and selected) 100%. Feels like 50% or less. This issue is removed when rebooting. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun May 3 00:35:53 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. UHD Graphics 620 (Whiskey Lake) [1043:16a1] InstallationDate: Installed on 2020-04-30 (2 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f3:0903 Elan Microelectronics Corp. ELAN:Fingerprint Bus 001 Device 002: ID 13d3:56dc IMC Networks USB2.0 HD UVC WebCam Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. ZenBook UX392FA_UX392FA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-28-generic root=UUID=cbcf9a35-a5f8-429f-adad-ad8f21bff5df ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/17/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX392FA.301 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX392FA 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.:bvrUX392FA.301:bd07/17/2019:svnASUSTeKCOMPUTERINC.:pnZenBookUX392FA_UX392FA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX392FA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: ZenBook UX392FA_UX392FA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 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+git20200226-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/mutter/+bug/1876530/+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 1886672] Re: Multiple screen display issues
This bug has now been reopened. Please try to reword it into a simple description of a single problem. ** This bug is no longer a duplicate of bug 184 gnome-shell crashed with SIGSEGV in _st_theme_node_ensure_background() from st_theme_node_paint_equal() from st_widget_recompute_style() from st_widget_style_changed() [when locking the screen] [usually due to dash-to-panel] -- 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/1886672 Title: Multiple screen display issues Status in gnome-shell package in Ubuntu: Incomplete Bug description: New bug for me. Issue was fine till last week. I think this may be related to the following as it started happening shortly thereafter. I have XPS13 with second monitor, all working fine till I lock screen or suspend. Then my second monitor will not 'resume'. I.e. stays off. This behaviour started after (or shortly after) playing a wine game using Lutris to launch. Shutting game down and almost immediately hitting suspend on the laptop. Was rushing out. It's a wild shot in the dark but I think something got messed up / not saved correctly in this process. To get it working I need to unplug monitor (using USB-C > HDMI) > suspend > plug in monitor > resume and sometimes still need to open display settings before it 'kicks in'. Damn annoying. Hope someone can help :) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME Date: Tue Jul 7 16:44:52 2020 DistUpgraded: 2020-05-15 15:17:42,708 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 [1028:082a] InstallationDate: Installed on 2019-01-29 (525 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Dell Inc. XPS 13 9360 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-05-15 (53 days ago) dmi.bios.date: 11/14/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.13.0 dmi.board.name: 0PVG6D dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.13.0:bd11/14/2019:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn0PVG6D:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9360 dmi.product.sku: 082A dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1 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+git20200226-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/gnome-shell/+bug/1886672/+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 1857191] Re: Dark themes don't work well with highlighted current line in gedit
** This bug is no longer a duplicate of bug 1887311 Active line is unreadable in case of dark theme ** This bug has been marked a duplicate of bug 1812663 Background Color And Text Color Both Wite with Dark Theme ** This bug is no longer a duplicate of bug 1812663 Background Color And Text Color Both White with Dark Theme -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to yaru-theme in Ubuntu. https://bugs.launchpad.net/bugs/1857191 Title: Dark themes don't work well with highlighted current line in gedit Status in GtkSourceView: New Status in gtksourceview4 package in Ubuntu: Triaged Status in yaru-theme package in Ubuntu: Confirmed Bug description: In order to checkout out an old bug report I started gedit, enabled "Highlight current line" and changed the application theme to "Yaru- dark" The current line is highlighted correctly but the text is unreadable because it is too light. The text needs to be much darker. This is not a theme that I would normally use so I'm not too bothered about how the problem is fixed but this configuration makes gedit very difficult to use as you can't actually see the text that you're adding, changing or deleting. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: yaru-theme-gtk 19.10.4 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CurrentDesktop: GNOME Date: Sat Dec 21 16:33:03 2019 InstallationDate: Installed on 2019-05-17 (218 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190517) PackageArchitecture: all SourcePackage: yaru-theme UpgradeStatus: Upgraded to focal on 2019-11-08 (42 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gtksourceview/+bug/1857191/+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 1865457] Re: gedit tango color scheme display ugly white grid pattern
*** This bug is a duplicate of bug 1857191 *** https://bugs.launchpad.net/bugs/1857191 ** This bug is no longer a duplicate of bug 1887311 Active line is unreadable in case of dark theme ** This bug has been marked a duplicate of bug 1812663 Background Color And Text Color Both Wite with Dark Theme ** This bug is no longer a duplicate of bug 1812663 Background Color And Text Color Both White with Dark Theme ** This bug has been marked a duplicate of bug 1857191 Dark themes don't work well with highlighted current line in gedit -- 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/1865457 Title: gedit tango color scheme display ugly white grid pattern Status in gedit package in Ubuntu: New Bug description: - launch gedit - in the three lines "burger" menu, select "Preferences" - in "View" tab, activate "Display grid pattern" option - in "Font & Colors" tab, select "/* Tango */" From now on, a uggly white grid covers the surface of the editing area. Shouldn't this dark theme display a dark grid as well ? ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gedit 3.35.90-1 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Mar 2 11:09:04 2020 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: gedit UpgradeStatus: Upgraded to focal on 2018-11-14 (473 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1865457/+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 1812663] Re: Background Color And Text Color Both Wite with Dark Theme
*** This bug is a duplicate of bug 1857191 *** https://bugs.launchpad.net/bugs/1857191 ** Tags added: focal ** This bug is no longer a duplicate of bug 1887311 Active line is unreadable in case of dark theme ** Summary changed: - Background Color And Text Color Both Wite with Dark Theme + Background Color And Text Color Both White with Dark Theme ** This bug has been marked a duplicate of bug 1857191 Dark themes don't work well with highlighted current line in gedit -- 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/1812663 Title: Background Color And Text Color Both White with Dark Theme Status in gedit package in Ubuntu: Confirmed Bug description: The background color and the text color are both white when using the dark layout. $ cat .config/gtk-3.0/settings.ini [Settings] gtk-application-prefer-dark-theme=1 ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gedit 3.30.2-0ubuntu0.18.10.2 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Jan 21 13:01:50 2019 InstallationDate: Installed on 2017-12-15 (402 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) SourcePackage: gedit UpgradeStatus: Upgraded to cosmic on 2018-10-24 (88 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1812663/+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 1867819] Re: Dark theme current line highlight hard to read
*** This bug is a duplicate of bug 1857191 *** https://bugs.launchpad.net/bugs/1857191 ** This bug is no longer a duplicate of bug 1887311 Active line is unreadable in case of dark theme ** This bug has been marked a duplicate of bug 1812663 Background Color And Text Color Both Wite with Dark Theme ** This bug is no longer a duplicate of bug 1812663 Background Color And Text Color Both White with Dark Theme ** This bug has been marked a duplicate of bug 1857191 Dark themes don't work well with highlighted current line in gedit -- 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/1867819 Title: Dark theme current line highlight hard to read Status in gedit package in Ubuntu: New Bug description: In focal, with a dark theme (adwaita-dark), the current line highlight in almost the same color as the text, making it very hard to read. see screenshot. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gedit 3.36.0-3 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Mar 17 11:28:29 2020 InstallationDate: Installed on 2019-08-17 (213 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1) SourcePackage: gedit UpgradeStatus: Upgraded to focal on 2020-03-06 (11 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1867819/+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 1875277] Re: Active|Focused line in the dark mode is unreadable. Highliht and font color are almost the same.
*** This bug is a duplicate of bug 1857191 *** https://bugs.launchpad.net/bugs/1857191 ** This bug is no longer a duplicate of bug 1887311 Active line is unreadable in case of dark theme ** This bug has been marked a duplicate of bug 1812663 Background Color And Text Color Both Wite with Dark Theme ** This bug is no longer a duplicate of bug 1812663 Background Color And Text Color Both White with Dark Theme ** This bug has been marked a duplicate of bug 1857191 Dark themes don't work well with highlighted current line in gedit -- 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/1875277 Title: Active|Focused line in the dark mode is unreadable. Highliht and font color are almost the same. Status in gedit package in Ubuntu: New Bug description: Active|Focused line in the dark mode is unreadable. Highliht and font color are almost the same. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gedit 3.36.1-1 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Apr 27 06:07:07 2020 InstallationDate: Installed on 2020-04-25 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: gedit UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1875277/+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 1877841] Re: with the dark theme, the active line is highlighted and I cannot see the text I am typing.
*** This bug is a duplicate of bug 1857191 *** https://bugs.launchpad.net/bugs/1857191 ** This bug is no longer a duplicate of bug 1887311 Active line is unreadable in case of dark theme ** This bug has been marked a duplicate of bug 1812663 Background Color And Text Color Both Wite with Dark Theme ** This bug is no longer a duplicate of bug 1812663 Background Color And Text Color Both White with Dark Theme ** This bug has been marked a duplicate of bug 1857191 Dark themes don't work well with highlighted current line in gedit -- 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/1877841 Title: with the dark theme, the active line is highlighted and I cannot see the text I am typing. Status in gedit package in Ubuntu: New Bug description: 1) Release: 20.04 2) Version: 3.36.1-1 3) Expected: I have the Dark theme on. On opening Gedit, the active line is all white. When I typed, I expected to see letters. 4) What happened: Nothing appeared. I thought it had locked up. I tapped on the Enter key and it went to the next line, revealing the text I had typed on the previously active line. So, it seems like with Dark theme on the text is white and same as the highlight. When I switched back to Standard theme, no problems. The text was black, the blank space is white and the highlight is slightly off-white (beige maybe, not good with the naming of colors). It's perfectly legible. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gedit 3.36.1-1 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun May 10 17:35:24 2020 ExecutablePath: /usr/bin/gedit InstallationDate: Installed on 2020-05-10 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANGUAGE=en_PH:en LANG=en_PH.UTF-8 SourcePackage: gedit UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1877841/+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 1879406] Re: Dark mode on gedit - unable to see text
*** This bug is a duplicate of bug 1857191 *** https://bugs.launchpad.net/bugs/1857191 ** This bug is no longer a duplicate of bug 1887311 Active line is unreadable in case of dark theme ** This bug has been marked a duplicate of bug 1812663 Background Color And Text Color Both Wite with Dark Theme ** This bug is no longer a duplicate of bug 1812663 Background Color And Text Color Both White with Dark Theme ** This bug has been marked a duplicate of bug 1857191 Dark themes don't work well with highlighted current line in gedit -- 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/1879406 Title: Dark mode on gedit - unable to see text Status in gedit package in Ubuntu: New Bug description: Unable to see current line of text on gedit when in dark mode and with default gedit setting to highlight current line. Highilght is the same colour as the text. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gedit 3.36.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon May 18 22:20:55 2020 InstallationDate: Installed on 2020-05-17 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: gedit UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1879406/+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 1887311] Re: Active line is unreadable in case of dark theme
*** This bug is a duplicate of bug 1857191 *** https://bugs.launchpad.net/bugs/1857191 ** This bug has been marked a duplicate of bug 1812663 Background Color And Text Color Both Wite with Dark Theme ** This bug is no longer a duplicate of bug 1812663 Background Color And Text Color Both White with Dark Theme ** This bug has been marked a duplicate of bug 1857191 Dark themes don't work well with highlighted current line in gedit -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtksourceview4 in Ubuntu. https://bugs.launchpad.net/bugs/1887311 Title: Active line is unreadable in case of dark theme Status in gtksourceview4 package in Ubuntu: Confirmed Bug description: Hello, The active line is unreadable on ubuntu 20.04 with the default dark themes. I assume that modify the /usr/share/gtksourceview-4/styles/tango.xml (in repo: gtksourceview4/data/styles/tango.xml) with the following from: to a less harsch colour: at line #49. Thank's in advance, cociweb ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libgtksourceview-4-0 4.6.0-1 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jul 12 23:16:41 2020 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=hu_HU.UTF-8 SHELL=/bin/bash SourcePackage: gtksourceview4 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtksourceview4/+bug/1887311/+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 1870443] Re: white fonts on white background on highlighted line in gedit with dark-theme
*** This bug is a duplicate of bug 1857191 *** https://bugs.launchpad.net/bugs/1857191 ** This bug is no longer a duplicate of bug 1887311 Active line is unreadable in case of dark theme ** This bug has been marked a duplicate of bug 1812663 Background Color And Text Color Both Wite with Dark Theme ** This bug is no longer a duplicate of bug 1812663 Background Color And Text Color Both White with Dark Theme ** This bug has been marked a duplicate of bug 1857191 Dark themes don't work well with highlighted current line in gedit -- 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/1870443 Title: white fonts on white background on highlighted line in gedit with dark-theme Status in gedit package in Ubuntu: New Bug description: Gedit with Ubuntu Dark-Theme and Tango shows white fonts on white background when the line is highlighted (current line). Attached image exemplifies it. The expected behaviour is to have a darker background with white fonts, or darker fonts with white background. To fix it i had to change Gedit's Color Scheme or disabling "Highlight current line". ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gedit 3.36.1-1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Apr 2 19:27:57 2020 InstallationDate: Installed on 2020-04-02 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401) SourcePackage: gedit UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1870443/+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 1875018] Re: Current/selected line text is barely visible when using yaru-dark
*** This bug is a duplicate of bug 1857191 *** https://bugs.launchpad.net/bugs/1857191 ** This bug is no longer a duplicate of bug 1887311 Active line is unreadable in case of dark theme ** This bug has been marked a duplicate of bug 1812663 Background Color And Text Color Both Wite with Dark Theme ** This bug is no longer a duplicate of bug 1812663 Background Color And Text Color Both White with Dark Theme ** This bug has been marked a duplicate of bug 1857191 Dark themes don't work well with highlighted current line in gedit -- 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/1875018 Title: Current/selected line text is barely visible when using yaru-dark Status in gedit package in Ubuntu: New Bug description: I am currently using Ubuntu 20.04 with the dark theme (yaru-dark). I have gedit configured to highlight current line. Using yaru and yaru-light this works well, but when using yaru-dark the current line is highlighted with almost white color, masking the white text which become barely visible. See attached screenshot. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gedit 3.36.1-1 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Apr 25 10:16:28 2020 SourcePackage: gedit UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1875018/+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 1884124] Re: Text Editor (geditunusable with yaru-dark
*** This bug is a duplicate of bug 1857191 *** https://bugs.launchpad.net/bugs/1857191 ** This bug is no longer a duplicate of bug 1887311 Active line is unreadable in case of dark theme ** This bug has been marked a duplicate of bug 1812663 Background Color And Text Color Both Wite with Dark Theme ** This bug is no longer a duplicate of bug 1812663 Background Color And Text Color Both White with Dark Theme ** This bug has been marked a duplicate of bug 1857191 Dark themes don't work well with highlighted current line in gedit -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to yaru-theme in Ubuntu. https://bugs.launchpad.net/bugs/1884124 Title: Text Editor (geditunusable with yaru-dark Status in yaru-theme package in Ubuntu: New Bug description: 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu Description: Ubuntu 20.04 LTS Release: 20.04 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center gedit: Installed: 3.36.2-0ubuntu1 Candidate: 3.36.2-0ubuntu1 Version table: *** 3.36.2-0ubuntu1 500 500 http://ca.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.36.1-1 500 500 http://ca.archive.ubuntu.com/ubuntu focal/main amd64 Packages 3) What you expected to happen gedit/Text Editor to look nice and usable in yaru-dark (Settings > Appearance > Dark) 4) What happened instead Highlighted line is unreadable. It highlights in white but the text is very light gray! The cursor is almost impossible to see as well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yaru-theme/+bug/1884124/+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 1873930] Re: White line with white font on current active line with dark Yaru theme
*** This bug is a duplicate of bug 1857191 *** https://bugs.launchpad.net/bugs/1857191 ** This bug is no longer a duplicate of bug 1887311 Active line is unreadable in case of dark theme ** This bug has been marked a duplicate of bug 1812663 Background Color And Text Color Both Wite with Dark Theme ** This bug is no longer a duplicate of bug 1812663 Background Color And Text Color Both White with Dark Theme ** This bug has been marked a duplicate of bug 1857191 Dark themes don't work well with highlighted current line in gedit -- 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/1873930 Title: White line with white font on current active line with dark Yaru theme Status in gedit package in Ubuntu: Confirmed Bug description: The active line is white with white font since upgrade to focal. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gedit 3.36.1-1 ProcVersionSignature: Ubuntu 5.4.0-25.29-lowlatency 5.4.30 Uname: Linux 5.4.0-25-lowlatency x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Apr 20 21:14:33 2020 InstallationDate: Installed on 2020-02-08 (72 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: gedit UpgradeStatus: Upgraded to focal on 2020-04-20 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1873930/+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 1870393] Re: Poor contrast in some applications
*** This bug is a duplicate of bug 1857191 *** https://bugs.launchpad.net/bugs/1857191 ** This bug is no longer a duplicate of bug 1887311 Active line is unreadable in case of dark theme ** This bug has been marked a duplicate of bug 1812663 Background Color And Text Color Both Wite with Dark Theme ** This bug is no longer a duplicate of bug 1812663 Background Color And Text Color Both White with Dark Theme ** This bug has been marked a duplicate of bug 1857191 Dark themes don't work well with highlighted current line in gedit -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to yaru-theme in Ubuntu. https://bugs.launchpad.net/bugs/1870393 Title: Poor contrast in some applications Status in yaru-theme package in Ubuntu: New Bug description: In some applications the contrast between the background and text colour is very poor when using the Yaru theme in "Dark Mode". For example, If the theme is set to Dark via the settings application under "Appearance" and gedit (GNOME Text Editor" is launched. The background of the line the cursor is on is light very similar to the text colour. I've attached a screenshot. In the "Standard" mode the theme subtly highlights the current line. But this is not the case for the "Dark" mode. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: yaru-theme-gtk 20.04.4 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Apr 2 17:46:15 2020 InstallationDate: Installed on 2020-03-20 (12 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200320) PackageArchitecture: all SourcePackage: yaru-theme UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yaru-theme/+bug/1870393/+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 1877876] Re: white line at gedit with the dark windows skin
*** This bug is a duplicate of bug 1857191 *** https://bugs.launchpad.net/bugs/1857191 ** This bug is no longer a duplicate of bug 1887311 Active line is unreadable in case of dark theme ** This bug has been marked a duplicate of bug 1812663 Background Color And Text Color Both Wite with Dark Theme ** This bug is no longer a duplicate of bug 1812663 Background Color And Text Color Both White with Dark Theme ** This bug has been marked a duplicate of bug 1857191 Dark themes don't work well with highlighted current line in gedit -- 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/1877876 Title: white line at gedit with the dark windows skin Status in gedit package in Ubuntu: New Bug description: With the dark window skin enabled type marker in gedit turns into a white line, so you can't see what your typing. Description: Ubuntu 20.04 LTS Release: 20.04 gedit: Geïnstalleerd: 3.36.1-1 Kandidaat: 3.36.1-1 Versietabel: *** 3.36.1-1 500 500 http://nl.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1877876/+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 1871068] Re: Gedit current line highlighting doesn't play well with Yaru-dark
*** This bug is a duplicate of bug 1857191 *** https://bugs.launchpad.net/bugs/1857191 ** This bug is no longer a duplicate of bug 1887311 Active line is unreadable in case of dark theme ** This bug has been marked a duplicate of bug 1812663 Background Color And Text Color Both Wite with Dark Theme ** This bug is no longer a duplicate of bug 1812663 Background Color And Text Color Both White with Dark Theme ** This bug has been marked a duplicate of bug 1857191 Dark themes don't work well with highlighted current line in gedit -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to yaru-theme in Ubuntu. https://bugs.launchpad.net/bugs/1871068 Title: Gedit current line highlighting doesn't play well with Yaru-dark Status in yaru-theme package in Ubuntu: New Bug description: By default, gedit has "Highlight current line" option enabled. While that works great for Yaru and Adwaita, this is barely usable with Yaru-dark, because both background and foreground are just different shades of white. While this is a minor issue and can be easily fixed by adjusting gedit's color scheme, that might give not the best impression for a first-time Ubuntu user. apt policy gedit gedit: Installed: 3.36.1-1 Candidate: 3.36.1-1 Version table: *** 3.36.1-1 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status apt policy yaru-theme-gtk yaru-theme-gtk: Installed: 20.04.4 Candidate: 20.04.4 Version table: *** 20.04.4 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu focal/main i386 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: yaru-theme-gtk 20.04.4 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Apr 6 11:43:32 2020 InstallationDate: Installed on 2019-11-07 (150 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) PackageArchitecture: all SourcePackage: yaru-theme UpgradeStatus: Upgraded to focal on 2020-03-04 (32 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yaru-theme/+bug/1871068/+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 1879886] Re: Current line background color doesn't respect system dark theme
*** This bug is a duplicate of bug 1857191 *** https://bugs.launchpad.net/bugs/1857191 ** This bug is no longer a duplicate of bug 1887311 Active line is unreadable in case of dark theme ** This bug has been marked a duplicate of bug 1812663 Background Color And Text Color Both Wite with Dark Theme ** This bug is no longer a duplicate of bug 1812663 Background Color And Text Color Both White with Dark Theme ** This bug has been marked a duplicate of bug 1857191 Dark themes don't work well with highlighted current line in gedit -- 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/1879886 Title: Current line background color doesn't respect system dark theme Status in gedit package in Ubuntu: New Bug description: On Ubuntu 20.04 with a dark theme in gedit current line background color is bright white, while the rest of the background is dark grey. White font color on white background is 100% unreadable. gedit: Installed: 3.36.2-0ubuntu1 Candidate: 3.36.2-0ubuntu1 Version table: *** 3.36.2-0ubuntu1 500 500 http://at.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.36.1-1 500 500 http://at.archive.ubuntu.com/ubuntu focal/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gedit 3.36.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu May 21 08:51:28 2020 InstallationDate: Installed on 2020-04-24 (27 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: gedit UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1879886/+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 1872370] Re: gedit current line is illegibly highlighted on Breeze-Dark theme
*** This bug is a duplicate of bug 1857191 *** https://bugs.launchpad.net/bugs/1857191 ** This bug is no longer a duplicate of bug 1887311 Active line is unreadable in case of dark theme ** This bug has been marked a duplicate of bug 1812663 Background Color And Text Color Both Wite with Dark Theme ** This bug is no longer a duplicate of bug 1812663 Background Color And Text Color Both White with Dark Theme ** This bug has been marked a duplicate of bug 1857191 Dark themes don't work well with highlighted current line in gedit -- 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/1872370 Title: gedit current line is illegibly highlighted on Breeze-Dark theme Status in gedit package in Ubuntu: New Bug description: When gedit is launched in KDE with the Breeze-Dark theme active, the line with the cursor is highlighted white even though the text is white. This makes it impossible to read the text. "lsb_release -rd": Description:Ubuntu Focal Fossa (development branch) Release:20.04 "apt-cache policy gedit" gedit: Installed: 3.36.1-1 Candidate: 3.36.1-1 Version table: *** 3.36.1-1 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status "apt-cache policy kde-config-gtk-style" kde-config-gtk-style: Installed: 4:5.18.4.1-0ubuntu1 Candidate: 4:5.18.4.1-0ubuntu1 Version table: *** 4:5.18.4.1-0ubuntu1 500 500 http://archive.ubuntu.com/ubuntu focal/universe amd64 Packages 100 /var/lib/dpkg/status "apt-cache policy breeze-gtk-theme" breeze-gtk-theme: Installed: 5.18.4.1-0ubuntu1 Candidate: 5.18.4.1-0ubuntu1 Version table: *** 5.18.4.1-0ubuntu1 500 500 http://archive.ubuntu.com/ubuntu focal/universe amd64 Packages 100 /var/lib/dpkg/status Procedure: 1. Spin up a VirtualBox VM 2. Insert http://cdimage.ubuntu.com/kubuntu/daily-live/20200412/focal-desktop-amd64.iso as the CD 3. Click on "Try Kubuntu" 4. Open Konsole 5. Run "sudo apt install gedit" 6. Open System Settings 7. Go into "Global Theme" 8. Select "Breeze Dark" 9. Click "Apply" 10. Click the home icon 11. Go into "Application Style" 12. Click "Configure GNOME/GTK Application Style" 13. Set both the "GTK2 theme" and "GTK3 theme" dropdowns to "Breeze-Dark" 14. Click "Apply" 15. Open gedit 16. Type some text Expected behavior: To be able to read the line I'm typing on. This was the behavior before Ubuntu 20.04 unified GTK and Qt themes. While restoring the behavior would be better than having completely illegible text, it would be preferred to get gedit and the Breeze-Dark theme to actually work together. Actual behavior: The current line is illegible. The line is highlighted white even though the text is white. A screenshot of this behavior is attached. Workaround: Move the cursor to another line before trying to read the text, or select the text before trying to read it. This workaround is very annoying. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1872370/+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 1887222] Re: Plugins bundled with Rhythmbox link to for-sale domain
** Information type changed from Private Security to Public Security ** Summary changed: - Plugins bundled with Rhythmbox link to for-sale domain + Plugins bundled with Rhythmbox link to for-sale domain (rhythmbox.org has been drop-caught) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/1887222 Title: Plugins bundled with Rhythmbox link to for-sale domain (rhythmbox.org has been drop-caught) Status in rhythmbox package in Ubuntu: New Bug description: Plugins bundled with Rhythmbox including "Cover Art Search", "FM Radio", and "Python Console" still link to http://www.rhythmbox.org/. Although http://www.rhythmbox.org/ used to redirect to https://wiki.gnome.org/Apps/Rhythmbox (source: https://web.archive.org/web/20200122080148/http://www.rhythmbox.org/), it now redirects to https://www.dropcatch.com/domain/rhythmbox.org, a site that appears to be selling the domain. Note: This is my first bug report! I apologize for attaching files that aren't relevant -- I'm still figuring this out! Most relevant is the PNG attatchment, bugReport.png. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: rhythmbox 3.4.4-1ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jul 11 02:02:53 2020 ExecutablePath: /usr/bin/rhythmbox InstallationDate: Installed on 2020-03-24 (109 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, user) LANG=en_US.UTF-8 SourcePackage: rhythmbox UpgradeStatus: Upgraded to focal on 2020-06-19 (22 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1887222/+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 938751] Re: Images are washed out or colors are skewed in some apps (particularly Image Viewer and Chrome)
That flag is still available in Chrome at least :) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/938751 Title: Images are washed out or colors are skewed in some apps (particularly Image Viewer and Chrome) Status in Eye of GNOME: New Status in GNOME Shell: Unknown Status in chromium-browser package in Ubuntu: Confirmed Status in colord package in Ubuntu: Confirmed Status in eog package in Ubuntu: Confirmed Status in inkscape package in Ubuntu: Confirmed Bug description: Images are washed out or colors are skewed in some apps, notably Chrome/Chromium and Image Viewer (eog). Workaround: Settings > Devices > Colour > and disable or remove your monitor's colour profile To manage notifications about this bug go to: https://bugs.launchpad.net/eog/+bug/938751/+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 1873052] Re: GNOME 3.36 Lands Scaled/Transformed Hardware Cursors Support and keeps another not scaled cursor mid screen
Note there are two related upstream bugs: https://gitlab.gnome.org/GNOME/mutter/-/issues/1108 https://gitlab.gnome.org/GNOME/mutter/-/issues/1165 But those are only on resume from suspend and not related to fractional scaling. ** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #1108 https://gitlab.gnome.org/GNOME/mutter/-/issues/1108 ** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #1165 https://gitlab.gnome.org/GNOME/mutter/-/issues/1165 -- 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/1873052 Title: GNOME 3.36 Lands Scaled/Transformed Hardware Cursors Support and keeps another not scaled cursor mid screen Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: In Progress Bug description: Showing two cursors after login to ubuntu-desktop. One cursor moves and is scaled, and one is stationary mid screen and not scaled. The moving cursor does not appear on screenshots, making it difficult to upload a screenshot. Previously reported: https://gitlab.gnome.org/GNOME/mutter/issues/904 https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1827428 Package: mutter 3.36.1-3ubuntu1 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-4ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Apr 15 20:06:53 2020 DisplayManager: gdm3 RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-03-31 (15 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1873052/+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 1882309] Re: Cutted off font on Facebook in Firefox
Whole facebook use font Nimbus Sans (NimbusSans-Regular) but cutted off text is merely at 12px font size. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1882309 Title: Cutted off font on Facebook in Firefox Status in Mozilla Firefox: New Status in firefox package in Ubuntu: New Bug description: The domain of site is cutted off on Facebook site as it is seen on this screenshot. https://i.postimg.cc/44Bt3H7j/Zrzut-ekranu-z-2020-06-06-00-07-36.png I've seen this problem in Ubuntu 20.04 and I haven't seen in Ubuntu 19.10. This issue is merely in Firefox. Facebook site in Google Chrome looks ok. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: firefox 77.0.1+build1-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: konrad 1159 F pulseaudio /dev/snd/pcmC1D0p: konrad 1159 F...m pulseaudio /dev/snd/controlC0: konrad 1159 F pulseaudio BuildID: 2020060727 CasperMD5CheckResult: skip Channel: Unavailable CurrentDesktop: MATE Date: Sat Jun 6 00:05:28 2020 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:731 DefaultProfilePrefSources: /usr/lib/firefox/defaults/pref/all-ubuntumate.js DefaultProfileThemes: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) # Include files from /etc/network/interfaces.d: source-directory /etc/network/interfaces.d InstallationDate: Installed on 2020-06-05 (0 days ago) InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IpRoute: default via 192.168.0.1 dev wlp2s0 proto dhcp metric 600 169.254.0.0/16 dev wlp2s0 scope link metric 1000 192.168.0.0/24 dev wlp2s0 proto kernel scope link src 192.168.0.8 metric 600 Profile0Extensions: extensions.sqlite corrupt or missing Profile0IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile0Locales: extensions.sqlite corrupt or missing Profile0PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:731 Profile0PrefSources: /usr/lib/firefox/defaults/pref/all-ubuntumate.js prefs.js Profile0Themes: extensions.sqlite corrupt or missing Profiles: Profile1 (Default) - LastVersion=None/None (Out of date) Profile0 - LastVersion=77.0.1/2020060727 (In use) RunningIncompatibleAddons: False SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/25/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: A23 dmi.board.name: 0V8RX3 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA23:bd11/25/2019:svnDellInc.:pnLatitudeE7250:pvr:rvnDellInc.:rn0V8RX3:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E7250 dmi.product.sku: 062D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1882309/+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 1887311] Re: Active line is unreadable in case of dark theme
The attachment "tango.patch" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.] ** Tags added: patch -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtksourceview4 in Ubuntu. https://bugs.launchpad.net/bugs/1887311 Title: Active line is unreadable in case of dark theme Status in gtksourceview4 package in Ubuntu: Confirmed Bug description: Hello, The active line is unreadable on ubuntu 20.04 with the default dark themes. I assume that modify the /usr/share/gtksourceview-4/styles/tango.xml (in repo: gtksourceview4/data/styles/tango.xml) with the following from: to a less harsch colour: at line #49. Thank's in advance, cociweb ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libgtksourceview-4-0 4.6.0-1 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jul 12 23:16:41 2020 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=hu_HU.UTF-8 SHELL=/bin/bash SourcePackage: gtksourceview4 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtksourceview4/+bug/1887311/+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 1887315] Re: Nautilus crashes while over-typing search term on remote smb file system
Another way to type into the search field over a remote share that makes nautilus crash: type the first character (incorrectly), backspace, then re-type. -- 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/1887315 Title: Nautilus crashes while over-typing search term on remote smb file system Status in nautilus package in Ubuntu: New Bug description: ==Impact== nautilus crashes while typing the term to search a remote directory within an NT file system over the smb protocol. The problem may affect other remote file systems or protocols, but I have only tested these. Repeatable. ==How to repeat== 1. Open Nautilus 2. In the sidebar, click Other Locations 3. Type smb://example/share into the 'Connect to server' field or select an existing share URI 4. Click Connect 5. Optionally, when the contents of the share appears, select any depth of sub-directories. 6. Click the search icon and type a search string 7. Once the search results have returned, without closing the search box, select the previous search term and over-type another search term. Nautilus crashes. Typically, prior to the window disappearing the graphics freezes within the search field showing both the previous and the current search terms on top of each other. Often it is necessary to kill the nautilus process and/or reboot the smb daemon on the remote machine before being able to use the smb share again. Before typing a second search term, if instead of over-typing, you delete the selection either i) with the key; or ii) clicking the (x) to clear the field; or iii) clicking the search icon twice to remove and reinstate the search field; it is possible to search for a second term without crashing. It is possible that the crash depends on how fast the search term is typed, because nautilus starts searching as you type. I have tried to paste a search term over an existing term, which usually seems to work without crashing. On the other hand, I have had nautilus crash when typing a search term after having explicitly cleared the search field, but before nautilus has displayed the full contents of the directory again (about 150 files). I have not had nautilus crash when over-typing the search field for a local file system, whether ntfs or ext3. ==Related bugs== Bug #1795028 seems to be identical, and claims to have been fixed in package nautilus - 1:3.26.4-0~ubuntu18.04.2 but it does not appear to be fixed in 3.36.3 under Ubuntu 20.04. Hopefully this report explains more precisely how to reproduce the crash. ==Crash Reports== A typical crash report from my system is here: https://errors.ubuntu.com/oops/2dd9aa90-c462-11ea-9e47-fa163e102db1 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.36.3-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jul 12 21:03:59 2020 InstallationDate: Installed on 2020-06-03 (38 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1887315/+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 1887311] Re: Active line is unreadable in case of dark theme
please apply the same for classic theme as well. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtksourceview4 in Ubuntu. https://bugs.launchpad.net/bugs/1887311 Title: Active line is unreadable in case of dark theme Status in gtksourceview4 package in Ubuntu: Confirmed Bug description: Hello, The active line is unreadable on ubuntu 20.04 with the default dark themes. I assume that modify the /usr/share/gtksourceview-4/styles/tango.xml (in repo: gtksourceview4/data/styles/tango.xml) with the following from: to a less harsch colour: at line #49. Thank's in advance, cociweb ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libgtksourceview-4-0 4.6.0-1 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jul 12 23:16:41 2020 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=hu_HU.UTF-8 SHELL=/bin/bash SourcePackage: gtksourceview4 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtksourceview4/+bug/1887311/+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 1865457] Re: gedit tango color scheme display ugly white grid pattern
*** This bug is a duplicate of bug 1887311 *** https://bugs.launchpad.net/bugs/1887311 ** This bug has been marked a duplicate of bug 1887311 Active line is unreadable in case of dark theme -- 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/1865457 Title: gedit tango color scheme display ugly white grid pattern Status in gedit package in Ubuntu: New Bug description: - launch gedit - in the three lines "burger" menu, select "Preferences" - in "View" tab, activate "Display grid pattern" option - in "Font & Colors" tab, select "/* Tango */" From now on, a uggly white grid covers the surface of the editing area. Shouldn't this dark theme display a dark grid as well ? ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gedit 3.35.90-1 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Mar 2 11:09:04 2020 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: gedit UpgradeStatus: Upgraded to focal on 2018-11-14 (473 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1865457/+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 1887315] [NEW] Nautilus crashes while over-typing search term on remote smb file system
Public bug reported: ==Impact== nautilus crashes while typing the term to search a remote directory within an NT file system over the smb protocol. The problem may affect other remote file systems or protocols, but I have only tested these. Repeatable. ==How to repeat== 1. Open Nautilus 2. In the sidebar, click Other Locations 3. Type smb://example/share into the 'Connect to server' field or select an existing share URI 4. Click Connect 5. Optionally, when the contents of the share appears, select any depth of sub-directories. 6. Click the search icon and type a search string 7. Once the search results have returned, without closing the search box, select the previous search term and over-type another search term. Nautilus crashes. Typically, prior to the window disappearing the graphics freezes within the search field showing both the previous and the current search terms on top of each other. Often it is necessary to kill the nautilus process and/or reboot the smb daemon on the remote machine before being able to use the smb share again. Before typing a second search term, if instead of over-typing, you delete the selection either i) with the key; or ii) clicking the (x) to clear the field; or iii) clicking the search icon twice to remove and reinstate the search field; it is possible to search for a second term without crashing. It is possible that the crash depends on how fast the search term is typed, because nautilus starts searching as you type. I have tried to paste a search term over an existing term, which usually seems to work without crashing. On the other hand, I have had nautilus crash when typing a search term after having explicitly cleared the search field, but before nautilus has displayed the full contents of the directory again (about 150 files). I have not had nautilus crash when over-typing the search field for a local file system, whether ntfs or ext3. ==Related bugs== Bug #1795028 seems to be identical, and claims to have been fixed in package nautilus - 1:3.26.4-0~ubuntu18.04.2 but it does not appear to be fixed in 3.36.3 under Ubuntu 20.04. Hopefully this report explains more precisely how to reproduce the crash. ==Crash Reports== A typical crash report from my system is here: https://errors.ubuntu.com/oops/2dd9aa90-c462-11ea-9e47-fa163e102db1 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.36.3-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jul 12 21:03:59 2020 InstallationDate: Installed on 2020-06-03 (38 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- 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/1887315 Title: Nautilus crashes while over-typing search term on remote smb file system Status in nautilus package in Ubuntu: New Bug description: ==Impact== nautilus crashes while typing the term to search a remote directory within an NT file system over the smb protocol. The problem may affect other remote file systems or protocols, but I have only tested these. Repeatable. ==How to repeat== 1. Open Nautilus 2. In the sidebar, click Other Locations 3. Type smb://example/share into the 'Connect to server' field or select an existing share URI 4. Click Connect 5. Optionally, when the contents of the share appears, select any depth of sub-directories. 6. Click the search icon and type a search string 7. Once the search results have returned, without closing the search box, select the previous search term and over-type another search term. Nautilus crashes. Typically, prior to the window disappearing the graphics freezes within the search field showing both the previous and the current search terms on top of each other. Often it is necessary to kill the nautilus process and/or reboot the smb daemon on the remote machine before being able to use the smb share again. Before typing a second search term, if instead of over-typing, you delete the selection either i) with the key; or ii) clicking the (x) to clear the field; or iii) clicking the search icon twice to remove and reinstate the search field; it is possible to search for a second term without crashing. It is possible that the crash depends on how fast the search term is typed, because nautilus starts searching as you type. I have tried to paste a search term over an existing term, which usually seems to work without crashing. On the other hand, I have had nautilus crash when
[Desktop-packages] [Bug 1812663] Re: Background Color And Text Color Both Wite with Dark Theme
*** This bug is a duplicate of bug 1887311 *** https://bugs.launchpad.net/bugs/1887311 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gedit (Ubuntu) Status: New => Confirmed -- 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/1812663 Title: Background Color And Text Color Both Wite with Dark Theme Status in gedit package in Ubuntu: Confirmed Bug description: The background color and the text color are both white when using the dark layout. $ cat .config/gtk-3.0/settings.ini [Settings] gtk-application-prefer-dark-theme=1 ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gedit 3.30.2-0ubuntu0.18.10.2 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Jan 21 13:01:50 2019 InstallationDate: Installed on 2017-12-15 (402 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) SourcePackage: gedit UpgradeStatus: Upgraded to cosmic on 2018-10-24 (88 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1812663/+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 1873930] Re: White line with white font on current active line with dark Yaru theme
*** This bug is a duplicate of bug 1887311 *** https://bugs.launchpad.net/bugs/1887311 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gedit (Ubuntu) Status: New => Confirmed -- 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/1873930 Title: White line with white font on current active line with dark Yaru theme Status in gedit package in Ubuntu: Confirmed Bug description: The active line is white with white font since upgrade to focal. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gedit 3.36.1-1 ProcVersionSignature: Ubuntu 5.4.0-25.29-lowlatency 5.4.30 Uname: Linux 5.4.0-25-lowlatency x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Apr 20 21:14:33 2020 InstallationDate: Installed on 2020-02-08 (72 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: gedit UpgradeStatus: Upgraded to focal on 2020-04-20 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1873930/+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 1887311] Re: Active line is unreadable in case of dark theme
** Patch added: "tango.patch" https://bugs.launchpad.net/ubuntu/+source/gtksourceview4/+bug/1887311/+attachment/5392130/+files/tango.patch -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtksourceview4 in Ubuntu. https://bugs.launchpad.net/bugs/1887311 Title: Active line is unreadable in case of dark theme Status in gtksourceview4 package in Ubuntu: Confirmed Bug description: Hello, The active line is unreadable on ubuntu 20.04 with the default dark themes. I assume that modify the /usr/share/gtksourceview-4/styles/tango.xml (in repo: gtksourceview4/data/styles/tango.xml) with the following from: to a less harsch colour: at line #49. Thank's in advance, cociweb ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libgtksourceview-4-0 4.6.0-1 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jul 12 23:16:41 2020 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=hu_HU.UTF-8 SHELL=/bin/bash SourcePackage: gtksourceview4 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtksourceview4/+bug/1887311/+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 1887311] Re: Active line is unreadable in case of dark theme
** Description changed: Hello, The active line is unreadable on ubuntu 20.04 with the default dark themes. - I assume that modify the /usr/share/gtksourceview-4/styles/tango.xml with the following from: + I assume that modify the /usr/share/gtksourceview-4/styles/tango.xml (in repo: gtksourceview4/data/styles/tango.xml) with the following from: to a less harsch colour: + + at line #49. Thank's in advance, cociweb ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libgtksourceview-4-0 4.6.0-1 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jul 12 23:16:41 2020 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=hu_HU.UTF-8 SHELL=/bin/bash SourcePackage: gtksourceview4 UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtksourceview4 in Ubuntu. https://bugs.launchpad.net/bugs/1887311 Title: Active line is unreadable in case of dark theme Status in gtksourceview4 package in Ubuntu: Confirmed Bug description: Hello, The active line is unreadable on ubuntu 20.04 with the default dark themes. I assume that modify the /usr/share/gtksourceview-4/styles/tango.xml (in repo: gtksourceview4/data/styles/tango.xml) with the following from: to a less harsch colour: at line #49. Thank's in advance, cociweb ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libgtksourceview-4-0 4.6.0-1 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jul 12 23:16:41 2020 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=hu_HU.UTF-8 SHELL=/bin/bash SourcePackage: gtksourceview4 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtksourceview4/+bug/1887311/+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 1870443] Re: white fonts on white background on highlighted line in gedit with dark-theme
*** This bug is a duplicate of bug 1887311 *** https://bugs.launchpad.net/bugs/1887311 ** This bug is no longer a duplicate of bug 1857191 Dark themes don't work well with highlighted current line in gedit ** This bug has been marked a duplicate of bug 1887311 Active line is unreadable in case of dark theme -- 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/1870443 Title: white fonts on white background on highlighted line in gedit with dark-theme Status in gedit package in Ubuntu: New Bug description: Gedit with Ubuntu Dark-Theme and Tango shows white fonts on white background when the line is highlighted (current line). Attached image exemplifies it. The expected behaviour is to have a darker background with white fonts, or darker fonts with white background. To fix it i had to change Gedit's Color Scheme or disabling "Highlight current line". ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gedit 3.36.1-1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Apr 2 19:27:57 2020 InstallationDate: Installed on 2020-04-02 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401) SourcePackage: gedit UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1870443/+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 1870393] Re: Poor contrast in some applications
*** This bug is a duplicate of bug 1887311 *** https://bugs.launchpad.net/bugs/1887311 ** This bug is no longer a duplicate of bug 1857191 Dark themes don't work well with highlighted current line in gedit ** This bug has been marked a duplicate of bug 1887311 Active line is unreadable in case of dark theme -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to yaru-theme in Ubuntu. https://bugs.launchpad.net/bugs/1870393 Title: Poor contrast in some applications Status in yaru-theme package in Ubuntu: New Bug description: In some applications the contrast between the background and text colour is very poor when using the Yaru theme in "Dark Mode". For example, If the theme is set to Dark via the settings application under "Appearance" and gedit (GNOME Text Editor" is launched. The background of the line the cursor is on is light very similar to the text colour. I've attached a screenshot. In the "Standard" mode the theme subtly highlights the current line. But this is not the case for the "Dark" mode. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: yaru-theme-gtk 20.04.4 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Apr 2 17:46:15 2020 InstallationDate: Installed on 2020-03-20 (12 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200320) PackageArchitecture: all SourcePackage: yaru-theme UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yaru-theme/+bug/1870393/+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 1875018] Re: Current/selected line text is barely visible when using yaru-dark
*** This bug is a duplicate of bug 1887311 *** https://bugs.launchpad.net/bugs/1887311 ** This bug is no longer a duplicate of bug 1857191 Dark themes don't work well with highlighted current line in gedit ** This bug has been marked a duplicate of bug 1887311 Active line is unreadable in case of dark theme -- 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/1875018 Title: Current/selected line text is barely visible when using yaru-dark Status in gedit package in Ubuntu: New Bug description: I am currently using Ubuntu 20.04 with the dark theme (yaru-dark). I have gedit configured to highlight current line. Using yaru and yaru-light this works well, but when using yaru-dark the current line is highlighted with almost white color, masking the white text which become barely visible. See attached screenshot. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gedit 3.36.1-1 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Apr 25 10:16:28 2020 SourcePackage: gedit UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1875018/+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 1884124] Re: Text Editor (geditunusable with yaru-dark
*** This bug is a duplicate of bug 1887311 *** https://bugs.launchpad.net/bugs/1887311 ** This bug is no longer a duplicate of bug 1857191 Dark themes don't work well with highlighted current line in gedit ** This bug has been marked a duplicate of bug 1887311 Active line is unreadable in case of dark theme -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to yaru-theme in Ubuntu. https://bugs.launchpad.net/bugs/1884124 Title: Text Editor (geditunusable with yaru-dark Status in yaru-theme package in Ubuntu: New Bug description: 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu Description: Ubuntu 20.04 LTS Release: 20.04 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center gedit: Installed: 3.36.2-0ubuntu1 Candidate: 3.36.2-0ubuntu1 Version table: *** 3.36.2-0ubuntu1 500 500 http://ca.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.36.1-1 500 500 http://ca.archive.ubuntu.com/ubuntu focal/main amd64 Packages 3) What you expected to happen gedit/Text Editor to look nice and usable in yaru-dark (Settings > Appearance > Dark) 4) What happened instead Highlighted line is unreadable. It highlights in white but the text is very light gray! The cursor is almost impossible to see as well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yaru-theme/+bug/1884124/+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 1812663] Re: Background Color And Text Color Both Wite with Dark Theme
*** This bug is a duplicate of bug 1887311 *** https://bugs.launchpad.net/bugs/1887311 ** This bug is no longer a duplicate of bug 1857191 Dark themes don't work well with highlighted current line in gedit ** This bug has been marked a duplicate of bug 1887311 Active line is unreadable in case of dark theme -- 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/1812663 Title: Background Color And Text Color Both Wite with Dark Theme Status in gedit package in Ubuntu: New Bug description: The background color and the text color are both white when using the dark layout. $ cat .config/gtk-3.0/settings.ini [Settings] gtk-application-prefer-dark-theme=1 ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gedit 3.30.2-0ubuntu0.18.10.2 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Jan 21 13:01:50 2019 InstallationDate: Installed on 2017-12-15 (402 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) SourcePackage: gedit UpgradeStatus: Upgraded to cosmic on 2018-10-24 (88 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1812663/+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 1867819] Re: Dark theme current line highlight hard to read
*** This bug is a duplicate of bug 1887311 *** https://bugs.launchpad.net/bugs/1887311 ** This bug is no longer a duplicate of bug 1857191 Dark themes don't work well with highlighted current line in gedit ** This bug has been marked a duplicate of bug 1887311 Active line is unreadable in case of dark theme -- 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/1867819 Title: Dark theme current line highlight hard to read Status in gedit package in Ubuntu: New Bug description: In focal, with a dark theme (adwaita-dark), the current line highlight in almost the same color as the text, making it very hard to read. see screenshot. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gedit 3.36.0-3 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Mar 17 11:28:29 2020 InstallationDate: Installed on 2019-08-17 (213 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1) SourcePackage: gedit UpgradeStatus: Upgraded to focal on 2020-03-06 (11 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1867819/+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 1875277] Re: Active|Focused line in the dark mode is unreadable. Highliht and font color are almost the same.
*** This bug is a duplicate of bug 1887311 *** https://bugs.launchpad.net/bugs/1887311 ** This bug is no longer a duplicate of bug 1857191 Dark themes don't work well with highlighted current line in gedit ** This bug has been marked a duplicate of bug 1887311 Active line is unreadable in case of dark theme -- 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/1875277 Title: Active|Focused line in the dark mode is unreadable. Highliht and font color are almost the same. Status in gedit package in Ubuntu: New Bug description: Active|Focused line in the dark mode is unreadable. Highliht and font color are almost the same. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gedit 3.36.1-1 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Apr 27 06:07:07 2020 InstallationDate: Installed on 2020-04-25 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: gedit UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1875277/+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 1873930] Re: White line with white font on current active line with dark Yaru theme
*** This bug is a duplicate of bug 1887311 *** https://bugs.launchpad.net/bugs/1887311 ** This bug is no longer a duplicate of bug 1857191 Dark themes don't work well with highlighted current line in gedit ** This bug has been marked a duplicate of bug 1887311 Active line is unreadable in case of dark theme -- 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/1873930 Title: White line with white font on current active line with dark Yaru theme Status in gedit package in Ubuntu: New Bug description: The active line is white with white font since upgrade to focal. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gedit 3.36.1-1 ProcVersionSignature: Ubuntu 5.4.0-25.29-lowlatency 5.4.30 Uname: Linux 5.4.0-25-lowlatency x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Apr 20 21:14:33 2020 InstallationDate: Installed on 2020-02-08 (72 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: gedit UpgradeStatus: Upgraded to focal on 2020-04-20 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1873930/+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 1857191] Re: Dark themes don't work well with highlighted current line in gedit
*** This bug is a duplicate of bug 1887311 *** https://bugs.launchpad.net/bugs/1887311 ** This bug has been marked a duplicate of bug 1887311 Active line is unreadable in case of dark theme -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtksourceview4 in Ubuntu. https://bugs.launchpad.net/bugs/1857191 Title: Dark themes don't work well with highlighted current line in gedit Status in GtkSourceView: New Status in gtksourceview4 package in Ubuntu: Triaged Status in yaru-theme package in Ubuntu: Confirmed Bug description: In order to checkout out an old bug report I started gedit, enabled "Highlight current line" and changed the application theme to "Yaru- dark" The current line is highlighted correctly but the text is unreadable because it is too light. The text needs to be much darker. This is not a theme that I would normally use so I'm not too bothered about how the problem is fixed but this configuration makes gedit very difficult to use as you can't actually see the text that you're adding, changing or deleting. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: yaru-theme-gtk 19.10.4 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CurrentDesktop: GNOME Date: Sat Dec 21 16:33:03 2019 InstallationDate: Installed on 2019-05-17 (218 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190517) PackageArchitecture: all SourcePackage: yaru-theme UpgradeStatus: Upgraded to focal on 2019-11-08 (42 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gtksourceview/+bug/1857191/+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 1877841] Re: with the dark theme, the active line is highlighted and I cannot see the text I am typing.
*** This bug is a duplicate of bug 1887311 *** https://bugs.launchpad.net/bugs/1887311 ** This bug is no longer a duplicate of bug 1857191 Dark themes don't work well with highlighted current line in gedit ** This bug has been marked a duplicate of bug 1887311 Active line is unreadable in case of dark theme -- 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/1877841 Title: with the dark theme, the active line is highlighted and I cannot see the text I am typing. Status in gedit package in Ubuntu: New Bug description: 1) Release: 20.04 2) Version: 3.36.1-1 3) Expected: I have the Dark theme on. On opening Gedit, the active line is all white. When I typed, I expected to see letters. 4) What happened: Nothing appeared. I thought it had locked up. I tapped on the Enter key and it went to the next line, revealing the text I had typed on the previously active line. So, it seems like with Dark theme on the text is white and same as the highlight. When I switched back to Standard theme, no problems. The text was black, the blank space is white and the highlight is slightly off-white (beige maybe, not good with the naming of colors). It's perfectly legible. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gedit 3.36.1-1 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun May 10 17:35:24 2020 ExecutablePath: /usr/bin/gedit InstallationDate: Installed on 2020-05-10 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANGUAGE=en_PH:en LANG=en_PH.UTF-8 SourcePackage: gedit UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1877841/+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 1871068] Re: Gedit current line highlighting doesn't play well with Yaru-dark
*** This bug is a duplicate of bug 1887311 *** https://bugs.launchpad.net/bugs/1887311 ** This bug is no longer a duplicate of bug 1857191 Dark themes don't work well with highlighted current line in gedit ** This bug has been marked a duplicate of bug 1887311 Active line is unreadable in case of dark theme -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to yaru-theme in Ubuntu. https://bugs.launchpad.net/bugs/1871068 Title: Gedit current line highlighting doesn't play well with Yaru-dark Status in yaru-theme package in Ubuntu: New Bug description: By default, gedit has "Highlight current line" option enabled. While that works great for Yaru and Adwaita, this is barely usable with Yaru-dark, because both background and foreground are just different shades of white. While this is a minor issue and can be easily fixed by adjusting gedit's color scheme, that might give not the best impression for a first-time Ubuntu user. apt policy gedit gedit: Installed: 3.36.1-1 Candidate: 3.36.1-1 Version table: *** 3.36.1-1 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status apt policy yaru-theme-gtk yaru-theme-gtk: Installed: 20.04.4 Candidate: 20.04.4 Version table: *** 20.04.4 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu focal/main i386 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: yaru-theme-gtk 20.04.4 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Apr 6 11:43:32 2020 InstallationDate: Installed on 2019-11-07 (150 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) PackageArchitecture: all SourcePackage: yaru-theme UpgradeStatus: Upgraded to focal on 2020-03-04 (32 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yaru-theme/+bug/1871068/+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 1879886] Re: Current line background color doesn't respect system dark theme
*** This bug is a duplicate of bug 1887311 *** https://bugs.launchpad.net/bugs/1887311 ** This bug is no longer a duplicate of bug 1857191 Dark themes don't work well with highlighted current line in gedit ** This bug has been marked a duplicate of bug 1887311 Active line is unreadable in case of dark theme -- 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/1879886 Title: Current line background color doesn't respect system dark theme Status in gedit package in Ubuntu: New Bug description: On Ubuntu 20.04 with a dark theme in gedit current line background color is bright white, while the rest of the background is dark grey. White font color on white background is 100% unreadable. gedit: Installed: 3.36.2-0ubuntu1 Candidate: 3.36.2-0ubuntu1 Version table: *** 3.36.2-0ubuntu1 500 500 http://at.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.36.1-1 500 500 http://at.archive.ubuntu.com/ubuntu focal/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gedit 3.36.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu May 21 08:51:28 2020 InstallationDate: Installed on 2020-04-24 (27 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: gedit UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1879886/+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 1877876] Re: white line at gedit with the dark windows skin
*** This bug is a duplicate of bug 1887311 *** https://bugs.launchpad.net/bugs/1887311 ** This bug is no longer a duplicate of bug 1857191 Dark themes don't work well with highlighted current line in gedit ** This bug has been marked a duplicate of bug 1887311 Active line is unreadable in case of dark theme -- 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/1877876 Title: white line at gedit with the dark windows skin Status in gedit package in Ubuntu: New Bug description: With the dark window skin enabled type marker in gedit turns into a white line, so you can't see what your typing. Description: Ubuntu 20.04 LTS Release: 20.04 gedit: Geïnstalleerd: 3.36.1-1 Kandidaat: 3.36.1-1 Versietabel: *** 3.36.1-1 500 500 http://nl.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1877876/+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 1872370] Re: gedit current line is illegibly highlighted on Breeze-Dark theme
*** This bug is a duplicate of bug 1887311 *** https://bugs.launchpad.net/bugs/1887311 ** This bug is no longer a duplicate of bug 1857191 Dark themes don't work well with highlighted current line in gedit ** This bug has been marked a duplicate of bug 1887311 Active line is unreadable in case of dark theme -- 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/1872370 Title: gedit current line is illegibly highlighted on Breeze-Dark theme Status in gedit package in Ubuntu: New Bug description: When gedit is launched in KDE with the Breeze-Dark theme active, the line with the cursor is highlighted white even though the text is white. This makes it impossible to read the text. "lsb_release -rd": Description:Ubuntu Focal Fossa (development branch) Release:20.04 "apt-cache policy gedit" gedit: Installed: 3.36.1-1 Candidate: 3.36.1-1 Version table: *** 3.36.1-1 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status "apt-cache policy kde-config-gtk-style" kde-config-gtk-style: Installed: 4:5.18.4.1-0ubuntu1 Candidate: 4:5.18.4.1-0ubuntu1 Version table: *** 4:5.18.4.1-0ubuntu1 500 500 http://archive.ubuntu.com/ubuntu focal/universe amd64 Packages 100 /var/lib/dpkg/status "apt-cache policy breeze-gtk-theme" breeze-gtk-theme: Installed: 5.18.4.1-0ubuntu1 Candidate: 5.18.4.1-0ubuntu1 Version table: *** 5.18.4.1-0ubuntu1 500 500 http://archive.ubuntu.com/ubuntu focal/universe amd64 Packages 100 /var/lib/dpkg/status Procedure: 1. Spin up a VirtualBox VM 2. Insert http://cdimage.ubuntu.com/kubuntu/daily-live/20200412/focal-desktop-amd64.iso as the CD 3. Click on "Try Kubuntu" 4. Open Konsole 5. Run "sudo apt install gedit" 6. Open System Settings 7. Go into "Global Theme" 8. Select "Breeze Dark" 9. Click "Apply" 10. Click the home icon 11. Go into "Application Style" 12. Click "Configure GNOME/GTK Application Style" 13. Set both the "GTK2 theme" and "GTK3 theme" dropdowns to "Breeze-Dark" 14. Click "Apply" 15. Open gedit 16. Type some text Expected behavior: To be able to read the line I'm typing on. This was the behavior before Ubuntu 20.04 unified GTK and Qt themes. While restoring the behavior would be better than having completely illegible text, it would be preferred to get gedit and the Breeze-Dark theme to actually work together. Actual behavior: The current line is illegible. The line is highlighted white even though the text is white. A screenshot of this behavior is attached. Workaround: Move the cursor to another line before trying to read the text, or select the text before trying to read it. This workaround is very annoying. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1872370/+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 1879406] Re: Dark mode on gedit - unable to see text
*** This bug is a duplicate of bug 1887311 *** https://bugs.launchpad.net/bugs/1887311 ** This bug is no longer a duplicate of bug 1857191 Dark themes don't work well with highlighted current line in gedit ** This bug has been marked a duplicate of bug 1887311 Active line is unreadable in case of dark theme -- 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/1879406 Title: Dark mode on gedit - unable to see text Status in gedit package in Ubuntu: New Bug description: Unable to see current line of text on gedit when in dark mode and with default gedit setting to highlight current line. Highilght is the same colour as the text. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gedit 3.36.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon May 18 22:20:55 2020 InstallationDate: Installed on 2020-05-17 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: gedit UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1879406/+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 1887311] Re: Active line is unreadable in case of dark theme
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gtksourceview4 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtksourceview4 in Ubuntu. https://bugs.launchpad.net/bugs/1887311 Title: Active line is unreadable in case of dark theme Status in gtksourceview4 package in Ubuntu: Confirmed Bug description: Hello, The active line is unreadable on ubuntu 20.04 with the default dark themes. I assume that modify the /usr/share/gtksourceview-4/styles/tango.xml with the following from: to a less harsch colour: Thank's in advance, cociweb ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libgtksourceview-4-0 4.6.0-1 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jul 12 23:16:41 2020 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=hu_HU.UTF-8 SHELL=/bin/bash SourcePackage: gtksourceview4 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtksourceview4/+bug/1887311/+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 1887311] [NEW] Active line is unreadable in case of dark theme
Public bug reported: Hello, The active line is unreadable on ubuntu 20.04 with the default dark themes. I assume that modify the /usr/share/gtksourceview-4/styles/tango.xml with the following from: to a less harsch colour: Thank's in advance, cociweb ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libgtksourceview-4-0 4.6.0-1 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jul 12 23:16:41 2020 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=hu_HU.UTF-8 SHELL=/bin/bash SourcePackage: gtksourceview4 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gtksourceview4 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Summary changed: - Active line is unreadable oin case of dark theme + Active line is unreadable in case of dark theme ** Description changed: Hello, - The active line is unreadable on ubunut 20.04 with the default dark themes. + The active line is unreadable on ubuntu 20.04 with the default dark themes. I assume that modify the /usr/share/gtksourceview-4/styles/tango.xml with the following from: to a less harsch colour: Thank's in advance, cociweb ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libgtksourceview-4-0 4.6.0-1 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jul 12 23:16:41 2020 ProcEnviron: - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=hu_HU.UTF-8 - SHELL=/bin/bash + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=hu_HU.UTF-8 + SHELL=/bin/bash SourcePackage: gtksourceview4 UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtksourceview4 in Ubuntu. https://bugs.launchpad.net/bugs/1887311 Title: Active line is unreadable in case of dark theme Status in gtksourceview4 package in Ubuntu: New Bug description: Hello, The active line is unreadable on ubuntu 20.04 with the default dark themes. I assume that modify the /usr/share/gtksourceview-4/styles/tango.xml with the following from: to a less harsch colour: Thank's in advance, cociweb ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libgtksourceview-4-0 4.6.0-1 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jul 12 23:16:41 2020 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=hu_HU.UTF-8 SHELL=/bin/bash SourcePackage: gtksourceview4 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtksourceview4/+bug/1887311/+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 1887304] [NEW] Display configuration gets applied only after I log in
Public bug reported: This isn't new, this idiocy has annoyed me ever since I've been using Ubuntu; however, after upgrading to 20.04 I'm disappointed to see that it still hasn't been fixed. I use a laptop and I have an external monitor that I keep connected most of the time. So, I have it set up to use the external screen as the only display. However, when I boot and the login screen shows up, a different configuration, which I guess is the default, is applied, with the laptop's built-in display as the main display and the external screen as the secondary one in extended desktop configuration. Therefore the login screen shows up on the builtin display. Only after I log in, my configuration gets applied and the builtin displey turns off and the external one becomes the only one. It's not a huge deal since the laptop screen is kind of in front of me anyway so I can see it, but it's not ideal and it's stupid. Also, it implies that when I do log in, I have that few seconds of all-black screens while the displays adjust, which is irritating considered they would have had plenty of time to do that before I logged in. I guess the display configuration is somehow stored as associated to the user, and I understand that theoretically different users may have different configurations. However, that's no excuse. As an administrator, I should be able to choose a configuration that gets applied from the beginning before anybody logs in. Also, given that I am the ONLY user (which is a pretty common scenario on Desktop), it should be the default that my configuration be the global configuration (with the possibility to choose differently). Probably a good solution would be to have, in the Displays settings, an option such as "apply this configuration globally" (or whatever better phrasing), meaning it would be applied before login. Obviously that doesn't mean that, if the saved configuration is not applicable to the current situation at startup (e.g. I have set it up to use only the external monitor but there is no external monitor connected right now), it shouldn't automatically switch to a different workable setting. I think it already does that if that happens after login, so that would be no different before login. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.108 Wed Dec 11 11:06:58 PST 2019 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2) .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Jul 12 21:04:20 2020 DistUpgraded: 2020-07-12 20:55:12,554 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia-340, 340.108, 5.3.0-62-generic, x86_64: installed nvidia-340, 340.108, 5.4.0-40-generic, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] 3rd Gen Core processor Graphics Controller [1025:0647] NVIDIA Corporation GF117M [GeForce 610M/710M/810M/820M / GT 620M/625M/630M/720M] [10de:1140] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] GeForce 710M [1025:0691] InstallationDate: Installed on 2013-10-11 (2466 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: Acer Aspire V3-571G ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to focal on 2020-07-12 (0 days ago) dmi.bios.date: 10/15/2012 dmi.bios.vendor: Acer dmi.bios.version: V2.07 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: VA50_HC_CR dmi.board.vendor: Acer dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.07 dmi.modalias: dmi:bvnAcer:bvrV2.07:bd10/15/2012:svnAcer:pnAspireV3-571G:pvrV2.07:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnAcer:ct10:cvrV2.07: dmi.product.family: Type1Family dmi.product.name: Aspire V3-571G dmi.product.sku: Aspire V3-_0648_V2.07 dmi.product.version: V2.07 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1 version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri:
[Desktop-packages] [Bug 1881918] Re: Update GNOME Software to 3.36.1 in Focal
I can also confirm that the gnome-software 3.36.1-0ubuntu0.20.04.0 version from focal-proposed works fine. Thanks! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1881918 Title: Update GNOME Software to 3.36.1 in Focal Status in One Hundred Papercuts: Fix Committed Status in gnome-software package in Ubuntu: Fix Released Status in gnome-software source package in Focal: Fix Committed Bug description: [ Description ] GNOME upstream have released a new stable version of gnome-software. [ QA ] GNOME has a micro release exception that covers this package. https://wiki.ubuntu.com/StableReleaseUpdates/GNOME So we don't need to verify the fixes explicitly. [ Regression Potential ] Changes could cause issues in GNOME Software, which might make it hard to install or remove software. Default store in Ubuntu is snap-store, so this doesn't affect the majority of users. To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1881918/+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 1884856] Re: [snap] chromium is built with NEON on armhf (SIGILL, Illegal instruction)
Hi, Olivier! Today's Chromium-browser from the candidate channel is working great on NVIDIA Tegra20! Thank you for the fix! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1884856 Title: [snap] chromium is built with NEON on armhf (SIGILL, Illegal instruction) Status in chromium-browser package in Ubuntu: Fix Committed Bug description: Chromium-browser stopped working on NVIDIA Tegra20 devices since the time it was switched to the snap packaging. # gdb /snap/bin/chromium ... Thread 11 "chrome" received signal SIGILL, Illegal instruction. 0xb6b4ee9a in std::__1::locale::__imp::__imp(unsigned int) () from target:/snap/chromium/1211/usr/lib/chromium-browser/libffmpeg.so (gdb) bt #0 0xb6b4ee9a in std::__1::locale::__imp::__imp(unsigned int) () from target:/snap/chromium/1211/usr/lib/chromium-browser/libffmpeg.so #1 0xb6b509c8 in std::__1::locale::__global() () from target:/snap/chromium/1211/usr/lib/chromium-browser/libffmpeg.so #2 0xb6b50a32 in std::__1::locale::locale() () from target:/snap/chromium/1211/usr/lib/chromium-browser/libffmpeg.so #3 0xb6b3e7d0 in std::__1::basic_streambuf >::basic_streambuf() () from target:/snap/chromium/1211/usr/lib/chromium-browser/libffmpeg.so #4 0xb6b3ede6 in std::__1::DoIOSInit::DoIOSInit() () from target:/snap/chromium/1211/usr/lib/chromium-browser/libffmpeg.so #5 0xb6b3f9b2 in _GLOBAL__sub_I_iostream.cpp () from target:/snap/chromium/1211/usr/lib/chromium-browser/libffmpeg.so #6 0xb6f215c0 in ?? () from target:/lib/ld-linux-armhf.so.3 (gdb) layout asm │ >0xb6b4ee9a <_ZNSt3__16locale5__impC2Ej+10> vmov.i32q8, #0 ; 0x │ 0xb6b4ee9e <_ZNSt3__16locale5__impC2Ej+14> mov r9, r0 │ 0xb6b4eea0 <_ZNSt3__16locale5__impC2Ej+16> add.w r3, r9, #40 ; 0x28 NVIDIA Tegra20 is one of ARMv7 CPUs which do not support NEON instructions, "vmov.i32 q8" is the ARM NEON instruction because q8 is the NEON register. Will be great if the compiler flags could be changed back to what was used for the deb packaging, thanks in advance! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1884856/+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 1887300] [NEW] Wacom overlay text labels are invisible
Public bug reported: https://github.com/ubuntu/yaru/issues/2099 [Impact] * The wacom overlay text is invisible and users can not use this gnome- shell dialog to map their wacom tablet hardware buttons * Backporting this to the stable release focal will let wacom users use this dialogue again, which is very important because you have no other way to map it in ubuntu * The fix is already in yaru master https://github.com/ubuntu/yaru/pull/2198 [Test Case] * Plug a wacom tablet to your computer, search for "wacom" in the gnome shell search and press enter to open the corresponding gnome-control- center page. Now open the dialog to map your buttons. See how the labels for each button are invisible * Build yaru from master and repeat these steps and see how the labels appear and you can properly map the correct button [Regression Potential] * No regression potential * Built and tested with the yaru master branch [Other Info] * Yaru issue: https://github.com/ubuntu/yaru/issues/2099 * yaru fix: https://github.com/ubuntu/yaru/pull/2198 ** Affects: yaru-theme (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to yaru-theme in Ubuntu. https://bugs.launchpad.net/bugs/1887300 Title: Wacom overlay text labels are invisible Status in yaru-theme package in Ubuntu: New Bug description: https://github.com/ubuntu/yaru/issues/2099 [Impact] * The wacom overlay text is invisible and users can not use this gnome-shell dialog to map their wacom tablet hardware buttons * Backporting this to the stable release focal will let wacom users use this dialogue again, which is very important because you have no other way to map it in ubuntu * The fix is already in yaru master https://github.com/ubuntu/yaru/pull/2198 [Test Case] * Plug a wacom tablet to your computer, search for "wacom" in the gnome shell search and press enter to open the corresponding gnome- control-center page. Now open the dialog to map your buttons. See how the labels for each button are invisible * Build yaru from master and repeat these steps and see how the labels appear and you can properly map the correct button [Regression Potential] * No regression potential * Built and tested with the yaru master branch [Other Info] * Yaru issue: https://github.com/ubuntu/yaru/issues/2099 * yaru fix: https://github.com/ubuntu/yaru/pull/2198 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yaru-theme/+bug/1887300/+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 1887298] [NEW] blue GtkSpinner is hard to see on red .destrucive-action buttons
Public bug reported: [Impact] * Blue blue GtkSpinner is hard to see on red .destrucive-action buttons, like the "Stop scanning" button in simple-scan, Link to the yaru github issue: https://github.com/ubuntu/yaru/issues/2182 [Test Case] * Press the green "Scan" button in simple-scan and it will turn red with a "Stop" label and a blue spinner inside the button. The spinner is hard to see on this red background * Build yaru from master and notice how the white spinner is much more visible against a red background [Regression Potential] * No regression potential * Tested by building yaru from source [Other Info] * Link to the github pull request: https://github.com/ubuntu/yaru/pull/2187 ** Affects: yaru-theme (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to yaru-theme in Ubuntu. https://bugs.launchpad.net/bugs/1887298 Title: blue GtkSpinner is hard to see on red .destrucive-action buttons Status in yaru-theme package in Ubuntu: New Bug description: [Impact] * Blue blue GtkSpinner is hard to see on red .destrucive-action buttons, like the "Stop scanning" button in simple-scan, Link to the yaru github issue: https://github.com/ubuntu/yaru/issues/2182 [Test Case] * Press the green "Scan" button in simple-scan and it will turn red with a "Stop" label and a blue spinner inside the button. The spinner is hard to see on this red background * Build yaru from master and notice how the white spinner is much more visible against a red background [Regression Potential] * No regression potential * Tested by building yaru from source [Other Info] * Link to the github pull request: https://github.com/ubuntu/yaru/pull/2187 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yaru-theme/+bug/1887298/+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 1835605] Re: /usr/lib/gvfs/gvfs-afc-volume-monitor: error while loading shared libraries: libssl.so.1.0.0
/usr/local/lib/* files Thank you for taking the time to report this bug and trying to help make Ubuntu better. However, it seems that you are not using a software package provided by the official Ubuntu repositories. Because of this the Ubuntu project can not support or fix your particular bug. Please report this bug to the provider of the software package. Thanks! If you are interested in learning more about software repositories and Ubuntu, check https://help.ubuntu.com/community/Repositories. ** Changed in: gvfs (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1835605 Title: /usr/lib/gvfs/gvfs-afc-volume-monitor: error while loading shared libraries: libssl.so.1.0.0 Status in gvfs package in Ubuntu: Invalid Bug description: When I upgraded to Disco, I got the following error: gvfs-afc-volume-monitor[6816]: /usr/lib/gvfs/gvfs-afc-volume-monitor: error while loading shared libraries: libssl.so.1.0.0: cannot open shared object file: No such file or directory dpkg --list gvfs** Gewünscht=Unbekannt/Installieren/R=Entfernen/P=Vollständig Löschen/Halten | Status=Nicht/Installiert/Config/U=Entpackt/halb konFiguriert/ Halb installiert/Trigger erWartet/Trigger anhängig |/ Fehler?=(kein)/R=Neuinstallation notwendig (Status, Fehler: GROSS=schlecht) ||/ NameVersion Architektur Beschreibung +++-===--- ii gvfs:amd64 1.40.1-1 amd64userspace virtual filesystem - GIO module ii gvfs-backends 1.40.1-1 amd64userspace virtual filesystem - backends ii gvfs-bin1.40.1-1 amd64userspace virtual filesystem - deprecated command-line tools ii gvfs-common 1.40.1-1 all userspace virtual filesystem - common data files ii gvfs-daemons1.40.1-1 amd64userspace virtual filesystem - servers ii gvfs-fuse 1.40.1-1 amd64userspace virtual filesystem - fuse server ii gvfs-libs:amd64 1.40.1-1 amd64userspace virtual filesystem - private libraries ldd -r /usr/lib/gvfs/gvfs-afc-volume-monitor linux-vdso.so.1 (0x7ffcd31f7000) libglib-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 (0x7fb3eb9bb000) libgobject-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 (0x7fb3eb95f000) libimobiledevice.so.6 => /usr/local/lib/libimobiledevice.so.6 (0x7fb3eb73c000) libplist.so.3 => /usr/local/lib/libplist.so.3 (0x7fb3eb52d000) libgio-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 (0x7fb3eb364000) libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7fb3eb179000) libpcre.so.3 => /lib/x86_64-linux-gnu/libpcre.so.3 (0x7fb3eb103000) libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x7fb3eb0e2000) libffi.so.6 => /usr/lib/x86_64-linux-gnu/libffi.so.6 (0x7fb3eb0d8000) libssl.so.1.0.0 => not found libcrypto.so.1.0.0 => not found libusbmuxd.so.4 => /usr/local/lib/libusbmuxd.so.4 (0x7fb3eaed) libgmodule-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libgmodule-2.0.so.0 (0x7fb3eaec8000) libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x7fb3eaeac000) libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x7fb3eaea6000) libmount.so.1 => /lib/x86_64-linux-gnu/libmount.so.1 (0x7fb3eae4a000) libselinux.so.1 => /lib/x86_64-linux-gnu/libselinux.so.1 (0x7fb3eae2) libresolv.so.2 => /lib/x86_64-linux-gnu/libresolv.so.2 (0x7fb3eae05000) /lib64/ld-linux-x86-64.so.2 (0x7fb3ebb27000) libblkid.so.1 => /lib/x86_64-linux-gnu/libblkid.so.1 (0x7fb3eadae000) librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x7fb3eada3000) libuuid.so.1 => /lib/x86_64-linux-gnu/libuuid.so.1 (0x7fb3ead9a000) undefined symbol: ERR_remove_thread_state, version OPENSSL_1.0.0 (/usr/local/lib/libimobiledevice.so.6) undefined symbol: SSL_CTX_use_RSAPrivateKey, version OPENSSL_1.0.0 (/usr/local/lib/libimobiledevice.so.6) undefined symbol: CRYPTO_cleanup_all_ex_data, version OPENSSL_1.0.0 (/usr/local/lib/libimobiledevice.so.6) undefined symbol: EVP_PKEY_free, version OPENSSL_1.0.0 (/usr/local/lib/libimobiledevice.so.6) undefined symbol: PEM_write_bio_X509, version OPENSSL_1.0.0 (/usr/local/lib/libimobiledevice.so.6) undefined symbol: X509_set_notAfter, version OPENSSL_1.0.0 (/usr/local/lib/libimobiledevice.so.6) undefined symbol: ASN1_INTEGER_set, version OPENSSL_1.0.0 (/usr/local/lib/libimobiledevice.so.6) undefined symbol: X509_set_notBefore, version OPENSSL_1.0.0 (/usr/local/lib/libimobiledevice.so.6) undefined symbol: RSA_new,
[Desktop-packages] [Bug 1887297] [NEW] gnome-shell notifications and gtk3 menus are hard to distinguish from the background
Public bug reported: [Impact] * Gtk and shell menus, popups and notifications are often hard to distinguish against the elements that are beneath them (Yaru github bugs: https://github.com/ubuntu/yaru/issues/2221 and https://github.com/ubuntu/yaru/issues/2217) * backporting this QOL change to focal would greatly improve the legibility of the yaru theme(s) * the fixes for this are already in the master branch of https://github.com/ubuntu/yaru [Test Case] * populate gtk3 menus against a nautilus window and spawn a notification by either adding or removing a favourite app in the dock with rightclick add/remove favourite. Gtk3 menus almost look like they are part of the window and not a different part of the desktop. Notifications, especially when using yaru-light are also hard to see and recognize [Regression Potential] * No regression potential * Tested by building the fixed branch(es) of yaru and then switching back and forth the gtk3 and shell themes, please see the corresponding github pull requests https://github.com/ubuntu/yaru/pull/2232 + https://github.com/ubuntu/yaru/pull/2236 [Other Info] * Yaru github bugs: https://github.com/ubuntu/yaru/issues/2221 and https://github.com/ubuntu/yaru/issues/2217 ** Affects: yaru-theme (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to yaru-theme in Ubuntu. https://bugs.launchpad.net/bugs/1887297 Title: gnome-shell notifications and gtk3 menus are hard to distinguish from the background Status in yaru-theme package in Ubuntu: New Bug description: [Impact] * Gtk and shell menus, popups and notifications are often hard to distinguish against the elements that are beneath them (Yaru github bugs: https://github.com/ubuntu/yaru/issues/2221 and https://github.com/ubuntu/yaru/issues/2217) * backporting this QOL change to focal would greatly improve the legibility of the yaru theme(s) * the fixes for this are already in the master branch of https://github.com/ubuntu/yaru [Test Case] * populate gtk3 menus against a nautilus window and spawn a notification by either adding or removing a favourite app in the dock with rightclick add/remove favourite. Gtk3 menus almost look like they are part of the window and not a different part of the desktop. Notifications, especially when using yaru-light are also hard to see and recognize [Regression Potential] * No regression potential * Tested by building the fixed branch(es) of yaru and then switching back and forth the gtk3 and shell themes, please see the corresponding github pull requests https://github.com/ubuntu/yaru/pull/2232 + https://github.com/ubuntu/yaru/pull/2236 [Other Info] * Yaru github bugs: https://github.com/ubuntu/yaru/issues/2221 and https://github.com/ubuntu/yaru/issues/2217 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yaru-theme/+bug/1887297/+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 1887296] [NEW] Moving popup windows drags the application's main window behind it
Public bug reported: Sometimes programs open a "popup" or a "secondary", "child" window, I don't know what the word is. For example, in Chrome, if I right-click on an image in a web page and choose "Save As", this will open a new file browser window that allows me to browse for a directory to save the image to. Until Ubuntu 16.04, I could move that child window around by dragging it by its title bar, and that would not move around the parent window behind it. Now, it does. That is, the "parent" window greyes out, and moving the "child" window (i.e. the popup) on the foreground causes the parent window in the background to move as if they were glued together. In the above example, if I drag around the "Save As" window, the Chrome window behind it moves too. Even worse, if the parent window is maximized, it will "oppose resistance" to the dragging of the popup window, and if I drag far enough, the parent window will unmaximize and unblock the movement of both windows. It's pure madness. I can't imagine a scenario where this is the unavoidable consequence of some improvement. It looks like it is by design. Why? What were you thinking? Why do you ACTIVELY work to degrade usability and make the users' life miserable?? Here's a very real-life example: As mentioned above, I right-click on something in the browser (like an image or a video) and do Save As. When the file browser window opens, it covers the content of the web page from which I was saving the content. Maybe I want to move the child window in order to reveal the web page that I was visiting in the first place, because the context (which I haven't memorized in full in my brain just yet) helps me choose a file name for the very file I'm saving. Another example: I am browsing some folder in Nautilus. I right-click on a file or folder inside it, and open Properties. That opens in a popup. Now I want to have another look at the name of the file I selected (of which I'm now seeing the properties), and those around it, because I'm wondering if I chose the wrong file, or for whatever other reason. I can't do taht without closing the Properties window. The everyday examples are countless. This is idiotic. Seriously, what are you doing? ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.3.0-62.56-generic 5.3.18 Uname: Linux 5.3.0-62-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.108 Wed Dec 11 11:06:58 PST 2019 GCC version: gcc version 9.2.1 20191008 (Ubuntu 9.2.1-9ubuntu2) .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Jul 12 18:11:28 2020 DistUpgraded: 2020-07-12 15:56:23,368 INFO cache.commit() DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia-340, 340.108: added ExtraDebuggingInterest: No GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] 3rd Gen Core processor Graphics Controller [1025:0647] NVIDIA Corporation GF117M [GeForce 610M/710M/810M/820M / GT 620M/625M/630M/720M] [10de:1140] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] GeForce 710M [1025:0691] InstallationDate: Installed on 2013-10-11 (2465 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: Acer Aspire V3-571G ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-62-generic root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to focal on 2020-07-12 (0 days ago) dmi.bios.date: 10/15/2012 dmi.bios.vendor: Acer dmi.bios.version: V2.07 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: VA50_HC_CR dmi.board.vendor: Acer dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.07 dmi.modalias: dmi:bvnAcer:bvrV2.07:bd10/15/2012:svnAcer:pnAspireV3-571G:pvrV2.07:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnAcer:ct10:cvrV2.07: dmi.product.family: Type1Family dmi.product.name: Aspire V3-571G dmi.product.sku: Aspire V3-_0648_V2.07 dmi.product.version: V2.07 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1 version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1
[Desktop-packages] [Bug 1887294] [NEW] Display freeze
Public bug reported: The display is completely frozen, and no signal is output to the monitors. There is also no signal when switching to a console (Ctr- Alt-F1). I have normal access via SSH. It happens about once in 14 days. Only happens when turning the display off or on (about once in 15 screen power cycles). nvidia-smi still works (via SSH; without any options) DISPLAY=:1 xset dpms force on hangs indefinitely. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-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.100 Fri May 29 08:45:51 UTC 2020 GCC version: ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 BootLog: CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Sun Jul 12 17:47:58 2020 DistUpgraded: 2020-05-17 13:48:43,365 DEBUG entry '# deb [arch=amd64] https://repo.skype.com/deb stable main # disabled on upgrade to focal' was disabled (unknown mirror) DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 440.100, 5.4.0-39-generic, x86_64: installed nvidia, 440.100, 5.4.0-40-generic, x86_64: installed (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) v4l2loopback, 0.12.3, 5.4.0-39-generic, x86_64: installed v4l2loopback, 0.12.3, 5.4.0-40-generic, x86_64: installed ExtraDebuggingInterest: Yes GpuHangFrequency: Very infrequently GraphicsCard: NVIDIA Corporation GP106 [GeForce GTX 1060 6GB] [10de:1c03] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP106 [GeForce GTX 1060 6GB] [1043:85ae] InstallationDate: Installed on 2016-07-27 (1445 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic root=/dev/mapper/ubuntu--vg-root ro splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to focal on 2020-05-17 (56 days ago) dmi.bios.date: 04/17/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3601 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8C WS 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.:bvr3601:bd04/17/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8CWS:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1 version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1 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 Jul 7 22:02:38 2020 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.20.8-2ubuntu2.1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal freeze possible-manual-nvidia-install ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1887294 Title: Display freeze Status in xorg package in Ubuntu: New Bug description: The display is completely frozen, and no signal is output to the monitors. There is also no signal when switching to a console (Ctr- Alt-F1). I have normal access via SSH. It happens about once in 14 days. Only happens when turning the display off or on (about once in 15 screen power cycles). nvidia-smi still works (via SSH; without any options) DISPLAY=:1 xset dpms force on hangs indefinitely. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14
[Desktop-packages] [Bug 1887287] [NEW] No show-desktop shortcut out of the box since 18.04
Public bug reported: On Ubuntu 16.04 I was used to the keyboard shortcut ctrl+Super+D to reveal the Desktop by minimizing all windows (it was not exactly the same as minimizing all windows but whatever). That shortcut was changed at almost every major release, which was already irritating enough, but at least there always was one. Now, however, there doesn't seem to be any half-discoverable keyboard shortcut to show the desktop. I have tried Super+D, Ctrl+Alt+D (both mentioned in a bullshit article I found out by googling), and every other similar combination I can think of involving a D. Nothing works. I shouldn't have to install a tool and create a shortcut to it just to reveal the desktop. It's something basic. Especially considering that it used to be available out of the box. So sick of Ubuntu going backwards. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-62.56-generic 5.3.18 Uname: Linux 5.3.0-62-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.108 Wed Dec 11 11:06:58 PST 2019 GCC version: gcc version 9.2.1 20191008 (Ubuntu 9.2.1-9ubuntu2) .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu8.9 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Jul 12 15:30:58 2020 DistUpgraded: 2020-07-12 15:02:52,488 DEBUG running apport_crash() DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia-340, 340.108, 4.15.0-109-generic, x86_64: installed nvidia-340, 340.108, 4.4.0-185-generic, x86_64: installed nvidia-340, 340.108, 5.3.0-62-generic, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] 3rd Gen Core processor Graphics Controller [1025:0647] NVIDIA Corporation GF117M [GeForce 610M/710M/810M/820M / GT 620M/625M/630M/720M] [10de:1140] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] GeForce 710M [1025:0691] InstallationDate: Installed on 2013-10-11 (2465 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: Acer Aspire V3-571G ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-62-generic root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to eoan on 2020-07-12 (0 days ago) dmi.bios.date: 10/15/2012 dmi.bios.vendor: Acer dmi.bios.version: V2.07 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: VA50_HC_CR dmi.board.vendor: Acer dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.07 dmi.modalias: dmi:bvnAcer:bvrV2.07:bd10/15/2012:svnAcer:pnAspireV3-571G:pvrV2.07:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnAcer:ct10:cvrV2.07: dmi.product.family: Type1Family dmi.product.name: Aspire V3-571G dmi.product.sku: Aspire V3-_0648_V2.07 dmi.product.version: V2.07 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.14.0+19.10.20190918-0ubuntu1 version.libdrm2: libdrm2 2.4.101-2~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~19.10.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~19.10.3 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1 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 xserver.bootTime: Sun Jul 12 15:12:31 2020 xserver.configfile: default xserver.errors: modeset(G0): eglGetDisplay() failed modeset(G0): glamor initialization failed NVIDIA(0): Failed to initiate mode change. NVIDIA(0): Failed to complete mode change xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.20.5+git20191008-0ubuntu1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan third-party-packages 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/1887287 Title: No show-desktop shortcut out of the box since 18.04 Status in xorg package in Ubuntu: New Bug description: On Ubuntu 16.04 I was used to the keyboard shortcut ctrl+Super+D to reveal the Desktop by minimizing all windows (it was not exactly the same as minimizing all windows but whatever). That shortcut was changed at
[Desktop-packages] [Bug 1881401] Re: HPLIP, hp-doctor, hp-check should support Ubuntu 20.04 LTS with its package base
By running hp-setup, I am able to add my device, however it shows "Device communication error" with error code 5012. ** Attachment added: "Screenshot showing error message from HP Toolbox" https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/1881401/+attachment/5391950/+files/hptoolbox-devicecommunicationerror-1.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/1881401 Title: HPLIP, hp-doctor, hp-check should support Ubuntu 20.04 LTS with its package base Status in HPLIP: In Progress Status in hplip package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Have Ubuntu 20.04 LTS installed 2. Install HPLIP with `sudo apt-get install hplip-gui` 3. Install all stuff to satisfy `hp-doctor` requirements by: sudo apt-get build-dep hplip sudo apt-get install build-essential libtool libtool-bin libcups2-dev cups-bsd cups-client avahi-utils gtk2-engines-pixbuf xsane python3-notify2 4. Run `hp-doctor` and `hp-check` Expected results: * `hp-doctor` ran successfully without errors * `hp-check` ran successfully without errors Actual results: ``` $ hp-doctor HP Linux Imaging and Printing System (ver. 3.20.3) Self Diagnse Utility and Healing Utility ver. 1.0 ... Checking for Dependencies warning: ubuntu-20.04 version is not supported. Using ubuntu-19.10 versions dependencies to verify and install... ... -- | PERMISSION | -- Missing Required Dependencies - error: 'libcups2' package is missing or 'cups' service is not running. error: 'python3-pyqt4' package is missing/incompatible error: 'gtk2-engines-pixbuf' package is missing/incompatible Missing Optional Dependencies - error: 'python3-dbus.mainloop.qt' package is missing/incompatible ... $ hp-check Saving output in log file: /home/mate/hp-check.log HP Linux Imaging and Printing System (ver. 3.20.3) Dependency/Version Check Utility ver. 15.1 ... --- | SUMMARY | --- Missing Required Dependencies - error: 'libcups2' package is missing/incompatible error: 'python3-pyqt4' package is missing/incompatible error: 'gtk2-engines-pixbuf' package is missing/incompatible Missing Optional Dependencies - error: 'python3-dbus.mainloop.qt' package is missing/incompatible Total Errors: 3 Total Warnings: 0 Done. ``` Note: many mentioned packages are already installed, Qt4 related packages are not installable: ``` $ sudo apt-get install libcups2 libcups2-dev Reading package lists... Done Building dependency tree Reading state information... Done libcups2 is already the newest version (2.3.1-9ubuntu1.1). libcups2-dev is already the newest version (2.3.1-9ubuntu1.1). 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. $ sudo apt-get install gtk2-engines-pixbuf Reading package lists... Done Building dependency tree Reading state information... Done gtk2-engines-pixbuf is already the newest version (2.24.32-4ubuntu4). 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. $ sudo apt-get install python3-pyqt4 Reading package lists... Done Building dependency tree Reading state information... Done E: Unable to locate package python3-pyqt4 $ sudo apt-get install python3-dbus.mainloop.qt Reading package lists... Done Building dependency tree Reading state information... Done E: Unable to locate package python3-dbus.mainloop.qt E: Couldn't find any package by glob 'python3-dbus.mainloop.qt' E: Couldn't find any package by regex 'python3-dbus.mainloop.qt' ``` Please consider to fix HPLIP package and support 20.04 LTS package base before 20.04.1 release! ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: hplip 3.20.3+dfsg0-2 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: MATE Date: Sat May 30 12:25:39 2020 InstallationDate: Installed on 2020-04-23 (36 days ago) InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added. Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/12p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/12p, 480M MachineType:
[Desktop-packages] [Bug 1881401] Re: HPLIP, hp-doctor, hp-check should support Ubuntu 20.04 LTS with its package base
Screenshot showing error code (HP Toolbox). ** Attachment added: "hptoolbox-devicecommunicationerror-2.png" https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/1881401/+attachment/5391951/+files/hptoolbox-devicecommunicationerror-2.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/1881401 Title: HPLIP, hp-doctor, hp-check should support Ubuntu 20.04 LTS with its package base Status in HPLIP: In Progress Status in hplip package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Have Ubuntu 20.04 LTS installed 2. Install HPLIP with `sudo apt-get install hplip-gui` 3. Install all stuff to satisfy `hp-doctor` requirements by: sudo apt-get build-dep hplip sudo apt-get install build-essential libtool libtool-bin libcups2-dev cups-bsd cups-client avahi-utils gtk2-engines-pixbuf xsane python3-notify2 4. Run `hp-doctor` and `hp-check` Expected results: * `hp-doctor` ran successfully without errors * `hp-check` ran successfully without errors Actual results: ``` $ hp-doctor HP Linux Imaging and Printing System (ver. 3.20.3) Self Diagnse Utility and Healing Utility ver. 1.0 ... Checking for Dependencies warning: ubuntu-20.04 version is not supported. Using ubuntu-19.10 versions dependencies to verify and install... ... -- | PERMISSION | -- Missing Required Dependencies - error: 'libcups2' package is missing or 'cups' service is not running. error: 'python3-pyqt4' package is missing/incompatible error: 'gtk2-engines-pixbuf' package is missing/incompatible Missing Optional Dependencies - error: 'python3-dbus.mainloop.qt' package is missing/incompatible ... $ hp-check Saving output in log file: /home/mate/hp-check.log HP Linux Imaging and Printing System (ver. 3.20.3) Dependency/Version Check Utility ver. 15.1 ... --- | SUMMARY | --- Missing Required Dependencies - error: 'libcups2' package is missing/incompatible error: 'python3-pyqt4' package is missing/incompatible error: 'gtk2-engines-pixbuf' package is missing/incompatible Missing Optional Dependencies - error: 'python3-dbus.mainloop.qt' package is missing/incompatible Total Errors: 3 Total Warnings: 0 Done. ``` Note: many mentioned packages are already installed, Qt4 related packages are not installable: ``` $ sudo apt-get install libcups2 libcups2-dev Reading package lists... Done Building dependency tree Reading state information... Done libcups2 is already the newest version (2.3.1-9ubuntu1.1). libcups2-dev is already the newest version (2.3.1-9ubuntu1.1). 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. $ sudo apt-get install gtk2-engines-pixbuf Reading package lists... Done Building dependency tree Reading state information... Done gtk2-engines-pixbuf is already the newest version (2.24.32-4ubuntu4). 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. $ sudo apt-get install python3-pyqt4 Reading package lists... Done Building dependency tree Reading state information... Done E: Unable to locate package python3-pyqt4 $ sudo apt-get install python3-dbus.mainloop.qt Reading package lists... Done Building dependency tree Reading state information... Done E: Unable to locate package python3-dbus.mainloop.qt E: Couldn't find any package by glob 'python3-dbus.mainloop.qt' E: Couldn't find any package by regex 'python3-dbus.mainloop.qt' ``` Please consider to fix HPLIP package and support 20.04 LTS package base before 20.04.1 release! ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: hplip 3.20.3+dfsg0-2 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: MATE Date: Sat May 30 12:25:39 2020 InstallationDate: Installed on 2020-04-23 (36 days ago) InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added. Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/12p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/12p, 480M MachineType: innotek GmbH VirtualBox Papersize: a4 ProcKernelCmdLine:
[Desktop-packages] [Bug 1887285] [NEW] Restore the "open with" submenu
Public bug reported: Up until a few hours ago I was using Ubuntu 16.04. When right-clicking on a file in Nautilus, the context menu used to have a submenu, right next to the "open with " option, called "open with...", where the items in the submenu were the most common applications. Half of the times I open files with some of those (but the other half I do open the same file with the default application, so changing the default is not good enough for me, also I don't like to do that). So, having the submenu was very useful to me (and millions of other users). After upgrading to 18.10 and now 19.10, that submenu is gone. Now you have to click on "open with another application", wait for a completely separate, bloated popup to load and show up somewhere else, and then select the application to open the file with. This looks like it can only have been done by design, so I guess it's yet another idiotic decision made by the lunatics that maintain Nautilus, who clearly don't give two minutes of thought to what they are doing. This is ridiculous and has to be reverted. Since it has been proven that upstream Gnome developers can't be trusted to have any common sense and hence are very unlikely to be inclined to fix this, if Ubuntu insists in keeping Nautilus as the chosen default file manager, Ubuntu should patch this. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: nautilus 1:3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-62.56-generic 5.3.18 Uname: Linux 5.3.0-62-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.11-0ubuntu8.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Jul 12 15:21:02 2020 GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'192' b'org.gnome.nautilus.list-view' b'use-tree-view' b'true' b'org.gnome.nautilus.list-view' b'default-visible-columns' b"['name', 'size', 'type', 'date_modified']" 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 (2465 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: nautilus UpgradeStatus: Upgraded to eoan on 2020-07-12 (0 days ago) usr_lib_nautilus: ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan third-party-packages -- 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/1887285 Title: Restore the "open with" submenu Status in nautilus package in Ubuntu: New Bug description: Up until a few hours ago I was using Ubuntu 16.04. When right-clicking on a file in Nautilus, the context menu used to have a submenu, right next to the "open with " option, called "open with...", where the items in the submenu were the most common applications. Half of the times I open files with some of those (but the other half I do open the same file with the default application, so changing the default is not good enough for me, also I don't like to do that). So, having the submenu was very useful to me (and millions of other users). After upgrading to 18.10 and now 19.10, that submenu is gone. Now you have to click on "open with another application", wait for a completely separate, bloated popup to load and show up somewhere else, and then select the application to open the file with. This looks like it can only have been done by design, so I guess it's yet another idiotic decision made by the lunatics that maintain Nautilus, who clearly don't give two minutes of thought to what they are doing. This is ridiculous and has to be reverted. Since it has been proven that upstream Gnome developers can't be trusted to have any common sense and hence are very unlikely to be inclined to fix this, if Ubuntu insists in keeping Nautilus as the chosen default file manager, Ubuntu should patch this. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: nautilus 1:3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-62.56-generic 5.3.18 Uname: Linux 5.3.0-62-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.11-0ubuntu8.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Jul 12 15:21:02 2020 GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'192' b'org.gnome.nautilus.list-view' b'use-tree-view' b'true' b'org.gnome.nautilus.list-view' b'default-visible-columns' b"['name', 'size', 'type', 'date_modified']" 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 (2465 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
[Desktop-packages] [Bug 1881401] Re: HPLIP, hp-doctor, hp-check should support Ubuntu 20.04 LTS with its package base
Screenshot of auto-detected printer in the Gnome Control Center ** Attachment added: "Printer listed n Gnome Control Center" https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/1881401/+attachment/5391945/+files/printer-gnomecontrolcenter.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/1881401 Title: HPLIP, hp-doctor, hp-check should support Ubuntu 20.04 LTS with its package base Status in HPLIP: In Progress Status in hplip package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Have Ubuntu 20.04 LTS installed 2. Install HPLIP with `sudo apt-get install hplip-gui` 3. Install all stuff to satisfy `hp-doctor` requirements by: sudo apt-get build-dep hplip sudo apt-get install build-essential libtool libtool-bin libcups2-dev cups-bsd cups-client avahi-utils gtk2-engines-pixbuf xsane python3-notify2 4. Run `hp-doctor` and `hp-check` Expected results: * `hp-doctor` ran successfully without errors * `hp-check` ran successfully without errors Actual results: ``` $ hp-doctor HP Linux Imaging and Printing System (ver. 3.20.3) Self Diagnse Utility and Healing Utility ver. 1.0 ... Checking for Dependencies warning: ubuntu-20.04 version is not supported. Using ubuntu-19.10 versions dependencies to verify and install... ... -- | PERMISSION | -- Missing Required Dependencies - error: 'libcups2' package is missing or 'cups' service is not running. error: 'python3-pyqt4' package is missing/incompatible error: 'gtk2-engines-pixbuf' package is missing/incompatible Missing Optional Dependencies - error: 'python3-dbus.mainloop.qt' package is missing/incompatible ... $ hp-check Saving output in log file: /home/mate/hp-check.log HP Linux Imaging and Printing System (ver. 3.20.3) Dependency/Version Check Utility ver. 15.1 ... --- | SUMMARY | --- Missing Required Dependencies - error: 'libcups2' package is missing/incompatible error: 'python3-pyqt4' package is missing/incompatible error: 'gtk2-engines-pixbuf' package is missing/incompatible Missing Optional Dependencies - error: 'python3-dbus.mainloop.qt' package is missing/incompatible Total Errors: 3 Total Warnings: 0 Done. ``` Note: many mentioned packages are already installed, Qt4 related packages are not installable: ``` $ sudo apt-get install libcups2 libcups2-dev Reading package lists... Done Building dependency tree Reading state information... Done libcups2 is already the newest version (2.3.1-9ubuntu1.1). libcups2-dev is already the newest version (2.3.1-9ubuntu1.1). 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. $ sudo apt-get install gtk2-engines-pixbuf Reading package lists... Done Building dependency tree Reading state information... Done gtk2-engines-pixbuf is already the newest version (2.24.32-4ubuntu4). 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. $ sudo apt-get install python3-pyqt4 Reading package lists... Done Building dependency tree Reading state information... Done E: Unable to locate package python3-pyqt4 $ sudo apt-get install python3-dbus.mainloop.qt Reading package lists... Done Building dependency tree Reading state information... Done E: Unable to locate package python3-dbus.mainloop.qt E: Couldn't find any package by glob 'python3-dbus.mainloop.qt' E: Couldn't find any package by regex 'python3-dbus.mainloop.qt' ``` Please consider to fix HPLIP package and support 20.04 LTS package base before 20.04.1 release! ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: hplip 3.20.3+dfsg0-2 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: MATE Date: Sat May 30 12:25:39 2020 InstallationDate: Installed on 2020-04-23 (36 days ago) InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added. Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/12p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/12p, 480M MachineType: innotek GmbH VirtualBox Papersize: a4 ProcKernelCmdLine:
[Desktop-packages] [Bug 1881401] Re: HPLIP, hp-doctor, hp-check should support Ubuntu 20.04 LTS with its package base
HP Toolbox showing no devices. ** Attachment added: "printer-hplip.png" https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/1881401/+attachment/5391949/+files/printer-hplip.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/1881401 Title: HPLIP, hp-doctor, hp-check should support Ubuntu 20.04 LTS with its package base Status in HPLIP: In Progress Status in hplip package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Have Ubuntu 20.04 LTS installed 2. Install HPLIP with `sudo apt-get install hplip-gui` 3. Install all stuff to satisfy `hp-doctor` requirements by: sudo apt-get build-dep hplip sudo apt-get install build-essential libtool libtool-bin libcups2-dev cups-bsd cups-client avahi-utils gtk2-engines-pixbuf xsane python3-notify2 4. Run `hp-doctor` and `hp-check` Expected results: * `hp-doctor` ran successfully without errors * `hp-check` ran successfully without errors Actual results: ``` $ hp-doctor HP Linux Imaging and Printing System (ver. 3.20.3) Self Diagnse Utility and Healing Utility ver. 1.0 ... Checking for Dependencies warning: ubuntu-20.04 version is not supported. Using ubuntu-19.10 versions dependencies to verify and install... ... -- | PERMISSION | -- Missing Required Dependencies - error: 'libcups2' package is missing or 'cups' service is not running. error: 'python3-pyqt4' package is missing/incompatible error: 'gtk2-engines-pixbuf' package is missing/incompatible Missing Optional Dependencies - error: 'python3-dbus.mainloop.qt' package is missing/incompatible ... $ hp-check Saving output in log file: /home/mate/hp-check.log HP Linux Imaging and Printing System (ver. 3.20.3) Dependency/Version Check Utility ver. 15.1 ... --- | SUMMARY | --- Missing Required Dependencies - error: 'libcups2' package is missing/incompatible error: 'python3-pyqt4' package is missing/incompatible error: 'gtk2-engines-pixbuf' package is missing/incompatible Missing Optional Dependencies - error: 'python3-dbus.mainloop.qt' package is missing/incompatible Total Errors: 3 Total Warnings: 0 Done. ``` Note: many mentioned packages are already installed, Qt4 related packages are not installable: ``` $ sudo apt-get install libcups2 libcups2-dev Reading package lists... Done Building dependency tree Reading state information... Done libcups2 is already the newest version (2.3.1-9ubuntu1.1). libcups2-dev is already the newest version (2.3.1-9ubuntu1.1). 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. $ sudo apt-get install gtk2-engines-pixbuf Reading package lists... Done Building dependency tree Reading state information... Done gtk2-engines-pixbuf is already the newest version (2.24.32-4ubuntu4). 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. $ sudo apt-get install python3-pyqt4 Reading package lists... Done Building dependency tree Reading state information... Done E: Unable to locate package python3-pyqt4 $ sudo apt-get install python3-dbus.mainloop.qt Reading package lists... Done Building dependency tree Reading state information... Done E: Unable to locate package python3-dbus.mainloop.qt E: Couldn't find any package by glob 'python3-dbus.mainloop.qt' E: Couldn't find any package by regex 'python3-dbus.mainloop.qt' ``` Please consider to fix HPLIP package and support 20.04 LTS package base before 20.04.1 release! ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: hplip 3.20.3+dfsg0-2 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: MATE Date: Sat May 30 12:25:39 2020 InstallationDate: Installed on 2020-04-23 (36 days ago) InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added. Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/12p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/12p, 480M MachineType: innotek GmbH VirtualBox Papersize: a4 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic
[Desktop-packages] [Bug 1881401] Re: HPLIP, hp-doctor, hp-check should support Ubuntu 20.04 LTS with its package base
Printer displayed in CUPS ** Attachment added: "cups-printerlisted.png" https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/1881401/+attachment/5391948/+files/cups-printerlisted.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/1881401 Title: HPLIP, hp-doctor, hp-check should support Ubuntu 20.04 LTS with its package base Status in HPLIP: In Progress Status in hplip package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Have Ubuntu 20.04 LTS installed 2. Install HPLIP with `sudo apt-get install hplip-gui` 3. Install all stuff to satisfy `hp-doctor` requirements by: sudo apt-get build-dep hplip sudo apt-get install build-essential libtool libtool-bin libcups2-dev cups-bsd cups-client avahi-utils gtk2-engines-pixbuf xsane python3-notify2 4. Run `hp-doctor` and `hp-check` Expected results: * `hp-doctor` ran successfully without errors * `hp-check` ran successfully without errors Actual results: ``` $ hp-doctor HP Linux Imaging and Printing System (ver. 3.20.3) Self Diagnse Utility and Healing Utility ver. 1.0 ... Checking for Dependencies warning: ubuntu-20.04 version is not supported. Using ubuntu-19.10 versions dependencies to verify and install... ... -- | PERMISSION | -- Missing Required Dependencies - error: 'libcups2' package is missing or 'cups' service is not running. error: 'python3-pyqt4' package is missing/incompatible error: 'gtk2-engines-pixbuf' package is missing/incompatible Missing Optional Dependencies - error: 'python3-dbus.mainloop.qt' package is missing/incompatible ... $ hp-check Saving output in log file: /home/mate/hp-check.log HP Linux Imaging and Printing System (ver. 3.20.3) Dependency/Version Check Utility ver. 15.1 ... --- | SUMMARY | --- Missing Required Dependencies - error: 'libcups2' package is missing/incompatible error: 'python3-pyqt4' package is missing/incompatible error: 'gtk2-engines-pixbuf' package is missing/incompatible Missing Optional Dependencies - error: 'python3-dbus.mainloop.qt' package is missing/incompatible Total Errors: 3 Total Warnings: 0 Done. ``` Note: many mentioned packages are already installed, Qt4 related packages are not installable: ``` $ sudo apt-get install libcups2 libcups2-dev Reading package lists... Done Building dependency tree Reading state information... Done libcups2 is already the newest version (2.3.1-9ubuntu1.1). libcups2-dev is already the newest version (2.3.1-9ubuntu1.1). 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. $ sudo apt-get install gtk2-engines-pixbuf Reading package lists... Done Building dependency tree Reading state information... Done gtk2-engines-pixbuf is already the newest version (2.24.32-4ubuntu4). 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. $ sudo apt-get install python3-pyqt4 Reading package lists... Done Building dependency tree Reading state information... Done E: Unable to locate package python3-pyqt4 $ sudo apt-get install python3-dbus.mainloop.qt Reading package lists... Done Building dependency tree Reading state information... Done E: Unable to locate package python3-dbus.mainloop.qt E: Couldn't find any package by glob 'python3-dbus.mainloop.qt' E: Couldn't find any package by regex 'python3-dbus.mainloop.qt' ``` Please consider to fix HPLIP package and support 20.04 LTS package base before 20.04.1 release! ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: hplip 3.20.3+dfsg0-2 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: MATE Date: Sat May 30 12:25:39 2020 InstallationDate: Installed on 2020-04-23 (36 days ago) InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added. Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/12p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/12p, 480M MachineType: innotek GmbH VirtualBox Papersize: a4 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic
[Desktop-packages] [Bug 1881401] Re: HPLIP, hp-doctor, hp-check should support Ubuntu 20.04 LTS with its package base
Scanner error displayed by SimpleScan ** Attachment added: "Scanner error displayed by SimpleScan" https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/1881401/+attachment/5391947/+files/scanner-error.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/1881401 Title: HPLIP, hp-doctor, hp-check should support Ubuntu 20.04 LTS with its package base Status in HPLIP: In Progress Status in hplip package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Have Ubuntu 20.04 LTS installed 2. Install HPLIP with `sudo apt-get install hplip-gui` 3. Install all stuff to satisfy `hp-doctor` requirements by: sudo apt-get build-dep hplip sudo apt-get install build-essential libtool libtool-bin libcups2-dev cups-bsd cups-client avahi-utils gtk2-engines-pixbuf xsane python3-notify2 4. Run `hp-doctor` and `hp-check` Expected results: * `hp-doctor` ran successfully without errors * `hp-check` ran successfully without errors Actual results: ``` $ hp-doctor HP Linux Imaging and Printing System (ver. 3.20.3) Self Diagnse Utility and Healing Utility ver. 1.0 ... Checking for Dependencies warning: ubuntu-20.04 version is not supported. Using ubuntu-19.10 versions dependencies to verify and install... ... -- | PERMISSION | -- Missing Required Dependencies - error: 'libcups2' package is missing or 'cups' service is not running. error: 'python3-pyqt4' package is missing/incompatible error: 'gtk2-engines-pixbuf' package is missing/incompatible Missing Optional Dependencies - error: 'python3-dbus.mainloop.qt' package is missing/incompatible ... $ hp-check Saving output in log file: /home/mate/hp-check.log HP Linux Imaging and Printing System (ver. 3.20.3) Dependency/Version Check Utility ver. 15.1 ... --- | SUMMARY | --- Missing Required Dependencies - error: 'libcups2' package is missing/incompatible error: 'python3-pyqt4' package is missing/incompatible error: 'gtk2-engines-pixbuf' package is missing/incompatible Missing Optional Dependencies - error: 'python3-dbus.mainloop.qt' package is missing/incompatible Total Errors: 3 Total Warnings: 0 Done. ``` Note: many mentioned packages are already installed, Qt4 related packages are not installable: ``` $ sudo apt-get install libcups2 libcups2-dev Reading package lists... Done Building dependency tree Reading state information... Done libcups2 is already the newest version (2.3.1-9ubuntu1.1). libcups2-dev is already the newest version (2.3.1-9ubuntu1.1). 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. $ sudo apt-get install gtk2-engines-pixbuf Reading package lists... Done Building dependency tree Reading state information... Done gtk2-engines-pixbuf is already the newest version (2.24.32-4ubuntu4). 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. $ sudo apt-get install python3-pyqt4 Reading package lists... Done Building dependency tree Reading state information... Done E: Unable to locate package python3-pyqt4 $ sudo apt-get install python3-dbus.mainloop.qt Reading package lists... Done Building dependency tree Reading state information... Done E: Unable to locate package python3-dbus.mainloop.qt E: Couldn't find any package by glob 'python3-dbus.mainloop.qt' E: Couldn't find any package by regex 'python3-dbus.mainloop.qt' ``` Please consider to fix HPLIP package and support 20.04 LTS package base before 20.04.1 release! ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: hplip 3.20.3+dfsg0-2 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: MATE Date: Sat May 30 12:25:39 2020 InstallationDate: Installed on 2020-04-23 (36 days ago) InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added. Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/12p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/12p, 480M MachineType: innotek GmbH VirtualBox Papersize: a4 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic
[Desktop-packages] [Bug 1881401] Re: HPLIP, hp-doctor, hp-check should support Ubuntu 20.04 LTS with its package base
Scanner listed/detected by SimpleScan ** Attachment added: "scanner-detected-simplescan.png" https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/1881401/+attachment/5391946/+files/scanner-detected-simplescan.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/1881401 Title: HPLIP, hp-doctor, hp-check should support Ubuntu 20.04 LTS with its package base Status in HPLIP: In Progress Status in hplip package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Have Ubuntu 20.04 LTS installed 2. Install HPLIP with `sudo apt-get install hplip-gui` 3. Install all stuff to satisfy `hp-doctor` requirements by: sudo apt-get build-dep hplip sudo apt-get install build-essential libtool libtool-bin libcups2-dev cups-bsd cups-client avahi-utils gtk2-engines-pixbuf xsane python3-notify2 4. Run `hp-doctor` and `hp-check` Expected results: * `hp-doctor` ran successfully without errors * `hp-check` ran successfully without errors Actual results: ``` $ hp-doctor HP Linux Imaging and Printing System (ver. 3.20.3) Self Diagnse Utility and Healing Utility ver. 1.0 ... Checking for Dependencies warning: ubuntu-20.04 version is not supported. Using ubuntu-19.10 versions dependencies to verify and install... ... -- | PERMISSION | -- Missing Required Dependencies - error: 'libcups2' package is missing or 'cups' service is not running. error: 'python3-pyqt4' package is missing/incompatible error: 'gtk2-engines-pixbuf' package is missing/incompatible Missing Optional Dependencies - error: 'python3-dbus.mainloop.qt' package is missing/incompatible ... $ hp-check Saving output in log file: /home/mate/hp-check.log HP Linux Imaging and Printing System (ver. 3.20.3) Dependency/Version Check Utility ver. 15.1 ... --- | SUMMARY | --- Missing Required Dependencies - error: 'libcups2' package is missing/incompatible error: 'python3-pyqt4' package is missing/incompatible error: 'gtk2-engines-pixbuf' package is missing/incompatible Missing Optional Dependencies - error: 'python3-dbus.mainloop.qt' package is missing/incompatible Total Errors: 3 Total Warnings: 0 Done. ``` Note: many mentioned packages are already installed, Qt4 related packages are not installable: ``` $ sudo apt-get install libcups2 libcups2-dev Reading package lists... Done Building dependency tree Reading state information... Done libcups2 is already the newest version (2.3.1-9ubuntu1.1). libcups2-dev is already the newest version (2.3.1-9ubuntu1.1). 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. $ sudo apt-get install gtk2-engines-pixbuf Reading package lists... Done Building dependency tree Reading state information... Done gtk2-engines-pixbuf is already the newest version (2.24.32-4ubuntu4). 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. $ sudo apt-get install python3-pyqt4 Reading package lists... Done Building dependency tree Reading state information... Done E: Unable to locate package python3-pyqt4 $ sudo apt-get install python3-dbus.mainloop.qt Reading package lists... Done Building dependency tree Reading state information... Done E: Unable to locate package python3-dbus.mainloop.qt E: Couldn't find any package by glob 'python3-dbus.mainloop.qt' E: Couldn't find any package by regex 'python3-dbus.mainloop.qt' ``` Please consider to fix HPLIP package and support 20.04 LTS package base before 20.04.1 release! ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: hplip 3.20.3+dfsg0-2 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: MATE Date: Sat May 30 12:25:39 2020 InstallationDate: Installed on 2020-04-23 (36 days ago) InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added. Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/12p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/12p, 480M MachineType: innotek GmbH VirtualBox Papersize: a4 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic
[Desktop-packages] [Bug 1881401] Re: HPLIP, hp-doctor, hp-check should support Ubuntu 20.04 LTS with its package base
It seems I may have spoken too soon... So I got the both the printer and the scanner working, however on next boot, it had reverted right back to only the being able to print. Any attempt to scan resulted in the "Can't communicate with the device" error message. Interestingly, *something* appears to automatically detect both the printer and scanner, as both the Gnome Control Center and Simple Scan list my device. However, this apparently doesn't extend to HPLIP toolbox. I have attached a copy the output from hp-check -i ** Attachment added: "Output from command hpcheck -i" https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/1881401/+attachment/5391944/+files/hp-check.log -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/1881401 Title: HPLIP, hp-doctor, hp-check should support Ubuntu 20.04 LTS with its package base Status in HPLIP: In Progress Status in hplip package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Have Ubuntu 20.04 LTS installed 2. Install HPLIP with `sudo apt-get install hplip-gui` 3. Install all stuff to satisfy `hp-doctor` requirements by: sudo apt-get build-dep hplip sudo apt-get install build-essential libtool libtool-bin libcups2-dev cups-bsd cups-client avahi-utils gtk2-engines-pixbuf xsane python3-notify2 4. Run `hp-doctor` and `hp-check` Expected results: * `hp-doctor` ran successfully without errors * `hp-check` ran successfully without errors Actual results: ``` $ hp-doctor HP Linux Imaging and Printing System (ver. 3.20.3) Self Diagnse Utility and Healing Utility ver. 1.0 ... Checking for Dependencies warning: ubuntu-20.04 version is not supported. Using ubuntu-19.10 versions dependencies to verify and install... ... -- | PERMISSION | -- Missing Required Dependencies - error: 'libcups2' package is missing or 'cups' service is not running. error: 'python3-pyqt4' package is missing/incompatible error: 'gtk2-engines-pixbuf' package is missing/incompatible Missing Optional Dependencies - error: 'python3-dbus.mainloop.qt' package is missing/incompatible ... $ hp-check Saving output in log file: /home/mate/hp-check.log HP Linux Imaging and Printing System (ver. 3.20.3) Dependency/Version Check Utility ver. 15.1 ... --- | SUMMARY | --- Missing Required Dependencies - error: 'libcups2' package is missing/incompatible error: 'python3-pyqt4' package is missing/incompatible error: 'gtk2-engines-pixbuf' package is missing/incompatible Missing Optional Dependencies - error: 'python3-dbus.mainloop.qt' package is missing/incompatible Total Errors: 3 Total Warnings: 0 Done. ``` Note: many mentioned packages are already installed, Qt4 related packages are not installable: ``` $ sudo apt-get install libcups2 libcups2-dev Reading package lists... Done Building dependency tree Reading state information... Done libcups2 is already the newest version (2.3.1-9ubuntu1.1). libcups2-dev is already the newest version (2.3.1-9ubuntu1.1). 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. $ sudo apt-get install gtk2-engines-pixbuf Reading package lists... Done Building dependency tree Reading state information... Done gtk2-engines-pixbuf is already the newest version (2.24.32-4ubuntu4). 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. $ sudo apt-get install python3-pyqt4 Reading package lists... Done Building dependency tree Reading state information... Done E: Unable to locate package python3-pyqt4 $ sudo apt-get install python3-dbus.mainloop.qt Reading package lists... Done Building dependency tree Reading state information... Done E: Unable to locate package python3-dbus.mainloop.qt E: Couldn't find any package by glob 'python3-dbus.mainloop.qt' E: Couldn't find any package by regex 'python3-dbus.mainloop.qt' ``` Please consider to fix HPLIP package and support 20.04 LTS package base before 20.04.1 release! ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: hplip 3.20.3+dfsg0-2 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: MATE Date: Sat May 30 12:25:39 2020 InstallationDate: Installed on 2020-04-23 (36 days ago) InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added. Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
[Desktop-packages] [Bug 1879968] Re: copy/paste still sometimes fails in LibreOffice on mutter 3.36.2
I'd really like to test this (on 20.04), but there is no sign of it yet, even as a developer option pre-release. -- 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/1879968 Title: copy/paste still sometimes fails in LibreOffice on mutter 3.36.2 Status in Mutter: Fix Released Status in mutter package in Ubuntu: Confirmed Bug description: In Ubuntu 19.10 and 20.04 there was a bug that caused copy and paste operations to fail pretty often: the text that was pasted was not the text that was just copied. See the long discussion at bug #1852183. The bug was recently marked closed, since the package mutter - 3.36.2-1ubuntu1~20.04.1 landed in focal-updates and makes the bug occur much less frequently. Unfortunately the bug still exists, and is not difficult to reproduce. I am running Ubuntu 20.04 and have the new 3.36.2-1ubuntu1~20.04.1 version of mutter. I just opened two LibreOffice Writer windows side by side, and repeatedly selected some text in the left window, copied it, then attempted to paste it into the right window. In my experiment, approximately 1 in every 20 paste operations failed: it did not paste the text that was just copied, but instead the text that was copied before that. Now, an error rate of 1 in 20 may not seem so bad. On the other hand, if you spend all day writing a document and copy and paste dozens of times during the day, then you may hit this bug multiple times per day (as I have been recently), which is a significant annoyance. I tested in LibreOffice since that is where I have seen the bug most often, but I have also seen it occur in other applications as well. To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1879968/+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 1845801] Re: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.
The attachment "vt_handoff.patch" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.] ** Tags added: patch -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1845801 Title: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login. Status in OEM Priority Project: New Status in gdm3 package in Ubuntu: Confirmed Status in gnome-session package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-430 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-435 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-440 package in Ubuntu: Confirmed Status in gdm3 source package in Eoan: Confirmed Status in gnome-session source package in Eoan: Confirmed Status in nvidia-graphics-drivers-435 source package in Eoan: Confirmed Bug description: I just updated to the Ubuntu 19.10 beta. After boot, I'm shown the GDM login screen (which I shouldn't; I have auto login enabled), and logging in just takes me back to the same user selection screen even though the password is correct. If I switch to a TTY and run `sudo pkill gnome-session-binary`, logging in through GDM starts working again. I should add that the do-release-upgrade was rocky; I did it in a terminal from within gnome, went away for a while, and when I returned, I just saw an Ubuntu 19.10 in a TTY. I was able to do `sudo dpkg --configure -a` and complete the upgrade, but I don't know if something's still messed up due to that. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 NonfreeKernelModules: 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 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 9.2.1 20190909 (Ubuntu 9.2.1-8ubuntu1) ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Sep 28 19:55:42 2019 DistUpgraded: 2019-09-28 18:35:15,142 INFO cache.commit() DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia, 435.21, 5.3.0-13-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP102 [GeForce GTX 1080 Ti] [1043:85e4] InstallationDate: Installed on 2019-09-14 (13 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: MSI MS-7A67 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-13-generic root=UUID=04974c80-e732-49b6-8148-c3dce7c02a25 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to eoan on 2019-09-28 (0 days ago) dmi.bios.date: 01/25/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.60 dmi.board.asset.tag: Default string dmi.board.name: H270I GAMING PRO AC (MS-7A67) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.60:bd01/25/2018:svnMSI:pnMS-7A67:pvr1.0:rvnMSI:rnH270IGAMINGPROAC(MS-7A67):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.family: Default string dmi.product.name: MS-7A67 dmi.product.sku: Default string dmi.product.version: 1.0 dmi.sys.vendor: MSI version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.1.6-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20190820-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-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 To manage notifications
[Desktop-packages] [Bug 1887271] Re: Square rectangles instead of system fonts after upgrade
** Package changed: ubuntu => xorg (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/1887271 Title: Square rectangles instead of system fonts after upgrade Status in xorg package in Ubuntu: New Bug description: After upgrading my room mate's Fujitsu Esprimo Desktop PC to 20.04 Focal Fossa (from Bionic 18.04): Any system font line is being displayed distorted / erroneous / in sort of placeholder blocks or SQUARE RECTANGLES, as if the fonts set wouldn't be installed at all... Tthe 'gsettings'-procedure from some link mentioned on askubuntu-com wouldn't help either (with copy into unreadable terminal display font output) Gnome-tweak didn't help, BUT I can copy text from terminal into libreoffice document and thus make it readable afterwards. I cannot find any information about "system font output/printing" on the whole internet leaving me with a mysrltery about how that stuff works from xserver to gnome, Wayland- session login IMPOSSIBLE in order to print the correct display font ... I will attach some screenshots later on if possible. P.S.: firefox/libreoffice fonts are being displayed correctly inside any homepage ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg (not installed) ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Ist ein Verzeichnis: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.108 Wed Dec 11 11:06:58 PST 2019 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2) ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Jul 12 10:55:08 2020 DistUpgraded: 2020-06-29 10:31:32,274 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia-340, 340.108, 5.3.0-51-generic, x86_64: installed nvidia-340, 340.108, 5.4.0-39-generic, x86_64: installed nvidia-340, 340.108, 5.4.0-40-generic, x86_64: installed rtlwifi-new, 0.10: added GraphicsCard: NVIDIA Corporation G84 [GeForce 8600 GT] [10de:0402] (rev a1) (prog-if 00 [VGA controller]) Subsystem: CardExpert Technology G84 [GeForce 8600 GT] [10b0:0801] InstallationDate: Installed on 2017-08-28 (1048 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) LightdmLog: [+6033.49s] DEBUG: Seat seat0 changes active session to [+6033.53s] DEBUG: Seat seat0 changes active session to c5 [+6033.53s] DEBUG: Session c5 is already active MachineType: FUJITSU SIEMENS ESPRIMO P ProcEnviron: LANGUAGE=de_AT:de PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_AT.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz root=/dev/sdb4 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-06-29 (13 days ago) dmi.bios.date: 10/11/2007 dmi.bios.vendor: FUJITSU SIEMENS // Phoenix Technologies Ltd. dmi.bios.version: 6.00 R1.12.2312.A3 dmi.board.name: D2312-A3 dmi.board.vendor: FUJITSU SIEMENS dmi.board.version: S26361-D2312-A3 dmi.chassis.type: 2 dmi.chassis.vendor: FUJITSU SIEMENS dmi.chassis.version: ESPP dmi.modalias: dmi:bvnFUJITSUSIEMENS//PhoenixTechnologiesLtd.:bvr6.00R1.12.2312.A3:bd10/11/2007:svnFUJITSUSIEMENS:pnESPRIMOP:pvr:rvnFUJITSUSIEMENS:rnD2312-A3:rvrS26361-D2312-A3:cvnFUJITSUSIEMENS:ct2:cvrESPP: dmi.product.name: ESPRIMO P dmi.sys.vendor: FUJITSU SIEMENS version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1 version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1 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+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 xserver.bootTime: Sat Jul 11 20:24:02 2020 xserver.configfile: /etc/X11/xorg.conf xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.20.8-2ubuntu2.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1887271/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe :
[Desktop-packages] [Bug 1887271] [NEW] Square rectangles instead of system fonts after upgrade
You have been subscribed to a public bug: After upgrading my room mate's Fujitsu Esprimo Desktop PC to 20.04 Focal Fossa (from Bionic 18.04): Any system font line is being displayed distorted / erroneous / in sort of placeholder blocks or SQUARE RECTANGLES, as if the fonts set wouldn't be installed at all... Tthe 'gsettings'-procedure from some link mentioned on askubuntu-com wouldn't help either (with copy into unreadable terminal display font output) Gnome-tweak didn't help, BUT I can copy text from terminal into libreoffice document and thus make it readable afterwards. I cannot find any information about "system font output/printing" on the whole internet leaving me with a mysrltery about how that stuff works from xserver to gnome, Wayland-session login IMPOSSIBLE in order to print the correct display font ... I will attach some screenshots later on if possible. P.S.: firefox/libreoffice fonts are being displayed correctly inside any homepage ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg (not installed) ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Ist ein Verzeichnis: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.108 Wed Dec 11 11:06:58 PST 2019 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2) ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Jul 12 10:55:08 2020 DistUpgraded: 2020-06-29 10:31:32,274 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia-340, 340.108, 5.3.0-51-generic, x86_64: installed nvidia-340, 340.108, 5.4.0-39-generic, x86_64: installed nvidia-340, 340.108, 5.4.0-40-generic, x86_64: installed rtlwifi-new, 0.10: added GraphicsCard: NVIDIA Corporation G84 [GeForce 8600 GT] [10de:0402] (rev a1) (prog-if 00 [VGA controller]) Subsystem: CardExpert Technology G84 [GeForce 8600 GT] [10b0:0801] InstallationDate: Installed on 2017-08-28 (1048 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) LightdmLog: [+6033.49s] DEBUG: Seat seat0 changes active session to [+6033.53s] DEBUG: Seat seat0 changes active session to c5 [+6033.53s] DEBUG: Session c5 is already active MachineType: FUJITSU SIEMENS ESPRIMO P ProcEnviron: LANGUAGE=de_AT:de PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_AT.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz root=/dev/sdb4 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-06-29 (13 days ago) dmi.bios.date: 10/11/2007 dmi.bios.vendor: FUJITSU SIEMENS // Phoenix Technologies Ltd. dmi.bios.version: 6.00 R1.12.2312.A3 dmi.board.name: D2312-A3 dmi.board.vendor: FUJITSU SIEMENS dmi.board.version: S26361-D2312-A3 dmi.chassis.type: 2 dmi.chassis.vendor: FUJITSU SIEMENS dmi.chassis.version: ESPP dmi.modalias: dmi:bvnFUJITSUSIEMENS//PhoenixTechnologiesLtd.:bvr6.00R1.12.2312.A3:bd10/11/2007:svnFUJITSUSIEMENS:pnESPRIMOP:pvr:rvnFUJITSUSIEMENS:rnD2312-A3:rvrS26361-D2312-A3:cvnFUJITSUSIEMENS:ct2:cvrESPP: dmi.product.name: ESPRIMO P dmi.sys.vendor: FUJITSU SIEMENS version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1 version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1 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+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 xserver.bootTime: Sat Jul 11 20:24:02 2020 xserver.configfile: /etc/X11/xorg.conf xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.20.8-2ubuntu2.1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal resolution ubuntu -- Square rectangles instead of system fonts after upgrade https://bugs.launchpad.net/bugs/1887271 You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1870356] Re: Can't connect to paired bluetooth devices via g-c-c
Not a fix but a workaround: I installed the gnome-shell-extension-bluetooth-quick-connect package. In integrates well with the Gnome UI, adding a menu similar to the WiFi networks one but for Bluetooth devices, and it connects almost every time. -- 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/1870356 Title: Can't connect to paired bluetooth devices via g-c-c Status in gnome-control-center: Unknown Status in gnome-control-center package in Ubuntu: Triaged Bug description: I have a paired bluetooth device listed as "Disconnected" in the Bluetooth section of gnome-control-center. In order to connect to it I click on the device name and switch the "Connection" slider to the "on" position. The slider moves but immediately bounces back to the "off" position, and nothing happens: the connection is not established. It never works even if I try several times. This happens on an up-to-date Focal system and it's always reproducible across reboots and power cycles of the device. I don't think it's a problem of the device itself or of the underlying bluetooth stack, as connecting/disconnecting to the device works perfectly if I use blueman-manager instead of gnome-control-center. I don't know if this is a regression as I was not using bluetooth before installing Focal. FWIW (very little), the device connects/disconnects perfectly to Android phones. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-02-26 (400 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190226) NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: gnome-control-center 1:3.36.1-1ubuntu2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-20.24-generic 5.4.27 Tags: focal uec-images wayland-session third-party-packages Uname: Linux 5.4.0-20-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-01-21 (72 days ago) UserGroups: adm cdrom dialout dip docker libvirt lpadmin lxd plugdev sambashare sbuild sudo utah _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1870356/+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 1845801] Re: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.
if the result in #101 is positive for everyone, then I think it's because of this missed patch since from cosmic ** Patch added: "vt_handoff.patch" https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1845801/+attachment/5391915/+files/vt_handoff.patch -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1845801 Title: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login. Status in OEM Priority Project: New Status in gdm3 package in Ubuntu: Confirmed Status in gnome-session package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-430 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-435 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-440 package in Ubuntu: Confirmed Status in gdm3 source package in Eoan: Confirmed Status in gnome-session source package in Eoan: Confirmed Status in nvidia-graphics-drivers-435 source package in Eoan: Confirmed Bug description: I just updated to the Ubuntu 19.10 beta. After boot, I'm shown the GDM login screen (which I shouldn't; I have auto login enabled), and logging in just takes me back to the same user selection screen even though the password is correct. If I switch to a TTY and run `sudo pkill gnome-session-binary`, logging in through GDM starts working again. I should add that the do-release-upgrade was rocky; I did it in a terminal from within gnome, went away for a while, and when I returned, I just saw an Ubuntu 19.10 in a TTY. I was able to do `sudo dpkg --configure -a` and complete the upgrade, but I don't know if something's still messed up due to that. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 NonfreeKernelModules: 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 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 9.2.1 20190909 (Ubuntu 9.2.1-8ubuntu1) ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Sep 28 19:55:42 2019 DistUpgraded: 2019-09-28 18:35:15,142 INFO cache.commit() DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia, 435.21, 5.3.0-13-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP102 [GeForce GTX 1080 Ti] [1043:85e4] InstallationDate: Installed on 2019-09-14 (13 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: MSI MS-7A67 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-13-generic root=UUID=04974c80-e732-49b6-8148-c3dce7c02a25 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to eoan on 2019-09-28 (0 days ago) dmi.bios.date: 01/25/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.60 dmi.board.asset.tag: Default string dmi.board.name: H270I GAMING PRO AC (MS-7A67) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.60:bd01/25/2018:svnMSI:pnMS-7A67:pvr1.0:rvnMSI:rnH270IGAMINGPROAC(MS-7A67):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.family: Default string dmi.product.name: MS-7A67 dmi.product.sku: Default string dmi.product.version: 1.0 dmi.sys.vendor: MSI version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.1.6-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20190820-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-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 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1845801/+subscriptions --
[Desktop-packages] [Bug 1845801] Re: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.
Hi Guys, Help me to test this, this works for me, please find this line "set vt_handoff=vt.handoff=7" in /boot/grub/grub.cfg, and change it to "set vt_handoff=vt.handoff=1", then reboot let's see how it goes, thanks. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1845801 Title: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login. Status in OEM Priority Project: New Status in gdm3 package in Ubuntu: Confirmed Status in gnome-session package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-430 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-435 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-440 package in Ubuntu: Confirmed Status in gdm3 source package in Eoan: Confirmed Status in gnome-session source package in Eoan: Confirmed Status in nvidia-graphics-drivers-435 source package in Eoan: Confirmed Bug description: I just updated to the Ubuntu 19.10 beta. After boot, I'm shown the GDM login screen (which I shouldn't; I have auto login enabled), and logging in just takes me back to the same user selection screen even though the password is correct. If I switch to a TTY and run `sudo pkill gnome-session-binary`, logging in through GDM starts working again. I should add that the do-release-upgrade was rocky; I did it in a terminal from within gnome, went away for a while, and when I returned, I just saw an Ubuntu 19.10 in a TTY. I was able to do `sudo dpkg --configure -a` and complete the upgrade, but I don't know if something's still messed up due to that. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 NonfreeKernelModules: 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 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 9.2.1 20190909 (Ubuntu 9.2.1-8ubuntu1) ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Sep 28 19:55:42 2019 DistUpgraded: 2019-09-28 18:35:15,142 INFO cache.commit() DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia, 435.21, 5.3.0-13-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP102 [GeForce GTX 1080 Ti] [1043:85e4] InstallationDate: Installed on 2019-09-14 (13 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: MSI MS-7A67 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-13-generic root=UUID=04974c80-e732-49b6-8148-c3dce7c02a25 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to eoan on 2019-09-28 (0 days ago) dmi.bios.date: 01/25/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.60 dmi.board.asset.tag: Default string dmi.board.name: H270I GAMING PRO AC (MS-7A67) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.60:bd01/25/2018:svnMSI:pnMS-7A67:pvr1.0:rvnMSI:rnH270IGAMINGPROAC(MS-7A67):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.family: Default string dmi.product.name: MS-7A67 dmi.product.sku: Default string dmi.product.version: 1.0 dmi.sys.vendor: MSI version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.1.6-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20190820-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-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 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1845801/+subscriptions -- Mailing list:
[Desktop-packages] [Bug 1845801] Re: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.
Hi Guys, Help me to test this, this works for me, please find this line "set vt_handoff=vt.handoff=7" in /boot/grub/grub.cfg, and change it to "set vt_handoff=vt.handoff=1", then reboot let's see how it go, thanks. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1845801 Title: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login. Status in OEM Priority Project: New Status in gdm3 package in Ubuntu: Confirmed Status in gnome-session package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-430 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-435 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-440 package in Ubuntu: Confirmed Status in gdm3 source package in Eoan: Confirmed Status in gnome-session source package in Eoan: Confirmed Status in nvidia-graphics-drivers-435 source package in Eoan: Confirmed Bug description: I just updated to the Ubuntu 19.10 beta. After boot, I'm shown the GDM login screen (which I shouldn't; I have auto login enabled), and logging in just takes me back to the same user selection screen even though the password is correct. If I switch to a TTY and run `sudo pkill gnome-session-binary`, logging in through GDM starts working again. I should add that the do-release-upgrade was rocky; I did it in a terminal from within gnome, went away for a while, and when I returned, I just saw an Ubuntu 19.10 in a TTY. I was able to do `sudo dpkg --configure -a` and complete the upgrade, but I don't know if something's still messed up due to that. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 NonfreeKernelModules: 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 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 9.2.1 20190909 (Ubuntu 9.2.1-8ubuntu1) ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Sep 28 19:55:42 2019 DistUpgraded: 2019-09-28 18:35:15,142 INFO cache.commit() DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia, 435.21, 5.3.0-13-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP102 [GeForce GTX 1080 Ti] [1043:85e4] InstallationDate: Installed on 2019-09-14 (13 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: MSI MS-7A67 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-13-generic root=UUID=04974c80-e732-49b6-8148-c3dce7c02a25 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to eoan on 2019-09-28 (0 days ago) dmi.bios.date: 01/25/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.60 dmi.board.asset.tag: Default string dmi.board.name: H270I GAMING PRO AC (MS-7A67) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.60:bd01/25/2018:svnMSI:pnMS-7A67:pvr1.0:rvnMSI:rnH270IGAMINGPROAC(MS-7A67):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.family: Default string dmi.product.name: MS-7A67 dmi.product.sku: Default string dmi.product.version: 1.0 dmi.sys.vendor: MSI version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.1.6-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20190820-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-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 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1845801/+subscriptions -- Mailing list:
[Desktop-packages] [Bug 1767654] Re: [Intel Braswell] Cursor gets stuck on left side of the screen
@Bob Lawrence (pilotbob42) So i'm back with a better workaround. First I enabled the intel driver like I specified in my first point.(this removes the tearing) Then I used your workaround, but this was causing the other inputs to error at startup so I on some forum that adding a command at startup applications is a better solution. So i added:"xrandr --output HDMI-3 --mode 1920x1080 --scale 0.x0." as a new command in Startup Applications. -- 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/1767654 Title: [Intel Braswell] Cursor gets stuck on left side of the screen Status in Linux: New Status in gnome-shell package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: When moving the cursor to the left side of the screen, it stops close to the edge. The cursor still moves over in the area but invisible until I move it out of the area. When it doesn't do this, glitching occurs on the screen where the cursor is until I log out. And on screen cast it shows the cursor going to the side of the screen and moving. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Apr 28 09:49:51 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:22b1] (rev 21) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:2060] InstallationDate: Installed on 2018-04-27 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2a Intel Corp. Bus 001 Device 003: ID 05e3:0610 Genesys Logic, Inc. 4-port hub Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: \\boot\vmlinuz-4.15.0-20-generic root=UUID=c6f92850-287a-4747-ac0d-3af593994183 ro quiet splash vt.handoff=1 initrd=boot\initrd.img-4.15.0-20-generic SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/08/2017 dmi.bios.vendor: Intel Corp. dmi.bios.version: PYBSWCEL.86A.0062.2017.0308.1328 dmi.board.name: NUC5CPYB dmi.board.vendor: Intel Corporation dmi.board.version: H61145-408 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrPYBSWCEL.86A.0062.2017.0308.1328:bd03/08/2017:svn:pn:pvr:rvnIntelCorporation:rnNUC5CPYB:rvrH61145-408:cvn:ct3:cvr: version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1767654/+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
