Nel,
Just try the script on your 10.10, and let us know.
One or two months ago, I tried to compile the source on 10.10 alpha, and it
gave errors. After some googling, it looked liked kernel 2.6.34+ needs some
extra #define in the C source code
Sander
On Mon, Oct 11, 2010 at 23:42, Nel Mac <622
Anders,
The patch you're pointing to (dated feb 2010) is incorporated in the source
made by 'anttip' and available on
http://linuxtv.org/hg/~anttip/tda18218/rev/40e288163c8d (dated july 2010)
I'm pointing to (and my script on
http://www.appelboor.com/af9015/usb-dvb-make-script.sh uses )
But, AFA
H
Sander
On Thu, Sep 23, 2010 at 18:26, Sander Jonkers - GMX wrote:
> Anders,
>
> The patch you're pointing to (dated feb 2010) is incorporated in the
> source made by 'anttip' and available on
> http://linuxtv.org/hg/~anttip/tda18218/rev/40e288163c8d (d
The status is now "Nominated for Maverick by Joe".
What are the chances this af9015 / TDA18218 bugfix will get into the
official Maverick release, so ultimately (before) 10-10-10? Reason: I
believe there's now a feature freeze in place for Maverick, so I'm
wondering about the Maverick feasibility.
A tip for Do-It-Yourself-ers: it seems you can check which af9015 driver
has been tda18218 patched (by yourself ;-( ). Howto: run the one-liner
below, and if it says "tda18218_attach" on the next line, it's patched.
Below is my output; apparantly I've two version patched, the others not.
san...@
Hi Jeremy,
On which Ubuntu should I test this: Lucid or Maverick?
And which upstream kernel should I use? The most recent dated version within
Lucid or Maverick? So, for Lucid: within
http://kernel.ubuntu.com/~kernel-ppa/mainline/ the
http://kernel.ubuntu.com/~kernel-ppa/mainline/v2.6.35-rc1-luci
FWIW:
On Maverick Meerkat (Ubuntu 10.10) Alpha 3, the kernel message is
af9015: tuner NXP TDA18218 not supported yet
So let's check if that message is going to disappear in the newer
versions ...
--
USB DVB-T: TDA18218 not yet compiled in af9015
https://bugs.launchpad.net/bugs/622397
You recei
Public bug reported:
Short: This is a request to get the TDA18218 patched compiled into the
Ubuntu Linux kernel.
Long:
I have a DVB-T USB stick with an af9015 chip, and a TDA18218 tuner. The
TDA18218 is not recognized. This is a well known problem. The relevant
message in /var/log/messages is:
** Attachment added: "AlsaDevices.txt"
https://bugs.launchpad.net/bugs/622397/+attachment/1511415/+files/AlsaDevices.txt
** Attachment added: "AplayDevices.txt"
https://bugs.launchpad.net/bugs/622397/+attachment/1511416/+files/AplayDevices.txt
** Attachment added: "ArecordDevices.txt"
PS:
Best to run the script with sudo.
Running the script (Compiling) takes 10 - 40 minutes, depending on the speed of
your machine
I will post the /var/log/messages with the corrert drivers in place (ie after
running my script)
--
USB DVB-T: TDA18218 not yet compiled in af9015
https://bugs.lau
Bug report
https://bugs.launchpad.net/ubuntu/+source/kaffeine/+bug/553320 has the
same problem ("af9015: tuner id:179 not supported, please report!"), but
the bug report is incorrectly linked to kaffeine; it's a kernel driver
problem.
--
USB DVB-T: TDA18218 not yet compiled in af9015
https://bugs
After running my script (compiling took 18 minutes on my Athlon X2), and
a reboot, the /var/log/messages shows that the USB-stick is recognized
(see below): "NXP TDA18218HN successfully identified.".
IMHO this means the patch is correct, and I hope it can get into the
mainstream kernel.
Aug 22 2
Additional remark: the need to not-compile firedtv has to do with
another bug, as http://www.linuxtv.org/wiki/index.php/How_to_Obtain
,_Build_and_Install_V4L-
DVB_Device_Drivers#Building.2FCompiling_the_Modules says:
/QUOTE
Building/Compiling the Modules
Note: If you are using Ubuntu, before proce
Maik,
Yup, that's exactly the problem. "Solution": stick with 10.04 and run my
script to get your USB stick working.
On Thu, Sep 30, 2010 at 20:26, Maik Wagner
<622...@bugs.launchpad.net>wrote:
> I am currently testing the RC of Maverick Meerkat and dmesg gives me the
> following output:
>
> [
Public bug reported:
Fresh install of Ubuntu 22.04, fully updated, no changes or configuration at
all.
Newish HP laptop (so recent hardware)
Problem: After resuming from suspend, the laptop's keyboard is not
working for about 30 seconds (the laptop's touchpad is working at once).
Looking at dme
Ah, it seems to happen after a fresh boot too: the login is there, mouse
is working, but keyboard not. It takes 20 - 30 seconds before keyboard
is working.
Snippet from dmesg (leaving out wlo1 stuff):
...
[di mei 31 20:09:47 2022] skl_hda_dsp_generic skl_hda_dsp_generic:
hda_dsp_hdmi_build_contr
Still there in current Ubuntu 22.04 (fresh install, fully updated)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1960893
Title:
i915 gives trace in dmesg
To manage notifications about this bug go t
Thanks for replying.
See included dmesg. I generated it with the following command ...
hopefully OK
sudo dmesg -T > dmesg_after_suspend_and_resume.txt
Snippet from dmesg:
[wo jun 1 11:38:40 2022] i8042: [28649] 65 -> i8042 (parameter)
[wo jun 1 11:38:40 2022] i8042: [28649] ab <- i8042 (inte
I tried "i8042.noaux=1", but no change: after boot and after resume:
touchpad works immediatly, but keyboard takes 25-45 seconds.
dmesg included
** Attachment added: "dmesg "i8042.noaux=1""
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1976396/+attachment/5594428/+files/dmesg.i8042.no
Ah, SOLVED, like this:
Triggered by your remarks, I found
https://unix.stackexchange.com/a/656183, which says:
RUB_CMDLINE_LINUX_DEFAULT="atkbd.reset i8042.reset i8042.nomux quiet splash".
If this doesn't work, follow the same process but try
GRUB_CMDLINE_LINUX_DEFAULT="i8042.direct i8042.dumbk
Out of curiosity:
The manual work (adding the line to GRUB): is that how it should be, or
a bug (something Ubuntu should take care of)?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1976396
Title:
Only i8042.direct ... not good. Keyboard not working for x seconds
Only i8042.dumbkbd ... yes, works! Keyboard working immediatly.
So my /etc/default/grub now contains:
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash i8042.dumbkbd"
And stuff from dmesg:
sander@zwart2204:~$ sudo dmesg | grep i8042
[
Interesting ... triggered by "[ 0.278602] i8042: PNP: PS/2 appears to
have AUX port disabled, if this is incorrect please boot with
i8042.nopnp", I just tried i8042.nopnp as only option in GRUB, and that
works too: keyboard works immediatly.
And that message was already in the first dmesg ... so t
That second paragraph should read:
And that message was already in the first dmesg ... so the i8042 driver
already KNEW something was fishy, and hinted what I should do ... ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bug
Me too. I did the things below. I'll now test if the flicerking is gone.
Interesting quote above: "running on battery also seems to worsen the
problem slightly.". I normally use my laptop on power, but on battery
for the past days. So that might be reason I only noticed it now.
sander@witje:~$
Public bug reported:
Unstable Wifi
Sometimes most Wifi AP's (including my own) or not seen
dmesg filled with
[di feb 15 06:44:54 2022] rtw_8821ce :01:00.0: failed to send h2c command
[di feb 15 06:44:54 2022] rtw_8821ce :01:00.0: failed to send h2c command
[di feb 15 06:44:54 2022] rtw_8
Public bug reported:
[1.904158] kernel: [ cut here ]
[1.904159] kernel: i915 :00:02.0: drm_WARN_ON(val == 0x)
[1.904176] kernel: WARNING: CPU: 3 PID: 328 at
drivers/gpu/drm/i915/display/intel_tc.c:761 intel_tc_port_init+0x1c4/0x1d0
[i915]
[1.9
Public bug reported:
Ubuntu 24.04, fully updated
Running arp-scan with sudo, results in the errors below and no OUI
resolving, if the current directory is not owned or not writable by
root.
Also in Debian:
https://groups.google.com/g/linux.debian.bugs.dist/c/Fh4m_uTbUGQ
A bug, a feature, or a P
The same problem on another system (xubuntu 24.04):
sander@xubuntu:~$ sudo arp-scan --localnet --interface=wlp2s0 | head -4
Interface: wlp2s0, type: EN10MB, MAC: 84:4b:f5:47:70:6d, IPv4: 192.168.178.31
WARNING: Cannot open MAC/Vendor file ieee-oui.txt: Permission denied
WARNING: Cannot open MAC/V
FWIW / Workaround:
Uninstalled arp-scan
From https://github.com/royhills/arp-scan, made and installe arp-scan, and it's
working:
sander@xubuntu:~$ sudo arp-scan --localnet --interface=wlp2s0 | head -4
Interface: wlp2s0, type: EN10MB, MAC: 84:4b:f5:47:70:6d, IPv4: 192.168.178.31
Target list from
Same here on my Ubuntu 24.04.1:
$ sudo bpftrace
bpftrace: error while loading shared libraries: libLLVM-18.so.18.1: cannot open
shared object file: No such file or directory
$ apt-show-versions | grep -i bpftrace
bpftrace:amd64/noble-updates 0.20.2-1ubuntu4.2 uptodate
Indeed problem gone after
? Related:
https://github.com/bleachbit/bleachbit/issues/1703#issuecomment-2306621045
"From a fast search these escape sequence are deprecated from python 3.6
and SyntaxWarning from 3.12"
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu
And using xlsx2csv, also results in Warnings:
$ xlsx2csv powerbi.xlsx bla-xls2csv.csv
/usr/bin/xlsx2csv:809: SyntaxWarning: invalid escape sequence '\d'
elif re.match("^\d+(\.\d+)?$", self.data) and re.match(".*[hsmdyY]",
format_str) and not re.match(
/usr/bin/xlsx2csv:810: SyntaxWarning: inva
$ xlsx2csv --version 2>/dev/null
0.7.8
whereas https://github.com/dilshod/xlsx2csv is at 0.8.3 (July 2024).
So ... I installed the python pip module xslxc2v in a uv venv:
uv venv
uv pip install xlsx2csv
... and no more error message:
$ .venv/bin/xlsx2csv --version
0.8.4
So already solved
FWIW
Found on https://stackoverflow.com/a/50504635 :
Python 3 interprets string literals as Unicode strings, and therefore your \d
is treated as an escaped Unicode character.
Declare your RegEx pattern as a raw string instead by prepending r, as
below:
r'\nRevision: (\d+)\n'
--
You received
Was solved in September 2022 in the source: 'update regex string-
literals to avoid "DeprecationWarning: invalid escape sequence"'
https://github.com/dilshod/xlsx2csv/commit/b88b6b7a3b9089c3d373e4c73933969f75c6927d
(found via blame:
https://github.com/dilshod/xlsx2csv/blame/master/xlsx2csv.py#L86
Public bug reported:
$ sudo apt install xlsx2csv
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following NEW packages will be installed:
xlsx2csv
0 upgraded, 1 newly installed, 0 to remove and 1 not upgraded.
Need to get 186 kB of archives.
401 - 437 of 437 matches
Mail list logo
