[Bug 2055114] Re: fail2ban is broken in 24.04 Noble
FWIW, this is what we did in Fedora: https://src.fedoraproject.org/rpms/fail2ban/c/24c973f252f6d1b4231ee49ee4d5efac785a2fe8?branch=rawhide i.e., we depend on packages of the asynchat and asyncore libs that were added to pypi for this kind of purpose - https://pypi.org/project/pyasynchat/ and https://pypi.org/project/pyasyncore/ - and we also had to disable a couple of tests. I don't know if Ubuntu/Debian packaged the split-out asynchat and asyncore libs yet. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055114 Title: fail2ban is broken in 24.04 Noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fail2ban/+bug/2055114/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061118] Re: Rendering issues in vmware with 3d on (GTK ngl backend)
OK, so I just tried this out on the same host I did my Fedora 40 testing, a Windows 11 23H2 system with Intel graphics (no NVIDIA) and VMWare Player 17. I grabbed the Ubuntu 24.04 beta desktop image - ubuntu-24.04-beta- desktop-amd64.iso - and booted it. From that environment I could reproduce the bug. I tested using "Files" (nautilus) - I ran it and it was completely messed up in much the same way as on Fedora, lots of bits of the UI just not shown at all. Then I ran an install. I guess your installs work differently from ours, they don't just dump the live environment onto the disk, because when I booted the installed system, it had mesa 24.0.5 already (verified with `dpkg -l`). And for me, the bug is indeed fixed. Now when I run Files, it renders perfectly. Ditto Text Editor (another GTK4 app). However, reading Oliver's original description again, it really doesn't sound like the same bug. I didn't observe any "black flickering artifacts" during install, and I never saw such a thing in Fedora 40 testing either. I also didn't see anything like "desktop screen is black and then locks up the whole application, cannot shutdown or interact with Player". For me, both in Ubuntu and Fedora, when a system is affected by this bug, GTK 4-based apps tend to be missing large amounts of UI elements, but the desktop shell itself is not affected at all, let alone does it lock up or become unresponsive. So, I think Oliver is seeing something else, but I don't know what. I'd recommend you get a few more folks to test and see what they see, and report the host hardware config. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061118 Title: Rendering issues in vmware with 3d on (GTK ngl backend) To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/2061118/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061118] Re: Rendering issues in vmware with 3d on (GTK ngl backend)
FWIW, I did my testing - which found this is broken for a Fedora 40 guest with mesa 24.0.4, but fixed with 24.0.5 - on a Windows 11 (23H2) host. No idea what's different for Oliver, sorry :( I guess I could try with an Ubuntu guest on my test setup, I've got a bit of spare time today. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061118 Title: Rendering issues in vmware with 3d on (GTK ngl backend) To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/2061118/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1638516] Re: Fatal error with GPG after upgrade to Ubuntu 16.10
Still, that's no reason to close this as invalid. It's silly to suggest that everyone in the world who uses duply has to add this to their config manually once their GPG is new enough. Instead, duply should know that it has to use those options if gpg is 2.1 or newer... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1638516 Title: Fatal error with GPG after upgrade to Ubuntu 16.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/duply/+bug/1638516/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1720768] Re: gnome-shell crashed with SIGTRAP in object_instance_finalize from js::Class::doFinalize ["Finalizing proxy for an object that's scheduled to be unrooted: Gio.Subprocess\n"]
BTW, for your Apport folks - I'm currently unpicking rather a mess caused by our equivalent tool (abrt) considering many crashes that run through a particular codepath in GNOME Shell as duplicates when they are not in fact duplicates at all. See https://bugzilla.redhat.com/show_bug.cgi?id=1509086 for more details on that. You might wanna check if the same thing is affecting Apport in any way. ** Bug watch added: Red Hat Bugzilla #1509086 https://bugzilla.redhat.com/show_bug.cgi?id=1509086 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1720768 Title: gnome-shell crashed with SIGTRAP in object_instance_finalize from js::Class::doFinalize ["Finalizing proxy for an object that's scheduled to be unrooted: Gio.Subprocess\n"] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1720768/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1720768] Re: gnome-shell crashed with SIGTRAP in object_instance_finalize from js::Class::doFinalize ["Finalizing proxy for an object that's scheduled to be unrooted: Gio.Subprocess\n"]
We have several reports of the same crash message ("Finalizing proxy for
an object that's scheduled to be unrooted: Gio.Subprocess") in Fedora:
https://bugzilla.redhat.com/show_bug.cgi?id=1466948
https://bugzilla.redhat.com/show_bug.cgi?id=1517479
https://bugzilla.redhat.com/show_bug.cgi?id=1514732
https://bugzilla.redhat.com/show_bug.cgi?id=1522921
https://bugzilla.redhat.com/show_bug.cgi?id=1523323
at least. Not sure if they all have the same underlying cause. One
report mentions the Easy Screen Cast extension, and also claims to have
solved the problem by disabling pipewire.service .
** Bug watch added: Red Hat Bugzilla #1466948
https://bugzilla.redhat.com/show_bug.cgi?id=1466948
** Bug watch added: Red Hat Bugzilla #1517479
https://bugzilla.redhat.com/show_bug.cgi?id=1517479
** Bug watch added: Red Hat Bugzilla #1514732
https://bugzilla.redhat.com/show_bug.cgi?id=1514732
** Bug watch added: Red Hat Bugzilla #1522921
https://bugzilla.redhat.com/show_bug.cgi?id=1522921
** Bug watch added: Red Hat Bugzilla #1523323
https://bugzilla.redhat.com/show_bug.cgi?id=1523323
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1720768
Title:
gnome-shell crashed with SIGTRAP in object_instance_finalize from
js::Class::doFinalize ["Finalizing proxy for an object that's
scheduled to be unrooted: Gio.Subprocess\n"]
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1720768/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1728588] Re: Xwayland crashed with wl_registry@2: error 0: invalid global wl_output (36) after kernel: [drm:intel_mst_disable_dp [i915]] *ERROR* failed to update payload -22
For reference, I've found some other reports with the same basic issue - Wayland crash with an error like this: Oct 27 08:28:38 danielpc-arch org.gnome.Shell.desktop[7418]: (EE) Oct 27 08:28:38 danielpc-arch org.gnome.Shell.desktop[7418]: Fatal server error: Oct 27 08:28:38 danielpc-arch org.gnome.Shell.desktop[7418]: (EE) wl_registry@2: error 0: invalid global wl_output (36) Oct 27 08:28:38 danielpc-arch org.gnome.Shell.desktop[7418]: (EE) * https://bugs.freedesktop.org/show_bug.cgi?id=103474 * https://bugzilla.redhat.com/show_bug.cgi?id=1514220 (and dupes) ** Bug watch added: freedesktop.org Bugzilla #103474 https://bugs.freedesktop.org/show_bug.cgi?id=103474 ** Bug watch added: Red Hat Bugzilla #1514220 https://bugzilla.redhat.com/show_bug.cgi?id=1514220 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1728588 Title: Xwayland crashed with wl_registry@2: error 0: invalid global wl_output (36) after kernel: [drm:intel_mst_disable_dp [i915]] *ERROR* failed to update payload -22 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1728588/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1715330] Re: gnome-shell crashed with SIGSEGV in _cogl_boxed_value_set_x()
Filed https://bugzilla.gnome.org/show_bug.cgi?id=787568 . ** Bug watch added: GNOME Bug Tracker #787568 https://bugzilla.gnome.org/show_bug.cgi?id=787568 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1715330 Title: gnome-shell crashed with SIGSEGV in _cogl_boxed_value_set_x() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1715330/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1715330] Re: gnome-shell crashed with SIGSEGV in _cogl_boxed_value_set_x()
There's some discussion upstream too at https://bugzilla.gnome.org/show_bug.cgi?id=787240 - but note that it's a confused bug report that starts out being about a different bug, which is reported in Launchpad as https://bugs.launchpad.net/ubuntu/+source /gnome-shell/+bug/1714330 . I will file a new upstream bug for the _console_boxed_value_set_x crash. ** Bug watch added: GNOME Bug Tracker #787240 https://bugzilla.gnome.org/show_bug.cgi?id=787240 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1715330 Title: gnome-shell crashed with SIGSEGV in _cogl_boxed_value_set_x() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1715330/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1715330] Re: gnome-shell crashed with SIGSEGV in _cogl_boxed_value_set_x()
We're seeing what's probably the same crash in Fedora 27, though my reproducer is to start a VM in virt-manager: https://bugzilla.redhat.com/show_bug.cgi?id=1490072 It was suggested to try 3.25.92 and see if that fixes it. ** Bug watch added: Red Hat Bugzilla #1490072 https://bugzilla.redhat.com/show_bug.cgi?id=1490072 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1715330 Title: gnome-shell crashed with SIGSEGV in _cogl_boxed_value_set_x() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1715330/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1423811] Re: 219-1ubuntu1 regression: boot hangs, logind fails
FWIW I was seeing something that sounds very similar on F22: https://bugzilla.redhat.com/show_bug.cgi?id=1201964 but it *seems* to have gone away with systemd-219-11.fc22, which is basically the same as systemd 'v219-stable' - http://cgit.freedesktop.org/systemd/systemd-stable/log/?h=v219-stable - at85a6fabdd3e43cfab0fc6359e9f2a9e368d4a3ed , core/namespace: fix path sorting. Seems like something fixed it for me. 219-9.fc22 was definitely broken for me; that build had 'v219-stable' as of commit 4acdc3835b2c9d395f1df95bb1dd5620a4a0e7e5 , service: don't add After= dependencies on .busname units if kdbus support is disabled. So it seems like something between two those commits on v219-stable fixed it for me, assuming it stays fixed. ** Bug watch added: Red Hat Bugzilla #1201964 https://bugzilla.redhat.com/show_bug.cgi?id=1201964 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1423811 Title: 219-1ubuntu1 regression: boot hangs, logind fails To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1423811/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1183804] Re: [Fujitsu LIFEBOOK U772] WARNING: at /build/buildd/linux-3.8.0/drivers/gpu/drm/i915/intel_display.c:1028 intel_wait_for_pipe_off+0xe2/0x1a0 [i915]()
This 'wait_for_pipe_off' issue seems pretty widespread. It may well be a dupe of #1182386 , and there is a Fedora report at https://bugzilla.redhat.com/show_bug.cgi?id=919120 . I have been seeing it a couple of times per boot on Fedora 18 from kernel 3.8.9 all the way to kernel 3.10, on a Sony Vaio VPC-Z11. ** Bug watch added: Red Hat Bugzilla #919120 https://bugzilla.redhat.com/show_bug.cgi?id=919120 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1183804 Title: [Fujitsu LIFEBOOK U772] WARNING: at /build/buildd/linux-3.8.0/drivers/gpu/drm/i915/intel_display.c:1028 intel_wait_for_pipe_off+0xe2/0x1a0 [i915]() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1183804/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 865791] Re: Pointer Speed settings have no effect on touchpad
Also affects Fedora 19: filed upstream , https://bugzilla.gnome.org/show_bug.cgi?id=699502 ** Bug watch added: GNOME Bug Tracker #699502 https://bugzilla.gnome.org/show_bug.cgi?id=699502 ** Also affects: gnome-control-center via https://bugzilla.gnome.org/show_bug.cgi?id=699502 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/865791 Title: Pointer Speed settings have no effect on touchpad To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/865791/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 960124] Re: [VPCZ13C5E or VPCZ114GX, Realtek ALC889, Speaker, Internal] No sound at all
Note - I have a somewhat-longstanding thread on this issue (wrt my VPCZ112GDS) on the alsa-devel list: http://mailman.alsa-project.org/pipermail/alsa- devel/2012-March/050492.html is where it started back in March, and: http://mailman.alsa-project.org/pipermail/alsa- devel/2012-July/053561.html is where it picks up this month. tiwai has posted a patch that seems to fix it, though I don't know if it takes all the complexities discussed in this report into account. I have posted a mail to the thread pointing at this report, so both threads should now be aware of the other. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/960124 Title: [VPCZ13C5E or VPCZ114GX, Realtek ALC889, Speaker, Internal] No sound at all To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/960124/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 960124] Re: [VPCZ13C5E or VPCZ114GX, Realtek ALC889, Speaker, Internal] No sound at all
I've confirmed that the patch tiwai posted at http://mailman.alsa- project.org/pipermail/alsa-devel/2012-July/053601.html resolves the bug, for my VPCZ11 anyhow: sound through the internal speaker works as it did prior to 3.2, and sound still works through the headphone socket, auto- muting the speakers when connected. I couldn't test anything to do with external mic/headset, though. You have to re-diff the patch somewhat to apply against anything older than the current kernel 'sound' branch, but it's easy enough to do. I tested it against 3.5.0. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/960124 Title: [VPCZ13C5E or VPCZ114GX, Realtek ALC889, Speaker, Internal] No sound at all To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/960124/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 745392] Re: Fails to compile with GCC 4.6 (unless using -fpermissive)
just for the record, you should probably thank Hicham, not me: he wrote the patch :) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/745392 Title: Fails to compile with GCC 4.6 (unless using -fpermissive) -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 411181] Re: sane detects but doesn't scan with HP network scanner
Having a very similar experience with an M1212nf: I got it to scan one page once, but after that it always fails - trying to scan, or just to use --help with scanimage to get the supported parameters - with the Error during device I/O message. This is on Fedora 14, so I suspect this is some kind of upstream bug, not Ubuntu specific. I have hplip 3.10.9 (packaged Fedora). -- sane detects but doesn't scan with HP network scanner https://bugs.launchpad.net/bugs/411181 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 411181] Re: sane detects but doesn't scan with HP network scanner
also see: https://bugs.launchpad.net/hplip/+bug/395284 -- sane detects but doesn't scan with HP network scanner https://bugs.launchpad.net/bugs/411181 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 411181] Re: sane detects but doesn't scan with HP network scanner
ah, found the best reference for the 1212nf at least: https://bugs.launchpad.net/hplip/+bug/653391 -- sane detects but doesn't scan with HP network scanner https://bugs.launchpad.net/bugs/411181 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 532633] Re: [light-theme] please revert the order of the window controls back to menu:minimize, maximize, close
Mark, if you'd let someone entirely unrelated plunk an oar in for a minute, I think However, it does line things up nicely for work I would like us to do in future. is at the nub of this. You've said a couple of times that the idea is to free up the right hand corner for Other Stuff You Will Put There Later, which is a valid idea. What I don't get, though, is why you think it makes sense to do the freeing-up before you've got around to inventing the Other Stuff. It gives people all the drawbacks of the re-arranging with none of the benefits of the Cool New Stuff, so it's not that surprising that they wind up belly-aching. You said somewhere that you think it's better to 'get ready' for the change now, but...why? I don't see how it would be innately more difficult for people to adjust to the new layout once you've got the Cool New Stuff ready, and then they'd have the Cool New Stuff to make up for having to adjust to the new layout. Sure, it probably wouldn't be any _easier_ either, but that's not really a sufficient argument for doing it now. If you did it when the other changes are ready too, it'd probably make a lot more sense to people. If you've covered this somewhere, sorry, but if I haven't seen it, probably a lot of others haven't either =) -- [light-theme] please revert the order of the window controls back to menu:minimize,maximize,close https://bugs.launchpad.net/bugs/532633 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 396945] Re: I can't load the new kernel 2.6.31-1 or 2.6.31-2 on Ubuntu Karmic because of a driver : RT2860
No, that's not why. rt2860 fails to compile on 2.6.31 because compatibility with the old net_device API has been dropped between 2.6.30 and 2.6.31, and rt2860 uses this API. It needs to be ported to the new net_driver_ops API. Here's the upstream discussion of the drop: http://patchwork.ozlabs.org/patch/27566/ Here's a bug report for VirtualBox which hit the same problem, include a patch to port to the new API: http://www.virtualbox.org/ticket/4264 I am seeing if I can hack together a patch for rt2860 based on the VirtualBox patch, but I'm no hacker, so I can't promise anything. ** Bug watch added: Virtualbox Trac #4264 http://www.virtualbox.org/ticket/4264 -- I can't load the new kernel 2.6.31-1 or 2.6.31-2 on Ubuntu Karmic because of a driver : RT2860 https://bugs.launchpad.net/bugs/396945 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 396945] Re: I can't load the new kernel 2.6.31-1 or 2.6.31-2 on Ubuntu Karmic because of a driver : RT2860
actually, what i'm looking at is rt2860sta, the driver from ralink. if this is about the in-kernel driver, sorry for the noise. -- I can't load the new kernel 2.6.31-1 or 2.6.31-2 on Ubuntu Karmic because of a driver : RT2860 https://bugs.launchpad.net/bugs/396945 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 303193] Re: Please remove kiosktool from Jaunty
The KDE 4 port of kiosktool is under active development in SVN - svn://anonsvn.kde.org/home/kde/trunk/extragear/sysadmin/kiosktool - and some distributions package this version already. -- Please remove kiosktool from Jaunty https://bugs.launchpad.net/bugs/303193 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 106380] Re: No sound or distorted sound from certain Audigy models by default due to digital output being unmuted
What's going to happen is that ALSA will be adapted so that, in all cases, 'muted' gives analog output, and 'unmuted' gives digital. That will basically fix the problem. But it will take a bit of time, as ALSA has to be coded to understand which way to set it up for each different codec. -- No sound or distorted sound from certain Audigy models by default due to digital output being unmuted https://bugs.launchpad.net/bugs/106380 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 190515] Re: [Hardy] Low bandwidth with rt2400 / rt2500 drivers
** Bug watch added: Mandriva Linux #42180 http://qa.mandriva.com/show_bug.cgi?id=42180 ** Also affects: linux (Mandriva) via http://qa.mandriva.com/show_bug.cgi?id=42180 Importance: Unknown Status: Unknown -- [Hardy] Low bandwidth with rt2400 / rt2500 drivers https://bugs.launchpad.net/bugs/190515 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 264019] Re: unable to visit some websites and ftpsites with 2.6.27
bobby: because TCP timestamps are a desired feature. The fact that they were broken in the upstream kernel for a long time was the bug. It's just that now they've been fixed, this is exposing the fact that some routers do not handle timestamps correctly. -- unable to visit some websites and ftpsites with 2.6.27 https://bugs.launchpad.net/bugs/264019 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 272247] Re: System freezes during boot, unless I hold a key down
Added links to the Mandriva and upstream reports for this issue. ** Bug watch added: Mandriva Linux #44342 http://qa.mandriva.com/show_bug.cgi?id=44342 ** Also affects: linux (Mandriva) via http://qa.mandriva.com/show_bug.cgi?id=44342 Importance: Unknown Status: Unknown ** Bug watch added: Linux Kernel Bug Tracker #11727 http://bugzilla.kernel.org/show_bug.cgi?id=11727 ** Also affects: linux via http://bugzilla.kernel.org/show_bug.cgi?id=11727 Importance: Unknown Status: Unknown -- System freezes during boot, unless I hold a key down https://bugs.launchpad.net/bugs/272247 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 254668] Re: [2.6.27] pausing during boot (several issues)
** Bug watch added: Mandriva Linux #44342 http://qa.mandriva.com/show_bug.cgi?id=44342 ** Also affects: mandriva via http://qa.mandriva.com/show_bug.cgi?id=44342 Importance: Unknown Status: Unknown -- [2.6.27] pausing during boot (several issues) https://bugs.launchpad.net/bugs/254668 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 255342] Re: Freedesktop's autostart makes (almost) impossible having both KDE4 and GNOME installed in the same machine
Someone complained about the same thing in Mandriva: http://forum.mandriva.com/viewtopic.php?p=548286#548286 Looks like an upstream issue. -- Freedesktop's autostart makes (almost) impossible having both KDE4 and GNOME installed in the same machine https://bugs.launchpad.net/bugs/255342 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 255342] Re: Freedesktop's autostart makes (almost) impossible having both KDE4 and GNOME installed in the same machine
OK, there's reports for this in both KDE and GNOME: https://bugs.kde.org/show_bug.cgi?id=170817 https://bugs.kde.org/show_bug.cgi?id=163582 http://bugzilla.gnome.org/show_bug.cgi?id=551700 http://bugzilla.gnome.org/show_bug.cgi?id=548339 I don't think INVALID is a good resolution. ** Also affects: kdebase via http://bugs.kde.org/show_bug.cgi?id=170817 Importance: Unknown Status: Unknown -- Freedesktop's autostart makes (almost) impossible having both KDE4 and GNOME installed in the same machine https://bugs.launchpad.net/bugs/255342 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 255342] Re: Freedesktop's autostart makes (almost) impossible having both KDE4 and GNOME installed in the same machine
** Also affects: gnome-session via http://bugzilla.gnome.org/show_bug.cgi?id=548339 Importance: Unknown Status: Unknown ** Also affects: kdebase (Mandriva) Importance: Undecided Status: New -- Freedesktop's autostart makes (almost) impossible having both KDE4 and GNOME installed in the same machine https://bugs.launchpad.net/bugs/255342 You received this bug notification because you are a member of Almost Kubuntu Bugs, which is subscribed to kdebase in ubuntu. -- kubuntu-bugs mailing list [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 59908] Re: identify command requires mpeg2decode
Both encoding and decoding are now fixed in upstream ImageMagick. Any version since 6.4.2.10 should be OK, so this bug can be closed relative to any distro release that includes ImageMagick 6.4.2.10 or later. -- identify command requires mpeg2decode https://bugs.launchpad.net/bugs/59908 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 253768] Re: kde 4.1 does not automount LUKS encrypted external USB harddisks
It works in KDE 3 because of a third party patch Ubuntu integrated. See upstream bug: http://bugs.kde.org/show_bug.cgi?id=113629 The Ubuntu bug is: https://bugs.launchpad.net/ubuntu/+source/kdebase/+bug/128863 This support is not part of original upstream KDE 3. Adding support to KDE 4 would depend on someone writing something along the lines of this patch, either upstream KDE or a third party as before. -- kde 4.1 does not automount LUKS encrypted external USB harddisks https://bugs.launchpad.net/bugs/253768 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 128863] Re: [WISH] Merge patch for LUKS support from SuSE
Just to record that obviously this functionality is lost with the switch to KDE 4, as is shown by #253768. -- [WISH] Merge patch for LUKS support from SuSE https://bugs.launchpad.net/bugs/128863 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 204184] Re: Transmission doesn't open torrents via Firefox 3
This is fixed in upstream SVN, should be fixed in the next release. It is also fixed in the current Mandriva package. -- Transmission doesn't open torrents via Firefox 3 https://bugs.launchpad.net/bugs/204184 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 204184] Re: Transmission doesn't open torrents via Firefox 3
This issue also occurs on Mandriva. It's not related to any kind of transmission-gtk naming / desktop file / whatever issue for us, as it's never been called that in our package. I have brought this up with upstream. We believe it's a race condition between Firefox and Transmission. Briefly, from 1.30 on, when Transmission is already running and something runs 'transmission sometorrent.torrent', a second transmission instance spawns, passes the torrent filename on to the first via DBus, then shuts down again. We believe that when it shuts down, Firefox then deletes the .torrent file as it thinks the operation is complete. So if the first instance of Transmission doesn't manage to pick everything up before Firefox deletes the temporary file, the bug happens. Upstream will look at fixing this by passing the entire torrent metainfo over DBus rather than just passing the filename and relying on it still being there for the first instance to look at. Since 1.30 this is actually technically a different bug from what was first reported both here and upstream, just to avoid confusion. -- Transmission doesn't open torrents via Firefox 3 https://bugs.launchpad.net/bugs/204184 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 59908] Re: identify command requires mpeg2decode
OK, the ImageMagick folks have fixed the decoding side of things (which is the easy bit). As per http://www.imagemagick.org/discourse- server/viewtopic.php?f=3t=11827 , SVN trunk now uses ffmpeg for decoding, not mpeg2decode . Encoding isn't done yet. -- identify command requires mpeg2decode https://bugs.launchpad.net/bugs/59908 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 59908] Re: identify command requires mpeg2decode
mpeg2decode and mpeg2encode are the very old MPEG reference encoder and decoder. The problem for distros is they are not F/OSS - the license does not mention modification or redistribution rights, and you can't consider them as implied. So we can't package them. I've looked at patching ImageMagick to use something else. I think I have a replacement that will work for decoding: this is quite simple, it just involves replacing the 'mpeg2decode' command ImageMagick uses with an ffmpeg command that does the same thing. Encoding is not so straightforward. The problem is that mpeg2encode uses a weird system that nothing else uses. The command is very simple - mpeg2encode in.par out.mpeg . The trickery is all in the .par file, which is essentially a one-time job configuration file: it specifies all the details about what you actually want to encode. In the ImageMagick source, coders/mpeg.c contains a big bunch of code to write an appropriate .par file for the operation. No modern, F/OSS encoder that I've found seems to be able to understand .par files. They all expect you to just feed them a series of images direct on the command line, which is a completely different system. So to migrate ImageMagick from mpeg2encode to something modern you'd have to substantially change mpeg.c to just feed out a series of YUV images, not write a .par file, and call the delegate properly, *then* change the delegate from mpeg2encode to mpeg2enc or ffmpeg or mencoder or whatever you want to use. Unfortunately, my (non-existent) C skills don't extend to that, really, though I may give it a bash. I'll attach patches when I have something I know works. -- identify command requires mpeg2decode https://bugs.launchpad.net/bugs/59908 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 59908] Re: identify command requires mpeg2decode
I have done: http://www.imagemagick.org/discourse- server/viewtopic.php?f=3t=11827p=38454#p38454 They say: A patch from you or another user is the best path to getting this into the ImageMagick source base as quickly as possible. We are in agreement with you but the ImageMagick developers are currently swamped and we will not get to this problem for a minimum of several months. Unfortunately I can't my patch to work. :( It needs someone with a better understanding of how exactly the code works. I can give a few pointers, though, if it helps anyone else. The actual commands used are in magick/delegate.c and config/delegates.xml.in (the latter seems to be the one that's actually operative, at least in my case). For the mpeg case, these are called from coders/mpeg.c , so you need to look at that to see exactly what it does, too. Currently ImageMagick uses this command for decoding: command=quot;mpeg2decodequot; -q -b quot;%iquot; -f -r -o3 quot;%u%%dquot; which basically works out to: mpeg2decode -q -b (input) -f -r -o3 (output) where %i is the input and %u%%d is the output. I'm not quite sure how %u%%d *works* - that's the bit I can't figure out and I think is what's preventing me from patching it properly. The following ffmpeg command does something rather similar: ffmpeg -i (input) -vcodec ppm -an -f rawvideo (output) but just substituting it in the most logical way doesn't work. I'm missing something here but I'm not sure what. The logical mpeg2dec program, btw, doesn't actually seem capable of doing what's needed (for one thing it doesn't seem possible to control the output filenames). You don't need to keep rebuilding to test modifications. The installed ImageMagick package will contain a file named delegates.xml , somewhere like /usr/lib/ImageMagick-6.4.2/config/ . You can edit this and change the command directly in there - the change will be applied the next time you run an ImageMagick command. You can test with simply 'identify file.mpg' . If it's working right, you should get something like: [EMAIL PROTECTED] ~]$ identify movie.mpg movie.mpg=/home/adamw/tmp/magick-XXRc9qGL0.ppm[0] MPEG 128x128 128x128+0+0 8-bit DirectClass 48kb (repeated a lot of times, use a short movie). For encoding it gets more complex, but again the basic thing is you need to look at what mpeg.c does - in this case it'll need to be changed - and then adjust the delegate to a modern command (probably mpeg2enc , which most distros package). I'll see if I can find all discussions of this issue in various places and link them together... -- identify command requires mpeg2decode https://bugs.launchpad.net/bugs/59908 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 59908] Re: identify command requires mpeg2decode
** Bug watch added: Mandriva Linux #39643 http://qa.mandriva.com/show_bug.cgi?id=39643 ** Also affects: imagemagick (Mandriva) via http://qa.mandriva.com/show_bug.cgi?id=39643 Importance: Unknown Status: Unknown -- identify command requires mpeg2decode https://bugs.launchpad.net/bugs/59908 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 210725] Re: RaLink RT2790 not working
** Bug watch added: Mandriva Linux #42520 http://qa.mandriva.com/show_bug.cgi?id=42520 ** Also affects: mandriva via http://qa.mandriva.com/show_bug.cgi?id=42520 Importance: Unknown Status: Unknown -- RaLink RT2790 not working https://bugs.launchpad.net/bugs/210725 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 221834] Re: inotify regression in dbus 1.1.20 (with patch)
+1, this should really be fixed. restarting dbus isn't really a viable workaround, as many applications barf when dbus is restarted under them, restarting dbus on a running system isn't something you really want to do. The patch is simple and was integrated upstream in dbus 1.2.x , there's no problems with it. -- inotify regression in dbus 1.1.20 (with patch) https://bugs.launchpad.net/bugs/221834 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 223212] Re: Non-free files distributed without license/copyright info
it may be worthwhile to have some kind of cross-distro effort to get a clear license for the DVB firmware stuff, so all distros can include it safely. -- Non-free files distributed without license/copyright info https://bugs.launchpad.net/bugs/223212 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 188621] Re: Conflict between Ndiswrapper and ssb
*** This bug is a duplicate of bug 182716 *** https://bugs.launchpad.net/bugs/182716 Sorry, I got this reference from a forum thread. Didn't know it was a dupe. What's the original? Why hasn't this been resolved as a dupe of it? -- Conflict between Ndiswrapper and ssb https://bugs.launchpad.net/bugs/188621 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 188621] Re: Conflict between Ndiswrapper and ssb
*** This bug is a duplicate of bug 182716 *** https://bugs.launchpad.net/bugs/182716 Honestly? Nope. I actually went and looked specifically for such a thing after reading your last message, and it either wasn't there or wasn't noticeable. I see the one above the comment box now, but it still took me about thirty seconds to find the one at the top of the page today. (Partly the fault of me forcing my own GTK+ color scheme on pages in Firefox, admittedly. If I turn that off, the yellow background makes it more visible). Sorry about that. -- Conflict between Ndiswrapper and ssb https://bugs.launchpad.net/bugs/188621 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 182716] Re: bcm4306 doesn't work with b43 / ssb
Duplicating my comments from 188621... Regarding the ohci_hcd / ssb issue, the required fix is CONFIG_USB_OHCI_HCD_SSB=n in kernel build config. This option, when enabled, makes ohci_hcd depend on ssb, but is only needed to support a USB controller that is found only in embedded devices (so not relevant to standard Ubuntu). As long as that option's set to y, ssb will be loaded whenever ohci_hcd is loaded, regardless of blacklisting or anything else. In Mandriva's case, ohci_hcd was being loaded on all systems (even systems with no USB controller requiring the ohci_hcd driver) due to a change in mkinitrd. I don't know if this part also affects Ubuntu, but regardless, the above fixes the problem. Bug should be sent to your kernel devs. -- bcm4306 doesn't work with b43 / ssb https://bugs.launchpad.net/bugs/182716 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 188621] Re: Conflict between Ndiswrapper and ssb
*** This bug is a duplicate of bug 182716 *** https://bugs.launchpad.net/bugs/182716 Hi all. We have this same issue on Mandriva (I'm encountering it on my personal system and trying to figure it out; I'm not a kernel hacker, just bashing away as best I can). I have half of it figured out. ssb is being loaded because ohci_hcd is being loaded. ohci_hcd has a dependency on ssb as long as the kernel build has: CONFIG_USB_OHCI_HCD_SSB=y so a quick fix would probably be to disable that option. However, what I can't figure out is why ohci_hcd is being loaded at all. On my system, it is not listed in any modprobe configuration file, and I have verified with lspci -k that no hardware in my system is considered by the kernel to be supported by ohci_hcd. I also checked manually that none of my hardware has a modalias matching the modalias'es associated with ohci_hcd , according to modinfo ohci_hcd . And to do the obvious test - all my USB ports and hardware still work with ohci_hcd not loaded at all. So I really cannot figure out what is causing ohci_hcd to be loaded on my system. It would seem to be something in the upstream kernel / modprobe stuff, if the problem occurs in both Mandriva and Ubuntu. Others have reported that blacklisting ohci_hcd has no effect. This would make sense given my tests above, but I haven't tested this specifically on my system yet. I will do the next time I reboot. -- Conflict between Ndiswrapper and ssb https://bugs.launchpad.net/bugs/188621 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 188621] Re: Conflict between Ndiswrapper and ssb
*** This bug is a duplicate of bug 182716 *** https://bugs.launchpad.net/bugs/182716 Okay, further research. On Mandriva, ohci_hcd is apparently loaded on all systems in the initrd, due to a change in mkinitrd. I suspect this is the same in Ubuntu. Basically this boils down to: CONFIG_USB_OHCI_HCD_SSB=y is just wrong for a general-purpose distribution. From the help for that option: Support for the Sonics Silicon Backplane (SSB) attached Broadcom USB OHCI core. This device is present in some embedded devices with Broadcom based SSB bus. If unsure, say N. So it's apparently only useful for supporting a USB controller that only exists in some embedded devices. There's therefore no reason to enable it for a general-purpose distro. I guess you guys should assign this bug to your kernel team and have them disable that option. That's what I'm doing for MDV. -- Conflict between Ndiswrapper and ssb https://bugs.launchpad.net/bugs/188621 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 175680] Re: TI SD reader 0x104c 0x803c does not work
dupe of 137686. Sorry. -- TI SD reader 0x104c 0x803c does not work https://bugs.launchpad.net/bugs/175680 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 164048] Re: audacious pulseaudio plugin is making stuttering sound
I am having the exact same issue on Mandriva, looks like a general problem in the plugin. I don't know who is responsible for this, either :\ -- audacious pulseaudio plugin is making stuttering sound https://bugs.launchpad.net/bugs/164048 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 175680] TI SD reader 0x104c 0x803c does not work
Public bug reported: We had a bug reported in Mandriva: http://qa.mandriva.com/show_bug.cgi?id=35887 where a specific TI SD card reader (PCI ID in the summary) did not work. We identified a fix for this bug and issued an update. The reporter mentioned in passing that he noticed the same problem in Ubuntu 7.10, so I thought you may also be interested in the bug report. The issue is an insufficient timeout in the mmc driver, and the specific patch we came up with is here: http://svn.mandriva.com/cgi- bin/viewvc.cgi/packages/updates/2008.0/kernel-2.6/current/PATCHES/patches/DB35_mmc_power_up_delay.patch?view=markuppathrev=114631 this has been tested by the developer (who was affected by the same bug) and by the initial reporter to resolve the problem. All relevant details are in the Mandriva bug report. ** Affects: kernel-image-2.6.7-i386 (Ubuntu) Importance: Undecided Status: New -- TI SD reader 0x104c 0x803c does not work https://bugs.launchpad.net/bugs/175680 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 175680] Re: TI SD reader 0x104c 0x803c does not work
Package assignment is likely wrong, btw. You have a metric assload of packages with 'kernel' in the name and I really had no idea what was the appropriate one. The reporter tested with a stock Ubuntu 7.10 live CD, so the issue is in the stock 7.10 kernel. -- TI SD reader 0x104c 0x803c does not work https://bugs.launchpad.net/bugs/175680 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 114534] Re: Suggested patches for gimmie
Well, they're all getting closed as duplicates of the very same bugs upstream. See the b.g.o. references in my initial report. Note the number of duplicates. -- Suggested patches for gimmie https://bugs.launchpad.net/bugs/114534 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 114534] Re: Suggested patches for gimmie
well, as I suggested, given the significance of the bugs (and the fact that gimmie is hardly a heavily-developed app with a long history of stability to lose), it may make more sense simply to push 0.2.7 as an update for your stable releases than try to patch 0.2.4. That would depend on how strict your update policy is, though, I guess. -- Suggested patches for gimmie https://bugs.launchpad.net/bugs/114534 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 114534] Re: Suggested patches for gimmie
really? ah :( that could be a problem. I kinda figured you had 0.2.6. um, I suspect a version update wouldn't be a bad idea, but I don't know if you're allowed to do that. -- Suggested patches for gimmie https://bugs.launchpad.net/bugs/114534 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 114534] Re: Suggested patches for gimmie
http://svn.mandriva.com/cgi- bin/viewvc.cgi/packages/cooker/gimmie/current/SOURCES/gimmie-0.2.6 -computer-crash.patch?view=markuppathrev=41525 http://svn.mandriva.com/cgi- bin/viewvc.cgi/packages/cooker/gimmie/current/SOURCES/gimmie-0.2.6 -source-crash.patch?view=markuppathrev=41525 -- Suggested patches for gimmie https://bugs.launchpad.net/bugs/114534 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 114534] Re: Suggested patches for gimmie
no problem, and I think I can safely say the GNOME bug squad will thank you =) I don't know what your policy on version updates is, but you could also solve this by updating the package to 0.27, the patches are included in that version. -- Suggested patches for gimmie https://bugs.launchpad.net/bugs/114534 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 114534] Suggested patches for gimmie
Public bug reported: Binary package hint: gimmie Hi, Ubuntu guys. I'm the Mandriva maintainer for gimmie (an experimental GNOME panel / launcher). I noticed that two particular gimmie bugs are getting a *huge* amount of duplicate reports from Ubuntu users in GNOME Bugzilla: http://bugzilla.gnome.org/show_bug.cgi?id=421732 http://bugzilla.gnome.org/show_bug.cgi?id=421620 I've fixed these in the Mandriva package by backporting the following two patches from SVN. You should probably apply these to your package too. :) -- --- trunk/gimmie/gimmie_computer.py 2007/03/22 00:44:46 385 +++ trunk/gimmie/gimmie_computer.py 2007/03/22 20:22:15 389 @@ -103,7 +103,8 @@ uri = volume.get_activation_uri() break else: -raise ValueError, Cannot find URI to open for drive '%s' % drive +raise ValueError, Cannot find URI to open for drive '%s' % \ + drive.get_display_name() Item.__init__(self, uri=uri, @@ -214,7 +215,10 @@ yield self.cd_burner for drive in self.vol_monitor.get_connected_drives(): -yield DriveItem(drive) +try: +yield DriveItem(drive) +except ValueError: +pass class PrinterItem(Item): --- trunk/gimmie/gimmie_computer.py 2007/03/22 20:22:15 389 +++ trunk/gimmie/gimmie_computer.py 2007/03/25 03:16:42 391 @@ -485,12 +485,8 @@ uri=source://Administration, filter_by_date=False) -self.system_settings_menu_tree = None -try: -self.system_settings_menu_tree = MenuTree(system-settings.menu) -self.system_settings_menu_tree.connect(reload, lambda x: self.emit(reload)) -except ValueError: -pass +self.system_settings_menu_tree = MenuTree(system-settings.menu) +self.system_settings_menu_tree.connect(reload, lambda x: self.emit(reload)) self.system_settings_menu_source = None self.do_reload() @@ -737,7 +733,10 @@ settings] if not settings.has_administration(): -source_list.append(AdministrationSource()) +try: +source_list.append(AdministrationSource()) +except ValueError, err: +print !!! Error loading Administration items:, err ### Uncomment to list settings inside their toplevel folders in the sidebar #source_list += SettingsSource().get_toplevel_source_list() ** Affects: gimmie (Ubuntu) Importance: Undecided Status: Unconfirmed -- Suggested patches for gimmie https://bugs.launchpad.net/bugs/114534 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
