[Dx-packages] [Bug 1467695] Re: Alt-Grave (`) switcher has flickering/pulsing shadow artifacts
Hello, a workaround that I have discovered is to disable framebuffer objects in the Compiz OpenGL plugin: gsettings set org.compiz.opengl:/org/compiz/profiles/unity/plugins/opengl/ framebuffer-object false Enter that in the terminal and it would take effect immediately; no logout required. Of course, we can expect that other desktop features that absolutely need OpenGL framebuffer objects might glitch or be affected in some way. And again, this is just a workaround to make the unsightly behaviour go away, and by no means a fix. It does give a clue, though, that it's related to the use of framebuffer objects by whatever it is that renders shadows and glow effects. -- You received this bug notification because you are a member of DX Packages, which is subscribed to nux in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1467695 Title: Alt-Grave (`) switcher has flickering/pulsing shadow artifacts Status in Nux: Triaged Status in Unity: Triaged Status in nux package in Ubuntu: Confirmed Status in unity package in Ubuntu: Triaged Status in nux source package in Xenial: Confirmed Status in unity source package in Xenial: Triaged Bug description: 1. Hold down Alt and keep it held down. 2. Press and release the key above Tab (Grave, or `). Keep alt held down. While Alt is held down, the drop shadows for the window or windows of the current application will keep building up and then going back to normal and building up again. It's almost as though the windows are being redrawn may times per second into a buffer without clearing it first each time (but clearing it every second or so). While this is happening, I notice that the drop shadow for the top bar does the same thing. This can also be observed if one uses Alt-Tab to select an app that has multiple windows that then expand out into a similar display. I've observed this on systems with Intel, NVIDIA, and ATI display hardware, so I don't think it's hardware-specific. All my Ubuntu systems have 2 or 3 monitors. I suspect multiple monitors are needed to reproduce this. To manage notifications about this bug go to: https://bugs.launchpad.net/nux/+bug/1467695/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1550129] Re: scope-runner-dbus.py crashed with SIGABRT
*** This bug is a duplicate of bug 1538471 *** https://bugs.launchpad.net/bugs/1538471 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1538471, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1550129/+attachment/4581477/+files/CoreDump.gz ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1550129/+attachment/4581479/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1550129/+attachment/4581480/+files/ProcStatus.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1550129/+attachment/4581481/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1550129/+attachment/4581482/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1538471 scope-runner-dbus.py assert failure: *** Error in `/usr/bin/python3': free(): invalid next size (fast): 0x01ca17b0 *** ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of DX Packages, which is subscribed to libunity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1550129 Title: scope-runner-dbus.py crashed with SIGABRT Status in libunity package in Ubuntu: New Bug description: I was browsing the 'net when out of the sudden the error message came up. I am running Xenial Xesus 16.04 amd64. ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: unity-scopes-runner 7.1.4+15.10.20151002-0ubuntu2 ProcVersionSignature: Ubuntu 4.3.0-7.18-generic 4.3.3 Uname: Linux 4.3.0-7-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CrashCounter: 1 CurrentDesktop: Unity Date: Thu Feb 25 22:53:00 2016 Dependencies: Disassembly: $7 = 0x0 ExecutablePath: /usr/share/unity-scopes/scope-runner-dbus.py InstallationDate: Installed on 2016-02-09 (16 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160131) InterpreterPath: /usr/bin/python3.5 PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/share/unity-scopes/scope-runner-dbus.py -s files/gdrive.scope ProcEnviron: XDG_RUNTIME_DIR= SHELL=/bin/bash LANGUAGE=en_US PATH=(custom, no user) LANG=en_US.UTF-8 Signal: 6 SourcePackage: libunity StacktraceTop: Title: scope-runner-dbus.py crashed with SIGABRT UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libunity/+bug/1550129/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 919801] Re: Unity dash file search is extremely slow
Not completely. While this change improve things on zeitgeist side (not fully), the unity lens part has still some room for improvements I think. -- You received this bug notification because you are a member of DX Packages, which is subscribed to zeitgeist in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/919801 Title: Unity dash file search is extremely slow Status in unity-lens-files: Incomplete Status in Zeitgeist Framework: Incomplete Status in unity-lens-files package in Ubuntu: Confirmed Status in zeitgeist package in Ubuntu: Fix Released Bug description: When I try to use the Unity dash search feature to navigate to files and folders, it is extremely slow. For example, if I hit the super button to launch the search and then type "Pictures" to get my pictures directory, it takes almost 5 seconds for the folder icon to show. In comparison, if I use Gnome-Do to navigate to my Pictures folder, it's basically instant. I have attached a video screencast so that you can see the problem for yourself. --- ApportVersion: 1.23-0ubuntu4 Architecture: i386 CompizPlugins: [core,bailer,detection,composite,opengl,compiztoolbox,decor,move,vpswitch,place,session,imgpng,mousepoll,resize,gnomecompat,regex,snap,grid,wall,unitymtgrabhandles,animation,expo,ezoom,workarounds,fade,scale,unityshell] DistroRelease: Ubuntu 11.10 InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Beta i386 (20110413) NonfreeKernelModules: nvidia Package: unity 5.0.0~+bzr1825ubuntu0+611 PackageArchitecture: i386 ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 3.0.0-14.23-generic 3.0.9 Tags: oneiric running-unity Uname: Linux 3.0.0-14-generic i686 UnreportableReason: This is not a genuine Ubuntu package UpgradeStatus: Upgraded to oneiric on 2011-10-14 (99 days ago) UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare To manage notifications about this bug go to: https://bugs.launchpad.net/unity-lens-files/+bug/919801/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 919801] Re: Unity dash file search is extremely slow
Is this bug done? Can I remove the unity-lens task? -- You received this bug notification because you are a member of DX Packages, which is subscribed to zeitgeist in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/919801 Title: Unity dash file search is extremely slow Status in unity-lens-files: Incomplete Status in Zeitgeist Framework: Incomplete Status in unity-lens-files package in Ubuntu: Confirmed Status in zeitgeist package in Ubuntu: Fix Released Bug description: When I try to use the Unity dash search feature to navigate to files and folders, it is extremely slow. For example, if I hit the super button to launch the search and then type "Pictures" to get my pictures directory, it takes almost 5 seconds for the folder icon to show. In comparison, if I use Gnome-Do to navigate to my Pictures folder, it's basically instant. I have attached a video screencast so that you can see the problem for yourself. --- ApportVersion: 1.23-0ubuntu4 Architecture: i386 CompizPlugins: [core,bailer,detection,composite,opengl,compiztoolbox,decor,move,vpswitch,place,session,imgpng,mousepoll,resize,gnomecompat,regex,snap,grid,wall,unitymtgrabhandles,animation,expo,ezoom,workarounds,fade,scale,unityshell] DistroRelease: Ubuntu 11.10 InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Beta i386 (20110413) NonfreeKernelModules: nvidia Package: unity 5.0.0~+bzr1825ubuntu0+611 PackageArchitecture: i386 ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 3.0.0-14.23-generic 3.0.9 Tags: oneiric running-unity Uname: Linux 3.0.0-14-generic i686 UnreportableReason: This is not a genuine Ubuntu package UpgradeStatus: Upgraded to oneiric on 2011-10-14 (99 days ago) UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare To manage notifications about this bug go to: https://bugs.launchpad.net/unity-lens-files/+bug/919801/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1549783] Re: Indicator shows "Tomorrow" for an alarm happening today when checked after midnight
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: indicator-datetime (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-datetime in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1549783 Title: Indicator shows "Tomorrow" for an alarm happening today when checked after midnight Status in indicator-datetime package in Ubuntu: Confirmed Bug description: BQ E4.5 (krillin) running OTA9.1 I have 2 recurring alarms set for 0730 and 0800. If I pull down the clock indicator bar after midnight, the 0730 alarm is listed as "Tomorrow". The Clock app lists the alarm correctly (although, if I rememebr correctly, there was previously a bug where the clock app would get this wrong too). The alarm functions correctly, but the indicator is unsettling. Steps to reproduce bug: 1. Create an alarm for *tomorrow morning*, say at 08:00 AM using the clock app. 2. When you swipe down the datetime indicator, it should correctly say that the alarm is scheduled for tomorrow 08:00 AM. 3. Open the system-settings app, and manually change the time to after midnight, say 02:00 AM next day. 4. Now swipe down the datetime indicator and it still says alarm scheduled for tomorrow 08:00 AM instead of "08:00AM". 5. Reopen the clock app and you will notice that it correctly say alarm is scheduled to run in another 6 hours (08:00AM minus 02:00AM) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1549783/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1549783] Re: Indicator shows "Tomorrow" for an alarm happening today when checked after midnight
** Description changed: BQ E4.5 (krillin) running OTA9.1 I have 2 recurring alarms set for 0730 and 0800. If I pull down the clock indicator bar after midnight, the 0730 alarm is listed as "Tomorrow". The Clock app lists the alarm correctly (although, if I rememebr correctly, there was previously a bug where the clock app would get this wrong too). The alarm functions correctly, but the indicator is unsettling. + + Steps to reproduce bug: + 1. Create an alarm for *tomorrow morning*, say at 08:00 AM using the clock app. + 2. When you swipe down the datetime indicator, it should correctly say that the alarm is scheduled for tomorrow 08:00 AM. + 3. Open the system-settings app, and manually change the time to after midnight, say 02:00 AM next day. + 4. Now swipe down the datetime indicator and it still says alarm scheduled for tomorrow 08:00 AM instead of "08:00AM". + 5. Reopen the clock app and you will notice that it correctly say alarm is scheduled to run in another 6 hours (08:00AM minus 02:00AM) -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-datetime in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1549783 Title: Indicator shows "Tomorrow" for an alarm happening today when checked after midnight Status in indicator-datetime package in Ubuntu: Confirmed Bug description: BQ E4.5 (krillin) running OTA9.1 I have 2 recurring alarms set for 0730 and 0800. If I pull down the clock indicator bar after midnight, the 0730 alarm is listed as "Tomorrow". The Clock app lists the alarm correctly (although, if I rememebr correctly, there was previously a bug where the clock app would get this wrong too). The alarm functions correctly, but the indicator is unsettling. Steps to reproduce bug: 1. Create an alarm for *tomorrow morning*, say at 08:00 AM using the clock app. 2. When you swipe down the datetime indicator, it should correctly say that the alarm is scheduled for tomorrow 08:00 AM. 3. Open the system-settings app, and manually change the time to after midnight, say 02:00 AM next day. 4. Now swipe down the datetime indicator and it still says alarm scheduled for tomorrow 08:00 AM instead of "08:00AM". 5. Reopen the clock app and you will notice that it correctly say alarm is scheduled to run in another 6 hours (08:00AM minus 02:00AM) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1549783/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1549783] Re: Indicator shows "Tomorrow" for an alarm happening today when checked after midnight
** Attachment added: "Clock app show the alarm correctly" https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1549783/+attachment/4580806/+files/screenshot20160224_012320048.png -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-datetime in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1549783 Title: Indicator shows "Tomorrow" for an alarm happening today when checked after midnight Status in indicator-datetime package in Ubuntu: New Bug description: BQ E4.5 (krillin) running OTA9.1 I have 2 recurring alarms set for 0730 and 0800. If I pull down the clock indicator bar after midnight, the 0730 alarm is listed as "Tomorrow". The Clock app lists the alarm correctly (although, if I rememebr correctly, there was previously a bug where the clock app would get this wrong too). The alarm functions correctly, but the indicator is unsettling. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1549783/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1549783] [NEW] Indicator shows "Tomorrow" for an alarm happening today when checked after midnight
Public bug reported: BQ E4.5 (krillin) running OTA9.1 I have 2 recurring alarms set for 0730 and 0800. If I pull down the clock indicator bar after midnight, the 0730 alarm is listed as "Tomorrow". The Clock app lists the alarm correctly (although, if I rememebr correctly, there was previously a bug where the clock app would get this wrong too). The alarm functions correctly, but the indicator is unsettling. ** Affects: indicator-datetime (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Screenshot of indicator showing wrong day for alarm" https://bugs.launchpad.net/bugs/1549783/+attachment/4580805/+files/screenshot20160224_012251931.png -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-datetime in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1549783 Title: Indicator shows "Tomorrow" for an alarm happening today when checked after midnight Status in indicator-datetime package in Ubuntu: New Bug description: BQ E4.5 (krillin) running OTA9.1 I have 2 recurring alarms set for 0730 and 0800. If I pull down the clock indicator bar after midnight, the 0730 alarm is listed as "Tomorrow". The Clock app lists the alarm correctly (although, if I rememebr correctly, there was previously a bug where the clock app would get this wrong too). The alarm functions correctly, but the indicator is unsettling. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1549783/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
