** Changed in: meson (Ubuntu Jammy)
Status: New => Won't Fix
** Changed in: openvswitch (Ubuntu Jammy)
Status: New => In Progress
** Changed in: spice-protocol (Ubuntu Jammy)
Status: New => Fix Committed
** Changed in: virglrenderer (Ubuntu Jammy)
Status: New => Fix
** Tags added: update-excuse
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gvfs in Ubuntu.
https://bugs.launchpad.net/bugs/1713098
Title:
Frequent DEP8 test failures related to ftp
To manage notifications about this bug go to:
** Tags added: update-excuse
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gvfs in Ubuntu.
https://bugs.launchpad.net/bugs/1875669
Title:
autopkgtest failures
To manage notifications about this bug go to:
Public bug reported:
Backport the following packages to the server-backports PPA for noble:*
['meson', 'dpdk', 'edk2', 'libslirp', 'libvirt', 'libvirt-python',
'openvswitch', 'qemu', 'rdma-core', 'seabios', 'spice', 'spice-
protocol', 'spice-vdagent', 'virglrenderer', 'virt-manager']
** Affects:
** Tags added: update-excuse
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to dbus-cpp in Ubuntu.
https://bugs.launchpad.net/bugs/1939065
Title:
autopkgtest failure in 0002-benchmark test
To manage notifications about this bug go
Public bug reported:
Most architectures are failing to build 5.0.3-2.
I've reproduced failure locally:
dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols
file: see diff output below
dpkg-gensymbols: warning: debian/libdbus-cpp5/DEBIAN/symbols doesn't match
completely
Public bug reported:
From https://launchpad.net/ubuntu/+source/dbus-cpp/5.0.3-2, it looks
like the build failed on all architectures except armhf, and on armhf
there was a test failure:
https://autopkgtest.ubuntu.com/results/autopkgtest-
Public bug reported:
https://autopkgtest.ubuntu.com/results/autopkgtest-
impish/impish/armhf/m/mutter/20210805_091629_afb25@/log.gz
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a
timestamp of 0 for 0x43
not ok 18 stacking/override-redirect.metatest
15:
Thanks Han, that makes sense that the issue is actually in the volume
monitor's (lack of) handling for autofs' transitory nature. I'll
reassign to that package for further investigation.
** Package changed: autofs (Ubuntu) => gvfs (Ubuntu)
--
You received this bug notification because you are
It sort of sounds like there is a race condition going on in the
consumption of the key sequence. I don't want to guess exactly what the
problem is in this particular case, but just as general X info (which
you probably already know...):
Keyboard input is processed through several levels...
I am not reproducing this bug on latest stable mutter.
mutter:
Installed: 3.34.3-1ubuntu1
01:00.0 VGA compatible controller:
Advanced Micro Devices, Inc. [AMD/ATI] Cape Verde PRO [Radeon HD 7750/8740 /
R7 250E] (rev 87)
I'm running a 6-head system on focal-devel, with gnome-shell/mutter and
I'm able to reproduce the faulty on bionic (not upgraded from xenial),
with GTK_IM_MODULE=xim and an empty .xinputrc.
Can also confirm the workaround suggested by Heiko L seems to fix this
issue, by changing /usr/share/themes/Ambiance/gtk-3.20/gtk.css to this:
> textview text {
>
I can't say for certain if the issue resides with ssh-askpass-fullscreen
or is a UI usability issue in unity, gnome, or elsewhere, however this
UI is not driven by OpenSSH itself, so I'll retarget this bugtask to
ssh-askpass-fullscreen as a slightly more likely candidate.
** Package changed:
I've inferred that the reporting process itself possibly interferes with the
misbehaviour. After submitting this report (before the terminal session was
closed, however) (began through a terminal session and not the Alt-F2 launcher,
using ubuntu-bug [PID of nautilus]) the reported behaviour is
Public bug reported:
I've recently upgraded from 18.10 to 19.04.
When I right-click on any folder the context menu has extra padding on the
bottom edge, below the 'properties' item. Performing the same action on files
doesn't produce the problem.
Strangely, while reporting this bug the noted
Thanks for clearing up that misconception, Daniel (at least for me; I
thought there was at least a sizable team employed by Canonical). I'll be
happy to run these versions and do some testing. I'll looking forward to
19.04/19.10, so I'll see how they are in their current state and report any
bugs
Will do.
On Tue, Feb 26, 2019, 9:00 PM Daniel van Vugt, <
daniel.van.v...@canonical.com> wrote:
> Bryce,
>
> I am not talking about an "issue" at all. If you are experiencing
> problems then please log new bugs for them.
>
> --
> You received this bug no
Might that be the same issue affecting the context menu (right click) when
using zoom? How does the drawing work for those menus?
On Tue, Feb 26, 2019, 8:35 PM Daniel van Vugt, <
daniel.van.v...@canonical.com> wrote:
> And it only occurred to me today that zoom performance should (and does
>
So to resolve the issue, the default package (which is deprecated) must be
manually changed?
Should I simply install gnome-shell-extensions to resolve it? I'm not clear on
what you mean, or why the issue is invalid.
As installed from the disc, the issue is present so I'm unsure what I'm
Public bug reported:
Behaviour observed in Ubuntu Cosmic 18.10
gnome-shell 3.30.2-0ubuntu1.18.10.1 from cosmic-proposed
The expected behaviour is for new icons to populate unoccupied cells
below the column, or occupy the first cell of a new column, or displace
other icons to maintain
If you look a few posts earlier in the thread, you'll see a guide on how to
test the proposed package. It shouldn't be long now before all users
receive the update. You won't need to reconfigure anything then.
On Mon, Feb 18, 2019, 4:05 PM Declan <1767...@bugs.launchpad.net wrote:
> Ok, I am on
followed instructions the first time I upgraded to the
proposed package the dependency failed to install. The package works now.
Should I submit a bug for the context-menu flickering?
-Bryce
Expected behaviour of system menu when zoom functionality enabled.
On 2019-02-17 8:59 p.m., Daniel van Vugt
I have an HD 5870.
I'm not using any additional or proprietary drivers (according to that tab in
Software & Updates); however, 'Proprietary drivers for devices' is enabled in
the Ubuntu Software tab in Software & Updates.
The only PPAs I have are for Google Chrome, PlayOnLinux, and Alexander
I can. It will need to happen this evening (+12 hours from this reply),
though.
On Wed, Feb 6, 2019, 1:30 AM Marco Trevisan (Treviño) Anyway, Bryce, can you give us context about your hw (graphic card,
> drivers, ppas? and versions)?
> Otherwise is probably hard to reproduce your issue,
** Tags removed: verification-done-cosmic
** Tags added: verification-failed-cosmic
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1767648
Title:
Top bar and shell dialogs are not
Yes, a warm reboot was performed after initial testing to confirm lack
of function. Cold booted this morning and the fix still does not work,
so I'm reverting to the previous package now. I'll go through the
process of reenabling -proposed when the next fix is released for other
testing
Unintentionally unassigned Cosmic from Daniel. Please reassign to
Daniel.
** Changed in: mutter (Ubuntu Cosmic)
Assignee: Daniel van Vugt (vanvugt) => Bryce (bryce-a-carson)
** Changed in: mutter (Ubuntu Cosmic)
Assignee: Bryce (bryce-a-carson) => (unassigned)
--
You re
Verified on Cosmic that mutter version 3.30.2-1~ubuntu.18.10.3 does NOT
fix the problem.
** Attachment added: "Proof of installation; proof of bug."
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1767648/+attachment/5235249/+files/Screenshot%20from%202019-02-01%2021-16-19.png
--
You
The original CR2 image from the camera is:
Exif.Image.XResolution Rational1 72
Exif.Image.YResolution Rational1 72
Exif.Image.ResolutionUnitShort 1 inch
But I use Darktable to process the raw image, and it's output
Public bug reported:
When sending images edited with Shotwell to Window's users, the
properties of the image show a vertical and horizontal resolution of 1
PPI. I'm assuming that this is a metadata mislabel and that the image
would have the same problem, but Shotwell does not show the PPI/DPI of
** Changed in: inkscape
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/1226962
Title:
Keyboard shortcuts (hotkeys) not
Public bug reported:
systemd-resolved returns a malformed packet when looking up an openpgp
key (via a cert record rfc4398) from my internal authoritative dns
server.
The command I used was gpg2 -v --auto-key-locate=clear,cert,local
--locate-keys [Email Address]
This works correctly if I change
@mpt yes, this is still an issue on Ubuntu 14.04LTS.
My /home partition fills up nearly every day (bad on an SSD also because of
write amplification).
-rw-r- 3151151104 Feb 4 13:06 gnome-session-Unity.log
The log spam is useuless repetive stuff like:
(putty:29947): GLib-CRITICAL **:
This seems to still be an issue: and it's a serious issue when a semi
public computer is involved, as those using the computer won't know the
password.
It is also a problem to train users to enter their password when a
prompt box comes up: that's just ripe for abuse.
See also:
Swap is the equivalent of main memory: the security issues are no
different. Nobody can complain about swap written to disk, as that's a
risk for any piece of main memory at any time. Why turn things so far
upside down to support an edge case (infinite scrollback left open for long
periods of
The oom killer will only come along if some epic long files have been
cat'ed to the terminal,
and infinite scrollback is selected. Speed, battery life, SSD life, energy
use and privacy are all reasons to have the common case be no disk writes.
--
You received this bug notification because you
How do you think gnome-terminal should handle that? Suppose you have 4
GB of ram, shall it consume up to 3 GB and then starting using the
disk? Sounds not only hard to implement, but also why should it take
away RAM from other apps?
The Linux virtual memory system is highly adept at swapping out
@Egmont wrote:
Running out of disk space is much less likely and effects the system less
badly than running out of RAM, and your RAM would eventually make it into the
disk (swap) anyways.
But I run out of ram space very rarely. It's highly elegant to keep
volatile data in RAM unless RAM is
Here's output of sudo strace -p XX where X is the process ID
of the misbehaving gvfsd-afp:
recvfrom(7, , 16, 0, NULL, NULL) = 0
poll([{fd=3, events=POLLIN}], 1, 0) = 0 (Timeout)
recvfrom(7, , 16, 0, NULL, NULL) = 0
poll([{fd=3, events=POLLIN}], 1, 0) = 0 (Timeout)
(The prior backtrace is under Ubuntu 14.04LTS fully patched) gvfs
Version: 1.20.1-1ubuntu1
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gvfs in Ubuntu.
https://bugs.launchpad.net/bugs/951585
Title:
gvfsd-afp consumes 100% of
See also http://ubuntuforums.org/showthread.php?t=1830432
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to vte in Ubuntu.
https://bugs.launchpad.net/bugs/1430620
Title:
gnome-terminal writes excessively to /tmp (affecting SSD
Public bug reported:
1) In a gnome-terminal run sudo fatrace -f W -t (filter for writes plus
timestamps).
2) In another window cat a file to the screen.
3) Observe the activity. I see large churn on the /tmp partitition:
20:41:24.158837 gnome-terminal(23352): W /tmp/#132835 (deleted)
Probably related, here's a small sample as captured by the new fatrace
--filter W utility on Ubuntu 14.04 LTS:
09:35:01.577176 gnome-terminal(8923): RW /tmp/#132358 (deleted)
09:35:01.588323 gnome-terminal(8923): W /tmp/#132359 (deleted)
09:35:01.588323 gnome-terminal(8923): RW /tmp/#132359
Public bug reported:
In Ubuntu 14.04LTS:
In system settings there's a control for Default applications for Web.
This does not appear to change the gnome-conf settings.
See attached screenshot.
Note how Firefox is shown in one place, Chrome in the other.
This in turn leads to incorrect behavior
*** This bug is a duplicate of bug 795985 ***
https://bugs.launchpad.net/bugs/795985
Still true as of Ubuntu 12.04.4 LTS,
with US English Locale and 101 Key Keyboard.
Neither the numbers above the keyboard, nor the numeric pad . work.
--
You received this bug notification because you are a
The problem for me was that it could not resolve my Exchange Servers
host name. Once I straightened that out it connected right away. I'm not
sure if that is your problem or not, but could it be?
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
This is NOT a duplicate of #1079953
And 12.04 is a LTS support version, so a fix for 13.10 is not relevant.
The proper URL for the stable release updates is
https://wiki.ubuntu.com/StableReleaseUpdates
The feature is completely broken in 12.04 LTS due tothe missing
dependency.
** This bug is
Using 12.04, fresh upgrade, fully patched:
alacarte launches but clicking *Properties* or *New Item* results in a crash.
Checking [x] report this error does nothing apparent.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to alacarte
And pressing HELP gives: The URI ‘ghelp:user-guide?menu-editor#menu-
editor’ does not point to a valid page.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to alacarte in Ubuntu.
https://bugs.launchpad.net/bugs/1079953
Title:
Main
Public bug reported:
While bug https://bugs.launchpad.net/ubuntu/+source/alacarte/+bug/1079953 is
closed,
the issue persists. With alacarte 0.13.2-2ubuntu4 on Ubuntu 12.04, nothing
works.
Pressing *New Item* or *Properties* results in a crash. Checkbox actions don't
take.
And inexplicably
https://bugs.launchpad.net/ubuntu/+source/alacarte/+bug/1251022
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to alacarte in Ubuntu.
https://bugs.launchpad.net/bugs/1079953
Title:
Main Menu Editor alacarte is Completely Broken in
** Information type changed from Private to Public
** Changed in: gnome-panel (Ubuntu)
Importance: Medium = High
** Changed in: gnome-panel (Ubuntu)
Status: Confirmed = Triaged
** Description changed:
gnome-panel crashed when I changed the theme from Ambiance to Radiance.
+
+
Seems to be easily reproducible on 12.04 (tested on several machines).
Found this googling around a bit, found https://mail.gnome.org/archives
/gtk-devel-list/2010-December/msg00065.html
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed
** Changed in: xkeyboard-config (Ubuntu Precise)
Assignee: Bryce Harrington (bryce) = (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gtk+2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/937822
Title:
[precise] F10
** Package changed: xorg (Ubuntu) = gnome-power-manager (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-power-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1154838
Title:
when I run the program brightness lock
** Also affects: gnome-disk-utility (Ubuntu Raring)
Importance: Undecided
Status: Confirmed
** Changed in: gnome-disk-utility (Ubuntu Raring)
Milestone: None = ubuntu-13.04
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed
** Tags added: raring
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/408903
Title:
Does not handle microphone mute button (KEY_MICMUTE)
To manage notifications
** Package changed: xorg (Ubuntu) = gnome-settings-daemon (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/1145689
Title:
error dialog due to problems
Sounds like a dupe of bug 1145689 (which has more detailed logs
attached).
Workaround would be to move aside ~/.config/monitors.xml (but attach it
here first).
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-settings-daemon in
** Also affects: hundredpapercuts/precise
Importance: Undecided
Status: New
** Also affects: hundredpapercuts/quantal
Importance: Undecided
Status: New
** Also affects: hundredpapercuts/raring
Importance: Undecided
Status: Confirmed
** Changed in:
Unless you narrow the problem to the X driver specifically, probably
better to just handle it as a gnome-power-manager issue.
** Package changed: xorg (Ubuntu) = gnome-power-manager (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
[Unsubscribing ubuntu-sponsors since it appears the posted patches need
further work.]
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/1065979
Title:
*** This bug is a duplicate of bug 1059316 ***
https://bugs.launchpad.net/bugs/1059316
** This bug is no longer a duplicate of bug 459637
totem assert failure: totem: /build/buildd/libdvdnav-4.1.3/src/vm/vm.c:863:
vm_get_video_aspect: Assertion `aspect == 0 || aspect == 3' failed.
** This
** Changed in: xorg-server (Ubuntu Hardy)
Assignee: Bryce Harrington (bryce) = (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm in Ubuntu.
https://bugs.launchpad.net/bugs/160264
Title:
[nvidia] compiz displays
@Roman, I mean details like verifying that you have the right version of
xkeyboard-config installed. You may need to reboot, as well.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gtk+2.0 in Ubuntu.
It's been long enough that there's probably not much value in completing
the oneiric backport.
** Changed in: gnome-control-center (Ubuntu Oneiric)
Status: Triaged = Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
** Package changed: xserver-xorg-video-intel (Ubuntu) = gnome-settings-
daemon (Ubuntu)
** Changed in: gnome-settings-daemon (Ubuntu S-series)
Status: Confirmed = Triaged
** Changed in: gnome-settings-daemon (Ubuntu S-series)
Importance: Undecided = High
** Changed in:
** Changed in: xserver-xorg-input-evdev (Ubuntu)
Assignee: Canonical X.org (canonical-x) = (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/408903
A while ago we wrote up some architecture and troubleshooting documents
for hotkeys - https://wiki.ubuntu.com/Hotkeys
Some of that has gotten dated (e.g. we don't use HAL anymore), but it's
still roughly descriptive. Many of the tools listed there are still
useful in isolating where in the stack
@Roman, more details needed.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gtk+2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/937822
Title:
[precise] F10 always opens the menu, cannot be overriden (after
xkeyboard-config
Quantal)
Status: Triaged = Fix Committed
** Changed in: xkeyboard-config (Ubuntu Precise)
Assignee: (unassigned) = Bryce Harrington (bryce)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gtk+2.0 in Ubuntu.
https
** Description changed:
+ [Impact]
+ F10 behaves the same as Shift-F10. This causes menus to pop up incorrectly.
+
+ [Fix]
+ Upstream patch preserves Shift so that Shift-F10 and F10 act as separate keys.
+
+ [Test Case]
+ 1. Open a gnome-terminal window
+ 2. Run aptitude
+ 3. Press F10
+
+
Unlikely to be X doing this, but feel free to reopen if evidence comes to light
indicating X is doing something wrong.
I'd suggest also trying multiple times and see if the fault is reproducible or
not.
** Changed in: xorg (Ubuntu)
Status: New = Invalid
--
You received this bug
The postr task should now be fixed due to the sync for bug #1050484
** Changed in: postr (Ubuntu)
Status: New = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus in Ubuntu.
** Changed in: gnome-panel (Ubuntu)
Status: Confirmed = Triaged
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-panel in Ubuntu.
https://bugs.launchpad.net/bugs/948667
Title:
gnome-panel crashed with SIGSEGV in
** Description changed:
- When trying to print a photo, the printer stops with status rendering
- completed. I have to remove all printing jobs and restart CUPS to be
- able to print again. This error does not occur when printing other
- documents, i.e. simple text.
+ [Impact]
+
+ [Fix]
+
+
Not sure from comment #42 why this failed verification, but as there is
at the moment nothing further to be sponsored, I'm unsubbing sponsors
for now.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to rhythmbox in Ubuntu.
I'm no longer using rhythmbox.
** Changed in: rhythmbox (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to rhythmbox in Ubuntu.
https://bugs.launchpad.net/bugs/940569
Title:
Adding playlist
** Description changed:
This has been going on since 11.10 dev, maybe should be addressed
- In Edit - Preferences, the Settings button is greyed out unavailable. So
there is no user available means to adjust encoding for vorbis, mp3, mp4, ect.
+ In Edit Preferences, on the Music tab the
** Changed in: xkeyboard-config (Ubuntu Precise)
Status: Fix Committed = Triaged
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to rhythmbox in Ubuntu.
https://bugs.launchpad.net/bugs/221112
Title:
Can't use space bar in
The fix has been reverted out, due to a bug report (bug #1013881) filed
about it during testing in -proposed.
You guys will need to work with upstream to find a better way of fixing
it that doesn't cause regressions for anyone.
--
You received this bug notification because you are a member of
This bug is closed; it's better to open a new bug (with fresh backtrace
and logs) than to comment on this one.
** Changed in: gnome-desktop (Ubuntu)
Assignee: Bryce Harrington (bryce) = (unassigned)
** Changed in: gnome-control-center (Ubuntu)
Assignee: Bryce Harrington (bryce
In investigating further it appears that something (apport?) is linking
people to this bug report. However, this bug was fixed four years ago.
It's likely the logic in whatever is linking to this is faulty in some
fashion, rather than that this ancient crash has come back.
In any case, like I
** Package changed: xorg (Ubuntu) = gnome-settings-daemon (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/1008249
Title:
quantal 3 June daily build external
** Package changed: xorg (Ubuntu) = gnome-settings-daemon (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/1007588
Title:
quantal 1 June i386.iso external
** Package changed: xorg (Ubuntu) = gnome-settings-daemon (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/1006413
Title:
quantal 20120530 cannot set displays
@Sarvatt, is there anything we should do on the -synaptics end for this
bug? When we looked at the issue previously it did not seem like
XRecord was easily fixable for this usage; are there any new ideas on
what we might do (even if just papering over it...)?
** Changed in:
*** This bug is a duplicate of bug 806306 ***
https://bugs.launchpad.net/bugs/806306
** This bug is no longer a duplicate of private bug 939555
** This bug has been marked a duplicate of bug 806306
rhythmbox crashed with SIGSEGV in g_hash_table_lookup_node()
--
You received this bug
** Description changed:
Steps to reproduce:
1. insert a CD
2. let rhythmbox recognize it
3. remove it with the button on the drive
4. the CD is now removed from the drive but rhythmbox already shows it
5. now insert a new CD
6. rhythmbox crashes
+
+ #0 0x7f08c4128740 in ??
#1 0x7f08dd022a56 in g_hash_table_lookup_node (hash_table=0x41ec880,
key=0x41ec890, notify=1) at /build/buildd/glib2.0-2.28.6/./glib/ghash.c:313
node = value optimized out
node_index = value optimized out
hash_value = value optimized out
step = 0
313:
** Visibility changed to: Public
** Changed in: rhythmbox (Ubuntu)
Importance: Medium = High
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to rhythmbox in Ubuntu.
https://bugs.launchpad.net/bugs/985264
Title:
rhythmbox crashed
Are you able to reproduce this on Precise?
I attempted using the directions provided, but on ejecting the first
disc, rb cleared itself. The second cd was detected and loaded ok.
There have been some significant changes to the section of glib2.0 code
this bug hit, perhaps it already got fixed
405: *hash_return = hash_value;
406:
407: node_index = hash_value % hash_table-mod; /* SIGFPE */
408: node_hash = hash_table-hashes[node_index];
Attached patch should fix it.
** Patch added:
0001-Fix-modulo-division-by-zero-SIGFPE-in-g_hash_table_l.patch
I can't reproduce this in Precise using the steps given. You should re-
test and see if you are able to reproduce it on Precise and if so,
clarify the directions.
I've been messing around with adding/removing layouts for some other
bugs for some time now and have never seen this dialog. My
I am not able to reproduce this on precise.
Notably, the 'keyboard model' option is no longer provided in the GUI
(at least, no where I can find), so it's no longer possible to put
keyboards into this broken state using the directions given in this bug.
If you still know of a way that affects
** Package changed: libxklavier (Ubuntu) = gnome-settings-daemon
(Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/396360
Title:
gnome-settings-daemon does not
** Tags added: precise quantal
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/360970
Title:
Multi-monitor - When using two displays with different vertical
resolution, icons
Now that -nvidia supports xrandr 1.2, it's probably not worth the effort
to fix this. For quantal, presumably the stock config dialog should
just work with nvidia, so no need for special hacks there. And for
precise, unfortunately I think even if we did come up with a special
hack it wouldn't be
** Description changed:
- Binary package hint: rhythmbox
+ [Impact]
+ In the fr(oss) keymap, both space and Ctrl + space return the same
XLookupString, which prevents space from being used in some applications.
- I tried to search for The Do in the search bar, but the space bar
- didn't write
** Also affects: rhythmbox (Ubuntu Precise)
Importance: Undecided
Status: New
** Also affects: quodlibet (Ubuntu Precise)
Importance: Undecided
Status: New
** Also affects: xkeyboard-config (Ubuntu Precise)
Importance: Undecided
Status: New
** No longer affects:
1 - 100 of 1314 matches
Mail list logo
