Hi,
to...@tuxteam.de wrote:
> Ah, it seems to be this one, from 2002:
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=155175
So it's not a bug but a feature. :(
I'm riddling over the code about the connection to an old graphics
algorithm (Bresenham's Algorithm) and how shred pr
On 2/10/24 08:32, Thomas Schmitt wrote:
Hi,
i wrote:
shred: -: invalid file type
to...@tuxteam.de wrote:
Hmm. This looks like a genuine bug: the man page mentions it.
Even the help text in
https://sources.debian.org/src/coreutils/9.4-3/src/shred.c/
says
If FILE is -, shred
Hi,
i wrote:
> > shred: -: invalid file type
to...@tuxteam.de wrote:
> Hmm. This looks like a genuine bug: the man page mentions it.
Even the help text in
https://sources.debian.org/src/coreutils/9.4-3/src/shred.c/
says
If FILE is -, shred standard output.
The name "-&
gt; > A non-existing file path causes "No such file or directory".
>
> Hmm. This looks like a genuine bug: the man page mentions it.
>
> Also, /dev/stdout as target runs into the very same problem.
Ah, it seems to be this one, from 2002:
https://bugs.debian.org/cgi-bin/b
On Sat, Feb 10, 2024 at 11:38:21AM +0100, Thomas Schmitt wrote:
[...]
> But shred(1) on Debian 11 refuses on "-" contrary to its documentation:
> shred: -: invalid file type
> A non-existing file path causes "No such file or directory".
Hmm. This looks lik
Tim Janssen wrote:
> I use debian server on my NUC to run a low powered home server. It freezes
> every 2-3 days what looks to be a kernel bug. From a lot of testing it only
> occurs when the ethernet cable is inserted and it seems it has to do
> something with low power mo
Dear Sir/Madam,
I use debian server on my NUC to run a low powered home server. It freezes
every 2-3 days what looks to be a kernel bug. From a lot of testing it only
occurs when the ethernet cable is inserted and it seems it has to do
something with low power mode (c-states). These issues have
twice it gives
list of candidates, so I do not see any difference from Tab Tab. Perhaps
I just use it rarely enough, so I believe that moving cursor is less
convenient. 2 keys instead of single Tab is not a problem, anyway I use
[Ctrl+/] (undo) frequently enough.
Concerning the bug, may
On Tue 30 Jan 2024 at 10:34:21 (+0700), Max Nikulin wrote:
> On 30/01/2024 02:51, David Wright wrote:
> > . Press HOME,
> > . Type any letter that makes a "wrong" command name (eg aokular),
> > . Press END,
>
> The escape "Esc /" workaround has been posted in this thread already.
Yes, I believe
On 30/01/2024 02:51, David Wright wrote:
. Press HOME,
. Type any letter that makes a "wrong" command name (eg aokular),
. Press END,
The escape "Esc /" workaround has been posted in this thread already. It
uses built-in readline path completion instead of BASH programmable
completion. It
On 1/29/24 20:59, Greg Wooledge wrote:
complete -r isn't intended as a workaround. It's intended as a diagnostic
step.
Seeing the problem go away when completion goes away means that the
problem is *in* the completion. Thus, he knows which package to file
a bug report against.
Yes, I
n using completion for directory/filenames,
> . Once you reach the right directory, and if you need filtering,
> press HOME DELETE END and you've got filtering back again.
> . Obviously press HOME DELETE if you didn't do the previous step.
>
> > I will submit a bug report for
makes a "wrong" command name (eg aokular),
. Press END,
. Press TAB and carry on using completion for directory/filenames,
. Once you reach the right directory, and if you need filtering,
press HOME DELETE END and you've got filtering back again.
. Obviously press HOME DELETE if you didn't do the previous step.
> I will submit a bug report for the package bash-completion.
Cheers,
David.
h itself (hint: it's not).
Thank you for your responses! After 'complete -r' the problem
disappears. I should add that I never touched the autocomplete settings.
I will submit a bug report for the package bash-completion.
On Mon 29 Jan 2024 at 12:59:39 (-0500), Greg Wooledge wrote:
> On Tue, Jan 30, 2024 at 12:05:24AM +0700, Max Nikulin wrote:
> > On 29/01/2024 19:40, Greg Wooledge wrote:
> > > Let me test that as well
> > [...]
> > > unicorn:/tmp$ xyz dir\ with\ blanks/dir2/file
> >
> > "okular" is important
On Tue, Jan 30, 2024 at 12:05:24AM +0700, Max Nikulin wrote:
> On 29/01/2024 19:40, Greg Wooledge wrote:
> > Let me test that as well
> [...]
> > unicorn:/tmp$ xyz dir\ with\ blanks/dir2/file
>
> "okular" is important here. Only limited set of file name suffixes are
> allowed for some
On 29/01/2024 19:40, Greg Wooledge wrote:
Let me test that as well
[...]
unicorn:/tmp$ xyz dir\ with\ blanks/dir2/file
"okular" is important here. Only limited set of file name suffixes are
allowed for some commands. You do not need to have okular installed,
completion rules are part
uot;/file
>
> (first experiments with tab completion, not shown)
>
> unicorn:/tmp$ mkdir -p 'dir with blanks'/dir1
> unicorn:/tmp$ touch "$_"/otherfile
> unicorn:/tmp$ xyz dir\ with\ blanks/dir
> dir1/ dir2/
> unicorn:/tmp$ xyz dir\ with\ blanks/dir2/file
>
> I'
r\ with\ blanks/dir
dir1/ dir2/
unicorn:/tmp$ xyz dir\ with\ blanks/dir2/file
I'm assuming whatever issue you're seeing is the result of a
bash-completion bug, not a bash bug. If you can confirm that, then
you'll know which package to file a bug against.
Dear Debian Team,
I think I found a bug, and I'm writing to this list as I don't know the
associated package (according to https://www.debian.org/Bugs/Reporting).
I'm experiencing this bug in konsole (KDE's terminal emulator), but the
same bug has been reported here
https://askubuntu.com
-1.3.2-linux-x86-64/bin/cwebp /usr/bin/cwebp'
returned a non-zero code: 1
What happens if you run the mv(1) command by hand?
# mv /tmp/webp/unzipped/libwebp-1.3.2-linux-x86-64/bin/cwebp /usr/bin/cwebp
The reason I'm here is because of this bug:
https://bugs.debian.org/cgi-bin/bugreport.cgi
9.39G 493G 9.39G
/var/lib/docker*
```
Of course these paths shouldn't be relevant as all of the paths in the
docker container should be inside a docker volume all mounted under
/var/lib/docker.
The reason I'm here is because of this bug:
https://bugs.debian.org/cgi-bin
Good afternoon
Another option is to use a keyboard shortcut. My last laptop came with
this set up using a Fn key combo (eg fn-f5)
So I'm using a key that was set to answer MSteams calls - what?
Check keyboard - shortcuts - touchpad. cinnamon gives options of
toggle/switch on/ switch-off. I
On 25/01/2024 21:42, Max Nikulin wrote:
Try
lsusb --verbose --tree
I have received a private reply. Please, send messages to the mailing
list in such cases.
I intentionally combined -vt options and I find output more convenient
than for just "lsusb -t". The "-t" option changes
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
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
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 it via repo
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 in mc. SSH in
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 Shell Link i
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 properly.
The bug
h
>> 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
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 be no urgency to provide a stable update.
> But you may send a follow up in the tracking
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 the b
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 releva
> 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-2.
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 skills
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
>
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
>
>
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
e 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 bugs
>>>>> 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/Linux sys
;>>> 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
h :)
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 that hardware
isn't a
ld 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 wifi driver modules
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
hough 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?
>>
>> Perhaps:
>&
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 w
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
> > > > 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
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/msg00680.html
>
> h
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
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 if I'm wr
> 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
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
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
>
ournal,
seguramente tengas algún mensaje de error que te pueda dar alguna
pista.
- Baja alguna LiveCD de Ubuntu u otra distribución modernita para ver
si te sigue haciendo lo mismo.
>> He intentado hacer un bug report pero no he sabido a que paquete le
>> corresponde el bug no se
rele Hub USB C con Ethernet - 5 en 1:
>
> [2]https://www.amazon.es/gp/product/B09ZQNCQHC/ref=ppx_yo_dt_b_asin_title_o04_s00?ie=UTF8=1
>He intentado hacer un bug report pero no he sabido a que paquete le
>corresponde el bug no se si es problema de GNOME o de Wayland o del driver
&g
Revodok Pro 10 En 1:
https://www.amazon.es/dp/B0BXDQS4BD?psc=1=ppx_yo2ov_dt_b_product_details
El Lemorele Hub USB C con Ethernet - 5 en 1:
https://www.amazon.es/gp/product/B09ZQNCQHC/ref=ppx_yo_dt_b_asin_title_o04_s00?ie=UTF8=1
He intentado hacer un bug report pero no he sabido a que paquete le
Rectifico si utilizo el adaptador incluido por defecto con el portátil da los
mismos problemas que el original.
De: Aimar Urteaga
Enviado: sábado, 2 de diciembre de 2023 18:47
Para: debian-user-spanish@lists.debian.org
Asunto: Problema reportando bug
Hola
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,
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
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 include the
str
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
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 intuitive
> 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 cor
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
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 com
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
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
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 Midnight
hatever 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 pressing 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 up the dial
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? Is
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
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 problem occurs every
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 syst
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
and syslog
In-Reply-To: <8fd40dfa-6fe1-7888-daaf-08012c726...@vandervlis.nl>
X-Previous-Subject: Re: libdvd-pkg’s postinst script is broken
On Mon, Sep 04, 2023 at 11:28:03PM +0200, Paul van der Vlis wrote:
>
> Nu heb ik de bug gefixed volgens mij. Maar wat te doen met het resultaat?
Toevo
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
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
for 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
101 - 200 of 8562 matches
Mail list logo
