I would like to report back that on Ubuntu 20.04 with Intel AX200
network card (8087:0029), I resolved this issue by following @Hui Wang's
instruction
ibt-20-1-3.sfi and ibt-20-1-3.ddc from 20.10 driver
HSP/HSF was greyed out before but is now available and functioning after
powering off and on
Public bug reported:
I installed two computers, just with standard process, from within
China. They were normal 64 bit images of 14.04 downloaded from the
Ubuntu website, English version.
Because its from within China, the install tried to somehow customize. I
had Chinese in my list of
** Changed in: nautilus (Ubuntu)
Assignee: (unassigned) = KT Jagtheesh (jagtheesh-kt)
** Changed in: nautilus (Ubuntu)
Status: Invalid = New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
https://bugs.launchpad.net/bugs
There appears to be some details found here:
http://code.google.com/p/gma500/issues/detail?id=10 with potential
solution.
** Bug watch added: code.google.com/p/gma500/issues #10
http://code.google.com/p/gma500/issues/detail?id=10
--
Acer AspireOne 751h: can't lower/increase brightness
I went through thee steps in
https://wiki.ubuntu.com/Hotkeys/Troubleshooting. There's no info found
with keymap, no info from acpi_listen. The problem still persist in
Maverick.
--
Acer AspireOne 751h: can't lower/increase brightness
https://bugs.launchpad.net/bugs/566203
You received this bug
The brightness increase OSD no longer come up when I turn on/off
Bluetooth on Maverick (and previously in Lucid).
--
Acer AspireOne 751h: can't lower/increase brightness
https://bugs.launchpad.net/bugs/566203
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Public bug reported:
I have an Acer AspireOne 751h laptop with an Intel GMA500 Poulsbo video
card. It is running Ubuntu Karmic and has been configured with the psb
driver, so X server is working fine. However, the brightness keys don't
work (Fn+left/right arrow). I am able to lower/increase
Public bug reported:
Binary package hint: kile
After ending kile it takes some time and then
Application: Kile (kile), signal: Segmentation fault
[KCrash Handler]
#5 0x7fae56a07b00 in QStackedWidget::currentWidget() const () from
/usr/lib/libQtGui.so.4
#6 0x006cf2fd in _start ()
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/37389700/Dependencies.txt
** Attachment added: ProcMaps.txt
http://launchpadlibrarian.net/37389701/ProcMaps.txt
** Attachment added: ProcStatus.txt
http://launchpadlibrarian.net/37389702/ProcStatus.txt
--
kile gives
Problem appear to have been solved now.
Thanks a lot!
--
Scanner not accessible: udev/hal
https://bugs.launchpad.net/bugs/211708
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
Output of 'stat /var/cache/hald/fdi-cache':
File: `/var/cache/hald/fdi-cache'
Size: 742548 Blocks: 1464 IO Block: 4096 regular file
Device: 806h/2054d Inode: 46357 Links: 1
Access: (0644/-rw-r--r--) Uid: (0/root) Gid: (0/root)
Access: 2028-02-29
** Attachment added: debugging hal
http://launchpadlibrarian.net/14433287/kern.log
--
Scanner not accessible: udev/hal
https://bugs.launchpad.net/bugs/211708
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
hal.log
** Attachment added: debugging hal
http://launchpadlibrarian.net/14433317/hal.log
--
Scanner not accessible: udev/hal
https://bugs.launchpad.net/bugs/211708
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
lshal.txt
** Attachment added: debugging hal
http://launchpadlibrarian.net/14433349/lshal.txt
--
Scanner not accessible: udev/hal
https://bugs.launchpad.net/bugs/211708
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
debugging hal
** Attachment added: kern.log
http://launchpadlibrarian.net/13530464/kern.log
--
Scanner not accessible: udev/hal
https://bugs.launchpad.net/bugs/211708
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
debugging hal
** Attachment added: hal.log
http://launchpadlibrarian.net/13530478/hal.log
--
Scanner not accessible: udev/hal
https://bugs.launchpad.net/bugs/211708
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
debugging hal
** Attachment added: lshal.txt
http://launchpadlibrarian.net/13530487/lshal.txt
--
Scanner not accessible: udev/hal
https://bugs.launchpad.net/bugs/211708
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
Problem still exists.
Output of `dpkg -l | grep \( libsane \| sane\-utils \| xsane \|
xsane\-common \| udev \| hal \)`
ii hal0.5.11~rc2-1ubuntu6
Hardware Abstraction Layer
ii libsane1.0.19-1ubuntu3
Public bug reported:
Follow on to https://bugs.launchpad.net/ubuntu/+source/sane-
backends/+bug/180794 . The scanner is not accessible by a normal user
but is accessible by root.
Output of 'lsusb':
Bus 003 Device 002: ID 0483:2016 SGS Thomson Microelectronics Fingerprint Reader
Bus 003 Device
A new bug has been filed: https://bugs.launchpad.net/ubuntu/+source
/sane-backends/+bug/211708
--
access to usb device denied in latest hardy package
https://bugs.launchpad.net/bugs/180794
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Output of 'lshal' attached.
** Attachment added: output of lshal
http://launchpadlibrarian.net/13107960/hal.txt
--
Scanner not accessible: udev/hal
https://bugs.launchpad.net/bugs/211708
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
No, not a problem with xsane. If I were to change
/etc/udev/rules.d/40-permissions.rules
to have:
# USB devices (usbfs replacement)
SUBSYSTEM==usb, ENV{DEVTYPE}==usb_device, MODE=0666
SUBSYSTEM==usb_device,MODE=0666
then everything works fine also.
--
access to usb device
Fishor, the user is already in 'scanner' group.
--
access to usb device denied in latest hardy package
https://bugs.launchpad.net/bugs/180794
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Martin, the scanner used to work with earlier versions of Ubuntu. The
scanner works also if I were to run it as root.
--
access to usb device denied in latest hardy package
https://bugs.launchpad.net/bugs/180794
You received this bug notification because you are a member of Ubuntu
Bugs, which is
This bug is still present for me in Hardy beta. I am using
libsane: 1.0.19-1ubuntu3
sane-utils: 1.0.19-1ubuntu3
xsane: 0.995-1ubuntu1
xsane-common: 0.995-1ubuntu1
udev: 117-4ubuntu1
hal: 0.5.11~rc2-1ubuntu5
--
access to usb device denied in latest hardy package
25 matches
Mail list logo
