I can confirm this bug in a fresh install of Karmic. It usually starts
happening after I've been using Nautilus for a few hours. I had the same
problem in Jaunty, so perhaps it's hardware related? Anyway, I'll have a
poke around and see if I can consistently reproduce it.
--
nautilus double
** Changed in: rednotebook
Status: New = Fix Released
** Changed in: rednotebook (Ubuntu)
Status: New = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/720973
Title:
*** This bug is a security vulnerability ***
Public security bug reported:
Binary package hint: firefox
When I re-check for the Submit Crash Report tick box, it only shows
un-ticked.
** Affects: firefox (Ubuntu)
Importance: Undecided
Status: New
** Visibility changed to: Public
**Update 3-14-11 3:09AM PST** Apparently this option must ticked only
in Standard Browsing mode first, NOT in Private Browsing mode. Once
ticked on in Standard Browsing mode, it shall stay ticked on when
switching to Private mode. Just my thoughts; It should be working in
either mode, for turning
**2nd Update 3-14-11 9:50PM PST** This bug is still there. When I close
FF, then restart FF the bug still does show up. Thanks. :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/734744
Title:
LL
Public bug reported:
Binary package hint: software-center
I press the icon to start/open the Ubuntu Software Center and wait, then
nothing happens. No bug report window opens either.
Natty Narwhal 11.04 Alpha 3+ i386 (on 64bit AMD)
** Affects: software-center (Ubuntu)
Importance:
*** This bug is a duplicate of bug 631215 ***
https://bugs.launchpad.net/bugs/631215
** Visibility changed to: Public
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/732459
Title:
** Changed in: gdm (Ubuntu)
Status: Invalid = Incomplete
** Changed in: gdm (Ubuntu)
Status: Incomplete = In Progress
** Changed in: gdm (Ubuntu)
Status: In Progress = Opinion
** Changed in: gdm (Ubuntu)
Status: Opinion = In Progress
--
No sound on Login screen
OK, about 10-12 days ago I started testing/trying out 10.10 Maverick
Meerkat Alpha2. The login screen with the no sound bug has returned
and remains without sound as of the date of this comment.
** Changed in: gdm (Ubuntu)
Status: In Progress = Incomplete
--
No sound on Login screen
Hello.
Thank you, for your response and inquiry.[?] OK, as of the official release
of Lucid, the sound is working normally with the login screen (GDM). The
Bug No.475144 can now be (as of Lucid), marked as fixed. I thank you kindly.
Have a great week.[?]
Kindest regards.
On Fri, Jul 2, 2010 at
apport information
** Tags added: apport-collected
** Description changed:
1) Ubuntu 9.10 Karmic Koala
2)
3)Ubuntu question sound (drum) at Login screen Ubuntu Desktop start up
sound/music to be smooth.
4)Login screen-no sound Ubuntu Desktop start up-choppy sound
FYI-1) Thus far
apport information
** Attachment added: AplayDevices.txt
http://launchpadlibrarian.net/43049037/AplayDevices.txt
--
No sound at Login screen choppy sound at desktop start up
https://bugs.launchpad.net/bugs/475171
You received this bug notification because you are a member of Ubuntu
Bugs,
apport information
** Attachment added: ArecordDevices.txt
http://launchpadlibrarian.net/43049038/ArecordDevices.txt
--
No sound at Login screen choppy sound at desktop start up
https://bugs.launchpad.net/bugs/475171
You received this bug notification because you are a member of Ubuntu
apport information
** Attachment added: BootDmesg.txt
http://launchpadlibrarian.net/43049040/BootDmesg.txt
--
No sound at Login screen choppy sound at desktop start up
https://bugs.launchpad.net/bugs/475171
You received this bug notification because you are a member of Ubuntu
Bugs, which is
apport information
** Attachment added: Card0.Amixer.values.txt
http://launchpadlibrarian.net/43049041/Card0.Amixer.values.txt
--
No sound at Login screen choppy sound at desktop start up
https://bugs.launchpad.net/bugs/475171
You received this bug notification because you are a member of
apport information
** Attachment added: Card0.Codecs.codec97.0.ac97.0.0.txt
http://launchpadlibrarian.net/43049042/Card0.Codecs.codec97.0.ac97.0.0.txt
--
No sound at Login screen choppy sound at desktop start up
https://bugs.launchpad.net/bugs/475171
You received this bug notification
apport information
** Attachment added: Card0.Codecs.codec97.0.ac97.0.0.regs.txt
http://launchpadlibrarian.net/43049043/Card0.Codecs.codec97.0.ac97.0.0.regs.txt
--
No sound at Login screen choppy sound at desktop start up
https://bugs.launchpad.net/bugs/475171
You received this bug
apport information
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/43049044/Dependencies.txt
--
No sound at Login screen choppy sound at desktop start up
https://bugs.launchpad.net/bugs/475171
You received this bug notification because you are a member of Ubuntu
Bugs,
apport information
** Attachment added: PciMultimedia.txt
http://launchpadlibrarian.net/43049046/PciMultimedia.txt
--
No sound at Login screen choppy sound at desktop start up
https://bugs.launchpad.net/bugs/475171
You received this bug notification because you are a member of Ubuntu
Bugs,
apport information
** Attachment added: ProcCpuinfo.txt
http://launchpadlibrarian.net/43049048/ProcCpuinfo.txt
--
No sound at Login screen choppy sound at desktop start up
https://bugs.launchpad.net/bugs/475171
You received this bug notification because you are a member of Ubuntu
Bugs,
Hi Brad,
Thanks for your response and help. Karmic Koala 9.10, still lacks sound at
the login screen and the desktop startup sound is still choppy.
I am currently using Lucid Lynx 10.04, since Alpha 3 sound in the buggy
area is much improved. There was an update that did revert back to the
** Branch unlinked: lp:inkscape
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/170225
Title:
relative image paths instead of absolute
To manage notifications about this bug go to:
Same issue on Lenovo ThinkPat P76. Brightness control was working
before.
$ uname -r
5.4.0-59-generic
$ lspci |grep -i vga
01:00.0 VGA compatible controller: NVIDIA Corporation TU104GLM [Quadro RTX 5000
Mobile / Max-Q] (rev a1)
$ sudo lshw -c video
*-display
The 460 driver package was installed with the latest updates and I've
rebooted.
For me, at least, it's working perfectly again.
And I made a mistake on my machine type: it's a ThinkPad P73.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Not me. I'm using Ubuntu 20.04. Until it's made available by the
software update mechanisms I won't touch it.
But "brightness regressions"? We're talking about basic control. How
does passing regression tests helps this issue? Or did people ignore
regression tests before releasing the 450 series?
The 460 driver is broken again. No brightness control.
01 May 2021: nvidia-driver-460 (proprietary, tested).
A reboot fixed everything. Reporting this here as it's not a bug with
the driver.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
26 matches
Mail list logo
