Public bug reported:
I've upgraded from precise to trusty a few weeks ago and I'm not able to
use unity anymore. If I choose "Ubuntu" on lightdm, I got only my
desktop screen, with no dash nor top bar, just my desktop icons. If I
open any window, The window appears with no title bar.
To report th
** 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/1268146
Title:
Very high cpu usage for compi
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
look at all reported bugs in a timely manner. There have been many
changes in Ubuntu since that time you reported the bug and your problem
may have been fixed
Can anyone still reproduce this bug?
** Changed in: ubuntukylin
Milestone: trusty-beta1 => trusty-final-beta-freeze
--
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.
Actually, it looks like this broke at some point in unity7 too.
Given that nobody else is asking for this, and since the work to support
it is growing past the one-paragraph-of-code level of effort, I'm going
to mark this as a WontFix.
** Changed in: libindicator
Status: Confirmed => Won't
** Changed in: indicator-datetime (Ubuntu)
Status: Confirmed => 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/861236
Title:
** Package changed: indicator-datetime (Ubuntu) => unity-control-center
(Ubuntu)
--
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/1187981
Title:
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
look at all reported bugs in a timely manner. There have been many
changes in Ubuntu since that time you reported the bug and your problem
may have been fixed
Valgrind is showing a clean bill of health when I test with 14.04 trunk
now.
** Changed in: indicator-datetime (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-datetime in Ubuntu.
Matching
** Package changed: indicator-datetime (Ubuntu) => unity-control-center
(Ubuntu)
--
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/1173563
Title:
There have been many changes in indicator-datetime since this bug was
reported. In particular it no longer uses dbusmenu at all, so the
codepath in this crash no longer exists.
If issues persist for you on a currently supported Ubuntu version,
please report them in new bug tickets. Thank you!
**
*** This bug is a duplicate of bug 1197645 ***
https://bugs.launchpad.net/bugs/1197645
** This bug is no longer a duplicate of private bug 1211548
** This bug has been marked a duplicate of bug 1197645
indicator-datetime-service crashed with SIGSEGV in
cal_client_emit_backend_property_chan
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
However, processing it in order to get sufficient information for the
developers failed (it does not generate an useful symbolic stack trace).
This might be caused by some outdated packages which were installed on
Hi Barry,
Is this still an issue in Trusty? I rewrote the sleep/skew detection
code post-13.10 so if you have a convenient setup I'd love to hear how
this goes.
** Changed in: indicator-datetime (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you ar
** Summary changed:
- indicator-datetime-service crashed with SIGSEGV in g_object_ref()
+ indicator-datetime-service crashed with SIGSEGV in
cal_client_emit_backend_property_changed_idle_cb()
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to i
This was never a supported feature, but it's a neat idea and I wouldn't
be against re-enabling this.
The old indicator-datetime code set the label text this way:
>gboolean use_markup = FALSE;
>if (pango_parse_markup(timestr, -1, 0, NULL, NULL, NULL, NULL))
>use_mar
** Changed in: indicator-datetime (Ubuntu)
Status: New => Confirmed
** Also affects: libindicator
Importance: Undecided
Status: New
** Changed in: libindicator
Status: New => Confirmed
** Changed in: libindicator
Importance: Undecided => Wishlist
** Changed in: indica
** Package changed: indicator-datetime (Ubuntu) => unity-control-center
(Ubuntu)
--
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/1205620
Title:
*** This bug is a duplicate of bug 966658 ***
https://bugs.launchpad.net/bugs/966658
** This bug has been marked a duplicate of bug 966658
Indicator Date Time shows clocks that have been deleted from the list.
--
You received this bug notification because you are a member of DX
Packages,
I don't believe this merits the "High" importance under the guidelines
of https://wiki.ubuntu.com/Bugs/Bug%20importances... this doesn't have a
severe impact on users, make a default Ubuntu installation generally
unusable, etc.
One could argue this is a Low importance but (ie, there is an easy
wor
Charles: I'm sorry, I don't really remember if I removed those packages
— maybe I did by accident. Since I reported this problem I've upgraded
to Trusty and never faced it again.
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-sessio
Public bug reported:
shutdown while testing a dbus-monitor script to work around a problem in in my
java app :)
Seems like your logoff is pretty broken, a simple test java app with a jframe
and a shutdown hook (only) always returns non-zero on logoff (and doesn't run
the hook) and other gnome p
Thanks for reporting this bug and helping to make Ubuntu better.
This crash appears to be caused by a configuration error:
org.gnome.Evolution.DefaultSources is provided by evolution-data-server-
common, which is required by evolution-data-server, which is required by
indicator-datetime. So if the
*** This bug is a duplicate of bug 1055166 ***
https://bugs.launchpad.net/bugs/1055166
Public bug reported:
The Ubuntu Error Tracker has been receiving reports about a problem
regarding unity. This problem was most recently seen with version
7.1.2+14.04.20140303-0ubuntu1, the problem page at
*** This bug is a duplicate of bug 1055166 ***
https://bugs.launchpad.net/bugs/1055166
** This bug has been marked a duplicate of bug 1055166
compiz crashed with SIGSEGV in memmove() from drisw_update_tex_buffer() from
dri_set_tex_buffer2() from operator() from compiz::opengl::bindTexImage
Hi Rick,
If you ssh into the phablet and run "url-dispatcher settings:///system
/time-date" (you may need to install url-dispatcher-tools to pick up the
command-line app), does the settings panel launch for you? This is a
command-line version of the same call that datetime makes.
FWIW, I did a fr
** Summary changed:
- J. Random User Showing In Unity Power Menu Indicator
+ J. Random User Showing In Session Indicator
** Package changed: ido (Ubuntu) => indicator-session (Ubuntu)
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to ido in Ub
This bug was fixed in the package unity - 7.1.2+14.04.20140305-0ubuntu1
---
unity (7.1.2+14.04.20140305-0ubuntu1) trusty; urgency=low
[ Chris Townsend ]
* Fix more Panel Autopilot test failures. (LP: #1287745)
[ William Hua ]
* Improve debug logging for gnome key grabber.
This bug was fixed in the package unity - 7.1.2+14.04.20140305-0ubuntu1
---
unity (7.1.2+14.04.20140305-0ubuntu1) trusty; urgency=low
[ Chris Townsend ]
* Fix more Panel Autopilot test failures. (LP: #1287745)
[ William Hua ]
* Improve debug logging for gnome key grabber.
This bug was fixed in the package unity - 7.1.2+14.04.20140305-0ubuntu1
---
unity (7.1.2+14.04.20140305-0ubuntu1) trusty; urgency=low
[ Chris Townsend ]
* Fix more Panel Autopilot test failures. (LP: #1287745)
[ William Hua ]
* Improve debug logging for gnome key grabber.
This bug was fixed in the package unity - 7.1.2+14.04.20140305-0ubuntu1
---
unity (7.1.2+14.04.20140305-0ubuntu1) trusty; urgency=low
[ Chris Townsend ]
* Fix more Panel Autopilot test failures. (LP: #1287745)
[ William Hua ]
* Improve debug logging for gnome key grabber.
This bug was fixed in the package unity - 7.1.2+14.04.20140305-0ubuntu1
---
unity (7.1.2+14.04.20140305-0ubuntu1) trusty; urgency=low
[ Chris Townsend ]
* Fix more Panel Autopilot test failures. (LP: #1287745)
[ William Hua ]
* Improve debug logging for gnome key grabber.
Thank you for your bug report, that's a known issue and Marco said he's
working on it
** Package changed: gnome-keyring (Ubuntu) => unity (Ubuntu)
** Changed in: unity (Ubuntu)
Importance: Undecided => High
** Changed in: unity (Ubuntu)
Status: New => Triaged
** Changed in: unity (Ubu
You have been subscribed to a public bug:
Running Trusty and after my last set of updates, I'm seeing the the
'Cancel' button in the 'Unlock private key' dialog floating above the
text from the tick box so it looks like: 'Automatically unlock this key
whenever I'm lo[Cancel]'
** Affects: unity (U
*** This bug is a duplicate of bug 1275379 ***
https://bugs.launchpad.net/bugs/1275379
** This bug has been marked a duplicate of bug 1275379
unity_support_test crashed with SIGSEGV in __GI___pthread_mutex_lock()
--
You received this bug notification because you are a member of DX
Package
** Changed in: indicator-datetime
Status: Fix Committed => Fix Released
--
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/465689
Title:
U
So's happening here is that indicator-datetime-service stopped for
whatever reason and wasn't restarted by the system. If the problem was
repeatable, we could try to figure out why it stopped in the first
place. Fortunately, Ted Gould's upstart coding this cycle has fixed the
restarting problem.
T
Zsombor, I think so this is good enough for now, since qtorganizer5-eds
currently generates all its icaltimes as floating (because of the use of
with icaltime_from_timet()).
Given more time, it would be nicer to handle both floating and non-
floating times there. But since the only current user is
** Changed in: indicator-sound
Status: In Progress => 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/829648
Title:
[ffe] No
*** This bug is a duplicate of bug 813139 ***
https://bugs.launchpad.net/bugs/813139
** This bug has been marked a duplicate of bug 813139
indicator-session-service crashed: Unable to get system bus
** Summary changed:
- indicator-session-service crashed with signal 5 in
g_simple_async_r
> #1 0x7fa61cfe7ee3 in g_signal_handler_disconnect (instance=0x21,
handler_id=140351430766768) at
/build/buildd/glib2.0-2.39.3/./gobject/gsignal.c:2572
That instance pointer is suspicious... possibly a NULL structure pointer
got dereferenced? Although it's an odd number...
--
You received t
This used to occur when an instance of indicator-session would try to
register itself on the system bus but would fail for some reason -- say,
if there was already an instance running that hadn't let go yet, or if
there was an issue with the bus. Variations of this crash message
happened for variou
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
The rest of the backtrace tells a more interesting tale; it looks like maybe
gtk-logout-helper was smashing the stack in a loop. gtk-logout-helper.c was
removed in the 13.10 release, so It would help us a lot if
Marking as incomplete pending feedback from Design.
mpt, any thoughts on this?
** Also affects: ayatana-design
Importance: Undecided
Status: New
** Changed in: indicator-session (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a me
** Branch linked: lp:~charlesk/indicator-session/lp-1212664
--
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-se
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
However, processing it in order to get sufficient information for the
developers failed (it does not generate an useful symbolic stack trace).
This might be caused by some outdated packages which were installed on
This is crashing with GSettings failing to find the
'org.gnome.desktop.lockdown' schema.
Do you have gsettings-desktop-schemas or gnome-screensaver installed?
** Summary changed:
- indicator-session-service crashed with signal 5 in g_object_new_valist()
+ indicator-session-service crashed with "
Public bug reported:
I just upgraded from Ubuntu 13.10 to the development Trusty Thar. When I
log in from the Unity Greeter, my session is opened by there are no
Unity components: launcher, top panel, dash.
What works: tty1-6, Nautilus (I see my desktop), Firefox, Gnome-Terminal, etc.
Everything
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://b
** Branch linked: lp:~townsend/unity/fix-lp1073990
--
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/1073990
Title:
AP test should be written as a unit test
** Changed in: unity
Status: Triaged => In Progress
** Changed in: unity (Ubuntu)
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.l
They should just use
org.freedesktop.DisplayManager
/org/freedesktop/DisplayManager/Session*
org.freedesktop.DisplayManager.Session
Lock
We can distropatch gnome-screensaver to forward the signal or "just"
patch the clients.
--
You received this bug notification because you are a member of DX
Pa
This bug was fixed in the package unity-control-center -
14.04.3+14.04.20140305.1-0ubuntu1
---
unity-control-center (14.04.3+14.04.20140305.1-0ubuntu1) trusty; urgency=low
[ Lars Uebernickel ]
* Add "Show sound volume in the menu bar" check box (LP: #829648)
-- Ubuntu daily relea
If the client talk directly to gnome-screensaver we cannot do that much.
A good client should use the standard freedesktop interface.
--
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://
$ dpkg-query --show compiz
compiz 1:0.9.11+14.04.20140303-0ubuntu1
$ dpkg-query --show unity
unity 7.1.2+14.04.20140303-0ubuntu1
This seems fix-released with those above versions. Note, that
1:0.9.11+14.04.20140214 has a *huge* changelog
** Changed in: unity (Ubuntu)
Status: Confirmed
Vladimir, thanks for this report. It's true that "Estimating..." is
quite long. (Though it's not the longest thing that can appear in an
indicator menu title: that honor belongs to your login name.)
It's important that we show something more than just the icon, for
people who are expecting to see
Is this going to get fixed in 13.10 where it was broken? Seriously,
this completely ruins the desktop.
--
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/124059
“Estimating…” is part of the spec, so bumping this ticket over to Design
** Also affects: ayatana-design
Importance: Undecided
Status: New
** Changed in: indicator-power (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of DX
Pack
In the landing PPA now https://launchpad.net/~ci-train-ppa-
service/+archive/landing-006/+packages
** Changed in: hud
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to hud in Ubuntu.
https://bugs.laun
This bug was fixed in the package indicator-sound -
12.10.2+14.04.20140305-0ubuntu1
---
indicator-sound (12.10.2+14.04.20140305-0ubuntu1) trusty; urgency=low
[ Lars Uebernickel ]
* Honor com.canonical.indicator.sound visible (LP: #829648)
-- Ubuntu daily releaseWed, 05 Mar 20
System settings are set to display in top panel, and not in window title
bars.
If a non maximised window is opened there are no menus on the window
title bar present, if the window is maximised then unmaximised, menus
are displayed in both top panel and window title bar.
--
You received this bug
This is also quite repeatable in Transmission. When I first show it
using the indicator menu, there are no menus displayed. In this
instance, the only way I can find to get the menus to work is to
maximize Transmission and then un-maximize it - the menus then appear,
at least until I open a pop-up
I'd prefer a mouse-free solution since I rarely use the mouse!
--
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/798445
Title:
can't discern between two file
The problem that's blocked me until now, in designing a solution for
this, is that a Do Not Disturb mode would so often be forgotten. To be
effective, you'd need to remember to turn it on every time you launched
the particular app, or went into the particular app mode, and turn it
off afterwards. A
Similar to #21 (m-gehre), I think rather than being able to disable
items, a better design would be to enable users to select a "default"
display device. That way everyone has access to the panel's
information, but each individual can determine the most important device
to display.
--
You receiv
Public bug reported:
When using locally integrated menus, Terminal app's name isn't displayed
in the title bar. Title bar only echoes the username@host prompt.
Ubuntu release: 14.04 64bit
package info: Unity 7.1.2+14.04.20140303-0ubuntu1
The expected output is that the window title should displa
Daniel Lombraña González, Please see
https://bugs.launchpad.net/ubuntu/+source/systemd-
shim/+bug/1184262/comments/151 .
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to systemd-shim in Ubuntu.
https://bugs.launchpad.net/bugs/1184262
Title:
Sending to systemd-shim for review. Please reassign if not a systemd-shim
issue. For background information, please see:
https://bugs.launchpad.net/ubuntu/+source/systemd-shim/+bug/1184262
** Package changed: linux (Ubuntu) => systemd-shim (Ubuntu)
** Changed in: systemd-shim (Ubuntu)
Sta
It seems a fundamental problem to me. Even without the duplicated name
problem, its pretty important to be able to see a file path to know
where is it located. The only way at the moment is to open it and then
do save as to see its path. A mouse over popping up the path would seem
the obvious solut
You have been subscribed to a public bug:
Waking from Sleep, Wireless Connections resume without delay, but the Ethernet
connection does not reactivate unless forced by command or by rebooting the
system.
the interface (very) occasionally resumes properly, but the reported condition
occurs >80%
I have the same problem with Ubuntu 13.10: just enabling/disabling
fullscreen gets me this problem: when disabling fullscreen, the parts
(the launcher to the left and the menu to the top) not used anymore by
the app (be it, in my case, Firefox or SublimeText) are not refreshed. I
have to unmaximize
Public bug reported:
The Ubuntu Error Tracker has been receiving reports about a problem
regarding unity. This problem was most recently seen with version
7.1.2+14.04.20140303-0ubuntu1, the problem page at
https://errors.ubuntu.com/problem/635e5bf8aacf144dbbed48d4662015571f4a
contains more de
** Changed in: unity (Ubuntu)
Importance: Undecided => High
** Changed in: unity (Ubuntu)
Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptio
** Changed in: unity8
Status: New => In Progress
--
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/1269409
Title:
Reenable closing apps from HUD
Status in Camera App:
In Progress
Status
*** This bug is a duplicate of bug 1282782 ***
https://bugs.launchpad.net/bugs/1282782
** This bug has been marked a duplicate of bug 1282782
Newest compiz/unity has decided that it owns my Alt key
--
You received this bug notification because you are a member of DX
Packages, which is sub
Public bug reported:
open several windows of one application type (gnome-terminal is good, but
anything will do)
hover over the launcher icon and use the mouse wheel to scroll between them,
raising windows one after another, scroll back and the sequence is not reversed.
rock the wheel back and f
Public bug reported:
I have two machines which have a number of strange behaviours from the
HUD key.
1) before attempting to change it away from its reported Alt_L setting,
both Alt_L and Alt_R were showing HUD.
2) I was able to move it way from Alt_L to Disable it ok, then it was
correctly Disa
I observe that the menu access keys are correctly disabled if
UBUNTU_MENUPROXY=0 is set in the environment, disabling the global menu
to revert to menu bar drawn within the gnome-terminal window.
Therefore, I've marked the bug as also affecting unity, as it seems
highly likely that at least some o
Oh, right. It's easy to change the unity setting to use its locker or
g-s, I'm not sure what it means for the clients though. Unity team, care
to comment on that?
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to unity in Ubuntu.
Matching subscr
Public bug reported:
(Long) Pressing the super (aka "windows") key displays the "Keyboard
Shortcuts" overlay. However, this summary does not show that Super+L is
now a shortcut for locking the screen.
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: unity 7.1.2+14.04.20140303-0ubuntu1
ProcVe
*** This bug is a duplicate of bug 1199571 ***
https://bugs.launchpad.net/bugs/1199571
** This bug has been marked a duplicate of bug 1199571
compiz crashed with SIGSEGV in af_latin_hints_compute_edges()
--
You received this bug notification because you are a member of DX
Packages, which
I can reproduce this bug on n4 with firmware in dev channel rel 194.
In my current test, my proposed branch in bug #1287599 can fix this bug,
too.
I'll make this bug fix committed if the proposed branch there is
approved and confirm still can fix this bug.
** Changed in: indicator-power (Ubuntu)
I was referring to "Note that the behaviour is configurable, so it's
easy to fallback to use gnome-screensaver" but having to patch things
doesn't sound that easy?
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to unity in Ubuntu.
Matching subsc
Not a lot of information to add, but from my experience this crash
happens randomly. I mean, it is when an icon with more than one window
opened is clicked (when it would scale the windows from that program
down and show all of them so I can select one), but sometimes I go days
without a reboot and
84 matches
Mail list logo