[Bug 160311] Re: Window Resize Difficult (Window Border Thickness)
** Also affects: hundredpapercuts Importance: Undecided Status: New -- Window Resize Difficult (Window Border Thickness) https://bugs.launchpad.net/bugs/160311 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 11334] Re: Copy-Paste doesn't work if the source is closed before the paste
@David Siegel, I don't think that the amount of discussion should be a factor on whether this is a papercut or not, nor do I believe that there are "divergent opinions" on this bug - everyone is pretty much saying the same thing - copy/paste in linux is laughably broken and has been for many years. The only divergence of opinion I'm seeing on this bug discussion is whether glipper/parcelite/etc are suitable workarounds. The common message seems to be that they are not, so this is still a papercut for nearly every user of linux, let alone Ubuntu. Sure, perhaps this entails too much work for a papercut, but your stated reasons for changing its status are (I think) invalid. -- Copy-Paste doesn't work if the source is closed before the paste https://bugs.launchpad.net/bugs/11334 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 344252] [NEW] CPU Frequency Scaling defaults to "Performance" instead of "OnDemand"
Public bug reported: Binary package hint: cpufreqd Ubuntuforums thread : http://ubuntuforums.org/showthread.php?t=1098459 In Jaunty 9.04, a few days ago, it was noticed that the default CPU frequency is now "Performance". Before, it was set to "OnDemand". This can be changed back again on a per-session basis by clicking on the CPUFreq applet (in gnome) and changing the setting to whatever is desired, or changed permanently either by updating "/sys/devices/system/cpu/cpu0/cpufreq/scaling_governor" or using "cpufreq-selector -g ondemand" However, when using a laptop, this is not desirable default behaviour as the effect on battery is obvious. This setting should be "OnDemand" by default. ** Affects: cpufreqd (Ubuntu) Importance: Undecided Status: New -- CPU Frequency Scaling defaults to "Performance" instead of "OnDemand" https://bugs.launchpad.net/bugs/344252 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 344252] Re: CPU Frequency Scaling defaults to "Performance" instead of "OnDemand"
Yep, confirmed here too. Even when updating /sys/devices/cpu0/cpufreq/scaling_governer (for both my CPUs), it still reverts back to Performance on next boot, so clearly there's a script over-writing this. I thought there might be something in /etc/default, but I can't see anything relevant at a glance (I'm no expert). -- CPU Frequency Scaling defaults to "Performance" instead of "OnDemand" https://bugs.launchpad.net/bugs/344252 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 339228] Re: gnome-settings-daemon and gnome-display-properties slow down xserver when external monitor added
Latest updates as of today appear to have fixed this issue here. MacMini, Intel graphics, Jaunty Alpha 6 install with latest updates. -- gnome-settings-daemon and gnome-display-properties slow down xserver when external monitor added https://bugs.launchpad.net/bugs/339228 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 328679] Re: keyboard bindings partially ignored
I think that the gnome-compatibility plug-in should be considered a default-on whenever compiz is enabled by Ubuntu GUIs (such as the System/Preferences/Appearance dialog). If you use Appearance to turn on Compiz, on a new install, not only will keyboard shortcuts break instantly because gnome-compatibility-plugin isn't activate by default, but you'll also have no easy way to fix this (well, apart from turning off compiz again) because the compiz settings manager is also not installed by default on a new Ubuntu installation. I don't think many new users will make the connection between turning on graphical effects and their key bindings breaking. And although you might then argue that new users won't be using Alt-F2, they probably will use printscreen. -- keyboard bindings partially ignored https://bugs.launchpad.net/bugs/328679 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 327442] Re: use metacity snapping behavior
As Nerd_bloke notes, this is definitely a regression from Intrepid. If you turn on Compiz via the appearance menu, you'll have no way to override this behaviour since Ubuntu doesn't ship with ccsm by default. On small screens (well, in fact just about any screen smaller than 1280x1024), this makes moving a window pretty much impossible - the default "stickiness" of the snap means that you can't get the window away from the sides of the screen. -- use metacity snapping behavior https://bugs.launchpad.net/bugs/327442 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 347512] [NEW] Regression : Inbuilt Bluetooth devices are no longer recognised
Public bug reported: On my both an old Dell x300 and a new Toshiba U-400 laptop, the built in bluetooth device is not recognised in Jaunty 9.04. An external dongle, however, is recognised and works correctly. I have reproduced this behaviour using both Bluez-gnome and Blueman 1.02 (from Blueman developer's PPA). Using Intrepid 8.10, the internal bluetooth device is recognised correctly in both laptops. The built-in in bluetooth dongle is correctly identified on my MacMini, so this issue is related only the certain bluetooth models in those affected laptops. This bug report is possibly linked to https://bugs.launchpad.net/blueman/+bug/317566, but that bug is filed directly against blueman and I believe that this is a kernel/driver issue. Please let me know if there is additional information I can provide to diagnose the issue. ** Affects: ubuntu Importance: Undecided Status: New -- Regression : Inbuilt Bluetooth devices are no longer recognised https://bugs.launchpad.net/bugs/347512 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 347537] [NEW] Can't change or disable system sounds
Public bug reported:
Binary package hint: gnome-control-center
Using Jaunty 9.04 , in System/Preferences/Sound ("Sounds" tab), it's
impossible to change or disable any of the system sounds. Although they
appear to have changed, when you close the window, everything reverts
back to "default".
Workaround : This issue appears to be caused by the "theme", which is by
default blank. Once you've chosen the "Ubuntu" theme, you can make
changes which stick. NOTE: once you have chosen the "Ubuntu" theme, you
can't revert it back to being blank, so if you wish to confirm this bug,
please do so by making a change while the theme is blank, then closing
the window and re-opening.
I wanted to log this against gnome-sound-properties, but there's no
package for that apparently.
** Affects: gnome-control-center (Ubuntu)
Importance: Undecided
Status: New
--
Can't change or disable system sounds
https://bugs.launchpad.net/bugs/347537
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 346095] Re: notify-osd doesn't honor my preference
Pardon my inexperience with launchpad, but if this bug has been marked as "invalid", does that effectively close discussion? I notice that the status has not been changed to "wontfix", so is this still a valid bug. If not, has another bug against usability regarding this issue been created and can it be linked to from here? That is, if this bug really is "invalid", then have other bugs been created to address for example : 1. Removing this system is impossible without breaking the ubuntu-desktop meta package (and others it would appear, like gnome-power-manager, and in my case, bizarrely the "Listen" media player, but not Rhythmbox for some reason). 2. Wishlist for positioning 3. Usability bugs against, for example, the length of time a notification stays on the screen (too short for my young sons to actually read them). There just can't be a "sane default" for the length of time some text stays on the screen... people are too diverse. And you can't argue that "it doesn't matter because it's not a big deal if you missed it", because in that case, why bother with putting them on the screen in the first place? There are probably more, but I'm worried that serious issues surrounding this system are being swept under the rug in the run up to beta. -- notify-osd doesn't honor my preference https://bugs.launchpad.net/bugs/346095 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 347512] Re: Regression : Inbuilt Bluetooth devices are no longer recognised
It turns out that this is directly related to bug : https://bugs.launchpad.net/ubuntu/+source/linux/+bug/45021 My Toshiba U-400 needs the Omnibook module in order to use its internal Bluetooth adaptor. Full instructions are here : http://docs.google.com/View?docid=dgd53r6d_36hqmmh4hn, which outlines how to install module-assistant from Debian, compile the omnibook-source module and add it to the modprobe. Works a charm. -- Regression : Inbuilt Bluetooth devices are no longer recognised https://bugs.launchpad.net/bugs/347512 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 45021] Re: including "omnibook" module would help with ACPI support on HP laptops
This is still not changed in Jaunty - I finally got my Toshiba U-400's built-in bluetooth to work by following the guides here : http://docs.google.com/View?docid=dgd53r6d_36hqmmh4hn That guide is probably very similar to the instructions posted by Dave Lentz, above, but as it uses the module-assistant, the whole process becomes four steps, which is a little easier to follow (for me, at any rate, since module-assistant does all the hard work). I'll propose this for Jaunty, but as it's already in beta and final release is only a few weeks away, I doubt anything will move on this now. -- including "omnibook" module would help with ACPI support on HP laptops https://bugs.launchpad.net/bugs/45021 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 407063] Re: Seahorse Not Displaying Password Tab
Is there any chance this fix will hit the repos before the Alpha 4 freeze (4 days away)? -- Seahorse Not Displaying Password Tab https://bugs.launchpad.net/bugs/407063 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 160311] Re: Resizing windows by grabbing window borders is difficult
I love the idea of a transparent border, but I despite ANY snapping behaviour. Regardless, however, I'm not convinced that the work being undertaken as a paper-cut will include such complicated solutions. Rather, the patch Thomas submitted upstream, which includes a slider to determine border thickness would seem to be a nice stop-gap solution until a transparent (and/or snap) solution can be implemented. -- Resizing windows by grabbing window borders is difficult https://bugs.launchpad.net/bugs/160311 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 393012] Re: smb: Error while copying file, "Invalid argument"
I'm not sure what's going on with the upstream bug? http://bugzilla.gnome.org/show_bug.cgi?id=588391 shows (still) as "unconfirmed". Does anyone with know-how on the Gnome bug tracker know what's needed to bring this to the attention of the gnome devs? It seems that Tomas Bzatek, the gvfs dev, asked for confirmation if this was reproducible on smbclient. I think the problem is that the confirmation came from the original bug-poster, possibly rendering the confirmation invalid? -- smb: Error while copying file, "Invalid argument" https://bugs.launchpad.net/bugs/393012 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 160311] Re: Resizing windows by grabbing window borders is difficult
Well, the way I understand it is that Thomas' patch doesn't actually change the theme border thickness? It just adds a slider to the theme customisation controls so that those who want a larger border can drag up the width. No "losers" that I can see. I just don't think that there's been any movement upstream on this, so I don't know if Thomas' bug can be applied directly to Ubuntu. -- Resizing windows by grabbing window borders is difficult https://bugs.launchpad.net/bugs/160311 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 403135] Re: The banshee notification area icon has a black background
Can you try closing Banshee, open system/preferences/appearance and choosing a different theme - say Dust, or Dust Sand - then re-running Banshee to see if it updates its background? -- The banshee notification area icon has a black background https://bugs.launchpad.net/bugs/403135 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 404623] [NEW] Samba shares created by smbclient are read-only
Public bug reported: Binary package hint: samba Full Background : http://ubuntuforums.org/showthread.php?p=7677294#post7677294 In Karmic, Alpha 2 and Alpha 3, when a share is created using the smbclient command (such as AutoFS uses), the share is created read-only. The same configuration on Jaunty results correctly in a read-write share. Having created the share, it's possible to "sudo nautilus" and read/write to the share in question. Has a default changed in smbclient which now needs to be set explicitly when using it to mount cifs shares? ProblemType: Bug Architecture: i386 DistroRelease: Ubuntu 9.04 Package: smbclient 2:3.3.2-1ubuntu3 ProcEnviron: PATH=(custom, user) LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: samba Uname: Linux 2.6.30-020630-generic i686 ** Affects: samba (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 -- Samba shares created by smbclient are read-only https://bugs.launchpad.net/bugs/404623 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 404623] Re: Samba shares created by smbclient are read-only
** Attachment added: "Dependencies.txt" http://launchpadlibrarian.net/29519834/Dependencies.txt -- Samba shares created by smbclient are read-only https://bugs.launchpad.net/bugs/404623 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 404623] Re: Samba shares created by smbclient are read-only
** Tags added: autofs karmic -- Samba shares created by smbclient are read-only https://bugs.launchpad.net/bugs/404623 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 404623] Re: Samba shares created by smbclient are read-only
*** This bug is a duplicate of bug 393012 *** https://bugs.launchpad.net/bugs/393012 ** This bug has been marked a duplicate of bug 393012 smb: Error while copying file, "Invalid argument" -- Samba shares created by smbclient are read-only https://bugs.launchpad.net/bugs/404623 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 75358] Re: ad-hoc networks don't work with Intel wireless
I've just subscribed to this bug since I'm using Lucid on a Toshiba u-400 laptop with Intel wireless - I can't connect to my phone's WIFI Ad-Hoc network. In dmesg I see : [18263.828668] iwlagn :08:00.0: Microcode SW error detected. Restarting 0x200. [18263.867730] Registered led device: iwl-phy0::radio [18263.86] Registered led device: iwl-phy0::assoc [18263.867820] Registered led device: iwl-phy0::RX [18263.867860] Registered led device: iwl-phy0::TX [18263.930687] iwlagn :08:00.0: Microcode SW error detected. Restarting 0x200. I'm not sure if it's relevant, but I'll run Jeremy's apport command and attach the results. -- ad-hoc networks don't work with Intel wireless https://bugs.launchpad.net/bugs/75358 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 75358] Re: ad-hoc networks don't work with Intel wireless
Or not. Apport-collect recognises that I didn't file this bug originally so wants me to file a new bug. Can anyone confirm the best course of action here? -- ad-hoc networks don't work with Intel wireless https://bugs.launchpad.net/bugs/75358 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 393012] Re: smb: Error while copying file, "Invalid argument"
Confirmed in Ubuntu Lucid, beta 2. Autofs still created the /smb folder with 755 permissions, as root. This means that regardless of your credentials, you can't write the resulting folder/share. Putting : /smb/etc/auto.smbuid=1000,gid=1000,--timeout=300 as your /etc/auto.master still works (see comment #27). Pretty much broken, still. -- smb: Error while copying file, "Invalid argument" https://bugs.launchpad.net/bugs/393012 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 45021] Re: including "omnibook" module would help with ACPI support on HP laptops
Since adding the module manually, I haven't had to recompile my kernel once during the lucid development phase. So all that appears to be missing now is the auto detection of a laptop which requires use of the omnibook module. Is this possible? -- including "omnibook" module would help with ACPI support on HP laptops https://bugs.launchpad.net/bugs/45021 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 393012] Re: smb: Error while copying file, "Invalid argument"
And is your share read-only? That's the issue I'm experiencing with autofs. I'd appreciate it if you could confirm this bug if so. However, I don't think anyone is now tracking this bug. I added the "affects project" for autofs too late after the relevant gvfs issues were fixed. Combined with this bug report : https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/211631 which outlines how Karmic is unable to shutdown/restart gracefully when samba shares are specified in /etc/fstab, we now have the depressing situation whereby Karmic is unable to automatically create shares to samba. And this bug : https://bugs.edge.launchpad.net/gnome-mount/+bug/388444 which highlights that gvfs shares aren't automatically mounted appears to be dead too. I don't consider gvfs in its current state as much use for a networked PC. My only option at the moment is to consider abandoning samba and implementing NFS instead, although that's not an option I can take at my workplace. I only have Karmic on one of my boxes. If I ever decide to install it beyond that, I'll probably raise additional bugs on this issue. For the moment, I've lost motivation. -- smb: Error while copying file, "Invalid argument" https://bugs.launchpad.net/bugs/393012 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 522337] Re: Karmic & Lucid WiFi DNS not working
@Neskie : By including OpenDNS servers into your router's config, you have effectively bypassed this bug. Remove the OpenDNS server entries by updating your router and you'll see the issue is very much apparent on Karmic, but is NOT apparent on Macs, Windows or earlier versions of Ubuntu. The issue might be resolver, might be IPv6, might be Network Manager, but it was definitely introduced in Karmic and remains an active bug today. If anyone on the Network Manager team would like to investigate this issue more fully, I'm pretty handy with Wireshark/tcpdump traces too and I'm happy to back up any of the.scarecrows initial reports/traces, if it would be useful to do so. -- Karmic & Lucid WiFi DNS not working https://bugs.launchpad.net/bugs/522337 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"
Nick, if you like them on the, you should change them to the left. But /by default/ these buttons should be on the right for the many, many reasons already discussed on Brainstorm, Planet Ubuntu, Ubuntuforums and this very bug report. Ubuntu. Linux for human beings. I hope that remains the case, despite reports like this one. Funnily enough, I notice that this particular slogan is no longer present on the Ubuntu.com website. -- [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 532633] Re: [Master] Window Control buttons: position/order/alignment
The final release should clear up the remaining aspects of this "design choice" (galling to call it that). System/appearance still shows all themes with buttons on the right. Radiance, Ambiance and Dust have buttons left, while Clearlooks, Dust Sand and New wave have buttons right. No consistency and therefore genuine support headache. Very disappointing. At least the damage is contained to three themes - removing them is just one more thing to do with a new Ubuntu release. -- [Master] Window Control buttons: position/order/alignment 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 532633] Re: [light-theme] please revert the order of the window controls back to "menu:minimize, maximize, close"
It's taken two years and 116 comments here (https://bugs.edge.launchpad.net/metacity/+bug/160311) to make absolutely no progress whatsoever. I doubt we'll be seeing this LTS with buttons on the right. Maybe the next LTS. General "usability" in Ubuntu is pretty low and I think it's down to a complete lack of usability studies. If they /are/ performed, they're being done so privately and the results are remaining private. Until we can see the results of such a study, all we have is one person's opinions against another. And it sounds a lot like Mark's made up his mind on this one - given his comments and participation in this thread and the suspicious timing of this change (on the day of the UI freeze). -- [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 347512] Re: Regression : Inbuilt Bluetooth devices are no longer recognised
The issue still exists in Lucid (10.04) Beta 1. There is no detection of my Toshiba's bluetooth hardware without the omnibook module. Sadly, I've already used module assistant to create a new omnibook- capable kernel on my laptop which experiences the issue, so I don't want to be running that kernel when I run the apport-collect command. I'll reboot over the next couple of days and send that information. I've never tested an upstream kernel before either, but will follow the link and do my best to complete that work too. -- Regression : Inbuilt Bluetooth devices are no longer recognised https://bugs.launchpad.net/bugs/347512 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: [Master] Window Control buttons: position/order/alignment
Jeff makes a good point about his wife exclaiming "Can't they leave anything alone??". We had similar immense pain when we upgraded to Office 2007 at my work. The office "ribbon" wasn't just viewed as a waste of developer time by our staff, but also caused actual affront. As if Microsoft had scrapped toolbars and introduced the ribbon very specifically to annoy our staff. A short article corroborating this experience : http://j-walkblog.com/index.php?/weblog/posts/office_2007_training/ (Yes, we upgraded anyway, but by god, yes, we needed a /lot/ of training and nearly two years later, few have anything good to say about the ribbon) As for the latest updates making the buttons theme-dependent, this is kind of good news, but I also worry that even simply offering a theme with buttons on the left will introduce very real support issues. For example, when supporting PC-illiterate staff remotely and without access to VNC/screen control - you may have to ask these people to "move your mouse up to the top right of the window and click on the little "x" button". Well, that's not going to work if they've chosen a radiance theme, is it? A minor point perhaps, but we've been asked for data, so here it is. The way this change was introduced, the blind-siding and subsequent utter silence on the matter and the recent comment spam from Pako and to a less extent, Scholli, have made it extremely difficult for me to see the matter objectively. And I can't believe that there /still/ hasn't been any real counter arguments to comment #71. That comment, incidentally, was a touch over two weeks ago. I know. It feels longer. -- [Master] Window Control buttons: position/order/alignment 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
Re: [Bug 532633] Re: [light-theme] please revert the order of the window controls back to "menu:minimize, maximize, close"
I don't think many people thought this was a vote. We're not voting, we're complaining, in the only manner open to us as members of the community - in a bug report. The problem is that no-one appears to be listening, despite the excellent arguments against this decision. And no-one has yet tried to counter those arguments. That's not good. On 17 Mar 2010 22:34, "fewt" wrote: "you don't get to second-guess their decisions" "You don't get to see a lot of what they see unless you're on that team." "being an open community is not the same as saying everybody has a say in everything." "There aren't any good reasons for that" "we are not voting on design decisions." So, its your ball, it isn't a community ball and if we don't like it we shouldn't use your distribution because it belongs to you, your team, and no one else. I get it now. Thanks for the clarification, and all of these great one-liners. -- [light-theme] please revert the order of the window controls back to "menu:minimize,maximize,cl... -- [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 532633] Re: [light-theme] please revert the order of the window controls back to "menu:minimize, maximize, close"
Still no comments from the design team at all? Compiz, Firefox,, gnome- appearance, gnome-shell, etc that will need to be remodelled? What about the users who don't like the buttons on the left and swap it to the right - will they therefore forgo the pleasures of Cool New Stuff when 10.10 comes out? Will doing so break themes? Worse still, will everything be patched to have close-on-left and therefore look stupid when users change to buttons-on-right? What about Kubuntu and the other distros which don't appear to have picked up this change? What about a simple method of feedback to guage how many users oppose this? All questions asked over and over again in this thread, met with total and utter silence. -- [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 532633] Re: [light-theme] please revert the order of the window controls back to "menu:minimize, maximize, close"
Shouldn't this bug, by now, be assigned to someone on the desktop experience team? And can anyone confirm when a decision will be made regarding this? And still no comments from anyone who was responsible for this? Other, obviously, Mark himself. Or any rebuttal to comments made in post 71? -- [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 160311] Re: Resizing windows by grabbing window borders is difficult
Woah! I wouldn't go /that/ far! But at least you'd be able to resize windows, eh? :-) If you don't change your theme much, I recommend following the instructions I posted way back in comment 58 (https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/160311/comments/58). It's clunky and manual, but it works and results in a usable theme regardless of which one you choose. And with Lucid in interface freeze, this isn't getting fixed for another 6 months now. -- Resizing windows by grabbing window borders is difficult https://bugs.launchpad.net/bugs/160311 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 393012] Re: smb: Error while copying file, "Invalid argument"
The shutdown bug is being discussed here : https://bugs.launchpad.net/ubuntu/+source/network- manager/+bug/211631?comments=all, but there's no fix as yet. The umountcifs.sh script does still work, but as I say, Network Manager drops the WIFI connection far, far too early in the shutdown process for it to have any impact. Seems to be a change from Jaunty to Karmic in how the shutdown scripts are processed - possibly upstart related, since even running umountcifs in K01 is quick enough. -- smb: Error while copying file, "Invalid argument" https://bugs.launchpad.net/bugs/393012 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 211631] Re: Network is brought down before network filesystems are unmounted (CIFS timeout at shutdown)
@James : That would be awesome and exactly what I'll propose to the networkmanager list (when I get round to it). @Sixela : As H3g3m0n notes, the bug is still apparent on WIFI systems. In general, worth noting another reason gvfs shares don't always work out - nautilus won't process thumbnails for "remote" filesystems by default and it considers gvfs mounts as remote (fair enough). Meanwhile, fstab filesystems aren't considered remote. It's not feasible in my case to turn on previewing in all remote systems, since if I use my laptop at work, it'll connect to systems where a preview of the files would not be desirable (too slow). -- Network is brought down before network filesystems are unmounted (CIFS timeout at shutdown) https://bugs.launchpad.net/bugs/211631 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 211631] Re: Network is brought down before network filesystems are unmounted (CIFS timeout at shutdown)
Confirmed here too. I've tried all the solutions listed previously to resolve this issue in Karmic and Wireless, but I always experience a hang on shutdown. The only "workaround" (not really) I've found so far is to add the "users" option to my /etc/fstab entry for my cifs share, then manually unmount the volume before shutting down / restarting the laptop. Although the umountcifs script still works when run manually, I've tried linking to just about every position in /etc/rc0.d (and /etc/rc6.d) with no success. A linked thread here also suggests putting umountcifs in /etc/gdm/Postsession/default - all that seems to do is break the exit usplash (or whatever that's called now - the ubunut logo thing that fades away) - but the hang persists. Is there perhaps some kind of upstart configuration that needs to be modfied in Karmic to emulate the K0umountcifs behaviour? -- Network is brought down before network filesystems are unmounted (CIFS timeout at shutdown) https://bugs.launchpad.net/bugs/211631 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 45021] Re: including "omnibook" module would help with ACPI support on HP laptops
It would appear that we've missed the Karmic boat for this bug : http://www.linux-archive.org/ubuntu-kernel-team/376283-ubuntu-lp-438323-added-omnibook-module-support-toshiba-hp.html >From that, I read that there's a possibility that this module could make it to Jaunty as a DKMS module. Sadly, I have no idea what that means or entails. I know that the directions I followed (see comment 18 : https://bugs.edge.launchpad.net/ubuntu/+source/linux/+bug/45021/comments/18) to compile this in Jaunty now fail due to unresolvable dependencies in Karmic, so any help to investigate this DKMS option would be greatly appreciated. I rely on my bluetooth module in order to use my 3G phone (as a modem) and my bluetooth mouse, so my laptop is stuck on Jaunty until I can activate my Omnibook driver in Karmic somehow. -- including "omnibook" module would help with ACPI support on HP laptops https://bugs.launchpad.net/bugs/45021 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 393012] Re: smb: Error while copying file, "Invalid argument"
Przemysław Kochański, you've indicated that you've tested this and it works. Can you post details of what you tested? As previously stated, I've updated to smbclient 3.4.0-3 (now ubuntu5 as of posting), but all my smb shares are /still/ mounted read-only by autofs. Should I open another bug? Steps to replicate : 1. Create a standard samba share on your server with read/write guest access, no password. I use Jaunty 64-bit for my server. 2. Install beta karmic on your client PC, then update fully. 3. Install autofs (I've also tried autofs5, with same result). 4. edit /etc/auto.master and uncomment /smb line 5. sudo invoke.rc.d autofs restart 6. Use nautilus to browse to /smb// You'll notice your share is read-only. Now run gksudo nautilus and browse to the same directory for read/write access. The exact same procedure on a Jaunty build results in read/write shares as expected. -- smb: Error while copying file, "Invalid argument" https://bugs.launchpad.net/bugs/393012 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 393012] Re: smb: Error while copying file, "Invalid argument"
No change here, using AutoFS to mount my shares - they're all still read-only unless I run nautilus with sudo. sca...@groovy:~$ dpkg-query -W smbclient smbclient 2:3.4.0-3ubuntu1 Latest smbclient appears to be installed and my auto.master simply mounts the share using smbclient. Is there something I'm missing here - perhaps something that needs to be updated in the auto.smb script in order to restore Jaunty's read/write behaviour using this new smbclient package? I'll add the autofs package to this bug report in the hope that someone can help. ** Also affects: autofs Importance: Undecided Status: New -- smb: Error while copying file, "Invalid argument" https://bugs.launchpad.net/bugs/393012 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 55780] Re: Dell Inspiron WiFi light does not show on/off status
Still apparent on Ubuntu 9.10 (Karmic Koala), fully up to date as of 3rd January 2010. @S B : the bug is "confirmed" when the bug is still open and apparent. It will change to either "Fix released" or "Won't fix" depending on the solution/lack thereof. -- Dell Inspiron WiFi light does not show on/off status https://bugs.launchpad.net/bugs/55780 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 328679] Re: keyboard bindings partially ignored
As comment three points out, you need the compiz-settings-manager to enable gnome-compatibilty to get your keyboard shortcuts back (although this should be auto-detected and added automatically by Karmic). This app also includes a "reset to default value" button on almost all effects. You can use this to reset the bindings you've chnaged. -- keyboard bindings partially ignored https://bugs.launchpad.net/bugs/328679 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 211631] Re: Network is brought down before network filesystems are unmounted (CIFS timeout at shutdown)
Hi Spaetz. That "fix" was documented as early as comment 7 and is discussed thoroughly throughout the 110 or so comments. Sadly, the fix doesn't work in Karmic any more. Well, I'll qualify that - it works for wired connections, but not for WIFI. Network Manager brings WIFI connections down internally on a shutdown signal BEFORE any startup/shutdown script is run. I recommend anyone still affected by this bug to use autofs to mount their CIFS and NFS shares. Autofs gracefully kills the connection on an interface disconnection without triggering the dreaded "CIFS VFS server not responding" message and subsequent 90 second delay. I *think* that this bug is only apparent now if : a) You're mounting remote NFS/CIFS shares by specifying them in /etc/fstab AND b) You're using WIFI to connect to said shares and you forget to disconnect/unmount the shares before shutting down. Correct me if I'm wrong. I'm not sure if there's a way to update the bug to reflect this? -- Network is brought down before network filesystems are unmounted (CIFS timeout at shutdown) https://bugs.launchpad.net/bugs/211631 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 346095] Re: Regression: bubble location setting from notification-daemon is not migrated to notify-osd
Erick, people will "flog the team" until one of them marks this bug "won't fix". Why hasn't that happened if SABDFL's word is law? Actually, I do agree that it's nice that a decision is sometimes made, even if I myself feel it's the wrong one. But bug reports like this are important to argue/highlight that Mark sometimes /does/ make the wrong decision. Up to a point, at least. If that point has now been reached, change its status and be done. Ultimately, I get that Mark has final say, but if we can't even present argument for and against anymore, then the community around Ubuntu will eventually drift away to where they're valued. Hopefully that won't be the case. -- Regression: bubble location setting from notification-daemon is not migrated to notify-osd https://bugs.launchpad.net/bugs/346095 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 344252] Re: CPU Frequency Scaling defaults to "Performance" instead of "OnDemand"
I've changed laptops since reporting this bug 18 months ago. This is no longer the case on my Toshiba Satellite U405. I can no longer contribute to this bug except to suggest that this bug would go away if the app remembered what the user chose and stick to it. A common trait on the Gnome desktop - try turning off WIFI or Bluetooth, then reboot. Bam! Back on again. Pretty frustrating. Someone else will have to confirm this bug, assuming it's still an issue in Maverick or Lucid. -- CPU Frequency Scaling defaults to "Performance" instead of "OnDemand" https://bugs.launchpad.net/bugs/344252 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: [Master] Window Control buttons: position/order/alignment
@Pako : you can't "prove" an opinion, which is what left vs right is. @bhaavanmerchant : You should be able to change theme from the appearance menu - no need for anything else. I typically install "Shiki-Color" from the repo, then switch to that. The buttons will instantly be back to normal. @Everyone, this bug is now closed. Mark has left the discussion (he's not notified directly of these comments any more), the bug status is "won't fix" and the default positioning is staying on the left. You can still, so far, simply change them back to the right again. This bug report is now (always was, in hindsight) just noise and I'm un- subscribing from it too. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/532633 Title: [Master] Window Control buttons: position/order/alignment To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/light-themes/+bug/532633/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 211631] Re: Network is brought down before network filesystems are unmounted (CIFS timeout at shutdown)
Your options are : 1. Use a wired connection 2. Avoid Samba/CIFS shares and configure your server for NFS instead 3. Use AutoFS to create your network shares. In case 3, AutoFS replaces the need to configure anything in /etc/fstab. Seems to work well enough with most connections, although another bug (https://bugs.launchpad.net/autofs/+bug/393012/comments/34) will give you some issues when you first set it up. Samba shares and Ubuntu, at least over WIFI, don't make for a very happy experience, I'm afraid. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/211631 Title: Network is brought down before network filesystems are unmounted (CIFS timeout at shutdown) To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/211631/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 831604] Re: likewise-open users don’t get ecryptfs home directory
Are there manual workarounds for this? Full disk encryption is too clunky for corporate use and the lack of encrypted home folders in an Active Directory environment means missing a huge advantage an Ubuntu install would have over a Windows device. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/831604 Title: likewise-open users don’t get ecryptfs home directory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/likewise-open/+bug/831604/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 160311] Re: Resizing windows by grabbing window borders is difficult [please no more comments; patches welcome]
Comment #11 already details how to manually work around this bug. Of course, if you change theme thereafter, you'll have to edit that theme's metactiy-1.xml file too. https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/160311/comments/11 I hate to be doom and gloom, but this metacity bug is upstream on gnome : for a couple of reasons, it's unlikely to be fixed ever. The upstream bug had a patch issued Dec 2008 (!), since ignored and the last comment there was January this year. It's much more likely that this will be addressed in Gnome 3. To that end, I'd recommend hacking your themes until then. It's been three and a half years now and nominated for every release of Ubuntu since it was raised, so I can't see anyone taking up this torch when a new Gnome and theme engine are just round the corner. To my mind, the importance (low) of this bug speaks volumes regarding whether it will be fixed. Perhaps Ayatana will make a difference, but sadly Paper Cuts didn't (it was ignored by the last two Paper Cuts attempts). Sorry if I sound jaded. In my head, this bug was buried a long time ago. -- Resizing windows by grabbing window borders is difficult [please no more comments; patches welcome] https://bugs.launchpad.net/bugs/160311 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 658481] [NEW] Toshiba U400 won't suspend when Bluetooth is enabled
Public bug reported: Binary package hint: bluez Although the bluetooth module in my Toshiba Satellite Pro U400 is now recognised out of the box (without the need for the Omnibook module), it prevents my laptop from entering suspend. Attempting to enter suspend while the bluetooth is enabled causes a hardlock. Once this occurs, a power down is the only options (CTRL-ALT terminal not responsive, CTRL- ALT-SYSRQ commands not responsive - not even REISUB). If I click on the indicator applet to disable bluetooth, suspend (and resume) works as it did on Lucid. This is completely reproducible. There's nothing in /var/log/pm- suspend.log, but I'll attach working and non-working examples nonetheless. An Ubuntu Forums suggestion to disable NVS saving had no effect (http://ubuntuforums.org/showthread.php?t=1586178&page=5). ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: bluez 4.69-0ubuntu2 ProcVersionSignature: Ubuntu 2.6.35-22.33-generic 2.6.35.4 Uname: Linux 2.6.35-22-generic i686 Architecture: i386 Date: Mon Oct 11 16:42:38 2010 InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007) InterestingModules: rfcomm sco bnep l2cap btusb bluetooth MachineType: TOSHIBA Satellite Pro U400 ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-22-generic root=UUID=ba4e6587-4b1a-4642-9f6b-bb14bb3158b9 ro quiet splash acpi_sleep=nonvs ProcEnviron: LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: bluez dmi.bios.date: 07/14/2008 dmi.bios.vendor: TOSHIBA dmi.bios.version: V1.10 dmi.board.name: Satellite Pro U400 dmi.board.vendor: TOSHIBA dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: N/A dmi.modalias: dmi:bvnTOSHIBA:bvrV1.10:bd07/14/2008:svnTOSHIBA:pnSatelliteProU400:pvrPSU45E-005005EN:rvnTOSHIBA:rnSatelliteProU400:rvrNotApplicable:cvnTOSHIBA:ct10:cvrN/A: dmi.product.name: Satellite Pro U400 dmi.product.version: PSU45E-005005EN dmi.sys.vendor: TOSHIBA hciconfig: hci0: Type: BR/EDR Bus: USB BD Address: 00:03:7A:91:59:03 ACL MTU: 1021:6 SCO MTU: 64:1 UP RUNNING PSCAN RX bytes:2028 acl:0 sco:0 events:69 errors:0 TX bytes:2694 acl:0 sco:0 commands:69 errors:0 ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 maverick -- Toshiba U400 won't suspend when Bluetooth is enabled https://bugs.launchpad.net/bugs/658481 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 658481] Re: Toshiba U400 won't suspend when Bluetooth is enabled
** Attachment added: "BootDmesg.txt" https://bugs.launchpad.net/bugs/658481/+attachment/1685171/+files/BootDmesg.txt ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/658481/+attachment/1685172/+files/CurrentDmesg.txt ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/658481/+attachment/1685173/+files/Dependencies.txt ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/658481/+attachment/1685174/+files/Lspci.txt ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/658481/+attachment/1685175/+files/Lsusb.txt ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/658481/+attachment/1685176/+files/ProcCpuinfo.txt ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/658481/+attachment/1685177/+files/ProcInterrupts.txt ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/658481/+attachment/1685178/+files/ProcModules.txt ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/658481/+attachment/1685179/+files/UdevDb.txt ** Attachment added: "UdevLog.txt" https://bugs.launchpad.net/bugs/658481/+attachment/1685180/+files/UdevLog.txt ** Attachment added: "rfkill.txt" https://bugs.launchpad.net/bugs/658481/+attachment/1685181/+files/rfkill.txt ** Attachment added: "syslog.txt" https://bugs.launchpad.net/bugs/658481/+attachment/1685182/+files/syslog.txt -- Toshiba U400 won't suspend when Bluetooth is enabled https://bugs.launchpad.net/bugs/658481 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 658481] Re: Toshiba U400 won't suspend when Bluetooth is enabled
I can't get a working suspend anymore - literally just once it worked, now it just hangs again, regardless of Bluetooth. If anyone can help troubleshoot the problem, that would be great. In the meantime, I attach the /var/log/pm-suspend.log I took of a "hung" connection. It doesn't look like it'll be any help. ** Attachment added: "Log written just before complete hang." https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/658481/+attachment/1685352/+files/FAILED-pm-suspend.log -- Toshiba U400 won't suspend when Bluetooth is enabled https://bugs.launchpad.net/bugs/658481 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 658481] Re: Toshiba U400 won't suspend when Bluetooth is enabled
Recent kernel update (Tuesday 11th Oct 2010) has made a slight improvement. I now get one suspend/resume. All subsequent attempts to suspend thereafter fail with identical symptoms to this initial bug report. If anyone can help troubleshoot this, I'd greatly appreciated it. -- Toshiba U400 won't suspend when Bluetooth is enabled https://bugs.launchpad.net/bugs/658481 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 658481] Re: Toshiba U400 won't suspend when Bluetooth is enabled
Well, I need suspend/resume more than I need my bluetooth mouse, so I've got the following (rubbish) workaround to disable bluetooth : Edit /etc/modprobe.d/blacklist.conf Add the following lines at the bottom : # Added October 11th 2010 blacklist toshiba_bluetooth blacklist bluetooth Reboot. Suspend/Resume is now working, but of course, no bluetooth any more. I'll maybe try compiling my own Omnibook module as per this ancient article : https://docs.google.com/View?docid=dgd53r6d_36hqmmh4hn. I'm not sure it's even relevant anymore, but whatever - worth a shot. -- Toshiba U400 won't suspend when Bluetooth is enabled https://bugs.launchpad.net/bugs/658481 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 160311] Re: Resizing windows by grabbing window borders is difficult
There are lots of workarounds in the previous 163 comments, but this 3 year old bug doesn't need workarounds, it needs Ayatana members or others to address the issue before we reach a seventh release of Ubuntu without a fix. -- Resizing windows by grabbing window borders is difficult https://bugs.launchpad.net/bugs/160311 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 160311] Re: Resizing windows by grabbing window borders is difficult
For reference, Ayatana are actually discussing this right now. https://lists.launchpad.net/ayatana/msg03040.html As usual, the Ayatana team take a particularly high-level view of issues like this, so instead of discussing how to implement borders that can actually be dragged without ninja-like precision, they are instead discussing why we need to re-size in the first place and wouldn't it be a far better solution if you never had to resize a window... Still, this might help alleviate the frustration felt by subscribers to this bug - knowing that's it's well known, understood and someone out there cares. -- Resizing windows by grabbing window borders is difficult https://bugs.launchpad.net/bugs/160311 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
