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
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,
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
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
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,
Package: nvidia-legacy-340xx-driver
Followup-For: Bug #1029681
X-Debbugs-Cc: pitsior...@outlook.com
The ts contacted me and said that the symlink does not work.
Since last time, we had another, bigger flood that caused even more damage, and
I do not know if I will have the gt210 by Christmas so
Package: lxappearance
Followup-For: Bug #1052210
X-Debbugs-Cc: pitsior...@outlook.com
Lxde (= the package) is just a metapackage which installs all the relevant
packages for lxde (= the desktop enviroment), lxappearance and lxappearance-
obconf included.
So, don't worry if it gets removed, it is
Package: lxappearance
Followup-For: Bug #1052210
X-Debbugs-Cc: pitsior...@outlook.com
@10dmar10
Do you have lxapperance-obconf installed too? If yes, have you tried removing
it?
And if possible, please open a new bug report there, with grave severity. The
patch is already available, so it won't
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
Package: lxappearance
Followup-For: Bug #1052210
X-Debbugs-Cc: pitsior...@outlook.com
If anyone is interested to patch lxappearance-obconf, there is this patch in
its github page which fixes the segfault in gtk3.
https://github.com/lxde/lxappearance-
Package: lxappearance
Version: 0.6.3-4
Followup-For: Bug #1052210
X-Debbugs-Cc: pitsior...@outlook.com
Same thing here, the -4 update did not fix the app for me as well. I do not
have gdb installed and I have no idea how to debug something, thus no gdb
output from me.
dmesg output
[ 284.595381]
Package: nvidia-legacy-340xx-driver
Followup-For: Bug #1029681
X-Debbugs-Cc: pitsior...@outlook.com
First and foremost, sorry for not replying earlier and for not testing the glx
symlink as proposed. The storms, the floods and the power outages that happened
here the first days of September
Package: lxappearance
Version: 0.6.3-3
Followup-For: Bug #1052210
X-Debbugs-Cc: pitsior...@outlook.com
Until the patch is applied in debian's package too, can someone raise this to
grave, please? It does render the package unusable after all and I really wish
apt-listbugs would catch it and
Package: rxvt-unicode
Version: 9.31-1
Followup-For: Bug #996815
X-Debbugs-Cc: pitsior...@outlook.com
I think it is time to close this. Fontconfig's update to 2.14.2 on August 16th
(that is when it reached testing) made urxvt's font spacing return to normal,
so the letterspace parameter in
Package: nvidia-legacy-340xx-driver
Version: 340.108-19
Followup-For: Bug #1029681
X-Debbugs-Cc: pitsior...@outlook.com
Last century's? The tesla (nv50) family was release near the end of the 2010's
decade and it, luckily, had full support by nvidia until the end of 2019! And
since then, it is
Package: nvidia-legacy-340xx-driver
Version: 340.108-19
Followup-For: Bug #1029681
X-Debbugs-Cc: pitsior...@outlook.com
Kodi, with today's release of 20.2, fixed the gl library issue with this commit
here
https://github.com/xbmc/xbmc/pull/23226
In other news, a few days ago, qbittorrent became
Package: nvidia-legacy-340xx-driver
Version: 340.108-18
Followup-For: Bug #1029681
X-Debbugs-Cc: pitsior...@outlook.com
Honest question to the maintainers, and to the qt5 maintainers too:
What if someone wants to install/run a package that explicitly depends on
libqt5gui5?
I wanted to try
Package: nvidia-legacy-340xx-driver
Version: 340.108-18
Followup-For: Bug #1029681
X-Debbugs-Cc: pitsior...@outlook.com
I contacted an arch user who still uses nvidia 340 from aur and, as he mentions
in the comments, there is no issue with qt5 apps and nvidia 340 there.
I do not know how arch
Package: firefox-esr
Followup-For: Bug #1032983
X-Debbugs-Cc: pitsior...@outlook.com
The same thing applies to thunderbird 102.9.0 that reached the repo yesterday.
Broken tls support there means no email can be sent or received and rss feeds
do not work.
I also have an ms exchange calendar in tb,
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
Package: nvidia-legacy-340xx-driver
Version: 340.108-17
Followup-For: Bug #1029681
X-Debbugs-Cc: pitsior...@outlook.com
Thank you for the clarifications. No offence, but as you described it, this is
practically "planned obsolescence in the opensouce world". Ok, the 340 driver
is old and it does
Package: nvidia-legacy-340xx-driver
Version: 340.108-17
Followup-For: Bug #1029681
X-Debbugs-Cc: pitsior...@outlook.com
Some manjaro user from github found a solution for kodi v20. Launching it like
so makes it work, so this probably means that kodi v20, unlike v19, does not
detect the library
Package: nvidia-legacy-340xx-driver
Version: 340.108-17
Followup-For: Bug #1029681
X-Debbugs-Cc: pitsior...@outlook.com
Please excuse me if I have already said anything of the following and I am now
repeating myself. I have so much in my mind that sometimes I forget what I said
a couple of days
Package: nvidia-legacy-340xx-driver
Version: 340.108-17
Followup-For: Bug #1029681
X-Debbugs-Cc: pitsior...@outlook.com
According to these reports that come from ubuntu, mint and arch, kodi 20 has
the same issue with the nvidia 340 driver, regardless of kernel and xorg
version. Thus, I think it
Package: nvidia-legacy-340xx-driver
Version: 340.108-17
Followup-For: Bug #1029681
X-Debbugs-Cc: pitsior...@outlook.com
Sorry but no, I can not trace it to something specific. Everything was working
fine on 6.0 and -16, but they are like 2 months old now. I have very few qt
apps and I rarely use
Package: nvidia-legacy-340xx-driver
Version: 340.108-17
Followup-For: Bug #1029681
X-Debbugs-Cc: pitsior...@outlook.com
Ok I just did it, but nothing changed. In detail:
- I installed -16 from snapshot
- I let dkms fail to build the driver and apt/dpkg with its failed exit status
- I moved the
Package: nvidia-legacy-340xx-driver
Version: 340.108-17
Followup-For: Bug #1029681
X-Debbugs-Cc: pitsior...@outlook.com
Please help me on that...
I have already backed up the patch file on my dekstop. If I install -16 from
snapshot.d.o, dkms will rebuild the driver right after apt installs it and
Package: nvidia-legacy-340xx-driver
Version: 340.108-17
Followup-For: Bug #1029681
X-Debbugs-Cc: pitsior...@outlook.com
First of all, the title should be "gl related apps fail to launch" and let me
explain why.
I tried libreelec 11 beta 1 which came out a few days ago. It uses kernel 6.1,
nvidia
Package: nvidia-legacy-340xx-driver
Version: 340.108-17
Followup-For: Bug #1029681
X-Debbugs-Cc: pitsior...@outlook.com
How can I install 6.0 alongside -16 to test if it works with qt5 5.15.8 and
kodi 20? Installing 6.0 is easy, installing -16 is easy too. The problem is
that when I install -16,
Package: nvidia-legacy-340xx-driver
Version: 340.108-17
Followup-For: Bug #1029681
X-Debbugs-Cc: pitsior...@outlook.com
Goodmorning. Before I start, I would like to say that yesterday I completely
missed message #27 above and that I am really sorry for that useless wall of
text that reportbug
Package: nvidia-legacy-340xx-driver
Version: 340.108-17
Followup-For: Bug #1029681
X-Debbugs-Cc: pitsior...@outlook.com
Thank you for all that info.
Please allow me to check the -dbgsym packages and post a new strace the
following days. It is something new for me and I will probably make a mess
Package: gcolor3
Version: 2.4.0-2
Followup-For: Bug #1018895
X-Debbugs-Cc: pitsior...@outlook.com
Thank you for verifying it on gnome. I can't see the benefit of installing the
remaining xdg-desktop-portal packages. For instance, the one for kde wants to
install a ton of kde packages and the wlr
Package: gcolor3
Version: 2.4.0-2
Followup-For: Bug #1018895
X-Debbugs-Cc: pitsior...@outlook.com
This bug affects me as well. I am on openbox under x11 and the packages xdg-
desktop-portal and xdg-desktop-portal-gtk (as suggested elsewhere) were already
installed on my end.
I have also installed
Package: samba
Followup-For: Bug #1009998
X-Debbugs-Cc: pitsior...@outlook.com
The 4.16.2 upgrade reached testing a moment ago, so I tested my filemanager
(pcmanfm, gtk version) for the issue. It can connect to
smb://host/sharename (or smb://ip/sharename)
but not to
smb://host (or smb://ip)
Source: gvfs
Followup-For: Bug #1009998
X-Debbugs-Cc: pitsior...@outlook.com
You are right about that. However, the bug is a problem of gvfs that does not
work with samba 4.16 and not the other way round, because smbclient works as it
should. I am still expecting an upstream patch or an upgrade
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
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
Package: firefox
Version: 96.0.3-1
Followup-For: Bug #1006616
X-Debbugs-Cc: pitsior...@outlook.com
Dear Maintainer,
First of all, I know that firefox 97 requires rustc, cargo and nss to build.
How about updating those 3 and building firefox 97+ for the experimental repo?
It is not just to get
Source: linux
Followup-For: Bug #989010
X-Debbugs-Cc: pitsior...@outlook.com
Preface: In case I did not mention it above, I had a suspicion that the issue
might be related to cpu frequency scaling.
1+ month has passed with 5.15. The blank screen issue appeared a few more times
the following
Source: linux
Followup-For: Bug #989010
X-Debbugs-Cc: pitsior...@outlook.com
And it just happened again, on the very first boot of the day, as if nothing
has changed since May. I was right for not upgrading past 5.10.28 all those
months.
-- System Information:
Debian Release: bookworm/sid
APT
Package: thunderbird
Version: 1:91.0~b5-1
Followup-For: Bug #992216
X-Debbugs-Cc: pitsior...@outlook.com
Although I agree with what you say about security, please consider uploading
v91 to experimental, like you already do for firefox-esr. For anyone that is on
91b5, the upgrade to v91 as stable
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
Source: linux
Followup-For: Bug #989010
X-Debbugs-Cc: pitsior...@gmail.com
One thing I noticed this weekend.
Time it took for 5.10.38/40 to reach testing from unstable: 7 days, despite
this awful bug here.
Time it took for 5.10.46 to reach testing from unstable: 20+ days and still
counting.
Package: thunderbird
Version: 1:90.0~b2-1
Followup-For: Bug #990631
X-Debbugs-Cc: pitsior...@gmail.com
One minor update. My friend, the arch user, built thunderbird beta (91b1 as of
yesterday) from source and he reports that the blank preferences issue is now
gone there.
So, please package 91b1
Package: thunderbird
Version: 1:90.0~b2-1
Followup-For: Bug #990631
X-Debbugs-Cc: pitsior...@gmail.com
Any chance of fixing this? I found the reason for the egl errors (it's
webrender that is being forced by default). But there is no way to access
about:config and disable it, because it has to be
Source: linux
Followup-For: Bug #989010
X-Debbugs-Cc: pitsior...@gmail.com
There are 2 words that can completely justify my "appaling lack of respect for
debian developers": hardware failure. And it happened not once, but twice.
Plus, the support I received from here is non existant in every
Package: thunderbird
Version: 1:90.0~b2-1
Followup-For: Bug #990631
X-Debbugs-Cc: pitsior...@gmail.com
First things first, I missed message #20. It seems that the errors on the
terminal are identical for ff 89 and tb 90b2 and, imho, irrelevant to the
preferences tab issue.
I do think nvidia is
Package: thunderbird
Version: 1:90.0~b2-1
Followup-For: Bug #990631
X-Debbugs-Cc: pitsior...@gmail.com
So, a friend lended me his vm with debian unstable + gnome. Gnome defaults to
wayland, but it can be configured to run on xorg too. Selecting either session
(gnome or gnome on xorg) makes no
Package: thunderbird
Version: 1:90.0~b2-1
Followup-For: Bug #990631
X-Debbugs-Cc: pitsior...@gmail.com
You are right about nvidia, but I do not use wayland... And I probably won't be
using it until it becomes as stable as xorg. Also, my card supports up to
opengl 3.3, if this is the case.
I
Package: thunderbird
Version: 1:90.0~b2-1
Severity: important
X-Debbugs-Cc: pitsior...@gmail.com
Dear Maintainer,
I upgraded to 90b2 (from 78.11) a few minutes ago, because I really wanted to
see if tb has adopted that proton redesign ff 89 introduced. It hasn't (yet).
And I noticed that every
Source: linux
Followup-For: Bug #989010
X-Debbugs-Cc: pitsior...@gmail.com
I noticed that 5.10.46 reached unstable yesterday. If it was not for this
issue, I would have already upgraded, like I udually do when a kernel upgrade
comes out.
However, this time I had to check the config file for that
Source: linux
Followup-For: Bug #989010
X-Debbugs-Cc: pitsior...@gmail.com
Finally, a sane reply that does not blame nvidia's driver.
I have written above that something must have changed, at least regarding intel
hw, because I was missing the coretemp readings on my conky. However, from the
Source: linux
Followup-For: Bug #989010
X-Debbugs-Cc: pitsior...@gmail.com
One more week passed with no issues. That's how things are when a kernel works
as it should and the gpu driver is flawless. Stability that matches the one of
a really stable distro or the one of windows 7.
As I expected,
Source: linux
Followup-For: Bug #989010
X-Debbugs-Cc: pitsior...@gmail.com
About the logs. Did anyone of you reply to my question "where can I find those
logs?" and I missed it? All I have found, again BY MYSELF, is this file here
that when I run cat on it, gibberish shows up in the terminal. I
Source: linux
Followup-For: Bug #989010
X-Debbugs-Cc: pitsior...@gmail.com
To no surprise, the severity was lowered again. Without a single suggestion or
reason, again.
Imho, that is the usual incompetence most devs here show, so I am not
surprised. It's a real shame however for a distro this
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
Source: linux
Followup-For: Bug #989010
X-Debbugs-Cc: pitsior...@gmail.com
Control: severity -1 critical
Now that I have your attention, because raising the severity is the only way to
get an answer here, let me begin.
I noticed that this mess of a kernel reached testing today. As it seems, its
Source: linux
Followup-For: Bug #989010
X-Debbugs-Cc: pitsior...@gmail.com
I came accross these 2 threads on r/debian and I am now thinking that my
problem too may not be related to debian packaging/patching/configuration but
to some upstream flaw(s) of 5.10.
The guy in the second thread has done
Source: linux
Followup-For: Bug #989010
X-Debbugs-Cc: pitsior...@gmail.com
How would YOU feel if a system upgrade destroyed an (old yet) perfectly working
piece of important hardware? What if it destroyed another piece of similar
hardware a few days later?
How would you feel if all those days you
Control: severity -1 critical
Source: linux
Followup-For: Bug #989010
X-Debbugs-Cc: pitsior...@gmail.com
I borrowed an old pc from a friend to test those 2 gpus. NONE of them reached
the post, which means they are damaged now. Moreover, when the ati was
connected, the system was beeping as if it had no vga on.
Thank you
Source: linux
Followup-For: Bug #989010
X-Debbugs-Cc: pitsior...@gmail.com
One thing I forgot last time. The ati card was fucked up AFTER it ran on
5.10.40 for a couple of boots. I installed it because I wanted to check if it
works any better there (scrolling is laggy on all browsers).
Do you
Source: linux
Followup-For: Bug #989010
X-Debbugs-Cc: pitsior...@gmail.com
And the same thing happened again today, with the ati card this time! I logged
in via ssh and, like with nvidia and nouveaum radeon was not found in lsmod. I
then checked lspci and the entire vga part was not there, as if
Source: linux
Followup-For: Bug #989010
X-Debbugs-Cc: pitsior...@gmail.com
I never thought I would say that, but radeon's capabilities are inferior even
to nvidia's legacy driver.
It has been a few hours now and I am still struggling to get vaapi working on
mpv and mplayer. 2d acceleration is
Source: linux
Version: linux-image-5.10.0-7-amd64
Followup-For: Bug #989010
X-Debbugs-Cc: pitsior...@gmail.com
Impending rant, because I think it is indeed a hardware failure that was caused
from the kernel upgrade.
I successfully downgraded linux-compiler-gcc-10-x86 and linux-kbuild-5.10 to
Source: linux
Version: linux-image-5.10.0-7-amd64
Followup-For: Bug #989010
X-Debbugs-Cc: pitsior...@gmail.com
Can I somehow determine that the button does run systemctl poweroff and not
sleep when I press it? All I can see in the shutdown messages, for that split
second they appear, is just the
Source: linux
Followup-For: Bug #989010
X-Debbugs-Cc: pitsior...@gmail.com
First of all, I removed 5.10.38 because I want grub to directly boot to the
working kernel without me having to select it via grub's advanced menu.
Yes, nvidia (340 legacy) is the reason the tainted message pops up. To be
Package: src:linux
Version: 5.10.38-1
Severity: important
X-Debbugs-Cc: pitsior...@gmail.com
Preface.
I have disabled sleep, hibernate etc via systemd as you can see below.
$ systemctl status sleep.target suspend.target hibernate.target hybrid-
sleep.target
● sleep.target
Loaded: masked
Package: onedrive
Version: 2.4.10-1
Severity: normal
Tags: upstream
X-Debbugs-Cc: pitsior...@gmail.com
Dear Maintainer,
As the title suggests, please update to the latest version (2.4.11 at the time
of writing). I am having a serious issue with 502 and 504 errors when using the
app. I have
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
Package: upnp-router-control
Version: 0.2-1.2+b1
Followup-For: Bug #985951
X-Debbugs-Cc: pitsior...@gmail.com
Thank you for the clarification and the quick response. Feel free to close this
bug now.
Package: upnp-router-control
Version: 0.2-1.2+b1
Severity: minor
Tags: upstream
X-Debbugs-Cc: pitsior...@gmail.com
Dear Maintainer,
Earlier, I noticed that upnp-router-control was removed from the repo 1+ year
ago. I had installed it a couple of years ago in order to troubleshoot some
connection
Package: hddtemp
Version: 0.3-beta15-54
Followup-For: Bug #981462
X-Debbugs-Cc: pitsior...@gmail.com
I second to the above. If it helps, this is the systemd service file that arch
provides
https://github.com/archlinux/svntogit-
packages/blob/packages/hddtemp/trunk/service
-- System Information:
Package: webfs
Severity: normal
X-Debbugs-Cc: pitsior...@gmail.com
On every boot, this message shows up in dmesg stating the obvious
[ 16.606515] systemd-sysv-generator[153]: SysV service '/etc/init.d/webfs'
lacks a native systemd unit file. Automatically generating a unit file for
Package: inadyn
Followup-For: Bug #983309
X-Debbugs-Cc: pitsior...@gmail.com
There is a systemd service file available from upstream!
https://github.com/troglobit/inadyn/blob/5f7ef01e2b5597c02e15c0001a9a250f0356d774/inadyn.service.in
Package: inadyn
Severity: normal
X-Debbugs-Cc: pitsior...@gmail.com
Although I have no hopes for this getting fixed, because the package seems
unmaintained for the last ~8 years, here goes.
On every boot, this message shows up in dmesg stating the obvious
systemd-sysv-generator[153]: SysV
Package: chromium
Followup-For: Bug #982062
X-Debbugs-Cc: pitsior...@gmail.com
So, in your opinion, a browser is useful only for rendering pages? Nowadays,
web technologies have evolved and web pages are not static html. Sites are
complex and the ability for someone to sync
Package: firefox
Followup-For: Bug #981809
X-Debbugs-Cc: pitsior...@gmail.com
Fixed after today's upgrade to 85.0.1. It was probably built with the same
cargo version as the previous ones.
-- Package-specific info:
-- Extensions information
Name: Amazon.co.uk
Location:
Package: chromium
Severity: important
Tags: upstream
X-Debbugs-Cc: pitsior...@gmail.com
~20 days ago, google announced that they are limiting api availability on March
15th 2021.
https://blog.chromium.org/2021/01/limiting-private-api-availability-in.html
This means that sync and some other
Package: firefox
Version: 84.0.2-1
Followup-For: Bug #981809
X-Debbugs-Cc: pitsior...@gmail.com
I just read in r/debian that ff 85 needs a newer version of cargo.
Guess we are now waiting for it...
-- Package-specific info:
-- Extensions information
Name: Amazon.co.uk
Location:
Package: firefox
Version: 84.0.2-1
Severity: normal
X-Debbugs-Cc: pitsior...@gmail.com
Dear Maintainer,
Firefox 85 was released (from upstream) more than a week ago and its source
package reached the repo just a day later. However, the binary package is still
nowhere to be found. It is not even
Package: apt
Version: 2.1.18
Severity: normal
X-Debbugs-Cc: pitsior...@gmail.com
Dear Maintainer,
It must be the 4th or 5th time that I notice the following behavior, so I
report it today.
I do this to update my system
apt-get update && apt-get upgrade && apt-get dist-upgrade
The update part
Package: libpam-runtime
Version: 1.4.0-2
Severity: normal
X-Debbugs-Cc: pitsior...@gmail.com
Dear Maintainer,
After today's upgrade to 1.4.0 in testing, I get this message everytime I run
su
$ su
Password:
Warning: your password will expire in 32632 days.
And the number changes everytime, but
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,
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:
is a
dependency of python3-reportbug. It is that simple.
Thank you in advance and happy new year :)
-- Package-specific info:
** Environment settings:
INTERFACE="gtk"
** /home/jim/.reportbugrc:
reportbug_version "7.8.0"
mode standard
ui gtk
realname "jim_p"
email &qu
Package: gcc-10
Followup-For: Bug #973785
X-Debbugs-Cc: pitsior...@gmail.com
Solved after today's update to 10.2.1-3. You can close this bug report.
-- System Information:
Debian Release: bullseye/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental')
Package: python3-reportbug
Version: 7.8.0
Followup-For: Bug #975398
X-Debbugs-Cc: pitsior...@gmail.com
When shall we expect the updated version to reach the repos?
Obviously, reportbug stopped working properly for me too and I (well... a
friend of mine) had to apply the forementioned patch to get
Package: midori
Severity: normal
Tags: upstream
X-Debbugs-Cc: pitsior...@gmail.com
Dear Maintainer,
Leaving aside that midori in debian completely missed versions 8 and 9,
although they were both released in 2019 from upstream, TIL that a lot has
changed in midori since 2019.
First, it is now
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
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:
Package: obsession
Version: 20140608-2+b1
Followup-For: Bug #976632
X-Debbugs-Cc: pitsior...@gmail.com
Well, I use it alongside fbpanel, which was removed from testing due to some
ftbfs issue with gcc10.
I plan to replace it with lxpanel, which has some built in function for a
shutdown "menu"...
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: obsession
Version: 20140608-2+b1
Severity: normal
Tags: upstream
X-Debbugs-Cc: pitsior...@gmail.com
As it seems, the project is dead. The link to bitbucket leads to a 404. Plus
its developer* has probably moved to github and obsession is not among the
things he currently maintains.
So,
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
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:
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.
1 - 100 of 237 matches
Mail list logo
