[Desktop-packages] [Bug 2002862] Re: Sound low please help me
Please go to Settings > Sound and take a screenshot of the window. Please also run 'alsa-info' and attach the text file it produces. ** Package changed: gnome-shell (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 gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2002862 Title: Sound low please help me Status in Ubuntu: Incomplete Bug description: hp laptop 15-bs0xx my loptop sound very low after i shift windows to ubuntu ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.5-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74 Uname: Linux 5.15.0-58-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Jan 14 08:13:55 2023 DisplayManager: gdm3 InstallationDate: Installed on 2023-01-13 (0 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) RelatedPackageVersions: mutter-common 42.2-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2002862/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1986451] Re: Can't click context menu items when they cover the dock (in a Xorg session)
Try not to blame "wayland" for "many bugs that degrade the Linux experience". They're almost all specific to the Nvidia driver: https://bugs.launchpad.net/ubuntu/+bugs?field.tag=nvidia-wayland But if you are aware of any more then please let us know. -- 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/1986451 Title: Can't click context menu items when they cover the dock (in a Xorg session) Status in Dash to dock: Unknown Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: New Bug description: ubuntu dock in bottom position won't let me click on button (convert java file to Kotlin file) in android studio, but in the left position everything works correctly. That is, if the menu android studio overlaps the ubuntu dock, then the menu buttons will not be pressed. https://youtu.be/KsOVG7Uucow ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .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 515.65.01 Wed Jul 20 14:00:58 UTC 2022 GCC version: ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CompositorRunning: None Date: Sun Aug 14 10:52:56 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: openrazer-driver/3.4.0, 5.15.0-43-generic, x86_64: installed openrazer-driver/3.4.0, 5.15.0-46-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Xiaomi UHD Graphics 620 [1d72:1701] Subsystem: Xiaomi Mi Notebook Pro [GeForce MX150] [1d72:1701] InstallationDate: Installed on 2022-07-13 (31 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Timi TM1701 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic root=UUID=7c5eaac1-9b38-4169-8a20-0fef5e97c644 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/02/2018 dmi.bios.release: 106.121 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: XMAKB5R0P0603 dmi.board.asset.tag: Any dmi.board.name: TM1701 dmi.board.vendor: Timi dmi.board.version: MP dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Timi dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 0.3 dmi.modalias: dmi:bvnINSYDECorp.:bvrXMAKB5R0P0603:bd02/02/2018:br106.121:efr0.3:svnTimi:pnTM1701:pvr:rvnTimi:rnTM1701:rvrMP:cvnTimi:ct10:cvrChassisVersion:sku: dmi.product.family: Timibook dmi.product.name: TM1701 dmi.sys.vendor: Timi version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.5-0ubuntu0.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-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-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/dash-to-dock/+bug/1986451/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1982560] Re: Mouse lag/stutter (missed frames) in Wayland sessions
Comment #36 reminds me this bug might be a red herring for some. If the OP is using dual GPUs then that alone might be the cause of their problem. Mutter Wayland sessions don't handle dual-GPU-dual-monitor setups efficiently... francesco: Please try a single monitor setup and tell us if the problem persists. Everyone else: Please always start by reporting your own separate bugs. ** Changed in: gnome-shell (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1982560 Title: Mouse lag/stutter (missed frames) in Wayland sessions Status in gnome-shell package in Ubuntu: Incomplete Bug description: Mouse lag on fresh install of ubuntu 22.04 LTS (wayland). This problem didn't occur in previous version of ubuntu based on xorg. Specifically, frequent mouse lag when I turn on the pc, when I unlock the pc or when heavy operations are done on it. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-11-13 (50 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: gnome-shell 42.5-0ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.15.0-56.62-generic 5.15.64 RelatedPackageVersions: mutter-common 42.5-0ubuntu1 Tags: jammy wayland-session Uname: Linux 5.15.0-56-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1982560/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2002926] Re: GNOME Console doesn't copy last line
** Description changed: Impact -- - GNOME Console 43 has switched to GTK4 and the last line of text isn't being copied. + GNOME Console 43 has switched to GTK4 and the final line of text isn't being copied. If there is only one line you are trying to copy, the clipboard is apparently empty. Test Case - + Copy a selection that includes the end of the line. One easy way to do this is to triple-click the line. Then right-click and choose Copy. + + All the lines should be copied including the final line. What Could Go Wrong --- + This is a one line fix that modifies a function (vte_terminal_get_text_selected) that is only used by GNOME Builder and GNOME Console. (GNOME Builder is affected by the same bug). + + Neither GNOME Builder nor GNOME Console are included by default in any + Ubuntu flavor. GNOME Console may replace GNOME Terminal as the default + terminal app for Ubuntu Desktop in a future Ubuntu release. This bug was + a blocker for that happening. ** Changed in: vte2.91 (Ubuntu Kinetic) Status: New => In Progress ** Description changed: Impact -- GNOME Console 43 has switched to GTK4 and the final line of text isn't being copied. If there is only one line you are trying to copy, the clipboard is apparently empty. Test Case - - Copy a selection that includes the end of the line. One easy way to do this is to triple-click the line. Then right-click and choose Copy. + Install the updated vte packages and gnome-console. - All the lines should be copied including the final line. + Run the Console app. + + Run this command: + cat /etc/os-release + + Copy a selection that includes the end of the line. One easy way to do + this is to triple-click the line. Then right-click and choose Copy. + + Then right-click and choose Paste. + + All the lines should be pasted including the final line. What Could Go Wrong --- This is a one line fix that modifies a function (vte_terminal_get_text_selected) that is only used by GNOME Builder and GNOME Console. (GNOME Builder is affected by the same bug). Neither GNOME Builder nor GNOME Console are included by default in any Ubuntu flavor. GNOME Console may replace GNOME Terminal as the default terminal app for Ubuntu Desktop in a future Ubuntu release. This bug was a blocker for that happening. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to vte2.91 in Ubuntu. https://bugs.launchpad.net/bugs/2002926 Title: GNOME Console doesn't copy last line Status in vte2.91 package in Ubuntu: Fix Committed Status in vte2.91 source package in Kinetic: In Progress Bug description: Impact -- GNOME Console 43 has switched to GTK4 and the final line of text isn't being copied. If there is only one line you are trying to copy, the clipboard is apparently empty. Test Case - Install the updated vte packages and gnome-console. Run the Console app. Run this command: cat /etc/os-release Copy a selection that includes the end of the line. One easy way to do this is to triple-click the line. Then right-click and choose Copy. Then right-click and choose Paste. All the lines should be pasted including the final line. What Could Go Wrong --- This is a one line fix that modifies a function (vte_terminal_get_text_selected) that is only used by GNOME Builder and GNOME Console. (GNOME Builder is affected by the same bug). Neither GNOME Builder nor GNOME Console are included by default in any Ubuntu flavor. GNOME Console may replace GNOME Terminal as the default terminal app for Ubuntu Desktop in a future Ubuntu release. This bug was a blocker for that happening. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vte2.91/+bug/2002926/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2002926] [NEW] GNOME Console doesn't copy last line
Public bug reported: Impact -- GNOME Console 43 has switched to GTK4 and the final line of text isn't being copied. If there is only one line you are trying to copy, the clipboard is apparently empty. Test Case - Install the updated vte packages and gnome-console. Run the Console app. Run this command: cat /etc/os-release Copy a selection that includes the end of the line. One easy way to do this is to triple-click the line. Then right-click and choose Copy. Then right-click and choose Paste. All the lines should be pasted including the final line. What Could Go Wrong --- This is a one line fix that modifies a function (vte_terminal_get_text_selected) that is only used by GNOME Builder and GNOME Console. (GNOME Builder is affected by the same bug). Neither GNOME Builder nor GNOME Console are included by default in any Ubuntu flavor. GNOME Console may replace GNOME Terminal as the default terminal app for Ubuntu Desktop in a future Ubuntu release. This bug was a blocker for that happening. ** Affects: vte2.91 (Ubuntu) Importance: High Status: Fix Committed ** Affects: vte2.91 (Ubuntu Kinetic) Importance: High Status: In Progress ** Tags: kinetic ** Also affects: vte2.91 (Ubuntu Kinetic) Importance: Undecided Status: New ** Changed in: vte2.91 (Ubuntu Kinetic) Importance: Undecided => High -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to vte2.91 in Ubuntu. https://bugs.launchpad.net/bugs/2002926 Title: GNOME Console doesn't copy last line Status in vte2.91 package in Ubuntu: Fix Committed Status in vte2.91 source package in Kinetic: In Progress Bug description: Impact -- GNOME Console 43 has switched to GTK4 and the final line of text isn't being copied. If there is only one line you are trying to copy, the clipboard is apparently empty. Test Case - Install the updated vte packages and gnome-console. Run the Console app. Run this command: cat /etc/os-release Copy a selection that includes the end of the line. One easy way to do this is to triple-click the line. Then right-click and choose Copy. Then right-click and choose Paste. All the lines should be pasted including the final line. What Could Go Wrong --- This is a one line fix that modifies a function (vte_terminal_get_text_selected) that is only used by GNOME Builder and GNOME Console. (GNOME Builder is affected by the same bug). Neither GNOME Builder nor GNOME Console are included by default in any Ubuntu flavor. GNOME Console may replace GNOME Terminal as the default terminal app for Ubuntu Desktop in a future Ubuntu release. This bug was a blocker for that happening. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vte2.91/+bug/2002926/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 45836] Re: Scrolling in the view-source window
** Changed in: firefox Status: Confirmed => Invalid -- 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/45836 Title: Scrolling in the view-source window Status in Mozilla Firefox: Invalid Status in firefox package in Ubuntu: Invalid Bug description: Using the latest Dapper (05/21/06), I have problems with the view- source window. When the source window is maximized and I want to select text by mouse going from right to left the window does not scroll when hitting the left edge. Going from left to right works well. Also Unmaximized window works in both directions. To recreate: 1) Open a view-source window by View > Page Source. 2) Maximize the view-source window. 3) Check that there is a line wider then the actual view-source window and go to the end of this line. 4) Select text from the end of this line going far left. 5) Window does not scroll. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/45836/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1999083] Re: cannot rename multiple files
Turns out I wasn't running Nautilus, I was running Nemo. My mistake. I installed Nautilus. Problem solved. ** Changed in: nautilus (Ubuntu) Status: New => Invalid -- 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/1999083 Title: cannot rename multiple files Status in nautilus package in Ubuntu: Invalid Bug description: If I highlight two or more files at once and either press F2 or right- click and choose "Rename..." from the popup menu, I expect to be able to rename those files in one action. Instead, nothing happens. There is absolutely no perceptible response from the system (well the pop-up menu does disappear, if I tried the right-click option). The bulk rename feature worked in the previous version of Ubuntu. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: nautilus (not installed) ProcVersionSignature: Ubuntu 5.15.0-56.62-generic 5.15.64 Uname: Linux 5.15.0-56-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Dec 7 11:50:48 2022 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 EcryptfsInUse: Yes InstallationDate: Installed on 2017-01-24 (2143 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1999083/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1970139] Re: VNC Connection doesn't work on arm64 (Raspberry Pi 4 8Gb) in Ubuntu 22.04 LTS
Unrelated to the current report, anyway I'll stick to my old Raspbian 32 bits (Buster) since Ubuntu 22.04 currently lacks video hardware acceleration: https://ubuntuforums.org/showthread.php?t=2478838 ... one of the main uses of my RaspbPi being to watch videos without having run my Desktop PC! So yes, Ubuntu on Raspberry Pi 4 is a nice proof of concept, but there is some work to do to catch up with the Raspeberry Pi OS... and not only on VNC that is so much better integrated on Raspbian. Keep up the good job! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-remote-desktop in Ubuntu. https://bugs.launchpad.net/bugs/1970139 Title: VNC Connection doesn't work on arm64 (Raspberry Pi 4 8Gb) in Ubuntu 22.04 LTS Status in gnome-remote-desktop package in Ubuntu: Fix Released Bug description: # lsb_release -rd Description: Ubuntu 22.04 LTS Release: 22.04 # apt-cache policy gnome-remote-desktop gnome-remote-desktop: Instalados: 42.0-4ubuntu1 Candidato: 42.0-4ubuntu1 Tabla de versión: *** 42.0-4ubuntu1 500 500 http://ports.ubuntu.com/ubuntu-ports jammy/main arm64 Packages 100 /var/lib/dpkg/status # uname -a Linux fpgrpi 5.15.0-1005-raspi #5-Ubuntu SMP PREEMPT Mon Apr 4 12:21:48 UTC 2022 aarch64 aarch64 aarch64 GNU/Linux Summary of the bug: --- When I try to connect to gnome-remote-desktop using VNC to a Raspberry Pi 4 Model B Rev 1.4 (8Gb) under Ubuntu 22.04 LTS the VNC client can't connect (connection is refused). The connection passes the Password check validation but don't connect (sometimes shows screen garbage before disconnecting). I've used several VNC clients (Remmina in Ubuntu and Real VNC in Android) getting the same problem failing either in X11 or Wayland. Notes: - VNC connection does work in in previous Ubuntu 21.10 version with the same architecture (arm64) and same Raspberry Pi. - VNC connection also does work in amd64 machines with Ubuntu 22.04 LTS and gnome-remote-desktop 42.0-4ubuntu1, exactly the same software version that doesn't work on arm64 (Raspberry Pi). There is no apport info at all. Also there is almost no info in the journal regarding this problem. When I try to connect to VNC server it show this: On Wayland: --- abr 25 00:21:42 fpgrpi kernel: vc4-drm gpu: swiotlb buffer is full (sz: 1884160 bytes), total 32768 (slots), used 3 (slots) abr 25 00:21:42 fpgrpi kernel: vc4-drm gpu: swiotlb buffer is full (sz: 4169728 bytes), total 32768 (slots), used 3 (slots) abr 25 00:21:42 fpgrpi kernel: vc4-drm gpu: swiotlb buffer is full (sz: 8130560 bytes), total 32768 (slots), used 83 (slots) abr 25 00:21:42 fpgrpi kernel: vc4-drm gpu: swiotlb buffer is full (sz: 8294400 bytes), total 32768 (slots), used 3 (slots) abr 25 00:21:42 fpgrpi kernel: vc4-drm gpu: swiotlb buffer is full (sz: 8294400 bytes), total 32768 (slots), used 3 (slots) abr 25 00:21:42 fpgrpi kernel: vc4-drm gpu: swiotlb buffer is full (sz: 8294400 bytes), total 32768 (slots), used 3 (slots) abr 25 00:21:42 fpgrpi kernel: vc4-drm gpu: swiotlb buffer is full (sz: 8294400 bytes), total 32768 (slots), used 3 (slots) abr 25 00:21:43 fpgrpi systemd[1381]: gnome-remote-desktop.service: Main process exited, code=killed, status=11/SEGV abr 25 00:21:43 fpgrpi systemd[1381]: gnome-remote-desktop.service: Failed with result 'signal'. abr 25 00:21:43 fpgrpi gnome-shell[1497]: D-Bus client with active sessions vanished abr 25 00:21:43 fpgrpi systemd[1381]: gnome-remote-desktop.service: Scheduled restart job, restart counter is at 1. abr 25 00:21:43 fpgrpi systemd[1381]: Stopped GNOME Remote Desktop. abr 25 00:21:43 fpgrpi systemd[1381]: Starting GNOME Remote Desktop... abr 25 00:21:43 fpgrpi systemd[1381]: Started GNOME Remote Desktop. abr 25 00:21:43 fpgrpi gnome-remote-desktop-daemon[2125]: Cannot load libcuda.so.1 abr 25 00:21:43 fpgrpi gnome-remote-desktop-daemon[2125]: Cannot load libnvidia-encode.so.1 abr 25 00:21:43 fpgrpi gnome-remote-de[2125]: RDP server started abr 25 00:21:43 fpgrpi gnome-remote-de[2125]: VNC server started On X11: --- abr 25 00:12:18 fpgrpi systemd[2859]: gnome-remote-desktop.service: Main process exited, code=killed, status=11/SEGV abr 25 00:12:18 fpgrpi gnome-shell[3044]: D-Bus client with active sessions vanished abr 25 00:12:18 fpgrpi systemd[2859]: gnome-remote-desktop.service: Failed with result 'signal'. abr 25 00:12:18 fpgrpi systemd[2859]: gnome-remote-desktop.service: Scheduled restart job, restart counter is at 19. abr 25 00:12:18 fpgrpi systemd[2859]: Stopped GNOME Remote Desktop. abr 25 00:12:18 fpgrpi systemd[2859]: Starting GNOME Remote Desktop... abr 25 00:12:18 fpgrpi systemd[2859]: Started GNOME Remote Desktop. abr 25 00:12:19 fpgrpi gnome-remote-desktop-daemon[23876]: Cannot load libcuda.so.1 abr 25 00:12:19 fpgrpi
[Desktop-packages] [Bug 1970139] Re: VNC Connection doesn't work on arm64 (Raspberry Pi 4 8Gb) in Ubuntu 22.04 LTS
@fprietog Indeed I regret the open VNC standard is dropped in favour of the proprietary Microsoft's protocol RDP, itself using H.264 licence ridden compression. It might be a more efficient standard (I hope so at least), but it does not go in the direction of freedom! This issue about RDP would be pretty much the same. On a clean 22.04 RaspbPi 4, the keyring only has 2 keys: the one for VNC password, and the one for RDP configuration. So, in all probability, if the server machine you want to access remotely via RDP has been set as auto-login, which is convenient for a headless Raspberry Pi 4, the machine won't be able to access whatever RDP configuration you have set for the reason explained above (follow the link), and would probably use a default, and possibly a random password when needed. Then, you probably won't be able to access the machine with RDP also without doing the same trick. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-remote-desktop in Ubuntu. https://bugs.launchpad.net/bugs/1970139 Title: VNC Connection doesn't work on arm64 (Raspberry Pi 4 8Gb) in Ubuntu 22.04 LTS Status in gnome-remote-desktop package in Ubuntu: Fix Released Bug description: # lsb_release -rd Description: Ubuntu 22.04 LTS Release: 22.04 # apt-cache policy gnome-remote-desktop gnome-remote-desktop: Instalados: 42.0-4ubuntu1 Candidato: 42.0-4ubuntu1 Tabla de versión: *** 42.0-4ubuntu1 500 500 http://ports.ubuntu.com/ubuntu-ports jammy/main arm64 Packages 100 /var/lib/dpkg/status # uname -a Linux fpgrpi 5.15.0-1005-raspi #5-Ubuntu SMP PREEMPT Mon Apr 4 12:21:48 UTC 2022 aarch64 aarch64 aarch64 GNU/Linux Summary of the bug: --- When I try to connect to gnome-remote-desktop using VNC to a Raspberry Pi 4 Model B Rev 1.4 (8Gb) under Ubuntu 22.04 LTS the VNC client can't connect (connection is refused). The connection passes the Password check validation but don't connect (sometimes shows screen garbage before disconnecting). I've used several VNC clients (Remmina in Ubuntu and Real VNC in Android) getting the same problem failing either in X11 or Wayland. Notes: - VNC connection does work in in previous Ubuntu 21.10 version with the same architecture (arm64) and same Raspberry Pi. - VNC connection also does work in amd64 machines with Ubuntu 22.04 LTS and gnome-remote-desktop 42.0-4ubuntu1, exactly the same software version that doesn't work on arm64 (Raspberry Pi). There is no apport info at all. Also there is almost no info in the journal regarding this problem. When I try to connect to VNC server it show this: On Wayland: --- abr 25 00:21:42 fpgrpi kernel: vc4-drm gpu: swiotlb buffer is full (sz: 1884160 bytes), total 32768 (slots), used 3 (slots) abr 25 00:21:42 fpgrpi kernel: vc4-drm gpu: swiotlb buffer is full (sz: 4169728 bytes), total 32768 (slots), used 3 (slots) abr 25 00:21:42 fpgrpi kernel: vc4-drm gpu: swiotlb buffer is full (sz: 8130560 bytes), total 32768 (slots), used 83 (slots) abr 25 00:21:42 fpgrpi kernel: vc4-drm gpu: swiotlb buffer is full (sz: 8294400 bytes), total 32768 (slots), used 3 (slots) abr 25 00:21:42 fpgrpi kernel: vc4-drm gpu: swiotlb buffer is full (sz: 8294400 bytes), total 32768 (slots), used 3 (slots) abr 25 00:21:42 fpgrpi kernel: vc4-drm gpu: swiotlb buffer is full (sz: 8294400 bytes), total 32768 (slots), used 3 (slots) abr 25 00:21:42 fpgrpi kernel: vc4-drm gpu: swiotlb buffer is full (sz: 8294400 bytes), total 32768 (slots), used 3 (slots) abr 25 00:21:43 fpgrpi systemd[1381]: gnome-remote-desktop.service: Main process exited, code=killed, status=11/SEGV abr 25 00:21:43 fpgrpi systemd[1381]: gnome-remote-desktop.service: Failed with result 'signal'. abr 25 00:21:43 fpgrpi gnome-shell[1497]: D-Bus client with active sessions vanished abr 25 00:21:43 fpgrpi systemd[1381]: gnome-remote-desktop.service: Scheduled restart job, restart counter is at 1. abr 25 00:21:43 fpgrpi systemd[1381]: Stopped GNOME Remote Desktop. abr 25 00:21:43 fpgrpi systemd[1381]: Starting GNOME Remote Desktop... abr 25 00:21:43 fpgrpi systemd[1381]: Started GNOME Remote Desktop. abr 25 00:21:43 fpgrpi gnome-remote-desktop-daemon[2125]: Cannot load libcuda.so.1 abr 25 00:21:43 fpgrpi gnome-remote-desktop-daemon[2125]: Cannot load libnvidia-encode.so.1 abr 25 00:21:43 fpgrpi gnome-remote-de[2125]: RDP server started abr 25 00:21:43 fpgrpi gnome-remote-de[2125]: VNC server started On X11: --- abr 25 00:12:18 fpgrpi systemd[2859]: gnome-remote-desktop.service: Main process exited, code=killed, status=11/SEGV abr 25 00:12:18 fpgrpi gnome-shell[3044]: D-Bus client with active sessions vanished abr 25 00:12:18 fpgrpi systemd[2859]: gnome-remote-desktop.service: Failed with result 'signal'. abr 25 00:12:18 fpgrpi systemd[2859]:
[Desktop-packages] [Bug 1664501] Re: Unable to wake up monitor after it goes to sleep (after locking x session, for example)
Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. Ubuntu 16.04 (xenial) reached end-of-standard-support on April 29, 2021. I'm setting the status of this bug to 'Incomplete' as it's not seen any activity for some time. If this is still an issue when using a currently maintained release of Ubuntu then please let us know which one(s) otherwise this bug report can be left to expire in approximately 60 days time. ** Changed in: xorg (Ubuntu) Status: Confirmed => 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/1664501 Title: Unable to wake up monitor after it goes to sleep (after locking x session, for example) Status in xorg package in Ubuntu: Incomplete Bug description: Additional info: lsb_release: Description: Ubuntu 16.04.1 LTS Release: 16.04 I'm using an external monitor attached via VGA (seen as DP2 in xrandr output) in an extended desktop configuration (not cloned). Whenever the X session starts some kind of screen saving (for example, after locking the screen), the external monitor and the laptop screen both go to a saving power state. After that, If I try to wake them up (moving cursor, touch keys, etc.), only the laptop's panel goes back. The external monitor stays in a suspended state. If I force it to wake up and scan inputs, it doesn't find any, and it doesn't appear as conencted in xrandr otput. The only way I've found to wake it up is by performing the following sequence of operations: ALT+F1 [switch to first tty/console] --> this does wake up and activate the monitor, mirroring login as my user $ xrandr -d :0 #DP2 still doesn't appear logout ALT+F7 [go back to X] At this point, the external monitor is working and X detects it and re-enables the extended desktop Doing just ALT+F1/ALT+F7, doesn't work (I need to execute xrandr in order to make the whole thing work) Doing xrandr from the graphical environment (directly in a xterminal in the Xsession) doesn't wake up the monitor Looks like there's no need to add any addictional operation/parameter to xrandr in order to make this process work, no need to set output settings, etc. Just issue "xrandr -d :0" and things magically work Thanks in advance ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40 Uname: Linux 4.4.0-62-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Tue Feb 14 10:54:19 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Skylake Integrated Graphics [103c:8079] MachineType: HP HP EliteBook 840 G3 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-62-generic root=ZFS=rpool/ROOT/ubuntu ro boot=zfs quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/22/2016 dmi.bios.vendor: HP dmi.bios.version: N75 Ver. 01.05 dmi.board.name: 8079 dmi.board.vendor: HP dmi.board.version: KBC Version 85.61 dmi.chassis.asset.tag: 5CG6247TWJ dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrN75Ver.01.05:bd03/22/2016:svnHP:pnHPEliteBook840G3:pvr:rvnHP:rn8079:rvrKBCVersion85.61:cvnHP:ct10:cvr: dmi.product.name: HP EliteBook 840 G3 dmi.sys.vendor: HP version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Tue Feb 14 10:49:09 2017 xserver.configfile: default xserver.errors: xserver.logfile:
[Desktop-packages] [Bug 1432413] Re: Synaptic Touchpad xevents are hijacked under X
Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. I'm setting the status of this bug to 'Incomplete' as it's not seen any activity for some time. If this is still an issue when using a currently maintained release of Ubuntu then please let us know which one(s) otherwise this bug report can be left to expire in approximately 60 days time. ** Changed in: xorg (Ubuntu) Status: Confirmed => 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/1432413 Title: Synaptic Touchpad xevents are hijacked under X Status in xorg package in Ubuntu: Incomplete Bug description: Synaptic Touchpad xevents are hijacked under X11. I have a problem with the synaptic touch-pad on my Acer Aspire that started around a week ago. The problem can be described as that there is a massive amount of xevents being generated and appearing to originate from the touch-pad even though the touch-pad is not used. I have tested the HW which seems to work fine. The test performed is to start a terminal session (Ctrl + Alt + 2) before the fault occurs and check the xevents by running ~$ sudo evtest /dev/input/eventX where the X to use is found in /proc/bus/input/devices and found by running ~$ cat /proc/bus/input/devices |grep mouse No matter how much the touch-pad is used will the console show the corresponding events which indicates that HW and driver works OK as long it is not under X When the problem has occurred (in Desktop mode) is it easy (but inconvenient) to get back to normal by key combo Fn+F7 twice, turn off touch-pad and then turn on again. And more, one can get unlucky in the sense that the generated events could click somewhere one do not want to click. During the problem is it impossible to use the mouse since it flies around (mostly going in a bottom to top of screen direction) but one can check the generated events using evtest again. How can I help troubleshooting the problem? ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 3.16.0-31.43~14.04.1-generic 3.16.7-ckt5 Uname: Linux 3.16.0-31-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.7 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sun Mar 15 19:51:13 2015 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation ValleyView Gen7 [8086:0f31] (rev 0e) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Device [1025:0933] InstallationDate: Installed on 2015-02-21 (22 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) MachineType: Acer Aspire E3-112 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-31-generic root=UUID=a97d0b51-4244-48ca-ba87-bc3a38a8b62d ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/20/2014 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.08 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: R2 dmi.board.vendor: Acer dmi.board.version: Type2 - A01 Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.08:bd08/20/2014:svnAcer:pnAspireE3-112:pvrV1.08:rvnAcer:rnR2:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.name: Aspire E3-112 dmi.product.version: V1.08 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.11.3+14.04.20150122-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1~ubuntu2 version.libgl1-mesa-dri: libgl1-mesa-dri N/A version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Sun Mar 15 18:59:07 2015 xserver.configfile: /etc/X11/xorg.conf xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id1576 vendor BOE xserver.version: 2:1.16.0-1ubuntu1.2~trusty2 To manage
[Desktop-packages] [Bug 1664596] Re: xset led on, enables mouse-keys
Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. I'm setting the status of this bug to 'Incomplete' as it's not seen any activity for some time. If this is still an issue when using a currently maintained release of Ubuntu then please let us know which one(s) otherwise this bug report can be left to expire in approximately 60 days time. ** Changed in: xorg (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/1664596 Title: xset led on, enables mouse-keys Status in xorg package in Ubuntu: Incomplete Bug description: I have a backlit keyboard on a stationary PC. The back-light goes off at random intervals. I'm a heavy user of numeric keypad. That turns into mouse-keys at intervals as well. Both issues results in a rather annoying user experience. I have not been able to determine the reason or what lead up to this. But it often happen whenever I take a short break. (after a few minutes of inactivity) Therefore I periodically run a script to turn the back-light back on and disable mouse-keys. It turns out that setting the back-light on, enables the mouse-keys again! Something is wired with this. But this last part is easy to reproduce with this script: #!/bin/sh /usr/bin/gsettings set org.gnome.desktop.a11y.keyboard mousekeys-enable false # disables mouse-keys /usr/bin/gsettings get org.gnome.desktop.a11y.keyboard mousekeys-enable # reports false and mouse-keys are actually disabled xset led on /usr/bin/gsettings get org.gnome.desktop.a11y.keyboard mousekeys-enable # reports false, but mouse-keys are actually enabled! /usr/bin/gsettings set org.gnome.desktop.a11y.keyboard mousekeys-enable false # disables mouse-keys again. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40 Uname: Linux 4.4.0-62-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Tue Feb 14 15:17:53 2017 DistUpgraded: 2016-06-03 10:07:29,690 DEBUG icon theme changed, re-reading DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Cape Verde XT [Radeon HD 7770/8760 / R7 250X] [1002:683d] (prog-if 00 [VGA controller]) Subsystem: XFX Pine Group Inc. Cape Verde XT [Radeon HD 7770/8760 / R7 250X] [1682:3232] InstallationDate: Installed on 2015-07-29 (565 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: ASUSTeK Computer INC. CM6330_CM6630_CM6730_CM6830-8 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-62-generic root=UUID=458544bf-05e1-4b76-93ee-1c5cfa8f7683 ro quiet splash usbcore.autosuspend=-1 vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to xenial on 2016-06-03 (256 days ago) dmi.bios.date: 08/27/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0402 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: CM6330_CM6630_CM6730_CM6830 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev x.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0402:bd08/27/2012:svnASUSTeKComputerINC.:pnCM6330_CM6630_CM6730_CM6830-8:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnCM6330_CM6630_CM6730_CM6830:rvrRevx.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: CM6330_CM6630_CM6730_CM6830-8 dmi.product.version: System Version dmi.sys.vendor: ASUSTeK Computer INC. version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Tue Feb 14 12:39:26 2017 xserver.configfile: default xserver.errors:
[Desktop-packages] [Bug 1589056] Re: HDMI does not work
Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. Ubuntu 16.04 (xenial) reached end-of-standard-support on April 29, 2021. I'm setting the status of this bug to 'Incomplete' as it's not seen any activity for some time. If this is still an issue when using a currently maintained release of Ubuntu then please let us know which one(s) otherwise this bug report can be left to expire in approximately 60 days time. ** Changed in: xorg (Ubuntu) Status: Triaged => 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/1589056 Title: HDMI does not work Status in xorg package in Ubuntu: Incomplete Bug description: xrandr displays "HDMI-1 disconnected (normal left inverted right x axis y axis)" even if it is connected using a HDMI cable to a Samsung monitor (model S27B350H) that has both HDMI and VGA connectors. WORKAROUND: Use the Nvidia proprietary driver. Graphics by lspci -vvv: 01:00.0 VGA compatible controller: NVIDIA Corporation G84GLM [Quadro FX 570M] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device 30c5 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- [disabled] Capabilities: Kernel driver in use: nouveau --- ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 BootLog: root: clean, 247512/1281120 files, 1867600/512 blocks [[0;1;31mFAILED[0m] Failed to start Automatically refresh installed snaps. See 'systemctl status snapd.refresh.service' for details. [[0;32m OK [0m] Started Authenticate and Authorize Users to Run Privileged Tasks. CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None DistUpgraded: 2016-06-24 18:11:48,939 DEBUG icon theme changed, re-reading DistroCodename: xenial DistroRelease: Ubuntu 16.04 DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation G84GLM [Quadro FX 570M] [10de:040c] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company G84GLM [Quadro FX 570M] [103c:30c5] InstallationDate: Installed on 2015-11-21 (228 days ago) InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) Package: xorg 1:7.7+13ubuntu3 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-28-generic root=UUID=bdc3be24-dee9-4ead-bca0-c9b1e45a87e5 ro persistent quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13 Tags: xenial ubuntu Uname: Linux 4.4.0-28-generic x86_64 UpgradeStatus: Upgraded to xenial on 2016-06-24 (12 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 12/01/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68MVD Ver. F.20 dmi.board.name: 30C5 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 71.36 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68MVDVer.F.20:bd12/01/2011:svnHewlett-Packard:pn:pvrF.20:rvnHewlett-Packard:rn30C5:rvrKBCVersion71.36:cvnHewlett-Packard:ct10:cvr: dmi.product.version: F.20 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1589056/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1615864] Re: Screen resolution not saved after reboot or logout and back in
Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. Ubuntu 16.04 (xenial) reached end-of-standard-support on April 29, 2021. I'm setting the status of this bug to 'Incomplete' as it's not seen any activity for some time. If this is still an issue when using a currently maintained release of Ubuntu then please let us know which one(s) otherwise this bug report can be left to expire in approximately 60 days time. ** Changed in: xorg (Ubuntu) Status: Confirmed => 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/1615864 Title: Screen resolution not saved after reboot or logout and back in Status in xorg package in Ubuntu: Incomplete Bug description: The issue is that Ubuntu 16.04 does not save or read the saved screen resolution settings of 1920x1080 from my Vizio 42 inch TV HDMI connected to my computer. When booting into the desktop the mouse pointer is small as if in 1920x1080 but then changes to a larger pointer then the resolution is then 1280x720 which seems to what 16.04 falls back to. The TV reports the proper information under xrandr. gee@HTPC:~$ xrandr Screen 0: minimum 8 x 8, current 1920 x 1080, maximum 4096 x 4096 VGA-0 disconnected (normal left inverted right x axis y axis) TV-0 disconnected (normal left inverted right x axis y axis) HDMI-0 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 980mm x 580mm 1280x720 60.00 + 59.94 1920x1080 59.9459.94* 60.0560.0050.04 720x576 50.0050.08 720x480 59.94 640x480 59.93 WORKAROUND: Type at the terminal: xrandr -s 1920x1080 --- .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: u'/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 304.131 Sun Nov 8 21:43:33 PST 2015 GCC version: gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.2) .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME-Flashback:Unity DistUpgraded: Fresh install DistroCodename: xenial DistroRelease: Ubuntu 16.04 DistroVariant: ubuntu DkmsStatus: nvidia-304, 304.131, 4.4.0-34-generic, x86_64: installed nvidia-304, 304.131, 4.4.0-36-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation C68 [GeForce 7050 PV / nForce 630a] [10de:053a] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] C68 [GeForce 7050 PV / nForce 630a] [1462:349f] InstallationDate: Installed on 2016-08-20 (12 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) Lsusb: Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 002: ID 099a:7202 Zippy Technology Corp. Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: MSI MS-7349 NonfreeKernelModules: nvidia Package: xorg 1:7.7+13ubuntu3 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-36-generic root=UUID=377930d2-4053-4a10-96ef-8cac652e4c24 ro quiet splash ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16 Tags: xenial ubuntu Uname: Linux 4.4.0-36-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin plugdev pulse pulse-access sambashare sudo video _MarkForUpload: True dmi.bios.date: 03/19/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: CaptiveWorks CW-3000HD V2.37 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: MS-7349 dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrCaptiveWorksCW-3000HDV2.37:bd03/19/2008:svnMSI:pnMS-7349:pvr1.0:rvnMSI:rnMS-7349:rvr1.0:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: MS-7349 dmi.product.version: 1.0 dmi.sys.vendor: MSI version.compiz: compiz 1:0.9.12.2+16.04.20160801.3-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
[Desktop-packages] [Bug 1803222] Re: keyboard is not typing anymore after walking up from suspend
Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. Ubuntu 16.04 (xenial) reached end-of-standard-support on April 29, 2021. I'm setting the status of this bug to 'Incomplete' as it's not seen any activity for some time. If this is still an issue when using a currently maintained release of Ubuntu then please let us know which one(s) otherwise this bug report can be left to expire in approximately 60 days time. ** Changed in: xorg-server (Ubuntu) Status: Confirmed => Incomplete -- 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/1803222 Title: keyboard is not typing anymore after walking up from suspend Status in xorg-server package in Ubuntu: Incomplete Bug description: my keyboard is not typing anymore after walking up from suspend ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-38.41~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-38-generic x86_64 NonfreeKernelModules: wl .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.18 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: Wed Nov 14 01:18:20 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 4.13.0-36-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 4.15.0-38-generic, x86_64: installed GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0106] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Sony Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [104d:90b8] InstallationDate: Installed on 2018-11-08 (5 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) MachineType: Sony Corporation SVF1421E2EW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic root=UUID=9e5fff3a-5a47-425f-aff8-0e05ed437a1c ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/19/2016 dmi.bios.vendor: Insyde Corp. dmi.bios.version: R0250DA dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.modalias: dmi:bvnInsydeCorp.:bvrR0250DA:bd07/19/2016:svnSonyCorporation:pnSVF1421E2EW:pvrC10JBKXD:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A: dmi.product.family: VAIO dmi.product.name: SVF1421E2EW dmi.product.version: C10JBKXD dmi.sys.vendor: Sony Corporation version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.91-2~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Wed Nov 14 01:04:21 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu4.1~16.04.2 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1803222/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2002904] Re: Firefox does not start in xubuntu 22.10: libgtk-3.so.0 not found
ok i have more info now, probably related i have simultaneously installed 2 snap versions: 2.57 the one in ubuntu reposs (deb package) 2.58 from snap -- 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/2002904 Title: Firefox does not start in xubuntu 22.10: libgtk-3.so.0 not found Status in firefox package in Ubuntu: New Status in snapd package in Ubuntu: New Bug description: freshly installed Xubuntu 22.10 --- ProblemType: Bug ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: XFCE DistroRelease: Ubuntu 22.10 InstallationDate: Installed on 2022-12-03 (43 days ago) InstallationMedia: Xubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221018) ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17 Snap: snapd 2.58 (latest/stable) Snap.Changes: ID Estado Generado Listo Resumen 16 Done2023-01-15T07:14:35+01:00 2023-01-15T07:26:56+01:00 Autorefrescar 6 snaps Tags: kinetic Uname: Linux 5.19.0-29-generic x86_64 UpgradeStatus: Upgraded to kinetic on 2023-01-15 (0 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2002904/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2002904] Snap.Info.snapd.txt
apport information ** Attachment added: "Snap.Info.snapd.txt" https://bugs.launchpad.net/bugs/2002904/+attachment/5641448/+files/Snap.Info.snapd.txt -- 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/2002904 Title: Firefox does not start in xubuntu 22.10: libgtk-3.so.0 not found Status in firefox package in Ubuntu: New Status in snapd package in Ubuntu: New Bug description: freshly installed Xubuntu 22.10 --- ProblemType: Bug ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: XFCE DistroRelease: Ubuntu 22.10 InstallationDate: Installed on 2022-12-03 (43 days ago) InstallationMedia: Xubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221018) ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17 Snap: snapd 2.58 (latest/stable) Snap.Changes: ID Estado Generado Listo Resumen 16 Done2023-01-15T07:14:35+01:00 2023-01-15T07:26:56+01:00 Autorefrescar 6 snaps Tags: kinetic Uname: Linux 5.19.0-29-generic x86_64 UpgradeStatus: Upgraded to kinetic on 2023-01-15 (0 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2002904/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2002904] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/2002904/+attachment/5641446/+files/ProcEnviron.txt -- 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/2002904 Title: Firefox does not start in xubuntu 22.10: libgtk-3.so.0 not found Status in firefox package in Ubuntu: New Status in snapd package in Ubuntu: New Bug description: freshly installed Xubuntu 22.10 --- ProblemType: Bug ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: XFCE DistroRelease: Ubuntu 22.10 InstallationDate: Installed on 2022-12-03 (43 days ago) InstallationMedia: Xubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221018) ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17 Snap: snapd 2.58 (latest/stable) Snap.Changes: ID Estado Generado Listo Resumen 16 Done2023-01-15T07:14:35+01:00 2023-01-15T07:26:56+01:00 Autorefrescar 6 snaps Tags: kinetic Uname: Linux 5.19.0-29-generic x86_64 UpgradeStatus: Upgraded to kinetic on 2023-01-15 (0 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2002904/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2002904] Snap.Connections.txt
apport information ** Attachment added: "Snap.Connections.txt" https://bugs.launchpad.net/bugs/2002904/+attachment/5641447/+files/Snap.Connections.txt -- 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/2002904 Title: Firefox does not start in xubuntu 22.10: libgtk-3.so.0 not found Status in firefox package in Ubuntu: New Status in snapd package in Ubuntu: New Bug description: freshly installed Xubuntu 22.10 --- ProblemType: Bug ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: XFCE DistroRelease: Ubuntu 22.10 InstallationDate: Installed on 2022-12-03 (43 days ago) InstallationMedia: Xubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221018) ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17 Snap: snapd 2.58 (latest/stable) Snap.Changes: ID Estado Generado Listo Resumen 16 Done2023-01-15T07:14:35+01:00 2023-01-15T07:26:56+01:00 Autorefrescar 6 snaps Tags: kinetic Uname: Linux 5.19.0-29-generic x86_64 UpgradeStatus: Upgraded to kinetic on 2023-01-15 (0 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2002904/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2002904] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/2002904/+attachment/5641445/+files/ProcCpuinfoMinimal.txt -- 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/2002904 Title: Firefox does not start in xubuntu 22.10: libgtk-3.so.0 not found Status in firefox package in Ubuntu: New Status in snapd package in Ubuntu: New Bug description: freshly installed Xubuntu 22.10 --- ProblemType: Bug ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: XFCE DistroRelease: Ubuntu 22.10 InstallationDate: Installed on 2022-12-03 (43 days ago) InstallationMedia: Xubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221018) ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17 Snap: snapd 2.58 (latest/stable) Snap.Changes: ID Estado Generado Listo Resumen 16 Done2023-01-15T07:14:35+01:00 2023-01-15T07:26:56+01:00 Autorefrescar 6 snaps Tags: kinetic Uname: Linux 5.19.0-29-generic x86_64 UpgradeStatus: Upgraded to kinetic on 2023-01-15 (0 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2002904/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2002904] Re: Firefox does not start in xubuntu 22.10: libgtk-3.so.0 not found
apport information ** Tags added: apport-collected ** Description changed: freshly installed Xubuntu 22.10 + --- + ProblemType: Bug + ApportVersion: 2.23.1-0ubuntu3 + Architecture: amd64 + CasperMD5CheckResult: pass + CurrentDesktop: XFCE + DistroRelease: Ubuntu 22.10 + InstallationDate: Installed on 2022-12-03 (43 days ago) + InstallationMedia: Xubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221018) + ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17 + Snap: snapd 2.58 (latest/stable) + Snap.Changes: + ID Estado Generado Listo Resumen + 16 Done2023-01-15T07:14:35+01:00 2023-01-15T07:26:56+01:00 Autorefrescar 6 snaps + Tags: kinetic + Uname: Linux 5.19.0-29-generic x86_64 + UpgradeStatus: Upgraded to kinetic on 2023-01-15 (0 days ago) + UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo + _MarkForUpload: True ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/2002904/+attachment/5641444/+files/Dependencies.txt -- 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/2002904 Title: Firefox does not start in xubuntu 22.10: libgtk-3.so.0 not found Status in firefox package in Ubuntu: New Status in snapd package in Ubuntu: New Bug description: freshly installed Xubuntu 22.10 --- ProblemType: Bug ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: XFCE DistroRelease: Ubuntu 22.10 InstallationDate: Installed on 2022-12-03 (43 days ago) InstallationMedia: Xubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221018) ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17 Snap: snapd 2.58 (latest/stable) Snap.Changes: ID Estado Generado Listo Resumen 16 Done2023-01-15T07:14:35+01:00 2023-01-15T07:26:56+01:00 Autorefrescar 6 snaps Tags: kinetic Uname: Linux 5.19.0-29-generic x86_64 UpgradeStatus: Upgraded to kinetic on 2023-01-15 (0 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2002904/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2002904] Re: Firefox does not start in xubuntu 22.10: libgtk-3.so.0 not found
purging and reinstalling seems to be a working workaround -- 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/2002904 Title: Firefox does not start in xubuntu 22.10: libgtk-3.so.0 not found Status in firefox package in Ubuntu: New Status in snapd package in Ubuntu: New Bug description: freshly installed Xubuntu 22.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2002904/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2002845] Re: debhelper 13.11.4ubuntu1 broke dh-translations
** Bug watch added: Debian Bug tracker #1028963 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028963 ** Also affects: debhelper (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028963 Importance: Unknown Status: Unknown ** Bug watch removed: Debian Bug tracker #1016354 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016354 -- 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/2002845 Title: debhelper 13.11.4ubuntu1 broke dh-translations Status in debhelper package in Ubuntu: Fix Committed Status in gnome-control-center package in Ubuntu: Invalid Status in gnome-text-editor package in Ubuntu: Invalid Status in pkgbinarymangler package in Ubuntu: Fix Released Status in debhelper package in Debian: Unknown Bug description: Today's debhelper 13.11.4ubuntu1 merge broke dh-translations. https://launchpad.net/ubuntu/+source/gnome-text-editor/43.2-1ubuntu1 gnome-text-editor build log excerpt --- dh_translations Can't exec "meson introspect '/<>/obj-x86_64-linux-gnu' --targets | jq -r -M '.[].name | select(endswith("-pot")) | sub("-pot"; "")'": No such file or directory at /usr/share/perl5/Debian/Debhelper/Dh_Lib.pm line 518. dh_translations: error: exec (for cmd: "meson introspect '/<>/obj-x86_64-linux-gnu' --targets | jq -r -M '.[].name | select(endswith(\"-pot\")) | sub(\"-pot\"; \"\")'") failed: No such file or directory dh_translations: error: "meson introspect '/<>/obj-x86_64-linux-gnu' --targets | jq -r -M '.[].name | select(endswith(\"-pot\")) | sub(\"-pot\"; \"\")'" returned exit code 25 Other Info -- Gunnar identified the bad commit as https://salsa.debian.org/debian/debhelper/-/commit/62a8608 https://launchpad.net/~gunnarhj/+archive/ubuntu/debhelper/+packages https://pastebin.ubuntu.com/p/P8qM2sHn9C/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debhelper/+bug/2002845/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2002904] Re: Firefox does not start in xubuntu 22.10: libgtk-3.so.0 not found
** Tags added: snap ** Also affects: firefox (Ubuntu) Importance: Undecided Status: New ** Tags added: kinetic -- 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/2002904 Title: Firefox does not start in xubuntu 22.10: libgtk-3.so.0 not found Status in firefox package in Ubuntu: New Status in snapd package in Ubuntu: New Bug description: freshly installed Xubuntu 22.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2002904/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2000862] Re: Nautilus search start tracker-miner-fs everytime
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nautilus (Ubuntu) Status: New => Confirmed -- 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/2000862 Title: Nautilus search start tracker-miner-fs everytime Status in nautilus package in Ubuntu: Confirmed Bug description: Everytime I enter a text in Nautilus to start a search, tracker-miner- fs starts, crawling the filesystem for 10-15 mins. No search results are shown before the process finish. However, if I start a search from the command line using tracker3 it works as expected, if I start a search from gnome-shell it works as expected, and with the nightly version of nautilus (flatpak) it works as expected as well. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: nautilus 1:43.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-26.27-generic 5.19.7 Uname: Linux 5.19.0-26-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Jan 2 11:38:22 2023 GsettingsChanges: b'org.gnome.nautilus.list-view' b'default-zoom-level' b"'small'" b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'" b'org.gnome.nautilus.window-state' b'initial-size' b'(1248, 638)' InstallationDate: Installed on 2022-02-25 (310 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) SourcePackage: nautilus UpgradeStatus: Upgraded to kinetic on 2022-10-09 (84 days ago) usr_lib_nautilus: file-roller 43.0-1 nautilus-extension-gnome-terminal 3.46.2-1ubuntu1 nautilus-share0.7.5-0.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2000862/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2000862] Re: Nautilus search start tracker-miner-fs everytime
I confirm in Ubuntu 22.10 very but very annoying bug that freezes gone-files and it unusable -- 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/2000862 Title: Nautilus search start tracker-miner-fs everytime Status in nautilus package in Ubuntu: Confirmed Bug description: Everytime I enter a text in Nautilus to start a search, tracker-miner- fs starts, crawling the filesystem for 10-15 mins. No search results are shown before the process finish. However, if I start a search from the command line using tracker3 it works as expected, if I start a search from gnome-shell it works as expected, and with the nightly version of nautilus (flatpak) it works as expected as well. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: nautilus 1:43.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-26.27-generic 5.19.7 Uname: Linux 5.19.0-26-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Jan 2 11:38:22 2023 GsettingsChanges: b'org.gnome.nautilus.list-view' b'default-zoom-level' b"'small'" b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'" b'org.gnome.nautilus.window-state' b'initial-size' b'(1248, 638)' InstallationDate: Installed on 2022-02-25 (310 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) SourcePackage: nautilus UpgradeStatus: Upgraded to kinetic on 2022-10-09 (84 days ago) usr_lib_nautilus: file-roller 43.0-1 nautilus-extension-gnome-terminal 3.46.2-1ubuntu1 nautilus-share0.7.5-0.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2000862/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1771331] Re: [radeon] boot error, low resolution graphic mode
Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. Ubuntu 16.04 (xenial) reached end-of-standard-support on April 29, 2021. I'm setting the status of this bug to 'Incomplete' as it's not seen any activity for some time. If this is still an issue when using a currently maintained release of Ubuntu then please let us know which one(s) otherwise this bug report can be left to expire in approximately 60 days time. ** Changed in: xorg-server (Ubuntu) Status: New => Incomplete -- 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/1771331 Title: [radeon] boot error, low resolution graphic mode Status in xorg-server package in Ubuntu: Incomplete Bug description: This error only takes a short time, I suppose it must be due to some update of the Kernel or due to a change in Xorg. It does not always happen, only on some occasions when (re) starting the system the error "graphic mode in low resolution" appears but the appearance of the desktop is the same. I do not use high resolution graphics or 3D games. Only typical desktop applications. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-124.148-generic 4.4.117 Uname: Linux 4.4.0-124-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.17 Architecture: amd64 BootLog: CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Tue May 15 12:45:53 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7540D] [1002:9991] (prog-if 00 [VGA controller]) Subsystem: ASRock Incorporation Trinity [Radeon HD 7540D] [1849:9991] InstallationDate: Installed on 2017-01-17 (482 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-124-generic root=UUID=e48303dd-74b7-4cd9-b061-53998eeb96fa ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/20/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.50 dmi.board.name: FM2A75M-HD+ dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.50:bd11/20/2013:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnFM2A75M-HD+:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.83-1~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Tue May 15 12:24:45 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-0ubuntu0.7 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1771331/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1638139] Re: xvfb fails to launch
Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. Ubuntu 14.04 (trusty) reached end-of-standard-support on April 25, 2019. I'm setting the status of this bug to 'Incomplete' as it's not seen any activity for some time. If this is still an issue when using a currently maintained release of Ubuntu then please let us know which one(s) otherwise this bug report can be left to expire in approximately 60 days time. ** Changed in: xorg-server (Ubuntu) Status: New => Incomplete -- 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/1638139 Title: xvfb fails to launch Status in xorg-server package in Ubuntu: Incomplete Bug description: The system for this bug is running Trusty with xvfb 2:1.15.1-0ubuntu2.7 Xvfb fails to launch after being used for a couple days and I can't see any reason to why it wont launch. We have inetd.conf setup to run an x11vnc script with the following command whenever a connection comes in on port 5902 (assumed to be a tunneled VNC). /usr/bin/x11vnc -inetd -oa /tmp/x11vnc.log -once -noxrecord -env FD_GEOM=1024x768 -env FD_XDMCP_IF=127.0.0.1 -create_xsrv Xvfb.xdmcp -gone 'pkill -f "Xvfb.*`echo $DISPLAY | cut -d . -f 1`\>"' x11vnc is attempting to launch xvfb but it's failing after having worked for multiple connections and there doesn't seem to be any indication on why. The log files show this error: 28/10/2016 20:22:28 x11vnc version: 0.9.13 lastmod: 2011-08-10 pid: 30524 28/10/2016 20:22:28 28/10/2016 20:22:28 wait_for_client: WAIT:cmd=FINDCREATEDISPLAY-Xvfb.xdmcp 28/10/2016 20:22:28 28/10/2016 20:22:28 initialize_screen: fb_depth/fb_bpp/fb_Bpl 24/32/2560 28/10/2016 20:22:28 28/10/2016 20:22:28 initialize_screen: -inetd mode: F_GETFL(stdin): 0x2 28/10/2016 20:22:28 initialize_screen: -inetd mode: F_GETFL(stdout): 0x2 28/10/2016 20:22:28 initialize_screen: -inetd mode and stdio is O_RDWR 28/10/2016 20:22:28 other clients: 28/10/2016 20:22:28 Normal socket connection 28/10/2016 20:22:28 incr accepted_client=1 for 127.0.0.1:40110 sock=3 28/10/2016 20:22:28 wait_for_client: got client 28/10/2016 20:22:28 client progressed=0 in 15/10 0.009395 s 28/10/2016 20:22:28 client useCopyRect: 127.0.0.1 0 28/10/2016 20:22:28 client_set_net: 127.0.0.1 0.0002 28/10/2016 20:22:28 wait_for_client: running: env X11VNC_SKIP_DISPLAY='' /bin/sh /tmp/x11vnc-find_display.6APOWs xauth: unable to generate an authority file name 28/10/2016 20:22:28 wait_for_client: find display cmd failed. 28/10/2016 20:22:28 wait_for_client: FINDCREATEDISPLAY cmd: /bin/sh /tmp/x11vnc-find_display.6APOWs Xvfb.xdmcp trying N=20 ... /root redir_daemon= /usr/bin/xauth: unable to generate an authority file name
[Desktop-packages] [Bug 1300620] Re: [Lenovo ThinkPad S1 Yoga] Middle button does not work for scrolling
Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. Ubuntu 14.04 (trusty) reached end-of-standard-support on April 25, 2019. I'm setting the status of this bug to 'Incomplete' as it's not seen any activity for some time. If this is still an issue when using a currently maintained release of Ubuntu then please let us know which one(s) otherwise this bug report can be left to expire in approximately 60 days time. ** Changed in: xorg (Ubuntu) Status: Confirmed => 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/1300620 Title: [Lenovo ThinkPad S1 Yoga] Middle button does not work for scrolling Status in xorg package in Ubuntu: Incomplete Bug description: On my clickpad (Touchpad with no button) the middle mouse button doesn't work for scrolling with trackpoint. I've configured a soft middlemouse button area via the following script: #!/bin/bash TOUCHPAD="SynPS/2 Synaptics TouchPad" TRACKPOINT="TPPS/2 IBM TrackPoint" killall -9 syndaemon echo "touchpad on" xinput set-prop "${TOUCHPAD}" "Synaptics Off" 0 echo "setting soft button areas" #Order: RightButtonAreaLeft, RightButtonAreaRight, RightButtonAreaTop, RightButtonAreaBottom, MiddleButtonAreaLeft, MiddleButtonAreaRight, MitddleButtonAreaTop, MiddleButtonAreaBottom" xinput set-prop "${TOUCHPAD}" "Synaptics Soft Button Areas" 4000, 0, 4063, 0, 3000, 4000, 4063, 1500 #xinput set-prop "${TOUCHPAD}" "Synaptics Soft Button Areas" 4000, 0, 0, 4466, 3000, 3999, 0, 1500 echo "enable twofingerscrolling in both directions" xinput set-prop "${TOUCHPAD}" "Synaptics Two-Finger Scrolling" 1, 1 echo "shortening upper and lower edge to reserve space for 'just button' actions. Order: left, right, top, bottom" xinput set-prop "${TOUCHPAD}" "Synaptics Area" 0, 0, 1500, 4000 #workaround for just scrolling #xinput set-prop "${TOUCHPAD}" "Synaptics Area" 0, 4000, 1500, 0 echo "enabling palm detection" xinput set-prop "${TOUCHPAD}" "Synaptics Palm Detection" 1 #echo "Middle mouse button emulation for scrolling on trackpoint" #xinput set-prop "${TRACKPOINT}" "Evdev Wheel Emulation" 1 #xinput set-prop "${TRACKPOINT}" "Evdev Wheel Emulation Button" 2 #xinput set-prop "${TRACKPOINT}" "Evdev Wheel Emulation Timeout" 200 #xinput set-prop "${TRACKPOINT}" "Evdev Wheel Emulation Axes" 6 7 4 5 # horizontal und vertikal echo "enable tap events" # RTCornerButton, RBCornerButton, LTCornerButton, LBCornerButton, TapButton1, TapButton2, TapButton3 xinput set-prop "${TOUCHPAD}" "Synaptics Tap Action" 2, 3, 1, 1, 1, 3, 0 echo "list actual properties" xinput list-props "${TOUCHPAD}" echo "no touch while typing" syndaemon -i 0.5 -d ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7 Uname: Linux 3.13.0-20-generic x86_64 ApportVersion: 2.14-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: kwin CurrentDesktop: KDE Date: Tue Apr 1 09:02:37 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: kubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:2217] InstallationDate: Installed on 2014-03-25 (6 days ago) InstallationMedia: Kubuntu 14.04 LTS "Trusty Tahr" - Beta amd64 (20140324) LightdmGreeterLog: QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: Datei oder Verzeichnis nicht gefunden QFileSystemWatcher: failed to add paths: /var/lib/lightdm/.config/ibus/bus Bus::open: Can not get ibus-daemon's address. IBusInputContext::createInputContext: no connection to ibus-daemon file:///usr/share/kde4/apps/lightdm-kde-greeter/themes/userbar/main.qml:135: Unable to assign [undefined] to QString usersession LightdmGreeterLogOld: QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: Datei oder Verzeichnis nicht gefunden QFileSystemWatcher: failed to add paths: /var/lib/lightdm/.config/ibus/bus Bus::open: Can not get ibus-daemon's address. IBusInputContext::createInputContext: no connection to ibus-daemon file:///usr/share/kde4/apps/lightdm-kde-greeter/themes/userbar/main.qml:135: Unable to assign [undefined] to QString usersession MachineType: LENOVO 20C0S0AX00 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-20-generic.efi.signed root=UUID=389305e0-f86b-4068-a352-fe5597926b87 ro rootflags=subvol=@ kopt=root=/dev/mapper/ray-root quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade
[Desktop-packages] [Bug 1300707] Re: Xorg crashed with SIGABRT in __GI___open_catalog()
Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. Ubuntu 14.04 (trusty) reached end-of-standard-support on April 25, 2019. I'm setting the status of this bug to 'Incomplete' as it's not seen any activity for some time. If this is still an issue when using a currently maintained release of Ubuntu then please let us know which one(s) otherwise this bug report can be left to expire in approximately 60 days time. ** Changed in: xorg-server (Ubuntu) Status: New => Incomplete -- 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/1300707 Title: Xorg crashed with SIGABRT in __GI___open_catalog() Status in xorg-server package in Ubuntu: Incomplete Bug description: Happens during Portal2 play, intel driver. ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: xserver-xorg-core 2:1.15.0-1ubuntu7 ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7 Uname: Linux 3.13.0-19-generic i686 ApportVersion: 2.13.3-0ubuntu1 Architecture: i386 Date: Fri Mar 28 18:25:51 2014 ExecutablePath: /usr/bin/Xorg InstallationDate: Installed on 2013-07-19 (255 days ago) InstallationMedia: Xubuntu 13.04 "Raring Ringtail" - Release i386 (20130423.1) ProcCmdline: /usr/bin/X -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch ProcEnviron: Signal: 6 SourcePackage: xorg-server StacktraceTop: __GI___open_catalog (cat_name=0xb9097d88 "\030r\t\271(\246\f\271\340\337\n\271\021", nlspath=0x1 , env_var=0xb8bb8268 "@\225\273\270`\004,\267nux/", catalog=0x0) at open_catalog.c:278 Title: Xorg crashed with SIGABRT in __GI___open_catalog() UpgradeStatus: Upgraded to trusty on 2013-11-30 (121 days ago) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1300707/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1485676] Re: Windows titlebar doesn't correctly handle clicks from multitouch input devices
Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. Ubuntu 14.04 (trusty) reached end-of-standard-support on April 25, 2019. I'm setting the status of this bug to 'Incomplete' as it's not seen any activity for some time. If this is still an issue when using a currently maintained release of Ubuntu then please let us know which one(s) otherwise this bug report can be left to expire in approximately 60 days time. ** Changed in: xorg-server (Ubuntu) Status: New => Incomplete -- 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/1485676 Title: Windows titlebar doesn't correctly handle clicks from multitouch input devices Status in xorg-server package in Ubuntu: Incomplete Bug description: Hi, it seems that in Ubuntu Gnome 14.04 LTS with xfce4 as window manager, windows seems "locked" in their position on the screen. If I click on every other position the mouse pointer moves and click works, but on title-bar nothing happens, neither close/resize/hide buttons work. After a few debugging I've found the problem is related to Xorg bug #70790 (https://bugzilla.freedesktop.org/show_bug.cgi?id=70790) which has been fixed in January with patch at https://bugzilla.freedesktop.org/attachment.cgi?id=111666. So I've rebuilt the xorg-xserver-core packages with patch applied (just 3 lines) and everything works correctly. Is there a way to have it fixed on main distribution too ? Thank you, Luca ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xserver-xorg-core 2:1.15.1-0ubuntu2.7 ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Mon Aug 17 18:20:45 2015 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation ValleyView Gen7 [8086:0f31] (rev 0e) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation ValleyView Gen7 [8086:0f31] InstallationDate: Installed on 2015-08-17 (0 days ago) InstallationMedia: Ubuntu-GNOME 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) MachineType: TOSHIBA 6140E3R ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=it_IT.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic root=UUID=cdcce3b8-7bcf-44bd-8c0a-b37cdba2bb93 ro quiet splash vt.handoff=7 SourcePackage: xorg-server UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/01/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: XCKT120 dmi.board.name: Intel Bay Trail - Desktop dmi.board.vendor: TOSHIBA dmi.board.version: 1.0 dmi.chassis.type: 13 dmi.chassis.vendor: TOSHIBA dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrXCKT120:bd08/01/2014:svnTOSHIBA:pn6140E3R:pvr6140E3R:rvnTOSHIBA:rnIntelBayTrail-Desktop:rvr1.0:cvnTOSHIBA:ct13:cvr: dmi.product.name: 6140E3R dmi.product.version: 6140E3R dmi.sys.vendor: TOSHIBA version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.60-2~ubuntu14.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.4 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1.6 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Mon Aug 17 18:18:17 2015 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.15.1-0ubuntu2.7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1485676/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2002290] Re: Poor Arabic rendering in VTE
Hi Egmond. Thank you for the info. About lam-alif: Yes, you are right. It indeed is displayed like a U in my screenshot, although it should have been similar to a "y", but as you said, it is not that terribly bad and can be read without an issue. Perhaps we can improve it in a future work! About RTL bug: I have searched and found the following file from you regarding the modes you described: https://github.com/skirino/vte/blob/master/perf/bidi.sh And I tried the following modes: - alias ltr='printf "\e[1 k"' - alias rtl='printf "\e[2 k"' I attached images for how they look like (Also a 3rd screenshot for autodetect again). The RTL base one would have been good if the user is expected to write everything 100% in Arabic. However that's not the case; normal commands are written in English but the output of the commands may be Arabic, and some strings may not be translated. You can see how the Shell interrupter is displayed totally missed up if you write one line in English, and the other line in Arabic. In fact, if you try to write in English using RTL base, then you will notice that the shell interrupter is moving to the left side with you as you write! :D I think it would be good if someone developed a command line based tool in Arabic/RTL languages, then he/she can opt for using this mode by default (because their application is 100% for RTL-based audience), but in the normal average terminal it would be a horrible user experience. The LTR one was just like the default situation in VTE. The text is not displayed good if it was Arabic and the line gets messed up. Please tell me if you need more tests or experiments, I would be happy to provide them. Yes, of course we can also add Urdu and Persian and other RTL-based languages to the list from $locale, it was just a simple example. Thank you again Egmont for taking time to do all this work and respond here. Best. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/2002290 Title: Poor Arabic rendering in VTE Status in gnome-terminal package in Ubuntu: New Status in vte2.91 package in Ubuntu: New Bug description: VTE has a number of issues when it comes to rendering Arabic letters in the terminal, which could affect a number of languages (Arabic, Urdu, Persian... etc). Bug 1: Any Arabic word in any VTE-based terminal is choppily displayed with spaces between its letters, making readability hard and sometimes not possible. Sometimes the letters are crushed together very closely making reading impossible too. Bug 2: If a non-Arabic text and an Arabic text are displayed together in the same line, then the entire line will be missed up and you won't be able to understand what is being said. Both of these bugs can be seen from the image I attached. I reported both of these bugs together because it's unlikely they can be fixed separately, probably they are related to each other. Problem can be seen in any VTE-based terminal. Here I am using GNOME Terminal 3.44.0 on Ubuntu 22.04, but it can be seen in any Ubuntu version and in any terminal version as well (it has been there since forever). I reported the bug here instead of upstream because that's what they said at the page: https://wiki.gnome.org/Apps/Terminal/ReportingBugs, but this bug is not related to Ubuntu only; it happens on all Linux distributions. Happy to provide any information you need, or any do tests or experiments. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/2002290/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2002290] Re: Poor Arabic rendering in VTE
** Attachment added: "VTE BiDi LTR base.png" https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/2002290/+attachment/5641433/+files/VTE%20BiDi%20LTR%20base.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/2002290 Title: Poor Arabic rendering in VTE Status in gnome-terminal package in Ubuntu: New Status in vte2.91 package in Ubuntu: New Bug description: VTE has a number of issues when it comes to rendering Arabic letters in the terminal, which could affect a number of languages (Arabic, Urdu, Persian... etc). Bug 1: Any Arabic word in any VTE-based terminal is choppily displayed with spaces between its letters, making readability hard and sometimes not possible. Sometimes the letters are crushed together very closely making reading impossible too. Bug 2: If a non-Arabic text and an Arabic text are displayed together in the same line, then the entire line will be missed up and you won't be able to understand what is being said. Both of these bugs can be seen from the image I attached. I reported both of these bugs together because it's unlikely they can be fixed separately, probably they are related to each other. Problem can be seen in any VTE-based terminal. Here I am using GNOME Terminal 3.44.0 on Ubuntu 22.04, but it can be seen in any Ubuntu version and in any terminal version as well (it has been there since forever). I reported the bug here instead of upstream because that's what they said at the page: https://wiki.gnome.org/Apps/Terminal/ReportingBugs, but this bug is not related to Ubuntu only; it happens on all Linux distributions. Happy to provide any information you need, or any do tests or experiments. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/2002290/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2002290] Re: Poor Arabic rendering in VTE
** Attachment added: "VTE BiDi RTL base.png" https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/2002290/+attachment/5641432/+files/VTE%20BiDi%20RTL%20base.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/2002290 Title: Poor Arabic rendering in VTE Status in gnome-terminal package in Ubuntu: New Status in vte2.91 package in Ubuntu: New Bug description: VTE has a number of issues when it comes to rendering Arabic letters in the terminal, which could affect a number of languages (Arabic, Urdu, Persian... etc). Bug 1: Any Arabic word in any VTE-based terminal is choppily displayed with spaces between its letters, making readability hard and sometimes not possible. Sometimes the letters are crushed together very closely making reading impossible too. Bug 2: If a non-Arabic text and an Arabic text are displayed together in the same line, then the entire line will be missed up and you won't be able to understand what is being said. Both of these bugs can be seen from the image I attached. I reported both of these bugs together because it's unlikely they can be fixed separately, probably they are related to each other. Problem can be seen in any VTE-based terminal. Here I am using GNOME Terminal 3.44.0 on Ubuntu 22.04, but it can be seen in any Ubuntu version and in any terminal version as well (it has been there since forever). I reported the bug here instead of upstream because that's what they said at the page: https://wiki.gnome.org/Apps/Terminal/ReportingBugs, but this bug is not related to Ubuntu only; it happens on all Linux distributions. Happy to provide any information you need, or any do tests or experiments. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/2002290/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2002290] Re: Poor Arabic rendering in VTE
** Attachment added: "VTE BiDi autodetect.png" https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/2002290/+attachment/5641431/+files/VTE%20BiDi%20autodetect.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/2002290 Title: Poor Arabic rendering in VTE Status in gnome-terminal package in Ubuntu: New Status in vte2.91 package in Ubuntu: New Bug description: VTE has a number of issues when it comes to rendering Arabic letters in the terminal, which could affect a number of languages (Arabic, Urdu, Persian... etc). Bug 1: Any Arabic word in any VTE-based terminal is choppily displayed with spaces between its letters, making readability hard and sometimes not possible. Sometimes the letters are crushed together very closely making reading impossible too. Bug 2: If a non-Arabic text and an Arabic text are displayed together in the same line, then the entire line will be missed up and you won't be able to understand what is being said. Both of these bugs can be seen from the image I attached. I reported both of these bugs together because it's unlikely they can be fixed separately, probably they are related to each other. Problem can be seen in any VTE-based terminal. Here I am using GNOME Terminal 3.44.0 on Ubuntu 22.04, but it can be seen in any Ubuntu version and in any terminal version as well (it has been there since forever). I reported the bug here instead of upstream because that's what they said at the page: https://wiki.gnome.org/Apps/Terminal/ReportingBugs, but this bug is not related to Ubuntu only; it happens on all Linux distributions. Happy to provide any information you need, or any do tests or experiments. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/2002290/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp