On 4/24/21 10:04 PM, Samuel Sieb wrote:
You don't need a backtrace to report a bug. "This program crashed and I
don't know why" is still a valid bug report.
Also, be sure to include as much detail about what you were doing when
it crashed because if/when somebody's going to need it and it's b
On 25/04/2021 11:06, home user wrote:
Is that causing problems? I'm not sure why I did that. But most likely,
because I was not familiar with the various desktops, I gave myself the chance
to try all (or most?) of them and choose. I routinely use ksysguard and k3b
(from plasma), and caja (f
On 4/24/21 7:26 PM, home user wrote:
On 4/24/21 4:01 PM, Samuel Sieb wrote:
On 2021-04-24 12:37 p.m., home user wrote:
The problem report implies that a bug should not be submitted because
the backtrace does not contain enough meaningful function frames to
be reported.
Not really. What it s
On 25/04/2021 10:12, home user wrote:
Read Tim's comment again. "He" wrote the notes in a file. Not dnf or another
process.
The basis for my question was the sentence "I think the installation routine leaves a couple of files about the install in there, itself.". But I might easily be misund
On 4/24/21 8:37 PM, Ed Greshko wrote:
On 25/04/2021 10:12, home user wrote:
I recall you once did have an option for plasma on wayland.
You still have a
/usr/share/wayland-sessions/plasmawayland.desktop
file?
yes:
bash.2[~]: su -
Password:
-bash.1[~]: ls -l /usr/share/wayland-sessions/pl
On 25/04/2021 10:12, home user wrote:
A few minutes ago, I rebooted. There is only one plasma option in the menu:
"Plasma". I chose that and completed the login.
bash.1[~]: su -
Password:
-bash.1[~]: journalctl -b 0 | grep wayland
-bash.2[~]: env | grep -i wayland
-bash.3[~]:
I recall you
On 4/24/21 4:01 PM, Samuel Sieb wrote:
On 2021-04-24 12:37 p.m., home user wrote:
The problem report implies that a bug should not be submitted because
the backtrace does not contain enough meaningful function frames to be
reported.
Not really. What it said is that it can't be automatically
On 4/24/21 4:24 PM, Ed Greshko wrote:
On 25/04/2021 03:42, home user wrote:
On 4/24/21 12:34 AM, Tim via users wrote:
For later on, once you're back working again:
Next time you do an install, leave some notes in the /root homespace
about what you've done. I think the installation routine le
general FYI for everyone...
This Fedora docs web page says that wayland has been the default gnome
display server, and has been the default since F-25:
"https://docs.fedoraproject.org/en-US/quick-docs/configuring-xorg-as-default-gnome-session/";.
___
On 25/04/2021 03:42, home user wrote:
On 4/24/21 12:34 AM, Tim via users wrote:
For later on, once you're back working again:
Next time you do an install, leave some notes in the /root homespace
about what you've done. I think the installation routine leaves a
couple of files about the instal
On 2021-04-24 12:37 p.m., home user wrote:
The problem report implies that a bug should not be submitted because
the backtrace does not contain enough meaningful function frames to be
reported.
Not really. What it said is that it can't be automatically submitted,
but you can still file a bug
On Sat, 24 Apr 2021 at 16:43, home user wrote:
> On 4/24/21 12:34 AM, Tim via users wrote:
>
> > For later on, once you're back working again:
> >
> > Next time you do an install, leave some notes in the /root homespace
> > about what you've done. I think the installation routine leaves a
> > co
On 4/24/21 12:34 AM, Tim via users wrote:
For later on, once you're back working again:
Next time you do an install, leave some notes in the /root homespace
about what you've done. I think the installation routine leaves a
couple of files about the install in there, itself. And I write some
p
On 4/22/21 9:59 PM, Qiyu Yan wrote:
在 2021-04-22星期四的 11:25 -0600，home user写道：
I did my weekly patches (dnf upgrade), rebooted, and logged in as a
regular user. A problem popped-up. The top part of the details is
below. I'm not (yet) seeing any other problems. Is this a false
alarm? If not,
On 4/22/21 4:09 PM, Patrick O'Callaghan wrote:
On Thu, 2021-04-22 at 15:29 -0600, home user wrote:
On 4/22/21 3:23 PM, Patrick O'Callaghan wrote:
Was your original installation the default Workstation or KDE Spin?
It was the default workstation (GNOME?).
This would have been early spring 20
On 4/22/21 12:41 PM, Joe Zeff wrote:
On 4/22/21 11:29 AM, home user wrote:
I did that as a part of the upgrade earlier this month. But I try again:
bash.1[~]: su -
Password:
-bash.1[~]: dnf distro-sync
Last metadata expiration check: 0:51:59 ago on Thu 22 Apr 2021
10:35:59 AM MDT.
Dependenci
On Tue, 20 Apr 2021 10:32:47 +0200 Frank Elsner via users wrote:
> Hi,
>
> running an full updated Fedora 33 I have the following problem:
>
> For a few days I have been observing that the screen isn't locked
> when the system comes up after suspend. What could I have changed
> unintentionally or
On Sat, Apr 24, 2021, 6:18 AM Michael Hennebry <
henne...@web.cs.ndsu.nodak.edu> wrote:
>
> mount /dev/sda3 /mnt
> mount /proc /mnt/proc
> mount /dev /mnt/dev
> mount /dev/pts /mnt/dev/pts
>
> You need to use -B to bind mount the pseudo filesystems, and probably also
> need to include
sda3/etc/fstab :
#
# /etc/fstab
# Created by anaconda on Tue Nov 24 17:36:35 2020
#
# Accessible filesystems, by reference, are maintained under '/dev/disk/'.
# See man pages fstab(5), findfs(8), mount(8) and/or blkid(8) for more info.
#
# After editing this file, run 'systemctl daemon-reload' to
19 matches
Mail list logo
