On Tue, Sep 29, 2020 at 4:10 PM Nicolas Bock <1891...@bugs.launchpad.net>
wrote:
> On Tue, Sep 29 2020, Brian Murray wrote:
>
> > On Tue, Sep 29, 2020 at 12:38:38PM -, Nicolas Bock wrote:
> > Could you please run 'systemctl status whoopsie' and
> > include the output of the command here?
>
>
@Brian M:
As you suggest that my or my problem reported likely by Dan van Vugt
with my install of Ubuntu-MATE 20.10 had this similar problem of long
strings of "Failed to start " items in the TTY and very long boot times
. . . wasn't exactly "fixed" by trashing the /var/crash directory as he
@Daniel:
Thanks again for those commands . . . I didn't know if removing the
whole crash directory was the way to remove those files . . . .
So I ran that command, then I did the "apt update" . . . but then I ran
"apt -f install" . . . and that showed a bunch of things to add and
subtract . . .
Public bug reported:
Been having problems with my installation of 20.10 U-MATE . . . reported
here earlier to little fanfare . . . but the issues with very slow boot
times, and then when finally arriving at GUI log in window, the log in
"tray" is positioned upper left corner of the display and
Adding my story here . . . in U-MATE running sources.list as "devel" and
some of the list is ID-ing as "groovy" . . . it is showing as 20.10 . .
. had some issues with the broadcom package not updating in apt, so on
the U-MATE forum with wolfman and he had me look at my "Software &
Updates" data,
Just to add my $.02 . . . I also had this problem with perhaps 6/12
daily and then I zsyncd what I think is the 6/15 daily . . . finding the
same "kernel panic" report as Dan found. A couple days later I
downloaded a fresh 19.04 iso and ran the install . . . and that went
well.
Glad to hear that
On Sat, Jul 30, 2016 at 5:04 AM, ernsteiswuerfel
wrote:
> Glad to hear you finally got it working, somehow. ;-)
Me too . . . must have been some "divine intervention" . . . as I was about
to give up on it for the day. I believe it was the choice for "fbdev"
driver that
Public bug reported:
I was working on bug #1541082 which was reporting "blotchy" graphics
images on my PowerMac3,1 with Rage ATI Pro 128 card . . . and got the
suggestion to try to add the "r128" driver, which I did. After that the
display went black. After fiddling around with it, I removed
On Fri, Jul 29, 2016 at 11:20 AM, Fritz Hudnut <este.el@gmail.com>
wrote:
> But, I was thinking this morning I have some notes about the display
> "modes" where I have used something like "1024 x 768@60-32" . . .
> something like that, and ***that*** did mak
On Fri, Jul 29, 2016 at 10:24 AM, ernsteiswuerfel
wrote:
> Added the upstream bug to this tracker. Then I realized that strictly
> speaking this bug "X doesn't start with r128 driver (ATI RAGE)
> [powerpc]" has a different meaning from this one here "blotchy
> graphics". I
On Wed, Jul 27, 2016 at 4:19 PM, ernsteiswuerfel
wrote:
> It would be a good idea to let the
> upstream devs know that. xorg/driver/xf86-video-r128 is actively
> maintained and still receives patches (last one 8 days ago). You could
> file a bug against upstream:
>
On Wed, Jul 27, 2016 at 4:19 PM, ernsteiswuerfel
wrote:
> In the meantime you could try to get one of the other drivers
>> "modesetting", "fbdev", "fbdevhw" to work with 24 bit depth. You can use
>> my xorg.conf as starting point and edit it manually. Just put it in
>>
On Wed, Jul 27, 2016 at 4:19 PM, ernsteiswuerfel
wrote:
> In the meantime you could try to get one of the other drivers
> "modesetting", "fbdev", "fbdevhw" to work with 24 bit depth. You can use
> my xorg.conf as starting point and edit it manually. Just put it in
>
On Tue, Jul 26, 2016 at 5:40 PM, ernsteiswuerfel
wrote:
> Check your boot messages with "journalctl -k" and your
> /var/log/Xorg.0.log then you will get a hint what went wrong with r128.
>
> On current Ubuntu versions there is no need for an xorg.conf, only if
> you need to
@ernst:
I saw one of my problems, on the Xorg configure I didn't run "sudo service
lightdm stop" first . . . maybe I'll try that later or tomorrow . . . still
wondering why "r128" didn't show up in "lsmod" . . . .
F
--
You received this bug notification because you are a member of Ubuntu
Touch
>
> Just found out that the needed xserver-xorg-video-r128 package is no
> longer installed by default in Yakkety. Maybe this is also the case in
> Xenial. So the easy solution for you would be to "sudo apt-get install
> xserver-xorg-video-r128" and reboot. Maybe you get an accelerated 24bpp
>
@ernst:
Many, many thanks for the details . . . I can see numerous "errors" showing
up as the OS loads, including something about the "r128" "failing," I think
we've discussed some of these things before . . . but, since for the most
part "things were working" I didn't mess with it.
But, indeed,
@ernsteiswuerfel:
Thanks for the post. I believe that in the install of U-MATE on the 3,1
things ran so well that there is no xorg.conf. Most everything in he
display resolution is great, and it was only the background image that was
looking like the topo map.
Since the dev had gotten back to
@CP:
I took a screenshot, I think that should be pretty clear now.
F
On Mon, Jul 4, 2016 at 5:03 PM, Christopher M. Penalver <
christopher.m.penal...@gmail.com> wrote:
> Fritz Hudnut, my eyes must not be refined enough to see the problem.
>
> ** Changed in: xorg (Ubuntu)
On Mon, Jul 4, 2016 at 5:03 PM, Christopher M. Penalver <
christopher.m.penal...@gmail.com> wrote:
> Fritz Hudnut, my eyes must not be refined enough to see the problem.
It is very clear in the last photos, if you know what a topographic map
looks like? Do you know what I'm referring
On Mon, Jul 4, 2016 at 2:16 PM, Fritz Hudnut <este.el@gmail.com>
wrote:
> On Mon, Jul 4, 2016 at 1:56 PM, Christopher M. Penalver <
> christopher.m.penal...@gmail.com> wrote:
>
>> Fritz Hudnut, I think your dist-upgrade to yakkety test is sufficient
>&g
On Mon, Jul 4, 2016 at 12:16 PM, Christopher M. Penalver <
christopher.m.penal...@gmail.com> wrote:
> ** Tags added: needs-picture
Here are two of a number of shots, I was trying to keep the file size
small, as the originals are approx 1.7 MBs . . . the Xu desktop photo #135
might be a little
On Mon, Jul 4, 2016 at 9:04 AM, Christopher M. Penalver <
christopher.m.penal...@gmail.com> wrote:
> 2) To see if this is already resolved, could you please test
> http://cdimage.ubuntu.com/daily-live/current/ and advise to the results?
>
@Christopher:
I ran an update/upgrade just a few
flash drive of the daily . . . . I ***could*** do that, but, it will
take some time, and, then, question is, has anything "changed" such that it
won't be a time flush? : - 0
On Mon, Jul 4, 2016 at 9:04 AM, Christopher M. Penalver <
christopher.m.penal...@gmail.com> wrote:
>
This data was repeated numerous times at the end of the running of the
"sudo apport-collect -p xorg 1541082" Don't know if it showed up
elsewhere, this is just one "paragraph."
Crash Annotation GraphicsCriticalError: |[0][GFX1]: Unknown image format
1 (t=19.9352) |[10606][GFX1]: Unknown image
apport information
** Attachment added: "Dependencies.txt"
https://bugs.launchpad.net/bugs/1541082/+attachment/4695347/+files/Dependencies.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: "Xrandr.txt"
https://bugs.launchpad.net/bugs/1541082/+attachment/4695357/+files/Xrandr.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: "xdpyinfo.txt"
https://bugs.launchpad.net/bugs/1541082/+attachment/4695358/+files/xdpyinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1541082/+attachment/4695350/+files/Lspci.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: "JournalErrors.txt"
https://bugs.launchpad.net/bugs/1541082/+attachment/4695349/+files/JournalErrors.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1541082/+attachment/4695354/+files/UdevDb.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: "XorgLogOld.txt"
https://bugs.launchpad.net/bugs/1541082/+attachment/4695356/+files/XorgLogOld.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1541082/+attachment/4695353/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: "XorgLog.txt"
https://bugs.launchpad.net/bugs/1541082/+attachment/4695355/+files/XorgLog.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1541082/+attachment/4695351/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1541082/+attachment/4695352/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: "GconfCompiz.txt"
https://bugs.launchpad.net/bugs/1541082/+attachment/4695348/+files/GconfCompiz.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
apport information
** Tags added: apport-collected ubuntu xenial
** Description changed:
Gents:
Another issue I found on my recent install of U-MATE 16.04 PPC on my
Powermac 3,1 . . . had some "kernel certificate" errors on booting the
live DVD, which carried over to the install . .
@Gunnar:
Thanks kindly for the reply, looks like a bit before you posted here,
Manfred H on answers offered what might be a similar suggestion . . .
since he has patiently been working with me for awhile on this problem I
tried it first, and it seems to have fixed the problem . . . I'm typing
Pursuing this issue on the questions format has given me some things
to try out, including creating a new user, which I can log into and
sudo with . . . original user will not log into GUI, only TTY. I'm
adding my apport data here as the problem continues . . . .
F
--
You received this bug
OK, that seems to have failed. I guess I will open a new bug report
about this similar problem.
F
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1059254
Title:
Lightdm
Public bug reported:
I am having a problem on my iBook G4 running Lu 14.04.1 . . . after
running a recent update/upgrade with only 3 or 4 items listed, dbus
was one I remember . . . screen went black . . . tried to do something
in TTY console to restart . . . then wound up shutting down. On
apport information
** Tags added: apport-collected trusty
** Description changed:
I am having a problem on my iBook G4 running Lu 14.04.1 . . . after
running a recent update/upgrade with only 3 or 4 items listed, dbus
was one I remember . . . screen went black . . . tried to do something
I am having a problem with a similar issue as the OP on my iBook G4
running Lu 14.04 . . . after running a recent update/upgrade with only 3
or 4 items listed, dbus was one I remember . . . screen went black . .
. tried to do something in TTY console to restart . . . then wound up
shutting down.
44 matches
Mail list logo