[Desktop-packages] [Bug 1885998] Re: Unable to use fingerprint login
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command, as it will automatically gather debugging information, in a terminal: apport-collect 1885998 When reporting bugs in the future please use apport by using 'ubuntu- bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs. ** Package changed: gnome-control-center (Ubuntu) => libfprint (Ubuntu) ** Changed in: libfprint (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1885998 Title: Unable to use fingerprint login Status in libfprint package in Ubuntu: Incomplete Bug description: I'm using ubuntu 20.04 LTS on ThinkPad X390. When I'm trying to enable fingerprint login, there's an error: GDBus.Error:net.reactivated.Fprint.Error.Internal:Open failed with error: The driver encountered a protocol error with the divice. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libfprint/+bug/1885998/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1885998] [NEW] Unable to use fingerprint login
Public bug reported: I'm using ubuntu 20.04 LTS on ThinkPad X390. When I'm trying to enable fingerprint login, there's an error: GDBus.Error:net.reactivated.Fprint.Error.Internal:Open failed with error: The driver encountered a protocol error with the divice. ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New -- 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/1885998 Title: Unable to use fingerprint login Status in gnome-control-center package in Ubuntu: New Bug description: I'm using ubuntu 20.04 LTS on ThinkPad X390. When I'm trying to enable fingerprint login, there's an error: GDBus.Error:net.reactivated.Fprint.Error.Internal:Open failed with error: The driver encountered a protocol error with the divice. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1885998/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1857392] Re: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10).
Running 20.04. Seems to me this bug appears only after I run Transmission Bit Torrent Client. My log files have shown that my kernel has been changed and after that I may lose wifi and lan connectivity. I have performed a fresh install of 20.04 numerous times to eliminate the problem and have run a fresh install for days without any problems until Transmission is run. Logs show that the my kernel was modified from root however I do not even know how to access root much less make changes to the kernel. I am wondering if there is some agency or entity that makes these changes as root to prevent torrenting, Below is copy of my warnings from logs. 10:12:38 PM dbus-daemon: [session uid=1000 pid=1610] Successfully activated service 'org.gnome.Logs' 9:15:10 PM gnome-shell: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10). 9:15:10 PM gnome-shell: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10). 9:15:10 PM gnome-shell: Window manager warning: Overwriting existing binding of keysym 36 with keysym 36 (keycode f). 9:15:10 PM gnome-shell: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e). 9:15:10 PM gnome-shell: Window manager warning: Overwriting existing binding of keysym 39 with keysym 39 (keycode 12). 9:15:10 PM gnome-shell: Window manager warning: Overwriting existing binding of keysym 38 with keysym 38 (keycode 11). 9:15:10 PM gnome-shell: Window manager warning: Overwriting existing binding of keysym 34 with keysym 34 (keycode d). 9:15:10 PM gnome-shell: Window manager warning: Overwriting existing binding of keysym 33 with keysym 33 (keycode c). 9:15:10 PM gnome-shell: Window manager warning: Overwriting existing binding of keysym 32 with keysym 32 (keycode b). 9:15:10 PM gnome-shell: Window manager warning: Overwriting existing binding of keysym 31 with keysym 31 (keycode a). 9:07:50 PM systemd: tracker-store.service: Succeeded. 9:07:50 PM tracker-store: OK 9:07:20 PM systemd: Started Tracker metadata database store and lookup manager. 9:07:20 PM dbus-daemon: [session uid=1000 pid=1610] Successfully activated service 'org.freedesktop.Tracker1' 9:07:20 PM systemd: Starting Tracker metadata database store and lookup manager... 9:07:20 PM dbus-daemon: [session uid=1000 pid=1610] Activating via systemd: service name='org.freedesktop.Tracker1' unit='tracker-store.service' requested by ':1.0' (uid=1000 pid=1607 comm="/usr/libexec/tracker-miner-fs " label="unconfined") Below is copy of my logs with "kernel" in the search option. 8:42:53 PM kernel: perf: interrupt took too long (3942 > 3930), lowering kernel.perf_event_max_sample_rate to 50500 6:59:33 PM kernel: snd_hda_codec_idt hdaudioC1D0:speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) 6:59:33 PM kernel: [TTM] Zone kernel: Available graphics memory: 1746504 KiB 6:59:33 PM kernel: [drm] initializing kernel modesetting (SUMO 0x1002:0x9647 0x103C:0x169B 0x00). 6:59:27 PM kernel: Started udev Kernel Device Manager. 6:59:27 PM kernel: Starting udev Kernel Device Manager... 6:59:27 PM kernel: Finished Apply Kernel Variables. 6:59:27 PM kernel: Mounted Kernel Configuration File System. 6:59:27 PM kernel: Starting Apply Kernel Variables... 6:59:27 PM kernel: Mounting Kernel Configuration File System... 6:59:27 PM kernel: Finished Load Kernel Modules. 6:59:27 PM kernel: Mounted Kernel Trace File System. 6:59:27 PM kernel: Starting Remount Root and Kernel File Systems... 6:59:27 PM kernel: Mounting Kernel Trace File System... 6:59:27 PM kernel: Listening on udev Kernel Socket. 6:59:27 PM kernel: Freeing unused kernel image memory: 1192K 6:59:27 PM kernel: Write protecting the kernel read-only data: 22528k 6:59:27 PM kernel: Freeing unused kernel image memory: 2712K 6:59:27 PM kernel: Loaded X.509 cert 'Build time autogenerated kernel key: fc5d997396576c92a1f0014cbc11f394a5a98020' 6:59:27 PM kernel: Memory: 3432580K/3648416K available (14339K kernel code, 2397K rwdata, 4952K rodata, 2712K init, 4992K bss, 215836K reserved, 0K cma-reserved) 6:59:27 PM kernel: Kernel command line: BOOT_IMAGE=/boot/vmlinuz-5.4.0-39-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 6:59:27 PM kernel: Booting paravirtualized kernel on bare hardware 6:59:27 PM kernel: KERNEL supported cpus: This log show no unusual changes as noted from previous sessions requiring a fresh install with the possible exception of the first line of the above log, but I included it for reference. Has anybody else noticed these warnings after torrenting? -- 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/1857392 Title: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10). Status in gnome-shell package in Ubuntu: Confirmed Bug description: 1) Ub
[Desktop-packages] [Bug 362359] Re: Focus gets stuck to a window - impossible to select other windows
I just experienced this behavior with Ubuntu 20.04 (Gnome, X11, Nvidia GTX 1070). Only one window had focus. Some windows appeared in front of the focused window, but I could not click on them - clicking on them only sent mouse clicks to the window in the background. The "dots" in the dock that show what applications are open all disappeared, and if I moved my mouse over the apps then they became highlighted and wouldn't un-highlight. This is the first time I've experienced this issue, I've been using Ubuntu 20.04 since release, and 18.04 before that since its release. -- 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/362359 Title: Focus gets stuck to a window - impossible to select other windows Status in xorg-server package in Ubuntu: Fix Released Bug description: Alright, terribly annoying bug that gets me to reboot several times a day, but very hard to understand how to trigger it. What happens: after some time of usage, you get "stuck" in a window. Idem est, you can not select another window. You can still click, select and drag in the window that has the focus, but clicking on other windows, or on the panel, just doesn't work. Notes: - With window I don't mean "application window". For example it can only be the page view in firefox, and you won't be able to click the buttons or the URL field. It can also be the main text window in xchat, and you wont be able to click in the user list or to change the chatroom. - The click seems to be grabbed by the window having the focus, even if you click outside of it. For example, using xchat, if the main text window has focus, clicking and dragging in the user list will actually select text in the main text window. - Using xev, it seems that clics do not get passed to the correct window at all (nothing received) - I have no idea what triggers this as sometimes it will trigger alone - pc works, I leave it for an hour, I come back, the problem is triggered - Curious effect now: dragging and dropping to another window gives focus to the window, and seems to be the only way to do so. For example if in firefox the main page view window has the focus and I cant click the buttons, drag and dropping text to the buttons gives the focus to the buttons, and I can't clic the page view window anymore. Drag and dropping a button to the page view window gives it its focus back Additional info: * Compiz disabled * Intel graphic card * Ubuntu jaunty - latest patches * Using a laptop, with an USB mouse HAL, xserver, I have no idea where to file this bug into. I hope it will be fixed before the release, it is really terribly annoying :s Please tell me if there is any other detail I can provide. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/362359/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1875005] Re: It's impossible to easily switch between integrated AMD GPU and dedicated NVIDIA card without rebooting
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: xserver-xorg-video-amdgpu (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-amdgpu in Ubuntu. https://bugs.launchpad.net/bugs/1875005 Title: It's impossible to easily switch between integrated AMD GPU and dedicated NVIDIA card without rebooting Status in mutter package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-440 package in Ubuntu: Confirmed Status in xserver-xorg-video-amdgpu package in Ubuntu: Confirmed Bug description: I have a laptop with both AMD Raven and Nvidia GTX 1050 video adapters. I wanted to test the new game mode in Ubuntu 20.04, and noticed that only the AMD Raven actually works. To do the test, I tried launching a terminal and running gxgears, both in a normal way, and then using the "start using dedicated video adapter" (or whatever it really is in English) option in gnome-shell. Using the standard video adapter (probably the AMD Raven), it works, but slowly. Using the dedicated video adapter, I get the following: juloliv@juloliv:~$ glxgears X Error of failed request: BadValue (integer parameter out of range for operation) Major opcode of failed request: 152 (GLX) Minor opcode of failed request: 3 (X_GLXCreateContext) Value in failed request: 0x0 Serial number of failed request: 25 Current serial number in output stream: 26 NB: in both cases, I tried launching nvidia-settings and got the following: juloliv@juloliv:~$ nvidia-settings ERROR: Unable to load info from any available system (nvidia-settings:9213): GLib-GObject-CRITICAL **: 12:33:29.270: g_object_unref: assertion 'G_IS_OBJECT (object)' failed ** Message: 12:33:29.273: PRIME: No offloading required. Abort ** Message: 12:33:29.273: PRIME: is it supported? no And then a blank window... ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] est un dossier: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2) ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: GNOME Date: Sat Apr 25 12:26:50 2020 DistUpgraded: 2020-04-24 17:27:13,114 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: L’exécution du processus fils « ./xorg_fix_proprietary.py » a échoué (Aucun fichier ou dossier de ce type) (8)) DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 440.64, 5.4.0-26-generic, x86_64: installed EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GraphicsCard: Subsystem: ASUSTeK Computer Inc. GP107M [GeForce GTX 1050 Mobile] [1043:1bb1] Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev c2) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Picasso [1043:1bb1] InstallationDate: Installed on 2020-02-07 (77 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: ASUSTeK COMPUTER INC. VivoBook_ASUSLaptop X570DD_D570DD ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic root=UUID=decd423a-61f1-452c-bf0d-16b54ea1b5ad ro quiet splash nouveau.modeset=0 vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-04-24 (0 days ago) dmi.bios.date: 06/28/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X570DD.300 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X570DD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX570DD.300:bd06/28/2019:svnASUSTeKCOMPUTERINC.:pnVivoBook_ASUSLaptopX570DD_D570DD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX570DD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: VivoBook dmi.product.name: VivoBook_ASUSLaptop X570DD_D570DD dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. nvidia-settings: ERROR: Unable to load info from any available system ERROR: U
[Desktop-packages] [Bug 1875005] Re: It's impossible to easily switch between integrated AMD GPU and dedicated NVIDIA card without rebooting
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nvidia-graphics-drivers-440 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-amdgpu in Ubuntu. https://bugs.launchpad.net/bugs/1875005 Title: It's impossible to easily switch between integrated AMD GPU and dedicated NVIDIA card without rebooting Status in mutter package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-440 package in Ubuntu: Confirmed Status in xserver-xorg-video-amdgpu package in Ubuntu: Confirmed Bug description: I have a laptop with both AMD Raven and Nvidia GTX 1050 video adapters. I wanted to test the new game mode in Ubuntu 20.04, and noticed that only the AMD Raven actually works. To do the test, I tried launching a terminal and running gxgears, both in a normal way, and then using the "start using dedicated video adapter" (or whatever it really is in English) option in gnome-shell. Using the standard video adapter (probably the AMD Raven), it works, but slowly. Using the dedicated video adapter, I get the following: juloliv@juloliv:~$ glxgears X Error of failed request: BadValue (integer parameter out of range for operation) Major opcode of failed request: 152 (GLX) Minor opcode of failed request: 3 (X_GLXCreateContext) Value in failed request: 0x0 Serial number of failed request: 25 Current serial number in output stream: 26 NB: in both cases, I tried launching nvidia-settings and got the following: juloliv@juloliv:~$ nvidia-settings ERROR: Unable to load info from any available system (nvidia-settings:9213): GLib-GObject-CRITICAL **: 12:33:29.270: g_object_unref: assertion 'G_IS_OBJECT (object)' failed ** Message: 12:33:29.273: PRIME: No offloading required. Abort ** Message: 12:33:29.273: PRIME: is it supported? no And then a blank window... ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] est un dossier: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2) ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: GNOME Date: Sat Apr 25 12:26:50 2020 DistUpgraded: 2020-04-24 17:27:13,114 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: L’exécution du processus fils « ./xorg_fix_proprietary.py » a échoué (Aucun fichier ou dossier de ce type) (8)) DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 440.64, 5.4.0-26-generic, x86_64: installed EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GraphicsCard: Subsystem: ASUSTeK Computer Inc. GP107M [GeForce GTX 1050 Mobile] [1043:1bb1] Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev c2) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Picasso [1043:1bb1] InstallationDate: Installed on 2020-02-07 (77 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: ASUSTeK COMPUTER INC. VivoBook_ASUSLaptop X570DD_D570DD ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic root=UUID=decd423a-61f1-452c-bf0d-16b54ea1b5ad ro quiet splash nouveau.modeset=0 vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-04-24 (0 days ago) dmi.bios.date: 06/28/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X570DD.300 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X570DD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX570DD.300:bd06/28/2019:svnASUSTeKCOMPUTERINC.:pnVivoBook_ASUSLaptopX570DD_D570DD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX570DD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: VivoBook dmi.product.name: VivoBook_ASUSLaptop X570DD_D570DD dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. nvidia-settings: ERROR: Unable to load info from any available system ERROR:
[Desktop-packages] [Bug 1875005] Re: It's impossible to easily switch between integrated AMD GPU and dedicated NVIDIA card without rebooting
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: mutter (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-amdgpu in Ubuntu. https://bugs.launchpad.net/bugs/1875005 Title: It's impossible to easily switch between integrated AMD GPU and dedicated NVIDIA card without rebooting Status in mutter package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-440 package in Ubuntu: Confirmed Status in xserver-xorg-video-amdgpu package in Ubuntu: Confirmed Bug description: I have a laptop with both AMD Raven and Nvidia GTX 1050 video adapters. I wanted to test the new game mode in Ubuntu 20.04, and noticed that only the AMD Raven actually works. To do the test, I tried launching a terminal and running gxgears, both in a normal way, and then using the "start using dedicated video adapter" (or whatever it really is in English) option in gnome-shell. Using the standard video adapter (probably the AMD Raven), it works, but slowly. Using the dedicated video adapter, I get the following: juloliv@juloliv:~$ glxgears X Error of failed request: BadValue (integer parameter out of range for operation) Major opcode of failed request: 152 (GLX) Minor opcode of failed request: 3 (X_GLXCreateContext) Value in failed request: 0x0 Serial number of failed request: 25 Current serial number in output stream: 26 NB: in both cases, I tried launching nvidia-settings and got the following: juloliv@juloliv:~$ nvidia-settings ERROR: Unable to load info from any available system (nvidia-settings:9213): GLib-GObject-CRITICAL **: 12:33:29.270: g_object_unref: assertion 'G_IS_OBJECT (object)' failed ** Message: 12:33:29.273: PRIME: No offloading required. Abort ** Message: 12:33:29.273: PRIME: is it supported? no And then a blank window... ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] est un dossier: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2) ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: GNOME Date: Sat Apr 25 12:26:50 2020 DistUpgraded: 2020-04-24 17:27:13,114 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: L’exécution du processus fils « ./xorg_fix_proprietary.py » a échoué (Aucun fichier ou dossier de ce type) (8)) DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 440.64, 5.4.0-26-generic, x86_64: installed EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GraphicsCard: Subsystem: ASUSTeK Computer Inc. GP107M [GeForce GTX 1050 Mobile] [1043:1bb1] Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev c2) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Picasso [1043:1bb1] InstallationDate: Installed on 2020-02-07 (77 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: ASUSTeK COMPUTER INC. VivoBook_ASUSLaptop X570DD_D570DD ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic root=UUID=decd423a-61f1-452c-bf0d-16b54ea1b5ad ro quiet splash nouveau.modeset=0 vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-04-24 (0 days ago) dmi.bios.date: 06/28/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X570DD.300 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X570DD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX570DD.300:bd06/28/2019:svnASUSTeKCOMPUTERINC.:pnVivoBook_ASUSLaptopX570DD_D570DD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX570DD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: VivoBook dmi.product.name: VivoBook_ASUSLaptop X570DD_D570DD dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. nvidia-settings: ERROR: Unable to load info from any available system ERROR: Unable to load info
[Desktop-packages] [Bug 1716301] Re: wifi driver: mt7601u not work on 16.04
Tested and now my MT7601U USB Dongle (Ralink Technology, Corp. MT7601U Wireless Adapter) is working in Ubuntu 20.04 :) https://askubuntu.com/questions/1205254/ralink-tech-mt7601u-wireless-adapter-on-xubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to usb-modeswitch-data in Ubuntu. https://bugs.launchpad.net/bugs/1716301 Title: wifi driver: mt7601u not work on 16.04 Status in linux package in Ubuntu: Confirmed Status in usb-modeswitch-data package in Ubuntu: Confirmed Bug description: In the beginning, when the adapter is pluged in, it's mounted as a disk including driver files for Windows, and $> lsusb Bus 003 Device 010: ID 148f:2878 Ralink Technology, Corp. after eject the disk, $> lsusb Bus 003 Device 011: ID 148f:7601 Ralink Technology, Corp. MT7601U Wireless Adapter I tried following 3 drivers: 1) the default mt7601u included in the kernel: 4.4.0-91-generic after eject the disk, $> lsmod|grep mt mt7601u 102400 0 mac80211 737280 1 mt7601u cfg80211 565248 2 mac80211,mt7601u binfmt_misc 20480 1 $> modinfo mt7601u filename: /lib/modules/4.4.0-91-generic/kernel/drivers/net/wireless/mediatek/mt7601u/mt7601u.ko srcversion: E8B632D369E0C2A9F1CF7D8 alias: usb:v7392p7710d*dc*dsc*dp*ic*isc*ip*in* .. depends: mac80211,cfg80211 intree: Y vermagic: 4.4.0-91-generic SMP mod_unload modversions $> dmesg // begin [ 4581.094119] usb 3-4: USB disconnect, device number 6 [ 4584.872751] usb 3-4: new high-speed USB device number 7 using xhci_hcd [ 4585.001408] usb 3-4: New USB device found, idVendor=148f, idProduct=2878 [ 4585.001413] usb 3-4: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 4585.001416] usb 3-4: Product: Љ [ 4585.001418] usb 3-4: Manufacturer: Љ [ 4585.001753] usb-storage 3-4:1.0: USB Mass Storage device detected [ 4585.001873] scsi host6: usb-storage 3-4:1.0 [ 4586.001122] scsi 6:0:0:0: CD-ROM MediaTek Flash autorun 0.01 PQ: 0 ANSI: 0 CCS [ 4586.001978] sr 6:0:0:0: [sr0] scsi3-mmc drive: 52x/52x cd/rw xa/form2 cdda tray [ 4586.002529] sr 6:0:0:0: Attached scsi CD-ROM sr0 [ 4586.002716] sr 6:0:0:0: Attached scsi generic sg1 type 5 [ 4619.658385] ISO 9660 Extensions: Microsoft Joliet Level 3 [ 4619.691737] ISOFS: changing to secondary root [ 4691.563347] usb 3-4: USB disconnect, device number 7 [ 4693.638315] usb 3-4: new high-speed USB device number 8 using xhci_hcd [ 4693.766896] usb 3-4: New USB device found, idVendor=148f, idProduct=2878 [ 4693.766901] usb 3-4: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 4693.766903] usb 3-4: Product: Љ [ 4693.766905] usb 3-4: Manufacturer: Љ [ 4693.767338] usb-storage 3-4:1.0: USB Mass Storage device detected [ 4693.768063] scsi host7: usb-storage 3-4:1.0 [ 4694.766737] scsi 7:0:0:0: CD-ROM MediaTek Flash autorun 0.01 PQ: 0 ANSI: 0 CCS [ 4694.767423] sr 7:0:0:0: [sr0] scsi3-mmc drive: 52x/52x cd/rw xa/form2 cdda tray [ 4694.767908] sr 7:0:0:0: Attached scsi CD-ROM sr0 [ 4694.768147] sr 7:0:0:0: Attached scsi generic sg1 type 5 [ 4728.418255] ISO 9660 Extensions: Microsoft Joliet Level 3 [ 4728.427856] ISOFS: changing to secondary root [ 4733.824182] sr 7:0:0:0: [sr0] tag#0 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK [ 4733.824190] sr 7:0:0:0: [sr0] tag#0 CDB: Start/Stop Unit 1b 00 00 00 02 00 [ 4733.824218] usb 3-4: USB disconnect, device number 8 [ 4733.824281] sr 7:0:0:0: [sr0] tag#0 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK [ 4733.824291] sr 7:0:0:0: [sr0] tag#0 CDB: Prevent/Allow Medium Removal 1e 00 00 00 00 00 [ 4734.099901] usb 3-4: new high-speed USB device number 9 using xhci_hcd [ 4734.238749] usb 3-4: New USB device found, idVendor=148f, idProduct=7601 [ 4734.238754] usb 3-4: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 4734.238757] usb 3-4: Product: 802.11 n WLAN [ 4734.238772] usb 3-4: Manufacturer: MediaTek [ 4734.238775] usb 3-4: SerialNumber: 1.0 [ 4735.432096] usb 3-4: reset high-speed USB device number 9 using xhci_hcd [ 4735.562543] mt7601u 3-4:1.0: ASIC revision: 76010001 MAC revision: 76010500 [ 4735.563089] mt7601u 3-4:1.0: Firmware Version: 0.1.00 Build: 7640 Build time: 201302052146 [ 4739.011624] mt7601u 3-4:1.0: Vendor request req:07 off:09a8 failed:-110 [ 4742.131399] mt7601u 3-4:1.0: Vendor request req:02 off:09a8 failed:-110 [ 4745.251254] mt7601u 3-4:1.0: Vendor request req:07 off:0734 failed:-110 [ 4748.371056] mt7601u 3-4:1.0: Vendor request req:42 off:0230 failed:-110 [ 4751.490880] mt7601u 3-4:1.0: Vendor request req:07 off:0080 failed:-110 [ 4754.610694] mt7601u 3-4:1.0: Vendor request req:02 off:0080 failed:-110 [ 4757.730501] mt7601u 3-4:1.0: Vendor request req:02 off:0080 failed:-110 [ 4757.730548] mt7601u: probe of 3-4:1.0 failed with error -110 [ 4757.730870] usbcore: registered new
[Desktop-packages] [Bug 1877016] Re: ubuntu-wsl / wslu : needs /mnt/c/windows/system32/ in PATH env variable
Hi Sean, It will. It usually takes 2-3 weeks to complete the SRU (StableReleaseUpdates) process -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wslu in Ubuntu. https://bugs.launchpad.net/bugs/1877016 Title: ubuntu-wsl / wslu : needs /mnt/c/windows/system32/ in PATH env variable Status in wslu package in Ubuntu: Fix Released Status in wslu source package in Xenial: Confirmed Status in wslu source package in Bionic: Confirmed Status in wslu source package in Focal: Confirmed Status in wslu source package in Groovy: Fix Released Bug description: [Impact] This affects all wslu tools on all releases. When PATH do not include Windows path, the all tools will complain that reg.exe is not found. [Test Case] * Add appendWindowsPath = false under [interop] section in /etc/wsl.conf file, and restart the distribution * run any wslu tool (like wslfetch) * "/mnt/c/Windows/System32/reg.exe: Permission denied" should not be shown [Regression Potential] * For future release of wslu 3.1.0 proposed, huge refactoring will be needed. [Original Bug Report] ubuntu-wsl / wslu : needs /mnt/c/windows/system32/ in PATH env variable $ wslfetch /usr/bin/wslfetch: line 108: reg.exe: command not found /usr/bin/wslsys: line 108: reg.exe: command not found /usr/bin/wslsys: line 183: /mnt/c/Windows/System32/reg.exe: Permission denied /usr/bin/wslsys: line 185: /mnt/c/Windows/System32/reg.exe: Permission denied /usr/bin/wslsys: line 187: /mnt/c/Windows/System32/reg.exe: Permission denied /usr/bin/wslsys: line 189: /mnt/c/Windows/System32/reg.exe: Permission denied /usr/bin/wslsys: line 108: reg.exe: command not found /usr/bin/wslsys: line 183: /mnt/c/Windows/System32/reg.exe: Permission denied /usr/bin/wslsys: line 185: /mnt/c/Windows/System32/reg.exe: Permission denied /usr/bin/wslsys: line 187: /mnt/c/Windows/System32/reg.exe: Permission denied /usr/bin/wslsys: line 189: /mnt/c/Windows/System32/reg.exe: Permission denied /usr/bin/wslsys: line 108: reg.exe: command not found /usr/bin/wslsys: line 183: /mnt/c/Windows/System32/reg.exe: Permission denied /usr/bin/wslsys: line 185: /mnt/c/Windows/System32/reg.exe: Permission denied /usr/bin/wslsys: line 187: /mnt/c/Windows/System32/reg.exe: Permission denied /usr/bin/wslsys: line 189: /mnt/c/Windows/System32/reg.exe: Permission denied /usr/bin/wslsys: line 108: reg.exe: command not found /usr/bin/wslsys: line 183: /mnt/c/Windows/System32/reg.exe: Permission denied /usr/bin/wslsys: line 185: /mnt/c/Windows/System32/reg.exe: Permission denied /usr/bin/wslsys: line 187: /mnt/c/Windows/System32/reg.exe: Permission denied /usr/bin/wslsys: line 189: /mnt/c/Windows/System32/reg.exe: Permission denied /usr/bin/wslsys: line 108: reg.exe: command not found /usr/bin/wslsys: line 183: /mnt/c/Windows/System32/reg.exe: Permission denied /usr/bin/wslsys: line 185: /mnt/c/Windows/System32/reg.exe: Permission denied /usr/bin/wslsys: line 187: /mnt/c/Windows/System32/reg.exe: Permission denied /usr/bin/wslsys: line 189: /mnt/c/Windows/System32/reg.exe: Permission denied ./+o+- Windows 10 Linux Subsystem y. 'yy+ rafaeldtinoco@lenovo .;//+/h yyo BUILD: .++ .:/++/-.`sss/` BRANCH: .:++o: `\/:---:/-RELEASE:Ubuntu 20.04 LTS o:+o+:++. `'-/ooo+\ KERNEL: Linux 4.4.0-18362-Microsoft .:+o:+o/. `+sssooo+\ UPTIME: 0d 2h 6m .++/+ +oo+o:` \sssooo; /+++//+: oo+o \+/+o+++ o++o ydddhh+ .++.o+ +oo+:` /dddhhh; .+.o+oo:. odd+ \+.++o+o` -.:ohdh+ `:o+++ oyo++os: .o: .syhhh'.oo++o. /osyyy.+++\ ` +oo+++o:/ `oo++'` After : echo $PATH /snap/bin:/snap/sbin:/mnt/c/windows/system32/:/home/rafaeldtinoco/work/sources/upstream/ubuntu-dev-tools/:/usr/lib/ccache:/sbin:/bin:/usr/sbin:/usr/bin:/home/rafaeldtinoco/work/sources/bzr/ubuntu-archive-tools:/home/rafaeldtinoco/work/sources/upstream/lxd/bin:. $ wslfetch ./+o+- Windows 10 Linux Subsystem y. 'yy+ rafaeldtinoco@lenovo .;//+/h yyo BUILD:18363 .++ .:/++/-.`sss/` BRANCH: 19h1_release .:++o: `\/:---:/-RELEASE: Ubuntu 20.04 LTS o:+o+:++. `'-/ooo+\ KERNEL: Linux 4.4.0-18362-Microsoft .:+o:+o/. `+sssooo+\ UPTIME: 0d 2h 19m .++/+ +oo+o:` \sssooo; /+++//+: oo+o \+/+o+++ o++o ydddhh+ .++.o+ +oo+:` /dddhhh; .+.o+oo:. odd+ \+.++o+o` -.:ohdh+ `:o+++ oh
[Desktop-packages] [Bug 1885452] Re: pc freezes and crashes during accountsservice upgrade on fresh ubuntu focal fossa install
Actually it could still be bug 1843982 if the problem only happened up to and including the most recent accountsservice update. Meaning it shouldn't happen any more...? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1885452 Title: pc freezes and crashes during accountsservice upgrade on fresh ubuntu focal fossa install Status in gnome-session package in Ubuntu: Incomplete Bug description: After a fresh install of Focal Fossa and running sudo apt update and sudo apt upgrade, when the upgrade reaches "setting up accountsservice" the PC freezes, then crashes. This was reproducible on another computer (laptop). I reinstalled Ubuntu and put the package on hold. Later, I found that by installing and activating lightdm, this problem was remediated. Found this solution accidentally, while I was looking to correct login screen loops after I installed the nvidia drivers. This is unrelated, since the laptop does not have nvidia. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-06-29 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Package: accountsservice 0.6.55-0ubuntu12~20.04.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-39.43-generic 5.4.41 Tags: focal Uname: Linux 5.4.0-39-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-session/+bug/1885452/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1885452] Re: pc freezes and crashes during accountsservice upgrade on fresh ubuntu focal fossa install
BTW, the Nvidia automatic login issue is bug 1845801. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1885452 Title: pc freezes and crashes during accountsservice upgrade on fresh ubuntu focal fossa install Status in gnome-session package in Ubuntu: Incomplete Bug description: After a fresh install of Focal Fossa and running sudo apt update and sudo apt upgrade, when the upgrade reaches "setting up accountsservice" the PC freezes, then crashes. This was reproducible on another computer (laptop). I reinstalled Ubuntu and put the package on hold. Later, I found that by installing and activating lightdm, this problem was remediated. Found this solution accidentally, while I was looking to correct login screen loops after I installed the nvidia drivers. This is unrelated, since the laptop does not have nvidia. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-06-29 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Package: accountsservice 0.6.55-0ubuntu12~20.04.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-39.43-generic 5.4.41 Tags: focal Uname: Linux 5.4.0-39-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-session/+bug/1885452/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1885452] Re: pc freezes and crashes during accountsservice upgrade on fresh ubuntu focal fossa install
Actually it could still be 1843982 if the problem only happened up to and including the most recent accountsservice update. Meaning it shouldn't happen any more...? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1885452 Title: pc freezes and crashes during accountsservice upgrade on fresh ubuntu focal fossa install Status in gnome-session package in Ubuntu: Incomplete Bug description: After a fresh install of Focal Fossa and running sudo apt update and sudo apt upgrade, when the upgrade reaches "setting up accountsservice" the PC freezes, then crashes. This was reproducible on another computer (laptop). I reinstalled Ubuntu and put the package on hold. Later, I found that by installing and activating lightdm, this problem was remediated. Found this solution accidentally, while I was looking to correct login screen loops after I installed the nvidia drivers. This is unrelated, since the laptop does not have nvidia. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-06-29 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Package: accountsservice 0.6.55-0ubuntu12~20.04.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-39.43-generic 5.4.41 Tags: focal Uname: Linux 5.4.0-39-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-session/+bug/1885452/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1885452] Re: pc freezes and crashes during accountsservice upgrade on fresh ubuntu focal fossa install
Sounds like bug 1843982, but you seem to have that fix already. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1885452 Title: pc freezes and crashes during accountsservice upgrade on fresh ubuntu focal fossa install Status in gnome-session package in Ubuntu: Incomplete Bug description: After a fresh install of Focal Fossa and running sudo apt update and sudo apt upgrade, when the upgrade reaches "setting up accountsservice" the PC freezes, then crashes. This was reproducible on another computer (laptop). I reinstalled Ubuntu and put the package on hold. Later, I found that by installing and activating lightdm, this problem was remediated. Found this solution accidentally, while I was looking to correct login screen loops after I installed the nvidia drivers. This is unrelated, since the laptop does not have nvidia. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-06-29 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Package: accountsservice 0.6.55-0ubuntu12~20.04.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-39.43-generic 5.4.41 Tags: focal Uname: Linux 5.4.0-39-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-session/+bug/1885452/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1885941] Re: Bug on boot
** Package changed: xorg (Ubuntu) => ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1885941 Title: Bug on boot Status in Ubuntu: Incomplete Bug description: See attached detailed file. Just started reporting internal system errors on boot up. Not sure why this has started - don't think I've installed anything recently to spark it off but there was a system update recently. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3.1 ProcVersionSignature: Ubuntu 4.4.0-184.214-generic 4.4.223 Uname: Linux 4.4.0-184-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.23 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 Jul 1 18:06:26 2020 DistUpgraded: 2020-05-30 23:46:52,273 DEBUG icon theme changed, re-reading DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Mobile 4 Series Chipset Integrated Graphics Controller [1025:013c] Subsystem: Acer Incorporated [ALI] Mobile 4 Series Chipset Integrated Graphics Controller [1025:013c] InstallationDate: Installed on 2020-05-30 (31 days ago) InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 (20160217.1) MachineType: Acer Extensa 5630 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-184-generic root=UUID=7db4d8a4-7f23-45ec-99b9-fd99f55368aa ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to xenial on 2020-05-30 (31 days ago) dmi.bios.date: 12/05/2008 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: V1.25 dmi.board.name: Homa dmi.board.vendor: Acer dmi.board.version: Rev dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvrV1.25:bd12/05/2008:svnAcer:pnExtensa5630:pvr0100:rvnAcer:rnHoma:rvrRev:cvnAcer:ct10:cvrN/A: dmi.product.name: Extensa 5630 dmi.product.version: 0100 dmi.sys.vendor: Acer 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 2:1.18.4-0ubuntu0.8 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: Wed Jul 1 17:25:18 2020 xserver.configfile: default xserver.errors: /dev/dri/card0: failed to set DRM interface version 1.4: Permission denied /dev/dri/card0: failed to set DRM interface version 1.4: Permission denied xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id5460 vendor CMO xserver.version: 2:1.18.4-0ubuntu0.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1885941/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1885278] Re: Black screen after standby on Intel NUC
** Changed in: xorg-server (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1885278 Title: Black screen after standby on Intel NUC Status in xorg-server package in Ubuntu: New Bug description: I have Kubuntu 20.04 on an Intel NUC NUC7JY. When I go into standby and try to wake it up, the NUC wakes up but there is no picture only black screen. This can be reproduced every time I go into standby. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-39.43-generic 5.4.41 Uname: Linux 5.4.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: KDE Date: Fri Jun 26 15:07:18 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: Intel Corporation UHD Graphics 605 [8086:3185] (rev 03) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation UHD Graphics 605 [8086:2072] InstallationDate: Installed on 2020-06-25 (0 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 003: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 002: ID 03f0:034a HP, Inc Elite Keyboard Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Intel(R) Client Systems NUC7CJYH ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-39-generic root=UUID=30399171-99ff-4cba-8ebe-26915e7b80c9 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/18/2019 dmi.bios.vendor: Intel Corp. dmi.bios.version: JYGLKCPX.86A.0050.2019.0418.1441 dmi.board.name: NUC7JYB dmi.board.vendor: Intel Corporation dmi.board.version: J67967-404 dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnIntelCorp.:bvrJYGLKCPX.86A.0050.2019.0418.1441:bd04/18/2019:svnIntel(R)ClientSystems:pnNUC7CJYH:pvrJ67971-405:rvnIntelCorporation:rnNUC7JYB:rvrJ67967-404:cvnIntelCorporation:ct35:cvr2.0: dmi.product.family: JY dmi.product.name: NUC7CJYH dmi.product.version: J67971-405 dmi.sys.vendor: Intel(R) Client Systems version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1885278/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1882462] Re: Displays wake up pre-maturely (likely driven by notification)
Also try setting the monitor's input source (there's a button for that surely) to something other than 'Auto'. I fear Auto might be doing some active scanning and wake itself up when it comes back to the connector that you're using but wish to keep off. -- 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/1882462 Title: Displays wake up pre-maturely (likely driven by notification) Status in Mutter: Unknown Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: After a period of time, my displays go to sleep as they should. However, I often come back to find that the displays are awake, the mouse pointer is on a screen, but the screens are otherwise black. They're in this weird "awake but not fully on" mode. At that point, they will not go back to sleep as they should unless I fully awake them and let them go back to sleep. I don't know exactly what triggers the "half awake" but I suspect it's a notification. The displays shouldn't turn on without a user action. It wastes power and is clearly broken. I've attached a photo for an example. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.2-1ubuntu1~20.04.1 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jun 7 16:10:20 2020 DisplayManager: gdm3 InstallationDate: Installed on 2018-07-24 (684 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180724) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1~20.04.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-01-07 (152 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1882462/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1882462] Re: Displays wake up pre-maturely (likely driven by notification)
I've set this bug to track: https://gitlab.gnome.org/GNOME/mutter/-/issues/877 but there's also: https://gitlab.gnome.org/GNOME/mutter/-/issues/976 and maybe also see: https://gitlab.gnome.org/GNOME/mutter/-/issues/915 Although I think we should be careful to keep this bug about a single issue. ** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #877 https://gitlab.gnome.org/GNOME/mutter/-/issues/877 ** Also affects: mutter via https://gitlab.gnome.org/GNOME/mutter/-/issues/877 Importance: Unknown Status: Unknown ** Also affects: mutter (Ubuntu) Importance: Undecided Status: New ** Changed in: mutter (Ubuntu) Status: New => Confirmed ** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #976 https://gitlab.gnome.org/GNOME/mutter/-/issues/976 ** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #915 https://gitlab.gnome.org/GNOME/mutter/-/issues/915 -- 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/1882462 Title: Displays wake up pre-maturely (likely driven by notification) Status in Mutter: Unknown Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: After a period of time, my displays go to sleep as they should. However, I often come back to find that the displays are awake, the mouse pointer is on a screen, but the screens are otherwise black. They're in this weird "awake but not fully on" mode. At that point, they will not go back to sleep as they should unless I fully awake them and let them go back to sleep. I don't know exactly what triggers the "half awake" but I suspect it's a notification. The displays shouldn't turn on without a user action. It wastes power and is clearly broken. I've attached a photo for an example. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.2-1ubuntu1~20.04.1 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jun 7 16:10:20 2020 DisplayManager: gdm3 InstallationDate: Installed on 2018-07-24 (684 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180724) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1~20.04.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-01-07 (152 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1882462/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1738774]
Just for your information. As an icon designer and mauntainer now all icon themes have SVG versions. So I would say its safe if in some point we reach perfect SVG support, than the PNG version can be removed or moved to the extension sites. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1738774 Title: Pixeled icons with LibreOffice 5.1.6.2 on HiDPI/4K display Status in LibreOffice: Confirmed Status in libreoffice package in Ubuntu: Confirmed Bug description: LibreOffice 5.1.6.2 shipped with Ubuntu 16.04.3 LTS shows pixeled icons on a HiDPI/4K monitor like used in the Dell XPS 13 9360. To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1738774/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1885278] Re: Black screen after standby on Intel NUC
s. the attached file ** Attachment added: "prevboot.txt" https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1885278/+attachment/5388812/+files/prevboot.txt -- 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/1885278 Title: Black screen after standby on Intel NUC Status in xorg-server package in Ubuntu: Incomplete Bug description: I have Kubuntu 20.04 on an Intel NUC NUC7JY. When I go into standby and try to wake it up, the NUC wakes up but there is no picture only black screen. This can be reproduced every time I go into standby. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-39.43-generic 5.4.41 Uname: Linux 5.4.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: KDE Date: Fri Jun 26 15:07:18 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: Intel Corporation UHD Graphics 605 [8086:3185] (rev 03) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation UHD Graphics 605 [8086:2072] InstallationDate: Installed on 2020-06-25 (0 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 003: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 002: ID 03f0:034a HP, Inc Elite Keyboard Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Intel(R) Client Systems NUC7CJYH ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-39-generic root=UUID=30399171-99ff-4cba-8ebe-26915e7b80c9 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/18/2019 dmi.bios.vendor: Intel Corp. dmi.bios.version: JYGLKCPX.86A.0050.2019.0418.1441 dmi.board.name: NUC7JYB dmi.board.vendor: Intel Corporation dmi.board.version: J67967-404 dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnIntelCorp.:bvrJYGLKCPX.86A.0050.2019.0418.1441:bd04/18/2019:svnIntel(R)ClientSystems:pnNUC7CJYH:pvrJ67971-405:rvnIntelCorporation:rnNUC7JYB:rvrJ67967-404:cvnIntelCorporation:ct35:cvr2.0: dmi.product.family: JY dmi.product.name: NUC7CJYH dmi.product.version: J67971-405 dmi.sys.vendor: Intel(R) Client Systems version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1885278/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1625324] Re: prints pdf files very faintly on EPSON WF-7620. All other types of files print normally
Thank you for taking the time to report this bug and trying to help make Ubuntu better. However, it seems that you are not using a software package provided by the official Ubuntu repositories. Because of this the Ubuntu project can not support or fix your particular bug. Please report this bug to the provider of the software package. Thanks! If you are interested in learning more about software repositories and Ubuntu, check https://help.ubuntu.com/community/Repositories. ** Package changed: evince (Ubuntu) => cups (Ubuntu) ** Changed in: cups (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1625324 Title: prints pdf files very faintly on EPSON WF-7620. All other types of files print normally Status in cups package in Ubuntu: Incomplete Bug description: Printer is installed as a network printer. Windows does not print pdf files faintly. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: evince 3.18.2-1ubuntu4 ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16 Uname: Linux 4.4.0-36-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity Date: Mon Sep 19 15:06:37 2016 InstallationDate: Installed on 2016-08-09 (41 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: evince UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1625324/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1619901] Re: links to local files are always processed as relative paths
could you give some details on how you create the pdf and paths references? is that still an issue in recent versions? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1619901 Title: links to local files are always processed as relative paths Status in evince package in Ubuntu: Incomplete Bug description: When I create a pdf with a link to an absolute path (e.g. /home/me/link.pdf) and open it in evince it tries to read it as relative to the path of the opened pdf, e.g. if I open /home/me/doc.pdf and click on the preceding link evince tries to open /home/me/home/me/link.pdf. It should open /home/me/link.pdf, otherwise the user is unable to link to files outside the local directory Ubuntu 16.04.1 Evince 3.18.2-1ubuntu4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1619901/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1617995] Re: Evince says "The document contains no pages" while viewing pdf file
** Changed in: evince (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1617995 Title: Evince says "The document contains no pages" while viewing pdf file Status in evince package in Ubuntu: Confirmed Bug description: Evince says "The document contains no pages" while viewing pdf file Please see file attached. Ver. Evince 3.18.2 on Ubuntu 16.04 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1617995/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1625324] Re: prints pdf files very faintly on EPSON WF-7620. All other types of files print normally
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 look at all reported bugs in a timely manner. There have been many changes in Ubuntu since that time you reported the bug and your problem may have been fixed with some of the updates. It would help us a lot if you could test it on a currently supported Ubuntu version. When you test it and it is still an issue, kindly upload the updated logs by running only once: apport-collect 1625324 and any other logs that are relevant for this particular issue. ** Changed in: cups (Ubuntu) Importance: Undecided => Low ** Changed in: cups (Ubuntu) Status: Invalid => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1625324 Title: prints pdf files very faintly on EPSON WF-7620. All other types of files print normally Status in cups package in Ubuntu: Incomplete Bug description: Printer is installed as a network printer. Windows does not print pdf files faintly. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: evince 3.18.2-1ubuntu4 ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16 Uname: Linux 4.4.0-36-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity Date: Mon Sep 19 15:06:37 2016 InstallationDate: Installed on 2016-08-09 (41 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: evince UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1625324/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1619901] Re: links to local files are always processed as relative paths
Thank you for taking the time to report this bug and help make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read 'How to report bugs effectively' http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem. We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures. At a minimum, we need: 1. The specific steps or actions you took that caused you to encounter the problem. 2. The behavior you expected. 3. The behavior you actually encountered (in as much detail as possible). Thanks! ** Changed in: evince (Ubuntu) Importance: Undecided => Low ** Changed in: evince (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1619901 Title: links to local files are always processed as relative paths Status in evince package in Ubuntu: Incomplete Bug description: When I create a pdf with a link to an absolute path (e.g. /home/me/link.pdf) and open it in evince it tries to read it as relative to the path of the opened pdf, e.g. if I open /home/me/doc.pdf and click on the preceding link evince tries to open /home/me/home/me/link.pdf. It should open /home/me/link.pdf, otherwise the user is unable to link to files outside the local directory Ubuntu 16.04.1 Evince 3.18.2-1ubuntu4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1619901/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1629633] Re: evince displays blank thumbnails for some pages
** Changed in: evince (Ubuntu) Status: Confirmed => Triaged ** Bug watch added: gitlab.gnome.org/GNOME/evince/-/issues #525 https://gitlab.gnome.org/GNOME/evince/-/issues/525 ** Changed in: evince Importance: Medium => Unknown ** Changed in: evince Status: Expired => Unknown ** Changed in: evince Remote watch: GNOME Bug Tracker #740331 => gitlab.gnome.org/GNOME/evince/-/issues #525 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1629633 Title: evince displays blank thumbnails for some pages Status in Evince: Unknown Status in evince package in Ubuntu: Triaged Bug description: Hi, To reproduce this bug: - load the attached PS file into evince - if thumbnails are not displayed then press F9 and choose to display thumbnails - evince displayd a blank thumbnail for pages 6 and 7 ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: evince 3.22.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-19.21-lowlatency 4.8.0-rc8 Uname: Linux 4.8.0-19-lowlatency x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CurrentDesktop: KDE Date: Sun Oct 2 10:10:28 2016 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: evince UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/evince/+bug/1629633/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1650076] Re: Evince scrolls even when unfocused after image/text is selected
The upstream report https://gitlab.gnome.org/GNOME/evince/-/issues/747 indicates that the issue is now fixed in recent versions ** Bug watch added: gitlab.gnome.org/GNOME/evince/-/issues #747 https://gitlab.gnome.org/GNOME/evince/-/issues/747 ** Changed in: evince (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1650076 Title: Evince scrolls even when unfocused after image/text is selected Status in Evince: Expired Status in evince package in Ubuntu: Fix Released Bug description: When an image or portion of text in a pdf is clicked in Evince, dragged (as if to drag it to another application), then let go of, Evince will continue to scroll depending on where the pointer is placed, even if the window or workspace is changed. The user's place is quickly lost. To reproduce: 1.) Open a pdf with Evince. 2.) Left click on an image or page of a if it is an image, or select some text. 3.) With the left mouse button held down, drag it so that the "hand holding a document" icon appears. 4.) Let go of the left mouse button. 5.) Go to another window or desktop, and note that depending on the location of the mouse on the screen Evince, even unfocused, will scroll the pdf in that direction (e.g. up if the mouse is near the top). The only way to stop Evince from scrolling is to go back to Evince and click or scroll again. I've tested this on with Evince 3.18.2 on Ubuntu 16.04. This did not occur back in 14.04. (Edited to include easier method of reproduction.) To manage notifications about this bug go to: https://bugs.launchpad.net/evince/+bug/1650076/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1640674] Re: Some fonts are corrupted
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 look at all reported bugs in a timely manner. There have been many changes in Ubuntu since that time you reported the bug and your problem may have been fixed with some of the updates. It would help us a lot if you could test it on a currently supported Ubuntu version. When you test it and it is still an issue, kindly upload the updated logs by running only once: apport-collect 1640674 and any other logs that are relevant for this particular issue. ** Changed in: evince (Ubuntu) Importance: Undecided => Low ** Changed in: evince (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1640674 Title: Some fonts are corrupted Status in evince package in Ubuntu: Incomplete Bug description: Hello Some of cyrillic fonts is corrupted, some isn't. The same issue is in xpdf. It's ok in mupdf 2435491_10-11-2016.pdf - example file ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: evince 3.18.2-1ubuntu4 ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21 Uname: Linux 4.4.0-45-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity Date: Wed Nov 9 20:19:32 2016 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 2016-10-06 (34 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 KernLog: SourcePackage: evince UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1640674/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1661760] Re: Evince does not print pdf.
Thank you for taking the time to report this bug and help make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read 'How to report bugs effectively' http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem. We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures. At a minimum, we need: 1. The specific steps or actions you took that caused you to encounter the problem. 2. The behavior you expected. 3. The behavior you actually encountered (in as much detail as possible). Thanks! ** Changed in: evince (Ubuntu) Importance: Undecided => Low ** Changed in: evince (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1661760 Title: Evince does not print pdf. Status in evince package in Ubuntu: Incomplete Bug description: The print job is sent but is stopped shortly. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: evince (not installed) ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40 Uname: Linux 4.4.0-62-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: XFCE Date: Fri Feb 3 20:19:29 2017 InstallationDate: Installed on 2017-02-03 (0 days ago) InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: evince UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1661760/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1690341] Re: evince does not change timestamp of pdf forms
Thank you for your bug report. Is that still an issue in newer versions? If so could you report it upstream on https://gitlab.gnome.org/GNOME/evince/-/issues ? ** Changed in: evince (Ubuntu) Importance: Undecided => Low ** Changed in: evince (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1690341 Title: evince does not change timestamp of pdf forms Status in evince package in Ubuntu: Incomplete Bug description: After filling in a pdf-form and "Save a copy ..." the mtime of the filled in form is the same as that of the original form. Observed with: evince 3.10.3 on 14.04 LTS evince 3.18.2 on 16.04 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1690341/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1675397] Re: ctrl-f cannot find wrapped text in columns
** Changed in: evince (Ubuntu) Importance: Medium => Low -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1675397 Title: ctrl-f cannot find wrapped text in columns Status in evince package in Ubuntu: Confirmed Bug description: Please use this document to reproduce the issue: https://docs.bmc.com/docs/download/attachments/677783897/CTM_Admin_9.0.00.400_488755.pdf With Ctrl+F, you can find the term HYPHEN in CTM_VARIABLE_ALLOW_HYPHEN on page 155, but you cannot find the term ALLOW. Adobe Reader can (see attachment "find.png"), and I also expect Evince to find the term, even if the text is wrapped because the column is too small. In Evince there seems to be a newline character at the position where it should just wrap the column text. Copy&Paste of the row will result in the same behaviour: CTM_VARIABLE_ALLO W_HYPHEN Enables user-defined variables to contain the - (hyphen) character. Valid values: N, Y Default: N Refresh Type: Manual NOTE: If a job has an variable that includes a hyphen in the variable name, it will fail when submitted to an agent that is running on UNIX. Again, Adobe Reader does not split CTM_VARIABLE_ALLOW_HYPHEN on two lines: CTM_VARIABLE_ALLOW_HYPHEN Enables user-defined variables to contain the - (hyphen) character. Valid values: N, Y Default: N Refresh Type: Manual NOTE: If a job has an variable that includes a hyphen in the variable name, it will fail when submitted to an agent that is running on UNIX. $ lsb_release -rd Description: Ubuntu 16.04.2 LTS Release: 16.04 $ apt-cache policy evince evince: Installed: 3.18.2-1ubuntu4 Candidate: 3.18.2-1ubuntu4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1675397/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1664392] Re: Drawing failure with large MediaBox
** Changed in: evince (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1664392 Title: Drawing failure with large MediaBox Status in evince package in Ubuntu: Invalid Bug description: If a document contains pages with large differences in page size (/MediaBox field), drawing failure occurs. Attached is an example with two empty pages, the first one has dimensions 10x10 and the second one has dimensions 10x10. Upon opening with Evince, the window does not display properly and the following appears on stderr (you may need to zoom in to trigger this bug). (evince:14359): Gtk-WARNING **: drawing failure for widget `EvView': invalid matrix (not invertible) (evince:14359): Gtk-WARNING **: drawing failure for widget `GtkScrolledWindow': invalid matrix (not invertible) (evince:14359): Gtk-WARNING **: drawing failure for widget `GtkOverlay': invalid matrix (not invertible) (evince:14359): Gtk-WARNING **: drawing failure for widget `GtkBox': invalid matrix (not invertible) (evince:14359): Gtk-WARNING **: drawing failure for widget `GtkPaned': invalid matrix (not invertible) (evince:14359): Gtk-WARNING **: drawing failure for widget `GtkBox': invalid matrix (not invertible) (evince:14359): Gtk-WARNING **: drawing failure for widget `EvWindow': invalid matrix (not invertible) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1664392/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1690939] Re: evince crashes with segmentation fault when $DISPLAY is set
Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps: 1. Look in /var/crash for crash files and if found run: ubuntu-bug YOURFILE.crash Then tell us the ID of the newly-created bug. 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. 3. If step 2 also failed then apply the workaround from bug 994921, reboot, reproduce the crash, and retry step 1. Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself. ** Changed in: evince (Ubuntu) Importance: Undecided => Low ** Changed in: evince (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1690939 Title: evince crashes with segmentation fault when $DISPLAY is set Status in evince package in Ubuntu: Invalid Bug description: I ssh into another computer with X11-forwarding and compression to run some programs. My $DISPLAY is automatically set to "localhost:10.0" or the like and I can successfully run xterm and xeyes and all those programs. When I try to run evince, I get "Segmentation fault (core dumped)". No core file is generated when this happens. When I am logged into the same system locally, I have no problem with evince -- only when ssh'ed in remotely. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1690939/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1710319] Re: package evince-common 3.18.2-1ubuntu4.1 failed to install/upgrade: package evince-common is not ready for configuration cannot configure (current status 'half-inst
Thank you for your bug report, it does sound like a local issue during the installation than a package bug though ** Changed in: evince (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1710319 Title: package evince-common 3.18.2-1ubuntu4.1 failed to install/upgrade: package evince-common is not ready for configuration cannot configure (current status 'half-installed') Status in evince package in Ubuntu: Invalid Bug description: This is in Ubuntu 16.04 LTS on my 64bit Intel Celeron CPU 900 @ 2.2GHz. Not sure what the deal is actually since the update status shows up to date. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: evince-common 3.18.2-1ubuntu4.1 ProcVersionSignature: Ubuntu 4.4.0-91.114-generic 4.4.76 Uname: Linux 4.4.0-91-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 Date: Fri Aug 11 21:31:05 2017 DpkgHistoryLog: Start-Date: 2017-08-11 21:30:43 Requested-By: lucastoshi (1000) Upgrade: update-manager-core:amd64 (1:16.04.7, 1:16.04.8), update-manager:amd64 (1:16.04.7, 1:16.04.8), python3-update-manager:amd64 (1:16.04.7, 1:16.04.8) DuplicateSignature: package:evince-common:3.18.2-1ubuntu4.1 Processing triggers for bamfdaemon (0.5.3~bzr0+16.04.20160824-0ubuntu1) ... Rebuilding /usr/share/applications/bamf-2.index... dpkg: error processing package evince-common (--configure): package evince-common is not ready for configuration ErrorMessage: package evince-common is not ready for configuration cannot configure (current status 'half-installed') InstallationDate: Installed on 2016-12-10 (244 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) PackageArchitecture: all ProcCmdline: BOOT_IMAGE=/vmlinuz-4.4.0-91-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: evince Title: package evince-common 3.18.2-1ubuntu4.1 failed to install/upgrade: package evince-common is not ready for configuration cannot configure (current status 'half-installed') UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1710319/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1704558] Re: package evince-common 3.18.2-1ubuntu4.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configur
Thank you for your bug report, it does sound like a local issue during the installation than a package bug though ** Changed in: evince (Ubuntu) Importance: Undecided => Low ** Changed in: evince (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1704558 Title: package evince-common 3.18.2-1ubuntu4.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in evince package in Ubuntu: Invalid Bug description: I'm not sure what's wrong with my computer. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: evince-common 3.18.2-1ubuntu4.1 ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70 Uname: Linux 4.4.0-83-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 Date: Sat Jul 15 09:55:42 2017 DuplicateSignature: package:evince-common:3.18.2-1ubuntu4.1 Setting up libevview3-3:amd64 (3.18.2-1ubuntu4.1) ... dpkg: error processing package evince-common (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2016-11-05 (251 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) PackageArchitecture: all ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-83-generic.efi.signed root=UUID=681dd408-e5f7-4fe5-a53e-b26cce065387 ro quiet splash vt.handoff=7 SourcePackage: evince Title: package evince-common 3.18.2-1ubuntu4.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1704558/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1727518] Re: Presentation mode broken with HighDPI and 200% scale
** Changed in: evince (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1727518 Title: Presentation mode broken with HighDPI and 200% scale Status in Evince: Expired Status in evince package in Ubuntu: Fix Released Bug description: When using a presentation mode with a HighDPI screen and 200% scaling the slides are rendered only partially and a large part is clipped. Probably this upstream bug: https://bugzilla.redhat.com/show_bug.cgi?id=1369216 ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: evince 3.26.0-1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Oct 25 22:33:18 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2017-10-19 (5 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: evince UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/evince/+bug/1727518/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1702081] Re: /usr/bin/evince-thumbnailer:11:__memmove_avx_unaligned:memmove:pk_load_font:load_font_file:font_reference
There has been no report since 18.10, closing ** Changed in: evince (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1702081 Title: /usr/bin/evince- thumbnailer:11:__memmove_avx_unaligned:memmove:pk_load_font:load_font_file:font_reference Status in evince package in Ubuntu: Fix Released Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding evince. This problem was most recently seen with package version 3.18.2-1ubuntu4+elementary2~ubuntu0.4.1, the problem page at https://errors.ubuntu.com/problem/35941fdc002cd10a3558ad080a065b2aa541845c contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1702081/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1726055] Re: Feature request: keyboard shortcut for "Add Bookmark" menu action
The issue has been fixed in newer versions, https://gitlab.gnome.org/GNOME/evince/-/issues/1321 ** Bug watch added: gitlab.gnome.org/GNOME/evince/-/issues #1321 https://gitlab.gnome.org/GNOME/evince/-/issues/1321 ** Changed in: evince (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1726055 Title: Feature request: keyboard shortcut for "Add Bookmark" menu action Status in evince package in Ubuntu: Fix Released Bug description: Nothing to add to the summary. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1726055/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1723869] Re: evince crashed with SIGSEGV in _create_touch_event()
The issue is fixed in newer GNOME versions according to the upstream report ** Changed in: evince (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1723869 Title: evince crashed with SIGSEGV in _create_touch_event() Status in evince package in Ubuntu: Fix Released Bug description: Evince seems to crash periodically for no apparent reason. ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: evince 3.26.0-1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Oct 8 22:21:48 2017 EcryptfsInUse: Yes ExecutablePath: /usr/bin/evince InstallationDate: Installed on 2017-09-16 (29 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic.efi.signed root=UUID=b7c25b8a-4364-450d-9e58-6bf3b66eab2d ro quiet splash vt.handoff=7 ProcEnviron: SHELL=/usr/bin/zsh XDG_RUNTIME_DIR= PATH=(custom, no user) LANGUAGE=en_GB:en LANG=en_GB.UTF-8 SegvAnalysis: Segfault happened at: 0x7ff61faf5e40:mov0x18(%rbp),%rdi PC (0x7ff61faf5e40) ok source "0x18(%rbp)" (0x0018) not located in a known VMA region (needed readable region)! destination "%rdi" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: evince StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6 ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libwayland-client.so.0 Title: evince crashed with SIGSEGV in ffi_call_unix64() UpgradeStatus: Upgraded to artful on 2017-10-05 (10 days ago) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1723869/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1885452] Re: pc freezes and crashes during accountsservice upgrade on fresh ubuntu focal fossa install
As I mentioned, I think the problem is not related to nvidia drivers. If I install nvidia drivers I have to do it by first disabling automatic log in at startup, otherwise I get a login loop after first reboot. If I disable automatic log in, then I do not get any crash when upgrading accountsservice. To sum up, accountsservice upgrade crashes only on 'GDM + login automatically'. On 'LightDM + login automatically', it stalls a bit but does not crash, while on 'GDM + disabled automatic login' it works perfectly. I installed ubuntu on an older laptop with no nvidia cards and the same problem appeared, otherwise I would not have reported this issue as it would have probably been related to a particular configuration, of my PC. Please let me know if you think I can try something else. Thanks! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1885452 Title: pc freezes and crashes during accountsservice upgrade on fresh ubuntu focal fossa install Status in gnome-session package in Ubuntu: Incomplete Bug description: After a fresh install of Focal Fossa and running sudo apt update and sudo apt upgrade, when the upgrade reaches "setting up accountsservice" the PC freezes, then crashes. This was reproducible on another computer (laptop). I reinstalled Ubuntu and put the package on hold. Later, I found that by installing and activating lightdm, this problem was remediated. Found this solution accidentally, while I was looking to correct login screen loops after I installed the nvidia drivers. This is unrelated, since the laptop does not have nvidia. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-06-29 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Package: accountsservice 0.6.55-0ubuntu12~20.04.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-39.43-generic 5.4.41 Tags: focal Uname: Linux 5.4.0-39-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-session/+bug/1885452/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1736012] Re: package evince-common 3.18.2-1ubuntu4 failed to install/upgrade: el paquete evince-common no está listo para configurarse no se puede configurar (estado actual `h
thank you for your bug report, that does sound like a local corruption rather than a package bug though ** Changed in: evince (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1736012 Title: package evince-common 3.18.2-1ubuntu4 failed to install/upgrade: el paquete evince-common no está listo para configurarse no se puede configurar (estado actual `half-installed') Status in evince package in Ubuntu: Invalid Bug description: ocurre esta error al prender el computador ProblemType: Package DistroRelease: Ubuntu 16.04 Package: evince-common 3.18.2-1ubuntu4 ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11 Uname: Linux 4.8.0-36-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.13 Architecture: amd64 Date: Sat Dec 2 14:45:21 2017 DpkgHistoryLog: Start-Date: 2017-12-02 14:45:00 Commandline: apt-get install gimp Requested-By: juanmarcon (1000) Install: liblapack3:amd64 (3.6.0-2ubuntu2, automatic), libgegl-0.3-0:amd64 (0.3.4-1ubuntu2, automatic), libraw15:amd64 (0.17.1-1ubuntu0.1, automatic), libumfpack5.7.1:amd64 (1:4.4.6-1, automatic), libcamd2.4.1:amd64 (1:4.4.6-1, automatic), libccolamd2.9.1:amd64 (1:4.4.6-1, automatic), gimp-data:amd64 (2.8.16-1ubuntu1.1, automatic), python-cairo:amd64 (1.8.8-2, automatic), gimp:amd64 (2.8.16-1ubuntu1.1), libblas-common:amd64 (3.6.0-2ubuntu2, automatic), libbabl-0.1-0:amd64 (0.1.16-1, automatic), libgfortran3:amd64 (5.4.0-6ubuntu1~16.04.5, automatic), libamd2.4.1:amd64 (1:4.4.6-1, automatic), libsdl1.2debian:amd64 (1.2.15+dfsg1-3, automatic), python-gtk2:amd64 (2.24.0-4ubuntu1, automatic), libgimp2.0:amd64 (2.8.16-1ubuntu1.1, automatic), libblas3:amd64 (3.6.0-2ubuntu2, automatic), python-gobject-2:amd64 (2.28.6-12ubuntu1, automatic), libcholmod3.0.6:amd64 (1:4.4.6-1, automatic) ErrorMessage: el paquete evince-common no está listo para configurarse no se puede configurar (estado actual `half-installed') InstallationDate: Installed on 2017-11-22 (10 days ago) InstallationMedia: Xubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215) PackageArchitecture: all ProcCmdline: BOOT_IMAGE=/vmlinuz-4.8.0-36-generic root=UUID=d4cd7dcc-09f3-453d-95f3-95d9e6bf686f ro quiet splash vt.handoff=7 SourcePackage: evince Title: package evince-common 3.18.2-1ubuntu4 failed to install/upgrade: el paquete evince-common no está listo para configurarse no se puede configurar (estado actual `half-installed') UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1736012/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1729972] Re: /usr/bin/evince:11:g_dbus_proxy_call_internal:g_dbus_proxy_call:ev_media_player_keys_grab_keys:g_task_return_now:g_task_return
There has been no report since 18.10, closing ** Changed in: evince (Ubuntu) Importance: Undecided => Low ** Changed in: evince (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1729972 Title: /usr/bin/evince:11:g_dbus_proxy_call_internal:g_dbus_proxy_call:ev_media_player_keys_grab_keys:g_task_return_now:g_task_return Status in evince package in Ubuntu: Fix Released Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding evince. This problem was most recently seen with package version 3.26.0-1, the problem page at https://errors.ubuntu.com/problem/78386c52a123710120148985cf2cb23848b24228 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1729972/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1732038] Re: evince spams stderr with messages about "Allocating size to EvWindow"
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 look at all reported bugs in a timely manner. There have been many changes in Ubuntu since that time you reported the bug and your problem may have been fixed with some of the updates. It would help us a lot if you could test it on a currently supported Ubuntu version. When you test it and it is still an issue, kindly upload the updated logs by running only once: apport-collect 1732038 and any other logs that are relevant for this particular issue. ** Changed in: evince (Ubuntu) Importance: Undecided => Low ** Changed in: evince (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1732038 Title: evince spams stderr with messages about "Allocating size to EvWindow" Status in evince package in Ubuntu: Incomplete Bug description: Open a PDF and search it, for instance for the letter 'e'. evince prints numerous error messages to stderr of the form: (evince:30830): Gtk-WARNING **: Allocating size to EvWindow 0x559a7c972f10 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? The more common the search term, the more errors. There is also always one similar error about EvSidebar every time evince starts. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: evince 3.26.0-1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Nov 14 09:54:55 2017 InstallationDate: Installed on 2016-12-02 (345 days ago) InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Release amd64 (20161012.1) KernLog: SourcePackage: evince UpgradeStatus: Upgraded to artful on 2017-10-12 (32 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1732038/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1743043] Re: Evince sometimes fails to open under Wayland (Protocol error)
Thank you for your bug report, is that still an issue in newer ubuntu versions? ** Changed in: evince (Ubuntu) Status: Triaged => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1743043 Title: Evince sometimes fails to open under Wayland (Protocol error) Status in evince package in Ubuntu: Incomplete Bug description: Under Ubuntu 17.10 I find that Evince (3.26.0-1) often fails to open when I'm logged on using Wayland. There's no problem using X. The error is very simple. I double click a PDF file in my file manager and expect it to open in Evince (Document Viewer). And mostly that's what happens, but after having opened a few files, it just stops working for some files. The error seldom occurs with the first PDF file I open after a reboot, but after I've opened a few files, the error pops up, but only for some files. Some files I can click and they open in Evince each time, whereas other files will never open in Evince. They open fine in other applications and under X. When I try to open the file from the command line, I get the following error message: pinnerup@ergi:~$ evince Dropbox/Litteratur/Sprog/Græsk/Beekes\ \&\ van\ Beek\ –\ Etymological\ Dictionary\ of\ Greek.pdf Gdk-Message: Error 71 (Protocol error) dispatching to Wayland display. If I rename the file (e.g. by adding the number "2" to the file name), make a copy or move it to another directory, it opens without problems. However, after some time the renamed or new file will fail to open with the same error. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1743043/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1733793] Re: Evince reports wrong zoom percentage number on Wayland
no response, closing ** Changed in: evince (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1733793 Title: Evince reports wrong zoom percentage number on Wayland Status in evince package in Ubuntu: Invalid Bug description: The application struggles on zooming at any zoom levels if I'm running it on Wayland. Basically Evince fails at zooming correctly on all PDF documents. Whenever the zoom is set to Fit Page, Fit Width, or Automatic, the counter displays wrong percentage at 0% and Ctrl + +/- or Ctrl + Scroll Up/Down doesn't work. If I try to zoom to 50% or 200% using the presets on the drop-down menu, all pages in the document disappears and the counter now shows "-nan%". Encountered on Ubuntu 17.10 in Wayland GPU is Radeon HD 6410 and uses open-source drivers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1733793/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1736583] Re: Evince annotations lost on save
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 look at all reported bugs in a timely manner. There have been many changes in Ubuntu since that time you reported the bug and your problem may have been fixed with some of the updates. It would help us a lot if you could test it on a currently supported Ubuntu version. When you test it and it is still an issue, kindly upload the updated logs by running only once: apport-collect 1736583 and any other logs that are relevant for this particular issue. ** Changed in: evince (Ubuntu) Importance: Undecided => High ** Changed in: evince (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1736583 Title: Evince annotations lost on save Status in evince package in Ubuntu: Incomplete Bug description: I used Evince to annotate a ~70 page PDF. Over a few hours I added a handful of annotations to each page. After every 5th page or so I would "Save a Copy" in a new file name (same filename on every save). When I finished editing the document I saved and noticed that the modified time was not updating on the file. When opening the copy, no annotations were present. I tried saving as different file names and the same thing occurred. Then, stupidly, I opened the original file and it closed the file I had open with the hundreds of annotations and now no files have the annotations. My computer is currently at this state. I would really like to be able to recover the annotations if they happen to be in a cache file somewhere. Secondly, this seems to be a bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1736583/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1743703] Re: When I highlight text, after highlighting button, that enable highlighting become unpressed. And if I wont to highlight some text agan I need to press button agen
Thank you for your bug report, that sounds like https://gitlab.gnome.org/GNOME/evince/-/issues/862 ** Bug watch added: gitlab.gnome.org/GNOME/evince/-/issues #862 https://gitlab.gnome.org/GNOME/evince/-/issues/862 ** Changed in: evince (Ubuntu) Importance: Undecided => Low ** Changed in: evince (Ubuntu) Status: New => Triaged ** Also affects: evince via https://gitlab.gnome.org/GNOME/evince/-/issues/862 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1743703 Title: When I highlight text, after highlighting button, that enable highlighting become unpressed. And if I wont to highlight some text agan I need to press button agen. I do knot now if it is a bug, but I know that it is not useful. Status in Evince: Unknown Status in evince package in Ubuntu: Triaged Bug description: When I highlight text, after highlighting button, that enable highlighting become unpressed. And if I wont to highlight some text agan I need to press button (button change cousor mode from selecting to highlighting) agen. I do not now if it is a bug, but I know that it is not useful. To manage notifications about this bug go to: https://bugs.launchpad.net/evince/+bug/1743703/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1743288] Re: I can't install programms from Ububtu Software...package evince-common 3.18.2-1ubuntu4.3 failed to install/upgrade: package is in a very bad inconsistent state; yo
Thank you for your bug report, it does sound like a local corruption rather than a bug though ** Changed in: evince (Ubuntu) Importance: Undecided => Low ** Changed in: evince (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1743288 Title: I can't install programms from Ububtu Software...package evince- common 3.18.2-1ubuntu4.3 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in evince package in Ubuntu: Invalid Bug description: I can't install programms from Ububtu Software GUI ProblemType: Package DistroRelease: Ubuntu 16.04 Package: evince-common 3.18.2-1ubuntu4.3 ProcVersionSignature: Ubuntu 4.13.0-26.29~16.04.2-generic 4.13.13 Uname: Linux 4.13.0-26-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.15 AptOrdering: firefox: Install evince-common: Configure firefox: Configure NULL: ConfigurePending Architecture: amd64 Date: Sat Jan 6 16:08:44 2018 DpkgHistoryLog: Start-Date: 2018-01-06 16:08:07 Commandline: aptdaemon role='role-upgrade-packages' sender=':1.80' Upgrade: firefox:amd64 (57.0.3+build1-0ubuntu0.16.04.1, 57.0.4+build1-0ubuntu0.16.04.1) DuplicateSignature: package:evince-common:3.18.2-1ubuntu4.3 Processing triggers for man-db (2.7.5-1) ... dpkg: error processing package evince-common (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2017-11-14 (61 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) PackageArchitecture: all ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.13.0-26-generic.efi.signed root=UUID=d40e139c-b024-4be2-9047-4b1024f60ff8 ro quiet splash vt.handoff=7 SourcePackage: evince Title: package evince-common 3.18.2-1ubuntu4.3 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1743288/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1749440] Re: Unable to send mail via Gnome-Gmail
thank you for your bug report, it does sound rather an issue with gnome gmail though ** Package changed: evince (Ubuntu) => gnome-gmail (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1749440 Title: Unable to send mail via Gnome-Gmail Status in gnome-gmail package in Ubuntu: Confirmed Bug description: I have set GNOME-Gmail as my default e-mail application in Ubuntu 17.10. Now when I run Evince and select "Send to" (German "Senden an") nothing happens. I started Evince in a terminal which gave me the following error code: "/usr/bin/gnome-gmail: 3: exec: /usr/share/gnome-gmail/gnomegmail.py: Permission denied" Can anyone confirm this? Work-around or fix much appreciated! Thx To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-gmail/+bug/1749440/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1743244] Re: Keyboard autorepeat does not work after latest update
it doesn't sound like a problem with the evince pdf viewer though, reassigning -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1743244 Title: Keyboard autorepeat does not work after latest update Status in evince package in Ubuntu: Incomplete Bug description: After latest update, keyboard autorepeat has stopped working. I can confirm that the problem is related to the peaq-wmi module having been recently whitelisted as using modprobe to remove peaq-wmi fixes the problem. Workaround: Blacklist the peaq-wmi module I really think the peaq-wmi module should be re-blacklised by default until the bugs can be worked out. Running Xubuntu, version 16.04.3 LTS ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: evince 3.18.2-1ubuntu4.3 ProcVersionSignature: Ubuntu 4.13.0-26.29~16.04.2-generic 4.13.13 Uname: Linux 4.13.0-26-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CurrentDesktop: XFCE Date: Sun Jan 14 12:56:53 2018 InstallationDate: Installed on 2017-12-18 (27 days ago) InstallationMedia: Xubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) SourcePackage: evince UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1743244/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1743244] Re: Keyboard autorepeat does not work after latest update
Thank you for taking the time to report this bug and help make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read 'How to report bugs effectively' http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem. We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures. At a minimum, we need: 1. The specific steps or actions you took that caused you to encounter the problem. 2. The behavior you expected. 3. The behavior you actually encountered (in as much detail as possible). Thanks! ** Changed in: evince (Ubuntu) Importance: Undecided => Low ** Changed in: evince (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1743244 Title: Keyboard autorepeat does not work after latest update Status in evince package in Ubuntu: Incomplete Bug description: After latest update, keyboard autorepeat has stopped working. I can confirm that the problem is related to the peaq-wmi module having been recently whitelisted as using modprobe to remove peaq-wmi fixes the problem. Workaround: Blacklist the peaq-wmi module I really think the peaq-wmi module should be re-blacklised by default until the bugs can be worked out. Running Xubuntu, version 16.04.3 LTS ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: evince 3.18.2-1ubuntu4.3 ProcVersionSignature: Ubuntu 4.13.0-26.29~16.04.2-generic 4.13.13 Uname: Linux 4.13.0-26-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CurrentDesktop: XFCE Date: Sun Jan 14 12:56:53 2018 InstallationDate: Installed on 2017-12-18 (27 days ago) InstallationMedia: Xubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) SourcePackage: evince UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1743244/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1753966] Re: apparmor interfers with saving of PDF from evince
Thank you for your bug report. Is that still an issue? Do you use a special location for your user directory(or remote one)? ** Changed in: evince (Ubuntu) Importance: Undecided => Low ** Changed in: evince (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1753966 Title: apparmor interfers with saving of PDF from evince Status in evince package in Ubuntu: Incomplete Bug description: While trying to save an open PDF from evince, I clicked on the "create folder" button in the save dialog. Apparmor prevented directory creation in the respective directory. Saving within my "home" directory works. I consider this a bug. In my case, all user data resides in a separate data partition. With the current apparmor profiles, saving to this partition is hindered. Syslog contains: Mar 7 10:29:33 xxx kernel: [ 4569.159240] audit: type=1400 audit(1520414973.202:39): apparmor="DENIED" operation="mkdir" profile="/usr/bin/evince" name="x" pid=5393 comm="evince" requested_mask="c" denied_mask="c" fsuid=1000 ouid=1000 More generally, this seems to apply to a whole set of apparmor profiles that were updated or added recently... ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: apparmor-profiles (not installed) ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13 Uname: Linux 4.13.0-36-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CurrentDesktop: KDE Date: Wed Mar 7 10:32:37 2018 InstallationDate: Installed on 2017-12-01 (95 days ago) InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Release amd64 (20171017.1) ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-4.13.0-36-generic root=UUID=5c73304c-cd10-4645-99c9-2cf07aa48894 ro nosplash SourcePackage: apparmor Syslog: UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1753966/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1758497] Re: evince-thumbnailer crashed with SIGSEGV in tcache_get()
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 look at all reported bugs in a timely manner. Closing since one since it sounds like it was a font configuration issue and not one with the pdf viewer ** Changed in: evince (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1758497 Title: evince-thumbnailer crashed with SIGSEGV in tcache_get() Status in evince package in Ubuntu: Invalid Bug description: On ubuntu 18.04 bionic. Just logged in and this error comes out of nowhere. ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: evince 3.28.0-1 Uname: Linux 4.15.12-041512-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 Date: Fri Mar 23 22:55:53 2018 ExecutablePath: /usr/bin/evince-thumbnailer ProcAttrCurrent: /usr/bin/evince-thumbnailer (enforce) ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.15.12-041512-generic root=UUID=2f562704-a71b-4cb3-b9ca-86a2ff427b5e ro quiet splash vt.handoff=1 SegvAnalysis: Segfault happened at: 0x7fbec65d6207 <__GI___libc_malloc+407>: mov (%rdx),%rdi PC (0x7fbec65d6207) ok source "(%rdx)" (0x666e6f63746e6f66) not located in a known VMA region (needed readable region)! destination "%rdi" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: evince StacktraceTop: tcache_get (tc_idx=1) at malloc.c:2943 __GI___libc_malloc (bytes=32) at malloc.c:3050 () at /lib/x86_64-linux-gnu/libexpat.so.1 () at /lib/x86_64-linux-gnu/libexpat.so.1 () at /lib/x86_64-linux-gnu/libexpat.so.1 Title: evince-thumbnailer crashed with SIGSEGV in tcache_get() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1758497/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1755694] Re: evince crashed with SIGSEGV in IA__FcConfigSubstituteWithPat()
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please answer these questions: * Is this reproducible? * If so, what specific steps should we take to recreate this bug? * Is that specific to a document, if so could you add it to the bug report? This will help us to find and resolve the problem. ** Changed in: evince (Ubuntu) Importance: Medium => Low ** Changed in: evince (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1755694 Title: evince crashed with SIGSEGV in IA__FcConfigSubstituteWithPat() Status in evince package in Ubuntu: Incomplete Bug description: Crashed while opening a pdf file. ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: evince 3.27.92-1 ProcVersionSignature: Ubuntu 4.10.0-42.46~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-42-generic x86_64 NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Mar 14 12:04:07 2018 ExecutablePath: /usr/bin/evince ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.10.0-42-generic.efi.signed root=UUID=84d82523-78c3-487a-8680-e0b89e49e2c8 ro GRUB_CMDLINE_LINUX_DEFAULT=”quiet splash tpm_tis.interrupts=0 acpi_osi=Linux i915.preliminary_hw_support=1 idle=nomwait acpi=force acpi_enforce_resources=lax vt.handoff=1 ProcEnviron: XDG_RUNTIME_DIR= SHELL=/bin/bash LANGUAGE=en_IN:en PATH=(custom, user) LANG=en_IN SegvAnalysis: Segfault happened at: 0x7f665f71322c : mov(%rax,%rbx,8),%rax PC (0x7f665f71322c) ok source "(%rax,%rbx,8)" (0x5604cbb5af70) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: evince StacktraceTop: FcConfigSubstituteWithPat () from /usr/lib/x86_64-linux-gnu/libfontconfig.so.1 ?? () from /usr/lib/x86_64-linux-gnu/libpangocairo-1.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libpangoft2-1.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libpango-1.0.so.0 pango_itemize_with_base_dir () from /usr/lib/x86_64-linux-gnu/libpango-1.0.so.0 Title: evince crashed with SIGSEGV in FcConfigSubstituteWithPat() UpgradeStatus: Upgraded to bionic on 2018-03-09 (5 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1755694/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1761995] Re: Error Formatting luks device
I can confirm that this fix works on Ubuntu 20.04. To reiterate: sudo apt install libblockdev-crypto2 sudo service udisks2 restart -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-disk-utility in Ubuntu. https://bugs.launchpad.net/bugs/1761995 Title: Error Formatting luks device Status in udisks: Confirmed Status in gnome-disk-utility package in Ubuntu: Confirmed Status in meta-gnome3 package in Ubuntu: Confirmed Bug description: Application Gnome Disks When trying to format an encrypted drive I get this error: Error formatting volume Error creating the luks device:The function 'bd_crypto_luks_format_blob' called, but not implemented! (udisks- error-quark,0) 1. Description: Ubuntu Bionic Beaver (development branch) Release: 18.04 2. GNOME Disks 3.28.0-1ubuntu1 3. LUKS formatting disk should work 4. error message when opting for password protect volume (LUKS) utilizing format volume ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome (not installed) ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Apr 7 09:46:19 2018 InstallationDate: Installed on 2018-03-12 (26 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180311) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: meta-gnome3 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/udisks/+bug/1761995/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1762115] Re: Address boundary error
Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps: 1. Look in /var/crash for crash files and if found run: ubuntu-bug YOURFILE.crash Then tell us the ID of the newly-created bug. 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. 3. If step 2 also failed then apply the workaround from bug 994921, reboot, reproduce the crash, and retry step 1. Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself. ** Changed in: evince (Ubuntu) Importance: Undecided => Low ** Changed in: evince (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1762115 Title: Address boundary error Status in evince package in Ubuntu: Invalid Bug description: “evince” terminated by signal SIGSEGV (Address boundary error) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: evince 3.28.0-1 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Apr 8 13:20:35 2018 InstallationDate: Installed on 2018-03-21 (17 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180319) SourcePackage: evince UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1762115/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1762449] Re: /usr/bin/evince:11:g_type_check_instance_cast:ev_page_action_widget_set_current_page:ev_page_action_widget_set_document:g_closure_invoke:signal_emit_unlocked_R
Closing, there has been no report after 18.10 ** Changed in: evince (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1762449 Title: /usr/bin/evince:11:g_type_check_instance_cast:ev_page_action_widget_set_current_page:ev_page_action_widget_set_document:g_closure_invoke:signal_emit_unlocked_R Status in evince package in Ubuntu: Fix Released Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding evince. This problem was most recently seen with package version 3.26.0-3, the problem page at https://errors.ubuntu.com/problem/1e6a6edf4f1b615c3db2086177b2834c372dd290 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1762449/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1762425] Re: removing keyboard causes a restart
Thank you for taking the time to report this bug and help make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read 'How to report bugs effectively' http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem. We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures. At a minimum, we need: 1. The specific steps or actions you took that caused you to encounter the problem. 2. The behavior you expected. 3. The behavior you actually encountered (in as much detail as possible). Thanks! ** Changed in: evince (Ubuntu) Importance: Undecided => Low ** Changed in: evince (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1762425 Title: removing keyboard causes a restart Status in evince package in Ubuntu: Incomplete Bug description: removing keyboard,which is being used,in region and language settings causes soft restart. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: evince 3.26.0-1 ProcVersionSignature: Ubuntu 4.13.0-38.43-generic 4.13.16 Uname: Linux 4.13.0-38-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Apr 9 19:21:48 2018 InstallationDate: Installed on 2018-04-08 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash SourcePackage: evince UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1762425/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1760866] Re: evince crashed with SIGSEGV
Thank you for your bug report. Is that still an issue? Does it happen on a specific document? If so could you attach it there? ** Changed in: evince (Ubuntu) Importance: Medium => Low ** Changed in: evince (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1760866 Title: evince crashed with SIGSEGV Status in evince package in Ubuntu: Incomplete Bug description: Occured after updating Ubuntu 16.04 to Ubuntu 18.04 ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: evince 3.28.0-1 ProcVersionSignature: Ubuntu 4.13.0-38.43~16.04.1-generic 4.13.16 Uname: Linux 4.13.0-38-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Apr 3 15:48:35 2018 ExecutablePath: /usr/bin/evince InstallationDate: Installed on 2017-04-07 (360 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) KernLog: ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.13.0-38-generic root=UUID=ca55c159-bb62-4dd8-b07c-62b6ef55e404 ro quiet splash vt.handoff=1 SegvAnalysis: Segfault happened at: 0x5650d6d0e82d:mov0x38(%r13),%rax PC (0x5650d6d0e82d) ok source "0x38(%r13)" (0x0038) not located in a known VMA region (needed readable region)! destination "%rax" ok Stack memory exhausted (SP below stack segment) SegvReason: reading NULL VMA Signal: 11 SourcePackage: evince StacktraceTop: () () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 start_thread (arg=0x7f24b5b97700) at pthread_create.c:463 Title: evince crashed with SIGSEGV UpgradeStatus: Upgraded to bionic on 2018-03-29 (4 days ago) UserGroups: adm cdrom dip libvirt libvirtd lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1760866/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1762425] Re: removing keyboard causes a restart
the bug was reported agains the pdf viewer evince but it doesn't seem a problem with this software? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1762425 Title: removing keyboard causes a restart Status in evince package in Ubuntu: Incomplete Bug description: removing keyboard,which is being used,in region and language settings causes soft restart. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: evince 3.26.0-1 ProcVersionSignature: Ubuntu 4.13.0-38.43-generic 4.13.16 Uname: Linux 4.13.0-38-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Apr 9 19:21:48 2018 InstallationDate: Installed on 2018-04-08 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash SourcePackage: evince UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1762425/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1763564] Re: ubuntu suddently crash (stuck and nothing work) without reason
Thank you for taking the time to report this bug and help make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read 'How to report bugs effectively' http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem. We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures. At a minimum, we need: 1. The specific steps or actions you took that caused you to encounter the problem. 2. The behavior you expected. 3. The behavior you actually encountered (in as much detail as possible). Thanks! ** Changed in: evince (Ubuntu) Importance: Undecided => Low ** Changed in: evince (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1763564 Title: ubuntu suddently crash (stuck and nothing work) without reason Status in evince package in Ubuntu: Incomplete Bug description: it crash many time after using for less than 1h ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: evince 3.28.2-1 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Apr 13 10:52:26 2018 InstallationDate: Installed on 2018-04-12 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180409) SourcePackage: evince UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1763564/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1763564] Re: ubuntu suddently crash (stuck and nothing work) without reason
you reported the issue against the pdf viewer, does the problem has to do with this software? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1763564 Title: ubuntu suddently crash (stuck and nothing work) without reason Status in evince package in Ubuntu: Incomplete Bug description: it crash many time after using for less than 1h ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: evince 3.28.2-1 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Apr 13 10:52:26 2018 InstallationDate: Installed on 2018-04-12 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180409) SourcePackage: evince UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1763564/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1766213] Re: Document viewer hangs
Thank you for your bug report. Is that still an issue? Could you try with an newer Ubuntu serie? Is it specific to a document and if so could you share it? ** Changed in: evince (Ubuntu) Importance: Undecided => Low ** Changed in: evince (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1766213 Title: Document viewer hangs Status in evince package in Ubuntu: Incomplete Bug description: search in a pdf click on what is found in the left window document viewer goes dark document viewer hangs ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: evince 3.18.2-1ubuntu4.3 ProcVersionSignature: Ubuntu 4.13.0-38.43~16.04.1-generic 4.13.16 Uname: Linux 4.13.0-38-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 CurrentDesktop: Unity Date: Mon Apr 23 20:44:16 2018 ExecutablePath: /usr/bin/evince InstallationDate: Installed on 2017-12-13 (130 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) SourcePackage: evince UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1766213/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1768054] Re: PDF-Document not readable - viewer may not be able to display this type of document
Thank you for your bug report, it does sound similar to https://gitlab.gnome.org/GNOME/evince/-/issues/1031 ** Changed in: evince (Ubuntu) Importance: Undecided => Low ** Changed in: evince (Ubuntu) Status: New => Triaged ** Bug watch added: gitlab.gnome.org/GNOME/evince/-/issues #1031 https://gitlab.gnome.org/GNOME/evince/-/issues/1031 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1768054 Title: PDF-Document not readable - viewer may not be able to display this type of document Status in evince package in Ubuntu: Triaged Bug description: The attached document is not readable by evince, but it is readable by "Master PDF Editor" [1], so there may be a bug in evince. [1] https://code-industry.net/free-pdf-editor/#thinkupshortcodesthinkup_builder_toggle-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1768054/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1781414] Re: Error Atualização: E: Sub-process /usr/bin/dpkg returned an error code (1)
Thank you for your bug report, it doesn't seem it was an issue with the pdf viewer though ** Changed in: evince (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1781414 Title: Error Atualização: E: Sub-process /usr/bin/dpkg returned an error code (1) Status in evince package in Ubuntu: Invalid Bug description: sudo apt upgrade -y Lendo listas de pacotes... Pronto Construindo árvore de dependências Lendo informação de estado... Pronto Calculando atualização... Pronto Os pacotes a seguir serão atualizados: bluez bluez-cups bluez-obexd gir1.2-gnomedesktop-3.0 gir1.2-snapd-1 gnome-desktop3-data libbluetooth3 libgnome-desktop-3-17 libpython3-dev libpython3-stdlib libsnapd-glib1 python3 python3-dev python3-minimal python3-update-manager update-manager update-manager-core 17 pacotes atualizados, 0 pacotes novos instalados, 0 a serem removidos e 0 não atualizados. É preciso baixar 0 B/2.101 kB de arquivos. Depois desta operação, 6.144 B adicionais de espaço em disco serão usados. (Lendo banco de dados ... 217060 ficheiros e directórios actualmente instalados.) A preparar para desempacotar .../python3-dev_3.6.5-3ubuntu1_amd64.deb ... A descompactar python3-dev (3.6.5-3ubuntu1) sobre (3.6.5-3) ... A preparar para desempacotar .../python3-minimal_3.6.5-3ubuntu1_amd64.deb ... A descompactar python3-minimal (3.6.5-3ubuntu1) sobre (3.6.5-3) ... Configurando python3-minimal (3.6.5-3ubuntu1) ... (Lendo banco de dados ... 217060 ficheiros e directórios actualmente instalados.) A preparar para desempacotar .../00-python3_3.6.5-3ubuntu1_amd64.deb ... running python pre-rtupdate hooks for python3.6... A descompactar python3 (3.6.5-3ubuntu1) sobre (3.6.5-3) ... A preparar para desempacotar .../01-libpython3-dev_3.6.5-3ubuntu1_amd64.deb ... A descompactar libpython3-dev:amd64 (3.6.5-3ubuntu1) sobre (3.6.5-3) ... A preparar para desempacotar .../02-libpython3-stdlib_3.6.5-3ubuntu1_amd64.deb ... A descompactar libpython3-stdlib:amd64 (3.6.5-3ubuntu1) sobre (3.6.5-3) ... A preparar para desempacotar .../03-python3-update-manager_1%3a18.04.11.3_all.deb ... A descompactar python3-update-manager (1:18.04.11.3) sobre (1:18.04.11.2) ... A preparar para desempacotar .../04-update-manager-core_1%3a18.04.11.3_all.deb ... A descompactar update-manager-core (1:18.04.11.3) sobre (1:18.04.11.2) ... A preparar para desempacotar .../05-update-manager_1%3a18.04.11.3_all.deb ... A descompactar update-manager (1:18.04.11.3) sobre (1:18.04.11.2) ... A preparar para desempacotar .../06-bluez_5.48-0ubuntu3.1_amd64.deb ... A descompactar bluez (5.48-0ubuntu3.1) sobre (5.48-0ubuntu3) ... A preparar para desempacotar .../07-bluez-cups_5.48-0ubuntu3.1_amd64.deb ... A descompactar bluez-cups (5.48-0ubuntu3.1) sobre (5.48-0ubuntu3) ... A preparar para desempacotar .../08-bluez-obexd_5.48-0ubuntu3.1_amd64.deb ... A descompactar bluez-obexd (5.48-0ubuntu3.1) sobre (5.48-0ubuntu3) ... A preparar para desempacotar .../09-gnome-desktop3-data_3.28.2-0ubuntu1_all.deb ... A descompactar gnome-desktop3-data (3.28.2-0ubuntu1) sobre (3.28.1-1ubuntu1) ... A preparar para desempacotar .../10-libgnome-desktop-3-17_3.28.2-0ubuntu1_amd64.deb ... A descompactar libgnome-desktop-3-17:amd64 (3.28.2-0ubuntu1) sobre (3.28.1-1ubuntu1) ... A preparar para desempacotar .../11-gir1.2-gnomedesktop-3.0_3.28.2-0ubuntu1_amd64.deb ... A descompactar gir1.2-gnomedesktop-3.0:amd64 (3.28.2-0ubuntu1) sobre (3.28.1-1ubuntu1) ... A preparar para desempacotar .../12-gir1.2-snapd-1_1.41-0ubuntu0.18.04.1_amd64.deb ... A descompactar gir1.2-snapd-1:amd64 (1.41-0ubuntu0.18.04.1) sobre (1.39-0ubuntu1) ... A preparar para desempacotar .../13-libsnapd-glib1_1.41-0ubuntu0.18.04.1_amd64.deb ... A descompactar libsnapd-glib1:amd64 (1.41-0ubuntu0.18.04.1) sobre (1.39-0ubuntu1) ... A preparar para desempacotar .../14-libbluetooth3_5.48-0ubuntu3.1_amd64.deb ... A descompactar libbluetooth3:amd64 (5.48-0ubuntu3.1) sobre (5.48-0ubuntu3) ... Configurando libpython3-stdlib:amd64 (3.6.5-3ubuntu1) ... A processar 'triggers' para mime-support (3.60ubuntu1) ... A processar 'triggers' para ureadahead (0.100.0-20) ... ureadahead will be reprofiled on next reboot Configurando python3 (3.6.5-3ubuntu1) ... running python rtupdate hooks for python3.6... E: py3compile:183: cannot create directory /usr/share/hplip/ui5/__pycache__: FileNotFoundError(2, 'No such file or directory') [Errno 2] No such file or directory: '/usr/share/hplip/ui5/aboutdialog.py' [Errno 2] No such file or directory: '/usr/share/hplip/ui5/aboutdialog_base.py' [Errno 2] No such file or directory: '/usr/share/hplip/ui5/aligndialog.py' [Errno 2] No such file or directory: '/usr/share/hplip/ui5/aligndialog_base.py' [Errno 2] No s
[Desktop-packages] [Bug 1769834] Re: WLAN Adapter RTL 8821AU not recognized
** Package changed: evince (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1769834 Title: WLAN Adapter RTL 8821AU not recognized Status in linux package in Ubuntu: New Bug description: This Adapter works well under Windows 10 (64 Bit) but is not recognized by the Ubuntu 18.04 Desktop OS ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: evince 3.28.2-1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue May 8 09:04:39 2018 InstallationDate: Installed on 2018-05-07 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: evince UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1769834/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1781587] Re: Erro Ubuntu Bionic 18.04 LTS: E: Sub-process /usr/bin/dpkg returned an error code (1)
Thank you for your bug report, it doesn't seem it was an issue with the pdf viewer though ** Changed in: evince (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1781587 Title: Erro Ubuntu Bionic 18.04 LTS: E: Sub-process /usr/bin/dpkg returned an error code (1) Status in evince package in Ubuntu: Invalid Bug description: Alguém pode me ajudar na solução deste erro: Erro Ubuntu Bionic 18.04 LTS: E: Sub-process /usr/bin/dpkg returned an error code (1) edson@edson-p6540br:~$ sudo apt update [sudo] senha para edson: Atingido:1 http://linux.teamviewer.com/deb stable InRelease Atingido:2 http://br.archive.ubuntu.com/ubuntu bionic InRelease Ign:3 http://dl.google.com/linux/chrome/deb stable InRelease Atingido:4 http://linux.teamviewer.com/deb preview InRelease Atingido:5 https://deb.opera.com/opera-stable stable InRelease Atingido:6 http://br.archive.ubuntu.com/ubuntu bionic-backports InRelease Atingido:7 http://br.archive.ubuntu.com/ubuntu bionic-updates InRelease Atingido:8 http://dl.google.com/linux/chrome/deb stable Release Atingido:9 http://security.ubuntu.com/ubuntu bionic-security InRelease Atingido:10 http://archive.canonical.com/ubuntu bionic InRelease Atingido:11 http://ppa.launchpad.net/elementary-os/daily/ubuntu bionic InRelease Atingido:12 http://ppa.launchpad.net/noobslab/icons/ubuntu bionic InRelease Atingido:13 http://ppa.launchpad.net/ricotz/docky/ubuntu bionic InRelease Lendo listas de pacotes... Pronto Construindo árvore de dependências Lendo informação de estado... Pronto All packages are up to date. edson@edson-p6540br:~$ sudo apt upgrade Lendo listas de pacotes... Pronto Construindo árvore de dependências Lendo informação de estado... Pronto Calculando atualização... Pronto 0 pacotes atualizados, 0 pacotes novos instalados, 0 a serem removidos e 0 não atualizados. 6 pacotes não totalmente instalados ou removidos. Depois desta operação, 0 B adicionais de espaço em disco serão usados. Você quer continuar? [S/n] s Configurando python3 (3.6.5-3ubuntu1) ... running python rtupdate hooks for python3.6... E: py3compile:183: cannot create directory /usr/share/hplip/ui5/__pycache__: FileNotFoundError(2, 'No such file or directory') [Errno 2] No such file or directory: '/usr/share/hplip/ui5/aboutdialog.py' [Errno 2] No such file or directory: '/usr/share/hplip/ui5/aboutdialog_base.py' [Errno 2] No such file or directory: '/usr/share/hplip/ui5/aligndialog.py' [Errno 2] No such file or directory: '/usr/share/hplip/ui5/aligndialog_base.py' [Errno 2] No such file or directory: '/usr/share/hplip/ui5/cleandialog.py' [Errno 2] No such file or directory: '/usr/share/hplip/ui5/cleandialog_base.py' [Errno 2] No such file or directory: '/usr/share/hplip/ui5/colorcaldialog.py' [Errno 2] No such file or directory: '/usr/share/hplip/ui5/colorcaldialog_base.py' [Errno 2] No such file or directory: '/usr/share/hplip/ui5/devicesetupdialog.py' [Errno 2] No such file or directory: '/usr/share/hplip/ui5/devicesetupdialog_base.py' [Errno 2] No such file or directory: '/usr/share/hplip/ui5/deviceuricombobox.py' [Errno 2] No such file or directory: '/usr/share/hplip/ui5/devmgr5.py' [Errno 2] No such file or directory: '/usr/share/hplip/ui5/devmgr5_base.py' [Errno 2] No such file or directory: '/usr/share/hplip/ui5/devmgr_ext.py' [Errno 2] No such file or directory: '/usr/share/hplip/ui5/fabgrouptable.py' [Errno 2] No such file or directory: '/usr/share/hplip/ui5/fabnametable.py' [Errno 2] No such file or directory: '/usr/share/hplip/ui5/fabwindow.py' [Errno 2] No such file or directory: '/usr/share/hplip/ui5/fabwindow_base.py' [Errno 2] No such file or directory: '/usr/share/hplip/ui5/faxsetupdialog.py' [Errno 2] No such file or directory: '/usr/share/hplip/ui5/faxsetupdialog_base.py' [Errno 2] No such file or directory: '/usr/share/hplip/ui5/filetable.py' [Errno 2] No such file or directory: '/usr/share/hplip/ui5/firmwaredialog.py' [Errno 2] No such file or directory: '/usr/share/hplip/ui5/firmwaredialog_base.py' [Errno 2] No such file or directory: '/usr/share/hplip/ui5/infodialog.py' [Errno 2] No such file or directory: '/usr/share/hplip/ui5/infodialog_base.py' [Errno 2] No such file or directory: '/usr/share/hplip/ui5/linefeedcaldialog.py' [Errno 2] No such file or directory: '/usr/share/hplip/ui5/linefeedcaldialog_base.py' [Errno 2] No such file or directory: '/usr/share/hplip/ui5/loadpapergroupbox.py' [Errno 2] No such file or directory: '/usr/share/hplip/ui5/makecopiesdialog.py' [Errno 2] No such file or directory: '/usr/share/h
[Desktop-packages] [Bug 1785060] Re: Evince cannot open cbr-files based on rar v5
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command, as it will automatically gather debugging information, in a terminal: apport-collect 1785060 When reporting bugs in the future please use apport by using 'ubuntu- bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs. ** Changed in: evince (Ubuntu) Importance: Undecided => Low ** Changed in: evince (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1785060 Title: Evince cannot open cbr-files based on rar v5 Status in evince package in Ubuntu: Incomplete Bug description: Trying to open a cbr-Archive based on rar v5 leads to "Der Dateityp RAR-Archiv (application/vnd.rar) wird nicht unterstützt." CBR-Files based on other rar-Types, e.g. rarv4 works fine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1785060/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1785060] Re: Evince cannot open cbr-files based on rar v5
Could you also maybe include an example to the bug? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1785060 Title: Evince cannot open cbr-files based on rar v5 Status in evince package in Ubuntu: Incomplete Bug description: Trying to open a cbr-Archive based on rar v5 leads to "Der Dateityp RAR-Archiv (application/vnd.rar) wird nicht unterstützt." CBR-Files based on other rar-Types, e.g. rarv4 works fine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1785060/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1796354] Re: Document viewer (Evince) shows document "title" and not document "name" on titlebar
Thank you for your bug report, that's an upstream choice and you should rather open a ticket on gitlab.gnome.org to discuss changing the behaviour with the people writting the software ** Changed in: evince (Ubuntu) Importance: Undecided => Low ** Changed in: evince (Ubuntu) Status: New => Opinion -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1796354 Title: Document viewer (Evince) shows document "title" and not document "name" on titlebar Status in evince package in Ubuntu: Opinion Bug description: After upgrading to Ubuntu 18.04 Bionic Evince 3.28.2 shows document "title" and not document "name" on titlebar. This is very annoying since titles are pdf metadata that most commonly do not make sense, while pdf names (i.e. location) are easily modified by user and nexessary to distinguish files. This is actually a rebirth of an old issue that eas fixed in previous versions of Evince To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1796354/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1809685] Re: The evince application often freezes
Is anyone still having this issue in focal? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1809685 Title: The evince application often freezes Status in Evince: New Status in evince package in Ubuntu: Confirmed Bug description: Hi! The evince application (pdf document viewer) often freezes. Thanks. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: evince 3.28.4-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Dec 25 07:12:13 2018 InstallationDate: Installed on 2018-05-06 (232 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash SourcePackage: evince UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/evince/+bug/1809685/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1831588] Re: Slow photo saving from Evince to my folder in Nautilus
Is that still an issue? Is the ~1 second it takes to close the dialog that you consider slow? ** Changed in: evince (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1831588 Title: Slow photo saving from Evince to my folder in Nautilus Status in evince package in Ubuntu: Incomplete Bug description: Details in my video: https://photos.app.goo.gl/gouJpQSqS5QoXqFB6 Characteristics of my laptop: HP 250 G6, Intel Celeron N3350, integrated video card, 128 GB SSD, 4 GB DDR3, Ubuntu 19.04. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: nautilus 1:3.32.1-0ubuntu0.19.04.0 ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6 Uname: Linux 5.0.0-15-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Jun 4 12:39:02 2019 GsettingsChanges: b'org.gnome.nautilus.window-state' b'initial-size' b'(903, 495)' InstallationDate: Installed on 2019-05-31 (3 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1831588/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1822276] Re: Folder where a document was saved last is not saved
Thank you for your bug report. It seems similar to upstream https://gitlab.gnome.org/GNOME/evince/-/issues/909 but the behaviour should be that it stores in the same directory as the current document by default, or if it's a temp location then fallback to the document directory and it's not there to the user dir If you wish to discuss the behaviour it's better done on gitlab upstream than on launchpad ** Bug watch added: gitlab.gnome.org/GNOME/evince/-/issues #909 https://gitlab.gnome.org/GNOME/evince/-/issues/909 ** Changed in: evince (Ubuntu) Importance: Undecided => Low ** Changed in: evince (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1822276 Title: Folder where a document was saved last is not saved Status in evince package in Ubuntu: Invalid Bug description: This is probably a "duplicate" of a bug, which was fixed in evince 2.27, but now in evince 3.30 it seems to reappear again. Additionally, I am not sure if this is an evince bug or a gtk3 bug. The main problem is that the folder where a document was saved last is never stored. So for me a common workflow is downloading a pdf of a scientific publication and I need to store it somewhere in my filesystem. In many other instances (sumatrapdf on windows) the folder where I saved the last pdf is always stored. This means after I saved the first document for all subsequent documents I don't need to navigate the file system again. At the moment evince always starts in the home folder and I need to navigate through my filesystem again. This is on fedora 29 with evince 3.30.2 and gtk3 3.24.1. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1822276/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1822350] Re: evince crashed with SIGABRT in g_assertion_message()
** Changed in: evince (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1822350 Title: evince crashed with SIGABRT in g_assertion_message() Status in Evince: Fix Released Status in evince package in Ubuntu: Fix Released Bug description: https://gitlab.gnome.org/GNOME/evince/issues/1120 --- Click in 'File options->Dual' in my PDF. ProblemType: Crash DistroRelease: Ubuntu 19.04 Package: evince 3.32.0-1 Uname: Linux 5.0.5-050005-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Mar 29 13:24:40 2019 ExecutablePath: /usr/bin/evince InstallationDate: Installed on 2018-12-02 (116 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: BOOT_IMAGE=/@/boot/vmlinuz-5.0.5-050005-generic root=UUID=28bdadba-133c-4f5b-a5c9-b06993ea7ce2 ro rootflags=subvol=@ quiet splash vt.handoff=1 ProcEnviron: XDG_RUNTIME_DIR= SHELL=/bin/bash LANGUAGE=es_CL:es PATH=(custom, no user) LANG=es_CL.UTF-8 Signal: 6 SourcePackage: evince StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 g_hash_table_lookup () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () ?? () Title: evince crashed with SIGABRT in g_assertion_message_expr() UpgradeStatus: Upgraded to disco on 2018-12-02 (116 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/evince/+bug/1822350/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1842298] Re: Evince printing glitches on PDF documents from JHEP
The print preview displays fine on focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1842298 Title: Evince printing glitches on PDF documents from JHEP Status in evince package in Ubuntu: Fix Released Bug description: Evince is unable to print PDF documents from the open-access journal JHEP. Example file: https://link.springer.com/content/pdf/10.1007%2FJHEP07%282016%29126.pdf (alternatively, go to https://link.springer.com/article/10.1007%2FJHEP07%282016%29126 and click Download). Expected behavior: When I open the file in evince, hit Ctrl+P and go to "Preview" or print the file, I expect to see the document properly rendered. Actual behavior: Both the print preview and the printed result are an unreadable mess. I have encountered this problem on every PDF file from JHEP that I tested, but didn't encounter this problem on any PDF file from any other source. Only printing and print preview are affected, reading and browsing the file works without issues. The problem persists when a different printer is selected (in particular, it also appears when I choose "print to file"). I printed the same file on Windows using PDFXchange editor, where no problems appeared, suggesting that the file itself is not the root of the issue here. Affected package: evince Version information: Ubuntu 18.04.3 LTS, Evince version 3.28.4-0ubuntu1.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1842298/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1842298] Re: Evince printing glitches on PDF documents from JHEP
Thank you for taking the time to report this bug and helping to make Ubuntu better. However, I am closing it because the bug has been fixed in the current version of Ubuntu. This is a significant bug in Ubuntu. If you need a fix for the bug in previous versions of Ubuntu, please perform as much as possible of the SRU Procedure [1] to bring the need to a developer's attention. [1]: https://wiki.ubuntu.com/StableReleaseUpdates#Procedure ** Changed in: evince (Ubuntu) Importance: Undecided => Low ** Changed in: evince (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1842298 Title: Evince printing glitches on PDF documents from JHEP Status in evince package in Ubuntu: Fix Released Bug description: Evince is unable to print PDF documents from the open-access journal JHEP. Example file: https://link.springer.com/content/pdf/10.1007%2FJHEP07%282016%29126.pdf (alternatively, go to https://link.springer.com/article/10.1007%2FJHEP07%282016%29126 and click Download). Expected behavior: When I open the file in evince, hit Ctrl+P and go to "Preview" or print the file, I expect to see the document properly rendered. Actual behavior: Both the print preview and the printed result are an unreadable mess. I have encountered this problem on every PDF file from JHEP that I tested, but didn't encounter this problem on any PDF file from any other source. Only printing and print preview are affected, reading and browsing the file works without issues. The problem persists when a different printer is selected (in particular, it also appears when I choose "print to file"). I printed the same file on Windows using PDFXchange editor, where no problems appeared, suggesting that the file itself is not the root of the issue here. Affected package: evince Version information: Ubuntu 18.04.3 LTS, Evince version 3.28.4-0ubuntu1.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1842298/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1883497] Re: Only timing mode list in EDID supported on continuous freq monitors
Please provide: 1. An explanation of the bug on users and justification for backporting the fix to the stable release. 2. A discussion of how regressions are most likely to manifest, or may manifest even if it is unlikely, as a result of this change. 3. The version in which this bug is fixed in Groovy, and please fix the status of that task. ** Changed in: xorg-server (Ubuntu Focal) 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/1883497 Title: Only timing mode list in EDID supported on continuous freq monitors Status in HWE Next: New Status in X.Org X server: New Status in xf86-video-intel: Unknown Status in xorg-server package in Ubuntu: New Status in xorg-server source package in Focal: Incomplete Bug description: [Impact] Some new laptop display set EDID continuous freq bit 1. Then Xorg only uses the timing modes defined in EDID, no other modes are shown on Xorg. Upstream Bug: https://gitlab.freedesktop.org/drm/intel/-/issues/313 Fix of Xorg in merge request: https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/421 https://cgit.freedesktop.org/xorg/xserver/commit/?id=6a79a737e2c0bc730ee693b4ea4a1530c108be4e this is required to support new laptop models which use such panels [Test case] Test that a proper list of modes is shown with a panel that uses the new EDID. [Regression potential] The patch retains the previous code path for setting modes on GTF-able monitors, and only adds support for non-GTF monitors. So in that sense there shouldn't be any regression potential, this has been reviewed by an upstream expert. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1883497/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1848924] Re: Snap Evince can't open pdf files in USB drive
The issue is fixed in the beta channel now and will be in stable when 3.36 lands there ** Changed in: evince (Ubuntu) Status: In Progress => Fix Committed ** Changed in: evince (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1848924 Title: Snap Evince can't open pdf files in USB drive Status in evince package in Ubuntu: Fix Released Bug description: Steps to reproduce: - Put a .pdf file in an external USB drive - Double click on it or open it with Evince in any way Evince starts but it can't show the document, giving the error: Error opening file /media/username/Storage/file-name.pdf: Permission denied lsb_release -rd Description: Ubuntu 18.04.3 LTS Release: 18.04 snap --version snap2.42 snapd 2.42 series 16 ubuntu 18.04 kernel 4.15.0-65-generic snap list | grep evince evince3.32.0+git27.47fa15b1 163 stable ken-vandine - To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1848924/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1855581] Re: cannot select menu entry via keyboard
The issue is fixed in focal now ** Changed in: evince (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1855581 Title: cannot select menu entry via keyboard Status in evince package in Ubuntu: Fix Released Bug description: when I hit F10 and then start cursors down I expect some kind of visual confirmation of the menu entry I am to activate, but there is nothing highlighted. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: evince 3.28.4-0ubuntu1.2 ProcVersionSignature: Ubuntu 4.15.0-1065.75-oem 4.15.18 Uname: Linux 4.15.0-1065-oem x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Dec 8 11:50:26 2019 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+beaver-three-eyed-raven+X92 InstallationDate: Installed on 2019-11-16 (22 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 SourcePackage: evince UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1855581/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1867209] Re: evince crashes on searching in a PDF file
Thank you for your bug report, the issue seems resolved in the newer Ubuntu version (and upstream in poppler as mentioned on the gitlab bug you referenced), closing ** Changed in: evince (Ubuntu) Importance: Undecided => High ** Changed in: evince (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1867209 Title: evince crashes on searching in a PDF file Status in evince package in Ubuntu: Fix Released Bug description: Package: evince Version: 3.34.1-1 In the up-to-date Ubuntu 19.10 "eoan", Evince crashes when searching in a particular long PDF file. I open the file, press Ctrl+F to open a search string box, and type in some string that occurs in the document. Then, Evince starts searching, jumps to the first occurrence, and displays a thin progress bar while continuing searching. Evince doesn't terminate: about the middle of the search process, evince crashes: $ evince .pdf munmap_chunk(): invalid pointer Abgebrochen (Speicherabzug geschrieben) Unfortunately, I cannot share my PDF file due to legal reasons. However, the two files mentioned in https://gitlab.gnome.org/GNOME/evince/issues/1250 would do: - https://www.jaapsch.net/psion/pdffiles/hd6301-3_handbook.pdf - https://www.people.vcu.edu/~rhammack/BookOfProof/Main.pdf Searching for "the" (without the quotation marks) in any of these documents reproducibly crashes them. Here is the xterm contents on these occasions: $ export EV_DEBUG_JOBS=1 $ export G_MESSAGES_DEBUG=all $ evince Main.pdf (evince:8410): GLib-GIO-DEBUG: 21:40:47.788: _g_io_module_get_default: Found default implementation gvfs (GDaemonVfs) for ‘gio-vfs’ (evince:8410): Gtk-DEBUG: 21:40:47.860: Connecting to session manager (evince:8410): GLib-GIO-DEBUG: 21:40:47.869: desktop_file_dirs_lock: Resetting desktop app info dirs from (null) to /home/malkis/.config (evince:8410): GLib-GIO-DEBUG: 21:40:47.926: _g_io_module_get_default: Found default implementation dconf (DConfSettingsBackend) for ‘gsettings-backend’ (evince:8410): dconf-DEBUG: 21:40:47.926: watch_fast: "/org/gnome/evince/" (establishing: 0, active: 0) (evince:8410): dconf-DEBUG: 21:40:47.927: watch_established: "/org/gnome/evince/" (establishing: 1) (evince:8410): dconf-DEBUG: 21:40:47.951: watch_fast: "/org/gnome/evince/default/" (establishing: 0, active: 0) (evince:8410): dconf-DEBUG: 21:40:47.951: watch_established: "/org/gnome/evince/default/" (establishing: 1) (evince:8410): dconf-DEBUG: 21:40:48.028: watch_fast: "/org/gnome/desktop/lockdown/" (establishing: 0, active: 0) (evince:8410): dconf-DEBUG: 21:40:48.029: watch_established: "/org/gnome/desktop/lockdown/" (establishing: 1) ** (evince:8410): WARNING **: 21:40:50.284: No offset found for match "t" at page 9 after processing 55 results ** (evince:8410): WARNING **: 21:40:50.551: No offset found for match "the" at page 9 after processing 8 results munmap_chunk(): invalid pointer Abgebrochen (Speicherabzug geschrieben) $ evince hd6301-3_handbook.pdf (evince:8440): GLib-GIO-DEBUG: 21:41:26.259: _g_io_module_get_default: Found default implementation gvfs (GDaemonVfs) for ‘gio-vfs’ (evince:8440): Gtk-DEBUG: 21:41:26.332: Connecting to session manager (evince:8440): GLib-GIO-DEBUG: 21:41:26.340: desktop_file_dirs_lock: Resetting desktop app info dirs from (null) to /home/malkis/.config (evince:8440): GLib-GIO-DEBUG: 21:41:26.400: _g_io_module_get_default: Found default implementation dconf (DConfSettingsBackend) for ‘gsettings-backend’ (evince:8440): dconf-DEBUG: 21:41:26.400: watch_fast: "/org/gnome/evince/" (establishing: 0, active: 0) (evince:8440): dconf-DEBUG: 21:41:26.401: watch_established: "/org/gnome/evince/" (establishing: 1) (evince:8440): dconf-DEBUG: 21:41:26.424: watch_fast: "/org/gnome/evince/default/" (establishing: 0, active: 0) (evince:8440): dconf-DEBUG: 21:41:26.424: watch_established: "/org/gnome/evince/default/" (establishing: 1) (evince:8440): dconf-DEBUG: 21:41:26.596: watch_fast: "/org/gnome/desktop/lockdown/" (establishing: 0, active: 0) (evince:8440): dconf-DEBUG: 21:41:26.597: watch_established: "/org/gnome/desktop/lockdown/" (establishing: 1) free(): invalid next size (fast) Abgebrochen (Speicherabzug geschrieben) $ I cannot debug Evince myself (and a package such as evince-dbg seems to be unavailable anyway) and would therefore kindly ask the Ubuntu folks to attract the attention of the developers to this issue (or bugfix it or update Evince if a solution is already available). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1867209/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/
[Desktop-packages] [Bug 1866842] Re: AppArmor prevents evince to open >1 PDF file
Thank you for your bug report, the issue was fixed in this update https://bugs.launchpad.net/ubuntu/+source/evince/3.36.0-2 ** Changed in: evince (Ubuntu) Importance: Undecided => Low ** Changed in: evince (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1866842 Title: AppArmor prevents evince to open >1 PDF file Status in evince package in Ubuntu: Fix Released Bug description: On Ubuntu 20.04 (focal), evince 3.35.92-1 and 3.36.0-1 fail to open more than one PDF file via the command line: $ evince x.pdf y.pdf z.pdf Error launching evince file:///home/xyz/.../y.pdf: Failed to execute child process “/bin/sh” (Permission denied) Error launching evince file:///home/xyz/.../z.pdf: Failed to execute child process “/bin/sh” (Permission denied) Expected behavior: evince starts with one window each for x.pdf, y.pdf and z.pdf Actual behavior: evince starts with one window x.pdf dmesg output: [104866.021294] audit: type=1400 audit(1583846983.478:3714): apparmor="DENIED" operation="exec" profile="/usr/bin/evince" name="/bin/dash" pid=131016 comm="evince" requested_mask="x" denied_mask="x" fsuid=1000 ouid=0 [104866.022450] audit: type=1400 audit(1583846983.482:3715): apparmor="DENIED" operation="exec" profile="/usr/bin/evince" name="/bin/dash" pid=131019 comm="evince" requested_mask="x" denied_mask="x" fsuid=1000 ouid=0 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: evince 3.36.0-1 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu19 Architecture: amd64 CurrentDesktop: KDE Date: Tue Mar 10 14:20:38 2020 InstallationDate: Installed on 2016-11-26 (1199 days ago) InstallationMedia: Kubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.1) SourcePackage: evince UpgradeStatus: Upgraded to focal on 2020-03-06 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1866842/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1865131] Re: Evince 3.28.4-0 won't start anymore
Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps: 1. Look in /var/crash for crash files and if found run: ubuntu-bug YOURFILE.crash Then tell us the ID of the newly-created bug. 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. 3. If step 2 also failed then apply the workaround from bug 994921, reboot, reproduce the crash, and retry step 1. Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself. ** Changed in: evince (Ubuntu) Importance: Undecided => Low ** Changed in: evince (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1865131 Title: Evince 3.28.4-0 won't start anymore Status in evince package in Ubuntu: Invalid Bug description: Since a few days evince does not start anymore I tried reinstalling it but didn't fix it. If i type evince in terminal I get: (evince:10976): dbind-WARNING **: 12:53:45.012: Error retrieving accessibility bus address: org.freedesktop.DBus.Error.ServiceUnknown: The name org.a11y.Bus was not provided by any .service files Segmentation fault (core dumped) Don't know if it can be useful. If try to open a pdf I get: (evince:11711): dbind-WARNING **: 12:58:05.458: Error retrieving accessibility bus address: org.freedesktop.DBus.Error.ServiceUnknown: The name org.a11y.Bus was not provided by any .service files (evince:11719): dbind-WARNING **: 12:58:05.521: Error retrieving accessibility bus address: org.freedesktop.DBus.Error.ServiceUnknown: The name org.a11y.Bus was not provided by any .service files Segmentation fault (core dumped) I am on Lubuntu 18.04 evince 3.28.4-0 The same issue was reported on evince gitlab but someone (a dev?) said that the version is too old to be handled by them and ask here. https://gitlab.gnome.org/GNOME/evince/issues/1346 that's the original report (by another user with the same issue) Edit: Installing the latest version from Flathub makes evince to run again (even though in terminal shows the error below) (evince:2): dbind-WARNING **: 22:11:54.800: AT-SPI: Error retrieving accessibility bus address: org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown So while it does not fixes the issue from the affected version, it makes evince usable for users again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1865131/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1881918] Re: Update GNOME Software to 3.36.1 in Focal
After enabling -proposed I updated gnome-software to version 3.36.1-0ubuntu0.20.04.0. After checking that each category was fully populated with icons that represented software applications I successfully installed and removed two applications from the Ubuntu repositories (.deb) and a snap application. I also checked that the options on the 'hamburger' menu were functioning correctly and that it wasn't possible for gnome-software to remove itself. ** Tags removed: verification-needed verification-needed-focal ** Tags added: verification-done verification-done-focal ** Changed in: hundredpapercuts Status: New => Fix Committed ** Changed in: hundredpapercuts Importance: Wishlist => Medium -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1881918 Title: Update GNOME Software to 3.36.1 in Focal Status in One Hundred Papercuts: Fix Committed Status in gnome-software package in Ubuntu: Fix Released Status in gnome-software source package in Focal: Fix Committed Bug description: [ Description ] GNOME upstream have released a new stable version of gnome-software. [ QA ] GNOME has a micro release exception that covers this package. https://wiki.ubuntu.com/StableReleaseUpdates/GNOME So we don't need to verify the fixes explicitly. [ Regression Potential ] Changes could cause issues in GNOME Software, which might make it hard to install or remove software. Default store in Ubuntu is snap-store, so this doesn't affect the majority of users. To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1881918/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1885452] Re: pc freezes and crashes during accountsservice upgrade on fresh ubuntu focal fossa install
The problem does seem to have to do with the nouveau driver, did you try to enable nvidia instead? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1885452 Title: pc freezes and crashes during accountsservice upgrade on fresh ubuntu focal fossa install Status in gnome-session package in Ubuntu: Incomplete Bug description: After a fresh install of Focal Fossa and running sudo apt update and sudo apt upgrade, when the upgrade reaches "setting up accountsservice" the PC freezes, then crashes. This was reproducible on another computer (laptop). I reinstalled Ubuntu and put the package on hold. Later, I found that by installing and activating lightdm, this problem was remediated. Found this solution accidentally, while I was looking to correct login screen loops after I installed the nvidia drivers. This is unrelated, since the laptop does not have nvidia. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-06-29 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Package: accountsservice 0.6.55-0ubuntu12~20.04.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-39.43-generic 5.4.41 Tags: focal Uname: Linux 5.4.0-39-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-session/+bug/1885452/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1885941] Re: Bug on boot
Thank you for taking the time to report this bug and help make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read 'How to report bugs effectively' http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem. We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures. At a minimum, we need: 1. The specific steps or actions you took that caused you to encounter the problem. 2. The behavior you expected. 3. The behavior you actually encountered (in as much detail as possible). Thanks! ** Changed in: xorg (Ubuntu) Importance: Undecided => Low ** 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/1885941 Title: Bug on boot Status in xorg package in Ubuntu: Incomplete Bug description: See attached detailed file. Just started reporting internal system errors on boot up. Not sure why this has started - don't think I've installed anything recently to spark it off but there was a system update recently. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3.1 ProcVersionSignature: Ubuntu 4.4.0-184.214-generic 4.4.223 Uname: Linux 4.4.0-184-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.23 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 Jul 1 18:06:26 2020 DistUpgraded: 2020-05-30 23:46:52,273 DEBUG icon theme changed, re-reading DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Mobile 4 Series Chipset Integrated Graphics Controller [1025:013c] Subsystem: Acer Incorporated [ALI] Mobile 4 Series Chipset Integrated Graphics Controller [1025:013c] InstallationDate: Installed on 2020-05-30 (31 days ago) InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 (20160217.1) MachineType: Acer Extensa 5630 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-184-generic root=UUID=7db4d8a4-7f23-45ec-99b9-fd99f55368aa ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to xenial on 2020-05-30 (31 days ago) dmi.bios.date: 12/05/2008 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: V1.25 dmi.board.name: Homa dmi.board.vendor: Acer dmi.board.version: Rev dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvrV1.25:bd12/05/2008:svnAcer:pnExtensa5630:pvr0100:rvnAcer:rnHoma:rvrRev:cvnAcer:ct10:cvrN/A: dmi.product.name: Extensa 5630 dmi.product.version: 0100 dmi.sys.vendor: Acer 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 2:1.18.4-0ubuntu0.8 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: Wed Jul 1 17:25:18 2020 xserver.configfile: default xserver.errors: /dev/dri/card0: failed to set DRM interface version 1.4: Permission denied /dev/dri/card0: failed to set DRM interface version 1.4: Permission denied xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id5460 vendor CMO xserver.version: 2:1.18.4-0ubuntu0.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1885941/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1885953] Re: color-cc-panel calls gcm-calibrate which was removed from package
Thank you for your bug report, indeed that's known upstream https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/951 ** Bug watch added: gitlab.gnome.org/GNOME/gnome-control-center/-/issues #951 https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/951 ** Changed in: gnome-control-center (Ubuntu) Importance: Undecided => Low ** Changed in: gnome-control-center (Ubuntu) Status: New => Triaged ** Also affects: gnome-control-center via https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/951 Importance: Unknown Status: Unknown -- 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/1885953 Title: color-cc-panel calls gcm-calibrate which was removed from package Status in gnome-control-center: Unknown Status in gnome-control-center package in Ubuntu: Triaged Bug description: Description: Ubuntu 20.04 LTS Release: 20.04 gnome-control-center: 1:3.36.2-0ubuntu1 Trying to calibrate a scanner clicking on "Calibrate" button tries to launch /usr/bin/gcm-calibrate which is not present in the actual gnome-color-manager package. I expected a calibration window to be opened. Nothing happened. Launching gnome-control-center from terminal returned: (gnome-control-center:10648): color-cc-panel-WARNING **: 21:31:06.478: failed to run calibrate: Ezin izan da “/usr/bin/gcm-calibrate” prozesu haurra exekutatu (No such file or directory) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-39.43-generic 5.4.41 Uname: Linux 5.4.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jul 1 21:38:16 2020 InstallationDate: Installed on 2020-06-25 (6 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=eu_ES.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1885953/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1885313] Re: evince crashes when opening rfc8798.pdf
The focal version of poppler doesn't have the issue as pointed in the Debian report ** Package changed: evince (Ubuntu) => poppler (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1885313 Title: evince crashes when opening rfc8798.pdf Status in poppler package in Ubuntu: Fix Released Status in evince package in Debian: New Bug description: evince reproducabely crashes when opening the file rfc8798.pdf from https://www.rfc-editor.org/rfc/rfc8798.pdf: $ evince --version GNOME Document Viewer 3.28.4 $ evince rfc8798.pdf Segmentation fault (core dumped) $ cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=18.04 DISTRIB_CODENAME=bionic DISTRIB_DESCRIPTION="Ubuntu 18.04.4 LTS" Required information: 1) Ubuntu release info: $ lsb_release -rd Description:Ubuntu 18.04.4 LTS Release:18.04 2) Package version info: $ apt-cache policy evince evince: Installed: 3.28.4-0ubuntu1.2 Candidate: 3.28.4-0ubuntu1.2 Version table: *** 3.28.4-0ubuntu1.2 500 500 http://de.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 3.28.2-1 500 500 http://de.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 3) Expected outcome: I expected evince to successfully open the PDF, allowing me to read the document. 4) Observed behavior: The default PDF reader of Ubuntu, evince, crashed (reporting a "segmentation fault". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1885313/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1885313] Re: evince crashes when opening rfc8798.pdf
Thank you for taking the time to report this bug and helping to make Ubuntu better. However, I am closing it because the bug has been fixed in the current version of Ubuntu. This is a significant bug in Ubuntu. If you need a fix for the bug in previous versions of Ubuntu, please perform as much as possible of the SRU Procedure [1] to bring the need to a developer's attention. [1]: https://wiki.ubuntu.com/StableReleaseUpdates#Procedure ** Changed in: evince (Ubuntu) Importance: Undecided => High ** Changed in: evince (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1885313 Title: evince crashes when opening rfc8798.pdf Status in poppler package in Ubuntu: Fix Released Status in evince package in Debian: New Bug description: evince reproducabely crashes when opening the file rfc8798.pdf from https://www.rfc-editor.org/rfc/rfc8798.pdf: $ evince --version GNOME Document Viewer 3.28.4 $ evince rfc8798.pdf Segmentation fault (core dumped) $ cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=18.04 DISTRIB_CODENAME=bionic DISTRIB_DESCRIPTION="Ubuntu 18.04.4 LTS" Required information: 1) Ubuntu release info: $ lsb_release -rd Description:Ubuntu 18.04.4 LTS Release:18.04 2) Package version info: $ apt-cache policy evince evince: Installed: 3.28.4-0ubuntu1.2 Candidate: 3.28.4-0ubuntu1.2 Version table: *** 3.28.4-0ubuntu1.2 500 500 http://de.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 3.28.2-1 500 500 http://de.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 3) Expected outcome: I expected evince to successfully open the PDF, allowing me to read the document. 4) Observed behavior: The default PDF reader of Ubuntu, evince, crashed (reporting a "segmentation fault". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1885313/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1866574] [snapd-glib/eoan] verification still needed
The fix for this bug has been awaiting testing feedback in the -proposed repository for eoan for more than 90 days. Please test this fix and update the bug appropriately with the results. In the event that the fix for this bug is still not verified 15 days from now, the package will be removed from the -proposed repository. ** Tags added: removal-candidate -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to snapd-glib in Ubuntu. https://bugs.launchpad.net/bugs/1866574 Title: Update to 1.56 Status in snapd-glib package in Ubuntu: Fix Released Status in snapd-glib source package in Bionic: Confirmed Status in snapd-glib source package in Eoan: Fix Committed Status in snapd-glib source package in Focal: Fix Released Bug description: [Impact] A newer snapd-glib is available that adds support for new features in snapd. snapd-glib has an SRU exception as per https://wiki.ubuntu.com/SnapdGlibUpdates [Test Case] The reverse depends of snapd-glib should continue to function, this is currently: - gnome-software - gnome-initial-setup - pulseaudio [Regression Potential] Any new release has a risk of introducing bugs, this is mitigated by automatic regression tests. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd-glib/+bug/1866574/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1885953] [NEW] color-cc-panel calls gcm-calibrate which was removed from package
Public bug reported: Description:Ubuntu 20.04 LTS Release:20.04 gnome-control-center: 1:3.36.2-0ubuntu1 Trying to calibrate a scanner clicking on "Calibrate" button tries to launch /usr/bin/gcm-calibrate which is not present in the actual gnome- color-manager package. I expected a calibration window to be opened. Nothing happened. Launching gnome-control-center from terminal returned: (gnome-control-center:10648): color-cc-panel-WARNING **: 21:31:06.478: failed to run calibrate: Ezin izan da “/usr/bin/gcm-calibrate” prozesu haurra exekutatu (No such file or directory) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-39.43-generic 5.4.41 Uname: Linux 5.4.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jul 1 21:38:16 2020 InstallationDate: Installed on 2020-06-25 (6 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=eu_ES.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1885953 Title: color-cc-panel calls gcm-calibrate which was removed from package Status in gnome-control-center package in Ubuntu: New Bug description: Description: Ubuntu 20.04 LTS Release: 20.04 gnome-control-center: 1:3.36.2-0ubuntu1 Trying to calibrate a scanner clicking on "Calibrate" button tries to launch /usr/bin/gcm-calibrate which is not present in the actual gnome-color-manager package. I expected a calibration window to be opened. Nothing happened. Launching gnome-control-center from terminal returned: (gnome-control-center:10648): color-cc-panel-WARNING **: 21:31:06.478: failed to run calibrate: Ezin izan da “/usr/bin/gcm-calibrate” prozesu haurra exekutatu (No such file or directory) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-39.43-generic 5.4.41 Uname: Linux 5.4.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jul 1 21:38:16 2020 InstallationDate: Installed on 2020-06-25 (6 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=eu_ES.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1885953/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1816497] Re: [snap] vaapi chromium no video hardware decoding
@osomon: did you build for arm64? should I try again? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1816497 Title: [snap] vaapi chromium no video hardware decoding Status in chromium-browser package in Ubuntu: In Progress Bug description: News : - Candidate Chromium 83 Snap with vaapi enabled can be installed with : sudo snap install --channel=candidate/vaapi chromium Check that your vidéo is gpu decoded but checking "MojoVideoDecoder" in about:media-internals Widevine DRM streams will have DecryptingVideoDecoder Please report success/failure with - distro version - GPU Hardware used - Codec used --Original Bug report - Libva is no longer working for snap installed chromium 72.0.3626.109 (Official Build) snap (64-bit) I followed this instruction sudo snap install --channel=candidate/vaapi chromium My amdgpu can use libva `vainfo: Driver version: Mesa Gallium driver 18.3.3 for AMD STONEY (DRM 3.27.0, 4.20.0-10.1-liquorix-amd64, LLVM 7.0.1) vainfo: Supported profile and entrypoints VAProfileMPEG2Simple: VAEntrypointVLD VAProfileMPEG2Main : VAEntrypointVLD VAProfileVC1Simple : VAEntrypointVLD VAProfileVC1Main: VAEntrypointVLD VAProfileVC1Advanced: VAEntrypointVLD VAProfileH264ConstrainedBaseline: VAEntrypointVLD VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice VAProfileH264Main : VAEntrypointVLD VAProfileH264Main : VAEntrypointEncSlice VAProfileH264High : VAEntrypointVLD VAProfileH264High : VAEntrypointEncSlice VAProfileHEVCMain : VAEntrypointVLD VAProfileHEVCMain10 : VAEntrypointVLD VAProfileJPEGBaseline : VAEntrypointVLD VAProfileNone : VAEntrypointVideoProc` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1816497/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1877016] Re: ubuntu-wsl / wslu : needs /mnt/c/windows/system32/ in PATH env variable
Will this fix be released for versions of Ubuntu other than Groovy? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wslu in Ubuntu. https://bugs.launchpad.net/bugs/1877016 Title: ubuntu-wsl / wslu : needs /mnt/c/windows/system32/ in PATH env variable Status in wslu package in Ubuntu: Fix Released Status in wslu source package in Xenial: Confirmed Status in wslu source package in Bionic: Confirmed Status in wslu source package in Focal: Confirmed Status in wslu source package in Groovy: Fix Released Bug description: [Impact] This affects all wslu tools on all releases. When PATH do not include Windows path, the all tools will complain that reg.exe is not found. [Test Case] * Add appendWindowsPath = false under [interop] section in /etc/wsl.conf file, and restart the distribution * run any wslu tool (like wslfetch) * "/mnt/c/Windows/System32/reg.exe: Permission denied" should not be shown [Regression Potential] * For future release of wslu 3.1.0 proposed, huge refactoring will be needed. [Original Bug Report] ubuntu-wsl / wslu : needs /mnt/c/windows/system32/ in PATH env variable $ wslfetch /usr/bin/wslfetch: line 108: reg.exe: command not found /usr/bin/wslsys: line 108: reg.exe: command not found /usr/bin/wslsys: line 183: /mnt/c/Windows/System32/reg.exe: Permission denied /usr/bin/wslsys: line 185: /mnt/c/Windows/System32/reg.exe: Permission denied /usr/bin/wslsys: line 187: /mnt/c/Windows/System32/reg.exe: Permission denied /usr/bin/wslsys: line 189: /mnt/c/Windows/System32/reg.exe: Permission denied /usr/bin/wslsys: line 108: reg.exe: command not found /usr/bin/wslsys: line 183: /mnt/c/Windows/System32/reg.exe: Permission denied /usr/bin/wslsys: line 185: /mnt/c/Windows/System32/reg.exe: Permission denied /usr/bin/wslsys: line 187: /mnt/c/Windows/System32/reg.exe: Permission denied /usr/bin/wslsys: line 189: /mnt/c/Windows/System32/reg.exe: Permission denied /usr/bin/wslsys: line 108: reg.exe: command not found /usr/bin/wslsys: line 183: /mnt/c/Windows/System32/reg.exe: Permission denied /usr/bin/wslsys: line 185: /mnt/c/Windows/System32/reg.exe: Permission denied /usr/bin/wslsys: line 187: /mnt/c/Windows/System32/reg.exe: Permission denied /usr/bin/wslsys: line 189: /mnt/c/Windows/System32/reg.exe: Permission denied /usr/bin/wslsys: line 108: reg.exe: command not found /usr/bin/wslsys: line 183: /mnt/c/Windows/System32/reg.exe: Permission denied /usr/bin/wslsys: line 185: /mnt/c/Windows/System32/reg.exe: Permission denied /usr/bin/wslsys: line 187: /mnt/c/Windows/System32/reg.exe: Permission denied /usr/bin/wslsys: line 189: /mnt/c/Windows/System32/reg.exe: Permission denied /usr/bin/wslsys: line 108: reg.exe: command not found /usr/bin/wslsys: line 183: /mnt/c/Windows/System32/reg.exe: Permission denied /usr/bin/wslsys: line 185: /mnt/c/Windows/System32/reg.exe: Permission denied /usr/bin/wslsys: line 187: /mnt/c/Windows/System32/reg.exe: Permission denied /usr/bin/wslsys: line 189: /mnt/c/Windows/System32/reg.exe: Permission denied ./+o+- Windows 10 Linux Subsystem y. 'yy+ rafaeldtinoco@lenovo .;//+/h yyo BUILD: .++ .:/++/-.`sss/` BRANCH: .:++o: `\/:---:/-RELEASE:Ubuntu 20.04 LTS o:+o+:++. `'-/ooo+\ KERNEL: Linux 4.4.0-18362-Microsoft .:+o:+o/. `+sssooo+\ UPTIME: 0d 2h 6m .++/+ +oo+o:` \sssooo; /+++//+: oo+o \+/+o+++ o++o ydddhh+ .++.o+ +oo+:` /dddhhh; .+.o+oo:. odd+ \+.++o+o` -.:ohdh+ `:o+++ oyo++os: .o: .syhhh'.oo++o. /osyyy.+++\ ` +oo+++o:/ `oo++'` After : echo $PATH /snap/bin:/snap/sbin:/mnt/c/windows/system32/:/home/rafaeldtinoco/work/sources/upstream/ubuntu-dev-tools/:/usr/lib/ccache:/sbin:/bin:/usr/sbin:/usr/bin:/home/rafaeldtinoco/work/sources/bzr/ubuntu-archive-tools:/home/rafaeldtinoco/work/sources/upstream/lxd/bin:. $ wslfetch ./+o+- Windows 10 Linux Subsystem y. 'yy+ rafaeldtinoco@lenovo .;//+/h yyo BUILD:18363 .++ .:/++/-.`sss/` BRANCH: 19h1_release .:++o: `\/:---:/-RELEASE: Ubuntu 20.04 LTS o:+o+:++. `'-/ooo+\ KERNEL: Linux 4.4.0-18362-Microsoft .:+o:+o/. `+sssooo+\ UPTIME: 0d 2h 19m .++/+ +oo+o:` \sssooo; /+++//+: oo+o \+/+o+++ o++o ydddhh+ .++.o+ +oo+:` /dddhhh; .+.o+oo:. odd+ \+.++o+o` -.:ohdh+ `:o+++ oyo++os: .
[Desktop-packages] [Bug 1877016] Re: ubuntu-wsl / wslu : needs /mnt/c/windows/system32/ in PATH env variable
This bug was fixed in the package wslu - 2.3.6-0ubuntu3 --- wslu (2.3.6-0ubuntu3) groovy; urgency=medium * debian/rules: - update the svg conversion commands for the current inkscape version and fix the build -- Patrick Wu Wed, 01 Jul 2020 16:07:10 +0200 ** Changed in: wslu (Ubuntu Groovy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wslu in Ubuntu. https://bugs.launchpad.net/bugs/1877016 Title: ubuntu-wsl / wslu : needs /mnt/c/windows/system32/ in PATH env variable Status in wslu package in Ubuntu: Fix Released Status in wslu source package in Xenial: Confirmed Status in wslu source package in Bionic: Confirmed Status in wslu source package in Focal: Confirmed Status in wslu source package in Groovy: Fix Released Bug description: [Impact] This affects all wslu tools on all releases. When PATH do not include Windows path, the all tools will complain that reg.exe is not found. [Test Case] * Add appendWindowsPath = false under [interop] section in /etc/wsl.conf file, and restart the distribution * run any wslu tool (like wslfetch) * "/mnt/c/Windows/System32/reg.exe: Permission denied" should not be shown [Regression Potential] * For future release of wslu 3.1.0 proposed, huge refactoring will be needed. [Original Bug Report] ubuntu-wsl / wslu : needs /mnt/c/windows/system32/ in PATH env variable $ wslfetch /usr/bin/wslfetch: line 108: reg.exe: command not found /usr/bin/wslsys: line 108: reg.exe: command not found /usr/bin/wslsys: line 183: /mnt/c/Windows/System32/reg.exe: Permission denied /usr/bin/wslsys: line 185: /mnt/c/Windows/System32/reg.exe: Permission denied /usr/bin/wslsys: line 187: /mnt/c/Windows/System32/reg.exe: Permission denied /usr/bin/wslsys: line 189: /mnt/c/Windows/System32/reg.exe: Permission denied /usr/bin/wslsys: line 108: reg.exe: command not found /usr/bin/wslsys: line 183: /mnt/c/Windows/System32/reg.exe: Permission denied /usr/bin/wslsys: line 185: /mnt/c/Windows/System32/reg.exe: Permission denied /usr/bin/wslsys: line 187: /mnt/c/Windows/System32/reg.exe: Permission denied /usr/bin/wslsys: line 189: /mnt/c/Windows/System32/reg.exe: Permission denied /usr/bin/wslsys: line 108: reg.exe: command not found /usr/bin/wslsys: line 183: /mnt/c/Windows/System32/reg.exe: Permission denied /usr/bin/wslsys: line 185: /mnt/c/Windows/System32/reg.exe: Permission denied /usr/bin/wslsys: line 187: /mnt/c/Windows/System32/reg.exe: Permission denied /usr/bin/wslsys: line 189: /mnt/c/Windows/System32/reg.exe: Permission denied /usr/bin/wslsys: line 108: reg.exe: command not found /usr/bin/wslsys: line 183: /mnt/c/Windows/System32/reg.exe: Permission denied /usr/bin/wslsys: line 185: /mnt/c/Windows/System32/reg.exe: Permission denied /usr/bin/wslsys: line 187: /mnt/c/Windows/System32/reg.exe: Permission denied /usr/bin/wslsys: line 189: /mnt/c/Windows/System32/reg.exe: Permission denied /usr/bin/wslsys: line 108: reg.exe: command not found /usr/bin/wslsys: line 183: /mnt/c/Windows/System32/reg.exe: Permission denied /usr/bin/wslsys: line 185: /mnt/c/Windows/System32/reg.exe: Permission denied /usr/bin/wslsys: line 187: /mnt/c/Windows/System32/reg.exe: Permission denied /usr/bin/wslsys: line 189: /mnt/c/Windows/System32/reg.exe: Permission denied ./+o+- Windows 10 Linux Subsystem y. 'yy+ rafaeldtinoco@lenovo .;//+/h yyo BUILD: .++ .:/++/-.`sss/` BRANCH: .:++o: `\/:---:/-RELEASE:Ubuntu 20.04 LTS o:+o+:++. `'-/ooo+\ KERNEL: Linux 4.4.0-18362-Microsoft .:+o:+o/. `+sssooo+\ UPTIME: 0d 2h 6m .++/+ +oo+o:` \sssooo; /+++//+: oo+o \+/+o+++ o++o ydddhh+ .++.o+ +oo+:` /dddhhh; .+.o+oo:. odd+ \+.++o+o` -.:ohdh+ `:o+++ oyo++os: .o: .syhhh'.oo++o. /osyyy.+++\ ` +oo+++o:/ `oo++'` After : echo $PATH /snap/bin:/snap/sbin:/mnt/c/windows/system32/:/home/rafaeldtinoco/work/sources/upstream/ubuntu-dev-tools/:/usr/lib/ccache:/sbin:/bin:/usr/sbin:/usr/bin:/home/rafaeldtinoco/work/sources/bzr/ubuntu-archive-tools:/home/rafaeldtinoco/work/sources/upstream/lxd/bin:. $ wslfetch ./+o+- Windows 10 Linux Subsystem y. 'yy+ rafaeldtinoco@lenovo .;//+/h yyo BUILD:18363 .++ .:/++/-.`sss/` BRANCH: 19h1_release .:++o: `\/:---:/-RELEASE: Ubuntu 20.04 LTS o:+o+:++. `'-/ooo+\ KERNEL: Linux 4.4.0-18362-Microsoft .:+o:+o/.
[Desktop-packages] [Bug 1883924] Re: Ubuntu.exe will not be detected properly if other LTS version is installed
This bug was fixed in the package wslu - 2.3.6-0ubuntu3 --- wslu (2.3.6-0ubuntu3) groovy; urgency=medium * debian/rules: - update the svg conversion commands for the current inkscape version and fix the build -- Patrick Wu Wed, 01 Jul 2020 16:07:10 +0200 ** Changed in: wslu (Ubuntu Groovy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wslu in Ubuntu. https://bugs.launchpad.net/bugs/1883924 Title: Ubuntu.exe will not be detected properly if other LTS version is installed Status in wslu package in Ubuntu: Fix Released Status in wslu source package in Xenial: New Status in wslu source package in Bionic: New Status in wslu source package in Focal: New Status in wslu source package in Groovy: Fix Released Bug description: [Impact] This affects all wslu tools on all releases when using from the Ubuntu app from Microsoft Store. When other LTS version of app is installed from Microsoft Store, baseexec generated by wslu on Ubuntu app will not be using ubuntu.exe but other LTS release apps (such as ubuntu1804.exe) [Test Case] * Install Ubuntu and Ubuntu 18.04 LTS from Microsoft Store. * run any wslu tools (like wslfetch --help) * Verify that ~/.config/wslu/baseexec contains the path to ubuntu.exe [Regression Potential] * None for now. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wslu/+bug/1883924/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1865300] Re: gnome-shell-hotplug-sniffer crashed with SIGSEGV in g_str_hash() from g_hash_table_lookup() from deep_count_more_files_callback()
After 12 days in proposed I see that e.u.c has only one report, that looks to be more a false positive or a crash that isn't due to the same root case of this bug, so I'd say we can confirm this bug. ** Tags removed: verification-needed verification-needed-focal ** Tags added: verification-done verification-done-focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1865300 Title: gnome-shell-hotplug-sniffer crashed with SIGSEGV in g_str_hash() from g_hash_table_lookup() from deep_count_more_files_callback() Status in GNOME Shell: Unknown Status in glib2.0 package in Ubuntu: Invalid Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell source package in Focal: Fix Committed Bug description: [ Impact ] gnome-shell-hotplug-sniffer crashes when attaching some device that may have files with unknown content type [ Test case ] - Plug a media, but it's not yet known which kind of files cause this issue, so we should just monitor the e.u.c crash: https://errors.ubuntu.com/problem/2edf29b9677e3de0d55d2114024f39c4c52b45e9 [ Regression potential ] - No valid application for opening a media is shown by gnome-shell --- This is for 3.34: https://errors.ubuntu.com/problem/b6069e75f805530e3c7722835d567cfdb84f2fec --- Happened during normal use of the desktop. ProblemType: CrashDistroRelease: Ubuntu 20.04 Package: gnome-shell 3.34.3-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair wl ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Feb 29 19:51:58 2020 DisplayManager: gdm3 ExecutablePath: /usr/lib/gnome-shell/gnome-shell-hotplug-sniffer InstallationDate: Installed on 2020-01-25 (35 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200117) ProcCmdline: /usr/lib/gnome-shell/gnome-shell-hotplug-sniffer RelatedPackageVersions: mutter-common 3.34.3-1ubuntu1 SegvAnalysis: Segfault happened at: 0x7f5f54fa6444 : movsbl (%rdi),%eax PC (0x7f5f54fa6444) ok source "(%rdi)" (0x) not located in a known VMA region (needed readable region)! destination "%eax" ok SegvReason: reading NULL VMA Signal: 11SourcePackage: gnome-shell StacktraceTop: g_str_hash () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_hash_table_lookup () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () ?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0 Title: gnome-shell-hotplug-sniffer crashed with SIGSEGV in g_str_hash() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1865300/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1883920] Re: ubuntu logo in wslfetch needs update
This bug was fixed in the package wslu - 2.3.6-0ubuntu3 --- wslu (2.3.6-0ubuntu3) groovy; urgency=medium * debian/rules: - update the svg conversion commands for the current inkscape version and fix the build -- Patrick Wu Wed, 01 Jul 2020 16:07:10 +0200 ** Changed in: wslu (Ubuntu Groovy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wslu in Ubuntu. https://bugs.launchpad.net/bugs/1883920 Title: ubuntu logo in wslfetch needs update Status in wslu package in Ubuntu: Fix Released Status in wslu source package in Xenial: New Status in wslu source package in Bionic: New Status in wslu source package in Focal: New Status in wslu source package in Groovy: Fix Released Bug description: [Impact] This affects all wslu tools on all releases. The Ubuntu branding is the outdated version: https://cdn.patrickwu.space/garage/screenshots/Annotation2020-06-1814.png [Test Case] * Install Ubuntu WSL and install this fix. * run wslfetch command. * new logo should be shown like the following: https://cdn.patrickwu.space/garage/screenshots/Annotation2020-06-18111946.png [Regression Potential] * None for now. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wslu/+bug/1883920/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1885941] [NEW] Bug on boot
Public bug reported: See attached detailed file. Just started reporting internal system errors on boot up. Not sure why this has started - don't think I've installed anything recently to spark it off but there was a system update recently. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3.1 ProcVersionSignature: Ubuntu 4.4.0-184.214-generic 4.4.223 Uname: Linux 4.4.0-184-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.23 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 Jul 1 18:06:26 2020 DistUpgraded: 2020-05-30 23:46:52,273 DEBUG icon theme changed, re-reading DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Mobile 4 Series Chipset Integrated Graphics Controller [1025:013c] Subsystem: Acer Incorporated [ALI] Mobile 4 Series Chipset Integrated Graphics Controller [1025:013c] InstallationDate: Installed on 2020-05-30 (31 days ago) InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 (20160217.1) MachineType: Acer Extensa 5630 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-184-generic root=UUID=7db4d8a4-7f23-45ec-99b9-fd99f55368aa ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to xenial on 2020-05-30 (31 days ago) dmi.bios.date: 12/05/2008 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: V1.25 dmi.board.name: Homa dmi.board.vendor: Acer dmi.board.version: Rev dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvrV1.25:bd12/05/2008:svnAcer:pnExtensa5630:pvr0100:rvnAcer:rnHoma:rvrRev:cvnAcer:ct10:cvrN/A: dmi.product.name: Extensa 5630 dmi.product.version: 0100 dmi.sys.vendor: Acer 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 2:1.18.4-0ubuntu0.8 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: Wed Jul 1 17:25:18 2020 xserver.configfile: default xserver.errors: /dev/dri/card0: failed to set DRM interface version 1.4: Permission denied /dev/dri/card0: failed to set DRM interface version 1.4: Permission denied xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id5460 vendor CMO xserver.version: 2:1.18.4-0ubuntu0.8 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 ubuntu xenial -- 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/1885941 Title: Bug on boot Status in xorg package in Ubuntu: New Bug description: See attached detailed file. Just started reporting internal system errors on boot up. Not sure why this has started - don't think I've installed anything recently to spark it off but there was a system update recently. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3.1 ProcVersionSignature: Ubuntu 4.4.0-184.214-generic 4.4.223 Uname: Linux 4.4.0-184-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.23 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 Jul 1 18:06:26 2020 DistUpgraded: 2020-05-30 23:46:52,273 DEBUG icon theme changed, re-reading DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Mobile 4 Series Chipset Integrated Graphics Controller [1025:013c] Subsystem
[Desktop-packages] [Bug 1883497] Re: Only timing mode list in EDID supported on continuous freq monitors
** Description changed: [Impact] Some new laptop display set EDID continuous freq bit 1. Then Xorg only uses the timing modes defined in EDID, no other modes are shown on Xorg. Upstream Bug: https://gitlab.freedesktop.org/drm/intel/-/issues/313 Fix of Xorg in merge request: https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/421 https://cgit.freedesktop.org/xorg/xserver/commit/?id=6a79a737e2c0bc730ee693b4ea4a1530c108be4e + this is required to support new laptop models which use such panels + [Test case] Test that a proper list of modes is shown with a panel that uses the new EDID. [Regression potential] - should be low at this point + The patch retains the previous code path for setting modes on GTF-able monitors, and only adds support for non-GTF monitors. So in that sense there shouldn't be any regression potential, this has been reviewed by an upstream expert. -- 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/1883497 Title: Only timing mode list in EDID supported on continuous freq monitors Status in HWE Next: New Status in X.Org X server: New Status in xf86-video-intel: Unknown Status in xorg-server package in Ubuntu: New Status in xorg-server source package in Focal: New Bug description: [Impact] Some new laptop display set EDID continuous freq bit 1. Then Xorg only uses the timing modes defined in EDID, no other modes are shown on Xorg. Upstream Bug: https://gitlab.freedesktop.org/drm/intel/-/issues/313 Fix of Xorg in merge request: https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/421 https://cgit.freedesktop.org/xorg/xserver/commit/?id=6a79a737e2c0bc730ee693b4ea4a1530c108be4e this is required to support new laptop models which use such panels [Test case] Test that a proper list of modes is shown with a panel that uses the new EDID. [Regression potential] The patch retains the previous code path for setting modes on GTF-able monitors, and only adds support for non-GTF monitors. So in that sense there shouldn't be any regression potential, this has been reviewed by an upstream expert. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1883497/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1876510] Re: Print window too big for a 1366x768 screen
*** This bug is a duplicate of bug 1883886 *** https://bugs.launchpad.net/bugs/1883886 ** This bug has been marked a duplicate of bug 1883886 Print dialogue's height in Libreoffice Writer is too high to see and click buttons. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1876510 Title: Print window too big for a 1366x768 screen Status in libreoffice package in Ubuntu: Confirmed Bug description: On libreoffice write the window displayed for print is too big for a standard laptop screen 1366x768 so some important buttons are not visible and print can't be done see attachment ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libreoffice-core 1:6.4.2-0ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat May 2 20:54:16 2020 ExecutablePath: /usr/lib/libreoffice/program/soffice.bin InstallationDate: Installed on 2020-04-24 (8 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1876510/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1883886] Re: Print dialogue's height in Libreoffice Writer is too high to see and click buttons.
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: libreoffice (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1883886 Title: Print dialogue's height in Libreoffice Writer is too high to see and click buttons. Status in LibreOffice: Fix Released Status in libreoffice package in Ubuntu: Confirmed Bug description: Hello, I have the bug that is denoted here https://ask.libreoffice.org/en/question/240651/print-dialogue-too- large-to-select-ok-to-print/ and here https://bugs.documentfoundation.org/show_bug.cgi?id=127782#c67. Essentially, the libreoffice writer print's dialog box is too high for me to view and press the buttons with the mouse. A workaround is to just press ENTER to print. Please see the following screenshot for an example: https://snipboard.io/vc1X0f.jpg My information is as follows: Results of lsb_release -rd Description: Ubuntu 20.04 LTS Release: 20.04 Results of apt-cache policy libreoffice-writer libreoffice-writer: Installed: 1:6.4.3-0ubuntu0.20.04.1 Candidate: 1:6.4.3-0ubuntu0.20.04.1 Version table: *** 1:6.4.3-0ubuntu0.20.04.1 500 500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:6.4.2-0ubuntu3 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages Just FYI in case it is necessary: I am using Lubuntu 20.04 LTS with LXQt. Best regards, Owen Charles ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libreoffice-writer 1:6.4.3-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: LXQt Date: Wed Jun 17 12:47:56 2020 InstallationDate: Installed on 2020-06-05 (11 days ago) InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1883886/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1884761] Re: instead of the unix standard x-clipboard paste, middle click initiates scroll mode
You can disable that behavior in Tools > Options > LibreOffice > View. ** Changed in: libreoffice (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1884761 Title: instead of the unix standard x-clipboard paste, middle click initiates scroll mode Status in libreoffice package in Ubuntu: Invalid Bug description: when trying to paste the x-selection into a libreoffice writer window, a strange and pretty useless scroll mode appears instead with a small circular mouse pointer shape with two arrows. imho libreoffice should respect the unix/linux/x11 tradition where middle click was always meant for x-clipboard pasting. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libreoffice 1:6.4.3-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Tue Jun 23 14:04:25 2020 InstallationDate: Installed on 2018-01-29 (876 days ago) InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105) SourcePackage: libreoffice UpgradeStatus: Upgraded to focal on 2020-04-21 (63 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1884761/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
