On 25/01/2024 20:42, Henning Follmann wrote:
The issue is a usb hub. Somehow GNOME thinks this hub is a mouse.
Try
lsusb --verbose --tree
perhaps somebody plugged in a tiny receiver for a wireless mouse and
forgot about it.
On Wed, Jan 24, 2024 at 03:30:23PM -0500, Henning Follmann wrote:
> Hello,
> for a while I am using
>
> gsettings set org.gnome.desktop.peripherals.touchpad send-events
> 'disabled-on-external-mouse'
>
> which really worked fine.
>
> But since last week this does not work anymore; in the way th
Hello,
for a while I am using
gsettings set org.gnome.desktop.peripherals.touchpad send-events
'disabled-on-external-mouse'
which really worked fine.
But since last week this does not work anymore; in the way that the
trackpad is always disabled, even when the mouse is not connected.
I have to
On 2024-01-20 08:44 +0100, Sven Joachim wrote:
> On 2024-01-20 00:20 +0100, ju...@op.pl wrote:
>
>> I'm not sure if this is actually a bug in the mc package or maybe
>> somewhere in sshd or in some library that uses ssh. That's why I
>> didn't report
On 2024-01-20 00:20 +0100, ju...@op.pl wrote:
> I'm not sure if this is actually a bug in the mc package or maybe
> somewhere in sshd or in some library that uses ssh. That's why I
> didn't report it via reportbug. Anyway, I noticed the effects only in
> Shell Link
On Sat, Jan 20, 2024 at 12:20:55AM +0100, ju...@op.pl wrote:
> I'm not sure if this is actually a bug in the mc package or maybe somewhere
> in sshd or in some library that uses ssh. That's why I didn't report it via
> reportbug. Anyway, I noticed the effects only in Shel
I'm not sure if this is actually a bug in the mc package or maybe somewhere in
sshd or in some library that uses ssh. That's why I didn't report it via
reportbug. Anyway, I noticed the effects only in Shell Link in mc. SSH in the
terminal works fine. FTP Link in mc also works pr
gt; version info as Gareth posted). The one you mentioned was being tracked
>> in [2] and the corresponding Debian bug is [3]. My guess is that as
>> zfs-linux is not in "main" but "contrib", and the issue is marked
>> "no-dsa" (see [4]), there may b
On Sat 13/01/2024 at 02:32, Gareth Evans wrote:
> use of the actual "stable-backports" repo is not
> recommended or implied.
"implied" might be debatable given that was indeed my first thought, but not
intended to be implied, it seems. Certainly not necessary.
On Fri 12/01/2024 at 06:49, Jan Ingvoldstad wrote:
> ...
> It is far more concerning that one cannot trust that cp actually copies a
> file, and this is a blocker for installing the ZFS packages in Debian.
The update in bookworm-backports to 2.2.2-3 allegedly fixes this issue.
I have installed
-linux[1] on which the "action
>> needed" section has information about security issues (along with
>> version info as Gareth posted). The one you mentioned was being tracked
>> in [2] and the corresponding Debian bug is [3]. My guess is that as
>> zfs-linux is not i
acked
> in [2] and the corresponding Debian bug is [3]. My guess is that as
> zfs-linux is not in "main" but "contrib", and the issue is marked
> "no-dsa" (see [4]), there may be no urgency to provide a stable update.
> But you may send a follow up in the tracking bu
t seems that Bookworm's zfs-dkms package (from contrib) has the data
> > corruption bug that was fixed with OpenZFS 2.1.14 (and 2.2.2) on 2023-11-30.
> >
> > https://github.com/openzfs/zfs/releases/tag/zfs-2.1.14
> >
> > However, I see no relevant bug report in
Jan Ingvoldstad writes:
> Hi,
>
> It seems that Bookworm's zfs-dkms package (from contrib) has the data
> corruption bug that was fixed with OpenZFS 2.1.14 (and 2.2.2) on 2023-11-30.
>
> https://github.com/openzfs/zfs/releases/tag/zfs-2.1.14
>
> However, I see no r
> On 9 Jan 2024, at 06:41, Jan Ingvoldstad wrote:
>
> Hi,
>
> It seems that Bookworm's zfs-dkms package (from contrib) has the data
> corruption bug that was fixed with OpenZFS 2.1.14 (and 2.2.2) on 2023-11-30.
>
> https://github.com/openzfs/zfs/releases/tag/zfs-
Hi,
It seems that Bookworm's zfs-dkms package (from contrib) has the data
corruption bug that was fixed with OpenZFS 2.1.14 (and 2.2.2) on 2023-11-30.
https://github.com/openzfs/zfs/releases/tag/zfs-2.1.14
However, I see no relevant bug report in the bug tracker - have my
searching s
On Sat, 30 Dec 2023 17:50:03 +
Andrew Wood wrote:
> Found the following issue when running an upgrade.
>
> Apache refuses to restart with error:
>
> apache2_reload: Your configuration is broken. Not restarting Apache 2
> apache2_reload: apache2: Syntax error on line 146 of
> /etc/apache2/a
Andrew Wood wrote:
> This is because the php7.4 files have now been replaced with php8.2
>
> Specifically sym linsk in /etc/apache2/mods-enabled/ which link to
> /etc/apache2/mods-available/
> php7.4.conf -> ../mods-available/php7.4.conf
> php7.4.load -> ../mods-available/php7.4.load
>
> Shoul
Found the following issue when running an upgrade.
Apache refuses to restart with error:
apache2_reload: Your configuration is broken. Not restarting Apache 2
apache2_reload: apache2: Syntax error on line 146 of
/etc/apache2/apache2.conf: Syntax error on line 3 of
/etc/apache2/mods-enabled/php
Here are some foreseeable and preventable ones.
> AFAICT the only thing really different about "the bug"
> (#1057967/#1057969) is that it comes right after a bug that made a lot
> of noise (bug#1057843), so people have temporarily lost faith.
No faith lost on my part. And bug
>>>>> If so, then IIUC the answer is a resounding "YES, it is safe!".
> Safe not to fry your ext4 by Bug#1057843, yes, Stefan.
> Safe in general, as originally asked by Rick?
> He might be lucky, or maybe less so.
But that's always true: the GNU/Linu
;>>> If so, then IIUC the answer is a resounding "YES, it is safe!".
Safe not to fry your ext4 by Bug#1057843, yes, Stefan.
Safe in general, as originally asked by Rick? He might be lucky, or
maybe less so.
>>> Safety is subjective. A great deal will depend on what kind o
On Wed, Dec 13, 2023 at 10:33:15AM -0500, Greg Wooledge wrote:
[...]
> Perhaps I'm reading it incorrectly, but I still feel it's wise to wait
> a little while and see if any more problems pop up, if stability is
> important to you. I also salute the courage of those who've tested
> these recent
On Wed, 2023-12-13 at 10:10 -0500, Greg Wooledge wrote:
> If it's a remote server to which you have limited
> or no physical access, booting a kernel that may "just be unusable"
> (enough to prevent editing GRUB menus and rebooting) could be a disaster.
Which is what happened a few years ago to me
t.
Who knows, though :)
My superficial understanding, after skimming through the bug report,
is that problems could be triggered just by *loading* one of the
affected wifi driver modules. This would happen for any machine that
has one of the "right" kinds of wifi hardware, even if t
oting) could be a disaster.
>
> ...but that one most probably won't be attached via a Broadcom to the 'net.
>
> Who knows, though :)
My superficial understanding, after skimming through the bug report,
is that problems could be triggered just by *loading* one of the
affected
On Wed, Dec 13, 2023 at 10:10:37AM -0500, Greg Wooledge wrote:
> On Wed, Dec 13, 2023 at 09:56:46AM -0500, Stefan Monnier wrote:
> > If so, then IIUC the answer is a resounding "YES, it is safe!".
> > It just may be unusable, so you may have to downgrade to 6.1.0-13 until
> > the problem is fixed.
On Wed, Dec 13, 2023 at 09:56:46AM -0500, Stefan Monnier wrote:
> If so, then IIUC the answer is a resounding "YES, it is safe!".
> It just may be unusable, so you may have to downgrade to 6.1.0-13 until
> the problem is fixed.
>
> That's a very different issue from the ext4 corruption problem in
gt; Though unless I'm misunderstanding, just having a wi-fi (used or not) is
>> > > enough to trigger the bug. Please correct me if I'm wrong.
>> >
>> > "the bug"?
>> >
>> > What's this bug you're referring to?
>>
On 13 Dec 2023 16:23 +0900, from j...@bunsenlabs.org (John Crawley):
>> |Debian Bug report logs - #1057967
>> |Found in version linux/6.1.66-1
>> |Fixed in version linux/6.1.67-1
>
> Good to know, but as of now (Wed 13 Dec 07:20:59 UTC 2023):
> [...]
> Have to wait a
On 13/12/2023 15:24, Geert Stappers wrote:
An attempt to get beyond FUD
|Debian Bug report logs - #1057967
|linux-image-6.1.0-15-amd64 renders my physical bookworm/gnome computer largely
unusable version graph
|Package: src:linux; Maintainer for src:linux is Debian Kernel Team
;
|Affects
it.
> > > > Though unless I'm misunderstanding, just having a wi-fi (used or not) is
> > > > enough to trigger the bug. Please correct me if I'm wrong.
> > >
> > > "the bug"?
> > >
> > > What's this b
used or not) is
> > > enough to trigger the bug. Please correct me if I'm wrong.
> >
> > "the bug"?
> >
> > What's this bug you're referring to?
>
> Perhaps:
>
> https://lists.debian.org/debian-user/2023/12/msg
Can anyone please explain:
1. Why upgrades of stable into a potentially seriously compromised state were
allowed to continue, twice, rather than pulling the upgrades? or...
2. Why the best temporary solution isn't to revert the kernel to the last known
good version so upgrades-other-than-kernel
On Tue 12 Dec 2023 at 23:05:49 (-0500), Stefan Monnier wrote:
> > Well, the machine in question has a wi-fi but I don't plan on using it.
> > Though unless I'm misunderstanding, just having a wi-fi (used or not) is
> > enough to trigger the bug. Please correct me
> Well, the machine in question has a wi-fi but I don't plan on using it.
> Though unless I'm misunderstanding, just having a wi-fi (used or not) is
> enough to trigger the bug. Please correct me if I'm wrong.
"the bug"?
What's this bug you're referring to?
Stefan
Iman Hajibagheri wrote:
> Hello
> My laptop model is asus zenbook duo ux481 and I installed ubuntu desktop
> After installation, when I log in to my account for the first time, a
> welcome to ubuntu tab appears. I click on the help improve ubuntu section.
> My laptop stops after the yes option and
Hello
My laptop model is asus zenbook duo ux481 and I installed ubuntu desktop
After installation, when I log in to my account for the first time, a
welcome to ubuntu tab appears. I click on the help improve ubuntu section.
My laptop stops after the yes option and the operating system crashes. I
th
Testing
On Mon, Dec 4, 2023, 3:30 AM Thomas Schmitt wrote:
> .
> This seems to indicate that the firmware has a stake in the problem ...
>
> > Both the Thinkpad E14 Gen 5s had the same specifications and type number,
> > differing only in that the one with corruption of the installer has 24GB
> of
>
On 11/2/23 01:05, gene heskett wrote:
On 11/2/23 01:46, David Christensen wrote:
On 11/1/23 18:34, gene heskett wrote:
So what i'm going to do next is transfer my /home, the whole MaryAnn
from a 4 drive raid10 to a single 2T SSD,, and then switch /home from
the raid to a single drive, thereby
On 11/2/23 01:46, David Christensen wrote:
On 11/1/23 18:34, gene heskett wrote:
So what i'm going to do next is transfer my /home, the whole MaryAnn
from a 4 drive raid10 to a single 2T SSD,, and then switch /home from
the raid to a single drive, thereby removing the raid10 from the
culprit
On 11/1/23 18:34, gene heskett wrote:
So what i'm going to do next is transfer my /home, the whole MaryAnn
from a 4 drive raid10 to a single 2T SSD,, and then switch /home from
the raid to a single drive, thereby removing the raid10 from the culprit
list.
If that doesn't fix it, then its som
x27;s
about Volkswagen Bug automobiles.
That is informative, thanks Felix, but what is wrong with publishing
the correct address? Not being able to use it, I haven't reserved space
for it in the wet ram... ;o)>
For one thing, I never use it directly, and another, it doesn't i
gene heskett composed on 2023-11-01 19:20 (UTC-0400):
> Felix Miata wrote:
>> gene heskett composed on 2023-10-31 10:26 (UTC-0400):
>>> Mail sent to ad...@bugzilla.com bounces.
>> Bugzilla.com has nothing to do with tracking any kind of software issues.
>>
Am 26.10.2023 um 19:29:13 Uhr schrieb Kevin Freeman:
> I have a bug here that needs to be reported.
Please use the "reportbug" software for that, so it is in the bug
tracker and maintainers can find it.
> It has been present in multiple versions and still exists in Debian
&g
Dear friend,
Hello, I have a bug here that needs to be reported. It has been present in
multiple versions and still exists in Debian 12. The issue is related to
the desktop version's Wi-Fi icon and driver. While I can use Wi-Fi to
connect to the internet, I would like to have a more intu
> I have a bug report but am not sure which package it should be filed
> against. The Weather Report application, version 1.24.1, is affected,
> as is the weather reported by the Clock application, version 1.24.1, in
> the MATE desktop environment. Neither reports the correct weathe
On 10/18/23 00:18, Greg Marks wrote:
I have a bug report but am not sure which package it should be filed
against. The Weather Report application, version 1.24.1, is affected,
as is the weather reported by the Clock application, version 1.24.1, in
the MATE desktop environment. Neither reports
I have a bug report but am not sure which package it should be filed
against. The Weather Report application, version 1.24.1, is affected,
as is the weather reported by the Clock application, version 1.24.1, in
the MATE desktop environment. Neither reports the correct weather, and
the log files
Hello guys,
i'm running linux debian stable and i had troubles running gufw, i
solved the issue by installing the package polkit-mate and then add to
the startup programms the application:
/usr/libexec/polkit-mate-authentication-agent-1.
i am using xfce4, here is the output of dpkg --status ap
On Sun, Sep 24, 2023 at 11:13:44AM +, Sarah Marsh wrote:
> I am emailing to find information on how to file a bug report with Debian.
https://www.debian.org/Bugs/Reporting
> I received a message on my command line to file a report for the issue that I
> am having with the command
I am emailing to find information on how to file a bug report with Debian. I
received a message on my command line to file a report for the issue that I am
having with the command line and the Computer itself. The website says to file
through the command line but my commands do not work, I am
for Gtk > MenuBarAccel
> > Double-click on the row of "MenuBarAccel" to edit this property
> > In the "Edit Property" dialog, delete the value F10 (leave it
> > blank) and click Save.
>
> Mine still shows F10. I don't believe I've ever touched it.
>
I've got it on sid. I've reported it as bug 1050734.
The other mc workaround is 10 on the menu bar at the bottom.
--
Joe
On Sat, 23 Sep 2023 22:53:44 +0200
Greg wrote:
> I'm using mc in xfce4-terminal. To close mc you use F10 key.
> Unfortunately, the xfce4-terminal option
> Edit->Preferences->Advance->Disable menu shortcut key (F10 by default)
> Does not work. Whatever I set, F10 always activates menu.
Which ver
ut key (F10 by default)
Does not work. Whatever I set, F10 always activates menu.
Is this a bug? Could someone fix? Is there any workaround?
I'm not having the problem you describe on an up-to-date Bookworm
installation. In xfce4-terminal, choosing to disable the menu shortcut
key, starting
rk. Whatever I set, F10 always activates menu.
Is this a bug? Could someone fix? Is there any workaround?
I'm not having the problem you describe on an up-to-date Bookworm
installation. In xfce4-terminal, choosing to disable the menu shortcut
key, starting Midnight Commander and pressin
F10 always activates menu.
>
> Is this a bug? Could someone fix? Is there any workaround?
I'm not having the problem you describe on an up-to-date Bookworm
installation. In xfce4-terminal, choosing to disable the menu shortcut
key, starting Midnight Commander and pressing F10 brings u
Hi there,
I'm using mc in xfce4-terminal. To close mc you use F10 key.
Unfortunately, the xfce4-terminal option
Edit->Preferences->Advance->Disable menu shortcut key (F10 by default)
Does not work. Whatever I set, F10 always activates menu.
Is this a bug? Could someone fix
On Sep 07, 2023, duh_gently...@simplelogin.com wrote:
> Thank you for your advice!
No problem.
>
> lspci says:
> 00:01.3 PCI bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models
> 00h-0fh) PCIe GPP Bridge
Okay so it's the root PCI bridge on the motherboard. Are there any
BIOS/UEFI upd
user interface will not start.
On 07/09/2023 12.24, Dan Purgert - dan at djph.net wrote:
On Sep 07, 2023, duh_gently...@simplelogin.com wrote:
Hello,
I'd like to submit a bug, but I'm not quite sure which package it
should be.
I could not find anything similar in the bugtracker.
The probl
On Sep 07, 2023, duh_gently...@simplelogin.com wrote:
> Hello,
>
> I'd like to submit a bug, but I'm not quite sure which package it
> should be.
> I could not find anything similar in the bugtracker.
>
> The problem occurs every 10-20 times. After the syste
Hello,
I'd like to submit a bug, but I'm not quite sure which package it should
be. I could not find anything similar in the bugtracker.
The problem occurs every 10-20 times. After the system has been
suspended and then resumed, the following message is written to kern.log
On 2023-09-04, Dominique Dumont wrote:
> On Friday, 1 September 2023 04:37:37 CEST Wang Yizhen wrote:
>> Whenever I finished editing, I would delete the frame while keeping the
>> emacs running as daemon in the background. And next time when I wish to
>> edit anything, I would use the emacsclient
On Friday, 1 September 2023 04:37:37 CEST Wang Yizhen wrote:
> Whenever I finished editing, I would delete the frame while keeping the
> emacs running as daemon in the background. And next time when I wish to
> edit anything, I would use the emacsclient command in the terminal.
> `emacsclient -c -
On 2023-08-31, Charles Curley wrote:
> You need an emacs process running in order to use emacsclient. It need
> not be a daemon. -a="" will launch a daemon process if there isn't a
> process already running, daemon or otherwise.
emacs is enough if you put start-server in init file. Else it don't
a few days and found the solution at this link:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050287
Specifically it was this bit that fixed the issue:
Package: r8168-dkms
Version: 8.051.02-3
Severity: important
Dear Maintainer,
I confirm that the bug is present
> I would use the emacsclient command in the terminal. `emacsclient -c
> -a ""` somehow does the work, but it occupies the terminal until the
> new emacsclient frame is killed,
Try
emacsclient -c -a "" &
--
John Hasler
j...@sugarbit.com
Elmwood, WI USA
> > After upgraded to emacs 29.1+1-5, I found that the emacsclient
> > command is not working. More specifically, the following command
> > hangs emacs in daemon forever and no emacs frame pops up:
> >
> >
> > ```
> >
> > emacsclient -c -a "" -n
> >
> > ```
>
> What exactly are you trying to do?
>
> After upgraded to emacs 29.1+1-5, I found that the emacsclient
> command is not working. More specifically, the following command
> hangs emacs in daemon forever and no emacs frame pops up:
>
>
> ```
>
> emacsclient -c -a "" -n
>
> ```
What exactly are you trying to do?
The customary way
On 01/09/2023 00:10, Wang Yizhen wrote:
emacsclient -c -a "" -n
Instead of --alternate-editor= I would consider socket activation by
systemd user session. It ensures that emacs server process is started in
controlled environment that does not depend on caller process.
You may try to add exp
On Thu, 31 Aug 2023 23:59:11 +0200
Michel Verdier wrote:
> According to your link and what I do myself I think you need to have a
> daemon running. And emacsclient -a="" launches it if it's missing.
You need an emacs process running in order to use emacsclient. It need
not be a daemon. -a="" wil
On 2023-08-31, Charles Curley wrote:
> Having set up to use emacsclient, you (or more likely, programs
> you use such as a mail reader) can then call emacsclient so you can then
> edit files from that program in emacs. If you do it that way, you don't
> get (or need) an instance of emacs in daemon
On 8/31/23, Wang Yizhen wrote:
>
> I recently noticed a bug for the emacs package in sid. I have not
> reported a bug before, so I wrote this email to seek for help.
>
> After upgraded to emacs 29.1+1-5, I found that the emacsclient command
> is not working. More specifica
On Fri, 1 Sep 2023 01:10:46 +0800
Wang Yizhen wrote:
> After upgraded to emacs 29.1+1-5, I found that the emacsclient
> command is not working. More specifically, the following command
> hangs emacs in daemon forever and no emacs frame pops up:
>
>
> ```
>
> emacsclient -c -a "" -n
>
> ```
W
On 1 Sep 2023 01:10 +0800, from wang1zhe...@gmail.com (Wang Yizhen):
> I recently noticed a bug for the emacs package in sid. I have not reported a
> bug before, so I wrote this email to seek for help.
See https://www.debian.org/Bugs/ for information on the Debian bug
tracking process, inc
Dear Debian-user group:
I recently noticed a bug for the emacs package in sid. I have not
reported a bug before, so I wrote this email to seek for help.
After upgraded to emacs 29.1+1-5, I found that the emacsclient command
is not working. More specifically, the following command hangs
ded in the BIOS.
The reason, why I am telling this is, that all former kernels did not show
this issue, the only one is the actual kernel in bookworm. Maybe this is a
bug? I am thinking of a buggy timeout error or, if there is no EDD, then it
tries again and again. This issue appeared only on my
t; mail' message appears when it should not. In the example below I pressed TAB
> after the letter 'T' (which gave me expansion 'TODO'). I am running bash.
>
> $ me TYou have mail in /var/spool/mail/addw
> ODO
You can always look for bugs filed aga
I have recently upgraded to Bookworm.
I have set:
MAIL=/var/spool/mail/addw
MAILCHECK=60
I find that when doing filename expansion, by pressing TAB, that the 'You have
mail' message appears when it should not. In the example below I pressed TAB
after the letter 'T' (which gave me
Hello,
I have set up 40 identical systems with Debian 12.0: same SBC, same OS
version, same preseed file. These systems use a touchscreen monitor with an
eGalax USB controller. eGalax driver was installed on all of the 40 systems
and everything works fine except for 2 systems that are connected to
It is a MATE problem regrading two, possibly related issues. I was thinking
mate-desktop-environment, but maybe that is wrong. Maybe it is
mate-desktop-common or something else.
It has to do with:
(1) the panel placement; Limits on which displays it allows me to place the
panel; and,
(2) the i
On Thu, Jul 20, 2023 at 03:19:20PM -0700, Jon Folsom wrote:
> Hello,
>
> In a fresh installation of Bookworm, up-to-date as of today, there is a
> problem with CUPS printer configuration. I'm not sure which package to file
> a bug report against. I'll give a summary here;
Hello,
In a fresh installation of Bookworm, up-to-date as of today, there is a
problem with CUPS printer configuration. I'm not sure which package to file
a bug report against. I'll give a summary here; please let me know which
package I should reference using `reportbug`.
I have
On 6/27/23, Stefan Monnier wrote:
>> I recently updated from Bullseye to Bookworm and noticed that font hinting
>> settings in
>> `~/.config/fontconfig/fonts.conf` are ignored. This was not the case on
>> Bullseye and I'd like to
>> report this as a bug. When I
> I recently updated from Bullseye to Bookworm and noticed that font hinting
> settings in
> `~/.config/fontconfig/fonts.conf` are ignored. This was not the case on
> Bullseye and I'd like to
> report this as a bug. When I run reportbug it asks for a package name, but I
Hi all,
I recently updated from Bullseye to Bookworm and noticed that font hinting
settings in
`~/.config/fontconfig/fonts.conf` are ignored. This was not the case on
Bullseye and I'd like to
report this as a bug. When I run reportbug it asks for a package name, but I
have no idea
Hello Debian Team,
I have a bug to report and have not done that before, thus, I need some
assistance. My bug isn't with a specific package. If so, I am not sure
which one. Below I will describe the issue.
I use a Lenovo T560 with a Lenovo dock. It is the one that Lenovo made
for
пн, 5 июн. 2023 г. в 05:36, Paul Martz :
> If I mute audio in the desktop, then reboot into console mode, the SpeakUp
> screen reading software is also muted. I think this is a bug - muting the
> desktop should be a desktop property and should not affect the console screen
> rea
Hi all.
If I mute audio in the desktop, then reboot into console mode, the SpeakUp
screen reading software is also muted. I think this is a bug - muting the
desktop should be a desktop property and should not affect the console screen
reader. But I’m not sure which package I should file the
On Sat, May 13, 2023 at 10:18:37AM +, Schwibinger Michael wrote:
> * For Debian based distributions:
> # dpkg -i epson-inkjet-printer-escpr_.deb
>
>
>
> What is the name of architecture?
Typically, either amd64 or i386, depending on which one you installed.
The canonical way to find out
On Sat, May 13, 2023 at 10:18:37AM +, Schwibinger Michael wrote:
> First
> You asked for the bug message:
>
> https://ibb.co/Xtbz1Qp
> [https://i.ibb.co/jDTLmNG/epsonprot.jpg]<https://ibb.co/Xtbz1Qp>
> epsonprot hosted at ImgBB<https://ibb.co/Xtbz1Qp>
>
First
You asked for the bug message:
https://ibb.co/Xtbz1Qp
[https://i.ibb.co/jDTLmNG/epsonprot.jpg]<https://ibb.co/Xtbz1Qp>
epsonprot hosted at ImgBB<https://ibb.co/Xtbz1Qp>
Image epsonprot hosted in ImgBB
ibb.co
Good morning
https://www.epson.co.uk/products/printers/ink
gt; > > look
> > > > > > > just the same?
> > > > > > I enable GRUB_DISABLE_OS_PROBER so that the various other operating
> > > > > > systems are shown
> > > > > > if the new GRUB is properly installed I get the &q
ot with the "old" GRUB menu as explained above...it has Several
operating systems listed, my old default OS is still at the top of the
list.
back to the WiFi dongle, again the obscure firmware was properly installed
Is this a Bug or a user/hardware issue?
Presumably we are now back to talk
lained above...it has Several
operating systems listed, my old default OS is still at the top of the
list.
back to the WiFi dongle, again the obscure firmware was properly installed
Is this a Bug or a user/hardware issue?
Presumably we are now back to talking about Grub.
If you still hav
On Fri 21 Apr 2023 at 23:05:53 (+0700), Max Nikulin wrote:
> On 21/04/2023 11:26, David Wright wrote:
> > On Fri 21 Apr 2023 at 09:48:43 (+0700), Max Nikulin wrote:
> >
> > > Opt-out variant for ESP sounds reasonable for me. However I am unsure
> > > if it is possible to complete installation with
On 21/04/2023 11:26, David Wright wrote:
On Fri 21 Apr 2023 at 09:48:43 (+0700), Max Nikulin wrote:
Opt-out variant for ESP sounds reasonable for me. However I am unsure
if it is possible to complete installation with no ESP at all.
If you mean: to install Grub but not write to the ESP,
No,
On Fri 21 Apr 2023 at 09:48:43 (+0700), Max Nikulin wrote:
> Opt-out variant for ESP sounds reasonable for me. However I am unsure
> if it is possible to complete installation with no ESP at all.
If you mean: to install Grub but not write to the ESP, I think you can
do this by saying Yes to:
┌──
on 2 disks, both ones are marked
for usage as ESP. I am unsure if it causes installation error later or
grub is installed on both ones (taking into account single /boot/efi
mount point).
Do you contribute to d-i?
No, I do not. You may check if your case has been discussed on the
installer mail
201 - 300 of 5957 matches
Mail list logo
