[Dx-packages] [Bug 1170366] Re: Broken handling of All-Day events
Probably this bug: Bug #1293646 -- 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/1170366 Title: Broken handling of All-Day events Status in “indicator-datetime” package in Ubuntu: New Bug description: All-day events are not being shown on the day they occur, when that date is selected in the calendar, and all-day events which occur on Fridays seem to not be appearing at all. Furthermore, it also seems that all-day events which span multiple days are also handled poorly, listed as starting at 00:00 on the first day, and not appearing on the other days. In Online Services we have a few calendars for hours, meetings, and for the client engineering subteam we have review days, which we specify in a calendar. I have these calendars subscribed to in Evolution. The all-day events used to appear on the day they occurred, so this seems to be a regression. Some examples: All-day events; To see who is on call for reviews today, I must select the previous day. The event for Friday however, does not show up at all, so selecting Thursday dates on the calendar do not show me any future all-day events that occur on the Friday. Multi-day all-day event: I will be on holiday May 06-10, but this does not show correctly in the events list when I select any of those days. Instead, when I select the preceding Sunday May 05 in the calendar, the event shows as starting Monday at 00:00, rather than being an all- day event which spans multiple days. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: indicator-datetime 12.10.3daily13.03.26-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-18.28-generic 3.8.6 Uname: Linux 3.8.0-18-generic x86_64 ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 Date: Thu Apr 18 10:01:40 2013 InstallationDate: Installed on 2012-10-21 (178 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) MarkForUpload: True SourcePackage: indicator-datetime UpgradeStatus: Upgraded to raring on 2012-12-24 (114 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1170366/+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 1294580] Re: indicator-datetime-service panel clock freezes
Yeah, that's what I see in the strace log.
I think that the problem/symptom is that the poll just times out and
doesn't get data on the event-fd.
tail of indicator-datetime-service.strace.log:
11:00:28 eventfd2(0, O_NONBLOCK|O_CLOEXEC) = 22
11:00:28 write(22, \1\0\0\0\0\0\0\0, 8) = 8
11:00:28 write(6, \1\0\0\0\0\0\0\0, 8) = 8
11:00:28 futex(0xb580af10, FUTEX_WAKE_PRIVATE, 1) = 1
11:00:28 futex(0xb580ab08, FUTEX_WAKE_PRIVATE, 1) = 1
11:00:28 clock_gettime(CLOCK_MONOTONIC, {2931, 622027924}) = 0
11:00:28 futex(0xb5802f80, FUTEX_WAKE_PRIVATE, 1) = 1
11:00:28 clock_gettime(CLOCK_MONOTONIC, {2931, 622178855}) = 0
11:00:28 poll([{fd=22, events=POLLIN}], 1, 18) = 1 ([{fd=22,
revents=POLLIN}])
11:00:28 clock_gettime(CLOCK_MONOTONIC, {2931, 622230836}) = 0
11:00:28 clock_gettime(CLOCK_MONOTONIC, {2931, 622254879}) = 0
11:00:28 poll([{fd=22, events=POLLIN}], 1, 18) = 1 ([{fd=22,
revents=POLLIN}])
11:00:28 read(22, \1\0\0\0\0\0\0\0, 16) = 8
11:00:28 clock_gettime(CLOCK_MONOTONIC, {2931, 622328380}) = 0
11:00:28 clock_gettime(CLOCK_MONOTONIC, {2931, 622352161}) = 0
11:00:28 poll([{fd=22, events=POLLIN}], 1, 18 detached ...
and here just happens nothing, except a timeout after 18 miliseconds
(3 minutes). My guess is that there should have been a return with read
action on fd=22. Similar as earlier:
11:00:25 eventfd2(0, O_NONBLOCK|O_CLOEXEC) = 8
11:00:25 write(8, \1\0\0\0\0\0\0\0, 8) = 8
11:00:25 write(6, \1\0\0\0\0\0\0\0, 8) = 8
11:00:25 futex(0xb580af10, FUTEX_WAKE_PRIVATE, 1) = 1
11:00:25 futex(0xb580ab08, FUTEX_WAKE_PRIVATE, 1) = 1
11:00:25 clock_gettime(CLOCK_MONOTONIC, {2928, 426833813}) = 0
11:00:25 futex(0xb5802f80, FUTEX_WAKE_PRIVATE, 1) = 1
11:00:25 poll([{fd=8, events=POLLIN}], 1, 0) = 1 ([{fd=8, revents=POLLIN}])
11:00:25 write(6, \1\0\0\0\0\0\0\0, 8) = 8
11:00:25 futex(0xb580af10, FUTEX_WAKE_PRIVATE, 1) = 1
11:00:25 futex(0xb580ab08, FUTEX_WAKE_PRIVATE, 1) = 1
11:00:25 clock_gettime(CLOCK_MONOTONIC, {2928, 427817851}) = 0
11:00:25 futex(0xb5802f80, FUTEX_WAKE_PRIVATE, 1) = 1
11:00:25 poll([{fd=8, events=POLLIN}], 1, 0) = 1 ([{fd=8, revents=POLLIN}])
11:00:25 read(8, \3\0\0\0\0\0\0\0, 16) = 8
11:00:25 poll([{fd=8, events=POLLIN}], 1, 0) = 0 (Timeout)
11:00:25 read(8, 0xbfa5694c, 16)= -1 EAGAIN (Resource temporarily
unavailable)
11:00:25 write(8, \1\0\0\0\0\0\0\0, 8) = 8
11:00:25 close(8) = 0
11:00:25 eventfd2(0, O_NONBLOCK|O_CLOEXEC) = 8
11:00:25 write(8, \1\0\0\0\0\0\0\0, 8) = 8
11:00:25 write(6, \1\0\0\0\0\0\0\0, 8) = 8
11:00:25 futex(0xb580af10, FUTEX_WAKE_PRIVATE, 1) = 1
11:00:25 futex(0xb580ab08, FUTEX_WAKE_PRIVATE, 1) = 1
11:00:25 clock_gettime(CLOCK_MONOTONIC, {2928, 429068530}) = 0
11:00:25 futex(0xb5802f80, FUTEX_WAKE_PRIVATE, 1) = 1
11:00:25 clock_gettime(CLOCK_MONOTONIC, {2928, 429726382}) = 0
11:00:25 poll([{fd=8, events=POLLIN}], 1, 25000) = 1 ([{fd=8, revents=POLLIN}])
11:00:25 clock_gettime(CLOCK_MONOTONIC, {2928, 429874461}) = 0
11:00:25 clock_gettime(CLOCK_MONOTONIC, {2928, 429945589}) = 0
11:00:25 poll([{fd=8, events=POLLIN}], 1, 25000) = 1 ([{fd=8, revents=POLLIN}])
11:00:25 read(8, \1\0\0\0\0\0\0\0, 16) = 8
11:00:25 clock_gettime(CLOCK_MONOTONIC, {2928, 430235853}) = 0
11:00:25 clock_gettime(CLOCK_MONOTONIC, {2928, 430307703}) = 0
11:00:25 poll([{fd=8, events=POLLIN}], 1, 24999) = 1 ([{fd=8, revents=POLLIN}])
11:00:25 read(8, \1\0\0\0\0\0\0\0, 16) = 8
11:00:25 write(8, \1\0\0\0\0\0\0\0, 8) = 8
11:00:25 close(8) = 0
11:00:25 gettimeofday({1395223225, 139383}, NULL) = 0
11:00:25 write(6, \1\0\0\0\0\0\0\0, 8) = 8
I've no idea what this eventfd is, but I guess that is the pointer to the
problem.
--
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/1294580
Title:
indicator-datetime-service panel clock freezes
Status in “indicator-datetime” package in Ubuntu:
New
Bug description:
The clock in the panel freezes after running for (at least sometimes)
a few seconds.
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: indicator-datetime 13.10.0+14.04.20140314.1-0ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6
Uname: Linux 3.13.0-17-generic i686
ApportVersion: 2.13.3-0ubuntu1
Architecture: i386
CurrentDesktop: Unity
Date: Wed Mar 19 11:08:59 2014
ExecutablePath:
/usr/lib/i386-linux-gnu/indicator-datetime/indicator-datetime-service
InstallationDate: Installed on 2013-12-24 (84 days ago)
InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha i386 (20131224)
SourcePackage: indicator-datetime
UpgradeStatus: No upgrade log present (probably fresh install)
upstart.indicator-datetime.log: (process:6082): Indicator-Datetime-WARNING
**: AddressStart() failed:
GDBus.Error:org.freedesktop.Geoclue.Error.notAvailable: Geoclue master client
has no usable Address providers
To manage notifications about this bug go to:
[Dx-packages] [Bug 1289070] Re: Dash results do not report with Orca
*** This bug is a duplicate of bug 1066157 *** https://bugs.launchpad.net/bugs/1066157 ** This bug has been marked a duplicate of bug 1066157 dash +orca does not speak the names of application icons -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1289070 Title: Dash results do not report with Orca Status in “unity” package in Ubuntu: New Bug description: When using Gnome-orca the Dash has no accessibility with the edit field or the results. The catagories are read out though. Similar bugs are #1066157 and #843026 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140305-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-14.34-generic 3.13.5 Uname: Linux 3.13.0-14-generic x86_64 ApportVersion: 2.13.2-0ubuntu5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Fri Mar 7 11:12:25 2014 InstallationDate: Installed on 2014-03-01 (5 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140228) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1289070/+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 1295003] Re: Ubuntu does not honor “ignore-hosts” proxy settings for IPv6
** Package changed: ubuntu = d-conf (Ubuntu) -- You received this bug notification because you are a member of DX Packages, which is subscribed to d-conf in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1295003 Title: Ubuntu does not honor “ignore-hosts” proxy settings for IPv6 Status in “d-conf” package in Ubuntu: New Bug description: I just typed under dconf-editor, System → Proxy → ignore-hosts, the following content: ['localhost', '127.0.0.0/8', '::1', '192.168.0.1', '2000::/3', 'fc00::/8'] But, Google Chrome (and apt-get update / upgrade) is just ignoring this settings. Also, Firefox doesn't honor the `ingore-hosts` settings, even configuring it to Use system proxy settings. For example, my Proxy Server (Ubuntu with Squid3) is in dual-stacked mode BUT, I do NOT want to access IPv6 web sites through the Proxy, that's why I'm trying to ignore the entire IPv6 Internet with the entry 2000::/3 above, but, it does not work as expected. BTW, I don't need the proxy to access Hyperboria sites, which resides under fc00::/8 (local / private subnet) but, it doesn't work either... Why I'm doing this? Because my environment is already a IPv6-Only Network and, to access the old internet infrastructure (IPv4-Only), I need to go through the dual-stacked proxy. But I need the proxy only when a web site doesn't have IPv6... How can I know that it doesn't work?! It is simple, just access a web site that shows a IPv6 address on it, for example, http://www.sixxs.net or http://ipv6.whatismyv6.com, then, I'm still seeing the IPv6 address of the Proxy Server, so, ignore- hosts entry '2000::/3' doesn't seem to be working. Plus, when I'm trying to access a Hyperboria website, Squid returns an error that it can not reach `fc00::/8` network (Squid ERROR: (101) Network is unreachable) ...of course it can't, the cjdns router is running right on my Ubuntu Desktop, so, no need to go through proxy when browsing Hyperboria fc00::/8 but, Ubuntu isn't honoring ignore-hosts under proxy settings. Please guys, Linux is a O.S. built for networks! How can Ubuntu Proxy Setup be so simplistic?! And it doesn't even work! I already tried askubuntu.com but, no answer there, look: http://askubuntu.com/questions/435163/how-to-make-ubuntu-honor-ignore- hosts-proxy-settings-for-ipv6 I really appreciate any help! This is a serious problem. Thanks! Thiago To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/d-conf/+bug/1295003/+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 1295003] [NEW] Ubuntu does not honor “ignore-hosts” proxy settings for IPv6
You have been subscribed to a public bug: I just typed under dconf-editor, System → Proxy → ignore-hosts, the following content: ['localhost', '127.0.0.0/8', '::1', '192.168.0.1', '2000::/3', 'fc00::/8'] But, Google Chrome (and apt-get update / upgrade) is just ignoring this settings. Also, Firefox doesn't honor the `ingore-hosts` settings, even configuring it to Use system proxy settings. For example, my Proxy Server (Ubuntu with Squid3) is in dual-stacked mode BUT, I do NOT want to access IPv6 web sites through the Proxy, that's why I'm trying to ignore the entire IPv6 Internet with the entry 2000::/3 above, but, it does not work as expected. BTW, I don't need the proxy to access Hyperboria sites, which resides under fc00::/8 (local / private subnet) but, it doesn't work either... Why I'm doing this? Because my environment is already a IPv6-Only Network and, to access the old internet infrastructure (IPv4-Only), I need to go through the dual- stacked proxy. But I need the proxy only when a web site doesn't have IPv6... How can I know that it doesn't work?! It is simple, just access a web site that shows a IPv6 address on it, for example, http://www.sixxs.net or http://ipv6.whatismyv6.com, then, I'm still seeing the IPv6 address of the Proxy Server, so, ignore-hosts entry '2000::/3' doesn't seem to be working. Plus, when I'm trying to access a Hyperboria website, Squid returns an error that it can not reach `fc00::/8` network (Squid ERROR: (101) Network is unreachable) ...of course it can't, the cjdns router is running right on my Ubuntu Desktop, so, no need to go through proxy when browsing Hyperboria fc00::/8 but, Ubuntu isn't honoring ignore-hosts under proxy settings. Please guys, Linux is a O.S. built for networks! How can Ubuntu Proxy Setup be so simplistic?! And it doesn't even work! I already tried askubuntu.com but, no answer there, look: http://askubuntu.com/questions/435163/how-to-make-ubuntu-honor-ignore- hosts-proxy-settings-for-ipv6 I really appreciate any help! This is a serious problem. Thanks! Thiago ** Affects: d-conf (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- Ubuntu does not honor “ignore-hosts” proxy settings for IPv6 https://bugs.launchpad.net/bugs/1295003 You received this bug notification because you are a member of DX Packages, which is subscribed to d-conf in Ubuntu. -- 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 1278720] Re: Libreoffice HUD entries are unresponsive
This got fixed along with a couple of other apps (see LP: #1288025) ** Changed in: hud Status: New = Fix Released ** Changed in: hud (Ubuntu) Status: Confirmed = Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to hud in Ubuntu. https://bugs.launchpad.net/bugs/1278720 Title: Libreoffice HUD entries are unresponsive Status in Unity HUD: Fix Released Status in “hud” package in Ubuntu: Fix Released Bug description: On libreoffice, if I press Enter/click on a HUD entry nothing happens. I tried with Impress and Writer, the menu entries are shown alright, but when I activate them nothing happens. (Not sure if the bug is really on the HUD.) In case it matters, after installing Trusty, I removed libreoffice. It was recently that I reinstalled it via the ubuntu-desktop metapackage. libreoffice: Installed: 1:4.2.0~rc4-0ubuntu1 Candidate: 1:4.2.0~rc4-0ubuntu1 Version table: *** 1:4.2.0~rc4-0ubuntu1 0 500 http://do.archive.ubuntu.com/ubuntu/ trusty/universe i386 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: hud 13.10.1+14.04.20140206-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-8.27-generic 3.13.2 Uname: Linux 3.13.0-8-generic i686 ApportVersion: 2.13.2-0ubuntu2 Architecture: i386 CurrentDesktop: Unity Date: Tue Feb 11 02:02:16 2014 InstallationDate: Installed on 2014-01-14 (27 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha i386 (20140113) SourcePackage: hud UpgradeStatus: No upgrade log present (probably fresh install) upstart.window-stack-bridge.log: QDBusConnection: name 'org.ayatana.bamf' had owner '' but we thought it was ':1.5' To manage notifications about this bug go to: https://bugs.launchpad.net/hud/+bug/1278720/+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 915265] Re: [regression] Unity launcher on-screen corruption on resume from suspend with nVidia proprietary driver
They are really two separate issue which, nonetheless, we're tracking in LP: #1210077, and I think it makes sense to do so because the code to handle resume is already in place in Unity (which is what this bug report was about). It is true that one issue was in the nvidia driver (now fixed), however the other issue is in Unity. The latter, though, is really Upower not emitting the event on resume. This is why I suggested that we rely on Logind instead. -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/915265 Title: [regression] Unity launcher on-screen corruption on resume from suspend with nVidia proprietary driver Status in OEM Priority Project: Fix Released Status in OEM Priority Project oneiric series: Won't Fix Status in OEM Priority Project precise series: Fix Released Status in Unity: Fix Released Status in Unity 6.0 series: Fix Released Status in Unity Distro Priority: Fix Released Status in “unity” package in Ubuntu: Fix Released Status in “unity” source package in Oneiric: Won't Fix Status in “unity” source package in Precise: Fix Released Bug description: [Impact] This bug basically makes NVidia machines unusable after suspend. This is causing problems for users and OEMs that want to use 11.10 alike. [Development Fix] https://bazaar.launchpad.net/~unity-team/unity/trunk/revision/2205 [Test Case] . To reproduce: 1) Suspend 2) Resume 2a) login, if necessary. Note that the login screen (lightdm) displays properly 3) Notice the corrupted launcher 4) Mouse over the launcher; the launcher redraws and the corruption goes away [Regression Potential] Low. We have tested the fix in the development version that we're planning on releasing in April 26th and have found no problems. With the big diff, the regression potential might be a bit bigger for precise. == Original Report == The unity launcher is reliably corrupted upon resume from suspend with some (all?) NVidia hardware with the proprietary NVidia driver. All other visual elements seem to draw correctly, it's just the unity launcher that has this problem. The launcher looks fine after it redraws (for example, if you mouse over it). The problem is not reproducible on Intel or AMD graphics hardware, and I'm told (by Ted Gould) that it doesn't affect the nouveau driver. I have not tested the nouveau driver myself. This problem been reported several times in the comments of bug 676166, I'm filing this separate bug for clarity since 676166 is overloaded. To reproduce: 1) Suspend 2) Resume 2a) login, if necessary. Note that the login screen (lightdm) displays properly 3) Notice the corrupted launcher 4) Mouse over the launcher; the launcher redraws and the corruption goes away The problem affects 11.10, and is not fixed by upgrading to more recent unity, compiz, or nvidia drivers from oneiric-updates or even the most recent SRU candidates not yet in oneiric-proposed. Currently I have the following installed and the problem still exists: ii nvidia-common 1:0.2.35.1 Find obsolete NVIDIA drivers ii nvidia-current280.13-0ubuntu6 NVIDIA binary Xorg driver, kernel module and VDPAU library ii nvidia-current-updates285.05.09-0ubuntu0.1 NVIDIA binary Xorg driver, kernel module and VDPAU library ii nvidia-settings 280.13-0ubuntu2.1 Tool of configuring the NVIDIA graphics driver ii nvidia-settings-updates 285.05.09-0ubuntu0.1 Tool of configuring the NVIDIA graphics driver Unity SRU candidate (not yet in -proposed): ii unity 4.28.0-0ubuntu1~ppa1 Interface designed for efficiency of space and interaction. Compiz SRU candidate (not yet in -proposed): ii compiz 1:0.9.6+bzr20110929-0ubuntu6.1~oneiric1OpenGL window and compositing manager ii compiz-core 1:0.9.6+bzr20110929-0ubuntu6.1~oneiric1OpenGL window and compositing manager Hardware is a MacbookPro 3,1 w/ NVidia 8600M GT. I'm using the amd64 build of 11.10. lspci -vvnn output for graphics card: 01:00.0 VGA compatible controller [0300]: nVidia Corporation G84 [GeForce 8600M GT] [10de:0407] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Apple Computer Inc. Device [106b:00a0] Physical Slot: 1 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0 Interrupt: pin A routed to IRQ
[Dx-packages] [Bug 1294545] Re: unity-panel-service crashed with SIGSEGV in window_menu_get_entries()
** Branch linked: lp:ubuntu/trusty-proposed/indicator-appmenu -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-appmenu in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1294545 Title: unity-panel-service crashed with SIGSEGV in window_menu_get_entries() Status in “indicator-appmenu” package in Ubuntu: Triaged Bug description: crash occurred immediately after the unlock screen ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: indicator-appmenu 13.01.0+14.04.20140318-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-18.38-generic 3.13.6 Uname: Linux 3.13.0-18-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.13.3-0ubuntu1 Architecture: i386 CurrentDesktop: Unity Date: Wed Mar 19 12:49:30 2014 ExecutablePath: /usr/lib/unity/unity-panel-service InstallationDate: Installed on 2014-02-04 (42 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha i386 (20140203) ProcCmdline: /usr/lib/unity/unity-panel-service SegvAnalysis: Segfault happened at: 0xb57208f9 window_menu_get_entries+9:mov 0x44(%eax),%eax PC (0xb57208f9) ok source 0x44(%eax) (0x0044) not located in a known VMA region (needed readable region)! destination %eax ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: indicator-appmenu StacktraceTop: window_menu_get_entries () from /usr/lib/indicators3/7/libappmenu.so ?? () from /usr/lib/indicators3/7/libappmenu.so ?? () from /usr/lib/i386-linux-gnu/libindicator3.so.7 indicator_object_set_visible () from /usr/lib/i386-linux-gnu/libindicator3.so.7 ?? () from /usr/lib/indicators3/7/libappmenu.so Title: unity-panel-service crashed with SIGSEGV in window_menu_get_entries() 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/indicator-appmenu/+bug/1294545/+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
Re: [Dx-packages] [Bug 915265] Re: [regression] Unity launcher on-screen corruption on resume from suspend with nVidia proprietary driver
Those interfaces were removed from upstream upower so relying on them is probably not the best idea now. Thanks ZK On Thu, Mar 20, 2014 at 11:00 AM, Alberto Milone alberto.mil...@canonical.com wrote: They are really two separate issue which, nonetheless, we're tracking in LP: #1210077, and I think it makes sense to do so because the code to handle resume is already in place in Unity (which is what this bug report was about). It is true that one issue was in the nvidia driver (now fixed), however the other issue is in Unity. The latter, though, is really Upower not emitting the event on resume. This is why I suggested that we rely on Logind instead. -- You received this bug notification because you are a member of Canonical Hardware Enablement Team, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/915265 Title: [regression] Unity launcher on-screen corruption on resume from suspend with nVidia proprietary driver To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/915265/+subscriptions -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/915265 Title: [regression] Unity launcher on-screen corruption on resume from suspend with nVidia proprietary driver Status in OEM Priority Project: Fix Released Status in OEM Priority Project oneiric series: Won't Fix Status in OEM Priority Project precise series: Fix Released Status in Unity: Fix Released Status in Unity 6.0 series: Fix Released Status in Unity Distro Priority: Fix Released Status in “unity” package in Ubuntu: Fix Released Status in “unity” source package in Oneiric: Won't Fix Status in “unity” source package in Precise: Fix Released Bug description: [Impact] This bug basically makes NVidia machines unusable after suspend. This is causing problems for users and OEMs that want to use 11.10 alike. [Development Fix] https://bazaar.launchpad.net/~unity-team/unity/trunk/revision/2205 [Test Case] . To reproduce: 1) Suspend 2) Resume 2a) login, if necessary. Note that the login screen (lightdm) displays properly 3) Notice the corrupted launcher 4) Mouse over the launcher; the launcher redraws and the corruption goes away [Regression Potential] Low. We have tested the fix in the development version that we're planning on releasing in April 26th and have found no problems. With the big diff, the regression potential might be a bit bigger for precise. == Original Report == The unity launcher is reliably corrupted upon resume from suspend with some (all?) NVidia hardware with the proprietary NVidia driver. All other visual elements seem to draw correctly, it's just the unity launcher that has this problem. The launcher looks fine after it redraws (for example, if you mouse over it). The problem is not reproducible on Intel or AMD graphics hardware, and I'm told (by Ted Gould) that it doesn't affect the nouveau driver. I have not tested the nouveau driver myself. This problem been reported several times in the comments of bug 676166, I'm filing this separate bug for clarity since 676166 is overloaded. To reproduce: 1) Suspend 2) Resume 2a) login, if necessary. Note that the login screen (lightdm) displays properly 3) Notice the corrupted launcher 4) Mouse over the launcher; the launcher redraws and the corruption goes away The problem affects 11.10, and is not fixed by upgrading to more recent unity, compiz, or nvidia drivers from oneiric-updates or even the most recent SRU candidates not yet in oneiric-proposed. Currently I have the following installed and the problem still exists: ii nvidia-common 1:0.2.35.1 Find obsolete NVIDIA drivers ii nvidia-current280.13-0ubuntu6 NVIDIA binary Xorg driver, kernel module and VDPAU library ii nvidia-current-updates285.05.09-0ubuntu0.1 NVIDIA binary Xorg driver, kernel module and VDPAU library ii nvidia-settings 280.13-0ubuntu2.1 Tool of configuring the NVIDIA graphics driver ii nvidia-settings-updates 285.05.09-0ubuntu0.1 Tool of configuring the NVIDIA graphics driver Unity SRU candidate (not yet in -proposed): ii unity 4.28.0-0ubuntu1~ppa1 Interface designed for efficiency of space and interaction. Compiz SRU candidate (not yet in -proposed): ii compiz 1:0.9.6+bzr20110929-0ubuntu6.1~oneiric1OpenGL window and compositing manager ii compiz-core 1:0.9.6+bzr20110929-0ubuntu6.1~oneiric1
[Dx-packages] [Bug 1293163] Re: When Allow louder than 100% is checked, sound volume NotifyOSD shows the gauge only up to 100%
** Branch linked: lp:ubuntu/trusty-proposed/indicator-sound -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-sound in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1293163 Title: When Allow louder than 100% is checked, sound volume NotifyOSD shows the gauge only up to 100% Status in Sound Menu: In Progress Status in “indicator-sound” package in Ubuntu: Fix Released Bug description: When Allow louder than 100% box is checked in sound system settings, change of the sound volume by the mouse wheel over the sound indicator leads to the gauge in the NotifyOSD showing the volume level only up to 100%. That is, the maximum value of the gauge in the NotifyOSD corresponds to 100% and further change of the volume louder than 100% does not modify the gauge state. At the same time, the gauge in the sound indicator drop-down menu shows the volume correctly, i.e. the maximum value of the gauge in the drop-down corresponds to the actual maximum volume louder than 100% and 100% is somewhere in the middle. The same behaviour is expected for the gauge in the NotifyOSD. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: indicator-sound 12.10.2+14.04.20140313-0ubuntu1 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: Unity Date: Sun Mar 16 20:15:28 2014 InstallationDate: Installed on 2014-01-27 (48 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140124) SourcePackage: indicator-sound UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-sound/+bug/1293163/+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 1284840] Re: incorrect use of g_object_disconnect() in applet-main.c's entry_removed()
** Branch linked: lp:ubuntu/trusty-proposed/indicator-applet -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-applet in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1284840 Title: incorrect use of g_object_disconnect() in applet-main.c's entry_removed() Status in Indicator Applet: In Progress Status in “indicator-applet” package in Ubuntu: Fix Released Bug description: Introduced in http://bazaar.launchpad.net/~indicator-applet-developers /indicator-applet/trunk.14.04/revision/402.1.1 and reported by Alberts Muktupāvels (albertsmuktupavels) in a comment at https://code.launchpad.net/~mitya57/indicator-applet/unparent- label/+merge/208174/comments/488891 g_object_connect() and g_object_disconnect() have different signal_spec semantics, but applet-main.c is treating them identically. Low priority, but easy fix: use g_object_disconnect()'s any-signal catchall. To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-applet/+bug/1284840/+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 1284840] Re: incorrect use of g_object_disconnect() in applet-main.c's entry_removed()
This bug was fixed in the package indicator-applet - 12.10.2+14.04.20140320-0ubuntu1 --- indicator-applet (12.10.2+14.04.20140320-0ubuntu1) trusty; urgency=low [ Charles Kerr ] * Use the correct signal_spec syntax when calling g_object_disconnect(). (LP: #1284840) [ Dmitry Shachnev ] * Allow Gtk deprecations, to workaround FTBFS. -- Ubuntu daily release ps-jenk...@lists.canonical.com Thu, 20 Mar 2014 09:03:53 + ** Changed in: indicator-applet (Ubuntu) Status: New = Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-applet in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1284840 Title: incorrect use of g_object_disconnect() in applet-main.c's entry_removed() Status in Indicator Applet: In Progress Status in “indicator-applet” package in Ubuntu: Fix Released Bug description: Introduced in http://bazaar.launchpad.net/~indicator-applet-developers /indicator-applet/trunk.14.04/revision/402.1.1 and reported by Alberts Muktupāvels (albertsmuktupavels) in a comment at https://code.launchpad.net/~mitya57/indicator-applet/unparent- label/+merge/208174/comments/488891 g_object_connect() and g_object_disconnect() have different signal_spec semantics, but applet-main.c is treating them identically. Low priority, but easy fix: use g_object_disconnect()'s any-signal catchall. To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-applet/+bug/1284840/+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 1294545] Re: unity-panel-service crashed with SIGSEGV in window_menu_get_entries()
This bug was fixed in the package indicator-appmenu - 13.01.0+14.04.20140320-0ubuntu1 --- indicator-appmenu (13.01.0+14.04.20140320-0ubuntu1) trusty; urgency=low [ Charles Kerr ] * Don't dereference a NULL WindowMenu pointer. (LP: #1294545) -- Ubuntu daily release ps-jenk...@lists.canonical.com Thu, 20 Mar 2014 09:03:45 + ** Changed in: indicator-appmenu (Ubuntu) Status: Triaged = Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-appmenu in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1294545 Title: unity-panel-service crashed with SIGSEGV in window_menu_get_entries() Status in “indicator-appmenu” package in Ubuntu: Fix Released Bug description: crash occurred immediately after the unlock screen ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: indicator-appmenu 13.01.0+14.04.20140318-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-18.38-generic 3.13.6 Uname: Linux 3.13.0-18-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.13.3-0ubuntu1 Architecture: i386 CurrentDesktop: Unity Date: Wed Mar 19 12:49:30 2014 ExecutablePath: /usr/lib/unity/unity-panel-service InstallationDate: Installed on 2014-02-04 (42 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha i386 (20140203) ProcCmdline: /usr/lib/unity/unity-panel-service SegvAnalysis: Segfault happened at: 0xb57208f9 window_menu_get_entries+9:mov 0x44(%eax),%eax PC (0xb57208f9) ok source 0x44(%eax) (0x0044) not located in a known VMA region (needed readable region)! destination %eax ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: indicator-appmenu StacktraceTop: window_menu_get_entries () from /usr/lib/indicators3/7/libappmenu.so ?? () from /usr/lib/indicators3/7/libappmenu.so ?? () from /usr/lib/i386-linux-gnu/libindicator3.so.7 indicator_object_set_visible () from /usr/lib/i386-linux-gnu/libindicator3.so.7 ?? () from /usr/lib/indicators3/7/libappmenu.so Title: unity-panel-service crashed with SIGSEGV in window_menu_get_entries() 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/indicator-appmenu/+bug/1294545/+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 1293163] Re: When Allow louder than 100% is checked, sound volume NotifyOSD shows the gauge only up to 100%
This bug was fixed in the package indicator-sound - 12.10.2+14.04.20140320-0ubuntu1 --- indicator-sound (12.10.2+14.04.20140320-0ubuntu1) trusty; urgency=low [ Lars Uebernickel ] * Scale volume in notifications when allow-amplified-volume is set (LP: #1293163) * Use audio-volume-mute-blocking-panel instead of *-blocked-panel -- Ubuntu daily release ps-jenk...@lists.canonical.com Thu, 20 Mar 2014 08:58:30 + ** Changed in: indicator-sound (Ubuntu) Status: Confirmed = Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-sound in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1293163 Title: When Allow louder than 100% is checked, sound volume NotifyOSD shows the gauge only up to 100% Status in Sound Menu: In Progress Status in “indicator-sound” package in Ubuntu: Fix Released Bug description: When Allow louder than 100% box is checked in sound system settings, change of the sound volume by the mouse wheel over the sound indicator leads to the gauge in the NotifyOSD showing the volume level only up to 100%. That is, the maximum value of the gauge in the NotifyOSD corresponds to 100% and further change of the volume louder than 100% does not modify the gauge state. At the same time, the gauge in the sound indicator drop-down menu shows the volume correctly, i.e. the maximum value of the gauge in the drop-down corresponds to the actual maximum volume louder than 100% and 100% is somewhere in the middle. The same behaviour is expected for the gauge in the NotifyOSD. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: indicator-sound 12.10.2+14.04.20140313-0ubuntu1 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: Unity Date: Sun Mar 16 20:15:28 2014 InstallationDate: Installed on 2014-01-27 (48 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140124) SourcePackage: indicator-sound UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-sound/+bug/1293163/+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 1295065] Re: compiz crashed with SIGSEGV
*** This bug is a duplicate of bug 931389 *** https://bugs.launchpad.net/bugs/931389 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 #931389, 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/1295065/+attachment/4033628/+files/CoreDump.gz ** Attachment removed: Disassembly.txt https://bugs.launchpad.net/bugs/1295065/+attachment/4033630/+files/Disassembly.txt ** Attachment removed: ProcMaps.txt https://bugs.launchpad.net/bugs/1295065/+attachment/4033632/+files/ProcMaps.txt ** Attachment removed: ProcStatus.txt https://bugs.launchpad.net/bugs/1295065/+attachment/4033633/+files/ProcStatus.txt ** Attachment removed: Registers.txt https://bugs.launchpad.net/bugs/1295065/+attachment/4033634/+files/Registers.txt ** Attachment removed: Stacktrace.txt https://bugs.launchpad.net/bugs/1295065/+attachment/4033635/+files/Stacktrace.txt ** Attachment removed: ThreadStacktrace.txt https://bugs.launchpad.net/bugs/1295065/+attachment/4033636/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 931389 compiz crashed with SIGSEGV in af_latin_hints_compute_segments() ** 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 unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1295065 Title: compiz crashed with SIGSEGV Status in “unity” package in Ubuntu: New Bug description: On startup. Only change to system is new drives fitted. A symptom seems to be that the font used inside nautilus, and for launcher tooltips plus the clock in the menu bar, is *tiny* and not configurable through any of the font settings. ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140318-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-18.38-generic 3.13.6 Uname: Linux 3.13.0-18-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CrashCounter: 1 CurrentDesktop: Unity Date: Thu Mar 20 10:07:15 2014 ExecutablePath: /usr/bin/compiz InstallationDate: Installed on 2014-03-14 (5 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140314) ProcCmdline: compiz SegvAnalysis: Segfault happened at: 0x7fb48b558f8a:mov0x38(%rcx),%rdi PC (0x7fb48b558f8a) ok source 0x38(%rcx) (0x0038) not located in a known VMA region (needed readable region)! destination %rdi ok Stack memory exhausted (SP below stack segment) SegvReason: reading NULL VMA Signal: 11 SourcePackage: unity StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libfreetype.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libfreetype.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libfreetype.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libfreetype.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libfreetype.so.6 Title: compiz crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1295065/+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 1244205] Re: cupsd wakes up the hard disk every 14 minutes
Mike, thanks for the detailed comment.
Sorry about the off-hand remark. What I meant by get on the bus
properly is for CUPS to be on D-Bus all the time, not only when an
event happens and a subscription exists. I think the subscription-based
system is overkill for desktop notifications and makes our indicators,
settings pages, and print-dialogs needlessly complicated.
I'm glad to hear that we seem to be on the same page about that and that
it's similar to what you're doing on OSX already.
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-printers in Ubuntu.
https://bugs.launchpad.net/bugs/1244205
Title:
cupsd wakes up the hard disk every 14 minutes
Status in The Ubuntu Power Consumption Project:
New
Status in “cups” package in Ubuntu:
Won't Fix
Status in “indicator-printers” package in Ubuntu:
Fix Released
Bug description:
cupsd calls fsync() on /etc/subscriptions.conf.N every 14~15 minutes.
This causes the hard disk to wake up soon after it spins down.
Subscription renewal is from indicator-printers every 15 minutes.
I think we don't need cupsdRemoveFile() to always overwrite data and do a
fsync() for this file. Currently only Precise is confirmed to be affected.
Saucy seems not having the same issue according to
(http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/saucy/cups/saucy/view/head:/scheduler/file.c#L149)
block_dump from the kernel
7[19935.646436] cupsd(1066): dirtied inode 15336755 (subscriptions.conf.N)
on sda3
7[19935.646673] cupsd(1066): WRITE block 352753016 on sda3 (8 sectors)
7[19935.646755] cupsd(1066): dirtied inode 15335603 (?) on sda3
7[19935.646763] cupsd(1066): dirtied inode 15335603 (?) on sda3
7[19935.646776] cupsd(1066): WRITE block 352701128 on sda3 (8 sectors)
7[20774.607856] cupsd(1066): dirtied inode 15335603 (subscriptions.conf.N)
on sda3
7[20774.608034] cupsd(1066): WRITE block 352862776 on sda3 (8 sectors)
7[20774.608113] cupsd(1066): dirtied inode 15335607 (?) on sda3
7[20774.608120] cupsd(1066): dirtied inode 15335607 (?) on sda3
7[20774.608133] cupsd(1066): WRITE block 352753008 on sda3 (8 sectors)
7[21613.569033] cupsd(1066): dirtied inode 15335607 (subscriptions.conf.N)
on sda3
7[21613.569257] cupsd(1066): WRITE block 352753024 on sda3 (8 sectors)
7[21613.569345] cupsd(1066): dirtied inode 15336755 (?) on sda3
7[21613.569353] cupsd(1066): dirtied inode 15336755 (?) on sda3
7[21613.569367] cupsd(1066): WRITE block 352753016 on sda3 (8 sectors)
cups: scheduler/file.c
int /* O - 0 on success, -1 on error */
cupsdCloseCreatedConfFile(
cups_file_t *fp, /* I - File to close */
const char *filename)/* I - Filename */
{
...
snprintf(newfile, sizeof(newfile), %s.N, filename);
snprintf(oldfile, sizeof(oldfile), %s.O, filename);
if ((cupsdRemoveFile(oldfile) errno != ENOENT) ||
(rename(filename, oldfile) errno != ENOENT) ||
rename(newfile, filename))
{
cupsdLogMessage(CUPSD_LOG_ERROR, Unable to finalize \%s\: %s,
filename, strerror(errno));
return (-1);
}
return (0);
}
int /* O - 0 on success, -1 on error */
cupsdRemoveFile(const char *filename) /* I - File to remove */
{
...
/*
* Overwrite the file 7 times with 0xF6, 0x00, 0xFF, random, 0x00, 0xFF,
* and more random data.
*/
memset(buffer, 0xF6, sizeof(buffer));
if (overwrite_data(fd, buffer, sizeof(buffer), (int)info.st_size))
{
close(fd);
return (-1);
}
...
}
static int/* O - 0 on success, -1 on error */
overwrite_data(intfd, /* I - File descriptor */
const char *buffer,/* I - Buffer to write */
intbufsize, /* I - Size of buffer */
intfilesize) /* I - Size of file */
{
int bytes; /* Bytes to write/written */
/*
* Start at the beginning of the file...
*/
if (lseek(fd, 0, SEEK_SET) 0)
return (-1);
/*
* Fill the file with the provided data...
*/
while (filesize 0)
{
if (filesize bufsize)
bytes = bufsize;
else
bytes = filesize;
if ((bytes = write(fd, buffer, bytes)) 0)
return (-1);
filesize -= bytes;
}
/*
* Force the changes to disk...
*/
return (fsync(fd));
}
indicator-printers-service.c
#define NOTIFY_LEASE_DURATION (15 * 60)
int main (int argc, char *argv[])
{
...
g_timeout_add_seconds (NOTIFY_LEASE_DURATION - 60,
renew_subscription_timeout,
subscription_id);
...
}
To manage notifications about this bug go to:
[Dx-packages] [Bug 1274669] Re: scope-runner-dbus.py crashed with signal 5 in g_variant_new_va()
** Changed in: libunity (Ubuntu) Importance: Medium = High -- 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/1274669 Title: scope-runner-dbus.py crashed with signal 5 in g_variant_new_va() Status in Unity Manpages Scope: Confirmed Status in “libunity” package in Ubuntu: Confirmed Bug description: Typed disks in the dash and the crash occured shortly after opening disks. ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: unity-scopes-runner 7.1.3+14.04.20131106-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7 Uname: Linux 3.11.0-14-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.13.2-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Thu Jan 30 21:20:26 2014 Dependencies: ExecutablePath: /usr/share/unity-scopes/scope-runner-dbus.py InstallationDate: Installed on 2013-08-30 (153 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) InterpreterPath: /usr/bin/python3.3 PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/share/unity-scopes/scope-runner-dbus.py -s code/manpages.scope Signal: 5 SourcePackage: libunity StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_variant_new_va () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_variant_builder_add () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: scope-runner-dbus.py crashed with signal 5 in g_variant_new_va() UpgradeStatus: Upgraded to trusty on 2014-01-30 (0 days ago) UserGroups: adm cdrom dip lp lpadmin plugdev sambashare sudo vboxusers www-data To manage notifications about this bug go to: https://bugs.launchpad.net/unity-scope-manpages/+bug/1274669/+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 1274669] Re: scope-runner-dbus.py crashed with signal 5 in g_variant_new_va()
** Changed in: unity-scope-manpages Assignee: (unassigned) = David Callé (davidc3) ** Changed in: unity-scope-manpages Importance: Undecided = High ** Changed in: unity-scope-manpages Status: New = Confirmed -- 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/1274669 Title: scope-runner-dbus.py crashed with signal 5 in g_variant_new_va() Status in Unity Manpages Scope: Confirmed Status in “libunity” package in Ubuntu: Confirmed Bug description: Typed disks in the dash and the crash occured shortly after opening disks. ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: unity-scopes-runner 7.1.3+14.04.20131106-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7 Uname: Linux 3.11.0-14-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.13.2-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Thu Jan 30 21:20:26 2014 Dependencies: ExecutablePath: /usr/share/unity-scopes/scope-runner-dbus.py InstallationDate: Installed on 2013-08-30 (153 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) InterpreterPath: /usr/bin/python3.3 PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/share/unity-scopes/scope-runner-dbus.py -s code/manpages.scope Signal: 5 SourcePackage: libunity StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_variant_new_va () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_variant_builder_add () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: scope-runner-dbus.py crashed with signal 5 in g_variant_new_va() UpgradeStatus: Upgraded to trusty on 2014-01-30 (0 days ago) UserGroups: adm cdrom dip lp lpadmin plugdev sambashare sudo vboxusers www-data To manage notifications about this bug go to: https://bugs.launchpad.net/unity-scope-manpages/+bug/1274669/+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 1295106] [NEW] Webapps open a new chromium icon in the panel when launched
Public bug reported: Check the screenshot for easier understanding of the problem: There is 1 chromium icon (the regular one) and other 2 extra icons that spawn when launching the google calendar and grooveshark also shown in the screenshot. As an extra, this later two, don't receive any application pip. In general, it behaves like the already fixed, bug #1059475. So it is probably a regression. Maybe in bamf? ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity-webapps-service 2.5.0~+14.04.20140317.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-18.38-generic 3.13.6 Uname: Linux 3.13.0-18-generic x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Thu Mar 20 20:40:12 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2012-11-25 (480 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Alpha amd64 (20120627) SourcePackage: libunity-webapps UpgradeStatus: Upgraded to trusty on 2013-10-23 (148 days ago) ** Affects: libunity-webapps (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty ** Attachment added: Screenshot from 2014-03-20 20:44:19.png https://bugs.launchpad.net/bugs/1295106/+attachment/4033778/+files/Screenshot%20from%202014-03-20%2020%3A44%3A19.png ** Description changed: - I think that this has happened before, so probably a regression. Maybe - in bamf? - Check the screenshot for easier understanding of the problem: There is 1 chromium icon (the regular one) and other 2 extra icons that spawn when launching the google calendar and grooveshark also shown in the screenshot. As an extra, this later two, don't receive any application pip. + + In general, it behaves like the already fixed, bug #1059475. So it is + probably a regression. Maybe in bamf? ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity-webapps-service 2.5.0~+14.04.20140317.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-18.38-generic 3.13.6 Uname: Linux 3.13.0-18-generic x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Thu Mar 20 20:40:12 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2012-11-25 (480 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Alpha amd64 (20120627) SourcePackage: libunity-webapps UpgradeStatus: Upgraded to trusty on 2013-10-23 (148 days ago) -- You received this bug notification because you are a member of DX Packages, which is subscribed to libunity-webapps in Ubuntu. https://bugs.launchpad.net/bugs/1295106 Title: Webapps open a new chromium icon in the panel when launched Status in “libunity-webapps” package in Ubuntu: New Bug description: Check the screenshot for easier understanding of the problem: There is 1 chromium icon (the regular one) and other 2 extra icons that spawn when launching the google calendar and grooveshark also shown in the screenshot. As an extra, this later two, don't receive any application pip. In general, it behaves like the already fixed, bug #1059475. So it is probably a regression. Maybe in bamf? ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity-webapps-service 2.5.0~+14.04.20140317.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-18.38-generic 3.13.6 Uname: Linux 3.13.0-18-generic x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Thu Mar 20 20:40:12 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2012-11-25 (480 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Alpha amd64 (20120627) SourcePackage: libunity-webapps UpgradeStatus: Upgraded to trusty on 2013-10-23 (148 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libunity-webapps/+bug/1295106/+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 1294647] Re: laptop keeps turning off even with 70 % of battery,
indicator-power only shows the power remaining; the actual shutdown is done by gnome-settings-daemon's power-manager plugin. However, it's doing it in response to what it's told the power charge is by upower, so I suspect that's going to be a more useful place to report this issue if it is software-related. To be clear, you're getting this without any laptop battery critically low type messages? Could you attach the output of upower --dump from before the laptop shuts down? ** Package changed: indicator-power (Ubuntu) = upower (Ubuntu) -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-power in Ubuntu. https://bugs.launchpad.net/bugs/1294647 Title: laptop keeps turning off even with 70 % of battery, Status in “upower” package in Ubuntu: New Bug description: the laptop turns off automatically without any warning. When again switched on, it shows the right amount of power reamining but again starts draining quickly and turns off in about 10 mins. Again when switched on it has the right amnt of battery left. The battery is fine as it works well with windows and gives around 2.5 hrs .I am running 13.10, upgraded fron 12.10. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1294647/+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 1295122] [NEW] Alarms not going off reliably on recent touch images
Public bug reported: Alarms are not reliable on recent images on touch. Popey: See's the alarm notification but not hears no sound. davmor2: I see and hear the alarm and notification if the device is awake if the screen is blank though I sometimes get an alarm 2 minutes Plus after the alarm was meant to go off other times I neither see nor hear the alarm. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: indicator-datetime 13.10.0+14.04.20140314.1-0ubuntu1 Uname: Linux 3.4.0-5-mako armv7l ApportVersion: 2.13.3-0ubuntu1 Architecture: armhf Date: Thu Mar 20 13:12:36 2014 InstallationDate: Installed on 2014-03-20 (0 days ago) InstallationMedia: Ubuntu Trusty Tahr (development branch) - armhf (20140320) ProcEnviron: TERM=linux PATH=(custom, no user) SourcePackage: indicator-datetime UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: indicator-datetime (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug armhf mako r248 trusty ** Tags added: mako r248 -- 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/1295122 Title: Alarms not going off reliably on recent touch images Status in “indicator-datetime” package in Ubuntu: New Bug description: Alarms are not reliable on recent images on touch. Popey: See's the alarm notification but not hears no sound. davmor2: I see and hear the alarm and notification if the device is awake if the screen is blank though I sometimes get an alarm 2 minutes Plus after the alarm was meant to go off other times I neither see nor hear the alarm. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: indicator-datetime 13.10.0+14.04.20140314.1-0ubuntu1 Uname: Linux 3.4.0-5-mako armv7l ApportVersion: 2.13.3-0ubuntu1 Architecture: armhf Date: Thu Mar 20 13:12:36 2014 InstallationDate: Installed on 2014-03-20 (0 days ago) InstallationMedia: Ubuntu Trusty Tahr (development branch) - armhf (20140320) ProcEnviron: TERM=linux PATH=(custom, no user) SourcePackage: indicator-datetime UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1295122/+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 1284840] Re: incorrect use of g_object_disconnect() in applet-main.c's entry_removed()
** Changed in: indicator-applet Status: In Progress = Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-applet in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1284840 Title: incorrect use of g_object_disconnect() in applet-main.c's entry_removed() Status in Indicator Applet: Fix Released Status in “indicator-applet” package in Ubuntu: Fix Released Bug description: Introduced in http://bazaar.launchpad.net/~indicator-applet-developers /indicator-applet/trunk.14.04/revision/402.1.1 and reported by Alberts Muktupāvels (albertsmuktupavels) in a comment at https://code.launchpad.net/~mitya57/indicator-applet/unparent- label/+merge/208174/comments/488891 g_object_connect() and g_object_disconnect() have different signal_spec semantics, but applet-main.c is treating them identically. Low priority, but easy fix: use g_object_disconnect()'s any-signal catchall. To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-applet/+bug/1284840/+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 1293677] Re: FFE: Export data to accounts service
** Changed in: indicator-sound (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-sound in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1293677 Title: FFE: Export data to accounts service Status in “indicator-sound” package in Ubuntu: Confirmed Bug description: To support having a user control of the media player and volume on the greeter data needs to be exported by the sound indicator into the accounts service so that it can be read by the greeter user. This will then be used on the greeter to show the relevant data to the user when that user is selected on the greeter. A user on the Unity7 desktop today will not see the media players in the greeter. They will notice that volume/mute changes that they make while using the greeter will effect their session. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1293677/+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 1295122] Re: Alarms not going off reliably on recent touch images
https://www.youtube.com/watch?v=MOQCAemwgeY -- 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/1295122 Title: Alarms not going off reliably on recent touch images Status in “indicator-datetime” package in Ubuntu: New Bug description: Alarms are not reliable on recent images on touch. Popey: See's the alarm notification but not hears no sound. davmor2: I see and hear the alarm and notification if the device is awake if the screen is blank though I sometimes get an alarm 2 minutes Plus after the alarm was meant to go off other times I neither see nor hear the alarm. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: indicator-datetime 13.10.0+14.04.20140314.1-0ubuntu1 Uname: Linux 3.4.0-5-mako armv7l ApportVersion: 2.13.3-0ubuntu1 Architecture: armhf Date: Thu Mar 20 13:12:36 2014 InstallationDate: Installed on 2014-03-20 (0 days ago) InstallationMedia: Ubuntu Trusty Tahr (development branch) - armhf (20140320) ProcEnviron: TERM=linux PATH=(custom, no user) SourcePackage: indicator-datetime UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1295122/+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 1295122] Re: Alarms not going off reliably on recent touch images
set as critical as a promotion blocker ** Changed in: indicator-datetime (Ubuntu) Importance: Undecided = Critical ** Changed in: indicator-datetime (Ubuntu) Assignee: (unassigned) = Charles Kerr (charlesk) -- 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/1295122 Title: Alarms not going off reliably on recent touch images Status in “indicator-datetime” package in Ubuntu: New Bug description: Alarms are not reliable on recent images on touch. Popey: See's the alarm notification but not hears no sound. davmor2: I see and hear the alarm and notification if the device is awake if the screen is blank though I sometimes get an alarm 2 minutes Plus after the alarm was meant to go off other times I neither see nor hear the alarm. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: indicator-datetime 13.10.0+14.04.20140314.1-0ubuntu1 Uname: Linux 3.4.0-5-mako armv7l ApportVersion: 2.13.3-0ubuntu1 Architecture: armhf Date: Thu Mar 20 13:12:36 2014 InstallationDate: Installed on 2014-03-20 (0 days ago) InstallationMedia: Ubuntu Trusty Tahr (development branch) - armhf (20140320) ProcEnviron: TERM=linux PATH=(custom, no user) SourcePackage: indicator-datetime UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1295122/+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 1295003] Re: Ubuntu does not honor “ignore-hosts” proxy settings for IPv6
** Tags added: trusty -- You received this bug notification because you are a member of DX Packages, which is subscribed to d-conf in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1295003 Title: Ubuntu does not honor “ignore-hosts” proxy settings for IPv6 Status in “d-conf” package in Ubuntu: New Bug description: I just typed under dconf-editor, System → Proxy → ignore-hosts, the following content: ['localhost', '127.0.0.0/8', '::1', '192.168.0.1', '2000::/3', 'fc00::/8'] But, Google Chrome (and apt-get update / upgrade) is just ignoring this settings. Also, Firefox doesn't honor the `ingore-hosts` settings, even configuring it to Use system proxy settings. For example, my Proxy Server (Ubuntu with Squid3) is in dual-stacked mode BUT, I do NOT want to access IPv6 web sites through the Proxy, that's why I'm trying to ignore the entire IPv6 Internet with the entry 2000::/3 above, but, it does not work as expected. BTW, I don't need the proxy to access Hyperboria sites, which resides under fc00::/8 (local / private subnet) but, it doesn't work either... Why I'm doing this? Because my environment is already a IPv6-Only Network and, to access the old internet infrastructure (IPv4-Only), I need to go through the dual-stacked proxy. But I need the proxy only when a web site doesn't have IPv6... How can I know that it doesn't work?! It is simple, just access a web site that shows a IPv6 address on it, for example, http://www.sixxs.net or http://ipv6.whatismyv6.com, then, I'm still seeing the IPv6 address of the Proxy Server, so, ignore- hosts entry '2000::/3' doesn't seem to be working. Plus, when I'm trying to access a Hyperboria website, Squid returns an error that it can not reach `fc00::/8` network (Squid ERROR: (101) Network is unreachable) ...of course it can't, the cjdns router is running right on my Ubuntu Desktop, so, no need to go through proxy when browsing Hyperboria fc00::/8 but, Ubuntu isn't honoring ignore-hosts under proxy settings. Please guys, Linux is a O.S. built for networks! How can Ubuntu Proxy Setup be so simplistic?! And it doesn't even work! I already tried askubuntu.com but, no answer there, look: http://askubuntu.com/questions/435163/how-to-make-ubuntu-honor-ignore- hosts-proxy-settings-for-ipv6 I really appreciate any help! This is a serious problem. Thanks! Thiago To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/d-conf/+bug/1295003/+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 1294079] [NEW] New Lock Screen in 14.04 disables power management
You have been subscribed to a public bug: It appears that there are some power management issues related to the new lock screen in 14.04... To me, it appears that the screen never goes to sleep while displaying the lock screen, yet when I unlock it the screen often immediately goes to sleep and is then woken back up because I'm now using it. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: ubuntu-desktop 1.321 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: Unity Date: Tue Mar 18 11:50:52 2014 InstallationDate: Installed on 2013-10-25 (143 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) SourcePackage: ubuntu-meta UpgradeStatus: Upgraded to trusty on 2014-01-17 (59 days ago) ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages trusty -- New Lock Screen in 14.04 disables power management https://bugs.launchpad.net/bugs/1294079 You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. -- 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 1294079] Re: New Lock Screen in 14.04 disables power management
** Package changed: ubuntu-meta (Ubuntu) = unity (Ubuntu) -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1294079 Title: New Lock Screen in 14.04 disables power management Status in “unity” package in Ubuntu: New Bug description: It appears that there are some power management issues related to the new lock screen in 14.04... To me, it appears that the screen never goes to sleep while displaying the lock screen, yet when I unlock it the screen often immediately goes to sleep and is then woken back up because I'm now using it. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: ubuntu-desktop 1.321 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: Unity Date: Tue Mar 18 11:50:52 2014 InstallationDate: Installed on 2013-10-25 (143 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) SourcePackage: ubuntu-meta UpgradeStatus: Upgraded to trusty on 2014-01-17 (59 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1294079/+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 1294570] Re: Lockscreen: Privacy concern when unlocking after suspend
*** This bug is a duplicate of bug 1292446 *** https://bugs.launchpad.net/bugs/1292446 ** This bug has been marked a duplicate of bug 1292446 lockscreen: on autolock on suspend the fade does not complete before suspend leaving desktop partially visible for a short period on resume -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1294570 Title: Lockscreen: Privacy concern when unlocking after suspend Status in Unity: New Status in “unity” package in Ubuntu: New Bug description: Whenever I try to wake my laptop from suspend, it shows me the desktop for a second and then the unity lock screen fades in. This could be a big privacy concern for some users. Whenever the session is locked, only the lockscreen should be visible. The session should not be visible even for a second. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1294570/+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 1291088] Re: Doesn't unlock when coming back from the greeter
** Changed in: unity Assignee: (unassigned) = Andrea Azzarone (andyrock) ** Changed in: unity (Ubuntu) Assignee: (unassigned) = Andrea Azzarone (andyrock) ** Changed in: unity (Ubuntu) Status: Triaged = In Progress ** Changed in: unity Status: Triaged = In Progress -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1291088 Title: Doesn't unlock when coming back from the greeter Status in Unity: In Progress Status in “unity” package in Ubuntu: In Progress Bug description: Using the new unity-lock-screen from the current candidate version: - run unity on a system with multiple users - click on another user in indicator-session - the greeter is displayed with that user selected, so you can type the password to log in - select back your user and enter the password to unlock the session - what happens: the session is unlocked then locked again just after that - what should happen: the session should stay unlocked To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1291088/+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 1292391] Re: lockscreen - wallpaper is not properly resized when unplugging monitors
** Tags added: lockscreen -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1292391 Title: lockscreen - wallpaper is not properly resized when unplugging monitors Status in Unity: New Status in “unity” package in Ubuntu: New Bug description: Steps to repoduce: - Have 2 monitors/displays with different resolutions setup on your trusty installation. (In my case: Primary 1600x900 laptop screen and secondary 1920x1080 external monitor.) - Lock the screen via shortcut. - Remove one monitor. (In my case: Remove the external one.) - Result: The display setup change is detected but the wallpaper on the remaining screen shows artifacts of improper resizing. Unlocking and locking the screen again will display the wallpaper properly resized without artifacts. - Settings for background images in control center are set to resize for each screen (the 2nd option). I attached photos taken of the same screen with and without aritfacts (same size, though the dots have different spacing). Wallpaper used is from the current default selection. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1292391/+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 1265022] Re: package libboost1.49-dev 1.49.0-3.2ubuntu1 [modified: usr/bin/bcp] failed to install/upgrade: trying to overwrite '/usr/bin/bcp', which is also in package libboost1.53-
** Description changed: This started after the upgrade from 13.04 to 13.10 failed partway through. After the failure I am able to reboot and the machine does say it's running 13.10 But the Software Updater won't start it says: -An unresolvable problem occurred while initializing the package + An unresolvable problem occurred while initializing the package information. -Please report this bug against the 'update-manager' package and include the following error message: - E:Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages. + Please report this bug against the 'update-manager' package and include the following error message: + E:Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages. Trying to upgrade from the command line fails as follows: $ sudo apt-get upgrade -f Reading package lists... Done - Building dependency tree + Building dependency tree Reading state information... Done Correcting dependencies... Done The following packages have been kept back: - kdevelop libboost-all-dev libboost-chrono-dev libboost-date-time-dev - libboost-dev libboost-filesystem-dev libboost-graph-dev - libboost-graph-parallel-dev libboost-iostreams-dev libboost-locale-dev - libboost-math-dev libboost-mpi-dev libboost-mpi-python-dev - libboost-program-options-dev libboost-python-dev libboost-random-dev - libboost-regex-dev libboost-serialization-dev libboost-signals-dev - libboost-system-dev libboost-test-dev libboost-thread-dev libboost-timer-dev - libboost-wave-dev linux-generic linux-headers-generic linux-image-generic + kdevelop libboost-all-dev libboost-chrono-dev libboost-date-time-dev + libboost-dev libboost-filesystem-dev libboost-graph-dev + libboost-graph-parallel-dev libboost-iostreams-dev libboost-locale-dev + libboost-math-dev libboost-mpi-dev libboost-mpi-python-dev + libboost-program-options-dev libboost-python-dev libboost-random-dev + libboost-regex-dev libboost-serialization-dev libboost-signals-dev + libboost-system-dev libboost-test-dev libboost-thread-dev libboost-timer-dev + libboost-wave-dev linux-generic linux-headers-generic linux-image-generic The following packages will be upgraded: - libboost1.49-dev + libboost1.49-dev 1 upgraded, 0 newly installed, 0 to remove and 27 not upgraded. 71 not fully installed or removed. Need to get 0 B/9,208 kB of archives. After this operation, 36.9 kB of additional disk space will be used. - Do you want to continue [Y/n]? + Do you want to continue [Y/n]? (Reading database ... 405011 files and directories currently installed.) Preparing to replace libboost1.49-dev 1.49.0-3.2ubuntu1 (using .../libboost1.49-dev_1.49.0-4_amd64.deb) ... Unpacking replacement libboost1.49-dev ... dpkg: error processing /var/cache/apt/archives/libboost1.49-dev_1.49.0-4_amd64.deb (--unpack): - trying to overwrite '/usr/bin/bcp', which is also in package libboost1.53-tools-dev 1.53.0-6+exp3ubuntu8 + trying to overwrite '/usr/bin/bcp', which is also in package libboost1.53-tools-dev 1.53.0-6+exp3ubuntu8 dpkg-deb: error: subprocess paste was killed by signal (Broken pipe) Errors were encountered while processing: - /var/cache/apt/archives/libboost1.49-dev_1.49.0-4_amd64.deb + /var/cache/apt/archives/libboost1.49-dev_1.49.0-4_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) $ An unresolvable problem occurred while initializing the package information. An: command not found - $ + $ $ Please report this bug against the 'update-manager' package and include the following error message: Please: command not found $ E:Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages. ProblemType: Package DistroRelease: Ubuntu 13.10 Package: libboost1.49-dev 1.49.0-3.2ubuntu1 [modified: usr/bin/bcp] ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7 Uname: Linux 3.11.0-14-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 Date: Mon Dec 30 08:41:08 2013 Dependencies: - gcc-4.8-base 4.8.1-10ubuntu9 - libc6 2.17-93ubuntu4 - libgcc1 1:4.8.1-10ubuntu9 - libstdc++6 4.8.1-10ubuntu9 - multiarch-support 2.17-93ubuntu4 + gcc-4.8-base 4.8.1-10ubuntu9 + libc6 2.17-93ubuntu4 + libgcc1 1:4.8.1-10ubuntu9 + libstdc++6 4.8.1-10ubuntu9 + multiarch-support 2.17-93ubuntu4 DpkgTerminalLog: - Preparing to replace libboost1.49-dev 1.49.0-3.2ubuntu1 (using .../libboost1.49-dev_1.49.0-4_amd64.deb) ... - Unpacking replacement libboost1.49-dev ... - dpkg: error processing /var/cache/apt/archives/libboost1.49-dev_1.49.0-4_amd64.deb (--unpack): - trying to overwrite '/usr/bin/bcp', which is also in package libboost1.53-tools-dev 1.53.0-6+exp3ubuntu8 + Preparing to replace libboost1.49-dev 1.49.0-3.2ubuntu1 (using .../libboost1.49-dev_1.49.0-4_amd64.deb) ... + Unpacking replacement libboost1.49-dev ... + dpkg:
[Dx-packages] [Bug 1295194] [NEW] [lockscreen] It's possible to lock a guest-session
Public bug reported: Just hit that one by doing: - open guest session from the session indicator - in the guest session pick your user - go back to your session - use the indicator to pick the guest session - you are back to the guest session which is locked down ** Affects: unity Importance: High Assignee: Andrea Azzarone (andyrock) Status: In Progress ** Affects: unity (Ubuntu) Importance: Undecided Assignee: Andrea Azzarone (andyrock) Status: In Progress ** Tags: lockscreen ** Changed in: unity Importance: Undecided = High ** Changed in: unity Status: New = Incomplete ** Changed in: unity Status: Incomplete = Fix Committed ** Changed in: unity Status: Fix Committed = In Progress ** Also affects: unity (Ubuntu) Importance: Undecided Status: New ** Changed in: unity Milestone: None = 7.2.0 ** Changed in: unity Assignee: (unassigned) = Andrea Azzarone (andyrock) ** Changed in: unity (Ubuntu) Assignee: (unassigned) = Andrea Azzarone (andyrock) ** Tags added: lockscreen ** Branch linked: lp:~andyrock/unity/guest-session-lockscreen -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1295194 Title: [lockscreen] It's possible to lock a guest-session Status in Unity: In Progress Status in “unity” package in Ubuntu: In Progress Bug description: Just hit that one by doing: - open guest session from the session indicator - in the guest session pick your user - go back to your session - use the indicator to pick the guest session - you are back to the guest session which is locked down To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1295194/+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 1295122] Re: Alarms not going off reliably on recent touch images
Can you guys try to reproduce this issue after running 'powerd-cli active' (as root) on another terminal? Just to understand if this is related with the device going into deep suspend or not, as it's expected to be broken in case the device is fully suspended (no support for hw alarms yet). -- 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/1295122 Title: Alarms not going off reliably on recent touch images Status in “indicator-datetime” package in Ubuntu: New Bug description: Alarms are not reliable on recent images on touch. Popey: See's the alarm notification but not hears no sound. davmor2: I see and hear the alarm and notification if the device is awake if the screen is blank though I sometimes get an alarm 2 minutes Plus after the alarm was meant to go off other times I neither see nor hear the alarm. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: indicator-datetime 13.10.0+14.04.20140314.1-0ubuntu1 Uname: Linux 3.4.0-5-mako armv7l ApportVersion: 2.13.3-0ubuntu1 Architecture: armhf Date: Thu Mar 20 13:12:36 2014 InstallationDate: Installed on 2014-03-20 (0 days ago) InstallationMedia: Ubuntu Trusty Tahr (development branch) - armhf (20140320) ProcEnviron: TERM=linux PATH=(custom, no user) SourcePackage: indicator-datetime UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1295122/+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 1295194] Re: [lockscreen] It's possible to lock a guest-session
** Changed in: unity (Ubuntu) Status: New = In Progress -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1295194 Title: [lockscreen] It's possible to lock a guest-session Status in Unity: In Progress Status in “unity” package in Ubuntu: In Progress Bug description: Just hit that one by doing: - open guest session from the session indicator - in the guest session pick your user - go back to your session - use the indicator to pick the guest session - you are back to the guest session which is locked down To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1295194/+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 1295122] Re: Alarms not going off reliably on recent touch images
I ran powerd-cli active in another terminal. Set alarm for 1 min's time. Tapped power button to blank screen. Wait... Nothing happens. Tap power button once time for alarm has passed and the alarm appears and sounds. -- 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/1295122 Title: Alarms not going off reliably on recent touch images Status in “indicator-datetime” package in Ubuntu: New Bug description: Alarms are not reliable on recent images on touch. Popey: See's the alarm notification but not hears no sound. davmor2: I see and hear the alarm and notification if the device is awake if the screen is blank though I sometimes get an alarm 2 minutes Plus after the alarm was meant to go off other times I neither see nor hear the alarm. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: indicator-datetime 13.10.0+14.04.20140314.1-0ubuntu1 Uname: Linux 3.4.0-5-mako armv7l ApportVersion: 2.13.3-0ubuntu1 Architecture: armhf Date: Thu Mar 20 13:12:36 2014 InstallationDate: Installed on 2014-03-20 (0 days ago) InstallationMedia: Ubuntu Trusty Tahr (development branch) - armhf (20140320) ProcEnviron: TERM=linux PATH=(custom, no user) SourcePackage: indicator-datetime UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1295122/+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 1295194] Re: [lockscreen] It's possible to lock a guest-session
** Changed in: unity (Ubuntu) Importance: Undecided = High -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1295194 Title: [lockscreen] It's possible to lock a guest-session Status in Unity: In Progress Status in “unity” package in Ubuntu: In Progress Bug description: Just hit that one by doing: - open guest session from the session indicator - in the guest session pick your user - go back to your session - use the indicator to pick the guest session - you are back to the guest session which is locked down To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1295194/+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 1295237] [NEW] Sometimes alarms trigger at xx seconds past their time and dismiss on snap doesn't stop the ringing
Public bug reported: Steps to debug: adb shell sudo -u phablet -i stop indicator-datetime G_MESSAGES_DEBUG=all /usr/lib/arm-linux-gnueabihf/indicator-datetime/indicator-datetime-service In a separate terminal run: adb shell powerd-cli active Steps to reproduce: Set an alarm for 3 minutes time Hit the power button Repeat until the issue triggers. At some point the alarm will sound you hit dismiss in the snap decision and the alarm doesn't stop ringing. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: indicator-datetime 13.10.0+14.04.20140314.1-0ubuntu1 Uname: Linux 3.4.0-5-mako armv7l ApportVersion: 2.13.3-0ubuntu1 Architecture: armhf Date: Thu Mar 20 16:51:23 2014 InstallationDate: Installed on 2014-03-20 (0 days ago) InstallationMedia: Ubuntu Trusty Tahr (development branch) - armhf (20140320) ProcEnviron: TERM=linux PATH=(custom, no user) SourcePackage: indicator-datetime UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: indicator-datetime (Ubuntu) Importance: High Assignee: Charles Kerr (charlesk) Status: Confirmed ** Tags: apport-bug armhf mako r248 trusty -- 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/1295237 Title: Sometimes alarms trigger at xx seconds past their time and dismiss on snap doesn't stop the ringing Status in “indicator-datetime” package in Ubuntu: Confirmed Bug description: Steps to debug: adb shell sudo -u phablet -i stop indicator-datetime G_MESSAGES_DEBUG=all /usr/lib/arm-linux-gnueabihf/indicator-datetime/indicator-datetime-service In a separate terminal run: adb shell powerd-cli active Steps to reproduce: Set an alarm for 3 minutes time Hit the power button Repeat until the issue triggers. At some point the alarm will sound you hit dismiss in the snap decision and the alarm doesn't stop ringing. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: indicator-datetime 13.10.0+14.04.20140314.1-0ubuntu1 Uname: Linux 3.4.0-5-mako armv7l ApportVersion: 2.13.3-0ubuntu1 Architecture: armhf Date: Thu Mar 20 16:51:23 2014 InstallationDate: Installed on 2014-03-20 (0 days ago) InstallationMedia: Ubuntu Trusty Tahr (development branch) - armhf (20140320) ProcEnviron: TERM=linux PATH=(custom, no user) SourcePackage: indicator-datetime UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1295237/+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 1295237] Re: Sometimes alarms trigger at xx seconds past their time and dismiss on snap doesn't stop the ringing
confirming, seems a promotion blocker as well ** Changed in: indicator-datetime (Ubuntu) Importance: Undecided = High ** Changed in: indicator-datetime (Ubuntu) Status: New = Confirmed ** Changed in: indicator-datetime (Ubuntu) Assignee: (unassigned) = Charles Kerr (charlesk) -- 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/1295237 Title: Sometimes alarms trigger at xx seconds past their time and dismiss on snap doesn't stop the ringing Status in “indicator-datetime” package in Ubuntu: Confirmed Bug description: Steps to debug: adb shell sudo -u phablet -i stop indicator-datetime G_MESSAGES_DEBUG=all /usr/lib/arm-linux-gnueabihf/indicator-datetime/indicator-datetime-service In a separate terminal run: adb shell powerd-cli active Steps to reproduce: Set an alarm for 3 minutes time Hit the power button Repeat until the issue triggers. At some point the alarm will sound you hit dismiss in the snap decision and the alarm doesn't stop ringing. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: indicator-datetime 13.10.0+14.04.20140314.1-0ubuntu1 Uname: Linux 3.4.0-5-mako armv7l ApportVersion: 2.13.3-0ubuntu1 Architecture: armhf Date: Thu Mar 20 16:51:23 2014 InstallationDate: Installed on 2014-03-20 (0 days ago) InstallationMedia: Ubuntu Trusty Tahr (development branch) - armhf (20140320) ProcEnviron: TERM=linux PATH=(custom, no user) SourcePackage: indicator-datetime UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1295237/+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 1295237] Re: Sometimes alarms trigger at xx seconds past their time and dismiss on snap doesn't stop the ringing
** Also affects: unity-notifications Importance: Undecided Status: New ** Changed in: unity-notifications Importance: Undecided = High -- 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/1295237 Title: Sometimes alarms trigger at xx seconds past their time and dismiss on snap doesn't stop the ringing Status in Server and client library for desktop notifications in Unity: New Status in “indicator-datetime” package in Ubuntu: Confirmed Bug description: Steps to debug: adb shell sudo -u phablet -i stop indicator-datetime G_MESSAGES_DEBUG=all /usr/lib/arm-linux-gnueabihf/indicator-datetime/indicator-datetime-service In a separate terminal run: adb shell powerd-cli active Steps to reproduce: Set an alarm for 3 minutes time Hit the power button Repeat until the issue triggers. At some point the alarm will sound you hit dismiss in the snap decision and the alarm doesn't stop ringing. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: indicator-datetime 13.10.0+14.04.20140314.1-0ubuntu1 Uname: Linux 3.4.0-5-mako armv7l ApportVersion: 2.13.3-0ubuntu1 Architecture: armhf Date: Thu Mar 20 16:51:23 2014 InstallationDate: Installed on 2014-03-20 (0 days ago) InstallationMedia: Ubuntu Trusty Tahr (development branch) - armhf (20140320) ProcEnviron: TERM=linux PATH=(custom, no user) SourcePackage: indicator-datetime UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/unity-notifications/+bug/1295237/+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 1295237] Re: Sometimes alarms trigger at xx seconds past their time and dismiss on snap doesn't stop the ringing
Looks like what's happening here is indicator-datetime is blocking for
25 seconds inside of libnotify's notify_notification_show() call,
waiting for unity-notifications to respond.
(process:6560): Indicator-Datetime-DEBUG: ClockWatcher 0xbe92d450 calling
pulse() due to clock minute_changed
(process:6560): libnotify-WARNING **: Failed to connect to proxy
(process:6560): Indicator-Datetime-WARNING **: Unable to show snap decision
for 'Alarm': Timeout was reached
Those last three lines of that log are the interesting part. The code
being triggered is this:
auto nn = notify_notification_new(title, body.c_str(), icon_name);
if (mode == NOTIFY_MODE_SNAP)
{
notify_notification_set_hint_string(nn, x-canonical-snap-decisions,
true);
notify_notification_set_hint_string(nn,
x-canonical-private-button-tint, true);
notify_notification_add_action(nn, show, _(Show), on_snap_show,
data, nullptr);
notify_notification_add_action(nn, dismiss, _(Dismiss),
on_snap_dismiss, data, nullptr);
g_signal_connect(G_OBJECT(nn), closed, G_CALLBACK(on_snap_closed),
data);
}
g_object_set_data_full(G_OBJECT(nn), snap-data, data,
snap_data_destroy_notify);
GError * error = nullptr;
notify_notification_show(nn, error);
if (error != NULL)
{
g_warning(Unable to show snap decision for '%s': %s, body.c_str(),
error-message);
g_error_free(error);
data-show(data-appointment);
}
In libnotify, notify_notification_show() calls its helper function
_notify_get_proxy(), which calls g_dbus_proxy_new_for_bus_sync().
g_dbus_connection_send_message_with_reply_unlocked() uses a default
timeout of 25 seconds, which is consistent with what davmor2's seeing:
[11:38:20] davmor2 charles: it went off at 16:35:26 rather than
16:35:00
Another indication that this is where the 25 seconds went is the error
message returned by gio, which matches the one in the log.
send_message_with_reply_timeout_cb()'s message is Timeout was reached
--
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/1295237
Title:
Sometimes alarms trigger at xx seconds past their time and dismiss on
snap doesn't stop the ringing
Status in Server and client library for desktop notifications in Unity:
New
Status in “indicator-datetime” package in Ubuntu:
Confirmed
Bug description:
Steps to debug:
adb shell
sudo -u phablet -i
stop indicator-datetime
G_MESSAGES_DEBUG=all
/usr/lib/arm-linux-gnueabihf/indicator-datetime/indicator-datetime-service
In a separate terminal run:
adb shell
powerd-cli active
Steps to reproduce:
Set an alarm for 3 minutes time
Hit the power button
Repeat until the issue triggers.
At some point the alarm will sound you hit dismiss in the snap
decision and the alarm doesn't stop ringing.
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: indicator-datetime 13.10.0+14.04.20140314.1-0ubuntu1
Uname: Linux 3.4.0-5-mako armv7l
ApportVersion: 2.13.3-0ubuntu1
Architecture: armhf
Date: Thu Mar 20 16:51:23 2014
InstallationDate: Installed on 2014-03-20 (0 days ago)
InstallationMedia: Ubuntu Trusty Tahr (development branch) - armhf (20140320)
ProcEnviron:
TERM=linux
PATH=(custom, no user)
SourcePackage: indicator-datetime
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/unity-notifications/+bug/1295237/+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 1295267] [NEW] Windows change Monitor/Desktop after screen lock
Public bug reported: I run a dual monitor configuration, with one portrait and one landscape. I nearly always have multiple applications open in multiple windows across both monitors and all virtual desktops. When I lock the screen and then unlock, my application windows will move from their original position. Sometimes they are in completely random positions; Other times they seem to get the monitors confused, and rather than being in the top half of the portrait monitor they are on the top half of the landscape monitor; Sometimes it is only a new desktop, but the monitor position is the same; Sometimes it is the same desktop, but on the other monitor. Description:Ubuntu 13.10 Release:13.10 What I expect to happen: When I unlock my computer, all the windows are in the same position on the same monitor and desktop as I left them. What actually happens: When I unlock my computer, some or all of the windows have been changed to a random position on a random monitor and/or desktop. ** Affects: unity (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1295267 Title: Windows change Monitor/Desktop after screen lock Status in “unity” package in Ubuntu: New Bug description: I run a dual monitor configuration, with one portrait and one landscape. I nearly always have multiple applications open in multiple windows across both monitors and all virtual desktops. When I lock the screen and then unlock, my application windows will move from their original position. Sometimes they are in completely random positions; Other times they seem to get the monitors confused, and rather than being in the top half of the portrait monitor they are on the top half of the landscape monitor; Sometimes it is only a new desktop, but the monitor position is the same; Sometimes it is the same desktop, but on the other monitor. Description: Ubuntu 13.10 Release: 13.10 What I expect to happen: When I unlock my computer, all the windows are in the same position on the same monitor and desktop as I left them. What actually happens: When I unlock my computer, some or all of the windows have been changed to a random position on a random monitor and/or desktop. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1295267/+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 1295271] [NEW] On phone, alarms being shown without dismiss/show buttons
Public bug reported:
Reported by Popey @
http://popey.com/~alan/phablet/device-2014-03-20-123802.png
Part of the cause for this is fairly straightforward. The code that
generates the snap decision is shown at http://bazaar.launchpad.net
/~indicator-applet-developers/indicator-
datetime/trunk.14.04/view/head:/src/snap.cpp?start_revid=324#L225.
The relevant bit is that the two actions are added to the notification
only if (mode == NOTIFY_MODE_SNAP):
auto nn = notify_notification_new(title, body.c_str(), icon_name);
if (mode == NOTIFY_MODE_SNAP)
{
...
notify_notification_add_action(nn, show, _(Show), on_snap_show,
data, nullptr);
notify_notification_add_action(nn, dismiss, _(Dismiss),
on_snap_dismiss, data, nullptr);
...
}
...
notify_notification_show(nn, error);
Where the mode is chosen based on this:
http://bazaar.launchpad.net/~indicator-applet-developers/indicator-
datetime/trunk.14.04/view/head:/src/snap.cpp?start_revid=324#L205
i.e., if the notification server doesn't say that it supports actions,
we fall back to bubble notification instead.
I see a TODO item in indicator-datetime would be to add some debugging
information here so that we can report exactly what server caps we got
back from libnotify. In addition, since this is being reported at the
same time that davmor2 is reporting bug #1295237, I think it makes sense
to pull unity-notifications into this for more pairs of eyes.
** Affects: indicator-datetime (Ubuntu)
Importance: Undecided
Assignee: Charles Kerr (charlesk)
Status: Triaged
** Affects: unity-notifications (Ubuntu)
Importance: Undecided
Status: New
--
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/1295271
Title:
On phone, alarms being shown without dismiss/show buttons
Status in “indicator-datetime” package in Ubuntu:
Triaged
Status in “unity-notifications” package in Ubuntu:
New
Bug description:
Reported by Popey @
http://popey.com/~alan/phablet/device-2014-03-20-123802.png
Part of the cause for this is fairly straightforward. The code that
generates the snap decision is shown at http://bazaar.launchpad.net
/~indicator-applet-developers/indicator-
datetime/trunk.14.04/view/head:/src/snap.cpp?start_revid=324#L225.
The relevant bit is that the two actions are added to the notification
only if (mode == NOTIFY_MODE_SNAP):
auto nn = notify_notification_new(title, body.c_str(), icon_name);
if (mode == NOTIFY_MODE_SNAP)
{
...
notify_notification_add_action(nn, show, _(Show), on_snap_show,
data, nullptr);
notify_notification_add_action(nn, dismiss, _(Dismiss),
on_snap_dismiss, data, nullptr);
...
}
...
notify_notification_show(nn, error);
Where the mode is chosen based on this:
http://bazaar.launchpad.net/~indicator-applet-developers/indicator-
datetime/trunk.14.04/view/head:/src/snap.cpp?start_revid=324#L205
i.e., if the notification server doesn't say that it supports actions,
we fall back to bubble notification instead.
I see a TODO item in indicator-datetime would be to add some debugging
information here so that we can report exactly what server caps we got
back from libnotify. In addition, since this is being reported at the
same time that davmor2 is reporting bug #1295237, I think it makes
sense to pull unity-notifications into this for more pairs of eyes.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1295271/+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 1295271] Re: On phone, alarms being shown without dismiss/show buttons
** Attachment added: popey's screenshot
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1295271/+attachment/4034428/+files/device-2014-03-20-123802.png
** Also affects: unity-notifications (Ubuntu)
Importance: Undecided
Status: New
** Description changed:
Reported by Popey @
http://popey.com/~alan/phablet/device-2014-03-20-123802.png
- Part of this is fairly straightforward. The code that generates the snap
- decision is shown at http://bazaar.launchpad.net/~indicator-applet-
- developers/indicator-
+ Part of the cause for this is fairly straightforward. The code that
+ generates the snap decision is shown at http://bazaar.launchpad.net
+ /~indicator-applet-developers/indicator-
datetime/trunk.14.04/view/head:/src/snap.cpp?start_revid=324#L225.
The relevant bit is that the two actions are added to the notification
only if (mode == NOTIFY_MODE_SNAP):
auto nn = notify_notification_new(title, body.c_str(), icon_name);
if (mode == NOTIFY_MODE_SNAP)
{
...
notify_notification_add_action(nn, show, _(Show), on_snap_show,
data, nullptr);
notify_notification_add_action(nn, dismiss, _(Dismiss),
on_snap_dismiss, data, nullptr);
...
}
...
notify_notification_show(nn, error);
Where the mode is chosen based on this:
http://bazaar.launchpad.net/~indicator-applet-developers/indicator-
datetime/trunk.14.04/view/head:/src/snap.cpp?start_revid=324#L205
i.e., if the notification server doesn't say that it supports actions,
we fall back to bubble notification instead.
I see a TODO item in indicator-datetime would be to add some debugging
information here so that we can report exactly what server caps we got
back from libnotify. In addition, since this is being reported at the
same time that davmor2 is reporting bug #1295237, I think it makes sense
to pull unity-notifications into this for more pairs of eyes.
--
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/1295271
Title:
On phone, alarms being shown without dismiss/show buttons
Status in “indicator-datetime” package in Ubuntu:
Triaged
Status in “unity-notifications” package in Ubuntu:
New
Bug description:
Reported by Popey @
http://popey.com/~alan/phablet/device-2014-03-20-123802.png
Part of the cause for this is fairly straightforward. The code that
generates the snap decision is shown at http://bazaar.launchpad.net
/~indicator-applet-developers/indicator-
datetime/trunk.14.04/view/head:/src/snap.cpp?start_revid=324#L225.
The relevant bit is that the two actions are added to the notification
only if (mode == NOTIFY_MODE_SNAP):
auto nn = notify_notification_new(title, body.c_str(), icon_name);
if (mode == NOTIFY_MODE_SNAP)
{
...
notify_notification_add_action(nn, show, _(Show), on_snap_show,
data, nullptr);
notify_notification_add_action(nn, dismiss, _(Dismiss),
on_snap_dismiss, data, nullptr);
...
}
...
notify_notification_show(nn, error);
Where the mode is chosen based on this:
http://bazaar.launchpad.net/~indicator-applet-developers/indicator-
datetime/trunk.14.04/view/head:/src/snap.cpp?start_revid=324#L205
i.e., if the notification server doesn't say that it supports actions,
we fall back to bubble notification instead.
I see a TODO item in indicator-datetime would be to add some debugging
information here so that we can report exactly what server caps we got
back from libnotify. In addition, since this is being reported at the
same time that davmor2 is reporting bug #1295237, I think it makes
sense to pull unity-notifications into this for more pairs of eyes.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1295271/+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 1295237] Re: Sometimes alarms trigger at xx seconds past their time and dismiss on snap doesn't stop the ringing
I'm unable to connect to org.freedesktop.Notifications using gdbus command line utility or with d-feet either. Marking the datetime item invalid. ** Changed in: indicator-datetime (Ubuntu) Status: Confirmed = Invalid ** Changed in: unity-notifications 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/1295237 Title: Sometimes alarms trigger at xx seconds past their time and dismiss on snap doesn't stop the ringing Status in Server and client library for desktop notifications in Unity: Confirmed Status in “indicator-datetime” package in Ubuntu: Invalid Bug description: Steps to debug: adb shell sudo -u phablet -i stop indicator-datetime G_MESSAGES_DEBUG=all /usr/lib/arm-linux-gnueabihf/indicator-datetime/indicator-datetime-service In a separate terminal run: adb shell powerd-cli active Steps to reproduce: Set an alarm for 3 minutes time Hit the power button Repeat until the issue triggers. At some point the alarm will sound you hit dismiss in the snap decision and the alarm doesn't stop ringing. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: indicator-datetime 13.10.0+14.04.20140314.1-0ubuntu1 Uname: Linux 3.4.0-5-mako armv7l ApportVersion: 2.13.3-0ubuntu1 Architecture: armhf Date: Thu Mar 20 16:51:23 2014 InstallationDate: Installed on 2014-03-20 (0 days ago) InstallationMedia: Ubuntu Trusty Tahr (development branch) - armhf (20140320) ProcEnviron: TERM=linux PATH=(custom, no user) SourcePackage: indicator-datetime UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/unity-notifications/+bug/1295237/+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 718992] Re: Lack of wine notification area icons makes using wine more difficult
Issue 2 in the original report is this bug: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1103833 -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/718992 Title: Lack of wine notification area icons makes using wine more difficult Status in Unity: Fix Released Status in “unity” package in Ubuntu: Fix Released Status in “wine1.2” package in Ubuntu: Invalid Bug description: Binary package hint: wine1.2 Natty Narwhal (Alpha 2) - Unity with Wine issue Two Aesthetic and Ease of Use issues running Wine under 11.04A2 ISSUE #1: Notification Area has been removed, and so the normal Wine Dock has been undocked. This creates a floating Wine System Tray window, containing the notification icons from the normal systray. As it's now a normal window, it can be hidden beneath the (potential) dozens of windows that one has open, and means it might be difficult to sort out a misbehaving Wine App. ISSUE #2: All Wine apps are shown with a Wine icon on the Unity sidebar. This means it's not possible to identify (even by hovering over, which returns the label Wine) what the Wine app open is, without scrolling through the windows. Even if these programs WERE separated, they'd all have the Wine icon, so the ability to tell what the programs are is STILL not there. (Query: Based on process name?) MORE INFO: http://forum.winehq.org/viewtopic.php?p=56466 ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: wine (not installed) ProcVersionSignature: Ubuntu 2.6.38-1.28-generic 2.6.38-rc2 Uname: Linux 2.6.38-1-generic i686 Architecture: i386 Date: Mon Feb 14 20:55:29 2011 EcryptfsInUse: Yes InstallationMedia: Ubuntu 11.04 Natty Narwhal - Alpha i386 (20110202) ProcEnviron: LANGUAGE=en_GB:en LANG=en_GB.UTF-8 LC_MESSAGES=en_GB.utf8 SHELL=/bin/bash SourcePackage: wine1.2 To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/718992/+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 1295271] Re: On phone, alarms being shown without dismiss/show buttons
** Changed in: indicator-datetime (Ubuntu)
Status: New = Triaged
** Description changed:
Reported by Popey @
http://popey.com/~alan/phablet/device-2014-03-20-123802.png
Part of the cause for this is fairly straightforward. The code that
generates the snap decision is shown at http://bazaar.launchpad.net
/~indicator-applet-developers/indicator-
datetime/trunk.14.04/view/head:/src/snap.cpp?start_revid=324#L225.
The relevant bit is that the two actions are added to the notification
only if (mode == NOTIFY_MODE_SNAP):
auto nn = notify_notification_new(title, body.c_str(), icon_name);
if (mode == NOTIFY_MODE_SNAP)
{
...
notify_notification_add_action(nn, show, _(Show), on_snap_show,
data, nullptr);
notify_notification_add_action(nn, dismiss, _(Dismiss),
on_snap_dismiss, data, nullptr);
...
}
...
notify_notification_show(nn, error);
Where the mode is chosen based on this:
http://bazaar.launchpad.net/~indicator-applet-developers/indicator-
datetime/trunk.14.04/view/head:/src/snap.cpp?start_revid=324#L205
i.e., if the notification server doesn't say that it supports actions,
- we fall back to bubble notification instead.
+ we fall back to bubble notification instead. That also may explain the
+ reports of no sound being played, since we don't play sounds unless the
+ popup can be dismissed.
+
+ (This no-buttons-no-sound-just-a-popup behavior is intended for the
+ desktop, where notifications don't support actions. When working
+ properly, unity-notifications tells its clients that it supports
+ actions.)
I see a TODO item in indicator-datetime would be to add some debugging
information here so that we can report exactly what server caps we got
back from libnotify. In addition, since this is being reported at the
same time that davmor2 is reporting bug #1295237, I think it makes sense
to pull unity-notifications into this for more pairs of eyes.
--
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/1295271
Title:
On phone, alarms being shown without dismiss/show buttons
Status in “indicator-datetime” package in Ubuntu:
Triaged
Status in “unity-notifications” package in Ubuntu:
New
Bug description:
Reported by Popey @
http://popey.com/~alan/phablet/device-2014-03-20-123802.png
Part of the cause for this is fairly straightforward. The code that
generates the snap decision is shown at http://bazaar.launchpad.net
/~indicator-applet-developers/indicator-
datetime/trunk.14.04/view/head:/src/snap.cpp?start_revid=324#L225.
The relevant bit is that the two actions are added to the notification
only if (mode == NOTIFY_MODE_SNAP):
auto nn = notify_notification_new(title, body.c_str(), icon_name);
if (mode == NOTIFY_MODE_SNAP)
{
...
notify_notification_add_action(nn, show, _(Show), on_snap_show,
data, nullptr);
notify_notification_add_action(nn, dismiss, _(Dismiss),
on_snap_dismiss, data, nullptr);
...
}
...
notify_notification_show(nn, error);
Where the mode is chosen based on this:
http://bazaar.launchpad.net/~indicator-applet-developers/indicator-
datetime/trunk.14.04/view/head:/src/snap.cpp?start_revid=324#L205
i.e., if the notification server doesn't say that it supports actions,
we fall back to bubble notification instead. That also may explain the
reports of no sound being played, since we don't play sounds unless
the popup can be dismissed.
(This no-buttons-no-sound-just-a-popup behavior is intended for the
desktop, where notifications don't support actions. When working
properly, unity-notifications tells its clients that it supports
actions.)
I see a TODO item in indicator-datetime would be to add some debugging
information here so that we can report exactly what server caps we got
back from libnotify. In addition, since this is being reported at the
same time that davmor2 is reporting bug #1295237, I think it makes
sense to pull unity-notifications into this for more pairs of eyes.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1295271/+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 1295122] Re: Alarms not going off reliably on recent touch images
So, after further discussion in #ubuntu-touch, it looks like the seen- but-not-heard issue that popey's encountering, and the showing-up-late issue that davmor2 is seeing, are not related to phone nor screen wakeup issues. Dave fleshed out the showing-up-late issue at bug #1295237 I've expanded on the seen-but-not-heard issue at bug #1295271 Are there any other pending issues that need to be addressed? ** Changed in: indicator-datetime (Ubuntu) Status: New = Incomplete -- 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/1295122 Title: Alarms not going off reliably on recent touch images Status in “indicator-datetime” package in Ubuntu: Incomplete Bug description: Alarms are not reliable on recent images on touch. Even on not deep sleep mode, (wakelock with powerd-cli active), the alarm doesn't ring everytime when the screen is blanked. The first alarm worked, not the others. Popey: See's the alarm notification but not hears no sound. davmor2: I see and hear the alarm and notification if the device is awake if the screen is blank though I sometimes get an alarm 2 minutes Plus after the alarm was meant to go off other times I neither see nor hear the alarm. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: indicator-datetime 13.10.0+14.04.20140314.1-0ubuntu1 Uname: Linux 3.4.0-5-mako armv7l ApportVersion: 2.13.3-0ubuntu1 Architecture: armhf Date: Thu Mar 20 13:12:36 2014 InstallationDate: Installed on 2014-03-20 (0 days ago) InstallationMedia: Ubuntu Trusty Tahr (development branch) - armhf (20140320) ProcEnviron: TERM=linux PATH=(custom, no user) SourcePackage: indicator-datetime UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1295122/+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 1295237] Re: Sometimes alarms trigger at xx seconds past their time and dismiss on snap doesn't stop the ringing
-DEBUG: ClockWatcher 0xbeb2f450 calling
pulse() due to clock minute_changed
(process:8617): Indicator-Datetime-DEBUG: ClockWatcher 0xbeb2f450 calling
pulse() due to clock minute_changed
(process:8617): Indicator-Datetime-DEBUG: ClockWatcher 0xbeb2f450 calling
pulse() due to clock minute_changed
(process:8617): Indicator-Datetime-DEBUG:
/build/buildd/indicator-datetime-13.10.0+14.04.20140314.1/src/formatter.cpp:104
guint
unity::indicator::datetime::{anonymous}::calculate_seconds_until_next_fifteen_minutes(GDateTime*)
the next timestamp rebuild will be at 2014-03-20 18:00:00
(process:8617): Indicator-Datetime-DEBUG:
/build/buildd/indicator-datetime-13.10.0+14.04.20140314.1/src/formatter.cpp:104
guint
unity::indicator::datetime::{anonymous}::calculate_seconds_until_next_fifteen_minutes(GDateTime*)
the next timestamp rebuild will be at 2014-03-20 18:00:00
(process:8617): Indicator-Datetime-DEBUG:
/build/buildd/indicator-datetime-13.10.0+14.04.20140314.1/src/formatter.cpp:104
guint
unity::indicator::datetime::{anonymous}::calculate_seconds_until_next_fifteen_minutes(GDateTime*)
the next timestamp rebuild will be at 2014-03-20 18:00:00
(process:8617): Indicator-Datetime-DEBUG:
/build/buildd/indicator-datetime-13.10.0+14.04.20140314.1/src/formatter.cpp:104
guint
unity::indicator::datetime::{anonymous}::calculate_seconds_until_next_fifteen_minutes(GDateTime*)
the next timestamp rebuild will be at 2014-03-20 18:00:00
(process:8617): Indicator-Datetime-DEBUG: ClockWatcher 0xbeb2f450 calling
pulse() due to clock minute_changed
(process:8617): Indicator-Datetime-DEBUG: ClockWatcher 0xbeb2f450 calling
pulse() due to clock minute_changed
(process:8617): Indicator-Datetime-DEBUG: ClockWatcher 0xbeb2f450 calling
pulse() due to clock minute_changed
(process:8617): Indicator-Datetime-DEBUG: ClockWatcher 0xbeb2f450 calling
pulse() due to clock minute_changed
(process:8617): Indicator-Datetime-DEBUG: ClockWatcher 0xbeb2f450 calling
pulse() due to clock minute_changed
(process:8617): Indicator-Datetime-DEBUG: ClockWatcher 0xbeb2f450 calling
pulse() due to clock minute_changed
(process:8617): Indicator-Datetime-DEBUG: ClockWatcher 0xbeb2f450 calling
pulse() due to clock minute_changed
(process:8617): Indicator-Datetime-DEBUG: ClockWatcher 0xbeb2f450 calling
pulse() due to clock minute_changed
(process:8617): Indicator-Datetime-DEBUG: ClockWatcher 0xbeb2f450 calling
pulse() due to clock minute_changed
(process:8617): Indicator-Datetime-DEBUG: ClockWatcher 0xbeb2f450 calling
pulse() due to clock minute_changed
(process:8617): Indicator-Datetime-DEBUG: ClockWatcher 0xbeb2f450 calling
pulse() due to clock minute_changed
(process:8617): Indicator-Datetime-DEBUG: ClockWatcher 0xbeb2f450 calling
pulse() due to clock minute_changed
--
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/1295237
Title:
Sometimes alarms trigger at xx seconds past their time and dismiss on
snap doesn't stop the ringing
Status in Server and client library for desktop notifications in Unity:
Confirmed
Status in “indicator-datetime” package in Ubuntu:
Invalid
Bug description:
Steps to debug:
adb shell
sudo -u phablet -i
stop indicator-datetime
G_MESSAGES_DEBUG=all
/usr/lib/arm-linux-gnueabihf/indicator-datetime/indicator-datetime-service
In a separate terminal run:
adb shell
powerd-cli active
Steps to reproduce:
Set an alarm for 3 minutes time
Hit the power button
Repeat until the issue triggers.
At some point the alarm will sound you hit dismiss in the snap
decision and the alarm doesn't stop ringing.
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: indicator-datetime 13.10.0+14.04.20140314.1-0ubuntu1
Uname: Linux 3.4.0-5-mako armv7l
ApportVersion: 2.13.3-0ubuntu1
Architecture: armhf
Date: Thu Mar 20 16:51:23 2014
InstallationDate: Installed on 2014-03-20 (0 days ago)
InstallationMedia: Ubuntu Trusty Tahr (development branch) - armhf (20140320)
ProcEnviron:
TERM=linux
PATH=(custom, no user)
SourcePackage: indicator-datetime
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/unity-notifications/+bug/1295237/+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 1295291] [NEW] When moving a window between workspaces, the window shakes and vertical and horizontal thin lines appears for an instant. The transition is not smooth.
Public bug reported: When I use Unity, every time I move a window from one workspace to another using the keyboard bindings (SHIFT+CTRL+ALT+ arrow keys), the transition animation shows tiny vertical and horizontal lines and the window shakes a little bit, i.e., the transition is not smooth and doesn't look good. I'm using the stock Unity Packages in Ubuntu 13.10. To reproduce: * Load an application * Change that application window from one workspace to another using the keyboard bindings (SHIFT+CTRL+ALT+ arrow keys) * You should see the lack of smoothness in the transition animation. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: unity 7.1.2+13.10.20131014.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-18.32-generic 3.11.10.4 Uname: Linux 3.11.0-18-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Thu Mar 20 10:45:02 2014 DistUpgraded: 2013-12-10 08:50:02,890 DEBUG enabling apt cron job DistroCodename: saucy DistroVariant: ubuntu GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:3903] InstallationDate: Installed on 2013-10-05 (166 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MachineType: LENOVO IdeaPad U310 MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-18-generic root=UUID=51ecb09b-0548-4594-b753-690c45eb5426 ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: Upgraded to saucy on 2013-12-10 (100 days ago) dmi.bios.date: 09/04/2012 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: 65CN89WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Lenovo dmi.board.vendor: LENOVO dmi.board.version: 3194WIN8 STD SGL dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo U310 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvr65CN89WW:bd09/04/2012:svnLENOVO:pnIdeaPadU310:pvrLenovoU310:rvnLENOVO:rnLenovo:rvr3194WIN8STDSGL:cvnLENOVO:ct10:cvrLenovoU310: dmi.product.name: IdeaPad U310 dmi.product.version: Lenovo U310 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.46-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.2.1-1ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.2.1-1ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.14.5-1ubuntu2~saucy1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu10 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.904-0ubuntu2.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.9-2ubuntu1 xserver.bootTime: Thu Mar 20 08:31:03 2014 xserver.configfile: /etc/X11/xorg.conf xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id4140 vendor AUO xserver.version: 2:1.14.5-1ubuntu2~saucy1 ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 saucy ubuntu -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1295291 Title: When moving a window between workspaces, the window shakes and vertical and horizontal thin lines appears for an instant. The transition is not smooth. Status in “unity” package in Ubuntu: New Bug description: When I use Unity, every time I move a window from one workspace to another using the keyboard bindings (SHIFT+CTRL+ALT+ arrow keys), the transition animation shows tiny vertical and horizontal lines and the window shakes a little bit, i.e., the transition is not smooth and doesn't look good. I'm using the stock Unity Packages in Ubuntu 13.10. To reproduce: * Load an application * Change that application window from one workspace to another using the keyboard bindings (SHIFT+CTRL+ALT+ arrow keys) * You should see the lack of smoothness in the transition animation. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: unity 7.1.2+13.10.20131014.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-18.32-generic 3.11.10.4 Uname: Linux 3.11.0-18-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist:
[Dx-packages] [Bug 1294947] Re: Inkscape mnemonics parsed incorrectly
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: unity-gtk-module (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity-gtk-module in Ubuntu. https://bugs.launchpad.net/bugs/1294947 Title: Inkscape mnemonics parsed incorrectly Status in Unity GTK+ module: New Status in “inkscape” package in Ubuntu: Confirmed Status in “unity-gtk-module” package in Ubuntu: Confirmed Bug description: A regression with Inkscape and unity-gtk-module occurred. Menu item underscores are no longer parsed as mnemonics, and result in ugly menu item labels with visible underscores. Also several criticals are emitted (they're not present when run with UBUNTU_MENUPROXY=). To manage notifications about this bug go to: https://bugs.launchpad.net/unity-gtk-module/+bug/1294947/+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 1212664] Re: indicator-session-service crashed with Settings schema 'org.gnome.desktop.lockdown' is not installed
This bug was fixed in the package indicator-session - 12.10.5+14.04.20140320-0ubuntu1 --- indicator-session (12.10.5+14.04.20140320-0ubuntu1) trusty; urgency=low [ Charles Kerr ] * Don't show the lockscreen accelerator in switch-user mode. (LP: #1241906) * indicator-session relies on the org.gnome.desktop.lockdown schema provided by gsettings-desktop-schemas. (LP: #1212664) [ Ted Gould ] * Synchronize process management across indicators -- Ubuntu daily release ps-jenk...@lists.canonical.com Thu, 20 Mar 2014 19:18:01 + ** Changed in: indicator-session (Ubuntu) Status: Invalid = Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-session in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1212664 Title: indicator-session-service crashed with Settings schema 'org.gnome.desktop.lockdown' is not installed Status in “indicator-session” package in Ubuntu: Fix Released Bug description: I've seen the session indicator disappearing sometimes when I wake up the computer after suspension, that could be related to this. ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: indicator-session 12.10.5+13.10.20130812-0ubuntu1 ProcVersionSignature: Ubuntu 3.10.0-6.17-generic 3.10.3 Uname: Linux 3.10.0-6-generic i686 NonfreeKernelModules: wl ApportVersion: 2.12-0ubuntu3 Architecture: i386 Date: Thu Aug 15 06:38:04 2013 ExecutablePath: /usr/lib/i386-linux-gnu/indicator-session/indicator-session-service InstallationDate: Installed on 2013-08-08 (7 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha i386 (20130807) MarkForUpload: True ProcCmdline: /usr/lib/i386-linux-gnu/indicator-session/indicator-session-service ProcEnviron: SHELL=/bin/false XDG_RUNTIME_DIR=set PATH=(custom, no user) LANGUAGE=es_MX:es LANG=es_MX.UTF-8 Signal: 5 SourcePackage: indicator-session StacktraceTop: ?? () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0 ?? () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0 g_object_new_valist () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0 g_object_new () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0 g_settings_new () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0 Title: indicator-session-service crashed with signal 5 in g_object_new_valist() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-session/+bug/1212664/+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 1275379] Re: unity_support_test crashed with SIGSEGV in __GI___pthread_mutex_lock()
This solution was implemented using Ubuntu 13.10 x86_64 as the host machine. This bug seems to be fixed using Virtual Box 4.3.8. The downloads can be obtained from the repositories published by Oracle following the installation steps provided by the documentation: https://www.virtualbox.org/wiki/Linux_Downloads After installing the 14.04 iso on the guest machine, install any updates and the packages build-essential and dkms. These are needed for Virtual Box to install itself properly as a Debian package. After installing these packages, reboot the machine. After booting the guest machine, install the guest additions iso that is packaged with the Virtual Box 4.3.8 package. This should allow for proper 3D acceleration with the Unity desktop environment. -- 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/1275379 Title: unity_support_test crashed with SIGSEGV in __GI___pthread_mutex_lock() Status in “nux” package in Ubuntu: Confirmed Bug description: This occured on VirtualBox. ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: nux-tools 4.0.3+13.10.20131011-0ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-6.23-generic 3.13.0 Uname: Linux 3.13.0-6-generic x86_64 .tmp.unity.support.test.0: .tmp.unity.support.test.1: ApportVersion: 2.13.2-0ubuntu2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sun Feb 2 10:51:19 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu ExecutablePath: /usr/lib/nux/unity_support_test GraphicsCard: InnoTek Systemberatung GmbH VirtualBox Graphics Adapter [80ee:beef] (prog-if 00 [VGA controller]) InstallationDate: Installed on 2014-02-01 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140201) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox ProcCmdline: /usr/lib/nux/unity_support_test ProcEnviron: LANGUAGE=ja PATH=(custom, user) XDG_RUNTIME_DIR=set LANG=ja_JP.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-6-generic root=UUID=3059f971-387f-40ef-aa3c-259dd346cbb1 ro quiet splash vt.handoff=7 Renderer: Software SegvAnalysis: Segfault happened at: 0x7f6342c2a414 __GI___pthread_mutex_lock+4: mov 0x10(%rdi),%esi PC (0x7f6342c2a414) ok source 0x10(%rdi) (0x20d8) not located in a known VMA region (needed readable region)! destination %esi ok Stack memory exhausted (SP below stack segment) SegvReason: reading NULL VMA Signal: 11 SourcePackage: nux StacktraceTop: __GI___pthread_mutex_lock (mutex=0x0) at ../nptl/pthread_mutex_lock.c:66 ?? () from /usr/lib/x86_64-linux-gnu/dri/vboxvideo_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/vboxvideo_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/vboxvideo_dri.so start_thread (arg=0x7f63404de700) at pthread_create.c:312 Title: unity_support_test crashed with SIGSEGV in __GI___pthread_mutex_lock() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu2 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.0.1-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.0.1-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.14.5-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.907-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu1 xserver.bootTime: Sun Feb 2 10:51:12 2014 xserver.configfile: default xserver.errors: AIGLX error: vboxvideo does not export required DRI extension AIGLX: reverting to software rendering
[Dx-packages] [Bug 1293646] Re: Doesn't list all events for selected day
** Branch linked: lp:~charlesk/indicator-datetime/lp-1293646 -- 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/1293646 Title: Doesn't list all events for selected day Status in “indicator-datetime” package in Ubuntu: Triaged Bug description: Using current trusty: - configure a calendar with some events - click on a day with one of those - check that the events of the day are correctly listed Sometimes events are missing, it seems to be the one which happen earlier in the day that the current time. It would suggest the code is checking starting at the current hour and not at midnight for the selected day To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1293646/+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 1208019] Re: Eclipse menus doesn't show up in Saucy
** Changed in: unity-gtk-module Assignee: (unassigned) = William Hua (attente) ** Changed in: unity-gtk-module (Ubuntu) Assignee: (unassigned) = William Hua (attente) ** Changed in: unity-gtk-module (Ubuntu) Status: Confirmed = In Progress ** Changed in: unity-gtk-module Status: Confirmed = In Progress -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity-gtk-module in Ubuntu. https://bugs.launchpad.net/bugs/1208019 Title: Eclipse menus doesn't show up in Saucy Status in Eclipse: Confirmed Status in Unity GTK+ module: In Progress Status in “oracle-jdk7-installer” package in Ubuntu: Triaged Status in “unity-gtk-module” package in Ubuntu: In Progress Bug description: HOW TO REPRODUCE 1. Run Eclipse, Gimp or Inkscape. 2. Move the cursor to the top of the screen. 3. Click on any of the menu items (File, Edit, Navigate, ...) ** EXPECTED BEHAVIOUR ** - The content of the submenus show up. ** REAL BEHAVIOUR ** - Only the top-level headers are available. - Nothing happens when clicking on them - They don't show up in the HUD either. *** WORK-AROUND *** To modify /usr/share/applications/eclipse.desktop to look like this: [Desktop Entry] Type=Application Name=Eclipse Comment=Eclipse Integrated Development Environment Icon=eclipse Exec=env UBUNTU_MENUPROXY= eclipse Terminal=false Categories=Development;IDE;Java; RELEVANT DETAILS - Doesn't affect Ubuntu releases prior to 13.10. ** TECHNICAL INFO ** ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: eclipse 3.8.1-1ubuntu1 ProcVersionSignature: Ubuntu 3.10.0-6.17-generic 3.10.3 Uname: Linux 3.10.0-6-generic i686 ApportVersion: 2.11-0ubuntu1 Architecture: i386 Date: Sat Aug 3 17:03:55 2013 InstallationDate: Installed on 2013-07-08 (25 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha i386 (20130708) MarkForUpload: True PackageArchitecture: all SourcePackage: eclipse UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/eclipse/+bug/1208019/+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 1294444] Re: Launcher indicators/arrows are not refreshed inmediately
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: unity (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/129
Title:
Launcher indicators/arrows are not refreshed inmediately
Status in “unity” package in Ubuntu:
Confirmed
Bug description:
(By Launcher indicators I mean the little arrows which show the
window count.)
** Steps to reproduce **
1. Open one Firefox window. Notice that the window count is correct
(one indicator on the left of the Firefox launcher icon).
2. Open a second Firefox window.
Now, the number of indicators is still one. If I click the launcher
icon (activating the spread), the number of indicators is refreshed to
show the real number of Firefox windows.
I've seen this problem with other applications: Chrom{e,ium}, GNOME
Terminal, Nautilus/Files.
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: unity 7.1.2+14.04.20140313-0ubuntu1
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
CompizPlugins: No value set for
`/apps/compiz-1/general/screen0/options/active_plugins'
CurrentDesktop: Unity
Date: Tue Mar 18 22:08:14 2014
InstallationDate: Installed on 2014-03-16 (2 days ago)
InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140316)
SourcePackage: unity
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/129/+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 1292268] Re: Dash scope bar does not adjust to the dpi scale on start
** Changed in: unity Status: In Progress = Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1292268 Title: Dash scope bar does not adjust to the dpi scale on start Status in Unity: Fix Released Status in “unity” package in Ubuntu: Fix Released Bug description: Dash scope bar does not adjust to the dpi scale on start To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1292268/+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 1295413] Re: new unity lock screen doesn't appear after resume
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1292217 may or may not be related; but simply allowing the screen to timeout lock is not sufficient for me to reproduce, nor is plugging/unplugging an external display. Suspend/resume seems to be the trigger. -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1295413 Title: new unity lock screen doesn't appear after resume Status in “unity” package in Ubuntu: New Bug description: New lock screen is awesome. Unfortunately, for me, whenever I resume, I get a blank screen. I can switch VTs but switching to a text VT and back to X doesn't help. If I unplug and/or re-plug my external display, I'll sometimes get a black screen with a mouse, sometimes a lock screen that doesn't appear to be accepting keyboard input. This has happened twice now, running current trusty and I've ended up rebooting each time. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140318-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-18.38-generic 3.13.6 Uname: Linux 3.13.0-18-generic x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CurrentDesktop: Unity Date: Thu Mar 20 23:26:52 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2011-10-20 (882 days ago) InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-02-19 (29 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1295413/+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 1295413] [NEW] new unity lock screen doesn't appear after resume
Public bug reported: New lock screen is awesome. Unfortunately, for me, whenever I resume, I get a blank screen. I can switch VTs but switching to a text VT and back to X doesn't help. If I unplug and/or re-plug my external display, I'll sometimes get a black screen with a mouse, sometimes a lock screen that doesn't appear to be accepting keyboard input. This has happened twice now, running current trusty and I've ended up rebooting each time. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140318-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-18.38-generic 3.13.6 Uname: Linux 3.13.0-18-generic x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CurrentDesktop: Unity Date: Thu Mar 20 23:26:52 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2011-10-20 (882 days ago) InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-02-19 (29 days ago) ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1295413 Title: new unity lock screen doesn't appear after resume Status in “unity” package in Ubuntu: New Bug description: New lock screen is awesome. Unfortunately, for me, whenever I resume, I get a blank screen. I can switch VTs but switching to a text VT and back to X doesn't help. If I unplug and/or re-plug my external display, I'll sometimes get a black screen with a mouse, sometimes a lock screen that doesn't appear to be accepting keyboard input. This has happened twice now, running current trusty and I've ended up rebooting each time. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140318-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-18.38-generic 3.13.6 Uname: Linux 3.13.0-18-generic x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CurrentDesktop: Unity Date: Thu Mar 20 23:26:52 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2011-10-20 (882 days ago) InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-02-19 (29 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1295413/+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 1295003] Re: Ubuntu does not honor “ignore-hosts” proxy settings for IPv6
Søren, I don't think this is a d-conf fault... Since it is writing the configuration... The problem, apparently, is with the Ubuntu itself, that is ignoring that configuration, so, this affects the distro as a whole. Ubuntu NEEDs a much better Proxy Settings under System Settings = Network = Network Proxy. Even Windows XP have a better Proxy configuration than Trusty, this is a shame for us... :'( Don't you think?! Cheers! Thiago -- You received this bug notification because you are a member of DX Packages, which is subscribed to d-conf in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1295003 Title: Ubuntu does not honor “ignore-hosts” proxy settings for IPv6 Status in “d-conf” package in Ubuntu: New Bug description: I just typed under dconf-editor, System → Proxy → ignore-hosts, the following content: ['localhost', '127.0.0.0/8', '::1', '192.168.0.1', '2000::/3', 'fc00::/8'] But, Google Chrome (and apt-get update / upgrade) is just ignoring this settings. Also, Firefox doesn't honor the `ingore-hosts` settings, even configuring it to Use system proxy settings. For example, my Proxy Server (Ubuntu with Squid3) is in dual-stacked mode BUT, I do NOT want to access IPv6 web sites through the Proxy, that's why I'm trying to ignore the entire IPv6 Internet with the entry 2000::/3 above, but, it does not work as expected. BTW, I don't need the proxy to access Hyperboria sites, which resides under fc00::/8 (local / private subnet) but, it doesn't work either... Why I'm doing this? Because my environment is already a IPv6-Only Network and, to access the old internet infrastructure (IPv4-Only), I need to go through the dual-stacked proxy. But I need the proxy only when a web site doesn't have IPv6... How can I know that it doesn't work?! It is simple, just access a web site that shows a IPv6 address on it, for example, http://www.sixxs.net or http://ipv6.whatismyv6.com, then, I'm still seeing the IPv6 address of the Proxy Server, so, ignore- hosts entry '2000::/3' doesn't seem to be working. Plus, when I'm trying to access a Hyperboria website, Squid returns an error that it can not reach `fc00::/8` network (Squid ERROR: (101) Network is unreachable) ...of course it can't, the cjdns router is running right on my Ubuntu Desktop, so, no need to go through proxy when browsing Hyperboria fc00::/8 but, Ubuntu isn't honoring ignore-hosts under proxy settings. Please guys, Linux is a O.S. built for networks! How can Ubuntu Proxy Setup be so simplistic?! And it doesn't even work! I already tried askubuntu.com but, no answer there, look: http://askubuntu.com/questions/435163/how-to-make-ubuntu-honor-ignore- hosts-proxy-settings-for-ipv6 I really appreciate any help! This is a serious problem. Thanks! Thiago To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/d-conf/+bug/1295003/+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 1284898] Re: compiz crashed with SIGSEGV in ScaleScreen::getSelectedWindow()
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: unity (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1284898 Title: compiz crashed with SIGSEGV in ScaleScreen::getSelectedWindow() Status in “unity” package in Ubuntu: Confirmed Bug description: crashed when pressing super + w and trying to select a window ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140220-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-12.32-generic 3.13.4 Uname: Linux 3.13.0-12-generic x86_64 ApportVersion: 2.13.2-0ubuntu5 Architecture: amd64 CurrentDesktop: Unity Date: Tue Feb 25 18:17:20 2014 ExecutablePath: /usr/bin/compiz InstallationDate: Installed on 2014-02-25 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140223) ProcCmdline: compiz ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7f1d2b6410c0 _ZNK11ScaleScreen17getSelectedWindowEv: mov0x48(%rdi),%rax PC (0x7f1d2b6410c0) ok source 0x48(%rdi) (0x0048) not located in a known VMA region (needed readable region)! destination %rax ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: unity StacktraceTop: ScaleScreen::getSelectedWindow() const () from /usr/lib/compiz/libscale.so unity::UnityScreen::handleEvent(_XEvent*) () from /usr/lib/compiz/libunityshell.so CompScreen::handleEvent(_XEvent*) () from /usr/lib/libcompiz_core.so.ABI-20140123 PrivateScaleScreen::handleEvent(_XEvent*) () from /usr/lib/compiz/libscale.so CompScreen::handleEvent(_XEvent*) () from /usr/lib/libcompiz_core.so.ABI-20140123 Title: compiz crashed with SIGSEGV in ScaleScreen::getSelectedWindow() 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/unity/+bug/1284898/+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 1287580] Re: hud docs fail tests with gtk-doc 1.20
** Changed in: hud Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to hud in Ubuntu. https://bugs.launchpad.net/bugs/1287580 Title: hud docs fail tests with gtk-doc 1.20 Status in Unity HUD: Fix Released Status in “hud” package in Ubuntu: Fix Released Bug description: Building hud fails currently, and I've tracked it down to gtk-doc update to 1.20 two weeks ago. The failure is shown as (output cut a bit): --- 7/9 Test #7: doc-libhud-check ..***Failed0.03 sec E: 1 unused documentation entries 75.0%: Checks 4, Failures: 1 Start 8: doc-libhud-client-check 8/9 Test #8: doc-libhud-client-check ...***Failed0.03 sec E: 3 undocumented or incomplete symbols 75.0%: Checks 4, Failures: 1 Start 9: doc-libhud-gtk-check 9/9 Test #9: doc-libhud-gtk-check ..***Failed0.03 sec E: 1 undocumented or incomplete symbols 50.0%: Checks 4, Failures: 2 67% tests passed, 3 tests failed out of 9 --- Downgrading to https://launchpad.net/ubuntu/+source/gtk- doc/1.19-1ubuntu1 fixes the issue. I've only tested this with Qt 5.2 installed, but I assume it'd fail to build in the archive too currently. To manage notifications about this bug go to: https://bugs.launchpad.net/hud/+bug/1287580/+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
