[Bug 948613] Re: [FFE] Enable the Source and Gateway audio profiles in bluez by default
Was this regression tested? That patch made it's way into Debian where it broke A2DP headphones: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=%23724735 I haven't tested the Ubuntu package so I can't really comment on whether it broke Ubuntu as well, or if Ubuntu has some other piece we are missing in Debian that makes it work. > I don't think testing this should be a prerequisite ... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/948613 Title: [FFE] Enable the Source and Gateway audio profiles in bluez by default To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/948613/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 228624] Re: DVD writer not working since hardy upgrade
Perham: Sounds like you are suffering from a different bug to the rest of us (though yes, both would likely be kernel issues, hence why this bug is for 'Linux'). You might want to search and see if you can find a closer match or open a new bug. -- DVD writer not working since hardy upgrade https://bugs.launchpad.net/bugs/228624 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 228624] Re: DVD writer not working since hardy upgrade
bassani: As Jan has already pointed out, it should be: # defoptions=quiet splash locale=pt_BR all_generic_ide=1 you should also run sudo update-grub after making that change which will propagate that change to all normal boot stanzas. -- DVD writer not working since hardy upgrade https://bugs.launchpad.net/bugs/228624 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 238143] Re: bug status "triaged" is ambiguous
Ok, I've had a thought that this probably means that a priority has been assigned to the bug (fair enough, makes sense), and maybe I was a little too drunk (never good) when submitting the original bug to realise it then. I'm still very much against using such a rare word though - see for example bug #204534 where one of the comments is "Will this ever get fixed or is it just triaged (do it yourself)?" --- "do it yourself"?? Sounds like I'm not the only one not clear on the meaning. I propose replacing this term with "prioritised" or "priority assigned" - something that clearly defines itself rather than [potentially] wasting an hour per person before realising the meaning. -- bug status "triaged" is ambiguous https://bugs.launchpad.net/bugs/238143 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 238143] [NEW] bug status "triaged" is ambiguous
Public bug reported: This bug refers to launchpad itself - but I can't select that as a package. I've been trying to figure out the meaning of the bug status "triaged" for the last 20 minutes and it occurs to me that if I'm having this difficulty understanding it's meaning, I'm almost certainly not alone. What the hell does it mean when a bug is marked as "triaged"? I seem to be seeing "triage" defined as the process of sorting patients... right... into what exactly? Does it mean "low priority" or simply "I've determined what priority this patient is"? Seems to me that it could mean high priority equally as much as low priority. https://wiki.ubuntu.com/Bugs/HowToTriage doesn't help - it seems to take "triage" to mean "to sort" and doesn't mention "triaged" at all, except for "untriaged bugs", which I assume means unsorted bugs - so WHAT is a "triaged" bug? Maybe I'm missing some critical English definitions that everyone else knows and takes for granted --- but I doubt it. I'm in favour for picking a less ambigous term for describing ... whatever this term actually means. ** Affects: ubuntu Importance: Undecided Status: New -- bug status "triaged" is ambiguous https://bugs.launchpad.net/bugs/238143 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 204534] Re: kded (KDE daemon) crashes when i use calculator hotkey (Hardy)
+1 from me -- kded (KDE daemon) crashes when i use calculator hotkey (Hardy) https://bugs.launchpad.net/bugs/204534 You received this bug notification because you are a member of Kubuntu Team, which is subscribed to kdebase in ubuntu. -- kubuntu-bugs mailing list [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 238052] [NEW] mythtv not queuing auto transcode job
Public bug reported: Binary package hint: mythtv I have MythTV set to automatically transcode new recordings (using autodetect profile, which works fine when I manually queue it), but for some reason it is not queuing the job automatically. I have confirmed that this setting is being applied to each recording schedule, and the auto commercial flag job (which is set to start when the recording starts as opposed to when it finishes) is queued and works fine, just not the auto-transcode job. Fresh Hardy Herron install. MythTV (fronend, backend, etc) 0.21.0+fixes16838-0ubuntu3 ** Affects: mythtv (Ubuntu) Importance: Undecided Status: New -- mythtv not queuing auto transcode job https://bugs.launchpad.net/bugs/238052 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 190537] Re: [Gutsy] Display sleep sets wrong DPMS off time
I have experienced this behavior on two systems running Hardy, but am unsure of the trigger at present. It might have something to do with the display being suspended (possibly though other means - on one of the systems I have win+F9 rigged to run 'xset dpms force suspend' and noticed the screen turned off faster after executing that one time, but haven't noticed it other times, so I'm not sure). -- [Gutsy] Display sleep sets wrong DPMS off time https://bugs.launchpad.net/bugs/190537 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 236715] [NEW] nullmailer spams relay host if misconfigured
Public bug reported: Binary package hint: nullmailer I just got a call from our IT security officer on campus telling me my system was hammering the relay host and checking my logs it seems it was trying to connect ~20 times every second, but the relay was rejecting it because my hostname was misconfigured. This is very bad behaviour for any mailer program, expected behaviour would be for it to wait a minimum of 15 minutes before trying again. This is on Hardy Herron with nullmailer version 1:1.03-5. My fix, as with all mailer problems was to immediately swap to postfix so this bug no longer affects me, but is most definitely still present. ** Affects: nullmailer (Ubuntu) Importance: Undecided Status: New -- nullmailer spams relay host if misconfigured https://bugs.launchpad.net/bugs/236715 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 228624] Re: DVD writer not working since hardy upgrade
+1 from me.
At first I figured I wasn't able to play DVDs because maybe libdvdcss wasn't
installed or something and didn't think anything of it, but I've now checked
over everything and can confirm that it is the same problem described above.
Problem manifested after installing Hardy (I did a clean install courtesy of a
hard drive crash - possibly relevant is the fact that I was unable to install
using this drive due to IO errors while booting the live CD, likely from this
same issue - this may be reason to release an updated install disc once fixed.
I also have an external USB LG DVD burner which is working perfectly and I was
able to use to install from).
Strangely I am able to read the start of the CD/DVD - enough for the
system to recognise the media & filesystem and even mount, but not
enough to do anything useful with it. I checked and the last byte that
can be read is at location 0xAFFF on one CD, 0x7FFF on another DVD,
0x4 on the same DVD after ejecting & reinserting, etc, etc, etc.
There is data accessible further on each disc, but is very patchy as to
the exact locations.
sudo hdparm -i /dev/scd0
/dev/scd0:
Model=PIONEER DVD-RW DVR-111D, FwRev=1.23, SerialNo=
Config={ Fixed Removeable DTR<=5Mbs DTR>10Mbs nonMagnetic }
RawCHS=0/0/0, TrkSize=0, SectSize=0, ECCbytes=0
BuffType=13395, BuffSize=64kB, MaxMultSect=0
(maybe): CurCHS=0/0/0, CurSects=0, LBA=yes, LBAsects=0
IORDY=on/off, tPIO={min:240,w/IORDY:120}, tDMA={min:120,rec:120}
PIO modes: pio0 pio1 pio2 pio3 pio4
DMA modes: mdma0 mdma1 mdma2
UDMA modes: udma0 udma1 udma2 udma3 *udma4
AdvancedPM=no
Drive conforms to: Unspecified: ATA/ATAPI-2,3,4,5
* signifies the current active mode
Inserting a CD produces this in dmesg (doing anything with drive, CD or DVD
produces the first four lines with varying sectors):
[313609.816081] sr 6:0:0:0: [sr0] Result: hostbyte=DID_OK
driverbyte=DRIVER_SENSE,SUGGEST_OK
[313609.816089] sr 6:0:0:0: [sr0] Sense Key : Hardware Error [current]
[313609.816092] sr 6:0:0:0: [sr0] Add. Sense: Logical unit communication CRC
error (Ultra-DMA/32)
[313609.816097] end_request: I/O error, dev sr0, sector 104
[313609.816101] Buffer I/O error on device sr0, logical block 26
[313609.816106] Buffer I/O error on device sr0, logical block 27
[313609.816109] Buffer I/O error on device sr0, logical block 28
[313609.816112] Buffer I/O error on device sr0, logical block 29
[313609.816114] Buffer I/O error on device sr0, logical block 30
[313609.816116] Buffer I/O error on device sr0, logical block 31
[313609.816119] Buffer I/O error on device sr0, logical block 32
[313609.816121] Buffer I/O error on device sr0, logical block 33
[313609.816123] Buffer I/O error on device sr0, logical block 34
[313609.816126] Buffer I/O error on device sr0, logical block 35
[313609.916962] sr 6:0:0:0: [sr0] Result: hostbyte=DID_OK
driverbyte=DRIVER_SENSE,SUGGEST_OK
[313609.916969] sr 6:0:0:0: [sr0] Sense Key : Hardware Error [current]
[313609.916972] sr 6:0:0:0: [sr0] Add. Sense: Logical unit communication CRC
error (Ultra-DMA/32)
[313609.916977] end_request: I/O error, dev sr0, sector 236
[313610.233764] UDF-fs: No VRS found
[313610.267136] ISO 9660 Extensions: Microsoft Joliet Level 1
[313610.271363] ISOFS: changing to secondary root
[313611.663228] sr 6:0:0:0: [sr0] Result: hostbyte=DID_OK
driverbyte=DRIVER_SENSE,SUGGEST_OK
[313611.663235] sr 6:0:0:0: [sr0] Sense Key : Hardware Error [current]
[313611.663239] sr 6:0:0:0: [sr0] Add. Sense: Logical unit communication CRC
error (Ultra-DMA/32)
[313611.663243] end_request: I/O error, dev sr0, sector 392
[313611.669510] sr 6:0:0:0: [sr0] Result: hostbyte=DID_OK
driverbyte=DRIVER_SENSE,SUGGEST_OK
[313611.669514] sr 6:0:0:0: [sr0] Sense Key : Hardware Error [current]
[313611.669517] sr 6:0:0:0: [sr0] Add. Sense: Logical unit communication CRC
error (Ultra-DMA/32)
[313611.669520] end_request: I/O error, dev sr0, sector 392
[313611.788044] sr 6:0:0:0: [sr0] Result: hostbyte=DID_OK
driverbyte=DRIVER_SENSE,SUGGEST_OK
[313611.788052] sr 6:0:0:0: [sr0] Sense Key : Hardware Error [current]
[313611.788055] sr 6:0:0:0: [sr0] Add. Sense: Logical unit communication CRC
error (Ultra-DMA/32)
[313611.788060] end_request: I/O error, dev sr0, sector 380
[313611.797055] sr 6:0:0:0: [sr0] Result: hostbyte=DID_OK
driverbyte=DRIVER_SENSE,SUGGEST_OK
[313611.797062] sr 6:0:0:0: [sr0] Sense Key : Hardware Error [current]
[313611.797066] sr 6:0:0:0: [sr0] Add. Sense: Logical unit communication CRC
error (Ultra-DMA/32)
[313611.797071] end_request: I/O error, dev sr0, sector 380
[313611.803874] sr 6:0:0:0: [sr0] Result: hostbyte=DID_OK
driverbyte=DRIVER_SENSE,SUGGEST_OK
[313611.803881] sr 6:0:0:0: [sr0] Sense Key : Hardware Error [current]
[313611.803885] sr 6:0:0:0: [sr0] Add. Sense: Logical unit communication CRC
error (Ultra-DMA/32)
[313611.803889] end_request: I/O error, dev sr0, sector 384
[313611.969150] sr 6:0:0:0: [sr0] Result: hostbyte=DID_OK
driverbyte=DRIVER_SE
[Bug 140839] Re: Cannot increase display brightness with hotkeys
Can the people experiencing this bug see if the cause is the same as bug #140782 (which is the behaviour those of us using KDE are experiencing) by adding: blacklist video to the end of /etc/modprobe.d/blacklist and reboot. Check the behaviour of the brightness keys before gnome-power-manager starts, after it has started and from outside of X entirely. If the keys work, it would seem to indicate the same cause. -- Cannot increase display brightness with hotkeys https://bugs.launchpad.net/bugs/140839 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 87358] Re: Feisty - KDbus simply freezes
Confirming annoying UI experience in this app on feisty & gutsy. Even once the UI does start to respond it does lock up now and again after that (I'm not entirely sure what I'm doing to cause it to lock up - seems to only happen when the app doesn't have focus). -- Feisty - KDbus simply freezes https://bugs.launchpad.net/bugs/87358 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 140782] Re: Inspiron 1420 LCD brightness keys broken
My thinking is that on these models we should just let the BIOS handle this, since it handles it very well, and doing it through userspace means: * We need to handle it in every environment - KDE, Gnome, pure console, X with no window manager, etc. * We need to make sure it's always responsive and users do not perceive any delay * We're essentially going to end up telling the BIOS to do exactly what it wanted to do in the first place since these models handle it through libsmbios (I believe the controls in ACPI use libsmbios anyway based on what I read in a pre-feisty bug report). The only reason I can think of for not trusting it to the BIOS is if we need to override it for some reason (software driven brightness profiles? BIOS already keeps them for battery vs. AC, and it should still be possible to do more sophisticated stuff without disabling this feature since we can still get&set the brightness at any time). Just my 2c. Maybe there is a very good reason for not trusting the BIOS that I'm not seeing (Aside from "because we can"). -- Inspiron 1420 LCD brightness keys broken https://bugs.launchpad.net/bugs/140782 You received this bug notification because you are a member of Kubuntu Team, which is a bug contact for kdebase in ubuntu. -- kubuntu-bugs mailing list [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 140782] Re: Inspiron 1420 LCD brightness keys broken
Ahh that should have been: $ sudo echo blacklist video >> /etc/modprobe.d/blacklist $ sudo reboot -- Inspiron 1420 LCD brightness keys broken https://bugs.launchpad.net/bugs/140782 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 140782] Re: Inspiron 1420 LCD brightness keys broken
And so my _workaround_ is as follows: # echo blacklist video >> /etc/modprobe.d/ # reboot -- Inspiron 1420 LCD brightness keys broken https://bugs.launchpad.net/bugs/140782 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 140782] Re: Inspiron 1420 LCD brightness keys broken
And specifically occurs the moment that /lib/modules/2.6.22-11-generic/kernel/drivers/acpi/video.ko is loaded -- Inspiron 1420 LCD brightness keys broken https://bugs.launchpad.net/bugs/140782 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 140782] Re: Inspiron 1420 LCD brightness keys broken
While I booted up I continually hit Fn+Up/Down until the point when they stopped working. Noting the messages on screen at the time I then booted into recovery mode and manually started S10acpid and bingo the keys stopped working. -- Inspiron 1420 LCD brightness keys broken https://bugs.launchpad.net/bugs/140782 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 78017] Re: firehol no longer starts on Feisty
I don't think upstream cares so much yet because last time I checked the bug doesn't exist there (this behaviour is dependant on the combination of older versions of firehol and recent versions of certain core packages, which debian (at least etch) hasn't updated to yet but ubuntu has) The way I've fixed it on my affected systems (1 feisty, 1 gutsy) is simple, but we need a fix in the package: download latest firehol run (as root) get-iana.sh and answer yes to saving the list to /etc/firehol/RESERVED_IPS(If you're behind a proxy like me you need to first edit the script and remove '--no-proxy' so it will respect the http_proxy environment variable (One of those "What were they thinking?" moments)) copy firehol.sh to /sbin/firehol /etc/init.d/firehol restart This however ignores /etc/default/firehol, though patching the firehol script to support this in true debian style shouldn't be too hard. -- firehol no longer starts on Feisty https://bugs.launchpad.net/bugs/78017 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 140839] Re: Cannot increase display brightness with hotkeys
Maybe a duplicate/related to bug #140782 -- Cannot increase display brightness with hotkeys https://bugs.launchpad.net/bugs/140839 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 140782] Re: Inspiron 1420 LCD brightness keys broken
Getting and setting the brightness through D-Bus also works fine -- Inspiron 1420 LCD brightness keys broken https://bugs.launchpad.net/bugs/140782 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 140782] Re: Inspiron 1420 LCD brightness keys broken
** Attachment added: "lshal output" http://launchpadlibrarian.net/9462504/lshal -- Inspiron 1420 LCD brightness keys broken https://bugs.launchpad.net/bugs/140782 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 140782] Re: Inspiron 1420 LCD brightness keys broken
Confirming this behaviour on my Dell XPS M1710 running Kubuntu Gutsy - Fn+Up/Down work while booting (I assume they are still BIOS controlled at this point) until X and/or KDM starts. Possible duplicate/related to #140839 although symptoms are not quite identical (neither key works for me, while that bug reports that Fn+Down still works, though this may be due to differences with how KDE and Gnome handle this). I can still alter the brightness through /proc/acpi/video/VID/LCD and dellLcdBrightness from libsmbios, and it was working fine before I upgraded earlier today. -- Inspiron 1420 LCD brightness keys broken https://bugs.launchpad.net/bugs/140782 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
