[Desktop-packages] [Bug 2037151] Re: Chromium glitches, Brave too, might be GPU
** Package changed: gnome-panel (Ubuntu) => chromium-browser (Ubuntu) -- 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/2037151 Title: Chromium glitches, Brave too, might be GPU Status in chromium-browser package in Ubuntu: New Bug description: Hi there! I have a theory what this problem is, and i am going to post it in detail here https://bugs.launchpad.net/ubuntu/+source/chromium- browser/+bug/2037093 This was not supposed to be a "new" bug report, I wanted to use Apport and somehow attach my Apport output to an *existing* bug thread in bugs.launchpad.net Is there a way to do that? short version: i think its very similar to this: https://bugs.launchpad.net/ubuntu/+source/chromium- browser/+bug/2035360 also, Brave has already fixed the issue, i got a snap update from them about 8 hours ago and YES it fixed it. know anyone on their tech team who can tell you how they fixed it? ;-);-) cheers Peter Fisera https://earthangelconsulting.com ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-panel 1:3.44.0-1ubuntu1 ProcVersionSignature: Ubuntu 6.2.0-33.33~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-33-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: GNOME-Flashback:GNOME Date: Fri Sep 22 20:25:51 2023 ExecutablePath: /usr/bin/gnome-panel GsettingsChanges: b'org.gnome.gnome-panel.layout' b'object-id-list' b"['menu-bar', 'indicators', 'show-desktop', 'window-list', 'workspace-switcher', 'launcher', 'launcher-0', 'launcher-1', 'launcher-2', 'launcher-3', 'launcher-4', 'launcher-5', 'launcher-6', 'launcher-7', 'launcher-8', 'launcher-9', 'launcher-10', 'launcher-11', 'launcher-12', 'launcher-13', 'launcher-14', 'launcher-15', 'launcher-16', 'launcher-17', 'launcher-18', 'launcher-19', 'launcher-20', 'launcher-21', 'launcher-22', 'launcher-23', 'launcher-24', 'launcher-25', 'launcher-26', 'launcher-27', 'launcher-28', 'launcher-29']" b'org.gnome.gnome-panel.layout' b'toplevel-id-list' b"['top-panel', 'bottom-panel']" InstallationDate: Installed on 2021-11-17 (675 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash SourcePackage: gnome-panel UpgradeStatus: Upgraded to jammy on 2023-02-20 (215 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2037151/+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 1947420] Re: Buggish interface @ workstation panels previews when using dual portrait
** Changed in: mate-panel (Ubuntu) Status: Invalid => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libwnck3 in Ubuntu. https://bugs.launchpad.net/bugs/1947420 Title: Buggish interface @ workstation panels previews when using dual portrait Status in MATE Desktop: New Status in libwnck3 package in Ubuntu: Fix Released Status in mate-panel package in Ubuntu: Confirmed Status in libwnck3 package in Debian: Confirmed Bug description: ...Freshly upgraded to 21.10 using the same OS that I used to open most of my previous video glitches ever... EDIT:(Because in my mind I have opened several exotic bugs video related (quite possibly originating from my monitor setup?)) Using 2x monitor in portrait mode, the preview panel/widget(?) located at the bottom right side shows 2 things wrong: 1. The "Workspace 1" preview is very elongated when compared to not only all of it's previous incarnations (from 14.04 to 21.10) but also has an inconsistent size when compared to it's neighbouring "Workspace 2". Expectation: both 1 and 2 should be sized identically. 2. When hovering the mouse cursor on "Workspace 2" only it's left portion will highlight. Expectation: both monitors of "2" should highlight See enclosed picture. To manage notifications about this bug go to: https://bugs.launchpad.net/mate-desktop/+bug/1947420/+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 1990263] Re: bamfdaemon crashes with libwnck3 43.0-1
https://gitlab.gnome.org/GNOME/libwnck/-/merge_requests/46 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libwnck3 in Ubuntu. https://bugs.launchpad.net/bugs/1990263 Title: bamfdaemon crashes with libwnck3 43.0-1 Status in libwnck3 package in Ubuntu: New Bug description: bamfdaemon crashes with libwnck3 43.0-1 Thread 1 "bamfdaemon" received signal SIGSEGV, Segmentation fault. 0x77e10616 in invalidate_icons (self=0x5581da30) at ../libwnck/wnck-handle.c:81 81../libwnck/wnck-handle.c: Datei oder Verzeichnis nicht gefunden. (gdb) bt #0 0x77e10616 in invalidate_icons (self=0x5581da30) at ../libwnck/wnck-handle.c:81 #1 0x555713ca in bamf_legacy_screen_get_default () at ./src/bamf-legacy-screen.c:591 #2 0x5557b695 in bamf_legacy_screen_get_default () at ./src/bamf-matcher.c:3192 #3 bamf_matcher_init (self=0x55868140) at ./src/bamf-matcher.c:3137 #4 0x77204791 in g_type_create_instance () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 #5 0x771eb8cf in () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 #6 0x771ed118 in g_object_new_with_properties () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 #7 0x771edec1 in g_object_new () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 #8 0x5557b758 in bamf_matcher_get_default () at ./src/bamf-matcher.c:3290 #9 0x55574861 in bamf_on_bus_acquired (connection=0x55628000, name=, self=0x55697320) at ./src/bamf-daemon.c:59 #10 0x7733b905 in () at /lib/x86_64-linux-gnu/libgio-2.0.so.0 #11 0x772da559 in () at /lib/x86_64-linux-gnu/libgio-2.0.so.0 #12 0x772da783 in () at /lib/x86_64-linux-gnu/libgio-2.0.so.0 #13 0x77337e22 in () at /lib/x86_64-linux-gnu/libgio-2.0.so.0 #14 0x772da559 in () at /lib/x86_64-linux-gnu/libgio-2.0.so.0 #15 0x772da59d in () at /lib/x86_64-linux-gnu/libgio-2.0.so.0 #16 0x770e33bf in g_main_context_dispatch () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #17 0x77138098 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #18 0x770e2a6f in g_main_loop_run () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #19 0x5556c43b in main (argc=, argv=) at ./src/main.c:65 Happens when running gnome-xorg/x11 session under gnome-shell 43.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libwnck3/+bug/1990263/+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 1030022] Re: Port from legacy Xlib to modern XCB
** No longer affects: compiz ** Changed in: compiz (Ubuntu) Status: Triaged => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/1030022 Title: Port from legacy Xlib to modern XCB Status in 9wm package in Ubuntu: New Status in aewm package in Ubuntu: New Status in aewm++ package in Ubuntu: New Status in afterstep package in Ubuntu: New Status in amiwm package in Ubuntu: Invalid Status in blackbox package in Ubuntu: New Status in cairo package in Ubuntu: New Status in compiz package in Ubuntu: Invalid Status in ctwm package in Ubuntu: New Status in dwm package in Ubuntu: Opinion Status in enlightenment package in Ubuntu: New Status in fvwm package in Ubuntu: New Status in fvwm1 package in Ubuntu: New Status in gtk+3.0 package in Ubuntu: New Status in icewm package in Ubuntu: New Status in jwm package in Ubuntu: Invalid Status in larswm package in Ubuntu: New Status in lwm package in Ubuntu: New Status in matchbox-window-manager package in Ubuntu: New Status in metacity package in Ubuntu: Invalid Status in miwm package in Ubuntu: New Status in muffin package in Ubuntu: Fix Released Status in mutter package in Ubuntu: Fix Released Status in pekwm package in Ubuntu: New Status in ratpoison package in Ubuntu: New Status in sapphire package in Ubuntu: New Status in sawfish package in Ubuntu: New Status in spectrwm package in Ubuntu: Fix Released Status in tinywm package in Ubuntu: New Status in tritium package in Ubuntu: New Status in twm package in Ubuntu: New Status in vtwm package in Ubuntu: New Status in w9wm package in Ubuntu: New Status in windowlab package in Ubuntu: New Status in wm2 package in Ubuntu: New Status in wmaker package in Ubuntu: Opinion Status in xmonad package in Ubuntu: New Bug description: Port/rewrite the window manager to use the modern XCB (X C Binding) library instead of the old legacy Xlib. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/9wm/+bug/1030022/+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 1721955] Re: Human, Human-Clearlooks and other themes have incorrect gray window title color
** Changed in: compiz (Ubuntu) Status: Confirmed => Invalid -- 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/1721955 Title: Human, Human-Clearlooks and other themes have incorrect gray window title color Status in human-theme: New Status in community-themes package in Ubuntu: New Status in compiz package in Ubuntu: Invalid Status in gtk+2.0 package in Ubuntu: New Status in gtk+3.0 package in Ubuntu: New Status in human-theme package in Ubuntu: Confirmed Status in marco package in Ubuntu: Invalid Status in mate-themes package in Ubuntu: Invalid Bug description: Steps to reproduce: 1. Install Ubuntu 17.10 MATE or 18.04 LTS MATE 2. Install Human theme from `human-theme` package 3. Select Human theme from `mate-control-center` Appearance Expected results: window title color is set to Ubuntu's orange (#FFBE6B) Actual results: window title color is set to different gray/silver color (#a5a5a2) Note: other themes are affected too. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: human-theme 0.39.2 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic i686 ApportVersion: 2.20.7-0ubuntu2 Architecture: i386 CurrentDesktop: MATE Date: Sat Oct 7 15:43:03 2017 InstallationDate: Installed on 2017-10-07 (0 days ago) InstallationMedia: Ubuntu-MATE 17.10 "Artful Aardvark" - Alpha i386 (20170925.1) PackageArchitecture: all SourcePackage: human-theme UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/human-theme/+bug/1721955/+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 1949200] Re: gnome-shell crashed with SIGTRAP from error "Can't create a GtkStyleContext without a display connection" in gtk_style_context_init
3v1n0, gtk-module-Handle-display-closing-gracefully.patch introduced regression! Why are you setting d->object to NULL in on_object_disposed? By doing that you are introducing memory leak, no? Creating SoundEventData structure strong reference is added, it must be removed otherwise object will never get finalized!? I am attaching small test app that can be used to reproduce problem - it simply prints warning messages when GObject / GtkWindow is disposed and/or finalized. Basically looks like now canberra-gtk-module adds two extra refs that are not removed. Also with attached test app free_sound_event now is never called with d->object != NULL. ** Attachment added: "Test app" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1949200/+attachment/5606320/+files/test-gtk.c -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libcanberra in Ubuntu. https://bugs.launchpad.net/bugs/1949200 Title: gnome-shell crashed with SIGTRAP from error "Can't create a GtkStyleContext without a display connection" in gtk_style_context_init Status in gnome-shell package in Ubuntu: Won't Fix Status in libcanberra package in Ubuntu: Fix Released Bug description: GNOME Shell isn't meant to use GTK at all, but it's repeatedly crashing in GTK since the introduction of GNOME 40. https://errors.ubuntu.com/problem/45d4ce4e8f26828ab6993261e8a20208ecf261b0 https://errors.ubuntu.com/problem/e60359af65f32c18a4a6ccc93fd3469b0e675844 https://errors.ubuntu.com/problem/73a93ba578f68516e680373ae324db01336e8bad https://errors.ubuntu.com/problem/d69ccaf1379f588b04ecac2a6cc93b9be31100b4 This seems to be a result of Xwayland crashing and gnome-shell then trying to recover (and failing). Although gnome-shell shouldn't be using GTK, and Wayland sessions shouldn't be dependent on having an X11 server (Xwayland) available. Fixing either of those should resolve this. WORKAROUND: sudo apt remove libcanberra-gtk3-module TEST CASE: 1. Log into a Wayland session. 2. Open a Terminal. 3. $ xrandr # Just to ensure Xwayland starts 4. $ killall Xwayland Expected: gnome-shell still responds. Observed: gnome-shell freezes or exits. --- ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: gnome-shell 40.5-1ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu72 Architecture: amd64 CasperMD5CheckResult: pass CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Fri Oct 29 15:11:43 2021 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2021-10-27 (2 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211023) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANG=nb_NO.UTF-8 LANGUAGE=nb_NO:nb:no_NO:no:nn_NO:nn:en PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 40.5-1ubuntu2 Signal: 5 SourcePackage: gnome-shell StacktraceTop: g_log_writer_default () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_log_structured_array () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_log_structured_standard () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libgtk-3.so.0 g_type_create_instance () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: gnome-shell crashed with signal 5 in g_log_writer_default() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1949200/+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 1947420] Re: Buggish interface @ workstation panels previews when using dual portrait
Martin, this *IS* bug in mate-panel, next release libwnck release will have same problem... Revert in libwnck was added only because libwnck was released as 40.0 while it really should have been 41.alpha! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libwnck3 in Ubuntu. https://bugs.launchpad.net/bugs/1947420 Title: Buggish interface @ workstation panels previews when using dual portrait Status in MATE Desktop: New Status in libwnck3 package in Ubuntu: Fix Released Status in mate-panel package in Ubuntu: Invalid Bug description: ...Freshly upgraded to 21.10 using the same OS that I used to open most of my previous video glitches ever... Using 2x monitor in portrait mode, the preview panel/widget(?) located at the bottom right side shows 2 things wrong: 1. The "Workspace 1" preview is very elongated when compared to not only all of it's previous incarnations (from 14.04 to 21.10) but also has an inconsistent size when compared to it's neighbouring "Workspace 2". Expectation: both 1 and 2 should be sized identically. 2. When hovering the mouse cursor on "Workspace 2" only it's left portion will highlight. Expectation: both monitors of "2" should highlight See enclosed picture. To manage notifications about this bug go to: https://bugs.launchpad.net/mate-desktop/+bug/1947420/+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 1664369] Re: Super key always applied for VNC session
Is this still problem in 20.04? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/1664369 Title: Super key always applied for VNC session Status in metacity package in Ubuntu: New Bug description: This a regression report for bug 1440570 with the latest package installed on 14.04 Trusty. Problem still reproduces exactly as specified. Every time I press 'N' in terminal over VNC, a new window is opened. I don't want to delete my super key mappings, they are quite useful when interacting with the machine locally but I also need remote access to things like a web browser and VNC is most useful for this. Unfortunately the super key is constantly on. I saw that 1440570 was closed with a fix, I might have undone the fix because I used gnome- tweak-tool to swap my Alt-Win keys (Alt-Win behavior under typing). Even after switching this back however, the problem persists over VNC, making it unusable. Let me know what I can do to help debug. Output of apt list metacity: Listing... Done metacity/trusty-updates,now 1:2.34.13-0ubuntu4.1 amd64 [installed] Output of lsb_release -rd: Description:Ubuntu 14.04.5 LTS Release:14.04 #regression-update ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 4.4.0-62.83~14.04.1-generic 4.4.40 Uname: Linux 4.4.0-62-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.23 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Mon Feb 13 11:40:39 2017 DistUpgraded: Fresh install DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-osp1-20150720-0 DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: oem-audio-hda-daily-lts-xenial, 0.201611160201~ubuntu14.04.1, 4.4.0-62-generic, x86_64: installed synaptic-i2c-hid-3.13.0-32-backport, 1.6.4: added ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Sky Lake Integrated Graphics [8086:1912] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:06b9] InstallationDate: Installed on 2016-12-16 (59 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20150720-04:06 MachineType: Dell Inc. OptiPlex 7040 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-62-generic.efi.signed root=UUID=e4b640d9-85ce-43f1-9369-2744897fd9f5 ro pcie_aspm=off quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/12/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.4.9 dmi.board.name: 0Y7WYT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.4.9:bd09/12/2016:svnDellInc.:pnOptiPlex7040:pvr:rvnDellInc.:rn0Y7WYT:rvrA00:cvnDellInc.:ct3:cvr: dmi.product.name: OptiPlex 7040 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.11.3+14.04.20160425-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri N/A version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Wed Feb 8 15:18:04 2017 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 16485 vendor DEL xserver.version: 2:1.18.3-1ubuntu2.3~trusty1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/1664369/+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 1947420] Re: Buggish interface @ workstation panels previews when using dual portrait
This is not libwnck problem! ** Changed in: libwnck3 (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libwnck3 in Ubuntu. https://bugs.launchpad.net/bugs/1947420 Title: Buggish interface @ workstation panels previews when using dual portrait Status in MATE Desktop: New Status in Ubuntu MATE: Confirmed Status in libwnck3 package in Ubuntu: Invalid Status in mate-panel package in Ubuntu: Confirmed Bug description: ...Freshly upgraded to 21.10 using the same OS that I used to open most of my previous video glitches ever... Using 2x monitor in portrait mode, the preview panel/widget(?) located at the bottom right side shows 2 things wrong: 1. The "Workspace 1" preview is very elongated when compared to not only all of it's previous incarnations (from 14.04 to 21.10) but also has an inconsistent size when compared to it's neighbouring "Workspace 2". Expectation: both 1 and 2 should be sized identically. 2. When hovering the mouse cursor on "Workspace 2" only it's left portion will highlight. Expectation: both monitors of "2" should highlight See enclosed picture. To manage notifications about this bug go to: https://bugs.launchpad.net/mate-desktop/+bug/1947420/+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 1922795] Re: Gnome panel got stuck
** Package changed: gnome-panel (Ubuntu) => gnome-shell (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1922795 Title: Gnome panel got stuck Status in gnome-shell package in Ubuntu: New Bug description: I closed the lid of my laptop, then opened it and launched a browser by clicking it's icon on the left panel. After that all the panels in Gnome got stuck - clicking on the left or top panels gives nothing. I still can access the global menu via the Win key, also hot corners work. But the panels are not only frozen - they seem to be ignored by the window manager, because when I open some app, it is placed under a panel just like the panel did not exist at all. These happened to me already twice. I have: Ubuntu 20.04.2 LTS, kernel 5.8.0-48-generic Gnome version 3.36.8, Windowing System X11 HP Pavilion Laptop 15-cw1007nv To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1922795/+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 1001970] Re: Window placement grid broken or not existent
** Changed in: metacity (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/1001970 Title: Window placement grid broken or not existent Status in metacity package in Ubuntu: Invalid Bug description: Window placement grid is broken or does not exist. Ctrl+Alt+Numpad[0-9] does not work. WinKey+Numpad[0-9] does not work. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: metacity 1:2.34.1-1ubuntu11 ProcVersionSignature: Ubuntu 3.2.0-24.37-generic 3.2.14 Uname: Linux 3.2.0-24-generic x86_64 ApportVersion: 2.0.1-0ubuntu7 Architecture: amd64 Date: Sun May 20 16:46:19 2012 InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) SourcePackage: metacity UpgradeStatus: Upgraded to precise on 2012-02-01 (108 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/1001970/+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 242825] Re: large window frames misrender
This might be fixed, in quick test I was not able to reproduce this. ** Changed in: metacity (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/242825 Title: large window frames misrender Status in metacity package in Ubuntu: Invalid Bug description: Binary package hint: metacity I have a wide screen. And when I maximise windows the drag bar at the top misrenders above 3349 pixels wide. It just seems to run out of picture on the right end. I can recreate this effect on small screens by pushing the window off the left edge and widening. I'm guessing this is a metacity bug, but it might be something else. I do not have compiz running. It does not happen with xfwm. I have attached a screenshot - the bit with import bisect is actually leftovers from another window. Description: Ubuntu 8.04 Release: 8.04 metacity: Installed: 1:2.22.0-0ubuntu4 Candidate: 1:2.22.0-0ubuntu4 Version table: *** 1:2.22.0-0ubuntu4 0 500 http://us.archive.ubuntu.com hardy/main Packages 100 /var/lib/dpkg/status It happens on these two drivers: (II) Module nvidia: vendor="NVIDIA Corporation" compiled for 4.0.2, module version = 1.0.0 Module class: X.Org Video Driver (II) LoadModule: "intel" (II) Loading /usr/lib/xorg/modules/drivers//intel_drv.so (II) Module intel: vendor="X.Org Foundation" compiled for 1.4.0.90, module version = 2.2.1 Module class: X.Org Video Driver ABI class: X.Org Video Driver, version 2.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/242825/+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 907724] Re: can't assign numpad keys correctly to shortcuts
** Changed in: metacity (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/907724 Title: can't assign numpad keys correctly to shortcuts Status in metacity package in Ubuntu: Invalid Bug description: uname -a : Linux -Ubuntu-x64 3.0.0-14-generic #23-Ubuntu SMP Mon Nov 21 20:28:43 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux running Unity. I switch workspaces a lot so i found it usefull to be able to switch them even quicker by assigning the directions to the arrow keys on the numpad. My numpad is (while Numlock is off) a bunch of PageUp, PageDown, Home, End et cetera keys. When turning numlock on, all these functions are disabled in favor to the numbers. The problem is, that the shortcut is apparently not assigned to the Arrow but the Key itself, so pressing Num4 also triggers the shortcut to switch to the left, even while Numlock is activated. Thus, assigning shortcuts to the NumPad - Arrows makes it absolutely unusable to enter numbers, which in some way is the main use of the numpad. What I'd like it to be like: While the NumLock is off, i can trigger the Shortcut. While the NumLock is on, i can type numbers. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/907724/+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 13521] Re: window content not redrawn correctly when using 'reduced_resources'
** Changed in: metacity (Ubuntu) Status: Triaged => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/13521 Title: window content not redrawn correctly when using 'reduced_resources' Status in Metacity: New Status in metacity package in Ubuntu: Invalid Bug description: metacity: 1:2.9.34-0ubuntu1 if /apps/metacity/general/reduced_resources is set to 1 (or checked) when maximizing nautilus windows (through doubleclicking the titlebar) artificials of the hor and vert bars appear on the background. It seems when doubleclicking the titlebar the background will not be redrawn after resize. http://bugzilla.gnome.org/show_bug.cgi?id=161239: http://bugzilla.gnome.org/show_bug.cgi?id=161239 To manage notifications about this bug go to: https://bugs.launchpad.net/metacity/+bug/13521/+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 597227] Re: Should Metacity really show up as a program in Software Center instead of a system package?
** Changed in: metacity (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/597227 Title: Should Metacity really show up as a program in Software Center instead of a system package? Status in metacity package in Ubuntu: Invalid Status in software-center package in Ubuntu: Incomplete Bug description: software-center 2.0.5, Ubuntu 10.04 software-center 4.0.4, Ubuntu 11.04 1. Navigate to "Installed Software". 2. Scroll down to M. What happens: Metacity shows up by default. Any user can be looking through the installed software and think, "Metacity? GTK window manager? What's that? I don't need that!" and remove it, which I'm sure would cause some serious problems if that user decided to turn off visual effects or never had them on in the first place. Also, Metacity seems more like a system package than a program. What should happen: Metacity should be hidden by default, not appearing unless you choose "Show technical items". This can be implemented by removing Metacity's desktop file. [This bug report also previously mentioned capitalization of "Get Software" and "Installed Software", which is mostly obviated by the 5.0 redesign.] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/597227/+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 1001970] Re: Window placement grid broken or not existent
Placement grid? Can you give more info in case this is still relevant to you? ** Changed in: metacity (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/1001970 Title: Window placement grid broken or not existent Status in metacity package in Ubuntu: Incomplete Bug description: Window placement grid is broken or does not exist. Ctrl+Alt+Numpad[0-9] does not work. WinKey+Numpad[0-9] does not work. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: metacity 1:2.34.1-1ubuntu11 ProcVersionSignature: Ubuntu 3.2.0-24.37-generic 3.2.14 Uname: Linux 3.2.0-24-generic x86_64 ApportVersion: 2.0.1-0ubuntu7 Architecture: amd64 Date: Sun May 20 16:46:19 2012 InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) SourcePackage: metacity UpgradeStatus: Upgraded to precise on 2012-02-01 (108 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/1001970/+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 1459128] Re: metacity no longer honors keybindings without modmask?
I guess this is fixed in newer versions? ** Changed in: metacity (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/1459128 Title: metacity no longer honors keybindings without modmask? Status in metacity package in Ubuntu: Incomplete Bug description: I'm extremely attached to the following two keybindings: $ dconf read /org/gnome/desktop/wm/keybindings/raise ['F1'] $ dconf read /org/gnome/desktop/wm/keybindings/lower ['F2'] But they stopped working for me in metacity 2.34.13. (That is, I hit F1/F2 expecting the window under the mouse cursor to be raised/lowered respectively, and it doesn't happen.) When I run `METACITY_VERBOSE=1 METACITY_USE_LOGFILE=1 metacity --replace` and install my keybindings: $ dconf write /org/gnome/desktop/wm/keybindings/raise "['F1']" $ dconf write /org/gnome/desktop/wm/keybindings/lower "['F2']" I notice the following appears in the log file: KEYBINDINGS: Will not grab keybinding F1 without modmask. KEYBINDINGS: Will not grab keybinding F2 without modmask. If I then try installing similar bindings with a modmask: $ dconf write /org/gnome/desktop/wm/keybindings/raise "['F1']" $ dconf write /org/gnome/desktop/wm/keybindings/lower "['F2']" no such log message occurs, and the modified keybindings work! When I searched for that log message on the web, it led to this recent commit and bug reference: https://mail.gnome.org/archives/commits-list/2015-April/msg01612.html https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/1440570 Note however that this bug seems to refer to VNC, which I am not using. So is it the case that F1/F2, unmodified, can no longer be keyboard shortcuts? This would make me very sad, since I've used them several thousand times per day for the last 25 years or so, and I'm not sure I can rewire my fingers at this point. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/1459128/+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 952922] Re: grab handles on certain windows do not work
In case you still use Metacity, do you have same problem in Ubuntu 20.04+? ** Changed in: metacity (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/952922 Title: grab handles on certain windows do not work Status in metacity package in Ubuntu: Incomplete Bug description: When I open evince or nautilus, it is impossible to move up and down on the screen by grabbing the "handle" on the side. I have just tried with evince and nautilus, am assuming the problem is universal and caused by metacity. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: metacity 1:2.34.1-1ubuntu7 ProcVersionSignature: Ubuntu 3.2.0-18.26-lowlatency-pae 3.2.9 Uname: Linux 3.2.0-18-lowlatency-pae i686 ApportVersion: 1.94.1-0ubuntu2 Architecture: i386 Date: Mon Mar 12 07:50:55 2012 InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta i386 (20120301) ProcEnviron: TERM=xterm LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: metacity UpgradeStatus: Upgraded to precise on 2012-03-03 (8 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/952922/+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 1448429] Re: GNOME Flashback (Metacity): Compose Key not working as expected
Is this still problem in Ubuntu 20.04 or newer? ** Changed in: metacity (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/1448429 Title: GNOME Flashback (Metacity): Compose Key not working as expected Status in metacity package in Ubuntu: Incomplete Bug description: 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu Description: Ubuntu 15.04 Release: 15.04 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center xorg: Installed: 1:7.7+7ubuntu4 Candidate: 1:7.7+7ubuntu4 3) What you expected to happen The key combination AltGr + [ a produces ä (latin small letter a with diaresis) Works in GNOME Flashback (Compiz). 4) What happened instead The key combination AltGr + [ a produces ¨a Does not work in GNOME Flashback (Metacity). ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME-Flashback:Unity Date: Sat Apr 25 13:05:09 2015 DistUpgraded: 2015-04-23 21:17:34,692 DEBUG enabling apt cron job DistroCodename: vivid DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: No GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:21da] InstallationDate: Installed on 2013-10-28 (543 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: LENOVO 4291NA7 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-15-generic root=UUID=3b21f524-fe80-4ab0-8b84-c03e44abcd8b ro elevator=deadline quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to vivid on 2015-04-23 (1 days ago) dmi.bios.date: 04/11/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 8DET68WW (1.38 ) dmi.board.asset.tag: Not Available dmi.board.name: 4291NA7 dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr8DET68WW(1.38):bd04/11/2013:svnLENOVO:pn4291NA7:pvrThinkPadX220:rvnLENOVO:rn4291NA7:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 4291NA7 dmi.product.version: ThinkPad X220 dmi.sys.vendor: LENOVO 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 Apr 25 13:04:39 2015 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id4204 vendor AUO xserver.version: 2:1.17.1-0ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/1448429/+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 1780468] Re: Blurry titlebar font when window is not maximized
Is this still problem in 20.04 or newer Ubuntu versions? ** Changed in: metacity (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/1780468 Title: Blurry titlebar font when window is not maximized Status in metacity package in Ubuntu: Incomplete Bug description: What happens I've configured Compiz window manager to use gtk-window-decorator so that it may apply my Metacity theme for the titlebars. With this decorator, I've noticed that Compiz renders slightly blurry titlebar fonts when a window is not maximized. Once the window is maximized, sharp fonts are rendered. When a window is not maximized, the font seems to lack sub-pixel hinting or anti-aliasing, hence the slightly blurry appearance. I zoomed in on the font when the window was maximized and observed bluish lines around the characters. When a window was not maximized, the zoomed-in characters didn't have the bluish lines. I've tested and seen that the Marco window manager and the Emerald decorator (used with Compiz) both render sharp titlebar fonts regardless of whether a window is maximized or not. The image in the below link shows the slight difference in font rendering when Compiz is used with gtk-window-decorator. Firefox's window was maximized, with sharp text, while VLC's window was not maximized, with slightly blurry text. https://i.stack.imgur.com/5BalZ.png Upon switching to Marco window manager, both texts are sharp. https://i.stack.imgur.com/9Gzli.png When the "Compiz with gtk-window-decorator" setup is zoomed-in, blue lines around the maximized Firefox window titlebar text are visible (it looks like sub-pixel rendering to me). The blue lines are completely lacking in the un-maximized VLC window titlebar text. https://i.stack.imgur.com/XDSAU.png What I expect to happen --- The titlebar font rendering should be sharp for both maximized and un-maximized windows. The cause (clip_to_rounded_corners) --- Upon investigating, I've discovered that Compiz's gtk-window-decorator uses the libmetacity library. The clip_to_rounded_corners() function in "meta-theme-metacity.c" is called to draw rounded corners for the un-maximized windows in my theme. It seems the call to draw rounded corners by cairo_arc() in that function somehow affects the font rendering. When windows are maximized, the drawing of rounded corners is not performed, hence the sharp font rendering. I rebuilt the libmetacity library with the clip_to_rounded_corners() call commented out and achieved sharp fonts for un-maximized windows. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: metacity 1:3.28.0-1 ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18 Uname: Linux 4.15.0-24-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: MATE Date: Fri Jul 6 19:52:03 2018 InstallationDate: Installed on 2018-05-06 (61 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: metacity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/1780468/+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 1761873] Re: App title bar says "as superuser", but that's not the case
** Changed in: metacity (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/1761873 Title: App title bar says "as superuser", but that's not the case Status in metacity package in Ubuntu: Fix Released Bug description: I installed GIMP via flatpak. When I open GIMP, what I say in the summary above happens. I raised the problem on a GIMP users list. I was told that the same thing does NOT happen when GIMP is installed via flatpak in Fedora. The person who gave me that information also reported a bug to flatpak based on what I'd said, but flatpak closed the bug, claiming that the error isn't a flatpak error, but a Ubuntu error. Hence this report. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gnome-flashback 3.18.2-1ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-119.143-generic 4.4.114 Uname: Linux 4.4.0-119-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CurrentDesktop: GNOME-Flashback:Unity Date: Fri Apr 6 16:35:26 2018 InstallationDate: Installed on 2016-07-28 (617 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: gnome-flashback UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/1761873/+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 1842425] Re: No GUI with Gnome Flashback or Classic after apt dist-upgrade; Ubuntu on Wayland OK
** Changed in: gnome-flashback (Ubuntu) Status: New => Incomplete -- 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/1842425 Title: No GUI with Gnome Flashback or Classic after apt dist-upgrade; Ubuntu on Wayland OK Status in gnome-flashback package in Ubuntu: Incomplete Status in linux-signed-hwe package in Ubuntu: New Status in xorg-server package in Ubuntu: New Bug description: Did apt dist-upgrade . I usually use Gnome Flashback. Now rebooting with 5.0.0.27 or 5.0.25 and logging in at GUI screen only works for "Ubuntu on Wayland". Other attempts: (1) Flashback: login transitions to purple background screen and no mouse. hitting alt-ctrl-F1 leads to an unlock screen with a next button. entering pw and clicking NEXT leads to animated circle wait icon. alt-ctrl-f2 leads to a TTY2 text mode console login screen. Login and sudo shutdown now -r (2) Gnome Classic: login transitions to a blank screen with the LCD displaying a "No video" message. alt-ctrl-f1 and unlocking there also transitions to a blank screen with the LCD displaying a "No video" message. alt-ctrl-f3 then Login and sudo shutdown now -r. (3) Ubuntu: same as with Gnome Classic. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-flashback 3.28.0-1ubuntu1.4 ProcVersionSignature: Ubuntu 5.0.0-25.26~18.04.1-generic 5.0.18 Uname: Linux 5.0.0-25-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Sep 3 15:17:32 2019 InstallationDate: Installed on 2018-07-27 (403 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gnome-flashback UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-flashback/+bug/1842425/+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 1903224] Re: Pressing the launch terminal shortcut in activities view launches two terminals instead of one when CTRL modifier is used
** Package changed: metacity (Ubuntu) => gnome-shell (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1903224 Title: Pressing the launch terminal shortcut in activities view launches two terminals instead of one when CTRL modifier is used Status in gnome-shell package in Ubuntu: New Bug description: lsb_release -rd Description: Ubuntu 20.04.1 LTS Release: 20.04 Package: Xorg or Gnome, not really sure. Problem description: 1. I have set the Launch terminal shortcut in Settings/Keyboard shortcuts to CTRL+`. 2. I invoke the activities overview by pressing SUPER once. 3. I launch a terminal by pressing the newly set CTRL+` shortcut. What happened: two new terminal windows appeared. What is expected: launch only one terminal window. More info: This only happens when a CTRL modifier is used and the key is set to a non function (F1-F12) key. When an ALT or CTRL+ALT shortcut is used, only one window appears, as expected. Expected behaviour: launch only one terminal window while in the activities overview. What happened: two new terminal windows appeared in the activities overview. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1903224/+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 1893110] Re: Cant remove desktop icons ubuntu 20.04
GNOME Flashback has builtin desktop icons! Only org.gnome.gnome- flashback.desktop settings control whether gnome-flashback shows or not desktop icons. "org.gnome.gnome-flashback.desktop show-icons false" shows that icons are disabled. :) If you still get icons you have some other application auto-started that provides desktop icons. From your GSettings list it could be nemo. Check if there is nemo and/or nemo-desktop process running. ** Package changed: metacity (Ubuntu) => gnome-flashback (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/1893110 Title: Cant remove desktop icons ubuntu 20.04 Status in gnome-flashback package in Ubuntu: New Bug description: I've just upgraded to 20.04 from 18.04 and am having this issue using Gnome Flashback(metacity) desktop. The 'Home' and 'Trash' icons on my desktop continue to be there even after i have changed the settings using gsettings set the text below shows the output of gsettings list-recursively | grep icons -- i tried to add a screenshot but failed! edited to add screenshot link: https://imagizer.imageshack.com/img923/6561/LHeSfQ.png (base) matt@zakk-jr:~$ gsettings list-recursively | grep icons org.gnome.evolution.calendar show-icons-month-view false org.nemo.icon-view labels-beside-icons false org.gnome.gnome-flashback.desktop show-icons false org.cinnamon.desktop.interface menus-have-icons true org.cinnamon.desktop.interface buttons-have-icons false org.cinnamon.desktop.interface toolbar-icons-size 'large' org.gnome.gnome-flashback.desktop.icons icon-size '48px' org.gnome.gnome-flashback.desktop.icons column-spacing uint32 10 org.gnome.gnome-flashback.desktop.icons show-home false org.gnome.gnome-flashback.desktop.icons sort-by 'name' org.gnome.gnome-flashback.desktop.icons show-trash false org.gnome.gnome-flashback.desktop.icons placement 'free' org.gnome.gnome-flashback.desktop.icons row-spacing uint32 2 org.gnome.gnome-flashback.desktop.icons extra-text-width uint32 48 org.gnome.shell.extensions.openweather use-symbolic-icons true org.gnome.shell.extensions.topicons icon-size 24 org.gnome.shell.extensions.topicons icon-saturation 0.40002 org.gnome.shell.extensions.topicons tray-pos 'center' org.gnome.shell.extensions.topicons icon-contrast 0.0 org.gnome.shell.extensions.topicons icon-spacing 12 org.gnome.shell.extensions.topicons tray-order 1 org.gnome.shell.extensions.topicons icon-brightness 0.0 org.gnome.shell.extensions.topicons icon-opacity 220 org.gnome.desktop.background show-desktop-icons false org.gnome.desktop.interface menus-have-icons false org.gnome.desktop.interface buttons-have-icons false org.gnome.desktop.interface toolbar-icons-size 'large' org.gnome.shell.extensions.desktop-icons show-trash false org.gnome.shell.extensions.desktop-icons icon-size 'standard' org.gnome.shell.extensions.desktop-icons show-home false org.nemo.desktop show-desktop-icons false org.nemo.desktop show-orphaned-desktop-icons false org.gnome.gnome-panel.general prefer-symbolic-icons false I cant find any other settings that relate to this. If i create another user and use the metacity desktop the command gsettings set ortg.gnome,gnome.flashback.desktop show-icons false removes the icons, but not with my main user account further edit to show dconf-editor settings screenshot: https://imagizer.imageshack.com/img923/6079/l1CVh1.png To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-flashback/+bug/1893110/+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 1878440] Re: gnome-panel - hplip - icon-menu empty
I think real bug is in indicator-application. Definitely not in indicator-applet as it only loads various indicators. I guess it could be fixed also in hplip... For some reason menu is set after some delay - https://git.launchpad.net/ubuntu/+source/hplip/tree/ui5/systemtray.py#n359 ** Changed in: hplip (Ubuntu) Status: Invalid => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/1878440 Title: gnome-panel - hplip - icon-menu empty Status in gnome-flashback package in Ubuntu: Invalid Status in hplip package in Ubuntu: Confirmed Status in indicator-application package in Ubuntu: Confirmed Bug description: in gnome-panel (gnome-flashback) there is an icon for hp-printer (looks like part of indicator-applet), if i click it, a menu is shown, but no readable menuentries. i tried to make screenshot while menu is open, but menu is not visble on this screenshot (seems like it is some kind of overlay). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: hplip 3.20.3+dfsg0-2 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CupsErrorLog: CurrentDesktop: GNOME-Flashback:GNOME Date: Wed May 13 17:33:35 2020 InstallationDate: Installed on 2020-04-27 (16 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lpstat: device for HP-Color-LaserJet-MFP-M277dw: socket://192.168.0.200 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 27c6:530c Shenzhen Goodix Technology Co.,Ltd. Fingerprint Reader Bus 001 Device 002: ID 0c45:671f Microdia Integrated_Webcam_HD Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. G5 5590 Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/HP-Color-LaserJet-MFP-M277dw.ppd'] failed with exit code 2: grep: /etc/cups/ppd/HP-Color-LaserJet-MFP-M277dw.ppd: Permission denied ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=7c9113b7-ca65-4c46-9435-f5d2b73bab72 ro quiet splash vt.handoff=7 SourcePackage: hplip UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/07/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.12.0 dmi.board.name: 0KW84T dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.12.0:bd02/07/2020:svnDellInc.:pnG55590:pvr:rvnDellInc.:rn0KW84T:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: GSeries dmi.product.name: G5 5590 dmi.product.sku: 08EA dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-flashback/+bug/1878440/+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 1878440] Re: gnome-panel - hplip - icon-menu empty
Don't know... This needs to be done after hplip tray icon is added/started. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/1878440 Title: gnome-panel - hplip - icon-menu empty Status in gnome-flashback package in Ubuntu: Invalid Status in hplip package in Ubuntu: Invalid Status in indicator-application package in Ubuntu: Confirmed Bug description: in gnome-panel (gnome-flashback) there is an icon for hp-printer (looks like part of indicator-applet), if i click it, a menu is shown, but no readable menuentries. i tried to make screenshot while menu is open, but menu is not visble on this screenshot (seems like it is some kind of overlay). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: hplip 3.20.3+dfsg0-2 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CupsErrorLog: CurrentDesktop: GNOME-Flashback:GNOME Date: Wed May 13 17:33:35 2020 InstallationDate: Installed on 2020-04-27 (16 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lpstat: device for HP-Color-LaserJet-MFP-M277dw: socket://192.168.0.200 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 27c6:530c Shenzhen Goodix Technology Co.,Ltd. Fingerprint Reader Bus 001 Device 002: ID 0c45:671f Microdia Integrated_Webcam_HD Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. G5 5590 Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/HP-Color-LaserJet-MFP-M277dw.ppd'] failed with exit code 2: grep: /etc/cups/ppd/HP-Color-LaserJet-MFP-M277dw.ppd: Permission denied ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=7c9113b7-ca65-4c46-9435-f5d2b73bab72 ro quiet splash vt.handoff=7 SourcePackage: hplip UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/07/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.12.0 dmi.board.name: 0KW84T dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.12.0:bd02/07/2020:svnDellInc.:pnG55590:pvr:rvnDellInc.:rn0KW84T:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: GSeries dmi.product.name: G5 5590 dmi.product.sku: 08EA dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-flashback/+bug/1878440/+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 1878440] Re: gnome-panel - hplip - icon-menu empty
>From quick look this might be problem in indicator-application... Looks like hplip trayicon first is created without menu, "/NO_DBUSMENU" is set as "Menu" for status notifier item. Then it is updated to correct menu path, but indicator does not recreate menu. D-Bus menu is created only when application is added: https://git.launchpad.net/ubuntu/+source/indicator-application/tree/src/indicator-application.c#n555 As workaround use `systemctl --user restart indicator- application.service` to restart indicator application. Then it will pickup / use correct menu path. ** Package changed: indicator-applet (Ubuntu) => indicator-application (Ubuntu) ** Changed in: hplip (Ubuntu) Status: New => Invalid ** Changed in: gnome-flashback (Ubuntu) Status: New => Invalid ** Changed in: indicator-application (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/1878440 Title: gnome-panel - hplip - icon-menu empty Status in gnome-flashback package in Ubuntu: Invalid Status in hplip package in Ubuntu: Invalid Status in indicator-application package in Ubuntu: Confirmed Bug description: in gnome-panel (gnome-flashback) there is an icon for hp-printer (looks like part of indicator-applet), if i click it, a menu is shown, but no readable menuentries. i tried to make screenshot while menu is open, but menu is not visble on this screenshot (seems like it is some kind of overlay). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: hplip 3.20.3+dfsg0-2 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CupsErrorLog: CurrentDesktop: GNOME-Flashback:GNOME Date: Wed May 13 17:33:35 2020 InstallationDate: Installed on 2020-04-27 (16 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lpstat: device for HP-Color-LaserJet-MFP-M277dw: socket://192.168.0.200 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 27c6:530c Shenzhen Goodix Technology Co.,Ltd. Fingerprint Reader Bus 001 Device 002: ID 0c45:671f Microdia Integrated_Webcam_HD Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. G5 5590 Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/HP-Color-LaserJet-MFP-M277dw.ppd'] failed with exit code 2: grep: /etc/cups/ppd/HP-Color-LaserJet-MFP-M277dw.ppd: Permission denied ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=7c9113b7-ca65-4c46-9435-f5d2b73bab72 ro quiet splash vt.handoff=7 SourcePackage: hplip UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/07/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.12.0 dmi.board.name: 0KW84T dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.12.0:bd02/07/2020:svnDellInc.:pnG55590:pvr:rvnDellInc.:rn0KW84T:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: GSeries dmi.product.name: G5 5590 dmi.product.sku: 08EA dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-flashback/+bug/1878440/+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 1878440] Re: gnome-panel - hplip - icon-menu empty
Use Screenshot application to create screenshot. Choose "Grab the whole screen", set few seconds as delay, press "Take Screenshot". Open menu and and after delay screenshot will be created. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/1878440 Title: gnome-panel - hplip - icon-menu empty Status in gnome-flashback package in Ubuntu: New Status in hplip package in Ubuntu: New Status in indicator-applet package in Ubuntu: New Bug description: in gnome-panel (gnome-flashback) there is an icon for hp-printer (looks like part of indicator-applet), if i click it, a menu is shown, but no readable menuentries. i tried to make screenshot while menu is open, but menu is not visble on this screenshot (seems like it is some kind of overlay). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: hplip 3.20.3+dfsg0-2 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CupsErrorLog: CurrentDesktop: GNOME-Flashback:GNOME Date: Wed May 13 17:33:35 2020 InstallationDate: Installed on 2020-04-27 (16 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lpstat: device for HP-Color-LaserJet-MFP-M277dw: socket://192.168.0.200 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 27c6:530c Shenzhen Goodix Technology Co.,Ltd. Fingerprint Reader Bus 001 Device 002: ID 0c45:671f Microdia Integrated_Webcam_HD Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. G5 5590 Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/HP-Color-LaserJet-MFP-M277dw.ppd'] failed with exit code 2: grep: /etc/cups/ppd/HP-Color-LaserJet-MFP-M277dw.ppd: Permission denied ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=7c9113b7-ca65-4c46-9435-f5d2b73bab72 ro quiet splash vt.handoff=7 SourcePackage: hplip UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/07/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.12.0 dmi.board.name: 0KW84T dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.12.0:bd02/07/2020:svnDellInc.:pnG55590:pvr:rvnDellInc.:rn0KW84T:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: GSeries dmi.product.name: G5 5590 dmi.product.sku: 08EA dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-flashback/+bug/1878440/+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 1882558] Re: desktop - missing templates to create new files
Please create separate issues for Ubuntu default session and for GNOME Flashback session... Ubuntu default session use gnome-shell-extension-desktop-icons to manage desktop icons. In GNOME Flashback desktop icons are provided by gnome-flashback and bug should be reported here - https://gitlab.gnome.org/GNOME/gnome- flashback/-/issues. -- 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/1882558 Title: desktop - missing templates to create new files Status in gnome-shell-extension-desktop-icons package in Ubuntu: Triaged Status in nautilus package in Ubuntu: Won't Fix Bug description: Hi, in nautilus i can create new files by templates in (german) directory ~/Vorlagen i miss the option to create files on desktop this way regards Frank To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/1882558/+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 1881115] Re: shift-delete not handled
Nautilus in 20.10 has development release - 3.37.x. You don't want development release in stable / LTS release. Also adding needed change as patch is risky, change is not small: https://gitlab.gnome.org/GNOME/nautilus/-/merge_requests/504 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-desktop-icons in Ubuntu. https://bugs.launchpad.net/bugs/1881115 Title: shift-delete not handled Status in gnome-shell-extension-desktop-icons: Unknown Status in gnome-flashback package in Ubuntu: Fix Released Status in gnome-shell-extension-desktop-icons package in Ubuntu: Triaged Bug description: shift-delete does nothing, in menu there is only "move to trash" (+open +properties), no way to delete files without trash regards Frank ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.36.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME-Flashback:GNOME Date: Thu May 28 14:12:30 2020 GsettingsChanges: b'org.gnome.nautilus.preferences' b'always-use-location-entry' b'true' b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'" b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'owner', 'group', 'permissions', 'where', 'date_modified', 'date_modified_with_time', 'date_accessed', 'recency', 'starred', 'detailed_type']" InstallationDate: Installed on 2020-04-27 (31 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-desktop-icons/+bug/1881115/+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 1883423] Re: no menu bar in LibreOffice
You have at some point added it. Appmenu applet has never been on panel by default. The only bug here is that `indicator-appmenu` should depend on bamfdaemon. If you don't need/want appmenu you can remove indicator- appmenu and bamfdaemon. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1883423 Title: no menu bar in LibreOffice Status in libreoffice package in Ubuntu: New Bug description: In Ubuntu 20.04 with GNOME Flashback session, the top menu bar (File, View etc.) is not present in LibreOffice applications (in regular GNOME Shell, the menu is present OK). There seems to be no way to make the menu appear, except of uninstalling libreoffice-gtk3 package, but then all styling from the GNOME theme is lost and LibreOffice has the "raw" X toolkit look. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1883423/+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 1883423] Re: no menu bar in LibreOffice
Does installing `bamfdaemon` fixes problem? ** Branch linked: lp:~mitya57/indicator-appmenu/depend-on-bamfdaemon -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1883423 Title: no menu bar in LibreOffice Status in libreoffice package in Ubuntu: New Bug description: In Ubuntu 20.04 with GNOME Flashback session, the top menu bar (File, View etc.) is not present in LibreOffice applications (in regular GNOME Shell, the menu is present OK). There seems to be no way to make the menu appear, except of uninstalling libreoffice-gtk3 package, but then all styling from the GNOME theme is lost and LibreOffice has the "raw" X toolkit look. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1883423/+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 1875317] Re: Unable to launch the application by its desktop icon copied from Applications menu
Hmm, works for me even without "4.2. Make icon executable" step. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1875317 Title: Unable to launch the application by its desktop icon copied from Applications menu Status in gnome-flashback package in Ubuntu: New Status in gnome-panel package in Ubuntu: New Status in ubuntu-meta package in Ubuntu: New Bug description: Steps to reproduce: 1. Install GNOME FlashBack, login to it 2. Open Applications menu 3. Drag some icon from Applications menu to the desktop 4.1. Do mouse double click on just copied icon 4.2. Make icon executable 4.3. Do mouse double click on just copied icon again Expected results: * user is able to run application by clicking on its desktop-file Actual results: * user is unable to run application by clicking on its desktop-file, the text editor is opened instead ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-desktop 1.450 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME-Flashback:GNOME Date: Mon Apr 27 12:16:04 2020 InstallationDate: Installed on 2020-04-24 (2 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-meta UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-flashback/+bug/1875317/+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 1875317] Re: Unable to launch the application by its desktop icon copied from Applications menu
Hmm, works for me even without "4.2. Make icon executable" step. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1875317 Title: Unable to launch the application by its desktop icon copied from Applications menu Status in gnome-flashback package in Ubuntu: New Status in gnome-panel package in Ubuntu: New Status in ubuntu-meta package in Ubuntu: New Bug description: Steps to reproduce: 1. Install GNOME FlashBack, login to it 2. Open Applications menu 3. Drag some icon from Applications menu to the desktop 4.1. Do mouse double click on just copied icon 4.2. Make icon executable 4.3. Do mouse double click on just copied icon again Expected results: * user is able to run application by clicking on its desktop-file Actual results: * user is unable to run application by clicking on its desktop-file, the text editor is opened instead ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-desktop 1.450 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME-Flashback:GNOME Date: Mon Apr 27 12:16:04 2020 InstallationDate: Installed on 2020-04-24 (2 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-meta UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-flashback/+bug/1875317/+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 430203] Re: bell.ogg is unresponsive (outside HIG response times) [regression]
** Changed in: metacity (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/430203 Title: bell.ogg is unresponsive (outside HIG response times) [regression] Status in Metacity: Fix Released Status in metacity package in Ubuntu: Fix Released Status in ubuntu-sounds package in Ubuntu: Fix Released Status in metacity package in Fedora: Fix Released Bug description: Binary package hint: ubuntu-sounds The instantaneous beep in the default Ubuntu 9.10 preview install has been switched to a slow firing, and slow to repeat sound: /usr/share/sounds/ubuntu/stereo/bell.ogg the easiest way to cause this sound to be played in anger is to open a Terminal (eg. gnome-terminal) and hit the backspace. There is an audible delay in the latency until the sound is played and approximately 1 second until the sound is replayed (despite the key repeat likely firing at over 25 Hz. Viewing the Vorbis file with ogginfo and mhWavedit shows that it is is approximately 900 milliseconds in length! $ ogginfo /usr/share/sounds/ubuntu/stereo/bell.ogg | grep Playback Playback length: 0m:00.882s The file consists of ~50 milliseconds of silence, ~200 milliseconds of actual sound and then a further ~650 milliseconds of silence. Ideally the white space should be trimmed to the *absolute maximum*. The sound needs to play *immediately* to meet the requirements set of the HIG for interactive feedback (100 millisecond upper bound). If further delays are being introduced by the Vorbis loading then this sound (which should be immediate and responsive) should probably be converted to an uncompressed format. Failing that, the sound could be reverted to the previous short and quick 'bip' sound used previously. To manage notifications about this bug go to: https://bugs.launchpad.net/metacity/+bug/430203/+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 486154] Re: System beep broken in Karmic despite heroic efforts to fix it
Wontfix. ** Changed in: metacity (Ubuntu) Status: Triaged => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libcanberra in Ubuntu. https://bugs.launchpad.net/bugs/486154 Title: System beep broken in Karmic despite heroic efforts to fix it Status in Metacity: New Status in libcanberra package in Ubuntu: Invalid Status in linux-lts-xenial package in Ubuntu: Confirmed Status in metacity package in Ubuntu: Invalid Status in pulseaudio package in Ubuntu: Invalid Bug description: Between Jaunty and Karmic, a number of changes were made to keep the PC speaker from beeping. As part of this, system bell events are now captured by metacity, which uses libcanberra to play a sound. For users without speakers, this fails to be useful. The current setup makes restoring the old behavior extremely difficult. The absolute show stopper is that metacity traps audible system bell events. This behavior is, as best we can tell, not configurable. The attached patch keeps metacity from capturing system bell events. It also removes the sound playback capability. As Lucid will be using pulse audio's module-x11-bell to play sounds for system bell events, it is not necessary for this capability to be in metacity. Additionally, this removes the discrepancy between metacity's and compiz's handling of system bell events. There are several other difficulties in enabling the system bell: 1) Even if it is taken out of the blacklist, the pcspkr module may not load properly. Another modprobe may be necessary to get it loaded. See bug #398161. 2) Something in Gnome's startup does the equivalent of `xset b off`, so `xset b on` must be run on every login. (Note that bug #280767 keeps you from setting the bell volume with xset.) 3) A number of settings in gnome-terminal and gconf may keep the shell from sounding system bell events. Comments #28, #34, and #50 give more detailed summaries of the various problems. To manage notifications about this bug go to: https://bugs.launchpad.net/metacity/+bug/486154/+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 971051] Re: No Alt+Tab in gnome classic session (switcher plugin not loaded)
** Changed in: ubuntu-gnome-flashback Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/971051 Title: No Alt+Tab in gnome classic session (switcher plugin not loaded) Status in Compiz: Invalid Status in Ubuntu GNOME Flashback: Invalid Status in compiz package in Ubuntu: Fix Released Status in gnome-session package in Ubuntu: Invalid Status in Baltix: New Bug description: When using the Gnome Classic session (with Compiz) in Ubuntu Precise Pangolin, I cannot use alt + tab to switch applications. WORKAROUND: 1. Install packages: sudo apt-get install compiz-plugins compizconfig-settings-manager 2. Run "ccsm" 3. Scroll down to Window Management and enable (tick) "Application Switcher". ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: gnome-panel 1:3.4.0-0ubuntu1 Uname: Linux 3.3.0-030300-generic x86_64 ApportVersion: 2.0-0ubuntu2 Architecture: amd64 Date: Sun Apr 1 21:01:11 2012 InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20120108) ProcEnviron: LANGUAGE=en_GB:en TERM=xterm LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: gnome-panel UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/971051/+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 238335] Re: Too many obsolete panel directories in ~/.gconf/apps
** Changed in: gnome-panel (Ubuntu) Status: Triaged => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gconf in Ubuntu. https://bugs.launchpad.net/bugs/238335 Title: Too many obsolete panel directories in ~/.gconf/apps Status in GNOME Panel: Fix Released Status in gconf package in Ubuntu: Invalid Status in gconf-editor package in Ubuntu: Invalid Status in gnome-panel package in Ubuntu: Invalid Bug description: Binary package hint: gnome-panel Old (obsolete) gnome panel entries in gconf-editor never get deleted. If a user has more than the original two panels at one time, then decides to delete a few of them (say they had 5 customized panels, and bringing it down to 1), the system warns the user that all the settings will be lost. Which is what they want. But all the deleted panel entries are still located in /apps/panel/toplevels. Furthermore, opening ~/.gconf/apps/panel will list all those previous entries. They're not loaded when the user starts gnome, but they are nonetheless present in that location. This situation can get a little overwhelming when a user is used to deleting panels and creating new ones frequently (since that's easier than to remove every single item on the panel individually). For example, I currently have 15 different toplevels which settings I can change in gconf-editor, although i only have 2 panels total on my desktop (panels 5 and 15). All the others, 1-4 + 6 - 14 are obsolete. Every time I massively delete/add new panels, I find myself having to hunt down the toplevels listings and playing with the settings to see which panels are the ones I actually have available. This turn, I only had to do this 15 times... What will I do when the number of entries get to 50? 100? 150? This situation is just one major headache waiting to happen. NOTE: Let me clarify, saying that I _never_ had 15 panels at once at any one time on my desktop. Old and obsolete panel entries are not overwritten by new ones, which would curb the growth time of the problem at the very least; they are still there, taking up space, and new ones need to be created. I'll end this with a question: At the beginning, notice that i said that the system warns you that all your settings for whichever panel you are trying to delete will be lost/removed. That prompt makes the user falsely assume that the panel entries are indeed deleted. If so, why are they still in ~/.gconf/apps/panel ? To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-panel/+bug/238335/+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 58977] Re: Maximizing ignores docked panles with Xinerama
** Changed in: compiz (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/58977 Title: Maximizing ignores docked panles with Xinerama Status in Metacity: Fix Released Status in compiz package in Ubuntu: Fix Released Status in kdebase-workspace package in Ubuntu: Invalid Status in metacity package in Ubuntu: Fix Released Status in metacity package in Debian: Fix Released Bug description: Binary package hint: metacity Hi When I add another screen using Xinerama, the gnome panels remain in the first screen, which is great, but when the panel is aligned vertically near the border between the two screens (either on the right of the left screen, or on the left of the right screen), maximizing a window ignores the panel, and the window is maximized right to the edge of the screen. Steps to reproduce: 1. Use xinerama with the second screen to the right of the first. 2. Add a vertical gnome panel to the right edge of the left screen. 3. maximize a window in the left screen. 4. The screen is maximized right to the edge of the screen, instead of the edge of the panel. To manage notifications about this bug go to: https://bugs.launchpad.net/metacity/+bug/58977/+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 369064] Re: Maximized apps go under the bottom bar when using vertically stacked screens
** Changed in: metacity (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/369064 Title: Maximized apps go under the bottom bar when using vertically stacked screens Status in metacity package in Ubuntu: Fix Released Bug description: Binary package hint: metacity When using vertically stacked screens, maximized windows on the main screen have their status bar or lower portion of the window hidden underneath the bottom bar. ProblemType: Bug Architecture: i386 DistroRelease: Ubuntu 9.04 Package: metacity 1:2.25.144-0ubuntu2 ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: metacity Uname: Linux 2.6.28-11-generic i686 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/369064/+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 45706] Re: Resizing improvement request
** Changed in: metacity (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/45706 Title: Resizing improvement request Status in metacity package in Ubuntu: Invalid Bug description: When I watch TV, I would love to be able to resize the window while keeping the aspect ratio constant. I gathered that metacity does already handle thie feature. However I understand that it must be handled by the application. But I watch TV using the programs "tvtime" or "xawtv", both of which are not gnome programs so can't assume that they are being used with metacity. So it would be great if it could be possible for the user, not the program, to control the aspect ratio. I dunno, for example, if I hold the "control" key while resizing the window, make metacity lock the aspect ratio, or add some option in the window menu (top left corner) or something... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/45706/+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 395116] Re: Pidgin massive synchronization notifications halt metacity
** Changed in: metacity (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/395116 Title: Pidgin massive synchronization notifications halt metacity Status in Pidgin: New Status in metacity package in Ubuntu: Invalid Bug description: Binary package hint: metacity How to reproduce the bug: 2 computers ( one with ubuntu using metacity - 1 MSN account ) - Add on MSN account as many contacts as you can. Probably 200-300 contacts. This account is set up in Pidgin and works perfectly on one computer. The contacts are stored on the local contact list and the server as well. - Disable the account on the first computer, and log in via Pidgin on another computer. The system should retrieve contacts from the server and add them to the local list. - While logged in, on the second computer, delete all the contacts of the specific account. Log out. - Go back to the first computer and log in. Now Pidgin will pop up one synchronization notification for every contact that is on the local contact list of the first computer, but not on the server; asking whether the contacts on the local contact file should be sent back to the server. - The user has to click YES or NO for every single window. There is no option for massive accepting or refusal. - After 25 or so notification pop ups at the same time (the user has no opportunity to click so fast, so that's going to happen for sure), the graphical environment will stop responding. - Problem can be solved temporarily by logging into the console and killing pidgin - Problem can be solved permanently when deleting the local contact database, so that Pidgin doesn't worry about the contacts syncing (or might there also be an option in Pidgin preferences, no idea) ProblemType: Bug Architecture: i386 DistroRelease: Ubuntu 8.10 ExecutablePath: /usr/bin/pidgin Package: pidgin 1:2.5.7-1ubuntu1~pidgin3.8.10 ProcEnviron: PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: pidgin Uname: Linux 2.6.27-14-generic i686 UnreportableReason: This is not a genuine Ubuntu package To manage notifications about this bug go to: https://bugs.launchpad.net/pidgin/+bug/395116/+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 467972] Re: metacity assert failure: metacity:ERROR:core/bell.c:211:bell_flash_window_frame: assertion failed: (window->frame != NULL)
** Changed in: metacity (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/467972 Title: metacity assert failure: metacity:ERROR:core/bell.c:211:bell_flash_window_frame: assertion failed: (window->frame != NULL) Status in Metacity: Fix Released Status in metacity package in Ubuntu: Fix Released Bug description: Binary package hint: metacity I don't know what happened. It just crashed. I was using Chrome when it happened and I just upgraded to Karmic today. ProblemType: Crash Architecture: i386 AssertionMessage: metacity:ERROR:core/bell.c:211:bell_flash_window_frame: assertion failed: (window->frame != NULL) Date: Sun Nov 1 11:45:57 2009 DistroRelease: Ubuntu 9.10 ExecutablePath: /usr/bin/metacity Package: metacity 1:2.28.0-0ubuntu1 ProcCmdline: metacity ProcEnviron: LANGUAGE=en_US.UTF-8 LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-14.48-generic Signal: 6 SourcePackage: metacity StacktraceTop: __kernel_vsyscall () raise () from /lib/tls/i686/cmov/libc.so.6 abort () from /lib/tls/i686/cmov/libc.so.6 g_assertion_message () from /lib/libglib-2.0.so.0 g_assertion_message_expr () from /lib/libglib-2.0.so.0 Title: metacity assert failure: metacity:ERROR:core/bell.c:211:bell_flash_window_frame: assertion failed: (window->frame != NULL) Uname: Linux 2.6.31-14-generic i686 UserGroups: adm admin audio cdrom dialout dip fax floppy fuse lpadmin netdev plugdev powerdev sambashare scanner tape video XsessionErrors: (gnome-settings-daemon:3172): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed (nautilus:3192): Eel-CRITICAL **: eel_preferences_get_boolean: assertion `preferences_is_initialized ()' failed (polkit-gnome-authentication-agent-1:3195): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed (gnome-panel:3206): Gdk-WARNING **: /build/buildd/gtk+2.0-2.18.3/gdk/x11/gdkdrawable-x11.c:952 drawable is not a pixmap or window (chrome:3337): Gdk-WARNING **: XID collision, trouble ahead To manage notifications about this bug go to: https://bugs.launchpad.net/metacity/+bug/467972/+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 892589] Re: attaching an external monitor to a laptop makes the image bad
** Changed in: metacity (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/892589 Title: attaching an external monitor to a laptop makes the image bad Status in metacity package in Ubuntu: Invalid Bug description: If you attach an external monitor to a laptop while Ubuntu is running, always makes the image of the screen look bad on both the internal and the external monitor. I have two command attached to keyboard shortcuts which sometimes can make the computer usable again, if you switch back and forth between the internal and external monitor with: xrandr --output LVDS1 --off --output VGA1 --auto #switch on the internal monitor, external off xrandr --output LVDS1 --auto --output VGA1 --off #external on, internal off The success seem to depend on what programs are running at the moment of running those commands. If you only have a terminal opened it goes fine, but with Libreoffice and Firefox you need to restart Ubuntu. Attached are three screenshots which all show the screen looks like when the external monitor is attached. Ubuntu 11.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/892589/+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 533758] Re: Button order/position should be part of Theme
** Changed in: metacity (Ubuntu) Status: Triaged => Invalid ** No longer affects: metacity -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/533758 Title: Button order/position should be part of Theme Status in metacity package in Ubuntu: Invalid Bug description: Binary package hint: metacity Given the change of default button layout in Lucid, I feel that this should be part of theme rather a part of a separate gconf entity. (I realise that might be a contentious request - but note I'm not asking to undo the new default button layout, just to associate it with the new themes rather than laying it down whatever theme people have). I'm referencing this from https://bugs.launchpad.net/ubuntu/+source /gnome-control-center/+bug/532754 which is the fact that the appearance dialog doesn't match the new reality. Dave To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/533758/+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 968011] Re: window title font can't be scaled in precise (03-28)
** Changed in: metacity (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/968011 Title: window title font can't be scaled in precise (03-28) Status in light-themes: Invalid Status in metacity package in Ubuntu: Invalid Bug description: window title font will remain absolute size no matter I scale up or down using Gnome-tweak-tool or universal access from system settings this happens in 12.04 64-bit daily from yesterday To manage notifications about this bug go to: https://bugs.launchpad.net/light-themes/+bug/968011/+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 1024802] Re: metacity crashed with SIGABRT in XFlush()
** Changed in: metacity (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/1024802 Title: metacity crashed with SIGABRT in XFlush() Status in metacity package in Ubuntu: Invalid Bug description: metacity crashed. ProblemType: Crash DistroRelease: Ubuntu 12.10 Package: metacity 1:2.34.1-1ubuntu11 ProcVersionSignature: Ubuntu 3.5.0-4.4-generic 3.5.0-rc6 Uname: Linux 3.5.0-4-generic i686 ApportVersion: 2.3-0ubuntu4 Architecture: i386 Date: Sat Jul 14 23:03:59 2012 ExecutablePath: /usr/bin/metacity InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 (20120423) ProcCmdline: metacity ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash Signal: 6 SourcePackage: metacity StacktraceTop: ?? () from /usr/lib/i386-linux-gnu/libX11.so.6 ?? () from /usr/lib/i386-linux-gnu/libX11.so.6 _XEventsQueued () from /usr/lib/i386-linux-gnu/libX11.so.6 _XFlush () from /usr/lib/i386-linux-gnu/libX11.so.6 XFlush () from /usr/lib/i386-linux-gnu/libX11.so.6 Title: metacity crashed with SIGABRT in _XEventsQueued() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/1024802/+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 957276] Re: metacity crashed with SIGABRT in XSync()
** Changed in: metacity (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/957276 Title: metacity crashed with SIGABRT in XSync() Status in metacity package in Ubuntu: Invalid Bug description: I was playing around with Remmina's windowed mode, trying to move the window around, when I got this crash. This is the first time this has happened, and I am unable to reproduce it. ProblemType: Crash DistroRelease: Ubuntu 12.04 Package: metacity 1:2.34.1-1ubuntu8 ProcVersionSignature: Ubuntu 3.2.0-18.29-generic 3.2.9 Uname: Linux 3.2.0-18-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 1.94.1-0ubuntu2 Architecture: amd64 Date: Fri Mar 16 14:06:55 2012 ExecutablePath: /usr/bin/metacity InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120301) ProcCmdline: metacity ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash Signal: 6 SourcePackage: metacity StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6 _XReply () from /usr/lib/x86_64-linux-gnu/libX11.so.6 XSync () from /usr/lib/x86_64-linux-gnu/libX11.so.6 ?? () Title: metacity crashed with SIGABRT in _XReply() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/957276/+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 1033417] Re: all window manager shortcuts (e.g. Alt-F4) broken in Unity
** Changed in: metacity (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/1033417 Title: all window manager shortcuts (e.g. Alt-F4) broken in Unity Status in metacity package in Ubuntu: Invalid Bug description: Since about a week, all window manager shortcuts are broken, that is: pressing them does nothing. This affects most prominently Alt-F4 and Alt-Tab. The panel's shortcuts, like Alt, Super and Super+Number, are still working, as are shortcuts inside applications (and every other keyboard input). xev tells me that all input events for Alt-F4 are sent to the client window. This system is a virtual machine in VirtualBox under a 64-bit Windows 7 host; guest additions are installed. The system is used for web development; my typical session contains Firefox, Konsole (from KDE), Pidgin and pgAdmin III. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: metacity 1:2.34.1-1ubuntu11 ProcVersionSignature: Ubuntu 3.2.0-27.43-generic 3.2.21 Uname: Linux 3.2.0-27-generic x86_64 ApportVersion: 2.0.1-0ubuntu11 Architecture: amd64 Date: Mon Aug 6 08:59:53 2012 InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) ProcEnviron: LANGUAGE= TERM=xterm-256color PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/zsh SourcePackage: metacity UpgradeStatus: Upgraded to precise on 2012-06-05 (61 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/1033417/+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 1061032] Re: ref_count == 0, but source was still attached to a context
** Changed in: metacity (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/1061032 Title: ref_count == 0, but source was still attached to a context Status in metacity package in Ubuntu: Invalid Bug description: Startng a user sesson desktop as "Gnome Sesson Classicc (Without effects)" I change to compiz and after to metacity. Then a error message is showed from glib: $ compiz --replace & [1] 2880 $ compiz (core) - Info: Loading plugin: core compiz (core) - Info: Starting plugin: core compiz (core) - Info: Loading plugin: ccp compiz (core) - Info: Starting plugin: ccp compizconfig - Info: Backend : ini compizconfig - Info: Integration : true compizconfig - Info: Profile : default $ metacity --replace & [2] 2883 $ compiz (core) - Info: Stopping plugin: ccp compiz (core) - Info: Unloading plugin: ccp compiz (core) - Info: Stopping plugin: core compiz (core) - Info: Unloading plugin: core (process:2880): GLib-WARNING **: /build/buildd/glib2.0-2.34.0/./glib/gmain.c:1817: ref_count == 0, but source was still attached to a context! ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: metacity 1:2.34.8-0ubuntu4 ProcVersionSignature: Ubuntu 3.5.0-16.25-generic 3.5.4 Uname: Linux 3.5.0-16-generic i686 ApportVersion: 2.6.1-0ubuntu1 Architecture: i386 Date: Wed Oct 3 17:31:54 2012 InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha i386 (20091126) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=es_ES.UTF-8 SHELL=/bin/bash SourcePackage: metacity UpgradeStatus: Upgraded to quantal on 2012-04-26 (160 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/1061032/+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 924909] Re: Windows have grey traces in Ubiquity
** Changed in: metacity (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/924909 Title: Windows have grey traces in Ubiquity Status in metacity package in Ubuntu: Invalid Status in openbox package in Ubuntu: Fix Released Status in xfwm4 package in Ubuntu: Fix Released Bug description: I'm testing Xubuntu amd64 Precise alpha2 in live mode. When I get the screen to choose if I want to try it without any change or to install it, the background is black. Moving the window, it became grey "following the window". Sorry for this very bad report, I hope it's understandable. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: casper 1.302 ProcVersionSignature: Ubuntu 3.2.0-12.21-generic 3.2.2 Uname: Linux 3.2.0-12-generic x86_64 ApportVersion: 1.91-0ubuntu1 Architecture: amd64 CasperVersion: 1.302 Date: Wed Feb 1 14:47:54 2012 LiveMediaBuild: Xubuntu 12.04 "Precise Pangolin" - Alpha amd64 (20120201) ProcEnviron: PATH=(custom, no user) LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: casper UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.casper.conf: 2012-02-01T15:42:30 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/924909/+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 497031] Re: Auto maximize windows when dragging mouse cursor to the top of the screen
** Changed in: metacity (Ubuntu) Status: Triaged => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/497031 Title: Auto maximize windows when dragging mouse cursor to the top of the screen Status in Metacity: Expired Status in metacity package in Ubuntu: Invalid Bug description: Binary package hint: metacity Dragging a window to the top of the screen not always maximize the window. ProblemType: Bug Architecture: amd64 Date: Tue Dec 15 13:19:38 2009 DistroRelease: Ubuntu 9.10 ExecutablePath: /usr/bin/metacity Package: metacity 1:2.28.0-0ubuntu1 ProcEnviron: SHELL=/bin/bash LANG=es_AR.UTF-8 ProcVersionSignature: Ubuntu 2.6.31-16.53-generic SourcePackage: metacity Uname: Linux 2.6.31-16-generic x86_64 XsessionErrors: (gnome-settings-daemon:1949): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed (gnome-settings-daemon:1949): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed (polkit-gnome-authentication-agent-1:1994): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed (nautilus:1989): Eel-CRITICAL **: eel_preferences_get_boolean: assertion `preferences_is_initialized ()' failed To manage notifications about this bug go to: https://bugs.launchpad.net/metacity/+bug/497031/+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 1216292] Re: top program bar does not work with lenovo touchpad -- regression
"Package: metacity (not installed)", so not a bug in metacity. Ubuntu 13.10 is End Of Life. ** Changed in: metacity (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/1216292 Title: top program bar does not work with lenovo touchpad -- regression Status in metacity package in Ubuntu: Invalid Bug description: So I woke up this morning (24-Aug-13) and my synaptic touchpad works to move the mouse but the buttons do not work on metacity components such as those three little circles in the upper left, nor to re-position the box, nor the side sliders. Keystroke commands work fine, as does my Lenovo touch screen. But the buttons to my synaptics touch pad seem to be non-operational. So I blamed metacity, because it wasn't recognizing the input from my touchpad buttons. The problem could also, of course, be with the drivers somehow. Funny, that little red button in the middle of my Lenovo typepad doesn't seem to work at all, but I usually don't use it so I'm not sure if the issues are connected. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: metacity (not installed) ProcVersionSignature: Ubuntu 3.11.0-3.8-generic 3.11.0-rc6 Uname: Linux 3.11.0-3-generic x86_64 ApportVersion: 2.12.1-0ubuntu2 Architecture: amd64 Date: Sat Aug 24 07:06:54 2013 InstallationDate: Installed on 2013-08-12 (12 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130811) MarkForUpload: True SourcePackage: metacity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/1216292/+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 894493] Re: After I use Xine Unity 2d panel become invisible
** Changed in: metacity (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/894493 Title: After I use Xine Unity 2d panel become invisible Status in Metacity: Expired Status in unity-2d: Invalid Status in metacity package in Ubuntu: Invalid Status in unity-2d package in Ubuntu: Invalid Bug description: After I use Xine in Unity 2d , Unity 2d panel and menu bar become invisible. OnClick, OnMouseOver is work. To manage notifications about this bug go to: https://bugs.launchpad.net/metacity/+bug/894493/+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 437139] Re: metacity assert failure: metacity:ERROR:core/boxes.c:1161:meta_rectangle_edge_aligns: code should not be reached
** Changed in: metacity (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/437139 Title: metacity assert failure: metacity:ERROR:core/boxes.c:1161:meta_rectangle_edge_aligns: code should not be reached Status in Metacity: Fix Released Status in metacity package in Ubuntu: Fix Released Status in metacity source package in Precise: Invalid Status in metacity package in Debian: Fix Released Bug description: Binary package hint: metacity I think this is a new bug ProblemType: Crash Architecture: i386 AssertionMessage: metacity:ERROR:core/boxes.c:1161:meta_rectangle_edge_aligns: code should not be reached Date: Sat Sep 26 13:13:02 2009 DistroRelease: Ubuntu 9.10 ExecutablePath: /usr/bin/metacity Package: metacity 1:2.28.0-0ubuntu1 ProcCmdline: /usr/bin/metacity --replace ProcEnviron: LANG=it_IT.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-11.36-generic Signal: 6 SourcePackage: metacity StacktraceTop: __kernel_vsyscall () raise () from /lib/tls/i686/cmov/libc.so.6 abort () from /lib/tls/i686/cmov/libc.so.6 g_assertion_message () from /lib/libglib-2.0.so.0 ?? () Title: metacity assert failure: metacity:ERROR:core/boxes.c:1161:meta_rectangle_edge_aligns: code should not be reached Uname: Linux 2.6.31-11-generic i686 UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare To manage notifications about this bug go to: https://bugs.launchpad.net/metacity/+bug/437139/+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 1736449] Re: package libmetacity-private3a:amd64 1:3.18.7-0ubuntu0.3 failed to install/upgrade: Abhängigkeitsprobleme - verbleibt unkonfiguriert
** Changed in: metacity (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/1736449 Title: package libmetacity-private3a:amd64 1:3.18.7-0ubuntu0.3 failed to install/upgrade: Abhängigkeitsprobleme - verbleibt unkonfiguriert Status in metacity package in Ubuntu: Invalid Bug description: The bug frequently occurs during updates. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libmetacity-private3a:amd64 1:3.18.7-0ubuntu0.3 ProcVersionSignature: Ubuntu 4.4.0-101.124-generic 4.4.95 Uname: Linux 4.4.0-101-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.13 Architecture: amd64 Date: Tue Dec 5 15:44:07 2017 ErrorMessage: Abhängigkeitsprobleme - verbleibt unkonfiguriert InstallationDate: Installed on 2016-07-21 (502 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1.3 apt 1.2.24 SourcePackage: metacity Title: package libmetacity-private3a:amd64 1:3.18.7-0ubuntu0.3 failed to install/upgrade: Abhängigkeitsprobleme - verbleibt unkonfiguriert UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/1736449/+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 894487] Re: Gnome-panel won't redraw under tooltip
** Changed in: metacity (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/894487 Title: Gnome-panel won't redraw under tooltip Status in metacity package in Ubuntu: Invalid Bug description: When using metacity if I place a nautilus window under gnome-panel in the bottom, and I move my mouse on a shortcut to have a tool-tip over gnome-panel, when I move the mouse to another shortcut, the area where the tool-tip was on gnome-panel is incorrectly redrawn with the content under gnome-panel. This behaviour is only reproducible with metacity, using compiz doesn't have the same issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/894487/+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 971322] Re: Unity-2D/metacity window placement/move problems in precise
** Changed in: metacity (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/971322 Title: Unity-2D/metacity window placement/move problems in precise Status in metacity package in Ubuntu: Invalid Bug description: I've upgraded oneiric to precise (32 bit). One annoying problem is the window placement/moving policy now. In oneiric this worked (I am using Unity-2D, so metacity, composing manager/effects are enabled) very well. If I open a new window, it will be placed "stacked" on existing window (eg if I open a new terminal (usually I have to open more of them), even if there is lots of "free" space on the workspace. So, I think metacity in oneiric tries to use available 'free' screen space, which is not true for oneiric. Another annoying thing is the window border "resistance". In oneiric, if I move a window, there is need for a little "push more" action to be able to move window when border is at another window's border. It's a great help to align windows in a nice way. In precise, this does not work, or at least it behaves oddly: if I move a window towards another horizontally this _is_ this effect, however not at the border but _before_ it! There is a huge space, probably the same size as the Unity launcher bar, is it possible, that positions are miscalculated? I am using "auto hide" for Unity. There is similar problem vertically however the "gap" is smaller, and I have no idea if there is some relation of the size of the gap and any other thing. It's about half of the height of the top panel, for example. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: metacity 1:2.34.1-1ubuntu9 ProcVersionSignature: Ubuntu 3.2.0-21.34-generic-pae 3.2.13 Uname: Linux 3.2.0-21-generic-pae i686 ApportVersion: 2.0-0ubuntu2 Architecture: i386 Date: Mon Apr 2 09:05:42 2012 InstallationMedia: Ubuntu-Server 10.04.1 LTS "Lucid Lynx" - Release i386 (20100816.2) SourcePackage: metacity UpgradeStatus: Upgraded to precise on 2012-03-01 (31 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/971322/+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 985449] Re: unity-2d launcher behind a full screen window
** Changed in: metacity (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/985449 Title: unity-2d launcher behind a full screen window Status in metacity package in Ubuntu: Invalid Bug description: Not exactly a show-stopper bug ... I have a terminal window, not maximazed, but full screen. I'm using Unity-2D+metacity, with composite support is switched on. The terminal window is semi- transparent. Now, if I move the mouse to the left side of the screen, I can see (through the semi transparent window) that Unity-2D's launcher is shown (it's configured for auto-hide). I guess it's a problem, since in case of a full screen window, I wouldn't except that anything other is activated if I move the mouse through the screen, as the screen is filled with a full screen window, so no other thing should be involved. The only problem I have with this: if I switch workspace then, unity-2d's launcher is still shown, so I have to move the mouse pointer on it, and then remove so it can be hidden, which is a bit annoying to do all the time, as I would like auto-hide ... Maybe it's not a metacity but an unity-2d problem? ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: metacity 1:2.34.1-1ubuntu11 ProcVersionSignature: Ubuntu 3.2.0-23.36-generic-pae 3.2.14 Uname: Linux 3.2.0-23-generic-pae i686 ApportVersion: 2.0.1-0ubuntu5 Architecture: i386 Date: Thu Apr 19 09:34:33 2012 InstallationMedia: Ubuntu-Server 10.04.1 LTS "Lucid Lynx" - Release i386 (20100816.2) SourcePackage: metacity UpgradeStatus: Upgraded to precise on 2012-03-01 (48 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/985449/+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 949191] Re: Maximize button-tooltips doesn't disappear after clicked
** Changed in: metacity (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to metacity in Ubuntu.
https://bugs.launchpad.net/bugs/949191
Title:
Maximize button-tooltips doesn't disappear after clicked
Status in metacity package in Ubuntu:
Invalid
Bug description:
Hi,
when I move the mouse pointer to a window's 'maximize' button, and
waiting for the tooltip ("Maximize window") show, a "Close window"
tooltip gets up after I clicked on the 'maximize' button immediately,
and I can't remove it from the screen anymore.
The only way to remove it, I need to size back the window, and move
the pointer again to the buttons to show up a tooltip again.
Configuration:
Ubuntu 12.04 beta 1
Intel® Core 2 Duo E4500
Intel® G965 / ICH8 Chipset
Intel® GMA X3000
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: metacity 1:2.34.1-1ubuntu7
ProcVersionSignature: Ubuntu 3.2.0-18.28-generic-pae 3.2.9
Uname: Linux 3.2.0-18-generic-pae i686
ApportVersion: 1.94-0ubuntu2
Architecture: i386
Date: Wed Mar 7 18:02:40 2012
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta i386 (20120301)
ProcEnviron:
TERM=xterm
LANG=hu_HU.UTF-8
SHELL=/bin/bash
SourcePackage: metacity
UpgradeStatus: Upgraded to precise on 2012-03-07 (0 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/949191/+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 733431] Re: Windows lack borders: visually unpleasant and leaves only one option to resize
** Changed in: metacity (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to metacity in Ubuntu.
https://bugs.launchpad.net/bugs/733431
Title:
Windows lack borders: visually unpleasant and leaves only one option
to resize
Status in Ayatana Design:
Invalid
Status in light-themes:
Fix Released
Status in Unity:
Invalid
Status in unity-2d:
Invalid
Status in metacity package in Ubuntu:
Invalid
Bug description:
The latest change in light-themes (bug #733233) to drop the window
borders lowers the visual quality and the usability of the desktop for
Metacity users. Unity 2D users are all affected as well as Classic
desktop users with 'No Effects'.
Visually there is no frontier any more between application which just
looks odd. I do not know of any other OS that does that. The main
difference with Compiz is that Metacity does not have shadows.
Usability wise, the border was also use has a handle (probably too
thin) to let the user resize the window. Without that border the user
can only resize the window using the bottom right handle.
Proposal to re-apply zero-pixel borders:
Bug #740579 ("Wishlist: move to 0px borders now that Unity and
Unity-2D/Metacity can cope")
To manage notifications about this bug go to:
https://bugs.launchpad.net/ayatana-design/+bug/733431/+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 1495733] Re: /usr/bin/metacity:6:g_assertion_message:g_assertion_message_expr:meta_rectangle_edge_aligns:apply_edge_resistance:apply_edge_resistance_to_each_side
** Changed in: metacity (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/1495733 Title: /usr/bin/metacity:6:g_assertion_message:g_assertion_message_expr:meta_rectangle_edge_aligns:apply_edge_resistance:apply_edge_resistance_to_each_side Status in metacity package in Ubuntu: Invalid Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding metacity. This problem was most recently seen with version 1:3.14.3-1ubuntu7, the problem page at https://errors.ubuntu.com/problem/402541de22135316e7f1ce394346da0d4f716d2f contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/1495733/+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 1160843] Re: Top panel is not active, does not show date or allow access to System Settings
** Changed in: metacity (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/1160843 Title: Top panel is not active, does not show date or allow access to System Settings Status in metacity package in Ubuntu: Invalid Bug description: This is a regression. After updates of Tues 27 Mar 2013, the date vanished from the top panel and some of the icons lost functions. For instance, it is no longer possible to access System Settings that way. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: metacity 1:2.34.13-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-14.9-lowlatency 3.8.4 Uname: Linux 3.8.0-14-lowlatency x86_64 ApportVersion: 2.9.2-0ubuntu5 Architecture: amd64 Date: Wed Mar 27 07:02:05 2013 InstallationDate: Installed on 2013-01-04 (81 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130102) MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: metacity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/1160843/+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 1636620] Re: no wallpaper when compositing manager disabled
This is not metacity bug and 16.10 has reached End of Life long time ago. ** Changed in: metacity (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/1636620 Title: no wallpaper when compositing manager disabled Status in metacity package in Ubuntu: Invalid Bug description: When compositing-manager is disabled for metacity, no wallpaper is shown. Ubuntu version: 16.10 (yakkety) metacity version: 1:3.20.3-1ubuntu2 Steps to reproduce: - open dconf-editor and set org.gnome.metacity.compositing-manager to false Expected result: - window shadows disappear, but otherwise no visible changes Actual result: - wallpaper disappears as well, desktop becomes solid black (note that the desktop is still functional, icons are shown normally; it's just the wallpaper that's missing) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/1636620/+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 1860175] Re: Ability to rearrange applet icons by drag/drop.
** Package changed: gnome-applets (Ubuntu) => gnome-shell (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1860175 Title: Ability to rearrange applet icons by drag/drop. Status in gnome-shell package in Ubuntu: New Bug description: 1) Ubuntu 19.10 2) Gnome 3.34.1 3) Ability to drag/drop applet icons to different places on the top bar. 4) Unable to drag/drop applet icons. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1860175/+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 1780468] Re: Blurry titlebar font when window is not maximized
Can you test https://gitlab.gnome.org/GNOME/metacity/commit/ef433bd7dec58cc9f062e0cda57cb259ff3745f1? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/1780468 Title: Blurry titlebar font when window is not maximized Status in metacity package in Ubuntu: New Bug description: What happens I've configured Compiz window manager to use gtk-window-decorator so that it may apply my Metacity theme for the titlebars. With this decorator, I've noticed that Compiz renders slightly blurry titlebar fonts when a window is not maximized. Once the window is maximized, sharp fonts are rendered. When a window is not maximized, the font seems to lack sub-pixel hinting or anti-aliasing, hence the slightly blurry appearance. I zoomed in on the font when the window was maximized and observed bluish lines around the characters. When a window was not maximized, the zoomed-in characters didn't have the bluish lines. I've tested and seen that the Marco window manager and the Emerald decorator (used with Compiz) both render sharp titlebar fonts regardless of whether a window is maximized or not. The image in the below link shows the slight difference in font rendering when Compiz is used with gtk-window-decorator. Firefox's window was maximized, with sharp text, while VLC's window was not maximized, with slightly blurry text. https://i.stack.imgur.com/5BalZ.png Upon switching to Marco window manager, both texts are sharp. https://i.stack.imgur.com/9Gzli.png When the "Compiz with gtk-window-decorator" setup is zoomed-in, blue lines around the maximized Firefox window titlebar text are visible (it looks like sub-pixel rendering to me). The blue lines are completely lacking in the un-maximized VLC window titlebar text. https://i.stack.imgur.com/XDSAU.png What I expect to happen --- The titlebar font rendering should be sharp for both maximized and un-maximized windows. The cause (clip_to_rounded_corners) --- Upon investigating, I've discovered that Compiz's gtk-window-decorator uses the libmetacity library. The clip_to_rounded_corners() function in "meta-theme-metacity.c" is called to draw rounded corners for the un-maximized windows in my theme. It seems the call to draw rounded corners by cairo_arc() in that function somehow affects the font rendering. When windows are maximized, the drawing of rounded corners is not performed, hence the sharp font rendering. I rebuilt the libmetacity library with the clip_to_rounded_corners() call commented out and achieved sharp fonts for un-maximized windows. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: metacity 1:3.28.0-1 ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18 Uname: Linux 4.15.0-24-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: MATE Date: Fri Jul 6 19:52:03 2018 InstallationDate: Installed on 2018-05-06 (61 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: metacity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/1780468/+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 58977] Re: Maximizing ignores docked panles with Xinerama
** Changed in: compiz (Ubuntu) Status: Fix Committed => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/58977 Title: Maximizing ignores docked panles with Xinerama Status in Metacity: Confirmed Status in compiz package in Ubuntu: Confirmed Status in kdebase-workspace package in Ubuntu: Invalid Status in metacity package in Ubuntu: Triaged Status in metacity package in Debian: Confirmed Bug description: Binary package hint: metacity Hi When I add another screen using Xinerama, the gnome panels remain in the first screen, which is great, but when the panel is aligned vertically near the border between the two screens (either on the right of the left screen, or on the left of the right screen), maximizing a window ignores the panel, and the window is maximized right to the edge of the screen. Steps to reproduce: 1. Use xinerama with the second screen to the right of the first. 2. Add a vertical gnome panel to the right edge of the left screen. 3. maximize a window in the left screen. 4. The screen is maximized right to the edge of the screen, instead of the edge of the panel. To manage notifications about this bug go to: https://bugs.launchpad.net/metacity/+bug/58977/+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 1359211] Re: Mouse cursor tiny when hovering unity elements in high DPI mode
** Changed in: compiz Status: Fix Committed => Fix Released ** Changed in: unity-settings-daemon (Ubuntu Wily) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1359211 Title: Mouse cursor tiny when hovering unity elements in high DPI mode Status in Compiz: Fix Released Status in Unity: Fix Released Status in Unity 7.3 series: In Progress Status in compiz package in Ubuntu: Fix Released Status in unity package in Ubuntu: Fix Released Status in unity-settings-daemon package in Ubuntu: Fix Released Status in compiz source package in Wily: Fix Released Status in unity source package in Wily: Fix Released Status in unity-settings-daemon source package in Wily: Invalid Bug description: [Impact] On a high DPI screen (220 DPI) the mouse cursor is really tiny when hovering unity elements. There are various keys in dconf to change the cursor's scale factor or size. I've managed to change it in a way that it looks normal when inside application windows, but its still tiny when on unity elements. I think this should be set automatically by the scale factor setting in system settings. (Using unity 7.3.1+14.10.20140811-0ubuntu1) [Test Case] * Log in * Launch Firefox * Move the mouse over the panel or the launcher, then back over the Firefox window. * Cursor should always be of the same size [Regression Potential] * Mouse cursors might appear wrong for some actions To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1359211/+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 1813872] Re: ubuntu keyboard indicator lost after focus on field type password
** Package changed: gnome-applets (Ubuntu) => gnome-shell (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1813872 Title: ubuntu keyboard indicator lost after focus on field type password Status in gnome-shell package in Ubuntu: Confirmed Bug description: 1. Open Firefox. 2. Go to page with field input type="password". 3. Stay focus on this field. 4. keyboard indicator lost. 5. Profit!!! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1813872/+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 1568852] Re: missing title bar for some applications
Good to hear that this does not happen on bionic. :) Unfortunately I have to say that this will not get fixed in 16.04, especially without steps with how to reproduce this. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/1568852 Title: missing title bar for some applications Status in metacity package in Ubuntu: Confirmed Bug description: Some applications are missing the titlebar in gnome-session-flashback with Metacity. Standard GNOME applications are not affected, but some that use Xlib directly, like mupdf or feh, are. Steps to reproduce: - Use mupdf to display any .pdf file, or use feh to display any image file. Expected result: - A window with a title bar appears. Actual result: - A window without title bar, but thicker borders, appears. - This does not always happen; sometimes, the title bars appear just fine. - see attached screenshot Things I tried: - Enabling/disabling org.gnome.metacity.compositing-manager via dconf-editor doesn't make a difference. - In an Xlib-based program I wrote myself, I could get rid of this by doing a dummy call to XSetWMNormalHints() with BaseSize set to the window size I was using anyway and MinSize set to 1x1. metacity: Installed: 1:3.18.3-1ubuntu2 Candidate: 1:3.18.3-1ubuntu2 Version table: *** 1:3.18.3-1ubuntu2 500 500 http://de.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status Description: Ubuntu Xenial Xerus (development branch) Release: 16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/1568852/+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 1292398] Re: Second screen position isn't saved from one session to another
alextomko, do you have same problem in 18.04? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1292398 Title: Second screen position isn't saved from one session to another Status in elementary OS: Fix Released Status in GNOME Settings Daemon: Incomplete Status in GNOME Shell: Confirmed Status in Ubuntu GNOME: Confirmed Status in Ubuntu GNOME trusty series: Confirmed Status in Ubuntu GNOME xenial series: Confirmed Status in Ubuntu GNOME Flashback: Confirmed Status in Unity: New Status in gnome-settings-daemon package in Ubuntu: Triaged Status in gnome-shell package in Ubuntu: Fix Released Bug description: (Noticed on Ubuntu 14.04 beta 1 GNOME) At work I have a second screen, which I prefer to virtually put on the left side of my laptop screen. Using gnome-control-center I can change the position of the second without problem. But when I disconnect the second screen (to work on another place) and then connect it again OR if I just power off the laptop and turn it on again, the second screen position is set back to the default right position. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gnome-control-center 1:3.6.3-0ubuntu53 ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6 Uname: Linux 3.13.0-17-generic x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Mar 14 08:50:00 2014 InstallationDate: Installed on 2014-03-01 (12 days ago) InstallationMedia: Ubuntu-GNOME 14.04 "Trusty Tahr" - Alpha amd64 (20140226) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_gnome-control-center: deja-dup 29.5-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/elementaryos/+bug/1292398/+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 1769838] Re: Per-window input sources option does not work on Bionic with gnome-flashback
** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/1769838 Title: Per-window input sources option does not work on Bionic with gnome- flashback Status in gnome-flashback package in Ubuntu: Fix Released Status in metacity package in Ubuntu: Fix Released Status in gnome-flashback source package in Bionic: Fix Committed Status in metacity source package in Bionic: Fix Committed Bug description: [Impact] * An explanation of the effects of the bug on users and: Setting the 'Input Source Options' to 'Allow different sources for each window' does not work. * justification for backporting the fix to the stable release: This is a bug in Ubuntu Bionic's version of gnome-flashback (3.28) (because the GUI lets the user change the input source option but the backend does nothing) [Test Case] * detailed instructions how to reproduce the bug - Set Input Source Options to Allow different sources for each window in gnome-control-center -> Region & Language -> Options - Realize that if you set different layouts for different windows it does not change automatically when changing windows. [Regression Potential] * Metacity now ignores its own events when predicting focus changes. Its own events are recognized by comparing timestamps and serial numbers. If something potentially goes wrong, it can either not ignore its own events, or ignore external events. In both cases the focus prediction will be broken. Also there could be potentially a race condition, but the patch protects against it by making a dummy request with bumped serial number. (Note: the second metacity patch is an amendment for the first one, so the previous analysis applies to both patches.) * GNOME-Flashback has some new code for handling per-window input sources. The change_per_window_source() function returns early if the sources_per_window option (obtained from GSettings: org.gnome.desktop .input-sources per-window) is false. As that option is false by default, in the default configuration most of the new code won't be executed at all. The potential breakage may happen if it is set to true. Such potential breakage includes: wrong input sources handling (it was wrong before anyway), gnome-flashback crashes. The patches are already applied in Cosmic, and currently no crashes are reported against the Cosmic version of gnome-flashback on errors.ubuntu.com. [Other Info] This needs fixes in both gnome-flashback and metacity. Here are the relevant commits in gnome-3-28 branches: https://gitlab.gnome.org/GNOME/metacity/commit/b96341dabffc3589 (ensure that we ignore our own focus events for focus predictions) https://gitlab.gnome.org/GNOME/metacity/commit/9956d376d38d0ad6 (fix problems with focus tracking) https://gitlab.gnome.org/GNOME/gnome-flashback/commit/3c4c6ecddef48cd5 (implement per window input sources) The gnome-session-flashback dependency on metacity will be bumped. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-flashback/+bug/1769838/+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 1793167] Re: Dual screen: context menu and dialog truncated
** Package changed: gnome-panel (Ubuntu) => gnome-shell (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1793167 Title: Dual screen: context menu and dialog truncated Status in gnome-shell package in Ubuntu: New Bug description: I'm using two displays vertically. One large (3840x2160) and one small (1920 x1080 If I put the 2 displays horizontally or vertically with left edge aligned everything is correct. If I put the large display above the small one without left edges aligned, I have got the following problems: - When right clicking in nautilus the contect menu is either tiny or completly truncated - When I open Eclipse, the first JDialog is truncated and I can't continue opening it. I'm using Ubuntu 18.04 LTS Description: Ubuntu 18.04.1 LTS Release: 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1793167/+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 1507764] Re: metacity crashed with signal 5 in _XEventsQueued() ; forcing gnome session to logout
3.18.7 is way too old at this point. Please upgrade if you can. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/1507764 Title: metacity crashed with signal 5 in _XEventsQueued() ; forcing gnome session to logout Status in metacity package in Ubuntu: Expired Bug description: This bug seemed to occur already since earlier versions of Ubuntu, and usually would just end up leaving me with undecorated windows, from which recovery was as easy as restarting metacity by hand, but in this release of Ubuntu (15.04), it seems gnome-session tries to restart it too many times in a too short span, and then decides arbitrarily that it failed so bad it has to kill the whole session. So, while the metacity bug is really a thing, my real problem actually might be a gnome-session-bin bug. I expect metacity crashing would not bring down the whole session, as is the case currently. At any rate, this is extremely annoying, I am hitting this bug about every two days, and because of it and the regression in crash handling, I end up losing all my windows and running programs. (In all fairness, I am suspecting a hardware issue, but the problem remains that a sub process dying should not cause the parent process to die like this) ProblemType: Crash DistroRelease: Ubuntu 15.04 Package: metacity 1:3.14.3-1ubuntu7 ProcVersionSignature: Ubuntu 3.19.0-31.36-generic 3.19.8-ckt7 Uname: Linux 3.19.0-31-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.17.2-0ubuntu1.5 Architecture: amd64 CrashCounter: 1 CurrentDesktop: GNOME-Flashback:Unity Date: Tue Oct 20 05:19:37 2015 ExecutablePath: /usr/bin/metacity InstallationDate: Installed on 2010-01-30 (2088 days ago) InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027.1) ProcCmdline: metacity ProcEnviron: LANGUAGE=en_US:en PATH=(custom, user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/zsh Signal: 5 SourcePackage: metacity StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6 _XEventsQueued () from /usr/lib/x86_64-linux-gnu/libX11.so.6 _XGetRequest () from /usr/lib/x86_64-linux-gnu/libX11.so.6 XFixesCopyRegion () from /usr/lib/x86_64-linux-gnu/libXfixes.so.3 Title: metacity crashed with signal 5 in _XEventsQueued() UpgradeStatus: Upgraded to vivid on 2015-09-05 (44 days ago) UserGroups: adm admin audio cdrom dialout libvirtd lpadmin plugdev pulse pulse-access sambashare vboxusers video To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/1507764/+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 1568852] Re: missing title bar for some applications
3.18 is very old release, does this happens with 3.28? Is there any way to reproduce this bug always? Bug description says that it does not happen always... :( -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/1568852 Title: missing title bar for some applications Status in metacity package in Ubuntu: Confirmed Bug description: Some applications are missing the titlebar in gnome-session-flashback with Metacity. Standard GNOME applications are not affected, but some that use Xlib directly, like mupdf or feh, are. Steps to reproduce: - Use mupdf to display any .pdf file, or use feh to display any image file. Expected result: - A window with a title bar appears. Actual result: - A window without title bar, but thicker borders, appears. - This does not always happen; sometimes, the title bars appear just fine. - see attached screenshot Things I tried: - Enabling/disabling org.gnome.metacity.compositing-manager via dconf-editor doesn't make a difference. - In an Xlib-based program I wrote myself, I could get rid of this by doing a dummy call to XSetWMNormalHints() with BaseSize set to the window size I was using anyway and MinSize set to 1x1. metacity: Installed: 1:3.18.3-1ubuntu2 Candidate: 1:3.18.3-1ubuntu2 Version table: *** 1:3.18.3-1ubuntu2 500 500 http://de.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status Description: Ubuntu Xenial Xerus (development branch) Release: 16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/1568852/+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 1780468] Re: Blurry titlebar font when window is not maximized
Can you attach your theme? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/1780468 Title: Blurry titlebar font when window is not maximized Status in metacity package in Ubuntu: New Bug description: What happens I've configured Compiz window manager to use gtk-window-decorator so that it may apply my Metacity theme for the titlebars. With this decorator, I've noticed that Compiz renders slightly blurry titlebar fonts when a window is not maximized. Once the window is maximized, sharp fonts are rendered. When a window is not maximized, the font seems to lack sub-pixel hinting or anti-aliasing, hence the slightly blurry appearance. I zoomed in on the font when the window was maximized and observed bluish lines around the characters. When a window was not maximized, the zoomed-in characters didn't have the bluish lines. I've tested and seen that the Marco window manager and the Emerald decorator (used with Compiz) both render sharp titlebar fonts regardless of whether a window is maximized or not. The image in the below link shows the slight difference in font rendering when Compiz is used with gtk-window-decorator. Firefox's window was maximized, with sharp text, while VLC's window was not maximized, with slightly blurry text. https://i.stack.imgur.com/5BalZ.png Upon switching to Marco window manager, both texts are sharp. https://i.stack.imgur.com/9Gzli.png When the "Compiz with gtk-window-decorator" setup is zoomed-in, blue lines around the maximized Firefox window titlebar text are visible (it looks like sub-pixel rendering to me). The blue lines are completely lacking in the un-maximized VLC window titlebar text. https://i.stack.imgur.com/XDSAU.png What I expect to happen --- The titlebar font rendering should be sharp for both maximized and un-maximized windows. The cause (clip_to_rounded_corners) --- Upon investigating, I've discovered that Compiz's gtk-window-decorator uses the libmetacity library. The clip_to_rounded_corners() function in "meta-theme-metacity.c" is called to draw rounded corners for the un-maximized windows in my theme. It seems the call to draw rounded corners by cairo_arc() in that function somehow affects the font rendering. When windows are maximized, the drawing of rounded corners is not performed, hence the sharp font rendering. I rebuilt the libmetacity library with the clip_to_rounded_corners() call commented out and achieved sharp fonts for un-maximized windows. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: metacity 1:3.28.0-1 ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18 Uname: Linux 4.15.0-24-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: MATE Date: Fri Jul 6 19:52:03 2018 InstallationDate: Installed on 2018-05-06 (61 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: metacity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/1780468/+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 1780468] Re: Blurry titlebar font when window is not maximized
Is problem visible also in metacity-theme-viewer? If so then please use max scale and attach to upstream bug screenshot that looks good and other that shows problem. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/1780468 Title: Blurry titlebar font when window is not maximized Status in metacity package in Ubuntu: New Bug description: What happens I've configured Compiz window manager to use gtk-window-decorator so that it may apply my Metacity theme for the titlebars. With this decorator, I've noticed that Compiz renders slightly blurry titlebar fonts when a window is not maximized. Once the window is maximized, sharp fonts are rendered. When a window is not maximized, the font seems to lack sub-pixel hinting or anti-aliasing, hence the slightly blurry appearance. I zoomed in on the font when the window was maximized and observed bluish lines around the characters. When a window was not maximized, the zoomed-in characters didn't have the bluish lines. I've tested and seen that the Marco window manager and the Emerald decorator (used with Compiz) both render sharp titlebar fonts regardless of whether a window is maximized or not. The image in the below link shows the slight difference in font rendering when Compiz is used with gtk-window-decorator. Firefox's window was maximized, with sharp text, while VLC's window was not maximized, with slightly blurry text. https://i.stack.imgur.com/5BalZ.png Upon switching to Marco window manager, both texts are sharp. https://i.stack.imgur.com/9Gzli.png When the "Compiz with gtk-window-decorator" setup is zoomed-in, blue lines around the maximized Firefox window titlebar text are visible (it looks like sub-pixel rendering to me). The blue lines are completely lacking in the un-maximized VLC window titlebar text. https://i.stack.imgur.com/XDSAU.png What I expect to happen --- The titlebar font rendering should be sharp for both maximized and un-maximized windows. The cause (clip_to_rounded_corners) --- Upon investigating, I've discovered that Compiz's gtk-window-decorator uses the libmetacity library. The clip_to_rounded_corners() function in "meta-theme-metacity.c" is called to draw rounded corners for the un-maximized windows in my theme. It seems the call to draw rounded corners by cairo_arc() in that function somehow affects the font rendering. When windows are maximized, the drawing of rounded corners is not performed, hence the sharp font rendering. I rebuilt the libmetacity library with the clip_to_rounded_corners() call commented out and achieved sharp fonts for un-maximized windows. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: metacity 1:3.28.0-1 ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18 Uname: Linux 4.15.0-24-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: MATE Date: Fri Jul 6 19:52:03 2018 InstallationDate: Installed on 2018-05-06 (61 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: metacity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/1780468/+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 1780468] Re: Blurry titlebar font when window is not maximized
In metacity-theme-viewer you should change GTK+ to Metacity... Please open upstream issue: https://gitlab.gnome.org/GNOME/metacity/issues -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/1780468 Title: Blurry titlebar font when window is not maximized Status in metacity package in Ubuntu: New Bug description: What happens I've configured Compiz window manager to use gtk-window-decorator so that it may apply my Metacity theme for the titlebars. With this decorator, I've noticed that Compiz renders slightly blurry titlebar fonts when a window is not maximized. Once the window is maximized, sharp fonts are rendered. When a window is not maximized, the font seems to lack sub-pixel hinting or anti-aliasing, hence the slightly blurry appearance. I zoomed in on the font when the window was maximized and observed bluish lines around the characters. When a window was not maximized, the zoomed-in characters didn't have the bluish lines. I've tested and seen that the Marco window manager and the Emerald decorator (used with Compiz) both render sharp titlebar fonts regardless of whether a window is maximized or not. The image in the below link shows the slight difference in font rendering when Compiz is used with gtk-window-decorator. Firefox's window was maximized, with sharp text, while VLC's window was not maximized, with slightly blurry text. https://i.stack.imgur.com/5BalZ.png Upon switching to Marco window manager, both texts are sharp. https://i.stack.imgur.com/9Gzli.png When the "Compiz with gtk-window-decorator" setup is zoomed-in, blue lines around the maximized Firefox window titlebar text are visible (it looks like sub-pixel rendering to me). The blue lines are completely lacking in the un-maximized VLC window titlebar text. https://i.stack.imgur.com/XDSAU.png What I expect to happen --- The titlebar font rendering should be sharp for both maximized and un-maximized windows. The cause (clip_to_rounded_corners) --- Upon investigating, I've discovered that Compiz's gtk-window-decorator uses the libmetacity library. The clip_to_rounded_corners() function in "meta-theme-metacity.c" is called to draw rounded corners for the un-maximized windows in my theme. It seems the call to draw rounded corners by cairo_arc() in that function somehow affects the font rendering. When windows are maximized, the drawing of rounded corners is not performed, hence the sharp font rendering. I rebuilt the libmetacity library with the clip_to_rounded_corners() call commented out and achieved sharp fonts for un-maximized windows. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: metacity 1:3.28.0-1 ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18 Uname: Linux 4.15.0-24-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: MATE Date: Fri Jul 6 19:52:03 2018 InstallationDate: Installed on 2018-05-06 (61 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: metacity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/1780468/+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 1780468] Re: Blurry titlebar font when window is not maximized
Do you have same problem with metacity? Sounds like you tested only gtk- window-decorator and marco... Can you test also with metacity-theme-viewer? Does it happen also with other themes? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/1780468 Title: Blurry titlebar font when window is not maximized Status in metacity package in Ubuntu: New Bug description: What happens I've configured Compiz window manager to use gtk-window-decorator so that it may apply my Metacity theme for the titlebars. With this decorator, I've noticed that Compiz renders slightly blurry titlebar fonts when a window is not maximized. Once the window is maximized, sharp fonts are rendered. When a window is not maximized, the font seems to lack sub-pixel hinting or anti-aliasing, hence the slightly blurry appearance. I zoomed in on the font when the window was maximized and observed bluish lines around the characters. When a window was not maximized, the zoomed-in characters didn't have the bluish lines. I've tested and seen that the Marco window manager and the Emerald decorator (used with Compiz) both render sharp titlebar fonts regardless of whether a window is maximized or not. The image in the below link shows the slight difference in font rendering when Compiz is used with gtk-window-decorator. Firefox's window was maximized, with sharp text, while VLC's window was not maximized, with slightly blurry text. https://i.stack.imgur.com/5BalZ.png Upon switching to Marco window manager, both texts are sharp. https://i.stack.imgur.com/9Gzli.png When the "Compiz with gtk-window-decorator" setup is zoomed-in, blue lines around the maximized Firefox window titlebar text are visible (it looks like sub-pixel rendering to me). The blue lines are completely lacking in the un-maximized VLC window titlebar text. https://i.stack.imgur.com/XDSAU.png What I expect to happen --- The titlebar font rendering should be sharp for both maximized and un-maximized windows. The cause (clip_to_rounded_corners) --- Upon investigating, I've discovered that Compiz's gtk-window-decorator uses the libmetacity library. The clip_to_rounded_corners() function in "meta-theme-metacity.c" is called to draw rounded corners for the un-maximized windows in my theme. It seems the call to draw rounded corners by cairo_arc() in that function somehow affects the font rendering. When windows are maximized, the drawing of rounded corners is not performed, hence the sharp font rendering. I rebuilt the libmetacity library with the clip_to_rounded_corners() call commented out and achieved sharp fonts for un-maximized windows. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: metacity 1:3.28.0-1 ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18 Uname: Linux 4.15.0-24-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: MATE Date: Fri Jul 6 19:52:03 2018 InstallationDate: Installed on 2018-05-06 (61 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: metacity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/1780468/+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 1777240] Re: Pop-up window from panel indicator qbirthday too much to the left, not fully visible
** Changed in: gnome-shell (Ubuntu) Status: Incomplete => New -- 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/1777240 Title: Pop-up window from panel indicator qbirthday too much to the left, not fully visible Status in gnome-shell package in Ubuntu: New Bug description: I managed to install the great birthday reminder tool qbirthday (https://github.com/lafrech/qbirthday, Qt port of GBirthday, a GTK application) on normal Ubuntu 18.04 (GNOME). It works fine but the displayed list (pop-up window) is placed to the left side and therefore not fully visible (it works without flaws with the desktop MATE), see attached screenshot. It is interesting that once every other week, the window opens with one click and mostly visible (just a bit too much to the right). Thanks for any help and hint in advance. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1777240/+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 1737836] Re: Standard clock applet is oversized in Artful
I think I know where is the problem, but I have no time to test / confirm it... If there is no response from me after 1. June then please open upstream bug when all GNOME modules will be migrated to gitlab. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-panel in Ubuntu. https://bugs.launchpad.net/bugs/1737836 Title: Standard clock applet is oversized in Artful Status in gnome-panel package in Ubuntu: New Bug description: In Artful if the standard clock applet is used there is a dead-space to the left of it. In my first screenshot you can see the dead-space between the indicator-applet and the clock applet. In the second screenshot you can see I've moved the clock applet to the left and the same dead-space exists between it and the inhibit-applet. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-panel 1:3.24.1-1ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13 Uname: Linux 4.13.0-19-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 CurrentDesktop: GNOME-Flashback:GNOME Date: Tue Dec 12 15:19:25 2017 GsettingsChanges: b'org.gnome.gnome-panel.layout' b'object-id-list' b"['window-list', 'workspace-switcher', 'clock', 'indicator-applet', 'inhibit-applet', 'menu-button', 'trash-applet', 'launcher', 'launcher-0', 'launcher-1']" b'org.gnome.gnome-panel.layout' b'toplevel-id-list' b"['bottom-panel']" InstallationDate: Installed on 2017-12-11 (1 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-panel UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-panel/+bug/1737836/+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 635310] Re: Gnome-Applets (Invest) - ^DJI symbol stopped showing
** Changed in: gnome-applets (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-applets in Ubuntu. https://bugs.launchpad.net/bugs/635310 Title: Gnome-Applets (Invest) - ^DJI symbol stopped showing Status in gnome-applets package in Ubuntu: Invalid Bug description: Binary package hint: gnome-applets DELL LATITUDE D600 UBUNTU 9.10 +proposed GNOME 2.28.1 GNOME-APPLETS 2.28.0 INVEST 2.28.0 EXPECTED: Have been using stock symbols ^DJI, ^W1DOW, FXI, EWU - to pull Dow Jones Industrial Average, Dow Jones Global Index, iShares FTSE/Xinhua China 25 Index and iShares MSCI United Kingdom Index since February 2010 from the Yahoo Finance servers without problems. ACTUAL: ^DJI shows under preferences, but no longer displays. Have tried: deleting/restoring ^DJI and/or all of the symbols; removing/restoring to panel; deleting ~/.gnome2/invest- applet/stocks.pickle ProblemType: Bug Architecture: i386 CheckboxSubmission: a4c8a5401b1e450828d3582bd9d33b9e CheckboxSystem: efd05939b08abfe86caa44c3820f8e56 Date: Fri Sep 10 14:44:32 2010 DistroRelease: Ubuntu 9.10 InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5) Package: gnome-applets 2.28.0-0ubuntu2 ProcEnviron: PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-22.64-generic SourcePackage: gnome-applets Uname: Linux 2.6.31-22-generic i686 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-applets/+bug/635310/+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 988473] Re: /usr/bin/invest-chart has bogus #! line
** Changed in: gnome-applets (Ubuntu) Status: Triaged => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-applets in Ubuntu. https://bugs.launchpad.net/bugs/988473 Title: /usr/bin/invest-chart has bogus #! line Status in GNOME Applets: Fix Released Status in gnome-applets package in Ubuntu: Invalid Bug description: % head -n 1 /usr/bin/invest-chart #!/usr/bin/env python While it's fine, preferable even for the development version of invest-chart to use the above #! line, it is asking for trouble in the deployed production version. When installed, invest-chart should use #!/usr/bin/python To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-applets/+bug/988473/+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 504042] Re: invest applet MACD is incorrectly displayed
** Changed in: gnome-applets (Ubuntu) Status: Triaged => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-applets in Ubuntu. https://bugs.launchpad.net/bugs/504042 Title: invest applet MACD is incorrectly displayed Status in GNOME Applets: New Status in gnome-applets package in Ubuntu: Invalid Bug description: Binary package hint: gnome-applets using Ubuntu 9.10 karmic gnome-applets: Installed: 2.28.0-0ubuntu2 currently, the MACD indicator is displayed as two histograms, one for the MACD and one for the "signal line". this is incorrect. the MACD graph should be presented as two lines for the MACD and signal, and optionally, a histogram to show the difference between the two. the wikipedia page here shows what i mean: http://en.wikipedia.org/wiki/MACD It took me a while to work out what was going on with the macd on this applet, and currently the information which this indicator is supposed to convey is often hard to read. i really like this applet and find it much more convenient that anything else available, but this is letting it down IMHO. best regards, ex-oficio To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-applets/+bug/504042/+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 972371] Re: Invest Applet fails to open menu options
** Changed in: gnome-applets (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-applets in Ubuntu. https://bugs.launchpad.net/bugs/972371 Title: Invest Applet fails to open menu options Status in gnome-applets package in Ubuntu: Invalid Bug description: This is version 3.2.1 Invest Applet fails to open any menu options with an error like: TypeError occurred: on_refresh() takes exactly 3 arguments (2 given) TypeError occurred: on_about() takes exactly 3 arguments (2 given) TypeError occurred: on_preferences() takes exactly 3 arguments (2 given) TypeError occurred: on_help() takes exactly 3 arguments (2 given) I have succesfully modified applet.py like this: def on_about(self, action) on each option and it works. I have removed applet.pyc too. I have had no other errors changing those functions. (Sorry my poor English) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-applets/+bug/972371/+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 775387] Re: Invest-applet fails to start after upgrade to Natty
** Changed in: gnome-applets (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-applets in Ubuntu. https://bugs.launchpad.net/bugs/775387 Title: Invest-applet fails to start after upgrade to Natty Status in gnome-applets package in Ubuntu: Invalid Bug description: Binary package hint: gnome-applets Bug occurred immediately after upgrade from Maverick to Natty. (I am now using the Ubuntu Classic desktop, to retain Gnome stuff) gnome-applets version: 2.32.1.1-0ubuntu5 I expected the Invest applet to be visible in my Gnome toolbar after the upgrade; however although other applets are present (system monitor, weather, etc) I cannot see the Invest icon. Attempting to add it back does not give any errors messages, however it does not appear. Attempting to run the applet from the command line produces the following output: tobyc@adonai:~$ /usr/lib/gnome-applets/invest-applet -d 2011-05-02 17:18:52.192521: Debugging enabled 2011-05-02 17:18:52.192570: Data Dir: /usr/share/gnome-applets/invest-applet 2011-05-02 17:18:52.192585: Detected PROXY: None A "ps" command shows that the applet is now running - however it still does not appear anywhere in my visible toolbars. Killing and restarting the applet also does not help. Ditto for rebooting. Any way I can help debug this? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-applets/+bug/775387/+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 250997] Re: gweather-applet-2 crashed with SIGSEGV in bonobo_ui_node_to_string()
** Changed in: gnome-applets (Ubuntu) Status: Triaged => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-applets in Ubuntu. https://bugs.launchpad.net/bugs/250997 Title: gweather-applet-2 crashed with SIGSEGV in bonobo_ui_node_to_string() Status in GNOME Applets: Expired Status in gnome-applets package in Ubuntu: Invalid Bug description: Binary package hint: gnome-applets N/A ProblemType: Crash Architecture: i386 Date: Tue Jul 22 14:25:49 2008 DistroRelease: Ubuntu 8.04 ExecutablePath: /usr/lib/gnome-applets/gweather-applet-2 NonfreeKernelModules: nvidia Package: gnome-applets 2.22.2-0ubuntu2 PackageArchitecture: i386 ProcCmdline: /usr/lib/gnome-applets/gweather-applet-2 --oaf-activate-iid=OAFIID:GNOME_GWeatherApplet_Factory --oaf-ior-fd=22 ProcEnviron: LANG=en_US.UTF-8 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games SHELL=/bin/bash Signal: 11 SourcePackage: gnome-applets StacktraceTop: ?? () from /usr/lib/libbonoboui-2.so.0 ?? () from /usr/lib/libbonoboui-2.so.0 ?? () from /usr/lib/libbonoboui-2.so.0 bonobo_ui_node_to_string () from /usr/lib/libbonoboui-2.so.0 bonobo_ui_util_set_ui () from /usr/lib/libbonoboui-2.so.0 Title: gweather-applet-2 crashed with SIGSEGV in bonobo_ui_node_to_string() Uname: Linux 2.6.24-19-generic i686 UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev powerdev scanner video To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-applets/+bug/250997/+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 385948] Re: Invest stock data does not refresh automatically
** Changed in: gnome-applets (Ubuntu) Status: Triaged => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-applets in Ubuntu. https://bugs.launchpad.net/bugs/385948 Title: Invest stock data does not refresh automatically Status in GNOME Applets: Expired Status in gnome-applets package in Ubuntu: Invalid Bug description: Binary package hint: gnome-applets Running the Invest GNOME-applet (2.26.1) on Ubuntu 9.04. The stock data does not refresh automatically, I have to right-click on the applet and select "refresh." There doesn't seem to be any options for controlling a refresh interval. Stock data should periodically refresh automatically. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-applets/+bug/385948/+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 315671] Re: weather applet hangs when closing details window
** Changed in: gnome-applets (Ubuntu) Status: Triaged => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-applets in Ubuntu. https://bugs.launchpad.net/bugs/315671 Title: weather applet hangs when closing details window Status in GNOME Applets: Expired Status in gnome-applets package in Ubuntu: Invalid Bug description: Binary package hint: gnome-applets This bug appeared when I upgraded from intrepid to jaunty: the weather applet displays correctly in the panel, and can open its details window. However, when I click the Close button in that window, it hangs, with this stacktrace. It seems to be reproducible. (gdb) bt #0 0xb80b7430 in __kernel_vsyscall () #1 0xb7958997 in poll () from /lib/tls/i686/cmov/libc.so.6 #2 0xb7a4478b in IA__g_poll (fds=0x93b9e08, nfds=8, timeout=-1) at /build/buildd/glib2.0-2.19.4/glib/gpoll.c:127 #3 0xb7a37052 in g_main_context_iterate (context=0x906ef38, block=1, dispatch=1, self=0x90163c0) at /build/buildd/glib2.0-2.19.4/glib/gmain.c:2761 #4 0xb7a37381 in IA__g_main_context_iteration (context=0x906ef38, may_block=1) at /build/buildd/glib2.0-2.19.4/glib/gmain.c:2511 #5 0xb73c3287 in link_main_iteration () from /usr/lib/libORBit-2.so.0 #6 0xb73c32f9 in link_wait () from /usr/lib/libORBit-2.so.0 #7 0xb73c3edd in link_connection_wait_connected () from /usr/lib/libORBit-2.so.0 #8 0xb73ab925 in ?? () from /usr/lib/libORBit-2.so.0 #9 0xb73abb18 in ORBit_object_get_connection () from /usr/lib/libORBit-2.so.0 #10 0xb73aa772 in ORBit_small_invoke_stub () from /usr/lib/libORBit-2.so.0 #11 0xb73aaa39 in ORBit_small_invoke_stub_n () from /usr/lib/libORBit-2.so.0 #12 0xb73b778a in ORBit_c_stub_invoke () from /usr/lib/libORBit-2.so.0 #13 0xb6af5a14 in Accessibility_EventListener_notifyEvent (_obj=0x907c928, e=0xbfad3240, ev=0xb6c0322c) at Accessibility-stubs.c:422 #14 0xb6bff37c in spi_atk_emit_eventv (gobject=0x9362a58, detail1=0, detail2=0, any=0xbfad32ac, format=0xb6c01264 "window:%s") at bridge.c:802 #15 0xb6bffb27 in spi_atk_bridge_window_event_listener ( ---Type to continue, or q to quit--- signal_hint=0xbfad33ac, n_param_values=1, param_values=0x93bc168, data=0x9080268) at bridge.c:1272 #16 0xb7ad4099 in signal_emit_unlocked_R (node=0x907f7e0, detail=0, instance=0x9362a58, emission_return=0x0, instance_and_params=0x93bc168) at /build/buildd/glib2.0-2.19.4/gobject/gsignal.c:3210 #17 0xb7ad5d9e in IA__g_signal_emit_valist (instance=0x9362a58, signal_id=179, detail=0, var_args=0xbfad354c "ô\017¯·ØZ7\t") at /build/buildd/glib2.0-2.19.4/gobject/gsignal.c:2977 #18 0xb7ad6246 in IA__g_signal_emit (instance=0x9362a58, signal_id=179, detail=0) at /build/buildd/glib2.0-2.19.4/gobject/gsignal.c:3034 #19 0xb6b6cca9 in ?? () from /usr/lib/gtk-2.0/modules/libgail.so #20 0xb7acb0ce in IA__g_cclosure_marshal_VOID__UINT_POINTER ( closure=0x907f9b8, return_value=0x0, n_param_values=3, param_values=0x9375ad8, invocation_hint=0xbfad371c, marshal_data=0x935f078) at /build/buildd/glib2.0-2.19.4/gobject/gmarshal.c:672 #21 0xb7abcc9b in IA__g_closure_invoke (closure=0x907f9b8, return_value=0x0, n_param_values=3, param_values=0x9375ad8, invocation_hint=0xbfad371c) at /build/buildd/glib2.0-2.19.4/gobject/gclosure.c:767 #22 0xb7ad4685 in signal_emit_unlocked_R (node=0x9073fd0, detail=458, instance=0x906a540, emission_return=0x0, instance_and_params=0x9375ad8) at /build/buildd/glib2.0-2.19.4/gobject/gsignal.c:3244 #23 0xb7ad5d9e in IA__g_signal_emit_valist (instance=0x906a540, signal_id=154, detail=458, var_args=0xbfad3920 "") ---Type to continue, or q to quit--- at /build/buildd/glib2.0-2.19.4/gobject/gsignal.c:2977 #24 0xb7ad60ed in IA__g_signal_emit_by_name (instance=0x906a540, detailed_signal=0xb6b74442 "children-changed::remove") at /build/buildd/glib2.0-2.19.4/gobject/gsignal.c:3071 #25 0xb6b65901 in ?? () from /usr/lib/gtk-2.0/modules/libgail.so #26 0xb6b6598a in ?? () from /usr/lib/gtk-2.0/modules/libgail.so #27 0xb7ad4099 in signal_emit_unlocked_R (node=0x9047898, detail=0, instance=0x935f078, emission_return=0x0, instance_and_params=0x93bc1c8) at /build/buildd/glib2.0-2.19.4/gobject/gsignal.c:3210 #28 0xb7ad5d9e in IA__g_signal_emit_valist (instance=0x935f078, signal_id=16, detail=0, var_args=0xbfad3bdc "ôÏñ·xð5\t") at /build/buildd/glib2.0-2.19.4/gobject/gsignal.c:2977 #29 0xb7ad6246 in IA__g_signal_emit (instance=0x935f078, signal_id=16, detail=0) at /build/buildd/glib2.0-2.19.4/gobject/gsignal.c:3034 #30 0xb7dcefc4 in IA__gtk_widget_hide (widget=0x935f078) at /build/buildd/gtk+2.0-2.14.5/gtk/gtkwidget.c:3087 #31 0xb7dcf080 in gtk_widget_dispose (object=0x935f078) at /build/buildd/gtk+2.0-2.14.5/gtk/gtkwidge
[Desktop-packages] [Bug 561294] Re: Not a helpful or appropiate error message displayed
strangedata, you should report that for gnome-shell, this bug is for metacity which is not used by gnome shell session. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/561294 Title: Not a helpful or appropiate error message displayed Status in metacity package in Ubuntu: Confirmed Bug description: Binary package hint: metacity running compiz --replace as trying to debug an issue with lucid Beta 2 and I get the following output - Window manager warning: last_user_time (1271002643) is greater than comparison timestamp (799652). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Window manager warning: 0x4600028 (Social bro) appears to be one of the offending windows with a timestamp of 1271002643. Working around... Window manager warning: Received a _NET_WM_MOVERESIZE message for 0x4600028 (Social bro); these messages lack timestamps and therefore suck. while the error output is helpful surely a user seeing "these messages lack timestamps and therefore suck." is not at all helpful and should have a more appropriate error message displayed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/561294/+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 96800] Re: [apport] gnome-panel crashed with SIGSEGV in panel_applet_lockable()
** Changed in: gnome-panel (Ubuntu) Status: Triaged => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-panel in Ubuntu. https://bugs.launchpad.net/bugs/96800 Title: [apport] gnome-panel crashed with SIGSEGV in panel_applet_lockable() Status in GNOME Panel: Expired Status in gnome-panel package in Ubuntu: Invalid Bug description: Binary package hint: gnome-panel Browsing, and doing updates at the same time with Synaptic. ProblemType: Crash Architecture: i386 Date: Mon Mar 26 11:53:39 2007 DistroRelease: Ubuntu 7.04 ExecutablePath: /usr/bin/gnome-panel Package: gnome-panel 2.18.0-0ubuntu2 PackageArchitecture: i386 ProcCmdline: gnome-panel --sm-client-id 117f010001174923510005659 --screen 0 ProcCwd: /home/rodolfo ProcEnviron: SHELL=/bin/bash PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/bin/X11:/usr/games LANG=en_CA.UTF-8 LANGUAGE=en_CA:en Signal: 11 SourcePackage: gnome-panel StacktraceTop: panel_applet_lockable () panel_applet_frame_sync_menu_state () ?? () ?? () ?? () Uname: Linux amdasus 2.6.20-13-generic #2 SMP Sun Mar 25 00:21:25 UTC 2007 i686 GNU/Linux UserGroups: adm admin audio cdrom dialout dip floppy lpadmin plugdev scanner video To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-panel/+bug/96800/+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 1738651] Re: top right panel in Gnome Metacity Freezes a few minutes after login
*** This bug is a duplicate of bug 1725721 *** https://bugs.launchpad.net/bugs/1725721 ** This bug has been marked a duplicate of bug 1725721 gnome-panel in gnome-flashback-metacity session does not update time, indicators ; unable to click on gear button -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-panel in Ubuntu. https://bugs.launchpad.net/bugs/1738651 Title: top right panel in Gnome Metacity Freezes a few minutes after login Status in gnome-panel package in Ubuntu: New Bug description: Hello, I've reinstalled Ubuntu 17.10, and the top right panel in Gnome Metacity fails to respond after a minute or so. The left click doesn't work, but the right click does work (although it doesn't fix anything, it only says "About" which is useless). The upper left "Applications" and "Places" still works. I should also add that the time freezes as well. -Dave To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-panel/+bug/1738651/+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 1743686] Re: File system folder in nautilus Artful/Bionic flashback session does nothing
Unless `computer://` uri is invalid these days this is bug in nautilus. You can do this from terminal and get same thing/bug: nautilus computer:// ** Package changed: gnome-panel (Ubuntu) => nautilus (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-panel in Ubuntu. https://bugs.launchpad.net/bugs/1743686 Title: File system folder in nautilus Artful/Bionic flashback session does nothing Status in nautilus package in Ubuntu: New Bug description: Go to Places > Computer, left-click to open "Files", then select File System either by double-click or right-click + open and nothing happens. If you go Places > Home > Other locations and select Computer the file system opens as expected. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-panel 1:3.24.1-1ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13 Uname: Linux 4.13.0-25-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CurrentDesktop: GNOME-Flashback:GNOME Date: Tue Jan 16 21:54:39 2018 GsettingsChanges: b'org.gnome.gnome-panel.layout' b'object-id-list' b"['window-list', 'workspace-switcher', 'clock', 'cpu-freq-applet', 'indicator-applet', 'inhibit-applet', 'menu-button', 'multi-load-applet', 'trash-applet', 'launcher', 'launcher-0', 'launcher-1']" b'org.gnome.gnome-panel.layout' b'toplevel-id-list' b"['bottom-panel']" b'org.gnome.gnome-panel.run-dialog' b'history' b"['gufw']" InstallationDate: Installed on 2018-01-16 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-panel UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1743686/+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 1741902] Re: Drag and drop state may be freezed by rogue application
>From your bug: "Windows can still be bought to front by clicking them, but never gain focus and no application (besides nautlilus I guess, which is stalled) receives clicks or keystrokes." This sounds like nautilus has grabbed mouse & keyboard when it started drag & drop operation. From what I know it is perfectly valid action on X. Any app can grab keyboard and/or mouse... https://freedesktop.org/wiki/Specifications/XDND/ Read "Protecting against malfunctioning programs" section. It seems that it is application responsibility to make sure it does not crash and/or lock (doesn't wait forever). Reading your bug seems that nautilus just enters in "waiting forever" state when sftp connection drops. It just waits for something that will never happen and also does not ungrab keyboard and/or mouse. Yes, that is bad, very bad situation... But I don't see how this could be fixed somewhere else. Metacity (window manager) is not involved here, also I think there is nothing to fix in X. How can X know that application has entered some bad state? Nautilus most likely can detect that connection drops and in such case it must make sure that any started drag & drop operation is cancelled. If that happens with other apps, then it might be bug at toolkit level - gtk+. Can you provide steps how to reproduce this bug? Might be good idea to forward bug to upstream project: https://gitlab.gnome.org/GNOME/nautilus Maybe nautilus developers has already fixed this in newer versions. My 16.04 installations shows 1:3.18.4.is.3.14.3-0ubuntu6 as nautilus version which is very old version. -- 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/1741902 Title: Drag and drop state may be freezed by rogue application Status in metacity package in Ubuntu: New Status in nautilus package in Ubuntu: New Bug description: I had some issues with nautlilus in the past time, that of cause need to be resolved by the nautlilus devs, but it turns out that IO freezes (eg. dropped sftp connections) may freeze nautlilus while drag and drop operations, and hence freeze metacity in some kind, as d&d seems to lock some control to the participating applications. What I do: Drag a file from nautilus. What happens: Nautilus blocks for some reason, eg. dropped sftp connection. The mouse pointer stays in dragging state after releasing the mouse button. No drop action is executed. Windows can still be bought to front by clicking them, but never gain focus and no application (besides nautlilus I guess, which is stalled) receives clicks or keystrokes. If at some point nautilus crashes in turn, the system usability is fully restored. If not, a restart by hard shutdown is needed to regain control. What should happen: If an application fails to commence it's drag and drop interaction, the action should be canceled on metacity's behalf. Otherwise any rogue application can stop user interaction down to moving the pointer around, requiring hard reboot. Security considerations: Low. The freezed state seems to block screen locking, and may reveal an unprotected desktop if the rogue application releases control at some point, eg. by crashing. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: metacity 1:3.18.7-0ubuntu0.3 ProcVersionSignature: Ubuntu 4.4.0-105.128-generic 4.4.98 Uname: Linux 4.4.0-105-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CurrentDesktop: GNOME-Flashback:Unity Date: Mon Jan 8 14:52:41 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2016-08-23 (503 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: metacity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/1741902/+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 1741348] Re: gnome-flashback/gnome-panel: bottom right workspace selector will not accept preference change to more than 1 workspace
sudo apt-get install compizconfig-settings-manager Above will install settings manager if it is not already installed. Then open application, click on `General Options` and select `Desktop Size` tab. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-panel in Ubuntu. https://bugs.launchpad.net/bugs/1741348 Title: gnome-flashback/gnome-panel: bottom right workspace selector will not accept preference change to more than 1 workspace Status in gnome-panel package in Ubuntu: New Bug description: xwininfo: Window id: 0x2200016 "Bottom Expanded Edge Panel" Absolute upper-left X: 0 Absolute upper-left Y: 1416 Relative upper-left X: 0 Relative upper-left Y: 0 Width: 2560 Height: 24 Depth: 32 Visual: 0x82 Visual Class: TrueColor Border width: 0 Class: InputOutput Colormap: 0x222 (not installed) Bit Gravity State: NorthWestGravity Window Gravity State: NorthWestGravity Backing Store State: NotUseful Save Under State: no Map State: IsViewable Override Redirect State: no Corners: +0+1416 -0+1416 -0-0 +0-0 -geometry 2560x24+0-0 ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-panel 1:3.24.1-1ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13 Uname: Linux 4.13.0-21-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CurrentDesktop: GNOME-Flashback:GNOME Date: Thu Jan 4 15:32:50 2018 EcryptfsInUse: Yes GsettingsChanges: b'org.gnome.gnome-panel.layout' b'object-id-list' b"['menu-bar', 'show-destkop', 'window-list', 'workspace-switcher', 'launcher', 'launcher-0', 'launcher-1', 'launcher-2', 'launcher-3', 'launcher-4', 'launcher-5', 'launcher-7', 'launcher-8', 'launcher-10', 'launcher-12', 'launcher-13', 'launcher-6', 'launcher-9', 'launcher-14', 'notification-area', 'indicator-applet-complete', 'launcher-11']" b'org.gnome.gnome-panel.layout' b'toplevel-id-list' b"['top-panel', 'bottom-panel']" InstallationDate: Installed on 2017-01-05 (364 days ago) InstallationMedia: It SourcePackage: gnome-panel UpgradeStatus: Upgraded to artful on 2017-10-22 (74 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-panel/+bug/1741348/+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 1738651] Re: top right panel in Gnome Metacity Freezes a few minutes after login
Might be problem with indicator-applet. Does journalctl have errors and/or warnings related to indicator-applet when it freezes? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-panel in Ubuntu. https://bugs.launchpad.net/bugs/1738651 Title: top right panel in Gnome Metacity Freezes a few minutes after login Status in gnome-panel package in Ubuntu: New Bug description: Hello, I've reinstalled Ubuntu 17.10, and the top right panel in Gnome Metacity fails to respond after a minute or so. The left click doesn't work, but the right click does work (although it doesn't fix anything, it only says "About" which is useless). The upper left "Applications" and "Places" still works. I should also add that the time freezes as well. -Dave To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-panel/+bug/1738651/+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 1741348] Re: gnome-flashback/gnome-panel: bottom right workspace selector will not accept preference change to more than 1 workspace
This is known bug, you have to use CompizConfig Settings Manager to change that. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-panel in Ubuntu. https://bugs.launchpad.net/bugs/1741348 Title: gnome-flashback/gnome-panel: bottom right workspace selector will not accept preference change to more than 1 workspace Status in gnome-panel package in Ubuntu: New Bug description: xwininfo: Window id: 0x2200016 "Bottom Expanded Edge Panel" Absolute upper-left X: 0 Absolute upper-left Y: 1416 Relative upper-left X: 0 Relative upper-left Y: 0 Width: 2560 Height: 24 Depth: 32 Visual: 0x82 Visual Class: TrueColor Border width: 0 Class: InputOutput Colormap: 0x222 (not installed) Bit Gravity State: NorthWestGravity Window Gravity State: NorthWestGravity Backing Store State: NotUseful Save Under State: no Map State: IsViewable Override Redirect State: no Corners: +0+1416 -0+1416 -0-0 +0-0 -geometry 2560x24+0-0 ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-panel 1:3.24.1-1ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13 Uname: Linux 4.13.0-21-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CurrentDesktop: GNOME-Flashback:GNOME Date: Thu Jan 4 15:32:50 2018 EcryptfsInUse: Yes GsettingsChanges: b'org.gnome.gnome-panel.layout' b'object-id-list' b"['menu-bar', 'show-destkop', 'window-list', 'workspace-switcher', 'launcher', 'launcher-0', 'launcher-1', 'launcher-2', 'launcher-3', 'launcher-4', 'launcher-5', 'launcher-7', 'launcher-8', 'launcher-10', 'launcher-12', 'launcher-13', 'launcher-6', 'launcher-9', 'launcher-14', 'notification-area', 'indicator-applet-complete', 'launcher-11']" b'org.gnome.gnome-panel.layout' b'toplevel-id-list' b"['top-panel', 'bottom-panel']" InstallationDate: Installed on 2017-01-05 (364 days ago) InstallationMedia: It SourcePackage: gnome-panel UpgradeStatus: Upgraded to artful on 2017-10-22 (74 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-panel/+bug/1741348/+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 1741902] Re: Drag and drop state may be freezed by rogue application
Well, I don't know how drag & drop works so I can not say that it is bug in X server. I would start by reporting / re-assigning this bug to nautilus especially if it is only app that causes this problem. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/1741902 Title: Drag and drop state may be freezed by rogue application Status in metacity package in Ubuntu: New Bug description: I had some issues with nautlilus in the past time, that of cause need to be resolved by the nautlilus devs, but it turns out that IO freezes (eg. dropped sftp connections) may freeze nautlilus while drag and drop operations, and hence freeze metacity in some kind, as d&d seems to lock some control to the participating applications. What I do: Drag a file from nautilus. What happens: Nautilus blocks for some reason, eg. dropped sftp connection. The mouse pointer stays in dragging state after releasing the mouse button. No drop action is executed. Windows can still be bought to front by clicking them, but never gain focus and no application (besides nautlilus I guess, which is stalled) receives clicks or keystrokes. If at some point nautilus crashes in turn, the system usability is fully restored. If not, a restart by hard shutdown is needed to regain control. What should happen: If an application fails to commence it's drag and drop interaction, the action should be canceled on metacity's behalf. Otherwise any rogue application can stop user interaction down to moving the pointer around, requiring hard reboot. Security considerations: Low. The freezed state seems to block screen locking, and may reveal an unprotected desktop if the rogue application releases control at some point, eg. by crashing. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: metacity 1:3.18.7-0ubuntu0.3 ProcVersionSignature: Ubuntu 4.4.0-105.128-generic 4.4.98 Uname: Linux 4.4.0-105-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CurrentDesktop: GNOME-Flashback:Unity Date: Mon Jan 8 14:52:41 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2016-08-23 (503 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: metacity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/1741902/+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 1741902] Re: Drag and drop state may be freezed by rogue application
Why do you think that Metacity is the one who freezes? Have you tried other window managers and/or sessions and this happens only with Metacity? The thing is that Metacity does not do anything with drag and drop so that might be bug in nautilus and/or xserver. Can you provide steps that I can use to reproduce problem? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/1741902 Title: Drag and drop state may be freezed by rogue application Status in metacity package in Ubuntu: New Bug description: I had some issues with nautlilus in the past time, that of cause need to be resolved by the nautlilus devs, but it turns out that IO freezes (eg. dropped sftp connections) may freeze nautlilus while drag and drop operations, and hence freeze metacity in some kind, as d&d seems to lock some control to the participating applications. What I do: Drag a file from nautilus. What happens: Nautilus blocks for some reason, eg. dropped sftp connection. The mouse pointer stays in dragging state after releasing the mouse button. No drop action is executed. Windows can still be bought to front by clicking them, but never gain focus and no application (besides nautlilus I guess, which is stalled) receives clicks or keystrokes. If at some point nautilus crashes in turn, the system usability is fully restored. If not, a restart by hard shutdown is needed to regain control. What should happen: If an application fails to commence it's drag and drop interaction, the action should be canceled on metacity's behalf. Otherwise any rogue application can stop user interaction down to moving the pointer around, requiring hard reboot. Security considerations: Low. The freezed state seems to block screen locking, and may reveal an unprotected desktop if the rogue application releases control at some point, eg. by crashing. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: metacity 1:3.18.7-0ubuntu0.3 ProcVersionSignature: Ubuntu 4.4.0-105.128-generic 4.4.98 Uname: Linux 4.4.0-105-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CurrentDesktop: GNOME-Flashback:Unity Date: Mon Jan 8 14:52:41 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2016-08-23 (503 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: metacity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/1741902/+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 1729728] Re: window picker is broken in 3.26
Oh, sorry for that. It seems that GSettings schema is not installed. Should be fixed by: https://git.gnome.org/browse/gnome-applets/commit/?id=6aedbc3a6af541902c210f15e400635d165011ba -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-applets in Ubuntu. https://bugs.launchpad.net/bugs/1729728 Title: window picker is broken in 3.26 Status in gnome-applets package in Ubuntu: New Bug description: WindowPicker seems to be broken in 3.26. It just crashes upon applet addition on fresh 17.10. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-applets/+bug/1729728/+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
