Package: lxpanel
Followup-For: Bug #1052376
X-Debbugs-Cc: pitsior...@outlook.com
I just noticed that lxpanel got an upgrade earlier this month. However, since
there is no changelog from upstream, it is really sad to see that 1 major
release and 1.5 years later the only issue that was fixed was the
Package: lxpanel
Followup-For: Bug #1052376
X-Debbugs-Cc: pitsior...@outlook.com
One year after the worst gtk3 migration ever and the package remains broken. On
my end, the forked lxpanel 0.10.2.r1 of lxde-continued solved only the geometry
issue but not the rest (tooltips, theming, cropped icons
Package: deborphan
Version: 1.7.35
Followup-For: Bug #1065310
X-Debbugs-Cc: pitsior...@outlook.com
Thank you for the clarification. As it seems, there is no viable alternative to
deborphan right now :(
-- System Information:
Debian Release: trixie/sid
APT prefers testing
APT policy: (990, 't
Package: deborphan
Version: 1.7.35
Followup-For: Bug #1065310
X-Debbugs-Cc: pitsior...@outlook.com
As a user of deborphan for more than a decade on all my systems, it is sad to
see it go. Is there an apt command or parameter that replaces it?
-- System Information:
Debian Release: trixie/sid
A
Package: lxpanel
Version: 0.10.2.rc1-1
Followup-For: Bug #1052376
X-Debbugs-Cc: pitsior...@outlook.com
Since there is no interest from the maintainers in fixing a 6+ month old grave
bug, I want to ask. Has anyone moved away from lxpanel or even lxde? I would
switch to lxqt, but lxqt is one major v
Package: lxpanel
Version: 0.10.2.rc1-1
Followup-For: Bug #1052376
X-Debbugs-Cc: pitsior...@outlook.com
Judging from the infrequient updates the package gets in the last couple of
years, I think that it will be fixed after the freeze for debian 13, because it
must be sorted out as a grave but. And
Package: mesa-vdpau-drivers
Followup-For: Bug #1059782
X-Debbugs-Cc: pitsior...@outlook.com
I know that mesa 24 will fix the issue, and I know it has been packaged in
experimental, since I first noticed my videos showing black with vaapi, 1+ week
ago.
Sadly, mesa is a core component of the os, lik
Package: mesa-vdpau-drivers
Followup-For: Bug #1059782
X-Debbugs-Cc: pitsior...@outlook.com
Sadly, I do not have a gitlab account. But I think that the issue is discussed
here
https://gitlab.freedesktop.org/mesa/mesa/-/issues/10468
Below is the output of vaapi-info. Please notice the first lines
Package: mesa-vdpau-drivers
Followup-For: Bug #1059782
X-Debbugs-Cc: pitsior...@outlook.com
So, 23.3.4 reached testing today and the problem is still there. As expected,
it is not an upstream issue, so can the maintainer have a look at the
forementioned patch and correct the package?
If it helps,
Package: mesa-vdpau-drivers
Followup-For: Bug #1059782
X-Debbugs-Cc: pitsior...@outlook.com
@Vasyl Gello
Shouldn't this be opened under mesa-VA-drivers as a new bug report with the
same or greater severity?
I am on a 6450, I am using radeon and I have lost vaapi on all my players since
23.3.x mov
Package: lxpanel
Version: 0.10.1-4.1
Followup-For: Bug #1052376
X-Debbugs-Cc: pitsior...@outlook.com
I would like to publically thank Jeroen Diederen for patching lxpanel for me
(thus the .1 at the end of the package version) and for showing us the github
repo of lxde-continued.
He has replied at
Package: lxpanel
Version: 0.10.1-4
Followup-For: Bug #1052376
X-Debbugs-Cc: pitsior...@outlook.com
Has anyone tried (or even switched to) another panel? I am currently trying
vala-panel. It is not perfect, e.g. it sometimes crashes and I had to symlink a
lib so as to get the tray area working, but
Package: lxpanel
Version: 0.10.1-4
Followup-For: Bug #1052376
X-Debbugs-Cc: pitsior...@outlook.com
Any chance of merging any of the patches from the other bug report?
Let's say that I can live with the panel being bright (I use numix as gtk
theme)... or with the tooltips that show up on the top of
Package: mps-youtube
Followup-For: Bug #952583
X-Debbugs-Cc: pitsior...@outlook.com
Speaking of progress from upstream, and only 2 days after my comment here, a
new version was released from upstream!
https://github.com/mps-youtube/yewtube/releases/tag/v2.9.4
The project was renamed to yewtube an
Package: gvfs-backends
Version: 1.50.2-1
Followup-For: Bug #1009998
X-Debbugs-Cc: pitsior...@outlook.com
One month since I posted the relavant patch for samba, 2 minor upgrades for
samba and 1 major upgrade for gvfs later and the problem is still there (at
least on my end)!
-- System Information
Package: gvfs-backends
Version: 1.50.1-1
Followup-For: Bug #1009998
X-Debbugs-Cc: pitsior...@outlook.com
So, I was hoping that yesterday's update to 1.50.1 (in testing) would solve the
issue, but nothing changed. Likewise, it was not solved with today's upgrade
for samba (in unstable) to 4.16.1+df
Package: debianutils
Followup-For: Bug #992410
X-Debbugs-Cc: pitsior...@outlook.com
I second to that. It happened on my i686 pc that runs unstable.
As a workaround, one can symlink /usr/bin/run-parts to /bin/run-parts
ln -s /usr/bin/run-parts /bin/run-parts
and network.service comes up as usual.
Source: linux
Followup-For: Bug #989010
X-Debbugs-Cc: pitsior...@gmail.com
Finally a sane reply by someone!
First of all, I do not think that my issue is related to sleep at all. I
mentioned all that in the first post just in case. I know sleep is problematic
in linux, thus I never use it. I also
Package: nvidia-graphics-drivers-legacy-340xx
Followup-For: Bug #973599
X-Debbugs-Cc: pitsior...@gmail.com
I just found out about the removal of nvidia legacy 340xx through reddit and I
admit I had not noticed it all those months.
Since the first days of kernel 5.x in debian, back in mid 2019, I w
Package: pepperflashplugin-nonfree
Version: 1.8.7
Severity: grave
Tags: upstream
Justification: renders package unusable
X-Debbugs-Cc: pitsior...@gmail.com
Dear Maintainer,
Please consider this a followup of #978954, which talks about flash's
deprecation from adobe.
As mentioned in the title, the
Package: lighttpd
Version: 1.4.57-1
Followup-For: Bug #979232
X-Debbugs-Cc: pitsior...@gmail.com
I have that one too! Downgrading media-types to 1.0.1 from testing fixes the
issue, so I am pinning it until the next lighttpd update.
Thank you both.
-- System Information:
Debian Release: bullseye
Package: nvidia-legacy-340xx-driver
Followup-For: Bug #976056
X-Debbugs-Cc: pitsior...@gmail.com
Thank you very much! I promise to do my best to keep the driver in the repo.
-- Package-specific info:
uname -a:
Linux mitsos 5.9.0-4-amd64 #1 SMP Debian 5.9.11-1 (2020-11-27) x86_64 GNU/Linux
/pro
Package: adb
Followup-For: Bug #976007
X-Debbugs-Cc: pitsior...@gmail.com
Now that every single package of android-platform-system-core has reached
testing, the bug has been resolved, so please close this report.
The same applies to #975707.
Thank you.
-- System Information:
Debian Release: bu
Package: nvidia-legacy-340xx-driver
Version: 340.108-8
Followup-For: Bug #976056
X-Debbugs-Cc: pitsior...@gmail.com
First of all, I am really sorry about the annoying logs that spawn under every
message of mine. I am not putting them there on purpose, this is all
reportbug's work. I tried setting
Package: nvidia-legacy-340xx-driver
Version: 340.108-8
Followup-For: Bug #976056
X-Debbugs-Cc: pitsior...@gmail.com
I tried using the patch for 5.9 from aur, with the help of a friend who is
using arch, but dkms failed to build the module
dkms: running auto installation service for kernel 5.9.0-4
Package: adb
Followup-For: Bug #976007
X-Debbugs-Cc: pitsior...@gmail.com
Fixed in v10.x that finally reached unstable earlier for amd64 and i386!
$ adb devices
List of devices attached
ABCDEF1234567890device
The same applies to #975707.
Thank you very much.
-- System Information:
Deb
Package: nvidia-legacy-340xx-driver
Version: 340.108-8
Followup-For: Bug #976056
X-Debbugs-Cc: pitsior...@gmail.com
So, 5.9.11 has just reached testing. Too bad I can not upgrade to it because of
this bug here.
I will wait for 5.10 to reach the repos and hope that a patch will be found by
then.
Package: adb
Version: 1:8.1.0+r23-8
Followup-For: Bug #976007
X-Debbugs-Cc: pitsior...@gmail.com
While we are still waiting for adb 10.x to hit unstable for amd64 or i386,
please merge this with #975707. It is practically the same thing and they have
the same solution.
-- System Information:
De
Package: nvidia-legacy-340xx-driver
Version: 340.108-8
Followup-For: Bug #976056
X-Debbugs-Cc: pitsior...@gmail.com
As it seems, arch builds its kernel with the same parameter disabled, as seen
on line 6528 here
https://github.com/archlinux/svntogit-packages/blob/packages/linux/trunk/config
And y
Package: nvidia-legacy-340xx-driver
Version: 340.108-8
Followup-For: Bug #976056
X-Debbugs-Cc: pitsior...@gmail.com
That is tough! It may also be the end for me on debian, after ~13 years,
because my financial status does not allow a hw upgrade right now. Why is that
kernel parameter so important?
Package: nvidia-legacy-340xx-driver
Version: 340.108-8
Followup-For: Bug #976056
X-Debbugs-Cc: pitsior...@gmail.com
So, this change is/was really needed? What will happen to nvidia 340 now?
One of the reasons I am still on debian is that it still packages it. I can not
find a patch for it so as to
Package: nvidia-legacy-340xx-driver
Version: 340.108-8
Followup-For: Bug #976056
X-Debbugs-Cc: pitsior...@gmail.com
What does this mean for a simple user like me? Is it the end for nvidia 340xx
on debian? I do not want to move to nouveau at all!
-- Package-specific info:
uname -a:
Linux mitsos
Package: adb
Version: 1:8.1.0+r23-8
Followup-For: Bug #976007
X-Debbugs-Cc: pitsior...@gmail.com
As expected, downgrading android-libboringssl to its previous version
(8.1.0+r23-3) makes adb usable again, and fdroidcl too.
$ adb devices
List of devices attached
ABCDEF1234567890device
I a
Package: adb
Version: 1:8.1.0+r23-8
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: pitsior...@gmail.com
Dear Maintainer,
After todays upgrade of android-libboringssl to v10.0.0+r36-1 in testing, adb
completely broke down!
$ adb devices
List of devices attached
* daemon not
Package: nvidia-legacy-340xx-driver
Followup-For: Bug #972430
I just made the update to version -8 and everything works as it should. Thank
you once more :)
-- Package-specific info:
uname -a:
Linux mitsos 5.9.0-1-amd64 #1 SMP Debian 5.9.1-1 (2020-10-17) x86_64 GNU/Linux
/proc/version:
Linux v
Package: nvidia-legacy-340xx-driver
Version: 340.108-7
Followup-For: Bug #972430
Thank you for using the patch I discovered.
Just a heads up. 5.9 has reached testing today and version -8 of nvidia legacy
has not reached unstable yet (at least in the mirror I use).
So, I have put linux-image-amd64
Package: nvidia-legacy-340xx-driver
Version: 340.108-7
Followup-For: Bug #972430
The patches that I posted above are from that aur page. Unfortunately, I do not
know how to test them.
I have noticed that when dkms builds the module, some line like these appear
applying a.patch
applying b.patch
a
Package: nvidia-legacy-340xx-driver
Version: 340.108-7
Followup-For: Bug #972430
I found these 2 patches from aur. In my eyes they seem identical
https://github.com/warpme/minimyth2/blob/master/script/nvidia/nvidia-340.108/files/nvidia-340.108-fix-5.9-kernel-
compile.patch
http://ix.io/2Bbp
And
Package: nvidia-legacy-340xx-driver
Version: 340.108-7
Followup-For: Bug #972430
I just found this, which is for all the nvidia drivers, not just this one.
However, I am pretty sure that 340xx won't be updated since it is eol, so I
hope someone makes a patch for it again.
https://forums.developer
Package: nvidia-legacy-340xx-driver
Version: 340.108-7
Severity: grave
Justification: renders package unusable
Dear Maintainer,
As usual, new kernel in unstable and nvidia 340x fails to build once more. Here
is the log
https://paste.debian.net/1167671/
There is no suitable patch at the moment of
Package: policykit-1
Version: 0.105-26
Followup-For: Bug #965164
Same thing here, on my debian unstable installation.
I did this to "force" dpkg complete the installation, but I do not know if it
is correct
mkdir /usr/lib/policykit-1/
cp /usr/libexec/polkit-agent-helper-1 /usr/lib/policykit-1/po
Package: droopy
Version: 0.20160830-1
Followup-For: Bug #963673
I found this commit on github
https://github.com/goreliu/Droopy/commit/41964791459c7caebe59f5e5ce6d30e78503c82b
which simply removes the 2 instances of "macpath" from the file and makes
droopy work again. I tested it and it does work
Package: droopy
Version: 0.20160830-1
Severity: grave
Tags: upstream
Justification: renders package unusable
Dear maintainer.
I launched droopy earlier to transfer some files, and it failed like so
$ droopy
Traceback (most recent call last):
File "/usr/bin/droopy", line 81, in
import macp
Package: qbittorrent-nox
Version: 4.2.4-1+b1
Followup-For: Bug #962645
You are right! I have set qbittorrent (gui and -nox) to delete the torrents
from its list when they are done on the amd64 system.
I disabled it and it does not crash.
If it is fixed on 4.2.5 from upstream, when can we expect a
Package: qbittorrent-nox
Version: 4.2.4-1+b1
Followup-For: Bug #962645
Yes and no. It now works as it should on my i386 system, but it still fails on
the amd64 one.
The output I get at the terminal is identical to the one I mention above. Also,
the gui version of qbittorrent crashes on the amd64 s
Package: qbittorrent-nox
Followup-For: Bug #962645
Downgrading to 4.2.4-1, the one from last week before the binary update, makes
qbittorrent work as it should, so I assume something went really wrong with
that boost 1.71 build.
-- System Information:
Debian Release: bullseye/sid
APT prefers
Package: qbittorrent-nox
Version: 4.2.4-1+b1
Followup-For: Bug #962645
The same thing happens on the gui version of qbittorrent, at least on amd64!
The torrent is added as usual, it downloads as it should and once it is done,
qbittorrent crashes with the following output
https://paste.debian.net/
Package: qbittorrent-nox
Version: 4.2.4-1+b1
Severity: grave
Justification: renders package unusable
Dear Maintainer,
Qbittorrent-nox has become unusable on both amd64 and i386 since the last
binary update (4.2.4-1 to 4.2.4-1+b1) which was 7 days ago. It worked as it
should before that update, on
Package: nvidia-legacy-340xx-driver
Followup-For: Bug #958446
It works! I noticed that 5.6 reached unstable today, so I tried it asap.
The driver compiles as it should, 3d acceleration works, vdpau works, even the
temperatures work!
Thank you for everything :)
-- Package-specific info:
uname -
Package: nvidia-legacy-340xx-driver
Version: 340.108-4
Followup-For: Bug #958446
Dear Maintainer,
I just got the email that the bug was closed and I got really happy! Then I
checked the report here and I noticed this bit
Closed the wrong bug in the upload ...
And then the reference to #956458,
Package: nvidia-legacy-340xx-driver
Version: 340.108-4
Followup-For: Bug #958446
I know the command I have to run, I just don't know the path to use there. And
last time I patched the file manually, because it was only one file, I wrote
that one line by hand :D
If you show me the way, e.e. the exa
Package: chromium
Version: 81.0.4044.92-1
Severity: grave
Tags: upstream security
Justification: user security hole
Dear Maintainer,
As the title suggests, please update chromium to 81.0.4044.113 (or later),
because it includes a patch for CVE-2020-6457, which is a critical security
issue. More i
Package: nvidia-legacy-340xx-driver
Version: 340.108-4
Severity: grave
Tags: patch
Justification: renders package unusable
Dear Maintainer,
As with my previous bug reports, nvidia legacy 340 fails to build again. Here
is the full log
https://pastebin.com/i5wR0s5V
Here is the patch, again from au
Package: nvidia-legacy-340xx-driver
Followup-For: Bug #956034
Thank you for updating/patching the package so quickly! Everything works great
now.
However, I also get this message in dmesg and I wonder if it is something I
should worry about
[8.473415] resource sanity check: requesting [mem 0
Package: nvidia-legacy-340xx-driver
Version: 340.108-3
Followup-For: Bug #956034
Got it!
Patching was as easy as
patch /usr/src/nvidia-legacy-340xx-340.108/uvm/Makefile < 03-unfuck-
for-5.5.x.patch
and forcing dkms to rebuild it was done with
dkms autoinstall
via the recovery mode. Now I have
Package: nvidia-legacy-340xx-driver
Version: 340.108-3
Severity: grave
Tags: patch
Justification: renders package unusable
Dear Maintainer,
As with my previous bug reports for kernels 5.2 to 5.4, here is a new one for
5.5.
Building it fails like so
https://gist.github.com/pitsi/54af884134b251c237
Package: mps-youtube
Version: 0.2.7.1-2
Severity: grave
Tags: upstream
Justification: renders package unusable
Dear Maintainer,
It seems that google has disabled mps-youtube's api key, so it can no longer
search for videos. Here is the full discussion on the project's github page
https://github.c
Package: nvidia-legacy-340xx-driver
Followup-For: Bug #948195
First of all, thank you for fixing the issue. It is really nice to have a
working nvidia driver again.
Second, I read this in the news file
The 340.xx legacy driver series has been declared as End-of-Life by
NVIDIA. No further upd
Package: nvidia-legacy-340xx-driver
Followup-For: Bug #948195
Well, I had suggested the update to 340.108 on December 27th, at the bottom of
a previous bug report of mine for 340.xx and kernel 5.4 (#946137).
It seems they did update the package a few days later, on new year's eve, but I
did not no
Package: nvidia-legacy-340xx-driver
Followup-For: Bug #948195
I finally managed to install 340.107-8 from the snapshot repo and, as you can
also see in the logs below, there is no issue with it.
I am pinning it for now...
-- Package-specific info:
uname -a:
Linux mitsos 5.4.0-1-amd64 #1 SMP Deb
Package: nvidia-legacy-340xx-driver
Version: 340.108-1
Severity: grave
Justification: renders package unusable
Dear Maintainer,
After todays upgrade to 340.108, the system fails to boot in the desktop
enviroment and dmesg reports a kernel panic, as seen on the paste here
https://paste.debian.net/
Package: ftp.debian.org
Followup-For: Bug #942123
Thank you for removing transmission-remote-cli as I had requested on #900981 1+
year ago.
Is there any chance of packaging tremc or stig now, so as to keep at least one
ncurses-based client for transmission-daemon?
Package: e2fsprogs
Version: 1.44.5-1
Followup-For: Bug #932855
Thank you so much! I can finally access my data :)
-- System Information:
Debian Release: bullseye/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel
Package: e2fsprogs
Version: 1.44.5-1
Followup-For: Bug #932855
Proof that I did install logsave 1 as I said above
# cat var/log/apt/history.log | tail -5
Start-Date: 2019-07-24 09:10:05
Commandline: apt-get install logsave
Requested-By: vaggos (1000)
Install: logsave:i386 (1.45.3-1)
End-Date: 20
Package: e2fsprogs
Version: 1.44.5-1
Followup-For: Bug #932855
I know it will sound like a support question, but please help me.
I have 2 pcs, one with debian unstable i386 and one with debian testing amd64.
Obviously, the first one was hit by that bug earlier today.
Because I have no optical dri
Package: firefox
Version: 67.0-3
Followup-For: Bug #929846
I was expecting 67.0-4 to reach the repos soon, since the bug was closed
earlier today.
Instead, all I got was an upgrade to libnss3 which downgraded it from 3.44 to
3.42.1 as seen in apt's output
Unpacking libnss3:amd64 (2:3.44+really3.4
Package: firefox
Version: 67.0-3
Followup-For: Bug #929846
Upgrading libnss3 to 3.44 of unstable did fix the issue, so please add it as
dependency, like "libnss3 (>= 2:3.44)".
Also, I did not get your suggestion about setting
network.http.spdy.enabled.http2 to false. Is it a security concern?
Obv
Package: megadown
Version: 0~20180705+git83c53dd-1
Severity: grave
Tags: upstream
Justification: renders package unusable
Dear Maintainer,
When trying to download a file from mega, which is the sole reason this script
exists, megadown fails like so
$ megadown
'https://mega.nz/#!3QsG0IDJ!wnEhMRAj
Package: beep
Version: 1.4.3-1
Severity: grave
Tags: upstream
Justification: renders package unusable
Dear Maintainer,
After today's upgrade to version 1.4.x, beep no longer works and pops the above
error. After checking its man page, I found out that it tries to access these
devices, in that spe
Package: firefox
Version: 60.0.2-1
Severity: grave
Justification: renders package unusable
Dear Maintainer,
So, a few days ago, apt autoremoved ffmpeg's libraries (libavcodec57,
libavdevice57, libavfilter6, libavformat57, libavutil55, libswresample2,
libswscale4 and a couple more) because they we
Package: chromium
Version: 67.0.3396.62-1
Followup-For: Bug #900539
How can I help you debugging? For the record, I use dmo's libav* libs, but they
are still build against ffmpeg 3.4.x.
-- System Information:
Debian Release: buster/sid
APT prefers testing
APT policy: (990, 'testing'), (500,
Package: chromium
Version: 67.0.3396.62-1
Followup-For: Bug #900533
Dear Maintainer,
Is there any info on when this issue could be fixed? It has been a week since
this bug report was opened and there are no official comments here regarding
any progress, neither some newer source package suggestin
Package: qbittorrent
Followup-For: Bug #880229
I am using qbittorrent 3.3.15, I am having /tmp in ram (tmpfs) and what you
mention does not happen. I also have all my browsers' caches inside /tmp as
well (/tmp/cache) and I do keep at least one browser open all the time.
More specifically. This is
Package: thunderbird
Followup-For: Bug #871629
Count me in as well, using debian testing. I had to downgrade to 52.2.1-4 to
get it back to work.
-- System Information:
Debian Release: buster/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental')
Archite
Package: thunderbird
Version: 1:45.7.1-2
Followup-For: Bug #857029
To the ones that removed the comment parts and made it work again. Can you
please write a patch for it or paste the corrected file in pastebin?
I removed the comment parts but the message shows up again.
And please merge it with b
75 matches
Mail list logo
