Control: retitle -1 firmware-iwlwifi: Please update to newest kernel version
Hi there,
any updates on this bug on when the new version will be uploaded?
Regards
Hi all,
>> No. Without a package as an argument it won't.
Thanks! You're right. Let me write it down here again:
- "apt upgrade" (no argument) will never remove a package, only upgrade
or install
- "apt upgrade pkg_name" will remove, upgrade or install the required
package to
Hi all,
>> (modifiers btw is not a good word. I guess it was never documented so
far partly as this is a rather advanced feature and mainly because naming
things is hard)
yes, we brought it up in our conversation but I agree it was not directly
related to the subject as it was an apt advanced
Hi there,
> If "apt upgrade" is saying that it removes packages, that is a bug, yes.
@david: it is not a bug, apparently.
To put everything in a nutshell:
- "apt upgrade" can remove packages
- "apt upgrade" accepts specific packages to be upgraded
Therefore, this behaviour is expected
Control: retitle -1 apt upgrade : it removes packages when it shouldn't.
which I don't really recommend for the reasons stated above).
Anyway, I think some clarification is needed from the developers to shed
some light on this.
Regards
On Tue, Mar 12, 2024 at 3:12 AM Wesley Schwengle
wrote:
> On Mon, Mar 11, 2024 at 11:32:24PM +0100, Miguel Angel Rojas wrote:
> > > I
> I see. It looks like `apt upgrade ' behaves as `apt install
> '. Which (to me) is unexpected behaviour, as the man page is
quite
>clear on its behaviour (man 8 apt-get):
Well, clearly it shouldn’t. To begin with, “apt install” should mark a
package as manual installed while “apt upgrade”
u requested.
Regards
On Mon, Mar 11, 2024 at 5:44 PM Wesley Schwengle
wrote:
>
> Hi Miguel,
>
> On Mon, Mar 11, 2024 at 05:09:47PM +0100, Miguel Angel Rojas wrote:
> > > I do not know, at times I'm also wondering why it doesn't do it, but I
> > didn't
> > >
settled
down. I have a feeling that it is the same bug but there is no way to probe
it with this transition going on.
Regards
On Mon, Mar 11, 2024 at 3:04 PM Wesley Schwengle
wrote:
>
> Hello Miguel,
>
> On Mon, Mar 11, 2024 at 09:50:12AM +0100, Miguel Angel Rojas wrote:
>
> &
Hi Wesley,
>This problem isn't because of apt, the problem is that gdb-minimal/gdb
> dependencies cannot be satified. A full-upgrade is the equivalent of a
> dist-upgrade which will remove packages to resolve the dependencies. The
> problem you are facing is the t64 transition[1][2] where not
looks like success.
And yes, wifi is working fine although I haven't properly done any
performance test yet.
Regards
On Sun, Feb 11, 2024 at 4:15 PM Diederik de Haas
wrote:
> Hi Miguel,
>
> On Sunday, 11 February 2024 16:03:20 CET Miguel A. Rojas wrote:
> > I forgot to
Hi Diederik,
I forgot to include you the dmesg as promised:
[ 2.235947] iwlwifi :00:14.3: enabling device ( -> 0002)
[ 2.237778] iwlwifi :00:14.3: Detected crf-id 0x1300504, cnv-id
0x80401 wfpm id 0x8030
[ 2.237805] iwlwifi :00:14.3: PCI dev 7a70/0074, rev=0x430,
.
Thanks!
On Fri, Feb 9, 2024 at 7:48 PM Diederik de Haas
wrote:
> Control: tag -1 moreinfo
>
> Hi,
>
> On Friday, 9 February 2024 19:35:01 CET Miguel A. Rojas wrote:
> > A few days ago, I went to
> >
> https://git.kernel.org/pub/scm/linux/kernel/git/firmware/lin
Hi Diederik,
A few days ago, I went to
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git
and update the missing loaded modules.
Indeed, I noticed that I have another messages related to the iwlwifi
module: "kernel: iwlwifi :00:14.3: firmware: failed to load
found 966218 linux/6.5.6-1
found 966218 firmware-iwlwifi/20230515-3
Bug still running around ;)
regards
Hi there,
I think this could be related to the fact that current kernel packages
naming convention don't match the regular expression in
/etc/apt/apt.conf.d/01autoremove.
There are some '.' that the regular expression doesn't take care of.
NeverAutoRemove
{
"^firmware-linux.*";
9/23 12:55, Alexis Murzeau wrote:
Hi,
On Sat, 16 Sep 2023 00:55:12 +0200 Miguel Angel Rojas
wrote:
Hi there,
Downgrading the following packages:
- sddm-themes-breeze
- sddm-theme-debian-breeze
to version 4:5.27.7-2 makes sddm fully usable again with no issues.
It seems some changes have
Hi there,
Downgrading the following packages:
- sddm-themes-breeze
- sddm-theme-debian-breeze
to version 4:5.27.7-2 makes sddm fully usable again with no issues.
It seems some changes have been made on version 4:5.27.8-1 that have broken
sddm.
I hope this helps.
Regards
Hi there,
I can confirm the bug is there. Libraries are not found and NVIDIA driver
fails to build.
Regards
Hi all,
It seems the problem is fixed with the new release (418.88)
Thanks
On Tue, Aug 13, 2019 at 12:42 AM Debian Bug Tracking System <
ow...@bugs.debian.org> wrote:
> Thank you for filing a new Bug report with Debian.
>
> You can follow progress on this Bug here: 934648:
>
On 10/21/2015 12:22 AM, Luca Boccassi wrote:
Hi Miguel,
The reason I'm asking is because I can't reproduce any problems on GDM,
with any software that uses GLX or other libraries, after adding the
workaround.
But I noticed something looking again at the system info you forwarded,
the only user
>
>
> I must first say that I am absolutely not familiar with KDE, the QT
> environment and how it works. But the thread that raises the abort
> doesn't look like it's in the GL libraries code:
>
> Maybe there's some context I'm missing. Forgive me for asking, but are
> you sure this is due to the
Hi Luca,
Here you have the report you asked about the plasmashell. I do not know if
it could be related to a configuration issue, but again very easy to
reproduce. Here you have 2 reports (same error in 2 consecutive log on
sessions).
These crashes are related to the plasmashell (I manually
Hi Luca,
Thanks for the quick answer!
Here you have both report you asked for. Hopefully it will help us to know
where the issue is.
Regards
On Sun, Oct 18, 2015 at 9:43 PM, Luca Boccassi <luca.bocca...@gmail.com>
wrote:
> On Sun, 2015-10-18 at 20:16 +0200, Miguel Angel Rojas wrot
Hi all,
Vladimir is right, same issue here. Indeed, It is weird to me not so many
people is currently reporting on it, but it is affecting a lot of programs.
Something happens when upgrading to version 0.6.x (I agree at this point)
plasma-desktop is also unable to start and panic (black
:39 PM, Michael Biebl bi...@debian.org wrote:
On 18.11.2012 13:29, Miguel A. Rojas wrote:
# The primary network interface
allow-hotplug eth0
iface eth0 inet static
address 192.168.2.2
netmask 255.255.255.0
network 192.168.2.0
broadcast 192.168.2.255
Hi Michael,
You're right. This is not the default route but it seems my DNS
servers are pointing to the my router (DHCP default configuration in my
router); therefore I cannot resolve DNS entries because these DNS
packages are going through eth0 (eth0 route entry is before wlan one,
Hi Anton,
I see you point. I am not an expert on this but here are my thoughts:
- If ckbcomp could not be called at boot time... why this is inside in
/bin/setupcon (which is called at boot time)? Same idea for the other
binaries you mentioned
- How is the preliminary keymap
Package: gally
Version: 0.5.1-1
Severity: grave
Justification: renders package unusable
-- System Information:
Debian Release: wheezy/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.32-5-amd64 (SMP w/2 CPU cores)
Locale:
Package: libopenipmi0
Version: 2.0.16-1.1
Severity: grave
# aptitude install libopenipmi0
Reading package lists... Done
Building dependency tree
Reading state information... Done
Reading extended state information... Done
Initializing package states... Done
Reading task descriptions... Done
The
Ablassmeier a...@grinser.de wrote:
tags 513142 + unreproducible
thanks
hi Miguel,
On Mon, Jan 26, 2009 at 09:34:26PM +0100, Miguel A. Rojas wrote:
Configuring zabbix-frontend-php (1:1.6.2-2) ...
dbconfig-common: writing config to
/etc/dbconfig-common/zabbix-frontend-php.conf
*** WARNING
Hi,
It is confirmed that variable parameters we are using are not the one
zabbix are using right now. The reason why DB_* vars are still working is
for compatibility reason for older versions. Here you have the link:
http://www.zabbix.com/forum/showthread.php?t=11593
Michael, do
Thanks for the quick response. I didn't have enough time to test the
package but one of the zabbix developers
has posted an example of the zabbix.conf.php file.
It seems that Debian configuration file is quite different from the
current one that zabbix generates:
I've just tested the package and it seems there is something wrong:
Configuring zabbix-frontend-php (1:1.6.2-2) ...
dbconfig-common: writing config to
/etc/dbconfig-common/zabbix-frontend-php.conf
*** WARNING: ucf was run from a maintainer script that uses debconf, but
the
Package: zabbix-frontend-php
Version: 1:1.6.2-2
Severity: normal
You will receive the following error when 1.6.2-2 is installing:
Configuring zabbix-frontend-php (1:1.6.2-2) ...
dbconfig-common: writing config to
/etc/dbconfig-common/zabbix-frontend-php.conf
*** WARNING: ucf was run from a
Package: zabbix-frontend-php
Version: 1:1.6.2-1
Severity: important
You will receive the following error when trying to execute scripts
through maps:
socket_connect() [a
href='function.socket-connect'function.socket-connect/a]: Host lookup
failed [-10001]: Unknown
36 matches
Mail list logo
