[Bug 2060077] [NEW] Unable to load the feed
Public bug reported: Unable to load podcast feeds in Rythmbox. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: rhythmbox 3.4.7-2ubuntu2 ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4 Uname: Linux 6.8.0-11-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Apr 2 16:13:03 2024 InstallationDate: Installed on 2022-04-07 (726 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Daily amd64 (20220405) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: rhythmbox UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.init.d.apport: 2024-02-22T08:20:00 ** Affects: rhythmbox (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble third-party-packages -- 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/2060077 Title: Unable to load the feed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/2060077/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2056772] [NEW] Properties locks up
Public bug reported: On SMB mounted file systems, right click properties on audio files causes the Nautilus to freeze. Force/Wait appears. The file system has read/write permission. Happens every time for large .flac files. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: nautilus 1:46~beta-0ubuntu3 ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4 Uname: Linux 6.8.0-11-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Mar 11 10:33:22 2024 GsettingsChanges: b'org.gnome.nautilus.preferences' b'migrated-gtk-settings' b'true' b'org.gnome.nautilus.preferences' b'recursive-search' b"'always'" b'org.gnome.nautilus.preferences' b'show-directory-item-counts' b"'always'" b'org.gnome.nautilus.preferences' b'show-image-thumbnails' b"'always'" b'org.gnome.nautilus.window-state' b'initial-size' b'(1241, 1039)' InstallationDate: Installed on 2022-04-07 (704 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Daily amd64 (20220405) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.init.d.apport: 2024-02-22T08:20:00 usr_lib_nautilus: file-roller 43.1-1 nautilus-extension-gnome-terminal 3.51.90-1ubuntu1 nautilus-share0.7.5-0.3 ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/2056772 Title: Properties locks up To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2056772/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1877746] Re: Lock screen not working
Done, didn't fix it. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1877746 Title: Lock screen not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1877746/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1877746] Re: Lock screen not working
No, but I did do a dconf -f, and that at least lets me do it manually now. It will not lock automatically. Of course, it reset everything, which as introduced others problems. Question, what call is exposed to applications to get to determine DPI? I am having scaling issues in Maple 2017.3 and Maple 2020. If I use Gnome (default) it works fine. I am unable to get Wayland up. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1877746 Title: Lock screen not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1877746/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1877746] Re: Lock screen not working
No crash files for Wayland. May 12 16:21:46 apollo systemd[2574]: Starting GNOME Shell on Wayland... May 12 16:21:46 apollo rtkit-daemon[2201]: Successfully made thread 3777373 of process 3777373 owned by '1000' high priority at nice level -11. May 12 16:21:46 apollo rtkit-daemon[2201]: Supervising 4 threads of 2 processes of 2 users. May 12 16:21:46 apollo rtkit-daemon[2201]: Supervising 4 threads of 2 processes of 2 users. May 12 16:21:46 apollo rtkit-daemon[2201]: Successfully made thread 3777422 of process 3777373 owned by '1000' RT at priority 5. May 12 16:21:46 apollo rtkit-daemon[2201]: Supervising 5 threads of 2 processes of 2 users. May 12 16:21:46 apollo gnome-shell[3777410]: Failed to open gpu '/dev/dri/card0': Failed to activate universal planes: Operation not permitted May 12 16:21:46 apollo gnome-shell[3777410]: Failed to create backend: No GPUs found May 12 16:21:46 apollo systemd[2574]: Started Sound Service. May 12 16:21:46 apollo systemd[2574]: gnome-shell-wayland.service: Failed with result 'protocol'. May 12 16:21:46 apollo systemd[2574]: Failed to start GNOME Shell on Wayland. May 12 16:21:46 apollo systemd[2574]: Dependency failed for GNOME Shell on Wayland. May 12 16:21:46 apollo systemd[2574]: Dependency failed for GNOME Wayland Session. May 12 16:21:46 apollo systemd[2574]: Dependency failed for GNOME Wayland Session (session: ubuntu). May 12 16:21:46 apollo systemd[2574]: gnome-session-wayland@ubuntu.target: Job gnome-session-wayland@ubuntu.target/start failed with result 'dependency'. May 12 16:21:46 apollo systemd[2574]: gnome-session-wayland.target: Job gnome-session-wayland.target/start failed with result 'dependency'. May 12 16:21:46 apollo systemd[2574]: gnome-shell-wayland.target: Job gnome-shell-wayland.target/start failed with result 'dependency'. May 12 16:21:46 apollo systemd[2574]: gnome-shell-wayland.service: Triggering OnFailure= dependencies. May 12 16:21:46 apollo systemd[2574]: unicast-local-avahi.path: Succeeded. May 12 16:21:46 apollo systemd[2574]: Stopped Path trigger for Avahi .local domain notifications. May 12 16:21:46 apollo systemd[2574]: update-notifier-release.path: Succeeded. May 12 16:21:46 apollo systemd[2574]: Stopped Path trigger for new release of Ubuntu notifications. May 12 16:21:46 apollo systemd[2574]: Condition check resulted in Disable GNOME Shell extensions after failure being skipped. May 12 16:21:46 apollo systemd[2574]: Stopped target GNOME Session Manager is ready. May 12 16:21:46 apollo systemd[2574]: Stopping GNOME Session Manager (session: ubuntu)... May 12 16:21:46 apollo systemd[2574]: gnome-session-manager@ubuntu.service: Succeeded. May 12 16:21:46 apollo systemd[2574]: Stopped GNOME Session Manager (session: ubuntu). May 12 16:21:46 apollo systemd[2574]: Stopped target Tasks to be run before GNOME Session starts. May 12 16:21:46 apollo systemd[2574]: Stopped target Session services which should run early before the graphical session is brought up. May 12 16:21:46 apollo systemd[2574]: Reached target Shutdown running GNOME Session. May 12 16:21:46 apollo systemd[2574]: Stopping Start gnome-keyring as SSH agent... May 12 16:21:46 apollo systemd[2574]: Stopping Monitor Session leader for GNOME Session... May 12 16:21:46 apollo systemd[2574]: Starting Restart DBus after GNOME Session shutdown... May 12 16:21:46 apollo systemd[2574]: Stopped target Shutdown running GNOME Session. May 12 16:21:46 apollo systemd[2574]: gnome-keyring-ssh.service: Succeeded. May 12 16:21:46 apollo systemd[2574]: Stopped Start gnome-keyring as SSH agent. May 12 16:21:46 apollo systemd[2574]: Reached target Shutdown running GNOME Session. May 12 16:21:46 apollo systemd[2574]: Stopped target Shutdown running GNOME Session. May 12 16:21:46 apollo systemd[2574]: Started Restart DBus after GNOME Session shutdown. May 12 16:21:46 apollo systemd[2574]: gnome-session-monitor.service: Succeeded. May 12 16:21:46 apollo systemd[2574]: Stopped Monitor Session leader for GNOME Session. May 12 16:21:46 apollo gvfsd[3777335]: A connection to the bus can't be made May 12 16:21:46 apollo systemd[2574]: Stopping D-Bus User Message Bus... May 12 16:21:46 apollo systemd[2574]: gnome-session-restart-dbus.service: Succeeded. May 12 16:21:46 apollo systemd[2574]: run-user-1000-gvfs.mount: Succeeded. May 12 16:21:46 apollo systemd[3776558]: run-user-1000-gvfs.mount: Succeeded. May 12 16:21:46 apollo systemd[2574]: gvfs-daemon.service: Succeeded. May 12 16:21:46 apollo systemd[1]: run-user-1000-gvfs.mount: Succeeded. May 12 16:21:46 apollo systemd[2574]: dbus.service: Succeeded. May 12 16:21:46 apollo systemd[2574]: Stopped D-Bus User Message Bus. May 12 16:21:46 apollo systemd[2574]: Started D-Bus User Message Bus. *-display description: VGA compatible controller product: TU116 [GeForce GTX 1660 Ti] vendor: NVIDIA Corporation physical id: 0 bus info: pci@:09:00.0 version: a1
[Bug 1877746] Re: Lock screen not working
Wayland won't launch. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1877746 Title: Lock screen not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1877746/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1877746] Re: Lock screen not working
org.gnome.desktop.session session-name 'ubuntu' org.gnome.desktop.session idle-delay uint32 900 org.gnome.desktop.lockdown mount-removable-storage-devices-as-read-only false org.gnome.desktop.lockdown disable-command-line false org.gnome.desktop.lockdown disable-log-out false org.gnome.desktop.lockdown disable-printing false org.gnome.desktop.lockdown disable-lock-screen false org.gnome.desktop.lockdown disable-print-setup false org.gnome.desktop.lockdown disable-user-switching false org.gnome.desktop.lockdown disable-application-handlers false org.gnome.desktop.lockdown disable-save-to-disk false org.gnome.desktop.lockdown user-administration-disabled false -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1877746 Title: Lock screen not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1877746/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1877675] Re: Workspaces broken with latest update
It was a gnome config update that came down a couple of days ago. I have two monitors, the left is 1920x1080 rotated left. The monitor on the right is 3440x1440. I use the keyboard bindings ctrl up arrow and down arrow. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1877675 Title: Workspaces broken with latest update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1877675/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1877675] Re: Workspaces broken with latest update
This issue seems to be related to the saving the screen resolution issue. If my left monitor gets switched back to vertical, workspaces come back. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1877675 Title: Workspaces broken with latest update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1877675/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1767505] Re: Rhythmbox Radio - Internal Data Stream Error
I pulled the source code and fixed it myself. I tried to push it back up, but I guess they were not interested. -- 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/1767505 Title: Rhythmbox Radio - Internal Data Stream Error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1767505/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 201786] Re: ssh Agent admitted failure to sign using the key on big endian machines
** Changed in: gnome-keyring (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/201786 Title: ssh Agent admitted failure to sign using the key on big endian machines To manage notifications about this bug go to: https://bugs.launchpad.net/seahorse/+bug/201786/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1767505] [NEW] Rhythmbox Radio - Internal Data Stream Error
Public bug reported: When trying to play any radio station, I get a dialog that states after about 20 seconds of playing: Couldn't start playback Internal data stream error ** Affects: rhythmbox (Ubuntu) Importance: Undecided Status: New -- 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/1767505 Title: Rhythmbox Radio - Internal Data Stream Error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1767505/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1503056] [NEW] Gnome screensaver disregards user settings
Public bug reported: When I lock the screen, the gnome-screensaver-command initiates the screensaver within about 3 seconds. My system preferences indicate to wait one hour before turning off the screen. This is a bug. As a workaround for this blatantly incorrect behavior, I have changed my lock command to the following: gnome-screensaver-command -l && gnome-screensaver-command -d This wakes the screen after a few seconds, so that my login screen stays on. The reason it is problem for the screen to turn off is that it often loses connection and will not wake up again. After locking the screen, sometimes I have to unplug the monitor's DisplayPort cable from the PC and plug it back in again. Otherwise the monitor will not show what the PC is doing, even though the PC is receiving commands and even allows me to (blindly) login. So it is imperative that the screensaver honor the user's system settings. This is a bug. Please fix the implementation. Thanks. ** Affects: gnome-screensaver (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/1503056 Title: Gnome screensaver disregards user settings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1503056/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1451944] Re: Gnome-terminal in Ubuntu Unity shrinks to minimum size
** Description changed: When I open a terminal in Ubuntu 15.04, it shrinks to 1 character by 1 character. I can use the corner resizer to make the window bigger, but it immediately shrinks to 1x1. There are a few x,y combinations that allow the window to stay at the desired size, but if you're off by a pixel, the window shrinks to 1x1. There is another question (http://askubuntu.com/questions/423733/gnome- terminal-in-kubuntu-shrinks-to-minimum-size), Gnome-terminal in Kubuntu shrinks to minimum size, that is basically the same thing, but in KDE. I tried to follow the instructions: - In KDE, go to System Settings. Return to the overview if you are not + In KDE, go to System Settings. Return to the overview if you are not already there. In the Workspace Appearance and Behavior section, click Window Behavior. In the area to the left, click the Window Rules icon. but, there is no Workspace Appearance and Behavior section. I couldn't find a similar setting in ccsm, gnome-tweak-tool or unity-tweak-tool. % dpkg-query --show compiz compiz1:0.9.12.1+15.04.20150410.1-0ubuntu1 % dpkg-query --show unity unity 7.3.2+15.04.20150420-0ubuntu1 ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: gnome-terminal 3.14.2-0ubuntu3 ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3 Uname: Linux 3.19.0-16-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Tue May 5 09:59:55 2015 ExecutablePath: /usr/lib/gnome-terminal/gnome-terminal-server InstallationDate: Installed on 2013-05-02 (732 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) SourcePackage: gnome-terminal UpgradeStatus: Upgraded to vivid on 2015-04-26 (8 days ago) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1451944 Title: Gnome-terminal in Ubuntu Unity shrinks to minimum size To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1451944/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1014473] Re: hdmi video out broken on package upgrade
I was using my laptop to play movies on my tv using hdmi. When I upgraded recently, which included a new kernel, the hdmi causes the computer to freeze, forcing a reboot. As long as I don't plug in the hdmi everything works properly. But the instant I plug in the cable the computer freezes. The wifi continues to function but nothing else. I can't switch to a terminal screen. The only thing I can do is reboot. I have not tried going back to an earlier kernel but will try that soon. -- 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/1014473 Title: hdmi video out broken on package upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1014473/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 836632] [NEW] gedit cannot read driver install package on this machine
Public bug reported: Have successfully installed same printer on a desktop PC with 11.04 installed. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: gedit 2.30.4-2ubuntu1 ProcVersionSignature: Ubuntu 2.6.38-11.48-generic 2.6.38.8 Uname: Linux 2.6.38-11-generic i686 Architecture: i386 Date: Mon Aug 29 08:08:17 2011 ExecutablePath: /usr/bin/gedit InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110427.1) ProcEnviron: LANGUAGE=en_US:en PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gedit UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gedit (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug apport-lpi i386 natty -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/836632 Title: gedit cannot read driver install package on this machine To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/836632/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 836632] Re: gedit cannot read driver install package on this machine
-- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/836632 Title: gedit cannot read driver install package on this machine To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/836632/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 760821] [NEW] Evolution Not sending hotmail E-mails
Public bug reported: Hi Guys, This is a very recent error while trying to use Evolution to send hotmail E-mail. It's worth noting I have been using Evolution to do this with no problems up until today and no settings have changed. When I use send/receive I receive any incoming mail fine but it hangs on the sending mail or an error message STARTTSL command failed :Unkown is given. Server type SMTP Server smtp.live.com Server requires auth checked TLS Encryption Auth type Plain Address myaddr...@hotmail.com I have tried changing TLS TO SSL, Auth type to login with no success. Any help greatly appreciated. ** Affects: evolution (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/760821 Title: Evolution Not sending hotmail E-mails -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 87054] Re: [Needs Packaging] Microdia SN9C201 webcam driver
Followed John Logan's steps Does not work for me Using a MS LC VX-6000 on Jaunty amd64 Starting Cheese causes webcam light to flash (guess its trying to initialize), but no image or video in cheese. Anyone any suggestions as to how to investigate further/fix? Thanks. -- [Needs Packaging] Microdia SN9C201 webcam driver https://bugs.launchpad.net/bugs/87054 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 195180] Re: user-mountable (nfs) filesystems are not showing up in Computer view of nautilus
I agree, I use user mountable nfs shares for my music and video at home, but on my laptop, I don't automount them since there is no use when I'm on the road etc. Double clicking in the Computer portion of nautilus was very useful.. is this just a gvfs regression, or is it gone for good? -- user-mountable (nfs) filesystems are not showing up in Computer view of nautilus https://bugs.launchpad.net/bugs/195180 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 102921] Re: Moving the mouse cursor over the gnome-system-monitor temporarily causes network and disk usage to become zero
I use Edgy Eft, gnome-system-monitor 2.16.1-0ubuntu1. It doesn't affect the performance of my computer, the problem is that the monitor reports 0% network/disk usage under certain conditions: When the mouse cursor enters or exits the system-monitor panel applet window. Moving the cursor between the different areas of the system-monitor (e.g. between Memory and Network). If the cursor is stationary within the window, the graph acts normally. If the cursor is outside the window, the graph acts normally. I have also confirmed the bug on a system running Fiesty Fawn, gnome- system-monitor 2.18.1-0ubuntu1. -- Moving the mouse cursor over the gnome-system-monitor temporarily causes network and disk usage to become zero https://bugs.launchpad.net/bugs/102921 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 102921] Re: Moving the mouse cursor over the gnome-system-monitor temporarily causes network and disk usage to become zero
*** This bug is a duplicate of bug 97190 *** https://bugs.launchpad.net/bugs/97190 No, its not the tooltip which displays the incorrect information, but the graphs on the panel itself. In the attached screenshot, the network graph shows a drop to almost 0% near the middle, even though my network usage was actually remaining relatively constant. This drop in the graph was caused by moving my mouse cursor repeatedly on and off over the system-monitor. ** Attachment added: system-monitor.png http://librarian.launchpad.net/7296553/system-monitor.png -- Moving the mouse cursor over the gnome-system-monitor temporarily causes network and disk usage to become zero https://bugs.launchpad.net/bugs/102921 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 102921] Moving the mouse cursor over the gnome-system-monitor temporarily causes network and disk usage to become zero
Public bug reported: Binary package hint: gnome-system-monitor Repeatedly moving the mouse cursor on and off over the gnome-system- monitor will cause network usage and disk usage to remain at 0%. ** Affects: gnome-system-monitor (Ubuntu) Importance: Undecided Status: Unconfirmed -- Moving the mouse cursor over the gnome-system-monitor temporarily causes network and disk usage to become zero https://bugs.launchpad.net/bugs/102921 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug contact for gnome-system-monitor in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 73023] Re: Round orange emblems have lack usability
I agree, but not wholy.. I like the way icons are unified in a way, with similar shapes, but still distinction between them in a way.. However, I think it also has something to do with the placement of the emblems, the way you perceive the image as a whole.. As i see it, when you look at it, you see a folder first, then some undistinguishible 'emblems' sort of floating above them, and then the text line beneath the folder icon.. Then you have to look a second time to see what each folder is, in both cases, either with the orange ones as with the tangerine-emblems.. Wouldn't it be a far better idea to make folder icons with emblems on them instead of floating emblems (see bug attachment (screen taken on a mac, hey, i'm a graphic designer!? ^_^ ), so that you minimize the space used, thus maximizing what you perceive.. ** Attachment added: Example emblemfolders http://librarian.launchpad.net/5203251/Picture%201.png -- Round orange emblems have lack usability https://launchpad.net/bugs/73023 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 73023] Re: Round orange emblems have lack usability
Something I just noticed from looking at the orange emblems again, is that the the lighting on them, makes them become a bit harder to look at.. the example I posted before has a very faint gradual tint in the round forms, but the glare on the orange emblems is really fat, which makes it blend in with the white icons.. I agree with your concern on the shape and color of the emblems, but design-wise, I agree with the way they have made them.. It is part of the unified look troughout the whole theme.. However, it still lacks some useability I agree.. The tangerine theme is good in showing the icons in shape, but not in color, or in outline.. They are all not the same.. Maybe it's a good idea to get behind the 'drawing table' and keep this thread going with some ideas and propositions? -- Round orange emblems have lack usability https://launchpad.net/bugs/73023 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 39069] Re: [Bug 39069] Re: Adding Printer Fails with no Dialog
After an update this morning, I'm able to add a printer. I know the bug descriptor wasn't the best, but unless you digg pretty deeply into cups, I'm not aware of any other way to add a printer (the web interface has always been locked down in ubuntu), so the fact that gnome-cups-add was failing should be read as Average-Joe can't add a printer, and gets no error messege! Either way I guess this bug can be closed... -- Adding Printer Fails with no Dialog https://launchpad.net/malone/bugs/39069 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 39069] Re: Adding Printer Fails with no Dialog
I've tried adding Allow from statement in my cupsd.conf for my ip address and localhost with no luck. here's the error log entries, as I launch and run gnome-cups-add: E [11/Apr/2006:11:50:47 -0700] [cups-driverd] Unable to open driver directory /usr/lib/cups/driver: No such file or directory E [11/Apr/2006:11:51:11 -0700] CUPS-Add-Printer: Unauthorized E [11/Apr/2006:11:51:11 -0700] copy_model: empty PPD file! E [11/Apr/2006:11:51:11 -0700] PID 9183 stopped with status 1! E [11/Apr/2006:11:51:11 -0700] [cups-driverd] Unable to open /usr/share/ppd/ - No such file or directory -- Adding Printer Fails with no Dialog https://launchpad.net/malone/bugs/39069 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 39069] Adding Printer Fails with no Dialog
Public bug reported: Affects: gnome-cups-manager (Ubuntu) Severity: Normal Priority: (none set) Status: Unconfirmed Description: Trying to add an HP Color Laserjet 4650 connected over the network with a jetdirect card. Running gnome-cups-add from the command line Am able to select Network/Jetdirect, and enter ip address. Then select the Driver, and hit apply, and gnome-cups-add quits without adding the printer. I get the following error on the command line: ** (gnome-cups-add:6283): WARNING **: IPP request failed with status 1280 Selected ppd file = foomatic-rip/HP/HP-Color_LaserJet_4610-Postscript.ppd Selected ppd file = foomatic-rip/HP/HP-Color_LaserJet_4650-Postscript.ppd ** (gnome-cups-add:6283): WARNING **: IPP request failed with status 1280 -- Adding Printer Fails with no Dialog https://launchpad.net/malone/bugs/39069 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
