Daily测试中，Dash中的Fcitx输入法切换一直有问题：首次点击进入Dash主页，Fcitx输入法可正常切换使用；一旦切入Dash其它页面，或者再切回Dash主页，Fcitx输入法均无法切换使用，使用"ctrl+空格"进行切换时无响应，只能输入英文字母。此问题存在很久了，一直未被解决。
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to nux in Ubuntu.
Matching subscriptions: dx-packag
Here's a debdiff incorporating the proposed patch.
** Patch added: "Proposed debdiff for trusty"
https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/907640/+attachment/3954813/+files/metacity_2.34.13-0ubuntu4.debdiff
--
You received this bug notification because you are a member of DX
Pa
** Also affects: metacity (Ubuntu)
Importance: Undecided
Status: New
--
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/907640
Title:
alt-backtick doesn't work properly
Status in A
** Attachment added: "The .desktop-file"
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1271729/+attachment/3954702/+files/Mean%20Streets.desktop
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions
Public bug reported:
Ubuntu: 13.10
Unity: 7.1.2+13.10.20131014.1-0ubuntu1
- Creating a fully compatible .desktop file in Ubuntu 13.10 and placing
it in either ~/.local/share/applications or /usr/share/applications
doesn't generate an icon in Unity.
- However, copying an exisiting launcher and ed
** Changed in: unity
Status: In Progress => Triaged
** Changed in: unity (Ubuntu)
Status: In Progress => Triaged
--
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
Public bug reported:
When the monitor is disconnected I still have windows that are indicated as on
a different desktop, but in fact they are on the same desktop.
This doesn't change until I close and reopen them :/
** Affects: unity (Ubuntu)
Importance: Undecided
Status: New
**
Since the developers think it's a bug in Unity, assigning to the correct
package.
** Package changed: ktorrent (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
htt
You have been subscribed to a public bug:
This bug was previously reported to KDE here:
https://bugs.kde.org/show_bug.cgi?id=305816
We have concluded that the bug is likely in Unity.
The following is a copy-and-paste of the original report (please see the page
above for more details and a short
Mirco, could you have a look to that one?
** Changed in: notify-osd (Ubuntu)
Assignee: (unassigned) => Mirco Müller (macslow)
** Summary changed:
- volume indicator placement issue on multimonitor system
+ incorrect placement on multimonitor systems with focus-follow on
--
You received th
Confirmed, that's an issue with multimonitor focus-follow, which is now
the default in trusty. That bug should be fixed this cycle since the
default change made it quite visible
** Changed in: notify-osd (Ubuntu)
Status: New => Confirmed
** Changed in: notify-osd (Ubuntu)
Importance: Un
** Changed in: notify-osd
Status: Confirmed => Fix Released
--
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/904835
Title:
notify-osd keeps on w
Maybe we should reopen thi bug, today I had this problem again, after a
hard reboot (REISUB). Killing unity panel service worked fine to restore
the clock.
using Ubuntu 13.10 with latest updates.
--
You received this bug notification because you are a member of DX
Packages, which is subscribed t
And here's my systemd-shim.log (see Martin's comment #88). Just like
Christian, I do not have to press Ctrl+C, it exits a few moments after
resuming and entering the user password.
** Attachment added: "Suspended using Unity menu"
https://bugs.launchpad.net/ubuntu/+source/systemd-shim/+bug/125
Still occurs on trusty. Anybody working on this?
** Tags added: 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, dx-packages
https://bugs.launchpad.net/bugs/646029
Title:
Menu bar
I have 6-0ubuntu0.13.10.
Please see the attached nm.log that I created as Martin described in #82.
I had to wait some time after "sudo Networkmanager ..." until my wifi was
connected. Then I suspended which took the usual while. After resume, the
network was disconnected as usual. I didn't have
I attached a logfile (without timestamps, because I don't know how) that
was recorded during "sudo gdbus call -y -d [...]", 30 seconds of
waiting, resuming the computer from standby and entering the password.
** Attachment added: "logfile for sudo gdbus call -y -d"
https://bugs.launchpad.net/u
I can't reproduce the working state now with 10 tries. And all those
logs of broken resuming only have a single suspend.target call.
--
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/125212
Thank you for your answer. I will try to do that, however I don't know
much about D-BUS. I managed to activate the system bus logging and dbus-
monitor outputs a lot now. However that's too much for my console
window and it is without timestamps. How can I get a useful logfile that
I can upload he
I am seeing this occasionally (13.10 32 bit). killall unity-panel-
service restores it.
--
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/1244285
I concur with zob. Bug is still present in January 23rd build, and is
very unprofessional. With new users coming in this year due to the
publicity boost Linux has received in the gaming sector, it is advisable
to remove this sort of amateurish mistake, to create the best
impression.
--
You receiv
I can confirm that the tz is not updated, but toggling seconds or 12/24
doesn't fix it here ... changing the auto-detection one does it though
** Changed in: indicator-datetime (Ubuntu)
Importance: Undecided => High
** Changed in: indicator-datetime (Ubuntu)
Status: New => Confirmed
**
** Description changed:
indicator-datetime 13.10.0+13.10.20131023.2-0ubuntu1, Ubuntu 13.10
1. Open "System Settings" > "Time & Date".
2. Change the time zone. (And if bug 1102890 has been fixed, choose "Apply".)
3. Look at the clock in the menu bar.
+ 4. In the "Clock" tab, toggle any o
The same symptoms recurred in Ubuntu 13.10, now reported as bug 1271484.
--
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/735445
Title:
clock d
Public bug reported:
indicator-datetime 13.10.0+13.10.20131023.2-0ubuntu1, Ubuntu 13.10
1. Open "System Settings" > "Time & Date".
2. Change the time zone. (And if bug 1102890 has been fixed, choose "Apply".)
3. Look at the clock in the menu bar.
What happens: The clock still shows the time in t
** Summary changed:
- Add OK button and Cancel button in indicator-datetime setting
+ Too difficult to undo mistaken change to time/date settings
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-datetime in Ubuntu.
Matching subscript
Setting back to "New" - I responded to the feedback.
** Changed in: compiz
Status: Expired => New
** Changed in: unity (Ubuntu)
Status: Expired => New
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to unity in Ubuntu.
Matching su
So in systemd-shim3.log StartUnit('suspend.target') is called once,
while in systemd-shim2.log it's called twice. Are you sure that systemd-
shim2.log was the one where things worked properly? It seems much more
likely to me that calling StartUnit('suspend.target') twice in short
succession might c
Here network manager resumed properly.
** Attachment added: "systemd-shim2.log"
https://bugs.launchpad.net/ubuntu/+source/systemd-shim/+bug/1252121/+attachment/3954187/+files/systemd-shim2.log
--
You received this bug notification because you are a member of DX
Packages, which is subscribed
Seems that in some cases (1 in 5 tries) networkmanager resumes. Attached
is the case when it does not resume.
Note that I don't have to press ctrl+c to stop logging; it exits itself.
** Attachment added: "systemd-shim3.log"
https://bugs.launchpad.net/ubuntu/+source/systemd-shim/+bug/1252121/+
Thanks Christian. So this is yet another bug than the one that Daniel
and Rafael are experiencing.
First, please ensure (dpkg -l systemd-shim) that you have version 6-...
installed. If you do, please run this
sudo G_DBUS_DEBUG=all annotate-output /usr/lib/*/systemd-shim 2>&1 |
tee /tmp/systemd-
The signal is really missing. Attached is the dbus log when closing and
opening the lid.
** Attachment added: "dbus-lid.log"
https://bugs.launchpad.net/ubuntu/+source/systemd-shim/+bug/1252121/+attachment/3954133/+files/dbus-lid.log
--
You received this bug notification because you are a mem
32 matches
Mail list logo
