[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 Ubuntu Desktop Bugs, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1921651 Title: colon in name causes gvfs hang when copying to phone To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1921651/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 Ubuntu Desktop Bugs, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1921651 Title: colon in name causes gvfs hang when copying to phone To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1921651/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1766938 Title: gnome-shell crashed in standard_pict_format_for_depth() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1766938/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 Ubuntu Desktop Bugs, 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1849873/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 Ubuntu Desktop Bugs, 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1849873/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 Ubuntu Desktop Bugs, 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1828748/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1776260 Title: Can't use three monitors properly; "xrandr: screen cannot be larger than 8192x8192" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1776260/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1776260 Title: Can't use three monitors properly; "xrandr: screen cannot be larger than 8192x8192" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1776260/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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, &root_return, 322 &x_ret, &y_ret, &w_ret, &h_ret, &bw_ret, &depth_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 Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1766938 Title: gnome-shell crashed in standard_pict_format_for_depth() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1766938/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1766938 Title: gnome-shell crashed in standard_pict_format_for_depth() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1766938/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1766938 Title: gnome-shell crashed in standard_pict_format_for_depth() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1766938/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1766938 Title: gnome-shell crashes after a few seconds To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1766938/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1766938 Title: gnome-shell crashes after a few seconds To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1766938/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1766938 Title: gnome-shell crashes after a few seconds To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1766938/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1766938 Title: gnome-shell crashes after a few seconds To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1766938/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 Ubuntu Desktop Bugs, 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"?! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1662418/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 Ubuntu Desktop Bugs, 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"?! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1662418/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 Ubuntu Desktop Bugs, 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1436640/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 Ubuntu Desktop Bugs, 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1436640/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 in hex string Syntax Error (1159997): Illegal character in hex string Syntax Error (116): Illegal character 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 Ubuntu Desktop Bugs, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1216621 Title: evince can't display JavaKid811.pdf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1216621/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 Ubuntu Desktop Bugs, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/160311 Title: Resizing windows by grabbing window borders is difficult To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/160311/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 Ubuntu Desktop Bugs, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/975176 Title: gvfsd-obexftp crashed with SIGSEGV in send_reply() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/975176/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 Ubuntu Desktop Bugs, 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/desktop-file-utils/+bug/931851/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 Ubuntu Desktop Bugs, 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/desktop-file-utils/+bug/931851/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 Ubuntu Desktop Bugs, 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/885492/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 Ubuntu Desktop Bugs, 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() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/907052/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 736606] Re: "Do Nothing" option not available by default in the power management preferences dialog
Bug 595071 is another possible dup. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in Ubuntu. https://bugs.launchpad.net/bugs/736606 Title: "Do Nothing" option not available by default in the power management preferences dialog To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/736606/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 595071] Re: gnome-display-properties closed switched, off notebook display shouldn't affect external screen
Is this a dup of bug 736606 ? -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/595071 Title: gnome-display-properties closed switched, off notebook display shouldn't affect external screen -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 736606] Re: "Do Nothing" option not available by default in the power management preferences dialog
Bug 745275 is a dup of this one (ok, it came first, but this one is more nicely written up). This is one of the problems described in "Day 7: Lessons from the Unity Trenches (30 Days With Ubuntu)", http://www.pcworld.com/businesscenter/article/229734 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in Ubuntu. https://bugs.launchpad.net/bugs/736606 Title: "Do Nothing" option not available by default in the power management preferences dialog -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 745275] Re: Closing lid field does not offer option "nothing"
Let's make this a dup of bug 736606, that is identical but has two votes and a slightly better writeup. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in Ubuntu. https://bugs.launchpad.net/bugs/745275 Title: Closing lid field does not offer option "nothing" -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 190227] Re: ia32 apps look for libs on the wrong place
Still present in Jaunty Alpha 2 when starting Google Chrome: Gtk-Message: Failed to load module "canberra-gtk-module": /usr/lib/gtk-2.0/modules/libcanberra-gtk-module.so: wrong ELF class: ELFCLASS64 Possible culprit: $ strings /usr/lib32/libgdk_pixbuf-2.0.so | grep /usr/lib /usr/lib/gtk-2.0/2.10.0/loader-files.d -- ia32 apps look for libs on the wrong place https://bugs.launchpad.net/bugs/190227 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gtk+2.0 in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 190227] Re: ia32 apps look for libs on the wrong place
The Chromium project is gathering a list of the 32-bit-on-64-bit problems they're facing at http://code.google.com/p/chromium/wiki/Linux64BitIssues It would be good if we could resolve all of them for Koala. It's sad that resolving these is considered low importance. The 32 bit subsystem should work, dammit. -- ia32 apps look for libs on the wrong place https://bugs.launchpad.net/bugs/190227 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gtk+2.0 in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 190227] Re: ia32 apps look for libs on the wrong place
I'm getting this with apps on Jaunty Beta. In particular, I get the errors Gtk-Message: Failed to load module "canberra-gtk-module": /usr/lib/gtk-2.0/modules/libcanberra-gtk-module.so: wrong ELF class: ELFCLASS64 /usr/lib/gio/modules/libgvfsdbus.so: wrong ELF class: ELFCLASS64 Failed to load module: /usr/lib/gio/modules/libgvfsdbus.so /usr/lib/gio/modules/libgiogconf.so: wrong ELF class: ELFCLASS64 Failed to load module: /usr/lib/gio/modules/libgiogconf.so /usr/lib/gio/modules/libgioremote-volume-monitor.so: wrong ELF class: ELFCLASS64 Failed to load module: /usr/lib/gio/modules/libgioremote-volume-monitor.so when I try to run a particular 32 bit test app (test_shell from chromium.org) built on jaunty. -- ia32 apps look for libs on the wrong place https://bugs.launchpad.net/bugs/190227 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gtk+2.0 in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 332253] Re: Epiphany doesn't mention Ubuntu in user agent string
** Description changed: Binary package hint: epiphany-browser The Wine project is trying to streamline their download page by detecting the distribution of visitors. However, Epiphany doesn't - mention Ubuntu in the user agent string, so it's impossible to detect. + mention Ubuntu in the user agent string, so Epiphany users will get the + non-streamlined download page. - http://www.winehq.org/pipermail/wine-devel/2009-February/073411.html + Epiphany is using the useragent string + Mozilla/5.0 (X11; U; Linux x86_64; en; rv:1.9.0.6) Gecko/20080528 Epiphany/2.22 Firefox/3.0 + but firefox puts the distro in between the Gecko and the browser name + Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.0.6) Gecko/2009020911 Ubuntu/8.10 (intrepid) Firefox/3.0.6" + + It would be nice if Epiphany did the same. + + See also http://www.winehq.org/pipermail/wine- + devel/2009-February/073411.html Ubuntu 8.10 x86-64 Epiphany 2.24.1 -- Epiphany doesn't mention Ubuntu in user agent string https://bugs.launchpad.net/bugs/332253 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to epiphany-browser in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 190227] Re: ia32 apps look for libs on the wrong place
Here's a workaround script for at least Ubuntu 8.04.1. What other libraries should be added to this list? #!/bin/sh # Script to work around https://bugs.launchpad.net/ubuntu/+source/ia32-libs/+bug/190227 # "Picasa can't capture images on 64 bit ubuntu" if grep -q /usr/lib /usr/lib32/libgphoto2.so.2.3.0 && ! grep -q /usr/lib32 /usr/lib32/libgphoto2.so.2.3.0 then echo Your system has the bug. Applying workaround. sudo ln -s /usr/lib32 /usr/l32 sudo sed -i.bak 's/\/usr\/lib\//\/usr\/l32\//g' /usr/lib32/libgphoto2.so.2.3.0 /usr/lib32/libgphoto2_port.so.0.8.0 else echo Your system does not have the bug. fi -- ia32 apps look for libs on the wrong place https://bugs.launchpad.net/bugs/190227 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gtk+2.0 in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 190227] Re: ia32 apps look for libs on the wrong place
Is this still a problem in Intrepid? -- ia32 apps look for libs on the wrong place https://bugs.launchpad.net/bugs/190227 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gtk+2.0 in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 41747] Re: if network cable not plugged in on boot, no address ever acquired
This works in Hardy. ** Changed in: gnome-netstatus (Ubuntu) Status: Triaged => Fix Released -- if network cable not plugged in on boot, no address ever acquired https://bugs.launchpad.net/bugs/41747 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a direct subscriber. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs