After interacting with the issue further, it seems that the display
'wake-up' is delayed to ~10 seconds after a key is pressed (keyboard or
mouse) as opposed to within a few seconds of that key press.
The bug description and name should probably be updated to reflect this.
--
You received this b
I was unable to test another graphics card in the pcie slot, but the
intel graphics from the cpu do not reproduce this issue.
I've also tested with another monitor with similar specs and the issue
doesn't occur on that one, so I think it's isolated to only one monitor
I have (the affected monitor
Public bug reported:
After locking screen, the keyboard is not able to "wake up" the display
even after entering password and logging in (Able to log in
successfully, but display is still in standby mode). A mouse click has
to be performed to get the display to turn on.
Both keyboard and mouse ar
Looks like this is more of a firmware issue with these docks and/or a
driver issue with the 8152, so I'm throwing this back onto the queue
where it was.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/16
Public bug reported:
I am running Ubuntu 18.04:
lsb_release -rd
Description:Ubuntu 18.04.4 LTS
Release:18.04
Ever since HWE Kernel 5.3 images were introduced, ZFS module is shipped
in version 0.8.1 .
modinfo /lib/modules/5.3.0-28-generic/kernel/zfs/zfs.ko |head
filename: /lib/m
Looks like this is more of a firmware issue with these docks and/or a
driver issue with the 8152, so I'm throwing this back onto the queue
where it was.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/17
** Package changed: ubuntu => linux-lts-xenial (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1750165
Title:
e1000e :00:1f.6 eno1: Detected Hardware Unit Hang (Intel I219-LM )
To manage
Public bug reported:
I am running Ubuntu 16.04 on a Supermicro X11SAE mainboard.
The machines was put into service several months ago. Ever since that time, the
NIC eno1 is causing problems from time to time. When the machine boots up
everything seems to be fine for a while. For no particular re
I confirm that Workaround proposed by eros2 worked on my laptop Lenovo
Flex 14 with Xubuntu 17.10
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1720219
Title:
Repeated keys stop after a few characte
this only happen when one installed wireshark(and wireshark-qt) without
installing wireshark-gtk, but wireshark-gtk is an optional dependency
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1722979
Titl
Public bug reported:
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu Artful Aardvark (development branch)
Release:17.10
Codename: artful
$ apt show wireshark
Package: wireshark
Version: 2.4.0-1
Priority: optional
Section: universe/net
Or
It was only showing this core dump when installing package with apt before. but
after upgrade to latest packages today (apt update && apt full-upgrade), I
can't login to GDM (black screen).
The workaround is remove the package sogoupinyin, which provide this file
/usr/share/glib-2.0/schemas/50_s
jarod@ubuntu-pc:~$ ll /etc/resolv.conf
-rw-r--r-- 1 root root 78 Aug 28 09:38 /etc/resolv.conf
jarod@ubuntu-pc:~$ cat /etc/resolv.conf
# Generated by NetworkManager
nameserver 114.114.114.114 # this entry is manually add by me
nameserver 127.0.1.1
jarod@ubuntu-pc:~$ systemctl status systemd
update to systemd (234-2ubuntu9) doesn't help, after reboot I still need
manually add nameserver to /etc/resolve.conf
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1712283
Title:
Cannot resolve DNS
same error.
$ ls /boot/
abi-4.10.0-22-generic initrd.img-4.10.0-22-generic
initrd.img-4.4.0-14-generic initrd.img-4.4.0-8-generic
memtest86+_multiboot.bin
config-4.10.0-22-generic initrd.img-4.4.0-10-generic
initrd.img-4.4.0-15-generic initrd.img-4.4.0-9-generic
System.map-4.10.0-2
MySQL started to throw apparmor errors after enabling slow-query-logs.
I haven't used this log option for quite some time. So it probably sat for a
few years (and several migrations) uncommented in my my.cnf.
It turned out that the variable name had changes. The entry used to be
"log_slow_queries
Last night I ran into the same problem. I upgraded from 12.04 LTS to 16.04.1
LTS Server and got stuck at boot.
The last message complained about a UUID not being present. It turned out it
was the /usr FS. Doing an "lvm lvscan" from the initrd prompt showed all but
one LVs inactive. The only one
I dug a little deeper and found that only 2 of my 4 NFS Shares were mentioned
in the mountall.log.
The /var/log/upstart/statd-mounting*.log for the 2 other filesystems also
contained "Terminated" as their only line.
The machine booted 4 times today with no error in the logs so far. So
the error
Both files show exactly one entry:
cat /var/log/upstart/statd-mounting-_video0.log
/var/log/upstart/statd-mounting-_mp3.log
Terminated
Terminated
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1157171
I forgot...
Ubuntu 13.10 64bit server is running on my machine.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1157171
Title:
NFS mounts in /etc/fstab fail
To manage notifications about this bug go
The problem of NFS shares not being mounted does still exist.
/var/log/upstart/mountall.log showed the following today:
mount.nfs: rpc.statd is not running but is required for remote locking.
mount.nfs: Either use '-o nolock' to keep locks local, or start statd.
mount.nfs: an incorrect mount optio
Public bug reported:
[INFO] /build/buildd/fcitx-4.2.0/src/core/errorhandler.c:58-FCITX -- Get Signal
No.: 28
Obtained 6 stack frames.
fcitx() [0x4010aa]
/lib/x86_64-linux-gnu/libc.so.6(+0x364c0) [0x7fc03691d4c0]
/lib/x86_64-linux-gnu/libpthread.so.0(sem_wait+0x2e) [0x7fc036cb1fce]
fcitx() [0x400f
I'm about 99% certain this will be fixed by this patch:
http://patchwork.linuxtv.org/patch/9685/
The suspend/resume cycles resubmit the missing rx_urb right now, which
un-wedges the driver. This patch will be in 3.3 sooner or later, and was
cc'd to stable, so it should also wind up in 3.2.x event
No clue. I don't use *buntu at all, let alone follow its development
releases. The bug I had in mind was fixed in kernel 3.0 though.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/778296
Title:
lirc
If I'm thinking clearly, the 0.8.7-0ubuntu4.1 package has the requisite
ioctl patches to work just fine with the in-kernel lirc drivers. And
lirc_i2c is dead, its functionality is entirely replaced by the in-
kernel ir-kbd-i2c driver. And lirc-modules-source should not be used.
Ever. Its been remov
That hardware is fully supported by the upstream (as of 2.6.39) ite-cir
driver.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/819832
Title:
IR device misconfigured or not configured at all in Ubuntu
wrt comment #13, there's a bug in the mceusb driver that affects some IR
signals, which was fixed in kernel 3.0 with the stable tree cc'd. I
believe it should end up in 2.6.39 stable, dunno if 2.6.38 stable is
actually being maintained anymore, so no clue if ubuntu will ever get
the fix before its
In reply to comment #6, you're doing it wrong. On multiple levels. You
are trying to use devinput, but the mceusb driver hasn't been configured
to use the hauppauge rc5 keymap. Then you're trying to use a raw IR
config with that. Won't work. You need to use /dev/lirc0 for a raw IR
config. For devin
The lirc drivers are provided by the kernel now, lirc-modules-source
should be thrown off a cliff.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/810459
Title:
package lirc-modules-source 0.8.7-0ubun
I encounter the same issue after upgrade from 11.04.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/807291
Title:
Mouse and keyboard unresponsive until re-plugged in
To manage notifications about th
Something is wonky in Ubuntu. lircd tries to get exclusive access to the
input device, which prevents any of its events from being delivered to
X. It works perfectly fine in other distros -- I have an ATI
RemoteWonder II myself, works perfectly fine in Fedora. Not sure what's
going on. One guess wo
The spew is from the imon kernel driver, and can probably be rate-
limited. I'll add an entry to my TODO list.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/603468
Title:
Lirc too verbose when crash
Okay, if its multiple machines, I put the blame squarely on the ftdi_sio
and dib0700 drivers for apparently not implementing any suspend/resume
support. I've actually dug out my usb-uirt hardware, which has some usb-
serial ftdi driver as well, iirc., and will see if I can reproduce the
issue and t
Choice excerpts from dmesg:
[0.00] Atom PSE erratum detected, BIOS microcode update
recommended
[0.00] ACPI: BIOS bug: multiple APIC/MADT found, using 0
[0.00] ACPI: If "acpi_apic_instance=2" works better, notify
linux-a...@vger.kernel.org
[0.180781] [Firmware Bug]:
Still sounds like a kernel-level issue underneath. Can you provide dmesg
output from after a fresh boot, suspend and resume?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/359356
Title:
USB device at
99% certain this is not an lirc bug, it is a kernel bug. Devices
disconnecting and reconnecting on suspend/resume is indicative of buggy
support for the usb chipset on the system(s) in question. The isn't
anything in lirc that assigns ttyUSB devices, that is purely the kernel.
--
You received thi
For the record, suspend and resume with both the mceusb and streamzap
drivers in 2.6.38 and up works just fine her, without stopping/starting
lircd. Pretty sure cases where they aren't working are either old
kernels and/or IR device drivers, or buggy usb chipset support.
--
You received this bug
For the love of all that is good, do NOT use that atrocious xbmc wiki
script, that's Doing It Wrong on multiple levels, particularly for the
very latest lirc bits.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.
Already posted a link to the patch in comment #9.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/789819
Title:
Lirc mceusb resume problem
To manage notifications about this bug go to:
https://bugs.l
The added udev rules look fine, they should be harmless and unrelated
here. The pm-suspend log looks fine too. The problem is that your usb
controller appears to be forcing a full disconnect and reconnect of all
usb devices. That equates to a new mceusb device being plugged in, and
some udev and/or
So three problems here:
1) During resume, we see this:
kernel: [ 29.950131] usb 4-3: USB disconnect, address 2
This is your mceusb device. For some reason, your USB chipset isn't
being suspended correctly, and its causing a full disconnect and
reconnect of at least mceusb device. That's bad (an
trace for the actual oops. Can I get the full oops trace please?
Basically, I think this is a manifestation of something I've already
submitted a fix for upstream, but its a slightly unexpected one.
http://git.kernel.org/?p=linux/kernel/git/jarod/linux-2.6-ir.git;a=co
What is this business about:
8<
Jun 16 19:28:46 htpc kernel: [ 186.431342] lirc_dev: module unloaded
Jun 16 19:28:46 htpc kernel: [ 186.441789] lirc_dev: IR Remote Control driver
registered, major 250
Jun 16 19:28:46 htpc kernel: [ 186.444385] ir_lirc_codec: Unknown parameter
`lirc_dev'
Okay, so it looks like there may well be some work that needs to be done
on the resume function of the mceusb driver. Getting that squared away
is the real answer to this problem, not some highly questionable script.
I have the topseed 1784:0008 device myself, should be able to reproduce
(and fix)
Pretty sure that 2.6.32-era driver code for the Nova-T 500 doesn't
support anything but a Hauppauge RC5 remote, without significant
hacking. You may have better luck with a 2.6.38 kernel, or at least, a
media_build replacement of all your v4l/dvb/rc code.
http://www.linuxtv.org/wiki/index.php/How_
Which of the traces in the arch ticket are you seeing? The one Benjamin
Hodgetts was seeing is definitely fixed in the upstream kernel,
including the 2.6.38.y stable tree. The other one from nicoalas is news
to me.
--
You received this bug notification because you are a member of Ubuntu
Bugs, whi
ry kept up
to date with the latest and greatest information for how to configure
every remote under the sun would be helpful. I just don't have the
time to create such a thing. I do answer quite a bit of email on the
aforementioned mailing lists though. The mythbuntu control center and
har
Its not "some conflict". The kernel has IR drivers in it now, with
protocol decoders, so you get native linux input layer events from most
stock remotes, no lirc required whatsoever. There's also an lirc bridge
driver in the kernel for "legacy" mode, but the need to disable the in-
kernel decoders
I'm still quite sure ati_remote + lircd's devinput driver works just
fine for the firefly hardware when you're talking to the right event
device.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/787735
T
That "automatic lirc resume script" is full of fail. Wtf is it trying to
rmmod/modprobing the driver for? Who comes up with this sort of dreadful
crap?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/789
ati_remote apparently doesn't have everything in the driver properly
wired up for udev to create the persistent symlink in by-id/, so you'll
have to use some other means of discovery. You can point straight to a
/dev/input/eventX device, or by name or phys, per
http://lirc.org/html/devinput.html.
You need to fill in REMOTE_DEVICE, per my prior comment.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/787735
Title:
Snapstream Firefly non-functional
--
ubuntu-bugs mailing list
ubuntu-bugs@lists
Okay, dmesg looks much better. I'm assuming some "helpful" Ubuntu lirc
package bit is adding that blacklist file. Remove it. Let ati_remote
load. Instruct lircd to use the 'devinput' driver, with device
'/dev/input/by-id/', and the lircd.conf.devinput config
provided by lirc. Dunno how or if that's
Also, from dmesg:
[ 31.654252] lirc_dev: IR Remote Control driver registered, major 61
[ 31.654621] ir_lirc_codec: Unknown symbol lirc_dev_fop_poll (err 0)
[ 31.655146] ir_lirc_codec: Unknown symbol lirc_dev_fop_open (err 0)
[ 31.655242] ir_lirc_codec: disagrees about version of symbol li
Ah, so you've blacklisted ati_remote, ok, that makes more sense then.
But why do that? Let ati_remote load, and then use lircd's devinput
mode. (Not that atilibusb shouldn't work too).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
ht
"Editing atilibusb out of /etc/modprobe.d/lirc-blacklist allows the
module to be loaded" is, um, well, nonsensical. Config files in
/etc/modprobe.d/ are for configuring kernel module loading params.
atilibusb isn't a kernel module. Its a userspace lircd driver plugin.
--
You received this bug not
lsusb and dmesg output after a clean boot please. My suspicion: the in-
kernel ati_remote driver is already bound to it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/787735
Title:
Snapstream Firefl
This is now supported by the ite-cir driver that was merged in 2.6.39.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/626030
Title:
lirc does not have support for ITE8708 receiver
--
ubuntu-bugs ma
OP: Note also though: devinput mode with the windows media center rc-6
keymap loaded isn't going to work at all with a TiVo remote. You need to
either load a tivo keymap (which I don't think exists until kernel
2.6.39 or .40), or just use the /dev/lirc0 method with the TiVo
lircd.conf you were prev
There are two perfectly valid ways to use the mceusb driver, one is via
the "default" lirc driver and /dev/lirc0, the other is using devinput
and the mceusb device's input layer event device (or better, its symlink
in /dev/input/by-id/). The current problem with trying to use devinput
mode is that
Public bug reported:
Binary package hint: lirc-modules-source
Ubuntu 11.04 is shipping with a 2.6.38 kernel, which has numerous lirc
device drivers from the staging tree enabled, as well as rc-core
infrastructure and several new rc-core device drivers. The rc-core
drivers and the in-kernel lirc d
http://lirc.git.sourceforge.net/git/gitweb.cgi?p=lirc/lirc;a=commitdiff;h=77c9429dde46f108ab4ba47791977abae3a6af3c
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/663497
Title:
Transmitter (irsend) br
I've had at least one report that the 2.6.36 imon module behaves as
expected for another imon/mce user -- but it does still require v4l-
utils ir-keytable. However, I don't think the problem here is actually
in the imon code itself, but rather in the ir layer, so simply pulling
in imon.c from 2.6.3
I've patched a 5ms exit delay into the send_packet() function in
lirc_imon in current lirc cvs (and in the merged-upstream-in-2.6.35 imon
driver). The microsecond delays were a bit on the low side. This 5ms
delay doesn't show any functional regressions on any of the three imon
devices I've got, and
There's a patch for this in the 2.6.32.y stable tree:
http://git.kernel.org/?p=linux/kernel/git/stable/linux-2.6.32.y.git;a=commitdiff;h=7e1228c91635433ff63583dbdc6f1a1249dd5116
--
Syslog fills up with generic-usb "control queue full"
https://bugs.launchpad.net/bugs/422035
You received this bug
** Description changed:
Binary package hint: console-data
I am running Lucid-amd64 on my machine.
lsb_release -rd
Description:Ubuntu lucid (development branch)
Release:10.04
I installed it via:
debootstrap --arch amd64 lucid /tftpboot/ubuntu-10.4
http://de.archi
** Description changed:
Binary package hint: console-data
I am running Lucid-amd64 on my machine.
lsb_release -rd
Description:Ubuntu lucid (development branch)
Release:10.04
I installed it via:
debootstrap --arch amd64 lucid /tftpboot/ubuntu-10.4
http://de.archi
Public bug reported:
Binary package hint: console-data
I am running Lucid-amd64 on my machine.
lsb_release -rd
Description:Ubuntu lucid (development branch)
Release:10.04
I installed it via:
debootstrap --arch amd64 lucid /tftpboot/ubuntu-10.4
http://de.archive.ubuntu.com/ubuntu/
c
I forgot to provide the link to the docu page.
Here it is: http://library.gnome.org/admin/gdm/stable/configuration.html.en
--
XDMCP cannot be enabled via custom.conf
https://bugs.launchpad.net/bugs/477270
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscr
Public bug reported:
Binary package hint: gdm
I am running Ubuntu 9.10 x86_64 with gdm 2.28.1-0ubuntu1.
According to point 5.4.4 on the Gnome gdm docu page an "Enable=true"
under [xdmcp] in /etc/gdm/custom.conf should be sufficient to enable
XDMCP from gdm. Unfortunately it isn't.
** Affects: g
*** This bug is a duplicate of bug 442498 ***
https://bugs.launchpad.net/bugs/442498
I have found a little HowTo, explaining how to populate the LDAP server under
Ubuntu 9.10.
See here: http://ubuntuforums.org/showpost.php?p=8161118&postcount=6
Please consider this problem solved.
--
no pro
Public bug reported:
Binary package hint: slapd
I'm running Ubuntu 9.10 x86_64 with package slapd version
2.4.18-0ubuntu1.
Upon first installation of slapd, the user is not prompted to enter the admin
password as described for Ubuntu 9.04 (see:
https://help.ubuntu.com/9.04/serverguide/C/openld
Michael Nagel wrote:
> is this still an issue?
>
> ** Changed in: linux-restricted-modules (Ubuntu)
>Status: New => Incomplete
>
I do not have this motherboard and graphics card anymore, so I cannot
tell if the problem still persists.
Regards.
André
--
Black Screen after Login with
Hi Sebastien,
I've used Evolutioin 2.24.2 and it working fine now.
Thanks for your help.
Bob
--
e-mail redirect doesn't work correctly
https://bugs.launchpad.net/bugs/281202
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-b
the receiver will reply to your e-mail address, and not to the address
it originated from.
--
e-mail redirect doesn't work
https://bugs.launchpad.net/bugs/281202
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing lis
* Is this reproducible?
Yes, it is reproducible.
* If so, what specific steps should we take to recreate this bug?
1) open the mailbox,
2) double click on the email and a new windows appears
3) Click on "Message" and choose "Forward as" en choose "redirect"
4) Enter the new email adres and click "
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/18391317/Dependencies.txt
** Attachment added: "ProcMaps.txt"
http://launchpadlibrarian.net/18391318/ProcMaps.txt
** Attachment added: "ProcStatus.txt"
http://launchpadlibrarian.net/18391319/ProcStatus.txt
--
e-mail
Public bug reported:
Binary package hint: evolution
Hi,
I'm trying to redirect an email i received in my inbox.
The email was intended for our customer-ticket system. When I redirect
the e-mail to the system with evolution, it looks like the e-mail is
sent from my account in stead of the origin
I can confirm this bug too.
with this bug, the whole system nearly unusable..
--
control modifier gets lost in hardy
https://bugs.launchpad.net/bugs/211892
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
Sarah is right, install kdebase-kio-plugins can fix this problem
--
Problem with deleting files in amarok from within gnome.
https://bugs.launchpad.net/bugs/60475
You received this bug notification because you are a member of Kubuntu
Team, which is subscribed to amarok in ubuntu.
--
kubuntu-bug
after
sudo ln -s /usr/lib/libexpat.so /usr/lib/libexpat.so.0
wink can launch, but seems its function not working.
new a project and press the hotkeys no screenshot being done
--
wink: error while loading shared libraries: libexpat.so.0
https://bugs.launchpad.net/bugs/208125
You received this bug
Public bug reported:
Binary package hint: wink
ubuntu: 8.04
[code]
$ wink
/usr/lib/wink/wink: error while loading shared libraries: libexpat.so.0: cannot
open shared object file: No such file or directory
[/code]
can fix by:
[code]
sudo ln -s /usr/lib/libexpat.so /usr/lib/libexpat.so.0
[/code]
Public bug reported:
Binary package hint: empathy
ubuntu: 8.04
empathy: 0.22.0-1
after install empathy and launch it one time, now when i login gnome
session, empathy will start too( i exit the empathy program before last
logout)
** Affects: empathy (Ubuntu)
Importance: Undecided
Public bug reported:
I installed Ubuntu 7.10 x86_64 on an Asus P5K with 2G RAM , Intel E4500, NVidia
8600GTS and a 250GB "SAMSUNG HD250HJ" HDD.
After installation Gnome was working fine, but after installing the
nvidia-glx-new driver(plus enabling) and rebooting, the screen went all black
after
84 matches
Mail list logo
