Hello Olivier,
thank you very much for your efforts but I have to bring this up here:
Having "some general friction with following upstream" seems to be an ongoing
problem with Thunderbird.
Transition from TB 68 to 78 left users of ubuntus latest LTS without security
updates for over 6 months
I can confirm that the new PGP solution is working flawlessly in
thunderbird 1:78.7.1+build1-0ubuntu0.20.04.1.
I personally don't _like_ this new integrated pgp approach but it works
as intended. Hope there will be more enigmail feeling soon but well,
this back port seems to be ready for
At Fosdem 21 conference it was announced that next summer Thunderbird 91
will be released, which again will include fundamental changes. My
impression is that this time many months have been wasted because of
unclear procedures and responsibilities - not because of unsolvable
technical problems.
Konstantin is right. I'm also using the snap for now but for different
reasons this is not a good solution for beginners - like my parents for
example.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I have been watching this issue for several months and am excited that
it is finally moving forward. It looks to me like all the organizational
details have now been resolved. What's still holding us back from
getting the latest Thunderbird?
--
You received this bug notification because you are
I've tested torbrowser-launcher 0.2.9-2ubuntu1 from bionic-proposed with
Ubuntu 18.04 and Linux Mint 19.3 and can confirm that everything is
running perfect again. torbrowser-launcher 0.2.9-2ubuntu1 has been able
to update Torbrowser to Version 10.0.1. on both machines. All these
error messages
Oh, please excuse me. (These many different drivers and kernels begin to
confuse me. ;) )
I wanted to say that AMDGPU with kernel 5.3 is affected here.
Can you say when there will be a fixed AMDGPU/kernel version will be
available for Ubuntu 18.04?
Thanks!
--
You received this bug
I (and some others I saw) have this problem with RADEON and recent 5.3
kernel and this is already the newest kernel that comes with Ubuntu
18.04. I want to stay with the standard kernels as this is my productive
system and I don't want to mess it.
Can you say, when a patched kernel with working
Thank you, Martin, for providing this simple but clever and VERY
effective workaround! I can confirm that it works.
I'd like to add, that you have to execute this script with 'bash fix_sound.sh'.
'sh fix_sound.sh' doesn't work because debian and ubuntu use dash as
non-interactive shell and dash
Same here. Still no sound with the testing kernels. :-/
For the sake of completeness I have also attached the dmesg output with some
other current and old kernels. Only with 4.15.0-50 and 5.0.0-15 I have sound.
I'm eagerly waiting for the solution to this problem.
--
You received this bug
** Attachment added: "dmesg_5.0.0-34.36+hdmi-audio-test-generic_no-sound.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1834771/+attachment/5309662/+files/dmesg_5.0.0-34.36+hdmi-audio-test-generic_no-sound.txt
--
You received this bug notification because you are a member of
** Attachment added: "dmesg_5.0.0-36-generic_no-sound.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1834771/+attachment/5309666/+files/dmesg_5.0.0-36-generic_no-sound.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: "dmesg_4.15.0-50-generic_sound-working.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1834771/+attachment/5309663/+files/dmesg_4.15.0-50-generic_sound-working.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Attachment added: "dmesg_5.0.0-15-generic_sound-working.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1834771/+attachment/5309664/+files/dmesg_5.0.0-15-generic_sound-working.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
** Attachment added: "dmesg_4.15.0-72-generic_no-sound.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1834771/+attachment/5309665/+files/dmesg_4.15.0-72-generic_no-sound.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Attachment added: "dmesg_4.15.0-68.77+hdmi-audio-test-generic_no-sound.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1834771/+attachment/5309661/+files/dmesg_4.15.0-68.77+hdmi-audio-test-generic_no-sound.txt
--
You received this bug notification because you are a member of
All affected users I found in forums so far reported that they have
amdgpu in use.
I don't know if nouveau and radeon drivers have the same problem or not.
So as you already wrote in
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1834771/comments/20
the root problem seems to be that amdgpu
The submitted fix causes many users to have no HDMI sound at all,
because they are not able to select their sound device. See the
corresponding bug report:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1834771
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Please excuse the delay.
I can confirm now, that Kernel 5.3.0-19 is also affected by this
problem.
Thanks for your assistance but I don't see why switching to proprietary
drivers should be the right solution for a regression introduced as a
side effect of a bugfix. In your bug
correction: Pavucontrol shows all available HDMI OUTputs as "unplugged".
(and Gnome Sound Setting doesn't show any HDMI devices at all)
... and before someone suggests it: I don't think "All AMD users should wait
for a maybe fixed Kernel 5.2." is not a proper solution for that problem. :-)
--
I'm also affected by this bug under Linux Mint 19.2 and with Radeon RX 580
(amdgpu driver).
With all new Kernels from 5.0.0-16 on my HDMI monitor isn't recognized as
"plugged in" and I don't have audio output. Pavucontrol shows all available
HDMI imputs as "unplugged".
Going back to 5.0.0-15
As long as the Thunderbird people provide Lightning-Updates as Addon,
this method IS update proof. (But nobody knows, how long they will do
that because officially Lightning is shipped as part of Thunderbird
now.)
This method may work for the next months(years?) but you are right: We
finally need
Use your Eyes, Elbarbudo!!! :-)
Newest Thunderbird version in Ubuntu 18.04 is 60.4.0 and
lightning-6.2.5-sm+tb.xpi requires at least 60.5. You need
lightning-6.2.4-sm+tb.xpi (or an older one depending on your
Thunderbird) - all aviable on the same website.
Two ways to get it right:
- Check your
All relevant Lightning versions for current Thunderbird 60.x have been
uploaded to Thunderbird addons page:
https://addons.thunderbird.net/thunderbird/addon/lightning
So localized Lightning can be downloaded and installed again.
I can confirm this workaround is working!
Let this never ending
I added proposed repo again and installed samba version 2:4.7.6+dfsg
~ubuntu-0ubuntu2.4 from proposed and I'm happy to say, that this version
fixed the bug. I tested Nemo, Nautilus and Thunar and all of them are
able to delete all kind of directories within Samba shares now. Thanks a
lot for your
No problem. Thank you for your time! Will review the new patch when its
out. :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1795772
Title:
rmdir on non-empty samba directory fails silently
To
Thunar (1.6.15) is also affected now. Without the fix Thunar was able to
delete empty and non-empty directories. Now it cannot delete ANY
directory too. :(
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: samba (Ubuntu Bionic)
Status: Fix Committed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1795772
Title:
rmdir on non-empty samba directory fails silently
To
Ok, I did further testing and the fix made things even worse!
(I used two - apart from this new samba version - identical VMs to verify the
behavior.)
Before the fix I was not able to delete non-empty directories.
With installed fix I'm not able to delete ANY directory - regardless of content!
I also rebooted my client but the problem persists. I searched Synaptic
for "samba" and all samba packages are version 2:4.7.6+dfsg~ubuntu-
0ubuntu2.3 now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I added proposed repo and installed samba version 2:4.7.6+dfsg~ubuntu-
0ubuntu2.3 from proposed, but to be honest I don't see any difference in
Nemo.
I tested with Nemo 3.8.6 to delete a non empty directory within a smb
share before and after the update and both failed silently. Just to be
sure:
** Tags removed: verification-needed-bionic
** Tags added: verification-failed-bionic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1795772
Title:
rmdir on non-empty samba directory fails silently
As nobody seems to care for this bug, I also think Lightning translation
will be broken forever. :-(
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/545778
Title:
xul-ext-lightning is only available
Any good news? :-)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1795772
Title:
rmdir on non-empty samba directory fails silently
To manage notifications about this bug go to:
I don't see any progress here. Meanwhile some corresponding Bugs at
Thunderbird's Bugzilla have been closed because this localization issue
is a packaging problem and they decided not to provide any new
(localized) Lightning versions via AddOn functionality because they
already ship it with
https://ftp.mozilla.org/pub/calendar/lightning/candidates/6.2b6-candidates/build1
/linux-x86_64/
here you only get betas of Lightning and not the final versions. And
also no automated updates at all. So this can only be a temporary
limited workaround.
--
You received this bug notification
The Thunderbird people don't provide current Lightning versions in their
AddOn repository anymore because they integrated Lightning in their
Thunderbird builds. It is a real shame that this localization issue
persists for nearly one decade now. Because of this shortcoming (missing
translations for
Hello Andreas,
this answer makes me calm me down. I thought for a second bionic has been
forgotten. And yes, this bug is indeed very very annoying. I'm surprised that
I'm the first one who reports this. Probably most affected users don't even
noticed yet that they are constantly leaving a mess
Thanks for your work! Progress looks promising, but I run samba
2:4.7.6+dfsg~ubuntu-0ubuntu2.2 on bionic. Would you please push your fix
also to this package so that LTS users benefit from a working delete
function. Please excuse my impatientness. I'm not familiar with the
process of bug fixing at
Public bug reported:
When you delete a non-empty directory in Nautilus or Nemo, the Folder-
Icon disappears and stays away but when you refresh the current
directory or navigate back there it reappears. No error message at all.
This bug is very annoying in two ways:
1) When you only have smb
40 matches
Mail list logo
