[Desktop-packages] [Bug 2056506] Re: ubuntu-dock 89 crashes on gnome-shell 45 with signal 6 when right clicking on the dock [clutter_actor_dispose: assertion failed: (priv->parent == NULL)]
I'm not sure if this is the same exact bug, my problem just seems to happen randomly not when necessarily when I close something, I'm still trying to identify a reproducible cause. My problem seems more similar to https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension- ubuntu-dock/+bug/2056633 but it is marked as a duplicate of this, so I'm posting my debug journalctl.txt info here. ** Attachment added: "journal.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/2056506/+attachment/5772540/+files/journal.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/2056506 Title: ubuntu-dock 89 crashes on gnome-shell 45 with signal 6 when right clicking on the dock [clutter_actor_dispose: assertion failed: (priv->parent == NULL)] Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Fix Released Bug description: I'm using Noble for sometime and I'm having a very annoying and odd problem: everytime I close an application on x11 (Wayland doesn't work any better) clicking with the right button in the dock and choosing "Quit" I got that screen saying that something went wrong and I need to close the session and start over. Please, let me know what logs do you need. I couldn't find any meaningful information by myself. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/2056506/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2064037] [NEW] GDM session crashes after returning from a screen-off.
Public bug reported: I've written an AskUbuntu question about this: https://askubuntu.com/questions/1511958/screen-lock-keeps-occuring- on-24-04-even-though-i-believe-ive-disabled-it/1512075#1512075 Originally I thought it was gnome not respecting my setting to prevent locking the screen after idling, but after discussing the issue on matrix (https://matrix.to/#/!EJhpCQHHqqcNicfiql:xentonix.net/$kPbn- fqDZgoG4s6PyQfki8tcSKJUpGH9QrXZSSV_vKY?via=decred.org=matrix.org=ubuntu.com) I think it is actually just a gdm or gnome-shell crash that happens when the PC idles, the screen turns off, and then I wake it. To summarize the symptom. I have the PC set to disable the screen after being idle for 5 minutes. I also set it such that it should not lock the session when this happens. (I want to turn on the screen and get right back to where I was without password overhead). What I've observed is that when I give the idle PC keyboard input, it wakes to a login screen, and when I login my windows from the previous session are completely gone (although tmux sessions are still alive). I've attached a relevant section of `journalctl --user` from around the time when I last tried to interact with the idle PC. I believe the "wake" event happens at `Apr 28 13:42:43` at which point we start seeing whoopsie messages: ``` Apr 28 13:42:44 toothbrush systemd[1]: Started whoopsie.service - crash report submission. ``` And then what looks like logs indicating that I was logged out and the previous session was ended: ``` Apr 28 13:42:56 toothbrush systemd[1]: run-user-1000-gvfs.mount: Deactivated successfully. Apr 28 13:42:57 toothbrush gdm-password][60731]: pam_unix(gdm-password:session): session closed for user joncrall Apr 28 13:42:57 toothbrush systemd[1]: session-61.scope: Deactivated successfully. Apr 28 13:42:57 toothbrush systemd[1]: session-61.scope: Consumed 12min 9.467s CPU time. Apr 28 13:42:57 toothbrush systemd-logind[1790]: Session 61 logged out. Waiting for processes to exit. Apr 28 13:42:57 toothbrush systemd-logind[1790]: Removed session 61. ``` The time from `13:42:44` to `13:43:07` where I get: ``` Apr 28 13:43:07 toothbrush systemd-logind[1790]: New session 221 of user joncrall. Apr 28 13:43:07 toothbrush systemd[1]: Started session-221.scope - Session 221 of User joncrall. ``` seems about right, because it takes a few seconds to go from de-idling the machine to seeing any sort of display. System Information: No LSB modules are available. Description:Ubuntu 24.04 LTS Release:24.04 # System Details Report --- ## Report details - **Date generated:** 2024-04-28 15:17:36 ## Hardware Information: - **Hardware Model:** ASUS ROG STRIX Z590-E GAMING WIFI - **Memory:** 128.0 GiB - **Processor:** 11th Gen Intel® Core™ i9-11900K × 16 - **Graphics:**NVIDIA GeForce RTX™ 3090 - **Graphics 1:** NVIDIA GeForce RTX™ 3090 - **Disk Capacity:** 45.0 TB ## Software Information: - **Firmware Version:**0232 - **OS Name:** Ubuntu 24.04 LTS - **OS Build:**(null) - **OS Type:** 64-bit - **GNOME Version:** 46 - **Windowing System:**X11 - **Kernel Version:** Linux 6.8.0-31-generic Nvidia versions: NVIDIA-SMI 535.171.04 Driver Version: 535.171.04 CUDA Version: 12.2 ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: gdm3 46.0-2ubuntu1 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Apr 28 15:04:13 2024 InstallationDate: Installed on 2024-04-25 (3 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.gdm3.custom.conf: 2024-04-25T18:50:53.891514 ** Affects: gdm3 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble ** Attachment added: "Journalctl logs" https://bugs.launchpad.net/bugs/2064037/+attachment/5772117/+files/journalctl_logs.log -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/2064037 Title: GDM session crashes after returning from a screen-off. Status in gdm3 package in Ubuntu: New Bug description: I've written an AskUbuntu question about this: https://askubuntu.com/questions/1511958/screen-lock-keeps-occuring-
[Desktop-packages] [Bug 2063970] Re: Enhanced tiling orange shading that indicates what a window will resize to will persist even after I'm done with the adjustment.
I've confirmed it does happen when just using super+arrow and no mouse interaction. I still cannot get it to work reliably though. My monitor setup looks roughly like this: ``` +--+ |2 | +--+ | | |1 | +--+ | | +--+ | | |3 | | | | | | | +--+ +--+ ``` In one test, I was moving a window in monitor 3, and after pressing super+down the orange box appeared across the bottom of monitor 2, which is kinda weird. -- 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/2063970 Title: Enhanced tiling orange shading that indicates what a window will resize to will persist even after I'm done with the adjustment. Status in gnome-shell package in Ubuntu: New Bug description: I've got a fresh install of the first 24.04 release, and I'm seeing strange behavior related to super+arrow keys and the enhanced tiling. I've disabled tiling popups and tiling groups, but I like the quad blocks. The issue is when I'm moving around windows, sometimes the orange shading that indicates what a window will resize to will persist even after I'm done with the adjustment. I'm not sure how to reproduce yet, but it's happened several times. Not sure if I'll be able to take a screenshot or not. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: gnome-shell 46.0-0ubuntu5 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Apr 27 16:06:49 2024 DisplayManager: gdm3 InstallationDate: Installed on 2024-04-25 (2 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) RelatedPackageVersions: mutter-common 46.0-1ubuntu9 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2063970/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2063970] Re: Enhanced tiling orange shading that indicates what a window will resize to will persist even after I'm done with the adjustment.
I was able to get a screenshot of the issue. I edited the images to remove sensitive information I was working with at the time, but the point is that I was moving around windows (I forget if I was using super+arrow or dragging to corners), and the issue happened. I'm still not sure exactly how to reproduce, but this at least provides some illustration of what is happening. Also note. I have 3 monitors. Two are in landscape and 1 is in portrait. Nothing of interest was in the other monitors. I'll also note I'm using nvidia graphics. I have an RTX 3090 driving the 3 monitors. ** Attachment added: "Screenshot of issue where orange overlay does not go away" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2063970/+attachment/5771713/+files/gnome-shell-bug-reproduction.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2063970 Title: Enhanced tiling orange shading that indicates what a window will resize to will persist even after I'm done with the adjustment. Status in gnome-shell package in Ubuntu: New Bug description: I've got a fresh install of the first 24.04 release, and I'm seeing strange behavior related to super+arrow keys and the enhanced tiling. I've disabled tiling popups and tiling groups, but I like the quad blocks. The issue is when I'm moving around windows, sometimes the orange shading that indicates what a window will resize to will persist even after I'm done with the adjustment. I'm not sure how to reproduce yet, but it's happened several times. Not sure if I'll be able to take a screenshot or not. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: gnome-shell 46.0-0ubuntu5 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Apr 27 16:06:49 2024 DisplayManager: gdm3 InstallationDate: Installed on 2024-04-25 (2 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) RelatedPackageVersions: mutter-common 46.0-1ubuntu9 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2063970/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2063970] [NEW] Enhanced tiling orange shading that indicates what a window will resize to will persist even after I'm done with the adjustment.
Public bug reported: I've got a fresh install of the first 24.04 release, and I'm seeing strange behavior related to super+arrow keys and the enhanced tiling. I've disabled tiling popups and tiling groups, but I like the quad blocks. The issue is when I'm moving around windows, sometimes the orange shading that indicates what a window will resize to will persist even after I'm done with the adjustment. I'm not sure how to reproduce yet, but it's happened several times. Not sure if I'll be able to take a screenshot or not. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: gnome-shell 46.0-0ubuntu5 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Apr 27 16:06:49 2024 DisplayManager: gdm3 InstallationDate: Installed on 2024-04-25 (2 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) RelatedPackageVersions: mutter-common 46.0-1ubuntu9 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble -- 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/2063970 Title: Enhanced tiling orange shading that indicates what a window will resize to will persist even after I'm done with the adjustment. Status in gnome-shell package in Ubuntu: New Bug description: I've got a fresh install of the first 24.04 release, and I'm seeing strange behavior related to super+arrow keys and the enhanced tiling. I've disabled tiling popups and tiling groups, but I like the quad blocks. The issue is when I'm moving around windows, sometimes the orange shading that indicates what a window will resize to will persist even after I'm done with the adjustment. I'm not sure how to reproduce yet, but it's happened several times. Not sure if I'll be able to take a screenshot or not. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: gnome-shell 46.0-0ubuntu5 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Apr 27 16:06:49 2024 DisplayManager: gdm3 InstallationDate: Installed on 2024-04-25 (2 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) RelatedPackageVersions: mutter-common 46.0-1ubuntu9 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2063970/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2060575] Re: gnome-keyring fails to automatically unlock login keyring after recent updates in noble
I can confirm the behaviour after a recent upgrade from mantic to noble and has also been reported in https://discourse.ubuntu.com/t/noble-dev- branch-why-does-the-keyring-stay-locked-upon-login-also-why-did-apt- install-work-but-apt-upgrade-fail/43979 Another oddity is, that I seem to have to type the password twice into the second, non-overlay password prompt, which has me type my password four times for a complete login. This may also be connected to recent changes about how the ssh-agent is initialised, which may or may not involve problems with the Keyring or the new GCR. (Does anybody know what the abbreviation means? Its readme stays silent about it.) - https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/2061288 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/2060575 Title: gnome-keyring fails to automatically unlock login keyring after recent updates in noble Status in gnome-keyring package in Ubuntu: Triaged Bug description: After installing recent updates in 24.04, upon logging in the gnome- shell based UI pops up saying that the login keyring was not unlocked and asking for the users password to be input to unlock it. Similarly a second, non-gnome-shell based UI is also present asking the same thing. Will try and get a screenshot to attach. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: libpam-gnome-keyring 46.1-2build1 ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1 Uname: Linux 6.8.0-22-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Apr 9 06:16:46 2024 InstallationDate: Installed on 2021-08-03 (980 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210802) RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: gnome-keyring UpgradeStatus: Upgraded to noble on 2024-01-31 (68 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/2060575/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2061288] [NEW] Multiple conflicting SSH agents and SSH_AUTH_SOCK not set after upgrade to noble
Public bug reported: After upgrading mantic to noble, there are multiple SSH agents who are independently trying to set SSH_AUTH_SOCK, none of which is successful. 1. ~/.config/autostart/gnome-keyring-ssh.desktop (identical to /etc/xdg/autostart/gnome-keyring-ssh.desktop, if not modified) This will start the regular GNOME Keyring SSH Agent. It will set the Agent location to /run/user/1000/ssh, while the Socket is initialised at /run/user/1000/.ssh 2. If that one is not running, the user unit ssh-agent.service kicks in. It sets the Socket to live at /run/user/1000/openssh_agent 3. Parallely, there is also a GPG agent emulating SSH support gpg-agent- ssh.socket Socket at /run/user/1000/gnupg/S.gpg-agent.ssh 4. There is also the (new?) user unit gcr-ssh-agent.socket It sets its Socket to live at /run/user/1000/gcr/ssh --- The last one seems to be preferred by GNOME upstream nowadays, but also comes with caveats, as its unit does not set the SSH_AUTH_SOCK variable. This commit from !137 (see below) does not seem to be included in /usr/lib/systemd/user/gcr-ssh-agent.socket - https://gitlab.gnome.org/GNOME/gcr/-/commit/b12cc639949c4b548d84625b292a2aff1faaf195 Apparently it's solved upstream with the gcr 4.2.1 release. Installed is 4.2.0-4build1 There are discussions about how this is possibly resolved in - https://gitlab.gnome.org/GNOME/gnome-build-meta/-/issues/770 closed - https://gitlab.gnome.org/GNOME/gnome-build-meta/-/merge_requests/2623 open - https://gitlab.gnome.org/GNOME/gcr/-/issues/55 closed - https://gitlab.gnome.org/GNOME/gcr/-/merge_requests/137 merged - https://gitlab.gnome.org/GNOME/gcr/-/merge_requests/138 closed - https://gitlab.gnome.org/GNOME/gcr/-/merge_requests/139 reverts 137 Similar regressions around GCR (What does that abbreviation even mean? It's not explained in the readme) are described in the following, including other possible workarounds: - https://www.adamsdesk.com/posts/fix-gnome-keyring-ssh-auth-sock/ - https://bbs.archlinux.org/viewtopic.php?id=292403 ** Affects: gnome-keyring (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/2061288 Title: Multiple conflicting SSH agents and SSH_AUTH_SOCK not set after upgrade to noble Status in gnome-keyring package in Ubuntu: New Bug description: After upgrading mantic to noble, there are multiple SSH agents who are independently trying to set SSH_AUTH_SOCK, none of which is successful. 1. ~/.config/autostart/gnome-keyring-ssh.desktop (identical to /etc/xdg/autostart/gnome-keyring-ssh.desktop, if not modified) This will start the regular GNOME Keyring SSH Agent. It will set the Agent location to /run/user/1000/ssh, while the Socket is initialised at /run/user/1000/.ssh 2. If that one is not running, the user unit ssh-agent.service kicks in. It sets the Socket to live at /run/user/1000/openssh_agent 3. Parallely, there is also a GPG agent emulating SSH support gpg- agent-ssh.socket Socket at /run/user/1000/gnupg/S.gpg-agent.ssh 4. There is also the (new?) user unit gcr-ssh-agent.socket It sets its Socket to live at /run/user/1000/gcr/ssh --- The last one seems to be preferred by GNOME upstream nowadays, but also comes with caveats, as its unit does not set the SSH_AUTH_SOCK variable. This commit from !137 (see below) does not seem to be included in /usr/lib/systemd/user/gcr-ssh-agent.socket - https://gitlab.gnome.org/GNOME/gcr/-/commit/b12cc639949c4b548d84625b292a2aff1faaf195 Apparently it's solved upstream with the gcr 4.2.1 release. Installed is 4.2.0-4build1 There are discussions about how this is possibly resolved in - https://gitlab.gnome.org/GNOME/gnome-build-meta/-/issues/770 closed - https://gitlab.gnome.org/GNOME/gnome-build-meta/-/merge_requests/2623 open - https://gitlab.gnome.org/GNOME/gcr/-/issues/55 closed - https://gitlab.gnome.org/GNOME/gcr/-/merge_requests/137 merged - https://gitlab.gnome.org/GNOME/gcr/-/merge_requests/138 closed - https://gitlab.gnome.org/GNOME/gcr/-/merge_requests/139 reverts 137 Similar regressions around GCR (What does that abbreviation even mean? It's not explained in the readme) are described in the following, including other possible workarounds: - https://www.adamsdesk.com/posts/fix-gnome-keyring-ssh-auth-sock/ - https://bbs.archlinux.org/viewtopic.php?id=292403 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/2061288/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1715749] Re: Intermittent black screen on HP EliteBook 840 G1
This bug still exists on Ubuntu 23.10. HP Elitebook 840 G1. inxi -Fxz System: Kernel: 6.5.0-21-generic arch: x86_64 bits: 64 compiler: N/A Desktop: GNOME v: 45.2 Distro: Ubuntu 23.10 (Mantic Minotaur) Machine: Type: Laptop System: Hewlett-Packard product: HP EliteBook 840 G1 v: A3009DD10303 serial: Mobo: Hewlett-Packard model: 198F v: KBC Version 15.59 serial: BIOS: Hewlett-Packard v: L71 Ver. 01.46 date: 07/20/2018 Battery: ID-1: BAT0 charge: 42.8 Wh (94.7%) condition: 45.2/45.2 Wh (100.0%) volts: 13.0 min: 11.4 model: Hewlett-Packard Primary status: charging CPU: Info: dual core model: Intel Core i5-4300U bits: 64 type: MT MCP arch: Haswell rev: 1 cache: L1: 128 KiB L2: 512 KiB L3: 3 MiB Speed (MHz): avg: 2622 high: 2708 min/max: 800/2900 cores: 1: 2594 2: 2594 3: 2594 4: 2708 bogomips: 19952 Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx Graphics: Device-1: Intel Haswell-ULT Integrated Graphics vendor: Hewlett-Packard driver: i915 v: kernel arch: Gen-7.5 bus-ID: 00:02.0 Device-2: Cheng Uei Precision Industry (Foxlink) HP HD Webcam driver: uvcvideo type: USB bus-ID: 2-7:3 Display: wayland server: X.Org v: 1.23.2 with: Xwayland v: 23.2.0 compositor: gnome-shell driver: X: loaded: modesetting unloaded: fbdev,vesa dri: crocus gpu: i915 resolution: 1280x720~60Hz API: OpenGL v: 4.6 Mesa 23.2.1-1ubuntu3.1 renderer: Mesa Intel HD Graphics 4400 (HSW GT2) direct-render: Yes Audio: Device-1: Intel Haswell-ULT HD Audio vendor: Hewlett-Packard driver: snd_hda_intel v: kernel bus-ID: 00:03.0 Device-2: Intel 8 Series HD Audio vendor: Hewlett-Packard 8 driver: snd_hda_intel v: kernel bus-ID: 00:1b.0 API: ALSA v: k6.5.0-21-generic status: kernel-api Server-1: PipeWire v: 0.3.79 status: active Network: Device-1: Intel Ethernet I218-LM vendor: Hewlett-Packard driver: e1000e v: kernel port: 3080 bus-ID: 00:19.0 IF: enp0s25 state: down mac: Device-2: Intel Wireless 7260 driver: iwlwifi v: kernel bus-ID: 02:00.0 IF: wlo1 state: up mac: IF-ID-1: docker0 state: down mac: Bluetooth: Device-1: Intel Bluetooth wireless interface driver: btusb v: 0.8 type: USB bus-ID: 2-3.2:4 Report: hciconfig ID: hci0 rfk-id: 0 state: up address: bt-v: 4.0 lmp-v: 6 Drives: Local Storage: total: 119.24 GiB used: 72.01 GiB (60.4%) ID-1: /dev/sda vendor: Samsung model: MZ7PC128HAFU-000H1 size: 119.24 GiB Partition: ID-1: / size: 116.52 GiB used: 72.01 GiB (61.8%) fs: ext4 dev: /dev/sda4 Swap: ID-1: swap-1 type: file size: 4 GiB used: 127.2 MiB (3.1%) file: /swap.img Sensors: System Temperatures: cpu: 47.0 C mobo: N/A Fan Speeds (rpm): N/A Info: Processes: 268 Uptime: 2h 29m Memory: total: 8 GiB available: 7.65 GiB used: 5.26 GiB (68.8%) Init: systemd target: graphical (5) Compilers: gcc: 13.2.0 Packages: 2038 Shell: Bash v: 5.2.15 inxi: 3.3.29 -- 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/1715749 Title: Intermittent black screen on HP EliteBook 840 G1 Status in xorg package in Ubuntu: Expired Bug description: Once every couple hours, the internal laptop display goes black for a few seconds. This was reproducible: + With the laptop connected to a port replicator and the external display connected into the port replicator DP port via DP-DVI adapter. The external display remains on during this time. + With the laptop not connected into a port replicator but connected to an external display. The external display remains on during this time. + With the laptop not connected to either a port replicator or an external display. The hard disk was originally installed with Ubuntu MATE 14.10 in a HP EliteBook 6930p, upgraded to 15.04, 15.10 and eventually 16.04 and finally moved to the EliteBook 840 G1. The problem started immediately after the drive move. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79 Uname: Linux 4.4.0-93-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CurrentDesktop: MATE Date: Fri Sep 8 00:53:24 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2014-12-09 (1002 days ago) InstallationMedia: Ubuntu MATE 14.10 "Utopic Unicorn" - amd64 (20141023) SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: MATE DistUpgraded: Fresh install DistroCodename: xenial DistroRelease: Ubuntu 16.04 DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b)
[Desktop-packages] [Bug 2039235] Re: gnome-online-accounts -> when signing into google account, infinite loading after entering password
Same for me but some details that can be usefull to know : - Using a workspace email = evrything is fine - Using a personal google email = i have the endless loading problem (for workspace i've used the "add a GOOGLE account" button) Not too familiar with what .txt file to psot and how to do so... lmk if i can do anything -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/2039235 Title: gnome-online-accounts -> when signing into google account, infinite loading after entering password Status in gnome-online-accounts package in Ubuntu: Confirmed Bug description: 1) What you expected to happen - sign in is successful, which will allow google services to populate the appropriate applications (calendar, mail, google drive) 2) What actually happened - sign in hangs infinitely after entering the password - the process is able to detect that the password is correct or incorrect. When entering an incorrect password, it will correctly and quickly complain that the password is incorrect. When entering the correct password, the bug will occur. 3) Steps to reproduce a) start the program b) select online accounts c) select google d) enter email e) enter password f) loads forever ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-online-accounts 3.48.0-2 ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3 Uname: Linux 6.5.0-9-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Oct 12 22:27:59 2023 InstallationDate: Installed on 2023-10-12 (0 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Release amd64 (20231011) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: gnome-online-accounts UpgradeStatus: No upgrade log present (probably fresh install) Hardware info (not sure if relevant): cpu: intel gpu: nvidia (driver version: "Using NVIDIA driver metapackage from nvidia-driver-535(proprietary, tested)") To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/2039235/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2039092] [NEW] Gnome hangs on activity overview. Did the alt+f2 r workaround, but sent this bug report first.
Public bug reported: I did the alt+f2 r workaround, but sent this bug report first. Hopefully this system debugging information helps the team resolve the issue. It happens frequently. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.9-0ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-33.33~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-33-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown Date: Wed Oct 11 12:43:50 2023 DisplayManager: gdm3 InstallationDate: Installed on 2021-04-11 (913 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: mutter-common 42.9-0ubuntu5 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy third-party-packages ** Description changed: I did the alt+f2 r workaround, but sent this bug report first. Hopefully - this helps resolve the issue. It happens frequently. + this system debugging information helps the team resolve the issue. It + happens frequently. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.9-0ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-33.33~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-33-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown Date: Wed Oct 11 12:43:50 2023 DisplayManager: gdm3 InstallationDate: Installed on 2021-04-11 (913 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: mutter-common 42.9-0ubuntu5 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2039092 Title: Gnome hangs on activity overview. Did the alt+f2 r workaround, but sent this bug report first. Status in gnome-shell package in Ubuntu: New Bug description: I did the alt+f2 r workaround, but sent this bug report first. Hopefully this system debugging information helps the team resolve the issue. It happens frequently. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.9-0ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-33.33~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-33-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown Date: Wed Oct 11 12:43:50 2023 DisplayManager: gdm3 InstallationDate: Installed on 2021-04-11 (913 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: mutter-common 42.9-0ubuntu5 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2039092/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1828107] Re: gvfs can't list shares from smb servers that disabled SMB1
The SMB1 code should be entirely removed from the stack. It’s insecure and deprecated everywhere. On Tue, May 2, 2023 at 8:56 AM BloodyIron <1828...@bugs.launchpad.net> wrote: > Upgraded to Ubuntu 23.04 and the issue persists... Will this ever get > fixed? This is now over 4 years old. > > -- > You received this bug notification because you are subscribed to a > duplicate bug report (1881780). > https://bugs.launchpad.net/bugs/1828107 > > Title: > gvfs can't list shares from smb servers that disabled SMB1 > > Status in gvfs: > New > Status in gvfs package in Ubuntu: > Triaged > > Bug description: > After bug #1778322 is fixed (just needs a gvfs rebuild with newer > samba), samba machines will start to show up again in the "windows > network" tab in nautilus. But if a server has disabled the SMB1 > protocol, nautilus will show an error when that server is clicked on, > instead of showing the shares list. > > Even with SMB1 disabled, it should still be technically possible to > get a share list, since smbclient can do it: > > andreas@nsnx:~$ nmblookup -A 192.168.122.101 > Looking up status of 192.168.122.101 > D-NO-SMB1 <00> - B > D-NO-SMB1 <03> - B > D-NO-SMB1 <20> - B > ..__MSBROWSE__. <01> - B > WORKGROUP <00> - B > WORKGROUP <1d> - B > WORKGROUP <1e> - B > > MAC Address = 00-00-00-00-00-00 > > andreas@nsnx:~$ smbclient -L 192.168.122.101 -N > WARNING: The "syslog" option is deprecated > > Sharename Type Comment > - --- > print$ Disk Printer Drivers > pub_no_smb1 Disk > IPC$IPC IPC Service (d-no-smb1 server (Samba, > Ubuntu)) > Reconnecting with SMB1 for workgroup listing. > protocol negotiation failed: NT_STATUS_INVALID_NETWORK_RESPONSE > Failed to connect with SMB1 -- no workgroup available > > andreas@nsnx:~$ smbclient //192.168.122.101/pub_no_smb1 -U > ubuntu%ubuntu -m NT1 > WARNING: The "syslog" option is deprecated > protocol negotiation failed: NT_STATUS_INVALID_NETWORK_RESPONSE > > andreas@nsnx:~$ smbclient //192.168.122.101/pub_no_smb1 -U > ubuntu%ubuntu -m SMB2 > WARNING: The "syslog" option is deprecated > Try "help" to get a list of possible commands. > smb: \> dir > . D0 Fri May 3 18:16:38 > 2019 > .. D0 Fri May 3 18:15:24 > 2019 > hello.txt N 21 Fri May 3 18:16:12 > 2019 > hello-from-nsnx.txt A9 Fri May 3 18:16:38 > 2019 > > 20509264 blocks of size 1024. 13121800 blocks > available > > To manage notifications about this bug go to: > https://bugs.launchpad.net/gvfs/+bug/1828107/+subscriptions > > -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1828107 Title: gvfs can't list shares from smb servers that disabled SMB1 Status in gvfs: New Status in gvfs package in Ubuntu: Triaged Bug description: After bug #1778322 is fixed (just needs a gvfs rebuild with newer samba), samba machines will start to show up again in the "windows network" tab in nautilus. But if a server has disabled the SMB1 protocol, nautilus will show an error when that server is clicked on, instead of showing the shares list. Even with SMB1 disabled, it should still be technically possible to get a share list, since smbclient can do it: andreas@nsnx:~$ nmblookup -A 192.168.122.101 Looking up status of 192.168.122.101 D-NO-SMB1 <00> - B D-NO-SMB1 <03> - B D-NO-SMB1 <20> - B ..__MSBROWSE__. <01> - B WORKGROUP <00> - B WORKGROUP <1d> - B WORKGROUP <1e> - B MAC Address = 00-00-00-00-00-00 andreas@nsnx:~$ smbclient -L 192.168.122.101 -N WARNING: The "syslog" option is deprecated Sharename Type Comment - --- print$ Disk Printer Drivers pub_no_smb1 Disk IPC$IPC IPC Service (d-no-smb1 server (Samba, Ubuntu)) Reconnecting with SMB1 for workgroup listing. protocol negotiation failed: NT_STATUS_INVALID_NETWORK_RESPONSE Failed to connect with SMB1 -- no workgroup available andreas@nsnx:~$ smbclient //192.168.122.101/pub_no_smb1 -U ubuntu%ubuntu -m NT1 WARNING: The "syslog" option is deprecated protocol negotiation failed: NT_STATUS_INVALID_NETWORK_RESPONSE andreas@nsnx:~$ smbclient //192.168.122.101/pub_no_smb1 -U ubuntu%ubuntu -m SMB2 WARNING: The "syslog" option is deprecated Try "help" to get a list of possible commands.
[Desktop-packages] [Bug 1715749] Re: Intermittent black screen on HP EliteBook 840 G1
Update -- possibly resolved by upgrading to kubuntu 22.10. I installed that and so far ... fingers crossed, no more black screens. Jon -- 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/1715749 Title: Intermittent black screen on HP EliteBook 840 G1 Status in xorg package in Ubuntu: Confirmed Bug description: Once every couple hours, the internal laptop display goes black for a few seconds. This was reproducible: + With the laptop connected to a port replicator and the external display connected into the port replicator DP port via DP-DVI adapter. The external display remains on during this time. + With the laptop not connected into a port replicator but connected to an external display. The external display remains on during this time. + With the laptop not connected to either a port replicator or an external display. The hard disk was originally installed with Ubuntu MATE 14.10 in a HP EliteBook 6930p, upgraded to 15.04, 15.10 and eventually 16.04 and finally moved to the EliteBook 840 G1. The problem started immediately after the drive move. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79 Uname: Linux 4.4.0-93-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CurrentDesktop: MATE Date: Fri Sep 8 00:53:24 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2014-12-09 (1002 days ago) InstallationMedia: Ubuntu MATE 14.10 "Utopic Unicorn" - amd64 (20141023) SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: MATE DistUpgraded: Fresh install DistroCodename: xenial DistroRelease: Ubuntu 16.04 DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Haswell-ULT Integrated Graphics Controller [103c:198f] InstallationDate: Installed on 2014-12-09 (1158 days ago) InstallationMedia: Ubuntu MATE 14.10 "Utopic Unicorn" - amd64 (20141023) MachineType: Hewlett-Packard HP EliteBook 840 G1 Package: xorg 1:7.7+13ubuntu3 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-112-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98 Tags: xenial ubuntu Uname: Linux 4.4.0-112-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/23/2016 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: L71 Ver. 01.37 dmi.board.name: 198F dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 15.59 dmi.chassis.asset.tag: CNU407CM0V dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrL71Ver.01.37:bd05/23/2016:svnHewlett-Packard:pnHPEliteBook840G1:pvrA3009DD10203:rvnHewlett-Packard:rn198F:rvrKBCVersion15.59:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP EliteBook 840 G1 dmi.product.version: A3009DD10203 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.83-1~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~16.04.4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.4 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1715749/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1715749] Re: Intermittent black screen on HP EliteBook 840 G1
I have the same issue with a fresh install of kubuntu 22.04 LTS on an HP 820 G1. Random screen blackout -- machine can only be revived by a reboot. The Windows operating system that was replaced by kubuntu worked flawlessly (except that it was Windows, which is one hell of a flaw). -- 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/1715749 Title: Intermittent black screen on HP EliteBook 840 G1 Status in xorg package in Ubuntu: Confirmed Bug description: Once every couple hours, the internal laptop display goes black for a few seconds. This was reproducible: + With the laptop connected to a port replicator and the external display connected into the port replicator DP port via DP-DVI adapter. The external display remains on during this time. + With the laptop not connected into a port replicator but connected to an external display. The external display remains on during this time. + With the laptop not connected to either a port replicator or an external display. The hard disk was originally installed with Ubuntu MATE 14.10 in a HP EliteBook 6930p, upgraded to 15.04, 15.10 and eventually 16.04 and finally moved to the EliteBook 840 G1. The problem started immediately after the drive move. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79 Uname: Linux 4.4.0-93-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CurrentDesktop: MATE Date: Fri Sep 8 00:53:24 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2014-12-09 (1002 days ago) InstallationMedia: Ubuntu MATE 14.10 "Utopic Unicorn" - amd64 (20141023) SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: MATE DistUpgraded: Fresh install DistroCodename: xenial DistroRelease: Ubuntu 16.04 DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Haswell-ULT Integrated Graphics Controller [103c:198f] InstallationDate: Installed on 2014-12-09 (1158 days ago) InstallationMedia: Ubuntu MATE 14.10 "Utopic Unicorn" - amd64 (20141023) MachineType: Hewlett-Packard HP EliteBook 840 G1 Package: xorg 1:7.7+13ubuntu3 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-112-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98 Tags: xenial ubuntu Uname: Linux 4.4.0-112-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/23/2016 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: L71 Ver. 01.37 dmi.board.name: 198F dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 15.59 dmi.chassis.asset.tag: CNU407CM0V dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrL71Ver.01.37:bd05/23/2016:svnHewlett-Packard:pnHPEliteBook840G1:pvrA3009DD10203:rvnHewlett-Packard:rn198F:rvrKBCVersion15.59:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP EliteBook 840 G1 dmi.product.version: A3009DD10203 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.83-1~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~16.04.4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.4 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1715749/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 929447] Re: gnome-shell freezes when entering "overview"
This is probably caused by something different than the described issue, but I'm experiencing this symptom periodically on 22.04. I can still move my mouse around, but I can't exit the overview. I can ssh into the box, so it is some issue with gnome getting stuck. I submitted a report. -- 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/929447 Title: gnome-shell freezes when entering "overview" Status in gnome-shell package in Ubuntu: Fix Released Bug description: This is new as of today's updates in precise. Every so often (but frequently) gnome-shell with hang when accessing "overview". Dropping down to console and killing gnome-shell restarts it and I'm able to carry on. But it's damn frustrating ;) Happy to provide additional info, please just let me know what and how to get it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/929447/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1991015] [NEW] Reminna has unusable framerate when clipboard sync turned on
Public bug reported: On an intermittent basis, Remmina will, if clipboard sync is on, drop to an unusably low framerate after login to the remote machine. I have not managed to fully determine the conditions under which this occurs: it appears to happen or not happen consistently across a login session on the local machine (conditional upon clipboard sync being on), or possibly across a boot of the local machine. I have noticed it start occurring or stop occurring on reboots. When it occurs, it occurs for both remote machines I have set up (A Raspberry Pi 2 running Ubuntu Mate 18.04 and an x86 server running Debian Bullseye with LxQT). When it does not occur, it does not occur for either machine (this seems to include the case where clipboard sync has been turned off for one remote machine and not the other and the connections are open simultaneously, in which case the issue appears on neither!). The local machine is running Kubuntu 20.04, though some Mate components are also running on top of KDE. The connection is made via RDP, to xrdp v 0.6.x on the Raspberry Pi and xrdp 0.9.12 on the x86 server. All devices are in the same room, with gigabit ethernet connections. I have verified that I am getting gigabit bandwidth with iperf3, and ping latencies are sub-millisecond. Remmina is version 1.4.2+dfsg-1ubuntu1 ** Affects: remmina (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to remmina in Ubuntu. https://bugs.launchpad.net/bugs/1991015 Title: Reminna has unusable framerate when clipboard sync turned on Status in remmina package in Ubuntu: New Bug description: On an intermittent basis, Remmina will, if clipboard sync is on, drop to an unusably low framerate after login to the remote machine. I have not managed to fully determine the conditions under which this occurs: it appears to happen or not happen consistently across a login session on the local machine (conditional upon clipboard sync being on), or possibly across a boot of the local machine. I have noticed it start occurring or stop occurring on reboots. When it occurs, it occurs for both remote machines I have set up (A Raspberry Pi 2 running Ubuntu Mate 18.04 and an x86 server running Debian Bullseye with LxQT). When it does not occur, it does not occur for either machine (this seems to include the case where clipboard sync has been turned off for one remote machine and not the other and the connections are open simultaneously, in which case the issue appears on neither!). The local machine is running Kubuntu 20.04, though some Mate components are also running on top of KDE. The connection is made via RDP, to xrdp v 0.6.x on the Raspberry Pi and xrdp 0.9.12 on the x86 server. All devices are in the same room, with gigabit ethernet connections. I have verified that I am getting gigabit bandwidth with iperf3, and ping latencies are sub-millisecond. Remmina is version 1.4.2+dfsg-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/remmina/+bug/1991015/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1989239] Re: 20.04 LTS: Trackpad cursor on MacBook Pro freezes mid-motion
** Description changed: Reporting according to https://wiki.ubuntu.com/DebuggingTouchpadDetection , following section 4 Attaching: xinput output evtest output xev output xmodmap output live videos of evtest and xev showing physical motion on trackpad without cursor movement: https://drive.google.com/drive/folders/1q44ZO7GdvVU2VLg6HatNPj19hD_SjtYk?usp=sharing (videos may still be uploading / processing) Model: MacBook Pro A1278 2010 model + + Important: bug gets gradually worse until trackpad is no longer usable, + restart helps ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xserver-xorg-input-libinput 0.29.0-1 ProcVersionSignature: Ubuntu 5.15.0-46.49~20.04.1-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Sep 10 09:03:24 2022 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu InstallationDate: Installed on 2022-07-23 (48 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) MachineType: Apple Inc. MacBookPro8,1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic root=UUID=7a3fcdea-96d5-4ac7-942e-cf8967060e37 ro quiet splash vt.handoff=7 SourcePackage: xserver-xorg-input-libinput UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/10/18 dmi.bios.release: 0.1 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP81.88Z.0050.B00.1804101331 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-94245B3640C91C81 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro8,1 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-94245B3640C91C81 dmi.modalias: dmi:bvnAppleInc.:bvrMBP81.88Z.0050.B00.1804101331:bd04/10/18:br0.1:svnAppleInc.:pnMacBookPro8,1:pvr1.0:rvnAppleInc.:rnMac-94245B3640C91C81:rvrMacBookPro8,1:cvnAppleInc.:ct10:cvrMac-94245B3640C91C81:skuSystemSKU#: dmi.product.family: MacBook Pro dmi.product.name: MacBookPro8,1 dmi.product.sku: System SKU# dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.3 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 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-libinput in Ubuntu. https://bugs.launchpad.net/bugs/1989239 Title: 20.04 LTS: Trackpad cursor on MacBook Pro freezes mid-motion Status in xserver-xorg-input-libinput package in Ubuntu: New Bug description: Reporting according to https://wiki.ubuntu.com/DebuggingTouchpadDetection , following section 4 Attaching: xinput output evtest output xev output xmodmap output live videos of evtest and xev showing physical motion on trackpad without cursor movement: https://drive.google.com/drive/folders/1q44ZO7GdvVU2VLg6HatNPj19hD_SjtYk?usp=sharing (videos may still be uploading / processing) Model: MacBook Pro A1278 2010 model Important: bug gets gradually worse until trackpad is no longer usable, restart helps ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xserver-xorg-input-libinput 0.29.0-1 ProcVersionSignature: Ubuntu 5.15.0-46.49~20.04.1-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Sep 10 09:03:24 2022 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu InstallationDate: Installed on 2022-07-23 (48 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) MachineType: Apple Inc. MacBookPro8,1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic root=UUID=7a3fcdea-96d5-4ac7-942e-cf8967060e37 ro quiet splash vt.handoff=7 SourcePackage: xserver-xorg-input-libinput UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/10/18 dmi.bios.release: 0.1 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP81.88Z.0050.B00.1804101331 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-94245B3640C91C81 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro8,1
[Desktop-packages] [Bug 1989239] [NEW] 20.04 LTS: Trackpad cursor on MacBook Pro freezes mid-motion
Public bug reported: Reporting according to https://wiki.ubuntu.com/DebuggingTouchpadDetection , following section 4 Attaching: xinput output evtest output xev output xmodmap output live videos of evtest and xev showing physical motion on trackpad without cursor movement: https://drive.google.com/drive/folders/1q44ZO7GdvVU2VLg6HatNPj19hD_SjtYk?usp=sharing (videos may still be uploading / processing) Model: MacBook Pro A1278 2010 model ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xserver-xorg-input-libinput 0.29.0-1 ProcVersionSignature: Ubuntu 5.15.0-46.49~20.04.1-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Sep 10 09:03:24 2022 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu InstallationDate: Installed on 2022-07-23 (48 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) MachineType: Apple Inc. MacBookPro8,1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic root=UUID=7a3fcdea-96d5-4ac7-942e-cf8967060e37 ro quiet splash vt.handoff=7 SourcePackage: xserver-xorg-input-libinput UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/10/18 dmi.bios.release: 0.1 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP81.88Z.0050.B00.1804101331 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-94245B3640C91C81 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro8,1 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-94245B3640C91C81 dmi.modalias: dmi:bvnAppleInc.:bvrMBP81.88Z.0050.B00.1804101331:bd04/10/18:br0.1:svnAppleInc.:pnMacBookPro8,1:pvr1.0:rvnAppleInc.:rnMac-94245B3640C91C81:rvrMacBookPro8,1:cvnAppleInc.:ct10:cvrMac-94245B3640C91C81:skuSystemSKU#: dmi.product.family: MacBook Pro dmi.product.name: MacBookPro8,1 dmi.product.sku: System SKU# dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.3 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 ** Affects: xserver-xorg-input-libinput (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubuntu ** Attachment added: "xev, xmodmap, xinput, evtest" https://bugs.launchpad.net/bugs/1989239/+attachment/5614891/+files/bug.zip ** Description changed: Reporting according to https://wiki.ubuntu.com/DebuggingTouchpadDetection , following section 4 Attaching: xinput output evtest output xev output xmodmap output live videos of evtest and xev showing physical motion on trackpad without cursor movement: https://drive.google.com/drive/folders/1q44ZO7GdvVU2VLg6HatNPj19hD_SjtYk?usp=sharing (videos may still be uploading / processing) + + Model: MacBook Pro A1278 2010 model ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xserver-xorg-input-libinput 0.29.0-1 ProcVersionSignature: Ubuntu 5.15.0-46.49~20.04.1-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Sep 10 09:03:24 2022 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu InstallationDate: Installed on 2022-07-23 (48 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) MachineType: Apple Inc. MacBookPro8,1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic root=UUID=7a3fcdea-96d5-4ac7-942e-cf8967060e37 ro quiet splash vt.handoff=7 SourcePackage: xserver-xorg-input-libinput UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/10/18 dmi.bios.release: 0.1 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP81.88Z.0050.B00.1804101331 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-94245B3640C91C81 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro8,1 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-94245B3640C91C81 dmi.modalias: dmi:bvnAppleInc.:bvrMBP81.88Z.0050.B00.1804101331:bd04/10/18:br0.1:svnAppleInc.:pnMacBookPro8,1:pvr1.0:rvnAppleInc.:rnMac-94245B3640C91C81:rvrMacBookPro8,1:cvnAppleInc.:ct10:cvrMac-94245B3640C91C81:skuSystemSKU#: dmi.product.family: MacBook
[Desktop-packages] [Bug 1972080] Re: GNOME (non-Ubuntu) login screen mouse cursor is a semi-opaque white square (missing adwaita-icon-theme-full)
Removal of the package 'sabily-gdm-themes' and rebooting had no effect on my situation. Daniel, perhaps you have some insight into this. What information I've found in my internet search says that gdm/gdm3 defaults to Adwaita icon theme. I'm looked for "how to configure" type articles about gdm and none have been applicable or have had not effect. Do you know how to reconfigure gdm in Ubuntu 22.04? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1972080 Title: GNOME (non-Ubuntu) login screen mouse cursor is a semi-opaque white square (missing adwaita-icon-theme-full) Status in gdm3 package in Ubuntu: New Status in gnome-shell package in Ubuntu: New Bug description: Do not think this is hardware dependent, but I'm using an HPE MicroServer Gen10 Plus. I installed the server edition of 22.04. Post-Installation, I added some desktop environments. After logging in, these are working fine. However on the gdm login entry and password entry screens I had no mouse pointer icon. A semi-opaque white square tracked the mouse movements. My reading suggested that gdm defaults to using the cursor icon theme provided by the adwaita-icon-theme package. I discovered this theme comes in two sizes, a basic, smaller package installed automatically and a larger "full" package. $ apt list 'adwaita-icon-theme*' Listing... Done adwaita-icon-theme/jammy,now 41.0-1ubuntu1 all [installed,automatic] adwaita-icon-theme-full/jammy,now 41.0-1ubuntu1 all [installed] $ The gdm mouse pointer appears and disappears with installation and removal of the package "adwaita-icon-theme-full". Either gdm's dependencies should include the "full" package OR the appropriate mouse pointer icons should be moved from the full to the basic "adwaita-icon-theme" package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1972080/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1972080] Re: [mgag200] Mouse cursor is a semi-opaque white square
Adding MUTTER_DEBUG_DISABLE_HW_CURSORS=1 to /etc/environment and rebooting had no effect on the issue. White square "mouse pointer" is present on gdm login screen if /usr/share/icons/adwaita/cursors is missing (renamed). If instead I install a symbolic link .../Adwaita/cursors -> .../Yaru/cursors and restart gdm I get valid mouse pointers. gdm is clearly looking for its cursor files in the Adwaita theme directory rather than Yaru. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1972080 Title: [mgag200] Mouse cursor is a semi-opaque white square Status in linux package in Ubuntu: Incomplete Status in mutter package in Ubuntu: New Bug description: Do not think this is hardware dependent, but I'm using an HPE MicroServer Gen10 Plus. I installed the server edition of 22.04. Post-Installation, I added some desktop environments. After logging in, these are working fine. However on the gdm login entry and password entry screens I had no mouse pointer icon. A semi-opaque white square tracked the mouse movements. My reading suggested that gdm defaults to using the cursor icon theme provided by the adwaita-icon-theme package. I discovered this theme comes in two sizes, a basic, smaller package installed automatically and a larger "full" package. $ apt list 'adwaita-icon-theme*' Listing... Done adwaita-icon-theme/jammy,now 41.0-1ubuntu1 all [installed,automatic] adwaita-icon-theme-full/jammy,now 41.0-1ubuntu1 all [installed] $ The gdm mouse pointer appears and disappears with installation and removal of the package "adwaita-icon-theme-full". Either gdm's dependencies should include the "full" package OR the appropriate mouse pointer icons should be moved from the full to the basic "adwaita-icon-theme" package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1972080/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1972080] Re: [mgag200] Mouse cursor is a semi-opaque white square
The reported problem is during login, not after successful login. I don't think mutter configuration has any effect before graphical login. Ubuntu's cursor theme may come from 'yaru-theme-icon', but does gdm's? Two files affect the observed condition: /usr/share/icons/Adwaita/cursors/left_ptr /usr/share/icons/Adwaita/cursors/xterm These come from the package 'adwaita-theme-icon-full'. If the package is not installed I have no login screen mouse pointer. Install the package and the pointer appears. Leave the package installed and deleted the two above files and the pointer is gone. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1972080 Title: [mgag200] Mouse cursor is a semi-opaque white square Status in linux package in Ubuntu: Incomplete Status in mutter package in Ubuntu: New Bug description: Do not think this is hardware dependent, but I'm using an HPE MicroServer Gen10 Plus. I installed the server edition of 22.04. Post-Installation, I added some desktop environments. After logging in, these are working fine. However on the gdm login entry and password entry screens I had no mouse pointer icon. A semi-opaque white square tracked the mouse movements. My reading suggested that gdm defaults to using the cursor icon theme provided by the adwaita-icon-theme package. I discovered this theme comes in two sizes, a basic, smaller package installed automatically and a larger "full" package. $ apt list 'adwaita-icon-theme*' Listing... Done adwaita-icon-theme/jammy,now 41.0-1ubuntu1 all [installed,automatic] adwaita-icon-theme-full/jammy,now 41.0-1ubuntu1 all [installed] $ The gdm mouse pointer appears and disappears with installation and removal of the package "adwaita-icon-theme-full". Either gdm's dependencies should include the "full" package OR the appropriate mouse pointer icons should be moved from the full to the basic "adwaita-icon-theme" package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1972080/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1798166] Re: “Mouse battery low” notification can't be disabled
I'm using Ubuntu 20.04.4 LTS and GNOME 3.36.8 Still having this problem. Very surprised it has lasted this long. In any case, if it is fixed, will this change make it to the next LTS update? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1798166 Title: “Mouse battery low” notification can't be disabled Status in gnome-settings-daemon package in Ubuntu: Confirmed Status in linux package in Ubuntu: Invalid Bug description: https://gitlab.gnome.org/GNOME/gnome-settings-daemon/issues/108 --- I have a wireless mouse powered by non-rechargeable battery. The mouse works absolutely fine even with low battery level. Problem is, Ubuntu gives notifications about the battery level all the time. I have had this issue for almost two months now, and mouse is working perfectly. I had to click away the notification almost every time I moved the mouse. I was then able to make the notifications appear less frequently, but the notification still always appear after some interval, and always after I log in. Here are some specific things I have tried, they have not helped. https://askubuntu.com/questions/1071406/how-to-disable-mouse-battery- low-notification-in-ubuntu-18-04 1) Description: Ubuntu 18.04.1 LTS Release: 18.04 2) I assume the packet in question is notify-osd, not sure. notify-osd: Installed: (none) Candidate: 0.9.35+16.04.20160415-0ubuntu2 Version table: 0.9.35+16.04.20160415-0ubuntu2 500 500 http://fi.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages 3) I expected that no notifications would appear when notifications are set to off 4) Mouse battery low - notification always appears --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: ohto 2927 F...m pulseaudio /dev/snd/controlC0: ohto 2927 F pulseaudio /dev/snd/controlC1: ohto 2927 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-07-28 (79 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic root=UUID=a59cc41b-0147-4609-b6c5-75fa912d2396 ro quiet splash vt.handoff=1 ProcVersionSignature: hostname 4.15.0-36.39-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-36-generic N/A linux-backports-modules-4.15.0-36-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-36-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/15/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F12 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z77X-UP5 TH-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF12:bd05/15/2014:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ77X-UP5TH-CF:rvrTobefilledbyO.E.M.:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1798166/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1811724] Re: libbd_mdraid.so.2: cannot open shared object file
Same on Ubuntu 20.04 both GA and HWE kernel. Sure, it just takes this command to find which package has it: $ apt-file search libbd_mdraid.so.2 And get "libblockdev-mdraid2", which does "fix" it, but I DON'T need it. Depends on packages I don't need, MOST don't need: $ apt show libblockdev-mdraid2 Depends: libblockdev-utils2 (>= 2.20), libbytesize1 (>= 2.1), libc6 (>= 2.27), libglib2.0-0 (>= 2.42.2), mdadm (>= 3.3.2) However it's the same on Raspbian for the Raspberry Pi, so it's more of a Debian problem. And installing that package then wants exim4 and all... A mail server?? For a library? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to udisks2 in Ubuntu. https://bugs.launchpad.net/bugs/1811724 Title: libbd_mdraid.so.2: cannot open shared object file Status in udisks2 package in Ubuntu: Confirmed Bug description: Had some (probably unrelated?) trouble typing input into login console, and went looking through /var/log/syslog : found Jan 14 21:10:21 vps39184 udisksd[611]: udisks daemon version 2.8.1 starting Jan 14 21:10:22 vps39184 udisksd[611]: failed to load module mdraid: libbd_mdraid.so.2: cannot open shared object file: No such file or directory Jan 14 21:10:22 vps39184 udisksd[611]: Failed to load the 'mdraid' libblockdev plugin Seems to give this warning every time I boot. udisks2: Installed: 2.8.1-3 Candidate: 2.8.1-3 ubuntu: 19.04 disco ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: udisks2 2.8.1-3 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu18 Architecture: amd64 CustomUdevRuleFiles: 80-net-setup-link.rules Date: Mon Jan 14 21:31:52 2019 Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: Red Hat KVM ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: root=/dev/vda1 ro vga16fb.modeset=0 quiet splash SourcePackage: udisks2 UpgradeStatus: Upgraded to disco on 2018-11-23 (52 days ago) dmi.bios.date: 01/01/2007 dmi.bios.vendor: Seabios dmi.bios.version: 0.5.1 dmi.chassis.type: 1 dmi.chassis.vendor: Red Hat dmi.modalias: dmi:bvnSeabios:bvr0.5.1:bd01/01/2007:svnRedHat:pnKVM:pvrRHEL6.6.0PC:cvnRedHat:ct1:cvr: dmi.product.family: Red Hat Enterprise Linux dmi.product.name: KVM dmi.product.version: RHEL 6.6.0 PC dmi.sys.vendor: Red Hat To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/udisks2/+bug/1811724/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1930640] Re: Error when using S3 multipart upload - TypeError: cannot use a string pattern on a bytes-like object
Confirmed everything appears to be working. We can consider this closed. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to duplicity in Ubuntu. https://bugs.launchpad.net/bugs/1930640 Title: Error when using S3 multipart upload - TypeError: cannot use a string pattern on a bytes-like object Status in Duplicity: In Progress Status in duplicity package in Ubuntu: New Bug description: I followed the solution in https://bugs.launchpad.net/ubuntu/+source/duplicity/+bug/1908971 (I was running duplicity 0.8.11.1612-1 as well), but after upgrading to 0.8.19, the problem still persists for me when trying to use S3 multipart uploads. Note: This problem doesn't appear to exist in duplicity 0.7.17 running on python2.7, which is making me wonder if this is a python3.8 related issue. user@host:~$ lsb_release -rd Description: Ubuntu 20.04.2 LTS Release: 20.04 user@host:~$ apt-cache policy duplicity duplicity: Installed: 0.8.19-ppa202104291804~ubuntu20.04.1 Candidate: 0.8.19-ppa202104291804~ubuntu20.04.1 Version table: *** 0.8.19-ppa202104291804~ubuntu20.04.1 500 500 http://ppa.launchpad.net/duplicity-team/duplicity-release-git/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status 0.8.11.1612-1 500 500 http://us-west-2.ec2.archive.ubuntu.com/ubuntu focal/main amd64 Packages Start duply v2.2, time is 2021-06-02 22:58:11. Using profile '/root/.duply/artifactory_backup'. Using installed duplicity version 0.8.19, python 3.8.5 (/usr/bin/python3), gpg 2.2.19 (Home: /root/.gnupg), awk 'GNU Awk 5.0.1, API: 2.0 (GNU MPFR 4.0.2, GNU MP 6.2.0)', grep 'grep (GNU grep) 3.4', bash '5.0.17(1)-release (x86_64-pc-linux-gnu)'. Checking TEMP_DIR '/tmp' is a folder and writable (OK) Test - En/Decryption skipped. (GPG disabled) --- Start running command PRE at 22:58:11.550 --- Skipping n/a script '/root/.duply/artifactory_backup/pre'. --- Finished state OK at 22:58:11.563 - Runtime 00:00:00.013 --- --- Start running command BKP at 22:58:11.595 --- Using archive dir: /root/.cache/duplicity/duply_artifactory_backup Using backup name: duply_artifactory_backup GPG binary is gpg, version (2, 2, 19) Import of duplicity.backends.adbackend Succeeded Import of duplicity.backends.azurebackend Succeeded Import of duplicity.backends.b2backend Succeeded Import of duplicity.backends.boxbackend Failed: No module named 'boxsdk' Import of duplicity.backends.cfbackend Succeeded Import of duplicity.backends.dpbxbackend Succeeded Import of duplicity.backends.gdocsbackend Succeeded Import of duplicity.backends.gdrivebackend Succeeded Import of duplicity.backends.giobackend Succeeded Import of duplicity.backends.hsibackend Succeeded Import of duplicity.backends.hubicbackend Succeeded Import of duplicity.backends.idrivedbackend Succeeded Import of duplicity.backends.imapbackend Succeeded Import of duplicity.backends.jottacloudbackend Succeeded Import of duplicity.backends.lftpbackend Succeeded Import of duplicity.backends.localbackend Succeeded Import of duplicity.backends.mediafirebackend Succeeded Import of duplicity.backends.megabackend Succeeded Import of duplicity.backends.megav2backend Succeeded Import of duplicity.backends.megav3backend Succeeded Import of duplicity.backends.multibackend Succeeded Import of duplicity.backends.ncftpbackend Succeeded Import of duplicity.backends.onedrivebackend Succeeded Import of duplicity.backends.par2backend Succeeded Import of duplicity.backends.pcabackend Succeeded Import of duplicity.backends.pydrivebackend Succeeded Import of duplicity.backends.rclonebackend Succeeded Import of duplicity.backends.rsyncbackend Succeeded Import of duplicity.backends.s3_boto3_backend Succeeded Multiprocessing is not supported on linux, will use threads instead. Import of duplicity.backends.s3_boto_backend Succeeded Import of duplicity.backends.ssh_paramiko_backend Succeeded Import of duplicity.backends.ssh_pexpect_backend Succeeded Import of duplicity.backends.swiftbackend Succeeded Import of duplicity.backends.sxbackend Succeeded Import of duplicity.backends.tahoebackend Succeeded Import of duplicity.backends.webdavbackend Succeeded Setting multipart boto backend process pool to 4 processes Reading globbing filelist /root/.duply/artifactory_backup/exclude Main action: inc Acquiring lockfile b'/root/.cache/duplicity/duply_artifactory_backup/lockfile' duplicity 0.8.19 Args: /usr/bin/duplicity --name duply_artifactory_backup --no-encryption --verbosity 9 --full-if-older-than 7D --volsize 1024 --s3-use-multiprocessing --s3-multipart-chunk-size 512 --allow-source-mismatch --exclude-filelist /root/.duply/artifactory_backup/exclude /MyDirectory
[Desktop-packages] [Bug 1930640] Re: Error when using S3 multipart upload - TypeError: cannot use a string pattern on a bytes-like object
After a little more digging, I believe part of my issue with the boto3+s3 option was that I was still using the full URL rather than just the bucket name, so rather than: boto3+s3://BUCKET_NAME/folder I was still using: boto3+s3://s3-us-west-2.amazonaws.com/BUCKET_NAME/folder So this appears to be working and I'm seeing files show up in S3 and nothing has produced an error so far after six hours (and counting) of backing up. Although it's still weird that the old S3 URL of s3://s3-us- west-2.amazonaws.com/BUCKET_NAME/folder that works in the 0.7.19 version of Duplicity with Python 2.7 was able to use the old S3 URL, but the new one on 0.8.19 (and 0.8.11) didn't seem to jive with it. But since the boto3+s3://bucket_name works with the multipart chunking, I'll just stick with this instead. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to duplicity in Ubuntu. https://bugs.launchpad.net/bugs/1930640 Title: Error when using S3 multipart upload - TypeError: cannot use a string pattern on a bytes-like object Status in Duplicity: In Progress Status in duplicity package in Ubuntu: New Bug description: I followed the solution in https://bugs.launchpad.net/ubuntu/+source/duplicity/+bug/1908971 (I was running duplicity 0.8.11.1612-1 as well), but after upgrading to 0.8.19, the problem still persists for me when trying to use S3 multipart uploads. Note: This problem doesn't appear to exist in duplicity 0.7.17 running on python2.7, which is making me wonder if this is a python3.8 related issue. user@host:~$ lsb_release -rd Description: Ubuntu 20.04.2 LTS Release: 20.04 user@host:~$ apt-cache policy duplicity duplicity: Installed: 0.8.19-ppa202104291804~ubuntu20.04.1 Candidate: 0.8.19-ppa202104291804~ubuntu20.04.1 Version table: *** 0.8.19-ppa202104291804~ubuntu20.04.1 500 500 http://ppa.launchpad.net/duplicity-team/duplicity-release-git/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status 0.8.11.1612-1 500 500 http://us-west-2.ec2.archive.ubuntu.com/ubuntu focal/main amd64 Packages Start duply v2.2, time is 2021-06-02 22:58:11. Using profile '/root/.duply/artifactory_backup'. Using installed duplicity version 0.8.19, python 3.8.5 (/usr/bin/python3), gpg 2.2.19 (Home: /root/.gnupg), awk 'GNU Awk 5.0.1, API: 2.0 (GNU MPFR 4.0.2, GNU MP 6.2.0)', grep 'grep (GNU grep) 3.4', bash '5.0.17(1)-release (x86_64-pc-linux-gnu)'. Checking TEMP_DIR '/tmp' is a folder and writable (OK) Test - En/Decryption skipped. (GPG disabled) --- Start running command PRE at 22:58:11.550 --- Skipping n/a script '/root/.duply/artifactory_backup/pre'. --- Finished state OK at 22:58:11.563 - Runtime 00:00:00.013 --- --- Start running command BKP at 22:58:11.595 --- Using archive dir: /root/.cache/duplicity/duply_artifactory_backup Using backup name: duply_artifactory_backup GPG binary is gpg, version (2, 2, 19) Import of duplicity.backends.adbackend Succeeded Import of duplicity.backends.azurebackend Succeeded Import of duplicity.backends.b2backend Succeeded Import of duplicity.backends.boxbackend Failed: No module named 'boxsdk' Import of duplicity.backends.cfbackend Succeeded Import of duplicity.backends.dpbxbackend Succeeded Import of duplicity.backends.gdocsbackend Succeeded Import of duplicity.backends.gdrivebackend Succeeded Import of duplicity.backends.giobackend Succeeded Import of duplicity.backends.hsibackend Succeeded Import of duplicity.backends.hubicbackend Succeeded Import of duplicity.backends.idrivedbackend Succeeded Import of duplicity.backends.imapbackend Succeeded Import of duplicity.backends.jottacloudbackend Succeeded Import of duplicity.backends.lftpbackend Succeeded Import of duplicity.backends.localbackend Succeeded Import of duplicity.backends.mediafirebackend Succeeded Import of duplicity.backends.megabackend Succeeded Import of duplicity.backends.megav2backend Succeeded Import of duplicity.backends.megav3backend Succeeded Import of duplicity.backends.multibackend Succeeded Import of duplicity.backends.ncftpbackend Succeeded Import of duplicity.backends.onedrivebackend Succeeded Import of duplicity.backends.par2backend Succeeded Import of duplicity.backends.pcabackend Succeeded Import of duplicity.backends.pydrivebackend Succeeded Import of duplicity.backends.rclonebackend Succeeded Import of duplicity.backends.rsyncbackend Succeeded Import of duplicity.backends.s3_boto3_backend Succeeded Multiprocessing is not supported on linux, will use threads instead. Import of duplicity.backends.s3_boto_backend Succeeded Import of duplicity.backends.ssh_paramiko_backend Succeeded Import of duplicity.backends.ssh_pexpect_backend Succeeded Import of duplicity.backends.swiftbackend Succeeded Import of duplicity.backends.sxbackend Succeeded Import of
[Desktop-packages] [Bug 1930640] Re: Error when using S3 multipart upload - TypeError: cannot use a string pattern on a bytes-like object
No funny characters in the bucket name. It's literally just alpha characters and dashes: labkey-artifactory- backup And the folder it drops into uses an underscore: artifactory_backup I'll recheck that link. There were a few that I already saw, but were not applicable to my situation. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to duplicity in Ubuntu. https://bugs.launchpad.net/bugs/1930640 Title: Error when using S3 multipart upload - TypeError: cannot use a string pattern on a bytes-like object Status in Duplicity: In Progress Status in duplicity package in Ubuntu: New Bug description: I followed the solution in https://bugs.launchpad.net/ubuntu/+source/duplicity/+bug/1908971 (I was running duplicity 0.8.11.1612-1 as well), but after upgrading to 0.8.19, the problem still persists for me when trying to use S3 multipart uploads. Note: This problem doesn't appear to exist in duplicity 0.7.17 running on python2.7, which is making me wonder if this is a python3.8 related issue. user@host:~$ lsb_release -rd Description: Ubuntu 20.04.2 LTS Release: 20.04 user@host:~$ apt-cache policy duplicity duplicity: Installed: 0.8.19-ppa202104291804~ubuntu20.04.1 Candidate: 0.8.19-ppa202104291804~ubuntu20.04.1 Version table: *** 0.8.19-ppa202104291804~ubuntu20.04.1 500 500 http://ppa.launchpad.net/duplicity-team/duplicity-release-git/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status 0.8.11.1612-1 500 500 http://us-west-2.ec2.archive.ubuntu.com/ubuntu focal/main amd64 Packages Start duply v2.2, time is 2021-06-02 22:58:11. Using profile '/root/.duply/artifactory_backup'. Using installed duplicity version 0.8.19, python 3.8.5 (/usr/bin/python3), gpg 2.2.19 (Home: /root/.gnupg), awk 'GNU Awk 5.0.1, API: 2.0 (GNU MPFR 4.0.2, GNU MP 6.2.0)', grep 'grep (GNU grep) 3.4', bash '5.0.17(1)-release (x86_64-pc-linux-gnu)'. Checking TEMP_DIR '/tmp' is a folder and writable (OK) Test - En/Decryption skipped. (GPG disabled) --- Start running command PRE at 22:58:11.550 --- Skipping n/a script '/root/.duply/artifactory_backup/pre'. --- Finished state OK at 22:58:11.563 - Runtime 00:00:00.013 --- --- Start running command BKP at 22:58:11.595 --- Using archive dir: /root/.cache/duplicity/duply_artifactory_backup Using backup name: duply_artifactory_backup GPG binary is gpg, version (2, 2, 19) Import of duplicity.backends.adbackend Succeeded Import of duplicity.backends.azurebackend Succeeded Import of duplicity.backends.b2backend Succeeded Import of duplicity.backends.boxbackend Failed: No module named 'boxsdk' Import of duplicity.backends.cfbackend Succeeded Import of duplicity.backends.dpbxbackend Succeeded Import of duplicity.backends.gdocsbackend Succeeded Import of duplicity.backends.gdrivebackend Succeeded Import of duplicity.backends.giobackend Succeeded Import of duplicity.backends.hsibackend Succeeded Import of duplicity.backends.hubicbackend Succeeded Import of duplicity.backends.idrivedbackend Succeeded Import of duplicity.backends.imapbackend Succeeded Import of duplicity.backends.jottacloudbackend Succeeded Import of duplicity.backends.lftpbackend Succeeded Import of duplicity.backends.localbackend Succeeded Import of duplicity.backends.mediafirebackend Succeeded Import of duplicity.backends.megabackend Succeeded Import of duplicity.backends.megav2backend Succeeded Import of duplicity.backends.megav3backend Succeeded Import of duplicity.backends.multibackend Succeeded Import of duplicity.backends.ncftpbackend Succeeded Import of duplicity.backends.onedrivebackend Succeeded Import of duplicity.backends.par2backend Succeeded Import of duplicity.backends.pcabackend Succeeded Import of duplicity.backends.pydrivebackend Succeeded Import of duplicity.backends.rclonebackend Succeeded Import of duplicity.backends.rsyncbackend Succeeded Import of duplicity.backends.s3_boto3_backend Succeeded Multiprocessing is not supported on linux, will use threads instead. Import of duplicity.backends.s3_boto_backend Succeeded Import of duplicity.backends.ssh_paramiko_backend Succeeded Import of duplicity.backends.ssh_pexpect_backend Succeeded Import of duplicity.backends.swiftbackend Succeeded Import of duplicity.backends.sxbackend Succeeded Import of duplicity.backends.tahoebackend Succeeded Import of duplicity.backends.webdavbackend Succeeded Setting multipart boto backend process pool to 4 processes Reading globbing filelist /root/.duply/artifactory_backup/exclude Main action: inc Acquiring lockfile b'/root/.cache/duplicity/duply_artifactory_backup/lockfile' duplicity 0.8.19 Args: /usr/bin/duplicity --name duply_artifactory_backup --no-encryption --verbosity 9
[Desktop-packages] [Bug 1930640] Re: Error when using S3 multipart upload - TypeError: cannot use a string pattern on a bytes-like object
I've tried using boto3+s3:// as well before and it was unsuccessful. Swapping it out with this newer version of duplicity produced an error regarding the HeadBucket operation. See new failure below. I turned up the verbosity to 9 for this one. Note: My company is using Duplicity 0.8.11 and Duply in other servers (Servers are running Ubuntu 20.04 w/Python 3.5.8) without issue. However, this particular machine is the only one where we needed to implement multipart chunks due to the size of the backup being so huge compared to our other servers that don't need it. I know that on a different server (Ubuntu 16.04) running Duplicity 0.7.19 on Python 2.7, the multipart chunking worked without issue, but since we can't run that version of Python or Duplicity on this newer version of Ubuntu, I'm not sure what else we need to do to get 0.8.19 to work here. Start duply v2.2, time is 2021-06-04 21:26:37. Using profile '/root/.duply/artifactory_backup'. Using installed duplicity version 0.8.19, python 3.8.5 (/usr/bin/python3), gpg 2.2.19 (Home: /root/.gnupg), awk 'GNU Awk 5.0.1, API: 2.0 (GNU MPFR 4.0.2, GNU MP 6.2.0)', grep 'grep (GNU grep) 3.4', bash '5.0.17(1)-rele ase (x86_64-pc-linux-gnu)'. Checking TEMP_DIR '/tmp' is a folder and writable (OK) Test - En/Decryption skipped. (GPG disabled) --- Start running command PRE at 21:26:37.615 --- Skipping n/a script '/root/.duply/artifactory_backup/pre'. --- Finished state OK at 21:26:37.628 - Runtime 00:00:00.012 --- --- Start running command BKP at 21:26:37.659 --- Using archive dir: /root/.cache/duplicity/duply_artifactory_backup Using backup name: duply_artifactory_backup GPG binary is gpg, version (2, 2, 19) Import of duplicity.backends.adbackend Succeeded Import of duplicity.backends.azurebackend Succeeded Import of duplicity.backends.b2backend Succeeded Import of duplicity.backends.boxbackend Succeeded Import of duplicity.backends.cfbackend Succeeded Import of duplicity.backends.dpbxbackend Succeeded Import of duplicity.backends.gdocsbackend Succeeded Import of duplicity.backends.gdrivebackend Succeeded Import of duplicity.backends.giobackend Succeeded Import of duplicity.backends.hsibackend Succeeded Import of duplicity.backends.hubicbackend Succeeded Import of duplicity.backends.idrivedbackend Succeeded Import of duplicity.backends.imapbackend Succeeded Import of duplicity.backends.jottacloudbackend Succeeded Import of duplicity.backends.lftpbackend Succeeded Import of duplicity.backends.localbackend Succeeded Import of duplicity.backends.mediafirebackend Succeeded Import of duplicity.backends.megabackend Succeeded Import of duplicity.backends.megav2backend Succeeded Import of duplicity.backends.megav3backend Succeeded Import of duplicity.backends.multibackend Succeeded Import of duplicity.backends.ncftpbackend Succeeded Import of duplicity.backends.onedrivebackend Succeeded Import of duplicity.backends.par2backend Succeeded Import of duplicity.backends.pcabackend Succeeded Import of duplicity.backends.pydrivebackend Succeeded Import of duplicity.backends.rclonebackend Succeeded Import of duplicity.backends.rsyncbackend Succeeded Import of duplicity.backends.s3_boto3_backend Succeeded Multiprocessing is not supported on linux, will use threads instead. Import of duplicity.backends.s3_boto_backend Succeeded Import of duplicity.backends.ssh_paramiko_backend Succeeded Import of duplicity.backends.ssh_pexpect_backend Succeeded Import of duplicity.backends.swiftbackend Succeeded Import of duplicity.backends.sxbackend Succeeded Import of duplicity.backends.tahoebackend Succeeded Import of duplicity.backends.webdavbackend Succeeded Reading globbing filelist /root/.duply/artifactory_backup/exclude Main action: inc Acquiring lockfile b'/root/.cache/duplicity/duply_artifactory_backup/lockfile' duplicity 0.8.19 Args: /usr/bin/duplicity --name duply_artifactory_backup --no-encryption --verbosity 9 --full-if-older-than 7D --volsize 1024 --s3-use-multiprocessing --s3-multipart-chunk-size 512 --allow-source-mismatch --exclude-filelist /root/.duply/artifactory_backup/exclude /labkey boto3+s3://s3-us-west-2.amazonaws.com/BUCKET-NAME/artifactory_backup Linux ip-172-30-115-92 5.4.0-1049-aws #51-Ubuntu SMP Wed May 12 21:13:52 UTC 2021 x86_64 x86_64 /usr/bin/python3 3.8.5 (default, May 27 2021, 13:30:53) [GCC 9.3.0] Using temporary directory /tmp/duplicity-_k91zmc2-tempdir Registering (mkstemp) temporary file /tmp/duplicity-_k91zmc2-tempdir/mkstemp-t1cl2e0h-1 Temp has 138928574464 available, backup will use approx 1395864371. Backtrace of previous error: Traceback (innermost last): File "/usr/lib/python3/dist-packages/duplicity/backend.py", line 384, in inner_retry return fn(self, *args) File "/usr/lib/python3/dist-packages/duplicity/backend.py", line 604, in list return
[Desktop-packages] [Bug 1930640] Re: Error when using S3 multipart upload - TypeError: cannot use a string pattern on a bytes-like object
Unfortunately, the same issue is coming up, even after installing the requirements via pip. Traceback (most recent call last): File "/usr/lib/python3/dist-packages/duplicity/backends/_boto_multi.py", line 223, in _upload mp.upload_part_from_file(fd, offset + 1, cb=_upload_callback, File "/usr/lib/python3/dist-packages/boto/s3/multipart.py", line 257, in upload_part_from_file key.set_contents_from_file(fp, headers=headers, replace=replace, File "/usr/lib/python3/dist-packages/boto/s3/key.py", line 1307, in set_contents_from_file self.send_file(fp, headers=headers, cb=cb, num_cb=num_cb, File "/usr/lib/python3/dist-packages/boto/s3/key.py", line 760, in send_file self._send_file_internal(fp, headers=headers, cb=cb, num_cb=num_cb, File "/usr/lib/python3/dist-packages/boto/s3/key.py", line 932, in _send_file_internal self.content_type = mimetypes.guess_type(self.path)[0] File "/usr/lib/python3.8/mimetypes.py", line 292, in guess_type return _db.guess_type(url, strict) File "/usr/lib/python3.8/mimetypes.py", line 117, in guess_type scheme, url = urllib.parse._splittype(url) File "/usr/lib/python3.8/urllib/parse.py", line 1008, in _splittype match = _typeprog.match(url) TypeError: cannot use a string pattern on a bytes-like object There were some errors in the install of packages via pip, but I don't think any of these would have caused this particular issue: ERROR: launchpadlib 1.10.13 requires testresources, which is not installed. ERROR: pyopenssl 20.0.1 has requirement cryptography>=3.2, but you'll have cryptography 2.8 which is incompatible. ERROR: mediafire 0.6.0 has requirement requests<=2.11.1,>=2.4.1, but you'll have requests 2.25.1 which is incompatible. ERROR: debtcollector 2.2.0 has requirement pbr!=2.1.0,>=2.0.0, but you'll have pbr 1.10.0 which is incompatible. ERROR: oslo-i18n 5.0.1 has requirement pbr!=2.1.0,>=2.0.0, but you'll have pbr 1.10.0 which is incompatible. ERROR: stevedore 3.3.0 has requirement pbr!=2.1.0,>=2.0.0, but you'll have pbr 1.10.0 which is incompatible. ERROR: oslo-utils 4.9.0 has requirement pbr!=2.1.0,>=2.0.0, but you'll have pbr 1.10.0 which is incompatible. ERROR: os-service-types 1.7.0 has requirement pbr!=2.1.0,>=2.0.0, but you'll have pbr 1.10.0 which is incompatible. ERROR: keystoneauth1 4.3.1 has requirement pbr!=2.1.0,>=2.0.0, but you'll have pbr 1.10.0 which is incompatible. ERROR: oslo-serialization 4.1.0 has requirement pbr!=2.1.0,>=2.0.0, but you'll have pbr 1.10.0 which is incompatible. ERROR: python-keystoneclient 4.2.0 has requirement pbr!=2.1.0,>=2.0.0, but you'll have pbr 1.10.0 which is incompatible. Shouldn't it also be urllib3 since the above is in python3.5.8? I do have the urllib3 package: pip3 install urllib3 Requirement already satisfied: urllib3 in /usr/lib/python3/dist-packages (1.25.8) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to duplicity in Ubuntu. https://bugs.launchpad.net/bugs/1930640 Title: Error when using S3 multipart upload - TypeError: cannot use a string pattern on a bytes-like object Status in duplicity package in Ubuntu: Incomplete Bug description: I followed the solution in https://bugs.launchpad.net/ubuntu/+source/duplicity/+bug/1908971 (I was running duplicity 0.8.11.1612-1 as well), but after upgrading to 0.8.19, the problem still persists for me when trying to use S3 multipart uploads. Note: This problem doesn't appear to exist in duplicity 0.7.17 running on python2.7, which is making me wonder if this is a python3.8 related issue. user@host:~$ lsb_release -rd Description: Ubuntu 20.04.2 LTS Release: 20.04 user@host:~$ apt-cache policy duplicity duplicity: Installed: 0.8.19-ppa202104291804~ubuntu20.04.1 Candidate: 0.8.19-ppa202104291804~ubuntu20.04.1 Version table: *** 0.8.19-ppa202104291804~ubuntu20.04.1 500 500 http://ppa.launchpad.net/duplicity-team/duplicity-release-git/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status 0.8.11.1612-1 500 500 http://us-west-2.ec2.archive.ubuntu.com/ubuntu focal/main amd64 Packages Start duply v2.2, time is 2021-06-02 22:58:11. Using profile '/root/.duply/artifactory_backup'. Using installed duplicity version 0.8.19, python 3.8.5 (/usr/bin/python3), gpg 2.2.19 (Home: /root/.gnupg), awk 'GNU Awk 5.0.1, API: 2.0 (GNU MPFR 4.0.2, GNU MP 6.2.0)', grep 'grep (GNU grep) 3.4', bash '5.0.17(1)-release (x86_64-pc-linux-gnu)'. Checking TEMP_DIR '/tmp' is a folder and writable (OK) Test - En/Decryption skipped. (GPG disabled) --- Start running command PRE at 22:58:11.550 --- Skipping n/a script '/root/.duply/artifactory_backup/pre'. --- Finished state OK at 22:58:11.563 - Runtime 00:00:00.013 --- --- Start running command BKP at 22:58:11.595 --- Using archive dir: /root/.cache/duplicity/duply_artifactory_backup Using backup name:
[Desktop-packages] [Bug 1908971] Re: TypeError: cannot use a string pattern on a bytes-like object
I ran into the same issue, but upgrading to 0.8.19 didn't fix it. I've put in a new bug for this: https://bugs.launchpad.net/ubuntu/+source/duplicity/+bug/1930640 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to duplicity in Ubuntu. https://bugs.launchpad.net/bugs/1908971 Title: TypeError: cannot use a string pattern on a bytes-like object Status in Duplicity: Fix Released Status in duplicity package in Ubuntu: New Bug description: user@host:~$ lsb_release -rd Description:Ubuntu 20.10 Release:20.10 user@host:~$ apt-cache policy duplicity duplicity: Installed: 0.8.11.1612-1 Candidate: 0.8.11.1612-1 Version table: *** 0.8.11.1612-1 500 500 http://nz.archive.ubuntu.com/ubuntu groovy/main amd64 Packages 100 /var/lib/dpkg/status user@host:~$ http_proxy= AWS_ACCESS_KEY_ID=[omitted-key-id] AWS_SECRET_ACCESS_KEY=[omitted-key] PASSPHRASE=[omitted-encryption-password] duplicity --s3-use-new-style --s3-use-ia --s3-use-multiprocessing --no-print-statistics --verbosity 1 --exclude-device-files --exclude-filelist [omitted-exclude-path] --include-filelist [omitted-include-path] --exclude '**' / [omitted-s3-storage-path] TypeError: cannot use a string pattern on a bytes-like object During handling of the above exception, another exception occurred: Traceback (most recent call last): ... ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: duplicity 0.8.11.1612-1 ProcVersionSignature: Ubuntu 5.8.0-33.36-lowlatency 5.8.17 Uname: Linux 5.8.0-33-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu50.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Tue Dec 22 16:37:45 2020 InstallationDate: Installed on 2020-11-19 (33 days ago) InstallationMedia: Kubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) ProcEnviron: LANGUAGE=en_NZ:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_NZ.UTF-8 SHELL=/bin/bash SourcePackage: duplicity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/duplicity/+bug/1908971/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1930640] [NEW] Error when using S3 multipart upload - TypeError: cannot use a string pattern on a bytes-like object
Public bug reported: I followed the solution in https://bugs.launchpad.net/ubuntu/+source/duplicity/+bug/1908971 (I was running duplicity 0.8.11.1612-1 as well), but after upgrading to 0.8.19, the problem still persists for me when trying to use S3 multipart uploads. Note: This problem doesn't appear to exist in duplicity 0.7.17 running on python2.7, which is making me wonder if this is a python3.8 related issue. user@host:~$ lsb_release -rd Description:Ubuntu 20.04.2 LTS Release:20.04 user@host:~$ apt-cache policy duplicity duplicity: Installed: 0.8.19-ppa202104291804~ubuntu20.04.1 Candidate: 0.8.19-ppa202104291804~ubuntu20.04.1 Version table: *** 0.8.19-ppa202104291804~ubuntu20.04.1 500 500 http://ppa.launchpad.net/duplicity-team/duplicity-release-git/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status 0.8.11.1612-1 500 500 http://us-west-2.ec2.archive.ubuntu.com/ubuntu focal/main amd64 Packages Start duply v2.2, time is 2021-06-02 22:58:11. Using profile '/root/.duply/artifactory_backup'. Using installed duplicity version 0.8.19, python 3.8.5 (/usr/bin/python3), gpg 2.2.19 (Home: /root/.gnupg), awk 'GNU Awk 5.0.1, API: 2.0 (GNU MPFR 4.0.2, GNU MP 6.2.0)', grep 'grep (GNU grep) 3.4', bash '5.0.17(1)-release (x86_64-pc-linux-gnu)'. Checking TEMP_DIR '/tmp' is a folder and writable (OK) Test - En/Decryption skipped. (GPG disabled) --- Start running command PRE at 22:58:11.550 --- Skipping n/a script '/root/.duply/artifactory_backup/pre'. --- Finished state OK at 22:58:11.563 - Runtime 00:00:00.013 --- --- Start running command BKP at 22:58:11.595 --- Using archive dir: /root/.cache/duplicity/duply_artifactory_backup Using backup name: duply_artifactory_backup GPG binary is gpg, version (2, 2, 19) Import of duplicity.backends.adbackend Succeeded Import of duplicity.backends.azurebackend Succeeded Import of duplicity.backends.b2backend Succeeded Import of duplicity.backends.boxbackend Failed: No module named 'boxsdk' Import of duplicity.backends.cfbackend Succeeded Import of duplicity.backends.dpbxbackend Succeeded Import of duplicity.backends.gdocsbackend Succeeded Import of duplicity.backends.gdrivebackend Succeeded Import of duplicity.backends.giobackend Succeeded Import of duplicity.backends.hsibackend Succeeded Import of duplicity.backends.hubicbackend Succeeded Import of duplicity.backends.idrivedbackend Succeeded Import of duplicity.backends.imapbackend Succeeded Import of duplicity.backends.jottacloudbackend Succeeded Import of duplicity.backends.lftpbackend Succeeded Import of duplicity.backends.localbackend Succeeded Import of duplicity.backends.mediafirebackend Succeeded Import of duplicity.backends.megabackend Succeeded Import of duplicity.backends.megav2backend Succeeded Import of duplicity.backends.megav3backend Succeeded Import of duplicity.backends.multibackend Succeeded Import of duplicity.backends.ncftpbackend Succeeded Import of duplicity.backends.onedrivebackend Succeeded Import of duplicity.backends.par2backend Succeeded Import of duplicity.backends.pcabackend Succeeded Import of duplicity.backends.pydrivebackend Succeeded Import of duplicity.backends.rclonebackend Succeeded Import of duplicity.backends.rsyncbackend Succeeded Import of duplicity.backends.s3_boto3_backend Succeeded Multiprocessing is not supported on linux, will use threads instead. Import of duplicity.backends.s3_boto_backend Succeeded Import of duplicity.backends.ssh_paramiko_backend Succeeded Import of duplicity.backends.ssh_pexpect_backend Succeeded Import of duplicity.backends.swiftbackend Succeeded Import of duplicity.backends.sxbackend Succeeded Import of duplicity.backends.tahoebackend Succeeded Import of duplicity.backends.webdavbackend Succeeded Setting multipart boto backend process pool to 4 processes Reading globbing filelist /root/.duply/artifactory_backup/exclude Main action: inc Acquiring lockfile b'/root/.cache/duplicity/duply_artifactory_backup/lockfile' duplicity 0.8.19 Args: /usr/bin/duplicity --name duply_artifactory_backup --no-encryption --verbosity 9 --full-if-older-than 7D --volsize 1024 --s3-use-multiprocessing --s3-multipart-chunk-size 512 --allow-source-mismatch --exclude-filelist /root/.duply/artifactory_backup/exclude /MyDirectory s3://s3-us-west-2.amazonaws.com/BUCKET-NAME/artifactory_backup Linux ip-172-30-115-92 5.4.0-1047-aws #49-Ubuntu SMP Wed Apr 28 22:47:04 UTC 2021 x86_64 x86_64 /usr/bin/python3 3.8.5 (default, May 27 2021, 13:30:53) [GCC 9.3.0] === Log errors: Attempt 4 failed. BackendException: Multipart upload failed. Aborted. Writing duplicity-full.20210602T225820Z.vol1.difftar.gz Uploading s3://s3-us-west-2.amazonaws.com/BUCKET-NAME/artifactory_backup/duplicity-full.20210602T225820Z.vol1.difftar.gz to STANDARD Storage Uploading 1073705932 bytes in 2 chunks Waiting for the pool to finish processing 2 tasks
[Desktop-packages] [Bug 1915984] [NEW] Disk Usage Analyzer no longer functions at all; freezes several seconds after start
Public bug reported: Disk Usage Analyzer no longer works at all; becomes unresponsive several seconds after starting ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: baobab 3.34.0-1 ProcVersionSignature: Ubuntu 5.8.0-43.49~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Feb 17 21:50:12 2021 InstallationDate: Installed on 2020-09-29 (141 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: baobab UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: baobab (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 baobab in Ubuntu. https://bugs.launchpad.net/bugs/1915984 Title: Disk Usage Analyzer no longer functions at all; freezes several seconds after start Status in baobab package in Ubuntu: New Bug description: Disk Usage Analyzer no longer works at all; becomes unresponsive several seconds after starting ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: baobab 3.34.0-1 ProcVersionSignature: Ubuntu 5.8.0-43.49~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Feb 17 21:50:12 2021 InstallationDate: Installed on 2020-09-29 (141 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: baobab UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/baobab/+bug/1915984/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1913613] Re: Second monitor is detected but has no signal
** Description changed: xrandr Screen 0: minimum 320 x 200, current 3840 x 1080, maximum 16384 x 16384 eDP connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 344mm x 194mm -1920x1080 59.93*+ 39.99 -1680x1050 59.93 -1280x1024 59.93 -1440x900 59.93 -1280x800 59.93 -1280x720 59.93 -1024x768 59.93 -800x600 59.93 -640x480 59.93 + 1920x1080 59.93*+ 39.99 + 1680x1050 59.93 + 1280x1024 59.93 + 1440x900 59.93 + 1280x800 59.93 + 1280x720 59.93 + 1024x768 59.93 + 800x600 59.93 + 640x480 59.93 HDMI-1-0 connected (normal left inverted right x axis y axis) -1920x1080 60.00 + 59.9450.00 -1680x1050 59.95 -1600x900 60.00 -1280x1024 75.0260.02 -1280x800 59.81 -1280x720 60.0059.9450.00 -1024x768 75.0360.00 -800x600 75.0060.32 -720x576 50.00 -720x480 59.94 -640x480 75.0059.9459.93 + 1920x1080 60.00 + 59.9450.00 + 1680x1050 59.95 + 1600x900 60.00 + 1280x1024 75.0260.02 + 1280x800 59.81 + 1280x720 60.0059.9450.00 + 1024x768 75.0360.00 + 800x600 75.0060.32 + 720x576 50.00 + 720x480 59.94 + 640x480 75.0059.9459.93 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.4.0-64.72~18.04.1-generic 5.4.78 Uname: Linux 5.4.0-64-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Es un directorio: '/proc/driver/nvidia/capabilities/gpu0' .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Es un directorio: '/proc/driver/nvidia/capabilities/mig' .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Es un directorio: '/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 460.32.03 Sun Dec 27 19:00:34 UTC 2020 - GCC version: gcc version 7.5.0 (Ubuntu 7.5.0-3ubuntu1~18.04) + NVRM version: NVIDIA UNIX x86_64 Kernel Module 460.32.03 Sun Dec 27 19:00:34 UTC 2020 + GCC version: gcc version 7.5.0 (Ubuntu 7.5.0-3ubuntu1~18.04) ApportVersion: 2.20.9-0ubuntu7.21 Architecture: amd64 BootLog: - + CompositorRunning: None Date: Thu Jan 28 16:52:43 2021 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: - nvidia, 460.32.03, 5.4.0-64-generic, x86_64: installed - rtl8821ce, 5.5.2.1, 5.4.0-42-generic, x86_64: installed - rtl8821ce, 5.5.2.1, 5.4.0-64-generic, x86_64: installed + nvidia, 460.32.03, 5.4.0-64-generic, x86_64: installed + rtl8821ce, 5.5.2.1, 5.4.0-42-generic, x86_64: installed + rtl8821ce, 5.5.2.1, 5.4.0-64-generic, x86_64: installed GraphicsCard: - NVIDIA Corporation Device [10de:1f91] (rev a1) (prog-if 00 [VGA controller]) -Subsystem: ASUSTeK Computer Inc. Device [1043:109f] - Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev c1) (prog-if 00 [VGA controller]) -Subsystem: ASUSTeK Computer Inc. Device [1043:18f1] + NVIDIA Corporation Device [10de:1f91] (rev a1) (prog-if 00 [VGA controller]) + Subsystem: ASUSTeK Computer Inc. Device [1043:109f] + Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev c1) (prog-if 00 [VGA controller]) + Subsystem: ASUSTeK Computer Inc. Device [1043:18f1] InstallationDate: Installed on 2021-01-27 (0 days ago) InstallationMedia: Ubuntu 18.04.5 LTS "Bionic Beaver" - Release amd64 (20200806.1) MachineType: ASUSTeK COMPUTER INC. TUF Gaming FX505DT_FX505DT ProcEnviron: - LANGUAGE=es - TERM=xterm-256color - PATH=(custom, no user) - LANG=es_ES.UTF-8 - SHELL=/bin/bash + LANGUAGE=es + TERM=xterm-256color + PATH=(custom, no user) + LANG=es_ES.UTF-8 + SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-64-generic root=UUID=a4e7f6c4-6b4b-46b3-b120-84a8805ac9dd ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/22/2020 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: FX505DT.315 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: FX505DT 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:
[Desktop-packages] [Bug 1913613] [NEW] Second monitor is detected but has no signal
Public bug reported: xrandr Screen 0: minimum 320 x 200, current 3840 x 1080, maximum 16384 x 16384 eDP connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 344mm x 194mm 1920x1080 59.93*+ 39.99 1680x1050 59.93 1280x1024 59.93 1440x900 59.93 1280x800 59.93 1280x720 59.93 1024x768 59.93 800x600 59.93 640x480 59.93 HDMI-1-0 connected (normal left inverted right x axis y axis) 1920x1080 60.00 + 59.9450.00 1680x1050 59.95 1600x900 60.00 1280x1024 75.0260.02 1280x800 59.81 1280x720 60.0059.9450.00 1024x768 75.0360.00 800x600 75.0060.32 720x576 50.00 720x480 59.94 640x480 75.0059.9459.93 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.4.0-64.72~18.04.1-generic 5.4.78 Uname: Linux 5.4.0-64-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Es un directorio: '/proc/driver/nvidia/capabilities/gpu0' .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Es un directorio: '/proc/driver/nvidia/capabilities/mig' .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Es un directorio: '/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 460.32.03 Sun Dec 27 19:00:34 UTC 2020 GCC version: gcc version 7.5.0 (Ubuntu 7.5.0-3ubuntu1~18.04) ApportVersion: 2.20.9-0ubuntu7.21 Architecture: amd64 BootLog: CompositorRunning: None Date: Thu Jan 28 16:52:43 2021 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 460.32.03, 5.4.0-64-generic, x86_64: installed rtl8821ce, 5.5.2.1, 5.4.0-42-generic, x86_64: installed rtl8821ce, 5.5.2.1, 5.4.0-64-generic, x86_64: installed GraphicsCard: NVIDIA Corporation Device [10de:1f91] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:109f] Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev c1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:18f1] InstallationDate: Installed on 2021-01-27 (0 days ago) InstallationMedia: Ubuntu 18.04.5 LTS "Bionic Beaver" - Release amd64 (20200806.1) MachineType: ASUSTeK COMPUTER INC. TUF Gaming FX505DT_FX505DT ProcEnviron: LANGUAGE=es TERM=xterm-256color PATH=(custom, no user) LANG=es_ES.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-64-generic root=UUID=a4e7f6c4-6b4b-46b3-b120-84a8805ac9dd ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/22/2020 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: FX505DT.315 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: FX505DT 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.:bvrFX505DT.315:bd09/22/2020:svnASUSTeKCOMPUTERINC.:pnTUFGamingFX505DT_FX505DT:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnFX505DT:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: TUF Gaming dmi.product.name: TUF Gaming FX505DT_FX505DT dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~18.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic corruption 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/1913613 Title: Second monitor is detected but has no signal Status in xorg package in Ubuntu: New Bug description: xrandr Screen 0: minimum 320 x 200, current 3840 x 1080, maximum 16384 x 16384 eDP connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 344mm x 194mm 1920x1080 59.93*+ 39.99 1680x1050 59.93 1280x1024 59.93 1440x900 59.93 1280x800 59.93 1280x720 59.93
[Desktop-packages] [Bug 1805666] Re: Evolution Alarm Notify continues pop-up reminders even though notifications disabled
Same issue for me as I'd like general notifications just not routed to Gnome via the Evolution popup. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1805666 Title: Evolution Alarm Notify continues pop-up reminders even though notifications disabled Status in evolution-data-server package in Ubuntu: Invalid Bug description: I have turned off notifications for evolution alarm notify in settings: https://i.imgur.com/BNlfgzA.png But I still get pop-ups from the evolution alarm notify app for calendar events: https://i.imgur.com/BBdr9gm.png ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: evolution-data-server 3.30.1-1build1 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Nov 28 11:31:46 2018 ExecutablePath: /usr/lib/evolution/evolution-data-server/evolution-alarm-notify InstallationDate: Installed on 2018-07-14 (136 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: evolution-data-server UpgradeStatus: Upgraded to cosmic on 2018-10-29 (30 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1805666/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1714244] Re: [snap] apparmor denials on /etc/chromium-browser/policies/
Running Chromium Version 86.0.4240.111 (Official Build) snap (64-bit) on Ubuntu 20.04 and I'm not seeing my policies enforced inside Chromium. -- 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/1714244 Title: [snap] apparmor denials on /etc/chromium-browser/policies/ Status in chromium-browser package in Ubuntu: Fix Committed Bug description: [1565519.440403] audit: type=1400 audit(1504185084.568:68574811): apparmor="ALLOWED" operation="open" profile="snap.chromium.chromium" name="/etc/chromium-browser/policies/managed/" pid=19433 comm ="chromium-browse" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 [1565519.440527] audit: type=1400 audit(1504185084.568:68574812): apparmor="ALLOWED" operation="open" profile="snap.chromium.chromium" name="/etc/chromium-browser/policies/recommended/" pid=19433 comm ="chromium-browse" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 Those denials don't appear to prevent the app from running. Still, they should be investigated and fixed if possible. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1714244/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1870736] Re: [nvidia] Screen scaling 125% gives 200%
Still doesn't work for me after all updates，and there are side effects... Now every time I boot up, the Desktop's font is very small, even there is no external monitor...if ALT + F2 -> R, then restore :( libmutter-6-0: Installed: 3.36.4-0ubuntu0.20.04.2 Candidate: 3.36.4-0ubuntu0.20.04.2 Version table: *** 3.36.4-0ubuntu0.20.04.2 500 500 http://cn.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.36.1-3ubuntu3 500 500 http://cn.archive.ubuntu.com/ubuntu focal/main amd64 Packages +-+ | NVIDIA-SMI 440.64 Driver Version: 440.64 CUDA Version: 10.2 | |---+--+--+ | GPU NamePersistence-M| Bus-IdDisp.A | Volatile Uncorr. ECC | | Fan Temp Perf Pwr:Usage/Cap| Memory-Usage | GPU-Util Compute M. | |===+==+==| | 0 GeForce MX150 Off | :03:00.0 Off | N/A | | N/A 55CP0N/A / N/A |630MiB / 2002MiB | 7% Default | +---+--+--+ journalctl.log => restart,Desktop's font NG journalctl_r.log=> Alt+F2->r ,Desktop's font OK ** Attachment added: "journalctl.zip" https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1870736/+attachment/5405332/+files/journalctl.zip -- 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/1870736 Title: [nvidia] Screen scaling 125% gives 200% Status in gnome-control-center package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: Procedure used: 1. Fully updated system via apt update && apt upgrade 2. Select the screen setup in gnome control center 3. Click the "Fractional scaling" toggle 4. Select 125% and click the green "use" button top right (it says "Anvend" in dansih) 5. Observe that the window has grown a lot, click the "use new settings" button 6. The window tells me, I am at 200% scaling. The "200%" option is now highlighted. 7. Switch back to 100% and file this bug. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.16 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Sat Apr 4 09:42:34 2020 InstallationDate: Installed on 2018-01-14 (810 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=da_DK.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: Upgraded to focal on 2020-04-03 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1870736/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1870736] Re: [nvidia] Screen scaling 125% gives 200%
Will those changes be merged into the 20.04.1 release? -- 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/1870736 Title: [nvidia] Screen scaling 125% gives 200% Status in gnome-control-center package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: Procedure used: 1. Fully updated system via apt update && apt upgrade 2. Select the screen setup in gnome control center 3. Click the "Fractional scaling" toggle 4. Select 125% and click the green "use" button top right (it says "Anvend" in dansih) 5. Observe that the window has grown a lot, click the "use new settings" button 6. The window tells me, I am at 200% scaling. The "200%" option is now highlighted. 7. Switch back to 100% and file this bug. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.16 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Sat Apr 4 09:42:34 2020 InstallationDate: Installed on 2018-01-14 (810 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=da_DK.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: Upgraded to focal on 2020-04-03 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1870736/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1870736] Re: [nvidia] Screen scaling 125% gives 200%
journalctl /usr/bin/gnome-shell -b0 -ef ** Attachment added: "journalctl2.log" https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1870736/+attachment/5391652/+files/journalctl2.log -- 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/1870736 Title: [nvidia] Screen scaling 125% gives 200% Status in gnome-control-center package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: Procedure used: 1. Fully updated system via apt update && apt upgrade 2. Select the screen setup in gnome control center 3. Click the "Fractional scaling" toggle 4. Select 125% and click the green "use" button top right (it says "Anvend" in dansih) 5. Observe that the window has grown a lot, click the "use new settings" button 6. The window tells me, I am at 200% scaling. The "200%" option is now highlighted. 7. Switch back to 100% and file this bug. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.16 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Sat Apr 4 09:42:34 2020 InstallationDate: Installed on 2018-01-14 (810 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=da_DK.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: Upgraded to focal on 2020-04-03 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1870736/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1870736] Re: [nvidia] Screen scaling 125% gives 200%
@3v1n0 NVidi MX150 (440) The updated package not work for me. ** Attachment added: "journalctl.log" https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1870736/+attachment/5391651/+files/journalctl.log -- 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/1870736 Title: [nvidia] Screen scaling 125% gives 200% Status in gnome-control-center package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: Procedure used: 1. Fully updated system via apt update && apt upgrade 2. Select the screen setup in gnome control center 3. Click the "Fractional scaling" toggle 4. Select 125% and click the green "use" button top right (it says "Anvend" in dansih) 5. Observe that the window has grown a lot, click the "use new settings" button 6. The window tells me, I am at 200% scaling. The "200%" option is now highlighted. 7. Switch back to 100% and file this bug. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.16 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Sat Apr 4 09:42:34 2020 InstallationDate: Installed on 2018-01-14 (810 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=da_DK.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: Upgraded to focal on 2020-04-03 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1870736/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1881780] Re: Nautilus requires SMBv1 to work from "Other Locations" without manually typing in the address.
Logically this seems to be correct. I’m not a samba developer, so I don’t have direct insights to what is happening when. I don’t know much about the samba discovery process. The easy way to test this is startup FreeNAS in a VM because they disable SMBv1 by default. On Tue, Jun 30, 2020 at 2:05 PM Andreas Hasenack <1881...@bugs.launchpad.net> wrote: > Ah, I think I see what you mean. Nautilus (gvfs actually) is temporarily > downgrading the protocol for the discovery, but it's not reverting that > when trying to actually connect to a discovered host. Is that it? > > This does ring a bell, it was supposed to be fixed with an SRU on > bionic, and in the development release back then. That SRU is what > enabled this temporary fallback to smbv1 while doing discovery, and > reverted when connecting. > > This needs troubleshooting. > > > ** Also affects: gvfs (Ubuntu) >Importance: Undecided >Status: New > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1881780 > > Title: > Nautilus requires SMBv1 to work from "Other Locations" without > manually typing in the address. > > Status in gvfs package in Ubuntu: > New > Status in nautilus package in Ubuntu: > Incomplete > > Bug description: > Navigate to Other Locations. Your SMB share should show here. > Clicking on the share will cause an error "Unable to access location; > Invalid Argument" if SMBv1 is disabled on the remote host. Manually > connecting by typing in the address still works. > > SMBv1 is deprecated due to WannaCry and other vulnerabilities. Please > fully deprecate SMBv1 by default. > > ProblemType: Bug > DistroRelease: Ubuntu 20.04 > Package: nautilus 1:3.36.1.1-1ubuntu2 > ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 > Uname: Linux 5.4.0-33-generic x86_64 > NonfreeKernelModules: nvidia_modeset nvidia > ApportVersion: 2.20.11-0ubuntu27.2 > Architecture: amd64 > CasperMD5CheckResult: skip > Date: Tue Jun 2 11:41:18 2020 > GsettingsChanges: > > InstallationDate: Installed on 2019-10-13 (232 days ago) > InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) > ProcEnviron: >TERM=xterm-256color >PATH=(custom, no user) >LANG=en_US.UTF-8 >SHELL=/bin/bash > SourcePackage: nautilus > UpgradeStatus: Upgraded to focal on 2020-04-24 (39 days ago) > usr_lib_nautilus: > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1881780/+subscriptions > -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1881780 Title: Nautilus requires SMBv1 to work from "Other Locations" without manually typing in the address. Status in gvfs package in Ubuntu: New Status in nautilus package in Ubuntu: Incomplete Bug description: Navigate to Other Locations. Your SMB share should show here. Clicking on the share will cause an error "Unable to access location; Invalid Argument" if SMBv1 is disabled on the remote host. Manually connecting by typing in the address still works. SMBv1 is deprecated due to WannaCry and other vulnerabilities. Please fully deprecate SMBv1 by default. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.36.1.1-1ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip Date: Tue Jun 2 11:41:18 2020 GsettingsChanges: InstallationDate: Installed on 2019-10-13 (232 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: Upgraded to focal on 2020-04-24 (39 days ago) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1881780/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1881780] Re: Nautilus requires SMBv1 to work from "Other Locations" without manually typing in the address.
No but when you use the automatic detection of smb services which I’m guessing uses NetBios or something like that it won’t connect if SMBv1 is disabled. So simply navigating to Other Locations and clicking on the automatically enumerated host names, the connection will completely fail if SMBv1 is disabled. This might be related to samba directly because the same thing happens in VLC. The current workaround is to manually specify the URL to connect to the desired share. On Tue, Jun 30, 2020 at 1:35 PM Andreas Hasenack <1881...@bugs.launchpad.net> wrote: > When you manually connect, by typing in the full smb url, it doesn't > mean SMB1 is being used. You can verify that by running "sudo smbstatus" > on the server. > > ** Changed in: nautilus (Ubuntu) >Status: New => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1881780 > > Title: > Nautilus requires SMBv1 to work from "Other Locations" without > manually typing in the address. > > Status in nautilus package in Ubuntu: > Incomplete > > Bug description: > Navigate to Other Locations. Your SMB share should show here. > Clicking on the share will cause an error "Unable to access location; > Invalid Argument" if SMBv1 is disabled on the remote host. Manually > connecting by typing in the address still works. > > SMBv1 is deprecated due to WannaCry and other vulnerabilities. Please > fully deprecate SMBv1 by default. > > ProblemType: Bug > DistroRelease: Ubuntu 20.04 > Package: nautilus 1:3.36.1.1-1ubuntu2 > ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 > Uname: Linux 5.4.0-33-generic x86_64 > NonfreeKernelModules: nvidia_modeset nvidia > ApportVersion: 2.20.11-0ubuntu27.2 > Architecture: amd64 > CasperMD5CheckResult: skip > Date: Tue Jun 2 11:41:18 2020 > GsettingsChanges: > > InstallationDate: Installed on 2019-10-13 (232 days ago) > InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) > ProcEnviron: >TERM=xterm-256color >PATH=(custom, no user) >LANG=en_US.UTF-8 >SHELL=/bin/bash > SourcePackage: nautilus > UpgradeStatus: Upgraded to focal on 2020-04-24 (39 days ago) > usr_lib_nautilus: > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1881780/+subscriptions > -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1881780 Title: Nautilus requires SMBv1 to work from "Other Locations" without manually typing in the address. Status in nautilus package in Ubuntu: Incomplete Bug description: Navigate to Other Locations. Your SMB share should show here. Clicking on the share will cause an error "Unable to access location; Invalid Argument" if SMBv1 is disabled on the remote host. Manually connecting by typing in the address still works. SMBv1 is deprecated due to WannaCry and other vulnerabilities. Please fully deprecate SMBv1 by default. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.36.1.1-1ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip Date: Tue Jun 2 11:41:18 2020 GsettingsChanges: InstallationDate: Installed on 2019-10-13 (232 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: Upgraded to focal on 2020-04-24 (39 days ago) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1881780/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1882556] Re: Sometimes taking a screenshot will crash gnome-shell
On a fresh install of 20.04, it seems my system is now sending crash reports. From what I can tell this is a bug in gnome-shell instead of gnome-screenshot as I initially thought. The most recent crash link as of the time of writing is here: https://errors.ubuntu.com/oops/8211fa26-ae79-11ea-a61b-fa163e6cac46 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screenshot in Ubuntu. https://bugs.launchpad.net/bugs/1882556 Title: Sometimes taking a screenshot will crash gnome-shell Status in gnome-screenshot package in Ubuntu: Invalid Bug description: When taking a screenshot, sometimes my whole GNOME desktop will crash. It feels like about a quarter of the time. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-screenshot 3.36.0-1ubuntu1 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: Mon Jun 8 11:30:15 2020 InstallationDate: Installed on 2020-05-05 (34 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/usr/bin/zsh SourcePackage: gnome-screenshot UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screenshot/+bug/1882556/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1882556] Re: Sometimes taking a screenshot will crash gnome-shell
Thanks for pointing out those instructions. I wasn't entirely sure where that stuff was. Unfortunately, it seems that there's no useful crash logs in /var/crash, and nothing is showing up online either. The best I can do is give you a short video of the symptoms, in hopes that something can help. https://photos.app.goo.gl/NuXQqPsxdK7z7zs68 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screenshot in Ubuntu. https://bugs.launchpad.net/bugs/1882556 Title: Sometimes taking a screenshot will crash gnome-shell Status in gnome-screenshot package in Ubuntu: Invalid Bug description: When taking a screenshot, sometimes my whole GNOME desktop will crash. It feels like about a quarter of the time. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-screenshot 3.36.0-1ubuntu1 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: Mon Jun 8 11:30:15 2020 InstallationDate: Installed on 2020-05-05 (34 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/usr/bin/zsh SourcePackage: gnome-screenshot UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screenshot/+bug/1882556/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1882556] [NEW] Sometimes taking a screenshot will crash gnome-shell
Public bug reported: When taking a screenshot, sometimes my whole GNOME desktop will crash. It feels like about a quarter of the time. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-screenshot 3.36.0-1ubuntu1 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: Mon Jun 8 11:30:15 2020 InstallationDate: Installed on 2020-05-05 (34 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/usr/bin/zsh SourcePackage: gnome-screenshot UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-screenshot (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screenshot in Ubuntu. https://bugs.launchpad.net/bugs/1882556 Title: Sometimes taking a screenshot will crash gnome-shell Status in gnome-screenshot package in Ubuntu: New Bug description: When taking a screenshot, sometimes my whole GNOME desktop will crash. It feels like about a quarter of the time. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-screenshot 3.36.0-1ubuntu1 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: Mon Jun 8 11:30:15 2020 InstallationDate: Installed on 2020-05-05 (34 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/usr/bin/zsh SourcePackage: gnome-screenshot UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screenshot/+bug/1882556/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1870736] Re: [nvidia] Screen scaling 125% gives 200%
Dear experts ,we're still waiting for the fix -( -- 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/1870736 Title: [nvidia] Screen scaling 125% gives 200% Status in gnome-control-center package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: Procedure used: 1. Fully updated system via apt update && apt upgrade 2. Select the screen setup in gnome control center 3. Click the "Fractional scaling" toggle 4. Select 125% and click the green "use" button top right (it says "Anvend" in dansih) 5. Observe that the window has grown a lot, click the "use new settings" button 6. The window tells me, I am at 200% scaling. The "200%" option is now highlighted. 7. Switch back to 100% and file this bug. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.16 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Sat Apr 4 09:42:34 2020 InstallationDate: Installed on 2018-01-14 (810 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=da_DK.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: Upgraded to focal on 2020-04-03 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1870736/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1870736] Re: [nvidia] Screen scaling 125% gives 200%
Affected as well: Ubuntu 20.04 LTS GeForce MX150 NVIDIA-Linux-x86_64-440.82.run -- 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/1870736 Title: [nvidia] Screen scaling 125% gives 200% Status in gnome-control-center package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: Procedure used: 1. Fully updated system via apt update && apt upgrade 2. Select the screen setup in gnome control center 3. Click the "Fractional scaling" toggle 4. Select 125% and click the green "use" button top right (it says "Anvend" in dansih) 5. Observe that the window has grown a lot, click the "use new settings" button 6. The window tells me, I am at 200% scaling. The "200%" option is now highlighted. 7. Switch back to 100% and file this bug. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.16 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Sat Apr 4 09:42:34 2020 InstallationDate: Installed on 2018-01-14 (810 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=da_DK.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: Upgraded to focal on 2020-04-03 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1870736/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 938751] Re: Images are washed out or colors are skewed in some apps
** Changed in: chromium-browser (Ubuntu) Assignee: (unassigned) => jon grahaqm (skyking2630) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/938751 Title: Images are washed out or colors are skewed in some apps Status in Eye of GNOME: New Status in chromium-browser package in Ubuntu: Confirmed Status in colord package in Ubuntu: Confirmed Status in eog package in Ubuntu: Confirmed Bug description: Images are washed out or colors are skewed in some apps, notably Chrome/Chromium and Image Viewer (eog). Workaround: Settings > Devices > Colour > and disable or remove your monitor's colour profile To manage notifications about this bug go to: https://bugs.launchpad.net/eog/+bug/938751/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1672459] Re: incorrectly asks for password on .pdf file
On 07/22/2019 07:10 AM, Paul White wrote: > I cannot reproduce the problem using either evince 3.28 in Xubuntu > 18.04, or evince 3.32 in Ubuntu 19.10 (dev). I've also viewed the same > file downloaded from other sources. There have been several reports of > this problem in the past but they seem to have been fixed before this > bug report was raised. > OK, that is fine. Eventually, this system will get creaky enough that I will have to update. Just a case of inertia! Thanks for looking into it, and glad that newer versions do not have the problem. Jon -- 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/1672459 Title: incorrectly asks for password on .pdf file Status in evince package in Ubuntu: Fix Released Bug description: Ubuntu 12.04.3 LTS, evince 3.4.0, just updated it with apt-get and still shows the problem. Here's a file that asks for password : https://www.fairchildsemi.com/datasheets/FO/FODM121.pdf But, it seems a bunch of Fairchild semi files have the same problem. Reads fine with acroread, asks for a password in evince. apt-cache shows : evince: Installed: 3.4.0-0ubuntu1.8 Candidate: 3.4.0-0ubuntu1.8 Version table: *** 3.4.0-0ubuntu1.8 0 500 http://us.archive.ubuntu.com/ubuntu/ precise-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.4.0-0ubuntu1 0 500 http://us.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages Thanks, Jon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1672459/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1672459] Re: incorrectly asks for password on .pdf file
On 07/21/2019 07:04 AM, Paul White wrote: > We are sorry that we do not always have the capacity to review all > reported bugs in a timely manner. You reported this bug some time ago > and there have been many changes in Ubuntu since that time. > > Ubuntu 12.04 (precise) reached end-of-life on April 28, 2017. > > Do you still see a problem related to the one that you reported when > using a currently supported version of Ubuntu? Please let us know if you > do otherwise this report can be left to expire in approximately 60 days > time. > > WOW, I don't even remember reporting this bug! The link I gave in the bug report doesn't work anymore, but if you enter FODM121 in the search box and then click on the pdf link that comes up, it STILL does the same thing, on evince 3.4.0 And, it may just be a badly formatted document, too. The URL is : https://www.onsemi.com/pub/Collateral/FODM2705-D.pdf I am still running 12.04 on some systems, I have too many tricky packages installed to update until it is REALLY necessary. Thanks, Jon -- 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/1672459 Title: incorrectly asks for password on .pdf file Status in evince package in Ubuntu: Incomplete Bug description: Ubuntu 12.04.3 LTS, evince 3.4.0, just updated it with apt-get and still shows the problem. Here's a file that asks for password : https://www.fairchildsemi.com/datasheets/FO/FODM121.pdf But, it seems a bunch of Fairchild semi files have the same problem. Reads fine with acroread, asks for a password in evince. apt-cache shows : evince: Installed: 3.4.0-0ubuntu1.8 Candidate: 3.4.0-0ubuntu1.8 Version table: *** 3.4.0-0ubuntu1.8 0 500 http://us.archive.ubuntu.com/ubuntu/ precise-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.4.0-0ubuntu1 0 500 http://us.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages Thanks, Jon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1672459/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1825691] [NEW] segmentation fault (core dumped)
Public bug reported: $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 19.04 Release:19.04 Codename: disco $ gnome-control-center -v 22:48:42.0979 cc-object-storage:DEBUG: Finished creating D-Bus proxy for CcObjectStorage::dbus-proxy(org.gnome.SettingsDaemon.Color,/org/gnome/SettingsDaemon/Color,org.freedesktop.DBus.Properties) 22:48:42.0979 cc-object-storage:DEBUG: Adding object GDBusProxy (CcObjectStorage::dbus-proxy(org.gnome.SettingsDaemon.Color,/org/gnome/SettingsDaemon/Color,org.freedesktop.DBus.Properties) → 0x7f733c001d40) to the storage 22:48:42.0979 cc-object-storage:DEBUG: Finished creating D-Bus proxy for CcObjectStorage::dbus-proxy(org.gnome.SettingsDaemon.Color,/org/gnome/SettingsDaemon/Color,org.gnome.SettingsDaemon.Color) 22:48:42.0979 cc-object-storage:DEBUG: Adding object GDBusProxy (CcObjectStorage::dbus-proxy(org.gnome.SettingsDaemon.Color,/org/gnome/SettingsDaemon/Color,org.gnome.SettingsDaemon.Color) → 0x56285a90fe80) to the storage 22:48:42.0979 display-cc-panel: WARNING: no sunset data, using 16.00 22:48:42.0979 display-cc-panel:DEBUG: setting adjustment 16.000 to 16:00 22:48:42.0980 display-cc-panel: WARNING: no sunrise data, using 8.00 22:48:42.0980 display-cc-panel:DEBUG: setting adjustment 8.000 to 8:00 22:48:42.0982 cc-object-storage:DEBUG: Finished creating D-Bus proxy for CcObjectStorage::dbus-proxy(org.gnome.Shell,/org/gnome/Shell,org.gnome.Shell) 22:48:42.0982 cc-object-storage:DEBUG: Adding object GDBusProxy (CcObjectStorage::dbus-proxy(org.gnome.Shell,/org/gnome/Shell,org.gnome.Shell) → 0x7f733c001dd0) to the storage 22:48:42.0990 display-cc-panel:DEBUG: SensorProxy vanished 22:48:42.0990 display-cc-panel:DEBUG: Has no accelerometer 22:48:42.0991 display-cc-panel:DEBUG: Resetting current config! 22:48:42.0991 GLib-GObject: CRITICAL: g_object_ref: assertion 'G_IS_OBJECT (object)' failed [1]12354 segmentation fault (core dumped) gnome-control-center -v $ dmesg [ 1811.497720] gnome-control-c[12354]: segfault at 0 ip 5628579aebc0 sp 7ffefa8ea438 error 4 in gnome-control-center[562857967000+119000] [ 1811.497728] Code: 40 00 48 8b 2b 4c 89 e6 48 89 ef e8 ca f9 ff ff 31 d2 31 f6 48 89 ef e8 ce f9 ff ff 48 8b 5b 08 48 85 db 75 dd 5b 5d 41 5c c3 <48> 8b 07 ff a0 98 00 00 00 0f 1f 80 00 00 00 00 48 8b 07 ff a0 a0 ** 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/1825691 Title: segmentation fault (core dumped) Status in gnome-control-center package in Ubuntu: New Bug description: $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 19.04 Release: 19.04 Codename: disco $ gnome-control-center -v 22:48:42.0979 cc-object-storage:DEBUG: Finished creating D-Bus proxy for CcObjectStorage::dbus-proxy(org.gnome.SettingsDaemon.Color,/org/gnome/SettingsDaemon/Color,org.freedesktop.DBus.Properties) 22:48:42.0979 cc-object-storage:DEBUG: Adding object GDBusProxy (CcObjectStorage::dbus-proxy(org.gnome.SettingsDaemon.Color,/org/gnome/SettingsDaemon/Color,org.freedesktop.DBus.Properties) → 0x7f733c001d40) to the storage 22:48:42.0979 cc-object-storage:DEBUG: Finished creating D-Bus proxy for CcObjectStorage::dbus-proxy(org.gnome.SettingsDaemon.Color,/org/gnome/SettingsDaemon/Color,org.gnome.SettingsDaemon.Color) 22:48:42.0979 cc-object-storage:DEBUG: Adding object GDBusProxy (CcObjectStorage::dbus-proxy(org.gnome.SettingsDaemon.Color,/org/gnome/SettingsDaemon/Color,org.gnome.SettingsDaemon.Color) → 0x56285a90fe80) to the storage 22:48:42.0979 display-cc-panel: WARNING: no sunset data, using 16.00 22:48:42.0979 display-cc-panel:DEBUG: setting adjustment 16.000 to 16:00 22:48:42.0980 display-cc-panel: WARNING: no sunrise data, using 8.00 22:48:42.0980 display-cc-panel:DEBUG: setting adjustment 8.000 to 8:00 22:48:42.0982 cc-object-storage:DEBUG: Finished creating D-Bus proxy for CcObjectStorage::dbus-proxy(org.gnome.Shell,/org/gnome/Shell,org.gnome.Shell) 22:48:42.0982 cc-object-storage:DEBUG: Adding object GDBusProxy (CcObjectStorage::dbus-proxy(org.gnome.Shell,/org/gnome/Shell,org.gnome.Shell) → 0x7f733c001dd0) to the storage 22:48:42.0990 display-cc-panel:DEBUG: SensorProxy vanished 22:48:42.0990
[Desktop-packages] [Bug 1819909] [NEW] Problem with windows
Public bug reported: No border around windows, no resizing buttons (max, min, close). Windows cannot be moved or resized. Alt+tab and Alt+F4 have no effect, but some other keyboard shortcuts, e.g. ctrl+alt+T and ctrl+Q, seem to work ok. Only closing a window changes focus; even clicking with mouse doesn't. For instance, I can use ctrl+alt+t to open a terminal, and click in it all I want, but even though it is on top, whatever I type just goes into this window. When I close the browser, however, it will gain focus. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18 Uname: Linux 4.15.0-46-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: XFCE Date: Wed Mar 13 08:30:21 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: virtualbox, 5.2.18, 4.15.0-43-generic, x86_64: installed virtualbox, 5.2.18, 4.15.0-45-generic, x86_64: installed virtualbox, 5.2.18, 4.15.0-46-generic, x86_64: installed GraphicsCard: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:22b1] (rev 35) (prog-if 00 [VGA controller]) Subsystem: Lenovo Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [17aa:3809] InstallationDate: Installed on 2018-09-10 (184 days ago) InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 13d3:a745 IMC Networks Bus 001 Device 003: ID 0cf3:e360 Atheros Communications, Inc. Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 80T7 ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-46-generic root=/dev/mapper/xubuntu--vg-root ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/28/2016 dmi.bios.vendor: LENOVO dmi.bios.version: 1GCN12WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: 00RD15IPG076 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40700 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 110-15IBR dmi.modalias: dmi:bvnLENOVO:bvr1GCN12WW:bd02/28/2016:svnLENOVO:pn80T7:pvrLenovoideapad110-15IBR:rvnLENOVO:rn00RD15IPG076:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoideapad110-15IBR: dmi.product.family: IDEAPAD dmi.product.name: 80T7 dmi.product.version: Lenovo ideapad 110-15IBR dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1~18.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1819909 Title: Problem with windows Status in xorg package in Ubuntu: New Bug description: No border around windows, no resizing buttons (max, min, close). Windows cannot be moved or resized. Alt+tab and Alt+F4 have no effect, but some other keyboard shortcuts, e.g. ctrl+alt+T and ctrl+Q, seem to work ok. Only closing a window changes focus; even clicking with mouse doesn't. For instance, I can use ctrl+alt+t to open a terminal, and click in it all I want, but even though it is on top, whatever I type just goes into this window. When I close the browser, however, it will gain focus. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18 Uname: Linux 4.15.0-46-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: XFCE Date: Wed Mar 13 08:30:21 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: virtualbox, 5.2.18, 4.15.0-43-generic, x86_64: installed virtualbox, 5.2.18, 4.15.0-45-generic, x86_64: installed virtualbox, 5.2.18, 4.15.0-46-generic, x86_64:
[Desktop-packages] [Bug 1660316] Re: apparmor denial of CUPS
I'm seeing this in Ubuntu 18.04 as well. I have 2 printers configured an HP LaserJet p4015 and a Canon ImageRunner C5030. kernel: [35100.990629] audit: type=1400 audit(1536755161.327:158): apparmor="DENIED" operation="capable" profile="/usr/sbin/cupsd" pid=15321 comm="cupsd" capability=12 capname="net_admin" -- 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/1660316 Title: apparmor denial of CUPS Status in cups package in Ubuntu: Expired Bug description: Printing is enabled when doing sudo aa-complain cupsd Here is an extract of /var/log/syslog: Jan 30 12:41:59 dag-TS-P500 kernel: [ 868.929457] audit: type=1400 audit(1485776519.269:37): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/cups/backend/cups-pdf" pid=6932 comm="apparmor_parser" Jan 30 12:41:59 dag-TS-P500 kernel: [ 868.929744] audit: type=1400 audit(1485776519.269:38): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/cupsd" pid=6932 comm="apparmor_parser" Jan 30 12:41:59 dag-TS-P500 kernel: [ 868.945422] audit: type=1400 audit(1485776519.285:39): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/cupsd//third_party" pid=6932 comm="apparmor_parser" Jan 30 12:42:10 dag-TS-P500 kernel: [ 879.817070] audit: type=1400 audit(1485776530.158:40): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/cups/backend/cups-pdf" pid=6941 comm="apparmor_parser" Jan 30 12:42:10 dag-TS-P500 kernel: [ 879.817342] audit: type=1400 audit(1485776530.158:41): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/cupsd" pid=6941 comm="apparmor_parser" Jan 30 12:42:10 dag-TS-P500 kernel: [ 879.837254] audit: type=1400 audit(1485776530.178:42): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/cupsd//third_party" pid=6941 comm="apparmor_parser" Jan 30 12:42:16 dag-TS-P500 zeitgeist-datah[3706]: downloads-directory-provider.vala:120: Couldn't process /home/dag/.glvndcEQzqA: Error when getting information for file '/home/dag/.glvndcEQzqA': No such file or directory Jan 30 12:42:23 dag-TS-P500 dbus[996]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' Jan 30 12:42:23 dag-TS-P500 systemd[1]: Starting Hostname Service... Jan 30 12:42:24 dag-TS-P500 dbus[996]: [system] Successfully activated service 'org.freedesktop.hostname1' Jan 30 12:42:24 dag-TS-P500 systemd[1]: Started Hostname Service. Jan 30 12:42:26 dag-TS-P500 kernel: [ 895.746636] audit: type=1400 audit(1485776546.086:43): apparmor="DENIED" operation="capable" profile="/usr/sbin/cupsd" pid=6967 comm="lpd" capability=12 capname="net_admin" Jan 30 12:42:54 dag-TS-P500 systemd[1]: Starting Cleanup of Temporary Directories... Jan 30 12:42:54 dag-TS-P500 systemd-tmpfiles[6973]: [/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for path "/var/log", ignoring. Jan 30 12:42:54 dag-TS-P500 systemd[1]: Started Cleanup of Temporary Directories. Jan 30 12:44:03 dag-TS-P500 dbus-daemon[2707]: Activating service name='com.ubuntu.OneConf' Jan 30 12:44:03 dag-TS-P500 dbus-daemon[2707]: Successfully activated service 'com.ubuntu.OneConf' Jan 30 12:44:03 dag-TS-P500 com.ubuntu.OneConf[2707]: WARNING:oneconf.hosts:Error in loading other_hosts file: [Errno 2] No such file or directory: '/home/dag/.cache/oneconf/d2fc3bf30c9f4976b441a8f14de53bda/other_hosts' Jan 30 12:44:23 dag-TS-P500 dbus-daemon[2707]: Activating service name='com.ubuntu.sso' Jan 30 12:44:24 dag-TS-P500 dbus-daemon[2707]: Successfully activated service 'com.ubuntu.sso' Jan 30 12:45:51 dag-TS-P500 kernel: [ 1100.685842] audit: type=1400 audit(1485776751.028:44): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/cups/backend/cups-pdf" pid=7024 comm="apparmor_parser" Jan 30 12:45:51 dag-TS-P500 kernel: [ 1100.686099] audit: type=1400 audit(1485776751.028:45): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/cupsd" pid=7024 comm="apparmor_parser" Jan 30 12:45:51 dag-TS-P500 kernel: [ 1100.700446] audit: type=1400 audit(1485776751.044:46): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/cupsd//third_party" pid=7024 comm="apparmor_parser" Jan 30 12:45:57 dag-TS-P500 kernel: [ 1106.940891] audit: type=1400 audit(1485776757.284:47): apparmor="ALLOWED" operation="capable" profile="/usr/sbin/cupsd" pid=7031 comm="lpd" capability=12 capname="net_admin" Jan 30 12:45:57 dag-TS-P500 kernel: [ 1106.940938] audit: type=1400 audit(1485776757.284:48): apparmor="ALLOWED" operation="capable" profile="/usr/sbin/cupsd" pid=7031 comm="lpd" capability=12 capname="net_admin" ProblemType: Bug DistroRelease: Ubuntu
[Desktop-packages] [Bug 1772677] Re: gnome-shell filling up syslog with thousands of entries (stack traces ending in osdWindow.js:206/207)
I have the same issue. I am rotating syslog hourly - which isn't ideal but mitigates the problem for now. Sep 9 19:48:58 tsunami org.gnome.Shell.desktop[1920]: == Stack trace for context 0x55813e634330 == Sep 9 19:48:58 tsunami org.gnome.Shell.desktop[1920]: #0 0x7ffd6a265310 I resource:///org/gnome/shell/ui/osdWindow.js:207 (0x7f0dd44c7780 @ 273) Sep 9 19:48:58 tsunami org.gnome.Shell.desktop[1920]: #1 0x7ffd6a265380 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f0dd45b5de0 @ 71) Sep 9 19:48:58 tsunami org.gnome.Shell.desktop[1920]: #2 0x7ffd6a265380 I self-hosted:916 (0x7f0dd45f12b8 @ 367) Sep 9 19:48:58 tsunami org.gnome.Shell.desktop[1920]: #3 0x7ffd6a265420 I resource:///org/gnome/gjs/modules/signals.js:128 (0x7f0dd45d2230 @ 386) Sep 9 19:48:58 tsunami org.gnome.Shell.desktop[1920]: #4 0x7ffd6a2654d0 b resource:///org/gnome/shell/ui/layout.js:531 (0x7f0dd44042b8 @ 127) Sep 9 19:48:58 tsunami org.gnome.Shell.desktop[1920]: #5 0x7ffd6a265540 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f0dd45b5de0 @ 71) Sep 9 19:48:58 tsunami org.gnome.Shell.desktop[1920]: #6 0x7ffd6a265540 I self-hosted:916 (0x7f0dd45f12b8 @ 367) -- 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/1772677 Title: gnome-shell filling up syslog with thousands of entries (stack traces ending in osdWindow.js:206/207) Status in gnome-shell package in Ubuntu: Confirmed Bug description: I'm seeing a several gigs (more than 70GB) a day of the following entries on syslog: May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: == Stack trace for context 0x557ebb0a3320 == May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #0 0x7ffcc6cedf80 I resource:///org/gnome/shell/ui/osdWindow.js:206 (0x7f31f00c96f8 @ 231) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #1 0x7ffcc6cedff0 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f31d4db5de0 @ 71) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #2 0x7ffcc6cedff0 I self-hosted:915 (0x7f31d4df12b8 @ 367) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #3 0x7ffcc6cee090 I resource:///org/gnome/gjs/modules/signals.js:128 (0x7f31d4dd3230 @ 386) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #4 0x7ffcc6cee140 b resource:///org/gnome/shell/ui/layout.js:531 (0x7f31f00042b8 @ 127) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #5 0x7ffcc6cee1b0 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f31d4db5de0 @ 71) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #6 0x7ffcc6cee1b0 I self-hosted:915 (0x7f31d4df12b8 @ 367) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: == Stack trace for context 0x557ebb0a3320 == May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #0 0x7ffcc6cedf80 I resource:///org/gnome/shell/ui/osdWindow.js:207 (0x7f31f00c96f8 @ 258) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #1 0x7ffcc6cedff0 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f31d4db5de0 @ 71) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #2 0x7ffcc6cedff0 I self-hosted:915 (0x7f31d4df12b8 @ 367) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #3 0x7ffcc6cee090 I resource:///org/gnome/gjs/modules/signals.js:128 (0x7f31d4dd3230 @ 386) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #4 0x7ffcc6cee140 b resource:///org/gnome/shell/ui/layout.js:531 (0x7f31f00042b8 @ 127) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #5 0x7ffcc6cee1b0 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f31d4db5de0 @ 71) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #6 0x7ffcc6cee1b0 I self-hosted:915 (0x7f31d4df12b8 @ 367) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: == Stack trace for context 0x557ebb0a3320 == May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #0 0x7ffcc6cedf80 I resource:///org/gnome/shell/ui/osdWindow.js:206 (0x7f31f00c96f8 @ 231) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #1 0x7ffcc6cedff0 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f31d4db5de0 @ 71) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #2 0x7ffcc6cedff0 I self-hosted:915 (0x7f31d4df12b8 @ 367) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #3 0x7ffcc6cee090 I resource:///org/gnome/gjs/modules/signals.js:128 (0x7f31d4dd3230 @ 386) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #4 0x7ffcc6cee140 b resource:///org/gnome/shell/ui/layout.js:531 (0x7f31f00042b8 @ 127) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #5 0x7ffcc6cee1b0 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f31d4db5de0 @ 71) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #6 0x7ffcc6cee1b0 I self-hosted:915 (0x7f31d4df12b8 @ 367) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: ==
[Desktop-packages] [Bug 1774601] [NEW] gio trash (or gvfs-trash) on a vboxsf partition fails with "Unable to find or create trash directory"
Public bug reported: I am using an Ubuntu 18.04 Vagrant machine, which has had the ubuntu- mate-desktop tasksel applied to it. I mount a filesystem from the Virtualbox Host using this line in /etc/fstab: HostHome /HostHome vboxsf _netdev,uid=1000,gid=1000,dmask=0077,fmask=0177 0 0 With this build, I have installed the atom snap package, and when I try to remove a file from the file tree, I get an error saying: The following file couldn't be moved to the trash. /HostHome/Documents/01 Projects/K5-Ansible-Openstack-Development-Machine/ansible_users.retry Is gvfs-trash installed? On further investigation, I found that while gvfs-trash is installed (via the gvfs-common package), it has been depreciated, preferring gio. Running either `gio trash` or `gvfs-trash` specifying that path (`/HostHome/Documents/01 Projects/K5-Ansible-Openstack-Development- Machine/ansible_users.retry`) returns this report: gio: file:///HostHome/Documents/01%20Projects/K5-Ansible-Openstack- Development-Machine/ansible_users.retry: Unable to find or create trash directory for /HostHome/Documents/01 Projects/K5-Ansible-Openstack- Development-Machine/ansible_users.retry ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libglib2.0-bin 2.56.1-2ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: MATE Date: Fri Jun 1 08:26:04 2018 SourcePackage: glib2.0 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: glib2.0 (Ubuntu) Importance: Undecided Status: New ** Affects: gvfs (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic uec-images ** Also affects: gvfs (Ubuntu) Importance: Undecided Status: New -- 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/1774601 Title: gio trash (or gvfs-trash) on a vboxsf partition fails with "Unable to find or create trash directory" Status in glib2.0 package in Ubuntu: New Status in gvfs package in Ubuntu: New Bug description: I am using an Ubuntu 18.04 Vagrant machine, which has had the ubuntu- mate-desktop tasksel applied to it. I mount a filesystem from the Virtualbox Host using this line in /etc/fstab: HostHome /HostHome vboxsf _netdev,uid=1000,gid=1000,dmask=0077,fmask=0177 0 0 With this build, I have installed the atom snap package, and when I try to remove a file from the file tree, I get an error saying: The following file couldn't be moved to the trash. /HostHome/Documents/01 Projects/K5-Ansible-Openstack-Development-Machine/ansible_users.retry Is gvfs-trash installed? On further investigation, I found that while gvfs-trash is installed (via the gvfs-common package), it has been depreciated, preferring gio. Running either `gio trash` or `gvfs-trash` specifying that path (`/HostHome/Documents/01 Projects/K5-Ansible-Openstack-Development- Machine/ansible_users.retry`) returns this report: gio: file:///HostHome/Documents/01%20Projects/K5-Ansible- Openstack-Development-Machine/ansible_users.retry: Unable to find or create trash directory for /HostHome/Documents/01 Projects/K5-Ansible- Openstack-Development-Machine/ansible_users.retry ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libglib2.0-bin 2.56.1-2ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: MATE Date: Fri Jun 1 08:26:04 2018 SourcePackage: glib2.0 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1774601/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1747827] Re: alt-tab no longer lets me switch between terminal windows
Yes, this bug should move to gnome-shell -- I'm using the default in ubuntu-17.10, which is gnome-shell. ** Package changed: unity (Ubuntu) => gnome-shell (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1747827 Title: alt-tab no longer lets me switch between terminal windows Status in gnome-shell package in Ubuntu: New Bug description: I typically use multiple terminal windows, rather than tabs within terminal windows, because I find that the context of the visible part of the overlapping windows is highly useful. Up to 17.04, I could use alt-tab to switch between different windows that were each running a terminal instance. As of 17.10, I can only switch between "the current terminal focus window" and "other apps" -- other terminal windows are not part of the alt-tab "ring" Especially going back and forth between the two latest terminal windows with a single alt-tab is crucial to a productive workflow, and all OS-es I've used have supported this for the last 20 years. Except now, I'm expected to Alt-tab a few times to get "back" to terminal, then press arrow-down and arrow-right to select another terminal window. Wot? That's not helpful. This fundamentally breaks my workflow, and is not something I can live with. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: unity 7.5.0+17.10.20171010-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia .proc.driver.nvidia.gpus..42.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:42:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 384.111 Tue Dec 19 23:51:45 PST 2017 GCC version: gcc version 7.2.0 (Ubuntu 7.2.0-8ubuntu3) .proc.driver.nvidia.warnings.fbdev: Your system is not currently configured to drive a VGA console on the primary VGA device. The NVIDIA Linux graphics driver requires the use of a text-mode VGA console. Use of other console drivers including, but not limited to, vesafb, may result in corruption and stability problems, and is not supported. .tmp.unity_support_test.0: ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Feb 6 20:30:28 2018 DistUpgraded: 2018-02-05 15:47:10,383 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: artful DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.10.0-42-generic, x86_64: installed bbswitch, 0.8, 4.13.0-32-generic, x86_64: installed nvidia-384, 384.111, 4.10.0-42-generic, x86_64: installed nvidia-384, 384.111, 4.13.0-32-generic, x86_64: installed GraphicsCard: NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP102 [GeForce GTX 1080 Ti] [1043:85ea] InstallationDate: Installed on 2017-08-26 (164 days ago) InstallationMedia: Ubuntu-Server 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-32-generic.efi.signed root=/dev/mapper/nvm--vg0-root ro rd.driver.blacklist=nouveau SourcePackage: unity UpgradeStatus: Upgraded to artful on 2018-02-05 (1 days ago) dmi.bios.date: 08/11/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0318 dmi.board.asset.tag: Default string dmi.board.name: PRIME X399-A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0318:bd08/11/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX399-A:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.13.1+17.10.20170901-0ubuntu1 version.libdrm2: libdrm2 2.4.83-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~17.10.2 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~17.10.2 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications
[Desktop-packages] [Bug 1748511] Re: Xorg crash
Thanks for the questions 1) Removing the kernel parameter causes the same problem (plus, shutdown doesn't work.) 2) I cannot take the graphics card out of the laptop, but I uninstalled the nouveau package xserver-xorg-video-nouveau. This may have improved things; see below! 3) This is on a fresh install of 17.10 on a freshly partitioned/formatted disk. 4) When I log in to an Xorg session (after removing the nouveau xorg driver,) the desktop takes a long time to appear. The computer is largely unresponsive to mouse/keyboard for many seconds, then becomes responsive for a second, then goes unresponsive again; this repeats a few times, before the desktop entirely locks up (and a SSH shell also is locked up at that point.) However, pointing on the touchscreen will move the cursor in this state; moving the touchpad does not move the cursor, and nothing can be clicked/interacted with. Regarding 2) after logging into a default session (Wayland,) with the nouveau Xorg driver removed, but the nouveau kernel module still loaded (despite blacklisting,) it has not crashed my desktop yet. vainfo seems to think that I have accelerated video decoding, and glxgears runs at 60 fps in full screen, so perhaps this is a workaround? -- 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/1748511 Title: Xorg crash Status in xorg package in Ubuntu: Incomplete Bug description: Shortly after logging in for the first time, the screen goes black, and after a little while, I'm back at the login screen. A subsequent login puts me in "dumb software mode." ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Feb 9 10:45:29 2018 DistUpgraded: Fresh install DistroCodename: artful DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:591b] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:07be] Subsystem: Dell GP107M [GeForce GTX 1050 Mobile] [1028:07be] InstallationDate: Installed on 2018-02-09 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) MachineType: Dell Inc. XPS 15 9560 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-32-generic.efi.signed root=UUID=4305e654-6011-4413-ac27-724450f22361 ro quiet splash acpi_rev_override=5 vt.handoff=7 Renderer: Software SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/30/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.0 dmi.board.name: 05FFDN dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.0:bd08/30/2017:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn05FFDN:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9560 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.83-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~17.10.2 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~17.10.2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1748511/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1748514] [NEW] DNS doesn't work
Public bug reported: I am running a fresh install of Ubuntu Desktop 17.10 on a Dell XPS 15 9560 laptop. I'm using an external Thunderbolt dock to connect to wired Ethernet. I have additionally installed openssh-server on the system. When I boot the system as normal, NetworkManager ends up creating a resolv.conf file that contains "nameserver 127.0.1.1" However, with this file, DNS doesn't work -- "ping www.google.com" doesn't resolve, web pages don't resolve, ubuntu update doesn't find servers, and so forth. If I do the following, the system works fine: "mv /etc/resolv.conf /etc/resolv.conf.old" "echo 'nameserver 8.8.8.8' > /etc/resolv.conf" But I have to re-do this every time I boot. I have configured manual DNS as 8.8.8.8,8.8.4.4 in the properties for the Wired network connection. It also doesn't work if I use the default DHCP servers (Comcast, who poisons DNS for their customers so I generally don't use that.) My DHCP server is a MikroTik Routerboard Router/Access point (I'm using wired Ethernet for now.) Other wired machines on the same network work fine, including older versions of Ubuntu with DNS set to 8.8.8.8. netstat -naplt udp doesn't show anything listening on port 53 locally, I don't know of that's expected or not for whatever the 127.0.1.1 proxy is. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: network-manager 1.8.4-1ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Feb 9 10:53:31 2018 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-02-09 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) IpRoute: default via 10.0.0.1 dev enxa44cc88a6c8b proto static metric 100 10.0.0.0/8 dev enxa44cc88a6c8b proto kernel scope link src 10.0.0.40 metric 100 169.254.0.0/16 dev enxa44cc88a6c8b scope link metric 1000 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAMEUUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH SLAVE Wired connection 1 b5405fe6-c553-3491-a172-711c8a3e1717 802-3-ethernet 1518202258 Fri 09 Feb 2018 10:50:58 AM PST yes 4294966297 no/org/freedesktop/NetworkManager/Settings/1 yes enxa44cc88a6c8b activated /org/freedesktop/NetworkManager/ActiveConnection/2 -- nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH enxa44cc88a6c8b ethernet connected /org/freedesktop/NetworkManager/Devices/2 Wired connection 1 b5405fe6-c553-3491-a172-711c8a3e1717 /org/freedesktop/NetworkManager/ActiveConnection/2 wlp2s0 wifi disconnected /org/freedesktop/NetworkManager/Devices/3 -- -- -- lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/1 -- -- -- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.8.4connected started full enabled enabled enabled enabled enabled ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1748514 Title: DNS doesn't work Status in network-manager package in Ubuntu: New Bug description: I am running a fresh install of Ubuntu Desktop 17.10 on a Dell XPS 15 9560 laptop. I'm using an external Thunderbolt dock to connect to wired Ethernet. I have additionally installed openssh-server on the system. When I boot the system as normal, NetworkManager ends up creating a resolv.conf file that contains "nameserver 127.0.1.1" However, with this file, DNS doesn't work -- "ping www.google.com" doesn't resolve, web pages don't resolve, ubuntu update doesn't find servers, and so forth. If I do the following, the system works fine: "mv /etc/resolv.conf /etc/resolv.conf.old" "echo 'nameserver 8.8.8.8' > /etc/resolv.conf" But I
[Desktop-packages] [Bug 1748511] [NEW] Xorg crash
Public bug reported: I've installed ubuntu desktop 17.10 amd64 from scratch in UEFI mode on a Dell XPS 15 9560 laptop. This laptop comes with i915 built-in graphics, as well as an NVIDIA 1050 GPU, but I am not trying to make the NVIDIA work yet, and have blacklisted nouveau. I'm using xorg 1:7.7+19ubuntu3 xserver-xorg-video-intel/artful,now 2:2.99.917+git20170309-0ubuntu1 amd64 I have to set acpi_rev_override=5 in the kernel boot parameters, because rev 6 causes other bugs (hang on shutdown, for example.) I'm using whatever the default desktop (presumably Gnome) and compositor are for a ubuntu desktop install. I can boot to login; I can log in to desktop, but shortly after desktop login, the screen goes black, and after a little while, I'm back at the login screen. Logging in again, works, but at that point, I believe I'm in "dumb software mode." ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Feb 9 10:45:29 2018 DistUpgraded: Fresh install DistroCodename: artful DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:591b] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:07be] Subsystem: Dell GP107M [GeForce GTX 1050 Mobile] [1028:07be] InstallationDate: Installed on 2018-02-09 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) MachineType: Dell Inc. XPS 15 9560 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-32-generic.efi.signed root=UUID=4305e654-6011-4413-ac27-724450f22361 ro quiet splash acpi_rev_override=5 vt.handoff=7 Renderer: Software SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/30/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.0 dmi.board.name: 05FFDN dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.0:bd08/30/2017:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn05FFDN:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9560 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.83-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~17.10.2 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~17.10.2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful crash ubuntu wayland-session -- 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/1748511 Title: Xorg crash Status in xorg package in Ubuntu: New Bug description: I've installed ubuntu desktop 17.10 amd64 from scratch in UEFI mode on a Dell XPS 15 9560 laptop. This laptop comes with i915 built-in graphics, as well as an NVIDIA 1050 GPU, but I am not trying to make the NVIDIA work yet, and have blacklisted nouveau. I'm using xorg 1:7.7+19ubuntu3 xserver-xorg-video-intel/artful,now 2:2.99.917+git20170309-0ubuntu1 amd64 I have to set acpi_rev_override=5 in the kernel boot parameters, because rev 6 causes other bugs (hang on shutdown, for example.) I'm using whatever the default desktop (presumably Gnome) and compositor are for a ubuntu desktop install. I can boot to login; I can log in to desktop, but shortly after desktop login, the screen goes black, and after a little while, I'm back at the login screen. Logging in again, works, but at that point, I believe I'm in "dumb software mode." ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Feb 9 10:45:29 2018 DistUpgraded: Fresh install DistroCodename: artful DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:591b] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:07be] Subsystem: Dell GP107M [GeForce GTX 1050 Mobile] [1028:07be] InstallationDate: Installed on 2018-02-09 (0 days ago) InstallationMedia: Ubuntu 17.10
[Desktop-packages] [Bug 1221955] Re: GNOME_KEYRING_RESULT_IO_ERROR from launchpadlib
I believe this has been fixed in libsecret in
https://bugzilla.gnome.org/show_bug.cgi?id=778357.
** Bug watch added: GNOME Bug Tracker #778357
https://bugzilla.gnome.org/show_bug.cgi?id=778357
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-keyring in Ubuntu.
https://bugs.launchpad.net/bugs/1221955
Title:
GNOME_KEYRING_RESULT_IO_ERROR from launchpadlib
Status in GNOME Keyring:
Invalid
Status in gnome-keyring package in Ubuntu:
Confirmed
Status in gnome-keyring package in Debian:
Confirmed
Bug description:
I have no reliable way to reproduce it, but every now and then when
using pull-ppa-source (from lp:kubuntu-dev-tools) the script fails
with this error: (tokens stripped from output)
Gkr-Message: received an invalid, unencryptable, or non-utf8 secret
Gkr-Message: call to daemon returned an invalid response: (null).(null)()
Gkr-Message: received an invalid, unencryptable, or non-utf8 secret
Gkr-Message: call to daemon returned an invalid response: (null).(null)()
The authorization page:
(https://launchpad.net/+authorize-token?oauth_token=<>_permission=DESKTOP_INTEGRATION)
should be opening in your browser. Use your browser to authorize
this program to access Launchpad on your behalf.
Press any key to continue or wait (5) seconds...
Waiting to hear from Launchpad about your decision...
00:24:38 unnamed app(24933) ClientApp::doIt: Creating ClientApp
00:24:38 kioclient(24933) ClientApp::kde_open:
KUrl("https://launchpad.net/+authorize-token?oauth_token=<>_permission=DESKTOP_INTEGRATION")
00:24:38 kioclient(24933)/kio (KRun) KRun::slotTimeout: KRun(0x269dbe0)
slotTimeout called
00:24:38 kioclient(24933)/kio (KRun) KRun::init: INIT called
00:24:38 kioclient(24933)/kdecore (KSycoca) KSycocaPrivate::openDatabase:
Trying to open ksycoca from "/var/tmp/kdecache-yofel/ksycoca4"
00:24:38 kioclient(24933)/kfile (kdelibs) KRecentDocument::add:
KRecentDocument::add for
"https://launchpad.net/+authorize-token?oauth_token=<>_permission=DESKTOP_INT
EGRATION"
00:24:38 kioclient(24933)/kio (KRun) runTempService: runTempService: first
url
"https://launchpad.net/+authorize-token?oauth_token=<>_permission=DESKTOP_INTEGRATION"
00:24:38 kioclient(24933)/kio (KRun) supportedProtocols: supportedProtocols:
("KIO")
00:24:38 kioclient(24933)/kio (KRun) runTempService: runTempService: KProcess
args= ("/usr/bin/firefox",
"https://launchpad.net/+authorize-token?oauth_token=<>_permiss
ion=DESKTOP_INTEGRATION")
00:24:38 kioclient(24933)/kdecore (KStartupInfo)
KStartupInfo::createNewStartupId: creating:
"yofel-T510;1378506278;233618;24933_TIME0" : ""
00:24:38 kioclient(24933)/kdecore (KStartupInfo) KStartupInfo::sendStartup:
sending "new: ID="yofel-T510;1378506278;233618;24933_TIME0" BIN="firefox"
DESCRIPTION="Launching " DESKTOP=1 WM
CLASS="0" HOSTNAME=yofel-T510 NAME="firefox" SCREEN=0"
00:24:38 kioclient(24933)/kdecore (KStartupInfo) KStartupInfo::sendChange:
sending "change: ID="yofel-T510;1378506278;233618;24933_TIME0" PID=24935"
00:24:38 kioclient(24933)/kio (KRun) KRun::slotTimeout: KRun(0x269dbe0)
slotTimeout called
(process:24935): GLib-CRITICAL **: g_slice_set_config: assertion
'sys_page_size == 0' failed
Gtk-Message: Failed to load module "canberra-gtk-module"
Gtk-Message: Failed to load module "canberra-gtk-module"
00:24:38 kioclient(24933)/kio (KRun) KProcessRunner::slotProcessExited:
"firefox" exitCode= 0 exitStatus= 0
00:24:38 kioclient(24933)/kdecore (KStartupInfo) KStartupInfo::sendFinish:
sending "remove: ID="yofel-T510;1378506278;233618;24933_TIME0"
HOSTNAME=yofel-T510 PID=24935"
Gkr-Message: secret service operation failed: The secret was transferred or
encrypted in an invalid way.
Traceback (most recent call last):
File "/usr/bin/pull-ppa-source", line 49, in
lp = Launchpad.login_with("pull-ppa-source", "production")
File "/usr/lib/python2.7/dist-packages/launchpadlib/launchpad.py", line
539, in login_with
credential_save_failed, version)
File "/usr/lib/python2.7/dist-packages/launchpadlib/launchpad.py", line
346, in _authorize_token_and_login
credentials = authorization_engine(credentials, credential_store)
File "/usr/lib/python2.7/dist-packages/launchpadlib/credentials.py", line
520, in __call__
credential_store.save(credentials, self.unique_consumer_id)
File "/usr/lib/python2.7/dist-packages/launchpadlib/credentials.py", line
276, in save
raise e
keyring.errors.PasswordSetError: GNOME_KEYRING_RESULT_IO_ERROR
Happens usually when using the kubuntu ppa packages batch backport
script which calls pull-ppa-source about 160 times (once for every KDE
SC source).
ProblemType: BugDistroRelease: Ubuntu 13.10
Package: gnome-keyring 3.8.2-0ubuntu3
ProcVersionSignature: Ubuntu 3.11.0-4.9-generic 3.11.0-rc7
Uname: Linux 3.11.0-4-generic x86_64
NonfreeKernelModules:
[Desktop-packages] [Bug 1681523] Re: [Launcher] missing right click options
@sbierman & @md-5 I'm not sure of the relationship between the two files, but in addition to `/usr/share/applications/gnome-terminal.desktop` you may also need to change `/usr/share/applications/org.gnome.Terminal.desktop` similarly. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1681523 Title: [Launcher] missing right click options Status in gnome-terminal package in Ubuntu: Confirmed Bug description: Running : Description: Ubuntu Zesty Zapus (development branch) Release: 17.04 Not sure where to postthis but... Just noticed that "Right Click" options for the "Terminal" App are missing when it's locked to the 'Launcher' side-bar. You used to get the option to open "Open a New Window" or "Open a New Tab" when you right clicked on the launcher icon. Now the only options are "Terminal", "Unlock from Launcher" and "Quit". ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: unity 7.5.0+17.04.20170407.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 378.13 Tue Feb 7 20:10:06 PST 2017 GCC version: gcc version 6.3.0 20170321 (Ubuntu 6.3.0-10ubuntu1) .proc.driver.nvidia.warnings.fbdev: Your system is not currently configured to drive a VGA console on the primary VGA device. The NVIDIA Linux graphics driver requires the use of a text-mode VGA console. Use of other console drivers including, but not limited to, vesafb, may result in corruption and stability problems, and is not supported. .tmp.unity_support_test.0: ApportVersion: 2.20.4-0ubuntu3 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: Mon Apr 10 18:44:46 2017 DistUpgraded: Fresh install DistroCodename: zesty DistroVariant: ubuntu GraphicsCard: NVIDIA Corporation GK208 [GeForce GT 710B] [10de:128b] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ZOTAC International (MCO) Ltd. GK208 [GeForce GT 710B] [19da:7326] InstallationDate: Installed on 2017-03-04 (36 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170303) MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. ProcEnviron: LANGUAGE=en_GB:en TERM=xterm-256color PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic.efi.signed root=UUID=4b931084-da89-4473-81b2-7b6e8d83488e ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/19/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: FC dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: F2A78M-HD2 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrFC:bd01/19/2016:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnF2A78M-HD2:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz 1:0.9.13.1+17.04.20170109-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.76-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.3-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.3-1ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.14-0ubuntu1 xserver.bootTime: Mon Apr 10 18:43:48 2017 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.19.3-1ubuntu1 To manage notifications about this bug go to:
[Desktop-packages] [Bug 1714810] Re: gnome-terminal shrinks window to nothing
I already confirmed the "non-symmetric" behavior:
> the following padding does NOT cause the problem:
> padding: 1px 1px 1px 1px;
> The following padding DOES cause the problem:
> padding: 2px 1px 1px 1px;
Regarding scrollbars with un-filled space, I guess Linux will keep
sucking on the desktop for the foreseeable future for political reasons
:-)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-terminal in Ubuntu.
https://bugs.launchpad.net/bugs/1714810
Title:
gnome-terminal shrinks window to nothing
Status in gnome-terminal package in Ubuntu:
New
Bug description:
Using Ubuntu 17.04, vim, in gnome-terminal. Default everythings from
the desktop install, default Theme. The only change is the default
window size in the settings -- I have it at 149x48. This bug happens
even with the default 80x24 window size. The font is the default (not
overridden) Monospace Regular 12.
When running vim in gnome-terminal, there is an ugly margin of
terminal-background color on the right/bottom of the terminal window.
My vim background is gray, my terminal background is green, vim
displays gray background but there is a green border just slightly
slimmer than one character cell on the right/bottom. This also happens
for other terminal programs (including the shell) if they set the
background color of output.
In an attempt to at least make this less ugly, I tried to add some
padding to the terminal to center the drawable area that vim paints
with the background. I added the following to my gtk.css:
$ cat .config/gtk-3.0/gtk.css
vte-terminal {
padding: 8px 8px 5px 1px;
}
Now, when I open gnome-terminal, it keeps resizing itself to be
shorter in the Y axis, one line at a time, until it is only one line
high. It's almost like an animation of the window height, collapsing
the window to be very short. After it stops there, I can manually snap
the terminal to top/bottom edges of the screen, and it will stay
there, but trying to resize it will just keep shrinking the height.
This bug is about the resizing behavior. My totally uneducated guess
is that there's some off-by-one error when allocating space for the
terminal window contents. Terminal calculates contents, sets the
window, measures contents, decides to attempt to "snap" to size of
character cell, rounds down, window gets shorter, terminal measures
contents, decides to attempt to "snap" to size of character cell,
rounds down, window gets shorter, ...
If that is, indeed, the case, then the other bug (the ugly border) may
be caused by the same problem, but I will file a separate bug for
that.
$ lsb_release -rd
Description: Ubuntu 17.04
Release: 17.04
$ apt-cache policy gnome-terminal
gnome-terminal:
Installed: 3.20.2-1ubuntu8
Candidate: 3.20.2-1ubuntu8
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1714810/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1714810] Re: gnome-terminal shrinks window to nothing
Thanks for the pointer!
The window in the screen shot is taken with zero configured padding. The
green strip between the gray vim background and the orange scroll bar is
all ugly padding added by gnome-terminal.
It sounds from your description as if the real problem is in "vte" which is
used by gnome-terminal?
Note that, in the worst of cases, when I maximize a window and get a green
border on the bottom, I will sometimes get a line of text "stuck" there, and
it's inaccessible by any normal editor commands or cursor movement. I can't
reproduce this on demand (yet) though.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-terminal in Ubuntu.
https://bugs.launchpad.net/bugs/1714810
Title:
gnome-terminal shrinks window to nothing
Status in gnome-terminal package in Ubuntu:
New
Bug description:
Using Ubuntu 17.04, vim, in gnome-terminal. Default everythings from
the desktop install, default Theme. The only change is the default
window size in the settings -- I have it at 149x48. This bug happens
even with the default 80x24 window size. The font is the default (not
overridden) Monospace Regular 12.
When running vim in gnome-terminal, there is an ugly margin of
terminal-background color on the right/bottom of the terminal window.
My vim background is gray, my terminal background is green, vim
displays gray background but there is a green border just slightly
slimmer than one character cell on the right/bottom. This also happens
for other terminal programs (including the shell) if they set the
background color of output.
In an attempt to at least make this less ugly, I tried to add some
padding to the terminal to center the drawable area that vim paints
with the background. I added the following to my gtk.css:
$ cat .config/gtk-3.0/gtk.css
vte-terminal {
padding: 8px 8px 5px 1px;
}
Now, when I open gnome-terminal, it keeps resizing itself to be
shorter in the Y axis, one line at a time, until it is only one line
high. It's almost like an animation of the window height, collapsing
the window to be very short. After it stops there, I can manually snap
the terminal to top/bottom edges of the screen, and it will stay
there, but trying to resize it will just keep shrinking the height.
This bug is about the resizing behavior. My totally uneducated guess
is that there's some off-by-one error when allocating space for the
terminal window contents. Terminal calculates contents, sets the
window, measures contents, decides to attempt to "snap" to size of
character cell, rounds down, window gets shorter, terminal measures
contents, decides to attempt to "snap" to size of character cell,
rounds down, window gets shorter, ...
If that is, indeed, the case, then the other bug (the ugly border) may
be caused by the same problem, but I will file a separate bug for
that.
$ lsb_release -rd
Description: Ubuntu 17.04
Release: 17.04
$ apt-cache policy gnome-terminal
gnome-terminal:
Installed: 3.20.2-1ubuntu8
Candidate: 3.20.2-1ubuntu8
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1714810/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1714810] Re: gnome-terminal shrinks window to nothing
Output of "lshw"
** Attachment added: "lshw"
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1714810/+attachment/4944297/+files/hw.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-terminal in Ubuntu.
https://bugs.launchpad.net/bugs/1714810
Title:
gnome-terminal shrinks window to nothing
Status in gnome-terminal package in Ubuntu:
New
Bug description:
Using Ubuntu 17.04, vim, in gnome-terminal. Default everythings from
the desktop install, default Theme. The only change is the default
window size in the settings -- I have it at 149x48. This bug happens
even with the default 80x24 window size. The font is the default (not
overridden) Monospace Regular 12.
When running vim in gnome-terminal, there is an ugly margin of
terminal-background color on the right/bottom of the terminal window.
My vim background is gray, my terminal background is green, vim
displays gray background but there is a green border just slightly
slimmer than one character cell on the right/bottom. This also happens
for other terminal programs (including the shell) if they set the
background color of output.
In an attempt to at least make this less ugly, I tried to add some
padding to the terminal to center the drawable area that vim paints
with the background. I added the following to my gtk.css:
$ cat .config/gtk-3.0/gtk.css
vte-terminal {
padding: 8px 8px 5px 1px;
}
Now, when I open gnome-terminal, it keeps resizing itself to be
shorter in the Y axis, one line at a time, until it is only one line
high. It's almost like an animation of the window height, collapsing
the window to be very short. After it stops there, I can manually snap
the terminal to top/bottom edges of the screen, and it will stay
there, but trying to resize it will just keep shrinking the height.
This bug is about the resizing behavior. My totally uneducated guess
is that there's some off-by-one error when allocating space for the
terminal window contents. Terminal calculates contents, sets the
window, measures contents, decides to attempt to "snap" to size of
character cell, rounds down, window gets shorter, terminal measures
contents, decides to attempt to "snap" to size of character cell,
rounds down, window gets shorter, ...
If that is, indeed, the case, then the other bug (the ugly border) may
be caused by the same problem, but I will file a separate bug for
that.
$ lsb_release -rd
Description: Ubuntu 17.04
Release: 17.04
$ apt-cache policy gnome-terminal
gnome-terminal:
Installed: 3.20.2-1ubuntu8
Candidate: 3.20.2-1ubuntu8
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1714810/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1714810] Re: gnome-terminal shrinks window to nothing
output of "dpkg -l"
** Attachment added: "dpkg -l"
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1714810/+attachment/4944298/+files/dpkg.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-terminal in Ubuntu.
https://bugs.launchpad.net/bugs/1714810
Title:
gnome-terminal shrinks window to nothing
Status in gnome-terminal package in Ubuntu:
New
Bug description:
Using Ubuntu 17.04, vim, in gnome-terminal. Default everythings from
the desktop install, default Theme. The only change is the default
window size in the settings -- I have it at 149x48. This bug happens
even with the default 80x24 window size. The font is the default (not
overridden) Monospace Regular 12.
When running vim in gnome-terminal, there is an ugly margin of
terminal-background color on the right/bottom of the terminal window.
My vim background is gray, my terminal background is green, vim
displays gray background but there is a green border just slightly
slimmer than one character cell on the right/bottom. This also happens
for other terminal programs (including the shell) if they set the
background color of output.
In an attempt to at least make this less ugly, I tried to add some
padding to the terminal to center the drawable area that vim paints
with the background. I added the following to my gtk.css:
$ cat .config/gtk-3.0/gtk.css
vte-terminal {
padding: 8px 8px 5px 1px;
}
Now, when I open gnome-terminal, it keeps resizing itself to be
shorter in the Y axis, one line at a time, until it is only one line
high. It's almost like an animation of the window height, collapsing
the window to be very short. After it stops there, I can manually snap
the terminal to top/bottom edges of the screen, and it will stay
there, but trying to resize it will just keep shrinking the height.
This bug is about the resizing behavior. My totally uneducated guess
is that there's some off-by-one error when allocating space for the
terminal window contents. Terminal calculates contents, sets the
window, measures contents, decides to attempt to "snap" to size of
character cell, rounds down, window gets shorter, terminal measures
contents, decides to attempt to "snap" to size of character cell,
rounds down, window gets shorter, ...
If that is, indeed, the case, then the other bug (the ugly border) may
be caused by the same problem, but I will file a separate bug for
that.
$ lsb_release -rd
Description: Ubuntu 17.04
Release: 17.04
$ apt-cache policy gnome-terminal
gnome-terminal:
Installed: 3.20.2-1ubuntu8
Candidate: 3.20.2-1ubuntu8
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1714810/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1714810] Re: gnome-terminal shrinks window to nothing
Thanks for your answer!
Yes, the ugly margin is there even when not maximizing the terminal and even
when not using a css override file. (I removed the css override so I can keep
working.)
I'm attaching a screen shot (the ugly border is only on the right side,
probably scroll bar related?)
Also worthy of note (sorry, spaced on this last time): I installed this as
Ubuntu Server, and then added the desktop by doing sudo apt install
ubuntu-desktop. I have also installed the NVIDIA CUDA tools, which installs the
NVIDIA 375 driver.
Interestingly, my control panels don't have any option to select default window
chrome sizes or font sizes, although the Terminal application itself does. I
wonder if ubuntu-desktop doesn't actually include *everything* it needs. (I
also noted that gnome-screenshot wasn't installed by default; I had to install
it manually.)
The version of ubuntu-desktop is 1.379 and the version of unity is
7.5.0+17.04.20170407.1-0ubuntu1
Regarding "symmetric" margins, the following padding does NOT cause the problem:
padding: 1px 1px 1px 1px;
The following padding DOES cause the problem:
padding: 2px 1px 1px 1px;
** Attachment added: "screen shot of ugly margin and versions"
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1714810/+attachment/4944285/+files/Screenshot%20from%202017-09-04%2010-34-02.png
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-terminal in Ubuntu.
https://bugs.launchpad.net/bugs/1714810
Title:
gnome-terminal shrinks window to nothing
Status in gnome-terminal package in Ubuntu:
New
Bug description:
Using Ubuntu 17.04, vim, in gnome-terminal. Default everythings from
the desktop install, default Theme. The only change is the default
window size in the settings -- I have it at 149x48. This bug happens
even with the default 80x24 window size. The font is the default (not
overridden) Monospace Regular 12.
When running vim in gnome-terminal, there is an ugly margin of
terminal-background color on the right/bottom of the terminal window.
My vim background is gray, my terminal background is green, vim
displays gray background but there is a green border just slightly
slimmer than one character cell on the right/bottom. This also happens
for other terminal programs (including the shell) if they set the
background color of output.
In an attempt to at least make this less ugly, I tried to add some
padding to the terminal to center the drawable area that vim paints
with the background. I added the following to my gtk.css:
$ cat .config/gtk-3.0/gtk.css
vte-terminal {
padding: 8px 8px 5px 1px;
}
Now, when I open gnome-terminal, it keeps resizing itself to be
shorter in the Y axis, one line at a time, until it is only one line
high. It's almost like an animation of the window height, collapsing
the window to be very short. After it stops there, I can manually snap
the terminal to top/bottom edges of the screen, and it will stay
there, but trying to resize it will just keep shrinking the height.
This bug is about the resizing behavior. My totally uneducated guess
is that there's some off-by-one error when allocating space for the
terminal window contents. Terminal calculates contents, sets the
window, measures contents, decides to attempt to "snap" to size of
character cell, rounds down, window gets shorter, terminal measures
contents, decides to attempt to "snap" to size of character cell,
rounds down, window gets shorter, ...
If that is, indeed, the case, then the other bug (the ugly border) may
be caused by the same problem, but I will file a separate bug for
that.
$ lsb_release -rd
Description: Ubuntu 17.04
Release: 17.04
$ apt-cache policy gnome-terminal
gnome-terminal:
Installed: 3.20.2-1ubuntu8
Candidate: 3.20.2-1ubuntu8
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1714810/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1408963] Re: [Xbuntu 14.04, 14.10 and 15.04] Network manager stops working: iwl3945 0000:03:00.0: BSM uCode verification failed at addr ...; wlan0: deauthenticating from... by
This affects me as well. I have trace information in the attached syslog. Below are the outputs from: * lsb_release -a * apt-cache policy network-manager * hwinfo --netcard - jss $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 16.04.3 LTS Release:16.04 Codename: xenial $ apt-cache policy network-manager network-manager: Installed: 1.2.6-0ubuntu0.16.04.1 Candidate: 1.2.6-0ubuntu0.16.04.1 Version table: *** 1.2.6-0ubuntu0.16.04.1 500 500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main i386 Packages 100 /var/lib/dpkg/status 1.2.2-0ubuntu0.16.04.4 500 500 http://security.ubuntu.com/ubuntu xenial-security/main i386 Packages 1.1.93-0ubuntu4 500 500 http://us.archive.ubuntu.com/ubuntu xenial/main i386 Packages $ hwinfo --netcard 24: PCI 200.0: 0200 Ethernet controller [Created at pci.366] Unique ID: rBUF.DLcddtZ5wl3 Parent ID: z8Q3.lhbiXmvIKtB SysFS ID: /devices/pci:00/:00:1c.0/:02:00.0 SysFS BusID: :02:00.0 Hardware Class: network Model: "Lenovo ThinkPad X60/X60s" Vendor: pci 0x8086 "Intel Corporation" Device: pci 0x109a "82573L Gigabit Ethernet Controller" SubVendor: pci 0x17aa "Lenovo" SubDevice: pci 0x207e "ThinkPad X60/X60s" Driver: "e1000e" Driver Modules: "e1000e" Device File: eth0 Memory Range: 0xee00-0xee01 (rw,non-prefetchable) I/O Ports: 0x2000-0x201f (rw) IRQ: 28 (1760 events) HW Address: 00:16:d3:31:a0:90 Link detected: no Module Alias: "pci:v8086d109Asv17AAsd207Ebc02sc00i00" Driver Info #0: Driver Status: e1000e is active Driver Activation Cmd: "modprobe e1000e" Config Status: cfg=new, avail=yes, need=no, active=unknown Attached to: #10 (PCI bridge) 25: PCI 300.0: 0282 WLAN controller [Created at pci.366] Unique ID: y9sn.FZoxbnX_PE2 Parent ID: qTvu.nWUCVv8jNeC SysFS ID: /devices/pci:00/:00:1c.1/:03:00.0 SysFS BusID: :03:00.0 Hardware Class: network Model: "Intel PRO/Wireless 3945ABG [Golan] Network Connection" Vendor: pci 0x8086 "Intel Corporation" Device: pci 0x4227 "PRO/Wireless 3945ABG [Golan] Network Connection" SubVendor: pci 0x8086 "Intel Corporation" SubDevice: pci 0x1010 Revision: 0x02 Driver: "iwl3945" Driver Modules: "iwl3945" Device File: wlan0 Features: WLAN Memory Range: 0xedf0-0xedf00fff (rw,non-prefetchable) IRQ: 31 (120102 events) HW Address: 00:18:de:66:4b:57 Link detected: yes WLAN channels: 1 2 3 4 5 6 7 8 9 10 11 36 40 44 48 52 56 60 64 149 153 157 161 165 WLAN frequencies: 2.412 2.417 2.422 2.427 2.432 2.437 2.442 2.447 2.452 2.457 2.462 5.18 5.2 5.22 5.24 5.26 5.28 5.3 5.32 5.745 5.765 5.785 5.805 5.825 WLAN encryption modes: WEP40 WEP104 TKIP CCMP WLAN authentication modes: open sharedkey wpa-psk wpa-eap Module Alias: "pci:v8086d4227sv8086sd1010bc02sc80i00" Driver Info #0: Driver Status: iwl3945 is active Driver Activation Cmd: "modprobe iwl3945" Config Status: cfg=new, avail=yes, need=no, active=unknown Attached to: #11 (PCI bridge) ** Attachment added: "syslog" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1408963/+attachment/4944203/+files/syslog -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1408963 Title: [Xbuntu 14.04, 14.10 and 15.04] Network manager stops working: iwl3945 :03:00.0: BSM uCode verification failed at addr ...; wlan0: deauthenticating from... by local choice (Reason: 3=DEAUTH_LEAVING), Status in network-manager package in Ubuntu: Confirmed Bug description: From time to time, the system loses all wireles networks and kubuntu network manager applet goes blank - not even one network is shown. All wifi connections are broken. Rebooting fixes the issue, switching to WICD on-the-fly enables to continue browsing without rebooting, so it seems to be no hardware issue or iwl3945 issue. What to expect: stable connections and flawless network managing. What happens: so above. Further informations about the system, the network configuration, the package version can be found in the attachment, also parts of rsyslog and dmesg. Interesting, according to some helpers, are the following lines: dmesg: wlan0: deauthenticating from 02:26:4d:ac:8f:45 by local choice (Reason: 3=DEAUTH_LEAVING) lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 14.10 Release:14.10 Codename: utopic apt-cache policy network-manager network-manager: Installiert: 0.9.8.8-0ubuntu28 Installationskandidat: 0.9.8.8-0ubuntu28 Versionstabelle: *** 0.9.8.8-0ubuntu28 0 500 http://de.archive.ubuntu.com/ubuntu/ utopic/main amd64 Packages
[Desktop-packages] [Bug 1714810] [NEW] gnome-terminal shrinks window to nothing
Public bug reported:
Using Ubuntu 17.04, vim, in gnome-terminal. Default everythings from the
desktop install, default Theme. The only change is the default window
size in the settings -- I have it at 149x48. This bug happens even with
the default 80x24 window size. The font is the default (not overridden)
Monospace Regular 12.
When running vim in gnome-terminal, there is an ugly margin of terminal-
background color on the right/bottom of the terminal window. My vim
background is gray, my terminal background is green, vim displays gray
background but there is a green border just slightly slimmer than one
character cell on the right/bottom. This also happens for other terminal
programs (including the shell) if they set the background color of
output.
In an attempt to at least make this less ugly, I tried to add some
padding to the terminal to center the drawable area that vim paints with
the background. I added the following to my gtk.css:
$ cat .config/gtk-3.0/gtk.css
vte-terminal {
padding: 8px 8px 5px 1px;
}
Now, when I open gnome-terminal, it keeps resizing itself to be shorter
in the Y axis, one line at a time, until it is only one line high. It's
almost like an animation of the window height, collapsing the window to
be very short. After it stops there, I can manually snap the terminal to
top/bottom edges of the screen, and it will stay there, but trying to
resize it will just keep shrinking the height.
This bug is about the resizing behavior. My totally uneducated guess is
that there's some off-by-one error when allocating space for the
terminal window contents. Terminal calculates contents, sets the window,
measures contents, decides to attempt to "snap" to size of character
cell, rounds down, window gets shorter, terminal measures contents,
decides to attempt to "snap" to size of character cell, rounds down,
window gets shorter, ...
If that is, indeed, the case, then the other bug (the ugly border) may
be caused by the same problem, but I will file a separate bug for that.
$ lsb_release -rd
Description:Ubuntu 17.04
Release:17.04
$ apt-cache policy gnome-terminal
gnome-terminal:
Installed: 3.20.2-1ubuntu8
Candidate: 3.20.2-1ubuntu8
** Affects: gnome-terminal (Ubuntu)
Importance: Undecided
Status: New
** Attachment added: "screen capture showing the bug"
https://bugs.launchpad.net/bugs/1714810/+attachment/4943672/+files/2017-09-03-gnome-terminal-2017-09-03_10.44.05.mp4
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-terminal in Ubuntu.
https://bugs.launchpad.net/bugs/1714810
Title:
gnome-terminal shrinks window to nothing
Status in gnome-terminal package in Ubuntu:
New
Bug description:
Using Ubuntu 17.04, vim, in gnome-terminal. Default everythings from
the desktop install, default Theme. The only change is the default
window size in the settings -- I have it at 149x48. This bug happens
even with the default 80x24 window size. The font is the default (not
overridden) Monospace Regular 12.
When running vim in gnome-terminal, there is an ugly margin of
terminal-background color on the right/bottom of the terminal window.
My vim background is gray, my terminal background is green, vim
displays gray background but there is a green border just slightly
slimmer than one character cell on the right/bottom. This also happens
for other terminal programs (including the shell) if they set the
background color of output.
In an attempt to at least make this less ugly, I tried to add some
padding to the terminal to center the drawable area that vim paints
with the background. I added the following to my gtk.css:
$ cat .config/gtk-3.0/gtk.css
vte-terminal {
padding: 8px 8px 5px 1px;
}
Now, when I open gnome-terminal, it keeps resizing itself to be
shorter in the Y axis, one line at a time, until it is only one line
high. It's almost like an animation of the window height, collapsing
the window to be very short. After it stops there, I can manually snap
the terminal to top/bottom edges of the screen, and it will stay
there, but trying to resize it will just keep shrinking the height.
This bug is about the resizing behavior. My totally uneducated guess
is that there's some off-by-one error when allocating space for the
terminal window contents. Terminal calculates contents, sets the
window, measures contents, decides to attempt to "snap" to size of
character cell, rounds down, window gets shorter, terminal measures
contents, decides to attempt to "snap" to size of character cell,
rounds down, window gets shorter, ...
If that is, indeed, the case, then the other bug (the ugly border) may
be caused by the same problem, but I will file a separate bug for
that.
$ lsb_release -rd
Description: Ubuntu 17.04
Release: 17.04
$
[Desktop-packages] [Bug 1692477] Re: Thunderbird 52.1.1 no longer able to see remotely mounted folders
This looks very much like https://bugs.launchpad.net/bugs/1694129 which
I raised a week ago.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to thunderbird in Ubuntu.
https://bugs.launchpad.net/bugs/1692477
Title:
Thunderbird 52.1.1 no longer able to see remotely mounted folders
Status in thunderbird package in Ubuntu:
Confirmed
Bug description:
Since the upgrade of Thunderbird to 52.1.1 remotely mounted folders no
longer show up in the attach dialog window.
- What is happening
In nautilus mount a folder ("Connect to Server") from a remote server
- smb:// or ssh:// are the two I have tried.
Start a new email and go to attach a file from the remote folder. The
shared folder is not visible in the attach file dialog but is visible
in nautilus
- What should happen
In nautilus mount a folder ("Connect to Server") from a remote server
- smb:// or ssh:// are the two I have tried.
Start a new email and go to attach a file from the remote folder. I
can see the remote folder from the attach file dialog.
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 16.04.2 LTS
Release: 16.04
Codename: xenial
$ apt-cache policy thunderbird
thunderbird:
Installed: 1:52.1.1+build1-0ubuntu0.16.04.1
Candidate: 1:52.1.1+build1-0ubuntu0.16.04.1
Version table:
*** 1:52.1.1+build1-0ubuntu0.16.04.1 500
500 http://gb.archive.ubuntu.com/ubuntu xenial-updates/main amd64
Packages
500 http://security.ubuntu.com/ubuntu xenial-security/main amd64
Packages
100 /var/lib/dpkg/status
1:38.6.0+build1-0ubuntu1 500
500 http://gb.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1692477/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1694129] [NEW] Cannot attach Network Shares in Thunderbird
Public bug reported: Suddenly (and I'm not sure if this was after a recent Ubuntu update or a Thunderbird one, Thunderbird no longer shows "Network" locations in the 'Attach File(s)' window. Normally below "Bookmarks" is another section "Network" which shows my network locations, however this entire section is now missing. There is now no way of attaching a file existing anywhere on the network to an outgoing email. Nautilus can see and access all the network locations 100% fine. Drag/drop into the outgoing email from Nautilus will attach a network file to the email but Thunderbird refuses to send it and throws up a "Send Message Error": Sending of the message failed. There was an error attaching smb://mypc/my documents/myfolder/file.xls. Please check that you have access to the file. Attaching network files in Thunderbird and on Ubuntu 14.04 has worked fine for two years. I'm a "user" and really not that au-fait with the inner workings of Linux so I hope this helps. Thanks ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: thunderbird 1:52.1.1+build1-0ubuntu0.14.04.1 ProcVersionSignature: Ubuntu 3.13.0-119.166-generic 3.13.11-ckt39 Uname: Linux 3.13.0-119-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.14.1-0ubuntu3.24 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: jon2048 F pulseaudio BuildID: 20170512195315 Channel: Unavailable CurrentDesktop: Unity Date: Sun May 28 15:09:59 2017 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2014-12-10 (900 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) IpRoute: default via 192.168.1.1 dev wlan0 proto static 192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.7 metric 9 Locales: extensions.sqlite corrupt or missing Plugins: Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so PrefSources: prefs.js ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash Profiles: Profile0 (Default) - LastVersion=52.1.1/20170512195315 (In use) RunningIncompatibleAddons: False SourcePackage: thunderbird Themes: extensions.sqlite corrupt or missing UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: dmi.bios.date: 08/08/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X551CA.202 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X551CA 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.:bvrX551CA.202:bd08/08/2013:svnASUSTeKCOMPUTERINC.:pnX551CA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX551CA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: X551CA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. ** Affects: thunderbird (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1694129 Title: Cannot attach Network Shares in Thunderbird Status in thunderbird package in Ubuntu: New Bug description: Suddenly (and I'm not sure if this was after a recent Ubuntu update or a Thunderbird one, Thunderbird no longer shows "Network" locations in the 'Attach File(s)' window. Normally below "Bookmarks" is another section "Network" which shows my network locations, however this entire section is now missing. There is now no way of attaching a file existing anywhere on the network to an outgoing email. Nautilus can see and access all the network locations 100% fine. Drag/drop into the outgoing email from Nautilus will attach a network file to the email but Thunderbird refuses to send it and throws up a "Send Message Error": Sending of the message failed. There was an error attaching smb://mypc/my documents/myfolder/file.xls. Please check that you have access to the file. Attaching network files in Thunderbird and on Ubuntu 14.04 has worked fine for two years. I'm a "user" and really not that au-fait with the inner workings of Linux so I hope this helps. Thanks ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: thunderbird 1:52.1.1+build1-0ubuntu0.14.04.1 ProcVersionSignature: Ubuntu 3.13.0-119.166-generic 3.13.11-ckt39 Uname: Linux 3.13.0-119-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.14.1-0ubuntu3.24 Archit
[Desktop-packages] [Bug 1681523] Re: [Launcher] missing right click options
I raised this problem at https://askubuntu.com/q/904680/475088 For a temporary workaround, which at least gives you back the "New Terminal" context menu item: File "/usr/share/applications/gnome-terminal.desktop" includes line: OnlyShowIn=GNOME;Unity7; In 16.04 that line was: OnlyShowIn=GNOME;Unity; I changed line to remove the "7" (and remove locked icon and re-lock on Launcher) I now get "New Terminal" again on right-click. However, there is something odd, because although I can open a new terminal now from that icon, it launches a single new icon for the new terminal and that one does not offer "New Terminal". -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1681523 Title: [Launcher] missing right click options Status in gnome-terminal package in Ubuntu: Confirmed Bug description: Running : Description: Ubuntu Zesty Zapus (development branch) Release: 17.04 Not sure where to postthis but... Just noticed that "Right Click" options for the "Terminal" App are missing when it's locked to the 'Launcher' side-bar. You used to get the option to open "Open a New Window" or "Open a New Tab" when you right clicked on the launcher icon. Now the only options are "Terminal", "Unlock from Launcher" and "Quit". ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: unity 7.5.0+17.04.20170407.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 378.13 Tue Feb 7 20:10:06 PST 2017 GCC version: gcc version 6.3.0 20170321 (Ubuntu 6.3.0-10ubuntu1) .proc.driver.nvidia.warnings.fbdev: Your system is not currently configured to drive a VGA console on the primary VGA device. The NVIDIA Linux graphics driver requires the use of a text-mode VGA console. Use of other console drivers including, but not limited to, vesafb, may result in corruption and stability problems, and is not supported. .tmp.unity_support_test.0: ApportVersion: 2.20.4-0ubuntu3 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: Mon Apr 10 18:44:46 2017 DistUpgraded: Fresh install DistroCodename: zesty DistroVariant: ubuntu GraphicsCard: NVIDIA Corporation GK208 [GeForce GT 710B] [10de:128b] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ZOTAC International (MCO) Ltd. GK208 [GeForce GT 710B] [19da:7326] InstallationDate: Installed on 2017-03-04 (36 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170303) MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. ProcEnviron: LANGUAGE=en_GB:en TERM=xterm-256color PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic.efi.signed root=UUID=4b931084-da89-4473-81b2-7b6e8d83488e ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/19/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: FC dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: F2A78M-HD2 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrFC:bd01/19/2016:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnF2A78M-HD2:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz 1:0.9.13.1+17.04.20170109-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.76-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.3-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.3-1ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel
[Desktop-packages] [Bug 1672459] [NEW] incorrectly asks for password on .pdf file
Public bug reported: Ubuntu 12.04.3 LTS, evince 3.4.0, just updated it with apt-get and still shows the problem. Here's a file that asks for password : https://www.fairchildsemi.com/datasheets/FO/FODM121.pdf But, it seems a bunch of Fairchild semi files have the same problem. Reads fine with acroread, asks for a password in evince. apt-cache shows : evince: Installed: 3.4.0-0ubuntu1.8 Candidate: 3.4.0-0ubuntu1.8 Version table: *** 3.4.0-0ubuntu1.8 0 500 http://us.archive.ubuntu.com/ubuntu/ precise-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.4.0-0ubuntu1 0 500 http://us.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages Thanks, Jon ** Affects: evince (Ubuntu) Importance: Undecided Status: New -- 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/1672459 Title: incorrectly asks for password on .pdf file Status in evince package in Ubuntu: New Bug description: Ubuntu 12.04.3 LTS, evince 3.4.0, just updated it with apt-get and still shows the problem. Here's a file that asks for password : https://www.fairchildsemi.com/datasheets/FO/FODM121.pdf But, it seems a bunch of Fairchild semi files have the same problem. Reads fine with acroread, asks for a password in evince. apt-cache shows : evince: Installed: 3.4.0-0ubuntu1.8 Candidate: 3.4.0-0ubuntu1.8 Version table: *** 3.4.0-0ubuntu1.8 0 500 http://us.archive.ubuntu.com/ubuntu/ precise-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.4.0-0ubuntu1 0 500 http://us.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages Thanks, Jon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1672459/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1585551] Re: gnome-settings-daemon leaking memory after idle
FIX: Finally found a solution that does not require me to disable screen blanking and turning my monitors off physically: 1. Run dconf-editor 2. org > gnome > settings-daemon > plugins > power 3. "Set to Default" on ALL keys (this sets GNOME to never blank the screen since "sleep-inactive-ac-timeout" and "sleep-inactive-battery-timeout" defaults to 0), then UNCHECK "active", so it is false 4. Run a command at login like this: "bash -c "sleep 10 && xset dpms 0 0 900" (sleep for 10 seconds avoids GNOME taking over) 5. I also disabled the "housekeeping", "orientation" and "xrandr" plugins as they are not needed for me I strongly suspect it has to do with my dual monitor setup (DVI and HDMI), and that the bug may exist in newer GNOME versions as well. Will check later with a live USB stick. Cheers. ** Changed in: gnome-settings-daemon (Ubuntu) Status: Invalid => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1585551 Title: gnome-settings-daemon leaking memory after idle Status in gnome-settings-daemon package in Ubuntu: Confirmed Bug description: Hi When my system goes to idle (lock and black screen), GDM starts to get slow. and if I let it be in idle for longer time it will be more and more slow. Also at this point the gnome-shell is slow too and gnome-settings- daemon starts to leak memory. again with more idle time gnome-shell will be more slow an gnome-settings-daemon will leaks more memory from 7MB up to more than 7GB. (ending process of gnome-settings-daemon and restarting shell with "r" command fixes these problems until next idle) I'm using gnome ppa (ppa:gnome3-team/gnome3) I have reported a bug for GDM3 too https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1581937 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gnome-settings-daemon 3.18.2-0ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME Date: Wed May 25 13:53:27 2016 InstallationDate: Installed on 2016-04-22 (32 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 (20160421) SourcePackage: gnome-settings-daemon UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1585551/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1585551] Re: gnome-settings-daemon leaking memory after idle
Running Alt + F2 and then "r" to restart GNOME Shell helps speed up everything again, because AFAIK it restarts gnome-settings-daemon, but after that it still uses relatively much more RAM than after a reboot. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1585551 Title: gnome-settings-daemon leaking memory after idle Status in gnome-settings-daemon package in Ubuntu: Invalid Bug description: Hi When my system goes to idle (lock and black screen), GDM starts to get slow. and if I let it be in idle for longer time it will be more and more slow. Also at this point the gnome-shell is slow too and gnome-settings- daemon starts to leak memory. again with more idle time gnome-shell will be more slow an gnome-settings-daemon will leaks more memory from 7MB up to more than 7GB. (ending process of gnome-settings-daemon and restarting shell with "r" command fixes these problems until next idle) I'm using gnome ppa (ppa:gnome3-team/gnome3) I have reported a bug for GDM3 too https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1581937 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gnome-settings-daemon 3.18.2-0ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME Date: Wed May 25 13:53:27 2016 InstallationDate: Installed on 2016-04-22 (32 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 (20160421) SourcePackage: gnome-settings-daemon UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1585551/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1585551] Re: gnome-settings-daemon leaking memory after idle
Running Valgrind as described here: https://bugzilla.redhat.com/show_bug.cgi?id=1321995 ...I get the content in the attachment, not very helpful it seems? Also see my screenshot above. Note: It should be noted that I run a dual monitor setup with one monitor on DVI and another on HDMI. Saw a forum post or something suggesting that it could affect it. I don't have a way to know. But it only happens on this computer, not on a Intel NUC running the same distro (but not same HW) connected to my TV. ** Bug watch added: Red Hat Bugzilla #1321995 https://bugzilla.redhat.com/show_bug.cgi?id=1321995 ** Attachment added: "valgrind.log" https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1585551/+attachment/4827649/+files/valgrind.log -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1585551 Title: gnome-settings-daemon leaking memory after idle Status in gnome-settings-daemon package in Ubuntu: Invalid Bug description: Hi When my system goes to idle (lock and black screen), GDM starts to get slow. and if I let it be in idle for longer time it will be more and more slow. Also at this point the gnome-shell is slow too and gnome-settings- daemon starts to leak memory. again with more idle time gnome-shell will be more slow an gnome-settings-daemon will leaks more memory from 7MB up to more than 7GB. (ending process of gnome-settings-daemon and restarting shell with "r" command fixes these problems until next idle) I'm using gnome ppa (ppa:gnome3-team/gnome3) I have reported a bug for GDM3 too https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1581937 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gnome-settings-daemon 3.18.2-0ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME Date: Wed May 25 13:53:27 2016 InstallationDate: Installed on 2016-04-22 (32 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 (20160421) SourcePackage: gnome-settings-daemon UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1585551/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1585551] Re: gnome-settings-daemon leaking memory after idle
See attachment. gnome-settings-daemon eating 65 % of my 8 GB RAM less than 24 hours after a reboot. ** Attachment added: "Bug.png" https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1585551/+attachment/4827646/+files/Bug.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1585551 Title: gnome-settings-daemon leaking memory after idle Status in gnome-settings-daemon package in Ubuntu: Invalid Bug description: Hi When my system goes to idle (lock and black screen), GDM starts to get slow. and if I let it be in idle for longer time it will be more and more slow. Also at this point the gnome-shell is slow too and gnome-settings- daemon starts to leak memory. again with more idle time gnome-shell will be more slow an gnome-settings-daemon will leaks more memory from 7MB up to more than 7GB. (ending process of gnome-settings-daemon and restarting shell with "r" command fixes these problems until next idle) I'm using gnome ppa (ppa:gnome3-team/gnome3) I have reported a bug for GDM3 too https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1581937 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gnome-settings-daemon 3.18.2-0ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME Date: Wed May 25 13:53:27 2016 InstallationDate: Installed on 2016-04-22 (32 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 (20160421) SourcePackage: gnome-settings-daemon UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1585551/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1585551] Re: gnome-settings-daemon leaking memory after idle
Same her on Ubuntu GNOME 16.04 64-bit with GNOME 3 Team PPA. gnome- settings-daemon can eat up my 8 GB RAM after time, and then desktop 3D animations are very slow/choppy. Solution is to log out and in again. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1585551 Title: gnome-settings-daemon leaking memory after idle Status in gnome-settings-daemon package in Ubuntu: Invalid Bug description: Hi When my system goes to idle (lock and black screen), GDM starts to get slow. and if I let it be in idle for longer time it will be more and more slow. Also at this point the gnome-shell is slow too and gnome-settings- daemon starts to leak memory. again with more idle time gnome-shell will be more slow an gnome-settings-daemon will leaks more memory from 7MB up to more than 7GB. (ending process of gnome-settings-daemon and restarting shell with "r" command fixes these problems until next idle) I'm using gnome ppa (ppa:gnome3-team/gnome3) I have reported a bug for GDM3 too https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1581937 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gnome-settings-daemon 3.18.2-0ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME Date: Wed May 25 13:53:27 2016 InstallationDate: Installed on 2016-04-22 (32 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 (20160421) SourcePackage: gnome-settings-daemon UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1585551/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1656302] [NEW] USB sound card intermittant/unable to play audio
Public bug reported: I have a EDIROL UA-1A USB soundcard which for the most part under 12.04 worked however after a period of uptime, ALSA calls started failing with messages of this nature: ALSA lib pcm_dmix.c:1022:(snd_pcm_dmix_open) unable to open slave ALSA lib pcm_dmix.c:1022:(snd_pcm_dmix_open) unable to open slave ALSA lib pcm_dmix.c:1022:(snd_pcm_dmix_open) unable to open slave ALSA lib pcm_dmix.c:1022:(snd_pcm_dmix_open) unable to open slave and the kernel ring buffer would have streams of: [673754.825092] xhci_hcd :02:00.0: ERROR Transfer event TRB DMA ptr not part of current TD [673754.830412] xhci_hcd :02:00.0: ERROR Transfer event TRB DMA ptr not part of current TD and: [673429.575699] retire_capture_urb: 596 callbacks suppressed sometimes unplugging/plugging the card would fix this, other times a system reboot was required. Since the upgrade to 14.04 this seems to have got worse in that most of the time it behaves in this manner and the unplugging/plugging approach never works. From a kernel perspective, I was already running a 3.13.x release with 12.04 so there's not been a major update on this front since the upgrade. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: pulseaudio 1:4.0-0ubuntu11.1 ProcVersionSignature: Ubuntu 3.13.0-106.153-generic 3.13.11-ckt39 Uname: Linux 3.13.0-106-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.23 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jon 25970 F pulseaudio /dev/snd/pcmC0D0c: jon 25970 F...m pulseaudio /dev/snd/pcmC0D0p: jon 25970 F...m pulseaudio CurrentDesktop: LXDE Date: Fri Jan 13 12:56:13 2017 InstallationDate: Installed on 2013-07-25 (1268 days ago) InstallationMedia: Ubuntu-Server 12.04.2 LTS "Precise Pangolin" - Release amd64 (20130214) ProcEnviron: LANGUAGE=en_GB:en TERM=xterm PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio Symptom: audio UpgradeStatus: Upgraded to trusty on 2016-12-28 (15 days ago) dmi.bios.date: 02/22/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: X9SBAA dmi.board.vendor: Supermicro dmi.board.version: 0123456789 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 17 dmi.chassis.vendor: Supermicro dmi.chassis.version: 0123456789 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd02/22/2013:svnSupermicro:pnX9SBAA:pvr0123456789:rvnSupermicro:rnX9SBAA:rvr0123456789:cvnSupermicro:ct17:cvr0123456789: dmi.product.name: X9SBAA dmi.product.version: 0123456789 dmi.sys.vendor: Supermicro ** Affects: ubuntu Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages trusty ** Package changed: pulseaudio (Ubuntu) => ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1656302 Title: USB sound card intermittant/unable to play audio Status in Ubuntu: New Bug description: I have a EDIROL UA-1A USB soundcard which for the most part under 12.04 worked however after a period of uptime, ALSA calls started failing with messages of this nature: ALSA lib pcm_dmix.c:1022:(snd_pcm_dmix_open) unable to open slave ALSA lib pcm_dmix.c:1022:(snd_pcm_dmix_open) unable to open slave ALSA lib pcm_dmix.c:1022:(snd_pcm_dmix_open) unable to open slave ALSA lib pcm_dmix.c:1022:(snd_pcm_dmix_open) unable to open slave and the kernel ring buffer would have streams of: [673754.825092] xhci_hcd :02:00.0: ERROR Transfer event TRB DMA ptr not part of current TD [673754.830412] xhci_hcd :02:00.0: ERROR Transfer event TRB DMA ptr not part of current TD and: [673429.575699] retire_capture_urb: 596 callbacks suppressed sometimes unplugging/plugging the card would fix this, other times a system reboot was required. Since the upgrade to 14.04 this seems to have got worse in that most of the time it behaves in this manner and the unplugging/plugging approach never works. From a kernel perspective, I was already running a 3.13.x release with 12.04 so there's not been a major update on this front since the upgrade. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: pulseaudio 1:4.0-0ubuntu11.1 ProcVersionSignature: Ubuntu 3.13.0-106.153-generic 3.13.11-ckt39 Uname: Linux 3.13.0-106-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.23 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jon 25970 F pulseaudio /dev/snd/pcmC0D0c: jon 25970 F...m pulseaudio /dev/snd/pcmC0D0p: jon 25970 F...m pulseaudio CurrentDesktop: LXDE Date: Fri Jan 13 12:56:13 2017 InstallationDate: Installed on 2013-07-25 (1268 days ago) InstallationMedia: Ubuntu-Server 12.04.2 LTS "Precise Pangolin" - Release amd64 (20130214) P
[Desktop-packages] [Bug 1250196] Re: HP Scanject 2100c not working on USB 3 root hub
I've performed the upgrade from 12.04 to 14.04 over the Christmas break which has restored all the repositories back to default (I was using the PPA from Rolf's PPA to work round this) and can confirm it's all working now. There's still the massive delay on the start of the initial scan (as mentioned in #32) which consumes 100% of the CPU but I can live with that. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to sane-backends in Ubuntu. https://bugs.launchpad.net/bugs/1250196 Title: HP Scanject 2100c not working on USB 3 root hub Status in sane-backends package in Ubuntu: Incomplete Bug description: I have a HP Scanject 2100c which uses the Sane plustek backend for comms. My PC only has a USB 3 root hub, when the device is connected, either directly or via an external USB 2 hub, it does not work. In general (although not always), 'scanimage -L' will detect the scanner ok: device `plustek:libusb:001:012' is a Hewlett-Packard Scanjet 2100c flatbed scanner however there is always about a 30s delay before the shell prompt is returned. Scanning always fails however, using the suggested method on the sane HOW-TO page: scanimage -vvv -format pnm >outfile.pnm Calling sane_exit is the usual response. By enabling debug on the plustek backend, the response I normally get results in the following: [plustek] Vendor ID=0x03F0, Product ID=0x0505 [plustek] usbio_DetectLM983x [plustek] * could not read version register! [plustek] open failed: -1 [plustek] sane_get_devices (0x7fff0686dbc8, 0) In an effort to try and diagnose this, I've build the latest SANE backends from scratch and tried out the latest libusb none of which has resolved the issue. My original kernel was a 3.5.x, I pushed it up to 3.8.0-30 this also made no difference. My guess based on what I've seen is that this is related to the USB 3 hub. The HP Scanjet worked ok on my old Linux box (a 2.6.27 kernel with USB 2 hub). The key difference (aside from this being a 64 bit flavour of Linux) is the USB. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: libsane 1.0.22-7ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-30.44~precise1-generic 3.8.13.6 Uname: Linux 3.8.0-30-generic x86_64 ApportVersion: 2.0.1-0ubuntu17.5 Architecture: amd64 Date: Mon Nov 11 19:41:08 2013 InstallationMedia: Ubuntu-Server 12.04.2 LTS "Precise Pangolin" - Release amd64 (20130214) MarkForUpload: True ProcEnviron: LANGUAGE=en_GB:en TERM=xterm PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: sane-backends UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1250196/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1605260] Re: Memory leak in libnl-3 (3.2.21-1ubuntu3) in 14.04
Discussed with rbasak, with conclusion that this isn't high enough priority to SRU; risky to change unless this is causing real production issues. I'll attach my debdiff in case needing to resurrect at a later time. ** Patch added: "libnl3_3.2.21-1ubuntu4.debdiff" https://bugs.launchpad.net/ubuntu/+source/libnl3/+bug/1605260/+attachment/4730906/+files/libnl3_3.2.21-1ubuntu4.debdiff ** Changed in: libnl3 (Ubuntu Trusty) Status: New => Won't Fix ** Changed in: libnl3 (Ubuntu) Status: Triaged => Fix Released ** Changed in: libnl3 (Ubuntu Trusty) Importance: Undecided => Low -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libnl3 in Ubuntu. https://bugs.launchpad.net/bugs/1605260 Title: Memory leak in libnl-3 (3.2.21-1ubuntu3) in 14.04 Status in libnl3 package in Ubuntu: Fix Released Status in libnl3 source package in Trusty: Won't Fix Bug description: There is a memory leak in libnl 3.2.21 fixed by upstream here: http://lists.infradead.org/pipermail/libnl/2013-April/000985.html and released as part of libnl-3.2.22 (git commit rev df66b0f267af636848d7f0301d3f5863c58fb313). However, this fix doesn't make it into Ubuntu 14.04LTS. Please, apply. $ lsb_release -rd Description:Ubuntu 14.04.4 LTS Release:14.04 $ apt-cache policy libnl-3-200 libnl-3-200: Installed: 3.2.21-1ubuntu3 Candidate: 3.2.21-1ubuntu3 Version table: *** 3.2.21-1ubuntu3 0 500 http://ua.archive.ubuntu.com/ubuntu/ trusty-updates/main i386 Packages 100 /var/lib/dpkg/status 3.2.21-1 0 500 http://ua.archive.ubuntu.com/ubuntu/ trusty/main i386 Packages $ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libnl3/+bug/1605260/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1616982] [NEW] fix initialization of DEB_VENDOR for derivatives
Public bug reported: Hi debian/rules only supports two values for DEB_VENDOR: Debian and Ubuntu. As derivative distributions put other values in this variable, libreoffice cannot be built there. With this patch DEB_VENDOR is always initialized to either Debian or Ubuntu depending on which the host distribution derives from. This problem was found when trying to build libreoffice on ubuntuBSD but is likely to affect other derivative distributions. ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New ** Tags: patch ubuntubsd ** Patch added: "libreoffice.diff" https://bugs.launchpad.net/bugs/1616982/+attachment/4727710/+files/libreoffice.diff -- 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/1616982 Title: fix initialization of DEB_VENDOR for derivatives Status in libreoffice package in Ubuntu: New Bug description: Hi debian/rules only supports two values for DEB_VENDOR: Debian and Ubuntu. As derivative distributions put other values in this variable, libreoffice cannot be built there. With this patch DEB_VENDOR is always initialized to either Debian or Ubuntu depending on which the host distribution derives from. This problem was found when trying to build libreoffice on ubuntuBSD but is likely to affect other derivative distributions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1616982/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 971219] Re: Remmina Crashes with when connecting to some RDP hosts
I changed the color from 8bpp to 16bpp, but I don't think it caused the crash immediately on the next connection, though I don't remember now. However, once it started crashing, it crashed on every connection attempt. I changed it to 8bpp and then I could connect without a crash. I then changed it back to 16bpp and I am still able to connect. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to freerdp in Ubuntu. https://bugs.launchpad.net/bugs/971219 Title: Remmina Crashes with when connecting to some RDP hosts Status in freerdp package in Ubuntu: Confirmed Bug description: When connecting to some RDP Hosts Remmina will crash every time they are 2008 server hosts but not all 2008 server hosts have the problem. [ 2375.493642] remmina[7647]: segfault at 10018 ip 7f0db307718c sp 7f0da4c836f0 error 6 in libfreerdp-core.so.1.0.1[7f0db306+42000] [ 2509.507670] remmina[7727]: segfault at 10018 ip 7fe454b6b18c sp 7fe4467b36f0 error 6 in libfreerdp-core.so.1.0.1[7fe454b54000+42000] ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: remmina 1.0.0-1ubuntu5 ProcVersionSignature: Ubuntu 3.2.0-17.27-generic 3.2.6 Uname: Linux 3.2.0-17-generic x86_64 ApportVersion: 2.0-0ubuntu2 Architecture: amd64 Date: Mon Apr 2 11:24:51 2012 InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120301) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: remmina UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/freerdp/+bug/971219/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1514474] Re: package tex-common 6.04 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
@zenigata17 this worked for me, thanks! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to tex-common in Ubuntu. https://bugs.launchpad.net/bugs/1514474 Title: package tex-common 6.04 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in tex-common package in Ubuntu: Confirmed Bug description: dist-upgrade from wily to xenial ProblemType: Package DistroRelease: Ubuntu 16.04 Package: tex-common 6.04 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.19.2-0ubuntu4 Architecture: amd64 Date: Mon Nov 9 09:56:09 2015 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2011-07-12 (1580 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha amd64 (20110705.1) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.3ubuntu1 apt 1.0.10.2ubuntu1 SourcePackage: tex-common Title: package tex-common 6.04 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to xenial on 2011-12-23 (1416 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tex-common/+bug/1514474/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1613007] [NEW] package tex-common 6.04 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Public bug reported: while upgrading to 16.04 got this error ProblemType: Package DistroRelease: Ubuntu 16.04 Package: tex-common 6.04 ProcVersionSignature: Ubuntu 3.13.0-93.140-generic 3.13.11-ckt39 Uname: Linux 3.13.0-93-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Sat Aug 13 20:12:00 2016 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2014-01-06 (950 days ago) InstallationMedia: Ubuntu-Server 12.04.3 LTS "Precise Pangolin" - Release amd64 (20130820.2) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.12~ubuntu16.04.1 SourcePackage: tex-common Title: package tex-common 6.04 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to xenial on 2016-08-14 (0 days ago) ** Affects: tex-common (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to tex-common in Ubuntu. https://bugs.launchpad.net/bugs/1613007 Title: package tex-common 6.04 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in tex-common package in Ubuntu: New Bug description: while upgrading to 16.04 got this error ProblemType: Package DistroRelease: Ubuntu 16.04 Package: tex-common 6.04 ProcVersionSignature: Ubuntu 3.13.0-93.140-generic 3.13.11-ckt39 Uname: Linux 3.13.0-93-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Sat Aug 13 20:12:00 2016 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2014-01-06 (950 days ago) InstallationMedia: Ubuntu-Server 12.04.3 LTS "Precise Pangolin" - Release amd64 (20130820.2) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.12~ubuntu16.04.1 SourcePackage: tex-common Title: package tex-common 6.04 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to xenial on 2016-08-14 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tex-common/+bug/1613007/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1589611] Re: gnome-terminal crash on non-utf8 locale
In my case, I had a happy, up-to-date Xenial Ubuntu installation. I decided to load the xubuntu packages too, as an alternative desktop. Switching back to regular Ubuntu later, gnome-terminal no longer works, for the above reasons. Having determined that the problem is that DBus isn't providing correct locale information, I have used: * "sudo locale-gen --purge" * "sudo dpkg-reconfigure locales" (selecting only en_GB locales that are UTF-8) * "sudo gnome-language-selector" (ditto) ...and rebooted after each, but gnome-terminal still fails with status 8 when launched from xterm. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1589611 Title: gnome-terminal crash on non-utf8 locale Status in gnome-terminal package in Ubuntu: Confirmed Bug description: Dear Maintainer, I set my ubuntu 16.04 box's locale to zh_CN.GBK or zh_CN.GB18030, gnome-terminal crash every time when I try to open it. This is some info: Error constructing proxy for org.gnome.Terminal:/org/gnome/Terminal/Factory0: Error calling StartServiceByName for org.gnome.Terminal: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process org.gnome.Terminal exited with status 8 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gnome-terminal 3.18.3-1ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: XFCE Date: Tue Jun 7 01:09:44 2016 InstallationDate: Installed on 2016-05-02 (35 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: gnome-terminal UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1589611/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1534501] Re: dnsmasq error logs fill up storage drive memory
I resolved this by disabling the dnsmasq plugin in /etc/NetworkManager/NetworkManager.conf, as I wanted to keep my own dnsmasq configuration. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1534501 Title: dnsmasq error logs fill up storage drive memory Status in dnsmasq package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: Confirmed Status in resolvconf package in Ubuntu: Invalid Status in rsyslog package in Ubuntu: Invalid Bug description: snippet of logs. Jan 15 00:28:24 localhost NetworkManager[1211]: DNS: plugin dnsmasq update failed Jan 15 00:28:24 localhost NetworkManager[1211]: Writing DNS information to /sbin/resolvconf Jan 15 00:28:24 localhost NetworkManager[1211]: dnsmasq: failed to create listening socket for 127.0.1.1: Address already in use Jan 15 00:28:24 localhost dnsmasq[30416]: failed to create listening socket for 127.0.1.1: Address already in use Jan 15 00:28:24 localhost dnsmasq[30416]: FAILED to start up Jan 15 00:28:24 localhost NetworkManager[1211]: dnsmasq exited with error: Network access problem (address in use; permissions; etc) (2) Jan 15 00:28:24 localhost NetworkManager[1211]: Writing DNS information to /sbin/resolvconf Jan 15 00:28:24 localhost NetworkManager[1211]: DNS: plugin dnsmasq child quit unexpectedly; refreshing DNS Jan 15 00:28:24 localhost NetworkManager[1211]: DNS: starting dnsmasq... Jan 15 00:28:24 localhost NetworkManager[1211]: dnsmasq not available on the bus, can't update servers. Jan 15 00:28:24 localhost NetworkManager[1211]: [1452846504.397836] [dns-manager/nm-dns-dnsmasq.c:387] update(): dnsmasq owner not found on bus: Could not get owner of name 'org.freedesktop.NetworkManager.dnsmasq': no such name Jan 15 00:28:24 localhost NetworkManager[1211]: DNS: plugin dnsmasq update failed Jan 15 00:28:24 localhost NetworkManager[1211]: Writing DNS information to /sbin/resolvconf Jan 15 00:28:24 localhost NetworkManager[1211]: dnsmasq: failed to create listening socket for 127.0.1.1: Address already in use Jan 15 00:28:24 localhost dnsmasq[30429]: failed to create listening socket for 127.0.1.1: Address already in use Jan 15 00:28:24 localhost dnsmasq[30429]: FAILED to start up Jan 15 00:28:24 localhost NetworkManager[1211]: dnsmasq exited with error: Network access problem (address in use; permissions; etc) (2) Jan 15 00:28:24 localhost NetworkManager[1211]: Writing DNS information to /sbin/resolvconf Jan 15 00:28:24 localhost NetworkManager[1211]: DNS: plugin dnsmasq child quit unexpectedly; refreshing DNS Jan 15 00:28:24 localhost NetworkManager[1211]: DNS: starting dnsmasq... Jan 15 00:28:24 localhost NetworkManager[1211]: dnsmasq not available on the bus, can't update servers. Jan 15 00:28:24 localhost NetworkManager[1211]: [1452846504.407691] [dns-manager/nm-dns-dnsmasq.c:387] update(): dnsmasq owner not found on bus: Could not get owner of name 'org.freedesktop.NetworkManager.dnsmasq': no such name Jan 15 00:28:24 localhost NetworkManager[1211]: DNS: plugin dnsmasq update failed Jan 15 00:28:24 localhost NetworkManager[1211]: Writing DNS information to /sbin/resolvconf Jan 15 00:28:24 localhost NetworkManager[1211]: dnsmasq: failed to create listening socket for 127.0.1.1: Address already in use Jan 15 00:28:24 localhost dnsmasq[30442]: failed to create listening socket for 127.0.1.1: Address already in use Jan 15 00:28:24 localhost dnsmasq[30442]: FAILED to start up Jan 15 00:28:24 localhost NetworkManager[1211]: dnsmasq exited with error: Network access problem (address in use; permissions; etc) (2) Jan 15 00:28:24 localhost NetworkManager[1211]: Writing DNS information to /sbin/resolvconf Jan 15 00:28:24 localhost NetworkManager[1211]: DNS: plugin dnsmasq child quit unexpectedly; refreshing DNS Jan 15 00:28:24 localhost NetworkManager[1211]: DNS: starting dnsmasq... Jan 15 00:28:24 localhost NetworkManager[1211]: dnsmasq not available on the bus, can't update servers. Jan 15 00:28:24 localhost NetworkManager[1211]: [1452846504.419365] [dns-manager/nm-dns-dnsmasq.c:387] update(): dnsmasq owner not found on bus: Could not get owner of name 'org.freedesktop.NetworkManager.dnsmasq': no such name Jan 15 00:28:24 localhost NetworkManager[1211]: DNS: plugin dnsmasq update failed Jan 15 00:28:24 localhost NetworkManager[1211]: Writing DNS information to /sbin/resolvconf Jan 15 00:28:24 localhost NetworkManager[1211]: dnsmasq: failed to create listening socket for 127.0.1.1: Address already in use Jan 15 00:28:24 localhost dnsmasq[30455]: failed to create listening socket for 127.0.1.1: Address already in use Jan 15 00:28:24 localhost dnsmasq[30455]: FAILED to start up Jan 15 00:28:24 localhost NetworkManager[1211]: dnsmasq exited with
[Desktop-packages] [Bug 1283793] Re: Keyboard doesn't respond during login and in unity without re-selecting it from the keyboard selector
I can confirm this appears to have resolved the issue for me. -- 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/1283793 Title: Keyboard doesn't respond during login and in unity without re- selecting it from the keyboard selector Status in xorg package in Ubuntu: Expired Bug description: This has been an issue for me since I installed Trusty. It's a relatively short-lived issue each time I start up, as I need to enable the keyboard before I can log in, and then I can type into the password field. I have removed the EN-US keyboard, as I'm using an EN-GB keyboard. Happy to do some diagnostics, but I'm not hugely technical! ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-11.31-generic 3.13.3 Uname: Linux 3.13.0-11-generic x86_64 NonfreeKernelModules: wl .tmp.unity.support.test.0: ApportVersion: 2.13.2-0ubuntu5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sun Feb 23 18:48:44 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.141+bdcom, 3.13.0-11-generic, x86_64: installed bcmwl, 6.30.223.141+bdcom, 3.13.0-8-generic, x86_64: installed virtualbox, 4.3.6, 3.13.0-11-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Device [1025:0743] InstallationDate: Installed on 2014-02-18 (5 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140217) MachineType: Acer V5-171 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-11-generic root=UUID=043d32d2-d60b-4d36-8c89-00870d31cc9b ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/26/2012 dmi.bios.vendor: Acer dmi.bios.version: V1.02 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Mimic dmi.board.vendor: Acer dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.02 dmi.modalias: dmi:bvnAcer:bvrV1.02:bd04/26/2012:svnAcer:pnV5-171:pvrV1.02:rvnAcer:rnMimic:rvrType2-BoardVersion:cvnAcer:ct10:cvrV1.02: dmi.product.name: V5-171 dmi.product.version: V1.02 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.11+14.04.20140218-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0~rc1-1ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0~rc1-1ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Sun Feb 23 18:45:59 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id4377 vendor CMN xserver.version: 2:1.15.0-1ubuntu6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1283793/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1598492] Re: disable MERGELIBS on ubuntuBSD
Cool thanks! Btw it's Jon not Joe ;-) -- 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/1598492 Title: disable MERGELIBS on ubuntuBSD Status in libreoffice package in Ubuntu: Fix Committed Bug description: MERGELIBS is a problem for ubuntuBSD because it triggers very long command-lines during build which surpass the FreeBSD value for ARG_MAX (see https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208154). Other GNU/kFreeBSD systems like Debian only enable MERGELIBS for !kfreebsd. However in Ubuntu version of libreoffice this condition isn't present. Could you use attached patch to only enable MERGELIBS on !kfreebsd? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1598492/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1598492] [NEW] disable MERGELIBS on ubuntuBSD
Public bug reported: MERGELIBS is a problem for ubuntuBSD because it triggers very long command-lines during build which surpass the FreeBSD value for ARG_MAX (see https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208154). Other GNU/kFreeBSD systems like Debian only enable MERGELIBS for !kfreebsd. However in Ubuntu version of libreoffice this condition isn't present. Could you use attached patch to only enable MERGELIBS on !kfreebsd? ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New ** Tags: patch ubuntubsd ** Patch added: "mergelibs.diff" https://bugs.launchpad.net/bugs/1598492/+attachment/4694411/+files/mergelibs.diff -- 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/1598492 Title: disable MERGELIBS on ubuntuBSD Status in libreoffice package in Ubuntu: New Bug description: MERGELIBS is a problem for ubuntuBSD because it triggers very long command-lines during build which surpass the FreeBSD value for ARG_MAX (see https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208154). Other GNU/kFreeBSD systems like Debian only enable MERGELIBS for !kfreebsd. However in Ubuntu version of libreoffice this condition isn't present. Could you use attached patch to only enable MERGELIBS on !kfreebsd? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1598492/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1564616] Re: detaching lightdm into background
Hi Is this bug fixed? Do you need other information / patch? Thanks! On Mon, Jun 06, 2016 at 04:17:42AM -, Launchpad Bug Tracker wrote: > [Expired for lightdm (Ubuntu) because there has been no activity for 60 > days.] > > ** Changed in: lightdm (Ubuntu) >Status: Incomplete => Expired > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1564616 > > Title: > detaching lightdm into background > > Status in lightdm package in Ubuntu: > Expired > > Bug description: > Hi > > When starting /etc/init.d/lightdm (either directly from root console > or through SysV init), it will get stuck because lightdm doesn't fork > into background when starting. > > Please could you add --background option to start-stop-daemon to fix > this? (note: the debian lightdm package already does this) > > This change is needed for ubuntuBSD (which uses SysV init to manage > system daemons). > > Thank you! > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1564616/+subscriptions -- Jon Boden ubuntuBSD -- The power of FreeBSD kernel with familiarity of Ubuntu OS! http://www.ubuntubsd.org/ -- https://twitter.com/ubuntuBSD -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1564616 Title: detaching lightdm into background Status in lightdm package in Ubuntu: Expired Bug description: Hi When starting /etc/init.d/lightdm (either directly from root console or through SysV init), it will get stuck because lightdm doesn't fork into background when starting. Please could you add --background option to start-stop-daemon to fix this? (note: the debian lightdm package already does this) This change is needed for ubuntuBSD (which uses SysV init to manage system daemons). Thank you! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1564616/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1589146] [NEW] ubuntuBSD support
Public bug reported: Hi Symbols files need some updates in order to build on ubuntuBSD. Please can you include them? https://bazaar.launchpad.net/~ubuntubsd/ubuntubsd/patches- xenial/download/jon%40ubuntubsd.org-20160601072740-fr30k90py99vinto/ilmbase.diff-20160426081048-uj0038tten98r2t3-24/ilmbase.diff Thank you! ** Affects: ilmbase (Ubuntu) Importance: Undecided Status: New ** Tags: patch ubuntubsd -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ilmbase in Ubuntu. https://bugs.launchpad.net/bugs/1589146 Title: ubuntuBSD support Status in ilmbase package in Ubuntu: New Bug description: Hi Symbols files need some updates in order to build on ubuntuBSD. Please can you include them? https://bazaar.launchpad.net/~ubuntubsd/ubuntubsd/patches- xenial/download/jon%40ubuntubsd.org-20160601072740-fr30k90py99vinto/ilmbase.diff-20160426081048-uj0038tten98r2t3-24/ilmbase.diff Thank you! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ilmbase/+bug/1589146/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1565080] Re: ubuntuBSD support
Hi I've updated the patch to 11.2.0-1ubuntu2 as it needed a resync: https://bazaar.launchpad.net/~ubuntubsd/ubuntubsd/patches- xenial/download/jon%40ubuntubsd.org-20160521075150-b99t0kkt6lhzepsv/mesa.diff-20160426081048-uj0038tten98r2t3-45/mesa.diff Please could you apply it? ** Patch removed: "mesa.diff" https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1565080/+attachment/4619847/+files/mesa.diff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1565080 Title: ubuntuBSD support Status in mesa package in Ubuntu: New Bug description: Hi Please could you apply attached patch to make mesa buildable on ubuntuBSD? It just needs to adjust a few dependencies. Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1565080/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1562002] Re: Nautilus: lag after choosing action in top right menu
Opened a bug against Ubuntu Gnome for this issue. https://bugs.launchpad.net/ubuntu-gnome/+bug/1584280 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1562002 Title: Nautilus: lag after choosing action in top right menu Status in nautilus package in Ubuntu: Confirmed Bug description: choosing action like New Tab, New Folder, Select Items Matching, will make nautilus lag (unresponsive) ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: nautilus 1:3.18.4.is.3.14.3-0ubuntu4 ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6 Uname: Linux 4.4.0-15-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Mar 25 20:52:21 2016 GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' b"'890x550+685+36'" InstallationDate: Installed on 2016-03-24 (1 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323.1) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1562002/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1562002] Re: Nautilus: lag after choosing action in top right menu
Unity status is unknown, I only have Ubuntu Gnome installed. This applies to any action in the menu, "Invert selection" "New Tab" and any other I tested. This is causing the whole desktop to hang. I opened the system monitor to see if it was causing the processor to hang, upon using an item from the menu, the system monitor's "resources" screen froze for the entire time of the lag-nearly a minute as I recall). When the desktop was working again, you could see where the CPU's had been spiking one at a time to 100% then dropping as the next one spiked for entire history shown (mine is set at 60 seconds) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1562002 Title: Nautilus: lag after choosing action in top right menu Status in nautilus package in Ubuntu: Confirmed Bug description: choosing action like New Tab, New Folder, Select Items Matching, will make nautilus lag (unresponsive) ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: nautilus 1:3.18.4.is.3.14.3-0ubuntu4 ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6 Uname: Linux 4.4.0-15-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Mar 25 20:52:21 2016 GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' b"'890x550+685+36'" InstallationDate: Installed on 2016-03-24 (1 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323.1) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1562002/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1582002] Re: ubuntuBSD support
Thanks! On Mon, May 16, 2016 at 03:35:24PM -, Till Kamppeter wrote: > Patch applied to the Debian GIT repository of CUPS. It will get into > Ubuntu with the next CUPS package release. > > ** Changed in: cups (Ubuntu) >Status: New => Fix Committed > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1582002 > > Title: > ubuntuBSD support > > Status in cups package in Ubuntu: > Fix Committed > > Bug description: > Hi > > There's a small mistake in ubuntu-cupsd-idleexittimeout-upstart.patch > which makes cups build fail on ubuntuBSD. > > Please could you apply patch below to fix this? > > https://bazaar.launchpad.net/~ubuntubsd/ubuntubsd/patches- > > xenial/download/jon%40ubuntubsd.org-20160514042053-51py386hvtgb4wi7/cups.diff-20160514042015-ubvn8v1dxv52wfcy-1/cups.diff > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1582002/+subscriptions -- Jon Boden ubuntuBSD -- The power of FreeBSD kernel with familiarity of Ubuntu OS! http://www.ubuntubsd.org/ -- https://twitter.com/ubuntuBSD -- 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/1582002 Title: ubuntuBSD support Status in cups package in Ubuntu: Fix Committed Bug description: Hi There's a small mistake in ubuntu-cupsd-idleexittimeout-upstart.patch which makes cups build fail on ubuntuBSD. Please could you apply patch below to fix this? https://bazaar.launchpad.net/~ubuntubsd/ubuntubsd/patches- xenial/download/jon%40ubuntubsd.org-20160514042053-51py386hvtgb4wi7/cups.diff-20160514042015-ubvn8v1dxv52wfcy-1/cups.diff To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1582002/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1565333] Re: ubuntuBSD support
Hi The patch needed an update as it didn't apply anymore. Here is it: https://bazaar.launchpad.net/~ubuntubsd/ubuntubsd/patches- xenial/download/jon%40ubuntubsd.org-20160515013335-qkfnehk373pa1azi/xorgserver.diff-20160426081048-uj0038tten98r2t3-72 /xorg-server.diff ** Patch removed: "xorg-server.diff" https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1565333/+attachment/4620937/+files/xorg-server.diff -- 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/1565333 Title: ubuntuBSD support Status in xorg-server package in Ubuntu: Confirmed Bug description: Hi Please could you apply attached patch to make xorg-server buildable on ubuntuBSD? It just needs to adjust a few dependencies. Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1565333/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1582002] [NEW] ubuntuBSD support
Public bug reported: Hi There's a small mistake in ubuntu-cupsd-idleexittimeout-upstart.patch which makes cups build fail on ubuntuBSD. Please could you apply patch below to fix this? https://bazaar.launchpad.net/~ubuntubsd/ubuntubsd/patches- xenial/download/jon%40ubuntubsd.org-20160514042053-51py386hvtgb4wi7/cups.diff-20160514042015-ubvn8v1dxv52wfcy-1/cups.diff ** Affects: cups (Ubuntu) Importance: Undecided Status: New ** Tags: patch ubuntubsd -- 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/1582002 Title: ubuntuBSD support Status in cups package in Ubuntu: New Bug description: Hi There's a small mistake in ubuntu-cupsd-idleexittimeout-upstart.patch which makes cups build fail on ubuntuBSD. Please could you apply patch below to fix this? https://bazaar.launchpad.net/~ubuntubsd/ubuntubsd/patches- xenial/download/jon%40ubuntubsd.org-20160514042053-51py386hvtgb4wi7/cups.diff-20160514042015-ubvn8v1dxv52wfcy-1/cups.diff To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1582002/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1565337] Re: ubuntuBSD support
Actually there's some trouble with qxl on ubuntuBSD, see: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1568104 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=819822 ** Bug watch added: Debian Bug tracker #819822 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=819822 ** Tags removed: patch patch-forwarded-debian -- 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/1565337 Title: ubuntuBSD support Status in xorg package in Ubuntu: New Bug description: Hi Please could you enable xserver-xorg-video-vmware & xserver-xorg- video-qxl for !Linux architectures? This is useful for ubuntuBSD. Patch is already sent to Debian. Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1565337/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1568104] Re: Xorg Needs KVM Support within UbuntuBSD
I got this comment from Steven Chamberlain (Debian GNU/kFreeBSD developer): On Sun, Apr 17, 2016 at 02:57:07PM +0100, Steven Chamberlain wrote: > Hi! > > (I'm not registered on Launchpad, so mailing you directly...) > > In reply to > https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1568104 > > it seems to be a problem with xserver-xorg-video-qxl, not the Xorg > server itself. > > Firstly: > > | [ 144.925] (II) [KMS] drm report modesetting isn't supported. > > may be expected, if the FreeBSD kernel does not have a KMS driver for > QXL. The detection happens in > http://sources.debian.net/src/libdrm/2.4.58-2/xf86drmMode.c/?hl=724#L776 > which mainly looks at a sysctl hw.dri.*.modesetting to ask the kernel of > KMS is enabled or not. (Maybe the original reporter could share his > output of `sysctl hw.dri` to confirm this). > > Without that, it falls back to some other mode of operation. It seems > to attempt some kind of direct memory-mapped I/O, and maybe that code is > unsuitable for kFreeBSD: > > | [ 145.095] (EE) Backtrace: > | [ 145.096] (EE) 0: /usr/bin/X (xorg_backtrace+0x4e) [0x58cc8e] > | [ 145.096] (EE) 1: /usr/bin/X (0x40+0x191009) [0x591009] > | [ 145.096] (EE) 2: ?? [0x7043] > | [ 145.096] (EE) 3: /usr/lib/x86_64-kfreebsd-gnu/libpciaccess.so.0 > | (pci_io_write8+0x3) [0x80104e203] > | [ 145.096] (EE) 4: /usr/lib/xorg/modules/drivers/qxl_drv.so > | (0x8055a5000+0xb530) [0x8055b0530] > | [ 145.096] (EE) 5: /usr/lib/xorg/modules/drivers/qxl_drv.so > | (0x8055a5000+0x7811) [0x8055ac811] > > (Installing package xserver-xorg-video-qxl-dbg might give a more > detailed backtrace). > > However, if kFreeBSD doesn't support KMS with QXL, maybe it has no > advantage over plain VESA mode? I would consider disabling/uninstalling > the QXL driver, if it can't be easily fixed for kFreeBSD. Then Xorg > would fall back to VESA mode and not crash. > > Regards, > -- > Steven Chamberlain > ste...@pyro.eu.org -- 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/1568104 Title: Xorg Needs KVM Support within UbuntuBSD Status in xorg-server package in Ubuntu: New Bug description: When starting X in a KVM instance on UbuntuBSD, Xorg crashes with the following log: http://paste.ubuntu.com/15696451/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1568104/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1283793] Re: Keyboard doesn't respond during login and in unity without re-selecting it from the keyboard selector
I have not been noticeably aware of this issue for several months (it's an intermittent issue), however, I have applied the BIOS update, and will monitor the situation. The dmidecode lines returns V1.09 and 10/30/2012 respectively. -- 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/1283793 Title: Keyboard doesn't respond during login and in unity without re- selecting it from the keyboard selector Status in xorg package in Ubuntu: Expired Bug description: This has been an issue for me since I installed Trusty. It's a relatively short-lived issue each time I start up, as I need to enable the keyboard before I can log in, and then I can type into the password field. I have removed the EN-US keyboard, as I'm using an EN-GB keyboard. Happy to do some diagnostics, but I'm not hugely technical! ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-11.31-generic 3.13.3 Uname: Linux 3.13.0-11-generic x86_64 NonfreeKernelModules: wl .tmp.unity.support.test.0: ApportVersion: 2.13.2-0ubuntu5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sun Feb 23 18:48:44 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.141+bdcom, 3.13.0-11-generic, x86_64: installed bcmwl, 6.30.223.141+bdcom, 3.13.0-8-generic, x86_64: installed virtualbox, 4.3.6, 3.13.0-11-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Device [1025:0743] InstallationDate: Installed on 2014-02-18 (5 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140217) MachineType: Acer V5-171 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-11-generic root=UUID=043d32d2-d60b-4d36-8c89-00870d31cc9b ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/26/2012 dmi.bios.vendor: Acer dmi.bios.version: V1.02 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Mimic dmi.board.vendor: Acer dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.02 dmi.modalias: dmi:bvnAcer:bvrV1.02:bd04/26/2012:svnAcer:pnV5-171:pvrV1.02:rvnAcer:rnMimic:rvrType2-BoardVersion:cvnAcer:ct10:cvrV1.02: dmi.product.name: V5-171 dmi.product.version: V1.02 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.11+14.04.20140218-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0~rc1-1ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0~rc1-1ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Sun Feb 23 18:45:59 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id4377 vendor CMN xserver.version: 2:1.15.0-1ubuntu6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1283793/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1567658] [NEW] ubuntuBSD support
Public bug reported: Hi Please could you apply attached patch to make brltty installable on ubuntuBSD? It just needs to adjust the initramfs-tools dependency. Thanks! ** Affects: brltty (Ubuntu) Importance: Undecided Status: New ** Tags: patch ubuntubsd ** Patch added: "brltty.diff" https://bugs.launchpad.net/bugs/1567658/+attachment/4628241/+files/brltty.diff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to brltty in Ubuntu. https://bugs.launchpad.net/bugs/1567658 Title: ubuntuBSD support Status in brltty package in Ubuntu: New Bug description: Hi Please could you apply attached patch to make brltty installable on ubuntuBSD? It just needs to adjust the initramfs-tools dependency. Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/brltty/+bug/1567658/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1564616] Re: detaching lightdm into background
Hi Should work fine. -b is the same as --background Thanks! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1564616 Title: detaching lightdm into background Status in lightdm package in Ubuntu: Incomplete Bug description: Hi When starting /etc/init.d/lightdm (either directly from root console or through SysV init), it will get stuck because lightdm doesn't fork into background when starting. Please could you add --background option to start-stop-daemon to fix this? (note: the debian lightdm package already does this) This change is needed for ubuntuBSD (which uses SysV init to manage system daemons). Thank you! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1564616/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
