[Desktop-packages] [Bug 1921651] Re: colon in name causes gvfs hang when copying to phone
Also: if the colon is in the name of a directory you are copying, the directory gets created with the colon in the name, but any attempt to put files in it hangs. Deleting the colon-named things via Files does seem to work, though. And transferring files with spaces, dashes, and umlauts in the names works fine, too. It's just the colon that causes trouble. -- 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/1921651 Title: colon in name causes gvfs hang when copying to phone Status in gvfs package in Ubuntu: New Bug description: A colon in a file or directory name causes the operation to hang when copying to a phone via ptp. To reproduce: On android phone: 1) plug usb cable between phone and computer 2) Go to settings. Search for USB. Click on "Standard USB configuration". (Alternately, notice mystery status card at very bottom of notifications saying "Android system - charging over USB, click for options", and click on it.) 3) Select PTP. Then on Ubuntu 20.04 (and probably other recent vintages as well): 0) observe your phone popping up in dock and in Files 1) cp good.mp3 bad:.mp3 2) xdg-open . 3) In dock or Files, also open your phone 4) drag good.mp3 to your phone, note that it succeeds 5) drag bad:.mpd to your phone, note that it hangs ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gvfs 1.44.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-48.54~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-48-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Mar 28 15:28:32 2021 InstallationDate: Installed on 2020-10-17 (162 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gvfs UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1921651/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1921651] [NEW] colon in name causes gvfs hang when copying to phone
Public bug reported: A colon in a file or directory name causes the operation to hang when copying to a phone via ptp. To reproduce: On android phone: 1) plug usb cable between phone and computer 2) Go to settings. Search for USB. Click on "Standard USB configuration". (Alternately, notice mystery status card at very bottom of notifications saying "Android system - charging over USB, click for options", and click on it.) 3) Select PTP. Then on Ubuntu 20.04 (and probably other recent vintages as well): 0) observe your phone popping up in dock and in Files 1) cp good.mp3 bad:.mp3 2) xdg-open . 3) In dock or Files, also open your phone 4) drag good.mp3 to your phone, note that it succeeds 5) drag bad:.mpd to your phone, note that it hangs ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gvfs 1.44.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-48.54~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-48-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Mar 28 15:28:32 2021 InstallationDate: Installed on 2020-10-17 (162 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gvfs UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gvfs (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1921651 Title: colon in name causes gvfs hang when copying to phone Status in gvfs package in Ubuntu: New Bug description: A colon in a file or directory name causes the operation to hang when copying to a phone via ptp. To reproduce: On android phone: 1) plug usb cable between phone and computer 2) Go to settings. Search for USB. Click on "Standard USB configuration". (Alternately, notice mystery status card at very bottom of notifications saying "Android system - charging over USB, click for options", and click on it.) 3) Select PTP. Then on Ubuntu 20.04 (and probably other recent vintages as well): 0) observe your phone popping up in dock and in Files 1) cp good.mp3 bad:.mp3 2) xdg-open . 3) In dock or Files, also open your phone 4) drag good.mp3 to your phone, note that it succeeds 5) drag bad:.mpd to your phone, note that it hangs ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gvfs 1.44.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-48.54~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-48-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Mar 28 15:28:32 2021 InstallationDate: Installed on 2020-10-17 (162 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gvfs UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1921651/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1766938] Re: gnome-shell crashed in standard_pict_format_for_depth()
I no longer have access to the system in question, and haven't seen it anywhere else, may as well close as abandoned. -- 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/1766938 Title: gnome-shell crashed in standard_pict_format_for_depth() Status in gnome-shell package in Ubuntu: Incomplete Status in mutter package in Ubuntu: Incomplete Bug description: I have a fleet of Dell T7500's, a few Dell 3620's, a Skull Canyon, and a Hades Canyon, and a few other odds and ends, running a mix of ubuntu 16.04 and 17.10. On one of the T7500 ubuntu 17.10 boxes (nvidia 340 package, Quadro K5000 card), I did sudo "do-release-upgrade -d". Went fine, but on reboot, the desktop would come up for about ten seconds, then the system would shut down. Did systemctl set-default multi-user.target then removed all traces of the proprietary driver with sudo apt remove --purge nvidia-340 nvidia-opencl-icd-340 nvidia-settings nvidia-384 nvidia-opencl-icd-384 nvidia-prime libcuda1-340 and rebooted. Logging in to the console and running 'startx' reproduces the problem reliably, and does not shut down the system. Installing lwm, and a .xinitrc that started an xterm, let startx succeed, and the system was stable running firefox, so it's not an obvious graphics problem. /var/log/syslog says Apr 25 09:59:41 rbb-ubu1710-3 org.gnome.Shell.desktop[3936]: ** Apr 25 09:59:41 rbb-ubu1710-3 org.gnome.Shell.desktop[3936]: mutter:ERROR:x11/iconcache.c:303:standard_pict_format_for_depth: code should not be reached Apr 25 09:59:41 rbb-ubu1710-3 org.gnome.Shell.desktop[3936]: == Stack trace for context 0x556d30f3c4c0 == Apr 25 09:59:41 rbb-ubu1710-3 dbus-daemon[690]: [system] Successfully activated service 'org.freedesktop.fwupd' Apr 25 09:59:41 rbb-ubu1710-3 systemd[1]: Started Firmware update daemon. Apr 25 09:59:42 rbb-ubu1710-3 PackageKit: get-updates transaction /2379_acbceaca from uid 1000 finished with success after 1175ms Apr 25 09:59:42 rbb-ubu1710-3 gnome-session[3605]: gnome-session-binary[3605]: WARNING: Application 'org.gnome.Shell.desktop' killed by signal 6 Apr 25 09:59:42 rbb-ubu1710-3 gnome-session[3605]: gnome-session-binary[3605]: WARNING: App 'org.gnome.Shell.desktop' respawning too quickly Apr 25 09:59:42 rbb-ubu1710-3 gnome-session[3605]: gnome-session-binary[3605]: CRITICAL: We failed, but the fail whale is dead. Sorry Apr 25 09:59:42 rbb-ubu1710-3 gnome-session-binary[3605]: Unrecoverable failure in required component org.gnome.Shell.desktop Apr 25 09:59:42 rbb-ubu1710-3 gnome-session-binary[3605]: WARNING: Application 'org.gnome.Shell.desktop' killed by signal 6 Apr 25 09:59:42 rbb-ubu1710-3 gnome-session-binary[3605]: WARNING: App 'org.gnome.Shell.desktop' respawning too quickly Apr 25 09:59:42 rbb-ubu1710-3 gnome-session-binary[3605]: CRITICAL: We failed, but the fail whale is dead. Sorry ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.1-0ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 Date: Wed Apr 25 10:06:55 2018 DisplayManager: GsettingsChanges: b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2018-01-04 (111 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170918) SourcePackage: gnome-shell UpgradeStatus: Upgraded to bionic on 2018-04-24 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1766938/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1865870] Re: [nvidia] xorg via gdm-x-session fails to start with "Cannot run in framebuffer mode. Please specify busIDs for all framebuffer devices"
I saw this on an ubuntu 20.04 alpha system when I did 'ubuntu-drivers install' to get drivers for my gtx 1080. Reinstalling ubuntu 20.04 final made the problem vanish (whew). -- 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/1865870 Title: [nvidia] xorg via gdm-x-session fails to start with "Cannot run in framebuffer mode. Please specify busIDs for all framebuffer devices" Status in nvidia-graphics-drivers-440 package in Ubuntu: New Status in xorg-server package in Ubuntu: New Bug description: After performing apt dist-upgrade and rebooting, plymouth doesn't run in full resolution and the graphical session won't start. The system is stuck on a blinking cursor. A full log file is attached. Here is the error: Mär 03 13:04:13 /usr/lib/gdm3/gdm-x-session[1753]: (EE) Screen 0 deleted because of no matching config section. Mär 03 13:04:13 /usr/lib/gdm3/gdm-x-session[1753]: (II) UnloadModule: "modesetting" Mär 03 13:04:13 /usr/lib/gdm3/gdm-x-session[1753]: (EE) Screen 1 deleted because of no matching config section. Mär 03 13:04:13 /usr/lib/gdm3/gdm-x-session[1753]: (II) UnloadModule: "fbdev" Mär 03 13:04:13 /usr/lib/gdm3/gdm-x-session[1753]: (II) UnloadSubModule: "fbdevhw" Mär 03 13:04:13 /usr/lib/gdm3/gdm-x-session[1753]: (EE) Screen 1 deleted because of no matching config section. Mär 03 13:04:13 /usr/lib/gdm3/gdm-x-session[1753]: (II) UnloadModule: "vesa" Mär 03 13:04:13 /usr/lib/gdm3/gdm-x-session[1753]: (EE) Mär 03 13:04:13 /usr/lib/gdm3/gdm-x-session[1753]: Fatal server error: Mär 03 13:04:13 /usr/lib/gdm3/gdm-x-session[1753]: (EE) Cannot run in framebuffer mode. Please specify busIDsfor all framebuffer devices Interestingly, pressing Ctrl+Alt+F1 when the system is stuck successfully starts the XServer and brings up the login screen. While I experience some font rendering issues, most things seem to work fine after that. lsb_release -rd Description: Ubuntu Focal Fossa (development branch) Release: 20.04 uname -a Linux 5.4.0-14-generic #17-Ubuntu SMP Thu Feb 6 22:47:59 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux The system is a Dell G5 15 5590 laptop using dual intel/nvidia rtx graphics: lshw -c video *-display Beschreibung: VGA compatible controller Produkt: TU106M [GeForce RTX 2060 Mobile] Hersteller: NVIDIA Corporation Physische ID: 0 Bus-Informationen: pci@:01:00.0 Version: a1 Breite: 64 bits Takt: 33MHz Fähigkeiten: pm msi pciexpress vga_controller bus_master cap_list rom Konfiguration: driver=nvidia latency=0 Ressourcen: irq:165 memory:ec00-ecff memory:c000-cfff memory:d000-d1ff ioport:4000(Größe=128) memory:ed00-ed07 *-display Beschreibung: VGA compatible controller Produkt: UHD Graphics 630 (Mobile) Hersteller: Intel Corporation Physische ID: 2 Bus-Informationen: pci@:00:02.0 Version: 00 Breite: 64 bits Takt: 33MHz Fähigkeiten: pciexpress msi pm vga_controller bus_master cap_list rom Konfiguration: driver=i915 latency=0 Ressourcen: irq:152 memory:eb00-ebff memory:8000-8fff ioport:5000(Größe=64) memory:c-d To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-440/+bug/1865870/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1849873] Re: Cannot compile programs that use gtk.h and -Werror
Filed https://gitlab.gnome.org/GNOME/gtk/issues/2221 in case it's an upstream
bug.
I'll probably regret that.
** Bug watch added: gitlab.gnome.org/GNOME/gtk/issues #2221
https://gitlab.gnome.org/GNOME/gtk/issues/2221
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gtk+2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1849873
Title:
Cannot compile programs that use gtk.h and -Werror
Status in gtk+2.0 package in Ubuntu:
New
Bug description:
To reproduce:
sudo apt install libgtk2.0-dev && echo "#include " > foo.c
&& gcc -Werror -c foo.c $(pkg-config --cflags gtk+-2.0) || echo FAIL
Should complete silently and produce foo.o, but instead, fails as
follows:
Reading package lists... Done
Building dependency tree
Reading state information... Done
libgtk2.0-dev is already the newest version (2.24.32-4ubuntu1).
libgtk2.0-dev set to manually installed.
0 upgraded, 0 newly installed, 0 to remove and 1 not upgraded.
In file included from /usr/include/gtk-2.0/gtk/gtkobject.h:37,
from /usr/include/gtk-2.0/gtk/gtkwidget.h:36,
from /usr/include/gtk-2.0/gtk/gtkcontainer.h:35,
from /usr/include/gtk-2.0/gtk/gtkbin.h:35,
from /usr/include/gtk-2.0/gtk/gtkwindow.h:36,
from /usr/include/gtk-2.0/gtk/gtkdialog.h:35,
from /usr/include/gtk-2.0/gtk/gtkaboutdialog.h:32,
from /usr/include/gtk-2.0/gtk/gtk.h:33,
from foo.c:1:
/usr/include/gtk-2.0/gtk/gtktypeutils.h:236:1: error: ‘GTypeDebugFlags’ is
deprecated [-Werror=deprecated-declarations]
236 | voidgtk_type_init (GTypeDebugFlagsdebug_flags);
| ^~~~
In file included from /usr/include/glib-2.0/gobject/gobject.h:24,
from /usr/include/glib-2.0/gobject/gbinding.h:29,
from /usr/include/glib-2.0/glib-object.h:23,
from /usr/include/glib-2.0/gio/gioenums.h:28,
from /usr/include/glib-2.0/gio/giotypes.h:28,
from /usr/include/glib-2.0/gio/gio.h:26,
from /usr/include/gtk-2.0/gdk/gdkapplaunchcontext.h:30,
from /usr/include/gtk-2.0/gdk/gdk.h:32,
from /usr/include/gtk-2.0/gtk/gtk.h:32,
from foo.c:1:
/usr/include/glib-2.0/gobject/gtype.h:679:1: note: declared here
679 | {
| ^
In file included from /usr/include/gtk-2.0/gtk/gtktoolitem.h:31,
from /usr/include/gtk-2.0/gtk/gtktoolbutton.h:30,
from /usr/include/gtk-2.0/gtk/gtkmenutoolbutton.h:30,
from /usr/include/gtk-2.0/gtk/gtk.h:126,
from foo.c:1:
/usr/include/gtk-2.0/gtk/gtktooltips.h:73:3: error: ‘GTimeVal’ is deprecated:
Use 'GDateTime' instead [-Werror=deprecated-declarations]
73 | GTimeVal last_popdown;
| ^~~~
In file included from /usr/include/glib-2.0/glib/galloca.h:32,
from /usr/include/glib-2.0/glib.h:30,
from /usr/include/glib-2.0/gobject/gbinding.h:28,
from /usr/include/glib-2.0/glib-object.h:23,
from /usr/include/glib-2.0/gio/gioenums.h:28,
from /usr/include/glib-2.0/gio/giotypes.h:28,
from /usr/include/glib-2.0/gio/gio.h:26,
from /usr/include/gtk-2.0/gdk/gdkapplaunchcontext.h:30,
from /usr/include/gtk-2.0/gdk/gdk.h:32,
from /usr/include/gtk-2.0/gtk/gtk.h:32,
from foo.c:1:
/usr/include/glib-2.0/glib/gtypes.h:551:8: note: declared here
551 | struct _GTimeVal
|^
cc1: all warnings being treated as errors
FAIL
This is a regression since ubuntu 19.04.
Noticed while building cef.
Workaround: -DGTK_DISABLE_DEPRECATED
ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: libgtk2.0-dev 2.24.32-4ubuntu1
ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
Uname: Linux 5.3.0-18-generic x86_64
ApportVersion: 2.20.11-0ubuntu8
Architecture: amd64
Date: Fri Oct 25 09:48:14 2019
InstallationDate: Installed on 2019-10-18 (7 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
SourcePackage: gtk+2.0
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1849873/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1849873] [NEW] Cannot compile programs that use gtk.h and -Werror
Public bug reported:
To reproduce:
sudo apt install libgtk2.0-dev && echo "#include " > foo.c &&
gcc -Werror -c foo.c $(pkg-config --cflags gtk+-2.0) || echo FAIL
Should complete silently and produce foo.o, but instead, fails as
follows:
Reading package lists... Done
Building dependency tree
Reading state information... Done
libgtk2.0-dev is already the newest version (2.24.32-4ubuntu1).
libgtk2.0-dev set to manually installed.
0 upgraded, 0 newly installed, 0 to remove and 1 not upgraded.
In file included from /usr/include/gtk-2.0/gtk/gtkobject.h:37,
from /usr/include/gtk-2.0/gtk/gtkwidget.h:36,
from /usr/include/gtk-2.0/gtk/gtkcontainer.h:35,
from /usr/include/gtk-2.0/gtk/gtkbin.h:35,
from /usr/include/gtk-2.0/gtk/gtkwindow.h:36,
from /usr/include/gtk-2.0/gtk/gtkdialog.h:35,
from /usr/include/gtk-2.0/gtk/gtkaboutdialog.h:32,
from /usr/include/gtk-2.0/gtk/gtk.h:33,
from foo.c:1:
/usr/include/gtk-2.0/gtk/gtktypeutils.h:236:1: error: ‘GTypeDebugFlags’ is
deprecated [-Werror=deprecated-declarations]
236 | voidgtk_type_init (GTypeDebugFlagsdebug_flags);
| ^~~~
In file included from /usr/include/glib-2.0/gobject/gobject.h:24,
from /usr/include/glib-2.0/gobject/gbinding.h:29,
from /usr/include/glib-2.0/glib-object.h:23,
from /usr/include/glib-2.0/gio/gioenums.h:28,
from /usr/include/glib-2.0/gio/giotypes.h:28,
from /usr/include/glib-2.0/gio/gio.h:26,
from /usr/include/gtk-2.0/gdk/gdkapplaunchcontext.h:30,
from /usr/include/gtk-2.0/gdk/gdk.h:32,
from /usr/include/gtk-2.0/gtk/gtk.h:32,
from foo.c:1:
/usr/include/glib-2.0/gobject/gtype.h:679:1: note: declared here
679 | {
| ^
In file included from /usr/include/gtk-2.0/gtk/gtktoolitem.h:31,
from /usr/include/gtk-2.0/gtk/gtktoolbutton.h:30,
from /usr/include/gtk-2.0/gtk/gtkmenutoolbutton.h:30,
from /usr/include/gtk-2.0/gtk/gtk.h:126,
from foo.c:1:
/usr/include/gtk-2.0/gtk/gtktooltips.h:73:3: error: ‘GTimeVal’ is deprecated:
Use 'GDateTime' instead [-Werror=deprecated-declarations]
73 | GTimeVal last_popdown;
| ^~~~
In file included from /usr/include/glib-2.0/glib/galloca.h:32,
from /usr/include/glib-2.0/glib.h:30,
from /usr/include/glib-2.0/gobject/gbinding.h:28,
from /usr/include/glib-2.0/glib-object.h:23,
from /usr/include/glib-2.0/gio/gioenums.h:28,
from /usr/include/glib-2.0/gio/giotypes.h:28,
from /usr/include/glib-2.0/gio/gio.h:26,
from /usr/include/gtk-2.0/gdk/gdkapplaunchcontext.h:30,
from /usr/include/gtk-2.0/gdk/gdk.h:32,
from /usr/include/gtk-2.0/gtk/gtk.h:32,
from foo.c:1:
/usr/include/glib-2.0/glib/gtypes.h:551:8: note: declared here
551 | struct _GTimeVal
|^
cc1: all warnings being treated as errors
FAIL
This is a regression since ubuntu 19.04.
Noticed while building cef.
Workaround: -DGTK_DISABLE_DEPRECATED
ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: libgtk2.0-dev 2.24.32-4ubuntu1
ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
Uname: Linux 5.3.0-18-generic x86_64
ApportVersion: 2.20.11-0ubuntu8
Architecture: amd64
Date: Fri Oct 25 09:48:14 2019
InstallationDate: Installed on 2019-10-18 (7 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
SourcePackage: gtk+2.0
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: gtk+2.0 (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug eoan
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gtk+2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1849873
Title:
Cannot compile programs that use gtk.h and -Werror
Status in gtk+2.0 package in Ubuntu:
New
Bug description:
To reproduce:
sudo apt install libgtk2.0-dev && echo "#include " > foo.c
&& gcc -Werror -c foo.c $(pkg-config --cflags gtk+-2.0) || echo FAIL
Should complete silently and produce foo.o, but instead, fails as
follows:
Reading package lists... Done
Building dependency tree
Reading state information... Done
libgtk2.0-dev is already the newest version (2.24.32-4ubuntu1).
libgtk2.0-dev set to manually installed.
0 upgraded, 0 newly installed, 0 to remove and 1 not upgraded.
In file included from /usr/include/gtk-2.0/gtk/gtkobject.h:37,
from /usr/include/gtk-2.0/gtk/gtkwidget.h:36,
from /usr/include/gtk-2.0/gtk/gtkcontainer.h:35,
from /usr/include/gtk-2.0/gtk/gtkbin.h:35,
from
[Desktop-packages] [Bug 1732766] Re: firefox 57 does not display fish in fishgl.com on intel 530?
Upstream bug now https://bugzilla.mozilla.org/show_bug.cgi?id=1399501 -- 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/1732766 Title: firefox 57 does not display fish in fishgl.com on intel 530? Status in Mozilla Firefox: In Progress Status in firefox package in Ubuntu: Confirmed Bug description: On my two intel graphics Ubuntu 16.04 systems (both Dell 3620's), firefox does not display any fish; it simply shows the back wall. OpenGL vendor string: Intel Open Source Technology Center OpenGL renderer string: Mesa DRI Intel(R) HD Graphics 530 (Skylake GT2) OpenGL core profile version string: 4.5 (Core Profile) Mesa 17.0.7 OpenGL core profile shading language version string: 4.50 fishgl works fine in chrome, and on other ubuntu systems here. Affects both firefox 56.0+build6-0ubuntu0.16.04.2 and 57.0+build4-0ubuntu0.16.04.5 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: firefox 57.0+build4-0ubuntu0.16.04.5 ProcVersionSignature: Ubuntu 4.4.0-98.121-generic 4.4.90 Uname: Linux 4.4.0-98-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.1-0ubuntu2.12 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: dank 1843 F...m pulseaudio /dev/snd/controlC0: dank 1843 F pulseaudio /dev/snd/controlC1: dank 1843 F pulseaudio BuildID: 20171115095126 Channel: Unavailable Date: Thu Nov 16 10:55:39 2017 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) IpRoute: default via 10.10.1.1 dev enp0s31f6 10.0.3.0/24 dev lxcbr0 proto kernel scope link src 10.0.3.1 linkdown 10.10.0.0/16 dev enp0s31f6 proto kernel scope link src 10.10.130.236 169.254.0.0/16 dev enp0s31f6 scope link metric 1000 IwConfig: lono wireless extensions. enp0s31f6 no wireless extensions. lxcbr0no wireless extensions. Locales: extensions.sqlite corrupt or missing PrefSources: prefs.js ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Profiles: Profile0 (Default) - LastVersion=57.0/20171115095126 (In use) RfKill: RunningIncompatibleAddons: False SourcePackage: firefox Themes: extensions.sqlite corrupt or missing UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: dmi.bios.date: 05/26/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.6 dmi.board.name: 09WH54 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 6 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.6:bd05/26/2016:svnDellInc.:pnPrecisionTower3620:pvr:rvnDellInc.:rn09WH54:rvrA00:cvnDellInc.:ct6:cvr: dmi.product.name: Precision Tower 3620 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1732766/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1822426] Re: 19.04 Built in Intel HDA sound is disabled upon resume
FWIW, I ran into this after updating to 19.04 from 18.04. Audio working fine with HDMI (yay) but not with back panel audio (boo) unless I ran aplay as root, e.g. sudo aplay -D sysdefault:CARD=PCH /usr/share/sounds/alsa/Front_Left.wav ps showed timidity running. 'sudo apt remove timidity; sudo killall timidity' resolved the problem. -- 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/1822426 Title: 19.04 Built in Intel HDA sound is disabled upon resume Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Incomplete Bug description: With 19.04, Intel Corporation 8 Series/C220 Series Chipset High Definition Audio Controller intermittently is not enabled when resuming from sleep. The HDMI sound device is enabled but that is not hooked up on my system. New with 19.04, when sound works after resume, an icon labeled "Built in Audio Stereo" appears during the resume process. Unsure if this is related, but sound seems to sleep when not in use. Launching sound enabled apps produces a quiet "tick, thud" sound as sound system turns on. When sound is not working, killall pusleaudio "fixes" the issue. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: darin 4814 F pulseaudio /dev/snd/controlC1: darin 4814 F pulseaudio /dev/snd/controlC0: darin 4814 F pulseaudio CurrentDesktop: KDE Date: Sat Mar 30 10:20:24 2019 InstallationDate: Installed on 2018-01-13 (441 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180112) SourcePackage: pulseaudio UpgradeStatus: Upgraded to disco on 2019-03-27 (3 days ago) dmi.bios.date: 08/18/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2103 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z87-PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2103:bd08/18/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ87-PRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.sku: All dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1822426/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1828748] [NEW] gmtp can't connect to phone while gvfs-gphoto2-volume-monitor running
Public bug reported: My Nokia 6.1 phone is properly autodetected, and I can fetch files from it fine via the default ubuntu gui (using gvfs etc). However, running gmtp fails. To diagnose this I tried running mtp-detect. This fails with dank@thinky:~$ mtp-detect libmtp version: 1.1.16 Listing raw device(s) Device 0 (VID=2e04 and PID=c025) is a Nokia 6. Found 1 device(s): Nokia: 6 (2e04:c025) @ bus 3, dev 35 Attempting to connect device(s) error returned by libusb_claim_interface() = -6LIBMTP PANIC: Unable to initialize device Unable to open raw device 0 OK. As described in https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1314556/comments/40 killing gvfs-gphoto2-volume-monitor let mtd-detect and gmtd work properly. Is the clash expected? ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gvfs-backends 1.40.1-1 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun May 12 15:21:27 2019 InstallationDate: Installed on 2017-04-29 (743 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gvfs UpgradeStatus: Upgraded to disco on 2019-05-12 (0 days ago) ** Affects: gvfs (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco -- 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/1828748 Title: gmtp can't connect to phone while gvfs-gphoto2-volume-monitor running Status in gvfs package in Ubuntu: New Bug description: My Nokia 6.1 phone is properly autodetected, and I can fetch files from it fine via the default ubuntu gui (using gvfs etc). However, running gmtp fails. To diagnose this I tried running mtp-detect. This fails with dank@thinky:~$ mtp-detect libmtp version: 1.1.16 Listing raw device(s) Device 0 (VID=2e04 and PID=c025) is a Nokia 6. Found 1 device(s): Nokia: 6 (2e04:c025) @ bus 3, dev 35 Attempting to connect device(s) error returned by libusb_claim_interface() = -6LIBMTP PANIC: Unable to initialize device Unable to open raw device 0 OK. As described in https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1314556/comments/40 killing gvfs-gphoto2-volume-monitor let mtd-detect and gmtd work properly. Is the clash expected? ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gvfs-backends 1.40.1-1 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun May 12 15:21:27 2019 InstallationDate: Installed on 2017-04-29 (743 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gvfs UpgradeStatus: Upgraded to disco on 2019-05-12 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1828748/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1814607] [NEW] ubuntu 18.04.2 daily is janky with chromium on fishgl.com?
Public bug reported: I've been testing as follows: - install chromium (or chrome, or chrome beta) - open http://fishgl.com - crank up number of fish to 325 (or as high as it'll go and sustain 60 fps) - after fish are happily swimming, watch them swim for 60 seconds, and count number of times the screen freezes This was fine (i.e. zero hangs) on 18.04.1 + https://ubuntuforums.org/showthread.php?t=2400400 but not fine on 18.04.2 (i.e. always hangs briefly within 60 seconds) The last four times I ran this, I got 4, 2, 8, 3 hangs in 60 seconds. Each hang usually lasted for less than a second. Some lasted for a second and a half (maybe that was two hangs back to back). Running xclock -update 1 seems to show that the hang extends to other apps, i.e. when the fish hang, xclock also seems to hang. Running firefox in parallel, or a second chromium window, seems to avoid the hang. tail -f /var/log/syslog didn't show any new output during hangs. (There are a lot of gnome-shell stack dumps in /var/log/syslog, fwiw.) I'll try to test on a non-Hades system. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.18.0-14.15~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-14-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Feb 4 16:50:27 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:694e] (rev c0) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Device [8086:2073] InstallationDate: Installed on 2019-02-04 (0 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Beta amd64 (20190204) MachineType: Intel Corporation NUC8i7HNK ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-14-generic root=UUID=861436ab-4967-41b5-99bc-64b8726682a5 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/01/2018 dmi.bios.vendor: Intel Corp. dmi.bios.version: HNKBLi70.86A.0049.2018.0801.1601 dmi.board.name: NUC8i7HNB dmi.board.vendor: Intel Corporation dmi.board.version: J68197-502 dmi.chassis.type: 3 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnIntelCorp.:bvrHNKBLi70.86A.0049.2018.0801.1601:bd08/01/2018:svnIntelCorporation:pnNUC8i7HNK:pvrJ71486-502:rvnIntelCorporation:rnNUC8i7HNB:rvrJ68197-502:cvnIntelCorporation:ct3:cvr2.0: dmi.product.family: Intel NUC dmi.product.name: NUC8i7HNK dmi.product.version: J71486-502 dmi.sys.vendor: Intel Corporation version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1~18.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic performance ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1814607 Title: ubuntu 18.04.2 daily is janky with chromium on fishgl.com? Status in xorg package in Ubuntu: New Bug description: I've been testing as follows: - install chromium (or chrome, or chrome beta) - open http://fishgl.com - crank up number of fish to 325 (or as high as it'll go and sustain 60 fps) - after fish are happily swimming, watch them swim for 60 seconds, and count number of times the screen freezes This was fine (i.e. zero hangs) on 18.04.1 + https://ubuntuforums.org/showthread.php?t=2400400 but not fine on 18.04.2 (i.e. always hangs briefly within 60 seconds) The last four times I ran this, I got 4, 2, 8, 3 hangs in 60 seconds. Each hang usually lasted for less than a second. Some lasted for a second and a half (maybe that was two hangs back to back). Running xclock -update 1 seems to show that the hang extends to other apps, i.e. when the fish hang, xclock also seems to hang. Running firefox in parallel, or a second chromium window, seems to avoid the hang. tail -f /var/log/syslog didn't show any new output during hangs. (There are a lot of gnome-shell stack dumps in /var/log/syslog, fwiw.) I'll try to test on a non-Hades system. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1
[Desktop-packages] [Bug 1814606] [NEW] ubuntu 18.04.2 daily is janky with chromium on fishgl.com?
Public bug reported: I've been testing Ubuntu 18.04.1 with Hades Canyon using the recipe https://mzwiki.oblong.com/wiki/Hades_Canyon My smoke test is: - install chromium (or chrome, or chrome beta) - open http://fishgl.com - crank up number of fish to 325 (or as high as it'll go and sustain 60 fps) - after fish are happily swimming, watch them swim for 60 seconds, and count number of times the screen freezes This was fine (i.e. zero hangs) on 18.04.1 + https://mzwiki.oblong.com/wiki/Hades_Canyon but not fine on 18.04.2 (i.e. always hangs briefly within 60 seconds) The last four times I ran this, I got 4, 2, 8, 3 hangs in 60 seconds. Each hang usually lasted for less than a second. Some lasted for a second and a half (maybe that was two hangs back to back). Running xclock -update 1 seems to show that the hang extends to other apps, i.e. when the fish hang, xclock also seems to hang. Running firefox in parallel, or a second chromium window, seems to avoid the hang. tail -f /var/log/syslog didn't show any new output during hangs. (There are a lot of gnome-shell stack dumps in /var/log/syslog, fwiw.) I'll try to test on a non-Hades system. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.18.0-14.15~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-14-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Feb 4 16:15:59 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:694e] (rev c0) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Device [8086:2073] InstallationDate: Installed on 2019-02-04 (0 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Beta amd64 (20190204) MachineType: Intel Corporation NUC8i7HNK ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-14-generic root=UUID=861436ab-4967-41b5-99bc-64b8726682a5 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/01/2018 dmi.bios.vendor: Intel Corp. dmi.bios.version: HNKBLi70.86A.0049.2018.0801.1601 dmi.board.name: NUC8i7HNB dmi.board.vendor: Intel Corporation dmi.board.version: J68197-502 dmi.chassis.type: 3 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnIntelCorp.:bvrHNKBLi70.86A.0049.2018.0801.1601:bd08/01/2018:svnIntelCorporation:pnNUC8i7HNK:pvrJ71486-502:rvnIntelCorporation:rnNUC8i7HNB:rvrJ68197-502:cvnIntelCorporation:ct3:cvr2.0: dmi.product.family: Intel NUC dmi.product.name: NUC8i7HNK dmi.product.version: J71486-502 dmi.sys.vendor: Intel Corporation version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1~18.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic performance ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1814606 Title: ubuntu 18.04.2 daily is janky with chromium on fishgl.com? Status in xorg package in Ubuntu: New Bug description: I've been testing Ubuntu 18.04.1 with Hades Canyon using the recipe https://mzwiki.oblong.com/wiki/Hades_Canyon My smoke test is: - install chromium (or chrome, or chrome beta) - open http://fishgl.com - crank up number of fish to 325 (or as high as it'll go and sustain 60 fps) - after fish are happily swimming, watch them swim for 60 seconds, and count number of times the screen freezes This was fine (i.e. zero hangs) on 18.04.1 + https://mzwiki.oblong.com/wiki/Hades_Canyon but not fine on 18.04.2 (i.e. always hangs briefly within 60 seconds) The last four times I ran this, I got 4, 2, 8, 3 hangs in 60 seconds. Each hang usually lasted for less than a second. Some lasted for a second and a half (maybe that was two hangs back to back). Running xclock -update 1 seems to show that the hang extends to other apps, i.e. when the fish hang, xclock also seems to hang. Running firefox in parallel, or a second chromium window, seems to avoid the hang. tail -f /var/log/syslog didn't show any new output during hangs. (There are
[Desktop-packages] [Bug 1714178] Re: Triple 4K monitor display failed (modesetting driver limited to 8192x8192)
I should have mentioned, my Hades has 32GB of RAM. With 8GB or less of RAM, the problem might persist (if I understand the mailing list posts). -- 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/1714178 Title: Triple 4K monitor display failed (modesetting driver limited to 8192x8192) Status in X.Org X server: Confirmed Status in linux package in Ubuntu: Triaged Status in mesa package in Ubuntu: Triaged Status in xorg-server package in Ubuntu: Triaged Status in linux source package in Bionic: Confirmed Status in mesa source package in Bionic: Confirmed Status in xorg-server source package in Bionic: Confirmed Bug description: Title: Triple monitor display failed with Dell Dock (HiDPI) (modesetting) Summary: Triple monitor display failed with Dell Dock (HiDPI) (modesetting) Steps: 1. a laptop with Built-in 4K LCD 2. Cold boot system with Dell Dock connected 3. Connect a 4K monitor to Dock 4. Connect 2nd 4K monitor to Dock 5. Go to [All Settings]=>[Displays] to have the following configuration. Resolution: 4kx2k@60Hz (one Built-in LCD + two external monitors) Mirror displays: disable Expected results: Triple monitor display should works without issues Actual results: Triple monitor display failed with Dell Dock Additional information: 1. Linux distribution: Ubuntu 16.04+modesetting, 16.04.3, and 17.04 2. Laptop: Dell Precision 5520 3. Dell Business Thunderbolt Dock - TB16 https://goo.gl/vFDjpi WORKAROUND (UBUNTU 18.04+): Log in to "Ubuntu on Wayland" instead of "Ubuntu". --- .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity DistUpgraded: Fresh install DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 DistroCodename: xenial DistroRelease: Ubuntu 16.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:591d] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:07bf] Subsystem: Dell Device [1028:07bf] InstallationDate: Installed on 2017-08-29 (2 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 MachineType: Dell Inc. Precision 5520 Package: xorg-server (not installed) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.11.0-14-generic.efi.signed root=UUID=b79ae801-0652-4785-beaf-e8387d798948 ro acpi_rev_override quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.11.0-14.20~16.04.1-generic 4.11.12 Tags: xenial ubuntu compiz-0.9 Uname: Linux 4.11.0-14-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/08/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.3 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.3:bd05/08/2017:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.name: Precision 5520 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1714178/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1714178] Re: Triple 4K monitor display failed (modesetting driver limited to 8192x8192)
This just changed for me... but the hardware may matter, as I'm on Hades Canyon, using the amd gpu, not HD graphics. A few days ago I updated to the then-latest 4.19-rc2 (and wrote https://ubuntuforums.org/showthread.php?t=2400400 documenting exactly what I did). Using plain old X (no desktop) on my Hades Canyon, I now see a 16384 x 16384 limit: $ xrandr Screen 0: minimum 320 x 200, current 11520 x 2160, maximum 16384 x 16384 Three screens horizontally work. https://www.mail-archive.com/amd-gfx@lists.freedesktop.org/msg24954.html looks related. I have not yet tested on HD graphics with the new kernel. -- 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/1714178 Title: Triple 4K monitor display failed (modesetting driver limited to 8192x8192) Status in X.Org X server: Confirmed Status in linux package in Ubuntu: Triaged Status in mesa package in Ubuntu: Triaged Status in xorg-server package in Ubuntu: Triaged Status in linux source package in Bionic: Confirmed Status in mesa source package in Bionic: Confirmed Status in xorg-server source package in Bionic: Confirmed Bug description: Title: Triple monitor display failed with Dell Dock (HiDPI) (modesetting) Summary: Triple monitor display failed with Dell Dock (HiDPI) (modesetting) Steps: 1. a laptop with Built-in 4K LCD 2. Cold boot system with Dell Dock connected 3. Connect a 4K monitor to Dock 4. Connect 2nd 4K monitor to Dock 5. Go to [All Settings]=>[Displays] to have the following configuration. Resolution: 4kx2k@60Hz (one Built-in LCD + two external monitors) Mirror displays: disable Expected results: Triple monitor display should works without issues Actual results: Triple monitor display failed with Dell Dock Additional information: 1. Linux distribution: Ubuntu 16.04+modesetting, 16.04.3, and 17.04 2. Laptop: Dell Precision 5520 3. Dell Business Thunderbolt Dock - TB16 https://goo.gl/vFDjpi WORKAROUND (UBUNTU 18.04+): Log in to "Ubuntu on Wayland" instead of "Ubuntu". --- .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity DistUpgraded: Fresh install DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 DistroCodename: xenial DistroRelease: Ubuntu 16.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:591d] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:07bf] Subsystem: Dell Device [1028:07bf] InstallationDate: Installed on 2017-08-29 (2 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 MachineType: Dell Inc. Precision 5520 Package: xorg-server (not installed) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.11.0-14-generic.efi.signed root=UUID=b79ae801-0652-4785-beaf-e8387d798948 ro acpi_rev_override quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.11.0-14.20~16.04.1-generic 4.11.12 Tags: xenial ubuntu compiz-0.9 Uname: Linux 4.11.0-14-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/08/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.3 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.3:bd05/08/2017:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.name: Precision 5520 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1714178/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to :
[Desktop-packages] [Bug 1770742] Re: Cannot find -lGL
This just hit me as well, on a kosher 18.04 system.
I recently upgraded to a newer nvidia card, so that must have mangled it
somehow.
Looks like three of its symlinks got nuked:
ls: cannot access '/usr/lib/x86_64-linux-gnu/libEGL.so': No such file or
directory
ls: cannot access '/usr/lib/x86_64-linux-gnu/libGL.so': No such file or
directory
ls: cannot access '/usr/lib/x86_64-linux-gnu/libGLESv2.so': No such file or
directory
lrwxrwxrwx 1 root root 22 Jun 5 07:16
/usr/lib/x86_64-linux-gnu/libGLdispatch.so -> libGLdispatch.so.0.0.0
...
-rw-r--r-- 1 root root 4697 Jan 25 2018 /usr/share/doc/libglvnd-dev/copyright
Doing
sudo apt install --reinstall libglvnd-dev
resolved the problem here.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libglvnd in Ubuntu.
https://bugs.launchpad.net/bugs/1770742
Title:
Cannot find -lGL
Status in libglvnd package in Ubuntu:
Invalid
Bug description:
I was trying to compile a OpenGL program, but it fails to compile. I
suppose the package this bug is in is really libglvnd-dev, but I could
not find that in Launchpad.
Anyway, the linking error is:
/usr/bin/x86_64-linux-gnu-ld: cannot find -lGL
collect2: error: ld returned 1 exit status
This seems to be because the symlink libGL.so is missing. If I go to
/usr/lib/x86_64-linux-gnu and type:
sudo ln -s libGL.so.1 libGL.so
then compiling works.
Here is a (nonsensical) test program:
#include
int main(int argc, char *argv[])
{
glEnable(GL_DEPTH_TEST);
return 0;
}
which I compile with:
gcc testgl.c -lGL
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: libgl1 1.0.0-2ubuntu2
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
CurrentDesktop: KDE
Date: Fri May 11 15:48:17 2018
EcryptfsInUse: Yes
InstallationDate: Installed on 2018-04-29 (12 days ago)
InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64
(20180426)
SourcePackage: libglvnd
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libglvnd/+bug/1770742/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1732766] Re: firefox 57 does not display fish in fishgl.com on intel 530?
Also occurs on Ubuntu 18.04 updated to latest mesa and using Vega M graphics. -- 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/1732766 Title: firefox 57 does not display fish in fishgl.com on intel 530? Status in firefox package in Ubuntu: Confirmed Bug description: On my two intel graphics Ubuntu 16.04 systems (both Dell 3620's), firefox does not display any fish; it simply shows the back wall. OpenGL vendor string: Intel Open Source Technology Center OpenGL renderer string: Mesa DRI Intel(R) HD Graphics 530 (Skylake GT2) OpenGL core profile version string: 4.5 (Core Profile) Mesa 17.0.7 OpenGL core profile shading language version string: 4.50 fishgl works fine in chrome, and on other ubuntu systems here. Affects both firefox 56.0+build6-0ubuntu0.16.04.2 and 57.0+build4-0ubuntu0.16.04.5 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: firefox 57.0+build4-0ubuntu0.16.04.5 ProcVersionSignature: Ubuntu 4.4.0-98.121-generic 4.4.90 Uname: Linux 4.4.0-98-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.1-0ubuntu2.12 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: dank 1843 F...m pulseaudio /dev/snd/controlC0: dank 1843 F pulseaudio /dev/snd/controlC1: dank 1843 F pulseaudio BuildID: 20171115095126 Channel: Unavailable Date: Thu Nov 16 10:55:39 2017 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) IpRoute: default via 10.10.1.1 dev enp0s31f6 10.0.3.0/24 dev lxcbr0 proto kernel scope link src 10.0.3.1 linkdown 10.10.0.0/16 dev enp0s31f6 proto kernel scope link src 10.10.130.236 169.254.0.0/16 dev enp0s31f6 scope link metric 1000 IwConfig: lono wireless extensions. enp0s31f6 no wireless extensions. lxcbr0no wireless extensions. Locales: extensions.sqlite corrupt or missing PrefSources: prefs.js ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Profiles: Profile0 (Default) - LastVersion=57.0/20171115095126 (In use) RfKill: RunningIncompatibleAddons: False SourcePackage: firefox Themes: extensions.sqlite corrupt or missing UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: dmi.bios.date: 05/26/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.6 dmi.board.name: 09WH54 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 6 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.6:bd05/26/2016:svnDellInc.:pnPrecisionTower3620:pvr:rvnDellInc.:rn09WH54:rvrA00:cvnDellInc.:ct6:cvr: dmi.product.name: Precision Tower 3620 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1732766/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1776260] Re: Can't use three monitors properly; "xrandr: screen cannot be larger than 8192x8192"
Thanks... sounds like it's a hardware limitation, and the fix involves noticing when the limit's being violated, and doing extra work in that case. I wonder what the framerate impact of that extra work will be. -- 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/1776260 Title: Can't use three monitors properly; "xrandr: screen cannot be larger than 8192x8192" Status in mutter package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Incomplete Bug description: https://www.intel.com/content/www/us.../mini-pcs.html claims that the Skull Canyon ( NUC6i7KYK ) can handle three 4k displays, so I'm experimenting with a Skull Canyon running a fresh minimal Ubuntu 18.04. It works great when plugged into one 4k monitor (via any of the three ports: hdmi, mini-dp, or type c; all three show up in xrandr as DisplayPort). It even seems to work ok when I plug in two. Doesn't matter which two. When I plug in all three, and boot to normal graphical.target mode with the usual gdm greeter, one of the three screens does show gdm, and allows me to log in. But I can't seem to get all three screens active at the same time. Falling back to old school tools, I did 'sudo systemctl set-default multi-user.target' and rebooted. Logging in, creating a trivial .xinitrc, and doing 'startx' started the X server, and all three screens show the same output. So far so good. But trying to arrange them like this: $ xrandr --auto --output DP-2 --right-of DP-1 --output DP-3 --right-of DP-2 fails with xrandr: screen cannot be larger than 8192x8192 (desired size 11520x2160) Using --above instead of --right-of works, but that's not how the monitors are arranged. I tried creating /usr/share/X11/xorg.conf.d/85-screen.conf containing Section "Screen" Identifier "Default Screen" DefaultDepth24 SubSection "Display" Virtual 11520 6480 EndSubSection EndSection and applied it by killing X and doing startx again, but that gave very strange results: the mouse showed up on two screens, but .xinit didn't seem to have taken effect, and the content on the screen was the same as before startx. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xserver-xorg-core 2:1.19.6-1ubuntu4 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Mon Jun 11 09:49:40 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Iris Pro Graphics 580 [8086:193b] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Iris Pro Graphics 580 [8086:2064] InstallationDate: Installed on 2018-06-08 (2 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-22-generic root=UUID=80ac733c-b098-4643-84a4-fe81874f2101 ro rootflags=subvol=@ quiet splash vt.handoff=1 SourcePackage: xorg-server UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/03/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: KYSKLi70.86A.0037.2016.0603.1032 dmi.board.name: NUC6i7KYB dmi.board.vendor: Intel Corporation dmi.board.version: H90766-404 dmi.chassis.type: 3 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrKYSKLi70.86A.0037.2016.0603.1032:bd06/03/2016:svn:pn:pvr:rvnIntelCorporation:rnNUC6i7KYB:rvrH90766-404:cvnIntelCorporation:ct3:cvr1.0: version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1776260/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help :
[Desktop-packages] [Bug 1776260] Re: Can't use three monitors properly; "xrandr: screen cannot be larger than 8192x8192"
Thanks, I'll try weston-launch when I get a chance, and I'll try it on ubuntu 18.04 with intel graphics. In the meantime, I checked the maximum size a few systems report, and it does seem to be a property of the graphics hardware and/or driver. See also http://webglstats.com/webgl2/parameter/MAX_TEXTURE_SIZE === + uname -a Linux rbb-ubu1604-6 4.4.0-128-generic #154-Ubuntu SMP Fri May 25 14:15:18 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux + grep maximum + xrandr Screen 0: minimum 8 x 8, current 3840 x 6480, maximum 32767 x 32767 + lspci + grep VGA 03:00.0 VGA compatible controller: NVIDIA Corporation Device 1c03 (rev a1) + glxinfo + grep string server glx vendor string: NVIDIA Corporation server glx version string: 1.4 client glx vendor string: NVIDIA Corporation client glx version string: 1.4 OpenGL vendor string: NVIDIA Corporation OpenGL renderer string: GeForce GTX 1060 6GB/PCIe/SSE2 OpenGL core profile version string: 4.5.0 NVIDIA 390.67 OpenGL core profile shading language version string: 4.50 NVIDIA OpenGL version string: 4.6.0 NVIDIA 390.67 OpenGL shading language version string: 4.60 NVIDIA OpenGL ES profile version string: OpenGL ES 3.2 NVIDIA 390.67 OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20 === + uname -a Linux rbb-ubu1804-5 4.17.0-999-generic #201806080237 SMP Fri Jun 8 06:41:11 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux + xrandr + grep maximum Screen 0: minimum 320 x 200, current 7680 x 2160, maximum 16384 x 16384 + lspci + grep VGA 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Vega [Radeon RX Vega M] (rev c0) + glxinfo + grep string server glx vendor string: SGI server glx version string: 1.4 client glx vendor string: Mesa Project and SGI client glx version string: 1.4 OpenGL vendor string: X.Org OpenGL renderer string: AMD VEGAM (DRM 3.26.0, 4.17.0-999-generic, LLVM 6.0.0) OpenGL core profile version string: 4.5 (Core Profile) Mesa 18.2.0-devel OpenGL core profile shading language version string: 4.50 OpenGL version string: 3.1 Mesa 18.2.0-devel OpenGL shading language version string: 1.40 OpenGL ES profile version string: OpenGL ES 3.1 Mesa 18.2.0-devel OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.10 === + uname -a Linux rbb-ubu1804-6 4.15.0-23-generic #25-Ubuntu SMP Wed May 23 18:02:16 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux + xrandr + grep maximum Screen 0: minimum 320 x 200, current 3840 x 6480, maximum 8192 x 8192 + lspci + grep VGA 00:02.0 VGA compatible controller: Intel Corporation Iris Pro Graphics 580 (rev 09) + glxinfo + grep string server glx vendor string: SGI server glx version string: 1.4 client glx vendor string: Mesa Project and SGI client glx version string: 1.4 OpenGL vendor string: Intel Open Source Technology Center OpenGL renderer string: Mesa DRI Intel(R) Iris Pro Graphics 580 (Skylake GT4e) OpenGL core profile version string: 4.5 (Core Profile) Mesa 18.0.0-rc5 OpenGL core profile shading language version string: 4.50 OpenGL version string: 3.0 Mesa 18.0.0-rc5 OpenGL shading language version string: 1.30 OpenGL ES profile version string: OpenGL ES 3.2 Mesa 18.0.0-rc5 OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20 -- 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/1776260 Title: Can't use three monitors properly; "xrandr: screen cannot be larger than 8192x8192" Status in mutter package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Incomplete Bug description: https://www.intel.com/content/www/us.../mini-pcs.html claims that the Skull Canyon ( NUC6i7KYK ) can handle three 4k displays, so I'm experimenting with a Skull Canyon running a fresh minimal Ubuntu 18.04. It works great when plugged into one 4k monitor (via any of the three ports: hdmi, mini-dp, or type c; all three show up in xrandr as DisplayPort). It even seems to work ok when I plug in two. Doesn't matter which two. When I plug in all three, and boot to normal graphical.target mode with the usual gdm greeter, one of the three screens does show gdm, and allows me to log in. But I can't seem to get all three screens active at the same time. Falling back to old school tools, I did 'sudo systemctl set-default multi-user.target' and rebooted. Logging in, creating a trivial .xinitrc, and doing 'startx' started the X server, and all three screens show the same output. So far so good. But trying to arrange them like this: $ xrandr --auto --output DP-2 --right-of DP-1 --output DP-3 --right-of DP-2 fails with xrandr: screen cannot be larger than 8192x8192 (desired size 11520x2160) Using --above instead of --right-of works, but that's not how the monitors are arranged. I tried creating /usr/share/X11/xorg.conf.d/85-screen.conf containing Section "Screen" Identifier "Default Screen"
[Desktop-packages] [Bug 1776260] Re: Can't use three monitors properly; "xrandr: screen cannot be larger than 8192x8192"
Sorry, that Intel URL should have been https://www.intel.com/content/www/us/en/support/articles/05571/mini- pcs.html -- 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/1776260 Title: Can't use three monitors properly; "xrandr: screen cannot be larger than 8192x8192" Status in xorg-server package in Ubuntu: New Bug description: https://www.intel.com/content/www/us.../mini-pcs.html claims that the Skull Canyon ( NUC6i7KYK ) can handle three 4k displays, so I'm experimenting with a Skull Canyon running a fresh minimal Ubuntu 18.04. It works great when plugged into one 4k monitor (via any of the three ports: hdmi, mini-dp, or type c; all three show up in xrandr as DisplayPort). It even seems to work ok when I plug in two. Doesn't matter which two. When I plug in all three, and boot to normal graphical.target mode with the usual gdm greeter, one of the three screens does show gdm, and allows me to log in. But I can't seem to get all three screens active at the same time. Falling back to old school tools, I did 'sudo systemctl set-default multi-user.target' and rebooted. Logging in, creating a trivial .xinitrc, and doing 'startx' started the X server, and all three screens show the same output. So far so good. But trying to arrange them like this: $ xrandr --auto --output DP-2 --right-of DP-1 --output DP-3 --right-of DP-2 fails with xrandr: screen cannot be larger than 8192x8192 (desired size 11520x2160) Using --above instead of --right-of works, but that's not how the monitors are arranged. I tried creating /usr/share/X11/xorg.conf.d/85-screen.conf containing Section "Screen" Identifier "Default Screen" DefaultDepth24 SubSection "Display" Virtual 11520 6480 EndSubSection EndSection and applied it by killing X and doing startx again, but that gave very strange results: the mouse showed up on two screens, but .xinit didn't seem to have taken effect, and the content on the screen was the same as before startx. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xserver-xorg-core 2:1.19.6-1ubuntu4 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Mon Jun 11 09:49:40 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Iris Pro Graphics 580 [8086:193b] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Iris Pro Graphics 580 [8086:2064] InstallationDate: Installed on 2018-06-08 (2 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-22-generic root=UUID=80ac733c-b098-4643-84a4-fe81874f2101 ro rootflags=subvol=@ quiet splash vt.handoff=1 SourcePackage: xorg-server UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/03/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: KYSKLi70.86A.0037.2016.0603.1032 dmi.board.name: NUC6i7KYB dmi.board.vendor: Intel Corporation dmi.board.version: H90766-404 dmi.chassis.type: 3 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrKYSKLi70.86A.0037.2016.0603.1032:bd06/03/2016:svn:pn:pvr:rvnIntelCorporation:rnNUC6i7KYB:rvrH90766-404:cvnIntelCorporation:ct3:cvr1.0: version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1776260/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1776260] [NEW] Can't use three monitors properly; "xrandr: screen cannot be larger than 8192x8192"
Public bug reported: https://www.intel.com/content/www/us.../mini-pcs.html claims that the Skull Canyon ( NUC6i7KYK ) can handle three 4k displays, so I'm experimenting with a Skull Canyon running a fresh minimal Ubuntu 18.04. It works great when plugged into one 4k monitor (via any of the three ports: hdmi, mini-dp, or type c; all three show up in xrandr as DisplayPort). It even seems to work ok when I plug in two. Doesn't matter which two. When I plug in all three, and boot to normal graphical.target mode with the usual gdm greeter, one of the three screens does show gdm, and allows me to log in. But I can't seem to get all three screens active at the same time. Falling back to old school tools, I did 'sudo systemctl set-default multi-user.target' and rebooted. Logging in, creating a trivial .xinitrc, and doing 'startx' started the X server, and all three screens show the same output. So far so good. But trying to arrange them like this: $ xrandr --auto --output DP-2 --right-of DP-1 --output DP-3 --right-of DP-2 fails with xrandr: screen cannot be larger than 8192x8192 (desired size 11520x2160) Using --above instead of --right-of works, but that's not how the monitors are arranged. I tried creating /usr/share/X11/xorg.conf.d/85-screen.conf containing Section "Screen" Identifier "Default Screen" DefaultDepth24 SubSection "Display" Virtual 11520 6480 EndSubSection EndSection and applied it by killing X and doing startx again, but that gave very strange results: the mouse showed up on two screens, but .xinit didn't seem to have taken effect, and the content on the screen was the same as before startx. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xserver-xorg-core 2:1.19.6-1ubuntu4 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Mon Jun 11 09:49:40 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Iris Pro Graphics 580 [8086:193b] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Iris Pro Graphics 580 [8086:2064] InstallationDate: Installed on 2018-06-08 (2 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-22-generic root=UUID=80ac733c-b098-4643-84a4-fe81874f2101 ro rootflags=subvol=@ quiet splash vt.handoff=1 SourcePackage: xorg-server UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/03/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: KYSKLi70.86A.0037.2016.0603.1032 dmi.board.name: NUC6i7KYB dmi.board.vendor: Intel Corporation dmi.board.version: H90766-404 dmi.chassis.type: 3 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrKYSKLi70.86A.0037.2016.0603.1032:bd06/03/2016:svn:pn:pvr:rvnIntelCorporation:rnNUC6i7KYB:rvrH90766-404:cvnIntelCorporation:ct3:cvr1.0: version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 ** Affects: xorg-server (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1776260 Title: Can't use three monitors properly; "xrandr: screen cannot be larger than 8192x8192" Status in xorg-server package in Ubuntu: New Bug description: https://www.intel.com/content/www/us.../mini-pcs.html claims that the Skull Canyon ( NUC6i7KYK ) can handle three 4k displays, so I'm experimenting with a Skull Canyon running a fresh minimal Ubuntu 18.04. It works great when plugged into one 4k monitor (via any of the three ports: hdmi, mini-dp, or type c; all three show up in xrandr as DisplayPort). It even seems to work ok when I plug in two. Doesn't matter which two. When I plug in all three, and boot to normal graphical.target mode with the usual gdm greeter, one of the three screens does show gdm, and allows me to log in. But I
[Desktop-packages] [Bug 1766938] Re: gnome-shell crashed in standard_pict_format_for_depth()
optimized out, alas. But: (gdb) frame 9 #9 surface_from_pixmap (xdisplay=xdisplay@entry=0x56149472f000, xpixmap=xpixmap@entry=31457330, height=, width=) at x11/iconcache.c:325 325 return cairo_xlib_surface_create_with_xrender_format (xdisplay, xpixmap, DefaultScreenOfDisplay (xdisplay), (gdb) list 320 321 if (!XGetGeometry (xdisplay, xpixmap, _return, 322 _ret, _ret, _ret, _ret, _ret, _ret)) 323 return NULL; 324 325 return cairo_xlib_surface_create_with_xrender_format (xdisplay, xpixmap, DefaultScreenOfDisplay (xdisplay), 326 pict_format_for_depth (xdisplay, depth_ret), w_ret, h_ret); 327 } 328 329 static gboolean (gdb) print depth_ret $2 = 16 So, not corrupt, just not handled? FWIW, see also https://bugzilla.redhat.com/show_bug.cgi?id=1239129 I'm having a little trouble believing my screen was using 16 bit mode, could one of the cached icons have been 16 bits? ** Bug watch added: Red Hat Bugzilla #1239129 https://bugzilla.redhat.com/show_bug.cgi?id=1239129 -- 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/1766938 Title: gnome-shell crashed in standard_pict_format_for_depth() Status in gnome-shell package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: I have a fleet of Dell T7500's, a few Dell 3620's, a Skull Canyon, and a Hades Canyon, and a few other odds and ends, running a mix of ubuntu 16.04 and 17.10. On one of the T7500 ubuntu 17.10 boxes (nvidia 340 package, Quadro K5000 card), I did sudo "do-release-upgrade -d". Went fine, but on reboot, the desktop would come up for about ten seconds, then the system would shut down. Did systemctl set-default multi-user.target then removed all traces of the proprietary driver with sudo apt remove --purge nvidia-340 nvidia-opencl-icd-340 nvidia-settings nvidia-384 nvidia-opencl-icd-384 nvidia-prime libcuda1-340 and rebooted. Logging in to the console and running 'startx' reproduces the problem reliably, and does not shut down the system. Installing lwm, and a .xinitrc that started an xterm, let startx succeed, and the system was stable running firefox, so it's not an obvious graphics problem. /var/log/syslog says Apr 25 09:59:41 rbb-ubu1710-3 org.gnome.Shell.desktop[3936]: ** Apr 25 09:59:41 rbb-ubu1710-3 org.gnome.Shell.desktop[3936]: mutter:ERROR:x11/iconcache.c:303:standard_pict_format_for_depth: code should not be reached Apr 25 09:59:41 rbb-ubu1710-3 org.gnome.Shell.desktop[3936]: == Stack trace for context 0x556d30f3c4c0 == Apr 25 09:59:41 rbb-ubu1710-3 dbus-daemon[690]: [system] Successfully activated service 'org.freedesktop.fwupd' Apr 25 09:59:41 rbb-ubu1710-3 systemd[1]: Started Firmware update daemon. Apr 25 09:59:42 rbb-ubu1710-3 PackageKit: get-updates transaction /2379_acbceaca from uid 1000 finished with success after 1175ms Apr 25 09:59:42 rbb-ubu1710-3 gnome-session[3605]: gnome-session-binary[3605]: WARNING: Application 'org.gnome.Shell.desktop' killed by signal 6 Apr 25 09:59:42 rbb-ubu1710-3 gnome-session[3605]: gnome-session-binary[3605]: WARNING: App 'org.gnome.Shell.desktop' respawning too quickly Apr 25 09:59:42 rbb-ubu1710-3 gnome-session[3605]: gnome-session-binary[3605]: CRITICAL: We failed, but the fail whale is dead. Sorry Apr 25 09:59:42 rbb-ubu1710-3 gnome-session-binary[3605]: Unrecoverable failure in required component org.gnome.Shell.desktop Apr 25 09:59:42 rbb-ubu1710-3 gnome-session-binary[3605]: WARNING: Application 'org.gnome.Shell.desktop' killed by signal 6 Apr 25 09:59:42 rbb-ubu1710-3 gnome-session-binary[3605]: WARNING: App 'org.gnome.Shell.desktop' respawning too quickly Apr 25 09:59:42 rbb-ubu1710-3 gnome-session-binary[3605]: CRITICAL: We failed, but the fail whale is dead. Sorry ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.1-0ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 Date: Wed Apr 25 10:06:55 2018 DisplayManager: GsettingsChanges: b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2018-01-04 (111 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170918) SourcePackage: gnome-shell UpgradeStatus: Upgraded to bionic on 2018-04-24 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1766938/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help :
[Desktop-packages] [Bug 1766938] Re: gnome-shell crashed in standard_pict_format_for_depth()
Too late! The world has moved on, and I can no longer upload this bug: You have some obsolete package versions installed. Please upgrade the following packages and check if the problem still occurs: libdb5.3, libplist3, libssl1.1, openssl I guess if it happens on another machine, I'll upload it properly and add a link here. I still have the .crash file if you want 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/1766938 Title: gnome-shell crashed in standard_pict_format_for_depth() Status in gnome-shell package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: I have a fleet of Dell T7500's, a few Dell 3620's, a Skull Canyon, and a Hades Canyon, and a few other odds and ends, running a mix of ubuntu 16.04 and 17.10. On one of the T7500 ubuntu 17.10 boxes (nvidia 340 package, Quadro K5000 card), I did sudo "do-release-upgrade -d". Went fine, but on reboot, the desktop would come up for about ten seconds, then the system would shut down. Did systemctl set-default multi-user.target then removed all traces of the proprietary driver with sudo apt remove --purge nvidia-340 nvidia-opencl-icd-340 nvidia-settings nvidia-384 nvidia-opencl-icd-384 nvidia-prime libcuda1-340 and rebooted. Logging in to the console and running 'startx' reproduces the problem reliably, and does not shut down the system. Installing lwm, and a .xinitrc that started an xterm, let startx succeed, and the system was stable running firefox, so it's not an obvious graphics problem. /var/log/syslog says Apr 25 09:59:41 rbb-ubu1710-3 org.gnome.Shell.desktop[3936]: ** Apr 25 09:59:41 rbb-ubu1710-3 org.gnome.Shell.desktop[3936]: mutter:ERROR:x11/iconcache.c:303:standard_pict_format_for_depth: code should not be reached Apr 25 09:59:41 rbb-ubu1710-3 org.gnome.Shell.desktop[3936]: == Stack trace for context 0x556d30f3c4c0 == Apr 25 09:59:41 rbb-ubu1710-3 dbus-daemon[690]: [system] Successfully activated service 'org.freedesktop.fwupd' Apr 25 09:59:41 rbb-ubu1710-3 systemd[1]: Started Firmware update daemon. Apr 25 09:59:42 rbb-ubu1710-3 PackageKit: get-updates transaction /2379_acbceaca from uid 1000 finished with success after 1175ms Apr 25 09:59:42 rbb-ubu1710-3 gnome-session[3605]: gnome-session-binary[3605]: WARNING: Application 'org.gnome.Shell.desktop' killed by signal 6 Apr 25 09:59:42 rbb-ubu1710-3 gnome-session[3605]: gnome-session-binary[3605]: WARNING: App 'org.gnome.Shell.desktop' respawning too quickly Apr 25 09:59:42 rbb-ubu1710-3 gnome-session[3605]: gnome-session-binary[3605]: CRITICAL: We failed, but the fail whale is dead. Sorry Apr 25 09:59:42 rbb-ubu1710-3 gnome-session-binary[3605]: Unrecoverable failure in required component org.gnome.Shell.desktop Apr 25 09:59:42 rbb-ubu1710-3 gnome-session-binary[3605]: WARNING: Application 'org.gnome.Shell.desktop' killed by signal 6 Apr 25 09:59:42 rbb-ubu1710-3 gnome-session-binary[3605]: WARNING: App 'org.gnome.Shell.desktop' respawning too quickly Apr 25 09:59:42 rbb-ubu1710-3 gnome-session-binary[3605]: CRITICAL: We failed, but the fail whale is dead. Sorry ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.1-0ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 Date: Wed Apr 25 10:06:55 2018 DisplayManager: GsettingsChanges: b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2018-01-04 (111 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170918) SourcePackage: gnome-shell UpgradeStatus: Upgraded to bionic on 2018-04-24 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1766938/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1766938] Re: gnome-shell crashed in standard_pict_format_for_depth()
Sure, sorry for uploading it wrong in the first place. The new bug is ... uh... it didn't create one, it just went into the ether, in a cloud of dots. -- 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/1766938 Title: gnome-shell crashed in standard_pict_format_for_depth() Status in gnome-shell package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: I have a fleet of Dell T7500's, a few Dell 3620's, a Skull Canyon, and a Hades Canyon, and a few other odds and ends, running a mix of ubuntu 16.04 and 17.10. On one of the T7500 ubuntu 17.10 boxes (nvidia 340 package, Quadro K5000 card), I did sudo "do-release-upgrade -d". Went fine, but on reboot, the desktop would come up for about ten seconds, then the system would shut down. Did systemctl set-default multi-user.target then removed all traces of the proprietary driver with sudo apt remove --purge nvidia-340 nvidia-opencl-icd-340 nvidia-settings nvidia-384 nvidia-opencl-icd-384 nvidia-prime libcuda1-340 and rebooted. Logging in to the console and running 'startx' reproduces the problem reliably, and does not shut down the system. Installing lwm, and a .xinitrc that started an xterm, let startx succeed, and the system was stable running firefox, so it's not an obvious graphics problem. /var/log/syslog says Apr 25 09:59:41 rbb-ubu1710-3 org.gnome.Shell.desktop[3936]: ** Apr 25 09:59:41 rbb-ubu1710-3 org.gnome.Shell.desktop[3936]: mutter:ERROR:x11/iconcache.c:303:standard_pict_format_for_depth: code should not be reached Apr 25 09:59:41 rbb-ubu1710-3 org.gnome.Shell.desktop[3936]: == Stack trace for context 0x556d30f3c4c0 == Apr 25 09:59:41 rbb-ubu1710-3 dbus-daemon[690]: [system] Successfully activated service 'org.freedesktop.fwupd' Apr 25 09:59:41 rbb-ubu1710-3 systemd[1]: Started Firmware update daemon. Apr 25 09:59:42 rbb-ubu1710-3 PackageKit: get-updates transaction /2379_acbceaca from uid 1000 finished with success after 1175ms Apr 25 09:59:42 rbb-ubu1710-3 gnome-session[3605]: gnome-session-binary[3605]: WARNING: Application 'org.gnome.Shell.desktop' killed by signal 6 Apr 25 09:59:42 rbb-ubu1710-3 gnome-session[3605]: gnome-session-binary[3605]: WARNING: App 'org.gnome.Shell.desktop' respawning too quickly Apr 25 09:59:42 rbb-ubu1710-3 gnome-session[3605]: gnome-session-binary[3605]: CRITICAL: We failed, but the fail whale is dead. Sorry Apr 25 09:59:42 rbb-ubu1710-3 gnome-session-binary[3605]: Unrecoverable failure in required component org.gnome.Shell.desktop Apr 25 09:59:42 rbb-ubu1710-3 gnome-session-binary[3605]: WARNING: Application 'org.gnome.Shell.desktop' killed by signal 6 Apr 25 09:59:42 rbb-ubu1710-3 gnome-session-binary[3605]: WARNING: App 'org.gnome.Shell.desktop' respawning too quickly Apr 25 09:59:42 rbb-ubu1710-3 gnome-session-binary[3605]: CRITICAL: We failed, but the fail whale is dead. Sorry ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.1-0ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 Date: Wed Apr 25 10:06:55 2018 DisplayManager: GsettingsChanges: b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2018-01-04 (111 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170918) SourcePackage: gnome-shell UpgradeStatus: Upgraded to bionic on 2018-04-24 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1766938/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1766938] Re: gnome-shell crashes after a few seconds
Doesn't sound like a release blocker offhand, but sheesh. Boot loops are no fun. -- 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/1766938 Title: gnome-shell crashes after a few seconds Status in gnome-shell package in Ubuntu: New Bug description: I have a fleet of Dell T7500's, a few Dell 3620's, a Skull Canyon, and a Hades Canyon, and a few other odds and ends, running a mix of ubuntu 16.04 and 17.10. On one of the T7500 ubuntu 17.10 boxes (nvidia 340 package, Quadro K5000 card), I did sudo "do-release-upgrade -d". Went fine, but on reboot, the desktop would come up for about ten seconds, then the system would shut down. Did systemctl set-default multi-user.target then removed all traces of the proprietary driver with sudo apt remove --purge nvidia-340 nvidia-opencl-icd-340 nvidia-settings nvidia-384 nvidia-opencl-icd-384 nvidia-prime libcuda1-340 and rebooted. Logging in to the console and running 'startx' reproduces the problem reliably, and does not shut down the system. Installing lwm, and a .xinitrc that started an xterm, let startx succeed, and the system was stable running firefox, so it's not an obvious graphics problem. /var/log/syslog says Apr 25 09:59:41 rbb-ubu1710-3 org.gnome.Shell.desktop[3936]: ** Apr 25 09:59:41 rbb-ubu1710-3 org.gnome.Shell.desktop[3936]: mutter:ERROR:x11/iconcache.c:303:standard_pict_format_for_depth: code should not be reached Apr 25 09:59:41 rbb-ubu1710-3 org.gnome.Shell.desktop[3936]: == Stack trace for context 0x556d30f3c4c0 == Apr 25 09:59:41 rbb-ubu1710-3 dbus-daemon[690]: [system] Successfully activated service 'org.freedesktop.fwupd' Apr 25 09:59:41 rbb-ubu1710-3 systemd[1]: Started Firmware update daemon. Apr 25 09:59:42 rbb-ubu1710-3 PackageKit: get-updates transaction /2379_acbceaca from uid 1000 finished with success after 1175ms Apr 25 09:59:42 rbb-ubu1710-3 gnome-session[3605]: gnome-session-binary[3605]: WARNING: Application 'org.gnome.Shell.desktop' killed by signal 6 Apr 25 09:59:42 rbb-ubu1710-3 gnome-session[3605]: gnome-session-binary[3605]: WARNING: App 'org.gnome.Shell.desktop' respawning too quickly Apr 25 09:59:42 rbb-ubu1710-3 gnome-session[3605]: gnome-session-binary[3605]: CRITICAL: We failed, but the fail whale is dead. Sorry Apr 25 09:59:42 rbb-ubu1710-3 gnome-session-binary[3605]: Unrecoverable failure in required component org.gnome.Shell.desktop Apr 25 09:59:42 rbb-ubu1710-3 gnome-session-binary[3605]: WARNING: Application 'org.gnome.Shell.desktop' killed by signal 6 Apr 25 09:59:42 rbb-ubu1710-3 gnome-session-binary[3605]: WARNING: App 'org.gnome.Shell.desktop' respawning too quickly Apr 25 09:59:42 rbb-ubu1710-3 gnome-session-binary[3605]: CRITICAL: We failed, but the fail whale is dead. Sorry ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.1-0ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 Date: Wed Apr 25 10:06:55 2018 DisplayManager: GsettingsChanges: b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2018-01-04 (111 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170918) SourcePackage: gnome-shell UpgradeStatus: Upgraded to bionic on 2018-04-24 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1766938/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1766938] Re: gnome-shell crashes after a few seconds
Ah, that assert is in mutter.
$ mkdir ~/xsrc
$ cd ~/xsrc
$ apt-get source libmutter-2-0
$ cd ~
$ apport-retrace -g _usr_bin_gnome-shell.1000.crash
(gdb) bt
...
(gdb) frame 7
#7 0x7f75c6bb5fbe in standard_pict_format_for_depth (depth=) at x11/iconcache.c:303
303 x11/iconcache.c: No such file or directory.
(gdb) directory xsrc/mutter-3.28.1/src
(gdb) list 291
291 static int
292 standard_pict_format_for_depth (int depth)
293 {
294 switch (depth)
295 {
296 case 1:
297 return PictStandardA1;
298 case 24:
299 return PictStandardRGB24;
300 case 32:
301 return PictStandardARGB32;
302 default:
303 g_assert_not_reached ();
304 }
FWIW, that code was added in
https://gitlab.gnome.org/GNOME/mutter/commit/9b903e93e3cd0601b436c55b7cea1fbecf29895f
So... uh... maybe some icon on my system is making it unhappy?
I gather gtk-update-icon-cache is involved?
buildbot@rbb-ubu1804-3:~$ ls -l /usr/share/icons/*/*.cache
-rw-r--r-- 1 root root 35776 Apr 24 14:57
/usr/share/icons/Adwaita/icon-theme.cache
-rw-r--r-- 1 root root 20312 Apr 25 09:40
/usr/share/icons/hicolor/icon-theme.cache
-rw-r--r-- 1 root root 49808 Apr 24 14:39
/usr/share/icons/HighContrast/icon-theme.cache
-rw-r--r-- 1 root root 26816 Apr 24 14:57
/usr/share/icons/Humanity-Dark/icon-theme.cache
-rw-r--r-- 1 root root 327184 Apr 24 14:57
/usr/share/icons/Humanity/icon-theme.cache
-rw-r--r-- 1 root root628 Apr 24 14:57
/usr/share/icons/LoginIcons/icon-theme.cache
-rw-r--r-- 1 root root 54104 Apr 24 14:57
/usr/share/icons/ubuntu-mono-dark/icon-theme.cache
-rw-r--r-- 1 root root 55040 Apr 24 14:57
/usr/share/icons/ubuntu-mono-light/icon-theme.cache
But now I can't get it to crash anymore.
so maybe I accidentally fixed it by installing some package that updated the
icon caches...?
$ grep hicolor /var/log/dpkg.log
...
2018-04-24 14:42:29 status installed hicolor-icon-theme:all 0.17-2
...
2018-04-24 15:33:00 status installed hicolor-icon-theme:all 0.17-2
...
2018-04-25 09:40:43 status installed hicolor-icon-theme:all 0.17-2
Hrmf. My uneducated theory is that an icon cache was corrupt, but is fine now.
Who knows?
--
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/1766938
Title:
gnome-shell crashes after a few seconds
Status in gnome-shell package in Ubuntu:
New
Bug description:
I have a fleet of Dell T7500's, a few Dell 3620's, a Skull Canyon, and
a Hades Canyon, and a few other odds and ends, running a mix of ubuntu
16.04 and 17.10.
On one of the T7500 ubuntu 17.10 boxes (nvidia 340 package, Quadro K5000
card),
I did sudo "do-release-upgrade -d". Went fine, but on reboot, the desktop
would
come up for about ten seconds, then the system would shut down.
Did
systemctl set-default multi-user.target
then removed all traces of the proprietary driver with
sudo apt remove --purge nvidia-340 nvidia-opencl-icd-340 nvidia-settings
nvidia-384 nvidia-opencl-icd-384 nvidia-prime libcuda1-340
and rebooted. Logging in to the console and running 'startx' reproduces the
problem reliably, and does not shut down the system.
Installing lwm, and a .xinitrc that started an xterm, let startx succeed, and
the system was stable running firefox, so it's not an obvious graphics
problem.
/var/log/syslog says
Apr 25 09:59:41 rbb-ubu1710-3 org.gnome.Shell.desktop[3936]: **
Apr 25 09:59:41 rbb-ubu1710-3 org.gnome.Shell.desktop[3936]:
mutter:ERROR:x11/iconcache.c:303:standard_pict_format_for_depth: code should
not be reached
Apr 25 09:59:41 rbb-ubu1710-3 org.gnome.Shell.desktop[3936]: == Stack trace
for context 0x556d30f3c4c0 ==
Apr 25 09:59:41 rbb-ubu1710-3 dbus-daemon[690]: [system] Successfully
activated service 'org.freedesktop.fwupd'
Apr 25 09:59:41 rbb-ubu1710-3 systemd[1]: Started Firmware update daemon.
Apr 25 09:59:42 rbb-ubu1710-3 PackageKit: get-updates transaction
/2379_acbceaca from uid 1000 finished with success after 1175ms
Apr 25 09:59:42 rbb-ubu1710-3 gnome-session[3605]:
gnome-session-binary[3605]: WARNING: Application 'org.gnome.Shell.desktop'
killed by signal 6
Apr 25 09:59:42 rbb-ubu1710-3 gnome-session[3605]:
gnome-session-binary[3605]: WARNING: App 'org.gnome.Shell.desktop' respawning
too quickly
Apr 25 09:59:42 rbb-ubu1710-3 gnome-session[3605]:
gnome-session-binary[3605]: CRITICAL: We failed, but the fail whale is dead.
Sorry
Apr 25 09:59:42 rbb-ubu1710-3 gnome-session-binary[3605]: Unrecoverable
failure in required component org.gnome.Shell.desktop
Apr 25 09:59:42 rbb-ubu1710-3 gnome-session-binary[3605]: WARNING:
Application 'org.gnome.Shell.desktop' killed by signal 6
Apr 25 09:59:42 rbb-ubu1710-3 gnome-session-binary[3605]: WARNING: App
'org.gnome.Shell.desktop' respawning too quickly
Apr 25 09:59:42 rbb-ubu1710-3
[Desktop-packages] [Bug 1766938] Re: gnome-shell crashes after a few seconds
apport-retrace -g _usr_bin_gnome-shell.1000.crash bt indicates it's an assert in standard_pict_format_for_depth: (gdb) bt #0 0x7f75c68f0727 in raise (sig=) at ../sysdeps/unix/sysv/linux/raise.c:51 #1 0x56149221ba6b in dump_gjs_stack_on_signal_handler (signo=6) at ../src/main.c:367 #2 0x7f75c68f0890 in () at /lib/x86_64-linux-gnu/libpthread.so.0 #3 0x7f75c652be97 in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51 #4 0x7f75c652d801 in __GI_abort () at abort.c:79 #5 0x7f75c868dfa5 in g_assertion_message () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #6 0x7f75c868e00a in g_assertion_message_expr () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #7 0x7f75c6bb5fbe in standard_pict_format_for_depth (depth=) at x11/iconcache.c:303 #8 0x7f75c6bb5fbe in pict_format_for_depth (depth=, xdisplay=0x56149472f000) at x11/iconcache.c:310 #9 0x7f75c6bb5fbe in surface_from_pixmap (xdisplay=xdisplay@entry=0x56149472f000, xpixmap=xpixmap@entry=31457330, height=, width=) at x11/iconcache.c:325 #10 0x7f75c6bb6117 in try_pixmap_and_mask (display=0x5614949c0200, src_pixmap=src_pixmap@entry=31457330, src_mask=src_mask@entry=31457332, iconp=iconp@entry=0x7fff9d183198) at x11/iconcache.c:345 #11 0x7f75c6bb65a4 in meta_read_icons (screen=0x56149454bcd0, xwindow=31457316, icon_cache=0x561495d18df8, wm_hints_pixmap=31457330, wm_hints_mask=31457332, iconp=iconp@entry=0x7fff9d183198, ideal_width=96, ideal_height=96, mini_iconp=0x7fff9d1831a0, ideal_mini_width=16, ideal_mini_height=16) at x11/iconcache.c:546 #12 0x7f75c6bbd3c1 in meta_window_x11_update_icon (window=0x561495d18e30, icon=0x7fff9d183198, mini_icon=0x7fff9d1831a0) at x11/window-x11.c:1472 #13 0x7f75c6ba2608 in meta_window_update_icon_now (window=window@entry=0x561495d18e30, force=force@entry=1) at core/window.c:5326 #14 0x7f75c6ba9abd in _meta_window_shared_new (display=display@entry=0x5614949c0200, screen=screen@entry=0x56149454bcd0, client_type=client_type@entry=META_WINDOW_CLIENT_TYPE_X11, surface=surface@entry=0x0, xwindow=xwindow@entry=31457316, existing_wm_state=existing_wm_state@entry=0, effect=, attrs=) at core/window.c:1148 #15 0x7f75c6bbf6a0 in meta_window_x11_new (display=display@entry=0x5614949c0200, xwindow=31457316, must_be_viewable=must_be_viewable@entry=0, effect=effect@entry=META_COMP_EFFECT_CREATE) at x11/window-x11.c:3148 #16 0x7f75c6bb4554 in handle_other_xevent (display=display@entry=0x5614949c0200, event=event@entry=0x7fff9d183640) at x11/events.c:1372 #17 0x7f75c6bb4deb in meta_display_handle_xevent (event=0x7fff9d183640, display=0x5614949c0200) at x11/events.c:1791 #18 0x7f75c6bb4deb in xevent_filter (xevent=0x7fff9d183640, event=, data=0x5614949c0200) at x11/events.c:1830 #19 0x7f75c5e07edf in () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 #20 0x7f75c5e081c9 in () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 #21 0x7f75c5dd2d70 in gdk_display_get_event () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 #22 0x7f75c5e07f72 in () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 #23 0x7f75c8667287 in g_main_context_dispatch () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #24 0x7f75c86674c0 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #25 0x7f75c86677d2 in g_main_loop_run () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #26 0x7f75c6b94a7c in meta_run () at core/main.c:664 -- 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/1766938 Title: gnome-shell crashes after a few seconds Status in gnome-shell package in Ubuntu: New Bug description: I have a fleet of Dell T7500's, a few Dell 3620's, a Skull Canyon, and a Hades Canyon, and a few other odds and ends, running a mix of ubuntu 16.04 and 17.10. On one of the T7500 ubuntu 17.10 boxes (nvidia 340 package, Quadro K5000 card), I did sudo "do-release-upgrade -d". Went fine, but on reboot, the desktop would come up for about ten seconds, then the system would shut down. Did systemctl set-default multi-user.target then removed all traces of the proprietary driver with sudo apt remove --purge nvidia-340 nvidia-opencl-icd-340 nvidia-settings nvidia-384 nvidia-opencl-icd-384 nvidia-prime libcuda1-340 and rebooted. Logging in to the console and running 'startx' reproduces the problem reliably, and does not shut down the system. Installing lwm, and a .xinitrc that started an xterm, let startx succeed, and the system was stable running firefox, so it's not an obvious graphics problem. /var/log/syslog says Apr 25 09:59:41 rbb-ubu1710-3 org.gnome.Shell.desktop[3936]: ** Apr 25 09:59:41 rbb-ubu1710-3 org.gnome.Shell.desktop[3936]: mutter:ERROR:x11/iconcache.c:303:standard_pict_format_for_depth: code should not be reached Apr 25 09:59:41 rbb-ubu1710-3
[Desktop-packages] [Bug 1766938] [NEW] gnome-shell crashes after a few seconds
Public bug reported: I have a fleet of Dell T7500's, a few Dell 3620's, a Skull Canyon, and a Hades Canyon, and a few other odds and ends, running a mix of ubuntu 16.04 and 17.10. On one of the T7500 ubuntu 17.10 boxes (nvidia 340 package, Quadro K5000 card), I did sudo "do-release-upgrade -d". Went fine, but on reboot, the desktop would come up for about ten seconds, then the system would shut down. Did systemctl set-default multi-user.target then removed all traces of the proprietary driver with sudo apt remove --purge nvidia-340 nvidia-opencl-icd-340 nvidia-settings nvidia-384 nvidia-opencl-icd-384 nvidia-prime libcuda1-340 and rebooted. Logging in to the console and running 'startx' reproduces the problem reliably, and does not shut down the system. Installing lwm, and a .xinitrc that started an xterm, let startx succeed, and the system was stable running firefox, so it's not an obvious graphics problem. /var/log/syslog says Apr 25 09:59:41 rbb-ubu1710-3 org.gnome.Shell.desktop[3936]: ** Apr 25 09:59:41 rbb-ubu1710-3 org.gnome.Shell.desktop[3936]: mutter:ERROR:x11/iconcache.c:303:standard_pict_format_for_depth: code should not be reached Apr 25 09:59:41 rbb-ubu1710-3 org.gnome.Shell.desktop[3936]: == Stack trace for context 0x556d30f3c4c0 == Apr 25 09:59:41 rbb-ubu1710-3 dbus-daemon[690]: [system] Successfully activated service 'org.freedesktop.fwupd' Apr 25 09:59:41 rbb-ubu1710-3 systemd[1]: Started Firmware update daemon. Apr 25 09:59:42 rbb-ubu1710-3 PackageKit: get-updates transaction /2379_acbceaca from uid 1000 finished with success after 1175ms Apr 25 09:59:42 rbb-ubu1710-3 gnome-session[3605]: gnome-session-binary[3605]: WARNING: Application 'org.gnome.Shell.desktop' killed by signal 6 Apr 25 09:59:42 rbb-ubu1710-3 gnome-session[3605]: gnome-session-binary[3605]: WARNING: App 'org.gnome.Shell.desktop' respawning too quickly Apr 25 09:59:42 rbb-ubu1710-3 gnome-session[3605]: gnome-session-binary[3605]: CRITICAL: We failed, but the fail whale is dead. Sorry Apr 25 09:59:42 rbb-ubu1710-3 gnome-session-binary[3605]: Unrecoverable failure in required component org.gnome.Shell.desktop Apr 25 09:59:42 rbb-ubu1710-3 gnome-session-binary[3605]: WARNING: Application 'org.gnome.Shell.desktop' killed by signal 6 Apr 25 09:59:42 rbb-ubu1710-3 gnome-session-binary[3605]: WARNING: App 'org.gnome.Shell.desktop' respawning too quickly Apr 25 09:59:42 rbb-ubu1710-3 gnome-session-binary[3605]: CRITICAL: We failed, but the fail whale is dead. Sorry ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.1-0ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 Date: Wed Apr 25 10:06:55 2018 DisplayManager: GsettingsChanges: b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2018-01-04 (111 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170918) SourcePackage: gnome-shell UpgradeStatus: Upgraded to bionic on 2018-04-24 (0 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- 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/1766938 Title: gnome-shell crashes after a few seconds Status in gnome-shell package in Ubuntu: New Bug description: I have a fleet of Dell T7500's, a few Dell 3620's, a Skull Canyon, and a Hades Canyon, and a few other odds and ends, running a mix of ubuntu 16.04 and 17.10. On one of the T7500 ubuntu 17.10 boxes (nvidia 340 package, Quadro K5000 card), I did sudo "do-release-upgrade -d". Went fine, but on reboot, the desktop would come up for about ten seconds, then the system would shut down. Did systemctl set-default multi-user.target then removed all traces of the proprietary driver with sudo apt remove --purge nvidia-340 nvidia-opencl-icd-340 nvidia-settings nvidia-384 nvidia-opencl-icd-384 nvidia-prime libcuda1-340 and rebooted. Logging in to the console and running 'startx' reproduces the problem reliably, and does not shut down the system. Installing lwm, and a .xinitrc that started an xterm, let startx succeed, and the system was stable running firefox, so it's not an obvious graphics problem. /var/log/syslog says Apr 25 09:59:41 rbb-ubu1710-3 org.gnome.Shell.desktop[3936]: ** Apr 25 09:59:41 rbb-ubu1710-3 org.gnome.Shell.desktop[3936]: mutter:ERROR:x11/iconcache.c:303:standard_pict_format_for_depth: code should not be reached Apr 25 09:59:41 rbb-ubu1710-3 org.gnome.Shell.desktop[3936]: == Stack trace for context 0x556d30f3c4c0 == Apr 25 09:59:41 rbb-ubu1710-3 dbus-daemon[690]: [system] Successfully activated service 'org.freedesktop.fwupd' Apr 25 09:59:41 rbb-ubu1710-3 systemd[1]: Started Firmware
[Desktop-packages] [Bug 1655709] Re: Spurious crash report dialog on every login
Still in ubuntu 17.10 with nvidia card. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1655709 Title: Spurious crash report dialog on every login Status in xorg package in Ubuntu: Confirmed Bug description: For the last few years, on nearly all my computers, ubuntu has rewarded my logging in with a crash dialog. Nothing's actually wrong; xorg probably trips over its shoelaces every time it shuts down, but so late in the process that it doesn't matter. Today I went through the crash upload procedure, but no web browser window opened, so either I did something wrong, or the bug is marked 'ignore uploads' somehow... hence this manual report. This bug has to have been reported before, but has probably been marked WONTFIX or something because it is benign. But it does matter, and it's not benign, because I, my wife, and my son get those darn crash dialogs. It doesn't seem to matter what graphics card or driver is in use. Want the crash file left behind after the last upload? ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xserver-xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-43.63-generic 4.4.21 Uname: Linux 4.4.0-43-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.96 Sun Nov 8 22:33:28 PST 2015 GCC version: gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.2) .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Wed Jan 11 08:56:26 2017 DistUpgraded: 2016-04-26 16:26:11,919 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: xenial DistroVariant: ubuntu DpkgLog: ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GT215M [GeForce GTS 360M] [10de:0cb1] (rev a2) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GT215M [GeForce GTS 360M] [1043:203c] InstallationDate: Installed on 2014-07-18 (908 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) Lsusb: Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 04f2:b071 Chicony Electronics Co., Ltd 2.0M UVC Webcam / CNF7129 Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK Computer Inc. G60JX ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.4.0-43-generic root=UUID=28258489-6453-456a-9ecc-c41a02ad0631 ro rootflags=subvol=@ nomodeset quiet splash SourcePackage: xorg UpgradeStatus: Upgraded to xenial on 2016-04-26 (259 days ago) dmi.bios.date: 08/16/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 208 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: G60JX dmi.board.vendor: PEGATRON CORPORATION dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: PEGATRON Computer Inc. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr208:bd08/16/2010:svnASUSTeKComputerInc.:pnG60JX:pvr1.0:rvnPEGATRONCORPORATION:rnG60JX:rvr1.0:cvnPEGATRONComputerInc.:ct10:cvr1.0: dmi.product.name: G60JX dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK Computer Inc. version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Wed Jan 11 08:41:53 2017 xserver.configfile: default xserver.errors: open /dev/fb0: No such file or directory xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.18.3-1ubuntu2.3 To manage notifications about this bug
[Desktop-packages] [Bug 1732766] Re: firefox 57 does not display fish in fishgl.com on intel 530?
Also occurs on ubuntu 17.10. -- 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/1732766 Title: firefox 57 does not display fish in fishgl.com on intel 530? Status in firefox package in Ubuntu: Confirmed Bug description: On my two intel graphics Ubuntu 16.04 systems (both Dell 3620's), firefox does not display any fish; it simply shows the back wall. OpenGL vendor string: Intel Open Source Technology Center OpenGL renderer string: Mesa DRI Intel(R) HD Graphics 530 (Skylake GT2) OpenGL core profile version string: 4.5 (Core Profile) Mesa 17.0.7 OpenGL core profile shading language version string: 4.50 fishgl works fine in chrome, and on other ubuntu systems here. Affects both firefox 56.0+build6-0ubuntu0.16.04.2 and 57.0+build4-0ubuntu0.16.04.5 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: firefox 57.0+build4-0ubuntu0.16.04.5 ProcVersionSignature: Ubuntu 4.4.0-98.121-generic 4.4.90 Uname: Linux 4.4.0-98-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.1-0ubuntu2.12 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: dank 1843 F...m pulseaudio /dev/snd/controlC0: dank 1843 F pulseaudio /dev/snd/controlC1: dank 1843 F pulseaudio BuildID: 20171115095126 Channel: Unavailable Date: Thu Nov 16 10:55:39 2017 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) IpRoute: default via 10.10.1.1 dev enp0s31f6 10.0.3.0/24 dev lxcbr0 proto kernel scope link src 10.0.3.1 linkdown 10.10.0.0/16 dev enp0s31f6 proto kernel scope link src 10.10.130.236 169.254.0.0/16 dev enp0s31f6 scope link metric 1000 IwConfig: lono wireless extensions. enp0s31f6 no wireless extensions. lxcbr0no wireless extensions. Locales: extensions.sqlite corrupt or missing PrefSources: prefs.js ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Profiles: Profile0 (Default) - LastVersion=57.0/20171115095126 (In use) RfKill: RunningIncompatibleAddons: False SourcePackage: firefox Themes: extensions.sqlite corrupt or missing UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: dmi.bios.date: 05/26/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.6 dmi.board.name: 09WH54 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 6 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.6:bd05/26/2016:svnDellInc.:pnPrecisionTower3620:pvr:rvnDellInc.:rn09WH54:rvrA00:cvnDellInc.:ct6:cvr: dmi.product.name: Precision Tower 3620 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1732766/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1732766] [NEW] firefox 57 does not display fish in fishgl.com on intel 530?
Public bug reported: On my two intel graphics Ubuntu 16.04 systems (both Dell 3620's), firefox does not display any fish; it simply shows the back wall. OpenGL vendor string: Intel Open Source Technology Center OpenGL renderer string: Mesa DRI Intel(R) HD Graphics 530 (Skylake GT2) OpenGL core profile version string: 4.5 (Core Profile) Mesa 17.0.7 OpenGL core profile shading language version string: 4.50 fishgl works fine in chrome, and on other ubuntu systems here. Affects both firefox 56.0+build6-0ubuntu0.16.04.2 and 57.0+build4-0ubuntu0.16.04.5 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: firefox 57.0+build4-0ubuntu0.16.04.5 ProcVersionSignature: Ubuntu 4.4.0-98.121-generic 4.4.90 Uname: Linux 4.4.0-98-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.1-0ubuntu2.12 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: dank 1843 F...m pulseaudio /dev/snd/controlC0: dank 1843 F pulseaudio /dev/snd/controlC1: dank 1843 F pulseaudio BuildID: 20171115095126 Channel: Unavailable Date: Thu Nov 16 10:55:39 2017 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) IpRoute: default via 10.10.1.1 dev enp0s31f6 10.0.3.0/24 dev lxcbr0 proto kernel scope link src 10.0.3.1 linkdown 10.10.0.0/16 dev enp0s31f6 proto kernel scope link src 10.10.130.236 169.254.0.0/16 dev enp0s31f6 scope link metric 1000 IwConfig: lono wireless extensions. enp0s31f6 no wireless extensions. lxcbr0no wireless extensions. Locales: extensions.sqlite corrupt or missing PrefSources: prefs.js ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Profiles: Profile0 (Default) - LastVersion=57.0/20171115095126 (In use) RfKill: RunningIncompatibleAddons: False SourcePackage: firefox Themes: extensions.sqlite corrupt or missing UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: dmi.bios.date: 05/26/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.6 dmi.board.name: 09WH54 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 6 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.6:bd05/26/2016:svnDellInc.:pnPrecisionTower3620:pvr:rvnDellInc.:rn09WH54:rvrA00:cvnDellInc.:ct6:cvr: dmi.product.name: Precision Tower 3620 dmi.sys.vendor: Dell Inc. ** Affects: firefox (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages 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/1732766 Title: firefox 57 does not display fish in fishgl.com on intel 530? Status in firefox package in Ubuntu: New Bug description: On my two intel graphics Ubuntu 16.04 systems (both Dell 3620's), firefox does not display any fish; it simply shows the back wall. OpenGL vendor string: Intel Open Source Technology Center OpenGL renderer string: Mesa DRI Intel(R) HD Graphics 530 (Skylake GT2) OpenGL core profile version string: 4.5 (Core Profile) Mesa 17.0.7 OpenGL core profile shading language version string: 4.50 fishgl works fine in chrome, and on other ubuntu systems here. Affects both firefox 56.0+build6-0ubuntu0.16.04.2 and 57.0+build4-0ubuntu0.16.04.5 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: firefox 57.0+build4-0ubuntu0.16.04.5 ProcVersionSignature: Ubuntu 4.4.0-98.121-generic 4.4.90 Uname: Linux 4.4.0-98-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.1-0ubuntu2.12 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: dank 1843 F...m pulseaudio /dev/snd/controlC0: dank 1843 F pulseaudio /dev/snd/controlC1: dank 1843 F pulseaudio BuildID: 20171115095126 Channel: Unavailable Date: Thu Nov 16 10:55:39 2017 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) IpRoute: default via 10.10.1.1 dev enp0s31f6 10.0.3.0/24 dev lxcbr0 proto kernel scope link src 10.0.3.1 linkdown 10.10.0.0/16 dev enp0s31f6 proto kernel scope link src 10.10.130.236 169.254.0.0/16 dev enp0s31f6 scope link metric 1000 IwConfig: lono wireless extensions. enp0s31f6 no wireless extensions. lxcbr0no wireless extensions. Locales: extensions.sqlite corrupt or missing PrefSources: prefs.js ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Profiles: Profile0 (Default) - LastVersion=57.0/20171115095126 (In use) RfKill: RunningIncompatibleAddons: False SourcePackage: firefox
[Desktop-packages] [Bug 1662418] Re: Can't view photos on SD card from Canon SX610 because "windows is hibernated"?!
Hah. I watched her do it. She inserted the SD card, then clicked on the dual boot Windows drive. So this is both a UX problem (user couldn't tell how to access an SD card) and a duplicate of bug 1362840. -- 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/1662418 Title: Can't view photos on SD card from Canon SX610 because "windows is hibernated"?! Status in nautilus package in Ubuntu: New Bug description: I got my wife a Canon SX610 HS camera for xmas. Alas, whenever she puts its SD card into our Ubuntu 16.04 computer to look at the pictures, she gets the error Unable to access "209 GB Volume" Error mounting /dev/sdb2 at /media/zilf/902C022F2C021140: Command-line `mount -t "ntfs" -o "uhelper=udisks2,nodev,nosuid,uid=1003,gid=1003" "/dev/sdb2" "/media/zilf/902C022F2C021140"' exited with non-zero exit status 14: Windows is hibernated, refused to mount. Failed to mount '/dev/sdb2': Operation not permitted The NTFS partition is in an unsafe state. Please resume and shutdown Windows fully (no hibernation or fast restarting), or mount the volume read-only with the 'ro' mount option. Nautilus should do the mount readonly rather than throwing an error. (Yeah, she won't be able to delete photos, but at least she'd be able to see them.) (This is related to bug 1362840, but that one is really Windows; this is a camera.) ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: nautilus 1:3.18.4.is.3.14.3-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40 Uname: Linux 4.4.0-62-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: Unity Date: Mon Feb 6 21:43:47 2017 GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' b"'890x550+65+422'" InstallationDate: Installed on 2016-11-06 (92 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) JournalErrors: Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] failed with exit code 1: Hint: You are currently not seeing messages from other users and the system. Users in the 'systemd-journal' group can see all messages. Pass -q to turn off this notice. No journal files were opened due to insufficient permissions. SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1662418/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1662418] [NEW] Can't view photos on SD card from Canon SX610 because "windows is hibernated"?!
Public bug reported: I got my wife a Canon SX610 HS camera for xmas. Alas, whenever she puts its SD card into our Ubuntu 16.04 computer to look at the pictures, she gets the error Unable to access "209 GB Volume" Error mounting /dev/sdb2 at /media/zilf/902C022F2C021140: Command-line `mount -t "ntfs" -o "uhelper=udisks2,nodev,nosuid,uid=1003,gid=1003" "/dev/sdb2" "/media/zilf/902C022F2C021140"' exited with non-zero exit status 14: Windows is hibernated, refused to mount. Failed to mount '/dev/sdb2': Operation not permitted The NTFS partition is in an unsafe state. Please resume and shutdown Windows fully (no hibernation or fast restarting), or mount the volume read-only with the 'ro' mount option. Nautilus should do the mount readonly rather than throwing an error. (Yeah, she won't be able to delete photos, but at least she'd be able to see them.) (This is related to bug 1362840, but that one is really Windows; this is a camera.) ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: nautilus 1:3.18.4.is.3.14.3-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40 Uname: Linux 4.4.0-62-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: Unity Date: Mon Feb 6 21:43:47 2017 GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' b"'890x550+65+422'" InstallationDate: Installed on 2016-11-06 (92 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) JournalErrors: Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] failed with exit code 1: Hint: You are currently not seeing messages from other users and the system. Users in the 'systemd-journal' group can see all messages. Pass -q to turn off this notice. No journal files were opened due to insufficient permissions. SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nautilus (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 nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1662418 Title: Can't view photos on SD card from Canon SX610 because "windows is hibernated"?! Status in nautilus package in Ubuntu: New Bug description: I got my wife a Canon SX610 HS camera for xmas. Alas, whenever she puts its SD card into our Ubuntu 16.04 computer to look at the pictures, she gets the error Unable to access "209 GB Volume" Error mounting /dev/sdb2 at /media/zilf/902C022F2C021140: Command-line `mount -t "ntfs" -o "uhelper=udisks2,nodev,nosuid,uid=1003,gid=1003" "/dev/sdb2" "/media/zilf/902C022F2C021140"' exited with non-zero exit status 14: Windows is hibernated, refused to mount. Failed to mount '/dev/sdb2': Operation not permitted The NTFS partition is in an unsafe state. Please resume and shutdown Windows fully (no hibernation or fast restarting), or mount the volume read-only with the 'ro' mount option. Nautilus should do the mount readonly rather than throwing an error. (Yeah, she won't be able to delete photos, but at least she'd be able to see them.) (This is related to bug 1362840, but that one is really Windows; this is a camera.) ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: nautilus 1:3.18.4.is.3.14.3-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40 Uname: Linux 4.4.0-62-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: Unity Date: Mon Feb 6 21:43:47 2017 GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' b"'890x550+65+422'" InstallationDate: Installed on 2016-11-06 (92 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) JournalErrors: Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] failed with exit code 1: Hint: You are currently not seeing messages from other users and the system. Users in the 'systemd-journal' group can see all messages. Pass -q to turn off this notice. No journal files were opened due to insufficient permissions. SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1662418/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1655709] [NEW] Spurious crash report dialog on every login
Public bug reported: For the last few years, on nearly all my computers, ubuntu has rewarded my logging in with a crash dialog. Nothing's actually wrong; xorg probably trips over its shoelaces every time it shuts down, but so late in the process that it doesn't matter. Today I went through the crash upload procedure, but no web browser window opened, so either I did something wrong, or the bug is marked 'ignore uploads' somehow... hence this manual report. This bug has to have been reported before, but has probably been marked WONTFIX or something because it is benign. But it does matter, and it's not benign, because I, my wife, and my son get those darn crash dialogs. It doesn't seem to matter what graphics card or driver is in use. Want the crash file left behind after the last upload? ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xserver-xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-43.63-generic 4.4.21 Uname: Linux 4.4.0-43-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.96 Sun Nov 8 22:33:28 PST 2015 GCC version: gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.2) .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Wed Jan 11 08:56:26 2017 DistUpgraded: 2016-04-26 16:26:11,919 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: xenial DistroVariant: ubuntu DpkgLog: ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GT215M [GeForce GTS 360M] [10de:0cb1] (rev a2) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GT215M [GeForce GTS 360M] [1043:203c] InstallationDate: Installed on 2014-07-18 (908 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) Lsusb: Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 04f2:b071 Chicony Electronics Co., Ltd 2.0M UVC Webcam / CNF7129 Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK Computer Inc. G60JX ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.4.0-43-generic root=UUID=28258489-6453-456a-9ecc-c41a02ad0631 ro rootflags=subvol=@ nomodeset quiet splash SourcePackage: xorg UpgradeStatus: Upgraded to xenial on 2016-04-26 (259 days ago) dmi.bios.date: 08/16/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 208 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: G60JX dmi.board.vendor: PEGATRON CORPORATION dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: PEGATRON Computer Inc. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr208:bd08/16/2010:svnASUSTeKComputerInc.:pnG60JX:pvr1.0:rvnPEGATRONCORPORATION:rnG60JX:rvr1.0:cvnPEGATRONComputerInc.:ct10:cvr1.0: dmi.product.name: G60JX dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK Computer Inc. version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Wed Jan 11 08:41:53 2017 xserver.configfile: default xserver.errors: open /dev/fb0: No such file or directory xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.18.3-1ubuntu2.3 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 third-party-packages ubuntu xenial -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1655709 Title: Spurious crash report dialog on every login Status in xorg package in Ubuntu: New Bug description: For the last few years, on nearly all my computers, ubuntu has rewarded my logging in with a
[Desktop-packages] [Bug 1639640] Re: haswell i915 black screen regression with DVI; VGA ok?
Not sure which package this should be against; since it might be DRM, maybe it should be against the linux kernel? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1639640 Title: haswell i915 black screen regression with DVI; VGA ok? Status in xserver-xorg-video-intel package in Ubuntu: New Bug description: After a recent update (early Nov 2016), my 16.04 system (an HP Pavillion 500-321, i.e. a generic i5-4570 system with integrated graphics) started showing a black screen on boot (after the grub menu finished). A fresh 16.10 live USB image also has the same problem on this system (but not on an nvidia system), as does a fresh 16.10 install. A fresh 16.04 install does NOT have the problem; the problem can be reproduced on this system by doing a fresh 16.04 install followed by letting it update automatically to the latest 16.04 packages. After some experimentation, I discovered that after booting up into the black screen, I could (usually?) rescue the session by pressing the computer's power button. This brought the screen to life, showing Ubuntu's "reboot or power down?" dialog. Cancelling that left you with a working system. I also discovered that if I booted first to text mode with sudo systemctl set-default multi-user.target and then after logging in via text mode, switch to graphics with startx or with sudo systemctl start graphical.target the screen also was fine. So, um, er, is it a race condition? Is graphical.target missing a wants? And what recent update could be introducing this problem? ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.1 ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21 Uname: Linux 4.4.0-45-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sun Nov 6 14:00:22 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [103c:2af7] InstallationDate: Installed on 2016-11-06 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Hewlett-Packard 500-321 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-45-generic root=UUID=a3be56db-508b-49ea-9d57-7f8270d98e4e ro SourcePackage: xserver-xorg-video-intel UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/27/2014 dmi.bios.vendor: AMI dmi.bios.version: 80.18 dmi.board.name: 2AF7 dmi.board.vendor: Hewlett-Packard dmi.board.version: 1.04 dmi.chassis.asset.tag: MXX4320BPH dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnAMI:bvr80.18:bd06/27/2014:svnHewlett-Packard:pn500-321:pvr1.00:rvnHewlett-Packard:rn2AF7:rvr1.04:cvnHewlett-Packard:ct3:cvr: dmi.product.name: 500-321 dmi.product.version: 1.00 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Sun Nov 6 13:52:03 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id9170 vendor ACI xserver.version: 2:1.18.3-1ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1639640/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1639640] Re: black screen at boot until pressing power-off button?
I booted with drm.debug=14 and looked at the output of dmesg. It had lines like [0.717202] [drm:i915_dump_device_info] i915 device info: gen=7, pciid=0x0412 rev=0x06 flags=need_gfx_hws,is_haswell,has_fbc,has_hotplug,has_llc,has_ddi,has_fpga_dbg, ... [0.938640] [drm:drm_helper_probe_single_connector_modes_merge_bits] [CONNECTOR:36:VGA-1] disconnected [0.938641] [drm:drm_helper_probe_single_connector_modes_merge_bits] [CONNECTOR:39:HDMI-A-1] [0.938642] [drm:intel_hdmi_detect] [CONNECTOR:39:HDMI-A-1] which made me realize: the drm driver cares a lot about which video connector you plug into. On a whim, I replaced the DVI video cable with a VGA one... and the problem went away! So, that's a better workaround for me: just use a vga cable. ** Summary changed: - black screen at boot until pressing power-off button? + haswell i915 black screen regression with DVI; VGA ok? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1639640 Title: haswell i915 black screen regression with DVI; VGA ok? Status in xserver-xorg-video-intel package in Ubuntu: New Bug description: After a recent update (early Nov 2016), my 16.04 system (an HP Pavillion 500-321, i.e. a generic i5-4570 system with integrated graphics) started showing a black screen on boot (after the grub menu finished). A fresh 16.10 live USB image also has the same problem on this system (but not on an nvidia system), as does a fresh 16.10 install. A fresh 16.04 install does NOT have the problem; the problem can be reproduced on this system by doing a fresh 16.04 install followed by letting it update automatically to the latest 16.04 packages. After some experimentation, I discovered that after booting up into the black screen, I could (usually?) rescue the session by pressing the computer's power button. This brought the screen to life, showing Ubuntu's "reboot or power down?" dialog. Cancelling that left you with a working system. I also discovered that if I booted first to text mode with sudo systemctl set-default multi-user.target and then after logging in via text mode, switch to graphics with startx or with sudo systemctl start graphical.target the screen also was fine. So, um, er, is it a race condition? Is graphical.target missing a wants? And what recent update could be introducing this problem? ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.1 ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21 Uname: Linux 4.4.0-45-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sun Nov 6 14:00:22 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [103c:2af7] InstallationDate: Installed on 2016-11-06 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Hewlett-Packard 500-321 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-45-generic root=UUID=a3be56db-508b-49ea-9d57-7f8270d98e4e ro SourcePackage: xserver-xorg-video-intel UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/27/2014 dmi.bios.vendor: AMI dmi.bios.version: 80.18 dmi.board.name: 2AF7 dmi.board.vendor: Hewlett-Packard dmi.board.version: 1.04 dmi.chassis.asset.tag: MXX4320BPH dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnAMI:bvr80.18:bd06/27/2014:svnHewlett-Packard:pn500-321:pvr1.00:rvnHewlett-Packard:rn2AF7:rvr1.04:cvnHewlett-Packard:ct3:cvr: dmi.product.name: 500-321 dmi.product.version: 1.00 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel
[Desktop-packages] [Bug 1639640] Re: black screen at boot until pressing power-off button?
Seems to have gotten worse with the next batch of updates (linux-image-4.4.0-47-generic:amd64); now it won't show a screen at all, even when booting to multiuser, after the kernel sets the graphics mode. Works fine if I give nomodeset, but then I can't use accelerated graphics. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1639640 Title: black screen at boot until pressing power-off button? Status in xserver-xorg-video-intel package in Ubuntu: New Bug description: After a recent update (early Nov 2016), my 16.04 system (an HP Pavillion 500-321, i.e. a generic i5-4570 system with integrated graphics) started showing a black screen on boot (after the grub menu finished). A fresh 16.10 live USB image also has the same problem on this system (but not on an nvidia system), as does a fresh 16.10 install. A fresh 16.04 install does NOT have the problem; the problem can be reproduced on this system by doing a fresh 16.04 install followed by letting it update automatically to the latest 16.04 packages. After some experimentation, I discovered that after booting up into the black screen, I could (usually?) rescue the session by pressing the computer's power button. This brought the screen to life, showing Ubuntu's "reboot or power down?" dialog. Cancelling that left you with a working system. I also discovered that if I booted first to text mode with sudo systemctl set-default multi-user.target and then after logging in via text mode, switch to graphics with startx or with sudo systemctl start graphical.target the screen also was fine. So, um, er, is it a race condition? Is graphical.target missing a wants? And what recent update could be introducing this problem? ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.1 ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21 Uname: Linux 4.4.0-45-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sun Nov 6 14:00:22 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [103c:2af7] InstallationDate: Installed on 2016-11-06 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Hewlett-Packard 500-321 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-45-generic root=UUID=a3be56db-508b-49ea-9d57-7f8270d98e4e ro SourcePackage: xserver-xorg-video-intel UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/27/2014 dmi.bios.vendor: AMI dmi.bios.version: 80.18 dmi.board.name: 2AF7 dmi.board.vendor: Hewlett-Packard dmi.board.version: 1.04 dmi.chassis.asset.tag: MXX4320BPH dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnAMI:bvr80.18:bd06/27/2014:svnHewlett-Packard:pn500-321:pvr1.00:rvnHewlett-Packard:rn2AF7:rvr1.04:cvnHewlett-Packard:ct3:cvr: dmi.product.name: 500-321 dmi.product.version: 1.00 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Sun Nov 6 13:52:03 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id9170 vendor ACI xserver.version: 2:1.18.3-1ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1639640/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to :
[Desktop-packages] [Bug 1639640] [NEW] black screen at boot until pressing power-off button?
Public bug reported: After a recent update (early Nov 2016), my 16.04 system (an HP Pavillion 500-321, i.e. a generic i5-4570 system with integrated graphics) started showing a black screen on boot (after the grub menu finished). A fresh 16.10 live USB image also has the same problem on this system (but not on an nvidia system), as does a fresh 16.10 install. A fresh 16.04 install does NOT have the problem; the problem can be reproduced on this system by doing a fresh 16.04 install followed by letting it update automatically to the latest 16.04 packages. After some experimentation, I discovered that after booting up into the black screen, I could (usually?) rescue the session by pressing the computer's power button. This brought the screen to life, showing Ubuntu's "reboot or power down?" dialog. Cancelling that left you with a working system. I also discovered that if I booted first to text mode with sudo systemctl set-default multi-user.target and then after logging in via text mode, switch to graphics with startx or with sudo systemctl start graphical.target the screen also was fine. So, um, er, is it a race condition? Is graphical.target missing a wants? And what recent update could be introducing this problem? ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.1 ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21 Uname: Linux 4.4.0-45-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sun Nov 6 14:00:22 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [103c:2af7] InstallationDate: Installed on 2016-11-06 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Hewlett-Packard 500-321 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-45-generic root=UUID=a3be56db-508b-49ea-9d57-7f8270d98e4e ro SourcePackage: xserver-xorg-video-intel UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/27/2014 dmi.bios.vendor: AMI dmi.bios.version: 80.18 dmi.board.name: 2AF7 dmi.board.vendor: Hewlett-Packard dmi.board.version: 1.04 dmi.chassis.asset.tag: MXX4320BPH dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnAMI:bvr80.18:bd06/27/2014:svnHewlett-Packard:pn500-321:pvr1.00:rvnHewlett-Packard:rn2AF7:rvr1.04:cvnHewlett-Packard:ct3:cvr: dmi.product.name: 500-321 dmi.product.version: 1.00 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Sun Nov 6 13:52:03 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id9170 vendor ACI xserver.version: 2:1.18.3-1ubuntu2 ** Affects: xserver-xorg-video-intel (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 ubuntu xenial -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1639640 Title: black screen at boot until pressing power-off button? Status in xserver-xorg-video-intel package in Ubuntu: New Bug description: After a recent update (early Nov 2016), my 16.04 system (an HP Pavillion 500-321, i.e. a generic i5-4570 system with integrated graphics) started showing a black screen on boot (after the grub menu finished). A fresh 16.10 live USB image also has the same problem on this system (but not on an nvidia system), as does a fresh 16.10 install. A fresh 16.04 install does NOT have the problem; the problem can be reproduced on this system by doing a fresh 16.04 install followed by
[Desktop-packages] [Bug 1531035] [NEW] system-config-printer hangs halfway through
Public bug reported: Did System Settings -> printers -> add -> find network printer, selected my printer, typed in my password... and it hung. Rebooting and retrying gave same results. ps shows dank 1649 0.0 0.2 615088 23396 ?Ssl 16:11 0:00 /usr/lib/x86_64-linux-gnu/indicator-printers/indicator-printers-service dank 2294 0.3 1.4 1146332 115808 ? Sl 16:11 0:03 /usr/bin/python3 /usr/share/system-config-printer/system-config-printer.py dank 3222 0.0 0.2 289168 18800 ?Sl 16:14 0:00 /usr/bin/python3 /usr/share/system-config-printer/install-printerdriver.py openprinting-gutenprint deb http://www.openprinting.org/download/printdriver/debian/ lsb3.2 contrib F8897B6F00075648E248B7EC24CBF5474CFD1E2F dank 0.0 0.0 13696 2208 pts/6S+ 16:29 0:00 grep --color=auto print dank@winky:~$ ps augxw | grep dpkg root 3443 0.0 0.0 0 0 pts/2ZN+ 16:15 0:00 [dpkg] root 3444 0.0 0.0 4476 856 pts/2SN+ 16:15 0:00 /bin/sh -c /usr/sbin/dpkg-preconfigure --apt || true root 3446 0.0 0.2 63152 18288 pts/2SN+ 16:15 0:00 /usr/bin/perl -w /usr/sbin/dpkg-preconfigure --apt root 3448 0.0 0.0 0 0 pts/2ZN+ 16:15 0:00 [dpkg-preconfigu] /var/log/apt/history.log shows Start-Date: 2016-01-04 16:10:39 Commandline: aptdaemon role='role-install-packages' sender=':1.113' Install: rpm2cpio:amd64 (4.12.0.1+dfsg1-3build2, automatic), lsb-multimedia:amd64 (4.1+Debian11ubuntu8, automatic), libpod-plainer-perl:amd64 (1.04-1, automatic), rpm-common:amd64 (4.12.0.1+dfsg1-3build2, automatic), lsb-languages:amd64 (4.1+Debian11ubuntu8, automatic), lsb-core:amd64 (4.1+Debian11ubuntu8, automatic), lib32z1:amd64 (1.2.8.dfsg-2ubuntu4, automatic), lsb-graphics:amd64 (4.1+Debian11ubuntu8, automatic), rpm:amd64 (4.12.0.1+dfsg1-3build2, automatic), librpm3:amd64 (4.12.0.1+dfsg1-3build2, automatic), lsb-cxx:amd64 (4.1+Debian11ubuntu8, automatic), lsb-desktop:amd64 (4.1+Debian11ubuntu8, automatic), debugedit:amd64 (4.12.0.1+dfsg1-3build2, automatic), pax:amd64 (20140703-2, automatic), openprinting-gutenprint:amd64 (5.2.7-1lsb3.2), librpmsign3:amd64 (4.12.0.1+dfsg1-3build2, automatic), alien:amd64 (8.94, automatic), lsb-security:amd64 (4.1+Debian11ubuntu8, automatic), librpmbuild3:amd64 (4.12.0.1+dfsg1-3build2, automatic), lsb:amd64 (4.1+Debian11ubuntu8, automatic), libjp eg62:amd64 (6b2-2, automatic), lsb-printing:amd64 (4.1+Debian11ubuntu8, automatic), librpmio3:amd64 (4.12.0.1+dfsg1-3build2, automatic) Error: Sub-process /usr/bin/dpkg exited unexpectedly End-Date: 2016-01-04 16:10:40 Doing 'sudo apt-get install rpm2cpio lsb-multimedia libpod-plainer-perl rpm-common lsb-languages lsb-core lib32z1 lsb-graphics rpm librpm3 lsb-cxx lsb-desktop debugedit pax openprinting-gutenprint librpmsign3 alien lsb-security librpmbuild3 lsb libjpeg62 lsb-printing librpmio3' failed with debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by another process: Resource temporarily unavailable dpkg: error processing package lsb-core (--configure): subprocess installed post-installation script returned error exit status 1 dank@winky:~$ sudo fuser -v /var/cache/debconf/config.dat USERPID ACCESS COMMAND /var/cache/debconf/config.dat: root 3446 F dpkg-preconfigu Killing 3446 didn't help, something just retried the operation. Killing install-printerdriver.py seemed to get things unstuck, showed me the "Choose Driver" dialog, was able to complete and print a test page. No idea why dpkg was originally unhappy. This may be a dup of bug 1307917. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: system-config-printer-common 1.5.7+20150819-0ubuntu4 ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6 Uname: Linux 4.2.0-19-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CurrentDesktop: Unity Date: Mon Jan 4 16:34:06 2016 InstallationDate: Installed on 2015-08-23 (134 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added. MachineType: Acer Aspire E5-573G PackageArchitecture: all Papersize: letter ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-19-generic root=UUID=726444db-9654-4ecb-b3f9-f96271673731 ro quiet splash vt.handoff=7 SourcePackage: system-config-printer UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: Upgraded to wily on 2015-11-27 (38 days ago) dmi.bios.date: 03/17/2015 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.07 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: ZORO_BH dmi.board.vendor: Acer dmi.board.version: Type2 - A01 Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias:
[Desktop-packages] [Bug 1334446] Re: Installing printer driver via control panel hangs
15.10 works for me! I'm willing to call it fixed. -- 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/1334446 Title: Installing printer driver via control panel hangs Status in system-config-printer package in Ubuntu: Confirmed Status in system-config-printer package in Fedora: Unknown Bug description: Trying to add a printer via system settings. Got to a messagebox that said "Installing driver openprinting-gutenprint. Installing..." and then hung at 50% progress. ps shows that dpkg and dpkg-preconfigure terminated, but no parent reaped them: dank 16336 0.6 0.9 1212316 111316 ? Sl 14:17 0:05 /usr/bin/python /usr/share/system-config-printer/system-config-printer.py dank 16434 0.0 0.0 238912 11924 ?Sl 14:22 0:00 /usr/bin/python /usr/share/system-config-printer/install-printerdriver.py openprinting-gutenprint deb http://www.openprinting.org/download/printdriver/debian/ lsb3.2 contrib F8897B6F00075648E248B7EC24CBF5474CFD1E2F root 16438 2.4 0.8 298400 99004 ?SNl 14:22 0:13 /usr/bin/python3 /usr/sbin/aptd root 16606 0.0 0.4 298400 57456 pts/39 SNs+ 14:23 0:00 /usr/bin/python3 /usr/sbin/aptd root 16607 0.0 0.0 0 0 pts/39 ZN+ 14:23 0:00 [dpkg] root 16608 0.0 0.0 648 pts/39 SN+ 14:23 0:00 /bin/sh -c /usr/sbin/dpkg-preconfigure --apt || true root 16609 0.0 0.1 64272 15816 pts/39 SN+ 14:23 0:00 /usr/bin/perl -w /usr/sbin/dpkg-preconfigure --apt root 16611 0.0 0.0 0 0 pts/39 ZN+ 14:23 0:00 [dpkg-preconfigu] Clicking cancel on the messagebox did nothing; everything was still hung. Looks like this was mentioned once before, http://ubuntuforums.org/showthread.php?t=2186209 Doing kill -HUP to the process "/usr/bin/python /usr/share/system-config-printer/system-config-printer.py" unblocked everything, and dpkg-cache policy reported that openprinting-gutenprint was installed. Control panel still didn't show the printer I'd wanted, so I tried it again, and this time it completed (slowly). ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: system-config-printer-gnome 1.4.3+20140219-0ubuntu2.1 ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2 Uname: Linux 3.13.0-29-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CupsErrorLog: Error: [Errno 13] Permission denied: '/var/log/cups/error_log' CurrentDesktop: Unity CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order /var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission denied Date: Wed Jun 25 14:31:21 2014 Lpstat: device for EPSON-Stylus-CX6600: ipps://trudge.local:631/printers/EPSON_Stylus_CX6600 MachineType: Dell Inc. Precision WorkStation T7500 PackageArchitecture: all Papersize: letter ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-29-generic root=UUID=114bd4a5-fd4b-4701-8155-506c50cb9da9 ro nomdmonddf nomdmonisw nomdmonddf nomdmonisw SourcePackage: system-config-printer UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/30/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A12 dmi.board.name: 06FW8P dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 7 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA12:bd10/30/2011:svnDellInc.:pnPrecisionWorkStationT7500:pvr:rvnDellInc.:rn06FW8P:rvrA02:cvnDellInc.:ct7:cvr: dmi.product.name: Precision WorkStation T7500 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/system-config-printer/+bug/1334446/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1521806] [NEW] undefined reference to glProgramUniform3fv when building opengl app
Public bug reported: A library which is being developed against the nvidia libGL.so fails to link against mesa's libGL.so. The linker complains: foo: undefined reference to `glProgramUniform1fv' foo: undefined reference to `glProgramUniform1i' foo: undefined reference to `glProgramUniform2fv' foo: undefined reference to `glProgramUniform3fv' foo: undefined reference to `glProgramUniform4fv' foo: undefined reference to `glProgramUniformMatrix3fv' foo: undefined reference to `glProgramUniformMatrix4fv' foo: undefined reference to `glXCreateContextAttribsARB' Is this expected behavior, punishing the developer for not using an extension loader, or something? Or should mesa export everything nvidia exports? Sounds like it's expected behavior, given http://sourceforge.net/p/mesa3d/mailman/message/26157363/ but I thought I'd file it in case some other OpenGL noob runs into it. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: libgl1-mesa-dev 10.1.3-0ubuntu0.4 ProcVersionSignature: Ubuntu 3.13.0-55.92-generic 3.13.11-ckt20 Uname: Linux 3.13.0-55-generic x86_64 NonfreeKernelModules: veth aufs xt_CHECKSUM iptable_mangle ipt_MASQUERADE iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack xt_tcpudp bridge stp llc iptable_filter ip_tables x_tables rfcomm bnep bluetooth coretemp crct10dif_pclmul crc32_pclmul ghash_clmulni_intel vmw_balloon aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd serio_raw vmwgfx ppdev ttm parport_pc lp parport drm shpchp mac_hid vmw_vmci i2c_piix4 psmouse vmw_pvscsi vmxnet3 mptspi e1000 floppy mptscsih mptbase pata_acpi ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 Date: Tue Dec 1 15:29:17 2015 ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: mesa UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: mesa (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1521806 Title: undefined reference to glProgramUniform3fv when building opengl app Status in mesa package in Ubuntu: New Bug description: A library which is being developed against the nvidia libGL.so fails to link against mesa's libGL.so. The linker complains: foo: undefined reference to `glProgramUniform1fv' foo: undefined reference to `glProgramUniform1i' foo: undefined reference to `glProgramUniform2fv' foo: undefined reference to `glProgramUniform3fv' foo: undefined reference to `glProgramUniform4fv' foo: undefined reference to `glProgramUniformMatrix3fv' foo: undefined reference to `glProgramUniformMatrix4fv' foo: undefined reference to `glXCreateContextAttribsARB' Is this expected behavior, punishing the developer for not using an extension loader, or something? Or should mesa export everything nvidia exports? Sounds like it's expected behavior, given http://sourceforge.net/p/mesa3d/mailman/message/26157363/ but I thought I'd file it in case some other OpenGL noob runs into it. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: libgl1-mesa-dev 10.1.3-0ubuntu0.4 ProcVersionSignature: Ubuntu 3.13.0-55.92-generic 3.13.11-ckt20 Uname: Linux 3.13.0-55-generic x86_64 NonfreeKernelModules: veth aufs xt_CHECKSUM iptable_mangle ipt_MASQUERADE iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack xt_tcpudp bridge stp llc iptable_filter ip_tables x_tables rfcomm bnep bluetooth coretemp crct10dif_pclmul crc32_pclmul ghash_clmulni_intel vmw_balloon aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd serio_raw vmwgfx ppdev ttm parport_pc lp parport drm shpchp mac_hid vmw_vmci i2c_piix4 psmouse vmw_pvscsi vmxnet3 mptspi e1000 floppy mptscsih mptbase pata_acpi ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 Date: Tue Dec 1 15:29:17 2015 ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: mesa UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1521806/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1487748] Re: Touchpad not recognized in Aspire E15 e5-573g-59c3
Workaround: at boot, press F2 to get into BIOS, then set trackpad to Basic instead of Advanced. This even lets you scroll with a two-fingered gesture, and changes the output of cat /proc/bus/input/devices to: I: Bus=0011 Vendor=0002 Product=0007 Version=01b1 N: Name=SynPS/2 Synaptics TouchPad P: Phys=isa0060/serio1/input0 S: Sysfs=/devices/platform/i8042/serio1/input/input6 U: Uniq= H: Handlers=mouse1 event8 B: PROP=5 B: EV=b B: KEY=e520 61 0 0 0 0 B: ABS=66080001103 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-synaptics in Ubuntu. https://bugs.launchpad.net/bugs/1487748 Title: Touchpad not recognized in Aspire E15 e5-573g-59c3 Status in xserver-xorg-input-synaptics package in Ubuntu: New Bug description: Live booting Ubuntu 15.04 via USB key worked, but touchpad and wifi didn't work, had to plug in a mouse and ethernet. This report is about the touchpad. cat /proc/bus/input/devices says I: Bus=0018 Vendor=06cb Product=2970 Version=0100 N: Name=SYN1B81:01 06CB:2970 UNKNOWN P: Phys= S: Sysfs=/devices/pci:00/INT3432:00/i2c-8/i2c-SYN1B81:01/0018:06CB:2970.0001/input/input14 U: Uniq= H: Handlers=mouse0 event13 B: PROP=5 B: EV=b B: KEY=6420 1 0 0 0 0 B: ABS=2608003 ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xserver-xorg-input-synaptics 1.8.1-1ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CasperVersion: 1.360 CurrentDesktop: Unity Date: Sat Aug 22 18:23:44 2015 DistUpgraded: Fresh install DistroCodename: vivid DistroVariant: ubuntu LiveMediaBuild: Ubuntu 15.04 Vivid Vervet - Release amd64 (20150422) MachineType: Acer Aspire E5-573G ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/username.seed boot=casper quiet splash --- SourcePackage: xserver-xorg-input-synaptics UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/17/2015 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.07 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: ZORO_BH dmi.board.vendor: Acer dmi.board.version: Type2 - A01 Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.07:bd03/17/2015:svnAcer:pnAspireE5-573G:pvrV3.72:rvnAcer:rnZORO_BH:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.name: Aspire E5-573G dmi.product.version: V3.72 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.12.1+15.04.20150410.1-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.60-2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.2-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2build1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2build1 xserver.bootTime: Sat Aug 22 09:32:26 2015 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 16620 vendor AUO xserver.version: 2:1.17.1-0ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/1487748/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1487748] [NEW] Touchpad not recognized in Aspire E15 e5-573g-59c3
Public bug reported: Live booting Ubuntu 15.04 via USB key worked, but touchpad and wifi didn't work, had to plug in a mouse and ethernet. This report is about the touchpad. cat /proc/bus/input/devices says I: Bus=0018 Vendor=06cb Product=2970 Version=0100 N: Name=SYN1B81:01 06CB:2970 UNKNOWN P: Phys= S: Sysfs=/devices/pci:00/INT3432:00/i2c-8/i2c-SYN1B81:01/0018:06CB:2970.0001/input/input14 U: Uniq= H: Handlers=mouse0 event13 B: PROP=5 B: EV=b B: KEY=6420 1 0 0 0 0 B: ABS=2608003 ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xserver-xorg-input-synaptics 1.8.1-1ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CasperVersion: 1.360 CurrentDesktop: Unity Date: Sat Aug 22 18:23:44 2015 DistUpgraded: Fresh install DistroCodename: vivid DistroVariant: ubuntu LiveMediaBuild: Ubuntu 15.04 Vivid Vervet - Release amd64 (20150422) MachineType: Acer Aspire E5-573G ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/username.seed boot=casper quiet splash --- SourcePackage: xserver-xorg-input-synaptics UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/17/2015 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.07 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: ZORO_BH dmi.board.vendor: Acer dmi.board.version: Type2 - A01 Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.07:bd03/17/2015:svnAcer:pnAspireE5-573G:pvrV3.72:rvnAcer:rnZORO_BH:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.name: Aspire E5-573G dmi.product.version: V3.72 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.12.1+15.04.20150410.1-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.60-2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.2-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2build1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2build1 xserver.bootTime: Sat Aug 22 09:32:26 2015 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 16620 vendor AUO xserver.version: 2:1.17.1-0ubuntu3 ** Affects: xserver-xorg-input-synaptics (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug ubuntu vivid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-synaptics in Ubuntu. https://bugs.launchpad.net/bugs/1487748 Title: Touchpad not recognized in Aspire E15 e5-573g-59c3 Status in xserver-xorg-input-synaptics package in Ubuntu: New Bug description: Live booting Ubuntu 15.04 via USB key worked, but touchpad and wifi didn't work, had to plug in a mouse and ethernet. This report is about the touchpad. cat /proc/bus/input/devices says I: Bus=0018 Vendor=06cb Product=2970 Version=0100 N: Name=SYN1B81:01 06CB:2970 UNKNOWN P: Phys= S: Sysfs=/devices/pci:00/INT3432:00/i2c-8/i2c-SYN1B81:01/0018:06CB:2970.0001/input/input14 U: Uniq= H: Handlers=mouse0 event13 B: PROP=5 B: EV=b B: KEY=6420 1 0 0 0 0 B: ABS=2608003 ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xserver-xorg-input-synaptics 1.8.1-1ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CasperVersion: 1.360 CurrentDesktop: Unity Date: Sat Aug 22 18:23:44 2015 DistUpgraded: Fresh install DistroCodename: vivid DistroVariant: ubuntu LiveMediaBuild: Ubuntu 15.04 Vivid Vervet - Release amd64 (20150422) MachineType: Acer Aspire E5-573G ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/username.seed boot=casper quiet splash --- SourcePackage: xserver-xorg-input-synaptics UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/17/2015 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.07 dmi.board.asset.tag: Type2 - Board
[Desktop-packages] [Bug 1334446] Re: Installing printer driver via control panel hangs
I see upstream calls it fixed. Problem still happening in ubuntu 15.04. Is the fix in ubuntu 15.10 alpha? I could test that. -- 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/1334446 Title: Installing printer driver via control panel hangs Status in system-config-printer package in Ubuntu: Confirmed Status in system-config-printer package in Fedora: Unknown Bug description: Trying to add a printer via system settings. Got to a messagebox that said Installing driver openprinting-gutenprint. Installing... and then hung at 50% progress. ps shows that dpkg and dpkg-preconfigure terminated, but no parent reaped them: dank 16336 0.6 0.9 1212316 111316 ? Sl 14:17 0:05 /usr/bin/python /usr/share/system-config-printer/system-config-printer.py dank 16434 0.0 0.0 238912 11924 ?Sl 14:22 0:00 /usr/bin/python /usr/share/system-config-printer/install-printerdriver.py openprinting-gutenprint deb http://www.openprinting.org/download/printdriver/debian/ lsb3.2 contrib F8897B6F00075648E248B7EC24CBF5474CFD1E2F root 16438 2.4 0.8 298400 99004 ?SNl 14:22 0:13 /usr/bin/python3 /usr/sbin/aptd root 16606 0.0 0.4 298400 57456 pts/39 SNs+ 14:23 0:00 /usr/bin/python3 /usr/sbin/aptd root 16607 0.0 0.0 0 0 pts/39 ZN+ 14:23 0:00 [dpkg] defunct root 16608 0.0 0.0 648 pts/39 SN+ 14:23 0:00 /bin/sh -c /usr/sbin/dpkg-preconfigure --apt || true root 16609 0.0 0.1 64272 15816 pts/39 SN+ 14:23 0:00 /usr/bin/perl -w /usr/sbin/dpkg-preconfigure --apt root 16611 0.0 0.0 0 0 pts/39 ZN+ 14:23 0:00 [dpkg-preconfigu] defunct Clicking cancel on the messagebox did nothing; everything was still hung. Looks like this was mentioned once before, http://ubuntuforums.org/showthread.php?t=2186209 Doing kill -HUP to the process /usr/bin/python /usr/share/system-config-printer/system-config-printer.py unblocked everything, and dpkg-cache policy reported that openprinting-gutenprint was installed. Control panel still didn't show the printer I'd wanted, so I tried it again, and this time it completed (slowly). ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: system-config-printer-gnome 1.4.3+20140219-0ubuntu2.1 ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2 Uname: Linux 3.13.0-29-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CupsErrorLog: Error: [Errno 13] Permission denied: '/var/log/cups/error_log' CurrentDesktop: Unity CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order /var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission denied Date: Wed Jun 25 14:31:21 2014 Lpstat: device for EPSON-Stylus-CX6600: ipps://trudge.local:631/printers/EPSON_Stylus_CX6600 MachineType: Dell Inc. Precision WorkStation T7500 PackageArchitecture: all Papersize: letter ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-29-generic root=UUID=114bd4a5-fd4b-4701-8155-506c50cb9da9 ro nomdmonddf nomdmonisw nomdmonddf nomdmonisw SourcePackage: system-config-printer UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/30/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A12 dmi.board.name: 06FW8P dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 7 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA12:bd10/30/2011:svnDellInc.:pnPrecisionWorkStationT7500:pvr:rvnDellInc.:rn06FW8P:rvrA02:cvnDellInc.:ct7:cvr: dmi.product.name: Precision WorkStation T7500 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/system-config-printer/+bug/1334446/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1276186] Re: System becomes unresponsive, ibus-ui-daemon takes ~150 % cpu
Bug 1271839 may be related. I saw both the high CPU usage and extreme RAM usage (about 1 megabyte/second leak). It happened when I minimized Chrome, but continued long after I killed all the chrome processes. ibus-ui-gtk3 got up to 2+ gigabytes of ram pretty quickly. Putting more details at bug 1271839. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1276186 Title: System becomes unresponsive, ibus-ui-daemon takes ~150 % cpu Status in ibus package in Ubuntu: Confirmed Bug description: As stated the graphical desktop became unresponsive. Dropping to CTRL + ALT + F1 terminal and `top`showed ibus-ui-daemon taking around 150 % cpu time and ibus-ui-gtk3 taking around 50 % cpu time. (names may contain minor errors) Tried to kill processes, rebooted. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: ibus 1.5.3-6ubuntu2.1 ProcVersionSignature: Ubuntu 3.11.0-15.25-generic 3.11.10 Uname: Linux 3.11.0-15-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 Date: Tue Feb 4 16:41:03 2014 InstallationDate: Installed on 2013-09-10 (147 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MarkForUpload: True SourcePackage: ibus UpgradeStatus: Upgraded to saucy on 2013-10-23 (104 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1276186/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1271839] Re: ibus-ui-gtk3 big memory leak
Bug 1276186 may be an acute form of this bug. I saw both the high CPU usage and extreme RAM usage (about 1 megabyte/second leak). It happened when I minimized Chrome, but continued long after I killed all the chrome processes. ibus-ui-gtk3 got up to 2+ gigabytes of ram pretty quickly. I'll attach an apport log. I guess I could figure out how to valgrind the app by disabling ibus in System Settings / Language Support, then following https://code.google.com/p/ibus/wiki/IBusStartUpTroubleShooting, or maybe by looking at the startup hook installed by im-config and modifying it. But since I don't need an input method, I may just live with ibus disabled. ** Attachment added: apport.ibus.ptzz6wvv.apport https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1271839/+attachment/4365915/+files/apport.ibus.ptzz6wvv.apport -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1271839 Title: ibus-ui-gtk3 big memory leak Status in ibus package in Ubuntu: Expired Bug description: ubuntu 13.10 64bit 2gb of memory leak Also seen on Ubuntu 14.04 64Bit To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1271839/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1436640] Re: gnome-keyring chews CPU and disk for 40 seconds on chrome startup
On a slower Ubuntu 14.10 system (AMD e-450) with chrome 39.0.2171.95, it takes longer (90 seconds of cpu?) to finish. A few seconds after the churning stops, I see: $ ps augxw | grep keyr dank 2103 32.7 0.6 384248 25184 ?SLl 13:32 1:28 /usr/bin/gnome-keyring-daemon --daemonize --login dank 6019 0.0 0.0 13680 2104 pts/7S+ 13:36 0:00 grep keyr -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1436640 Title: gnome-keyring chews CPU and disk for 40 seconds on chrome startup Status in chromium-browser package in Ubuntu: New Bug description: To reproduce: 0) start top 1) start chrome 2) watch disk light flash; watch cpu activity for gnome-keyring peg; notice gnome-keyring in D state; notice chrome and whole machine responding poorly 3) 40 seconds later, system returns to normal, and chrome beings responding quickly as expected. This is ironic and annoying, since I never use gnome's keyring. Ever. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gnome-keyring 3.10.1-1ubuntu4.1 ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11 Uname: Linux 3.13.0-43-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 CurrentDesktop: Unity Date: Wed Mar 25 19:52:44 2015 InstallationDate: Installed on 2014-07-18 (251 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) SourcePackage: gnome-keyring UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1436640/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1436640] [NEW] gnome-keyring chews CPU and disk for 40 seconds on chrome startup
Public bug reported: To reproduce: 0) start top 1) start chrome 2) watch disk light flash; watch cpu activity for gnome-keyring peg; notice gnome-keyring in D state; notice chrome and whole machine responding poorly 3) 40 seconds later, system returns to normal, and chrome beings responding quickly as expected. This is ironic and annoying, since I never use gnome's keyring. Ever. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gnome-keyring 3.10.1-1ubuntu4.1 ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11 Uname: Linux 3.13.0-43-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 CurrentDesktop: Unity Date: Wed Mar 25 19:52:44 2015 InstallationDate: Installed on 2014-07-18 (251 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) SourcePackage: gnome-keyring UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-keyring (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1436640 Title: gnome-keyring chews CPU and disk for 40 seconds on chrome startup Status in gnome-keyring package in Ubuntu: New Bug description: To reproduce: 0) start top 1) start chrome 2) watch disk light flash; watch cpu activity for gnome-keyring peg; notice gnome-keyring in D state; notice chrome and whole machine responding poorly 3) 40 seconds later, system returns to normal, and chrome beings responding quickly as expected. This is ironic and annoying, since I never use gnome's keyring. Ever. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gnome-keyring 3.10.1-1ubuntu4.1 ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11 Uname: Linux 3.13.0-43-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 CurrentDesktop: Unity Date: Wed Mar 25 19:52:44 2015 InstallationDate: Installed on 2014-07-18 (251 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) SourcePackage: gnome-keyring UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1436640/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1436640] Re: gnome-keyring chews CPU and disk for 40 seconds on chrome startup
dank@i5:~$ ls -l ~/.local/share/keyrings/ insgesamt 564 -rw--- 1 dank dank 569425 Mar 25 19:51 login.keyring -rw--- 1 dank dank207 Jul 7 2013 user.keystore See also https://productforums.google.com/forum/#!topic/chrome/0nLjeCisf1A and http://code.google.com/p/chromium/issues/detail?id=98601#c35 and https://src.chromium.org/svn/trunk/src/chrome/browser/password_manager/native_backend_gnome_x_unittest.cc https://src.chromium.org/svn/trunk/src/chrome/browser/password_manager/native_backend_gnome_x.cc Evidently chrome uses gnome-keyring, and beats the crap out of it while syncing password stores with the cloud. ** Bug watch added: code.google.com/p/chromium/issues #98601 http://code.google.com/p/chromium/issues/detail?id=98601 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1436640 Title: gnome-keyring chews CPU and disk for 40 seconds on chrome startup Status in gnome-keyring package in Ubuntu: New Bug description: To reproduce: 0) start top 1) start chrome 2) watch disk light flash; watch cpu activity for gnome-keyring peg; notice gnome-keyring in D state; notice chrome and whole machine responding poorly 3) 40 seconds later, system returns to normal, and chrome beings responding quickly as expected. This is ironic and annoying, since I never use gnome's keyring. Ever. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gnome-keyring 3.10.1-1ubuntu4.1 ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11 Uname: Linux 3.13.0-43-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 CurrentDesktop: Unity Date: Wed Mar 25 19:52:44 2015 InstallationDate: Installed on 2014-07-18 (251 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) SourcePackage: gnome-keyring UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1436640/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1314367] Re: Flickering with Ubuntu 14.04 and nvidia card reappeared
fwiw: I hit this using the latest from Nvidia's download site, and also using the xorg-edgers ppa ( 346.47-0ubuntu1-xedgers14.04.1 ). The flipping in the terminal seems to be at the same speed as the cursor blink. I only noticed it in gnome terminal. xterm does not exhibit the problem. My system's a Dell T7500 with a Geforce gtx 570 running somewhat up to date ubuntu 14.04.1 CCSMWorkaroundsForce synchronization between X and GLX seemed to help a bit initially, but the problem is still present enough to make gnome terminal nearly unusable. nvidia-settings -a GPUPowerMizerMode=1 seems to help more. With that, I haven't seen the flipping in my 30 seconds of extensive testing. Like Tom, I don't think I can install a new OS on this system, but I guess I might have time to boot the live cd sometime. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1314367 Title: Flickering with Ubuntu 14.04 and nvidia card reappeared Status in xorg package in Ubuntu: Incomplete Bug description: As requested in Bug #1310633 I'm opening a new bug. With a previous version of Ubuntu I already had this flickering. With additional options for the kernel module I was able to fix the flickering. options nvidia NVreg_RegistryDwords=PerfLevelSrc=0x NVreg_Mobile=3 NVreg_ModifyDeviceFiles=0 With version 14.04 and the nvidia-331 (331.38-0ubuntu7) driver the flickering reappeared although the line is still present in options.conf. Using modprobe --resolve-alias nvidia I found the correct driver module name which in my case is nvidia_331. Changing the module name in options.conf to nvidia_331 X doesn't start anymore. Removing the NVreg_ModifyDeviceFiles option X is starting again, but does not solve the issue. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 331.38 Wed Jan 8 19:32:30 PST 2014 GCC version: gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: Unity Date: Tue Apr 29 21:09:41 2014 DistUpgraded: 2014-04-17 23:47:50,572 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: bbswitch, 0.7, 3.13.0-24-generic, x86_64: installed nvidia-331, 331.38, 3.13.0-24-generic, x86_64: installed vboxhost, 4.3.10, 3.13.0-24-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GT215GLM [Quadro FX 1800M] [10de:0cbc] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:1521] InstallationDate: Installed on 2012-11-17 (528 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) MachineType: Hewlett-Packard HP EliteBook 8540w PccardctlStatus: Socket 0: 3.3V 16-bit PC Card Subdevice 0 (function 0) bound to driver pata_pcmcia ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic root=UUID=c6af930a-63f1-4015-9c42-bdde793e3e5a ro quiet splash SourcePackage: xorg UpgradeStatus: Upgraded to trusty on 2014-04-17 (11 days ago) dmi.bios.date: 09/13/2013 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68CVD Ver. F.24 dmi.board.name: 1521 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 32.35 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68CVDVer.F.24:bd09/13/2013:svnHewlett-Packard:pnHPEliteBook8540w:pvr:rvnHewlett-Packard:rn1521:rvrKBCVersion32.35:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP EliteBook 8540w dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.11+14.04.20140409-0ubuntu1 version.ia32-libs: ia32-libs 20090808ubuntu36 version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu5 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu5 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime:
[Desktop-packages] [Bug 1153934] Re: Some radio streams which used to play OK don't play after updating to rhythmbox 2.98 or higher due a libsoup bug
Not fixed in trusty? On a fresh vanilla trusty, clicking on http://www.radioberlin.de/live.m3u brings up rhythmbox but it fails to play, complaining could not determine type of stream. I killed gvfsd-http and clicked on the new station in Radio, and this time it installed the needed plugins and started playing, but I didn't try clicking on the new station in Radio without killing first. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libsoup2.4 in Ubuntu. https://bugs.launchpad.net/bugs/1153934 Title: Some radio streams which used to play OK don't play after updating to rhythmbox 2.98 or higher due a libsoup bug Status in Soup HTTP Library: Fix Released Status in “libsoup2.4” package in Ubuntu: Fix Released Bug description: The following stream, which I have saved in Radio: http://radioclasica.rtve.stream.flumotion.com/rtve/radioclasica.mp3.m3u used to play perfectly (heard it daily) with the previous version of rhythmbox, but after upgrading to Ubuntu 13.04 which brought a new version does not play any more. Some other streams still play perfectly, for instance: http://www.catmusica.cat/directes/catmusica_wm.m3u After clicking the radio nothing happens, it doesn't play the stream or produces any other message whatsoever WORKAROUND: Run the command sudo killall gvfsd-http after playing a station. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: libgstreamer0.10-0 0.10.36-1ubuntu2 ProcVersionSignature: Ubuntu 3.8.0-11.20-generic 3.8.2 Uname: Linux 3.8.0-11-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.9.1-0ubuntu1 Architecture: amd64 Date: Tue Mar 12 08:22:27 2013 InstallationDate: Installed on 2010-10-25 (868 days ago) InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release amd64 (20101007) MarkForUpload: True SourcePackage: gstreamer0.10 UpgradeStatus: Upgraded to raring on 2013-03-01 (10 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/libsoup/+bug/1153934/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1334446] [NEW] Installing printer driver via control panel hangs
Public bug reported: Trying to add a printer via system settings. Got to a messagebox that said Installing driver openprinting-gutenprint. Installing... and then hung at 50% progress. ps shows that dpkg and dpkg-preconfigure terminated, but no parent reaped them: dank 16336 0.6 0.9 1212316 111316 ? Sl 14:17 0:05 /usr/bin/python /usr/share/system-config-printer/system-config-printer.py dank 16434 0.0 0.0 238912 11924 ?Sl 14:22 0:00 /usr/bin/python /usr/share/system-config-printer/install-printerdriver.py openprinting-gutenprint deb http://www.openprinting.org/download/printdriver/debian/ lsb3.2 contrib F8897B6F00075648E248B7EC24CBF5474CFD1E2F root 16438 2.4 0.8 298400 99004 ?SNl 14:22 0:13 /usr/bin/python3 /usr/sbin/aptd root 16606 0.0 0.4 298400 57456 pts/39 SNs+ 14:23 0:00 /usr/bin/python3 /usr/sbin/aptd root 16607 0.0 0.0 0 0 pts/39 ZN+ 14:23 0:00 [dpkg] defunct root 16608 0.0 0.0 648 pts/39 SN+ 14:23 0:00 /bin/sh -c /usr/sbin/dpkg-preconfigure --apt || true root 16609 0.0 0.1 64272 15816 pts/39 SN+ 14:23 0:00 /usr/bin/perl -w /usr/sbin/dpkg-preconfigure --apt root 16611 0.0 0.0 0 0 pts/39 ZN+ 14:23 0:00 [dpkg-preconfigu] defunct Clicking cancel on the messagebox did nothing; everything was still hung. Looks like this was mentioned once before, http://ubuntuforums.org/showthread.php?t=2186209 Doing kill -HUP to the process /usr/bin/python /usr/share/system-config-printer/system-config-printer.py unblocked everything, and dpkg-cache policy reported that openprinting-gutenprint was installed. Control panel still didn't show the printer I'd wanted, so I tried it again, and this time it completed (slowly). ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: system-config-printer-gnome 1.4.3+20140219-0ubuntu2.1 ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2 Uname: Linux 3.13.0-29-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CupsErrorLog: Error: [Errno 13] Permission denied: '/var/log/cups/error_log' CurrentDesktop: Unity CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order /var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission denied Date: Wed Jun 25 14:31:21 2014 Lpstat: device for EPSON-Stylus-CX6600: ipps://trudge.local:631/printers/EPSON_Stylus_CX6600 MachineType: Dell Inc. Precision WorkStation T7500 PackageArchitecture: all Papersize: letter ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-29-generic root=UUID=114bd4a5-fd4b-4701-8155-506c50cb9da9 ro nomdmonddf nomdmonisw nomdmonddf nomdmonisw SourcePackage: system-config-printer UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/30/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A12 dmi.board.name: 06FW8P dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 7 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA12:bd10/30/2011:svnDellInc.:pnPrecisionWorkStationT7500:pvr:rvnDellInc.:rn06FW8P:rvrA02:cvnDellInc.:ct7:cvr: dmi.product.name: Precision WorkStation T7500 dmi.sys.vendor: Dell Inc. ** Affects: system-config-printer (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages trusty -- 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/1334446 Title: Installing printer driver via control panel hangs Status in “system-config-printer” package in Ubuntu: New Bug description: Trying to add a printer via system settings. Got to a messagebox that said Installing driver openprinting-gutenprint. Installing... and then hung at 50% progress. ps shows that dpkg and dpkg-preconfigure terminated, but no parent reaped them: dank 16336 0.6 0.9 1212316 111316 ? Sl 14:17 0:05 /usr/bin/python /usr/share/system-config-printer/system-config-printer.py dank 16434 0.0 0.0 238912 11924 ?Sl 14:22 0:00 /usr/bin/python /usr/share/system-config-printer/install-printerdriver.py openprinting-gutenprint deb http://www.openprinting.org/download/printdriver/debian/ lsb3.2 contrib F8897B6F00075648E248B7EC24CBF5474CFD1E2F root 16438 2.4 0.8 298400 99004 ?SNl 14:22 0:13 /usr/bin/python3 /usr/sbin/aptd root 16606 0.0 0.4 298400 57456 pts/39 SNs+ 14:23 0:00 /usr/bin/python3 /usr/sbin/aptd root 16607 0.0 0.0 0 0 pts/39 ZN+ 14:23 0:00 [dpkg] defunct root 16608 0.0 0.0 648 pts/39 SN+ 14:23 0:00 /bin/sh -c /usr/sbin/dpkg-preconfigure --apt || true root 16609 0.0 0.1 64272 15816 pts/39 SN+ 14:23 0:00 /usr/bin/perl -w /usr/sbin/dpkg-preconfigure --apt root 16611 0.0 0.0 0 0 pts/39 ZN+ 14:23 0:00 [dpkg-preconfigu] defunct
[Desktop-packages] [Bug 1305202] [NEW] workplace switcher not active by default, contradicting doc
Public bug reported: In Trusty beta 2, fully updated, the workplace switcher is not active by default. This contradicts the doc, https://help.ubuntu.com/14.04/ubuntu-help/shell-windows.html I had to turn to a a third party page, http://iloveubuntu.net/ubuntu-1404-received-improved-keyboard-shortcuts-workspaces to see how to enable it. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140404-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8 Uname: Linux 3.13.0-23-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Wed Apr 9 10:28:55 2014 InstallationDate: Installed on 2014-04-07 (1 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Beta amd64 (20140326) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dp-unity https://bugs.launchpad.net/bugs/1305202 Title: workplace switcher not active by default, contradicting doc Status in “unity” package in Ubuntu: New Bug description: In Trusty beta 2, fully updated, the workplace switcher is not active by default. This contradicts the doc, https://help.ubuntu.com/14.04/ubuntu-help/shell-windows.html I had to turn to a a third party page, http://iloveubuntu.net/ubuntu-1404-received-improved-keyboard-shortcuts-workspaces to see how to enable it. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140404-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8 Uname: Linux 3.13.0-23-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Wed Apr 9 10:28:55 2014 InstallationDate: Installed on 2014-04-07 (1 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Beta amd64 (20140326) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1305202/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 538691] Re: no versioned library symlinks provided for libGL in /usr/lib
google earth may not have had correct dependencies. -- 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/538691 Title: no versioned library symlinks provided for libGL in /usr/lib Status in “mesa” package in Ubuntu: Opinion Bug description: In the current lucid package libGL.so.1 is no longer installed under /usr/lib Many programs are built against this versioned library, and the versioned library is available in debian and in ubuntu karmic. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/538691/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1219583] Re: SANE does not work anymore with Epson Perfection 1650. Used to work perfectly.
Please import sane-backends in time for 14.04... -- 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/1219583 Title: SANE does not work anymore with Epson Perfection 1650. Used to work perfectly. Status in “sane-backends” package in Ubuntu: New Status in “sane-backends” package in Debian: Fix Released Bug description: On my plain vanilla ubuntu 13.04 system, with an Epson Perfection 1650 scanner plugged in, clicking 'Scan' in xsane, or running scanimage, yielded a short scan run and the message '[epson2] e2_ext_read: cancel request received' on stderr. This turns out to be caused by the commit commit 63a8dd4ebc9535b23d7a922cb0e7a9a682edd955 Author: Alessandro Zummo a.zu...@towertech.it Date: Sat Jan 9 23:21:50 2010 +0100 epson2: improved error detection as guessed by a comment in the related Debian bug report http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=597922#127 which also had a spot-on suggestion for how to fix it. I've attached the draft patch to http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=597922#215 There is also an upstream bug report, https://alioth.debian.org/tracker/?group_id=30186atid=410366func=detailaid=312793 but I have not been able to comment there (alioth's login system defeated me). That upstream bug report also has a simple workaround (edit /etc/sane.d/dll.conf to uncomment epson and comment epson2), but a real fix would be nice. So, assuming no upstream release before 13.10, how about adding my patch? I'd be happy to submit it in a more ubuntu-friendly form. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: libsane 1.0.23-0ubuntu1 [modified: usr/lib/x86_64-linux-gnu/sane/libsane-epson2.so.1.0.23] ProcVersionSignature: Ubuntu 3.8.0-29.42-generic 3.8.13.5 Uname: Linux 3.8.0-29-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.9.2-0ubuntu8.3 Architecture: amd64 Date: Sun Sep 1 16:09:30 2013 InstallationDate: Installed on 2013-06-15 (78 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MarkForUpload: True 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/1219583/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1072403] Re: [GeForce 8600M GT] Unity and GnomeShell hang or crash with nouveau kernel error messages fail ttm_validate, validate vram_list and validate: -12
The default install of Ubuntu 13.10 seems to have this problem for me on an old Dell Optiplex 740 with built-in GeForce 6150 LE. Dec 23 22:34:01 ath64 kernel: [ 5663.040020] nouveau E[Xorg[25847]] reloc wait_idle failed: -16 Dec 23 22:34:01 ath64 kernel: [ 5663.040028] nouveau E[Xorg[25847]] reloc apply: -16 Dec 23 22:34:02 ath64 whoopsie[945]: online Dec 23 22:34:46 ath64 kernel: [ 5708.120570] nouveau E[Xorg[25847]] fail ttm_validate Dec 23 22:34:46 ath64 kernel: [ 5708.120581] nouveau E[Xorg[25847]] validate vram_list Dec 23 22:34:46 ath64 kernel: [ 5708.120584] nouveau E[Xorg[25847]] validate: -16 Dec 23 22:35:32 ath64 kernel: [ 5753.249571] nouveau E[ PGRAPH][:00:05.0] ERROR nsource: ILLEGAL_MTHD nstatus: BAD_ARGUMENT PROTECTION_FAULT Dec 23 22:35:32 ath64 kernel: [ 5753.249581] nouveau E[ PGRAPH][:00:05.0] ch 1 [0x00048000 Xorg[25847]] subc 0 class 0x0039 mthd 0x0480 data 0x015f1000 Dec 23 22:35:32 ath64 kernel: [ 5753.249599] nouveau E[ PGRAPH][:00:05.0] ERROR nsource: ILLEGAL_MTHD nstatus: BAD_ARGUMENT PROTECTION_FAULT Dec 23 22:35:32 ath64 kernel: [ 5753.249605] nouveau E[ PGRAPH][:00:05.0] ch 1 [0x00048000 Xorg[25847]] subc 0 class 0x0039 mthd 0x0484 data 0x015f1000 ... Dec 23 22:36:09 ath64 kernel: [ 5791.241800] nouveau W[ PFIFO][:00:05.0] unknown intr 0x0001, ch 1 Dec 23 22:36:09 ath64 kernel: [ 5791.241806] nouveau W[ PFIFO][:00:05.0] unknown intr 0x0001, ch 1 Dec 23 22:36:09 ath64 kernel: [ 5791.241811] nouveau E[ PFIFO][:00:05.0] still angry after 101 spins, halt ... Dec 24 07:36:05 ath64 kernel: [ 1101.587875] nouveau E[Xorg[1039]] fail ttm_validate Dec 24 07:36:05 ath64 kernel: [ 1101.587883] nouveau E[Xorg[1039]] validate vram_list Dec 24 07:36:05 ath64 kernel: [ 1101.587885] nouveau E[Xorg[1039]] validate: -12 Dec 24 07:36:05 ath64 kernel: [ 1101.588144] nouveau E[Xorg[1039]] fail ttm_validate Dec 24 07:36:05 ath64 kernel: [ 1101.588146] nouveau E[Xorg[1039]] validate vram_list Dec 24 07:36:05 ath64 kernel: [ 1101.588148] nouveau E[Xorg[1039]] validate: -12 Dec 24 07:36:20 ath64 kernel: [ 1116.588016] nouveau E[Xorg[1039]] reloc wait_idle failed: -16 Dec 24 07:36:20 ath64 kernel: [ 1116.588023] nouveau E[Xorg[1039]] reloc apply: -16 Dec 24 07:36:20 ath64 kernel: [ 1116.592006] [sched_delayed] sched: RT throttling activated Dec 24 07:36:50 ath64 kernel: [ 1146.588016] nouveau E[Xorg[1039]] reloc wait_idle failed: -16 Dec 24 07:36:50 ath64 kernel: [ 1146.588023] nouveau E[Xorg[1039]] reloc apply: -16 Dec 24 07:39:11 ath64 gnome-session[1726]: Gdk-WARNING: gnome-session: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.#012 The system seemed unstable. Leaving it on overnight, the display was dead (although ctl-alt-f1 was able to take me to the console); after rebooting, it failed to configure and build wine (!). Installing the proprietary Nvidia seems to help; building wine now succeeds, and there are no warnings in syslog. So, at least on this old nvidia hardware, xserver-xorg-video-nouveau 1:1.0.9-2ubuntu1 does not seem production-ready for even light use. I'm ok with the proprietary driver, but it would be nice to run untainted someday. ** Attachment added: syslog.txt https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1072403/+attachment/3935177/+files/syslog.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/1072403 Title: [GeForce 8600M GT] Unity and GnomeShell hang or crash with nouveau kernel error messages fail ttm_validate, validate vram_list and validate: -12 Status in “xserver-xorg-video-nouveau” package in Ubuntu: Confirmed Bug description: Hi, since I reinstalled my Ubuntu (previous version was 11.04) my window managers have become very unstable. I believe it is nouveau's fault as I found these lines in /var/log/kern.log: Oct 28 18:00:50 jakob-Vostro-1500 kernel: [ 1454.599145] [drm] nouveau :01:00.0: fail ttm_validate Oct 28 18:00:50 jakob-Vostro-1500 kernel: [ 1454.599150] [drm] nouveau :01:00.0: validate vram_list Oct 28 18:00:50 jakob-Vostro-1500 kernel: [ 1454.599204] [drm] nouveau :01:00.0: validate: -12 The crashes appear to be nondeterministic: Most of the time, when I boot the system with external displays plugged into the VGA port, something crashes. In the worst cases the whole system crashes and only SysRq keys are working. At other times I'm still able to reach the terminal via ctrl-alt-f1. Even if the system survived, the window manager often later on hangs and displays false colors and sometimes recovers. The log files automatically attached by apport should document the latter error symptom. I'd be happy to supply more information if you can give me hints how to gather them. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package:
[Desktop-packages] [Bug 1219583] Re: SANE does not work anymore with Epson Perfection 1650. Used to work perfectly.
My fix was accepted upstream: commit 0f23fb3fc19880361d62d1ec894472a1cc5a3af4 Author: Dan Kegel d...@kegel.com Date: Sun Sep 1 15:14:45 2013 -0700 Epson Perfection 1650 doesn't support the FSG_STATUS_CANCEL_REQ bit. Fixes s -- 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/1219583 Title: SANE does not work anymore with Epson Perfection 1650. Used to work perfectly. Status in “sane-backends” package in Ubuntu: New Bug description: On my plain vanilla ubuntu 13.04 system, with an Epson Perfection 1650 scanner plugged in, clicking 'Scan' in xsane, or running scanimage, yielded a short scan run and the message '[epson2] e2_ext_read: cancel request received' on stderr. This turns out to be caused by the commit commit 63a8dd4ebc9535b23d7a922cb0e7a9a682edd955 Author: Alessandro Zummo a.zu...@towertech.it Date: Sat Jan 9 23:21:50 2010 +0100 epson2: improved error detection as guessed by a comment in the related Debian bug report http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=597922#127 which also had a spot-on suggestion for how to fix it. I've attached the draft patch to http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=597922#215 There is also an upstream bug report, https://alioth.debian.org/tracker/?group_id=30186atid=410366func=detailaid=312793 but I have not been able to comment there (alioth's login system defeated me). That upstream bug report also has a simple workaround (edit /etc/sane.d/dll.conf to uncomment epson and comment epson2), but a real fix would be nice. So, assuming no upstream release before 13.10, how about adding my patch? I'd be happy to submit it in a more ubuntu-friendly form. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: libsane 1.0.23-0ubuntu1 [modified: usr/lib/x86_64-linux-gnu/sane/libsane-epson2.so.1.0.23] ProcVersionSignature: Ubuntu 3.8.0-29.42-generic 3.8.13.5 Uname: Linux 3.8.0-29-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.9.2-0ubuntu8.3 Architecture: amd64 Date: Sun Sep 1 16:09:30 2013 InstallationDate: Installed on 2013-06-15 (78 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MarkForUpload: True 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/1219583/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1219583] Re: SANE does not work anymore with Epson Perfection 1650. Used to work perfectly.
Given that beta1 is in three days, I suppose this is a long shot, but: I'm attaching the commit and checking the 'patch' checkbox... ** Patch added: Cherrypicked fix from upstream https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1219583/+attachment/3799374/+files/0001-Epson-Perfection-1650-doesn-t-support-the-FSG_STATUS.patch -- 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/1219583 Title: SANE does not work anymore with Epson Perfection 1650. Used to work perfectly. Status in “sane-backends” package in Ubuntu: New Bug description: On my plain vanilla ubuntu 13.04 system, with an Epson Perfection 1650 scanner plugged in, clicking 'Scan' in xsane, or running scanimage, yielded a short scan run and the message '[epson2] e2_ext_read: cancel request received' on stderr. This turns out to be caused by the commit commit 63a8dd4ebc9535b23d7a922cb0e7a9a682edd955 Author: Alessandro Zummo a.zu...@towertech.it Date: Sat Jan 9 23:21:50 2010 +0100 epson2: improved error detection as guessed by a comment in the related Debian bug report http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=597922#127 which also had a spot-on suggestion for how to fix it. I've attached the draft patch to http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=597922#215 There is also an upstream bug report, https://alioth.debian.org/tracker/?group_id=30186atid=410366func=detailaid=312793 but I have not been able to comment there (alioth's login system defeated me). That upstream bug report also has a simple workaround (edit /etc/sane.d/dll.conf to uncomment epson and comment epson2), but a real fix would be nice. So, assuming no upstream release before 13.10, how about adding my patch? I'd be happy to submit it in a more ubuntu-friendly form. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: libsane 1.0.23-0ubuntu1 [modified: usr/lib/x86_64-linux-gnu/sane/libsane-epson2.so.1.0.23] ProcVersionSignature: Ubuntu 3.8.0-29.42-generic 3.8.13.5 Uname: Linux 3.8.0-29-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.9.2-0ubuntu8.3 Architecture: amd64 Date: Sun Sep 1 16:09:30 2013 InstallationDate: Installed on 2013-06-15 (78 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MarkForUpload: True 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/1219583/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1219583] [NEW] SANE does not work anymore with Epson Perfection 1650. Used to work perfectly.
Public bug reported: On my plain vanilla ubuntu 13.04 system, with an Epson Perfection 1650 scanner plugged in, clicking 'Scan' in xsane, or running scanimage, yielded a short scan run and the message '[epson2] e2_ext_read: cancel request received' on stderr. This turns out to be caused by the commit commit 63a8dd4ebc9535b23d7a922cb0e7a9a682edd955 Author: Alessandro Zummo a.zu...@towertech.it Date: Sat Jan 9 23:21:50 2010 +0100 epson2: improved error detection as guessed by a comment in the related Debian bug report http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=597922#127 which also had a spot-on suggestion for how to fix it. I've attached the draft patch to http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=597922#215 There is also an upstream bug report, https://alioth.debian.org/tracker/?group_id=30186atid=410366func=detailaid=312793 but I have not been able to comment there (alioth's login system defeated me). That upstream bug report also has a simple workaround (edit /etc/sane.d/dll.conf to uncomment epson and comment epson2), but a real fix would be nice. So, assuming no upstream release before 13.10, how about adding my patch? I'd be happy to submit it in a more ubuntu-friendly form. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: libsane 1.0.23-0ubuntu1 [modified: usr/lib/x86_64-linux-gnu/sane/libsane-epson2.so.1.0.23] ProcVersionSignature: Ubuntu 3.8.0-29.42-generic 3.8.13.5 Uname: Linux 3.8.0-29-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.9.2-0ubuntu8.3 Architecture: amd64 Date: Sun Sep 1 16:09:30 2013 InstallationDate: Installed on 2013-06-15 (78 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MarkForUpload: True SourcePackage: sane-backends UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: sane-backends (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug raring -- 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/1219583 Title: SANE does not work anymore with Epson Perfection 1650. Used to work perfectly. Status in “sane-backends” package in Ubuntu: New Bug description: On my plain vanilla ubuntu 13.04 system, with an Epson Perfection 1650 scanner plugged in, clicking 'Scan' in xsane, or running scanimage, yielded a short scan run and the message '[epson2] e2_ext_read: cancel request received' on stderr. This turns out to be caused by the commit commit 63a8dd4ebc9535b23d7a922cb0e7a9a682edd955 Author: Alessandro Zummo a.zu...@towertech.it Date: Sat Jan 9 23:21:50 2010 +0100 epson2: improved error detection as guessed by a comment in the related Debian bug report http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=597922#127 which also had a spot-on suggestion for how to fix it. I've attached the draft patch to http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=597922#215 There is also an upstream bug report, https://alioth.debian.org/tracker/?group_id=30186atid=410366func=detailaid=312793 but I have not been able to comment there (alioth's login system defeated me). That upstream bug report also has a simple workaround (edit /etc/sane.d/dll.conf to uncomment epson and comment epson2), but a real fix would be nice. So, assuming no upstream release before 13.10, how about adding my patch? I'd be happy to submit it in a more ubuntu-friendly form. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: libsane 1.0.23-0ubuntu1 [modified: usr/lib/x86_64-linux-gnu/sane/libsane-epson2.so.1.0.23] ProcVersionSignature: Ubuntu 3.8.0-29.42-generic 3.8.13.5 Uname: Linux 3.8.0-29-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.9.2-0ubuntu8.3 Architecture: amd64 Date: Sun Sep 1 16:09:30 2013 InstallationDate: Installed on 2013-06-15 (78 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MarkForUpload: True 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/1219583/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1216621] [NEW] evince can't display JavaKid811.pdf
Public bug reported: The file http://myflex.org/books/java4kids/JavaKid811.pdf displays fine in acroread, but in evince, paging down through it yields blank pages and lots of warnings on the console like Syntax Error (1159997): Illegal character ff in hex string Syntax Error (1159997): Illegal character d3 in hex string Syntax Error (116): Illegal character d4 in hex string ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: evince 3.6.1-1ubuntu3 ProcVersionSignature: Ubuntu 3.8.0-27.40-generic 3.8.13.4 Uname: Linux 3.8.0-27-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.9.2-0ubuntu8.3 Architecture: amd64 Date: Sun Aug 25 10:26:11 2013 InstallationDate: Installed on 2013-06-15 (71 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) KernLog: MarkForUpload: True SourcePackage: evince UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: evince (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug raring -- 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/1216621 Title: evince can't display JavaKid811.pdf Status in “evince” package in Ubuntu: New Bug description: The file http://myflex.org/books/java4kids/JavaKid811.pdf displays fine in acroread, but in evince, paging down through it yields blank pages and lots of warnings on the console like Syntax Error (1159997): Illegal character ff in hex string Syntax Error (1159997): Illegal character d3 in hex string Syntax Error (116): Illegal character d4 in hex string ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: evince 3.6.1-1ubuntu3 ProcVersionSignature: Ubuntu 3.8.0-27.40-generic 3.8.13.4 Uname: Linux 3.8.0-27-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.9.2-0ubuntu8.3 Architecture: amd64 Date: Sun Aug 25 10:26:11 2013 InstallationDate: Installed on 2013-06-15 (71 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) KernLog: MarkForUpload: True SourcePackage: evince UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1216621/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 577919] Re: chromium-browser fails to start (guest account, OpenVZ): Failed to move to new PID namespace: Operation not permitted
Uh-oh. I'm seeing this again with lightdm 1.6.0-0ubuntu3 on ubuntu 13.04 guest sessions with Google Chrome 28.0.1500.95. Perhaps the bug is back in a slightly new form? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm-guest-session in Ubuntu. https://bugs.launchpad.net/bugs/577919 Title: chromium-browser fails to start (guest account, OpenVZ): Failed to move to new PID namespace: Operation not permitted Status in Chromium Browser: Unknown Status in Light Display Manager: Fix Released Status in OpenVZ kernel (patchset): Confirmed Status in “gdm-guest-session” package in Ubuntu: Confirmed Status in “lightdm” package in Ubuntu: Fix Released Status in “lightdm-remote-session-freerdp” package in Ubuntu: Fix Released Status in “lightdm-remote-session-uccsconfigure” package in Ubuntu: Fix Released Status in “gdm-guest-session” source package in Precise: Won't Fix Status in “lightdm” source package in Precise: Fix Released Status in “lightdm-remote-session-freerdp” source package in Precise: Invalid Status in “lightdm-remote-session-uccsconfigure” source package in Precise: Invalid Bug description: Binary package hint: chromium-browser [Impact] Chromium-browser does not launch from guest session. Fix by Jamie Strandboge: It would be nice if AppArmor could merge profiles, but we can't yet, so we need to do like you initially did: have two mostly identical profiles. Because the lightdm remote sessions are shipping policy copies, the maintenance cost is getting high. I will be abstracting out the guest rules into abstracations/lightdm and then have a small snippet using a child profile in abstractions/lightdm_chromium-browser. The guest and remote lightdm profiles can just include these and all the policy is in the abstractions. Using a lightdm.d directory is a good idea, but upstream AppArmor is currently discussing how to best handle .d directories like this, and I'd rather not add another one until that discussions is finished. [Test Case] 1. install chromium-browser 2. login to the guest account 3. login to vt1 or login via ssh as a regular user and verify that the lightdm profile is loaded and guest session applications are confined: $ sudo aa-status apparmor module is loaded. ... /usr/lib/lightdm/lightdm/lightdm-guest-session-wrapper ... /usr/lib/lightdm/lightdm/lightdm-guest-session-wrapper (1378) /usr/lib/lightdm/lightdm/lightdm-guest-session-wrapper (1414) /usr/lib/lightdm/lightdm/lightdm-guest-session-wrapper (1417) /usr/lib/lightdm/lightdm/lightdm-guest-session-wrapper (1418) ... Note: number of profiles and pids will vary. 4. try to start chromium-browser either via the Dash or a terminal Prior to upgrading, chromium-browser will fail to start with: Failed to move to new PID namespace: Operation not permitted After upgrading, the guest session should be functional and chromium-browser should start. In addition, aa-status should report a child profile for chromium-browser and chromium-browser should be under that confinement with other guest session applications under the lightdm-guest-session-wrapper confinement: $ sudo aa-status apparmor module is loaded. ... /usr/lib/lightdm/lightdm/lightdm-guest-session-wrapper /usr/lib/lightdm/lightdm/lightdm-guest-session-wrapper//chromium_browser ... /usr/lib/lightdm/lightdm/lightdm-guest-session-wrapper (2667) /usr/lib/lightdm/lightdm/lightdm-guest-session-wrapper (2672) /usr/lib/lightdm/lightdm/lightdm-guest-session-wrapper (2682) ... /usr/lib/lightdm/lightdm/lightdm-guest-session-wrapper//chromium_browser (3090) /usr/lib/lightdm/lightdm/lightdm-guest-session-wrapper//chromium_browser (3092) /usr/lib/lightdm/lightdm/lightdm-guest-session-wrapper//chromium_browser (3093) ... [Regression Potential] As mentioned in the Impact, the apparmor profile for lightdm has necessarily been broken out into multiple parts. As such, there is potential that the guest session profile won't work correctly, however, this is easily seen in the test cases and these changes have been in place since 12.10. [Other Info] Attached is a debdiff for 12.04. It: - adds debian/patches/05_lp577919-fix-chromium-launch.patch which is the same as debian/patches/09_lp577919-fix-chromium-launch.patch from quantal, except it a) does not include the fix for bug #1059510, which is uneeded on precise and b) includes the fix for bug #1189948 to install the abstractions with the correct permissions - additionally, debian/lightdm.postinst is updated to reload the apparmor profile on upgrade to this version of lightdm. The code in question uses the same logic as dh_apparmor, and I'm not sure why lightdm doesn't use dh_apparmor. Rather than making several packaging changes to use dh_apparmor, I chose this
[Desktop-packages] [Bug 1033533] Re: Xorg crashed with SIGABRT: exaMemcpyBox with src=0x0 on nouveau with SW rendering
This is 100% reproducible here. All I have to do is run 'make check' in wine,
tell gdb to attach to X and ignore SIGPIPE,
and in a few minutes, gdb says e.g.
Program received signal SIGSEGV, Segmentation fault.
0x7f74ae864bd5 in ?? () from /lib/x86_64-linux-gnu/libc.so.6
(gdb) bt
#0 0x7f74ae864bd5 in ?? () from /lib/x86_64-linux-gnu/libc.so.6
#1 0x7f74ac53985e in memcpy (__len=2700, __src=0x0, __dest=0x7f74b2ba40d0)
at /usr/include/x86_64-linux-gnu/bits/string3.h:51
#2 exaMemcpyBox (pbox=pbox@entry=0x7fffd5a2fbc0, src=0x0, src_pitch=2752,
dst=0x7f74b2ba40d0 h\377\255\256t\177,
dst_pitch=2700, pPixmap=0x7f74b2b80e50) at
../../exa/exa_migration_classic.c:59
...
This is on a stock install of 13.04 daily from April 21 or so.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-nouveau in Ubuntu.
https://bugs.launchpad.net/bugs/1033533
Title:
Xorg crashed with SIGABRT: exaMemcpyBox with src=0x0 on nouveau with
SW rendering
Status in “xserver-xorg-video-nouveau” package in Ubuntu:
Confirmed
Status in “xserver-xorg-video-nouveau” source package in Quantal:
Confirmed
Status in “xserver-xorg-video-nouveau” source package in Raring:
Confirmed
Bug description:
Crash doing memcpy in EXA on nouveau, with software rendering
activated.
#8 signal handler called
No symbol table info available.
#9 __memcpy_sse2 () at ../sysdeps/x86_64/multiarch/../memcpy.S:72
No locals.
#10 0x7f570e63684e in memcpy (__len=23, __src=0x0, __dest=0x7f5713877100)
at /usr/include/x86_64-linux-gnu/bits/string3.h:52
No locals.
#11 exaMemcpyBox (pbox=pbox@entry=0x7fffef000de0, src=0x0, src_pitch=64,
dst=0x7f5713877100 , dst_pitch=24, pPixmap=error reading variable: Unhandled
dwarf expression opcode 0xfa) at ../../exa/exa_migration_classic.c:59
i = 16
cpp = optimized out
bytes = 23
#12 0x7f570e636d03 in exaCopyDirty (migrate=migrate@entry=0x7fffef000e40,
pValidDst=0x7f5713dc3e40, pValidSrc=0x7f5713dc3e50, transfer=0x7f570f28b7f0
nouveau_exa_download_from_screen, fallback_index=fallback_index@entry=1,
sync=0x7f570e635780 exaWaitSync) at ../../exa/exa_migration_classic.c:240
pPixmap = 0x7f5713dc3da0
pExaPixmap = 0x7f5713dc3e00
damage = optimized out
CopyReg = {extents = {x1 = 0, y1 = 0, x2 = 23, y2 = 16}, data = 0x0}
save_use_gpu_copy = 1
save_pitch = 64
pBox = 0x7fffef000de0
nbox = 1
access_prepared = 1
need_sync = 0
#13 0x7f570e636f32 in exaCopyDirtyToSys
(migrate=migrate@entry=0x7fffef000e40) at ../../exa/exa_migration_classic.c:285
pPixmap = optimized out
pExaScr = 0x7f5713877100
pExaPixmap = 0x0
#14 0x7f570e63951a in exaPrepareAccessReg_mixed (pPixmap=0x7f5713dc3da0,
index=optimized out, pReg=0x0) at ../../exa/exa_migration_mixed.c:254
as_dst = 1
pixmaps = {{as_dst = 0, as_src = 1, pPix = 0x7f5713dc3da0, pReg =
0x0}}
pExaPixmap = 0x7f5713dc3e00
has_gpu_copy = optimized out
success = optimized out
[Original Report]
The crash report started immediately after login.
ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: xserver-xorg-core 2:1.12.99.902-0ubuntu1
ProcVersionSignature: Ubuntu 3.5.0-8.8-generic 3.5.0
Uname: Linux 3.5.0-8-generic x86_64
.tmp.unity.support.test.0:
ApportVersion: 2.4-0ubuntu6
Architecture: amd64
CompizPlugins: No value set for
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CrashCounter: 1
Date: Sun Aug 5 14:46:44 2012
DistUpgraded: Fresh install
DistroCodename: quantal
DistroVariant: ubuntu
DkmsStatus:
virtualbox, 4.1.18, 3.5.0-6-generic, x86_64: installed
virtualbox, 4.1.18, 3.5.0-8-generic, x86_64: installed
ExecutablePath: /usr/bin/Xorg
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
NVIDIA Corporation C61 [GeForce 6100 nForce 400] [10de:03d2] (rev a2)
(prog-if 00 [VGA controller])
Subsystem: NVIDIA Corporation Device [10de:cb84]
InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Alpha amd64 (20120519)
Lsusb:
Bus 001 Device 002: ID 18ec:3399 Arkmicro Technologies Inc.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
ProcCmdline: /usr/bin/X :0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7
-novtswitch -background none
ProcEnviron:
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-8-generic
root=UUID=a80eff25-65c3-4db0-adad-31d8ea95823b ro quiet splash vt.handoff=7
Renderer: Software
Signal: 6
SourcePackage: xorg-server
StacktraceTop:
?? () from /lib/x86_64-linux-gnu/libc.so.6
?? () from /usr/lib/xorg/modules/libexa.so
?? () from /usr/lib/xorg/modules/libexa.so
?? () from /usr/lib/xorg/modules/libexa.so
?? () from
[Desktop-packages] [Bug 160311] Re: Resizing windows by grabbing window borders is difficult
I suspect it's because they want to emulate how the Mac UI works, and the Mac only lets you grab the lower right corner. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to light-themes in Ubuntu. https://bugs.launchpad.net/bugs/160311 Title: Resizing windows by grabbing window borders is difficult Status in Ayatana Design: Fix Released Status in One Hundred Paper Cuts: Fix Released Status in The Metacity Window Manager: In Progress Status in Release Notes for Ubuntu: Fix Released Status in Unity 2D: Confirmed Status in “human-gtk-theme” package in Ubuntu: Invalid Status in “light-themes” package in Ubuntu: Fix Released Status in “metacity” package in Ubuntu: Confirmed Status in “human-gtk-theme” source package in Maverick: Invalid Status in “light-themes” source package in Maverick: Triaged Status in “metacity” source package in Maverick: Triaged Bug description: * This should mostly be fixed for Natty and might get backported to earlier releases as well. For Precise (12.04) this is again broken for unity-2d (as of 17.7.2012 unity-2d 5.12.0-0ubuntu1.1). Note that if the window has a scrollbar, you can grab that to resize the window. If not, you are stuck with the 1px border. Workaround: NONE KNOWN (see comment 320)? * *Blueprint for Natty, Ubuntu 11.04: https://blueprints.edge.launchpad.net/ubuntu/+spec/packageselection- dx-n-resizing-windows Work items1 * Make sure the new resize grip fits in current applications; doesn't interfere with anything. We should make some noise about this during the Natty cycle so people keep their eyes open and file bugs. 2 * Invisible window resize area - around 3px invisible area to allow resize on all sides. * Working grip backported to gtk2 already available in ppa : https://launchpad.net/~bratsche/+archive/gtk * Workaround: Edit /usr/share/themes/Ambiance/metacity-1/metacity- theme-1.xml. Set the following values in frame_geometry_normal as desired: distance name=left_width value=3/ distance name=right_width value=3/ distance name=bottom_height value=3/ Binary package hint: metacity - The issue has been an issue for users (especially of large) screens for several releases- Trackpad users seem to be particularly impacted by this- The issue appears to have been significantly aggravated in Lucid by changing the border width from 3 pixels to 1 pixel The window borders in metacity are far too thin to be used for comfortable window resizing, and resize handles are not available in all applications (or even most). In fact, of all the windows I have open right now, not a single one of them has a resize handle. The result is that I get a lot of misses when I try to drag a window border, which usually results in my clicking on the wrong window altogether. The best fix for this usability bug is to create an invisible region around each non-maximized window about 4px thick that can be used for resizing (in addition to the visible border). Or perhaps there should be a border thickness option on the System Preferences Windows dialog (although the default thickness should still be increased considerably). Ideally all windows would also have a resize handle but I realize that these have to be application controlled (at least that seems to be the position of the metacity team). To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/160311/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 371897]
This is not a user forum. User comments in here aren't especially helpful. -- 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/371897 Title: Occasional sound drops in Wine via PulseAudio Status in Wine: Confirmed Status in “pulseaudio” package in Ubuntu: Confirmed Status in “wine” package in Ubuntu: Triaged Bug description: Binary package hint: wine I'm running the Spotify Windows application on two laptops under Wine with both internal and external USB sound card. With both cards you get the occasional pop and click in the sound suggesting some data loss somewhere. I've selected the alsa drivers in winecfg and the whole thing is running via the alsa compatibility layer in pulseaudio. Jaunty 9.04 UNR and standard Ubuntu desktop. wine: Installed: 1.0.1-0ubuntu6 Candidate: 1.0.1-0ubuntu6 Version table: *** 1.0.1-0ubuntu6 0 500 http://gb.archive.ubuntu.com jaunty/universe Packages 100 /var/lib/dpkg/status pulseaudio: Installed: 1:0.9.14-0ubuntu20 Candidate: 1:0.9.14-0ubuntu20 Version table: *** 1:0.9.14-0ubuntu20 0 500 http://gb.archive.ubuntu.com jaunty/main Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/wine/+bug/371897/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 975176] Re: gvfsd-obexftp crashed with SIGSEGV in send_reply()
I see something superficially similar when I run 'xscanimage' and acquire a preview. Haven't seen the full stack yet. -- 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/975176 Title: gvfsd-obexftp crashed with SIGSEGV in send_reply() Status in “gvfs” package in Ubuntu: Confirmed Status in “gvfs” package in Fedora: Unknown Bug description: This bug occurs in combination with bug 975170. ProblemType: Crash DistroRelease: Ubuntu 12.04 Package: gvfs-backends 1.12.0-0ubuntu3 ProcVersionSignature: Ubuntu 3.2.0-22.35-generic-pae 3.2.14 Uname: Linux 3.2.0-22-generic-pae i686 NonfreeKernelModules: wl ApportVersion: 2.0-0ubuntu4 Architecture: i386 CrashCounter: 1 Date: Fri Apr 6 15:57:39 2012 ExecutablePath: /usr/lib/gvfs/gvfsd-obexftp InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Beta i386 (20120328) ProcCmdline: /usr/lib/gvfs/gvfsd-obexftp --spawner :1.6 /org/gtk/gvfs/exec_spaw/6 ProcEnviron: SHELL=/bin/bash PATH=(custom, user) LANG=de_DE.UTF-8 SegvReason: reading NULL VMA Signal: 11 SourcePackage: gvfs Title: gvfsd-obexftp crashed with SIGSEGV in g_cclosure_marshal_VOID__VOIDv() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vdr To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/975176/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 862614] Re: Using wireless network during install causes hilarity and confusion later
Still present in 12.04 beta 1. Still going to mightily confuse anyone installing ubuntu without an ethernet connection. Additional symptom: there was a route via the wlan using the autoconfig ip address as a gateway, which caused problems even if I plugged a real ethernet cable in. The installer folks might want to take a look at this, too, since the wireless interface they set up at boot time doesn't work after installation is finished. -- 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/862614 Title: Using wireless network during install causes hilarity and confusion later Status in “network-manager” package in Ubuntu: New Bug description: The installer (I used the alternate installer) wanted a network connection for use during the install. My cheap ethernet cable had failed, so lazily I used wireless. Install went fine, but: - on every bootup, the system waited for two minutes for a network connection, even though I had by then plugged in a reliable ethernet connection - in network manager, the wireless showed up as unmanaged and could not be configured I see somebody else reported the same thing (see bug 280417 comment #16 by Skaggs) some time ago, so this is not a regression. Commenting out the wireless adaptor in /etc/network/interfaces and rebooting solved the problem. So, there are two or three problems here: 1) the installer should warn you that the network adaptor you choose during the install is placed into /etc/network/interfaces and may need to be removed from there for proper system operation 2) the system doesn't actually manage to reestablish a network connection on that wireless adaptor when it's started that way, though it does fine later once you remove it from that file and manage it with network manager 3) network manager might want to provide some mouseover help explaining how to switch a device from unmanaged to managed. I'm filing it under network manager since that's where I first ran into it, and that's where I first saw the workaround documented. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/862614/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 931851] [NEW] package desktop-file-utils 0.19-0ubuntu2 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 1
Public bug reported: This was alpha 1 just after updating to alpha 2 via update manager. ProblemType: Package DistroRelease: Ubuntu 12.04 Package: desktop-file-utils 0.19-0ubuntu2 ProcVersionSignature: Ubuntu 3.2.0-10.18-generic 3.2.1 Uname: Linux 3.2.0-10-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 1.91-0ubuntu1 Architecture: amd64 Date: Mon Feb 13 17:02:37 2012 ErrorMessage: ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Alpha amd64 (2030.1) SourcePackage: desktop-file-utils Title: package desktop-file-utils 0.19-0ubuntu2 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to precise on 2012-02-14 (0 days ago) ** Affects: desktop-file-utils (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package precise -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to desktop-file-utils in Ubuntu. https://bugs.launchpad.net/bugs/931851 Title: package desktop-file-utils 0.19-0ubuntu2 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 1 Status in “desktop-file-utils” package in Ubuntu: New Bug description: This was alpha 1 just after updating to alpha 2 via update manager. ProblemType: Package DistroRelease: Ubuntu 12.04 Package: desktop-file-utils 0.19-0ubuntu2 ProcVersionSignature: Ubuntu 3.2.0-10.18-generic 3.2.1 Uname: Linux 3.2.0-10-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 1.91-0ubuntu1 Architecture: amd64 Date: Mon Feb 13 17:02:37 2012 ErrorMessage: ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Alpha amd64 (2030.1) SourcePackage: desktop-file-utils Title: package desktop-file-utils 0.19-0ubuntu2 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to precise on 2012-02-14 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/desktop-file-utils/+bug/931851/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 931851] Re: package desktop-file-utils 0.19-0ubuntu2 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 1
-- You received this bug notification because you are a member of Desktop Packages, which is subscribed to desktop-file-utils in Ubuntu. https://bugs.launchpad.net/bugs/931851 Title: package desktop-file-utils 0.19-0ubuntu2 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 1 Status in “desktop-file-utils” package in Ubuntu: New Bug description: This was alpha 1 just after updating to alpha 2 via update manager. ProblemType: Package DistroRelease: Ubuntu 12.04 Package: desktop-file-utils 0.19-0ubuntu2 ProcVersionSignature: Ubuntu 3.2.0-10.18-generic 3.2.1 Uname: Linux 3.2.0-10-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 1.91-0ubuntu1 Architecture: amd64 Date: Mon Feb 13 17:02:37 2012 ErrorMessage: ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Alpha amd64 (2030.1) SourcePackage: desktop-file-utils Title: package desktop-file-utils 0.19-0ubuntu2 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to precise on 2012-02-14 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/desktop-file-utils/+bug/931851/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 907052] Re: gnome-settings-daemon crashed with signal 5 in _XReply()
This has happened to me about once a day for the last five days, usually immediately upon login. I'm only testing 64 bit precise, haven't checked to see if it happens in 32 bits as well. -- 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/907052 Title: gnome-settings-daemon crashed with signal 5 in _XReply() Status in “gnome-settings-daemon” package in Ubuntu: Confirmed Bug description: gnome-settings-daemon crashed with signal 5 in _XReply() ProblemType: Crash DistroRelease: Ubuntu 12.04 Package: gnome-settings-daemon 3.2.2-0ubuntu5 ProcVersionSignature: Ubuntu 3.2.0-6.12-generic 3.2.0-rc6 Uname: Linux 3.2.0-6-generic x86_64 ApportVersion: 1.90-0ubuntu1 Architecture: amd64 CrashCounter: 1 Date: Tue Dec 20 21:05:13 2011 ExecutablePath: /usr/lib/gnome-settings-daemon/gnome-settings-daemon InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Alpha amd64+mac (20111206) ProcCmdline: /usr/lib/gnome-settings-daemon/gnome-settings-daemon ProcEnviron: PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash Signal: 5 SourcePackage: gnome-settings-daemon StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6 _XReply () from /usr/lib/x86_64-linux-gnu/libX11.so.6 XRRSetCrtcConfig () from /usr/lib/x86_64-linux-gnu/libXrandr.so.2 gnome_rr_crtc_set_config_with_time () from /usr/lib/libgnome-desktop-3.so.2 ?? () from /usr/lib/libgnome-desktop-3.so.2 Title: gnome-settings-daemon crashed with signal 5 in _XReply() UpgradeStatus: Upgraded to precise on 2011-12-12 (7 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-settings-daemon/+bug/907052/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 885492] Re: p11-kit: couldn't load module: /usr/lib/i386-linux-gnu/pkcs11/gnome-keyring-pkcs11.so
I'm hitting this trying to run wine on precise pangolin alpha 1 on x86_64 with ia32-libs. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/885492 Title: p11-kit: couldn't load module: /usr/lib/i386-linux-gnu/pkcs11/gnome- keyring-pkcs11.so Status in “gnome-keyring” package in Ubuntu: Confirmed Bug description: whenever I try to do a `git push`, I get this error: `p11-kit: couldn't load module: /usr/lib/i386-linux-gnu/pkcs11/gnome-keyring-pkcs11.so: /usr/lib/i386-linux-gnu/pkcs11/gnome-keyring-pkcs11.so: cannot open shared object file: No such file or directory` Distributor ID: Ubuntu Description: Ubuntu precise (development branch) Release: 12.04 Codename: precise To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/885492/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 917399] Re: Ubuntu 12.04 alpha 1 network flaky after update
Also affects ubuntu 11.10. Here's what was happening: my wifi interface was showing up as up but unmanaged (this is a very fresh installation, so that's how the installer left it), and 'route' showed Kernel IP routing table Destination Gateway Genmask Flags Metric RefUse Iface default 192.168.0.1 0.0.0.0 UG0 00 eth0 default 192.168.0.1 0.0.0.0 UG10000 wlan0 link-local * 255.255.0.0 U 1000 00 eth0 192.168.0.0 * 255.255.255.0 U 0 00 wlan0 192.168.0.0 * 255.255.255.0 U 1 00 eth0 The command 'ifconfig wlan0 down' fixed the problem! After that, the routing table was Destination Gateway Genmask Flags Metric RefUse Iface 0.0.0.0 192.168.0.1 0.0.0.0 UG0 00 eth0 169.254.0.0 0.0.0.0 255.255.0.0 U 1000 00 eth0 192.168.0.0 0.0.0.0 255.255.255.0 U 1 00 eth0 and everything was hunky-dory. So the problem was that the installer left my system in an inconsistent state: wlan0 was up but not managed, and acted as a packet /dev/null 35 seconds out of every 43 seconds. ** Package changed: ubuntu = network-manager (Ubuntu) -- 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/917399 Title: Ubuntu 12.04 alpha 1 network flaky after update Status in “network-manager” package in Ubuntu: New Bug description: Testing 12.04 alpha 1 64 bit on my Asus G60JX laptop. Worked well enough with previous versions ( http://kegel.com/linux/asus-g60jx-laptop.html ). As with previous versions of Ubuntu, the Live CD / normal desktop installer couldn't get graphics right, so used alternate install iso, and had to specify nomodeset on kernel commandline after installation to get any graphics. Was able to do a complete software update, then rebooted. After that, networking seemed flakier. When I try downloading the nvidia display driver with Additional Drivers, the download seems to hang after a few seconds. Rebooting and retrying doesn't help. There were several crashes, and apport collected data for them and even uploaded one of them, but I was unable to finish the login process at launchpad. I had to reboot to 11.04 to file this report. This is all with wired networking, as wireless doesn't work at all. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/917399/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 917399] Re: Ubuntu 12.04 alpha 1 network flaky after update
Title of bug should be something like installer and/or network manager mistakenly adds route via broken wlan0, causing intermittent complete packet loss -- 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/917399 Title: Ubuntu 12.04 alpha 1 network flaky after update Status in “network-manager” package in Ubuntu: New Bug description: Testing 12.04 alpha 1 64 bit on my Asus G60JX laptop. Worked well enough with previous versions ( http://kegel.com/linux/asus-g60jx-laptop.html ). As with previous versions of Ubuntu, the Live CD / normal desktop installer couldn't get graphics right, so used alternate install iso, and had to specify nomodeset on kernel commandline after installation to get any graphics. Was able to do a complete software update, then rebooted. After that, networking seemed flakier. When I try downloading the nvidia display driver with Additional Drivers, the download seems to hang after a few seconds. Rebooting and retrying doesn't help. There were several crashes, and apport collected data for them and even uploaded one of them, but I was unable to finish the login process at launchpad. I had to reboot to 11.04 to file this report. This is all with wired networking, as wireless doesn't work at all. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/917399/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 917399] Re: Ubuntu 12.04 alpha 1 network flaky after update
See also bug 917402, which describes another symptom of the underlying disagreement. -- 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/917399 Title: Ubuntu 12.04 alpha 1 network flaky after update Status in “network-manager” package in Ubuntu: New Bug description: Testing 12.04 alpha 1 64 bit on my Asus G60JX laptop. Worked well enough with previous versions ( http://kegel.com/linux/asus-g60jx-laptop.html ). As with previous versions of Ubuntu, the Live CD / normal desktop installer couldn't get graphics right, so used alternate install iso, and had to specify nomodeset on kernel commandline after installation to get any graphics. Was able to do a complete software update, then rebooted. After that, networking seemed flakier. When I try downloading the nvidia display driver with Additional Drivers, the download seems to hang after a few seconds. Rebooting and retrying doesn't help. There were several crashes, and apport collected data for them and even uploaded one of them, but I was unable to finish the login process at launchpad. I had to reboot to 11.04 to file this report. This is all with wired networking, as wireless doesn't work at all. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/917399/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 701015] Re: problem with ssl rapidssl https://www.digitalav.com.br
I can reproduce this with ubuntu 11.10's firefox; it doesn't like the site https://www.gamersgate.com/account/register Chrome has no problem with it; I guess Chrome has its own list of ca's. See also http://bugs.winehq.org/show_bug.cgi?id=29170 ** Bug watch added: Wine Bugzilla #29170 http://bugs.winehq.org/show_bug.cgi?id=29170 -- 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/701015 Title: problem with ssl rapidssl https://www.digitalav.com.br Status in “firefox” package in Ubuntu: Confirmed Bug description: Binary package hint: firefox work fine in others browsers (ie, chrome, opera) error: sec_error_unknown_issuer ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: firefox 3.6.13+build3+nobinonly-0ubuntu0.10.10.1 ProcVersionSignature: Ubuntu 2.6.35-24.42-generic 2.6.35.8 Uname: Linux 2.6.35-24-generic x86_64 NonfreeKernelModules: nvidia Architecture: amd64 Date: Mon Jan 10 11:20:28 2011 FirefoxPackages: firefox 3.6.13+build3+nobinonly-0ubuntu0.10.10.1 firefox-gnome-support 3.6.13+build3+nobinonly-0ubuntu0.10.10.1 firefox-branding 3.6.13+build3+nobinonly-0ubuntu0.10.10.1 abroswer N/A abrowser-branding N/A InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release amd64 (20101007) ProcEnviron: LANGUAGE=pt_BR:pt:en LANG=pt_BR.utf8 SHELL=/bin/bash SourcePackage: firefox To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/701015/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 862614] [NEW] Using wireless network during install causes hilarity and confusion later
Public bug reported: The installer (I used the alternate installer) wanted a network connection for use during the install. My cheap ethernet cable had failed, so lazily I used wireless. Install went fine, but: - on every bootup, the system waited for two minutes for a network connection, even though I had by then plugged in a reliable ethernet connection - in network manager, the wireless showed up as unmanaged and could not be configured I see somebody else reported the same thing (see bug 280417 comment #16 by Skaggs) some time ago, so this is not a regression. Commenting out the wireless adaptor in /etc/network/interfaces and rebooting solved the problem. So, there are two or three problems here: 1) the installer should warn you that the network adaptor you choose during the install is placed into /etc/network/interfaces and may need to be removed from there for proper system operation 2) the system doesn't actually manage to reestablish a network connection on that wireless adaptor when it's started that way, though it does fine later once you remove it from that file and manage it with network manager 3) network manager might want to provide some mouseover help explaining how to switch a device from unmanaged to managed. I'm filing it under network manager since that's where I first ran into it, and that's where I first saw the workaround documented. ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New -- 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/862614 Title: Using wireless network during install causes hilarity and confusion later Status in “network-manager” package in Ubuntu: New Bug description: The installer (I used the alternate installer) wanted a network connection for use during the install. My cheap ethernet cable had failed, so lazily I used wireless. Install went fine, but: - on every bootup, the system waited for two minutes for a network connection, even though I had by then plugged in a reliable ethernet connection - in network manager, the wireless showed up as unmanaged and could not be configured I see somebody else reported the same thing (see bug 280417 comment #16 by Skaggs) some time ago, so this is not a regression. Commenting out the wireless adaptor in /etc/network/interfaces and rebooting solved the problem. So, there are two or three problems here: 1) the installer should warn you that the network adaptor you choose during the install is placed into /etc/network/interfaces and may need to be removed from there for proper system operation 2) the system doesn't actually manage to reestablish a network connection on that wireless adaptor when it's started that way, though it does fine later once you remove it from that file and manage it with network manager 3) network manager might want to provide some mouseover help explaining how to switch a device from unmanaged to managed. I'm filing it under network manager since that's where I first ran into it, and that's where I first saw the workaround documented. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/862614/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
