[Bug 1668309] Re: Scaling on xps13 means only a part of the screen is visible at any time.
Any progress here? Affects me on 18.04 LTS. ** Bug watch added: gitlab.gnome.org/GNOME/vino/issues #9 https://gitlab.gnome.org/GNOME/vino/issues/9 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1668309 Title: Scaling on xps13 means only a part of the screen is visible at any time. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vino/+bug/1668309/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1668309] Re: Scaling on xps13 means only a part of the screen is visible at any time.
I have filled an issue in upstream: https://gitlab.gnome.org/GNOME/vino/issues/9 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1668309 Title: Scaling on xps13 means only a part of the screen is visible at any time. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vino/+bug/1668309/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1782679] Re: systemd-resolved can't resolve at all, need to add nameservers to resolve.conf
Any progress here? systemd-resolved has plus that it's integrated with DNS options from systemd-networkd, but for end user it has many issues, especially related to DNSSEC. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1782679 Title: systemd-resolved can't resolve at all, need to add nameservers to resolve.conf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1782679/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1845214] [NEW] Keyboard NumLock indicator turns off on connecting another keyboard
Public bug reported: My USB HID keyboard has NumLock LED. It usually works fine. However, when I plug in YubiKey (hardware security token, it is also identified as a USB HID keyboard) NumLock LED turns OFF, but the NumLock feature is still ON. If I press NumLock, NumLock becomes disabled (it is displayed by DE and checked by typing). If I press NumLock again, NumLock turns back ON with LED. I originally thought that issue could be related to the fact that YubiKey does not have a NumLock led, so it reports LED as nonexisting and stuff happens. However, today I tried attaching another USB keyboard: LED on first one still goes off; but LED on second goes ON immediately after plugging in. Pressing NumLock once disables NumLock and LED on first keyboard, as with YubiKey; pressing again enabled NumLock and both LEDs. Seems like my user session (on vt2) is running Xorg while login screen (on vt1, the one that allows to choose a user and that you see before first login) is running Wayland; both are faulty. Because of this, I believe the issue is in the kernel. However, I am not sure, so you can ask for way more reports to be added, I will add those. Reproducing should be pretty easy with any cheap USB keyboards, nothing special is used by me. Operating system: Ubuntu 18.04 Bionic Beaver. Linux kernel: 18.04 HWE, 5.0.0-25. However, I think I saw this blinking before upgrading to HWE. DE: GNOME. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-generic-hwe-18.04 5.0.0.29.86 ProcVersionSignature: Ubuntu 5.0.0-25.26~18.04.1-generic 5.0.18 Uname: Linux 5.0.0-25-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Sep 24 16:52:08 2019 SourcePackage: linux-meta-hwe UpgradeStatus: Upgraded to bionic on 2018-09-03 (386 days ago) ** Affects: linux-meta-hwe (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1845214 Title: Keyboard NumLock indicator turns off on connecting another keyboard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-hwe/+bug/1845214/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1814169] Re: Mutter upsteam bug: cannot overwrite workspaces layout
Huh. So, when will the fixed version land? For now, I rebuild published version with the patch above. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1814169 Title: Mutter upsteam bug: cannot overwrite workspaces layout To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1814169/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1814169] Re: Mutter upsteam bug: cannot overwrite workspaces layout
Patch as a file ** Patch added: "0001-Allow-workspace-layout-to-be-overridden.patch" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1814169/+attachment/5234887/+files/0001-Allow-workspace-layout-to-be-overridden.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1814169 Title: Mutter upsteam bug: cannot overwrite workspaces layout To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1814169/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1814169] [NEW] Mutter upsteam bug: cannot overwrite workspaces layout
Public bug reported:
Running up-to-date Ubuntu Cosmic. Since I am running a version with
manually applied patched from below, I couldn't use the ubuntu-bug
helper.
Bug: When using GNOME extension “Workspace grid” that arranges
workspaces in a grid, one can find that horizontal switch animation is
replaced with a vertical one. This is caused by a bug in mutter itself,
it's acknowledged and fixed in upsteam. Applying the patch for the
current version in Ubuntu solves the issue as well.
GIFs of the issue could be found here: https://medium.com/@hkdb/patch-
gnome-3-30-for-workspace-grid-1ee8b1dd92f9.
Upstream bug: https://gitlab.gnome.org/GNOME/mutter/issues/270.
Upsteam fix:
https://gitlab.gnome.org/rmyorston/mutter/commit/97a3a9b24b3655003467d5fac6bb1ec1c60e
(merged into master 3 months ago).
The patch to fix is, literally, adding 1 meaningful line:
>From 86a719cc78149b7db189ff7e5d1f16418d257e9e Mon Sep 17 00:00:00 2001
From: Ron Yorston
Date: Tue, 2 Oct 2018 12:47:05 +0100
Subject: [PATCH] Allow workspace layout to be overridden
meta_workspace_manager_override_workspace_layout is implemented by
calling meta_workspace_manager_update_workspace_layout which
respects the workspace_layout_overridden flag. After the first call
to meta_workspace_manager_override_workspace_layout all subsequent
calls fail silently.
Reset workspace_layout_overridden to FALSE before calling
meta_workspace_manager_update_workspace_layout.
Signed-off-by: Ron Yorston
---
src/core/meta-workspace-manager.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/src/core/meta-workspace-manager.c
b/src/core/meta-workspace-manager.c
index 2670f4938..abc819db0 100644
--- a/src/core/meta-workspace-manager.c
+++ b/src/core/meta-workspace-manager.c
@@ -496,6 +496,8 @@ meta_workspace_manager_override_workspace_layout
(MetaWorkspaceManager *workspac
int n_rows,
int
n_columns)
{
+ workspace_manager->workspace_layout_overridden = FALSE;
+
meta_workspace_manager_update_workspace_layout (workspace_manager,
starting_corner,
vertical_layout,
--
2.17.1
Hopefully this one is fast to test and apply ;)
** Affects: mutter (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1814169
Title:
Mutter upsteam bug: cannot overwrite workspaces layout
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1814169/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1772688] Re: Aptitude does not want to autoremove Linux kernel, while apt wants
It's actually the files that configure apt to do intended behavior, but somehow aptitude has it's own mind :/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1772688 Title: Aptitude does not want to autoremove Linux kernel, while apt wants To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aptitude/+bug/1772688/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1772688] Re: Aptitude does not want to autoremove Linux kernel, while apt wants
Forgot one thing: if ask aptitude explicitly why linux-image-... is needed, it will reply that no reason for this package was found. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1772688 Title: Aptitude does not want to autoremove Linux kernel, while apt wants To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aptitude/+bug/1772688/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1772688] [NEW] Aptitude does not want to autoremove Linux kernel, while apt wants
Public bug reported:
>From some update last year or so, apt has achived the tools to remove
old Linux kernels via /etc/kernel/postinst.d/apt-auto-removal. This is
really great, but for some reason, all apt tools agree on this (apt-get
autoremove, apt autoremove), but aptitude does not.
For example, here I have an installation where 4.15.0-20 is safe for
deinstallation, and generated by script above config agrees:
$ LANG=C apt --dry-run autoremove
NOTE: This is only a simulation!
apt needs root privileges for real execution.
Keep also in mind that locking is deactivated,
so don't depend on the relevance to the real current situation!
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages will be REMOVED:
linux-cloud-tools-4.15.0-20 linux-cloud-tools-4.15.0-20-generic
linux-headers-4.15.0-20
linux-headers-4.15.0-20-generic linux-image-4.15.0-20-generic
linux-modules-4.15.0-20-generic
linux-modules-extra-4.15.0-20-generic linux-tools-4.15.0-20
linux-tools-4.15.0-20-generic
0 upgraded, 0 newly installed, 9 to remove and 0 not upgraded.
Remv linux-cloud-tools-4.15.0-20-generic [4.15.0-20.21]
Remv linux-cloud-tools-4.15.0-20 [4.15.0-20.21]
Remv linux-headers-4.15.0-20-generic [4.15.0-20.21] <--- Those
Remv linux-headers-4.15.0-20 [4.15.0-20.21] <---
little
Remv linux-modules-extra-4.15.0-20-generic [4.15.0-20.21]
Remv linux-image-4.15.0-20-generic [4.15.0-20.21] <---
buggers
Remv linux-modules-4.15.0-20-generic [4.15.0-20.21] <--- here!
Remv linux-tools-4.15.0-20-generic [4.15.0-20.21]
Remv linux-tools-4.15.0-20 [4.15.0-20.21]
but aptitude does not:
$ LANG=C aptitude --simulate safe-upgrade
The following packages will be REMOVED:
linux-cloud-tools-4.15.0-20{u} linux-cloud-tools-4.15.0-20-generic{u}
linux-modules-extra-4.15.0-20-generic{u} linux-tools-4.15.0-20{u}
linux-tools-4.15.0-20-generic{u}
0 packages upgraded, 0 newly installed, 5 to remove and 0 not upgraded.
Need to get 0 B of archives. After unpacking 178 MB will be freed.
Note: Using 'Simulate' mode.
Do you want to continue? [Y/n/?] y
Would download/install/remove packages.
Removing modules-extra seems fine for it, though!
I have looked over all apt configs, there was no sign for me that aptitude was
configured specificly to keep the images.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: aptitude 0.8.10-6ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-21.22-generic 4.15.17
Uname: Linux 4.15.0-21-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Tue May 22 19:48:48 2018
InstallationDate: Installed on 2017-03-05 (443 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
ProcEnviron:
TERM=tmux-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=ru_RU.UTF-8
SHELL=/bin/bash
SourcePackage: aptitude
UpgradeStatus: Upgraded to bionic on 2018-05-03 (18 days ago)
** Affects: aptitude (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug bionic third-party-packages
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1772688
Title:
Aptitude does not want to autoremove Linux kernel, while apt wants
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/aptitude/+bug/1772688/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1769456] [NEW] Thunderbird renders emoji in email subject with enourmous size
Public bug reported: Well, if you have an email with an emoji in subject, Thunderbird renders it with enourmous size, like 6-7 rows in mail list. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: thunderbird 1:52.7.0+build1-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ldvsoft2831 F pulseaudio BuildID: 20180416164209 Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Sun May 6 14:31:48 2018 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 2016-04-23 (742 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) IpRoute: default via 192.168.1.1 dev wlp3s0 proto dhcp metric 600 10.205.113.0/24 dev docker0 proto kernel scope link src 10.205.113.1 linkdown 169.254.0.0/16 dev wlp3s0 scope link metric 1000 172.17.0.0/16 dev br-cf01c9a4a624 proto kernel scope link src 172.17.0.1 linkdown 192.168.1.0/24 dev wlp3s0 proto kernel scope link src 192.168.1.124 metric 600 Locales: extensions.sqlite corrupt or missing PrefSources: prefs.js /usr/share/xul-ext/enigmail/defaults/preferences/enigmail.js /usr/share/xul-ext/enigmail/defaults/preferences/000system.js ProcEnviron: TERM=tmux-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash Profiles: Profile0 (Default) - LastVersion=52.7.0/20180416164209 (In use) RunningIncompatibleAddons: False SourcePackage: thunderbird Themes: extensions.sqlite corrupt or missing UpgradeStatus: Upgraded to bionic on 2018-05-04 (1 days ago) dmi.bios.date: 06/16/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: U40Sd.202 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: U40Sd 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.:bvrU40Sd.202:bd06/16/2011:svnASUSTeKComputerInc.:pnU40Sd:pvr1.0:rvnASUSTeKComputerInc.:rnU40Sd:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0: dmi.product.family: U dmi.product.name: U40Sd dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK Computer Inc. ** Affects: thunderbird (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic third-party-packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1769456 Title: Thunderbird renders emoji in email subject with enourmous size To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1769456/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1767669] [NEW] Systemd-resolved cannot forget local DNS Domain name after leaving the network
Public bug reported: At my university, WiFi network setup sets a local DNS Domain name (in a form of .). That's alright; but when I come home with my laptop and resume it, the local DNS Domain name is still set (checked via systemd-resovle --status), and because of that I cannot open my university website: it's domain cannot be resoved on a local DNS (of course it cannot be resolved, it's not in local network anymore). Resolving manually on any other DNS server (via dig @) works perfectly fine. Resolving any non-local name works fine too. DNS resolver IP's are right. Restarting systemd-resolved or-and NetworkManager does not fix the issue, only the full reboot can help. That's pretty annoying. I am running Ubuntu 17.10 (soon to be upgraded to 18.04). Have this issue since installing 17.10, but wasn't able to find a clue until today. What should be happening: Well, after I leave the network, resolver should forget local settings from that network, right? What is happeing: it does not. Well, at least the resolver ip's are right. P.S. It might be a NetworkManager issue but the only thing that I find that remembers local DNS is the systemd-resolved, feel free to change package. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: systemd 234-2ubuntu12.3 ProcVersionSignature: Ubuntu 4.13.0-39.44-generic 4.13.16 Uname: Linux 4.13.0-39-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Apr 28 18:26:01 2018 InstallationDate: Installed on 2016-04-23 (734 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: ASUSTeK Computer Inc. U40Sd ProcEnviron: LANG=ru_RU.UTF-8 TERM=tmux-256color SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, user) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-39-generic root=UUID=ea1ac96c-71bd-4b8e-81ad-24abb9a24ce0 ro nogpumanager quiet splash vt.handoff=7 SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/docker.service → /etc/systemd/system/docker.service.d/docker.conf [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /lib/systemd/system/user@.service → /lib/systemd/system/user@.service.d/timeout.conf 3 overridden configuration files found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/16/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: U40Sd.202 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: U40Sd 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.:bvrU40Sd.202:bd06/16/2011:svnASUSTeKComputerInc.:pnU40Sd:pvr1.0:rvnASUSTeKComputerInc.:rnU40Sd:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0: dmi.product.family: U dmi.product.name: U40Sd dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK Computer Inc. mtime.conffile..etc.systemd.resolved.conf: 2018-04-19T19:34:54.154657 ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful third-party-packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1767669 Title: Systemd-resolved cannot forget local DNS Domain name after leaving the network To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1767669/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1757960] Re: Gnome Shell crashes with SIGSEGV when I turn off the monitor
While I can reproduce the bug for 100%, only one file is present in /var/crash, and it was an old night crash. I still reported it: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1757978 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1757960 Title: Gnome Shell crashes with SIGSEGV when I turn off the monitor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1757960/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1757960] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1757960/+attachment/5086661/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1757960 Title: Gnome Shell crashes with SIGSEGV when I turn off the monitor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1757960/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1757960] JournalErrors.txt
apport information ** Attachment added: "JournalErrors.txt" https://bugs.launchpad.net/bugs/1757960/+attachment/5086660/+files/JournalErrors.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1757960 Title: Gnome Shell crashes with SIGSEGV when I turn off the monitor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1757960/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1757960] Re: Gnome Shell crashes with SIGSEGV when I turn off the monitor
apport information ** Tags added: apport-collected artful ** Description changed: For quite some time, I have seen my gnome-shell session randomly dying on me when I am away from the desktop for quite some time. Only now have I found the reproducable cause: when my monitor is turned off (by power preserving or by pressing the power button), Shell SISSEGVs out of existance. I guess it is highly related to my destop configuration: I use proprietary NVIDIA drivers and my display is connected via DisplayPort, if this gives you ideas. Maybe in the end the bug is in the driver? - Here are some system logs around the time of a crash, maybe it can give - you ideas what to check or whom to blame. If you need any other - information, don't hesitate asking me for it, I will try my best. + Here are some system logs around the time of a crash, maybe it can give you ideas what to check or whom to blame. If you need any other information, don't hesitate asking me for it, I will try my best. + --- + ApportVersion: 2.20.7-0ubuntu3.7 + Architecture: amd64 + CurrentDesktop: ubuntu:GNOME + DisplayManager: gdm3 + DistroRelease: Ubuntu 17.10 + GsettingsChanges: + org.gnome.shell enabled-extensions ['alternate-...@gnome-shell-extensions.gcampax.github.com', 'workspace-g...@mathematical.coffee.gmail.com', 'panel-...@berend.de.schouwer.gmail.com', 'Per_Window_Keyboard_Layout@nullie-laptop', 'ubuntu-appindicat...@ubuntu.com', 'system-moni...@paradoxxx.zero.gmail.com', 'disconnect-w...@kgshank.net', 'logoutbut...@kyle.aims.ac.za', 'native-window-placem...@gnome-shell-extensions.gcampax.github.com', 'drive-m...@gnome-shell-extensions.gcampax.github.com', 'remove-dropdown-arr...@mpdeimos.com'] + org.gnome.shell command-history ['', 'r'] + org.gnome.shell favorite-apps ['org.gnome.Terminal.desktop', 'org.gnome.Nautilus.desktop', 'google-chrome.desktop'] + org.gnome.desktop.interface gtk-im-module 'ibus' + org.gnome.desktop.interface clock-show-date true + InstallationDate: Installed on 2017-03-05 (381 days ago) + InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) + NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia + Package: gnome-shell 3.26.2-0ubuntu0.1 + PackageArchitecture: amd64 + ProcEnviron: + TERM=tmux-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=ru_RU.UTF-8 + SHELL=/bin/bash + ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13 + Tags: artful + Uname: Linux 4.13.0-37-generic x86_64 + UpgradeStatus: Upgraded to artful on 2018-01-11 (69 days ago) + UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo video wireshark + _MarkForUpload: True ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1757960/+attachment/5086659/+files/Dependencies.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1757960 Title: Gnome Shell crashes with SIGSEGV when I turn off the monitor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1757960/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1757960] Re: Gnome Shell crashes with SIGSEGV when I turn off the monirot
** Description changed: For quite some time, I have seen my gnome-shell session randomly dying on me when I am away from the desktop for quite some time. Only now have - I found the reproducable cause: when my moni + I found the reproducable cause: when my monitor is turned off (by power + preserving or by pressing the power button), Shell SISSEGVs out of + existance. I guess it is highly related to my destop configuration: I + use proprietary NVIDIA drivers and my display is connected via + DisplayPort, if this gives you ideas. Maybe in the end the bug is in the + driver? + + Here are some system logs around the time of a crash, maybe it can give + you ideas what to check or whom to blame. If you need any other + information, don't hesitate asking me for it, I will try my best. ** Summary changed: - Gnome Shell crashes with SIGSEGV when I turn off the monirot + Gnome Shell crashes with SIGSEGV when I turn off the monitor ** Attachment added: "System journal segment around one of the latest crashes" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1757960/+attachment/5086652/+files/gnome-session-related.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1757960 Title: Gnome Shell crashes with SIGSEGV when I turn off the monitor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1757960/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1731587] Re: Application 'org.gnome.Shell.desktop' killed by signal 11
I get this bug ofter when I am away from the computer: on my return my session is dead :/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1731587 Title: Application 'org.gnome.Shell.desktop' killed by signal 11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/1731587/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1757960] [NEW] Gnome Shell crashes with SIGSEGV when I turn off the monitor
Public bug reported: For quite some time, I have seen my gnome-shell session randomly dying on me when I am away from the desktop for quite some time. Only now have I found the reproducable cause: when my monitor is turned off (by power preserving or by pressing the power button), Shell SISSEGVs out of existance. I guess it is highly related to my destop configuration: I use proprietary NVIDIA drivers and my display is connected via DisplayPort, if this gives you ideas. Maybe in the end the bug is in the driver? Here are some system logs around the time of a crash, maybe it can give you ideas what to check or whom to blame. If you need any other information, don't hesitate asking me for it, I will try my best. ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1757960 Title: Gnome Shell crashes with SIGSEGV when I turn off the monitor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1757960/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1757961] [NEW] Gnome Shell crashes with SIGSEGV when I turn off the monirot
Public bug reported: For quite some time, I have seen my gnome-shell session randomly dying on me when I am away from the desktop for quite some time. Only now have I found the reproducable cause: when my moni ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1757961 Title: Gnome Shell crashes with SIGSEGV when I turn off the monirot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1757961/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
