[Bug 2058143] Re: Decoding glitchy on GM45 - MR has been pending since 2020
So the MR fixing the particular glitch I'm seeing on my Thinkpad T400 / GM45 is https://github.com/intel/intel-vaapi-driver/pull/514 . Including that would be enough to close this bug - it's pretty small and straight forward. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2058143 Title: Decoding glitchy on GM45 - MR has been pending since 2020 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-vaapi-driver/+bug/2058143/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2058143] [NEW] Decoding glitchy on GM45 - MR has been pending since 2020
Public bug reported: Ubuntu 24.04 will ship with Gstreamer 1.24, which finally promoted many "va*" plugins to primary, i.e. enabled them by default and will thus be used by more apps than in the past. I tested this on an old Thinkpad T400 / Intel GM45 and ran into a glitch. Fortunately there's pending MR (see below) fixing that - but Intel does not seem to maintain https://github.com/intel/intel-vaapi- driver any more, so it will likely never get merged or released. I'd thus like to request to add the MR in question to the Debian/Ubuntu package. However, while on it, it might sense to add a few more fixes that have accumulated: - All new commits on the master branch (~7?) - https://github.com/intel/intel-vaapi-driver/pull/566, which will be needed for upcoming Wayland compositor changes. - https://github.com/intel/intel-vaapi-driver/pull/514 which fixes glitches for e.g. Gstreamer based players on very old generations (GM45). I tested/verified this one myself. - Potentially: https://github.com/intel/intel-vaapi-driver/pull/530 - unfortunately I don't have the hardware to verify this one. If you prefer, I can also try to open a MR at https://salsa.debian.org/multimedia-team/intel-vaapi- driver/-/merge_requests - but I'm not very used to the debian packaging workflow. Thanks for considering :) ** Affects: intel-vaapi-driver (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2058143 Title: Decoding glitchy on GM45 - MR has been pending since 2020 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-vaapi-driver/+bug/2058143/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1930485]
This should have been fixed a while ago and it works for me - jhwilliams, can you still reproduce this issue? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1930485 Title: Can't Start Firefox 88 on Weston/Wayland, Ubuntu 18.0.4. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1930485/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871644]
(In reply to Emilio Cobos Álvarez (:emilio) from comment #30) > So given there's no way to access the other border corners, and that this > works for our purposes, I think we should probably just roll with it, > thoughts? I'd agree - should work well for almost everyone. One question I had to think of is if we want to use rounded corners at the bottom at some point - more and more GTK4 apps do that, e.g. nautilus/files. But we can also leave that for the future. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871644 Title: Top corners of Firefox windows have weird black protrusions from the rounded edges To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1871644/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871644]
Thanks emilio, that's a good hint. The comment says > It may cause performance issues so let's put it under a preference and enable > it for desktop environment which do that by default. This is clearly outdated and from a pre Webrender time. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871644 Title: Top corners of Firefox windows have weird black protrusions from the rounded edges To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1871644/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871644]
This just became even more prominent in 95 with colorways. We need a way to support this with alpha visuals as XShape is neither available on Wayland nor on X11 with HW Webrender - i.e. it's only available in legacy fallback paths. As the default theme supports this (even though with a grey corner), I suppose this is not really a graphics but rather a theme issue. Emilio, do you happen to know how the default theme gets its corners and what would need to be done to make it work for other themes as well? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871644 Title: Top corners of Firefox windows have weird black protrusions from the rounded edges To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1871644/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1915870] Re: gnome-shell/gnome-session-check-accelerated-gl-helper crashed with SIGSEGV in cso_destroy_context() [r300_dri.so]
Just got crash reports at Firefox about this - apparently visiting/closing any website with WebGL is enough to trigger this on affected drivers. https://crash- stats.mozilla.org/report/index/318626ed-3353-4bf4-8df2-75ccb0210403 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1915870 Title: gnome-shell/gnome-session-check-accelerated-gl-helper crashed with SIGSEGV in cso_destroy_context() [r300_dri.so] To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1915870/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917191]
Jan, this might be important for you as well (archlinux). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917191 Title: firefox will not start after it crashed unexpectedly To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1917191/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1905330] [NEW] Backport Wayland frame callback fix for 3.28 for Firefox testing infrastructure
Public bug reported: The Firefox testing infrastructure is based on Ubuntu 18.04. In order to enable the Wayland backend by default, we need to also run test on that. There is one particular bug in Mutter 3.28 that I'd like to see fixed for that, thus requesting a backport of a patch. It's already in the upstream repo, but as 3.28 is not supported upstream any more, I request it here explicitly: https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1570 @vanvugt @3v1n0 this would be super helpful for us, I hope I can convince you about that, even if Ubuntu 18.04 doesn't support Wayland officially. It can be tested by running Firefox with `MOZ_ENABLE_WAYLAND=1` and setting `widget.wayland_vsync.enabled:1` in the config (soon to be enabled by default). If, after launching Firefox again, everything works as expected - well, then it works. Bonus: the patch also affects a number of other Wayland applications, so some users might be happy to see it as well. ** Affects: mutter (Ubuntu) Importance: Undecided Status: New ** Tags: wayland ** Tags added: wayland ** Description changed: The Firefox testing infrastructure is based on Ubuntu 18.04. In order to - enable the Wayland backend by default, we need to enable it for the - Wayland backend first. + enable the Wayland backend by default, we need to also run test on that. There is one particular bug in Mutter 3.28 that I'd like to see fixed for that, thus requesting a backport of a patch. It's already in the upstream repo, but as 3.28 is not supported upstream any more, I request it here explicitly: https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1570 @vanvugt @3v1n0 this would be super helpful for us, I hope I can convince you about that, even if Ubuntu 18.04 doesn't support Wayland officially. It can be tested by running Firefox with `MOZ_ENABLE_WAYLAND=1` and setting `widget.wayland_vsync.enabled:1` in the config (soon to be enabled by default). If, after launching Firefox again, everything works as expected - well, then it works. Bonus: the patch also affects a number of other Wayland applications, so some users might be happy to see it as well. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1905330 Title: Backport Wayland frame callback fix for 3.28 for Firefox testing infrastructure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1905330/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893021]
Ouch, sorry and thanks for that! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1893021 Title: Flash plugin symbol lookup error with firefox 80.0+build2 on xenial (gtk_window_set_titlebar) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1893021/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1889784]
It's likely that you see bug 1658035 - should be fixed by next nightly. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1889784 Title: Hardware-accelerated video decoding (VA-API) broken in Firefox 79 (Wayland) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1889784/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1688592]
(In reply to eric.riese from comment #34) > > In my opinion the bounty was already earned when this issue was resolved but > I don't know who gets to be the arbiter. That would certainly be Martin Stránský :) Martin, do you want to claim the bounty? If you don't care about it / don't need it yourself, you could donate it or so. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1688592 Title: Missing VA-API hardware decoding support drains battery To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1688592/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1424201]
(In reply to eric.riese from comment #34) > > In my opinion the bounty was already earned when this issue was resolved but > I don't know who gets to be the arbiter. That would certainly be Martin Stránský :) Martin, do you want to claim the bounty? If you don't care about it / don't need it yourself, you could donate it or so. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1424201 Title: Web browsers lacking hardware-accelerated video decoding To manage notifications about this bug go to: https://bugs.launchpad.net/chromium-browser/+bug/1424201/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1688592]
That should be bug 1572697 for Wayland. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1688592 Title: Missing VA-API hardware decoding support drains battery To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1688592/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1424201]
That should be bug 1572697 for Wayland. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1424201 Title: Web browsers lacking hardware-accelerated video decoding To manage notifications about this bug go to: https://bugs.launchpad.net/chromium-browser/+bug/1424201/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1688592]
Although this bug is only about decoding support, I'd like to leave a note about the rendering: AFAIK rendering without any slow copies requires DMABUF support, so processes can share resources on the GPU. For the Wayland backend this about to land, see bug 1552590, quote: > Wayland dmabuf surface are located in GPU and can be attached as EGLImage or wl_buffer. It allows direct rendering to GPU and share the HW buffer across processes. Also see bug 1010527 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1688592 Title: Missing VA-API hardware decoding support drains battery To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1688592/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1424201]
Although this bug is only about decoding support, I'd like to leave a note about the rendering: AFAIK rendering without any slow copies requires DMABUF support, so processes can share resources on the GPU. For the Wayland backend this about to land, see bug 1552590, quote: > Wayland dmabuf surface are located in GPU and can be attached as EGLImage or wl_buffer. It allows direct rendering to GPU and share the HW buffer across processes. Also see bug 1010527 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1424201 Title: Web browsers lacking hardware-accelerated video decoding To manage notifications about this bug go to: https://bugs.launchpad.net/chromium-browser/+bug/1424201/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1688592]
The dependency of this bug could probably changed from ogl-linux-beta to bug 1491303, as webrender will replace all the old rendering architecture and is already enabled on linux + intel in nightly. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1688592 Title: Missing VA-API hardware decoding support drains battery To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1688592/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1750633] Re: signer and verifier have been deprecated
Hej Kenneth, thanks for the answer. I agree that this is a sufficient workaround, but for an LTS version of Ubuntu, I think it would be worthwhile considering backporting this fix. People will use Ubuntu 18.04 for many years to come and many will hit this issue, especially people using it on servers and doing backups with duplicity. Installing packages from pip makes updates more complicated and dangerous and is certainly not the desired state for backup solutions. Maybe the maintainer of paramiko, @jbouse, can comment on that? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1750633 Title: signer and verifier have been deprecated To manage notifications about this bug go to: https://bugs.launchpad.net/cursive/+bug/1750633/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1750633] Re: signer and verifier have been deprecated
Here's the link to the upstream fix: https://github.com/paramiko/paramiko/pull/979/commits/fdc09c9f93fd189a6398d5b350a3c91011d9b4cb I'd like to kindly request a backport (actually simply applying) it. It's a fairly trivial and I just tested it on my server (18.04) without issues. ** Also affects: duplicity Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1750633 Title: signer and verifier have been deprecated To manage notifications about this bug go to: https://bugs.launchpad.net/cursive/+bug/1750633/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1714989] Re: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() from st_label_set_text() from ffi_call_unix64()
The patch got accepted upstream for gnome-shell 3.30. And hopefully for some 3.28.3 version. For Fedora users who end up here because it's the top entry on a common search engine, the corresponding bug entry is here: https://bugzilla.redhat.com/show_bug.cgi?id=1489554 ** Bug watch added: Red Hat Bugzilla #1489554 https://bugzilla.redhat.com/show_bug.cgi?id=1489554 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1714989 Title: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() from st_label_set_text() from ffi_call_unix64() To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1714989/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1750633] Re: signer and verifier have been deprecated
I'd really appreciate a backport of the fix. Some other distributions shipping with paramiko 2.0 ship it already, for example mageia (https://advisories.mageia.org/MGAA-2018-0077.html) It affects everyone doing backups with duplicity over ssh, most notably when using cronjobs. Probably quite a big group. Unfortunately it's not enough to just set the log verbosity to error. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1750633 Title: signer and verifier have been deprecated To manage notifications about this bug go to: https://bugs.launchpad.net/cursive/+bug/1750633/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 883459]
I see the same bug in trojita. Do trojita and kmail2 share code? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/883459 Title: KMail duplicates emails To manage notifications about this bug go to: https://bugs.launchpad.net/kdepim/+bug/883459/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 883459]
Dear devs, would if help if you had access to a mailbox showing this issue. If so, let me know, and I see what I can do. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/883459 Title: KMail duplicates emails To manage notifications about this bug go to: https://bugs.launchpad.net/kdepim/+bug/883459/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 883459]
I experienced the described issue for all akonadi/kmail versions which are ported to frameworks. The system I am using is Arch with the following (relevant) packages installed - plasma-desktop: 5.5.1 - plasma-framework: 5.17 - framework components 5.17 - kde applications: 15.12, including kmail and akonadi Moreover, as a dependency of digikam, the following kde 4 stuff is there - kdebase-runtime: 15.12 - kdebase-lib: 15.12 - kdepimlibs4: 4.14.10 - libkipi4: 15.08 - libakonadi-qt4: 1.13.0 - libbaloo4: 4.14.3 I configure two generic imap resource in kmail. The first points to the mail server of my university, the second to the one of my web provider. I do not know what imap server they are running, but likely they are running different software. Thus, I guess, the issue is not with the server but with the client side. I do not configure anything special like server side subscription or sieve script. On initial population of the mailboxes, everything seem fine. All messages are there and readable. The trouble starts as soon as I start to move around mails manually or via kmail filters or delete messages. Say, I move a message from the Inbox to the Private folder. The message disappears in the Inbox and seems to be moved to Privat. However, the message is not really moved. I is still in the Inbox and reappears the next time kmail refreshes the Inbox. The mail is grayed in the Inbox (everything is good with the messages in Private). In the Inboxr, I can not click on it, move or delete it. It just sits there, grayed out, not touchable. Now, using the web interface of my universities mail system, the mail is marked as deleted in the Inbox, but still there. At least, using the web interface, I can select the massage and delete it for real. Then, also in kmail, the message disappears. Unfortunately, I can not properly name the state of the deleted message in "imap"-terms. On top of this issue, moved messages start to appear in the target folder multiple times. There is always one instance of the message which is clickable and good, but with time, multiple grayed out versions start to accumulate. They seem to be in the same state as the moved one in the source folder. If there is any more information I can provide, do not hesitate to drop me a mail. Reproducible: Always Steps to Reproduce: 1. Create a Imap resource in framework based kmail 2. Move or delete messages 3. Refresh mailbox and observe grayed out, uncklickable messages Actual Results: Messages are not moved or deleted from mailbox. Expected Results: Messages should be moved or deleted from mailbox. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/883459 Title: KMail duplicates emails To manage notifications about this bug go to: https://bugs.launchpad.net/kdepim/+bug/883459/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 150569] Re: GNOME keyring manager doesn't open keyring on login
Yes I am using gdm and I am using autologin. Why doesn't it work with autologin? Can it be fixed till final release? -- GNOME keyring manager doesn't open keyring on login https://bugs.launchpad.net/bugs/150569 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 150569] GNOME keyring manager doesn't open keyring on login
Public bug reported: In Gnome 2.20 it is possible that the keyring will be automatically opened on login. This is nice because it's not needed to give the password anymore when the network manager needs access to the keyring for protected wireless networks. The new feature is also noted on http://www.gnome.org/start/2.20/notes/en/index.html#rnusers-password-management As it is stated it needs some work in the distribution that it works and since I get a new prompt with a checkbox to automatically open the keyring if checked, I guess it really should work. At the moment checking the box doesn't seem to do anything and giving the password also doesn't seem to open the keyring because I get a second prompt which looks exactly as the prompts from earlier GNOME versions. After I input the password for the keyring in this "old" prompt the keyring is opened. Would be nice if that feature would work. ** Affects: ubuntu Importance: Undecided Status: New -- GNOME keyring manager doesn't open keyring on login https://bugs.launchpad.net/bugs/150569 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 144175] Re: tilda stays like a gray window with compiz enabled
me too and all the guys in this -> http://ubuntuforums.org/showthread.php?t=556932 thread -- tilda stays like a gray window with compiz enabled https://bugs.launchpad.net/bugs/144175 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 139294] Re: [needs-packaging] DSSS (The D programming language Shared Software System)
There is already a package for Debian -> http://uploads.dunnewind.net/package.php?id=25 -- [needs-packaging] DSSS (The D programming language Shared Software System) https://bugs.launchpad.net/bugs/139294 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 139294] Re: [needs-packaging] DSSS (The D programming language Shared Software System)
** Bug watch added: Debian Bug tracker #441426 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=441426 ** Also affects: debian via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=441426 Importance: Unknown Status: Unknown -- [needs-packaging] DSSS (The D programming language Shared Software System) https://bugs.launchpad.net/bugs/139294 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 48682] Re: adept doesn't work behind a proxy server
Kubuntu has just been released and this bug is still present. I'd like to add that also "apt-get" and aptitude commands from the console should work and the file /etc/wgetrc should be updated with the current proxy -- adept doesn't work behind a proxy server https://bugs.launchpad.net/bugs/48682 You received this bug notification because you are a member of Kubuntu Team, which is a direct subscriber. -- kubuntu-bugs mailing list [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 94468] Re: D-Link Airplus DWL-G520+ not working in FF, even with ndiswrapper
I solved it upgrading ndiswrapper-utils to version 1.9. Please include version 1.9 from Feisty Fawn Beta, because it is not easy to download that package from another os and then copying and installing it. on the contrary the acx driver does *not* work, as usual. -- D-Link Airplus DWL-G520+ not working in FF, even with ndiswrapper https://launchpad.net/bugs/94468 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 94468] D-Link Airplus DWL-G520+ not working in FF, even with ndiswrapper
Public bug reported: It is something related to acx, ndiswrapper (and its utils). I wrote a long description of the problem here: http://www.ubuntuforums.org/showthread.php?t=389935 ** Affects: Ubuntu Importance: Undecided Status: Unconfirmed -- D-Link Airplus DWL-G520+ not working in FF, even with ndiswrapper https://launchpad.net/bugs/94468 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
