Sorry for the comment spam. Last one. The difference between the working
and broken pc files is this:
x...@y:~$ diff pc.broken-jaunty pc.fixed-sergey
22,25c22
key BKSP {
type=CTRL+ALT,
symbols[Group1]= [ BackSpace, Terminate_Server ]
};
---
key BKSP { [
Sebastien
Upstream suggested it's an issue in xkeyboard-config _if_ the
/usr/share/X11/xkb/symbols/pc file provided didn't work.
I have just tested the file that Sergey attached to the upstream and it
works perfectly.
I think it's reasonable to assume the problem is our xkeyboard-config
** Attachment added: Newer working symbols/pc file from Upstream
http://launchpadlibrarian.net/31478756/pc.fixed-sergey
--
Cannot use Windows key in keyboard shortcuts
https://bugs.launchpad.net/bugs/12153
You received this bug notification because you are a member of Ubuntu
Bugs, which is a
Sebastien
I've just installed Karmic Alpha 5 under VirtualBox 3.0.4: it is even
more broken.
It recognises left Windows key + R as Alt + R (Alt + R comes up as
Alt + R, too).
It recognises right Windows key as ISO Level 3 Shift and won't accept
a modifier.
The XKB xprop settings are the same
The second upstream bug I created has run its course:
http://bugzilla.gnome.org/show_bug.cgi?id=579658
Suggestion is that the symbols/pc file is out of date. I will test this
on my Jaunty. Others, how does it work for you?
Remember NOT to use Super is mapped to Win keys when testing this.
That
As I understand it, the problem is that Nautilus doesn't show the
default directory on FTP login, leaving the user to guess their path.
The upstream fixed a problem whereby the user wouldn't be able to enter
their path, once guessed... so I guess we've got a workaround.
As the upstream (can't
I agree re removing this package or replacing it with another until this
is fixed. It is insecure and I cannot see why many would use it without
SSL. With SSL it's great, but if we have to repackage ourselves each
time we install it may as well not be in the repository...
--
IMAP/POP3+SSL/TLS
I have just raised it downstream:
http://bugzilla.gnome.org/show_bug.cgi?id=589028
I'm not sure how to tag this bug with downstream info, otherwise I
would.
** Bug watch added: GNOME Bug Tracker #589028
http://bugzilla.gnome.org/show_bug.cgi?id=589028
--
gvfsd-archive doesn't handle
Great comment, Sam. This is getting complicated. Can I propose a simple
solution?
In comment 103 of this I described the original upstream bug:
http://bugzilla.gnome.org/show_bug.cgi?id=165343
The maintainer insist it's fixed but I disagreed, so I opened another
against libgnomekbd as per his
Sergio, thanks for your comments.
I have just tried the laptop again in scenario #2 with the release 9.04
as described, and it appeared to undock and redock without incident. I
don't have the time to work through each of the scenarios at the moment,
but I will get back to this bug when I do.
I think the problem _is_ how the panel behaves when it is resized. Have
a look at the first comments.
There's a workaround with gconf which makes the panel's handling much
more graceful, but this is analogous to Windows users having to edit the
registry to be able to change resolutions nicely. It
That's a workaround, not a fix, and has been mentioned in this and the
upstream tickets.
It's fixed when it's not broken out of the box.
--
Cannot use Windows key in keyboard shortcuts
https://bugs.launchpad.net/bugs/12153
You received this bug notification because you are a member of Ubuntu
Yes -- broken on Hardy, Intrepid and Jaunty. Changing Super is mapped
to Win keys fixes it.
Is this really an issue for GNOME now, rather than a default
configuration issue with Ubuntu?
I don't see how bug #1 will ever get fixed with this one open. It's
nothing to do with unusual keyboards: it's
Original upstream http://bugzilla.gnome.org/show_bug.cgi?id=165343 is
still marked as fixed; some disagreement as to what that bug was about.
I have opened a new upstream bug in libgnomekbd over the default
layouts, as per Nelson's comment above.
http://bugzilla.gnome.org/show_bug.cgi?id=579658
Backtrace attached.
k...@stumpy:~$ apt-cache policy gvfs-backends
gvfs-backends:
Installed: 1.2.1-0ubuntu1
Candidate: 1.2.1-0ubuntu1
Version table:
*** 1.2.1-0ubuntu1 0
500 http://gb.archive.ubuntu.com jaunty/main Packages
100 /var/lib/dpkg/status
** Attachment added:
Public bug reported:
Binary package hint: computer-janitor
Computer Janitor may list the same package for removal twice, if there
are two reasons to remove it.
For example, I have libawn0-bzr shown twice when I run CJ. When
selected, the first entry reads: Package is not longer supported
[etc.]
I have not been able to replicate this. There was likely a post-install
failure and your suspicion is correct. Invalid is fine, thanks. :-)
--
computer-janitor handles dpkg errors poorly
https://bugs.launchpad.net/bugs/36
You received this bug notification because you are a member of Ubuntu
Thanks duanedesign. This is still a problem for me with my Sony VGN-
SZ3XWP in Sony docking station.
Jaunty 9.04, up to date as of today:
k...@stumpy:~$ uname -ar
Linux stumpy 2.6.28-11-generic #40-Ubuntu SMP Fri Apr 3 17:39:51 UTC 2009 i686
GNU/Linux
k...@stumpy:~$ dpkg -l | grep kernel |
I think this relates to and may be a dupe of #44082.
--
applets constantly mix up and slip
https://bugs.launchpad.net/bugs/96071
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Good to see the workarounds. However, this is still broken out of the
box in Jaunty.
I have attached a screenshot with panel at 1920 width, then downsized to
1280 without any interference.
For some reason my two right-side controls (workspace switcher, window
selector) get moved into the middle
I believe the specific error first reported in this bug Unknown symbol
tifm_has_ms_pif has gone with the moves to Hardy, Intrepid, Jaunty. The
later tifm messages look like duplicates of #222557.
--
tifm_ms: Unknown symbol tifm_has_ms_pif
https://bugs.launchpad.net/bugs/159951
You received this
Surely this is a duplicate of #222557?
--
Sony Laptop Memory Stick Reader doesn't work
https://bugs.launchpad.net/bugs/48987
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
FWIW it wasn't working for me in 8.10 prior to upgrade a fortnight ago,
either.
--
Vaio VGN-SZ3XWP docking station cant hot dock/undock.
https://bugs.launchpad.net/bugs/163211
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
With an in-built Sony VGN-SZ3XWP it didn't work in 8.10, and doesn't
work in 9.04, which just says:
tifm_core: MemoryStick card detected in socket 0:0
This is very similar to #48987 and #159951.
--
MemStick problem with card_reader (tifm)
https://bugs.launchpad.net/bugs/222557
You received
** Visibility changed to: Public
--
gvfsd-archive doesn't handle deletion of mounted remote files
https://bugs.launchpad.net/bugs/355674
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Public bug reported:
Binary package hint: computer-janitor
computer-janitor fires up with a list of about 25 fixes to make, most
of which are 3rd-party packages that I'd like to keep.
Remove/fix? is selected by default for all fixes, but I only want
the first 2. Thus I have 23 checkboxes to
Public bug reported:
Binary package hint: computer-janitor
computer-janitor does not say what it will do with selected items. For
example: .dpkg-old files.
The top part of the form says This applications helps you to find and
remove software..., but the first column in the listbox says
Public bug reported:
Binary package hint: computer-janitor
Sometimes computer-janitor fails when removing packages, with:
Could not clean up properly
E:Sub-process /usr/bin/dpkg returned an error code (1)
This error message is not clear. On running the application again, it
removed the
Whilst this was fine in Hardy (at least, it showed 1TB free), it is
broken again in Intrepid and now shows 0.0K. Nautilus could copy files
to sshfs mounts as it always saw free space in Hardy -- under Intrepid
it refuses, as it sees no space.
--
sshfs mounted drives do not show correct size and
29 matches
Mail list logo