Public bug reported:
here it is: http://tumble.brouhaha.com/
i find it very useful and now that i finally recalled its name i'd like it to
be packaged in ubuntu :D
thanks
Paolo
** Affects: Ubuntu
Importance: Undecided
Status: New
** Tags: needs-packaging
--
[needs-packaging]
Here it's greyed out too
--
Split in volumes - option gets grayed out.
https://bugs.launchpad.net/bugs/513244
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
update: it works with rar and 7z , after i installed them
--
Split in volumes - option gets grayed out.
https://bugs.launchpad.net/bugs/513244
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
I confirm that this bug still exist currently, on lucid
--
Changing long passwords causes spurious error
https://bugs.launchpad.net/bugs/356766
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Public bug reported:
Since lucid, when i try to connect with gnokii to my nokia 6510, it
starts hanging and it does not work anymore.
irattaching the dongle works fine and irdadump shows that the device is
actually recognized, but when gnokii starts to communicate with the
phone, it starts
what i did, precisely, is:
# modprobe ircomm-tty
# modprobe irda-usb ; irattach irda0 -s
# gnokii --getdisplaystatus
GNOKII Versione 0.6.28
then gnokii hangs indefinitely
attached you find the irdadump log. you find at line 21 the beginning of
the communication with my irda phone (nokia
it also happens with the newer gnokii 0.6.29 (non in ubuntu)
So i assume it's not a gnokii fault
--
irda-usb and gnokii/other ir apps doesnt work anymore since lucid
https://bugs.launchpad.net/bugs/596400
You received this bug notification because you are a member of Ubuntu
Bugs, which is
i changed to simple IRDA now, and gnokii works again!
so problem solved thanks
--
irda-usb and gnokii/other ir apps doesnt work anymore since lucid
https://bugs.launchpad.net/bugs/596400
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hi, I have the same problem now (2014 07).
I tried to patch /usr/src/dahdi-2.5.0.1+dfsg-1ubuntu3/ like in post #8, but
patch fails not finding the file to patch.
I also trie to modify xbus-sysfs.c y hand following the patch changes, and then
it compiles but it fails to load, complaining like:
I must also report that uninstalling the two packages (dahdi-linux and
dahdi-dkms), downloading dahdi from asterisk website (version
2.9.something) and compiling from sources against the ubuntu kernel
works, and the module seems to load fine
--
You received this bug notification because you are
Nobody that is able to even reproduce this?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1733068
Title:
Unmounted USB drives wake up on 16.04
To manage notifications about this bug go to:
Seems that with the new kernel the disk stays awake and never even tries
to go standby:
http://codepad.org/lIRqEBOW
Edit:
i did stop this script for a while, and the disk went to sleep (not standby,
but i think suspend or more. The drive was not only spun down, but the light
was blinking, so
working on it, but i was also thinking: The same value is returned in 14.04.
Can it be that 16.04 kernel does not honor that value and keeps polling at a
10minute interval?
these driver sense error always come up at a 600secs interval, and they
are definitely generated by the same process that
Trying 4.14.4 ((from mainline debs).
So far it looks promising: Hdparm seems now able to also query/set the status
(before it was returning an error with this drive), and it's about one H since
i forced it to standby and the drive is staying in standby.
--
You received this bug notification
Spoke too early, drive just woke up out of the blue, after having been
manually unmounted in nautilus, and forced to standby with hdparm -y
(now that it works), without me re-mounting it or anything.
dmesg does not report anything relevant:
[ 641.041831] EXT4-fs (sde1): mounted filesystem with
Updated the description: I tested with 14.04 and as expected everything
goes to sleep when it should and stays sleeping.
I have the serious fear this is a regression in the kernel SATA subsystem.
HOWEVER, i'm willing to test it more on 16.04.
Could someone point me at a super stripped-down
and, by the way, this is the kind of messages that flood dmesg:
[ 118.189091] sd 7:0:0:0: [sdc] tag#0 FAILED Result: hostbyte=DID_ERROR
driverbyte=DRIVER_SENSE
[ 118.189101] sd 7:0:0:0: [sdc] tag#0 Sense Key : Hardware Error [current]
[descriptor]
[ 118.189106] sd 7:0:0:0: [sdc] tag#0 Add.
also, on 16.04, in addition to the above messages, the drive not only
does not go to standby (with the led blinking regularly), but it also
does not spin down. Tested with 3 different 16.04 (2 ubuntus and one kde
neon) on 2 different systems
--
You received this bug notification because you are
Thank you Alan, for providing these valuable info.
Actually i noticed the polling by looking at dmesg. I suspected that the errors
in my distribution's kernel (4.4.0 in 16.04) were somehow related to a kernel
polling process with a default of 10 minutes.
I will try to do both things you
Ok, i think i gathered some relevant evidence.
I had the drive plugged on a 16.04, and at some point i noticed it went standby
(led blinking intermittently).
Last dmesg lines were [ 6217.720607] perf interrupt took too long (5053 >
5000), lowering kernel.perf_event_max_sample_rate to 25000
[
first finding:
cat /sys/block/sdb/events_poll_msecs
-1
will now proceed testing a newer kernel to check if the problem has been
fixed in the meanwhile
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
so far the feeling is that
-) 3.14 seems to support this drive better, as it appears to be able to
retrieve its power status and to, more importantly, set it, unlike the previous
kernel (4.4-)
-) 3.14 seems to be also more invasive. Previously, hdparm -C would return some
error, but never wake
Public bug reported:
On Ubuntu 16.04, if i plug in a USB drive, then unmount it (eject
button) in nautilus, then force it to sleep (hdparm -y), the drive
reports to be in standby:
hdparm -C /dev/sdd
/dev/sdd:
drive state is: standby
However, after some time during which i have not tried to
yes, of course there's no source package to blame. Or, at least, i donno
which one it would be..
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1733068
Title:
Unmounted USB drives wake up on 16.04
can it be related to
https://bugzilla.redhat.com/show_bug.cgi?id=1351305#c36 ?
** Bug watch added: Red Hat Bugzilla #1351305
https://bugzilla.redhat.com/show_bug.cgi?id=1351305
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
oh, and 14.04 disks stay mounted (just not accessed)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1733068
Title:
Unmounted USB drives wake up on 16.04
To manage notifications about this bug go
Thank you for the suggestion!
So i tried it out, on the unmounted usb drive, and this is what i got:
http://paste.ubuntu.com/26128246/
the fear is that it might not (only) be some userspace daemon to keep the drive
alive..
But it doesn't seem to me that it is easy to understand what's going
to compare, this is what i got on the 14.04 where unmounted HDs stay
standby
http://paste.ubuntu.com/26128324/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1733068
Title:
Unmounted USB drives
Ok, so i managed to start btrace when i saw the disk sleeping and stopped after
it woke up:
http://paste.ubuntu.com/26128577/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1733068
Title:
Unmounted
Happens here too, the proposed fix solves the problem.
Please upstream it!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1774242
Title:
Wacom touchscreens should use libinput, not wacom driver
To
18.04 seems still br0ken. One of the last updates restored the broken
70-wacom.conf
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1774242
Title:
Wacom touchscreens should use libinput, not wacom
Public bug reported:
As per summary, after dist-upgrading a 18.04LTS on the device, the trackpoint
and touchpad buttons stopped working.
Booting back with 5.3.0-40 has them working.
Fix this regression pls (and also add support for the microphone)
** Affects: ubuntu
Importance: Undecided
** Description changed:
As per summary, after dist-upgrading a 18.04LTS on the device, the trackpoint
and touchpad buttons stopped working.
Booting back with 5.3.0-40 has them working.
Fix this regression pls (and also add support for the microphone)
+
+ Update: Just tested 20.04LTS live,
i can confirm this bug in 20.04 as well.
Trying to figure out the workaround for now. Not sure what eoan-proposed is,
and the fw on the intel page is version .34, while in /lib/firmware is .46, so
not sure that is gonna help
--
You received this bug notification because you are a member of
In that comment the link is from -46 to the downloaded -34?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1848921
Title:
iwlwifi firmware crashes intel 9260ac [8086:2526] subsystem
[8086:0010]
** Package changed: ubuntu => linux (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1875983
Title:
Thinkpad X1 Tablet Gen3 trackpoint and touchpad buttons not working
with 5.3.0-51
To
got the driver crash now, after 2 days. so problem isn't fixed in -26.
I also think i found out how to reproduce: The problem happens basically
immediately when connecting a BB10 device (Z10) to the machine with wifi
access point mode activated.
other devices (iOS, xperia) seem to only trigger
got the driver crash now, after 2 days. so problem isn't fixed in -26,
but it works better
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1848921
Title:
iwlwifi firmware crashes intel 9260ac
I tried, with kernel 5.4.0-28 from 20.04, to downgrade to -43 (and,
fwiw, also to 41 and 38, after which i stopped as none was working), but
no luck for me. I might try to boot 5.3.0 which i still have to check if
that helps at all..
--
You received this bug notification because you are a member
Update: i tried again 20.04 live, and, with kernel 5.4.0-26, wifi seems to work
alright.
So i installed 5.4.0-26 (i believe it was already replaced by -28 upon
installation), but by doing so the wifi HW isn't even recognized, with dmesg
looking for microcode. I'll keep investigating how does
Adding that after about half hour i'm still getting
[ 1923.231089] iwlwifi :00:14.3: Unhandled alg: 0x71b
Usually a crash follows. So it might follow. But at least i have
transfered a wholly different amount of data in the meanwhile. -28 and
-29 would be crashing after 2 min or so.
--
You
Problem seems fixed in 5.4.0-26 with hwe package, loading .46 firmware.
So regression introduced in -28 and -29.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1848921
Title:
iwlwifi firmware
5.4.0-29-generic seems so far to improve the situation a little.
It takes longer for the driver to crash, but it eventually does.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1848921
Title:
thanks for the feedback Zed, i will give this a shot.
It's so sad to see how laggy canonical is in fixing such a serious bugs, but
also how careless in introducing regressions such as this one.
I believe these wireless cards are extremely widespread, so i wonder how it's
possible not to catch
the last proposed solution is not fixing the problem at least for me, running:
Linux 5.6.11-050611-generic
Loaded firmware version: 46.6bf1df06.0 9000-pu-b0-jf-b0-46.ucode
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
45 matches
Mail list logo
