[Bug 551950] Re: gnome-bluetooth cannot use pin = 1234
Still a problem in 14.04LTS. Had to revert to using bluetooth manager, again. Works every time with bluetooth manager. Why has this not been addressed?!?!?!?! -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-bluetooth in Ubuntu. https://bugs.launchpad.net/bugs/551950 Title: gnome-bluetooth cannot use pin = 1234 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-bluetooth/+bug/551950/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 551950] Re: gnome-bluetooth cannot use pin = 1234
I guess I don't fully get your response. This has been noted as a bug since saucy and has never had a patch or workaround associated with it (other than using bluman instead of gnome-bluetooth). Is there a better bug list for gnome specific problems than here? -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-bluetooth in Ubuntu. https://bugs.launchpad.net/bugs/551950 Title: gnome-bluetooth cannot use pin = 1234 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-bluetooth/+bug/551950/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1228939] Re: The "turn screen off when inactive for" option is not saved
not fixed. Still present. I can select any time I want in the 'turn screen off' dialog box, it saves it, but the screen never turns off. This is with the Nvidia driver and Gnome 3 window manager, do not know of that is pertinent or not. I confirm it on 2 installs where 13.10 is upgraded from 13.04. Used to work in all ubuntu releases I can remember. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1228939 Title: The "turn screen off when inactive for" option is not saved To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1228939/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 373477] Re: Can't save files to Samba (cifs) shares because they report 0 bytes free
In 12.04, it is still an issue. I run 13.10 at home and it appears fixed, there, but not in 12.04. Using Wine/Excel 2007. Cannot open a file from the server share (windows domain), but need to use nautilus to get it local edit then put it back on server via nautilus. Like I said, I think this is fixed in 13.10+, because I can VPN in and edit the files directly on the share from MSoffice running in Wine, but not in 12.04. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/373477 Title: Can't save files to Samba (cifs) shares because they report 0 bytes free To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/373477/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1582048] [NEW] cannot timeout suspend GDM from logind
Public bug reported: Previously (12.04 - 15.04), if I edited the /etc/systemd/logind.conf file to auto suspend the GDM login screen it worked. Now, if I edit the 2 lines to cause a suspend if the login screen (GDM) is up and no one logs in for 15 minutes, I get unintended random suspend from an active, logged in user. The edit I make is to uncomment 2 lines: ... IdleAction=suspend IdleActionSec=15min ... This happens with 15.10 and 16.04 and is repeatable on my 3 machines. 1 is nvidia current, another nvidia legacy and another is i915. All were clean installs (not upgraded) Release: Description:Ubuntu 16.04 LTS Release:16.04 Version: systemd: Installed: 229-4ubuntu5 Candidate: 229-4ubuntu5 Version table: *** 229-4ubuntu5 500 500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 100 /var/lib/dpkg/status 229-4ubuntu4 500 500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages What I expect: If no user is logged in, the GDM screen should suspend. If a user is logged in, it should not suspend What happens: after a user logs in, the computer will suspend after 15 min. There is nothing odd in the dmesg log. It just appears as any suspend event. If a user is logged in, it should not suspend unless the user has a timeout and suspend set fort their login. ** Affects: systemd-shim (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd-shim in Ubuntu. https://bugs.launchpad.net/bugs/1582048 Title: cannot timeout suspend GDM from logind To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd-shim/+bug/1582048/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1773801] [NEW] gvfs will not allow a NFS mount
Public bug reported: gvfs will not allow an NFS mount. In nautilus, one cannot mount an NFS mount using 'other locations'. If a valid url is typed, (nfs://IP _ADDRESS/MOUNT_POINT one can never select 'connect' as it is always greyed out. Fully up to date ubuntu 18.04. Duplicates same behavior on 2 machines. Also impedes deja-dup using nfs for backups. This functionality works as expected in Arch with the Gnome interface. $ lsb_release -rd Description:Ubuntu 18.04 LTS Release:18.04 $ apt-cache policy gvfs gvfs: Installed: 1.36.1-0ubuntu1 Candidate: 1.36.1-0ubuntu1 Version table: *** 1.36.1-0ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status ** Affects: gvfs (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1773801 Title: gvfs will not allow a NFS mount To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1773801/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1637988] Re: gvfsd-nfs not present in gvfs-backends, why?
Still an issue with 18.04. FWIW, it is included in the Arch version of Gnome and gvfs-nfs works in Arch. Both in Nautilus and in DejaDup. NFS should also be a possible means of a backup with deja-dup, but because this module is not included in gvfs, it does not work. Waiting for this regression to be remedied. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1637988 Title: gvfsd-nfs not present in gvfs-backends, why? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1637988/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 551950] Re: gnome-bluetooth cannot use pin = 1234
Still broken in 13.10. You can select special pin, but not continue to pair it. It is a shame this has been broken for so long and such a simple repair. My work around is to use bluetooth manager instead of gnome bluetooth. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-bluetooth in Ubuntu. https://bugs.launchpad.net/bugs/551950 Title: gnome-bluetooth cannot use pin = 1234 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-bluetooth/+bug/551950/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 551950] Re: gnome-bluetooth cannot use pin = 1234
Sounds like a rewrite is in order. Blueman always works for me. Gnome Bluetooth is pretty well broken, IMO. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-bluetooth in Ubuntu. https://bugs.launchpad.net/bugs/551950 Title: gnome-bluetooth cannot use pin = 1234 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-bluetooth/+bug/551950/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 930848] Re: USB BT dongle freezes machine
For what it is worth, this same dongle hangs a windows 7 machine as well as a Mac. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-bluetooth in Ubuntu. https://bugs.launchpad.net/bugs/930848 Title: USB BT dongle freezes machine To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-bluetooth/+bug/930848/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 930848] [NEW] USB BT dongle freezes machine
Public bug reported: new BT dongle is very flaky. If it will pair, whenever it is used to send any data, it freezes the machine (flashing caps lock and num lock leds). The only way to get it back is to press and hold the power button. I have 2 other dongles which work fine. It announces itself as a "ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)" like the another one I have. I have been able to make it work under Win7 x64. usb-devices reports more information: T: Bus=04 Lev=01 Prnt=01 Port=03 Cnt=01 Dev#= 9 Spd=12 MxCh= 0 D: Ver= 2.00 Cls=e0(wlcon) Sub=01 Prot=01 MxPS=64 #Cfgs= 1 P: Vendor=0a12 ProdID=0001 Rev=19.15 C: #Ifs= 2 Cfg#= 1 Atr=c0 MxPwr=0mA I: If#= 0 Alt= 0 #EPs= 3 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb I: If#= 1 Alt= 0 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb The key is the Rev 19.15. This one does not work I have another one which reports Rev 01.34 and it works fine. I have seen this showing up around the web. The compatibility lists all list Cambridge Silicon Radio, Ltd 0a12:0001, but not all of these devices that report this are the same, or so it appears. Don't know if it just because it is a BT 2.0 and it is incorrectly assigned a driver. This is on Ubuntu 11.10 x64 This is with gnome-bluetooth or Bluetooth-manager I got a freeze, I expected a connection and a file transfer ** Affects: gnome-bluetooth (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-bluetooth in Ubuntu. https://bugs.launchpad.net/bugs/930848 Title: USB BT dongle freezes machine To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-bluetooth/+bug/930848/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 930848] Re: USB BT dongle freezes machine
The chip in the adapter is marked OVC3620. Do not know if this is helpful or not. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-bluetooth in Ubuntu. https://bugs.launchpad.net/bugs/930848 Title: USB BT dongle freezes machine To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-bluetooth/+bug/930848/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 255228] Re: Disabling the suspend and hibernate locks via gconf-editor doesn't do anything (from Intrepid to lucid included)
>From a clean install of 64 bit Natty, it works as expected. I set the gconf settings so that it does not lock the screen. To make thsi really work, I had to set the gconfedit setting Desktop -> Gnome -> Lockdown disable_lock_screen and now it will not ask for a password if I suspend it from that user profile. Yea! -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in Ubuntu. https://bugs.launchpad.net/bugs/255228 Title: Disabling the suspend and hibernate locks via gconf-editor doesn't do anything (from Intrepid to lucid included) -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 574046] Re: shares-admin doesn't "see" NFS and SMB installed (no support for Upstart jobs)
This version did not work for me. I am running 10.10 - fully updated and was running gnome-system-tools 2.32.0. Still not recognizing that Samba was installed and running. To get it to work I had to create a sym link. "sudo ln -s /etc/init.d/smbd /etc/init.d/samba". Will this change again when samba4 goes mainstream? -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-system-tools in ubuntu. https://bugs.launchpad.net/bugs/574046 Title: shares-admin doesn't "see" NFS and SMB installed (no support for Upstart jobs) -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 501207] Re: sound-juicer, rhythmbox, nautilus crash at audio CD insertion
I am running 32 bit 10.10 fully up to date. It appears that sound juicer will extract music. When I put the CD in the drive with rhythmbox, though, it crashes. dmesg shows this: [35518.296548] rhythmbox[4357]: segfault at 0 ip 02aa531a sp b1fe3120 error 6 in libnss_wins.so.2[2a5c000+2c7000] [35531.484507] rhythmbox[4372]: segfault at 0 ip 02a9431a sp b02fe120 error 6 in libnss_wins.so.2[2a4b000+2c7000] [35588.795612] rhythmbox[4412]: segfault at 0 ip 0425731a sp ae79a120 error 6 in libnss_wins.so.2[420e000+2c7000] [35748.654722] rhythmbox[4489]: segfault at 0 ip 02d6431a sp b01fd120 error 6 in libnss_wins.so.2[2d1b000+2c7000] [36080.848801] rhythmbox[4550]: segfault at 0 ip 035ff31a sp afffe120 error 6 in libnss_wins.so.2[35b6000+2c7000] -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to brasero in ubuntu. https://bugs.launchpad.net/bugs/501207 Title: sound-juicer, rhythmbox, nautilus crash at audio CD insertion -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 581277] Re: rhythmbox crashes when clicking a radio stream
Broken again. Tried streams the other day and it crashes Rhythmbox. Click on Last FM and it crashes. Select and double click on a stream and it crashes as well. If you select the stream and hit play, it will play the first song in the playlist (not the stream). If you double click the stream it crashes with this: (19:06:45) [0x9584e68] [playing_changed_cb] rb-mpris-plugin.c:888: emitting PlaybackStatus change (19:06:45) [0x9584e68] [show_controls] rb-visualizer-plugin.c:852: showing controls (19:06:45) [0x9584e68] [paned_size_allocate_cb] rb-shell.c:2949: paned position 160 (19:06:45) [0x9584e68] [paned_size_allocate_cb] rb-shell.c:2950: right_paned position 400 (19:06:45) [0x9584e68] [rb_statusbar_sync_status] rb-statusbar.c:472: updating status with: '19 stations', 'Connecting', 0.00 Segmentation fault -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to rhythmbox in ubuntu. https://bugs.launchpad.net/bugs/581277 Title: rhythmbox crashes when clicking a radio stream -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 581277] Re: rhythmbox crashes when clicking a radio stream
Oh yes, I forgot, this is with Ubuntu 10.10 fully updated. It worked at one time, but no longer. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to rhythmbox in ubuntu. https://bugs.launchpad.net/bugs/581277 Title: rhythmbox crashes when clicking a radio stream -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 255228] Re: Disabling the suspend and hibernate locks via gconf-editor doesn't do anything (from Intrepid to lucid included)
I also have this same problem in Maverick. The recipe I used is here: http://ubuntuforums.org/showthread.php?t=1466504 I have even tried disabling password for this account from the users menu. I have tried disabling all accounts except one. No matter what, I still get a login dialog box. It is not the same dialog box as the main login dialog. I get 'username' with a blank box. I type it in then this goes away and comes back with 'password' and a blank box. Once I type it in, it all comes back. When I set the user to not require a password, I still get the first dialog box asking for username. then it goes directly to the desktop. This is a public account and I want the machine to suspend when not in use and come back when needed. If I were to log in with my credentials, I would not want this behavior, but the one login is fine. I am pretty happy that I have been able to get WOL working and suspend almost working. If I can get this bug resolved, I am in business! Well, not just this bug. Also my sound card does not want to come back and I have to issue a "sudo alsa force- reload" in order to get sound back when I resume, but that is probably another bug. And I have a workaround for that one... -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in ubuntu. https://bugs.launchpad.net/bugs/255228 Title: Disabling the suspend and hibernate locks via gconf-editor doesn't do anything (from Intrepid to lucid included) -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 562714] Re: cannot parse valid podcast feeds
ongoing issue in 10.4 as well. "Error in podcast. There was a problem adding this podcast. Unable to parse feed contents." This is with my podcasts as well as the npr podcast feed listed above. Please advise. this is with 0.12.8 fully up to date. If I could get gtkpod to work, i'd use that. -- cannot parse valid podcast feeds https://bugs.launchpad.net/bugs/562714 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to rhythmbox in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 562714] Re: cannot parse valid podcast feeds
If I were to guess, there was a 'fix' to PHP that is causing Rhythmbox to be broken... Do not know the workings of this, but it is annoying... If it is a regular http link, it seems to work just fine. If it is a link with php?id=14 or some such, it fails. hth find the issue. KeithG -- cannot parse valid podcast feeds https://bugs.launchpad.net/bugs/562714 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to rhythmbox in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 542343] Re: gnome-panel will not autostart on lucid
Well, this is affecting me as well on released code?!? I "killall gnome- panel" and it works fine, but from login I get no panels except for one login (mine). The 2 other 'users' get no panels at all. I have set them up with a launcher icon that kills the panels and resets teh panels and all is fine. I updated Lucid last night and spent a lot of time trying to diagnose and got nowhere. Deleting the config files ~/.g*** and allowing them to be rebuilt does not work. I did try to install that mac like launcher which did not work so I uninstalled it. Also nanny would also not run so I uninstalled that as well (I get no configuration panel though it shows an icon in the panel when it launches). Something is amiss. Much rebooting and logging in and out and no joy. Any help appreciated. -- gnome-panel will not autostart on lucid https://bugs.launchpad.net/bugs/542343 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-panel in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
