[Bug 1505624] [NEW] Upgrade to 5.1
Public bug reported: This package is outdated. Please update to 5.1. The 5.0 series includes significant fixes and new features over the current 4.3 which includes a number of new features. http://sweethome3d.com/history.jsp ** Affects: sweethome3d (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/1505624 Title: Upgrade to 5.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sweethome3d/+bug/1505624/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1372520] Re: On Lenovo Yoga 2 Pro laptop PS/2 Synaptics TouchPad detected as pointer device by Xorg
Affects me too, using Yoga Lenovo Yoga 2 laptop (not Pro). Running 14.10 both 15.04, Kubuntu, with KF5, Plasma 5.1.9.0, Kernel: Linux 3.16.0-24-generic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1372520 Title: On Lenovo Yoga 2 Pro laptop PS/2 Synaptics TouchPad detected as pointer device by Xorg To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1372520/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 725800] Re: Empathy away doesn't equate to Facebook's idle
This has been done already in Pidgin - Facebook Chat Quoted from: http://code.google.com/p/pidgin-facebookchat/wiki/Changelog Changelog From time to time, this plugin gets updated. This is a list of changes to it. Version 1.68 Support for new group chats Fix for setting status messages Fix for when FB chat is down for maintenance -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/725800 Title: Empathy away doesn't equate to Facebook's idle -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 3200] Re: Non-root user not able to mount webdav-shares
This issue is indeed documented. But it is not usable or comprehendible for the majority of ubuntu users. More and more people are using webdav in their offices or at home. An enhancement is needed - perhaps a control panel item - to ease setting-up web directories. -- Non-root user not able to mount webdav-shares https://bugs.launchpad.net/bugs/3200 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 506361] Re: kdesudo - process for the file protocol died unexpectedly
** Description changed: Binary package hint: kdesudo When running kdesudo or kdesudo dbus-launch dolphin or another app that uses file protocol, the following message is received: The process for the file protocol died unexpectedly and the relevant folder shows no contents. Gksudo dbus-launch seems to work OK after any previous kdesudo attempts have timed-out. I have also posted about this at the Kubuntu forums (http://kubuntuforums.net/forums/index.php?topic=3109260.0) where some have confirmed the issue and others not. It seems to be inconsistent. Regards, Steve ProblemType: Bug Architecture: i386 Date: Tue Jan 12 10:57:33 2010 DistroRelease: Ubuntu 9.10 NonfreeKernelModules: nvidia Package: kdesudo 3.4.2.2-0ubuntu1 ProcEnviron: - LANGUAGE=en_GB:en - LANG=en_GB.UTF-8 - SHELL=/bin/bash + LANGUAGE=en_GB:en + LANG=en_GB.UTF-8 + SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-18.55-generic SourcePackage: kdesudo Uname: Linux 2.6.31-18-generic i686 XsessionErrors: - (polkit-gnome-authentication-agent-1:2207): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed - (unknown:2692): Gdk-CRITICAL **: gdk_window_get_origin: assertion `GDK_IS_WINDOW (window)' failed - (unknown:2692): Gdk-CRITICAL **: gdk_window_get_origin: assertion `GDK_IS_WINDOW (window)' failed + (polkit-gnome-authentication-agent-1:2207): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed + (unknown:2692): Gdk-CRITICAL **: gdk_window_get_origin: assertion `GDK_IS_WINDOW (window)' failed + (unknown:2692): Gdk-CRITICAL **: gdk_window_get_origin: assertion `GDK_IS_WINDOW (window)' failed -- kdesudo - process for the file protocol died unexpectedly https://bugs.launchpad.net/bugs/506361 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 453260] Re: Can not connect using WEP ASCII keys
Many thanks! I've tested it on a couple of routers and public wifi network and can confirm that it works fine with WEP ASCII keys. (Running plasma-widget-networkmanagement from Aurélien's ppa repository on Kubuntu Karmic Beta 64bit.) [Unfortunately, one little snag, which warrants a separate bug - when I get the chance I'll search/create a new bug for KDE. The default for the software on connecting to a WEP network is to ask the user to enter a WEP passphrase rather than a WEP ASCII or HEX key. I realise that there's no way of the software differentiating between passphrases and keys, but that there is a way of differentiating between different ASCII and HEX keys. Thus the user must at least choose either key or passphrase, the rest is figured automatically. I suggest it would be far better for a request for a key to be the default, because: a) the vast majority of WEP usage is via ASCII or HEX keys rather than passphrases - as (from broad anecdotal experience, and market rationale) consumer devices and public networks to not default to using WEP passphrases; b) the few usages of WEP passphrase almost always involve technical users or users in corporate spheres with either technical support or a far greater awareness then the general public of 'having to do something special' with their wifi settings. ] -- Can not connect using WEP ASCII keys https://bugs.launchpad.net/bugs/453260 You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to plasma-widget-network-manager in ubuntu. -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 453260] Re: Can not connect using WEP ASCII keys
I appreciate the difficulties with 64bit WEP ASCII keys. However, networkmanager itself (as well as Windows systems and MacOS, and Gnome using networkmanager) all permit the user to attempt to connect. WEP ASCII keys are very common, including in public wifi networks. Most users either a) cannot obtain the hex equivalents (e.g. in a public networks), b) do not know why their connections have failed, c) do not have the knowledge or information, or internet access, to find out why. Having no capability to enter and attempt connection using WEP ASCII keys is therefore a major regression in the implementation of networkmanager. I submit that it is preferable to permit a user to attempt connection using the algorithms that were formerly permitted, albeit with a warning message that WEP ASCII usage is deprecated and may not work. Even if it doesn't work with half the connections it is not rational to deny any attempt at connections via this method. In any event, I would suggest that when a user attempts to enter a 64bit WEP key, rand it can't connect, rather than just having their connection refused, a message should display explaining why their connection isn't working, and what they may do to about (get a HEX key, or use WPA for example). This would at least prevent some users worrying what was going wrong with their computer, and attempting all kinds of fixes (aggravated further since they may have no internet connection to research the problem, and if their WEP key and connection used to work fine with Gnome, KDE ,or Windows). -- Can not connect using WEP ASCII keys https://bugs.launchpad.net/bugs/453260 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 339313] Re: Kubuntu Jaunty: Cannot Connect To Wireless Network with WEP shared key
This bug is still present in Kubuntu Karmic 9.10 beta - plasma-widget- networkmanagement package does not offer the user an option to enter a 40 or 128-bit ASCII WEP key (which is not the same as a passphrase). Using the hex workaround is not realistic (nor reasonable) for the majority of users. ** Changed in: plasma-widget-networkmanagement (Ubuntu Karmic) Status: Fix Released = Confirmed -- Kubuntu Jaunty: Cannot Connect To Wireless Network with WEP shared key https://bugs.launchpad.net/bugs/339313 You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to plasma-widget-network-manager in ubuntu. -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 339313] Re: Kubuntu Jaunty: Cannot Connect To Wireless Network with WEP shared key
Re: Comment #82 - I agree there is a workaround, but that doesn't mean the software works as expected. The issue is not whether the network works by using a workaround, but that as the default network management package in Kubuntu the software MUST offer the user the option to enter the WEP ASCII key when Kubuntu 9.10 is released or lots of users will be floundering with effectively no internet access, unable to a) figure out what's wrong, b) get internet access to find out how to fix it, and c) may be unable to implement the workaround easily. -- Kubuntu Jaunty: Cannot Connect To Wireless Network with WEP shared key https://bugs.launchpad.net/bugs/339313 You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to plasma-widget-network-manager in ubuntu. -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 339313] Re: Kubuntu Jaunty: Cannot Connect To Wireless Network with WEP shared key
Can we upgrade this to critical? It would effectively be an internet blocker for many users. -- Kubuntu Jaunty: Cannot Connect To Wireless Network with WEP shared key https://bugs.launchpad.net/bugs/339313 You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to plasma-widget-network-manager in ubuntu. -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 339313] Re: Kubuntu Jaunty: Cannot Connect To Wireless Network with WEP shared key
See upstream bug: https://bugs.kde.org/show_bug.cgi?id=199786 It seems that a reliable algorithm hash isn't available to convert the 40 and 104bit ASCII WEP keys to HEX. 128bit keys are available, and implemented already (pass phrase?). Though, does anyone know why other OSes (and Gnome(?)) manage this? I would argue that the previous capability, even if not 100%, is worth implementation (albeit with a warning that it may not work). Furthermore, when a user attempts to enter a 40 or 104bit ASCII key I propose that they should get a warning saying ASCII keys may not work, there should then be an attempt at a conversion to HEX, and if that fails, they should receive a warning explaining the situation and how to obtain and enter a HEX key. At minimum this warning would prevent people from flailing around (especially with no internet connection) trying to find out what's 'broken' with their systems. ** Bug watch added: KDE Bug Tracking System #199786 http://bugs.kde.org/show_bug.cgi?id=199786 -- Kubuntu Jaunty: Cannot Connect To Wireless Network with WEP shared key https://bugs.launchpad.net/bugs/339313 You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to plasma-widget-network-manager in ubuntu. -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 328173] Re: npviewer.bin crashed with signal 5 in _XError()
I experienced this using Konqueror, whilst visiting some flash-heavy websites (64bit build on 64bit PC). It froze (but didn't crash) Konqueror. -- npviewer.bin crashed with signal 5 in _XError() https://bugs.launchpad.net/bugs/328173 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 307004] Re: padevchooser doesn't play well with volume control applet
In my configuration I have internal laptop speakers and mic. I plug in a usb headset. Kmix sees it and creates a seperate tab for the headset. In systemsettings/media I can test the headset and everything works. But in Kmix there's no way of setting the USB headset to be the one from which sound comes :( and neither is there a way of setting it to automatically become the default device when plugged in (as occurs with a standard jack headphone). So I installed padevchooser. But even so, as the original poster states, there's no easy way to use the volume control. I mentioned the above just to underscore how frustrating this bug is for a user who has already had to go to such trouble just to realise that their USB headset is recognised, but they can't use it without trawling google. -- padevchooser doesn't play well with volume control applet https://bugs.launchpad.net/bugs/307004 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 431015] Re: No Icon in System Tray KDE 4.3.1
Upon clicking on the menu in padevchooser (from the systemtray icon) many of the icons in the menu are also missing. -- No Icon in System Tray KDE 4.3.1 https://bugs.launchpad.net/bugs/431015 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 252094] Re: MASTER: Poor graphics performance on Intel
Just for info: Intel Linux Graphics On Ubuntu Still Flaky http://www.phoronix.com/scan.php?page=articleitem=intel_q309_flakesnum=3 -- MASTER: Poor graphics performance on Intel https://bugs.launchpad.net/bugs/252094 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 288650] Re: Intel Java Graphics Performace degradation in Intrepid
General article relating to some of the intel graphics architectural changes, and specifically to the absolutely terrible graphic performance drops in ubuntu 9.04: http://www.phoronix.com/scan.php?page=articleitem=ubuntu_904_intelnum=1 http://www.phoronix.com/scan.php?page=news_itempx=NzA0NQ -- Intel Java Graphics Performace degradation in Intrepid https://bugs.launchpad.net/bugs/288650 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 288650] Re: Intel Java Graphics Performace degradation in Intrepid
.. and this from Bryce, explaining the background to a of the changes: http://www2.bryceharrington.org:8080/drupal/intel-2.6.1 -- Intel Java Graphics Performace degradation in Intrepid https://bugs.launchpad.net/bugs/288650 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 252094] Re: Poor graphics performance on Intel G965 system, ubuntu 8.10 alpha 3
Same here, just 59 frames per second as of today's updates. -- Poor graphics performance on Intel G965 system, ubuntu 8.10 alpha 3 https://bugs.launchpad.net/bugs/252094 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 252094] Re: Poor graphics performance on Intel G965 system, ubuntu 8.10 alpha 3
Same problem here, with an intel x3100 card (on a Samsung Q45). Up to 8.04.1 (Kubuntu) I was able to use KDE4 'desktop effects' easily. Also, sInce upgrading to 8.10 Alpha 3 (from 8.04.1), desktop effects are not working, enabling them results in a mainly black, garbled screen. -- Poor graphics performance on Intel G965 system, ubuntu 8.10 alpha 3 https://bugs.launchpad.net/bugs/252094 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 252094] Re: Poor graphics performance on Intel G965 system, ubuntu 8.10 alpha 3
I have now found a workaround for the issue. I think it basically is to do with the upgrade from XAA to EXA acceleration. EXA appears not be working with the Intel GMA 965 (GM) chipset (including the Intel X3100). Upon editing my xorg.conf file to add references to XAA I now have better performance, and am able to use KDE4 desktop effects. In particular, under Section Device, I added: Option XaaNoPixmapCache Option XAANoOffscreenPixmaps 1 Option DRI true Option AccelMethod XAA and also VideoRam440320 Option XvMCSurfaces 6 Option May_Need_ForceBIOS 1 but not sure if these last three items are necessary. ** Attachment added: Working xorg.conf for GMA965 chipsets under hardy 4.1 or intrepid k/ubuntu. http://launchpadlibrarian.net/16355670/xorg.conf.amended.txt -- Poor graphics performance on Intel G965 system, ubuntu 8.10 alpha 3 https://bugs.launchpad.net/bugs/252094 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 252094] Re: Poor graphics performance on Intel G965 system, ubuntu 8.10 alpha 3
Also, remove (or comment-out) any lines in your xorg.conf file referring to EXA, if you have them! -- Poor graphics performance on Intel G965 system, ubuntu 8.10 alpha 3 https://bugs.launchpad.net/bugs/252094 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 252094] Re: Poor graphics performance on Intel G965 system, ubuntu 8.10 alpha 3
And one more thing, I'm not sure it's essential, but it may be wise to ensure that you specify the driver as 'intel' in your Device Section. i.e. Section Device Identifier Configured Video Device Driver intel -- Poor graphics performance on Intel G965 system, ubuntu 8.10 alpha 3 https://bugs.launchpad.net/bugs/252094 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
