Yes, it's very inconvenient that good old 'cal -m' or 'cal -3m' doesn't
work in Ubuntu.
Are any workarounds e.g. to get sources (where?) and compile right
version of cal which support -m or -M option?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscri
Chris, it seems that correct bug report for our current problems is bug
1049282 (https://bugs.launchpad.net/ubuntu/+source/indicator-
multiload/+bug/1049282), you can subsribe there.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
http
Thanks, Andy! Seems to work fine. I had to use "256" as "VelocityScale"
(with 32 it's too slow for me), and it makes synaptiks unusable, but
everything else is fine.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpa
Same as comment #49: leak is not fixed in indicator-multiload
0.3-0+66~33~17~precise1, unity5.16.0-0ubuntu1, compiz
1:0.9.7.8-0ubuntu1.4
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/779717
Title:
12.04 is also affected. Note also the following thread on x230 which may
or may not be related to this bug: http://forum.notebookreview.com
/lenovo-ibm/676519-x230-trackpoint-issue-very-choppy-not-smooth-all-
normal.html . On my laptop, touchpad works fine under Windows, so it
seems to be driver is
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/974424
Title:
keybindings don't work for non-English layouts
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ter
Public bug reported:
Keybindings which involves alphabetical characters (like Ctrl+Shift+T
for new tab) don't work when non-English (e.g. cyrillic) layout is
active, which is very annoing.
[user@xennie user #333]$ lsb_release -rd ~
Description:Ubuntu precise (development branch)
Release:
** Summary changed:
- next_tab and prev_tab keybindings stop working if changed from default
+ next_tab and prev_tab keybindings stop working if changed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/9
** Visibility changed to: Public
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/973584
Title:
compiz crashed with SIGSEGV in std::basic_string, std::allocator >::basic_string()
To manage notificatio
** Visibility changed to: Public
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/974099
Title:
synapse crashed with SIGSEGV in g_markup_escape_text()
To manage notifications about this bug go to:
htt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/974060
Title:
next_tab and prev_tab keybindings stop working if changed from default
To manage notifications about this bug go to:
https://bugs.launchpa
Public bug reported:
When I'm trying to change the default keybindings for "Switch to the
next tab" and "Switch to previous tab" (next_tab and prev_tab), new
bindings don't work. When I open "Preferences" dialog again, it says
that keybindings for this actions are "Disabled". Restoring default
val
This also may be related to
https://bugs.launchpad.net/ubuntu/+source/wmctrl/+bug/582348, but I'm
not sure.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/971147
Title:
xdotool and wmctrl don't move
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/971147
Title:
xdotool and wmctrl don't move and resize windows after they are
(semi)maximized
To manage notifications about this bug go to:
https://bu
Public bug reported:
The command
/usr/bin/xdotool windowmove `/usr/bin/xdotool getwindowfocus` 0 0
is supposed to move currenly selected window to the top left corner. It
works fine on clean start, but after I maximize (or half-maximize) and
then restore some window, it becomes "broken", and thi
15 matches
Mail list logo