[Dx-packages] [Bug 1603522] Re: package libaccountsservice0:amd64 0.6.40-2ubuntu11.1 failed to install/upgrade: package libaccountsservice0:amd64 is already installed and configured
*** This bug is a duplicate of bug 1407757 *** https://bugs.launchpad.net/bugs/1407757 ** This bug has been marked a duplicate of bug 1407757 multi-arch packages cannot be installed due to dpkg wrongly detecting them as already installed -- You received this bug notification because you are a member of DX Packages, which is subscribed to accountsservice in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1603522 Title: package libaccountsservice0:amd64 0.6.40-2ubuntu11.1 failed to install/upgrade: package libaccountsservice0:amd64 is already installed and configured Status in accountsservice package in Ubuntu: New Bug description: !!! ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libaccountsservice0:amd64 0.6.40-2ubuntu11.1 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 AptdaemonVersion: 1.1.1+bzr982-0ubuntu14 Architecture: amd64 CrashReports: 644:0:114:0:2016-07-15 22:50:30.533780610 +0430:2016-07-15 22:50:30.533780610 +0430:/var/crash/accountsservice.0.upload 600:108:114:0:2016-07-15 22:50:33.045792493 +0430:2016-07-15 22:50:33.045792493 +0430:/var/crash/accountsservice.0.uploaded 640:0:114:1811528:2016-07-15 22:50:27.901772975 +0430:2016-07-15 22:50:28.901772975 +0430:/var/crash/accountsservice.0.crash 600:0:114:246312:2016-07-15 22:46:50.832750320 +0430:2016-07-15 22:46:51.832750320 +0430:/var/crash/bash-completion.0.crash 600:0:114:246332:2016-07-15 22:46:50.856750249 +0430:2016-07-15 22:46:51.856750249 +0430:/var/crash/libaccountsservice0:amd64.0.crash Date: Fri Jul 15 22:46:51 2016 DuplicateSignature: package:libaccountsservice0:amd64:0.6.40-2ubuntu11.1 Processing triggers for desktop-file-utils (0.22-1ubuntu5) ... dpkg: error processing package bash-completion (--configure): package bash-completion is already installed and configured ErrorMessage: package libaccountsservice0:amd64 is already installed and configured InstallationDate: Installed on 2016-07-14 (1 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 (20160421) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.10ubuntu1 SourcePackage: accountsservice Title: package libaccountsservice0:amd64 0.6.40-2ubuntu11.1 failed to install/upgrade: package libaccountsservice0:amd64 is already installed and configured UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1603522/+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 876491] Re: We should have a "reduced resources" settings for Unity 2D
*** This bug is a duplicate of bug 1598770 *** https://bugs.launchpad.net/bugs/1598770 ** This bug has been marked a duplicate of bug 1598770 Unity in low-graphics mode has animations and unneeded redraws -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity-2d in Ubuntu. https://bugs.launchpad.net/bugs/876491 Title: We should have a "reduced resources" settings for Unity 2D Status in unity-2d package in Ubuntu: Opinion Bug description: It would be nice it we could deactivate all kinds of animations, etc. When used with a terminal server, these kinds of animations can dramatically reduce the user experience. Even the minimize animation in Unity 2D (shrinking rectangle) can sometimes take several seconds when connected to the terminal server over a mobile broadband connection, for instance. Other than that, it's fast and responsive. It shouldn't be necessary to switch to another shell just because of this. Having the same interface in your office and when you're on the run, is valuable in and of itself. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-2d/+bug/876491/+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 420583] Re: Notify-osd looks are not customizable
I don't understand this code really:
indicator-applet-developers/notify-osd/trunk/src/defaults.c
gint
defaults_get_on_screen_timeout (Defaults* self)
{
gint on_screen_timeout;
if (!self || !IS_DEFAULTS (self))
return 0;
g_object_get (self, "on-screen-timeout", _screen_timeout, NULL);
return on_screen_timeout;
}
x time for n characters?
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to notify-osd in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/420583
Title:
Notify-osd looks are not customizable
Status in notify-osd package in Ubuntu:
Confirmed
Bug description:
Binary package hint: notify-osd
At the moment the notify-osd looks are not configurable (not with a
GUI, and as far as I can see not with gconf and/or a configuration
file).
THis should be possible to do: in the first place with gconf (or
configuration file) and in the longer term a GUI (maybe not all
aspects, but at least some of them).
Rationale:
Color settings:
https://bugs.launchpad.net/ubuntu/+source/notify-osd/+bug/334310?comments=all
(Mirco has confirmed the problem and seems to work on a solution)
Presentation settings: If notifications should be visible in fullscreen or
not (and what priority should be shown)
(https://bugs.launchpad.net/ubuntu/+source/notify-osd/+bug/402962)
Font settings:
https://bugs.launchpad.net/ubuntu/+source/notify-osd/+bug/335383 (is already
being worked on...)
Also things like blur and fade out settings should be configurable
Timeout settings: the time notifications stay should also be
configurable: some people read faster than others, so the very-
sensible default (of x time per n characters) can be good, but some
people maybe like y time per n characters.
Placement settings (which is the real cause of the bug report: center-right
is in my option very bad UI design (maybe it is just an experiment): Probably
it is more noticeable than top-right but it is also more probable that it is in
your way:
While reading (a big text) the part I'm reading is often more or less in the
center, so I can do 2 things when such a notification happens: Scroll down so I
can read the text again, or move my mouse so it appears above the notification
so I can read the text under it...
It thought notify-osd was about "passive" notifications that didn't take your
attention so you were not obliged to do anything, with the new (non-)sensible
non-configurable default setting I have to react (sometimes) to a
notification...
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/notify-osd/+bug/420583/+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 420583] Re: Notify-osd looks are not customizable
Just digging around indicator-applet-developers/notify-
osd/trunk/src/display.c
/* if there is already one bubble on display
we don't have room for another one */
if (bubble_is_visible (bubble))
return NULL;
not great, but off topic.
on topic:
if (bubble_is_urgent (bubble))
{
/* pick-up the /first/ urgent bubble
in the queue (FIFO) */
return bubble;
}
We replace this, and excuse my bashism, with something like
bubble_is_"$URGENCY" (and have no specification == urgent for your
default behavior) and let it be set by an environment variable; then the
hook is customizable like any other freedesktop feature.
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to notify-osd in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/420583
Title:
Notify-osd looks are not customizable
Status in notify-osd package in Ubuntu:
Confirmed
Bug description:
Binary package hint: notify-osd
At the moment the notify-osd looks are not configurable (not with a
GUI, and as far as I can see not with gconf and/or a configuration
file).
THis should be possible to do: in the first place with gconf (or
configuration file) and in the longer term a GUI (maybe not all
aspects, but at least some of them).
Rationale:
Color settings:
https://bugs.launchpad.net/ubuntu/+source/notify-osd/+bug/334310?comments=all
(Mirco has confirmed the problem and seems to work on a solution)
Presentation settings: If notifications should be visible in fullscreen or
not (and what priority should be shown)
(https://bugs.launchpad.net/ubuntu/+source/notify-osd/+bug/402962)
Font settings:
https://bugs.launchpad.net/ubuntu/+source/notify-osd/+bug/335383 (is already
being worked on...)
Also things like blur and fade out settings should be configurable
Timeout settings: the time notifications stay should also be
configurable: some people read faster than others, so the very-
sensible default (of x time per n characters) can be good, but some
people maybe like y time per n characters.
Placement settings (which is the real cause of the bug report: center-right
is in my option very bad UI design (maybe it is just an experiment): Probably
it is more noticeable than top-right but it is also more probable that it is in
your way:
While reading (a big text) the part I'm reading is often more or less in the
center, so I can do 2 things when such a notification happens: Scroll down so I
can read the text again, or move my mouse so it appears above the notification
so I can read the text under it...
It thought notify-osd was about "passive" notifications that didn't take your
attention so you were not obliged to do anything, with the new (non-)sensible
non-configurable default setting I have to react (sometimes) to a
notification...
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/notify-osd/+bug/420583/+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 420583] Re: Notify-osd looks are not customizable
Use case: Ubuntu derivative/rebranding diversity. Derivatives might have different interest in notifications; ie some kind of kiosk distro could intentionally favor full screen, urgency=normal, as a default behavior while a multimedia desktop may want something like elementary's wingpanel-indicator-notifications-bzr (status notifier notification log) and no bubbles. An adoptable notify-osd would win brownie points for Ayatana Design. A lot of non-Unity derivatives have already opted for their own ad-hoc notification method. -- You received this bug notification because you are a member of DX Packages, which is subscribed to notify-osd in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/420583 Title: Notify-osd looks are not customizable Status in notify-osd package in Ubuntu: Confirmed Bug description: Binary package hint: notify-osd At the moment the notify-osd looks are not configurable (not with a GUI, and as far as I can see not with gconf and/or a configuration file). THis should be possible to do: in the first place with gconf (or configuration file) and in the longer term a GUI (maybe not all aspects, but at least some of them). Rationale: Color settings: https://bugs.launchpad.net/ubuntu/+source/notify-osd/+bug/334310?comments=all (Mirco has confirmed the problem and seems to work on a solution) Presentation settings: If notifications should be visible in fullscreen or not (and what priority should be shown) (https://bugs.launchpad.net/ubuntu/+source/notify-osd/+bug/402962) Font settings: https://bugs.launchpad.net/ubuntu/+source/notify-osd/+bug/335383 (is already being worked on...) Also things like blur and fade out settings should be configurable Timeout settings: the time notifications stay should also be configurable: some people read faster than others, so the very- sensible default (of x time per n characters) can be good, but some people maybe like y time per n characters. Placement settings (which is the real cause of the bug report: center-right is in my option very bad UI design (maybe it is just an experiment): Probably it is more noticeable than top-right but it is also more probable that it is in your way: While reading (a big text) the part I'm reading is often more or less in the center, so I can do 2 things when such a notification happens: Scroll down so I can read the text again, or move my mouse so it appears above the notification so I can read the text under it... It thought notify-osd was about "passive" notifications that didn't take your attention so you were not obliged to do anything, with the new (non-)sensible non-configurable default setting I have to react (sometimes) to a notification... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/notify-osd/+bug/420583/+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 1598770] Re: Unity in low-graphics mode has animations and unneeded redraws
Hi I'm not running in Low GFX mode but dash and switcher are opaque, how can I re enable transparency for dash and switcher? -- 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/1598770 Title: Unity in low-graphics mode has animations and unneeded redraws Status in compiz package in Ubuntu: Fix Released Status in nux package in Ubuntu: Fix Released Status in unity package in Ubuntu: Fix Released Status in unity-control-center package in Ubuntu: Fix Released Status in compiz source package in Xenial: Fix Committed Status in nux source package in Xenial: Fix Committed Status in unity source package in Xenial: Fix Committed Status in unity-control-center source package in Xenial: Fix Committed Bug description: [Impact] When unity is in Low graphics mode (because of software rendering) there are still window animations and fade effects which we should get rid of. [Test case] This should apply naturally to a (virtual-)machine with no hardware acceleration or There are multiple ways to force low-gfx mode: 1) Add an upstart job such as: cat << EOF > ~/.config/upstart/lowgfx.conf start on starting unity7 pre-start script #initctl set-env --global UNITY_LOW_GFX_MODE=1 initctl set-env --global LIBGL_ALWAYS_SOFTWARE=1 end script EOF 2) Run unity with: COMPIZ_CONFIG_PROFILE=ubuntu-lowgfx On login unity should use opaque views (dash, switcher, launcher, shortcut-dialogs) with no fading and reduced effects. Windows should also use smaller shadows. [Regression potential] Some settings from unity-control-center couldn't be applied to normal profile. Low graphics mode might be used as normal one. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1598770/+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 1603543] Re: scope-runner-dbus.py crashed with SIGSEGV in ffi_call_unix64()
*** This bug is a duplicate of bug 1194465 *** https://bugs.launchpad.net/bugs/1194465 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 #1194465, 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/1603543/+attachment/4701618/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1603543/+attachment/4701619/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1603543/+attachment/4701621/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1603543/+attachment/4701622/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1603543/+attachment/4701623/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1603543/+attachment/4701624/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1603543/+attachment/4701625/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1194465 scope-runner-dbus.py crashed with SIGSEGV in auth_session_remote_object_destroyed_cb() ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of DX Packages, which is subscribed to libunity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1603543 Title: scope-runner-dbus.py crashed with SIGSEGV in ffi_call_unix64() Status in libunity package in Ubuntu: New Bug description: . ProblemType: Crash DistroRelease: Ubuntu 16.10 Package: unity-scopes-runner 7.1.4+16.10.20160516-0ubuntu1 ProcVersionSignature: Ubuntu 4.6.0-9.11-generic 4.6.4 Uname: Linux 4.6.0-9-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.2-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Fri Jul 15 16:14:35 2016 Dependencies: ExecutablePath: /usr/share/unity-scopes/scope-runner-dbus.py InstallationDate: Installed on 2016-06-06 (39 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) InterpreterPath: /usr/bin/python3.5 PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/share/unity-scopes/scope-runner-dbus.py -s files/gdrive.scope ProcEnviron: XDG_RUNTIME_DIR= SHELL=/bin/bash LANGUAGE=en_CA:en PATH=(custom, no user) LANG=en_CA.UTF-8 SegvAnalysis: Segfault happened at: 0x7fc9d80118de:cmp(%rax),%rbp PC (0x7fc9d80118de) ok source "(%rax)" (0x4) not located in a known VMA region (needed readable region)! destination "%rbp" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: libunity StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libsignon-glib.so.1 ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6 ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6 g_cclosure_marshal_generic () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: scope-runner-dbus.py crashed with SIGSEGV in ffi_call_unix64() UpgradeStatus: Upgraded to yakkety on 2016-06-14 (31 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libunity/+bug/1603543/+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 390508] Re: notifyOSD ignores the expire timeout parameter
>mpt
Glad to see this bug is still bothering you, because it still bothers
us.
bug 420583's proposal great, and it's been sitting there for seven
years.
Seven years ago there was an idea that could probably have avoided all
this trouble.
Did the x time per n characters algorithm ever really get implemented?
Where is the proposed settings dialog (aside from leolik's fork, which
has one)?
How much progress has been made toward making the hooks customizable?
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to notify-osd in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/390508
Title:
notifyOSD ignores the expire timeout parameter
Status in Ayatana Design:
New
Status in One Hundred Papercuts:
Invalid
Status in Message Web:
New
Status in notify-osd package in Ubuntu:
Won't Fix
Status in notify-osd package in Arch Linux:
New
Bug description:
Binary package hint: libnotify-bin
adyroman@panther:~/libnotify-0.4.5/tools$ lsb_release -rd
Description: Ubuntu 9.04
Release: 9.04
adyroman@panther:~/libnotify-0.4.5/tools$
adyroman@panther:~/libnotify-0.4.5/tools$ apt-cache policy libnotify-bin
libnotify-bin:
Installed: 0.4.5-0ubuntu1
Candidate: 0.4.5-0ubuntu1
Version table:
*** 0.4.5-0ubuntu1 0
500 http://ro.archive.ubuntu.com jaunty/universe Packages
100 /var/lib/dpkg/status
adyroman@panther:~/libnotify-0.4.5/tools$
adyroman@panther:~/libnotify-0.4.5/tools$ cat notify-send.c | grep
expire_timeout
static glong expire_timeout = NOTIFY_EXPIRES_DEFAULT;
{ "expire-time", 't', 0,G_OPTION_ARG_INT, _timeout,
notify_notification_set_timeout(notify, expire_timeout);
adyroman@panther:~/libnotify-0.4.5/tools$
To manage notifications about this bug go to:
https://bugs.launchpad.net/ayatana-design/+bug/390508/+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 420583] Re: Notify-osd looks are not customizable
>Timeout settings: the time notifications stay should also be configurable: some people read faster than others, so the very-sensible default (of x time per n characters) can be good, but some people maybe like y time per n characters. That would be wonderful. Implement that; put a high priority on it. Make it happen. -- You received this bug notification because you are a member of DX Packages, which is subscribed to notify-osd in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/420583 Title: Notify-osd looks are not customizable Status in notify-osd package in Ubuntu: Confirmed Bug description: Binary package hint: notify-osd At the moment the notify-osd looks are not configurable (not with a GUI, and as far as I can see not with gconf and/or a configuration file). THis should be possible to do: in the first place with gconf (or configuration file) and in the longer term a GUI (maybe not all aspects, but at least some of them). Rationale: Color settings: https://bugs.launchpad.net/ubuntu/+source/notify-osd/+bug/334310?comments=all (Mirco has confirmed the problem and seems to work on a solution) Presentation settings: If notifications should be visible in fullscreen or not (and what priority should be shown) (https://bugs.launchpad.net/ubuntu/+source/notify-osd/+bug/402962) Font settings: https://bugs.launchpad.net/ubuntu/+source/notify-osd/+bug/335383 (is already being worked on...) Also things like blur and fade out settings should be configurable Timeout settings: the time notifications stay should also be configurable: some people read faster than others, so the very- sensible default (of x time per n characters) can be good, but some people maybe like y time per n characters. Placement settings (which is the real cause of the bug report: center-right is in my option very bad UI design (maybe it is just an experiment): Probably it is more noticeable than top-right but it is also more probable that it is in your way: While reading (a big text) the part I'm reading is often more or less in the center, so I can do 2 things when such a notification happens: Scroll down so I can read the text again, or move my mouse so it appears above the notification so I can read the text under it... It thought notify-osd was about "passive" notifications that didn't take your attention so you were not obliged to do anything, with the new (non-)sensible non-configurable default setting I have to react (sometimes) to a notification... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/notify-osd/+bug/420583/+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 1603522] Re: package libaccountsservice0:amd64 0.6.40-2ubuntu11.1 failed to install/upgrade: package libaccountsservice0:amd64 is already installed and configured
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of DX Packages, which is subscribed to accountsservice in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1603522 Title: package libaccountsservice0:amd64 0.6.40-2ubuntu11.1 failed to install/upgrade: package libaccountsservice0:amd64 is already installed and configured Status in accountsservice package in Ubuntu: New Bug description: !!! ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libaccountsservice0:amd64 0.6.40-2ubuntu11.1 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 AptdaemonVersion: 1.1.1+bzr982-0ubuntu14 Architecture: amd64 CrashReports: 644:0:114:0:2016-07-15 22:50:30.533780610 +0430:2016-07-15 22:50:30.533780610 +0430:/var/crash/accountsservice.0.upload 600:108:114:0:2016-07-15 22:50:33.045792493 +0430:2016-07-15 22:50:33.045792493 +0430:/var/crash/accountsservice.0.uploaded 640:0:114:1811528:2016-07-15 22:50:27.901772975 +0430:2016-07-15 22:50:28.901772975 +0430:/var/crash/accountsservice.0.crash 600:0:114:246312:2016-07-15 22:46:50.832750320 +0430:2016-07-15 22:46:51.832750320 +0430:/var/crash/bash-completion.0.crash 600:0:114:246332:2016-07-15 22:46:50.856750249 +0430:2016-07-15 22:46:51.856750249 +0430:/var/crash/libaccountsservice0:amd64.0.crash Date: Fri Jul 15 22:46:51 2016 DuplicateSignature: package:libaccountsservice0:amd64:0.6.40-2ubuntu11.1 Processing triggers for desktop-file-utils (0.22-1ubuntu5) ... dpkg: error processing package bash-completion (--configure): package bash-completion is already installed and configured ErrorMessage: package libaccountsservice0:amd64 is already installed and configured InstallationDate: Installed on 2016-07-14 (1 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 (20160421) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.10ubuntu1 SourcePackage: accountsservice Title: package libaccountsservice0:amd64 0.6.40-2ubuntu11.1 failed to install/upgrade: package libaccountsservice0:amd64 is already installed and configured UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1603522/+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 1603522] [NEW] package libaccountsservice0:amd64 0.6.40-2ubuntu11.1 failed to install/upgrade: package libaccountsservice0:amd64 is already installed and configured
Public bug reported: !!! ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libaccountsservice0:amd64 0.6.40-2ubuntu11.1 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 AptdaemonVersion: 1.1.1+bzr982-0ubuntu14 Architecture: amd64 CrashReports: 644:0:114:0:2016-07-15 22:50:30.533780610 +0430:2016-07-15 22:50:30.533780610 +0430:/var/crash/accountsservice.0.upload 600:108:114:0:2016-07-15 22:50:33.045792493 +0430:2016-07-15 22:50:33.045792493 +0430:/var/crash/accountsservice.0.uploaded 640:0:114:1811528:2016-07-15 22:50:27.901772975 +0430:2016-07-15 22:50:28.901772975 +0430:/var/crash/accountsservice.0.crash 600:0:114:246312:2016-07-15 22:46:50.832750320 +0430:2016-07-15 22:46:51.832750320 +0430:/var/crash/bash-completion.0.crash 600:0:114:246332:2016-07-15 22:46:50.856750249 +0430:2016-07-15 22:46:51.856750249 +0430:/var/crash/libaccountsservice0:amd64.0.crash Date: Fri Jul 15 22:46:51 2016 DuplicateSignature: package:libaccountsservice0:amd64:0.6.40-2ubuntu11.1 Processing triggers for desktop-file-utils (0.22-1ubuntu5) ... dpkg: error processing package bash-completion (--configure): package bash-completion is already installed and configured ErrorMessage: package libaccountsservice0:amd64 is already installed and configured InstallationDate: Installed on 2016-07-14 (1 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 (20160421) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.10ubuntu1 SourcePackage: accountsservice Title: package libaccountsservice0:amd64 0.6.40-2ubuntu11.1 failed to install/upgrade: package libaccountsservice0:amd64 is already installed and configured UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: accountsservice (Ubuntu) Importance: Undecided Status: New ** Tags: already-installed amd64 apport-package xenial -- You received this bug notification because you are a member of DX Packages, which is subscribed to accountsservice in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1603522 Title: package libaccountsservice0:amd64 0.6.40-2ubuntu11.1 failed to install/upgrade: package libaccountsservice0:amd64 is already installed and configured Status in accountsservice package in Ubuntu: New Bug description: !!! ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libaccountsservice0:amd64 0.6.40-2ubuntu11.1 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 AptdaemonVersion: 1.1.1+bzr982-0ubuntu14 Architecture: amd64 CrashReports: 644:0:114:0:2016-07-15 22:50:30.533780610 +0430:2016-07-15 22:50:30.533780610 +0430:/var/crash/accountsservice.0.upload 600:108:114:0:2016-07-15 22:50:33.045792493 +0430:2016-07-15 22:50:33.045792493 +0430:/var/crash/accountsservice.0.uploaded 640:0:114:1811528:2016-07-15 22:50:27.901772975 +0430:2016-07-15 22:50:28.901772975 +0430:/var/crash/accountsservice.0.crash 600:0:114:246312:2016-07-15 22:46:50.832750320 +0430:2016-07-15 22:46:51.832750320 +0430:/var/crash/bash-completion.0.crash 600:0:114:246332:2016-07-15 22:46:50.856750249 +0430:2016-07-15 22:46:51.856750249 +0430:/var/crash/libaccountsservice0:amd64.0.crash Date: Fri Jul 15 22:46:51 2016 DuplicateSignature: package:libaccountsservice0:amd64:0.6.40-2ubuntu11.1 Processing triggers for desktop-file-utils (0.22-1ubuntu5) ... dpkg: error processing package bash-completion (--configure): package bash-completion is already installed and configured ErrorMessage: package libaccountsservice0:amd64 is already installed and configured InstallationDate: Installed on 2016-07-14 (1 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 (20160421) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.10ubuntu1 SourcePackage: accountsservice Title: package libaccountsservice0:amd64 0.6.40-2ubuntu11.1 failed to install/upgrade: package libaccountsservice0:amd64 is already installed and configured UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1603522/+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 1598770] Re: Unity in low-graphics mode has animations and unneeded redraws
** Tags removed: verification-needed ** Tags added: verification-done -- 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/1598770 Title: Unity in low-graphics mode has animations and unneeded redraws Status in compiz package in Ubuntu: Fix Released Status in nux package in Ubuntu: Fix Released Status in unity package in Ubuntu: Fix Released Status in unity-control-center package in Ubuntu: Fix Released Status in compiz source package in Xenial: Fix Committed Status in nux source package in Xenial: Fix Committed Status in unity source package in Xenial: Fix Committed Status in unity-control-center source package in Xenial: Fix Committed Bug description: [Impact] When unity is in Low graphics mode (because of software rendering) there are still window animations and fade effects which we should get rid of. [Test case] This should apply naturally to a (virtual-)machine with no hardware acceleration or There are multiple ways to force low-gfx mode: 1) Add an upstart job such as: cat << EOF > ~/.config/upstart/lowgfx.conf start on starting unity7 pre-start script #initctl set-env --global UNITY_LOW_GFX_MODE=1 initctl set-env --global LIBGL_ALWAYS_SOFTWARE=1 end script EOF 2) Run unity with: COMPIZ_CONFIG_PROFILE=ubuntu-lowgfx On login unity should use opaque views (dash, switcher, launcher, shortcut-dialogs) with no fading and reduced effects. Windows should also use smaller shadows. [Regression potential] Some settings from unity-control-center couldn't be applied to normal profile. Low graphics mode might be used as normal one. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1598770/+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 1598770] Please test proposed package
Hello Marco, or anyone else affected, Accepted unity into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/unity/7.4.0+16.04.20160715-0ubuntu1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! -- 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/1598770 Title: Unity in low-graphics mode has animations and unneeded redraws Status in compiz package in Ubuntu: Fix Released Status in nux package in Ubuntu: Fix Released Status in unity package in Ubuntu: Fix Released Status in unity-control-center package in Ubuntu: Fix Released Status in compiz source package in Xenial: Fix Committed Status in nux source package in Xenial: Fix Committed Status in unity source package in Xenial: Fix Committed Status in unity-control-center source package in Xenial: Fix Committed Bug description: [Impact] When unity is in Low graphics mode (because of software rendering) there are still window animations and fade effects which we should get rid of. [Test case] This should apply naturally to a (virtual-)machine with no hardware acceleration or There are multiple ways to force low-gfx mode: 1) Add an upstart job such as: cat << EOF > ~/.config/upstart/lowgfx.conf start on starting unity7 pre-start script #initctl set-env --global UNITY_LOW_GFX_MODE=1 initctl set-env --global LIBGL_ALWAYS_SOFTWARE=1 end script EOF 2) Run unity with: COMPIZ_CONFIG_PROFILE=ubuntu-lowgfx On login unity should use opaque views (dash, switcher, launcher, shortcut-dialogs) with no fading and reduced effects. Windows should also use smaller shadows. [Regression potential] Some settings from unity-control-center couldn't be applied to normal profile. Low graphics mode might be used as normal one. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1598770/+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 1212337] Re: accounts-daemon crashed with SIGSEGV in dbus_connection_send()
Hello. It seems, that this problem still is not fixed in 12.04 LTS Release (e.g. Xubuntu: yes, I know it has EoL status). `accountsservice` crashing every time after every user logs in. But it seems, that "solution" is to disable `apport` via '/etc/default/apport' file. It's pretty simple: 1) edit apport file; $ sudo leafpad /etc/default/apport 2) change 'enabled=1' option to 'enabled=0' 3) save and exit. That's all. After system restart etc., and user login, `accountsservice` crash does not occur. As I already mentioned: Xubuntu 12.04 LTS is EoL and it seems that this issue is fixed in Ubuntu (see above table with 'Affects', 'Status', 'Importance' etc. rows). Best regards. ** Summary changed: - accounts-daemon crashed with SIGSEGV in dbus_connection_send() + [Partial Solved] accounts-daemon crashed with SIGSEGV in dbus_connection_send() -- You received this bug notification because you are a member of DX Packages, which is subscribed to accountsservice in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1212337 Title: [Partial Solved] accounts-daemon crashed with SIGSEGV in dbus_connection_send() Status in accountsservice package in Ubuntu: Fix Released Status in accountsservice source package in Precise: Confirmed Bug description: Hi. There appeared some problems with 'accountsservice' -- a D-Bus interface for user account query and manipulation, that honestly have occurred day-to-day. ### PROBLEM DESCRIPTION: A few weeks ago after login as a normal user, 'accountsservice' (used for querying and manipulating user account informations) crashed. On the beginning it was a random incident. After a few days, 'accountsservice' crashed each time after every user logs on. I think, that's all what I can write, to try to describe this issue, because everything seems to be okay -- no system freezing or slowdowns, no problems after packages update/upgrade etc. ### DETAILED INFORMATIONS: == * ProblemType: Crash * Uname: Linux 3.2.0-51-generic-pae i686 * Architecture: i386 * DistroRelease: Ubuntu 12.04 (Xubuntu 12.04 variant) * Package: accountsservice 0.6.15-2ubuntu9.6 * ApportVersion: 2.0.1-0ubuntu17.4 * NonfreeKernelModules: nvidia * Segfault happened at: 0xb76bb7c3: mov0x10(%eax),%eax * Executable Path (ProcCmdline): /usr/lib/accountsservice/accounts-daemon Also '/var/log/apport.log' file contain some informations about this issue. Everything is in a attached log file. ,-[ $ lsb_release -rd ] | Description:Ubuntu 12.04.3 LTS | Release:12.04 `- ### WHAT HAVE HAD AN IMPACT ON THIS ISSUE? == I have no ideas, why it started to happen. Only one thing, which I've done for a few weeks before problems with 'accountsservice' was 'conky-all' install. Nothing more, nothing less -- no serious administrative tasks were performed (except e.g. kernel or programs updates via APT utility or UpdateManager, but it seems to be obvious). ### APPENDIX: = I would like to notice, that this issue still occurs, after next point Xubuntu update -- from 12.04.2 to 12.04.3 version. So for now, kernel version is; 3.2.0-55-generic-pae. Anything related with this bug, when all of this started to happen, remains unchanged. One more, important, thing to mention is that - in my case - 'accountsservices' crashed even after a fresh Xubuntu 12.04 install. For more info, please see comment #12. Best regards. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1212337/+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 1436405] Re: Duplicate menu (both unity and in-app) for Qt5 apps
I've logged a bug with Qt. https://bugreports.qt.io/browse/QTBUG-54793 -- You received this bug notification because you are a member of DX Packages, which is subscribed to appmenu-qt5 in Ubuntu. https://bugs.launchpad.net/bugs/1436405 Title: Duplicate menu (both unity and in-app) for Qt5 apps Status in One Hundred Papercuts: Confirmed Status in appmenu-qt5 package in Ubuntu: Confirmed Status in libdbusmenu-qt package in Ubuntu: Confirmed Bug description: At least konsole and khelpcenter suffers from this bug: Start the app inside the default Unity environment (not under KDE). Notice that the app's menubar appears twice. Once in the upper row of the whole desktop, as expected and as it is for every Gnome app. And also inside the application's window, wasting precious screen real estate. In Utopic, at least for konsole, I'm quite sure that the menu wasn't duplicated inside the app, it only appeared on the desktop's top Unity bar. (I'm not sure I guessed the component right; please reassign as appropriate.) ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: libdbusmenu-qt5 0.9.3+14.10.20140619-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2 Uname: Linux 3.19.0-10-generic x86_64 ApportVersion: 2.16.2-0ubuntu4 Architecture: amd64 CurrentDesktop: Unity Date: Wed Mar 25 16:33:14 2015 InstallationDate: Installed on 2012-05-30 (1028 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) SourcePackage: libdbusmenu-qt UpgradeStatus: Upgraded to vivid on 2015-03-17 (7 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1436405/+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 1436405] Re: Duplicate menu (both unity and in-app) for Qt5 apps
I believe the issue may lie with Qt. QMenuBar only supports "native" menu bars in OSX & windows CE as stated in http://doc.qt.io/qt-5/qmenubar.html#nativeMenuBar-prop This causes calls to QMenuBar::setVisible to fall through to QWidget::setVisible which then sets the menu bar visual component of the app window to visible. -- You received this bug notification because you are a member of DX Packages, which is subscribed to appmenu-qt5 in Ubuntu. https://bugs.launchpad.net/bugs/1436405 Title: Duplicate menu (both unity and in-app) for Qt5 apps Status in One Hundred Papercuts: Confirmed Status in appmenu-qt5 package in Ubuntu: Confirmed Status in libdbusmenu-qt package in Ubuntu: Confirmed Bug description: At least konsole and khelpcenter suffers from this bug: Start the app inside the default Unity environment (not under KDE). Notice that the app's menubar appears twice. Once in the upper row of the whole desktop, as expected and as it is for every Gnome app. And also inside the application's window, wasting precious screen real estate. In Utopic, at least for konsole, I'm quite sure that the menu wasn't duplicated inside the app, it only appeared on the desktop's top Unity bar. (I'm not sure I guessed the component right; please reassign as appropriate.) ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: libdbusmenu-qt5 0.9.3+14.10.20140619-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2 Uname: Linux 3.19.0-10-generic x86_64 ApportVersion: 2.16.2-0ubuntu4 Architecture: amd64 CurrentDesktop: Unity Date: Wed Mar 25 16:33:14 2015 InstallationDate: Installed on 2012-05-30 (1028 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) SourcePackage: libdbusmenu-qt UpgradeStatus: Upgraded to vivid on 2015-03-17 (7 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1436405/+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
