[Desktop-packages] [Bug 1722454] Re: Duplicity fails with MemoryError
** Also affects: duplicity
Importance: Undecided
Status: New
--
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/1722454
Title:
Duplicity fails with MemoryError
Status in Duplicity:
New
Status in duplicity package in Ubuntu:
New
Bug description:
Running the following command:
/usr/bin/python /usr/bin/duplicity collection-status
--exclude=/mnt/jabba/juergh/backup/gollum
--include=/home/juergh/.cache/deja-dup/metadata --exclude=/home/juergh
/.uk-pkg --exclude=/home/juergh/Music --exclude=/home/juergh/debug
--exclude=/home/juergh/canonical/cve-matrix/cve-matrix/cve-tracker
--exclude=/home/juergh/canonical/cve-matrix/cve-autotriage
--exclude=/home/juergh/Desktop --exclude=/home/juergh/.cache
--exclude=/home/juergh/tmp --exclude=/home/juergh/git
--exclude=/home/juergh/Downloads
--exclude=/home/juergh/.local/share/Trash
--exclude=/home/juergh/.cache/deja-dup/tmp
--exclude=/home/juergh/.thumbnails --exclude=/home/juergh/.cache/deja-
dup --exclude=/home/juergh/.cache --include=/home/juergh
--exclude=/sys --exclude=/run --exclude=/proc --exclude=/var/tmp
--exclude=/tmp --exclude=** --gio
file:///mnt/jabba/juergh/backup/gollum --no-encryption --verbosity=9
--gpg-options=--no-use-agent --archive-dir=/home/juergh/.cache/deja-
dup --tempdir=/home/juergh/.cache/deja-dup/tmp --log-fd=19
results in:
Traceback (most recent call last):
File "/usr/bin/duplicity", line 1546, in
with_tempdir(main)
File "/usr/bin/duplicity", line 1540, in with_tempdir
fn()
File "/usr/bin/duplicity", line 1391, in main
do_backup(action)
File "/usr/bin/duplicity", line 1416, in do_backup
globals.archive_dir).set_values()
File "/usr/lib/python2.7/dist-packages/duplicity/collections.py", line 710,
in set_values
self.get_backup_chains(partials + backend_filename_list)
File "/usr/lib/python2.7/dist-packages/duplicity/collections.py", line 836,
in get_backup_chains
add_to_sets(f)
File "/usr/lib/python2.7/dist-packages/duplicity/collections.py", line 824,
in add_to_sets
if set.add_filename(filename):
File "/usr/lib/python2.7/dist-packages/duplicity/collections.py", line 101,
in add_filename
self.set_manifest(filename)
File "/usr/lib/python2.7/dist-packages/duplicity/collections.py", line 148,
in set_manifest
self.set_files_changed()
File "/usr/lib/python2.7/dist-packages/duplicity/collections.py", line 128,
in set_files_changed
mf = self.get_manifest()
File "/usr/lib/python2.7/dist-packages/duplicity/collections.py", line 250,
in get_manifest
return self.get_local_manifest()
File "/usr/lib/python2.7/dist-packages/duplicity/collections.py", line 224,
in get_local_manifest
return manifest.Manifest().from_string(manifest_buffer)
File "/usr/lib/python2.7/dist-packages/duplicity/manifest.py", line 215, in
from_string
vi = VolumeInfo().from_string(match.group(1))
File "/usr/lib/python2.7/dist-packages/duplicity/manifest.py", line 383, in
from_string
linelist = s.strip().split("\n")
MemoryError
ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: duplicity 0.7.12-1ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
Uname: Linux 4.13.0-12-generic x86_64
ApportVersion: 2.20.7-0ubuntu2
Architecture: amd64
CurrentDesktop: GNOME
Date: Tue Oct 10 08:05:45 2017
InstallationDate: Installed on 2017-05-25 (137 days ago)
InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
SourcePackage: duplicity
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/duplicity/+bug/1722454/+subscriptions
--
Mailing list: https://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 1726717] [NEW] Alignment of external screen limits placing of icons
Public bug reported: Reporting against gnome-desktop since I do not know better. Please assign to appropriate package. Thanks! Using external monitors with the gnome desktop behaves unexpected in a few ways. One is, that the alignment of screens limits, where icons can be placed on that screens: My external monitor is higher than the internal screen of my laptop. I have aligned the screens at the bottom. This makes the bottom part of the (external, higher) screen unusable for placing icons. This is probably best seen on the attached screenshot. Thanks for caring! ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-session (not installed) ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 24 08:49:30 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2015-12-13 (680 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: gnome-session UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-session (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful wayland-session ** Attachment added: "Alignment of screens limits where icons can be placed." https://bugs.launchpad.net/bugs/1726717/+attachment/4990296/+files/Screen-alignment-icons.jpg -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1726717 Title: Alignment of external screen limits placing of icons Status in gnome-session package in Ubuntu: New Bug description: Reporting against gnome-desktop since I do not know better. Please assign to appropriate package. Thanks! Using external monitors with the gnome desktop behaves unexpected in a few ways. One is, that the alignment of screens limits, where icons can be placed on that screens: My external monitor is higher than the internal screen of my laptop. I have aligned the screens at the bottom. This makes the bottom part of the (external, higher) screen unusable for placing icons. This is probably best seen on the attached screenshot. Thanks for caring! ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-session (not installed) ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 24 08:49:30 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2015-12-13 (680 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: gnome-session UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1726717/+subscriptions -- Mailing list: https://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 1724583] Re: gdm3 in Ubuntu 17.10 doesn't list wayland sessions when using hybrid graphics
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-shell (Ubuntu) Status: New => Confirmed -- 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/1724583 Title: gdm3 in Ubuntu 17.10 doesn't list wayland sessions when using hybrid graphics Status in gdm3 package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Status in gdm3 package in Fedora: Unknown Bug description: I've just upgraded to Ubuntu 17.10 and switched the login manager from sddm to gdm3. Unfortunately it doesn't list the -wayland sessions. The /usr/share/xsessions folder indeed only contains the -xorg -related sessions: $ ls -la /usr/share/xsessions total 36 drwxr-xr-x 2 root root 4096 okt 18 16:00 . drwxr-xr-x 427 root root 20480 okt 18 15:56 .. -rw-r--r-- 1 root root 201 okt 13 12:56 gnome-xorg.desktop -rw-r--r-- 1 root root 2354 aug 23 16:39 plasma.desktop -rw-r--r-- 1 root root 262 okt 13 12:56 ubuntu-xorg.desktop How can I enable the ubuntu-wayland session please? ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gdm3 3.26.1-3ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Oct 18 16:37:47 2017 InstallationDate: Installed on 2016-09-05 (408 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: gdm3 UpgradeStatus: Upgraded to artful on 2017-10-18 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1724583/+subscriptions -- Mailing list: https://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 1724877] Re: nautilus crashed with SIGABRT in g_assertion_message() (slot_proxy_drag_data_received)
Hi Sebastien, It is not currently reproductible as it happened when i was just using the system in no specific way. -- 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/1724877 Title: nautilus crashed with SIGABRT in g_assertion_message() (slot_proxy_drag_data_received) Status in nautilus package in Ubuntu: Incomplete Bug description: 1) ubuntu 17.10 2) no package 3) no crash 4) crash ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: nautilus 1:3.26.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Oct 19 17:06:01 2017 ExecutablePath: /usr/bin/nautilus InstallationDate: Installed on 2017-10-19 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcCmdline: /usr/bin/nautilus --gapplication-service ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANGUAGE=fr_BE:fr LANG=fr_BE.UTF-8 Signal: 6 SourcePackage: nautilus StacktraceTop: g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: nautilus crashed with SIGABRT in g_assertion_message() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1724877/+subscriptions -- Mailing list: https://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 1724583] Re: gdm3 in Ubuntu 17.10 doesn't list wayland sessions when using hybrid graphics
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gdm3 (Ubuntu) Status: New => Confirmed -- 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/1724583 Title: gdm3 in Ubuntu 17.10 doesn't list wayland sessions when using hybrid graphics Status in gdm3 package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Status in gdm3 package in Fedora: Unknown Bug description: I've just upgraded to Ubuntu 17.10 and switched the login manager from sddm to gdm3. Unfortunately it doesn't list the -wayland sessions. The /usr/share/xsessions folder indeed only contains the -xorg -related sessions: $ ls -la /usr/share/xsessions total 36 drwxr-xr-x 2 root root 4096 okt 18 16:00 . drwxr-xr-x 427 root root 20480 okt 18 15:56 .. -rw-r--r-- 1 root root 201 okt 13 12:56 gnome-xorg.desktop -rw-r--r-- 1 root root 2354 aug 23 16:39 plasma.desktop -rw-r--r-- 1 root root 262 okt 13 12:56 ubuntu-xorg.desktop How can I enable the ubuntu-wayland session please? ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gdm3 3.26.1-3ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Oct 18 16:37:47 2017 InstallationDate: Installed on 2016-09-05 (408 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: gdm3 UpgradeStatus: Upgraded to artful on 2017-10-18 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1724583/+subscriptions -- Mailing list: https://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 1556435] Re: totem crashed with SIGSEGV
*** This bug is a duplicate of bug 1574253 *** https://bugs.launchpad.net/bugs/1574253 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: totem (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1556435 Title: totem crashed with SIGSEGV Status in totem package in Ubuntu: Confirmed Bug description: Just opening Totem causes it to segfault: $ totem Segmentation fault (core dumped) The machine in question is an old desktop with Pentium 4 and Radeon 9200 SE AGP graphics card, Radeon driver. The OS is Ubuntu 16.04 with gnome-flashback (metacity). ~$ lscpu Architecture: i686 CPU op-mode(s):32-bit Byte Order:Little Endian CPU(s):2 On-line CPU(s) list: 0,1 Thread(s) per core:2 Core(s) per socket:1 Socket(s): 1 Vendor ID: GenuineIntel CPU family:15 Model: 4 Model name:Intel(R) Pentium(R) 4 CPU 3.00GHz Stepping: 1 CPU MHz: 3060.436 BogoMIPS: 6120.87 L1d cache: 16K L2 cache: 1024K Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx constant_tsc pebs bts pni dtes64 monitor ds_cpl cid xtpr Full hardware specs are at http://paste.ubuntu.com/15360138/. ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: totem 3.18.1-1ubuntu4 ProcVersionSignature: Ubuntu 4.4.0-12.28-generic 4.4.4 Uname: Linux 4.4.0-12-generic i686 ApportVersion: 2.20-0ubuntu3 Architecture: i386 CrashCounter: 1 CurrentDesktop: GNOME-Flashback:Unity Date: Sat Mar 12 17:45:41 2016 Disassembly: => 0x1: Cannot access memory at address 0x1 ExecutablePath: /usr/bin/totem InstallationDate: Installed on 2016-02-14 (26 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha i386 (20160212) ProcCmdline: totem SegvAnalysis: Segfault happened at: 0x1: Cannot access memory at address 0x1 PC (0x0001) not located in a known VMA region (needed executable region)! SegvReason: executing NULL VMA Signal: 11 SourcePackage: totem StacktraceTop: ?? () ?? () from /usr/lib/i386-linux-gnu/libcogl.so.20 ?? () from /usr/lib/i386-linux-gnu/libcogl.so.20 ?? () from /usr/lib/i386-linux-gnu/libcogl.so.20 ?? () from /usr/lib/i386-linux-gnu/libcogl.so.20 Title: totem crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1556435/+subscriptions -- Mailing list: https://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 1726714] Re: gnome-control-center crashed with SIGABRT in g_assertion_message()
*** This bug is a duplicate of bug 1720441 *** https://bugs.launchpad.net/bugs/1720441 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1720441, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1726714/+attachment/4990274/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1726714/+attachment/4990276/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1726714/+attachment/4990279/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1726714/+attachment/4990280/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1726714/+attachment/4990281/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1726714/+attachment/4990282/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1726714/+attachment/4990283/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1720441 ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- 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/1726714 Title: gnome-control-center crashed with SIGABRT in g_assertion_message() Status in gnome-control-center package in Ubuntu: New Bug description: The control center crashed ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: gnome-control-center 1:3.26.1-0ubuntu4 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 24 08:42:43 2017 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2017-10-23 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcCmdline: gnome-control-center wifi ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash Signal: 6 SourcePackage: gnome-control-center StacktraceTop: g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libnma.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libnma.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libnma.so.0 Title: gnome-control-center crashed with SIGABRT in g_assertion_message() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1726714/+subscriptions -- Mailing list: https://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 1726707] Re: gnome-software crashes machine hard
tried to get additional information via recipes in https://help.ubuntu.com/community/DebuggingSystemCrash but no luck. - Alt-SysRq does nothing at all - linux-crashdump was successfully installed (checked via /proc/cmdline) but there is nothing in /var/crash after powercycle - tracing the system logfiles via ssh revealed no further information -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1726707 Title: gnome-software crashes machine hard Status in gnome-software package in Ubuntu: New Bug description: gnome-software instantly crashes my machine hard reproducible, only forced power off possible. mouse stuck, no num-lock, machine not pingable anymore. as there is no crash report whatsoever generated i installed ssh on the machine and started "DISPLAY=:0 gnome-software --verbose" via ssh session, output attached. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1726707/+subscriptions -- Mailing list: https://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 1723857] Re: onscreen keyboard appears whenever i touch touchscreen
*** This bug is a duplicate of bug 1721315 *** https://bugs.launchpad.net/bugs/1721315 Well I experience the same issue without using a stylus or keyboard and I was tracking bug 1721315. The pre-conditions may be unimportant so let's assume it's the same bug. If it's not then please clarify in the description here how this one is different. As for X11 vs Wayland, for high-level behaviour like whether something is displayed at all, those should always be the same for both X11 and Wayland. So that distinction should be irrelevant until proven otherwise. It's also not necessary to copy the entire contents from an upstream bug. Although for some bug trackers LaunchPad will do it automatically. Bug 1721315 is also older than this one, which is preferred when deduplicating bugs. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-desktop in Ubuntu. https://bugs.launchpad.net/bugs/1723857 Title: onscreen keyboard appears whenever i touch touchscreen Status in gnome-desktop: Confirmed Status in Ubuntu: Confirmed Status in caribou package in Ubuntu: Confirmed Status in gnome-desktop package in Ubuntu: Confirmed Bug description: I'm in 17.10. Whenever I touch the touchscreen, the keyboard appears. It is disabled in System Preferences > Universal Access. This didn't happen in any previous Ubuntus, including 17.04 GNOME, nor in Fedora, which is GNOME based. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-desktop/+bug/1723857/+subscriptions -- Mailing list: https://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 1667659] Re: signon-ui crashed with SIGSEGV in QWindow::show()
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: signon-ui (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to signon-ui in Ubuntu. https://bugs.launchpad.net/bugs/1667659 Title: signon-ui crashed with SIGSEGV in QWindow::show() Status in signon-ui package in Ubuntu: Confirmed Bug description: NA ProblemType: Crash DistroRelease: Ubuntu 17.04 Package: signon-ui-x11 0.17+17.04.20161109-0ubuntu1 Uname: Linux 4.10.0-041000-lowlatency x86_64 ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 CrashCounter: 1 CurrentDesktop: Unity:Unity7 Date: Fri Feb 24 18:45:43 2017 ExecutablePath: /usr/bin/signon-ui InstallationDate: Installed on 2017-02-24 (0 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170224) ProcCmdline: /usr/bin/signon-ui SegvAnalysis: Segfault happened at: 0x7f5ae5b478de <_ZN7QWindow4showEv+14>:mov 0x8(%rbx),%rax PC (0x7f5ae5b478de) ok source "0x8(%rbx)" (0x0008) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: signon-ui StacktraceTop: QWindow::show() () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5 ?? () ?? () ?? () ?? () Title: signon-ui crashed with SIGSEGV in QWindow::show() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/signon-ui/+bug/1667659/+subscriptions -- Mailing list: https://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 1726716] Re: gvfsd-mtp crashed with SIGSEGV
*** This bug is a duplicate of bug 1706097 *** https://bugs.launchpad.net/bugs/1706097 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1706097, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1726716/+attachment/4990284/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1726716/+attachment/4990286/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1726716/+attachment/4990290/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1726716/+attachment/4990291/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1726716/+attachment/4990292/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1726716/+attachment/4990293/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1726716/+attachment/4990294/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1706097 gvfsd-mtp crashed with SIGSEGV ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- 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/1726716 Title: gvfsd-mtp crashed with SIGSEGV Status in gvfs package in Ubuntu: New Bug description: ubuntu 17.10 ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: gvfs-backends 1.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Oct 24 12:33:21 2017 ExecutablePath: /usr/lib/gvfs/gvfsd-mtp ProcCmdline: /usr/lib/gvfs/gvfsd-mtp --spawner :1.22 /org/gtk/gvfs/exec_spaw/9 SegvAnalysis: Segfault happened at: 0x7ff69fbc65a9:mov0x18(%rax),%rax PC (0x7ff69fbc65a9) ok source "0x18(%rax)" (0x0018) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gvfs StacktraceTop: () at /usr/lib/x86_64-linux-gnu/gvfs/libgvfsdaemon.so () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 Title: gvfsd-mtp crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip kvm libvirt lpadmin lxd plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1726716/+subscriptions -- Mailing list: https://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 1725526] Re: gnome-control-center crashed with SIGSEGV in g_type_check_instance_cast()
*** This bug is a duplicate of bug 1725219 *** https://bugs.launchpad.net/bugs/1725219 ** This bug has been marked a duplicate of bug 1725219 /usr/bin/gnome-control-center:11:g_type_check_instance_cast:ext_ubuntu_dock_placement_changed_callback:g_closure_invoke:signal_emit_unlocked_R:g_signal_emit_valist -- 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/1725526 Title: gnome-control-center crashed with SIGSEGV in g_type_check_instance_cast() Status in gnome-control-center package in Ubuntu: In Progress Bug description: automatic bug report ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: gnome-control-center 1:3.26.1-0ubuntu4 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Oct 20 19:33:33 2017 EcryptfsInUse: Yes ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2017-08-22 (59 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) ProcCmdline: gnome-control-center --overview ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7f5cf12c8de2 : mov(%rdi),%rbp PC (0x7f5cf12c8de2) ok source "(%rdi)" (0x3ff0) not located in a known VMA region (needed readable region)! destination "%rbp" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: gnome-control-center StacktraceTop: g_type_check_instance_cast () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: gnome-control-center crashed with SIGSEGV in g_type_check_instance_cast() UpgradeStatus: Upgraded to artful on 2017-10-20 (0 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1725526/+subscriptions -- Mailing list: https://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 1726735] [NEW] DNS resolve.conf error
Public bug reported: ubuntu 17.10, systemd-resolved listen 127.0.0.53 but 127.0.1.1 setted in resolve.conf !! andy@Andy-Desktop:~$ uname -a Linux Andy-Desktop 4.13.0-16-generic #19-Ubuntu SMP Wed Oct 11 18:35:14 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux andy@Andy-Desktop:~$ cat /etc/resolv.conf # Generated by NetworkManager search 9office nameserver 127.0.1.1 andy@Andy-Desktop:~$ sudo netstat -nlup| grep resolve udp0 0 127.0.0.53:53 0.0.0.0:* 700/systemd-resolve udp0 0 0.0.0.0:53550.0.0.0:* 700/systemd-resolve udp6 0 0 :::5355 :::* 700/systemd-resolve andy@Andy-Desktop:~$ ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: 127.0.0.53 ** Description changed: - ubuntu 17.10, systemd-resolved listen 127.0.0.53 but 127.0.1.1 seted in + ubuntu 17.10, systemd-resolved listen 127.0.0.53 but 127.0.1.1 setted in resolve.conf !! andy@Andy-Desktop:~$ uname -a Linux Andy-Desktop 4.13.0-16-generic #19-Ubuntu SMP Wed Oct 11 18:35:14 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux - andy@Andy-Desktop:~$ cat /etc/resolv.conf + andy@Andy-Desktop:~$ cat /etc/resolv.conf # Generated by NetworkManager search 9office nameserver 127.0.1.1 - andy@Andy-Desktop:~$ sudo netstat -nlup| grep resolve - udp0 0 127.0.0.53:53 0.0.0.0:* 700/systemd-resolve - udp0 0 0.0.0.0:53550.0.0.0:* 700/systemd-resolve - udp6 0 0 :::5355 :::* 700/systemd-resolve + udp0 0 127.0.0.53:53 0.0.0.0:* 700/systemd-resolve + udp0 0 0.0.0.0:53550.0.0.0:* 700/systemd-resolve + udp6 0 0 :::5355 :::* 700/systemd-resolve andy@Andy-Desktop:~$ ** Tags added: 127.0.0.53 -- 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/1726735 Title: DNS resolve.conf error Status in network-manager package in Ubuntu: New Bug description: ubuntu 17.10, systemd-resolved listen 127.0.0.53 but 127.0.1.1 setted in resolve.conf !! andy@Andy-Desktop:~$ uname -a Linux Andy-Desktop 4.13.0-16-generic #19-Ubuntu SMP Wed Oct 11 18:35:14 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux andy@Andy-Desktop:~$ cat /etc/resolv.conf # Generated by NetworkManager search 9office nameserver 127.0.1.1 andy@Andy-Desktop:~$ sudo netstat -nlup| grep resolve udp0 0 127.0.0.53:53 0.0.0.0:* 700/systemd-resolve udp0 0 0.0.0.0:53550.0.0.0:* 700/systemd-resolve udp6 0 0 :::5355 :::* 700/systemd-resolve andy@Andy-Desktop:~$ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1726735/+subscriptions -- Mailing list: https://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 1726739] [NEW] package cracklib-runtime 2.9.2-5build1 failed to install/upgrade: dependency problems - leaving triggers unprocessed
Public bug reported: upgrade to 17.10 ProblemType: Package DistroRelease: Ubuntu 17.10 Package: cracklib-runtime 2.9.2-5build1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 Date: Tue Oct 24 01:18:27 2017 ErrorMessage: dependency problems - leaving triggers unprocessed InstallationDate: Installed on 2017-01-14 (282 days ago) InstallationMedia: Ubuntu-MATE 16.10 "Yakkety Yak" - Release amd64 (20161012.1) Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-2ubuntu1 RelatedPackageVersions: dpkg 1.18.24ubuntu1 apt 1.5 SourcePackage: cracklib2 Title: package cracklib-runtime 2.9.2-5build1 failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: Upgraded to artful on 2017-10-24 (0 days ago) ** Affects: cracklib2 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package artful -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cracklib2 in Ubuntu. https://bugs.launchpad.net/bugs/1726739 Title: package cracklib-runtime 2.9.2-5build1 failed to install/upgrade: dependency problems - leaving triggers unprocessed Status in cracklib2 package in Ubuntu: New Bug description: upgrade to 17.10 ProblemType: Package DistroRelease: Ubuntu 17.10 Package: cracklib-runtime 2.9.2-5build1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 Date: Tue Oct 24 01:18:27 2017 ErrorMessage: dependency problems - leaving triggers unprocessed InstallationDate: Installed on 2017-01-14 (282 days ago) InstallationMedia: Ubuntu-MATE 16.10 "Yakkety Yak" - Release amd64 (20161012.1) Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-2ubuntu1 RelatedPackageVersions: dpkg 1.18.24ubuntu1 apt 1.5 SourcePackage: cracklib2 Title: package cracklib-runtime 2.9.2-5build1 failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: Upgraded to artful on 2017-10-24 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cracklib2/+bug/1726739/+subscriptions -- Mailing list: https://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 1726738] [NEW] package cracklib-runtime 2.9.2-5build1 failed to install/upgrade: dependency problems - leaving triggers unprocessed
*** This bug is a duplicate of bug 1726739 *** https://bugs.launchpad.net/bugs/1726739 Public bug reported: upgrade to 17.10 ProblemType: Package DistroRelease: Ubuntu 17.10 Package: cracklib-runtime 2.9.2-5build1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 Date: Tue Oct 24 01:18:27 2017 ErrorMessage: dependency problems - leaving triggers unprocessed InstallationDate: Installed on 2017-01-14 (282 days ago) InstallationMedia: Ubuntu-MATE 16.10 "Yakkety Yak" - Release amd64 (20161012.1) Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-2ubuntu1 RelatedPackageVersions: dpkg 1.18.24ubuntu1 apt 1.5 SourcePackage: cracklib2 Title: package cracklib-runtime 2.9.2-5build1 failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: Upgraded to artful on 2017-10-24 (0 days ago) ** Affects: cracklib2 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package artful -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cracklib2 in Ubuntu. https://bugs.launchpad.net/bugs/1726738 Title: package cracklib-runtime 2.9.2-5build1 failed to install/upgrade: dependency problems - leaving triggers unprocessed Status in cracklib2 package in Ubuntu: New Bug description: upgrade to 17.10 ProblemType: Package DistroRelease: Ubuntu 17.10 Package: cracklib-runtime 2.9.2-5build1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 Date: Tue Oct 24 01:18:27 2017 ErrorMessage: dependency problems - leaving triggers unprocessed InstallationDate: Installed on 2017-01-14 (282 days ago) InstallationMedia: Ubuntu-MATE 16.10 "Yakkety Yak" - Release amd64 (20161012.1) Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-2ubuntu1 RelatedPackageVersions: dpkg 1.18.24ubuntu1 apt 1.5 SourcePackage: cracklib2 Title: package cracklib-runtime 2.9.2-5build1 failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: Upgraded to artful on 2017-10-24 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cracklib2/+bug/1726738/+subscriptions -- Mailing list: https://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 1726306] Re: Failure to reactivate display after locking
It's definitely not (directly) related to either of those - I can't even get the display to come back on, let alone enter a password at the lock screen. -- 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/1726306 Title: Failure to reactivate display after locking Status in gdm3 package in Ubuntu: New Status in gnome-shell package in Ubuntu: New Bug description: I'm using a laptop with no external monitors attached (System76 Oryx Pro 2016). After the screen is locked (either manually or via timeout) and it blanks/deactivates the screen, the display remains deactivated and my session is unrecoverable. (I can still ssh into the machine, but have so far been unable to get the display back without rebooting, even via restarting gdm.) It seems somewhat similar to https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1715811 , but it's only after the display is deactivated, and not at boot. The scope of the problem seems to be compounded by the fact that there's no straightforward way to prevent gnome-shell from blanking the screen when it locks. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gdm3 3.26.1-3ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Oct 23 10:20:55 2017 SourcePackage: gdm3 UpgradeStatus: Upgraded to artful on 2017-10-20 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1726306/+subscriptions -- Mailing list: https://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 1726744] [NEW] package libsane1 1.0.27-1~experimental2ubuntu1 failed to install/upgrade: Versuch, gemeinsam benutztes »/lib/udev/hwdb.d/20-sane.hwdb« zu überschreiben, welches
Public bug reported: lsb_release -rd: Description:Ubuntu 17.10 Release:17.10 apt-cache policy libsane1: Installiert: 1.0.27-1~experimental2ubuntu1 Installationskandidat: 1.0.27-1~experimental2ubuntu1 Versionstabelle: *** 1.0.27-1~experimental2ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu artful/main amd64 Packages 100 /var/lib/dpkg/status What I expected to happen: A normal installation What happened instead: Following Errormessage: "package libsane1 1.0.27-1~experimental2ubuntu1 failed to install/upgrade: Versuch, gemeinsam benutztes »/lib/udev/hwdb.d/20-sane.hwdb« zu überschreiben, welches verschieden von anderen Instanzen des Paketes libsane1:i386 ist" ProblemType: Package DistroRelease: Ubuntu 17.10 Package: libsane1 1.0.27-1~experimental2ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 Date: Mon Oct 23 16:52:45 2017 ErrorMessage: Versuch, gemeinsam benutztes »/lib/udev/hwdb.d/20-sane.hwdb« zu überschreiben, welches verschieden von anderen Instanzen des Paketes libsane1:i386 ist Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-2ubuntu1 RelatedPackageVersions: dpkg 1.18.24ubuntu1 apt 1.5 SourcePackage: sane-backends Title: package libsane1 1.0.27-1~experimental2ubuntu1 failed to install/upgrade: Versuch, gemeinsam benutztes »/lib/udev/hwdb.d/20-sane.hwdb« zu überschreiben, welches verschieden von anderen Instanzen des Paketes libsane1:i386 ist UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: sane-backends (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package artful -- 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/1726744 Title: package libsane1 1.0.27-1~experimental2ubuntu1 failed to install/upgrade: Versuch, gemeinsam benutztes »/lib/udev/hwdb.d/20-sane.hwdb« zu überschreiben, welches verschieden von anderen Instanzen des Paketes libsane1:i386 ist Status in sane-backends package in Ubuntu: New Bug description: lsb_release -rd: Description: Ubuntu 17.10 Release: 17.10 apt-cache policy libsane1: Installiert: 1.0.27-1~experimental2ubuntu1 Installationskandidat: 1.0.27-1~experimental2ubuntu1 Versionstabelle: *** 1.0.27-1~experimental2ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu artful/main amd64 Packages 100 /var/lib/dpkg/status What I expected to happen: A normal installation What happened instead: Following Errormessage: "package libsane1 1.0.27-1~experimental2ubuntu1 failed to install/upgrade: Versuch, gemeinsam benutztes »/lib/udev/hwdb.d/20-sane.hwdb« zu überschreiben, welches verschieden von anderen Instanzen des Paketes libsane1:i386 ist" ProblemType: Package DistroRelease: Ubuntu 17.10 Package: libsane1 1.0.27-1~experimental2ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 Date: Mon Oct 23 16:52:45 2017 ErrorMessage: Versuch, gemeinsam benutztes »/lib/udev/hwdb.d/20-sane.hwdb« zu überschreiben, welches verschieden von anderen Instanzen des Paketes libsane1:i386 ist Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-2ubuntu1 RelatedPackageVersions: dpkg 1.18.24ubuntu1 apt 1.5 SourcePackage: sane-backends Title: package libsane1 1.0.27-1~experimental2ubuntu1 failed to install/upgrade: Versuch, gemeinsam benutztes »/lib/udev/hwdb.d/20-sane.hwdb« zu überschreiben, welches verschieden von anderen Instanzen des Paketes libsane1:i386 ist 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/1726744/+subscriptions -- Mailing list: https://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 1725190] Re: Please update modemmanager in xenial to the 1.6 series
** Changed in: modemmanager (Ubuntu) Assignee: (unassigned) => Alfonso Sanchez-Beato (alfonsosanchezbeato) ** Changed in: oem-priority Assignee: (unassigned) => Alex Tu (alextu) ** Changed in: modemmanager (Ubuntu) Importance: Undecided => Critical ** Changed in: modemmanager (Ubuntu) Status: New => In Progress ** Changed in: oem-priority Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1725190 Title: Please update modemmanager in xenial to the 1.6 series Status in OEM Priority Project: Confirmed Status in modemmanager package in Ubuntu: In Progress Bug description: We would like to upgrade xenial to 1.6 series so it supports the same modems as the modem-manager snap, specifically some new Sierra modems (HL8548 and others from HL series, popular in IoT devices). These are the packages that would need to be updated: libmbim: 1.12.2-2ubuntu1 in xenial, 1.14.0 in snap libqmi: 1.12.6-1 in xenial, 1.16.2 in snap modemmanager: 1.4.12-1ubuntu1 in xenial, 1.6.2 in snap This is also related to bug #1693756 which includes a subset of patches of what would be updated. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1725190/+subscriptions -- Mailing list: https://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 1726739] Re: package cracklib-runtime 2.9.2-5build1 failed to install/upgrade: dependency problems - leaving triggers unprocessed
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cracklib2 in Ubuntu. https://bugs.launchpad.net/bugs/1726739 Title: package cracklib-runtime 2.9.2-5build1 failed to install/upgrade: dependency problems - leaving triggers unprocessed Status in cracklib2 package in Ubuntu: New Bug description: upgrade to 17.10 ProblemType: Package DistroRelease: Ubuntu 17.10 Package: cracklib-runtime 2.9.2-5build1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 Date: Tue Oct 24 01:18:27 2017 ErrorMessage: dependency problems - leaving triggers unprocessed InstallationDate: Installed on 2017-01-14 (282 days ago) InstallationMedia: Ubuntu-MATE 16.10 "Yakkety Yak" - Release amd64 (20161012.1) Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-2ubuntu1 RelatedPackageVersions: dpkg 1.18.24ubuntu1 apt 1.5 SourcePackage: cracklib2 Title: package cracklib-runtime 2.9.2-5build1 failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: Upgraded to artful on 2017-10-24 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cracklib2/+bug/1726739/+subscriptions -- Mailing list: https://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 1726738] Re: package cracklib-runtime 2.9.2-5build1 failed to install/upgrade: dependency problems - leaving triggers unprocessed
*** This bug is a duplicate of bug 1726739 *** https://bugs.launchpad.net/bugs/1726739 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1726739, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Tags removed: need-duplicate-check ** This bug has been marked a duplicate of bug 1726739 package cracklib-runtime 2.9.2-5build1 failed to install/upgrade: dependency problems - leaving triggers unprocessed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cracklib2 in Ubuntu. https://bugs.launchpad.net/bugs/1726738 Title: package cracklib-runtime 2.9.2-5build1 failed to install/upgrade: dependency problems - leaving triggers unprocessed Status in cracklib2 package in Ubuntu: New Bug description: upgrade to 17.10 ProblemType: Package DistroRelease: Ubuntu 17.10 Package: cracklib-runtime 2.9.2-5build1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 Date: Tue Oct 24 01:18:27 2017 ErrorMessage: dependency problems - leaving triggers unprocessed InstallationDate: Installed on 2017-01-14 (282 days ago) InstallationMedia: Ubuntu-MATE 16.10 "Yakkety Yak" - Release amd64 (20161012.1) Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-2ubuntu1 RelatedPackageVersions: dpkg 1.18.24ubuntu1 apt 1.5 SourcePackage: cracklib2 Title: package cracklib-runtime 2.9.2-5build1 failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: Upgraded to artful on 2017-10-24 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cracklib2/+bug/1726738/+subscriptions -- Mailing list: https://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 1726745] [NEW] gnome-shell crashed with signal 5 in _XIOError()
*** This bug is a duplicate of bug 1556601 *** https://bugs.launchpad.net/bugs/1556601 Public bug reported: 1) Description: Ubuntu 17.10 Release:17.10 2) gnome-shell: Installé : 3.26.1-0ubuntu4 Candidat : 3.26.1-0ubuntu4 Table de version : *** 3.26.1-0ubuntu4 500 500 http://fr.archive.ubuntu.com/ubuntu artful/main amd64 Packages 100 /var/lib/dpkg/status 3) When I open a new user session I've got this issue. I can use Ubuntu without trouble but I've got this error message. I had 3 packages outdated I updated them. 4) But I've always the same error when I start a session. ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.1-0ubuntu4 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CrashCounter: 1 CurrentDesktop: GNOME-Greeter:GNOME Date: Tue Oct 24 09:55:09 2017 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: InstallationDate: Installed on 2017-10-22 (1 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/false Signal: 5 SourcePackage: gnome-shell StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libmutter-1.so.0 _XIOError () from /usr/lib/x86_64-linux-gnu/libX11.so.6 _XReply () from /usr/lib/x86_64-linux-gnu/libX11.so.6 XSync () from /usr/lib/x86_64-linux-gnu/libX11.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 Title: gnome-shell crashed with signal 5 in _XIOError() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash artful ** Information type changed from Private to Public -- 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/1726745 Title: gnome-shell crashed with signal 5 in _XIOError() Status in gnome-shell package in Ubuntu: New Bug description: 1) Description: Ubuntu 17.10 Release: 17.10 2) gnome-shell: Installé : 3.26.1-0ubuntu4 Candidat : 3.26.1-0ubuntu4 Table de version : *** 3.26.1-0ubuntu4 500 500 http://fr.archive.ubuntu.com/ubuntu artful/main amd64 Packages 100 /var/lib/dpkg/status 3) When I open a new user session I've got this issue. I can use Ubuntu without trouble but I've got this error message. I had 3 packages outdated I updated them. 4) But I've always the same error when I start a session. ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.1-0ubuntu4 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CrashCounter: 1 CurrentDesktop: GNOME-Greeter:GNOME Date: Tue Oct 24 09:55:09 2017 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: InstallationDate: Installed on 2017-10-22 (1 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/false Signal: 5 SourcePackage: gnome-shell StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libmutter-1.so.0 _XIOError () from /usr/lib/x86_64-linux-gnu/libX11.so.6 _XReply () from /usr/lib/x86_64-linux-gnu/libX11.so.6 XSync () from /usr/lib/x86_64-linux-gnu/libX11.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 Title: gnome-shell crashed with signal 5 in _XIOError() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1726745/+subscriptions -- Mailing list: https://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 1726745] Re: gnome-shell crashed with signal 5 in _XIOError()
*** This bug is a duplicate of bug 1556601 *** https://bugs.launchpad.net/bugs/1556601 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1556601, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1726745/+attachment/4990399/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1726745/+attachment/4990401/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1726745/+attachment/4990404/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1726745/+attachment/4990405/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1726745/+attachment/4990406/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1726745/+attachment/4990407/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1726745/+attachment/4990408/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1556601 gnome-shell crashed with signal 5 in _XIOError() from _XReply() from XSync() ["Connection to xwayland lost"] ** Tags removed: need-amd64-retrace -- 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/1726745 Title: gnome-shell crashed with signal 5 in _XIOError() Status in gnome-shell package in Ubuntu: New Bug description: 1) Description: Ubuntu 17.10 Release: 17.10 2) gnome-shell: Installé : 3.26.1-0ubuntu4 Candidat : 3.26.1-0ubuntu4 Table de version : *** 3.26.1-0ubuntu4 500 500 http://fr.archive.ubuntu.com/ubuntu artful/main amd64 Packages 100 /var/lib/dpkg/status 3) When I open a new user session I've got this issue. I can use Ubuntu without trouble but I've got this error message. I had 3 packages outdated I updated them. 4) But I've always the same error when I start a session. ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.1-0ubuntu4 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CrashCounter: 1 CurrentDesktop: GNOME-Greeter:GNOME Date: Tue Oct 24 09:55:09 2017 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: InstallationDate: Installed on 2017-10-22 (1 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/false Signal: 5 SourcePackage: gnome-shell StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libmutter-1.so.0 _XIOError () from /usr/lib/x86_64-linux-gnu/libX11.so.6 _XReply () from /usr/lib/x86_64-linux-gnu/libX11.so.6 XSync () from /usr/lib/x86_64-linux-gnu/libX11.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 Title: gnome-shell crashed with signal 5 in _XIOError() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1726745/+subscriptions -- Mailing list: https://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 1720684] Re: Bluetooth speaker used the HSP/HFP profile by default rather than the higher-quality A2DP profile
** Changed in: pulseaudio (Ubuntu) Status: Confirmed => In Progress ** Changed in: pulseaudio (Ubuntu) Importance: Undecided => High -- 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/1720684 Title: Bluetooth speaker used the HSP/HFP profile by default rather than the higher-quality A2DP profile Status in PulseAudio: Fix Released Status in pulseaudio package in Ubuntu: In Progress Bug description: Kubuntu 17.04 Bluetooth device: https://smile.amazon.com/VicTsing-Wireless-Waterproof-Hands-Free-Speakerphone/dp/B074DX13T1 (itentifies itself as "C6") The above Bluetooth speaker paired and started streaming audio perfectly in Kubuntu 17.04. But the audio quality was poor, because the default audio profile was the low-quality HSP/HFP one. When I switched it to the A2DP profile, it sounded perfect again. Can we make A2DP the default playback profile for Bluetooth audio devices? To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1720684/+subscriptions -- Mailing list: https://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 1726741] Re: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast()
*** This bug is a duplicate of bug 1722986 *** https://bugs.launchpad.net/bugs/1722986 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1722986, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1726741/+attachment/4990363/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1726741/+attachment/4990365/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1726741/+attachment/4990370/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1726741/+attachment/4990371/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1726741/+attachment/4990372/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1726741/+attachment/4990373/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1726741/+attachment/4990374/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1722986 gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() from st_label_set_text() from object_set_property() from g_object_setv() from g_object_set_property() ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- 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/1726741 Title: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() Status in gnome-shell package in Ubuntu: New Bug description: Issue occurred on session load during login. ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.1-0ubuntu4 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Oct 24 10:48:39 2017 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2014-06-05 (1236 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) ProcCmdline: /usr/bin/gnome-shell SegvAnalysis: Segfault happened at: 0x7f3bf2a3cde2 : mov(%rdi),%rbp PC (0x7f3bf2a3cde2) ok source "(%rdi)" (0x55be) not located in a known VMA region (needed readable region)! destination "%rbp" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: gnome-shell StacktraceTop: g_type_check_instance_cast () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 st_label_set_text () at /usr/lib/gnome-shell/libst-1.0.so g_object_setv () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_object_set_property () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 () at /usr/lib/libgjs.so.0 Title: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() UpgradeStatus: Upgraded to artful on 2017-10-23 (0 days ago) UserGroups: adm bumblebee cdrom dip libvirt libvirtd lpadmin plugdev sambashare sudo vboxsf vboxusers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1726741/+subscriptions -- Mailing list: https://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 1715641] Re: network-manager built against glibc-2.26 requires GLIBC_2.25 symbol yet doesn't depend on recent enough glibc
** Changed in: dpkg (Ubuntu) Status: Triaged => Invalid -- 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/1715641 Title: network-manager built against glibc-2.26 requires GLIBC_2.25 symbol yet doesn't depend on recent enough glibc Status in binutils: Fix Released Status in binutils package in Ubuntu: Fix Released Status in debhelper package in Ubuntu: Invalid Status in dpkg package in Ubuntu: Invalid Status in glibc package in Ubuntu: Invalid Status in network-manager package in Ubuntu: Fix Released Status in dpkg package in Debian: Fix Released Bug description: network-manager built against glibc-2.26 requires GLIBC_2.25 symbol yet doesn't depend on recent enough glibc # cat debian/network-manager.substvars misc:Breaks=ppp (<< 2.4.7-1+~), ppp (>= 2.4.7-2~) misc:Depends=init-system-helpers (>= 1.18~) misc:Pre-Depends= shlibs:Depends=libaudit1 (>= 1:2.2.1), libbluetooth3 (>= 4.91), libc6 (>= 2.17), libcurl3-gnutls (>= 7.16.3), libglib2.0-0 (>= 2.43.2), libgnutls30 (>= 3.5.0), libjansson4 (>= 2.0.1), libmm-glib0 (>= 1.0.0), libndp0 (>= 1.2), libnewt0.52, libnl-3-200 (>= 3.2.21), libnm0 (>= 1.8.0), libpolkit-agent-1-0 (>= 0.99), libpolkit-gobject-1-0 (>= 0.104), libpsl5 (>= 0.13.0), libreadline7 (>= 6.0), libselinux1 (>= 1.32), libsystemd0 (>= 221), libudev1 (>= 183), libuuid1 (>= 2.16) # grep GLIBC_2.25 -r . Binary file ./debian/tmp/usr/sbin/NetworkManager matches Binary file ./debian/tmp/usr/lib/NetworkManager/nm-iface-helper matches Binary file ./debian/network-manager/usr/sbin/NetworkManager matches Binary file ./debian/network-manager/usr/lib/NetworkManager/nm-iface-helper matches Binary file ./src/NetworkManager matches Binary file ./src/nm-iface-helper matches Binary file ./src/devices/wifi/tests/test-general matches Binary file ./src/devices/tests/test-lldp matches Binary file ./src/dhcp/tests/test-dhcp-utils matches Binary file ./src/dhcp/tests/test-dhcp-dhclient matches Binary file ./src/tests/test-resolvconf-capture matches Binary file ./src/tests/test-ip4-config matches Binary file ./src/tests/test-ip6-config matches Binary file ./src/tests/test-general matches Binary file ./src/tests/test-systemd matches Binary file ./src/tests/config/test-config matches Binary file ./src/settings/plugins/keyfile/tests/test-keyfile matches # ldd /usr/sbin/NetworkManager /usr/sbin/NetworkManager: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.25' not found (required by /usr/sbin/NetworkManager) I will add a manual dep to network-manager but this is weird. To manage notifications about this bug go to: https://bugs.launchpad.net/binutils/+bug/1715641/+subscriptions -- Mailing list: https://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 1726608] Re: Alt+Arrow in gnome-shell unexpectedly switches VTs
Thanks for the report, but it's a console-setup and not a gnome-shell bug. It's changing the keyboard mode under our feet. I'm excited that you can trigger this from a chroot. The reproducer seems kind of niche, but I guess it's up to you & cyphermox whether you'd like to backport the fixes to stables (and whether they need altering along the way). ** Package changed: gnome-shell (Ubuntu) => console-setup (Ubuntu) ** Also affects: console-setup (Ubuntu Zesty) Importance: Undecided Status: New ** Also affects: console-setup (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: console-setup (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: console-setup (Ubuntu) Status: New => Fix Released -- 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/1726608 Title: Alt+Arrow in gnome-shell unexpectedly switches VTs Status in console-setup package in Ubuntu: Fix Released Status in console-setup source package in Trusty: New Status in console-setup source package in Xenial: New Status in console-setup source package in Zesty: New Bug description: I'm experiencing a bug similar to bug 1710637 with Ubuntu 17.10 again. Test Case - schroot -u root -c trusty-amd64 edit /etc/apt/sources.list to xenial apt-get update apt-get install console-setup use alt+tab to bring up the window switcher then use alt+arrow to switch windows I then end up at the gdm login screen or a virtual tty. Installing a different set of packages, via apt-get dist-upgrade, actually ended up killing my desktop session. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.1-0ubuntu4 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Oct 23 14:30:16 2017 DisplayManager: gdm3 EcryptfsInUse: Yes GsettingsChanges: b'org.gnome.shell' b'enabled-extensions' b"['sound-output-device-choo...@kgshank.net', 'multi-monitors-add-on@spin83', 'datetime-for...@daniel-khodabakhsh.github.com', 'ubuntu-appindicat...@ubuntu.com']" b'org.gnome.shell' b'favorite-apps' b"['org.gnome.Nautilus.desktop', 'terminator.desktop', 'virt-manager.desktop', 'chromium-browser.desktop', 'firefox.desktop', 'simple-scan.desktop']" b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" b'org.gnome.desktop.interface' b'clock-show-date' b'true' InstallationDate: Installed on 2013-01-16 (1741 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130116) 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/console-setup/+bug/1726608/+subscriptions -- Mailing list: https://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 1726753] Re: Après le démarrage de la session, et au bout de 30 secondes environ, un message apparaît signalant qu'une erreur s'est produite. D'autre part le clavier numérique
*** This bug is a duplicate of bug 1723342 *** https://bugs.launchpad.net/bugs/1723342 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1723342, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1726753/+attachment/4990455/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1726753/+attachment/4990457/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1726753/+attachment/4990461/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1726753/+attachment/4990462/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1726753/+attachment/4990463/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1726753/+attachment/4990464/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1726753/+attachment/4990465/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1723342 ** Information type changed from Private to Public ** Tags removed: need-i386-retrace -- 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/1726753 Title: Après le démarrage de la session, et au bout de 30 secondes environ, un message apparaît signalant qu'une erreur s'est produite. D'autre part le clavier numérique ne fonctionne pas. Status in nautilus package in Ubuntu: New Bug description: Il m'est difficile d'en dire plus. Sauf que je constate que ces bogues arrivent après la mise à niveau de Ubuntu 17.04 vers Ubuntu 17.10. trochet@trochet-ubuntu16:~$ lsb_release -rd Description: Ubuntu 17.10 Release: 17.10 Quel est le package utilisé juste après l'ouverture de session, étant donné que je n'ai rien ouvert? What you expected to happen? J'aimerais pouvoir continuer dans ma session. What happened instead? Sans etre dérangé par des messages d'erreur. Je viens aussi de voir que l'accent grave du verbe etre ne s'affiche pas. Avec la version précédente (Ubuntu 16.04 et 17.04) mon clavier (version Français-variante) fonctionnait parfaitement. ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: nautilus 1:3.26.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic i686 ApportVersion: 2.20.7-0ubuntu3 Architecture: i386 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 24 08:43:15 2017 ExecutablePath: /usr/bin/nautilus-desktop InstallationDate: Installed on 2015-10-07 (747 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release i386 (20150422) ProcCmdline: nautilus-desktop ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash Signal: 5 SourcePackage: nautilus StacktraceTop: ?? () from /usr/lib/i386-linux-gnu/libX11.so.6 ?? () from /usr/lib/i386-linux-gnu/libX11.so.6 _XEventsQueued () from /usr/lib/i386-linux-gnu/libX11.so.6 XPending () from /usr/lib/i386-linux-gnu/libX11.so.6 ?? () from /usr/lib/i386-linux-gnu/libgdk-3.so.0 Title: nautilus-desktop crashed with signal 5 in _XEventsQueued() UpgradeStatus: Upgraded to artful on 2017-10-22 (1 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1726753/+subscriptions -- Mailing list: https://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 1726764] [NEW] package libwinpr-input0.1:amd64 1.1.0~git20140921.1.440916e+dfsg1-5ubuntu1 [modified: usr/lib/x86_64-linux-gnu/libwinpr-input.so.0.1.0 usr/share/doc/libwinpr-inp
Public bug reported: dpkg ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libwinpr-input0.1:amd64 1.1.0~git20140921.1.440916e+dfsg1-5ubuntu1 [modified: usr/lib/x86_64-linux-gnu/libwinpr-input.so.0.1.0 usr/share/doc/libwinpr-input0.1/changelog.Debian.gz] ProcVersionSignature: Ubuntu 4.8.0-49.52~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-49-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 Date: Tue Oct 24 14:41:29 2017 Dependencies: gcc-6-base 6.0.1-0ubuntu1 libc6 2.23-0ubuntu9 libgcc1 1:6.0.1-0ubuntu1 DuplicateSignature: package:libwinpr-input0.1:amd64:1.1.0~git20140921.1.440916e+dfsg1-5ubuntu1 [modified: usr/lib/x86_64-linux-gnu/libwinpr-input.so.0.1.0 usr/share/doc/libwinpr-input0.1/changelog.Debian.gz] Processing triggers for libc-bin (2.23-0ubuntu9) ... dpkg: error processing package libwinpr-input0.1:amd64 (--configure): package libwinpr-input0.1:amd64 is not ready for configuration ErrorMessage: package libwinpr-input0.1:amd64 is not ready for configuration cannot configure (current status 'half-installed') InstallationDate: Installed on 2017-04-30 (176 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.24 SourcePackage: freerdp Title: package libwinpr-input0.1:amd64 1.1.0~git20140921.1.440916e+dfsg1-5ubuntu1 [modified: usr/lib/x86_64-linux-gnu/libwinpr-input.so.0.1.0 usr/share/doc/libwinpr-input0.1/changelog.Debian.gz] failed to install/upgrade: package libwinpr-input0.1:amd64 is not ready for configuration cannot configure (current status 'half-installed') UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: freerdp (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 freerdp in Ubuntu. https://bugs.launchpad.net/bugs/1726764 Title: package libwinpr-input0.1:amd64 1.1.0~git20140921.1.440916e+dfsg1-5ubuntu1 [modified: usr/lib/x86_64 -linux-gnu/libwinpr-input.so.0.1.0 usr/share/doc/libwinpr- input0.1/changelog.Debian.gz] failed to install/upgrade: package libwinpr-input0.1:amd64 is not ready for configuration cannot configure (current status 'half-installed') Status in freerdp package in Ubuntu: New Bug description: dpkg ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libwinpr-input0.1:amd64 1.1.0~git20140921.1.440916e+dfsg1-5ubuntu1 [modified: usr/lib/x86_64-linux-gnu/libwinpr-input.so.0.1.0 usr/share/doc/libwinpr-input0.1/changelog.Debian.gz] ProcVersionSignature: Ubuntu 4.8.0-49.52~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-49-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 Date: Tue Oct 24 14:41:29 2017 Dependencies: gcc-6-base 6.0.1-0ubuntu1 libc6 2.23-0ubuntu9 libgcc1 1:6.0.1-0ubuntu1 DuplicateSignature: package:libwinpr-input0.1:amd64:1.1.0~git20140921.1.440916e+dfsg1-5ubuntu1 [modified: usr/lib/x86_64-linux-gnu/libwinpr-input.so.0.1.0 usr/share/doc/libwinpr-input0.1/changelog.Debian.gz] Processing triggers for libc-bin (2.23-0ubuntu9) ... dpkg: error processing package libwinpr-input0.1:amd64 (--configure): package libwinpr-input0.1:amd64 is not ready for configuration ErrorMessage: package libwinpr-input0.1:amd64 is not ready for configuration cannot configure (current status 'half-installed') InstallationDate: Installed on 2017-04-30 (176 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.24 SourcePackage: freerdp Title: package libwinpr-input0.1:amd64 1.1.0~git20140921.1.440916e+dfsg1-5ubuntu1 [modified: usr/lib/x86_64-linux-gnu/libwinpr-input.so.0.1.0 usr/share/doc/libwinpr-input0.1/changelog.Debian.gz] failed to install/upgrade: package libwinpr-input0.1:amd64 is not ready for configuration cannot configure (current status 'half-installed') UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/freerdp/+bug/1726764/+subscriptions -- Mailing list: https://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 1726739] Re: package cracklib-runtime 2.9.2-5build1 failed to install/upgrade: dependency problems - leaving triggers unprocessed
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: cracklib2 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cracklib2 in Ubuntu. https://bugs.launchpad.net/bugs/1726739 Title: package cracklib-runtime 2.9.2-5build1 failed to install/upgrade: dependency problems - leaving triggers unprocessed Status in cracklib2 package in Ubuntu: Confirmed Bug description: upgrade to 17.10 ProblemType: Package DistroRelease: Ubuntu 17.10 Package: cracklib-runtime 2.9.2-5build1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 Date: Tue Oct 24 01:18:27 2017 ErrorMessage: dependency problems - leaving triggers unprocessed InstallationDate: Installed on 2017-01-14 (282 days ago) InstallationMedia: Ubuntu-MATE 16.10 "Yakkety Yak" - Release amd64 (20161012.1) Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-2ubuntu1 RelatedPackageVersions: dpkg 1.18.24ubuntu1 apt 1.5 SourcePackage: cracklib2 Title: package cracklib-runtime 2.9.2-5build1 failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: Upgraded to artful on 2017-10-24 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cracklib2/+bug/1726739/+subscriptions -- Mailing list: https://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 1717987] Re: gnome-control-center crashed with SIGABRT in mem_error()
I was sending new info with bug #1726758 -- 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/1717987 Title: gnome-control-center crashed with SIGABRT in mem_error() Status in gnome-control-center package in Ubuntu: Incomplete Bug description: crashed when adding a network printer ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: gnome-control-center 1:3.26.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10 Uname: Linux 4.12.0-13-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Mon Sep 18 18:40:07 2017 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2017-04-21 (149 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412) ProcCmdline: gnome-control-center --overview ProcEnviron: PATH=(custom, user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash Signal: 6 SourcePackage: gnome-control-center StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 __nptl_deallocate_tsd () at pthread_create.c:291 Title: gnome-control-center crashed with SIGABRT in __nptl_deallocate_tsd() UpgradeStatus: Upgraded to artful on 2017-09-15 (3 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1717987/+subscriptions -- Mailing list: https://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 1717987] Re: gnome-control-center crashed with SIGABRT in mem_error()
HP Laserjet 1200 PS -- 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/1717987 Title: gnome-control-center crashed with SIGABRT in mem_error() Status in gnome-control-center package in Ubuntu: Incomplete Bug description: crashed when adding a network printer ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: gnome-control-center 1:3.26.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10 Uname: Linux 4.12.0-13-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Mon Sep 18 18:40:07 2017 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2017-04-21 (149 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412) ProcCmdline: gnome-control-center --overview ProcEnviron: PATH=(custom, user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash Signal: 6 SourcePackage: gnome-control-center StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 __nptl_deallocate_tsd () at pthread_create.c:291 Title: gnome-control-center crashed with SIGABRT in __nptl_deallocate_tsd() UpgradeStatus: Upgraded to artful on 2017-09-15 (3 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1717987/+subscriptions -- Mailing list: https://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 1726764] Re: package libwinpr-input0.1:amd64 1.1.0~git20140921.1.440916e+dfsg1-5ubuntu1 [modified: usr/lib/x86_64-linux-gnu/libwinpr-input.so.0.1.0 usr/share/doc/libwinpr-input
** Tags removed: need-duplicate-check -- 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/1726764 Title: package libwinpr-input0.1:amd64 1.1.0~git20140921.1.440916e+dfsg1-5ubuntu1 [modified: usr/lib/x86_64 -linux-gnu/libwinpr-input.so.0.1.0 usr/share/doc/libwinpr- input0.1/changelog.Debian.gz] failed to install/upgrade: package libwinpr-input0.1:amd64 is not ready for configuration cannot configure (current status 'half-installed') Status in freerdp package in Ubuntu: New Bug description: dpkg ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libwinpr-input0.1:amd64 1.1.0~git20140921.1.440916e+dfsg1-5ubuntu1 [modified: usr/lib/x86_64-linux-gnu/libwinpr-input.so.0.1.0 usr/share/doc/libwinpr-input0.1/changelog.Debian.gz] ProcVersionSignature: Ubuntu 4.8.0-49.52~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-49-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 Date: Tue Oct 24 14:41:29 2017 Dependencies: gcc-6-base 6.0.1-0ubuntu1 libc6 2.23-0ubuntu9 libgcc1 1:6.0.1-0ubuntu1 DuplicateSignature: package:libwinpr-input0.1:amd64:1.1.0~git20140921.1.440916e+dfsg1-5ubuntu1 [modified: usr/lib/x86_64-linux-gnu/libwinpr-input.so.0.1.0 usr/share/doc/libwinpr-input0.1/changelog.Debian.gz] Processing triggers for libc-bin (2.23-0ubuntu9) ... dpkg: error processing package libwinpr-input0.1:amd64 (--configure): package libwinpr-input0.1:amd64 is not ready for configuration ErrorMessage: package libwinpr-input0.1:amd64 is not ready for configuration cannot configure (current status 'half-installed') InstallationDate: Installed on 2017-04-30 (176 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.24 SourcePackage: freerdp Title: package libwinpr-input0.1:amd64 1.1.0~git20140921.1.440916e+dfsg1-5ubuntu1 [modified: usr/lib/x86_64-linux-gnu/libwinpr-input.so.0.1.0 usr/share/doc/libwinpr-input0.1/changelog.Debian.gz] failed to install/upgrade: package libwinpr-input0.1:amd64 is not ready for configuration cannot configure (current status 'half-installed') UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/freerdp/+bug/1726764/+subscriptions -- Mailing list: https://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 1726758] Re: gnome-control-center crashed with SIGABRT in g_slice_free_chain_with_offset()
*** This bug is a duplicate of bug 1718477 *** https://bugs.launchpad.net/bugs/1718477 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1718477, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1726758/+attachment/4990477/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1726758/+attachment/4990479/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1726758/+attachment/4990482/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1726758/+attachment/4990483/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1726758/+attachment/4990484/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1726758/+attachment/4990485/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1726758/+attachment/4990486/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1718477 ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- 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/1726758 Title: gnome-control-center crashed with SIGABRT in g_slice_free_chain_with_offset() Status in gnome-control-center package in Ubuntu: New Bug description: After Upgrade to 17.10 I had problems with my print server. After purge and reinstall cups I was installing a hp printer and then the control center crashed ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: gnome-control-center 1:3.26.1-0ubuntu4 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 24 10:30:09 2017 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2016-04-27 (544 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) ProcCmdline: gnome-control-center --overview ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash Signal: 6 SourcePackage: gnome-control-center StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_slice_free_chain_with_offset () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_markup_parse_context_free () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: gnome-control-center crashed with SIGABRT in g_slice_free_chain_with_offset() UpgradeStatus: Upgraded to artful on 2017-10-22 (1 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare scanner sudo vboxsf vboxusers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1726758/+subscriptions -- Mailing list: https://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 1716160] Re: System goes to sleep with external monitor and lid closed after login
@Sebastien
Ok. I found some fault in the old patch.
suspend_on_lid_close (GsdPowerManager *manager)
{
+if (manager->priv->inhibit_lid_switch_action)
+return FALSE;
+
return !external_monitor_is_connected (manager->priv->rr_screen);
}
@@ -1242,6 +1247,26 @@ restart_inhibit_lid_switch_timer (GsdPow
}
static void
+setup_lid_closed_action (GsdPowerManager *manager)
+{
+GsdPowerActionType policy;
+
+if (up_client_get_on_battery (manager->priv->up_client)) {
+policy = g_settings_get_enum (manager->priv->settings,
"lid-close-battery-action");
+} else {
+policy = g_settings_get_enum (manager->priv->settings,
"lid-close-ac-action");
+}
+
+if (policy == GSD_POWER_ACTION_NOTHING) {
+ inhibit_lid_switch (manager);
+manager->priv->inhibit_lid_switch_action = TRUE;
+} else {
+uninhibit_lid_switch (manager);
+manager->priv->inhibit_lid_switch_action = FALSE;
+}
+}
+
The issue was:
Every-time lid state is changed, "setup_lid_closed_action" is performed
but it doesn't take account whether external monitor is connected or not
and automatically uninhibit the lid_switch & hence even if
"suspend_on_lid_close" = false; it can't work as we already performed
"uninhibit_lid_switch (manager)"
I slightly modified it:
+
+if (policy == GSD_POWER_ACTION_NOTHING) {
+ inhibit_lid_switch (manager);
+manager->priv->inhibit_lid_switch_action = TRUE;
+} else {
+ if (external_monitor_is_connected (manager->priv->rr_screen)) {
+ inhibit_lid_switch(manager);
+ manager->priv->inhibit_lid_switch_action = TRUE;
+} else {
+ uninhibit_lid_switch (manager);
+ manager->priv->inhibit_lid_switch_action = FALSE;
+}
+}
+}
I am testing this now. I will reply here soon.
--
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/1716160
Title:
System goes to sleep with external monitor and lid closed after login
Status in gdm3 package in Ubuntu:
Invalid
Status in gnome-settings-daemon package in Ubuntu:
Fix Released
Status in gnome-shell package in Ubuntu:
Invalid
Status in gdm3 source package in Artful:
Invalid
Status in gnome-settings-daemon source package in Artful:
Fix Released
Status in gnome-shell source package in Artful:
Invalid
Bug description:
Using a laptop with lid closed and an external monitor, you can boot.
Bios will show on the external monitor, as well as gdm when boot is finished.
You can then choose a user and type in your password, which is accepted.
But then, system goes to sleep (as the lid is cloesd I guess).
Going out of sleep with the power button shows the gnome shell.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1716160/+subscriptions
--
Mailing list: https://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 1726782] Re: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast()
*** This bug is a duplicate of bug 1714989 *** https://bugs.launchpad.net/bugs/1714989 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1714989, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1726782/+attachment/4990598/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1726782/+attachment/4990600/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1726782/+attachment/4990604/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1726782/+attachment/4990605/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1726782/+attachment/4990606/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1726782/+attachment/4990607/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1726782/+attachment/4990608/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1714989 gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() from st_label_set_text() from ffi_call_unix64() [dash-to-panel specific?] ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- 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/1726782 Title: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() Status in gnome-shell package in Ubuntu: New Bug description: gnome-shell[4956] general protection ip:7fd18e98ce0d sp:7ffd4b868110 error:0 in libgobject-2.0.so.0.5400.1[7fd18e957000+52000] ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.1-0ubuntu4 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia wl ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CrashCounter: 1 CurrentDesktop: GNOME Date: Tue Oct 24 11:18:42 2017 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2012-03-01 (2062 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111011) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANGUAGE=fr:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_CH.UTF-8 SHELL=/bin/zsh SegvAnalysis: Segfault happened at: 0x7ff1409adde2 : mov(%rdi),%rbp PC (0x7ff1409adde2) ok source "(%rdi)" (0x88126810d0038) not located in a known VMA region (needed readable region)! destination "%rbp" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: gnome-shell StacktraceTop: g_type_check_instance_cast () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 st_label_set_text () from /usr/lib/gnome-shell/libst-1.0.so ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6 ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6 ?? () from /usr/lib/libgjs.so.0 Title: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm admin audio cdrom dialout lp lpadmin netdev plugdev pulse pulse-access sambashare scanner video wireshark To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1726782/+subscriptions -- Mailing list: https://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 1714989] Re: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() from st_label_set_text() from ffi_call_unix64() [dash-to-panel specific?]
** Tags added: bugpattern-needed -- 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/1714989 Title: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() from st_label_set_text() from ffi_call_unix64() [dash-to-panel specific?] Status in GNOME Shell: Confirmed Status in gnome-shell package in Ubuntu: Incomplete Bug description: Saw some reports with the same title but they're all for previous versions. error report: https://errors.ubuntu.com/problem/1c95cc2653ab00054b5d1764e41d974328a5f49d ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.25.91-0ubuntu2 ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8 Uname: Linux 4.12.0-12-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Sep 4 16:52:13 2017 DisplayManager: gdm3 EcryptfsInUse: Yes ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2017-04-21 (135 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7fd97c8e7e5d : movzbl 0x16(%rax),%edx PC (0x7fd97c8e7e5d) ok source "0x16(%rax)" (0xeb1e) not located in a known VMA region (needed readable region)! destination "%edx" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-shell StacktraceTop: g_type_check_instance_cast () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 st_label_set_text () from /usr/lib/gnome-shell/libst-1.0.so ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6 ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6 ?? () from /usr/lib/libgjs.so.0 Title: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1714989/+subscriptions -- Mailing list: https://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 1722599] Re: gnome-shell crash on search specific app [gtkicontheme.c:4258:gtk_icon_info_load_icon_finish: assertion failed: (icon_info_get_pixbuf_ready (icon_info))]
Disable file search solve the issue for me ** Attachment added: "search-pref .png" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1722599/+attachment/4990622/+files/search-pref%20.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/1722599 Title: gnome-shell crash on search specific app [gtkicontheme.c:4258:gtk_icon_info_load_icon_finish: assertion failed: (icon_info_get_pixbuf_ready (icon_info))] Status in gnome-shell package in Ubuntu: Confirmed Bug description: org.gnome.Shell.desktop[1759]: Gtk:ERROR:/build/gtk+3.0-Th_a5U/gtk+3.0-3.22.24/./gtk/gtkicontheme.c:4258:gtk_icon_info_load_icon_finish: assertion failed: (icon_info_get_pixbuf_ready (icon_info)) ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4 Uname: Linux 4.13.0-15-generic x86_64 ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 10 19:20:12 2017 DisplayManager: gdm3 InstallationDate: Installed on 2017-09-25 (15 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170923) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash 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/1722599/+subscriptions -- Mailing list: https://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 256021] Re: glxinfo crashed with SIGSEGV in __libc_start_main()
** Attachment removed: "8006346FD4D033379D089FED83F31A9D.jpg" https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/256021/+attachment/4872667/+files/8006346FD4D033379D089FED83F31A9D.jpg ** Attachment removed: "E72A3127770287C810DB50E385323340.jpg" https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/256021/+attachment/4906250/+files/E72A3127770287C810DB50E385323340.jpg ** Attachment removed: "C573B18EB3EC5ED3AA6613B767D418E3.jpg" https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/256021/+attachment/4902205/+files/C573B18EB3EC5ED3AA6613B767D418E3.jpg ** Attachment removed: "F13424FA77909B54CE704E1587D00928.jpg" https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/256021/+attachment/4910380/+files/F13424FA77909B54CE704E1587D00928.jpg ** Attachment removed: "AC7BCDC2ADA4ABCD6505E44FA567A556.jpg" https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/256021/+attachment/4908128/+files/AC7BCDC2ADA4ABCD6505E44FA567A556.jpg -- 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/256021 Title: glxinfo crashed with SIGSEGV in __libc_start_main() Status in mesa package in Ubuntu: Fix Released Status in mesa source package in Jaunty: Fix Released Status in mesa source package in Karmic: Fix Released Bug description: [Impact] Fixes segmentation faults in glXGetFBConfigs() that happen frequently when the nvidia binary drivers are present on the system (even if they are not in use) by adding a null pointer check. While the SEGV seems innocuous since it only happens with glxinfo, quite a few essential programs such as compiz use glxinfo to detect GL capabilities and this causes problems. This is fixed in Karmic which as of this time has mesa 7.4.1, but the issue still stands in jaunty's 7.4. [Symptoms] Segfaults in glxinfo. glxinfo reporting Xlib: extension "GLX" missing on display. [Patch] http://launchpadlibrarian.net/28340399/mesa_7.4-0ubuntu3.2.debdiff [Test Case] In an affected system (such as one with nvidia drivers loaded) 1. Run glxinfo 2. Errors with a segfault 3. Attempt to start compiz 4. Fails to start because it can't run glxinfo [Regression Potential] Essentially none. It simply adds a null pointer check right before dereferencing it. This fix has been tested in Karmic as well as upstream for some time, and was included in the 7.4.1 bugfix release. UPDATE:Oct 8 2008. installed daily updates ( 2.6.27-6-generic ) and still getting this same glxinfo error on boot I was running PlayOnLinux and tried to install 3d acceleration from there when glxinfo crashed. Description: Ubuntu intrepid (development branch) Release: 8.10 mesa version : 7.1~rc3-1ubuntu2 (intrepid) ProblemType: Crash Architecture: i386 DistroRelease: Ubuntu 8.10 ExecutablePath: /usr/bin/glxinfo NonfreeKernelModules: nvidia Package: mesa-utils 7.1~rc3-1ubuntu2 ProcAttrCurrent: unconfined ProcCmdline: glxinfo ProcEnviron: SHELL=/bin/bash PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games LANG=en_US.UTF-8 Signal: 11 SourcePackage: mesa Stacktrace: #0 0x0804ad66 in ?? () #1 0xb7d66685 in __libc_start_main () from /lib/tls/i686/cmov/libc.so.6 #2 0x08048e81 in ?? () StacktraceTop: ?? () __libc_start_main () from /lib/tls/i686/cmov/libc.so.6 ?? () ThreadStacktrace: . Thread 1 (process 7142): #0 0x0804ad66 in ?? () #1 0xb7d66685 in __libc_start_main () from /lib/tls/i686/cmov/libc.so.6 #2 0x08048e81 in ?? () Title: glxinfo crashed with SIGSEGV in __libc_start_main() Uname: Linux 2.6.26-5-generic i686 UserGroups: adm admin cdrom dialout fuse lpadmin plugdev sambashare To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/256021/+subscriptions -- Mailing list: https://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 51043] Re: ListView - Context-menu options missing when pointer is above files/folders
** Attachment removed: "B3F0BBFD720296CB5D8FA277B76A31B7.jpg" https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/51043/+attachment/4896970/+files/B3F0BBFD720296CB5D8FA277B76A31B7.jpg ** Attachment removed: "AAAFE1EB48FFB63E.jpg" https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/51043/+attachment/4932231/+files/AAAFE1EB48FFB63E.jpg ** Attachment removed: "F9ABD09DE01DB163.jpg" https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/51043/+attachment/4970809/+files/F9ABD09DE01DB163.jpg -- 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/51043 Title: ListView - Context-menu options missing when pointer is above files/folders Status in One Hundred Papercuts: Fix Released Status in Nautilus: Fix Released Status in nautilus package in Ubuntu: Fix Released Bug description: What I did: - Nautilus is configured to show listview, and the directory-tree on the left ( just checked, symbolview has the same issue ) - right-click on a file/folder and clicking on copy - change to the folder where the file/foldershould be copied to - rightclick anywhere in the listview of the contents of that folder What happened: - When rightclicking on a folder, there is the option to insert into that folder ( which is nice ) and cut and copy - no paste - When rightclicking on a file the only options are cut and copy - no paste - When actually rightclicking on the actual folder from the tree-view, paste into that folder exists, but is inactive (!!!) - so no workaround available What I expected: a past option that pasts the "files/folders" I've "copied" before into the folder at whichs contents I'm looking. and a paste into that folder option in the treeview What I found out : when there are very few files/folders in a folder, and the list is shorter than the nautilus window could show - the whitespace below the list has this option. This should simply be added to the files and folders. P.S: please do not remove paste into that folder - its nice actually, but not all I expected... To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/51043/+subscriptions -- Mailing list: https://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 1726797] [NEW] Segmentation fault on annotation and "Open Copy"
Public bug reported: Evince version 3.18.2 crashes (Segmentation fault (core dumped)) on Ubuntu 16.04.3 LTS on the following sequence of actions: 1. Open any pdf, for example http://gahp.net/wp-content/uploads/2017/09/sample.pdf. 2. Add any annotation, for example highlight the document title. 3. Click File->Open a copy. ** 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/1726797 Title: Segmentation fault on annotation and "Open Copy" Status in evince package in Ubuntu: New Bug description: Evince version 3.18.2 crashes (Segmentation fault (core dumped)) on Ubuntu 16.04.3 LTS on the following sequence of actions: 1. Open any pdf, for example http://gahp.net/wp-content/uploads/2017/09/sample.pdf. 2. Add any annotation, for example highlight the document title. 3. Click File->Open a copy. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1726797/+subscriptions -- Mailing list: https://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 1705369] Re: Ubuntu 17.10 boots to black screen when using Nvidia drivers (on a desktop with an Intel GPU)
The solution that worked in my case: 4.13.0-16-lowlatency Nvidia GT 620 gdm3 with Wayland sudo apt purge nvidia* sudo apt install linux-headers-$(uname -r) sudo apt install nvidia-384 -- 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/1705369 Title: Ubuntu 17.10 boots to black screen when using Nvidia drivers (on a desktop with an Intel GPU) Status in gdm3 package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Invalid Status in nvidia-graphics-drivers-375 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-384 package in Ubuntu: Confirmed Bug description: Ubuntu 17.10 boots to black screen when using Nvidia drivers (on a desktop with an Intel GPU) WORKAROUNDS: * Disable integrated graphics/GPU in your BIOS. * Add 'nomodeset' to your kernel command line. ORIGINAL DESCRIPTION: This bug is very similar to https://bugs.launchpad.net/ubuntu-gnome/+bug/1559576 which is closed. I have been asked to open a new bug report. The issue is on Ubuntu 17.10 with gdm3 fully updated as of July 20, 2017. I upgraded to 17.10 from a freshly installed Ubuntu 17.04. - Lightdm works - Nouveau driver works - Nvidia driver 375.66 (proprietary) does not work - Nvidia driver 384.47 (open source) does not work (from https://launchpad.net/~graphics-drivers/+archive/ubuntu/ppa) - Nvidia drivers work with Ubuntu Gnome 17.04 I am using Nvidia GTX 1080 and Intel i7-4790K lsb_release -rd: Description: Ubuntu Artful Aardvark (development branch) Release: 17.10 apt-cache policy gnome-shell: gnome-shell: Installed: 3.24.2-0ubuntu7 Candidate: 3.24.2-0ubuntu7 Version table: *** 3.24.2-0ubuntu7 500 500 http://sa.archive.ubuntu.com/ubuntu artful/main amd64 Packages 100 /var/lib/dpkg/status uname -s -r -v -p -i -o: Linux 4.11.0-11-generic #16-Ubuntu SMP Wed Jul 12 20:40:19 UTC 2017 x86_64 x86_64 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1705369/+subscriptions -- Mailing list: https://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 1725190] Re: Please update modemmanager in xenial to the 1.6 series
verified the packages in #1 on BRM5-DVT1-C2RX with WWAN DW5811 and DW5816. Both of these 2 WWAN cards work well. BIOS: 0.5.1 IMAGE: X82 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1725190 Title: Please update modemmanager in xenial to the 1.6 series Status in OEM Priority Project: Confirmed Status in modemmanager package in Ubuntu: In Progress Bug description: We would like to upgrade xenial to 1.6 series so it supports the same modems as the modem-manager snap, specifically some new Sierra modems (HL8548 and others from HL series, popular in IoT devices). These are the packages that would need to be updated: libmbim: 1.12.2-2ubuntu1 in xenial, 1.14.0 in snap libqmi: 1.12.6-1 in xenial, 1.16.2 in snap modemmanager: 1.4.12-1ubuntu1 in xenial, 1.6.2 in snap This is also related to bug #1693756 which includes a subset of patches of what would be updated. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1725190/+subscriptions -- Mailing list: https://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 1726795] Re: epiphany-search-provider crashed with SIGSEGV in wl_list_insert_list()
*** This bug is a duplicate of bug 1716208 *** https://bugs.launchpad.net/bugs/1716208 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1716208, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1726795/+attachment/4990701/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1726795/+attachment/4990703/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1726795/+attachment/4990707/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1726795/+attachment/4990708/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1726795/+attachment/4990709/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1726795/+attachment/4990710/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1726795/+attachment/4990711/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1716208 epiphany-search-provider crashed with SIGSEGV in wl_list_insert_list() ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to epiphany-browser in Ubuntu. https://bugs.launchpad.net/bugs/1726795 Title: epiphany-search-provider crashed with SIGSEGV in wl_list_insert_list() Status in epiphany-browser package in Ubuntu: New Bug description: This happened while switching from Ubuntu Wayland to Ubuntu Xorg (like my previous, bug report). It looks like that applications are not terminated correctly or in the correct order, which leads to issues when communicating with Wayland. This indicates a missing check whether Wayland is available. ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: epiphany-browser 3.26.1-1ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 24 10:50:50 2017 ExecutablePath: /usr/lib/epiphany-search-provider InstallationDate: Installed on 2016-05-31 (510 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) ProcCmdline: /usr/lib/epiphany-search-provider SegvAnalysis: Segfault happened at: 0x7ff0d64bfe30 : mov %rbp,(%rax) PC (0x7ff0d64bfe30) ok source "%rbp" ok destination "(%rax)" (0x0005) not located in a known VMA region (needed writable region)! SegvReason: writing NULL VMA Signal: 11 SourcePackage: epiphany-browser StacktraceTop: wl_list_insert_list () at /usr/lib/x86_64-linux-gnu/libwayland-server.so.0 () at /usr/lib/x86_64-linux-gnu/libwayland-server.so.0 wl_display_destroy () at /usr/lib/x86_64-linux-gnu/libwayland-server.so.0 () at /usr/lib/x86_64-linux-gnu/libwebkit2gtk-4.0.so.37 () at /usr/lib/x86_64-linux-gnu/libwebkit2gtk-4.0.so.37 Title: epiphany-search-provider crashed with SIGSEGV in wl_list_insert_list() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/epiphany-browser/+bug/1726795/+subscriptions -- Mailing list: https://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 1717987] Re: gnome-control-center crashed with SIGABRT in mem_error()
In my case I finally added the printer but with cups web interface not with gnome-control-center -- 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/1717987 Title: gnome-control-center crashed with SIGABRT in mem_error() Status in gnome-control-center package in Ubuntu: Incomplete Bug description: crashed when adding a network printer ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: gnome-control-center 1:3.26.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10 Uname: Linux 4.12.0-13-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Mon Sep 18 18:40:07 2017 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2017-04-21 (149 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412) ProcCmdline: gnome-control-center --overview ProcEnviron: PATH=(custom, user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash Signal: 6 SourcePackage: gnome-control-center StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 __nptl_deallocate_tsd () at pthread_create.c:291 Title: gnome-control-center crashed with SIGABRT in __nptl_deallocate_tsd() UpgradeStatus: Upgraded to artful on 2017-09-15 (3 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1717987/+subscriptions -- Mailing list: https://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 1726799] Re: Xorg crashed with SIGABRT in OsAbort()
*** This bug is a duplicate of bug 1673649 *** https://bugs.launchpad.net/bugs/1673649 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1673649, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1726799/+attachment/4990722/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1726799/+attachment/4990725/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1726799/+attachment/4990738/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1726799/+attachment/4990740/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1726799/+attachment/4990741/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1726799/+attachment/4990742/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1726799/+attachment/4990743/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1673649 Xorg crashed with SIGABRT in OsAbort() ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- 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/1726799 Title: Xorg crashed with SIGABRT in OsAbort() Status in xorg-server package in Ubuntu: New Bug description: Update manager crash after starting update. ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: xserver-xorg-core 2:1.19.5-0ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CompositorRunning: None Date: Tue Oct 24 12:14:42 2017 DistUpgraded: 2017-10-24 09:35:16,014 DEBUG got a conffile-prompt from dpkg for file: '/etc/NetworkManager/NetworkManager.conf' DistroCodename: artful DistroVariant: ubuntu ExecutablePath: /usr/lib/xorg/Xorg ExtraDebuggingInterest: No GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Dell 4th Gen Core Processor Integrated Graphics Controller [1028:05be] Advanced Micro Devices, Inc. [AMD/ATI] Mars XTX [Radeon HD 8790M] [1002:6606] (rev ff) (prog-if ff) InstallationDate: Installed on 2014-06-06 (1236 days ago) InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64 (20130820.2) MachineType: Dell Inc. Latitude E6540 ProcCmdline: /usr/lib/xorg/Xorg -core :1 -seat seat0 -auth /var/run/lightdm/root/:1 -nolisten tcp vt8 -novtswitch ProcEnviron: PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic root=/dev/mapper/hostname--vg-root ro quiet splash vt.handoff=7 Signal: 6 SourcePackage: xorg-server StacktraceTop: OsAbort () ?? () FatalError () xf86PostProbe () InitOutput () Title: Xorg crashed with SIGABRT in OsAbort() UpgradeStatus: Upgraded to artful on 2017-10-24 (0 days ago) UserGroups: XorgConf: Section "Device" Identifier "Default Card 0" BusID "PCI:0@0:2:0" EndSection dmi.bios.date: 02/18/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 0725FP dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA08:bd02/18/2014:svnDellInc.:pnLatitudeE6540:pvr01:rvnDellInc.:rn0725FP:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6540 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. 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.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 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-xo
[Desktop-packages] [Bug 1666681] Re: Restore interactive_search.patch (type-ahead search)
** Summary changed: - Drop interactive_search.patch (type-ahead search) + Restore interactive_search.patch (type-ahead search) -- 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/181 Title: Restore interactive_search.patch (type-ahead search) Status in nautilus package in Ubuntu: Confirmed Bug description: Nautilus dropped the popular type-ahead search feature years ago. Ubuntu has been carrying a patch to revert that change. See bug 1164016 for the original LP bug and patch proposal. Nautilus is now under very active development. During the 3.22 cycle, that patch needed to be rebased. I tried to do it and what I came up with caused a crash (it didn't really crash for me, but ricotz and some others experienced it) and the first letter typed activated type- ahead search but the first letter was dropped. In other words, you would need to type "ddow" to activate the Downloads folder instead of just "dow" like in previous releases. (LP: #1635988) I did that rebase in October 2016 and no one has stepped up then to improve the patch. The Nautilus maintainer csoriano has said that the slots and views changed significantly during 3.22 and will likely be refactored more in the future. If there's no one available to maintain the patch, unfortunately, we'll eventually have to drop the patch to not be stuck on an ancient version of Nautilus. I am proposing that we do this at the start of the 17.10 development cycle. This gives 6 months for a developer to step up and try to fix the patch and 12 months before 18.04 LTS. Other Items === - For better performance with the built-in search, we need to reconsider avoiding tracker in Unity (LP: #176) - There is an option in Preferences for users to disable searching in subfolders. I don't think we want to do that by default but maybe it can help some people. The current Nautilus 3.24 packaging is in the GNOME3 Staging PPA with this patch now disabled. https://launchpad.net/~gnome3-team/+archive/ubuntu/gnome3-staging/+packages?field.series_filter=zesty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/181/+subscriptions -- Mailing list: https://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 1705369] Re: Ubuntu 17.10 boots to black screen when using Nvidia drivers (on a desktop with an Intel GPU)
That did not work for me. I had to uninstall gdm3 completely in order to be able to even get a login screen up. -- 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/1705369 Title: Ubuntu 17.10 boots to black screen when using Nvidia drivers (on a desktop with an Intel GPU) Status in gdm3 package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Invalid Status in nvidia-graphics-drivers-375 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-384 package in Ubuntu: Confirmed Bug description: Ubuntu 17.10 boots to black screen when using Nvidia drivers (on a desktop with an Intel GPU) WORKAROUNDS: * Disable integrated graphics/GPU in your BIOS. * Add 'nomodeset' to your kernel command line. ORIGINAL DESCRIPTION: This bug is very similar to https://bugs.launchpad.net/ubuntu-gnome/+bug/1559576 which is closed. I have been asked to open a new bug report. The issue is on Ubuntu 17.10 with gdm3 fully updated as of July 20, 2017. I upgraded to 17.10 from a freshly installed Ubuntu 17.04. - Lightdm works - Nouveau driver works - Nvidia driver 375.66 (proprietary) does not work - Nvidia driver 384.47 (open source) does not work (from https://launchpad.net/~graphics-drivers/+archive/ubuntu/ppa) - Nvidia drivers work with Ubuntu Gnome 17.04 I am using Nvidia GTX 1080 and Intel i7-4790K lsb_release -rd: Description: Ubuntu Artful Aardvark (development branch) Release: 17.10 apt-cache policy gnome-shell: gnome-shell: Installed: 3.24.2-0ubuntu7 Candidate: 3.24.2-0ubuntu7 Version table: *** 3.24.2-0ubuntu7 500 500 http://sa.archive.ubuntu.com/ubuntu artful/main amd64 Packages 100 /var/lib/dpkg/status uname -s -r -v -p -i -o: Linux 4.11.0-11-generic #16-Ubuntu SMP Wed Jul 12 20:40:19 UTC 2017 x86_64 x86_64 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1705369/+subscriptions -- Mailing list: https://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 1726806] [NEW] package dblatex 0.3.7-1 failed to install/upgrade: le sous-processus script post-removal installé a retourné une erreur de sortie d'état 127
Public bug reported: Upgrade from 16.O4 LTS to 17.04 half-failed for LaTeX ProblemType: Package DistroRelease: Ubuntu 16.04 Package: dblatex 0.3.7-1 ProcVersionSignature: Ubuntu 4.10.0-37.41~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-37-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 Date: Tue Oct 24 12:57:48 2017 ErrorMessage: le sous-processus script post-removal installé a retourné une erreur de sortie d'état 127 InstallationDate: Installed on 2017-07-26 (89 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.2.24 SourcePackage: dblatex Title: package dblatex 0.3.7-1 failed to install/upgrade: le sous-processus script post-removal installé a retourné une erreur de sortie d'état 127 UpgradeStatus: Upgraded to xenial on 2017-10-24 (0 days ago) ** Affects: dblatex (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package third-party-packages xenial -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to dblatex in Ubuntu. https://bugs.launchpad.net/bugs/1726806 Title: package dblatex 0.3.7-1 failed to install/upgrade: le sous-processus script post-removal installé a retourné une erreur de sortie d'état 127 Status in dblatex package in Ubuntu: New Bug description: Upgrade from 16.O4 LTS to 17.04 half-failed for LaTeX ProblemType: Package DistroRelease: Ubuntu 16.04 Package: dblatex 0.3.7-1 ProcVersionSignature: Ubuntu 4.10.0-37.41~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-37-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 Date: Tue Oct 24 12:57:48 2017 ErrorMessage: le sous-processus script post-removal installé a retourné une erreur de sortie d'état 127 InstallationDate: Installed on 2017-07-26 (89 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.2.24 SourcePackage: dblatex Title: package dblatex 0.3.7-1 failed to install/upgrade: le sous-processus script post-removal installé a retourné une erreur de sortie d'état 127 UpgradeStatus: Upgraded to xenial on 2017-10-24 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dblatex/+bug/1726806/+subscriptions -- Mailing list: https://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 1726738] Re: package cracklib-runtime 2.9.2-5build1 failed to install/upgrade: dependency problems - leaving triggers unprocessed
*** This bug is a duplicate of bug 1681231 *** https://bugs.launchpad.net/bugs/1681231 ** This bug is no longer a duplicate of bug 1726739 package cracklib-runtime 2.9.2-5build1 failed to install/upgrade: dependency problems - leaving triggers unprocessed ** This bug has been marked a duplicate of bug 1681231 package cracklib-runtime 2.9.2-3 failed to install/upgrade: dependency problems - leaving triggers unprocessed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cracklib2 in Ubuntu. https://bugs.launchpad.net/bugs/1726738 Title: package cracklib-runtime 2.9.2-5build1 failed to install/upgrade: dependency problems - leaving triggers unprocessed Status in cracklib2 package in Ubuntu: New Bug description: upgrade to 17.10 ProblemType: Package DistroRelease: Ubuntu 17.10 Package: cracklib-runtime 2.9.2-5build1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 Date: Tue Oct 24 01:18:27 2017 ErrorMessage: dependency problems - leaving triggers unprocessed InstallationDate: Installed on 2017-01-14 (282 days ago) InstallationMedia: Ubuntu-MATE 16.10 "Yakkety Yak" - Release amd64 (20161012.1) Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-2ubuntu1 RelatedPackageVersions: dpkg 1.18.24ubuntu1 apt 1.5 SourcePackage: cracklib2 Title: package cracklib-runtime 2.9.2-5build1 failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: Upgraded to artful on 2017-10-24 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cracklib2/+bug/1726738/+subscriptions -- Mailing list: https://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 1711241] Re: Unity support patch doesn't build with nautilus 3.25.90
Hi Jeremy, Sorry for the delay. I have modified the headerbar patch for nautilus https://git.launchpad.net/~khurshid-alam/nautilus/+git/unity- test/tree/debian/patches/0002-Only-use-a-header-bar-in-GNOME-shell.patch For me, It is working well in Unity and Ubuntu (both xorg and wayland) sessions and nautilus doesn't crash. Please test and if it works for you please re-enable the patch. Screencast: https://vimeo.com/239618810 ** Patch added: "patch" https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1711241/+attachment/4990798/+files/0002-Only-use-a-header-bar-in-GNOME-shell.patch -- 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/1711241 Title: Unity support patch doesn't build with nautilus 3.25.90 Status in nautilus package in Ubuntu: Fix Released Bug description: I have prepared nautilus 3.25.90 in the GNOME3 Staging PPA for Ubuntu 17.10 "artful". The 12_unity_launcher_support.patch has a problem that fails the build and I don't know how to fix it so I disabled the patch for now. Nautilus 3.25 introduces meson support and drops autotools support so that's one factor when I updated the patch. But when I disable the patch, nautilus crashes on start in Unity. Build log attached. Build Log Excerpt == [164/222] cc -Isrc/nautilus@sta -Isrc -Isubprojects/libgd/libgd -I../src -I. -I../ -Isubprojects/libgd -I../subprojects/libgd -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/at-spi2-atk/2.0 -I/usr/include/at-spi-2.0 -I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -I/usr/include/gtk-3.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/mirclient -I/usr/include/mircore -I/usr/include/mircookie -I/usr/include/harfbuzz -I/usr/include/pango-1.0 -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng16 -I/usr/include/gnome-autoar-0 -I/usr/include/libxml2 -I/usr/include/zeitgeist-2.0 -I/usr/include/gsettings-desktop-schemas -I/usr/include/gail-3.0 -I/usr/include/gnome-desktop-3.0 -I/usr/include/tracker-2.0 -I/usr/include/tracker-2.0/libtracker-sparql -I/usr/include/libexif -I/usr/include/unity/unity -I/usr/include/dee-1.0 -I/usr/include/libdbusmenu-glib-0.4 -I/usr/include/exempi-2.0 -fdiagnostics-color=always -pipe -D_FILE_OFFSET_BITS=64 -Wno-deprecated-declarations -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -pthread -DLIBGD_GTK_HACKS=1 -DLIBGD__VIEW_COMMON=1 -DLIBGD_MAIN_ICON_VIEW=1 -DLIBGD_MAIN_LIST_VIEW=1 -DLIBGD_MAIN_VIEW=1 -DLIBGD_TAGGED_ENTRY=1 -MMD -MQ 'src/nautilus@sta/unity-quicklist-handler.c.o' -MF 'src/nautilus@sta/unity-quicklist-handler.c.o.d' -o 'src/nautilus@sta/unity-quicklist-handler.c.o' -c ../src/unity-quicklist-handler.c FAILED: src/nautilus@sta/unity-quicklist-handler.c.o cc -Isrc/nautilus@sta -Isrc -Isubprojects/libgd/libgd -I../src -I. -I../ -Isubprojects/libgd -I../subprojects/libgd -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/at-spi2-atk/2.0 -I/usr/include/at-spi-2.0 -I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -I/usr/include/gtk-3.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/mirclient -I/usr/include/mircore -I/usr/include/mircookie -I/usr/include/harfbuzz -I/usr/include/pango-1.0 -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng16 -I/usr/include/gnome-autoar-0 -I/usr/include/libxml2 -I/usr/include/zeitgeist-2.0 -I/usr/include/gsettings-desktop-schemas -I/usr/include/gail-3.0 -I/usr/include/gnome-desktop-3.0 -I/usr/include/tracker-2.0 -I/usr/include/tracker-2.0/libtracker-sparql -I/usr/include/libexif -I/usr/include/unity/unity -I/usr/include/dee-1.0 -I/usr/include/libdbusmenu-glib-0.4 -I/usr/include/exempi-2.0 -fdiagnostics-color=always -pipe -D_FILE_OFFSET_BITS=64 -Wno-deprecated-declarations -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -pthread -DLIBGD_GTK_HACKS=1 -DLIBGD__VIEW_COMMON=1 -DLIBGD_MAIN_ICON_VIEW=1 -DLIBGD_MAIN_LIST_VIEW=1 -DLIBGD_MAIN_VIEW=1 -DLIBGD_TAGGED_ENTRY=1 -MMD -MQ 'src/nautilus@sta/unity-quicklist-handler.c.o' -MF 'src/nautilus@sta/unity-quicklist-handler.c.o.d' -o 'src/nautilus@sta/unity-quicklist-handler.c.o' -c ../src/unity-quicklist-handler.c ../src/unity-quicklist-handler.c: In function ‘unity_quicklist_handler_get_singleton’: ../src/unity-quicklist-handler.c:154:9: error: expected declaration or statement at end of input unity_quicklist_handler_singleton = unity_quicklist_handler_new (); ^ ../src/unity-quicklist-handle
[Desktop-packages] [Bug 1726739] Re: package cracklib-runtime 2.9.2-5build1 failed to install/upgrade: dependency problems - leaving triggers unprocessed
*** This bug is a duplicate of bug 1681231 *** https://bugs.launchpad.net/bugs/1681231 ** This bug has been marked a duplicate of bug 1681231 package cracklib-runtime 2.9.2-3 failed to install/upgrade: dependency problems - leaving triggers unprocessed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cracklib2 in Ubuntu. https://bugs.launchpad.net/bugs/1726739 Title: package cracklib-runtime 2.9.2-5build1 failed to install/upgrade: dependency problems - leaving triggers unprocessed Status in cracklib2 package in Ubuntu: Confirmed Bug description: upgrade to 17.10 ProblemType: Package DistroRelease: Ubuntu 17.10 Package: cracklib-runtime 2.9.2-5build1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 Date: Tue Oct 24 01:18:27 2017 ErrorMessage: dependency problems - leaving triggers unprocessed InstallationDate: Installed on 2017-01-14 (282 days ago) InstallationMedia: Ubuntu-MATE 16.10 "Yakkety Yak" - Release amd64 (20161012.1) Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-2ubuntu1 RelatedPackageVersions: dpkg 1.18.24ubuntu1 apt 1.5 SourcePackage: cracklib2 Title: package cracklib-runtime 2.9.2-5build1 failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: Upgraded to artful on 2017-10-24 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cracklib2/+bug/1726739/+subscriptions -- Mailing list: https://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 1726805] Re: mouse stutters since update to 17.10
*** This bug is a duplicate of bug 1723342 *** https://bugs.launchpad.net/bugs/1723342 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1723342, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1726805/+attachment/4990786/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1726805/+attachment/4990788/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1726805/+attachment/4990792/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1726805/+attachment/4990793/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1726805/+attachment/4990794/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1726805/+attachment/4990795/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1726805/+attachment/4990796/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1723342 ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- 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/1726805 Title: mouse stutters since update to 17.10 Status in nautilus package in Ubuntu: New Bug description: the mouse is not so nice since the update. i also would love to have more options for mouse in the settings (third mousebutton activate/deactivate), speed of the scrollwheel ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: nautilus 1:3.26.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 24 12:01:02 2017 ExecutablePath: /usr/bin/nautilus-desktop InstallationDate: Installed on 2017-06-21 (125 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) ProcCmdline: nautilus-desktop ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash Signal: 5 SourcePackage: nautilus StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6 _XEventsQueued () from /usr/lib/x86_64-linux-gnu/libX11.so.6 XPending () from /usr/lib/x86_64-linux-gnu/libX11.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 Title: nautilus-desktop crashed with signal 5 in _XEventsQueued() UpgradeStatus: Upgraded to artful on 2017-10-23 (1 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1726805/+subscriptions -- Mailing list: https://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 1725017] Re: file-roller crashed with SIGSEGV in g_action_map_lookup_action()
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: file-roller (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to file-roller in Ubuntu. https://bugs.launchpad.net/bugs/1725017 Title: file-roller crashed with SIGSEGV in g_action_map_lookup_action() Status in file-roller package in Ubuntu: Confirmed Bug description: Description: Ubuntu 17.10 Release: 17.10 file-roller: Installed: 3.26.1-0ubuntu1 Candidate: 3.26.1-0ubuntu1 Version table: *** 3.26.1-0ubuntu1 500 500 http://ca.archive.ubuntu.com/ubuntu artful/main amd64 Packages 100 /var/lib/dpkg/status Don't know how this happned. ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: file-roller 3.26.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Oct 19 18:23:52 2017 ExecutablePath: /usr/bin/file-roller InstallationDate: Installed on 2017-10-19 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcCmdline: file-roller /home/username/Downloads/discord-0.0.2.tar.gz SegvAnalysis: Segfault happened at: 0x7f4a0e78271c : mov0x10(%rax),%rax PC (0x7f4a0e78271c) ok source "0x10(%rax)" (0x0010) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: file-roller StacktraceTop: g_action_map_lookup_action () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 ?? () g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: file-roller crashed with SIGSEGV in g_action_map_lookup_action() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/1725017/+subscriptions -- Mailing list: https://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 1725055] Re: pptp vpn cannot be easily connected in gnome network manager and gnome control center
** Changed in: gnome-control-center Status: Unknown => Confirmed ** Changed in: gnome-control-center Importance: Unknown => High -- 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/1725055 Title: pptp vpn cannot be easily connected in gnome network manager and gnome control center Status in gnome-control-center: Confirmed Status in gnome-control-center package in Ubuntu: Triaged Status in network-manager package in Ubuntu: New Status in network-manager-applet package in Ubuntu: New Bug description: I tried to reactivate a VPN (for PPTP) several times again and again using PPTP, and it is just that it just suddenly turns off every time I try to turn on. There is no process ongoing for PPTP. I tried to use an OpenVPN plugin for VPN, it works depending on the VPN server. I depend on VPN a lot especially on FreeVPN PPTP. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-control-center 1:3.26.1-0ubuntu4 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Oct 20 07:48:21 2017 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2017-10-19 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: LANGUAGE=en_PH:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_PH.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1725055/+subscriptions -- Mailing list: https://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 1726509] Re: screen rotates randomly on ubuntu 17.10
*** This bug is a duplicate of bug 1726160 *** https://bugs.launchpad.net/bugs/1726160 After the reboot screen is now in landscape orientation (as it suppose to be). I have it locked using widget. -- 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/1726509 Title: screen rotates randomly on ubuntu 17.10 Status in gnome-shell package in Ubuntu: Incomplete Bug description: I recently upgraded from Ubuntu 17.04 to 17.10. Everything went well, but when I boot up the system, my screen rotation was set to left. Then I tried using xandr to rotate my screen, but my every effort failed. Can anybody help me on the same? I have an HP Pavilion 14 inch laptop. Thank you. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1726509/+subscriptions -- Mailing list: https://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 1726826] [NEW] screen 256 colour TERM setting breaks logging into older hosts
Public bug reported: As of 16.04, the screen program started using a 256 colour setting. The problem is that this setting is relatively new and has not had a chance to propagate to older hosts, including something as new as the previous 15.x release. For example: -- paul@1604-host:~$ echo $TERM screen.xterm-256color paul@y1604-host:~$ ssh oldermachine Welcome to Ubuntu 15.04 (GNU/Linux 3.19.0-84-generic x86_64) * Documentation: https://help.ubuntu.com/ 0 packages can be updated. 0 updates are security updates. Last login: Mon Oct 23 15:52:17 2017 from yow-pgortmak-d1.wrs.com paul@oldermachine:~$ echo foo > foo paul@yoldermachine:~$ less foo WARNING: terminal is not fully functional foo (press RETURN) paul@oldermachine:~$ export TERM=screen paul@yoldermachine:~$ less foo foo paul@oldermachine:~$ cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=15.04 DISTRIB_CODENAME=vivid DISTRIB_DESCRIPTION="Ubuntu 15.04" paul@oldermachine:~$ -- This makes it extremely annoying to use 16.04 in order to interact with any other linux/unix machines. The 256 color term type needs at least a couple years roll-out time before it becomes the default. Otherwise the older machines won't have it and they will complain and default to ancient crippled defaults and nag you each time they have to do so. ** Affects: gnome-terminal (Ubuntu) Importance: Undecided Status: New ** Affects: screen (Ubuntu) Importance: Undecided Status: New ** Tags: 256 color screen ** Also affects: screen (Ubuntu) Importance: Undecided Status: New -- 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/1726826 Title: screen 256 colour TERM setting breaks logging into older hosts Status in gnome-terminal package in Ubuntu: New Status in screen package in Ubuntu: New Bug description: As of 16.04, the screen program started using a 256 colour setting. The problem is that this setting is relatively new and has not had a chance to propagate to older hosts, including something as new as the previous 15.x release. For example: -- paul@1604-host:~$ echo $TERM screen.xterm-256color paul@y1604-host:~$ ssh oldermachine Welcome to Ubuntu 15.04 (GNU/Linux 3.19.0-84-generic x86_64) * Documentation: https://help.ubuntu.com/ 0 packages can be updated. 0 updates are security updates. Last login: Mon Oct 23 15:52:17 2017 from yow-pgortmak-d1.wrs.com paul@oldermachine:~$ echo foo > foo paul@yoldermachine:~$ less foo WARNING: terminal is not fully functional foo (press RETURN) paul@oldermachine:~$ export TERM=screen paul@yoldermachine:~$ less foo foo paul@oldermachine:~$ cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=15.04 DISTRIB_CODENAME=vivid DISTRIB_DESCRIPTION="Ubuntu 15.04" paul@oldermachine:~$ -- This makes it extremely annoying to use 16.04 in order to interact with any other linux/unix machines. The 256 color term type needs at least a couple years roll-out time before it becomes the default. Otherwise the older machines won't have it and they will complain and default to ancient crippled defaults and nag you each time they have to do so. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1726826/+subscriptions -- Mailing list: https://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 1726815] Re: gnome-shell crashed with signal 5 in g_malloc0()
*** This bug is a duplicate of bug 1726780 *** https://bugs.launchpad.net/bugs/1726780 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1726780, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1726815/+attachment/4990854/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1726815/+attachment/4990856/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1726815/+attachment/4990860/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1726815/+attachment/4990861/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1726815/+attachment/4990862/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1726815/+attachment/4990863/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1726815/+attachment/4990864/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1726780 ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- 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/1726815 Title: gnome-shell crashed with signal 5 in g_malloc0() Status in gnome-shell package in Ubuntu: New Bug description: Attempting to open an application (Visual Studio Code) from the Activities overview. Shell hung for a minute, then restarted, the application opened successfully after this delay. ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.1-0ubuntu4 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Oct 24 07:17:09 2017 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2017-10-20 (3 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Signal: 5 SourcePackage: gnome-shell StacktraceTop: g_malloc0 () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /usr/lib/gnome-shell/libst-1.0.so _st_create_shadow_pipeline () from /usr/lib/gnome-shell/libst-1.0.so _st_create_shadow_pipeline_from_actor () from /usr/lib/gnome-shell/libst-1.0.so ?? () from /usr/lib/gnome-shell/libst-1.0.so Title: gnome-shell crashed with signal 5 in g_malloc0() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1726815/+subscriptions -- Mailing list: https://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 1726831] Re: gnome-calendar crashed with SIGSEGV in g_type_check_instance_cast()
*** This bug is a duplicate of bug 1725244 *** https://bugs.launchpad.net/bugs/1725244 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1725244, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1726831/+attachment/4990930/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1726831/+attachment/4990932/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1726831/+attachment/4990935/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1726831/+attachment/4990936/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1726831/+attachment/4990937/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1726831/+attachment/4990938/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1726831/+attachment/4990939/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1725244 ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-calendar in Ubuntu. https://bugs.launchpad.net/bugs/1726831 Title: gnome-calendar crashed with SIGSEGV in g_type_check_instance_cast() Status in gnome-calendar package in Ubuntu: New Bug description: Calendar was running in the background ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: gnome-calendar 3.26.2-1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Oct 24 13:19:03 2017 ExecutablePath: /usr/bin/gnome-calendar InstallationDate: Installed on 2017-03-30 (207 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) ProcCmdline: /usr/bin/gnome-calendar --gapplication-service ProcEnviron: XDG_RUNTIME_DIR= SHELL=/bin/bash LANGUAGE=en_US:en PATH=(custom, user) LANG=en_US.UTF-8 SegvAnalysis: Segfault happened at: 0x7fa882673de2 : mov(%rdi),%rbp PC (0x7fa882673de2) ok source "(%rdi)" (0x00be) not located in a known VMA region (needed readable region)! destination "%rbp" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-calendar StacktraceTop: g_type_check_instance_cast () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 () ffi_call_unix64 () at /usr/lib/x86_64-linux-gnu/libffi.so.6 ffi_call () at /usr/lib/x86_64-linux-gnu/libffi.so.6 g_cclosure_marshal_generic () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: gnome-calendar crashed with SIGSEGV in g_type_check_instance_cast() UpgradeStatus: Upgraded to artful on 2017-10-22 (1 days ago) UserGroups: adm cdrom dip input lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1726831/+subscriptions -- Mailing list: https://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 1717673] Re: gnome-calendar crashed with SIGSEGV in gtk_stack_set_visible_child_name()
I've also had a crash in this function. I rebooted to finish installing 17.04, my Google calendars showed up in Evolution but not GNOME Shell or GNOME Calendar. When I tried to add an event, GNOME calendar crashed. The event was successfully added to Google Calendar. After restarting GNOME Calendar, everything showed up fine. Bug 1689894 might be a duplicate of this bug. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-calendar in Ubuntu. https://bugs.launchpad.net/bugs/1717673 Title: gnome-calendar crashed with SIGSEGV in gtk_stack_set_visible_child_name() Status in gnome-calendar package in Ubuntu: Incomplete Bug description: crashed when editing preferences ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: gnome-calendar 3.26.0-1 ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10 Uname: Linux 4.12.0-13-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Sep 16 12:13:39 2017 ExecutablePath: /usr/bin/gnome-calendar InstallationDate: Installed on 2017-04-22 (147 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412) ProcCmdline: /usr/bin/gnome-calendar --gapplication-service SegvAnalysis: Segfault happened at: 0x7f7e39a85f57 : mov0x30(%rdi,%rax,1),%edx PC (0x7f7e39a85f57) ok source "0x30(%rdi,%rax,1)" (0xfe80) not located in a known VMA region (needed readable region)! destination "%edx" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: gnome-calendar StacktraceTop: gtk_stack_set_visible_child_name () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () ?? () g_hash_table_foreach () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () Title: gnome-calendar crashed with SIGSEGV in gtk_stack_set_visible_child_name() UpgradeStatus: Upgraded to artful on 2017-09-03 (12 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1717673/+subscriptions -- Mailing list: https://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 1717673] Re: gnome-calendar crashed with SIGSEGV in gtk_stack_set_visible_child_name()
(So after crashing, I wasn't able to reproduce the crash.) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-calendar in Ubuntu. https://bugs.launchpad.net/bugs/1717673 Title: gnome-calendar crashed with SIGSEGV in gtk_stack_set_visible_child_name() Status in gnome-calendar package in Ubuntu: Incomplete Bug description: crashed when editing preferences ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: gnome-calendar 3.26.0-1 ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10 Uname: Linux 4.12.0-13-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Sep 16 12:13:39 2017 ExecutablePath: /usr/bin/gnome-calendar InstallationDate: Installed on 2017-04-22 (147 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412) ProcCmdline: /usr/bin/gnome-calendar --gapplication-service SegvAnalysis: Segfault happened at: 0x7f7e39a85f57 : mov0x30(%rdi,%rax,1),%edx PC (0x7f7e39a85f57) ok source "0x30(%rdi,%rax,1)" (0xfe80) not located in a known VMA region (needed readable region)! destination "%edx" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: gnome-calendar StacktraceTop: gtk_stack_set_visible_child_name () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () ?? () g_hash_table_foreach () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () Title: gnome-calendar crashed with SIGSEGV in gtk_stack_set_visible_child_name() UpgradeStatus: Upgraded to artful on 2017-09-03 (12 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1717673/+subscriptions -- Mailing list: https://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 1725487] Re: Hot corner ripple animation is still blue in Ubuntu/Ambiance
Hey Nathanel, sure!
We are trying to follow what upstream applies as much as possible. They
are using a png file there, so I think either working with them to
change for css rules or having their png file into a csv is what makes
more sense in case they change in the future how they are applying
transformations to it.
--
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/1725487
Title:
Hot corner ripple animation is still blue in Ubuntu/Ambiance
Status in gnome-shell package in Ubuntu:
Triaged
Bug description:
Enabling hot-corners using dconf-editor under 'org.gnome.shell enable-
hot-corner' as true, the colour of the ripple is still blue (Adwaita
default scheme) since the compiled shell theme still uses the
specified asset resource:///org/gnome/shell/theme/corner-ripple-
ltr.png - this is also valid for the rtl asset.
I have solved the issue by appending an override to match the current
ubuntu.css overrides as follows:
.ripple-box {
border-radius: 0px 0px 64px 0px !important;
background: #e95420 !important;
width:64px !important;
height:64px !important;
}
.ripple-box:rtl {
border-radius: 0px 0px 0px 64px !important;
background: #e95420 !important;
width:64px !important;
height:64px !important;
}
ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: gnome-shell 3.26.1-0ubuntu4
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Oct 20 17:25:06 2017
DisplayManager: gdm3
InstallationDate: Installed on 2017-10-20 (0 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
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/1725487/+subscriptions
--
Mailing list: https://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 1718552] Re: gnome-shell uses lots of memory
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-shell (Ubuntu) Status: New => Confirmed -- 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/1718552 Title: gnome-shell uses lots of memory Status in gnome-shell package in Ubuntu: Confirmed Bug description: On Ubuntu 17.10 (daily build, VirtualBox), gnome-shell uses lots of memory, even more after opening and closing just a few apps (LibreOffice Writer, Chromium, Nautilus.) More than 640 mb. Also,the CPU usage is quite high too, even if nothing is running in the foreground. See screen captures. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1718552/+subscriptions -- Mailing list: https://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 1725836] Re: No more than 2 displays
Hi Daniel When powering up, I see the booting messages on screen 1 an 3. When signing in I can use screen 2. After signing in I can only see output on screens 1 and 2. In the monitor display function all three displays are detected. Screen 2 is the primary display. If I play around with the monitor display function i can get screen 1 and 2 to work or screen 1 and 3 to work or screen 2 and 3 to work, but I cannot get all three to work at the same time. The screen that is not working is blank. If this does not help I can take some photographs of the screens and send them to you if you wish. Peter On Tue, Oct 24, 2017 at 1:06 AM, Daniel van Vugt < daniel.van.v...@canonical.com> wrote: > What exactly do you see on the third display? Is it off/sleeping? > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1725836 > > Title: > No more than 2 displays > > Status in gnome-shell package in Ubuntu: > Incomplete > Status in mutter package in Ubuntu: > Incomplete > > Bug description: > I have three displays that worked fine in 17.04. > Now ith 17.10 I can only use two of them. Either 1 & 2, 1& 3 or 2 2 & 3. > All three seem to be properly specified in monitors.xml. > The display setup scree detects all three. > UBUNTU 17.10 > AMD PitcairnLSB Version: core-9.20160110ubuntu5-amd64: > core-9.20160110ubuntu5-noarch:security-9.20160110ubuntu5-amd64:security-9. > 20160110ubuntu5-noarch > --- > ApportVersion: 2.20.7-0ubuntu3 > Architecture: amd64 > CurrentDesktop: ubuntu:GNOME > DisplayManager: gdm3 > DistroRelease: Ubuntu 17.10 > InstallationDate: Installed on 2017-02-23 (242 days ago) > InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 > (20161012.2) > Package: mutter > PackageArchitecture: amd64 > ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 > Tags: artful > Uname: Linux 4.13.0-16-generic x86_64 > UpgradeStatus: Upgraded to artful on 2017-10-20 (3 days ago) > UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo > _MarkForUpload: True > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+ > bug/1725836/+subscriptions > -- 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/1725836 Title: No more than 2 displays Status in gnome-shell package in Ubuntu: Incomplete Status in mutter package in Ubuntu: Incomplete Bug description: I have three displays that worked fine in 17.04. Now ith 17.10 I can only use two of them. Either 1 & 2, 1& 3 or 2 2 & 3. All three seem to be properly specified in monitors.xml. The display setup scree detects all three. UBUNTU 17.10 AMD PitcairnLSB Version: core-9.20160110ubuntu5-amd64:core-9.20160110ubuntu5-noarch:security-9.20160110ubuntu5-amd64:security-9.20160110ubuntu5-noarch --- ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2017-02-23 (242 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) Package: mutter PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Tags: artful Uname: Linux 4.13.0-16-generic x86_64 UpgradeStatus: Upgraded to artful on 2017-10-20 (3 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1725836/+subscriptions -- Mailing list: https://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 784440] Re: Volume always too loud: "headphone" level always reset to 100% (AD1981B, ICH6)
Alsa still doesn’t restore its settings on boot. It even resets when unplugging my audio cable. This is a big annoyance resulting in quirky workarounds where people manually store a configuration and loading it via autostart after sleeping for N seconds. Any way this can progress? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/784440 Title: Volume always too loud: "headphone" level always reset to 100% (AD1981B, ICH6) Status in alsa-driver package in Ubuntu: Confirmed Bug description: The volume of the sound coming out from the headphone jack is always too loud. When the GNOME volume applet slider is set to ~50%, I see the following values on alsamixer: * Master: 52% * Headhone: 100% * PCM: 74% The sound coming out from the jack is unbearably high. If I set the slider to ~3% (a setting that produces an high but acceptable volume) the alsamixer values change to * Master: 0% * Headphone: 100% * PCM: 10% I found that setting Headphone to ~40% is the only way to get an acceptable volume when the GNOME volume applet slider is set to ~50%. The problem now is that these seems to be no way to store that value permanently, it is always reset to 100% on boot. So, * the default values for this device should be adjusted to values that produce an acceptable volume on the headphone jake. * the value manually set for the Headphone knob should be restored on boot. ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: alsa-base 1.0.22.1+dfsg-0ubuntu3 ProcVersionSignature: Ubuntu 2.6.32-31.61-generic 2.6.32.32+drm33.14 Uname: Linux 2.6.32-31-generic i686 AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21. Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gioele 1219 F pulseaudio gioele 4707 F alsamixer Card0.Amixer.info: Card hw:0 'ICH6'/'Intel ICH6 with AD1981B at irq 23' Mixer name : 'Analog Devices AD1981B' Components : 'AC97a:41445374' Controls : 34 Simple ctrls : 23 Date: Wed May 18 09:06:34 2011 EcryptfsInUse: Yes PackageArchitecture: all SelectedCard: 0 ICH6 ICH4 - Intel ICH6 SourcePackage: alsa-driver Symptom: audio Title: [ICH4 - Intel ICH6] Playback problem dmi.bios.date: 11/29/2005 dmi.bios.vendor: Dell Inc. dmi.bios.version: A07 dmi.board.name: 0WH415 dmi.board.vendor: Dell Inc. dmi.chassis.type: 16 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA07:bd11/29/2005:svnDellInc.:pnOptiPlexSX280:pvr:rvnDellInc.:rn0WH415:rvr:cvnDellInc.:ct16:cvr: dmi.product.name: OptiPlex SX280 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/784440/+subscriptions -- Mailing list: https://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 1700092] Re: Text is tiny on HiDPI screens
** Tags added: artful -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1700092 Title: Text is tiny on HiDPI screens Status in gedit: Confirmed Status in gedit package in Ubuntu: Confirmed Bug description: I am on Artful and have switched to GNOME as GNOME is the default desktop now and Unity shows some instabilities. I am using a Lenovo Thinkpad X1 Carbon (2nd gen.) notebook with 14-inch QHD (2560x1440) display, so I am well over the good old 72-dpi CRT resolution. With some effort I have at least got a somewhat useful scaling of the GUI elements (esp. text size), mainly by getting into Unity7, getting into the Display Settings there, removing my ~1.5 scaling factor, returning to GNOME, installing the advanced settings manager (gnome- tweak-tool or so) and setting a scaling factor of ~2). Large text in accessibilty does not work for me as it makes the text huge. Unfortunately gedit does not bother on these efforts, it seems to be hard-coded to 72 dpi and so the text is tiny, unusable not only for people with vision problems. As this is the default text editor, which is often also called by web browsers to display text files, this needs to get fixed. Please take this into account ASAP, ideally on 17.10 at the latest. Please consider backporting upstream fixes for achieving this goal. To manage notifications about this bug go to: https://bugs.launchpad.net/gedit/+bug/1700092/+subscriptions -- Mailing list: https://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 1726848] Re: gnome-control-center crashed with SIGSEGV
*** This bug is a duplicate of bug 1720400 *** https://bugs.launchpad.net/bugs/1720400 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1726813, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1726848/+attachment/4991016/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1726848/+attachment/4991018/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1726848/+attachment/4991021/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1726848/+attachment/4991022/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1726848/+attachment/4991023/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1726848/+attachment/4991024/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1726848/+attachment/4991025/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1726813 ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- 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/1726848 Title: gnome-control-center crashed with SIGSEGV Status in gnome-control-center package in Ubuntu: New Bug description: gnome-control-center crashed with SIGSEGV ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: gnome-control-center 1:3.26.1-0ubuntu4 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 24 14:25:00 2017 ExecutablePath: /usr/bin/gnome-control-center ProcCmdline: gnome-control-center --overview ProcEnviron: PATH=(custom, user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7f54ca7e7b3b:mov0x8(%rax),%rax PC (0x7f54ca7e7b3b) ok source "0x8(%rax)" (0x0008) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-control-center StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1 ?? () from /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1 ?? () from /usr/lib/x86_64-linux-gnu/dri/r600_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/r600_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/r600_dri.so Title: gnome-control-center crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom davfs2 davfs2 dialout dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1726848/+subscriptions -- Mailing list: https://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 980519] Re: Random log off in Ubuntu 12.04 LTS
My Dell Latitude E5410 automatically logs me off while am working and closes all my applications. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers in Ubuntu. https://bugs.launchpad.net/bugs/980519 Title: Random log off in Ubuntu 12.04 LTS Status in Unity: Fix Released Status in gnome-desktop package in Ubuntu: Confirmed Status in nvidia-graphics-drivers package in Ubuntu: Fix Released Status in unity package in Ubuntu: Fix Released Status in xorg package in Ubuntu: Fix Released Status in Fedora: New Bug description: I get logged off from Ubuntu sometimes. There is no error message or any indication that it is going to log off. The screen goes black, and after 2-4 seconds, i get presented with the Ubuntu Log On Screen. There is no clear pattern (or at least if have not noticed any). One time i am working with Netbeans, another time i am using firefox. This also means that at present i can not clearly say what package might be causing this behaviour. I am fairly sure the problem lies in 12.04 (or more precise - the combination of 12.04 and the hardware i am using). I do not have the same problem running 11.04 or 11.10. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/980519/+subscriptions -- Mailing list: https://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 1502476] Re: Totem menubar is displayed in fullscreen mode during gnome-flaskback session
Most probably the very same problem is present in Eog https://bugs.launchpad.net/ubuntu/+source/eog/+bug/1545872 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1502476 Title: Totem menubar is displayed in fullscreen mode during gnome-flaskback session Status in Totem: New Status in totem package in Ubuntu: Confirmed Bug description: The menubar of Totem video player doesn't hide in fullscreen mode when I use gnome-flashback session. To manage notifications about this bug go to: https://bugs.launchpad.net/totem/+bug/1502476/+subscriptions -- Mailing list: https://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 1726861] [NEW] bookmarks & history system not available
Public bug reported: I've followed the troubleshooting information suggested in Firefox with no results including multiple reboots. Also uninstalled & reinstalled firefox. Still cannot restore bookmarks or import bookmarks from html. Cannot sync bookmarks using firefox sync. Firefox still reports that the bookmark & history system is not available because some files are in use by another application. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: firefox 56.0+build6-0ubuntu0.16.04.2 ProcVersionSignature: Ubuntu 4.4.0-97.120-generic 4.4.87 Uname: Linux 4.4.0-97-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia AddonCompatCheckDisabled: False ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: brent 2321 F pulseaudio /dev/snd/controlC2: brent 2321 F pulseaudio /dev/snd/controlC0: brent 2321 F pulseaudio BuildID: 20171003101344 Channel: Unavailable CurrentDesktop: GNOME Date: Tue Oct 24 07:49:01 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 2015-03-09 (959 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) IpRoute: default via 192.168.1.1 dev eth0 proto static metric 100 169.254.0.0/16 dev eth0 scope link metric 1000 192.168.1.0/24 dev eth0 proto kernel scope link src 192.168.1.203 metric 100 IwConfig: lono wireless extensions. eth0 no wireless extensions. Locales: extensions.sqlite corrupt or missing MostRecentCrashID: bp-c54702b4-1092-4d28-8224-51ecd1171023 Plugins: Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so PrefSources: prefs.js ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Profiles: Profile0 (Default) - LastVersion=56.0/20171003101344 (In use) RfKill: RunningIncompatibleAddons: False SourcePackage: firefox Themes: extensions.sqlite corrupt or missing UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/03/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1102 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P7P55 LX dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1102:bd01/03/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP7P55LX:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer ** Affects: firefox (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1726861 Title: bookmarks & history system not available Status in firefox package in Ubuntu: New Bug description: I've followed the troubleshooting information suggested in Firefox with no results including multiple reboots. Also uninstalled & reinstalled firefox. Still cannot restore bookmarks or import bookmarks from html. Cannot sync bookmarks using firefox sync. Firefox still reports that the bookmark & history system is not available because some files are in use by another application. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: firefox 56.0+build6-0ubuntu0.16.04.2 ProcVersionSignature: Ubuntu 4.4.0-97.120-generic 4.4.87 Uname: Linux 4.4.0-97-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia AddonCompatCheckDisabled: False ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: brent 2321 F pulseaudio /dev/snd/controlC2: brent 2321 F pulseaudio /dev/snd/controlC0: brent 2321 F pulseaudio BuildID: 20171003101344 Channel: Unavailable CurrentDesktop: GNOME Date: Tue Oct 24 07:49:01 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 2015-03-09 (959 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) IpRoute: default via 192.168.1.1 dev eth0 proto static metric 100 169.254.0
[Desktop-packages] [Bug 1726853] Re: system-config-printer.py crashed with TypeError in get_authentication(): update expected at most 1 arguments, got 2
** Information type changed from Private to Public ** Changed in: system-config-printer (Ubuntu) Assignee: (unassigned) => Till Kamppeter (till-kamppeter) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to system-config-printer in Ubuntu. https://bugs.launchpad.net/bugs/1726853 Title: system-config-printer.py crashed with TypeError in get_authentication(): update expected at most 1 arguments, got 2 Status in system-config-printer package in Ubuntu: New Bug description: After changing my NT domain passowrd, got NT_STATUS_ACCESS_DENIED when trying to print something to samba printer. Rather than prompting for a new password, system-config-printer just crash... not sure this is really link to my password update as I upgrade my system from 17.04 to 17.10 as the same time... $ lsb_release -rd Description: Ubuntu 17.10 Release: 17.10 $ apt-cache policy system-config-printer system-config-printer: Installed: 1.5.9+20170825-0ubuntu1 Candidate: 1.5.9+20170825-0ubuntu1 Version table: *** 1.5.9+20170825-0ubuntu1 500 500 http://ch.archive.ubuntu.com/ubuntu artful/main amd64 Packages 500 http://ch.archive.ubuntu.com/ubuntu artful/main i386 Packages 100 /var/lib/dpkg/status ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: system-config-printer 1.5.9+20170825-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-16.19-lowlatency 4.13.4 Uname: Linux 4.13.0-16-lowlatency x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CrashCounter: 1 CurrentDesktop: XFCE Date: Tue Oct 24 14:34:30 2017 ExecutablePath: /usr/share/system-config-printer/system-config-printer.py InstallationDate: Installed on 2016-05-03 (539 days ago) InstallationMedia: Ubuntu-Studio 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) InterpreterPath: /usr/bin/python3.6 Lpstat: device for DCP9020CDW: dnssd://Brother%20DCP-9020CDW._ipp._tcp.local/?uuid=e3248000-80ce-11db-8000-30055c0d34df device for FollowMe: smb://print/FOLLOWME_PS device for HP-Officejet-4630: socket://192.168.1.116:9100 device for HP_Officejet_4630_series_AD35AD: dnssd://HP%20Officejet%204630%20series%20%5BAD35AD%5D._ipp._tcp.local/?uuid=1c852a4d-b800-1f08-abcd-d0bf9cad35ad device for KyoceraMda: socket://192.168.1.112:9100 MachineType: LENOVO 20FAS11D00 PackageArchitecture: all Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/DCP9020CDW.ppd', '/etc/cups/ppd/HP_Officejet_4630_series_AD35AD.ppd', '/etc/cups/ppd/HP-Officejet-4630.ppd', '/etc/cups/ppd/KyoceraMda.ppd', '/etc/cups/ppd/FollowMe.ppd'] failed with exit code 2: grep: /etc/cups/ppd/DCP9020CDW.ppd: Permission denied grep: /etc/cups/ppd/HP_Officejet_4630_series_AD35AD.ppd: Permission denied grep: /etc/cups/ppd/HP-Officejet-4630.ppd: Permission denied grep: /etc/cups/ppd/KyoceraMda.ppd: Permission denied grep: /etc/cups/ppd/FollowMe.ppd: Permission denied ProcCmdline: /usr/bin/python3 /usr/share/system-config-printer/system-config-printer.py ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-lowlatency root=UUID=5cbe7176-d524-4b66-8e26-e53e6f331691 ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2 PythonArgs: ['/usr/share/system-config-printer/system-config-printer.py'] PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-2ubuntu1 SourcePackage: system-config-printer Title: system-config-printer.py crashed with TypeError in get_authentication(): update expected at most 1 arguments, got 2 UpgradeStatus: Upgraded to artful on 2017-10-21 (2 days ago) UserGroups: adm audio cdrom dip docker lpadmin plugdev postgres sambashare sudo vboxusers dmi.bios.date: 01/15/2016 dmi.bios.vendor: LENOVO dmi.bios.version: N1CET37W (1.05 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FAS11D00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1CET37W(1.05):bd01/15/2016:svnLENOVO:pn20FAS11D00:pvrThinkPadT460s:rvnLENOVO:rn20FAS11D00:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460s dmi.product.name: 20FAS11D00 dmi.product.version: ThinkPad T460s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/system-config-printer/+bug/1726853/+subscriptions -- Mailing list: https://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 1726848] Re: gnome-control-center crashed with SIGSEGV
*** This bug is a duplicate of bug 1720400 *** https://bugs.launchpad.net/bugs/1720400 ** This bug is no longer a duplicate of private bug 1726813 ** This bug has been marked a duplicate of bug 1720400 /usr/bin/gnome-control-center:11:update_buffers:image_get_buffers:intel_update_image_buffers:intel_update_renderbuffers:intel_prepare_render -- 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/1726848 Title: gnome-control-center crashed with SIGSEGV Status in gnome-control-center package in Ubuntu: New Bug description: gnome-control-center crashed with SIGSEGV ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: gnome-control-center 1:3.26.1-0ubuntu4 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 24 14:25:00 2017 ExecutablePath: /usr/bin/gnome-control-center ProcCmdline: gnome-control-center --overview ProcEnviron: PATH=(custom, user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7f54ca7e7b3b:mov0x8(%rax),%rax PC (0x7f54ca7e7b3b) ok source "0x8(%rax)" (0x0008) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-control-center StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1 ?? () from /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1 ?? () from /usr/lib/x86_64-linux-gnu/dri/r600_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/r600_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/r600_dri.so Title: gnome-control-center crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom davfs2 davfs2 dialout dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1726848/+subscriptions -- Mailing list: https://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 1726827] Re: gnome-shell crashed with SIGSEGV in clutter_actor_is_visible()
** Information type changed from Private to Public -- 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/1726827 Title: gnome-shell crashed with SIGSEGV in clutter_actor_is_visible() Status in gnome-shell package in Ubuntu: New Bug description: Crashed during resume from suspend. ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.1-0ubuntu4 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CrashCounter: 1 CurrentDesktop: GNOME Date: Tue Oct 24 06:50:44 2017 DisplayManager: gdm3 EcryptfsInUse: Yes ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2016-11-15 (343 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) ProcCmdline: /usr/bin/gnome-shell SegvAnalysis: Segfault happened at: 0x7f8b26803c46 : cmp %rax,(%rdx) PC (0x7f8b26803c46) ok source "%rax" ok destination "(%rdx)" (0x4455e9fdf6e410) not located in a known VMA region (needed writable region)! SegvReason: writing unknown VMA Signal: 11 SourcePackage: gnome-shell StacktraceTop: clutter_actor_is_visible () from /usr/lib/x86_64-linux-gnu/mutter/libmutter-clutter-1.so ?? () from /usr/lib/x86_64-linux-gnu/mutter/libmutter-clutter-1.so ?? () from /usr/lib/x86_64-linux-gnu/mutter/libmutter-clutter-1.so ?? () from /usr/lib/gnome-shell/libst-1.0.so ?? () from /usr/lib/gnome-shell/libst-1.0.so Title: gnome-shell crashed with SIGSEGV in clutter_actor_is_visible() UpgradeStatus: Upgraded to artful on 2017-10-21 (2 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1726827/+subscriptions -- Mailing list: https://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 1726797] Re: Segmentation fault on annotation and "Open Copy"
Thank you for taking the time to report this bug and helping to make Ubuntu better. However, your crash report is either missing or challenging to deal with as a ".crash" file. Please follow these instructions to have apport report a new bug about your crash that can be dealt with by the automatic retracer. If you are running the Ubuntu Stable Release you might need to enable apport in /etc/default/apport and restart. Now open your file manager, navigate to your /var/crash directory and open the crash report you wish to submit. If this fails you will have to open a terminal and file your report with 'ubuntu-bug /var/crash/_my_crash_report.crash' where _my_crash_report.crash is the crash you would like to report. If you get an error that you aren't allowed to access this report you will have to file it with 'sudo ubuntu-bug /var/crash/_my_crash_report.crash'. I'm closing this bug report since the process outlined above will automatically open a new bug report which can then dealt with more efficiently. Thanks in advance for your cooperation and understanding. ** Changed in: evince (Ubuntu) Importance: Undecided => High ** Changed in: evince (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1726797 Title: Segmentation fault on annotation and "Open Copy" Status in evince package in Ubuntu: Invalid Bug description: Evince version 3.18.2 crashes (Segmentation fault (core dumped)) on Ubuntu 16.04.3 LTS on the following sequence of actions: 1. Open any pdf, for example http://gahp.net/wp-content/uploads/2017/09/sample.pdf. 2. Add any annotation, for example highlight the document title. 3. Click File->Open a copy. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1726797/+subscriptions -- Mailing list: https://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 1726707] Re: gnome-software crashes machine hard
Could you add your syslog after getting the issue? Is your ssh session still active after getting the bug? Could be a kernel issue... ** Changed in: gnome-software (Ubuntu) Importance: Undecided => High ** Changed in: gnome-software (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1726707 Title: gnome-software crashes machine hard Status in gnome-software package in Ubuntu: Incomplete Bug description: gnome-software instantly crashes my machine hard reproducible, only forced power off possible. mouse stuck, no num-lock, machine not pingable anymore. as there is no crash report whatsoever generated i installed ssh on the machine and started "DISPLAY=:0 gnome-software --verbose" via ssh session, output attached. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1726707/+subscriptions -- Mailing list: https://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 1726707] Re: gnome-software crashes machine hard
Does moving /usr/lib/x86_64-linux-gnu/gs- plugins-11/libgs_plugin_fwupd.so away workaround the locking? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1726707 Title: gnome-software crashes machine hard Status in gnome-software package in Ubuntu: Incomplete Bug description: gnome-software instantly crashes my machine hard reproducible, only forced power off possible. mouse stuck, no num-lock, machine not pingable anymore. as there is no crash report whatsoever generated i installed ssh on the machine and started "DISPLAY=:0 gnome-software --verbose" via ssh session, output attached. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1726707/+subscriptions -- Mailing list: https://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 1726760] Re: gnome-shell crashed with SIGSEGV in gtk_action_observer_action_removed()
** Information type changed from Private to Public -- 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/1726760 Title: gnome-shell crashed with SIGSEGV in gtk_action_observer_action_removed() Status in gnome-shell package in Ubuntu: New Bug description: The system was stopped when i was trying openned Geary ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.1-0ubuntu4 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 24 10:35:03 2017 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell ProcCmdline: /usr/bin/gnome-shell ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7f0c24dc5a87 :mov(%rbx),%rdx PC (0x7f0c24dc5a87) ok source "(%rbx)" (0x014d) not located in a known VMA region (needed readable region)! destination "%rdx" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-shell StacktraceTop: gtk_action_observer_action_removed () from /usr/lib/gnome-shell/libgnome-shell-menu.so ?? () from /usr/lib/gnome-shell/libgnome-shell-menu.so ?? () from /usr/lib/gnome-shell/libgnome-shell-menu.so gtk_action_muxer_remove () from /usr/lib/gnome-shell/libgnome-shell-menu.so gtk_action_muxer_insert () from /usr/lib/gnome-shell/libgnome-shell-menu.so Title: gnome-shell crashed with SIGSEGV in gtk_action_observer_action_removed() UpgradeStatus: Upgraded to artful on 2017-10-23 (0 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1726760/+subscriptions -- Mailing list: https://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 1726821] [NEW] It takes a while for the tray notification menu to open when clicking on the time and date in the top bar
You have been subscribed to a public bug: Dear all, Once I click on the time and date entry in the top bar, it takes a couple of seconds for the menu to open [1]. Tested on Ubuntu 17.10 with the latest updates installed. Not sure if this is a bug or user error. [1] https://www.useloom.com/share/a80d02fd2f894c9fa6eac201c4fa1c7b ** Affects: gnome-shell (Ubuntu) Importance: Low Status: New -- It takes a while for the tray notification menu to open when clicking on the time and date in the top bar https://bugs.launchpad.net/bugs/1726821 You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1726854] Re: gnome-calendar crashed with SIGSEGV in get_circle_surface_from_color()
*** This bug is a duplicate of bug 1726198 *** https://bugs.launchpad.net/bugs/1726198 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1726198, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1726854/+attachment/4991065/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1726854/+attachment/4991067/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1726854/+attachment/4991070/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1726854/+attachment/4991071/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1726854/+attachment/4991072/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1726854/+attachment/4991073/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1726854/+attachment/4991074/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1726198 ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-calendar in Ubuntu. https://bugs.launchpad.net/bugs/1726854 Title: gnome-calendar crashed with SIGSEGV in get_circle_surface_from_color() Status in gnome-calendar package in Ubuntu: New Bug description: calendar crashed while i wasn't even using it. ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: gnome-calendar 3.26.2-1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 24 08:42:14 2017 EcryptfsInUse: Yes ExecutablePath: /usr/bin/gnome-calendar InstallationDate: Installed on 2017-10-19 (4 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcCmdline: /usr/bin/gnome-calendar --gapplication-service ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANG=en_US.UTF-8 SegvAnalysis: Segfault happened at: 0x55ca93f600a3 : movsd 0x18(%r12),%xmm3 PC (0x55ca93f600a3) ok source "0x18(%r12)" (0x0018) not located in a known VMA region (needed readable region)! destination "%xmm3" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-calendar StacktraceTop: get_circle_surface_from_color () ?? () ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6 ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6 g_cclosure_marshal_generic () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: gnome-calendar crashed with SIGSEGV in get_circle_surface_from_color() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1726854/+subscriptions -- Mailing list: https://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 1726821] Re: It takes a while for the tray notification menu to open when clicking on the time and date in the top bar
Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance. ** Package changed: ubuntu => gnome-shell (Ubuntu) ** Changed in: gnome-shell (Ubuntu) Importance: Undecided => Low -- 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/1726821 Title: It takes a while for the tray notification menu to open when clicking on the time and date in the top bar Status in gnome-shell package in Ubuntu: New Bug description: Dear all, Once I click on the time and date entry in the top bar, it takes a couple of seconds for the menu to open [1]. Tested on Ubuntu 17.10 with the latest updates installed. Not sure if this is a bug or user error. [1] https://www.useloom.com/share/a80d02fd2f894c9fa6eac201c4fa1c7b To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1726821/+subscriptions -- Mailing list: https://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 1725897] Re: Offers to install snaps that need the gnome-3-26-1604 snap & be connected to work
Well, you have the deb installed not the snap so the info is correct. Anyway it's offtopic for this bug and known as bug #1711801 so better to continue the discussion in that one About bug reporting for snaps there is no real standard place at the moment, you can use the forum or contact the maintainer... -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1725897 Title: Offers to install snaps that need the gnome-3-26-1604 snap & be connected to work Status in gnome-software package in Ubuntu: New Bug description: If doing this then it should install the needed snap (if not already installed) & perform the connection for the user Test case: Open Ubuntu Software Search gnome-system-monitor It will show it as not being installed (another bug, see screenshot? Click to install After install finishes click the launch button What happens: Nothing User must install gnome-3-26-1604 snap & then run an obscure (to normal users) connect command ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-software 3.26.1-0ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Oct 21 22:32:15 2017 InstallationDate: Installed on 2017-10-06 (15 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171004) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-limba N/A gnome-software-plugin-snap3.26.1-0ubuntu2 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1725897/+subscriptions -- Mailing list: https://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 1726826] Re: screen 256 colour TERM setting breaks logging into older hosts
I'm not sure why newer versions of screen (or Ubuntu's configuration) tend to set this weird value of "screen.xterm-256color". The more readable value "screen-256color" is supported at least since Trusty 14.04 (see https://packages.ubuntu.com/trusty/all/ncurses- base/filelist), probably much earlier than that (I'm seeing forum posts about "screen-256color" dated 2011-ish). I recommend that you configure your local screen to set this value instead. Indeed screen setting a new value of "screen.xterm-256color" that hasn't had years to get deployed across systems is a bug. (On a somewhat related note, this whole architecture is plain dead broken. ssh'ing and friends should transfer the entire description of the current terminal's behavior, not just a name. Then we wouldn't have to wait for years, anything new would be usable straight away.) -- 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/1726826 Title: screen 256 colour TERM setting breaks logging into older hosts Status in gnome-terminal package in Ubuntu: New Status in screen package in Ubuntu: New Bug description: As of 16.04, the screen program started using a 256 colour setting. The problem is that this setting is relatively new and has not had a chance to propagate to older hosts, including something as new as the previous 15.x release. For example: -- paul@1604-host:~$ echo $TERM screen.xterm-256color paul@y1604-host:~$ ssh oldermachine Welcome to Ubuntu 15.04 (GNU/Linux 3.19.0-84-generic x86_64) * Documentation: https://help.ubuntu.com/ 0 packages can be updated. 0 updates are security updates. Last login: Mon Oct 23 15:52:17 2017 from yow-pgortmak-d1.wrs.com paul@oldermachine:~$ echo foo > foo paul@yoldermachine:~$ less foo WARNING: terminal is not fully functional foo (press RETURN) paul@oldermachine:~$ export TERM=screen paul@yoldermachine:~$ less foo foo paul@oldermachine:~$ cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=15.04 DISTRIB_CODENAME=vivid DISTRIB_DESCRIPTION="Ubuntu 15.04" paul@oldermachine:~$ -- This makes it extremely annoying to use 16.04 in order to interact with any other linux/unix machines. The 256 color term type needs at least a couple years roll-out time before it becomes the default. Otherwise the older machines won't have it and they will complain and default to ancient crippled defaults and nag you each time they have to do so. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1726826/+subscriptions -- Mailing list: https://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 1726858] Re: Xorg crashed with SIGSEGV in miPointerSetPosition()
*** This bug is a duplicate of bug 1681084 *** https://bugs.launchpad.net/bugs/1681084 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1681084, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1726858/+attachment/4991091/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1726858/+attachment/4991094/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1726858/+attachment/4991104/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1726858/+attachment/4991106/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1726858/+attachment/4991107/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1726858/+attachment/4991108/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1726858/+attachment/4991109/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1681084 ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- 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/1726858 Title: Xorg crashed with SIGSEGV in miPointerSetPosition() Status in xorg-server package in Ubuntu: New Bug description: I wasn't doing anything fancy at the time of crash. Was just switching my mouse pointer back and forth between my dual monitors (One, laptop built-in display, connected to Intel GPU and other one, connected to NVidia GPU via HDMI). Using nouveau on Wayland. Fresh Ubuntu 17.10 installation. No configuration residues from old installs. ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: xserver-xorg-core 2:1.19.5-0ubuntu2 Uname: Linux 4.13.8-041308-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Oct 24 14:47:21 2017 DistUpgraded: Fresh install DistroCodename: artful DistroVariant: ubuntu ExecutablePath: /usr/lib/xorg/Xorg ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company HD Graphics 530 [103c:820f] Subsystem: Hewlett-Packard Company GM107M [GeForce GTX 960M] [103c:820f] InstallationDate: Installed on 2017-10-20 (3 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: HP HP Pavilion Notebook ProcCmdline: /usr/lib/xorg/Xorg vt2 -displayfd 3 -auth /run/user/1000/gdm/Xauthority -background none -noreset -keeptty -verbose 3 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.8-041308-generic root=UUID=069ee2d3-f680-4e62-b9bc-6b64e21e145a ro quiet splash pci=noaer vt.handoff=7 SegvAnalysis: Segfault happened at: 0x55cc3aa9ca6c:cmp0x10(%rax),%ecx PC (0x55cc3aa9ca6c) ok source "0x10(%rax)" (0x2e6600401f0fc403) not located in a known VMA region (needed readable region)! destination "%ecx" ok Stack memory exhausted (SP below stack segment) SegvReason: reading unknown VMA Signal: 11 SourcePackage: xorg-server StacktraceTop: ?? () miPointerSetPosition () ?? () ?? () GetPointerEvents () Title: Xorg crashed with SIGSEGV in miPointerSetPosition() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo dmi.bios.date: 05/05/2016 dmi.bios.vendor: Insyde dmi.bios.version: F.06 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 820F dmi.board.vendor: HP dmi.board.version: 82.24 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.06:bd05/05/2016:svnHP:pnHPPavilionNotebook:pvrType1ProductConfigId:rvnHP:rn820F:rvr82.24:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null dmi.product.name: HP Pavilion Notebook dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.83-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1 version.xserver-xorg
[Desktop-packages] [Bug 1725814] Re: The Activities top left button reacts to a mouse-up (e.g. drag and drop) instead of a click
Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance. -- 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/1725814 Title: The Activities top left button reacts to a mouse-up (e.g. drag and drop) instead of a click Status in gnome-shell package in Ubuntu: Confirmed Bug description: Honestly I have no idea which package this is in and I could not identify it by following the wiki page for identifying packages. I had no luck with the ubuntu-bug command either. Feel free to migrate at your discretion. The Activities menu/button at the top left in the desktop menu(?) bar seems to listen to left-mouse-up instead of a full click with the mouse. If I want to e.g. select all my files on the desktop by click-and- dragging a selection box and then end the selection at the top left of the screen I will then also activate the Activities button if I release the mouse button over it. I expect most button-like UI controls to only trigger on complete mouse clicks: mouse down, mouse up. Pretty much the *only* exception to this expectation -- that I can think of -- is when a click is initiated on one menu item and finishes on a menu item that is its peer. --- Description: Ubuntu 17.10 Release: 17.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1725814/+subscriptions -- Mailing list: https://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 1726717] Re: Alignment of external screen limits placing of icons
Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance. ** Package changed: gnome-session (Ubuntu) => nautilus (Ubuntu) ** Changed in: nautilus (Ubuntu) Importance: Undecided => Low -- 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/1726717 Title: Alignment of external screen limits placing of icons Status in nautilus package in Ubuntu: New Bug description: Reporting against gnome-desktop since I do not know better. Please assign to appropriate package. Thanks! Using external monitors with the gnome desktop behaves unexpected in a few ways. One is, that the alignment of screens limits, where icons can be placed on that screens: My external monitor is higher than the internal screen of my laptop. I have aligned the screens at the bottom. This makes the bottom part of the (external, higher) screen unusable for placing icons. This is probably best seen on the attached screenshot. Thanks for caring! ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-session (not installed) ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 24 08:49:30 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2015-12-13 (680 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: gnome-session UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1726717/+subscriptions -- Mailing list: https://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 1711534] [NEW] Application list cluttered on a fresh Artful installation
You have been subscribed to a public bug: GNOME Shell application list contains many rarely-used and sometimes redundant app icons like: * 3 different icons for fcitx * 2 icons for OnBoard (OnBoard settings are accessible from OnBoard itself) * ImageMagick (Most probably rarely used, especially when there's also EOG) * Language Support, Input Method (There's a language panel in gnome-control-center, so this looks like a unity-control-center leftover) Because of that, the application list is 3 pages long, making other apps unnecessarily hard to find. One way to solve that would be to pack rarely-used, but still useful stuff into GNOME's Sundry app folder. Completely redundant icons can probably be just removed. Original suggestion: https://didrocks.fr/2017/08/03/ubuntu--guadec-2017 -and-plans-for-gnome-shell-migration/#comment-3455664382 ** Affects: gnome-menus (Ubuntu) Importance: Undecided Status: Confirmed -- Application list cluttered on a fresh Artful installation https://bugs.launchpad.net/bugs/1711534 You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-menus in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1725667] Re: Wacom Intuos comic/draw/photo/art is not detected
Thanks ** Changed in: gnome-control-center (Ubuntu) Status: New => Triaged -- 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/1725667 Title: Wacom Intuos comic/draw/photo/art is not detected Status in gnome-control-center: Confirmed Status in gnome-control-center package in Ubuntu: Triaged Bug description: The tablet works but since it's not detected it's not possible to change settings from the control center. However, command-line commands such as ''xsetwacom'' do work to an extent (could map the output to a specific monitor but could not assign a key to all 4 buttons of the tablet, only 2). The configuration is lost each time the pc is restarted or if the tablet is removed and then replugged. (ps. This bug might be related to the fact that this tablet does not have a ''rubber'' on the other end of the pen, but I cannot confirm it). To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1725667/+subscriptions -- Mailing list: https://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 1711241] Re: Unity support patch doesn't build with nautilus 3.25.90
Khurshid, please file a new bug. If you attach a patch you want sponsored, please subscribe ubuntu-sponsors. Otherwise, it will be very easy for your work to not be seen since this bug is fixed and closed. -- 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/1711241 Title: Unity support patch doesn't build with nautilus 3.25.90 Status in nautilus package in Ubuntu: Fix Released Bug description: I have prepared nautilus 3.25.90 in the GNOME3 Staging PPA for Ubuntu 17.10 "artful". The 12_unity_launcher_support.patch has a problem that fails the build and I don't know how to fix it so I disabled the patch for now. Nautilus 3.25 introduces meson support and drops autotools support so that's one factor when I updated the patch. But when I disable the patch, nautilus crashes on start in Unity. Build log attached. Build Log Excerpt == [164/222] cc -Isrc/nautilus@sta -Isrc -Isubprojects/libgd/libgd -I../src -I. -I../ -Isubprojects/libgd -I../subprojects/libgd -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/at-spi2-atk/2.0 -I/usr/include/at-spi-2.0 -I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -I/usr/include/gtk-3.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/mirclient -I/usr/include/mircore -I/usr/include/mircookie -I/usr/include/harfbuzz -I/usr/include/pango-1.0 -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng16 -I/usr/include/gnome-autoar-0 -I/usr/include/libxml2 -I/usr/include/zeitgeist-2.0 -I/usr/include/gsettings-desktop-schemas -I/usr/include/gail-3.0 -I/usr/include/gnome-desktop-3.0 -I/usr/include/tracker-2.0 -I/usr/include/tracker-2.0/libtracker-sparql -I/usr/include/libexif -I/usr/include/unity/unity -I/usr/include/dee-1.0 -I/usr/include/libdbusmenu-glib-0.4 -I/usr/include/exempi-2.0 -fdiagnostics-color=always -pipe -D_FILE_OFFSET_BITS=64 -Wno-deprecated-declarations -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -pthread -DLIBGD_GTK_HACKS=1 -DLIBGD__VIEW_COMMON=1 -DLIBGD_MAIN_ICON_VIEW=1 -DLIBGD_MAIN_LIST_VIEW=1 -DLIBGD_MAIN_VIEW=1 -DLIBGD_TAGGED_ENTRY=1 -MMD -MQ 'src/nautilus@sta/unity-quicklist-handler.c.o' -MF 'src/nautilus@sta/unity-quicklist-handler.c.o.d' -o 'src/nautilus@sta/unity-quicklist-handler.c.o' -c ../src/unity-quicklist-handler.c FAILED: src/nautilus@sta/unity-quicklist-handler.c.o cc -Isrc/nautilus@sta -Isrc -Isubprojects/libgd/libgd -I../src -I. -I../ -Isubprojects/libgd -I../subprojects/libgd -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/at-spi2-atk/2.0 -I/usr/include/at-spi-2.0 -I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -I/usr/include/gtk-3.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/mirclient -I/usr/include/mircore -I/usr/include/mircookie -I/usr/include/harfbuzz -I/usr/include/pango-1.0 -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng16 -I/usr/include/gnome-autoar-0 -I/usr/include/libxml2 -I/usr/include/zeitgeist-2.0 -I/usr/include/gsettings-desktop-schemas -I/usr/include/gail-3.0 -I/usr/include/gnome-desktop-3.0 -I/usr/include/tracker-2.0 -I/usr/include/tracker-2.0/libtracker-sparql -I/usr/include/libexif -I/usr/include/unity/unity -I/usr/include/dee-1.0 -I/usr/include/libdbusmenu-glib-0.4 -I/usr/include/exempi-2.0 -fdiagnostics-color=always -pipe -D_FILE_OFFSET_BITS=64 -Wno-deprecated-declarations -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -pthread -DLIBGD_GTK_HACKS=1 -DLIBGD__VIEW_COMMON=1 -DLIBGD_MAIN_ICON_VIEW=1 -DLIBGD_MAIN_LIST_VIEW=1 -DLIBGD_MAIN_VIEW=1 -DLIBGD_TAGGED_ENTRY=1 -MMD -MQ 'src/nautilus@sta/unity-quicklist-handler.c.o' -MF 'src/nautilus@sta/unity-quicklist-handler.c.o.d' -o 'src/nautilus@sta/unity-quicklist-handler.c.o' -c ../src/unity-quicklist-handler.c ../src/unity-quicklist-handler.c: In function ‘unity_quicklist_handler_get_singleton’: ../src/unity-quicklist-handler.c:154:9: error: expected declaration or statement at end of input unity_quicklist_handler_singleton = unity_quicklist_handler_new (); ^ ../src/unity-quicklist-handler.c:154:9: error: expected declaration or statement at end of input To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1711241/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad
[Desktop-packages] [Bug 1666681] Re: Restore interactive_search.patch (type-ahead search)
Sorry, I spent time trying to get the old patch to work but my patch didn't work. See paragraph 2 of the bug description. If someone contributes a working patch, the Ubuntu Desktop team may reconsider. ** Changed in: nautilus (Ubuntu) Status: Confirmed => Won't Fix -- 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/181 Title: Restore interactive_search.patch (type-ahead search) Status in nautilus package in Ubuntu: Won't Fix Bug description: Nautilus dropped the popular type-ahead search feature years ago. Ubuntu has been carrying a patch to revert that change. See bug 1164016 for the original LP bug and patch proposal. Nautilus is now under very active development. During the 3.22 cycle, that patch needed to be rebased. I tried to do it and what I came up with caused a crash (it didn't really crash for me, but ricotz and some others experienced it) and the first letter typed activated type- ahead search but the first letter was dropped. In other words, you would need to type "ddow" to activate the Downloads folder instead of just "dow" like in previous releases. (LP: #1635988) I did that rebase in October 2016 and no one has stepped up then to improve the patch. The Nautilus maintainer csoriano has said that the slots and views changed significantly during 3.22 and will likely be refactored more in the future. If there's no one available to maintain the patch, unfortunately, we'll eventually have to drop the patch to not be stuck on an ancient version of Nautilus. I am proposing that we do this at the start of the 17.10 development cycle. This gives 6 months for a developer to step up and try to fix the patch and 12 months before 18.04 LTS. Other Items === - For better performance with the built-in search, we need to reconsider avoiding tracker in Unity (LP: #176) - There is an option in Preferences for users to disable searching in subfolders. I don't think we want to do that by default but maybe it can help some people. The current Nautilus 3.24 packaging is in the GNOME3 Staging PPA with this patch now disabled. https://launchpad.net/~gnome3-team/+archive/ubuntu/gnome3-staging/+packages?field.series_filter=zesty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/181/+subscriptions -- Mailing list: https://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 1726874] Re: gnome-shell crashed with signal 5 in _XIOError()
*** This bug is a duplicate of bug 1556601 *** https://bugs.launchpad.net/bugs/1556601 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1556601, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1726874/+attachment/4991247/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1726874/+attachment/4991249/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1726874/+attachment/4991253/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1726874/+attachment/4991254/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1726874/+attachment/4991255/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1726874/+attachment/4991256/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1726874/+attachment/4991257/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1556601 gnome-shell crashed with signal 5 in _XIOError() from _XReply() from XSync() ["Connection to xwayland lost"] ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- 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/1726874 Title: gnome-shell crashed with signal 5 in _XIOError() Status in gnome-shell package in Ubuntu: New Bug description: Asus G752VS Ubuntu 17.10 X.org session ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.1-0ubuntu4 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: GNOME-Greeter:GNOME Date: Tue Oct 24 15:39:53 2017 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: InstallationDate: Installed on 2017-10-24 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcCmdline: /usr/bin/gnome-shell Signal: 5 SourcePackage: gnome-shell StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libmutter-1.so.0 _XIOError () from /usr/lib/x86_64-linux-gnu/libX11.so.6 _XReply () from /usr/lib/x86_64-linux-gnu/libX11.so.6 XSync () from /usr/lib/x86_64-linux-gnu/libX11.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 Title: gnome-shell crashed with signal 5 in _XIOError() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1726874/+subscriptions -- Mailing list: https://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 1711534] Re: Application list cluttered on a fresh Artful installation
Ubuntu 17.10 does not include fcitx by default (even on the live ISO) or Onboard or ImageMagick. Language Support is still included because of LP: #1631750 We haven't discussed the Input Methods app yet, but maybe that's not needed in 18.04… ** Package changed: ubuntu-meta (Ubuntu) => gnome-menus (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-menus in Ubuntu. https://bugs.launchpad.net/bugs/1711534 Title: Application list cluttered on a fresh Artful installation Status in gnome-menus package in Ubuntu: Confirmed Bug description: GNOME Shell application list contains many rarely-used and sometimes redundant app icons like: * 3 different icons for fcitx * 2 icons for OnBoard (OnBoard settings are accessible from OnBoard itself) * ImageMagick (Most probably rarely used, especially when there's also EOG) * Language Support, Input Method (There's a language panel in gnome-control-center, so this looks like a unity-control-center leftover) Because of that, the application list is 3 pages long, making other apps unnecessarily hard to find. One way to solve that would be to pack rarely-used, but still useful stuff into GNOME's Sundry app folder. Completely redundant icons can probably be just removed. Original suggestion: https://didrocks.fr/2017/08/03/ubuntu-- guadec-2017-and-plans-for-gnome-shell-migration/#comment-3455664382 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-menus/+bug/1711534/+subscriptions -- Mailing list: https://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 1726744] Re: package libsane1 1.0.27-1~experimental2ubuntu1 failed to install/upgrade: Versuch, gemeinsam benutztes »/lib/udev/hwdb.d/20-sane.hwdb« zu überschreiben, welches ve
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: sane-backends (Ubuntu) Status: New => Confirmed -- 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/1726744 Title: package libsane1 1.0.27-1~experimental2ubuntu1 failed to install/upgrade: Versuch, gemeinsam benutztes »/lib/udev/hwdb.d/20-sane.hwdb« zu überschreiben, welches verschieden von anderen Instanzen des Paketes libsane1:i386 ist Status in sane-backends package in Ubuntu: Confirmed Bug description: lsb_release -rd: Description: Ubuntu 17.10 Release: 17.10 apt-cache policy libsane1: Installiert: 1.0.27-1~experimental2ubuntu1 Installationskandidat: 1.0.27-1~experimental2ubuntu1 Versionstabelle: *** 1.0.27-1~experimental2ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu artful/main amd64 Packages 100 /var/lib/dpkg/status What I expected to happen: A normal installation What happened instead: Following Errormessage: "package libsane1 1.0.27-1~experimental2ubuntu1 failed to install/upgrade: Versuch, gemeinsam benutztes »/lib/udev/hwdb.d/20-sane.hwdb« zu überschreiben, welches verschieden von anderen Instanzen des Paketes libsane1:i386 ist" ProblemType: Package DistroRelease: Ubuntu 17.10 Package: libsane1 1.0.27-1~experimental2ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 Date: Mon Oct 23 16:52:45 2017 ErrorMessage: Versuch, gemeinsam benutztes »/lib/udev/hwdb.d/20-sane.hwdb« zu überschreiben, welches verschieden von anderen Instanzen des Paketes libsane1:i386 ist Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-2ubuntu1 RelatedPackageVersions: dpkg 1.18.24ubuntu1 apt 1.5 SourcePackage: sane-backends Title: package libsane1 1.0.27-1~experimental2ubuntu1 failed to install/upgrade: Versuch, gemeinsam benutztes »/lib/udev/hwdb.d/20-sane.hwdb« zu überschreiben, welches verschieden von anderen Instanzen des Paketes libsane1:i386 ist 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/1726744/+subscriptions -- Mailing list: https://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 1707352] Re: the change from libsane to libsane1 broke many (all?) 3rd party plug-ins for sane
I called the workaround "ugly", because it bypasses the apt package management routines and there might be no easy way back when a working upgrade is released. -- 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/1707352 Title: the change from libsane to libsane1 broke many (all?) 3rd party plug- ins for sane Status in sane-backends package in Ubuntu: Fix Committed Status in sane-backends source package in Artful: Fix Committed Status in sane-backends package in Debian: New Bug description: Impact == 1) The Debian maintainer renamed libsane to libsane1-experimental "to match with the soname". This apparently fixes a Lintian warning, but makes installing 3rd-party plug-ins hard, as they typically depend on "libsane", not on "libsane1". The first try to add a "Provides: libsane" to libsane1 (which created a virtual package) didn't make drivers installable that claim to depend on a minimum version of libsane as virtual packages are ignored in this case. 2) The soname change might be justified by the new version breaking (several? most?) 3rd party plug-ins even if the library version number doesn't indicate any bigger change than any ordinary new version of the library - which might indicate that this phenomenon might be an upstream bug. libsane 1.0.25 in zesty includes libsane.so.1.25 libsane1 1.0.27 in artful includes libsane.so.1.27 It is to note that depending on the manufacturer for many old scanners there won't be new versions of the plug-ins that are recompiled like this. Test Case = Visit http://support.epson.net/linux/en/iscan_c.html Download the amd64 deb .tar.gz Unzip it. Install the iscan .deb from the core folder. It won't install before this SRU because it Depends: libsane Regression Potential The fix here was proposed to the Debian maintainer in July but there's been virtually zero response on it. In the meantime the workaround that was proposed initially has started to result in automatically uninstalling gtk - which makes the system basically useless. It doesn't seem like adding the Provides will make things any worse for third-party drivers but it has a goodme chance of making things better for some. Impossibility of workarounds Just installing an old version of libsane is impossible as it uninstalls libgtk (which depends on libsane1 which conflicts with libsane) making the system basically useless. Original Bug Report === I don't know if that can be prevented in the long run. But both brscan (for my brother scanner) and iscan (for my epson scanners) have been broken by the change from libsane to libsane1. For iscan I have unpackaged the debian package, changed the dependency it contains from libsane to libsane1 and installed the changed package. But even then my epson scanners no more work leaving me without any scanner => Reporting a bug. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: libsane1 1.0.27-1~experimental1ubuntu2 Uname: Linux 4.13.0-041300rc2-lowlatency x86_64 ApportVersion: 2.20.6-0ubuntu4 Architecture: amd64 Date: Sat Jul 29 08:38:15 2017 EcryptfsInUse: Yes 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/1707352/+subscriptions -- Mailing list: https://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 1716341] Re: Settings for external monitor are deleted after reboot, suspension, log out
** Tags added: regression-release -- 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/1716341 Title: Settings for external monitor are deleted after reboot, suspension, log out Status in gnome-control-center: Fix Released Status in gnome-shell package in Ubuntu: Triaged Status in gnome-shell source package in Artful: Triaged Bug description: New Gnome Settings on Ubuntu 17.10 Settings for external monitor are working but after reboot/suspension /log-out log-in, the system will not remember the setup. Example: 1- open Gnome Settings and select "Devices → Displays" 2- set the external monitor as "Single Display" and click on "Apply" 3- log-out After log-in the laptop monitor will be set as default instead of the external monitor. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1716341/+subscriptions -- Mailing list: https://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 1726877] Re: gnome-shell crashed with signal 5
*** This bug is a duplicate of bug 1505409 *** https://bugs.launchpad.net/bugs/1505409 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1505409, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1726877/+attachment/4991268/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1726877/+attachment/4991270/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1726877/+attachment/4991273/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1726877/+attachment/4991274/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1726877/+attachment/4991275/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1726877/+attachment/4991276/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1726877/+attachment/4991277/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1505409 gnome-shell crashed with SIGTRAP in x_io_error() from _XIOError() from _XEventsQueued() from XPending() from gdk_check_xpending() ["Connection to xwayland lost"] ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- 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/1726877 Title: gnome-shell crashed with signal 5 Status in gnome-shell package in Ubuntu: New Bug description: crash gnome shell ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.1-0ubuntu4 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: GNOME-Greeter:GNOME Date: Thu Oct 19 08:55:16 2017 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: InstallationDate: Installed on 2017-10-19 (5 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANGUAGE=es_PE:es PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_PE.UTF-8 SHELL=/bin/false Signal: 5 SourcePackage: gnome-shell StacktraceTop: () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0 _XIOError () at /usr/lib/x86_64-linux-gnu/libX11.so.6 _XEventsQueued () at /usr/lib/x86_64-linux-gnu/libX11.so.6 XPending () at /usr/lib/x86_64-linux-gnu/libX11.so.6 () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 Title: gnome-shell crashed with signal 5 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1726877/+subscriptions -- Mailing list: https://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 1726881] Re: cups-browsed crashed with SIGSEGV in dbus_watch_handle()
*** This bug is a duplicate of bug 1726869 *** https://bugs.launchpad.net/bugs/1726869 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1726869, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1726881/+attachment/4991304/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1726881/+attachment/4991308/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1726881/+attachment/4991318/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1726881/+attachment/4991320/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1726881/+attachment/4991321/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1726881/+attachment/4991322/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1726881/+attachment/4991323/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1726869 ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups-filters in Ubuntu. https://bugs.launchpad.net/bugs/1726881 Title: cups-browsed crashed with SIGSEGV in dbus_watch_handle() Status in cups-filters package in Ubuntu: New Bug description: . ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: cups-browsed 1.17.9-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 Date: Tue Oct 24 11:55:49 2017 ExecutablePath: /usr/sbin/cups-browsed ExecutableTimestamp: 1507223021 InstallationDate: Installed on 2016-11-15 (342 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) Lpstat: device for GHPF4Q2: hp:/net/HP_LaserJet_P3010_Series?zc=GHPF4Quad2 device for HPF4Q2: hp:/net/HP_LaserJet_P3010_Series?zc=HPF4Quad2 device for Ricoh-Aficio-MP-C4502: ipp://130.229.43.212:631/ipp MachineType: LENOVO 30B8S09D00 Papersize: a4 PpdFiles: HPF4Q2: HP LaserJet P3010 Series Postscript (recommended) GHPF4Q2: HP LaserJet P3010 Series Postscript (recommended) Ricoh-Aficio-MP-C4502: Ricoh Aficio MP C4502 PS ProcAttrCurrent: /usr/sbin/cups-browsed (enforce) ProcCmdline: /usr/sbin/cups-browsed ProcCwd: / ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic.efi.signed root=UUID=9b31024e-745b-49e2-b125-83271dca97b0 ro quiet splash noapic vt.handoff=7 SegvAnalysis: Segfault happened at: 0x7fc0f5edab5c : jmpq *%rax PC (0x7fc0f5edab5c) ok source "*%rax" (0x2f3133363a74736f) not located in a known VMA region (needed readable region)! SegvReason: reading unknown VMA Signal: 11 SourcePackage: cups-filters StacktraceTop: dbus_watch_handle () from /lib/x86_64-linux-gnu/libdbus-1.so.3 ?? () from /usr/lib/x86_64-linux-gnu/libavahi-glib.so.1 g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: cups-browsed crashed with SIGSEGV in dbus_watch_handle() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 06/20/2016 dmi.bios.vendor: LENOVO dmi.bios.version: S02KT29A dmi.board.name: 1031 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.type: 7 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrS02KT29A:bd06/20/2016:svnLENOVO:pn30B8S09D00:pvrThinkStationP910:rvnLENOVO:rn1031:rvrNODPK:cvnLENOVO:ct7:cvrNone: dmi.product.family: ThinkStation P910 dmi.product.name: 30B8S09D00 dmi.product.version: ThinkStation P910 dmi.sys.vendor: LENOVO upstart.cups-browsed.override: manual To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1726881/+subscriptions -- Mailing list: https://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 1726882] Re: unity-greeter crashed with SIGABRT in g_assertion_message()
*** This bug is a duplicate of bug 1625282 *** https://bugs.launchpad.net/bugs/1625282 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1625282, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1726882/+attachment/4991325/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1726882/+attachment/4991327/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1726882/+attachment/4991330/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1726882/+attachment/4991331/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1726882/+attachment/4991332/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1726882/+attachment/4991333/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1726882/+attachment/4991334/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1625282 ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-greeter in Ubuntu. https://bugs.launchpad.net/bugs/1726882 Title: unity-greeter crashed with SIGABRT in g_assertion_message() Status in unity-greeter package in Ubuntu: New Bug description: After upgrading to 17.10. It looped and did not start. I had to open a console session and run dpkg --configure -a This, after trying to sudo apt-get purge nvidia* ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: unity-greeter 17.10.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 Date: Mon Oct 23 18:29:09 2017 ExecutablePath: /usr/sbin/unity-greeter InstallationDate: Installed on 2017-08-28 (56 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) ProcCmdline: /usr/sbin/unity-greeter ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/false Signal: 6 SourcePackage: unity-greeter StacktraceTop: g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 Title: unity-greeter crashed with SIGABRT in g_assertion_message() UpgradeStatus: Upgraded to artful on 2017-10-23 (0 days ago) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-greeter/+bug/1726882/+subscriptions -- Mailing list: https://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 1726888] [NEW] Dock right-click window list pointlessly moved to "All Windows" submenu
Public bug reported: In Ubuntu 17.10, when I right click on an application in the dock, rather than seeing a list of all my windows for that application in the menu that pops up, that list has now been relegated to an "All Windows" submenu. This is pointless and stupid. It adds two extra actions -- moving the mouse to the "All Windows" menu item and clicking on it -- every time I want to switch to a different application window using the dock. I can't see any justification for this change whatsoever. Please bring back the old behavior. (Also, the "All Windows" submenu now shows pictures of windows as well as window titles. The presence of those pictures should be configurable (at least). I don't need to see pictures of my windows, the titles were always sufficient, took up less space, and were quicker to parse and navigate than pictures are.) ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.1-0ubuntu4 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 24 10:28:06 2017 DisplayManager: gdm3 InstallationDate: Installed on 2017-05-19 (157 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: gnome-shell UpgradeStatus: Upgraded to artful on 2017-10-20 (3 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful regression-release wayland-session -- 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/1726888 Title: Dock right-click window list pointlessly moved to "All Windows" submenu Status in gnome-shell package in Ubuntu: New Bug description: In Ubuntu 17.10, when I right click on an application in the dock, rather than seeing a list of all my windows for that application in the menu that pops up, that list has now been relegated to an "All Windows" submenu. This is pointless and stupid. It adds two extra actions -- moving the mouse to the "All Windows" menu item and clicking on it -- every time I want to switch to a different application window using the dock. I can't see any justification for this change whatsoever. Please bring back the old behavior. (Also, the "All Windows" submenu now shows pictures of windows as well as window titles. The presence of those pictures should be configurable (at least). I don't need to see pictures of my windows, the titles were always sufficient, took up less space, and were quicker to parse and navigate than pictures are.) ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.1-0ubuntu4 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 24 10:28:06 2017 DisplayManager: gdm3 InstallationDate: Installed on 2017-05-19 (157 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: gnome-shell UpgradeStatus: Upgraded to artful on 2017-10-20 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1726888/+subscriptions -- Mailing list: https://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 1724699] Re: nautilus crashed with SIGSEGV in nautilus_file_get_search_fts_snippet()
Launchpad doesn't support the new gitlab instance of Nautilus bugtracker, so here's the link: https://gitlab.gnome.org/GNOME/nautilus/issues/82 -- 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/1724699 Title: nautilus crashed with SIGSEGV in nautilus_file_get_search_fts_snippet() Status in nautilus package in Ubuntu: Confirmed Bug description: Searched something in nautilus and tried to drag an item from the list to a folder in the list and this crash showed up. ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: nautilus 1:3.26.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Oct 18 21:49:08 2017 EcryptfsInUse: Yes ExecutablePath: /usr/bin/nautilus InstallationDate: Installed on 2015-09-28 (750 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) ProcCmdline: /usr/bin/nautilus --gapplication-service ProcEnviron: XDG_RUNTIME_DIR= SHELL=/bin/bash LANGUAGE=en_PH:en PATH=(custom, user) LANG=en_PH.UTF-8 SegvAnalysis: Segfault happened at: 0x55c069d25660 : mov0x18(%rdi),%rax PC (0x55c069d25660) ok source "0x18(%rdi)" (0x0018) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: nautilus StacktraceTop: nautilus_file_get_search_fts_snippet () () () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 g_hash_table_foreach () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 Title: nautilus crashed with SIGSEGV in nautilus_file_get_search_fts_snippet() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker fuse kismet libvirt libvirtd lp lpadmin lxd mail mythtv netdev plugdev sambashare sbuild scanner sudo video To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1724699/+subscriptions -- Mailing list: https://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 1724699] Re: nautilus crashed with SIGSEGV in nautilus_file_get_search_fts_snippet()
Hello Seb, I'm sorry if I'm not so tech-savvy, but I think the bug has already been reported here (as you surely already know) : https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1724699 I tried to follow the instructions but I see here https://bugzilla.gnome.org/enter_bug.cgi?classification=__all that Nautilus has been moved to GitLab. I don't really understand what I'm supposed to do. On Mon, Oct 23, 2017 at 11:12 PM, Sebastien Bacher wrote: > Thank you for taking the time to report this bug and helping to make > Ubuntu better. The issue you are reporting is an upstream one and it > would be nice if somebody having it could send the bug to the developers > of the software by following the instructions at > https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please > tell us the number of the upstream bug (or the link), so we can add a > bugwatch that will inform us about its status. Thanks in advance. > > ** Information type changed from Private to Public > > ** Changed in: nautilus (Ubuntu) >Importance: Medium => High > > -- > You received this bug notification because you are subscribed to a > duplicate bug report (1725438). > https://bugs.launchpad.net/bugs/1724699 > > Title: > nautilus crashed with SIGSEGV in > nautilus_file_get_search_fts_snippet() > > Status in nautilus package in Ubuntu: > Confirmed > > Bug description: > Searched something in nautilus and tried to drag an item from the list > to a folder in the list and this crash showed up. > > ProblemType: Crash > DistroRelease: Ubuntu 17.10 > Package: nautilus 1:3.26.0-0ubuntu1 > ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 > Uname: Linux 4.13.0-16-generic x86_64 > ApportVersion: 2.20.7-0ubuntu3 > Architecture: amd64 > CurrentDesktop: GNOME > Date: Wed Oct 18 21:49:08 2017 > EcryptfsInUse: Yes > ExecutablePath: /usr/bin/nautilus > InstallationDate: Installed on 2015-09-28 (750 days ago) > InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) > ProcCmdline: /usr/bin/nautilus --gapplication-service > ProcEnviron: >XDG_RUNTIME_DIR= >SHELL=/bin/bash >LANGUAGE=en_PH:en >PATH=(custom, user) >LANG=en_PH.UTF-8 > SegvAnalysis: >Segfault happened at: 0x55c069d25660 > : > mov0x18(%rdi),%rax >PC (0x55c069d25660) ok >source "0x18(%rdi)" (0x0018) not located in a known VMA region > (needed readable region)! >destination "%rax" ok > SegvReason: reading NULL VMA > Signal: 11 > SourcePackage: nautilus > StacktraceTop: >nautilus_file_get_search_fts_snippet () >() >() at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 >g_hash_table_foreach () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 >() at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 > Title: nautilus crashed with SIGSEGV in nautilus_file_get_search_fts_ > snippet() > UpgradeStatus: No upgrade log present (probably fresh install) > UserGroups: adm cdrom dip docker fuse kismet libvirt libvirtd lp lpadmin > lxd mail mythtv netdev plugdev sambashare sbuild scanner sudo video > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/ > 1724699/+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/1724699 Title: nautilus crashed with SIGSEGV in nautilus_file_get_search_fts_snippet() Status in nautilus package in Ubuntu: Confirmed Bug description: Searched something in nautilus and tried to drag an item from the list to a folder in the list and this crash showed up. ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: nautilus 1:3.26.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Oct 18 21:49:08 2017 EcryptfsInUse: Yes ExecutablePath: /usr/bin/nautilus InstallationDate: Installed on 2015-09-28 (750 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) ProcCmdline: /usr/bin/nautilus --gapplication-service ProcEnviron: XDG_RUNTIME_DIR= SHELL=/bin/bash LANGUAGE=en_PH:en PATH=(custom, user) LANG=en_PH.UTF-8 SegvAnalysis: Segfault happened at: 0x55c069d25660 : mov0x18(%rdi),%rax PC (0x55c069d25660) ok source "0x18(%rdi)" (0x0018) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: nautilus StacktraceTop: nautilus_file_get_search_fts_snippet () () () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 g_hash_table_foreach () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 Title: nautilus crashed with SIGSEGV in nautilus_file_get_search_fts_snippet() UpgradeStatus: No upgrade log present (probab
[Desktop-packages] [Bug 1713803] Re: replacement of resolvconf with systemd needs integration
** Changed in: cloud-initramfs-tools (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pppconfig in Ubuntu.
https://bugs.launchpad.net/bugs/1713803
Title:
replacement of resolvconf with systemd needs integration
Status in android-androresolvd package in Ubuntu:
Triaged
Status in avahi package in Ubuntu:
Triaged
Status in bind9 package in Ubuntu:
Triaged
Status in cloud-init package in Ubuntu:
Incomplete
Status in cloud-initramfs-tools package in Ubuntu:
Invalid
Status in dhcpcd5 package in Ubuntu:
New
Status in dibbler package in Ubuntu:
Won't Fix
Status in dnscrypt-proxy package in Ubuntu:
New
Status in dnsmasq package in Ubuntu:
New
Status in dnssec-trigger package in Ubuntu:
New
Status in fetchmail package in Ubuntu:
New
Status in freedombox-setup package in Ubuntu:
New
Status in initramfs-tools package in Ubuntu:
Confirmed
Status in isc-dhcp package in Ubuntu:
Fix Released
Status in ndisc6 package in Ubuntu:
New
Status in netscript-2.4 package in Ubuntu:
Won't Fix
Status in open-iscsi package in Ubuntu:
New
Status in openvpn package in Ubuntu:
New
Status in postfix package in Ubuntu:
New
Status in pppconfig package in Ubuntu:
New
Status in pump package in Ubuntu:
New
Status in resolvconf package in Ubuntu:
Invalid
Status in sendmail package in Ubuntu:
New
Status in squid3 package in Ubuntu:
New
Status in systemd package in Ubuntu:
Invalid
Status in unbound package in Ubuntu:
New
Status in vpnc package in Ubuntu:
New
Status in vpnc-scripts package in Ubuntu:
New
Status in whereami package in Ubuntu:
Triaged
Bug description:
There is a plan to remove resolvconf from the Ubuntu Server image.
resolvconf integrated with other parts of the system in 2 ways:
* hooks invoked on change (/etc/resolvconf/update.d/)
* resolvconf tool (invoked with -a and -d or -u)
Packages which install files into /etc/resolvconf/update.d are:
- dnsmasq: This may be mostly covered by systemd-resolved itself (the dns
caching path).
- resolvconf: This probably isn't necessary in systemd-resolved path.
- unbound: This is another "validating, recursive, caching DNS resolver".
The list of Depends/Suggests/Recommends on resolvconf.
# for pkg in $(apt-cache rdepends resolvconf | grep -v openreso | grep -v
Reverse); do out=$(apt-cache show $pkg | grep resolvconf); src=$(apt-cache show
$pkg | awk '$1 == "Source:" { print $2 }'); [ -n "$src" ] || src=$pkg; case
"$out" in Depends:*resolvconf) r=depends;; Suggests:*) r=suggests;;
Recommends:*) r=recommends;; esac; echo "$r $src"; done | sort -u
depends android-androresolvd
recommends avahi
recommends dhcpcd5
recommends dibbler
recommends ndisc6
recommends whereami
suggests bind9
suggests dnscrypt-proxy
suggests dnsmasq
suggests dnssec-trigger
suggests fetchmail
suggests freedombox-setup
suggests isc-dhcp
suggests netscript-2.4
suggests openvpn
suggests postfix
suggests pppconfig
suggests pump
suggests resolvconf
suggests sendmail
suggests squid3
suggests vpnc
suggests vpnc-scripts
ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: systemd 234-2ubuntu9
ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
Uname: Linux 4.12.0-11-generic x86_64
ApportVersion: 2.20.6-0ubuntu7
Architecture: amd64
Date: Tue Aug 29 18:53:50 2017
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
LANG=C.UTF-8
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.12.0-11-generic
root=UUID=f897b32a-eacf-4191-9717-844918947069 ro quiet splash vt.handoff=7
SourcePackage: systemd
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.vendor: Intel Corporation
Related bugs:
* bug 1698181: Switch to netplan renderer in Artful
* bug 1714308: dns does not work in initramfs after configure_networking
* bug 1717983 replacement of isc-dhcp-client with with systemd-networkd for
dhclient needs integration
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/android-androresolvd/+bug/1713803/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
